Develop Bugs

[Guide] Re-lock and Un-root WI-FI Xoom Build HWI69

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

[Unroot] How to Unroot Nexus 10! [Factory Firmware]

Here's a video tutorial guide for noobs who want to unroot/unbrick your Nexus 10.
Drivers: http://stockroms.net/file/Drivers/android/usb_driver.zip
fastboot for Windows/Mac/Linux: http://downloadandroidrom.com/file/tools/fastboot.zip
Stock Firmware: http://stockroms.net/file/Nexus10
For Windows, type: (XXX may depend on the stock firmware)
Code:
fastboot flash bootloader bootloader-XXX.img
fastboot reboot-bootloader
fastboot flash radio radio-XXX-XXX.img
fastboot reboot-bootloader
fastboot -w update image-XXX-XXX.zip
For Mac OSX, type: (XXX may depend on the stock firmware)
Code:
./fastboot-mac flash bootloader bootloader-XXX.img
./fastboot-mac reboot-bootloader
./fastboot-mac flash radio radio-XXX-XXX.img
./fastboot-mac reboot-bootloader
./fastboot-mac -w update image-XXX-XXX.zip
For Linux, type: (XXX may depend on the stock firmware)
Code:
./fastboot-linux flash bootloader bootloader-XXX.img
./fastboot-linux reboot-bootloader
./fastboot-linux flash radio radio-XXX-XXX.img
./fastboot-linux reboot-bootloader
./fastboot-linux -w update image-XXX-XXX.zip
*Note – If you do not have radio image, you can skip that one.
*Note for Mac/Linux – If you get permissions error, try “chmod 755 *” before doing all the commands and also try adding “sudo” in front of the commands if you still have trouble.
Step-by-Step guide with photos here

for some reason after doing the last step it automatically reboots and it ends up with an android with a triangle with an exclamation point ...help?

jarjar124 said:
for some reason after doing the last step it automatically reboots and it ends up with an android with a triangle with an exclamation point ...help?
Click to expand...
Click to collapse
Try pressing power, volumeup, and volumedown, all together until you see the blue menus, once you see that, do a factory reset and reboot.

zedomax said:
Try pressing power, volumeup, and volumedown, all together until you see the blue menus, once you see that, do a factory reset and reboot.
Click to expand...
Click to collapse
doesnt that bring me to the bootloader?
edit: now i cant mount sd card in recovery after doing this....i think this is why its not booting....any help?

Don't we need do the following code before unroot?
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata

if you really bricked yours as badly as I did, you might have to re format one or more partitions.
Fastboot format partitionname
Then fastboot flash partitionname imagefilename.
Sent from my Nexus 10 using xda premium

padest.com said:
Don't we need do the following code before unroot?
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
Click to expand...
Click to collapse
Don't think so, it overwrites everything so i don't think it matters.

I've fully flashed the factory image and it just sits there seemingly looping.
I've flashed the stock recovery, from Stockroms . net, the bootloader and image from the Google Developers page and it still just sits there.
Anyone have any ideas?
I've also tried erasing all partitions and then flashing again. Right now i`m willing to try anything

Why not link to the official source?
https://developers.google.com/android/nexus/images#mantaray

H3g3m0n said:
Why not link to the official source?
https://developers.google.com/android/nexus/images#mantaray
Click to expand...
Click to collapse
Also doesn't the official archive even come with a batch file that does all the necessary commands automatically? The latest pre-4.2 image from Google for the Nexus 7 did anyway.
padest.com said:
Don't we need do the following code before unroot?
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
Click to expand...
Click to collapse
The batch file I mentioned above for the N7 did this, and a guide somewhere else written before said that this was necessary due to some bug in the past (I guess something wasn't being overwritten properly).

Hmm, I did just the 'fastboot -w update image-mantaray-jop40c.zip' since I didn't want to mess with the bootloader, just reflash the stock rom.
Got the red triangle with !, rebooted and still got it, but after a few minutes it rebooted by itself and worked. Hopefully it was just doing some kind of first boot thing or wiping stuff.
EDIT: Also seems to have flashed over my recovery, but no biggie.

Where did I go wrong?
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\DMR>cd Downloads
C:\Users\DMR\Downloads>cd fastboot
The system cannot find the path specified.
C:\Users\DMR\Downloads>cd fastbot
The system cannot find the path specified.
C:\Users\DMR\Downloads>cd fastboot
C:\Users\DMR\Downloads\fastboot>fastboot flash bootloader bootloader-manta-ma
ntalj12.img
sending 'bootloader' (1280 KB)...
OKAY [ 0.157s]
writing 'bootloader'...
OKAY [ 0.137s]
finished. total time: 0.295s
C:\Users\DMR\Downloads\fastboot>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
C:\Users\DMR\Downloads\fastboot>fastboot -w update image-mantaray-jop40c.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MANTALJ12
Baseband Version.....: no modem
Serial Number........: R32CA04NW1T
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.002s]
sending 'boot' (4606 KB)...
OKAY [ 0.573s]
writing 'boot'...
OKAY [ 0.131s]
sending 'recovery' (5106 KB)...
OKAY [ 0.637s]
writing 'recovery'...
OKAY [ 0.138s]
sending 'system' (528847 KB)...
OKAY [ 65.906s]
writing 'system'...
OKAY [ 14.811s]
erasing 'userdata'...
OKAY [ 0.231s]
erasing 'cache'...
OKAY [ 0.034s]
rebooting...
finished. total time: 82.474s
C:\Users\DMR\Downloads\fastboot>
Click to expand...
Click to collapse

espionage724 said:
Also doesn't the official archive even come with a batch file that does all the necessary commands automatically? The latest pre-4.2 image from Google for the Nexus 7 did anyway.
Click to expand...
Click to collapse
Here is exactly what the batch file from Google says:
Code:
@ECHO OFF
:: Copyright 2012 The Android Open Source Project
::
:: Licensed under the Apache License, Version 2.0 (the "License");
:: you may not use this file except in compliance with the License.
:: You may obtain a copy of the License at
::
:: http://www.apache.org/licenses/LICENSE-2.0
::
:: Unless required by applicable law or agreed to in writing, software
:: distributed under the License is distributed on an "AS IS" BASIS,
:: WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
:: See the License for the specific language governing permissions and
:: limitations under the License.
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-manta-mantalj12.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-mantaray-jop40c.zip
echo Press any key to exit...
pause >nul
exit

Mine does same thing
t-mizzle said:
Where did I go wrong?
Click to expand...
Click to collapse
Reboots after erasing cache and then will hang on Nexus X screen forever. Any extra steps or commands to assist?

Not working...
So I somehow bricked my N10 (all I did was flash CWM recovery, and then I couldn't mount /sdcard and it bootloops) so I tried this.
I get this:
Code:
% fastboot-mac -w update image-mantaray-jop40c.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MANTALJ12
Baseband Version.....: no modem
Serial Number........: R32CB01971P
--------------------------------------------
checking product... OKAY
checking version-bootloader... OKAY
sending 'boot' (4606 KB)... OKAY
writing 'boot'... OKAY
sending 'recovery' (5106 KB)... OKAY
writing 'recovery'... OKAY
sending 'system' (528847 KB)... ERROR: usb_write failed with status e00002be
FAILED (data transfer failure (No such file or directory))
Anyone have any ideas?...

format?
fastboot help file doesn't show format, it is erase <partition>
Is that the correct command?
c0t0d0s2 said:
if you really bricked yours as badly as I did, you might have to re format one or more partitions.
Fastboot format partitionname
Then fastboot flash partitionname imagefilename.
Sent from my Nexus 10 using xda premium
Click to expand...
Click to collapse
---------- Post added at 10:38 PM ---------- Previous post was at 10:07 PM ----------
t-mizzle said:
Where did I go wrong?
Click to expand...
Click to collapse
So I was kind of stuck at same spot you were I believe, where after the cache the device autorebooted and then hung on the splash screen.
I booted into the (now) stock recovery and formatted and wiped cache and it booted up fine. Hope you have the same luck.

I did exaclty what the OP said and I am at the boot up boot image of the X that is multi color and it just loops there.

I'm still stuck in bootloop. Entering recovery from fastboot brings up the laying android icon with the red triangle/exclamation mark.
What steps do I take next?

t-mizzle said:
I'm still stuck in bootloop. Entering recovery from fastboot brings up the laying android icon with the red triangle/exclamation mark.
What steps do I take next?
Click to expand...
Click to collapse
Press power and volume up and let go, you'll get various recovery options. Select wipe data and confirm. It'll wipe, then reboot.

Hatman41 said:
Press power and volume up and let go, you'll get various recovery options. Select wipe data and confirm. It'll wipe, then reboot.
Click to expand...
Click to collapse
Looks like today I'm more stupid than usually. I tried pressing power and volume up both in fastboot and in recovery mode, neither gave me recovery options. I know I am close but I can't nail it...

Format partitions in fastboot mode

Hi, my kf2 is stucked at fastboot, i'm not able to boot into recovery or system, i have succesfully installed fff-1.4a using a factory cable (because it was bricked with the stock bootloader) and have installed the otter2-twrp-2.4.4.0-recovery.img from hashcode..
It boots and i see the blue kindle logo, and have a menu, but when i select recevery it just turns on the amber light and stays there, i have left it for about 5 minutes waiting to see if it get to revery with no luck.
I tried this:
Code:
sudo fastboot -i 0x18d1 getvar product
< waiting for device >
product: kindle
finished. total time: 0.000s
sudo fastboot -i 0x18d1 oem format
...
OKAY [ 0.068s]
finished. total time: 0.068s
Then
Code:
sudo fastboot -i 0x18d1 flash boot fff-u-boot_v1.4a.bin
< waiting for device >
sending 'boot' (243 KB)...
OKAY [ 0.065s]
writing 'boot'...
OKAY [ 0.051s]
finished. total time: 0.115s
sudo fastboot reboot
rebooting...
sudo fastboot -i 0x18d1 flash boot fff-u-boot_v1.4a.bin
< waiting for device >
sending 'boot' (243 KB)...
OKAY [ 0.065s]
writing 'boot'...
OKAY [ 0.051s]
finished. total time: 0.115s
It succeed as you can see, it has the fff bootloader and twrp recovery is installed!!
Then i tried
Code:
sudo fastboot -i 0x18d1 flash zip cm-10.1-20130704-NIGHTLY-otter2.zip
< waiting for device >
sending 'zip' (155204 KB)...
OKAY [ 38.806s]
writing 'zip'...
FAILED (remote: partition does not exist)
finished. total time: 38.813s
It seem like a partition table problem maybe because i'm trying to install Cyanogenmod and not a stock image...
I think maybe i must reformat the partitions but i only have access to fastboot and i have read the documentation of Android Fastboot in OmapPedia but i'm not sure it's a "generic" information and don't want to mess up things more.
I have read many trheads in the forum but all of them use adb and there's not a thread with instructions about it..
Or maybe i need to flash all the images (system, kernel, etc..) with fastboot but i don't know where to get it, the main problem is that i'm not able to boot into recovery and maybe that point to the real problem
Any help is appreciated !!
Thank's

You can't write CyanogenMod from fast boot.
Sounds like somewhere in there you formatted the system partition. You need the stack file on the system partition in order to boot into recovery.
Restore to stock using fast boot and try again.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

How?
mindmajick said:
You can't write CyanogenMod from fast boot.
Sounds like somewhere in there you formatted the system partition. You need the stack file on the system partition in order to boot into recovery.
Restore to stock using fast boot and try again.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Maybe it is the problem as fastboot oem format seems to do the job...
I have downloaded the stock update-kindle-6.3.2_D01E_4110520.bin, please can you point to the thread explainig how to do that using fastboot or it's just as easy as rename the file to update.zip and flash it directly?
Edited: also i'm not completely sure it's a kf2 and can't get a hint on how to discover it without knowing the is version :banghead: I've looked one the motherboard and is a MB0090 F3F.
I've downloaded the stock bin for the kf2 too...
Thank' for your quick reply

Well. If you have a kf2... The update you downloaded is wrong. IT'S FOR THE ORIGINAL KINDLE FIRE.
Without knowing what device u have u better slow down a sec. Any advice i give COULD permabrick u of you're on the wrong device.
What color was the BOX it came in? What is the model# on the back? (Same for kf1 AND 2 BUT NOT THE KF HD 7" OR 8").
Be advised- this device is EASY TO BRICK. BE CAREFUL.
--
Sent from my mind to your screen.
---------- Post added at 02:48 AM ---------- Previous post was at 02:40 AM ----------
Also. The correct update file wont work either.
You can only flash image files from fastboot.
--
Sent from my mind to your screen.

It's apparent you have a KF1 and not a KF2. The command "fastboot -i 0x18d1..." would not work on the KF2 because it still has the stock bootloader (unless something miraculous happened while I was AFK). The stock bootloader has a VID of 1949, and will not answer to commands using a different VID. 18d1 is Goggle's VID and is indicative of having FFF installed (KF1 only).
BTW, the "-i 0x18d1" part is completely unnecessary on FFF.
That's not your biggest problem though....
Code:
sudo fastboot -i 0x18d1 flash boot fff-u-boot_v1.4a.bin
That command is completely wrong. What you're doing there is flashing the bootloader (fff-u-boot_v1.4a.bin) to the boot (kernel) partition. Obviously, there is no way that could possibly would work out for you. After the "fastboot" portion of the command, you need to specify what you want done with the image in question: flash or boot. "Flash" is persistent, "boot" is for one boot only. In the next part of the command, you need to specify which partition the image in question goes to; bootloader, recovery, boot, etc.
What you need to do is get an actual recovery.img and flash it to your recovery partition before you can even think of accessing said recovery to flash a ROM and get your device working again.

soupmagnet said:
It's apparent you have a KF1 and not a KF2. The command "fastboot -i 0x18d1..." would not work on the KF2 because it still has the stock bootloader (unless something miraculous happened while I was AFK). The stock bootloader has a VID of 1949, and will not answer to commands using a different VID. 18d1 is Goggle's VID and is indicative of having FFF installed (KF1 only).
BTW, the "-i 0x18d1" part is completely unnecessary on FFF.
That's not your biggest problem though....
Code:
sudo fastboot -i 0x18d1 flash boot fff-u-boot_v1.4a.bin
That command is completely wrong. What you're doing there is flashing the bootloader (fff-u-boot_v1.4a.bin) to the boot (kernel) partition. Obviously, there is no way that could possibly would work out for you. After the "fastboot" portion of the command, you need to specify what you want done with the image in question: flash or boot. "Flash" is persistent, "boot" is for one boot only. In the next part of the command, you need to specify which partition the image in question goes to; bootloader, recovery, boot, etc.
What you need to do is get an actual recovery.img and flash it to your recovery partition before you can even think of accessing said recovery to flash a ROM and get your device working again.
Click to expand...
Click to collapse
Well you are completely right!! Didn't realize I was flashing it to the kernel partition, I bought this on eBay and it was already bricked, when I used the factory cable first time I got a lab26 device, and it was a 1949 so, if I'm right it's a kf2.
I've already flashed a twrp recovery but it won't boot.. I'll try sintering else and post the results here
Sent from my SPH-D710 using xda premium

LUC4X said:
when I used the factory cable first time I got a lab26 device, and it was a 1949 so, if I'm right it's a kf2.
I've already flashed a twrp recovery but it won't boot.. I'll try sintering else and post the results here
Click to expand...
Click to collapse
No. The stock bootloader on all generations and variants of Kindle Fires have vendor IDs of 1949. The fact that your device responds to the "fastboot -i 0x18d1..." clearly means you have a custom bootloader installed in its place. If you have an actual custom bootloader installed (not 2nd bootloader) then you clearly cannot possibly have a KF2.
In this thread, you say you have installed recovery twice, but the information given seems to suggest otherwise.
So to try and get to the root of the problem, what is the exact command you used to install custom recovery, and what custom recovery (version) did you install?

Glad you are here soupmagnet!
I didn't even look at the commands he was using but i definitely learned stuff from your posts. Thanks again
--
Sent from my mind to your screen.

Commands used
soupmagnet said:
No. The stock bootloader on all generations and variants of Kindle Fires have vendor IDs of 1949. The fact that your device responds to the "fastboot -i 0x18d1..." clearly means you have a custom bootloader installed in its place. If you have an actual custom bootloader installed (not 2nd bootloader) then you clearly cannot possibly have a KF2.
In this thread, you say you have installed recovery twice, but the information given seems to suggest otherwise.
So to try and get to the root of the problem, what is the exact command you used to install custom recovery, and what custom recovery (version) did you install?
Click to expand...
Click to collapse
Sorry guys i was out of town...
These are the commands (bootloader & recovery) i've used till now:
sudo fastboot -i 0x18d1 flash bootloader fff-u-boot_v1.4a.bin
< waiting for device >
sending 'bootloader' (243 KB)...
OKAY [ 0.065s]
writing 'bootloader'...
OKAY [ 0.083s]
finished. total time: 0.148s
sudo fastboot -i 0x18d1 flash recovery otter2-twrp-2.4.4.0-recovery.img
sending 'recovery' (8153 KB)...
OKAY [ 2.042s]
writing 'recovery'...
OKAY [ 2.705s]
finished. total time: 4.748s
Click to expand...
Click to collapse
Also tryed the twrp from teamw's site in both versions (otter & blaze) just to make sure, by issuing the following commands:
sudo fastboot -i 0x18d1 flash recovery openrecovery-twrp-2.5.0.0-blaze.img
< waiting for device >
sending 'recovery' (6144 KB)...
OKAY [ 1.540s]
writing 'recovery'...
OKAY [ 1.514s]
finished. total time: 3.054s
Click to expand...
Click to collapse
With this, when i reboot and select the recovery it turns on the amber light for 2 seconds and shuts down.
Then when i install the other recovery version (blaze from teamw):
sudo fastboot -i 0x18d1 flash recovery openrecovery-twrp-2.5.0.0-otter.img
< waiting for device >
sending 'recovery' (6144 KB)...
OKAY [ 1.540s]
writing 'recovery'...
OKAY [ 0.684s]
finished. total time: 2.224s
Click to expand...
Click to collapse
When select recovery i get the same result: amber light for 2 seconds and turns off.
And with hashcode otter2-twrp-2.4.4.0-recovery.img:
sudo fastboot -i 0x18d1 flash recovery otter2-twrp-2.4.4.0-recovery.img
< waiting for device >
sending 'recovery' (8153 KB)...
OKAY [ 2.042s]
writing 'recovery'...
OKAY [ 0.894s]
finished. total time: 2.937s
Click to expand...
Click to collapse
It hangs on amber light and i have to manually turn it off holding the power buttom for 10 seconds...
So you think it is a kf1 based on the device id?, it shows that id after i installed the fff-u-boot_v1.4a.bin from hashcode that i intended for the kf2...
Well, based on that i have installed a kf1 bootloader:
Downloaded the Kindle Fire Utility v0.9.9.zip from http://forum.xda-developers.com/showthread.php?t=2192818
Unzipped it (as i'm GNU/Linux)
"Grepped" recursively till find the web address to download files from
Downloaded fff-u-boot_v1.4a.bin
Downloaded openrecovery-twrp-2.4.4.0-blaze.img
Followed the install procedure
Same result !!, still can't get it to boot into recovery...
Really i hope someone here can point me to the right direction to fix this tablet, can't figure out what's wrong with kf(?)

LUC4X said:
So you think it is a kf1 based on the device id?, it shows that id after i installed the fff-u-boot_v1.4a.bin from hashcode that i intended for the kf2...
Well, based on that i have installed a kf1 bootloader:
Downloaded the Kindle Fire Utility v0.9.9.zip from http://forum.xda-developers.com/showthread.php?t=2192818
Unzipped it (as i'm GNU/Linux)
"Grepped" recursively till find the web address to download files from
Downloaded fff-u-boot_v1.4a.bin
Downloaded openrecovery-twrp-2.4.4.0-blaze.img
Followed the install procedure
Same result !!, still can't get it to boot into recovery...
Really i hope someone here can point me to the right direction to fix this tablet, can't figure out what's wrong with kf(?)
Click to expand...
Click to collapse
Lets get a few things clear right off the bat. The file named fff-u-boot_v1.4a.bin is the custom bootloader for the KF1. The bootloader flashed in the KF2 2nd bootloader installation is named otter2-u-boot-prod-10.2.4.bin. If you flash the fff-u-boot_v1.4a.bin (FFF1.4a) onto a KF2, you would end up with something that is slightly less useful than a doorstop.
Why you re-installed it is a mystery to me. You already had FFF1.4a installed. I know this (as I explained earlier) by the fact that your commands, using the "-i 0x18d1" switch, were successful. If you had a stock bootloader, no commands containing that particular vendor ID would work at all. If you had a KF2, there is absolutely NO WAY you would have a device that responds to fastboot commands using "-i 0x18d1". Even with a modified KF2, with 2nd bootloader installed, the vendor ID would still be 1949 and all fastboot commands must include "-i 0x1949" or they will not work. You can confirm the fact that you have FireFireFire installed by entering a fastboot command without adding "i- 0x18d1". With FireFireFire (KF1 only), the commands will still work because it is unnecessary to specify the vendor ID.
That being said, I'm not entirely sure what's going on with TWRP using both "otter" and "blaze" for the board name (I think it has something to do with Goo Manager?), but anything you get from the TWRP website should work for the KF1 (for the time being at least). Anything you get from Hashcode will be for the 2nd generation KFs.
I would suggest, to avoid complicating things any further, that you download Cannibal Open Touch recovery, confirm that the MD5sums match after downloading, and flash it to recovery in fastboot. COTR only works for the KF1 (not made for the 2nd Generation devices yet) so there is "practically" no way you can get the wrong one. If that works and you still want to try TWRP, download the one for Blaze, check the MD5 (as you should with everything), and try flashing it in recovery again.
If you still can't get your device to boot into recovery, try the command again, but replace the word "flash" with the word "boot" and leave out the partition (i.e. 'fastboot boot openrecovery-twrp-2.4.4.0-blaze.img'). If the device boots into recovery, then you know you have the right one and you may have bad blocks in your recovery partition preventing it from booting, but you won't know for sure without checking a few things out first.

Followed your instructions and get the same result...
Maybe i should install a complete system from fastboot and let it try to boot, but where can i get those files?
What do you think?

soupmagnet said:
Lets get a few things clear right off the bat. The file named fff-u-boot_v1.4a.bin is the custom bootloader for the KF1. The bootloader flashed in the KF2 2nd bootloader installation is named otter2-u-boot-prod-10.2.4.bin. If you flash the fff-u-boot_v1.4a.bin (FFF1.4a) onto a KF2, you would end up with something that is slightly less useful than a doorstop.
Why you re-installed it is a mystery to me. You already had FFF1.4a installed. I know this (as I explained earlier) by the fact that your commands, using the "-i 0x18d1" switch, were successful. If you had a stock bootloader, no commands containing that particular vendor ID would work at all. If you had a KF2, there is absolutely NO WAY you would have a device that responds to fastboot commands using "-i 0x18d1". Even with a modified KF2, with 2nd bootloader installed, the vendor ID would still be 1949 and all fastboot commands must include "-i 0x1949" or they will not work. You can confirm the fact that you have FireFireFire installed by entering a fastboot command without adding "i- 0x18d1". With FireFireFire (KF1 only), the commands will still work because it is unnecessary to specify the vendor ID.
That being said, I'm not entirely sure what's going on with TWRP using both "otter" and "blaze" for the board name (I think it has something to do with Goo Manager?), but anything you get from the TWRP website should work for the KF1 (for the time being at least). Anything you get from Hashcode will be for the 2nd generation KFs.
I would suggest, to avoid complicating things any further, that you download Cannibal Open Touch recovery, confirm that the MD5sums match after downloading, and flash it to recovery in fastboot. COTR only works for the KF1 (not made for the 2nd Generation devices yet) so there is "practically" no way you can get the wrong one. If that works and you still want to try TWRP, download the one for Blaze, check the MD5 (as you should with everything), and try flashing it in recovery again.
If you still can't get your device to boot into recovery, try the command again, but replace the word "flash" with the word "boot" and leave out the partition (i.e. 'fastboot boot openrecovery-twrp-2.4.4.0-blaze.img'). If the device boots into recovery, then you know you have the right one and you may have bad blocks in your recovery partition preventing it from booting, but you won't know for sure without checking a few things out first.
Click to expand...
Click to collapse
Followed your instructions and get the same result...
Maybe i should install a complete system from fastboot and let it try to boot, i've found you uploaded a system.img to androidfilehost...
What do you think?

I posted that ages ago. I'm not even sure what device it's for.
Check the file size. If it's around 350MB go ahead. If it's closer to 500MB then it's probably for the HD.
I can't imagine why you couldn't load recovery using the 'fastboot boot recovery.img' command. Did you receive any errors when trying?

soupmagnet said:
I posted that ages ago. I'm not even sure what device it's for.
Check the file size. If it's around 350MB go ahead. If it's closer to 500MB then it's probably for the HD.
I can't imagine why you couldn't load recovery using the 'fastboot boot recovery.img' command. Did you receive any errors when trying?
Click to expand...
Click to collapse
There's not error message, this is the output:
Code:
sudo fastboot boot CannibalOpenTouch-v2.1_otter.img
< waiting for device >
downloading 'boot.img'...
OKAY [ 1.394s]
booting...
OKAY [ 0.004s]
finished. total time: 1.398s
But it never boots up and stays off.
I'm seriously thinking it may be a hardware failure but i wont give up until i'm completely sure about it.. that's why i though i should reformat partitions at the first time but the fastboot oem format command "seems" to work, perhaps it takes very short time to execute 0.068s and it is a very short time, so i though maybe it isn't really formatting anything, is it a "normal time"?
Right now i'm downloading the file it's 380MB maybe something good could happen!!
I'll try the following and will post the results:
Code:
fastboot flash system system.img
fastboot erase userdata
fastboot erase cache
fastboot reboot

LUC4X said:
There's not error message, this is the output:
Code:
sudo fastboot boot CannibalOpenTouch-v2.1_otter.img
< waiting for device >
downloading 'boot.img'...
OKAY [ 1.394s]
booting...
OKAY [ 0.004s]
finished. total time: 1.398s
But it never boots up and stays off.
I'm seriously thinking it may be a hardware failure but i wont give up until i'm completely sure about it.. that's why i though i should reformat partitions at the first time but the fastboot oem format command "seems" to work, perhaps it takes very short time to execute 0.068s and it is a very short time, so i though maybe it isn't really formatting anything, is it a "normal time"?
Right now i'm downloading the file it's 380MB maybe something good could happen!!
I'll try the following and will post the results:
Code:
fastboot flash system system.img
fastboot erase userdata
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
The command 'fastboot oem format' will only make sure the partition layout is stock, it does not format the partitions themselves. The information within the limits of the partitions will remain untouched, so it won't do you much good in this situation. The only way to properly format any partition is with recovery (or 'parted' which is usually run from recovery anyway). Your situation is rather unique because the "fastboot boot' command doesn't write anything to the recovery partition. It loads the disk image you choose, into active memory, as if your computer were a separate partition on which that image is stored. There shouldn't be any reason for it to not work properly.
Try to flash the system partition you downloaded and see how it goes. I would also suggest that you make absolutely sure the md5sums match before installing any image to your device, including the recovery images you downloaded before.

soupmagnet said:
The command 'fastboot oem format' will only make sure the partition layout is stock, it does not format the partitions themselves. The information within the limits of the partitions will remain untouched, so it won't do you much good in this situation. The only way to properly format any partition is with recovery (or 'parted' which is usually run from recovery anyway). Your situation is rather unique because the "fastboot boot' command doesn't write anything to the recovery partition. It loads the disk image you choose, into active memory, as if your computer were a separate partition on which that image is stored. There shouldn't be any reason for it to not work properly.
Try to flash the system partition you downloaded and see how it goes. I would also suggest that you make absolutely sure the md5sums match before installing any image to your device, including the recovery images you downloaded before.
Click to expand...
Click to collapse
Code:
sudo fastboot flash system system.img
sending 'system' (389120 KB)...
OKAY [ 97.308s]
writing 'system'...
OKAY [ 36.819s]
finished. total time: 134.131s
sudo fastboot erase userdata
erasing 'userdata'...
OKAY [116.935s]
finished. total time: 116.935s
sudo fastboot erase cache
erasing 'cache'...
OKAY [ 29.189s]
finished. total time: 29.189s
sudo fastboot reboot
rebooting...
finished. total time: 0.000s
Must be hardware, it's sad... if it where a SMD flash memory i would try to changed it but it's a tyni BGA chip...
Thank you very much for your help

I wouldn't give up just yet. You can still try to usbboot, using the shorting trick.

soupmagnet said:
I wouldn't give up just yet. You can still try to usbboot, using the shorting trick.
Click to expand...
Click to collapse
I'll try tonight !!
Sent from my SPH-D710 using xda premium

soupmagnet said:
I wouldn't give up just yet. You can still try to usbboot, using the shorting trick.
Click to expand...
Click to collapse
./usb_fix_parts_and_install_fff_twrp
Loading FFF through USB...
?
waiting for OMAP44xx device...
sending 2ndstage to target...
waiting for 2ndstage response...
sending image to target...
Fixing partitions...
< waiting for device >
... OKAY
Installing x-loader...
sending 'xloader' (128 KB)... OKAY
writing 'xloader'... OKAY
Flash FFF...
sending 'bootloader' (211 KB)... OKAY
writing 'bootloader'... OKAY
Flash TWRP...
sending 'recovery' (5260 KB)... OKAY
writing 'recovery'... OKAY
Resetting bootmode to standard boot...
... OKAY
Loading TWRP...
downloading 'boot.img'... OKAY
booting... OKAY
Click to expand...
Click to collapse
Same as before, it won't reboot after sending the boot to recovery command and if try to get into recovery it turns off after an amber light..

LUC4X said:
Followed your instructions and get the same result...
Maybe i should install a complete system from fastboot and let it try to boot, but where can i get those files?
What do you think?
Click to expand...
Click to collapse
At the begining i saw you were using "fastboot flash zip...." that's wrong command.. should be "fastboot flash update xxxx.zip"
so if you find the totally package, youcan use it.
also you has mixture the boot.img and bootloader.bin..
recovery is not needed if you can flash the right bootloader and boot.:laugh:

Another Hard Brick Nexus 7 2013 help please

I try updating via abd, Now hard brick, as it cannot update boot.img
Use Vol Down + Power to attempt to get to bootloader, it boot the Teamwin screen this reboot back Google logo then reboot back to Teamwin screen again, cannot get into trwp at all.
On the Teamwin sreen it saying wiping something, but I cannot read it quick enough.
Abd No luck as well, help please.
Can you please explain what to do now, I would greatly appreciate your help, or I going to throw it in the bin.
Edit: Managed to get into Bootloader now problem below
C:\adb>flash-all.bat
sending 'bootloader' (3911 KB)...
OKAY [ 0.138s]
writing 'bootloader'...
OKAY [ 1.426s]
finished. total time: 1.570s
rebooting into bootloader...
OKAY [ 0.012s]
finished. total time: 0.016s
error: update package missing boot.img
Press any key to exit...
I check the zip file it has boot.img inside it?
Ok how to flashboot manually as I've unpack the zip what the procedure?
Ok I found flash manual.bat
Here the script:
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-flo-flo-04.05.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
exit
echo Press any key to exit...
pause >nul
exit
Anyway cross fingers I rebooting now, and hope to see Android I let you in 15 minutes,

Well it won't boot into Android 6? what now?

right got it going again when back to mra58k, i found nrt 2.06 has issue which cause my problem in the first place.

NOOB NEEDS HELP unlocked htc convert to verizon

well, basically i have no clue what im doing and im in desperate need of help. I have managed to get the phone into S-OFF and unlocked but now im stuck on how exactly i change the radio image and etc. mainly because i am so incompetent when it comes to this coding stuff. can someone give me a very very detailed walk through? i cant even get past my first commands and im losing my mind. any help will be appreciated really dont want to waste $700 on this phone idk if this helps but im trying to do this on a MAC

dfoote87 said:
well, basically i have no clue what im doing and im in desperate need of help. I have managed to get the phone into S-OFF and unlocked but now im stuck on how exactly i change the radio image and etc. mainly because i am so incompetent when it comes to this coding stuff. can someone give me a very very detailed walk through? i cant even get past my first commands and im losing my mind. any help will be appreciated really dont want to waste $700 on this phone idk if this helps but im trying to do this on a MAC
Click to expand...
Click to collapse
[Guide] Convert US Unlocked to Verizon Variant (w/ proper IMS/hd Voice/Wifi Calling!)]

Im ****ed.
Truthfully, I dont even know what program/directory i need to flash the radio IMG or how to even enure i dont brick the phone. .... i dont even know how to type code. Is there anyway someone could mirror my computer and basically do everything for me? id be willing to pay some cash for it.

dfoote87 said:
Truthfully, I dont even know what program/directory i need to flash the radio IMG or how to even enure i dont brick the phone. .... i dont even know how to type code. Is there anyway someone could mirror my computer and basically do everything for me? id be willing to pay some cash for it.
Click to expand...
Click to collapse
Lol, no need for that. Have you gone through the thread linked by andy? Tell us whats clear for you and what's not and we'll try to help.

Tarima said:
Lol, no need for that. Have you gone through the thread linked by andy? Tell us whats clear for you and what's not and we'll try to help.
Click to expand...
Click to collapse
well, i think i have fastboot downloaded, and the radio image in andys link, i just dont know how to type commands and etc in terminal and how to tell if im even connected to the phone properly.

dfoote87 said:
well, i think i have fastboot downloaded, and the radio image in andys link, i just dont know how to type commands and etc in terminal and how to tell if im even connected to the phone properly.
Click to expand...
Click to collapse
The link doesn't tell you to flash the radio by itself, it says to flash a full verizon ruu which will bring your phone to complete verizon software including the radio. So if you're already S-off, just need to change cid and mid, find a Verizon ruu and flash it.
I don't have a Mac, but try the instructions in this video (only until the part where he enters the first terminal command) and see if you can communicate with the phone using fastboot.

Well ive got fastboot communicating with my phone. now i cant get it to flash or change cid im sure im doing something wrong

dfoote87 said:
Well ive got fastboot communicating with my phone. now i cant get it to flash or change cid im sure im doing something wrong
Click to expand...
Click to collapse
Can you give more details? What do you mean your can't change cid?
You need to be in Download mode to make those changes (vol down + pwr). What steps did you take?

I downloaded the file to change the CID. copy and pasted the code and it keeps saying command not found

the phone is in download mode

Brittanys-MacBook-Pro:desktop brittrobinette$ ./fastboot devices
HT6B4BN01483 fastboot
Brittanys-MacBook-Pro:desktop brittrobinette$ ./fastboot htc_fastboot oem writecid VZW__001
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default: 2048
Brittanys-MacBook-Pro:desktop brittrobinette$

i have the files on the desktop screen btw

dfoote87 said:
the phone is in download mode
Click to expand...
Click to collapse
What command are you entering to change cid? Don't forget, from the video I sent you you have to add ./ before typing fastboot
---------- Post added at 03:24 AM ---------- Previous post was at 03:19 AM ----------
dfoote87 said:
Brittanys-MacBook-Pro:desktop brittrobinette$ ./fastboot devices
HT6B4BN01483 fastboot
Brittanys-MacBook-Pro:desktop brittrobinette$ ./fastboot htc_fastboot oem writecid VZW__001
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default: 2048
Brittanys-MacBook-Pro:desktop brittrobinette$
Click to expand...
Click to collapse
Redo the same thing, but remove the htc_fastboot part.
So, instead, type:
fastboot oem writecid VZW__001
Edit:
Actually in your case it's
./fastboot oem writecid VZW__001

i looked at the CID and MID and the CID is BS_US001
MID-2PS650000 so i dont think they need changed.

dfoote87 said:
i looked at the CID and MID and the CID is BS_US001
MID-2PS650000 so i dont think they need changed.
Click to expand...
Click to collapse
Correct.
Did the command I wrote work?

Brittanys-MacBook-Pro:desktop brittrobinette$ ./fastboot flash radio /Users/brittrobinette/Desktop/VzwHTC10_1.19.605.9radio.img
sending 'radio' (71680 KB)...
OKAY [ 3.785s]
writing 'radio'...
(bootloader) HOSD CL#801953
FAILED (remote: 35 RU_PARTITION_NOT_SUPPORT radio)
finished. total time: 4.791s

dfoote87 said:
Brittanys-MacBook-Pro:desktop brittrobinette$ ./fastboot flash radio /Users/brittrobinette/Desktop/VzwHTC10_1.19.605.9radio.img
sending 'radio' (71680 KB)...
OKAY [ 3.785s]
writing 'radio'...
(bootloader) HOSD CL#801953
FAILED (remote: 35 RU_PARTITION_NOT_SUPPORT radio)
finished. total time: 4.791s
Click to expand...
Click to collapse
Again, why are you not following the steps described in the thread linked by andy? There is nothing in there about flashing radios separately.

Tarima said:
Again, why are you not following the steps described in the thread linked by andy? There is nothing in there about flashing radios separately.
Click to expand...
Click to collapse
whenever i click on that file from DOTTAT it says it wont run on my OS because its a program for windows

dfoote87 said:
whenever i click on that file from DOTTAT it says it wont run on my OS because its a program for windows
Click to expand...
Click to collapse
Do you have a microSD card?

yes