Related
Hope this helps.
1. Install android sdk and use the included install manager in the sdk to install the latest google usb drivers and platform tools (platform tools include fastboot and adb). Make sure adb and fastboot directory is in your Path variable as well.
2.Download latest stock image for Nexus 9 from google: https://developers.google.com/android/nexus/images?hl=en
3.Download latest twrp (here is the latest right now 10/6/2015): http://forum.xda-developers.com/nex...recovery-twrp-2-8-2-0-touch-recovery-t2944788
4.Download either a stock boot image with the no- forceencrypt flag set or a kernel with the no-forceencrypt flag set
a.I use the elementalx kernel (10/6/2015): http://forum.xda-developers.com/nexus-9/orig-development/kernel-elementalx-n9-0-02-alpha-t2931657
b.A stock kernel for the MRA58K build with the no-forceencrypt flag set can be found here (boot.zip): http://forum.xda-developers.com/nexus-9/general/marshmallow-factory-images-available-t3218290/page3
5.Download the latest supersu that works with nexus (beta now) : http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
6.Make sure you have usb debugging enabled and ability to unlock bootloader (android developer options menu on nexus).
7.Unzip the 6.0 stock image into a folder and open a command window in the folder.
8.Type the following:
a.adb reboot bootloader, wait until nexus boots into bootloader
b.fastboot oem unlock
c.flash-all, now wait a few minutes while the stock image flashes
9.At this point your nexus will reboot. Once you’re started, up you need to again enable usb debugging and the ability to unlock your bootloader in the android developer options menu. Now type the following to flash TWRP:
a.adb reboot bootloader, wait until nexus boots into bootloader
b.fastboot flash recovery twrp.img (or whatever the image filename is from the twrp download).
10.Important: now make sure you boot DIRECTLY into TWRP via the button combination (power and volume down), a fastboot command, or the fastboot menu. If you don’t TWRP will be deleted and you’ll need to reflash using the last step.
11.Once in TWRP, hit “cancel” when asked for the password and then erase/wipe data and make sure MTP is enabled (dig around the menus in TWRP, it’s all in there somewhere). This erases the encrypted partition and allows you to use adb to push files to your sdcard.
12.Now type adb push supersufile.zip /sdcard/supersufile.zip, make sure you’re typing from the correct directory.
13.Install supersu via the install menu on TWRP.
14.You now need to install a kernel with the no-forceencrypt flag set:
a.If you want to install a custom kernel (like elementalx), type adb push elementalxfile.zip /sdcard/elementalxfile.zip, make sure you’re typing from the correct directory. Then use TWRP to install the zip from your sdcard.
b.If you want to install the modified stock boot.img then unzip the boot.zip, boot back into the bootloader and type: fastboot flash boot boot.img. Make sure you do NOT boot back into the android OS before doing this step or you'll have to reflash twrp.
Reboot and you’re good to go.
Didnt work for me.
Flash-all script doesn't work for everyone use these steps:
Code:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot –w
fastboot flash boot boot.img [unencypted if wanted]
fastboot flash cache cache.img
fastboot flash recovery recovery.img [twrp usually]
fastboot flash system system.img
fastboot flash vendor vendor.img
typo
excellent guide, just a small typo on 9.b, "fastboot (not flashboot) flash recovery twrp.img"
Thank you
Fda979 said:
excellent guide, just a small typo on 9.b, "fastboot (not flashboot) flash recovery twrp.img"
Thank you
Click to expand...
Click to collapse
Fixed. Thanks.
Sent from my Nexus 9 using Tapatalk
You can't just flash latest stable SuperSU, you need SuperSU 2.50+ beta and a modified boot.img. Instructions here: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
- sYndrome - said:
You can't just flash latest stable SuperSU, you need SuperSU 2.50+ beta and a modified boot.img. Instructions here: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
Click to expand...
Click to collapse
I flashed the latest supersu and the latest elementalx kernel.... been running it since about an hour after elementalx kernel for 6.0 final was posted....... everything seems to be working fine. Are you sure? Maybe i'm having no problems with supersu because i'm using elementalx? let me know the reason, i'll check it out on my tablet and see if i can reproduce, and if so i'll modify the guide. But after about a day and a half use, i've had no issues. thx for quality checking.
gt
Am I missing something?
can I not just do a wipe and flash the img with twrp like a custom rom? Edit: Got it working. For me it was much easier to use this as opposed to the android sdk, because it would not detect my version of java. From there I followed your instructions, mostly. Putting the files you posted inside the directory the mini adb client allowed the flash-all command to work. From there I followed chainfire's instructions on the latest SU. Everything seems to be running smoothly. Thanks for the initiative, OP :good:
i used supersu 2.52 due to it seems be be required by the guides and i get the notification that the binary needs to be updated. i have not done that yet. is updating the binary something i should try to do? or, if not is it ok to turn off notifications from supersu? thanks.
dkryder said:
i used supersu 2.52 due to it seems be be required by the guides and i get the notification that the binary needs to be updated. i have not done that yet. is updating the binary something i should try to do? or, if not is it ok to turn off notifications from supersu? thanks.
Click to expand...
Click to collapse
Of course update binaries. Choose normal method.
Verttex said:
Flash-all script doesn't work for everyone use these steps:
Code:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot –w
fastboot flash boot boot.img [unencypted if wanted]
fastboot flash cache cache.img
fastboot flash recovery recovery.img [twrp usually]
fastboot flash system system.img
fastboot flash vendor vendor.img
Click to expand...
Click to collapse
I was facing same issue, then updated fastboot(android-sdk) and flash-all script worked fine for me.
That should work as well. That sequence of commands should work with any fastboot version. Just make sure to flash the vendor.img, some scripts don't use that as it's only used for the Nexus 9.
Why so complicated? I just installed @wug's NRT toolkit(on a Venue8 pro) and it did everything for me. Now im on rooted stock 6.0 with disabled encryption. Only thing i needed to do is to flash latest super su beta 2.52, that's it.
Verttex said:
Flash-all script doesn't work for everyone use these steps:
Code:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot –w
fastboot flash boot boot.img [unencypted if wanted]
fastboot flash cache cache.img
fastboot flash recovery recovery.img [twrp usually]
fastboot flash system system.img
fastboot flash vendor vendor.img
Click to expand...
Click to collapse
i did all this, no worries and no error messages
i did fastboot reboot
now I am in a weird loop of
- google screen
- your device is corrupt
- google screen
- twrp (it flashes quite quickly, error messages on mounting everything and last line says something about renaming and something about stock rom)
loop
any ideas ?
Did you make sure to flash vendor.img?
You might try flashing the regular recovery first and then boot in, turn on oem unlock and adb, and then flash twrp and modified boot.img, then reboot into twrp (don't boot normally or it will erase twrp) and flash SuperSU.
Verttex said:
Did you make sure to flash vendor.img?
You might try flashing the regular recovery first and then boot in, turn on oem unlock and adb, and then flash twrp and modified boot.img, then reboot into twrp (don't boot normally or it will erase twrp) and flash SuperSU.
Click to expand...
Click to collapse
yes, that seems to have been it
flashing TWRP seems to have been the problem so I have left everything as stock until root etc works on the stovk kernel
thanks for your help
Nice guide.
I install Busybox from Play, I assume that's needed? Everyone else doing this?
- sYndrome - said:
You can't just flash latest stable SuperSU, you need SuperSU 2.50+ beta and a modified boot.img. Instructions here: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
Click to expand...
Click to collapse
added link to the latest beta supersu. thx.
All of these steps worked for me, but my battery doesn't charge right I don't think. It says battery life is at 3,745%. It runs out somewhere around 3,000%. Any ideas on how to fix that?
hi guys, my computer ( wins10) donset read adb device.
but i i use fastboot commands its able to list my devices, but ' adb devices' shows none listed? i am suck, might have soft brick it, able to boot into stock recocery. any suggestions?
oneplus 5 phone.
What are you trying to do?
Rhoban said:
What are you trying to do?
Click to expand...
Click to collapse
Was trying to update , but got stuck at boot screen .
Just flash the stock ROM with the stock recovery.
I can’t sideload it, “ adb not working “
Rhoban said:
Just flash the stock ROM with the stock recovery.
Click to expand...
Click to collapse
Files all courupted
With stock recovery you can't use adb sideload in windows 10.
If you're unlocked i would flash Codeworkx TWRP, download the OOS 5.0.1 Full Rom Zip, boot into TWRP, copy the zip to your phone or sideload the zip.
If you're not unlocked (and thus being unable to flash twrp) use windows 7 and sideload the zip.
You can download ADB drivers here
Can you boot? Turn on USB debugging , make sure that you allow the device when booted.
Do an advanced devices when in the OS make sure it's there.
Then you can install a TWRP recovery and do what you need to.
maikvitesse said:
With stock recovery you can't use adb sideload in windows 10.
If you're unlocked i would flash Codeworkx TWRP, download the OOS 5.0.1 Full Rom Zip, boot into TWRP, copy the zip to your phone or sideload the zip.
If you're not unlocked (and thus being unable to flash twrp) use windows 7 and sideload the zip.
You can download ADB drivers here
Click to expand...
Click to collapse
Hi bro, I am unlocked ! I mange to find a win7 pc. I ran both commands “adb devices” and “Fastboot devices”
Both shows me my devices number hence drivers are working fine.
Now do I flash twrp and sidleload? Because I can’t sideload in stock “error: *cant read zip*”. Do advice me!
PS: can boot into OS, no OS in system only recovery . USB debugging was on before boot loop happens! Thanks for all advices !
maikvitesse said:
With stock recovery you can't use adb sideload in windows 10.
If you're unlocked i would flash Codeworkx TWRP, download the OOS 5.0.1 Full Rom Zip, boot into TWRP, copy the zip to your phone or sideload the zip.
If you're not unlocked (and thus being unable to flash twrp) use windows 7 and sideload the zip.
You can download ADB drivers here
Click to expand...
Click to collapse
dladz said:
Can you boot? Turn on USB debugging , make sure that you allow the device when booted.
Do an advanced devices when in the OS make sure it's there.
Then you can install a TWRP recovery and do what you need to.
Click to expand...
Click to collapse
Hi ! USB debugging was turn on before boot loop happened. Can’t boot into OS , only recovery
lolitsryan96 said:
Hi bro, I am unlocked ! I mange to find a win7 pc. I ran both commands “adb devices” and “Fastboot devices”
Both shows me my devices number hence drivers are working fine.
Now do I flash twrp and sidleload? Because I can’t sideload in stock “error: *cant read zip*”. Do advice me!
PS: can boot into OS, no OS in system only recovery . USB debugging was on before boot loop happens! Thanks for all advices !
Click to expand...
Click to collapse
be sure your bootloader is unlocked
turn your phone into fastboot
open command prompt to the folder your twrp is in.
rename the twrp image file to recovery.img
do the following command: fastboot flash recovery recovery.img
after that boot into recovery
press adb sideload
on the computer, open command prompt to the folder where your zip file is in.
rename the rom zip file to rom.zip
do the following command: adb sideload rom.zip
done!
Thanks bro, I shall update you on the situation once I done, at work now.
Do I need to “open command promt “ at my sdk folder/plat-form tools?
maikvitesse said:
be sure your bootloader is unlocked
turn your phone into fastboot
open command prompt to the folder your twrp is in.
rename the twrp image file to recovery.img
do the following command: fastboot flash recovery recovery.img
after that boot into recovery
press adb sideload
on the computer, open command prompt to the folder where your zip file is in.
rename the rom zip file to rom.zip
do the following command: adb sideload rom.zip
done!
Click to expand...
Click to collapse
hi bro, sideload failed i think, i cant find sideload file. when the sideload end. its gave x1.00 something like that.
maikvitesse said:
be sure your bootloader is unlocked
turn your phone into fastboot
open command prompt to the folder your twrp is in.
rename the twrp image file to recovery.img
do the following command: fastboot flash recovery recovery.img
after that boot into recovery
press adb sideload
on the computer, open command prompt to the folder where your zip file is in.
rename the rom zip file to rom.zip
do the following command: adb sideload rom.zip
done!
Click to expand...
Click to collapse
attach image, successfully sideload but phone still in bootloop?
lolitsryan96 said:
attach image, successfully sideload but phone still in bootloop?
Click to expand...
Click to collapse
you need to wipe everything before flashing
maikvitesse said:
you need to wipe everything before flashing
Click to expand...
Click to collapse
just wipe, now re-sideloading. how it works. bloody nightmare dude.
maikvitesse said:
you need to wipe everything before flashing
Click to expand...
Click to collapse
still stuck at the boot loop, any advice
maikvitesse said:
you need to wipe everything before flashing
Click to expand...
Click to collapse
hi brother finally did it!
my oneplus 5 was encrypted totally forgot about hence need to wipe full back to factory stage, learn my lesson the hard way really grateful for your help!
ps; i am going to Holland on may-june for my euro trip! any places of interest in Holland?
lolitsryan96 said:
hi brother finally did it!
my oneplus 5 was encrypted totally forgot about hence need to wipe full back to factory stage, learn my lesson the hard way really grateful for your help!
ps; i am going to Holland on may-june for my euro trip! any places of interest in Holland?
Click to expand...
Click to collapse
nice good to hear!
haha, well tourists like Amsterdam so do visit that and visit The Hague/Scheveningen. I like these 3 places the most I think. Look up TripAdvisor for good attractions once you're there. do visit 'The Amsterdam Dungeon' don't miss that, I liked it very very much!
how to install the drivers?
maikvitesse said:
With stock recovery you can't use adb sideload in windows 10.
If you're unlocked i would flash Codeworkx TWRP, download the OOS 5.0.1 Full Rom Zip, boot into TWRP, copy the zip to your phone or sideload the zip.
If you're not unlocked (and thus being unable to flash twrp) use windows 7 and sideload the zip.
You can download ADB drivers here
Click to expand...
Click to collapse
Cannot adb to the phone in FASTBOOT. adb devices shows nothing when in FASTBOOT, but shows the device when in normal boot.
Hence I cannot upgrade TWRP from 3.2.1-1 to 3.2.3-0. Was trying this so to upgrade from beta23 to the beta 26, now 27 with which 3.2.1-1 seems to have problems.
A 2nd approach, just re-installing beta23 without Magisk18 gives the stock recovery which manages the beta27 install. But then I'm blocked from a Magisk18 install and still cannot use FASTBOOT mode to put TWRP back on.
Thought the adb drives could be old and sought new drivers, even assuming your link is to the most current I don't know how to get my Windows7 to use the zip file. Can you assist? This would let me put the latest TWRP, hence install Magisk18 and be rooted again!
I've a big problem, and I hope someone can help me
I wanted to change the rom, so I've rebooted my phone in recovery mode and executed a full wipe, after that I've updated TWRP, everything seemed to have gone well so i restarted my phone, but at this point it neither boot the rom(obviously, it is full wiped) nor the TWRP can start...
What can I do? I can only start the Fastboot screen...
How'd you update TWRP? If you did it through fastboot commands, you can just flash TWRP to the recovery partition, or boot it directly.
If you didn't do it through fastboot commands, you'll need to get that to fix it. Google has links to the latest android-tools for Windows and Linux on their Android site somewhere.
From there, you'll need TWRP (either official or codeworkx's), and then you use the flashboot executable to flash it: fastboot flash recovery TWRP.img
espionage724 said:
How'd you update TWRP? If you did it through fastboot commands, you can just flash TWRP to the recovery partition, or boot it directly.
If you didn't do it through fastboot commands, you'll need to get that to fix it. Google has links to the latest android-tools for Windows and Linux on their Android site somewhere.
From there, you'll need TWRP (either official or codeworkx's), and then you use the flashboot executable to flash it: fastboot flash recovery TWRP.img
Click to expand...
Click to collapse
Thanks, I solved reflashing it via ADB with fastboot command
Works only on Tank HD and Mantis 4K.
The process is really simple and requires very little effort to return back to 100% stock in case you return your device or for many reasons. Ok download and find the official latest stock image for your Fire TV, and download then install ADB and Fastboot on your computer, plug your Fire TV in to your computer, make sure ADB is on, then type in these given commands, ADB devices, ADB reboot recovery, ADB shell, twrp wipe /system, twrp sideload, ADB sideload update.zip (rename the .bin to .zip) and let it continue flashing. Once finished, take the update.zip and extract it. Find the boot.img from the folder and type this in. ADB sideload (drag and drop) boot.img /storage/emulated/0 (if this doesn't transfer while in TWRP, reboot into the /system and type in the same command again), this is where you'll need an OTG cable with a mouse (For the Fire TV Stick 4K it'll boot into TWRP on boot with OTG so cancel the rebooting in 3..2...1.. and click install in TWRP, on the lower right hand corner click on install image, boot.img and flash it as boot. Backup the boot.img and restore it with your mouse. Unplug your device, and plug it back into the computer, ADB reboot recovery, ADB shell reboot-amonet, it'll now be in hacked fastboot mode. Make sure it's recognized as a fastboot device and type in these final commands, fastboot flash boot (drag and drop) boot.img then reboot. After rebooting, type in ADB reboot recovery and you'll now see no command which means you successfully removed TWRP with stock updates now.
For those without OTG, still the same instructions (Backup the boot after flashing the stock image and restore it with these commands that can be found here):
https://twrp.me/faq/openrecoveryscript.html
Skel40 said:
Find the boot.img from the folder and type this in. ADB sideload (drag and drop) boot.img /storage/emulated/0 (if this doesn't transfer while in TWRP, reboot into the /system and type in the same command again), this is where you'll need an OTG cable with a mouse (For the Fire TV Stick 4K it'll boot into TWRP on boot with OTG so cancel the rebooting in 3..2...1.. and click install in TWRP, on the lower right hand corner click on install image, boot.img and flash it as boot. Backup the boot.img and restore it with your mouse.
Click to expand...
Click to collapse
You don't need to deal with the boot.img in TWRP, it gets flashed together with the rom. Also no need for a backup and a restore.
Simply flash the stock rom with TWRP, then reboot to the BL with 'adb shell reboot-amonet' followed by a 'fastboot flash boot boot.img'
In case someone wants to send the stick back, a 'fastboot format userdata' is a good idea, then fastboot reboot
Just at the reboot, TWRP gets replaced with the stock recovery.
Done.
Update: Finally got on the latest and greatest, no root or TWRP. I found a list of the stock ROMS in the link below. As stated above, I simply flashed the stock ROM in TWRP and then rebooted and did a factory reset followed by and update. Simple as that.
https://www.aftvnews.com/amazon-fire-tv-fire-tv-stick-software-update-history/
Where can I find an unrooted stock ROM? I'm trying to get rid of twrp on one of my firetv boxes. I started by allowing OTA updates and when I try to update, it will download and then acts like it will install it, but upon reboot it is still on the same version. Presumably because TWRP is interfering with the install process? Either way, direction yo a stock image is appreciated. All I can seem to find are rprerooted images.
For 4k
https://forum.xda-developers.com/fire-tv/general/official-stock-image-fire-tv-stick-4k-6-t4088247
First Post, rename bin to zip.
Flash with twrp.
adb push firmware.zip /sdcard/firmware.zip
adb shell twrp wipe cache
adb shell twrp wipe data
adb shell twrp wipe dalvik
adb shell twrp wipe /system
adb shell twrp install /sdcard/firmware.zip
Extract boot.img from Firmware.zip
adb shell reboot-amonet
fastboot flash boot boot.img
fastboot reboot
Now you are back at Stock.
0815hoffi said:
For 4k
https://forum.xda-developers.com/fire-tv/general/official-stock-image-fire-tv-stick-4k-6-t4088247
First Post, rename bin to zip.
Flash with twrp.
adb push firmware.zip /sdcard/firmware.zip
adb shell twrp wipe cache
adb shell twrp wipe data
adb shell twrp wipe dalvik
adb shell twrp wipe /system
adb shell twrp install /sdcard/firmware.zip
Extract boot.img from Firmware.zip
adb shell reboot-amonet
fastboot flash boot boot.img
fastboot erase userdata
fastboot reboot
Now you are back at Stock.
Click to expand...
Click to collapse
Does this remove twrp? I want to go back to stock but NOT UNISTALL TWRP because aftv-gapps are not working for me so i want to go back to stock and re-root it and install aftv gapps
ROM_gamer987 said:
Does this remove twrp? I want to go back to stock but NOT UNISTALL TWRP because aftv-gapps are not working for me so i want to go back to stock and re-root it and install aftv gapps
Click to expand...
Click to collapse
This will remove TWRP
Code:
adb shell reboot-amonet
fastboot flash boot boot.img
fastboot erase userdata
fastboot reboot
This code restores original Recovery and bootloader, if you want to keep TWRP then don't use these commands, you can use above commands to unroot.
ROM_gamer987 said:
I want to go back to stock but NOT UNISTALL TWRP because aftv-gapps are not working for me so i want to go back to stock and re-root it and install aftv gapps
Click to expand...
Click to collapse
If its a gapps system install, simply wipe system and flash a new stock bin (renamed to zip).
-----------------
Note to everyone, the guide above in OP works only for 'tank' (aka second gen stick) and 'mantis' (aka 4k stick).
SweenWolf said:
This will remove TWRP
Code:
adb shell reboot-amonet
fastboot flash boot boot.img
fastboot erase userdata
fastboot reboot
This code restores original Recovery and bootloader, if you want to keep TWRP then don't use these commands, you can use above commands to unroot.
Click to expand...
Click to collapse
Well I did these commands and twrp is still there, I guess I was lucky and the boot.img failed or something, Now I got gapps working
I might be missing something, but as far as i can see, following the steps from this thread will only flash the stock boot.img (which is not patched with amonet when using fastboot) and erase userdata (reset), but it will not remove twrp (which reside in the recovery partition).
To replace TWRP with stock recovery, the fastboot command should look like this:
fastboot flash recovery stock_recovery.img
"stock_recovery.img" filename is just an example,of course.
Pretoriano80 said:
I might be missing something
Click to expand...
Click to collapse
I don't know
k4y0z said in the 4k thread, that the stock recovery gets restored (out of the boot.img) at first boot...
Though your command should work fine obviously.
k4y0z said:
Is it possible to remove the hacked bootloader and twrp?
Click to expand...
Click to collapse
You would have to flash stock update-bin via TWRP first and then flash the stock boot.img from that same update-bin separately via hacked fastboot.
Amazon recovery should then be restored on first boot.
Click to expand...
Click to collapse
Permalink
@0815hoffi, i have followed all the mentioned command steps above and TWRP still exists. Attached is the proof. It doesn't show up during normal boots but when reset or Fire stick auto software update is performed it takes control. TWRP even installs Fire stick software update too.
@Pretoriano80 looks like you are correct. Is there a way i can completely remove TWRP since now i have restored Fire stick original OS and not going through shorting and root process again. adb doesn't work now.
TwrpFire
matrixddl said:
@0815hoffi, i have followed all the mentioned command steps above and TWRP still exists. Attached is the proof. It doesn't show up during normal boots but when reset or Fire stick auto software update is performed it takes control. TWRP even installs Fire stick software update too.
@Pretoriano80 looks like you are correct. Is there a way i can completely remove TWRP since now i have restored Fire stick original OS and not going through shorting and root process again. adb doesn't work now.
TwrpFire
Click to expand...
Click to collapse
For me it worked on TvStick2 .
You must use Stock rom , not prerooted.
Wipe System , Flash rom, Boot amonet, Flash Boot.bin with Fastboot, reboot.
Run oobe, enable ADB.
Adb shell reboot recovery.
Stock Recovery should comes up....
0815hoffi said:
For me it worked on TvStick2 .
You must use Stock rom , not prerooted.
Wipe System , Flash rom, Boot amonet, Flash Boot.bin with Fastboot, reboot.
Run oobe, enable ADB.
Adb shell reboot recovery.
Stock Recovery should comes up....
Click to expand...
Click to collapse
I have downloaded latest stock from here
Now to retry the process do i have to unlock again or anyway i can continue using existing twrp.
No if you can Boot to twrp.
Sus_i said:
I don't know
k4y0z said in the 4k thread, that the stock recovery gets restored (out of the boot.img) at first boot...
Though your command should work fine obviously.
Permalink
Click to expand...
Click to collapse
Ok, i figured how it works. Probably if the recovery signature doesn't match on first clean boot, then it will trigger the /system/bin/install-recovery.sh script and that will flash/install the stock recovery.
But if for some reason that script was removed/modified, then it will fail to replace TWRP with the stock recovery (maybe that's why this guide works for some but not for all).
0815hoffi said:
No if you can Boot to twrp.
Click to expand...
Click to collapse
I rooted again and tried to try to restore original and still TWRP exists. I have followed your steps as well as original OP's instructions still no luck.
I was on mantis-6.2.6.8-rooted_r1 and from there i used the stock update-kindle-mantis-NS6276_user_2933_0004396381572 to restore? Which version of stock rom did you use?
Pretoriano80 said:
Ok, i figured how it works. Probably if the recovery signature doesn't match on first clean boot, then it will trigger the /system/bin/install-recovery.sh script and that will flash/install the stock recovery.
But if for some reason that script was removed/modified, then it will fail to replace TWRP with the stock recovery (maybe that's why this guide works for some but not for all).
Click to expand...
Click to collapse
Is there a way to check or fix this?
Same as installed.
Try with
https://d1s31zyz7dcc2d.cloudfront.n...dle-mantis-NS6268_user_2315_0003255372676.bin
Flash it, boot, make initial Setup.
Then reboot to twrp and follow the Guide
matrixddl said:
I rooted again and tried to try to restore original and still TWRP exists. I have followed your steps as well as original OP's instructions still no luck.
I was on mantis-6.2.6.8-rooted_r1 and from there i used the stock update-kindle-mantis-NS6276_user_2933_0004396381572 to restore? Which version of stock rom did you use?
Is there a way to check or fix this?
Click to expand...
Click to collapse
I don't know why it doesn't work for you, so i have no idea how to fix.
Personally, when i went back to full factory condition, i flashed every partition with hacked fastboot.
I have it testet with my 4k Stick Installed Version 6.2.7.3.
I think the Problem is #fastboot erase userdata
dont run this.
Now i am back at Stock.
Thats the Log off my test.
https://androidfilehost.com/?fid=6006931924117923181
Installed Version 6.2.7.3
D:\FireTV2K4K>adb push ftvs4k_6.2.7.3.zip /sdcard/
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
10290 KB/s (648296329 bytes in 61.522s)
D:\FireTV2K4K>adb shell reboot recovery
D:\FireTV2K4K>adb shell twrp wipe cache
Formatting Cache using mke2fs...
Done.
Done processing script file
D:\FireTV2K4K>adb shell twrp wipe data
Wiping data without wiping /data/media ...
Done.
Formatting cache using mke2fs...
Done.
Done processing script file
D:\FireTV2K4K>adb shell twrp wipe dalvik
Wiping Cache & Dalvik...
-- Dalvik Cache Directories Wipe Complete!
Done processing script file
D:\FireTV2K4K>adb shell twrp wipe /system
Formatting System using mke2fs...
Done.
Done processing script file
D:\FireTV2K4K>adb shell twrp install /sdcard/ftvs4k_6.2.7.3.zip
Installing zip file '/sdcard/ftvs4k_6.2.7.3.zip'
Checking for Digest file...
[amonet] Load microloader from recovery...
[amonet] Remove boot patch...
[amonet] OK
Target: Amazon/mantis/mantis:6.0/NS6273/2773N:user/amz-p,release-keys
Patching system image unconditionally...
Patching vendor image unconditionally...
script succeeded: result was [1.000000][amonet] Install boot patch...
[amonet] OK
[amonet] Install recovery patch...
[amonet] ALREADY_INSTALLED
Done processing script file
D:\FireTV2K4K>adb shell reboot-amonet
D:\FireTV2K4K>fastboot devices
************* fastboot
D:\FireTV2K4K>fastboot flash boot boot.img
target reported max download size of 134217728 bytes
sending 'boot' (7522 KB)...
OKAY [ 0.312s]
writing 'boot'...
OKAY [ 0.484s]
finished. total time: 0.797s
D:\FireTV2K4K>fastboot erase userdata
******** Did you mean to fastboot format this ext4 partition?
erasing 'userdata'...
OKAY [ 0.141s]
finished. total time: 0.156s
D:\FireTV2K4K>fastboot reboot
rebooting...
finished. total time: -0.000s
D:\FireTV2K4K>
_________________________________________________
TWRP is still here
_________________________________________________
Update on initial Setup is running > auto reboot to TWRP
_________________________________________________
D:\FireTV2K4K>adb shell
~ # ^[[5;5R
~ # ^[[7;5R
~ # ^[[9;5R
~ # ^[[11;5Rexit
exit
D:\FireTV2K4K>
D:\FireTV2K4K>adb push ftvs4k_6.2.7.3.zip /sdcard/
9691 KB/s (648296329 bytes in 65.325s)
D:\FireTV2K4K>adb shell twrp install /sdcard/ftvs4k_6.2.7.3.zip
Installing zip file '/sdcard/ftvs4k_6.2.7.3.zip'
Checking for Digest file...
[amonet] Load microloader from recovery...
[amonet] Remove boot patch...
[amonet] OK
Target: Amazon/mantis/mantis:6.0/NS6273/2773N:user/amz-p,release-keys
Patching system image unconditionally...
Patching vendor image unconditionally...
script succeeded: result was [1.000000][amonet] Install boot patch...
[amonet] OK
[amonet] Install recovery patch...
[amonet] ALREADY_INSTALLED
Done processing script file
D:\FireTV2K4K>adb shell reboot-amonet
D:\FireTV2K4K>fastboot devices
************* fastboot
D:\FireTV2K4K>fastboot flash boot boot.img
target reported max download size of 134217728 bytes
sending 'boot' (7522 KB)...
OKAY [ 0.312s]
writing 'boot'...
OKAY [ 0.489s]
finished. total time: 0.801s
D:\FireTV2K4K>fastboot reboot
rebooting...
finished. total time: -0.000s
D:\FireTV2K4K>
__________________________________________________________________________________________________
After Bootup Update is running, now it reboots to Stock recovery and 6.2.7.6 will be is installed.
__________________________________________________________________________________________________
Click to expand...
Click to collapse
adb shell reboot recovery > boots now to stock Amazon recovery.
This worked.
Installed version 6276. adb reboot recovery returns "No Command".
Kudos for you help and patience.
0815hoffi said:
I have it testet with my 4k Stick Installed Version 6.2.7.3.
I think the Problem is #fastboot erase userdata
dont run this.
Now i am back at Stock.
Thats the Log off my test.
adb shell reboot recovery > boots now to stock Amazon recovery.
Click to expand...
Click to collapse
My phone is wt86047 with stock ROM, and I want to install TWRP then LineageOS. The process I do is the following:
1. From fastboot, flash latest TWRP twrp-3.6.1_9-0-wt88047.img using fastboot flash recovery twrp-3.6.1_9-0-wt88047.img
2. Boot into recovery, flash resize_wt88047x_v6.zip
3. Reboot into fastboot, enter fastboot -w
4. Phone goes into bootloop.
5. Flash stock ROM again with MiFlash.
6. I'm now back to step #1.
What am I doing wrong?
bomberb17 said:
What am I doing wrong
Click to expand...
Click to collapse
Skip step "3. Reboot into fastboot, enter fastboot -w" and try again. Are you executing fastboot -w because the flash script wants you to do this?
WoKoschekk said:
Skip step "3. Reboot into fastboot, enter fastboot -w" and try again. Are you executing fastboot -w because the flash script wants you to do this?
Click to expand...
Click to collapse
Yes, that is what the flash script tells me. If I skip step #3, then the partition containing lineage-19.1-20220323-UNOFFICIAL-wt88047x.zip is lost. Also TWRP recovery no longer works after the partition script.
bomberb17 said:
Yes, that is what the flash script tells me. If I skip step #3, then the partition containing lineage-19.1-20220323-UNOFFICIAL-wt88047x.zip is lost. Also TWRP recovery no longer works after the partition script.
Click to expand...
Click to collapse
what about using lineage recovery as recommended in this thread?
[ROM][12.1][UNOFFICIAL][wt88047x] LineageOS 19.1
Important information: This thread is for LineageOS 19.1 opensource builds for Wingtech WT88047, marketed as Redmi 2 by Xiaomi. The following will not be supported in this thread: Custom Kernels Mods Modified system files Xposed Magisk What's...
forum.xda-developers.com
Instead of flashing any zip you have to sideload them with ADB
Lineage recovery link is broken..
And what is the way to sideload lineage-19.1-20220323-UNOFFICIAL-wt88047x.zip? And after which step?
So after I install resize_wt88047x_v6.zip, I get:
"WARNING - TWRP DETECTED
Please reboot to fastboot and run the following:
fastboot -w
Done!"
I didn't reboot to fastboot this time, and I followed this process for the lineage rom
How to Install Custom ROM on Android via ADB Sideload
In this comprehensive tutorial, we will show you the detailed steps to install a Custom ROM on Android using ADB Sideload feature of TWRP.
www.droidwin.com
and the log says:
"..
Patching system image unconditionally...
E1001: Failed to update system image.
Updater process ended with ERROR: 1
mount -o bind '/data/media/0' '/sdcard' process ended with signal: 6"
Thoughts?
bomberb17 said:
So after I install resize_wt88047x_v6.zip, I get:
"WARNING - TWRP DETECTED
Please reboot to fastboot and run the following:
fastboot -w
Done!"
I didn't reboot to fastboot this time, and I followed this process for the lineage rom
How to Install Custom ROM on Android via ADB Sideload
In this comprehensive tutorial, we will show you the detailed steps to install a Custom ROM on Android using ADB Sideload feature of TWRP.
www.droidwin.com
and the log says:
"..
Patching system image unconditionally...
E1001: Failed to update system image.
Updater process ended with ERROR: 1
mount -o bind '/data/media/0' '/sdcard' process ended with signal: 6"
Thoughts?
Click to expand...
Click to collapse
You need to sideload it only in Lineage recovery and not in TWRP.
Try this:
1. flash resize_wt88047x_v6.zip
2. reboot into fastboot and run fastboot -w
3. start TWRP and go to Wipe > Format Data
4. reboot into TWRP
5. flash the ROM
If error still exists do not reboot and start ADB. Then run adb pull /tmp/recovery.log recovery.txt. This will save a copy of the TWRP log named recovery.txt inside your ADB folder. Then upload this file here.
bomberb17 said:
Lineage recovery link is broken..
Click to expand...
Click to collapse
Extract the lineage 19.1 rom and find recovery.img
put it into platform tools folder and execute fastboot command
fastboot flash recovery recovery.img
fastboot reboot
then you have lineage recovery
I finally managed to install lineage rom by sideloading resize_wt88047x_v6.zip, then formatting data, cache and system partitions, then adb reboot recovery then sideload lineage rom.
Phew!