I did a search, but, didn't find anything that was quite like my question.
I recently had to return my EVO for warranty work. I was given a new one at the store.
Before I went to the Sprint store, I made a backup using ROM Manager/Clockworkmod that morning. So, I brought my new EVO home, went throught the jailbreak/unlock process, and, installed ROM Manager.
I opened ROM Manager, found the backup I had made, and started the restore process. From all appearances, the restore is going fine. It finishes the process, and I reboot the phone.
At this point, that smooth sailing starts hitting whitecaps. It starts to reboot, but, it never finishes. It's just an endless reboot loop. It will just loop through the intitial reboot screens until the battery is dead. I know, I let it sit that long.
I also had a couple of other, earlier, backups on the SD card. I tried those with the same result. Does anyone have an idea as to why the restore gets stuck in the boot process?
I would really appreciate any help with this. I'm at a loss at this point.
Thanks,
GT
Admins,
Sorry, it just hit me that, while I was searching the Development forum for info on ROM Manager and Clockworkmod, I posted my question to the forum also.
Please move to the appropriate forum. My apologies; I obviously was on autopilot when I posted.
Thanks,
GT
Your issue is that your new phone is not the same as your old one. Your backups will not work cross devices.
Sent from my RLS5 Sprint HTC Evo
I
garynky said:
I did a search, but, didn't find anything that was quite like my question.
I recently had to return my EVO for warranty work. I was given a new one at the store.
Before I went to the Sprint store, I made a backup using ROM Manager/Clockworkmod that morning. So, I brought my new EVO home, went throught the jailbreak/unlock process, and, installed ROM Manager.
I opened ROM Manager, found the backup I had made, and started the restore process. From all appearances, the restore is going fine. It finishes the process, and I reboot the phone.
At this point, that smooth sailing starts hitting whitecaps. It starts to reboot, but, it never finishes. It's just an endless reboot loop. It will just loop through the intitial reboot screens until the battery is dead. I know, I let it sit that long.
I also had a couple of other, earlier, backups on the SD card. I tried those with the same result. Does anyone have an idea as to why the restore gets stuck in the boot) process?
I would really appreciate any help with this. I'm at a loss at this point.
Thanks,
GT
Click to expand...
Click to collapse
I hope you removed the wimax.img from clockwork before backing it up.. not sure if the version of clockwork you used had the ability to backup your 4g keys....
Be careful and if you got the new Evo then I would suggest Amon
Sent from my PC36100 using XDA App
Thank you for the replies. I appreciate you taking time to answer.
The answers have led to a couple of follow-up questions. First, is there any sort of workaround for restoring a Clockworkmod backup onto another device?
Second, I have to admit to no knowledge of the issue of removing a wimax.img file, and, whether or not the version of Clockworkmod I used made a backup of the files.
Thanks again for the help.
GT
garynky said:
Admins,
Sorry, it just hit me that, while I was searching the Development forum for info on ROM Manager and Clockworkmod, I posted my question to the forum also.
Please move to the appropriate forum. My apologies; I obviously was on autopilot when I posted.
Thanks,
GT
Click to expand...
Click to collapse
You have successfully donned the flame retardant armor. No fun in being a jerk now
Sent from my PC36100 using XDA App
neudof said:
Your issue is that your new phone is not the same as your old one. Your backups will not work cross devices.
Sent from my RLS5 Sprint HTC Evo
Click to expand...
Click to collapse
sounds pretty much on the money
garynky said:
I did a search, but, didn't find anything that was quite like my question.
I recently had to return my EVO for warranty work. I was given a new one at the store.
Before I went to the Sprint store, I made a backup using ROM Manager/Clockworkmod that morning. So, I brought my new EVO home, went throught the jailbreak/unlock process, and, installed ROM Manager.
I opened ROM Manager, found the backup I had made, and started the restore process. From all appearances, the restore is going fine. It finishes the process, and I reboot the phone.
At this point, that smooth sailing starts hitting whitecaps. It starts to reboot, but, it never finishes. It's just an endless reboot loop. It will just loop through the intitial reboot screens until the battery is dead. I know, I let it sit that long.
I also had a couple of other, earlier, backups on the SD card. I tried those with the same result. Does anyone have an idea as to why the restore gets stuck in the boot process?
I would really appreciate any help with this. I'm at a loss at this point.
Thanks,
GT
Click to expand...
Click to collapse
More than likely you have different hardware. Clockwork backups will not work on different devices. Backups are device spefic.
Best bet is going to be to unroot, flash stock pc36img. Reroot flash rom of choice (virus Mytouch port ). Youre going to have to start over. That will give you the best chance of success.
Use titanium backup for apps and back contacts to google for if this were to happen again.
Related
This is quite a story I've got here, but just bear with me while I tell it.
Two days ago, I spotted a fps unlock kernel on the Development board here on XDA. I was feeling a bit reckless, so I decided to flash the kernel without doing a Titanium backup. At this point, I was running Fresh 0.5.3. After installing the kernel and rebooting the device, I was greeted with a looping boot animation. Needless to say, I wasn't a happy camper. I flashed every previous version of this kernel, as well as the original kernel, with no success. A Nandroid restore proved to be futile as well. I also tried flashing a fresh copy of the rom onto my phone without doing a complete wipe. No go on that attempt. Finally, I did the stupidest thing I've done with this device and did a complete wipe (data/cache/dalvik,sd:ext), followed by a fresh flash of Fresh (har har). That did the trick. Keep in mind that before performing this last step, I copied the app and app-private folders from my SD card in case of anything.
However, it was then that I realized that my stupid ass had no way of restoring the apps! You see, at least a hundred of the apps on my phone are non-market apk files that would take FAR too long to reflash individually. With that in mind, I installed a bootable version of Ubuntu onto my flash drive, which I used with my netbook in order to access the ext3 partition on my Evo. Afterward, I copied over all of the data from app and app-private onto my SD card. I thought I had finally succeeded in doing something that could have been done so much more easily had I waited to back my **** up previously!
Anyway, that last part occurred about an hour ago. After the files had copied, I exited recovery mode and restarted my phone. I was greeted with the glorious 'FRESSSSHHHHH' boot animation. And then it greeted me again. And again. AND AGAIN AND AGAIN AND AGAIN AND AGAIN RAAARRGH. Anyway, that's where I'm currently at in this whole dilemma. I thought the boot loop meant that the apks in the two app folders were being installed, but an hour is an awfully long time for that to happen.
So now, I am here begging for help from you, the fine people at XDA developers. Is this boot loop animation normal when I've just copied all those files over to the app and app private folder? If not, is there any way to restore my apps without installing them individually through adb or the phone itself?
i don't have fresh, but i use dc 3.2.3 and had a similar issue. i don't honestly remember exactly what i did, but i do know i did a bunch of stuff without backing up and got the boot loop.
here's my thread on it:
http://forum.xda-developers.com/showthread.php?t=722072
i'd link you to the solution we found, but as it's not the exact rom, maybe the troubleshooting steps will resolve your issue. i ended up flashing the engineering build to get access to android, and then flashing dc again to get up to speed.
good luck and let us know how it goes!
shift_ said:
i don't have fresh, but i use dc 3.2.3 and had a similar issue. i don't honestly remember exactly what i did, but i do know i did a bunch of stuff without backing up and got the boot loop.
here's my thread on it:
http://forum.xda-developers.com/showthread.php?t=722072
i'd link you to the solution we found, but as it's not the exact rom, maybe the troubleshooting steps will resolve your issue. i ended up flashing the engineering build to get access to android, and then flashing dc again to get up to speed.
good luck and let us know how it goes!
Click to expand...
Click to collapse
It's not so much fixing the bootloop that I'm worried about. I've already experienced it three times this week, and that can be fixed by wiping the phone clean. What I'm wondering is whether I can install the apps I have backed up by copying over the files from app and app-private
Needless to say, I'll read the thread you linked me to. It might have some useful information .
First off, thanks for all the help so far, this site is the best!
I just rooted my Evo using the unrevoked3. Had a little bit of trouble, nothing major, and overall it was a success. I also installed ROM Manager and Titanium Backup, based on suggestions found here.
The problem is, I'm not quite getting how to flash the roms... I downloaded one through ROM manager, and it seemed to work, but I didn't notice a single thing different. I tried to install CyanogenMod, and it downloaded, but it would always fail during the install.
I tried downloading on my computer, then moving the .zip file to my sdcard. Then I select "install rom from sdcard" and everything seems to go ok, I end up having to go into recovery and "rollback" my phone to the stock rom, because twice now I've almost bricked my phone.
Really, what I'm wanting is a setup like that "Kuma Style" one (without the animal), and a different bootscreen. I have spent a lot of time searching around, and it seems simple enough, I just seem to be missing some integral part of the proccess.....
Any help is appreciated!
Mark_Hardware said:
First off, thanks for all the help so far, this site is the best!
I just rooted my Evo using the unrevoked3. Had a little bit of trouble, nothing major, and overall it was a success. I also installed ROM Manager and Titanium Backup, based on suggestions found here.
The problem is, I'm not quite getting how to flash the roms... I downloaded one through ROM manager, and it seemed to work, but I didn't notice a single thing different. I tried to install CyanogenMod, and it downloaded, but it would always fail during the install.
I tried downloading on my computer, then moving the .zip file to my sdcard. Then I select "install rom from sdcard" and everything seems to go ok, I end up having to go into recovery and "rollback" my phone to the stock rom, because twice now I've almost bricked my phone.
Really, what I'm wanting is a setup like that "Kuma Style" one (without the animal), and a different bootscreen. I have spent a lot of time searching around, and it seems simple enough, I just seem to be missing some integral part of the proccess.....
Any help is appreciated!
Click to expand...
Click to collapse
I am not familiar with Unrevoked, but just running unrevoked doesn't completely root your phone. You need to do the second parts of rooting which unlocks nand.
Ah, so there is more to do. Maybe that's the problem then.... *off in search of how to unlock nand
Mark_Hardware said:
Ah, so there is more to do. Maybe that's the problem then.... *off in search of how to unlock nand
Click to expand...
Click to collapse
Unlocking nand just unlocks something so that you can save full image backups. That wouldn't lead to your phone not installing a ROM right, it's just something you'll want just in case things go wrong. So still finish the root and get nand. But that's not what you're missing here.
Possible error: Did you wipe settings &factory reset and wipe cache in ClockworkMod before flashing the ROM? I think that could lead to some problems.
Try flashing the alternative Amon Ra recovery through rom manager (will state that rom manager won't be fully functional unless clockworkmod is installed) and loading the roms onto the sd card then reboot into recovery. Amon Ra seems to work better imo than clockworkmod. When you're talking about something like "kuma style," those are themes that are usually flashable in recovery also. The boot animation could alse be flashable in recovery but if not, there are instructions on how to adb push custom ones onto your phone.
rugedraw said:
I am not familiar with Unrevoked, but just running unrevoked doesn't completely root your phone. You need to do the second parts of rooting which unlocks nand.
Click to expand...
Click to collapse
just fyi, the latest unrevoked (3.21) unlocks nand so u dont need to do it.
"unrevoked3 will permanently unlock NAND write protection by default on the following phones:
*
Sprint EVO 4G"
i'd link the wiki but i cant cuz i'm a new user lol
Gah! So I downloaded the enamored theme, moved it to the sd card, then went to ROM Manager and selected "Reboot into Recovery"and selected the enamored.zip. It said the install was a success, but when I rebooted, the phone stuck on the bootanimation. I tried restarting a couple times, but it always gets stuck in the same place.
I booted into recovery (if thats waht you call the hold the volume button down while pushing the power button trick), and selected recover, then nandroid, then a time under yesterdays date. Phone recovered fine.
WtH am I doing wrong? I realize I am way out of my league, but I'm not completely retarded. Again, GAH!
Are u wiping data and cache when flashing a ROM? I have been stuck at the CM6 boot animation when coming from a different Rom and not wiping.
Sent from my PC36100 using XDA App
Mark_Hardware said:
Gah! So I downloaded the enamored theme, moved it to the sd card, then went to ROM Manager and selected "Reboot into Recovery"and selected the enamored.zip. It said the install was a success, but when I rebooted, the phone stuck on the bootanimation. I tried restarting a couple times, but it always gets stuck in the same place.
I booted into recovery (if thats waht you call the hold the volume button down while pushing the power button trick), and selected recover, then nandroid, then a time under yesterdays date. Phone recovered fine.
WtH am I doing wrong? I realize I am way out of my league, but I'm not completely retarded. Again, GAH!
Click to expand...
Click to collapse
When you flash a theme, it could take up to 2-5 minutes to finish. This occurs during the boot animation. I flash themes all the time and I notice it's usually around 2-3 minutes wait. Maybe faster for others but that's just been my experience. If it's over 5 minutes than there's probably something wrong with your zip file or maybe clockworkmod recovery doesn't flash it properly. Also, it could be an issue with the kernel you're using...I noticed on kingklick cfs #10, I was stuck on boot animation for about 7 minutes and so I reverted back to the stock kernel and the theme was applied within 3 minutes.
ok, apparently I've been missing that step...
where do I do that again?
mizzos4 said:
When you flash a theme, it could take up to 2-5 minutes to finish. This occurs during the boot animation. I flash themes all the time and I notice it's usually around 2-3 minutes wait. Maybe faster for others but that's just been my experience. If it's over 5 minutes than there's probably something wrong with your zip file or maybe clockworkmod recovery doesn't flash it properly.
Click to expand...
Click to collapse
I waited a good long time. Am I at least headed in the right direction? Sorry to sound whiny, it's just that there's a few little things I want to do, and I'm intimidated as hell by actually doing any command line, so I'm hoping to avoid that- aka riding someone else's coattails
First, which rom are you using and is it stock or custom kernel? Are you using clockworkmod recovery? Try flashing the alternative amon ra recovery in rom manager then boot into recovery and apply your selected theme.
if you are using a stock rom it must say stock 2.2 deodexed
if it is not a deodexed rom.. of any kind.. then themes will say they flashed but they will either brick your phone or not work at all.
and stop using clockwork.... just use amon ra
Sent from my PC36100 using XDA App
I could be way off here, but I've seen some people who rooted using unrevoked, and run into trouble flashing things (or maybe I'm thinking of trouble with terminal commands) and it turned out they couldn't find flash_image anywhere in there SD card, Which should be installed (someone please correct me if I'm wrong).
I saw a lot of reports of this in chainsDDs superuser thread, if I remember correctly. They had to install flash_image.img (which is a file available on toasts part 2 root tutorial)
I obviously could be wrong about this, I've never used unrevoked, I rooted via toast, and his method included everything.
@ V_lestat
Thanks for the heads up about themes having the ability to brick your phone if not deodexed, I never knew that. I flash roms and kernels a lotbut never messed with themes much.
At OP, have a look at virus Rom thread. It's a great ROM, and he has built some different themes to go with it. Beautiful stuff, great ROM, great thread.
Good luck
Sent from my PC36100 using XDA App
See, some people say use clockwork, some people say Amon.
I looked around a lot beforehand, and people kept saying to use unrevoked, so I did. Now people say I should have used Toast?
Thanks for everybodies help so far, I am reading everything and taking it all in.
I Don't Mean to add any Confusion to your situation. I am new to this also.. I went with unrevoked also and when I booted into recovery with clockwork mod. I did a nand back up first to make sure if anything went wrong I could just boot back into recovery and load my backup. Then I wiped my Data & Davlick Cache all of the caches. Then I installed my Rom and it worked like a charm. I will add it did take about 5 to 7 mins to boot only on the first time though. I hope that helps some as to the process and what to do first don't give up XDA rocks with the smartest mind on the planet.
Mark_Hardware said:
ok, apparently I've been missing that step...
where do I do that again?
Click to expand...
Click to collapse
If you are using ROM Manager to "install zip from card" it presents you with a dialog with two unchecked check boxes. One of them is "wipe data + cache". make sure you check it before hitting ok on that dialog.
If you are manually booting into recovery then in the recovery choices you will see one that says wipe data and one thats says wipe davlik cache. first do a nandroid back up then wipe those data and davlik then install the rom. By the way are you just installing a theme or a full rom that might be the issue i am just wondering maybe a senior member can help on wether you can install a theme over a rooted stock theme or not?
Success!
I went into ROM Manager, backed up current ROM, went into recovery manually, wiped the cache, then installed from zip, and it worked! I tried a cool theme I found, and I like it, but it seemed old. I just installed fresh, and the enamored theme, and all is working great!
A couple more questions,
1) how do I get my contacts back?
2) How do I get my apps back onto my phone? I have them backed up on appbrain, but I haven't been able to find how to get them back to the phone.
So far, I've tried a couple of ROM's (and/or themes) and I've ended up flashing back to my own "safe" one, until I figure these two things out.
A tremendous thanks to everyones help! I seriously couldn't have done it without you guys
Edit; Oh yeah, one other thing. How do I delete the other nand backups? There's like 5, and I need to free up some memory. I tried going in and selecting one to see if it gave me the option to delete, but I didn't see anywhere that it did.... Got it. Search feature to the rescue
Hey everyone.
I know there's a couple other threads with this problem, but none of them included their last_kmsg files. It took a bunch of tries before I could stay booted up long enough to grab it, but I have one.
I'm getting a significant number of reboots on my EVO. Like almost unusable at times. It seems fairly random, although there's a slight suspicion is has something to do with the GPS. Maps has been a crash-cause before and the most recent bout last night was brought on by foursquare. (the annoying part is I had just used 4sq fine 30 minutes prior with no issues. Then, booted it up, refreshed locations and my phone was unusable for hours.)
I've done all the standard things. Fix permissions, wipe cache, wipe dalvik, wipe data/system, reinstall the latest CM7 build (update-cm-7.0.2.1-Supersonic-signed.zip), wipe cache, wipe dalvik. I entered my google account info but told it not to sync anything. It is now rebooting less than a minute after it starts up. I haven't installed any apps at all since this most recent wipe/reload of CM7. It reboots with and without the sd card installed.
I'm at a loss here and getting incredibly frustrated. Many replies say it's as easy to fix as wipe everything and re-do it. Obviously something abnormal is screwed up on my phone and I can't figure it out.
Here's the pastebin from this morning: pastebin.com/Ki7H8bH3 (Crap, I don't post here enough to be allowed to post links. Just add the http part to that.)
And then when I got awake enough, I did another complete wipe/reload. The rebooting is even worse now, it's taken me almost an hour to get to a point I can install es explorer to try and pull another file. And when I did, it was blank.
Any ideas?
Thanks!
1. Go to the link below and download the PC36IMG.zip file for amon RA v2.3 and place it on the root of your SD card.
http://forum.xda-developers.com/showthread.php?t=705026
2. Shutdown your device.
3. Simultaneously press the DOWN volume button and the power button until your device starts. There will be a short pause and then a few lines of text will scroll across the screen. Afterwards, the bootloader will automatically detect the PC36IMG.zip file and prompt you to install it. Follow the easy prompts to install. Installation will take less than 10 seconds to complete. Afterwards, reboot into your new recovery. Go to the backup/restore menu and make a nandroid backup of your current setup.
4. Now go to the wipe menu and wipe EVERYTHING in it EXCEPT the SD card.
5. Go to the flash menu and flash the rom you desire to flash.
On many occasions, reflashing the recovery solved rebooting issues and hopefully, it will solve yours.
posting & replying via the XDA Premium app.
Hi dougjamal,
Thanks for the reply.
I've made some progress. Last night I had done a majority of what you suggested, with installing amon RA. I've also just formatted my entire sd card just to be sure.
I haven't tried wiping things other than cache and dalvik, so I'll try that.
My progress I mentioned is that I had CM7 up and running until I flashed a new kernel and gapps in there. So I guess I'll just stick with the stock CM7 kernel, try your extra wiping and see how that works.
Thanks!
grifta67 said:
Hi dougjamal,
Thanks for the reply.
I've made some progress. Last night I had done a majority of what you suggested, with installing amon RA. I've also just formatted my entire sd card just to be sure.
I haven't tried wiping things other than cache and dalvik, so I'll try that.
My progress I mentioned is that I had CM7 up and running until I flashed a new kernel and gapps in there. So I guess I'll just stick with the stock CM7 kernel, try your extra wiping and see how that works.
Thanks!
Click to expand...
Click to collapse
You're very welcome. Sorry for the delayed response. I was having a late lunch and then drove home. Anyway, keep us informed of your progress and enjoy the rest of your day.
posting & replying via the XDA Premium app.
No worried on any delay, just glad to have someone that took a read and time to reply!
Ugh, it's the randomness of this that has me so frustrated. I thought I had a good install again, I left it sit on the "touch the android" screen for a few minutes and it stayed on. Made it through the setup process ok. I allowed the setup to "auto-download" a handful of the google apps it asks if you want. Once they got to about 38%... boom, restart.
So I did another toooootal wipe and I'll manually install those apps one by one. We'll see...
dougjamal said:
1. Go to the link below and download the PC36IMG.zip file for amon RA v2.3 and place it on the root of your SD card.
http://forum.xda-developers.com/showthread.php?t=705026
2. Shutdown your device.
3. Simultaneously press the DOWN volume button and the power button until your device starts. There will be a short pause and then a few lines of text will scroll across the screen. Afterwards, the bootloader will automatically detect the PC36IMG.zip file and prompt you to install it. Follow the easy prompts to install. Installation will take less than 10 seconds to complete. Afterwards, reboot into your new recovery. Go to the backup/restore menu and make a nandroid backup of your current setup.
4. Now go to the wipe menu and wipe EVERYTHING in it EXCEPT the SD card.
5. Go to the flash menu and flash the rom you desire to flash.
On many occasions, reflashing the recovery solved rebooting issues and hopefully, it will solve yours.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
Seems like this gets posted quite often, huh??? lol
Don't rule out a corrupt download. If you have the time, download both Salvage-Mod 1.2.1 and the gapps zip from http://www.salvage-mod.com/node/4. If you like CM7, you may like Salvage-Mod. It is pure gingerbread. If you decide to flash it, see whether or not you get bootloops with it.
posting & replying via the XDA Premium app.
HipKat said:
Seems like this gets posted quite often, huh??? lol
Click to expand...
Click to collapse
Indeed, my friend...lol...but it works.
posting & replying via the XDA Premium app.
HipKat said:
Seems like this gets posted quite often, huh??? lol
Click to expand...
Click to collapse
It does and it wish it was that easy. It's frustrating to read that others seem to have no issues at all yet when I follow those directions, which are everywhere, nothing seems to work.
dougjamal said:
Don't rule out a corrupt download. If you have the time, download both Salvage-Mod 1.2.1 and the gapps zip from http://www.salvage-mod.com/node/4. If you like CM7, you may like Salvage-Mod. It is pure gingerbread. If you decide to flash it, see whether or not you get bootloops with it.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
I re-downloaded CM7 this morning thinking that might be the issue, but it hasn't seemed to help. I'll give a different rom a try probably, maybe there's something other than CM7 I'd be content with.
Whelp, I downloaded SalvageMod and their gapps. Wiped everything, installed salvage, installed gapps, rebooted.
I got through set-up, was ok for a couple minutes, then as I was going into my contacts to see if they had sync'd yet... reboot.
This makes me think this can't be a ROM issue.
Any other ideas?
Does the same thing happen when you run a stock (or close-to-stock) rom? Main reason I ask is that this might actually be some sort of hardware problem, but one of the best ways to test for that is to be running on stock software. I wouldn't necessarily suggest flashing an RUU to get to the latest official release, but there are stock rooted roms out there that you could try.
You probably went with CM specifically to get away from Sense and the default HTC stuff (that's most people's reasons anyway), but if you flash a stock rom and it's still rebooting like that then I'd say chances are REALLY good that it's hardware and that you'd have grounds for getting a replacement phone (just remember to unroot first.)
And if it stops randomly rebooting on you then you'll have at least narrowed things down a bit.
jesuspgt said:
Does the same thing happen when you run a stock (or close-to-stock) rom? Main reason I ask is that this might actually be some sort of hardware problem, but one of the best ways to test for that is to be running on stock software. I wouldn't necessarily suggest flashing an RUU to get to the latest official release, but there are stock rooted roms out there that you could try.
You probably went with CM specifically to get away from Sense and the default HTC stuff (that's most people's reasons anyway), but if you flash a stock rom and it's still rebooting like that then I'd say chances are REALLY good that it's hardware and that you'd have grounds for getting a replacement phone (just remember to unroot first.)
And if it stops randomly rebooting on you then you'll have at least narrowed things down a bit.
Click to expand...
Click to collapse
Hey jesuspgt,
I haven't tried that yet. I'll look around for a rooted stock ROM later and give that a shot.
My current status is back to uncertainty. At the moment, my evo has been sitting here fine, not rebooting, for the past hour or two. It's still the Salvage ROM I first installed (i.e. I haven't reinstalled it since it rebooted). Now I haven't really used it any, so it might go to hell as soon as I do that, but for now, it's on and only had that one (maybe two, I can't keep track...) initial reboot.
That's what makes it tricky to diagnose. I know using any custom ROM runs the risk of loosing stability and all ROMs probably produce a reboot here and there. Tough to tell if it's just a "comes with the territory" type of reboot or an actual problem.
Even though I'm sure there's some CM features I'll miss, maybe Salvage is my answer.
Thanks!
*sigh* Well I decided to try using some apps and guess what... reboot.
All I was doing was trying to play a game of Androminion, which is about as basic and not-tasking as possible, so I can't imagine that's what crashed things.
The only thing I can think of that you *may* need to do is reflash your hboot and/or your baseband, PRI & NV from within recovery. You can download it from the link below.
http://forum.xda-developers.com/showthread.php?t=715485
posting & replying via the XDA Premium app.
dougjamal said:
The only thing I can think of that you *may* need to do is reflash your hboot and/or your baseband, PRI & NV from within recovery. You can download it from the link below.
http://forum.xda-developers.com/showthread.php?t=715485
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
Excellent, I'm going to try that. My hboot is still 0.93!
Hey dougjamal,
Just wanted to drop an update. I know how annoying it is to help someone out and never hear how things ended up!
Who knows what combo helped, but I'm fairly stable now. After updating my hboot, I flashed to Sprint Lovers, did the ##GPSCLRX# trick and then flashed to the latest nightly of CM7 (63 I believe). Only one or two crashes and one bootloop since then.
Of course, as luck would have it, a new problem showed up in the form of a dead spot on my touch screen. Right about where the "Clear" button is for notifications, that entire strip across the phone won't respond to touch. I was hoping it was a nightly issue, but I switched to a different rom and the issue was still there. Looks like it's going in for a warranty claim after-all!
Thanks for all your help
-grifta67
Ok... here's the deal. I just decided to switch roms finally to see what is new out there. I had been running an old version of Uber Kingdom. Here is the problem I am having. It is boot looping. Relatively simple problem to fix usually. But wait, there's more! It is boot looping in every single rom I install. Sometimes it won't boot to clockwork properly either and I have to pull the battery. Is there someway I can fix this? Or is this a hardware problem (which I kind of doubt)? I just don't understand what the heck is going on. I have been flashing different roms left and right for the past few hours trying to get this thing to stabilize. Sometimes it will boot up into the rom, I will get mostly through the google accounts setup, and then it will restart, and then loop. Other times it won't even get past the white incredible screen, and then sometimes it will make it into the rom splash screen. I have attempted to install CM7 nightly, Uber kingdom, and Synergy so far. I can flash the new rom, I can mount the SD card in clockwork, but then it begins to loop again as soon as I leave clockwork.
Let me know if you need any other information.
Is there a way to just completely redo EVERYTHING, clockwork, rom, everything, just to make sure I have a nice clean slate?
Thanks a ton for reading through this novel. I am extremely frustrated.
~Will
PS, I may not get back to this thread until morning. I have to get to sleep for work. Sorry if I don't respond right away to information requests. Thanks again!
If you can mount the SD card, download the stock RUU from www.dougpiston.com, put it on the root of the SD card named exactly PB31IMG.zip, and boot into hboot to install it. Your phone should be restored to stock, a clean slate.
Tried a different SD?
Sent from my ADR6300 using XDA Premium App
How are you downloading and flashing the ROM? I had this problem when trying to do everything through Rom Manager. Even trying to flash in recovery with a ROM downloaded through ROM Manager would loop.
Update
Well, I was just getting ready to flash the original RUU when I tried one last time to restore my old Uber rom setup and it worked (whereas the last 3 times of doing exactly the same process didn't). It stopped looping at least, even though I am still running the same rom I was before. I think tonight I am still going to attempt to flash the RUU anyway and start over anew.
To answer the questions before, No, I did not try a different SD. I didn't know it could make that much difference. Still on the original one that came with the phone.
As the downloading and flashing process goes, I was downloading direct from the XDA forums on my laptop, then transferring the files via USB. I have never really liked using the Rom Manager. It cuts me out of the XDA loop and I don't get to see all the bleeding edge discussions, etc...
So I will try to flash everything new tonight, and then post my results for anyone who is curious. Thanks for the help guys!
Hello,
Last night I rooted my device using this (http://forum.xda-developers.com/showthread.php?t=1265429) method and file from zedomax and everything worked great except when I booted my device there was a yellow triangle with a black “!” in it. I figured that just indicated the device was rooted or running a 3rd party kernel so I didn’t worry about it.
Today I launched my camera app and it failed to load the interface but showed the image from the camera momentary then crashed back to the home screen. I restarted my device and when the device restarted it was very slow and unresponsive and after unlocking it my live wallpaper was gone replaced with the last background I used before selecting a live background a couple weeks back. No icons or widgets loaded and I am unable to open the settings tray. The only things I am able to do with the phone is pull down the notification bar, respond to text messages, adjust the volume and hold power to restart the phone. All of which are very slow and delayed.
When I connect the device to my computer windows is no longer able to load the drivers and Kies is unable to connect with the device. I am not sure what caused this or how to resolve this issue so any advice or known fixes would be fantastic! I am unable to get to clockwork mod to restore my backup and I am unable to get to Kies or the phone settings to do a factory reset so I really don’t know what to do they were supposed to be a last resort and now I don’t even think I can do them. I am an experienced techie but I am new to android and this is the first device I have rooted so any advice would be great no matter how basic it may be.
UPDATE: I just connected the phone via USB to my laptop at work and it was able to discover and install everything it needed to connect with the phone. I am installing Kies now so at least there is hope of a factory restore, although I really hope it doesn't come to that!
Boot into download mode and flash the stock eg30 tar file from crawrj.
Sent From My Evo Killer!!!
Thanks Already started doing that waiting for it to download now
Still no touchwiz... great!
Try flashing a stock rom via clockworkmod.
efarley said:
Still no touchwiz... great!
Click to expand...
Click to collapse
You can root again and restore your backup, or go to this website www.lostandtired.com (midnight roms blog) click on android development and download and flash the sprint bloat and TW restore zip. Hope that helps.
I flashed the stock rom which didn't change anything so then I used clockworkMod to do a factory reset which ended up trapping me into a boot loop. I could use Odin to flash new roms but the device would never go past the 4G logo
I ended up taking the device back to Best Buy and since the loading screen showed the stock rom and they couldn't get past the 4G logo I just had to say it wasn't rooted and they gave me a new one.
I would love to know if anyone has any idea of what went wrong here so that I can feel comfortable rooting again. Also if anyone has some basic articles handy that teach basics of rooting that would be great, I didn't even know about clockwork mod until after I had this problem so knowing things like that earlier would have helped a lot I think. I'll be spending the weekend looking up everything I can find on the subject so any reading you guys can suggest would be fantastic.
efarley said:
I flashed the stock rom which didn't change anything so then I used clockworkMod to do a factory reset which ended up trapping me into a boot loop. I could use Odin to flash new roms but the device would never go past the 4G logo
I ended up taking the device back to Best Buy and since the loading screen showed the stock rom and they couldn't get past the 4G logo I just had to say it wasn't rooted and they gave me a new one.
I would love to know if anyone has any idea of what went wrong here so that I can feel comfortable rooting again. Also if anyone has some basic articles handy that teach basics of rooting that would be great, I didn't even know about clockwork mod until after I had this problem so knowing things like that earlier would have helped a lot I think. I'll be spending the weekend looking up everything I can find on the subject so any reading you guys can suggest would be fantastic.
Click to expand...
Click to collapse
If you a clockwork and "stock rom" you were still rooted...Doing a factory reset will send you into bootloop when rooted. Trying to flash other roms on a bootloop is not going to work. You need to have grabbed a backup such as Zedo has on his post and put the backup in clockwork folder on your phone. Then flash that in CWM. Would of brought you out of bootloop to a stock rom with his kernal. Now you can flash Roms and kernals or could of flashed crawf or anyone else FULL stock rom and been back to stock kernel and rom and not rooted.
dallastx said:
If you a clockwork and "stock rom" you were still rooted...Doing a factory reset will send you into bootloop when rooted. Trying to flash other roms on a bootloop is not going to work. You need to have grabbed a backup such as Zedo has on his post and put the backup in clockwork folder on your phone. Then flash that in CWM. Would of brought you out of bootloop to a stock rom with his kernal. Now you can flash Roms and kernals or could of flashed crawf or anyone else FULL stock rom and been back to stock kernel and rom and not rooted.
Click to expand...
Click to collapse
Ohhhh that's what happened! Awesome thanks. I will be much better prepared with backups out the wazoo this time haha.
Now if only I could figure out why Touchwiz died in the first place hmmm....
I hope you can figure it out, just postin here to say that when I saw this thread, it reminded me of the thread over in the EVO forums about the guy who claimed that sprint removed his Sense from his phone.
Khilbron said:
I hope you can figure it out, just postin here to say that when I saw this thread, it reminded me of the thread over in the EVO forums about the guy who claimed that sprint removed his Sense from his phone.
Click to expand...
Click to collapse
haha SPRINT removed it?! So that person thinks sprint monitors every device and has a team of techies on staff to hack your phone and brick it if you break their rules?... yeah that totally makes more sense than a file got corrupted when you were messing with the kernel.. some people maybe shouldn't be rooting their devices in the first place haha