Installed twrp, made a backup, however did a reboot and now cannot access twrp, I hold down the volume up button after the blue logo, but it either boots normally or shows the fastboot logo, any ideas
bluekiwi said:
Installed twrp, made a backup, however did a reboot and now cannot access twrp, I hold down the volume up button after the blue logo, but it either boots normally or shows the fastboot logo, any ideas
Click to expand...
Click to collapse
Power off, connect to wall charger and charge it for a few minutes.
Sent from my XT912 using Tapatalk
update to issue
I managed to track down the issue at hand. It was related to twrp 2.83. Installed twrp 2.70 and all was fine, however in the google play store, the youtube app tries to update and never downloads, just keeps trying, locks up google play from updating other apps or doing anything else.
Will try different rom, was using omni rom, will try candy5
bluekiwi said:
I managed to track down the issue at hand. It was related to twrp 2.83. Installed twrp 2.70 and all was fine, however in the google play store, the youtube app tries to update and never downloads, just keeps trying, locks up google play from updating other apps or doing anything else.
Will try different rom, was using omni rom, will try candy5
Click to expand...
Click to collapse
which Kindle Fire do you have?
sd_shadow said:
which Kindle Fire do you have?
Click to expand...
Click to collapse
kindle fire hd 7" 2012 version.
can you recommend a good lollipop rom/gapps package
any idea why the youtube play store download failure/stall?
Related
I recently decided to restore my rooted Kindle Fire HD 7." The kindle starts just fine, and displays the normal kindle fire boot screen. However, instead of the usual Amazon start-up and device registration screen, it gave me the default Android startup. However, everytime I hit start, the setup wizard ends up crashing. I had the Google Play store installed before the unroot. I have not messed around with custom roms, or anything like that. Windows sees the Kindle just fine, however it doesn't register under ADB. Is there anything I can do? I do not have a factory cable, nor can I find where to get one.
cunfuzzed said:
I recently decided to restore my rooted Kindle Fire HD 7." The kindle starts just fine, and displays the normal kindle fire boot screen. However, instead of the usual Amazon start-up and device registration screen, it gave me the default Android startup. However, everytime I hit start, the setup wizard ends up crashing. I had the Google Play store installed before the unroot. I have not messed around with custom roms, or anything like that. Windows sees the Kindle just fine, however it doesn't register under ADB. Is there anything I can do? I do not have a factory cable, nor can I find where to get one.
Click to expand...
Click to collapse
Where did you find instructions for the restore? I need to restore one to stock too.
SeanPlunk said:
Where did you find instructions for the restore? I need to restore one to stock too.
Click to expand...
Click to collapse
Settings->Device->Factory
Also, the device doesn't show up when I try fastboot.
I have a rooted kindle fire hd 7" that has TWRP 2.4.40 and Kinology 2.01 on it. Recently, I decided to re-install, doing this.
First:
Plugged in usb power cable (needed to charge)
Second:
Went into recovery mode via holding down the power button inside Kinology
Third:
Did a factory reset, wiped both cache and dalvic cahce
Fourth:
Flashed roms in this order;
Amazon OS 7.31 part 1
Amazon OS 7.31 part 2
Amazon OS 7.31 part 3
Kinology 2.01
Google Apps
Fith:
Cleared cache and dalvic cache again
Sixth:
hit "Reboot System"
Seventh:
Now I'm stuck at blue Kindle Fire logo, after the orange one first shows up. What should I do? I do not have a recovery cable, and the device is not detected. ADB drivers are fully installed.
Edit : Fixed
Had to boot into recovery by holding down volume up (the side closest to the mic jack) while booting!
GreyGeist said:
I have a rooted kindle fire hd 7" that has TWRP 2.4.40 and Kinology 2.01 on it. Recently, I decided to re-install, doing this.
First:
Plugged in usb power cable (needed to charge)
Second:
Went into recovery mode via holding down the power button inside Kinology
Third:
Did a factory reset, wiped both cache and dalvic cahce
Fourth:
Flashed roms in this order;
Amazon OS 7.31 part 1
Amazon OS 7.31 part 2
Amazon OS 7.31 part 3
Kinology 2.01
Google Apps
Fith:
Cleared cache and dalvic cache again
Sixth:
hit "Reboot System"
Seventh:
Now I'm stuck at blue Kindle Fire logo, after the orange one first shows up. What should I do? I do not have a recovery cable, and the device is not detected. ADB drivers are fully installed.
Click to expand...
Click to collapse
You didn't flash part 0 of Kinology. Also, you didn't make a backup of Kinology before you did this in case of disaster, did you?
I made a backup
Don't start assuming things because I'm new! I've jailbroken two devices before the fire hd, and yes, I made a backup. My problem is getting to the recovery.
Edit:
If you are not currently running Kinology or Stock OS with TWRP 2.4.4.0, download Kinology-step0a-boot-7.3.0-twrp-2.4.4.0.zip. This will flash four items: stock 7.3.0 xloader, stock 7.2.3 bootloader, Freedom boot/kernel 7.3.0, and TWRP recovery 2.4.4.0.
Click to expand...
Click to collapse
-Kinology 2.01 page
Kinology step 0 was not my problem.
GreyGeist said:
Don't start assuming things because I'm new! I've jailbroken two devices before the fire hd, and yes, I made a backup. My problem is getting to the recovery.
Edit:
-Kinology 2.01 page
Kinology step 0 was not my problem.
Click to expand...
Click to collapse
I didn't assume anything. You've jailbroken, as in Apple devices? The KFHD is an Android device, if you didn't know. It doesn't matter if your ADB drivers are fully installed, ADB requires both devices to fully boot and then it starts communicating. My thread in my signature, #7.
Fixed!
seokhun said:
I didn't assume anything. You've jailbroken, as in Apple devices? The KFHD is an Android device, if you didn't know. It doesn't matter if your ADB drivers are fully installed, ADB requires both devices to fully boot and then it starts communicating. My thread in my signature, #7.
Click to expand...
Click to collapse
I've jailbroken two different consoles, and rooted + CWM'd an android galaxy s2. But that's off topic! What is really awesome, and that nobody has been able to point out, is that you can restore perfectly fine as long as your first bootloader isn't broken, as I just found out. You just have to hold down volume up while booting, and it goes right into recovery! Happy to have device back! Flashed CM10.1 Tablet, works perfectly after multiple reboots. By the way, while you're here, as a senior member, where should I find more ROMs? I'm starting a list of kindle fire hd roms on reddit and looking for recomendations!
GreyGeist said:
I've jailbroken two different consoles, and rooted + CWM'd an android galaxy s2. But that's off topic! What is really awesome, and that nobody has been able to point out, is that you can restore perfectly fine as long as your first bootloader isn't broken, as I just found out. You just have to hold down volume up while booting, and it goes right into recovery! Happy to have device back! Flashed CM10.1 Tablet, works perfectly after multiple reboots. By the way, while you're here, as a senior member, where should I find more ROMs? I'm starting a list of kindle fire hd roms on reddit and looking for recomendations!
Click to expand...
Click to collapse
Consoles? I think we call those "devices" but whatever floats your boat. Take a look at the thread in my signature, Step 4.
Ok so I have a Kindle Fire HD that I had "hacked" to be a full Android tablet. It was flashed with CyanogenMod 'gapps-jb-20130813-signed.zip'. I got the bright idea to update the CyanogenMod, and that's when it all went to sh!t. Now the thing only boots to Team Win Recovery Project.
Any suggestions on how I get past this? I attached a picture of what I am seeing when it boots.
Update twrp to 2.7, wipe system and your caches, flash the latest cm and the latest gapps.
stunts513 said:
Update twrp to 2.7, wipe system and your caches, flash the latest cm and the latest gapps.
Click to expand...
Click to collapse
OK. I am going to give it a go today. Thanks for the point in the right direction, I will provide updates.
Not sure what I did, but now the stupid thing isn't even coming on. Do I need the factory cable for this? If so that is at home, I will have to try this again later.
ckshowtime said:
Not sure what I did, but now the stupid thing isn't even coming on. Do I need the factory cable for this? If so that is at home, I will have to try this again later.
Click to expand...
Click to collapse
Can you tell us what you did to the device?
SafinWasi said:
Can you tell us what you did to the device?
Click to expand...
Click to collapse
I wiped the device from the TWRP v2.6.3.0 screen. Now the only thing it does is boot to the TWRP v2.6.3.0 screen I referenced in an earlier post. I have been reading posts/threads and downloading different files into a folder for 2 days now. The thing is that my PC is not recognizing the Kindle in Windows Explorer, it does recognize it in Device Manager though.
I am at a loss for how to get anything I have on my pc over to the Kindle if it isn't showing in Windows Explorer. Oh...and I do have the factory cable with me as well.
So now the stupid thing is stuck in a boot loop it appears. It just keeps coming up with the Kindle Fire, fire is in orange. It does this with the cable plugged in and without.
I currently am trying to install CM12.1 onto my Amazon Fire 7, but unfortunately, it looks like I may have messed up in the process (I am stuck with the Amazon logo re-looping every ~15-20 seconds). I am able to go into the safe recovery mode, so I assume I haven't bricked the device completely, but I was wondering, what exactly is the best way to flash CM12.1 onto this device?
There seems to be an excessive amount of information, but very little organization, so would love to hear what the "best" steps would be to get CM12.1 on this bad boy.
I don't have the device yet but from what i read you need to tell us more info like what was your amazon v. 5.0.1 or 5.1.1 and how you install cm by TWRP or flash fire
Sent from my iPhone using Tapatalk
it will all depend on the version you have, but here you will find most info.
http://forum.xda-developers.com/amazon-fire/general/videos-tutorials-how-to-root-flash-roms-t3254268
shabuboy said:
it will all depend on the version you have, but here you will find most info.
http://forum.xda-developers.com/amazon-fire/general/videos-tutorials-how-to-root-flash-roms-t3254268
Click to expand...
Click to collapse
So I went ahead and installed the original firmware (5.1.1), but now am wondering where do I go from here. I have the device rooted and installed Flashify, but I am not sure how to install TWRP for 5.1.1, as I was using Rootjunky's .bat file.
darkgiant said:
So I went ahead and installed the original firmware (5.1.1), but now am wondering where do I go from here. I have the device rooted and installed Flashify, but I am not sure how to install TWRP for 5.1.1, as I was using Rootjunky's .bat file.
Click to expand...
Click to collapse
You can't install TWRP on 5.11, if you want to flash roms you have to use FlashFire now.
This is due to the 5.11 ota update including a bootloader update which removes the ability to fastboot boot.
Just follow the instructions to install CM 12.1 and wait for it to boot.
Ownster said:
You can't install TWRP on 5.11, if you want to flash roms you have to use FlashFire now.
This is due to the 5.11 ota update including a bootloader update which removes the ability to fastboot boot.
Click to expand...
Click to collapse
Yeah, so I just found that out few seconds ago. I tried to flash and install CM, but after the reboot, it just goes back to the FireOS "Optimizing system storage and applications..." screen, no idea what I am doing wrong...
I am also wiping everything too before I flash the CM and GAPPS zip files
darkgiant said:
I am also wiping everything too before I flash the CM and GAPPS zip files
Click to expand...
Click to collapse
I would be very careful using flashfire if your coming from fire os 5.1.1, we cannot use TWRP and a few people(myself included) have lost access to Amazon recovery, if you get stuck in a boot loop you have no way to recover your device, your best bet is to wait to see if a more secure way appears of flashing a device that has been using fire os 5.1.1.
abacabie said:
I would be very careful using flashfire if your coming from fire os 5.1.1, we cannot use TWRP and a few people(myself included) have lost access to Amazon recovery, if you get stuck in a boot loop you have no way to recover your device, your best bet is to wait to see if a more secure way appears of flashing a device that has been using fire os 5.1.1.
Click to expand...
Click to collapse
I have no idea what you are talking about. You can most certainly reflash the Amazon firmware when you are stuck in the boot cycle by transferring the file from ADB (after holding volume down + power for more than 10 seconds), and than restart the device, and you are back to FireOS 5.1.1.
I have already went ahead and Flashed SlimLP, and so far so good, it seems fine to me, I guess I'll have to wait and see how stable it is.
darkgiant said:
I have no idea what you are talking about. You can most certainly reflash the Amazon firmware when you are stuck in the boot cycle by transferring the file from ADB (after holding volume down + power for more than 10 seconds), and than restart the device, and you are back to FireOS 5.1.1.
Click to expand...
Click to collapse
Glad it worked well for you. Not everyone has been so fortunate. One persons favorable experience does not equate to everyone. Some of those impacted are veteran users who 'lost' devices testing out code and techniques that you are now benefiting from.
darkgiant said:
I have no idea what you are talking about. You can most certainly reflash the Amazon firmware when you are stuck in the boot cycle by transferring the file from ADB (after holding volume down + power for more than 10 seconds), and than restart the device, and you are back to FireOS 5.1.1.
I have already went ahead and Flashed SlimLP, and so far so good, it seems fine to me, I guess I'll have to wait and see how stable it is.
Click to expand...
Click to collapse
If you read my post properly i said " lost access to Amazon recovery" , there is no way to transfer the file from ADB as ADB is not there, due to the fact that there is no Amazon recovery, holding volume down + power does nothing, if you look around the forum you will see this has happened to a few people myself included .
darkgiant said:
I have no idea what you are talking about. You can most certainly reflash the Amazon firmware when you are stuck in the boot cycle by transferring the file from ADB (after holding volume down + power for more than 10 seconds), and than restart the device, and you are back to FireOS 5.1.1.
I have already went ahead and Flashed SlimLP, and so far so good, it seems fine to me, I guess I'll have to wait and see how stable it is.
Click to expand...
Click to collapse
He's talking about how his device got buggered from a dirty Rom load. In his case and for a few others, they've lost the option to sideload back to stock.
Anyway here's the bare minimum process, since it sounds like you've gone through the details parts of Rom loading before.
#1 restore to stock rom 5.1.1
#2 install SuperSU/Root
#3 install flashfire
#4 install CM/SlimLP and Gapps (pico, micro, mini) of your choice, and your done.
When I put CM on my 5.1.1 Fire device, I installed flashfire.apk manually, used open Gapps pico, and the CM 12-30-2015 image.
abacabie said:
If you read my post properly i said " lost access to Amazon recovery" , there is no way to transfer the file from ADB as ADB is not there, due to the fact that there is no Amazon recovery, holding volume down + power does nothing, if you look around the forum you will see this has happened to a few people myself included .
Click to expand...
Click to collapse
Gotcha, didn't know there was level of increments the relooping represented. Well either way, hopefully something gets developed to all the "hard-bricked" users.
Hi guys, need a bit of help if possible, my 5th Gen fire, which I had rooted, side loaded play store, removed adverts and removed amazon launcher and replaced with 3rd party launcher so it was like a rooted vanilla android tablet...
Now here comes the issue, since yesterday the tablet has been not been able to connect to the wifi as it's stating that the parental controls had kicked in and wouldn't allow me to authenticate no matter what details I entered, so after reading a couple of articles on Google apparently the only way round it was to factory reset it, which I did, unfortunately this now means that the tablet is booting up into a factory reset version of the fire without a launcher installed! Obviously iv now lost my play store etc so cant get to any app to get on the Internet or anything!? Any ideas at all?
Can you get into the stock recovery? or into the fastboot screen?
If you can get into the stock recovery, you should be able to flash the stock image through adb. http://forum.xda-developers.com/amazon-fire/general/unbrick-amazon-fire-7in-2015-5th-gen-t3285294
Else if you can get into the fastboot mode, you could try to install nova launcher again.
just verify the version you have before attempting any recovery. You cannot install 5.0.1 if you already have 5.1.1.
xOutcasTx said:
Can you get into the stock recovery? or into the fastboot screen?
If you can get into the stock recovery, you should be able to flash the stock image through adb. http://forum.xda-developers.com/amazon-fire/general/unbrick-amazon-fire-7in-2015-5th-gen-t3285294
Else if you can get into the fastboot mode, you could try to install nova launcher again.
Click to expand...
Click to collapse
I can get to the recovery screen (power tablet up with Vol down button) menu can't get it to boot to the OS now as it's talking about doing a system /software ota update and doesn't actually do anything. Not sure how I'd get the launcher installed via fast boot tbh
Did you read and follow the link provided on post #2?
thanks guys, managed to flash it back to stock via recovery, drivers were being a bit of a pain, got it working in the end, then decided to update it to CM 12.1 with Gapps, seems to be working a treat now!