Database Users

rooting problems

hey. i have no clue why but my g1 isnt get rooted. ive did everything in the unlockrs step if you go to theunlockr.com. everything went successful and exactly what his did but when i go to terminal and type su it says permission denied.when i power on using camera and end it goes to android on skateboards(i doont not that matters). anyone have any ideas

mr.johnsexydavis911 said:
hey. i have no clue why but my g1 isnt get rooted. ive did everything in the unlockrs step if you go to theunlockr.com. everything went successful and exactly what his did but when i go to terminal and type su it says permission denied.when i power on using camera and end it goes to android on skateboards(i doont not that matters). anyone have any ideas
Click to expand...
Click to collapse
I followed the unlockr's steps to help David test out his new guides, and I never had a problem. If your going into terminal and typing "su" and getting the permission denied message, that means everything DIDN'T go successfully. The skating androids when in bootloader means that you have an SPL that allows you to upload custom ROMs but says nothing about whether you have root. Follow the steps again paying particular attention to each one.

If you really want to root your phone easily and without problems or confusion, follow this guy's instructions:
http://www.youtube.com/watch?v=xOo2V9qCauc

Main Version Is Older! Update Fail! Message

Hi,
Thanks in advance for anyone who tries to help me.
A few weeks ago I tried to gain root access to HTC Eris. I followed the prereq and part one of the guide but stopped there. Rebooted my phone, checked the version (2.1) and went about reinstalling apps and such.
Now I want to install a different ROM so I went back and tried to start from the beginning and put PB00IMG.zip on my phone, went to hboot, let run but then I get the message "Main Version is older! Update Fail! Do you want to reboot device?"
So when I move onto III in the walk through, I get an error on the command
adb push flash_image /system/bin
It would seem like I've lost root right? Is there anyway I can check to see if I accidentally installed the leak w/o root?
Thanks,
Nate

Easy way is to do
adb shell
if the prompt is
$
your likely on leak
if the prompt is
#
your on root.
Once your on root, flash recovery.

I am anticipating the next question, so here is your answer. If you did indeed root your phone, you should have loaded a recovery image as jcase mentioned.
First, load the new ROM onto the root of your sd card. Next, power off your phone. Then, hold down the vol up button and turn on your phone. It should boot into the recovery console. From here to load another ROM, you need to perform a wipe and then load your new ROM by flashing. You should see a Wipe and Flash from Zip menu option in recovery.
In the Wipe menu, choose the first two options in order (factory reset and cache). Wait for each to complete. Next, pressing vol down should get you back to the main menu. From here choose Flash from Zip and then select the ROM zip file you loaded onto your sd card and wait for the update to complete. Last, reboot your phone from the menu.

jcase said:
Easy way is to do
adb shell
if the prompt is
$
your likely on leak
if the prompt is
#
your on root.
Once your on root, flash recovery.
Click to expand...
Click to collapse
$
When you say "likely" you pretty much mean "sorry but you're non-rooted and I don't want to be the one to tell you" ?

xnatex21 said:
$
When you say "likely" you pretty much mean "sorry but you're non-rooted and I don't want to be the one to tell you" ?
Click to expand...
Click to collapse
You have 2.1 from the OTA, or on phone at purchase or from an image you flashed?

try su
xnatex21 said:
$
When you say "likely" you pretty much mean "sorry but you're non-rooted and I don't want to be the one to tell you" ?
Click to expand...
Click to collapse
adb shell
$ su
If you still have a $ then you most "likely" loaded a leak rather then root. If you get a # then you are in luck.
I don't remember if the the leak that included su had adb set to root by default.
good luck.

jcase said:
You have 2.1 from the OTA, or on phone at purchase or from an image you flashed?
Click to expand...
Click to collapse
I followed a guide a few weeks ago that must have been for the leaked version of 2.1.
thisismyanonymousaccount said:
adb shell
$ su
If you still have a $ then you most "likely" loaded a leak rather then root. If you get a # then you are in luck.
I don't remember if the the leak that included su had adb set to root by default.
good luck.
Click to expand...
Click to collapse
I get
su: permission denied
Click to expand...
Click to collapse
I guess that means my phone I'm stuck with it...FML!

xnatex21 said:
I guess that means my phone I'm stuck with it...FML!
Click to expand...
Click to collapse
Yes, sadly you are now stuck with the Leak.
Stay tuned as the devs are still working on it.

g00gl3 said:
Yes, sadly you are now stuck with the Leak.
Stay tuned as the devs are still working on it.
Click to expand...
Click to collapse
Does anyone know what HTC says about all of this? Can I send the phone back to them and have them "restore" the phone to factory settings?

xnatex21 said:
Does anyone know what HTC says about all of this? Can I send the phone back to them and have them "restore" the phone to factory settings?
Click to expand...
Click to collapse
Technically, modifying your device would void warranties. Even if they could "restore" the device, it would still have the newer bootloader that is causing the rooting issue. Some people have "lost" or "broken" the device bad enough that they could get a replacement from Verizon. However, there is mixed results as to what bootloader the refurbished devices come back with.

I posted before about the safety of re-rooting my eris from 1.5 to a rooted 2.2 rom, and due to lack of responses on any forums over the web, I jumped the gun today. First off my Eris after un-rooting it, wouldn't take the OTA update for 2.1, it downloaded and verified that, but after it rebooted, it was still at 1.5 saying no new updates are available. I cannot download the eris 1 click root app as it's only for 2.1 I'm assuming because it says it's not compatible with 1.5 firmware when I download it. I tried to follow this guide [Walkthrough] From stock (1.5) to rooted 2.1 (update - new link) - xda-developers and when I installed the PB00IMG.zip it downloaded but failed to flash and the screen read "Main version is older". I tried this guide All-In-One Auto-Root Script - Page 4 - xda-developers and when it says it's flashing the root image, it goes straight to a screen with only two options "recovery" something and "fastboot". None of which are listed as options in the guides. I am just trying to root my 1.5 eris and flash the KaosFroyo V3 eris rom with Amon Ra's recovery image. Thanks if anyone can help my problem, or shed light on the situation! Sorry if there's been a fix to this problem already stated, I've desperately been browsing many forums and hundreds of replies to no avail. Thanks again.

It looks to me like you got a pretty reasonable answer to the same question over on Android Forums
bftb0

Rooting OTB 2.1 Eris

I have now Rooted Two 2.1 Eris the last few days. I dont know if this has been covered, I did a search and honestly searching here is a little fetch.
This is a place holder.
POST here if you want to know how to root 2.1 or post here and let me know if its already been known how to root.
Here is the Phone Information and Specs of the one i just rooted.
Firmware Version
2.1
Baseband
2.42.00.04.12
Kernel Verison
2.6.29-8a03cb9a
[email protected] #1
Build Number
2.36.605.1 CL165907 Release-keys
Software Number
2.36.605.1
Browser Version
WebKit 3.1
PRL Version
58005
ERI Version
5

Were the specs like this before or after the rooting?

After the root.
I should have got the specs before the root. I can tell you how to do it if you have a 2.1 its fast.
I just want someone on here to verify it.

Sure why not.

Just post how to do it instead of trying to drag on a thread and make yourself big, I honestly dont think you did root them or you would of posted a tutorial. prove me wrong... go for it.

FireSokar said:
Just post how to do it instead of trying to drag on a thread and make yourself big, I honestly dont think you did root them or you would of posted a tutorial. prove me wrong... go for it.
Click to expand...
Click to collapse
Yeah honestly I'm with this guy ^.

Trust me i dont need to make myself big on xda i could care less.
Heres what I have been doing on them, push the 1.5 root to the phone reboot recovery install like you would root on 1.5 It should complete.
You will notice when it reboots that YOU DO NOT HAVE SUPER USER.
What i did was went to my cmd prompt typed adb shell, i have #. So i proceeded with installing recovery.
Once installing the new recovery i adb reboot recovery again. This time you get the green letters with the recovery, I installed the offical2.1with root over the OTB 2.1 with root. Pretty much you could install any rom with root on it.
Wiped and rebooted. Now i have 2.1 with superuser and root.

amoamare said:
Trust me i dont need to make myself big on xda i could care less.
Heres what I have been doing on them, push the 1.5 root to the phone reboot recovery install like you would root on 1.5 It should complete.
You will notice when it reboots that YOU DO NOT HAVE SUPER USER.
What i did was went to my cmd prompt typed adb shell, i have #. So i proceeded with installing recovery.
Once installing the new recovery i adb reboot recovery again. This time you get the green letters with the recovery, I installed the offical2.1with root over the OTB 2.1 with root. Pretty much you could install any rom with root on it.
Wiped and rebooted. Now i have 2.1 with superuser and root.
Click to expand...
Click to collapse
Correct me if I'm wrong but by 1.5 root you mean the 1.5 to 2.1 rooted update and that only works for phones running 1.5 which we already had. Now there trying to get root for the 2.1 leaks/ota. not to mention i think the 1.5 root was a PB00IMG.zip which is not for recovery.

Okay so I initially didnt think i would have to spell this out.
Push PB00IMG.zip to root of the SDCARD on a 2.1 OTB eris.
Adb reboot recovery apply the PB00IMG.zip
Wait for complete and reboot phone.
When the phone boots up you WILL NOT HAVE THE SUPERUSER installed. Instead if you go to your cmd prompt and type adb shell you get the # < then install the recovery-RA-eris-v1.6.2.img and flash image as usual.
Reboot recovery this time you get the Green Letters Recovery.

amoamare said:
Okay so I initially didnt think i would have to spell this out.
Push PB00IMG.zip to root of the SDCARD on a 2.1 OTB eris.
Adb reboot recovery apply the PB00IMG.zip
Wait for complete and reboot phone.
When the phone boots up you WILL NOT HAVE THE SUPERUSER installed. Instead if you go to your cmd prompt and type adb shell you get the # < then install the recovery-RA-eris-v1.6.2.img and flash image as usual.
Reboot recovery this time you get the Green Letters Recovery.
Click to expand...
Click to collapse
I would like it if you spelled it out even more. I am not familiar with all the ADB shell commands, so could you list the exact command for each step? That would help me out greatly, thanks!

AcidRoot said:
Correct me if I'm wrong but by 1.5 root you mean the 1.5 to 2.1 rooted update and that only works for phones running 1.5 which we already had. Now there trying to get root for the 2.1 leaks/ota. not to mention i think the 1.5 root was a PB00IMG.zip which is not for recovery.
Click to expand...
Click to collapse
He is trying to tell you that he has the old root method working on 2.1.
I know that he has done this on two devices. One fresh out the box with 2.1 and one that was updated to 2.1.
I am looking for a 2.1 Eris myself to duplicate.
I personally remember having a problem loading the root file on a 2.1 Eris, but I only tried one of them. Then I left it alone.
I think I gave up too easy when I was told that it could not be done with that file.

Exactly I was told it could not be done.
What happend was the one out of box I ended up launching the Root with out checking if it was 1.5 or 2.1 When the phone wouldnt reboot after trying to root i wiped the handset. It loaded after some time like 15 mins. I looked for the Superuser program and it wasnt installed.
Ended up checking software version it was 2.1. A little fustrated I ran my script for cricket WITCH REQUIRES ROOT.
It rebooted the phone and what did i notice my **** was on the phone without root. So i thought. I check adb shell and i got the #. So i hit up installing recovery and i was able to install it so i install the official 2.1 with root rom to get the superuser apk on the phone.

amoamare said:
Exactly I was told it could not be done.
What happend was the one out of box I ended up launching the Root with out checking if it was 1.5 or 2.1 When the phone wouldnt reboot after trying to root i wiped the handset. It loaded after some time like 15 mins. I looked for the Superuser program and it wasnt installed.
Ended up checking software version it was 2.1. A little fustrated I ran my script for cricket WITCH REQUIRES ROOT.
It rebooted the phone and what did i notice my **** was on the phone without root. So i thought. I check adb shell and i got the #. So i hit up installing recovery and i was able to install it so i install the official 2.1 with root rom to get the superuser apk on the phone.
Click to expand...
Click to collapse
version 1.47 or 1.49?

amoamare said:
Exactly I was told it could not be done.
What happend was the one out of box I ended up launching the Root with out checking if it was 1.5 or 2.1 When the phone wouldnt reboot after trying to root i wiped the handset. It loaded after some time like 15 mins. I looked for the Superuser program and it wasnt installed.
Ended up checking software version it was 2.1. A little fustrated I ran my script for cricket WITCH REQUIRES ROOT.
It rebooted the phone and what did i notice my **** was on the phone without root. So i thought. I check adb shell and i got the #. So i hit up installing recovery and i was able to install it so i install the official 2.1 with root rom to get the superuser apk on the phone.
Click to expand...
Click to collapse
What was the boot screen like? The Green Android people that wave at you or the HTC "quietly brilliant" screen

Holy **** It works!

I dont remember boot screen.
as far as version 1.47 or 1.49
Im not sure what your asking here, version of the PBIMG i used ?

amoamare said:
I dont remember boot screen.
as far as version 1.47 or 1.49
Im not sure what your asking here, version of the PBIMG i used ?
Click to expand...
Click to collapse
No when you took the phone out of the box and started it for the first time after the green androids on skate boards did little green android guys wave or did you get the htc quietly brillant

amoamare said:
I dont remember boot screen.
as far as version 1.47 or 1.49
Im not sure what your asking here, version of the PBIMG i used ?
Click to expand...
Click to collapse
HBOOT version I believe.

PusherRobot said:
Holy **** It works!
Click to expand...
Click to collapse
Hey man, what are the commands you used? I pushed PB00IMG.zip to the sdcard, but when I do > adb reboot recovery , it simply restarts and shows that phone icon with the red triangle over it. When I manually pressed power and volume down, the same error as always occurs (version is older). What am I doing wrong?

amoamare said:
I dont remember boot screen.
as far as version 1.47 or 1.49
Im not sure what your asking here, version of the PBIMG i used ?
Click to expand...
Click to collapse
Well congratulations, you found a bass ackwards way to root a phone with a (more than likely) 1.47 bootloader. We've had it for months, welcome to the party. Although, You're a little late...

Unlock Problem: Permission Denied??

I have my device bridged and it says its connected and recognized when I run ADB. When I try to run the Script it says the following:
Failed to copy /efs/nv_data.bin Permission: Denied
*Error Unable to find file <.\nv_data.bin>
Could not find C:\Documents and Settings\1\Desktop\Generate Unlock Windows\nv_data.bin
If anyone could help that would be greatly appreciated.
It is on JFD stock, which I rooted from JF16 using Odin.
I have installed all the drivers as well, and I have it on debug mode.

If I root the phone, will that work?
Also, what are some good programs to copy the EFS folder?
Sorry for all the questions.

I'm fairly certain you have to be rooted

I am rooted as of 10 mins ago.
I tried to unlock it and I still got the same thing.
It says Permission Denied
Anyone have any ideas?

Does anyone know how to get SU permission?
I am trying to pull that nv_data.bin
But it says I do not have permission.

molson24 said:
Does anyone know how to get SU permission?
I am trying to pull that nv_data.bin
But it says I do not have permission.
Click to expand...
Click to collapse
in Terminal?
type:
su
(and hit enter)
before the command that needs superuser permission.

Also you probably would be better off just pulling the whole efs folder.

molson24 said:
I have my device bridged and it says its connected and recognized when I run ADB. When I try to run the Script it says the following:
Failed to copy /efs/nv_data.bin Permission: Denied
*Error Unable to find file <.\nv_data.bin>
Could not find C:\Documents and Settings\1\Desktop\Generate Unlock Windows\nv_data.bin
If anyone could help that would be greatly appreciated.
It is on JFD stock, which I rooted from JF16 using Odin.
I have installed all the drivers as well, and I have it on debug mode.
Click to expand...
Click to collapse
for permission denied try this:
open terminal emulator on your phone (download it from the market if you dont have it yet)
or you can type "adb shell" without quotations into the dos prompt and do it from there.
and type:
su
chmod 777 /efs/nv_data.bin
exit
exit
then in the dos prompt try:
adb pull /efs
or if you just want nv_data.bin:
adb pull /efs/nv_data.bin
if you need further help, this was written for the 19000 but it should help you anyways.
http://www.communityhosting.net/sgsunlock/i9000.html

You need to copy your nv_data.bin from your phone to your pc
You should see a folder made in the repair_nv_data folder like this Sauverarde_efs_apres_reparation
Move your nv_data.bin there along with nv_data.binvierge and repairation_nv_data.jar and Step2 and Step 4
Run Step 2 again and then Step 4 after its done creating the new nv_data.bin
I can't remember but I think you have to delete nv_data.md5 and a few others from your phone first

Thanks for the help boys!
The phone is now unlocked, it took the whole night, but I finally got it.
Ended up using this method here
http ://www.communityhosting.net/sgsunlock/
Worked fine, but theres alot of steps you have to follow, so it just takes time.
The reason I was having problems with the SU permission, was because the phone screen always shuts off after a few seconds or w/e and I never saw the pop up asking to accept the SU Permission. lol

molson24 said:
Thanks for the help boys!
The phone is now unlocked, it took the whole night, but I finally got it.
Ended up using this method here
http ://www.communityhosting.net/sgsunlock/
Worked fine, but theres alot of steps you have to follow, so it just takes time.
The reason I was having problems with the SU permission, was because the phone screen always shuts off after a few seconds or w/e and I never saw the pop up asking to accept the SU Permission. lol
Click to expand...
Click to collapse
lol yeah I can see that happening
I've accidently denied su permission a few times myself even when I do notice the pop up
well congrats!

Thanks Dude!!
The only weird thing that is happening is that when I am connected on wifi... My downloads dont seem to be working really... They worked for 20 mins... And then I tried at a few mins later and it says download starting and dosent do anything. I can browse the internet fine and I am connected so I am not really sure.
Also, If I am still in JFD stock, If I were to flash it again with JFK with Odin, would this lock the phone back up again? Or If I were to flash it back from J16 to JFD, would it still be unlocked?
I am not sure, but I am thinking I reload JFD again, and root it again, then maybe the downloads will work properly. Any thoughts?

molson24 said:
Thanks Dude!!
The only weird thing that is happening is that when I am connected on wifi... My downloads dont seem to be working really... They worked for 20 mins... And then I tried at a few mins later and it says download starting and dosent do anything. I can browse the internet fine and I am connected so I am not really sure.
Also, If I am still in JFD stock, If I were to flash it again with JFK with Odin, would this lock the phone back up again? Or If I were to flash it back from J16 to JFD, would it still be unlocked?
I am not sure, but I am thinking I reload JFD again, and root it again, then maybe the downloads will work properly. Any thoughts?
Click to expand...
Click to collapse
Unlocking should not break your downloads (At least I've never heard of it happening) but you'll be fine flashing any rom you like, without having to unlock again.
are you still on t-mobile just unlocked?
orare you on a different carrier now that your unlocked?
the main things to be careful of when flashing roms is:
be careful going from froyo (2.2 JK2/JK6) back to eclair (2.1 JFD/JI6) its a little tricky, but not too bad.
and be careful with lag fixes, if you use one always disable it before flashing. (I never found them very useful myself anyways)
going from JFD to JI6 and back should be fine though.
if you want a completly clean slate then you can use Odin and it still wont re-lock your phone.
you might even find that you like some of the roms out there better than the stock one
I know I did.

[Q] When I click attempt permroot, nothing happens....

I did the gfree way to get S=off... everything work but the last step
"12. If this is the first time you have rooted your device you will need to run visionary again (temproot w/set system r/w after root checked and then attempt permroot) to make root privileges permanent and then reboot again. Now "su" should work properly for you."
When I click attempt permroot, nothing happens.... everything else works... when I type SU ... I have access, can I be permanent root with out actually clicking attempt permroot.... is there another way to tell
Thanks... I just got my mytouch and I want to put MIUI ROM on it

just reboot the phone, and then open terminal emulator. type su
if you get root, your good to go

option94 said:
just reboot the phone, and then open terminal emulator. type su
if you get root, your good to go
Click to expand...
Click to collapse
By "root"
you mean "#"
Thats what I get...#
So I'm ok... I just installed clockworkmod recovery... so now I'm looking for MIUI ROM....which one do I pick?

I haven't really followed miui dev much. I believe both are pretty stable. Just read through the threads, especially the OP's and the last few pages to get an idea, and pick whichever one sounds best to you.