Apologize for my noobiness. Just rooted Droid X for first time. Went fine and successfully flashed MIUI ROM first and then Liberty. Saved versions each time while in recovery mode. Now I want to go back to my saved MIUI ROM. Do I redo original flashing process again (wipe data, caches and install from .zip) or do I just "restore" saved ROM? How is that done?
Restore
Sent from my DROIDX using XDA App
I may be wrong on this one, as I haven't gone back to 1st init (Liberty) roms in quite some time...
But you might have problems restoring the MIUI backup.
If you do...
Simply flash the miui zip.
Boot up.
And then get back into recovery and restore.
Thanks, was able to get back into MIUI with restore.
Thanks , that worked for me too.
Related
So, I'm a bit new around here and to rooting and flashing roms. I recently have been flashing rooms directly from rom manager. Everything was fine for weeks until I recentely tried flashing a rom by RVU. Now I'm stuck in the stock evo 4 g load screen and it keeps loading over and over. Any suggestions ? Is there away back into the boot loader ?
Turrubiates said:
So, I'm a bit new around here and to rooting and flashing roms. I recently have been flashing rooms directly from rom manager. Everything was fine for weeks until I recentely tried flashing a rom by RVU. Now I'm stuck in the stock evo 4 g load screen and it keeps loading over and over. Any suggestions ? Is there away back into the boot loader ?
Click to expand...
Click to collapse
To get back to the bootloader, you'd need to pull the battery (won't hurt anything) and put it back in. Then hold the power button and volume down. That will get you to the bootloader
What do you mean you tried flashing a rom by RVU? I'm confused. RUU is rom utility update, or rom update utility, or something ike that. But if you ran an RUU it would put you back to completely stock.
If I were you, and in your situation, I'd pull the battery, boot to bootloader, and see if you can still get to your recovery. If you can, I'd try wiping everything then either restoring a nandroid backup if you have one, or a fresh install of a ROM. If you don't have recovery, post back and we'll see what needs to happen to get you back up again.
Well, the rom I flashed was created by team RVU....at least that's what it said. So, I made it as far as recovery. But by wipe you mean a wipe back to stock? I'm in as far as my clockwork mod recovery screen. Kinda lost now !!
Turrubiates said:
Well, the rom I flashed was created by team RVU....at least that's what it said. So, I made it as far as recovery. But by wipe you mean a wipe back to stock? I'm in as far as my clockwork mod recovery screen. Kinda lost now !!
Click to expand...
Click to collapse
Okay I gotchya now, although I don't think I've been informed of RVU before, I'll have to check it out. Anyways, thats good that you can still get to recovery. So you have never used it before? Just did everything from ROM manager before huh? I'm not familiar with clockwork recovery, as I use Amon, I'm trying to remember the little differences. First, you don't have any nandroid backups do you? Prob not if you're not familiar with clockwork and had never created a nandroid backup before! I'm not sure if backups made with ROM manager can be restored using CWM, doubtful though. So by wipe, I mean wipe data/factory reset, wipe cache, and wipe davlik cache. You will need to have a ROM on your sd card, so that you can install it from recovery. In order to wipe the dalvik cache using clockwork, i believe it is under the advanced section. Not sure though. Once you have everything wiped, and the ROM of your choice on the main directory of your sd card, choose 'flash zip from sd card' or 'install zip from sd card" or something to that nature, then find the ROM and flash it. If all goes well, you should be able to boot up after that. If you do indeed happen to have a nandroid backup, choose to restore that.
Yup, everything I've done has been through rom manager. Anywho, I peeked around inside some files. Inside my install zip from sd. I found a file labeled nandroid. Could that be the backup that your referring too ? If so, would i still have to wipe my phone ?
Turrubiates said:
Yup, everything I've done has been through rom manager. Anywho, I peeked around inside some files. Inside my install zip from sd. I found a file labeled nandroid. Could that be the backup that your referring too ? If so, would i still have to wipe my phone ?
Click to expand...
Click to collapse
Nandroid folder is for amon RA backups. Clockwork backups are in the clockwork/backup folder.
Have you backed up your previous install? If so wipe all factory reset then restore a backup. Otherwise wipe all and flash a new rom.
This is why you do research and learn how to properly use your phone and any custom recovery before you reach this step. This is why manufacturers have crappy warranty policies because people ruin their phones by being stupid.
Sent from my PC36100 using XDA App
Rem3Dy said:
Nandroid folder is for amon RA backups. Clockwork backups are in the clockwork/backup folder.
Have you backed up your previous install? If so wipe all factory reset then restore a backup. Otherwise wipe all and flash a new rom.
This is why you do research and learn how to properly use your phone and any custom recovery before you reach this step. This is why manufacturers have crappy warranty policies because people ruin their phones by being stupid.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Thank for lending a hand. Instead of trial and error, I simply started a thread. Oh, and thanks for reminding me I'm stupid!!!
Ever since I flashed the leaked rom that was stock for the mt4g, I have had problems flashing any other roms.
No matter what rom I attempt to flash it gets stuck in a boot loop. I have to wipe everything and reinstall the rom 5 or 6 times get it to actually load up and some times it won't take at all. Tried to switch to a miui rom last night just to try some thing different, but no go.
Even the backups I have don't work. From recovery I go to the backups I have and it tells me no files were found when I chose the one I want to restore. One of the backups was made right before I tried to flash the different rom.
I have the good chip. Engineering boot. 3.0.2.4 recovery. and root of course.
And running virtuous fusion now because of reasons posted above.
Sent from my HTC Glacier using Tapatalk
So on a wild hair i decided to try out the latest official firmware. Stupid i know.
Now when i SBF back to the old firmware as stated in the cyanogenmod full update guide, root and bootstrap i can get into CWM recovery but no matter what rom i use it just bootloops. Then if i try to go back into CWM i of course find its the stock 3e recovery.
Did i perma-bork my phone from having custom roms or is there a problem between the chair and monitor? lol
did you wipe data and cache?
http://forum.xda-developers.com/archive/index.php/t-914110.html
DX .605 ROOT
marculous said:
did you wipe data and cache?
http://forum.xda-developers.com/archive/index.php/t-914110.html
DX .605 ROOT
Click to expand...
Click to collapse
Yeah, after I got the first bootloop I tried with apex and liberty and on each attempt wiped data and cache 3x
wipe data and cache, factory reset, then sbf? idk, I've been where you are many times and i always have to go back to the guides to get the process right, in the correct order.
DX .605 ROOT
So is there no reason that the newest OTA* would ruin the ability to put custom roms on?
i wouldn't think so, but i know for cm7 to get on my phone i had to sbf back to 2.2 from the. 596 i was on. guess it depends on the rom. me personally, i just left cm7 for. 605, rooted because i like the blur camera and hdmi support. took off most of the bloat but not all, it jacked up my contacts.
DX .605 ROOT
just treid it again, SBF'd back, rooted, bootstrapped, wiped data and cache and installed Liberty to come to a boot loop. i think .605 has locked me out of custom roms
spockmeat said:
just treid it again, SBF'd back, rooted, bootstrapped, wiped data and cache and installed Liberty to come to a boot loop. i think .605 has locked me out of custom roms
Click to expand...
Click to collapse
can you sbf back to an earlier version?
DX .605 ROOT
Yes I can go back to the froyo SBF without any problem. The issue is, once i do that, then repeat the steps and flash a custom rom, no matter what rom i use, i get a bootloop. the stock SBF and OTA work fine, its just once a custom rom is installed.
spockmeat said:
just treid it again, SBF'd back, rooted, bootstrapped, wiped data and cache and installed Liberty to come to a boot loop. i think .605 has locked me out of custom roms
Click to expand...
Click to collapse
How long did you bootloop? Liberty 3 2.0 can take up to 10 mins to load first time around... I'm assuming you are just seeing the spinning eagle? I thought I was bootlooping too, luckily I got caught up doing something else set the phone down and 10 mins later I had liberty running
sent from my Droid X running Liberty 3
hootowlserenade said:
How long did you bootloop? Liberty 3 2.0 can take up to 10 mins to load first time around... I'm assuming you are just seeing the spinning eagle? I thought I was bootlooping too, luckily I got caught up doing something else set the phone down and 10 mins later I had liberty running
sent from my Droid X running Liberty 3
Click to expand...
Click to collapse
No, it bootloops at the M Logo screen.
the M logo comes up for like 2 seconds, then the phone reboots.
The only variance to this is when i flash the AIO APEX rom, then it just sits at the google logo indefinitely. But on any other rom including Cyanogenmod and Libery it bootloops at the "M" Logo.
There is no reason for this to happen. Sticking at the Motorola's logo shows that something didn't flash correctly.
My only guess is a md5sum mismatch on every rom you are trying to flash, either that or you are trying to flash Froyo roms while using the Gingerbread kernel.
What you should do is SBF again to .602. AFTER you SBF, format data and cache via stock recovery then reboot. If it asks you to update don't take it.
Go to Rootzwiki and download a rom such as Vortex, MIUI, or ICS. Make sure that the md5sum on the rom you select matches the one given in the thread.
Root your phone with Pete's Motorola's Root Tools. Then install ClockworkMod Recovery with Droid 2 Bootstrapper. After you install ClockworkMod Recovery download Rom Manager from the market. Set your device to 'Droid X', and it will download and update ClockworkMod Recovery to the latest version.
Once this is complete, reboot into the newly updated ClockworkMod Recovery (which should be blue), and install your chosen rom.
Once you have installed it wipe data and cache, as well as the dalbik cache. Then reboot your phone.
If you have followed my directions down to every last comma, then your phone should boot into your newly flashed rom. If this doesn't work then something is very wrong. Something beyond my understanding that probably won't be fixable.
Feel free to message me if you have any questions. Best of luck to you!
Sent from my DROIDX using XDA App
infazzdar said:
There is no reason for this to happen. Sticking at the Motorola's logo shows that something didn't flash correctly.
My only guess is a md5sum mismatch on every rom you are trying to flash, either that or you are trying to flash Froyo roms while using the Gingerbread kernel.
What you should do is SBF again to .602. AFTER you SBF, format data and cache via stock recovery then reboot. If it asks you to update don't take it.
Go to Rootzwiki and download a rom such as Vortex, MIUI, or ICS. Make sure that the md5sum on the rom you select matches the one given in the thread.
Root your phone with Pete's Motorola's Root Tools. Then install ClockworkMod Recovery with Droid 2 Bootstrapper. After you install ClockworkMod Recovery download Rom Manager from the market. Set your device to 'Droid X', and it will download and update ClockworkMod Recovery to the latest version.
Once this is complete, reboot into the newly updated ClockworkMod Recovery (which should be blue), and install your chosen rom.
Once you have installed it wipe data and cache, as well as the dalbik cache. Then reboot your phone.
If you have followed my directions down to every last comma, then your phone should boot into your newly flashed rom. If this doesn't work then something is very wrong. Something beyond my understanding that probably won't be fixable.
Feel free to message me if you have any questions. Best of luck to you!
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
^This werk'd! I owe you vigorous oral.
spockmeat said:
^This werk'd! I owe you vigorous oral.
Click to expand...
Click to collapse
wow...........
I'm sorry in advance if it has been asked already.
Do I need to perform any wipes before restoring a backup? I'm currently on CM7.2 RC1 and made a backup of it and want to switch to Defy+ CM9 build for a while then go back to CM7.2. Last time I did it (restored CM7 backup after installing CM9) it just stuck on Boot logo and couldn't move on so I had to start from scratch (new installation). Any guides just mention clicking on restore and that's all. Thanks in advance for an answer!
Can anyone help me? I did as I wrote (switched for a while to CM9 GB build from CM7.2 FROYO) then wanted to restore CM7 backup, tried both with and without wipes (data, cache, dalvik) but it just gets stuck on boot logo and won't move on. What am I doing wrong?
You don't need to do a wipe for restoring a nandroid..
I assume you're using the same recovery with which you made the backup..
neo.ank said:
You don't need to do a wipe for restoring a nandroid..
I assume you're using the same recovery with which you made the backup..
Click to expand...
Click to collapse
Thanks for an answer! I made a backup with CM7 (froyo) recovery and was restoring with the one that was installed along with CM9 (gb). So that was the cause?
You flashed the CM9 ROM through recovery.. right??
ROM's do not change recovery.. Its the same for both..
MarcinRN said:
I'm sorry in advance if it has been asked already.
Do I need to perform any wipes before restoring a backup? I'm currently on CM7.2 RC1 and made a backup of it and want to switch to Defy+ CM9 build for a while then go back to CM7.2. Last time I did it (restored CM7 backup after installing CM9) it just stuck on Boot logo and couldn't move on so I had to start from scratch (new installation). Any guides just mention clicking on restore and that's all. Thanks in advance for an answer!
Click to expand...
Click to collapse
Why don't you try Dual Boot...
refer to the below mentionedlink:
http://forum.xda-developers.com/showthread.php?t=1364659
However, to install CM9 I'm not sure if someone uploaded itsnandroid backup. Please note that to use the backup and restore youcan only use a Nandroid backup as ROM.zip file can not be restored.
What I understand from your post is that you have CM9 rom in zipformat; if this is the case then you can only install it usingInstall from SD card option from Custom Recovery.
---------- Post added at 11:09 PM ---------- Previous post was at 11:09 PM ----------
neo.ank said:
You flashed the CM9 ROM through recovery.. right??
ROM's do not change recovery.. Its the same for both..
Click to expand...
Click to collapse
Wiping data removes Custom recovery. If the new ROM has aCustom recovery then only it appears otherwise we have to reinstallthe Custom recovery.
neo.ank said:
You flashed the CM9 ROM through recovery.. right??
ROM's do not change recovery.. Its the same for both..
Click to expand...
Click to collapse
Yes, i flashed CM9 through recovery.
Rajneeshgadge17 said:
Why don't you try Dual Boot...
refer to the below mentionedlink:
http://forum.xda-developers.com/showthread.php?t=1364659
However, to install CM9 I'm not sure if someone uploaded itsnandroid backup. Please note that to use the backup and restore youcan only use a Nandroid backup as ROM.zip file can not be restored.
What I understand from your post is that you have CM9 rom in zipformat; if this is the case then you can only install it usingInstall from SD card option from Custom Recovery.
Wiping data removes Custom recovery. If the new ROM has aCustom recovery then only it appears otherwise we have to reinstallthe Custom recovery.
Click to expand...
Click to collapse
I think you got me wrong. I was using CM 7.2 Froyo build and made a backup of it through recovery. Then I installed CM9 GB build (wiped data, installed rom, kernel, gapps) and have been using it for a while then I wanted to switch back to my CM7.2 backup (went to the recovery, choosed restore) and it said restoring was succesfull but when I rebooted it just stuck on bootlogo and couldn't move on. Any idea what am I doing wrong?
MarcinRN said:
Yes, i flashed CM9 through recovery.
I think you got me wrong. I was using CM 7.2 Froyo build and made a backup of it through recovery. Then I installed CM9 GB build (wiped data, installed rom, kernel, gapps) and have been using it for a while then I wanted to switch back to my CM7.2 backup (went to the recovery, choosed restore) and it said restoring was succesfull but when I rebooted it just stuck on bootlogo and couldn't move on. Any idea what am I doing wrong?
Click to expand...
Click to collapse
Technically, you haven't done anything wrong. What I've learnt from my experience and posts, this is one heck of a weird phone.
Might be a chance your backup is corrupted or incomplete (highly unlikely bt I've seen it in a device)
Or some other glitch which m nt sure of..
Sent from my MB526 using Tapatalk 2
Wiping data removes Custom recovery. If the new ROM has aCustom recovery then only it appears otherwise we have to reinstallthe Custom recovery.
Click to expand...
Click to collapse
Well as I said..this phone definitely acts senseless sometimes.. a data wipe in my case didn't remove the recovery or bootmenu.
Even reported it in the app thread..
Sent from my MB526 using Tapatalk 2
neo.ank said:
Technically, you haven't done anything wrong. What I've learnt from my experience and posts, this is one heck of a weird phone.
Might be a chance your backup is corrupted or incomplete (highly unlikely bt I've seen it in a device)
Or some other glitch which m nt sure of..
Click to expand...
Click to collapse
It was second time it failed to restore a backup I was trying to do the same a while ago and was unsuccesfull too. Seems like my phone is cursed
Thanks for trying anyway!
MarcinRN said:
Yes, i flashed CM9 through recovery.
I think you got me wrong. I was using CM 7.2 Froyo build and made a backup of it through recovery. Then I installed CM9 GB build (wiped data, installed rom, kernel, gapps) and have been using it for a while then I wanted to switch back to my CM7.2 backup (went to the recovery, choosed restore) and it said restoring was succesfull but when I rebooted it just stuck on bootlogo and couldn't move on. Any idea what am I doing wrong?
Click to expand...
Click to collapse
Now, I understand your issue.
Try using below mentioned steps:
1. Boot into latest/custom recovery;
2. Wipe data/cache;
3. Restore the complete Nandroid backup;
4. Now from advance wipe dalvik cache and battery logs;
5. Now reboot the phone.
Please use above mentioned steps and share the results.
Hope this helps!!
Also try to install latest clockwordmod backup.
check this website for more detail http://www.clockworkmod.com/
@MarcinRN
I think your problem is kernel related, if you switch to CM7 from CM9 with GB-Kernel you must restore the froyo-kernel for CM7.
RATTAR said:
@MarcinRN
I think your problem is kernel related, if you switch to CM7 from CM9 with GB-Kernel you must restore the froyo-kernel for CM7.
Click to expand...
Click to collapse
That's the problem. You can find the kernels on epsy's site. Flash the kernel and restore the nand (there are also options in advanced restore if it still doesn't work, don't know if you need them)
Sent from my MB525 using XDA
Thanks guys I'll try it next time. However, I read somewhere that backup contains kernel too, don't know how much true is in that.
So ive been having this issue and it started all after i tried to flash the ubuntu zips that were supposed to work with a custom recovery. I flashed correctly as everyone said to do so, and my recovery would restart during flashing of the armhf.zip(the larger zip). The armhf.zip would get around 2/3 done and then just restart the recovery but now i am having the problem that i cannot recover from any of my recoveries without my recovery restarting. TWRP will recover the system and then while it is recovering the /data partition it restarts back into the recovery, but does not finish the restore. I am running the latest twrp 2.4.1.0. Please let me know if anyone knows how to fix this issue, or if you have experienced this.
Thanks in advance,
I am wondering if i am going to have to flash factory firmware and rom from google and unroot, and then reroot and what not. Just let me know if any of this would help.
Ran into the same exact thing. Had limited success wiping, restoring nandroid backups, or installing CM10 nightlies. I was finally able to get back up and running this morning using http://forum.xda-developers.com/showthread.php?t=2121673 to do a full wipe then install a clean Android ROM.
Sent from my Nexus 10 using Tapatalk HD
melvis02 said:
Ran into the same exact thing. Had limited success wiping, restoring nandroid backups, or installing CM10 nightlies. I was finally able to get back up and running this morning using http://forum.xda-developers.com/showthread.php?t=2121673 to do a full wipe then install a clean Android ROM.
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
I am able to flash ROMs fine, its just restoring from nandroid that messes it up, did you do the kernel cleaner and superwipe or just the super wipe zip?
Edit: nevermind I just flashed super wipe, and everything is all good now, I can fully restore. Thanks for the help, I appreciate it.
Sent from my Nexus 10 using xda app-developers app