User Profile
tmutren
Newbie Caller
Joined 2 years ago
User Widgets
Contribuciones
Re: T-Mobile Revvl 6 5G Boot loop and com.android.phone error
Update 1: Don't buy this phone under any circumstances, even as a "free" replacement (it is not free of charge, you pay at least sales tax + "handling fee" of $35). I returned this phone back to T-Mobile store without replacement and got refunded for "handling fee" and sales tax.. Update 2: Same problem was mentioned here https://community.t-mobile.com/android-9/android-update-4724160Visto0likes0ComentariosRe: Tmobile Revvl 6 Pro 5G loses cellular connection after November OS update
Possibly related to this https://community.t-mobile.com/android-9/t-mobile-revvl-6-5g-boot-loop-and-com-android-phone-error-50584 I suspect something happened with IMS registration.It could be related to specific tower(s) in the area.32Visto0likes0ComentariosT-Mobile Revvl 6 5G Boot loop and com.android.phone error
I got this error for two Revvl 6 phones (returned 1st one, got the second and got this error in 36 hours after initial setup, the same as for the first phone). In 36 hours the problem started again on a new phone. Nothing helps. Full reset helps for a few hours and the problems starts again. The phone is new, nothing special is installed , only added Google Account and some apps restored using Google account (basic apps, like Facebook, Whatsapp etc). The error The errors com.android.phone pops up and in a few seconds the phone restarts by itself. Boot loop forever unless you remove SIM card. The following message displayed after restart When I press "Try again", I get the same error and restart again. Full video of the error and boot loop: https://mega.nz/file/JQ0xSQbQ#SfmNQmLz3rVlXhjS_phu0_N-vcqJtXSx6Dz5hjJzRzY I tried multiple T-Mobile SIM cards and get the same issue for both phones. The problem does not exist if the phone started without SIM card. The phone is updated to the latest available version of Android (Android 12) and latest security patch (March 2023). I am not sure 100% but this problem is related to IMS registration. I had the same problem for my old T-Mobile's LG-G4. At some point this phone became incompatible with T-Mobile VoLTE and started to trigger this error (but without bootloop). IMS was not registered after this error. I cannot verify this theory because Revvl 6 bootloops without possibility to check the status of IMS. T-Mobile should be ashamed of selling such low quality and buggy device.2.1KViews0likes1Comentario