Database Users

Please help me install the recovery image on my rooted Nexus one!

Hi all,
I am completely at my wits end here and just don't know what to do
I have successfully unlocked my stock Nexus One boatloader, and have installed superboot to root it.
- I am using Windows 7 64 bit with all USB drivers for the nexus one correctly installed
- I have remembered to reset debuggingt mode in the Nexus USB settings
- Rooted apps seem to be working fine - I've just been playing with the LED torch app and I have a 'Superuser Permission' icon in my programs list
I am attempting to install the Amon_Ra recovery file - I've tried two different versions of it with no joy so far.... 1.7.0 and 1.6.2
I am able to boot into fastboot (with the skateboarding droids) with no probs. I can see the device using fastboot devices. However, when I try to send any recovery image using fastboot, it just hangs there with an empty progress bar on the right hand side of the screen in green that doesn't fill up.... Here is the terminal output:
---
C:\AndroidSDK\android-sdk-windows\tools>fastboot devices
HT9C(-REMOVED-) fastboot
C:\AndroidSDK\android-sdk-windows\tools>fastboot flash recovery recovery.img
sending 'recovery' (3948 KB)...
---
Anybody have any idea why it hangs here and if there is anything else I can do to maybe figure out why? I'm pretty certain I've almost cracked it - installing this recovery image is a problem
Thanks in advance!
Gil

don't rename the recovery.img file.
Then if that still doesn't work...maybe try using a terminal on your phone. Not sure myself which terminal app works.

SiNJiN76 said:
don't rename the recovery.img file.
Then if that still doesn't work...maybe try using a terminal on your phone. Not sure myself which terminal app works.
Click to expand...
Click to collapse
Thanks for the quick response!
It still fails even when I don't rename the recovery image.
Re 'using a terminal on my phone' - is there a guide to this anywhere? Do I download a shell or something?
TIA!
Gil

Go to market and search Android Terminal Emulator.
Then follow these instructions:
via terminal app
Code:
Copy recovery-RA-nexus-v1.7.0.img to the root of your sdcard
start the terminal app
su(press enter)
flash_image recovery /sdcard/recovery-RA-nexus-v1.7.0.img(press enter)
reboot recovery(press enter)
Got those instructions from the Recovery thread.

It looks like fastboot is not properly detecting your device? Also, did you install "superroot" before attempting to flash recovery image?

Thanks everyone for the help so far.
SiNJiN76 said:
Go to market and search Android Terminal Emulator.
Then follow these instructions:
via terminal app
Code:
Copy recovery-RA-nexus-v1.7.0.img to the root of your sdcard
start the terminal app
su(press enter)
flash_image recovery /sdcard/recovery-RA-nexus-v1.7.0.img(press enter)
reboot recovery(press enter)
Got those instructions from the Recovery thread.
Click to expand...
Click to collapse
I have tried these steps - when I issue the su command, I get root and a dialog box prompting me to allow it. However, when I type the flash_image command, I get the following message:
flash_image: not found
How is it that I don't have the flash_image command on my Nexus?!
aoch88 said:
It looks like fastboot is not properly detecting your device? Also, did you install "superroot" before attempting to flash recovery image?
Click to expand...
Click to collapse
I think fastboot is detecting my device, because I managed to display the serial number (I obsficated most of the output above for security reasons) and I also successfully unlocked the bootloader. After I unlocked the bootloader, I tried to copy over the recovery image, and it just hung, so I then went and installed Modaco's superboot version ERD27 with himem enabled. This allowed me root access but still will not allow me to flash with the recovery image.
In addition, I have noticed that since I installed superboot himem, I am having a couple of network issues. Firstly - my 3G signal has now dropped from virtually full strength all the time to now never more than 50% strength, and frequently gives network errors when accessing the android store. It has also said "emergency calls only" a couple of times and probably worst of all (!) no longer checks my gmail automatically (I have plenty of emails but don't get notified - texts work fine though and my contacts are all still there and my account seems to be linked) - could the superboot have affected this in any way?
Thanks all for your help - I'm getting a little worried I may have totally borked my phone now
Gil

A little extra info if it helps anyone - I just tried to erase the recovery image in fastboot to see if I could then write a new recovery image. Here is the output:
---
C:\AndroidSDK\android-sdk-windows\tools>fastboot devices
HT9CXP8##### fastboot
C:\AndroidSDK\android-sdk-windows\tools>fastboot erase recovery
erasing 'recovery'... FAILED (remote: not allowed)
---
Anybody have any clue what this means?

Try to redownload the recovery image, maybe you got a bad download.

thisisgil said:
when I try to send any recovery image using fastboot, it just hangs there with an empty progress bar on the right hand side of the screen in green that doesn't fill up....
Click to expand...
Click to collapse
Can you try a different USB port? I found when flashing mine that it didn't like USB1.1 only worked on USB2.0

thisisgil said:
A little extra info if it helps anyone - I just tried to erase the recovery image in fastboot to see if I could then write a new recovery image. Here is the output:
---
C:\AndroidSDK\android-sdk-windows\tools>fastboot devices
HT9CXP8##### fastboot
C:\AndroidSDK\android-sdk-windows\tools>fastboot erase recovery
erasing 'recovery'... FAILED (remote: not allowed)
---
Anybody have any clue what this means?
Click to expand...
Click to collapse
Another thing I discovered recently: Never use a port on a USB hub. Always use a USB port on the PC directly. I was having trouble flashing ROMs on my Acer Liquid and they went away when I stopped using a port on the hub.

without a doubt i bet its a naming issue, this is one of those things that go unmentioned and overlooked. either u do or dont have file extensions showing or not and or the .img does or does not need to be changed to .zip, i messed with this for days last year when flashing my g1. just go and change whatever you hide/show known file extensions is set to and see if ur problem is solved.
Sent from my Nexus One using the XDA mobile application powered by Tapatalk

AndyBurns said:
Can you try a different USB port? I found when flashing mine that it didn't like USB1.1 only worked on USB2.0
Click to expand...
Click to collapse
Thank you AndyBurns. I registered just to say that. You saved me a lot of time.
I had the same problem. Had the USB cable plugged into my front 1.1 ports instead of the back 2.0 ports. Switch ports and now I'm good to go.
Thank you.

Hi all -
Just wanted to post a follow up to this message, in the hope that it may help someone in the future!
Basically, I was not using the original USB cable that came with the nexus one (lost it), and instead was using a cable that I bought from a mobile phone retailer - it was basically one of those 6-in-1 multi USB cables where I had to put an adaptor on the end to switch it from mini to micro USB to fit the Nexus one.
Anyhow, for some reason, despite the fact that I could charge the phone using this new cable, and access it through device manager, explore the contents of the phone, root it etc etc, it would not do the flash as described above. I went out and bought a dedicated 1 metre gold plated micro USB cable, and it worked great
Dodgy cables - should have thought of this before I spent days frigging around and maybe even almost bricking the phone with a bad flash

How to Unbrick (Stuck at Boot Animation) Kindle Fire on a Mac..?

*disclaimer: I am posting here because for all of my searching, I don't see help for unbricking on a Mac when you're already rooted...
********UPDATE: I SOLVED THE ISSUE! I WILL POST A HOW-TO FOR MAC USERS VERY SOON!********
My problem:
I can't use the usual steps in this forum to get past the boot animation because I can't see my device on my Mac anymore since this whole boot loop started. How do I get into adb if my kindle is in boot limbo..?
Note: My Kindle is rooted, I have adb on my Mac and everything was fine until I updated my GoEx Launcher. Help!
Thanks in advance, and I'll donate/buy beers for whoever can help!!!

Am I seriously the only one in this forum who uses a Mac to access adb??

I heard issues, so I dual booted into windows to run the commands.
Sent from my HTC Glacier using xda premium

smirkis said:
I heard issues, so I dual booted into windows to run the commands.
Click to expand...
Click to collapse
Ok. I guess I'm just gonna have to bite the bullet and find a PC. Still, I don't understand how being on a PC or a Mac will make a difference if the kindle is stuck at the boot animation, how will the PC ever get to communicate with it..? I'm mean if it's looping then it never gets to initialize enough for adb to access it... right?

Ok, so for some unexplainable reason, I got my iMac to recognize that my kindle is attached (unlike my Macbook, which never sees it while it's boot looping). Yes, I am still in boot loop though. I think my problem is I never make it into fastboot mode.
When I am in adb, I can see that my kindle is rooted (the permissions pop up in the Terminal) but when I get to the fastboot part, it always returns "permission denied" for any command I enter.
If I've gotten this kindle to talk to adb via Terminal (on Mac) while it's in boot loop mode, there HAS to be a way to push it even further and get it to wipe the system and back to stock... right?
Help!!!!

***UPDATE***
I've somehow gotten into fastboot mode (i think) because the logo is no longer flashing. But of course now that it's in fastboot, Terminal says:
error: device not found
I downloaded fastboot.exe (but what folder should it be in???) and run the fastboot commands, starting with: cd /system/bin
...but it just says: No such file or directory
I feel like I'm really close here lol.. someone, throw me a bone!

im not really familure with macs I know that it is unix based but how do the drivers work? is it like PC or more like linux?

***UPDATE***
PROGRESS!!!
I was able to enter the fastboot commands to erase user data, told it to boot into bootmode 4000, and then I entered the command to reboot...
...that's where it ends. lol
Apparently the Terminal is stuck at: "rebooting..."
I'm gonna stare at it as long as I can, hopefully it reboots because if it does, I can post a new thread for all the Mac users who got stuck like me...
**cross your fingers!***

wtphoto said:
im not really familure with macs I know that it is unix based but how do the drivers work? is it like PC or more like linux?
Click to expand...
Click to collapse
...more like Linux!

OMG OMG OMG OMG!!!! I DID IT!!!!
LOL AWESOME!!!!!!!!!!!!!!!!
Ok! So I'm gonna post my steps for Mac users.. unfortunately, not tonight because I'll be up trying to get CM7 on this bad boy! lol
...and yeah, I know what you're sayin. 'Why hack it some more after you just got it back up and running?!"
Well, that's the life of a geek lol. Not to mention that now I know how to get it back if I crash it again, so.. yeah. Here's to being a geek baby!
Thanks for NOT helping guys... I guess trial and error IS the best teacher!

I know when I was having an issue getting fastboot to recognize I had to add 51-android.rules to my /etc/udev/rules.d directory
**edit** NM looks like you got it, sorry I came in late

wtphoto said:
I know when I was having an issue getting fastboot to recognize I had to add 51-android.rules to my /etc/udev/rules.d directory
**edit** NM looks like you got it, sorry I came in late
Click to expand...
Click to collapse
Hey, thanks! Yeah I already had it in the bag by the time you posted, but thanks for trying to help...
I am in the process of organizing a new post with the steps I went through to get unbricked on my mac. I will be posting soon!

webmastertroi said:
Hey, thanks! Yeah I already had it in the bag by the time you posted, but thanks for trying to help...
I am in the process of organizing a new post with the steps I went through to get unbricked on my mac. I will be posting soon!
Click to expand...
Click to collapse
Thanks so much man!!!!! <3 you (no homo) ur a life saver!!!! can't wait for this guide epic thanks to you!

LOL!!! Glad to know someone else can use it! I have been busy working and now I'm in airport to fly out for the holidays, but I'm working to post it hopefully tomorrow or Friday... I'm on it!
Sent from my Kindle Fire using xda premium

Well, I'm now in the same boat and also on a mac...stuck at boot and can't seem to get it to be recognized by adb... If someone could post the steps, I'd be very grateful...

bikeracer4487 said:
Well, I'm now in the same boat and also on a mac...stuck at boot and can't seem to get it to be recognized by adb... If someone could post the steps, I'd be very grateful...
Click to expand...
Click to collapse
I apologize for the wait. I'm traveling for the holiday and simply haven't had the time. I will try to work on it asap. It's a pretty lengthy post with a lot of steps and I will have to organize it all lol. I will soon though...
Merry Christmas in the meantime..

Here is the fix that should work on Windows/Mac/Linux:
1. first have your kindle plugged in and off
2. in the command prompt, browse to the android platform tools, where fastboot is.
3. type in fastboot -i 0x1949 oem idme bootmode 4000
4. It should show < waiting for device >
5. Turn on your Kindle
If its still sitting at the yellow triangle, then type fastboot -i 0x1949 reboot

lchanmanl said:
Here is the fix that should work on Windows/Mac/Linux:
1. first have your kindle plugged in and off
2. in the command prompt, browse to the android platform tools, where fastboot is.
3. type in fastboot -i 0x1949 oem idme bootmode 4000
4. It should show < waiting for device >
5. Turn on your Kindle
If its still sitting at the yellow triangle, then type fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
HOLY CRAP!! That just fixed my kindle that has been bricked for 2 weeks. THANKS!

HELP!
Troi:
I am in the same boat as you. Can you post the steps you used to unbrick your Fire on a Mac?
Thanks,
David

lchanmanl said:
Here is the fix that should work on Windows/Mac/Linux:
1. first have your kindle plugged in and off
2. in the command prompt, browse to the android platform tools, where fastboot is.
3. type in fastboot -i 0x1949 oem idme bootmode 4000
4. It should show < waiting for device >
5. Turn on your Kindle
If its still sitting at the yellow triangle, then type fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
I'm still stuck at the triangle after step 5. So I tried the fastboot -i 0x1949 reboot and I get this message
ERROR: usb_read failed with status e00002ed
any thoughts?
EDIT: the error now says
ERROR: could not get pipe properties

Unlocked but can't root/install CWM

I used the toolkit for mac and it unlocked me, but when it came to the next steps it said device not found and then told me to highlight recovery and press start, when I do I get the android with the red ! symbol.
Can someone help me?

That symbol is a security feature within the stock recovery, volume up and power to access the stock recovery.
Sent from my Nexus 4 using Tapatalk 4

I tried that it's not working I press up then power the phone reboots and the red ! symbol shows up...
I searched and saw hold power and press up when I see the red ! but it just reboots the phone...
help please?
Sent from my GT-N5110 using Tapatalk 4

ADB wont work in stock recovery
roguedroid said:
I tried that it's not working I press up then power the phone reboots and the red ! symbol shows up...do you know the adb instructions on how to push supersymmetric and cwm?
edit my adb now won't recognize my phone even though it did a few mins ago...
I'm frustrated, been trying to access the stock recovery for the past several mins and simply can't.
help please?
Sent from my GT-N5110 using Tapatalk 4
Click to expand...
Click to collapse
For me also Stock recovery never worked. Just try to flash CWM or TWRP.
Btw, What toolkit did you use and how did you install the drivers. Please answer these, so that someone can help you better.(Or is it just the 'mac toolkit' ?)
My suggestion: PLZ DO NOT USE TOOLKIT. If you are stuck at some point while using the toolkit, then you'll not know what went wrong and how you can correct it. Do it manually. It is the most hassle-free method. Trust me.
I think that ADB will not work in stock recovery(may be you can boot normally into your phone and then try adb). The thing which you are looking for is 'fastboot'.
1) Restart ur phone (Power Button + Volume Down, i guess) and land in the bootloader and connect your phone to PC.
2) In CMD prompt(or Terminal), type 'fastboot devices'. If your device gets listed here, then fastboot is working and drivers are properly installed. If not, then drivers are not properly installed in your PC. You need both ADB and FASTBOOT drivers. Install them properly.
PS: For MAC, i think the command is slightly different. Something like './fastboot devices' . Please look for the same in this forum or just google it and find out.
3) Follow this guide for flashing CWM and Rooting.
http://forum.xda-developers.com/showthread.php?t=2266654
4) For properly installing the Drivers, read " A. Install the drivers " in the below thread (actually you can read the entire thread )
http://forum.xda-developers.com/showthread.php?t=2010312&highlight=cwm+6+0+3+5
My knowledge is limited to Windows PC, sorry if I am not of much help. Thanks !

badhri said:
For me also Stock recovery never worked. Just try to flash CWM or TWRP.
Btw, What toolkit did you use and how did you install the drivers. Please answer these, so that someone can help you better.(Or is it just the 'mac toolkit' ?)
My suggestion: PLZ DO NOT USE TOOLKIT. If you are stuck at some point while using the toolkit, then you'll not know what went wrong and how you can correct it. Do it manually. It is the most hassle-free method. Trust me.
I think that ADB will not work in stock recovery(may be you can boot normally into your phone and then try adb). The thing which you are looking for is 'fastboot'.
1) Restart ur phone (Power Button + Volume Down, i guess) and land in the bootloader and connect your phone to PC.
2) In CMD prompt(or Terminal), type 'fastboot devices'. If your device gets listed here, then fastboot is working and drivers are properly installed. If not, then drivers are not properly installed in your PC. You need both ADB and FASTBOOT drivers. Install them properly.
PS: For MAC, i think the command is slightly different. Something like './fastboot devices' . Please look for the same in this forum or just google it and find out.
3) Follow this guide for flashing CWM and Rooting.
http://forum.xda-developers.com/showthread.php?t=2266654
4) For properly installing the Drivers, read " A. Install the drivers " in the below thread (actually you can read the entire thread )
http://forum.xda-developers.com/showthread.php?t=2010312&highlight=cwm+6+0+3+5
My knowledge is limited to Windows PC, sorry if I am not of much help. Thanks !
Click to expand...
Click to collapse
I used the nexus 4 Mac rootkit I found in here.
It unlocked my phone fine. But when it came to installing a recovery and root it didn't.
Neither my adb or fastboot are working now before I unlocked and I messed around and they worked now nada ...
I went to YouTube saw my problem tried pressing volume up and power like in the video and it just gives me a black screen and either turns the phone off or reboots it normally...not sure if in supposed to hold power and let go of volume or vice versa.
I placed all the files on the storage I just need to access stock recovery which I strangely cannot now...
Tried framearoot and got nowhere.
Very frustrating
Sent from my GT-N5110 using Tapatalk 4

Sort out the drivers and adb,fastboot
roguedroid said:
I used the nexus 4 Mac rootkit I found in here.
It unlocked my phone fine. But when it came to installing a recovery and root it didn't.
Neither my adb or fastboot are working now before I unlocked and I messed around and they worked now nada ...
I went to YouTube saw my problem tried pressing volume up and power like in the video and it just gives me a black screen and either turns the phone off or reboots it normally...not sure if in supposed to hold power and let go of volume or vice versa.
I placed all the files on the storage I just need to access stock recovery which I strangely cannot now...
Tried framearoot and got nowhere.
Very frustrating
Sent from my GT-N5110 using Tapatalk 4
Click to expand...
Click to collapse
Just as I mentioned, i also had the same problem with stock recovery. So I simply flashed a Custom one(CWM, in my case)
Get the ADB and FASTBOOT working and that'll solve your recovery problem. Try fiddling with your drivers again. Not sure how to do that in MAC. If FASTBOOT is working, the you can boot into a Custom Recovery(you need not even flash it) and perform whatever you need to.
fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
Again, look at the efrant's guide i referred above; i took this from there only.Remember to replace 'customrecovery.img', with the actual downloaded custom recovery image name.
Or you can try posting your problem with the toolkit, in mac toolkit's thread.

I have been youtubing everything and finally got to
Reboot system
apply update from adb
wipe data/factory reset
wipe cache partition.
I now can get adb working so I tried ./adb sideload cwm from my desktop and it is giving me signature verification failed. installation aborted.
What can I do to resolve this?
I searched xda and no one can solve this issue from the threads I've read.

I fixed it! Whooohoooo! Installed cwm and root ....now to install pa rom.
Thanks for the help!
Sent from my GT-N5110 using Tapatalk 4

Fastboot discussion.

I have searched and couldn't find a fastboot thread. So here it is.
I found out fastboot is working on Linux.
Bad news is Windows seems to need another driver for fastboot.
Please help look for a windows driver or make one.
The fastboot commands all seem to work fine.
Here you guys go! Enjoy.
Code:
[SIZE=5][SIZE=3][SIZE=5][SIZE=3]adb reboot-bootloader
fastboot -i 0x1949 command_here[/SIZE][/SIZE][/SIZE][/SIZE]
Just noticed pokey9000 said this but it was overlooked.
pokey9000 said:
That's it. And you're running fastboot as "fastboot -i 0x1949 your_command_here", and you have udev set to allow permissions for that VID (or are running as root) in Linux?
Click to expand...
Click to collapse
Thank you.
Still don't believe me, look at the last picture.
I'm having issues with some commands. Please test it out and enjoy!

shimp208 said:
In the Fire TV section a fastboot cable was created by splicing two USB A to B cables together, so that the A to A ends were together which when connected from your computer to the Fire TV on bootup put the device in fastboot mode, in the process then your computer recognized (Running Windows 8 was the example given) the device and installed the proper drivers. Since the devices are similar, a potential solution would be use the cable, have the computer recognize it and install the drivers, then backup the drivers, and share them here for others to use.
Click to expand...
Click to collapse
I'm quite sure the cable isn't the issue. Also that's just it, I can't get windows to recognize it or find much info about it. The adb driver for the device isn't enough I guess. The funny thing is windows says it's working properly as 'Kindle' for a little while when you plug it in (while in bootloader) then device manager refreshes and reports 'cannot start'. I tried launching 'fastboot devices' many times but still nothing. I think it needs a software fix and not a hardware one but I have no past experience using fastboot. So... noob alert.
btw the driver windows tries to use is ms_comp_mtp(Generic driver installed=true) and adb uses the Amazon one on the fourm here.
DevNode status Value:
01802400
DN_HAS_PROBLEM
DN_DISABLEABLE
DN_NT_ENUMERATOR
DN_NT_DRIVER
Also Bus reported device description Value:
fastboot
VID=1949 & PID=000C
(0x1949 && 0x000c)
Current Driver files:
\system32\DRIVERS\UMDF\WpdMtpDr.dll
\system32\DRIVERS\winusb.sys
\system32\DRIVERS\WUDFRd.sys
\system32\WpdMtp.dll
\system32\WpdMtpUS.dll
We need someone good on this.

I have a problem

I don't think there's ever been a question of getting into fastboot mode by using the adb reboot-bootloader command.
The issue is how to enter fastboot if the device is semi-bricked.
The device has source in the original bootloader to boot into fastboot mode if both volume buttons are pressed while powering on the device. But this has since been altered and now will only work if the device is unlocked.

Hashcode said:
I don't think there's ever been a question of getting into fastboot mode by using the adb reboot-bootloader command.
The issue is how to enter fastboot if the device is semi-bricked.
The device has source in the original bootloader to boot into fastboot mode if both volume buttons are pressed while powering on the device. But this has since been altered and now will only work if the device is unlocked.
Click to expand...
Click to collapse
Is flashing the stock .bin file any different than doing a factory reset?
I am bricked, have root, have adb, can get fastboot using adb reboot-bootloader in windows 8. I also have a Linux box if necessary.

saphi95 said:
I have a problem
Click to expand...
Click to collapse
I would recommend taking a look at this thread here, specifically the "Fixing No Permissions Error" section which should allow you to fix the problem your encountering.

dcoig1 said:
Is flashing the stock .bin file any different than doing a factory reset?
I am bricked, have root, have adb, can get fastboot using adb reboot-bootloader in windows 8. I also have a Linux box if necessary.
Click to expand...
Click to collapse
Fastboot works with win8? Not with win7.1 If you have fastboot working with win8 please go to device manager (when your in the bootloader) click properties on the device then look for what driver it uses.
Hashcode said:
I don't think there's ever been a question of getting into fastboot mode by using the adb reboot-bootloader command.
The issue is how to enter fastboot if the device is semi-bricked.
The device has source in the original bootloader to boot into fastboot mode if both volume buttons are pressed while powering on the device. But this has since been altered and now will only work if the device is unlocked.
Click to expand...
Click to collapse
My main reason is to get fastboot working with windows. I just can't. Linux seems to work with fastboot but I can't access it via windows.

Just uninstall the kindle driver and replace it with the generic fastboot one

hello all,
i've kindle fire hdx 7" , no adb, grey screen logo then shutdown and goes to black screen.
when connected using cable, it show new devices... QHSUSB_BULK and sometime unknown devices.
press hold power button and volume up only go to recovery mode, but cannot recovery the system..
always go to grey screen logo...
sorry for my bad english language...
hope all of you, understand what i mean here
i need solution for fix the problem soon. thanks

I think all that works is reboot into fastboot mode. Windows 8 says no drivers are loaded. I tried a command (can't remember what) and it just went out to lunch so... I guess windows 8 isn't working either. Only to put the device in fastboot.

there are three oem commands:
oem device-info
oem idme
oem relock
Click to expand...
Click to collapse
but it doesn't support oem unlock so there must be another way of unlocking the bootloader, when you try some of the commands the device returns "not allowed for locked hw". Does anyone know what the "hw" is ?

hw = hardware?

MaximilianOzora said:
hello all,
i've kindle fire hdx 7" , no adb, grey screen logo then shutdown and goes to black screen.
when connected using cable, it show new devices... QHSUSB_BULK and sometime unknown devices.
press hold power button and volume up only go to recovery mode, but cannot recovery the system..
always go to grey screen logo...
sorry for my bad english language...
hope all of you, understand what i mean here
i need solution for fix the problem soon. thanks
Click to expand...
Click to collapse
Read up on this bud.

Hi,
I have a bricked kindle hdx 8.9 that stops at "Kindle Fire" boot screen. I am a newbie at these things.
Just discovered that it still respond to some adb queries. Sounds like there is still hope to recover... Could it be the bootloader is messed up? Anyway to reload an image boot file to repair?
Also "fastboot reboot-bootloader" puts it into fastboot mode...with the status "ready"....and i just dont know how to proceed. Any one can help?

uhg
Facepalm

just back a little: was rooted in April but with subsequent amazon auto updates - didn't have su status. But I was able to load apps & files, installed vpns, quite a few docs,mp4 files, etc. Not really using much of the new freedom or whatever was left of it... Nothing exciting.
Was working well until one fine sunday afternoon, just 2 weeks ago when it just simply stopped after rebooting from a previous low battery charge. Was told it could be an interrupted routine update when the battery power just fell below threshold - but thot it wouldn't have erase the previous image before the new update is effective. Or it could possibly be a deleted file that is related to the booting process as I did a bit of clean up prior to the last reboot?
In the meantime, I did some adb shell/pull to explore or extract the files, photos,etc in /sdcard & other places back to my PC just in case they were not backup by the cloud. Maybe it was not bricked...but just lost a boot file or something...

In a bad situation, have absolutely zero ADB access as my build.prop is botched (bad permissions) and I did a factory reset in hopes of recovering. There is a "fastboot cable" on amazon that says it will reboot a hdx into fastboot mode, but I'm unsure of it's legitimacy. Help?

here try
Tumbtack said:
In a bad situation, have absolutely zero ADB access as my build.prop is botched (bad permissions) and I did a factory reset in hopes of recovering. There is a "fastboot cable" on amazon that says it will reboot a hdx into fastboot mode, but I'm unsure of it's legitimacy. Help?
Click to expand...
Click to collapse
This thread.read read read http://forum.xda-developers.com/showthread.php?t=2588608

I don't quite understand. Why is a special cable required for this? What makes it any different from the standard one that comes with the device?

I don't know if this will add anything to the discussion...but I can confirm fastboot is working on Ubuntu 14.04. I am using a kindle fire HDX 7" and it detects it on devices..and most commands work. Sometimes the terminal must be closed and reopened for commands to go through..
fastboot oem unlock works..or rather it says "Okay" but I'm unable to flash anything.

I ruined my phone and i need help

Hi i need to unroot and factory reset the phone. Oneplus 2 What ive already done or tried: I started to try unrooting it through superSU but that didnt work i just waited waited and nothing hapened. so then i tried to fastboot img but just got error the device is locked even though i did enable oem unluck and usb debuging. so then i wrote in cmd: fastboot oem unlock and now the phone starts up to the op logo then restard into it again after a second D'=
Im not familiar with forums and very stressed to get my phone working so i would be very very gratefull for help.

now i cant even charge it the batery logo doesnt come up after i did fasboot oem unlock again.... rip

spacebite said:
Hi i need to unroot and factory reset the phone. Oneplus 2 What ive already done or tried: I started to try unrooting it through superSU but that didnt work i just waited waited and nothing hapened. so then i tried to fastboot img but just got error the device is locked even though i did enable oem unluck and usb debuging. so then i wrote in cmd: fastboot oem unlock and now the phone starts up to the op logo then restard into it again after a second D'=
Im not familiar with forums and very stressed to get my phone working so i would be very very gratefull for help.
Click to expand...
Click to collapse
spacebite said:
no i cant even charge it the batery logo doesnt come up after i did fasboot oem unlock again.... rip
Click to expand...
Click to collapse
Got to OnePlus support center and go in download section and download official ROM. Hold power and volume up bottons and connect it to PC. After that go in folder where adb files are located on your PC (If you don't have them, search on Google for "adb install 15 sec"). Hold left shift on your keyboard and right click your mouse in that folder on an empty space. Click something related with command window and type "fastboot devices". If you get some kind of feedback it's 2minute of work! If you don't have anything come up, try to start your device in fastboot mode again (second sentence in this post). After you got a feedback from command "fastboot devices" flash custom recovery (I suggest TWRP, Google it and download the .IMG file for your device). To flash a custom recovery type this in command line: "fastboot flash recovery IMAGE_NAME.img"
*replace IMAGE_NAME with actual image name...
After that boot in recovery by disconnecting the phone and powering off the phone. Press and hold power button and volume down buttons till blue TWRP logo appears. After that connect your device on PC and transfer your .Zip file(ROM) to internal memory of your device. You should go back to main menu of recovery and select wipe>advanced wipe, select everything BUT INTERNAL STORAGE!!!***IMPORTANT***
Then you just install ROM like you would normally do...
Press thanks it i helped! Hope I didn't missed something.
This is written in mind with that you have unlocked bootloader like you have written in your post...

x8Cooler said:
Got to OnePlus support center and go in download section and download official ROM. Hold power and volume up bottons and connect it to PC. After that go in folder where adb files are located on your PC (If you don't have them, search on Google for "adb install 15 sec"). Hold left shift on your keyboard and right click your mouse in that folder on an empty space. Click something related with command window and type "fastboot devices". If you get some kind of feedback it's 2minute of work! If you don't have anything come up, try to start your device in fastboot mode again (second sentence in this post). After you got a feedback from command "fastboot devices" flash custom recovery (I suggest TWRP, Google it and download the .IMG file for your device). To flash a custom recovery type this in command line: "fastboot flash recovery IMAGE_NAME.img"
*replace IMAGE_NAME with actual image name...
After that boot in recovery by disconnecting the phone and powering off the phone. Press and hold power button and volume down buttons till blue TWRP logo appears. After that connect your device on PC and transfer your .Zip file(ROM) to internal memory of your device. You should go back to main menu of recovery and select wipe>advanced wipe, select everything BUT INTERNAL STORAGE!!!***IMPORTANT***
Then you just install ROM like you would normally do...
Press thanks it i helped! Hope I didn't missed something.
This is written in mind with that you have unlocked bootloader like you have written in your post...
Click to expand...
Click to collapse
thanks i will try when i get home

Fallow this and don't trust any guides written out of memory with likely any mistakes.. (no offense)
This guide has various approaches to recover your phone, remember to research first and don't type carelessly any adb commands, it's not enough to just tick "oem unlock" in developer options, you'd have to type command on fastboot too, to unlock the bootloader.. there are many guides and youtube tutorials on this subject, absolutely unnecessary to blindly kill it, anyways I'll never understand how you can be so reckless with your phone..
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Edit: the state you brought your phone into is called "hard bricked" - have fun..
Sent from my OnePlus2 using XDA Labs

spacebite said:
thanks i will try when i get home
Click to expand...
Click to collapse
Don't!
If you get no joy from following the instructions in the link given by @Sam Nakamura, try @fareed_xtreme's Official OP2 Stock Reset to OOS 3.0.2

Sam Nakamura said:
Fallow this and don't trust any guides written out of memory with likely any mistakes.. (no offense)
This guide has various approaches to recover your phone, remember to research first and don't type carelessly any adb commands, it's not enough to just tick "oem unlock" in developer options, you'd have to type command on fastboot too, to unlock the bootloader.. there are many guides and youtube tutorials on this subject, absolutely unnecessary to blindly kill it, anyways I'll never understand how you can be so reckless with your phone..
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Edit: the state you brought your phone into is called "hard bricked" - have fun..
Sent from my OnePlus2 using XDA Labs
Click to expand...
Click to collapse
Aight thank you i had some suspicion it might be ...-bricked didnt know which though so thank you

If you can get in the bootloader then possibly the device is still OK. Just need to get the right ROM.
Try different TWRP versions. Sometimes, one particular version can save the world.