• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Moonshine s-off for k2_cl [BOOST]

I'm struggling a bit getting through all of the second test distiller runs; I've run the htc bootloader unlocker and have twrp installed (My bootloader reads 'tampered' and 'unlocked'). I've removed htc sync and any drivers referencing it. I have the full android sdk suite installed and can run adb and fastboot from the command line (using Windows). I'm running Jellybean (4.2.2) with hboot 2.21 on an htc one sv (k2_cl). I'm running moonshine from inside the platform-tools folder.
I've found that if I run distiller and leave the phone alone, it'll reboot it and put it into fastboot usb. It detects fastboot, then says that it's booting it back into the normal mode and then it waits for an ADB check. If I unplug and remove the battery from the phone and reconnect it, then it'll go through the ADB check fine. It goes back to fastboot once more, and I repeat the process of unplugging it and reconnecting it. At this point I get the following error:

!! Do NOT for any reason touch, unplug, lick or maim your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
[PL8011000-2.21.0000]
Test 2: Booting device
Waiting for ADB (53/120)
Test 2.1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
Waiting for ADB (69/120)
ERROR: Make sure that device is htcdev.com unlocked and run distiller again!!
Press ENTER to exit

I'm at something of a loss as to what exactly I'm doing wrong. Anybody have any ideas?

Update: I've switched over to a linux live cd and have been trying to make progress on this with the universal s-off tool made by rumrunners. Moonshine gives the same response as on PC. I get the following error after running soju:

Please wait....
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (6/120)
Waiting
Test 2: Booting device
Waiting for ADB (19/120)
must ferment longer...

must sanitize, skunky rum is nasty
hold please..............................................
[************************************************************]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
FATAL: Download updated package at www.rumrunner.us
 
Kurozen said:
I'm struggling a bit getting through all of the second test distiller runs; I've run the htc bootloader unlocker and have twrp installed (My bootloader reads 'tampered' and 'unlocked'). I've removed htc sync and any drivers referencing it. I have the full android sdk suite installed and can run adb and fastboot from the command line (using Windows). I'm running Jellybean (4.2.2) with hboot 2.21 on an htc one sv (k2_cl). I'm running moonshine from inside the platform-tools folder.
I've found that if I run distiller and leave the phone alone, it'll reboot it and put it into fastboot usb. It detects fastboot, then says that it's booting it back into the normal mode and then it waits for an ADB check. If I unplug and remove the battery from the phone and reconnect it, then it'll go through the ADB check fine. It goes back to fastboot once more, and I repeat the process of unplugging it and reconnecting it. At this point I get the following error:

!! Do NOT for any reason touch, unplug, lick or maim your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
[PL8011000-2.21.0000]
Test 2: Booting device
Waiting for ADB (53/120)
Test 2.1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
Waiting for ADB (69/120)
ERROR: Make sure that device is htcdev.com unlocked and run distiller again!!
Press ENTER to exit

I'm at something of a loss as to what exactly I'm doing wrong. Anybody have any ideas?

Update: I've switched over to a linux live cd and have been trying to make progress on this with the universal s-off tool made by rumrunners. Moonshine gives the same response as on PC. I get the following error after running soju:

Please wait....
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (6/120)
Waiting
Test 2: Booting device
Waiting for ADB (19/120)
must ferment longer...

must sanitize, skunky rum is nasty
hold please..............................................
[************************************************************]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
FATAL: Download updated package at www.rumrunner.us
Click to expand...

You will definitely have to use rumrunner and not moonshine. Plug your device in to your computer, open up terminal and type then enter:
Code: 
adb devices

If your device serial number shows up then you are good. If it does not then you must resolve this by ensuring your system is communicating with your device and vice versa.

If it is indeed working then go ahead and boot in to your bootloader. You should see, usb fastboot, in red text. While still in your terminal type and enter:
Code: 
fastboot devices

You should see your devices serial number be displayed.

If neither are being displayed then you will not be able to S-Off because your computer and the phone are not communicating. This will result to insuring you have the proper drivers installed.

May I suggest dumping windows altogether and installing linux ;-)
 
When I put those into command prompt I get:

Code: 
c:\android-sdk>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT342SXXXXX    device


c:\android-sdk>fastboot devices
HT342SXXXXX    fastboot

May I suggest dumping windows altogether and installing linux ;-)
Click to expand...

I'd be happy to jump over to linux.
 
Are you rooted? If so, do you lose root at any point in time after rebooting the device? If yes, then a custom kernel to insure you don't lose root may be required. The kernel from the TWRP recovery I built comes with HTC write protection removed. Unpack the custom recovery image and grab the kernel. Now, unpack your boot.img. swap the kernel binaries. Rebuild your boot.img. Flash your boot.img. All that HTC write protection stuff should be properly disabled now and you shouldnt lose root at this point.

Try rumrummer again.
 
If the device is S-Off then you wouldn't really be able to tell. Those who are S-On would really see the difference. I say try his kernel out. If it fails, then there is my solution.

I have contacted SimonSickle over on XDA. I have been busy so I have requested if he could build a simple kernel with write protection removed and what not so users would be able to do what they needed to do on their device. He has obliged to do it but I am not putting pressure on him over this.
We shall see :-)
 
ModdingMyMind said:
Are you rooted? If so, do you lose root at any point in time after rebooting the device? If yes, then a custom kernel to insure you don't lose root may be required. The kernel from the TWRP recovery I built comes with HTC write protection removed. Unpack the custom recovery image and grab the kernel. Now, unpack your boot.img. swap the kernel binaries. Rebuild your boot.img. Flash your boot.img. All that HTC write protection stuff should be properly disabled now and you shouldnt lose root at this point.

Try rumrummer again.
Click to expand...

I haven't lost root, but my phone is S-ON and that sounds really cool; I'll try switching over to that kernel. I'm looking at your guide here (http://androidforums.com/one-sv-all-things-root/845477-development-unofficial-twrp-k2_cl.html). What command do I use to unpack the custom image to get the kernel and boot.img? I used
Code: 
 sudo fastboot flash recovery K2_CL_TWRP_2.7.1.0d_Extended.img
but I'm wondering if that's the wrong way to be going about it.
 
Kurozen said:
I haven't lost root, but my phone is S-ON and that sounds really cool; I'll try switching over to that kernel. I'm looking at your guide here (http://androidforums.com/one-sv-all-things-root/845477-development-unofficial-twrp-k2_cl.html). What command do I use to unpack the custom image to get the kernel and boot.img? I used
Code: 
 sudo fastboot flash recovery K2_CL_TWRP_2.7.1.0d_Extended.img
but I'm wondering if that's the wrong way to be going about it.
Click to expand...

This guide basically allows the ability to unpack and repack on your device. However, just use this guide for general purposes.

http://androidforums.com/showthread.php?t=811999
 
I took apart the two boot images and swapped the kernel from the K2_CL_TWRP_2.7.1.0d_Extended.img into my boot image, recompiled it, and flashed it via fastboot. I'm still getting a failed result from the HTC Dumlock and rumrunner. :/ Thoughts?
 
Kurozen said:
I took apart the two boot images and swapped the kernel from the K2_CL_TWRP_2.7.1.0d_Extended.img into my boot image, recompiled it, and flashed it via fastboot. I'm still getting a failed result from the HTC Dumlock and rumrunner. :/ Thoughts?
Click to expand...

Well, assuming your device is properly prepped as per instructions from the rumrunner website then the only other thing it may be is their server could be down. Internet access without any virus protection or firewalls is a must or it won't work period. However, with that said, if their server is down that could cause an issue.
 
I see. Would the htc dumlock application be reporting a failure if it had already previously succeeded? Also, would there be any benefits of writing the boot.img via a dd command?
 
Kurozen said:
I see. Would the htc dumlock application be reporting a failure if it had already previously succeeded? Also, would there be any benefits of writing the boot.img via a dd command?
Click to expand...

Because you are S-On you won't be able to write using DD if my memory serves me correctly - I have been S-Off for so long now lol.

Try it, and if it fails, then try it from within the TWRP recovery and see what happens.

To write the boot.img to the boot partition:
Code: 
dd if=/sdcard/boot.img of=[B]/dev/block/mmcblk0p20[/B]
 
Kurozen said:
I see. Would the htc dumlock application be reporting a failure if it had already previously succeeded? Also, would there be any benefits of writing the boot.img via a dd command?
Click to expand...

HTC Dumlock Instructions:
HTC Dumlock Instructions specifically for S-On users but S-Off users can use it as well if they choose to:

1. Install the build of TWRP using your method of choice, but you must actually flash TWRP to recovery.* No fastboot booting it.* We need it in recovery so that this build of TWRP will be flashed to your boot.* This new build of TWRP has features in it to easily restore your original boot.

2. Reboot into recovery.

3. Make a backup of your phone.

4. Tap Advanced.

5. Tap HTC Dumlock. (If you don't see HTC Dumlock then you need to remove any custom TWRP theme that you might be using.)

6. Tap Install HTC Dumlock.* This will install the app and binaries needed to make everything work nicely.

7. Reboot your device.

8. Find and open the HTC Dumlock app.

9. If/when prompted, give the app root (SuperUser) permissions.

10. Tap the Execute HTC Dumlock button.

11. Wait patiently for a couple of minutes.* It takes a little while.
If your device doesn't reboot automatically, reboot it manually.* Reboot it normally.* DO NOT reboot it to recovery.
You should now be in your recovery, but your recovery is flashed into boot.

12. Tap Advanced.

13. Tap HTC Dumlock.

14. Tap Restore Original Boot.

Use your recovery like normal.* Flash a new kernel.* Restore a backup with a different kernel.* Do whatever you please!
 
ModdingMyMind said:
Because you are S-On you won't be able to write using DD if my memory serves me correctly - I have been S-Off for so long now lol.

Try it, and if it fails, then try it from within the TWRP recovery and see what happens.

To write the boot.img to the boot partition:
Code: 
dd if=/sdcard/boot.img of=[B]/dev/block/mmcblk0p20[/B]
Click to expand...


Tried writing to the boot partition both from within the OS, from within recovery using terminal, and from bootloader using fastboot; it seems it worked in all three cases, but I'm still getting the failed result from the htc dumlock app and the rumrunner's soju process. :/

When I run the HTC Dumlock app, I immediately get "Operation complete! Result was (fail) if it doesn't rebooot automatically, you will have to reboot manually."

And Supersu flashes the "HTC Dumlock has been given superuser permission for an interactive shell" notice.
 
also having trouble gaining s-off.. boost htc one sv k2_cl hboot is 2.21 jb 4.2.2
both adb and fastboot enabled and phone unlocked.. have tried both rumrunner and firewater.. firewater got to the permissions then returned the "whelp, this sucks, firewater can not work on your device" message and rumrunner gets stuck here:

==================== rumrunner S-OFF 0.5.0 ==============================

rumrunner S-OFF comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for users
however the authors disclaim any liability for damage to your phone
or other materials or devices used during this process.

The entire risk of running rumrunner S-OFF lies with you, the user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever caused.

Do you understand the implications of this warning?
(Yes/No)
Yes

Dear User: We will expect that YOU:
(1) Know how to use ADB and FASTBOOT binaries
---- [Yes, use these tools to test USB connection BEFORE running rumrunner] ----

(2) Realize that rumrunner S-OFF cannot support every CUSTOM rom in this world
(3) Understand that irc support IS NOT A GENERAL HELPDESK
(4) Are able to identify and download the CORRECT package for YOUR device
(5) Know how to enable USB-debugging on YOUR device (Yes, do that now)
(6) Understand that you may NOT repack or redistribute rumrunner S-OFF

Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (12/120)
Waiting
Test 2: Booting device
Waiting for ADB (23/120)
must ferment longer...

must sanitize, skunky rum is nasty
hold please..............................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (12/120)
FATAL: Download updated package at www.rumrunner.us
Press ENTER to exit
 
BHoller said:
Yes. Rumrunner 0.5.0
Click to expand...

You must be the same guy looking for assistance over on XDA :-). Welcome to AF. Could you refresh my memory by informing me if you have USB debugging turned on? See picture below for visual clarity.

8usapy7e.jpg
 
BHoller said:
Yes debug mode is on.. and yes, same guy
Click to expand...

Ok, you have USB debugging turn on.

You have working adb and fastboot binaries.

You have communication with your device and your computer.

You have a internet connection with your computer while running rumrunner.

You have any and all anti software's turned completely off.

You have no lockscreen/password/encryption turned on for your device (all is disabled).

Your device is rooted.

You have the proper drivers installed (with regards to using windows).

Going off the top of my head, you should not be having any trouble. My only assumption is you missed a step somewhere and it is giving you problems. My suggestion would be to go over the check list provided as info over on the rumrunner website and insure you have accomplished all tasks before proceeding using rumrunner.
 
BHoller said:
Yes to all and have followed the instructions.. even firewater failed
Click to expand...

Nevertheless, I would double check just in case by a slight smidge of chance that you did overlook something.

It can happen, if you have ever written scripts before you will know what I mean lol.
 
Hmm, well, I seem to be without any further ideas at the moment. Shame I can't give an absolute solution for you.... You and the guy above are about the only ones I know who have had this trouble. Many others have been rather successful after they get guidance to double check everything which tends to lead to something small being overlooked.
 
You must log in or register to reply here.
Back
Top Bottom