Hey Guys
UPDATE Wow I put mu dhd on usb en en clockworkmod popped up. De red/orange led above blinks. I really don't want to brick it some more times.
Update2 phone works again Thanks XDA for the nice topics
Murphy's law become truth or something. I just wrote an entire topic and my pc crashed.
I really want to know if my device is Bricked. Just for sure.
What happened?
My dhd did some unasual things like freezes, laggy can't install apps anymore etc.
I was running Gingerbread sense 2.3.3, before I upgrade to 2.3 I backupedd my 2.2 with nandroid.
So I flashed a new rom, problems aren't solved
So I think I restore my DHD with nandroid restore to froyo 2.2 That takes a while. When I came back my dhd was completely black. So I waited another 30 minutes. And pull off the battery
And from there. My dhd doesn't do anything.
1 No boot
2 No clockworkmod
3 ??
My DHD is rooted ENG-S-OFF
What to do Now?
WOW I
Hi Glaxo
Glaxo said:
Hey Guys
Murphy's law become truth or something. I just wrote an entire topic and my pc crashed.
I really want to know if my device is Bricked. Just for sure.
What happened?
My dhd did some unasual things like freezes, laggy can't install apps anymore etc.
I was running Gingerbread sense 2.3.3, before I upgrade to 2.3 I backupedd my 2.2 with nandroid.
So I flashed a new rom, problems aren't solved
So I think I restore my DHD with nandroid restore to froyo 2.2 That takes a while. When I came back my dhd was completely black. So I waited another 30 minutes. And pull off the battery
And from there. My dhd doesn't do anything.
1 No boot
2 No clockworkmod
3 ??
My DHD is rooted ENG-S-OFF
What to do Now?
Click to expand...
Click to collapse
May be your battery flat [no charge], try recharging the it.
Take Care
TheQuest
I really had a hart attack. I flashed cyangen mod7.0 as a test. And he is booting.
It works for now. And now i had to sleep some more hours.
Thanks anyway
I am really fast paranoid, I think I have to fix it myself before i asking it here.
Hi Glaxo
De red/orange led above blinks. I really don't want to brick it some more times.
Click to expand...
Click to collapse
That normal, it is the power [charge] light.
Take Care
TheQuest
Related
I've owned my DInc for around 8 months now and a week after I got the phone I had rooted it... The only thing I truly did was install a few custom ROM's on it to try out what I liked, when Froyo was in it's prime I used CM6 nearly every day, and now Gingerbread is around I've been running steady on OMGB6/7 for the past few months...
My problem is that last week my phone randomly rebooted and decided to get stuck on the white "HTC" boot logo... It stayed there for around 10 minutes before I finally decided to pull the battery, restart it, and the same thing occured.
Of course I have CWR installed with Nandroid backups, but when I used the backup for the current ROM I was on, it happened again getting stuck at the white screen. So I fired up CWR again and restored to a previous version of OMGB6 and that ran steady until today (in the middle of calculus of course) it rebooted after sending a text and got stuck at the white screen once more...
Now I CWR restored to my Stock HTC Sense ROM and I'm running that as we speak (and god, is it god-awful).
WTF is wrong with my Incredible? I'm guessing something got corrupted maybe in the /boot partition or something of the likes? Could someone please help me? I've never had this problem before... and never did any "customization" other than wiping my cache/data/dalvik/battery stats and installing different ROMs.
Thank you!
al2x said:
I've owned my DInc for around 8 months now and a week after I got the phone I had rooted it... The only thing I truly did was install a few custom ROM's on it to try out what I liked, when Froyo was in it's prime I used CM6 nearly every day, and now Gingerbread is around I've been running steady on OMGB6/7 for the past few months...
My problem is that last week my phone randomly rebooted and decided to get stuck on the white "HTC" boot logo... It stayed there for around 10 minutes before I finally decided to pull the battery, restart it, and the same thing occured.
Of course I have CWR installed with Nandroid backups, but when I used the backup for the current ROM I was on, it happened again getting stuck at the white screen. So I fired up CWR again and restored to a previous version of OMGB6 and that ran steady until today (in the middle of calculus of course) it rebooted after sending a text and got stuck at the white screen once more...
Now I CWR restored to my Stock HTC Sense ROM and I'm running that as we speak (and god, is it god-awful).
WTF is wrong with my Incredible? I'm guessing something got corrupted maybe in the /boot partition or something of the likes? Could someone please help me? I've never had this problem before... and never did any "customization" other than wiping my cache/data/dalvik/battery stats and installing different ROMs.
Thank you!
Click to expand...
Click to collapse
This used to happen with me on OMGB, its one of the reasons I switched to CM7. When I rebooted it used to get stuck on the splash screen. Mine, however, would work after a battery pull. I'm not sure, I'd try a fresh install, if that doesnt help, try out CM7, its a pretty stable.
Oh ok... so you're saying its probably just a ROM issue with OMGB? I'd switch to CM7 but the only thing I want is stock Gingerbread, I really hate the little customizations they put into CM7. Do they still have that CM7 Source project going on where it was pretty much stock gingerbread? Thanks again!
al2x said:
Oh ok... so you're saying its probably just a ROM issue with OMGB? I'd switch to CM7 but the only thing I want is stock Gingerbread, I really hate the little customizations they put into CM7. Do they still have that CM7 Source project going on where it was pretty much stock gingerbread? Thanks again!
Click to expand...
Click to collapse
I'm not saying thats 100% the case. I'm just saying that used to happen to me when I ran OMGB. I couldn't find a fix, so I just switched ROMs. I don't think CM7 has a just stock gingerbread look. But how can you not like all the features they packed into it?
AOSP + SD
Perhaps try flashing a Sense ROM and see if the issue persists.
Why?
AOSP ROMs interact quite a bit w/ the SD card. So, if there are issues w/ the SD card, the Sense ROM may not present as many funky issues.
After that test, I'd try another SD card and see if the issue persists.
If a different SD yields no wonky stuff, the answer was faulty SD card.
continual spontaneous reboots
I have the same issue. I was using CM6.1 I think and it's been fine for awhile and then it just started spontaneously rebooting. I can no longer get into Clockwork, all I can do is hold volume down and power to start it and from there, nothing will start the phone. I get the HTC spash and after about 3 seconds, it reboots and gets stuck in that cycle. Nothing has really changed and it rebooted on it's own to start the problem.
So, it's not like I installed something and rebooted. I'm interested in hearing if others are having the issues and what exactly their thoughts are.
OK here it goes... I decided to root my phone for so many reasons.. now i had it working for a few roms, (developers I think you might get be puzzled on this), well I rooted the unrevoked 3 for the incredible file.. it went well on the rooting part and my super user app worked fine... so i go in my rom manager premium app,,, i tried to download the latest version of the gingerbread rom... i forgot what was it called but its the only the latest gingerbread rom... now I loaded it... it was going good until the rebooted part when my incredible was rebooting and started to have the gingerbread being eating and loading part.. so I thought it was good but i noticed it was already over an hour and it still was showing that same loading part.... Now I am stuck and Im thinking I f*cked up my phone... lmao.. just material things thats all to me.. but i love my incredible... I was hoping if any developers can help me out on this situation because I just don want to go buy a new phone... I think unrevoked doesnt know how to make solid apk files to root phones.. Please if anyone can find a solution to this please let me know.. I am thinking of letting my battery go because is still running... but damn... I thinking... before my battery would die real fast and now i am trying to make it go dead it doesnt want to... apps should be like this... last long conserve battery more....my battery was at 40 percent.. when i started to root it into the gingerbread from rom manager... its been two hours and a half and still running the same animation... please help...
Thank you
xXblastingXx said:
OK here it goes... I decided to root my phone for so many reasons.. now i had it working for a few roms, (developers I think you might get be puzzled on this), well I rooted the unrevoked 3 for the incredible file.. it went well on the rooting part and my super user app worked fine... so i go in my rom manager premium app,,, i tried to download the latest version of the gingerbread rom... i forgot what was it called but its the only the latest gingerbread rom... now I loaded it... it was going good until the rebooted part when my incredible was rebooting and started to have the gingerbread being eating and loading part.. so I thought it was good but i noticed it was already over an hour and it still was showing that same loading part.... Now I am stuck and Im thinking I f*cked up my phone... lmao.. just material things thats all to me.. but i love my incredible... I was hoping if any developers can help me out on this situation because I just don want to go buy a new phone... I think unrevoked doesnt know how to make solid apk files to root phones.. Please if anyone can find a solution to this please let me know.. I am thinking of letting my battery go because is still running... but damn... I thinking... before my battery would die real fast and now i am trying to make it go dead it doesnt want to... apps should be like this... last long conserve battery more....my battery was at 40 percent.. when i started to root it into the gingerbread from rom manager... its been two hours and a half and still running the same animation... please help...
Thank you
Click to expand...
Click to collapse
Your phone is in a bootloop, pull the battery go into recorvery pwr+vol down. Restore a backup of an old ROM, or you can try to just pull the battery and try turning it on normally, but you might get caught in bootloop. If you're in that boot animation it will take a while for battery to die.
Sent from my Incredible using XDA App
I tried that but the boot loop is still in effect... should i just wait till the battery is dead to try to recover my old rom?
Just go into recovery and restore you're old ROM.
Sent from my Incredible using XDA App
Just restore to an older backup, or put a new ROM on your SD Card (using a reader obviously) and flash that. Make sure you wipe data/cache/dalvik (in advanced menu)
Just make sure that if you have been letting the battery die to let it charge via the wall outlet first. Don't ever try to flash anything on a low battery. Battery goes while you flash important stuff... you could be in deeper trouble.
Hi guys,
I need your expertise and ultimately your help!
So i was running Lee droid for months, it was all good, did loads of flashing of roms without never any (massive) issues.
Last week, i decided i wanted to try gingerbread, so I flashed gingervilain and the kernel that went this it. I din't really like it, i missed sense too much so i decided to go back to Lee Droid.
I did a clean install after wiping everything as i've done dozens of times in the past. But ever since a problem has arisen.
Whenever I'm on call, when i move the phone away from my face, the screen doesn't turn on and I can't turn it on at all, even when i press on the power button. Which means i can't hang up. So if i call someone and end up on voicemail, I need to remove the battery to finish the call, and whenever I am on the phone with someone I have to ask the person to hang up as I have no control over the phone.
The phone is to be totally irresponsive.
I tried to re-install gingervillain and had the same problem. So I reverted again back to Lee's rom, from a clean install and the problem persists!!
Last night I tried to format the card and I installed snq's new kernel, but it still doesn't work.
I have no clue what's going on. Could it be a voltage issue???
I'm s-on by the way.
I'm seriously confused at what the fark could be going on!?
Anyone has any idea?
On Lee's rom forum, a poster told me to flash a RUU or WWE rom. But I don't really wanna do that for two reasons :
1. I'm not sure it will work since installing Lee's rom on a clean install didn't solve anything
2. I don't really wanna go through the hassle of rooting my phone again
Thanks!
Using an RUU is your best bet since no one knows wtf is going on. I would say to do that as well and I'm sure maybe a few others would. Yes, you would have to root again (not like it takes forever and not like you have to do anything other than plug your phone into your PC and run the unrevoked utility, seriously). That would be your best chance for fixing it. BTW, using an RUU would wipe everything out and start fresh so it probably would fix the issue.
If it doesn't... well, that's for another time.
u can try go into settings turn off senser
exit settings
then go back in settings again set the senser on again
I see more and more people having the deep sleep bug, rooted or not.
Wish I knew how to fix the damn thing! The only sure thing is that if the phone is at stock condition (rooted or not does not matter), it doesn't have the problem.
When I install some apps, it would start doing this!
Alright, I guess I don't have much choice then! I'll flash a ruu.
Thanks a lot fo your help guys
I had cyanogenmod 7 installed on my EVO and one day my phone just turned itself off. This time it will only boot up to the white HTC EVO screen then power itself back off and continue to cycle. I loaded into bootloader and tried to go into recovery. As soon as I select recovery it goes right back to the white screen and continues to loop. I tried to clear storage and recieved the same results. I searched a tone online and tried to find a resolution. As far as I can get is install the boot interface driver and HBOOT USB the phone. All root programs get stuck at the "waiting for device". Any help would be much appreciated.
Drake13 said:
I had cyanogenmod 7 installed on my EVO and one day my phone just turned itself off. This time it will only boot up to the white HTC EVO screen then power itself back off and continue to cycle. I loaded into bootloader and tried to go into recovery. As soon as I select recovery it goes right back to the white screen and continues to loop. I tried to clear storage and recieved the same results. I searched a tone online and tried to find a resolution. As far as I can get is install the boot interface driver and HBOOT USB the phone. All root programs get stuck at the "waiting for device". Any help would be much appreciated.
Click to expand...
Click to collapse
sorry but you're pretty much S O L on this, has something to do with a bad boot.img and you can't get it to take another one might as well file a lost phone claim and pay the $100 and get a new one thats what i had to do and they just happened to have sent me the 3d instead so i guess i got a bit lucky.
i still have my evo 4g and still working on it but its been about a month and i haven't had any luck with it.
Sounds like you have no recovery or not completely rooted. You could try to put a recovery CWM or Amon-Ra file renamed PC36IMG.zip onto your sd card from your computer, put card back into phone then go in to hboot see if it will flash you a recovery then try to go into it
If that doesn't work search for a stock ruu file for the Evo, rename PC36IMG.zip, place on your card, put card back in phone, flash through hboot. This will return your phone to stock unrooted, then you try the process again
Sent from my PC36100 using XDA Premium App
That's what happened to my phone also..It just happened out of nowhere..
I tried everything and in the end I had to file an insurance claim.
And once again, a phone running CM7 goes into this mysterious unfixable bootloop.
What is up with that?
What is up with that, I'm about to remove this rom its not really all that. Its already messed up my keyboard, sometimes I have to take the battery out just to restart it.
I Loved CM7 when I had it, but then i started seeing all these bootloop issues start up in the early part of Summer, and I refuse to put it back on. Sorry to those that dev and support it, but seriously, out of all the cases on here, and there have been a bunch, only one was on a phone that didn't have CM7 on it.
HipKat said:
I Loved CM7 when I had it, but then i started seeing all these bootloop issues start up in the early part of Summer, and I refuse to put it back on. Sorry to those that dev and support it, but seriously, out of all the cases on here, and there have been a bunch, only one was on a phone that didn't have CM7 on it.
Click to expand...
Click to collapse
Most of those phones from the 'CM Scare" had bad nand blocks, and it had to be replaced. They had them frothe very beginning, but just decided to act up then. It also happen to some users using MIUI.
Okay my speaker got distorted so I decided to unrooted to take it in for service. Now the phone is unrooted but theres only one problem! Now the phone will boot up to the normal home screen but within 2 to five minutes, it shuts itself down and boot back up to home screen again and the cycle starts again. I have reset few times but same ting' happens. Now sprint is ordering a new phone for me hope its not the 3D i don't think I like it. So now I have my evo still but will give it to sprint once my new phone is in at the sprint store tuesday! Oh by the way, beside the speaker problem the phone was working fine as normal before the unrooting. thx
teh roxxorz said:
t also happen to some users using MIUI.
Click to expand...
Click to collapse
No! Don't say that!!
tony_2018 said:
What is up with that, I'm about to remove this rom its not really all that. Its already messed up my keyboard, sometimes I have to take the battery out just to restart it.
Click to expand...
Click to collapse
I've been using CM for about a year and NEVER had either of those two problems. There has to be an issue with something else you've loaded onto the phone that isn't playing nice.
Concordium said:
I've been using CM for about a year and NEVER had either of those two problems. There has to be an issue with something else you've loaded onto the phone that isn't playing nice.
Click to expand...
Click to collapse
No one ever said every install of CM7 will lead to this bootloop, but almost every case of this bootloop, the user was running CM7
HipKat said:
No! Don't say that!!
Click to expand...
Click to collapse
Miui is based of cm's fixes and what not right?
Having trouble with AOSP? http://forum.xda-developers.com/showthread.php?t=1295702
No, MIUI is not based on CM. It's a completely different ROM
Yeah but I'm pretty sure they use their fixes since its a port
Having trouble with AOSP? http://forum.xda-developers.com/showthread.php?t=1295702
It's true that most of the cases happened on CM7, but from what I understand it can happen on any rom... and has happened on Sense and AOSP.
There's no known fix. You can try to RUU, but even if the RUU flashes properly, the phone will never boot. You're eternally stuck with hboot/fastboot. File an insurance claim, that's about all you can do. I had a similar problem with a stock, never-been-rooted Evo. I got a replacement through insurance without paying the deductible, but I was s-on.
Hopefully I don't get slammed for suggesting this, but if you don't want to pay the deductible for a "lost" phone, you can flash a radio through hboot and pull the battery. If you do it at the right time, the phone will completely brick and never turn on again. It may take a few tries. Then you can take it in and you shouldn't have to pay the deductible, as long as you play dumb of course.
I think this happens due to bad nand blocks on your boot partition, so the main cause is hardware. Something in the rom triggers the never-ending splashscreen bootloop (I'm assuming something related to the boot.img). I could be entirely wrong about this though.
You can't live in fear, if it happens it happens. It's one of the risks you take when rooting and flashing. The number of cases is small compared to the number of people with rooted Evos, especially considering only a portion of people are active on this site, and a lot of the reports come from members that wouldn't post or even be a member if they didn't have the problem. I wouldn't let the possibility deter you from running whatever rom you want.
Sent from my Evo + MIUI using Tapatalk!
I myself am stuck with same issue. Nothing takes. So where does hboot reside when loaded? I also have looked in vain for diagnostic flashes....
Now one thing I noticed is that I installed PDAnet and it shows it installed an app to the phone, however I cant connect. I think cause I cant boot the phone and enable what it telling me to...so how is it this software can load an apk and I cant?
Overall, I am now however learning and it has become a hobby.
Theres an answer somewhere I would think. Thinking maybe its time to tear apart and look for jtag points....
I have had this happen to me a few times, I leave the RUU on the sd card and when this happens and do what bimmerman7 wrote on the first page. This has always worked for me when I get stuck in a bootloop when trying to access recovery.
Hi,
I'm not a very well versed with this rooting thing so I hope you guys can help me out here with some guidance. I have rooted a Desire HD for my friend quite some time ago. I follow step by step tutorial and managed to get it up and working with a custom ROM despite not knowing what half the steps are about.
Now, I tried to flash ICS 8.0 for him and it seems that it wasnt flashed properly as it is on a reboot loop over and over again. I did a factory restore before flashing and flashed using clockworkmod.
The main problem lies within I only remember parts and pieces of how I manage to root his phone the last time. How can I get it back working again without wiping off the root and s-off etc. Or is this just a small problem where I can reflash the rom without having to do all those again?
Let me know if you need any information about the phone. Thanks
If you are still able to get into recovery, make sure you do a FULL WIPE. Afterwards re-flash the rom and reboot your phone, should be fine.
---------- Post added at 10:07 AM ---------- Previous post was at 10:04 AM ----------
And something more:
if you're not sure what is the correct wipe you must do before installing a new rom, download this Super Wipe script (it's actually from ARHD but works with any rom ofcourse as it's just a full wipe), then you are 100% sure the problem will not lay with the wiping.
I tried to hold on to volume up key while powering on and all I get is 3 short vibrates and the yellow led on top blinking. The screen is blank, not even lit. Any idea what this means?
turn the phone off, pull the battery out and turn the phone on while holding the volume down button.
Now get into recovery and to a full wipe
so clear the cache partitions etc.
than flash again
btw ICS 8.0 does not excist
i gues you mean the 8.0 build from lord C ?
hi!
I've managed to get it to boot up in recovery mode! It was my stupidity to boot it up while pressing volume up when actually you had to press volume down. Got ICS up and running. Sorry for the confusion. Yep I was referring to the version 8 of the IceColdSandwich
I'll be sure to lurk around for more updates!!
orenzai said:
hi!
I've managed to get it to boot up in recovery mode! It was my stupidity to boot it up while pressing volume up when actually you had to press volume down. Got ICS up and running. Sorry for the confusion. Yep I was referring to the version 8 of the IceColdSandwich
I'll be sure to lurk around for more updates!!
Click to expand...
Click to collapse
No problem youre welcome
no questions anymore?
maybe about ics?
haha some bugs so far. the camera stopped working after 1 day. it focuses and snaps but the photo isnt saved. it worked when i first flashed it yesterday
Happend to me too. Use an alternative camera app for the issues with the cam
Sent from my Desire HD using xda premium
This is what happens when you dont read. These roms are always in the beta considered beta nad not really meant for people that dont know what they are doing or not willing to spend the time to read about it. Custom roms are not meant to be flashed to be part of the cool crowd. They are meant to help people learn how to do develop things on their own and how to trouble shoot issues.
zelendel said:
This is what happens when you dont read. These roms are always in the beta considered beta nad not really meant for people that dont know what they are doing or not willing to spend the time to read about it. Custom roms are not meant to be flashed to be part of the cool crowd. They are meant to help people learn how to do develop things on their own and how to trouble shoot issues.
Click to expand...
Click to collapse
I was expecting bugs. I'm on that likes to try out the newest things. But never mind, it's my friends phone and he couldnt bear with the bugs. It rebooted a few times randomly last night. Told me to flash it back to gingerbread for him. I'll keep an eye for the thread for more updates. Thank you all so much for the help guys!:laugh: