Rooting the RUU 2.1 Sprint Leak - Hero CDMA Android Development

I am interesting in finding out how to root the RUU 2.1 Sprint Leak, I tried to root my 1.5 to install damagecontrol 2.06, but I had the newest patch and flashrek and other methods wouldn't root it.
Any Suggestions or Links to help me figure out how to load damagecontrol 2.06 rom and root the RUU 2.1 Sprint Leak.
Thanks so much
amdme127

I guess you missed the sticky at the top.
http://wiki.xda-developers.com/index.php?pagename=CDMA Hero Guides

Thanks so much I appreciate it

amdme127 said:
I am interesting in finding out how to root the RUU 2.1 Sprint Leak, I tried to root my 1.5 to install damagecontrol 2.06, but I had the newest patch and flashrek and other methods wouldn't root it.
Any Suggestions or Links to help me figure out how to load damagecontrol 2.06 rom and root the RUU 2.1 Sprint Leak.
Thanks so much
amdme127
Click to expand...
Click to collapse
Well, the leaked RUU comes with root. Are you trying to root your stock hero on 1.5 to be able to flash things?

regaw_leinad said:
Well, the leaked RUU comes with root. Are you trying to root your stock hero on 1.5 to be able to flash things?
Click to expand...
Click to collapse
Silly question prolly, but if it comes with root, why cant I get into recovery, by pushing home and power?

Roman G said:
Silly question prolly, but if it comes with root, why cant I get into recovery, by pushing home and power?
Click to expand...
Click to collapse
becuase when you used the ruu, it overwrote the custom recovery image with the stock test 2.1 recovery image.
You'll have to load the flash_image file on the phone and chmod it. Then flash the custom recovery again. I think I saw a guide somewhere in here.

Roman G said:
Silly question prolly, but if it comes with root, why cant I get into recovery, by pushing home and power?
Click to expand...
Click to collapse
If you run the .exe it rewrites the recovery.

Roman G said:
Silly question prolly, but if it comes with root, why cant I get into recovery, by pushing home and power?
Click to expand...
Click to collapse
Already answered

So is it true that you can gain root access through ADB!

danknee said:
If you run the .exe it rewrites the recovery.
Click to expand...
Click to collapse
not only the recovery, but the radio, bootloader, well, everything.
It's quite the long process to go back, don't know if anyone has tried it yet. Don't know if some of the things can go back a version.

Roman G said:
So is it true that you can gain root access through ADB!
Click to expand...
Click to collapse
Yeah, but, you don't have busybox installed, so you can't do really anything in adb shell.

regaw_leinad said:
not only the recovery, but the radio, bootloader, well, everything.
It's quite the long process to go back, don't know if anyone has tried it yet. Don't know if some of the things can go back a version.
Click to expand...
Click to collapse
I did it for the 2.10 radio and went back to flipz after.
Manually push flash_image to /system/bin >> You have to give flash_image permissions with adb
Code:
adb shell chmod 0755 /system/bin/flash_image
>> Root and reflash recovery (use this guide, except substitute 1.6.2 instead of 1.5.2 recovery (or use whatever recovery you want)>> Then reboot into recovery and nandroid back to your original build. You can even nandroid back to Fresh 2.0d and you will retain your new PRI.
If you have never made a backup, then download whatever ROM you want to try and use flash from .zip in recovery to flash the new ROM.
I included flash_image if you need it to push. This is not a .zip file, but I had to add .zip to attach it here. Rename it without the .zip or push it by typing
Code:
adb push flash_image.zip /system/bin/flash_image

danknee said:
I did it for the 2.10 radio and went back to flipz after.
Manually push flash_image to /system/bin >> You have to give flash_image permissions with adb
Code:
adb shell chmod 0755 /system/bin/flash_image
>> Root and reflash recovery (use this guide, except substitute 1.6.2 instead of 1.5.2 recovery (or use whatever recovery you want)>> Then reboot into recovery and nandroid back to your original build. You can even nandroid back to Fresh 2.0d and you will retain your new PRI.
If you have never made a backup, then download whatever ROM you want to try and use flash from .zip in recovery to flash the new ROM.
I included flash_image if you need it to push. This is not a .zip file, but I had to add .zip to attach it here. Rename it without the .zip or push it by typing
Code:
adb push flash_image.zip /system/bin/flash_image
Click to expand...
Click to collapse
oh yeah, i've seen that post all over like 3 times already. whoops. well has anyone else tried it?

regaw_leinad said:
oh yeah, i've seen that post all over like 3 times already. whoops. well has anyone else tried it?
Click to expand...
Click to collapse
SMW did, plus he posted a link on how to RUU back to 1.56 after doing it as well....without the RUU...lol.
The bootloader is modified, so you can't just RUU the old fashioned way.
smw6180 said:
If it doesn't work, try this post: http://forum.xda-developers.com/showpost.php?p=6013606
It's basically going to stock without using the RUU.
Click to expand...
Click to collapse

danknee said:
SMW did, plus he posted a link on how to RUU back to 1.56 after doing it as well.
Click to expand...
Click to collapse
cool thanks

http://forum.xda-developers.com/showthread.php?p=6142928#post6142928
I wrote up a tutorial on how to root any 1.5 based Hero using the Sprint 2.1 leaked test RUU. This might help.

Any ideas:
I have gone and tried a few tutorials on this site for putting on Amon's image and I always get a denied for the flash_image command when running in adb shell.
This is where I keep getting stopped at in all these tutorials.
Thanks for the help

amdme127 said:
Any ideas:
I have gone and tried a few tutorials on this site for putting on Amon's image and I always get a denied for the flash_image command when running in adb shell.
This is where I keep getting stopped at in all these tutorials.
Thanks for the help
Click to expand...
Click to collapse
he posted how to fix that right above you...
http://forum.xda-developers.com/showpost.php?p=6151388&postcount=12

Thanks so much, I missed that post, so thanks for pointing it out to me.
Putting DamageControl 2.06 rom right now, thanks so much for the help again

amdme127 said:
Thanks so much, I missed that post, so thanks for pointing it out to me.
Putting DamageControl 2.06 rom right now, thanks so much for the help again
Click to expand...
Click to collapse
No problem

Related

[ROM] Stock 2.1 Hero Update zip from RUU_Hero_C_Sprint_2.20.651.1_signed_test.exe

Since some people were interested I've made a stock update zip from the RUU_Hero_C_Sprint_2.20.651.1_signed_test.exe so you can flash via recovery.
This is just for those who want a completely stock rom to work off of or those that can't or don't want to run the RUU. If you want something already tweaked then use DamageControl. I'm not trying to start a custom rom I just did this for a couple people that wanted it.
It does not include the new hboot or radio.img included in the RUU and the system is stock except for adding busybox, patched su and sh.
To use su you need to install Superuser.apk.
Busybox is not installed by default you can do that through a terminal app or adb executing su and running "busybox --install /system/xbin".
You must be rooted and flash via Amon_ra recovery. Recommend nandroid backup and wipe/factory reset before flashing.
Here is a link to my post on how to make an update zip from the RUU.
Download link for the update/rom:
http://dl.dropbox.com/u/6022412/zen-hero_0.1b.zip
The link might be down since dropbox just suspended my public links due to excessive traffic.
Alternate download:
http://www.4shared.com/file/YqMmKAzL/zen-hero_01b.html
This is a link to my google code site where i put up some of the binaries/scripts that I use for rom making. These are linux binaries. If you download them put them in your path so you can execute them from anywhere. Also make sure you chmod them to executable. If you don't know how the google can tell you.
http://code.google.com/p/zen-droid/downloads/list
Due to recent events I just want to say that the devs here put a lot of work into getting you guys these leaked roms. They risk their credibility and their sources risk their jobs. So have some respect and remember it's just a phone.
Thank you,I'm sure a lot of people were wanting this.
What is the point of making a zip when you can just use the RUU?
My RUU just got done booting!
Roman G said:
What is the point of making a zip when you can just use the RUU?
My RUU just got done booting!
Click to expand...
Click to collapse
For people not running windows and for people that don't want to risk flashing hboot or the radio.img.
See I did not know it came with the radio image!
Just booted up fine and got the new radio image and a knew PRI# and was able to update my PRL as well!
Zenulator: heh I'm working on a rom I titled Zendroid... wonder if people will confuse it as being something related to you.
obelisk79 said:
Zenulator: heh I'm working on a rom I titled Zendroid... wonder if people will confuse it as being something related to you.
Click to expand...
Click to collapse
crazy, his link says zendroid in it too
http://code.google.com/p/zen-droid/downloads/list
obelisk79 said:
Zenulator: heh I'm working on a rom I titled Zendroid... wonder if people will confuse it as being something related to you.
Click to expand...
Click to collapse
Yea I thought that was kind of funny. Nice name for a rom though
yeah well, I thought it had a nicer ring to it than fengshuidroid.... was going for a rom which was also centered around a nice clean theme to the sense ui. I'm still making headway on the project.
Re: [ROM] Stock 2.1 Hero Update.zip
Maybe this is a stupid question but, The phone needs to be rooted to install this rom?
Sent from my HERO200 using xda app
theclawpr said:
Maybe this is a stupid question but, The phone needs to be rooted to install this rom?
Sent from my HERO200 using xda app
Click to expand...
Click to collapse
yes you need root and a recovery image
Roman G said:
See I did not know it came with the radio image!
Just booted up fine and got the new radio image and a knew PRI# and was able to update my PRL as well!
Click to expand...
Click to collapse
Interesting! What is the new PRI that you have now?
raynda said:
Interesting! What is the new PRI that you have now?
Click to expand...
Click to collapse
2.10_003 I believe it's the one that damage had that no one could figure out where he got it other than the official release!
okay i have a question, i was trying to update the recovery image to the 1.6.2 . but i get an error ..
The img file is in the sd card and when i do flash_image recovery recovery-RA-heroc-v1.6.2.img i get flash_image not found error ...
i tired to go from scratch and do the factory 1.5 image (RUU) but now says can not start bootloader ...any ideas?
rgildoss said:
okay i have a question, i was trying to update the recovery image to the 1.6.2 . but i get an error ..
The img file is in the sd card and when i do flash_image recovery recovery-RA-heroc-v1.6.2.img i get flash_image not found error ...
i tired to go from scratch and do the factory 1.5 image (RUU) but now says can not start bootloader ...any ideas?
Click to expand...
Click to collapse
adb shell
cd /sdcard
flash_image recovery blah.blah.blah
smw6180 said:
adb shell
cd /sdcard
flash_image recovery blah.blah.blah
Click to expand...
Click to collapse
error
flash_image: not found
rgildoss said:
error
flash_image: not found
Click to expand...
Click to collapse
Thats because the flash images is not called blah.blah.blah
VinceOB said:
Thats because the flash images is not called blah.blah.blah
Click to expand...
Click to collapse
i know that ...lol
ever i try i can not load the damn recovery image ...
power + menu gives me a picture of the phone with ! .....
how can i load the recovery image ?
The phone is rooted but just wont take the revory image
Now this might be a stupid question, but do we need Root for this? I have a friend who's terrified of Rooting but really wants 2.1, so could he just Flash this through the Stock Recovery Image, or should I force him to Root?
Edit: NVM sorry I just read the 1st post on page 2. Told you it was a stupid question.
It seems like the flash_image command is missing.

Stock recovery

Is there a way to get back to stock recovery from RA without using the original RUU?
herzzreh said:
Is there a way to get back to stock recovery from RA without using the original RUU?
Click to expand...
Click to collapse
should be in the questions board.
yea, i havent done it but pretty sure my theory will work! not sure why you want to do this ...
you'll need some technical/advanced experience or an adventurous spirit to learn the commands! im gonna explain them here because you can use the search feature to find all sorts of explanations!
here are the steps (in my theory):
get a hold of the rom .zip from the .6 RUU. extract the recovery.img. put it on the sdcard
flash_image recovery /sdcard/recovery.img

ENG bootloader (0.76 needed for CM6) extended fastboot commands.

I took hboot 0.76.2000 from toast's root nand unlock part2 and put it in a new PC36IMG, so that those who installed unrevoked forever can get the extended fastboot commands back.
NOTE: This is only for unrevoked forever users.
Tested to work if flashed from hboot (bootloader)
Not tested in recovery.
NOTE 2: Make a nandroid backup.
Place file on root of sdcard, power off your phone, then power on your phone by holding volume+down and pressing+holding the power button until the white bootloader appears. Press volume up once asked to install the bootloader.
NOTE 3: For those experiencing being stuck in bootloader, you can boot into recovery, flash your current ROM again, (without data wiping) OR just restore a nandroid backup. Flashing a custom kernel will also get you out of the loop. I'm going to go ahead and assume flashing anything other than hboot iwll get you out of the loop.
This will NOT wipe your device, however, backing up is always recommended.
UPDATE: It appears as though everyone is getting stuck in bootloader after this procedure. You can get out of this by reflashing your current ROM (without wiping) and/or restore a nandroid backup. Some have reported errors when trying to restore a nandroid backup. YMMV
Karadorde has put together a package that works. Read his instructions below:
First and foremost it seems that if you get stuck in the Bootloader (no matter what method you are using) then your Nandroid backups are broken. I don't know that anyone has been able to successfully restore from one of those yet.
The file in the OP allows you to apply just the engineering HBOOT.img (hboot_0.76.2000.img) This works flawlessly for some but not so well for others.
The file in Post 71 and Post 91 allows you to apply a full PC36IMG.zip that contains the engineering HBOOT.img (hboot_0.76.2000.img) This is a fix for some who have gotten stuck in the Bootloader after using the file from the OP. At the same time this has also caused the some of the same issues people were having with getting stuck in the Bootloader from the OP. This file will not downgrade any part of your phone, however, it will wipe the phone. Also it is reported that it broke root on one phone. I believe this only happened to one person, need confirmation on if it happened to multiple.
If you get stuck in the Bootloader you can re-flash your Kernel to fix the issue. Not sure if this works with the stock Kernel or if you have to have a custom Kernel. Looking for feedback on this.
If you get stuck in the Bootloader reflash your current rom. Need feedback on this as well.
Link to Karadorde's updated package: http://www.freeza-inc.com/PC36IMG.zip
Here's the recovery flashable version that I made a while ago
Calkulin said:
Here's the recovery flashable version that I made a while ago
Click to expand...
Click to collapse
Nice. had no idea you made it
Guess I should have searched last night lol.
freeza said:
Nice. had no idea you made it
Guess I should have searched last night lol.
Click to expand...
Click to collapse
Well I made it but never posted it as there was no way of flashing it unless you had the ENG hboot to begin with
anyway of having 79.00 with the commands?
I'm sorry op but its surely going to be asked so might as get it out quickly lol
Exactly what commands are missing?
rjmjr69 said:
anyway of having 79.00 with the commands?
I'm sorry op but its surely going to be asked so might as get it out quickly lol
Exactly what commands are missing?
Click to expand...
Click to collapse
He's talking about the fastboot commands, the commands you run when you reboot your phone and set your as "fastboot". Here's some commands you've probably seen if you've tried flashing a custom kernel:
Code:
fastboot flash zimage zImage
fastboot reboot
pseudoremora said:
He's talking about the fastboot commands, the commands you run when you reboot your phone and set your as "fastboot". Here's some commands you've probably seen if you've tried flashing a custom kernel:
Code:
fastboot flash zimage zImage
fastboot reboot
Click to expand...
Click to collapse
Adding on to this, you probably only need fastboot commands if you're planning on doing some serious rom development.
sk63 said:
Adding on to this, you probably only need fastboot commands if you're planning on doing some serious rom development.
Click to expand...
Click to collapse
Thanks for answering
one slight thing I am confused on now with unrevoked forever available.
Is it possible to flash the ENG boot without changing the PRI ?
for example:
- stock 2.1 evo / 1.40 pri
- unrevoked 3 + unrevoked forever
- still on 1.40 pri
- flash ENG boot without 1.34 pri, leaving the 1.40 pri
?
I would like to know the same thing.
-frank
Sent from my PC36100 using XDA App
TeknoJnky said:
one slight thing I am confused on now with unrevoked forever available.
Is it possible to flash the ENG boot without changing the PRI ?
for example:
- stock 2.1 evo / 1.40 pri
- unrevoked 3 + unrevoked forever
- still on 1.40 pri
- flash ENG boot without 1.34 pri, leaving the 1.40 pri
?
Click to expand...
Click to collapse
kaediil said:
I would like to know the same thing.
-frank
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
yes, it is.
Can this be reversed? Do you have the 79.00 to flash back?
rjmjr69 said:
Can this be reversed? Do you have the 79.00 to flash back?
Click to expand...
Click to collapse
I can extract it from an official RUU.
freeza said:
I can extract it from an official RUU.
Click to expand...
Click to collapse
Ok but will the phone still be unlocked via unrevokedforever?
rjmjr69 said:
Ok but will the phone still be unlocked via unrevokedforever?
Click to expand...
Click to collapse
yes, it will.
freeza said:
yes, it will.
Click to expand...
Click to collapse
Cool I would like that very much please thanks sir
rjmjr69 said:
Cool I would like that very much please thanks sir
Click to expand...
Click to collapse
here you go.
freeza said:
here you go.
Click to expand...
Click to collapse
You seem in the know, so I'm asking you... I ran unrevoked forever, it said it was successful, but my HBOOT stayed as ENG HBOOT .76. Is that correct or did I screw up unrevoked somehow?
Thanks for this. I flashed the wrong damned pc36img.zip (thought I was flashing the one that had rooted 1.47) to get back to a sense rom from cm6 to do the pri hackery and had upgraded hboot.
Now that my pri's fixed I'd rather have S-OFF and the engineering hboot than sit here and reset my phone another 20ish times to get 1.40 pri back after re-flashing the engineering image!
freeza said:
here you go.
Click to expand...
Click to collapse
So this is the same file that it ends up with when you run unrevokedforever?
Does it say s-on or off?

Untouched stock froyo 2.2 Asia OTA ROM

This is an incremental rom for ASIA HTC aria, do not install it for another models!
http://rapidshare.com/files/4381358...hTC_Asia_TW_2.37.709.4-1.35.709.3_release.zip
just updated my wife's aria to froyo. lost all the custom recovery stuff but still.
Here is the official OTA zip from the phone.
you can flash it in clockwork recovery by toggling the signature setting (you will lose clockwork though, you have been warned)
also do anyone know how to get rid of the superuser 'ninja' icon once you flashed this?
enjoy
looks like I need root permission to remove that superuser thing, should have done that before upgrading...
If this contains the new hboot, I highly recommend not flashing it.
Edit: it does - do NOT flash this if you ever want root.
Bad idea.
attn1 said:
If this contains the new hboot, I highly recommend not flashing it.
Edit: it does - do NOT flash this if you ever want root.
Bad idea.
Click to expand...
Click to collapse
thanks for the heads-up attn1, maybe we can dissect this to find a workaround
attn1 said:
If this contains the new hboot, I highly recommend not flashing it.
Edit: it does - do NOT flash this if you ever want root.
Bad idea.
Click to expand...
Click to collapse
yes its un-modified from HTC. will just have to wait for a new root
one thing I dont quite get is how come this rom is so small (80MB) compare to all the other roms
Is it an incremental update or a full rom?
can anyone shed some light?
zyo said:
yes its un-modified from HTC. will just have to wait for a new root
Click to expand...
Click to collapse
Well until a new method is developed, it's beyond foolish to flash this incremental update over a rom it was never intended for.
zyo said:
one thing I dont quite get is how come this rom is so small (80MB) compare to all the other roms
Is it an incremental update or a full rom?
can anyone shed some light?
Click to expand...
Click to collapse
Yes, it's an incremental update to the Hong Kong ROM that should not be flashed over any other rom.
As OP, you can edit this thread with a warning - please. This is not a complete rom, and because it was not intended for the AT&T ROM or any other than the HK ROM, some of the patches may not be executed correctly. If you start to experience some funkiness, I can probably get your phone flashed to the Gratia leak ROM, but as of now there is no going back to stock.
attn1 said:
Well until a new method is developed, it's beyond foolish to flash this incremental update over a rom it was never intended for.
Yes, it's an incremental update to the Hong Kong ROM that should not be flashed over any other rom.
As OP, you can edit this thread with a warning - please. This is not a complete rom, and because it was not intended for the AT&T ROM or any other than the HK ROM, some of the patches may not be executed correctly. If you start to experience some funkiness, I can probably get your phone flashed to the Gratia leak ROM, but as of now there is no going back to stock.
Click to expand...
Click to collapse
Thats ok I am actually using an Asian model Aria (not ATT)
but if there is a way to get rid of that superuser icon will be nice (even if that means I have to go back to Gratia leaked first)
zyo said:
Thats ok I am actually using an Asian model Aria (not ATT)
but if there is a way to get rid of that superuser icon will be nice (even if that means I have to go back to Gratia leaked first)
Click to expand...
Click to collapse
if you have the HK phone, with a goldcard you could probably flash your original shipping RUU. It's on shipped-roms.com.
That should return the phone to stock, without superuser icons. Let me know what HBOOT you have on it at that point. In any event, after that you should be able to flash the ota again after that, going to a stock 2.2 HK setup. You won't have root, and you won't be able to do custom recovery.
Please let me know if you can downgrade that phone with the this RUU and a goldcard. You will need root access, so if SU does not work anymore, then you will need to use Visionary for temp root.
RUU: http://tinyurl.com/2g8fvs3
VISIONARY: http://www.mediafire.com/?xhwc5m7f273l7b2
Goldcard procedure below:
(procedure from BLAyo)
BlaY0 said:
Here are few easy steps on how to make Goldcard without taking it out of your phone but you have to be root (VISIONary temproot is fine).
You will be doing this from command prompt:
Code:
adb shell
su
First you need to find out sdcard's CID:
Code:
cat /sys/class/mmc_host/mmc0/mmc0:*/cid
...copy it into text box on http://hexrev.soaa.me/. Now go to http://psas.revskills.de/?q=goldcard and put in the reversed CID you have got on previous web page. Push goldcard.img to your phone via 2nd command prompt:
Code:
adb push goldcard.img /data/local/
...unmount sdcard via Settings, go back to 1st command prompt and make a backup then make goldcard:
Code:
dd if=/dev/block/mmcblk0 count=1 of=/data/local/sdcard_backup.img
cat /data/local/goldcard.img > /dev/block/mmcblk0
sync
exit
You may also pull that backup to your PC:
Code:
adb pull /data/local/sdcard_backup.img .
Click to expand...
Click to collapse
I think temproot alone is enough to remove that superuser icon? Just need the permission to remove that apk
zyo said:
I think temproot alone is enough to remove that superuser icon? Just need the permission to remove that apk
Click to expand...
Click to collapse
Yes, that should work. The long way may provide you with a full downgrade/root path.
someone in the forum I visit reported that he used Visionary to gain temp root, then downgraded the phone (by modifying misc partition, I guess) and installed 2.1 RUU. But HBOOT didn't be downgraded. Its version is still 1.0, can't be rooted.
attn1 said:
Yes, that should work. The long way may provide you with a full downgrade/root path.
Click to expand...
Click to collapse
hmm that visionary + you gave me didnt work
It went black screen and after 2mins force close
and before you ask yes usb debugging has been turned on,
I have tried in terminal with su, got permission denied
ok did manage to pass that black screen but terminal still shows permission denied and I didnt see that allow permission popup
help anyone?
zyo said:
ok did manage to pass that black screen but terminal still shows permission denied and I didnt see that allow permission popup
help anyone?
Click to expand...
Click to collapse
you have to be rooted to have su and the popup working... And I'm pretty sure you just de-rooted the phone, and installed an hboot that no one knows how to root yet.
Hopefully no one else does the same.
I used visionary which is suppose to grant me temporary su. check previous post please
attn1 said:
if you have the HK phone, with a goldcard you could probably flash your original shipping RUU. It's on shipped-roms.com.
That should return the phone to stock, without superuser icons. Let me know what HBOOT you have on it at that point. In any event, after that you should be able to flash the ota again after that, going to a stock 2.2 HK setup. You won't have root, and you won't be able to do custom recovery.
Please let me know if you can downgrade that phone with the this RUU and a goldcard. You will need root access, so if SU does not work anymore, then you will need to use Visionary for temp root.
RUU: http://tinyurl.com/2g8fvs3
VISIONARY: http://www.mediafire.com/?xhwc5m7f273l7b2
Goldcard procedure below:
(procedure from BLAyo)
Click to expand...
Click to collapse
Just a quick note here I manage to make a goldcard and flashed a hk 2.2 froyo rom onto it. you DO NOT need any root to make a gold card only adb
zyo said:
Just a quick note here I manage to make a goldcard and flashed a hk 2.2 froyo rom onto it. you DO NOT need any root to make a gold card only adb
Click to expand...
Click to collapse
How is it? Fast? Stable? Laggy like the Gratia ROM?

[Q] is there a way to unroot and lock the bootloader again ?

is there a way to unroot and lock the bootloader again ?
quattro_rs said:
is there a way to unroot and lock the bootloader again ?
Click to expand...
Click to collapse
Yes.
Several discussions about it already in here.
To relock the bootloader is as simple as "fastboot oem lock" command.
There's a couple of different ways to get the root out, they're all mentioned in the thread for it.
but as of now no way to flash the stock recovery
slowz3r said:
but as of now no way to flash the stock recovery
Click to expand...
Click to collapse
If you apply the 2.3.1 update, it reflashes the stock recovery on every normal boot, doesn't it?
I lost "permanent" CWM when I did the update and went back to stock. You can still get to CWM via ROM Mgr or fastboot flash.
distortedloop said:
If you apply the 2.3.1 update, it reflashes the stock recovery on every normal boot, doesn't it?
I lost "permanent" CWM when I did the update and went back to stock. You can still get to CWM via ROM Mgr or fastboot flash.
Click to expand...
Click to collapse
Some people had issues flashing 2.3.1 official using CWM.
2.3.1 is incremental so it doesnt include a full recovery
slowz3r said:
Some people had issues flashing 2.3.1 official using CWM.
2.3.1 is incremental so it doesnt include a full recovery
Click to expand...
Click to collapse
2.3.1 may not include a full recovery, but it includes patches to the boot image (boot.img.p & recovery-from-boot.p) and a script to install the patches on each boot if the recovery is not stock.
The script is /etc/install-recovery.sh and here's what it does:
Code:
#!/system/bin/sh
if ! applypatch -c MTD:recovery:2048:8fa462e56115c0bf8141c3879afc8966a2b1c7f0; then
log -t recovery "Installing new recovery image"
applypatch MTD:boot:2949120:ddf4dec1310bc3213cbcdee1f4915e86f045755b MTD:recovery 33b0a9d47b4c83c37d763affdebe5fa84e4f220d 3194880 ddf4dec1310bc3213cbcdee1f4915e86f045755b:/system/recovery-from-boot.p
else
log -t recovery "Recovery image already installed"
fi
can someone explain how to do it step by step im new at this ?
ok i managed to lock the bootloader but im still not sure how to unroot the device !
distortedloop said:
2.3.1 may not include a full recovery, but it includes patches to the boot image (boot.img.p & recovery-from-boot.p) and a script to install the patches on each boot if the recovery is not stock.
The script is /etc/install-recovery.sh and here's what it does:
Code:
#!/system/bin/sh
if ! applypatch -c MTD:recovery:2048:8fa462e56115c0bf8141c3879afc8966a2b1c7f0; then
log -t recovery "Installing new recovery image"
applypatch MTD:boot:2949120:ddf4dec1310bc3213cbcdee1f4915e86f045755b MTD:recovery 33b0a9d47b4c83c37d763affdebe5fa84e4f220d 3194880 ddf4dec1310bc3213cbcdee1f4915e86f045755b:/system/recovery-from-boot.p
else
log -t recovery "Recovery image already installed"
fi
Click to expand...
Click to collapse
Oh, alright
google hasnt released a full OS for flashing have they?
quattro_rs said:
can someone explain how to do it step by step im new at this ?
Click to expand...
Click to collapse
It's in the FAQ that is stickied at the top of the forum here...this is always a good place to start when looking for answers.
Here's the relevant section with links:
Q: How do I root/unroot the Nexus S?
Check the development section links below for more detail, but you gain root on the Nexus S by booting the phone into fastboot mode and typing "fastboot oem unlock." This will wipe your phone and it's SD card partition. To unroot it, again boot into fastboot mode and type "fastboot oem lock."
Step 1: http://forum.xda-developers.com/showthread.php?t=878786
Step 2: http://forum.xda-developers.com/showthread.php?t=875875
In the event you want to return to stock, simply flash the NAND backup found here: http://forum.xda-developers.com/showthread.php?t=884093 . This will restore everything, including the stock recovery image. Then as mentioned above go into the bootloader/fastboot mode and enter "fastboot oem lock" in ADB.
(All credit goes to the original author(s) of the linked thread!)
Click to expand...
Click to collapse
If that doesn't get you going, let me know specifically what's confusing you and I'll try to help.
For me, on 2.3.1, I think I would just use adb shell to rm or uninstall the superuser.apk (/data/app/com.noshufou.android.su-1.apk (might be different name on yours depending on version) and then to rm the su binary (/system/bin/su). Then I'd reboot the phone to make sure the recovery was stock, then I'd fastboot oem lock the phone.
Flashing a nandroid might be easier for you.
slowz3r said:
Oh, alright
google hasnt released a full OS for flashing have they?
Click to expand...
Click to collapse
Not that I'm aware of!
Wish they would...I miss having a nice stock image from a trusted source to go back to, but other than root and CWM, I haven't messed with the OS; Gingerbread's fast and sweet enough for me for now.
I don't care for some of the apps though, the gapps camera sucks by a long shot compared to Samsung's SGS camera app, for example.
distortedloop said:
Not that I'm aware of!
Wish they would...I miss having a nice stock image from a trusted source to go back to, but other than root and CWM, I haven't messed with the OS; Gingerbread's fast and sweet enough for me for now.
I don't care for some of the apps though, the gapps camera sucks by a long shot compared to Samsung's SGS camera app, for example.
Click to expand...
Click to collapse
Normally I would do CM, but Im not a fan of alpha stage builds, ill wait for beta and then do nightlies from there
Hopefully the CM team take care of issues like the camera, and such
EDIT: never been a fan of CWM, hope Amon_RA releases a recovery
slowz3r said:
Normally I would do CM, but Im not a fan of alpha stage builds, ill wait for beta and then do nightlies from there
Hopefully the CM team take care of issues like the camera, and such
EDIT: never been a fan of CWM, hope Amon_RA releases a recovery
Click to expand...
Click to collapse
Ditto.
Ditto.
Ditto (for the most part, CWM isn't bad, but I also prefer Amon_RA).
distortedloop said:
It's in the FAQ that is stickied at the top of the forum here...this is always a good place to start when looking for answers.
Here's the relevant section with links:
If that doesn't get you going, let me know specifically what's confusing you and I'll try to help.
For me, on 2.3.1, I think I would just use adb shell to rm or uninstall the superuser.apk (/data/app/com.noshufou.android.su-1.apk (might be different name on yours depending on version) and then to rm the su binary (/system/bin/su). Then I'd reboot the phone to make sure the recovery was stock, then I'd fastboot oem lock the phone.
Flashing a nandroid might be easier for you.
Click to expand...
Click to collapse
i manged to lock/unlcok the bootloader ,
what i dont understand is this :
Requirements:
-Clockwork recovery or other custom recovery
Click to expand...
Click to collapse
quattro_rs said:
i manged to lock/unlcok the bootloader ,
what i dont understand is this :
Click to expand...
Click to collapse
the stock recovery does not allow you to flash custom/unsigned roms or other files for that matter.
so a custom Recovery is required, as of now the only one I believe is available is ClockWorkMod
got it all working now thanks to you and distortedloop .
thanks a lot guys.

Categories

Resources