Database Users

I think I bricked my nexus (my fault) please help!

Hello all,
I think I may have bricked my nexus one. It is completely my fault for attempting things that I knew little about, so flame away But after the flaming, if anyone is willing to help I would be sooooo thankfull...
I successfully rooted my phone following the instructions on this page: (all links edited with a double asterisk as I don't believe I can post links)
h**p://theunlockr.com/2010/01/02/how-to-root-the-nexus-one/
Then successfully installed cyanogenmod (which is awesome!) following this page:
h**p://theunlockr.com/2010/01/08/how-to-load-a-custom-rom-on-the-nexus-one/
All was well, I even got the modaco desire rom up and running, and was happily switching back and forth using the recovery screen. I had nand backups for specific setups, etc.
Then I decided it would be good to know how to go back to stock, and found this page:
h**p://**w.androidspin.com/2010/05/06/guide-unrooting-your-nexus-one-its-like-it-never-happened-almost/
I followed the instructions to the letter (I think) except for erasing userdata (it said "failed: remote not allowed"). I thought that things would be ok, since I'd recently wiped, so I followed the page till the end.
The phone rebooted, and I got the original nexus boot animation - but it's in an endless loop! What's worse, it that now when I try to go to the bootloader or recovery mode, I get the exclamation triangle with the little android.
Is there any way through a command prompt (or other method) that I can fix this? I tried to re-flash the RA recovery image through the command prompt, but the response was, "waiting for device."
ANYTHING that anyone can suggest to help, I would be so thankful! I've been loving the nexus, and hate to think that I crippled it
Thanks in advance,
Randy

I doubt its bricked.
Noticed you didnt mention that fast boot doesnt work? (power button+trackball) try it.
Once you get to fastboot you can flash any ROM back. (fastboot flash **** commands from a command shell)

Did you ever perform a Nand Backup from Recovery?

It's not bricked, the only way to brick is to interrupt power when flashing a Radio image

Connect phone to PC. Open command prompt.
adb reboot recovery
Wipe, reflash.

So far, nobody has managed to brick a Nexus. There is no way as the fastboot mode can restore the whole phone and can't be messed with. Make sure you have the latest version of the SDK with correct USB drivers and fastboot. Then try and reflash the recovery image.
-------------------------------------
Sent from my Nexus One

nexus5894 said:
So far, nobody has managed to brick a Nexus. There is no way as the fastboot mode can restore the whole phone and can't be messed with. Make sure you have the latest version of the SDK with correct USB drivers and fastboot. Then try and reflash the recovery image.
-------------------------------------
Sent from my Nexus One
Click to expand...
Click to collapse
Actually...
http://forum.xda-developers.com/showpost.php?p=6320068&postcount=404

Paul22000 said:
Actually...
http://forum.xda-developers.com/showpost.php?p=6320068&postcount=404
Click to expand...
Click to collapse
............................

It worked!!!!!
It worked!!
britoso, thank you soooooo much! The only way that I knew to get into bootloader/recovery was via power button/volume down, but power/trackball brought up the bootloader screen, and I clicked on fastboot. I was able to flash the RA recover image through the command terminal via fastboot, then able to get into recovery. I had cyan and modaco sense on the sd, and was able to flash one of them on.
​
I never thought I'd be so happy to see "quietly brilliant"!!! I WILL buy you a beer, a case in fact as soon as money clears my paypal account.
I have learned my lesson, research research research. (I did do some, but not enough to feel comfortable with what I was doing - hence my cry for help!)
Other than the phone and OS itself, the thing I like most about the nexus is the fact that one CAN root, and then customize (sold a Telus moto droid because I could not do that very thing).
I digress... thanks again so much!
And Paul, thanks for your sense ROM; I've had HTC phones from the Touch to the the diamond to the Hero, and missed the UI!

Randy Malkoski said:
It worked!!
britoso, thank you soooooo much! The only way that I knew to get into bootloader/recovery was via power button/volume down, but power/trackball brought up the bootloader screen, and I clicked on fastboot. I was able to flash the RA recover image through the command terminal via fastboot, then able to get into recovery. I had cyan and modaco sense on the sd, and was able to flash one of them on.
​
I never thought I'd be so happy to see "quietly brilliant"!!! I WILL buy you a beer, a case in fact as soon as money clears my paypal account.
I have learned my lesson, research research research. (I did do some, but not enough to feel comfortable with what I was doing - hence my cry for help!)
Other than the phone and OS itself, the thing I like most about the nexus is the fact that one CAN root, and then customize (sold a Telus moto droid because I could not do that very thing).
I digress... thanks again so much!
And Paul, thanks for your sense ROM; I've had HTC phones from the Touch to the the diamond to the Hero, and missed the UI!
Click to expand...
Click to collapse
Glad to hear it. You learn the most by trial and error.

I think i got the same problem. i tried to Unlock Bootloader and Root Google Nexus One which was successful but then i tried to superboot it and when it came to the part where you "double click the ‘install-superboot-windows.bat’ file" i clicked it but it did not go to the nnext screen where the superboot completes it just stayed at the "bootloader screen". i must hve not done something or done something wrong i dont know.
So then i unplugged the phone from the pc and rebooted it. when it reeboted i wasnt getting any network, the phone was slow and the notification bar would not slide down...also i noticed the phone restarting on itself...
/i tried all kinds of "restore to factory settings" but not solved. Can anyone tell me what to do tht will work. I coud not understand what was said in the above thread as i am new to this android n my first time rooting n stuff n i believe that solution would work for me too..if some one could please explain in simple tirms the steps i need to take would be good...
Really appreciate it....

revonomics said:
I think i got the same problem. i tried to Unlock Bootloader and Root Google Nexus One which was successful but then i tried to superboot it and when it came to the part where you "double click the ‘install-superboot-windows.bat’ file" i clicked it but it did not go to the nnext screen where the superboot completes it just stayed at the "bootloader screen". i must hve not done something or done something wrong i dont know.
So then i unplugged the phone from the pc and rebooted it. when it reeboted i wasnt getting any network, the phone was slow and the notification bar would not slide down...also i noticed the phone restarting on itself...
/i tried all kinds of "restore to factory settings" but not solved. Can anyone tell me what to do tht will work. I coud not understand what was said in the above thread as i am new to this android n my first time rooting n stuff n i believe that solution would work for me too..if some one could please explain in simple tirms the steps i need to take would be good...
Really appreciate it....
Click to expand...
Click to collapse
Tell me what i need to download again and how to go about it...i really need my phone working again ((((

[Q] New kind of unfixable Super Brick?

My kindle is bricked and I have tried everything.
This is what i did: I rooted it, installed CM7, it worked fine. I then wanted to go back to the stock rom (due to countless FCs and freezing in CM) so i flashed the stock rom through TWRP. When i re-booted, the TWRP recovery screen no longer shows and it has the stock kindle fire logo on screen.
It does not show up in device manager in windows, I have re-installed the usb drivers multiple times. Any recovery methods using ADB simply result in "waiting for device" forever.
I have tried:
hard reset
fastboot commands
booting to linux live cd with firekit
kindle fire unbrick utility
None of these work because it does connect via usb
Anyone else have this problem>?
EDIT: Im fed up, ive tried every method on XDA and youtube, nothing works. I convinced amazon to replace it. Thanks anyways.

Hi Try This http://forum.xda-developers.com/showthread.php?t=1398728

lovejoy777 said:
Hi Try This http://forum.xda-developers.com/showthread.php?t=1398728
Click to expand...
Click to collapse
If you notice, that uses ADB shell. All of these commands result in "waiting for device" as it it not detected as a USB device

Sorry forgot to attach
Ok dont worry ive gotten my self into the same issue and lots of other ones lol
I just kept on trying different things.
it will be a driver issue Ill try to find the thread that got me out of it
---------- Post added at 11:11 PM ---------- Previous post was at 11:03 PM ----------
Found it Try this.http://forum.xda-developers.com/showthread.php?t=1399889

I bricked mine last night and kept getting stuck at "waiting for device" and figured out Windows ceases to recognize it as something it has a driver for.
Windows Device Manager showed the Kindle with a yellow sign next to it. I right clicked and updated the driver but rather than detecting it at all I manually picked a device.
Don't have Windows in front of me right now but it was something like "Android Phone" for the device type and then the device was the first one listed "ADB Interface" or something starting with ADB anyway.
Once that driver was loaded I could issue ADB commands again and got it fixed.
Sent from my Kindle Fire using Tapatalk

Please do the KF rooting community a favor when you get your new kindle and stay away from rooting it. You obviosuly cant take the time to fix your own problems and would rather give amazon another reason to hate root users.

googlelover said:
Please do the KF rooting community a favor when you get your new kindle and stay away from rooting it. You obviosuly cant take the time to fix your own problems and would rather give amazon another reason to hate root users.
Click to expand...
Click to collapse
not very nice - I had same problem - stuck at boot logo.
instead of telling someone where to go maybe a fix would be better.

bg4 said:
not very nice - I had same problem - stuck at boot logo.
instead of telling someone where to go maybe a fix would be better.
Click to expand...
Click to collapse
Well considering he already convinced amazon to send him a new one its a little too late, and others have already weighed in to help, its not very nice but its the truth. If he would have just waited more than an hour for people to try and help him he would probably have been able to fix it.

Jus a quick servh would give you the answers you're looking for. It's not bricked. So relax

HaroldBawls said:
Rooting it inst the issue, trying to put a phone OS on a tablet is the issue.
Click to expand...
Click to collapse
?
Tell that to all the Nook Color users running CM7 or to Samsung, HTC and others that shipped tablets with Android 2.2 and 2.3

googlelover said:
Please do the KF rooting community a favor when you get your new kindle and stay away from rooting it. You obviosuly cant take the time to fix your own problems and would rather give amazon another reason to hate root users.
Click to expand...
Click to collapse
Troll found. Anti-Hate taser activate.
Sent from my Kindle Fire using Tapatalk

Hey, quick question. I'm having similar issues and want to just call it a day.
When you convinced Amazon to replace it, did you tell them it was rooted/modified? Also, are they shipping you a new one just like that? Or do you have to send yours back first. Thanks! A response would be very much appreciated.

i had an issue last night and spent seven hours between dos and reading forums and couldn't find the answer, but at 630 this morning i got it and retested it today again by rebricking it and fixing it and it has to be the easiest thing that i've ever done.
unplug your kindle
turn your computer off
turn off your kindle with a hard reset
turn the computer back on and plug the kindle in
turn the kindle back on
in kindle utilities hit 1 and press enter
then hit 1 and press enter
it should go to reset your kindle and say it's done and to press any button to continue but don't press anything until your kindle is back on the splash menu
it worked for me when i couldn't find anything else to do and is way to simple to not try, so i hope it helps someone else

zbhest said:
Hey, quick question. I'm having similar issues and want to just call it a day.
When you convinced Amazon to replace it, did you tell them it was rooted/modified? Also, are they shipping you a new one just like that? Or do you have to send yours back first. Thanks! A response would be very much appreciated.
Click to expand...
Click to collapse
I was on skype with him. He said he was "playing angry birds, it restarted and is stuck at the 'kindle fire logo' " they didn't ask if it was rooted, no questions asked.
Sent from my Kindle Fire using Tapatalk

mattlgroff said:
I was on skype with him. He said he was "playing angry birds, it restarted and is stuck at the 'kindle fire logo' " they didn't ask if it was rooted, no questions asked.
Sent from my Kindle Fire using Tapatalk
Click to expand...
Click to collapse
This is exactly what happened. Because it didn't have the TWRP recovery screen or anything, any average tech support person wouldnt be able to tell it had been rooted. The failure actually happened after installing the stock rom so im pretty sure if they even take the time to inspect it, they wil see an unused, unrooted stock rom on the devoce

punkboyarde said:
i had an issue last night and spent seven hours between dos and reading forums and couldn't find the answer, but at 630 this morning i got it and retested it today again by rebricking it and fixing it and it has to be the easiest thing that i've ever done.
unplug your kindle
turn your computer off
turn off your kindle with a hard reset
turn the computer back on and plug the kindle in
turn the kindle back on
in kindle utilities hit 1 and press enter
then hit 1 and press enter
it should go to reset your kindle and say it's done and to press any button to continue but don't press anything until your kindle is back on the splash menu
it worked for me when i couldn't find anything else to do and is way to simple to not try, so i hope it helps someone else
Click to expand...
Click to collapse
Thanks, but this only works if it connects over usb. Doing this results in "waiting for device" as mentioned before

Broken touch screen, need to get Stock

The touchscreen on my Fire stopped working today. I already talked to Amazon and am getting a replacement, but I want to revert back to stock before sending it in. I've seen ways to do this with TWRP, but I don't have a touchscreen to use TWRP, or any recovery for that matter, with.
Is there any way to do this?
I do have full ADB and Fastboot access, with FireFireFire working, but do not have a currently working rom installed (I was on CM9, and it won't go past the boot screen).

drk.hd said:
The touchscreen on my Fire stopped working today. I already talked to Amazon and am getting a replacement, but I want to revert back to stock before sending it in. I've seen ways to do this with TWRP, but I don't have a touchscreen to use TWRP, or any recovery for that matter, with.
Is there any way to do this?
I do have full ADB and Fastboot access, with FireFireFire working, but do not have a currently working rom installed (I was on CM9, and it won't go past the boot screen).
Click to expand...
Click to collapse
There is a way to do this with adb... I just do not know the proper commands. Sorry

Does installing a custom rom void the warranty? Seems like it would be BS for Amazon not to honor it when it's apparently a hardware related issue.

sengwall said:
Does installing a custom rom void the warranty? Seems like it would be BS for Amazon not to honor it when it's apparently a hardware related issue.
Click to expand...
Click to collapse
No, I don't think it does, but I'd rather not take the chance.

drk.hd said:
No, I don't think it does, but I'd rather not take the chance.
Click to expand...
Click to collapse
YES! It absolutely does. The second the device was rooted it broke warranty.
Sent from my myTouch_4G_Slide using XDA App

The same thing actually happened to me earlier today. I was just browsing some sites on the ICS rom when it just stopped responding. I couldn't get it to recognize any touches even after a bunch of reboots, so I just figured it to be some bug that hadn't been squashed yet. When I dropped down to recovery and saw the same issue, I knew I had a real problem.
Hoping against hope, I tried both CWMR and TWRP on it and got no results. Like you, I figured it would have to go back to Amazon, so I started searching for a way to get it back to stock... nothing obvious jumped out at me because everything is written with access to recovery in mind... which doesn't help.
So, I started reading about adb and going through the built-in help. As I was familiarizing myself with some basic adb commands and options, I left TWRP open in front of me. I don't know how long I had it that way when I mindlessly tapped on the screen and thought I saw it flicker. Yes! I had pressed the Wipe button and it had taken me to that section. It's been working fine ever since.
I'm not claiming I did anything and I don't have a how-to on how to fix it, but it couldn't hurt to just leave the thing running in recovery for a while and see if the touchscreen comes back to life for you too.
Still, I'd love to see someone with more adb knowledge provide a simple tutorial on how to get it back to stock without access to recovery. I'm sure it would be helpful to someone in the future... maybe even me if the same problem comes up again.
Best of luck to you.

Just ignore my comment
Sent from my Amazon Kindle Fire using Tapatalk

If your on the rooted stock rom you could always wait until Amazon pushing the next OTA

You will have to make a fastboot image and flash that with fastboot. But before you create the image, you will have to create all the appropriate symlinks. Then you run...
Code:
make_ext4fs -l 512m -a system -s /path/to/fastboot_system.img /path/to/system_folder
That will create the fastboot image. Then when FFF gives you fastboot access, you run...
Code:
fastboot flash system fastboot_system.img
You will also need a fastboot image for recovery and the bootloader.

Isn't there any easy way like with my desire, simple ruu.
Or hasn't anyone created these images to flash. I also need to get back to stock everything and send it to amazon, my wifi gets error after some period of time and some times when screen goes off, try'd 3 roms and stock.

There is a way to tell the device to install /sdcard/update.zip via shell commands. I forget what they are tho. Something about the extendedcommands. If I have time tomorrow I'll look it up.

here it is:
http://www.theandroidsoul.com/kindle-fire-stock-rom-installation-guide/

b63 said:
here it is:
http://www.theandroidsoul.com/kindle-fire-stock-rom-installation-guide/
Click to expand...
Click to collapse
Thanks for the link. I'm back on this thread because I think my Kindle Fire touchscreen is now dead for good. However, those instructions do not work as-is because you need to press a button on the screen to tell the Kindle Fire to allow the host to mount it as a USB Mass Storage device. Although those instructions don't get you all the way there, I was able to use the core idea to get my Kindle Fire back to stock. So, many thanks for pointing me in the right direction.
On top of the touchscreen not working, I ended up partially bricking the device trying to find a way to flash it back to stock, so I had also posted in the Unbricking thread. I posted my solution there....
http://forum.xda-developers.com/showpost.php?p=23226260&postcount=701
Odds are, if you have a device that is booting correctly, you will be able to ignore steps 3 and 4 and get it booting back to stock. I do have a couple of other suggestions... Leave your USB cable hooked up to the Kindle Fire as it boots into stock for the first time. This is the only time that it will automatically mount the /sdcard to your computer and you will have a chance to reclaim (and delete) all the files stored there. You can also do something like 'adb pull /sdcard C:\sdcard' before you flash. Also, depending on what ROM and apps you were using before starting the process, you might want to delete your user data and reset the device to factory defaults. You can do this with 'fastboot erase userdata' and the next time you start the device, you'll get a warning that it's about to reset. Hit the power button and you should have a clean, fresh from the factory Kindle fire... albeit with a broken touchscreen. Good luck!

After several failed attempts to follow this guide (no offense to posters; I appreciate your contributions), I found this to be the simplest method.
http://stackoverflow.com/questions/10817721/wipe-data-factory-reset-through-adb
Download stock update, then it's basic procedure in adb:
adb push C:/update.zip /sdcard/update.zip
adb shell
recovery --wipe_data
After reboot, go back into to adb shell and do "recovery--update_package=/sdcard/update.zip"
Factory reset, etc. and you're good to go.

Team Win Recovery Loop

Hello, I am new to XDA as being a member. This is my first post, and I promise I have spent at least an hour looking for similar threads to no avail.
Now to explain my problem,
Last night I rooted my kindle again after the 6.3 update that destroyed my last root. I used the Kindle Fire utility 9.5 by Vashypoo, and selected install permanent root with superuser.
As I discovered after this, I needed to get team win recovery before getting 6.3, so the KFU installed it for me, and it backed up my data before continuing with the rest of the root. After it said complete, I booted up my kindle, to find a yellow triangle and in a couple seconds, i got sent to this page automatically that I know now is the team win main menu. Every time I boot up my kindle, I get sent to the team win main page. I saw on a video by Nat3mil that the reason this was happening was because my kindle was automatically booting in recovery, so I tried to use kindle's bootmode menu to change the bootmode back to normal (4000) whenever I try, I get a message saying "The system cannot find the drive specified", and it would stop doing anything. I tried to manually set the bootmode back to normal by using command lines from a forum here on xda, similar to my problem, HOWEVER, whenever I try to connect my kindle to the pc, 9 out of ten times, my computer doesnt even recognize my kindle is connected, and when it does, it installs software, KFU says adb is online, and STILL whenever I try using KFU, command lines, or the Kindle Unbrick utility, it says "waiting for device". I literally cannot do a thing without help.... So to sum up, my problem is that I cannot connect my kindle to the computer, and second, I don't know what else to try... I really need help, and I have been doing tons of research (over six hours) to no avail, or progress.
Thank you for your time, and I hope that someone can help me.

Read this guide. It will give you an idea of what your problem is and what you are doing wrong. Its lengthy but worth it if you want do much with your Kindle, like installing recovery.
http://forum.xda-developers.com/showthread.php?p=23747567
Sent from my Amazon Kindle Fire using xda premium

your on the right path When you get it to say waiting for device hold the power button to shut the kindle off and then turn it back on and it will connect during boot up

soupmagnet said:
Read this guide. It will give you an idea of what your problem is and what you are doing wrong. Its lengthy but worth it if you want do much with your Kindle, like installing recovery.
http://forum.xda-developers.com/showthread.php?p=23747567
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
You see, I already read this in my expansive research. It doesnt exactly help, My computer does not recognize my device. I have manually installed the driver multiple times, my problem is not ignorance... But the thread was a bit helpful with less knowledgeable people such as myself. I do however have MUCH more experience with a lot of this than I let on by my passage above. Thank you for answering, but do you know what to do in my case? This is not a repeated thread, because I have seen nothing like this on a previous thread

MLS_Dumpster said:
You see, I already read this in my expansive research. It doesnt exactly help, My computer does not recognize my device. I have manually installed the driver multiple times, my problem is not ignorance... But the thread was a bit helpful with less knowledgeable people such as myself. I do however have MUCH more experience with a lot of this than I let on by my passage above. Thank you for answering, but do you know what to do in my case? This is not a repeated thread, because I have seen nothing like this on a previous thread
Click to expand...
Click to collapse
You have to get it to how you had it to say waiting for device... reinstall the drivers, reboot comp what ever you have to do than do what i posted... you can even open a command promp from the KFU tools folder by going to tools hold shift and right click... open command than type..
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot

It happens randomly, You see, another problem I have been having is that, My kindle has no problem connecting to the computer, in device manager, I have adb interface up and running, my kindle connected, but it isnt useable, it says my adb is offline, and whenever that happens, I cannot do a thing... There is no tred whatsoever as to how to get adb working, as it happens at random tries of me installing the drivers, and restarting my comp/kindle, do you have any idea how to get it working? Thanks by the way, You literally are a lifesaver.

MLS_Dumpster said:
It happens randomly, You see, another problem I have been having is that, My kindle has no problem connecting to the computer, in device manager, I have adb interface up and running, my kindle connected, but it isnt useable, it says my adb is offline, and whenever that happens, I cannot do a thing... There is no tred whatsoever as to how to get adb working, as it happens at random tries of me installing the drivers, and restarting my comp/kindle, do you have any idea how to get it working? Thanks by the way, You literally are a lifesaver.
Click to expand...
Click to collapse
Im on linux so idk how to set it up on windows.... i have read of people having issues with the drivers and having to reinstall them after using kfu.. id just make sure you delete the kindle driver and the android adb composite driver and start fresh.. or even try and mount it threw twrp mabe that will help

Thanks for helping me, seriously. Windows is annoying with drivers. I'll try what you suggested. Thanks again

DJLamontagneIII said:
Im on linux so idk how to set it up on windows.... i have read of people having issues with the drivers and having to reinstall them after using kfu.. id just make sure you delete the kindle driver and the android adb composite driver and start fresh.. or even try and mount it threw twrp mabe that will help
Click to expand...
Click to collapse
THANK YOU THANK YOU THANK YOU THANK YOU
IT WORKED. YOU, sir, are a life saver.
Thanks again.

MLS_Dumpster said:
THANK YOU THANK YOU THANK YOU THANK YOU
IT WORKED. YOU, sir, are a life saver.
Thanks again.
Click to expand...
Click to collapse
Awsome

MLS_Dumpster said:
You see, I already read this in my expansive research. It doesnt exactly help, My computer does not recognize my device. I have manually installed the driver multiple times, my problem is not ignorance... But the thread was a bit helpful with less knowledgeable people such as myself. I do however have MUCH more experience with a lot of this than I let on by my passage above. Thank you for answering, but do you know what to do in my case? This is not a repeated thread, because I have seen nothing like this on a previous thread
Click to expand...
Click to collapse
I wasn't trying to be rude but the exact problem you were having was covered in the thread that I posted along with the same solution suggested by DJLamontagnelll.
Sent from my Amazon Kindle Fire using xda premium

soupmagnet said:
I wasn't trying to be rude but the exact problem you were having was covered in the thread that I posted along with the same solution suggested by DJLamontagnelll.
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
I think I sounded more harsh than I meant to be. The solutions on the thread only cover one of my problems, and thats the drive thing. Thanks, you did help.
Sent from my Kindle Fire using XDA

Hello.
I write to you because I have a big problem with mi LG G2 D802.
Yesterday I tried to install a CRM apk to use in a signature of the University. I was using CM11, but the apk had failed. So, I restored my ROM STOCK backup and when the phone start, a new update was downloaded and installed. Then, the phone only enter in recovery mode. I tried the different wipes, restore again ROM Stock, install again CM11 ROM but the problem was not solved.
I tried to enter in bootleader (pushing vol+ and insert the usb cable), but the phone reboot in recovery.
Now, I don´t know why, the phone is empty. I tried to restore ROM Stock backup from USB OTG but the recovery don´t recognizes the folders.
Please, can anybody help me? I need the pone!
Thanks.
Regards,
Nicolas.

nicolas_h18 said:
Hello.
I write to you because I have a big problem with mi LG G2 D802.
Yesterday I tried to install a CRM apk to use in a signature of the University. I was using CM11, but the apk had failed. So, I restored my ROM STOCK backup and when the phone start, a new update was downloaded and installed. Then, the phone only enter in recovery mode. I tried the different wipes, restore again ROM Stock, install again CM11 ROM but the problem was not solved.
I tried to enter in bootleader (pushing vol+ and insert the usb cable), but the phone reboot in recovery.
Now, I don´t know why, the phone is empty. I tried to restore ROM Stock backup from USB OTG but the recovery don´t recognizes the folders.
Please, can anybody help me? I need the pone!
Thanks.
Regards,
Nicolas.
Click to expand...
Click to collapse
Please post in correct forum. G2 Q&A, Help & Troubleshooting

Kindle Fire bricked. Need major help

Hello, so this is my first time trying to root an android device, and I think I messed up. I watched a tutorial on youtube on how to do it and successfully installed superuser and twrp from a batch file ( I had to install adb drivers first ). I wasn't really sure I did it in the correct steps, so I wanted to revert back to the stock os. I booted into twrp and wiped the data ( cache, system, etc) from twrp. I then mounted it and transfered the kindle fire update 6.3.1 to my KF. I used the option on twrp to revert back to stock using the newly transferred zip. It ran for awhile then prompted me to click reboot. So I did. And this is where it gets tricky
After the reboot, all I see is the boot screen displaying "kindle fire." It never booted and lasted like this for hours. I tried to boot into twrp but I think it got deleted. I googled the problem and found it was in some sort of fastboot loop. I tried many fixes, using adb and other fastboot commands. Every time I tried anything, all I got was "waiting for device." Also, I couldn't use adb shell because it said system/bin/sh was not found. I went to my computer and found that the kindle fire no longer showed up as a removable device, but it showed up in device manager as adb composite interface under android phone. I thought that somehow all of my system files got deleted and thats why it says system/bin/sh not found. I tried to use the adb push command to manually send the update.zip to the KF but it is no longer a mounted drive, so there is nowhere to send it to. I'm at a loss here, Ive tried numerous utilities such as KFU, firekit, unbrick utility. I just need to figure out a way to remount the KF and copy over the folder "system" in the update.zip. If anyone could help me that would be great, as I have been trying to fix this for three days now.:fingers-crossed:

Read the How To in the attached link and it should help you figure out what the problem is and get you unbricked, http://forum.xda-developers.com/showthread.php?t=1552547.

tazmanhawaii said:
Read the How To in the attached link and it should help you figure out what the problem is and get you unbricked, http://forum.xda-developers.com/showthread.php?t=1552547.
Click to expand...
Click to collapse
That doesn't really help me at all, as I have tried the solutions that what you just posted provides, and none of them have worked. I have tried flashing firefirefire and twrp to the kindle fire using fastboot, but to no avail. I think I need a bit more help than a beginner's guide can provide, but thanks for the link.

Marblesnake said:
That doesn't really help me at all, as I have tried the solutions that what you just posted provides, and none of them have worked. I have tried flashing firefirefire and twrp to the kindle fire using fastboot, but to no avail. I think I need a bit more help than a beginner's guide can provide, but thanks for the link.
Click to expand...
Click to collapse
First of all, when you try to revert to stock without wiping the necessary partitions, bad things will happen. What usually happens is you end up with some sort of frankenROM with no working shell and no custom bootloader or recovery.
Based on your description, it seems like you aren't in fastboot at all. You can confirm this by paying attention to the boot screen at the device starts up. If you see a bright Kindle Fire logo that stays bright, you're in fastboot. If you see a bright Kindle Fire logo that dims a little after a few seconds, you're no longer in fastboot and the device is trying to boot normally. What usually happens in situations like yours is, not only does the system have no way of booting, but there is also no working shell to send the necessary commands to change the bootmode, and you will receive the typical "system/bin/sh not found" error.
The problem is without a working shell, you cannot get into fastboot to install custom recovery and you cannot install recovery while booted "normally" without a working shell.
You have two options:
* Acquire a factory cable. A Motorola style factory programming cable to be exact. You can purchase one, or make one yourself. There is a thread in the KF General forum with information regarding both. The factory cable will put the device in fastboot so you will be able to install custom recovery and repair your system.
or
* Use Firekit. But in order for Firekit to work properly in your situation, you need to put the device in USBboot to install a "new" bootloader and recovery. This consists of opening the device and using the "shorting trick" as described in the Firekit thread. I would suggest creating a liveUSB with "persistence" and install the SoupKit. SoupKit comes with Firekit along with a number of other tools you may find useful.
Either way, you need to get custom recovery installed so you can wipe your system and data (factory reset) partitions and flash a new ROM. If it's the stock ROM you want, MoDaCo is your best bet. Once you install a custom ROM, there is no need to "root" as all custom ROMs come pre-rooted.
Hope that helps.

soupmagnet said:
First of all, when you try to revert to stock without wiping the necessary partitions, bad things will happen. What usually happens is you end up with some sort of frankenROM with no working shell and no custom bootloader or recovery.
Based on your description, it seems like you aren't in fastboot at all. You can confirm this by paying attention to the boot screen at the device starts up. If you see a bright Kindle Fire logo that stays bright, you're in fastboot. If you see a bright Kindle Fire logo that dims a little after a few seconds, you're no longer in fastboot and the device is trying to boot normally. What usually happens in situations like yours is, not only does the system have no way of booting, but there is also no working shell to send the necessary commands to change the bootmode, and you will receive the typical "system/bin/sh not found" error.
The problem is without a working shell, you cannot get into fastboot to install custom recovery and you cannot install recovery while booted "normally" without a working shell.
You have two options:
* Acquire a factory cable. A Motorola style factory programming cable to be exact. You can purchase one, or make one yourself. There is a thread in the KF General forum with information regarding both. The factory cable will put the device in fastboot so you will be able to install custom recovery and repair your system.
or
* Use Firekit. But in order for Firekit to work properly in your situation, you need to put the device in USBboot to install a "new" bootloader and recovery. This consists of opening the device and using the "shorting trick" as described in the Firekit thread. I would suggest creating a liveUSB with "persistence" and install the SoupKit. SoupKit comes with Firekit along with a number of other tools you may find useful.
Either way, you need to get custom recovery installed so you can wipe your system and data (factory reset) partitions and flash a new ROM. If it's the stock ROM you want, MoDaCo is your best bet. Once you install a custom ROM, there is no need to "root" as all custom ROMs come pre-rooted.
Hope that helps.
Click to expand...
Click to collapse
Thanks for the help. Yeah, I tried the firekit method but didn't use the shorting trick. I have scoured the internet for information and tricks and it seems like these are my last two options before I throw this thing out the window. I have seen your posts in other threads and you have been a great help throughout this ordeal.

factory cable
thank you for this information. I am in the same predicament. I am purchasing a factory cable from Amazon $1.27.
It is sold by Earlybirdsavings and is a 3ft micro USB factory cable for kindle fire and Motorola Xoom.
thank you for all the helpful information!