Related
TWRP installed. was on pre 6.2.1 Factor reset to deliver as a gift for xmas.
Reboot and stuck in TWRP. factory reset from there but just goes right back in to TWRP. I'm stuck.
Suggestions?
Flash a rom, and never factory reset.
Sent from my MB865 using xda premium
have you tried
adb shell
idme bootmode 4000
or vashypooh's kindle fire utility to change the bootmode?
pcrii said:
have you tried
adb shell
idme bootmode 4000
or vashypooh's kindle fire utility to change the bootmode?
Click to expand...
Click to collapse
Linux. Adb isn't seeing it. Is there a specific mode within TWRP I'm supposed to be in? I can mount and I've tried installing Update zip with a rooted 6.2.1 and CM7. says installing but then gets the misc error and after reboot just bounced back to TWRP
Can get zipped ROMs on there. Says installing. Complete. But nope, just back to TWRP. Damnit
Reinstall the drivers.
Sent from my Kindle Fire using Tapatalk
itsDefying said:
Reinstall the drivers.
Sent from my Kindle Fire using Tapatalk
Click to expand...
Click to collapse
Don't need em. Native on Linux. Worked fine before i decided to get stupid
jonjon68 said:
Linux. Adb isn't seeing it. Is there a specific mode within TWRP I'm supposed to be in? I can mount and I've tried installing Update zip with a rooted 6.2.1 and CM7. says installing but then gets the misc error and after reboot just bounced back to TWRP
Click to expand...
Click to collapse
Had to restart adb. schweeee. Thank you sir.
Before you get all mad at me, I know there is another thread for this. This is a method that has worked for me when all other methods have failed.
I found out about this after looking around the interwebs for a while when my Kindle was stuck in a recovery loop, or stuck at the boot logo.
Your Kindle is stuck at the boot logo? I think I can help! Follow these steps!
This is WINDOWS ONLY for the time being!
1. Download and extract Kindle Fire Utility. You should be able to easily find it on the xda forums.
2. Reboot your PC.
2.5. If you have FIREFIREFIRE, go into the drivers folder in the Kindle Fire Utility and open up adb_usb.ini. Add the following line:
Code:
0x18d1
Do not delete the other lines.
3. After the reboot, connect your Kindle via USB. Go into where you unzipped Kindle Fire Utility, and run install_drivers.bat
4. Once that's done, open up a command prompt and navigate to the "tools" folder of the Kindle Fire Utility.
You do this by using this command:
Code:
cd (File path to tools folder)
Or in my case:
Code:
cd C:\Users\ZombiePiratez\Desktop\KFire Utility\Kindle Fire Utility\tools
5. After that, run the following commands:
If you DO NOT have FIREFIREFIRE, then use these commands:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
If you DO have FIREFIREFIRE
Code:
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
If all else fails, try these commands:
Code:
fastboot oem idme bootmode 4000
fastboot reboot
6. Hopefully by this point, your Kindle will be rebooting. THIS WILL NOT WORK FOR EVERYONE. Only people stuck at the bootlogo, or in a recovery loop.
Now, go have fun with your newly awesome and unbricked Kindle Fire!
What is firefirefire? Have yet to see a formal definition of that
androidcues said:
What is firefirefire? Have yet to see a formal definition of that
Click to expand...
Click to collapse
Its a bootloader
Sent from my Kindle Fire using xda premium
Thanks Man, I was messing around with CM7 and I rebooted into recovery not knowing that it would keep me in a recovery boot loop and KFU wasn't helping trying to help me.
Tierehl said:
Thanks Man, I was messing around with CM7 and I rebooted into recovery not knowing that it would keep me in a recovery boot loop and KFU wasn't helping trying to help me.
Click to expand...
Click to collapse
Happy to help
Zombiepiratez said:
Before you get all mad at me, I know there is another thread for this. This is a method that has worked for me when all other methods have failed.
I found out about this after looking around the interwebs for a while when my Kindle was stuck in a recovery loop, or stuck at the boot logo.
Your Kindle is stuck at the boot logo? I think I can help! Follow these steps!
This is WINDOWS ONLY for the time being!
1. Download and extract Kindle Fire Utility. You should be able to easily find it on the xda forums.
2. Reboot your PC.
2.5. If you have FIREFIREFIRE, go into the drivers folder in the Kindle Fire Utility and open up adb_usb.ini. Add the following line:
Code:
0x18d1
Do not delete the other lines.
3. After the reboot, connect your Kindle via USB. Go into where you unzipped Kindle Fire Utility, and run install_drivers.bat
4. Once that's done, open up a command prompt and navigate to the "tools" folder of the Kindle Fire Utility.
You do this by using this command:
Code:
cd (File path to tools folder)
Or in my case:
Code:
cd C:\Users\ZombiePiratez\Desktop\KFire Utility\Kindle Fire Utility\tools
5. After that, run the following commands:
If you DO NOT have FIREFIREFIRE, then use these commands:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
If you DO have FIREFIREFIRE
Code:
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
If all else fails, try these commands:
Code:
fastboot oem idme bootmode 4000
fastboot reboot
6. Hopefully by this point, your Kindle will be rebooting. THIS WILL NOT WORK FOR EVERYONE. Only people stuck at the bootlogo, or in a recovery loop.
Now, go have fun with your newly awesome and unbricked Kindle Fire!
Click to expand...
Click to collapse
Unfortunately this will only work if your windows based computer even recognizes the kindle, which mine doesn't. Thanks tho. I've given mine to my tech geek who has access to linux based system, so hopefully he will be able to recover my brick.
Sent from my MB860 using XDA App
Sorry about that. I wish I could help.
I am a newbie. I recover my kf using the recovery boot with kfu and it works fine now. how could
I know if it is in the recovery boot loop? Many thanks.
Sent from my GT-I9100 using XDA App
Zombiepiratez said:
Sorry about that. I wish I could help.
Click to expand...
Click to collapse
Its ok. I read everywhere its impossible to brick a kindle so im hoping that's true.
Sent from my MB860 using XDA App
My Windows PC wouldn't recognize my KF stuck in recovery mode, either. I think it reported in as an "unknown USB device" or something. I had to shut down the Kindle and then plug the USB in, which for whatever reason got my computer to recognize it. I think it might be similar to the effect of a battery drain?
*Snip*
Double post, fail.
CiggyPipe said:
My Windows PC wouldn't recognize my KF stuck in recovery mode, either. I think it reported in as an "unknown USB device" or something. I had to shut down the Kindle and then plug the USB in, which for whatever reason got my computer to recognize it. I think it might be similar to the effect of a battery drain?
Click to expand...
Click to collapse
Did it just immediately recognize it, or did you have to re-install drivers? And i'm not sure about the battery drain thing...
CiggyPipe said:
My Windows PC wouldn't recognize my KF stuck in recovery mode, either. I think it reported in as an "unknown USB device" or something. I had to shut down the Kindle and then plug the USB in, which for whatever reason got my computer to recognize it. I think it might be similar to the effect of a battery drain?
Click to expand...
Click to collapse
Tried that to no avail as well.
Sent from my MB860 using XDA App
Zombiepiratez said:
Did it just immediately recognize it, or did you have to re-install drivers? And i'm not sure about the battery drain thing...
Click to expand...
Click to collapse
I guess I should make note that by this point I'd uninstalled the driver I used. It was recognized as "kindle" once after I plugged it in while off, so then I went ahead and manually reinstalled the driver (from Jayce Ooi's site), which allowed the fastboot commands to work. Otherwise, the command would hang at <waiting for device>.
Thanks! My kindle fire was stuck at the firefirefire logo. My computer couldn't even recognize my kindle but I uninstalled the Android ADB composite interface and plugged it back in, when the kindle was off. Then I used your commands to get fastboot. I installed TWRP, now I'm stuck in TWRP and can't mount my sd... to flash any rom.
Thanks
Thanks for the info. i thought i'd bricked it and the info worked a treat. that will teach me to keep my mouth shut "of course i can root your kindle"
try fixing permissions under advanced, and then make sure only the sdcard box is marked in mount option.
Sent from my Amazon Kindle Fire using xda premium
Zombiepiratez said:
Before you get all mad at me, I know there is another thread for this. This is a method that has worked for me when all other methods have failed.
I found out about this after looking around the interwebs for a while when my Kindle was stuck in a recovery loop, or stuck at the boot logo.
Your Kindle is stuck at the boot logo? I think I can help! Follow these steps!
This is WINDOWS ONLY for the time being!
1. Download and extract Kindle Fire Utility. You should be able to easily find it on the xda forums.
2. Reboot your PC.
2.5. If you have FIREFIREFIRE, go into the drivers folder in the Kindle Fire Utility and open up adb_usb.ini. Add the following line:
Code:
0x18d1
Do not delete the other lines.
3. After the reboot, connect your Kindle via USB. Go into where you unzipped Kindle Fire Utility, and run install_drivers.bat
4. Once that's done, open up a command prompt and navigate to the "tools" folder of the Kindle Fire Utility.
You do this by using this command:
Code:
cd (File path to tools folder)
Or in my case:
Code:
cd C:\Users\ZombiePiratez\Desktop\KFire Utility\Kindle Fire Utility\tools
5. After that, run the following commands:
If you DO NOT have FIREFIREFIRE, then use these commands:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
If you DO have FIREFIREFIRE
Code:
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
If all else fails, try these commands:
Code:
fastboot oem idme bootmode 4000
fastboot reboot
6. Hopefully by this point, your Kindle will be rebooting. THIS WILL NOT WORK FOR EVERYONE. Only people stuck at the bootlogo, or in a recovery loop.
Now, go have fun with your newly awesome and unbricked Kindle Fire!
Click to expand...
Click to collapse
I'm sorry but I tried all the steps above but KF's still stuck at boot logo. I flashed CM9 stock kernel 3.0 with FFF 1.4a and CWR, wiped everything and factory reset, then install...but it just hangs at the blue skating droid logo... any idea?
jamesphan said:
I'm sorry but I tried all the steps above but KF's still stuck at boot logo. I flashed CM9 stock kernel 3.0 with FFF 1.4a and CWR, wiped everything and factory reset, then install...but it just hangs at the blue skating droid logo... any idea?
Click to expand...
Click to collapse
The Unbrick utility won't help in your case. When the device hangs at the boot animation or goes to a blank screen afterwards, the problem is usually one of three things.
* the rom installed is corrupted
* you didn't wipe the necessary data before installing
* you tried flashing a rom that's incompatible with the recovery you are using (I'm betting this is most likely the case)
Try installing a different rom (preferably non-ICS) to see if that fixes the problem. Of so, check to see if you're using the latest version of CWM by Hashcode or install TWRP to run ICS based roms.
Any further questions regarding this matter should be redirected to the Q&A section.
[Edit:] For some reason I thought this was the thread for the Unbrick Utility. Regardless, the solution is still the same.
You are a GENIOUS!!!
Thanks a LOT!!!!!!!!!!
I finally managed to unbrick my KF and reroot it a few weeks ago only for amazon to come out with 6.2.3 or whatever the new version is and of course it unrooted it.
I have a MacBook Pro so I decided to use BreakDroid to reroot my KF.
Well in the process of doing so it installed CWM which has turned into a total monster.
Now my KF will only load to either the Yellow Triangle screen or the CWM-based Recovery menu screen. I keep trying to boot it out of that mode by using
cd /Users/macuser/android-sdk-macosx/tools
./fastboot-mac -i 0x1949 oem idme bootmode 5002
but that just seems to take me to the red CWM menu screen.
Does anybody know how I can get CWM off of my KF for GOOD?
I swear if I see that red menu or that yellow triangle again I'm going to throw it across the room.
Help a girl out?
To change to normal boot, use 4000 or use the following fast boot commands:
fastboot -i 0x1949 oem idme bootmode 4000
or
fastboot oem idme bootmode 4000
then fastboot reboot
Sent from my Amazon Kindle Fire using Tapatalk
Didn't Work
I tried that...it didn't work either. It just brought me back to that stupid yellow triangle.
Since you have cwm, restore your backup or flash your desirable ROM.
Sent from my Amazon Kindle Fire using Tapatalk
=D
You know I actually decided to do that on my own before I read your post and it totally worked! Thank you for giving me the advice though.
I am glad you got your KF working
Sent from my Amazon Kindle Fire using Tapatalk
I tried this but it didn't seem to work for me.
One problem is when I renamed the update to "update.zip" it doesnt show up as a file I can install in TWRP. However, when I actually .zip the update then it shows up.
I used install and it says "installing" with a progress bar, but when I reboot it goes right back into TWRP recovery mode.
My kindle is fully accessible through Kindle Fire Utility, but it will only stay in recovery mode, If I try to put it back into normal mode it gives a message "The system cannot find the drive specified".
I think at some point I deleted the system files using TWRP assuming I could just flash them back. I'm guessing I was wrong at this point.
Any help would be appreciated.
all u had to do, was tap reboot system on cwm. its not twrp, it ain't broken. no adb boot mode changes. just reboot lol
Sent from my HTC Glacier using xda premium
my problem is that when i used rom toolbox after flashing twrp recovery from hashcode (do all and dont flash the recovery only)for reset my tab into recovery. my tablet entered in a endless recovery, it charged but i could enter the os, then it was with few battery and i recharged it, then it had a few battery and i dont charged it, and now it dont boot, i charged it and nothing, i know that i can use fastboot but my device wasnt recognoized, so i think i will need the drivers. please help me
Kindle Fire HD and 2 First Aide Software - Noob (Simple) Version
persano said:
my problem is that when i used rom toolbox after flashing twrp recovery from hashcode (do all and dont flash the recovery only)for reset my tab into recovery. my tablet entered in a endless recovery, it charged but i could enter the os, then it was with few battery and i recharged it, then it had a few battery and i dont charged it, and now it dont boot, i charged it and nothing, i know that i can use fastboot but my device wasnt recognoized, so i think i will need the drivers. please help me
Click to expand...
Click to collapse
persano,
OK, so if I understand you correctly, you performed Hascodes steps to install TWRP Recovery and now your device loops the Recovery, correct?
If yes, plug in the Fastboot cable to the Kindle first then to your PC but first use our utility to install the drivers then proceed to recover the device.
Here is a link: http://forum.xda-developers.com/showthread.php?t=2096888
We have an option in the software to install the driver - do not use the backup or OTA disable feature, we are working on that function.
If you have trouble with that driver, which you should not but if you do, reply back and we will add instructions. Do Not worry, we will get you back online.
prokennexusa said:
persano,
OK, so if I understand you correctly, you performed Hascodes steps to install TWRP Recovery and now your device loops the Recovery, correct?
If yes, plug in the Fastboot cable to the Kindle first then to your PC but first use our utility to install the drivers then proceed to recover the device.
Here is a link: http://forum.xda-developers.com/showthread.php?t=2096888
We have an option in the software to install the driver - do not use the backup or OTA disable feature, we are working on that function.
If you have trouble with that driver, which you should not but if you do, reply back and we will add instructions. Do Not worry, we will get you back online.
Click to expand...
Click to collapse
the only option of drivers is the adb one
Kindle Bootloops After Installing TWRP On The Kindle
persano said:
the only option of drivers is the adb one
Click to expand...
Click to collapse
persano,
The ADB Driver and Fastboot driver are one of the same drivers, so having said this when you have a working ADB Driver, you will have a working Fastboot driver. Now, we have no idea what Hashcode did when developing TWRP on the Kindle, although he is a genius so I am sure he thought of everything.
Have you posted the issue in his Thread? He may have a way to recover TWRP directly since our Method will place you back to a stock Kindle.
prokennexusa said:
persano,
The ADB Driver and Fastboot driver are one of the same drivers, so having said this when you have a working ADB Driver, you will have a working Fastboot driver. Now, we have no idea what Hashcode did when developing TWRP on the Kindle, although he is a genius so I am sure he thought of everything.
Have you posted the issue in his Thread? He may have a way to recover TWRP directly since our Method will place you back to a stock Kindle.
Click to expand...
Click to collapse
yeah i posted in his thread
How To End A TWRP Bootloop
persano said:
yeah i posted in his thread
Click to expand...
Click to collapse
persano,
Any response yet? Here are some pointers that apply to TWRP on other Androids, so it should apply to your Kindle:
If you get stuck at a screen with a yellow triangle, run:
Code:
fastboot oem idme bootmode 4000 -i 0x1949
If your device is always booting TWRP run:
Code:
adb shell "idme bootmode 4000"
Step 1: If you still can't get out of booting TWRP (A Bootloop), first run:
Code:
adb shell "idme bootmode 4002"
Step 2: Reboot your device, then run:
Code:
adb shell "idme bootmode 4000"
Step 3: Reboot again and you should be out of your bootloop.
Please let us know if one of these solves your issue.
prokennexusa said:
persano,
Any response yet? Here are some pointers that apply to TWRP on other Androids, so it should apply to your Kindle:
If you get stuck at a screen with a yellow triangle, run:
Code:
fastboot oem idme bootmode 4000 -i 0x1949
If your device is always booting TWRP run:
Code:
adb shell "idme bootmode 4000"
Step 1: If you still can't get out of booting TWRP (A Bootloop), first run:
Code:
adb shell "idme bootmode 4002"
Step 2: Reboot your device, then run:
Code:
adb shell "idme bootmode 4000"
Step 3: Reboot again and you should be out of your bootloop.
Please let us know if one of these solves your issue.
Click to expand...
Click to collapse
but my tablet dont boot, it get out of battery after alot of bootloops
How To End A TWRP Bootloop
persano said:
but my tablet dont boot, it get out of battery after alot of bootloops
Click to expand...
Click to collapse
persano,
So at the moment you battery is dead or your Kindle is dead, period?
If the Kindle is dead and will no longer accept a charge, you will need to send it back to Amazon for replacement. If you are out of Warranty or concerned Amazon will not warranty the device, send it to our office and we will get you a new one. We know you are Argentina but if you send it vis UPS or FedEx we will get it quickly.
If you would like a new Kindle send us a PM and we will post our shipping address.
prokennexusa said:
persano,
So at the moment you battery is dead or your Kindle is dead, period?
If the Kindle is dead and will no longer accept a charge, you will need to send it back to Amazon for replacement. If you are out of Warranty or concerned Amazon will not warranty the device, send it to our office and we will get you a new one. We know you are Argentina but if you send it vis UPS or FedEx we will get it quickly.
If you would like a new Kindle send us a PM and we will post our shipping address.
Click to expand...
Click to collapse
thanks then i will see. i think hashcode is a killer developer xD
and how a new kinlde, what you will do with the old?
i bougth it from ebay, amazon will renplace it ?
How To Ship Th Kindle To Xerocomm, Inc.
persano said:
thanks then i will see. i think hashcode is a killer developer xD
and how a new kinlde, what you will do with the old?
i bougth it from ebay, amazon will renplace it ?
Click to expand...
Click to collapse
persano,
If you ship it to us, we will register the device to our business Amazon account, where we own 40 Kindles, then we will ask Amazon to replace it. The old Kindle will go back to Amazon for parts - we will take care of having the device swapped out for you. Be sure you De-register the device from your Amazon Account, if you did not register the device to Amazon better yet.
The only caveat is the Kindle need to be in excellent condition without signs of being dropped, otherwise Amazon will reject the replacement.
If Hashcode can not fix the problem, ship the Kindle (well packaged and insured) to us:
Xerocomm, Inc.
dba The Noob Series
Attn: Chris Bryant
1684 Northstar Drive
Petaluma, CA 94954-6603
USA
Main Phone: 707-774-5923
prokennexusa said:
persano,
If you ship it to us, we will register the device to our business Amazon account, where we own 40 Kindles, then we will ask Amazon to replace it. The old Kindle will go back to Amazon for parts - we will take care of having the device swapped out for you. Be sure you De-register the device from your Amazon Account, if you did not register the device to Amazon better yet.
The only caveat is the Kindle need to be in excellent condition without signs of being dropped, otherwise Amazon will reject the replacement.
If Hashcode can not fix the problem, ship the Kindle (well packaged and insured) to us:
Xerocomm, Inc.
dba The Noob Series
Attn: Chris Bryant
1684 Northstar Drive
Petaluma, CA 94954-6603
USA
Main Phone: 707-774-5923
Click to expand...
Click to collapse
in the box and with the usb?
its in exellent
II can add a bit to this discussion from what I gather in the bootloader / TWRP thread:
1. i believe that persano has only flashed the recovery.img and not the boot.img or the stack jump file to system. And then issued a "reboot recovery" in ROM toolbox which has probably set the bootmode to 3 or 5, i forget, but it will direct the stock bootloader to jump to recovery directly.
Unfortunately, without a boot.img (containing a 2nd bootloader) and a stack file to match, this ends with an unloadable recovery.img which will hang the device.
2. The solution (in any case) is to use a fastboot cable which will power the device regardless of battery charge and to enter fastboot mode. Which can be configured via the Android SDK install, and perhaps some reinstallation of USB drivers in the Windows device manager (should show "adb composite device").
Here you can flash back the stock recovery (and/or boot.img if needed) as well as reset the bootmode by entering:
fastboot -i 0x1949 oem idme bootmode 1
And all will be good as new.
Sent from my DROID RAZR HD using Tapatalk 2
Hashcode said:
II can add a bit to this discussion from what I gather in the bootloader / TWRP thread:
1. i believe that persano has only flashed the recovery.img and not the boot.img or the stack jump file to system. And then issued a "reboot recovery" in ROM toolbox which has probably set the bootmode to 3 or 5, i forget, but it will direct the stock bootloader to jump to recovery directly.
Unfortunately, without a boot.img (containing a 2nd bootloader) and a stack file to match, this ends with an unloadable recovery.img which will hang the device.
2. The solution (in any case) is to use a fastboot cable which will power the device regardless of battery charge and to enter fastboot mode. Which can be configured via the Android SDK install, and perhaps some reinstallation of USB drivers in the Windows device manager (should show "adb composite device").
Here you can flash back the stock recovery (and/or boot.img if needed) as well as reset the bootmode by entering:
fastboot -i 0x1949 oem idme bootmode 1
And all will be good as new.
Sent from my DROID RAZR HD using Tapatalk 2
Click to expand...
Click to collapse
but my tablet dont boot when i connect it
Hashcode said:
II can add a bit to this discussion from what I gather in the bootloader / TWRP thread:
1. i believe that persano has only flashed the recovery.img and not the boot.img or the stack jump file to system. And then issued a "reboot recovery" in ROM toolbox which has probably set the bootmode to 3 or 5, i forget, but it will direct the stock bootloader to jump to recovery directly.
Unfortunately, without a boot.img (containing a 2nd bootloader) and a stack file to match, this ends with an unloadable recovery.img which will hang the device.
2. The solution (in any case) is to use a fastboot cable which will power the device regardless of battery charge and to enter fastboot mode. Which can be configured via the Android SDK install, and perhaps some reinstallation of USB drivers in the Windows device manager (should show "adb composite device").
Here you can flash back the stock recovery (and/or boot.img if needed) as well as reset the bootmode by entering:
fastboot -i 0x1949 oem idme bootmode 1
And all will be good as new.
Sent from my DROID RAZR HD using Tapatalk 2
Click to expand...
Click to collapse
how to configure it in the sdk
persano said:
but my tablet dont boot when i connect it
Click to expand...
Click to collapse
With fastboot cable?
Maromi said:
With fastboot cable?
Click to expand...
Click to collapse
yeah
persano said:
how to configure it in the sdk
Click to expand...
Click to collapse
in the Android SDK manager
click tools
click manage add-on sites
click user defined sites
click new
paste this address
http://kindle-sdk.s3.amazonaws.com/addon.xml
Maromi said:
in the Android SDK manager
click tools
click manage add-on sites
click user defined sites
click new
paste this address
http://kindle-sdk.s3.amazonaws.com/addon.xml
Click to expand...
Click to collapse
and then
amazon will remplace it !!!!! yeah!!!!
i live in argentina but they will remplace it
How To Stop A Kindle Fire HD Bootloop
persano said:
in the box and with the usb?
its in exellent
Click to expand...
Click to collapse
persano,
No, just the tablet. First open a chat with Amazon, see if they will replace the device, if no, send it to us and we will have the device replaced.
If tried reinstalling the drivers and also using the toolkit. I choose not to flash a recovery, just temporary boot so I can install stuff. I tried using fastboot to boot twrp but all I get is a black screen. Seems like sometimes the driver changes. Never had this problem on 4.2
Sent from my Nexus 7 using Tapatalk 4
biggyk said:
If tried reinstalling the drivers and also using the toolkit. I choose not to flash a recovery, just temporary boot so I can install stuff. I tried using fastboot to boot twrp but all I get is a black screen. Seems like sometimes the driver changes. Never had this problem on 4.2
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Boot your Nexus to the bootloader by first powering down the phone then simultaneously press and hold the volume down and power buttons for 2 seconds. Once in the bootloader connect the USB cable from the Nexus to your computer. Open a command prompt in the folder where you have installed fastboot, type "fastboot devices", and press enter. If you see a deviceID listed, you will be able to flash TWRP with the command "fastboot flash recovery openrecovery-twrp-2.6.0.0-mako.img" (assuming you are installing TWRP v2.6.0.0); otherwise, you will need to reinstall the Nexus drivers.
^The op wants to boot the recovery, not flash it.
Google removed the "fastboot boot" command in the new 4.3 bootloader. The new way to do this is by using the following command:
Code:
fastboot -c "lge.kcal=0|0|0|x" boot recovery.img
Sent using xda-developers app
Chromium_ said:
^The op wants to boot the recovery, not flash it.
Google removed the "fastboot boot" command in the new 4.3 bootloader. The new way to do this is by using the following command:
Code:
fastboot -c "lge.kcal=0|0|0|x" boot recovery.img
Sent using xda-developers app
Click to expand...
Click to collapse
Thank you. Worked fine!!:victory: