Related
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
I have noticed for most of his roms that he has been stating in the OP that you must partition your SD card. Is that really necessary, I am quite happy with how the latest CyanogenMod since it is working for me, but would like to try out his newest Kingdom rom due to it being Sense 3.0. So my questionis:
Would it be ok for me to just do factory reset, wipe cache, and wipe dalvik and then flashing his rom along with the pri downgrade and stock kernal?
DNarsingh said:
I have noticed for most of his roms that he has been stating in the OP that you must partition your SD card. Is that really necessary, I am quite happy with how the latest CyanogenMod since it is working for me, but would like to try out his newest Kingdom rom due to it being Sense 3.0. So my questionis:
Would it be ok for me to just do factory reset, wipe cache, and wipe dalvik and then flashing his rom along with the pri downgrade and stock kernal?
Click to expand...
Click to collapse
I know that you can do that, however, you partition your SD Card so that it can store ROM cache and application cache without taking up your internal memory. These new 3.0 ROMs are extremely large and take up a lot of internal storage on your phone. So if you don't partition your SD you will be out of memory on your phone really fast. Hope that helps and answers your question.
drgonzo712 said:
I know that you can do that, however, you partition your SD Card so that it can store ROM cache and application cache without taking up your internal memory. These new 3.0 ROMs are extremely large and take up a lot of internal storage on your phone. So if you don't partition your SD you will be out of memory on your phone really fast. Hope that helps and answers your question.
Click to expand...
Click to collapse
Yes that does help, thanks. Also, you wouldn't by any chance know if we have to use that stock kernal, do you? Are other kernals compatible? I have seen that some people are using the Tiamat one, but I would like to use the latest Savage Zen if its possible.
You don't need to flash the stock kernel fyi. It's already baked in. He put it there to d/l in case you try an alternate kernel and don't like the results, you can always flash back to stock kernel. Most alternate kernels Bork the camera and our video capability. I have only stuck with the stock kernels, i have no suggestions on alternates.
Sent from my Infected EVO using XDA Premium App.
DNarsingh said:
Yes that does help, thanks. Also, you wouldn't by any chance know if we have to use that stock kernal, do you? Are other kernals compatible? I have seen that some people are using the Tiamat one, but I would like to use the latest Savage Zen if its possible.
Click to expand...
Click to collapse
As far as I know, none of the alternative Kernels work 100% since the devs don't have the actual release to rip apart. Most of the kernels were built for Froyo and can run on Gingerbread and Sense 3.0, but like KB112 said it will bork the cam.
I came from CM7 as well, I loved it but I missed sense, this kingdom rom virus is working on is really nice, unless you are a sense hater I recommend trying it. I would also just go ahead and partition your sd card, roms and just getting bigger and bigger and htc still havent figured out that we always need more system space then they give us.
it is not required, but it will give you a lot more space to install your apps from the market
Ok thanks guys, now I guess I just need to get my new card and then I will partition it
Sense 3.0 Roms...cant get past White HTC EVO 4g screen
I have been having a MAJOR problem flashing any of Viruses Sense 3.0 roms. I've tried A0.1 and A0.2. I have partitioned the SD card (2GB on ext3, the SD card is the one the phone came with), wiped, wiped, and wiped again. The rom installs on the phone fine, but when I try to flash it, it never goes past the white HTC EVO 4G screen. The white screen stays on for about 20 seconds, goes off, then comes back on again, and this cycle happens over and over again. I've let the phone sit for up to 15 minutes at a time, but it never goes past the white screen. I've never seen the rom's splash screen. Multiple battery pulls and restarts haven't helped. I can't figure out what is going on. If anyone can point me in the right direction, I would appreciate it. I tried flashing the DoubleShot rom, same results. Thanks in advance.
scorpio1107 said:
I have been having a MAJOR problem flashing any of Viruses Sense 3.0 roms. I've tried A0.1 and A0.2. I have partitioned the SD card (2GB on ext3, the SD card is the one the phone came with), wiped, wiped, and wiped again. The rom installs on the phone fine, but when I try to flash it, it never goes past the white HTC EVO 4G screen. The white screen stays on for about 20 seconds, goes off, then comes back on again, and this cycle happens over and over again. I've let the phone sit for up to 15 minutes at a time, but it never goes past the white screen. I've never seen the rom's splash screen. Multiple battery pulls and restarts haven't helped. I can't figure out what is going on. If anyone can point me in the right direction, I would appreciate it. I tried flashing the DoubleShot rom, same results. Thanks in advance.
Click to expand...
Click to collapse
Not sure of your issues as it both had worked well for me. (though I am back on gingersense b4 until a bit later tonight) You may want to do a bit of reading in the roms thread.
As a side note though the original card is only class 2 (read quite slow) and therefore will not be of much use to run data or apps from anyway. 16gb class 10 cards can be gotten on amazon for about 25 - 30 bones. (maybe cheaper)
Thanks for the response. I was wondering if the SD card was the problem. I will look into getting another one. Just curious to see if anyone else had any ideas.
can anyone help?
i had troubles flashing last night. mine would actually hang on the white evo 4g screen and not go any further. i would pull the battery and reflash and it would work.i must have flashed about 6 or 7 times trying to get everything in order. finally got all the icons to show up and seemed to work right except the weather would crash and the gallery would just show a white screen, never partitioned the sd card though. so now i am loading all my stuff back to the sd card after a partition. there was two parts to the partition, first size i put was 1 gig and the second size it asked for i put 512k. i don't know what each one is for but what do i do after i finish transfering everything back on. just flash as normal? do i actually see the extra partition and put something in it?
from what i saw last night this sense 3.0 is true eye candy. you can't get enough of it. it looks really sexy!
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!
Hi!
For te past couple of days i have massive problems with my desire. SOme quirkiness had begun to show up before, but nothing on this scale. It all started on thursday when my battery died and when i came home and plugged the phone in, it came into a constant bootloop. At first i tried everything i did in a simmilar case of a bootloop - took the SD Card out, run check for errors on both partitions (i have an ext partition, yeah), run fix permissions from clockworkmod, make a nandroid backup and restore the ext image, everything that used to help. It didn't now.
So i gave up and made a fresh install of the Nikez JB ROM. I have a weird quirk with Nikez JB ROMs that freezes the phone, if i open Chrome from it's shortcut in the dock/launcher (opening links from GMail for example works okay). So it froze, and reboots (it reboots after ~10 seconds). And there came another bootloop. When i came home again, i did another fresh install. All was well for the friday evening, until i came home lat at night and opened Chrome again. What a mistake. I woke up to the lovely Evervolv boot animation.
Yesterday i installed Sandvold ICS 0.18.2.1, configured everything and went out. When i called a freind, the phone froze again (it was dialing until it dialed out, but the call UI was frozen). After pulling the battery, yep, you guesed it, bootloop. Multiple reboots, with or without SD and SIM card didn't help. I did a fresh install while being out, since i needed to be connectable. And i did another one just 10 minutes ago, only to boot into 'sorry, that and that app closed' errors. Right now it's sitting here with the first use since i reinstalled it AGAIN.
It's worth noting, that i had an 8 GB Class 10 SD card. Which apparently died. I put in the original 4 GB c2 card in yesterday, hoping it would be okay. It clearly wasn't. The 4 gig one worked okay up until now, but 2 months ago i killed a 8 GB c10 after about a year. This one held up for only a month or two. GParted dies when trying to create a partition in the last 1024 MB, so the ext has been affected.
Since the 4 GB is supposed to work, what's left, dead NAND? How can i check that? Do you guys have any suggestions as to what to do, appart from 'get a new phone' (trying to wait till 29th to see, what the Nexus 4 will be like)?
I prolly missed a ton of info, so ask away (i'm in kind of a bad mood since i have a dead phone and i might have a tiny hangover, but it's not bad).
Anyone?
I reinstalled Sandovld's ICS ROM again yesterday, downloaded all the apps, made a nandroid backup and only after that made all the settings. Later, i got two calls, the first went fine, but before ringing at the second one, the phone froze (i heard buzzing in my radio speaker and a friend came over, confirming, it was him). It didn't boot. So i restored the backup, made all the settings again (it worked), went back to CWM recovery, made another backup and that's where the story ends, it doesn't boot anymore. Another format and reinstall probably would help, but it's not actually a solution...
Ideas?
Try a GB rom that doesn't need an ext partition, like CM7. See what happens.
Technically a GB rom, like CM7, also needs an ext partition (CM7 was one of my first custom, non-Sense ROMs, tested exactly because of the ext support) or the ICS doesn't, it's not ROM dependant.
But a GB ROM, maybe even an official version, is definetly on my to-do list, i just don't know when i'll get around to it.
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