Related
So I just got a new Evo! Sweet!
It came with software version 1.13.651.1.
I want to be able to flash ROMs and run Titanium Backup Pro.
What's the best/latest root method? Should I upgrade software first, or leave it?
(There are so many threads/sites, I'm confused as to what method is best/easiest.)
Thanks!
Do you mean 2.13? It depends on hboot, if you have 1.12 you can use lazy panda to soff. Anything 1.15 and higher and you need to dev unlock, there is no soff. You can try regawmod to unlock but people are having issues. It's easier to just sign up to HTC dev and unlock that way.
Under "about phone" it says 1.13.651.1 ... no, not 2.13.
Not sure how to check the hboot version....
1.13 is the first version that the phone shipped with. You might be lucky enough to have hboot 1.12. If so then you can run regaw's method and use lazypanda.
Just checking, you may be able to soff the phone. More then likely you have 1.12 hold power and wait for phone to turn off, let go then press and hold power + volume down, it will force bootloader
Make sure to check all your info and use this thread
http://forum.xda-developers.com/showthread.php?t=1690919
Then this
http://forum.xda-developers.com/showthread.php?t=1737123
I would assume that you have hboot 1.13. If that's the case do not accept any ota's or you will lose the ability to get s-off. Check the development thread and you'll find an auto-rooter thread. Then read up on lazy panda s-off. You should probably spend a couple days reading and re-reading in case you have any issues you'll know how to resolve them.
Sent from my EVO using xda premium
Is it 1.13? Been awhile lol
Yeah, I had to check. Lol
Yeah, my bad with all the odd numbers it just felt right.
Sent from my EVO using xda premium
I checked, and I do have hboot 1.12.
I guess that's a good thing!
So just do the lazy panda method?
You need to root then s-off. Use the threads in posted in order, all instructions are there.
metalfan78 said:
Make sure to check all your info and use this thread
http://forum.xda-developers.com/showthread.php?t=1690919
Then this
http://forum.xda-developers.com/showthread.php?t=1737123
Click to expand...
Click to collapse
I'm on a Mac; no Windows. So I can't do the RegawMOD...
Should I do this:
http://androidforums.com/evo-4g-lte-all-things-root/572162-how-get-full-root-mac.html
?
That should work, just make sure that you use the latest twrp and if you plan on flashing a different Rom skip flashing superuser, its an unnecessary extra step
om4 said:
That should work, just make sure that you use the latest twrp and if you plan on flashing a different Rom skip flashing superuser, its an unnecessary extra step
Click to expand...
Click to collapse
I got as far as running the runmemac.sh script; but now it's stuck on "waiting for device ... daemon started successfully..."
There IS a USB icon on the Evo, and it's in "charge only" mode ... and the boot screen showed "UNLOCKED" ...
Hmmm ...
So you flashed the unlock code? Sorry, I wasn't thinking about soff, you will need to flash supersu or superuser for root to be able to run lazy panda. Usually most users have hboot 1.15 or higher and can't use lazy panda so it slipped my mind
om4 said:
So you flashed the unlock code? Sorry, I wasn't thinking about soff, you will need to flash supersu or superuser for root to be able to run lazy panda. Usually most users have hboot 1.15 or higher and can't use lazy panda so it slipped my mind
Click to expand...
Click to collapse
Yes, the unlocking part worked fine; now I'm trying to get root, but adb won't see the phone (anymore).
(following this guide: http://androidforums.com/evo-4g-lte-all-things-root/572162-how-get-full-root-mac.html)
To get root flash the superuser zip in recovery, did you flash twrp
USB debugging needs to be re-enabled after unlock but for rooting stock, you need to flash recovery in fastboot. The recovery that comes with the zip you downloaded is a bit out of date you can download the latest from team win website and put it in the adb folder, after flashing twrp, you can flash the superuser zip that came with the zip you downloaded
om4 said:
USB debugging needs to be re-enabled after unlock but for rooting stock, you need to flash recovery in fastboot. The recovery that comes with the zip you downloaded is a bit out of date you can download the latest from team win website and put it in the adb folder, after flashing twrp, you can flash the superuser zip that came with the zip you downloaded
Click to expand...
Click to collapse
AHA! Re-enable debug! That was it! Thanks!
So are you saying to NOT run that shell script? I think it installs busybox and su...
Code:
#!/bin/bash
varadb=adb-mac
echo "---------------------------------------------------------------"
echo " One-Click Root ToolKit For Evo 4G LTE! "
echo " Script by Max Lee from HTCEvoHacks.com "
echo " Credits go to XDA users sparkym3 and Dan Rosenburg for exploit. "
echo "---------------------------------------------------------------"
echo " [*] This script will: "
echo " (1) root your Evo 4G LTE on ICS "
echo " (2) install Busybox "
echo " (3) install SU files "
echo " [*] Before u begin: "
echo " (4) Make sure to read full instructions at OneXRoot.com! "
echo "---------------------------------------------------------------"
echo "--- STARTING ----"
echo "--- WAITING FOR DEVICE"
./$varadb wait-for-device
echo "Start Rooting..."
./$varadb shell mv /data/local/tmp /data/local/tmp.bak
./$varadb shell ln -s /data /data/local/tmp
./$varadb reboot
echo "reboot #1 - DO NOT DISCONNECT YOUR DEVICE!"
./$varadb wait-for-device
./$varadb shell "echo \"ro.kernel.qemu=1\" > /data/local.prop"
./$varadb reboot
echo "reboot #2 - DO NOT DISCONNECT YOUR DEVICE!"
./$varadb wait-for-device
./$varadb remount
./$varadb push su /system/bin/su
./$varadb shell "chown root.shell /system/bin/su"
./$varadb shell "chmod 06755 /system/bin/su"
./$varadb shell "rm /system/xbin/su"
./$varadb shell "ln -s /system/bin/su /system/xbin/su"
./$varadb push Superuser.apk /system/app/.
./$varadb shell rm /data/local.prop
./$varadb shell rm /data/local/tmp
./$varadb shell mv /data/local/tmp.bak /data/local/tmp
./$varadb push busybox /data/local/tmp/.
./$varadb shell "chmod 755 /data/local/tmp/busybox"
./$varadb shell "/data/local/tmp/busybox mount -o remount,rw /system"
./$varadb shell "dd if=/data/local/tmp/busybox of=/system/xbin/busybox"
./$varadb shell "chown root.shell /system/xbin/busybox"
./$varadb shell "chmod 04755 /system/xbin/busybox"
./$varadb shell "/system/xbin/busybox --install -s /system/xbin"
./$varadb shell "rm -r /data/local/tmp/busybox"
echo "rebooting"
./$varadb reboot
echo "All Done rooting Evo 4G LTE, check out HTCEvoHacks.com for more cool stuff like ROMs, hacks, tips, and more!"
@pause
Oh, I didn't read through the entire tutorial you linked lol, that should do it actually
Got root, then su binary installed need some help backtracking a few things. If someone is up for it?
I guess the first thing first is. The first time I adb shell'd I got promted with root user: ( does this happen right off the bat for anyone else? I did a few things before this with modstrings and busybox. But, didn't try adb till after)
Code:
adb shell
[email protected]:/ #
Once I noticed I had root on shell I simply found the system mount at /dev/ubui0_0 and I mounted it rw.
Code:
[email protected]:/ # mount -o remount, /dev/ubi0_0
moved the su binary over to the sdcard. wrote it to system/xbin link named to /system/bin. gave permisions.
Code:
adb push su /sdcard/
[email protected]:/ # cat /sdcard/su > /system/xbin/su
[email protected]:/ # ln -s /system/xbin/su
[email protected]:/ # chmod 6755 /system/xbin/su
[email protected]:/ # su
[email protected]:/ # :D
Off I went. I need to update the binary, but as of right now Superuser shows root as 'allow', SuperSU deny (think it old binary).
If you guys are not getting root after adb shell on this device, I think I can backtrack the modstrings and other stuff I did.
I really don't know where this device sits on getting rooted. It seems like some windows programs did it before an update that happened at some point, but not anymore? I don't have access to windows so I don't keep up with those methods.
Thanks! Hope someone can help me out.
hi to all can u pls help me to s off my htc one max im desperate to s off my phone i unlock bootloader flash twrp recovery flash viperom 2.0 but when im in cmd to push firewater nothings happn and firewater not run in command heres my log...
Code:
C:\Users\nehj>cd c:\adb
c:\adb>adb reboot
adb server is out of date. killing...
* daemon started successfully *
c:\adb>adb wait-for-device push firewater /data/local/tmp
adb server is out of date. killing...
* daemon started successfully *
2810 KB/s (4522136 bytes in 1.571s)
c:\adb>adb shell
[email protected]/# chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]/# /data/local/tmp/firewater
/data/local/tmp/firewater
[email protected]/#
i already try other rom like cm12 pacman rom but when im in command same as in log firewater not run....:crying::crying::crying:
Firewater is dead server side. You'll have to pay for sunshine.apk.
Don't waste your time, only way to do it is called sunshine, it cost 25 usd. It worth it. You will need to flash a pure stock RUU, get root and run sunshine.
Hi,
I've changed my build.prop and now my phone won't boot, it stay on the boot logo.
I've installed supersu on the phone , it is rooted as I have root access using phone interface.
But now I'm stuck on boot logo and try to access the phone via adb shell :
But the su Command in adb shell doesn't give root access, it stays in "shell" user.
I never used it as my phone was well and running so I didn't allow su to get root access in a shell in the supersu apk.
How can we override this ?
adb root doesn't work neither.
Any idea ?
Thanks
My phone : honor 6, Android 4.4.2, SuperSu
C:\Users\U403774\Downloads\Honor6\HONOR 6 Multi-Tool>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ $ su
su
1|[email protected]:/ $ mount -o remount,rw -t ext4 /dev/block/platform/ff1fe000.dw
mc0/by-name/system /system
dev/block/platform/ff1fe000.dwmmc0/by-name/system /system <
mount: Operation not permitted
255|[email protected]:/ $
255|[email protected]:/ $ id
id
uid=2000(shell) gid=2000(shell) groups=1003(graphics),1004(input),1007(log),1011
(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),
3006(net_bw_stats) context=u:r:adbd:s0
[email protected]:/ $
Saved, thanks to TWRP recovery file manager !!
But I still be curious , and if someone knows , I'd like to get the answer to my first question.
"But the su Command in adb shell doesn't give root access, it stays in "shell" user.
I never used it as my phone was well and running so I didn't allow su to get root access in a shell in the supersu apk.
How can we override this ?"
thanks
I've tried KingRoot but it tells me the device isn't supported. Are there any ways to install a custom recovery like TWRP or CWM?
Extract the boot.img file from "UPDATE.APP", upload it here, and I'll root it manually for you.
mann1 said:
Extract the boot.img file from "UPDATE.APP", upload it here, and I'll root it manually for you.
Click to expand...
Click to collapse
I saw your post on another thread here so I got the tools to extract it, but my knowledge is limited at ro.secure=0 and bash. If you wouldn't mind sharing I'd love to know how it's done.
I've attached the file.
Well, first you need to download the following files:
1-Your rooted_boot img from here
2-Compressed folder mann1.zip from here
===
Now lets start,
1- Unzip the rooted img then flash it, (be careful it's not tested)
2- 2- Unzip the file "mann1.zip" to get folder "mann1" then copy it directly into your device internal storage NOT the SD card. Put the the whole folder not the files inside
3-If the rooted boot worked fine, restart your device in the normal mode (NOT the recovery nor bootloader), and type the following commands one by one:
Code:
adb devices
adb root
adb shell
Now you supposed to see your root like that
[email protected]:/ #
complete the commands in the adb shell:
mount -o remount,rw /system
mount -o remount,rw /etc
mkdir /system/bin/.ext
mkdir /etc/init.d
cat /sdcard/mann1/busybox > /system/bin/busybox
cat /sdcard/mann1/su > /system/xbin/su
cat /sdcard/mann1/Superuser.apk > /system/app/Superuser.apk
cat /sdcard/mann1/su > /system/xbin/daemonsu
cat /sdcard/mann1/su > /system/xbin/sugote
cat /system/bin/sh > /system/xbin/sugote-mksh
cat /sdcard/mann1/supolicy > /system/xbin/supolicy
cat /sdcard/mann1/otasurvival.sh > /system/xbin/otasurvival.sh
cat /sdcard/mann1/libsupol.so > /system/lib/libsupol.so
cat /sdcard/mann1/su > /system/bin/.ext/.su
cat /sdcard/mann1/su > /etc/.installed_su_daemon
cat /sdcard/mann1/install-recovery.sh > /etc/install-recovery.sh
cat /sdcard/mann1/99SuperSUDaemon > /etc/init.d/99SuperSUDaemon
chown 0.0 /system/bin/busybox
chmod 0755 /system/bin/busybox
chown 0.0 /system/app/Superuser.apk
chmod 0755 /system/app/Superuser.apk
chown 0.0 /system/xbin/su
chmod 0755 /system/xbin/su
chown 0.0 /system/xbin/sugote
chmod 0755 /system/xbin/sugote
chown 0.0 /system/xbin/sugote-mksh
chmod 0755 /system/xbin/sugote-mksh
chown 0.0 /system/xbin/daemonsu
chmod 0755 /system/xbin/daemonsu
chown 0.0 /system/xbin/supolicy
chmod 0755 /system/xbin/supolicy
chown 0.0 /system/xbin/otasurvival.sh
chmod 0755 /system/xbin/otasurvival.sh
chown 0.0 /system/lib/libsupol.so
chmod 0755 /system/lib/libsupol.so
chown 0.0 /system/bin/.ext/.su
chmod 0755 /system/bin/.ext/.su
chown 0.0 /etc/.installed_su_daemon
chmod 0755 /etc/.installed_su_daemon
chown 0.0 /etc/install-recovery.sh
chmod 0755 /etc/install-recovery.sh
chown 0.0 /etc/init.d/99SuperSUDaemon
chmod 0755 /etc/init.d/99SuperSUDaemon
daemonsu -d
reboot
I assumed you already know the adb and fastboot commands to flash the boot
If everything run smoothly,after restarting your device you will find SuperSU installed, and the device is rooted w/o custom recovery.
mann1 said:
Code:
adb devices
adb root
adb shell
Now you supposed to see your root like that
[email protected]:/ #
Click to expand...
Click to collapse
I just booted the image and tried to start adb as root which it does however adb shell drops me into a regular shell, I also tried to flash it but still, no dice.
Code:
[email protected]:~/Music/root$ adb root
restarting adbd as root
[email protected]:~/Music/root$ adb shell
[email protected]:/ $ exit
I have a feeling there may be a software block inside system.img to prevent adb starting a shell as root, any idea?
adamhighdefinition said:
I just booted the image and tried to start adb as root which it does however adb shell drops me into a regular shell, I also tried to flash it but still, no dice.
I have a feeling there may be a software block inside system.img to prevent adb starting a shell as root, any idea?
Click to expand...
Click to collapse
The method works fine under Windows, but I've never tried it out under Linux.
Try this new root_boot2.img HERE (be careful it's not tested)
Pls flash it, don't just boot it:
fastboot flash boot root_boot2.img
If you get error with "adb root", skip it and keep going till the "reboot"
Good luck
mann1 said:
The method works fine under Windows, but I've never tried it out under Linux.
Try this new root_boot2.img HERE (be careful it's not tested)
Pls flash it, don't just boot it:
fastboot flash boot root_boot2.img
If you get error with "adb root", skip it and keep going till the "reboot"
Good luck
Click to expand...
Click to collapse
Just tested it, it caused a bootloop though, I cleared the cache and it still looped. I'll flash the first one and test it on windows then I'll report back.
The first one does allow me to see the Logcat output for all of the system services in Android Studio though, so it is giving elevated permissions.
Yeah, same on windows. Drops me into a normal shell.
Well, try this one
mann1 said:
Well, try this one
Click to expand...
Click to collapse
Dude thank you! I was repacking custom systems all night last night trying to install it directly into the rom.
In your mann1 folder the su binary is out of date btw
adamhighdefinition said:
Dude thank you! I was repacking custom systems all night last night trying to install it directly into the rom.
In your mann1 folder the su binary is out of date btw
Click to expand...
Click to collapse
Yvw, then this last one worked fine with you.
Su binary is extracted from the most recent version of SuperSu.apk, but in all cases we just use it to get rooted then you can update the whole package via Google play.
mann1 said:
Yvw, then this last one worked fine with you.
Click to expand...
Click to collapse
Yeah, last one worked for the Mediapad T1 8.0 Pro T1-921L.
mann1 said:
Su binary is extracted from the most recent version of SuperSu.apk, but in all cases we just use it to get rooted then you can update the whole package via Google play..
Click to expand...
Click to collapse
Must just be supersu being weird then, thanks again.
This tutorial explains how to root the kernel of any device under Linux. Here
Good luck