Database Users

Before I scrap my phone...

Hi All,
I just bought a new Hero two days ago. Since then I performed the following steps:
1.) downloaded the kernel source from HTC
2.) Compiled a kernel.
3.) As root:
a.) adb push newBoot.img /sdcard
b.) # cat /dev/zero > /dev/mtd/mtd2
c.) #flash_image boot /sdcard/newBoot.img
I did not install a recovery image unfortunately.
So.. after doing those steps the phone reboots, and displays
"HTC". It doesn't progress past there.
things i've tried.
1.) Installed a known .img that works. Renamed Recovery-RA-1.5.2.img to /sdcard/newBoot.img
2.) Copied other images that might work to /sdcard/newBoot.img
3.) renamed an image to HERC[DIAG|IMG].zip
Any other ideas I can try? I can boot to fastboot screen. Just not sure what else to do before I scrap it.
Any suggestions welcome.

how long did you wait at the HTC screen? it can take up to 10 minutes after the first boot.

hmm.. I didn't wait more than 5 minutes... I'll give that a try and see what happens. Hopefully that's all there is to it....

or you can just download a stock RUU and flash that.. Will atleast get you back to stock.

OK I tried that.. but since I can't boot into linux, I cannot get any adb commands to respond.
Between the "htc" screen that goes nowhere and the
the fastboot screen, I'm not sure how to install it.
I keep getting a USB 170 error.
still waiting at the HTC screen.

Sitting at the "HTC" screen for over 20 minutes now.. So I'm assuming that it's not going to boot. I'll let it go for a few more minutes.
Is there a way to install the RUU image from the fastboot screen?

fred43 said:
Sitting at the "HTC" screen for over 20 minutes now.. So I'm assuming that it's not going to boot. I'll let it go for a few more minutes.
Is there a way to install the RUU image from the fastboot screen?
Click to expand...
Click to collapse
The phone just needs to be on and connected to the pc when you run the RUU.

I'm assuming by "on and connected" that adb commands need to work?
Unfortunately my phone has 2 states. fastboot, and "HTC" screen that I mentioned above. I am unable to run any adb commands in HTC screen mode ( NO USB device is detected.)
The only way I can detect a USB device is when the phone is in fastboot mode.

fred43 said:
I'm assuming by "on and connected" that adb commands need to work?
Unfortunately my phone has 2 states. fastboot, and "HTC" screen that I mentioned above. I am unable to run any adb commands in HTC screen mode ( NO USB device is detected.)
The only way I can detect a USB device is when the phone is in fastboot mode.
Click to expand...
Click to collapse
If you can get in to fastboot then you should be able to run RUU while booted up in to fastboot. If not then you should be able to flash either a boot.img or RA's recovery img while in fast boot. At that point you should be able to boot the phone or boot in to a recovery image and flash a rom.
Option 1) Copy Recovery-RA-1.5.2.img to your sdcard and do: fastboot boot /sdcard/Recovery-RA-1.5.2.img
Option 2) Download fresh rom (or any rom) and then extract the boot.img from the zip and copy it to your sdcard. And then fastboot boot /sdcard/boot.img
Option 3) You can TRY actually flashing an img through fastboot but I'm pretty sure it's disabled on our phones. fastboot flash recovery /sdcard/Recovery-RA-1.5.2.img
FYI - The kernel source available from HTC is for the GSM Hero, not CDMA. That's why you are having problems.
You can PM me if you have questions.

flipzmode said:
Option 1) Copy Recovery-RA-1.5.2.img to your sdcard and do: fastboot boot /sdcard/Recovery-RA-1.5.2.img
Click to expand...
Click to collapse
Ok this option looks promising. The problem I have is :
"cannot load '/sdcard/boot.img'"
running the command:
"fastboot boot /sdcard/boot.img" ( AS root on my linux machine )
Note: I can see the usb device with fastboot devices
I think this error is happening from the linux machine. I tried this command as a non-root user and got the same response.
flipzmode said:
FYI - The kernel source available from HTC is for the GSM Hero, not CDMA. That's why you are having problems.
Click to expand...
Click to collapse
Ah.. That is why. My original goal was to create a kernel module for the phone... looks like this could be challenging without the correct sources.

Ok this option looks promising. The problem I have is :
"cannot load '/sdcard/boot.img'"
running the command:
"fastboot boot /sdcard/boot.img" ( AS root on my linux machine )
Note: I can see the usb device with fastboot devices
Click to expand...
Click to collapse
Ok try running it off of your computer then. fastboot boot /home/user/boot.img (wherever you actually have it)
Ah.. That is why. My original goal was to create a kernel module for the phone... looks like this could be challenging without the correct sources.
Click to expand...
Click to collapse
Yup. That's our exact problem and why we are somewhat limited on what we can do for modifying stuff.

With HBOOT-1.41.0000, the boot option is disabled apparently...
sudo ~/android/android-sdk-linux_86/tools/fastboot boot ./boot.img
downloading 'boot.img'... FAILED (remote: not allow)

Yea I knew that with our hboot the option to flash via fastboot was disabled, but I have been able to successfully boot through it. That's how I test my boot imgs. Other than trying the RUU while you are in fastboot it seems like it's pretty dead.
What happens if you boot in to the recovery partition? The stock one. Does adb see the phone then?

Well I just tested the RUU, 1.29 version. I got this error:
ERROR[140]: BOOTLOADER VERSION ERROR
The recovery partition ( default one) apparently doesn't exist just shows an
X or something with a phone. ( The default image ?)
What version of fastboot are you using? That seems to be my only hope at this point.

Is this a "with google" branded phone?
The fastboot I have is the one that came with the sdk for windows. It doesn't provide me with any type of version number.

Ok, I got it to boot off of one of the later fresh.zip's boot.img.
The default version of hboot has most options of fastboot disabled.
However, there is a way of getting around it.
1.) boot into fastboot mode
2.) fastboot -s $DEVICEID oem rebootRUU
3.) fastboot whatever, upgrade, boot etc all seem to work.
Still waiting on the boot... still stuck at the "HTC" screen. hopefully it will boot up eventually.

fred43 said:
2.) fastboot -s $DEVICEID oem rebootRUU
Click to expand...
Click to collapse
I knew that command worked with adb (that's how you do a manual RUU) but I didn't think it worked in fastboot. Good to know.
See if you can adb now that it's running off a proper boot.img.

Well looks like I spoke to soon. The boot option apparently ignores the file argument while in oem mode.

OK. so I'm back at square one. IN RUU mode, is there anything I can do?
Can I get a stock image later than 1.29 somewhere? Something that will
pass the security check of the installer.

fred43 said:
OK. so I'm back at square one. IN RUU mode, is there anything I can do?
Can I get a stock image later than 1.29 somewhere? Something that will
pass the security check of the installer.
Click to expand...
Click to collapse
Not that has been made available, no. You didn't answer me earlier. Is your phone stamped "with google" on the back cover?

[SOLVED] i9020t - Hard bricked! bootloader not flashing - need ops file

Mistakenly I replaced /dev/mtd/mtd0 partition with dd command.
Now phone is not booting.
Am able to get into fastboot mod by using AdamOutler's Unbrickable mod applcation. But flashboot flash bootloader giving error
Code:
sending 'bootloader' (1536 KB)...
OKAY [ 0.210s]
writing 'bootloader'...
FAILED (remote: Write Fail)
finished. total time: 0.318s
Even tried with ODIN (without re partitioning) , but it also failed when flashing bootloader.
I think I need to re-partition my device. Any one have (or know to generate) odin partition system file ?
Any other way or work around ?
* Am in india, and I dont think samsung sells I9020T here.
* I saw the post http://forum.xda-developers.com/showthread.php?t=947950
but i couldnt find necessary files there.
EDIT:
I able to fix it.
If you want to know how I fixed it, here is it.
1. Boot into fastboot mod via unbrickable mod application.
2. fastboot boot stock-recovery.img
3. flash stock rom
4. everything will be fixed.

What did you do to get your phone "bricked?" So you cannot get into the bootloader at all? Are you sure its download mode you are getting to? It is really really hard to brick a Nexus s...
Sent from my Nexus S 4G using xda premium

As long as you can get into download mode and your computer will recognize the phone you're not bricked. From download you can reflash all the files to get the phone back up and running through Odin.

I am not able to flash bootloader. Even odin fails to flash it. I think I need to re partition my device. But OPS file is not available any where. If you know how to make it, plase help me.
Is there any way to format the bootloader partition ? (using fastboot) ?

Rem3Dy said:
What did you do to get your phone "bricked?" So you cannot get into the bootloader at all? Are you sure its download mode you are getting to? It is really really hard to brick a Nexus s...
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
I mistakenly replaced /dev/mtd/mtd0 with dd command. :'(
Can any one give me a copy of /dev/mtd/mtd0 ?
(you can make that by 'dd bs=4096 if=/dev/mtd/mtd0 of=/sdcard/filename')

jishnu7 said:
My phone is now in completely bricked form. Am only able to get into download mod.
I saw a post http://forum.xda-developers.com/showthread.php?t=947950
but i couldnt find necessary files there.
Please share odin/ops and other necessary files.
Click to expand...
Click to collapse
Why you can not use AdamOutler resurector ? It's really really worked ...just try it and you'll see
Take a look here , it was my problem => http://forum.xda-developers.com/showthread.php?t=1474539
Good luck!

surdu_petru said:
Why you can not use AdamOutler resurector ? It's really really worked ...just try it and you'll see
Take a look here , it was my problem => http://forum.xda-developers.com/showthread.php?t=1474539
Good luck!
Click to expand...
Click to collapse
I am using that to bootup my device. But am not able to flash bootloader.

jishnu7 said:
I am using that to bootup my device. But am not able to flash bootloader.
Click to expand...
Click to collapse
OK!
B : try again ...and wait for image UnBrickable to change..than press ...Downloade Mode ...... you'll see ( where it was Device not found, No device detected ) fastboot fastboot mode ...right now tape into terminal :
# ./fastboot flash bootloader bootloader.img
...you will see that copy something
# ./fastboot flash boot boot.img
..you will see that copy something
# ./fastboot flash recovery recovery.img
...you will see that copy something
- now you can go into recovery to flash your favorite system....100% works !!!
A : ( attention! you do not need to touch any key in your device : just open Ubuntu....and in terminal comm write :
>$ sudo su
passw : ( write your password)
># java -jar UnBrickableResurrectorR40.jar
- Select "S5PC110 (Nexus S)"
- connect USB cable
- put the battery back
and wait ....after a few seconds you will see img. UnBrickable changed , now follow the above instructions ..(B)....).
Good luck ! for me it works very nice !
If this does not work , you have only solutions : remove the battery from your phone , and leave it two or three days , than you can go to (A) than (B)

surdu_petru said:
OK!
B : try again ...and wait for image UnBrickable to change..than press ...Downloade Mode ...... you'll see ( where it was Device not found, No device detected ) fastboot fastboot mode ...right now tape into terminal :
# ./fastboot flash bootloader bootloader.img
...you will see that copy something
# ./fastboot flash boot boot.img
..you will see that copy something
# ./fastboot flash recovery recovery.img
...you will see that copy something
- now you can go into recovery to flash your favorite system....100% works !!!
A : ( attention! you do not need to touch any key in your device : just open Ubuntu....and in terminal comm write :
>$ sudo su
passw : ( write your password)
># java -jar UnBrickableResurrectorR40.jar
- Select "S5PC110 (Nexus S)"
- connect USB cable
- put the battery back
and wait ....after a few seconds you will see img. UnBrickable changed , now follow the above instructions ..(B)....).
Good luck ! for me it works very nice !
If this does not work , you have only solutions : remove the battery from your phone , and leave it two or three days , than you can go to (A) than (B)
Click to expand...
Click to collapse
I used 'flash bootloader' earlier also, it is not flashing. Giving some write failed error. That is my problem.

I've had the same thing happen... no matter what degree of flashing, which steps taken, NONE of the so called 100% working fixes take... phone gets stuck and hangs in the google bootloader screen.... NO RECOVERY AT ALL....
All the packs and ODIN techniques over the web seem to fail and NOTHING else but the proper files seem to be the last hope...
Once in awhile, one can get into fastboot... but any attempts to load recovery directly land flat and hard back on the google boot screen and don't budge... it's like the fastboot flash operations never happened... or some other error of enigmatic mystery thwart all attempts to get this rather expensive paperweight to revive...
There's gotta be some way to fix this!!
Anyone? please and thanks!

[Q] Stuck in Bootloader

Hi all,
my nexus wont start after (failed?!) flashing with factory image. bootloader and recovery mode are accessable. i have no backup so i need to flash a new img, but my tablet wont be recognized by my computer anymore(adb drivers not working?!). i tried to deinstall and reinstall the adb drivers alrdy. Device manager shows nexus 7 as Android Phone with "Android Bootloader interface" i cant install adb drivers while in bootloader. in recovery mode i succeeded installing the adb drivers and the tablet is shown correctly in device manager... i need help dont know what to do :crying: .. any suggestions ?

ADB and fastboot drivers are different.

Pirateghost said:
ADB and fastboot drivers are different.
Click to expand...
Click to collapse
yes .. what are u trying to tell me? dont get it.. i used nexus root toolkit to help me apply those drivers.. but it wont work for bootloader/fastboot mode.. i cant flash my tablet because my device wont be recognized by my pc.. im stuck at the bootloaderscreen/fastbootmode....

http://bit.ly/Zqk7pm

and what do u want me to type in there ? i alrdy used google for the last 7 hours ?

oads said:
and what do u want me to type in there ? i alrdy used google for the last 7 hours ?
Click to expand...
Click to collapse
SMH
i filled it in for you.....

Pirateghost said:
SMH
i filled it in for you.....
Click to expand...
Click to collapse
ok sry wasnt patient enough to see... ya well this all makes sense to someone who knows what hes doing but to a noob like me? i thought i alrdy installed fastboot drivers since i unrooted the device a month ago? do i need to deinstall the driver "Android Phone with "Android Bootloader interface"" in device manager first, before applying the new fastboot drivers? pls help me through this i think i damaged enough alrdy ..

no. ADB and fastboot require separate drivers. just install the drivers required for n7 fastboot. there was a link in that list.
there are tutorials here on xda, as well as youtube videos and tutorials on other sites. take a little initiative and learn the ropes. it will help you out later on.

oads said:
ok sry wasnt patient enough to see... ya well this all makes sense to someone who knows what hes doing but to a noob like me? i thought i alrdy installed fastboot drivers since i unrooted the device a month ago? do i need to deinstall the driver "Android Phone with "Android Bootloader interface"" in device manager first, before applying the new fastboot drivers? pls help me through this i think i damaged enough alrdy ..
Click to expand...
Click to collapse
Just relax and take your time.
If your tablet can go into fastboot mode, it is fine and will get better; the only thing standing between it's current state and being brought back to life is a little learning on your part.
Now you see what the problems are with using a toolkit - because they hide all the gory details from you, when the smallest thing goes wrong you are totally helpless due to a lack of understanding about what things are going on underneath the hood. And as it turns out, what "goes on under the hood" isn't really all that complicated either if you do things the full manual way.
Which is not to say that you can not simply just use the toolkit again; if you previously successfully installed drivers that allowed you to talk to the tablet in all of these modes:
- fastboot
- adb w/ custom recovery booted
- adb with Android booted
then it is not evident that you need to be fooling with drivers.
I suggest you read this thread, from start to finish
[GUIDE] Flashing a Factory Image with fastboot / return to stock
Then, go over to your toolkit thread and read it from start to finish. You will see that there are & have been plenty of people in circumstances nearly identical to yours.
good luck

hey thx for ur replies! im a lil more calm now than i was 30 min !
the big problem i still have is that my tablet will show up as Androidphone/Android Bootloader Interface not as an unknown device or as the Nexus 7 it is when i plug it in.. so i cant install the drivers am i correct? well i tried it a few times .. deinstalled and reinstalled .. the problem persists? anyone familiar with that? when i change into Recovery Modus it will show up as Androidphone/Google Nexus ADB Interface.. so my first steps to get rid of this mess would be ...?

oads said:
hey thx for ur replies! im a lil more calm now than i was 30 min !
the big problem i still have is that my tablet will show up as Androidphone/Android Bootloader Interface not as an unknown device or as the Nexus 7 it is when i plug it in.. so i cant install the drivers am i correct? well i tried it a few times .. deinstalled and reinstalled .. the problem persists? anyone familiar with that? when i change into Recovery Modus it will show up as Androidphone/Google Nexus ADB Interface.. so my first steps to get rid of this mess would be ...?
Click to expand...
Click to collapse
that does not sound like a problem to me at all.
You communicate with the device using the "fastboot" program when it is in bootloader/fastboot mode, and with the "adb" program when it is in custom recovery boot.
What you see in the device manager appears to be completely normal - In different modes it shows up in different places. It's not supposed to show up with the same driver in different modes.
Code:
fastboot devices
will show you whether you are communicating successfully with the device when it is in bootloader/fastboot mode, and
Code:
adb devices
will show you whether you are communicating successfully with the device in recovery mode.
I suppose your toolkit has some stoopid menu or buttons someplace that will allow you to test for exactly the same thing. Now all you need to do is stop posting here and read a little bit.
good luck

bftb0 said:
Now all you need to do is stop posting here and read a little bit.
good luck
Click to expand...
Click to collapse
well i did read quite a lot today :crying: i cant find my device when i type in adb devices, im pretty sure i have the right drivers installed since i followed the instructions step by step.
this guy seems to have the same problem: http://forum.xda-developers.com/showthread.php?t=1808076
could someone tell me if this could be a possible solution :http://stackoverflow.com/questions/...e-over-usb-via-adb-devices-from-windows-7-x64
also would it be possible to just get into the bootloader (since thats the purpose of adb drivers and i can do this) and just proceed with fastboot commands ? if i type in fastboot devices the tablet will show up...

In your first post, you indicated that you couldn't connect to the tablet that was in bootloader mode with adb.
And then you were told - once vaguely and once quite specifically - that *nobody* can communicate with the tablet using adb when the tablet is in bootloader/fastboot mode.
As stated previously, use the "fastboot" program when the tablet is in bootloader mode, and use the "adb" program when the tablet is booted to the custom recovery (or the regular android boot if USB debugging has been enabled).
You can use either one of these modes to effect a rescue so long as they are working correctly - they don't need to both be working. Eventually you would want that to be the case, but for the moment why don't you just stick with what is working for you.
If you get a device ID printed when you execute "fastboot devices" when the tablet is in boot loader/fastboot mode, that is all you need to reinstall a factory ROM, using nothing but fastboot.

thx for pointing me in the right direction! so i started flashing with the fastboot commands... as soon i get to: fastboot flash radio radio-tilapia-1231_0.17.0_1025.img
i receive:
error: cannot load 'radio-tilapia-1231_0.17.0_1025.img': No error
any clues? thx in advance
edit:using 4.2.2 factory rom for nexus 7 3g

oads said:
thx for pointing me in the right direction! so i started flashing with the fastboot commands... as soon i get to: fastboot flash radio radio-tilapia-1231_0.17.0_1025.img
i receive:
error: cannot load 'radio-tilapia-1231_0.17.0_1025.img': No error
any clues? thx in advance
edit:using 4.2.2 factory rom for nexus 7 3g
Click to expand...
Click to collapse
Well, I can't see what instructions you are following, and there is a possibility of sensitivity to an exact sequence. In particular, is a
fastboot reboot-bootloader
performed after the bootloader is flashed, but before the radio is flashed? It might be important that you are performing the radio flash from one bootloader vs. the other. Just a guess. (Along the same lines, do you see something unexpected happening, such as a boot to the recovery after the radio flash command?)
There are some other threads on this I think. (I have a grouper device not tilapia) But I thought that those threads were about problems with radio flashing when a custom recovery (rather than a stock recovery) was on the phone, but that was for applying the OTA package for tilapia rather than flashing directly from fastboot.
-------------------------------------------------------
[Edit] whoops, wait a minute.... "cannot load"
When you run fastboot from the command line, the file names you give are relative to the current directory. Did you move those image files into the same directory that you are executing the "fastboot" command from?
Alternately you can specify the full pathname to wherever you unpacked the files, for instance
fastboot flash radio C:\myfolder\unpacked\googlen7\4.2.2\radio-tilapia-1231_0.17.0_1025.img

hi! basically im following this guide http://forum.xda-developers.com/showthread.php?t=1907796!
GSM/HSPA+ devices (nakasig)
Code:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader bootloader-tilapia-4.18.img
> fastboot reboot-bootloader
> fastboot flash radio radio-tilapia-1231_0.17.0_1025.img
> fastboot reboot-bootloader
> fastboot -w update image-nakasig-jdq39.zip
its all good till i want to flash the radio. The .img is in the correct folder, just tried it again... could it be broken? should i try a other factory update like 4.2.1?

oads said:
hi! basically im following this guide http://forum.xda-developers.com/showthread.php?t=1907796!
GSM/HSPA+ devices (nakasig)
Code:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader bootloader-tilapia-4.18.img
> fastboot reboot-bootloader
> fastboot flash radio radio-tilapia-1231_0.17.0_1025.img
> fastboot reboot-bootloader
> fastboot -w update image-nakasig-jdq39.zip
its all good till i want to flash the radio. The .img is in the correct folder, just tried it again... could it be broken? should i try a other factory update like 4.2.1?
Click to expand...
Click to collapse
I would complete the rest of the steps first and see if everything is still working. Your device *should* still work just fine with an old radio firmware. (Boot it up and see what radio firmware the OS reports on the Settings... about device... status page).
I'll pull down the tilapia image and tell you what MD5 I observe for the radio image.

just to verify, you actually have the 3g/4g model? or just the wifi only model. if wifi only, there is no radio

Pirateghost said:
just to verify, you actually have the 3g/4g model? or just the wifi only model. if wifi only, there is no radio
Click to expand...
Click to collapse
yes

SHA1
0798439d363beb145d9223a42ed9edf3de1a30f4 nakasig-jdq39-factory-0798439d.tgz
bb824d449f44d2ad43c5d2a463fe1244d2faf525 nakasig-jdq39/radio-tilapia-1231_0.17.0_1205.img
f406ae9133c56200306d5c7d64d151f21e0be3c4 nakasig-jdq39/image-nakasig-jdq39.zip
MD5
ee8db1ed6ff1c007fe12136d4bc65cd8 nakasig-jdq39-factory-0798439d.tgz
276cb738e5b9e18a088b6a3eef8155ad nakasig-jdq39/radio-tilapia-1231_0.17.0_1205.img
4cfa996b6513a7fa53db7cbfd1134396 nakasig-jdq39/image-nakasig-jdq39.zip
radio image is 16,777,216 bytes long
---------- Post added at 05:43 PM ---------- Previous post was at 05:40 PM ----------
the google - provided instructions (flash-all.sh) have 10 second sleeps after the bootloader resets - are you waiting long enough?
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-tilapia-4.18.img
fastboot reboot-bootloader
sleep 10
fastboot flash radio radio-tilapia-1231_0.17.0_1205.img
fastboot reboot-bootloader
sleep 10
Also - something to check since you are rebooting the bootloader - does the device show up correctly in the Windows device manager? (Sometimes with soft reboots I have found the need to pull the USB cable and plug it back in to the PC).

Kindle Fire HD (3rd Generation) Bootloader Unlock and TWRP

Code:
#include <std/disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will amputate it with
* a piece of rusty metal. Unless it kills your cat, in which case I shall apologise
* for your loss.
*/
This is for the 2013 Kindle Fire HD (3rd Generation) "soho" or KFSOWI. Please follow the instructions below very carefully. These instructions WILL change, ensure you keep up to date.
First, download and extract the attachment (exploit.zip) into a folder. Then you need to download Fire OS 4.5.5.1 and SuperSU into that folder. Check the MD5 sums!
Although not recommended, if your Fire is rooted, you can enter fastboot mode without a fastboot cable. Using a fastboot cable covers you against most cases of bricking your device. Not using one increases the likelihood.
To use this totally unsupported, unsafe method of accessing fastboot mode, run
Code:
adb shell su -c "dd if=/dev/zero of=/dev/block/platform/omap_hsmmc.1/by-name/boot bs=1 count=1 seek=848"
adb reboot
Make sure you have the latest version of adb and fastboot and that you have installed drivers for the Fire (if you run an inferior operating system). Boot into Fire OS and ensure you have a good charge on the device. Connect the device with a fastboot cable and enter fastboot mode.
Run
Code:
fastboot -i 0x1949 oem format
fastboot -i 0x1949 flash boot hijack.img
fastboot -i 0x1949 flash system system.img
fastboot -i 0x1949 continue
Now wait for the Amazon logo with the orange underline and run
Code:
fastboot -i 0x1949 flash boot recovery.img
fastboot -i 0x1949 oem format
fastboot -i 0x1949 continue
Now wait for TWRP to load up and go into Advanced -> ADB Sideload and tick the two boxes (Wipe Dalvik Cache and Wipe Cache) then swipe the slider (Swipe to Start Sideload). Return to your terminal and run (changing the filename, if necessary)
Code:
adb sideload [B]update-kindle-11.4.5.5_user_455002120.bin[/B]
Now wait for TWRP to finish flashing and press Back then go into ADB Sideload and swipe the slider (Swipe to Start Sideload). Return to your terminal and run (changing the filename, if necessary)
Code:
adb sideload [B]UPDATE-SuperSU-v2.46.zip[/B]
If you want to, you can download the Google Apps and flash them in a similar manner. Google Apps will cause issues with Fire OS if you perform a factory reset! You have been warned.
Now wait for TWRP to finish flashing, remove the fastboot cable and press Reboot System. When the device has booted, reinsert the cable and run
Code:
adb push recovery.img /sdcard/recovery.img
adb shell su -c "dd if=/sdcard/recovery.img of=/dev/block/platform/omap_hsmmc.1/by-name/recovery"
adb push exploit.img /sdcard/exploit.img
adb shell su -c "dd if=/sdcard/exploit.img of=/dev/block/platform/omap_hsmmc.1/by-name/exploit"
adb shell rm /sdcard/recovery.img /sdcard/exploit.img
To boot into recovery, power off the device and hold the volume button [ - ] then push the power button (you may need to do this more than once). When the Amazon logo appears, release the volume button.
Please could any testers report back with results, and which model they have (pictures of it running TWRP would be nice). If you have any problems, also include your entire terminal session and any errors TWRP gives when flashing. You shan't recieve help otherwise. If you are inexperienced, please wait for other testers to try this method.
Please refrain from mirroring any of the files, just link back to this post.
ROM Developers: you need to add boot.img from the files to the beginning of your ROM's boot.img
XDA:DevDB Information
Kindle Fire HD (3rd Generation) Bootloader Unlock and TWRP, Tool/Utility for the Amazon 7" Kindle Fire HD
Contributors
spudowiar
Version Information
Status: Alpha
Created 2015-12-13
Last Updated 2016-01-01

Reserved

Reserved

Reserved

nice work
To be clear this is for:
[Kindle Fire HD] 3rd Gen/2013
Codename: soho
Model # KFSOWI

sd_shadow said:
nice work
[Kindle Fire HD] 3rd Gen/2013
Codename: soho
Model # KFSOWI
Click to expand...
Click to collapse
I'll start on TWRP soon then I'll post a full unlocking tutorial

Many happy people in soho-land today--thanks!

sd_shadow said:
nice work
To be clear this is for:
[Kindle Fire HD] 3rd Gen/2013
Codename: soho
Model # KFSOWI
Click to expand...
Click to collapse
Yep, KFSOWI. I've tried this on my 8GB one but I'll need someone with a rooted 16GB to confirm something

spudowiar said:
Yep, KFSOWI. I've tried this on my 8GB one but I'll need someone with a rooted 16GB to confirm something
Click to expand...
Click to collapse
I can help, tell me what to do
Sent from my Mi-4c using Tapatalk

http://i.imgur.com/tuMFhAP.jpg

The unlock is released, go to the first post to find out how to install!

Test #1
This is a major accomplishment and all us hackers love you. :good:
I tested and here are some observations/suggestions.
1. Make a backup of your device before starting this exploit.
2. The command "adb reboot" does not reboot into fastboot mode even when connected with fastboot cable.
Try to disconnect fastboot cable, turn off device, and reconnect fastboot cable. Boots into fastboot ok.
Will try from scratch again.

bobcat131 said:
2. The command "adb reboot" does not reboot into fastboot mode even when connected with fastboot cable.
Click to expand...
Click to collapse
does this work?
Code:
adb reboot-bootloader
Sent from my KFFOWI using Tapatalk

Got it!
sd_shadow said:
does this work?
Code:
adb reboot-bootloader
Of course! My bad.
Click to expand...
Click to collapse

I got stucked.
Everything went well until the second oem format command. Thats just not working. I'm using ubuntu in a virtualbox on windows 7, i'll try it tomorrow from my workplace where I have a real ubuntu installation.
I have a 16G version.
the console output:
[email protected]:/home/bari/SOHO# fastboot -i 0x1949 devices
00D306073494080F fastboot
[email protected]:/home/bari/SOHO# fastboot -i 0x1949 oem format
...
OKAY [ 0.052s]
finished. total time: 0.052s
[email protected]:/home/bari/SOHO# fastboot -i 0x1949 flash boot recovery.img
target reported max download size of 1005584384 bytes
sending 'boot' (8192 KB)...
OKAY [ 1.033s]
writing 'boot'...
OKAY [ 0.583s]
finished. total time: 1.616s
[email protected]:/home/bari/SOHO# fastboot -i 0x1949 flash system system.img
target reported max download size of 1005584384 bytes
sending 'system' (6370 KB)...
OKAY [ 0.821s]
writing 'system'...
OKAY [ 0.913s]
finished. total time: 1.734s
[email protected]:/home/bari/SOHO# fastboot -i 0x1949 continue
resuming boot...
OKAY [ 0.004s]
finished. total time: 0.004s
[email protected]:/home/bari/SOHO# fastboot -i 0x1949 oem format
...
FAILED (command write failed (Broken pipe))
finished. total time: 0.002s
[email protected]:/home/bari/SOHO#
Click to expand...
Click to collapse

Test 2 failed.
All went well, until I rebooted to system from TWRP. It booted straight into language select then system settings and no navigation bar or home screen.
Stuck in system settings .
Is this just me or a bug?

bobcat131 said:
This is a major accomplishment and all us hackers love you. :good:
I tested and here are some observations/suggestions.
1. Make a backup of your device before starting this exploit.
2. The command "adb reboot" does not reboot into fastboot mode even when connected with fastboot cable.
Try to disconnect fastboot cable, turn off device, and reconnect fastboot cable. Boots into fastboot ok.
3. The adb reboot recovery command reboots into red triangle options and unable to enter recovery.
Using power button and volume button also boots into red triangle. Needs a fix.
4. Boot into system is not complete. No navigation.
5. Missed the exploit flash, so I will reset and test again.
Click to expand...
Click to collapse
Which model do you have (8GB or 16GB)? I tested these instructions from stock using my fastboot cable, YMMV.
That is probably wise but Amazon provide complete stock images of everything but the system (which can be reconstructed), cache and userdata
"adb reboot" should reboot into fastboot mode since it does a hard reboot, I did this since my fastboot cable (whilst it worked with the "otter2") only allowed one command if it had been plugged into the powered off "soho". I only have access to one fastboot cable and this worked for that one.
That means you didn't flash SuperSU or the recovery (that is the stock recovery)
Not flashing the exploit results in the recovery not booting (the screen would flash red and fastboot would load up on both of the methods you tried), you didn't flash SuperSU or the recovery (the stock recovery booted up)
Rhyn said:
I got stucked.
Everything went well until the second oem format command. Thats just not working. I'm using ubuntu in a virtualbox on windows 7, i'll try it tomorrow from my workplace where I have a real ubuntu installation.
I have a 16G version.
the console output:
Click to expand...
Click to collapse
You were too quick on that command. I wrote "arrow underline" in the instructions, I meant "orange underline". (originally I wrote "orange arrow underline" ) What happened is fastboot reinitialised but was not accepting commands. Also, VirtualBox may take a bit of time (there was a USB disconnect/reconnect). A live CD would be much easier, I avoided putting any Linux commands in here (I have a script to craft the images).
bobcat131 said:
All went well, until I rebooted to system from TWRP. It booted straight into language select then system settings and no navigation bar or home screen.
Stuck in system settings .
Is this just me or a bug?
Click to expand...
Click to collapse
As I said, I tested these instructions from stock. Did you try a factory reset? (You can do a backup in TWRP )
sd_shadow said:
does this work?
Code:
adb reboot-bootloader
Of course! My bad.
Click to expand...
Click to collapse
See above.
Anyway, this is definitely a WIP, I have access to one device and one fastboot cable. You can help iron out any bugs with this method. Thanks for trying!

Booting into TWRP might cause a TWRP bootloop (when you reboot, it boots back into TWRP instead of system). For now, only use TWRP with access to a fastboot cable (so you can go into fastboot and do fastboot -i 0x1949 continue) or you could flash /system/recovery.img to the recovery partition and reboot using the stock recovery - but don't bother!

spudowiar said:
You were too quick on that command. I wrote "arrow underline" in the instructions, I meant "orange underline". (originally I wrote "orange arrow underline" ) What happened is fastboot reinitialised but was not accepting commands. Also, VirtualBox may take a bit of time (there was a USB disconnect/reconnect). A live CD would be much easier, I avoided putting any Linux commands in here (I have a script to craft the images).
Click to expand...
Click to collapse
It was the virtualbox. On my work computer from linux it worked perfectly.
Pictures as you requested http://imgur.com/a/GVr7f

Rhyn said:
It was the virtualbox. On my work computer from linux it worked perfectly.
Pictures as you requested http://imgur.com/a/GVr7f
Click to expand...
Click to collapse
It could be a coincidence (if the first fastboot worked, it must have been VirtualBox reconnecting the USB). But still, good to see it worked

Bricked/softbricked essential device: please help

I recently got the Essential Phone and instinctively decided to mess around and flash a custom recovery. I then found out that TWRP is not compatible with the essential phone running 8.1 beta. I am now stuck in fastboot mode. However, when i enter recovery mode, it goes straight to the logo screen with powered by android underneath and nothing occurs. When I start the phone back up, it also goes to the powered by android screen and does not load up. My computer does not recognize my device through ADB. My bootloader is unlocked. Any help is much appreciated as I do not want to have a useless phone after having it for a day. Thank you
--from what i gathered, fixing the phone is a matter of flashing the stock.img, which i have downloaded. However, because my phone is unable to be recognized by adb/fastboot I am unsure how to accomplish this

nickyg101 said:
I recently got the Essential Phone and instinctively decided to mess around and flash a custom recovery. I then found out that TWRP is not compatible with the essential phone running 8.1 beta. I am now stuck in fastboot mode. However, when i enter recovery mode, it goes straight to the logo screen with powered by android underneath and nothing occurs. When I start the phone back up, it also goes to the powered by android screen and does not load up. My computer does not recognize my device through ADB. My bootloader is unlocked. Any help is much appreciated as I do not want to have a useless phone after having it for a day. Thank you
--from what i gathered, fixing the phone is a matter of flashing the stock.img, which i have downloaded. However, because my phone is unable to be recognized by adb/fastboot I am unsure how to accomplish this
Click to expand...
Click to collapse
Make sure not to use the cable that came with the phone.
Reboot the computer, try a different USB port.

tech_head said:
Make sure not to use the cable that came with the phone.
Reboot the computer, try a different USB port.
Click to expand...
Click to collapse
I am using a different cable; one i purchased separately from the phone. After rebooting computer, should i again attempt to connect via adb and fastboot and, if it connects, attempt to flash to stock? thank you very much for the quick response

nickyg101 said:
I am using a different cable; one i purchased separately from the phone. After rebooting computer, should i again attempt to connect via adb and fastboot and, if it connects, attempt to flash to stock? thank you very much for the quick response
Click to expand...
Click to collapse
after resetting my mac, it recognizes my phone in fastboot mode
- i believe now all i need to do is flash the stock image i downloaded, which im not sure how to do

nickyg101 said:
after resetting my mac, it recognizes my phone in fastboot mode
- i believe now all i need to do is flash the stock image i downloaded, which im not sure how to do
Click to expand...
Click to collapse
The stock image on essential website has fastboot script.

Joylesstuna said:
The stock image on essential website has fastboot script.
Click to expand...
Click to collapse
when i locate the file, how should i flash it as?
fastboot flash boot 'boot.img'
my phone is not recognized over adb; rather when i go to recovery i got the red triangle over the android with "no command" underneath it

update: thank you all for the help i appreciate it a lot. When i run the script that came with the download from the essential site, my phone will boot back up but the wifi does not work.
Macintosh-2:~ xxxxx$ #!/bin/bash
Macintosh-2:~ xxxxx$ fastboot flash nvdef nvdef.img
error: cannot load 'nvdef.img': No such file or directory
Macintosh-2:~ xxxxx$ fastboot flash boot boot.img
error: cannot load 'boot.img': No such file or directory
Macintosh-2:~ xxxxx$ fastboot flash system system.img
error: cannot load 'system.img': No such file or directory
Macintosh-2:~ xxxxx$ fastboot flash bluetooth bluetooth.img
error: cannot load 'bluetooth.img': No such file or directory
Macintosh-2:~ xxxxx$ fastboot flash abl abl.img
error: cannot load 'abl.img': No such file or directory
Macintosh-2:~ xxxxx$ fastboot flash dsp dsp.img
error: cannot load 'dsp.img': No such file or directory
Macintosh-2:~ xxxxx$ fastboot flash modem modem.img
error: cannot load 'modem.img': No such file or directory
Macintosh-2:~ xxxxx$ fastboot erase userdata
******** Did you mean to fastboot format this ext4 partition?
erasing 'userdata'...
OKAY [ 0.294s]
finished. total time: 0.294s
Macintosh-2:~ xxxxx$ fastboot reboot
rebooting...
This is what occured in terminal and then my phone subsequently booted up into the new phone setup screen. it looks like the problem is that its not flashing any of the required modules and is only erasing my phone?

i was able to flash each however it just keeps rebooting to the fastboot screen :/

nickyg101 said:
i was able to flash each however it just keeps rebooting to the fastboot screen :/
Click to expand...
Click to collapse
Which firmware are you trying to flash?
Are you using one of the back to stock ROM images?
That is what you should use.
Open the script and use the commands line by line in a terminal.
If you are using a Mac it is a good idea to reboot before you start flashing.
If you have used ads or fast boot, it can sometimes get into a state where it won't see the device.
My Mac (native USB-C) will often crash when trying to flash the system image.

Yes I am attempting to flash back to stock. I got the zip from the essential site https://www.essential.com/developer/current-builds
and this is what the package looks like

nickyg101 said:
Yes I am attempting to flash back to stock. I got the zip from the essential site https://www.essential.com/developer/current-builds
and this is what the package looks like
Click to expand...
Click to collapse
I would look here and flash one this post.
https://forum.xda-developers.com/showpost.php?p=74437484&postcount=1

Every time i try flashing the stock stuff back on to the device, it boots right into bootloader (my bootloader is unlocked) no matter what. Is there a way around this or do you know why this would occur?

tech_head said:
I would look here and flash one this post.
https://forum.xda-developers.com/showpost.php?p=74437484&postcount=1
Click to expand...
Click to collapse
I flashed the april version of oreo and it flashes everything but then still always just boots right into fastboot mode. thank you for your continued help

You need to use the command fastboot flashing unlock_critical
Then use the back to stock firmware from this thread
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681/page48
That should set you write and don't forget to fastboot -w as well just to make sure

We got it back to stock Thanks everyone. It was a small thing I was missing on my end

Also when going into recovery, when you get to the "no command" screen you to press a key combo to enter recovery mode. I think it was power then volume up. It's always like that even in a fully functional device.

Would you mind posting how you fixed it and what was wrong? This is how we learn!