Related
Even if you lose data, brick your device or/and throw it against the wall after reading this post
I am absolutely not responsible for anything you do to your android !
This procedure works on Linux (see NOTES below before).
1 - Ensure you have the latest android SDK installed on your computer, and that USB debugging is enabled on your device
2 - Backup your data with "adb backup":
adb backup -apk -shared -all -f backup.ab
(No warranty: You should also backup your sms (and paid application or application data) with something else.
Details and latest warnings here: http://forum.xda-developers.com/showthread.php?t=1420351)
3 - Restart in bootloader:
adb reboot bootloader
4 - Unlock the bootloader (everything will be erased, you need to confirm on your device)
fastboot oem unlock
5 - Restart, skip configuration steps, enable USB debugging again
6 - Restore your data with adb restore:
adb restore backup.ab
7 - Download the latest TWRP image on your computer, from the official TeamWin Recovery Project site: http://teamw.in/project/twrp2
8 - Download or push the latest CWM-superSU zipped package from eg http://download.chainfire.eu/282/SuperSU/
9 - Restart in bootloader:
adb reboot bootloader
10 - Boot TWRP, eg;
fastboot boot openrecovery-twrp-2.3.1.0-grouper.img
11 - Using TWRP, Install the CWM-superSU zipped package previously downloaded on your android.
12 - Reboot your device, you are set !
NOTES:
- If you need to re-root your system after a firmware update, restart at step 7 with USB debugging enabled.
- with Linux you need to:
* Run "sudo bash" first in the terminal window to enter administrator mode.
* Change to directory "android-sdk-linux/platform-tools" and prefix every command with ./
* If command "./adb devices" returns a "????? no permissions" error, restart adb server as root:
./adb kill-server
./adb start-server
Is this not the wrong forum ?
Sent from my Galaxy Nexus using xda premium
danishprakash said:
Is this not the wrong forum ?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Ditto.
Step 4 should read 'Unlock Bootloader.'
Is this not the injustice forum ?
Dispatched from my Collection Linkage using xda reward
this is good for those who have been holding out on root and don't want to lose everything. the first time i rooted i was hesistant because i lost everything. so nice post, and im sure it'll be useful to lots of people, who understand it
Um, so..
adb backup + Nexus 7 Rooting Guide
http://forum.xda-developers.com/showpost.php?p=29271179&postcount=218
on the walkthrough over in the gnex forums, users found out that you need to set a backup password in developer options, otherwise the backup would not work, does the n7 not need the password?
I just wanted to root, not problems...
My priority was to backup the stock partitions just in case - user data is a bonus i did not need..
Then I found out it was possible to start a recovery partition with "fastboot boot" while keeping every partitions untouched
Ideal to not mess up things with flashing an unsuitable or syphilitic version of a system partition downloaded I don't know where ...
I did not want to use any rootkit for the exact same reasons, plus i'm allergic to Windows...
Hi luc, don't bother he complaints - I reckon you're on the right sub-forum (Nexus 7 General : tips & tricks), and your tutorial is so clear, simple, and to the point. I got my Nexus 7 rooted pretty much straigh away.
I've sent my thanks to your posts. Much appreciated.
Just need a bit of editing - "fastboot oem unlock" should be "sudo fastboot oem unlock"
The same with "sudo fastboot boot openrecovery-twrp-2.3.1.0-grouper.img"
(without the sudo prefix, fastboot waits forever)
Now my Nexus 7 is rooted, and I can stick my 64 GB flashdisk to my Nexus 7, making its capacity 80 GB
Thanks again for sharing.
Unlocking the downloader wipes the device does it not?
sufehmi said:
Just need a bit of editing - "fastboot oem unlock" should be "sudo fastboot oem unlock"
The same with "sudo fastboot boot openrecovery-twrp-2.3.1.0-grouper.img"
(without the sudo prefix, fastboot waits forever)
Click to expand...
Click to collapse
I did not want to scare others users with linux stuff on top of page.
However linux users should read the NOTES for linux mentioned there and run "sudo bash"
Thanks for your return !
CJHolderUK said:
Unlocking the downloader wipes the device does it not?
Click to expand...
Click to collapse
You can backup before unlocking the bootloader, as described in step 2.
Would I be right in thinking this will only work using Linux? would it be possible if I ran Linux as a virtual machine in Microsoft Virtual PC? Sorry if it's a dumb question, I am rather new here.
OP - clean and nice write up, thanks.
shezzuk1 said:
Would I be right in thinking this will only work using Linux? would it be possible if I ran Linux as a virtual machine in Microsoft Virtual PC? Sorry if it's a dumb question, I am rather new here.
Click to expand...
Click to collapse
It will work from windows, just don't forget to install Android SDK. Start cmd as Admin and navigate to platform-tools
Code:
cd "c:\Program Files (x86)\Android\android-sdk\platform-tools"
All other commands will be the same and you don't need to care about Linux stuff at the end of OP post.
Don't forget that unlocking the bootloader wipes the internal SD card, too. That's part of the data partition. Read more here.
Hello guys,
I'm a new noob in the forum. I was following the thread about android on kindle fire hd7 and since this weekend (ty hashcode :good seems i can try the rom on my kindle device. Now... i'm totally noob in this kind of operation, there is something vital or important i have to know before i brick my kindle fire?? OR i can just follow the instruction, install bootloader and then loading the rom? There is a video or something more deep to read before try to install?? Thank you and thank you for your future answer,
Petar
PetarHolland said:
Hello guys,
I'm a new noob in the forum. I was following the thread about android on kindle fire hd7 and since this weekend (ty hashcode :good seems i can try the rom on my kindle device. Now... i'm totally noob in this kind of operation, there is something vital or important i have to know before i brick my kindle fire?? OR i can just follow the instruction, install bootloader and then loading the rom? There is a video or something more deep to read before try to install?? Thank you and thank you for your future answer,
Petar
Click to expand...
Click to collapse
If you haven't already, read this...
http://forum.xda-developers.com/showthread.php?t=2228534
...it will tell you what you need to know to avoid bricking your device, and how to restore it if needed.
Thanks, i will read this, then i'll post here if i still need some information The entire process seems to be very hard ^^
soupmagnet said:
If you haven't already, read this...
http://forum.xda-developers.com/showthread.php?t=2228534
...it will tell you what you need to know to avoid bricking your device, and how to restore it if needed.
Click to expand...
Click to collapse
I'm stoked to see the outcome of that great work of porting the ROM to our kindle fires 7''.
Congrats for that great effort!
I was following the instructions you've provided. Apparently, my situation is that i'm in the 2x2 cell.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Therefore, I have the ADB drivers installed but can not achieve to enter in fastboot mode. What should I do? Should l install android's SDK? Here I'm completely lost in how to proceed...
Thanks in advance
Root first, so head to the QEMU root thread in the Development forum. After that, install the 2nd-bootloader by Hashcode, I recommend you use the FireFlash app in the Themes and Apps forum, just download the files from Hashcode's thread, plug them in, hit flash, and hold Volume-Up when you see the orange Kindle logo, all the way until it turns blue, then release a few seconds after.
Recovery does take a minute to appear, so now you're into TWRP recovery, go ahead and reboot, then download the ROM from Hashcode's CM10.1 thread with the GApps. Transfer the .zip files (both of them, the ROM and the GApps) to the internal storage. Boot into recovery by shutting down, powering on, and hold Volume-Up, same deal. Once you're into TWRP, wipe system and factory reset. After that's done, flash the ROM and the GApps, and you're done. Reboot, and voila.
ed! said:
I'm stoked to see the outcome of that great work of porting the ROM to our kindle fires 7''.
Congrats for that great effort!
I was following the instructions you've provided. Apparently, my situation is that i'm in the 2x2 cell.
Therefore, I have the ADB drivers installed but can not achieve to enter in fastboot mode. What should I do? Should l install android's SDK? Here I'm completely lost in how to proceed...
Thanks in advance
Click to expand...
Click to collapse
Yes, you need to install Android SDK. What allows you to use fastboot is the fastboot.exe file in the /platform-tools folder after you install the SDK. There are many guides on YouTube to doing this.
Thanks for your very kind reply, seokhun
I'm a bit confused now. Do I still need fastboot commands and SDK for the method you suggested? I mean, the one with the app that flashes everything....
Sorry If i'm asking too many questions but as a noob, I'd like to be very cautious with the procedure. I'm still not familiar with the kindle's way. I wish I were with my Samsung Galaxy phone flashing custom roms
I forgot to mention, I was already rooted and have stock rom with bootloader 7.3.1
Indeed... The entire process is hard, i'm trying to organize the information. SO the step are:
-Fastboot
-Installing bootloader
-Cleaning the system/exporting img
-Installing the rom
-Wipe
-Reboot
android :victory:
Right?
Some questions:
I read about a special cable, i can't do the process with the standard miniusb cable?
I read about downgrade the firmware of my kindle... I have the 7.3.0.3 version, i need to downgrade before install the bootloader right?
ed! said:
Thanks for your very kind reply, seokhun
I'm a bit confused now. Do I still need fastboot commands and SDK for the method you suggested? I mean, the one with the app that flashes everything....
Sorry If i'm asking too many questions but as a noob, I'd like to be very cautious with the procedure. I'm still not familiar with the kindle's way. I wish I were with my Samsung Galaxy phone flashing custom roms
I forgot to mention, I was already rooted and have stock rom with bootloader 7.3.1
Click to expand...
Click to collapse
@PetarHolland
I'll try to answer your questions:
Factory cable
You do not absolutely need a factory cable to get into fastboot mode. When you have successfully rooted your device and have the adb drivers setup correctly, the command adb shell su -c "reboot bootloader" will do the trick. A factory cable can be considered an insurance: If push comes to shove and you brick your device, the factory cable will force the Kindle to boot up in fastboot mode.
Firmware downgrade
Just follow Hashcode's instructions given here: http://forum.xda-developers.com/showthread.php?t=2128848 (Step 4.5). Works like a charm.
Good luck to you!
Nice, that's really nice... So i just need to install the bootloader first following the instruction, then install the rom doing the 4.5 step. My doubt are cleared now, i will try tonight I hope with success
E_Zatopek said:
@PetarHolland
I'll try to answer your questions:
Factory cable
You do not absolutely need a factory cable to get into fastboot mode. When you have successfully rooted your device and have the adb drivers setup correctly, the command adb shell su -c "reboot bootloader" will do the trick. A factory cable can be considered an insurance: If push comes to shove and you brick your device, the factory cable will force the Kindle to boot up in fastboot mode.
Firmware downgrade
Just follow Hashcode's instructions given here: http://forum.xda-developers.com/showthread.php?t=2128848 (Step 4.5). Works like a charm.
Good luck to you!
Click to expand...
Click to collapse
PetarHolland said:
Nice, that's really nice... So i just need to install the bootloader first following the instruction, then install the rom doing the 4.5 step. My doubt are cleared now, i will try tonight I hope with success
Click to expand...
Click to collapse
Just a note of caution, as with all flashing of rom's. Whilst the fastboot cable is not 'required/essential' if you do mess it up , there is a potential that you 'could' brick, and depending to what extent your at, the cable becomes vital. In a nutshell if you can get your hands on a cable its recommeded as the earlier thread stated its a kind of insurance!
Good luck
kgyuszko
Thanks to all for your support. Everything worked out as expected and now I'm digging in the Recovery menu
There's one simple step I have to added to the ones written by Hashcode. That is, when trying to copy stack file to /data/local/tmp I had to change permissions to that folder in order to make the transfer happen. Originally was set to rwx-rwx-x and the adb push command failed.
Apart from this, as I said, everything flew as expected
Roughly, what I did was:
- Root the kindle 7.3.1 stock rom with Bin4ry_v28
- Install android SKD
- Follow step by step Hashcode's guide taking care to the permission change of /data/local/tmp till I reached the part of the fastboot commands.
- Active the fastboot with the following command and continue with the steps of the guide:
Code:
adb shell su -c "reboot bootloader"
Now the upcoming and logical question (i guess) is how do you buckup all you current apps and data before flashing a custom ROM?
Guys i stopped myself at the first step.. i followed the root instruction, i've done the file Path trick, and now i'm able to write ADB on my cmd terminal and see all the information, on the device setup i see the android composite adb interface BUT when i launch the RootQemu file this is the message i recive when i try to launch the app: You must install your device specific driver so that the device is visible to ADB. Any way to proceed??? thanks ( i'm running 7.3.1)
ed! said:
Thanks to all for your support. Everything worked out as expected and now I'm digging in the Recovery menu
There's one simple step I have to added to the ones written by Hashcode. That is, when trying to copy stack file to /data/local/tmp I had to change permissions to that folder in order to make the transfer happen. Originally was set to rwx-rwx-x and the adb push command failed.
Apart from this, as I said, everything flew as expected
Roughly, what I did was:
- Root the kindle 7.3.1 stock rom with Bin4ry_v28
- Install android SKD
- Follow step by step Hashcode's guide taking care to the permission change of /data/local/tmp till I reached the part of the fastboot commands.
- Active the fastboot with the following command and continue with the steps of the guide:
Code:
adb shell su -c "reboot bootloader"
Now the upcoming and logical question (i guess) is how do you buckup all you current apps and data before flashing a custom ROM?
Click to expand...
Click to collapse
from ondom
UPDATE:
i used the bin4ry v29 to root my kindle fire, i have the superuser folder on my app screen, so i think everythings goes ok. now following the hashcode instruction to get Bootloader, i'm stucked launching the fastboot mode:
i type in my cmd:
fastboot -i 0x1949 getvar product
I get the <waiting for device> screen
but when i connect my kindle, they start normally and no "product: Tate-XXX-XX" screen appear.
Where i'm wrong??? How can i launch the fastboot mode?
PetarHolland said:
Guys i stopped myself at the first step.. i followed the root instruction, i've done the file Path trick, and now i'm able to write ADB on my cmd terminal and see all the information, on the device setup i see the android composite adb interface BUT when i launch the RootQemu file this is the message i recive when i try to launch the app: You must install your device specific driver so that the device is visible to ADB. Any way to proceed??? thanks ( i'm running 7.3.1)
Click to expand...
Click to collapse
ed! said:
Thanks to all for your support. Everything worked out as expected and now I'm digging in the Recovery menu
There's one simple step I have to added to the ones written by Hashcode. That is, when trying to copy stack file to /data/local/tmp I had to change permissions to that folder in order to make the transfer happen. Originally was set to rwx-rwx-x and the adb push command failed.
Apart from this, as I said, everything flew as expected
Roughly, what I did was:
- Root the kindle 7.3.1 stock rom with Bin4ry_v28
- Install android SKD
- Follow step by step Hashcode's guide taking care to the permission change of /data/local/tmp till I reached the part of the fastboot commands.
- Active the fastboot with the following command and continue with the steps of the guide:
Code:
adb shell su -c "reboot bootloader"
Now the upcoming and logical question (i guess) is how do you buckup all you current apps and data before flashing a custom ROM?
Click to expand...
Click to collapse
Once you have Hashcode's TWRP build, simply backup using the Backup option from the recovery's main menu. If anything occurs when you flash ROMs, boot back into recovery and restore.
PetarHolland said:
UPDATE:
i used the bin4ry v29 to root my kindle fire, i have the superuser folder on my app screen, so i think everythings goes ok. now following the hashcode instruction to get Bootloader, i'm stucked launching the fastboot mode:
i type in my cmd:
fastboot -i 0x1949 getvar product
I get the <waiting for device> screen
but when i connect my kindle, they start normally and no "product: Tate-XXX-XX" screen appear.
Where i'm wrong??? How can i launch the fastboot mode?
Click to expand...
Click to collapse
Your fastboot isn't working properly. Did you make sure that your fastboot worked? In order for fastboot to work, you must have installed Android SDK. Videos are available on YouTube to help you do this. Once you correctly set up Android SDK, you will automatically have fastboot.
Otherwise, your ADB drivers aren't working. When you turn on the tablet, go to Settings > Security > ADB and turn it on. Then plug your tablet into the computer. Now your ADB drivers will be installed. This will allow you to use fastboot.
How can i test if my fastboot work? if i type fastboot on cmd i have the entire instruction of fastboot, so the command is recognised....
seokhun said:
Once you have Hashcode's TWRP build, simply backup using the Backup option from the recovery's main menu. If anything occurs when you flash ROMs, boot back into recovery and restore.
Your fastboot isn't working properly. Did you make sure that your fastboot worked? In order for fastboot to work, you must have installed Android SDK. Videos are available on YouTube to help you do this. Once you correctly set up Android SDK, you will automatically have fastboot.
Otherwise, your ADB drivers aren't working. When you turn on the tablet, go to Settings > Security > ADB and turn it on. Then plug your tablet into the computer. Now your ADB drivers will be installed. This will allow you to use fastboot.
Click to expand...
Click to collapse
fastboot -i 0x1949 getvar product
<waiting for device>
but when i plug my kindle fire and reboot, no fastboot, still <waiting for device>
I previously installed the sdk developer tool and changed the PATH adding the skd folder path to the windows shortcut for the cmd.
soupmagnet said:
fastboot -i 0x1949 getvar product
Click to expand...
Click to collapse
You don't reboot. When you enter that command and get the <waiting>, leave the tablet turned off and just plug it in. If your fastboot works, you'll be in fastboot mode.
Nope, i tryed every possibility, plugging turned off, plugging turned on and reboot, leaving to "waiting for device" for 2 hours, and nothing happened. soupmagnet suggested me to use the kindle first aid script to reinstall the adb drivers, seems the best option atm....
seokhun said:
You don't reboot. When you enter that command and get the <waiting>, leave the tablet turned off and just plug it in. If your fastboot works, you'll be in fastboot mode.
Click to expand...
Click to collapse
Cyanogenmod logo all the time
seokhun said:
Root first, so head to the QEMU root thread in the Development forum. After that, install the 2nd-bootloader by Hashcode, I recommend you use the FireFlash app in the Themes and Apps forum, just download the files from Hashcode's thread, plug them in, hit flash, and hold Volume-Up when you see the orange Kindle logo, all the way until it turns blue, then release a few seconds after.
Recovery does take a minute to appear, so now you're into TWRP recovery, go ahead and reboot, then download the ROM from Hashcode's CM10.1 thread with the GApps. Transfer the .zip files (both of them, the ROM and the GApps) to the internal storage. Boot into recovery by shutting down, powering on, and hold Volume-Up, same deal. Once you're into TWRP, wipe system and factory reset. After that's done, flash the ROM and the GApps, and you're done. Reboot, and voila.
Yes, you need to install Android SDK. What allows you to use fastboot is the fastboot.exe file in the /platform-tools folder after you install the SDK. There are many guides on YouTube to doing this.
Click to expand...
Click to collapse
I did exactly this and now i get the cyanogenmod logo all the time after reboot. been this way for 40 mins already. Can someone suggest what to do next?
When I normally plug my htc one into my laptop that is running win 8.1 64 bit. It shows that my phone is connected and opens files for me to view What is on my phone. When I'm in boot loader and I plug it in (I'm trying to unlock it to root) I hear the notification sound that the phone is connected to computer but the file box doesn't open showing me what's on the phone. Is this normal? If so, how do I open cmd prompt to type in OEM command and what should the command initially say before I type my oem command? Thanks for any help you can give.
dcm1200 said:
When I normally plug my htc one into my laptop that is running win 8.1 64 bit. It shows that my phone is connected and opens files for me to view What is on my phone. When I'm in boot loader and I plug it in (I'm trying to unlock it to root) I hear the notification sound that the phone is connected to computer but the file box doesn't open showing me what's on the phone. Is this normal? If so, how do I open cmd prompt to type in OEM command and what should the command initially say before I type my oem command? Thanks for any help you can give.
Click to expand...
Click to collapse
You will not see you data in bootloader mode. What is your bootloader version? You will not be able to send fastboot commands using windows 8.1 with hboot 1.44.
open the cmd prompt from your adb/fastboot.exe folder and type
Code:
fastboot devices
and see if the device is recognized by your computer
and go see those video guide here: http://forum.xda-developers.com/htc-one#root
Be sure to use the latest htc drivers and latest android sdk (abd/fastboot)
And again, you will not be able to use fastboot with a win8.1 computer if your bootloader is 1.44
dcm1200 said:
When I normally plug my htc one into my laptop that is running win 8.1 64 bit. It shows that my phone is connected and opens files for me to view What is on my phone. When I'm in boot loader and I plug it in (I'm trying to unlock it to root) I hear the notification sound that the phone is connected to computer but the file box doesn't open showing me what's on the phone. Is this normal? If so, how do I open cmd prompt to type in OEM command and what should the command initially say before I type my oem command? Thanks for any help you can give.
Click to expand...
Click to collapse
Sorry mate but I will not troubleshoot via PM because its too much confusing and other members can't help you if you send me pm. Keep posting here it will be much easier. Hope you understand
QUOTE=alray;50379334]Sorry mate but I will not troubleshoot via PM because its too much confusing and other members can't help you if you send me pm. Keep posting here it will be much easier. Hope you understand [/QUOTE
But after flashing twrp recovery and copying supersu to internal storage I erased cache in cms before going into recovery mode then unzipped supersu and rebooted phone. I opened super su and said that there is no binary file or that it is not working. I also dl'ed a root checker and it said that I'm not rooted. Any ideas on what to do now?
dcm1200 said:
QUOTE=alray;50379334]Sorry mate but I will not troubleshoot via PM because its too much confusing and other members can't help you if you send me pm. Keep posting here it will be much easier. Hope you understand [/QUOTE
But after flashing twrp recovery and copying supersu to internal storage I erased cache in cms before going into recovery mode then unzipped supersu and rebooted phone. I opened super su and said that there is no binary file or that it is not working. I also dl'ed a root checker and it said that I'm not rooted. Any ideas on what to do now?
Click to expand...
Click to collapse
install superSU.zip the same as you install a rom in recovery
clsA said:
install superSU.zip the same as you install a rom in recovery
Click to expand...
Click to collapse
Please pardon my ignorance but I'm new to this. How? Is it the same basic way that I flashed twrp to my phone?
I spent about 6 hours yesterday trying to root my Kindle Fire HD 7" tablet using various methods. I've searched numerous posts and tried several ways with no success.
I believe my ADB drivers are working properly because I am able to reboot the tablet from adb successfully. And in the Windows Device Manager it shows the "Android Composite ADB Interface" as my driver. But the command "adb reboot bootloader" just reboots back into the standard Home screen. And any fastboot command just gives me the "waiting for device" response.
I am on Version 7.4.8 of the firmware so I am trying to find a way to downgrade. I purchased it in November 2012 so it is the 2012 tablet. But every method I try just fails for one reason or another. So my question is, do I need a factory cable in order to get anywhere with this? Is it even doable with this version firmware?
Thank you in advance.
It is doable without a factory cable, the known rooting utilities people typically use are kindle fire first aid or binary's root. If you still can't get it to root, you can technically use a fastboot cable and kffa to restore it to a earlier is that os pre-rooted.
Sent from my Amazon Kindle Fire HD using Tapatalk
pastorbob62 said:
I spent about 6 hours yesterday trying to root my Kindle Fire HD 7" tablet using various methods. I've searched numerous posts and tried several ways with no success.
I believe my ADB drivers are working properly because I am able to reboot the tablet from adb successfully. And in the Windows Device Manager it shows the "Android Composite ADB Interface" as my driver. But the command "adb reboot bootloader" just reboots back into the standard Home screen. And any fastboot command just gives me the "waiting for device" response.
I am on Version 7.4.8 of the firmware so I am trying to find a way to downgrade. I purchased it in November 2012 so it is the 2012 tablet. But every method I try just fails for one reason or another. So my question is, do I need a factory cable in order to get anywhere with this? Is it even doable with this version firmware?
Thank you in advance.
Click to expand...
Click to collapse
First thing you need to do is download the SDK package and set the paths correctly. Here is a video guide https://www.youtube.com/watch?v=oaNM-lt_aHw
Once the paths are set then you go to where your tools folder is and hold shift and right click on your mouse and left click on "open command window here." Then type "adb devices" and enter. When you get a device number you will have proof your ADB is working correct. The fact you see it in your device manager is a pretty good sign though.
The command you are looking for is (must be rooted to use this command otherwise you do need a factory cord.)
adb shell su -c reboot bootloader
This is the command to check the whether fastboot is working
fastboot -i 0x1949 getvar product
This is the command to get you out of fastboot.
fastboot -i 0x1949 reboot
No fastboot commands will work until you download the SDK package and set the environment up. You should be able to get into the bootloader though.
LinearEquation said:
First thing you need to do is download the SDK package and set the paths correctly. Here is a video guide https://www.youtube.com/watch?v=oaNM-lt_aHw
Once the paths are set then you go to where your tools folder is and hold shift and right click on your mouse and left click on "open command window here." Then type "adb devices" and enter. When you get a device number you will have proof your ADB is working correct. The fact you see it in your device manager is a pretty good sign though.
The command you are looking for is (must be rooted to use this command otherwise you do need a factory cord.)
adb shell su -c reboot bootloader
This is the command to check the whether fastboot is working
fastboot -i 0x1949 getvar product
This is the command to get you out of fastboot.
fastboot -i 0x1949 reboot
No fastboot commands will work until you download the SDK package and set the environment up. You should be able to get into the bootloader though.
Click to expand...
Click to collapse
I appreciate your reply and information very much. However, I downloaded the SDK package and installed it over a year ago and have used Fastboot for three other devices numerous times. I used Fastboot with my Asus TF300T to flash recoveries, and return to Asus Stock on more occasions than I can count. I am currently running CROMBi-kk 20140323 on that same tablet. Just to be certain, I connected it just now as I am typing this and verified several Fastboot commands. I also have a Huawei U8800-51 and a Samsung S4 Mini Duo GT-I9192 and have used Fastboot commands with them as well.
So I don't think it is an issue with the driver not being installed correctly, or the SDK not being present unless it is a version specific issue. But the Samsung phone is much newer than the Kindle so I don't think it is that either.
So I guess that puts me at an impasse until I get a factory cable. Or I can just forget customizing the Kindle.
pastorbob62 said:
I appreciate your reply and information very much. However, I downloaded the SDK package and installed it over a year ago and have used Fastboot for three other devices numerous times. I used Fastboot with my Asus TF300T to flash recoveries, and return to Asus Stock on more occasions than I can count. I am currently running CROMBi-kk 20140323 on that same tablet. Just to be certain, I connected it just now as I am typing this and verified several Fastboot commands. I also have a Huawei U8800-51 and a Samsung S4 Mini Duo GT-I9192 and have used Fastboot commands with them as well.
So I don't think it is an issue with the driver not being installed correctly, or the SDK not being present unless it is a version specific issue. But the Samsung phone is much newer than the Kindle so I don't think it is that either.
So I guess that puts me at an impasse until I get a factory cable. Or I can just forget customizing the Kindle.
Click to expand...
Click to collapse
You said you were using simply adb reboot bootloader right? Did you try the command I suggested? "adb shell su -c reboot bootloader" because if everything is set up right then this should work. CD from the tools folder.
LinearEquation said:
You said you were using simply adb reboot bootloader right? Did you try the command I suggested? "adb shell su -c reboot bootloader" because if everything is set up right then this should work. CD from the tools folder.
Click to expand...
Click to collapse
Okay, got it working. Not sure what the problem was but I reinstalled SDK-Tools and Platform-Tools using the latest version of SDK. I was then able to use KFFA to root the Kindle and do a full backup. Not sure why it didn't work before the reinstall since I used ADB and Fastboot with my TF300T as recently as a week and a half ago while testing CROMBi-kk. Also verified they still worked with that tablet yesterday. Whatever the problem, it was specific to the Kindle.
One more question. Is it necessary to downgrade from 7.4.8 before installing a second bootloader and custom ROM? Or is that just a precautionary step because some people have had issues.
pastorbob62 said:
Okay, got it working. Not sure what the problem was but I reinstalled SDK-Tools and Platform-Tools using the latest version of SDK. I was then able to use KFFA to root the Kindle and do a full backup. Not sure why it didn't work before the reinstall since I used ADB and Fastboot with my TF300T as recently as a week and a half ago while testing CROMBi-kk. Also verified they still worked with that tablet yesterday. Whatever the problem, it was specific to the Kindle.
One more question. Is it necessary to downgrade from 7.4.8 before installing a second bootloader and custom ROM? Or is that just a precautionary step because some people have had issues.
Click to expand...
Click to collapse
Its kinda just a precautionary measure, to put it plainly, your kindle will bootloop into recovery if you do the process on 7.4.8, so unless you know how to use "Adb push" its suggested to put the rom and gapps onto the kindle ahead of time so it will be there when you start to bootloop into recovery. On another note, you do need to downgrade the bootloader though, if you use hashcodes method, please check the md5sum on the bootloader file before flashing it to avoid a hardbrick. If you used the fireflash method i wouldnt worry about it, just make sure you check off the downgrade bootloader button above or beside the red warning text.
I had these same issues. The device wouldn't boot into fastboot while it was <waiting for device>.
I did this.
1. Used Many Root Tool to gain root. http://forum.xda-developers.com/showthread.php?t=1886460
2. Placed the Rom and Gapps file on my sd card to be safe.
3. Used Anonymous.123's Tool up until the fastboot <waiting for device> malfunction. http://forum.xda-developers.com/showthread.php?t=2685414
4. Opened the Batch File for the Flasher Tool and copied and pasted the fastboot commands into a terminal with the Kindle in Fastboot. The only way I could get it in fastboot was "adb shell su -c reboot bootloader"
This will install the 4.2 bootloader so you don't have to flash back.
5. Profit 2nd Bootloader and TWRP
Good luck. You'll get it.
Sorry I Keep using the quote reply wrong. Havn't been on XDA in a while.
Okay, following Hashcode's procedure, I have successfully completed all steps up to flashing CM 10.2. TWRP works great and I made a backup from it. Not really necessary since I had backed up my Kindle three different ways and also copied all of my data to my PC as well.
But when I went to copy the TWRP backup to my PC for safekeeping I discovered that now I no longer have access to my Kindle from my PC's file explorer when I am booted into my Kindle. Prior to doing any of the steps here I could swap files back and forth without any problem. So how do I get that feature back??
I am running WIndows 8.1. This worked before I followed the procedures here. Also, when I pull files in adb where do they get stored??? Can't seem to find them.
Check the storage settings in CM you have to turn MTP storage in.
Sent from my Galaxy Nexus using xda app-developers app
Hi mates, please help.
I have just update my girlfriends HTC One M7.
It was a 4.2 Android version from ARHD. I didn't notice that I needed to update Recovery in order to run new ROMs and now is looping in HTC logos.
The problem is that Fastboot isn't working with Windows 8.1 (I've been hours trying different drivers).
ADB is working right, but I can not install RECOVERY.IMG throught recovery or sideload.
I was thinking in installing through sideload an old ROM that works with my Recovery but I can not find any.
¿Any other solution?
¿A factory reset will work?
Thanks,
I'm in a hurry, i'm leaving soon and i do not like to let her with a brick mobile.
SergiNS said:
Hi mates, please help.
I have just update my girlfriends HTC One M7.
It was a 4.2 Android version from ARHD. I didn't notice that I needed to update Recovery in order to run new ROMs and now is looping in HTC logos.
The problem is that Fastboot isn't working with Windows 8.1 (I've been hours trying different drivers).
ADB is working right, but I can not install RECOVERY.IMG throught recovery or sideload.
I was thinking in installing through sideload an old ROM that works with my Recovery but I can not find any.
¿Any other solution?
¿A factory reset will work?
Thanks,
I'm in a hurry, i'm leaving soon and i do not like to let her with a brick mobile.
Click to expand...
Click to collapse
Win 8.1 does not work with lower hboots. You should try a Win 7 computer or Linux on USB.
HOW TO USE LINUX FOR FASTBOOT & ADB VIA USB
This guide originally posted by @Danny201281
http://forum.xda-developers.com/showpost.php?p=54272479&postcount=219Linux is your friend; if your drivers are not working the chances of getting them working again without the phone booting are slim. But Linux doesn't need drivers to talk to your device.
Go here: http://www.pendrivelinux.com/ and download Universal USB Installer – Easy as 1 2 3
Then go here: http://releases.ubuntu.com/12.04/ and download Ubuntu from the first link at the top that says PC (Intel x86) desktop CD
Then use these files to create a bootable Linux USB drive with at least a 2 GB persistent file for storing files. You'll also probably need to change your boot settings in the computers bios to boot from USB.
MOVING YOUR FILES TO UBUNTU
Once booted you should be at a screen with options to "Try Ubuntu” or "Install Ubuntu". We don’t need to Install anything so just choose "Try Ubuntu" and the computer will boot to the Ubuntu Desktop (If you get a popup saying "system has encountered an error" or something similar just cancel and ignore it, it should have no effect on what we need to do as it is due to missing Linux OS updates we don’t need). On the left of the screen you'll see the Dock. Open the orange folder icon near the top this is the Home folder. It’s where we need to put any files we need to work with such as a rom.zip you want to push to the device or recovery.img files for flashing.
To get your files here is a simple drag and drop process. In the top left of the Home folder you'll see the drive structure of you pc under devices. Choose your PCs hard drive and Right-Click then" Open in a new window". Locate your .zip or .img files and drag them into the home folder. Now wait for the copy process to complete and rename them for easier typing later, e.g., rom.zip, firmware.zip or recovery.img etc.
USING ADB AND FASTBOOT
First you need to install adb fastboot; this is easy just 3 commands in the terminal. Thanks to Webupd8 team.
Code:
sudo add-apt-repository ppa:nilarimogard/webupd8
Code:
sudo apt-get update
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
Make sure your connected to the internet and press Ctrl+Alt+T to open the terminal then type or copy and paste the above commands one at a time waiting for each to complete their output. It may seem to have stopped at times but be patient when the prompt returns to normal enter the next command and when there all done you’re ready to use adb and fastboot.
Once you've moved all the files you need to the home folder that’s it you’re ready to go. Close everything down on the desktop (optional) and press Ctrl+Alt+T this will open the terminal now connect your phone with the USB cable. All fastboot commands need to have the "sudo" prefix added at the start, e.g.
fastboot flash recovery recovery.img becomes sudo fastboot flash recovery recovery.img
fastboot devices becomes sudo fastboot devices
However, adb should work basically the same as on windows. If you do have problems with normal adb commands adding “sudo” can help here as well.
If you get "no permissions ?????????" when trying to use adb, type:
Code:
killall adb
Disconnect the phone for a few seconds, then reconnect and type:
Code:
sudo adb devices
adb should now work as normal without the sudo prefix.
Click to expand...
Click to collapse
majmoz said:
Win 8.1 does not work with lower hboots. You should try a Win 7 computer or Linux on USB.
Click to expand...
Click to collapse
¿Isn't just easier to flash an old ROM that doesn't need TWRP 2.6 or higher?
I'm not used into Linux
Thanks a lot, please give any alternative you know.
SergiNS said:
¿Isn't just easier to flash an old ROM that doesn't need TWRP 2.6 or higher?
I'm not used into Linux
Thanks a lot, please give any alternative you know.
Click to expand...
Click to collapse
Yes, if you can find an older ROM that doesn't require an updated custom recovery. However, you wanted to update your girlfriends ROM and in order to do that you will need the newer custom recovery!
The other option, if you can find a newer RUU you could flash that and possibly Win 8.1 will work with the higher hboot.
Personally, Linux is not that difficult and if you follow the instructions posted you will not have an issue.
majmoz said:
Yes, if you can find an older ROM that doesn't require an updated custom recovery. However, you wanted to update your girlfriends ROM and in order to do that you will need the newer custom recovery!
The other option, if you can find a newer RUU you could flash that and possibly Win 8.1 will work with the higher hboot.
Personally, Linux is not that difficult and if you follow the instructions posted you will not have an issue.
Click to expand...
Click to collapse
I'm installing it on a pendrive right now.
Hope is easy.
Is taking time "Creating a persistent File"
As it seems, I can get files from HDD from Ubuntu isn't it?
Thanks
SergiNS said:
I'm installing it on a pendrive right now.
Hope is easy.
Is taking time "Creating a persistent File"
As it seems, I can get files from HDD from Ubuntu isn't it?
Thanks
Click to expand...
Click to collapse
Yes you will be able to access files on your pc's harddrive from the Linux pendrive. But it's better to copy them to the Linux home folder as in my guide before flashing. This is why you need the persistent file. It's like a Virtual Hard drive on your usb stick
Otherwise it will complicate flashing with long file paths needed for the adb and fastboot commands.
Just follow my mini guide and you'll be fine
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Danny201281 said:
Yes you will be able to access files on your pc's harddrive from the Linux pendrive. But it's better to copy them to the Linux home folder as in my guide before flashing. This is why you need the persistent file. It's like a Virtual Hard drive on your usb stick
Otherwise it will complicate flashing with long file paths needed for the adb and fastboot commands.
Just follow my mini guide and you'll be fine
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
Thanks a lot mate.
Right now is all done.
I will keep Ubuntu in my pendrive, it can help me in many ways.
Thanks for the guide and for the quick answers.
Always a pleasure to be in this forum.
SergiNS said:
Thanks a lot mate.
Right now is all done.
I will keep Ubuntu in my pendrive, it can help me in many ways.
Thanks for the guide and for the quick answers.
Always a pleasure to be in this forum.
Click to expand...
Click to collapse
Your welcome. Glad it got you out of trouble, Linux ain't so scary eh! [emoji12]
P.s no need to say thanks, there's a button for that sure majmoz would appreciate one or two :good:
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good: