Database Info

[Q] Rooting the 3G Xoom (Stock 3.2) with CWM - error 0x120000

Hi folks,
atm I feel like a complete newb because I cant manage to root my xoom according to http://forum.xda-developers.com/showthread.php?t=1074979 with fastboot. (Can't flash through cwm since the device is stock 3.2)
What I have:
Motorola Xoom EU 3G (MZ601)
Android Version 3.2
Kernel 2.6.36.3
Firmware GAS_EMEA_USAEVRSTUTMDE_P016
What doesn't work:
As soon as I try to flash recovery my almighty command line says:
Code:
>fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
sending 'recovery' (3998 KB)...
OKAY [ 0.490s]
writing 'recovery'...
FAILED (command write failed (Unknown error))
finished. total time: 1.103s
My xoom shows "Starting Fastboot protocol support" as if nothing happened.
When I try to issue the command again immediatly, the error changes to:
Code:
>fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
sending 'recovery' (3998 KB)...
FAILED (remote: (00120000))
finished. total time: 0.274s
The xoom is showing "Failed to process command error(0x120000)".
Here is what I've done so far, aside from following the post mentioned above including all tipps in that thread.
tried three different cables for connecting the xoom to my PC, including the original one.
tried two different computers with three different OSs (x64 only so far)
tried to flash the image immediatly after the oem unlock without booting into system
tried everey single usb port on every system
tried updating chipset drivers as well as the usb drivers
I don't know what to try next. Could someone please give me a hint what to try next? I'm stuck here.
Thanks in advance & thanks for reading, Jan

jan_goose said:
Here is what I've done so far, aside from following the post mentioned above including all tipps in that thread.
tried three different cables for connecting the xoom to my PC, including the original one.
tried two different computers with three different OSs (x64 only so far)
tried to flash the image immediatly after the oem unlock without booting into system
tried everey single usb port on every system
tried updating chipset drivers as well as the usb drivers
I don't know what to try next. Could someone please give me a hint what to try next? I'm stuck here.
Thanks in advance & thanks for reading, Jan
Click to expand...
Click to collapse
Have you tried to check the md5-checksum of the image file?

llama-power said:
Have you tried to check the md5-checksum of the image file?
Click to expand...
Click to collapse
Hi, indeed, I forgot that. I've checked it and they are matching, so no luck here.
Does someone know if maybe 64bit systems could cause problems? (And what to do aside from buying a new PC ^^)

jan_goose said:
Hi, indeed, I forgot that. I've checked it and they are matching, so no luck here.
Does someone know if maybe 64bit systems could cause problems? (And what to do aside from buying a new PC ^^)
Click to expand...
Click to collapse
well, they could but on my 64bit system everything worked out fine. You could try installing a 32 bit OS, as your computer is likely compatible to that. I don't, however, believe that would do any good as it looks like your computer is doing what it should, only your xoom isn't... (to me, it looks like your computer is sending the file just fine but the xoom just doesn't want to flash that file to memory)...
what does fastboot getvar all return?

llama-power said:
what does fastboot getvar all return?
Click to expand...
Click to collapse
A command I wasn't aware of, thanks.
While charging, it says:
Code:
(bootloader) version-bootloader: 1049
(bootloader) product: xoom-cdma
(bootloader) secure: yes
(bootloader) model: MZ600
(bootloader) memory-info: 0x101:0x5454:0
(bootloader) mid: 001
(bootloader) version: 0.4
(bootloader) serialno: 037C710041XXXX
(bootloader) version-baseband: N_01.100.05P
(bootloader) version-baseband-2:
(bootloader) battery-status: 45%:7.847V:0.869A:21.37C
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
I'm a bit confused because it says "MZ600", but according to the tablet info when android has booted it is a MZ601.
I'm living in germany, where I've also bought the device and it's got a 3g module which i'm actually using.

jan_goose said:
While charging, it says:
Click to expand...
Click to collapse
did you just omit the (bootloader) iswarrantyvoid: yes or did that really not appear? Apart from that, everything looks just like on my device... Thus, I am officially out of ideas... I'd offer to have a look at your device next week as I'll be in your location then but I currently don't see how that would do any good...
jan_goose said:
I'm a bit confused because it says "MZ600", but according to the tablet info when android has booted it is a MZ601.
Click to expand...
Click to collapse
yeah, that distracted me at first too, but a friends MZ601 which is neither rooted nor unlocked, says the same, so I think thats fine...
Anyhow... sorry, no clue what's wrong with your device...:-(
can you flash a the recovery image from Motorola?

llama-power said:
can you flash a the recovery image from Motorola?
Click to expand...
Click to collapse
Actually, I couldn't.
I didn't even try before. This simple question of yours emerged something like a nerdrage from deep inside.
I looked sternly at my xoom and decided that I won't go down first.
Well, the rest was luck, but since I've tried it multiple times and it worked, here are the steps:
Start slowly with these lines (I know them by heart by now)
Code:
adb reboot bootloader
fastboot flash recovery recovery-solarnz-XXXXXX-XXXX.img
It will fail. Do the last line again, it will show error 0x120000.
Now you have to be quick as soon as you submitted the next line:
Code:
fastboot reboot
Unplug your device from the PC and start hitting the Volume down button immediatly (this means: do not tap and hold, press it multiple times) until the display says fastboot is ready .
Now re-plug the xoom to the PC again and re-do this:
Code:
fastboot flash recovery recovery-solarnz-XXXXXX-XXXX.img
This time, everything goes well.
If, like me, you are coming from stock, don't forget you must not reboot to system again, but directly to recovery and install something like Team EOS ROM.
I have no clue why it worked, but since I was so fascinated that I've tried it three times I guess one could say it's reproducable.
Good night and thanks to llama-power for being inspirational.

wow
jan_goose said:
Actually, I couldn't.
I didn't even try before. This simple question of yours emerged something like a nerdrage from deep inside.
I looked sternly at my xoom and decided that I won't go down first.
Well, the rest was luck, but since I've tried it multiple times and it worked, here are the steps:
Start slowly with these lines (I know them by heart by now)
Code:
adb reboot bootloader
fastboot flash recovery recovery-solarnz-XXXXXX-XXXX.img
It will fail. Do the last line again, it will show error 0x120000.
Now you have to be quick as soon as you submitted the next line:
Code:
fastboot reboot
Unplug your device from the PC and start hitting the Volume down button immediatly (this means: do not tap and hold, press it multiple times) until the display says fastboot is ready .
Now re-plug the xoom to the PC again and re-do this:
Code:
fastboot flash recovery recovery-solarnz-XXXXXX-XXXX.img
This time, everything goes well.
If, like me, you are coming from stock, don't forget you must not reboot to system again, but directly to recovery and install something like Team EOS ROM.
I have no clue why it worked, but since I was so fascinated that I've tried it three times I guess one could say it's reproducable.
Good night and thanks to llama-power for being inspirational.
Click to expand...
Click to collapse
i tried your method did not work i was also getting the error code what worked was using [Recovery] EOS recovery (R6) CWM Based and it pushed thru fastboot no problem just a heads up

Just to confirm...
jan_goose said:
A command I wasn't aware of, thanks.
While charging, it says:
Code:
(bootloader) version-bootloader: 1049
(bootloader) product: xoom-cdma
(bootloader) secure: yes
(bootloader) model: MZ600
(bootloader) memory-info: 0x101:0x5454:0
(bootloader) mid: 001
(bootloader) version: 0.4
(bootloader) serialno: 037C710041XXXX
(bootloader) version-baseband: N_01.100.05P
(bootloader) version-baseband-2:
(bootloader) battery-status: 45%:7.847V:0.869A:21.37C
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
I'm a bit confused because it says "MZ600", but according to the tablet info when android has booted it is a MZ601.
I'm living in germany, where I've also bought the device and it's got a 3g module which i'm actually using.
Click to expand...
Click to collapse
Did you verify if that information is correct? I get the same info from fastboot

Onedroidev said:
Did you verify if that information is correct? I get the same info from fastboot
Click to expand...
Click to collapse
I have no idea why the information seems to be wrong, but obviously it can be ignored, at least in my case.
As long as you've got a 3G module, it is not a MZ600, regardless what fastboot is saying.

[Q] Fastboot Flash Command Hangs Device

I just got my new tablet today... it automatically did all it's updates while it was charging - I unlocked it following the tutorials and some strange issues started happening where the recovery ROMs I flashed couldn't see the system partitions. I tried a few different recovery ROMs (TWRP, CWM) but both did the same.
The problem, now when I try and flash anything using the bootloader, my command prompt claims it finished successfully, but my tablet's green flashing box stops flashing and does nothing until I hold on the power button to hard boot it.
Any ideas? Here's the information I've been able to gather:
Code:
PS C:\android-sdk\platform-tools> .\fastboot.exe -i 0x0b05 getvar all
(bootloader) version-bootloader: 1.0
(bootloader) version-baseband: 2.0
(bootloader) version: 0.4
(bootloader) serialno: 0asdfghjklzxcvbnm
(bootloader) mid: 001
(bootloader) product: Cardhu
(bootloader) secure: yes
(bootloader) unlocked: no
(bootloader) uart-on: yes
(bootloader) partition-size:bootloader: 0x0000000000800000
(bootloader) partition-type:bootloader: basic
(bootloader) partition-size:recovery: 0x0000000000800000
(bootloader) partition-type:recovery: basic
(bootloader) partition-size:boot: 0x0000000000800000
(bootloader) partition-type:boot: basic
(bootloader) partition-size:system: 0x0000000030000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x000000001ac00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x00000006e5680000
(bootloader) partition-type:userdata: ext4
all:
finished. total time: 0.105s
PS C:\android-sdk\platform-tools> .\fastboot.exe -i 0x0b05 erase recovery
erasing 'recovery'...
OKAY [ 1.237s]
finished. total time: 1.238s
PS C:\android-sdk\platform-tools> .\fastboot.exe -i 0x0b05 flash recovery openrecovery-twrp-2.4.3.0-tf300t-JB.blob
sending 'recovery' (7670 KB)...
OKAY [ 2.099s]
writing 'recovery'...
OKAY [ 2.694s]
finished. total time: 4.795s
PS C:\android-sdk\platform-tools>
I can erase and getvar all day, but flash makes it freeze up.

I forgot to include that once it locks up, the fastboot command does this:
Code:
PS C:\android-sdk\platform-tools> ./fastboot -i 0x0B05 devices
???????????? fastboot
PS C:\android-sdk\platform-tools> ./fastboot -i 0x0B05 getvar all
getvar:all FAILED (command write failed (Unknown error))
finished. total time: 0.592s
PS C:\android-sdk\platform-tools>

kulm said:
I just got my new tablet today... it automatically did all it's updates while it was charging - I unlocked it following the tutorials and some strange issues started happening where the recovery ROMs I flashed couldn't see the system partitions. I tried a few different recovery ROMs (TWRP, CWM) but both did the same.
(bootloader) unlocked: no
Have you unlocked? Your posted information says no. If you are on 4.2 I can't say but previous firmware disallowed use of fastboot prior to unlocking.
Click to expand...
Click to collapse

tobdaryl said:
kulm said:
(bootloader) unlocked: no
Have you unlocked? Your posted information says no. If you are on 4.2 I can't say but previous firmware disallowed use of fastboot prior to unlocking.
Click to expand...
Click to collapse
I wondered the same thing - but I had TWRP working on it and it says on the top when I reboot "The device is unlocked"...
Click to expand...
Click to collapse

kulm said:
tobdaryl said:
I wondered the same thing - but I had TWRP working on it and it says on the top when I reboot "The device is unlocked"...
Click to expand...
Click to collapse
I have not seen this or read of this issue. Are you on the 4.2 version of software? If so you are in uncharted waters.
I didn't get the update and can't use the ota to install. I like many others are waiting for the asus firmware version.
I have read one reply where cwm didn't work on 4.2.
Something else I have never seen is the bootloader serial number displayed. You may wish to remove that line from your post. Just choose edit and delete that line, then save.
If on 4.2 this may indicate that cwm and twrp will require an update to work properly.
If you can use your tablet as is then I suggest doing so or flash stock JB firmware the most recent is 10.4.2.20 but for my use 10.4.2.18 has less lag and everything I need works properly.
I'll bookmark this thread and try to come back with some help after more research. Failing that maybe someone else will reply with a good suggestion.
Good Luck!
Please respond with your firmware version.
This is the standard method used to unlock the bootloader with fastboot. I can't use it since I'm not on 4.2 and won't suggest that you do; it is for information only at this point.
fastboot oem unlock
I suspect we would need to use the -i 0x0b05 as in fastboot -i 0x0b05 oem unlock.
Click to expand...
Click to collapse

tobdaryl said:
kulm said:
I have not seen this or read of this issue. Are you on the 4.2 version of software? If so you are in uncharted waters.
I didn't get the update and can't use the ota to install. I like many others are waiting for the asus firmware version.
I have read one reply where cwm didn't work on 4.2.
If on 4.2 this may indicate that cwm and twrp will require an update to work properly.
If you can use your tablet as is then I suggest doing so or flash stock JB firmware the most recent is 10.4.2.20 but for my use 10.4.2.18 has less lag and everything I need works properly.
I'll bookmark this thread and try to come back with some help after more research. Failing that maybe someone else will reply with a good suggestion.
Good Luck!
Please respond with your firmware version.
This is the standard method used to unlock the bootloader with fastboot. I can't use it since I'm not on 4.2 and won't suggest that you do; it is for information only at this point.
fastboot oem unlock
I suspect we would need to use the -i 0x0b05 as in fastboot -i 0x0b05 oem unlock.
Click to expand...
Click to collapse
Thanks for the response - the SN is bogus.So, when I boot without pushing vol up/down it goes to the "ASUS" logo screen with "device unlocked" at the top and it just sits... I can get into APX with vol up and fastboot with vol down.
With vol down this comes up at the top:
Code:
Key driver not found.. Booting OS
Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.8-20130225" A03
Starting Fastboot USB download protocol
Then it has the typical RCK, Android and Wipe Data options.
When I choose RCK I get:
Code:
Booting Recovery kernel image
Booting Failed
Unrecoverable bootloader error (0x00000000)
The device hangs until I power cycle from there.
Click to expand...
Click to collapse

kulm said:
tobdaryl said:
Thanks for the response - the SN is bogus.So, when I boot without pushing vol up/down it goes to the "ASUS" logo screen with "device unlocked" at the top and it just sits... I can get into APX with vol up and fastboot with vol down.
With vol down this comes up at the top:
Code:
Key driver not found.. Booting OS
Android cardhu-user bootloader <1.00 e> released by "US_epad-1.6.1.8-20130225" A03
Starting Fastboot USB download protocol
Then it has the typical RCK, Android and Wipe Data options.
When I choose RCK I get:
Code:
Booting Recovery kernel image
Booting Failed
Unrecoverable bootloader error (0x00000000)
The device hangs until I power cycle from there.
Click to expand...
Click to collapse
I am completely lost, if this is 4.2 that might be why. If you will give me your version I'll try to help you search and get an answer. Go to settings/about tablet/ and tell me what you have for build# and android version.
The serial# is not your tablet serial# but bootloader serial#. This may be in response to our recent petition to asus for the ability to unlock the bootloader in addition to the tablet unlock we now have.
If so this should allow nvflash for people on the JB bootloader.
Note: If you are on 4.2 you might look at settings and see if encryption is turned on, at least two have mentioned that it is on by default and it will cause various issues with fastboot and cwm or twrp.
Now that I think about it even on 4.1 encryption has caused some strange results.
Click to expand...
Click to collapse

tobdaryl said:
kulm said:
I am completely lost, if this is 4.2 that might be why. If you will give me your version I'll try to help you search and get an answer. Go to settings/about tablet/ and tell me what you have for build# and android version.
The serial# is not your tablet serial# but bootloader serial#. This may be in response to our recent petition to asus for the ability to unlock the bootloader in addition to the tablet unlock we now have.
If so this should allow nvflash for people on the JB bootloader.
Note: If you are on 4.2 you might look at settings and see if encryption is turned on, at least two have mentioned that it is on by default and it will cause various issues with fastboot and cwm or twrp.
Now that I think about it even on 4.1 encryption has caused some strange results.
Click to expand...
Click to collapse
I am on 4.2.1 and am having the same issue. I just checked and encryption is turned off on mine.
Click to expand...
Click to collapse

mistyv said:
tobdaryl said:
I am on 4.2.1 and am having the same issue. I just checked and encryption is turned off on mine.
Click to expand...
Click to collapse
Thanks for the update. I'll start searching also and report when I have some news.
Good Luck!
I'm finding several with fastboot issues as well as cwm and twrp issues but no resolutions yet.
I'll try to keep you posted if I get something positive.
Click to expand...
Click to collapse

My device is doin the same thing i would go into fastboot mode and the green box would just freeze up but when i push the recovery it says that is was successful b ut the device doesnt take the recovery then when i tried to push it again it fails can anyone help
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app

ryuken11221 said:
My device is doin the same thing i would go into fastboot mode and the green box would just freeze up but when i push the recovery it says that is was successful b ut the device doesnt take the recovery then when i tried to push it again it fails can anyone help
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
Click to expand...
Click to collapse
That is what mine did and I thought it wasn't installing, but it actually did. Once I rebooted back into fastboot and selected RCK mine would boot into the recovery, but the internal and external sd card wouldn't mount. I tried TWRP and CWM, but no luck with either.
According to this thread http://forum.xda-developers.com/showthread.php?t=2180376 it is likely an encryption issue with 4.2.1 and we will have to wait till someone finds a fix. I was apparently wrong about the encryption on my earlier post.

ryuken11221 said:
My device is doin the same thing i would go into fastboot mode and the green box would just freeze up but when i push the recovery it says that is was successful b ut the device doesnt take the recovery then when i tried to push it again it fails can anyone help
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
Click to expand...
Click to collapse
I'm not finding answers to this problem; just questions.
I can't get 4.2 until Asus drops the file on their site.
At this point maybe everyone put this area on hold for a few days till we can get the full download and try to figure out what is happening and how to resolve these issues. Try to use your unit as it is for a few days and avoid possible bricks.

I have a full system dump of 4.2.1. Just extracting the bootloader and flashing it causes recovery to think it is encrypted. Custom recovery that is. Also I noticed that the 10.6.1.8 kernel doesn't like some updater-script commands. Finally there is a new file in /system/etc called recovery-resource.dat. I wonder if Asus has put some measures I in place to stop customising?

sbdags said:
I have a full system dump of 4.2.1. Just extracting the bootloader and flashing it causes recovery to think it is encrypted. Custom recovery that is. Also I noticed that the 10.6.1.8 kernel doesn't like some updater-script commands. Finally there is a new file in /system/etc called recovery-resource.dat. I wonder if Asus has put some measures I in place to stop customising?
Click to expand...
Click to collapse
Thanks for the good info. That explains a lot.
Were you using the update-binary from 10.6.1.8 or an earlier version?
Great catch. I just checked and we now have a different version of update-binary. Now I need to revisit my edify scripts.
Thanks!

Well I'm still running 4.1.1 I haven't be able to upgrade to 4.2 just as yet so I'm not sure what the issue with my device is I just restored it back to back to factory for work purposes and now I wanted to root it back and install recovery now this
Sent from my SAMSUNG-SGH-I747 using XDA Premium HD app

tobdaryl said:
Thanks for the good info. That explains a lot.
Were you using the update-binary from 10.6.1.8 or an earlier version?
Great catch. I just checked and we now have a different version of update-binary. Now I need to revisit my edify scripts.
Thanks!
Click to expand...
Click to collapse
I haven't actually flashed all of it but tried to make it compatible with my TF700. I also tried 2 or 3 different updater binaries and they made no difference.
Specifically format now wanted 5 args where only needed 4 before. No idea what the 5th is. Package extract file didn't like me writing to /tmp but was OK with /data/media ..... Weird
Looks like a permissions thing?

sbdags said:
I haven't actually flashed all of it but tried to make it compatible with my TF700. I also tried 2 or 3 different updater binaries and they made no difference.
Specifically format now wanted 5 args where only needed 4 before. No idea what the 5th is. Package extract file didn't like me writing to /tmp but was OK with /data/media ..... Weird
Looks like a permissions thing?
Click to expand...
Click to collapse
Thanks for the help.

OK is this straying from what the topic is about just asking
Sent from my SAMSUNG-SGH-I747 using XDA Premium HD app

ryuken11221 said:
OK is this straying from what the topic is about just asking
Sent from my SAMSUNG-SGH-I747 using XDA Premium HD app
Click to expand...
Click to collapse
It is about the 4.2 rom and related issues; however I am done. Sorry for the interruption.

tobdaryl said:
It is about the 4.2 rom and related issues; however I am done. Sorry for the interruption.
Click to expand...
Click to collapse
Not a problem just wondering if I can get help with this just very very frustrating
Sent from my SAMSUNG-SGH-I747 using XDA Premium HD app

Operation not permitted

Subject line pretty much sums it up. I've been to loads of GUIs and walkthroughs - in the end my device remains locked down. I have TWRP as my recovery and a rooted version of the stock CM11S. I have my debugging on. My computer has permission with it set to remember my choice. I've dabbled in both OSX and Windows adb. The goal is to go back to stock EVERYTHING. I'm going to send it back.
Please help.

Lol you told us everything except for which operation is not permitted.
Transmitted via Bacon

Flashing pretty much anything via fastboot. When I 'fastboot oem unlock' the system isnt formatted or anything. Is it because my recovery isnt stock? I've tried restoring stock recovery, but after it loads once, a reboot just goes into TWRP again. I dont understand.

Xephrey said:
Flashing pretty much anything via fastboot. When I 'fastboot oem unlock' the system isnt formatted or anything. Is it because my recovery isnt stock? I've tried restoring stock recovery, but after it loads once, a reboot just goes into TWRP again. I dont understand.
Click to expand...
Click to collapse
If you don't have the stock recovery installed, isn't your bootloader unlocked already? What happens when you issue these commands?
Code:
fastboot devices
Code:
fastboot oem device-info
Transmitted via Bacon

timmaaa said:
If you don't have the stock recovery installed, isn't your bootloader unlocked already? What happens when you issue these commands?
Code:
fastboot devices
Code:
fastboot oem device-info
Transmitted via Bacon
Click to expand...
Click to collapse
C:\Users\Chris\Desktop\android-sdk-windows\platform-tools>fastboot devices
97e265f5 fastboot
and
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.005s]
finished. total time: 0.005s

What about the question I asked?
Transmitted via Bacon

Oh sorry. Yeah, that's where things get weird. It's locked now, but I guess I was able to get it unlocked long enough to get TWRP injected. Not sure when / how it locked.

So you don't know at what point this started happening?
Transmitted via Bacon

I don't.

Usually there's a catalyst for things like this, without knowing the catalyst it's difficult to troubleshoot.
Transmitted via Bacon

Well shoot.

Come to think of it, I think I may have typed in oem lock at one point and then unlock promptly thereafter.

Solution
Great news! I've solved the issue. I used OnePlus One Toolkit by @manudroid19
http://forum.xda-developers.com/oneplus-one/development/oneplus-one-toolkit-manudroid19-gui-t2807418
I tried the Experimental Method or #2 to unlock the bootloader. Then you're given the option of downloading TWRP. At first I thought that was lame cause I already had that installed - that's what I was trying to get away from. But I finally understood that I had the option of running that recovery off of my PC by initiating fastboot mode on my One, then typing 'fastboot boot <local path of TWRP.zip I just downloaded>'. And from there I was able to sideload the unlock / tamper toggler as made available here:
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Sideload actually completed successfully! I had tried sideload before with every attampt ending in red-text failure. I then went into fastboot mode on my One and flashed stock recovery. Then I used OnePlus One Toolbox v2 by @inthiaano:
http://forum.xda-developers.com/oneplus-one/development/toolbox-oneplus-one-toolbox-t2808987
Because it had stock CM11S as an option. This was also the toolbox I used to flash stock recovery earlier cause I couldn't find it anywhere else. After I flashed that, I did the fastboot boot <local TWRP> sideload unlock toggler again to achieve:
DUN DUN DUN DUUUNNNNN...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
Factory reset and return-ready. FINALLY!
So happy. Now I can get my money back and buy an Nvidia Shield 2 instead.

[Q&A] [MOD] OnePlus One Unlocker: Reset Unlock & Tamper Bit

Q&A for [MOD] OnePlus One Unlocker: Reset Unlock & Tamper Bit
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

Thank you so much!!!!!!!
This solved my problem like a charm!

bootloader
bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.005s]

bootloader locked twrp recovery specific problem
Hello. I did post my problem on OPO forum but didnt found my answer. Iwil try here now
As answer for your questions in 1st post:
1) yes i did unlock by bootloader before.
2) I am running twrp recovery now (and thats the only thing left on my OnePlus One no Os)
3) (bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.016s]
finished. total time: 0.016s
4) E:\One plus one\2222\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (5560 KB)...
OKAY [ 0.168s]
writing 'boot'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.186s
5) well basicly i tried everything including your method... i am trying to fix this for 2 days now. Ill just describe whats happening when i try to do your method in different ways because seems like your method is the solution for my phone the only thing is how to make it to work...
first off all when i tried to push that file thru adb push command nothing was apppering on my phone...
than i bought my usb otg cable and connected usb stick with that file... it helped because my phone saw that file and i could instal it... but when i tried to instal it thru TWRP it was saying that
MD5 check sum is wrong and instalation failed...
Today i tried siedeload that file thru "adb sideload ..." command and
E:\One plus one\2222\adt-bundle-windows-x86_64-2014702\sdk\platform-tools>adb sideload OnePlusOne-Bootunlocker.zip
error:closed
error:closed
Hope this is clear enough plzzzz help i want my OPO back tho i bought it like 3 weeks
Thx for any answers ...
OKi downloaded difeerent file and MD5 sum was alright this time... sorry for trouble and thx for fixing my problem

Thx guys for restoring my OPO all is working fine i have back to stock phone and 38r thru automatic update 1 more time thx and cheers. Good job

Fastboot flash
If I want to flash via fastboot, in which state the Unlock Bit and Tamper Bit have to be?
Im trying to flash stock 38r, and im getting the error that device not unlocked. Tried to unlock with fastboot oem unlock, but when i flash the stock rom, im getting that error.
Thanks.

I got this question too!

The script does not work, I have tested on XNPH22R and XNPH33R it always remains
Device tampered: true
Device unlocked: false
probably the tamper go to true when you lock the bootloader
it might work a script that lock the bootloader and reset the tampe at the same time

Can't UNlock boot loader
I have a locked bootloader and nothing i try is unlocking it.
background, i rooted and tried to go back to start. Now when my phone turns on i get the system ui error non stop. So i'm hoping to unlock bootloader and reflash stock rom.
Device Tampered: true
device unlocked: false
from here, i don't have a clue what to do.

Can't unlocked boot loader
Hi there, I believe I messed my phone while trying to root and install twrp recovery. Now I can't run "oem unlock" to unlock my phone, I can't go to recovery, the only thing I can get into is FASTBOOT mode. Here is my screen shoot , please take a look and let me know what should I do . I downloaded Boot Unlocker from your post, but don't know how to flash it since I can't run "boot recovery twrp.img"
Please take a look at my attachment .
Thanks

pablikowskipablik said:
Hello. I did post my problem on OPO forum but didnt found my answer. Iwil try here now
As answer for your questions in 1st post:
1) yes i did unlock by bootloader before.
2) I am running twrp recovery now (and thats the only thing left on my OnePlus One no Os)
3) (bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.016s]
finished. total time: 0.016s
4) E:\One plus one\2222\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (5560 KB)...
OKAY [ 0.168s]
writing 'boot'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.186s
5) well basicly i tried everything including your method... i am trying to fix this for 2 days now. Ill just describe whats happening when i try to do your method in different ways because seems like your method is the solution for my phone the only thing is how to make it to work...
first off all when i tried to push that file thru adb push command nothing was apppering on my phone...
than i bought my usb otg cable and connected usb stick with that file... it helped because my phone saw that file and i could instal it... but when i tried to instal it thru TWRP it was saying that
MD5 check sum is wrong and instalation failed...
Today i tried siedeload that file thru "adb sideload ..." command and
E:\One plus one\2222\adt-bundle-windows-x86_64-2014702\sdk\platform-tools>adb sideload OnePlusOne-Bootunlocker.zip
error:closed
error:closed
Hope this is clear enough plzzzz help i want my OPO back tho i bought it like 3 weeks
Thx for any answers ...
OKi downloaded difeerent file and MD5 sum was alright this time... sorry for trouble and thx for fixing my problem
Click to expand...
Click to collapse
--------------------------------
HI , my problem is exactly like your, can you tell me how did you solve it please ?

Oneplus tamper flag
I am trying to set my tamper flag on my Oneplus to false, but I can't seem to get both to stay false. I am on 38R and following the instructions from here to flash back stock rom and recovery. And here to reset tamper flags. I can't seem to get the device tampered flag to false. Instead I get this
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
What am I doing wrong. Thanks

paralaxx said:
I am trying to set my tamper flag on my Oneplus to false, but I can't seem to get both to stay false. I am on 38R and following the instructions from here to flash back stock rom and recovery. And here to reset tamper flags. I can't seem to get the device tampered flag to false. Instead I get this
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
What am I doing wrong. Thanks
Click to expand...
Click to collapse
Why does it matter? It doesn't affect your warranty or anything.
Transmitted via Bacon

timmaaa said:
Why does it matter? It doesn't affect your warranty or anything.
Transmitted via Bacon
Click to expand...
Click to collapse
I thought have the tamper flag as True voids warranty no? Plus, I am trying to contact customer service for a problem I have and knowing OnePlus I don't want to give them any excuses for fixing my phone.

paralaxx said:
I thought have the tamper flag as True voids warranty no? Plus, I am trying to contact customer service for a problem I have and knowing OnePlus I don't want to give them any excuses for fixing my phone.
Click to expand...
Click to collapse
Not sure where you got that information but it's incorrect. Unlocking the bootloader trips the tamper but neither void your warranty.
Transmitted via Bacon

Tampered - TRUE
--------------

Hello guys! I'm wondering why my brand new, out of box OPO had tamper flag set to TRUE?? I was just updated to 38R through OTA and went to fastboot and checked with device-info... It was the first command I ever used in fastboot so how is that possible?

THANK YOU!
That really worked, same happened to me and I have been over a day reading and trying to put this to work! thank you

Locked Bootloader
Hi Mate's !!
I am facing same problem. my boot loader is locked i tried
Fastboot oem device-info (It give)
(bootloader) Device tempered:true
(bootloader) Device Unlock:false
(bootloader)Charger screen enable: false
Okey[0,005s]
Then i try
Fastboot oem unlock (It restart the phone in recovery mode) but device gives same info
(bootloader) Device tempered:true
(bootloader) Device Unlock:false
I also tried to bootloaderunlocker.zip by sideload but result is installation failed due to signature verification
Help me
Thanks in advance

Oneplus one Tamper bit
Hi,
Just got a quick question I was looking into flash android lollipop onto my opo deceive but wanted to do a little research before starting. I saw this post on the tamper bit and unlock script. I thought I would see what my "fastboot oem device-info" was as I have not unlock this device before. To my surprise the tamper bit came back true and the unlock bit came back false. I'm curious how this could be if I have never unlocked the device? If anyone could shed some light on this that would be great. Thanks in advance.

[Q] OTA Update 2.2 has bricked my brand new ST?

So I just got my Shield Tablet today and of course I get notifications of OTA updates. I applied the first two (1.something and 2.1) just fine. Then the 2.2 update downloads and I tell it to install, which it starts to do. Little Android with his chest open shows up and the status bar does it's thing, then it reboots back to the nvidia boot image.... and hangs there. For over an hour I let it stay to see if it was doing some updating in the background, but nothing else happens. So I power it down by holding the power button, then turn it back on. Same deal. Stuck at the boot image.
Of course I'm not unlocked or rooted, so I only have the stock recovery. Any suggestions on how to resurrect this, or am I headed to customer support for an exchange?

Nastybutler said:
So I just got my Shield Tablet today and of course I get notifications of OTA updates. I applied the first two (1.something and 2.1) just fine. Then the 2.2 update downloads and I tell it to install, which it starts to do. Little Android with his chest open shows up and the status bar does it's thing, then it reboots back to the nvidia boot image.... and hangs there. For over an hour I let it stay to see if it was doing some updating in the background, but nothing else happens. So I power it down by holding the power button, then turn it back on. Same deal. Stuck at the boot image.
Of course I'm not unlocked or rooted, so I only have the stock recovery. Any suggestions on how to resurrect this, or am I headed to customer support for an exchange?
Click to expand...
Click to collapse
you need to unlock the bootloader

Daniele12 said:
you need to unlock the bootloader
Click to expand...
Click to collapse
I am facing the same problem after OTA 3.0 update.
I tried all methods of unlocking bootloader but couldn't.
Please help me if any new method of unlocking bootloader is available.

VijayBais said:
I am facing the same problem after OTA 3.0 update.
I tried all methods of unlocking bootloader but couldn't.
Please help me if any new method of unlocking bootloader is available.
Click to expand...
Click to collapse
Can you not get it to boot into the bootloader? (Press and hold Vol - and then press the power button)

Keithn said:
Can you not get it to boot into the bootloader? (Press and hold Vol - and then press the power button)
Click to expand...
Click to collapse
yes i can get into the fastboot mode.
But the point is that i couldn't unlock the device using "fastboot oem unlock" command.
Also USB Debugging is disabled, and cant boot inside android to enable it.

VijayBais said:
yes i can get into the fastboot mode.
But the point is that i couldn't unlock the device using "fastboot oem unlock" command.
Also USB Debugging is disabled, and cant boot inside android to enable it.
Click to expand...
Click to collapse
USB debugging isn't necessary, that's for ADB. What does it tell you when you try to use that command? Is it "waiting for device" ? I would check to make sure you have drivers for fastboot and that the shield is using them (sometimes it won't automatically load the proper driver).
Also, no custom recovery?

Keithn said:
USB debugging isn't necessary, that's for ADB. What does it tell you when you try to use that command? Is it "waiting for device" ? I would check to make sure you have drivers for fastboot and that the shield is using them (sometimes it won't automatically load the proper driver).
Also, no custom recovery?
Click to expand...
Click to collapse
It shows following unknown error
C:\Downloads\nv-recovery-image-shield-tablet-lte-row-update2_2_1\image>fastboot oem unlock
...
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) erasing userdata...
FAILED (remote: (Unknown error code))
finished. total time: 5.003s

I know this won't help VijayBais, but after a while I guess the stock kernel and everything settled in and it stopped random restarting and when I did restart, after installing apps and whatnot, it booted right back up. Now that I'm on 5.1, I haven't had any issues with it freezing up, or random restarts. Crisis averted.

VijayBais said:
It shows following unknown error
C:\Downloads\nv-recovery-image-shield-tablet-lte-row-update2_2_1\image>fastboot oem unlock
...
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) erasing userdata...
FAILED (remote: (Unknown error code))
finished. total time: 5.003s
Click to expand...
Click to collapse
Not sure what else to do. Is your recovery stock? Have you tried to do a factory reset then unlock?

Keithn said:
Not sure what else to do. Is your recovery stock? Have you tried to do a factory reset then unlock?
Click to expand...
Click to collapse
No, I haven't done any factory reset till now.
Even the recovery option doesn't proceed to further options on bootloader page.

You can't get into the recovery menu? When you chose it and get the dead android do you quickly tap the power+volume up combo?