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
**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!
Update 11-26-2012
The issue that this procedure was designed to overcome has been resolved in the latest version of CWM (6.0.1.9 or newer). Please view http://forum.xda-developers.com/showthread.php?t=1781899 for details and download links. If you do not want to upgrade to the latest CWM the directions below will still work but you should really just update.
Background
Due to the multi-user support capabilities of Android 4.2(+) the clockworkmod directory created by ClockworkMod and used to store downloads and backups is being created in /data/media. Unfortunately this directory is not accessible to individual users and therefore backups created in recovery can not be viewed or modified by ROM Manager and vice versa. ROM Manager will look for the directory /data/media/<user number> (e.g. /data/media/0) to which /sdcard is mounted when you are logged in as the user whose number is <user number> (e.g. 0).
Requirements
ClockworkMod Recovery installed and functioning
ROM Manager
ADB installed on your computer and functioning
Willingness to accept that you are on your own and I am not responsible if you mess something up!
Solution
1. Boot into CWM recovery
2. Attach your Nexus 7 to your computers USB port
3. Open an ADB shell using a console from your computer
Code:
adb shell
4. Confirm that you have a clockworkmod directory at /sdcard/clockworkmod (I am using user number 0 for the rest of this procedure, if you wish to use a different user substitute 0 with your user number)
Code:
cd /data/media/0
ls
4a. If you do not see a clockworkmod directory create one with the command below, otherwise proceed to step 5
Code:
mkdir /data/media/0/clockworkmod
5. See if you have a clockworkmod directory at /data/media
Code:
cd /data/media
ls
5a. If you see a clockworkmod directory type the command below, otherwise proceed to step 6
Code:
mv clockworkmod clockworkmod_bak
6. Create the symbolic link
Code:
ln -s /data/media/0/clockworkmod/ clockworkmod
7. If you already had backups in clockworkmod (now clockworkmod_bak) you can move them to the new folder by executing the following command
Code:
mv clockworkmod_bak/backup/ clockworkmod/
mv clockworkmod_bak/blobs/ clockworkmod/
mv clockworkmod_bak/download/ clockworkmod/
WARNING: I tested a backup from recovery and verified the backup was in ROM Manager, renamed the backup in ROM Manager, and confirmed the backup was renamed in recovery. Due to time constraints I did not restore the backup though I can't imagine why it would fail. As mentioned above do this at your own risk. If you do not have a unix/linux experience I would suggest that you wait for someone with experience to follow these steps (I wrote them after I did the procedure so they haven't been vetted) before you attempt it yourself.
Very helpful, i was wondering what they did to mess up clockwork mod
been trying to undo 4.2 for hours as i dont quite like it
truehybridx said:
Very helpful, i was wondering what they did to mess up clockwork mod
been trying to undo 4.2 for hours as i dont quite like it
Click to expand...
Click to collapse
I am on the fence about 4.2 myself and when I couldn't see my 4.1.2 backup I had a panic moment. I have to admit that either 4.2 is growing on me or I am already forgetting how good 4.1.2 was .
sandnap said:
I am on the fence about 4.2 myself and when I couldn't see my 4.1.2 backup I had a panic moment..
Click to expand...
Click to collapse
+1! Panic indeed! LOL
Great tutorial. Thanks and have a happy thanksgiving
Is there a way to do this without using adb? I don't know how to get it working.
It looks like you are just moving all the files from one location to another, right? If thats the case can I just move them with a file explorer? Also where are the back-ups from pre 4.2 stored, I thought it was sdcard/clockworkmod/ Can I move the back-ups from there to a data/media/clockworkmod folder?
StarOrc said:
Is there a way to do this without using adb? I don't know how to get it working.
It looks like you are just moving all the files from one location to another, right? If thats the case can I just move them with a file explorer? Also where are the back-ups from pre 4.2 stored, I thought it was sdcard/clockworkmod/ Can I move the back-ups from there to a data/media/clockworkmod folder?
Click to expand...
Click to collapse
Please see my update to the original post. Once you update to the latest CWM you can copy any existing backups to the new backup and blobs folders under /data/media/clocworkmod. This is discussed in more detail in the thread I linked to.
Code:
mv clockworkmod_bak/backup/ clockworkmod/
mv clockworkmod_bak/blobs/ clockworkmod/
mv clockworkmod_bak/download/ clockworkmod/
This is me just being nit picky, but this looks better:
Code:
mv clockworkmod_bak/* clockworkmod/
I guess for people not confident in their linux abilities that '*' misplaced could be deadly though...anyway thanks for the simple and great workaround/explanation.
Wiping/ Factory resets (in CWM or TWRP) don't erase this data folder? Are we confident in this?
255|[email protected]:/data/media/clockworkmod # mv backup/ /sdcard/clockworkmod/
failed on 'backup/' - Cross-device link
How are you able to move the directories?
This seriously annoys me. Despite the recent surge of newer android devices not containing any sd card slots for secure file storage away from ROM flashing, everything is now embedded. I have had several accidental internal storage deletions containing backups and roms and no the clockworkmod is even harder to locate and backup conveniently through usb/ftp. Thanks for the tut.
TheAtheistReverend said:
Wiping/ Factory resets (in CWM or TWRP) don't erase this data folder? Are we confident in this?
Click to expand...
Click to collapse
Yeah i am wondering that too.it doesnt feel safe for me that the backups are in the system but not in sdcard.
nexus file locations
On the nexus devices (certainly the 7, which has no external sdcard), the only real mounted portions are cache, system and data. Locations like /sdcard/ /storage/emulated/0 etc. are all fuse mounted from /data/media
Supposedly most of the data portion will survive flashing new ROMs and recoveries, everything except unlocking the boot loader, which wipes data f to meet the android security model.
Doesn't feel very safe, though.
amp said:
This seriously annoys me. Despite the recent surge of newer android devices not containing any sd card slots for secure file storage away from ROM flashing, everything is now embedded. I have had several accidental internal storage deletions containing backups and roms and no the clockworkmod is even harder to locate and backup conveniently through usb/ftp. Thanks for the tut.
Click to expand...
Click to collapse
I would use TWRP. I have switched and never looked back. It has quite a few more advanced options that I didn't see with clockworkmod, and overall has be MUCH more reliable.
The clockworkmod recovery issue stated in this thread does not affect TWRP at all.
Thanx for this, it seems to work even for the latest CWM.
Sent with desire from My One
angusc said:
Thanx for this, it seems to work even for the latest CWM.
Sent with desire from My One
Click to expand...
Click to collapse
Iget an error: Read-only File system :crying:
fokus said:
Iget an error: Read-only File system :crying:
Click to expand...
Click to collapse
If doing commands with adb did you remember to use
adb shell
And check that your command line starts with #......
Sent with desire from My One
angusc said:
If doing commands with adb did you remember to use
adb shell
And check that your command line starts with #......
Sent with desire from My One
Click to expand...
Click to collapse
Yes, that is exactly what i did.
I am on ARHD 11.0
S-off
ElementalX 2.2
I'm on ARHD 11.0 as well.
Strange, I followed the OP from step 1 to 6. I couldn't get step 7 to work so I just used my root explorer to copy the directory contents across in to the newly created clockworkmod folder, then deleted the clockworkmod.bak directory and all was good.
Tip: copy and paste each cmd from the OP in to your adb commands window......
Sent with desire from My One
angusc said:
I'm on ARHD 11.0 as well.
Strange, I followed the OP from step 1 to 6. I couldn't get step 7 to work so I just used my root explorer to copy the directory contents across in to the newly created clockworkmod folder, then deleted the clockworkmod.bak directory and all was good.
Tip: copy and paste each cmd from the OP in to your adb commands window......
Sent with desire from My One
Click to expand...
Click to collapse
THX. That is what i did. I also tried it via Terminal on the device - same error: System read only... hmmm
EDIT: Works fine now after e vew reboots. THX
When trying to use RUU's i get a error that it cant update my htc one.
i tried both europian RUU's and its a europian phone(dutch no simlock)
i also have a nandroid but i cant restore it....it says no files found.
Where do i place the nandroid backup(made by clockworkmod) and how do i restore it?
thanks.
borgqueenx said:
When trying to use RUU's i get a error that it cant update my htc one.
i tried both europian RUU's and its a europian phone(dutch no simlock)
i also have a nandroid but i cant restore it....it says no files found.
Where do i place the nandroid backup(made by clockworkmod) and how do i restore it?
thanks.
Click to expand...
Click to collapse
I read your post in my guide thread. What recovery do you have CWM or TWRP?
borgqueenx said:
When trying to use RUU's i get a error that it cant update my htc one.
i tried both europian RUU's and its a europian phone(dutch no simlock)
i also have a nandroid but i cant restore it....it says no files found.
Where do i place the nandroid backup(made by clockworkmod) and how do i restore it?
thanks.
Click to expand...
Click to collapse
I know my device(From the Netherlands Sim Unlock) is on WWE firmware. Is yours carrier branded?
My advice would be to try Reinstalling CWM through HTC One AIO toolkit and then place the backup back in the CWM folder.
Maybe that will work.
clockworkmod is the installed recovery.
it just doesnt want to start the restore function. i can however select install from sd card fine, proofing that it has no problems seeing the data....
mine is not carrier branded.
So when you attempt to do the restore from CWM it lists the date/name of your backup but fails? Or can you not even get CWM to start the restore because it doesn't see the backups?
crushalot said:
So when you attempt to do the restore from CWM it lists the date/name of your backup but fails? Or can you not even get CWM to start the restore because it doesn't see the backups?
Click to expand...
Click to collapse
no it does not list anything.
tried moving the backup folder but i have no idea where to place it. already tried putting it in root, triying to put it in /backup and in /clockwordmod or something.
the error i get is: couldnt open directory, no files found.
borgqueenx said:
no it does not list anything.
tried moving the backup folder but i have no idea where to place it. already tried putting it in root, triying to put it in /backup and in /clockwordmod or something.
the error i get is: couldnt open directory, no files found.
Click to expand...
Click to collapse
Sorry this part can be tricky because folder path is slightly different on 4.1.2 than 4.2.2. Also I haven't used CWM in a long time since I switched to TWRP.
Did you try putting the entire clockwordmod folder in:
/data/media
Then try the restore.
crushalot said:
Sorry this part can be tricky because folder path is slightly different on 4.1.2 than 4.2.2. Also I haven't used CWM in a long time since I switched to TWRP.
Did you try putting the entire clockwordmod folder in:
/data/media
Then try the restore.
Click to expand...
Click to collapse
had to make both folders, they didnt exist. there is a .data folder though.
edit: didnt work putting the backup folder in there.
borgqueenx said:
had to make both folders, they didnt exist. there is a .data folder though.
edit: didnt work putting the backup folder in there.
Click to expand...
Click to collapse
You didn't use the correct folders. I am not talking about folders on the root of your sdcard, I am talking about root of file system.
You should have a file explorer tool that will allow you to navigate to root and have R/W permissions so we can move files if needed. If not go to the play store and install https://play.google.com/store/apps/...wxLDEwOSwiY29tLmVzdHJvbmdzLmFuZHJvaWQucG9wIl0
Open the application and on the top left there is a small icon, click it and should open the fast access menu. Choose Root Explorer and then Mount R/W when prompted, click ok (keep defaults).
Now you should be at the device root and it will say Device in the top middle of ES.
Now browse to /data/ then /media
If you do not see a clockwork mod folder in media that is where we need to move the CMW backups in order to be able to restore them from recovery.
So move the clockwordmod folder from media/0/clockworkmod to the root of /media folder so it looks like
/data/media/clockworkmod(folders within here have your backups)
Then boot into recovery and try the restore.
crushalot said:
You didn't use the correct folders. I am not talking about folders on the root of your sdcard, I am talking about root of file system.
You should have a file explorer tool that will allow you to navigate to root and have R/W permissions so we can move files if needed. If not go to the play store and install https://play.google.com/store/apps/...wxLDEwOSwiY29tLmVzdHJvbmdzLmFuZHJvaWQucG9wIl0
Open the application and on the top left there is a small icon, click it and should open the fast access menu. Choose Root Explorer and then Mount R/W when prompted, click ok (keep defaults).
Now you should be at the device root and it will say Device in the top middle of ES.
Now browse to /data/ then /media
If you do not see a clockwork mod folder in media that is where we need to move the CMW backups in order to be able to restore them from recovery.
So move the clockwordmod folder from media/0/clockworkmod to the root of /media folder so it looks like
/data/media/clockworkmod(folders within here have your backups)
Then boot into recovery and try the restore.
Click to expand...
Click to collapse
tried to do exactly what you told me.
there is a data folder in root, but there is no media folder inside of that.
and if i try to create it it fails and says i should try giving the folder another name.
edit: never mind a restart of the app fixed it.
EDIT: didnt work.
my backup folder is inside /data/media/clockworkmod/
and clockwork recovery still gives desame error.
First confirm where CWM is actually putting your backups. Do this by booting into recovery and choose to do a backup. Then uncheck all partitions but the smallest and allow it to backup.
When you reboot navigate through the folders we have been talking about and see the exact path of where it put it. Then compare the contents of the backup folders to make sure it is not your original backup that is messed up.
As long as you place your backup(inside its folder) in the folder where CWM put the test backup, then you should be able to see it from recovery and restore it. If not your original backup may not be any good.
Going offline for about hour for lunch. Be back around 1:30pm EST.
grrrrrr...
made a backup for testing where clockword puts them.
they are in /data/media/clockwordmod/backup
my backup is placed in /data/media/clockwordmod.
when i try to move my backup folder to /data/media/clockwordmod/backup it says successfull, but nothing happens. i cant seem to move the folder.
EDIT: ok copying pasting worked instead of cutting pasting.
i now restored...but for some reason recovery is still clockwordmod, and it still shows tampered and unlocked on first screen before recovery.
Well you probably backed up with the custom recovery installed, right? You'll have to flash the stock recovery manually.
If you want it to be locked, you'll have to lock it. revone will do that for you, after you've flashed stock recovery.
BenPope said:
Well you probably backed up with the custom recovery installed, right? You'll have to flash the stock recovery manually.
If you want it to be locked, you'll have to lock it. revone will do that for you, after you've flashed stock recovery.
Click to expand...
Click to collapse
i made the backup using a started version of clockwordmod, not a flashed version of clockwordmod.
....but ok. where can i find the normalrecovery and how to flash it?
borgqueenx said:
i made the backup using a started version of clockwordmod, not a flashed version of clockwordmod.
....but ok. where can i find the normalrecovery and how to flash it?
Click to expand...
Click to collapse
Odd.
Have you tried looking for the stock recovery? A high proportion of the posts here are about returning to stock.
borgqueenx said:
grrrrrr...
EDIT: ok copying pasting worked instead of cutting pasting.
i now restored...but for some reason recovery is still clockwordmod, and it still shows tampered and unlocked on first screen before recovery.
Click to expand...
Click to collapse
That is all normal. All you have done is reset the ROM back to default. You will still need to restore the stock recovery and then relock the bootloader to get to 100% stock.
I am trying to find all the info needed for you to finish up and I will post it.
---------- Post added at 02:02 PM ---------- Previous post was at 01:44 PM ----------
borgqueenx said:
i made the backup using a started version of clockwordmod, not a flashed version of clockwordmod.
....but ok. where can i find the normalrecovery and how to flash it?
Click to expand...
Click to collapse
Back in post number 4 you state that CWM is your installed recovery.
So it seems correct that you have a custom recovery installed. However since you are S-Off, before I put together something for you to go back I need to know:
Did you upgrade your firmware?
Did you flash a new hboot (to get rid of the red warning lettering)?
Did you flash a new splash screen?
If you answered no to all three of those questions, you should be able to get back to stock by performing the following:
Download the ResetRecovery zip I made for you here:
https://dl.dropboxusercontent.com/u/36946918/ResetRecovery.zip
Unzip all the files into a folder. (examples will use C:\temp)
Install the HTCDriver.exe to make sure the device drivers are installed on your PC.
Make sure that USB device debugging is enabled on your device.
Open a command prompt and navigate to that folder - Start>Run>cmd Enter
Code:
cd c:\temp
Connect USB cable to phone and PC.
With the PC booted type:
Code:
adb reboot bootloader
When the bootloader screen appears:
Code:
fastboot erase cache
Then:
Code:
fastboot flash recovery recovery.img
Reboot phone and go into recovery to make sure that CWM has been replaced by HTC stock recovery. If HTC recovery appears then reboot phone.
Now relock the bootloader:
Use the revone file that you probably used to get S-Off. (If needed it can be downloaded here: http://forum.xda-developers.com/showthread.php?t=2314582)
Push revone to your device:
Put the downloaded revone (rename file to just revone) file in your adb/fastboot folder (c:\temp) and push it using this command:
Code:
adb push revone /data/local/tmp/
open a adb shell by typing:
Code:
adb shell
Now change to that directory:
Code:
cd /data/local/tmp
Now set permissions
Code:
chmod 755 revone
Since you have the tampered flag run this to remove it:
Code:
revone -t
Now do this so it will show locked:
Code:
revone -l
The newer revisions of revone don't do the actual locking any longer but it may output the command you need to run to fully re-lock:
Type exit to exit the adb shell session and issue the command to re-lock the device:
Code:
fastboot oem writesecureflag 3
Now verify that it worked by booting into the bootloader:
Code:
adb reboot bootloader
You should see it say Locked at the top and S-On, just like it was out of the box!
i have no idea if i upgraded firmware. i was from stock to android revolution wich is the newest android version.
but now i am back on stock.
software number 1.29.401.16
i didnt try to get rid of warning texr and i didnt flash a custom splash screen.
can i proceed with those instructions?
borgqueenx said:
i have no idea if i upgraded firmware. i was from stock to android revolution wich is the newest android version.
but now i am back on stock.
software number 1.29.401.16
i didnt try to get rid of warning texr and i didnt flash a custom splash screen.
can i proceed with those instructions?
Click to expand...
Click to collapse
Yes, you would know if you flashed firmware because it has many warnings and a few steps. Your version number is stock, the thing that worries me is that you are S-off and originally you thought you only unlocked bootloader.
Did you use revone or moonshine to achieve S-off?
Do you see the red warning lettering on the splash screen when booting?
AS long as the custom recovery is back to stock and you see the red warning letter on splash then you should be ok to proceed with locking now.
crushalot said:
Yes, you would know if you flashed firmware because it has many warnings and a few steps. Your version number is stock, the thing that worries me is that you are S-off and originally you thought you only unlocked bootloader.
Did you use revone or moonshine to achieve S-off?
Do you see the red warning lettering on the splash screen when booting?
AS long as the custom recovery is back to stock and you see the red warning letter on splash then you should be ok to proceed with locking now.
Click to expand...
Click to collapse
is s-off desame as unlocking bootloader?
i unlocked bootloader yes. no idea about s-off. never did anything where i saw s-on or s-off.
yes i see those red warning letters.
i have never used or heard of revone or moonshine before you mentioned it here.
need to know how to get stock recovery back then^^
Is there a way to just make a TWRP backup on my old phone with a broken screen, load it onto the new phone and do a restore?
New phone is unlocked with latest twrp flashed.
This would save me a lot of headache!
Yes. If EVERYTHING is EXACTLY the SAME
sent from my mobile device
Explain further? I have no OS currently, will the TWRP include the Rom, or do i need to install the current rom on my old phone first?
Drakeskakes said:
Explain further? I have no OS currently, will the TWRP include the Rom, or do i need to install the current rom on my old phone first?
Click to expand...
Click to collapse
What he is saying, is that if the versions of OS and firmware is exactly the same on both phones, compare fastboot getvar all, then a TWRP nandroid backup from the working phone could be copied (adb sideload) to the other phone and restored from TWRP .
sideload
Hi,
I realize this is an old thread, but doesn't adb sideload expect a zip file? All of my TWRP backups are folders containing 11 files of various sizes, I don't see a way to specify a zip backup, so what am I missing here?
Thanks -
dmm108 said:
Hi,
I realize this is an old thread, but doesn't adb sideload expect a zip file? All of my TWRP backups are folders containing 11 files of various sizes, I don't see a way to specify a zip backup, so what am I missing here?
Thanks -
Click to expand...
Click to collapse
In this case you would use adb push.
Code:
adb push "nameofbackupfolder" /sadcard/TWRP/BACKUPS/YOURSERIALNO"/"nameofbackupfolder
This will create the necessary folder in your twrp backups and copy each of the files into the folder :good:
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Danny201281 said:
In this case you would use adb push.
Code:
adb push "nameofbackupfolder" /sadcard/TWRP/BACKUPS/YOURSERIALNO"/"nameofbackupfolder
This will create the necessary folder in your twrp backups and copy each of the files into the folder :good:
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
thanks very much! (clicked as well)