-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root [S-Off] Facepalm S-Off for HTC Evo 4g LTE
- Thread starter ocnbrze
- Start date
-
- Tags
- htc evo 4g lte
Rxpert83
Dr. Feelgood
Unfortunately, not with s-on. I would try doing at least the first few steps of babyracun. You end up doing an old ruu throigh fastboot
jl79
Android Enthusiast
I thought I read somewhere that if you are hboot 1.15 or higher you can upgrade/downgrade your firmware? I'm hboot 2.09
jl79
Android Enthusiast
I'm so lost right now its ridiculous!
jl79
Android Enthusiast
Okay, so first things first...I still want to try Facepalm but I want to make sure I am fully ready phone wise.
I can't figure out why that RUU last night said I was on 3.16, but on the phone in the about phone tab it says 3.15
Also didn't 3.16 like just come out last week? I haven't done an update in almost a month and I haven't taken any OTAs (since I am still unlocked).
That babyracun method looked pretty easy since it doesn't involve me having to use Ubuntu...but I am not sure if I am in the correct current state to be able to use it. Out of desperation last night right before my backup finally worked I downloaded the babyracun zip and when I extracted the zip there was only one file in the folder...shouldn't there be more?
Lastly I am sorry if I am being a pain in the rear...I didn't mean for all this to go on so long or to have this thread go all over other topics besides what it was intended for. I sure do hope that I can one day get the understanding of this EVO4g LTE down like I did my old EVO.
I can't figure out why that RUU last night said I was on 3.16, but on the phone in the about phone tab it says 3.15
Also didn't 3.16 like just come out last week? I haven't done an update in almost a month and I haven't taken any OTAs (since I am still unlocked).
That babyracun method looked pretty easy since it doesn't involve me having to use Ubuntu...but I am not sure if I am in the correct current state to be able to use it. Out of desperation last night right before my backup finally worked I downloaded the babyracun zip and when I extracted the zip there was only one file in the folder...shouldn't there be more?
Lastly I am sorry if I am being a pain in the rear...I didn't mean for all this to go on so long or to have this thread go all over other topics besides what it was intended for. I sure do hope that I can one day get the understanding of this EVO4g LTE down like I did my old EVO.
jl79
Android Enthusiast
So I decided to give facepalm a try again since now my SuperSU seems to be updated correctly and running properly.
Here is what I got after running the CID commands, the part in red is where I'm not sure what happened...but I believe the first three commands worked if I am correct:
C:\Android>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
root@android:/ # su
su
root@android:/ # echo -ne "22222222" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
v/block/mmcblk0p5 bs=1 seek=20 <
8+0 records in
8+0 records out
8 bytes transferred in 0.006 secs (1333 bytes/sec)
root@android:/ # adb reboot bootloader
adb reboot bootloader
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|root@android:/ #
Here is what I got after running the CID commands, the part in red is where I'm not sure what happened...but I believe the first three commands worked if I am correct:
C:\Android>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
root@android:/ # su
su
root@android:/ # echo -ne "22222222" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
v/block/mmcblk0p5 bs=1 seek=20 <
8+0 records in
8+0 records out
8 bytes transferred in 0.006 secs (1333 bytes/sec)
root@android:/ # adb reboot bootloader
adb reboot bootloader
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|root@android:/ #
Rxpert83
Dr. Feelgood
You have to enter exit twice to get out of the shell and back ibto your normal directory before doing adb
Ran into that myself. As of right now youre trying to run adb from the phone whenb you want it on the computer.
The instructions are def not a step by step guide if youre new to running commands
Ran into that myself. As of right now youre trying to run adb from the phone whenb you want it on the computer.
The instructions are def not a step by step guide if youre new to running commands
jl79
Android Enthusiast
Okay, so I can pretty much pick up where I left off then after closing out the command prompt window.
As for the information I got back after entering those first three commands...does that look correct?
jl79
Android Enthusiast
That's what I was wondering...kind of like how we used Terminal Emulator on the old EVO to see if we had true SU?
***EDIT***
Tried it and it did not work, all I got in command prompt was a list of available commands...nothing about CID.
After successfully completing
adb reboot bootloader
The command to check is
fastboot getvar cid
adb reboot bootloader
The command to check is
fastboot getvar cid
jl79
Android Enthusiast
What result or message should I be looking for after entering that command?
***EDIT***
Here is what I got after entering those commands:
C:\Android>adb reboot bootloader
C:\Android>fastboot getvar cid
cid: SPCS_001
finished. total time: 0.003s
C:\Android>
SPCS_001 is Sprint PCS, United States.
SuperCID is a string of ones - 1111111 or so, as stated above.
SuperCID is a string of ones - 1111111 or so, as stated above.
jl79
Android Enthusiast
So I guess it didn't work.
Reboot, try again.
Pretty odd given that dd confirmed that it wrote.
Rxpert83, is that what you ran into?
Pretty odd given that dd confirmed that it wrote.
Rxpert83, is that what you ran into?
jl79
Android Enthusiast
Okay, retry what steps again...the 3 line CID commands or the fastboot getvar cid command?
The CID commands.
As mentioned above, you only need the # prompt to know that you're running as root.
If you get the # prompt in response to adb shell, go right to the echo command.
Then do the adb reboot, then the getvar command.
Rxpert83
Dr. Feelgood
Correct. Supercid isnt sticking. Try it a few more times, but if it doesnt take...
Recommend running the baby racun
Did you run past the echo command and fail, or did you check cid and stop? Not important, just curious, and I think I know the answer.
jl79
Android Enthusiast
The CID commands.
As mentioned above, you only need the # prompt to know that you're running as root.
If you get the # prompt in response to adb shell, go right to the echo command.
Then do the adb reboot, then the getvar command.
Okay, I will give it a go now!
Rxpert83
Dr. Feelgood
Did you run past the echo command and fail, or did you check cid and stop? Not important, just curious, and I think I know the answer.
Ran through it all "successfully" before troubleshooting and finding out cid failed.
jl79
Android Enthusiast
Results after trying again:
C:\Android>adb shell
root@android:/ # echo -ne "22222222" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
v/block/mmcblk0p5 bs=1 seek=20 <
8+0 records in
8+0 records out
8 bytes transferred in 0.002 secs (4000 bytes/sec)
root@android:/ # exit
exit
C:\Android>adb reboot bootloader
C:\Android>fastboot getvar cid
cid: SPCS_001
finished. total time: -0.000s
C:\Android>
The funny thing is SuperSU seems to be working properly this time since I am no longer getting the "update binary error"
C:\Android>adb shell
root@android:/ # echo -ne "22222222" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
v/block/mmcblk0p5 bs=1 seek=20 <
8+0 records in
8+0 records out
8 bytes transferred in 0.002 secs (4000 bytes/sec)
root@android:/ # exit
exit
C:\Android>adb reboot bootloader
C:\Android>fastboot getvar cid
cid: SPCS_001
finished. total time: -0.000s
C:\Android>
The funny thing is SuperSU seems to be working properly this time since I am no longer getting the "update binary error"
Rxpert83
Dr. Feelgood
Cid is still not sticking though, which was my issue