Related
I've owned my DInc for around 8 months now and a week after I got the phone I had rooted it... The only thing I truly did was install a few custom ROM's on it to try out what I liked, when Froyo was in it's prime I used CM6 nearly every day, and now Gingerbread is around I've been running steady on OMGB6/7 for the past few months...
My problem is that last week my phone randomly rebooted and decided to get stuck on the white "HTC" boot logo... It stayed there for around 10 minutes before I finally decided to pull the battery, restart it, and the same thing occured.
Of course I have CWR installed with Nandroid backups, but when I used the backup for the current ROM I was on, it happened again getting stuck at the white screen. So I fired up CWR again and restored to a previous version of OMGB6 and that ran steady until today (in the middle of calculus of course) it rebooted after sending a text and got stuck at the white screen once more...
Now I CWR restored to my Stock HTC Sense ROM and I'm running that as we speak (and god, is it god-awful).
WTF is wrong with my Incredible? I'm guessing something got corrupted maybe in the /boot partition or something of the likes? Could someone please help me? I've never had this problem before... and never did any "customization" other than wiping my cache/data/dalvik/battery stats and installing different ROMs.
Thank you!
al2x said:
I've owned my DInc for around 8 months now and a week after I got the phone I had rooted it... The only thing I truly did was install a few custom ROM's on it to try out what I liked, when Froyo was in it's prime I used CM6 nearly every day, and now Gingerbread is around I've been running steady on OMGB6/7 for the past few months...
My problem is that last week my phone randomly rebooted and decided to get stuck on the white "HTC" boot logo... It stayed there for around 10 minutes before I finally decided to pull the battery, restart it, and the same thing occured.
Of course I have CWR installed with Nandroid backups, but when I used the backup for the current ROM I was on, it happened again getting stuck at the white screen. So I fired up CWR again and restored to a previous version of OMGB6 and that ran steady until today (in the middle of calculus of course) it rebooted after sending a text and got stuck at the white screen once more...
Now I CWR restored to my Stock HTC Sense ROM and I'm running that as we speak (and god, is it god-awful).
WTF is wrong with my Incredible? I'm guessing something got corrupted maybe in the /boot partition or something of the likes? Could someone please help me? I've never had this problem before... and never did any "customization" other than wiping my cache/data/dalvik/battery stats and installing different ROMs.
Thank you!
Click to expand...
Click to collapse
This used to happen with me on OMGB, its one of the reasons I switched to CM7. When I rebooted it used to get stuck on the splash screen. Mine, however, would work after a battery pull. I'm not sure, I'd try a fresh install, if that doesnt help, try out CM7, its a pretty stable.
Oh ok... so you're saying its probably just a ROM issue with OMGB? I'd switch to CM7 but the only thing I want is stock Gingerbread, I really hate the little customizations they put into CM7. Do they still have that CM7 Source project going on where it was pretty much stock gingerbread? Thanks again!
al2x said:
Oh ok... so you're saying its probably just a ROM issue with OMGB? I'd switch to CM7 but the only thing I want is stock Gingerbread, I really hate the little customizations they put into CM7. Do they still have that CM7 Source project going on where it was pretty much stock gingerbread? Thanks again!
Click to expand...
Click to collapse
I'm not saying thats 100% the case. I'm just saying that used to happen to me when I ran OMGB. I couldn't find a fix, so I just switched ROMs. I don't think CM7 has a just stock gingerbread look. But how can you not like all the features they packed into it?
AOSP + SD
Perhaps try flashing a Sense ROM and see if the issue persists.
Why?
AOSP ROMs interact quite a bit w/ the SD card. So, if there are issues w/ the SD card, the Sense ROM may not present as many funky issues.
After that test, I'd try another SD card and see if the issue persists.
If a different SD yields no wonky stuff, the answer was faulty SD card.
continual spontaneous reboots
I have the same issue. I was using CM6.1 I think and it's been fine for awhile and then it just started spontaneously rebooting. I can no longer get into Clockwork, all I can do is hold volume down and power to start it and from there, nothing will start the phone. I get the HTC spash and after about 3 seconds, it reboots and gets stuck in that cycle. Nothing has really changed and it rebooted on it's own to start the problem.
So, it's not like I installed something and rebooted. I'm interested in hearing if others are having the issues and what exactly their thoughts are.
Hey Guys,
I've been some flashing lately and I'm not sure what caused the problem. I've been using SprintLovers Rom with no issues since Feb. But when it stopped being supported, so I switched over to [ ROM / 5-3 ] Calkulin's EViO 3 v1.0 Beta 2 [ 4.12 l Gingerbread l Tweaked ] (which IO loved by the way)but I kept getting constant reboots. I would be using Navigation or watching a video with Rock Player and within one min , my phone would go into a boot loop and stay rebooting until and I flashed the rom again. It drove me nuts and I couldnt take it anymore.
So I reformatted everything (even deleted my card by accident) and installed [MikRoms] - [6/7/2011] - MikG v1.03 - Re-Engineered GB Sense 2.1 + 3.0 (which I also love) and the reboots are not as frequent but they are still happening. The difference is that with this rom, its getting stuck in a boot loop at the HTC EVO 4G screen that you see when it boots up. If it does boot up, the phone gets to the Sense screen and reboots again. So the only way I can get it to boot back up is to flash the rom again from recovery.
I have a 32GB Duracell Microsd Card I got off Amazon: http://www.amazon.com/gp/product/B004AM6SOG
It worked perfectly with Sprintlovers rom, But as soon as I reformatted and flashed Calkuns rom, the reboots started,. I even tried using Nandroind and going back to a Sprintlovers backup and the reboots were happening on that rom and I never had issues with that rom.
So basically I'm trying to narrow down what is causing the rebooting. I thought maybe the memory card was going bad, but how can I tell? So what I started thinking was maybe my bootloader needs to be refomattted or cleaned? But I dont know how. Then after talking to Nick1313, who helped me reformat and get my phone running again, we started thinking maybe the internal memory of the phone has gotten corrupted. I assume that Android looks to boot the OS from the internal memory and then looks to the SD card for apps and etc....
Is there a way to test my SD card to see if its ok? is there a way to see tell if my internal memory is corrupted and if so can it be reformatted and fixed?
I saw some people having a similar issue in the Galaxy S forums,but no one seemed to have a solution.
My last resort is unrooting and returning my phone to the store tomorrow. The only problem with that is , I know they are gonna have to order me one and it wont be in until Monday or whatever and the is annoying.
Any ideas would be greatly appreciated.
Snarky Answer: Well, I now know which memory card NOT to get.
Serious: I really doubt your SD card has much to do with this. Internal memory does have the potential of getting corrupted. That said, it's not likely.
It's obvious that you had good specific reasons for flashing the rom you've flashed. My advice is to flash one that you've not flashed and see if your phone's behaviour is any different.
jesuspgt said:
Snarky Answer: Well, I now know which memory card NOT to get.
Serious: I really doubt your SD card has much to do with this. Internal memory does have the potential of getting corrupted. That said, it's not likely.
It's obvious that you had good specific reasons for flashing the rom you've flashed. My advice is to flash one that you've not flashed and see if your phone's behaviour is any different.
Click to expand...
Click to collapse
Thanks for the reply. I actually Flashed back to Sprint Lovers Rom last night to after deleting everything again and reboots were still happening. I flashed back to MikG rom this morning. No reboots as of yet. But it rebooted on me 5 times last night before I flashed Sprintlovers.
GPS has been the main app I've busing when the rebooting starts. So I'm testing my phone right now with having it map to a far location and keeping my screen on to see how long it takes to make my phone reboot. Right now I'm 3mins into the test.
Turns out the processor in my phone is bad and Sprint has to order me a new one
I rooted my Evo for the first time today using the Revolutionary method. Everything went smoothly following the instructions. I downloaded and flashed the latest Evo Classic ROM and I was loving it. It seems to be an awesome ROM. I have 200 MB free space instead of 46MB with all of my apps installed. Everything was great until I went to go to bed. I put the phone on the stock HTC charger and climbed in bed. Less than a minute later it rebooted. The phone has always done that at random times so I didn't think anything of it. Shortly after it booted it rebooted again. It just keeps rebooting over and over as long as it's on the charger! Now it even reboots when it's not charging but the interval is as long as 10 minutes instead of 1.
Has anyone else had this issue? I spent HOURS getting everything just right and customizing settings after flashing this ROM and I really don't want to have to do it all over again. I followed the instructions for flashing the ROM. I cleared the cache and wiped all data. I backed up my apps with Titanium Backup and restored a select number of them. My phone is my alarm clock. Now I can't trust it to wake me up in the morning to go to work!
EDIT: I just restored from my stock NAND backup and it is working fine for tonight. I'm guessing I need to just start from scratch and reflash Evo Classic? I can't seem to find anyone else that had this problem so I assume it was something with my flash or an app I had installed?
I flashed a fresh Evo Classic ROM and started over. Everything was great. I got it all setup and restore my apps. No rebooting problems. Put it on the charger. Worked fine. As a troubleshooting step I opened Sleep, my alarm clock app, and within 30 seconds it rebooted. Obviously something with that app triggered it. I uninstalled it. About a minute later it started a reboot loop in one minute intervals.
Apparently no one has any ideas or I am invisible. I can't post in the Evo Classic thread because I don't have enough posts to earn me the privilege.
Did you wipe dalvik? And what recovery are you using?
I am using Revolutionary recovery (I think?). It is the one that was installed when I rooted following the directions.
I only see two options:
Wipe Data/Factory Reset
Clear Cache Partition
I have done both of these each time I flashed. I just flashed again and installed only the Sleep As An Droid app fresh from the market. I opened it and within one minute it rebooted. Obviously this app doesn't agree with this ROM or something isn't going right during the wipe and/or flash.
Any other suggestions for a stable ROM that has the new Sense notification bar with quick settings?
EDIT: I found the Dalvik Cache wipe option under advanced. Doing it now and will reflash and try again.
EDIT 2: Well that failed. I wiped data, cache partition, and dalvik and flashed the ROM. I logged into my Google account, downloaded the app from the market, put the phone on the charger, opened the app, and it rebooted.
Is it rebooting if you don't use that particular app at all?
Evo450 said:
I am using Revolutionary recovery (I think?). It is the one that was installed when I rooted following the directions..
Click to expand...
Click to collapse
That recovery is called clockwork. You might think about changing your recovery to amon ra since some people have issues with clockwork because it doesn't properly wipe cache and dalvik
Hey there! Sorry about your issues. I don't always check the q&a, so you are usually better off posting on my thread or pm. I just happened to peep on here today
First. Use this. It's the second step on my instructions to flash Classic. Not necessary, but recommended. http://forum.xda-developers.com/showthread.php?t=705026
Second, don't use titanium backup. Instead, use mybackup root (free in market and included with my Rom). Not to bash tb, but mybackuproot has never given me issues while I've heard stories about tb.
Third, once you get amon ra installed, boot into recovery and wipe everything but your sdcard.
Fourth, download a fresh copy of classic from a reliable network, like home computer. Downloading from a phone is bad news (just a tip since you're newly rooted )
Fifth, flash and enjoy!
Please let me know how it goes for you.
Truly,
Tommy
tapatalk signature here. lovely.
Thank you very much for the reply! I will try your suggestions some time this weekend. I need my phone to work 100% as I am traveling so maybe Sunday I will try again.
I followed all of your suggestions and redownloaded the ROM, installed RA Recovery, cleared all data, cache, and dalvik several times, and reflashed the ROM.
I restored my apps and data using MyBackup Root and it took over 2 hours! I opened my alarm app and... reboot. Back to the same old reboot over and over.
I think I'll just go back to the stock ROM and remove the bloatware and call it good.
Theirs one obvious thing nobody mentioned. Google how to check a md5 sum do that with every rom you download and if it does not say its right don't flash, redownload and check again. Also restore as little as possible through mybackup and if you are restoring things like your alarms or any system settings don't.
As for good roms with quick settings like r2r going green lightning fast, or unleashed r6.
Ps I would suggest useing r2r superwipe before whatever you may flash n wipe both caches a few times first it might help
sent from a silky smooth evo useing tapatalk
did I help? hit that lil thanks button then
Also id recommend copying all contents of SD card to computer and wipe SD card then reload everything back onto SD card. I know sometimes the SD card can become corrupt and cause bootloops and random reboots
I checked the Md5 sums of everything I downloaded. I only restored my apps, text messages, and Bluetooth pairings. I even ended up buying a new, larger SD card yesterday and I formated and used it when I flashed.
This afternoon I flashed my latest backup of my stock ROM and used Titanium Backup to removed all of the Sprint bloatware. My phone is running very fast now with over 110 MB of internal memory available so I can't complain.
Maybe next weekend I will try another ROM but for now I need me phone to be working since I do not have a land line and I rely on my phone for work.
You said this happened before you ever rooted? Maybe its a factory defect if u got a.warrenty I would suggest unrooting and sending to them.
sent from a silky smooth evo useing tapatalk
did I help? hit that lil thanks button then
I got my original Evo on launch day and it had the random reboot problem from the first month. It was very infrequent at first but after a few months it got worse and worse. Finally, one day it started rebooting in a loop while I was at work. I took it directly to a Sprint store where they ordered me a replacement. The replacement has been great. It reboots on it's own once in a great while (maybe once every two months).
This seems to be very common. The reboots I got when I flashed the Evo Classic ROM were as bad as my original phone was just before it got replaced. The difference is that is definitely software based because flashing the stock ROM fixes it. The reboots I had on my original phone happened when the phone heated up randomly and were not fixed by a factory reset.
Its not normal they keep giveing you defects... I have never heard of.this problem anyway... I would take it bac
sent from a silky smooth evo useing tapatalk
did I help? hit that lil thanks button then
Evo450 said:
I got my original Evo on launch day and it had the random reboot problem from the first month. It was very infrequent at first but after a few months it got worse and worse. Finally, one day it started rebooting in a loop while I was at work. I took it directly to a Sprint store where they ordered me a replacement. The replacement has been great. It reboots on it's own once in a great while (maybe once every two months).
This seems to be very common. The reboots I got when I flashed the Evo Classic ROM were as bad as my original phone was just before it got replaced. The difference is that is definitely software based because flashing the stock ROM fixes it. The reboots I had on my original phone happened when the phone heated up randomly and were not fixed by a factory reset.
Click to expand...
Click to collapse
My girlfriend had the same issue with her second evo. She had the Black Evo at first than a friend of hers swapped her to the white Evo. She had the issue only on the white evo. She ended up having to replace the phone with another one. That one did the same thing for awhile so we thought it was an issue with an app she was running. I have the black evo and made a exact copy of her phone. I never once had the issue.
Sprint ended up replacing it agian with a line that something was different in the white Evo from the black one that was causing the issue. Ever since that day she hasn't had a problem with her phone. I just rooted and did her rom last night.
My question would be does the phone get hot? Or feel hot? The reason I ask is that the phones processor may restart the phone (in effort to cool it down) randomly. That is something to consider.
Glad I got the black
sent from a silky smooth evo useing tapatalk
did I help? hit that lil thanks button then
Evo450 said:
I got my original Evo on launch day and it had the random reboot problem from the first month. It was very infrequent at first but after a few months it got worse and worse. Finally, one day it started rebooting in a loop while I was at work. I took it directly to a Sprint store where they ordered me a replacement. The replacement has been great. It reboots on it's own once in a great while (maybe once every two months).
This seems to be very common. The reboots I got when I flashed the Evo Classic ROM were as bad as my original phone was just before it got replaced. The difference is that is definitely software based because flashing the stock ROM fixes it. The reboots I had on my original phone happened when the phone heated up randomly and were not fixed by a factory reset.
Click to expand...
Click to collapse
I kept getting the same thing when i flashed classic. I went back to shooter port which runs butter smooth and is fantastic looking with sense 3.0.
DO THIS TO TRY TO GET EVERYTHING WORKING (no more soft reboot)
-connect your sd card to your computer
-copy contents to your computer for a backup
-copy PC36IMG.zip to your sd card make sure it is on root of sd card(attached to message)
-disconnect usb cable then pull battery
-enter bootloader (vol down + power)
-when it asks if you want to install the new update select yes
-after thats done pull the battery again
-enter bootloader then select recovery ( you should now have amonRa 2.3 )
-flash zip from sd card (vrsuperwipe.zip *thanks to virus*)
-go back and go into wipe menu, wipe dalvik-cache, wipe sdext, battery stats, and rotate settings.
-go to partition sd card and partition for a gingersense rom if you have not done so already. (0 swap, 1024 or 2048 ext2, remaining FAT)
ABOVE PROCESS COULD TAKE SOME TIME, MAKE SURE YOUR SD CARD IS MOSTLY EMPTY BEFORE YOU DO THIS (ONLY HAVE PC36IMG.ZIP ON IT)
-select usb mass toggle and connect to computer
-copy over your choice of rom, i suggest the shooter e3d port by team nocturnal.
-flash rom
-go to flash zip from sd card again this time select TeamNocturnal folder and pick a kernel to flash (try all of them if you would like, some phones run better with different kernels. mine runs well with HDMwIn kernel.
-wipe dalvik-cache one more time and you are ready to reboot with no more random restarts hopefully.
good luck - and please hit the thanks button if any of this works for you
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
Hi guys,
I've got a bit of a problem. My phone is stuck in a boot loop, which is a problem I've dealt with before, with help from these threads.
But this time I'm really stuck. I can't access the HBoot screen like I normally can, by holding down the volume up and power off buttons simultaneously.
I am using (racks memory) I think it's the War something mod of Cyanogen 7 I believe. I installed it 5 months ago and it's been working fine. This is not a new or recent install!
The phone does suffer from low memory issues a lot, as do all Wildfire S's. I have managed to get around that previously by moving apps to the SD card or linking to it or making user apps into system apps. I was in the middle of chatting on whatsapp when suddenly the phoned just blipped and died on me.. then it went into the boot loop. It's never happened before and my suspicion is that it ran out of memory or something.
I've tried removing the battery and leaving it out for some time, no luck. I've tried restarting without the SD card and Sim card. No luck. I've tried connecting it to my laptop... no luck. All the usual tricks just aren't working.
I have TiBu installed and my most recent back up was less than 4 weeks ago. I also did a Nandroid system backup a few months ago, so I should be able to restore ok, I just can't access the HBoot screen.
The other weird thing is, when I left the loading screen going round long enough, like in the time it would normally have booted.. suddenly the sound of my new emails popping up plays... and today, even tho it was on the load screen, it made clicking sounds like when I activate apps when my finger touched the screen. It's almost like the phone has started up as normal, but the load screen just won't go away and underneath it all is normal.
I've never had anything quite like this happen before and I've been without my phone for 3 days now, so came here in desperation for some inspiration! hehe.
I am probably going to buy a new HTC phone with a large system memory cos altho I dearly love my Wildfire S, the low memory has caused me nothing but problems since I first bought it, and I have wasted hours and hours on it, trying to get around the problems caused by it. But until then, I need to get my contacts and messages back and continue to use it for now. I would also ideally like to keep it going and give it to my sister perhaps who doesn't have a smart phone. She won't need as many apps as I do, so it would likely suit her, or maybe my Mum.
Any help anyone can give would be massively appreciated. Thanks guys!
Can't access HBoot!
Hey is anyone out there? I know lots of people get stuck in boot loops and there's a million threads of support for that, but this is different. I can't access the recovery system either. I have clockwork mod on it and normally you can get into that fine. Trying to find help on this problem is really tough cos I have to wade through all the noob threads for standard easy fix boot loops. If anyone could help me on this I'd be extremely grateful.
This might be all I can offer but two things come to mind. The first is you said volume up its volume down to get into the bootloader. The other is to search in the wildfire forum regarding whatsapp. Recently I read a post about a guy who's phone crashed from whatsapp. I don't remember how he recovered you have to search on it; unfortunately the second time he couldn't recover.
Good luck
Sent from my HTC_Amaze_4G using xda app-developers app
Thank you!
MiCeltic said:
This might be all I can offer but two things come to mind. The first is you said volume up its volume down to get into the bootloader. The other is to search in the wildfire forum regarding whatsapp. Recently I read a post about a guy who's phone crashed from whatsapp. I don't remember how he recovered you have to search on it; unfortunately the second time he couldn't recover.
Good luck
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
Thank you for this... I'm willing to grasp at any thread at the moment. I did try the volume down option too but no dice there... but the whatsapp thread sounds promising, so I'm going to follow that up right now. It's after 4am and I've been sitting here working on this for hours and hours and at my wits end, so thank you! Fingers crossed!
Accessed HBoot!
Update:
Ok, I couldn't find the thread about whatsapp that was referred to above, but I have just tried accessing the recovery menu, using the volume down and power key, after first removing the sim card, but leaving the sd card in place. Suddenly that seemed to work! The menu came up!
I tried accessing it again with the sim card back in, and it refuses to come up again as before. So that at least is one issue resolved.
Now I'm having trouble mounting my SD card, which it says can't be mounted. I know the backups and recovery files are on the the SD card, but it just doesn't seem to see them there.
I wiped the dalvik cache in case that was causing any problems and it doesn't seem to have resolved this current issue so far. I'm going to keep trying other options as see how I get on, but I least wanted to share the solution to one of the problems my thread raised.
Further Update
I couldn't remember the name of my mod in the first post.. it was the WildChild mod.
After getting my phone into HBoot by removing the sim but keeping the SD card in, I found I was unable to mount the SD card. I researched this problem and some suggest the card may be corrupted.
I have checked the card on an external reader plugged into my PC and it read perfectly fine, and I managed to copy every bit of data on it across to the computer with ease. Others however found that after a reformat it eliminated any problems with mounting.. so that is what I am going to do and then try and restore the copy of the data I saved to the PC back onto the SD card.
Attempting now to reboot normally with the sim back in and the SD card removed this time produced a very desirable result. My phone started back up, albeit without the normal operating system. I was able to connect to wi-fi and my network and see a missed call voice mail message symbol. There are however no apps at all as yet and no background screen. I should mention that the phone did ask me to allow SuperUser permissions again.. I should also mention that I foolishly tried to Fix Permissions in CWM which then sat for a long time, eventually I removed the battery cos I thought it wasn't gonna do anything.. this is a big no no I now find out from the threads and I may have buggered it up a bit. I don't know.
My saga continues anyhow, and although I've not had much support on this, it might still be helpful for others to read and follow should whatsapp crashed their phone too and mess with their SD card somehow.
Another Update - Making Progress!
Next update on this...
I removed the SD card and put it in an external reader again on my PC.
Then I installed the free program Mini Tool Partition Wizard Home Edition and selected MiniTool Partion Wizard rather than the Power Data Recovery.
The Wizard allowed me to see the hidden partition on my drive. I understand now why it has always had trouble reading and writing to the SD card in the Ext section that was hidden. This should have been an EXT-2 or EXT-4 format partition I think, and mine is an EXT-3.
Maybe I'm wrong, I don't know much about these things and just learn as I go and by experiementing.
I had hoped to back up the hidden data in the partition but I was unsuccessful. Instead I found the Rebuild MBR (Master Boot Record) option and applied that to the entire SD card.
I then put it back in my phone, again without the Sim, and went into HBoot and recovery. I then went to my advanced back up and restore section and now the SD card is mountable and readable! I didn't have to wipe it or reformat!
I found my most recent up date which was the end of August... I wish I'd done them monthly, but oh well not too bad... and selected it and chose to Restore Boot.
Once it had completed I tried to reboot, but no dice. I put the sim card back in.. still didn't work... BUT I was now able to get into recovery again, this time without removing the Sim!
So inching along slowly here with this but making progress.
Next I plan to restore boot again, this time with the Sim card in.. and try and restart.. if that fails, I will go back into advanced recovery and try to also Restore System, and lastly restore SD-ext and see if each of those options repairs whatever damage that stupid Whatsapp did to my phone! I hope the little solution to various problems I've had are of some use to someone else here. Now wish me luck!
Wow, you were busy last night while most of the western world slept . I'm guessing if I posted at 11:10 PM and you said it was 4:00 AM, that your in the London timeline. I thought a little bit more, later, and I think that person's post I read fixed his phone by eventually getting into recovery and restoring, which as I remember worked that one time, until he reinstalled and used Whatsapp again some time later (it was at the insistence of a girl that used it). Whatsapp has, like 300 million users, but it does seem to give some people serious problems, and that's why I think most people are hesitant to try and help. They don't want to make things worse, since there are those instances of totally bricking a phone...but as long as a person can get into recovery, it's not bricked!
Interesting...I have done the, "fix mbr" in PCs many times, but I think you've taken it to new levels using it in phones! At least I don't remember reading anything much about someone doing it (in phones) before and it's brilliant, IMHO. You really did a great job sharing what you've done and I hope you get it fixed. I clicked a, "Thanks" for a good post follow up.
Insert standard disclaimer here: I'm not telling you to do anything, or what will or won't work, but sooner or later you're gonna have to restore that backup, but it's your choice on what to do; and, it sure seems like you know what you're doing, especially having made a backup to work from. I can appreciate the way you've gone piece by piece in your restore efforts to try and find where the problem occurred. The nice thing about the Wild Child ROM is it all works, and incidentally I think the developer uses ext2 for his extended SD card partition! It sounds like you reformatted to ext2 or ext4 from ext3, so the only thing there now is what came from restoring that backup piece in Clockwork; therefore, there's nothing that would be lost that isn't already; and, you backed up everything else on the SD card. So I don't want you to brick your phone either, but I'm wondering about wiping the cache and then the dalvik-cache, and then restoring your whole Nandroid backup?! I think your Whatsapp contacts are saved and so if the phone boots to a working condition you could just uninstall Whatsapp right away, boot into recovery and wipe cache and dalvik-cache again just to be safe, and then decide what to do about using Whatsapp again. As long as you can get into recovery, ultimately you could wipe, wipe, wipe and reinstall Wild Child to start all over if nothing else works.
On the other hand maybe you've already got this whole mess straightened out, if not, I'll again wish you - Good luck!
Solved!
So I next wiped the cache partition 3 times, as someone on another thread said sometimes it takes more than one go to clear it all properly for some reason.
I also wiped the dalvik cache again a couple more times. Then I went back to my back up and restored system. Then I tried to boot my baby back up.
I was falling asleep at this time but I remember the phone partially recovered. But most of the apps were broken. I had low memory issues too, so I uninstalled a few apps, managed to restore some individual apps or update them, and log in long enough to send messages to contacts with my email so I wouldn't lose them.
Then I fell asleep with the phone in my hand haha.. when I woke up I immediately continued with it and finally worked my way back to whatsapp being the last app I wanted to deal with. I managed to get into it and send some messages.
Then I did a full nandroid restore on everything.
The phone returned to it's state as of 2 months ago when I last did a nandroid back up. But some of my TiBu apps were backed up more recently. So I manually restored those and things were mostly back to how they were before and I am fairly happy with the low loss of data.
Whatsapp was working fine for a while.. but then it started having problems. It first had all my contacts there... then it lost their names but kept their numbers, then it lost all the old messages and right now I'm in the middle of trying to restore everything again and it's stuck on a restoration. I did a full uninstall of the app, restored the back-up, then it tried to update, but it always fails and now it's just hanging. So it definitely appears that whatsapp is one of the major causes of problems on my phone.
It was also one of the largest apps I had on there. Wildchild is an awesome rom, it only lacked video really and I installed a codec and player for that and got it working again, despite the guys on the Wildchild thread saying they didn't think it was possible. Yes I had trouble with it sometimes, but most of my trouble stems back to the low memory issues and the fact I broke all my apps up by spreading parts of them over the SD card, internal storage as user apps and system memory. That's a Wildfire S problem, not the fault of the Rom.
Anyway, I've made note of all the important numbers and will be buying a larger capacity HTC phone this week. Not sure which yet, but possibly a Sensation or Sensation XE, depending on my budget.
Thanks for your support MiCeltic. Yes I'm in London hehe. And I hadn't read anything about using MBR on a phone, but it was the SD card which had the problem and that certainly fixed it without having to wipe all my data.
I think what I have here is multiple layers of problems.. and I'm really pleased that after 3 days effort I managed to get past most of them. Once I get my new phone and transfer the contacts, I will have to think twice about using whatsapp.. it's my favourite app of all tho, so it will be hard to part with. This phone has many bugs.. I will completely erase it and reflash it when I get time and either keep it as a back up and maybe gift it to my sister or mum as I said before.
:good:
Last update
OK this is my past update on this... Whatsapp had one last surprise in store for me.
After it started messing up my phone again. I gave it one last chance. I completely removed it from the phone and installed it as new from the GooglePlay store. Then when I loaded it, it found the backed up Titanium BackUp messages and restored those.. then when I opened the app, it also had restored all my most recent messages, up to the day before it crashed the whole phone. I was amazed. They must have been stored on the server or something.. I think they sit there for 3 weeks. So I'm likely only missing one weeks worth of messages at most, about 4 weeks ago! Ha! Brilliant. I'm not doing a Nandroid backup cos everything is stable again and I hope to have no more troubles until it comes time to transfer all the date to the new handset... that's gonna take a while cos I will have to learn how to gain the boot mod rights all over again and maybe even flash a custom rom as the stock is sure to be loaded with bloatware. Still.. if it has a 1GB internal memory it shouldn't slow the phone down too much.. not compared to the tiny 150MB this little baby has!
If someone wants to close this thread now, feel free.
Cheers. :good:
You inspired me to read a little more last night and I did see where some people found a fix by uninstalling and then installing new (not from backup), then restoring their contacts. Seems like you've proved that point! Interestingly I read that ALL of your contacts are stored on the Whatsapp server, not just your contacts that have Whatsapp (Remember those permissions you accept when you install an app!). As I said, there are 300 million users, obviously not everyone has the problems, so hopefully it will work for you now and on your new phone, which after reading your posts I know you will make a back up of immediately and again after rooting...AND definitely before installing Whatsapp ! ! ! You might even find your next phone easier to root as a lot of them don't need an update of the bootloader on htcdev for the first step when unlocking and/or many can gain Soff!
Glad you got it working and now all's right with the world...well for now