Htc EVo4g
Rooted EVOlved Rom - Recharged Final
hdmwin Poon kernal
latest radios
This morning I open Titanium to restore an app.
! Updates! Change log first item:
"De integrate dalvik and save rom"
Im often low on rom so yea lets do that.
I find the option in tools. De integrate.
Infinite loop.
I tried reinstalling my kernal.
infinite loop.
cleared dalvik and cache
infinite loop
clear batt stats
infinite loop
plain old 'reboot' from recovery. infinite loop. shut down from recovery. infinite loop.
short rain dance about the living room waving phone above my head. infinite loop
Ran circles in living room so fast as to slow time to a stand still while bp. infinite loop.
I have not reinstalled the rom which is on the card for the ready.
Id like to avoid that if possible.
Suggestions?
I don't think it's avoidable. You are going to have to reinstall the ROM. As a rule of thumb, whenever I make any changes to my system, even if it is something as minor as changing a font or a boot screen, I make a back up.
lowandbehold said:
I don't think it's avoidable. You are going to have to reinstall the ROM. As a rule of thumb, whenever I make any changes to my system, even if it is something as minor as changing a font or a boot screen, I make a back up.
Click to expand...
Click to collapse
I have a nand backup.
...Yea I think you may be right. Its sitting next to me rebooting like crazy while I surf net. damnit.
Hmmm I wonder if the 'save rom' by de-integrating is even gonna work. I assume there is no rom. I figured Titanium, awesome as it is, wouldnt steer me wrong. cest la vie.
Here we go. Reflash. Well I was gonna check for new versions anyway.
I mean I have a nand backup but I also have the rom on my card. Im just gonna straight flash the rom. I wonder if I should be nand restoring instead.
All is well.
Reflashing rom did the trick. I dont have any saved memory though... :/
lol Im tempted to try it again.
Does anyone know anything about integrating dalvik into rom? Does this save memory? Is it worth it?
Related
I'm a bit stuck here. I've been running MIUI (1.7.9) for a month or so on my OG Droid. I decided that it was time to update. I flashed the latest version (1.9.9), and started restoring apps, data, and system info. Apps and data restored fine. When I restored system information, it just automatically rebooted. Now it gets stuck in a boot loop, where I see the MIUI load screen and then the lock screen. I get maybe 4 seconds before it either freezes or reloads. If I try to reboot in recovery during that time, it freezes during the reboot.
I also can't boot into recover. If I hold down X when starting up, the phone won't turn on. The screen brightens (but stays black) and then goes off. It keeps doing this until I let go of X.
I'm thinking I need to flash an SBF file via Bootloader. I'm a bit paranoid that I'll mess it up. I'm not sure which SBF to use now, and I really don't want to brick this phone if possible.
I would really appreciate any help. Thanks.
how did you solve your problem? i'm in the same situation
irafcummings said:
I'm a bit stuck here. I've been running MIUI (1.7.9) for a month or so on my OG Droid. I decided that it was time to update. I flashed the latest version (1.9.9), and started restoring apps, data, and system info. Apps and data restored fine. When I restored system information, it just automatically rebooted. Now it gets stuck in a boot loop, where I see the MIUI load screen and then the lock screen. I get maybe 4 seconds before it either freezes or reloads. If I try to reboot in recovery during that time, it freezes during the reboot.
I also can't boot into recover. If I hold down X when starting up, the phone won't turn on. The screen brightens (but stays black) and then goes off. It keeps doing this until I let go of X.
I'm thinking I need to flash an SBF file via Bootloader. I'm a bit paranoid that I'll mess it up. I'm not sure which SBF to use now, and I really don't want to brick this phone if possible.
I would really appreciate any help. Thanks.
Click to expand...
Click to collapse
what information did you recover?the info might mismatch because the roms differ.Also try flashing a new recovery like cwm or AmonRa
Also if you restored the system directory when you did a restore, its like building two houses on top of each other, its 2 full houses, so both will crash because of the pressure. It probably just installed the system restore on top of the update, did you do a data wipe? Furthermore, if you look in the folder with your backup data, your should only restore the data portion rather than doing a full phone restore! so in the future, do a full wipe before reporting, and also, store the backup in a remote area, but put your data folder back in the original location and install it!
Sent from my PG86100 using XDA App
I ended up flashing CWR via an SBF file. It seemed like CWR just got corrupted somehow. From that point, I was able to restore from the nandroid that I created prior to updating. Hope that helps.
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 installed avast mobile security and set everything up as a root user. I'm on the stock ROM and as soon as I was done setting everything up I rebooted and now Im' stuck in a boot loop. It does not boot loop every time... sometimes it boots up and after about a minute it reboots itself, then bootloops.
I removed avast as an administrator / rebooted / then did a clear data and uninstall. Same thing happens so I booted into amon and did a clear cache and dalvik cache.
I've also booted into Amon and wiped all caches. Still no go and I notice that I'm not getting any signal bars (yes, I remembered to put the cover back on). Any help would be greatly appreciated...
Try this.. http://forum.xda-developers.com/showthread.php?t=1394659
sent from ics land
edit: try what the person above me posted first.
Are you on the stock kernel too? I would recommend doing a full nandroid backup and an internal SD card backup and RUU from scratch if you can't get the loops to stop.
I ran avast! for a while with no issues. Could be the link above is what you need.
Thank you all, trying option #1 now. I do have a Nandroid backup I did after I first rooted, and I am on the the stock Kernel.
Holy Cow, it was set to WCDMA Preferred! I'm really surprised that avast changed that setting. I put it back to the correct setting and now my signal is back. I'm rebooting now to see if it sticks.
Thank you all a ton! I'll post back in a few and let you know if that did the trick *fingers crossed*....
Update: Been about 15 minutes and no bootloop or auto reboot so the fix seemed to have worked. Once again, thanks a ton you guys for the help, I appreciate it.
I doubt it was avast that did it. It seems to happen randomly to certain people.
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.
So I have had Cyangenmod 10 installed for several months now and it's been working fine until I would say the last 2 weeks. Now, sometimes it will lock up or slow down and when I restart it, it will get stuck on the cyangenmod logo and never fully boot. After several restarts, I can sometimes get in and all is fine. But today, I have rebooted the Nook Tablet about 10 times now and the Cyangenmod logo will spin for a bit, then stop and then spin and then stop, etc but I can never get in
Ideally, I don't want to restore as I have a number of things on the Tablet that I want to keep. Any suggestions before going that route?
Try going into recovery and wiping cache and dalvik-cache, and then reboot. When oddball things happen, this should be your first trouble shooting step.
Good luck
Sent with my Dinc4G
tried the wipes and still gets stuck on the cyangenmod logo..just spins and stops for a bit, then spins some more
any other ideas
Titanium backup the apps/data you want to keep then full wipe - data/factory reset.
Sent with my Dinc4G
can't do titanium backup if I cant even get passed the cyangenmod logo
Ya good point.
You may have to reflash the rom (or another rom) after a full wipe. I know you are trying to avoid this, but you may not have a choice. You should, however be able to restore your data through advance restore in recovery (make sure you do a backup first though). And it is possible something you put on your nt is causing this - not likely but possible.
Had you done any mods or such on you nt prior to this?
Edit - Another thought too, try flashing the latest update of cm10.1, Just wipe cache and dalvik cache. Flash over the top your current build.
Good luck
Sent with my Dinc4G