Hi,
I had my first experience with CWM, to try to get my Gtab working again, last night.
The folks on the IRC helped, and what I ended up doing was to use CWM to re-partition, then install stock TNT.
So, I'm wondering is: When is a re-partition (using CWM) recommended, i.e., "best practice"?
In particular, is it best to ALWAYS re-partition before installing a new ROM/firmware using CWM?
Or, is it not necessary?
Also, assuming that I'm always willing to lose everything (apps and data) on the Gtab, is there any downside to always doing a re-partition before flashing a new ROM?
Thanks,
Jim
jimcpl said:
Hi,
I had my first experience with CWM, to try to get my Gtab working again, last night.
The folks on the IRC helped, and what I ended up doing was to use CWM to re-partition, then install stock TNT.
So, I'm wondering is: When is a re-partition (using CWM) recommended, i.e., "best practice"?
In particular, is it best to ALWAYS re-partition before installing a new ROM/firmware using CWM?
Or, is it not necessary?
Also, assuming that I'm always willing to lose everything (apps and data) on the Gtab, is there any downside to always doing a re-partition before flashing a new ROM?
Thanks,
Jim
Click to expand...
Click to collapse
Probably not a downside but also unnecessary. I only do it if I am completely restoring my tablet with Nvflash, or if something I do causes my tablet to bootloop. Other than that I don't see the need.
When I go all the way back to stock I will do both items with "wipe" in the name on the first clockwork page. I also wipe the dalvik cache, and partition the sdcard to 2048, and 0. Then I run Nvflash to restore back to the very first TnT.. About as stock as you can get.
Related
I flashed tntlite 4.4.0 and things were going well, when I stupidly deleted a systemfile.
So I thought I'd reflash to fix that. That didn't work.
So I tried the NVFlash to reflash it. That got me into a boot loop situation.
I've tried the FORMAT.ZIP (http://forum.xda-developers.com/showthread.php?t=974422).
Still no joy.
Just boot loops. I'm really running out of ideas here. Any suggestions, besides making a nice black door stop out of it?
You need to clear cache and do a data wipe. Might even need to repartition your sdcard. Modify your nvflash to include clockworkmod. The instructions can be found with the bekit 1105 nvflash instructions.
Did that.. Went to Advanced, repartition SDCARD and it seems I'm close to being back in the game..
Repartition 2048 and 0. If that doesn't do it I don't know what will.
Well, it boots into the OS now.. Still need to setup a few things though.
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.
I recently rooted my droid charge for the first time. I still really don't know what I am doing but I did the cwm recovery with odin. Then I had pbj OC and gummycharged 1.8.5 in a zip file on the phone and I did not use odin with them. I want to try out humble because I want to try something different. But I want to use the theme ADW minimalist metallic. Is there a certain ROM that has to be used with this theme.
Another question I have is if I do a wipe via recovery mod, will I have to reinstall CWM with odin and redo pbj OC?
Thanks, sorry once again for noob questions. If anyone is able to help me via skype or some kind of instant message/mic program I'd be very appreciative. Ill be on for another hour or 2 tonight.
EDIT: If i do a factory reset on my phone will it unroot it and put it back to stock? On a few guides i see it where it says "wipe/factory reset" then next line it will say "wipe cache". Does this mean to go through cwm and wipe it. Then go to privacy and factory reset, or do they both do the exact same thing. And I dont know what wipe cache means. Thanks
PM me if you are able to skype/IM me.
I went through the same rooting process you did and did a factory reset and it won't make you lose root and you will still have CWM and whatever kernal you installed. By the way I always wipe cache when I do a factory reset to be on safe side.
Since you can't use CWM to backup in nandroid then once you do a factory reset to try out another rom you lose all your programs, settings etc and have to reinstall.
A program in the market called "Samsung Odinmaker" is like nandroid in that you can make as many backups of your system as you like thus making it very easy to switch roms and play around
So to try another rom all I gotta do is factory reset, put the zip of the rom in the sd card and go from there?
I dont plan on it but is there a way to try a new cwm or kernal.
Thanks
dapperdanman55 said:
I recently rooted my droid charge for the first time. I still really don't know what I am doing but I did the cwm recovery with odin. Then I had pbj OC and gummycharged 1.8.5 in a zip file on the phone and I did not use odin with them. I want to try out humble because I want to try something different. But I want to use the theme ADW minimalist metallic. Is there a certain ROM that has to be used with this theme.
Another question I have is if I do a wipe via recovery mod, will I have to reinstall CWM with odin and redo pbj OC?
Thanks, sorry once again for noob questions. If anyone is able to help me via skype or some kind of instant message/mic program I'd be very appreciative. Ill be on for another hour or 2 tonight.
EDIT: If i do a factory reset on my phone will it unroot it and put it back to stock? On a few guides i see it where it says "wipe/factory reset" then next line it will say "wipe cache". Does this mean to go through cwm and wipe it. Then go to privacy and factory reset, or do they both do the exact same thing. And I dont know what wipe cache means. Thanks
PM me if you are able to skype/IM me.
Click to expand...
Click to collapse
Check your pm
Sent from my SCH-I510 using XDA Premium App
hrdc69 said:
I went through the same rooting process you did and did a factory reset and it won't make you lose root and you will still have CWM and whatever kernal you installed. By the way I always wipe cache when I do a factory reset to be on safe side.
Since you can't use CWM to backup in nandroid then once you do a factory reset to try out another rom you lose all your programs, settings etc and have to reinstall.
A program in the market called "Samsung Odinmaker" is like nandroid in that you can make as many backups of your system as you like thus making it very easy to switch roms and play around
Click to expand...
Click to collapse
Thanks so much for this tip.
The only thing that has kept me from trying new roms was the hassle associated with not having a nandroid to restore if I didn't like the new rom.
I'm currently on Humble 1.2 and will flash the Humble 2.0 when I get home because I guess Odin doesn't work for Mac.
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.
I've flashed a couple ROMs without any issues, now after I do a factory reset, then try to wipe data in TWRP, it always fails. I still can wipe cache and Dalvik, but any ROM I try to install also fails. Anyone know what I can do to get the data wipe working? I suspect that's why my ROM installs are failing.
Thanks for any help you can give!
crjjr said:
I've flashed a couple ROMs without any issues, now after I do a factory reset, then try to wipe data in TWRP, it always fails. I still can wipe cache and Dalvik, but any ROM I try to install also fails. Anyone know what I can do to get the data wipe working? I suspect that's why my ROM installs are failing.
Thanks for any help you can give!
Click to expand...
Click to collapse
post a little more information on what you are getting when they fail, ie; what rom are you on, what are you flashing, are you unlocked, rooted? Think if you factory reset you might have lost root and may have to try again, or it may have messed up your unlocked bootloader.
Another thing to check is to make sure you have MD5 Check unchecked. IF it is checked, and you didn't download the MD5, it will fail your install
also, make sure you are flashing VZW Roms; with a lot of different versions out there, those ROMs made for sprint, at&t and TMO are likely to fail.
and as a last resort, might want to odin back to stock and try again. sometimes something gets out of whack and that's the only resort.
goldsmitht said:
post a little more information on what you are getting when they fail, ie; what rom are you on, what are you flashing, are you unlocked, rooted? Think if you factory reset you might have lost root and may have to try again, or it may have messed up your unlocked bootloader.
Another thing to check is to make sure you have MD5 Check unchecked. IF it is checked, and you didn't download the MD5, it will fail your install
also, make sure you are flashing VZW Roms; with a lot of different versions out there, those ROMs made for sprint, at&t and TMO are likely to fail.
and as a last resort, might want to odin back to stock and try again. sometimes something gets out of whack and that's the only resort.
Click to expand...
Click to collapse
Right now I'm on Liquid Smoot RC 7 that I've restored from Backup. I've also went back to my stock rooted backup and tried to install one. My bootloader is unlocked, and I'm rooted. I always check the bootloader before I boot into recovery.
I'm also only using ROMs in the VZ download list, like CleanRom (which failed), the JellyWiz (also failed). Even tried to go to Liquid Smooth RC 9 and it failed. The MD5 Check is unchecked.
Thanks for the advice, seems we think the same way. I just sooooo don't want to use Odin. I did it once, and didn't enjoy it at all.