Related
Ever since I flashed LeeDroid 1.8b, I've been having this odd problem. I've wiped the phone since and have flashed Open Desire 3.1.0 and I love it but I'm terrified to reboot my phone.
The phone will boot and freeze at the HTC white screen. This happens even if I try to boot into Recovery, (I can hold down vol+down and power button) but as soon as I select Recovery, it will freeze there at the HTC screen.
The only solution I have is to pull the battery and try again. It will do it around 2 - 3 times before it finally boots into Clockwork Recovery Mod SLCD or boot into Open Desire if I don't boot into recovery. This is the same if I decide to REBOOT the phone or power down and boot up.
This problem never happened when I originally flashed Cyanogen. I'm thinking there's still some files or something left that causes this freezing.. I also did a wipe and delete cache before flashing a new rom.
Does anyone else have this problem or help me sort it out?
Edit: Ah shoot.. wrong forum My bad..
no one?
Although Lee newer acknowledged it, I think it has to do with his ROM. I experienced the same issue while running 1.8b, with 1.8c I haven't rebooted by now, but still I have experienced this only after switching to his ROM and I noticed I am not alone on the ROM thread (other people are complaining too about getting stuck at the bootscreen).
I have changed many ROMs (generic 2.1, generic 2.2, pays, adamg ROM...) and never had such an issue, that is why I think it has to do something with lee's ROM.
If you have OpenDesire I would suggest to reboot it just to see how it will go.
Thanks for your response man! The problem is that I've wiped and everything and flashed Open Desire and I'm still experiencing the issue. Is there another way I can completely delete/format any traces of any previous ROM? I believe there's still some sort of remnants of his files left that are causing this!
THanks,
JD
A full wipe can never hurt.
As for freezing at the HTC screen when trying to boot into recovery, I experience this too. What I have found is that if I press no buttons after booting into HBOOT, until HBOOT has tried to load from the SDCard, and THEN selecting Recovery, Recovery boots every time.
However, if I push a button before HBOOT has loaded from the SDCard, I will freeze on the HTC screen regularly.
TheLastOne said:
A full wipe can never hurt.
As for freezing at the HTC screen when trying to boot into recovery, I experience this too. What I have found is that if I press no buttons after booting into HBOOT, until HBOOT has tried to load from the SDCard, and THEN selecting Recovery, Recovery boots every time.
However, if I push a button before HBOOT has loaded from the SDCard, I will freeze on the HTC screen regularly.
Click to expand...
Click to collapse
I will definitely try that.. do you ever have problems booting though? I freeze on the HTC screen during boot up as well and have to do 2 - 3 battery pulls before it finally decides to boot!
I do not, but hopefully a full wipe (data, cache, dalvik, etc) will solve that. Have you tried wiping everything?
I have, but the only wipe I perform is the one in the Clockwork Recovery. Also deleted the cache, but never have deleted or wiped dalvik cache?
I will try this later today and see what happens.. thanks!
TheLastOne said:
I do not, but hopefully a full wipe (data, cache, dalvik, etc) will solve that. Have you tried wiping everything?
Click to expand...
Click to collapse
Just sayin' I've not ever had a boot problem like this with LeeDrOiD. Running 1.8c at the moment.
Ditto.. No issues, its not a rom issue, you may have bad blocks on your nand.
Sent from my HTC Desire using XDA App
Tawm said:
Just sayin' I've not ever had a boot problem like this with LeeDrOiD. Running 1.8c at the moment.
Click to expand...
Click to collapse
I believe it was an issue with 1.8b..
LeeDroid said:
Ditto.. No issues, its not a rom issue, you may have bad blocks on your nand.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Hmm.. anyway to confirm this? It's a brand new device, barely two weeks old and never had this issue until I flashed 1.8b.. I'm going to try to wipe it completely and go from there, hopefully that solves the issue.
What's a nand?
Hi Quazis,
I have had a very similar problem with my Telstra desire after rooting and installing a Lee based rom called NexTSense. After that I installed Open Desire and experienced the same problems.
I am just now re-rooting my phone and going to install Pinky.
Just out of interest are you running on the 850mhz Rogers network? If so have you updated to the latest radios (5.09.20 I think?)? Telstra runs off this frequency also and I think it may have something to do with incompatible radios. -- Can anyone confirm this?
If this is the case maybe try Open Desire without updating the radios?
Hey,
We got the A8182 version of the Desire which has 850/1900 (I believe), so both bands that run on 3G.
Before I flashed LeeDroid, I had updated the radio (.20) and was on Cyanogen nightly build. I had no booting problems with that ROM, but I wanted something a little more stable. I modded it as well and the phone booted up no problem, also into recovery.
Once I flashed LeeDroid, that's when my problems arose. I only wiped/formated data and the cache.. I never formated that dalvik cache. I will wait until Open Desire 3.2.0 releases today and try that a full wipe/format.
Another member said he doesn't touch anything on the phone when he boots into recovery until the phone does the SD card check.. I tried it once and it went into recovery with no issues so maybe pressing buttons before the SD check does something??
I don't, but I did a full flash, and used my separate test sd card.
plasmafire said:
I don't, but I did a full flash, and used my separate test sd card.
Click to expand...
Click to collapse
I'm going to do this.. thankfully I have't customized my phone a lot so I'm going to format both the FAT32 and EXT3 partitions and full wipe.. to do a full wipe.. there's only data/factory, cache, davlik cache and battery stats correct? If I wipe those 4 items in Clockwork, that's considered a full wipe?
JD
Full flash wont help. I know because I did it.
I am to lazy from installing different ROMs, resetting my device, etc... so I will leave it as it is for now (LeeDroid 1.8c), and will try to reboot it as rare as possible (bootscreen takes a while, bootloop is possible too). But when I'll have some more time I will re-root and install another ROM and I am sure the issue will be gone.
Lee, nothing personal (in the end, I am using your ROM right now) but I think you should read more carefully the thread about LeeDroid. You will see many people get stuck at the booscreen and/or their devices keep rebooting with this ROM.
I don't have this issue with the same ROM as you.
-----------------------------------
- Sent via my HTC Desire -
Yes, not everyone has that problem (in that case we wouldn't need to talk about it - we would KNOW it). Just some people have this issue with that ROM. I would say 5% of the people have the bootloop problem, and 10% of the people have longer-than-average the bootscreen.
Still, it worths taking a look since 3-4 people from 10 participants on this thread say they have this problem with -this- ROM.
My 2 cents.
ljesh said:
Full flash wont help. I know because I did it.
I am to lazy from installing different ROMs, resetting my device, etc... so I will leave it as it is for now (LeeDroid 1.8c), and will try to reboot it as rare as possible (bootscreen takes a while, bootloop is possible too). But when I'll have some more time I will re-root and install another ROM and I am sure the issue will be gone.
Lee, nothing personal (in the end, I am using your ROM right now) but I think you should read more carefully the thread about LeeDroid. You will see many people get stuck at the booscreen and/or their devices keep rebooting with this ROM.
Click to expand...
Click to collapse
Why won't a full flash help? I don't have LeeDroid anymore, I had it for about 10 minutes because I didn't like it. I've since gone to Open Desire and the issue still persisted.. but it never happened when I had Cyanogen installed.
I'm scared to re-root because it requires a reboot and sometimes the HTC screen never goes away.. lol
hey there, its intresting to see that you have the same problem as me,
http://forum.xda-developers.com/showthread.php?t=755835&highlight=Recovery+Issue
the people who are saying they dont have a problem, i'd like to know what recovery you are using?
and what hboot you orignally came from, i.e. do you have a SLCD screen? and how did you root?
because it is now becoming obvious that leedroid rom is causing this issue as a lot of people are having problems.
during the weekend i will try flash the RUU for WWE with the hboot 0.83 included (using gold card)
and start from scratch and flash another.
no disprespect to the developer of leedroid, his work is good. just a lot of people on hboot 0.83 with the SLCD screen have issues.
I'm sorry that this thread is here again, still unsolved.
But I would really want to use my phone again. I've got nothing ATM.
What I've tried already:
- Every radio version wich can be downloaded for the Kaiser
- 2.6.32 and 2.6.25 Kernel - Latest 2.6.32 kernel with reboot fixes from Clamsyn
- Diffrent Android Builds like 'Fat Free Froyo', 'Not So Super Froyo', 'CM6.1 Gingerbread', 'Clemsyn's Final Froyo' and so on.
- Wi-Fi fixes
- Re-re-re-re-re-installing Android
- Re-re-re-re-re-flashing kernels and radios
The problem explained:
When using any radio/kernel/build my phone reboots every time my Wi-Fi is on.
At first when Android is freshly installed there are no problems at ass when using Wi-Fi, but after a while it starts to reboot as long as the Wi-Fi is on.
The Wi-Fi is on, I've got about 1 à 2 minutes before the phone reboots. After the reboot, the Wi-Fi restores his state from before the reboot. Now i've got about 30 seconds before it reboots again to turn off the Wi-Fi
VIDEO (CHEAP QUALITY):
http://www.youtube.com/watch?v=AlZMqB1evUE
If there's any more info on my mind I'll post it.
Hope someone's got a fix or solution for this.
Thanks
I had a similar problem, with WIFI and DATA connection, that I solved with:
this kernel http://forum.xda-developers.com/showpost.php?p=9768617&postcount=63
ROM: Scoot CyanogenMod 6.1 RLS5a
radio: 1.65.16.25
I suggest data on SD card partition for extra stability.
Millence said:
I had a similar problem, with WIFI and DATA connection, that I solved with:
this kernel http://forum.xda-developers.com/showpost.php?p=9768617&postcount=63
ROM: Scoot CyanogenMod 6.1 RLS5a
radio: 1.65.16.25
I suggest data on SD card partition for extra stability.
Click to expand...
Click to collapse
Thanks
I'll try that and let something know...
I can't seem to find out how to get the data on sdcardpartition...
i'm getting:
Could not determine filesystem size
Failed
Failed to format
blablabla
unmount: can't unmount /data: invalid argument
EDIT: Could be that i did the partition thing wrong. Trying another way ATM
EDIT: Nope doesn't work...
meh i suck
Install everything on NAND just to see if this combination works for you.
It takes a while until it starts to reboot.
Installing right now so... hoping...
Thanks a lot for even taking your time to help me
When this doesn't fix the problem I'm going to upload a small vid showing what it does. So it's easier to understand the problem. Android booted. Now install some apps and reboot and try to make it reboot again
I had a similar problem in the past.
I solved it with a complete install from the htc factory standard windows mobile rom including the radio. After the complete setup and the reboot after the setup you can try to install another radio and the android kernel and rom again.
This solved my problem. And I use the latest 1.71.09.01 radio and I have no problems with it.
Maybe this helps you.
mt1976 said:
I had a similar problem in the past.
I solved it with a complete install from the htc factory standard windows mobile rom including the radio. After the complete setup and the reboot after the setup you can try to install another radio and the android kernel and rom again.
This solved my problem. And I use the latest 1.71.09.01 radio and I have no problems with it.
Maybe this helps you.
Click to expand...
Click to collapse
I'ma try that as well. The problem now is: I have 0.00kb total memory and 0.00kb free so... can't install anything
wich radio?
EDIT: or does it come with the rom downloaded from htc website?
What's this thing I keep getting? Like I said in the previous posts, with the Failed, Failed to format
Never had that before lol'd :/
Still no luck. Keeps rebooting :/
Any other ideas???
If you have hard spl installed, then the installation ist really easy. Open the offical "Kaiser_HTC_ASIA_HK_WWE_3.34.721.2.exe" with 7zip and extract the RUU_signed.nbh to the root of your sd card. Then rename it in KAISIMG.nbh.
Manual for flashing:
http://forum.xda-developers.com/showthread.php?t=433835
---> Flashing Via MicroSD Card
Try it. And I think that you have to make the complete htc first setup process with reboot. My problems were gone after I made this complete setup with the standard htc rom. After that my kaiser was working well. So I installed another radio, kernel and android rom and all was working well after this.
Nope sorry, Tried that yesterday, Still rebooting.
I'm going to post a video wich shows it. Crappy Quality. Shot with my Nokia 3500c so... kind of... yeah...
Video will be posted in a couple of minutes
Uploaded
For anyone interested.
Hope this ever gets fixed
http://www.youtube.com/user/Syntax1993?feature=mhum
syntax1993 said:
Uploaded
For anyone interested.
Hope this ever gets fixed
http://www.youtube.com/user/Syntax1993?feature=mhum
Click to expand...
Click to collapse
Did you use BusyBox update that is in the particular thread? I found out, that it fu*ks up everything... messes the keyboard, breaks stability...
I am not using it anymore. Instead I put my apps to the androidinstall.tar file to avoid using newly installed app and it seems to be quite stable for me...
Nope no busybox used :s really ****ed up problem
srry for the language
i did have various probs with sd cards not recognised and failed to format on install.
even trying full format on win 7 and xp didnt help.
i used an sd formater from http://www.sdcard.org/consumers/formatter_3/ and select Full Erase On Format size adjustment on.
then, as if by magic ;-) , android installed. worth a try?
Trying that right now...
Thank you btw
If that works I just need to fix the Wi-Fi problem :s
I'm having real trouble with installing these roms.(insertcoin 1.0.8 and rcmixS V2.0)
What I've done so far.
Rooted with unrevoked.
Created ext3 partition using gParted.
Successfully installed rom to working.
To get it working, I have to revert to my stock backup and then copy over the top of the data etc.
Problems once working:
1) Mail app refuses to connect to active sync server and pull down mail, I've reverted to my stock backup and copied the settings to the letter and it still refuses to connect and get the mail
2) Contacts, HTCContacts will not display my contacts or let me access their cards, however shows their details in call log including FB picture.
I want to wipe everything and do it from scratch, however I get stuck on the wallpaper and notification bar and it won't load the rest of sense so it's completely unusable.
I know my ext3 partition works correctly as I've installed loads of apps etc when i got it working and quick system info registered my partition of 1gb ext3.
Try to clear storage from hboot, and flash the latest radio the last thing worked for me
You mate, are a blooming genious, I've been pulling my hair out wiping it from clockworkmod and it was such a simple fix, thank-you so much.
I can start enjoying my phone again instead of getting frustrated with it to the point i wanted to throw it against a wall
amraving said:
You mate, are a blooming genious, I've been pulling my hair out wiping it from clockworkmod and it was such a simple fix, thank-you so much.
I can start enjoying my phone again instead of getting frustrated with it to the point i wanted to throw it against a wall
Click to expand...
Click to collapse
Which fix worked? Clearing storage or new radio?
Kryten2k35 said:
Which fix worked? Clearing storage or new radio?
Click to expand...
Click to collapse
I think the second one, clearing storage doesn't help maybe in 1 out of 100 cases
latest radio is very important with InsertCoin
But do it before you flash a radio
Atleast i did
amraving said:
You mate, are a blooming genious, I've been pulling my hair out wiping it from clockworkmod and it was such a simple fix, thank-you so much.
I can start enjoying my phone again instead of getting frustrated with it to the point i wanted to throw it against a wall
Click to expand...
Click to collapse
I'm happy for you that you managed to do it, it looks like a simple fix, but it's one of the things that can brick your device easily so be careful when you flash radio's, always charge you battery full if you'll ever have to do it again(not that it will use up all of it just for safety)
Fyi, I used clear storage. I'm still on stock radio and hboot.
Sent from my HTC Desire using XDA App
That might explain why I could never get Insertcoin working properly!
Sent from my HTC Desire using XDA App
Hi,
I ve been through all this forum and the rest of the internet, but I couldnt find the answer ... so hopefully you will help me.
I have Desire Z - about 3 months old.
I ve rooted the phone and flashed to cyanogenmod 7.1 stable. All the time Ive followed guides here or on cyanogen section/wiki. CM has been running stable for a month maybe until today.
This morning I couldnt make a call - so I rebooted phone.
After reboot phone gets to the home screen and automatically reboots itself after 5 seconds.
info from hboot
VISION PVT ENG S-OFF
HBOOT-0.84.2000 (PC1011000)
MICROP-0425
eMMC-boot
OS ver 1.34.707.3
CID 1111111111
Click to expand...
Click to collapse
Ive already tried:
Wipe cache / davik cache
Wipe battery status
Recover to CM - backup created right after first flash - successfully - problem remains
Recover to original ROM - successfully - problem remains
any ideas?
also - if you dont have any advice to fix this problem - Id like to ask you, if you could point me to the best way, how to unroot/(s-on) etc. phone and make it look like its like stocked one for the purpose of waranty. - i dont mind any data nor in phone nor on sdcard, everything I need is synced to gmail acc. Thank you
cyber-mythius said:
Hi,
I ve been through all this forum and the rest of the internet, but I couldnt find the answer ... so hopefully you will help me.
I have Desire Z - about 3 months old.
I ve rooted the phone and flashed to cyanogenmod 7.1 stable. All the time Ive followed guides here or on cyanogen section/wiki. CM has been running stable for a month maybe until today.
This morning I couldnt make a call - so I rebooted phone.
After reboot phone gets to the home screen and automatically reboots itself after 5 seconds.
info from hboot
Ive already tried:
Wipe cache / davik cache
Wipe battery status
Recover to CM - backup created right after first flash - successfully - problem remains
Recover to original ROM - successfully - problem remains
any ideas?
also - if you dont have any advice to fix this problem - Id like to ask you, if you could point me to the best way, how to unroot/(s-on) etc. phone and make it look like its like stocked one for the purpose of waranty. - i dont mind any data nor in phone nor on sdcard, everything I need is synced to gmail acc. Thank you
Click to expand...
Click to collapse
Pull /proc/last_kmsg and see what it says; should help you narrow it down.
Sent from my HTC Vision using XDA App
could you gimme hand how? - the only point where I can get in the phone is to bootloader / recovery.
so i cant run terminal from apps in phone.
+ could anyone help me how to charge up battery with my problem? I have about 20% on both batteries and I dont want to loose them during repair progress.
to the /proc/last_kmsg - i could not find anything like this on sd
cyber-mythius said:
+ could anyone help me how to charge up battery with my problem? I have about 20% on both batteries and I dont want to loose them during repair progress.
to the /proc/last_kmsg - i could not find anything like this on sd
Click to expand...
Click to collapse
Sorry, I just got to work. The last_kmsg is on your device, not the sdcard. If you have ADB set up you should be able to access it by connecting your phone to your computer
Sent from my HTC Vision using XDA App
I have everything installed on the other PC where Ill be on monday. Maybe Ill find some time to look through it tommorow.
Thank you now for pointing me somewhere - Ill add more info when I ll have it.
I had a similar problem after flashing new rom. My Desire Z was also rebooting after a few seconds.
I downloaded 1.34.707.3 firmware(used to downgrade Desire Z from gingerbread) from CM wiki, installed it through fastboot (step 8) , rooted my phone once again following the wiki and since then my phone is working without any problems.
Battery can be charged up while the phone is turned off.
well I flashed phone with the downgrading rom as you mentioned and it helped a little
- phone is running and not restarting after few seconds - but randomly after 5-60 seconds (so I am able to do at least something ))...
On monday I ll root that bi*ch again, pull there CM7 or some other ROM and post here actual status.
Thank you so far
Similar problem
Hi, I have the exact same problem with my Desire Z. I've attached the last_msg if someone could help me with that.. also, my sdcard is not partitioned so could that have anything to do with it? Thanks, hopefully I'll get an answer soon
Resurrecting a bit of an old thread here but I have just experienced these exact symptoms.
A friend gave me his old Desire-Z so of course I immediately set about rooting it and trying some ROMs.
As a start I went with the most recent Cyanogenmod which is 7.2 at this time. Everything was going smoothly and was just getting used to the phone and it's physical keyboard. My biggest worry was that the battery life wouldn't be good enough for me so I was running a test to see how long it would last. I am a very light phone user. With background wifi disabled, gps disabled and the phone set to 2G only it ran for 7days and 3 hours! No problems there even with a well used battery. When it eventually died I hit the power button to wake it and it started booting and then shutdown again as you would expect. However after I had fully charged it it booted no problems but then went into the boot loop described above. It boots successfully to the home screen but then after 10-15 seconds it reboots. Frustrating!
I tried some things:
Clear cache from CWM: No change
Factory reset from CWM: No change
Reflash CM7.2 from CWM: No change
Clear Dalvik Cache from CWM: No change
Clear Battery stats from CWM: No change. I was hopeful this might be the problem as the battery had been unusually flat, perhaps some flag had been set that caused the reboot.
I have now recovered by reflashing the exploitable original image, PC10IMG.zip, and then going back through the rooting process. I wouldn't want to have to do it again though.
Possible explainations for the behaviour: I was running a battery monitor app (GSam Battery Monitor) which runs continuously and has various power related functions. Though I would have thought anything that was doing would have been removed by factory reset or reflashing CM.
During the 7 days I was testing ROM manager prompted me to update it and then to update the version of CWM that I had. This is perhaps more likely as would have survived everything else I tried to recover until I reflashed the original recovery.
Hope that helps someone and if anyone has any insight on this I'd lobe to hear it.
Steve
Looks like I spoke too soon. First time I had to reboot the phone I got stuck in the reboot loop again.
Hmm, really confused now. No idea what can be causing this that isn't solved by reflashing CM7.2 but is by going back to the original rom?
Steve
the only thing, that helped me back then was to flash another ROM ... give it a try.
there is several other ROMs based on CM, I'm pretty sure, that you'll find one, that will suit you best.
Thanks for the reply I appreciate you taking the time.
It's very odd I can't think what might be causing this. I ran CM7.2 with zero issues for a week. Then first time I had to reboot it gets stuck in the loop.
Since I was away from home I could not get into recovery. I could get into HBoot (by holing Vol. Down + Power) but because I had a PC10IMG.zip file on my sdcard it would just go straight in to asking if I wanted to update from that with no way to select recovery. And of course I needed to have the sdcard in the phone to get an image from it!
So I have been running from the exploitable 2.2 Rom from the rooting procedure since. That can reboot no problems.
Today I tried a much more recent CM10.1 based rom - stuck in boot loop.
Then a tried the Rooted G2 stock ROM which is obviously much older. It booted correctly one time. Then I rebooted it (actually shutdown and then turned on, it doesn't have a reboot option) and now I'm stuck in the reboot loop.
I'm doing a factory reset and clearing the Dalvik cache after flashing each ROM.
I have also tried booting without the sdcard or SIM card, no change.
Something I have observed is that the phone will reboot once after flashing with every ROM, even the original ROM, but then either runs correctly or continuously reboots.
I can only think that possibly I have wrong phone model. I know that the previous owner bought this contract free so it may be some import. Perhaps it's actually a G2 and I'm using the wrong HBoot? I think that's unlikely as it would show an error during the rooting process.
Steve
I doubt you have the wrong hboot, it wouldn't even start if you did. I would do a complete wipe and format maybe change firmware as well. Backup SD and reformat that as well. If you have true radio soff (rooted via gfree) then you are safe to use one of the pc10img.zips I created here
http://forum.xda-developers.com/showthread.php?p=27796375 (see post 30)
Make sure to remove it from SD this time or at least change the name when done
This will give you new engineering hboot, updated 4ext recovery, .19 radio but all can be changed to whatever if you want.
After the flash reformat all in recovery and flash a new rom
Sent from my Nexus 7 using xda premium
Thanks for your input.
Updating the radio rom does seem tempting if potentially dangerous! The claimed power saving especially. I haven't ever used 4ext recovery but given how CWM seems to be failing me I might give it a try.
I don't wan to speak too soon here (but doing so anyway!) it looks like I may have corrected the problems by using SuperWipeG2+ from here: http://forum.xda-developers.com/showthread.php?t=1044992
After running that, which can easily be done from CWM, the phone booted first time with no reboots.
I'll update this if that did not fix it.
Steve
Yep spoke too soon!
However I have found a way to reliably recover but it's not straight forward.
Boot to recovery. Run SuperWipeG2+.
Attempt to boot the phone, boot fails as there is no ROM installed. This step seems important.
Boot to recovery. Install ROM from zip and Gapps from zip.
Reboot and phone will boot successfully and stay booted!
I then have to recover all my contacts and apps from Google which takes a further 20/25 mins.
Having done that I still cannot reboot the phone. If I reboot (or shutdown and power on) it is then stuck ion the boot loop and I have to do that all over again!
This means I cannot ever allow the phone to go flat.
Aaarrgh!
Any suggestions? It has been suggested that installing another ROM could fix this. Any specific ROM? Any idea why that would work?
I have found that the light sensor doesn't seem to be working and the suggested fix for that is to install a Sense based ROM and then switch back. I can't see how that could work either.
Steve
Yeah I've heard the sense ROM thing works, I don't see how but people seem to swear by it. I would suggest you change all your firmware, new hboot, new radio, new recovery and what not a new ROM. There are lots of good ROMs to choose from so I wouldn't know what to recommend for you, personally I almost always use gingerbread based ones
Sent from my Nexus 7 using xda premium
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