Related
Changelog:
1.1 - Allow delete/restore without a name. Choose from the list.
1.0 - Use nandroid to make it one step process.
Currently, nandroid backups do not contain the a2sd app folders. It has been painful to say the least to jump between ROMs.
This script does two things:
1. Store and tag a ROM's nandroid backup and its apps data. You can provide any name for tagging while storing.
2. Restore a tagged ROM's app data and its latest nandroid backup.
The nice side effect of this is that you have complete environments you have created nicely bookmarked with easy to understand names and version numbers, ready to be restored easily.
Requirements:
1. Two partitions in order: fat32, ext2/3
2. cyanogen's recovery image 1.4. 1.3.1 will not work with V1.0.
3. Attached script called switchrom.txt downloaded and stored in folder /system/sd/ and renamed as switchrom.sh
Usage:
1. Boot into recovery using Home + End buttons together.
2. To bookmark and tag current ROM,
Go into console with Alt+X (or do adb shell from PC)
mount /system/sd
sh /system/sd/switchrom.sh -s <name>
e.g.
I am backing up soulife-1.2.3 with
sh /system/sd/switchrom.sh -s soulife-1.2.3
3. To restore a ROM,
Go into console with Alt+X (or do 'adb shell' from PC)
mount /system/sd
sh /system/sd/switchrom.sh -r
It will give you a list of available ROMs to restore and you can choose the one you want to restore using the corresponding number.
e.g.
I am restoring soulife-roger-new-3.9.1-latest with
Code:
sh /system/sd/switchrom.sh -r
1. JACMyTouchSkiV2-mod
2. JACxROM-1.3r3
3. cm-3.9.7-best-setup
4. drizzy-hero-2.8-best
5. soulife-ion-1.2.3-mod
6. soulife-roger-new-3.9.1-latest
Choose a ROM (type in the number and press enter)...6
Restoring ROM soulife-roger-new-3.9.1-latest, proceed? (y/n) y
Cleaning up /system/sd ...
Restoring soulife-roger-new-3.9.1-latest app data in /system/sd ...
Restoring nandroid backup...
Done restoring the ROM soulife-roger-new-3.9.1-latest.
Note that no extra steps are necessary. No wipe! No nandroid restore!
Note that options have changed since last version. Make sure to read the help with '-h' or '--help' option. Compression (-c option) is supported for both the apps partition and the nandroid but the way it is done in nandroid is dumb and takes like 17 minutes, so I would not recommend it at this time but you can definitely try it. I will post patches for nandroid script to fix that.
Code:
# sh /system/sd/switchrom.sh -h
Usage: /system/sd/switchrom.sh OPTIONS <rom_name>
Options are:
-h --help
-c --compress, only used with -s
-d --delete
-l --list
-r --restore
-s --store
-v --version
Always specify options as separate words
e.g. -c -r instead of -cr. Its required!
Don't use blanks or special characetrs in rom_name.
Compress will take longer but image will be smaller.
<rom_name> is optional with -r and -d. Choose from a list.
NOTES:
Note that this is not storing the whole backup of your EXT2/3 partition. This is just storing app* and dalv* folders needed to restore the ROM behavior, apps and settings only. If you wipe your EXT2/3 partition with a formatter or manually with 'rm -rf /system/sd/*', you will loose everything on that partition and won't get it back from this backup. This backup will only restore app* and dalv* folder.
It was reported that certain versions of 'adb' hangs in the sub-shell created and it doesn't pass through the commands that are typed. Make sure to upgrade the SDK to 1.5r3.
Awesome work, I'll try this out on my next rom switch. Can't ever have too many scripts I say.
added to my collection of scripts
This may sound like a silly question but please forgive me as I have not yet flashed the haykuro spl.
Once you've flashed the new spl, instead of flashing the update.zip of the cyanogen rom, can't you use nandroid restore? Or will that restore the previous spl as well (in my case HARD SPL)?
I ask because I would like to try the spl, but I'm so comfortable with my rom and settings that I would hate to wipe just to try Hero which is still in development. Call me crazy, but I like stable and finished builds. But I am curious and with a lot of time on my hands but not so much that I'm willing to lose everything just to try something that I'm not going to keep.
With this script, it would make it so much easier and would allow us to switch roms on the fly... but would it work from Hero builds and non-Hero builds?
I don't think I know enough about the SPL image contents to comment on this. But as far as I know SPL is not touched by nandroid restore. I upgraded the radio and SPL (haykuro) first, and then went with updating my ROM. I will never flash radio and SPL unless and until I really need to.
This script is just taking the pain out of switching between ROMs (whether Hero or Cyano or official) and nicely organizes your ROM backups. So, to answer your question:
would it work from Hero builds and non-Hero builds?
Click to expand...
Click to collapse
Yes. It would! I have switched between drizzy's Hero ROM and JACMyTouchSki (my favorite) many times using this. The restore is perfect!
Binary100100 said:
Once you've flashed the new spl, instead of flashing the update.zip of the cyanogen rom, can't you use nandroid restore? Or will that restore the previous spl as well (in my case HARD SPL)?
Click to expand...
Click to collapse
Considering the most amount of bricks come from radio/spl updates, I dont think this script would integrate backing up and restoring them. Same reason why rom's themselves dont include the latest radio/spl in the update.zip when it is required by the rom.
rondey- said:
Considering the most amount of bricks come from radio/spl updates, I dont think this script would integrate backing up and restoring them. Same reason why rom's themselves dont include the latest radio/spl in the update.zip when it is required by the rom.
Click to expand...
Click to collapse
Okay... so I'm running cyanogen's rom now with hardspl.
I back it up and lable it "Cyan 3.9"
I install the Haykuro spl (I already have the radio)
I install a Hero rom.
I try the Hero rom.
I backup the Hero rom and lable it "Hero"
I can then restore "Cyan 3.9" and still have the Haykuro spl.
Correct?
Binary100100 said:
Okay... so I'm running cyanogen's rom now with hardspl.
I back it up and lable it "Cyan 3.9"
I install the Haykuro spl (I already have the radio)
I install a Hero rom.
I try the Hero rom.
I backup the Hero rom and lable it "Hero"
I can then restore "Cyan 3.9" and still have the Haykuro spl.
Correct?
Click to expand...
Click to collapse
Make sure you use labels which don't have whitespace or other special characters in the name like use Cyan-3.9 instead of "Cyan 3.9". I don't think script likes it much at this time. I need to fix that.
Binary100100 said:
Okay... so I'm running cyanogen's rom now with hardspl.
I back it up and lable it "Cyan 3.9"
I install the Haykuro spl (I already have the radio)
I install a Hero rom.
I try the Hero rom.
I backup the Hero rom and lable it "Hero"
I can then restore "Cyan 3.9" and still have the Haykuro spl.
Correct?
Click to expand...
Click to collapse
The only difference between this and a "typical" nandroid restore should just be that it copies your ext2/3/4 partition for the app data. It wasnt listed anywhere that it would backup/restore your spl/radio.
Prior to flashing the haykuro spl I made a nandroid backup of the cyanogen rom I was using. I tested a hero rom and restored a nandroid backup of the cyanogen rom I was running and the new radio/spl were in place.
I think you need to dump all of mtd6ro and extract radio/spl by hand if you need to. Nandroid doesn't touch either of them.
rondey- said:
Prior to flashing the haykuro spl I made a nandroid backup of the cyanogen rom I was using. I tested a hero rom and restored a nandroid backup of the cyanogen rom I was running and the new radio/spl were in place.
Click to expand...
Click to collapse
Sweet! This was the exact answer that I was hoping and searching for for hours. Thank you very much. I've been getting guesses and theories this whole time and I knew someone out there just had to have personal experience with it. Thank you.
WOW amazing script!! just downloaded and used it
works very well!! can't wait to see what else you can do with it.
the perfect addition to a world that includes xda devs. nice work!
This may a dumb question, but why is it necessary to do this if your app data is still sitting on your ext partition, isnt it going to look for apps there anyway if you have apps2sd setup automatically like in a CM rom?
Cheers
The current version of nandroid lets you switch
Between backups, but not all options are yet connected to the UI.
devsk said:
Currently,
A. nandroid backups do not contain the a2sd app folders.
B. nandroid backups are not tagged but instead are time stamp based, so if you forget you backed up your most stable ROM with all the setup done and apps installed at 11:01pm on Friday, you will have tough time getting it back.
It has been painful to say the least to jump between ROMs.
This script does two things:
1. Store and tag a ROM's nandroid backup and its apps data. You can provide any name for tagging while storing.
2. Restore a tagged ROM's app data and make its nandroid backup the latest so that the recovery console can restore from it.
The nice side effect of this is that you have complete environments you have created nicely bookmarked with easy to understand names and version numbers, ready to be restored easily. Eventually, this should be part of the nandroid in recovery image itself.
Requirements:
cyanogen's recovery image 1.3.1
attached script (only txt extension is allowed) downloaded to /sdcard/switchrom.sh
Usage:
1. Boot into recovery using Home + End buttons together.
2. To bookmark and tag current ROM,
Do a nandroid backup first
Go into console with Alt+X (or do adb shell from PC)
mount /sdcard
sh /sdcard/switchrom.sh store <name>
e.g.
I am backing up soulife-1.2.3 with
sh /sdcard/switchrom.sh store soulife-1.2.3
3. To restore a ROM,
Go into console with Alt+X (or do 'adb shell' from PC)
mount /sdcard
sh /sdcard/switchrom.sh restore <name>
e.g.
I am restoring soulife-1.2.3 with
sh /sdcard/switchrom.sh restore soulife-1.2.3
Go back to recovery screen (by typing 'recovery' on the shell prompt if you are on console)
Alt+w to wipe
Do a nandroid restore from latest backup
I have tested this script with cyanogen 3.9, soulife 1.2.3, drizzy's hero and JACMyTouchSki.
Click to expand...
Click to collapse
I must be missing something...
I would like to say first, I am sure there is something I am missing, but to me it would just seem easier to do this in the terminal:
Make a copy of whatever ROM you want to use and rename it to update.zip. I will use Soulife's Ion for example. Also using the assumption you have an update.zip file on hand. You can use the ls command to see what all ROMs you have on your sdcard.
$ su
# cd /sdcard
# rm -r update.zip
# cp soulife.ion.v.1.2.2.zip /sdcard/update.zip
# reboot recovery
Flash as normal
I usually keep my phone backed up using backup for root users. So I just restore all my text messages and settings from the SD card and that is it.
I guess that is more typing, but to me each individual command it simpler.
mookie3three said:
This may a dumb question, but why is it necessary to do this if your app data is still sitting on your ext partition, isnt it going to look for apps there anyway if you have apps2sd setup automatically like in a CM rom?
Cheers
Click to expand...
Click to collapse
Apps data is not portable between ROMs. You need to clean it up otherwise expect random FCs.
ccunningham83 said:
I would like to say first, I am sure there is something I am missing, but to me it would just seem easier to do this in the terminal:
Make a copy of whatever ROM you want to use and rename it to update.zip. I will use Soulife's Ion for example. Also using the assumption you have an update.zip file on hand. You can use the ls command to see what all ROMs you have on your sdcard.
$ su
# cd /sdcard
# rm -r update.zip
# cp soulife.ion.v.1.2.2.zip /sdcard/update.zip
# reboot recovery
Flash as normal
Click to expand...
Click to collapse
And lose all that you did with your current ROM. I think you did not get the point of this script.... This is for people who have setup their phone well with a ROM and don't want to lose its goodness but still want to test other ROMs and possibly have a couple of them on their phone which they can switch to & from.
ccunningham83 said:
I would like to say first, I am sure there is something I am missing, but to me it would just seem easier to do this in the terminal:
Make a copy of whatever ROM you want to use and rename it to update.zip. I will use Soulife's Ion for example. Also using the assumption you have an update.zip file on hand. You can use the ls command to see what all ROMs you have on your sdcard.
$ su
# cd /sdcard
# rm -r update.zip
# cp soulife.ion.v.1.2.2.zip /sdcard/update.zip
# reboot recovery
Flash as normal
I usually keep my phone backed up using backup for root users. So I just restore all my text messages and settings from the SD card and that is it.
I guess that is more typing, but to me each individual command it simpler.
Click to expand...
Click to collapse
The thing you are missing is that many apps do not have an option to export their settings, nor do they store them in an easily accessible place. Even if you manage to pull their settings off /data/data/ folders, you still have problems with restoring them. First off, you have to worry about their Linux permissions since they don't get preserved on the Fat32 partition. Second, simply pushing back the setting folders won't work for apps that use SQLlite database to store account info, so you're stuck with re-entering everything manually.
Take K9 Mail for example. I have 4 accounts (both IMAP and POP3) that I have to set up every time I wipe my phone or reformat the Ext partition. Same with progress on most games. A tar of the entire Ext partition combined with a Nandroid image resolves most of these issues.
I get an error during backup.
I take a nandroid backup, enter recovery terminal, type in "mount /sdcard" enter "sh /sdcard/switchrom.sh store lastramjet" type in yes at the confirmation prompt and the script starts it's magic.
However, after the "moving nandroid (or something)" I get an error saying "Cannot umount /sdcard device/resource in use/busy". After that I get a successfully bookmarked the backup message.
Not sure if this matters, but just wanted to let you know
Just curious, what happens if I follow the rooting steps in the other thread but only do this:
adb push /directory_you_placed_asroot2/asroot2 /data/local/
adb shell
chmod 0755 /data/local/asroot2
/data/local/asroot2 /system/bin/sh
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
cat sh > su
chmod 4755 su
At this point, what state is the phone in? Do I have full root access to the file system? What are the issues/concerns if I don't proceed with flashing the recovery image. Just trying to understand the process and what each step is for. I understand the part above but can't understand why you have to flash a recovery image and can't just use the phone after root is achieved.
Thanks in advance. FYI...all I want to do with root access is delete some system files, nothing more.
mobilehavoc said:
Just curious, what happens if I follow the rooting steps in the other thread but only do this:
adb push /directory_you_placed_asroot2/asroot2 /data/local/
adb shell
chmod 0755 /data/local/asroot2
/data/local/asroot2 /system/bin/sh
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
cat sh > su
chmod 4755 su
At this point, what state is the phone in? Do I have full root access to the file system? What are the issues/concerns if I don't proceed with flashing the recovery image. Just trying to understand the process and what each step is for. I understand the part above but can't understand why you have to flash a recovery image and can't just use the phone after root is achieved.
Thanks in advance. FYI...all I want to do with root access is delete some system files, nothing more.
Click to expand...
Click to collapse
You don't have to flash the recovery image. I believe from that code you would have root and can run programs that require root. However, you would be unable to flash a new rom or any other update.zip (which means no auto apps2sd), partition your sd card easily or backup your phone in case something goes wrong. I suppose you are probably just asking for the sake of asking and knowledge but this is why a recovery image is HIGHLY recommended.
chuckhriczko said:
You don't have to flash the recovery image. I believe from that code you would have root and can run programs that require root. However, you would be unable to flash a new rom or any other update.zip (which means no auto apps2sd), partition your sd card easily or backup your phone in case something goes wrong. I suppose you are probably just asking for the sake of asking and knowledge but this is why a recovery image is HIGHLY recommended.
Click to expand...
Click to collapse
thanks. So if I don't flash the recovery image, I can't update to cooked ROMs or do the stuff you suggested but will the phone otherwise function normal? i.e. I can update to a Sprint/HTC update, I can factory reset the phone (assuming that'll kill root), etc.? I may do the whole process with the recovery image later but don't need it right now.
I only need to do this as a stopgap until Sprint/HTC releases an update.
mobilehavoc said:
thanks. So if I don't flash the recovery image, I can't update to cooked ROMs or do the stuff you suggested but will the phone otherwise function normal? i.e. I can update to a Sprint/HTC update, I can factory reset the phone (assuming that'll kill root), etc.? I may do the whole process with the recovery image later but don't need it right now.
I only need to do this as a stopgap until Sprint/HTC releases an update.
Click to expand...
Click to collapse
Well, I wouldnt recommend doing a sprint update either. That will cause you to lose root most likely. The only way then to keep root is wait until we get a dump of the update and then cook a rom that includes root, in which case you would need to flash the recovery image. Updates usually fix the exploits we use to gain root.
chuckhriczko said:
Well, I wouldnt recommend doing a sprint update either. That will cause you to lose root most likely. The only way then to keep root is wait until we get a dump of the update and then cook a rom that includes root, in which case you would need to flash the recovery image. Updates usually fix the exploits we use to gain root.
Click to expand...
Click to collapse
What he said...but yes, at the steps you quoted, mobilehavoc, you are capable of root access (you don't actually have it until you run that "su" command ). That allows you to read and modify otherwise locked away files and tweak to your hearts content!
Ive rooted and played around some but very little and followed everyones instructions very closely ( thank you for teaching a newbie ). Now how do I go back to original state that I backed up ( think I did ).
When I press the power and volume down button I get to the droid on skateboard, then I press the Home for recovery. I get the screen with all the options and I go to nandroid v2.2 restore and press trackball. It says restore latest backup press home to confirm. I do that and get the following error
Error : run 'nandroid-mobile.sh restore' via console.
What does this mean? Do i have to be tethered to PC and run this command from cmd prompt?
I am now lost again, any help is appreciated
Grinder16 said:
Ive rooted and played around some but very little and followed everyones instructions very closely ( thank you for teaching a newbie ). Now how do I go back to original state that I backed up ( think I did ).
When I press the power and volume down button I get to the droid on skateboard, then I press the Home for recovery. I get the screen with all the options and I go to nandroid v2.2 restore and press trackball. It says restore latest backup press home to confirm. I do that and get the following error
Error : run 'nandroid-mobile.sh restore' via console.
What does this mean? Do i have to be tethered to PC and run this command from cmd prompt?
I am now lost again, any help is appreciated
Click to expand...
Click to collapse
Just to confirm since it wasn't mentioned, you did a Nandroid backup earlier right? can you confirm that there's a folder on your sdcard called "nandroid"?
thecodemonk said:
Just to confirm since it wasn't mentioned, you did a Nandroid backup earlier right? can you confirm that there's a folder on your sdcard called "nandroid"?
Click to expand...
Click to collapse
Dont see that folder - I guess that is not good. Any ideas?
Grinder16 said:
Dont see that folder - I guess that is not good. Any ideas?
Click to expand...
Click to collapse
You must do a backup BEFORE you can do a restore..
To clarify for everyone, here's a breakdown of the steps:
adb push /directory_you_placed_asroot2/asroot2 /data/local/
This copies the asroot2 program to the /data/local folder on your phone.
adb shell
This logs you into the phone. From here on out, you are no longer executing Windows commands from a DOS shell - you are actually executing Linux commands on the phone.
chmod 0755 /data/local/asroot2
This changes the permissions on the asroot2 program so that it can be executed.
/data/local/asroot2 /system/bin/sh
This actually runs the root exploit and creates a file called /system/bin/sh that we will later turn into su.
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
This unmounts the /system partition and remounts it as writeable.
cd /system/bin
This puts you into the /system/bin folder.
cat sh > su
This creates the su program.
chmod 4755 su
This changes the persmissions on the su file to allow it to be executed.
theresthatguy said:
You must do a backup BEFORE you can do a restore..
Click to expand...
Click to collapse
I thought I had. What are the steps? I have a flash recovery image on my SD card. I have followed all instructions that I could find
Grinder16 said:
I thought I had. What are the steps? I have a flash recovery image on my SD card. I have followed all instructions that I could find
Click to expand...
Click to collapse
Boot to the recovery image then select "nandroid backup"
jonnythan said:
Boot to the recovery image then select "nandroid backup"
Click to expand...
Click to collapse
Can you provide those steps? Sorry but complete newbie here
"I get the screen with all the options and I go to nandroid v2.2 restore and press trackball. It says restore latest backup press home to confirm. I do that and get the following error"
Go there but select Backup instead of Restore.
Turn the phone off, hold the Home key, and turn it on. When you get to the screen with the green text select nandroid backup.
NOTE: This is a work in progress. While I have completed this guide myself SEVERAL times to ensure accuracy, It is possible that typos or errors in understanding exist. Please use at your own risk, and expect NOTHING from me. I will do my best to update this guide and improve the formatting as I find time. Feel free to leave feedback!
I cannot stress this enough: always have backups of any important information. While we may not be able to do full image-based backups until after root, you can still make sure we aren't deleting needed data. While yes, Google should hold your most important data and allow you to sync at any time, what would you do if Google went down? And I've even had trouble using the "Offline" function for some of the Apps. Therefore, Make a copy of everything on your SD card and read this excellent guide from Lifehacker about how to backup Google Apps data: Lifehacker
You will need an SD card. I recommend AT LEAST an 8GB Class 4. Most actually recommend a Class 6 for use with apps2sd, but I just wanted to let you know that it would still work with a Class 4. For those unaware, apps2sd allows you to save internal phone memory by placing after-market applications onto your SD card. Most users notice a speed benefit from this.
If you would like to purchase a Class 6 SD card, you can get a one here with three sizes available (4GB, 8GB, 16GB):
A-DATA MicroSDHC Class 6 Turbo With SD Adapter
To ensure the best possible load, perform a factory reset, and WIPE your SD card!
Code:
Menu > Settings > Security > Factory data reset > Reset phone > Erase everything
TRUE FACTORY RESET (UN-ROOT)
If you, like me, have already rooted and are trying to perform this process over again, you will unfortunately have to download the original ROM and flash it in Windows.
Download: RUU_Hero_C_Sprint_1.29.651.1_signed_release.exe
Run in Windows (I used XP through VMWare Fusion), and this will return the phone to the TRULY factory loaded state. Any other Factory data reset will simply reload the last ROM image saved, which, if you rooted and loaded MoDaCo, would be MoDaCo. I am encouraging you to follow this process to avoid any problems that may exist while the phone is rooted or loaded with the unofficial ROM. And even if you perform this process as a first-time rooter, it certainly wont hurt!
ROOT HERO [MAC]
(This is the process that allows modifications to occur on your phone):
The guide I follow and can verify is this:
Rooting CDMA Hero [Mac]
I do not use Windows as a primary platform, so I would recommend following this guide if you are on Windows:
How to root the CDMA Hero (DETAILED Windows guide)
You should be able to return to this guide after you have successfully completed the root process on Windows. Continue from the section "NANDROID BACKUP" below.
Per the purpose of this guide, I will detail my exact steps from the "Rooting CDMA Hero [Mac]" post. Thanks ajones7279!
Plug in your phone
Download Android SDK: http://developer.android.com/sdk/index.html
Unpack, Rename the extracted folder to "AndroidSDK" (This is case sensitive!), and Move it to "Applications" (I consider the Android SDK a set of applications.)
Open TextEdit, Click Format>Make Plain Text, then copy and paste the following:
Code:
export PATH=${PATH}:/Applications/AndroidSDK/tools
Save as: ".bash_profile"
On Phone: Go to Settings > Applications > Development>USB Debugging and make sure the option is checked.
On your Mac: Download asroot2: http://zenthought.org/tmp/asroot2
Save this file into: /Applications/AndroidSDK/tools
Open Terminal and run the following commands (You can copy and paste):
Code:
cd /Applications/AndroidSDK/tools
adb push asroot 2 /data/local
adb shell chmod 0755 /data/local/asroot2
adb shell
/data/local/asroot2 /system/bin/sh
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
cat sh > su
chmod 4775 su
exit
exit
At this point, the phone has root access.
Download: http://rapidshare.com/files/303797523/recovery-RA-heroc-v1.2.3.img
Save this file into: /Applications/AndroidSDK/tools
Go back to your terminal and type:
Code:
adb push recovery-RA-heroc-v1.2.3.img /sdcard/
adb shell
su
flash_image recovery /sdcard/recovery-RA-heroc-v1.2.3.img
exit
exit
adb shell reboot recovery
Now, the phone will reboot into recovery mode. To preserve our freshly rooted state, we will make a Nandroid backup.
NANDROID BACKUP
*NOTE: These steps assume that you have already entered Recovery Mode on the phone through Terminal "adb shell reboot recovery" or the "Quick Boot" app.*
On phone: Using the trackball, scroll down and select "Nandroid v2.2 backup". This will create a backup of the phone in its freshly rooted state to your SD card, under the nandroid directory.
After it completes the backup, we want to make sure that we have the backup "backed up" by copying it to our Mac (Just in case anything happens to the SD card!).
Select "USB Mass storage on"
After your SD Card appears, copy the contents of the "nandroid" folder to anywhere you wish on your Mac (You are using Time Machine right?)
Once the copy is complete, eject the sdcard in mac and select "USB Mass storage off" on the phone.
NOTE: Nandroid does not backup the contents of your SD card. If you don't want to lose what's on your SD card, MAKE A BACKUP COPY!
From this point forward, if you do something that seems to really mess with the phones functionality, you can simply go back to your Nandroid backup!
RESTORE NANDROID BACKUPS
Select "Nandroid v2.2 restore" *THIS WILL ERASE EVERYTHING ON YOUR PHONE*
Your phone will be returned to the condition it was in as of the last Nandroid backup. You can control which backup is restored by deleting the unwanted, time-stamped folders within the "nandroid" directory on your SD card. If you leave only one time-stamped backup folder, that is the backup that will be restored.
Note that this will leave the custom Recovery ROM we loaded (recovery-RA-heroc-v1.2.3.img) in place.
I actually perform a Restore after every Backup. While this takes extra time, you know your Backup is intact and not corrupted in any way!
If you are looking for a complete factory reset, you will need to scroll up to "TRUE FACTORY RESET (UN-ROOT)"
PREPARE SD CARD FOR APPS2SD (A2SD)
For those unaware, apps2sd allows you to save internal phone memory by placing after-market applications onto your SD card. Most users notice a speed benefit from this.
Select "Wipe SD: fat32+ext2+swap" *THIS WILL ERASE EVERYTHING ON YOUR SDCARD*
Select "USB Mass storage on"
The mounted drive should now be empty. Double-check that it was partitioned correctly by opening Disk Utility and verifying 3 partitions on the sdcard: NONAME, disk1s2, and disk1s3. Close Disk Utility.
LOAD Unofficial MoDaCo 1.2c Core ROM
Forum Post: Unofficial MoDaCo 1.2
Download: Unofficial MoDaCo 1.2c Core
Save this file into: your SD card. (the root of your SD card, probably named "NONAME" if you didn't change it. You can change it to whatever you want though.)
Save the file as: "update.zip" (Or rename it)
Eject your sdcard and Select "USB Mass storage off"
Select "Apply sdcard:update.zip"
Select "Reboot system now"
If it successfully loaded, you now have a fresh load of the Unofficial MoDaCo 1.2c ROM! Congrats!
I would recommend that you create another Nandroid backup. Scroll back up to "NANDROID BACKUP" and follow the steps over again and come back to this point.
Now you are ready for the workarounds!
Guide: Workaround Issues (Unofficial MoDaCo 1.2c)
Why'd you make another guide?
nice guide man, no need to respond why you made another guide, the more the merry, nicely detailed as well
Shhhhhh.
I was just curious because there are like six...
I made another guide because while many of the forum posts acomplish bits and pieces, my guide provides the overall picture. Root, ROM, and Backup. And my upcoming "Workarond Issues" guide will collect scattered information in a similar fashion.
I find it ironic that I thanked you for your contribution and you find this guide excessive. Would you prefer that I removed the guide?
No not at all. Yours is nice and concise. There's just a lot, that's all. That's why I said it would be nice if a moderator could have merged all the ones that were already written at the end of mine. Didn't mean any harm.
Ah, I see what you mean. To be honest, I am also making this guide for self reference. If most all of the information I need is together its easier to help myself as well as my friends and the community. Thanks again for all your contributions.
Just to raise awareness, Nandroid does NOT back up your apps if you are using AppsToSD as in MoDaCo. You must back up your apps separately.
True, thanks for the heads up. I'll work on a separate guide that details how to backup your other apps. I believe that anything after-market can be backed up and restored through ASTRO though, and this is much easier for most than adb and Terminal commands (push/pull).
The whole 1.56.651.2 Firmware update is also making me wait to post any further guides, as some of my worksarounds may prove useless. It looks like we still have the Apps Renaming and Reverting issue though, and I didn't see the Sprint admin adress such issues specfically.
?
ok i did the update to the hero. and now found out about rooting(im new to all this) do i run that program you put in the beginning with windows? and then does that rom resolve the issue with battery with sms and other things the OTA update fixed? or should i get another rom or .img idk what to call it really and what does RUU stand for?
Alright,
A couple things to add to this guide, for the complete noob, as I can try to explain it a little more clear.
This should be done prior to doing anything within the guide.
First, connect your phone to your computer and mount your sd card. This can be done by connecting the usb cable, then on your phone, drop down the menu and chose, connect to p.c., Mount SD card. Make a folder and backup your entire sd card to this folder. Once done, delete everything off the card. if you don't, you will run into format and partitions errors later in the guide.
Eject the sd card on the computer, and end usb sharing on the phone. remove the USB cable from the computer.
Next, on the phone Go to Settings > Applications > Development>USB Debugging
Make sure that USB debugging is NOT CHECKED. If its checked later in the guide you will run into errors pushing the files onto the phone.
At this point you can start the guide from the beginning, under the main heading Root Hero [MAC]
I am running OSX 10.6.2 so i ran into a couple of issues.
Next. Under the part where you have to create the .bash file. This file should be saved in your user folder.
/Users/USERNAME where USERNAME is the name of your user account.
For instance my User account is Hamspiced so my user folder is:
/Users/Hamspiced/
when saving the file, uncheck "if no extension is provided, use .txt".
Next, I couldn't copy paste the code because it wasn't parsed properly. This is what i had to do.
And this should be a direct copy paste into terminal. If you don't know how to access terminal click the spyglass in the upper right hand of the screen, and type in terminal. then you should be able to directly copy paste this text.
Code:
cd /Applications/AndroidSDK/tools
./adb push asroot2 /data/local
./adb shell chmod 0755 /data/local/asroot2
./adb shell
/data/local/asroot2 /system/bin/sh
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
cat sh > su
chmod 4775 su
exit
exit
As stated you should have root access on the phone. you can verify this by downloading Terminal emulator from the Market, then running the app. Once inside the app if you hold Menu, you should bring up the onscreen keyboard. if you type in "su" (stands for super user) it will change the prompt from $ to #. If yours does not change, start over, something went wrong. If it did change then you can proceed to the next part of this guide.
Next the guide is trying to put the recovery Image to your phone. This doesnt restore your phone, it just puts the recovery portion to it, and it allows you to do all the cool things to your phone, like allow you to create backups, restore backups, and load customs roms.
again i ran into issues with parsing the correct format so these are copy pastes from terminal.
Code:
./adb push recovery-RA-heroc-v1.2.3.img /sdcard/
./adb shell
su
flash_image recovery /sdcard/recovery-RA-heroc-v1.2.3.img
exit
exit
adb shell reboot recovery
If you get an access denied error pushing the recovery image, its because you had debugging turned on prior to connecting your phone to the computer. it must be off, then turned on once the phone is connected.
This will result in headaches, and endless google searching with no results.
Follow the rest of the guide regarding the Nandroid backup this backs up the entire phone settings. you want to save the raw phone backup as well as the backup after you load the rom. both are incredibly important!
Prepare SD Card for Apps2sd….
If when you checked Disk Utility and your SD card didnt partition properly follow these steps.
You must erase everything on your sd card for these steps to work. I ran into errors creating the partition. What i had to do was in the recovery mode chose factory recovery. when the phone restarted i had to go to Settings>Security>Factory Data Reset.
This restored EVERYTHING. THe phone, Sd Card, Etc. Everything was lost, however since in the begining, we made a backup of the SD card, and then we made a backup of our phone, we are fine.
Restart the phone in recovery mode once this finishes and restarts. (Hold Home and Power to turn on)
Next chose Part SD: fat32+ext2+swap this will partition the card properly. Then choose restart phone.
Once the phone restarts, we have to go through the normal steps that we did once we first received the phone for its first bootup. connect it to the computer, transfer over the Nandroid backup that should be saved from the first time you saved it on your phone. then restart the phone again in recovery mode.
Now you need to restore the nandroid backup. since you transferred it over, its the only nandroid backup there is, it will restore the phones origional settings. from here you can load the official MoDaCO rom fine on the SD card that is now formatted properly.
These are about all the issues and resolutions i ran into. Hopefully it helps someone else.
Guess it's subjective. I think I haven't turned off USB Debugging since shortly after I got the phone and didn't run into any problems. It's always on before I plug it in and I haven't ran into any errors while pushing a file to my sd card. Also didn't erase my sd card before I formatted (did back it up though of course) and everything went smooth. Dunno. It's always good to hear from diff people though. Also just edited my thread, thanks for the heads up.
need help rooting htc hero from sprint
i have 1.5 firmware bb version is 1.04.01.09.21 kernel version 2.6.27-533ce29dhtc [email protected] build number1.56.651.2 cl85027software 1.56 cant get root on this device can someone please help me
quis5550 said:
i have 1.5 firmware bb version is 1.04.01.09.21 kernel version 2.6.27-533ce29dhtc [email protected] build number1.56.651.2 cl85027software 1.56 cant get root on this device can someone please help me
Click to expand...
Click to collapse
Try here
http://forum.xda-developers.com/showthread.php?t=581686&highlight=root+mac
First, excellent guide! Personally, I used Universal Androot (snipurl.com/uaroot) to root my Hero, but this was a huge help in getting the SDK installed!
I'm running into a problem while trying to do the Nandroid backup. When I try to flash the recovery image, I get the following error message....
AJBlue98$ ./adb shell
$ cd /sdcard/
$ su
# flash_image recovery recovery-RA-herocv1.6.2.img
flash_image: not found
Click to expand...
Click to collapse
I even try the command with the leading "./" and I get essentially the same thing...
# ./flash_image recovery recovery-RA-herocv1.6.2.img
./flash_image: not found
Click to expand...
Click to collapse
I'm running the latest official Sprint 2.1 ROM on my Hero and Terminal on Mac OS X Snow Leopard 10.6.4 on a late-2009, 17 in. MacBook Pro. Oh, and I installed the Android SDK into another directory (had it installed before I found this tutorial), so here's my $PATH...
-bash: type: /opt/local/bin:/opt/local/sbin:/Users/AJBlue98/soylatte/bin:/Users/AJBlue98/android-sdk-mac_86:/opt/local/bin:/opt/local/sbin:/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/texbin:/usr/X11/bin: not found
Click to expand...
Click to collapse
Am I missing something? I'll really appreciate the help!
—Adam
ajblue98 said:
First, excellent guide! Personally, I used Universal Androot (snipurl.com/uaroot) to root my Hero, but this was a huge help in getting the SDK installed!
I'm running into a problem while trying to do the Nandroid backup. When I try to flash the recovery image, I get the following error message....
I even try the command with the leading "./" and I get essentially the same thing...
I'm running the latest official Sprint 2.1 ROM on my Hero and Terminal on Mac OS X Snow Leopard 10.6.4 on a late-2009, 17 in. MacBook Pro. Oh, and I installed the Android SDK into another directory (had it installed before I found this tutorial), so here's my $PATH...
Am I missing something? I'll really appreciate the help!
—Adam
Click to expand...
Click to collapse
yeah, you're missing the "flash_image" binary on your phone lol search xda for it and push it to /system/bin, then try the command again.
regaw_leinad said:
yeah, you're missing the "flash_image" binary on your phone lol search xda for it and push it to /system/bin, then try the command again.
Click to expand...
Click to collapse
Thanks, regaw_leinad, for the lead! I found a copy of the flash_image file and copied it to my Android SDK folder, but when I try to push it to my phone, I get this:
AJBlue98$ ./adb push flash_image /system/bin
failed to copy 'flash_image' to '/system/bin/flash_image': Permission denied
failed to copy 'flash_image' to '/system/bin/flash_image': Read-only file system
Click to expand...
Click to collapse
(I rebooted the phone and tried again after my original post. The error message changed. BTW I'm connected via USB with debugging turned on and "Charge only" selected as my connection type.)
I've tried running adb as root, but I get this:
AJBlue98$ ./adb root
adbd cannot run as root in production builds
Click to expand...
Click to collapse
Again, any help will be greatly appreciated!
—AJBlue98
ajblue98 said:
Thanks, regaw_leinad, for the lead! I found a copy of the flash_image file and copied it to my Android SDK folder, but when I try to push it to my phone, I get this:
(I rebooted the phone and tried again after my original post. The error message changed. BTW I'm connected via USB with debugging turned on and "Charge only" selected as my connection type.)
I've tried running adb as root, but I get this:
Again, any help will be greatly appreciated!
—AJBlue98
Click to expand...
Click to collapse
ok type
adb shell
then
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
to mount it as r/w
then try the flash image command again.
Adb root or adb remount won't work, because your boot.img isn't patched yet.
regaw_leinad said:
ok type
adb shell
then
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
to mount it as r/w
then try the flash image command again.
Adb root or adb remount won't work, because your boot.img isn't patched yet.
Click to expand...
Click to collapse
Okay, I did that. I'm still charge-only and debugging turned on, and here's what happened.
(N.B.: I'm on a Mac, so I have to include "./" before running an application in the current directory. Also, I'm including "AJBlue98" in front of my "$" prompts to differentiate my Mac's local prompts from the adb shell prompts.)
AJBlue98$ ./adb shell
$ mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount: Operation not permitted
Click to expand...
Click to collapse
So I tried these few things...
$ su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
# cd /sdcard/
# mv flash_image /system/bin
failed on 'flash_image' - Cross-device link
# exit
$ exit
AJBlue98$ ./adb shell su mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Permission denied
AJBlue98$ ./adb push flash_image /system/bin
failed to copy 'flash_image' to '/system/bin/flash_image': Permission denied
Click to expand...
Click to collapse
Now I'm completely flummoxed. As always, please help and thanks in advance!
Update: I got frisky, so I tried this, just for the heck of it...
AJBlue98$ ./adb shell
$ su
# cd /sdcard
# ./flash_image recovery /sdcard/recovery-RA-heroc_v1.2.3.img
./flash_image: permission denied
# chmod 755 ./flash_image
# ./flash_image recovery /sdcard/recovery-RA-heroc_v1.2.3.img
./flash_image: permission denied
# su ./flash_image recovery /sdcard/recovery-RA-heroc_v1.2.3.img
Permission denied
Click to expand...
Click to collapse
Update 2:
I got some help at irc.twit.tv from a good soul in the #twitlive channel, who pointed me to ROM Manager (downloadable from the Market). That just did the whole backup, hey-presto, no flash_image BS required.
Thanks for the help anyway, all!
ajblue98 said:
Okay, I did that. I'm still charge-only and debugging turned on, and here's what happened.
(N.B.: I'm on a Mac, so I have to include "./" before running an application in the current directory. Also, I'm including "AJBlue98" in front of my "$" prompts to differentiate my Mac's local prompts from the adb shell prompts.)
So I tried these few things...
Now I'm completely flummoxed. As always, please help and thanks in advance!
Update: I got frisky, so I tried this, just for the heck of it...
Update 2:
I got some help at irc.twit.tv from a good soul in the #twitlive channel, who pointed me to ROM Manager (downloadable from the Market). That just did the whole backup, hey-presto, no flash_image BS required.
Thanks for the help anyway, all!
Click to expand...
Click to collapse
sweet, glad you got it worked out
there were a few errors in what you did above, but looks like you got everything working without it, so that's good
I know, another thread about unrooting, but its a spin on the other threads that allows you to go back from hboot 1.47 to 1.41
I set out to unroot because I wanted to have my phone serviced by Sprint, only to find out that I was unable to use most methods because I had flashed the test RUU a few months back. (http://forum.xda-developers.com/showthread.php?t=661057) My hboot was the wrong version and I was getting the version check errors. Everyone seemed to say you could never go back to hboot 1.41. I could easily Nandroided back to an unrooted stock and reflash the recovery image, but that still leaves traces of the test RUU. After reading several posts and putting 2 and 2 together, I was able to successfully unroot and remove all traces of 2.1. I take no credit for this method other than putting a couple of methods together.
REQUIRES ANY CUSTOM RECOVERY IMAGE THAT SUPPORTS FLASHING A ZIP
ROOT
Ensure your phone is ROOTED
From Command Prompt
cd to your AndroidSDK\tools directory
Code:
adb push asroot2 /data/local/
adb shell chmod 0755 /data/local/asroot2
adb shell
/data/local/asroot2 /system/bin/sh
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
cat sh > su
chmod 4775 su
RADIO & HBOOT
Mount SD Card to USB
Copy STOCK-RADIO.ZIP & STOCK-HBOOT.ZIP to /sdcard/
Reboot Recovery
Flash STOCK-RADIO.ZIP & STOCK-HBOOT
Reboot
HERCIMG.ZIP AND Image Files
Mount SD Card to USB
Copy HERCIMG.ZIP to /sdcard/
Copy boot.img to /sdcard/
Copy recovery.img to /sdcard/
Copy misc.img to /sdcard/
Unmount SD Card to USB
FLASH IMAGE FILES
From Command Prompt
cd to your AndroidSDK\tools directory
Code:
adb shell
su
flash_image recovery /sdcard/recovery.img
flash_image boot /sdcard/boot.img
flash_image misc /sdcard/misc.img
FLASH HERCIMG.ZIP
Reboot phone to HBOOT by holding volume down while pressing power on
Press action (the trackball) when prompted
Reboot Phone
RESTORE PRL
Dialed ##786# (takes a while to come up)
Menu
Reset
Enter MSL. Phone will reboot into Recovery and format cache and data.
Reboot. Check PRI to be sure it went back to 1.70_003
Reboot
DONE
This worked perfectly for me. Haven't done it more than once, so try at your own risk. I assume your probably could flash the 1.56 RUU after you flash the image files instead of HERCIMG.ZIP but I didn't try. I actually was headed down a different path but left HERCIMG.ZIP on my sdcard when I booted to hboot.
Again I take no credit.
Here are the threads I compiled the information from.
http://forum.xda-developers.com/showthread.php?t=657086
http://forum.xda-developers.com/showthread.php?t=654119
Credit to:
dfbonney
rt1oo
And their respective sources
Downloads:
http://www.megaupload.com/?d=GK3Q435L
You can also download these from the threads above.
Sorry about the formatting...first long post.
I nominate you to run the release-signed RUU and try it
regaw_leinad said:
I nominate you to run the release-signed RUU and try it
Click to expand...
Click to collapse
lol..i was gonna ask who wants to be the guinea pig and try it
Sorry guys...I was just trying to help out by posting this. I realize there are already threads for this. I really needed my phone serviced and didn't want the risk of them flagging the thing.
I only wish I knew enough to root the new RUU.
eme82 said:
Sorry guys...I was just trying to help out by posting this. I realize there are already threads for this. I really needed my phone serviced and didn't want the risk of them flagging the thing.
I only wish I knew enough to root the new RUU.
Click to expand...
Click to collapse
wait... the one that was released today?? I rooted that 3 weeks ago, with my Regaw Root Method.
And then I woke up. <-----------
@ eme82
RADIO & HBOOT
Mount SD Card to USB
Copy STOCK-RADIO.ZIP & STOCK-HBOOT.ZIP to /sdcard/
Reboot Recovery
Flash STOCK-RADIO.ZIP & STOCK-HBOOT
Reboot
HERCIMG.ZIP AND Image Files
Mount SD Card to USB
Copy HERCIMG.ZIP to /sdcard/
Copy boot.img to /sdcard/
Copy recovery.img to /sdcard/
Copy misc.img to /sdcard/
Unmount SD Card to USB
I'm having difficulties finding the files you used. I wanted to use exactly the ones you used. Would it be to much trouble to link direct downloads? I did find and download HERCIMG.ZIP.
The ones I need:
STOCK-RADIO.ZIP & STOCK-HBOOT.ZIP
boot.img
recovery.img
misc.img
I'm sure you used general wording to describe the files you used, I just wanted to make sure I use everything you used to be successful.
Again, I hope it's not to much trouble. Thanks for the post.
Chaid said:
@ eme82
RADIO & HBOOT
Mount SD Card to USB
Copy STOCK-RADIO.ZIP & STOCK-HBOOT.ZIP to /sdcard/
Reboot Recovery
Flash STOCK-RADIO.ZIP & STOCK-HBOOT
Reboot
HERCIMG.ZIP AND Image Files
Mount SD Card to USB
Copy HERCIMG.ZIP to /sdcard/
Copy boot.img to /sdcard/
Copy recovery.img to /sdcard/
Copy misc.img to /sdcard/
Unmount SD Card to USB
I'm having difficulties finding the files you used. I wanted to use exactly the ones you used. Would it be to much trouble to link direct downloads? I did find and download HERCIMG.ZIP.
The ones I need:
STOCK-RADIO.ZIP & STOCK-HBOOT.ZIP
boot.img
recovery.img
misc.img
I'm sure you used general wording to describe the files you used, I just wanted to make sure I use everything you used to be successful.
Again, I hope it's not to much trouble. Thanks for the post.
Click to expand...
Click to collapse
They Are in the first post..
i unrooted with success, my only problem its still stuck with the 2.42.01.0427 radio...i tried flashing the stock 1.5 radio via recovery but no luck, can some please help? it would b greatly appreciated
I'm trying to downgrade my hboot (currently have 1.47). I'd like to try this method, but the direct download file listed in the first post no longer seems to work. Does anyone know where I can find a copy of those files, or another method of downgrading hboot? I was able to go from spint's official 2.1 rom back down to 1.56, but it didn't seem to help with downgrading my bootloader. Thanks!
This method we will use nandroid's recovery option in ClockworkMod
Requirements:
Rooted myTouch 3G 1.2 with USB Debugging
ClockworkMod Recovery Installed (can be install from ROM Manager)
Universal Androot apk saved to your AndroidSDK tools folder
(I will be doing this in adb)
Create the recovery folders
Code:
mkdir /sdcard/clockworkmod
mkdir /sdcard/clockworkmod/backup
mkdir /sdcard/clockworkmod/backup/Stock
Mount the SD card so you can access it on your computer.
Now extract SAPPIMG_Sapphire_T-Mobile_US_2.10.531.4_release_signed.zip (from shipped-roms) [FYI: I had to use 7zip for this] into clockworkmod/backup/Stock.
Now we are down with that unmount it and return to adb.
Once your phone has remounted the SD card do:
Code:
cd /sdcard/clockworkmod/backup/stock
md5sum * > nandroid.md5
cd ../../../
cat /system/bin/flash_image > flash_image
(If you do not have flash_image post here in this thread and I will pm you a link to it)
Reboot the phone and boot into recovery mode (hold home when powering on)
Once in there
**DO A FULL WIPE**
then restore the "Stock" backup from the restore menu,
It should get past boot and system then fail on /data THIS IS NORMAL
It is not safe to reboot your phone
Set up your phone and all that good stuff, then re-enable adb debugging.
in a command prompt cd to your androidsdk/tools folder and run
Code:
adb install UniversialAndroot.apk
and reroot your phone (bare with me)
once that is done do
Code:
adb shell
su
be sure to click allow on the Superuser Permission pop up that shows up on the phone
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/app
rm Superuser.apk
cd ..
cat /sdcard/flash_image > flash_image
chmod 0700 flash_image
./flash_image recovery /sdcard/clockworkmod/backup/Stock/recovery.img
rm flash_image
mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system
exit
unroot your phone via universal androot and uninstall it via the applications menu
reboot and done!
I have done this a couple times and every time it worked like a charm.
Hey there, I get to inputting the md5 command, but I get cannot create nandroid.md5: permission denied
What am I doing wrong?
Using a SAPPIMG.zip is not at all unsafe and is faster and easier.
Well, I have been trying to use the sappimg.zip from unlockr's guide and on the t-mobile dev forums, but yet all of them end up giving me a Main version is older! error.
I cant seem to find the solution.
I've had the same problem. I have made the gold card a million times (worked rooting the phone) and now it tells me the older error. Thought it would be easier reverting back, guess that's not true.
Anyways, can I get the flash_image file?
getting past the "older version" error
what i did to get past the "older version" error, was this:
step1: re-use gold card and the 1.5 version sappimg.zip from unlockr.com
step2: reboot using the original sappimg for t-mobile (i wont link from the post but i found it on XDA aka use search)
this will reload EVERYTHING as stock MT3g1.2 including original splash, and recovery images.
if you want to revert it to stock, try this: http://forum.xda-developers.com/showthread.php?t=641174, it may help
The safer way is to NOT BOTHER.
The update schedule is to run from today through the 25th inclusive. That's 11 days. The average length of time that any particular user will have to wait is therefore 5.5 days. Chances are that the update will be posted by tonight or tomorrow (latest), and 10 minutes later, it will be fixed so that it doesn't rob you of root (keep your options open!).
So... you save about 5 days of waiting (average) and end up with your options wide open. OR, you can commit to the average and end up locked out, possibly forever.
I like the way you think...
Sent from my T-Mobile myTouch 3G using XDA App
Need eng spl
bartcrusades said:
well, i have been trying to use the sappimg.zip from unlockr's guide and on the t-mobile dev forums, but yet all of them end up giving me a main version is older! Error.
I cant seem to find the solution.
Click to expand...
Click to collapse
just got through doing the same thing tried goldcard method and still got main version older....then i got it right...flash eng spl i beleive it was 0010 then do the sappimg.zip it works and when you finish the update your 0013 spl is back...then used universal androot installed superuser then installed rom manager and made backup of stock then put my phone back the way it was hopefully when the update comes out and i do think it will be a long time before it does i can restore backup of stock unroot with universal androot and uninstall superuser. At least thats the plan. If you want to do this look for kennys posts in the sappimg thread his directions are what i used.
That is the correct way to do it. Eng spl then tmo stock image. When done its back to completely stock.
Sent from my T-Mobile myTouch 3G using XDA App
hey i do not have flash_image can u post up a link? thanks.