Related
Update : Oct 24, 2015 It looks like the bricking scare is over, and there is an updated guide on how to upgrade to the latest Lollipop without bricking :
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
PUBLIC SERVICE ANNOUNCEMENT :
There are now several reports of super hard bricks (not even Amazon logo shows up) when people attempted to load 5.2.2 version via TWRP.
My best guess is that it has something to do with the 5.x update from Amazon that people request before downgrading to 4.5.3. If Amazon is providing a newer 5.x. update, it can be blocking the older 5.2.2 from working after the downgrade-upgrade procedure. When it bricked before, it would at least show "Amazon" logo, but now even the logo is gone.
One would have to capture this current 5.x update, and see what's in it. It's probably updating another partition out of those that were previously untouched :
http://forum.xda-developers.com/fire...idden-t3122246
All the downgrade-upgrade guides are on hold for now ... You are still safe to exist in the 4.5.x space (with root).
bibikalka said:
One would have to capture this current 5.x update, and see what's in it.
Click to expand...
Click to collapse
I assume I can capture file by reversing rename of DeviceSoftwareOTA.apk but leaving OTA updating blocked. Is that the method?
EDIT: Well, just did rename. No download yet. I've got otaverifier blocked. If nothing soon, I'll enable that and block dcp.
This update was strange and left a very small .data file in cache after saying a download was complete, ready to upgrade. Could not locate a bin file. I will/would try capturing a link via adb logcat.
could be a small update that just preps us to move back to the normal releases.
Just educated guesses.
siegesoldier said:
This update was strange and left a very small .data file in cache after saying a download was complete, ready to upgrade. Could not locate a bin file. I will/would try capturing a link via adb logcat.
could be a small update that just preps us to move back to the normal releases.
Just educated guesses.
Click to expand...
Click to collapse
All that downloaded for me were apk update files, no .data, but device>updates shows:
10.0.42-D-20150925-NA-4 is ready to install
I ran logcat during download and a couple of manual installs (pressing Install button, but I do have updates blocked). I didn't see anything obviously related to update in the logcats, but not sure what to look for. Since I didn't get the .data, will I find anything helpful in logcat? What should I look for? thx
p.s., Or must I unblock updating to capture?
siegesoldier said:
This update was strange and left a very small .data file in cache after saying a download was complete, ready to upgrade. Could not locate a bin file. I will/would try capturing a link via adb logcat.
could be a small update that just preps us to move back to the normal releases.
Just educated guesses.
Click to expand...
Click to collapse
Yep, this is weird. I wonder if one should flash 4.5.3 bootloaders with TWRP in Lollipop first as per this post http://forum.xda-developers.com/showpost.php?p=62011272&postcount=2 , and let it try to upgrade. This way whatever files it downloads, they will be sitting in /cache. But nothing will be run as it is a non-Amazon recovery.
Another poster indicated that the tablet rebooted about 3 times, and then he got new icons and Amazon launcher :
http://forum.xda-developers.com/showpost.php?p=63116048&postcount=141
bibikalka said:
I wonder if one should flash 4.5.3 bootloaders with TWRP in Lollipop first as per this post http://forum.xda-developers.com/showpost.php?p=62011272&postcount=2 , and let it try to upgrade. This way whatever files it downloads, they will be sitting in /cache. But nothing will be run as it is a non-Amazon recovery.
Click to expand...
Click to collapse
I'm more than willing to try to capture this if one of you can tell me how.
I don't quite follow the above. I'm running rooted 5.2.2. So I'd flash bootloaders and TWRP per guide, install OS 4.5.5, boot to OS and try to upgrade? Is this any different from someone already on 4.5.5 trying to upgrade? thx
DoLooper said:
I'm more than willing to try to capture this if one of you can tell me how.
I don't quite follow the above. I'm running rooted 5.2.2. So I'd flash bootloaders and TWRP per guide, install OS 4.5.5, boot to OS and try to upgrade? Is this any different from someone already on 4.5.5 trying to upgrade? thx
Click to expand...
Click to collapse
Not this complicated. I think you could flash 4.5.3 bootloaders + TWRP under 5.2.2, enable OTA updates, and continue working. When it decides to self-reboot (after the update is copied to /cache), it won't find stock 5.2 recovery. Instead, it'll hang (4.5.3 bootloaders cannot boot 5.2.2). At this point you can manually reboot into TWRP, and see what's in /cache. Then you just reapply 5.2.0 bootloaders + 5.2.0 recovery, and boot back into 5.2.2 (and do disable OTA here !!!) Hopefully it does not write into recovery partition before auto-rebooting, so that TWRP survives intact.
bibikalka said:
Not this complicated. I think you could flash 4.5.3 bootloaders + TWRP under 5.2.2, enable OTA updates, and continue working. When it decides to self-reboot (after the update is copied to /cache), it won't find stock 5.2 recovery. Instead, it'll hang (4.5.3 bootloaders cannot boot 5.2.2). At this point you can manually reboot into TWRP, and see what's in /cache. Then you just reapply 5.2.0 bootloaders + 5.2.0 recovery, and boot back into 5.2.2 (and do disable OTA here !!!) Hopefully it does not write into recovery partition before auto-rebooting, so that TWRP survives intact.
Click to expand...
Click to collapse
OK, I'll try this later or tomorrow. Still wonder though, couldn't you--anyone on 4.5.5--leave OTA package blocked but rename OTAsoftware extension back to apk, allowing the update to download but not install?
)':
Hello, I am french sorry for my english
My kindle fire is bricked
how to repair !! :crying::crying:
help me please :/
bibikalka said:
. . . At this point you can manually reboot into TWRP, and see what's in /cache. Then you just reapply 5.2.0 bootloaders + 5.2.0 recovery, and boot back into 5.2.2 (and do disable OTA here !!!) Hopefully it does not write into recovery partition before auto-rebooting, so that TWRP survives intact.
Click to expand...
Click to collapse
@bibikalka OK, ready to do this and (more or less) prepared to get replacement Fire . Just one question: Why do you think there will be anything in cache after the update and reboot attempt? i.e., wouldn't deleting it be part of the update process? Thanks! (Edit: NVM--I see your explanation above.)
EDIT @bibikalka, @everyone Thought the update was out for my region, but guess not: With DeviceSoftareOTA.apk named as originally and otaverifier enabled, Device>Updates just returns "no updates." Disabled otaverifier again and will wait on this.
I believe the update will download with DeviceSoftwareOTA.apk properly named--and hope it won't update with otaverifier disabled. So maybe I can get it. Anyway, I'll check for it over next few days, but maybe someone else will try this method first. (I am west-coast US and it seems always last to get updates.)
DoLooper said:
@bibikalka OK, ready to do this and (more or less) prepared to get replacement Fire . Just one question: Why do you think there will be anything in cache after the update and reboot attempt? i.e., wouldn't deleting it be part of the update process? Thanks!
Click to expand...
Click to collapse
I think it will prepare to update by staging the required files in /cache, but then it'll try to reboot to apply those files (usually updates are applied in recovery ...). So when reboot fails (as it should with TWRP & 4.5.3 bootloaders which don't boot Lollipop), you intercept the stuff in /cache and see what it has.
Added: If this works, do wipe /cache before leaving TWRP (when you restore 5.2 bootloaders). This way it won't pick up the scripts and run them ...
See edit here. Forgot that I'm always last to get an upgrade. Hope someone who might get it sooner will use bibkalka's method so we can get this show back on the road.
After downloading the 5.0.1 update once I have been unable to get it again. My build number has not updated so its possible they pulled it. Root etc still works so it doesn't look like it applied.
Hello, just wanted to say that I can testify to the fact that after updating to 5.2.2, then downgrading and going into TWRP, flashing all the zips, and then wiping cache before rebooting..... gets you a BRICK!! I've stupidly done it.... to my replacement from Amazon! Hopefully sometime in the future someone can get me out of this one....
hello there recently my rooted fire os 5 with xposed playstore just updated to 5.0.1 by it self and i swear i did have com.amazonotaverifier blocked its weird because it updated when i left my fire hd 6 on charge
it just updated itself to fire os 5.0.1 il stay on that fire os because people are saying you get bricked if you do the whole procedure like downgrade back to 4.5.3 and root and get custom recovery and flash all the zips = brick
2nd try to get 5.0.1 update
I didn't capture the update, but maybe learned something about OTA. Two things I hope someone can explain.
First, I've had extension of DeviceSoftwareOTA.apk renamed back to (plain) .apk since last attempt to capture update. Today:
1. "Check for updates" returned: 10.0.43.-D-20151007-NA-5 is ready to install
(last week there was one named: 10.0.42-D-20150925-NA-4)
2. I dd'd the 4.5.3 bootloaders and twrp (with otaverifier blocked)
3. Unblocked otaverifier, but the only thing that downloaded to /cache was "amazonmp3_10004310.apk" (update to mp3 player, i guess).
(last week they were apks for map and photo apps)
4. Hit "check for updates" again, but now it said "none" and /cache was empty.
(same thing last week)
Does anyone know about updates named like "10.0.43.-D-20151007-NA-5?" I've only seen them since I "corrected" the deviceSoftwareOTA.apk extension, and only apk files get downloaded. A couple logcats I got, however, have many more update entries than I've seen before, but I don't understand logcats very well. If someone who knows logcats could have a look, I'd appreciate it. Just tell me where to post. I think it would help us to know if these updates do more than update the accompanying apks.
------------------------
EDIT: NVM below! I'm getting # prompt because I recently set "adbd insecure" app to start at boot <doh> .
Second, I decided to start over and see if there was a different update waiting. So:
1. Went to twrp and flashed 5.2.0_stock_recovery_uboot.zip (for 5.0 stock recovery and bootloaders, i hope), wiped cache, and booted to OS.
2. Got l o o o n g startup. When OS finally loaded, "adb shell" hung CMD. I had to run TASKKILL /F /IM adb* >nul 2>&1 before adb shell was recognized. And when it was, it consistently returned # prompt: ([email protected]:/ #)
I'm definitely rooted, all google works, version still shows 5.0.0, build date July 20, but even after rebooting both tablet and computer, "adb shell" still always returns # prompt.
Can anyone tell me what's going on here? (Sorry this is tldr; hope a few of you slog through.) Thanks.
EDIT: it's late, maybe I'm nuts, but seems "adb shell" should return $ prompt, then "su" returns #.
DoLooper said:
I didn't capture the update, but maybe learned something about OTA. Two things I hope someone can explain.
First, I've had extension of DeviceSoftwareOTA.apk renamed back to (plain) .apk since last attempt to capture update. Today:
1. "Check for updates" returned: 10.0.43.-D-20151007-NA-5 is ready to install
(last week there was one named: 10.0.42-D-20150925-NA-4)
2. I dd'd the 4.5.3 bootloaders and twrp (with otaverifier blocked)
3. Unblocked otaverifier, but the only thing that downloaded to /cache was "amazonmp3_10004310.apk" (update to mp3 player, i guess).
(last week they were apks for map and photo apps)
4. Hit "check for updates" again, but now it said "none" and /cache was empty.
(same thing last week)
Does anyone know about updates named like "10.0.43.-D-20151007-NA-5?" I've only seen them since I "corrected" the deviceSoftwareOTA.apk extension, and only apk files get downloaded. A couple logcats I got, however, have many more update entries than I've seen before, but I don't understand logcats very well. If someone who knows logcats could have a look, I'd appreciate it. Just tell me where to post. I think it would help us to know if these updates do more than update the accompanying apks.
.
Click to expand...
Click to collapse
These updates appear to be just individual apps, nothing to do with the system. You can google the version numbers, and it'll find that stuff.
The only hope is to checksum all partitions, and find the one that was updated in the latest version 5, but otherwise does not change in earlier versions. One could right a script for that. Then we could overwrite it.
But I suspect the new update may have written into one of the partitions that have other stuff, so the checksum identification won't help.
bibikalka said:
The only hope is to checksum all partitions, and find the one that was updated in the latest version 5, but otherwise does not change in earlier versions. One could right a script for that. Then we could overwrite it.
But I suspect the new update may have written into one of the partitions that have other stuff, so the checksum identification won't help.
Click to expand...
Click to collapse
Would that mean 5.0.1 would not be rootable?
Hello, I am curious, would it be possible to use "fastboot boot recovery.img" instead of actually flashing it in order to get root in the new 5.2.2 (build date sep 23)? It seems this would solve the hard brick problem with flashing twrp.
I'm on a never-rooted 2014 HD6 with gapps & OS 5.2.2. Very interested in rooting this tablet.
hi,
my Eng is not good, i don't understand the title
Stop !!! Do not upgrade to lollipop via twrp !!!
on today i'm receive Fire HD 7 from my phone provider. This is free.
i was rooted it with kingroot. It was succesfull. But i want setup it with android with vietnames because my boy are 10 age.
it run fire os 4.5.3 now.
can i upgrade to android 5.x?
thank for read
I am not responsible for your bricked phone or pigeon poo on your toupe. Do at your own risk.
Many thanks to @SupahCookie for idea and motivation!
INTENTIONALLY DOES --NOT-- LOCK BOOTLOADER!!!
Get factory images here:
https://forum.xda-developers.com/mo...ock-images-t3736767/post75236696#post75236696
THIS GUIDE IS FOR FACTORY/STOCK ROMs - NOT YOUR AVERAGE CUSTOM ROM which may not have bootloaders!!! (thanks!!!!! @echo92 )
FIX:
IF YOU ARE ABLE TO GET TO FASTBOOT THIS SHOULD WORK.
IF YOU HAVE 8.x bootloaders AND ARE DOWNGRADING TO 7, use "Alternative to RSDlite" below.
1 boot to win - 7 or 10 works fine.
2 boot phone to fastboot, and connect phone to computer.
3 start RSDlite
pick a ROM. I believe I used a 7.1.1 rom
3Nov9-ADDISON_NPNS26.118-22-2-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
RSDlite installed it and fixed the problem.
- -
I was then able to use RSDlite to install @rafikowy 's signed 8.0 . - going up from 7 to 8.
- -
- -
If you are on 8.x bootloaders and want to go to 7.x bootloaders, use this (RSDlite throws an error and stops):
ALTERNATIVE TO RSDlite:
1 I used 7zip to extract that 7.1.1 zip (or any ROM zip) into a folder x,
2 add all the adb and fastboot junk to folder x,
3 add the attached file (rename it to flash.bat) to folder x.
4 boot phone to fastboot and connect to computer.
5 click on flash.bat - it throws a lot of "slot" errors but works just fine.
6 reboot your phone if it hasn't already and go through the 7.x install stuffs.
7 you will not show an IMEI if you are coming from an 8.x bootloader. However, it IS there.
NOTE: you may need to add a line to the flash.bat if there are more/less sparsechunk's in your FACTORY/STOCK ROM...
THIS IS NOT FOR CUSTOM ROMs!!!!!!!
EDIT: 3-8-19: I just did this myself to go back very briefly to 7.1 - be sure you don't flash TWRP to it if your going to take OTAs - it will brick it. boot to TWRP if you need TWRP briefly: fastboot boot twrpimg.img
----------
If you can boot to fastboot screen, you can do anything.
Never OTA a ROM if you have modified recovery (TWRP, etc) or if magisk is present.
https://forum.xda-developers.com/mo...p-flashing-t3813498/post77011495#post77011495
I changed the attached file to add pause and reboot and exit to make it slightly more automated.
I have successfully used this many times going back and forth. If you can boot to fastboot screen, you can save your phone and flash anything you want.
You may wish to advise users that if they downgrade to Nougat not to use Nougat OTA updates. The reason being that a downgraded stock Oreo device may still have the Oreo bootloader on it. Thus, attempting to use Nougat OTA updates may hard brick their device (as the bootloader is likely corrupted, meaning no fastboot).
Users could either use the Feb 2018 NPN26.118-22-2-17 firmware from your link https://mirrors.lolinet.com/firmware/moto/addison/official/RETAIL/ as that was the last Nougat firmware (and thus no Nougat OTA updates) or avoid using OTA updates whilst downgraded.
echo92 said:
You may wish to advise users that if they downgrade to Nougat not to use Nougat OTA updates. The reason being that a downgraded stock Oreo device may still have the Oreo bootloader on it. Thus, attempting to use Nougat OTA updates may hard brick their device (as the bootloader is likely corrupted, meaning no fastboot).
Users could either use the Feb 2018 NPN26.118-22-2-17 firmware from your link https://mirrors.lolinet.com/firmware/moto/addison/official/RETAIL/ as that was the last Nougat firmware (and thus no Nougat OTA updates) or avoid using OTA updates whilst downgraded.
Click to expand...
Click to collapse
Interesting. I used the above GUIDE to go up and down a number of times on my phone (about 20 total) , installing and running on both 7 and 8, and then went down to a Nov 7.1.1 and let it ota all the way up to 8.0 and that is what I am using now. I found that when i used a factory zip, and the above procedure, it corrected the bootloaders to the appropriate version that i was flashing - either RSDlite or the more manual path which ignores the errors worked for me.
Using the above procedure , you get the correct bootloaders, which are in the zip.
Please correct me if i am wrong!
KrisM22 said:
Interesting. I used the above GUIDE to go up and down a number of times on my phone (about 20 total) , installing and running on both 7 and 8, and then went down to a Nov 7.1.1 and let it ota all the way up to 8.0 and that is what I am using now. I found that when i used a factory zip, and the above procedure, it corrected the bootloaders to the appropriate version that i was flashing - either RSDlite or the more manual path which ignores the errors worked for me.
Using the above procedure , you get the correct bootloaders, which are in the zip.
Please correct me if i am wrong!
Click to expand...
Click to collapse
That's intriguing - we saw previously on Z Play that users downgrading their stock firmware (e.g. https://forum.xda-developers.com/moto-z-play/help/hard-brick-moto-z-play-patch-abril-t3782927 )and then using OTA updates hard bricked their device (hence the number of users asking for a blankflash, as fastboot no longer works). I don't know if these users hard bricked by downgrading their firmware too far and then flashed an OTA radically different to their previous firmware, or whether it's a risk that's taken by any downgrading of firmware.
When you used fastboot, did you see any 'security downgrade errors' when you flashed the bootloader, and is your bootloader version now C180, as you've flashed the Oreo OTA?
echo92 said:
That's intriguing - we saw previously on Z Play that users downgrading their stock firmware (e.g. https://forum.xda-developers.com/moto-z-play/help/hard-brick-moto-z-play-patch-abril-t3782927 )and then using OTA updates hard bricked their device (hence the number of users asking for a blankflash, as fastboot no longer works). I don't know if these users hard bricked by downgrading their firmware too far and then flashed an OTA radically different to their previous firmware, or whether it's a risk that's taken by any downgrading of firmware.
When you used fastboot, did you see any 'security downgrade errors' when you flashed the bootloader, and is your bootloader version now C180, as you've flashed the Oreo OTA?
Click to expand...
Click to collapse
YES - that's why I wrote these 3 guides - before, it was quite possible to wind up with a bootloader mix - esp depending on the zip you use! - factory/stock only!!!
I added a line to the guide saying that it is only intended to be used for the factory/stock zips as these have (I believe) the bootloaders appropriate to the ROM.
Many thanks for pursuing this! - I wonder if we'll have to exclude certain ROMs that are in the factory lists?????
echo92 said:
That's intriguing - we saw previously on Z Play that users downgrading their stock firmware (e.g. https://forum.xda-developers.com/moto-z-play/help/hard-brick-moto-z-play-patch-abril-t3782927 )and then using OTA updates hard bricked their device
Click to expand...
Click to collapse
If you have TWRP (or I assume any custom recovery) present when you try to ota, it can download just fine and then reboot to the update. I had TWRP and wound up in a situation where my phone would only boot to twrp no matter what I flashed or restored. I booted phone to fastboot, RSDlite'ed that 11-09-17 factory zip and all was well. In that particular case I did not fully install 7.x but immediately RSDlite'ed rafikowy's 8.0 signed stock and went on with my testing. Since then I always boot to TWRP rather than intalling it and do my thing. (thanks @jceballos )
When you used fastboot, did you see any 'security downgrade errors' when you flashed the bootloader, and is your bootloader version now C180, as you've flashed the Oreo OTA?
Click to expand...
Click to collapse
Sorry - since it throws a million errors I never look at it if it works.
The particular build I am on at the moment - is BL: C1.82
This one started from that Nov '17 build and ota'ed all the way to 8.0 Apr.
I root and unroot as needed per rafikowy's method but using a boot to TWRP - never an install TWRP.
I'll put up a new guide ref ota and recovery and brick.
KrisM22 said:
If you have TWRP (or I assume any custom recovery) present when you try to ota, it can download just fine and then reboot to the update. I had TWRP and wound up in a situation where my phone would only boot to twrp no matter what I flashed or restored. I booted phone to fastboot, RSDlite'ed that 11-09-17 factory zip and all was well. In that particular case I did not fully install 7.x but immediately RSDlite'ed rafikowy's 8.0 signed stock and went on with my testing. Since then I always boot to TWRP rather than intalling it and do my thing. (thanks @jceballos )
Sorry - since it throws a million errors I never look at it if it works.
The particular build I am on at the moment - is BL: C1.82
This one started from that Nov '17 build and ota'ed all the way to 8.0 Apr.
I root and unroot as needed per rafikowy's method but using a boot to TWRP - never an install TWRP.
I'll put up a new guide ref ota and recovery and brick.
Click to expand...
Click to collapse
1) If you have TWRP, then using an OTA will fail - as you've not got stock recovery (and likely other modifications, including possibly a system partition set to read-write status). As you noted, having TWRP seems to cause a bootloop when rebooting - I'm not sure if the OTA sets a boot flag to stay in recovery until the update is completed. For the G4/Plus, there's a possible solution by wiping the misc partition but I don't know if there's a similar partition for Z Play devices: https://forum.xda-developers.com/moto-g4/help/troubleshooting-twrp-boot-loop-ota-t3714325
The only other solution I've seen is a clean flash of the stock ROM to get your device booting properly.
Booting to TWRP rather than flashing would mean your stock recovery is still present on your device. The only downside is if you need to make modifications, you'd need your computer to boot to TWRP.
2)BL C1.82 seems to be the bootloader provided by the Oreo April 2018 security patch update, so your device looks to be on the right bootloader. It's still curious that the Nov 2017 firmware worked whereas countless other 'factory' stock ROMs caused hard bricks when downgraded to and then OTA updates were installed.
As you mentioned, custom ROMs don't have bootloaders and thus don't care about your bootloader version usually (though I've seen some ROMs require a certain bootloader). However, stock ROMs and stock OTA updates do have bootloaders, which is why downgrading can be risky.
echo92 said:
1) If you have TWRP, then using an OTA will fail - as you've not got stock recovery (and likely other modifications, including possibly a system partition set to read-write status). As you noted, having TWRP seems to cause a bootloop when rebooting - I'm not sure if the OTA sets a boot flag to stay in recovery until the update is completed. For the G4/Plus, there's a possible solution by wiping the misc partition but I don't know if there's a similar partition for Z Play devices: https://forum.xda-developers.com/moto-g4/help/troubleshooting-twrp-boot-loop-ota-t3714325
The only other solution I've seen is a clean flash of the stock ROM to get your device booting properly.
Booting to TWRP rather than flashing would mean your stock recovery is still present on your device. The only downside is if you need to make modifications, you'd need your computer to boot to TWRP.
2)BL C1.82 seems to be the bootloader provided by the Oreo April 2018 security patch update, so your device looks to be on the right bootloader. It's still curious that the Nov 2017 firmware worked whereas countless other 'factory' stock ROMs caused hard bricks when downgraded to and then OTA updates were installed.
As you mentioned, custom ROMs don't have bootloaders and thus don't care about your bootloader version usually (though I've seen some ROMs require a certain bootloader). However, stock ROMs and stock OTA updates do have bootloaders, which is why downgrading can be risky.
Click to expand...
Click to collapse
Downgrading is a piece of cake if you don't use RSDlite - it throws an error and stops. Using the bat file it can happily throw all the errors it wants and all I care is at the end I have what I want.
It does indeed change the entire environment when you bat file the zip contents. You can bat file to get from 8 to 7 and then use RSDlite to flash a different 7 OR 8 zip file. There is no resulting difference in whether you RSDlite it or bat file it - the bat file simply comes from the .xml file that is within the zip. There is very little or no difference between that among addison factory/stock zips. Other zips are different (custom ROMs.)
Grab any factory/stock zip for addison and expand it and you will see modems, bootloaders, indeed absolutely everything you would find on that phone if you went to a store and bought it. SupahCookie simply added a couple lock command lines because it was intended for folks who somehow thought that if phone was locked they could take it back to the store and get their money back. Or some such. I found that ATT folk didn't care if you were on CM or whatever if you just needed to swap SIMs or whatever.
I DON'T want to lock the phone as it prevents me from modifying forever. Oh yeah that reminds me I was going to post the obligatory guide (again) about how to flash a white boot logo so you don't get that message - it's still there LOL but since the font is in white, you can't see it.
I have a Moto Z2 Play and used this to get out of a rather sticky situation.. My IEMI shows 0 now and I'm curious if there's a way to fix this? Also, You say you've done OTA updates? My phone is telling my I have some, is it safe to try?
Necrowr said:
I have a Moto Z2 Play and used this to get out of a rather sticky situation.. My IEMI shows 0 now and I'm curious if there's a way to fix this? Also, You say you've done OTA updates? My phone is telling my I have some, is it safe to try?
Click to expand...
Click to collapse
Thanks for feedback and great on success.
IMEI will show zero if using oreo, It will show again if using N. Remember that if you go from O to N you need to use the "Alternative to RSD" as RSD will simply throw an error and stop.
If you have TWRP and/or Magisk you must get rid of them before ota - if twrp present you will soft brick and have to do alternative again - flash a stock recovery. Simply uninstalling/flash magisk will probably not be enough - it will likely d/l but error part way through update. If you are sitting on rafikowy's stock oreo, and haven't modified it, you should be fine. I know Apr and June are out there. I flashed his stock 8.0 and took June fine. Z2 should be no different though of course I can't guarantee it
If you have success, let us know what you have done so others looking in will know. Thanks!
KrisM22 said:
Thanks for feedback and great on success.
IMEI will show zero if using oreo, It will show again if using N. Remember that if you go from O to N you need to use the "Alternative to RSD" as RSD will simply throw an error and stop.
If you have TWRP and/or Magisk you must get rid of them before ota - if twrp present you will soft brick and have to do alternative again - flash a stock recovery. Simply uninstalling/flash magisk will probably not be enough - it will likely d/l but error part way through update. If you are sitting on rafikowy's stock oreo, and haven't modified it, you should be fine. I know Apr and June are out there. I flashed his stock 8.0 and took June fine. Z2 should be no different though of course I can't guarantee it
If you have success, let us know what you have done so others looking in will know. Thanks!
Click to expand...
Click to collapse
I actually flashed to this: ALBUS_C_7.1.1_NPS26.118-24_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip Which is a 7.1.1 variant and it is showing 0 when I check settings and when I dial *#06#. However upon connecting to the computer and running mfastboot getvar imei it returned a value. I only did the steps above which would mean I don't have TWRP or Magisk (when I fastboot and click recovery I get "no command")
****** Additional information *********
XT1710-01 Duel Sim Variant
I started your steps, only being able to access fastboot. The device would throw an error (I don't recall exactly but it ended up showing me them in the bootloader logs) whenever I tried to start it, or go to recovery. #DefinitelyThoughtItWasDead
Necrowr said:
I actually flashed to this: ALBUS_C_7.1.1_NPS26.118-24_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip Which is a 7.1.1 variant and it is showing 0 when I check settings and when I dial *#06#. However upon connecting to the computer and running mfastboot getvar imei it returned a value. I only did the steps above which would mean I don't have TWRP or Magisk (when I fastboot and click recovery I get "no command")
****** Additional information *********
XT1710-01 Duel Sim Variant
I started your steps, only being able to access fastboot. The device would throw an error (I don't recall exactly but it ended up showing me them in the bootloader logs) whenever I tried to start it, or go to recovery. #DefinitelyThoughtItWasDead
Click to expand...
Click to collapse
What rom was on phone when you got it and what have you done to it? Has it ever run 8.x?
original country of phone?
The bat file will always throw a lot of slot errors.
https://mirrors.lolinet.com/firmware/moto/albus/official/RETUS/
or
https://mirrors.lolinet.com/firmware/moto/albus/official/RETAIL/
might have some stock ROMs of interest...
KrisM22 said:
What rom was on phone when you got it and what have you done to it? Has it ever run 8.x?
original country of phone?
The bat file will always throw a lot of slot errors.
might have some stock ROMs of interest...
Click to expand...
Click to collapse
It had 7.1.1 stock. I rooted it, and then flashed Resurrection Remix (which was yes 8.1 I believe) and the upgraded bootloader. I then found out my service wouldn't work with that.. so I attempted to flash back to stock which gave me a flurry of issues.. eventually getting to nothing but fastboot working. Flashed back to working with your guide to 7.1.1
If it helps in in fastboot it tells me BL: C0.CD
Necrowr said:
It had 7.1.1 stock. I rooted it, and then flashed Resurrection Remix (which was yes 8.1 I believe) and the upgraded bootloader. I then found out my service wouldn't work with that.. so I attempted to flash back to stock which gave me a flurry of issues.. eventually getting to nothing but fastboot working. Flashed back to working with your guide to 7.1.1
If it helps in in fastboot it tells me BL: C0.CD
Click to expand...
Click to collapse
Custom ROMs won't usually update the bootloader (even if they are newer) as stock ROMs typically only have the bootloader firmware.
You could look into flashing the stock Oreo albus 8.0 ROM https://forum.xda-developers.com/z2-play/how-to/fastboot-rom-oreo-retail-via-fastboot-t3786153 or the 8.0 June 2018 firmware https://forum.xda-developers.com/z2-play/how-to/fastboot-rom-albusretail8-0-0opss27-76-t3822195 but please check that firmware has been released for your device variant.
I don't know if updating your baseband to stock Oreo formally may fix your IMEI issue.
Necrowr said:
It had 7.1.1 stock. I rooted it, and then flashed Resurrection Remix (which was yes 8.1 I believe) and the upgraded bootloader. I then found out my service wouldn't work with that.. so I attempted to flash back to stock which gave me a flurry of issues.. eventually getting to nothing but fastboot working. Flashed back to working with your guide to 7.1.1
If it helps in in fastboot it tells me BL: C0.CD
Click to expand...
Click to collapse
"BL: C0.CD" even right after flashing that albus 7.1.1 using "alternative" above?
What happens if you flash one of the oreo roms from the links I gave you above?
Yeah, RR wouldn't change bootloaders... so you upgraded bootloaders independendently?- that could easily lead to a soft brick... -
I read RR on Z2 and it says nothing about bootloaders even though it says 8.1 based, so i wonder if it needs 7.x bootloaders? I did not read entire thread...
In a reverse, I would wonder if you put an 8 on there if you wouldn't see your IMEI. (On the Z if you flash 8 You won't see the IMEI until you return to 7.)(wondering if z2 is reversed)
KrisM22 said:
"BL: C0.CD" even right after flashing that albus 7.1.1 using "alternative" above?
What happens if you flash one of the oreo roms from the links I gave you above?
Yeah, RR wouldn't change bootloaders... so you upgraded bootloaders independendently?- that could easily lead to a soft brick... -
I read RR on Z2 and it says nothing about bootloaders even though it says 8.1 based, so i wonder if it needs 7.x bootloaders? I did not read entire thread...
In a reverse, I would wonder if you put an 8 on there if you wouldn't see your IMEI. (On the Z if you flash 8 You won't see the IMEI until you return to 7.)(wondering if z2 is reversed)
Click to expand...
Click to collapse
Yes, right after flashing that is the BL that fastboot is showing me. I don't recall updating the bootloader so to speak, however RR did require an updated variant of twrp which I flashed 3.2.2 I believe to get (unsure if that would have changed the bootloader or not). I also tried flashing a stock Oreo (which you've stated stock Roms usually only have the bootloaders so maybe somewhere during this process I updated it?). I wish I had all the notes for what I did to give more precise information, but I'm in a position where I really need my phone so I kinda just panicked and started flashing things when my service wouldn't work.
I'm highly considering trying to run an OTA (though very afraid of bricking). - On a side note though, it wouldn't even tell me I had OTA's until I did the steps in the original post here (doing the different 7.1.1. and 8.0 flashes, it wouldn't ever tell me I had updates, and now it does).
*** Edit ***
Looks like I'm able to enter stock recovery, which makes me believe everything is stock at the moment.
Necrowr said:
Yes, right after flashing that is the BL that fastboot is showing me. I don't recall updating the bootloader so to speak, however RR did require an updated variant of twrp which I flashed 3.2.2 I believe to get (unsure if that would have changed the bootloader or not). I also tried flashing a stock Oreo (which you've stated stock Roms usually only have the bootloaders so maybe somewhere during this process I updated it?). I wish I had all the notes for what I did to give more precise information, but I'm in a position where I really need my phone so I kinda just panicked and started flashing things when my service wouldn't work.
I'm highly considering trying to run an OTA (though very afraid of bricking). - On a side note though, it wouldn't even tell me I had OTA's until I did the steps in the original post here (doing the different 7.1.1. and 8.0 flashes, it wouldn't ever tell me I had updates, and now it does).
*** Edit ***
Looks like I'm able to enter stock recovery, which makes me believe everything is stock at the moment.
Click to expand...
Click to collapse
If you flashed a stock O that would have changed bl to O, but doing the above with the stock 7.1.1 would have changed them back to N. No matter (other than academic) that you don't remember the path - flashing a stock anything reverts it to that point in time. However, IMEI may have been moved - don't know. It will likely show on EITHER 7.x or 8.x stock - just don't know which.
If you flash a stock 8.x from those links I gave you above, it should offer you ota, ASSUMING there are any at this point in time(Z has 2). Adding Magisk at any point seems to hose you for receiving any more ota's - don't understand why, even with magisk uninstall, so that would mean going back to the latest stock and losing what you have (which is why I try to take a TBPro and copy that backup to PC (because re-flashing 8.x stock will likely reset internal storage.).
yes, if you enter stock recovery, you are likely at stock, though you could reflash the latest 7 or 8 stock to be sure, depending on which you want to use as base. Since 8 is having security fixes released, I choose 8 and will likely have no more interest (no time!) in 7.
So, ran the OTA and it was fine running the update and staying on N. I also downloaded the OTA for Oreo, when trying to update the recovery error'd out. It looked like the error said "Error in modem unexpected results" or something similar.
Necrowr said:
So, ran the OTA and it was fine running the update and staying on N. I also downloaded the OTA for Oreo, when trying to update the recovery error'd out. It looked like the error said "Error in modem unexpected results" or something similar.
Click to expand...
Click to collapse
did it offer to let you d/l it again? you could try that.
However, there exist O stock zips in those links I gave you so you could just flash the latest...
Since these tablets don't have an external online resource for downloading system updates, only a sketchy OTA app (com.adups.fota) I'm collecting a library of OTAs, as well as boot/recovery/system images.
I have access to a 10.1 with keyboard (ONA19TB007) and without (ONA19TB003) that I can pull updates and images from, but I do not have access to the 8" (ONA19TB002) or newer 7" tablet. Any assistance with those two would be welcomed :good:
Onn 10.1" without keyboard - ONA19TB003
OTA
20191015-1827
Stock Images
October 2019
Full (Thanks @CaffeinePizza!)
Boot
Recovery
VbMeta
Vendor
System
May 2019
Full (Thanks @CaffeinePizza!)
Onn 10.1" with keyboard - ONA19TB007
OTA
20191011-1212
20190516-1437
Stock Images
October 2019
Boot
Recovery
Vendor
VbMeta
System
May 2019
Boot
Recovery
Vendor
VbMeta
System
Onn 8" - ONA19TB002
OTA
November 2019 (Thanks @martyfender)
July 2019 (Thanks @tek3195)
Stock Images
November 2019
Full (Thanks @CaffeinePizza!)
May 2019
Full (Thanks @CaffeinePizza!)
Onn 7" Surf - 100005206
OTA
November 2019 (Thanks @tek3195)
Stock Images
October 2019
Full (Thanks @deadman96385!!)
June 2019
Full (Thanks @deadman96385!)
*Reserved
NFSP G35 said:
Since these tablets don't have an external online resource for downloading system updates, only a sketchy OTA app (com.adups.fota) I'm collecting a library of OTAs, as well as boot/recovery/system images.
Click to expand...
Click to collapse
I discovered that running the following command
Code:
pm uninstall -k --user 0 com.adups.fota.sysoper && pm uninstall -k --user 0 com.adups.fota
withing adb shell will disable the over the air updates.
I do not know if there is any truth to this, but Malwarebytes has an article on this, claiming that the software can be used to collect user data so I chose to disable it.
^ yep. I ran across a lot of worrysome information about that software. I figure I can 'take one for the team' and leave it enabled on mine, and collect updates here.
That way, if anyone wants to update while leaving com.adups.fota disabled or uninstalled, now they will have a way to do so
NFSP G35 said:
^ yep. I ran across a lot of worrysome information about that software. I figure I can 'take one for the team' and leave it enabled on mine, and collect updates here.
That way, if anyone wants to update while leaving com.adups.fota disabled or uninstalled, now they will have a way to do so
Click to expand...
Click to collapse
I am repeating some information I previously stated since we now have a section specifically for this:
I am sure @CaffeinePizza would not mind, he posted stock roms in this POST. Maybe a link to this information in the OP will help people looking for a STOCK rom for the 8' and 10' devices. The images he is hosting are patched to April 5, 2019. Anyone wishing to flash these images will need the SP Flash tools.
OTA for 8" ONA19TB002 https://drive.google.com/file/d/10vFETRunJEkyZXGUV05-rmJy60qrnSuy/view?usp=sharing
I can not remember date but somewhere around July 2019.
tek3195 said:
OTA for 8" ONA19TB002 https://drive.google.com/file/d/10vFETRunJEkyZXGUV05-rmJy60qrnSuy/view?usp=sharing
I can not remember date but somewhere around July 2019.
Click to expand...
Click to collapse
Thanks! Added to the OP
I guess this would be the place for the 7" SURF OTA's to reside for now ? Here is ota for Onn 7" Surf Model 100005206 downloaded 11/7/2019 have not installed yet so don't have security patch date.
https://drive.google.com/file/d/1U77dxYgO-ihbO1XP6c8AiEnEtUlJRcfI/view?usp=sharing
tek3195 said:
I guess this would be the place for the 7" SURF OTA's to reside for now ? Here is ota for Onn 7" Surf Model 100005206 downloaded 11/7/2019 have not installed yet so don't have security patch date.
https://drive.google.com/file/d/1U77dxYgO-ihbO1XP6c8AiEnEtUlJRcfI/view?usp=sharing
Click to expand...
Click to collapse
Thanks!
Added to the OP along with a couple of images from the 007.
More to come once I can get them uploaded.
Random OT... I just noticed you're in PC... Hi from Tallahassee!
Maybe we should have a thread on sptools too... I still need to read up on mtk told but there are so many...
You're welcome to reference my thread and post a link to my server with the x003 and x002 stock images. SP Flash Tools is needed.
https://forum.xda-developers.com/showpost.php?p=80574967&postcount=192
https://www.nathanbar.net/files/android
I plan on making a proper thread, perhaps this weekend, on how to backup with Wwr, and flash with SP Tools. I will try to upload updated images from the newest OTA.
I may even make a blog post with photos on my site.
Can the Onn 8 update.zip be flashed in TWRP, or must it only be flashed in spflashtool?
Thanks
UPDATE:
I tried both ways and neither works. How does one apply this update.zip? Do I need to reflash the stock recovery and apply it there?
I copied the update.zip to:
Code:
/storage/emulated/0/Android/data/com.adups.fota/files/fota
When I go to settings,system, about tablet, wireless Update, local updates, I navigate to where the update is and if I choose update.zip,: make sure the file is official, it states it may wipe your data and will reboot to recovery to install. (which I assume needs to be the stock recovery?)
I, of course do not want to do this until I hear from someone who can clarify all of this: @tek3195
Thanks
martyfender said:
Can the Onn 8 update.zip be flashed in TWRP, or must it only be flashed in spflashtool?
Thanks
UPDATE:
I tried both ways and neither works. How does one apply this update.zip? Do I need to reflash the stock recovery and apply it there?
Click to expand...
Click to collapse
To my knowledge, it has to be flashed with the stock recovery
NFSP G35 said:
To my knowledge, it has to be flashed with the stock recovery
Click to expand...
Click to collapse
Yeah, it has to be stock recovery and can be done with adb sideload or update from sdcard. I haven't tried yet but it may be able to be repacked and flashed with TWRP. I know as it sits now the compatibility.zip is of wrong format to be flashed. It's a possibility, but something that would have to be done at each update. Also, regardless of how installed will it re-lock bootloader or erase /data? Some brands do. I don't know mine was already wiped before the update.zip. Just installed it from sdcard and says success although two errors at end. loader1 & loader2 could not read misc-sd, unable to set boot part. Find out in a few if relocked.
Okay,cool. The ota when installed manually did not re-lock the bootloader.
tek3195 said:
Yeah, it has to be stock recovery and can be done with adb sideload or update from sdcard. I haven't tried yet but it may be able to be repacked and flashed with TWRP. I know as it sits now the compatibility.zip is of wrong format to be flashed. It's a possibility, but something that would have to be done at each update. Also, regardless of how installed will it re-lock bootloader or erase /data? Some brands do. I don't know mine was already wiped before the update.zip. Just installed it from sdcard and says success although two errors at end. loader1 & loader2 could not read misc-sd, unable to set boot part. Find out in a few if relocked.
Okay,cool. The ota when installed manually did not re-lock the bootloader.
Click to expand...
Click to collapse
Yes, I re-flashed the stock recovery and booted to it. I attempted to flash the update.zip from there, but there was some error that it was not and official verified file.
Keep in mind that is not what it stated, I am just relaying a very vague, poor memory version of what I saw then.
I tried to restore the just released, twrp version in fastboot in linux, but had errors, so I booted to Windows 7 and reflashed the just released version of twrp in fastboot in Windows 7 WTF? fastboot in Linux Mint Mate, has, until now, worked flawlessly.
To clarify, I could not install the ota with an unlocked bootloader and Magisk installed.
20191015 stock firmware for ONA19TB003 has been uploaded. https://www.nathanbar.net/files/android/ONA19TB003/
CaffeinePizza said:
You're welcome to reference my thread and post a link to my server with the x003 and x002 stock images. SP Flash Tools is needed.
https://forum.xda-developers.com/showpost.php?p=80574967&postcount=192
https://www.nathanbar.net/files/android
I plan on making a proper thread, perhaps this weekend, on how to backup with Wwr, and flash with SP Tools. I will try to upload updated images from the newest OTA.
I may even make a blog post with photos on my site.
Click to expand...
Click to collapse
Thanks a ton BTW, I tried to apply the October OTA on mine, and it failed because the system partition was modified (I'm sure I was doing some silly experiment)
Worse yet, the wifi stopped working for some reason... So I grabbed the backup from your server, dd'd the system image over mine, and the OTA was able to apply without a problem. Wifi started acting right again too.
I'm adding links to the OP now.
Thanks again!
NFSP G35 said:
Thanks a ton BTW, I tried to apply the October OTA on mine, and it failed because the system partition was modified (I'm sure I was doing some silly experiment)
Worse yet, the wifi stopped working for some reason... So I grabbed the backup from your server, dd'd the system image over mine, and the OTA was able to apply without a problem. Wifi started acting right again too.
I'm adding links to the OP now.
Thanks again!
Click to expand...
Click to collapse
MD5 hashes are also uploaded with DOS CRLF since I uploaded them from Windows (in the same directory as the zips on the server). Note: MD5SUM should be used only to verify that a file is not corrupt during transfer.
10"
af2e056b8b929540b3030f7dcbf07c1a stock_20190516_pie.zip
d5c6c4f8f1ea21bf18d2ee0fcb1e6335 stock_ONA19TB003_20191015.zip
8"
2244d235325b22a8a7225a736fbafaf6 stock_ONA19TB002_20190516.zip
Also, I know the 7" tablet exists now, and I have yet to purchase one. I do know, however, that it is not part of the same family. Technically (though I haven't tried it), the stock images between the 8" and 10" are exactly the same besides the ITEMS partition (items.ini).
Just got done adding boot, recovery, vbmeta, vendor and system images for the October updates on both the ONA19TB003 and ONA19TB007
Hi team, I've been searching these forums all day and not able to find a good tutorial on how to return to Amazon Stock on my 8th Gen Fire 8" tablet.
I previously had Lineage 14 on it, but decided to go back to Stock and running into some issues:
- I have the 8th gen firmware downloaded
- When I set TWRP into "adb sideload" mode and run the command on my PC, I get "E1001: Failed to update system image."
- I tried to investigate the message in the update script, but not able to decipher the code
- I also tried Lineage 17, but it wouldn't get past the loading screen
- At this point, I just want to go back to stock
Can someone point me in the right direction? My goal is to get back to stock and use the Amazon Toolbox.
Thank you for your help!
Download the stock firmware (OS6, NOT OS7) change the file extension to '.zip' (from '.bin'), copy to a micro SD card and insert into the SD card slot on the tablet. Boot into TWRP and do an advanced wipe (clear system, data and cache/ dalvik). Use the 'install' option to flash the firmware zip. Reboot and follow the on-screen instructions.
MontysEvilTwin said:
Download the stock firmware (OS6, NOT OS7) change the file extension to '.zip' (from '.bin'), copy to a micro SD card and insert into the SD card slot on the tablet. Boot into TWRP and do an advanced wipe (clear system, data and cache/ dalvik). Use the 'install' option to flash the firmware zip. Reboot and follow the on-screen instructions.
Click to expand...
Click to collapse
I appreciate your response, MontysEvilTwin. You mentioned OS6, but I don't see OS6 on the Amazon Firmware site (https://www.amazon.com/gp/help/customer/display.html?nodeId=G2JXLC4L34GX73TE).
It shows Fire HD 8 (8th Generation) FireOS 7| FireOS 7.3.1.5. Previously I had Lineage (karnak) on there which would indicate the 8th gen... these tablets don't have an SD card slot, but I understand your point.
I spent 8+ hours yesterday googling and flashing, so I'm reluctant to go down this path unless it's proven. Let me know if you have a FireHD8 2018 model and got this to work successfully.
In the meanwhile, I was able to load Lineage 16 w/o issues.
msangapu said:
I appreciate your response, MontysEvilTwin. You mentioned OS6, but I don't see OS6 on the Amazon Firmware site (https://www.amazon.com/gp/help/customer/display.html?nodeId=G2JXLC4L34GX73TE).
It shows Fire HD 8 (8th Generation) FireOS 7| FireOS 7.3.1.5. Previously I had Lineage (karnak) on there which would indicate the 8th gen... these tablets don't have an SD card slot, but I understand your point.
I spent 8+ hours yesterday googling and flashing, so I'm reluctant to go down this path unless it's proven. Let me know if you have a FireHD8 2018 model and got this to work successfully.
In the meanwhile, I was able to load Lineage 16 w/o issues.
Click to expand...
Click to collapse
The HD 8 (8th generation) does have a micro SD slot, it is on the right hand side, on the edge just below the camera. You can install the OS software from internal memory if you wish, now that you have an OS installed to copy the update to internal memory.
If you try and load OS 7 with TWRP/ unlocked bootloader you will get a bootloop that you can only get out of it you disconnect the battery or allow it to go flat. You can upgrade OS6 to OS7 but you will need to fully revert to stock first: i.e. standard Android recovery, locked bootloader and unpatched boot image.
I have three Karnak tablets, one running OS6, one running OS7 and one running Lineage 16.0.
Link to OS 6.3.1.5 for Karnak: https://fireos-tablet-src.s3.amazonaws.com/eI3UXiCdWfm4l9xcFS5U61gf6a/update-kindle-Fire_HD8_8th_Gen-NS6315_user_2504_0003658074244.bin
MontysEvilTwin said:
The HD 8 (8th generation) does have a micro SD slot, it is on the right hand side, on the edge just below the camera. You can install the OS software from internal memory if you wish, now that you have an OS installed to copy the update to internal memory.
If you try and load OS 7 with TWRP/ unlocked bootloader you will get a bootloop that you can only get out of it you disconnect the battery or allow it to go flat. You can upgrade OS6 to OS7 but you will need to fully revert to stock first: i.e. standard Android recovery, locked bootloader and unpatched boot image.
I have three Karnak tablets, one running OS6, one running OS7 and one running Lineage 16.0.
Link to OS 6.3.1.5 for Karnak: https://fireos-tablet-src.s3.amazonaws.com/eI3UXiCdWfm4l9xcFS5U61gf6a/update-kindle-Fire_HD8_8th_Gen-NS6315_user_2504_0003658074244.bin
Click to expand...
Click to collapse
You're right about the SD slot. I located it. We had it in a case which didn't have an opening over the slot, so I never knew it existed *face palm*
Okay, so I'll attempt to get back to Stock Firmware. Thank you for your detailed response. Will update with results.
MontysEvilTwin said:
The HD 8 (8th generation) does have a micro SD slot, it is on the right hand side, on the edge just below the camera. You can install the OS software from internal memory if you wish, now that you have an OS installed to copy the update to internal memory.
If you try and load OS 7 with TWRP/ unlocked bootloader you will get a bootloop that you can only get out of it you disconnect the battery or allow it to go flat. You can upgrade OS6 to OS7 but you will need to fully revert to stock first: i.e. standard Android recovery, locked bootloader and unpatched boot image.
I have three Karnak tablets, one running OS6, one running OS7 and one running Lineage 16.0.
Link to OS 6.3.1.5 for Karnak: https://fireos-tablet-src.s3.amazonaws.com/eI3UXiCdWfm4l9xcFS5U61gf6a/update-kindle-Fire_HD8_8th_Gen-NS6315_user_2504_0003658074244.bin
Click to expand...
Click to collapse
Same message as before... E1001: Failed to update system image... Updater process ended with ERROR: 7
Follow-up, after more Googling (AKA scientific research these days) a random post recommended updating TWRP to the latest. Then after more Googling, I found a post with TWRP 3.3.1 for karnak. Of course it would be much easier to list this on the TWRP web site, but then it would be too easy and I'd miss my opportunity to get more grey hair. So right now something is installing...
MontysEvilTwin said:
The HD 8 (8th generation) does have a micro SD slot, it is on the right hand side, on the edge just below the camera. You can install the OS software from internal memory if you wish, now that you have an OS installed to copy the update to internal memory.
If you try and load OS 7 with TWRP/ unlocked bootloader you will get a bootloop that you can only get out of it you disconnect the battery or allow it to go flat. You can upgrade OS6 to OS7 but you will need to fully revert to stock first: i.e. standard Android recovery, locked bootloader and unpatched boot image.
I have three Karnak tablets, one running OS6, one running OS7 and one running Lineage 16.0.
Link to OS 6.3.1.5 for Karnak: https://fireos-tablet-src.s3.amazonaws.com/eI3UXiCdWfm4l9xcFS5U61gf6a/update-kindle-Fire_HD8_8th_Gen-NS6315_user_2504_0003658074244.bin
Click to expand...
Click to collapse
I'm able to use OS6 successfully and also Amazon Toolbox. I noticed in the system update that it's ready to upgrade to OS7. Given your warnings of bootloops, it's not something that I want to do. Is there a way to disable auto-update? Or a guide to get it back to full stock? I mainly need this for my kids to be able to watch/download Netflix. What do you suggest?
Hi, ill read your comments here, and im looking for some help, i got a Fire HD 8 "Amarok" and i went in Lineage OS, but then ill revert to Stock Firmware 6, and after that ill update to 7, and now im stuck in Bootloop, the problem is i cant get in to TWRM or even Recovery Mode. Any help on this?
MontysEvilTwin said:
The HD 8 (8th generation) does have a micro SD slot, it is on the right hand side, on the edge just below the camera. You can install the OS software from internal memory if you wish, now that you have an OS installed to copy the update to internal memory.
If you try and load OS 7 with TWRP/ unlocked bootloader you will get a bootloop that you can only get out of it you disconnect the battery or allow it to go flat. You can upgrade OS6 to OS7 but you will need to fully revert to stock first: i.e. standard Android recovery, locked bootloader and unpatched boot image.
I have three Karnak tablets, one running OS6, one running OS7 and one running Lineage 16.0.
Link to OS 6.3.1.5 for Karnak: https://fireos-tablet-src.s3.amazon...D8_8th_Gen-NS6315_user_2504_0003658074244.bin
Click to expand...
Click to collapse
Thank you for the simplified explanation - I'm trying to get back to a totally stock 2018 HD 8. I'm able to restore using the OS6 image file, but it gets stuck in a bootloop after doing an autoupdate to OS7. Removing the battery allows it to stop, but it simply jumps back into a bootloop once started. Is this because it has a modified bootloader/recovery? What is the easiest way to fix this so that It can update and run OS7
Hi,
Lost root access after updating my OnePlus 6T to Android 11 a few days back, hence decided to flash magisk_patched image that I had created around 2 months back. Phone didn't like it ofcourse and gave me a QualComm Crash Dump error.
After searching, managed to boot into bootloader, however wondering how do I now boot my phone - I have downloaded and installed latest recovery (3.5.2_9.0-fajita.img) and am able to boot into recovery as well as bootloader/ fastboot.
Have also downloaded the zip file for Android 11 stable version - OnePlus6TOxygen_34.J.60_OTA_0600_all_2108052232_8c516d0cce8795.zip
Question - What do I need to flash this? adb commands don't seem to be working, only fastboot commands seem to. Can I just "push" this zip file in fastboot or is that only for img files?
Any help woud be massively appreciated!
The update to 11 does not agree with Magisk which causes it to either fail to complete the update or to die at early boot depending on how bad things were messed up. You can reapply root once the update to 11 is finished though, so you can still have root.
In your case manually upgrading to 11, letting it finish the upgrade, and then installing Magisk again is your best bet, in which case you would either have to find something that understands the update format or manually extract the updated partitions from the payload, iirc
Extracted boot.img and used fastboot command : fastboot boot boot.img, but this doesn't seem to have worked as well. Just thinking aloud what else can be done?
Edit - It now tries to boot, but then seems to go into OnePlus Recovery (from the chinese characters displayed along with an option to choose English language)
sam_htc_touch said:
Have also downloaded the zip file for Android 11 stable version - OnePlus6TOxygen_34.J.60_OTA_0600_all_2108052232_8c516d0cce8795.zip
Question - What do I need to flash this? adb commands don't seem to be working, only fastboot commands seem to. Can I just "push" this zip file in fastboot or is that only for img files?
Click to expand...
Click to collapse
Masamune3210 said:
The update to 11 does not agree with Magisk which causes it to either fail to complete the update or to die at early boot depending on how bad things were messed up. You can reapply root once the update to 11 is finished though, so you can still have root.
In your case manually upgrading to 11, letting it finish the upgrade, and then installing Magisk again is your best bet, in which case you would either have to find something that understands the update format or manually extract the updated partitions from the payload, iirc
Click to expand...
Click to collapse
Hi, thanks for responding. I am not even concerned about root right now, just want my phone to boot up first Any suggestions on what can I try?
sam_htc_touch said:
Hi, thanks for responding. I am not even concerned about root right now, just want my phone to boot up first Any suggestions on what can I try?
Click to expand...
Click to collapse
For the benefit of others, all sorted finally y'day evening. Plenty of helpful tips in this thread
(Well I was able to boot into Android 11.1.1.1 - no root as yet, but I will perhaps look into that later, can't stand those annoying ads :-D )