Database Users

Root Nexus One on a Mac/Linux/Windows

Hi guys. I published a step by step guide for all the newbies (I had a tough time the first time. Slightly different combination but it works! Also flashed the custom recovery image!
http://ilikemygooglephone.com/2010/...-and-root-google-nexus-one-mac-windows-linux/

This tutorial on rooting and flashing the RA recovery rom is THE BOMB!
Followed all the steps and now I too have gone to the dark side, and eaten some cookies....
Nice work.

Great! Love it!

This how I REroot Android in my N1.
Needs:
1) RA recovery image v2.0
2) fastboot
3) adb
1) Set to bootloader
Code:
adb reboot-bootloader
2) Boot RA-recovery 2.0
Code:
fastboot boot /path/to/recovery-RA-nexus-v2.0.0.img
Yes, it only boot the recovery image in memory.
2a) If you have RA already, then just boot the recovery
3) RA: Mount -> mount /system
4) Change permission /system/bin/su to 4755
Code:
adb shell 'chmod 4755 /system/bin/su'
5) Reboot, and enjoy your rooted Android.
Tested, on FRG83D, FRG83G and GRI40 stocks
Good luck.
Thank you.

Does it have to be 2.0.0? or can it be any of the RA recoveries above 2.0.0?

bahathir said:
This how I REroot Android in my N1.
Needs:
1) RA recovery image v2.0
2) fastboot
3) adb
1) Set to bootloader
Code:
adb reboot-bootloader
2) Boot RA-recovery 2.0
Code:
fastboot boot /path/to/recovery-RA-nexus-v2.0.0.img
Yes, it only boot the recovery image in memory.
2a) If you have RA already, then just boot the recovery
3) RA: Mount -> mount /system
4) Change permission /system/bin/su to 4755
Code:
adb shell 'chmod 4755 /system/bin/su'
5) Reboot, and enjoy your rooted Android.
Tested, on FRG83D, FRG83G and GRI40 stocks
Good luck.
Thank you.
Click to expand...
Click to collapse
A question for you, if it's possible to simply just change the permission of the su file on the phone, why do most auto root zip's come with an su file of their own?
Could they not just run the script above?

this whole procedure thing ... do stock users like myself lose anything? Like, does it wipe data or does it simply root and nothing at all changes?
You can never tell with these procedures... half wipe the phone...

I haven't tested it, but from the steps listed above (by bahathir) you won't lose any data.
All he's doing is getting you to boot into fastboot mode (power on the phone while pressing the trackball), and then loading the custom recover into temporary memory.
Then, the system folder is mounted and the required permissions are applied to the su file. Once that's done, you reboot your phone and nothing else changes.
The question that I had above though, is that I've not seen this method used before. Most one-click root methond replace the su file (requiring you to flash a zip file from custom recovery).

ahh too bad it doesn't work. maybe a 2.3.3 thing, but I just tried unlocking my bootloader and it says I'm missing AdbWinApi.dll from my PC ... but it's clearly there.
I have the most up-to-date Android SDK packages. I've used them before to root my nexus without a hitch...

SU should be present on the system, and the method above takes it for granted. Thus it's for RErooting. Rooting methods bring the SU - they don't care if there's one on the system, assuming that there isn't.
On the other hand, I'm completely unsure that "fastboot boot recovery.img" will work on custom image and locked bootloader. If it's the case - this is the most overlooked and bulletproof rooting method for Nexus. But I doubt it's the case.

Here's a n00b question. I have an unlocked boot loader and had previously rooted my phone using superoneclick. I wiped all the data before moving to stock gingerbread since I was on CM7 nightlies before. So there is no "su" in my phone. I get the obvious error:
c:\android-sdk-windows\platform-tools>adb shell 'chmod 4755 /system/bin/su'
/sbin/sh: chmod 4755 /system/bin/su: not found
when I try to run the steps listed here. Any ideas how to get the 'su' on my phone?

I guess you're executing "rerooting guide". Well, you can stop now, since there is no SU.
Flash it on your phone. That would be the obvious solution. Running unlocked bootloader and custom recovery, not really hard to do.
When you're doing things you don't fully understand, sometimes you go in extremely awkward ways to accomplish simple tasks. Having unlocked bootloader, why are you bothering with those guides? Reboot to fastboot, flash custom recovery, flash SU package in recovery, reboot. That would be all. Hard? not really.

Jack_R1 said:
I guess you're executing "rerooting guide". Well, you can stop now, since there is no SU.
Flash it on your phone. That would be the obvious solution. Running unlocked bootloader and custom recovery, not really hard to do.
When you're doing things you don't fully understand, sometimes you go in extremely awkward ways to accomplish simple tasks. Having unlocked bootloader, why are you bothering with those guides? Reboot to fastboot, flash custom recovery, flash SU package in recovery, reboot. That would be all. Hard? not really.
Click to expand...
Click to collapse
Thanks Jack! Can you point me to an su package that I can safely flash with gingerbread?
Sent from my Nexus One using XDA App

I found the package nexus-addon-0.1-signed.zip while searching for 'su' packages to root an unlocked nexus one on this guide http://forum.xda-developers.com/showthread.php?t=636795 . Will it be safe to flash this on a stock gingerbread?

aliezad said:
I found the package nexus-addon-0.1-signed.zip while searching for 'su' packages to root an unlocked nexus one on this guide http://forum.xda-developers.com/showthread.php?t=636795 . Will it be safe to flash this on a stock gingerbread?
Click to expand...
Click to collapse
I don't think that zip would work.
I rooted by applying the su.zip provide by dsixda here: http://forum.xda-developers.com/showthread.php?t=968396 (attachment, bottom of first post)
You would need to flash this from custom recovery (I used Amon RA 2+).

Thanks Brownbay! Worked like a charm!

Jack_R1 said:
...I'm completely unsure that "fastboot boot recovery.img" will work on custom image and locked bootloader.
Click to expand...
Click to collapse
Unfortunately this won't work on a locked bootloader (at least, not on mine!), so if you've used 'super one click' to root your N1 without unlocking it (like me), this method won't work for you.

I already have had my bootloader unlocked. I'm wondering if this rooting method alone will wipe my phone?

No, it won't wipe your phone.

Can't get recovery image on my Hero (rooted)

Hi,
last year, I rooted my Hero, then I bought a Desire. But now my girlfriend would like to use my Hero. So I took my rooted Hero and tried to reflash a new rom, but on one way or another, it keeps failing.
I tried to re-install a new recovery, but accidentaly chose CDMA-hero instead of GSM-hero. Now I can't get into a recovery. When I try to boot the phone, while holding Home button, I only get the HERO-logo... I can get into fastboot though.
I remember I just installed a rooted stock rom: HTC Generic 2.73.405.66. Now I'm reading that this rom results in troubles installing a recovery. I tried EVERYTHING:
- flashrec: can't backup my image, can't flash a recovery (button greyed out)
- tried to downgrade to 2.73.405.5 as suggested on the homepage of flashrec
- tried the guide on modaco: http://android.modaco.com/content/h...ng-the-patched-recovery-image-on-your-device/
My situation is now: Hero is rooted, but my Hero doesn't have a recovery image...and I really need one to flash a custom rom on it...
Can anyone help me please?

Greetings,
Why not try this :
http://forum.xda-developers.com/showpost.php?p=4898505&postcount=1
Code:
Copy recovery-RA-hero-v1.6.2.img to the root of your sdcard
Boot into your current custom recovery (boot while holding HOME)
Connect your Hero via usb to your pc/mac/...
adb shell
$su (not required if you have root already)
#mount -a
#flash_image recovery /sdcard/recovery-RA-hero-v1.6.2.img
Change to this on my gsm hero today and easy enough to do via adb.

If above doesn't work. Just downgrade to 2.73.405.5 - use the goldcard method in my guide in my sig. Simple.

Steven_belfast said:
Greetings,
Why not try this :
http://forum.xda-developers.com/showpost.php?p=4898505&postcount=1
Code:
Copy recovery-RA-hero-v1.6.2.img to the root of your sdcard
Boot into your current custom recovery (boot while holding HOME)
Connect your Hero via usb to your pc/mac/...
adb shell
$su (not required if you have root already)
#mount -a
#flash_image recovery /sdcard/recovery-RA-hero-v1.6.2.img
Change to this on my gsm hero today and easy enough to do via adb.
Click to expand...
Click to collapse
euhm, the problem is, that I even can't get into recovery since it crashes and keeps showing the HERO-logo... and I already said that I can't downgrade, the process returns an error 'wrong client id' or something... I don't need the goldcard since my Hero is unbranded.

[Q] Cannot get to recovery with flashed clockwork (Bell D-Z Canada)

Edit: "Rom Development" is only meant for very advanced technical discussion directly related to ROM development activity and the delivery of actual ROMs and ROM components ONLY. Nothing else goes in here. Moved thread to "General." Please refer to "[REF] STOP! Read before posting!" ~TheRomMistress
Not able to get ROM manager to flash Clockwork for recovery. It shows successful but then when I reboot to recovery, it shows this image of red triangle over a cellphone, probably meaning recovery does not function.
Any ideas? I already have S-OFF done...

BriEE said:
Not able to get ROM manager to flash Clockwork for recovery. It shows successful but then when I reboot to recovery, it shows this image of red triangle over a cellphone, probably meaning recovery does not function.
Any ideas? I already have S-OFF done...
Click to expand...
Click to collapse
This is how I got it to work:
Step 1 - run Visionary R12 to get perm root.
Step 2 - Push the files from page 1 to phone via adb
./adb push [path to file]/wpthis-Z.ko /data/local/wpthis-Z.ko
./adb push [path to file]/hboot_7230_0.84.2000_100908.nb0 /data/local/hboot-eng.img
(as you can see above, I renamed the HBOOT file on the phone just to be consistent)
note: I'm not sure if you HAVE to put them in /data/local of if you can just run this from /sdcard - but I didn't want to experiment
Run the commands below as root via adb shell or from a terminal on your phone.
Step 3 -
insmod /data/local/wpthis-Z.ko
Step 4 -
dd if=/data/local/hboot-eng.img of=/dev/block/mmcblk0p18
Step 5 -
sync
Step 6 - Wait two minutes and then run clockwork and try to install recovery - do not reboot your phone.
Worked for me. Good luck.

I already have S-OFF and perm root though, why do it again?
So you're saying the WP isn't perm and neither is S-OFF? Is our root perm even lol?

Just reflash clockwork from rom manager. Same thing happened to me.

foxfire235 said:
Just reflash clockwork from rom manager. Same thing happened to me.
Click to expand...
Click to collapse
Same here, just reflash clockwork a second time and it should work.
Sent from my HTC Vision using XDA App

I had to flash CW twice as well. It seems successful after the first try but booting into recovery would show a black screen with a small phone icon.

codf4ther said:
I had to flash CW twice as well. It seems successful after the first try but booting into recovery would show a black screen with a small phone icon.
Click to expand...
Click to collapse
Did you just flash it twice, or did you follow the complete instructions twice?

[Q] G2 Lost S-OFF after hboot update?

First I want to thank all from this site for all the work you've done!
OK, got a G2 few days ago rooted it using rage method, updated radio to 26.04.02.17 (read that solved some problems with cyanogen's 6.1.1 ROM), installed 6.1.1 ROM and all was well... Then I decided to upgrade hboot (for no particular reason) to 0.85.005 with fastboot. After install it rebooted and noticed I now have SHIP S-ON ...and it wouldn't boot..got stuck on HTC splash screen. So I say oops...pull battery and go into recovery and do a restore to a rooted stock ROM. Was successful but was hoping it would give me root back but no joy. Then tried to install 6.1.1 from ROM manager but no joy. (no surprise with S_ON) So I'm wondering:
Why did hboot update change it to S-ON?
Why didn't my restore restore S_OFF? ( thought restore re-wrote everything)
AND..where do I go from here? Should I just use rage again to get root?
Any help would be greatly appreciated!!
Again, thanks to all!!
Edit: OK just realized I still have root access threw terminal emulator???
How can this be with S-ON??
So I guess I still have root so I tried to install cyogen 6.1.1 from sd card using revovery.
all seems to go well, says its complete but when I reboot, it gets stuck on HTC splash screen
Also tried gfree and this method http://forum.xda-developers.com/wik...cess_.28Permanent_Root_.2F_.22Permaroot.22.29
got to 2nd to last command:
# /data/local/tmp/root
and get
# mkdir failed for /system/xbin, file exists
Anyone??

That sounds like the stock *DZ* hboot, not the G2 one. If so, you're lucky you didn't brick your phone. I wouldn't switch hboots between DZ/G2 unless you were flashing the whole ROM.
The fact that it's a stock one explains why you have S-ON, if you only had S-OFF via the eng hboot before.
What you need to do is run gfree, as you say, to get proper radio S-OFF.
S-ON/S-OFF has nothing to do with root. So you can still be S-ON and have root.
If you did a nandroid restore through Clockwork then as far as I'm aware that doesn't include a restore/backup of hboot.
You won't be able to flash another custom ROM/recovery until you get S-OFF back again.
That "mkdir" error message is normal, just ignore it. But gfree doesn't work with CM 6.1.1. It will work on 6.1 but there are some incompatible kernels too.
I suggest installing the eng hboot (the correct one for your phone, see the Wiki) to get S-OFF (but be careful doing this, e.g the checksums). Then revert to a ROM that is compatible with gfree and run gfree to get radio S-OFF. Then you can revert back to 6.1.1 or whatever you want.

steviewevie said:
That sounds like the stock *DZ* hboot, not the G2 one. If so, you're lucky you didn't brick your phone. I wouldn't switch hboots between DZ/G2 unless you were flashing the whole ROM.
The fact that it's a stock one explains why you have S-ON, if you only had S-OFF via the eng hboot before.
What you need to do is run gfree, as you say, to get proper radio S-OFF.
S-ON/S-OFF has nothing to do with root. So you can still be S-ON and have root.
If you did a nandroid restore through Clockwork then as far as I'm aware that doesn't include a restore/backup of hboot.
You won't be able to flash another custom ROM/recovery until you get S-OFF back again.
That "mkdir" error message is normal, just ignore it. But gfree doesn't work with CM 6.1.1. It will work on 6.1 but there are some incompatible kernels too.
I suggest installing the eng hboot (the correct one for your phone, see the Wiki) to get S-OFF (but be careful doing this, e.g the checksums). Then revert to a ROM that is compatible with gfree and run gfree to get radio S-OFF. Then you can revert back to 6.1.1 or whatever you want.
Click to expand...
Click to collapse
Thanks for responding! Especially after this post has turned into more of a rambling blog as I learn more.
I tried to run gfree to get s-off and it doesn't work, stays s-on. Thought it was because of the "mkdir" error message I was getting. Then tried to install eng hboot using the whole G2 ROOT INSTRUCTIONS here:
http://forum.xda-developers.com/showthread.php?t=834228
Everything goes smooth except for the"mkdir failed for /system/xbin. file exists"
When I reboot, still have:
VISION PVT SHIP S-ON
hboot-0.85.0005
Any ideas??
Again thanks for any help and suggestions!
Just noticed the first commands in the G2 ROOT INSTRUCTIONS have a "$" sigh ie: "$ adb push su /sdcard/su"
Does this mean you should run "adb shell" first? If that.s the case, I get "adb: permission denied" although I do see su on sdcard.
(I know I'm really grasping here )

No, you don't run "adb shell" before running those adb commands, because "adb shell" will give you a command prompt on your phone, and those adb push commands need running from your PC's command prompt. That "$" prompt shown in the guide can be confusing, because it's being run from a PC running Linux, which has a $ prompt. If you have Windows then you will have some sort of "C:\" prompt.
If you are only installing the eng hboot though, you don't need to do all that, since you already have root. Skip to the "Perm Root" section in that guide that you linked, and do everything up to and including the "dd" command. Then the sync and reboot bit (skip over the "root" script).
Although check what message you get from the insmod command. We might have a problem here, because if you're on CM 6.1.1 (that's what you're on, right ?) then gfree won't work and I don't know if either of those wpthis modules (OTA and pre-OTA) will work properly on CM 6.1.1.
The insmod is crucial because unless that command gives you the "right" error message as shown in the procedure, it won't disable the NAND write protection and so won't let you write the hboot permanently.

A bit offtopic, but maybe someone will find this helpful: in many tutorials for *NIX (Linux, OSX, BSD etc.) users you'll find that what you need to type in a command prompt (terminal) starts with either $ or #.
While that may be confusing for Windows users, it is a hint as to whether you are supposed to run the commands as a simple user (the prompt shows a $) or as the administrator (or root) user (in which case, the prompt shows a #).

steviewevie said:
No, you don't run "adb shell" before running those adb commands, because "adb shell" will give you a command prompt on your phone, and those adb push commands need running from your PC's command prompt. That "$" prompt shown in the guide can be confusing, because it's being run from a PC running Linux, which has a $ prompt. If you have Windows then you will have some sort of "C:\" prompt.
If you are only installing the eng hboot though, you don't need to do all that, since you already have root. Skip to the "Perm Root" section in that guide that you linked, and do everything up to and including the "dd" command. Then the sync and reboot bit (skip over the "root" script).
Although check what message you get from the insmod command. We might have a problem here, because if you're on CM 6.1.1 (that's what you're on, right ?) then gfree won't work and I don't know if either of those wpthis modules (OTA and pre-OTA) will work properly on CM 6.1.1.
The insmod is crucial because unless that command gives you the "right" error message as shown in the procedure, it won't disable the NAND write protection and so won't let you write the hboot permanently.
Click to expand...
Click to collapse
ahhhh..thanx for clarifying "$" issue for me.
I am NOT on CM 6.1.1
I have stock OTA rom right now (with root), sorry for the misunderstanding
OK,this is exact error message I get:
insmod: init_module '/data/local/wpthis-OTA.ko' failed (function not implemented)
After I run dd=..... I get
2048+0 records in
2048+0records out
1048576 bytes transferred in 0.079 secs (13273113bytes/sec)
So all looks perfect to me, but I still get stuck with:
....S-ON
hboot-0.85.0005
does the "insmod" being in error message mean anything?
In any event, at least I still have a working phone and learned alot more
(like you said..I'm very lucky I didn't brick it flashing this hboot update)

That's the "correct" error message from insmod. But weird stuff is going on here, which isn't too suprising if you have the wrong hboot for your phone.
I'm getting confused, I thought you were on CM 6.1.1. I also thought your phone was stuck in a boot loop, but you seem to be able to still run commands as root, so presumly it boots ok now ?

steviewevie said:
That's the "correct" error message from insmod. But weird stuff is going on here, which isn't too suprising if you have the wrong hboot for your phone.
I'm getting confused, I thought you were on CM 6.1.1. I also thought your phone was stuck in a boot loop, but you seem to be able to still run commands as root, so presumly it boots ok now ?
Click to expand...
Click to collapse
Sorry for the misunderstanding, I had CM 6.1.1 on when I flashed wrong hboot. After that it would get stuck on HTC screen when trying to boot up into CM 6.1.1
So I booted into recovery and did a restore which luckily worked. Which now I have no idea why that worked looking back other than because it was a legit stock ROM, so it allowed it. Is this the case??
Last night I actually tried to un-root and get everything back to stock (including hboot) via this method:
ttp://theunlockr.com/2010/12/01/how-to-unroot-the-t-mobile-g2-htc-vision/
but got stuck on "dd if=/sdcard
/miscnew.img of=/dev/block/mmcblk0p17" with a read only ermision denied message
which I wasn't surprised because I have S=ON

How to unroot the latest RUU (5.07) [GUIDE]

Here is a quick guide on how to unroot the latest RUU 5.07. It seems that quite a few people are having trouble unrooting their device or running an official RUU while being on the latest update, or a ROM based on the latest update.
The problem is that HTC has fixed the bootloader (in particular Hboot 2.18) so that it will reject any PC36IMG.zip official software or RUU files that update previous operating systems on the phone (a S-ON phone). You would usually need a RUU (I'm calling both the PC3IMG.zip file and the RUU file an RUU) that is for your current operating system. If your phone is on the latest 5.07 update or a ROM that is based on the 5.07 update, then latest RUU that exist is for the Evo with RUU Supersonic 4.67. 5.07 never came out, done intentionally by HTC I believe. So none of the RUUs which exist today will work with the 5.07 update. The problem exist because the phone's misc partition is updated whenever you accept an update or run a RUU from HTC, or even flash a ROM. There are other cases as well. The only way to run an official RUU on a phone that is not currently S-OFF is either to downgrade the phone's misc partition, or to turn the phone S-OFF (which you will still have to flash the phone's misc partition to do).
What I've done is put together a quick guide for those who need (or just insist) on unrooting their Evo. It is brief and only for a PC (not a Mac). Hopefully, someone in the future can provide further details or make it Mac friendly or even more user friendly because I don't have a Mac, nor the time to spend to make this guide perfect. I have another phone too to deal with. Remember too, that everything is done at your own risk. So if something goes wrong, well you knew the risks.
For this guide I'm going to assume that you are on Hboot 2.18, the phone is S-ON, the bootloader is unlocked (UNLOCKED), and that the phone's ROM is currently rooted. If not, then this is not the right guide for you.
1. Download this zip file. It contains the necessary files that you will need.
https://dl.dropbox.com/u/38127313/sdk.zip
2. Plug your phone into your computer. Then go to Settings/Applications and uncheck Fastboot. Then goto Development and make sure that USB debugging is now checked. If you have a custom ROM, then the locations of these settings may be slightly different.
If you need the HTC drivers, then I have also included the drivers.exe file that you must run from your computer to install the "MyHtc" drivers that you must have under the computer's device manager when the phone is plug in.
3. Next, unzip the file to a folder, preferably sdk. Rename the "PC36IMG_SuperSonic_GB_Sprint_WWE_4.54.651.1_Radio_2.15.00.0808_NV_2.15_release_220182_signed" file to PC36IMG.zip (not PC36IMG.zip.zip). Place the phone into "Disk drive, then copy the PC36IMG.zip file to your sdcard. Afterwards, don't forget to change the phone back to "Charge only".
4. Next you will need to open a command prompt at the folder where you extracted the files. If you are not familiar or uncomfortable with adb commands, then I cannot help you here.
5. Type or copy the below commands exactly as they appear.
adb push flash_image /data/local <ENTER>
(This places the file on your phone in the /data/local directory).
adb push mtd-eng.img /data/local <ENTER>
(This places the file on your phone in the /data/local directory).
adb shell <ENTER>
(You should see either a dollar sign ($) or a pound sign (#) at your prompt, depending on your ROM. If you do not then something went wrong. And, No the phone will not brick if you should stop at this point).
su <ENTER>
(You might not need this command depending on your ROM, and also you should check to see if your phone is asking for superuser permissions. If everything went Ok, you should now see a pound (#) sign at your prompt. If you do not then something went wrong. And, No the phone will not brick if you should stop at this point).
cd /data/local <ENTER>
(You need to be in the directory where you put the flash_image and mtd-eng.img files).
chmod 755 flash_image <ENTER>
(flash_image needs to be assigned permissions).
./flash_image misc mtd-eng.img <ENTER>
(This is the most critical step here).
reboot bootloader <ENTER>
(I prefer this step, as it is much faster than pulling the battery and all that other stuff that people suggest).
The phone should now reboot directly into the bootloader. Also the phone will now be locked again (LOCKED OWW) regardless of its previous state. Next hit the power button. It will then take some time to read the PC36IMG.zip file. If everything went Ok, then it should ask you whether or not you want to accept the update, which means that your misc partition was successfully downgraded, and now you can successfully run the RUU.
EDIT: I have to re-upload the sdk.zip file, because the original one had a problem with the PC36IMG.zip file. It should be available shortly. The one I added does work this time; however, the phone may have to be updated in order to bring it back to the latest bootloader and update. It's not the latest RUU 4.67, but the second latest 4.54. I cannot believe that something was wrong with that file. Also, instead of the PC36IMG.zip file that I added, you could also use any other PC36IMG.zip file or a RUU.exe file from HTC. They should work as well. I would not recommend a RUU below Supersonic 3.70. I'm going to upload some of these as well when I get a chance. I have like all of them.

Re: How to unroot the latest RUU (5.07)
You should put "[GUIDE]" in the title, right now it seems like a question
Just a thought anyway.
Sent from my PG06100 using xda premium

CNexus said:
You should put "[GUIDE]" in the title, right now it seems like a question
Just a thought anyway.
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
Thanks for the advice. I'm currently re-uploading the sdk.zip file. Something went wrong with the PC36IMG file. It should be available again in a little while.

I wonder if you can help me?
I have a problem with an Evo I got from someone, it mostly gets stuck in a bootloop but sometimes it actually boots all the way up. As your guide mentioned, I'm not able to RUU because its on the 5.0.7. I think the phone was rooted because it had a few .apk's that require root including su.apk. I did a factory reset while the phone was on a sprint account but it didn't fix the issue........ long story short, I noticed the bootlooping stopped when she got off the phone, so I figured the bootloop was caused by the data running through it or something. Today I turned the phone on and fooled around with it for about an hour before I decided to put it on my pageplus account because my verizon droid razr was stolen yesterday, as soon as I did the esn swap with the pageplus rep the phone started the bootlooping again. So I came across your post and luckily got the phone to boot up and began following your guide...... when i got to the "su" I didn't get "#" sign and permission was denied. I noticed the su.apk was not in the app draw so I downloaded it, I also installed root explorer to see if I get root access, no luck. Since then I can't get the Evo to boot up..... So finally my question, is it possible to execute your guide in fastboot or is there a way to push su through fastboot via adb?
---------- Post added at 09:12 PM ---------- Previous post was at 09:05 PM ----------
6foot5nbad said:
I have a problem with an Evo I got from someone, it mostly gets stuck in a bootloop but sometimes it actually boots all the way up. As your guide mentioned, I'm not able to RUU because its on the 5.0.7. I think the phone was rooted because it had a few .apk's that require root including su.apk. I did a factory reset while the phone was on a sprint account but it didn't fix the issue........ long story short, I noticed the bootlooping stopped when she got off the phone, so I figured the bootloop was caused by the data running through it or something. Today I turned the phone on and fooled around with it for about an hour before I decided to put it on my pageplus account because my verizon droid razr was stolen yesterday, as soon as I did the esn swap with the pageplus rep the phone started the bootlooping again. So I came across your post and luckily got the phone to boot up and began following your guide...... when i got to the "su" I didn't get "#" sign and permission was denied. I noticed the su.apk was not in the app draw so I downloaded it, I also installed root explorer to see if I get root access, no luck. Since then I can't get the Evo to boot up..... So finally my question, is it possible to execute your guide in fastboot or is there a way to push su through fastboot via adb?
Click to expand...
Click to collapse
BTW, Bootloader is still unlocked

If bootloader is unlocked, flash a recovery through fastboot
Code:
fastboot flash recovery path/to/RECOVERY_NAME_HERE
Most likely RECOVERY_NAME will end with ".img" so the command would be like this:
Code:
fastboot flash recovery /path/to/recovery-evo.img
After that, search google for a "zip" file named "su-signed-efghi.zip", look for a hit on goo.im (search "evo 4g su-signed-efghi.zip") and download and place it on your sdcard
Boot into recovery (VolDown + Power, then user volume keys to navigate and power key to select recovery)
Then choose "flash zip" and locate the "su-signed-efghi.zip" file and flash it
You should now have the su binary installed in the correct place
Sent from my PG06100

CNexus said:
If bootloader is unlocked, flash a recovery through fastboot
Code:
fastboot flash recovery path/to/RECOVERY_NAME_HERE
Most likely RECOVERY_NAME will end with ".img" so the command would be like this:
Code:
fastboot flash recovery / path/to/recovery-evo.img
After that, search google for a "zip" file named "su-signed-efghi.zip", look for a hit on goo.im (search "evo 4g su-signed-efghi.zip") and download and place it on your sdcard
Boot into recovery (VolDown + Power, then user volume keys to navigate and power key to select recovery)
Then choose "flash zip" and locate the "su-signed-efghi.zip" file and flash it
You should now have the su binary installed in the correct place
Sent from my PG06100
Click to expand...
Click to collapse
Thanks for your quick response. Been trying that but its been going into a bootloop after I select recovery from hboot. Can't boot into recovery at all I was thinking about using adb to flash a stock recovery but all the recovery.img's i come across.... seem to be for an older hboot and/or system. Also I don't want to attempt anything that will make things worse. I've rooted dozens of Evo's on hboot 2.18 and I have a good Idea of how adb works. I'm wondering if that if I can manage to get S-Off will the phone be able to take an RUU then? or is there anyway to push a older flash_image to trick RUU into updating? I guess the question I should ask is what would you do if your evo would barely boot normally and couldn't get into recovery? the only thing that does work consistently is Hboot and I can't launch recovery through adb nor hboot.

update
6foot5nbad said:
Thanks for your quick response. Been trying that but its been going into a bootloop after I select recovery from hboot. Can't boot into recovery at all I was thinking about using adb to flash a stock recovery but all the recovery.img's i come across.... seem to be for an older hboot and/or system. Also I don't want to attempt anything that will make things worse. I've rooted dozens of Evo's on hboot 2.18 and I have a good Idea of how adb works. I'm wondering if that if I can manage to get S-Off will the phone be able to take an RUU then? or is there anyway to push a older flash_image to trick RUU into updating? I guess the question I should ask is what would you do if your evo would barely boot normally and couldn't get into recovery? the only thing that does work consistently is Hboot and I can't launch recovery through adb nor hboot.
Click to expand...
Click to collapse
I found and exploit on TacoRoot that will get me temp root access without booting into recovery as long as I had an recovery log in /data/data/recovery/log (stock preferably). So I would greatly appreciate if someone can post the file here. I want to attempt to use the exploit to get temp root access then use this guide to get to the point where i can use an RUU.
---------- Post added at 01:22 AM ---------- Previous post was at 01:11 AM ----------
6foot5nbad said:
I found and exploit on TacoRoot that will get me temp root access without booting into recovery as long as I had an recovery log in /data/data/recovery/log (stock preferably). So I would greatly appreciate if someone can post the file here. I want to attempt to use the exploit to get temp root access then use this guide to get to the point where i can use an RUU.
Click to expand...
Click to collapse
Also, I would need help on how to push the recovery log file to /data/data/recovery/log if possible or would it simply be adb push log /data/data/recovery/ ?

An RUU would only work if you had a lower or equal version on your phone than the RUU
As for your actual issue....you cant use adb while its in the bootloader, phone has to be fully booted if you want to do anything with adb
The only thing you can do while in hboot is to use fastboot
Try running:
Code:
fastboot reboot recovery
And see if that gets you into recovery
Sent from my PG06100

CNexus said:
An RUU would only work if you had a lower or equal version on your phone than the RUU
As for your actual issue....you cant use adb while its in the bootloader, phone has to be fully booted if you want to do anything with adb
The only thing you can do while in hboot is to use fastboot
Try running:
Code:
fastboot reboot recovery
And see if that gets you into recovery
Sent from my PG06100
Click to expand...
Click to collapse
Yes, I've tried -fastboot reboot recovery- in fastboot, just goes into a boot loop....... I did get the phone to stay booted overnight, I think as long as the battery is fully charged it stays on, and I can use adb now. The main issue now is that I can't boot into recovery therefore, like I mentioned it just goes into a bootloop and the battery discharges if I let the phone bootloop while trying to boot into recovery. Also, I noticed that the phone won't boot normally unless I have a full charge (Green Light). I think I just need the recovery log file, my thinking is if I can put the log file in the the correct location I can trick the phone into thinking it booted into recovery. If I can get temp root access then I use this guide to relock the bootloader and be able to use an RUU. Do you think that's possible?
---------- Post added at 12:24 PM ---------- Previous post was at 11:59 AM ----------
6foot5nbad said:
Yes, I've tried -fastboot reboot recovery- in fastboot, just goes into a boot loop....... I did get the phone to stay booted overnight, I think as long as the battery is fully charged it stays on, and I can use adb now. The main issue now is that I can't boot into recovery therefore, like I mentioned it just goes into a bootloop and the battery discharges if I let the phone bootloop while trying to boot into recovery. Also, I noticed that the phone won't boot normally unless I have a full charge (Green Light). I think I just need the recovery log file, my thinking is if I can put the log file in the the correct location I can trick the phone into thinking it booted into recovery. If I can get temp root access then I use this guide to relock the bootloader and be able to use an RUU. Do you think that's possible?
Click to expand...
Click to collapse
I forgot to mention, the TacoRoot Exploit requires the recovery log file (http://rootzwiki.com/topic/13713-tacoroot-htc-universal-root-exploit-12-30-2011/) to be in /data/data/recovery/ directory, so it requires a user to boot into recovery to create the log file, and I can't boot into recovery.... so my idea is to push the recovery log file to /data/data/recovery/log cause thats where the exploit is looking for the log file. I'm hoping that will prevent me from having to boot into recovery which is where I'm getting stuck on the tacoroot exploit. With shortydoggs guide, I'm getting stuck at the "su" command cause the evo (for some reason) isn't rooted anymore. So my plan is to get me temp root with TacoRoot so I can get "#" and continue with shortydoggs guide. Not sure if that's possible but at this point its my only option since I can't get into recovery to flash su.zip nor can I RUU cause I'm on 5.0.7 which has no RUU.

I can give you the file, but it's hard to get it to work without that recovery. You have to extract out of the zip file and then push it to the /data/data/recovery directory. I tried it myself and I can adb push it, but when doing the tacoroot --root, I get an error "/data/local/tacoroot.sh: cannot create /data/local.prop: permission denied".
EDIT: I uploaded the two files that you need. You need to unzip the two files. Then push the log file to the /data/data/recovery directory, and the local.prop file to the /data/ directory. Getting them there will be up to you, as I'm not the most Linux educated person out there. I'm only able to push the files because my phone is already rooted. Hopefully you figure it out or someone more familiar with Linux (adb) commands can help you. Then, the "adb shell /data/local/tacoroot.sh --root" command is a breeze.

Code:
adb push tacoroot.sh /data/local/tacoroot.sh
adb shell chmod /data/local/tacoroot.sh
adb shell sh /data/local/tacoroot.sh --setup
#should give an error after line above, its fine because you're pushing the local.prop yourself
adb push local.prop /data/local.prop
adb shell sh /data/local/tacoroot.sh --root
If anything goes wrong or it doesnt work, run this to revert
Code:
adb shell sh /data/local/tacoroot.sh --undo
I would've posted the tacoroot.sh for you since I use it in my shift utility to root your phone, but I wasn't sure if it was universal for all HTC devices or just for the evo shift. Sorry about that.
Sent from my PG06100

Thanks!!!
shortydoggg said:
I can give you the file, but it's hard to get it to work without that recovery. You have to extract out of the zip file and then push it to the /data/data/recovery directory. I tried it myself and I can adb push it, but when doing the tacoroot --root, I get an error "/data/local/tacoroot.sh: cannot create /data/local.prop: permission denied".
EDIT: I uploaded the two files that you need. You need to unzip the two files. Then push the log file to the /data/data/recovery directory, and the local.prop file to the /data/ directory. Getting them there will be up to you, as I'm not the most Linux educated person out there. I'm only able to push the files because my phone is already rooted. Hopefully you figure it out or someone more familiar with Linux (adb) commands can help you. Then, the "adb shell /data/local/tacoroot.sh --root" command is a breeze.
Click to expand...
Click to collapse
Thank you and CNexus. I'll try it and let you know how it went. I probably will fool around with it tomorrow sometime so I'll get back to you then. Going back a little, after I pushed flash_image and mtd-eng.img to data/local/, I noticed a blue status bar while in hboot, I'm assumming its searching for the pg36img.img update...... that said, is it necessary to push those files again?? BTW, great guide and write up. Thanks for everything. http://forum.xda-developers.com/images/smilies/good.gif
---------- Post added at 10:51 PM ---------- Previous post was at 10:46 PM ----------
Thanks for your help, I'll let you know how it goes tomorrow.
CNexus said:
Code:
adb push tacoroot.sh /data/local/tacoroot.sh
adb shell chmod /data/local/tacoroot.sh
adb shell sh /data/local/tacoroot.sh --setup
#should give an error after line above, its fine because you're pushing the local.prop yourself
adb push local.prop /data/local.prop
adb shell sh /data/local/tacoroot.sh --root
If anything goes wrong or it doesnt work, run this to revert
Code:
adb shell sh /data/local/tacoroot.sh --undo
I would've posted the tacoroot.sh for you since I use it in my shift utility to root your phone, but I wasn't sure if it was universal for all HTC devices or just for the evo shift. Sorry about that.
Thanks for your help, I'll let you know how it goes tomorrow.
Sent from my PG06100
Click to expand...
Click to collapse

Hi, Just wondering if you would mind re-uploading the original files? The link is broken, and I'd really like to unroot my phone, so it would be really appreciated. Thanks heaps!