[Q] device reboots always - Desire Q&A, Help & Troubleshooting

Hi xda folks.
in short:
Phone is s-off and rooted through revolutionary.
Lately I flashed a new rom [ROM][Android 2.3.7][Oxygen_r2 HBOOT]MIUI 2.3.7c modded by moss20.
I did run the a2sd+ installations scripts as documented on the rom thread.
One week after flashing, phone became slow and lagging.
Eventually one week later phone was down out of battery without me noticing.
Since then phone reboots after entering my pin code or later.
How can I figure out where the issue originates?
For those who wants more details here is the full history:
My phone is 3.5 years old. I never had problems. And succeeded for a long time to s-off, root and flash roms thanks to this forum.
I have a 8Gb class 4 sd card with 4Gb fat 32 partition followed by one 4Gb of ext4.
Latelly flashed that Miui based rom http://forum.xda-developers.com/showthread.php?t=1725629. I used the oxygen r2 Hboot, the little rom version and activate the a2sd+. After a week the phone became really slow and lagging. Then eventually I found my phone off, abnormally out of battery without noticing how it happened.
Since then it is rebooting from the moment I have entered my pin code.
I thought that flashing a new rom (sense rom) would help but the problem persits. I then used a bigger hboot from alpharev and flashed the sense rom again. It didn't help.
I had a little improvement when completely repartitionned the sd card with 6Gb fat32 partition followed by a 1 Gb ext4. Since then it do not always reboot after entering pin code. It somes times stays up for 10 minutes before rebooting. Using some apps on the phone most likely quickly trigger a reboot.
The last thing I did with no success is to reset stock Hboot and RUU following suggestion of http://forum.xda-developers.com/showthread.php?t=1103520. Behavior is the same as the last one.​
I have no backup.
Any help to spot or fix that reboot issue would be greatly appreciated I love this phone

75 view but no reply?
Is my post wrong? Too long?
I need at least some leads the find investigation paths.
I have the feeling it could be related to the access to the SD card. Because It is the 1st I executed manually the a2sd+ installation scripts. How can I check that?
Or is it possible that some tweaking in the MIUI based rom (see link in OP) brought instability (voltage, ...)?

AntoineWils said:
75 view but no reply?
Is my post wrong? Too long?
I need at least some leads the find investigation paths.
I have the feeling it could be related to the access to the SD card. Because It is the 1st I executed manually the a2sd+ installation scripts. How can I check that?
Or is it possible that some tweaking in the MIUI based rom (see link in OP) brought instability (voltage, ...)?
Click to expand...
Click to collapse
1st, don't be impatient
What recovery do you have installed?
If you have trouble just after installing/activating an a2sd script it could have something to do with your partitions.
The best known method to partition/format your sdcard is using 4ext recovery.
Another problem could be the sdcard itself, maybe try another if handy.
What could help in general is power off phone, remove battery and eject/insert sdcard a few times,
just in case there's a little contact problem.
You should always be aware of what hboot you use for your rom, so what rom do you actually use and what hboot have you flashed?

tom0769 said:
1st, don't be impatient
What recovery do you have installed?
If you have trouble just after installing/activating an a2sd script it could have something to do with your partitions.
The best known method to partition/format your sdcard is using 4ext recovery.
Another problem could be the sdcard itself, maybe try another if handy.
What could help in general is power off phone, remove battery and eject/insert sdcard a few times,
just in case there's a little contact problem.
You should always be aware of what hboot you use for your rom, so what rom do you actually use and what hboot have you flashed?
Click to expand...
Click to collapse
Recovery: the one installed via revolutionary.
The trouble did not come immediately after installing a2sd+ but 2 weeks after.
I am using GParted to partition my SD card (and repartionned several times since issue stared)
I did not try an other sd card but I will try.
I did eject/insert the sd card lots of time since the issue started.
When the problem occurred I had HBOOT oxygen r2 from alpharev.
currently I am back on stock (and issue persists):
HBOOT (0.75.0000, S-ON),
rom (RUU_Bravo_HTC_Europe_1.15.405.1_Radio_32.30.00.28U_4.05.00.11_release_121684),
radio 4.05.00.11
I can root and S-OFF + recovery whenever needed.

Today my phone stayed up for 12 hours.
It was charging almost all day long.
Could my issue be related to battery issue?
My problem started when I noticed the battery was completely uncharged. Until today I did not charge it more than necessary to be at 100%
I checked the contacts and they look ok (not bend and straight).

AntoineWils said:
Today my phone stayed up for 12 hours.
It was charging almost all day long.
Could my issue be related to battery issue?
My problem started when I noticed the battery was completely uncharged. Until today I did not charge it more than necessary to be at 100%
I checked the contacts and they look ok (not bend and straight).
Click to expand...
Click to collapse
If problems still occur on stock unrooted firmware then it is likely a hardware rather than software problem.
Your setup looked correct before things went wrong. You partitioned your sdcard correctly with gparted, and your hboot wouldn't have anything to do with it.
You could try swapping battery, no harm in trying, see if that makes a difference.

eddiehk6 said:
... You could try swapping battery, no harm in trying, see if that makes a difference.
Click to expand...
Click to collapse
Thank-you eddiehk6, I hope it is the battery. It is going better but the phone remains unstable by moments.
I was not aware a battery could be so cheap for 'old' devices.

eddiehk6 said:
If problems still occur on stock unrooted firmware then it is likely a hardware rather than software problem.
Your setup looked correct before things went wrong. You partitioned your sdcard correctly with gparted, and your hboot wouldn't have anything to do with it.
You could try swapping battery, no harm in trying, see if that makes a difference.
Click to expand...
Click to collapse
A strange thing I noticed is that the phone can stays forever without rebooting on the "enter pin code" screen.
When I enter the pin code it reboots between instantly 30 seconds.
Isn't this proving that it is not an hardware issue?

I swapped the battery but it did not change anything.
The only thing I noticed is that without a sim card the phone is more stable. It still reboots but only every few hours. With the sim card inserted it reboots every few minutes if I am lucky.
How can the presence of the sim have an influence on this behavior?

Think you've got a hardware issue if it's still rebooting on stock ROM and after changing battery.
The SIM card will make a difference as it's connecting to a network, or trying to connect. Somehow it's causing instability -> reboot.
Only last thing I can think of is to s-off and flash latest radio version through fastboot. No guarantees this will work or make any difference.

I've got mildwild 5 and sometime when I'm using it or I want to take a pic the screen goes blank and I have to reboot it so annoying, what do you think the problem is?
Sent from my HTC Desire using xda app-developers app

try Evervolv Turba 4.0.0p2 ROM btw here is solution if phone overheats http://forum.xda-developers.com/showthread.php?t=2277365

Mine is starting to reboot for no reason.
Sent from my HTC Desire HD A9191 using XDA Free mobile app

Related

3 Incredible's dead - up to 5 now

So I've had two incredible's now fall in to a boot loop
(wiped, pulled battery, RUU'd, went back to s-on - nothing worked)
first one I had for about 8 months with no issues until now. they did
send me a replacement XD and it did the same thing!
Now my wifes phone is doing it :\
I'm just verifying - if I RUU/S-on/remove sd card - then it HAS to be a hardware issue right? nothing that I could have done?
[Further info if needed]
All had CWR 3.0.0.5 and were rooted via unrevoked
h0x90 said:
So I've had two incredible's now fall in to a boot loop
(wiped, pulled battery, RUU'd, went back to s-on - nothing worked)
first one I had for about 8 months with no issues until now. they did
send me a replacement XD and it did the same thing!
Now my wifes phone is doing it :\
I'm just verifying - if I RUU/S-on/remove sd card - then it HAS to be a hardware issue right? nothing that I could have done?
[Further info if needed]
All had CWR 3.0.0.5 and were rooted via unrevoked
Click to expand...
Click to collapse
Were you using the same ROM or kernal each time?
It's the new cwm. It uses a different gscript setup. To a restore or flash incredible reengineered 2.3.1
If not that then I don't know. Did it happen after a Rom flash?
Sent from my Incredible using XDA App
well the first one was running Evervolv and had been for about 3 weeks.
it crashed during a phone call and never booted all the way again. (boot loop)
The second (This ones replacement) was running cm7 (Flashed it right as I got it) and worked fine the first day I had it (but I wasn't using it much that day) then it died while using the browser and fell victim to boot loopage.
The third one (my wifes phone) died about an hour later while using the browser but would still boot - but not stay on for very long. Especially if any sort of data was going on (like syncing with gmail). I figured since it was kind of working maybe it was the rom so I flashed s-on went back to stock 2.2 (ruu) where it now dies upon lock screen.
(or before sometimes)
[Ninja edit] Wifes phone had been running evervolv the amount same time as my first phone
all three were running latest CWM and had the default kernel for the rom they had. Also all 3 were flashed ruu and s-on including a clear storage for good measure (Verizon also had me do a factory reset come to think of it - before they would ship replacements)
Ianxcom said:
It's the new cwm. It uses a different gscript setup. To a restore or flash incredible reengineered 2.3.1
If not that then I don't know. Did it happen after a Rom flash?
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
could cwm leave something behind that would continue the boot loop after ruu?
That would suck because I've already sent in one phone would hate for them
to find something like that ><
have you tryed downgrading? i know i was having alot of issues with the new cwm. im running chingys rom and after the downgrade everything is running smooth again. cwm 2.5.1.2 seems to be working better...
HandsomeRob2310 said:
have you tryed downgrading? i know i was having alot of issues with the new cwm. im running chingys rom and after the downgrade everything is running smooth again. cwm 2.5.1.2 seems to be working better...
Click to expand...
Click to collapse
I've went complete stock everything (including recovery) and it didn't fix anything.
Have an update on the situation as well.
Verizon shipped me another 2 phones - both broken out of the box.
The first one just reboots over and over again and can't even enter recovery.
On the second device the speaker is blown -.-
Are you using the same or different SD card(s) amongst these failing devices?
The one you had running for 8 months, was that SD card at end of life?
Asking, as AOSP ROMs interact quite a bit more w/ the SD card than do Sense ROMs, so if your issues are all with AOSP ROMs, I suspect wonky SD card(s).
smtom said:
Are you using the same or different SD card(s) amongst these failing devices?
The one you had running for 8 months, was that SD card at end of life?
Asking, as AOSP ROMs interact quite a bit more w/ the SD card than do Sense ROMs, so if your issues are all with AOSP ROMs, I suspect wonky SD card(s).
Click to expand...
Click to collapse
I got that SD back when I got the phone so I hope its not
at the end of its life span.
I've actually didn't bother putting the SD cards in this last batch
because they were showing issues immediately (without any modding)
Thanks for the info on AOSP roms that could help diagnose future problems
That would explain a lot, actually, as AOSP ROMs call the sd during boot.
Sent from my ADR6300 using XDA App

Can internal memory be corrupted??????

Hey Guys,
I've been some flashing lately and I'm not sure what caused the problem. I've been using SprintLovers Rom with no issues since Feb. But when it stopped being supported, so I switched over to [ ROM / 5-3 ] Calkulin's EViO 3 v1.0 Beta 2 [ 4.12 l Gingerbread l Tweaked ] (which IO loved by the way)but I kept getting constant reboots. I would be using Navigation or watching a video with Rock Player and within one min , my phone would go into a boot loop and stay rebooting until and I flashed the rom again. It drove me nuts and I couldnt take it anymore.
So I reformatted everything (even deleted my card by accident) and installed [MikRoms] - [6/7/2011] - MikG v1.03 - Re-Engineered GB Sense 2.1 + 3.0 (which I also love) and the reboots are not as frequent but they are still happening. The difference is that with this rom, its getting stuck in a boot loop at the HTC EVO 4G screen that you see when it boots up. If it does boot up, the phone gets to the Sense screen and reboots again. So the only way I can get it to boot back up is to flash the rom again from recovery.
I have a 32GB Duracell Microsd Card I got off Amazon: http://www.amazon.com/gp/product/B004AM6SOG
It worked perfectly with Sprintlovers rom, But as soon as I reformatted and flashed Calkuns rom, the reboots started,. I even tried using Nandroind and going back to a Sprintlovers backup and the reboots were happening on that rom and I never had issues with that rom.
So basically I'm trying to narrow down what is causing the rebooting. I thought maybe the memory card was going bad, but how can I tell? So what I started thinking was maybe my bootloader needs to be refomattted or cleaned? But I dont know how. Then after talking to Nick1313, who helped me reformat and get my phone running again, we started thinking maybe the internal memory of the phone has gotten corrupted. I assume that Android looks to boot the OS from the internal memory and then looks to the SD card for apps and etc....
Is there a way to test my SD card to see if its ok? is there a way to see tell if my internal memory is corrupted and if so can it be reformatted and fixed?
I saw some people having a similar issue in the Galaxy S forums,but no one seemed to have a solution.
My last resort is unrooting and returning my phone to the store tomorrow. The only problem with that is , I know they are gonna have to order me one and it wont be in until Monday or whatever and the is annoying.
Any ideas would be greatly appreciated.
Snarky Answer: Well, I now know which memory card NOT to get.
Serious: I really doubt your SD card has much to do with this. Internal memory does have the potential of getting corrupted. That said, it's not likely.
It's obvious that you had good specific reasons for flashing the rom you've flashed. My advice is to flash one that you've not flashed and see if your phone's behaviour is any different.
jesuspgt said:
Snarky Answer: Well, I now know which memory card NOT to get.
Serious: I really doubt your SD card has much to do with this. Internal memory does have the potential of getting corrupted. That said, it's not likely.
It's obvious that you had good specific reasons for flashing the rom you've flashed. My advice is to flash one that you've not flashed and see if your phone's behaviour is any different.
Click to expand...
Click to collapse
Thanks for the reply. I actually Flashed back to Sprint Lovers Rom last night to after deleting everything again and reboots were still happening. I flashed back to MikG rom this morning. No reboots as of yet. But it rebooted on me 5 times last night before I flashed Sprintlovers.
GPS has been the main app I've busing when the rebooting starts. So I'm testing my phone right now with having it map to a far location and keeping my screen on to see how long it takes to make my phone reboot. Right now I'm 3mins into the test.
Turns out the processor in my phone is bad and Sprint has to order me a new one

[Q] Random shutdowns & bootloop on all roms!

Hi Everyone
I was hoping someone would be able to help me out as I’m a total Noob!
I have an HTC Desire on the Orange network in the UK. I started to get a few problems with my phone shutting down and restarting, my GF’s brother had been recommending that I root and flash a different rom for a while, and seeing as he has a Desire on the T-Mobile network and had never had any trouble with rooting his phone or any of the roms he used I decided to give it a shot.
I followed everything in Linkslovesandroid’s noob thread found here:
http://forum.xda-developers.com/showthread.php?t=1016084
I first tried CyanogenMod7 on GF’s brother’s recommendation, worked ok for a bit but I had problems with constant shutting down and restarting over and over again, is this called bootlooping? The only way to stop it was to remove the battery, even then it was no guarantee. Other things were going wrong like the screen freezing, certain buttons were unpressable etc.
I gave my phone to him and he couldn’t explain why such weird things were happening as his Desire experienced no problems at all. He suggested I try something different like GingerVillain. GV never loaded or booted up for me, I wiped data / factory reset, wiped cache, wiped dalvik, installed zip from SD, the rom would then install okay but when I rebooted the phone never ever got past the Alpha Rev S-off screen. This happened when I tried to install GV 2.5 and 2.6, I see that 2.7 has just been released but don’t see the point in trying seeing as the other 2 versions wouldn’t work.
I then tried Oxygen, again, worked ok for a while but started giving me random shut downs and restarts. Once I was driving down the motor way using sat nav software and the phone just shut down! I had to find somewhere to pull over to restart the sat nav software and again it restarted itself! Lol!
One day my phone went into an endless bootloop, no matter how many times I took the battery out the phone just wouldn’t stay on, I had to flash a new rom just to get the phone to fully boot up! I went back to CM7 but have the same old problems, so now I’m using MIUI and I’m still getting shutdowns!
What is wrong with my phone? If anyone has any ideas what I might’ve done wrong, or whats causing problems please offer your suggestions! I don’t really like the sense Roms, I’d like to try GingerVillain but I could never get it to install! I just need my phone to be stable enough to know I can send an SMS to someone without it restarting! If you need to know about Kernels or radios or anything please just ask me (and tell me where I can find out!) Like I said, I’m a noob when it comes to phones!
Same kind of problems here. Random restarts (no shutdowns) on various roms, including the original stock froyo. Happens mostly while installing stuff from the market.
Any ideas?
Sounds like the motherboard is faulty/hardware error. Send back to repair. Usually the kernel can cause problems and OCing (restarting), but you said, that it happens randomly on every ROM, so that means it is more likely a hardware problem.
I had this too, same symptoms sent it back to HTC, duff motherboard, back in 14 days and all working fine.
Only thing is it got reset to original contract so had to pay to unlock it and then root etc.
But well worth it!
Hi Guys
Thanks for your replies so far!
So is it likely that my motherboard was faulty all along? I used to get random restarts sometimes when I was on the sense that came pre-installed on the phone, but nowhere near as often as I get now I've rooted and flashed new roms.
Is it possible that I've damaged it in some way? That could get me in some trouble because when I rooted I'd have voided my warranty, if I send it back to Orange as faulty now they'll know and could pretty much tell me tough luck!
I've heard you can unroot and put your phone back to how it was, but they'd still be able to tell wouldn't they?
Has anyone ever sent a phone back for repair through Orange UK?
Thanks again for your responses so far guys!
For me it turned out that the SD card was corrupt in some way. Repartitioned and reformatted it, and this does help for now. Might try that first, before sending into repair.
Good luck!
reynard80 said:
For me it turned out that the SD card was corrupt in some way. Repartitioned and reformatted it, and this does help for now. Might try that first, before sending into repair.
Good luck!
Click to expand...
Click to collapse
I agree. If you have system files on your SD and if the SD gets corrupted you might get the result you've described.
That's interesting, the other night when I had such a severe bootloop that I had to flash a new rom just to get the phone to fully boot up, it only booted after I'd removed the SD card.
To begin with I was very happy because I thought I'd solved the problem and all I'd need was to buy a new SD card, however a short while later it happened again with no SD card inside at all!
I decided to give Ginger Villain another go hoping that removing the SD card after "install zip from SD card > reboot" would allow it to boot up, it didn't. Never got past the alpha rev screen.
How will I know if I have system files on the SD card? Should I maybe try the G-Parted stage of the noob guide again to reformat the card and create the ext-4 partition?
Thanks again for your time and help by the way!
dellaclearing said:
That's interesting, the other night when I had such a severe bootloop that I had to flash a new rom just to get the phone to fully boot up, it only booted after I'd removed the SD card.
To begin with I was very happy because I thought I'd solved the problem and all I'd need was to buy a new SD card, however a short while later it happened again with no SD card inside at all!
I decided to give Ginger Villain another go hoping that removing the SD card after "install zip from SD card > reboot" would allow it to boot up, it didn't. Never got past the alpha rev screen.
How will I know if I have system files on the SD card? Should I maybe try the G-Parted stage of the noob guide again to reformat the card and create the ext-4 partition?
Thanks again for your time and help by the way!
Click to expand...
Click to collapse
If your rom requires an sd-ext partition than it stores system files on the SD. Try a rom that doesn't require that. I would go as far as bringing the phone to stock just to verify if it's the phone or the SD. Bringing it back to stock is a requirement for you to return it for servicing if you realize that it's a problem with the phone not the SD.
paul.c said:
If your rom requires an sd-ext partition than it stores system files on the SD. Try a rom that doesn't require that. I would go as far as bringing the phone to stock just to verify if it's the phone or the SD. Bringing it back to stock is a requirement for you to return it for servicing if you realize that it's a problem with the phone not the SD.
Click to expand...
Click to collapse
Hi Paul, is it only stock roms that don't store system files on the SD or can you recommend a rom that doesn't require an ext partition as I'm not too sure what I'm looking for? I realise that I'll have to unroot before I can return the handset but if there's another custom rom out there I can test before unrooting that'd be good!
However, if you fully recommend returning the phone to stock to test then that's what I'll do!
dellaclearing said:
Hi Paul, is it only stock roms that don't store system files on the SD or can you recommend a rom that doesn't require an ext partition as I'm not too sure what I'm looking for? I realise that I'll have to unroot before I can return the handset but if there's another custom rom out there I can test before unrooting that'd be good!
However, if you fully recommend returning the phone to stock to test then that's what I'll do!
Click to expand...
Click to collapse
This ROM http://forum.xda-developers.com/showthread.php?t=896213 doesn't require SD for system files.
I'd first try the complete stock rom with a completely formatted SD card. You can be completely sure that there isn't a software problem with a custom rom.
If this doesn't work, try replacing the SD card. This did help for me.
If still no succes, send it for repairs.
paul.c said:
This ROM http://forum.xda-developers.com/showthread.php?t=896213 doesn't require SD for system files.
Click to expand...
Click to collapse
Thanks for linking me to that rom.
I did a bit of reading about roms that use ext sd partitions and have so far concluded that its for A2SD so an entire app can be run from the sd card instead of internal memory.
So anyway, I've just installed the Redux rom you linked me to that doesn't store sytem files on the sd, first 2 boots had a sudden shutdown and restart! I'm on the 3rd boot now, it's holding okay but I need to put it through its paces to see how long it can go and what sort of performance it will allow before it starts shutting down on me!
reynard80 said:
I'd first try the complete stock rom with a completely formatted SD card. You can be completely sure that there isn't a software problem with a custom rom.
If this doesn't work, try replacing the SD card. This did help for me.
If still no succes, send it for repairs.
Click to expand...
Click to collapse
Hi Reynard. If the Redux rom I've just flashed (less than 10 minutes ago) doesn't use the sd for system files, then if it keeps rebooting on me would that diagnose a faulty motherboard as reliably as using a stock rom?
I'm gonna unroot and flash a stock rom soon anyway, that way I can be sure before I send it back to Orange for repair, although apparently there isn't an official Orange UK stock rom available so I'm just gonna have to get as close as I can and hope they don't notice!
dellaclearing said:
Hi Reynard. If the Redux rom I've just flashed (less than 10 minutes ago) doesn't use the sd for system files, then if it keeps rebooting on me would that diagnose a faulty motherboard as reliably as using a stock rom?
I'm gonna unroot and flash a stock rom soon anyway, that way I can be sure before I send it back to Orange for repair, although apparently there isn't an official Orange UK stock rom available so I'm just gonna have to get as close as I can and hope they don't notice!
Click to expand...
Click to collapse
Probably there is a ROM just that it hasn't been leaked so I hope you won't get in trouble.
paul.c said:
Probably there is a ROM just that it hasn't been leaked so I hope you won't get in trouble.
Click to expand...
Click to collapse
Haha! Me too!
Dayamn! I didn't have a reboot all day on Redux, got home from work and installed Sygic sat nav software and the phone rebooted 3 times just while downloading the map! I had to remove the battery once as well.
Decided I'd just test Google maps navigation while driving to pick up the Mrs from work and it shut down on me
If I can get hold of another sd card to test I'll see if it makes a difference, but there's not really a lot more I can do now other than unroot and send it back to Orange. The strange thing is that it never used to reboot half as much on the stock rom the phone came with, and it never did it while I was sat nav'ing ever. It just used to happen randomly when I was texting or web browsing. Odd.
Where might be the best place to find the closest to stock rom for Desire Orange UK?
Just wanted to update you all.
I found my original SD card that came with the phone, I fully formatted it and then did a completely fresh install of Redux and performed the same tests and got the same results. Still crashed and rebooted! So that tells me it's the phone and not the card!
I'll be restoring to stock and calling Orange tomorrow to get a replacement / repair.
Thanks to everyone who helped me out along the way, your time and effort is very much appreciated!
Hi guys,
I made a goldcard and tried installing the stock ruu, it seemed to work but when I hold vol down and power on it still says:
AlphaRev
BRAVO PVT1 SHIP S-OFF
HBOOT 6.93.1002
I read on the Alpharev website that recent versions of Alpharev aren't overwritten by stock ruu's hboot so it must first be downgraded. I used android flasher to flash the Alpharev downgrader, then it just froze at the "why so serious" screen. I was advised to flash the stock bravo hboot found on the alpharev website, which I did and then I was finally able to install the ruu. Obviously I've done something wrong and I'm guessing its flashing the stock bravo hboot...
Would it be okay to use android flasher again to run just the downgrader image, and then using fastboot flash the ruu again?
Any ideas? I don't want to risk sending my phone back for repair still saying S-Off!
Okay, I kept reading through XDA and found a post by Dzumagos advising someone to do exactly what I just asked, use Android Flasher to run the Alpharev downgrader image and then reflash stock ruu, so I grew a set and tried it myself!
Bravo PVT1 SHIP S-ON
HBOOT-0.93.001
Voila! I'm now back to S-ON, so now I feel I'm ready to call Orange and tell them about the constant shutdowns and restarts, which have still been happening on stock btw, the phone also feels really hot too!
I just hope the replacement they send me is issue free!
Thanks again to everyone who helped out in this thread and in the orange uk ruu thread!
Cheers everyone!

hTC Desire keeps freezing after on rooted ROMs

Hey guys.
A while ago I`ve rooted my hTC Desire and did an S-OFF, to be able to install custom ROMs.
I`ve "tested" a few custom ROMs, but none of them seemed to be stable.
Currently I`m on SuperNova_Classic_2.0.2.0 with built in Data2SD (iData2SD)(the idea is to have a stable rooted ROM, with DATA2SD and Sense), but every time I flash the rom, then install my fav apps, the phone keeps freezing at certain points, sometimes it runs OK for a week - with no freezing - other times it freezes in the first couple of days after ROM flash. I`ve tried not to install that many apps, but I`m still facing this freeze problem.
Has anyone experienced this before?
Here are the steps I took for ROM flashing
1. Created a 1GB ext4 partition on SD-CARD, preceded by a FAT32 partition(as required in the tutorial of Supernova)
2. Rebooted into Recovery - wiped data/factory reset; wiped cache partition; wiped Dalvik Cache
3. Installed the ROM zip file from SD-CARD; on first boot, except for the Wi-Fi connection, I haven`t touched anything(google accounts etc. - skipped all steps - ), waited for the system to stabilyze, then did a normal reboot in order for the DATA2SD function to work. After next reboot, DATA2SD was working properly(I even had the pink LED light up), Storage Information was showing the 1GB ext partition as an internal memory.
4. Installed all my apps, configured phone, widgets etc.
This way, at a certain point, the phone simply freezes, have to remove the battery to be able to use it again.
Here are my phone specs:
Bravo PVT1 SHIP S-OFF
HBOOT-6.93.1002
MICROP-031d
TOUCH PANel-SYNT0101
RADIO-5.17.05.23
ClockworkMod Recovery v5.0.2.0
Transcend class 4 - 16GB microSD card
I`ve searched and searched on xda-developers, but haven`t found an answer for my problem, yet.
What am I doing wrong here?
Any help would be DEEPLY appreciated !!!
This is no help to you.... but I'm having exactly the same issue.
Sometimes it freezes when starting a game, but most of the time it won't unlock(ie phone unresponsive when I try to wake it).
This is not ROM related as it happened on several different Roms, with a full wipe between. I'm not overclocking.
The only things I can think of are:
-Partially corrupt ext partition on SD.
-failing hardware.
-some other sw issue ie radio(which has worked for a while before this started happening).
Thanks for your reply, Shaun - it does help, at least now I`m not alone in this
You`re right, it`t not ROM related, I`ve tried different ROMs myself, same problem.
I`ve also tried another SD CARD (class 2).
I don`t think it`s the radio, I have the latest version, the version required on Supernova tutorial for best compliance.
I really don`t want to believe that it`s a hardware fault, as I didn`t overclock either and always read/followed the exact right/official steps in root-ing/flashing ROMs.
I`ve reinstalled Supernova now, with absolutely no additional installation of fav apps. Going on 2 days with no freezeing, so far.
I`ll keep post-ing if any new developments occur.
Cheers.
You've not installed any apps at all? hmmm.
When you do re-install your apps(I assume from Titanium backup?), it'd be interesting to see if it starts freezing again.
This would then suggest either a dodgy app that we both have, or titanium backup itself causing the issue.
What SD card specs?
Sent from my HTC Desire using xda premium
rootSU said:
What SD card specs?
Click to expand...
Click to collapse
I'm using the same card that i've had for the last 18 months-
it's an 8gb class 2 card with 768mb partition, the rest is Fat32.
I`ve started reinstalling some of the apps, the most important ones, like iGo, YahooMessenger, YahooMail, etc., but didn`t use Titanium Backup, installed them manually using Market.
So far, so good, no freezing.
My SD CARD specs: Transcend Class 4 - 16GB; 1GB ext2 partition for apps, and the rest is FAT32.
LE
I could be wrong, but from what I`ve seen so far, I would recommend NOT to use widgets that require superuser permissions. Also, before flashing any pre-rooted ROM, be sure to turn "Signature verification" OFF, in the phone`s "Recovery" screen options. If your ROM has any kind of "Data2SD" scripts integrated, after flashing ROM - at first boot, DO NOT configure anything (google account, sync, etc.), DO NOT download/install any apps yet, ONLY enter the Wi-Fi settings(if that is the case); leave the system to stabylize, then do a normal reboot(if the ROM supports "Fast boot" - turn it OFF before rebooting). At second normal boot, the DATA2SD scripts should kick in ( u should see the phone`s notification LED turn to: pink or blue - depending on the script used by the ROM).
A class 2 is a definite no no for Data2sd IMHO. Class 4 is debatable. I had a bit of lag with an older version of data2sd on a class 4. It may be better now, Depends what speed the card writes at really. If its minimum for class (4 MB/s) that could be a bit touch and go. EXT 4 would be the best option for the 2nd partition
I recommend using an a2sd+ solution temporarily to see if the freezes go away
I would mind the lag, I didn`t get any lag using my card though, but just saying, would mind if it would be laggy, the real problem is the constant freezing I`ve had.
If it`ll freeze again, I think I`ll go back to stock Froyo, use Apps2SD and install only the bare minimum.
U know, another thing I never quite understood, I think hTC makes one of the best smartphones on the market, but they limit their possibilites with small batteries and very little internal storage space. What`s up with that?
rootSU said:
A class 2 is a definite no no for Data2sd IMHO.
I recommend using an a2sd+ solution temporarily to see if the freezes go away
Click to expand...
Click to collapse
I'm not using Data2SD. I'm using A2sd+. Same partition that I used on my Hero, and now my Desire for the last 14 months. Still getting freezes.
I don't think it's a speed issue.
a2sd should be fine on a class 2. What a2sd solution is it? Did you move dalvik too?
Its just a logical approach thats needed.
1) Eliminate the SD card by not running from it.
2) Change the rom
3) RUU
If after all that it still freezes, sounds like HW....
rootSU said:
a2sd should be fine on a class 2. What a2sd solution is it? Did you move dalvik too?
Its just a logical approach thats needed.
1) Eliminate the SD card by not running from it.
2) Change the rom
3) RUU
If after all that it still freezes, sounds like HW....
Click to expand...
Click to collapse
Yeah that's pretty much what I was thinking.
I'm currently on InsertCoin with A2SD+. I was on LeeDroid, then RunnyMede before that with the same issue. I did a full wipe when swapping Roms. Not sure about Dalvik- if it's done in the Rom then yes, otherwise I haven't consciously moved it.
1) I might try a different SD that i have lying around- Nandroid it etc.
2) As above, already done that.
3) Last resort. Although a rooted RUU wouldn't be a massive issue for a day or 2.
If it's HW, I better get some insurance.
Edited to add: my SD card is actually a class 4. SD card tests suggests read speeds of 19-20mb/s and write speeds of 7-9mb/s.
Fixed my issue. It's the Kernel. Apparently the latest 2 kernels have the ability to undervoltage when not in use. Unfortunately, this can also cause the lockups i've(and possibly you've) been experiencing.
The last kernel without this in is: 2.6.35.14_110911.
This has 100% solved my issue and I recommended flashing it if you still having the same issue.
Great.
If I get another freeze, I`ll flash the 2.6.35.14_110911 kernel u`ve recommended.
Thanks a lot, dude.
If ever in Romania, look me up, got a few beers with your name on them
LE
If it`s not too much to ask, could you possibly post a download link for that kernel version?
i_cs_u said:
Great.
If I get another freeze, I`ll flash the 2.6.35.14_110911 kernel u`ve recommended.
Thanks a lot, dude.
If ever in Romania, look me up, got a few beers with your name on them
LE
If it`s not too much to ask, could you possibly post a download link for that kernel version?
Click to expand...
Click to collapse
No problem.
I've never been to Romania...
Kernel at the bottom of this post:
http://forum.xda-developers.com/showpost.php?p=18894823&postcount=10450
Did you flash the kernel while on existing ROM, or did you reflash de ROM as well?
And what ROM are u using with this kernel?
try using the earlier versions of super nova and data2sd, I also had the freezing problem but that was AFTER I upgraded to the newest version of supernova and data2sd
I`m using the 2.0.2.0 version, not the latest 2.4.0.0.
Earlier than 2.0.2.0?
i_cs_u said:
Did you flash the kernel while on existing ROM, or did you reflash de ROM as well?
And what ROM are u using with this kernel?
Click to expand...
Click to collapse
Flashed straight over the top. Insertcoin ROM.
Use the latest Supernova and see. It has a pretty good kernel.

Random Reboots Problem - please help

I simply have done all i can - and it seems that i cant do it right. Please consider to help me, because im noob.
Before i state my problem i should say that i have googled an crossed xda forum for 4 days and without any improvement.
Problem I have is that, my phone randomly reboots at no particular time or place - but here come the details:
First, for purpose of unlocking phone from SIM lock from carrier, it was S-OFFed and rooted by someone else (previous owner).
Rom was installed - Oxygen 2.3.2. and it worked for few months without bugs.
Then, one day it restarted and stuck in bootloops, but it came up for few seconds, or some time (but not for long), and then again restarted and so on. Eventually it held enough to do a factory reset which generally helped, but with one strange thing - clock couldnt sync and loosed about an hour for 5-6 hours (really strange).
Then i decided to try some other ROM hoping to resolve clock issue.
When I go into HBOOt it says:
--- AlphaRev ---
BRAVO PVT4 SHIP S-OFF
HBOOT-6.93.1002
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.27
Aug 10 2010 17:52:10
Then i went here -> http://forum.xda-developers.com/show...p?t=1315961URL and done REALLY step by step whole procedure.
ROM was installed, along with -> http://forum.xda-developers.com/show....php?t=1408936
It worked flawllessly for about half an hour an then started rebooting on no particular action - sometimes went up for some time few secs to 10-20 mins an then reboot and sometimes it got stuck in endless loop (only pulling the battery helped).
Since it went wrong, i tried to RESTORE previosly made BACKUP of mentioned OXYGEN ROM, but sadly, same thing happened all the time.
I was devasteted, didnt know what to do so I decided to get back to STOCK ROM via RUU. (thought it would solve the problem)
I used RUU_Bravo_Froyo_HTC_WWE_2.29.405.14_Radio_32.49.00 .32U_5.11.05.27_release_224699_signed
Phone stayed S-OFF (obviosly for AlphaRev HBOOT) but have been preety stable comparing what was happening before, in terms: restarted few times for a day and allways rebooted back. Then i inserted other SIM card ant it began again with restarts as soon it went up and been up for 10-20 secs. After few reboots, it stabilised, but had different problem: couldnt add new account, and couldnt remove one I set up at the beginning (message said that i should do FACTORY reset if i want account removed). So I did factory reset - and NOTHING HAPPENED - evrything stayed exactly as it was - with account and everything.
Then i came across BORTAKs Guide ->http://forum.xda-developers.com/showthread.php?t=1275632 and followed step one, although it doesnt exactly match my probs - in terms that my phone boots up most of the time, but restarts randomly...
So I did what I was supposed to do and installed CyanogenMod after following step 10 Amon Ra's Recovery (I have PVT4 device) but same thing continues to happen - reboots, apparently on trying to add account on phone...
SORRY FOR SUCH LONG POST, but Im out of ideas, and new to this so PLEASE< PLEASE HELP me if u somehow can...
Thanks in advice
goxyendzy said:
I simply have done all i can - and it seems that i cant do it right. Please consider to help me, because im noob.
Before i state my problem i should say that i have googled an crossed xda forum for 4 days and without any improvement.
Problem I have is that, my phone randomly reboots at no particular time or place - but here come the details:
First, for purpose of unlocking phone from SIM lock from carrier, it was S-OFFed and rooted by someone else (previous owner).
Rom was installed - Oxygen 2.3.2. and it worked for few months without bugs.
Then, one day it restarted and stuck in bootloops, but it came up for few seconds, or some time (but not for long), and then again restarted and so on. Eventually it held enough to do a factory reset which generally helped, but with one strange thing - clock couldnt sync and loosed about an hour for 5-6 hours (really strange).
Then i decided to try some other ROM hoping to resolve clock issue.
When I go into HBOOt it says:
--- AlphaRev ---
BRAVO PVT4 SHIP S-OFF
HBOOT-6.93.1002
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.27
Aug 10 2010 17:52:10
Then i went here -> http://forum.xda-developers.com/show...p?t=1315961URL and done REALLY step by step whole procedure.
ROM was installed, along with -> http://forum.xda-developers.com/show....php?t=1408936
It worked flawllessly for about half an hour an then started rebooting on no particular action - sometimes went up for some time few secs to 10-20 mins an then reboot and sometimes it got stuck in endless loop (only pulling the battery helped).
Since it went wrong, i tried to RESTORE previosly made BACKUP of mentioned OXYGEN ROM, but sadly, same thing happened all the time.
I was devasteted, didnt know what to do so I decided to get back to STOCK ROM via RUU. (thought it would solve the problem)
I used RUU_Bravo_Froyo_HTC_WWE_2.29.405.14_Radio_32.49.00 .32U_5.11.05.27_release_224699_signed
Phone stayed S-OFF (obviosly for AlphaRev HBOOT) but have been preety stable comparing what was happening before, in terms: restarted few times for a day and allways rebooted back. Then i inserted other SIM card ant it began again with restarts as soon it went up and been up for 10-20 secs. After few reboots, it stabilised, but had different problem: couldnt add new account, and couldnt remove one I set up at the beginning (message said that i should do FACTORY reset if i want account removed). So I did factory reset - and NOTHING HAPPENED - evrything stayed exactly as it was - with account and everything.
Then i came across BORTAKs Guide ->http://forum.xda-developers.com/showthread.php?t=1275632 and followed step one, although it doesnt exactly match my probs - in terms that my phone boots up most of the time, but restarts randomly...
So I did what I was supposed to do and installed CyanogenMod after following step 10 Amon Ra's Recovery (I have PVT4 device) but same thing continues to happen - reboots, apparently on trying to add account on phone...
SORRY FOR SUCH LONG POST, but Im out of ideas, and new to this so PLEASE< PLEASE HELP me if u somehow can...
Thanks in advice
Click to expand...
Click to collapse
Did you try to run RUU after flashing Alpharev downgrade to achieve S-ON gain, or you just ran it over Alpharev stock?
Also did you try to format sd card or to remove it from phone and than to boot it up?
It all seems like it was SIM unlocked by a "fake" code so that are the issues that can happen.
Plus: to gain SIM unlock you don't need S-off and root.
nlooooo said:
Did you try to run RUU after flashing Alpharev downgrade to achieve S-ON gain, or you just ran it over Alpharev stock?
Also did you try to format sd card or to remove it from phone and than to boot it up?
It all seems like it was SIM unlocked by a "fake" code so that are the issues that can happen.
Plus: to gain SIM unlock you don't need S-off and root.
Click to expand...
Click to collapse
I ran it over Alpharev... Im really new to this so i ask for help.
U say that i should:
1) flash AlphaRev downgrade to achieve S-ON gain (HOW exactly? please link to some guide if exists)
2) then run RUU
I tried formatting SD card later, removed it, even change card and latest ROM (Cyanogen) is on other SD card and its all the same...
Thanks for fast reply
goxyendzy said:
I ran it over Alpharev... Im really new to this so i ask for help.
U say that i should:
1) flash AlphaRev downgrade to achieve S-ON gain (HOW exactly? please link to some guide if exists)
2) then run RUU
I tried formatting SD card later, removed it, even change card and latest ROM (Cyanogen) is on other SD card and its all the same...
Thanks for fast reply
Click to expand...
Click to collapse
Yes, both steps. With that you will overwrite both hboot and radio to stock ones, that could be the things that made you problems. You will get S-on after flashing of RUU (I recomend 2.3) when your hboot is overwritten.
This is a good guide how to use ADB and fastboot (you will need fastboot for flashing of hboot):
http://androidforums.com/desire-all...fastboot-windows-updated-1st-june-2011-a.html
But reading your post I think that the problem is with unlocking (SIM). If a guy that sold you the phone said he did it with S-off and root he is laying, as I told you it can't be done with that. The problem can occur when you unlock the phone with a "fake code" that actually removes the part of phone's software used to check for carrier and not replacing critical parts (something like that).
There's a tool:
http://forum.xda-developers.com/showthread.php?t=943726
Try to run it and see what you will get.
nlooooo said:
Yes, both steps. With that you will overwrite both hboot and radio to stock ones, that could be the things that made you problems. You will get S-on after flashing of RUU (I recomend 2.3) when your hboot is overwritten.
This is a good guide how to use ADB and fastboot (you will need fastboot for flashing of hboot):
http://androidforums.com/desire-all...fastboot-windows-updated-1st-june-2011-a.html
But reading your post I think that the problem is with unlocking (SIM). If a guy that sold you the phone said he did it with S-off and root he is laying, as I told you it can't be done with that. The problem can occur when you unlock the phone with a "fake code" that actually removes the part of phone's software used to check for carrier and not replacing critical parts (something like that).
There's a tool:
http://forum.xda-developers.com/showthread.php?t=943726
Try to run it and see what you will get.
Click to expand...
Click to collapse
Thanks in advance, ill try everything when i setup everything properly. Will update on progress! :good:
OK, at fisrt I have removed both SIM and SD cards and then:
1) flashed AlphaRev downgrade to achieve S-ON
2) then run RUU
Inserted only SIM card, and for now without reboots - but this was only 15 mins ago, so ill keep informing about case after testing, in hope not to get another reboot ever.
What I realised is thatr I dont have recovery?
Is this supposed to be? And how will I resolve problem If something unwanted occur?
Thanks a lot for Your help!
goxyendzy said:
OK, at fisrt I have removed both SIM and SD cards and then:
1) flashed AlphaRev downgrade to achieve S-ON
2) then run RUU
Inserted only SIM card, and for now without reboots - but this was only 15 mins ago, so ill keep informing about case after testing, in hope not to get another reboot ever.
What I realised is thatr I dont have recovery?
Is this supposed to be? And how will I resolve problem If something unwanted occur?
Thanks a lot for Your help!
Click to expand...
Click to collapse
You have recovery, but it is stock one (pretty different to custom ones ).
Now after you flashed 2.3 RUU you probably have 1.02 hboot, so go here:
revolutionary.io
Download the tool and follow the process described to achieve s-off and root again (the problem you have have nothing connected with s-off and root but probably with some parts of system software which might be recovered now). During the process you will flash Clockworkmod recovery, from which you will install Superuser.apk. After that reboot the phone and go here:
4ext.net
Download Recovery updater, install it to your phone and flash 4ext recovery. Than from recovery you can restore backup you have from your old rom, but my suggestion is to go here:
http://forum.xda-developers.com/showthread.php?t=809328
and find something for you, cause I think that you have to start from scratch to have a proper software (cause you already had problems with previous one).
If you're up to Oxygen again go here:
http://download.oxygen.im/roms/
but I think that there are a few roms on previous link that are based on Oxygen, but a little bit modified with some extra options.
Well, thanks really, but for now I would like to live things as they are...
I dont mind beeng S-ON and not rooted, if phone doesnt reboot again. I just need it functioning, without advanced options.
Are U suggesting that STOCK ROM is not the way I should go?
goxyendzy said:
Well, thanks really, but for now I would like to live things as they are...
I dont mind beeng S-ON and not rooted, if phone doesnt reboot again. I just need it functioning, without advanced options.
Are U suggesting that STOCK ROM is not the way I should go?
Click to expand...
Click to collapse
It's the way I went for a long time until I started experimenting, mostly because a lack of space. After that I found the thread I posted (All things desire) and wanted to try some advanced roms (Sense 3.0, 3.5) even made some stuff on my own on that way.
http://forum.xda-developers.com/showthread.php?p=23101063#post23101063
My opinion is that stock roms are the best solution foe our device, cause it runs smoothest and I think that Sense is something that brings HTC devices above all other android devices. I've never been a fan of AOSP software but I tried it, just to see how it feels. I even used MIUI rom for some time as the first software option.
Anyway, the story with memory problem stays, but the main point for getting s-off and root again are diagnostic and flashing options cause on s-off device you can flash all crucial partitions that can cause problems (hboot and radio-see attachment) and change partition table layout to gain space (see alpharev.nl)
I hope I helped!
nlooooo said:
It's the way I went for a long time until I started experimenting, mostly because a lack of space. After that I found the thread I posted (All things desire) and wanted to try some advanced roms (Sense 3.0, 3.5) even made some stuff on my own on that way.
http://forum.xda-developers.com/showthread.php?p=23101063#post23101063
My opinion is that stock roms are the best solution foe our device, cause it runs smoothest and I think that Sense is something that brings HTC devices above all other android devices. I've never been a fan of AOSP software but I tried it, just to see how it feels. I even used MIUI rom for some time as the first software option.
Anyway, the story with memory problem stays, but the main point for getting s-off and root again are diagnostic and flashing options cause on s-off device you can flash all crucial partitions that can cause problems (hboot and radio-see attachment) and change partition table layout to gain space (see alpharev.nl)
I hope I helped!
Click to expand...
Click to collapse
Since there are no reboots yet (I really hope its in past) U have been more than helpful! :good:
I still havent inserted sd card, and been consedering of getting a new one (with higher speed).
Also, as I see that U R my countryman (ko ce kome ako ne svoj svome), U have earned a few drinks when U come to my town!
I will be updating how things are regarding of this case.
Cheers :highfive:
goxyendzy said:
Since there are no reboots yet (I really hope its in past) U have been more than helpful! :good:
I still havent inserted sd card, and been consedering of getting a new one (with higher speed).
Also, as I see that U R my countryman (ko ce kome ako ne svoj svome), U have earned a few drinks when U come to my town!
I will be updating how things are regarding of this case.
Cheers :highfive:
Click to expand...
Click to collapse
No problem, I'm holding you for your word!
If you have no reboots try to insert different carriers sim cards and see if it's still unlocked.
reboots again
nlooooo said:
No problem, I'm holding you for your word!
If you have no reboots try to insert different carriers sim cards and see if it's still unlocked.
Click to expand...
Click to collapse
Reboots again...
After half a day of normal usage, I tried inserting another SIM (but from same carrier) and it started again...
Not so often but from time to time it reboots.
So I guess, at the end it seems it is hardware fault.
One strange thing thou (and it makes me wonder): When I try removing account it says I should do Factory Reset if I want to change that basic acc. But afrer performing Factory Reset NOTHING happens? Account is still there, along with other settings and/or installed apps.
Any ideas?
Invitation still holds

Categories

Resources