Develop Bugs

Tried to Root G2 (S-ON)

If on Recovery, it says S-ON, is that a Problem?

triumphantpower said:
If on Recovery, it says S-ON, is that a Problem?
Click to expand...
Click to collapse
If it says S-ON, you don't have permaroot. Did you follow the guide in the wiki?
Sent from my T-Mobile G2 using XDA App

I watched a Video from BlackPrince310. I got far into it, until I had to use the Terminal. I'm not sure what Wiki are you talking about.. Link?
(Thank You for the speedy reply btw)

triumphantpower said:
I watched a Video from BlackPrince310. I got far into it, until I had to use the Terminal. I'm not sure what Wiki are you talking about.. Link?
(Thank You for the speedy reply btw)
Click to expand...
Click to collapse
YouTube *really* shouldn't be the go to for things like this, unless you like bricks. This guide is by the folks who actually engineered the hack: http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
Sent from my T-Mobile G2 using XDA App

oh alright, Thank You OriginalGabriel.
But is rage an adb command or an app from the Market?

and where would the HTC G2 Drivers have to be installed?

triumphantpower said:
and where would the HTC G2 Drivers have to be installed?
Click to expand...
Click to collapse
If you've used adb (eg. you have the SDK installed on your computer), then you have the drivers already installed. Otherwise, unzip the file and when you plug your computer into your phone, point the hardware wizard to the folder that you unzipped
Rage is an included binary in gfree_temp-root.zip

Got it Thank You.
I got to where I have to use ADB, and while trying to $ adb push su /sdcard/su
It won't let allow me, it'll say access denied. (I've even put adb shell before that command)

I type in adb shell:
*daemon not running. starting it now on port 5037*
*daemon started successfully* and then any other command I type after that is Denied

triumphantpower said:
I type in adb shell:
*daemon not running. starting it now on port 5037*
*daemon started successfully* and then any other command I type after that is Denied
Click to expand...
Click to collapse
on your phone be sure you have menu>settings>applications>development>usb debugging checked (on)

I do. Using this Tutorial: http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
I got all the way to the Permaroot Section. When I have to issue these commands:
# cd /data/local
# chmod 777 gfree
# ./gfree -f
#sync
my phone reset before I got to type sync.
And before I got the chance to type the next lines of text, I had to turn on my phone issued them and got an error message of file exists and something else. I Booted my phone and it still says SHIP S-ON

triumphantpower said:
I do. Using this Tutorial: http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
I got all the way to the Permaroot Section. When I have to issue these commands:
# cd /data/local
# chmod 777 gfree
# ./gfree -f
#sync
my phone reset before I got to type sync.
And before I got the chance to type the next lines of text, I had to turn on my phone issued them and got an error message of file exists and something else. I Booted my phone and it still says SHIP S-ON
Click to expand...
Click to collapse
After you do the temp root, shut down adb (I am using a windows machine so I ctrl alt del and find it in task manager and shut it down that way) It should restart by itself when you do the perm root commands. ( you probably know this, but don't enter the # sign, it should be there by itself)

Thank You sooo much! I got the S-Off now finally, thank you very much!
Is there anything else I should do before I decided to Install a Custom ROM? Can I install a ROM from this Recovery? or Do I need to do a further step. According to the Tutorial I have Perm Root now but I've never used this Recovery before

triumphantpower said:
Thank You sooo much! I got the S-Off now finally, thank you very much!
Is there anything else I should do before I decided to Install a Custom ROM? Can I install a ROM from this Recovery? or Do I need to do a further step. According to the Tutorial I have Perm Root now but I've never used this Recovery before
Click to expand...
Click to collapse
Download ROM manager from the market, spend the few bucks for the upgrade and then install clockworkmod recovery through ROM Manager (if you haven't done this already). Then, do some more reading about doing a Nandroid backup and you're ready to go! Now, the fun begins....lol!

I don't mind buying ROM Manager Premium but can I do that with the Free Version? I downloaded the Free Version of ROM Manager v3.0.0.7 and when I selected Flash Clockwork Mod Recovery it gave me "an error occurred while attempting to run privileged commands!". Does the Paid Version go past that or am I missing something?

triumphantpower said:
I don't mind buying ROM Manager Premium but can I do that with the Free Version? I downloaded the Free Version of ROM Manager v3.0.0.7 and when I selected Flash Clockwork Mod Recovery it gave me "an error occurred while attempting to run privileged commands!". Does the Paid Version go past that or am I missing something?
Click to expand...
Click to collapse
do you have the superuser app now in your applications drawer?
edit: Also, disconnect the phone from the USB. That might give ROM manager a problem accessing your sd card if you're still connected.

yeah I have Superuser Permissions but it FC's when you try to open it

triumphantpower said:
yeah I have Superuser Permissions but it FC's when you try to open it
Click to expand...
Click to collapse
Try uninstalling ROM Manager and after that see if you still get a force close when you try to open Superuser.

Interesting Idea. I tried it, and still the same. Superuser FC's @[email protected]

triumphantpower said:
Interesting Idea. I tried it, and still the same. Superuser FC's @[email protected]
Click to expand...
Click to collapse
what happens when, in ROM Manager, you select "fix permissions"?

[MOD]NOOBS Flash the Eng 85 H-Boot and CWM 5 the easy way!!!S-OFF ONLY(UPDATED 2/04)

Hey All,
Here are some PD15IMG varients. This is great for noobs who are unsure about flashing the engineering boatlader wich is highly RECOMMENDED as well as a custom recovery. Once you have achieved s-off use this file to continue your rooting process. Again this only works for those of you that currently have S-OFF!!!!
You may ask why do I need an engineering bootloader the answer is you technically don't. However, it can be your last line of defense against a soft brick and is strongly suggested by any experienced modder!!!
I have included 3 separate downloads. The first file contains ClockworkMod and the engineering bootloader. I did not offer a separate file containing just CWM 5 or just the bootloader due to a few reasons. One being I believe everybody should have the Eng. bootloader and second being this offers a true flash of a custom recovery where Rom Manager does not. If you would like just one or the other open up the zip file and delete the desired file. The second file is the most recent update offered from T-Mobile. That file will give you the update unrooted and as it is intended from T-Mobile. However, it will give you an eng bootloader with CWM 5 instead of the locked bootloader and stock recovery. Allowing you to return to another rom or previous nandroid backup. The third file is for if you ever want to go back to a stock splash image or yours begins to fail. Finally, I also added thee new ClockworkMod touch recovery with the eng bootloader for the last file.
I am not responsible for anything that may happen to your device please proceed at your own risk. I have tested this myself and it works just fine. However, if something were to happen to your device don't blame me
1.Download which file you want
2. Rename it to PD15IMG and place on the root of your SD card
3. If using the second file make a nandroid backup first.
4. Boot into H-boot and apply the update (by holding volume down and powering on the phone)
5. Once the update has finished either re-rename the file to something different or delete it from the sd card otherwise you will keep installing the update
AGAIN THIS IS FOR S-OFF ONLY​
BLINGO BLAMO You now can either flash your favorite rom or restore a previous nandroid backup
The downloads
This file contains the new ClockworkMod 5.0.2.0 and the Eng H-Boot 85.2007
http://dl.dropbox.com/u/69550670/PD15IMG_eng_hboot_.zip
This file contains the Mysense update, Eng H-boot 85.2007 and ClockworkMod 5.8.1.0
http://dl.dropbox.com/u/69550670/PD15IMG_eng_hboot_touch_Recent_update.zip
THIS 2nd FILE WILL ERASE ALL FILES AND DATA ON YOUR PHONE
This File contains the original T-Mobile splash image (teejay this is for you lol)
http://dl.dropbox.com/u/69550670/PD15IMG_Splash_.zip
This file contains the ClockworkMod 5.8.1.0 TOUCH recovery along withe the Eng H-boot 85.2007
http://dl.dropbox.com/u/69550670/PD15IMG_eng_hboot_touch.zip
I hope this helps some of you out and relieves those headaches you had!!!!​

So this flashes the engineering bootloader, the latest ClockworkMod recovery, and the OTA Gingerbread ROM all in one shot? I've never heard of such a package, pretty cool! :thumbs up:
EDIT: I read it again, and apparently it's just the bootloader and recovery. Still pretty cool!

TeeJay3800 said:
So this flashes the engineering bootloader, the latest ClockworkMod recovery, and the OTA Gingerbread ROM all in one shot? I've never heard of such a package, pretty cool! :thumbs up:
EDIT: I read it again, and apparently it's just the bootloader and recovery. Still pretty cool!
Click to expand...
Click to collapse
It flashes the ota too, no root tho
Gonna add adb shell root to it tomorrow too
Sent from my Google Nexus 12! yup I'm from the future

Crazy but my root stayed after flashing new radio am u jus lucky or somethin
Sent from my HTC Glacier using XDA Premium App

mjeezy13947 said:
Crazy but my root stayed after flashing new radio am u jus lucky or somethin
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
flashing a radio doesnt affect root

You're welcome, glad to help propose the idea.
How about a second version that flashes only the ENG HBOOT & CWM but leaves data/system as-is? That might also be useful for some folks.

Ah excellent, I see you edited a second version into the top post.
I will keep this method in mind any time I see someone ask the same question about an HTC phone with S-OFF. It all seems to work the same once security is removed.

mark manning said:
Hey All,
I have a fix that brings the .85.2007 Engineering bootloader as well as Clockwork mod 3.0.2.4 to those of you who are stuck without root on the new 2.3 mysense build. This is also great for noobs who are unsure about flashing the engineering boatlader wich is highly RECOMMENDED as well as a custom recovery. Once you have achieved s-off use this file to continue your rooting process. Again this only works for those of you that currently have S-OFF!!!!
I am not responsible for anything that may happen to your device please proceed at your own risk. I have tested this myself and it works just fine. However, if something were to happen to your device don't blame me
1.Download which file you want
2. Rename it to PD15IMG and place on the root of your SD card
3. Boot into H-boot and apply the update (by holding volume down and powering on the phone)
AGAIN THIS IS FOR S-OFF ONLY​
BLINGO BLAMO You now can either flash your favorite rom or restore a previous nandroid backup
Thank you cmstlist for pointing me in the right direction and Bin4ry in the sensation forum for coming up with the mod, all I did is take his idea and apply it to our phone.
Bin4ry's original thread
http://forum.xda-developers.com/showthread.php?t=1122053
The downloads
This file is just the 85.2007 Eng H-boot and Clockworkmod 3.0.2.4
http://www.megaupload.com/?d=2TYRGS5J
This file contains the Mysense leak, Eng H-boot 85.2007 and Clockworkmod 3.0.2.4
http://www.megaupload.com/?d=JIJZI39L
THIS 2nd FILE WILL ERASE ALL FILES AND DATA ON YOUR PHONE
I hope this helps some of you out and relieves those headaches you had!!!!​
Click to expand...
Click to collapse
I'm sorry to be so dense but can you tell me how to:
"3. Boot into H-boot and apply the update"
i thought i needed the eng bootloader to apply updates
I understand that i can enter hboot by starting up while holding [power] + [volume down], but beyond that do i choose fastboot or recovery or image crc or what?
Thank you for your patience! You have been super helpful and generous!

crouchingpossum said:
I'm sorry to be so dense but can you tell me how to:
"3. Boot into H-boot and apply the update"
i thought i needed the eng bootloader to apply updates
I understand that i can enter hboot by starting up while holding [power] + [volume down], but beyond that do i choose fastboot or recovery or image crc or what?
Thank you for your patience! You have been super helpful and generous!
Click to expand...
Click to collapse
You do not need the Eng bootloader just s-off. Once you rename the file and it is on the root of your sd card. Power off the phone and turn it back on holding volume down. The phone will the check for the file and prompt you asking if you want to apply the update. To say yes you then press the volume up button and the phone does the rest. This will give you the clockworkmod custom recovery and the engineering bootloader
Sent from my Google Nexus 12! yup I'm from the future

Might be helpful to reiterate: after you've successfully applied the zip, rename or delete the file from your SD so you don't accidentally apply it multiple times.
Sent from my Nexus One using Tapatalk

How would I know if I ask ready have the engineer bootloader?
Sent from my HTC Glacier using XDA Premium App

bmakk2055 said:
How would I know if I ask ready have the engineer bootloader?
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
Check the number in bootloader to see which you have...where it says spl at the top.
Sent from myTouch 4G

TYSVM for your help,
I feel ashamed to ask for more help but i am stuck again
i suppose i am an ADB sdk noob,
I ran the pd15img.zip successfully then I went to load CM7 following the sdk directions here:
http://wiki.cyanogenmod.com/wiki/TMobile_myTouch_4G:_Full_Update_Guide#Method_via_ROM_Manager
(great easy to follow command line tutorial, thanks so much!)
but i am stuck again :
after:
"... Make sure USB debugging is enabled on the TMobile myTouch 4G by checking Settings » Applications » Development » USB debugging.
6. On the computer, open terminal and run the following commands:
adb push busybox /data/local/tmp/
adb push gfree /data/local/tmp/
adb push hboot-eng.img /data/local/tmp/
adb push psneuter /data/local/tmp/
adb push recovery-clockwork-3.0.2.4-glacier.img /data/local/tmp/recovery.img
adb push root_psn /data/local/tmp/
adb push su /sdcard/
adb push Superuser.apk /sdcard/
adb shell
chmod 755 /data/local/tmp/*
/data/local/tmp/psneuter
..."
I typed:
[adb push Superuser.apk /sdcard/
it replied: (1596 KB/s (196120 bytes in 0.120s)]
<- great success, everything moving along as planned
BUT:
I typed:
adb shell
$ chmod 755 /data/local/tmp/*
/data/local/tmp/psneuter
AND: Oh No!
unable to
chmod 755 /data/local/tmp/*
/data/local/tmp/psneuter: no such file or directory
Did i miss a step? I don't understand ; i see psneuter and psneuter.c files in the directory platform tools ...
what is chmod command, btw?
do i need to link this file to the shell or something?
I'm afraid to do anything with the phone while I'm halfway through this process, i apologize for being so very needy, but I'm super grateful for your taking the time to noob me thru this,
i promise I'll do my best to share my knowledge with the next poor noob when this is all said and done,
peace,
possum

crouchingpossum said:
TYSVM for your help,
I feel ashamed to ask for more help but i am stuck again
i suppose i am an ADB sdk noob,
I ran the pd15img.zip successfully then I went to load CM7 following the sdk directions here:
http://wiki.cyanogenmod.com/wiki/TMobile_myTouch_4G:_Full_Update_Guide#Method_via_ROM_Manager
(great easy to follow command line tutorial, thanks so much!)
but i am stuck again :
after:
"... Make sure USB debugging is enabled on the TMobile myTouch 4G by checking Settings » Applications » Development » USB debugging.
6. On the computer, open terminal and run the following commands:
adb push busybox /data/local/tmp/
adb push gfree /data/local/tmp/
adb push hboot-eng.img /data/local/tmp/
adb push psneuter /data/local/tmp/
adb push recovery-clockwork-3.0.2.4-glacier.img /data/local/tmp/recovery.img
adb push root_psn /data/local/tmp/
adb push su /sdcard/
adb push Superuser.apk /sdcard/
adb shell
chmod 755 /data/local/tmp/*
/data/local/tmp/psneuter
..."
I typed:
[adb push Superuser.apk /sdcard/
it replied: (1596 KB/s (196120 bytes in 0.120s)]
<- great success, everything moving along as planned
BUT:
I typed:
adb shell
$ chmod 755 /data/local/tmp/*
/data/local/tmp/psneuter
AND: Oh No!
unable to
chmod 755 /data/local/tmp/*
/data/local/tmp/psneuter: no such file or directory
Did i miss a step? I don't understand ; i see psneuter and psneuter.c files in the directory platform tools ...
what is chmod command, btw?
do i need to link this file to the shell or something?
I'm afraid to do anything with the phone while I'm halfway through this process, i apologize for being so very needy, but I'm super grateful for your taking the time to noob me thru this,
i promise I'll do my best to share my knowledge with the next poor noob when this is all said and done,
peace,
possum
Click to expand...
Click to collapse
All of that is unnecessary, sounds like you want cm7 so just download it boot into recovery and install it.
The pd15img takes care of most of that and if you install a custom rom it will already have root
Sent from my Google Nexus 12! yup I'm from the future

Ace42 said:
Check the number in bootloader to see which you have...where it says spl at the top.
Sent from myTouch 4G
Click to expand...
Click to collapse
I don't see spl, I see hboot_0.86.0000. I used halfcab root method
Sent from my HTC Glacier using XDA Premium App

bmakk2055 said:
I don't see spl, I see hboot_0.86.0000. I used halfcab root method
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
Dies it say S-OFF OR S-ON?
Sent from my Google Nexus 12! yup I'm from the future

mark manning said:
Dies it say S-OFF OR S-ON?
Sent from my Google Nexus 12! yup I'm from the future
Click to expand...
Click to collapse
I have s off
Sent from my HTC Glacier using XDA Premium App

bmakk2055 said:
I have s off
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
Then apply my image and you'll have the eng bootloader
Sent from my Google Nexus 12! yup I'm from the future

mark manning said:
Then apply my image and you'll have the eng bootloader
Sent from my Google Nexus 12! yup I'm from the future
Click to expand...
Click to collapse
What does the eng bootloader does exactly, I'm using virtuous unity
Sent from my HTC Glacier using XDA Premium App

bmakk2055 said:
I don't see spl, I see hboot_0.86.0000. I used halfcab root method
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
My bad it's hboot, but it contains the spl that manages the phone, sorry for the mix up.
Sent from myTouch 4G

[HOWTO] Root Your Stock Galaxy Nexus

This post is now deprecated there are new ways of rooting more easily here is the link to one of those
http://forum.xda-developers.com/showthread.php?t=1392310
just kept for reference
link no longer works as it is a very old boot img, if you wanna go this way use latest superboot
Rooting your Galaxy Nexus
Download this file contains necessary files and also lastest samsung drivers in case you dont have them, probably you need android sdk drivers for fastboot
Download
credit to @peteralfonso for the insecure boot.img which allows this to remount system and this way install su binary and Superuser.apk
This are the instructions for Galaxy Nexus
they require basic knowledge of fastboot adb and using command prompt/terminal
works same way on linux and windows
Be sure to have fastboot and adb ready and working
extract somewhere and you will get 4 files su, Superuser.apk , boot.img and drivers
turn off the phone
Boot into bootloader mode (Vol UP+ Vol Down + Power) then execute this command, be sure to have fastboot and boot.img on same folder or be ready to type a long path pointing to your boot.img
REMINDER: by doing fastboot oem unlock you will completely wipe your device so be sure to backup anything important
execute this command
Code:
fastboot oem unlock
fastboot boot boot.img
edit: thanks chirality forgot the oem unlock
the device will reboot and start in unsafe mode where you can enable adb as root usually on production devices this is not posible
Be sure to enable adb debugging on menu
back to command prompt
Code:
adb root
adb remount
adb push su /system/bin
adb push Superuser.apk /system/app
adb shell chmod 06755 /system/bin/su
adb shell chmod 06755 /system/app/Superuser.apk
adb reboot
and you are done and youve got your Galaxy Nexus rooted
This process does not involve flashing another boot.img, it just boots once with it and after that returns to original boot.img
As usual
YOU ARE PERFORMING THIS AT YOUR OWN RISK! I AM NOT RESPOSIBLE FOR ANY BRICKS OR PROBLEMS!
Which wont happen we are just pushing 2 files to our phone
edit2: sorry for the bad paths of adb was too late and didnt notice my error

Don't you have to do "fastboot oem unlock" first before being able to boot off the insecure image? I thought they fixed that with the Nexus S already.

Thanks for the post - apparently people are having problems with the Superboot method, so I'll give this a go when mine arrives today.
I guess this comes with all the usual "at your own risk" and "will void your warranty" warnings?
(sorry if that's a stupid question - this is my first Nexus, so I'm not sure where I stand on rooting, unlocking bootloaders, and the warranty etc.)

Great - worked without issue for me and I can now use the Entree VPN client for connecting into work. (the HD screen is great for remote desktop work)
Minor typo in the permissions lines though - should read:
adb shell chmod 06755 /system/bin/su
adb shell chmod 06755 /system/app/Superuser.apk
Thanks very much,
Chris.

Thanks for this davioxx for putting together the guide, chriscole for the fixes and @peteralfonso for the insecure boot.img.
I'm now succesfully rooted.
It seems Root Explorer needs an update for the GN though. Only opens in the bottom left corner of the screen for me, and is comprised of static.

Sorry for the newbee question, been quite a while since rooting my nexus one...
Do i need to enable adb debugging on phone menu before executing the fastboot oem unlock code and then enable it again after it reboots and starts in safe mode?

w00t!
Thank you
You may want to change the path names on the chmod part, I blindly followed the instructions and the files were in diffrent places from where I pushed them to
But thanks \o/
I haz root!

Tnx, easy like all nexus devices, now need some you tube for that!
Sent Via My HTC Desire HD

looks pretty simple ... hopefully it will be the same process for us in the States

Not 100% sure what's going on here. I haven't rooted since I got the Nexus One.
When my phone is on and connected, command prompt shows my phone as an attached device. But when I boot into bootloader, it isn't attached anymore and command prompt just tells me that the commands are unrecognized? How come?

majikdragoon said:
Not 100% sure what's going on here. I haven't rooted since I got the Nexus One.
When my phone is on and connected, command prompt shows my phone as an attached device. But when I boot into bootloader, it isn't attached anymore and command prompt just tells me that the commands are unrecognized? How come?
Click to expand...
Click to collapse
Are you doing it via adb or fastboot?

Not sure. I restarted the phone into bootloader and tried to follow the instructions
Hahaha... I was trying to sideload N64oid as it's been removed from the market. I ended up using Android Centrals Sideloader instead.

majikdragoon said:
Not sure. I restarted the phone into bootloader and tried to follow the instructions
Hahaha... I was trying to sideload N64oid as it's been removed from the market. I ended up using Android Centrals Sideloader instead.
Click to expand...
Click to collapse
Hi probably you dont have the bootloader driver installed, that has to be done manually at least for my win 64 machine, check this thread about that
Set Up ADB, fastboot and drivers Nexus S it is practically the same for your Galaxy Nexus

Oh ok! I'll look at that now. Thanks fellas

Why couldn't you just....
Fastboot OEM unlock
Fastboot flash recovery
Flash su zip in recovery
(obviously, I'm omitting some steps here like after Fastboot flashing recovery, booting into recovery...ect)
Unless there isn't a custom recovery available yet...
That's how I rooted BOTH the N1 and NS....
Sent from my HTC Sensation 4G using xda premium until I can get the Galaxy Nexus on T-Mobile

there isnt a custom recovery yet and stock recovery needs signed recoveries
actually not hard you take 3 mins in all process
Babydoll25 said:
Why couldn't you just....
Fastboot OEM unlock
Fastboot flash recovery
Flash su zip in recovery
(obviously, I'm omitting some steps here like after Fastboot flashing recovery, booting into recovery...ect)
Unless there isn't a custom recovery available yet...
That's how I rooted BOTH the N1 and NS....
Sent from my HTC Sensation 4G using xda premium until I can get the Galaxy Nexus on T-Mobile
Click to expand...
Click to collapse

Babydoll25 said:
Unless there isn't a custom recovery available yet...
Click to expand...
Click to collapse
Ding ding ding.
Also some people don't want to flash a custom recovery anyway.
Sent from my Nexus S using XDA App

Drivers
Does anyone know where else to get the drivers from? installed the ones attached but when i go into device manager, i am seeing android.1 and when type "fastboot devices" nothing comes up

coleburns said:
Does anyone know where else to get the drivers from? installed the ones attached but when i go into device manager, i am seeing android.1 and when type "fastboot devices" nothing comes up
Click to expand...
Click to collapse
How I got fastboot working was to install pdanet, one of the steps is to install all the drivers. It doesn't matter if it fails after that step, I didn't want pdanet anyways
The ones attached seem to only be for adb mode.
Sent from my Galaxy Nexus using xda premium

el3ctrik said:
How I got fastboot working was to install pdanet, one of the steps is to install all the drivers. It doesn't matter if it fails after that step, I didn't want pdanet anyways
The ones attached seem to only be for adb mode.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
thanks for that, managed to get it working with pdanet.
however when i try to run the adb commands, i get the adbt cannot run as root in production builds
how did you get rooted?
thanks

Kindle Fire 6.3 root

Warning
Below be dragons, please gather armor and basic computing knowledge before preceding </ubergeek>. Working adb AND fastboot are requires, support for adb and fastboot are NOT offered by me. If you question is related to OSX or Linux I may be able to help. If it is windows related, don't get pissed when I tell you "I have no idea", it is the truth.
This is at your own risk! Do not blame me if something goes wrong!
For 6.2, 6.2.1 and 6.2.2 please see BurritoRoot3 -> http://rootzwiki.com/topic/13027-rootbootloader-burritoroot3-kindle-fire-root-easy-root-edition/
While I have another root exploit, Amazon neglected pokey's far more beautiful one this update, and we have no good reason to blow another root for this update, so isntead here is a guide using fbmode.
Full credits for this goes to pokey9000 (see http://forum.xda-developers.com/showthread.php?t=1414832). This guide requires you to have adb and fastboot working FOR THE KINDLE FIRE, on whatever os you are on.
Required files:
fbmode.zip - http://forum.xda-developers.com/showthread.php?t=1414832
twrp2 - http://teamw.in/project/twrp2/79
su - http://dl.dropbox.com/u/8699733/kindlefire/su
firefirefirefire http://forum.xda-developers.com/showthread.php?t=1369405
fastboot + adb for your OS of choice.
unzip fbmode.zip
adb push fbmode /data/local/fbmode
adb shell chmod 755 /data/local/fbmode
adb shell /data/local/fbmode
adb reboot
Your kindle will "get stuck" on the kindle fire screen, but really it's just in fastboot mode.
fastboot -i 0x1949 flash bootloader <name of firefirefire image here>
fastboot -i 0x1949 flash recovery <name of recovery image here>
Your device will now boot into twrp recovery, and flash the firefirefire bootlaoder. When done it will prompt you to reboot. Upon reboot you will get stuck on the "yellow triangle" screen of firefire fire.
fastboot oem idme bootmode 5002
fastboot reboot
Once in recovery
adb shell mount system
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
Lets disable the root check before rebooting
adb shell mv /system/bin/check_rooted /system/bin/check_rooted.bak
adb shell idme bootmode 4000
adb reboot
Once booted into Android, install superuser
adb install Superuser.apk

So this is strictly to add root for someone who is running stock 6.3, correct?
Thanks for the write up.

Once again! You rule.

Your fast! I was gonna suggest pokeys bootmodes before tossing an exploit but u went straight for it lol. Great work jcase
Sent from my Kindle Fire using xda premium

kernelsandirs said:
Once again! You rule.
Click to expand...
Click to collapse
It's pokey's not mine, I just posted up a guide to stop ppl from asking me

smirkis said:
Your fast! I was gonna suggest pokeys bootmodes before tossing an exploit but u went straight for it lol. Great work jcase
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
I flashed back to stock and updated. My "secondary" exploit still exists, but after getting root I decided to check and see if fbmode would still work, and it does.
So we should be good for the next one as well.

Quick question you wonderful people,
Does this work with kinfauns 1.3 firefirefire?
It's basically just pokey9000's with some quirks and a different boot menu but figured I would ask the "big guys" first before I turn into one of those "I bricked my fire" folks. Cheers.

Laquox said:
Quick question you wonderful people,
Does this work with kinfauns 1.3 firefirefire?
It's basically just pokey9000's with some quirks and a different boot menu but figured I would ask the "big guys" first before I turn into one of those "I bricked my fire" folks. Cheers.
Click to expand...
Click to collapse
should work with anything

Wow, it didn't take them long to implement a root check at all. I guess more people are rooting their devices than had previously expected. They're selling them at a loss in the hopes that they will make it up in app store and prime sales. Woops. Oh well, I'm just glad I switched rooms when I did. It won't be long before they make them either unrootable (less likely) or stop selling them altogether (more likely).
Sent from my Amazon Kindle Fire using xda premium

soupmagnet said:
Wow, it didn't take them long to implement a root check at all. I guess more people are rooting their devices than had previously expected. They're selling them at a loss in the hopes that they will make it up in app store and prime sales. Woops. Oh well, I'm just glad I switched rooms when I did. It won't be long before they make them either unrootable (less likely) or stop selling them altogether (more likely).
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
no, every update has "broke" root. amazon does this so that their updates wont brick rooted devices. they haven't done anything to prevent people from rooting.

Worked fine, maybe I misread it or maybe you left out sticking superuser.apk in the adb/fastboot folder? Anywhoo I got root on 6.3 with this method, thanks

jcase said:
should work with anything
Click to expand...
Click to collapse
Indeed it does and I even re-added FFF 1.3 working like a charm. Thank you and pokey9000 for all the hard work!

Another fantastic job! Thanks so much!!

raiderep said:
Worked fine, maybe I misread it or maybe you left out sticking superuser.apk in the adb/fastboot folder? Anywhoo I got root on 6.3 with this method, thanks
Click to expand...
Click to collapse
No, I assume people setup their paths correctly during adb installation, negating the need for that.

BigFuzzyArchon said:
no, every update has "broke" root. amazon does this so that their updates wont brick rooted devices. they haven't done anything to prevent people from rooting.
Click to expand...
Click to collapse
Actually, this is the first time they have implemented something like this, its a separate service that checks for root, they run it at boot.

jcase said:
Actually, this is the first time they have implemented something like this, its a separate service that checks for root, they run it at boot.
Click to expand...
Click to collapse
they run it at boot and do what ?
would be interesting ...

Perhaps a stupid question, but where do I get the "Superuser.apk" used at the end of the instructions under 'adb install Superuser.apk'? Because It wasn't one of the files listed under needed files section. Thanks

daggy1985 said:
Perhaps a stupid question, but where do I get the "Superuser.apk" used at the end of the instructions under 'adb install Superuser.apk'? Because It wasn't one of the files listed under needed files section. Thanks
Click to expand...
Click to collapse
just google for "superuser.apk download" ...

daggy1985 said:
Perhaps a stupid question, but where do I get the "Superuser.apk" used at the end of the instructions under 'adb install Superuser.apk'? Because It wasn't one of the files listed under needed files section. Thanks
Click to expand...
Click to collapse
It's in the OP, just abbreviated as "su."
http://dl.dropbox.com/u/8699733/kindlefire/su

Droidanian said:
It's in the OP, just abbreviated as "su."
http://dl.dropbox.com/u/8699733/kindlefire/su
Click to expand...
Click to collapse
the su command and the superuser.apk are different things
the superuser.apk is a wrapper to su command

Really need help. hboot install went wrong

well the story is ive rooted the phone ages ago and i just tryed installing hboot.
when i was in the fast boot menu i always saw hboot in the titles up the top where s-off was and my radio.
well i tryed to install hboot using the terminal emulator method and i checked my MD5sums they all matched but when i turned the phone off it takes like 5 minutes to show the htc logo and it vibrates at the same time for 5 minutes or more then stops vibrating stays on the htc logo for a minute or 2 then goes to my roms boot screen and that i think is about normal boot time. it boots fine into my rom i can use it as normal.
but i cant use my 4EXT recovery or my fastboot or bootloader whatever its called.
i really need help im kicking myself for trying to install hboot just to try install a new radio so any help or suggestion would be great.
plus i originally rooted the phone using the hackkit method and i was thinking of going back to stock but because my fastboot/bootlaoder dosnt want to show i dunno what to do
im not much of a wizz at these things but i try my best

Can you boot into recovery from the rom?
Sent from a dream.

I dont think so i tried to get rom manager to boot into recovery and same with just holding the power botton and choosing it that way but i dont think it worked
Sent from my HTC Desire HD With Beats Audio using XDA

Don't think it worked? I'll take that as a no.
Link me to what you did, the hboot thing.
Sent from a dream.

kyaldearing said:
I dont think so i tried to get rom manager to boot into recovery and same with just holding the power botton and choosing it that way but i dont think it worked
Sent from my HTC Desire HD With Beats Audio using XDA
Click to expand...
Click to collapse
OK either you know it did not work or it did work which one is it. The I think it did not work just tells me you did not try it.
Sent from my Desire HD using xda premium

Im dont think it worked cause i waited 10 minutes and nothing happened so i took the battery out
and here is the link to what i did and used forum.xda-developers.com/showthread.php?t=841076
Sent from my HTC Desire HD With Beats Audio using XDA

I skimmed through the page you sent, and I do think it's fixeable. You just need to find someone more knowledgeable than myself. I don't want to recommend anything that could make things worse.
With that said, no idea what the hboot does, where it shows up and so forth. If you care to explain, maybe we can figure something out or, until someone who knows more joins in.
For the meantime, good luck.
Edit: I'm assuming hboot is the white screen before booting, which comes with the hack kit once rooted. Don't know why you wantedbto flash it again.....?
Sent from a dream.

I was going to put it back to stock.
And if no one else joins in then what should i do. If you have ideas please tell im not gonna go racing to try because whats happened but i can always keep them at the back of my mind
Sent from my HTC Desire HD With Beats Audio using XDA

Yeah you messed messed up boot loader. Flashing the eng boot on newer dhds causes issues. Here are some steps to fix it that had worked for others. Also you might want to stop in the ace hack kit irc room. They have actually helped quite a lot of people with this even though its not aahk related. Bunch of nice people there.
Note: All md5sums must be 2a28dcd53ea26504be9a86572a348aa1
let the phone fully boot. This may take 1/2 hour, and may vibrate like mad for a few minutes.
download http://tinyurl.com/6fkvepx
unzip PD98IMG-HBFX.zip to a folder you can get to from command prompt or terminal
get psneuter and gfree from hack kit, put in same folder as hboot.nb0 open command prompt and navigate to this folder
turn on usb debugging
Enter the following into the command prompt:
adb push hboot.nb0 /data/local/tmp/hboot.nb0
md5sum /data/local/tmp/hboot.nb0
adb push gfree /data/local/tmp/gfree
adb push psneuter /data/local/tmp/psneuter
adb shell chmod 777 /data/local/tmp/gfree
adb shell chmod 777 /data/local/tmp/psneuter
adb shell /data/local/tmp/psneuter
adb shell
(should have #)
/data/local/tmp/gfree -f
md5sum /data/local/tmp/hboot.nb0
dd if=/data/local/tmp/hboot.nb0 of=/dev/block/mmcblk0p18
sync
dd if=/dev/block/mmcblk0p18 of=/data/local/tmp/hboot.test
exit
adb pull /data/local/tmp/hboot.test
md5sum hboot.test
adb shell md5sum /dev/block/mmcblk0p18
adb reboot
Note: All md5sums must be 2a28dcd53ea26504be9a86572a348aa1

marsdta said:
Yeah you messed messed up boot loader. Flashing the eng boot on newer dhds causes issues. Here are some steps to fix it that had worked for others. Also you might want to stop in the ace hack kit irc room. They have actually helped quite a lot of people with this even though its not aahk related. Bunch of nice people there.
Note: All md5sums must be 2a28dcd53ea26504be9a86572a348aa1
let the phone fully boot. This may take 1/2 hour, and may vibrate like mad for a few minutes.
download http://tinyurl.com/6fkvepx
unzip PD98IMG-HBFX.zip to a folder you can get to from command prompt or terminal
get psneuter and gfree from hack kit, put in same folder as hboot.nb0 open command prompt and navigate to this folder
turn on usb debugging
Enter the following into the command prompt:
adb push hboot.nb0 /data/local/tmp/hboot.nb0
md5sum /data/local/tmp/hboot.nb0
adb push gfree /data/local/tmp/gfree
adb push psneuter /data/local/tmp/psneuter
adb shell chmod 777 /data/local/tmp/gfree
adb shell chmod 777 /data/local/tmp/psneuter
adb shell /data/local/tmp/psneuter
adb shell
(should have #)
/data/local/tmp/gfree -f
md5sum /data/local/tmp/hboot.nb0
dd if=/data/local/tmp/hboot.nb0 of=/dev/block/mmcblk0p18
sync
dd if=/dev/block/mmcblk0p18 of=/data/local/tmp/hboot.test
exit
adb pull /data/local/tmp/hboot.test
md5sum hboot.test
adb shell md5sum /dev/block/mmcblk0p18
adb reboot
Note: All md5sums must be 2a28dcd53ea26504be9a86572a348aa1
Click to expand...
Click to collapse
I tryed to boot into recovery and it worked took a while but happened and im not a wizz with this so i kinda need a nood version of this method and what its a complete boot
Sent from my HTC Desire HD With Beats Audio using XDA

kyaldearing said:
I tryed to boot into recovery and it worked took a while but happened and im not a wizz with this so i kinda need a nood version of this method and what its a complete boot
Sent from my HTC Desire HD With Beats Audio using XDA
Click to expand...
Click to collapse
Boot is when you power on the cellphone and it goes into your rom.
Sent from a dream.

Teichopsia said:
Boot is when you power on the cellphone and it goes into your rom.
Sent from a dream.
Click to expand...
Click to collapse
ok thank you

thank you so much this method worked perfectly and im so happy my phones back to normal

kyaldearing said:
thank you so much this method worked perfectly and im so happy my phones back to normal
Click to expand...
Click to collapse
Which OS are u using on ur computer.....and when i try the above method the first command is executed nothing happens..help??

waleedbutt256 said:
Which OS are u using on ur computer.....and when i try the above method the first command is executed nothing happens..help??
Click to expand...
Click to collapse
Lol continue writing until there's action, some of the commands don't bring back a report of whats happened. After each command wait like 5/10 seconds just to make sure.

waleedbutt256 said:
Which OS are u using on ur computer.....and when i try the above method the first command is executed nothing happens..help??
Click to expand...
Click to collapse
Im using Windows 7, make sure you have all your ABD drivers and phone drivers installed