[SOLVED] Recover from Failed to process command error (0x120000) - Xoom General

Description of the Error:
I have tried to flash the .img files several times. Boot, recovery and userdata all flash just fine. However, when ever I flash system I get the following error:
Failed to process command error (0x120000)
Solution:
Alrighty, it took me 2 days but I finally figured out how to get past this dreaded error.
My Fastboot was unable to flash system.img (but successfully flashed boot, recovery, and userdata) to my rooted, unlocked US Xoom Wi-Fi Only running 3.1, 3.2, and/or 3.21 (yes I tried from all 3 versions using various update.zip methods).
I was attempting to revert to stock using the methods described in multiple threads on XDA, but couldn't get past the 0x120000 error when trying to flash the system.img.
Disclaimer:
This was done on an unlocked, rooted US Wi-Fi Only Xoom running HC 3.1. While this fixed my issue, I take no responsibility if the method does not work on 3G/4G versions, non-US versions, or just plain works differently between different devices. Using dd to flash images is not the safest route, but for me it was the only route.
Prerequisites:
Have adb and fastboot setup (e.g., through installing the Android SDK)
Have CWM Recovery installed on Xoom
Steps:
Download the stock HWI69 images from bwcorvus' sticky http://forum.xda-developers.com/showthread.php?t=1049485
Extract the image files into your platform-tools directory in the android-sdk
Reboot into recovery
Code:
adb push boot.img /sdcard/
adb push system.img /sdcard/
adb push recovery.img /sdcard/
adb push userdata.img /sdcard/
adb shell
su (if it doesn't bring you into root # prompt)
busybox dd if=/sdcard/boot.img of=/dev/block/mmcblk1p7
busybox dd if=/sdcard/system.img of=/dev/block/mmcblk1p8
exit
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
Follow lock instructions on device

Plugging into another USB slot solved mine
I had the same problem. 1200003 error.
Plugging the tablet without an extension cable directly in on of the back slots solved the prob.

Related

Need help with ADB on a mac

I'm trying to install baconbits on my G2 and I have a mac. I cannot seem to get the recovery image to work through fastboot. Help?
I can access the phone through the terminal but once I command it to reboot to the bootloader I can't get it to find the img file
There's a fastboot binary available for download from this page: http://developer.htc.com/adp.html
I have the binary in my sdk's tools folder but I still can't figure it out. Where/how do input the command to boot the img file?
pak256 said:
I have the binary in my sdk's tools folder but I still can't figure it out. Where/how do input the command to boot the img file?
Click to expand...
Click to collapse
You can flash files from recovery if they are on the SD card. You can either adb push while in recovery, or mount USB storage and tranfer the file. Or just transfer it via USB while the phone is on (big, green android screen)
I'm not sure how to install baconbits, but I think you need fastboot to flash the .img file. Recovery flashes .zip files and fastboot flashes .img files. You can put fastboot-mac in the same folder as adb... then fastboot flash recovery your_recovery.img. You really don't need adb (for this) since you can boot into fastboot on the phone by restarting while holding down the trackpad button.
These might be the droids you are looking for...
Code:
adb (read the instructions)
adb devices (you'll see your phone if it's plugged in, turned on, and in the proper mode)
adb reboot bootloader (white screen with androids on skateboards)
fastboot-mac (more reading...)
fastboot-mac devices (your phone again)
fastboot flash recovery your_recovery.img
fastboot reboot-bootloader
For some reason, I had a little trouble flashing my recovery- sometimes it would hang and wouldn't flash, sometimes it would only fastboot boot. So if you run into trouble, there might be other problems.
While you are at it, you might as well save yourself the trouble and either add the adb and flashboot folders into your path, or put the binaries somewhere in your path. I also renamed fastboot-mac to fastboot for simplicity.
Going to try that when I get out of class but I think you helped me realize what I was doing wrong. Thanks and will let you know if it works
Sent from my T-Mobile G2 using XDA App
Okay I could get the fastboot prompts to work but when I try to flash the recovery it tells me "g2recovery.img" could not be loaded
okay, used clockwork and got it to work. yay!

[Moto G6 Play][JETER] Rooting progress thread for JETER

UPDATE: Root achieved see thread here
I've managed to extract the boot.img from my device using the following steps, but patching it with MAGISK ends up with boot loop.
Here are the steps I've done.
I've unlocked the bootloader using the standard methods. All ADB commands are run from a computer with ADB and fastboot setup.
Connect phone to computer, enabled ADB usb debugging.
Code:
adb reboot bootloader
Once the device reboots to the bootloader.
https://drive.google.com/file/d/1Q7CIF2-byTW7ERUXFU0XlWFYZQM5hysd/ DO NOT FLASH THIS TO YOUR DEVICE only boot from it. This is a patched Moto E5 TWRP image. It takes a while to boot.
Don't mess with anything inside TWRP.
Code:
fastboot boot moto-g6-play-jeter-patched-twrp.img
Once TWRP boots from your computer type:
Code:
adb pull /dev/block/platform/soc/7824900.sdhci/by-name/boot stockboot.img
adb reboot
Once the device reboots and you're back in android run
Code:
adb push stockboot.img /sdcard/
This will push the stockboot.img to your sdcard folder
Intall Magisk Manager - https://github.com/topjohnwu/MagiskManager/releases/download/v5.7.0/MagiskManager-v5.7.0.apk
Patch stockboot.img located on your sdcard using magisk manager.
Code:
adb pull /sdcard/MagiskManager/patched_boot.img
This will pull the patched_boot.img to your computer
Code:
adb reboot bootloader
Once the device reboots into the bootloader you can run
Code:
fastboot flash boot patched_boot.img
fastboot reboot
From here it boots to "N/A" and you get nothing. It just hangs there forever.
From here you can just flash the stockboot.img using the steps below
Hold power + volup + voldown which will boot back to the bootloader
Code:
fastboot flash boot stockboot.img
fastboot reboot
Now you're back on the stock bootloader and the device will boot up like normal.
Anyone have any advice on how to get MAGISK to patch correctly? The stock boot.img is ~16.8MB and the patched one from magisk is 12.1MB. I'm guessing that's the issue, but I'm not sure what else to do.
Hi!
I did the exact same thing with ALI, the Moto G6 non-plus. Glad to see that I'm not the only one struggling.
Hope we will find an answer...

Stuck loading twrp

Hi,
When my S7 Edge boots up it jumps to twrp but it's stuck on the teamwin logo screen and does not advance to menu.
This happened after I tried to format the data partition to ext4 via twrp and it just got stuck there too so when I rebooted it landed in this situation.
Unfortunately reflashing twrp or reflashing the stock rom via ODIN does not work as COM3 is recognized but then when I press start it doesnt do anything....
Also tried the suggestion I read online of:
fastboot format cache
fastboot format userdata
These commands just get stuck on <waiting for device>.
Also tried adb shell recovery --wipe_data but it gets stuck at I:LANG: en
Any help will be much appreciated!
Thanks
This is how I solved it in the end.
With cable connected I did:
1. adb push boot.img /external_sd
2. adb shell
3. dd if=/external_sd/boot.img of=/dev/block/platform/155a0000.ufs/by-name/RECOVERY
4. fastboot format cache
5. fastboot format userdata
6. adb shell recovery --wipe_data
7. adb fastboot recovery
Notes:
The boot.img was obtained from a downloaded stock rom image and by decompressing the AP file (just open it with 7Zip) and then you need to uncompress boot.img.lz4 with 7zip zstandard (look it up)
Step 1 took sometime to run since TWRP was stuck loading using a lot of CPU as phone was really really hot!
Sometime I needed to do a adb fastboot recovery and then quickly run and rerun command in step 1 until it succeeded.
Step 6 is redundant but is there just to be safe.
After this you are booted back to a stock recovery where you can use Odin to flash what you want.
In my case I flashed a stock rom and then flashed TWRP again.
redirts1978 said:
Hi,
When my S7 Edge boots up it jumps to twrp but it's stuck on the teamwin logo screen and does not advance to menu.
This happened after I tried to format the data partition to ext4 via twrp and it just got stuck there too so when I rebooted it landed in this situation.
Unfortunately reflashing twrp or reflashing the stock rom via ODIN does not work as COM3 is recognized but then when I press start it doesnt do anything....
Also tried the suggestion I read online of:
fastboot format cache
fastboot format userdata
These commands just get stuck on <waiting for device>.
Also tried adb shell recovery --wipe_data but it gets stuck at I:LANG: en
Any help will be much appreciated!
Thanks
Click to expand...
Click to collapse
HELP!!!! cant get my phone to be recogniced by adb, I have the same problem,
if its on TWRP boot screen or RECOVERY (blue downloading.... screen) its the same!!!
please help
redirts1978 said:
This is how I solved it in the end.
With cable connected I did:
1. adb push boot.img /external_sd
2. adb shell
3. dd if=/external_sd/boot.img of=/dev/block/platform/155a0000.ufs/by-name/RECOVERY
4. fastboot format cache
5. fastboot format userdata
6. adb shell recovery --wipe_data
7. adb fastboot recovery
Notes:
The boot.img was obtained from a downloaded stock rom image and by decompressing the AP file (just open it with 7Zip) and then you need to uncompress boot.img.lz4 with 7zip zstandard (look it up)
Step 1 took sometime to run since TWRP was stuck loading using a lot of CPU as phone was really really hot!
Sometime I needed to do a adb fastboot recovery and then quickly run and rerun command in step 1 until it succeeded.
Step 6 is redundant but is there just to be safe.
After this you are booted back to a stock recovery where you can use Odin to flash what you want.
In my case I flashed a stock rom and then flashed TWRP again.
Click to expand...
Click to collapse
i have exactly the same problem but cant boot to twrp or to OS ...only download mode...tried to flash twrp again not worked now try to flash stock firmware via odin ....PLEASE HELP ME
Kackwuerstchen said:
i have exactly the same problem but cant boot to twrp or to OS ...only download mode...tried to flash twrp again not worked now try to flash stock firmware via odin ....PLEASE HELP ME
Click to expand...
Click to collapse
I don't know what are you doing wrong but when I was stuck in this situation, I flashed stock firmware from sammobile and it fixed the problem.
Make sure you downloaded correct firmware.
Hi,
I know, its quite long time you solved this, but in which mode should be phone to use adb commands?
redirts1978 said:
This is how I solved it in the end.
With cable connected I did:
1. adb push boot.img /external_sd
2. adb shell
3. dd if=/external_sd/boot.img of=/dev/block/platform/155a0000.ufs/by-name/RECOVERY
4. fastboot format cache
5. fastboot format userdata
6. adb shell recovery --wipe_data
7. adb fastboot recovery
Notes:
The boot.img was obtained from a downloaded stock rom image and by decompressing the AP file (just open it with 7Zip) and then you need to uncompress boot.img.lz4 with 7zip zstandard (look it up)
Step 1 took sometime to run since TWRP was stuck loading using a lot of CPU as phone was really really hot!
Sometime I needed to do a adb fastboot recovery and then quickly run and rerun command in step 1 until it succeeded.
Step 6 is redundant but is there just to be safe.
After this you are booted back to a stock recovery where you can use Odin to flash what you want.
In my case I flashed a stock rom and then flashed TWRP again.
Click to expand...
Click to collapse
dankovac1999 said:
Hi,
I know, its quite long time you solved this, but in which mode should be phone to use adb commands?
Click to expand...
Click to collapse
Same problem and question here

Can't flash via TWRP, "failed mount system", twrp sideload not working either.. stuck

Can't flash via TWRP, "failed mount system", twrp sideload not working either.. stuck
I need my phone for work tomorrow so any help would be greatly appreciated.
I'm on TWRP 3.2.3-1 and was using the latest stock oreo rom from here: https://forum.xda-developers.com/g5...o-twrp-flashable-stock-builds-coming-t3830482
My phone suddenly didn't have a reception today, after rebooting I regained reception but couldn't make calls. I rebooted to recovery and tried to dirty flash the same stock twrp flashable oreo rom that I was using and it failed. Apparently the OS got corrupted. I tried repeatedly to flash the ROM and then noticed I was getting an error : failed to mount system , invalid argument. I couldn't mount system via the Mount tab in TWRP and I couldn't find anything helpful to resolve this error.
I did some more research downloaded the fastboot flashable ROM from here : https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-fastboot-flash-stock-oreo-t3848433 and tried to flash the rom via adb using adb sideload in twrp but twrp doesn't seem to load that function correctly. In the elevated command prompt in the adb directory I type adb sideload filename.zip and it just freezes up my PC. My device does show up with the adb devices command and shows " *Serial Number* RECOVERY ".
I don't understand what to do with the instructions in the fastboot flash stock thread I posted above and I'm at the limit of my knowledge. No idea how to proceed... any help is greatly appreciated.
I tried extracting the xml.zip into the adb folder and rebooted to bootloader/AP Fastboot Flash Mode and was going to try the commands in the fastboot Rom thread but my device only shows up in adb devices when I load twrp. uhhhhgggghhhhhh guess I'll have to buy a backup phone tomorrow while I try to get this one working
Holy hell.... I didn't realize since I was in the fastboot/bootloader I had to use "fastboot devices" command to see the device. Tried that and saw the device listed, so I created a .bat file using the commands in the fastboot roms thread above and I have a functional device again. Whohoooooo!
Did you try to format /System/ as EXT4?

How To Completely Remove TWRP and Return to Full Stock

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

Categories

Resources