FORUMS
Remove All Ads from XDA

[ROOT] ROOT Status of Official Sprint 2.1 release RUU: YES! | 6/03

47 posts
Thanks Meter: 4
 
Post Reply Email Thread
ROOT Status of RUU_Hero_C_Sprint_2.27.651.5_R_signed_release : YES

Update: Regaw finally made it for us all! More info here http://forum.xda-developers.com/showthread.php?t=694572
================================================== ====

I noticed that someone has mixed up the TEST RUU and the RELEASE RUU. However they are different. The test RUU has su file built inside, other than the release RUU!

I flashed RUU_Hero_C_Sprint_2.27.651.5_R_signed_release.exe and i love it very much.
This update is very great, except that I lose my root access. And I tried every method to get root back again but failed.

1. Using asroot2 to root - Failed
I followed the Sticky GUIDE "How to Root the Sprint CDMA Hero", but failed when running
Code:
/data/local/asroot2 /system/bin/sh
The process was killed.
I know the linux kernel changed to 2.6.29 with the update. Maybe that is the reason why asroot2 does not work.

2. Using flashrec to flash a custom recovery image and then get root - Failed
I installed FlashRec 1.1.3 from zenthought's website, but failed when I tried backingup my recovery image.

3.Using adb to push the su file into the phone - Failed
I dump the su file from damageless's rom and flipz's Fresh 2.1.1 rom. Then using adb to push it into /data/local/ and chmod it to 4777, but running failed. It just said "Permission Denied". However, i push a busybox file into /data/local/ and chmod it to 4777, the busybox command runs ok.
KeithKris pointed that Su doesn't work on /data because that directory is mounted nosuid.

4.Using fastboot to flash a custom recovery image and then get root - Failed
I reboot my phone into fastboot, then connect it to PC using USB. I tried this command "fastboot boot recovery-RA-heroc-v1.6.2.img" but faild, it said "downloading 'boot.img'... FAILED (remote: not allow)".

5.Trying to flash back to RUU_Hero_C_Sprint_2.20.651.1_signed_test.exe - Failed
It said "Error 140: BOOTLOADER Version Error!".
Although regaw_leinad has pointed that the md5s on both(release version and test version) hboots are the EXACT same.
Quote:

b819083aa9fe456c5a5fbde4917980e2
and
b819083aa9fe456c5a5fbde4917980e2

Thanks regaw_leinad for your kind help.

Update: 6. the Volex method - Failed
this volex method is revealed here. Already tested by regaw that 2.1 patched it. It doesn't work.

================================================== ====

After all these failures, there seems to be at least two ways to get the root back. And regaw_leinad and other guys are working hard on them.

1. Try to make a new asroot2 to exploit the linux 2.6.29/android 2.1 on our cdma hero. Here is the source code of our asroot2 -- heroc 1.5 exploit tool.
2. Try to hack the RUU file (actually we mean the rom.zip in the RUU.exe) and make sure it will pass the Bootloader check and signature check(maybe md5?). Then we could flash a RUU with su built inside and get the root back.


If anyone knows something about how to pass the signature check(maybe md5?) or linux kernel exploit, please share your wisdom. Thank you.

This post will be updated every day until the way to root comes out.

Update: Thanks to the donators in this thread! I believe the devs will find the exploit method soon with your support!

================================================== ====

BTW: Never ever flash the official 2.1 release RUU.exe unless you know what you are doing. You won't get root access until the exploit method has been found. If you do love the official update, you may flash this damageless's rom dump from the official 2.1 release. And the radio dump from the official 2.1 release is here1 and here2 (thanks to damageless and flipz, and remember flashing radio at your own risk). The only difference between damageless's dump and official RUU's system part is that it has root and busybox and it removed some useless apks.
 
 
19th May 2010, 06:32 AM |#2  
Senior Member
Flag CA
Thanks Meter: 0
 
More
would it be more like fastboot boot /sdcard/recovery-RA-.........img?
19th May 2010, 08:05 AM |#3  
imleon's Avatar
OP Member
Thanks Meter: 4
 
Donate to Me
More
Quote:
Originally Posted by justinisyoung

would it be more like fastboot boot /sdcard/recovery-RA-.........img?

I tried /sdcard/recovery....img again, faild. Because in this command the image file should be on the PC not on the phone.
19th May 2010, 08:54 AM |#4  
Junior Member
Thanks Meter: 0
 
More
1. Make sure you have the Android SDK installed. Read HERE for more info.

2. Download 4shared.com - online file sharing and storage - download flash_image.zip

3. Download 4shared.com - online file sharing and storage - download recovery-RA-heroc-v1.5.2.img

4. Unzip the first file, and place both in your Android SDK/tools folder.

5. Make sure USB debugging is ON

6. Connect your phone to the PC

7. Open the command window and navigate to the Android-sdk/tools folder on your computer.

8. At the prompt enter the following, one line at a time followed by enter
Code:

adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
exit
exit
adb push flash_image /system/bin
adb push recovery-RA-heroc-v1.5.2.img /sdcard
adb shell
chmod 0755 /system/bin/flash_image
reboot

9. Your phone will reboot. When it is finished, back at your command window, once again enter
Code:

adb shell
su
cd /sdcard
flash_image recovery recovery-RA-heroc-v1.5.2.img
reboot recovery

10. With any luck, you'll have the recovery image back and can load custom 2.1 based ROMS again.
__________________
19th May 2010, 09:07 AM |#5  
imleon's Avatar
OP Member
Thanks Meter: 4
 
Donate to Me
More
Quote:
Originally Posted by elhead17

1. Make sure you have the Android SDK installed. Read HERE for more info.

2. Download 4shared.com - online file sharing and storage - download flash_image.zip

3. Download 4shared.com - online file sharing and storage - download recovery-RA-heroc-v1.5.2.img

4. Unzip the first file, and place both in your Android SDK/tools folder.

5. Make sure USB debugging is ON

6. Connect your phone to the PC

7. Open the command window and navigate to the Android-sdk/tools folder on your computer.

8. At the prompt enter the following, one line at a time followed by enter
Code:

adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
exit
exit
adb push flash_image /system/bin
adb push recovery-RA-heroc-v1.5.2.img /sdcard
adb shell
chmod 0755 /system/bin/flash_image
reboot

9. Your phone will reboot. When it is finished, back at your command window, once again enter
Code:

adb shell
su
cd /sdcard
flash_image recovery recovery-RA-heroc-v1.5.2.img
reboot recovery

10. With any luck, you'll have the recovery image back and can load custom 2.1 based ROMS again.
__________________

Sorry dude, there is NO su file in this released version of RUU.
So you won't run su after adb shell
19th May 2010, 10:11 AM |#6  
Senior Member
Thanks Meter: 11
 
More
just a question but can you successfully run the testkeys release RUU on your phone?
19th May 2010, 04:01 PM |#7  
Senior Member
NJ
Thanks Meter: 18
 
More
I thought with new 2.1 update root access was removed and there was no way workaround to get root access. I might be wrong here.
You might want to try RUU back to 1.56 version and try to gain ROOT access and just flash ROM release by the dev's here which still give us ROOT access.
I'm not sure if it even possible to go back from 2.1 to 1.5 RUU. Maybe some with more knowleadge of RUU can chip in here.

In addition the RUU you flash is same one release by Devs here on their modify ROMs.
19th May 2010, 04:14 PM |#8  
Senior Member
Florida
Thanks Meter: 12
 
More
i dont think it is possible to ruu back to 1.5. i think a dev said something about hboot being updated so it needs a new way for root.
19th May 2010, 04:28 PM |#9  
regaw_leinad's Avatar
Inactive Recognized Developer
Flag Seattle, WA
Thanks Meter: 3,805
 
More
Quote:
Originally Posted by kashb91

i dont think it is possible to ruu back to 1.5. i think a dev said something about hboot being updated so it needs a new way for root.

You are correct sir. There's no way to downgrade hboot (without root), just like why you can't run the 1.29 RUU if you ran the 1.56, or yours came with 1.56 on it.
19th May 2010, 06:02 PM |#10  
SupahDave's Avatar
Senior Member
Thanks Meter: 123
 
More
F.A.I.L.
10chars
19th May 2010, 06:07 PM |#11  
gunnyman's Avatar
Senior Member
Flag Greenville SC
Thanks Meter: 2,696
 
Donate to Me
More
aside from people who "accidentally" installed RUU, The push to quickly root this release is probably low priority, first of all this phone is probably end of life, so the chances of it coming out of the factory with 2.1 on it are slim.
2nd I imagine when the Evo gets released this forum will become a ghost town as far as new development is concerned
Post Reply Subscribe to Thread

Tags
hero, root 2.1

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes