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 .
Hi,
I have a HTC Desire and just after I got it I managed to muddle through unbranding it to get rid of the Vodafone addons. At the same time I managed to root it.
I recently decided to take the jump and try some of the non stock ROMs as that's one of the reasons I went for Android.
I have to say there are some great tools out there and my sincere thanks to the developers, namely:
o AlphaRev
o ClockworkMod
o ROM Manager
o unrevoked
Wow nandroid is a real bare metal restore that works ))
When I decided to take the plunge I went through the recommended approach detailed elsewhere in this forum.
I've so far tried LeeDroid, Oxygen & Defrost.
I now have a slight problem that seems (perception) to be getting worse.
In summary, if I reboot into recovery (either power/back or ROM Manager) it sometimes works and more often now doesn't work. When it fails it just hangs at the AlphaRev screen, just a boot screen I guess. When it hangs it never recovers, battery out and try again, again, again .... then it'll work.
Does anyone have any thoughts on this boot into recovery issue ?
Colin
~~~~~~~~~~~~~~~~~~~
HTC Desire
AlphaRev S-OFF
Radio 32.49.00.32U_5.11.05.27
ROM currently Defrost (still trying the various flavours)
This is the issue, people get a brand new shiny phone and the first thing they do - as opposed to actually USING the thing - is find as many ways to bodge it as possible...
People need to actually read everything, take some time to absorb it and then read it again. Then use the phone as chances are unless they're a real app whore they'll never need to worry about internal space...
I've no idea why you're having issues but I assume you don't have a copy of the RUU your Desire originally came with so should you need to return to stock you can?? this is the first thing anyone should do before undertaking any type of customising and would save a lot of headaches
Hmm,
Not quite valid. I've had the phone for a few months now. I originally wanted to get rid of the Vodafone crap as that's caused me issues in the past with other phones, albeit not Android based. At the same time I wanted to go to Froyo which was on the never/never from Vodafone at the time. Again upgrading phones in the past has caused more issues when it's been used for a while.
I work in the IT sector and have dual boot on my laptop (XP & Ubuntu) as they do different things in different environments, so I'm used different look/feel/behaviour. I wanted to try some of the non HTC Sense ROMs, a couple of things bugged me a bit and after all you can try in the Android environment. That after all is the beauty of an Open System as opposed to a closed environment, e.g. Nokia Symbian, M$ Windows.
My only issue I have at the moment seems to be the tempremental behaviour of getting into recovery.
BTW I have a copy of the stock ROM but have no intention of ever going back to a Vodafone branded pre-froyo Android environment.
When I rooted, installed S-OFF, ClockworkMd, ..... I fully accepted the risks and knew that if I bricked the phone, it'd be my fault.
Regards
Colin
how bout reflashing recovery?
gol_n_dal said:
Hmm,
Not quite valid. I've had the phone for a few months now. I originally wanted to get rid of the Vodafone crap as that's caused me issues in the past with other phones, albeit not Android based. At the same time I wanted to go to Froyo which was on the never/never from Vodafone at the time. Again upgrading phones in the past has caused more issues when it's been used for a while.
I work in the IT sector and have dual boot on my laptop (XP & Ubuntu) as they do different things in different environments, so I'm used different look/feel/behaviour. I wanted to try some of the non HTC Sense ROMs, a couple of things bugged me a bit and after all you can try in the Android environment. That after all is the beauty of an Open System as opposed to a closed environment, e.g. Nokia Symbian, M$ Windows.
My only issue I have at the moment seems to be the tempremental behaviour of getting into recovery.
BTW I have a copy of the stock ROM but have no intention of ever going back to a Vodafone branded pre-froyo Android environment.
When I rooted, installed S-OFF, ClockworkMd, ..... I fully accepted the risks and knew that if I bricked the phone, it'd be my fault.
Regards
Colin
Click to expand...
Click to collapse
I didn't mean it as a flame btw, just that so many people come on here and blindly follow everyone else without actually realising what they're doing
>> I didn't mean it as a flame btw, just that so many people come on here and blindly follow everyone else without actually realising what they're doing
NP,
I get it all the time having to "help" people who tried things on their Home PCs or TVs, BluRay, HDMI inerconnect, ..... Shops offer bloody useless help to them. ;-)))
>> how bout reflashing recovery?
Yes, I've tried reflashing ClockworkMod through ROM Manager, it's currently 2.5.0.7 confirm by ROM manager and when it finally gets into recovery.
It just seems an intemittent issue that only arises when I want to do a Nandroid backup or "play" with the ROMs / Radio etc. The only solution I have is to remove the battery, count to 3 and re-insert it. Then try again.
It's not a show stopper just a real pain, especially when installing a new ROM/Radio when it's supposed to reboot. It's a case of how long do I leave it and hope it recovers to sod it, battery out and pray it's not bricked as a result.
Regards
Colin
Wellp. I win.
I win a no expenses paid trip to my nearest Sprint dealer.
Ever since I used unrevoked to root my phone in November, I've been voraciously digging through these forums for tasty roms. I've been snorting lines of Cyanogen, MIUI, and a myriad of other, well-designed roms.
Using a on older version of hboot (pre 1 methinks) I was able to avoid the latest hassles with ClockworkMod (plus, I down(up?)graded to 2.6 via RomManager).
Tonight, as I was enjoying some tasty foodstuffs at my local foodstuff vendor, my phone rebooted. Then, it rebooted again. Then again. I once made the folly of flashing a new rom without running the appropriate wipes, and was no stranger to the bootloop. I patiently fired up hboot (my poor volume rocker is all but wore out) and ordered up the trusty recovery mode.
...then it rebooted again... and again... and again.
PusSidiasus: ONOES! I HAVE THE WTFBBRICKED MY PRECIOUS!
SmartAsSidiasus: Hang on for a second, let's check the internet. Try this link: tinyurl.com/4vgeyeg
PusSidiasus: ...
Unfortunately, my internal dialogues are not nearly as witty. Also, my best attempts to de-brick-ify were for naught. Fastboot gave some wacky error message when I tried to flash a new recovery, and installing via PC36IMG.zip did nothing to improve the situation. I even went so far as to install a stock image someone pulled from an RUU (with a 2.02hboot, so as to avoid wimax woes)...
Still, a whole lotta nothing. I can't do anything beyond hboot, and whatever recovery image I install (Clockworkmod, AmanRa) the machine still bootloops.
At this juncture, I've resigned to taking the phone into the sprint store and playing dumb. It is a stock rom, though I hope the attendant misses the S-OFF bit at boot. Which brings me to my proper question:
1) Has anyone run aground a similar issue and found a way out?
OR...
2) Anyone know how to turn S-(back)ON in my current situation?
Any insight would be greatly appreciated. Also, you can rest assured that I'll be rooting again whatever phone I walk away with, and the work that is exhibited in these forums is amazing. Keep churning out wonderful roms and guides.
Sidiasus
(Currently, Sadiasus... )
First...... Wrong subforum. Try Q and A.
Second, in all your rom flashing, did you maybe forget to wipe, and re-wipe before your rom install?
Ah piss. I'll move subforums. Also, the last flash I ran (from Evervolv Gingerbread -> MIUI 1.1.07) I am quite certain I wiped. I may be mistaken, but non-wiped user data shouldn't bork recovery.
Happened to me when trying to root my brothers Evo. (Already had mine rooted). I thought the phone was bricked because there was no recovery installed and all that worked was hboot. I tried several different versions of PC36IMG.zip until 1 finally worked.
Cheers
Yes! try updating with PCM36IMG.zip ROm that should help you out, ex "Sprint lovers". Good luck.
sidiasus said:
Ah piss. I'll move subforums. Also, the last flash I ran (from Evervolv Gingerbread -> MIUI 1.1.07) I am quite certain I wiped. I may be mistaken, but non-wiped user data shouldn't bork recovery.
Click to expand...
Click to collapse
Recovery thing confused me a little bit. I didnt get in your post where that became a problem. If a phone bootloops all on its own, its usually due to wiping either not being done, or a certain recovery not wiping it correctly. At least that's what ive seen in all my reading. Hope you get this ironed out.
Mikedick said:
Recovery thing confused me a little bit. I didnt get in your post where that became a problem. If a phone bootloops all on its own, its usually due to wiping either not being done, or a certain recovery not wiping it correctly. At least that's what ive seen in all my reading. Hope you get this ironed out.
Click to expand...
Click to collapse
No problem, I tried to write in a more humorous style than the other "HALP" threads, and my ability to clearly relate the important details suffered. Thanks for the good wishes!
Etiquette question: I've duplicated this thread in Q & A, should I just delete this one?
Also, thanks to all for the lightning fast responses, trying more PC36IMG'ses.
Nah, just let it die.
Found like you're radio fried, it's a well known defect on some evos and incredibles. Try to put it in the fridge while turned off and afterward it may run for long enough to turn s-on.
Sent from my PC36100 using XDA App
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.
I'm relatively new to this ROM flashing business and, before I flash my first custom ROM, I have three quick questions that I would be very grateful if one of you more advanced developers could answer.
1. Is it possible to return to the stock ROM (or on the DInc, HTC Sense) without unrooting, or would I have to unroot and reroot?
2. What is the possibility of bricking my phone? I have seen a lot of warnings about bricking, but what is the actual probability that this will happen?
3. By using Titanium Backup, how much am I actually backing up and how much will I have to do myself to re-customize my phone?
Thank you.
1) Yes, by backing prior to your first flash you can always revert back to your backup. You could also download a stock rom and flash to that as another method of returning to stock.
2) Bricking and reading information on flashing have an inverse relationship a.k.a the more you read the less likely you brick and the less you read the more likely you brick. If you use that thing called google you will almost certainly not brick your device.
3) Not sure I can answer this one as I don't use titanium for anything. To get my phone back to the point I had it after each flash I only need to spend about 5 mins tweaking CPU, voltage and placing my clock widget where I want it. Google handles apps and contacts so that isn't a problem. You can backup your messages and what not with numerous programs. Customization can become endless i.e. themes, display tweaks etc but I don't really know how far into that you have gone.
You can follow my step-by-step tutorial, found here-Rooting Droid Incredible- for a very easy way to root.
Backup stock rom first. Don't be like me.
Where's ma rosie at?
I flashed the Optimized Shift ROM, and everything worked very well. However, I do have one more question - a patch for the ROM was posted today, and how do I install that? Do I just flash it like a normal ROM, or do I do something else?
The dev (newtoroot) should have said whether it was something you could flash over or do a full wipe (like before first installing a rom). You just flash the updated version like you did initially.
Whenever I try to restore to my backup of stock Sense/Froyo, my phone gets stuck on the white "HTC Incredible" screen, and I have to take out the battery and reboot into Optimized Sense. Because of this, it appears I may be stuck in a custom ROM. Is there anything I can do?
teentech said:
Whenever I try to restore to my backup of stock Sense/Froyo, my phone gets stuck on the white "HTC Incredible" screen, and I have to take out the battery and reboot into Optimized Sense. Because of this, it appears I may be stuck in a custom ROM. Is there anything I can do?
Click to expand...
Click to collapse
Make sure you do a full wipe, the same thing you'd do before flashing a new ROM, and then restore the backup.
RMarkwald said:
Make sure you do a full wipe, the same thing you'd do before flashing a new ROM, and then restore the backup.
Click to expand...
Click to collapse
Thank you. Unfortunately, I just tried that, and it once again wouldn't boot up. Is there anything else I can do?