I just want to know if there is a way to make the Nexus Wipe everything?
I am able to get to the recovery menu (I have clockworkMod).
I do not have any backup as the phone is new and I just installed arabic font from a source and it messed it up!
I tried clearing the cache but nothing works. I am searching for a built-in method to wipe everything and restore to factory but it seems it does not exist.
All I found was a link to a rooted 2.3.3 (from xda forum) and it said to put it in the backup folder of clockworkMod and ask to restore and it should work.
I tried flashing with the recovery img from http://forum.xda-developers.com/showthread.php?t=895545 but it did not do anything.
I am downloading the 90mb backup and hope it works.
jsaade said:
I just want to know if there is a way to make the Nexus Wipe everything?
I am able to get to the recovery menu (I have clockworkMod).
I do not have any backup as the phone is new and I just installed arabic font from a source and it messed it up!
I tried clearing the cache but nothing works. I am searching for a built-in method to wipe everything and restore to factory but it seems it does not exist.
All I found was a link to a rooted 2.3.3 (from xda forum) and it said to put it in the backup folder of clockworkMod and ask to restore and it should work.
I tried flashing with the recovery img from http://forum.xda-developers.com/showthread.php?t=895545 but it did not do anything.
I am downloading the 90mb backup and hope it works.
Click to expand...
Click to collapse
It will work Don't worry the I've not yet heard of anyone actually successfully bricking their Nexus S and you're far from being bricked.
The 2.3.3 worked fine an everything got recovered from titanium backup of 2.3.2 (even the SMSes and Emails)!
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.
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 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.
Due to problems with Google Services on my rooted Galaxy S5 (SM-G900F) I opted for a reset from TWRP and it returned to a condition where after some initial screens it was just stuck at "Checking for Updates" so I went back into TWRP and told it to wipe the other partitions. Whoops - now I have no OS (I was sort of assuming that the factory reset OS was somewhere else)
Which is the stock ROM for my Region - UK, unbranded - where do I get it from and how do I load it using Odin and/or TWRP?
TIA
Hello,
Did you make a nandroid backup of your stock ROM or a nandroid backup of a custom ROM if you installed one? If you have a nandroid backup of either of those then you can restore them in TWRP by choosing the restore option and then your nandroid then swipe the slider at the bottom of the screen. If you installed a custom ROM at any time before this and you still have the ROM file then you can reflash the ROM and Gapps.
If you don't have a custom ROM stored anywhere but can still get to recovery, then you can download any of the custom ROMs compatible with your device and a Gapps package that matches it and put them on your extsdcard then boot to recovery and flash the ROM and gapps, do the normal wipes in recovery after flashing, the normal wipes(wipe data/factory reset, wipe cache and wipe dalvik cache), DO NOT CHOOSE THE ADVANCED OPTIONS THAT LET YOU WIPE PARTITIONS.
Check this thread to see if it is your stock firmware, it SHOULD be but double check first, it also has instructions for rooting again and installing recovery.
http://forum.xda-developers.com/galaxy-s5/development/stock-rom-root-recovery-sm-g900f-t2967725
If that doesn't work then go to Sammobile.com and search for your stock firmware by using your device model number.
The firmwares can sometimes be found at samsung-updates.com also.
Find the right firmware for your exact model number and flash through Odin.
For further assistance, post your question in the forum linked below.
http://forum.xda-developers.com/galaxy-s5/help
Good luck.
Droidriven said:
Did you make a nandroid backup of your stock ROM or a nandroid backup of a custom ROM if you installed one?
Click to expand...
Click to collapse
Sadly not - wasn't expecting to need it, thought it would revert to factory default - I have Titanium backup of apps and data.
I am hopefully a few minutes away from downloading the stock ROM and hopefully can reflash that using ODIN.
KD
colehill said:
Sadly not - wasn't expecting to need it, thought it would revert to factory default - I have Titanium backup of apps and data.
I am hopefully a few minutes away from downloading the stock ROM and hopefully can reflash that using ODIN.
KD
Click to expand...
Click to collapse
Making nandroid backups in recovery is the most important and valuable function of custom recovery, flashing ROMs is its' secondary purpose Android is not like PC with a recovery partition that restores a factory IMG, on PC that factory IMG is stored in a recovery partition. The factory reset feature in stock android does not restore an IMG, it deletes all data from the user partition and leaves everything in system partition the way it is, if you delete a system app and then do a factory reset then you will still not have the system app that you deleted. Anything you modify in system remains the way you modified it if you use the factory reset option. You should only use the factory reset in recovery, not the factory reset in system settings when you have a rooted device with custom recovery.
I'm sure that when you found the recovery, the directions had to have mentioned making a nandroid backup of your stock ROM before flashing anything, your present situation is why you do that, so that if anything goes wrong then you can easily restore to the one ROM that you know for sure works with no issues.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
I'm sure that when you found the recovery, the directions had to have mentioned making a nandroid backup of your stock ROM before flashing anything, your present situation is why you do that, so that if anything goes wrong then you can easily restore to the one ROM that you know for sure works with no issues.
Click to expand...
Click to collapse
I installed the TWERP recovery as part of the rooting operation and I didn't pay any attention to the backup option - I thought that's what Titanium did.
I am learning and will make sure that I take a Nandroid backup once I have it back up and running. Life would be so much simpler if only Samsunng didn't stuff their 'phones with bloatware that can't be deleted in stock mode.
KD
colehill said:
I installed the TWERP recovery as part of the rooting operation and I didn't pay any attention to the backup option - I thought that's what Titanium did.
I am learning and will make sure that I take a Nandroid backup once I have it back up and running. Life would be so much simpler if only Samsunng didn't stuff their 'phones with bloatware that can't be deleted in stock mode.
KD
Click to expand...
Click to collapse
Titanium backup can only backup data that you installed or downloaded, it does not backup anything that comes on the phone itself, that is what custom recovery is for.
When following guides to mod your device, read and understand ALL instructions before you even make the first move to touch your device. Get used to being thorough about reading and understanding first or you'll end up in a mess, possibly even hard brick your device, all it takes is one wrong move. Not all mistakes are fixable with android devices.
Sent from my SCH-I535 using Tapatalk