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.
Related
EDIT 3/30: This problem should be solved with the updated version of CWR found here: http://forum.xda-developers.com/showthread.php?t=1017817
Remember that until devs start bundling it with their roms, you will need to flash it after you flash a new ROM. (Superclean 2.9.2 and before includes the broken recovery).
The problem was in the fact that cwr didn't have root access. The updated one now contains this fix.
If you are trying to restore a nandroid from an old backup, you might have issues. I'll try to see about this scenario to see the easiest way to do it (the steps from the previous post in this thread should work.)
Also, it looks like dbdata doesn't auto-mount, so you need to go into the mount menu and mount it before being able to run the fix_permissions script, if you want to run that.
I think I got it fixed so that it will auto-mount it in the script, but it won't be recompiled until JT does it.
Original thread:
Info and links:
http://forum.androidcentral.com/ver...s/72212-warning-trouble-nandroid-backups.html
http://forum.androidcentral.com/verizon-fascinate-rooting-roms-hacks/72185-3-days-hell.html
This seems to explain a lot of the issues people have been having. Probably best to check that thread for updated info, but copying and pasting for those who are other forum-phobic:
Landshark said:
Do not try to restore a themed nandroid backup for the time being!!
DroidXcon has done a great job of putting together the thread about clockworkmod recovery (cwm), how to install it, use it, and how to fix permissions since that is not working in cwm right now. That is not the only thing not working in cwm right now. Right now you are also unable to wipe battery stats and restore a nandroid backup that includes a theme through cwm. What is a nandroid backup? Well you can check out posts 6, 7, & 8 of DroidXcon's clockwork mod thread for a detailed description with visual aids:
DroidXcon's Clockwork Thread Here
The problem seems to stem from not being able to fix permissions in cwm. If you read DroidXcon's thread it should make more sense and I can only do an injustice to his work by trying to explain it here myself. Bottom line is like I said above we are unable to successfully restore nandroid backups that include a theme at this time without ending up in a force close loop of hell (FCLOH) at boot animation, a.k.a. boot loop. Jaekar99, Suicide Shift, and I have been working at this for some time without any solution. We have only been able to successfully restore a nandroid backup of only the base ROM. Which is basically pointless since in basically the same amount of time it takes to restore a nandroid backup of just the base ROM, I can boot into cwm, flash the base ROM, reboot, boot into cwm, wipe cache and dalvik, flash a theme, reboot, boot to cwm, wipe cache and dalvik, flash a patch or two, and reboot my phone.
There is also a problem trying to flash a ROM and a theme in the same cwm session. Doing so will almost certainly put you into a FCLOH at boot. Best advice is as always try to only flash ROMs when your battery is at or near 100%. I have also had fewer problems when I flash while my phone is plugged in, either to an outlet, or into the usb on my computer. In addition to that, you will have fewer problems, if any, flashing the ROM by itself, rebooting, booting back into cwm, wiping cache and dalvik cache, flashing a theme if you want one, rebooting, booting back into cwm, then flashing any additional patches or mods, then rebooting. I know that is a lot of steps to take, but it's better than the alternative, which is ending up in a FCLOH, THEN having to take all those steps. You know, it's that whole ounce of prevention thing.......
For more information about flashing themes, patches, mods, and boot animations, you can get great information in Jaekar99's Themes, ROMs, Kernels, Boot Animations thread. I believe he is also covering some of this warning material in an effort to get it to as many people as we can.
Jaekar99's Themes Thread Here
So for the time being, do not try to restore a themed nandroid backup through cwm. If you have already created nandroid backups in cwm, I would think you can just leave them there for when we figure out a solution or fixing permissions gets repaired in cwm.
Any questions about this, you can usually find Jaekar99, Suicide Shift, or me here in the forums. Post your questions here and we'll do our best to answer them. I will also keep this updated with any new information or results of what we are testing. Thank you, and sorry to anyone who ended up in a FCLOH because I didn't get this information out sooner. (davey11)
Also for instructions on how to wipe battery stats since it can't be done in cwm, check out Gunnermike53's [How to] [Discussion] Improve Battery Life thread. It also involves commands entered in Terminal Emulator.
Gunnermike53's Battery Life Thread Here
And let's get one more plug in here. If any of this terminology is confusing to you, or you are new to rooting and want a great guide to get you started and better informed, check out Sheepdog Elite's [How to] First time rooting walk-through.
Sheepdog Elite's First Time Rooting Thread Here
Click to expand...
Click to collapse
There is a workaround in process of being written up.
The workaround is to reflash your theme over the nandroid once you get the restore finished. It's been mentioned that after a few days some one had it go bad that way, but it's what we've got for now.
Thanks GizmoDroid,
I was going to post the same info here when I woke up this morning. A group of us over at AC were up til the wee hours working on solutions and I was falling asleep at the keyboard. I'm trying to be more active over here and will update my OP at AC and this thread here.
For now a solution that gets you past the FCLOH is to boot back into cwm and flash whatever theme you have in the nandroid. That will get you past the FCLOH, but some patches and mods are being overwritten by doing that. So far, Adrynalyne's nuance patch stayed, but the mod settings patch did not. We are still working on other possible solutions. For now, other than doing this testing, I am not even bothering with nandroid backups as I can boot to cwm, flash ROM, reboot, boot to cwm, wipe cache & dalvik, flash theme, reboot, boot to cwm, wipe, flash patches and mods, and reboot all in about the same amount of time it takes to safely restore a nandroid of just the base ROM to avoid the FCLOH.
Right now I am going to see if restoring a nandroid, then flashing the theme in the same cwm session avoids the FCLOH.
Result of latest test - PASS
So flashing the theme over the nandroid restore in the same cwm session resulted in a clean reboot with no FCBLOH (Added in the B for Boot -Force Close Boot Loop of Hell.) Same problem as before though as Adrynalyne's settings mod was overwritten by the theme. So while this takes care of the FCBLOH problem, but it involves extra steps. Which like I said before kind of defeats the purpose of having a nandroid backup to restore - creating a complete build you can then restore all at once instead of having to do it piecemeal. Well at least for now there is a way to get around the FCBLOH when restoring a themed nandroid backup. Thanks Sheepdog Elite for all the help and for finding this workaround. Everyone just remember if you use this workaround and have any additional patches or mods included in your themed nandroid backup, after you restore check to see if all of your mods and patches are still in place.
Since I don't use nandroids/themes much, instead of doing a bunch of testing myself, I'll just ask you guys this:
We are possibly talking about a permissions issue. Why not do a system partition dump before nandroid, and then after restoring, then see what's different? After that point, you can make a script that sets the permissions on those files.
Or if files are actually missing or corrupted, then you will be able to find this out too.
GizmoDroid said:
Since I don't use nandroids/themes much, instead of doing a bunch of testing myself, I'll just ask you guys this:
We are possibly talking about a permissions issue. Why not do a system partition dump before nandroid, and then after restoring, then see what's different? After that point, you can make a script that sets the permissions on those files.
Or if files are actually missing or corrupted, then you will be able to find this out too.
Click to expand...
Click to collapse
Thank you sir. I will pass this along and see what we can find out.
landshark68 said:
Thank you sir. I will pass this along and see what we can find out.
Click to expand...
Click to collapse
Actually, after some preliminary research, my suspicions are not the system partition but the dbdata partition (/dev/block/stl10).
Clockwork has had problems with this one in the past. I don't know if it's on the backup end or restoring end, but I bet it's an issue with one of the scripts mounting the wrong partition, or folder. (clockwork mod mounts it to /datadata while stock rom calls it /dbdata)
GizmoDroid said:
Actually, after some from preliminary research, my suspicions are not the system partition but the dbdata partition (/dev/block/stl10).
Clockwork has had problems with this one in the past. I don't know if it's on the backup end or restoring end, but I bet it's an issue with one of the scripts mounting the wrong partition, or folder. (clockwork mod mounts it to /datadata while stock rom calls it /dbdata)
Click to expand...
Click to collapse
Shark. This is sounding like one of us needs to go back to school to become a script editor. This is getting beyond me.
JaeKar99 said:
Shark. This is sounding like one of us needs to go back to school to become a script editor. This is getting beyond me.
Click to expand...
Click to collapse
Yeah, he pretty much got beyond me at Actually, I'm just a guy who has learned quickly and gotten good at flashing, rooting, and problem solving to help other people. I am completely lost when it comes to the technical side. I am trying to learn as much as I can though so I'm not so lost. If we can eventually get this info to the right people I would be happy with that. If those right people are the devs, I am more than happy putting this issue on the shelf until they are completely done with their current projects. But anything I can do in the meantime to help I will certainly do or try.
landshark68 said:
Yeah, he pretty much got beyond me at Actually, I'm just a guy who has learned quickly and gotten good at flashing, rooting, and problem solving to help other people. I am completely lost when it comes to the technical side. I am trying to learn as much as I can though so I'm not so lost. If we can eventually get this info to the right people I would be happy with that. If those right people are the devs, I am more than happy putting this issue on the shelf until they are completely done with their current projects. But anything I can do in the meantime to help I will certainly do or try.
Click to expand...
Click to collapse
The good news is I just successfully restored a themed nandroid!
The bad news is that I'm not exactly sure what I did to fix it.
Nandroid backed-up a themed install.
Nandroid restored same themed install.
Rebooted.
Eternal bootloop ensued.
Rebooted to CWM.
While in CWM, I plugged in the usb and connected via ADB shell. I then typed the following (replace the red part with whichever nandroid backup folder you want to restore)
Code:
/sbin/nandroid restore /sdcard/clockworkmod/backup/[COLOR="Red"]2000-01-01.00.06.31[/COLOR]/
Did some other stuff
Rebooted and was greeted with a successfully working phone!
Now, I did some other things too, so I'm not sure if this was the only thing it needed. If this is all it was, then it should be an easy CWM fix. Someone want to try that and let me know?
If that's not it, I'll tell you the other things I did. It's got to be one of them
Things to remember: nandroid doesn't back up your kernel or modem at this time. If you try to restore an nandroid backup with an incompatible kernel or modem, you will have problems. Flash these first.
GizmoDroid said:
The good news is I just successfully restored a themed nandroid!
The bad news is that I'm not exactly sure what did it.
Here's what I think I did:
While in CWM, I plugged in the usb and connected via ADB shell. I then typed the following (replace the red part with whichever nandroid backup folder you want to restore)
Code:
/sbin/nandroid restore /sdcard/clockworkmod/backup/[COLOR="Red"]2000-01-01.00.06.31[/COLOR]/
If this is what did it, then it should be an easy CWM fix. Someone want to try that and let me know? If that's not it, I'll tell you the other things I did. It's got to be one of them
Click to expand...
Click to collapse
I will try it and let you know.
Nope, that one wasn't it. Nothing happened in adb or on the phone. Next?
landshark68 said:
Nope, that one wasn't it. Nothing happened in adb or on the phone. Next?
Click to expand...
Click to collapse
Nothing happened... at all? Like it just went back to the prompt without saying anything?
If that's the case, we have bigger fish to fry, because it should have at the very least complained or showed some text.
GizmoDroid said:
Nothing happened... at all?
Click to expand...
Click to collapse
Never mind. Jut took a while for it to start rolling in adb. stand by for results.
Boot loop city
landshark68 said:
Boot loop city
Click to expand...
Click to collapse
Not being facetious here, but I need to know exactly what I did different than you.
Can you tell me all the steps you did, in as much detail as you have patience for?
GizmoDroid said:
Not being facetious here, but I need to know exactly what I did different than you.
Can you tell me all the steps you did, in as much detail as you have patience for?
Click to expand...
Click to collapse
Well I'm going to start over. After I went through the procedures I scrolled back up and noticed you tried to restore your nandroid through cwm first. I flashed to just plain sc 2.9.2v through cwm, booted to recovery, ran the commands through adb, rebooted when adb said restore complete. I will now follow your exact steps and try restoring the nandroid through cwm first.
And since I've been flashing so much stuff today I'm going to wipe data, cache, and dalvik before trying to restore the nandroid if you think I should start from a clean slate.
Actually, hold off a second. I just redid the steps myself, and that wasn't all of the commands needed, apparently.
Before you jump through a bunch of hopes again, let me try some stuff.
landshark68 said:
Well I'm going to start over. After I went through the procedures I scrolled back up and noticed you tried to restore your nandroid through cwm first. I flashed to just plain sc 2.9.2v through cwm, booted to recovery, ran the commands through adb, rebooted when adb said restore complete. I will now follow your exact steps and try restoring the nandroid through cwm first.
And since I've been flashing so much stuff today I'm going to wipe data, cache, and dalvik before trying to restore the nandroid if you think I should start from a clean slate.
Click to expand...
Click to collapse
Ya, best bet would be to start clean, flash ROM and theme, nandroid backup, nandroid restore, then do the manual nandroid restore from adb. Try to eliminate all the variables.
If that's not it, then it had to be some funky mounting stuff I was doing. But I'd rather not get into that if I don't have to, because I tried a bunch of stuff all at once.
Standing by. I just made a build of sc 2.9.2v and ultimate honeycomb 3.1.1. I'll make a nandroid backup of that while waiting.
ETA - And don't worry about the appearance of being facetious or hurting my feelings or insulting me. I'm a grown person with thick skin. And I've read a bunch of your posts and have the same mind set. Don't insult, but tell it exactly like it is.
I have finally got my phone unlocked and rooted. Now I am trying to install the quicksense ROM. I know I am doing something wrong, because all I get is the white HTC screen at start up, and thats as far as it goes. So, here is what I did, and maybe someone can help me out.
I downloaded amazing quicksense and dragged it into my sd card
I booted into recovery
I did a backup
I wiped the cashe
I went to install from sd card and chose the zipped quicksense file
I then got install from sd card complete
I then went back and rebooted phone
From here the phone freezes on the white HTC screen and does not fully boot.
I had to go back into recovery and do a restore to get my phone working again.
What am I doing wrong. Please help.
Seem like you did succeed at everything except the cleaning parts
Please try again by going into recovery and
1. wipe data/factory reset
2. Wipe cache partition
3. Go to Advance then wipe dalvik cache - after that, choose go back
4. Install rom from sdcard
5. Reboot
I will try and do what you have instructed. However I wanted to ask one question before I do this. In your first step to "wipe data/factory reset", will this reset my phone back to factory, essentially wiping all my data and everything I have on it? I know unlocking the bootloader did that, but it would suck if I had to do this every time I installed a ROM. Just want to make sure what I am up against. Thanks
ms2knights said:
I will try and do what you have instructed. However I wanted to ask one question before I do this. In your first step to "wipe data/factory reset", will this reset my phone back to factory, essentially wiping all my data and everything I have on it? I know unlocking the bootloader did that, but it would suck if I had to do this every time I installed a ROM. Just want to make sure what I am up against. Thanks
Click to expand...
Click to collapse
Hi
I am by no mean a dev so my advices is more like ... well, advice - not instructions my friends
Wipe data/factory reset mean wiping every personal datas that you had on the device and yes, this will reset your phone back to the present rom that you had on the device - in your case is the stock/factory/carriers rom.
Every time you install a new rom you should - and every dev will suggested this - wipe clean your data and whatever info that may still left on the device from previous rom - you may not need to do this when you update to the new version from the same rom. Sometimes the new version of the same rom featured too many changes then the dev will instructed user to wipe all the data. That's why we user should always read the first, second and third post to make sure we keep ourself up-to-date when flashing rom.
Personal data means your google account, emails, contact list, SMS, wifi password, bluetooth pairing and apps setting ... However, we can backup and restore most of these info using diferrent apps. Here are some app that I found helpful in term of backup:
* Gmail account for contacts list
* SMS backup for SMS and call log
* Titanium Backup for apps and it's data: This app is very useful, for example if you use it to backup your email app it will included your setup and password ect ... so after install new rom and restore a particular app, you have an option to restore the app plus it's data or data/app only
Read this thread for some useful tips on how to using Titanium Backup
http://forum.xda-developers.com/showthread.php?t=1324291
Googd luck and welcome to the Amaze
I really do appreciate your advice. I will go ahead and backup everything, and then attempt the ROM install again. Hopefully it will work this time. Again thanks.
Not a problem mate
Since you already backup your rom and QuikSense is a Sense rom anyway, it doesn't hurt to try restoring data from the backup. You can do this (after finish flashing the new rom) by go back into Recovery/Backup and restore/Advance restore/choose the backup file (in case you have more than 1 backup)/then chose restore data
I did this when switching from QuikSense rom to Senseless Rom and it work flawlessly
Worst case scenario is you will have to restore again. This will save a lot of steps.
ms2knights said:
I have finally got my phone unlocked and rooted. Now I am trying to install the quicksense ROM. I know I am doing something wrong, because all I get is the white HTC screen at start up, and thats as far as it goes. So, here is what I did, and maybe someone can help me out.
I downloaded amazing quicksense and dragged it into my sd card
I booted into recovery
I did a backup
I wiped the cashe
I went to install from sd card and chose the zipped quicksense file
I then got install from sd card complete
I then went back and rebooted phone
From here the phone freezes on the white HTC screen and does not fully boot.
I had to go back into recovery and do a restore to get my phone working again.
What am I doing wrong. Please help.
Click to expand...
Click to collapse
How long do you wait?
The first boot may take several minutes.
Do you have adb installed on your computer? If so then from the command prompt (or terminal if your running Ubuntu) type "adb shell logcat" and if it seems like it's repeating itself over and over again then your caught in a loop and would probably just need to clear the data and caches. Your problem should clear right up.
Binary100100 said:
How long do you wait?
The first boot may take several minutes.
Do you have adb installed on your computer? If so then from the command prompt (or terminal if your running Ubuntu) type "adb shell logcat" and if it seems like it's repeating itself over and over again then your caught in a loop and would probably just need to clear the data and caches. Your problem should clear right up.
Click to expand...
Click to collapse
To be honest with you, I did wait for maybe 5 min or less. I guess I thought it would boot normally. I will try again and give it some time.
Being very new to this, I am trying to learn all of this. How do I know if I have adb installed on my computer? Thanks
ms2knights said:
To be honest with you, I did wait for maybe 5 min or less. I guess I thought it would boot normally. I will try again and give it some time.
Being very new to this, I am trying to learn all of this. How do I know if I have adb installed on my computer? Thanks
Click to expand...
Click to collapse
Follow the instructions on this thread here:
http://forum.xda-developers.com/showthread.php?t=928370
Easiest way to set up ADB.
Hope this helps.
Well, I finally got it to work. My probem was that my sd card was not FAT32 but FAT. I think this was the problem I had with trying to flash clockworkmod. I did everything except the wipedata/factory rest, to see if it would work. And sure enough, I am now running Amazing Quicksense 1.5.1. Thanks for every ones help.
hey guys, been here since the launch of evo. rooting, flashing, everything.
today i wanted to switch roms. so i went about my normal process...
d/l new ROM
backup current ROM
backup apps
wipe cache and dalvic
flash new ROM
i got stuck on the last step. i went to flash the new ROM (nocturnal 1.3)
it said something along the lines of blah blah is already unmounted. i didnt pay too much attention to it because i was going to restart and try again. long story short, it will only boot to htc white screen and nothing else.
can anyone help me out?
p.s. im on clockwork recovery
PLEASE CLOSE
did you not wipe system and data? I am not super skilled, but maybe it tried to stick the entire ROM into the left over space of the last ROM that is still on there?
It won't boot to recovery? It should boot to recovery
weezymagic said:
hey guys, been here since the launch of evo. rooting, flashing, everything.
today i wanted to switch roms. so i went about my normal process...
d/l new ROM
backup current ROM
backup apps
wipe cache and dalvic
flash new ROM
i got stuck on the last step. i went to flash the new ROM (nocturnal 1.3)
it said something along the lines of blah blah is already unmounted. i didnt pay too much attention to it because i was going to restart and try again. long story short, it will only boot to htc white screen and nothing else.
can anyone help me out?
p.s. im on clockwork recovery
Click to expand...
Click to collapse
The error message you received is going to be the key to understanding the issue that occured. When it says unmounted, it is referring to a specific partition, either /data or /system most likely.
For starters, when it hangs on the htc white screen, this is usually either a kernel or ramdisk issue. If the kernel is known to be good, then it is probably a ramdisk issue. most ramdisk issues relate to a mismatch/incompatibility between the loaded kernel and the ROM.
First suggestion would be to reflash the ROM, clearing /cache and /data.
Second suggestion would be to restore a backup. This will confirm there is nothing wrong with your device hardware wise and you'll know it is a specific issue with the ROM you wanted to load.
Third suggestion, find the exact error, word for word, which occured in recovery and post up in the ROM thread asking if other users of that ROM also encountered, how they handled. Also feel free to post back up here.
When writing the programming behind a custom recovery, the error messages are added in there to help allow users and developers better knowledge of the exact issue so they can work to resolve them. Without the exact error message, it is similar to going to a car shop and saying, some light came on my dash, but I don't know what it was and now the car doesn't work. Fix it? Another words, it is very vague.
Hope the suggestions and tips help! Good luck!
my first instinct was to reflash the backup or new rom again but it wont boot to any rom, recovery or bootloader. it just hangs on the htc white screen
idk what happened but i got into the bootloader through battery pull, power+vol down. i know ive tried that in the past but this time it worked. now im restoring a nandroid from yesterday
weezymagic said:
idk what happened but i got into the bootloader through battery pull, power+vol down. i know ive tried that in the past but this time it worked. now im restoring a nandroid from yesterday
Click to expand...
Click to collapse
are you on twrp 1.0.x ? There is s charging issue where it won't restart right because it thinks It's already in recovery
sent from my EVO 3D via XDA app
weezymagic said:
hey guys, been here since the launch of evo. rooting, flashing, everything.
today i wanted to switch roms. so i went about my normal process...
d/l new ROM
backup current ROM
backup apps
wipe cache and dalvic
flash new ROM
i got stuck on the last step. i went to flash the new ROM (nocturnal 1.3)
it said something along the lines of blah blah is already unmounted. i didnt pay too much attention to it because i was going to restart and try again. long story short, it will only boot to htc white screen and nothing else.
can anyone help me out?
p.s. im on clockwork recovery
PLEASE CLOSE
Click to expand...
Click to collapse
You missed a step. After you wipe dalvik and cache, you ALWAYS need to wipe /system and /data, do a factory reset to make sure, or download a superwipe tool. The ONLY time you don't need to wipe completely is when you're updating your ROM, but even then it is recommended to wipe everything.
Twolazyg said:
You missed a step. After you wipe dalvik and cache, you ALWAYS need to wipe /system and /data, do a factory reset to make sure, or download a superwipe tool. The ONLY time you don't need to wipe completely is when you're updating your ROM, but even then it is recommended to wipe everything.
Click to expand...
Click to collapse
Agreed^^^^^
I Have restorted to being the noob that signs up to ask a question...The other day I was driving (pre-root) and I look down to notice my phone had power cycled on its own. I thought it would come back one, boy I was wrong....
It spiralled into endless boot cycle. It would at first reboot get to the 4g screen and then back to the htc...over and over. I was able to get into Hboot, and atempt to do a factory reset that didnt help because it became a endless reboot that way as well.
Now before any of you say "why dont you warranty replace the phone" Im a VZW agent, alas we dont have a warranty on our phones when it comes to our concessions lines...
Now, at that point I said enough is enough and I delved into the world of rooting. I self taught everything within a few hours. I had my phone unlocked and ready to go. I picked Ineffabile (http://forum.xda-developers.com/showthread.php?t=1420513) to use as a rom, I followed the procedure to a T it installed correctly, but then when it came back on everything seemed to work fine...for about 5 minutes and then it happened agian a power cycle all over again. and again...and again. It now comes on works for about 5mins and then reboots.
Im at a complete loss at this point I have gone back into the SD card and deleted the ph98 file etc.... I just dont know what to do. I need this phone to work.
Any help is appreciated Thank you so much!
I know you said it's not the wcdma problem but will your phone stay booted with the back cover off?
Else I'd ruu back to stock. Could try the different radios and see if it helps.
If you want to try the older radios and are on the OTA you'll have to hexedit you mainver. There's a guide if you look.
older radios? Im still new to this so I applogize...
A couple weeks ago there was an OTA (over the air update) that updated the radios - what controls the calls part of your phone and can affect reception and other stuff, I don't know everything it does. So if you wanted to try the older ones there's a thread somewhere, I think by con247, that has the older ones.
Here's a couple guides to help you get familiar with rooting stuff:
http://androidforums.com/evo-3d-all-things-root/389787-beginners-guide-rooting-android-devices.html
http://androidforums.com/evo-4g-all-things-root/129648-quick-intro-rooting-those-new-rooting.html
You can try flashing the kernel again. Sometimes bootlooping is a kernel issue, although it doesn't seem to be the cause of your situation.
How about insurance? Do you have that? Can you still get it?
feralicious said:
A couple weeks ago there was an OTA (over the air update) that updated the radios - what controls the calls part of your phone and can affect reception and other stuff, I don't know everything it does. So if you wanted to try the older ones there's a thread somewhere, I think by con247, that has the older ones.
You can try flashing the kernel again. Sometimes bootlooping is a kernel issue, although it doesn't seem to be the cause of your situation.
How about insurance? Do you have that? Can you still get it?
Click to expand...
Click to collapse
I dont have insurance =/ and cant get it either. Im trying to find the radios, and what kernal should I be flashing? because I cannot find the one that should match the rom im using.
What I dont understand is why the phone powers on, works for a few moments like nothing is wrong what so ever. Then freezes and reboots.
Oh, there's a new way of packing a ROM with a script that then installs the kernel so I guess it's all together now on Ineffabilis. Here's a link to the MikMik forum where they still have the stock rooted kernel as a separate download:
http://themikmik.com/showthread.php...-Beats-Tweaks-2-01-605-11&p=164906#post164906
Just take off the part of the name before PH98IMG.zip, put it on your external sd card. Do a battery pull, then reboot into bootloader by holding volume down + power. It will flash it and I think reboot. Then delete the PHzip file after that.
Don't know if it will help...
Oh... when you flashed Ineffabilis, did you restore any data from a backup? If yes, try flashing again and not restoring any data, just set up everything again manually. Also, if you restored any data from another phone's backup that could have caused problems. Basically you don't want to restore data from a different ROM.
feralicious said:
Oh, there's a new way of packing a ROM with a script that then installs the kernel so I guess it's all together now on Ineffabilis. Here's a link to the MikMik forum where they still have the stock rooted kernel as a separate download:
Just take off the part of the name before PH98IMG.zip, put it on your external sd card. Do a battery pull, then reboot into bootloader by holding volume down + power. It will flash it and I think reboot. Then delete the PHzip file after that.
Don't know if it will help...
Oh... when you flashed Ineffabilis, did you restore any data from a backup? If yes, try flashing again and not restoring any data, just set up everything again manually. Also, if you restored any data from another phone's backup that could have caused problems. Basically you don't want to restore data from a different ROM.
Click to expand...
Click to collapse
This is a clean SD card, and I didnt create a backup because I couldnt get the phone past Hboot when it was doing boot cycles previous to the root. I re-ruu'd right now. And im starting from scratch. I used clockwork before, Im trying amon ra now.
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....