This is an insecure boot image. It gives you full shell root. I will be uploading a true root package soon.
To use
0) Unlock via HTCDev.com
1) Boot to fastboot
2) Do "fastboot flash boot fireballBOOTINSECURE.img"
3) Original boot.img is attached if you need to revert.
con247 said:
This is an insecure boot image. It gives you full shell root. I will be uploading a true root package soon.
To use
0) Unlock via HTCDev.com
1) Boot to fastboot
2) Do "fastboot flash boot fireballBOOTINSECURE.img"
3) Original boot.img is attached if you need to revert.
Click to expand...
Click to collapse
Thanks again Con for all the hard work. Just to update all, I have successfully installed SuperSU using Con's insecure boot and ported TWRP recovery. You can get the flashable SuperSU zip file here on xda (just do simple search).
I have been able to remove so far 130 megs of bloat from this sucker. Also changed lcd density. Basically root access is here!
Big thanks again to Con for the help and efforts to help all of us inc 4g users.
Thank you soooo much for this. Like a dumbass, I had an old HTC One S boot.img that I managed to flash to my DINC4g and you saved me from the brick I created. I am very grateful.
Is this similar as S-OFF?
lepa71 said:
Is this similar as S-OFF?
Click to expand...
Click to collapse
No.
So what is the difference between root and this?
lepa71 said:
So what is the difference between root and this?
Click to expand...
Click to collapse
This is shell root. This is something that roms should include, but it is not "root" as you know it.
Did you use a command line when you rebuilt the kernel? I have been trying to make a kernel for AOSP and the boot.img is failing. I'm hoping this is where I am going wrong.
Related
So I had HBOOT 1.30.0000, and I used the old revolutionary method. Then there was a problem and now I'm left with S-Off, but no recovery and no root access. Can anyone help?
Amer532 said:
So I had HBOOT 1.30.0000, and I used the old revolutionary method. Then there was a problem and now I'm left with S-Off, but no recovery and no root access. Can anyone help?
Click to expand...
Click to collapse
If you have s-off then I'm pretty sure that all you need to do is flash a recovery, then flash a rooted rom. Check the recovery in my sig.
What was the "problem" if you don't mind me asking.
wikdNoob said:
If you have s-off then I'm pretty sure that all you need to do is flash a recovery, then flash a rooted rom. Check the recovery in my sig.
What was the "problem" if you don't mind me asking.
Click to expand...
Click to collapse
Can't remember, it was somethin in cmd that said connection interrupted or something like that. Can't remember exactly
wikdNoob said:
If you have s-off then I'm pretty sure that all you need to do is flash a recovery, then flash a rooted rom. Check the recovery in my sig.
What was the "problem" if you don't mind me asking.
Click to expand...
Click to collapse
Also, how would you install that recovery?
Amer532 said:
Also, how would you install that recovery?
Click to expand...
Click to collapse
Flash image GUI, google it. You could use fastboot to flash it but flash image is wayy easier.
wikdNoob said:
Flash image GUI, google it. You could use fastboot to flash it but flash image is wayy easier.
Click to expand...
Click to collapse
I cant use Flash image GUI because I don't have root access
wikdNoob said:
Flash image GUI, google it. You could use fastboot to flash it but flash image is wayy easier.
Click to expand...
Click to collapse
Never mind, I got it!!! All I had to do was run the revolutionary root again. Thanks for replying, I appreciate it
Amer532 said:
I cant use Flash image GUI because I don't have root access
Click to expand...
Click to collapse
Yeah, good point, sorry.
Put the recovery image in the same folder that you have adb in. Make sure usb debugging is turned on. The phone needs to be booted into android. Open the folder on your computer that has adb in it and hold shift while you right click, select open command prompt here, now type "adb push recovery.img /sdcard/" without the quotes. Now type "adb reboot bootloader", itll boot to hboot and you should be in fastboot usb, now type "fastboot flash recovery recovery.img" without the quotes.
Also, you,ll either have to change the name of the recovery to "recovery.img" or you can change the command i gave you, ie, fastboot flash recovery nameofyourrecovery.img
You now have your custom recovery back.
Hi guys. Finally i updated to ICS from the OTA and i reunlocked HBoot with HTC Dev. Now i'm Unlocked again which recovery shuld i Flash? And how to root now?
Same here
I had previously relocked my phone and reverted to stock cause I could not get a kernal that would not reboot my phone or cause it to heat up on a custom ics rom. I ran the new OTA and unlocked the phone via hTCdec site. I am now on 2.89 w/ hboot 1.58 s-on. I flashed the 4ext recovery successfully. I want to go s-off just cause lol. will flashing Vipers OTA give s-off or is there something else I should do?
Yes i know 4ext is the best but you can not install it because you need root and to get root you need a zip file and a recovery first. My question is which recovery and SU zip file.
luis4ever said:
Yes i know 4ext is the best but you can not install it because you need root and to get root you need a zip file and a recovery first. My question is which recovery and SU zip file.
Click to expand...
Click to collapse
All you need is the img file and flash it through fastboot from a computer. After that just flash a rooted Rom or whatever you want
Sent from my PG86100 using Tapatalk 2
dr.chucky said:
All you need is the img file and flash it through fastboot from a computer. After that just flash a rooted Rom or whatever you want
Sent from my PG86100 using Tapatalk 2
Click to expand...
Click to collapse
Agreed. I am not currently rooted just unlocked. I flashed the recovery via fastboot. download a recovery .img and place it in the same folder where you have your unlock files for the htcdev site. in the command prompt direct it to the folder where u have fastboot and your recovery files. type,"fastboot flash recovery "yourrecovery.img" Do not use the quotations I used and replace yourrecovery with the file name of your recovery.
dr.chucky said:
All you need is the img file and flash it through fastboot from a computer. After that just flash a rooted Rom or whatever you want
Sent from my PG86100 using Tapatalk 2
Click to expand...
Click to collapse
Sure i know that too. The question is where do i find that 4ext Recovery img file?
Rooting
dr.chucky said:
All you need is the img file and flash it through fastboot from a computer. After that just flash a rooted Rom or whatever you want
Sent from my PG86100 using Tapatalk 2
Click to expand...
Click to collapse
I know with unlocked and 4ext recovery I can do most things a rooted phone can do, but I want to be rooted just for the heck of it lol. If I flash vipers stock rooted ota deodexed zip will that give s-off. or could I just push a SU flashable img?
luisrodz said:
I know with unlocked and 4ext recovery I can do most things a rooted phone can do, but I want to be rooted just for the heck of it lol. If I flash vipers stock rooted ota deodexed zip will that give s-off. or could I just push a SU flashable img?
Click to expand...
Click to collapse
If you flash Vipers you will not get S-OFF. Just a rooted system
luis4ever said:
Sure i know that too. The question is where do i find that 4ext Recovery img file?
Click to expand...
Click to collapse
Here ya go.
So I decided to use htcdev to unlock my bootloader last night for the first time. I am on OTA 1.22.651.3. I know I am not "rooted" and am confused as to if I can actually try any custom ROMs. I read REGAWMOD's post regarding his rooter not working right now...is there another option? Sorry if I missed a post that explains this situation, but I just want to try a custom rom without screwing up my phone.
bman3333 said:
So I decided to use htcdev to unlock my bootloader last night for the first time. I am on OTA 1.22.651.3. I know I am not "rooted" and am confused as to if I can actually try any custom ROMs. I read REGAWMOD's post regarding his rooter not working right now...is there another option? Sorry if I missed a post that explains this situation, but I just want to try a custom rom without screwing up my phone.
Click to expand...
Click to collapse
There's really no reason to manually root if you've already unlocked the bootloader. All you need to do is flash a recovery and then you can flash any ROM, which will already have root access. Here's a good instructional on flashing a recovery:
http://forum.xda-developers.com/showthread.php?t=1830098
Sent from my EVO LTE
Thanks premo15 for the info and link.
The funny thing about htcdev was the stuff they make you download and the steps they make you go through to unlock the bootloader. I was thinking they were going to make me hop on one foot while patting my head and belly simultaneously. :laugh:
I read over and over, did some research, tried running cmd and so on.
having no luck
I went through the HTCDev, s-on but bootloader unlocked
I'm running stock 2.13
After unlock you need to flash twrp, you can use fastboot to do so, just download twrp from the teamwin website and put the image file in adb tools or android sdk folder and in the bootloader type fastboot flash recovery openrecovery-twrp-2.2.2.0-jewel.img
om4 said:
After unlock you need to flash twrp, you can use fastboot to do so, just download twrp from the teamwin website and put the image file in adb tools or android sdk folder and in the bootloader type fastboot flash recovery openrecovery-twrp-2.2.2.0-jewel.img
Click to expand...
Click to collapse
i tried doing that and i couldn't get it to. is there another way to do it?
Can you be more specific on how it isn't working?
om4 said:
Can you be more specific on how it isn't working?
Click to expand...
Click to collapse
yeah, sorry.
the steps i've taken were similar to the htcdev steps,
finish steps 1-7
after I typed "fastboot flash recovery recovery.img" into command prompt and gives me
"error: cannot load 'recovery.img'"
The name has to match, when you download twrp 2.2 the full name is openrecovery-twrp-2.2.2.0-jewel.img so it would be fastboot flash recovery openrecovery-twrp-2.2.2.0-jewel.img or you can rename to recovery.img
om4 said:
The name has to match, when you download twrp 2.2 the full name is openrecovery-twrp-2.2.2.0-jewel.img so it would be fastboot flash recovery openrecovery-twrp-2.2.2.0-jewel.img or you can rename to recovery.img
Click to expand...
Click to collapse
i re- downloaded and used command prompt again without changing name, worked fine this time. thanks for the help om4
flash some roms!!!!!!!!!! :victory::highfive::laugh::good::silly:
Why dont you just get goomanager from the market and flash it from there. Goomanager/flash rom/install open recovery,,,that easy bro
Sent from my EVO using xda premium
Thanks
premo15 said:
There's really no reason to manually root if you've already unlocked the bootloader. All you need to do is flash a recovery and then you can flash any ROM, which will already have root access. Here's a good instructional on flashing a recovery:
http://forum.xda-developers.com/showthread.php?t=1830098
Sent from my EVO LTE
Click to expand...
Click to collapse
Thanks Premo! I was also confused what to do at this point, might this be worth adding to the FAQ thread?
Hello I'm not new to rooting but I am to the fastboot and cmd prompt but anyways
I'm on my way to rooting my DNA, I'm as far as flashing the recovery I flashed a twrp recovery for DNA and as I boot into recovery all I get is a screen with rainbow lines I wanted to flash cwm but I didn't know if flashing over recoverys was a good idea so I tried to flash another DNA twrp recovery 2.4.1.0 I believe but now everytine I go to flash a recovery I get a "cannot load recovery.img unknown error no matter what I do can anybody help me with this
c2a5nn1o4n said:
Hello I'm not new to rooting but I am to the fastboot and cmd prompt but anyways
I'm on my way to rooting my DNA, I'm as far as flashing the recovery I flashed a twrp recovery for DNA and as I boot into recovery all I get is a screen with rainbow lines I wanted to flash cwm but I didn't know if flashing over recoverys was a good idea so I tried to flash another DNA twrp recovery 2.4.1.0 I believe but now everytine I go to flash a recovery I get a "cannot load recovery.img unknown error no matter what I do can anybody help me with this
Click to expand...
Click to collapse
did you enter this command when you were in fastboot usb mode?
is the recovery.img file in the correct directory (so fastboot can find it to flash it)
did you download the correct version...
Code:
fastboot flash recovery recovery.img
.torrented said:
did you enter this command when you were in fastboot usb mode?
is the recovery.img file in the correct directory (so fastboot can find it to flash it)
did you download the correct version...
Code:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Yes I got it to work the first time but now like I said it I get the can not load recovery.img unknown error
Yes all my pathing is right
c2a5nn1o4n said:
Yes I got it to work the first time but now like I said it I get the can not load recovery.img unknown error
Yes all my pathing is right
Click to expand...
Click to collapse
can you boot up into your ROM? if so download the GooManager app click the settings button and click install OpenRecovery and see if that works...
.torrented said:
can you boot up into your ROM? if so download the GooManager app click the settings button and click install OpenRecovery and see if that works...
Click to expand...
Click to collapse
I need to get into recovery to flash my superuser and busybox to obtain root unless there is another way.... Its the rainbow screen just a flaw in the display or would the entire recovery be messed up
c2a5nn1o4n said:
I need to get into recovery to flash my superuser and busybox to obtain root unless there is another way.... Its the rainbow screen just a flaw in the display or would the entire recovery be messed up
Click to expand...
Click to collapse
I've never heard of a "rainbow screen effect" when dealing with recoveries...
try downloading the CWM recovery found here http://tinyw.in/QGZG
or here is the TWRP recovery http://tinyw.in/8yFn
and last is the dlx-stock recovery pulled from the OTA (safe to use) http://dl.dropbox.com/u/10829584/stock_recovery_dlx.img
and try using a different usb port
c2a5nn1o4n said:
I need to get into recovery to flash my superuser and busybox to obtain root unless there is another way.... Its the rainbow screen just a flaw in the display or would the entire recovery be messed up
Click to expand...
Click to collapse
Cwm flashed fine and ran perfected I flashed my Su and busybox package and rebooted I still do not have root I went to the Su app and it said binary needs to be updated I accept and installation immediately failed
Edit: I tried again its rebooted my DNA I went back to supersu and it still says binary needs to b updated
SUCCESS you sir are a magical human being and I wish the best for u in life
c2a5nn1o4n said:
Cwm flashed fine and ran perfected I flashed my Su and busybox package and rebooted I still do not have root I went to the Su app and it said binary needs to be updated I accept and installation immediately failed
Edit: I tried again its rebooted my DNA I went back to supersu and it still says binary needs to b updated
SUCCESS you sir are a magical human being and I wish the best for u in life
Click to expand...
Click to collapse
I don't understand. Did you end up figuring it out again? If you are able to make it to recovery try flashing an already rooted rom, if not, you could just try to fasboot root again. It might help
I Have 2 more questions I was wondering if there is a WiFi hack yet and how is the its update going to effect my root
c2a5nn1o4n said:
Cwm flashed fine and ran perfected I flashed my Su and busybox package and rebooted I still do not have root I went to the Su app and it said binary needs to be updated I accept and installation immediately failed
Edit: I tried again its rebooted my DNA I went back to supersu and it still says binary needs to b updated
SUCCESS you sir are a magical human being and I wish the best for u in life
Click to expand...
Click to collapse
I read somewhere that if you flash the wrong model (dlxu) that you get messed up lines
c2a5nn1o4n said:
I Have 2 more questions I was wondering if there is a WiFi hack yet and how is the its update going to effect my root
Click to expand...
Click to collapse
I have not heard of a WiFi hack for the DNA... What kind of hack are you talking about... Like what does it do....
And I would just wait for a dev to make a flashable zip but you can flash the radio.img if you want to
Sent from my HTC6435LVW using XDA Premium HD app
.torrented said:
I read somewhere that if you flash the wrong model (dlxu) that you get messed up lines
I have not heard of a WiFi hack for the DNA... What kind of hack are you talking about... Like what does it do....
And I would just wait for a dev to make a flashable zip but you can flash the radio.img if you want to
Sent from my HTC6435LVW using XDA Premium HD app
Click to expand...
Click to collapse
I figured that out but now I'm losing root everytime I shut down even if I update binary in supersu
c2a5nn1o4n said:
I figured that out but now I'm losing root everytime I shut down even if I update binary in supersu
Click to expand...
Click to collapse
you need a kernel with system write enabled to be able to update binaries
TeamWin Recovery Project 2.6.3
So it took a little finesse but we have working TWRP now with f2fs support and touch working.
Device Tree Source: https://github.com/razrqcom-dev-team/
Background and geeky ****:
First off we need DTB (Device Tree Binary) for touch support. The X bootloader adds the dtb onto anything flashed to boot partition. So I built recovery and fastboot it to the boot partition. Ooops image is too big. Recompile kernel with xz compression and loose about 3 MB then it flashes to boot partition. Then I just "dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/sdcard/twrp263.img" and voila we have a working flashable recovery.img with DTB appended
OK, so on to what you came for:
Download: http://androidhosting.org/Devs/Dhacker29/MotoX/twrp263.img
Reboot to booloader and:
Code:
fastboot flash recovery twrp263.img
Hope you guys enjoy!
Special thanks to Dees Troy for the source and for implementing my mkfs.f2fs into TWRP.
hell yeah..thank. i love i got my developer edition and i just home nd bam u give me this beautiful images. thanks dhacker29 u r always rocking hard on github. thanks
Sent from my XT1060 using xda app-developers app
skiwong20 said:
hell yeah..thank. i love i got my developer edition and i just home nd bam u give me this beautiful images. thanks dhacker29 u r always rocking hard on github. thanks
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
The normal GSM version can be unlocked through the online moto method, right?
Maratu said:
The normal GSM version can be unlocked through the online moto method, right?
Click to expand...
Click to collapse
Yeah every model except ATT and VZW can be unlocked thourgh the bootloader unlock website as far as I know.
Flashed recovery, you're aren't rooted wanna root? Sure! installed su, finished install through twrp! Thanks much, looking forward to the coming months!
It works fine, thank you dhacker.
dhacker29 said:
Yeah every model except ATT and VZW can be unlocked thourgh the bootloader unlock website as far as I know.
Click to expand...
Click to collapse
Hey brudda, I just got my Dev Edition through Verizon and I can unlock bootloader through the moto website but was just wondering what steps do I need to take to get TWRP running. Do I unlock bootloader first with the moto website but then how do I obtain root? Right now I have root through JCase's PawnMyMoto exploit. Now do I need to start from scratch and get rid of his exploit so I won't be rooted anymore? Sometimes I think I should just wait until a dev has created a nice boot loader unlock, root and flash custom recovery tool.
Sent from my XT1060 using Xparent Cyan Tapatalk 2
You just unlock through moto website and fastboot recovery. It will ask you if you want to root when you reboot, if you're not rooted. Or you can flash the superuser of your vice in recovery. No exploit needed when unlocked.
dhacker29 said:
You just unlock through moto website and fastboot recovery. It will ask you if you want to root when you reboot, if you're not rooted. Or you can flash the superuser of your vice in recovery. No exploit needed when unlocked.
Click to expand...
Click to collapse
Ok so, I should get rid of the root I'm on and go to moto and unlock bootloader, then in fastboot go to recovery and from there obtain root. Then finally I can flash TWRP. RIGHT?
Sent from my XT1060 using Xparent Cyan Tapatalk 2
You don't have to unroot unless you want to.
1. Go to moto bootloader unlock site follow the steps to unlock bootloader.
2. Fastboot flash recovery twrp263.img
3. Boot into recovery. If you are not rooted it will ask you if you want to root when you exit.
dhacker29 said:
You don't have to unroot unless you want to.
1. Go to moto bootloader unlock site follow the steps to unlock bootloader.
2. Fastboot flash recovery twrp263.img
3. Boot into recovery. If you are not rooted it will ask you if you want to root when you exit.
Click to expand...
Click to collapse
Thanks boss. I sure do appreciate it.
Sent from my XT1060 using Xparent Cyan Tapatalk 2
This might be a dumb question, but will this w this on the Droid Maxx DE?
Sent from my Carbon XT926
It should work fine
Sent from my XT926 using Tapatalk 2
Thanks Dhacker. Appreciate it.
much appreciated
Just wanted to say thanks a bunch for doing this. Finally broke down and unlocked. Fastbooted this and made a backup.
just wanted to say thanks this all worked for me.
thank you for this... worked like a charm
Guys it's been a little while since I've used abd so I just wanna make sure I got this right. After unlocking the bootloader at moto website, I download the twrp image file and put it in the same adb folder where fastboot is (within adb folders), then shift + rt click, open command window and push the twrp image file. It's that correct? No YouTube videos yet, huh?
Thanks in advance!
Sent from my XT1056 using Tapatalk 2
EDIT: sorry, what button combo to get in bootloader?
pathtologos said:
Guys it's been a little while since I've used abd so I just wanna make sure I got this right. After unlocking the bootloader at moto website, I download the twrp image file and put it in the same adb folder where fastboot is (within adb folders), then shift + rt click, open command window and push the twrp image file. It's that correct? No YouTube videos yet, huh?
Thanks in advance!
Sent from my XT1056 using Tapatalk 2
EDIT: sorry, what button combo to get in bootloader?
Click to expand...
Click to collapse
You do not push the image to your phone, you flash it from your computer.
To boot into bootloader mode (fastboot) you can use adb (adb reboot recovery) or hold the power button and volume down for about 5 seconds.
the fastboot command you must issue is fastboot flash recovery <image_name>.img
mentose457 said:
You do not push the image to your phone, you flash it from your computer.
To boot into bootloader mode (fastboot) you can use adb (adb reboot recovery) or hold the power button and volume down for about 5 seconds.
the fastboot command you must issue is fastboot flash recovery <image_name>.img
Click to expand...
Click to collapse
You need to make sure the twrp img file is in the same folder that your fastboot.exe is in. Open a command prompt. Using the CD command navigate to that folder. Then use the fastboot command listed replacing the entire "<image_name>" with the file name for the recovery.
Side note - once rooted, for a quick no nonsense method to boot into fastboot / recovery, you can install a simple little app called Quick Boot from the Play store.