Somewhy it doesn't work.... it's stuck on 'waiting for device' and is not responding and i need my phone rooted badly...
Never mind, it's working...
Related
Ok, Im new to android and this account is new also because I cant remember the password of the old account...
So i was in 6.2, supposedly I rooted it, because I was able to run the Android marketplace. So Today I decided to give CM7 a try, so I follow a "tutorial" on
liliputing dot com, it is using "KindleFireUtility"
So when I hit "7" on KindleFire Utility , it downloaded twrp and the it said it has to check if the device was rooted or something, so it did all that, then it stay for like 10 minutes on "restarting device" or "waiting for device", and the kindle was doing nothing at all, it didnt turn off or do anything, so I got tired of waiting and hit the "Disconnect" button on the kindle screen, unplug the USB, the Kindle turned off and back on and it stays on the very first screen with the KinleFire Logo, it doesnt even shows the little animation. Now the computer doesnt detects the kindle at all...
I try to follow the steps in the topic : [HOW TO] Unbricking/Restoring your Kindle Fire 9 Attachment(s)
But it says "error: device not found"
What now?
I dont know is this has any relevance at all, but Im using a MacBook running Windows7 on "WMware Fusion"
Throwing a guess out there, you're probably still in fastboot.
//KindleFire.Tapatalk//
You're definitely on fastboot mode.
I just answered a similar problem here http://forum.xda-developers.com/showpost.php?p=20619033&postcount=11
Hope it helps you too.
ch0mch0m said:
You're definitely on fastboot mode.
I just answered a similar problem here http://forum.xda-developers.com/showpost.php?p=20619033&postcount=11
Hope it helps you too.
Click to expand...
Click to collapse
nope, either I cant seem to undestand exactly what i have to do and im doing it wrong, or it doesnt work on mine...
at one moment the computer recognize the kindle as a "unrecognize device" but still didnt work, or maybe I dont know how to do it, and now it doesnt recognize it anymore, just like it was yesterday, I connect it and nothing happens...
:/
You need to reinstall drivers to get your machine to see the kindle properly.
Sent from my PC36100 using xda premium
When The computer detects ir as a "unrecognize device" if I click update drivers I point it to where the drivers are and it tells me the drivers are up to date.
Kindlefiteutility shows "error: device not found" or something like that...
I'm still stuck /:
Shadow-of-Death said:
When The computer detects ir as a "unrecognize device" if I click update drivers I point it to where the drivers are and it tells me the drivers are up to date.
Kindlefiteutility shows "error: device not found" or something like that...
I'm still stuck /:
Click to expand...
Click to collapse
The instructions from this link fixed it for me the other day. I would do a complete shutdown of your Mac/PC instead of a reboot as a simple reboot didn't work for me the first time.
Ramer84015 said:
The instructions from this link fixed it for me the other day. I would do a complete shutdown of your Mac/PC instead of a reboot as a simple reboot didn't work for me the first time.
Click to expand...
Click to collapse
the thing is that I cant get the computer to recognize it as a kindle, or even a android phone!...
-_________________-
If I direct it to the folder with the drivers it doesnt do anything, and if I click pick from list, like the guy say on that post theres no "android" on the list.
So It seems I will just have to enjoy my Brick Fire how it is, I guess I can use it as a pretty expensive door stoper or paper weight....
I would like to know if there is some news about the unbrick of B80kas devices.
Because I juste bricked mine today, black screen tried cold boot it doesnt start, i can conect it in apx mode, but what we can do ? ... I am so disapointed from what i did -_-
Do you have a custom recovery that works? And does ADB work? Since you can't use NvFlash if both of those are no I think you may be out of luck.
My custom recovery was working, but I can't boot on it, my tab don't want to start, and adb say me there is "no device found ".
merjeu said:
My custom recovery was working, but I can't boot on it, my tab don't want to start, and adb say me there is "no device found ".
Click to expand...
Click to collapse
A few threads here show people managed to unbrick using adb by pushing method.. Just search them in the Q&A section..
I changed a cracked screen on a Nexus 4. I have done this before with no problems. It is not rooted and locked to a carrier. Now it is stuck in bootloop.
Now the real problem is that even though the phone will take a charge, when I connect it to a PC it the PV doesnt see the phone and it doesn't show up in file folders or in Nexus Toolkit.
So I cannot access ADB either since the PC doesn't see the device and same with Nexus Toolkit.
I can boot into recovery mode but it goes to Android man on back with red flag and "No Command Found" message.
I have spent a week on this. Who out there knows what the hell I can do. I have thought about swapping out the charger port to see if thats why the pc isnt seeing the phone...I am stumped. Help would be very appreciated folks.
Thanks
Wallstud44 said:
I changed a cracked screen on a Nexus 4. I have done this before with no problems. It is not rooted and locked to a carrier. Now it is stuck in bootloop.
Now the real problem is that even though the phone will take a charge, when I connect it to a PC it the PV doesnt see the phone and it doesn't show up in file folders or in Nexus Toolkit.
So I cannot access ADB either since the PC doesn't see the device and same with Nexus Toolkit.
I can boot into recovery mode but it goes to Android man on back with red flag and "No Command Found" message.
I have spent a week on this. Who out there knows what the hell I can do. I have thought about swapping out the charger port to see if thats why the pc isnt seeing the phone...I am stumped. Help would be very appreciated folks.
Thanks
Click to expand...
Click to collapse
What happened to this? I have the same damn issue. Although I managed to get fastboot and adb functionality with great difficulty. But the device doesn't seem to be able to boot into anything. I've tried every single thing software by the book, and by the forums too. I suspect it might be hardware.
Any luck?
My Phone doesnt boot .not even in recovery mode.help me pleasee
there was an option of installing the os in the twrp recovery mode but i didnt do it. i thought of switching off. now it doesnt even turn on.not even in recovery mode.what shoulld i do???. HELP
i tried opening it in adb but it shows "waiting for devices".
Plug it in your pc it should ve found as qualcom something device.Then you can unbrick it by some of the tutorials on web.With qualcom flasher or something like that
ikevin96x said:
My Phone doesnt boot .not even in recovery mode.help me pleasee
there was an option of installing the os in the twrp recovery mode but i didnt do it. i thought of switching off. now it doesnt even turn on.not even in recovery mode.what shoulld i do???. HELP
i tried opening it in adb but it shows "waiting for devices".
Click to expand...
Click to collapse
Always first do a complete search on xda, because there's always someone else who had the same problem earlier. This question has been asked a gazillion times. Thats not too big a problem. If you follow correctly, you'll be able to unbrick it in no time. Follow this tutorial and first try the third method. If that doesn't work then try the second one.
ikevin96x said:
My Phone doesnt boot .not even in recovery mode.help me pleasee
there was an option of installing the os in the twrp recovery mode but i didnt do it. i thought of switching off. now it doesnt even turn on.not even in recovery mode.what shoulld i do???. HELP
i tried opening it in adb but it shows "waiting for devices".
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=Aejq4DW4XOA
follow this tutorial, dont worry itll fix up its not a big issue - happened with me too
you might try this tutorial
my phone once was brick like that, but it solved after tried that tutorial.
hope it worked with you as well.
good luck
Was hoping anyone could give me some direction after I tried to root and unlock my V995 using the DirtySanta steps. I got to the part where you are to execute "Step3.bat". I received the message below which is how I figured out I didn't have the fastboot drivers.
(******Sidenote******
If you get message saying <waiting for device> on Step3.bat then you do not have the fastboot drivers installed(you may have the program but not the drivers).
To fix: Go to your device manager while the device is connected in fasboot and right click the item that says Android and select update drivers. Then select from internet. and let it install the drivers then try step3.bat again.
*************).
Afterwards the CMD screen closed out, and now i'm stuck with the unusable screen. Anyone else have this problem?
Thanks in advance guys.
What screen are you stuck on? LG logo?
Lonewolf17a said:
Was hoping anyone could give me some direction after I tried to root and unlock my V995 using the DirtySanta steps. I got to the part where you are to execute "Step3.bat". I received the message below which is how I figured out I didn't have the fastboot drivers.
(******Sidenote******
If you get message saying <waiting for device> on Step3.bat then you do not have the fastboot drivers installed(you may have the program but not the drivers).
To fix: Go to your device manager while the device is connected in fasboot and right click the item that says Android and select update drivers. Then select from internet. and let it install the drivers then try step3.bat again.
*************).
Afterwards the CMD screen closed out, and now i'm stuck with the unusable screen. Anyone else have this problem?
Thanks in advance guys.
Click to expand...
Click to collapse
Nevea said:
What screen are you stuck on? LG logo?
Click to expand...
Click to collapse
Actually I got passed that. Now my problem is I can't boot back into the system, just forces me back into TWRP. I'm fairly certain the stock ROM is gone because I was flying through screens too quickly. But I could be wrong.
Any advice?
Are you getting the "no os" messege or just boots you right into TWRP?
Nevea said:
Are you getting the "no os" messege or just boots you right into TWRP?
Click to expand...
Click to collapse
Just straight into TWRP. I've tried flashing US996 to no avail. Just staright back into TWRP.
Like this.
Phone powered off> Power phone on> Briefly LG Logo> Red Triangle message> LG Logo> TWRP.
No combination I've tried gets me out from TWRP. I can still get into Fastboot however.
I should say also I got the Secure Start Up message and it rewiped my phone.
That's about when this started.
It seems stuck at this point, and to my knowledge there is no stock Verizon Rom to flash to try to get it unstuck.
Thanks again and any help is appreciated.
Have you tried going into fastboot and reflashing boot1 then starting from step 3 in the rooting guide?
Nevea said:
Have you tried going into fastboot and reflashing boot1 then starting from step 3 in the rooting guide?
Click to expand...
Click to collapse
I have, that was actually my first thought. I get past step3.bat and follow TWRP instructions about SuperSU. Once I try to reboot into the system to complete first activation set up it sends me straight into TWRP. I've even just gone straight back into Fastboot to flash boot2.img and sent the ADB command to reboot. Straight back to TWRP.
Honestly my thought is once Secure Start Up wiped the device it did something to the system partition. Only thing against that logic is that it should have booted when I flashed US996. So I'm pretty well scratching my head.
gotta be something so small since you still have os. Wish i had verizon to help you out.. But im on ATT.. I backed up my system but no help to u.
Nevea said:
gotta be something so small since you still have os. Wish i had verizon to help you out.. But im on ATT.. I backed up my system but no help to u.
Click to expand...
Click to collapse
Don't sweat it bud. I appreciate your help. Guess I'm waiting for a Verizon stock until then!