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.
Related
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.
Hello guys. I appreciate in advance any help you can bring to this thread.
Please be aware (for my amount of messages) that i'm still a newbie. So, please don't brag or dismiss any opinions or suggestions just because... Instead, try to share your magnificent knowledge and solutions to the following problem:
I have a rooted Kindle Fire HD 7", with second bootloader and TWRP recovery. I was running a 4.2.2 version of Paranoid Android without any problem. I often update ROM's and twerks for the tablet and my SGS3, so i'm pretty much capable of solving many of problems i've faced before, but right now i'm stucked in a bootloop without knowing what to do.
I tried to update my recovery TRWP from 2.4.x version to a 2.6.x version of it (to be able to flash KK 4.4 on KFHD), i've downloaded .img from TWRP web page and flashed via "Flashify" (which i read is the 2nd easiest way to do it), but when i rebooted the device, it got into a bootloop (?). It shows Kindle Fire, first in normal letters color set white-orange, then second color set white-blue, and after it is shown a new icon that says "FASTBOOT kindle fire" in orange... And that's pretty much it. It doesn't moves forward and i can't access recovery mode by pressing power button as usual.
Do you have any ideas of what to do in this scenario? If yes, please share. If don't, thank you anyway for reading the thread.
guillemedina11 said:
Hello guys. I appreciate in advance any help you can bring to this thread.
Please be aware (for my amount of messages) that i'm still a newbie. So, please don't brag or dismiss any opinions or suggestions just because... Instead, try to share your magnificent knowledge and solutions to the following problem:
I have a rooted Kindle Fire HD 7", with second bootloader and TWRP recovery. I was running a 4.2.2 version of Paranoid Android without any problem. I often update ROM's and twerks for the tablet and my SGS3, so i'm pretty much capable of solving many of problems i've faced before, but right now i'm stucked in a bootloop without knowing what to do.
I tried to update my recovery TRWP from 2.4.x version to a 2.6.x version of it (to be able to flash KK 4.4 on KFHD), i've downloaded .img from TWRP web page and flashed via "Flashify" (which i read is the 2nd easiest way to do it), but when i rebooted the device, it got into a bootloop (?). It shows Kindle Fire, first in normal letters color set white-orange, then second color set white-blue, and after it is shown a new icon that says "FASTBOOT kindle fire" in orange... And that's pretty much it. It doesn't moves forward and i can't access recovery mode by pressing power button as usual.
Do you have any ideas of what to do in this scenario? If yes, please share. If don't, thank you anyway for reading the thread.
Click to expand...
Click to collapse
You can't just use anything when modding. TWRP has to come from Hashcode's thread because he modifies them for the Kindles`s. The other thing is the KFHD7 uses FireFlash. You can try flashing a Nandroid backup in TWRP or you will need a fastest cord and factory reset.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
guillemedina11 said:
Hello guys. I appreciate in advance any help you can bring to this thread.
Please be aware (for my amount of messages) that i'm still a newbie. So, please don't brag or dismiss any opinions or suggestions just because... Instead, try to share your magnificent knowledge and solutions to the following problem:
I have a rooted Kindle Fire HD 7", with second bootloader and TWRP recovery. I was running a 4.2.2 version of Paranoid Android without any problem. I often update ROM's and twerks for the tablet and my SGS3, so i'm pretty much capable of solving many of problems i've faced before, but right now i'm stucked in a bootloop without knowing what to do.
I tried to update my recovery TRWP from 2.4.x version to a 2.6.x version of it (to be able to flash KK 4.4 on KFHD), i've downloaded .img from TWRP web page and flashed via "Flashify" (which i read is the 2nd easiest way to do it), but when i rebooted the device, it got into a bootloop (?). It shows Kindle Fire, first in normal letters color set white-orange, then second color set white-blue, and after it is shown a new icon that says "FASTBOOT kindle fire" in orange... And that's pretty much it. It doesn't moves forward and i can't access recovery mode by pressing power button as usual.
Do you have any ideas of what to do in this scenario? If yes, please share. If don't, thank you anyway for reading the thread.
Click to expand...
Click to collapse
You should have used FireFlash or direct ADB. For now,you can try to restore a Nandroid backup and get the TWRP 2.6.3.1 image from Hashcode's thread. And use FireFlash this time!!
I can't help but notice that he said "twerks" in his original post :silly:
Sent from my 2013 Kindle Fire HD with Tapatalk
LinearEquation said:
You can't just use anything when modding. TWRP has to come from Hashcode's thread because he modifies them for the Kindles`s. The other thing is the KFHD7 uses FireFlash. You can try flashing a Nandroid backup in TWRP or you will need a fastest cord and factory reset.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you so very much for your helpful comment.
As i said in the first post, for any reason a can't access twrp recovery by pressing power button right after booting the device. I think a might need the fastboot cable.
Question: Original factory cable doesn't work in this case? y've noticed that i was triying to plug it to the pc with my samsung cable. does it make any real difference (Just comparing factory kindle cable and samsung cable)?.
guillemedina11 said:
Thank you so very much for your helpful comment.
As i said in the first post, for any reason a can't access twrp recovery by pressing power button right after booting the device. I think a might need the fastboot cable.
Question: Original factory cable doesn't work in this case? y've noticed that i was triying to plug it to the pc with my samsung cable. does it make any real difference (Just comparing factory kindle cable and samsung cable)?.
Click to expand...
Click to collapse
yes there's a different in KFHD factory cable and samsung cable cause factory cable are made specially for KFHD and its support good speed then samsung cable/
qoute: lol i am a newbie
A factory cable (also known as a fast boot cable) is not the cable that came with your kindle it is a cable you have to make or order.
On the micro USB side it shorts pin one and pin four.
When this cable is plugged in your kindle will boot to a screen that says fast boot and stay there. In this special mode we can use commands from a PC to change the kindles settings.
Sent from my XT907 using xda app-developers app
So I followed a guide that used fireflash to flash freedom boot and TWRP. The problem is when it got to the point of backing up before I installed the system, I didn't have enough space. Not a problem right? Well in my haste I rebooted out of TWRP and now I can't get back into TWRP or obviously the system which doesn't exist.
I would have thought it would be simple to get back into TWRP and just carry on but it looks like there is no easy way to get back into it?
This is a HD7 model no: X43Z60
Does the logo ever turn blue still?
stunts513 said:
Does the logo ever turn blue still?
Click to expand...
Click to collapse
No it just loops on the orange kindle fire one. It's worth mentioning that obviously it did initially turn blue to get into TWRP but after it asked if I would like to restart, it just went into the loop.
If it didn't turn blue you will need a fastboot cable/adapter to fix, I recommend team blackhats from hashcode's twrp tut.
You will have to reflash stock and go about reinstalling twrp/2nd bootloader, I think you wiped the stack override so it won't boot.
stunts513 said:
If it didn't turn blue you will need a fastboot cable/adapter to fix, I recommend team blackhats from hashcode's twrp tut.
You will have to reflash stock and go about reinstalling twrp/2nd bootloader, I think you wiped the stack override so it won't boot.
Click to expand...
Click to collapse
Thanks for the responses.
I have ordered a fastboot cable and it's nice to hear that this is still recoverable. Would you be able to point me in the direction of the best reflash stock tutorial you know of?
The tutorial I used to get into this mess used an APK to do all of the flashing / stack override methods.
That's the same method I used for flashing, it seemed to have worked for you so the method was fine. Anyways you can look in the general section fornmkindke fire first aid, or in the dev section's FAQ post for the SRT(system restore tool), either one fixes it.
stunts513 said:
That's the same method I used for flashing, it seemed to have worked for you so the method was fine. Anyways you can look in the general section fornmkindke fire first aid, or in the dev section's FAQ post for the SRT(system restore tool), either one fixes it.
Click to expand...
Click to collapse
Cheers for the help
Hi everybody
I've been running a rooted kindle fire hd for about a year with cyanogenmod and no problems. Tonight I downloaded the latest nightly update installed it with TWRP and re booted fine.
I kept getting google play services errors so decided to factory reset and clean everything up. Now I cannot get past the teamwin boot logo.
I see the orange kindlefire, blue kindlefire, then the teamwin logo flashes every 5 seconds.
Any ideas on how to recover this?
Regards
KP
kpugh162 said:
Hi everybody
I've been running a rooted kindle fire hd for about a year with cyanogenmod and no problems. Tonight I downloaded the latest nightly update installed it with TWRP and re booted fine.
I kept getting google play services errors so decided to factory reset and clean everything up. Now I cannot get past the teamwin boot logo.
I see the orange kindlefire, blue kindlefire, then the teamwin logo flashes every 5 seconds.
Any ideas on how to recover this?
Regards
KP
Click to expand...
Click to collapse
i have the same problem and there seems to be no way to get the kindle in any state to do anything, all I've found out so far is that its stuck trying to factory reset and there should be a way to reverse this, i hope someone can give us a solution or i might as well call my kindle a paperweight.
laharl_chaos said:
i have the same problem and there seems to be no way to get the kindle in any state to do anything, all I've found out so far is that its stuck trying to factory reset and there should be a way to reverse this, i hope someone can give us a solution or i might as well call my kindle a paperweight.
Click to expand...
Click to collapse
Thanks for letting me know, I purchased a factory cable today. Seems to be recognised by my laptop, but the kindle doesnt go into fastboot. There seems to be a few people with this problem. I've not seen any help offered yet. I'm not holding out much hope, doesn't seem any way to communicate with it.
Where did you get your info?
kpugh162 said:
Thanks for letting me know, I purchased a factory cable today. Seems to be recognised by my laptop, but the kindle doesnt go into fastboot. There seems to be a few people with this problem. I've not seen any help offered yet. I'm not holding out much hope, doesn't seem any way to communicate with it.
Where did you get your info?
Click to expand...
Click to collapse
i've found out a lot about bootloop issues and in most cases it seems like the first thing needed to fix the problem is a factory cable, i didn't get mine yet so i can't see if it will work but since your pc can see your kindle now you can try out kindle fire first aid 4.1.88-beta.
let me know if it works for you.
laharl_chaos said:
i've found out a lot about bootloop issues and in most cases it seems like the first thing needed to fix the problem is a factory cable, i didn't get mine yet so i can't see if it will work but since your pc can see your kindle now you can try out kindle fire first aid 4.1.88-beta.
let me know if it works for you.
Click to expand...
Click to collapse
I'd already tried that. Seems because the kindle is not fully booting up then kindle fire first aid doesnt recognise it. Unless what i've been sent is actually a normal usb, then I dont see any way of sorting this. I'll wait to see if you have better luck
kpugh162 said:
I'd already tried that. Seems because the kindle is not fully booting up then kindle fire first aid doesnt recognise it. Unless what i've been sent is actually a normal usb, then I dont see any way of sorting this. I'll wait to see if you have better luck
Click to expand...
Click to collapse
OK I may have cracked it here. I am no expert ( I wouldnt be in this mess if I was) i was playing with the adb commands with the factory cable connected.
Typed:
ADB devices
showed a device called D025A0A024540SF0 recovery
Typed:
ADB Reboot-Bootloader
Kindle fire boots into FASTBOOT screen. YEY ME!!!
Now i'm not really sure where to go, never used fastboot before.
After using kindlefire recovery tool, doing a wipe then option 2 my kindle booted up into TWRP.
I tried rebooting from here and now I get a flashing kindlefire logo.
occasionally i manage to get it into fastboot with the factory cable, but it doesnt stay there long enough to do anything. I hoping this is maybe a power issue so I'm leaving it plugged in overnight to attempt to charge it.
hope this info helps you, I feel like I was at a point to simply re flash a rom but messed up by rebooting from twrp.
I did it!!!!
Managed to get it to stay in fastboot mode and ran kindlerecover tool again. now have a working kindle running APEX launcher. Have to read up tomorrow and get cyanogenmod back.
kpugh162 said:
OK I may have cracked it here. I am no expert ( I wouldnt be in this mess if I was) i was playing with the adb commands with the factory cable connected.
Typed:
ADB devices
showed a device called D025A0A024540SF0 recovery
Typed:
ADB Reboot-Bootloader
Kindle fire boots into FASTBOOT screen. YEY ME!!!
Now i'm not really sure where to go, never used fastboot before.
After using kindlefire recovery tool, doing a wipe then option 2 my kindle booted up into TWRP.
I tried rebooting from here and now I get a flashing kindlefire logo.
occasionally i manage to get it into fastboot with the factory cable, but it doesnt stay there long enough to do anything. I hoping this is maybe a power issue so I'm leaving it plugged in overnight to attempt to charge it.
hope this info helps you, I feel like I was at a point to simply re flash a rom but messed up by rebooting from twrp.
I did it!!!!
Managed to get it to stay in fastboot mode and ran kindlerecover tool again. now have a working kindle running APEX launcher. Have to read up tomorrow and get cyanogenmod back.
Click to expand...
Click to collapse
Grats i'm glad it worked out for you man, i'll try out the same when i get my cable lol i ended up buying a new tablet thinking no one would solve this problem and now i just may have two if i get mine working also if you try loli pop again make sure you install gapps for it, that was my first mistake that led to me messing up my kindle the second being the factory reset, the devs should either disable or warn people not to try it since your screwed once you do anyways i'll give an update once i try to recover my kindle, cheers.
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.