Hey all, I've managed to get my hands on the Lollipop 5.2.2 update 2 bin. I had received the update previously which broke my 5.2.2 root, so I figured I might be able to get it again. I downgraded to 4.5.3, rooted, updated to 4.5.5 (keeping root), then checked for updates. The file that downloaded had a different filename and filesize than the currently available 5.2.2 bin, so I thought I would chance updating it and seeing if I got a brick or not. I booted into TWRP, changed the file extension of the bin to zip, then flashed it with TWRP alongside the 5.2.0 bootloaders/recovery. As a result, I am now running rooted 5.2.2 update 2! My build date says Sept. 23rd and I have a neat new launcher. I hope this can help prevent some bricks and bring some life back into these forums. Thanks to all of the kind people who have spent their time making such helpful guides and tutorials!
Link:
https://mega.nz/#!ZI1wTL6L!xbDNDvaJjLUWwqe8J9awAs4xNQvxreXCmZ1I6cWTLVA
Great news! Thanks for taking the plunge!
I successfully installed it on tablet running rooted July 23 developers preview. Nice . . .
I've downloaded your capture and am rooted on 4.5.5 but am pretty nervous to try to upgrade... Is your tablet still running fine with rooted lollipop? Also did you disable any amazon auto updater after you upgraded? Thanks for posting your capture!
increzible said:
I've downloaded your capture and am rooted on 4.5.5 but am pretty nervous to try to upgrade... Is your tablet still running fine with rooted lollipop? Also did you disable any amazon auto updater after you upgraded? Thanks for posting your capture!
Click to expand...
Click to collapse
Yup, still running great. After I upgraded I pm disabled com.amazon.otaverifier and com.amazon.device.software.ota as I didnt want any more surprise updates breaking my root. With these two disabled, a check for updates should fail completely. I think you should be fine for the update, just remember to flash the 5.2.0 bootloader/recovery along with it and swipe to root when you are asked.
OK do I need to flash any different GAPPs while I'm in twrp or will the ones installed in 4.5.x work? I'll be trying this later tonight and will report my results.
increzible said:
OK do I need to flash any different GAPPs while I'm in twrp or will the ones installed in 4.5.x work? I'll be trying this later tonight and will report my results.
Click to expand...
Click to collapse
I guess I'm not 100% sure on the GAPPS bit. I've just been using this little program:
http://forum.xda-developers.com/amazon-fire/general/installing-google-framework-playstore-t3216122
It installs all of the GAPPS with or without root in just a few clicks. The only difference between this and flashing I suppose would be that these are installed as user applications, not system applications. It all works the same though. Also, I'm not sure exactly which apps cross over if any in the upgrade. I did a clean wipe before flashing.
Hariiiii said:
I guess I'm not 100% sure on the GAPPS bit. I've just been using this little program:
http://forum.xda-developers.com/amazon-fire/general/installing-google-framework-playstore-t3216122
It installs all of the GAPPS with or without root in just a few clicks. The only difference between this and flashing I suppose would be that these are installed as user applications, not system applications. It all works the same though. Also, I'm not sure exactly which apps cross over if any in the upgrade. I did a clean wipe before flashing.
Click to expand...
Click to collapse
Ok so I decided to go ahead and update and just see what happened out of a nervous excitement. Updating with the zips went fine in TWRP and I swiped to keep root. Then I rebooted the device and waited while the device installed the system for “approximately 10 minutes” or an eternity in my experience. I had to reinstall supersu through the apk and update the binary when everything had booted up. Rebooted after binary update as per supersu direction and successfully pm disabled the above mentioned updaters. I then had to uninstall play services, play store etc via titanium in order to get the play store working using the method mentioned in Hariiiii’s above link. After uninstalling through titanium I rebooted and then ran the bat script afterwards. Rebooted again and logged into the play store and done. Everything seems to be working now. Thanks so much for this Hariiiii!
Glad it worked out well and that I could be of help!!
Hariiiii said:
Hey all, I've managed to get my hands on the Lollipop 5.2.2 update 2 bin ...
Click to expand...
Click to collapse
Awesome effort with this 5.2.2u2 !!! I suspect that perhaps flashing of 5.2.0 bootloaders could have been skipped, but for the sake of non-bricking safety it's a good move!!!
So far the record is this (in terms of bootloaders):
4.5.3 works fine after 5.2.2u2, 4.5.5 bricks after 5.2.2u2 (one report)
5.2.0 works fine after 5.2.2u2, 5.2.2 bricks after 5.2.2u2 (many reports)
Overall, the fix seems simple, so this is definitely good news!
bibikalka said:
So far the record is this (in terms of bootloaders):
4.5.3 works fine after 5.2.2u2, 4.5.5 bricks after 5.2.2u2 (one report)
5.2.0 works fine after 5.2.2u2, 5.2.2 bricks after 5.2.2u2 (many reports)
Click to expand...
Click to collapse
Ok, some confusion here. If you think 5.2.2u2 is the same as (or anyway has same bootloaders as) the September developer preview that resulted in bricks, then wasn't hariiiii's upgrade successful because he did flash the 5.2.0 bootloaders?
DoLooper said:
Ok, some confusion here. If you think 5.2.2u2 is the same as (or anyway has same bootloaders as) the September developer preview that resulted in bricks, then wasn't hariiiii's upgrade successful because he did flash the 5.2.0 bootloaders?
Click to expand...
Click to collapse
To be honest I'm pretty confused myself about exactly what is happening here. Let me throw you for a loop: when I first flashed 5.2.2u2 from 4.5.5, I didn't flash bootloaders OR RECOVERY and it booted fine. The bootloaders would take me to the OS but wouldn't boot TWRP so I had no recovery. I used the method to temporarily access TWRP by dd-ING 4.5.3 boot, tee1, and twrp, then did a clean wipe and flashed 5.2.0 recovery/boot first followed by the 5.2.2u2 bin.
Hariiiii said:
. . . when I first flashed 5.2.2u2 from 4.5.5, I didn't flash bootloaders OR RECOVERY and it booted fine.
Click to expand...
Click to collapse
Hmm. Davigar posted similar in my upgrade from dev preview guide (so I assume he's talking about 5.2.2u2). Sorry if this is a red herring, but it seems the different results might matter. Perhaps @bibikalka will weigh in.
davigar said:
Finally i follow the turorial and i forgive[forget] flash 5.2.0 recovery and gapps and it works then i flash twrp again by adb and i did wipes and flash update, gapps, xposed and 5.2.0 recovery[5.2.0_stock_recovery_uboot] and i hard bricked my fire. Why?
Click to expand...
Click to collapse
Hariiiii said:
The bootloaders would take me to the OS but wouldn't boot TWRP so I had no recovery. I used the method to temporarily access TWRP by dd-ING 4.5.3 boot, tee1, and twrp, then did a clean wipe and flashed 5.2.0 recovery/boot first followed by the 5.2.2u2 bin.
Click to expand...
Click to collapse
I'm not TWRP-smart (nor bootloader smart), but assume the order in which things are flashed matters. Because you flashed 5.2.0 bootloaders/recovery first, wouldn't the 5.2.2u2 bootloaders have overwritten the 5.2.0--so you're running 5.2.2u2 bootloaders?
DoLooper said:
Ok, some confusion here. If you think 5.2.2u2 is the same as (or anyway has same bootloaders as) the September developer preview that resulted in bricks, then wasn't hariiiii's upgrade successful because he did flash the 5.2.0 bootloaders?
Click to expand...
Click to collapse
Hariiiii said:
To be honest I'm pretty confused myself about exactly what is happening here. Let me throw you for a loop: when I first flashed 5.2.2u2 from 4.5.5, I didn't flash bootloaders OR RECOVERY and it booted fine. The bootloaders would take me to the OS but wouldn't boot TWRP so I had no recovery. I used the method to temporarily access TWRP by dd-ING 4.5.3 boot, tee1, and twrp, then did a clean wipe and flashed 5.2.0 recovery/boot first followed by the 5.2.2u2 bin.
Click to expand...
Click to collapse
DoLooper said:
Hmm. Davigar posted similar in my upgrade from dev preview guide (so I assume he's talking about 5.2.2u2). Sorry if this is a red herring, but it seems the different results might matter. Perhaps @bibikalka will weigh in.
I'm not TWRP-smart (nor bootloader smart), but assume the order in which things are flashed matters. Because you flashed 5.2.0 bootloaders/recovery first, wouldn't the 5.2.2u2 bootloaders have overwritten the 5.2.0--so you're running 5.2.2u2 bootloaders?
Click to expand...
Click to collapse
So it looks like the original poster was booting either 5.2.2u2 bootloaders or 4.5.3 bootloaders (when downgrading or getting temporary TWRP). Flashing 5.2.0 bootloaders before 5.2.2u2 zip only replaces recovery, since then the 5.2.0 bootloaders get flashed to 5.2.2u2 during the 5.2.2u2 zip update process. So effectively 5.2.0 bootloaders are not needed. However, it seems that 5.2.0 will boot after 5.2.2u2 since a few people have followed the mis-guided guide , and that worked fine!
Thus, if one gets 5.2.2u2, then only 4.5.3 bootloader works out of the 4.5.x series, or 5.2.0 and 5.2.2u2 but not 5.2.2(u1) which caused most bricks!
bibikalka said:
So it looks like the original poster was booting either 5.2.2u2 bootloaders or 4.5.3 bootloaders (when downgrading or getting temporary TWRP). Flashing 5.2.0 bootloaders before 5.2.2u2 zip only replaces recovery, since then the 5.2.0 bootloaders get flashed to 5.2.2u2 during the 5.2.2u2 zip update process. So effectively 5.2.0 bootloaders are not needed. However, it seems that 5.2.0 will boot after 5.2.2u2 since a few people have followed the mis-guided guide , and that worked fine!
Thus, if one gets 5.2.2u2, then only 4.5.3 bootloader works out of the 4.5.x series, or 5.2.0 and 5.2.2u2 but not 5.2.2(u1) which caused most bricks!
Click to expand...
Click to collapse
Hmmm but after downgrading to 4.5.3, I upgraded to 4.5.5 before 5.2.2u2. So after having 5.2.2u2, I successfully was able to use 4.5.3, 4.5.5, and of course 5.2.2u2. I'm really quite curious to figure out what exactly is driving these bricks. Is there any information I can grab from my tablet that might help to clarify? e.g. partition sizes, any system data
It's currently my suspicion that 5.2.0 bootloaders might not successfully boot 5.2.2.u2....given that I overwrote my 5.2.0 bootloaders with 5.2.2u2 ones by flashing the update second and it worked for me, meanwhile this other fellow from dolooper's guide thread flashed the 5.2.0 bootloaders after the update and got bricked.
bibikalka said:
So it looks like the original poster was booting either 5.2.2u2 bootloaders or 4.5.3 bootloaders (when downgrading or getting temporary TWRP). Flashing 5.2.0 bootloaders before 5.2.2u2 zip only replaces recovery, since then the 5.2.0 bootloaders get flashed to 5.2.2u2 during the 5.2.2u2 zip update process. So effectively 5.2.0 bootloaders are not needed. However, it seems that 5.2.0 will boot after 5.2.2u2 since a few people have followed the mis-guided guide , and that worked fine!
Thus, if one gets 5.2.2u2, then only 4.5.3 bootloader works out of the 4.5.x series, or 5.2.0 and 5.2.2u2 but not 5.2.2(u1) which caused most bricks!
Click to expand...
Click to collapse
Thanks for info. So more questions:
Why were hariiiii and davagar both able to boot after flashing an update in TWRP, but not overwriting TWRP with 5.2.0_stock_recovery_only? Does this mean that 5.2.2(u1) and (u2) can boot unsigned TWRP? [EDIT: Oh, wait. Maybe the issue wasn't that you couldn't boot to OS, but couldn't get into recovery with unsigned TWRP. That would make sense.]
When you say at end, "but not 5.2.2(u1)," you mean neither 4.5.3 nor 5.2.0 bootloaders work with that update? So people were getting bricked because they were running 4.5.3 bootloaders in TWRP and when 5.2.2(u1) bootloaders tried to kick in after the update was flashed they couldn't (kick in)?
But from what davigar has said, he was in same situation--running 4.5.3 bootloaders in TWRP when he updated to 5.2.2(u1). But we know he was able to boot afterward. The only difference seems to be he hadn't installed stock recovery.
Obviously I'll take out the bit about flashing 5.2.0_stock_recovery_uboot.zip in the update from dev preview guide. But now I'm unclear whether we need to flash 5.2.0_stock_recovery_only or not. [EDIT: NVM. Of course we do Thanks!]
---------- Post added at 08:44 PM ---------- Previous post was at 08:25 PM ----------
Hariiiii said:
It's currently my suspicion that 5.2.0 bootloaders might not successfully boot 5.2.2.u2....given that I overwrote my 5.2.0 bootloaders with 5.2.2u2 ones by flashing the update second and it worked for me, meanwhile this other fellow from dolooper's guide thread flashed the 5.2.0 bootloaders after the update and got bricked.
Click to expand...
Click to collapse
FWIW, we know 5.2.0 bootloaders do boot 5.2.2.u2. I'm using 'em. Davigar got bricked because of the 5.2.2u1/5.2.0 bootloader conflict, although I don't understand why he didn't get clobbered at the time he installed 5.2.2u1 while running 4.5.3 bootloaders like everyone else. Seems it must be related to not installing recovery. Hope bibikalka can enlighten us.
Hariiiii said:
Hmmm but after downgrading to 4.5.3, I upgraded to 4.5.5 before 5.2.2u2. So after having 5.2.2u2, I successfully was able to use 4.5.3, 4.5.5, and of course 5.2.2u2. I'm really quite curious to figure out what exactly is driving these bricks. Is there any information I can grab from my tablet that might help to clarify? e.g. partition sizes, any system data
Click to expand...
Click to collapse
Note that when you say you had "4.5.5" (I assume rooted?), you actually had 4.5.3 bootloaders with TWRP!!! The actual 4.5.5 bootloaders also brick. You are lucky that your 5.2.0 bootloaders got replaced by 5.2.2u2 (as you flashed the latest zip file), or you'd have a brick on your hands.
DoLooper said:
Thanks for info.
FWIW, we know 5.2.0 bootloaders do boot 5.2.2.u2. I'm using 'em. Davigar got bricked because of the 5.2.2u1/5.2.0 bootloader conflict, although I don't understand why he didn't get clobbered at the time he installed 5.2.2u1 while running 4.5.3 bootloaders like everyone else. Seems it must be related to not installing recovery. Hope bibikalka can enlighten us.
Click to expand...
Click to collapse
My current working theory is that once 5.2.2u2 bootloaders BOOTED at least once, there is no going back to anything prior to that (other than 4.5.3) 5.2.0 bootloaders work OK only for people who never booted 5.2.2u2 bootloaders before. Davigar first was booting 5.2.2u2 bootloaders, and then decided to "fix" things and flashed 5.2.0 bootloaders. At this point the Fire bricked.
bibikalka said:
Note that when you say you had "4.5.5" (I assume rooted?), you actually had 4.5.3 bootloaders with TWRP!!! The actual 4.5.5 bootloaders also brick. You are lucky that your 5.2.0 bootloaders got replaced by 5.2.2u2 (as you flashed the latest zip file), or you'd have a brick on your hands.
My current working theory is that once 5.2.2u2 bootloaders BOOTED at least once, there is no going back to anything prior to that (other than 4.5.3) 5.2.0 bootloaders work OK only for people who never booted 5.2.2u2 bootloaders before. Davigar first was booting 5.2.2u2 bootloaders, and then decided to "fix" things and flashed 5.2.0 bootloaders. At this point the Fire bricked.
Click to expand...
Click to collapse
Excellent theory! I think that actually explains all of the different results we've been trying to bring together. One thing though: I updated from 4.5.3 to 4.5.5 using the OTA download (and just changing the filename and flashing while it was still sitting in /cache). There was actually a point in time where I was using 4.5.5 as my OS in its entirety (It was through checking for updates within 4.5.5 that I was able to get the OTA download for 5.2.2u2). Shouldn't this mean that I would've had 4.5.5 bootloaders? (unless they are the same bootloaders as the 4.5.3 ones).
Hariiiii said:
link (remove the space in https):
http s://mega.nz/#!ZI1wTL6L!xbDNDvaJjLUWwqe8J9awAs4xNQvxreXCmZ1I6cWTLVA
Click to expand...
Click to collapse
So now that you've earned your cred could you please attach this link to the OP--so I my new rooters can more easily grab your yummy update? Thanks!
Hariiiii said:
Hey all, I've managed to get my hands on the Lollipop 5.2.2 update 2 bin. I had received the update previously which broke my 5.2.2 root, so I figured I might be able to get it again. I downgraded to 4.5.3, rooted, updated to 4.5.5 (keeping root), then checked for updates. The file that downloaded had a different filename and filesize than the currently available 5.2.2 bin, so I thought I would chance updating it and seeing if I got a brick or not. I booted into TWRP, changed the file extension of the bin to zip, then flashed it with TWRP alongside the 5.2.0 bootloaders/recovery. As a result, I am now running rooted 5.2.2 update 2! My build date says Sept. 23rd and I have a neat new launcher. I hope this can help prevent some bricks and bring some life back into these forums. Thanks to all of the kind people who have spent their time making such helpful guides and tutorials!
Link:
https://mega.nz/#!ZI1wTL6L!xbDNDvaJjLUWwqe8J9awAs4xNQvxreXCmZ1I6cWTLVA
Click to expand...
Click to collapse
Awesome, thanks a lot of grabbing this and making it available. I was able to use this to update from 4.5.2, and keep root/TWRP, and get playstore access, so I'm really happy! Question, though - my build date shows Sept 23, 2015, but OS version shows 5.0.1, not 5.2.2. Is that right?
Rasilon said:
Question, though - my build date shows Sept 23, 2015, but OS version shows 5.0.1, not 5.2.2. Is that right?
Click to expand...
Click to collapse
I confirm, mine also reports 5.0.1. And in quick settings there is not Blue Shade toggle
Related
OK, the question came up a couple of times, so let's have a guide out there.
Some people want 100% unrooted stock back, and not a trace of any rooting or TWRP. So here you are.
1) Boot into TWRP, do factory reset, and flash "5.2.0_stock_recovery_only.zip" from here :
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
2) Reboot into recovery, and sideload whatever stock you want (say, 4.5.3) as in here :
http://forum.xda-developers.com/fire-hd/general/how-to-downgrade-to-4-5-3-root-device-t3139351
3) don't ROOT 4.5.3
4) full stock !!!
bibikalka said:
OK, the question came up a couple of times, so let's have a guide out there.
Some people want 100% unrooted stock back, and not a trace of any rooting or TWRP. So here you are.
1) Boot into TWRP, do factory reset, and flash "5.2.0_stock_recovery_only.zip" from here :
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
2) Reboot into recovery, and sideload whatever stock you want (say, 4.5.3) as in here :
http://forum.xda-developers.com/fire-hd/general/how-to-downgrade-to-4-5-3-root-device-t3139351
3) don't ROOT 4.5.3
4) full stock !!!
Click to expand...
Click to collapse
Hopefully someone can help. I followed the instructions and my Kindle Fire HD 7 4th gen was back at 4.5.3. I allowed the device to OTA update to 4.5.5 and it restarted to complete the update and now it won't turn on at all. No Amazon logo, no signs of life. Any help?
arrfenwoof said:
Hopefully someone can help. I followed the instructions and my Kindle Fire HD 7 4th gen was back at 4.5.3. I allowed the device to OTA update to 4.5.5 and it restarted to complete the update and now it won't turn on at all. No Amazon logo, no signs of life. Any help?
Click to expand...
Click to collapse
Happened to me too, just returned it and got a refurbished one back.
If you use this, DO NOT OTA UPDATE. If you want to update to 4.5.5, I think you can get the 4.5.5 update bin, rename bin to zip, and flash in TWRP. (Or just flash 4.5.5)
Gimzie said:
Happened to me too, just returned it and got a refurbished one back.
If you use this, DO NOT OTA UPDATE. If you want to update to 4.5.5, I think you can get the 4.5.5 update bin, rename bin to zip, and flash in TWRP. (Or just flash 4.5.5)
Click to expand...
Click to collapse
I think if one had the latest Lollipop, it'll brick with any older bootloaders other than 4.5.3 This happened to a few other people around Oct/Nov.
Note if one is going for full stock without root, then after re-installing 4.5.3 the updates need to be blocked via adb.
bibikalka said:
I think if one had the latest Lollipop, it'll brick with any older bootloaders other than 4.5.3 This happened to a few other people around Oct/Nov.
Note if one is going for full stock without root, then after re-installing 4.5.3 the updates need to be blocked via adb.
Click to expand...
Click to collapse
I've had luck updating to official Fire OS 5 with ota, then downgrade to 4.5.3 with sideload, and then 5.0 ota again. Is this just because it's the official preview?
Gimzie said:
I've had luck updating to official Fire OS 5 with ota, then downgrade to 4.5.3 with sideload, and then 5.0 ota again. Is this just because it's the official preview?
Click to expand...
Click to collapse
bibikalka said:
I think if one had the latest Lollipop, it'll brick with any older bootloaders other than 4.5.3 This happened to a few other people around Oct/Nov.
Note if one is going for full stock without root, then after re-installing 4.5.3 the updates need to be blocked via adb.
Click to expand...
Click to collapse
Ok, just to add to this: Would it be possible to flash back to 4.5.3 (With Fire OS 5 developer preview enabled), then update to 5.0 with OTA, and request a downgrade through Amazon officially? (Or would the OTA not work)
Gimzie said:
I've had luck updating to official Fire OS 5 with ota, then downgrade to 4.5.3 with sideload, and then 5.0 ota again. Is this just because it's the official preview?
Click to expand...
Click to collapse
Gimzie said:
Ok, just to add to this: Would it be possible to flash back to 4.5.3 (With Fire OS 5 developer preview enabled), then update to 5.0 with OTA, and request a downgrade through Amazon officially? (Or would the OTA not work)
Click to expand...
Click to collapse
Why do all this ?
Any 5 version will let you downgrade to 4.5.3. The earlier developer preview then allowed any other bootloaders to run (4.5.4, 4.5.5, 5.0 preview, so upgrades were safe). But the latest 5.2.2u2 can only be downgraded to 4.5.3 and upgraded back to itself (with root), and will brick with any other bootloaders, see this :
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
bibikalka said:
Why do all this ?
Any 5 version will let you downgrade to 4.5.3. The earlier developer preview then allowed any other bootloaders to run (4.5.4, 4.5.5, 5.0 preview, so upgrades were safe). But the latest 5.2.2u2 can only be downgraded to 4.5.3 and upgraded back to itself (with root), and will brick with any other bootloaders, see this :
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
Click to expand...
Click to collapse
I followed that guide and already have rooted Fire OS 5.
So I guess to get to as stock as possible, I should simply flash 4.5.3, then block updates with ADB.
Gimzie said:
I followed that guide and already have rooted Fire OS 5.
So I guess to get to as stock as possible, I should simply flash 4.5.3, then block updates with ADB.
Click to expand...
Click to collapse
Well, the best stock is the one with ROOT When the device is rooted, it's literally a few simple modifications to the /system, so there is no need to fetishize ROOT-less stock.
But note that updates overwrite everything. So chaining versions makes no sense, and one should take the shortest route from where they are, to where they want to be while avoiding the bricking hazards.
bibikalka said:
Well, the best stock is the one with ROOT When the device is rooted, it's literally a few simple modifications to the /system, so there is no need to fetishize ROOT-less stock.
But note that updates overwrite everything. So chaining versions makes no sense, and one should take the shortest route from where they are, to where they want to be while avoiding the bricking hazards.
Click to expand...
Click to collapse
Well, I'm now running Fire OS 4.5.3, with root and TWRP installed. Blocked updates, and registered. Works like a charm. I find Fire OS 4 to be faster then Fire OS 5, although the sound quality went down for some reason.
@DoLooper recommended me to here, are any of these steps safe for me to use? I've never used Lolipop, only the rooted 4.5.4 with a different launcher from a the original root instructions you two came up with. I'd love to be on the latest non rooted firmware if possible.
My thread which has a bit of information. http://forum.xda-developers.com/fire-hd/help/factory-reset-rooted-fire-hd-t3338487
Shadowshinra said:
@DoLooper recommended me to here, are any of these steps safe for me to use? I've never used Lolipop, only the rooted 4.5.4 with a different launcher from a the original root instructions you two came up with. I'd love to be on the latest non rooted firmware if possible.
My thread which has a bit of information. http://forum.xda-developers.com/fire-hd/help/factory-reset-rooted-fire-hd-t3338487
Click to expand...
Click to collapse
Yes, if you have TWRP, I recommend that you follow this post :
http://forum.xda-developers.com/fire-hd/general/upgrade-to-4-5-5-root-t3174449
Basically, I recommend that you install stock 4.5.5.1 and flash bootloaders to 4.5.3 ( +TWRP), perhaps also make_space*zip. This would be step 2 (a), (b), and (c). Then reboot. So you'll have stock OS (with OTA blocked), but will have an option to boot into TWRP, and update at any later date you want.
It work with cm 11 rom
i restore fw 4.5.3 my device working but after i update ota firmware 4.5.5 my fire return hard brick Pls hep me
Not to practice necromancy on this thread but I'll admit I am a bit confused. I thought this guide restored your Fire back to stock, and by stock I mean just like you pulled it out of the box new, like complete factory defaults stock. I see mention of disabling OTA updates which on a stock Fire you can still do without issues. So my question is if there is a way to really REALLY restore a Fire that had TWRP / Rooted back to being completely stock?
So this may be a stupid question, but this is my first Nexus device. I will have a 6P delivered Thursday and plan to unlock, decrypt, and install TWRP. The guides so far reference using MDB08K, and the modified boot is only for this version currently. After I install TWRP, am I able to install the factory image for the latest MDB08M and just exclude flashing certain images? Or do I need to flash them all then wait for a new modified boot image for 08M and install TWRP over again?
geoff5093 said:
So this may be a stupid question, but this is my first Nexus device. I will have a 6P delivered Thursday and plan to unlock, decrypt, and install TWRP. The guides so far reference using MDB08K, and the modified boot is only for this version currently. After I install TWRP, am I able to install the factory image for the latest MDB08M and just exclude flashing certain images? Or do I need to flash them all then wait for a new modified boot image for 08M and install TWRP over again?
Click to expand...
Click to collapse
When I got mine the first thing I did was the OTA update and then I performed the root etc prcess
MrDSL said:
When I got mine the first thing I did was the OTA update and then I performed the root etc prcess
Click to expand...
Click to collapse
Its good to do this right away because when you unlock the bootloader, it wipes the phone. I haven't done this on mine yet because I'm curious about Android Pay and what impact that will have on it.
bitpushr said:
Its good to do this right away because when you unlock the bootloader, it wipes the phone. I haven't done this on mine yet because I'm curious about Android Pay and what impact that will have on it.
Click to expand...
Click to collapse
OH OH!!!! We have to behave, we have an Administrator with the same phone UGH!! Just kidding Hello @bitpushr
Somewheres around here someone is reporting pay working with unlock and root. If I recall correctly he removed root in su settings to add the card and then set back to root and it was working. Highly concerned individuals might want to verify that from multiple sources...
MrDSL said:
When I got mine the first thing I did was the OTA update and then I performed the root etc prcess
Click to expand...
Click to collapse
But don't you need to use the corresponding modified boot image to root it? There currently isn't one for the latest factory image I believe.
geoff5093 said:
But don't you need to use the corresponding modified boot image to root it? There currently isn't one for the latest factory image I believe.
Click to expand...
Click to collapse
Chainfire has one and I believe there is one in the development forum.
MrDSL said:
Chainfire has one and I believe there is one in the development forum.
Click to expand...
Click to collapse
I was looking at his thread, but I only see one for the 08K image.
http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
The one in the dev section also appears to only be for 08K: http://forum.xda-developers.com/nexus-6p/development/kernel-stock-decrypted-kernel-verity-t3235013
I just wanted to confirm that these need to be the same, so I'll wait for an update.
I thought Build MBD08K was the latest..
I know that I'm currently running cleanrom MBD08K with modified MBD08K boot.img
Modified MBD08K boot.img from chainfire works fine with newest MDB08M. On my phone I unlocked bootloader, flashed all the MDB08M files, than flashed the modified boot.img.
I have working root, decrypted with TWRP installed.
mysongranhills said:
Modified MBD08K boot.img from chainfire works fine with newest MDB08M. On my phone I unlocked bootloader, flashed all the MDB08M files, than flashed the modified boot.img.
I have working root, decrypted with TWRP installed.
Click to expand...
Click to collapse
Awesome!! ????
mysongranhills said:
Modified MBD08K boot.img from chainfire works fine with newest MDB08M. On my phone I unlocked bootloader, flashed all the MDB08M files, than flashed the modified boot.img.
I have working root, decrypted with TWRP installed.
Click to expand...
Click to collapse
I assume if we have MDB08K, rooted with TWRP and want to take the OTA to MDB08M, that we can use a similar procedure:
1. Flash stock boot.img and recovery.img from MDB08K factory image (temporarily disabling root and TWRP)
2. Download and install OTA
3. Reflash modified MDB08K boot.img from Chainfire
4. Reflash TWRP recovery
5. Install SuperSU 2.52 using TWRP
Has anyone tried this method?
rsmolen said:
I assume if we have MDB08K, rooted with TWRP and want to take the OTA to MDB08M, that we can use a similar procedure:
1. Flash stock boot.img and recovery.img from MDB08K factory image (temporarily disabling root and TWRP)
2. Download and install OTA
3. Reflash modified MDB08K boot.img from Chainfire
4. Reflash TWRP recovery
5. Install SuperSU 2.52 using TWRP
Has anyone tried this method?
Click to expand...
Click to collapse
No, but your logic is sound. I see no problems doing it that way. Why would you prefer the OTA updates over the latest factory images? I know for me part of the reason I did it the way I did was b/c I couldn't get phone to download/recognize that OTA update existed.
In case anyone else is still wondering, flashing the 08M factory image and then using the 08K modified boot works fine. I'm on the latest and rooted right now.
mysongranhills said:
No, but your logic is sound. I see no problems doing it that way. Why would you prefer the OTA updates over the latest factory images? I know for me part of the reason I did it the way I did was b/c I couldn't get phone to download/recognize that OTA update existed.
Click to expand...
Click to collapse
I just thought this would be slightly easier than flashing the system.img from the factory image. However, given the modified boot.img and systemless SuperSU, I guess only flashing the system.img (and radio.img if changed) from the new build would probably be easier at this point. However, if xPosed comes to Marshmallow and modifies system, that will be another step in the upgrade process, which presumably would not need to be done if you could take the OTA the way I proposed.
Hello,
after I've unlocked the bootloader can I still get OTA updates?
I'll just be on stock ROM with root. I also make a backup with nothing on except TWRP.
Lets hope so
LanceM said:
Lets hope so
Click to expand...
Click to collapse
have you tried it?
Yes you'll be able to get new updates with unlock bootloader.
DrakenFX said:
Yes you'll be able to get new updates with unlock bootloader.
Click to expand...
Click to collapse
Can you elaborate on this? The last I heard unlocking the bootloader (using the official procedure) stops OTA. Has this changed ?
mh127 said:
Can you elaborate on this? The last I heard unlocking the bootloader (using the official procedure) stops OTA. Has this changed ?
Click to expand...
Click to collapse
I never said Official getting OTA's , but i believe this is going to change staring with the new Unlock Bootloader procedure.
DrakenFX said:
I never said Official getting OTA's , but i believe this is going to change staring with the new Unlock Bootloader procedure.
Click to expand...
Click to collapse
OK, but AFAIK even with the unofficial unlock (with TWRP and root) the OTA will fail - unless you unroot and go back to locked stock bootloader. Correct me if I am wrong.
mh127 said:
OK, but AFAIK even with the unofficial unlock (with TWRP and root) the OTA will fail - unless you unroot and go back to locked stock bootloader. Correct me if I am wrong.
Click to expand...
Click to collapse
In my experience, what makes the difference - so far - is the recovery. Official ZTE updates and ROMS only flash through the stock recovery.
Unlocked bootloader has made no difference to me.
mh127 said:
OK, but AFAIK even with the unofficial unlock (with TWRP and root) the OTA will fail - unless you unroot and go back to locked stock bootloader. Correct me if I am wrong.
Click to expand...
Click to collapse
If you try to flash Official OTA yes will fail, cuz isn't modded to skip partitions check.
DrakenFX said:
If you try to flash Official OTA yes will fail, cuz isn't modded to skip partitions check.
Click to expand...
Click to collapse
This is getting confusing. "Getting OTA updates" (as OP asks) usually means that the update installs "on its own" by tapping notification rather than flashing via recovery, which is a bit more complicated process.
So back to the OP question: With root and TWRP can one get over-the-air official updates from ZTE without going to the recovery manually? I believe the answer to that is NO.
That said, there is probably a work around in getting the update, probably by manually flashing partitions that have changed in the update.
Is this right?
mh127 said:
This is getting confusing. "Getting OTA updates" (as OP asks) usually means that the update installs "on its own" by tapping notification rather than flashing via recovery, which is a bit more complicated process.
So back to the OP question: With root and TWRP can one get over-the-air official updates from ZTE without going to the recovery manually? I believe the answer to that is NO.
That said, there is probably a work around in getting the update, probably by manually flashing partitions that have changed in the update.
Is this right?
Click to expand...
Click to collapse
Well OPs Question actually was if OTA Updates are possible with unlocked boot-loader...
Root and TWRP is a whole different scenario and won't work with OTA for sure as OTA needs stock recovery and will check for unmodified system (not rooted)...
But if you are on stock with unlocked bootloader you should get notified about OTAs (as until now it did not check for bootloader lock status, but that could change in future) although I don't know if it will install correctly
Gachmuret said:
Well OPs Question actually was if OTA Updates are possible with unlocked boot-loader...
Root and TWRP is a whole different scenario and won't work with OTA for sure as OTA needs stock recovery and will check for unmodified system (not rooted)...
But if you are on stock with unlocked bootloader you should get notified about OTAs (as until now it did not check for bootloader lock status, but that could change in future) although I don't know if it will install correctly
Click to expand...
Click to collapse
OP mentioned that he used TWRP to make a backup, I assumed he has replaced stock recovery with TWRP, but that may not necessarily be the case.
If your device has an bootloader that was unlocked "unofficially" (either via sideloading the official unlock method or DrakenFX & Unjustifieddev's method), but is still completely stock (stock System, stock Boot, stock Recovery, stock everything besides the unlocked bootloader), you can still receive and apply OTAs. However, if you changed any of the partitions, like boot.img (root), recovery.img (TWRP), system.img (changes to system), you will still receive the OTA, but you won't be able to apply it, the update will fail. If you went through the official bootloader unlocking process, which involved you submitting a form to ZTE with your device's IMEI, you would no longer be able to receive OTAs.
What I did was sideload the official B20_Boot on by B20 device, unlocked my bootloader, flashed TWRP, flashed the TWRP Stock B20 dumps that were posted here on XDA, and reflashed stock recovery. This made my device completely stock B20 besides the unlocked bootloader. I then applied the official B27 OTA update, and it installed fine. I then reflashed TWRP (since my bootloader was still unlocked) and re-rooted my device.
If a new update comes out, I can just reflash the stock B27 TWRP dump posted here on XDA, reflash stock recovery, (if needed, reflash stock fastboot), and apply OTA.
xtermmin said:
...
What I did was sideload the official B20_Boot on by B20 device, unlocked my bootloader, flashed TWRP, flashed the TWRP Stock B20 dumps that were posted here on XDA, and reflashed stock recovery. This made my device completely stock B20 besides the unlocked bootloader. I then applied the official B27 OTA update, and it installed fine. I then reflashed TWRP (since my bootloader was still unlocked) and re-rooted my device.
If a new update comes out, I can just reflash the stock B27 TWRP dump posted here on XDA, reflash stock recovery, (if needed, reflash stock fastboot), and apply OTA.
Click to expand...
Click to collapse
So, with this procedure, do you lose all the app installations/other customizations? I believe that all of the application data is on a non-system partition (/data?) but did you need to go through all of the setting up of the phone after you did the upgrade this way?
rayman2k1 said:
So, with this procedure, do you lose all the app installations/other customizations? I believe that all of the application data is on a non-system partition (/data?) but did you need to go through all of the setting up of the phone after you did the upgrade this way?
Click to expand...
Click to collapse
Yes. Unlocking the bootloader does a factory reset, and doing a TWRP restore of a stock image (which overwrites your current partitions) overwrites what you had before.
EDIT: Actually, I think Internal Storage gets erased as well, but your microSD card will be fine.
xtermmin said:
Yes. Unlocking the bootloader does a factory reset, and doing a TWRP restore of a stock image (which overwrites your current partitions) overwrites what you had before.
EDIT: Actually, I think Internal Storage gets erased as well, but your microSD card will be fine.
Click to expand...
Click to collapse
Hmm, had guessed as much. I knew the bootloader unlocking did a wipe, but was hoping that recovery-flashing would do a backup/restore, as if the update had been applied through the in-ROM update procedure. Unless the OTA process only gets deltas and flashes them, leaving fs intact.
rayman2k1 said:
Hmm, had guessed as much. I knew the bootloader unlocking did a wipe, but was hoping that recovery-flashing would do a backup/restore, as if the update had been applied through the in-ROM update procedure. Unless the OTA process only gets deltas and flashes them, leaving fs intact.
Click to expand...
Click to collapse
Yeah, the OTA doesn't straight-up replace partitions, it checks and patches the existing partitions, so if a partition has been changed, the OTA install will fail.
I can confirm that as of this morning I have been running official 6.0.1 and my bootloader is still unlocked!
thewire1o1 said:
I can confirm that as of this morning I gave been running official 6.0.1
Click to expand...
Click to collapse
Are you part of the soak test?
TheSt33v said:
Are you part of the soak test?
Click to expand...
Click to collapse
I can not confirm or deny that!
thewire1o1 said:
I can not confirm or deny that!
Click to expand...
Click to collapse
Haha well you already violated your NDA with this post, so there's no need for that anymore.
Factory reset and download all of the system imgs so we can all upgrade.
Crowick said:
Factory reset and download all of the system imgs so we can all upgrade.
Click to expand...
Click to collapse
I would second that:good:
Crowick said:
Factory reset and download all of the system imgs so we can all upgrade.
Click to expand...
Click to collapse
VincentCode88 said:
I would second that:good:
Click to expand...
Click to collapse
Already done, as of 1pm Sunday 12/4/12016. Also there's a TWRP flashable version, and now even TWRP flashable ebloated ROM based on the OTA:
[OTA] Official Marshmallow build MCG24.251-5
http://forum.xda-developers.com/dro...ota-official-marshmallow-build-mcg24-t3512813
[ROM] MCG24.251-5 100% Stock (TWRP flashable)
http://forum.xda-developers.com/droid-turbo/development/rom-mcg24-251-5-100-stock-t3512949
debloated Verizon 6.0.1 ROM ( MCG24.251-5) (TWRP flashable)
Computerfreek274_MM_1.0.3 Marshmallow 6.0.1
http://forum.xda-developers.com/droid-turbo/development/computerfreek274mm1-0-android-6-0-1-t3503634
Best to unlock your bootloader and flash or you may never be able to unlock your bootloader later.
ChazzMatt said:
Already done, as of 1pm Sunday 12/4/12016. Also there's a TWRP flashable version, and now even TWRP flashable ebloated ROM based on the OTA:
[OTA] Official Marshmallow build MCG24.251-5
http://forum.xda-developers.com/dro...ota-official-marshmallow-build-mcg24-t3512813
Click to expand...
Click to collapse
Great! Work for me on my xt1254 stock and lock
superuser install?
I flashed the TWRP zip, wiped everything, then it said I need to install SU... tried several times, but just got the bootloader unlocked disclaimer screen... finally didn't install SU, and it appears to be working.
i wipe system and cache , flashed but just got the disclaimer unlocked screen.
is necessary tu uninstall su before^?
gherman222 said:
I flashed the TWRP zip, wiped everything, then it said I need to install SU... tried several times, but just got the bootloader unlocked disclaimer screen... finally didn't install SU, and it appears to be working.
Click to expand...
Click to collapse
Which SuperSu are you using?
The one in this post works for Quark Motorola Marshmallow. SuperSu beta 2.62. After you flash it for initial root, then you can update to newer version.
http://forum.xda-developers.com/showpost.php?p=69722490&postcount=17
INITIAL ROOT ON QUARK MOTOROLA MARSHMALLOW 6.0.1
This same version of Marshmallow was released back in July for sibling Quark Moto XT1225. We found out then newer versions of SuperSu don't work for initial root. You need this older version first. No need to re-invent the wheel. It's the same device, same software.
_______________
Go ahead and download SuperSU from the attached file at bottom of this post. It's an older version of SuperSu but works well on the Quark Motorola Marshmallow ROM. You can always update to newer version later.
BETA-SuperSU-v2.62-3-20151211162651
Attached to this bottom of this post or download from here:
https://download.chainfire.eu/751/SuperSU/
Flash this version initially. You can update to newer version later. (People had problems flashing the very newest SuperSu for initial root, but this version works good. Again, you can update to newer version later, after you gain root.)
_______
BONUS TIP - SuperSu Setting
After you reboot, go into SuperSu settings and UNcheck this box. Mount namespace separation.
Uncheck that. Disable that. Then, reboot.
If it's enabled it will conflict with Titanium Backup which you will use at some point, or should. And you will have no idea why Titanium Backup is saying you are out of space, when you are not -- but it's due to this setting in SuperSu!
"M" Motorola boot logos
checo79 said:
i wipe system and cache , flashed but just got the disclaimer unlocked screen.
is necessary tu uninstall su before^?
Click to expand...
Click to collapse
No. You can just reflash your choice of boot logo to replace the unlocked warning screen. It's just a static image Motorola insists on showing you that your bootloader is unlocked. I know, I UNLOCKED it on purpose!
Here's boot logos (not to be confused with boot animation -- the boot logo is what you see before the boot animation starts) you can flash with ADB. Various colors of the Motorola M logo.
Remove annoying bootloader unlocked warning
ADB FLASHABLE BOOT LOGOS
http://forum.xda-developers.com/showpost.php?p=68538894&postcount=2
And here's the same boot logos you can flash with TWRP:
TWRP FLASHABLE BOOT LOGOS
http://forum.xda-developers.com/showpost.php?p=68579272&postcount=5
Works for all Quarks (XT1254/XT1250/XT1225).
It worked! Thanks man.
ChazzMatt said:
Which SuperSu are you using?
The one in this post works for Quark Motorola Marshmallow. SuperSu beta 2.62. After you flash it for initial root, then you can update to newer version.
http://forum.xda-developers.com/showpost.php?p=69722490&postcount=17
Click to expand...
Click to collapse
can anyone who's taken the OTA verify that it doesn't undo an existing sunshine bootloader unlock?
I want to take it, but don't want to risk the unlock,
thanks!
rhcreed said:
can anyone who's taken the OTA verify that it doesn't undo an existing sunshine bootloader unlock?
I want to take it, but don't want to risk the unlock,
thanks!
Click to expand...
Click to collapse
It doesn't. Confirmed.
TheSt33v said:
It doesn't. Confirmed.
Click to expand...
Click to collapse
Thanks!,
Of course, I delayed it a couple days, and now it doesn't show the update available anymore. Still get the "you're up to date" even though it shows a failed download in the status.
Guess it's for the best, I'll wait for a 7 rom that's stable enough to be a DD.
rhcreed said:
Thanks!,
Of course, I delayed it a couple days, and now it doesn't show the update available anymore. Still get the "you're up to date" even though it shows a failed download in the status.
Guess it's for the best, I'll wait for a 7 rom that's stable enough to be a DD.
Click to expand...
Click to collapse
You can download the OTA from here and flash it.
ChazzMatt said:
You can download the OTA from here and flash it.
Click to expand...
Click to collapse
if I do that will it wipe what I have now, or upgrade like an ota? I'm unlocked but still stock, too lazy to want to wipe and rebuild just yet.
Know of a way to reset the update service so it tries again? (I'm googling now, but figured you knew better than I did )?
rhcreed said:
if I do that will it wipe what I have now, or upgrade like an ota? I'm unlocked but still stock, too lazy to want to wipe and rebuild just yet.
Know of a way to reset the update service so it tries again? (I'm googling now, but figured you knew better than I did )?
Click to expand...
Click to collapse
From the op description, it will wipe what you have. So, yeah, wait for the OTA.
http://forum.xda-developers.com/showthread.php?t=3512813
Here is the latest OTA. Verizon says it has security (*cough* Sunshine *cough*) patches. I can confirm that it does not re-lock an unlocked bootloader. It's so minor, they just decided to slap an extra -5 on it.
https://www.androidfilehost.com/?fid=745425885120733909
Do not take this if your bootloader is locked and you'd like to unlock it at some point. If you'd like to unlock it at some point, do it now! What are you waiting for?
You cannot flash this with TWRP.
TheSt33v said:
Do not take this if your bootloader is locked and you'd like to unlock it at some point.
Click to expand...
Click to collapse
There, fixed it for you.
Gotta bold the important stuff.
ChazzMatt said:
There, fixed it for you.
Gotta bold the important stuff.
Click to expand...
Click to collapse
You're inhibiting natural selection.
TheSt33v said:
Here is the latest OTA. Verizon says it has security (*cough* Sunshine *cough*) patches. I can confirm that it does not re-lock an unlocked bootloader. It's so minor, they just decided to slap an extra -5 on it.
https://mega.nz/#!70Zh1BbS!cC_mZ8xouLVwvMlOZLKW2UyC-JXDS7SdnCjxDoafXbI
Do not take this if your bootloader is locked and you'd like to unlock it at some point. If you'd like to unlock it at some point, do it now! What are you waiting for?
You cannot flash this with TWRP.
Click to expand...
Click to collapse
hweew ... new kernel ...
could you upload it?
3Dota said:
hweew ... new kernel ...
could you upload it?
Click to expand...
Click to collapse
TWRP flashable, including kernel, version will be up shortly.
TheSt33v said:
TWRP flashable, including kernel, version will be up shortly.
Click to expand...
Click to collapse
Any modem updates?
koftheworld said:
Any modem updates?
Click to expand...
Click to collapse
Yes. Will also be included in TWRP version.
Yee!
I'm already unlocked on Stock with Stock recovery, and tried taking the OTA, but got an error when it rebooted to install
Sent from my XT1254 using Tapatalk
mustafu said:
I'm already unlocked on Stock with Stock recovery, and tried taking the OTA, but got an error when it rebooted to install
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
Have you done any modifications at all? Even in the past? For example, if you were rooted and then unrooted, if any files were left over from that process, the update will fail. If you had xposed and removed it, same deal. Even if you replaced your emoji file with an updated one, that will also cause it to fail. Did you modify build.prop? Fail.
The only way to be sure that it will pass is to reflash MCG24.251-5 with fastboot before taking the OTA. Or you could always do it the easy way and flash MCG24.251-5-5 with TWRP: https://forum.xda-developers.com/droid-turbo/general/rom-mcg24-251-5-5-100-stock-t3565795
I have a "system update paused, waiting for wi-fi" in the status bar. I don't want to take this update - can someone help me remove the notification, and block future updates? I have bl unlocked and rooted...
Tia
I'm running 24.81.5 and just received 24.91.5. Did not install. Unlocked and rooted. If I take this will it fail or cause issues?
Sent from my XT1254 using XDA-Developers Legacy app
g0ndor said:
I have a "system update paused, waiting for wi-fi" in the status bar. I don't want to take this update - can someone help me remove the notification, and block future updates? I have bl unlocked and rooted...
Tia
Click to expand...
Click to collapse
Install titanium backup and freeze the app called Motorola Update Services.
Shtiff1 said:
I'm running 24.81.5 and just received 24.91.5. Did not install. Unlocked and rooted. If I take this will it fail or cause issues?
Sent from my XT1254 using XDA-Developers Legacy app
Click to expand...
Click to collapse
It will fail. Any modifications at all (like root or TWRP, for example) will cause the update to fail.
So I'm guessing it's for "security" issues. So I really don't need to take this, because it involves to much crap... Unrooting, cleaning cache, reflashing, having to do the phone over again, etc.... If that is all true, then how can I get rid of the system update?
g0ndor said:
I have a "system update paused, waiting for wi-fi" in the status bar. I don't want to take this update - can someone help me remove the notification, and block future updates? I have bl unlocked and rooted...
Tia
Click to expand...
Click to collapse
Download "Disable Service" from the play store
TheSt33v said:
It will fail. Any modifications at all (like root or TWRP, for example) will cause the update to fail.
Click to expand...
Click to collapse
I'm not aware of any modifications, I thought I went back to all stock. Recovery says qe 1/1, is it supposed to be 0/1?
Sent from my XT1254 using Tapatalk
mustafu said:
I'm not aware of any modifications, I thought I went back to all stock. Recovery says qe 1/1, is it supposed to be 0/1?
Click to expand...
Click to collapse
If you look at the update script for the OTA, the first two thirds of it are dedicated to checking the system partition (and maybe other partitions. It's a pretty long read and I certainly haven't read all of it) for modifications. If the update is failing, that means it has detected something that does not match what it is checking for. I don't think the qe flag matters, because in the past I'm pretty sure that I've been at 1/1, and after a successful OTA it changes to 0/1.
trial TWRP or temp TWRP custom recovery
trial TWRP or temp TWRP custom recovery
TheSt33v said:
If you look at the update script for the OTA, the first two thirds of it are dedicated to checking the system partition (and maybe other partitions. It's a pretty long read and I certainly haven't read all of it) for modifications. If the update is failing, that means it has detected something that does not match what it is checking for. I don't think the qe flag matters, because in the past I'm pretty sure that I've been at 1/1, and after a successful OTA it changes to 0/1.
Click to expand...
Click to collapse
Don't know if this would help someone install an update like this, but let me throw this out there. There's a way to boot to TWRP custom recovery and use TWRP without installing TWRP. Think of it as "temporary" TWRP.
Thus, you should still be able to flash stuff, including any TWRP-flashable updates, boot logos (to replace the unlocked bootloader warning, SuperSu, etc -- and when you reboot you still have stock recovery.
Now, I don't know why anyone would want to keep stock recovery when TWRP recovery does so much more... But I just recently helped someone with the same suggestion. He wanted to install SuperSu, get root, but keep stock recovery -- for some reason.
Anyway, think of it as "trial TWRP" or "temp TWRP".
I remembered when I made factory images for my Quark, in a variety of states, I used this temporary TWRP trick. I'd almost forgotten about it!
So, seems like you could flash THIS TWRP-flashable version of this update while temporarily booting to TWRP (but not actually installing it), and it wouldn't matter if everything "checked" out or not.
Of course, if you like it, then you can always install it permanently.
For reference, here's the most recent version of TWRP for our phone. (use the one with the most recent post date. @bhb27 updates it fairly often.)
TWRP FOR QUARK
https://www.androidfilehost.com/?w=files&flid=39562
Here's my complete reply:
______
Rahuld107 said:
@ChazzMatt,
Hi, can i root xt1225 using temporary twrp ( one time method). I don't need twrp/custom recovery. Just want root with stock recovery. I am on stock marshmallow, bootloader is unlocked .
Click to expand...
Click to collapse
TEMPORARY TWRP
OK, here's another suggestion. There is a way to boot to TWRP to install SuperSu but NOT install TWRP. You will not be flashing TWRP over stock recovery. You will STILL have stock recovery when you reboot. Think of it as "temporary" TWRP.
Put the TWRP file in your ADB folder and use this command. Your phone will boot to TWRP, but it will not be permanently installed. You can then flash SuperSu while booted into the TWRP interface and then reboot back to your system.
fastboot boot file-name.img (whatever your file name of TWRP is.)
Whereas, the command to permanently install TWRP is this:
fastboot flash recovery file-name.img (whatever your file name of TWRP is.)
___
Back when I first got this phone -- now over two years ago -- I made a bunch of backups in TWRP and posted the images online in various stages -- pure stock, stock + root, stock + root + TWRP. I made the first two with the "temporary" TWRP. People could flash them and already have root without having TWRP installed.
Moto Maxx - Moto Turbo XT1225 factory images (Mexico | Puerto Rico | India | Brazil)
https://forum.xda-developers.com/moto-maxx/development/moto-maxx-moto-turbo-xt1225-factory-t3078274
1) TWRP BACKUPS which I made in various stages, such as
stock, unrooted
stock + rooted
stock + rooted + permanent TWRP
Click to expand...
Click to collapse
See? Even just stock + rooted but with no TWRP. I made that backup with a "temporary" TWRP which did not overwrite the stock recovery.
But they were only for 4.4.4 Kitkat, which came with this phone. After we went to Lollipop, I posted some more images, but just pure factory. Still, the "temporary" TWRP trick is useful.
Is it just me or the Gallery app in 6.0.1 scrolls really slow? Btw i didnt do a clean update from LP in case that could be the reason