Related
So i got this lovely update from Verizon. I rooted using the one touch but never made any changes to the phone. Still using default UI etc. Just rooted to access saves, overclocking.
So the update reboots the phone, starts installing, and fails. Then i can go to the menu and reboot the phone. It will come all the way on, and immediately just shuts down and tried the update again. Stuck in this vicious cycle. Help?
Mount the SD card either in recovery or on a PC and see if there is a PG05IMG.zip on it. Remove it if so, then reboot.
tqhx said:
So i got this lovely update from Verizon. I rooted using the one touch but never made any changes to the phone. Still using default UI etc. Just rooted to access saves, overclocking.
So the update reboots the phone, starts installing, and fails. Then i can go to the menu and reboot the phone. It will come all the way on, and immediately just shuts down and tried the update again. Stuck in this vicious cycle. Help?
Click to expand...
Click to collapse
You can't install an OTA if your rooted, even if you haven't made any changes. The problem is the custom recovery (e.g. ClockworkMod)
When the update tries to install the updated recovery, it sees that the old stock recovery isn't there, and fails.
As far as recovering from that, I'm not entirely sure.
Seeing as you used the one touch root, I doubt you installed the S-Off eng bootloader. Try what the above poster suggested first.
Thanks for the replies guys. I did have s-off, but yeah ill tell you i tried what he suggested with no luck.
I ended up being ok i made another clockwork backup, did a full restore from a backup before the date of the update, then did just a data restore from the backup i had just made. Phone is back to normal. Thanks for the responses, ill give you both marks for being helpful
I'm in the same boat, except I was silly enough to not have a backup made. I do not see the PG05IMG.zip from recovery. Any other possible ways to fix this? If I have to clear all my data and start again, I'm ok with that though I'd obviously prefer not to do that.
Boot into clockwork recovery and wipe cache only.
Sent from my HTC Thunderbolt
This same issue has happened to me with the Verizon update. Long story on how it i clicked okay to the update. I told it reject at least 3 times already.
Anyway - i was stuck in this nasty reboot cycle. I was lucky to have a backup from March when I first rooted my TB. Not having a more recent backup is my bad.
So I have worked most of today with near factory settings from my recovered backup and now I am restoring todays backup to see if I can fix this reboot BS.
I did the Wipe Cache from ClockMod and when the phone rebooted it gave the prompt to reinstall the update which I cancelled. So success!!! Now I can clean up my junk apps and do a proper backup to protect myself in the future.
I have a Samsung Transform Ultra (rooted), I am using the stock ROM that came with the phone, recently I have corrupted something and need to attempt a factory reset, however some people have said that doing a factory reset on a rooted phone could brick it, so this brings a couple of questions:
1.- How would I un-root my phone, or, if un-rooting is not necessary, what steps should I take to factory reset it safely? My data is safely backed up already.
2.- Has anyone done a factory reset on a rooted Transform Ultra?
Any help would be most appreciated.
The4thDoctor said:
I have a Samsung Transform Ultra (rooted), I am using the stock ROM that came with the phone, recently I have corrupted something and need to attempt a factory reset, however some people have said that doing a factory reset on a rooted phone could brick it, so this brings a couple of questions:
1.- How would I un-root my phone, or, if un-rooting is not necessary, what steps should I take to factory reset it safely? My data is safely backed up already.
2.- Has anyone done a factory reset on a rooted Transform Ultra?
Any help would be most appreciated.
Click to expand...
Click to collapse
Don't you have a custom Recovery installed? I don't know about this device specifically, but there should be a factory reset option you can utilize within your Recovery image. You'll need a ROM to flash afterwards also, otherwise you'll have no OS on your device. Or simply flash a NANDroid backup.
Sent from my HTC Vision using XDA App
Since my (rooted) phone has the stock factory ROM only, and I never changed it, do I still need a ROM? My original ROM was never removed or changed.
The4thDoctor said:
Since my (rooted) phone has the stock factory ROM only, and I never changed it, do I still need a ROM? My original ROM was never removed or changed.
Click to expand...
Click to collapse
Well that's the thing, when you factory reset a rooted phone it wipes everything, including the OS. So after a factory reset there will be no ROM to boot into. Even though you've never changed it and you're running stock, you'd still need a copy of that stock ROM (if you wanted to continue running stock). But if you've made a nandroid backup (complete snapshot of your entire system) at some point before you noticed the current problem you're having, it might be easier to simply restore that particular backup via Recovery.
I never flashed any roms or recovery, just rooted.
Unfortunately, I never made a nandroid backup before I had this problem, however, my daughter has an identical phone, could I make such a backup from hers, and use it on my phone, then just delete her settings etc?
I had no idea that just rooting would kill the stock ROM image, making the phone un-recoverable, I thought that rooting only gave me superuser permissions.
The4thDoctor said:
I never flashed any roms or recovery, just rooted.
Unfortunately, I never made a nandroid backup before I had this problem, however, my daughter has an identical phone, could I make such a backup from hers, and use it on my phone, then just delete her settings etc?
I had no idea that just rooting would kill the stock ROM image, making the phone un-recoverable, I thought that rooting only gave me superuser permissions.
Click to expand...
Click to collapse
Looks like Clockworkmod doesn't support your device.... not sure what custom Recoveries are available for your phone... but rooting doesn't mess up the stock ROM, we (the users) mess up our ROMs. You're right when you said that rooting gives you superuser privileges, and with those privileges come the unfortunate ability to screws stuff up. In my case I have tons of backups and a custom Recovery whereby I can wipe the phone and restore if need be. I also have ADB installed and can use Fastboot commands if things go sideways. Basically if you're gonna root have a backup plan.
Can you perhaps follow an unrooting method? Then you could safely factory reset without losing the OS... you know...the more I think about this, the more I wonder if you could just use the factory reset option from within the phone's settings... on a custom ROM you'd never do it, but in your situation (no custom recovery or ROM) who knows, maybe it would work with a problem.... I'll ask a friend of mine and post back.
Edit: Never heard back, but in your case on the stock ROM without a custom Recovery you *should* be able to factory reset through the Privacy setting section of your settings. If you do lose root, simply re root and you're good to go.
Thanks, Well I am going to give it a try and see what happens, worst case, I will have to buy another phone.
EDIT: I had no problems with factory reset, thank you!
What do I backup when I sbf? Can I back up everything I need with TiBu pro? When I reboot my phone after sbfing, is it like getting it out of the box, but with a newer version? How do I restore everything? Will it save app data?
Sorry for all the questions, but I need to know.
Edit: Also, if it is like getting it out of the box, what happens to my verizon plan?
Arbybear said:
What do I backup when I sbf? Can I back up everything I need with TiBu pro? When I reboot my phone after sbfing, is it like getting it out of the box, but with a newer version? How do I restore everything? Will it save app data?
Sorry for all the questions, but I need to know.
Edit: Also, if it is like getting it out of the box, what happens to my verizon plan?
Click to expand...
Click to collapse
You can back up your apps and data with TiBu. After sbf your phone will be like new, out of box, and you will need to activate your phone. It does not effect your plan. You can restore your apps and data from TiBu after the sbf.
maggard5 said:
You can back up your apps and data with TiBu. After sbf your phone will be like new, out of box, and you will need to activate your phone. It does not effect your plan. You can restore your apps and data from TiBu after the sbf.
Click to expand...
Click to collapse
Thank you. Is the only bug in 2.3.4 the battery percentage?
Arbybear said:
Thank you. Is the only bug in 2.3.4 the battery percentage?
Click to expand...
Click to collapse
I am using cm7 so not sure what issues you might encounter with stock 2.3.4.
Sent from my MB870 using XDA App
If u aren't on a rom or have any tweaks
just sbf
sbf doesn't wipe ur user data AT ALL it just upgrade ur system
BUT if u have a rom running or scripts or tweaks like that then u may bootloop after the sbf and will need to data wipe from stock recovery to remedy the bootloop
If u r dong sbf just to upgrade u wont lose ur apps data ...
ashclepdia said:
If u aren't on a rom or have any tweaks
just sbf
sbf doesn't wipe ur user data AT ALL it just upgrade ur system
BUT if u have a rom running or scripts or tweaks like that then u may bootloop after the sbf and will need to data wipe from stock recovery to remedy the bootloop
If u r dong sbf just to upgrade u wont lose ur apps data ...
Click to expand...
Click to collapse
so do you HAVE to wipe after sbf? I thought I had read on here that people had successfully sbf's without a wipe? as your post would seem to suggest?
I sbf'd for the first time in forever tonight, but didn't wipe just yet cause I didn't feel like setting everything up from scratch again.
But I still have superuser listed in my app drawer, but I seem to no longer be rooted, and had to reactivate the phone.
If the "crashed" rom is the same as the sbf no wipe needed but it's a crapshoot if "crashed" is custom rom then sbf will need wiping!
skwoodwiva said:
If the "crashed" rom is the same as the sbf no wipe needed but it's a crapshoot if "crashed" is custom rom then sbf will need wiping!
Click to expand...
Click to collapse
not necessarily
im not exactly sure why sometimes you need a wipe, and sometimes you dont.
i havent sbfd enough times to figure that out cuz i can usually just nandroid restore back to where i need to be.
but i have definitly sbfd from a rom like eclipse and NOT needed a data wipe
and i have also sbf'd when just stock rooted with some tweaks and NEEDED data wipe to stop the bootloop.
three west said:
so do you HAVE to wipe after sbf? I thought I had read on here that people had successfully sbf's without a wipe? as your post would seem to suggest?
I sbf'd for the first time in forever tonight, but didn't wipe just yet cause I didn't feel like setting everything up from scratch again.
But I still have superuser listed in my app drawer, but I seem to no longer be rooted, and had to reactivate the phone.
Click to expand...
Click to collapse
if you did a sbf you no longer have root access
i am not sure if the superuser app will be wiped away at this point if you do a data wipe either, superuser is usually a /system/app am i correct?
BUT if it is a user app(found in /data/app) then you can just uninstall the superuser via manage applications
if it is system/app you NEED root access to be able to remove the apk
if you wanna check if you are rooted or not just try to use an app that requires root access, if you are not rooted it wont work.
so yes, you inferred correctly, a data wipe is not NECESSARY after EVERY sbf flash, BUT it IS needed if you get caught up in a bootoop, data wipe from android recovery is the only way to get out of a bootloop resulting from sbf flash.
it is aso recommnded to data wipe after a sbf flash just due to issues that may arise later and u might have to data wipe then to get rid of those issues, you might end up never needing to data wipe, but if you do run into issues, that will be the solution
sorry, im not tryng to ramble here, just trying to be clear as much as i can based on my experience and based on the many results of others and their feedback.(if i have caused confusion i apologize, just ask and i will try to clear it up, i just watched hitchhikers guide to the galaxy, if u have ever read the book or seen the movie you know where my mind is right now LMAO)
well I was just going back to stock for, ya know, reasons
I had been just rooted stock at the time. I really don't want to wipe and set everything up from scratch again.
Root is gone, BSR is not functional, but they both still show in the app drawer.
Pulldown toggles are gone.
I think I'm going to give it a shot like this and see what comes
I think you will WANT to SBF>Factory Reset if you wanna do the "reasons"...
But only bug noted(that I can remember anyway) is the battery jump.
TiBu will not restore your apps or data unless you are rooted. My suggestion... do a Nandroid Backup and then do provided instructions... at least this way you can go back to what you had before hand.
SBF will bring your phone to an Out-of-Box state... Exactly how you got it at Verizon.
Questions Asked:
What do I backup when I sbf?
Whatever you want. Nandroid will be for if you want to go back to what you were using. TiBu is for if you are going to apply:
-SBF to a different Android Version.
-Apply a New Rom.
Can I back up everything I need with TiBu pro?
Depends on what you are doing. TiBu is intended for apps and app data, also keep in mind to watch what you restore because you DO NOT want to restore the Settings and other system apps when you are going to a different android version(if you know the exceptions then you know the exceptions... Dragons lie ahead if you don't know what you are doing... just trust this advice).
This WILL NOT cover user configuration in the internal settings.
When I reboot my phone after sbfing, is it like getting it out of the box, but with a newer version?
Did you upgrade or downgrade? SBF is used to go back if you brick your device or need to be on a specific android version/kernel for applying a ROM. Yes it will be out of box state with a specific android version.(i.e. If you apply 2.2 SBF you go back to 2.2 android out-of-box. If you apply 2.3.3 SBF you go back to 2.3.3 android out-of-box. etc...)
How do I restore everything? Will it save app data?
Did you Nandroid or TiBu?
Nandroid:
Apply SBF to specific android version/kernel version you were previously on(you want to be on the kernel you had with said Nandroid backup). Boot into BSR/CWM then go to restore>Internal/External Memory>Restore>Wait for application of backup>Reboot.
TiBu
Once you are on a satisfied android version/kernel open TiBu and restore whatever apps you want. You get the option to restore App(s) Only, App(s) Data Only, or App(s) and Data.
Also, if it is like getting it out of the box, what happens to my verizon plan?
Nothing!! Your Verizon Plan is saved server side and is paired with your device MEID. After a SBF is applied, you can follow the initial boot and activate your phone or dial *228 at any time to activate your device.
I hope I answered everything for you sir. Good luck with SBFing...If you have ANY bootloops or crashes after SBFing do this please:
Boot into STOCK android recovery:
1. Turn device off or Battery Pull.
2. Hold Volume Down until step 4.
3. Turn on device.
4. You should see the Moto Red Logo with white text "Fastboot" at the top of your screen. Press volume down until white text reads Android Recovery.
5. Press Volume Up to select Android Recovery.
6. You should see a Blue Android with Yellow Exclamation point.
7. Press Volume Up + Volume Down at the same time.
8. Using Volume Keys, highlight "Factory/Data Reset" then press Power Button.
9. Select Yes.
10. Reboot once complete.
Side Note:
lol I'm really bored at work right now.
Well well. I know it may surprise you to see me here
I was messing with busybox, trying to update it. Apparently I did something wrong and the phone doesn't boot now. It'll go on the bootanimation, but at the very end, JUST before the menu softkeys lights come up, it instantly crashes and returns to the splash screen and the cycle is repeated.
Anything I can do to restore it back to an usable state, without losing the data I have on the phone? I know how to make it work again, that's really easy, but what I don't know how, is to make it work again without losing data.
I mean, busybox update seemed safe enough >_> Then it broke everything else.
Oh well, any answers would be appreciated.
Just a thought, no expert here but I've made changes to my phone tht caused me to get stuck and I've gone into recovery-restore-advanced restore and just restored the system part and its gotten me back to a running state.
I'm also thinking if you make a nandroid of your current state then try and fix the issue at least you can always have tht to go back to if someone gets you a better answer.
Wish you the best of luck, I hate having to wipe too!
I was born in Darkness.....
chozyn said:
Just a thought, no expert here but I've made changes to my phone tht caused me to get stuck and I've gone into recovery-restore-advanced restore and just restored the system part and its gotten me back to a running state.
I'm also thinking if you make a nandroid of your current state then try and fix the issue at least you can always have tht to go back to if someone gets you a better answer.
Wish you the best of luck, I hate having to wipe too!
I was born in Darkness.....
Click to expand...
Click to collapse
Didn't work, but it was a good idea actually. I didn't have a recent backup. Didn't make one, as I thought busybox would be easy enough and wouldn't affect much. Oops.
Man, I'm having such bad luck today... First, I accidentally deleted few gigs of stuff off my computer. Then my phone gets messed up due to something I did in busybox. Gee, what's next?
Damn....going out on a limb here but what if you back up your rom in its current not booting state. Then wipe and do a fresh install of the same Rom-backup the fresh install.
Afterwards flash the not booting backup you made and then do the advanced restore using the system IMG from the fresh install to see if it will boot?
Sorry thinking in layman's terms here.
I was born in Darkness.....
Flash the Rom over your brick it should boot back up. Busy box writes the files in /system/xbin (If I remember) so when you reflash the Rom you're using it writes everything back to normal. Just don't do a wipe and you should be good.
Anything that was changed in /system will be reset to original.. so if you had GNow it'll have to be reinstalled. Same thing with any other files in /system.
chozyn said:
Damn....going out on a limb here but what if you back up your rom in its current not booting state. Then wipe and do a fresh install of the same Rom-backup the fresh install.
Afterwards flash the not booting backup you made and then do the advanced restore using the system IMG from the fresh install to see if it will boot?
Sorry thinking in layman's terms here.
I was born in Darkness.....
Click to expand...
Click to collapse
I actually thought of this, but for some reason, it doesn't work. It still gets hard bootloops.
Double0EK said:
Flash the Rom over your brick it should boot back up. Busy box writes the files in /system/xbin (If I remember) so when you reflash the Rom you're using it writes everything back to normal. Just don't do a wipe and you should be good.
Anything that was changed in /system will be reset to original.. so if you had GNow it'll have to be reinstalled. Same thing with any other files in /system.
Click to expand...
Click to collapse
Thought of this before I did anything, but apparently it affected the /data too (The files inside there are intact, but something there is not allowing my phone to boot), thus continuing the hard bootloops.
I'm befuddled. I will have to figure this out later. For now, I just made a backup of the non-working ROM and wiped everything and flashed a ROM on it. I'll figure out what parts of /data to transfer back later. I needed a functioning phone, so yeah
Thanks for the help. If anyone else has any other good ideas, I'll try them out.
Keylogger_0 said:
I actually thought of this, but for some reason, it doesn't work. It still gets hard bootloops.
Thought of this before I did anything, but apparently it affected the /data too (The files inside there are intact, but something there is not allowing my phone to boot), thus continuing the hard bootloops.
I'm befuddled. I will have to figure this out later. For now, I just made a backup of the non-working ROM and wiped everything and flashed a ROM on it. I'll figure out what parts of /data to transfer back later. I needed a functioning phone, so yeah
Thanks for the help. If anyone else has any other good ideas, I'll try them out.
Click to expand...
Click to collapse
What rom are you using?
Grab that rom, in a zip file preferably, modify the updater script to not write to the data partition, wipe all partitions except data, flash and reboot.
Fix permissions and wipe caches if needed.
Hi all,
I have a Droid incredible 4g (stock, unrooted/unlocked, w/ the recent OTA update). I saw the Bootloader Unlock exploit in the developer's forum so I gave it a go, and it worked fine. Then I installed the Viper 1.0 ROM, but I haven't been able to get it to do anything after successfully booting except run through a loop of errors such as "Unfortunately, the process android.process.acore has stopped working." After I click "OK" on about 10 critical errors, it self-reboots and does the whole thing again.
Unfortunately, I didn't do a backup this time, so I have nothing to restore (first time I haven't done a backup, but also the first time I've ever had any kind of an issue w/ a ROM). I tried using the HTC Android ROM Update Utility 1.0.5.2011 that I found in the dev forum, but that didn't work either. Finally, I installed 2.17.605.2 Verizon Global Sense4.1 Android 4.0.4. It's a lot more stable than Viper was and the phone is basically usable, but I still get lots of critical errors. So this morning I went back to the forum and saw that I needed to downgrade to the old 1.43.605.3 kernel. I tried that and then reinstalled Viper 1.0, but it seemed to have no effect--still stuck in a critical error/reboot loop.
I realize that's the risk of playing with ROMs and I should have done a backup, but anyone have any ideas on how I can get my phone back and running?
Thanks!
Even though it explicitly stated you didn't need to do a backup, I did one anyway, to prevent something like this from happening. Always do a backup.
Did you verify the MD5Sum of ViperLTE?
Did you go to Recovery and Wipe -> Factory Reset and Wipe -> System both twice before trying to install the ROM?
Did you change anything in the ROM before attempting to load it?
There are lots of questions we could ask to ascertain the root of the problem, but these three are among the most important.
Wi-Fi won't work without the old boot.img, and from what I can tell, that's the only thing. It doesn't give critical errors.
I'm thinking since you are new to root you were un-aware the need to wipe before installing a rom.
im thinking that is the issue.
Thanks for the reply!
I didn't check the MD5 last night but I did just now and it matches.
I did a cache wipe the first time but not a system wipe. Then I started getting more desperate and tried reinstalling w/ system wipes and factory resets, but it didn't change anything.
No, I didn't change the ROM. Doing the Bootloader unlock exploit was about the absolute maximum of my technical abilities! The only thing I know I did wrong was that I didn't downgrade to the old boot version the first time (mainly because the wifi thing sounded inconsequential and I didn't want to learn the procedure if I didn't have to).
Anyway, I just tried Ultimate KangBang and it seems to work--no error messages so far. I don't know what I did wrong, but hopefully this keeps working!
IceDragon59 said:
Even though it explicitly stated you didn't need to do a backup, I did one anyway, to prevent something like this from happening. Always do a backup.
Did you verify the MD5Sum of ViperLTE?
Did you go to Recovery and Wipe -> Factory Reset and Wipe -> System both twice before trying to install the ROM?
Did you change anything in the ROM before attempting to load it?
There are lots of questions we could ask to ascertain the root of the problem, but these three are among the most important.
Wi-Fi won't work without the old boot.img, and from what I can tell, that's the only thing. It doesn't give critical errors.
Click to expand...
Click to collapse
andybones said:
I'm thinking since you are new to root you were un-aware the need to wipe before installing a rom.
im thinking that is the issue.
Click to expand...
Click to collapse
Yes, I took a short-cut that didn't quite work out. I didn't want to wipe the system because I wasn't sure if my pictures would be wiped too, but then when everything died I tried wiping everything and reinstalling and it didn't seem to improve anything. I did end up losing my pictures too. Oh well. Maybe it's just a combination of stuff I did to try to get things working (there was some trial and error in unlocking the bootloader but I did get that to work finally, and then more trial and error with the ROMs).
I guess the best thing to do is leave the phone the heck alone as long as it's working, for now. I just don't know why nothing seemed to work--I thought factory reset/fresh ROM would do it.
franklin411 said:
Yes, I took a short-cut that didn't quite work out. I didn't want to wipe the system because I wasn't sure if my pictures would be wiped too, but then when everything died I tried wiping everything and reinstalling and it didn't seem to improve anything. I did end up losing my pictures too. Oh well. Maybe it's just a combination of stuff I did to try to get things working (there was some trial and error in unlocking the bootloader but I did get that to work finally, and then more trial and error with the ROMs).
I guess the best thing to do is leave the phone the heck alone as long as it's working, for now. I just don't know why nothing seemed to work--I thought factory reset/fresh ROM would do it.
Click to expand...
Click to collapse
If UKB ROM works then Viper ROM will too, installing the boot.img is very simple it's one command
I can help you with that if you'd like
in recovery before installing ROM, do a wipe of, (I go in this order, but it doesn't matter.)
1) Factory Reset
2) System
3) Cache
4) Dalvik Cache
then install the ROM
just DO NOT do External storage (unless of coarse u WANT to wipe your SD-Card.)
as long as you don't wipe External Storage you won't lose anything that's on your SD-Card.
in the future it is always good practice to backup(nandroid) your current ROM. I have been burned too many times, always do a nandroid before you do anything in recovery.
your photos are normally saved to the SD, flashing ROMs or wiping the system will not delete them
andybones said:
If UKB ROM works then Viper ROM will too, installing the boot.img is very simple it's one command
I can help you with that if you'd like
in recovery before installing ROM, do a wipe of, (I go in this order, but it doesn't matter.)
1) Factory Reset
2) System
3) Cache
4) Dalvik Cache
then install the ROM
just DO NOT do External storage (unless of coarse u WANT to wipe your SD-Card.)
as long as you don't wipe External Storage you won't lose anything that's on your SD-Card.
Click to expand...
Click to collapse
It worked this time! Maybe the difference was that the boot.img file I downloaded was called "boot_signed.img" or something. I had no idea what it was supposed to look like, so I installed it that way and it didn't work. Then I tried renaming it to "boot.img" this morning and installing viper, but that didn't work. And then I restarted and installed UKB, and it worked. Just now I wiped and tried again with Viper and it's working fine. Maybe I did something this morning that caused it not to take properly when I tried with Viper, and then I reset and it worked.
Thanks for the help!
franklin411 said:
It worked this time! Maybe the difference was that the boot.img file I downloaded was called "boot_signed.img" or something. I had no idea what it was supposed to look like, so I installed it that way and it didn't work. Then I tried renaming it to "boot.img" this morning and installing viper, but that didn't work. And then I restarted and installed UKB, and it worked. Just now I wiped and tried again with Viper and it's working fine. Maybe I did something this morning that caused it not to take properly when I tried with Viper, and then I reset and it worked.
Thanks for the help!
Click to expand...
Click to collapse
na the name has nothing to do with it. it can be named whatever.
im guessing the wipe worked.
franklin411 said:
Hi all,
I have a Droid incredible 4g (stock, unrooted/unlocked, w/ the recent OTA update). I saw the Bootloader Unlock exploit in the developer's forum so I gave it a go, and it worked fine. Then I installed the Viper 1.0 ROM, but I haven't been able to get it to do anything after successfully booting except run through a loop of errors such as "Unfortunately, the process android.process.acore has stopped working." After I click "OK" on about 10 critical errors, it self-reboots and does the whole thing again.
Unfortunately, I didn't do a backup this time, so I have nothing to restore (first time I haven't done a backup, but also the first time I've ever had any kind of an issue w/ a ROM). I tried using the HTC Android ROM Update Utility 1.0.5.2011 that I found in the dev forum, but that didn't work either. Finally, I installed 2.17.605.2 Verizon Global Sense4.1 Android 4.0.4. It's a lot more stable than Viper was and the phone is basically usable, but I still get lots of critical errors. So this morning I went back to the forum and saw that I needed to downgrade to the old 1.43.605.3 kernel. I tried that and then reinstalled Viper 1.0, but it seemed to have no effect--still stuck in a critical error/reboot loop.
I realize that's the risk of playing with ROMs and I should have done a backup, but anyone have any ideas on how I can get my phone back and running?
Thanks!
Click to expand...
Click to collapse
weird, i was having the same problem with the same processes stopped working. i wiped cache dalvik and system but not factory reset. once i factory reset, it worked fine. i figured a system wipe would have been enough....