Following the video walk thoughs of rooting and installed TWRP.
I got the KF rooted successfully without issue, but the issue came when I went to install TWRP.
I got to the point where I ran the run.bat and then chose option 5 to install recovery. It download the recovery, and pushed it to the device. I watched it restart which it hung on the yellow triangle.
At this point the tutorial said to reinstall the drivers by running the .bat provided - that worked and it continued. I tapped "Reboot" on the KF. The script continued a bit further and the device rebooted and now it's stuck on the yellow triangle AGAIN. ADB refuses to respond and the drivers seem installed properly. I closed out the command prompt from the script because it was just hanging there.
Edit:
Device Manager shows Android Debug Bridge with an exclamation on it, claiming "This device cannot start".
Any idea what I should do at this juncture?
Thanks!
Ok, think I fixed it.
I found this trick:
"If you end up stuck at the yellow triangle, in KF Utility select Boot Normal, wait for it to say <waiting for device> and then press and hold the power button 20 seconds until the fire turns off, then when its off turn it back on. This sometimes happens, I have yet to find a clean solution "
Now, it booted back up.
At this stage, is TWRP installed??? I don't want this happen again LOL.
Had a similar problem as you, my drivers messed up going into fastboot on the Kindle Fire Utility and it hanged on boot.
If your fire displays the triangle on bootup that means Kindle Fire Utility has replaced the bootloader, which it does anyway before installing TWRP, so my guess is you're fine...
I'd wait for someone more experienced to answer as well though just to make sure.
Mwa exp. is definite not. So for mental ease I use only cmd prompt to do just the essential [ie.] adb device+ rtn key, and the like. God forbid I hit something that means solder a cable pin for connectivity after removing case rear enclosure on chasis, locate the ;X' chips, AND use extreme caution at this point. ...Still works don't fix it. Use alternate route.
I got it fixed as I stated above guys. Currently running ice cream sandwich!!
I rooted my kindle fire with the Kindle Fire Utility. Installed TWRP, and installed the rom - MIUI.us_blaze_4.0.3-2.2.3-alpha_0xD34D. After doing this, I reboot and I am stuck at the Yellow Triangle. If I push the power button to get into TWRP the power button turns orange and is still stuck at the yellow triangle . if I power off and on again , do nothing Windows detects the kindle for a few second and then it disappears and then is detected again and then disappears, so I cannot access the device through ADB ,
Any ideas or do I now have a paper weight instead of a kindle fire
Kindle fire Utility should work even without being recognized (well it did for me after turning on and off 3 times).
Does the device at least get's the firefirefire logo? If so, this is what I did
-Turn your kindle off by holding the power button down for at most 20 seconds.
-Plug kindle into your computer
-Run the unbrick utility
-Turn kindle on
-Wait for the Caution Sign with the fire logo (firefirefire logo)
-Choose first option on utility (Recovery Loop)
-Wait... (a max of 10 minutes)
This should work, if not, try to turn off your kindle on and off, and then try again.
==========================================
This is what worked for me (I've been tossing this around awhile now, and it even worked for two of my friends).
The link to the unbrick utility is: Here
Mine got stuck on the triangle as well and I thought I was screwed, but appears you are just stuck in fastboot.
What I did was use the KFU (vashypoo has made an awesome utility) and even though it didn't show as recognized when I opened the KFU, I was able to use Option 1 - Bootmode Menu, Then Option 1 - Normal.
My Fire restarted normally after that.
Give it a shot.
Check out this post: http://forum.xda-developers.com/showthread.php?t=1520826
Zane had to cycle a couple of times to get it to take.
Are there alternative download links for this utility....I keep downloading it from the site that this site provides and I keep getting viruses or incomplete downloading. I have been trying to unbrick my kindle for weeks and this seems like my last route...
Try this Linux solution. It was the only thing that worked for me.
http://forum.xda-developers.com/showthread.php?t=1430038
Solution for This: I had the exact same problem
http://forum.xda-developers.com/show...02&postcount=4
I had the exact same problem and b63 posted this as a reply. My Kindle was stuck on yellow triangle and was not recognized by ADB. When I tried to boot into twrp the power button turned orange but stayed on the yellow triangle. The thread above is what I used, worked perfectly.
Good Luck!
Kindle Fire Bricked and Windows doesn't recognize it.
First off, thanks for all the development and help in getting the Unbricking utility and the KFU for all of us noobs. I have been searching threads for hours before I decided to post, and I can't find the answer. I rooted with KFU and have TWRP installed. I ran MIUI several months until I decided to try MIUI 4.0 after I flashed 4.0 it rebooted to the yellow triangle and the power turned orange. I ran the unbricking utility and now the light is green, but it won't go any further. When I first plug in the kindle windows recognizes it for a second and then it disappears from the device manager completely. I have updated the driver several times, tried the KFU to get it to boot (4000) and nothing works. if I turn off the kindle and turn it back on KFU and windows will recognize it for a second and reboot it, but then it gets stuck on yellow triangle and never goes anywhere. Then I don't see it in the device manager anymore, not even 'unknown device'.
I did forget and leave the Kindle plugged into the computer while it was flashing MIUI 4.0, I don't know if that would have killed it. I never got a chance to see 4.0 it's been bricked ever since.
Any help or ideas would be greatly appreciated. I'm sorry if this specific situation has been covered anywhere in the forums and I missed it.
Thanks
this should help you:
http://forum.xda-developers.com/showpost.php?p=22433402&postcount=4
I rooted my Kindle Fire and installed CM9 on it using TWRP 2.0. I updated CM9 to CM9 Alpha but realized that I liked CM9 better. I then tried to flash MIUI 4.0.3 to my Kindle to see how that would work and got it to work but didn't like that either. I booted back into TWRP and then attempted to restore. Once I my restored it I hit the reboot system button and my Kindle got stuck on the yellow triangle. I unplugged and plugged it and attempted most if not all the suggestions by various threads. The problem is that every time I plug my Kindle into my computer while it is off it displays the yellow triangle and is only recognized for 10 seconds. After it disappears it reappears for 5 more seconds and then completely disappears. I attempted to use KFU to reboot it in normal 4000 by having KFU open plugging in my Kindle and quickly hitting the reboot in normal 4000 mode. KFU said that it told the Kindle to reboot in normal mode but when it started up again it stayed on the yellow triangle. I am really frantic as I love and use this tablet every day! Any help is appreciated!
bricked?
it seems like i keep finding people with the same problem as me that noone wants to help ;; this is madness
When you were connected to KFU and attempted to put it in normal bootmode did you attempt a hard reset when it said "Waiting for device...."? Sometimes the KF hangs and needs a 20 second hard reset
Try this using Ubuntu linux booted from a stick. Worked for me when nothing else would.
http://forum.xda-developers.com/showthread.php?t=1430038
http://forum.xda-developers.com/showpost.php?p=22433402&postcount=4
b63 said:
http://forum.xda-developers.com/showpost.php?p=22433402&postcount=4
Click to expand...
Click to collapse
This worked for me after hours working on it last night. Follow all those steps as they make the most sense and actually work compared to all the other threads I've read
glad to help ...
please mark the subject of the topic (edit first post) with [Solved]
After having problems with my amazon app, and all my google apps, I figured it was a good time to try and learn how to put a new rom in. So I picked CM9 and tried to no avail. I was getting the same problem as alot of guys on here where it said something about /media. But unlike the others, mine wouldn't load like the others. I also was unable to go back to CM7. I was stuck in TWRP. So I tried my back-up and still nothing. Then thinking maybe I had a bad download I tried another CM9 and nothing. Then I tried MUIU. All three said failure to install. Then after trying the MUIU, my computer quit recognizing my KF and it stopped loading into TWRP and just went straight into yellow triangle. I followed the other threads and added the line under the 1949 in .bit file. I reinstalled the drivers in my newly downloaded KFU. Then tried the adb and nothing works because my computer won't recognize the KFU.
Had the same problem as the op. This solution also worked for me.
Sent from my Transformer TF101 using Tapatalk
This is how I unbricked my TF300T that had no rom installed and a wrong bootloader/recovery combination. (4.2 bootloader with TWRP recovery JB version). Hope it helps.:good:
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I have the same on my TF300t and A700 - but it seems i just managed to get my TF300t back
i tried all fastboot (reflashing recovery, boot, system etc) no dice - especially since writing system was done after 3 secs all the time.
Here how i restored my TF300T JB
download your appropriate lates firmware from Asus (WW, US etc.) and extract the zip twice so you have your blob file
install your device drivers if needed (i used Google SDK ones) (and as a Tip Win8 sucks for Fastboot stuff so try to get Win7 Vista XP for this)
Reset your device with a paperclip/needle (about 2 cm down of your sdcard slot) and hold vol-down to enter fastboot
(the folowing i did at least 10 times already but didn't erase misc)
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
fastboot -i 0x0B05 reboot
* it also took a lot longer as it should:
C:\>fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
erasing 'system'...
OKAY [ 1.695s]
sending 'system' (800935 KB)...
OKAY [133.121s]
writing 'system'...
OKAY [153.973s]
finished. total time: 288.789s
im now setting my tab up to get back to CM (which initially caused this sh1theap due to autoupdate error, same as my A700 got bricked )
hope i could help you out!
cheers
-Buster <----(credits to him) Go to this link ---> http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12 because that's the guy that wrote this procedure from above (credits to him) :
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This part was me now -ozkrtech <--- (credits to me)
In addition to that, if you simply can't see your device using the command "adb devices" go check on device manager if you see a device called just "Transformer" with a yellow icon indicating it needs a driver, and manually update driver, select "browse my computer for drivers" and then select let me pick from a list of device drivers on my computer" there you will see a list of like 3 different drivers, one of them says "bootloader" and one of the others says "adb" (i think they self explain) but just in case try with each one of them you can keep on switching drivers until you get your device recognized by the command "adb devices".
You should be asking yourself... whats the right moment to do an "adb devices" command? well my tablet same as -Buster's tablet had the wrong recovery menu flashed (wrong bootloader version) and it just kept booting into the corrupted recovery (in my case TWRP) with the "can't mount anything" and "what's the password" issue. When you get to password screen just hit cancel and try the "adb devices" commando and you'll see it gets recognized with your device serial number.
Once your device gets recognized by "adb devices" command you will proceed to use "adb reboot-bootloader" command and the tablet will reboot into the menu that had 4 options but now have 3 options and its missing the fastboot option (don't panic) in the last bootloader it is auto-fastboot mode when you reach that screen with just 3 options in it now (yeah is the screen with the RCK option) at this point try "fastboot devices" command to see if your device gets recognized same as "adb devices" procedure, it should get recognized with a different serial number (don't know why, maybe that number isn't a serial number), at this time you are SO LUCKY! now you will follow what I posted at the beginning from that other dude ---> (-Buster) or follow his link --- > http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
And you'll have an unbricked tf300t in no time =) (I personally used the stock but newest Asus ROM) 4.2.1 (10.6.1.27.1) and it worked flawlessly.
**NOTE** don't turn off nor reset your device once you have formatted the partitions, no need for that (don't know what happends but it might get really hard bricked) just proceed to flash the stock rom after erasing the partitions.
I'm 100% positive this will work if your device is in same state as ours. (had TWRP for JB) then updated bootloader to version 4.2 and forgot to update twrp to version 4.2 or installed twrp version JB by mistake and lost fastboot and TWRP is asking password.
Hope it helps. Let me know your status and if it worked for you.
So I am in the same boat as I flashed the wrong twrp. My device shows up under adb devices and I can boot into the bootloader using adb reboot-bootloader. However, once there, I can not get the device recognized with fastboot. I have tried messing with the drivers like you suggested but nothing will get it to show up with fastboot. Anybody have advice on where to go from here?
So extra info. The device bootloops into twrp 2.6. The only way I can boot into fastboot mode is with adb reboot-bootloader and I can get into APX. I can also boot directly into my current ROM (Slim beta 3) by selecting android in the bootloader menu. I have tried flashing proper recovery through flashify, which is says was successful, but the wrong twrp never gets overwritten. Rebooting the device will send it back to twrp.
Thanks if anyone can help
Thanks, man! It took a while to find this thread, but this was exactly my problem. The adb driver in windows was the pre-solution to help get back to the fastboot server in the bootloader. Awesome information. Thanks again!
I have tried "adb reboot-bootloader" and then adb devices and fastboot devices and neither will show the tab listed while the tab reaches that screen with just 3 options. I have uninstalled reinstalled drivers, it does show in device manager as Asus Android Composite ADB Interface but when running the command it will not list the tablet. Any suggestions?
Hello!
A few days ago I tried to root my Asus TF300T because before that, I changed the lcd and the touchscreen from FPC-1 to G01 version. So I had to root and update touchscreen's firmware to 02-3011-4820.ekt. I already updated with last firmware from asus.com. First, I installed a TRWP recovery but was useless since the touchscreen doesn't worked. So I tried to rewrite CWM recovery. I reset it and I don't remember exactly if I begun to install or not CWM but when I tried to wipe data (Vol- + Power), the tablet has freezed. After a few minutes I did a hardware reset (pin hole). Since that, the tablet freeze with "Device Unlocked", Asus logo and nVidia. The device was already unlocked. I don't have any backup from it. No fastboot, no adb. Just APX mode. Is it possible to do something with it anymore? I tried BootTools2, extracted bloobs from last version of firmware, tryed to flash them with nvflash and wheelie but vainly. What is the next step? I'm a beginner!
Remember please I cannot go in fastboot recovery menu, only apx. Thank you in advance!
I can not thank you enough!!! my tablet is now working I honestly though it was done for aha THANK YOU!!!
Howdy, folks. I recently bricked my tablet thanks to a bad install of CWM, but following the OP's guide I was successfully able to reflash stock firmware and the device runs fine now.
However, upon reflashing said firmware, it became apparent to me (from reading various threads in the development subforum), that I would need to downgrade to an older firmware version to reflash TWRP. So I did that successfully, but now I am having a problem similar, or perhaps identical, to that of Bionicbowtieguy, in that ADB appears to be broken for my tablet. I have tried uninstalling and reinstalling the Asus usb drivers, in addition to reinstalling/updating all of the ADB software. Fastboot still works fine, but as such I'm unable to root using Motochop's rooting kit (I know there are other methods out there), nor am I able to flash a new recovery. I have also tried repeatedly reflashing the older stock in the hopes that ADB would magically start working again to no avail.
Does anyone have any suggestions to getting ADB to work for my tablet again? I have scoured the web, particularly these forums, for days looking for an answer, but haven't turned anything up yet. Any help would be greatly appreciated.
Gave back 10 years of my life that I lost once I discovered I flashed the wrong TWRP version. Can't thank you enough man.
Kombatant said:
Gave back 10 years of my life that I lost once I discovered I flashed the wrong TWRP version. Can't thank you enough man.
Click to expand...
Click to collapse
Same here!
Thank you OP for making this a topic even if you didn't come up with it you made it a thread that has saved a few people like myself money and headaches. Literally I just stumbled on this thread 10 minutes after I told my wife is be Tablet shipping Black Friday. Thank you sir.
Thank you.
I did this on a hackintosh running OSX since on Win 8.1 fastboot kept crashing.
March of this year I bricked my tablet during that 1 week period where nobody knew that TWRP was broken + fastboot freezing.
I must have tried everything, Maybe that erase misc was the key factor for success.
I was about to sell this for what I could get or send it to asus, now I can use it again!
How are you guys getting your tablet into fastboot mode? I've tried power on with volume down, the reset hole with volume down, and letting the battery die then recharge, then power on with volume down... Nothing. What am I doing wrong?
Sent from my Galaxy Nexus using Tapatalk
Best thread ever!! You are a life saver !!! thank you!!
leris2 said:
Best thread ever!! You are a life saver !!! thank you!!
Click to expand...
Click to collapse
Indeed. You are a god among men. Thank you so much
This worked! I thought I was out of luck. Thanks a lot.
I accidentally flashed an incomparable version of twrp. It would only boot straight into recovery and I couldn't get into recovery. TWRP kept asking for a password even though I never set one up and it wouldn't mount the internal storage or sd card.
I had to follow the instructions at the bottom to intall the drivers so adb and fastboot to work. After that I followed the instructions at the top.
The only thing different I did was skip the "fastboot erase boot" step. I was afraid that would really brick my device if I screwed up (Does this really erase the bootaloader leaving the device with no bootloader?).
Just wondering how long the fastboot window sits displaying < waiting for device > ? All my drivers are ok and I my pad shows up fine as a fastboot device in windows.
Cheers
Fastboot
Bolandk said:
Just wondering how long the fastboot window sits displaying < waiting for device > ? All my drivers are ok and I my pad shows up fine as a fastboot device in windows.
Cheers
Click to expand...
Click to collapse
They do not sit at all they will go right to it. You must not have the right combination yet. Keep trying.
Took me awhile to get the link.
norm883
FIXED!
BY GOD, I have no words for how incredible grateful I am right now! You not only saved my TF300T's life but also a lot of money for me and gave me another lesson of Android insight.
Thanks so much for this!
Let me know if I can return the favor somehow!
Regards,
(a very happy) philleicht
Hi. I think I'm having the same problem as some of the others in this thread.
Background: Tablet is unlocked, JB Rom (Paranoid Android) was installed since March, along with TWRP recovery. In preparation of installing CM11, I used Android Terminal Emulator to install the latest TWRP from a *.blob file, but I found that the latest TWRP is still not CM11-ready...
Setup to Issue: Last night, I decided I wanted to put CM11 on my TF300T. TWRP doesn't have a compatible recovery out for CM11 (install of CM11 rom fails every time), so I reinstalled the paranoid android ROM, and attempted to get the latest recovery from clockworkmod. On cwm's website, they only have choices for "transformer" "transformer prime" and "transformer infinity" which, when downloaded, have tf101, tf201, and tf700 in their filenames. (No tf300, that is)
So... I attempted to install the tf201 recovery (closest to mine, right?) by renaming the file cwm.blob, and using android terminal emulator to install it, the same way I did with TWRP. The first few times I tried and rebooted into recovery... TWRP was still installed... which was weird to me.
The big problem: Ultimately... when I rebooted the tablet, I just see the initial "ASUS" screen with "The Device is UnLocked." in the top-left corner. When I hold the power button to turn it off... it powers back on within a few seconds, and stays at the "ASUS" screen again. It will not stay off... and will not show anything but the "ASUS" splash screen. (With one exception, described later - "the only ray of hope...") If I hold the volume up or down buttons when powering on the device, absolutely nothing different happens. (since it doesn't STAY off... I've tried all kinds of different combinations of pushing/holding the appropriate buttons for when the tablet comes back on) IMPORTANT: I never see the "three icons" as expected when holding the volume button(s). No RCK, USB, etc... when the unit turns back on, it goes to the ASUS screen, and stays there until the battery dies. As a result... I can't get into recovery, fastboot, or APX or whatever in the traditional way.
Pressing the reset button alone, or reset + volume down has the effect of temporarily turning off the unit and then on again, the same as holding the power button to turn it off and letting it turn itself back on again.
The only ray of hope that I have is that *sometimes* if I press reset + volume up with the USB cable connected to a computer... the screen will STAY BLACK, but the "device connected" sound will play on my PC (Win 7 x64) as if I just plugged the tablet into USB on my computer, and I will get a message that it's trying to install an APX device. However, it eventually tells me that the device driver could not be installed. The screen on the tablet stays black in this case... until I reset it, hold the power button, etc.
So... I'm not opposed to (or unfamiliar with) using fastboot or any other command-line app to resurrect my tablet... I just haven't been able to get it into a condition that I can try something like that yet.
Is there any hope for my tablet? Somebody please help me. I'm open to sending a few bucks via paypal or google wallet to anyone that can lead me to a resolution. That would be cheaper than buying a new tablet... not to mention the priceless value of the progress I have in Fieldrunners 2. lol.
Thanks for your time!
~Ryan
same problem reboot back to twrp
well i may be stupid because i can't understand why i have tried a couple of commands and i still get the same problem reset volume down still goes back to twrp and ask for a password can someone please explain this in alittle more detail and what commands i also get the waiting for device in my commands is there another way to push these files into this device tf201 please help is there a way to do something in the twrp recovery like terminal command
I was a fool for flashing wrong recovery!
DrPhant0m said:
Hi. I think I'm having the same problem as some of the others in this thread.
Background: Tablet is unlocked, JB Rom (Paranoid Android) was installed since March, along with TWRP recovery. In preparation of installing CM11, I used Android Terminal Emulator to install the latest TWRP from a *.blob file, but I found that the latest TWRP is still not CM11-ready...
Setup to Issue: Last night, I decided I wanted to put CM11 on my TF300T. TWRP doesn't have a compatible recovery out for CM11 (install of CM11 rom fails every time), so I reinstalled the paranoid android ROM, and attempted to get the latest recovery from clockworkmod. On cwm's website, they only have choices for "transformer" "transformer prime" and "transformer infinity" which, when downloaded, have tf101, tf201, and tf700 in their filenames. (No tf300, that is)
So... I attempted to install the tf201 recovery (closest to mine, right?) by renaming the file cwm.blob, and using android terminal emulator to install it, the same way I did with TWRP. The first few times I tried and rebooted into recovery... TWRP was still installed... which was weird to me.
The big problem: Ultimately... when I rebooted the tablet, I just see the initial "ASUS" screen with "The Device is UnLocked." in the top-left corner. When I hold the power button to turn it off... it powers back on within a few seconds, and stays at the "ASUS" screen again. It will not stay off... and will not show anything but the "ASUS" splash screen. (With one exception, described later - "the only ray of hope...") If I hold the volume up or down buttons when powering on the device, absolutely nothing different happens. (since it doesn't STAY off... I've tried all kinds of different combinations of pushing/holding the appropriate buttons for when the tablet comes back on) IMPORTANT: I never see the "three icons" as expected when holding the volume button(s). No RCK, USB, etc... when the unit turns back on, it goes to the ASUS screen, and stays there until the battery dies. As a result... I can't get into recovery, fastboot, or APX or whatever in the traditional way.
Pressing the reset button alone, or reset + volume down has the effect of temporarily turning off the unit and then on again, the same as holding the power button to turn it off and letting it turn itself back on again.
The only ray of hope that I have is that *sometimes* if I press reset + volume up with the USB cable connected to a computer... the screen will STAY BLACK, but the "device connected" sound will play on my PC (Win 7 x64) as if I just plugged the tablet into USB on my computer, and I will get a message that it's trying to install an APX device. However, it eventually tells me that the device driver could not be installed. The screen on the tablet stays black in this case... until I reset it, hold the power button, etc.
So... I'm not opposed to (or unfamiliar with) using fastboot or any other command-line app to resurrect my tablet... I just haven't been able to get it into a condition that I can try something like that yet.
Is there any hope for my tablet? Somebody please help me. I'm open to sending a few bucks via paypal or google wallet to anyone that can lead me to a resolution. That would be cheaper than buying a new tablet... not to mention the priceless value of the progress I have in Fieldrunners 2. lol.
Thanks for your time!
~Ryan
Click to expand...
Click to collapse
I have exactly this! I hope someone knows the answer for this issue. Else the tablet will learn how to fly!
I tried to push the reset button as described earlier but nothing changes. Not able to go into recovery Just stuck at ASUS in the middle NVidia in the bottomright corner en upperleft corner 'this device is unlocked'
Hello!
Looks like my Fire HD 10 tablet got kinda bricked...
I can't get into the Recovery Mode to do factory reset.
This is after I've installed TWRP.
The tablet powers on and you can see the Amazon logo, when it disappears instead of going into Recovery it restarts and the Amazon logo pops up again, then goes into Fire logo and stays there forever.
This started happening when I was trying to follow one of the guides where you have to input commands through Linux Terminal.
I run the "sudo ./step-1.sh" command and since then the tablet is not loading all the way up anymore.
Is there a way I could get it to work with some ADB magic or something?
Huge thanks for any help!
Have a great rest of the day!
Is step-1.sh all you did or did you run the other scripts as well?
What was the output of the script?
If you try to enter recovery using the right volume-button and power it doesn't enter recovery?
Hey k4y0z!
My tablet was still operating when I input the command ./step-1.sh, then it turned off and on again to run the script as I've expected it to do.
But this is the point where it never went beyond the Fire logo again.
It did the same thing as when I try to enter Recovery Mode (yes, using the volume and power buttons), that is, showing the Amazon logo then it turns itself off and on to show the Amazon logo again and going to infinite Fire logo.
It looks like it tries to enter Recovery but can't and resets to try and load up normally.
I think the script was trying to enter Recovery too to do its thing but as this mode can't be entered it reset but this time being unable to even load up the system.
I could access Recovery before but not since I've installed TWRP and now the tablet can't access it too.
I recon the only way to fix this is if there's a way to somehow force Factory Reset with some software or a brute ADB command.
Though whenever I try to send a command this way it says <waiting for device> so it probably can't be done without loading up the system first.
I tried to run other scripts but nothing happened, the tablet was not responding to them.
The output of step-1.sh had no errors though I can't remember what it said exactly.
crowbringer said:
Hey k4y0z!
My tablet was still operating when I input the command ./step-1.sh, then it turned off and on again to run the script as I've expected it to do.
But this is the point where it never went beyond the Fire logo again.
It did the same thing as when I try to enter Recovery Mode (yes, using the volume and power buttons), that is, showing the Amazon logo then it turns itself off and on to show the Amazon logo again and going to infinite Fire logo.
It looks like it tries to enter Recovery but can't and resets to try and load up normally.
I think the script was trying to enter Recovery too to do its thing but as this mode can't be entered it reset but this time being unable to even load up the system.
I could access Recovery before but not since I've installed TWRP and now the tablet can't access it too.
I recon the only way to fix this is if there's a way to somehow force Factory Reset with some software or a brute ADB command.
Though whenever I try to send a command this way it says <waiting for device> so it probably can't be done without loading up the system first.
Click to expand...
Click to collapse
step-1.sh doesn't flash TWRP, this only happens in step-2.sh.
In step-1 it resizes userdata and adds two new partitions, recovery stays untouched.
Are you sure recovery worked before step-1? It sounds like it was already broken.
The problem now is, that the userdata is invalid, since it has been resized, that should normally be fixed by doing a factory-reset via recovery, but since your recovery is inaccessible this fails.
You will have to open the device and do the unbrick-procedure: https://forum.xda-developers.com/showpost.php?p=79169423&postcount=2