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 just recently went from the stock kernel with cwm eg30 deodexed root/busy box with 3g wifi hack to the new EL13 located below. (deodexed and modem flashed)
http://forum.xda-developers.com/showthread.php?t=1389874
I did a backup in titanium pro and cwm before starting.
The flashing went ok for the modem and the rom. I rebooted after wiping the cache and all and everything seemed ok.
I then started getting force closes and the launcher/phone would reboot. So thinking that there was some app data not installed right i went to do a restore in titanium and it would not complete do to the locking up/rebooting. I booted into cwm recovery to do an advanced restore and it keeps saying it cant access the folder ==> no files found and then goes back to main menu. I tried the fixed permissions and no change. The files are there I can see them on the internal sd as well as the copy i made to the external sd.
Is there something else I need to do? i cant seem to get it to restore.
I did end up clearing user data through cwm and it seemed to be successful except for the secure android piece of it. I rebooted an no force closes. I then ran titanium all apps+data +system data. 90% seems to restore except for widgets being set up on the home screen and widget locker. I can reset those up manually.
I want to make sure I am not going to have more force closing so I would prefer to restore all from the cwm nand if possible.
Any help with this would be greatly appreciated.
Something is wrong with the current recoveries for our phones in my opinion.
Maybe it's something we are doing, would be nice if a DEV could speak up but here is what I've noticed. I'm runing Calk's E4GT Rom. Is uses Rouge kernels/recovery and 99% of the time when I do a Nandroid backup when I try to restore is says something like files folders couldn't be found and drops back to menu.
Now if I mount my phones internal memory OR SDCard depending what I used, I'm finding my recoveries ON my device but for example I'm finding them in places like:
/smmc/smmc/bmmc/*
or
/sdcard/sdcard/*
* being the actual directory the backup is in.
That said if I MOVE those date coded folders to /clockworkmod/backup/* all the sudden the phone sees them.
It's making the Nandroid backups in the WRONG dir 99% of the time and I've had this happen at least a dozen or so times. Matter of fact, it just happened yesterday. My Nandroids showed up in /sdcard/sdcard/* so I moved the dated folder to the clockworkmod folder as mentioned and poof, it works. Then I made a another Nandroid backup and it made it in the right directory (/clockworkmod/backup/).
Who knows... DEV's? On a side note, I also had this happen with just the standard CWM as well as the ACS hacked one, not just the Rouge version.
Thanks. I figured this is what was happening. I did try coping a few things and nothing would help in my case. I did run another backup and it finally seen that one on the sd card.
When i do a restore do I need to wipe user data ect first?
The reason i asked, is I am on the EL13 and i am trying to trouble shoot why at certain points after installing apps or going into usb mode (usb debuging on) and then dismounting the phone, then unplugging the cable my phone freaks out, and basically ends up doing a quick reboot, (quick sprint splash screen and then back to the lock screen as the launcher loads) well tries to load. It usually fails. Then i have to power cycle the phone and all seems fine. Sometimes I get in a reboot loop though. I don't as far as I know have any kind of app moved to sd card outside of games that would have a service running that would freak out when in usb mode.
btw the apps were set up the same way that they were on my stock rooted only eg30 image and i had no issues like this whatsoever on that. I have only had these problems since going to the el13 on here. Both the deodexed and odexed and the sock odin version.
So I did a nan restore before the installing of my apps. Just a clean cwm/root el13 image and when I booted back all was fine until i install my apps again. Cleanly from market or amazon. When I try to move the game to the internal storage via the built in app management program it errors out/fails then I do it again and it moves over. Every now and then i get a device is full error message when installing apps when i clearly have tons of room left on the rom and internal sd.)
reg storage is only 200 megs used with 1.8 gig free and the internal sd has 10 gig free.
So I dont know why this would be happening when I do a restore with cwm. Maybe i didnt do something right.
I did wipe the dalvik/cache before booting though. it had no effect.
do a complete wipe, and restart all over again. the issue lies in the recoveries most of the time because one kernel uses clockwork while others use their own recoveries. restoring backups made by other recoveries can give you issues. i personally only like clockwork recoveries and the others just annoy me lol.
ssconceptz said:
do a complete wipe, and restart all over again. the issue lies in the recoveries most of the time because one kernel uses clockwork while others use their own recoveries. restoring backups made by other recoveries can give you issues. i personally only like clockwork recoveries and the others just annoy me lol.
Click to expand...
Click to collapse
They were all clock work backups/restores from the same build/flash/os build/version
Would even restoring some app data via titanium be bad? I dont do all data just on some games, and apps. Never anything system related
For me this issue was NOT because I changed recoveries which all of them are based on CWM anyway but that is besides the point.
I could have Team Rouges Recover based on CWM flashed, wipe my phone, and this issue comes up.
Seems to do it with all the recoveries though on and off.
Just to preface, I have been flashing ROMs for 2 years now, and am by no means new to the game. However, I'll be the first to say that I'm not immune to making stupid mistakes. So if I'm being stupid, you can tell me and not hurt my feelings
I will give a history of what I have done with my phone since Monday after I picked it up, and some quirks I have noticed.
- Set up my phone, accounts etc
- Let Google backup/restore download and install all of my apps
- Installed OTA to ALJC
- Installed Note2 Toolkit on my PC, drivers load, adb recognizes.
- Rooted & Installed CWM recovery
- Flashed stock de-odexed ALJC
- Installed 5x6 launcher & ALJC 4x1 reboot options (rebooted and proceed to setup my homescreens, icons, etc.) (I noticed when trying to flash items from "internal" sd card, it says there are not any
- inserted my SD Card from my OG Epic (Titanium backups in place)
- Restored text messages from .xml file via TB
- None of the games I wanted to transfer data from would run after restoring data from my TB backups, had to clear data and apps run fine, except for NBA Jam (guessing b/c they were from a CM10 ROM and a different device)
-Got all my apps setup, wiped all the bogus data I got from my prior TB backups. After playing with the phone, running apps for several hours, did a full Titanium backup of my phone
- Booted to CWM & Saved a nandroid backup to external SD Card
- Flashed (dirty) ULE 1.0 ALJC Rom (I thought by flashing dirty, it would preserve all my data, apps, etc. = I was wrong)
- Attempted to restore all of my Titanium backups (only ~60% would restore...still trying to figure this out).
- Attempted to restore the backed up 5x6 launcher (with my screens/icons setup intact) via TB. This kind of worked, it definitely changed the icon setup, but it was NOT 5x6, and it did not have my previous layout (probably b/c it was trying to fit a 5x6 on a 4x4).
- Figured that the dirty flash screwed things up, so I would restore my nandroid and go back to square one, where I had stock deodexed with 5x6 & reboot options, and launcher screens intact. So I booted CWM and restored that nandroid.
- After restoring and rebooting, I'm not sure if anything happened at all. I had a 4x4 launcher, no reboot options, and several of my apps were missing (particularly, the ones that would not restore from TB before)
- Figured I aught to factory reset and then restore, same result as above.
- Currently downloading stock ALJ1 tar so I can start all over again
Click to expand...
Click to collapse
I know this is long-winded, but I wanted to put it all out there in case I am doing something categorically wrong with my Note II, so I do not replicate this problem. It has always been the case that a nandroid backup gets me back EXACTLY where I was when I made it (on both my Touchpad & Epic). For whatever reason, this did not happen in this case, even after a factory reset/wipe.
Perhaps CWM isn't working properly? Perhaps I need to try TWRP so that I can manually wipe /system (as far as I can tell you can't manually do that in CWM, but if I understand correctly, this is done when you flash a ROM or restore a nandroid).
Am I doing something wrong? Also, why won't CWM see any of the files I downloaded to the internal memory? Several times now I have booted CWM and when I try to flashing things I downloaded, I have to reboot and move them to my external SD card so that CWM can see them.
Are there settings that are being saved to my external SD card that are causing problems (I highly doubt it)?
Thanks to any and all suggestions/guidance/advice.
Looking forward to learning more and more about these awesome devices.
MeetFace said:
Just to preface, I have been flashing ROMs for 2 years now, and am by no means new to the game. However, I'll be the first to say that I'm not immune to making stupid mistakes. So if I'm being stupid, you can tell me and not hurt my feelings
I will give a history of what I have done with my phone since Monday after I picked it up, and some quirks I have noticed.
I know this is long-winded, but I wanted to put it all out there in case I am doing something categorically wrong with my Note II, so I do not replicate this problem. It has always been the case that a nandroid backup gets me back EXACTLY where I was when I made it (on both my Touchpad & Epic). For whatever reason, this did not happen in this case, even after a factory reset/wipe.
Perhaps CWM isn't working properly? Perhaps I need to try TWRP so that I can manually wipe /system (as far as I can tell you can't manually do that in CWM, but if I understand correctly, this is done when you flash a ROM or restore a nandroid).
Am I doing something wrong? Also, why won't CWM see any of the files I downloaded to the internal memory? Several times now I have booted CWM and when I try to flashing things I downloaded, I have to reboot and move them to my external SD card so that CWM can see them.
Are there settings that are being saved to my external SD card that are causing problems (I highly doubt it)?
Thanks to any and all suggestions/guidance/advice.
Looking forward to learning more and more about these awesome devices.
Click to expand...
Click to collapse
Well I personally use twrp and have had no issues so I cannot speak on your nandroid issues...I do know however that in twrp after selecting internal or external sd card, you sometimes have to manually navigate to the respective sdcard...as for your TB not seeing your back ups from your prior device, go to preferences< backup location< detect and select scan whole device
Sent from my SPH-L900 using xda app-developers app
Just to clarify your remarks to avoid confusion. I can clearly see my TB backups.
I did have to go and do those steps first. About only half of them would restore though. Kind of odd. Maybe some data corruption? Didn't matter if I did them one at a time or during batch mode. Also didn't matter which of the 3 processing modes I selected in TB. Once one of the offending backups was being processed in batch mode, the restore process would hang until I force stopped TB or rebooted.
How much free storage does your internal sd have remaining? I ask because my wife's s3 would do the same when it was below 1gig
Multiple GB, probably 7 or 8. I store everything on my external, music, pics, etc. Haven't had that much chance to fill up the internal yet =]
I don't know. ..Very irritating isn't
It is indeed. But that's the risk of being a flashaholic
...and of being a first-mover on a brand new device =]
Beginning to wonder if me rooting with SuperSu, and then flashing (dirty) ULE which uses superuser, may have caused any problems. Perhaps binaries were conflicting?
MeetFace said:
Just to clarify your remarks to avoid confusion. I can clearly see my TB backups.
I did have to go and do those steps first. About only half of them would restore though. Kind of odd. Maybe some data corruption? Didn't matter if I did them one at a time or during batch mode. Also didn't matter which of the 3 processing modes I selected in TB. Once one of the offending backups was being processed in batch mode, the restore process would hang until I force stopped TB or rebooted.
Click to expand...
Click to collapse
Oh okay I see what you mean now...I have no idea whats going on there lol. ..I hope you can somehow get that figured out because I know how much it sucks to lose app Data
Sent from my SPH-L900 using xda app-developers app
I am really puzzled now, I just odined back to stock and then up through all rooting/etc to get to ULE again. Totally wiped everything. TB is still giving me fits. I'm assuming they backups were bad. Half work, half don't.
I was able to restore apps from a nandroid I made on my OG Epic a month ago. So that's helpful. I'm going to delete all my TB backups once I get everything situated and start fresh (possibly b/c I made backups while on an odexed ROM and restored them on a deodexed ROM?).
I think I'm going to stick with TWRP for now. I don't know if CWM was working properly at all, and TWRP has a few more features. TB wasn't able to see a single app to restore from the two CWM nandroids I made. Not sure what's up with that.
I was going to mention the codex stuff but it really shouldn't matter as you are backing up the data portion not the system. Still you might have a look at setting/storage. USB debug on ...all that jazz
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
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