Develop Bugs

[Q] Can't access bootloader at all. Please help!

Hi guys
I've searched the forum for something like this but I'm coming up empty handed. But then again, I'm freaking out a bit.
I just tried flashing ARHD 9.7.0 and I've hit a big snag... For a bit of background, I was previously running ARHD 9.4.2 with the Endeavoru-Faux123-010b3 kernal. The battery was at 35% when I started the process...
I downloaded the zip, put it onto my SD card and rebooted into CWM. No worries there.
Did a wipe/factory reset and wiped the cache aswell. No worries there.
I did NOT flash the boot.img in the zip as I believed it would work okay with the current kernel (possibly the issue)
Went to install zip from SD card and chose the zip to install. AROMA starts up and I go through the familiar install process. No problem there.
I checked the reboot now option in AROMA and let it reboot. This is where the fun begins...
I get the beepy boopy start up sound and let it sit there because, as we all know, first boot can take a while. 10 minutes later, it's stuck at the HTC One splash screen. So I thought I'd reboot into CWM and start over like I've done with other ROM/kernal incompatibilities.
So I hold down the power button, let the three lights blink and the screen go blank and hold down the volume down button. And it goes back to attempting to boot up. I've tried different combinations of holding the buttons down and letting them go and hell, I've even sat there hammering the volume down button while it starts up! Still, I can't get into the bootloader.
Obviously, no bootloader, no ADB connection so I can't go through CMD and can't re-flash the kernel.
I'm currently sitting here looking at it. The USB cable is plugged in and the orange light is lit up so I hope it's charging. I'm at a loss here guys. Please, if anyone can give me some help, I will be most appreciative.

I'm really sorry to have wasted your time. It worked eventually after about 50 tries! :laugh:
Looks like it ws a kernel incompatibility.
But out of curiosity and for anybody else who gets this problem and really can't boot into the bootloader, what would be the steps involved in recovering a device in that state? I'd rather look like a knob in public as long as something constructive comes from it. :silly:

It's a bit tricky to get into hboot after a forced reboot, I think we've all been there

Just avoid the problem altogether by flashing the boot.img inside the zip first to make sure that it boots. Once up and running, flash your custom kernel and modules.

Try this http://forum.xda-developers.com/showthread.php?t=1734365
And don't let go when reboots keep hold of buttons and it should go to bootloader
Sent from my HTC One X using xda premium

Need some help - possible defective hardware?

First off, S-off phone
So, I've been running the GPE rom posted by Joel for a while now with no issues... Today a friend wanted to see the phone, so I pulled it out of my pocket; hit power; nadda...
So I held power down for a while; got teh HTC screen; then nadda.
So we then attempted to get into recovery, power + vol down then selected recovery... Nadda, just a black screen.
I then redownloaded TWRP and fastboot flash recovery recoveryname.img, it tries to push it then it'll throw an error saying: "remote: image update error"
I looked around and found a thread with full directions with an RUU.. So I tried doing that, hwoever after clearing the cache via fastboot, when I try to do fastboot oem rebootRUU nothing happens.... sometimes teh screen goes blank, sometimes not.
Anything else I can try? I'm really wondering if it isn't defective hardware... .only had it 2 weeks too...

You are sure the phone is fully charged right ?
Sent from my Nexus 7 using Tapatalk 4

dottat said:
You are sure the phone is fully charged right ?
Click to expand...
Click to collapse
i was going to say the same thing. not sure how but i sometimes pull the phone out of my pocket with the screen on... so who knows which programs could have been tapped and running if it's bumping around in your pocket.

This is one of the reasons Verizon requires locked bootloaders now on all their phones. If the phone isn't even turning on, your first step should never be to try flashing a custom recovery or RUU (?!). If the phone has no charge and dies in the process, you could potentially brick it for good.
Sorry if that came across harsh, but... honestly, try charging your phone overnight first.

wireroid said:
This is one of the reasons Verizon requires locked bootloaders now on all their phones. If the phone isn't even turning on, your first step should never be to try flashing a custom recovery or RUU (?!). If the phone has no charge and dies in the process, you could potentially brick it for good.
Sorry if that came across harsh, but... honestly, try charging your phone overnight first.
Click to expand...
Click to collapse
Guess I should have put more details in the first post... when I got it into TWRP the first time it showed an 88% charge. I attempted to restore a backup and inside the recovery it would say it failed reading the memory and then it couldn't browse anything.
If I attempted to simply factory reset inside the recovery it would just lock up. If I tried to flash a rom via zip, it would lock up...
After a few times of rebooting it into the recovery I couldn't even click anything inside it without locking up.
it was at that point I tried to flash a different recovery and started getting the errors...
Anyways, more I researched it simply was a bad phone with defective hardware.
all good...

Samsung galaxy s2 sgh-t989 boot loop!

My daughter has this phone and she gave it to me to fix it was doing the same thing as stated in op kept rebooting on its own and would vibrae over an over , playing with the power button it would try to reboot sometimes it would get to the home screen but would rebot again i took the back piece off and cleaned around the power button and i would try to go into recovery but it kept rebooting, i kept trying and messing around with it and i got it to go into recovery and just enough time to clear cache brfote it robboted angian by itself still same thing, kept at it and got it to go into recovery again but i accidentally push update adb and it started to do what it does when you pushed that but i kept pressing power from a panic then i finally rebooted successful now im currently got it working its plugged into my computer it installed successfully but i don't see the storage on my computer, it does not have a sd card in it tho i have one to put in it and it does not have a sim card it it either tho i have the one my daughter gave me that she had to to her phone, i quickly turned on usb debuugging incase i need to odin firmware or something im not sure what do do from here so im asking any one that might know what i should do? If it was the power button i clean it as best as i can and aired it out too, im thinking this might tho do it again since im not sure what fixed it to this point except from what i did to it from what i wrote here. Please if anyone has any ideas out there so i can keep this thing fixed let me know in your replys TY!

mrdreamers said:
My daughter has this phone and she gave it to me to fix it was doing the same thing as stated in op kept rebooting on its own and would vibrae over an over , playing with the power button it would try to reboot sometimes it would get to the home screen but would rebot again i took the back piece off and cleaned around the power button and i would try to go into recovery but it kept rebooting, i kept trying and messing around with it and i got it to go into recovery and just enough time to clear cache brfote it robboted angian by itself still same thing, kept at it and got it to go into recovery again but i accidentally push update adb and it started to do what it does when you pushed that but i kept pressing power from a panic then i finally rebooted successful now im currently got it working its plugged into my computer it installed successfully but i don't see the storage on my computer, it does not have a sd card in it tho i have one to put in it and it does not have a sim card it it either tho i have the one my daughter gave me that she had to to her phone, i quickly turned on usb debuugging incase i need to odin firmware or something im not sure what do do from here so im asking any one that might know what i should do? If it was the power button i clean it as best as i can and aired it out too, im thinking this might tho do it again since im not sure what fixed it to this point except from what i did to it from what i wrote here. Please if anyone has any ideas out there so i can keep this thing fixed let me know in your replys TY!
Click to expand...
Click to collapse
First off, that's one hell of a long sentence!
Had you (or your daughter) recently installed a ROM and forgot to factory reset (clear all caches) the phone after doing so? Many at times, this is what causes boot loops. And you cleared cache, which I think has resolved the problem. However, MAKE A BACKUP on your phone (and onto your computer, just in case the phone hard-bricks) using your Recovery right away! Once you make the backup, there's no need to worry about whether you soft-brick your phone again; you can simply restore that backup. It's also highly possible that it was your power button, but since you said you did clean it up thoroughly, it might just be the cache preventing you from rebooting normally.
Either way, it's good to hear you got your phone working now. I would highly recommend that you make a backup before doing anything else with the phone - just to be on the safe side. Good luck!

Faulty power button. Fixed myself.

I take no responsibility for your damaged devices, or any stuff you did in wrong way.
So how it went wrong:
Some days ago i flashed some rom. it was working okay. Than i flashed some more, and random reboots started to occur. Than i tried to boot to recovery from rom, and it just started to bootloop, not booting to rom neither to recovery.
managed to get to download mode after several attempts, odined a recovery (twrp as i always use it).
rom booted after i flashed recovey via odin. than i went back to recovery, checked md5 and its ok. So than did another clean flash, it was running ok. But than i pick my phone out of pocket and it's dead again. Odined once more.
It was booting like this - 3-5 seconds/vibration/blackscreen. and also not displaying battery on charging, even no led, even not letting to get to download mode. After battery reinsert it starts to boot, without pressing a thing.
Try not to panic first, try to boot properly and test how power bottom behave.
Fix:
Disassemble, put 2 little pieces of rubber between button and board, and should work fine so no matter to go for repair. It consumed me 10 minutes. Assembles without any trouble. And saved 5-10 bucks.
Can attach some photos if you ask to.

#000000 said:
I take no responsibility for your damaged devices, or any stuff you did in wrong way.
So how it went wrong:
Some days ago i flashed some rom. it was working okay. Than i flashed some more, and random reboots started to occur. Than i tried to boot to recovery from rom, and it just started to bootloop, not booting to rom neither to recovery.
managed to get to download mode after several attempts, odined a recovery (twrp as i always use it).
rom booted after i flashed recovey via odin. than i went back to recovery, checked md5 and its ok. So than did another clean flash, it was running ok. But than i pick my phone out of pocket and it's dead again. Odined once more.
It was booting like this - 3-5 seconds/vibration/blackscreen. and also not displaying battery on charging, even no led, even not letting to get to download mode. After battery reinsert it starts to boot, without pressing a thing.
Try not to panic first, try to boot properly and test how power bottom behave.
Fix:
Disassemble, put 2 little pieces of rubber between button and board, and should work fine so no matter to go for repair. It consumed me 10 minutes. Assembles without any trouble. And saved 5-10 bucks.
Can attach some photos if you ask to.
Click to expand...
Click to collapse
Can you please attach some photos, I'm having the same issue with my power button

When I had this problem a month ago I took out my handy dandy heat gun after disassembling the back and cleaning with isopropal alcohol. Fixed mine right up and I haven't had any issues since *knocks on wood*. If I have anymore problems though I will try this, thanks.

landroid2000 said:
Can you please attach some photos, I'm having the same issue with my power button
Click to expand...
Click to collapse
Will upload in 1-2 days. Having issues with second device.

#000000 said:
Will upload in 1-2 days. Having issues with second device.
Click to expand...
Click to collapse
Okay thanks

This is a nasty issue with pretty much any Samsung device, these are pretty ingenious work arounds considering the actual solder job can be a nuisance. I obviously recommend replacing the button to anyone if possible but still interesting to see what works!
P.S. I work at a uBreakiFix, my manager hates this solder job :laugh:

How do I get out of Nexus 7 bootloop?

My Nexus 7 2013 tab is stuck on boot animation and not switching on thereafter. I installed a custom rom after flasing TWRP RECOVERY 3.0.2 via P.C and thereafter using the TWRP.
The installation process is successful each time but wont go further than the boot screen. I waited for almost an hour . Evem the Gapps zip is not installing and giving error on log saying that file not mapped. Any way out of this mess? Does it have anything to do with my process? ...I advance wipe the system , data and cache before flashing and the file.

Don't know if you ever figured this out, but last night, mine froze while the kids were playing a game. I couldn't do anything at all. I had to hold the power button down for a while and it finally shut down. I charged it overnight, and all I could get it to do was display the Google screen. I searched and searched for a solution, and the only crazy thing that actually worked was to give it a good whack! I don't know why, but as soon as I smacked it (not on the glass!!), it booted right up as normal. Very odd.

joskur98 said:
My Nexus 7 2013 tab is stuck on boot animation and not switching on thereafter. I installed a custom rom after flasing TWRP RECOVERY 3.0.2 via P.C and thereafter using the TWRP.
The installation process is successful each time but wont go further than the boot screen. I waited for almost an hour . Evem the Gapps zip is not installing and giving error on log saying that file not mapped. Any way out of this mess? Does it have anything to do with my process? ...I advance wipe the system , data and cache before flashing and the file.
Click to expand...
Click to collapse
Which rom? Do you use the right gapps? Flash the rom without gapps and look if it's booting

Don't know if you ever figured this out, but last night, mine froze while the kids were playing a game. I couldn't do anything at all. I had to hold the power button down for a while and it finally shut down. I charged it overnight, and all I could get it to do was display the Google screen. I searched and searched for a solution, and the only crazy thing that actually worked was to give it a good whack! I don't know why, but as soon as I smacked it (not on the glass!!), it booted right up as normal. Very odd.
Click to expand...
Click to collapse
Holy ****, this worked! Had the same problem last night for the first time (I used it until the battery drained and this morning I got the loop). Smacked it on the back and now it's fully on!
Shame I got desperate and did a factory reset first