My htc evo 4glte is on hboot 1.19 and its software says 2.13.651.1 710RD and Im currently trying to do the facepalm s-off method but im stuck with this. Im not sure what to do or what im doing wrong. :,(
C:\adb\sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT256S400039 device
C:\adb\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # echo -ne "22222222" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
ev/block/mmcblk0p5 bs=1 seek=20 <
8+0 records in
8+0 records out
8 bytes transferred in 0.003 secs (2666 bytes/sec)
[email protected]:/ # adb reboot bootloader
adb reboot bootloader
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|[email protected]:/ # adb reboot bootloader
adb reboot bootloader
error: device not found
1|[email protected]:/ #
After this part type
C:\adb\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # echo -ne "22222222" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
ev/block/mmcblk0p5 bs=1 seek=20 <
8+0 records in
8+0 records out
8 bytes transferred in 0.003 secs (2666 bytes/sec)
Code:
exit
Code:
exit
These 2 exit commands will bring you out of adb shell and back to the regular command prompt.
**Note** if the cmd window closes on the second exit command then only 1 exit command is needed. (it's been a while so don't really remember)
Then type reboot-bootloader
uh well it looks like i got to the black htc screen but it said unkown error data failure does that mean i need to redownload something and redo it? im going to do that i guess an try again it seems it didnt hurt anything to mess that up..
welp now its hanging at sending 'zip' step 3.. :did i screw it up? how long is it supposed to take? :,(
I hate life heres a copy of my dumb scribble and please save me from my stupidness. ^^
F:\4glte\Evo4GLTERoot2>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HT256S400039 device
F:\4glte\Evo4GLTERoot2>adb shell
[email protected]:/ $ su
su
[email protected]:/ # echo -ne "22222222" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
ev/block/mmcblk0p5 bs=1 seek=20 <
8+0 records in
8+0 records out
8 bytes transferred in 0.006 secs (1333 bytes/sec)
[email protected]:/ # exit
exit
[email protected]:/ $ exit
exit
F:\4glte\Evo4GLTERoot2>adb reboot bootloader
F:\4glte\Evo4GLTERoot2>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.080s]
finished. total time: 0.080s
F:\4glte\Evo4GLTERoot2>fastboot flash zip PJ7510000-EvoLTE.zip
sending 'zip' (35863 KB)...
woo thank you for your help! looks like after i switched usb ports (both are 2.0) it stopped with the data failure and it seems to be s-off. so how should i update the software on it now? can I just flash a rom? I really need to flash a new rom/update it because the person who owned it before me somehow delete alot of stuff and left a partition of trash that wasn't delete when the guy sold it to me and some things don't work right.(IE sound as in ringtone and music doesn't work) but it vibrates and it seems to work on the sprint network just fine and I can text and call and hear people just fine.
Kannz2 said:
woo thank you for your help! looks like after i switched usb ports (both are 2.0) it stopped with the data failure and it seems to be s-off. so how should i update the software on it now? can I just flash a rom? I really need to flash a new rom/update it because the person who owned it before me somehow delete alot of stuff and left a partition of trash that wasn't delete when the guy sold it to me and some things don't work right.(IE sound as in ringtone and music doesn't work) but it vibrates and it seems to work on the sprint network just fine and I can text and call and hear people just fine.
Click to expand...
Click to collapse
Honestly now that you're S-off I would consider running the RUU for the Android 4.3 update. Click the top link in my sig and read the RUU section, which includes instructions on how to install the RUU. The link to the 4.3 update can be found at the bottom of the first post.
the one that says 4.13.651.4 RUU or is it the second to the bottom on the androidruu link?
looks like it updated it to 4.3 thank you for the link and for having all that stuff in one spot! ^^ what should I do now? can I installed a rom now? I dont need to update it anymore right?
could I get some help finding a usable rom? none of the ones ive downloaded want to flash they keep saying updater failed.. :/ i keep getting error executing updater binary in zip when installing rom.
Try V20 of this ROM:
http://forum.xda-developers.com/showthread.php?t=2528953
would that rom work with this kernel? http://forum.xda-developers.com/showthread.php?t=2181243 or this one? http://forum.xda-developers.com/showthread.php?t=2075542
No & no. There are no custom kernels for 4.3 for the EVO LTE.
dang owells thanks a bunch for the working rom. ^^ looks like the sound somehow doesn't work at all even with the fresh rom install. I guess the person who sold it to me ripped me off.. at least the sound works through the headphones and everything else works okay..you know any really good roms I can try out or is it limited for roms aswell? also the airplane mode widget is kinda weird in v20 in that its not actually a widget its just a shortcut to the settings. :,(
EDIT:
um would you happen to know the version of rom that they changed the airplane mode an if I can go back to it without messing up the phone? is seems a minor annoyance to some but it is much less annoying to toggle a widget than constantly going in and out of the settings. thanks for all the help.
Related
Sup everybody. I was rooting my HTC Thunderbolt today and everything was going great....until I got to step 6 in the list. I put in the correct coding in ADB and got the correct MD5 info on output, but when I went to run the bootloader rewright i get the incorrect MD5 sum. Check it out: c:\android-sdk\tools>adb shell
# /data/local/busybox md5sum /data/local/hbooteng.nb0
/data/local/busybox md5sum /data/local/hbooteng.nb0
6991368ee2deaf182048a3ed9d3c0fcb /data/local/hbooteng.nb0
# dd if=/data/local/hbooteng.nb0 of=/dev/block/mmcblk0p18
dd if=/data/local/hbooteng.nb0 of=/dev/block/mmcblk0p18
2048+0 records in
2048+0 records out
1048576 bytes transferred in 0.415 secs (2526689 bytes/sec)
# /data/local/busybox md5sum /dev/block/mmcblk0p18
/data/local/busybox md5sum /dev/block/mmcblk0p18
bfa2f3ac5eb3bcf67af23509b4081999 /dev/block/mmcblk0p18
As you can tell the Green Numbers are correct according to the root guide but the red numbers were part of the incorrect MD5 sum
Now as far as I understand these are supposed to match....but even when everything was perfect up till this point it still screwed up!
Anybody got a clue to what I should do not to keep from bricking my phone?
Thanks in advance guys.
It appears that your downgrade did not stick according to your md5. Restart at step one.
Sent from my BAMF 2.0-5 Thunderbolt
Do not reboot
That is NOT the downgrade, that is the bootloader. DO NOT REBOOT your phone.
From the directions by jcase
jcase said:
If the output does not match "6991368ee2deaf182048a3ed9d3c0fcb," try again; if it still doesn’t work, seek help from chat.andirc.net in channel #root or go here AndIRC Thunderbolt Web Chat DO NOT REBOOT.
Click to expand...
Click to collapse
Try it one more time, if it doesn't work again, leave you phone plugged in so it doesn't die. Wait for an answer on IRC
Again DO NOT REBOOT
So I installed the latest ASUS firmware update (build 9.4.2.11) and lost root. I did not have OTA Rootkeeper (like an idiot) so I'm wondering if there is any way of re-rooting/restoring root without having to flash back to an earlier version.
If anyone can figure it out, it would be greatly appreciated.
You'll just have to wait until viperboy finds a way of rooting that firmware most likely. It shouldn't be too long.
I'm an idiot too.
Sent from my Transformer Prime TF201 using Tapatalk
I cringed as soon as I clicked that install button, but there was no way to cancel or stop the update to . . . soon as one of our awesome devs finds a new way to root, if any kind soul could post here to share the joy would be much appreciated.
zeusal said:
I cringed as soon as I clicked that install button....
Click to expand...
Click to collapse
I hang my head in shame also....
Made the same stupid move here
Looks like a lot of us in the same boat. Nothing to do but wait for a new root solution. I wish there was a way I could go back to previous version, root use OTA rootkeeper, then update. Other than that, the update is working great. Wifi signal seems to be a bit better, and I'm getting locks with GPS now.
Sent from my Transformer Prime TF201 using Tapatalk
Same thing here. Tried unrooting then rerooting using the viperboy primetime method and it didnt work. So now i just keep refreshing a bunch of different pages to see if anyone finds another way lol
Mea culpa etiam.
Sent from my Thunderbolt using Tapatalk
i was reading the root keeper as it was verifying the install, i was like NOOOOOOO
and well, you know the rest.
soon enough.
props to viper.
lets hope we have root again soon,
i do notice more stable wifi, it was going NUTS before the update, and now its great, and i already sideloaded my apps when i WAS rooted, so im kinda ok for a bit.
weeee,
loveing my prime, and cant wait for bootloader to be unlocked and get some stellar roms on this beast.
~k
I actually used ota root keeper, updated, and my update rendered it basically useless... I had no choice but to sideload it I guess at least now I have a functional tab again
For those who may have subscribed to this thread, good news if you are comfortable using ADB and shell.
I just used the stripped down version of ADB included with the previous one click root.
Testing that ADB has access
C:\Users\Zeusal\Downloads\TransformerPrimeRootICS>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ $ exit
exit
Executing commands from [ROOT] Mempodroid root - ICS including 9.4.2.11 I would have posted the below as feedback on actual thread to help those having issues troubleshoot, but I didn't have permission
C:\Users\Zeusal\Downloads\TransformerPrimeRootICS>adb push mempodroid /data/l
ocal
568 KB/s (37273 bytes in 0.064s)
C:\Users\Zeusal\Downloads\TransformerPrimeRootICS>adb push su /data/local
642 KB/s (22364 bytes in 0.034s)
C:\Users\Zeusal\Downloads\TransformerPrimeRootICS>adb shell chmod 777 /data/l
ocal/mempodroid
C:\Users\Zeusal\Downloads\TransformerPrimeRootICS>adb shell /data/local/mempo
droid 0xd9ec 0xaf47 mount -o remount,rw '' /system
C:\Users\Zeusal\Downloads\TransformerPrimeRootICS>adb shell
[email protected]:/ $ /data/local/mempodroid 0xd9ec 0xaf47 sh
/data/local/mempodroid 0xd9ec 0xaf47 sh
[email protected]:/ # cat /data/local/su > /system/xbin/su
cat /data/local/su > /system/xbin/su
[email protected]:/ # chown 0.0 /system/xbin/su
chown 0.0 /system/xbin/su
[email protected]:/ # chmod 06755 /system/xbin/su
chmod 06755 /system/xbin/su
[email protected]:/ # exit
exit
[email protected]:/ $ exit
exit
C:\Users\Zeusal\Downloads\TransformerPrimeRootICS>adb shell rm /data/local/me
mpodroid
C:\Users\Zeusal\Downloads\TransformerPrimeRootICS>adb shell rm /data/local/su
C:\Users\Zeusal\Downloads\TransformerPrimeRootICS>adb reboot
After Reboot
Launch Super User app if you were previously rooted, or else download it from the market
Execute from Options, "Su binary__Tap to check for updates", then update anyway to install busybox etc.
Root complete and functional, thank you very much for posting se1000!
The following guide should work for all loki-locked bootloaders, but I can only confirm that it worked on my D800. The problem I was having, was that loki_flash has been replaced with loki_tools, and there arent any guides out for loki_tools.
The right way to flash CWM requires you to generate your own recovery.lok from the aboot.img, and recovery.img (CWM) which you need to use loki_tools for.
PREREQUISITES
Device must be rooted
Device must be in Developer Mode
USB Debugging turned ON
Debugging RSA Signature must be accepted
Download CWM HERE
Download loki_tool HERE
Download ADB HERE
STEP 1 (Getting Files)
Follow this GUIDE to install ADB and FASTBOOT, once its complete, you will have adb installed to C:\adb
Download CWM, rename the file to 'recovery.img' (so its easier to work with) and move it to C:\adb
Download loki_tool and extract the file 'loki_tool' from the bin folder and place it in C:\adb
STEP 2 (Preparing for the Procedure)
Plug in your phone to the computer
In Windows Explorer, navigate to C:\
Shift+Right Click on the 'adb' folder, select 'Open command window here'
Type "adb devices" you should see:
Code:
C:\adb>adb devices
List of devices attached
<devid> device
If not, go back and turn on Develper Mode, USB Debugging, and accept the RSA Signature
STEP 3 (Flashing process)(note: I copied everything from the cmd prompt and edited it as a text file before thinking to post my procedure here, thats why it looks different)
In ADB type the following commands each step is commented out with what it does (someone could make it into a bat, but I'm too lazy.
Code:
// Sending recovery.img to device
C:\adb>adb push recovery.img /data/local/tmp/recovery.img
---------------
3456 KB/s (10510336 bytes in 2.969s)
---------------
// Sending loki_tool to device
C:\adb>adb push loki_tool /data/local/tmp/loki_tool
---------------
2777 KB/s (379248 bytes in 0.133s)
---------------
// entering Android Linux environment
C:\adb>adb shell
// sudo
[email protected]:/ $ su
// generating aboot.img
[email protected]:/ # dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img
---------------
2048+0 records in
2048+0 records out
1048576 bytes transferred in 0.072 secs (14563555 bytes/sec)
---------------
// changing permissions on aboot.img
[email protected]:/ # chmod 644 /data/local/tmp/aboot.img
// exiting Android Linux environment
[email protected]:/ # exit
[email protected]:/ $ exit
// saving aboot.img locally in case you need it again.
C:\adb>adb pull /data/local/tmp/aboot.img
---------------
2992 KB/s (1048576 bytes in 0.342s)
---------------
// entering Android Linux environment
C:\adb>adb shell
// changing directory
[email protected]:/ $ cd /data/local/tmp
// ls should list the following 3 files, if not, you are missing them and need to push them, or generate another aboot.img
[email protected]:/data/local/tmp $ ls
---------------
aboot.img
loki_tool
recovery.img
---------------
// changing the permissions of the files so loki_tool can use them
[email protected]:/data/local/tmp $ chmod 755 /data/local/tmp/loki_tool
[email protected]:/data/local/tmp $ chmod 755 /data/local/tmp/recovery.img
// executing loki_tool to generate the recovery.lok file
[email protected]:/data/local/tmp $ ./loki_tool patch recovery aboot.img recovery.img recovery.lok
---------------
Loki tool v2.1
[+] Detected target AT&T LG G2 build D80010o
[+] Original kernel address: 00008000
[+] Original ramdisk address: 05000000
[+] Writing device tree.
[+] Output file written to recovery.lok
---------------
// exiting Android Linux environment
[email protected]:/data/local/tmp $ exit
// Saving recovery.lok locally in case you need it again
C:\adb>adb pull /data/local/tmp/recovery.lok
---------------
2939 KB/s (10512384 bytes in 3.493s)
---------------
// entering Android Linux environment
C:\adb>adb shell
// sudo
[email protected]:/ $ su
// changing directory
[email protected]:/ $ cd /data/local/tmp
// flashing recovery.lok with loki_tool
[email protected]:/data/local/tmp # /data/local/tmp/loki_tool flash recovery /data/local/tmp/recovery.lok
---------------
Loki tool v2.1
[+] Loki validation passed, flashing image.
[+] Loki flashing complete!
---------------
// exiting Android Linux environment
[email protected]:/data/local/tmp # exit
[email protected]:/ $ exit
// reboot device into recovery
C:\adb>adb reboot recovery
---------------------------------
At this point your device should reboot into CWM, Congrats!
I know it's been 7 years, but this helped me get Magisk working on a locked bootloader. Thanks!
Platypus Enthusiast said:
I know it's been 7 years, but this helped me get Magisk working on a locked bootloader. Thanks!
Click to expand...
Click to collapse
I'm getting a "
Platypus Enthusiast said:
I know it's been 7 years, but this helped me get Magisk working on a locked bootloader. Thanks!
Click to expand...
Click to collapse
I keep getting "failed to find function to patch" error. Any thoughts?
Jackspsychosis said:
I'm getting a "
I keep getting "failed to find function to patch" error. Any thoughts?
Click to expand...
Click to collapse
I can do it for you if you like. I just need the aboot.img and the boot.img (or recovery.img) you're trying to patch.
Could I use this method to put a recovery on my lg g2 d802 (lollipop) on which it seems not to be any recovery (no command, when I press power+vol. down buttons) ?
TapaSte said:
Could I use this method to put a recovery on my lg g2 d802 (lollipop) on which it seems not to be any recovery (no command, when I press power+vol. down buttons) ?
Click to expand...
Click to collapse
I'm not sure if this is a good source, but maybe this might work:
Recovery Mode LG D802 G2, how to - HardReset.info
The Recovery mode it is the hidden feature which will enable a lot of useful operation.
www.hardreset.info
Platypus Enthusiast said:
I'm not sure if this is a good source, but maybe this might work:
Recovery Mode LG D802 G2, how to - HardReset.info
The Recovery mode it is the hidden feature which will enable a lot of useful operation.
www.hardreset.info
Click to expand...
Click to collapse
Like said, I've not recovery and if I press volume down + power I get "no command" screen.
First , your device must be S-OFF
S-off available now with Sunshine 3 and it's cost 25 $
1. Remove "Tampered flag"
Type following
adb devices
adb shell
su
echo -ne '\x00' | dd of=/dev/block/mmcblk0p6 bs=1 seek=5314564
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
Device boot into bootloader
Tampered is gone
2. Reset Bootloader to LOCKED
to LOCK bootloader, Type following: (recommended with using copy and paste or CTRL+C )
adb devices
adb shell
su
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
(recommended with using copy and paste or CTRL+C and paste)
exit
(exit twice until back to normal > prompt)
adb reboot bootloader
Device boot into bootloader
verify bootloader are now locked
3.UNLOCK bootloader
Following wint
adb devices
adb shell
su
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
(recommended with using copy and paste or CTRL+C and paste)
exit
(exit twice until back to normal > prompt)
adb reboot bootloader
verify bootloader are now unlocked
Really appreciate you putting this together1
If I ever RMA my phone I'm gonna appreciate it haha.
FoxyDrew said:
Really appreciate you putting this together1
If I ever RMA my phone I'm gonna appreciate it haha.
Click to expand...
Click to collapse
Haha this is just simple method , modified from M7 and M8
but it's worked as well
in case of it need .
Just a heads up these methods will work in Android Terminal Emulators from market just got to grant them root ( suggestions to copy and past echo line OP provides ) ... Also on newest Lollipop firmware the tampered flag still works but changes it to say software is official even if a custom rom and recovery are installed.
Sunshine 3 could be the cure for my headache **
Hi mytohn, sorry if this is the wrong way to contact you, but...
where can I get the program you are talking about (Sunshine 3)???
I need it for trying out if it will remove "Relocked" which HTC was so kind to demand for allowing me to install a RUU, and NOW I'M REALLY LOCKED =|:→$
↓ ↓☼↓ ↓
< S-off available now with Sunshine 3 and it's cost 25 $ >
mytohn said:
First , your device must be S-OFF
*****************************************************************
1. Remove "Tampered flag"
Type following
adb devices
adb shell
su
echo -ne '\x00' | dd of=/dev/block/mmcblk0p6 bs=1 seek=5314564
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
Device boot into bootloader
Tampered is gone
2. Reset Bootloader to LOCKED
to LOCK bootloader, Type following: (recommended with using copy and paste or CTRL+C )
adb devices
adb shell
su
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
(recommended with using copy and paste or CTRL+C and paste)
exit
(exit twice until back to normal > prompt)
adb reboot bootloader
Device boot into bootloader
verify bootloader are now locked
3.UNLOCK bootloader
Following wint
adb devices
adb shell
su
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
(recommended with using copy and paste or CTRL+C and paste)
exit
(exit twice until back to normal > prompt)
adb reboot bootloader
verify bootloader are now unlocked
Click to expand...
Click to collapse
Sc0rpio said:
Hi mytohn, sorry if this is the wrong way to contact you, but...
where can I get the program you are talking about (Sunshine 3)???
I need it for trying out if it will remove "Relocked" which HTC was so kind to demand for allowing me to install a RUU, and NOW I'M REALLY LOCKED =|:→$
↓ ↓☼↓ ↓
< S-off available now with Sunshine 3 and it's cost 25 $ >
Click to expand...
Click to collapse
You can find it out here and it cost 25 bucks
Cheers
http://theroot.ninja/
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.