Found this on XDA's main page.... was wondering if a couple devs could check it out and see if it will work on the Atrix2 ICS Leak....
http://forum.xda-developers.com/showthread.php?t=1620255
This opens up the ability to create Nandroid Backups without the need to reboot into Custom Recovery....
Sounds pretty convenient to me!!!
nephillim said:
Found this on XDA's main page.... was wondering if a couple devs could check it out and see if it will work on the Atrix2 ICS Leak....
http://forum.xda-developers.com/showthread.php?t=1620255
This opens up the ability to create Nandroid Backups without the need to reboot into Custom Recovery....
Sounds pretty convenient to me!!!
Click to expand...
Click to collapse
I read about that too. I don't see why it wouldn't work... (EDIT: but, without further due diligence and investigation into the matter I would strongly advise against it - and see Jim's posts below ) ...what's the worst that could happen?
It won't work right on our phone as is.
We might be able to modify it, but that might be more of a pain than just using CWM/bootmenu to grab a quick nandroid.
Just curious.... but why will it not work in the current state with our phones?
The fstab will need to changed, and we can NOT backup boot or recovery and such. and things like /preinstall and other things like are quite different on our phone. There will need to be a good bit of changes made. Just look at what it took to make safestrap and bootmenu work for our phone, and those both came from phones that were much closer to ours.
Ok. Thanks Jim!
nephillim said:
Ok. Thanks Jim!
Click to expand...
Click to collapse
Thanks, as always, Jim!
I was gonna say the same thing actually, but I figured I'd go the other route But, what's the worst that could happen is that it just wouldn't work..
Figured a quick request to a Dev would take me less time then running a nandroid backup..... flashing the online backup... then discovering I need to restore back.... lol
alteredlikeness said:
Thanks, as always, Jim!
I was gonna say the same thing actually, but I figured I'd go the other route But, what's the worst that could happen is that it just wouldn't work..
Click to expand...
Click to collapse
Well the worst would be a brick... if you backup and restore boot, it may not reinstall the signatures, which is why we don't back that up now, and only really backup /system and /data and sdcard, if you really want to.. oh and webtop in bootmenu gets backed up too now.
jimbridgman said:
Well the worst would be a brick... if you backup and restore boot, it may not reinstall the signatures, which is why we don't back that up now, and only really backup /system and /data and sdcard, if you really want to.. oh and webtop in bootmenu gets backed up too now.
Click to expand...
Click to collapse
Right, if you try to restore... wait, boot.img?!? Who would try to do that given our bootloader situation anyway?.. But, it would probably not even backup properly in the first place if the fstabs aren't pointing to the right place... ok.. this is getting too far off of and/or too deep into the topic.. or.. thanks, jim..
alteredlikeness said:
Right, if you try to restore... wait, boot.img?!? Who would try to do that given our bootloader situation anyway?.. But, it would probably not even backup properly in the first place if the fstabs aren't pointing to the right place... ok.. this is getting too far off of and/or too deep into the topic.. or.. thanks, jim..
Click to expand...
Click to collapse
Well, just take a look at that post from the OG subject that is linked here. It shows it backing up /boot, and you can back it up all day long, but restoring it has proven to brick phones, trust me I have done it with the A2 (restoring /boot with a backup, and bricking).
Related
just to give you guys some more confidence i ran trusselo's super easy batch scritp on my dad's windows 7 box to hack 3e recovery.
you can look at my 3e thread in captivate general but do not attempt the kernel swap methods!
use trusselo's script on windows
if it fails or you are on a mac/linux machine then use the manual 3e fix after you root the device.
after i got 3e modded for self signed update.zip zip flashing like the old 2e recovery on 2.1 sgs phones i installed rom manager and chose the captivate cwm recovery. rebooted into recovery, reinstaled packages. phone rebooted, reistaled packages again and i was sucessfully in cwm. from there i was able to backup the stock rom and installed a .zip file that just changed my build.prop (taking baby steps) i could have spoofed the build.prop in many ways but it was for the sake of testing. the flash was successful. i booted up checked for the change and confirmed it was written to /system properly.
then i rebooted and restored the backup. there were some graphical errors including a broken progress bar and a splash screen that covers the menu when the restore is done so it is difficult to navigate, but it is something. success! the restored rom booted and the old build.prop was in place proving it was a successful restore.
tomorrow i will try a replaced vending.apk (market) and the build.prop as a market fix and post it in a thread if it works. if gtg465x doesnt mind i will try to build a rom off his deodexed rom if someone doesnt beat me to it.
i think we need a bounty to buy a dev phone for someone more knowledgable than me. i dont want to go all cowboy and brick this thing, the captivate had much more as far as backup plans so im being more cautious with this one. and even if i had a dev phone i wouldnt be of as much help as others around xda.
Chika Da China Da Chinese Chicken?
Dani897 said:
just to give you guys some more confidence i ran trusselo's super easy batch scritp on my dad's windows 7 box to hack 3e recovery.
you can look at my 3e thread in captivate general but do not attempt the kernel swap methods!
use trusselo's script on windows
if it fails or you are on a mac/linux machine then use the manual 3e fix after you root the device.
after i got 3e modded for self signed update.zip zip flashing like the old 2e recovery on 2.1 sgs phones i installed rom manager and chose the captivate cwm recovery. rebooted into recovery, reinstaled packages. phone rebooted, reistaled packages again and i was sucessfully in cwm. from there i was able to backup the stock rom and installed a .zip file that just changed my build.prop (taking baby steps) i could have spoofed the build.prop in many ways but it was for the sake of testing. the flash was successful. i booted up checked for the change and confirmed it was written to /system properly.
then i rebooted and restored the backup. there were some graphical errors including a broken progress bar and a splash screen that covers the menu when the restore is done so it is difficult to navigate, but it is something. success! the restored rom booted and the old build.prop was in place proving it was a successful restore.
tomorrow i will try a replaced vending.apk (market) and the build.prop as a market fix and post it in a thread if it works. if gtg465x doesnt mind i will try to build a rom off his deodexed rom if someone doesnt beat me to it.
i think we need a bounty to buy a dev phone for someone more knowledgable than me. i dont want to go all cowboy and brick this thing, the captivate had much more as far as backup plans so im being more cautious with this one. and even if i had a dev phone i wouldnt be of as much help as others around xda.
Click to expand...
Click to collapse
Very nice. I am gonna try as well. As long as CM is working I am comfortable pushing my luck a little.
Awesome! Can you post the files or the link to the thread with the files?
slider2828 said:
Awesome! Can you post the files or the link to the thread with the files?
Click to expand...
Click to collapse
just look in the captivate general stickies. i would post a link but there is stuff in there that doesnt apply because we dont have any kernels to flash, i dont want to confuse anybody and cause bricks because someone flashes a sgs kernel. i might make new write up.
Chika Da China Da Chinese Chicken?
I was going to run the PC batch script but the download link actually downloaded a CWM zip.
That's no PC script....no batch file to be found.
EDIT: I am an idiot. Disregard.
slappyjoker said:
I was going to run the PC batch script but the download link actually downloaded a CWM zip.
That's no PC script....no batch file to be found.
EDIT: I am an idiot. Disregard.
Click to expand...
Click to collapse
you think you're an idiot now wait till you read the directions!
Chika Da China Da Chinese Chicken?
Dani897 said:
you think you're an idiot now wait till you read the directions!
Click to expand...
Click to collapse
That was pretty classic. But hey, it sure did work.
1st. Test with CM. Adhoc WiFi Supplicant Zip. (Success)
2nd. Dunno yet.
yep working great
i am backing up in cwm as we speak
samsungcaptivates said:
i am backing up in cwm as we speak
Click to expand...
Click to collapse
So CWM doesn't work in the traditional sense yet?
bella92108 said:
So CWM doesn't work in the traditional sense yet?
Click to expand...
Click to collapse
it does but there seems to be a problem. not sure why, i had no issues flashing small mods for testing but people are having trouble flashing roms. besides that the restore process seems to give me some graphical bugs but works. as far as i can tell it works like it should but i wont discredit others claiming issues mounting the sd card.
Dani897 said:
it does but there seems to be a problem. not sure why, i had no issues flashing small mods for testing but people are having trouble flashing roms. besides that the restore process seems to give me some graphical bugs but works. as far as i can tell it works like it should but i wont discredit others claiming issues mounting the sd card.
Click to expand...
Click to collapse
Hmm, how long is the timeframe between when CWM is updated? I'd love to get rid of all this AT&T [email protected]# they litter my phone with, but I don't want to brick it... and lots of people seem to brick phones without CWM, haha
bella92108 said:
Hmm, how long is the timeframe between when CWM is updated? I'd love to get rid of all this AT&T [email protected]# they litter my phone with, but I don't want to brick it... and lots of people seem to brick phones without CWM, haha
Click to expand...
Click to collapse
you can use titanium backup to remove stuff. also there is odin/heimdall to flash "refuse" from h8rift. they work and are also the safety net unique to samsung phones.
Dani897 said:
you can use titanium backup to remove stuff. also there is odin/heimdall to flash "refuse" from h8rift. they work and are also the safety net unique to samsung phones.
Click to expand...
Click to collapse
Yeah I suppose, I am just hoping that CWM for Infuse will release quick along with new ROMs (Gingerbread? hehe)
bella92108 said:
Yeah I suppose, I am just hoping that CWM for Infuse will release quick along with new ROMs (Gingerbread? hehe)
Click to expand...
Click to collapse
"Release quick?" We've been waiting for weeks already
beatblaster said:
"Release quick?" We've been waiting for weeks already
Click to expand...
Click to collapse
Weeks? Didn't this phone hit stores 5/21? That was 8 days ago.
bella92108 said:
Weeks? Didn't this phone hit stores 5/21? That was 8 days ago.
Click to expand...
Click to collapse
Nah, 5/15. It's been 2 weeks today. Anyway.....
Hey anyone find a way to install cwm install packages using this update.zip?
It says it can't mount the sdcard when I try to install the .zip.
Anyone?
I am thinking of taking the plunge and flashing a custom ROM on my Sensation and have read a lot on how to do it, but had a question from those that have. If before flash a new ROM I make a backup of my current stock ROM with clockworkmod, is it really as easy as going back into clockworkmod and restoring if I want to go back to "factory" settings?
I use my phone for work so don't want to be in a position where I need to spend hours trying to get it back if it does not work. I understand that things happen, but in an ideal world it seems as if it would be easy but wanted to hear it from people that have done this before.
Thank you for your time.
Very easy in fact. If you backup, then you go into the same menu in CWM, and press restore
TheStigx said:
Very easy in fact. If you backup, then you go into the same menu in CWM, and press restore
Click to expand...
Click to collapse
And will put it right back to how it was? Have you done this before? Does it matter if it is a stock ROM or not? It almost just sounds too easy Thank you.
jibninjas said:
And will put it right back to how it was? Have you done this before? Does it matter if it is a stock ROM or not? It almost just sounds too easy Thank you.
Click to expand...
Click to collapse
Many times I've just done what I said in the first post. It doesn't matter It was made so if something goes wrong, or you regret your flashed rom, then you can go back(if you backed up).
I always charge till 100 % before backing up or restoring
Well, I took the plunge. So for so good. It really it simple. Thanks for the help.
Your welcome, I hope everything goes well !
This is probably my first or second post here on XDA but ivr been a member for the last 6 months.. big thanks goes out to all the devs and everyone associated with XDA that helped me learn about this awesome hobby. Anywho i have a problem thats probably easily solved but i cannot figure out what to do. So bear with me this may be a noob question, My device is acting strange, i recently flashed the coredroid ROM and when i reboot i get my splash screen and then a blank screen... i wiped the dalvik cache and wiped everything else prior to flashing so im not sure it could be that, and i cant go into hboot to get back to recovery that way cause i have a radio.zip on the SD card and whenever i go into hboot it just asks me if i want to update by pressing up or dont update by pressing down, then after i choose ither one it wants to reboot...all i need to do is get back into recovery but at this point i dont know how. Can somebody please help me? Ive never had this problem before so im stumped!!! Thanks in advanced for all whom give me insight and point me in the right direction
Get a card reader take the PGIMG off of your SD. Redownload your ROM put it on your SD reflash.
Sent from my Inspire 4G using xda premium
remark517 said:
This is probably my first or second post here on XDA but ivr been a member for the last 6 months.. big thanks goes out to all the devs and everyone associated with XDA that helped me learn about this awesome hobby. Anywho i have a problem thats probably easily solved but i cannot figure out what to do. So bear with me this may be a noob question, My device is acting strange, i recently flashed the coredroid ROM and when i reboot i get my splash screen and then a blank screen... i wiped the dalvik cache and wiped everything else prior to flashing so im not sure it could be that, and i cant go into hboot to get back to recovery that way cause i have a radio.zip on the SD card and whenever i go into hboot it just asks me if i want to update by pressing up or dont update by pressing down, then after i choose ither one it wants to reboot...all i need to do is get back into recovery but at this point i dont know how. Can somebody please help me? Ive never had this problem before so im stumped!!! Thanks in advanced for all whom give me insight and point me in the right direction
Click to expand...
Click to collapse
Please please please please please please please pleaseeeeeeeeeeeee search for your answers. If you're gonna call it a noob question, chances are the answer is out there.
There are couple things you can do. One would be to get an SDcard reader and just delete the PD98IMG.zip off your sdcard. You can also just take out the sdcard and boot into HBOOT.(I think this should work, I remember seeing this as another option to getting a card reader) Once it does its thing you can then put the SDcard back in and boot to recover
Moving forward, always delete PD98IMG.zips off your sdcard immediately after you use them or just create a folder on your sdcard for radios or other PD98IMG.zips you want to always have on you. Remember to always clear wipe data, cache and dalvik cache before flashing. First boots may also take some time especially after full wipes.
thats one thing i was thinking about doing, but as of now im broke till friday and i dont have a card reader :/ do you think there may be any other way of going about fixing this???? or is that pretty much my only option? Thanks for the input!
edit: i posted this right as you did baconstrips, lol thanks forthe help
remark517 said:
thats one thing i was thinking about doing, but as of now im broke till friday and i dont have a card reader :/ do you think there may be any other way of going about fixing this???? or is that pretty much my only option? Thanks for the input!
edit: i posted this right as you did baconstrips, lol thanks forthe help
Click to expand...
Click to collapse
not a problem man! let us know if that got you fixed up
lol thanks bacon, that was a very simple fix.. i took out the SD and booted into hobbot then recovery, i dont know why i didnt think of that...
remark517 said:
lol thanks bacon, that was a very simple fix.. i took out the SD and booted into hobbot then recovery, i dont know why i didnt think of that...
Click to expand...
Click to collapse
hahaha, listen man we've all been there..something unexpected and freaky happens to your phone and logical thinking goes out the door! Glad you got it all worked out though!! Happy flashing sir!
Just out of curiosity, what ROM did you have before you flashed that one? And what steps did you take when flashing the ROM?
Oathdynasty said:
Just out of curiosity, what ROM did you have before you flashed that one? And what steps did you take when flashing the ROM?
Click to expand...
Click to collapse
OP stated he full wiped. My honest guess regardless of the previous ROM since he claims a full wipe was probably a bad flash or a bad download. It happens from time to time.
MMM-BACONSTRIPS said:
OP stated he full wiped. My honest guess regardless of the previous ROM since he claims a full wipe was probably a bad flash or a bad download. It happens from time to time.
Click to expand...
Click to collapse
If you don't run a MD5 (or SHA1 as appropriate) sum, you're borrowing against trouble.
I always calculate the sum when I download, and then again after copying it to my SDcard.
ST3ALTHPSYCH0 said:
If you don't run a MD5 (or SHA1 as appropriate) sum, you're borrowing against trouble.
I always calculate the sum when I download, and then again after copying it to my SDcard.
Click to expand...
Click to collapse
meh, I haven't checked a md5 number for ROM download in quite some time and haven't had any issues...when it comes to radios, well that's a different story. It's good practice to do it for all downloads but with ROMs for me I don't usually check it. I think I've had one problem in the last 4 months due to a bad download.
MMM-BACONSTRIPS said:
meh, I haven't checked a md5 number for ROM download in quite some time and haven't had any issues...when it comes to radios, well that's a different story. It's good practice to do it for all downloads but with ROMs for me I don't usually check it. I think I've had one problem in the last 4 months due to a bad download.
Click to expand...
Click to collapse
I create the torrents for Fuduntu Linux... I made summing a habit after creating a torrent with a bad ISO. Sum twice, upload once.
I see some topics about it. I plan to unlock and root as soon as I get the phone.
Just how important is it to backup this, and anything else I should backup too?
its pretty important.. nothing can go wrong by backing it up. once you root it back it up just in case so your new phone wont be a $600 paperweight!
When you install CWM do a nandroid backup of stock
THE SKATER DUDE said:
its pretty important.. nothing can go wrong by backing it up. once you root it back it up just in case so your new phone wont be a $600 paperweight!
When you install CWM do a nandroid backup of stock
Click to expand...
Click to collapse
That's good to hear. I figured I'd make stock backup too. Having stock rooted won't mess it up I'd presume? Is there an app that does it too?
I have flashed all the roms available, including CM10 and had no trouble with IMEI. Always good to backup though. There's a fairly simple process in the CM10 OP.
joaquinla1 said:
I have flashed all the roms available, including CM10 and had no trouble with IMEI. Always good to backup though. There's a fairly simple process in the CM10 OP.
Click to expand...
Click to collapse
It's built in I assume?
Recon0212 said:
That's good to hear. I figured I'd make stock backup too. Having stock rooted won't mess it up I'd presume? Is there an app that does it too?
Click to expand...
Click to collapse
once rooted and you have installed clockwork mod recovery or TWRP you can make a back up of your whole phone..this will not mess up anything. You can get these two recoveries by using the ez recovery app on google play....... To make a backup in the recovery it will say backup and restore as one of the main options
THE SKATER DUDE said:
once rooted and you have installed clockwork mod recovery or TWRP you can make a back up of your whole phone..this will not mess up anything. You can get these two recoveries by using the ez recovery app on google play
Click to expand...
Click to collapse
Sorry I don't think I was clear, I know about ROMs cause I do it on my Incredible. What I meant was backing up my IMEI
Recon0212 said:
Sorry I don't think I was clear, I know about ROMs cause I do it on my Incredible. What I meant was backing up my IMEI
Click to expand...
Click to collapse
O my bad you have to be rooted in order to run the operation through a terminal emulator app
If you poke around in development there's one for Mac/Ubuntu (I think Ubuntu anyway) that does root and clockwork recovery from your computer, and that's what I use because it's pretty quick and easy.
If it can ever be important you should make a backup of it though. Since fixing things is always a process, having comprehensive resources for it can trim a lot of time.
Using QPST it only took me like 5 minutes to back mine up. Really simple. Then I put a copy of the file on my HD, on my phone's SD card and one on my Google drive. Now I'm sure I can't lose it. LoL they are small files too. Under 500kb
--Sent from GlaDos baked potato
I’d like to look further into it.
I lost my IMEI and other connection data with a bad flash of a CM10 nightly. I had to do a lot of stuff, including manually typing in my IMEI using QPST and then returning my phone to the Verizon store for them to do some factory-reset style stuff to it before I got connectivity again. (Even though I was bone-stock with a re-locked bootloader they still knew I had rooted and messed with the kernel and other stuff, btw). And its not completely correct, even though I am in my home service area I constantly have the flashing grey triangle that says I am doing international roaming. Pretty weird. So long story short, backup IMEI and everything else BEFORE FLASHING ANYTHING.
Legato Bluesummers said:
Using QPST it only took me like 5 minutes to back mine up. Really simple. Then I put a copy of the file on my HD, on my phone's SD card and one on my Google drive. Now I'm sure I can't lose it. LoL they are small files too. Under 500kb
--Sent from GlaDos baked potato
Click to expand...
Click to collapse
That's good, I'll probably put it on my Skydrive then too.
Is there a high chance of losing it on flashing though? I just plan to flash CM10 really.
Recon0212 said:
That's good, I'll probably put it on my Skydrive then too.
Is there a high chance of losing it on flashing though? I just plan to flash CM10 really.
Click to expand...
Click to collapse
Yes, there's always a chance you'll loose it. Better to be safe, than sorry. It only takes a couple of minutes to backup and it may save you the hassle of an exchange.
I backed up the IMEI using this method ( QPST) http://rootzwiki.com/topic/32397-tutorial-imei-backup-nv-with-qpst-us-variants/ It doesn't say should i reset the modems to mtp-adb?
it doesn't say and i would have posted it there but the guy at the end of the thread seems like he is all pissy if you ask any questions. thanks guys
Check out this thread. http://forum.xda-developers.com/showthread.php?t=1852255
Flash the file in the OP in cwm recovery for an easy backup. NOTE: Your bootloader must be unlocked for it to work.
Sent from my SCH-I535 using xda app-developers app
thanks bro i did that one first but they say do all of them just in case. so i did .
Does anyone know why? Its done this since I first rooted and did my first back up.
Sent from my SCH-I535 using xda app-developers app
same here. i think thats just how CWM works.
ddurandSGS3 said:
same here. i think thats just how CWM works.
Click to expand...
Click to collapse
Hmmm. Its only ever done it on my s III. Never did it on my og evo or HTC sensation. Maybe its the version of cwm. Is there an updated one? I have version 6.0.1.2 I know there's a touch version but I heard it was buggy.
Sent from my SCH-I535 using xda app-developers app
There is a bug in the RTC software for this phone. Until that but gets fixed (would have to be by Samsung or VZW) this isnt going to change.
Yeah it sucks but just rename your backups after they are done
Hit me up on Gtalk if u need help @musclehead84
musclehead84 said:
Yeah it sucks but just rename your backups after they are done
Hit me up on Gtalk if u need help @musclehead84
Click to expand...
Click to collapse
I believe if you rename the backup then you will have to remake the MD5 for that backup, which isnt really a big deal. Just wanted to toss that out there.
apacseven said:
I believe if you rename the backup then you will have to remake the MD5 for that backup, which isnt really a big deal. Just wanted to toss that out there.
Click to expand...
Click to collapse
i keep 2 renamed nandroids that i restore regularly and run them without any issues.
apacseven said:
I believe if you rename the backup then you will have to remake the MD5 for that backup, which isnt really a big deal. Just wanted to toss that out there.
Click to expand...
Click to collapse
U can rename them as long as u don't use special characters.
Sent from my SCH-I535 using xda premium
Install rom manager from the market and flash the latest recovery through that. Walla, they're back to normal. Only fixable by Samsung or vzw? Wtf do people get this stuff? This question gets asked every other day and there are STILL people who think its some unsolvable bug.
Imatoasta said:
Install rom manager from the market and flash the latest recovery through that. Walla, they're back to normal. Only fixable by Samsung or vzw? Wtf do people get this stuff? This question gets asked every other day and there are STILL people who think its some unsolvable bug.
Click to expand...
Click to collapse
That's the first I've heard this. I have the latest cwm touch and wrong dates show. Actually I keep seeing people use RM and the recovery isn't flashing right.
Sent from my S3 running Eclipse 2.1
same me
Same me as well,:crying:
I thought that was normal since those numbers are no where near a type of date, I just rename it once booted into ROM.
Sent from my SCH-I535 using XDA Premium App
i suffering same issue too
Imatoasta said:
Install rom manager from the market and flash the latest recovery through that. Walla, they're back to normal. Only fixable by Samsung or vzw? Wtf do people get this stuff? This question gets asked every other day and there are STILL people who think its some unsolvable bug.
Click to expand...
Click to collapse
This is not true. I dl'd my CWM thru RM and my dates are still wrong. Where do u get this stuff?
Imatoasta said:
Install rom manager from the market and flash the latest recovery through that. Walla, they're back to normal. Only fixable by Samsung or vzw? Wtf do people get this stuff? This question gets asked every other day and there are STILL people who think its some unsolvable bug.
Click to expand...
Click to collapse
That's incorrect. The date issue is still there regardless of how it's flashed in. Some people have reported issues with restoring after renaming. Consensus seams to be if you keep the default cwm assigned name and add your own to the end of it without any spaces, any reported issues dissappear.
Boom! Jellybomb biatch!
annoying for sure. I just rename the moment I am done and booted back up.
TWRP date is also wrong but you can rename them anything you want at time backup. :laugh:
The guy meant backup FROM RM, it allows you to rename the backup file before it gets created, then reboots into recovery and creates the backup.
please try to search for your problem before posting... I'm typically the last to complain about that, but geez us...
Seirÿu said:
The guy meant backup FROM RM, it allows you to rename the backup file before it gets created, then reboots into recovery and creates the backup.
please try to search for your problem before posting... I'm typically the last to complain about that, but geez us...
Click to expand...
Click to collapse
TWRP does everything rom manager does except download roms which have been seen to cause bricks. Backups are named before creation also but already booted into recovery. One stop shop. Easier wipe.
prdog1 said:
TWRP does everything rom manager does except download roms which have been seen to cause bricks. Backups are named before creation also but already booted into recovery. One stop shop. Easier wipe.
Click to expand...
Click to collapse
I got to jump on that one of these days to see what all the fuss is about, I'm just loving cwm touch too much! I assume when changing, your existing nandroids will become useless, so would make sense to copy onto your cpu incase they are needed down the road...?
Boom! Jellybomb biatch!