Current Status of the Phone:
Inoperable. I am currently stuck in a boot cycle to CWM. I believe the Revo is an unrooted state at the moment.
Things I have done to remedy but failed:
I have: done a complete restore from a previous backup via CWM. I have wiped and installed Gingervolt from SD Card.
How did I get here:
My gingervolt was running a bit slow so I decided to go back to stock (bad idea I know). So I restored a previous backup and was successful. Figured since I was stock I might as well unroot. I unrooted via the All in One Zerg Rush Exploit and it was successful. I then did a Factory Reset / Data Wipe from Settings > Privacy > Data Wipe. This sent me into the CWM boot cycle.
Is there anything I can do?
Thanks for your help to those much more knowledgeable than myself.
Easy fix, follow this
http://forum.xda-developers.com/showthread.php?p=15501302
Sent from my VS910 4G using xda premium
Thank you so much brother
Related
I rooted my droid x using z4 root. That when fine. I backed up my phone with boot strap then cleared my data. I forgot to put the liberty zip on my phone so I resorted it and added the liberty zip. I think I may have forgotten to clear my data again before I tried to restart my phone with liberty ROM. Now it has been trying to boot with liberty and the liberty icon on it for 30 mins. I am not sure what to do now.
Please help me
not sure why you posed that here? anyways, boot back into recovery, even if its stock and just wipe data/factory reset
I am trying to create a back up of my system and the backup errors out in the data portion. It does not say why. Just says error when backing up on /data. I am currently on a rooted stock rom. I have tried using older versions of clockworkmod recovery with no success. Any help would be greatly appreciated. THANKS!
Sent from my DROID3 using XDA App
Are you using Koush's or Hashcode's versions specifically for the d3? Im asking because I thought there was only 2 versions and you said you tried older versions.
Sent from my DROID3 using XDA App
I used them both. Koush offers to flash older recoveries which is only 2 so far. I currently have hashcodes version and the same thing it going on.
I flashed the stock deodex via clockworkmod recovery and it worked like a charm. I then downloaded another zip and tried to flash it then i could no longer boot into clockwork recovery. So to solve that i deleted the d3 bootstrap then redownloaded it and i could boot into it again. So maybe try that then try a backup again? Im not sure why you would be getting an error
Sent from my DROID3 using XDA App
Well, you have to redo the bootstrap on droid 3 after every fresh install of a new ROM. I have tried deleting the bootstrap and reinstalling it with no success. It still errors out on the backup of the data portion. Maybe I might take a risky move and flash a new ROM without a backup and see if it is able to backup the data after the install. I hope I just don't brick my phone or get a bootloop. I would be screwed!
Installed Steel Droid v2 successfully but I tried a backup and it still had an error while back-up up of the data portion. I am at a loss of ideas on what to do next. Any help would be greatly appreciated. Thanks!
mothman57 said:
Installed Steel Droid v2 successfully but I tried a backup and it still had an error while back-up up of the data portion. I am at a loss of ideas on what to do next. Any help would be greatly appreciated. Thanks!
Click to expand...
Click to collapse
Maybe you have a corrupt fat filesystem on the backup destination...
Have you tried to do a checkdisk when connected to the pc ?
I just completed a checkdisk and I even formatted the SD Card yet still the same issue! I then tried to checkdisk the partition of the internal memory yet no success. Thanks for the help though. It is greatly appreciated.
Steel Droid 3 came out today. I installed the new ROM and still it errors out on the /data portion of the backup. Hopefully someone can help me here. Last resort is a full factory reset of the device. I am waiting before I do that.
Is anyone else experiencing these same issues?
Try SBFing, re-rooting and then using the tweaked boot-strapper. When all else fails, start from scratch. If that's still not working, I would venture to guess that your /data partition has issues (which SBFing should fix).
What OS are you using?
I'm having a different problem that maybe some can help with. I just flashed the sbf again, and I've rerooted stock, and now I'm trying to reflash SteelDroid3.
I'm running into an error I haven't had before with CWR. Everytime I try to flash any ROM (from internal or external) it fails - E:Can't open "location" (bad)
I've checked MD5 sums and tried muliple roms, all give the same error.
I started with Hashcodes tweaked Bootstrap, then uninstalled and tried koush's. Neither made a difference. I even tried CWR 5.0.2.5 vs 5.0.2.6 to see if that would make a difference. No luck there either. Even tried reflashing the SBF, still no go after getting reset up.
I can make nandroids, and I can restore nandroids, (restored a debloated I had made earlier no problem) So the only issue is flashing a new rom.
Any idea's
Thanks
I have windows 7 64bit on my computer. Android phone is the 2.3.4 with steel droid v3 ROM. As far as SBF goes, should I use the example on the android development section of RSDlite? And if I preform this, will it delete all my data/apps and restore it to like a factory reset?
Im having similar issues. Backups are not being created properly - the zip files only contain 2 files:
data.ext3
system.ext3
I have one backup that works from a week ago - it contains the following files:
.android_secure.vfat
cache.ext3
data.ext3
nandroid.md5
system.ext3
any ideas why backups wouldn't be created properly? (using the modified bootstrap and CWM)
That is exactly what I am experiencing as well. Just the system and data are being preformed, but the data is not properly finishing.
I think we just need more room on our SD cards. I cleared up a few gigs of info, and now its working just fine. give it a shot.
I dont think that is the issue. I have 14.6gb worth of free storage on my card. It has to be an issue with my internal storage or clockworkmod. I am guessing it is my internal storage.
Sent from my DROID3 using XDA App
Well, I decided to do it. I flashed the original unrooted ROM back on the phone. I have to say it sucked redoing all my phone tweaks, but it did fix the issue. I can now preform back-ups in full! Thanks for all who replied in this forum.
I recently installed a custom ROM (liquid Gingerbread v3.0) onto my Droid 1. But in doing so I lost my root access, and now i can't use ROM Manager to either restore my backups or switch to a different ROM. Some apps say it appears that I have root access but none of the root apps work. I tried using super one click to "unroot" but that froze during step #6. I also tried using it to root and that also froze during step 6. I should also note that the power button on my phone is broke, thus preventing me from booting into recovery mode. What can I do????
I found a way to get into recovery, is there an easy way just to restore stock?
chazm128 said:
I found a way to get into recovery, is there an easy way just to restore stock?
Click to expand...
Click to collapse
Back up and restore. Restore a backup
Sent from my Revolting Revolution. Powered my mtmichaelson.
There's a chance that you may have accidentally denied root access. You could have opened the Superuser app that should have been included with your ROM to ensure that SU requests weren't being blocked that way.
Also, when in doubt learn to use Recovery mode manually. You can't always trust ROM Manager to do everything for you. Sounds like it's best to manually wipe everything you can and install the ROM fresh.
So I just got this phone, and I've been trying to get it up to ICS. I've gone through and was able to complete the ICS update the first time completely, installed Safestrap, etc. Now this is where the issues came in. I did a backup, and then I started restoring some apps from titanium, from an old phone. This is where I started getting constant force closes. Tried fix permissions, went through again, same issue. So I wiped the phone, and went to restore with safestrap - it failed. Now on bootup, it refuses to even boot into safestrap anymore. All I can get is either a blank screen, or motorola recovery menu. By the fact that I can get into the motorola recovery menu, I presume it's not fully bricked, but I know there can be issues with installing on top of Safestrap.
Long story short, my question: In this condition, will flashing the same file I did during the ICS leak installation through Moto Recovery allow the phone to boot? Or will that cause a brick like downgrading from ICS does?
So, just to be sure, you installed one of the ICS leaks correct? Then you installed safestrap 2.0?
Sent from my Droid 4
Yes, that's exactly what I did. Was able to boot up into Safestrap (2.0) and restore through Safestrap, but after wiping /data I got errors with restoring a backup, and after rebooting to attempt it again, Safestrap splash screen no longer appears for me. It has the initial splash, and where the Safestrap splash should be, it just stays blank screen.
Not sure what would have caused this. I don't think you'll be able to flash the zip again since it looks for a .219 system build. Might be worth a shot though. You could also try booting into recovery and doing a factory reset. If neither of those work, try following the instructions for upgrading from one leak build to another.
Sent from my Droid 4
Tried Factory reset already, and attempted just flashing the update anyways - got an error saying build.prop file was invalid/missing?
Now I'm going through the tool steps to swap between ICS builds. At least I'll hopefully get something working.
Though I did do a step I forgot to mention, if that explains why it happened. After the Safestrap restore failed, I tried to do a partial restore of /system and /data. /system restored fine, when I went to do /data it said it was restoring /system in the log - could that have been an issue? A possible mistake in safestrap that overwrote the wrong folder? Or just an issue with the menu?
Doing the ICS switch got it working for me. Now to attempt round 2 and see if I can get into CM9, and Safestrap works right.
More research, root cause : Forgot to install busy box when doing the initial root.
Glad you got it working!
Sent from my Droid 4
Hi guys.
I was planning to install CM 7.2 on my Galaxy Ace for quite a long time and decided to do it today. I have rooted my phone and installed CWM on it, following steps described on the forum. I have made some backups with CWM and My Backup Root. Everything was fine, I have turned my phone off and back on without any problems. However, after doing the factory reset and clearing cache partition via CWM I cannot get past the bootloop animation, it keeps showing my network logo and Samsung logo. After about 5 minutes I have pulled the battery out and restored the CWM backup, but it didn't help. Any idea of what to do to bring my phone back to life?
Thanks,
Draggy
I have flashed my phone with the latest Samsung Galaxy Ace firmware using Odin, but it didn't help - instead of O2 logo there is only the Samsung animation now. I really don't know what to do.
Try a FULL Odin package, and make sure your phone model is the exact one of the rom you are flashing (5830/5830i etc)
Sent from my Ace on Apocalypse Rom
After flashing the new software I had to take the battery out and then go to the recovery mode and do the factory reset again. I think I now need to root my phone again and install CWM, as I've got the stock recovery now. Thanks for help.
Draggy28 said:
After flashing the new software I had to take the battery out and then go to the recovery mode and do the factory reset again. I think I now need to root my phone again and install CWM, as I've got the stock recovery now. Thanks for help.
Click to expand...
Click to collapse
Be careful next time
Sent from my GT-S5830 using xda app-developers app
The problem is that I haven't done anything wrong. I followed the steps from the forum and I would have never thought that the bootloop may happen because of factory resetting the phone. Anyway, I'll try and get the CM working tonight. :silly: