Database Develop

[Q] XT1092 in bootloop after update

So this is a bit of a comedy of errors on my part...
I took the OTA update to lollipop and (foolishly) followed the same method as on KK to get root, putting myself in a bootloop. I got myself out of it by clearing the userdata and the cache.
I went about sorting everything and achieved root using the chainfire method, that was fine and I then went about reinstalling the xposed modules I had before. Foolishly, I didn't double check the status of xposed on Lollipop and consequently put myself back in a bootloop (idiot). I redid what had worked earlier, clearing the userdata and the cache to no avail.
Obviously, the problem was not the same as before and I needed to disable xposed, but in clearing the userdata I not only removed the xposed_disable.zip file to do this and also turned off adb so I can't push it.
The bootloader is fine and I can use fastboot, but can't push anything across. I hadn't replaced the recovery but can boot into twrp. However, I cannot flash it because I cannot push it over using adb.
I can't work out exactly how far I need to go back/what exactly I need to flash in order to put this all back together again.
I would be very grateful for any help that people can give on this.

Seems you need a .19 stock system partition image to get rid of the bootloop. Hope somebody can backup his system after OTA and share his image,otherwise you have to wait for official release or take risk to downgrade.
----------------------------
If you can boot from TWRP, you can try put the Xposed-Disabler-Recovery.zip in an USB SD card(maybe need formatted to particular filesystem like ext4) linked your phone with otg cable,then mount the sdcard and flash the zip file via TWRP.

If you're not worried about going back with a full wipe to KK, you can follow this link here Seeing that you can get your phone into fastboot, it'll work fine.

HAXTREME said:
If you're not worried about going back with a full wipe to KK, you can follow this link here Seeing that you can get your phone into fastboot, it'll work fine.
Click to expand...
Click to collapse
Thank you! This seems to have solved the problem (whatever exactly it was) and the mobile data is fine which was what I was most unsure about.
I'm curious, my device was a XT1092GB (or at least, I believe it was a GB) and now shows as a 'reteu' where I believe it used to show as 'retgb'. This isn't a problem as it all seems to work, but should I be expecting the Lollipop OTA update to come through? I deliberately didn't follow through on the last part of that thread and install 5.0 that way, I didn't want to tempt fate! However, I would like the update if possible and am unsure which way to go about doing it.
Again, many thanks for all the suggestions everyone. This is why android is awesome

Its a stock EU 4.4.4 so the OTA should come through. Even if it doesn't, I'm sure there's a 5.0 retgb firmware doing the rounds on this forum.

HAXTREME said:
Its a stock EU 4.4.4 so the OTA should come through. Even if it doesn't, I'm sure there's a 5.0 retgb firmware doing the rounds on this forum.
Click to expand...
Click to collapse
I guess even if the 5.0 OTA doesn't come through (for the reasons as given here, any following OTA updates should be fine, right?
If not, do you reckon then 5.0 rom given in the link you sent would be appropriate or would this be a better route?
Thanks for the help!

No WiFi When Going From pre-rooted 5.1 to pre-rooted 4.4.4

To those of whom have downgraded back to a rooted 4.4.4 IMG from a rooted 5.1 IMG
I started out on a 4.4.4 img from ComputerFreak and then I did all the steps in his readme to upgrade to the pre-rooted 5.1 IMG. Everything went smoothly and everything worked correctly. The reason I want to go back to KK is that the XPosed Mods I use most do not work on 5.1 just yet. So I decided to revert back to KK until those mods become available on LP.
I flashed back to stock KK. That was also successful. The only mishap that comes up when on stock KK is the "Uninstall Motorola Sensor Serivces firmware". I researched this and everyone said they did not know what it was and/or to just reboot the phone and it does not come up again. I did not choose to uninstall it or take any action besides rebooting the phone and it usually "goes away".
THE REAL ISSUE:
Whenever I flash any rooted KK IMG to the phone via mofo the wifi does not turn on, no matter which rooted KK IMG I flash to the Turbo. I go to turn on the WiFi and the little switch image simply goes back to off as soon as i release my finger.
The WiFi works on stock KK and any pre-rooted LP IMG. I have done multiple data and cache wipes. I did it every time after flashing a new IMG.
ComputerFreak and I have been trying to figure this out and no solution. He said he's had the issue before but doesn't remember how to solve it and that others have had it too.
Thanks in advance for any help!! :good::good:

zacw4328 said:
To those of whom have downgraded back to a rooted 4.4.4 IMG from a rooted 5.1 IMG
I started out on a 4.4.4 img from ComputerFreak and then I did all the steps in his readme to upgrade to the pre-rooted 5.1 IMG. Everything went smoothly and everything worked correctly. The reason I want to go back to KK is that the XPosed Mods I use most do not work on 5.1 just yet. So I decided to revert back to KK until those mods become available on LP.
I flashed back to stock KK. That was also successful. The only mishap that comes up when on stock KK is the "Uninstall Motorola Sensor Serivces firmware". I researched this and everyone said they did not know what it was and/or to just reboot the phone and it does not come up again. I did not choose to uninstall it or take any action besides rebooting the phone and it usually "goes away".
THE REAL ISSUE:
Whenever I flash any rooted KK IMG to the phone via mofo the wifi does not turn on, no matter which rooted KK IMG I flash to the Turbo. I go to turn on the WiFi and the little switch image simply goes back to off as soon as i release my finger.
The WiFi works on stock KK and any pre-rooted LP IMG. I have done multiple data and cache wipes. I did it every time after flashing a new IMG.
ComputerFreak and I have been trying to figure this out and no solution. He said he's had the issue before but doesn't remember how to solve it and that others have had it too.
Thanks in advance for any help!! :good::good:
Click to expand...
Click to collapse
Did you reflash the 4.4.4 modems and radios, or did you just flash the 4.4.4 system image? I'm assuming that when you upgraded to 5.1, you flashed the 5.1 radios and modems.

TheSt33v said:
Did you reflash the 4.4.4 modems and radios, or did you just flash the 4.4.4 system image? I'm assuming that when you upgraded to 5.1, you flashed the 5.1 radios and modems.
Click to expand...
Click to collapse
Yeah, I flashed the 4.4.4 modems and radios. Which I'm assuming that's why it works on a stock 4.4.4 IMG. But idk why when the phone has rot access it won't work.

zacw4328 said:
Yeah, I flashed the 4.4.4 modems and radios. Which I'm assuming that's why it works on a stock 4.4.4 IMG. But idk why when the phone has rot access it won't work.
Click to expand...
Click to collapse
I'd be willing to bet that it has to do with the sensor firmware message that you got before. That message is no joke. Something involving the sensor firmware or whatever that is destroyed my last Turbo, which was luckily still somehow under warranty after everything I did to it. If I were you, I'd try flashing back to stock 4.4.4 and if you see that message, pick uninstall this time.

TheSt33v said:
I'd be willing to bet that it has to do with the sensor firmware message that you got before. That message is no joke. Something involving the sensor firmware or whatever that is destroyed my last Turbo, which was luckily still somehow under warranty after everything I did to it. If I were you, I'd try flashing back to stock 4.4.4 and if you see that message, pick uninstall this time.
Click to expand...
Click to collapse
I get it when I am on stock 4.4.4. Do you know what it does though? I need my phone.. Everything is working on stock 4.4.4 and a 5.1 IMG. Just not rooted 4.4.4.

zacw4328 said:
I get it when I am on stock 4.4.4. Do you know what it does though? I need my phone.. Everything is working on stock 4.4.4 and a 5.1 IMG. Just not rooted 4.4.4.
Click to expand...
Click to collapse
I believe it's the firmware for the various sensors on the phone (IR, gyroscope, etc.). When mine got corrupted, it affected all kinds of things on the phone. It took literally 20 minutes to boot and android OS would force close, among other things. Flashing back to stock (all images) did not solve the problem, which seems to imply that the firmware is stored on a partition that isn't flashed even during a full restore. The only thing that solved the problem was allowing the firmware to uninstall. However, when I went back to 5.1, they got corrupted again, this time beyond repair.
It doesn't sound like yours are corrupted since your problems are limited to Wi-Fi, and aren't catastrophic like mine were. You probably just have the 5.1 version still installed, which doesn't play well with the 4.4.4 images for some reason. Why the problem only appears when you have root, I have no idea. Are you using a rooted image that sets SELinux to permissive? If not, that might have something to do with it.

TheSt33v said:
I believe it's the firmware for the various sensors on the phone (IR, gyroscope, etc.). When mine got corrupted, it affected all kinds of things on the phone. It took literally 20 minutes to boot and android OS would force close, among other things. Flashing back to stock (all images) did not solve the problem, which seems to imply that the firmware is stored on a partition that isn't flashed even during a full restore. The only thing that solved the problem was allowing the firmware to uninstall. However, when I went back to 5.1, they got corrupted again, this time beyond repair.
It doesn't sound like yours are corrupted since your problems are limited to Wi-Fi, and aren't catastrophic like mine were. You probably just have the 5.1 version still installed, which doesn't play well with the 4.4.4 images for some reason. Why the problem only appears when you have root, I have no idea. Are you using a rooted image that sets SELinux to permissive? If not, that might have something to do with it.
Click to expand...
Click to collapse
If it is the literal sensors for things like IR and gyro, that would make sense as my IR sensors are not on right now on stock, non-rooted KK IMG. But I am afraid that if I do the uninstall, the phone will not be usable.
I'm not sure if the IMG sets SELinux to permissive or not. @computerfreek274 any input on that?

zacw4328 said:
If it is the literal sensors for things like IR and gyro, that would make sense as my IR sensors are not on right now on stock, non-rooted KK IMG. But I am afraid that if I do the uninstall, the phone will not be usable.
I'm not sure if the IMG sets SELinux to permissive or not. @computerfreek274 any input on that?
Click to expand...
Click to collapse
If it's CF's image, it does. I would do that uninstall if I were you. It will replace it with the factory default firmware. Up to you. If you decide to do it, flash a stock, unrooted image first, and clear cache. Maybe even factory reset if it's not too much of a pain.

TheSt33v said:
If it's CF's image, it does. I would do that uninstall if I were you. It will replace it with the factory default firmware. Up to you. If you decide to do it, flash a stock, unrooted image first, and clear cache. Maybe even factory reset if it's not too much of a pain.
Click to expand...
Click to collapse
I'm already back on a factory KK IMG and did aa few factory resets and cleared cahce multiple times. So just go ahead and do the uninstall then?

zacw4328 said:
I'm already back on a factory KK IMG and did aa few factory resets and cleared cahce multiple times. So just go ahead and do the uninstall then?
Click to expand...
Click to collapse
That's my recommendation. Just to be extra safe, leave your phone on for a while after you do it. Don't reset unless it tells you to for some reason.

TheSt33v said:
That's my recommendation. Just to be extra safe, leave your phone on for a while after you do it. Don't reset unless it tells you to for some reason.
Click to expand...
Click to collapse
Alright. I might try it out tomorrow.

Look, man. I have fxzd from LP images (cf, thest33v) over and over again. eveey single time, I did the uninstall. seems the only way you will have an issue is if you do not uninstall (revert) that piece of software. you can mod the xml file in the FXZ by removing the line "erase user data" and all will be golden. personally, I tend to back up my internal and just wipe anyway, though. run the stock fxz, do that option, and you will be good. Good luck man.

kitcostantino said:
Look, man. I have fxzd from LP images (cf, thest33v) over and over again. eveey single time, I did the uninstall. seems the only way you will have an issue is if you do not uninstall (revert) that piece of software. you can mod the xml file in the FXZ by removing the line "erase user data" and all will be golden. personally, I tend to back up my internal and just wipe anyway, though. run the stock fxz, do that option, and you will be good. Good luck man.
Click to expand...
Click to collapse
TheSt33v said:
That's my recommendation. Just to be extra safe, leave your phone on for a while after you do it. Don't reset unless it tells you to for some reason.
Click to expand...
Click to collapse
I just did the uninstall. It tried to download the 5.1 OTA(I keep force stopping MotoOTA) so I force stopped that again. After a second my phone rebooted. My IR sensors now work on stock 4.4.4. I haven't flashed a rooted 4.4.4 IMG yet to see if the WiFi will then work. I will do that sometime soon. This no root is killing me haha. Luckily I at least have a modded Pandora APK for no ads and unltd skips.
[EDIT]:
Well I still cannot use WiFi when flashing a rooted KK IMG to my phone.

zacw4328 said:
I just did the uninstall. It tried to download the 5.1 OTA(I keep force stopping MotoOTA) so I force stopped that again. After a second my phone rebooted. My IR sensors now work on stock 4.4.4. I haven't flashed a rooted 4.4.4 IMG yet to see if the WiFi will then work. I will do that sometime soon. This no root is killing me haha. Luckily I at least have a modded Pandora APK for no ads and unltd skips.
[EDIT]:
Well I still cannot use WiFi when flashing a rooted KK IMG to my phone.
Click to expand...
Click to collapse
That's bizarre. Have you been using the same rooted image every time? There might be something that's just corrupt in that image.

TheSt33v said:
That's bizarre. Have you been using the same rooted image every time? There might be something that's just corrupt in that image.
Click to expand...
Click to collapse
I've tried two different ones. They worked fine before I went to the rooted 5.1 img.

Update Questions

I have a XT1060 (Dev Ed), running Lollipop 5.1, it's rooted, has xposed, and TWRP. I got a notification for a system update, would it be okay for me to do the update? Or would it soft/hard brick my phone?

Asisentr said:
I have a XT1060 (Dev Ed), running Lollipop 5.1, it's rooted, has xposed, and TWRP. I got a notification for a system update, would it be okay for me to do the update? Or would it soft/hard brick my phone?
Click to expand...
Click to collapse
I'm in the same boat (although mine is not dev edition, I have unlocked the bootloader & rooted running xposed) and would love an answer!

So I attempted to install it since no one was giving me any warnings, I flashed it back to the custom recovery, and now my phone is in a bootloop.

Asisentr said:
So I attempted to install it since no one was giving me any warnings, I flashed it back to the custom recovery, and now my phone is in a bootloop.
Click to expand...
Click to collapse
You can't update if you've modified the system partition, ex. being rooted, having xposed etc.To update you need to be completely stock.

I received the same notification on my XT1060DEV. I chose to ignore it.

Anyone know what the update is for? Someone posted in the general section to "never update a rooted unlocked XT1060 ever" because it bricked it or something. My guess is they didn't know what they were doing. I've been having issues lately with my XT1060 not wanting to connect to 2.4GHz wireless networks, only 5GHz. I've tried removing apps one-at-a-time but no luck. Maybe a reset back to square one and the update is due.
Not sure what the update is for though.

So I'm unlocked and rooted on 5.1 with TWRP... but I don't have stock recovery. XT1060 verizon dev edition doesn't have a stock recovery for anything but 4.4.4. So how do I flash recovery to take the update? I'm assuming that flashing recovery from 4.4.4 is a bad idea? If so, what's the solution?

i have 2 1060s one is retail 16 gb (one daughter) the oher is 32 gig dev tooted twrp expoesd. dev daugher tried to do the update it failed and hten she rebooted. it kept tying to apply booting to recovery after 3 minutes and and failing until I removed the update form cache.
I shoul have captured it so I could examine and fix the script.
retail 16 gb updated just fine.
anybody know what this is?
if it not an image maybe we can apply the frixes directly

Mike7143 said:
Anyone know what the update is for?.......
Not sure what the update is for though.
Click to expand...
Click to collapse
Its the security update patch upto 1st April, 2016.
https://motorola-global-portal.cust...detail/a_id/110538/p/30,6720,8696/reg/1417809
I'm on completely stock 5.1 ROM but I have TWRP 2.8.7.0, Xposed installed. So in order for OTA to succeed I'll have to undo all the modifications including the removal of Xposed? The other changes I've made to the system are the removal of some of the Motorola bloatware.
The trick is now to get the right SBF from Motorola.

Yeah to take the ota you gotta go back to stock. Honestly, I ended up just dong a factory reset, downloaded a marshmallow ROM for my xt1060, and that was that!

Mike7143 said:
Yeah to take the ota you gotta go back to stock. Honestly, I ended up just dong a factory reset, downloaded a marshmallow ROM for my xt1060, and that was that!
Click to expand...
Click to collapse
Marshmallow?!

So far it's not to bad.

What do you mean by Marshmallow update!? This is just a security update so it should still be Lollipop.

Asisentr said:
So I attempted to install it since no one was giving me any warnings, I flashed it back to the custom recovery, and now my phone is in a bootloop.
Click to expand...
Click to collapse
If you are boot-looping after trying the update with TWRP, you will have to delete the update file using TWRP.
From the TWRP main menu, Choose Advanced, then File Manager.
Go into /cache, and delete the Blur_Versionxxxxblahblahblah.zip file.
That'll stop your boot loop.

Is it safe to do a system update

I have a Droid Turbo that is currently on version 5.1 (23.21.44) and I just recently unfroze the system update notifications for my phone because of the news of MM. I am currently rooted and have an unlocked bootloader but I don't have TWRP installed and would rather not install it for now if I don't have to.
The system update that it is trying to push to my phone isn't MM, instead it is version 23.21.49.en.US. Is it safe to just take this update while being rooted and with an unlocked bootloader? I'm also not sure how many updates I'll have to make my way through before reaching the MM update, but if there are other updates, should it also be safe to go ahead with those as well? I know I could install TWRP and flash the MM ROM that way but I would prefer to do the updates officially if it is not risking a bricked phone.
Thanks for any advice.
EDIT: I forgot to finish the title of the thread...

AirJordanTS said:
I have a Droid Turbo that is currently on version 5.1 (23.21.44) and I just recently unfroze the system update notifications for my phone because of the news of MM. I am currently rooted and have an unlocked bootloader but I don't have TWRP installed and would rather not install it for now if I don't have to.
The system update that it is trying to push to my phone isn't MM, instead it is version 23.21.49.en.US. Is it safe to just take this update while being rooted and with an unlocked bootloader? I'm also not sure how many updates I'll have to make my way through before reaching the MM update, but if there are other updates, should it also be safe to go ahead with those as well? I know I could install TWRP and flash the MM ROM that way but I would prefer to do the updates officially if it is not risking a bricked phone.
Thanks for any advice.
EDIT: I forgot to finish the title of the thread...
Click to expand...
Click to collapse
It's safe, but it will be unsuccessful until you unroot your phone and undo any other system modifications that you've done (xposed, for example). There's a huge part of the update script that checks every single file in your system partition to make sure nothing has been modified.

Ok great, thanks.
The only other modification I can think that I've made is enabling mobile Hotspot through editing a setting somewhere. Do you know if that would be affected or would need changed back?

AirJordanTS said:
Ok great, thanks.
The only other modification I can think that I've made is enabling mobile Hotspot through editing a setting somewhere. Do you know if that would be affected or would need changed back?
Click to expand...
Click to collapse
You did that by modifying /system/build.prop. That change might be okay, but I would change it back if I were you just to be safe. The change is going to be overwritten anyway once the OTA is done.

AirJordanTS said:
Ok great, thanks.
The only other modification I can think that I've made is enabling mobile Hotspot through editing a setting somewhere. Do you know if that would be affected or would need changed back?
Click to expand...
Click to collapse
It's possible it may miss overlooking that. The worst that could happen was the update just doesn't take. It fails and nothing is changed. There is a pure MM official version that you can Flash in TWRP. It will update everything, radios and all, but will not relock the bootloader. I recommend you download Titanium Backup and backup all of your apps and their data to be restored after the update. A factory reset is recommended after the update. Also, don't forget to back up all of your photos, documents, music, etc. 24.81.5 is MM. Your update was a prep for MM.

Thanks for the advice guys.
I didn't realize it but I had TWRP installed so I decided to flash a stock ROM and proceed with the OTA updates from there. The problem currently is that I'm being locked out of my phone because of the Google "verify your account" page. I reset my account password on that page and now I'm not able to log in.

question about maintaining root

So far I've been running my OP3T with stock rom with TWRP recovery and SuperSU to have root. This was mostly because I wanted the Adaway and titanium backup to work. I undid everything so I could update to the latest OxygenOS version, and now I'm on the stock recovery too, but with bootloader still unlocked I believe. I no longer have root after doing the upgrade as far as I can tell, still a bit new to all this flashing, haha. The last time I did this was when the nexus 4 came out
What is the best option for maintaining root while still being able to upgrade smoothly? I'm not against using one of the custom ROMs if that will help, but I do kinda like the stock rom so far!
thanks!

bluesrph said:
So far I've been running my OP3T with stock rom with TWRP recovery and SuperSU to have root. This was mostly because I wanted the Adaway and titanium backup to work. I undid everything so I could update to the latest OxygenOS version, and now I'm on the stock recovery too, but with bootloader still unlocked I believe. I no longer have root after doing the upgrade as far as I can tell, still a bit new to all this flashing, haha. The last time I did this was when the nexus 4 came out
What is the best option for maintaining root while still being able to upgrade smoothly? I'm not against using one of the custom ROMs if that will help, but I do kinda like the stock rom so far!
thanks!
Click to expand...
Click to collapse
This thread should answer all your questions and doubts
https://forums.oneplus.net/threads/...-or-custom-recovery-without-data-loss.479265/

saurabh40629 said:
This thread should answer all your questions and doubts
https://forums.oneplus.net/threads/...-or-custom-recovery-without-data-loss.479265/
Click to expand...
Click to collapse
Thank you, I have seen that post. I'm guessing any route I go I'll have to flash updates then? I was hoping to find a way to be able to use OTA updates.
I've also never been able to get rid of the dm-verity error, even after going back to stock and locking the bootloader. Is there anything I need to worry about with that or is it just an annoyance?
Sent from my OnePlus3T using XDA Labs

bluesrph said:
Thank you, I have seen that post. I'm guessing any route I go I'll have to flash updates then? I was hoping to find a way to be able to use OTA updates.
I've also never been able to get rid of the dm-verity error, even after going back to stock and locking the bootloader. Is there anything I need to worry about with that or is it just an annoyance?
Click to expand...
Click to collapse
Dm-verity u can bypass but bootloader one, you can not. Look at the apps, mods section.

bluesrph said:
Thank you, I have seen that post. I'm guessing any route I go I'll have to flash updates then? I was hoping to find a way to be able to use OTA updates.
I've also never been able to get rid of the dm-verity error, even after going back to stock and locking the bootloader. Is there anything I need to worry about with that or is it just an annoyance?
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
You shouldn't try to flash the partial OTAs while you are rooted and have a custom recovery installed. The partial zip will try to make specific changes in the restricted partitions (/system, /boot, /recovery, etc.) related to the update and prior modifications to these files may cause the update to fail and the phone to brick. You can still use the "Update" tab in the Settings menu to download the update though as OOS will detect root and download the full zip of the update for you. Simply flash the full zip in TWRP, wipe cache/dalvik, then flash SuperSU and you're good to go the next time an update rolls out. Updating by this method (rooting immedately after flashing update) will also prevent OOS from replacing TWRP with the stock recovery again. When you download the update, you'll know if it's the full zip if the file is >1 GB (they're usually ~1.4 GB,, whereas the partial zips are a few hundred MB).
Unlocked bootloader warning screen is cannot be removed without relocked and fully resetting (wiping) the phone. DM-verity warning screen can be removed by following this guide. Make sure that you are flashing the correct firmware for you current version of OOS though, flashing the wrong version can brick you phone.