Hello all,
I have successfully installed CM7 on my Nexus One. However, I have the following problem with CWM: if I ask it to make a backup from within the recovery or from RomManager, CWM (3.0.0.5, latest version available apparently for Nexus One) makes the backup, but after restarting, I am stuck on the CM7 splashscreen: I see the blue Android on his skateboard and the arrow goes around in circles (left it going for 15 minutes just to be sure).
Also, on a sidenote, when I made the initial nandroid backup in CWM from my stock Froyo, after the backup was done I had to go in RomManager and "fix permissions", because all my resident apps kept crashing with "forced close" errors. No idea where that came from. Restoring that backup did the same thing as well. I did not investigate that issue any more though as I was on my way to a CM7 upgrade anyways.
So I now have a perfectly good install of CM7 running, but I am scared of doing a CWM backup. This is far from an ideal situation, and I would love to be able to resolve this
Thanks for any help
Anyone? I really am quite upset with this situation
Use this instead?
http://forum.xda-developers.com/showthread.php?t=611829
Thanks, I will try it... though I have to admit I am nervous at the idea of having to again reinstall everything. Crossing my fingers!
yannack said:
Thanks, I will try it... though I have to admit I am nervous at the idea of having to again reinstall everything. Crossing my fingers!
Click to expand...
Click to collapse
Uh oh? It is just a custom recovery, no need to reinstall everything. You only flash the recovery and do the backup you cannot now with the broken CWM. (For my phone, there are even flashable zip files so you can switch b/w CWM and AmonRA "on the fly" via flash zip from recovery, not sure there are some for N1, try to search. )
Actually, the current problem I have is that after performing a backup, my phone doesn't boot anymore. The only solution I have at that point is to re-flash a complete ROM (flashing the backup doesn't work either), thus losing everything.
In short: making a backup means I then have to format and said backup is unworkable...
Which is why I am nervous at the idea of trying to make such a backup.
On a sidenote, RomManager is indeed able to flash both CWM and RA recoveries for N1 directly, which is quite nice indeed.
yannack said:
Actually, the current problem I have is that after performing a backup, my phone doesn't boot anymore. The only solution I have at that point is to re-flash a complete ROM (flashing the backup doesn't work either), thus losing everything.
In short: making a backup means I then have to format and said backup is unworkable...
Click to expand...
Click to collapse
I still do not understand why all this. Just flash a working recovery from fastboot (should press power and trackball IIRC on your phone). (And obviously do not use CWM to perform backups when it bricks your phone.)
On another note, flashing removery via ROM Manager resulted in bricked phones for many users, would avoid it personally.
Related
Ok, I just want to cover all my bases and make sure everything is set for me.
I rooted my ATRIX, installed ROM manager pro and Titanium backup pro, backed up my apps and data with Titanium, and flashed clockworkmod with rom manager.
I have the Alien rom and the alien theme downloaded and put on my sdcard.
From what I understand I just click install rom in rom manager and it should all be good correct?
Thanks for any advice! I just want to make sure I'm doing everything correctly.
Jup thats one way to do it. And it is a good method!
So go ahead and flash it if you already haven't done it
Sounds good to me.
should would fine long as your phone likes cwm, i had a lil issues with it myself but i'm running a new rezound that doesn't have the best support with it yet, i switched to amon ra recovery as it seemed to have a lil more to offer and didn't give me a issue with the scripts some roms use, long as that phone is well supported by cwm you should be fine tho
Or you can just boot intoo clockworkmod recovery and select "install zip from sdcard" and point to the zipfile of the new rom. A wipe is usually necessary and also doable from the recovery.
scarbutt11 said:
Ok, I just want to cover all my bases and make sure everything is set for me.
I rooted my ATRIX, installed ROM manager pro and Titanium backup pro, backed up my apps and data with Titanium, and flashed clockworkmod with rom manager.
I have the Alien rom and the alien theme downloaded and put on my sdcard.
From what I understand I just click install rom in rom manager and it should all be good correct?
Thanks for any advice! I just want to make sure I'm doing everything correctly.
Click to expand...
Click to collapse
Well, almost. You also need to unlock the bootloader before you can flash a ROM. You mentioned that you backed up your data using Titanium Backup, which is fine, but you should also create a backup in recovery. That way, if something goes wrong and you end up with a phone that won't get past the boot logo, you can simply boot into recovery and restore your phone to exactly how it was before. Just make sure you have at least 2GB of free space on your sd card so that it can perform a full backup. To perform a backup, turn off your phone, then right as you're turning it on again, hold the volume down button until "fastboot" shows up. Then press the down volume button until you see "Android Recovery." Now press up to enter recovery. From there, navigate to backup. I realize that this isn't necessary, but I soft-bricked my phone the first time I tried to flash a rom, and if I had done a proper backup, it would have saved me a lot of grief.
Hope this helped!
I would also make a Nandroid backup of the current system just in case. Nandroid backups never failed on me when needed. I do believe it is a good "go to" option if a restore backup is needed.
Just my two cents
Hi. I've been using a ROM for the last little while (SlimICS), and I like it, more or less. There's a feature in another ROM (ParanoidAndroid, per-app density), that I'd really like to try out, but this ROM also has a lot of features I don't want (tablet mode) and doubt I would like. I use TWRP as my recovery...if I use TWRP to make a backup of System, Data, Boot, Recovery, .android_secure, and EFS, will I be able to flash this other ROM, then restore the backup to go back to my old ROM after I play with the new one a bit? Will the backup of these items bring me back to exactly how it was before, if I do a Wipe Cache/Dalvik Cache/Factory Reset?
Sorry if these questions are answered elsewhere, I'm just trying to make sure that my limited understanding of all this isn't incorrect, in my specific situation.
If you make a backup through recovery, when you restore, it'll be exactly where you left off, settings and all, when you shut the phone down.
When backing up in Recovery, you are backing up the OS and apps. This is called a nandroid. This does not backup anything on the sdcard.
Yesterday, I flashed a different kernel version on my NS. Before flashing, I did a nandroid backup using Reovery. Unfortunately, the kernel failed to load properly and I was stuck in a boot loop. I restored my backup I have done previously, and my phone was back where it was, few minutes before. It is very easy to do and backups/restores and verified using MD5 checksum.
Keep in mind that some apps put stuff on the sdcard. So if you flash your phone to a new ROM, upgrade apps and then go back to another ROM, it is possible that some apps won't work anymore. I've never seen this happen but this is a possibility.
Hi Folks.
Ok here is my situation, I have a rooted and unlocked TF700.
I flashed Zeus 4 and all worked well, then flashed (after full wipe) PARANOIDANDROID 2.15 and again everything was great,
Yesterday I flashed Baked Bean 4 (again after a full wipe) and apart from some SD issues all seemed ok,
I then decided to restore my TWRP backup of Zeus as I needed to use my 64gig msd card.
After a full wipe and restore Zeus started up but the dpi was messed up (160) I think (way small)
I was seeing loads of FC's and file manager showed my internal SD as being empty. Rebooted to recovery and tried the "Format Data" option
It failed right away with this message "E: Unable to format data."
I have tried flashing the stock .26 rom via TWRP and I have the same issue, dpi set to 160 and internal sd not mounted.
It seems my Internal sd is corrupt
What is the procedure to reformat it via ADB or fastboot? (I have searched but the results I found relate to other devices and I dont want to simply follow instructions that might cause further harm to my TF700)
I have followed the NVflash brick proof procedure and have all relevant files backed up (I did this before flashing the last 2 roms)
Please can some one point me in the right direction
Thanks a lot
Jules
I always wipe cache, system, internal, davic and then do a factory reset.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
When you said that you tried to flash the stock .26 you meant installing not restoring a backup, right? What rom you have on your device right now?
Pretoriano80 said:
When you said that you tried to flash the stock .26 you meant installing not restoring a backup, right. What rom you have on your device right now?
Click to expand...
Click to collapse
Yip extracted the zip from the zip file and copied it to my ext sd and flashed it via TWRP
I have an unusable Zeus4,
Im about to try a full wipe again and then flash .26 again
EDIT
After flashing .26 and selecting reboot I get the "No OS installed! Are you sure you wish to reboot?" message
Looks like the system partition is corrupted, but i'm not sure. I think you should come here on IRC and maybe someone with more experience will help you - - http://webchat.freenode.net/?channels=asus-transformer
Thanks so much Pretoriano80!
With his help on IRC I was able to solve the problem,
In the end I had to return to complete stock, It seems CM10 caused some problems,
You are a a legend dude Thanks!!
:good:
ZaJules said:
Thanks so much Pretoriano80!
With his help on IRC I was able to solve the problem,
In the end I had to return to complete stock, It seems CM10 caused some problems,
You are a a legend dude Thanks!!
:good:
Click to expand...
Click to collapse
This same thing happened to me with my Prime when I was getting ready to send it off for RMA because of a broken HDMI port. Since I was unlocked I was advised to restore to stock before sending it in. However, before I got the chance to do that I started getting the "E: Unable to format data." error that you were. I ended up erasing all partitions from fastboot and putting a note in the box that it wouldn't boot after an OTA. I managed to get away with it and wasn't charged for fixing it
For future reference it would be really helpful to know how you fixed this. Did you do something like what is in this thread: http://forum.xda-developers.com/showthread.php?t=1803343.
Did you ever figure out how CM10 messed up your Infinity? I was running CM9 on my Prime when I got this error. Thanks!
It's hard to say if it was CM10 (or any other custom rom) or TWRP to mess the things up but we managed to get back to stock by replacing the twrp with CWM recovery and installing a modified .30 update package. Was a tricky one but we didn't had to mess with the partitions and that's good.
Pretoriano80 said:
It's hard to say if it was CM10 (or any other custom rom) or TWRP to mess the things up but we managed to get back to stock by replacing the twrp with CWM recovery and installing a modified .30 update package. Was a tricky one but we didn't had to mess with the partitions and that's good.
Click to expand...
Click to collapse
Why did you switch to CWM? Do you have any thoughts on the advantages and disadvantages of TWRP vs CWM?
paddycr said:
Why did you switch to CWM? Do you have any thoughts on the advantages and disadvantages of TWRP vs CWM?
Click to expand...
Click to collapse
Switched to CWM just to make sure it wasn't twrp recovery that somehow was failing to flash the partitions correctly. Tbh so far both do their job and both share the same limitation so far, meaning both fail to restore the boot partition (kernel) so in order to restore successfully (from a nandroid backup) you need to flash the right kernel after restoring is done. Otherwise i like TWRP better and never had issues with it, but i miss the advanced option from CWM, the one that let you format each partition individually.
Pretoriano80 said:
Switched to CWM just to make sure it wasn't twrp recovery that somehow was failing to flash the partitions correctly. Tbh so far both do their job and both share the same limitation so far, meaning both fail to restore the boot partition (kernel) so in order to restore successfully (from a nandroid backup) you need to flash the right kernel after restoring is done. Otherwise i like TWRP better and never had issues with it, but i miss the advanced option from CWM, the one that let you format each partition individually.
Click to expand...
Click to collapse
I'm not certain what you're referring to here. I've restored many times from different TWRP backups (for each custom rom that successfully boots and is half-decent, I make and keep a backup in case I want to jump around and try new things) and I've never had any issues. I am still on the .26 firmware update because I plan to do the nvflash thing. Are you saying that between Zeus v4 (ICS) and various Jelly Bean roms I've been on the same kernel? I gues I just haven't checked.
Anyway, I really love the TWRP recovery and use it with Xoom and Nexus 7 as well. It's so easy to use and always has been reliable.
okantomi said:
I'm not certain what you're referring to here. I've restored many times from different TWRP backups (for each custom rom that successfully boots and is half-decent, I make and keep a backup in case I want to jump around and try new things) and I've never had any issues. I am still on the .26 firmware update because I plan to do the nvflash thing. Are you saying that between Zeus v4 (ICS) and various Jelly Bean roms I've been on the same kernel? I gues I just haven't checked.
Anyway, I really love the TWRP recovery and use it with Xoom and Nexus 7 as well. It's so easy to use and always has been reliable.
Click to expand...
Click to collapse
For me moving between various roms by just restoring a backup never worked like it should. Let's say i'm on CM10 and i want to restore from a stock rom backup, the restore process is done, after reboot the device gets stuck to the first Asus screen and will stay there. Now if i get back to recovery and flash an update. zip containing the stock kernel the device will boot just fine, so definitely the boot image doesn't get restored in my case (with . 26 bootloader ).
Edit: @okantomi: You are using the internal storage or a MicroSD for backup / restoring? I'm really curious how this could work for some and not work for others, i mean same device, same recovery, same bootloader version...
Pretoriano80 said:
For me moving between various roms by just restoring a backup never worked like it should. Let's say i'm on CM10 and i want to restore from a stock rom backup, the restore process is done, after reboot the device gets stuck to the first Asus screen and will stay there. Now if i get back to recovery and flash an update. zip containing the stock kernel the device will boot just fine, so definitely the boot image doesn't get restored in my case (with . 26 bootloader ).
Edit: @okantomi: You are using the internal storage or a MicroSD for backup / restoring? I'm really curious how this could work for some and not work for others, i mean same device, same recovery, same bootloader version...
Click to expand...
Click to collapse
Ok, I only flash a new zip from the internal storage...made myself a "Flashworthy" folder which I keep stocked with newest versions of roms/gapps. I save my TWRP backups to my external microsdcard, as well as my TiBu backups. I have never had a problem restoring from TWRP this way, honestly.
okantomi said:
Ok, I only flash a new zip from the internal storage...made myself a "Flashworthy" folder which I keep stocked with newest versions of roms/gapps. I save my TWRP backups to my external microsdcard, as well as my TiBu backups. I have never had a problem restoring from TWRP this way, honestly.
Click to expand...
Click to collapse
Well, in this case i really have no clue why restoring works for some users but not for all.Dees_Troy, the dev behind Twrp recovery told me that .26 bootloader is to blame for the recovery failing to restore the boot partition, but looks like you have that bootloader version and restoring works good for you... interesting.
Pretoriano80 said:
Well, in this case i really have no clue why restoring works for some users but not for all.Dees_Troy, the dev behind Twrp recovery told me that .26 bootloader is to blame for the recovery failing to restore the boot partition, but looks like you have that bootloader version and restoring works good for you... interesting.
Click to expand...
Click to collapse
It is a mystery. Is there any other info that might be relevant to see why the difference in results? I ask because I would like to understand this device better, as well as potentially help others.
okantomi said:
It is a mystery. Is there any other info that might be relevant to see why the difference in results? I ask because I would like to understand this device better, as well as potentially help others.
Click to expand...
Click to collapse
I don't know, maybe the twrp version and the backup options, like if you are using compression or not, which partitions do you backup (boot, system, data, recovery, cache)...
Pretoriano80 said:
I don't know, maybe the twrp version and the backup options, like if you are using compression or not, which partitions do you backup (boot, system, data, recovery, cache)...
Click to expand...
Click to collapse
I'm using TWRP 2.2.2.1, I back up boot, system and data only, and I don't use compression.
Hi,
So I used the Revolutionary method to s-off and root my phone - this was successful. I then made a full backup using Titanium and a few other things like SMS and contact backups, which are on my laptop now.
I then installed SVHD v1.7.4 using Clockworkmod v4.0.1.4. It ran fine, but try as I might I couldn't load my contacts and SMS back into it. So I tried to restore is back to the stock rom by going into Clockwork's Recovery, wiping cache, data and system.
When I tried to restore to a previous point, it gave me an error message saying system.img, data.img and so on not found, so all restore has been skipped. Now I'm stuck at the 3 splash screen. I can still get into the bootloader though, and can potentially install SVHD again as it's still on the SD card.
A quick search through the forums shows users with similar problems from 2012, but I'm afraid of buggering up my phone further so I'm hoping someone could be so kind as to walk me through what I need to do.
xTheLostProphetx said:
Hi,
So I used the Revolutionary method to s-off and root my phone - this was successful. I then made a full backup using Titanium and a few other things like SMS and contact backups, which are on my laptop now.
I then installed SVHD v1.7.4 using Clockworkmod v4.0.1.4. It ran fine, but try as I might I couldn't load my contacts and SMS back into it. So I tried to restore is back to the stock rom by going into Clockwork's Recovery, wiping cache, data and system.
When I tried to restore to a previous point, it gave me an error message saying system.img, data.img and so on not found, so all restore has been skipped. Now I'm stuck at the 3 splash screen. I can still get into the bootloader though.
A quick search through the forums shows users with similar problems from 2012, but I'm afraid of buggering up my phone further so I'm hoping someone could be so kind as to walk me through what I need to do.
Click to expand...
Click to collapse
Have you make a nandroid backup
in recovery?- sorry i didn`t see it mentioned,...
if you haven`t, then there is nothing to restore...
system ( the whole nand image ) could only be restored,
when it was previously been written...
try to mount sd card- while in recovery,
and look for: Clockworkmod/backups/.....
if there is nothing, i`m afraid you`re ......
asgardr said:
Have you make a nandroid backup
in recovery?- sorry i didn`t see it mentioned,...
if you haven`t, then there is nothing to restore...
system ( the whole nand image ) could only be restored,
when it was previously been written...
try to mount sd card- while in recovery,
and look for: Clockworkmod/backups/.....
if there is nothing, i`m afraid you`re ......
Click to expand...
Click to collapse
Ah sorry, I forgot to mention. Yes, I have two backups in CWM. Neither of which seem to work.
xTheLostProphetx said:
Ah sorry, I forgot to mention. Yes, I have two backups in CWM. Neither of which seem to work.
Click to expand...
Click to collapse
have you been changing recovery version lattely?
what i mean is: if you have, then try to revert back
to the version you used to create nandroid with,
and if you haven`t, then try to grab 4ext recovery-
possibly newest release you can put your hands on,
and try to restore nandroid from there...
...there is also a tool called:
< CWM2update.zip.creator > by @ss429842,
that may partly be a cure for your trouble- perhaps....
asgardr said:
have you been changing recovery version lattely?
what i mean is: if you have, then try to revert back
to the version you used to create nandroid with,
and if you haven`t, then try to grab 4ext recovery-
possibly newest release you can put your hands on,
and try to restore nandroid from there...
...there is also a tool called:
< CWM2update.zip.creator > by @ss429842,
that may partly be a cure for your trouble- perhaps....
Click to expand...
Click to collapse
I don't think I've changed the recovery version, no. But I clearly did something very wrong. I couldn't access my SD card as it's internal and I was afraid I was stuck.
What I've done instead is find the SVHD zip file and installed that. Hopefully this will work and I can at least turn my phone on and proceed from there. It sucks being a noob!
Hi Folks, I hope this is posted in the right forum and sorry if I've missed seeing something similar already here.
I have a rooted Verizon GSIII on which I have been flashing custom ROMs and restoring nandroid backups without any problems for a while now (most recently I've been on Paranoid Android). Today I decided to try out Carbon ROM. I generated a nandroid backup using TWRP, then downloaded the ROM (the most recent nightly) and Gapps zip files using GooManager and flashed these after doing a factory reset. After rebooting the phone it seemed to start up OK... but it got as far as trying to find the network, which it unable to do. After selecting the skip option I then tried to sign in to my WiFi, but the keyboard didn't show up for me to type in the password. So I figured I'd cut my losses and just reboot into recovery and restore my PA backup. I was able to reboot into recovery and restore the backup but the PA backup pretty much did the same thing the carbon ROM did... just looped trying to find the network.
So... I'm not sure what went wrong or what to do next. Any suggestions???
I am able to boot the phone into recovery, but I'm afraid to start messing around too much without help as I'm no expert!
I do have the most recent nandroid backup and several earlier ones that did restore OK on my computer. Is there a way to flash any of these to the phone or to go back to stock?
Any help would be greatly appreciated.
Cheers.
Wipe catche dalvik factory reset then flash fresh batch of rom and gaaps if that works well getting tru start up then flash ur backup thats what i did.. If that dnt work then u gotta go tru odin back to stock