Related
Hi, stupid question here from a relative noob....
I have a Cincinnati Bell Vibrant, that I recently flashed CM7 on (after using Rom Manager to backup up my stock rom). Liked it, but found it too battery-intensive, so I booted into clockworkmod recovery and attempted to restore the backup of my stock rom. It failed on flashing the boot image, and now my phone is stuck on the Vibrant screen, and won't boot. None of the hardware combinations to get into recovery mode are working, but I can get it into download mode. Before I screw things up further, what is the best way to go from here to get the backup restored, or is it even possible at this point?
Thanks
tabbott01 said:
Hi, stupid question here from a relative noob....
I have a Cincinnati Bell Vibrant, that I recently flashed CM7 on (after using Rom Manager to backup up my stock rom). Liked it, but found it too battery-intensive, so I booted into clockworkmod recovery and attempted to restore the backup of my stock rom. It failed on flashing the boot image, and now my phone is stuck on the Vibrant screen, and won't boot. None of the hardware combinations to get into recovery mode are working, but I can get it into download mode. Before I screw things up further, what is the best way to go from here to get the backup restored, or is it even possible at this point?
Thanks
Click to expand...
Click to collapse
This doesn't sound too bad. Basically you want to Odin back to stock. Then reflash the rom you were on, then you can reboot back into recovery and restore your backup. If voodoo was enabled on your backup make sure voodoo is enabled again before restoring(it might work either way, but I'm not sure). When I've done this, I restore a prerooted 2.2 stock Rom without changing the bootloaders, but almost any official stock rom will also work. I'm on the go, so I don't have a link handy, but post back if needed and I will point you to the odin package I use. Good luck.
I also am having some issues with Clockworld recovery. The problem i am having is that when doing a nandriod backup this is the error i am recieving
"E:cant mount /dev/block/mmcblk1p1 (or @)
Cant mount /mnt/sdcard
any suggestions on whats going on?
phone_noobie said:
I also am having some issues with Clockworld recovery. The problem i am having is that when doing a nandriod backup this is the error i am recieving
"E:cant mount /dev/block/mmcblk1p1 (or @)
Cant mount /mnt/sdcard
any suggestions on whats going on?
Click to expand...
Click to collapse
Are you sure the sdcard is good? If so then I would follow the same steps listed above, that way you know your CWR is good.
mattb3 said:
Are you sure the sdcard is good? If so then I would follow the same steps listed above, that way you know your CWR is good.
Click to expand...
Click to collapse
yes it is good because i can see all the videos, pics i have saved in it. Also i put the new ROM on my internal sd card and its there so sd card is def good. What could be causing the problem?
To the op, I would use Odin, no real worries there.
To the other guy with sdcard issue, try moving all files to your PC, format your sdcard, reboot, move files back, flash cwr in ROM mgr, backup work? Move critical files back from PC.
mattb3 said:
This doesn't sound too bad. Basically you want to Odin back to stock. Then reflash the rom you were on, then you can reboot back into recovery and restore your backup. If voodoo was enabled on your backup make sure voodoo is enabled again before restoring(it might work either way, but I'm not sure). When I've done this, I restore a prerooted 2.2 stock Rom without changing the bootloaders, but almost any official stock rom will also work. I'm on the go, so I don't have a link handy, but post back if needed and I will point you to the odin package I use. Good luck.
Click to expand...
Click to collapse
Thanks...that's exactly what I did, except the backup would never quite "take." It completely loaded and cycled through the boot process, but I ended up on a boot-restore loop. So now I've Odin-ed back to stock with the closest build I could find to my stock (which I don't think is out there yet - FROYO.UVJL6.ULTIMOBILE - do you know anywhere to find it?), rooted, and am searching for a good, stable, battery-friendly mod once again.
s15274n said:
try moving all files to your PC, format your sdcard, reboot, move files back, flash cwr in ROM mgr, backup work? Move critical files back from PC.
Click to expand...
Click to collapse
i did try formatting, then moving all the stuff back and am still getting that same error message
^ what rom are you on, if one?
You could always ODIN, and use my option b cwr in the noob guide. I just tested making a backup using trigger 8/22 and know there are no issues. Not really sure whats up on your end. I will say though, I've emailed koush several times that there is an issue with cwr on the vibrant from rom manager, for some it won't even flash.
phone_noobie said:
i did try formatting, then moving all the stuff back and am still getting that same error message
Click to expand...
Click to collapse
try different sd card..or reinstall CWM...
Hello, I need some help with restoring via CWM on the Galaxy S3.
On the S2 I pretty much always used CM9 and jumped back and forth between versions and backing up/ restoring was never an issue.
Now however I am using the stock ROM and its rooted of course.
I made a back up of my stock rom 'cause I wanted to try and install some stuff.
I tried installing the jelly bean transition effects but the install failed, the device felt kinda sluggish (maybe my imagination) afterwards so I decided to restore my phone. The restoring went good but the last ting that happens is that CWM says that restoring /Data failed.
I reboot my phone and I come to the first start up screen where I get to choose language and so on. Everything but photos has been deleted. I try to install CM9, and I do that without any issues. Then I trie to backup my stock backup but I get the same error message and I get back to stock setup page.
My backup is a staggering 6GB, and I read somewhere that CWM can only restore 2GB?
I've deleted that backup and done another one but that is also 6GB.
Does anyone know how to restore from that first restore or how to make future restores work?
undegaard said:
Hello, I need some help with restoring via CWM on the Galaxy S3.
On the S2 I pretty much always used CM9 and jumped back and forth between versions and backing up/ restoring was never an issue.
Now however I am using the stock ROM and its rooted of course.
I made a back up of my stock rom 'cause I wanted to try and install some stuff.
I tried installing the jelly bean transition effects but the install failed, the device felt kinda sluggish (maybe my imagination) afterwards so I decided to restore my phone. The restoring went good but the last ting that happens is that CWM says that restoring /Data failed.
I reboot my phone and I come to the first start up screen where I get to choose language and so on. Everything but photos has been deleted. I try to install CM9, and I do that without any issues. Then I trie to backup my stock backup but I get the same error message and I get back to stock setup page.
My backup is a staggering 6GB, and I read somewhere that CWM can only restore 2GB?
I've deleted that backup and done another one but that is also 6GB.
Does anyone know how to restore from that first restore or how to make future restores work?
Click to expand...
Click to collapse
I had this problem with my sisters Xperia X8,couldn't restore anything that i backed up.It goes for a while and stops.But she had bootloader locked.I was shore that i unlocked her bootloader but i didn't,so i unlocked bootloader,and tried to backup and restore and it worked fine.
I'm not 100% and i don't know is that the way CWM works,but i think in order to restore your data,that you backed up,you have to unlock your bootloader.But it's the best to wait someone who knows this for 100% sure.
If you haven't unlocked bootloader try that,or you don't won't to lose your warranty!?
Good luck!
I don't think that CWM has size limitation but i can be wrong.
Have you made sure that your CWM is up-to-date? if in doubt flash the latest CF-root.
was there ever a resolution to this problem? I did the same thing, rooted the galaxy s 3 and unlock the bootloader. Get a backup of my stock set up using clockwork recovery mod. Now when I try to restore, it does not restore the data. All of my apps look like they are there, but none of them are really installed. I think I can just reinstall all of the apps by hand, I would like to know how to get over this.
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....
Hey guys, had a Note for a little while now and was running stock AT&T GB. I tried upgrading to ICS a couple of times using other threads in this forum, but I'd keep getting stuck in a boot loop and had to revert back to stock AT&T GB to recover my device per Da_G's method here: http://forum.xda-developers.com/showthread.php?t=1506330, and it worked fine.
However, I recently tried one more time to upgrade to ICS, failed and reverted back to stock AT&T GB per Da_G's method, and while my phone turns on, it has become sluggish to the point of being absolutely unusable. Screen touches work fine in some cases, and then take forever to register in the same spot later. The on screen keyboard cannot be invoked - it almost always hangs the phone. And the phone randomly reboots.
I did forget to wipe cache and dalvik cache the last time around while doing the install, and that probably caused this problem. But sine then I've wiped both caches and retried flashing, and also reinstalled a stock AT&T radio in case that was the problem, and also reset the flash counter per braway's methode here: http://forum.xda-developers.com/showthread.php?t=1569206, but to no avail...
My Note is pretty much useless at this time, so any light you guys can shed or any other tack you can suggest is going to help me immensely!
Thanks for the help!
Sid.
Wiping caches is not enough. You need to to a full data wipe/factory reset. At this point why not just flash your phone with Odin.
http://www.samsdroid.com/2012/07/i717uclf6-android-404-usa-at-stock-rom.html
This will fully wipe your phone and install the UCLF6 ICS ROM with matching radio.
Agoattamer said:
Wiping caches is not enough. You need to to a full data wipe/factory reset. At this point why not just flash your phone with Odin.
Click to expand...
Click to collapse
Sorry, I didn't mention - I DID do a factory wipe/data reset and I've been flashing the stock GB ROM via ODIN itself. But thanks for the link to the ICS ROM - I'll try installing this and report back.
Okay, I downloaded the UCLF6 ROM from the samsdroid site (took like 3 hours to download!), performed several factory data resets, cache wipes and dalvik cache wipes on my phone, and then flashed the ICS ROM via Odin. Odin showed "Passed", but the phone rebooted into recovery with a message "failed to mount /system" and "failed to mount /data". I then hit "reboot system now" and am stuck at boot loop. Booted back into recovery, got the same message about not being able to mount system and data. Hit "reboot system" again and back to boot loop...
What the heck am I doing wrong???
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
You do have an ATT i717 and not a canadian version? But I think your phone has other issues.
It is an AT&T SGH-i717. I've used it for 6 months now and it worked fine - it just never let me upgrade it to anything beyond GB... and now it is unusable even with GB.
Do you think it might be a hardware issue? Although, how could flashing and reflashing ROMs impact the hardware?
If the odin flashing did not straighten things out then I have to believe that there are other issues.
sid.asu said:
It is an AT&T SGH-i717. I've used it for 6 months now and it worked fine - it just never let me upgrade it to anything beyond GB... and now it is unusable even with GB.
Do you think it might be a hardware issue? Although, how could flashing and reflashing ROMs impact the hardware?
Click to expand...
Click to collapse
Did you try to flash ICS with Samsung Kies? If that doesn't work, your phone may have developed a hardware problem.
i have had the same issues as well, i am unsure if its me or what but everytime i have tried to flash a tmobile rom on my note which should work it slows down to a crawl i cannot even go through the setup process. I have tried via odin and through cwm touch. the next thing i flashed was t879uvlg3 modem and i was wondering if that was the issue and if so what modem should i flash that way i dont have to use kies for recovery cause man..........thats slow. I even made a nandroid backup and it was slow as well so if anyone has had this issue or any ideas please help me
oort cloud said:
Did you try to flash ICS with Samsung Kies? If that doesn't work, your phone may have developed a hardware problem.
Click to expand...
Click to collapse
My problem is that the phone does not stay on long enough for Kies to detect it - it keeps rebooting on GB. Well, guess it's cooked! Thanks for the help!