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
Related
I tried to install TWRP last night. I had the img file in the same directory as fastboot, but I received an error message saying "Fastboot not found" I had followed the instructions on the TeamWin site for the Kindle. When I gave up and unplugged my Fire, it appeared fine, but then I rebooted and ever since I've been stuck on the "kindle fire" splash screen. I checked to make sure the drivers are still installed from when I rooted, they are, but my computer won't recognize my fire. I also just tried the new Kindle Fire Utility, running it with admin priveledges and I get message that Fastboot is offline and pressing 1 for Normal just tells me "Waiting for Device..... then The system cannot find the path specified". I also held the power button for 20 seconds to totally shut down and restarted, didn't help. Am I hosed?
Sounds like you are in fastboot (I can be wrong) first make sure you have fastboot installed on your computer (Guide: Link ) next is when its on the kindle splash screen run - fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
Thank you. I may be getting closer. That did something. I saw the teamwin logo, and now I'm on the yellow triangle. I am not unplugging my Fire yet. Is there a next step? I'll continue researching, but if you can help, I'd really appreciate it
good then your basically done. Just hold the power button down when you start up the kindle until it changes colors and then you will be in recovery mode, then just hit reboot in recovery mode and your good to go.
Also the yellow triangle is the bootloader firefirefire which is bundled with TWRP 2.0
Thank you. I found the answers here: http://forum.xda-developers.com/showpost.php?p=20421225&postcount=222. Rebooting my PC didn't do the trick, I actually had to shut it down for a few minutes and then I followed those instructions. All good and Twrp is verified as installed. Thanks again.
sweet, glad you got it all worked out.
Just did my first nanoid backup Takes up about 500 megs, but now I have the piece of mind! What we need now are some really good roms to choose. Maybe a replacement for Amazon video so we don't have to temp unroot! I think I've been spoiled by my EVO 3D
I failed so hard im not even going to say what i was doing wrong, i want to punch my self in the face lol. Disregard this thread
I was going o install a different rom and in the application settings it said apps were still using up a bunch of space so i flashed the stock rom again, then went into the settings and hit factory reset.
Now when i Boot it up it goes to TWRP menu. I try going into the MOUNT option to put a flashable rom on their but my device doesnt show up on my computer? So KF utility doesnt find it either...
help?
ok, for some reason it wont even show up in device manager as anything. I tried reinstalling the drivers with kindle fure utility but it does nothing..
I am now stuck at the same place as you...
You should use the kindle fire utility to change your bootmode
from Recovery to Normal
Ok, this is how I just fixed mine. Using the KFU, having the KF plugged in to your pc. Now open the KFU and go to the boot mode, hit one to put it in normal boot and it will say waiting on the device, restart the kindle and it will say that it sent the command in a very short window. After that it will still load into twrp, just reboot the system and it should load into the Kindle Fire after twrp has run it normal boot up.
I've successfully rooted my T-Mobile LG Leon, and I've successfully installed TWRP, but for the life of me, I can't get the phone to boot into recovery. I can RE-boot into recovery from TWRP manager, but I can't actually boot into it from a fully powered-down state. I've tried every combination of the power and volume buttons I can think of, and nothing ever works. Download Mode works, the factory restore menu works, but I CANNOT get into recovery. Is there a very specific set of instructions anywhere that I can follow?
EDIT: Okay, I finally figured it out: You need to actually select to do a factory reset, and it throws you into the recovery menu.
Yeah, it was because the stock recovery doesn't exist as a menu, when you're running stock and enter the adb command "adb reboot recovery" it will reboot to the "factory reset mode" and the actual file of this mode is stored on partition named "recovery". Choosing the factory reset option boots the custom recovery because it replaces the said " factory reset mode" and that's the trick.
You can access recovery from the powered off state by holding volume down and power on until you see the lg sign. Without letting go of volume down, depress on the power button before clicking it back in and holding both buttons in until you see twrp pop up.
If you reboot to recovery now, it''ll probally say secure booting error. Simply go to the Developer options and enable OEM Unlock and that'll make you boot to it
You boot in the download mode by holding the vol up 10 seconds and during this 10 seconds you insert the usb. The LG Leon brand screen will come on a minute then it will go into download mode. It says not to unplug until firmware is done updating. So I guess you should have your custom recovery or whatever before you do this. I have only got this far, and thusly it sits. All Dressd up with no where to go...haha
kruc Ire said:
You boot in the download mode by holding the vol up 10 seconds and during this 10 seconds you insert the usb. The LG Leon brand screen will come on a minute then it will go into download mode. It says not to unplug until firmware is done updating. So I guess you should have your custom recovery or whatever before you do this. I have only got this far, and thusly it sits. All Dressd up with no where to go...haha
Click to expand...
Click to collapse
can't find "enable OEM" at all in developer options. have phone hooked computer, and on, it's sending and receiving. No OEM. Isn't there.
See, I'm trying to root this without using KingUser. Since I found that it was pretty easy to do from the very beginning with Samsung, and I just don't see any way to do it here. I can't get ADB Devices command to see the phone.
kruc Ire said:
can't find "enable OEM" at all in developer options. have phone hooked computer, and on, it's sending and receiving. No OEM. Isn't there.
See, I'm trying to root this without using KingUser. Since I found that it was pretty easy to do from the very beginning with Samsung, and I just don't see any way to do it here. I can't get ADB Devices command to see the phone.
Click to expand...
Click to collapse
I think I have the same issue, but I rooted my phone using kingroot, I haven't tested the adb commands, I just want to use twrp but no luck, it says Secure booting error and I can't find OEM Unlock option in Developer Menu.
duffycop said:
I think I have the same issue, but I rooted my phone using kingroot, I haven't tested the adb commands, I just want to use twrp but no luck, it says Secure booting error and I can't find OEM Unlock option in Developer Menu.
Click to expand...
Click to collapse
I got a good way to get it rooted with SuperSU. Ran a command window script I found out there. It worked and now I have SuperSU root. I also figured out how to get into recovery. It looks as though my phone is not the standard LEON that people are talking about here. It's got a few designations, and the T Mobile site advertises a Leon that seems very similar and is called by the name most are using..
Anyhow my LG Leon is designated as a H320. It also carries a v10 desiganation, v10b. The v10 is variable from a-h or a-i. It would seem that once it is updated to 5.1.1 android it gets upped, and becomes unrootable. Mine being a v10b was rootable, but it took me a while to get used to it, and make the command window work.
Unfortunately for me one of many things I tried before getting it rooted, was ADB fastboot. And since this told me to wait for too long, I pulled the plug on it and pulled the battery to get back into "normal" operations. Perhaps I should have waited, because after finding out a few things about the phone, I discovered the true way to get it into recovery:
The real way into recovery for my phone, is to (from power off state) hold the volume up, a few seconds, then plug the USB cable which is going to the computer into the phone. While holding the volume up until it comes to recovery. This will activate the recovery, (Now for me it activates that fastboot command line...and does nothing else). This was the bit of information I could have used from the beginning, that no one knows. All these places tell you to hold the power and volume up, and then let off power when the screen changes, but that never worked even once. You just hold the volume, and plug the USB from computer. This works.
For me it goes into a "FASTBOOT" header at the bottom of the screen that never changes.
I believe it does this because of my unsuccessful attempt to fastboot it before. And it does not have the right driver to get recognized in the computer. So I'm screwed as far as the recovery goes now.
It is rooted though. And it doesn't seem to have any alternate ROMS available anyways. so we're dealing with the loss of the recovery.
When I do try to use an app such as TWRP manager or CWM (ROM) Manager to reboot into recovery, I get a "boot certification verification -1" error instead of the fastboot line at the bottom of the startup screen and it boots normally from there. So many people asked about this "boot certification verification -1" and NO answers are available anywhere online. So that's where it stands for this phone right now.
Anyone know what driver I should use to get the thing recognized in the computer? I have downloaded a zipped fastboot tools, and it won't get recognized inside the driver manager as "android" only as "unknown device" so I can't use that route....I'm thinking about doing a factory reset to try to erase the fastboot attempt. That may not help though. Anyone?
kruc Ire said:
I got a good way to get it rooted with SuperSU. Ran a command window script I found out there. It worked and now I have SuperSU root. I also figured out how to get into recovery. It looks as though my phone is not the standard LEON that people are talking about here. It's got a few designations, and the T Mobile site advertises a Leon that seems very similar and is called by the name most are using..
Anyhow my LG Leon is designated as a H320. It also carries a v10 desiganation, v10b. The v10 is variable from a-h or a-i. It would seem that once it is updated to 5.1.1 android it gets upped, and becomes unrootable. Mine being a v10b was rootable, but it took me a while to get used to it, and make the command window work.
Unfortunately for me one of many things I tried before getting it rooted, was ADB fastboot. And since this told me to wait for too long, I pulled the plug on it and pulled the battery to get back into "normal" operations. Perhaps I should have waited, because after finding out a few things about the phone, I discovered the true way to get it into recovery:
The real way into recovery for my phone, is to (from power off state) hold the volume up, a few seconds, then plug the USB cable which is going to the computer into the phone. While holding the volume up until it comes to recovery. This will activate the recovery, (Now for me it activates that fastboot command line...and does nothing else). This was the bit of information I could have used from the beginning, that no one knows. All these places tell you to hold the power and volume up, and then let off power when the screen changes, but that never worked even once. You just hold the volume, and plug the USB from computer. This works.
For me it goes into a "FASTBOOT" header at the bottom of the screen that never changes.
I believe it does this because of my unsuccessful attempt to fastboot it before. And it does not have the right driver to get recognized in the computer. So I'm screwed as far as the recovery goes now.
It is rooted though. And it doesn't seem to have any alternate ROMS available anyways. so we're dealing with the loss of the recovery.
When I do try to use an app such as TWRP manager or CWM (ROM) Manager to reboot into recovery, I get a "boot certification verification -1" error instead of the fastboot line at the bottom of the startup screen and it boots normally from there. So many people asked about this "boot certification verification -1" and NO answers are available anywhere online. So that's where it stands for this phone right now.
Anyone know what driver I should use to get the thing recognized in the computer? I have downloaded a zipped fastboot tools, and it won't get recognized inside the driver manager as "android" only as "unknown device" so I can't use that route....I'm thinking about doing a factory reset to try to erase the fastboot attempt. That may not help though. Anyone?
Click to expand...
Click to collapse
I dunno, I have the H340AR, with this phones happens the same that with the Samsung Galaxy Ace 3, there are, 3G versions, 4G versions, regional versions, etc.. GA3 have 7275R, 7275B, 7272L, 7272T, I dunno, maybe if we could get a device tree for a H340 and an H320 we could make some TWRP and CM compiling, but I just can't figure it out how to make a device tree or even where to begin..
I successfully rooted my H340AR with Kingroot, it works like a charm. I haven't tried fastboot and I tried to install TWRP in this link https://dl.twrp.me/c50/ but I get that F error "Secure booting error". I guess I have my bootloader locked, so I'm trying to figure out how to unlock my bootloader.
I'm trying to contact with some developers and see if anyone can help me build a device tree.
]
Hi, I have that same phone H340AR LTE. I rooted it with Kingroot and also tried to use TWRP to gen into recovery and got that Security error. I only pulled out the baterry and turn it on again so it booted normally. I made a factory reset because I read that it could be a problem of OTA firmware update. Then I installed TWRP and BusyBox again and tried to get into recovery from TWRP option. When I did that, it showed up the Android lying in his back with a red triangle. I pulled a out the battery again and yes, it seems very dumb and simple but it worked and could reboot the phone.
However, I can't get into recovery from TWRP yet. I read that the problem with us not being able to unlock the bootloader(we don't have the OEM option) is because Leon has Lollipop 5.0.1 and OEM is for 5.1.1
pedrovay2003 said:
I've successfully rooted my T-Mobile LG Leon, and I've successfully installed TWRP, but for the life of me, I can't get the phone to boot into recovery. I can RE-boot into recovery from TWRP manager, but I can't actually boot into it from a fully powered-down state. I've tried every combination of the power and volume buttons I can think of, and nothing ever works. Download Mode works, the factory restore menu works, but I CANNOT get into recovery. Is there a very specific set of instructions anywhere that I can follow?
EDIT: Okay, I finally figured it out: You need to actually select to do a factory reset, and it throws you into the recovery menu.
Click to expand...
Click to collapse
when i pressed factory reset all it did was to a factory reset even though i flashed twrp.img successfully... help?
lg leon h345 lollipop 5.1.1
This device has a locked bootloader. If you flash a custom recovery on it, it will not boot into recovery, but will report a security issue. You will lose all recovery functionality, including factory reset, adb, fastboot. If your phone fails to boot, you have a brick.
Hello,
before I get into detail with my current problem at hand, I want to say that I'm extremely new to flashing/rooting my tablet and in most cases am very dependent on guides and how-tos. That being said, I've search through this forum among others in order to get my problem solved but had no success so far. So your expertise is basically my last resort and hope.
I have a Lenovo Yoga 2 1050L, as stated above, and tried to root it yesterday using this guide. Unfortunately, I messed up when it came to the system's image from the custom ROM because I downloaded the original firmware for the 10'' version L instead of the further below mentioned recovery firmware in step 3 (though that link was dead anyway). Moreover, I also included the recovery.img in the custom flash process and not only the system.img and I think the error occurred while flashing the recovery partition.
Long story short, the flashing process failed and I was left with a non-booting tablet.
The status-quo is I can boot into the bootloader mode (power button + volume down) where it'll say "normal boot", "recovery mode" etc. at the top with the android figure lying on the ground with an open stomach.
With the help of the Fastboot Tethered Recovery Launcher I can use the T3 option to change the device status to "fastboot-online". From what I understood I can then enter recovery mode if pressing volume up (so I can do a data/cache wipe) but it says
"could not open sys/devices/virtual/backlight" and I couldn't figure out what that's supposed to mean or how I can solve it.
I also tried to flash it again with the stock rom downloaded from here with the Intel Phone Flash Tool 4.4.4.
But that always failed at the "fastboot -s <device> oem wipe ESP" operation. It failed to execute that command resulting in a timeout only to try it once again. After that second attempt ended in a timeout too, it went on to the next step "fastboot -s <device> oem start_partitioning" but that also failed, ultimately making the whole flash process fail.
The curious thing (for me, anyway) was that I could flash the boot.img, system.img and recovery.img individually (by going to "Custom Flash" in the Phone Flash Tool and then selecting only one of those images) and all three processes succeeded. However, I only got the success message on the Phone Flash Tool, the tablet itself got stuck during the first reboot during or after the flash process.
In fact, every boot/reboot results in the tablet being stuck at the display of the Lenovo Logo. Nothing happens after that, it just stays there.
This happens whenever I try to boot normally or boot straight into recovery mode (Power + Volume Up). The only way I can boot my tablet and actually do something with it is the bootloader mode (Power + Volume Down) but as stated above, from there I didn't manage to get anywhere else so far.
Another thing I have tried is to enter fastboot mode because I read that I can also recover from there. But whenever trying to enter fastboot mode the tablet's display goes black, then a small text says "Fastboot starting..." and that's it. Nothing happens after that, no additional text or new screen.
What I also noticed is that whenever the tablet reboots itself or if I try to boot/reboot it, the tablet is not in the list of available devices anymore if I enter "adb devices" or "fastboot devices" in my command line (with connected tablet). Only when I redo the process with the Fastboot Tethered Recovery Launcher (option T3), can I access the device with those commands again (at first I could access it with "adb devices", later on only with "fastboot devices" and to be honest, I don't know why that is).
I actually just want to wipe the data of the tablet and install the stock ROM again because I think there's just some corrupt data that keeps my tablet from booting normally. But right now I don't even know how to do that because everything I've tried so far didn't work. Not even starting the tablet with the so-called "hard reset" (Power + Volume Down + Volume Up) worked, I only got a black screen in that case.
Because I tried to solve this problem myself all day yesterday, my tablet is now also down to about 20% of battery and I don't know if I can charge it up without a proper ROM installed (probably not). So that's another factor that's hindering me from trying out other steps.
I know this is a lot of text but I still hope there's someone out there who can help me with my problem. I am at my wit's end and would highly appreciate anyone who has knowlegde about this situation with this tablet helping me.
Best regards and thank you in advance
XShunyaX
Hey all, I recently flashed a new rom on my phone, which required me to factory reset my ticwatch I'm order to reconnect.
Upon doing to the first time, everything seems to have gone well, but had trouble connecting to the device. So I ran another factory reset. Since that one, I've been stuck in a boot loop.
I see the "device software can't be checked for corruption" screen for about 20 seconds, and then it vibrates, screen turns off, then I see the same screen again. And so on.
I tried letting the battery go to nothing and trying again, seems to be the same issue. I'm letting it charge and bootloop for now in case maybe I just don't have enough juice to make it through boot.
It is rooted, with custom ROM (followed a guide on this forum somewhere about half a year ago, was running great) and TWRP installed (at least it was, I've been unable to get to the recovery screen since the boot loop started). Cannot see it in adb ever in this process.
Anyone have any other suggestions? I remember the Samsung notes had a special USB tool that would bridge a couple pins to immediately go to recovery, is there a similar option here?
Can you get in usb mode,or fastboot or recovery maybe?There is solution..dont worry.I ghuess adb dont work,but you cant go to fastboot mode and boot twrp image and get in twrp recovery..in twrp recovery you need backup file..If you cant do that,we are going to another solution..
Yeah, I can't - via any combination of button holding - get into any booted mode. No recovery, no fastboot, nothing. If anything, some buttons seem to make it circle boot faster .
nieminen432 said:
Yeah, I can't - via any combination of button holding - get into any booted mode. No recovery, no fastboot, nothing. If anything, some buttons seem to make it circle boot faster .
Click to expand...
Click to collapse
,Yeah tough situation,and when you connect it to pc in that "broken mode" -boot loop and open adb shell on pc ,comand adb devices or fastboot devices,does it show device?When you screwed boot and you have twrp there must be option to get in twrp.One trick more go to manage devices in pc find your device if unknown you right klick on it,update drivers,manually,and then choose android,then android adb install device.
KristijanKG3 said:
,Yeah tough situation,and when you connect it to pc in that "broken mode" -boot loop and open adb shell on pc ,comand adb devices or fastboot devices,does it show device?When you screwed boot and you have twrp there must be option to get in twrp.One trick more go to manage devices in pc find your device if unknown you right klick on it,update drivers,manually,and then choose android,then android adb install device.
Click to expand...
Click to collapse
I tried adb devices, but not fastboot devices, thanks for the idea, I'll give it a go.
nieminen432 said:
I tried adb devices, but not fastboot devices, thanks for the idea, I'll give it a go.
Click to expand...
Click to collapse
Maybe it wont work,but if doesnt,we figure out something..Bootlop is not the end of your device..
No go on either command. Nothing shows up.
I'm half wondering if it's my battery at this point. I think I'm getting a new watch for Christmas anyway, so not a huge loss. But happy to keep trying if anyone else has any ideas.