my one s recently developed a strange issue, where if i try to run a nandroid backup, it will mostly finish, then reboot itself without fully completing the process, leaving me with a bunk backup and stuck on one rom for now. also, and the more important of my 2 concerns, is that i don't know if it will do this during a rom flash, nor do i want to find out, seeing as i have no current working backup. doe's anyone have any ideas as to how i could fix this?
mercenaryhmster said:
my one s recently developed a strange issue, where if i try to run a nandroid backup, it will mostly finish, then reboot itself without fully completing the process, leaving me with a bunk backup and stuck on one rom for now. also, and the more important of my 2 concerns, is that i don't know if it will do this during a rom flash, nor do i want to find out, seeing as i have no current working backup. doe's anyone have any ideas as to how i could fix this?
Click to expand...
Click to collapse
At a guess you got a high Hboot so that means when you restore its not restoring the boot.img. You need to flash that in fastboot.
Darknites said:
At a guess you got a high Hboot so that means when you restore its not restoring the boot.img. You need to flash that in fastboot.
Click to expand...
Click to collapse
nope, i have hboot 1.06, and either way that wouldn't, and shouldn't, cause a nandroid to fail during backup, nor for the phone to reboot by itself.
mercenaryhmster said:
nope, i have hboot 1.06, and either way that wouldn't, and shouldn't, cause a nandroid to fail during backup, nor for the phone to reboot by itself.
Click to expand...
Click to collapse
Oh if you mean you cant make a backup try a newer recovery or if its already up to date try an old one.
Edit, just to add I use TWRP 2.2.2.0 and it works fine.
Darknites said:
Oh if you mean you cant make a backup try a newer recovery or if its already up to date try an old one.
Edit, just to add I use TWRP 2.2.2.0 and it works fine.
Click to expand...
Click to collapse
tried using twrp 2.3, 2.2, cwm touch, regular cwm, does it on all of them.
mercenaryhmster said:
tried using twrp 2.3, 2.2, cwm touch, regular cwm, does it on all of them.
Click to expand...
Click to collapse
Not sure then sorry.
Do you have enough free space on your sdcard partition?
You can also try (un?)mounting /data and /system before you start the backup.
Just as an update, I solved my problem. It seems that there were some corrupted files on my data partition, and they were causing nandroid to fail and reboot randomly. So, since I was planning on wiping anyway, I wiped and set up viper again, and successfully made a nandroid after.
Related
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.
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!
I have a friend who has the Skyrocket.
He is rooted and has TWRP installed, but he is still running the stock rom and kernel.
Today his phone randomly rebooted and now it is stuck on the samsung logo. We have been able to take out the battery and boot into TWRP no problem.
We do have a backup from a while back and he is also considering trying a new rom at this point, but we'd like to be able to get this to boot.
Anyone have any ideas on how to get this thing to boot? What could have caused this?
Any help is greatly appreciated.
If the backup is a nandroid backup made in twrp restore that in twrp
jd1639 said:
If the backup is a nandroid backup made in twrp restore that in twrp
Click to expand...
Click to collapse
We do have a twrp backup and can restore it, but we're hoping to find something that will fix the boot issue.
Do you think it could possible fix the problem if we flashed a new kernel and then tried to boot? Can't hurt, right?
iLuvMudkips said:
We do have a twrp backup and can restore it, but we're hoping to find something that will fix the boot issue.
Do you think it could possible fix the problem if we flashed a new kernel and then tried to boot? Can't hurt, right?
Click to expand...
Click to collapse
You could try the kernel our you could also try wiping just cache and dalvik. I assume you're trying to save the data.
jd1639 said:
You could try the kernel our you could also try wiping just cache and dalvik. I assume you're trying to save the data.
Click to expand...
Click to collapse
We aren't trying to save the data. We already have a backup. We're trying to get this thing to boot without flashing a new rom or reverting to a backup.
iLuvMudkips said:
We aren't trying to save the data. We already have a backup. We're trying to get this thing to boot without flashing a new rom or reverting to a backup.
Click to expand...
Click to collapse
read the stickys, this one is right above your post, short answer wipe caches and if still a no go then do a factory reset, still a no go then restore, still a no go then read the sticky
I have root, s-off, using TWRP recovery. I backed up everything on my external SD card with TWRP, ran (what I think is) RUU to get a clean install and was able to update to 4.4.3. After update, I put TWRP back on, and restored all my apps, still have s-off and root. A couple of things didn't restore (like Tasker), but I chalked that up to them probably being on the internal storage and then erased.
Everything else seemed to be working fine, but my WiFi will not turn on, and the default Sense camera opens to a completely black screen.
Any suggestions?
Thanks,
Ian
istrasci said:
I have root, s-off, using TWRP recovery. I backed up everything on my external SD card with TWRP, ran (what I think is) RUU to get a clean install and was able to update to 4.4.3. After update, I put TWRP back on, and restored all my apps, still have s-off and root. A couple of things didn't restore (like Tasker), but I chalked that up to them probably being on the internal storage and then erased.
Everything else seemed to be working fine, but my WiFi will not turn on, and the default Sense camera opens to a completely black screen.
Any suggestions?
Thanks,
Ian
Click to expand...
Click to collapse
To be correct, you are running a 4.4.3 ROM with 4.4.3 firmware right? Also when you try to enable wifi from the status bar does it simply endlessly show its trying to turn it on?
Perhaps a viable option would be to try a factory reset via TWRP, I sometimes encounter issues when doing that after a firmware update. Actually my 4.4.3 was so messed up because of restoring apps that I was forced to go back to my 4.4.2 ROM. Soo as I said, since you have a backup I'd just at least give factory reset a try and if it doesn't fix it then you can restore your backup again.
Try another kernel, I had the same issues
Enviado desde mi unknown mediante Tapatalk
bighleo114312 said:
Try another kernel, I had the same issues
Enviado desde mi unknown mediante Tapatalk
Click to expand...
Click to collapse
I'm kinda new to all this flashing/recovery stuff. How exactly do I use another kernel?
istrasci said:
I have root, s-off, using TWRP recovery. I backed up everything on my external SD card with TWRP, ran (what I think is) RUU to get a clean install and was able to update to 4.4.3. After update, I put TWRP back on, and restored all my apps, still have s-off and root. A couple of things didn't restore (like Tasker), but I chalked that up to them probably being on the internal storage and then erased.
Everything else seemed to be working fine, but my WiFi will not turn on, and the default Sense camera opens to a completely black screen.
Any suggestions?
Thanks,
Ian
Click to expand...
Click to collapse
How did you restore your apps?
jsaxon2 said:
How did you restore your apps?
Click to expand...
Click to collapse
Through TWRP. I put it back on after the update and restored the apps and data (not the system) from the backup I'd made previously.
You could try and flash the stock rom from http://forum.xda-developers.com/showthread.php?t=2874699 through twrp and see if it works for you. Don't wipe anything, just try flashing on top of what you have. Might work.
jsaxon2 said:
You could try and flash the stock rom from http://forum.xda-developers.com/showthread.php?t=2874699 through twrp and see if it works for you. Don't wipe anything, just try flashing on top of what you have. Might work.
Click to expand...
Click to collapse
Do I do that through TWRP or through the bootloader?. Sorry, again I'm still new at this.
istrasci said:
Do I do that through TWRP or through the bootloader?. Sorry, again I'm still new at this.
Click to expand...
Click to collapse
Your posts didn't really make clear what exactly you did: From which rom you took the TWRP nandroid, which rom you restored it back to, what you mean by "you think you ran a RUU", what exactly from the nandroid you restored in TWRP....
Did you restore all of /data? If you did, you restored way more than just your apps and may have compatability issues.
Restoring /data IMHO is not a good idea after doing a firmware upgrade and flashing a corresponding rom.
A better strategy would be to backup just your apps and their data in TiBu and only restore those after you flashed the new firmware and the new rom.
Here's what I would do:
Factory reset in TWRP
Reflash the rom
Reinstall your apps (this time from scratch, next time you'll have a TiBu backup).