Related
Why should you root your Dream/G1?
You can install a full Linux distribution, like Debian.
You can run applications that require root, like Screenshot and Auto Rotate your Browser and or any other application.
You can install the latest Android build directly from the Android source tree.
Customize your boot image.
Create full backups of the state of your phone.
Create custom ROMs.
Install Applications to your SD Card to save space.
Use your phone as a tether to connect your computer/laptop to the internet.
Turn your phone into a wireless router that provides internet access.
Well, hopefully one of those reasons convinced you to get root access on your phone!
Preparing to Get Root on your Phone
Getting root on your phone involves exploiting a security hole that existed in an early version of Android. The versions with the security holes are known as RC19, RC28, and RC29 (or RC7 or lower for UK phones). As of RC30 (RC8 on UK), Google patched the security hole so that your phone can not be rooted (don't worry, we can still root it!).
To check your version, go to the Home Screen, click your menu button, choose "Settings", and then click "About phone". You will then see the following screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you have US-RC30/UK-RC8 or higher, you will first need to downgrade your phone to a previous version. (Skip these steps otherwise)
Format your phone's SD card to FAT32 mode:
Hook your phone up to your computer using a USB cable and then wait for the notification to show up in your title bar of your phone.
Click the notification, and then click "Mount".
A new removable disk should show up on your computer. Right click it and select Format, and select FAT32 as the file system type.
Download and unzip the RC29 or RC7 image file. Copy the DREAIMG.nbh file to the SD card. (RC29 for US, RC7 is for UK)
Turn the device power off.
Hold Camera button, and press Power button to entry boot loader mode. You should see a gray/white screen with instructions to flash your phone with the update on your SD card. If you don't see that, make sure you followed the instructions properly.
As per the on-screen instructions, press the Power button to start upgrade procedure. DO NOT DO ANYTHING TO INTERRUPT THIS PROCESS.
After it is finished, perform the restart your phone.
Rooting your RC29 or lower phone:
On RC29 phones and lower, anything you type into your keyboard is also being run in a hidden console with root permissions. More information regarding that at the bottom of this post. But, to get root access, do the following:
Instructions:
Download recovery.img or the new version by Amon recovery-RA-dream-v1.5.2.img and copy it to your SD card (see the previous instructions on how to copy from your computer to your Phone's SD card).
Download the Hard SPL and copy the zip file to the SD card.
All files must be on the root of your SD card.
Restart your phone. Wait for your phone to start up fully and show the home screen.
After your phone starts up, hit the enter key twice, type "telnetd" and press enter. (Yes, it will start up a contact search, don't worry. Just type it.)
Download an Android "Telnet" application from the Market and connect to localhost.
If you connect successfully, you will have a root prompt "#".
Type the following into Telnet (these commands will give you root access easier in the future):
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd sdcard
flash_image recovery recovery.img
cat recovery.img > /system/recovery.img
Now you have root!
What To Do Now That You Have Root
Now that you have root, you will want to apply "Hard SPL" to your phone. HardSPL is what will allow you to apply flash images from other regions (like UK on US phones, and vice versa), create full backups of your phone, install the latest build from the Android source, and usually resurrect your phone if it is "bricked". You have already downloaded the file to your SD card, so now you can apply it.
Power off your phone.
Start up in recovery mode by holding home and pressing power.
You will now enter recovery mode. You should see an exclamation.
If you do not see a menu on screen, press Alt-L to show the menu.
Press Alt-S to apply the update from the SD card.
After the update is complete, hold Home and press Back to restart.
And now, the last step! You are still running an old version of Android, but you want to upgrade to the latest and greatest update! You can do this, and not lose root by downloading modified versions of the updates.
First, choose a modified image from the list below:
ADP1.1: (md5: bacc58302e0b239d66c7bcc8db6c434b)
http://jf.odiness.com/v1.41/JFv1.41_ADP1.1_BuildEnvironment.tar.gz
http://android-dls.com/forum/index.php?f=24&t=241&rb_v=viewtopic
http://andblogs.net/2009/01/jesusfrekes-14-images-are-out/
RC33: (md5: f24b6c237775147cb4bc42efc2393973)
http://jf.odiness.com/v1.41/JFv1.41_RC33_BuildEnvironment.tar.gz
http://android-dls.com/forum/index.php?f=24&t=241&rb_v=viewtopic
http://andblogs.net/2009/02/new-rc33-based-images-from-jesusfreke/
RC8: (md5: de2d0d34adbb4015ee3aa5e4e7ca3c07)
http://jf.odiness.com/v1.41/JFv1.41_RC8_BuildEnvironment.tar.gz
http://android-dls.com/forum/index.php?f=24&t=241&rb_v=viewtopic
http://andblogs.net/2009/01/jesusfrekes-14-images-are-out/
Download the image.
Rename it to update.zip.
Copy it to your phone's SD card.
Turn your phone off.
Start up in recovery mode by holding Home and pressing Power.
Press alt-W to wipe your device. (You need to do this, or the device may hang at the flashing Android screen)
Press alt-S to apply the update.
And that's it! Remember to check the links up top to learn how to use root to do the advanced things I mentioned.
Rooting, Hacking, and Flashing your G1/Dream
Reserved for future posting
Wow this is great news keep the community updated. thanks man
EDIT:i just tested it my self!! your right this seems like root to me
Koush said:
I verified this by remounting the /system partition as read write and changing files around.
Click to expand...
Click to collapse
How did you do that?
Wow, good job!
I classify this as a major "oops" on Google's part...
humble said:
How did you do that?
Click to expand...
Click to collapse
mount -oremount,rw /dev/block/mtdblock3 /system
You can't remount that directory that unless you have root.
Use the dd command to copy stuff around (the cp command is not available). I should mention I'm a Windows guy, and am pretty clueless with Linux: my coworker figured the rest of this out once I got to a root prompt.
Incidentally, in the /system/bin directory there is a flash_image executable that changes the recovery.img used when you hard reset the device. I've noticed that I can run this without root access from a standard adb shell. Maybe we never needed to root the device after all... I think we can flash it without root access... I'm too scared to mess with that at all though.
i just rebooted from telnet!!! i must say this is cool
thanks dude I'm going to give it a run(not flashing) I'm scared too 428 and some change down the draine nooo
Yes!!! Now we dont even have to worry about the update.zip file!
Well, it still will be usefull for package updates.
I'm goin for the bootloader and pretty soon we'll be able to port Android to other HTC devices aswell.
Maybe this can be usefull its kind of old buthttp://benno.id.au/blog/2007/11/13/android-under-the-hood
well
i don't konw how safe it is but you can just chmod 777 files and access them through the glance file manager. can't open but you can copy and past them on the sd card and open from there. i wish i could figure out how to see them
i keep getting "Error running telnet: permission denied" in LogCat. any ideas ? i have rc29
hrm
i'm now getting Unable to chmod *******: Read-only file system across the board /////////////////nm i'm retarded
Koush said:
mount -oremount,rw /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
If you want to edit anything, you have to remount it as read/write.
yeah i forgot i rebooted my phone, lol just trying to see if i can figure out how to change the view when you mount the sd card to show all files.
anyone with RC29 getting root access ?
yeah i am
not that i know what to do with it
can u describe the steps ? i keep getting Permission denied
anyone know where the boot code is so I can tell it to mount all folders as read write at boot?
quedijo said:
Yes!!! Now we dont even have to worry about the update.zip file!
Well, it still will be usefull for package updates.
I'm goin for the bootloader and pretty soon we'll be able to port Android to other HTC devices aswell.
Click to expand...
Click to collapse
Good news!
Hope someone can develop something for Universal!
Cheers to all,
neerhaj said:
can u describe the steps ? i keep getting Permission denied
Click to expand...
Click to collapse
http://android-dls.com/forum/index.php?f=15&t=151&rb_v=viewtopic
All the steps are laid out there. pterminal downloadable and all.
WOW AFTER AGES>>>>>>> FINALLY!!!! YAY!!!
First i would like to thank every one who made this possible , im sorry i dont know ur names..
This is what i did i dont know if itll work for every one but fingers crossed....
1. its like the normal rooting procedure except with the boot.img that i have!!! U need the sdk for this to work!!
2. Download superhero rom v2: http://www.megaupload.com/?d=3Y02RZAT
3. rename as update.zip and place on sdcard.
4. Shutdown phone.
5. Download: http://rapidshare.com/files/248983573/recovery-RAv1.0H.img
6. place this img in the tools folder of the sdk.
7. Start phone in fastboot mode (power+voulme)
8. from the fastboot menu in cmd restart phone with the boot image provided above. (c:\sdk\tools fastboot boot recovery-RAv1.0H.img).
UPDATE:: DO A NANDROID BACKUP THEN USE THE BOOT.IMG THAT WAS BACKED UP BY NANDROID (ON YOUR SD CARD) FOR STEP NUMBER 12/13/14..
9. wipe data and update .
10. reset phone but remove battery when the rogers sign comes on.
11. go to flashboot mode again.
12. .......... use backed up boot.img
13. place this in the tools directory of the sdk
14. in cmd again flash the boot image (c:\sdk\tools fastboot flash boot boot.img)
15. Now reboot and thats it ur done!!!!
NO WIFI!!!! NO BLUETOOTH IN THE SUPER HERO ROM AM TRYING OTHER ROMS... I THINK THIS METHORD SHOULD WORK AN ALL ROMS NOW... maybe not....
after trying for a while only superhero works not the hero by haykuro... dunno why it keeps restarting at the htc splash screen....
waiting nice
Thanks for using my recovery! lol
reply: like i said in the begenning thnx to all tht helped....
ps the daldroid should work as well
good job man, very interested in this but gotta wait till wifi works.
i think wifi dosent work becase superhero was for dream not magic... but the ui is sweet!
can someone help to enable wifi and bluetooth??
Oh wow, thanks. I will shortly follow your instructions.
lol to fix wifi find out whos boot.img you stole rolleyes and take the wlan.ko from /system/lib/modules and throw it over the one in the build.
sign, package, fly.
EDIT:
also, in default.prop (within the boot.img) change it ro.secure to 0 if you want rooted adb shell
Code:
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.service.adb.enable=1
heh.. this is why sometimes you should wait before just throwing an incomplete build out
haykuro said:
lol to fix wifi find out whos boot.img you stole rolleyes and take the wlan.ko from /system/lib/modules and throw it over the one in the build.
sign, package, fly.
EDIT:
also, in default.prop (within the boot.img) change it ro.secure to 0 if you want rooted adb shell
Code:
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.service.adb.enable=1
heh.. this is why sometimes you should wait before just throwing an incomplete build out
Click to expand...
Click to collapse
That is exactly why I am waiting for a proper release to come out.......hint
LOL
it was the boot image i backed up myself... so what do i do exactly??? I kinda got the first part, used adb pull and push to copy over the file, but the edit just flew way oover my head.....
ps haykuro can you use this to make a biuld?? alsoo can u pls show me how to sign a package searched everywhere couldnt find out how...
re: TRIED THE wlan.ko file transfer still it says failed to start wlan!!!
Killadude said:
reply: like i said in the begenning thnx to all tht helped....
ps the daldroid should work as well
Click to expand...
Click to collapse
Yes, it works. Since June 8th ;-)
But daldroid-recovery is really a quick-mod of haykuro's one, so thank him (and others, I only mentioned him and a few others in a readme file in the ramdisk image)
I'm happy to see that someone else started releasing roms for pvt 32A board, because I was really busy and used all of my sparetime to try to rebuild a working kernel (Hero is running on my phone since 3 weeks, untested-bluetooth-fix, wlan fix, but still no working kernel, no iptables, so no release).
Going abroad for a few days, I'm sure I'll come back and be able to download your (or Haykuro's) new rom with a new built-from-sources-working-kernel for pvt32A ;-)
Greetings
Daldroid
Killadude said:
it was the boot image i backed up myself... so what do i do exactly??? I kinda got the first part but the edit just flew way oover my head.....
ps haykuro can you use this to make a biuld??
Click to expand...
Click to collapse
Im pretty sure he has
http://www.getyourdroidon.com/root/hero-sapphire-signed.zip
or did you mean a rogers specific one?
- Wifi and BT cannot start in this rom
yup one specific for rogers cuz our is the only goddam magic that couldnt until today be rooted!!
I just followed your instructions for the superherov2 rom and I ran into some problems.
I cannot upload the boot.img
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now my phone is stuck with the Rogers logo. Any ideas on how about I can go on fixing this problem.
First u could try in fastboot mode re booting to the recovery img boot..... once in there wait for a minute, connect usb to computer and in cmd go to tools folder and type
adb devices, if u see a serial underneath then type
adb push boot.img /data/local/boot.img
with the image you downloaded if this fails then, ill redriect u to a link Thanks to daldroid itll help you run the origanal magic rom, without the rogers crap installed on it. Just not you have to set the api settings in the menu to:
name: rogers
address: internet.com
to acess the rogers edge/3g internet.
http://www.arbitraryuser.com/blog/2...-south-africa-to-get-android-market-and-more/
just skip to instruction number 8 in the step by step instructions
PS IF U DID DO A NANDROID BACKUP JUST PLACE THE BOOT.IMG & SYSTEM.IMG THAT WERE BACKED UP INTO THE TOOLS FOLDER AND TYPE IN CMD
FASTBOOT FLASH BOOT BOOT.IMG
FASTBOOT FLASH SYSTEM SYSTEM.IMG
I had to do that many a times because most of the roms failed to install...
tell me if any of that helps...
PS thanks for the test i have now changed the instructions on the main page..
Killadude said:
First u could try in fastboot mode re booting to the recovery img boot..... once in there wait for a minute, connect usb to computer and in cmd go to tools folder and type
adb devices, if u see a serial underneath then type
adb push boot.img /data/local/boot.img
with the image you downloaded if this fails then, ill redriect u to a link Thanks to daldroid itll help you run the origanal magic rom, without the rogers crap installed on it. Just not you have to set the api settings in the menu to:
name: rogers
address: internet.com
to acess the rogers edge/3g internet.
http://www.arbitraryuser.com/blog/2...-south-africa-to-get-android-market-and-more/
just skip to instruction number 8 in the step by step instructions
PS IF U DID DO A NANDROID BACKUP JUST PLACE THE BOOT.IMG & SYSTEM.IMG THAT WERE BACKED UP INTO THE TOOLS FOLDER AND TYPE IN CMD
FASTBOOT FLASH BOOT BOOT.IMG
FASTBOOT FLASH SYSTEM SYSTEM.IMG
I had to do that many a times because most of the roms failed to install...
tell me if any of that helps...
PS thanks for the test i have now changed the instructions on the main page..
Click to expand...
Click to collapse
OK, if I try to use adb, it gives me an error stating that the device cannot be found.
I tried using my own boot.img, but I got the same error. Any ideas?
hotweiss said:
OK, if I try to use adb, it gives me an error stating that the device cannot be found.
I tried using my own boot.img, but I got the same error. Any ideas?
Click to expand...
Click to collapse
When you are in fastboot mode, "adb devices" won't show it. I THINK he meant "fastboot devices". It should show your devices in fastboot mode
OK, I used Ubuntu to fastboot my boot.img and that has now worked. I have one question now, how do you enter your Rogers data information. The ROM doesn't make a data connection with Rogers.
hotweiss said:
OK, I used Ubuntu to fastboot my boot.img and that has now worked. I have one question now, how do you enter your Rogers data information. The ROM doesn't make a data connection with Rogers.
Click to expand...
Click to collapse
Settings -> Wireless Controls -> Mobile networks -> Access Point Names
EDIT: read the NEXT post for the correct settings to put into the fields
I've tried using ROM manager and booting back into recovery mode but it stalls at the Google unlock screen. I've also tried installing the stock version of 2.3.2 version from Rom manager but got the same results.
I've also flashed the clockworkMod recovery to 3.0.0.5 then rebooted into Bootloader where i selected the "Recovery" option but again I only reach the Google unlock icon screen. It's been sitting at that screen for the past 20mins. Only way past it is to boot normally (after i reinsert the battery).
I have tried restoring from a previous backup but that too fails because it cant reach the recovery portion of the process after rebooting.
About Phone
Version: 2.3.2
Baseband Version: I9020XXJK8
Kernel Version: 2.6.35.7-g81433b [[email protected]#1]
CPU INFO: ARMv7 Processor Rev 2 (v7l)
Mod Version: CyanogenMod-7-02102011-NIGHTLY-NS
Build #: GRH78C
Click to expand...
Click to collapse
any help is greatly appreciated.
reflash recovery
thejron said:
reflash recovery
Click to expand...
Click to collapse
try reflashing the recovery from within the bootloader with "fastboot flash recovery recovery.img" or something like that. you should find something about this here on XDA i think.
floomat said:
try reflashing the recovery from within the bootloader with "fastboot flash recovery recovery.img" or something like that. you should find something about this here on XDA i think.
Click to expand...
Click to collapse
thx. i'll try that now.
thx for the reply, this page worked:
http://forum.xda-developers.com/sho...ighlight=fastboot+flash+recovery+recovery.img
i was able to update the ROM to 2.3.3, while in recovery mode. I rebooted the device but now when i go to Reboot>Recovery it still hangs at the google unlock screen. I think the only way for me to successfully access the recovery screen would be to connect my phone to the pc and run the fastboot boot-recovery-clockwork-3.0.0.5-crespo.img file.
headsh0tshurt said:
I think the only way for me to successfully access the recovery screen would be to connect my phone to the pc and run the fastboot boot-recovery-clockwork-3.0.0.5-crespo.img file.
Click to expand...
Click to collapse
What's happening is that Android is overwriting your custom recovery whenever it reboots.
To fix it, you first have to go back to the stock rom. Then, using either root explorer or adb, you have to rename /etc/install-recovery.sh
That way, when you flash your custom recovery, it doesn't rewrite the stock one when you reboot.
Check out this link:
http://forum.xda-developers.com/showthread.php?t=740748
edit: Also, in case someone else reads your post about using fastboot to get into recovery... the command is actually: "fastboot boot recovery-clockwork-3.0.0.5-crespo.img"
Note the space, not hyphen, between boot and the recovery image
Edit2: Ugh, the link I gave is pretty unclear (very shoddy google work). Anyway, the idea in the link is right, the command to remount your system in adb is:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
The full list of commands would be:
adb shell
su [you have to allow root access on your phone at this point - superuser will give you a popup]
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /
cd etc
mv ./install-recovery.sh ./install-recovery.sh.old
kaimyn said:
What's happening is that Android is overwriting your custom recovery whenever it reboots.
To fix it, you first have to go back to the stock rom. Then, using either root explorer or adb, you have to rename /etc/install-recovery.sh
That way, when you flash your custom recovery, it doesn't rewrite the stock one when you reboot.
Check out this link:
http://forum.xda-developers.com/showthread.php?t=740748
edit: Also, in case someone else reads your post about using fastboot to get into recovery... the command is actually: "fastboot boot recovery-clockwork-3.0.0.5-crespo.img"
Note the space, not hyphen, between boot and the recovery image
Edit2: Ugh, the link I gave is pretty unclear (very shoddy google work). Anyway, the idea in the link is right, the command to remount your system in adb is:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
The full list of commands would be:
adb shell
su [you have to allow root access on your phone at this point - superuser will give you a popup]
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /
cd etc
mv ./install-recovery.sh ./install-recovery.sh.old
Click to expand...
Click to collapse
i ran adb shell and entered the commands listed above. Below is a screenshot of what was entered.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now after I entered the mv ./install-recovery.sh ./install-recovery.sh.old
command it says that i can't rename the .install-recovery.sh because it doesn't exist. do i have to manually create a folder on the root with this name?
Did you go back to stock first? I think the files get deleted on a new rom, but for some reason you still have to rename the files while in stock. I had the same issue the first time I went to a custom rom.
I'm about to head to bed (asia) but I'll double check the directory in the morning.
You should also be able to Google the answer... I may have told you the wrong directory for the file. Look for something along the lines of android mount install-recovery.sh
Sent from my Nexus S using XDA App
No i didn't go back to stock prior to running the earlier cmd lines.
while in USB Debug mode, i transferred over the GRI40-2.3.3-rooted.zip into the phones' clockworkmod/backup folder. i then rebooted it into the bootloader and:
ran fastboot boot recovery-clockwork-3.0.0.5-crespo.img
Click to expand...
Click to collapse
I then chose the Backup & Restore option and selected to Restore the GRI40-2.3.3-rooted.
Once it was done i then selected reboot, it powered back on with full stock image. i rebooted it once more to confirm it had the stock image of 2.3.3. then from the bootloader screen i selected the recovery option and it took me to the screen with the android icon and the exclamation mark above it.
headsh0tshurt said:
No i didn't go back to stock prior to running the earlier cmd lines.
while in USB Debug mode, i transferred over the GRI40-2.3.3-rooted.zip into the phones' clockworkmod/backup folder. i then rebooted it into the bootloader and:
I then chose the Backup & Restore option and selected to Restore the GRI40-2.3.3-rooted.
Once it was done i then selected reboot, it powered back on with full stock image. i rebooted it once more to confirm it had the stock image of 2.3.3. then from the bootloader screen i selected the recovery option and it took me to the screen with the android icon and the exclamation mark above it.
Click to expand...
Click to collapse
So now if you delete or rename install-recovery.sh you should be good. For future reference
Code:
fastboot boot
Doesn't flash anything so you're literally just booting into an image so no matter what you wouldn't boot back into that image without the command again. If you want to flash a new recovery without using ROM Manager you can use the following command:
Code:
fastboot flash recovery recovery-clockworkmod-crespo-3.0.0.5.img
kenvan19 said:
So now if you delete or rename install-recovery.sh you should be good. For future reference
Click to expand...
Click to collapse
Okay I was not able to locate the file "install-recovery.sh" file on the SD, so from bootloader, I ran the code:
Code:
fastboot flash recovery recovery-clockworkmod-crespo-3.0.0.5.img
and went into recovery mode where i ran the latest nightly (cm_crespo_full-12.zip) and rebooted it more than once and each time it gets stuck @ the cyanogen mod7 boot screen....progress :/
headsh0tshurt said:
Okay I was not able to locate the file "install-recovery.sh" file on the SD, so from bootloader, I ran the code:
Code:
fastboot flash recovery recovery-clockworkmod-crespo-3.0.0.5.img
and went into recovery mode where i ran the latest nightly (cm_crespo_full-12.zip) and rebooted it more than once and each time it gets stuck @ the cyanogen mod7 boot screen....progress :/
Click to expand...
Click to collapse
interesting...Firstly because I wasn't paying close enough attention and mistyped the command (it should be fastboot flash recovery recovery-clockwork-crespo-3.0.0.5 not fastboot flash recovery recovery-clockworkmod-crespo-3.0.0.5) and it worked nonetheless.
There is a reason, however, you most likely weren't able to find the file etc/install-recovery.sh and that is because it isn't on the SD card. Unless you're using Root Explorer (paid app on the market, link here: https://market.android.com/details?id=com.speedsoftware.rootexplorer&feature=search_result) you're not going to see it.
Suggest you try the instructions at the bottom of this page > http://jaxov.com/2011/02/how-to-root-android-2-3-3-gingerbread-on-nexus-s/
7-step process that will help you go to CMR instead of stock recovery. Worked perfectly for me.
kenvan19 said:
interesting...Firstly because I wasn't paying close enough attention and mistyped the command (it should be fastboot flash recovery recovery-clockwork-crespo-3.0.0.5 not fastboot flash recovery recovery-clockworkmod-crespo-3.0.0.5) and it worked nonetheless.
There is a reason, however, you most likely weren't able to find the file etc/install-recovery.sh and that is because it isn't on the SD card. Unless you're using Root Explorer (paid app on the market, link here: https://market.android.com/details?id=com.speedsoftware.rootexplorer&feature=search_result) you're not going to see it.
Click to expand...
Click to collapse
yeah i copy/pasted what you wrote in my response but in actuality i wrote the correct file name into the the CMD and it went through. IF/when i get past the CM7 boot screen i'll look into the root explorer app. thx for the assist
kenvan19 said:
interesting...Firstly because I wasn't paying close enough attention and mistyped the command (it should be fastboot flash recovery recovery-clockwork-crespo-3.0.0.5 not fastboot flash recovery recovery-clockworkmod-crespo-3.0.0.5) and it worked nonetheless.
There is a reason, however, you most likely weren't able to find the file etc/install-recovery.sh and that is because it isn't on the SD card. Unless you're using Root Explorer (paid app on the market, link here: https://market.android.com/details?id=com.speedsoftware.rootexplorer&feature=search_result) you're not going to see it.
Click to expand...
Click to collapse
.cruiser said:
Suggest you try the instructions at the bottom of this page > http://jaxov.com/2011/02/how-to-root-android-2-3-3-gingerbread-on-nexus-s/
7-step process that will help you go to CMR instead of stock recovery. Worked perfectly for me.
Click to expand...
Click to collapse
Thanks for the link. I went through the instructions and the results were the same. the end of the instructions mentions to get the Root explorer on the phone but that doesnt work b/c i cant bypass the CM7 boot screen. so i just restored it to GRI40-2.3.3-rooted.zip via the clockwork recovery
The install-recovery.sh file is missing in CM7 - you have to do this process from a stock rom.
Personally, this is exactly how I did it. You may try it this way if you like... you should have instructions for all the individual pieces.
1. Go back to stock 2.3.2
2. Get the OTA update to 2.3.3
3. Unlock your bootloader
4. Using the fastboot boot recovery method, install SU
5. Boot in to Android and then rename install-recovery.sh
6. Install rom manager
7. Flash CWM 3.0.0.5
Good luck! Who knows, maybe you have to have an unlocked bootloader to get CWM to stick.
kaimyn said:
The install-recovery.sh file is missing in CM7 - you have to do this process from a stock rom.
Personally, this is exactly how I did it. You may try it this way if you like... you should have instructions for all the individual pieces.
1. Go back to stock 2.3.2
2. Get the OTA update to 2.3.3
3. Unlock your bootloader
4. Using the fastboot boot recovery method, install SU
5. Boot in to Android and then rename install-recovery.sh
6. Install rom manager
7. Flash CWM 3.0.0.5
Good luck! Who knows, maybe you have to have an unlocked bootloader to get CWM to stick.
Click to expand...
Click to collapse
my impatience got the best of me. after restoring it to the stock 2.3.3. i just reinstalled all the applications. none of my downloaded files (music/wallpapers) were lost.
[sarcasm]just have to go through the joy of reorganizing each screen [/sarcasm]. Mostly i am pisssed that i'd have to start from scratch in Angry birds .
This happened to me with gingercollab. I did fastboot flash then booted straight to recovery and installed cm7. Everything was working fine until I restored my nandroid of gingercollab by mistake.
Sent from my Nexus S using XDA Premium App
the issue was never resolved. and i get the system update for 2.3.4 about twice a week and i cant install it b/c after it restarts it bombs out at the android icon w/ the excalamtion mark.
i've tried the factory wipe/reset thinking that would start me off clean but that didnt work.
Unless you RENAME the stock recovery it WILL NEVER STICK. Unlocked bootloader or not. I just reflash recovery from fastboot if/when I need it.
Sent from a bird cage, with a swing!
Liberty still has something no other device has - ARIA!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
..........
Downloads:
cwm-5.0.2.3-liberty-agse.zip AGSE (ARIA) Edition - with cap key lights enabled
cwm-5.0.2.3-liberty.zip Stock Clockworkmod 5.0.2.3 - with cap key lights enabled
attn1 said:
Liberty still has something no other device has - ARIA!
Download: cwm-5.0.2.3-liberty-agse.zip
Click to expand...
Click to collapse
and apparently , interesting background images
*****
I am still on v2.5.0.1 - and help on how to install this img?
Thanks so much attn1!
Edit: found this for instructions, would this do?.....
HTML:
http://forum.xda-developers.com/showthread.php?t=1122694
here's 2 ways to do it:
if you have s-off:
boot phone into fastboot mode
hook phone to computer with usb cable
ON COMPUTER:
unzip cwm-5.0.2.3-liberty-agse.zip
command prompt
fastboot flash recovery cwm-5.0.2.3-liberty-agse.img
without s-off: (this is what I did, didn't have a USB cable handy)
terminal emulator
su
cd /sdcard/download
unzip cwm-5.0.2.3-liberty-agse.zip
flash_image recovery cwm-5.0.2.3-liberty-agse.img
tommyguns818 said:
Thanks so much attn1!
Edit: found this for instructions, would this do?.....
HTML:
http://forum.xda-developers.com/showthread.php?t=1122694
Click to expand...
Click to collapse
yep, if you are s-off with Revolutionary or AlpharevX.
Nutshell69 said:
and apparently , interesting background images
Click to expand...
Click to collapse
that's Aria herself.
Looking forward to the HTC Jenna
Sent from my Liberty using XDA App
i was wondering.....i've got s-off but no computer around me at the moment. is there a way to install this through the terminal app? I see sObe did it via terminal way but im not sure if he's s-off or not.
EDIT: I went for it and did it through terminal just like sObe and I have s-off. Worked like a charm. Thanks guys!!!
When I chose internal card I get
E:Can't mount /emc/
???
s0be said:
here's 2 ways to do it:
without s-off: (this is what I did, didn't have a USB cable handy)
terminal emulator
su
cd /sdcard/download
unzip cwm-5.0.2.3-liberty-agse.zip
flash_image recovery cwm-5.0.2.3-liberty-agse.img
Click to expand...
Click to collapse
tried this twice still failing :S
do i need to be running a certain rom?
I get through su just fine, i cd to the /sdcard/download (where my img is)
type in the flash_image .....
getting sh: flash_image: command not found
so looks like the terminal emulator isnt getting the PATH correctly
echo $PATH returns
/data/local/bin:/sbin:/system/sbin:/system/bin:/system/xbin
ug.
If your doing it through terminal, you need to make sure that your doing it exactly as shown in s0bes post. Also make sure that you have your new cwm 5.0.2.3 download in the download folder on your sd card.
Nutshell69 said:
tried this twice still failing :S
do i need to be running a certain rom?
I get through su just fine, i cd to the /sdcard/download (where my img is)
type in the flash_image .....
getting sh: flash_image: command not found
so looks like the terminal emulator isnt getting the PATH correctly
echo $PATH returns
/data/local/bin:/sbin:/system/sbin:/system/bin:/system/xbin
ug.
Click to expand...
Click to collapse
probably any aosp or cm based rom would work. the stock cleaned up roms, not so much.
Aside from the background thing, what advantages does this recovery have over 2.5.1.7? Is it faster? are the backups compatible?
T
s0be said:
probably any aosp or cm based rom would work. the stock cleaned up roms, not so much.
Click to expand...
Click to collapse
yea - i think thats the problem - not running a cm rom - will install 209 and try
thanks
***EDIT***
Installed CM 211 ROM
did these steps
terminal emulator
su
cd /sdcard/download
unzip cwm-5.0.2.3-liberty-agse.zip
flash_image recovery cwm-5.0.2.3-liberty-agse.img
getting errors :
mtd: erase failure at 0x00000000 (I/O error)
.......
thoughts?
Also curious of the benifit vs backward or forward compatibility gotchas. Anyone?
Edit. Tried to instal and get the same errors as above. S-on
Sent from my Liberty using XDA App
Nutshell69 said:
yea - i think thats the problem - not running a cm rom - will install 209 and try
thanks
***EDIT***
Installed CM 211 ROM
did these steps
terminal emulator
su
cd /sdcard/download
unzip cwm-5.0.2.3-liberty-agse.zip
flash_image recovery cwm-5.0.2.3-liberty-agse.img
getting errors :
mtd: erase failure at 0x00000000 (I/O error)
.......
thoughts?
Click to expand...
Click to collapse
Perhaps you can't flash a recovery from the rom without s-off? I'm not an expert to say that's the case... If so, you have to go through the whole unroot and re-flash procedure, which I forgot the steps to LONG ago. You might try rebooting into recovery, and using adb shell to do those steps. If you don't have ADB available, this may be beyond an easy upgrade.
I know of no advantages of this recovery over 2.5, btw.
SoCalHTCFuze said:
Also curious of the benifit vs backward or forward compatibility gotchas. Anyone?
Edit. Tried to instal and get the same errors as above. S-on
Sent from my Liberty using XDA App
Click to expand...
Click to collapse
s0be said:
Perhaps you can't flash a recovery from the rom without s-off? I'm not an expert to say that's the case... If so, you have to go through the whole unroot and re-flash procedure, which I forgot the steps to LONG ago. You might try rebooting into recovery, and using adb shell to do those steps. If you don't have ADB available, this may be beyond an easy upgrade.
I know of no advantages of this recovery over 2.5, btw.
Click to expand...
Click to collapse
In fact, you cannot flash a recovery without S-OFF, unless you use the original unrevoked tool and select custom recovery (the original unrevoked only managed to install a custom recovery which was good enough at the time).
The whole point of S-OFF is that you can flash the system partition. Like Gene said, if you don't have S-OFF, you'd need to unroot and use unrevoked again.
If you do have S-OFF, it's easy:
(OS X)
md5 /path/to/cwm-5.0.2.3-liberty-agse.img (confirm md5 sum)
./adb devices (confirm you're connected)
./adb reboot bootloader
./fastboot-mac devices
./fastboot-mac flash recovery /path/to/cwm-5.0.2.3-liberty-agse.img
./fastboot-mac reboot
./adb reboot recovery (wait to hit enter until the boot animation starts)
I haven't used it yet but I hear the backups are faster in 5.x
^^^ 5.0.2.3 is a little faster. I saw the new option to fix permissions in the recovery and tried it. Man it took like 30 min to run and chewed about 60 percent of battery. From now on I'll just use ROM manager. It never failed me and is way quicker. On further note....I like it. Go miss aria!
s0be said:
If so, you have to go through the whole unroot and re-flash procedure, which I forgot the steps to LONG ago.
Click to expand...
Click to collapse
Just so people in this situation are aware, you do not have to "unroot" your phone first. Just run Unrevoked a second time on your device and it will overwrite the recovery with the one you select.
drumist said:
Just so people in this situation are aware, you do not have to "unroot" your phone first. Just run Unrevoked a second time on your device and it will overwrite the recovery with the one you select.
Click to expand...
Click to collapse
egads - got this error
Error: failed to get root. Is your firmware too new?
Ok so i got a zte quest 5 (z3351s) though qlink. Not the phone i wanted but it was one i could afford. And it works very well just can't run amazon music and other apps at the same time.
But the bloatware is unreal. Used to in my galaxy s3&s4 days i could root and delete all apps i didn't need. I know i can disable them but i want them gone completely.
Majisk didnt work
Kingoroot same even used pc.
I am hoping someone knows of a way i can root this phone or at least delete all the un needed apps for example i have Google maps go (came stock) i put the org google maps which is better plus offers sat view.
Edit i did some math and converting and the useless apps 11 out of 58 come out to 349.72mb which is a lot if your phone only has 16gb of space. Also note i don't have hardly anything.
Worst case i can Hotspot to my note10+ for multitasking but not sure of data limit.
@TexasPride
a phone's Android can get considered "rooted" as soon as in Android the SU-binary is present. Hence you at any time at your own can install the appropriate SU-binary onto your phone's Android by means of ADB.
I heard about adb methods but i haven't messed with it in forever since apk/ios apps came out
jwoegerbauer said:
@TexasPride
a phone's Android can get considered "rooted" as soon as in Android the SU-binary is present. Hence you at any time at your own can install the appropriate SU-binary onto your phone's Android by means of ADB.
Click to expand...
Click to collapse
Are you sure it will always work?
I tried this method of installing supersu: https://github.com/spff/install-supersu-via-adb
As a result, I got my phone eternally showing the boot logo and not booting.
Not a problem to re-flash stock ROM but it is an example that there in no universal way to install SU (or SuperSU) via adb.
If you could give a link to some other method how SU could be installed, I'll give it a try of course.
vp1117 said:
Are you sure it will always work?
I tried this method of installing supersu: https://github.com/spff/install-supersu-via-adb
As a result, I got my phone eternally showing the boot logo and not booting.
Not a problem to re-flash stock ROM but it is an example that there in no universal way to install SU (or SuperSU) via adb.
If you could give a link to some other method how SU could be installed, I'll give it a try of course.
Click to expand...
Click to collapse
I spoke of SU-binary and NOT of SuperSU installer package
Example:
Code:
adb devices
adb push <location-of-matching-su-binary-on-computer> /sdcard/Downloads/ 2>nul
adb shell "chmod 0777 /sdcard/Downloads/su"
Of course you can install SuperSU package by means of ADB and this even when device is booted into Stock Recovery: but this requires to make some mods to SuperSU zip.
TexasPride, sorry I stepped in your thread.
jwoegerbauer said:
I spoke of SU-binary and NOT of SuperSU installer package
Click to expand...
Click to collapse
I see. It is often mixed in numerous materials one can find in the net. Subject is SU-binary update, but the ultimate goal is to install supersu.
jwoegerbauer said:
Example:
Code:
adb devices
adb push <location-of-matching-su-binary-on-computer> /sdcard/Downloads/ 2>nul
adb shell "chmod 0777 /sdcard/Downloads/su"
Click to expand...
Click to collapse
What should be result of running this code? SU-binary located in Downloads with 777 permission? What is the practical sense/use of it?
What software/application would use SU in that location?
Sorry for my questions. I'm not arguing. I try to understand the idea.
jwoegerbauer said:
Of course you can install SuperSU package by means of ADB and this even when device is booted into Stock Recovery: but this requires to make some mods to SuperSU zip.
Click to expand...
Click to collapse
Somehow, with my almost zero knowledge of edify and linux command line I got the same conclusion: SuperSU zip has to be modified in order to install it via adb on devices that do not have TWRP for sideload. I failed to find any examples of SuperSU modding...
@vp1117
Answering your questions from last to first:
Installing SuperSU.zip via ADB
The SuperSU.zip doesn't come with an EDIFY coded script, but with an Android SHELL script - everyone who has knowledge of LINUX scripting can read / modify it.
Android comes with TAR-binary, but not ZIP-binary. Hence the SuperSu.zip must get repacked into SuperSU.tar thus it can get extracted on Phone. The contents of such a TAR-file would look as shown here
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Making use of SU-binary
The SU-binary ( ~110KB ) is nothing else then the root user, as known from LINUX.
Running in Android via ADB a command that requires super-user ( root ) rights is done as follows
Example:
Code:
adb devices
adb shell "/sdard/Downloads/su -c '<ommand-that-requires-root-here>'"
jwoegerbauer said:
Answering your questions from last to first:
Installing SuperSU.zip via ADB
The SuperSU.zip doesn't come with an EDIFY coded script, but with an Android SHELL script - everyone who has knowledge of LINUX scripting can read / modify it.
Android comes with TAR-binary, but not ZIP-binary. Hence the SuperSu.zip must get repacked into SuperSU.tar thus it can get extracted on Phone. The contents of such a TAR-file would look as shown here
Click to expand...
Click to collapse
OK. I guess, I can repack zip to tar.
Sorry for my silly question but why should I need to keep superSU as an archive? Could not I just upload all folders + update-binary.sh to the phone? I'm sure I can do it.
Am I right my next step would be running update-binary.sh (~60 KB) from <adb shell> command line?
jwoegerbauer said:
Making use of SU-binary
The SU-binary ( ~110KB ) is nothing else then the root user, as known from LINUX.
Running in Android via ADB a command that requires super-user ( root ) rights is done as follows
Example:
Code:
adb devices
adb shell "/sdard/Downloads/su -c '<ommand-that-requires-root-here>'"
Click to expand...
Click to collapse
Interestingly, I can execute all commands I need without having su-binary (~100 KB) uploaded to my phone. It is strange but I see #-prompt after I ran <adb shell>. This happens on my UNrooted phone, running stock ROM. I guess, it's a specifics of my phone, no need to try explain it.
I done failed trying to read i dont really understand linux all that well. But if anyone has any links so i can download it and try it
vp1117 said:
Sorry for my silly question but why should I need to keep superSU as an archive? Could not I just upload all folders + update-binary.sh to the phone? I'm sure I can do it.
Am I right my next step would be running update-binary.sh (~60 KB) from <adb shell> command line?
Click to expand...
Click to collapse
Of course it's your decision how you transfer the SuperSU package onto phone: many ways lead to Rome.
My decision was to push SuperSU package repacked as TAR-file onto phone, extract it there, and finally run the modified update-binary.sh when phone is booted into recovery mode:
Code:
adb shell "$(cat < %supersu_dir%/update-binary.sh); echo $?"
So I rebooted to stock recovery and then uploaded following from UPDATE-SuperSU-v2.82-20170528234214.zip package to my phone's folder /tmp:
/arm64
/common
/META-INF
update-binary.sh
Here is what I got:
Z:\android\adb>adb shell "$(cat < /tmp/update-binary.sh); echo $?"
127
/system/bin/sh: #!/sbin/sh: not found
And here's what I got running same command from # command line:
# $(cat < /tmp/update-binary.sh); echo $?
/system/bin/sh: #!/sbin/sh: not found
127
In response to # ls -al /sbin I get lots of lines one of them is as follows:
lrwxrwxrwx 1 root root 7 1970-01-01 00:00 sh -> busybox
I feel that I'm doing something wrong, but what exactly?
In attached txt-file I put some more details I got in command line.
jwoegerbauer said:
... and finally run the modified update-binary.sh when phone is booted into recovery mode:
Click to expand...
Click to collapse
Am I right the only modification needed is to rename update-binary to update-binary.sh ?
@vp1117
NO.
When I said modified then I didn't mean simply rename it: The contents of original update-binary file must be rewritten / deleted in some parts. Also, believe me, it makes sense to repack original SuperSU.zip to SuperSu.tar as I demonstrated above. Take also note that, if device's Android isn't rooted yet, the location for unpacked SuperSU mandatory must be /data/local/tmp.
BTW:
I can see BusyBox is installed on your device's Android. Take note that BusyBox by default comes with the SU-binary. Hence your device's Android is rooted! Wondering why you waste your time with trying to completely install SuperSU from scratch?
jwoegerbauer said:
Wondering why you waste your time with trying to completely install SuperSU from scratch?
Click to expand...
Click to collapse
Good question.
Probably, because I see this when phone restarts from recovery to normal android:
jwoegerbauer said:
Also, believe me, it makes sense to repack original SuperSU.zip to SuperSu.tar as I demonstrated above.
Click to expand...
Click to collapse
OK, no problem, I can re-pack zip into tar.
However, what you demonstrated above was a screenshot showing update-binary.sh being inside the tar. At the same time you don't tell how update-binary.sh must be amended. Is it OK?
TexasPride
I'm very sorry I put so much spam in your thread. Please forgive me. If I knew how to delete my posts here I would deleted them.
vp1117 said:
TexasPride
I'm very sorry I put so much spam in your thread. Please forgive me. If I knew how to delete my posts here I would deleted them.
Click to expand...
Click to collapse
Its ok, i dont mind at all.
@TexasPride
FYI: I no longer participate this hijacked thread.