Related
Hi all,
I have a very strange issue after the latest official OTA update to version 7.4.1.
I recognized that my KFHD updated the firmware and after this, I had no root anymore. I used Root_with_Restore_by_Bin4ry_v30 and my KFHD was rooted again (confirmed with root checker). Now I see that I am no longer able to user the settings menu at the top, for wireless network connection, brightness, etc., because it is no longer available. From time to time it appears for a very short period, but disappeared at the same time and I have no chance to drop down this menu.
Anyone here with the same problem or who can help me?
Cheers,
Ingo
Guys, no one, who can help me?
arnakin said:
Guys, no one, who can help me?
Click to expand...
Click to collapse
If you have a recovery installed, I would say just grab the rooted 7.4.1 from the development section and flash that after full wiping. That should solve your issues.
arnakin said:
Hi all,
I have a very strange issue after the latest official OTA update to version 7.4.1.
I recognized that my KFHD updated the firmware and after this, I had no root anymore. I used Root_with_Restore_by_Bin4ry_v30 and my KFHD was rooted again (confirmed with root checker). Now I see that I am no longer able to user the settings menu at the top, for wireless network connection, brightness, etc., because it is no longer available. From time to time it appears for a very short period, but disappeared at the same time and I have no chance to drop down this menu.
Anyone here with the same problem or who can help me?
Cheers,
Ingo
Click to expand...
Click to collapse
When (if) Kinology gets updated (for 7.4.1 support), flash that and your problem will be solved. Unless you don't care about what software version you are on. In that case just flash it now.
A similar problem
-a- said:
When (if) Kinology gets updated (for 7.4.1 support), flash that and your problem will be solved. Unless you don't care about what software version you are on. In that case just flash it now.
Click to expand...
Click to collapse
The OTA updated to 7.4.1 and i tried flashing a custom ROM by Hashcode but, recovery isn't working and with a force recovery in FireFire Flash. It shows a yellow triangle with an explanation point. Also, my audio has stopped working but, i may have found a solution.
To keep in mind: Already Rooted with B4NARY's root, and Google Play Installed.
All Help is appreciated!
CVanB said:
The OTA updated to 7.4.1 and i tried flashing a custom ROM by Hashcode but, recovery isn't working and with a force recovery in FireFire Flash. It shows a yellow triangle with an explanation point. Also, my audio has stopped working but, i may have found a solution.
To keep in mind: Already Rooted with B4NARY's root, and Google Play Installed.
All Help is appreciated!
Click to expand...
Click to collapse
Personally the only tool I've ever used because I got myself in so deep at one point I had no options was the Kindle SRTool, the others seem to create problems, not because the tools were written bad or anything, but because amazon seems to like pushing out updates that don't really update much, but change things just enough to mess with the functionality of the tools. If you can get back to fast boot, you should just use the SRTool and start fresh. Then go to prokkenexxusa's rooting thread and use the manual root method not the automatic.
Solved
DroidIt! said:
Personally the only tool I've ever used because I got myself in so deep at one point I had no options was the Kindle SRTool, the others seem to create problems, not because the tools were written bad or anything, but because amazon seems to like pushing out updates that don't really update much, but change things just enough to mess with the functionality of the tools. If you can get back to fast boot, you should just use the SRTool and start fresh. Then go to prokkenexxusa's rooting thread and use the manual root method not the automatic.
Click to expand...
Click to collapse
I didn't click flash script when I rebooted into recovery from fire flash. In fire flash you have a couple options, two mandatory, using a older bootloader as the 2nd. flash a boot partition image, apply stack override, flash a recovery partition image, disable auto recovery auto update, then wipe cache wipe data wipe system install zip files, flash and install script. Lastly reboot and reboot into recovery. :victory:
So did you get your issues sorted OK, or are you still having problems?
Hi, I used PwnMyMoto-1.4.3-TMobile.apk to get root on my T-mobile Moto X.
http://forum.xda-developers.com/showthread.php?t=2444957
Today, there was an OTA update that downloaded and said it would install. Now the phone is stuck in a boot loop. It boots OK but about 45 seconds after loading it shuts down and reboots. I'm guessing its because the PwnMyMoto removed the stock recovery or altered it to be unable to install the OTA update. However I guess the phone still sees the downloaded OTA update and wants to install it, so it reboots the phone to try to install.
I can't post in the PwnMyMoto thread because I'm too new to XDA
I have froze the ota apk to try to prevent this
small update. I used the T-mobile bundle here to get stock recovery.img and put that on my phone (because PwnMyMoto removes it) and then the OTA update installed. I guess instead I could have removed the downloaded update if I knew where it was!! After the OTA I lost root
http://sbf.droid-developers.org/ghost_rcica/list.php
emerica243 said:
I have froze the ota apk to try to prevent this
Click to expand...
Click to collapse
what do you mean by this? Can you tell me how to do that?
jackashe said:
what do you mean by this? Can you tell me how to do that?
Click to expand...
Click to collapse
Freezing a particular app can be done using Titanium Backup. Its available for download on play store. Titanium Backup requires root permissions. Freezing an app will leave the app on your phone but it wont work cuz its frozen lol... the app wont be uninstalled. this way if you decide later that you need the app then you can just unfreeze it and use it.
OK, I have TB and I know it supports freeze. I didn't realize you could freeze the OTA capability as a separate program. However given that I already downloaded the update, its too late to freeze.
jackashe said:
small update. I used the T-mobile bundle here to get stock recovery.img and put that on my phone (because PwnMyMoto removes it) and then the OTA update installed. I guess instead I could have removed the downloaded update if I knew where it was!! After the OTA I lost root
http://sbf.droid-developers.org/ghost_rcica/list.php
Click to expand...
Click to collapse
sorry if i or many people would have seeen this earlier we could have stopped you. Always be patient next time because you may have lost root forever now. Not that we know a patch will come through to allow us to maintain root in 4.3, but jcase said he proabbly wouldn't make a rot for 4.3 because it could be a pain and he doens't want to waste any of the exploits he knows of. You could always figure out a way your phone is bad and go exchange it and root again and don't take OTA until someone has figured out something to do to maintain root. It would be worth it for me.
You always have the option to unlock your bootloader with the T-Mobile version. I plan on unlocking the Dev edition I will be buying and then buying a SquareTrade warranty and that will cover any issues I might ever have including breaking/water damage.
jackashe said:
small update. I used the T-mobile bundle here to get stock recovery.img and put that on my phone (because PwnMyMoto removes it) and then the OTA update installed. I guess instead I could have removed the downloaded update if I knew where it was!! After the OTA I lost root
http://sbf.droid-developers.org/ghost_rcica/list.php
Click to expand...
Click to collapse
FSRBIKER said:
You always have the option to unlock your bootloader with the T-Mobile version. I plan on unlocking the Dev edition I will be buying and then buying a SquareTrade warranty and that will cover any issues I might ever have including breaking/water damage.
Click to expand...
Click to collapse
Yup I almost unlocked the boot loader but instead I was able to flash stock recovery. I wish android itself was smart enough to not try to install OTA when recovery was gone. I finally read through the jcase thread and I think I might have been able to delete the downloaded OTA by running:
Code:
fastboot erase cache
fastboot erase userdata
But I didn't try that. I also don't know what exactly that would have erased.
I will certainly look into a SquareTrade warranty!
Argh, I'm having the same problem. I have a Sprint version with unlocked bootloader and PwnMyMoto 1.1. Began after OTA update today. I have about 20 seconds after booting up that I'm able to do things on the phone before it goes into a loop; I've tried uninstalling the camera and disabling the gallery, which I thought were the two things that were updated. Safe mode doesn't work, nor does trying to enter recovery through fastboot. I've even tried factory resetting the phone from settings, but it can't do this before the power-down process begins. I haven't had any success with working through adb and the command prompt on this phone (device not found). At this point, I'm SOL and out of ideas with a bricked phone. Any other ideas?
UPDATE... Tried the fastboot erase cache & userdata; essentially performed a hard reset of device. Not the most convenient thing, but at least I have a working phone now.
so if we freeze updater and ota, we should be covered?
not sure about the other suspect apk with is fota.apk. I rename otacerts.apk as well. I may be a little paranoid about this but bricking is definitely not an option
jayboyyyy said:
sorry if i or many people would have seeen this earlier we could have stopped you. Always be patient next time because you may have lost root forever now. Not that we know a patch will come through to allow us to maintain root in 4.3, but jcase said he proabbly wouldn't make a rot for 4.3 because it could be a pain and he doens't want to waste any of the exploits he knows of. You could always figure out a way your phone is bad and go exchange it and root again and don't take OTA until someone has figured out something to do to maintain root. It would be worth it for me.
Click to expand...
Click to collapse
Yeah, root is great... I guess I'll just have to keep fingers crossed that jcase works on 4.2.2 post OTA but since it hasn't even been pushed to all carriers maybe it won't happen. Yes, I should have NOT gotten the OTA, but once it had downloaded my phone was totally unusable until I restored recovery and it installed itself.
jackashe said:
Yeah, root is great... I guess I'll just have to keep fingers crossed that jcase works on 4.2.2 post OTA but since it hasn't even been pushed to all carriers maybe it won't happen. Yes, I should have NOT gotten the OTA, but once it had downloaded my phone was totally unusable until I restored recovery and it installed itself.
Click to expand...
Click to collapse
Curious have you tried to reroot, and for future reference I believe ota are usually in cache under the previous build # for Verizon at least.
shane1 said:
Curious have you tried to reroot, and for future reference I believe ota are usually in cache under the previous build # for Verizon at least.
Click to expand...
Click to collapse
I did try rooting again using PwnMyMoto-1.4.3-TMobile.apk but it failed to install (since one of the exploits it used is patched)
I have t-Mobile but how would I get to the cache? My phone would boot for about 45 seconds and in that time-frame I could adb shell into the phone but could not find the path for the OTA update. Do you mean it would be in /cache/some-build/ or so?
Yes in cache and you would have to attempt from a PC , which might not have been possible because the phone kept rebooting. Also I am sry for your loss
Would ota root keeper do anything for us?
Sent from my XT1058 using XDA Premium 4 mobile app
IncredibleHulk6 said:
Argh, I'm having the same problem. I have a Sprint version with unlocked bootloader and PwnMyMoto 1.1. Began after OTA update today. I have about 20 seconds after booting up that I'm able to do things on the phone before it goes into a loop; I've tried uninstalling the camera and disabling the gallery, which I thought were the two things that were updated. Safe mode doesn't work, nor does trying to enter recovery through fastboot. I've even tried factory resetting the phone from settings, but it can't do this before the power-down process begins. I haven't had any success with working through adb and the command prompt on this phone (device not found). At this point, I'm SOL and out of ideas with a bricked phone. Any other ideas?
UPDATE... Tried the fastboot erase cache & userdata; essentially performed a hard reset of device. Not the most convenient thing, but at least I have a working phone now.
Click to expand...
Click to collapse
Can you please tell me how you did this? Thanks in advance
Perhaps this thread helps http://forum.xda-developers.com/showthread.php?p=46179190#post46179190
Erk, after getting into the same post-Root update loop, I flashed back to stock using the recipe here: http://forum.xda-developers.com/showthread.php?p=46175635&postcount=8
I now have 13.9.0Q2.X-116-X-17-51 installed.
When I go to System updates to update to the OTA update 13.0Q2.X-116-X-17-54, I get told that I am already updated to the latest version.
Any help would be much appreciated!
jayboyyyy said:
sorry if i or many people would have seeen this earlier we could have stopped you. Always be patient next time because you may have lost root forever now. Not that we know a patch will come through to allow us to maintain root in 4.3, but jcase said he proabbly wouldn't make a rot for 4.3 because it could be a pain and he doens't want to waste any of the exploits he knows of. You could always figure out a way your phone is bad and go exchange it and root again and don't take OTA until someone has figured out something to do to maintain root. It would be worth it for me.
Click to expand...
Click to collapse
manfly9884 said:
Can you please tell me how you did this? Thanks in advance
Click to expand...
Click to collapse
You have to make sure you have downloaded & installed the Android SDK and the latest Motorola Android drivers to your computer. On your phone, shut it down before it has the chance to re-enter the boot loop cycle. Then press the down button simultaneously with the power button for a few seconds and release the down button a split second before releasing the power button. This enters the bootloader (you may have to try it a few times to get it). Plug your phone into the computer and open a command prompt on the computer; type "fastboot erase cache", hit enter, type " fastboot erase userdata" and hit enter. You'll see confirmation in the command prompt and your phone will reboot as factory reset.
Don't know what just happened, but here's the best I can explain and hopefully someone smarter than me can figure it out!
My G2 is rooted and running stock 4.4.2 version 24A and I have TWRP 2.7.0.0. I think, besides the hotspot hack, the only thing I had done to it is quarantine LG SetupWizard with App Quarantine. My phone has been trying to push through updates for months, but it never does it successfully becasue of root. Just now, I tried something different to see if I could get the OTA update to install...it was tring to install 26A. I took SetupWizzard out of quarantine and in Superuser I checked OTA survival. After it downloaded the OTA and rebooted it went straight to recovery. From recovery I tried to reboot to system, but it went straight into recovery. So, I restored the backup I made yesterday and tried to reboot back to system again and still it's going to recovery. Any ideas??
Fixed!
Found this thread after a search and reading a thread on the G3.
http://forum.xda-developers.com/showthread.php?t=2451696
Tsip85 said:
Don't know what just happened, but here's the best I can explain and hopefully someone smarter than me can figure it out!
My G2 is rooted and running stock 4.4.2 version 24A and I have TWRP 2.7.0.0. I think, besides the hotspot hack, the only thing I had done to it is quarantine LG SetupWizard with App Quarantine. My phone has been trying to push through updates for months, but it never does it successfully becasue of root. Just now, I tried something different to see if I could get the OTA update to install...it was tring to install 26A. I took SetupWizzard out of quarantine and in Superuser I checked OTA survival. After it downloaded the OTA and rebooted it went straight to recovery. From recovery I tried to reboot to system, but it went straight into recovery. So, I restored the backup I made yesterday and tried to reboot back to system again and still it's going to recovery. Any ideas??
Click to expand...
Click to collapse
The reason why this is happening is you are trying to install the update OTA with a custom recovery. The way these OTA updates work is the OS downloads the file and stores it in a secure location. It has an auto-run updating sequence to allow the OS to update in the regular recovery. Because you have TWRP, TWRP has no idea where to find the file to update the device and therefore, does nothing. However, when you boot up the phone again, it realizes the phone has not yet been updated and goes back into recovery to make sure the update goes through. It is a continuous cycle that therefore never completes it's self. To fix this, run these instructions:
Because the G2 does not have an external SD card, you should do this: use TWRP's awesome "terminal command" option to run the following: dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
You need to get this PERFECTLY or else you will destroy your phone. Hope this helps.
mach01 said:
The reason why this is happening is you are trying to install the update OTA with a custom recovery. The way these OTA updates work is the OS downloads the file and stores it in a secure location. It has an auto-run updating sequence to allow the OS to update in the regular recovery. Because you have TWRP, TWRP has no idea where to find the file to update the device and therefore, does nothing. However, when you boot up the phone again, it realizes the phone has not yet been updated and goes back into recovery to make sure the update goes through. It is a continuous cycle that therefore never completes it's self. To fix this, run these instructions:
Because the G2 does not have an external SD card, you should do this: use TWRP's awesome "terminal command" option to run the following: dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
You need to get this PERFECTLY or else you will destroy your phone. Hope this helps.
Click to expand...
Click to collapse
Thank you. I started searching for a solution and found a thread that had those exact instructions. And this little lesson has now led me to searching for something that will let me quickly and easily switch recoveries if I want to take an OTA.
Tsip85 said:
Thank you. I started searching for a solution and found a thread that had those exact instructions. And this little lesson has now led me to searching for something that will let me quickly and easily switch recoveries if I want to take an OTA.
Click to expand...
Click to collapse
Glad it helped. As for a recovery switcher, you might want to consider using a simple one of the Play Store. They are convenient and easy to use. This thread is really great: http://www.xda-developers.com/simple-recovery-switcher/
Hope this helps.
Tsip85 said:
Thank you. I started searching for a solution and found a thread that had those exact instructions. And this little lesson has now led me to searching for something that will let me quickly and easily switch recoveries if I want to take an OTA.
Click to expand...
Click to collapse
Would you mind sharing that link I need to find my bosses g2 please help
chazla86 said:
Would you mind sharing that link I need to find my bosses g2 please help
Click to expand...
Click to collapse
Yes...check the link I posted on the second post.
Hey all,
Thought I'd let those of you that have an AT&T Tab S 8.4 know that Lollipop has been released today. Happened to be on the AT&T Software update page here: http://www.att.com/esupport/softwareUpdateArticle.jsp?sid=KB425812&cv=820 and noticed it listed the update.
Manually checked for updates on my tablet, it's downloading now. My 8.4 on AT&T is totally stock.
Downloading now... 1.1GB
manually checking shows nothing for me
Mine wasn't too laggy after the upgrade. But as I know from places like XDA usually a very good idea to do a full system wipe which I did.
What I am most thankful for is there is now an option to remove that Samsung screen that has those Samsung widgets that go full page. Can't recall what it is called. Yeah I know could have got rid of that using a 3rd party launcher in 4.4 but so happy Samsung put option there to disable it finally. To get rid of it, long press blank space like you were going to add a widget, then click Home Screen Settings, then uncheck "Content Home Screen".
Has anyone who rooted with kingroot updated? I'm assuming it'll kill root, just curious if I need to unroot prior, or if the update will still install. I'll post the answer tomorrow after I update.
I've had some Samsung devices which will update while rooted, and some that will not.
Russ77 said:
Has anyone who rooted with kingroot updated? I'm assuming it'll kill root, just curious if I need to unroot prior, or if the update will still install. I'll post the answer tomorrow after I update.
I've had some Samsung devices which will update while rooted, and some that will not.
Click to expand...
Click to collapse
Not sure it will work.
Maybe try to adapt the method given by ashyx here: http://forum.xda-developers.com/galaxy-tab-s/general/guide-how-to-root-tripping-knox-kitkat-t3129484
It worked successfully for me on the T800
Russ77 said:
Has anyone who rooted with kingroot updated? I'm assuming it'll kill root, just curious if I need to unroot prior, or if the update will still install. I'll post the answer tomorrow after I update.
I've had some Samsung devices which will update while rooted, and some that will not.
Click to expand...
Click to collapse
I'm rooted with Kingroot and it's currently downloading the update. If you load Xposed Framework and Wanam Xposed, under Security hacks there's a setting for Fake System Status that allows you to set it to Original.
I'll follow up when the download finishes.
Update: The download completed but the install failed and then got stuck in a boot loop. Ended up having to go to the Samsung place at Best Buy to have them re-flash KitKat. Now the tab is telling me I have to wait 24 hours to check for updates. I'm sure everything will be good now that I'm back on a factory image.
fleabeard said:
I'm rooted with Kingroot and it's currently downloading the update. If you load Xposed Framework and Wanam Xposed, under Security hacks there's a setting for Fake System Status that allows you to set it to Original.
I'll follow up when the download finishes.
Update: The download completed but the install failed and then got stuck in a boot loop. Ended up having to go to the Samsung place at Best Buy to have them re-flash KitKat. Now the tab is telling me I have to wait 24 hours to check for updates. I'm sure everything will be good now that I'm back on a factory image.
Click to expand...
Click to collapse
Turn off automatic date and time and manually advance it by a day, and try again.
When they re-flashed KitKat did it wipe your tablet? The OTA failed me when rooted, failed me after un-installing adaway and un-rooting and removing KingUser. I cannot do a firmware upgrade via Kies 3 as it's not available. I cannot do an emergency firmware recover via Kies 3 as it's not soft bricked. I can't find either the KitKat or the Lollipop firmwares online anywhere... Currently I have a tablet, works fine, I did a factory reset (in the back of my mind knew this wouldn't work) that has a custom status and won't take the OTA.
If anyone knows where I can find the KitKat firmware, or the OTA, please let me know.
Or maybe someone could grab the OTA off their tablet after downloading prior to updating and share the wealth with the community???
Has any kingroot user tried triangle away, unroot via kinguser, and take the OTA?
Also just realized that if I can fail the OTA, I can obviously download it... Where do I grab it from if I wanted to flash it with odin or sideload?
Russ77 said:
Has anyone who rooted with kingroot updated? I'm assuming it'll kill root, just curious if I need to unroot prior, or if the update will still install. I'll post the answer tomorrow after I update.
I've had some Samsung devices which will update while rooted, and some that will not.
Click to expand...
Click to collapse
Russ77 said:
Turn off automatic date and time and manually advance it by a day, and try again.
When they re-flashed KitKat did it wipe your tablet? The OTA failed me when rooted, failed me after un-installing adaway and un-rooting and removing KingUser. I cannot do a firmware upgrade via Kies 3 as it's not available. I cannot do an emergency firmware recover via Kies 3 as it's not soft bricked. I can't find either the KitKat or the Lollipop firmwares online anywhere... Currently I have a tablet, works fine, I did a factory reset (in the back of my mind knew this wouldn't work) that has a custom status and won't take the OTA.
If anyone knows where I can find the KitKat firmware, or the OTA, please let me know.
Or maybe someone could grab the OTA off their tablet after downloading prior to updating and share the wealth with the community???
Click to expand...
Click to collapse
OTA came down successfully while not rooted. The reflash at Best Buy didn't wipe it.
As far as I know, the factory images for the AT&T versions aren't available anywhere, or at least I've been unable to find them. They obviously exist because I'm pretty sure the guy at Best Buy used Kies to flash with an image that's available to him from Samsung.
I re-rooted last night in the attempt of using triangle away to clear customs status, then un-rooting. This was odd because device status still shows custom but download mode shows official and Knox is 0.
While I was briefly rooted again I downloaded the OTA in the hopes of copying it to my PC and updating via ADB Sideload... Couldn't find it. If anyone knows where Samsung puts these I'll grab it and post it to share.
im not rooted, performed a factory reset, and my device still doesn't see any updates. Can somebody provide a link to the ROM?
Same situation here - no root, no mods, no available update
Sent from my SM-G925V using XDA Premium HD app
Same Thing Here Also
bshaw100 said:
Same situation here - no root, no mods, no available update
Sent from my SM-G925V using XDA Premium HD app
Click to expand...
Click to collapse
I've got the same thing: no root, no mods, no update available! Darn!!!!
I've got the same thing: no root, no mods, no update available!
Russ77 said:
I re-rooted last night in the attempt of using triangle away to clear customs status, then un-rooting. This was odd because device status still shows custom but download mode shows official and Knox is 0.
While I was briefly rooted again I downloaded the OTA in the hopes of copying it to my PC and updating via ADB Sideload... Couldn't find it. If anyone knows where Samsung puts these I'll grab it and post it to share.
Click to expand...
Click to collapse
The OTA gets downloaded to /cache. If you are rooted you can see it. But the OTA is not a complete ROM, just a differential to the ROM you have.
Sent from my SM-T707V using XDA Premium HD app
still nothing
gshaw_nash said:
I've got the same thing: no root, no mods, no update available! Darn!!!!
Click to expand...
Click to collapse
gshaw1967 said:
I've got the same thing: no root, no mods, no update available!
Click to expand...
Click to collapse
I've reset several time and cannot download the update. I get "Connecting to DM Server" and then update interrupted. Has anyone gotten around this?
---------- Post added at 08:58 AM ---------- Previous post was at 08:11 AM ----------
gshaw1967 said:
I've reset several time and cannot download the update. I get "Connecting to DM Server" and then update interrupted. Has anyone gotten around this?
Click to expand...
Click to collapse
Turns out there is a imei problem with the tablet that is preventing the download. My imei number is paired with a IPhone 4. Anyway will take a few day to fix then the upgrade should work.
I get the same. I wiped my device hoping for a different outcome, and still no update.
I found this in the thread below.
It is an old tread but I'll comment anyway. SM-T807 is the 3G version while SM-T805 is the LTE version. Both Hardware (CPU/GPU) and comms modules are different. So 805 LTE (which has Lollipop) firmware won't work for 807 (no Lollipop is currently available nor Samsung plans to release soon).
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-tab-s/help/sm-t805-sm-t807a-t2961117
John.
After not being able to take the OTA after rooting, even after un rooting, not being able to find the OTA and sideload (not in /cache), and not able use Kies or Odin I finally took it to the Samsung kiosk at my bestbuy.
They reflashed 4.4.2, didn't wipe anything, and immediately downloaded and successfully installed the lollipop update after getting home and on WiFi.
Just don't mention that you rooted ;')
So I apparently let it sit too long while setting up the ROM installation and it suddenly rebooted itself only to find that it wanted to attempt the OTA installation. I am on 5.1.2 currently. I stopped this swiftly but now it will not allow to access the stock recovery and only gives the FIRE logo and immediately begins trying to install the update which I promptly stop during validation. So the system has not been upgraded as of yet but it is sure trying like hell to do so. I have attempted to intercept the beginning installation with USB and adb. So far no go. Anyone have any ideas as to get around the fact that the new update is slated for install at every boot? Thanks in advance.
I made the same thing, I failed flashing lineage 12.1 from cyanogenmod 12.1 with flashfire.
then I restored a stock 5.1.2, it worked. but the root with kingroot was not complete and I went to bed.
When I switched on again, I got the upgrade message...
The recovery won't come out.
jaymz199 said:
So I apparently let it sit too long while setting up the ROM installation and it suddenly rebooted itself only to find that it wanted to attempt the OTA installation. I am on 5.1.2 currently. I stopped this swiftly but now it will not allow to access the stock recovery and only gives the FIRE logo and immediately begins trying to install the update which I promptly stop during validation. So the system has not been upgraded as of yet but it is sure trying like hell to do so. I have attempted to intercept the beginning installation with USB and adb. So far no go. Anyone have any ideas as to get around the fact that the new update is slated for install at every boot? Thanks in advance.
Click to expand...
Click to collapse
Le_Zouave said:
I made the same thing, I failed flashing lineage 12.1 from cyanogenmod 12.1 with flashfire.
then I restored a stock 5.1.2, it worked. but the root with kingroot was not complete and I went to bed.
When I switched on again, I got the upgrade message...
The recovery won't come out.
Click to expand...
Click to collapse
Tough situation. OTA updates are typically stored in the cache (mmcblk0p12) partition - although there is some evidence Amazon may now be using one or more other partitions which makes sense given their size. Flushing cache from fastboot would kill the pending OTA. Unfortunately, Amazon disabled both the 'erase' and 'format' commands. Not much can be done unless you can access stock recovery. Might have to accept the update.
Davey126 said:
Tough situation. OTA updates are typically stored in the cache (mmcblk0p12) partition - although there is some evidence Amazon may now be using one or more other partitions which makes sense given their size. Flushing cache from fastboot would kill the pending OTA. Unfortunately, Amazon disabled both the 'erase' and 'format' commands. Not much can be done unless you can access stock recovery. Might have to accept the update.
Click to expand...
Click to collapse
That's unfortunate that it is impossible to get to stock recovery on reboot. I will hold out for a possible solution on this one and see what comes of it. Thank you for the information.
Le_Zouave said:
I made the same thing, I failed flashing lineage 12.1 from cyanogenmod 12.1 with flashfire.
then I restored a stock 5.1.2, it worked. but the root with kingroot was not complete and I went to bed.
When I switched on again, I got the upgrade message...
The recovery won't come out.
Click to expand...
Click to collapse
I had completed the root process but had not flashed the ROM as of yet. I failed to block OTA while performing the root.My fault in the end. They waste no time force feeding the OTA.