Related
My phone is mullered :-(
Whenever I flash a new ROM, all I get is a constant boot loop on first boot.
Flashing a different ROM results in the same behaviour.
The only way out of it is to re-root, taking me back to version 1.15 or something, and then if i try to flash a new ROM - you guessed it, boot loop....
This first started when I had OpenDesire installed, which was fine to begin with, but then it randomly rebooted and started boot looping.
Since then I've tried about 4 or 5 different ROMs and nothing changes.
Any ideas as to what's wrong/a solution?
Just to add, I have one the lastest radios (.08) when I try and flash.
Perhaps flashing the radio after might help?
After much struggling, I've managed to sort it.
Ended up clearing storage in recovery, which helped so long as there was no SD card in it. Had to format and repartition the card, and fingers crossed, all seems well now.
Whenever you change between diferent ROMs it is a good practice to do a full wipe via recovery. 90 to 99% of the boot-loops can be fixed doing it...
The strange thing is that I did wipe between ROMs. I'm not sure why I had a problem this time round, as I haven't had with the previous 10 flashes...
Still, it's sorted now
Funny.. found this thread via google.
I'm having the exact same issue where no matter what rom I flash it gets stuck on bootloops during the startup animation and never makes it into the rom.
NANDroid backups are perfectly fine to restore, just unable to flash any new roms. Spent all last night trying everything from swapping recoveries, to re-rooting, flashing multiple roms, urgh.
Only thing I didn't try is re-formatting the SD card so gonna give that a go now (thanks to this thread) and report back later.
Annoying to say the least.
Well what do you know... a 'partition my SD card' through rom manager (after copying said contents to my computer) worked a charm.
Most interesting......... Praise this thread and any others that gain help from it.
Did you update your radio ?
Sent from my spectrum zx
Man i'm lucky. Two hugely annoying problems in one go.
First up, yes I have replaced my radio, many times The SD card was obviously not too happy with its ext partition, so repartitioning that worked.
I also had another issue crop up straight away that was probably caused by unhappy sdcard, where when restoring apps via titanium backup, phone would reset.
After running a RRU, re-rooting, all the full works.. I find that some of the apk backups are 1kb... Which is not normal. There were about 15 apps like this. I had a backup of these apps from a week or so ago and copied those to the titanium backup directory, restored, no problemo.
Even more annoyingly TB has a verrify backups option which reported all was well. FML.
Well that was a fun morning. Time to finally get back on track *sighface*
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
So yea...as much as I know my desire's motherboard needs replacement...And I dont have warranty. Is there any way to fix it without changeing whole motherboard?
You provide us no information at all about what's wrong with your device.
What do you want to do with it? Solder stuff?
There is a 100% chance that you will destroy your phone when you open it and mess around with the subminiaturized highly vulnerable microelectronics.
There's something called insurance.
Swyped...
hypophysis said:
You provide us no information at all about what's wrong with your device.
What do you want to do with it? Solder stuff?
There is a 100% chance that you will destroy your phone when you open it and mess around with the subminiaturized highly vulnerable microelectronics.
Click to expand...
Click to collapse
It restarts,boot loop i think it's called. So I cant afford new motherboard so could I take my phone to some1 that knows what he's doing and could he fix it?
LordRyver said:
It restarts,boot loop i think it's called. So I cant afford new motherboard so could I take my phone to some1 that knows what he's doing and could he fix it?
Click to expand...
Click to collapse
Maybe the forum can help you
For this we need some more information:
1. Do you have the original HTC Sense ROM?
1a. If YES skip the points 2 - 5 and continue with 6.
2. If NO: which ROM you have installed?
3. Did you change the Radio ROM?
4. Have you unrooted your phone?
5. Are you S-Off / changed Hboot (partition table)
6. Do you use the original SD-Card?
7. Since your reboots started: have you installed any software just before?
8. Which program(s)
If you can answer these question we can help you - I don't think (hope) your motherboard is dead. Often there are simple solution to fix a "dead" phone
MonacoHias said:
Maybe the forum can help you
For this we need some more information:
1. Do you have the original HTC Sense ROM?
1a. If YES skip the points 2 - 5 and continue with 6.
2. If NO: which ROM you have installed?
3. Did you change the Radio ROM?
4. Have you unrooted your phone?
5. Are you S-Off / changed Hboot (partition table)
6. Do you use the original SD-Card?
7. Since your reboots started: have you installed any software just before?
8. Which program(s)
If you can answer these question we can help you - I don't think (hope) your motherboard is dead. Often there are simple solution to fix a "dead" phone
Click to expand...
Click to collapse
1. I had,but it used to turn off and get into boot loop while playing games like GRave defense. Never happened while playing shoot bubbules.
2. DevNull. First was dev,then leedroid,now back to dev. I keep him in sd card in case my phone wont turn on. Sometimes it restarts in middle of movie so I left him 2 times until morning and it first time turned on and second time didnt,again started to restart. Same with reflashing roms. Sometimes helps,sometimes no.
3.Yes.Radio_32.56.00.32U_5.17.05.08
4.Yes. I had hboot 0.83 or 0.93 and I used AlpharevX and then unrevoked.
5.Yes.
6.I dont know, I got it when I bought phone. (it was used when I bought it.)
7.Hm......Well...I dont think so...when I bought it, I turned phone off and after um... about 1 h I tryed turn it on and it started restarting. Then after some time turened on again.
And btw now it sometimes starts restarting not even hot.
So your problem is random reboots? or does your device not start up at all?
If the problem is just a bootloop, you won't need to replace the motherboard. You just need to flash the correct and working software.
mortenmhp said:
So your problem is random reboots? or does your device not start up at all?
If the problem is just a bootloop, you won't need to replace the motherboard. You just need to flash the correct and working software.
Click to expand...
Click to collapse
But that used to happened with original rom too...un...one guy said that bootloop is because motherboard is faulty. Now I just watched whole movie. And it was ok. But I tink if I would use market or opera it would restart. But im not sure. Sometimes it dosnt restart. And if I would flash all correct software my phone would turn on quicker?
oh god...
Don't answer my question with the word but. It's NOT an answer. So lets take the question again and this time do only reply to the question:
Is you problem random reboots or a bootloop?
Those 2 are NOT the same, while random reboots is exactly what the name implies a bootloop implies that your phone is unable to enter the android system due to a failure on startup.
So please in order for anyone to help you, you must make it very clear what you problem is, as otherwise we cannot tell you what to do.
Everything you have told up until now is that you have some problem(you use bootloop and random reboot equally) and that you might or might not know that it happens when running some specific apps.
mortenmhp said:
oh god...
Don't answer my question with the word but. It's NOT an answer. So lets take the question again and this time do only reply to the question:
Is you problem random reboots or a bootloop?
Those 2 are NOT the same, while random reboots is exactly what the name implies a bootloop implies that your phone is unable to enter the android system due to a failure on startup.
So please in order for anyone to help you, you must make it very clear what you problem is, as otherwise we cannot tell you what to do.
Everything you have told up until now is that you have some problem(you use bootloop and random reboot equally) and that you might or might not know that it happens when running some specific apps.
Click to expand...
Click to collapse
Sorry. By bootloop I mean my phone restarts and then just starts viberating and just stays in white htc logo screen. But after some time I can enter android system. This happanes when I do something with my phone.
If I may throw 2 cents in...
I do not know if this will be the fix for you, but if I had this issue, the first thing I would do is boot the phone up and wait until it loads properly (I gather it loads sometimes but not others, which is why you watched a movie??), make a Titanium backup of everything, then Nandroid backup.
Next, do full wipe
1 Factory reset
2 (in Mounts/Storage) Format Dalvic/data/sdext/system
3 (in Advanced) Wipe Dalvic cache.
Now reflash your ROM and restore Titanium.
Might all sound like basic stuff, but any time I have had issues with bootloops or FCs or whatever, it's usually because I didn't wipe properly. Now I always wipe everything with new ROMs and never have an issue.
If this doesn't help, you may commence panicking I'M KIDDING!!
777ace said:
If I may throw 2 cents in...
I do not know if this will be the fix for you, but if I had this issue, the first thing I would do is boot the phone up and wait until it loads properly (I gather it loads sometimes but not others, which is why you watched a movie??), make a Titanium backup of everything, then Nandroid backup.
Next, do full wipe
1 Factory reset
2 (in Mounts/Storage) Format Dalvic/data/sdext/system
3 (in Advanced) Wipe Dalvic cache.
Now reflash your ROM and restore Titanium.
Might all sound like basic stuff, but any time I have had issues with bootloops or FCs or whatever, it's usually because I didn't wipe properly. Now I always wipe everything with new ROMs and never have an issue.
If this doesn't help, you may commence panicking I'M KIDDING!!
Click to expand...
Click to collapse
Did that already...first time all was the same,but now looks kinnda better. If it wont go to restarting screen while chagring i'll be happy...After doing factory reset it started to move things from pc to sd very slowly.
777ace said:
If I may throw 2 cents in...
I do not know if this will be the fix for you, but if I had this issue, the first thing I would do is boot the phone up and wait until it loads properly (I gather it loads sometimes but not others, which is why you watched a movie??), make a Titanium backup of everything, then Nandroid backup.
Next, do full wipe
1 Factory reset
2 (in Mounts/Storage) Format Dalvic/data/sdext/system
3 (in Advanced) Wipe Dalvic cache.
Now reflash your ROM and restore Titanium.
Might all sound like basic stuff, but any time I have had issues with bootloops or FCs or whatever, it's usually because I didn't wipe properly. Now I always wipe everything with new ROMs and never have an issue.
If this doesn't help, you may commence panicking I'M KIDDING!!
Click to expand...
Click to collapse
Hello LordRyve,
follow the great description from 777ace , these are the steps which should bring your Desire back.
I only would not restore all the programs via Titanium Backup after your fresh install. The reason is that there might be a "bad" program you have installed before. Just restore a program, check if system runs without problems, then restore the next and so on.
But NEVER restore system apps via Titanium backup - this mostly WILL mess up your system!
And before flashing devnull ROM download it again and check the MD5SUM, just to be sure your downloaded ROM is ok.
Good luck
MonacoHias said:
Hello LordRyve,
follow the great description from 777ace , these are the steps which should bring your Desire back.
I only would not restore all the programs via Titanium Backup after your fresh install. The reason is that there might be a "bad" program you have installed before. Just restore a program, check if system runs without problems, then restore the next and so on.
But NEVER restore system apps via Titanium backup - this mostly WILL mess up your system!
And before flashing devnull ROM download it again and check the MD5SUM, just to be sure your downloaded ROM is ok.
Good luck
Click to expand...
Click to collapse
Well now it runs rll great And I didn't do anything different. It restarted while charging but at about 98% it was cold again and I succesufly turened it on with first try. If something will go wrong i'll try do 777ace guide. Now I would like to ask...what to do that files would get transefered from my pc to sd faster? Because when my battery is not full it starts charging and overheating and restarting. Also isnt overheating and restarting caused by bad motherboard?
MonacoHias said:
Hello LordRyve,
follow the great description from 777ace , these are the steps which should bring your Desire back.
I only would not restore all the programs via Titanium Backup after your fresh install. The reason is that there might be a "bad" program you have installed before. Just restore a program, check if system runs without problems, then restore the next and so on.
But NEVER restore system apps via Titanium backup - this mostly WILL mess up your system!
And before flashing devnull ROM download it again and check the MD5SUM, just to be sure your downloaded ROM is ok.
Good luck
Click to expand...
Click to collapse
Also if there is bad app,could I try downloading it again after restoring with titanium?
LordRyver said:
Also if there is bad app,could I try downloading it again after restoring with titanium?
Click to expand...
Click to collapse
Sure you can.
With a bad app I ment that an app can mess up your system (not a corrupted program file).
For example task killers I would name "bad" apps as they are useless in current ROM and maybe could things worse.
A very important tip at the end: perform Nandroid backups on a regular basis - so you can allways come back to a working system.
LordRyver said:
...
Now I would like to ask...what to do that files would get transefered from my pc to sd faster? Because when my battery is not full it starts charging and overheating and restarting. Also isnt overheating and restarting caused by bad motherboard?
Click to expand...
Click to collapse
Do you use Windows or Linux? For me file transfer on Linux is much slower compared to Windows. Sometimes it helps to switch to another USB port on your PC.
Does your Desire also restarts when you use the power supply (charging not via PC)?
MonacoHias said:
Do you use Windows or Linux? For me file transfer on Linux is much slower compared to Windows. Sometimes it helps to switch to another USB port on your PC.
Does your Desire also restarts when you use the power supply (charging not via PC)?
Click to expand...
Click to collapse
Windows. Yes. It gets overheat. And switching to another USB port didn't helped. But I noticed that usb cable's part that puts into pc was a bit hot.
MonacoHias said:
Sure you can.
With a bad app I ment that an app can mess up your system (not a corrupted program file).
For example task killers I would name "bad" apps as they are useless in current ROM and maybe could things worse.
A very important tip at the end: perform Nandroid backups on a regular basis - so you can allways come back to a working system.
Click to expand...
Click to collapse
hm...I think problems start when I install classic ghost radar
Ok...can some1 explain me. my phone started to restart while moving movie from pc to sd. Now it's cold. But when I turn it on, it loads and after 1 sec in android system it starts restarting again. why?
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
The short version: I need to know how to do a carrier wipe on my Evo running CM 7.2, because ##72786# doesn't work.
The longer version: I've been trying to get my Evo activated on Ting since last Friday. It's been sitting around for about 2 years, and it was on an older version of CyanogenMod. Ting said I was all set, and to dial ##72786#, and then enter my MSL. When I do that, I get a message saying that my account could not be validated.
Over the weekend, I kept trying, but eventually decided to switch to a different ROM. That's been very frustrating, because I can't find working download links for the versions I want, and of the several others that I have tried, I can't get the phone to boot, after, at least not beyond the white screen. So, I put my PC36IMG on, and even that wouldn't do the trick. I thought maybe I'd bricked it, because it took 2 tries to get CM 7.2 going again, after all of that.
So, does anyone have any idea how to do a carrier wipe on CM7? From what I read, I have to do it differently, but using the stars in that code doesn't change anything. I tried a calculator hack, but that won't work for me, because the calculator it comes with doesn't have scientific mode. (Although I will now go try downloading one, to see if it works).
I'm at my wits end! I never had any problems during the 6 months or so using CM with Sprint, before I moved on to another phone. I've looked at hundreds of pages, mostly forum threads, and it seems so odd to me that I'm the only one with this problem.
One weird thing, on Sunday, Ting shows me as having downloaded a couple MBs of data, but to my knowledge, this has never successfully connected to their network. Perhaps I managed to get data to connect, when I wasn't aware? I never have even tried the steps to get data switched, since I can't get the carrier wipe done.
New number
If it matters, I didn't port my number, I'm getting a new number with this account.
Stars in Code Got Closer
So, I can use the dialer codes with stars in them. Or rather, some of them work. For example, *#*#33284#*#* will get me to a debug menu. When I try *#*#72786#*#* it reacts, but not like it should. The code I've been typing in disappears from the screen, as though it's been recognized as a valid code, but then nothing else happens, I don't get a menu, or anything.
I finally got another ROM flashed, and I was able to boot, but then the screen doesn't respond to my swipes, so I can't even unlock it. I'll be trying yet another ROM, but this is SO frustrating.
You need a sense ROM. Use captain throwbacks rooted stock. A sense ROM is the only tried and true way.
http://forum.xda-developers.com/showthread.php?p=26516892
Thanks for the reply! I believe I've tried that ROM, but I will give it another go.
The few roms I made from ctb base all have no problems using any codes, feel free to try one to program your phone, and if you do let me know if it worked.
I like to keep tabs on my work.
Sent from my PC36100 using Tapatalk 2
That ROM (captain throwback's 5.07.651.6 Stock Rooted - Deodexed) was already on my phone, so it was one I had tried. I went ahead and flashed it again, though. Pretty much anytime I flash a ROM, when my phone reboots, it stays on the white boot screen forever. I once let it go for 24 hours. I know it did it the very first time I rooted this phone, when I flashed the ROM. I eventually pull the battery, and most of the time, when I turn it on again after that, it boots normally. Some of the ROMs I've tried flashing in the last week won't boot at all, and I have to flash something else to get the phone going. I'm not sure now what the result of the first time I flashed this ROM was, but it's been sitting for about 30 minutes, now. I'm not sure how long I should let it go, before it's safe to pull the battery, so I'll probably wait until I run some errands, and come back to it in a few hours.
I'd be interested to know why the phone doesn't boot on the first try, after flashing, though. I wonder if that's why I've had no success with any of the ROMs I've tried, except for CM.
vinman, I will check yours out, if this isn't successful. I'm guessing the links in your signature will lead me to info?
Ok just to be clear, your rooted, s off, have a custom recovery like Amon 2.34 or smelks.
Do a back up of your sd card on your PC.
Now in recovery wipe everything,
Now format the sd card to 1024
Swap size 0
Upgrade Ext 2 to ext 3 or 4 if using a ROM with support for it, which mine has.
Now put your sd backup from your PC back on your phone sdcard
Now while still in recovery flash the ROM.
If your using mine it will reboot 3 times and take about 5 to 10 min to boot up do to the a2sd. Once it boots let it sit for 5 min to settle in.
Set up your google account
Now from dialer enter your codes you want it should work as I have a older version on my build just so you can use the codes.
Hope this works.
Sent from my PC36100 using Tapatalk 2
---------- Post added at 02:33 PM ---------- Previous post was at 02:32 PM ----------
vinman12 said:
Ok just to be clear, your rooted, s off, have a custom recovery like Amon 2.34 or smelks.
Do a back up of your sd card on your PC.
Now in recovery wipe everything,
Now format the sd card to 1024
Swap size 0
Upgrade Ext 2 to ext 3 or 4 if using a ROM with support for it, which mine has.
Now put your sd backup from your PC back on your phone sdcard
Now while still in recovery flash the ROM.
If your using mine it will reboot 3 times and take about 5 to 10 min to boot up do to the a2sd. Once it boots let it sit for 5 min to settle in.
Set up your google account
Now from dialer enter your codes you want it should work as I have a older version on my build just so you can use the codes.
Hope this works.
Sent from my PC36100 using Tapatalk 2
Click to expand...
Click to collapse
Just make sure you have all your Ting info in case you wipe it all.
Sent from my PC36100 using Tapatalk 2
So, this has been a pain, I'll put some detail here, in case someone else could use the info.
I backed the SD card up (again, again), and then from Recovery, I did a wipe (Wipe ALL userdata/factory reset). Then a Partition, where it asked the swap size first, which I set to 0. Then for Ext2-size, I set to 1024 MB. It then said FAT32-size would be remainder.
Back under partition, I did "SD:ext2 to ext3". There was an option to do "SD:ext3 to ext4", but I didn't do that. (Info on partitioning here, if anyone needs it)
Those took maybe a few minutes each. I then rebooted the phone normally, and turned on USB Storage, and copied just the clockworkmod folder over, so I'd have the the ROMs, that were saved there.
Nothing worked, so I started over. By nothing worked, I couldn't get it to boot to any of the ROMs I had, even the CM7 that had previously been working. It would just site at the white boot screen, and never would get to the CM7 screen, or whatever one was with the ROM I was trying, even when I'd let it sit for hours. Since I first rooted this phone a couple of years ago, it would often not boot after flashing a ROM, and just sit there at the white boot screen, but when the flash was successful, I'd have to pull the battery, and the 2nd time it would boot properly. I might not be cautious enough now, but I tend to not wait more than 30 minutes before pulling the battery. Also, in the past, I've flashed a ROM, and it wouldn't boot, so I'd repeat flashing that same ROM, and it would work the 2nd time. So, this whole thing has required a lot of patience and even more time. I typically walk through flashing a ROM, wait for it to not boot past the boot screen, reboot, and if it doesn't work I still wait a while, then lather, rinse, and repeat. Just trying to get this phone going in the last month, I've probably actively spent a good 15 hours, and that doesn't count when I just walk away and leave it plugged in, hoping time will help.
Anyway, I realized that that I had made a silly mistake, and that hadn't saved the PC36IMG_Supersonic_Radio_2.15.00.01.15.zip file as just PC36IMG.zip. So I did a wipe, and then partition.
When I partitioned the SD card again, I set swap to 0, and 2048 for the Ext 2, and the remainder for FAT32.
I tried pulling the SD card, using a reader, and copying the files over, but something was wrong, and my laptop wouldn't recognize the card. I'm fairly certain that the reader is broken, and doesn't work with micro SDs anymore, so I just put it back in the phone and tried to reboot.
First time booting, it stuck on the white boot screen again, so I gave it 10+ minutes then pulled the battery, and tried booting once more. Still no go, so wiped and tried again. Still no, 2nd reboot, still no. Tried ext 3, no go.
So, I finally got to the store, since I couldn't find my other Micro SD adapter that works, to get another, and put the PC36IMG file on. I booted to recovery, it found the file, installed it, and rebooted. It stuck on the white boot screen, as expected, so I gave it some time, pulled the battery, and rebooted again.
I've been at this for the last week, and although I was able to get the CM7 ROM going a couple of times, I can't get it going now. And the PC36IMG isn't going, after the 2nd reboot. I have hope, but it's waning. I'll be doing some additional research, in between other stuff, this afternoon. But, I thought I'd go ahead and post this, since I've been writing down what I've done as I go this time, just in case someone stumbles along and knows what I'm doing wrong.
So, I followed some of the advice from the Rooting for Dummies guide and I wiped the Dalvik Cache a couple of times, and then decided to go ahead and Wipe All a couple of times. Then I partitioned the SD card (0, 2048), followed by upgrading ext2 to ext3. I copied PC36IMG back over, and tried that again. I then decided to figure out what the ext2 thing was, and found this question about ext2, ext3, and ext4, which says that it doesn't hurt to go to ext4, that the older ROMs will convert it back, if needed. So, I did that.
Of note, when I rebooted, to try for the PC36IMG again, I noticed that it can't find what I think says PC36IMG.diag, although otherwise it always seems successful, other than not booting past the white boot screen.
I'm waiting to see if it gets past the boot screen, now. Assuming this doesn't work, I'll repeat with the ROMs that I have, and hope that will work. Probably won't post again today, unless I get somewhere new.
Wow, I finally got it going! Notes are below for reference. I tried the deoxed ROM mentioned at the end of my notes. (can't paste right on mobile) but only the 3rd try, it worked. The only thing different was that I didn't have it plugged into the wall when I ran through the flash and reboot, this time. Does anyone know if that would make a difference, or if it's coincidence? Anyway, next I'll want to go back to CM7, but I'll wait till tomorrow, after I backup, and have time.
Here are my unedited notes, in case it might help someone else...
Wiped, partitioned, enabled USB-MS, created a "clockworkmod" folder on the empty SD card, then copied the oldest folder I have handy, "2013-07-13-16.11.44" over. Then exited USB, and selected "backup/restore" and then "restore nandroid", intending to select that backup.
Of course, when I tried to mount the USB, my laptop refused to recognize it, so I had to reboot my laptop, before continuing with that step. This is kind of how every step along the way has gone. Rebooting didn't help, and I though tht worked!
at this might be why my laptop stopped seeing the card through the phone before, and I tried upgrading ext3 to ext 4, which I had skipped this time. That didn't work, so I went ahead and powered the phone off, and used the micro SD card reader to transfer those files over.
Of course, restoring the nandroid didn't work. Apparently, even though I put it back in the folder it came from, Nandroid expects it to be in a different folder. So, I created a "nandroid" folder, to put the files in. It needed them in appropriate subdirectories, so that didn't work.
Next, I pulled out my backup drive, and looked for my original Evo backups, from a couple of years ago.*
I found a nandroid folder that had the device name and then a backup folder with the expected type of name. I got that on the card, put it in, did the recovery, and this time, it was recognized, and the restore started. It took I'd say 20 minutes to complete. When I had it reboot, I walked away, and when I came back it had rebooted to recovery, which was unexpected. I had it power off, and then turned it back on. That repeated when I turned it off and on, so I guess that I've finally hit my first boot loop.
I did a wipe, moved PC36IMG to the root, and tried that. Rebooting gave me the white boot screen, then it went dark, rebooted and went to Recovery. I tried rebooting again, same thing. I did a wipe, then rebooted. It did the dark screen, then rebooted to Recovery. I tried again with the*5.07.651.6_stock_rooted_deodexed_CPTB ROM
I'm having the same exact issue.
Hi all,
I'm having the same exact problems described here, and for the same exact reason. I'm switching from Sprint to Ting, though I ported my number, too.
I've spent all afternoon trying to restore stock roms so I can input the ##72584# number or whatever it is and activate my service, but I can't get any roms to work right now. I'm going to try the recommended DEOX version mentioned in this thread now. Just putting in my note so others can see they're not alone.
If I get it working, I'll mention how.
Good luck. I'd be happy to help, however I can.
Given that sometimes I've had to install a ROM twice to get it to take, I'm really wondering if the phone being plugged into power (not even a PC) might have affected something. It would seem like a really weird thing, but that's the only thing that was different the last time I tried to install that ROM, and it was at least the 2nd time in a row, if not the 3rd. So, try multiple times, until you get it going.
Should not be this hard to flash a sense Rom and enter service programing codes. Simple thing is just back up your SD card to pc,
Then partition your SD card ext 2 is fine for stock gb Rom. So after partition put your backed up SD card back on your SD.
Wipe the phone 3 times except for SD. Flash Rom. Should work fine
What I had to do
In brief what worked for me is that I needed to install a stock rom without the custom recovery to allow the ## commands to work from the dial pad. You do not need to go all the way to S-ON.
Step 1 - Upgrade your custom recovery and have an image of your custom recovery for you to re-install. I use Clockwork Mod. You can get it here:
http://forum.xda-developers.com/showthread.php?t=1473525 Save PC36IMG.zip of your custom recovery on your PC for later.
Step 2 - Boot into your custom recovery and make a backup.
Step 3 - Download and save PC36IMG.zip of the STOCK ROM from here: http://forum.xda-developers.com/showthread.php?t=780141 You do not need the S-ON.
Step 4 - Reboot your EVO 4G into HBOOT with power and vol-down and let it install the stock ROM. THIS WILL OVERWRITE YOUR CUSTOM RECOVERY. You have your custom recovery saved from step 1, right?
Step 5 - Reboot and then use the keypad to do your carrier wipe from this page: https://help.ting.com/entries/22935397-Activation-for-your-HTC-Device Let it reboot several times.
Step 6 - Copy the PC36IMG.zip from step 1 onto your SD card.
Step 7 - Reboot using power vol-down into hboot again and let it install your custom recovery.
Step 8 - Reboot into your custom recovery and restore your backup image onto your phone.
Edited to add, I did not have to wipe my SD card, but your mileage may vary.
use sprint base sense Rom
use s sense base sprint Rom.
you can try digitalkarmav9
it worked for me.
best thing about Ting, you don't have to mess with flashing. and they are resonable if you don't use data.also unlike boost or virgin they toss over to verozon when you roam