5,595,760 Members 39,101 Now Online
XDA Developers Android and Mobile Development Forum

[GUIDE] Rumrunner S-OFF for HTC Desire V (T328w, Wind)

Tip us?
 
mr.wasssup
Old
#21  
mr.wasssup's Avatar
Member - OP
Thanks Meter 14
Posts: 31
Join Date: Jul 2013
Quote:
Originally Posted by piousheart View Post
LONG STORY SHORT - I GOT S-OFF EVEN AFTER RUMRUNNER FAILED!!!

I forgot to root the phone & relocked BL now i want root on Stock ROM how can reunlock it & than lock it again?
You are not first & not last, to whom Rumrunner done his job even if said "failed"...

Please, read carefully 2-d post "New possibilities with S-OFF" where you'll find how to change the status of the Bootloader Locked/Unlocked/Relocked

About that Notice. It`s not my own. It`s originally from the Rumrunner official site (bottom of the page, marked (**3**) & from this HTC Desire X thread.
Yes, it's just a bug without any hard bricks of what ever. I`m using my phone with S-OFF for 3 months and everything is OK.
The Following User Says Thank You to mr.wasssup For This Useful Post: [ Click to Expand ]
 
Inspect
Old
(Last edited by Inspect; 12th April 2014 at 05:02 PM.)
#22  
Junior Member
Thanks Meter 0
Posts: 6
Join Date: Dec 2009
Default Bootloader shows S-OFF... but actually it is NOT !?

Quote:
Originally Posted by piousheart View Post
LONG STORY SHORT - I GOT S-OFF EVEN AFTER RUMRUNNER FAILED!!!
Are you sure that you actually have S-OFF? Have you tested if it works by f.ex. changing your CID or flashing a new radio?
Does it sound like a silly question?... read on and you will know why I ask.

I too had a similar experience as you describe, and my bootloader now says that the phone is S-OFF, but I am still unable to change CID or flash a new radio (or even flash a new splash screen for that matter)!

My phone is the China Unicom branded HTC T328w (CID=HTCCN703) running on system and kernel images from hTC_Asia_TW_1.74.709.6 (CID=HTC__621) by use of "Pseudo flashing" method described elsewhere on this forum.

Some version details from before i attempted to run RumRunner the first time:
Kernel version: 3.0.16-g720e41b root@ABM022#1 PREEMPT
Baseband version: 1.10.34D.17_20.26.30.27U
Build number: 1.74.709.6 CL116923 release-keys
Bootloader info: Unlocked / S-ON / HBOOT-1.14.0002 / RADIO-1.10.34D.17
Recovery: CWM v5.8.3.1
Rooted with: SuperSU-v1.25
So here is the "short" version of what I tried:

Step 1:
  • Ran 'rumrunner_proto_0.7.1' with phone as described above
Result: FAILED! - No description of why it failed... just showing:
==================== rumrunner S-OFF 0.7.1 ==============================

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 (8/120)
Waiting
Test 2: Booting device
Waiting for ADB (22/120)
must ferment longer...

must sanitize, skunky rum is nasty
hold please............................................ .................
[TTTT********************************************** **********]
Press ENTER to exit
Step 2:
  • Flashed 'RUU_PRIMO_DS_ICS_40A_HTCCN_CHS_CU_1.71.1402.1_Rad io_1.07.34D.17_20.24.30.25U_release_272837_signed. exe' (this is the stock ROM my phone came shipped with)
  • Ran 'rumrunner_proto_0.7.1' again
Result: FAILED! - Showing:
==================== rumrunner S-OFF 0.7.1 ==============================

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 (6/120)
Waiting
Test 2: Booting device
Waiting for ADB (21/120)
must ferment longer...

must sanitize, skunky rum is nasty
hold please............................................ .................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (6/120)
Waiting for ADB (20/120)
must ferment longer...

chilling..................
it's a little stinky here, hmm....

heh, just a shot glass for this one....
bottles are packed, here we go, shhhhhh....

hmm, cap is on tighter than I expected........
heh, just a shot glass for this one....
pouring (1)...........................
unfortunately this isn't going to work out with your configuration. you have 2 options:
1.) flash an unsecure kernel that's compatible with your ROM and retry rumrunner (preferred and most reliable method).
2.) flash a different rom.
NOTE: No amount of messing around with su binaries and apk's is going to fix this issue for you!!!.
Better luck next time!!!!bye
Press ENTER to exit
Step 3:
  • Tried running the generic version of RumRunner (rumrunner_HTC_0.5.0) instead, as their website suggest that it doesn't necessarily need an unsecure kernel to work.
Result: FAILED! - Showing similar output as in Step 2 above:
==================== 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 (11/120)
Waiting
Test 2: Booting device
Waiting for ADB (25/120)
must ferment longer...

must sanitize, skunky rum is nasty
hold please............................................ ..
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (11/120)
Waiting for ADB (26/120)
must ferment longer...

chilling..................
it's a little stinky here, hmm....

bottles are packed, here we go, shhhhhh....

hmm, cap is on tighter than I expected........
pouring (1)...........................
unfortunately this isn't going to work out with your configuration. you have 2 options:
1.) flash an unsecure kernel that's compatible with your ROM and retry rumrunner (preferred and most reliable method).
2.) flash a different rom.
NOTE: No amount of messing around with su binaries and apk's is going to fix this issue for you!!!.
Better luck next time!!!!bye
Press ENTER to exit
Step 4:
  • Based on hellolalalam's sucess with Baidu ROM v5.1 (in post #16), I decided to give that a try.
  • But since it was getting late, and my Chinese is "somewhat rusty" I decided not to struggle with understanding the (Chinese only) Baidu ROM flash tool, and instead just flash the Baidu Kernel image via fastboot (since what I needed was just an unsecure kernel, and the Baidu ROM only appears to contain System, Kernel and Recovery anyways)
  • After successfully flashing the Baidu Kernel, I rebooted the phone... and noticed that it vibrated 7 times during boot! ...hmm!?
  • I then ran 'rumrunner_proto_0.7.1' again, and saw that:
    1. the bootloader was now showing the CID when RumRunner was performing "Test 1: Rebooting into bootloader". I was too focused on this to actually notice if it said S-ON or S-OFF in the top of the bootloader screen.
    2. the bootloader was indeed showing S-OFF the second time when RumRunner was performing "Rebooting into bootloader (again)"!
  • Then waited until RumRunner completed (sucessfully...)
Result: SUCCESS! - Showing:
==================== rumrunner S-OFF 0.7.1 ==============================

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 (5/120)
Waiting
Test 2: Booting device
Waiting for ADB (26/120)
must ferment longer...

must sanitize, skunky rum is nasty
hold please............................................ .................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (5/120)
Waiting for ADB (25/120)
must ferment longer...

chilling..................
it's a little stinky here, hmm....

heh, just a shot glass for this one....
bottles are packed, here we go, shhhhhh....

hmm, cap is on tighter than I expected........
heh, just a shot glass for this one....
pouring (1).......
Waiting for ADB (25/120)
must ferment longer...

what's that in the bottle still? rum foul, sloppy, real sloppy...
heh, just a shot glass for this one....
wait for it.........
yep, done. Hope you enjoyed the rum!
Don't forget to send us all your money - rumrunnerdevs@gmail.com
Press ENTER to exit
Click image for larger version

Name:	bootloader.jpg
Views:	12
Size:	81.5 KB
ID:	2682053

'fastboot getvar all' also shows 'security: off'
Code:
c:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.14.0002
(bootloader) version-baseband: 1.10.34D.17
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) serialno: MB335PGxxxxx
(bootloader) imei: 353638058xxxxxx
(bootloader) product: primods
(bootloader) platform: HBOOT-7227A
(bootloader) modelid: PL1110000
(bootloader) cidnum: HTCCN703
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: HTC
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-13a92e98
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.010s
But when I try to change CID it gives me 'Command error':
Code:
c:\Android>fastboot oem writecid 11111111
...
(bootloader) [ERR] Command error !!!
OKAY [  0.010s]
finished. total time: 0.010s
When I try to flash a new radio or a new splash screen it fails:
Code:
c:\Android>fastboot flash splash1 splash1.nb0
sending 'splash1' (768 KB)...
OKAY [  0.260s]
writing 'splash1'...
FAILED (remote: not allowed)
finished. total time: 0.270s

c:\Android>fastboot flash radio radio_1_10_34D_17.img
sending 'radio' (21376 KB)...
OKAY [  3.000s]
writing 'radio'...
FAILED (remote: not allowed)
finished. total time: 3.000s

My guess is that the "failed" attempts in Step 2 and/or Step 3 has made some (but NOT all) of the changes needed for S-OFF, but that these changes for some reason don't take effect until you flash something else onto the phone (in my case the Baidu Kernel, and in piousheart case the stock ROM).
The following "successful" attempt in Step 4 then (maybe) skips some crucial steps, because of the changes that were already done during Step 2/3!?... I don't know...


The question now is how do I get my phone back to S-ON, so that I can get a fresh start?
Or alternatively, is there a way (command line option, or something) to 'force' RumRunner to go through all the steps required for S-OFF?

Any help or advice on how to proceed from here will be greatly appreciated!
 
piousheart
Old
#23  
Senior Member
Thanks Meter 73
Posts: 698
Join Date: Mar 2012
Actually after having a failed rumrunner i got S-off and also the phone started vibrating on every boot.
I also changed splash screen with success and no red texts.
but i still dont know it really s-off or not i never tried things.

The reason of unlocking BL - root & performing s-off is my primos-ds is having a random reboot problem several times a day no matter if i am using it or not, sometimes it also reboots at late night when family sleeping at night

I thought of flashing the phone with stock rom to solve the problem but it still happens & i am so frustrated of this crap that i am gonna fCuk this device with a drill (may be i will make a video of that)

Also went to service center but those monkeys at there just flashes the phone and gives it back

ITS A CRAP CRAP CRAP!!!!!!!!!!

NO HTC FROM NOW
Only SONY OR GOOGLE NEXUS.
- Take a chance, you never know how perfect something can turn out!
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes