Related
For these steps to work, ensure that your Milestone currently contains an unprotected recovery image (eg. Brazilian 2.0.1 SPF or the vulnerable recovery SPF for 2.1 Milestones).
Also ensure that you have installed the Android SDK so that you can access your phone with ADB.
These instructions are mostly based on user poseiden's guide at alldroid.org, before the site went down and was cleaned up.
How to make a Nandroid backup
Download the ADBRecovery files from here.
Unzip the archive onto the base of your SD card, so that you have a /recovery folder and an update.zip (NOTE: if you had an earlier update.zip, it will be overwritten with the ADBRecovery update.zip, so back up or rename the original update.zip.)
Reboot your phone into recovery menu:
Turn off phone
Press Camera button, then press Power. Hold them both till you see recovery screen.
Press Volume Up and Camera button at the same time till you see the recovery menu.
Run the update.zip.
Connect via ADB and execute:
If you want everything backed up:
Code:
nandroid-mobile.sh --backup
If you don't want your installed apps + data backed up:
Code:
nandroid-mobile.sh --backup --nodata --nocache --nomisc
How to do a Nandroid restore
Ensure the Nandroid backup content is found under your phone's /sdcard/nandroid/console=ttyS2,115200n8 folder.
Ensure the /recovery folder and ADBRecovery update.zip is at the base of your SD card.
Reboot your phone into recovery menu:
Turn off phone
Press Camera button, then press Power. Hold them both till you see recovery screen.
Press Volume Up and Camera button at the same time till you see the recovery menu.
Run the update.zip.
Connect via ADB and execute:
Code:
nandroid-mobile.sh --restore
Type the name of the backup you want to restore.
Telus 2.0.1 unrooted backup
Here's a clean Telus Milestone 2.0.1 Nandroid backup. I found this one on the web, and then I removed the "su" and "Superuser.apk" files so that it's no longer rooted. Sorry, the original source is uncredited as I forgot where I got it from.
As far as I know, there is no shipped SPF of the 2.0.1 Telus firmware, so this is your only option to go back to stock.
http://www.multiupload.com/TA8V2QPJEO
I used this to restore back to stock Telus Milestone ROM so that I could return the device. The only thing different from the original purchased state was the recovery SPF, but that would be really hard to tell or to find out (just a version number difference).
There's a step missing from the backup process. You need to 'flash' the update.zip from the recovery menu before you can connect over adb.
slightly said:
There's a step missing from the backup process. You need to 'flash' the update.zip from the recovery menu before you can connect over adb.
Click to expand...
Click to collapse
Oops! Fixed now. Thanks!
no need for a computer to do this anymore custome recovery does all that from the phone now .
DAGr8 said:
no need for a computer to do this anymore custome recovery does all that from the phone now .
Click to expand...
Click to collapse
Wicked, thanks for letting us know. Do you have instructions or a link to one?
EDIT: You mean this?
http://www.motorolafans.com/forums/...m-update-recovery-package-updated-v1-12d.html
I see it also does root!
dsixda said:
Here's a clean Telus Milestone 2.0.1 Nandroid backup. I found this one on the web, and then I removed the "su" and "Superuser.apk" files so that it's no longer rooted. Sorry, the original source is uncredited as I forgot where I got it from.
As far as I know, there is no shipped SPF of the 2.0.1 Telus firmware, so this is your only option to go back to stock.
http://www.multiupload.com/TA8V2QPJEO
I used this to restore back to stock Telus Milestone ROM so that I could return the device. The only thing different from the original purchased state was the recovery SPF, but that would be really hard to tell or to find out (just a version number difference).
Click to expand...
Click to collapse
You just saved my Milestone. Thank you x10!
(using xperia x10)
I've made a lot of modifications to my stock rom, and would like to share it.... so is system.img a valid way to share my *own* rom or mod ? (valid as in technically feasible? means ppl can d/l it n flash using recovery n use it?)
my main concerns are... will it boot on someone else's device? (i tried it myself... total wipe + clean stock instal, followed by flashing only my backed up system.img, *didn't flash data.img, only system* it took an eternity to boot first time but it ran)
second concern... system.img doesn't have any personal data right? logs, msgs etc are in data partition i guess??
Sent from my X10i using XDA App
Sent from my X10i using XDA App
this is how i did it anyways. i had to flash the boot.img and update via stock recovery to get the ota to flash. but then no root!
so heres how i got it back:
download the superboot/paulobrien method (http://forum.xda-developers.com/showthread.php?t=882333).
boot phone to fastboot.
Code:
fastboot boot boot.superboot.img
let phone boot, open terminal, su, just to check.
reboot phone.
rooted and ota'd now!
I've got root back, but not by that method. I think it might be a mistake to flash that boot.img, as the 2.3.1 update patched boot.img... so replacing it with one from 2.3 might not be the best idea. But I guess no one really know what the changes might be.
I guess time will tell
The method I used was:
1. Boot into fastboot.
2.
Code:
fastboot flash recovery recovery-clockwork-3.0.0.0-crespo.img
3. Reboot from fastboot directly into recovery (not doing so will cause android to replace CWR).
4. Mount USB, copy su-2.3.6.1-ef-signed.zip to the /sdcard via windows/linux
5. Mount /system
6. Install update from zip (browse to were you put su-2.3.6.1-ef-signed.zip).
7. Install it, and reboot.
8. open root explorer, and rename /etc/install-recovery.sh to install-recovery.sh.old
9. open ROM Manager, reflash CWR.
now you are all done, rooted, w/ CWR
I reflashed CWM, then from CWM, remounted /system, then used adb to chmod 6775 su. That restored root pretty easily.
What Recovery image are you using? Are you able to get into it consistently? I can't from fastboot except for if I immediately hit it up after flashing CWM with fb, or from ROM Manager (flash from RM, then select reboot to recovery).
Luxferro said:
I've got root back, but not by that method. I think it might be a mistake to flash that boot.img, as the 2.3.1 update patched boot.img... so replacing it with one from 2.3 might not be the best idea. But I guess no one really know what the changes might be.
I guess time will tell
Click to expand...
Click to collapse
its not flashing it. read the command. its only booting to that image to install su. then reboot will bring you back to stock 2.3.1 boot.img.
distortedloop said:
I reflashed CWM, then from CWM, remounted /system, then used adb to chmod 6775 su. That restored root pretty easily.
What Recovery image are you using? Are you able to get into it consistently? I can't from fastboot except for if I immediately hit it up after flashing CWM with fb, or from ROM Manager (flash from RM, then select reboot to recovery).
Click to expand...
Click to collapse
im using stock recovery.
I'm rooted on 2.3.1 but I lose clockwork recovery when I reboot an gota reflash it using rom manager. Anyone having this problem
k0mpresd said:
its not flashing it. read the command. its only booting to that image to install su. then reboot will bring you back to stock 2.3.1 boot.img.
Click to expand...
Click to collapse
Sure it is. But on Android bootup, a script is running somewhere to replace it with stock recovery. They did this on Droid_1 after the first or second update (that's my only other android phone... so my android experience is limited).
edit: I just found the script. It's /etc/install-recovery.sh .... just renamed my to install-recovery.sh.old. gonna reflash CWR and test it now.
edit2: yep, works great now. CWR, and retained my 2.3.1 boot.img
So is this something that the devs of clockworkmod need to fix in order to not lose clockwork recovery when u reboot the phone
chris6278 said:
So is this something that the devs of clockworkmod need to fix in order to not lose clockwork recovery when u reboot the phone
Click to expand...
Click to collapse
No, it's a safety mechanism so you can't lose recovery... It has nothing to do with clockworkmod. Someone can make a root script or app that disables it easily. Or people can just do it themselves manually.
edit: actually, all that needs to be done is add some code to the update script inside su-2.3.6.1-ef-signed.zip so when it installs the update, it renames install-recovery.sh
distortedloop said:
I reflashed CWM, then from CWM, remounted /system, then used adb to chmod 6775 su. That restored root pretty easily.
What Recovery image are you using? Are you able to get into it consistently? I can't from fastboot except for if I immediately hit it up after flashing CWM with fb, or from ROM Manager (flash from RM, then select reboot to recovery).
Click to expand...
Click to collapse
I want to attempt to restore my root by using your method. But I'm lost at the part when you use adb chomd 6775 su,
When I go into adb, do i just type chomd 6775 su? Do I have to download something else to use this? Please explain, thanks
If u dont mind can u please provide the instructions on how to do it manually. Id really appreciate it. Sorry im a noob lol
Where in root explorer do i need to rename
Where in root explorer do i rename it
plmiller0905 said:
I want to attempt to restore my root by using your method. But I'm lost at the part when you use adb chomd 6775 su,
When I go into adb, do i just type chomd 6775 su? Do I have to download something else to use this? Please explain, thanks
Click to expand...
Click to collapse
chmod needs to be done at a # prompt.
chris6278 said:
Where in root explorer do i rename it
Click to expand...
Click to collapse
I'm trying not to be rude... but if you can post in this thread, you can read it to. Before you asked your question a couple different step by step posts outlined all you need to know.... and this thread is only 2 pages...
Is it just me or does adb remount no longer work?
If I use the old koush rootboot.img it works, but no wifi, if I use the stock boot.img, I get no wifi but am able to remount.
I can read an ive done all the steps u posted but my ? Is where in root explorer do i find /etc/install-recovery.sh so i can rename it? Im learning this as i go so excuse me if i sound stupid sometimes
chris6278 said:
I can read an ive done all the steps u posted but my ? Is where in root explorer do i find /etc/install-recovery.sh so i can rename it? Im learning this as i go so excuse me if i sound stupid sometimes
Click to expand...
Click to collapse
do you have root explorer? if not, it's just a file explorer that has root access. by default when you open it you are at /
you need to scroll down to /etc
go in that folder and find the install-recovery.sh
look up top for the button to turn it from read-only to read-write, click it
go back to the file long press it, and then choose rename.
Luxferro said:
I'm trying not to be rude... but if you can post in this thread, you can read it to. Before you asked your question a couple different step by step posts outlined all you need to know.... and this thread is only 2 pages...
Click to expand...
Click to collapse
Thanks..I already rerooted but thanks anways
I got root explorer an followed ur directions an now everything works great. Thanx for ur help an sorry for being a pain lol
Hi All
I looked around and didnt see anyone with my problem, I installed Rom Manager on my NC and when i went into recovery my NC just started boot looping. Does anyone have any suggestions on how i can fix this?
Same Problem....
Sorry I can't help I'm having the same problem I installed ROM Manager, tapped Backup Current Rom, clicked Ok and now it just keeps booting until it displays "Touch the Future of Reading" then turns off and does it all over again, I have tried interrupting the boot 8 times unfortunately I don't really think there is anything I'm interrupting as not only did that not work if I let it just sit it does the exact same thing without reverting to its non-rooted state. Please anyone help!!!
When in the loop...wait Dorothy to turn off... then just as it starts up hold power and n button for 4-5 seconds and release...should boot you into CWM. Then either try clearing cache and dalvik cache then reboot. What where you doing when it happened? Installing kernel? Making backup? Do you have the newest version of cwm?
Sent from my LogicPD Zoom2 using XDA App
If you look in the nook color development subforum right now there is a thread called how to boot into recovery and it explains and shows exactly what I mean... check it.out.
Sent from my LogicPD Zoom2 using XDA App
I already looked at a couple including one with a video showing you exactly how to do it (power/n buttons) it just keeps restarting like I'm not doing anything. I was trying to make a backup and ya i downloaded it yesterday
help plz. samsung galaxy s - after install ROM MANAGER click backup after - you have to install clockworkmod - i clicked YES - and problem - all the time my phone is restart in clockworkmod and and cant choose any option - apply sd card e.t.c. please help me what can i do for get my phone alive. step by step please my mates. thank you in advance. [email protected]
Use CWR to install the attached zip.
Note that this zip is different than some of the other ones floating around on the forum. This only *only* replaces uRecRam, the recovery ramdisk, with the stock 1.1 uRecRam and thereby uninstalls CWR. From my understanding, the other zips completely restore everything in /boot.
After installing this zip, reboot. You will probably get an "Installation Failed" screen; just reboot after that and you'll be fine.
It appears that something in 1.1 is not clearing the trigger to boot into recovery. This happens ever time CWR is run, so if you re-install from ROM Manager to make a backup, you'll have to re-apply this zip.
edison said:
Use CWR to install the attached zip.
Note that this zip is different than some of the other ones floating around on the forum. This only *only* replaces uRecRam, the recovery ramdisk, with the stock 1.1 uRecRam and thereby uninstalls CWR. From my understanding, the other zips completely restore everything in /boot.
After installing this zip, reboot. You will probably get an "Installation Failed" screen; just reboot after that and you'll be fine.
It appears that something in 1.1 is not clearing the trigger to boot into recovery. This happens ever time CWR is run, so if you re-install from ROM Manager to make a backup, you'll have to re-apply this zip.
Click to expand...
Click to collapse
Worked PERFECTLY!!! Thank you!!! I thought i was screwed! CWR screwed this thing into a loop! YOU ARE A SAVIOR!
edison said:
Use CWR to install the attached zip.
Note that this zip is different than some of the other ones floating around on the forum. This only *only* replaces uRecRam, the recovery ramdisk, with the stock 1.1 uRecRam and thereby uninstalls CWR. From my understanding, the other zips completely restore everything in /boot.
After installing this zip, reboot. You will probably get an "Installation Failed" screen; just reboot after that and you'll be fine.
It appears that something in 1.1 is not clearing the trigger to boot into recovery. This happens ever time CWR is run, so if you re-install from ROM Manager to make a backup, you'll have to re-apply this zip.
Click to expand...
Click to collapse
STICKY PLEASE!!!!! This is amazing and it freakin buried!
I found that if you install cwr from rom manager that if you reboot before rebooting into cwr, you will avoid the cwr boot loop.
I think this is a problem with any nook waswith 1.1 and rooted with AN3.0
Sent from my LogicPD Zoom2 using XDA App
I don't see the need of removing CWR. Setting BootCnt to 0 should be enough..
Use:
echo -n -e "\x08\x00\x00\x00" > /mnt/devconf/BootCnt
And you can also make a flashable zip of it if people are adb-phobic..
Sam
edison said:
Use CWR to install the attached zip.
Note that this zip is different than some of the other ones floating around on the forum. This only *only* replaces uRecRam, the recovery ramdisk, with the stock 1.1 uRecRam and thereby uninstalls CWR. From my understanding, the other zips completely restore everything in /boot.
After installing this zip, reboot. You will probably get an "Installation Failed" screen; just reboot after that and you'll be fine.
It appears that something in 1.1 is not clearing the trigger to boot into recovery. This happens ever time CWR is run, so if you re-install from ROM Manager to make a backup, you'll have to re-apply this zip.
Click to expand...
Click to collapse
You, sir, saved me from tossing my NC in a fit of frustration. CWR had me in Nook purgatory for 6 hours... Thank you kindly!
samuelhalff said:
I don't see the need of removing CWR. Setting BootCnt to 0 should be enough..
Use:
echo -n -e "\x08\x00\x00\x00" > /mnt/devconf/BootCnt
And you can also make a flashable zip of it if people are adb-phobic..
Sam
Click to expand...
Click to collapse
Sam, what you have will actually keep it in recovery - you're setting it to a count of 8.
However, this should *really* fix it (from adb shell):
mount /dev/block/mmcblk0p2 /rom
dd if=/dev/zero of=/rom/devconf/BootCnt bs=1 count=4
dd if=/dev/zero of=/rom/bcb bs=1 count=1088
umount /rom
The above fix is apparently in an upcoming CWR release (in git now). The /rom/bcb bit is apparently what causes the "Installation Failed" message, too.
As I mentioned, the zip I posted above will uninstall CWR. The bit above will fix the boot loop, but it will most likely reappear the next time you boot into recovery.
This worked perfect. Saved my CM7 install.
You're right sorry. Read the thread a bit quickly. Thaught it was standard bootlooping..
Sent from my NookColor using Tapatalk
damned that i didnt see that thread.. i passed 3 hours before testing this solution..
I don't know if its related but from now i can't install from market, it just download app and say "download successfull" . No installation..
edison said:
Use CWR to install the attached zip.
Note that this zip is different than some of the other ones floating around on the forum. This only *only* replaces uRecRam, the recovery ramdisk, with the stock 1.1 uRecRam and thereby uninstalls CWR. From my understanding, the other zips completely restore everything in /boot.
After installing this zip, reboot. You will probably get an "Installation Failed" screen; just reboot after that and you'll be fine.
It appears that something in 1.1 is not clearing the trigger to boot into recovery. This happens ever time CWR is run, so if you re-install from ROM Manager to make a backup, you'll have to re-apply this zip.
Click to expand...
Click to collapse
I am having exactly the same problem. But this solution isn't working for me. When I install the attachemnt I get an error:
--Installing: /sdcard/uninstall-CWR.zip
Finding update package...
Opening update package...
Installing update...
E:Error in /sdcard/uninstall-CWR.zip
(Status 0)
Installation aborted.
I didn't know if that was the error referred to above, but I reboot multiple times after this and it continues to boot into recovery mode. I've downloaded and transferred the file to the g tablet twice.
Please help.
Thanks
A clear flag on CWR would sure be nice. Here I am at work and have no way of removing it.
To give some background, I was booted, and in ROM manager, I clicked reboot to recovery - didn't work, so I figure "what the hell, let's kill it and try again." Wrong... So then I manage to get it rebooted into recovery, I do a factory reset (thinking everything's hosed at this point), then try to reboot, and what do you know? Yep, recovery again.
My guess is all this started after I updated SuperUser ... things started going weird after that.
Ah yes, and after a restore, I click on reboot system now - and it turns the device off??? Wonky...
edit: OMG... now the damn thing won't turn on at all... This is beautiful crap here...
edison said:
Use CWR to install the attached zip.
Note that this zip is different than some of the other ones floating around on the forum. This only *only* replaces uRecRam, the recovery ramdisk, with the stock 1.1 uRecRam and thereby uninstalls CWR. From my understanding, the other zips completely restore everything in /boot.
After installing this zip, reboot. You will probably get an "Installation Failed" screen; just reboot after that and you'll be fine.
It appears that something in 1.1 is not clearing the trigger to boot into recovery. This happens ever time CWR is run, so if you re-install from ROM Manager to make a backup, you'll have to re-apply this zip.
Click to expand...
Click to collapse
Thanks, Edison. This solution worked perfectly.
**Disclaimer** If you don't understand what follows, don't attempt this. I'm not responsible for you softbricking your device,
This is a quick guide for how to install the new android without losing anything. You'll need fastboot for this. Also, before doing this, be sure to download the supersu cwm update zip, and have it on your sdcard. Make sure you also already have a custom recovery installed (I did twrp, but i'm sure cwm will work just as well). I would also suggest having a backup done, through titanium backup and through recovery, just incase.
First, download the factory images for the n7 from google's website. Decompress them (if you're in windows, you'll need winrar or something similar.) After you decompress the archive, there'll be another one inside (image-nakasi-jop40c.zip), decompress this one as well. Under here, you'll see the .img files for all the partitions. For now, go up one directory. You'll also see here bootloader-grouper-4.13.img. Once you have all this, reboot into the bootloader.
Once you're in the bootloader, you can update the bootloader to the new version (this step isn't needed, but I did it anyways). Plug into your pc, and type fastboot devices. Make sure it's not blank. If it is, you have to update drivers. If you can see the device, open up a command prompt, and cd to the directory that has the bootloader-grouper file. Type the following:
fastboot flash bootloader-grouper-4.13.img
then, after it's done, type:
fastboot reboot-bootloader
Now, you'll be booted back into the bootloader, it'll say 4.13. On to the rom.
cd into the folder image-nakasi-jop40c (make sure you see the files system.img and boot.img before you continue. If you don't see them, the next steps will do nothing but erase your kernel and system parition.)
now, you see the image files. Type the following (still in the bootloader)
fastboot erase system
fastboot flash system system.img
wait until it completes, then type:
fastboot erase boot
fastboot flash boot boot.img
Once this is done, hit the volume up on the device until it shows recovery mode on the top. When it does, push the power key and you'll boot into your recovery (shouldn't be touched.) Inside here, flash the supersu cwm zip file, which'll flash the superuser binary, and supersu. Once this is done, do a factory reset (removing your data and cache.) Boot into the rom.
Once it's booted, you'll notice your internal sd card appears to be empty (mine did, I was worried at first.) For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place. You now have the rom booted, rooted, with all your data. Now, you can do a titanium restore to get all your stuff back.
My first boot got stuck for some reason. if it happens to you, just hold the power button and hard reboot. (I did this on 2 devices, it only happened to one of them, so I figured I'd give you all warning.)
Links:
SuperSu binary: https://docs.google.com/open?id=0B7a8xHNJlpgTR0ZkR1pWZWR2VzA
Google Factory Images: https://developers.google.com/android/nexus/images
Thanks for this.
I flashed the 4.2 ota in the dev section and I lost root. Can I just flash the supersu binary in cwm to regain root?
Thanks for this.. Apparently you found out too a clean 4.2 isn't rootable via typical methods.
That SuperSU package did the trick. I have to remember to keep a SuperSU binary on hand for these kinds of situations that SuperUser fails..
jefferson9 said:
Thanks for this.
I flashed the 4.2 ota in the dev section and I lost root. Can I just flash the supersu binary in cwm to regain root?
Click to expand...
Click to collapse
Yes. If you do it though cwm, you're not using any exploits, you're just inserting the superuser binary and supersu.apk into the proper places on the rom. On any nexus device, any rom, this will root it.
mstrk242 said:
Once it's booted, you'll notice your internal sd card appears to be empty (mine did, I was worried at first.) For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place.
Click to expand...
Click to collapse
DANGER WILL ROBINSON!!
The "odd reason" is called "multiple users" - add a second user and they get a folder called 10.
tehSmoogs said:
DANGER WILL ROBINSON!!
The "odd reason" is called "multiple users" - add a second user and they get a folder called 10.
Click to expand...
Click to collapse
Exactly.
If everything goes right we should have an AOSP prerooted build in about *looks at watch* 20 minutes.... Unless there is a compile error or SU error. *laff*
Back to watching the scrolling terminal window
Just got this working on a mac...
did not update bootloader(couldnt get it to)
other than that, same commands except all fastboots are ./fastboot on a mac
the only other trick is i needed the fastboot and abd files in the jop40c folder...seems to have worked like a charm....im deff on 4.2 with su installed... and it looks like my data is still there...once google is done restoring i'll know just how sucessfull it is, but so far, seems to work!!!
kwhee07 said:
Just got this working on a mac...
did not update bootloader(couldnt get it to)
other than that, same commands except all fastboots are ./fastboot on a mac
the only other trick is i needed the fastboot and abd files in the jop40c folder...seems to have worked like a charm....im deff on 4.2 with su installed... and it looks like my data is still there...once google is done restoring i'll know just how sucessfull it is, but so far, seems to work!!!
Click to expand...
Click to collapse
I did this all on linux, just kind of adapted the guide for windows. I figured all the linux users would understand how to do it on their own. Glad to know it's the same for mac as well.
OK where did they put the developer options? Not in settings on my 32GB 4.2 device
Never mind. This: http://www.androidpolice.com/2012/1...hidden-in-android-4-2-heres-how-to-find-them/
rootbrain said:
OK where did they put the developer options? Not in settings on my 32GB 4.2 device
Never mind. This: http://www.androidpolice.com/2012/1...hidden-in-android-4-2-heres-how-to-find-them/
Click to expand...
Click to collapse
Settings - about tablet - build number
push it a few times and it will enable dev options
You have .bat file in the package.
Why so complicated?
I downloaded 4.2 from here:
http://android.clients.google.com/p...gned-nakasi-JOP40C-from-JZO54K.094f6629.zipia
I then just flashed it from recovery via CWM.
Done.
CWM asked me if I wanted to maintain root and of course I chose the correct answer on this, so now my N7 is running on a rooted 4.2.
Here is my method:
1. Download official 4.1.2 from http://forum.xda-developers.com/showthread.php?t=1929270 and 4.2 OTA image from http://forum.xda-developers.com/showthread.php?t=1989188
2. Boot into CWM (i have CWM touch installed)
3. Clear data and install 4.1.2, don't forget to turn on root in the installer
4. reboot check that root is fully working
5. reboot into recovery install 4.2
6. before reboot CWM will ask to disable recovery flash and protect root. Ansver yes to both questions
I'm confused, it says if you are already on a custom rom, just flash as usual.
What makes this different?
I was on stock ROM rooted with some system modifications, and this wwadd the only way I could get the update working...
Sent from my Nexus 7 using xda app-developers app
mstrk242 said:
For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place. You now have the rom booted, rooted, with all your data. Now, you can do a titanium restore to get all your stuff back.
Click to expand...
Click to collapse
So I'm at the step listed above. I have 4.2 on my device but I can't seem to find this "0" folder. I'm browsing the /sdcard folder via adb shell. Am I looking at the wrong place? Do I have have the incorrect permissions? Or might it not be there?
Thanks.
Ill have to wait until a rooted rom is created, I have no comp.
Sent from my Nexus 7 using XDA Premium HD app
can I install image-nakasi-jop40c.zip directly without upgrading bootloader?
Zuk. said:
So I'm at the step listed above. I have 4.2 on my device but I can't seem to find this "0" folder. I'm browsing the /sdcard folder via adb shell. Am I looking at the wrong place? Do I have have the incorrect permissions? Or might it not be there?
Thanks.
Click to expand...
Click to collapse
Not advisable to move this folder - if it got moved to a new location by the o/s then there's probably a good reason why - maybe like 4.2 introducing multiple users
Each user appears to get their own "home" directory created in /mnt/shell/emulated/
Default user dir is "0"
Second user dir is "10"
Each contain the standard dir's from 4.1 and earlier.
Travelawyer said:
Why so complicated?
I downloaded 4.2 from here:
http://android.clients.google.com/p...signed-nakasi-JOP40C-from-JZO54K.094f6629.zip
I then just flashed it from recovery via CWM.
Done.
CWM asked me if I wanted to maintain root and of course I chose the correct answer on this, so now my N7 is running on a rooted 4.2.
Click to expand...
Click to collapse
You had two extra characters at the end of your link, but I fixed it above and it's good to go for others in the future. Just flashed it in TWRP, it didn't ask if I wanted to maintain root, hit reboot when it was complete and lost root, so it doesn't work for everyone - good news is that all my data remained intact without having to resort to advanced restoring my data from a backup....
When I tried the SuperSU binary root flash trick, I finally got root back. But don't think it's as easy to get to recovery! I had to obtain the TWRP Recovery one more time since it wiped it and put in place a recovery that did absolutely nothing but reboot the device after a few minutes, so you'll have to
Code:
fastboot flash recovery openrecovery-twrp-2.3.1.1-grouper.img
to get TWRP back.... Hope that helped everyone!
I have my wife's LG Revolution running Broken Out rom. I am getting to read to send int to big read for a replacement. They made me state that I had made not hardware or software modifications. So I need to return this to stock. I have successively used LGNPST in the past. But now the USB port does not work in data mode. A computer will charge the phone, but the phone does not prompt for USB Mode when plugin to a computer. I have tried 2 computers and 2 different cables. All of which work for my LG revolution with out a problem.
Is there any way to remove Clock Work mode and switch it to the factory recovery, and return the rom to Stock without a working USB port?
I have a way of copying files to the SD card if needed.
Thanks.
I like this this guys thoroughness, though, not totally relevant for you. The following steps would pertain best in your situation.
1) wipe data, cache, davlik cache from CWM
2) When the phone initial setup begins, bypass it with this method. Touch top left, top right, bottom right, then lastly bottom left.
3) OPTIONAL - Erase external SD card from settings menu (if you thnk it's necessary... you may not be sending that back in)
4) format internal memory from settings menu
5) LGNPST flash stock V9. Get the V9 TOT here and unzip it first.
Flashing the TOT just took me 20 minutes.
Really, though, just flashing the TOT will suffice.
That's very neet, thank you. But can I use LGNPST without a usb cable? My usb port will only charge, no data.
Sent using Tapatalk 2
Whoops. Missed that part. I was on a roll doing a TOT via USB myself. Maybe, if someone could wrangle you up a stock boot.img to flash in CWM after you unroot?
Sent from my VS910 4G using Tapatalk 2
If someone who is running a stock rooted rom, v9 or later, wants to put up a backup I can rip the rom out of it and make a flashable zip. Just when making the backup, go into the backup settings of cwm and change it to tar.gz. Not the blob crap.
Mine phone is now rooted, stock and running ZVb. This one could be backed up and installed on my. Wife's phone with the bad usb port?
I should install cwm on mine to take a backup?
Sent from my VS910 4G using Tapatalk 2
thesavo said:
Mine phone is now rooted, stock and running ZVb. This one could be backed up and installed on my. Wife's phone with the bad usb port?
I should install cwm on mine to take a backup?
Sent from my VS910 4G using Tapatalk 2
Click to expand...
Click to collapse
That would be awesome! To have at least the android part of the new update is better than nothing.
He still needs to find a way to remove cwm with out a pc?
I don't have clockwork on my stock + rooted Revolution. Can I use any rooted backup tool from the market/play store?
IF i have to use Clockwork mod recovery, can I just do a nandroid backup from the good phone the other phone? I have to take in to big red tomorrow.
Does anything need to be stripped out of the nandroid back?
I was just trying to think of another way to get you going. ADB Wireless sounded good up until the point that the SU part has to be removed. Then ADB Wireless would fail I'm sure.
My best guess for you is to use the Easy V8 - V9 All in One by Mark Once Again as a basis for commands to execute from terminal. I'm not sure if losing root during terminal will affect the operation however. Looking at the batch file adb shell commands, it looks fairly straightforward to manually do. I am just not 100% sure it will work. Someone else with more experience could chime in about that.
Below is what I copied out of the batch file, the UNROOTSTOCK portion.
The ALL CAPS portions are comments I have added in. The usual warnings apply. Use at your own risk.
Code:
rm /data/bootlogo/bootlogopid
ln -s /data /data/bootlogo/bootlogopid
REBOOT
echo 'ro.kernel.qemu=1' > /data/local.prop
REBOOT
UNROOTING TIME
rm /system/bin/su
rm /system/xbin/su
rm /system/app/Superuser.apk
rm /system/xbin/busybox
rm /system/bin/busybox
rm /data/local/tmp/* 2>/dev/null
USE A ROOT FILE EXPLORER APP TO COPY THIS Files\stockrecovery.img FROM THE EASY V8 - V9 ZIP. . .
TO HERE ON YOUR PHONE /data/local/tmp/stockrecovery.img
TIME TO PUSH THE STOCK RECOVERY
dd if=/data/local/tmp/stockrecovery.img of=/dev/block/mmcblk0p14 bs=4096
rm /data/local/tmp/* 2>/dev/null
CLEAN-UP TIME
rm /data/bootlogo/bootlogopid
rm /data/local.prop
REBOOT AND YOU'RE DONE!
Hope that helps, or that it spurs the help you need.
EDIT: To make it stock, all the superuser and busybox files need to be removed, and the stock boot image needs to replace the one that has CWM. Otherwise, CWM is still there. So, no. A nandroid from the other phone wouldn't help you.
But would a restored nandroird backup (from my phone) work enough to get me 1/2 way there? Would the nandroid restore leave me with
Rooted Verizon rom
Clockwork mod recovery.
If so. I could DD the stock recovery over clockwork mod recovery.
Then unroot it with a terminal app.
By the looks of your pseudo-code script, It does do all of that, in a different order.
It's possible to capture a stock, unmolested nandroid, but that would be from a bone stock phone with CWM I think. A dev did that for us on the Nabi 2, making a stock image before the rooting business. Then it's just getting the stock boot image back, if you catch my drift.
I could have done it a couple days ago having just reTOT'ed...
Edit: The Nabi is a tablet and I think some have shared their images, but I don't know if there are any implications sharing a phone nandroid.
Sent from my VS910 4G using Tapatalk 2
I have two of these VS910s. I just cleared out my internal SDCard on my VS910. It's rooted running the newest verizon rom. It doesn't have CWM right now, but is that required for nandroid backup? To restore to my wife's with the busted USB port? I'll run the backup to my sdcard then place it in her phone to run the restore.
Needing CWM. . . no. I was going to say yes, but there is a way to make a nandroid with your phone on. Using Online Nandroid, or an app developed based on it, Orange Backup, you can make an image with your phone on, no need for CWM. It will need a patch file installed, but I already got that going with the dev. It looks like it will work for the Revolution. One caveat. While I tested that it successfully backed up my phone, I didn't actually restore the nandroid created.
Looking into the Nabi's stock backup during rooting and recovery, the dev used TWRP instead of CWM. TWRP supports Open Recovery Scripts which he used to do a stock backup. No go for us with CWM, at least not how he did it. No matter because your phone is rooted.
OK, so I installed CWM recovery on my working phone. No big deal. I took two backups for good measure on the bad phone. I also restored one of the backups, it seamed to work.
I am taking a backup of my rooted stock phone. I will then attempt to restore it to the bad phone. Any thoughts to using DD in a terminal app on the phone? I should then dd the recovery.img file over CWM,
To unroot, i think i shuld be able to do as you suggested to delete SU.apk and busybox.
Good luck. Dinner is served now so I'll be missing for a while.
Bait-Fish said:
Good luck. Dinner is served now so I'll be missing for a while.
Click to expand...
Click to collapse
We have stupid verizon 4G LTE boot video on the bad phone. That's a good sign.
Edit: Its running a VZW rom now!
home stretch
Ok, so after restoring a Nandroid backup of verizon's VZB to the bad phone. Now I need to un-root it. and I should be good. Also, Settings -> about says its version VZ9 not VZB. Odd.
Plan.
Add my google account to get to play store.
Add a terminal app.
Use terminal to delete any nandroid backups.
Run DD from terminal to overwrite CWM with recovery,img
delete rooted files.
Run factory wipe. from settings menu or PWR + Vol Down.
Then I should be done
Any thoughts.?
Seems about right. The version won't tick up from VZ9 unless you do the actual OTA I understand. Something about the baseband.
Sent from my VS910 4G using Tapatalk 2