Develop Bugs

[Q] Phone Will Not Boot Past Splash Screen

I tried to flash the latest (at that time) Synergy Rom on Sunday. I had been trying out Sense 3.0 Roms since being on Cyanogen for 3 months and low in behold after flashing and rebooting, the phone hung on the splash screen, wouldn't even get to the boot animation. I pulled the battery out to reboot and kept doing the same things. So then i just figured I go through bootloader to get to recovery. When I hit recovery, the phone hung on the splash screen and thus I was forced to report my phone lost because I use it for work and was able to get a new one the next day (had to pull out my old bb 8530). The phone charges, but it will not do anything when powering on, or hitting recovery but go to splash. Once again when i try to go into recovery, it won't get there.
Any Help Please.

dels28 said:
I tried to flash the latest (at that time) Synergy Rom on Sunday. I had been trying out Sense 3.0 Roms since being on Cyanogen for 3 months and low in behold after flashing and rebooting, the phone hung on the splash screen, wouldn't even get to the boot animation. I pulled the battery out to reboot and kept doing the same things. So then i just figured I go through bootloader to get to recovery. When I hit recovery, the phone hung on the splash screen and thus I was forced to report my phone lost because I use it for work and was able to get a new one the next day (had to pull out my old bb 8530). The phone charges, but it will not do anything when powering on, or hitting recovery but go to splash. Once again when i try to go into recovery, it won't get there.
Any Help Please.
Click to expand...
Click to collapse
You need to reflash your recovery. Is it just hanging at the splash screen, or is it rebooting at the splash screen?
Download this PC36IMG I attatched (it's Amon RA recovery v2.3). Place the file on the main directory of your sd card (you'll probably need to take the SD card and use a card reader to get the file on the card....or put the card in another phone with an sd slot if you have access to one...just get the PC36IMG.zip file on your card). Once it's on the card and card's back in the phone, boot to your bootloader. It should scan and find the PC36IMG then ask you to update...select vol up to say yes. Should finish in 10-15 seconds. Then when it asks you to reboot, say no. Now from the bootloader menu, choose recovery. Do you successfully boot to recovery now, hopefully?

Ok, I got that, I put cyanogens latest release candidate from 5/5 on the card, I have Ra's recovery up, i guess i jumped ahead and the install aborted, tips please.

dels28 said:
Ok, I got that, I put cyanogens latest release candidate from 5/5 on the card, I have Ra's recovery up, i guess i jumped ahead and the install aborted, tips please.
Click to expand...
Click to collapse
So what part aborted? When you were flashing the rom? Just to clarify, you did successfully get the recovery flashed, right? Now it's the rom you're having trouble flashing?
If so, I'd be sure that you don't have a corrupted download. Check the md5 checksum, or simply try redownloading it and trying again. Good luck.

It starts to install the ROM, then it all of a sudden aborts after getting 50-75 percent complete. I'm trying RC 7.3 now, wala, it worked, well i have an extra evo now i need to figure out what to do with it. BIG THANKS.

dels28 said:
It starts to install the ROM, then it all of a sudden aborts after getting 50-75 percent complete. I'm trying RC 7.3 now, wala, it worked, well i have an extra evo now i need to figure out what to do with it. BIG THANKS.
Click to expand...
Click to collapse
You're welcome, glad you got it squared away.
As far as having two Evo's...just be careful. If I'm not mistaken, when you report a phone lost or stolen to Sprint, they will make the ESN bad. I'd check into that, to make sure that one them doesn't have a bad ESN. I didn't even catch that part of your OP that you had already gotten a new one, lol.

So I guess that will make the phone useless if I give it to my father in-law.

turn it back in n say u found it...in other words the right thing

after doing amon ra3.0.7 nandriod
sorry if question is silly. but last night i flash from cwm to amon ra 3.0.7 everything went good, rebooted phone fine. i rebooted into recovery did a nandriod back evrything fine. i did a reboit to recovery wipe everything except sd card and flash a custom rom and rebooted fine. i went back into revovery did a nandriod backup went fine. i went to reboot my phone and its stuck at splash screen. I followed Hip Kat instruction to the letter. di i miss something
any help would be greatly

I've been running a Sense ROM the last few days and wit the 3 different Sense Kernels I've flashed, I got stuck on the ROM's Splash Screen, had to do a battery pull and reboot and it was fine.
That could be your problem right there.

HipKat said:
I've been running a Sense ROM the last few days and wit the 3 different Sense Kernels I've flashed, I got stuck on the ROM's Splash Screen, had to do a battery pull and reboot and it was fine.
That could be your problem right there.
Click to expand...
Click to collapse
it was me i jump the gun after i flashed custom rom. i di all kinds of mods then i tried to nandriod. md5 check sum mismatch, so i just wiped everthing except sd card, reflashed custom rom its all good now. By the way thanks for your input about cwm being junk you were right amon ra is awesome, no more cwm for

Random Restarts

Hello every one,
I am new to the forums and have been looking around for some time. I have a major issue that I need some assistance with if possible.
I am running, well was running, gingerbread 2.3.3 on my HTC Evo 4g phone until yesterday night. Here is some info about what happened. I rooted my phone with revolutionary and everything was going good til I tried to install a new ROM on the phone. The ROM I was downloading was CyanogenMod7, When it finished downloading, the phone booted itself into recovery to install the ROM. Well this is when the problem started, it just sat at the install screen and when it got down with the install it just continued to boot itself into a loop.
I turned the phone off and tried to boot it into recovery, which it did by the way. I did a complete restore of the stock ROM and rebooted the phone, when the phone turned back on is when the phone just continued to restart itself over and over again. So, I did a complete wipe: Recovery, Clear storage etc and nothing seemed to work but instead of it restarting itself, it just sits at the recovery screen and wont go any further. Just like it doesn't have any OS installed to boot from.
I would like some help and see what I can do to fix this problem.
When I go to recovery and boot from the fastboot-bootloader it says:
SD checking "No Image" Loading...
No Image,
loading.....
No image,
Loading....
No image or wrong image....
Click to expand...
Click to collapse
on top of that the sd card well not mount to the phone. I am so lost right now.

Some one pelase help or point me in the right direction.

Which recovery are you using for this? Maybe you can actually get it together by doing a complete wipe and cleaning cache/dalvik and then do the recovery.

I am using the clockwork recovery v3.0.0.5.
Every time I try to wipe the Dalvik Cache it tells me
E:unknown volume for path [/sd-ext] Dalvik Cache wiped
Click to expand...
Click to collapse
I still get the same thing. The one issue that I have encountered was that the sd card is not mounted to the phone. I have android sdk tools installed but the program can't seem to find my phone when I run the command prompt. The other things is now my phone just randomly shuts down and the the battery light just blinks, like its in stand by mode or something. The only thing I can do is take the battery out and what, then replace the battery and see if it works.

Try to charge the battery without using the phone that way you can work with it. My suggestion is to use Amon-RA recovery. Works a whole lot better that Clockwork. And try from there if you can install the ROM right.
It might be problems with your SD card. If is not reading it then that would be the message.

I tried that and nothing, I gave up on trying to save the phone that I went and got a replacement for it.

[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

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!

Stuck in boot loop even after factory reset. Able to get into bootloader and recovery

Hoping for some help or alternatives to fix my fiancee's Pixel XL. Last night the phone just kept flashing the 'G' logo on for 10 seconds, off for 10 seconds. She said the phone was close to dying before it happened, and I imagine it probably ended up draining the battery afterwards with the constant bootloop. Plugged it in all night but the charging screen didn't come up and would just stay in the bootloop. I could get it into the boot loader (power button and volume down), but it wouldn't go into recovery mode and instead would go right back to the boot loop.
So I tried a battery pack to charge it and it still didn't show charging, but I was able to get it into recovery mode eventually, but still boot loop afterwards. At one point, after leaving it on boot loader menu while attempting to charge, it eventually just tried to start itself and made its way to the second Google splash screen after the main G logo. Looked like it froze there though and I couldn't get it to that point again.
On my way to work this morning I tried plugging it into my car's USB port after powering off from the boot loader, and this time I kept flashing that it was charging (looked like it was 3/4 charged but not sure how accurate that is). So I got into recovery again and tried 3 factory resets consecutively. Still bootloop after attempting a startup afterwards. There was a similar issue a couple weeks ago where it looked like it was stuck in a bootloop, but it turned out the phone actually was dead that time and the charger wasn't working. Once we switched chargers it booted right up.
Any other suggestions or possibilities? I don't have much troubleshooting experience otherwise. Phone is fully stock, Google Fi. Any other info I can provide please let me know!

well, i'm not sure if it makes a difference, but now for some reason i can't get into recovery mode again. just goes into the boot loop. It also goes into the boot loop as soon as I plug the phone in to charge.

cgibsong002 said:
well, i'm not sure if it makes a difference, but now for some reason i can't get into recovery mode again. just goes into the boot loop. It also goes into the boot loop as soon as I plug the phone in to charge.
Click to expand...
Click to collapse
I assume you can't get into the bootloader using power and volume down buttons?

I have always been about to get into the boot loader. Actually i can get into recovery again as well. Seems if i let it sit for a while it'll go to recovery again. Maybe heat related.

My OG Pixel did the same thing to me one morning. I tried everything to revive my pixel but nothing worked. I did some digging and it turns out there is an issue with the storage on the phone. It's just a old fancy paper weight.

cgibsong002 said:
I have always been about to get into the boot loader. Actually i can get into recovery again as well. Seems if i let it sit for a while it'll go to recovery again. Maybe heat related.
Click to expand...
Click to collapse
If you can get into recovery, have you tried to sideload a full ota.zip (not an update)?

mozhno said:
If you can get into recovery, have you tried to sideload a full ota.zip (not an update)?
Click to expand...
Click to collapse
I haven't. I see that Google has all the ota's on their site. Is there a specific one that i might want to try? The same one? Go back a few? Will i even be able to sideload if my phone is fully stock?
Edit: sideload adb successfully but no change. I loaded the 6-5 ota which was what i already had.

cgibsong002 said:
I haven't. I see that Google has all the ota's on their site. Is there a specific one that i might want to try? The same one? Go back a few? Will i even be able to sideload if my phone is fully stock?
Edit: sideload adb successfully but no change. I loaded the 6-5 ota which was what i already had.
Click to expand...
Click to collapse
Sounds as if it's time to just try stuff and see what sticks. Regarding using an ota, it works if you are stock, and I sideload it even if I have installed majisk or installed another kernel. It typically works for me with fewer chances of blowing things up than flashing a stock image. Regarding what to try next, you may have already gone into recovery to check the install function to see if your storage still appears and try to flash anything that worked in the past; if you have a backup in twrp you could try to restore it; you could wipe cache and dahlvik; or even sideload an earlier ota version that worked. Since the 6-5 ota did not work nothing really jumps out to me as obvious. One final caveat, I once had to reboot a sideloaded ota a second time before my pixel booted properly. If I think of something else I'll post again.

I took it to ubreakifix and they told me that this is indeed a known issue with pixel xl's that they all suffered from a faulty motherboard and that is indeed the cause here. Said he thought there was actually a class action about it so I'll have to look into it. Really pisses me off that Google repeatedly told me it's not a known issue when their authorized repair center says it is.
Anyway i have a warranty with Upsie that I'm hoping to get this replaced with. We'll see.

cgibsong002 said:
I took it to ubreakifix and they told me that this is indeed a known issue with pixel xl's that they all suffered from a faulty motherboard and that is indeed the cause here. Said he thought there was actually a class action about it so I'll have to look into it. Really pisses me off that Google repeatedly told me it's not a known issue when their authorized repair center says it is.
Anyway i have a warranty with Upsie that I'm hoping to get this replaced with. We'll see.
Click to expand...
Click to collapse
Good luck

I'm assuming you tried booting into twrp recovery, going to reboot, and picked slot A ( or B if already in A) to reboot to and then rebooted system? A lot of the times simply switching slots from recovery and then rebooting is the fix. At least for me.

手机早期经历的情况得说明一下。root没有？Twrp是谁的？

Also, for anyone else having this issue, try rebooting into the bootloader. Connect to PC, and try fastboot --set-active=a
If this doesn't work, try booting back into your recovery image using fastboot boot *whatever you named your TWRP recovery image* and then flashing your twrp.zip again in recovery, and when rebooting if you're in slot B choose slot A in recovery to boot into.
Also keep in mind in Windows 10, it uses Powershell, so commands have to be typed in .\fastboot not just fastboot or it won't take it.