Related
This is for Re-locking and Un-Rooting the US WIFI Xoom BUILD HWI69 ONLY
This is for use only on the Wifi-Only Xoom HWI69 build. Check your build number before you install!!!
Please note the following information does contain official Motorola images from a non Motorola source. The information in this thread has been tested, however I can not confirm that it will work for every situation. In no way will I or xda-developers.com be held accountable for any damage resulting from using this information. Use the following with extreme caution.
1. Download the necessary files from here:
http://www.android.net/forum/downloads.php?do=file&id=39
2. Unzip the files to the directory you will be running ADB from.
3. Enter the following commands into the command prompt
adb reboot bootloader
Xoom will then reboot into bootloader screen
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
After the final reboot you should be back to stock, Locked and Un-Rooted.
note: If you are using Terminal on a mac your commands should include a ./ before every command like this:
./adb reboot bootloader
Xoom will then reboot into bootloader screen
./fastboot flash boot boot.img
./fastboot flash system system.img
./fastboot flash recovery recovery.img
./fastboot flash userdata userdata.img
./fastboot erase cache
./fastboot oem lock
Credits go to Steady Hawkin on xoomforums.com
first of all, there is no hw169, it's a hwi69!
second, did u try this? b-coz last time when i try it, my xoom die
third in os x terminal commands is same like windows one
Last login: Wed May 18 22:11:38 on ttys000
Hooligans:~ Hooligan$ ./adb reboot bootloder
-bash: ./adb: No such file or directory
Hooligans:~ Hooligan$ adb reboot bootloder
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Click to expand...
Click to collapse
HooliganBG said:
first of all, there is no hw169, it's a hwi69!
second, did u try this? b-coz last time when i try it, my xoom die
third in os x terminal commands is same like windows one
Click to expand...
Click to collapse
fixed build number, thanks for that! ya i just did it yesterday and worked no problem.
everytime i run commands in terminal on my mac i have to put the ./ or else it wont work, never worked for me just typing it in normally
I just tried this and it works great! Excellent work OP!
After unrooting and unlocking and My 3.1 updates kicked in right away..... I think I will be running stock for a while
I flashed 3.1 from clockwork. Will this still work? Does the Xoom check for version before booting? like some HTC and Motorola phones?
Buddhahb said:
I flashed 3.1 from clockwork. Will this still work? Does the Xoom check for version before booting? like some HTC and Motorola phones?
Click to expand...
Click to collapse
check your build number in settings>about phone, it has to be HWI69 in order for this to work
I have that model. I was just making sure it wouldn't be a problem that I hate flashed the 3.1 update
what format are these imgs in?
I am trying to unyaffs them but it is not the right format
Your trying to what?
The build number does not matter. All that matters is you flash official images for YOUR device. For example the US wifi images on a us wifi device. The same goes for the 3g. Just do not relock the bootloader with out those images flash onto the device.
In a year from now your device could be running ice cream sandwich with who knows what build number. Unlocked bootloader = flash back official images when ever you want.
Sent from my Xoom using Tapatalk
I am trying to get the data out (on my pc)
I lost all the default stuff that come with the xoom.
Does doing the ota to android 3.1 change build number from HWI69 to HMJ37?
worked nice thanks man... sad to say im taking this thing back today to get the less cool looking transformer for 200 dollars less... same thing just looks not as cool... supposedly screen display is better too... thanks again..
yes it does... ur wifi onnly us xoom should have been that to begin with before the ota...
Video for Noobs
Made a video using this Tutorial for anyone interested.
http://www.youtube.com/watch?v=pT8NF-_nLCo
Gave all credit to those it belongs to.
Tried this last night but used HMJ37 instead of HWI69 and got myself into a weird situation where it wouldn't boot (stuck on Dual Core screen). Had to power off and use vol+ to get to fast boot and unlock again.
Is HWI69 the only build that can be oem locked ?
-Matt
Thanks!
Worked perfectly, thank you for taking the time to post this useful thread.
Code:
c:\android-sdk-windows>adb reboot bootloader
* daemon not running. starting it now *
* daemon started successfully *
c:\android-sdk-windows>cd tools
c:\android-sdk-windows\tools>fastboot flash boot boot.img
sending 'boot' (8192 KB)... OKAY [ 1.039s]
writing 'boot'... OKAY [ 2.139s]
finished. total time: 3.179s
c:\android-sdk-windows\tools>fastboot flash system system.img
sending 'system' (262144 KB)... OKAY [ 27.063s]
writing 'system'... OKAY [ 14.166s]
finished. total time: 41.231s
c:\android-sdk-windows\tools>fastboot flash recovery recovery.img
sending 'recovery' (12288 KB)... OKAY [ 1.427s]
writing 'recovery'... OKAY [ 2.038s]
finished. total time: 3.466s
c:\android-sdk-windows\tools>fastboot flash userdata userdata.img
sending 'userdata' (139233 KB)... OKAY [ 13.288s]
writing 'userdata'... OKAY [ 21.292s]
finished. total time: 34.582s
c:\android-sdk-windows\tools>fastboot erase cache
erasing 'cache'... OKAY [ 1.615s]
finished. total time: 1.616s
c:\android-sdk-windows\tools>fastboot oem lock
... INFO To continue, follow instructions on the d
evice's display...
OKAY [101.907s]
finished. total time: 101.908s
So I got my Kindle Fire a few months ago, already rooted. I went from TWRP to a CWM-based recovery, and I've been installing ROMs ever since without any issues. I'm currently running a CM9-based ROM, and I decided to play around with the softkeys, because I was tired of the bland white look. So I found some custom softkeys and flashed the .zip. I made sure to make a Nandroid before flashing, of course.
Upon rebooting from the flash, my KF got stuck in a bootloop. No biggie, this has happened before. I shut it down and rebooted to recovery, to restore the backup. But when it boots into recovery, it automatically reflashes the softkeys zip, and then reboots into the never-ending bootloop.
So the KF isn't necessarily bricked, I just can't get into recovery without it flashing a corrupted zip. I've tried two different unbricking tools, neither had any effect on it. Any ideas?
Can you mount SD card in Recovery and delete the Zip file through your PC?
linktohack said:
Can you mount SD card in Recovery and delete the Zip file through your PC?
Click to expand...
Click to collapse
I only wish I could. As soon as I boot into recovery, it flashed the zip, then reboots into the bootloop. I suspect this happens because I used ROM Manager to flash the zip, and recovery hasn't reset itself because the device isn't booting up all the way. So every time I try to access recovery, it performs the last action I gave it, which was to flash the zip.
I hope you aren't using Hashcode's (older) CWMR or you might be looking at a much larger problem.
http://forum.xda-developers.com/showthread.php?t=1651413
I'm not sure what's going on with your device, but the only way I know to get the recovery to do something on start up is to create a /cache/recovery/command file. That file should be a one time use command and get deleted after use, so your report of it happening each time you boot into recovery is puzzling.
If you want to take that out of the equation, I think you should either get to a shell prompt and delete the file manually or erase the cache partition entirely. Try getting to fastboot mode, boot a copy of the TWRP image, and hopefully it won't reboot on you automatically so you can use adb shell. Alternatively, erase the cache partition entirely with fastboot. If you do the latter, you'll probably need to remake the ext4 filesystem on the cache partition. Here are some fastboot references to get you started...
http://forum.xda-developers.com/showthread.php?t=1668159
http://forum.xda-developers.com/showpost.php?p=23747804&postcount=3
kinfauns said:
I hope you aren't using Hashcode's (older) CWMR or you might be looking at a much larger problem.
http://forum.xda-developers.com/showthread.php?t=1651413
I'm not sure what's going on with your device, but the only way I know to get the recovery to do something on start up is to create a /cache/recovery/command file. That file should be a one time use command and get deleted after use, so your report of it happening each time you boot into recovery is puzzling.
If you want to take that out of the equation, I think you should either get to a shell prompt and delete the file manually or erase the cache partition entirely. Try getting to fastboot mode, boot a copy of the TWRP image, and hopefully it won't reboot on you automatically so you can use adb shell. Alternatively, erase the cache partition entirely with fastboot. If you do the latter, you'll probably need to remake the ext4 filesystem on the cache partition. Here are some fastboot references to get you started...
http://forum.xda-developers.com/showthread.php?t=1668159
http://forum.xda-developers.com/showpost.php?p=23747804&postcount=3
Click to expand...
Click to collapse
Thanks for all that, but I managed to fastboot into it, and then wipe system and data. Then I rebooted to recovery and restored my backup. Never fastbooted into a device before, or done anything with adb commands, so it was a fun experience.
same symptoms: KF bootlooping, no recovery
Hi there,
I have a rooted/modded KF with MIUI, FFF 1.4a and TWRP.
After I gave it away to someone, who only "used it", it is now stuck in a bootloop.
I can get into fastboot via fastboot.exe and re-flashed FFF and TWRP, but no change: KF boots with the white/blue logo, I can press the powerbutton to get into recovery, but TWRP doesn´t show up. When I boot normally, it looks the same: Black screen after a few seconds.
I read about the battery issues, so I booted the KF with a fastboot command waiting to the device. The white/blue KF logo showd up and I left the device at the USB port at my PC for a complete night: no change
I tried to set another bootmode via fastboot.exe but the code doesn´t seem to make any difference.
I have a second KF which runs just fine (now with AOKP M5.1).
Is it bricked now?
Elviz42 said:
Hi there,
I have a rooted/modded KF with MIUI, FFF 1.4a and TWRP.
After I gave it away to someone, who only "used it", it is now stuck in a bootloop.
I can get into fastboot via fastboot.exe and re-flashed FFF and TWRP, but no change: KF boots with the white/blue logo, I can press the powerbutton to get into recovery, but TWRP doesn´t show up. When I boot normally, it looks the same: Black screen after a few seconds.
I read about the battery issues, so I booted the KF with a fastboot command waiting to the device. The white/blue KF logo showd up and I left the device at the USB port at my PC for a complete night: no change
I tried to set another bootmode via fastboot.exe but the code doesn´t seem to make any difference.
I have a second KF which runs just fine (now with AOKP M5.1).
Is it bricked now?
Click to expand...
Click to collapse
I'm not an expert on the KF, but from what you've described, I don't think it's bricked. Have you tried fastboot wiping system and data?
Mardenator said:
I'm not an expert on the KF, but from what you've described, I don't think it's bricked. Have you tried fastboot wiping system and data?
Click to expand...
Click to collapse
I just did:
D:\root>tools\fastboot erase system
erasing 'system'... OKAY [ 51.245s]
finished. total time: 51.246s
D:\root>tools\fastboot erase data
erasing 'data'... FAILED (remote: : partition doesn't exist)
finished. total time: 0.002s
D:\root>tools\fastboot erase userdata
erasing 'userdata'... OKAY [108.555s]
finished. total time: 108.577s
D:\root>tools\fastboot reboot
rebooting...
finished. total time: 0.001s
D:\root>
I tried to get into Recovery but no change.
Maybe it's a problem with TWRP. Have you tried fastboot flashing a CWM-based recovery?
Doesnt sound like you have twrp installed or its broken just resend twrp it should overwrite whatever is there
Thepooch said:
Doesnt sound like you have twrp installed or its broken just resend twrp it should overwrite whatever is there
Click to expand...
Click to collapse
He might want to fastboot erase recovery and then reflash TWRP.
I tried CWM:
D:\root>tools\fastboot flash boot recovery\fff.bin
sending 'boot' (243 KB)... OKAY [ 0.065s]
writing 'boot'... OKAY [ 0.052s]
finished. total time: 0.117s
D:\root>tools\fastboot flash recovery recovery\cwm.img
sending 'recovery' (5198 KB)... OKAY [ 1.321s]
writing 'recovery'... OKAY [ 1.418s]
finished. total time: 2.740s
D:\root>tools\fastboot oem idme bootmode 5001
... OKAY [ 0.667s]
finished. total time: 0.668s
D:\root>tools\fastboot reboot
rebooting...
finished. total time: 0.002s
D:\root>
No change, same behavior: Starts with white/blue letters and than "off". Entering recovery is not working.
Are you pushing the power button several times quickly when you see the white kindle blue fire and selecting recovery?
---------- Post added at 11:51 AM ---------- Previous post was at 11:49 AM ----------
You need to select with the power button or the new fff will just tell it to boot normal also twrp is better if you intend to flash anything ics related
Thepooch said:
Are you pushing the power button several times quickly when you see the white kindle blue fire and selecting recovery?
Click to expand...
Click to collapse
Yes. I also tried to enter recovery just by setting bootmode to 5001 with fastboot. This didn´t work either.
Try setting the bootmode to normal then use the power button to toggle to recovery after reflashing twrp also how your flashing them is incorrect
---------- Post added at 12:09 PM ---------- Previous post was at 12:00 PM ----------
fastboot -i 0x1949 flash recovery <file path> <name of recovery>
fastboot -i 0x1949 flash bootloader<file path><name of bootloader>
not fff.bin to recovery as you are doing but to bootloader
D:\root>tools\fastboot flash boot recovery\fff.bin
sending 'boot' (243 KB)... OKAY [ 0.065s]
writing 'boot'... OKAY [ 0.052s]
finished. total time: 0.117s
this one is really wrong your flashing the bootloader to the recovery partition dunno your doing something strange and thats your issue
you may wanna use firekit to get your bootloader and recovery correctly sent to avoid further issues http://forum.xda-developers.com/showthread.php?t=1430038
or like this leaving the id out
fastboot flash bootloader \path\to\fff.bin
fastboot flash recovery \path\to\twrp.img
Hi,
i did flash fff.img to boot(loader) , and after that CWM.img to recovery. But the image is in a folder called "recovery", perhaps this was confusing.
you wrote that you flashed it to boot not bootloader but yes its confusing
try again after an erase I guess
fastboot erase bootloader
fastboot erase recovery
or with the id -i 0x1949
Did that, no success:
D:\root>tools\fastboot getvar product
< waiting for device >
product: kindle
finished. total time: 0.000s
D:\root>tools\fastboot erase bootloader
erasing 'bootloader'... OKAY [ 0.511s]
finished. total time: 0.512s
D:\root>tools\fastboot erase recovery
erasing 'recovery'... OKAY [ 2.429s]
finished. total time: 2.429s
D:\root>tools\fastboot flash bootloader recovery\fff.bin
sending 'bootloader' (243 KB)... OKAY [ 0.065s]
writing 'bootloader'... OKAY [ 0.052s]
finished. total time: 0.117s
D:\root>tools\fastboot flash recovery recovery\openrecovery-twrp-blaze-2.1.1.img
sending 'recovery' (5568 KB)... OKAY [ 1.404s]
writing 'recovery'... OKAY [ 0.543s]
finished. total time: 1.947s
D:\root>tools\fastboot reboot
rebooting...
finished. total time: 0.001s
D:\root>
ok unplug it then hold your power button down for 1 min then power it on use power button to toggle to recovery option in boot menu see what you get if that doesnt work redownload twrp img and send that again without erase also there is a small chance you could be remaining in fastboot but I doubt it try select reset bootmode as well but you have no system at this point so getting to recovery is imperative
What does "fastboot boot twrp.img" do for you?
HTC One X won't boot. Somehow it stuck in bootloop while leaved unattended and spend all the battery.
Ok, I've read many threads here about the topic and after many different things tried (Power+VolUp under bright light, Charger batch script...)
I finally opened up the phone and disconnect battery, then charge the battery and tried fastboot...
So I manage to flash clockwork recovery but when try to get into recovery it stuck at HTC quietly brilliant screen
I figure, maybe I should flash original kernel (altough they shouldn't have to be linked) but flashing boot partition didn't work.
Code:
fastboot getvar battery-voltage
battery-voltage: 4052mV
finished. total time: 0.100s
fastboot flash recovery clockwork-touch-5.8.4.0-endeavoru.img
sending 'recovery' (5742 KB)...
OKAY [ 0.745s]
writing 'recovery'...
(bootloader) Format partition SOS done
OKAY [ 0.539s]
finished. total time: 1.285s
fastboot flash boot boot.img
and after last command I get error in syslogs
usbfs: USBDEVFS_CONTROL failed cmd fastboot rqt 128 rq 6 len 254 ret -110
(that's linux)
In windows,
Code:
fastboot flash boot kernel.img
sending 'boot' (6008KB)...
OKAY [ 0.811s]
writing 'boot'...
(bootloader) Format partition LNX done
and stays like that
After 10mins waiting I disconnected USB cable and get
Code:
FAILED (status read failed (Too many links ))
finished. total time: 621.177s
Should I just relock bootloader and try some RUU update or try something else?
I'm afraid, since flashing boot won't finish, that some problems may occur during RUU update and then... bye bye HOX :crying:
freedom74 said:
HTC One X won't boot. Somehow it stuck in bootloop while leaved unattended and spend all the battery.
Ok, I've read many threads here about the topic and after many different things tried (Power+VolUp under bright light, Charger batch script...)
I finally opened up the phone and disconnect battery, then charge the battery and tried fastboot...
So I manage to flash clockwork recovery but when try to get into recovery it stuck at HTC quietly brilliant screen
I figure, maybe I should flash original kernel (altough they shouldn't have to be linked) but flashing boot partition didn't work.
Code:
fastboot getvar battery-voltage
battery-voltage: 4052mV
finished. total time: 0.100s
fastboot flash recovery clockwork-touch-5.8.4.0-endeavoru.img
sending 'recovery' (5742 KB)...
OKAY [ 0.745s]
writing 'recovery'...
(bootloader) Format partition SOS done
OKAY [ 0.539s]
finished. total time: 1.285s
fastboot flash boot boot.img
and after last command I get error in syslogs
usbfs: USBDEVFS_CONTROL failed cmd fastboot rqt 128 rq 6 len 254 ret -110
(that's linux)
In windows,
Code:
fastboot flash boot kernel.img
sending 'boot' (6008KB)...
OKAY [ 0.811s]
writing 'boot'...
(bootloader) Format partition LNX done
and stays like that
After 10mins waiting I disconnected USB cable and get
Code:
FAILED (status read failed (Too many links ))
finished. total time: 621.177s
Should I just relock bootloader and try some RUU update or try something else?
I'm afraid, since flashing boot won't finish, that some problems may occur during RUU update and then... bye bye HOX :crying:
Click to expand...
Click to collapse
NO RUU for this Hboot and you flash too old recovery. After flashing the recovery run the command fastboot erase cache then flash the boot.img
Thant said:
NO RUU for this Hboot and you flash too old recovery. After flashing the recovery run the command fastboot erase cache then flash the boot.img
Click to expand...
Click to collapse
Should I use Philz-recovery
http://forum.xda-developers.com/showthread.php?t=2240646
and if everything goes well, meaning
Code:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot flash boot boot.img
I go back to HBOOT and choose RECOVERY in menu, right?
freedom74 said:
Should I use Philz-recovery
http://forum.xda-developers.com/showthread.php?t=2240646
and if everything goes well, meaning
Code:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot flash boot boot.img
I go back to HBOOT and choose RECOVERY in menu, right?
Click to expand...
Click to collapse
Yes. depend what you want to install I prefer Philz 5.15.9 there mount sd card work perfect.
Tried.
It stuck at
(bootloader) Format partition SOS done
Maybe <fastboot erase cache> before every operation should help?
But what's annoying me most is that when it stuck, there is no way I can get into bootloader but to disassemble the phone again and disconnect the battery and try again
Is there a way to get to bootloader without that?
freedom74 said:
Tried.
It stuck at
(bootloader) Format partition SOS done
Maybe <fastboot erase cache> before every operation should help?
But what's annoying me most is that when it stuck, there is no way I can get into bootloader but to disassemble the phone again and disconnect the battery and try again
Is there a way to get to bootloader without that?
Click to expand...
Click to collapse
change usb cable or usb port on the computer. Maybe faulty cable
@freedom74 what is your batter-voltage now?
Tried on two different computers, three different USB cables and ports... no rules whatsoever.
Anyway, now everything goes fine...
Code:
C:\adb>fastboot erase cache
erasing 'cache'...
OKAY [ 0.218s]
finished. total time: 0.234s
C:\adb>fastboot flash recovery recovery.img
sending 'recovery' (8050 KB)...
OKAY [ 1.139s]
writing 'recovery'...
(bootloader) Format partition SOS done
OKAY [ 0.655s]
finished. total time: 1.810s
C:\adb>fastboot erase cache
erasing 'cache'...
OKAY [ 0.218s]
finished. total time: 0.218s
C:\adb>fastboot flash boot boot.img
sending 'boot' (5086 KB)...
OKAY [ 0.764s]
writing 'boot'...
(bootloader) Format partition LNX done
OKAY [ 0.499s]
finished. total time: 1.264s
Then I disconnect USB cable, go to HBOOT and choose RECOVERY
it stuck on three android screen...
freedom74 said:
Tried on two different computers, three different USB cables and ports... no rules whatsoever.
Anyway, now everything goes fine...
Code:
C:\adb>fastboot erase cache
erasing 'cache'...
OKAY [ 0.218s]
finished. total time: 0.234s
C:\adb>fastboot flash recovery recovery.img
sending 'recovery' (8050 KB)...
OKAY [ 1.139s]
writing 'recovery'...
(bootloader) Format partition SOS done
OKAY [ 0.655s]
finished. total time: 1.810s
C:\adb>fastboot erase cache
erasing 'cache'...
OKAY [ 0.218s]
finished. total time: 0.218s
C:\adb>fastboot flash boot boot.img
sending 'boot' (5086 KB)...
OKAY [ 0.764s]
writing 'boot'...
(bootloader) Format partition LNX done
OKAY [ 0.499s]
finished. total time: 1.264s
Then I disconnect USB cable, go to HBOOT and choose RECOVERY
it stuck on three android screen...
Click to expand...
Click to collapse
wich recovery do you flash. Run again only the command fastboot erase cache and then try go in recovery
Thant said:
wich recovery do you flash. Run again only the command fastboot erase cache and then try go in recovery
Click to expand...
Click to collapse
The one you suggest... Philz 5.15.9
Code:
C:\adb>fastboot getvar battery-voltage
battery-voltage: 3976mV
finished. total time: 0.172s
C:\adb>fastboot erase cache
erasing 'cache'...
OKAY [ 0.218s]
finished. total time: 0.218s
C:\adb>fastboot erase cache
erasing 'cache'...
OKAY [ 0.234s]
finished. total time: 0.234s
C:\adb>
Stuck again, but now on "htc quietly brilliant" screen
freedom74 said:
The one you suggest... Philz 5.15.9
Click to expand...
Click to collapse
ok this is good are you run the command fastboot erase cache and then try to go in recovery
Go in bootloader with disconected phone from computer then choice recovery and confirm with power button
@freedom74 you must to put recovery.img and boot.img in your fastboot folder and then flash it
Thant said:
ok this is good are you run the command fastboot erase cache and then try to go in recovery
Go in bootloader with disconected phone from computer then choice recovery and confirm with power button
Click to expand...
Click to collapse
Did that... <fastboot erase cache> and then with disconnected phone tried to RECOVERY
Thant said:
you must to put recovery.img and boot.img in your fastboot folder and then flash it
Click to expand...
Click to collapse
@Thant As you can see from terminal output, that is the case.
freedom74 said:
Did that... <fastboot erase cache> and then with disconnected phone tried to RECOVERY
Click to expand...
Click to collapse
maybe bad download on the recovery try download again or flash TWRP2.8.0
Any suggestion/link for a kernel image?
Does it matters anyway?
@Thant
Done it with TWRP 2.8.0.0... shows "htc quietly brilliant" for a few sec and screen goes black...
freedom74 said:
Any suggestion/link for a kernel image?
Does it matters anyway?
@Thant
Done it with TWRP 2.8.0.0... shows "htc quietly brilliant" for a few sec and screen goes black...
Click to expand...
Click to collapse
try again with fastboot erase cache and then go in recovery the black screen means the phone try to go in recovery
Thant said:
try again with fastboot erase cache and then go in recovery the black screen means the phone try to go in recovery
Click to expand...
Click to collapse
Still nothing...
HTC screen, then goes black, phone vibrates, then again HTC screen... stays for a minute and then again, vibrates, HTC screen and stays
freedom74 said:
Still nothing...
HTC screen, then goes black, phone vibrates, then again HTC screen... stays for a minute and then again, vibrates, HTC screen and stays
Click to expand...
Click to collapse
no I am sure you don't do something right try again redownload CWM or TWRP check the MD5SUM then flash it don.t flash boot.img.
1. Delete all img files from your fastboot folder
2. Paste only your ecovery.img file there and rename it to recovery.img
3. run fastboot flash recovery recovery.img
4. run fastboot erase cache
5. Powerdown the power from bootloader manu and disconnect the phone from computer
6. Press and hold volume down and then press and hold power button until you go in bootloader, choice recovery and press power button
7. Report
Don't flash any boot.img or other things only recovery. If you go in recovery then install the rom and then and last flash the boot.img from rom.archive
Thant said:
Don't flash any boot.img or other things only recovery. If you go in recovery then install the rom and then and last flash the boot.img from rom.archive
Click to expand...
Click to collapse
Done exactly as you said...
When powerdown from bootloader menu, red LED turned on before I disconnect USB cable.
When cable was disconnected red LED stays ON.
I tried Power+VolDn - nothing
Long press Power after 10sec turn red LED off.
Tried again Power+VolDn to get into bootloader but without success.
I disconnect the battery and will try another round...
freedom74 said:
Done exactly as you said...
When powerdown from bootloader menu, red LED turned on before I disconnect USB cable.
When cable was disconnected red LED stays ON.
I tried Power+VolDn - nothing
Long press Power after 10sec turn red LED off.
Tried again Power+VolDn to get into bootloader but without success.
I disconnect the battery and will try another round...
Click to expand...
Click to collapse
You don't do the things as I say. Read again point 6
Press and hold FIRST THE VOLUME DOWN then PRESS and HOLD THE POWER BUTTON until you go in bootloader
And why you don't disconnect the cable from PC and with the volume down go to Power Down option in bootloader and press Power button to confirm this will turn off your phone
Thant said:
You don't do the things as I say. Read again point 6
Press and hold FIRST THE VOLUME DOWN then PRESS and HOLD THE POWER BUTTON until you go in bootloader
Click to expand...
Click to collapse
As I wrote eariler, I've done exactly as you said.
I know the combo for entering bootloader and I know it suppose to be first VolDn and then Power.
My Power+VolUp in previous post does not show the order I pressed the key. Sorry for me not being clear enough.
Thant said:
And why you don't disconnect the cable from PC and with the volume down go to Power Down option in bootloader and press Power button to confirm this will turn off your phone
Click to expand...
Click to collapse
I am disconnecting, but since you wrote
5. Powerdown the power from bootloader manu AND disconnect the phone from computer
Click to expand...
Click to collapse
I was follow that order, first powerdown from menu and then disconnect.
In that case red LED turn on before I was able to disconnect the USB cable.
I will try to first disconnect USB cable so that phone goes back from FASTBOOT USB into just FASTBOOT and then power down from menu.
And then VolDn+Power to enter bootloader and recovery.
My battery drop to 3.700mV so I need to recharge it a while.
p.s.
Thanks for your help and time.
No progress. Always ending at "htc quietly brilliant" screen.
I will try different recoveries with same steps but I don't see why would other work
when twrp 2.8.0.0 with good md5sum does not.
Code:
C:\Android>fastboot.exe getvar battery-voltage
battery-voltage: 3698mV
finished. total time: 0.109s
C:\Android>fastboot.exe flash recovery recovery.img
sending 'recovery' (6536 KB)...
OKAY [ 0.842s]
writing 'recovery'...
(bootloader) Format partition SOS done
OKAY [ 0.577s]
finished. total time: 1.420s
C:\Android>fastboot.exe erase cache
erasing 'cache'...
OKAY [ 0.218s]
finished. total time: 0.234s
C:\Android>
Hi,
i unlocked my bootloader using the original LG tool (unlock.bin).
fastboot getvar unlocked:
[[email protected] Desktop]# fastboot getvar unlocked
unlocked: yes
finished. total time: 0.004s
[[email protected] Desktop]#
Then i booted into bootloader using adb reboot bootloader.
fastboot flash recovery twrp-2.8.6.1-h815.img
gave me no error.
[[email protected] Desktop]# fastboot flash recovery twrp-2.8.6.1-h815.img
target reported max download size of 536870912 bytes
sending 'recovery' (32060 KB)...
OKAY [ 1.022s]
writing 'recovery'...
OKAY [ 0.287s]
finished. total time: 1.309s
[[email protected] Desktop]#
Now when i restart the phone using adb reboot recovery i get the "dead android" logo. No key combination works.
When booting using the Power+Vol-Down, the phone enters the reset menu. I select twice "YES", but TWRP is not started, and the phone is empty
Any idea?
Thanks
i went through the exact scenario, and found the solution myself, you're typing the wrong command, take the battery out, plug your phone into bootloader/fastboot mode or do it via adb
adb reboot bootloader
then flash the recovery again just to be safe
then either type fastboot boot twrp-2.8.6.1-h815.img
or adb boot twrp-2.8.6.1-h815.img
Dear all,
I'd like to install LineageOS on my Xiaomi Mi 10 Lite (monet).
I'm following the instructions here : https://wiki.lineageos.org/devices/monet/install.
Everything is going well until step "fastboot flash recovery <recovery_filename>.img".
I type "fastboot flash recovery <recovery_filename>.img" and everything seems to be good.
Sending 'recovery' (131072 KB) OKAY [ 4.907s]
Writing 'recovery' OKAY [ 0.571s]
Finished. Total time: 5.484s
But my phone does not power down. And when I try to reboot into the recovery mode (Volume Up + Power), the fastboot screen appears instead of recovery mode.
I also try with "fastboot boot <recovery_filename>.img".
Sending 'boot.img' (131072 KB) OKAY [ 5.044s]
Booting OKAY [ 0.154s]
Finished. Total time: 5.266s
The phone turns off and I reboot into recovery mode with success. I apply "Wipe Data" and go back to Main Menu after, as described.
But I don't find the "Apply Update" option.
Thank you for your help.
Stephane
Windows 10
stephane_p said:
Dear all,
I'd like to install LineageOS on my Xiaomi Mi 10 Lite (monet).
I'm following the instructions here : https://wiki.lineageos.org/devices/monet/install.
Everything is going well until step "fastboot flash recovery <recovery_filename>.img".
I type "fastboot flash recovery <recovery_filename>.img" and everything seems to be good.
Sending 'recovery' (131072 KB) OKAY [ 4.907s]
Writing 'recovery' OKAY [ 0.571s]
Finished. Total time: 5.484s
But my phone does not power down. And when I try to reboot into the recovery mode (Volume Up + Power), the fastboot screen appears instead of recovery mode.
I also try with "fastboot boot <recovery_filename>.img".
Sending 'boot.img' (131072 KB) OKAY [ 5.044s]
Booting OKAY [ 0.154s]
Finished. Total time: 5.266s
The phone turns off and I reboot into recovery mode with success. I apply "Wipe Data" and go back to Main Menu after, as described.
But I don't find the "Apply Update" option.
Thank you for your help.
Stephane
Windows 10
Click to expand...
Click to collapse
Use platform tools instead of Minimial adb and use the flash recovery command, it should work. and be careful if you need to disable
dm verity, i don't know Mi 10 Lite but yup
Spuffyffet said:
Use platform tools instead of Minimial adb and use the flash recovery command, it should work. and be careful if you need to disable
dm verity, i don't know Mi 10 Lite but yup
Click to expand...
Click to collapse
Thank you for your help.
I downloaded and used platform tools as described in LineageOS Wiki. And then, I used windows cmd for the adb and the fastboot commands.
stephane_p said:
Thank you for your help.
I downloaded and used platform tools as described in LineageOS Wiki. And then, I used windows cmd for the adb and the fastboot commands.
Click to expand...
Click to collapse
However, it's still not working. I have the same issue.
stephane_p said:
However, it's still not working. I have the same issue.
Click to expand...
Click to collapse
well use "fastboot reboot recovery"
Spuffyffet said:
well use "fastboot reboot recovery"
Click to expand...
Click to collapse
I used reboot recovery. I got:
Rebooting into recovery OKAY [ 0.000s]
Finished. Total time: 0.000s
But the fastboot screen is still here
stephane_p said:
I used reboot recovery. I got:
Rebooting into recovery OKAY [ 0.000s]
Finished. Total time: 0.000s
But the fastboot screen is still here
Click to expand...
Click to collapse
Use this brother: https://developer.android.com/studio/releases/platform-tools
you probably used Minimial ADB, it's the same but just use Platform tools (The one's i just sent)
Spuffyffet said:
Use this brother: https://developer.android.com/studio/releases/platform-tools
you probably used Minimial ADB, it's the same but just use Platform tools (The one's i just sent)
Click to expand...
Click to collapse
I downloaded platform-tools zip file (r33.0.0 for windows) and extract it in C:\Android\platform-tools
Then, I retry
C:\Android\platform-tools>fastboot flash recovery recovery.img
Sending 'recovery' (131072 KB) OKAY [ 5.415s]
Writing 'recovery' OKAY [ 0.586s]
Finished. Total time: 6.017s
C:\Android\platform-tools>fastboot reboot recovery
Rebooting into recovery OKAY [ 0.000s]
Finished. Total time: 0.000s
But, I still get the fastboot screen instead of recovery mode.
Thank you for your help.
Have you tried with another recovery image, like TWRP ?
mgkdv said:
Have you tried with another recovery image, like TWRP ?
Click to expand...
Click to collapse
well i have and it worked for me
mgkdv said:
Have you tried with another recovery image, like TWRP ?
Click to expand...
Click to collapse
I've tried with twrp but I get:
C:\Android>fastboot boot twrp_recovery.img
Sending 'boot.img' (131072 KB) OKAY [ 4.944s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
fastboot: error: Command failed
stephane_p said:
I've tried with twrp but I get:
C:\Android>fastboot boot twrp_recovery.img
Sending 'boot.img' (131072 KB) OKAY [ 4.944s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
fastboot: error: Command failed
Click to expand...
Click to collapse
You are using the wrong command bro, don't use boot. Use "fastboot flash recovery twrp_recovery.img". Why are you flashing recovery.img as boot bro?
OK guys I've found my mistake. I thought the model of my phone was Monet. But it's not. It's Toco... A stupid error showing that I have to be more rigorous.
I thank you again for your help. All the best for xda.
See you