Related
So I'm sending in my Kindle HD7 for a replacement, and I'd like to revert it back to stock. However, for some reason I can't get fastboot commands to work. It was working just fine the day before
I have root, version 7.3.0 stock ROM, and Hashcode's bootloader on my device. ADB works fine. Plugging in the factory cable boots the HD7 into fastboot mode, but commands aren't going through.
Things I've tried or attempted (along with searching the forums :silly:
- Reinstall Kindle drivers
- Reinstalled SDK and such
- Attempted to use SoupKit (though I gave up since I had a hard time adjusting with the Ubuntu interface)
- Kindle Restore Tool (hangs on waiting device)
- KFFirstAide (hangs on waiting device)
- Manual flashing via command prompt (hangs on waiting device)
I know this problem usually comes about because the drivers aren't correctly installed. I did notice that when in fastboot mode, device manager shows a triangle for "'tate-pvt-08". At this point however, I have no idea how to approach this problem.
Seems like I am either left with getting fastboot to work so I can flash to stock, or somehow use TWRP to flash back to stock (but it won't wipe out the 2nd bootloader?).
Any help is much appreciated!
Well I was able to restore to stock using TWRP.
All I had to do was download the 7.2.3 bin file from Amazon and flash it using TWRP. Doing this removed bootloader, twrp, root, as well as restored the device to stock.
It was an obvious solution...just took me a while to realize it lol
I do still wonder what was happening with my fastboot drivers/access though...
Closed as per OP request.
MD
HI,
I am sorry to bother the xdadevelopers community but I have tried to root the KIndle Fire HD 7" I offered to my mom for her birthday a week ago and i can't work around a problem :'(
I successfully installed Team Win Recovery Project. But anytime I boot i get into recovey (even when not pressing any button).
I hace searched the web for the last 3 days but any of the solutions have worked so far:
- I have tried to use adb shell "idme bootmode 4000" buti get /sbin/sh: idme not found
- I have tried adb shell nbmode but with the same result
- The rest of the solutions were for linux users.
So the question is ... what to do from here ?
Thank you very very much for any sugestion
Greetings from Bordeaux, France
Aaron Belle
Well, if you can get into recovery, that's a good thing.
I had this problem a couple of days ago. I had tried to revert from Chameleon OS back to the stock OS by flashing Haschode's stock OS zip, which resulted in the issue you described. I fixed it by restoring from a back up of ChaOS o had made, and it got me out of TWRP.
You could try re-flashing Hashcode's stock OS (it comes pre-rooted). It can be found here: http://forum.xda-developers.com/showthread.php?t=2218475
To move it on to your SD card, go to "Advanced" in TWRP and select "ADB Sideload," or something to that effect. Then from your PC, use a command window and enter "adb sideload name\of\zip.zip"
I don't remember if you have to wipe anything or not before you flash it
Hope this helped
>>Sent from my homebuilt TARDIS running Android 4.3... Or maybe it's a rooted Kindle Fire HD running ChameleonOS
Aaron Belle said:
HI,
I am sorry to bother the xdadevelopers community but I have tried to root the KIndle Fire HD 7" I offered to my mom for her birthday a week ago and i can't work around a problem :'(
I successfully installed Team Win Recovery Project. But anytime I boot i get into recovey (even when not pressing any button).
I hace searched the web for the last 3 days but any of the solutions have worked so far:
- I have tried to use adb shell "idme bootmode 4000" buti get /sbin/sh: idme not found
- I have tried adb shell nbmode but with the same result
- The rest of the solutions were for linux users.
So the question is ... what to do from here ?
Thank you very very much for any sugestion
Greetings from Bordeaux, France
Aaron Belle
Click to expand...
Click to collapse
Lol same thing happened to me when I flashed TWRP and 2nd BL. So basically, your in a boot loop. Don't worry you didn't do anything wrong, its just that the stock Kindle OS now hates us because we modified something. So here's what's gonna need to be done. You have TWRP, your all set to flash anything you want! But, you have no custom rom in there correct? My same mistake. Those are all easy fixes, the problem is playing with the KFHD7 drivers on your computer to detect your device 100% while its connected and on TWRP. I can't remember how I got mine to detect it, if I'm not mistaking I unisntalled ALL associated drivers, then reinstalled the ones provided for the rooting process WITH THE DEVICE STILL CONNECTED, then manually updating the driver to those installed drivers in C:/Program Files/Amazon/Kindle Fire. Once its installed, you would need to check by opening a command prompt with ADB, then check for devices by typing "ADB getdevices" if I'm not mistaking and see if some serial numbers show up. Then push the files thru ADB. If you wanna cheat your way thru ADB cause you don't know how to use it properly, do what I used to do. Download the Nexus 7 toolkit, install it, go to the folder where installed and create a shortcut for "tkmain.exe" to your desktop. Then open that and a green text command looking menu is in your view. If serials appear on the top, device is detected thru TWRP. If not keep playing with installing the drivers while in TWRP and refresh the green menu by using option 27 (type 27, then hit enter). Once those serials show up, download the custom ROM you want your mom to have. I recommend CM10.1 as its a small file, stabler than CM10.2, and its basically jellybean. Remember the folder where the Nexus 7 Toolkit was installed, where I first mentioned to make a shortcut for tkmain? Go back to that folder and look for a folder called "put files to push here". Throw the ROM there. Rename the ROM something short and with few or no symbols. When that's done, your ready to push it. Go to the wonderful green menu thingy, type 13 and hit enter. Then it will have two options. Type 2, hit enter. It will ask if your using an insecure bla bla bla. Type yes, hit enter. Then it should show the name of the ROM you threw in the folder, type it out exactly as spelled, hit enter. Push to /sdcard/. Some crap will appear and say "remount failed: Success" ignore that, don't panic, that's good. For a while nothing will show, but afterwards words should appear confirming the push, and Two last questions your gonna type no to. Now your ready to bring moms new device back to life! If you know how to flash a rom, do it. If not, swipe to wipe dalvik cache in Wipe menu, go back, Install > search SD card for your file and flash. Tada! You should see CM logo after the blue Kindle Fire logo and wait til the screen dims more or less, that means your a few seconds away from getting to touch. Remember to start it up, then flash GAPPS so mom can have Google Play, I'm sure she's gonna love Candy Crush Saga as mine does.
Sent from my Amazon Kindle Fire HD using xda app-developers app
May uestnl
Hi,
I have the same problem as AAron Belle, I think:
I followed the
"[REF] Installing Kindle Fire HD 7" 2nd-Bootloader + TWRP Complete Tutorial" till step 3.
I wanted to stop at step3 after installing 2nd bootloader and TWRP, without installing any custom ROMS.
I succeeded in the sense I don't have any red screen and the Kindle Fire HD 7 boots in TWRP (Screen Kindle fire in orange, then in blue, then TWRP).
But I can't find a way to boot anymore in the stock system (amazon).
I try to use a factory cable, but without success.
I would like to keep the 2nd bootloader and TWRP that I just installed, and as a first step use them in the amazon environnment.
Is there something I can do (not too complicated, I'm a noob!) ?
Thank you in advance,
Jeanphi
You can use "adb sideload" or "adb push" from a command prompt while plugged into your kindle in twrp and put a new ROM on it, like stock amazon, kinology, cm 10.1 or 10.2, etc.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
jeanphi506 said:
Hi,
I have the same problem as AAron Belle, I think:
I followed the
"[REF] Installing Kindle Fire HD 7" 2nd-Bootloader + TWRP Complete Tutorial" till step 3.
I wanted to stop at step3 after installing 2nd bootloader and TWRP, without installing any custom ROMS.
I succeeded in the sense I don't have any red screen and the Kindle Fire HD 7 boots in TWRP (Screen Kindle fire in orange, then in blue, then TWRP).
But I can't find a way to boot anymore in the stock system (amazon).
I try to use a factory cable, but without success.
I would like to keep the 2nd bootloader and TWRP that I just installed, and as a first step use them in the amazon environnment.
Is there something I can do (not too complicated, I'm a noob!) ?
Thank you in advance,
Jeanphi
Click to expand...
Click to collapse
Try the solution I mentioned above you. I'm no rocket scientist, or an android expert, just picked up a thing or two from experience. If I can do it you can as well. That's why I mentioned the toolkit I used. It may be for the Nexus 7 but it does the same adb commands used for all androids for you. That way if your not an adb expert you can use that. As I said, your first goal is to get your computer to properly detect the device while in TWRP, your stock kindle OS is just doing what it does best when simple modifications are done.
Lost access to stock amazon
stunts513 said:
You can use "adb sideload" or "adb push" from a command prompt while plugged into your kindle in twrp and put a new ROM on it, like stock amazon, kinology, cm 10.1 or 10.2, etc.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Thank you for the answer.
If I put a new ROM containing stock amazon, will I have still on the Kindle the 2nd bootloader and TWRP ?
Will my Kindle still be rooted ?
Jeanphi
jeanphi506 said:
Thank you for the answer.
If I put a new ROM containing stock amazon, will I have still on the Kindle the 2nd bootloader and TWRP ?
Will my Kindle still be rooted ?
Jeanphi
Click to expand...
Click to collapse
Depends on if the stock ROM is rooted, although usually, the answer is yes since messing around with things like overclocking and so on is always one of the reasons people seek to achieve root. If your going to flash this stock ROM, obviously only possible thru TWRP so yes you'll still have TWRP + 2nd BL. If your going to do the headachey fastboot restore, (not recommended at this point) then no. I've never gotten ADB sideload working, but either way I prefer pushing a rom to the internal SD and just installing.
How to get to the original OS after installing TWRP.
Crossvxm said:
Depends on if the stock ROM is rooted, although usually, the answer is yes since messing around with things like overclocking and so on is always one of the reasons people seek to achieve root. If your going to flash this stock ROM, obviously only possible thru TWRP so yes you'll still have TWRP + 2nd BL. If your going to do the headachey fastboot restore, (not recommended at this point) then no. I've never gotten ADB sideload working, but either way I prefer pushing a rom to the internal SD and just installing.
Click to expand...
Click to collapse
Thank you for answers. I think I will my first attempt to flash a Rom, through TWRP.
I will use this following link from Hashcode
"This flash .zip file contains the Amazon OS 7.4.3 update + root/Superuser.apk and should have OTAs disabled. You can use this to revert back to the Amazon OS should you need to for any reason.
Download Information for OS 7.4.3:
http://goo.im/devs/Hashcode/tate/kfh...n-os-7.4.3.zip
md5sum: 45e687e8e85975348f81f5cbfc8358ac"
Nevertheless, before doing that I might try to understand and use your first answer, as my Amazon 7.4.6 must still be on the system and this is just a question of access to it.
Jeanphi
jeanphi506 said:
Thank you for answers. I think I will my first attempt to flash a Rom, through TWRP.
I will use this following link from Hashcode
"This flash .zip file contains the Amazon OS 7.4.3 update + root/Superuser.apk and should have OTAs disabled. You can use this to revert back to the Amazon OS should you need to for any reason.
Download Information for OS 7.4.3:
http://goo.im/devs/Hashcode/tate/kfh...n-os-7.4.3.zip
md5sum: 45e687e8e85975348f81f5cbfc8358ac"
Nevertheless, before doing that I might try to understand and use your first answer, as my Amazon 7.4.6 must still be on the system and this is just a question of access to it.
Jeanphi
Click to expand...
Click to collapse
Once you flash any, there is no recovering the last stock you had, in this case, 7.4.6. This is lost for all of us. Now I haven't yet researched if there is a way to completely revert back to stock (as in removing the TWRP, 2nd boot loader and any other mods), but if there were, that's the way to go back to 7.4.6. However, no matter what ROM you toss on your device, any objects you may have had saved to your SD are still found as long as you don't delete em thru twrp. Remember before tossing in a rom, in the Wipe section, just swipe to factory reset, then go back and Install the zip from your storage.
Reinstalling stock OS
Crossvxm said:
Once you flash any, there is no recovering the last stock you had, in this case, 7.4.6. This is lost for all of us. Now I haven't yet researched if there is a way to completely revert back to stock (as in removing the TWRP, 2nd boot loader and any other mods), but if there were, that's the way to go back to 7.4.6. However, no matter what ROM you toss on your device, any objects you may have had saved to your SD are still found as long as you don't delete em thru twrp. Remember before tossing in a rom, in the Wipe section, just swipe to factory reset, then go back and Install the zip from your storage.
Click to expand...
Click to collapse
Coming back to give you some news.
I was not able to use the following link, as it was not on my Kindle and I was not able to have the kindle recognized by the computer.
"This flash .zip file contains the Amazon OS 7.4.3 update + root/Superuser.apk and should have OTAs disabled. You can use this to revert back to the Amazon OS should you need to for any reason."
I decided to use he backup I made and I used the following command, with the factory cable:
fastboot -i 0x1949 flash boot stock-boot.img
fastboot -i 0x1949 flash recovery stock-recovery.img
fastboot -i 0x1949 flash system stock-system.img
fastboot -i 0x1949 reboot
It worked and I have a working device, but without TWRP, 2nd boot loader.
I suppose I could have flashed directly the Amazon OS System mentionned earlier, but I was not exactly sure which command to use.
So, I will to try again to install TWRP, 2nd bootloader.
Thank you very much for your help. I will read again your answers to try to use them in the future.
Jeanphi
Completely fixed! Thanks!!
Download the Nexus 7 toolkit said:
I cant tell you how much of a life saver this was....this works 100% !! Just follow his instructions to a tee and this will save a lot of time and effort trying to get our TWRP loop!
Click to expand...
Click to collapse
Dear members of XDA,
first of all, sorry if this question already has been asked, but for some reason the search tool wouldn't work for me tonight.
Yesterday I succesfully installed CyanogenMod on a friend's 1st gen Kindle, and it was pretty easy - make sure that the drivers are ok, install TWRP, copy rom, wipe, install, done.
My Kindle 7' HD is rooted, and very modified, but I didn't want to try to mess with roms because I didn't had a factory cable. Well, I got one now, so the time has come.
I've checked Hashtag's post about the 2nd bootloader, and altought it is very helpful, I'm not sure if I'm ready to do all that stuff manually.
So, my question is this:
The KFFA has an option to install the 2nd bootloader + TWRP (option 39), and it itself states that it's the same process that can be found on Hashtag's post. Let's say I run that option, and all that is installed - what next? I just copy the rom and gapps to my device, use TWRP to wipe the stock rom, and install the new one? Just like that?
Any help will be much appreciated.
Thanks in advance, and best regards -
I suggest putting the ROM onto the kindle ahead of time along with its corresponding gapps, the latest is tends to boot loop into twrp after you flash second boot loader and twrp. You can still push them to the device even if that happens, but it tends to be more inconvenient.
Sent from my Amazon Kindle Fire HD using xda app-developers app
Well, I managed to install TWRP without breaking anything (altought not with KFFA but with FireFlash). I copied the CM rom and gapps, and wiped the stock OS... Only to find that I copied the wrong rom (I used the otter2 project, not the one modified by Hashcode).
No big deal, I tought, let's just copy the other rom and install it. The fact is that there is no way to make my computer recognize my kindle now. I have the latest version of ADB installed, I can get to TWRP screen without problems, but it always has a yellow marker on the device manager, and when I tipe "adb devices", nothing is listed.
Any tips?
Reinstalled some drivers, now the Kindle appears when I input "adb devices", even if it appears as an "android phone" on the device manager (without any yellow markers).
I can access TWRP and fastboot via the factory cable, but don't know how to continue from there. I want to copy Hashcode's ROM in order to flash it, but cannot find a way. I've read somewhere that it has to be sideloaded, I tried that before reinstalling the drivers, and it didn't work. Now I cannot find that procedure again.
In a 1st gen kindle I remember I could just transfer files via normal folders on windows, as long as I mount it using TWRP. Here on mine, even if I use TWRP's option to mount, nothing happens.
Solved!
Used this guide:
http://forum.xda-developers.com/showthread.php?t=2459498
Thanks once again, mr. Stunts!
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it. Nobody mentioned anything about it completely wiping the phone, including the internal SD card. I set most of the stuff back up again but realized that it was suffering from the bug on the old radio version that causes it to lose LTE randomly.
I went and rebooted into TWRP to try and flash it, and TWRP showed a completely empty sdcard partition and said it could not mount '/data'. I enabled "require pattern to boot," thinking it may not have known to decrypt the partition without that, and now I can't get into TWRP at all. I tried disabling the "require pattern to boot" option again but no luck. It shows the "Google" logo for about 5 seconds, then the blue "TEAMWIN" logo for about 3 seconds, then reboots to the "Google" logo and proceeds to boot normally. I should note that I have CM12.1 installed, and the latest TWRP. I've tried reflashing TWRP and that didn't help; I also did "fastboot format cache" and then "fastboot flash cache cache.img" using the stock factory cache.img. I got the radio flashed using fastboot, but I'd really like to have a working recovery.
briman0094 said:
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it. Nobody mentioned anything about it completely wiping the phone, including the internal SD card. I set most of the stuff back up again but realized that it was suffering from the bug on the old radio version that causes it to lose LTE randomly.
I went and rebooted into TWRP to try and flash it, and TWRP showed a completely empty sdcard partition and said it could not mount '/data'. I enabled "require pattern to boot," thinking it may not have known to decrypt the partition without that, and now I can't get into TWRP at all. I tried disabling the "require pattern to boot" option again but no luck. It shows the "Google" logo for about 5 seconds, then the blue "TEAMWIN" logo for about 3 seconds, then reboots to the "Google" logo and proceeds to boot normally. I should note that I have CM12.1 installed, and the latest TWRP. I've tried reflashing TWRP and that didn't help; I also did "fastboot format cache" and then "fastboot flash cache cache.img" using the stock factory cache.img. I got the radio flashed using fastboot, but I'd really like to have a working recovery.
Click to expand...
Click to collapse
no working recovery with a locked bootloader, sorry. if the bootloader is locked, you cant flash anything. its locked. to flash things, you need an unlocked bootloader. its like locking a door, but expecting it to open magically when you walk up to it.
simms22 said:
no working recovery with a locked bootloader, sorry. if the bootloader is locked, you cant flash anything. its locked. to flash things, you need an unlocked bootloader. its like locking a door, but expecting it to open magically when you walk up to it.
Click to expand...
Click to collapse
I forgot to mention that I re-unlocked the bootloader. I can also boot the OS so I'd be able to enable OEM unlock again if needed.
briman0094 said:
I forgot to mention that I re-unlocked the bootloader. I can also boot the OS so I'd be able to enable OEM unlock again if needed.
Click to expand...
Click to collapse
important thing to forget to mention
So what happened when you reflashed the lasted version of twrp for your device after verifying the downloads md5?
simms22 said:
important thing to forget to mention
Click to expand...
Click to collapse
I guess I assumed that when I said "continues to boot normally" people would assume I could re-enable "OEM Unlock" if needed
scryan said:
So what happened when you reflashed the lasted version of twrp for your device after verifying the downloads md5?
Click to expand...
Click to collapse
All the console output indicates success, and it boots to the initial "TEAMWIN" logo for a few seconds and reboots.
No Recovery Similiar issue
briman0094 said:
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it. Nobody mentioned anything about it completely wiping the phone, including the internal SD card. I set most of the stuff back up again but realized that it was suffering from the bug on the old radio version that causes it to lose LTE randomly.
I went and rebooted into TWRP to try and flash it, and TWRP showed a completely empty sdcard partition and said it could not mount '/data'. I enabled "require pattern to boot," thinking it may not have known to decrypt the partition without that, and now I can't get into TWRP at all. I tried disabling the "require pattern to boot" option again but no luck. It shows the "Google" logo for about 5 seconds, then the blue "TEAMWIN" logo for about 3 seconds, then reboots to the "Google" logo and proceeds to boot normally. I should note that I have CM12.1 installed, and the latest TWRP. I've tried reflashing TWRP and that didn't help; I also did "fastboot format cache" and then "fastboot flash cache cache.img" using the stock factory cache.img. I got the radio flashed using fastboot, but I'd really like to have a working recovery.
Click to expand...
Click to collapse
Briman, I seem to have a similar issue on my and wife's Google Nexus 6s. I unlocked and rooted using Wug Tool Kit I used in years past with seamless success. To confirm root CM 12.1 I can get into bootloader, Teamwin. From there I am to flash the Superuser, Busybox and TWRP zips under SD\iReady to Flash\Rootfiles..... Only I am not given an option on the menu? I am struggling with using the command prompt and proper paths from SDK Tools so that is not an option at this moment. I see a File Manager that shows this path but am hesitant to use it as I have READ this could cause damage ( brick) to the system. Watching your thread for answers or possibilities. I know the senior members as Simm22 dislike tool kits and so do I. I am simply trying to grow and learn.
ray6279 said:
Briman, I seem to have a similar issue on my and wife's Google Nexus 6s. I unlocked and rooted using Wug Tool Kit I used in years past with seamless success. To confirm root CM 12.1 I can get into bootloader, Teamwin. From there I am to flash the Superuser, Busybox and TWRP zips under SD\iReady to Flash\Rootfiles..... Only I am not given an option on the menu? I am struggling with using the command prompt and proper paths from SDK Tools so that is not an option at this moment. I see a File Manager that shows this path but am hesitant to use it as I have READ this could cause damage ( brick) to the system. Watching your thread for answers or possibilities. I know the senior members as Simm22 dislike tool kits and so do I. I am simply trying to grow and learn.
Click to expand...
Click to collapse
na, toolkits work fine. sure, they occasionally do mess up, but its not very ofver. i generally like ut when noobies do the rooting the correct way the first time, that way they can learn some basic things about how everything works. then, they can yse toolkits all they
btw, teamwin isnt your bootloader, its your recovery. team win = twrp. now all you need to do is download the latest supersu and flash it via your recovery, and the you can install a busybox app from tbe play store, and use it to unstall .
briman0094 said:
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it.
Click to expand...
Click to collapse
Saw that bit of advice where? I can't think of a single thing re-locking the bootloader would fix.
nhizzat said:
Saw that bit of advice where? I can't think of a single thing re-locking the bootloader would fix.
Click to expand...
Click to collapse
A screenshot of an e-mail from a Google employee regarding Android Pay and SafetyNet.
50% JOY No Fastboot?
simms22 said:
na, toolkits work fine. sure, they occasionally do mess up, but its not very ofver. i generally like ut when noobies do the rooting the correct way the first time, that way they can learn some basic things about how everything works. then, they can yse toolkits all they
btw, teamwin isnt your bootloader, its your recovery. team win = twrp. now all you need to do is download the latest supersu and flash it via your recovery, and the you can install a busybox app from tbe play store, and use it to unstall .
Click to expand...
Click to collapse
I followed your directions while working on my Nexus6 phone. Was able to access bootloader then install iReady files. Worked perfectly and phone loaded SUPERUSER, BUSYBOX & PERM RECOVERY. Not so much on wife's Nexus 6. I get thru UNLOCK & ROOT w/custom recovery on the Wug Fresh Tool Kit. At RECOVERY menu pulls up SD - Up one level. No option is allowed to continue on and load the three mentioned packages. I then able to reboot to system. Does it appear I am bootloading but not fastbooting? Will try and insert images.
ray6279 said:
I followed your directions while working on my Nexus6 phone. Was able to access bootloader then install iReady files. Worked perfectly and phone loaded SUPERUSER, BUSYBOX & PERM RECOVERY. Not so much on wife's Nexus 6. I get thru UNLOCK & ROOT w/custom recovery on the Wug Fresh Tool Kit. At RECOVERY menu pulls up SD - Up one level. No option is allowed to continue on and load the three mentioned packages. I then able to reboot to system. Does it appear I am bootloading but not fastbooting? Will try and insert images.
Click to expand...
Click to collapse
one question.. what is perm recovery?? the only recovery that works on the n6 is twrp recovery.
and when you are in her recovery, is it showing you the right location where the files should be? if nit, you csn change the lication.
Simm & Others. Thank you for your good words and suggestions. It would be easier for me to list what I did not attempt rather than what I did try. . I tried nearly most functions in the Wug Fresh ( by Harold) v2.0.5 after failing to find the correct command prompt to use ADB. What happened is an odditity. Mind you, I've been on these two Nexus 6 phones for 4-6hours a day for about ten days! Day later, Happened to be waiting for wife in parking lot and picked up phone and pressed SuperUser. Viola! It went into TWRP and gave me an RECOVERY option. On impluse, I flashed TWRP and Superuser zips. It took and processed. however, the best part of this is the hands on learning experience of booting, flashing, wiping, language, terms, SDK, Android and more. Once I figure out my path problem on my windows based PC to loading ABD commands I am continuing my self study of Android and App development. How do I get the packages out of the SDK Tool Kit to folders in PC? Thanks all.
ray6279 said:
Simm & Others. Thank you for your good words and suggestions. It would be easier for me to list what I did not attempt rather than what I did try. . I tried nearly most functions in the Wug Fresh ( by Harold) v2.0.5 after failing to find the correct command prompt to use ADB. What happened is an odditity. Mind you, I've been on these two Nexus 6 phones for 4-6hours a day for about ten days! Day later, Happened to be waiting for wife in parking lot and picked up phone and pressed SuperUser. Viola! It went into TWRP and gave me an RECOVERY option. On impluse, I flashed TWRP and Superuser zips. It took and processed. however, the best part of this is the hands on learning experience of booting, flashing, wiping, language, terms, SDK, Android and more. Once I figure out my path problem on my windows based PC to loading ABD commands I am continuing my self study of Android and App development. How do I get the packages out of the SDK Tool Kit to folders in PC? Thanks all.
Click to expand...
Click to collapse
your welcome, but you are still off in one bit of fact. you use fastboot, not adb, to flash a recovery(and system.img)
edit.. you can use apps like flashify to flash recovery, if you have root already.
So BOOTLOADER is the USB connection between the device and PC. FASTBOOT is the process via we make changes in the device via the PC. ADB is the device language via which we communicate. So do I still need to flash a system recovery image? Flashify App? I already went thru install>iready to flash> superuser (version)>busybox>flash>reboot>system. I'm going cross eyed from reading. The wiping part worries me as I fear formatting or deleting essential data.
ray6279 said:
So BOOTLOADER is the USB connection between the device and PC. FASTBOOT is the process via we make changes in the device via the PC. ADB is the device language via which we communicate. So do I still need to flash a system recovery image? Flashify App? I already went thru install>iready to flash> superuser (version)>busybox>flash>reboot>system. I'm going cross eyed from reading. The wiping part worries me as I fear formatting or deleting essential data.
Click to expand...
Click to collapse
ok, when wiping, dont do the first option wipe, itll wipe your whole phone clean. you need to select the advanced options and pick what you want wiped. fastboot is the way to unlock your bootloader, or flash a recovery. also, you use it to flash a system.img or any part of it.
adb is a general linux that can be used with android, anywhere but in the bootloader(only fastboot in the bootloader).
bootloader isnt the usb connection between the device and the pc, its part of the phone that boots it and decides if the rom is safe to run. thats why we unlock it. so we can flash roms eithout googles key.
fastboot is the tool that you use to do whatever needs to be fone in the bootloader, adb everywhere else.
a recovery you need if you want to flash custom roms, kernels, supersu, or other mods. you can also wipe different partitions with the recovery, or make a "nandroid' backup. thats a bavkup of everything. its like a complete snapshot of everything during the time you made it. if you ever mess up your phone, you can restore it, and you will be at the exact same place when you made the backup.
anything else?
Hey everybody!
This is my first time posting something on XDA. This is really cool.
So I just bricked my fire, hard. Let's start from the top:
- I used the super tools rootjunkysdl.com/?device=Amazon%20Fire%205th%20gen&folder=SuperTool to get the google play store.
- Using the google play store, I got flashfire.
- Using flashfire, I flashed SlimLP onto my tablet successfully and quickly.
- I got a little cocky, and based on the comments on the youtube.com/watch?v=NaCBSuUuhRE video that I used to flash SlimLP I decided to try the flashfire technique with CM since it is my favorite ROM.
- I did everything properly and the same, but... it got stuck here... for about an hour...
imgur.com/QJvmRz3
So I decided to do the smartest thing ever and cancel it myself by turning it off, I wasn't able to do anything else anyway. Either way, my tablet is now stuck in the cyanogen 12 boot load animation, the one of the cute blue head with the radar effect.
I would of fixed this a long time ago, but for some reason I'm not able to adb sideload.
I go into fastboot, I can detect the device, but not adb sideload.
I go into adb sideload mode, I can't detect the device, so definitely not sideload. :/
I've tried updating my drivers, I don't know if I'm doing it right, but while it was in fastboot mode, I changed it to Android Composite ADB Interface, and that didn't change anything.
No matter what I'm doing, whenever I do adb devices, I always get:
List of devices attached
Blank. Nothing. Only when I'm in fastboot mode do I get:
fastboot devices
G0K0H40454261ARU fastboot
Something, but still no ADB. I can't even load TWRP here, tried that, I just install it and it just sits there dumbly saying it's installed.
I'm bricked just like my tablet. Could I please get some help here? I'm very desperate to get this tablet back up and running, and I feel so stupid for not having stuck with Slim and trying to install CM. I really don't want it to stay bricked like this.
Thank you, XDA!
Do you know if you had amazon FireOS version 5.0.1 or 5.1.1?
Just to be clear, you have actually selected the adb sideload option on your Fire when you try to connect with adb on you pc, correct? ADB is not even active until the adb sideload option has been selected.
drillster said:
I can't even load TWRP here, tried that, I just install it and it just sits there dumbly saying it's installed.
Click to expand...
Click to collapse
We can not "install" twrp. The bootloader is locked & won't allow it. We can only temporarily load twrp into memory. Each time we want to use twrp, we must connect usb to a pc, enter fastboot mode & load twrp. But this can only been done on 5.0.1 Fires. It's been blocked on 5.1.1. No way to load twrp at all on 5.1.1.
Just use this method: http://forum.xda-developers.com/ama...howto-how-to-restore-frimware-device-t3238740
hAtE NeVeR dIeS said:
Just use this method: http://forum.xda-developers.com/ama...howto-how-to-restore-frimware-device-t3238740
Click to expand...
Click to collapse
Do not follow the instructions in that thread! It will permanently brick you if you're have the FireOS 5.1.1 bootloader. The OP of that thread finds it too hard to add a note that it's outdated. See the page 4, post #36
blueberry.sky said:
Do not follow the instructions in that thread! It will permanently brick you if you're have the FireOS 5.1.1 bootloader. The OP of that thread finds it too hard to add a note that it's outdated. See the page 4, post #36
Click to expand...
Click to collapse
I have 5.1.1... yeah, thanks.
blueberry.sky said:
Do you know if you had amazon FireOS ve wrsion 5.0.1 or 5.1.1?
Click to expand...
Click to collapse
I have 5.1.1.
blueberry.sky said:
Just to be clear, you have actually selected the adb sideload option on your Fire when you try to connect with adb on you pc, correct? ADB is not even active until the adb sideload option has been selected.
Click to expand...
Click to collapse
Yeah I selected apply update from adb, adb devices was blank, didn't work.
blueberry.sky said:
We can not "install" twrp. The bootloader is locked & won't allow it. We can only temporarily load twrp into memory. Each time we want to use twrp, we must connect usb to a pc, enter fastboot mode & load twrp. But this can only been done on 5.0.1 Fires. It's been blocked on 5.1.1. No way to load twrp at all on 5.1.1.
Click to expand...
Click to collapse
I went into fastboot mode, installed twrp, and nothing happened because yes, its 5.1.1.
I've seen some other people who also have been unable to get adb to work (in custom recovery). I don't recall a solution.
There is an option in fastboot to flash firmware, I haven't seen anyone try that yet..
blueberry.sky said:
I've seen some other people who also have been unable to get adb to work (in custom recovery). I don't recall a solution.
There is an option in fastboot to flash firmware, I haven't seen anyone try that yet..
Click to expand...
Click to collapse
Do you have any ideas on how to do this? I would greatly appreciate it.
Thank you!
Since I haven't read anyone try it before, there would be some risk. I suppose you are already bricked, seemingly without a way to fix it, but you could brick it harder. You might be able to get adb working. I may not have any ideas on how to get adb working for you, but someone else might know. If you try flashing the stock OS via fastboot, there is a chance you could brick it in a different way.
The command would be
Code:
fastboot update <filename-of-stock-firmware.zip>
But we don't have a .zip stock firmware file. In twrp recovery you can just rename the .bin file to .zip & it works. Not sure if that will also work for fastboot. My guess is it won't work & might brick you.
Also be aware, on Fires that self-updated to FireOS 5.1.1 (or came with 5.1.1 new) you must only flash 5.1.1. Attempting to flash 5.0.1 will brick it 100% of the time & it's unrecoverable.
drillster said:
No matter what I'm doing, whenever I do adb devices, I always get:
List of devices attached
. . .
Click to expand...
Click to collapse
Just a shot in the dark here, but have you gone into device manager while in sideload mode and updated drivers for KFFOWI under Other devices? Windows needs drivers for every mode.
I have same issue.
[QUOTE=drillster;64617577]Hey everybody!
This is my first time posting something on XDA. This is really cool.
So I just bricked my fire, hard. Let's start from the top:
- I used the super tools rootjunkysdl.com/?device=Amazon%20Fire%205th%20gen&folder=SuperTool to get the google play store.
- Using the google play store, I got flashfire.
- Using flashfire, I flashed SlimLP onto my tablet successfully and quickly.
- I got a little cocky, and based on the comments on the youtube.com/watch?v=NaCBSuUuhRE video that I used to flash SlimLP I decided to try the flashfire technique with CM since it is my favorite ROM.
- I did everything properly and the same, but... it got stuck here... for about an hour...
imgur.com/QJvmRz3
So I decided to do the smartest thing ever and cancel it myself by turning it off, I wasn't able to do anything else anyway. Either way, my tablet is now stuck in the cyanogen 12 boot load animation, the one of the cute blue head with the radar effect.
I would of fixed this a long time ago, but for some reason I'm not able to adb sideload.
I go into fastboot, I can detect the device, but not adb sideload.
I go into adb sideload mode, I can't detect the device, so definitely not sideload. :/
I've tried updating my drivers, I don't know if I'm doing it right, but while it was in fastboot mode, I changed it to Android Composite ADB Interface, and that didn't change anything.
No matter what I'm doing, whenever I do adb devices, I always get:
List of devices attached
Blank. Nothing. Only when I'm in fastboot mode do I get:
fastboot devices
G0K0H40454261ARU fastboot
Something, but still no ADB. I can't even load TWRP here, tried that, I just install it and it just sits there dumbly saying it's installed.
I'm bricked just like my tablet. Could I please get some help here? I'm very desperate to get this tablet back up and running, and I feel so stupid for not having stuck with Slim and trying to install CM. I really don't want it to stay bricked like this.
Thank you, XDA![/QUOTE]
I did the same thing. Slim worked great, tried to flashfire CM12, ot bricked. Can get fastboot, but nothing else. Afraid to try update from fastboot.
I just want to say thanks to everybody who contributed, I'm really appreciative of the support, especially because I didn't expect it, haha! Listening to blueberry.sky I'm going to try the flashboot update, because it's either that or a bricked device. School just started so I got busy with that.
DoLooper said:
Just a shot in the dark here, but have you gone into device manager while in sideload mode and updated drivers for KFFOWI under Other devices? Windows needs drivers for every mode.
Click to expand...
Click to collapse
So when I have it in adb mode, the fire doesn't seem to show up anywhere in any of my devices, and I can only find it when it's in fastboot mode. So when it's in that mode, I've tried Android ADB Interface, Android ADB Composite Interface, and when I go back to adb sideload, it's just not there in device manager. I don't know what this means, so any speculation? But no matter what mode I'm in or what driver I'm using, I can't seem to get it to show up in adb when in sideload mode.
Again, thanks everybody, and I hope anybody else in the future with this issue can refer to this thread for a lead!
So I just tried to flash update the firmware from Amazon amazon.com/gp/help/customer/display.html?nodeId=201830180 which I renamed from .bin to .zip:
C:\path\to\SuperTool>fastboot update update-kindle-global-37.5.4.1_user_541112720.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
I didn't rename the Slim and this is what I get:
C:\path\to\SuperTool>fastboot update Slim-ford-5.1.1.build.2.2b-20151210.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Is there anyway I can resolve this, so I can do SOMETHING?
Thank you!
drillster said:
So I just tried to flash update the firmware from Amazon amazon.com/gp/help/customer/display.html?nodeId=201830180 which I renamed from .bin to .zip:
Is there anyway I can resolve this, so I can do SOMETHING?
Thank you!
Click to expand...
Click to collapse
To be clear, you were able to, "adb sideload update-kindle-global-37.5.4.1_user_541112720.bin". To restore your Fire OS 5.1.1?
thekrakah said:
To be clear, you were able to, "adb sideload update-kindle-global-37.5.4.1_user_541112720.bin". To restore your Fire OS 5.1.1?
Click to expand...
Click to collapse
No, I did fastboot update in fastboot mode as suggested by blueberry.sky since ADB isn't working for reasons I stated before.
C:\path\to\SuperTool>fastboot update update-kindle-global-37.5.4.1_user_541112720.zip
drillster said:
No, I did fastboot update in fastboot mode as suggested by blueberry.sky since ADB isn't working for reasons I stated before.
C:\path\to\SuperTool>fastboot update update-kindle-global-37.5.4.1_user_541112720.zip
Click to expand...
Click to collapse
So when you say you go into "adb sideload mode. You selected "apply update from adb", and the Fire device is actively waiting for the sideload command, but you got nothing showing up in your device manager at that point?
I'm just clarifying because until the "apply update from adb" is activated, windows doesn't get a communication from the Fire device.
thekrakah said:
So when you say you go into "adb sideload mode. You selected "apply update from adb", and the Fire device is actively waiting for the sideload command, but you got nothing showing up in your device manager at that point?
I'm just clarifying because until the "apply update from adb" is activated, windows doesn't get a communication from the Fire device.
Click to expand...
Click to collapse
On my device, I can get fastboot, but not adb. if I reboot from fastboot, I only get the
CM logo and it sticks there permanently until I power off. When I boot to fastboot, the screen is blank but my Windows PC can see the device and return the SN. I can issue the command to reboot to bootloader, but reboots to fastboot with "fastboot" in small letters at the bottom of the screen. What else can I try? Thanks for all the help offered so far.
What happens when you try to get into recovery mode?
To get into recovery you start with the Fire off. Turn off by holding power button until it goes off (might take awhile). I just tried turning off from fastboot mode. Took only about 14 seconds of holding power.
To enter recovery: hold volume down button + hold power button.
blueberry.sky said:
What happens when you try to get into recovery mode?
To get into recovery you start with the Fire off. Turn off by holding power button until it goes off (might take awhile). I just tried turning off from fastboot mode. Took only about 14 seconds of holding power.
To enter recovery: hold volume down button + hold power button.
Click to expand...
Click to collapse
When I try to get into recovery, it boots with a blank screen. At that point, I can connect to my PC, type fastboot devices, and it will show me device. Then I try to reboot-bootloader, and it reboots to fastboot, but this time it says fastboot on the screen. I can't seem to get to recovery
watch this video to see if it helps.
https://www.youtube.com/watch?v=RQLoH-ahjy4