My rooted factory ROM Vivid suddenly started having really poor battery life.
Went keyboard to keyboard with ATT who told me try a few things and eventually said to do a factory reset and try the phone for a few days with no apps installed.
After doing the reset it went into a bootloop. I have recovered from this by relocking and re loading the factory ROM.
Question is after rooting should a factory reset cause a boot loop?
Also, is there any way to get the boot loader to say locked instead of relocked for warranty purposes?
Yes
The same thing happened to me. Yes, a factory reset at the wrong time can cause a boot loop.
As for the second question, I am wondering the same thing.
Many people are saying it is not possible and that it will stay UNLOCKED or RE-LOCKED forever
Related
I got my moto x today, updated it right away to lollipop, then went to work unlocking the bootloader, rooting, and installing TWRP.
All worked great, and then i went into TWRP to do a factory reset so that I could have the setup wizard when i turned my phone back on to set it up.
well after I did a factory wipe in TWRP (now i am thinking maybe i also checked to wipe system as well, but im not positive).
after the factory reset my device boots to the boot screen, and stops on the blue m logo at the end.
So i flashed the stock kitkat images using mfastboot, and it boots to the boot screen and then shuts off, doesnt even hang at the end anymore.
What are my options/ what the hell did i do?
Hi
I have an AT&T XT1058 with locked bootloader, on 4.4.4
I tried to rest it to factory, but it got stuck on 'Erasing...' (with the little droid) for more than an hour, so I reset it.
Since then it won't boot, only keep stuck on 'Erasing...'. I've tried reflashing it with ATT_XT1058_4.4.4-KXA21.12-L1.26_CFC_1FF both using RSD lite and manually using mfastboot, but no luck - the phone still boots to 'Erasing...' and sometimes after that to the recovery.
I didn't find anything in relevant threads. Does anyone have an idea?
Selecting 'Factory' in the bootloader seemed to fix it.
It is more comlicated than that
The phone does boot after selecting 'factory' in bootloader, but only once - turning the phone off and on again brings it back to its 'erasing...' state. Besides that the phone seems to not be able to charge the battery
mokagi said:
It is more comlicated than that
The phone does boot after selecting 'factory' in bootloader, but only once - turning the phone off and on again brings it back to its 'erasing...' state. Besides that the phone seems to not be able to charge the battery
Click to expand...
Click to collapse
Were you able to get this resolved? I have a xt1095 doing the same thing when I flash a stock recovery. Just shows the android guy and just stuck at erasing... When I flash TWRP it doesn't get stuck at the "erasing..." anymore but just boots straight into TWRP.
Sorry for the late response, I missed the notification on your message.
I wasn't able to fix it, returned it to motorola.
Hi,
I just bricked my phone, maybe hard-bricked.
To explain : I locked my bootloader back to try getting back a 100% stock experience, but after locking it, it started factory reset which is stuck at 99%, when i restart, it bootloop in factory reset menu and i can't access another menu such as bootloader or eRecovery
Thanks in advance
Edit: updating using SD card isn't working too
I think it's now totally dead, i tried to reboot to bootloader after battery drain, and it don't work
wtf, without any reason, i success to access bootloader and unlock it again
I was relocking bootloader while i had oreo recovery installed and it factory reset itself(as usual) but it is stuck on 99% for an hour now.
I have a 5th gen Kindle (Kids Edition) that is bone stock. With the recent update it received to 5.6.2.0, it seems like it's stuck in this endless upgrade/downgrade loop. It runs 5.3.6.4, then it will upgrade to 5.6.2.0, reboot automatically. After awhile, it will download the 5.3.6.4 automatically to "upgrade" it, auto reboot to 5.3.x, then after awhile, it will find the 5.6.2.0 upgrade and upgrade it.
It seems to do this constantly and I can't figure out a way to get it out of this loop! I've reset it to factory, did the boot loader wiped the davlik, did a factory wipe/reset from there, and still nothing. The exact same thing.
I was hoping somebody could share a hint on how I can get this device out of the loop and back working normally again.
Thanks!