Related
Hello all,
I rooted my HTC One XL a couple weeks back, installed CM10 (all was working fine), and in the process of installing the latest CM10 nightly, something went wrong. Flashed boot.img, then rom, then gapps. Wiped cache and dalvic cache, asked TWRP to restart system. This is where it's stuck now. It won't go past the htc logo, and I can't get into the bootloader by holding down power+vol down.
What did I do wrong? Is this fixable? Any help is greatly appreciated!
H8rift is working on a solution right now. If you can flash back to a backup? I would do so.
Sent from my One X using xda premium
---------- Post added at 10:52 PM ---------- Previous post was at 10:51 PM ----------
You can't get into recovery?
Sent from my One X using xda premium
vowelsounds said:
Hello all,
I rooted my HTC One XL a couple weeks back, installed CM10 (all was working fine), and in the process of installing the latest CM10 nightly, something went wrong. Flashed boot.img, then rom, then gapps. Wiped cache and dalvic cache, asked TWRP to restart system. This is where it's stuck now. It won't go past the htc logo, and I can't get into the bootloader by holding down power+vol down.
What did I do wrong? Is this fixable? Any help is greatly appreciated!
Click to expand...
Click to collapse
First off, can you get into TWRP, and do you have a backups of the time before you flashed the rom. When you hold power+vol down are you holding power until the home back and kill app buttons flash 6 times then release and hold vol down around 7 seconds till you see the screen with android skateboarders(Bootloader)
Second, I think their is a kit (Hasoons) Which you can try to boot you into bootloader or twrp recovery. But if your phone powers on, then i think your device is not a paperweight yet so dont worry to much as i think it can be fixed.
vowelsounds said:
Hello all,
I rooted my HTC One XL a couple weeks back, installed CM10 (all was working fine), and in the process of installing the latest CM10 nightly, something went wrong. Flashed boot.img, then rom, then gapps. Wiped cache and dalvic cache, asked TWRP to restart system. This is where it's stuck now. It won't go past the htc logo, and I can't get into the bootloader by holding down power+vol down.
What did I do wrong? Is this fixable? Any help is greatly appreciated!
Click to expand...
Click to collapse
It is fixable.
I did the same thing with my phone. Now I am successfully running ViperXL 2.1.2
Are you able to "fastboot oem lock" from the fastboot cmd prompt?
WhatTheAndroid? said:
First off, can you get into TWRP, and do you have a backups of the time before you flashed the rom. When you hold power+vol down are you holding power until the home back and kill app buttons flash 6 times then release and hold vol down around 7 seconds till you see the screen with android skateboarders(Bootloader)
Second, I think their is a kit (Hasoons) Which you can try to boot you into bootloader or twrp recovery. But if your phone powers on, then i think your device is not a paperweight yet so dont worry to much as i think it can be fixed.
Click to expand...
Click to collapse
I can't get into TWRP, and I have backups on the device. I am sorry for being a dummy, but you're saying the manual way to enter the boot loader is to hold power+voldown for 6 flashes, then release the power button but hold the voldown for 7 more seconds? I've just been holding down both for the full 15 flashes. I am going to look up Hasoons rn.
THANKS!!
vowelsounds said:
I can't get into TWRP, and I have backups on the device. I am sorry for being a dummy, but you're saying the manual way to enter the boot loader is to hold power+voldown for 6 flashes, then release the power button but hold the voldown for 7 more seconds? I've just been holding down both for the full 15 flashes. I am going to look up Hasoons rn.
THANKS!!
Click to expand...
Click to collapse
You are supposed to hold Power and Volume Down until the screen shuts off, then let go of power and continue holding volume down
vowelsounds said:
I can't get into TWRP, and I have backups on the device. I am sorry for being a dummy, but you're saying the manual way to enter the boot loader is to hold power+voldown for 6 flashes, then release the power button but hold the voldown for 7 more seconds? I've just been holding down both for the full 15 flashes. I am going to look up Hasoons rn.
THANKS!!
Click to expand...
Click to collapse
So your saying you can't get into bootloader but, you got into TWRP?
The correct way to get into bootloader is hold power+vol down until screen goes off, then release power button.
If that doesn't work you can try to open bootloader through the fastboot cmd prompt.(if you ahve Win7 just open the file where fastboot is, hold shift+right click and you can open the prompt from there)
Myrder said:
It is fixable.
I did the same thing with my phone. Now I am successfully running ViperXL 2.1.2
Are you able to "fastboot oem lock" from the fastboot cmd prompt?
Click to expand...
Click to collapse
Just tried this, cmd prompt reads "waiting for device". I am glad to know someone else got out of this :/
absolutelygrim said:
You are supposed to hold Power and Volume Down until the screen shuts off, then let go of power and continue holding volume down
Click to expand...
Click to collapse
What he said, but after your phone powers off, when i held it for around 7 more seconds, it booted into bootloader when i did it .But try both methods.I was stuck in a bootloop as well, you will be fine. I forgot commands for fastboot, but if anyone wants to tell them to him he could prob get into fastboot by command prompt mabye?
vowelsounds said:
Just tried this, cmd prompt reads "waiting for device". I am glad to know someone else got out of this :/
Click to expand...
Click to collapse
type "fastboot devices"
your serial number should be on the screen if fastboot recognizes your phone. but I was always able to get into bootloader through commands on the phone.
Also, I can't thank Absolutelygrim and a few others whom I can't think of their names for helping me out of that situation.
ANYTHING Absolutelygrim says, I would listen and take note.
Myrder said:
So your saying you can't get into bootloader but, you got into TWRP?
The correct way to get into bootloader is hold power+vol down for 6 flashes, then release power button.
If that doesn't work you can try to open bootloader through the fastboot cmd prompt.(if you ahve Win7 just open the file where fastboot is, hold shift+right click and you can open the prompt from there)
Click to expand...
Click to collapse
No I couldn't get into either, but I just did the power+voldown until screen off then hold vol down thing, and I got into bootloader and from there to recovery. I am going to flash a backup &c &c...
You people are so amazing!! Saved my life! Thank you, Thank you, Thank you, Thank you!
vowelsounds said:
No I couldn't get into either, but I just did the power+voldown until screen off then hold vol down thing, and I got into bootloader and from there to recovery. I am going to flash a backup &c &c...
You people are so amazing!! Saved my life! Thank you, Thank you, Thank you, Thank you!
Click to expand...
Click to collapse
Glad your device is back, good job. Hope i helped.
vowelsounds said:
No I couldn't get into either, but I just did the power+voldown until screen off then hold vol down thing, and I got into bootloader and from there to recovery. I am going to flash a backup &c &c...
You people are so amazing!! Saved my life! Thank you, Thank you, Thank you, Thank you!
Click to expand...
Click to collapse
Is there a way to close a thread? I've never done this before :/
Thanks to all of you again!
vowelsounds said:
No I couldn't get into either, but I just did the power+voldown until screen off then hold vol down thing, and I got into bootloader and from there to recovery. I am going to flash a backup &c &c...
You people are so amazing!! Saved my life! Thank you, Thank you, Thank you, Thank you!
Click to expand...
Click to collapse
It's always best to Nandroid before you flash a ROM.
I didn't and I almost made my phone into a very expensive paperweight. Thank god for RUUs.
I also tried to flash a ROM that was for the international version and not the XL which is our phone.
Mods will eventually Close it, just ingnore the thread and it will be closed soon.
If you want to, I know posting a thread in here can amount to a long wait time, just shoot me a PM and I'll give you my email. I get that directly to my phone so I'll be able to reply a lot quicker.
I have the same problem as this guy, but when I hol the volume down button, it has no effect... I hold vol down and power, lights flash 15 times, I keep holding volume down while phone reboots, but no matter how long I hold it down, it just stays at the HTC legal screen.
Was running CM 10.0, and updated to 10.1 (9-3-2012 nightly) with 3-03-2013 GAPPS, via TWRP. Made a backup before flash, Installed both the zips succefully, pressed reboot, and now it doesn't get past the legal screen, and no button pressing is getting me back to TWRP =(
I replaced the screen once, and the volume buttons behaved differently after I re-assembled. Both the buttons work, but they act differently. Pressing vol down or vol up both bring up the volume dialog, but instead of increasing or decreasing the amount, it swtiches between mute and non mute. So I'm thinking the button is not actually doing a 'volume down' action. Any thoughts?
AND, how do you actually turn this device off? It keeps turning itself back on after the 15 flashes.
Thanks for any help.
new developer need 10 posts in general discussion sry
Hello, just to start I have read through probably 100 post regarding similar issues but none are working. I have the ATT Htc one x EVITA 3.18 version. I did the super CID unlocked my bootloader through htc dev, flashed twrp recovery, and got a custom rom, gapps etc.. in twrp I wiped all data,system,cache, factory reset. Then flashed my rom and gapps (being kinda new to HTC devices I didn't flash the boot.img from the rom) now my phone after restarting just continues a bootloop (HTC Quietly Brilliant) screen, then powers off repeating this over and over.. I tried holding the volume down with the power button it just loops again, the I tried some other suggestions like holding power and vol down until the flashes stop and releasing power while continuing to hold volume down, again loops, then tried using volume up as well...none of these are working I don't understand what happened and why I can't get into any of these? I did not run any RUU. I tried using adb but of course i cant get into fastboot or anything so the phone is not recognized. If anyone could please help I really do appreciate it. I know this has been all over the threads but I read for the past 3 hours and could not get anything to work.. Thanks in advanced for any help it is much appreciated. :crying:
First of all, don't hold volume up and power, that's bad news. Trying random button combinations is a really bad idea. While it's looping just hold volume and the next time it starts again it should reach the bootloader.
Sent from my Evita
timmaaa said:
First of all, don't hold volume up and power, that's bad news. Trying random button combinations is a really bad idea. While it's looping just hold volume and the next time it starts again it should reach the bootloader.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the reply timmaaa... I usually would not try the other button presses just someone else had said that worked for them, but thanks for the advice. I did try what you said and just holding the volume down button, let it bootloop, and keep holding and it just continues to bootloop :/ it stay off for about 20 seconds the same then bootloops, with the htc screen for about 5 seconds the rinse and repeats D**n this thing is annoying. Any other Ideas? Thanks again man appreciate it.
if you are SOFF u can go for RUU?
Sonone said:
if you are SOFF u can go for RUU?
Click to expand...
Click to collapse
No I'm still s-on I didn't try to RUU cus I read it would brick..but seems I'm somewhat bricked anyway:silly:
sensei_777 said:
No I'm still s-on I didn't try to RUU cus I read it would brick..but seems I'm somewhat bricked anyway:silly:
Click to expand...
Click to collapse
are you sure you did get the SUPER CID cause if its not then you can RUU your device!
cause if you are not SUPERCID get a matching RUU or a latest version meant for your device!
only if you could somehow manage your phone to get recognized by a PC etc then you could flash boot.img with some toolkit etc and everything would have been fine!
but unless some expert actually figures out your problem dont RUU!
i really wonder whats obstructing the boot loader access!??
please let me know if u can get your device back to normal!
Sonone said:
are you sure you did get the SUPER CID cause if its not then you can RUU your device!
cause if you are not SUPERCID get a matching RUU or a latest version meant for your device!
only if you could somehow manage your phone to get recognized by a PC etc then you could flash boot.img with some toolkit etc and everything would have been fine!
but unless some expert actually figures out your problem dont RUU!
i really wonder whats obstructing the boot loader access!??
please let me know if u can get your device back to normal!
Click to expand...
Click to collapse
I had to change the CID to unlock the bootloader on htc dev, its like 11111 so that is super CID right?
Yea I've tried everything to get to adb since I am familiar with adb but its a no go none of the tool kits or even manual cmd is recognizing the device.. I had a one x just like this before and never had the problem getting into bootloader so I don't really get what is blocking it. Only thing I had done was flash twrp recovery, wiped data/factory reset, system and cache, then flashed the rom as one usually would and gapps, just I had forgot about these phones needing you to flash the boot.img. that is all I did to it. Kinda sucks I just got this thing yesterday from a friend too.
Yes, 11111111 is SuperCID. In any case I probably wouldn't attempt an RUU while the phone is this unstable, could be quite dangerous. It's possible the "adb reboot bootloader" command might work if you catch it at the right time in the boot cycle.
Sent from my Evita
timmaaa said:
Yes, 11111111 is SuperCID. In any case I probably wouldn't attempt an RUU while the phone is this unstable, could be quite dangerous. It's possible the "adb reboot bootloader" command might work if you catch it at the right time in the boot cycle.
Sent from my Evita
Click to expand...
Click to collapse
Thanks bud, well I can't get it to catch even using super finger speed cmd'ing lol.. oh well.. I'm not gonna try anything else other than the usual ways to get into bootloader until someone else has some idea what might be blocking it from entering. Is there anyway to turn it off? its just restarting over and over with the bootloop. Or does one just let it go dead? I suppose worse case senario sending it for Jtag would fix it right? thanks again to the both of you.
I believe in the command window your can press the down key to give the previous command again, so if you hit down and enter one after the other (spamming it) you might have a chance. I'm really surprised that continually holding volume down during the loop process isn't getting you to bootloader, that's very strange. There's no way to turn it off. But, it usually burns through a fair bit of battery during a boot loop so you could wait for it to die completely, charge it for a couple of hours, and then try the volume down + power combination to get to the bootloader. I hope it works, let us know how you go.
Sent from my Evita
timmaaa said:
I believe in the command window your can press the down key to give the previous command again, so if you hit down and enter one after the other (spamming it) you might have a chance. I'm really surprised that continually holding volume down during the loop process isn't getting you to bootloader, that's very strange. There's no way to turn it off. But, it usually burns through a fair bit of battery during a boot loop so you could wait for it to die completely, charge it for a couple of hours, and then try the volume down + power combination to get to the bootloader. I hope it works, let us know how you go.
Sent from my Evita
Click to expand...
Click to collapse
Yes well on my laptop its the up key that's what I was doing was spamming, you can hear the connected device sound on then off, but it just doesn't see it. I will let you all know once its working again and what I did or had to do to get it back so that it may possibly help others that run into the same issue. If not I suppose I'll try to get it Jtagged, too nice of a phone to use as a paperweight really
Yeah sorry, I knew it was one of the arrow keys, kinda took a stab in the dark at that one :sly:
Sent from my Evita
Hold down the power button until the phone turns off. You'll see the buttons flash. This simulates a battery pull. Then wait a few secs then hold vol down and press power button for 2 secs while still holding vol down. Wait for bootloader
Sent from my VENOMized HoxL
You should hold volume down while holding power. Holding power alone just initiates a reboot, not a power down, so if you're not holding volume down at the same time when the reboot kicks in it'll just reboot as normal.
Sent from my Evita
timmaaa said:
You should hold volume down while holding power. Holding power alone just initiates a reboot, not a power down, so if you're not holding volume down at the same time when the reboot kicks in it'll just reboot as normal.
Sent from my Evita
Click to expand...
Click to collapse
Nothing is working guys :/ full Battery drain and everything it just keeps looping no matter what I do it will not go in bootloader :crying: thanks for trying to help
If you are trying while the phone is plugged into power it will not work.
The method I use is to hold power until the screen shuts off then I let go of power and hold volume down until the bootloader comes up.
Sent from my One Xl using xda app-developers app
exad said:
If you are trying while the phone is plugged into power it will not work.
The method I use is to hold power until the screen shuts off then I let go of power and hold volume down until the bootloader comes up.
Sent from my One Xl using xda app-developer app
Click to expand...
Click to collapse
Yes I don't have power plugged in, I've never had a problem like this. . I also don't even have to turn off the screen everytime it loops it goes off for a good 20 seconds or more. But I did try what you all said too and it seems there is not even an effect at all it just loops
YAY!! I was messing around and held volume up and volume down with power, and it put the phone into some kind of off/sleep mode, then it recognized the device in windows device manager and said device cannot start, so I tried uninstalling the driver and then refreshed to let it reinstall them and during the reinstall i tried running the adb command and it let me back into bootloader! woo! that was lucky.. hopefully this can be helpful to others that get stuck like that. I'm worried now though i have bootloader sitting pretty what should I do first? I'm scared to loop again thanks all.
sensei_777 said:
Yes I don't have power plugged in, I've never had a problem like this. . I also don't even have to turn off the screen everytime it loops it goes off for a good 20 seconds or more. But I did try what you all said too and it seems there is not even an effect at all it just loops
YAY!! I was messing around and held volume up and volume down with power, and it put the phone into some kind of off/sleep mode, then it recognized the device in windows device manager and said device cannot start, so I tried uninstalling the driver and then refreshed to let it reinstall them and during the reinstall i tried running the adb command and it let me back into bootloader! woo! that was lucky.. hopefully this can be helpful to others that get stuck like that. I'm worried now though i have bootloader sitting pretty what should I do first? I'm scared to loop again thanks all.
Click to expand...
Click to collapse
Just flashed the boot.img good to go now thanks for the advice everyone
OK I'm stumped.
I was sick of the OTA updates bugging me so I set about flashing to 4.4.2 on my XT1034. All went along fine till I got to the part where I had to flash system with sparsechunk. It kept giving me a permissions error. I wasn't sure what to do so I decided to try rebooting, clearly that was not the answer. Now my phone shows the unlocked boot loader screen for a few seconds and goes to a black screen. I can tell the screen is on, it's just that the screen itself is showing all black. My computer recognizes that something in there and installs the drivers for the ADB interface and USB composite, but not the MTP device. All commands to adb or fastboot just says waiting for device.
Anyone have any idea?
Edit: Not sure if it makes a difference, but I was on stock 4.3, trying to go to 4.4.2 or in firmware terms...
from Blur_Version.14.14.16.falcon_umts.AWSRetail.en.US
to Blur_Version.172.44.4.falcon_umts.AWSRetail.en.US
If your phone even does not start in fastboot mode then i would say you are pretty much fu***d.
Fastboot Cable?
I just had a thought. I have a fastboot cable from my Droid Razr XT912. I wonder if that might force it into fastboot mode?
I'll have to wait till I get home to try it but I'll update it I make any progress.
Hold power button until phone turns off. Turn phone on while holding volume down.
tapman said:
I have a fastboot cable from my Droid Razr XT912.
Click to expand...
Click to collapse
You have a fastboot cable :fingers-crossed::laugh:
Thats really great!
No my friend, your USB cable will not help you to access fastboot mode.
The first way to access Fastboot is to press Volume Down + Power when the phone is switched off.
The second way to access Fastboot is to boot the phone into Android and then
Code:
adb reboot bootloader
But as you have no operating system on your phone there is only option one for you.
So your fastboot cable will not help you. Try several times to get in fastboot with option one.
lost101 said:
Hold power button until phone turns off. Turn phone on while holding volume down.
Click to expand...
Click to collapse
No luck. When I power it off it just power's itself back on a few seconds later whether I and holding the power button or not and regardless of if it's plugged in or not. I've tried the following combinations:
power off then hold volume down while it powers itself on
power off then power back on while holding volume down
hold power and volume down till it reboots
All have the same result, reboot, unlocked bootloader screen, blank, windows detects new hardware and tries to install drivers but fails on the MTP
So also if there is no cable connected it switches on itself?
Actually when it comes to the bootloader screen you missed already the fastboot entrance point.
Give it some more tries.
mokkami said:
So also if there is no cable connected it switches on itself?
Actually when it comes to the bootloader screen you missed already the fastboot entrance point.
Give it some more tries.
Click to expand...
Click to collapse
Correct. I'll keep trying :/
Edit: Sweet Jebus it worked! I'm back into fastboot
Thank you so very much!
Could be a coincidence but after taking off my case(otterbox defender) and trying again it worked. Maybe the membrane was causing me to press both volume buttons? Weird but I'll take it.
Glad to hear. Yeah i had also an Otterbox for my HHTC HD2 and i had also this problem.
Now you can go on to restore your Moto G
mokkami said:
Glad to hear. Yeah i had also an Otterbox for my HHTC HD2 and i had also this problem.
Now you can go on to restore your Moto G
Click to expand...
Click to collapse
Yup back up and running now, no idea why I was getting those permission errors. *shrug*
Thanks again
I bricked my htc one m8. Dont even know how, all i had was cyanogenmod 11 installed and it and my phone just boots into black screen after initial splash screen. I can get the charging indicator to show at low or full battery and i get vibration feedback when i hard reboot. I cant get into recovery or bootloader and my computer doesn't recognize it. What do!!
piisceiss said:
I bricked my htc one m8. Dont even know how, all i had was cyanogenmod 11 installed and it and my phone just boots into black screen after initial splash screen. I can get the charging indicator to show at low or full battery and i get vibration feedback when i hard reboot. I cant get into recovery or bootloader and my computer doesn't recognize it. What do!!
Click to expand...
Click to collapse
if your phone boots into a black screen its not hardbricked, hardbricked means it wont turn on at all and you have no indicators
piisceiss said:
I bricked my htc one m8. Dont even know how, all i had was cyanogenmod 11 installed and it and my phone just boots into black screen after initial splash screen. I can get the charging indicator to show at low or full battery and i get vibration feedback when i hard reboot. I cant get into recovery or bootloader and my computer doesn't recognize it. What do!!
Click to expand...
Click to collapse
Does ADB recognize the device?
piisceiss said:
I bricked my htc one m8. Dont even know how, all i had was cyanogenmod 11 installed and it and my phone just boots into black screen after initial splash screen. I can get the charging indicator to show at low or full battery and i get vibration feedback when i hard reboot. I cant get into recovery or bootloader and my computer doesn't recognize it. What do!!
Click to expand...
Click to collapse
Unplug your phone and hold volume up and power for 30
seconds. Do not have it plugged in while doing this.
Bierce22 said:
if your phone boots into a black screen its not hardbricked, hardbricked means it wont turn on at all and you have no indicators
Click to expand...
Click to collapse
Ok so thats good to know
DizDroid said:
Does ADB recognize the device?
Click to expand...
Click to collapse
No but i could be doing aomething wrong. Ill give it another go
piisceiss said:
No but i could be doing aomething wrong. Ill give it another go
Click to expand...
Click to collapse
You may need to uncheck usb debugging in developer options then reboot and go in and check usb debugging again then try adb tools using adb devices and see if it works then. Some m8's can be a real pain that way you just need to keep trying.
M9guy said:
You may need to uncheck usb debugging in developer options then reboot and go in and check usb debugging again then try adb tools using adb devices and see if it works then. Some m8's can be a real pain that way you just need to keep trying.
Click to expand...
Click to collapse
I cant boot into the os, it only goes to a black screen. It still vibrates though when i try doing any form of reset
piisceiss said:
I cant boot into the os, it only goes to a black screen. It still vibrates though when i try doing any form of reset
Click to expand...
Click to collapse
I would run the newest ruu that dottat has posted in the android development section for this phone, put it on your sd card using your computer, then put it back in your phone and boot to fastboot and let it pick it up and hit I believe it is yes and it will restore your phone. You are on 4.4.4 right ? If you are having problems getting to fastboot hold power and volume up until you see the lights change and or it vibrate then quickly switch to power and volume down and it should take you to fastboot, it may take you multiple tries to get it there. This sounds like the screen of death issues people have had on viperone which the fix for that so far has been to reverse the 4g handoff fix as most people that have the sod they had used the 4g handoff fix but if you cant get past the black screen then you cant do the fix for that. Have you tried leaving your phone sit for a while to see if it comes out of it ? Also most people only had that issue in weak signal areas so a good signal area could get your screen working again if you had done the 4g handoff fix. If you did some have said that the change can stick even through a ruu, but I cannot verify that either way.
Can I say I'm having an almost same problem.
I wiped my phone in prep of loading a new rom.
RUU the firmware for 4.4.4
Loaded twrp
and then it rebooted to the htc screen.
Now I can't get past that screen. I can hard reboot but it only comes back to that screen. and if I try to access it through the computer it can't load the driver so that I can sideload.
Help please
rcbarrieault said:
Can I say I'm having an almost same problem.
I wiped my phone in prep of loading a new rom.
RUU the firmware for 4.4.4
Loaded twrp
and then it rebooted to the htc screen.
Now I can't get past that screen. I can hard reboot but it only comes back to that screen. and if I try to access it through the computer it can't load the driver so that I can sideload.
Help please
Click to expand...
Click to collapse
it's tricky to get it back to hboot... but you can with practice. Hold power a both volume buttons until you think it finally has rebooted. Switch to only holding vol down to enter hboot. Timing and practice makes perfect.
It took about an hour of trying. But I did it. Plus I had to do a few other things to get things remounted.
rcbarrieault said:
It took about an hour of trying. But I did it. Plus I had to do a few other things to get things remounted.
Click to expand...
Click to collapse
I will have to try this. What other things did you do?
Once I was back in recovery I reformatted before rebooting and then from recovery I installed the rom.
dottat said:
it's tricky to get it back to hboot... but you can with practice. Hold power a both volume buttons until you think it finally has rebooted. Switch to only holding vol down to enter hboot. Timing and practice makes perfect.
Click to expand...
Click to collapse
I did this and we're all fixed, thank you for all the replies
dottat said:
it's tricky to get it back to hboot... but you can with practice. Hold power a both volume buttons until you think it finally has rebooted. Switch to only holding vol down to enter hboot. Timing and practice makes perfect.
Click to expand...
Click to collapse
I agree with Dottat, faced the same issue when trying to flash ARHD 22.1 on my Verizon M8. I think I sprayed some **** in my pants with that loud fart .
After trying several times I got the trick and could get into Hboot. The issue I think was I was holding Power + Volume up & down for more than required time and it Rebooted. We need to Switch Off the device by Holding Power + Volume UP & Down button for about 8-10 secs and then just remove the finger from Volume UP button. It takes you to Hboot mode..
Hello,
At one point this tablet was working just fine. It sat for a while and now it boot loops. Shows the amazon logo and auto restarts.
I can hold the proper volume up or down key and it says "Recovery Mode" on the bottom left but never enters into it.
Oddly enough I wasn't screwing around trying to do something I shouldn't have, but for the life of me I can't figure out what the deal is. Have anything I can try to possibly recover it? or is it straight to the bin.
Thank you in advance.
Take care,
Try fastboot boot recovery.img with the help of PC, if it boots format data and install rom.
Shiva Kumar A said:
Try fastboot boot recovery.img with the help of PC, if it boots format data and install rom.
Click to expand...
Click to collapse
Yeah good idea I'll report back .. I mean I can't break it anymore heh. I'm going to blame gamma rays coming down from from space and flipping a single bit in my 6 year old tablet............... causing it to boot loop.
So thinking out
Shiva Kumar A said:
Try fastboot boot recovery.img with the help of PC, if it boots format data and install rom.
Click to expand...
Click to collapse
So thinking out loud.
How do I get the tablet in a spot to accept a fastboot via USB?
It doesn't start up correctly to booted android. It doesn't enter TWRP... it seems as if I am stuck right?
likwidchz said:
So thinking out
So thinking out loud.
How do I get the tablet in a spot to accept a fastboot via USB?
It doesn't start up correctly to booted android. It doesn't enter TWRP... it seems as if I am stuck right?
Click to expand...
Click to collapse
What's happening when you try to boot into fastboot mode? After entering fastboot mode in cmd "fastboot boot twrp.img" "(drag and drop twrp file after boot )" it'll boot into twrp.
Shiva Kumar A said:
What's happening when you try to boot into fastboot mode? After entering fastboot mode in cmd "fastboot boot twrp.img" "(drag and drop twrp file after boot )" it'll boot into twrp.
Click to expand...
Click to collapse
You will have to explain how I would boot it into fastboot mode if
1 The tablet doesn't fully boot up past the amazon logo.
2 I cant even enter TWRP.
What am I missing?
Thank you and cheers!
When the device is fully shutdown press volume down + power.or maybe volume up check your device's combination key
Shiva Kumar A said:
When the device is fully shutdown press volume down + power.or maybe volume up check your device's combination key
Click to expand...
Click to collapse
Right then what? I'm missing something here.
likwidchz said:
Right then what? I'm missing something here.
Click to expand...
Click to collapse
I can't understand you what you trying to ask?
Shiva Kumar A said:
I can't understand you what you trying to ask?
Click to expand...
Click to collapse
Hello apologies,
I'll try and be as verbose as possible this time
This executes
[email protected]:/usr/src/giza# ./boot-fastboot.sh
[2023-02-08 12:26:26.386801] Waiting for preloader
[2023-02-08 12:26:50.335150] Found port = /dev/ttyACM0
[2023-02-08 12:26:50.365886] Handshake
[2023-02-08 12:26:50.386040] Preloader ready, sending FACTFACT
*Holding the left volume button + power button for some time.
[email protected]:/usr/src/giza# fastboot flash recovery bin/recovery.img
< waiting for any device >
Ive had this execute once, but when it does it looks like it wiped out TWRP as I cant get the small text to appear on the bottom left hand corner of the tablet while it does a boot holding power and the volume button.
So I'm not quite sure what I can do now.
Is there a method to flash TWRP with fastboot? or is that what the recovery is?
Could you provide a detailed list of items to try out and some high level instructions.
I've been thumbing through https://forum.xda-developers.com/t/unlock-root-twrp-unbrick-fire-hd-8-2016-giza.4303443/ this guide, but realize I'm not sure which step I need to start from, so I have bene trying a bunch of things and kind of stumped.
Thank you Shiva,
likwidchz said:
Right then what? I'm missing something here.
Click to expand...
Click to collapse
Bootloops are definitely a hassle sometimes. On your device your can either play the button game , watching the device closely and holding the the right button combo when the device goes black in hope that the device will boot into recovery or fastboot when it starts the bootloop again. The easiest thing for me to do sometimes is wait for the battery to drain completely dead then plug the device into the computer while holding the button combination to enter fastboot or recovery. The crappy part is waiting for the battery to drain. I did do a google and learned that Giza uses vol down button and pwr button to enter recovery. But with a dead battery it's likely one will only need to hold vol down button while plugging in the device. If it's in a bootloop it's probably not necessary to hold power button as well, just need to hold the vol down button at the time. I will say with a fair amount of confidence that the device is not a loss cause. Good luck, hope you get it working.
jonpjingleheimler said:
Bootloops are definitely a hassle sometimes. On your device your can either play the button game , watching the device closely and holding the the right button combo when the device goes black in hope that the device will boot into recovery or fastboot when it starts the bootloop again. The easiest thing for me to do sometimes is wait for the battery to drain completely dead then plug the device into the computer while holding the button combination to enter fastboot or recovery. The crappy part is waiting for the battery to drain. I did do a google and learned that Giza uses vol down button and pwr button to enter recovery. But with a dead battery it's likely one will only need to hold vol down button while plugging in the device. If it's in a bootloop it's probably not necessary to hold power button as well, just need to hold the vol down button at the time. I will say with a fair amount of confidence that the device is not a loss cause. Good luck, hope you get it working.
Click to expand...
Click to collapse
I had a weird assumption that I had to wait for the battery to drain. Its just weird this thing happened when it was working just fine.. usually I know when I screw something up pretty good.
I'm more curious on what command I need to be running and constantly retry to load up TWRP via fastboot.
Thanks!
likwidchz said:
I had a weird assumption that I had to wait for the battery to drain. Its just weird this thing happened when it was working just fine.. usually I know when I screw something up pretty good.
I'm more curious on what command I need to be running and constantly retry to load up TWRP via fastboot.
Thanks!
Click to expand...
Click to collapse
From what you have described issuing any command from a computer to the device wouldn't be possible as the device is bootlooping. I could not find any info on button combination to enter fastboot only recovery. from recovery there is a reboot to bootloader or fastboot option. that is your best bet. I have messed with at least a few different kindles in my time but there is always someone out there that has done more and may have another option they can add.
likwidchz said:
Hello apologies,
I'll try and be as verbose as possible this time
This executes
[email protected]:/usr/src/giza# ./boot-fastboot.sh
[2023-02-08 12:26:26.386801] Waiting for preloader
[2023-02-08 12:26:50.335150] Found port = /dev/ttyACM0
[2023-02-08 12:26:50.365886] Handshake
[2023-02-08 12:26:50.386040] Preloader ready, sending FACTFACT
*Holding the left volume button + power button for some time.
[email protected]:/usr/src/giza# fastboot flash recovery bin/recovery.img
< waiting for any device >
Ive had this execute once, but when it does it looks like it wiped out TWRP as I cant get the small text to appear on the bottom left hand corner of the tablet while it does a boot holding power and the volume button.
So I'm not quite sure what I can do now.
Is there a method to flash TWRP with fastboot? or is that what the recovery is?
Could you provide a detailed list of items to try out and some high level instructions.
I've been thumbing through https://forum.xda-developers.com/t/unlock-root-twrp-unbrick-fire-hd-8-2016-giza.4303443/ this guide, but realize I'm not sure which step I need to start from, so I have bene trying a bunch of things and kind of stumped.
Thank you Shiva,
Click to expand...
Click to collapse
Message me on telegram brother @HeyShiva
Shiva Kumar A said:
Message me on telegram brother @HeyShiva
Click to expand...
Click to collapse
Whats wrong with this forum?
likwidchz said:
Whats wrong with this forum?
Click to expand...
Click to collapse
Nothing, I can guide you there flawlessly. If you concerned about privacy no problem.
Shiva Kumar A said:
Nothing, I can guide you there flawlessly. If you concerned about privacy no problem.
Click to expand...
Click to collapse
I don't think you are the best person to guide on this one. You don't even seem to know what an Amazon tablet is, considering you suggested to fastboot boot when that cmd was patched back then in 2015.
@likwidchz If you're able to access fastboot thru boot-fastboot, erase preloader with fastboot erase boot0, reboot and run bootrom-step.sh again.
Rortiz2 said:
I don't think you are the best person to guide on this one. You don't even seem to know what an Amazon tablet is, considering you suggested to fastboot boot when that cmd was patched back then in 2015.
@likwidchz If you're able to access fastboot thru boot-fastboot, erase preloader with fastboot erase boot0, reboot and run bootrom-step.sh again.
Click to expand...
Click to collapse
Yes I don't know about this tablet, I thought it was just like any other tablets sorry
Rortiz2 said:
I don't think you are the best person to guide on this one. You don't even seem to know what an Amazon tablet is, considering you suggested to fastboot boot when that cmd was patched back then in 2015.
@likwidchz If you're able to access fastboot thru boot-fastboot, erase preloader with fastboot erase boot0, reboot and run bootrom-step.sh again.
Click to expand...
Click to collapse
Would you happen to be on IRC or some discord group?
I have done about ~7 of these tablets Suez/Giza but when something goes south, its not clear to me which step I need to start back from. Having a side conversation might help. In the end of the tablet is done, I am not going to be too broken up about it. But it's not a lost cause yet.
Thank you for the assistance! Much love.
--Take care.
likwidchz said:
Would you happen to be on IRC or some discord group?
I have done about ~7 of these tablets Suez/Giza but when something goes south, its not clear to me which step I need to start back from. Having a side conversation might help. In the end of the tablet is done, I am not going to be too broken up about it. But it's not a lost cause yet.
Thank you for the assistance! Much love.
--Take care.
Click to expand...
Click to collapse
I don't use IRC, but I do have Discord (R0rt1z2#3415).