Related
HOW TO UNROOT (ALMOST) ALL ANDROID DEVICES (SIMPLIFIED)
Firstly, in order to unroot your android device, you need:
1) An update available for your phone or an old nandroid backup that has a previous version of your phone android version
2) A nandroid backup done before you attempt the following steps below
Once the above conditions are met, you are ready to UNROOT your phone!
Before you read the procedure, read how it works
below and get a better picture:
HOW
Firstly, one known method of unrooting is to install an available system update. However, stock updates are signed with official keys and custom recoveries only accept updates signed with their custom keys.
So, to unroot, you need to have stock recovery installed. One way to get your phone`s stock recovery back is contained in the update zip.
The update zip is the key, literally. Look through it and you will find (usually in the system folder) a file called recovery.img, which will be used as your new stock recovery.
By flashing in the image into recovery, you can now install updates, keep your previous applications, enjoy being unrooted and updated.
There are other unroot options that tailor to specific android phones and versions, but this solution should work on all android phones.
Why unroot? Because sending in a rooted phone for repair will void your warranty. Also, by having a rooted phone, you run the risk of a rogue rooted application that does unwanted stuff to your phone.
PROCEDURE
Step 1) If you still have your original stock recovery that came with your phone, continue. Else search for my previous thread: "[RECOVERY] Reverting to original(STOCK) recovery" and follow the steps there. You can use the update file you used to revert to stock recovery here as well or vice versa
Step 2) Reboot you phone
Step 3) Check for system updates and download them
Step 4) Wait until phone reboots. All your applications and user settings will be retained.
Step 5a) Open up a terminal emulator on your phone and enter "su" (Check if unroot)
Step 5b) If you cant turn your phone on to check if unrooted, boot into recovery mode, open up adb enter:
Code:
adb shell
su
Step 6) If you get "permission denied" or something like that from step 5a/5b,
CONGRATULATIONS! YOUR PHONE HAS BEEN SUCCESSFULLY UNROOTED!
Step 7) If you don`t want to void your warranty, you should unistall applications that require root, especially Superuser
To date, I have rooted and unrooted my phone (Backflip) 3 times without any problems. In case your phone can`t be booted up, only to the bootloader or recovery, DO NOT WORRY! You can use the adb (android debug bridge) to flash in the stock recovery, push/pull the updates and reboot the phone into recovery mode or normal mode!!!
Useful ADB commands
Reboot Phone
Code:
adb shell
reboot
Reboot Phone into recovery mode
Code:
adb shell
reboot recovery
Flash a new recovery image temporarily (resets when rebooting)
Code:
adb shell
flash_image recovery /sdcard/recovery.img
Flash a new recovery image that does not reset when rebooting
Code:
adb shell
flash_image recovery /sdcard/recovery.img
exit
adb shell
cd system
su
mount -o rw,remount /dev/block/mtdblock1 /system
rm recovery.img
mount -o ro,remount /dev/block/mtdblock1 /system
exit
exit
Push file to sdcard
Code:
adb push file.blah /sdcard/file.blah
Push file to sdcard
Code:
adb pull /sdcard/file.blah file.blah
Here`s wishing you good luck and a belated happy new year!
Err.. Pretty cool info there but what if you don't meet above three requirements? I mean there are noobs like me who'd rather jump onto flashing while forgetting about nandroids etc. I guess there should be a one click unroot utility for all android devices like we have for rooting.
im really confused.
if the phone has been rooted (using fastboot oemunlock - yes) then how can we "unroot" this device? till today there has not been a way to do so.
but if what ur suggesting relocks the bootloader (removes the cross at bootup) then woohoo!
The main point
ok, i think you guys dont understand what my point on unrooting is...
What im trying to say is:
Updating your phone software with an original OTA update on the original rom the came with your phone will automatically reset root. However, custom roms and recoveries dont accept OTA updates, so you need to flash back your original recovery first, nevermind if you have a custom rom.
If you don`t meet the requirements, then i`m sorry, you`ll just have to wait for an available system update like me. However if you get one, be sure to come back here if you want to unroot.
Creating a one/two click-unroot application
Actually, you may be right. The unroot procedures can also be carried out by adb alone , not by user interaction. So a desktop application can be created that automates the process
1) Open adb shell
2) Enter su
3) Pull the update zip from the phone
4) Recursive/y search the zip for the file recovery.img
5) Run 'flash_image recovery recovery.img'
6) Run 'adb reboot' to reboot phone
7) Phone will install update on stock update when rebooting complete
8) When update installed, root will be removed and your phone will be updated as well!
We can send keystrokes to the adb for the adb shell.
siidheesh said:
Actually, you may be right. The unroot procedures can also be carried out by adb alone , not by user interaction. So a desktop application can be created that automates the process
1) Open adb shell
2) Enter su
3) Pull the update zip from the phone
4) Recursive/y search the zip for the file recovery.img
5) Run 'flash_image recovery recovery.img'
6) Run 'adb reboot' to reboot phone
7) Phone will install update on stock update when rebooting complete
8) When update installed, root will be removed and your phone will be updated as well!
We can send keystrokes to the adb for the adb shell.
Click to expand...
Click to collapse
Shouldn't be too hard, probably only a simple script would suffice I'll see what I can come up with (if I can do anything ). Supply the script with your required update zip to make it work in a different way (maybe, I'm not great with details)
Automated Script
Can someone please clarify that this would work (as an unroot script):
1. Opens ADB shell
2. Enters su
3. (User) Supply script with stock update.zip - in case it's not on phone (correct if this is unnecessary)
4. recovery.img extracted from update.zip
5. recovery.img flashed to phone via 'flash_image recovery recovery.img'
6. Reboots phone via 'adb reboot'
That installs stock recovery, but what if there was no OTA update to install for that particular device? That's the only problem I can see with such a script, so I'm hesitant to make it right now (besides, I don't have my Nexus with me at the moment, so I couldn't test it).
Dumb question but would flashing a stock update.zip from the stock recovery remove root? Or does it have to be OTA? Never having done it before I'm not sure.
Edit: If it did have to be OTA, maybe you could find the original update.zip (ie. no updates before it) and flash that, so there would be a higher chance of an OTA update?
Different definitions
Sorry people, when i mean ota update, i dont just over-the-air updates, i am referring to original updates for your original android system that came with your phone.
siidheesh said:
Sorry people, when i mean ota update, i dont just over-the-air updates, i am referring to original updates for your original android system that came with your phone.
Click to expand...
Click to collapse
So just to clarify, you could install any stock ROM for your device and it would remove root? Specifically if it was installed through stock recovery.
Thanks, hopefully I might be able to make some progress after this
not as easy as it seems
jonathongrigg said:
Can someone please clarify that this would work (as an unroot script):
1. Opens ADB shell
2. Enters su
3. (User) Supply script with stock update.zip - in case it's not on phone (correct if this is unnecessary)
4. recovery.img extracted from update.zip
5. recovery.img flashed to phone via 'flash_image recovery recovery.img'
6. Reboots phone via 'adb reboot'
That installs stock recovery, but what if there was no OTA update to install for that particular device? That's the only problem I can see with such a script, so I'm hesitant to make it right now (besides, I don't have my Nexus with me at the moment, so I couldn't test it).
Dumb question but would flashing a stock update.zip from the stock recovery remove root? Or does it have to be OTA? Never having done it before I'm not sure.
Edit: If it did have to be OTA, maybe you could find the original update.zip (ie. no updates before it) and flash that, so there would be a higher chance of an OTA update?
Click to expand...
Click to collapse
You cant make an unroot script that easily. Im halfway working on a .net application that does it on desktop.
Also, almost all great things come with a *catch*. In this case, you need to wait for an ota update to be available. Or if you took a nandroid backup some time back and updated your version, you can revert back to the old verison and update again.
siidheesh said:
You cant make an unroot script that easily. Im halfway working on a .net application that does it on desktop.
Also, almost all great things come with a *catch*. In this case, you need to wait for an ota update to be available. Or if you took a nandroid backup some time back and updated your version, you can revert back to the old verison and update again.
Click to expand...
Click to collapse
Oh well, I didn't realise I figured you could do it all from the command line, so a script of some kind might do. That said I wasn't entirely sure as I couldn't test the theory (no phone )
siidheesh said:
In this case, you need to wait for an ota update to be available. Or if you took a nandroid backup some time back and updated your version, you can revert back to the old verison and update again.
Click to expand...
Click to collapse
Another win for stock Android phones No waiting months for OTA updates! Well good luck on your .NET application, I only know Java and Python, so I can't really help you there, sorry.
dont know
my phone (Backflip) isnt a very popular phone and there`s only one rom for it. to date, i`be only tried unrooting via stock updating. Stock roms may work too, but im not sure...
adb shell
jonathongrigg said:
Oh well, I didn't realise I figured you could do it all from the command line, so a script of some kind might do. That said I wasn't entirely sure as I couldn't test the theory (no phone )
Click to expand...
Click to collapse
actually, i did mention that the unroot procedure can be done entirely from the adb shell, which is also in command line. im just making a program to enter those lines in automatically. normal batch scripts cant write to the adb shell as it is a separate shell in the command prompt...
What about doing a factory reset?
hi, would these unroot methods still work on the new updated highly secured samsung galaxy s2?
because i got the phone simlocked hoping to unlock it for t-mobile so rooted the phone but it was been unsuccessful at taking the sim lock off, so i wanted to make sure that this will still work on this phone.
Also after unroot i assume the yellow triangle will disappear, right?
oh yea thanks for replies and help in advance. Love the site
total noob here, I rooted my tab awhile bk, now needs warranty. I used 'superoneclick', but didnt backup anything first that i know of. U mention nandroid backup, update available for my phone, where do I get that, and how? Embarrassed I know nothing about these terms, trying to learn. Could u help me, please?
where can I find the recovery.img?
thanks
Does this work on all roots?
Hey all,
I recently decided to root my Incredible S and install the new release of Cyanogenmod 7 for the device. Achieving S-OFF and installing Clockworkmod went without a hitch. However, I remain unable to flash the radio, even after closely following the guide on the cyanogenmod wiki. When I attempt to use
adb with the following command
adb push PG32IMG.zip /sdcard/PG32IMG.zip
the console returns a cannot stat PG32IMG.zip: no such file or directory. When I try to unzip the file through Clockworkmod, it simply fails with an installation aborted. What can I do to remedy this?
My Incredible s is with Virgin Mobile, the radio i'm attempting to flash is 38.02.01.11
Thanks!
UPDATE Well, I took the plunge and installed the mod without flashing the radio. Everything is working except I have no volume in calls. Data, SMS/MMS work just fine. Is this a radio issue? I read that older radios may have this issue, but when I downloaded the recommended radio, I'm still unable to flash it.
Just a bump for the new issue...
Yes, the no audio during calls is a radio issue.
When you're in the terminal, make sure you're in the same directory as the file location before issuing the following command:
adb push PG32IMG.zip /sdcard/PG32IMG.zip
Useful guide: http://forum.xda-developers.com/showthread.php?t=1129014
Any idea what the right radio to use for a Virgin Mobile/Bell Canada user? I tried the "recommended" one (from the guide on the xda forum) , and when I try to install the update via the bootloader, I get a "Model ID incorrect" and an "Update Failed" error. I don't wanna mess up the SMS/Data functions with the wrong radio.
http://droid.neolobster.com/roms/PG32IMG_vivo_radio_3805.04.03.22_M.zip
MD5sum: dd73eafe12010e19e753ea831653a460
I currently have a Bell HTC Incredible S and the "recommended radio" works fine for me.
gu1dry said:
How to Flash:
In order for this to work, the HTC Incredible S needs to be S-OFF. Flashing the radio with a corrupt file or interrupting the flash, can brick the device, please proceed with caution.
Download the your choice of radio for the HTC Incredible S.
Make sure the filename is PG32IMG.zip exactly or it will not work and copy it to the same folder as adb (the /platform-tools folder within the Android SDK folder).
Connect the HTC Incredible S to the computer via USB.
On the computer, open terminal and run the following commands:
Code:
adb push PG32IMG.zip /sdcard/PG32IMG.zip
adb shell md5sum /sdcard/PG32IMG.zip
NOTE: The md5 should match up the provide the original download location. If not, redownload & try again.
Code:
adb reboot bootloader
The HTC Incredible S will reboot & usually boot into fastboot. Pressing the Power button will put the device into the bootloader.
The bootloader will scan for the radio update. Once it finds the update, select Yes.
Allow the bootloader to finish flashing the updated radio, and reboot the HTC Incredible S normally.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1129014
Turns out there was another PG32IMG hiding out on the sd card, that was probably what was confusing it. Works great now, thanks to everyone for the help!
I do have a Virgin HTC IS (virtually, idem toa bell one).
The recommended radio installs well on my device, but it does not wrok properly - no voice during in/out calls!
By the way, have you updated the divece to gingerbread 2.3.x? If yes and it it works well, do you mind to let me know which one you have installed ?
Thanks
Hello, all. First thread here on Xda, so I apologize if I missed something.
I own a myTouch 4g 2.3.4 and use an Ubuntu 11.04 desktop. I have the official SDK and ADB installed.
I'm looking to root my myTouch 4g and understand that as of now there is no method available for devices running 2.3.4... This means I need to downgrade in order to root... I've searched and searched and searched but am unable to find any guides on downgrading for those who use Linux.
wiki[dot]cyanogenmod[dot]com/wiki/HTC_Glacier:_Full_Update_Guide
I reviewed the above guide but was faced with quite a few programs in the rooting process that are available only for Windows.
Any help?
Looking to use Cyanogen as my rom, and therefore need to be running Android version 1.17.531.2
Okay, due to me being a noob I quickly discovered after more research that the platform is not a matter of concern when using the guide above.
HOWEVER...
I have a new problem...
Towards the bottom of the first section (this part
"Now that misc version has been downgraded, the HTC Glacier is ready to have the firmware downgraded. On the computer, open terminal and run the following commands:
adb push PD15IMG.zip /sdcard/PD15IMG.zip
adb shell md5sum /sdcard/PD15IMG.zip
NOTE: The md5 should match up the provide the original download location. If not, redownload & try again.
adb reboot bootloader
Use Volume up/down keys on the HTC Glacier for navigation and Power key for confirmation. Select Fastboot to flash the 1.17.531.2 firmware.
Once finished you can can continue to the next section.
I get an error when performing the following command:
adb shell md5sum /sdcard/PD15IMG.zip
md5sum: not found
Any help?
I found out the issue with the ADB environment & was able to finish off s-off , firmware upgrade & move to CleanRom 7 since yesterday and it is looking good.
For the masses, if it is of any interest. These are the steps I followed.
Pre-Requsite for S-OFF : Unlocked bootloader, Rooted etc.
a. Download the ADK (Android Dev Kit) ~470MB (This was the only option which worked for me)
b. Extract & copy the folder platform-tools to C:\ as android
c. Set the environment path to point to this folder. This would resolve all your *device not found* errors while running ADB.
If not, then
1. Remove all HTC drivers & sync software
2. Run a registry cleaner like Ccleaner to remove any leftout entries.
3. Download & run the latest HTC sync software.
4. Once Install has completed, connect your phone & switch on USB debugging. The PC would recognize the phone & install most drivers.
5. Fire up a CMD window in the Android folder & run "adb devices". If you see your phone listed, you're good to go.
Else,
6. Reboot the phone to bootloader & give it a wait. It should install the Android phone 1.0 device driver.
7. Boot the phone to Android & wait for system to install all drivers once more.
8. Run the command in step 5 again to verify that system recognizes your device.
If the above steps work, go ahead and s-off your phone. Then do the firmware upgrade if you wish & you should be able to run any ROM without issues.
Don't execute any steps while flashing ROMs if you don't see your device through ADB or don't understand what the step means :fingers-crossed:
Click to expand...
Click to collapse
Read this whole guide before starting.
This is for the 8th gen Fire HD8 (karnak).
Current version: amonet-karnak-v3.0.1.zip
This is based on @xyz`s original work, but adds some features such as reboot to hacked BL.
It also intends to simplify the installation process.
If you are already unlocked you can simply update by flashing the ZIP-file in TWRP.
NOTE: If you are on a firmware lower than 6.3.1.2 this process does not require you to open your device, but should something go horribly wrong, be prepared to do so.
What you need:
A Linux installation or live-system
A micro-USB cable
Install python3, PySerial, adb, fastboot dos2unix. For Debian/Ubuntu something like this should work:
Code:
sudo apt update
sudo add-apt-repository universe
sudo apt install python3 python3-serial adb fastboot dos2unix
1. Extract the attached zip-file "amonet-karnak-v3.0.1.zip" and open a terminal in that directory.
NOTE: If you are already rooted, continue with the next step, otherwise get mtk-su by @diplomatic from here and place (the unpacked binary) into amonet/bin folder
2. Enable ADB in Developer Settings
3. Start the script:
Code:
sudo ./fireos-step.sh
NOTE: If you are on a firmware newer than 6.3.0.1, a downgrade is necessary, this requires bricking the device temporarily. (The screen won't come on at all)
WARNING: There have been numerous reports that would indicate a hardware-change that doesn't allow access to the bootrom.
When bricking these devices there is currently no known way to unbrick.
This makes the hardware-method currently the safest option.
To brick firmware 6.3.1.2 use the attached brick-karnak.zip, boot into fastboot
Code:
adb reboot bootloader
and run
Code:
./brick-6312.sh
Make sure ModemManager is disabled or uninstalled:
Code:
sudo systemctl stop ModemManager
sudo systemctl disable ModemManager
After you have confirmed the bricking by typing "YES", you will need disconnect the device and run
Code:
sudo ./bootrom-step.sh
Then plug the device back in.
The device will reboot into TWRP.
You can now install Magisk from there.
Going back to stock
Extract the attached zip-file "amonet-karnak-return-to-stock.zip" into the same folder where you extracted "amonet-karnak-v3.0.1.zip" and open a terminal in that directory.
Then run:
Code:
sudo ./return-to-stock.sh
Your device should reboot into Amazon Recovery. Use adb sideload to install stock image from there. (Make sure to use FireOS 6.3.0.0 or newer, otherwise you may brick your device)
Important information
Don't flash boot/recovery images from FireOS (FlashFire, MagiskManager etc.)
TWRP will prevent updates from overwriting LK/Preloader/TZ, so generally installing an update should work without issues (only full updates, incremental updates won't work).
For ROM developers there is still an option to overwrite these, which should only be done after thorough testing and if needed (LK should never be updated).
It is still advised to disable OTA.
Very special thanks to @xyz` for making all this possible and putting up with the countless questions I have asked, helping me finish this.
Special thanks also to @diplomatic for his wonderfull mtk-su, allowing you to unlock without opening the device.
Thanks to @Kaijones23 for testing.
Unbricking / Unlocking with Firmware 6.3.1.2+
If Recovery OR FireOS are still accessible (or your firmware is below 6.3.1.2) there are other means of recovery, don't continue.
If your device shows one of the following symptoms:
It doesn't show any life (screen stays dark)
You see the white amazon logo, but cannot access Recovery or FireOS.
If you have a Type 1 brick, you may not have to open the device, if your device comes up in bootrom-mode (See Checking USB connection below).
Make sure the device is powered off, by holding the power-button for 20+ seconds
Start bootrom-step.sh
Plug in USB
In all other cases you will have to open the device.
Make sure ModemManager is disabled or uninstalled:
Code:
sudo systemctl stop ModemManager
sudo systemctl disable ModemManager
NOTE: If you have issues running the scripts, you might have to run them using sudo.
Also try using different USB-ports (preferably USB-2.0-ports)
Open the device and short the pin marked in the attached photo to ground while plugging in.
1. Extract the attached zip-file "amonet-karnak-v3.0.zip" and open a terminal in that directory.
2. start the script:
Code:
sudo ./bootrom-step.sh
It should now say Waiting for bootrom.
3. Short the device according to the attached photo and plug it in.
4. When the script asks you to remove the short, remove the short and press enter.
5. Wait for the script to finish.
If it stalls at some point, stop it and restart the process from step 2.
6. Your device should now reboot into unlocked fastboot state.
7. Run
Code:
sudo ./fastboot-step.sh
8. Wait for the device to reboot into TWRP.
9. Use TWRP to flash custom ROM, Magisk or SuperSU
Checking USB connection
In lsusb the boot-rom shows up as:
Code:
Bus 002 Device 013: ID [b]0e8d:0003[/b] MediaTek Inc. MT6227 phone
If it shows up as:
Code:
Bus 002 Device 014: ID [b]0e8d:2000[/b] MediaTek Inc. MT65xx Preloader
instead, you are in preloader-mode, try again.
dmesg lists the correct device as:
Code:
[ 6383.962057] usb 2-2: New USB device found, idVendor=[b]0e8d[/b], idProduct=[b]0003[/b], bcdDevice= 1.00
Reserved #2
Reserved #3
This is very cool @k4y0z!
Now we can use boot-recovery.sh & boot-fastboot no?
Regards!
Rortiz2 said:
This is very cool @k4y0z!
Now we can use boot-recovery.sh & boot-fastboot no?
Regards!
Click to expand...
Click to collapse
Yes, that is also supported.
k4y0z said:
NOTE: If you are on a firmware lower than 6.3.1.2 this process does not require you to open your device, but should something go horribly wrong, be prepared to do so.
NOTE: If you are on a firmware newer than 6.3.0.1, a downgrade is necessary, this requires bricking the device temporarily. (The screen won't come on at all)[/COLOR]
Click to expand...
Click to collapse
So do you need to open the case to run this exploit on the newest firmware, or can you just brick to install older lk/preloader, and go from there?
Kctucka said:
So do you need to open the case to run this exploit on the newest firmware, or can you just brick to install older lk/preloader, and go from there?
Click to expand...
Click to collapse
On 6.3.1.2 mtk-su has been fixed, so unless you already have root (or another way to get temp-root is found), bricking isn't an option and you will have to open the case.
If you do have root the script will do the bricking for you.
@k4y0z For people who already used the steps in xyz's thread and are running your TWRP and LineageOS, is there anything here that we're missing? Or is this just a new method to arrive at the same results?
jibgilmon said:
@k4y0z For people who already used the steps in xyz's thread and are running your TWRP and LineageOS, is there anything here that we're missing? Or is this just a new method to arrive at the same results?
Click to expand...
Click to collapse
k4y0z said:
This is based on @xyz`s original work, but adds some features such as reboot to hacked BL.
It also intends to simplify the installation process.
If you are already unlocked you can simply update by flashing the ZIP-file in TWRP.
Click to expand...
Click to collapse
Additionally it adds support for the boot-recovery and boot-fastboot scripts.
And a script to enable UART output for the kernel.
So nothing essential if you are already using the updated TWRP.
Ran this pup on a unit that I was keeping unrooted (aside from occational temp root via mtk-su) as a control but was becoming painful to use/maintain. Also missed TWRP. Worked like a champ with zero issues ... aside from stumbling over my own stupidity. Used Lubuntu live 18.04 and Magisk 19.3/7.3.2. Staying on FireOS 6.3.0.1 (w/hijacks) for now until a fully vetted custom ROM becomes available.
Thanks for the great tool and accompanying guidance.
I have added unbricking/bootrom instructions in Post #2
@k4y0z
If I flash your zip, can I then flash Amazon update as is? Will your TWRP manage the bootloaders/etc when flashing the stock ROM?
bibikalka said:
@k4y0z
If I flash your zip, can I then flash Amazon update as is? Will your TWRP manage the bootloaders/etc when flashing the stock ROM?
Click to expand...
Click to collapse
I think yeah:
TWRP will prevent updates from overwriting LK/Preloader/TZ, so generally installing an update should work without issues (only full updates, incremental updates won't work).
Click to expand...
Click to collapse
So I got a HD8 2018 today and it came with OS version that forced me to connect to WiFi and update itself. I was pretty pissed but I used this guide to get root easily.
I had Arch based linux installed which gave problems while running script, so I made bootable Ubuntu usb and that worked fine. Thank you everyone involved in developing this hack.
madman said:
So I got a HD8 2018 today and it came with OS version that forced me to connect to WiFi and update itself. I was pretty pissed but I used this guide to get root easily.
I had Arch based linux installed which gave problems while running script, so I made bootable Ubuntu usb and that worked fine. Thank you everyone involved in developing this hack.
Click to expand...
Click to collapse
For future reference you can avoid the presumed forced WiFi connect by putting in a bogus password; once authentication fails a 'skip' option will appear.
bibikalka said:
@k4y0z
If I flash your zip, can I then flash Amazon update as is? Will your TWRP manage the bootloaders/etc when flashing the stock ROM?
Click to expand...
Click to collapse
Rortiz2 said:
I think yeah:
Click to expand...
Click to collapse
Yes, exactly.
Rortiz2 said:
I think yeah:
Click to expand...
Click to collapse
k4y0z said:
Quote:
TWRP will prevent updates from overwriting LK/Preloader/TZ, so generally installing an update should work without issues (only full updates, incremental updates won't work).
Yes, exactly.
Click to expand...
Click to collapse
OK - tried to upgrade to the latest update-kindle-Fire_HD8_8th_Gen-NS6312_user_1852_0002517056644.bin using the suggestions above, and got a hardcore Amazon logo bootloop.
My actions. I had the old unlock, so I flashed the zip in this thread first. New TWRP showed up - so far so good. Then I flashed the Amazon update zip as is, thinking the updated TWRP would do its magic. Flashed Magisk, tried to reboot. No go - Amazon logo bootloop. No recovery either. So it feels that I lost the unlock, and, perhaps LK & preloader & TZ got overwritten with the new versions from the Amazon update zip.
Any recovery here other than opening the case?
bibikalka said:
OK - tried to upgrade to the latest update-kindle-Fire_HD8_8th_Gen-NS6312_user_1852_0002517056644.bin using the suggestions above, and got a hardcore Amazon logo bootloop.
My actions. I had the old unlock, so I flashed the zip in this thread first. New TWRP showed up - so far so good. Then I flashed the Amazon update zip as is, thinking the updated TWRP would do its magic. Flashed Magisk, tried to reboot. No go - Amazon logo bootloop. No recovery either. So it feels that I lost the unlock, and, perhaps LK & preloader & TZ got overwritten with the new versions from the Amazon update zip.
Any recovery here other than opening the case?
Click to expand...
Click to collapse
That is strange, I've had no issues installing that firmware unmodified through TWRP.
So you can't boot neither normal or recovery?
Does it say something in the corner when trying to boot recovery?
You can try the boot-fastboot.sh script to get into hacked fastboot.
k4y0z said:
That is strange, I've had no issues installing that firmware unmodified through TWRP.
So you can't boot neither normal or recovery?
Does it say something in the corner when trying to boot recovery?
You can try the boot-fastboot.sh script to get into hacked fastboot.
Click to expand...
Click to collapse
Cannot boot anywhere - no message about booting recovery either. When you tried installing unmodified firmware, was that on HD8 2018, or some other tablet? I wonder if perhaps there are some differences with HD8 2018 given that it's Nougat.
I will try the hacked fastboot, but most likely - will have to open the case.