hello-
i recently tried to root my wi-fi Nexus 9 following the directions i found in this post. (at the time i was running 5.1.1). at the completion of the process my tablet went into an infinite loop of
"Starting apps"
rebooting
"Starting apps"
rebooting
...
in order to revert, i tried to re-flash the stock 5.1.1 image (LMY47X). my N9 originally came with 5.0.1 installed, so i flashed this when i originally got it in order to upgrade to 5.1.1. simply running the flash-all.sh script didn't work for me, however, so i unzipped the image-volantis-lmy47x.zip file and ran the following commands in this order:
flash-all.sh (up to the point it fails)
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash vendor vendor.img
however, this process now fails on #2 with the following message:
Code:
> fastboot flash system system.img
target reported max download size of 518205818 bytes
erasing 'system'...
OKAY [ 0.437s]
sending sparse 'system' (499123 KB)...
ERROR: usb_write failed with status e00002ed
ERROR: usb_write failed with status e000404f
ERROR: usb_write failed with status e000404f
...
upon encountering this error the shell just hangs seemingly indefinitely (i waited for 15min before i finally ctrl-c'ed).
i also tried skipping flashing system.img and moving along with the rest of the steps, but i also encounter this problem when flashing vendor.img.
Code:
> fastboot flash vendor vendor.img
target reported max download size of 518205818 bytes
sending 'userdata' (144698 KB)...
ERROR: usb_write failed with status e00002ed
FAILED (data transfer failure (No such file or directory))
finished. total time: 0.914s
i'd be thankful for any advice anyone can give me on how to get this thing back up and running!
hsl43 said:
hello-
i recently tried to root my wi-fi Nexus 9 following the directions i found in this post. (at the time i was running 5.1.1). at the completion of the process my tablet went into an infinite loop of
"Starting apps"
rebooting
"Starting apps"
rebooting
...
in order to revert, i tried to re-flash the stock 5.1.1 image (LMY47X). my N9 originally came with 5.0.1 installed, so i flashed this when i originally got it in order to upgrade to 5.1.1. simply running the flash-all.sh script didn't work for me, however, so i unzipped the image-volantis-lmy47x.zip file and ran the following commands in this order:
flash-all.sh (up to the point it fails)
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash vendor vendor.img
however, this process now fails on #2 with the following message:
Code:
> fastboot flash system system.img
target reported max download size of 518205818 bytes
erasing 'system'...
OKAY [ 0.437s]
sending sparse 'system' (499123 KB)...
ERROR: usb_write failed with status e00002ed
ERROR: usb_write failed with status e000404f
ERROR: usb_write failed with status e000404f
...
upon encountering this error the shell just hangs seemingly indefinitely (i waited for 15min before i finally ctrl-c'ed).
i also tried skipping flashing system.img and moving along with the rest of the steps, but i also encounter this problem when flashing vendor.img.
Code:
> fastboot flash vendor vendor.img
target reported max download size of 518205818 bytes
sending 'userdata' (144698 KB)...
ERROR: usb_write failed with status e00002ed
FAILED (data transfer failure (No such file or directory))
finished. total time: 0.914s
i'd be thankful for any advice anyone can give me on how to get this thing back up and running!
Click to expand...
Click to collapse
Google updated the Android SDK (fastboot) in November of last year to enable flashing the extremely large Lollipop system.img files.
Update your Android SDK to the latest and you should be good to go.
FWIW: flash_all does not work.
RESOLVED. for the benefit of anybody else that may run into this problem...
after much Google sleuthing and gnashing of teeth, it turns out the solution was... to simply switch which USB port on my laptop the cable was plugged into. for the life of me, i don't know why, but i'll take it.
thanks @cam30era for your reply! your recommendation may have been a part of the solution, but as a developer, i keep my SDK reasonably up-to-date, so that particular issue didn't come into play in this instance. nonetheless, thanks very much again for taking the time to provide that info!
hi all so I read through many many posts i am 100% clear on the procedures of unlocking bootloader so i got permission from unlocking already log in to i.mi.com already double checked both phone and the unlock tool is same mi account but i am still getting 50% stuck error, checked driver is udpated, anyone has any actual solution to this? I see many people unlock it with zero problem am i missing anything?
Had this problem for weeks.
Only thing that actually worked is to flash the developer rom, try, it will complete.
Then flash back to the stable rom, pain in the arse I know, but save your time and try it.
en.miui.com/download-299.html
Make sure that you are on the developer ROM .
And it took me 2-3 days more to unlock my phone after getting confirmation from Xiaomi. Wait for 2-3 days so that their server gets updated.
edhahaha said:
hi all so I read through many many posts i am 100% clear on the procedures of unlocking bootloader so i got permission from unlocking already log in to i.mi.com already double checked both phone and the unlock tool is same mi account but i am still getting 50% stuck error, checked driver is udpated, anyone has any actual solution to this? I see many people unlock it with zero problem am i missing anything?
Click to expand...
Click to collapse
What ROM do you have?
i was at chinese stable, i flashed to latest developer chinese, 6.10.20 , doesn't work, then tried 6.10.13, samething, and i waited 2-3 days already.
edhahaha said:
i was at chinese stable, i flashed to latest developer chinese, 6.10.20 , doesn't work, then tried 6.10.13, samething, and i waited 2-3 days already.
Click to expand...
Click to collapse
Did you tried with developer global ?
If don't work, try with developer global MIUI7 . Worked for me.
You must be signed into the MIUI account on your device that you are using on the unlock application also.
Here are the steps i followed
1. I was on global stable ROM, flashed global developer ROM
2. login with Mi Account Id, not email or mobile number on phone as well as the unlock tool
3. Now I'm able to unlock the bootloader
4. Install Stable rom again if needed, I flashed it and my bootloader remained unlocked
The thing is,
Maybe you can try to check the lock status as well,
Mine showing 50% error several times,
But when i do "fastboot oem device-info"
It said that the BL was unlocked already,
I dont know how, but it seems the unlock was actually went through even when it show error
You have to be on a developer ROM, chinese or global doesn't matter.
If you're currently on chinese stable, you can switch to chinese developer. But if you're on Global stable, you can only switch to Global developer.
Hello. I had the same problem and I assume you have checked every single guide out there as well. I got around it when I changed my computer and unlock using the new computer. Maybe you can try doing the same thing and use your friend's laptop to unlock BL. To make sure there's no computer issue make sure to install ADB and Fastboot driver and check if your computer can detect your device in Fastboot mode (there has to be a guide out there, try google). Cheers
Hi, I run into the same issue on win 10 and also installed the android sdk to get the drivers.
Device Mi5 Pro
Latest chinese dev 6.10.20 (MIUI8)
I can find the device with fastboot, however "fastboot getvars" fail all the times with the same error:
Code:
fastboot getvar all
getvar:all FAILED (command write failed (Unknown error))
Thus the mi unlocker tool runs into the same issues:
Code:
DEBUG <11:15:16.127,T:5796> : Initializing native downloader...
INFO <11:15:16.127,T:5796> : init resource C:\Users\ose\Downloads\MiFlashUnlock_1.1.0317.1_en\res\ language:en region:
ERROR <11:15:17.003,T:2000> : product: return:getvar:product FAILED (command write failed (Unknown error))
ERROR <11:15:17.648,T:2000> : soc-id: return:getvar:soc-id FAILED (command write failed (Unknown error))
ERROR <11:15:18.294,T:2000> : soc_id: return:getvar:soc_id FAILED (command write failed (Unknown error))
ERROR <11:15:18.993,T:2000> : board_version: return:getvar:board_version FAILED (command write failed (Unknown error))
ERROR <11:15:18.993,T:2000> : Can't identify device in fastboot mode.(num=0)
INFO <11:15:34.057,T:4264> : to login by name:XXX pwd:XXX sid:XXX verify:EMPTY sec_token:EMPTY
INFO <11:15:34.090,T:4264> : LoginStep1
DEBUG <11:15:37.791,T:4264> : OnAccountLoggedIn
DEBUG <11:15:43.173,T:4264> : OnNewServiceCookies
DEBUG <11:15:43.173,T:4264> : Login success and get user detail
INFO <11:15:49.223,T:2032> : status result: {
"applyStatus" : 2,
"code" : 0,
"description" : null,
"shouldApply" : true,
"uid" : 1554152998
}
DEBUG <11:15:49.223,T:2032> : unlock status: 2
DEBUG <11:15:49.223,T:2032> : should apply:true
INFO <11:15:53.357,T:5796> : connected
DEBUG <11:15:56.569,T:10612> : VerifyDeviceInfo
ERROR <11:15:57.230,T:10612> : product: return:getvar:product FAILED (command write failed (Unknown error))
ERROR <11:15:57.873,T:10612> : soc-id: return:getvar:soc-id FAILED (command write failed (Unknown error))
ERROR <11:15:58.516,T:10612> : soc_id: return:getvar:soc_id FAILED (command write failed (Unknown error))
ERROR <11:15:59.215,T:10612> : board_version: return:getvar:board_version FAILED (command write failed (Unknown error))
ERROR <11:15:59.215,T:10612> : Can't identify device in fastboot mode.(num=0)
WARNING<11:15:59.215,T:10612> : cannot get product info again
ERROR <11:18:15.927,T:2000> : product: return:getvar:product FAILED (command write failed (Unknown error))
ERROR <11:18:16.589,T:2000> : soc-id: return:getvar:soc-id FAILED (command write failed (Unknown error))
ERROR <11:18:17.233,T:2000> : soc_id: return:getvar:soc_id FAILED (command write failed (Unknown error))
ERROR <11:18:17.935,T:2000> : board_version: return:getvar:board_version FAILED (command write failed (Unknown error))
ERROR <11:18:17.936,T:2000> : Can't identify device in fastboot mode.(num=0)
ERROR <11:18:19.035,T:2000> : product: return:getvar:product FAILED (command write failed (Unknown error))
ERROR <11:18:19.677,T:2000> : soc-id: return:getvar:soc-id FAILED (command write failed (Unknown error))
ERROR <11:18:20.319,T:2000> : soc_id: return:getvar:soc_id FAILED (command write failed (Unknown error))
ERROR <11:18:21.025,T:2000> : board_version: return:getvar:board_version FAILED (command write failed (Unknown error))
ERROR <11:18:21.025,T:2000> : Can't identify device in fastboot mode.(num=0)
I also cannot go back to a Global stable/dev rom, using the updater.
Any advises?
My phone is rooted and unlocked. I have installed adb and fastboot. I had twrp installed and I used it to install a custom rom. Then, I accidentally flashed something (maybe update.zip?) that not only changed the regular system partition, but also the recovery partition. I've been trying to get twrp back and I'm having major issues.
When I try the command "fastboot erase recovery" I receive the following error message:
erasing 'recovery'...
ERROR: usb_read failed with status e00002e8
FAILED (status read failed (Invalid argument))
finished. total time: 0.005s
I've searched google with several different parameters and nothing is helping me, so I figure best to post my own question. I get the same error and status e00002e8 when trying to flash recovery.img or boot.img
Perform the following procedure to add root to my ASUS MemoPad FHD 10 Model ME302C tablet, following the tutorial:
https://forum.xda-developers.com/showthread.php?t=2716296
When installing the TWRD recovery or reinstalling the system by default the following appears to me.
Error
CMD Console:
fastboot erase cache
fastboot erase userdata
fastboot flash update US_ME302C-V5.0.16-0-ota-user.zip
Console log:
sending 'update' (750959 KB)...
OKAY [ 85.831s]
writing 'update'...
FAILED (remote: problem with creating ota update file!)
finished. total time: 88.958s
E:Unable to rebane file /cache/update.zip: Cross-device link @
E:Unable to write file: /cache/update.zip
E:Update flash failed!
FLASH FAILED!
RESULT: FAIL(flash_cmds error!)
I can't install recovery. The default system of the ASUS page.
Do not start my tablet help please.
HELP ME!
I know there's so many threads made but I'm hoping someone can help me with my particular solution.
So I'm using the tutorial by this site which has worked so far and I've completed Part 1 (Unlocking the Bootloader).
My issue is, when I type the command: fastboot boot <insert_name_of_TWRP_image_here>.img
I get the following message:
(base) [email protected] android % ./fastboot boot twrp-3.2.3-0-blueline.img
Sending 'boot.img' (65536 KB) OKAY [ 0.287s]
Booting ERROR: usb_read failed with status e00002eb
FAILED (Status read failed (No such file or directory))
fastboot: error: Command failed
The .img file is definitely in the 'android' folder and I'm doing it correctly afaik because I've been able to unlock the Bootloader with no issue. Does anyone know what this message means?
Im definitely using the most up-to-date twrp file, I'm on a MacBook and my phone is a Pixel 3.
Thanks for any help!
MHuncho said:
I know there's so many threads made but I'm hoping someone can help me with my particular solution.
So I'm using the tutorial by this site which has worked so far and I've completed Part 1 (Unlocking the Bootloader).
My issue is, when I type the command: fastboot boot <insert_name_of_TWRP_image_here>.img
I get the following message:
(base) [email protected] android % ./fastboot boot twrp-3.2.3-0-blueline.img
Sending 'boot.img' (65536 KB) OKAY [ 0.287s]
Booting ERROR: usb_read failed with status e00002eb
FAILED (Status read failed (No such file or directory))
fastboot: error: Command failed
The .img file is definitely in the 'android' folder and I'm doing it correctly afaik because I've been able to unlock the Bootloader with no issue. Does anyone know what this message means?
Im definitely using the most up-to-date twrp file, I'm on a MacBook and my phone is a Pixel 3.
Thanks for any help!
Click to expand...
Click to collapse
Hi,
That might be a simple answer but try to add the full path of the file at the end of the command :
./fastboot boot [drag the file and drop it next to the word "boot" to have its full path written down without any typos]
Let me know what you get