Flashed Build HWI69 for US Retail on a Canadian wifi MZ604 xoom..tired of
waiting for 3.1 update.
adb reboot bootloader
fastboot oem unlock
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
fastboot reboot
It is stuck on Starting RSD mode 2.
I can not get it to fastboot protocol...device does not turn off.
Any solutions?
Fastboot OEM lock is where you went wrong. Anyway see this thread.
OK I did this procedure yesterday but did not relock (I know it says to on the moto site but the guide I read said not to).
Anyway, pressing power and vol up will force a reboot. Unsure what will happen when it boots back up though...!
You should be fine. Only trying to relock will cause this error.
To get back to fastboot after a bad lock do this.
Power button and volume up, this will reboot the device.
As soon as the screen turns back on holds down power and volume down. In about 60 seconds your device should go to fastboot. Do not let go until it gets there.
Sent From My Evo
Thanks for the reply . It now says Failed to boot LNX 0X0004
Starting Fastboot protocol support
However it will not connect to xoom.
<wait for device> when issue fastboot command.
What the hell is going on?
you need to read this thread
http://forum.xda-developers.com/showthread.php?t=1108518
The exact thread I linked to...(-__-)'
I followed instruction from motorla dev support site.
"h**p://developer.motorola.com/products/software/?pubid=987654"
It uses command "fastboot oem lock"! So why did locking brick the device?
here it is:
Device Software Images
Select the appropriate device software image to download and re-lock your device. If you need to find your build number on your Motorola device go to Settings and About Phone or About Tablet.
The commands to flash and re-lock your device are as follows:
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
Note: If no userdata.img file is present in your download, please issue the command:
fastboot erase userdata
The Moto instructions are for locking the device back to it's own image. You are not using your device's own image. Every guide I've seen on here tells you not to relock, regardless of what Moto say. Believe the devs.
Thanxs
I now believe the devs......
Thanks for the reply. Sent the beast out to moto Canada today.
tfx1 said:
I now believe the devs......
Thanks for the reply. Sent the beast out to moto Canada today.
Click to expand...
Click to collapse
Try making or obtaining a factory cable which its different from an OTG cable. Start with the two links below. This might save the day.
http://forum.xda-developers.com/showthread.php?t=1077414
http://forum.xda-developers.com/showthread.php?t=1108518
BACKGROUND INFO: I am trying to install color os rom using twrp recovery and it gives me "failed" when i flash it. I have heard that if you use CWM recovery it will work. i have installed TWRP recovery using toolbox that i downloaded from XDA. when i went back to toolbox to install CWM recovery it told me to boot into fastboot mode and I did. i also clicked attached devices under adb options and it gives my device number in CMD. when i select CWM recovery in toolbox and i hit flash it says make sure your device is in fastboot mode and i clicked ok. then it said within a few seconds your device will boot selected recovery and CMD pops up and it says FAILED. DEVICE NOT UNLOCKED CANNOT FLASH OR ERASE. i think this is because bootloader is locked but when i hit unlock boot loader in toolbox it says make sure your device is in fastboot mode and when i click ok, CMD pops for a second, then it closes and my device reboots immediately to TWRP recovery. also my device is ROOTED. i am able to install other ROMS such as mahdi and rom from OP. someone said that if i flash philz recovery.zip using TWRP recovery i will be able to install color os but still the same error. now i am stuck with philz recovery and i am unable to flash other recoveries. someone said that it is the oem lock and i went to CMD and typed fastoot oem unlock while my device was in fastboot mode and it said OK in cmd and the device booted right into philz recovery and still i am not able to flash another recovery. i went to CMD and typed fastboot oem device-info and it said device tempered- true, bootloader unlocked- false, charger screen enabled- false. I DONT KNOW IF ITS LOCKED BOOTLOADER, THAT I AM NOT ABLE TO UNLOCK, OR OEM LOCK, WHICH I TRIED TO UNLOCK AND IT SAID OK IN CMD, THAT IS NOT ENABLING ME TO FLASH BACK TO TWRP OR STOCK RECOVERY BECAUSE I HAVE MY ROM BACKUPS IN TWRP. PLEASE HELP ME TO GO BACK TO TWRP RECOVERY OR ANY RECOVERY.
Firstly, use paragraphs. Secondly, ditch the toolbox. Issue this fastboot command:
Code:
fastboot oem device-info
What's the output?
Transmitted via Bacon
timmaaa said:
Firstly, use paragraphs. Secondly, ditch the toolbox. Issue this fastboot command:
Code:
fastboot oem device-info
What's the output?
Transmitted via Bacon
Click to expand...
Click to collapse
device tempered- true, bootloader unlocked- false, charger screen enabled- false
Your bootloader is indeed locked. You can unlock it:
Code:
fastboot oem unlock
This will erase all user data on the device.
Transmitted via Bacon
timmaaa said:
Firstly, use paragraphs. Secondly, ditch the toolbox. Issue this fastboot command:
Code:
fastboot oem device-info
What's the output?
Transmitted via Bacon
Click to expand...
Click to collapse
Agreed with the paragraphs. OP did post the output of device-info in his OP post.
Calm down op, no need to use caps lock. Okay so anyways,
Do what timmaaa said, if that doesn't work try the following,
Do you have a copy of TWRP on your computer in the fastboot.exe folder? http://techerrata.com/browse/twrp2/bacon download 2.7.1.1
Go into fastboot mode, type in fastboot boot openrecovery-twrp-2.7.1.1-bacon.img
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
adb sideload that, then unlock your bootloader (fastboot oem unlock) in fastboot mode. then your phone will probably reboot, get into bootloader mode again then type fastboot flash recovery openrecovery-twrp-2.7.1.1-bacon.img and you will permanently flash twrp
timmaaa said:
Your bootloader is indeed locked. You can unlock it:
Code:
fastboot oem unlock
This will erase all user data on the device.
Transmitted via Bacon
Click to expand...
Click to collapse
i tried it nothing happens. the phone reboots into recovery and nothing erases. read my issue first. i already mentioned this. NOTHING HAPPENS WHEN I TYPE FASTBOOT OEM UNLOCK. IT SAYS OK. THEN THE PHONE BOOTS INTO RECOVERY AND NOTHING IS DELETED.
zephiK said:
Agreed with the paragraphs. OP did post the output of device-info in his OP post.
Calm down op, no need to use caps lock. Okay so anyways,
Do what timmaaa said, if that doesn't work try the following,
Do you have a copy of TWRP on your computer in the fastboot.exe folder? http://techerrata.com/browse/twrp2/bacon download 2.7.1.1
Go into fastboot mode, type in fastboot boot openrecovery-twrp-2.7.1.1-bacon.img
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
adb sideload that, then unlock your bootloader (fastboot oem unlock) in fastboot mode. then your phone will probably reboot, get into bootloader mode again then type fastboot flash recovery openrecovery-twrp-2.7.1.1-bacon.img and you will permanently flash twrp
Click to expand...
Click to collapse
when i flashed fastboot boot openrecovery-twrp-2.7.1.1-bacon.img it said ok in cmd and the device is still in fastboot mode and the logo of fastboot got more brighter. also what timaaaa said did not work. it said ok when i typed fastboot oem unlock in cmd and the device booted right to philz recovery and nothing got deleted.
zephiK said:
Agreed with the paragraphs. OP did post the output of device-info in his OP post.
Calm down op, no need to use caps lock. Okay so anyways,
Do what timmaaa said, if that doesn't work try the following,
Do you have a copy of TWRP on your computer in the fastboot.exe folder? http://techerrata.com/browse/twrp2/bacon download 2.7.1.1
Go into fastboot mode, type in fastboot boot openrecovery-twrp-2.7.1.1-bacon.img
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
adb sideload that, then unlock your bootloader (fastboot oem unlock) in fastboot mode. then your phone will probably reboot, get into bootloader mode again then type fastboot flash recovery openrecovery-twrp-2.7.1.1-bacon.img and you will permanently flash twrp
Click to expand...
Click to collapse
can you please explain me the steps in details. i downloaded 3 zip files that were in the link that you gave me. what should i do next? i found the steps confusing in the link.
My output is: device tempered- true, bootloader unlocked- true, charger screen enabled- false. Is it right? Thank you
MAX 94 said:
My output is: device tempered- true, bootloader unlocked- true, charger screen enabled- false. Is it right? Thank you
Click to expand...
Click to collapse
Yes. You are lucky dude. I can't unlock my bootloader.
So, I am the "lucky" one too
I did facktory reset and full wipe as I wanted to install back the CM11s, but I ended up in the "bricked" One :crying:
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
The command: fastboot oem unlock
Reset One to the TWRP, but it does not unlock it
Any falstboot command ends up with: Device not unlocked cannot flash or erase
I already playing with it over 20 hours, but I didnt find how to fix it
I had the same issue that could not unlock bootloader neither flash any room after brick. I used the computer downloaded color os and pushed it to my oneplus SD memory with cmd. But before that I installed twrp 2.7.1 in order to be able to flash os. The only rom was color os that I had success to install. Still bootloader not unlocked but color os rom has root privileged. But at least I have working phone. I installed twrp temporarily with toolkit from xda.
I succeeded to install the latest CyanogenMod 4.4.4. It is pain in the ass. But did it. Most implant is to unlock boot loader with flashing files from twrp. Then used toolkit and installed the rom and Chinese fastboot is gone.
[email protected] said:
I succeeded to install the latest CyanogenMod 4.4.4. It is pain in the ass. But did it. Most implant is to unlock boot loader with flashing files from twrp. Then used toolkit and installed the rom and Chinese fastboot is gone.
Click to expand...
Click to collapse
I have same problem as OP.
Code:
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.019s]
finished. total time: 0.019s
When i do "fastboot oem unlock" when my phone is in fastboot mode, the CMD tells me
Code:
E:\adt-bundle-windows\sdk\platform-tools>fastboot oem unlock
...
OKAY [ 0.005s]
finished. total time: 0.006s
E:\adt-bundle-windows\sdk\platform-tools>
Than he auto reboots into TWRP. I don't do anything there. I boot to android. I shut down. And I Boot to fastboot again. Than when i try to do a fastboot flash or boot he tells me "DEVICE NOT UNLOCKED cannot BOOT"
So every time i unlock it, he puts it immediatly in lock.
What to do?
Search for my post on the OnePlus.net forum...
And welcome to my 28 hours nightmare
djha53k said:
Search for my post on the OnePlus.net forum...
And welcome to my 28 hours nightmare
Click to expand...
Click to collapse
That's incredibly vague. If you really want to help you should provide a link.
Transmitted via Bacon
Sorry... the search for my nick on OnePlus forum gives you 5 results: https://forums.oneplus.net/search/2437238/?q=djha53k&o=relevance&c[node]=26
anyway here we go: https://forums.oneplus.net/threads/recovery.82350/page-8#post-6054985
edit: I wrote that post from bed at 12:55 AM on Tapatalk... and OnePlus forum is not there...
ever figured out how to fix this problem?
djha53k said:
So, I am the "lucky" one too
I did facktory reset and full wipe as I wanted to install back the CM11s, but I ended up in the "bricked" One :crying:
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
The command: fastboot oem unlock
Reset One to the TWRP, but it does not unlock it
Any falstboot command ends up with: Device not unlocked cannot flash or erase
I already playing with it over 20 hours, but I didnt find how to fix it
Click to expand...
Click to collapse
quackoman said:
ever figured out how to fix this problem?
Click to expand...
Click to collapse
Yes, long long loooooooooooooooooooooong time ago...
Suddenly the engl version of my post was already removed :crying:
I have only the czech version now
http://androidforum.cz/jak-opravit-chybu-device-not-unlocked-cannot-flash-or-erase-t59365.html
use google translator then :angel:
I fixed it by :starting up twrp... then I went to install and searched for the recovery (for me i had to go up a lvl and go to sdcard and it was the stock recovery.img)i wanted to flash but you have to chanege to images at the bottom left then I flashed it as recovery .. it failed then i flashed it as boot and then again as recovery and it worked then i reboted it i was promted with the normal recovery .. wiped data and applyd the oneplus ota update .. now it works grat and is fully unlocked IDK IF THAT WILL WORK FOR U OR EVEN HELP.... not responsible..
I have been in fast boot current bootloader screen is hboot 3.19.0.0000 radio 1.12.20.1211 and os 4.17.605.9
Im S-off unlocked
with TWRP 3.0.2.0 installed
DarkCodedDragon said:
I have been in fast boot current bootloader screen is hboot 3.19.0.0000 radio 1.12.20.1211 and os 4.17.605.9
Im S-off unlocked
with TWRP 3.0.2.0 installed
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=24052804347819109
Place the zip in your fastboot/adb directory on your computer.
Put the device in fastboot mode
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
Enter the following commands from terminal/command prompt in the fastboot directory, one at a time:
fastboot oem rebootRUU (this puts the device in RUU mode)
fastboot flash zip firmware.zip (rename file to firmware.zip to make it simple/optional)
It will say that the update did not finish, to flush again, so repeat the above step:
fastboot flash zip firmware.zip
Quote:
Important: the flash process halts at around 75% to 90% on phone screen! This is normal and a safety precaution!
The last few percent is the reboot, which is NOT happening automatically, so you get a chance to check the console output before reboot to make sure it is safe to reboot!
The bar will only fill up to 100% once you type the following command:
fastboot reboot-bootloader (this reboots the device to bootloader)
That's it, you're done. You can now reboot and will be running the latest firmware and radios.
http://forum.xda-developers.com/showpost.php?p=62734094&postcount=2
So from here do I just pick any 5.01 rom and flash with TWRP.?? And I do have to reflash SU after this correct?
I got updated rom , still need to check SU after rom loads thanks
Hello
at first sry for my english.
after an update i think i have a bricked Honor 8 (no custom rom), so i tried to rollback to stock rom.
But there are some problems, i only come into the fastboot modus.
1. Battery empty
it does not charge in normal way.
i have read some about laden.bat,
i tried this and the Honor go on and out and so on, i think this is ok but in the logfile you can see this
getvar:battery-voltage FAILED (command write failed (Unknown error))
can i use this file for Honor and what is the problem with this command?
I don't know about laden.bat but if you have more than 10% battery you should be able to unlock your bootloader then boot into recovery mode. If this works you'll be able to charge the phone as normal.
If you can't unlock the bootloader because battery is below 10% then you could try using this script to charge the battery up to the level you need....
" @Echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
"