I need some consolation. I unlocked my tablet using the asus unlocker. I did not have a custom rom installed but it was rooted. One day i needed more space on my tablet, i decided to be lazy and instead of deleting the apps i would factory reset the device. i used cwm as the factory reset instead of the one in the system. during the reset my tablet's battery dies. now it is completely bricked it will boot to the screen saying that the tablet is unlocked and won't progress past that. i have tried every combination of buttons and i cannot get into the cwm recovery nor any other screen. The tablet is completely unresponsive. Is there a way that i could open the tablet take the hard drive and format it on my computer. Then replace it with new firmware and boot loader? Any other suggestions would be greatly appreciated. Thanks.
I recently found out I soft bricked my LG Optimus V. I rooted it and it worked just fine but then I installed a font from "Font Installer *ROOT*" and after it rebooted it got stuck at the "ANDROID" screen. The only way I can turn on my phone is by removing the battery, going into recovery, clearing cache and then factory reset but I cant seem to lock the device without another automatic reboot which results then in a black screen. I looked online on how to fix it and from what I found out I need to backup the device and install a new ROM? How exactly do I do that?
Alright, so after having my Fire HD 6 rooted for a few months I started experiencing some random restart issues. I decided to reset to Factory Defaults as I believe that it doesn't touch root (Please verify that one.)
Whenever I clicked on Facotory Reset, however; it immediately restarted and DID NOT RESET.
Then I tried to boot into TWRP and just reflash 4.5.3 (Downgrade) but when I tried to boot into recovery nothing happened, it just booted as normal. Thinking that it was just an error on my part, liking the wrong buttons, etc, I tried running 'adb reboot recovery'
This yielded the same result, just a normal reboot.
I have since unrooted my Kindle to try to update to 5.0.1 (To downgrade again)
Upon trying to update, I restart with no change just like in Factory Reset.
This leaves me with no Root, and no Recovery.
Next I tried using Fastboot to reset it, which now leaves me in a reboot loop that's stuck on the "Fire" logo.
TL;DR:
I have no root, I cannot get into recovery, I cannot access bootloader since ADB doesn't have permission without me giving it (Again, bootloop)
Overall, I'm kind of screwed, any help appreciated.
KeybladePaladin said:
Alright, so after having my Fire HD 6 rooted for a few months I started experiencing some random restart issues. I decided to reset to Factory Defaults as I believe that it doesn't touch root (Please verify that one.)
Whenever I clicked on Facotory Reset, however; it immediately restarted and DID NOT RESET.
Then I tried to boot into TWRP and just reflash 4.5.3 (Downgrade) but when I tried to boot into recovery nothing happened, it just booted as normal. Thinking that it was just an error on my part, liking the wrong buttons, etc, I tried running 'adb reboot recovery'
This yielded the same result, just a normal reboot.
I have since unrooted my Kindle to try to update to 5.0.1 (To downgrade again)
Upon trying to update, I restart with no change just like in Factory Reset.
This leaves me with no Root, and no Recovery.
Next I tried using Fastboot to reset it, which now leaves me in a reboot loop that's stuck on the "Fire" logo.
TL;DR:
I have no root, I cannot get into recovery, I cannot access bootloader since ADB doesn't have permission without me giving it (Again, bootloop)
Overall, I'm kind of screwed, any help appreciated.
Click to expand...
Click to collapse
Please help.... I see you random viewer >.>
I think if someone had an answer they would have posted. Unfortunately, fastboot doesn't work on the 2014 HDs, and it sounds like that's what put you into the bootloop. At this point I think your only option is to contact Amazon for replacement if you're still under warranty.
DoLooper said:
I think if someone had an answer they would have posted. Unfortunately, fastboot doesn't work on the 2014 HDs, and it sounds like that's what put you into the bootloop. At this point I think your only option is to contact Amazon for replacement if you're still under warranty.
Click to expand...
Click to collapse
You're sure fastboot doesn't work? I believe I have used it prior to this with no issues. (By the way, warranty is out >.<)
KeybladePaladin said:
You're sure fastboot doesn't work? I believe I have used it prior to this with no issues. (By the way, warranty is out >.<)
Click to expand...
Click to collapse
Bootloader screen doesn't indicate fastboot mode. Getvar doesn't return anything. If flash commands worked, I'm sure someone would have reported it.
If you haven't tried all button combinations, you should. (You know, hold down power; try power and vol down; try all three.) Without recovery that's all I can suggest. Sorry this happened.
I got the same problem too.
I tried to root and install gapps follow this tutorial. Everything work perfectly.
One day, my Fire's battery was empty and it turned off. I charged it and when it started, it falt in bootloop. The screen show amazon about 8sec and reboot.
I booted into twrp and flashed only 2 files update-kindle-full_ariel-20.5.2.2_user_522053520 and supersu, try to make it work but it didn't
Now, when i hold power button , "Amazon" and then "Fire" appear and it stuck there.
I tried to get into recovery by power and volume+ but didn't work, the screen show "Amazon" and reboot and stuck on "Fire" again.
What should I do now?
Sorry about my English.
I installed Kingroot and used SuperSu-Me to replace Kingroot with the regular SuperSu. I take it that it did not work.
I rebooted and the phone stays at "Starting Apps".
There was nothing I could do about that so I Wiped Cache and Factory Reset from the built in recovery.
Reboot and it is stuck at "Starting Apps"
Reboot again and it get's stuck at "Upgrading Contacts"
Reboot again it is stuck at "Starting Apps"
After that it will not start again until I Wipe Data and Factory Reset again. The whole process starts again.
I am used to the Motorola phone where you can install an aftermarket recovery but I can't find anything on this phone.
I use Linux all of the time but I have a hard drive with Windows on it if I need with the Phone drivers.
Any help will really be greatly appreciated.
I'm in the same situation with a Vodafone Speed tab 6.
Used Kingroot and tried to replace it with SuperSU using Super Sume, now stuck on boot loop, can't even turn the tablet off.
Can't access recovery to do factory reset either.
Anyone have any ideas?
Thanks.
If you ever find a solution please post it here.
Ok so, a bit of background, I'm on a Vodafone speed tab 6 (vf-1397) running on a root using kingoroot converted to super sume using the app, everything was running fine as such I decided to start looking for apps to use when rooted and ended up coming across jrummyapps boot animations As such I thought, "oh that looks cool let's get that" being naïve and not having any recovery boot loaders installed because I only found out about them after I got into a boot loop. So I proceeded to test a few and they all worked till I got to the third, it proceeded to lock it into a boot loop and now I have no clue what to do, is there anything that I can do, I've tried everything in the recovery menu and nothing. Any help would be highly appreciated I did do a factory reset so it's not currently rooted it's just stock with a custom boot animation that I can't seem to get rid of. Thank you. If all else fails I'll take it to a local Vodafone store when I get back from my holiday.
Another thing I should add currently from my device I can
-reboot system now
-wipe data/factory reset
-wipe cache partition
-power down
-enable adb
Update on current status.
I've found a stock rom for the device and now have the files however, i didn't have usb debugger turned on before it got stuck in a boot loop so, are there any alternative ways of saving it or have i completely messed up?
I know its grave digging at this point but ........
load in recovery and select start adb
then select restart
the device will now load with an unsecured adb connection active