Hello everyone!
Here's the short version:
I want to s-off my htc one xl using rumrunner. However, every time I run the sudo ./sujo (linux) script, I always get the same error:
Code:
ERROR: run rumrunner again and READ (no adb connection to device. Debugging on? Drivers?)
I have checked my fastboot and adb connections and they all work fine. I have also enabled root permissions for adb and applications, usb debugging and the 'adb over network' options in the 'developer options' menu of CM12.
Here is a more detailed step-by-step of what I do:
First, I check the adb connection with "adb devices": (I've also tried other commands, just to make sure everything's OK)
Code:
:~/Android/rumrunner_HTC_0.5.0$ adb devices
List of devices attached
HT248W301724 device
Second, I run the "soju" program in the rumrunner download file:
Code:
:~/Android/rumrunner_HTC_0.5.0$ sudo ./soju
==================== 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....
ERROR: run rumrunner again and READ (no adb connection to device. Debugging on? Drivers?)
Here's some info on my device, if it helps:
CM version:
12.1-20151007-SNAPSHOT-YOG4PAO332-evita
Android Version
5.1.1
Baseband version:
0.23a.32.09.29_10.128.32.34aL
Kernel version:
3.4.105-ga346a29
[email protected] #1
Build number
cm_evita-usrdebug 5.1.1 LMY48B 37126a8090
test-keys
Also, here is my HBOOT info (shouldn't help, but I'll throw it on anyway just in case someone finds something!):
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT - 2.14.0000
RADIO-0.23A.32.09.29
OpenDSP - v31.1.0.45.0815
eMMC-boot
Nov 26 2012, 18:37:14:-1
I tried running the rumrunner script before flashing CM (i.e. while I was still using the stock HTC rom) and it worked all the way up to the "your phone is not rooted" part, at which time I flashed TWRP recovery onto my phone and flashed straight into CM (figuring it wouldn't make much of a difference).
I don't really want to get into the whole RUU mess. Anyone know what's going on here? How do I fix this adb issue? Help?
EDIT:
I fixed the adb problem I encountered above by using the following command:
Code:
adb kill-server
and then running
Code:
sudo ./soju
however, on CM12, I could only get to this point in the rumrunner program:
Code:
==================== 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 (8/120)
Waiting
Test 2: Booting device
Waiting for ADB (67/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[************************************************************]
Rebooting into bootloader (again)
Waiting for fastboot (8/120)
Waiting for ADB (18/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........
hell, that damn cap is on REALLY tight.......
pouring (1)...
WTF: What are you doing?
I wasn't sure what the problem was, so I downloaded and ran the "sunshine" (formerly "firewater") apk on my phone (I didn't pay for it, I just downloaded it to see what it was about). Then, in the initialisation process it produced an error saying that my current rom is not "similar enough to the stock rom" to run the program successfully. Then, I looked for a "more simiar rom" -- in the end I flashed Kickdroid 5.0.
After flashing Kickdroid, I selected the required options (usb debug, supersu -- which I flashed manually, etc.). Then I checked to see if adb was running (it was), and then ran the kill-server command listed above. After that, I ran rumrunner with no issues!
Code:
adb kill-server
Code:
==================== 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 (8/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 (8/120)
Waiting for ADB (20/120)
must ferment longer...
chilling..................
smells lovely in here....
bottles are packed, here we go, shhhhhh....
pouring (1)...................
pouring (2)..............
pouring (3)........
Waiting for ADB (17/120)
must ferment longer...
what's that in the bottle still? rum foul, sloppy, real sloppy...
wait for it.........
yep, done. Hope you enjoyed the rum!
Don't forget to send us all your money - [email protected]
I am now s-off (yay me!)
Related
Hello there, I was trying to root my Htc Sensation XE, these are the specs:
Bootloader locked
PYRAMID PVT SHIP S-ON RL
eMMC-Boot
Android Version: 4.0.3
HTC Sense Version: 3.6
Software Number: 3.33.401.106
Kernel Version: 3.0.16-g31a4fc7 [email protected]#1 SMP PREEMPT
Baseband Version: 11.76A.3504.00U_11.24A.3504.31_M
Build Number: 3.33.401.106 CL391535 release-keys
Browser Version: WebKit/534.30
I need immediate help on this issue. My hboot is on 1.29 and when i searched for S-OFF , i got mostly 2 methods. One was from htcdev.com to unlock the bootloader via htc site, but somehow i've been experiencing issues with the site (Whenever i log in, i'm logged out like 2-3 seconds later..). That leaves the other method, the one requiring the wire trick.. I've tried that so many times now, every time it says:
Do not remove sdcard from phone
Do wire-trick now!! Look instructions at web
Waiting device....
Found device... Please wait...
Getting into bar.....
Raising Glass
SUCCESS - Taking a sip.
SUCCESS - Beer is tasty.
SUCCESS - Beer is tasty.
SUCCESS - Beer is tasty.
SUCCESS - Beer is tasty.
SUCCESS - Buddies and Beer
Checking alcohol level......
Let's take one more......
S-OFF Failed
Errorcode: 66732337
ErrorMsg: Still sober
Quit....
Press ENTER to exit.....
I'm really worried, as i want to do a Custom ROM as soon as possible, but am really confused what to do.. Please help!!
hammadfozi said:
Hello there, I was trying to root my Htc Sensation XE, these are the specs:
Bootloader locked
PYRAMID PVT SHIP S-ON RL
eMMC-Boot
Android Version: 4.0.3
HTC Sense Version: 3.6
Software Number: 3.33.401.106
Kernel Version: 3.0.16-g31a4fc7 [email protected]#1 SMP PREEMPT
Baseband Version: 11.76A.3504.00U_11.24A.3504.31_M
Build Number: 3.33.401.106 CL391535 release-keys
Browser Version: WebKit/534.30
I need immediate help on this issue. My hboot is on 1.29 and when i searched for S-OFF , i got mostly 2 methods. One was from htcdev.com to unlock the bootloader via htc site, but somehow i've been experiencing issues with the site (Whenever i log in, i'm logged out like 2-3 seconds later..). That leaves the other method, the one requiring the wire trick.. I've tried that so many times now, every time it says:
Do not remove sdcard from phone
Do wire-trick now!! Look instructions at web
Waiting device....
Found device... Please wait...
Getting into bar.....
Raising Glass
SUCCESS - Taking a sip.
SUCCESS - Beer is tasty.
SUCCESS - Beer is tasty.
SUCCESS - Beer is tasty.
SUCCESS - Beer is tasty.
SUCCESS - Buddies and Beer
Checking alcohol level......
Let's take one more......
S-OFF Failed
Errorcode: 66732337
ErrorMsg: Still sober
Quit....
Press ENTER to exit.....
I'm really worried, as i want to do a Custom ROM as soon as possible, but am really confused what to do.. Please help!!
Click to expand...
Click to collapse
No man, you have understood it wrong.
1)You should UNLOCK YOUR BOOTLOADER with HTCdev website. If you do not unlock your bootloader you won't be able to do the next steps
2)Install the recovery with fastboot
3)Root
4)S-Off with Juopunutbear.
5)SuperCID if you want to
6)Custom ROM
That's the order of things, don't change it, or you'll face problems. Try the HTCDev website untill you unlock the bootloader
Read THIS thread, it has everything you need. It's for hboot 1.27, but it works with 1.29
actually he can do the juopunutbear method for S-OFF without using the HTCdev website
but yes first root
Just keep trying.
rzr86 said:
actually he can do the juopunutbear method for S-OFF without using the HTCdev website
but yes first root
Click to expand...
Click to collapse
Juopunutbear Prerequisites:
* Be unlocked using the HTCdev bootloader unlock.
* Be rooted (have superuser and/or an unsecured boot image installed)
* Have a spare microSD card or back up all contents of your SDcard
* Have fastboot and adb drivers installed and working (windows)
* Have usb debugging enabled
* Have a length of insulated wire of sufficient length to join the contact points for your device (paperclip)
At least that's the only way I know to do it
elvisypi said:
Juopunutbear Prerequisites:
* Be unlocked using the HTCdev bootloader unlock.
* Be rooted (have superuser and/or an unsecured boot image installed)
* Have a spare microSD card or back up all contents of your SDcard
* Have fastboot and adb drivers installed and working (windows)
* Have usb debugging enabled
* Have a length of insulated wire of sufficient length to join the contact points for your device (paperclip)
At least that's the only way I know to do it
Click to expand...
Click to collapse
yes i have seen that and i had been confused for some period but i read from some users to tell that it is unecessary to do it if you want to S-OFF with juopunutbear method.nevermind
elvisypi said:
Juopunutbear Prerequisites:
* Be unlocked using the HTCdev bootloader unlock.
* Be rooted (have superuser and/or an unsecured boot image installed)
* Have a spare microSD card or back up all contents of your SDcard
* Have fastboot and adb drivers installed and working (windows)
* Have usb debugging enabled
* Have a length of insulated wire of sufficient length to join the contact points for your device (paperclip)
At least that's the only way I know to do it
Click to expand...
Click to collapse
There is a version that doesnt need htcdev unlock as well - you just need to find it:
unlimited.io/jb_pyramidlocked.htm
Jonny said:
There is a version that doesnt need htcdev unlock as well - you just need to find it:
unlimited.io/jb_pyramidlocked.htm
Click to expand...
Click to collapse
+1
And there is a guide for it too ..Link in my signature
Sent from my HTC Sensation 4G using xda premium
---------- Post added at 09:57 AM ---------- Previous post was at 09:54 AM ----------
@OP
You just had wire trick failed.... That's all.. Keep trying..
Reduce the pause tome a bit and see
0.5 sec tap - - - 1.5 sec pause - - - 0.5 sec tap
Sent from my HTC Sensation 4G using xda premium
ganeshp said:
You just had wire trick failed.... That's all.. Keep trying..
Reduce the pause tome a bit and see
0.5 sec tap - - - 1.5 sec pause - - - 0.5 sec tap
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
actually you have been confused with the other user.i'm not trying nothing
Hey Folks,
This is my first post in the Sensation forums, i've been reading topics for a few days, but I didn't find any solution to my problem and i'm starting to get annoyed by it.
I've obtained a HTC Sensation a few days ago, and as with my previous devices (Galaxy Gio, Optimus Black) I wanted to flash a custom rom on it. I happened to unlock the bootloader of my friends Sensation few weeks earlier, so i thought this was going to be a piece of cake.
Well it wasn't, I couldn't unlock the bootloader using HTCdev method because the phone is vodafone branded. I tried numerous things, i wasn't able to perform the juopeanutbro (?) trick, tried flashing a custom hboot through fastboot (JB_hboot.zip) in linux (gave me an error 42 "Remote: Custom id check failed" or something like that). And after a few days of trying and trying i'm getting tired of it.
So my question is, is there any option i missed to achieve S-OFF or unlock bootloader? I'd love to flash a custom rom on it because I don't like the 4.0.3 Firmware which the phone is running now.
Phone Details:
Android version: 4.0.3 (vodafone)
HBOOT:1.27.0000
Radio: 11.29A.3504.18_M
CID:VODAPE17
Did you select the Vodafone model there in list of HTC dev...
Sent from my HTC Sensation XE with Beats Audio Z715e using XDA Premium 4 mobile app
Ihttp://forum.xda-developers.com/showthread.php?t=1668276
If htc Dev method doesn't work for your phone, use the non htc Dev method. Follow everything on the screen, do not run out of battery power (that will probably brick your phone)
Yes I did select the vodafone model, and I end up with the "failed" error when flashing unlock_code.bin. I don't understand why the HTCdev method doesn't work in the first place. And the method described by stillsober requires the almost impossible wire-trick.. Well i'm afraid there is no other method..
Redjack77 said:
Yes I did select the vodafone model, and I end up with the "failed" error when flashing unlock_code.bin. I don't understand why the HTCdev method doesn't work in the first place. And the method described by stillsober requires the almost impossible wire-trick.. Well i'm afraid there is no other method..
Click to expand...
Click to collapse
has your motherboard been replaced?
what error did you have?
It's not that impossible, I did it in like 10 tries, there are YouTube videos timed exactly so you know when to connect and disconnect the wire. plus you can try as many time as it takes so you really can't go wrong... You know both method require the insulated wire right? It's just one requires the more accurate timing
Well I've somehow managed to achieve S-OFF!!!!!! This is my fastboot screen:
h t t p://i43.tinypic.com/2wgubtj.jpg
I read in a guide somewhere on the forum that when having S-OFF flashing a custom recovery would be possible, and writing supercid too, well the first thing failed (again...) but I did manage to write supercid. This is my command prompt screen:
h t t p://i39.tinypic.com/2uqzkna.jpg
So what do I have to do now??
Redjack77 said:
Well I've somehow managed to achieve S-OFF!!!!!! This is my fastboot screen:
h t t p://i43.tinypic.com/2wgubtj.jpg
I read in a guide somewhere on the forum that when having S-OFF flashing a custom recovery would be possible, and writing supercid too, well the first thing failed (again...) but I did manage to write supercid. This is my command prompt screen:
h t t p://i39.tinypic.com/2uqzkna.jpg
So what do I have to do now??
Click to expand...
Click to collapse
what does it say in the top?
juopunutbear or locked?
also i can't view the pics
can you post here in a post?
Well on the picture it says ***Locked*** and you can just paste the link in your browser without the h t t p://, because i can't include links in my posts as I have lest than 10 posts submitted.
But I actually have solved all my problems, because I knew juopeanutbear had unlocked bootloaders available on his website and in fastboot you are possible to flash these with the command "fastboot oem rebootRUU" wich put the device in RUU update mode, and then flash the unlocked HBOOT from juopeanutbear's website with the command "fastboot flash zip jb_hboot.zip.
Note (to people who might find this useful in the future): The devices sticked on showing a green loading bar in RUU update mode after entering the second command, on the command prompt it showed done, but the device didn't reboot or what. Just wait a while (to be sure) and enter command "fastboot reboot-bootloader"
Now my fastboot screen shows **Juopeanutbear** instead of ***locked*** and I've already managed to flash clockworkmod SUCCESFULLY!!!!!!!
Now I will replace CWM by 4ext and i'm good to go I guess, how I managed to get S-off will remain a secret for me, I assume I did do the wire-trick correctly after all, but didn't notice (you know,, spending a few nights behind your PC doesn't give you a clear state of mind
Redjack77 said:
Well on the picture it says ***Locked*** and you can just paste the link in your browser without the h t t p://,
Click to expand...
Click to collapse
you are right
i included also the h t t p : //
so you managed it yourself
crongats
now it is time for a custom rom
note: probably after achieving S-OFF you chose no for installing the jb hboot
Running Team Venom's Viper sense 5 rom and just like I expected I LOVE IT!!
I am merely posting this here for all those considering to go S-Off but haven't found the courage for it yet or just aren't sure what S-Off actually is. So to ease your minds a little bit I wish to explain S-Off.
For starters, S-Off and root ARE TWO COMPLETELY DIFFERENT THINGS!
HTC has been securing their phones by locking the internal flash memory (NAND or eMMC)(eMMC in our case) to stop it from being written to, unless the file being flashed is signed by a private key only known to HTC. This is controlled by a flag (@ secuflag) and is identified as the device being S-ON. Telling the HBoot the device is Security Off (S-OFF) stops this check for the key, and allows us to write anything to any partition, which is what we are aiming for.
There are actually two levels of S-OFF. The Bootloader (HBoot) and the Radio. Getting S-Off on the HBoot gives us everything we need, but doesn't actually turn off the @ secuflag which is set in the radio - instead, the HBoot ignores it and therefore thinks it is S-Off, but this is not TRUE S-Off. It is possible to flash a HBoot that believes the Radio is set to S-OFF, as the HBoot is responsible for setting that flag.
Once the HBoot on the phone is S-OFF, we can write to all the partitions and basically do whatever we want, but it is possible to go one step further. Flashing a radio that is S-OFF and actually setting the @ secuflag to S-off gives us 100% total access to every part of the phone and it's software, as it becomes network unlocked allowing you to use any SIM and also allows you to flash a ROM from any carrier (known as Super CID). It also makes it practically impossible to permanently loose root no matter what you flash. Once you have radio S-OFF, it makes it much easier to flash new HBoots and ROMs even if you flash something that is locked down tight.
Setting the Radio to S-Off is not necessary, and gaining S-OFF on the HBoot is more than most people will ever need. Radio S-Off is just the last step of the puzzle, but it is worth noting that you can permanently brick your phone if flashing a radio or a HBoot, if either of these go wrong you will end up with a shiny expensive paper weight so there is risk involved. If this helped you in any way then feel free to click on the thanks button. Meanwhile, happy hunting!
Sent from my C525c using XDA Premium 4 mobile app
To determine if you are S-OFF via HBoot or Radio you can do one of two things.
1: Go into fastboot and type
Code:
fastboot oem readsecureflag
If you get secure_flag with the number zero then congrats - you are radio S-Off
If you get secure_flag 3 then I am sorry, you are not radio S-Off. - your modded HBoot is ignoring the radio in regards to @ secureflag.
2: (I don't recommend this lol)
You can flash a stock HBoot and then reboot your bootloader. If you see S-On after already having S-Off then this means you were S-Off via HBoot. However, I would like to note that some HBoots are written out to prevent themselves from being over written so S-Off isn't lost, but this prevention does not always work and is usually patched by HTC relatively quickly.
Sent from my C525c using XDA Premium 4 mobile app
Another note... If you do not have radio S-Off then the following fastboot command will not work nor will it bring you back to S-On:
fastboot oem writesecureflag 3
Reason for this is because you are already S-On, but its being masked by your modded HBoot. So in this case, flash a stock HBoot and that will substitute for the failing command in fastboot
Sent from my C525c using XDA Premium 4 mobile app
Hey guys
Hopefully I'm not making a mess of the forum and not asking a question that's already answered, I looked inside this forum but couldn't see if there was anything that was directly related to my issue.
I gained root access to my m9, I have TWRP as my recovery and have done nandroid backup and titanium backup I have not changed the rom at all it still is the Optus rom, hopefully I don't sound stupid and this makes sense. Now I wanted to unroot the phone which I did and locked the boot loader in an attempt to put it back to original status. But then I noticed then I noticed that instead of the device showing its status "locked" it showed "re locked" so I found a way to put it back to show its status to "locked" which I had to root the phone again and make the phone s-off by typing in a script in fast boot I can't remember exactly what the method was but if you need to know how I can look it up again, (I gained s-off By using sunshine app)
The problem I have now is the phone is in s-off and I want it too be back to the original unrooted,locked status but don't want to download any roms if I don't need to. I'm confused because there was some thread "http://forum.xda-developers.com/one-m9/general/guide-return-m9-to-100-stock-s-off-t3091730" explaining how to put back phone to original and making it s-on using fastboot Orem writesecureflag code 3, but I don't think this would work for Optus carrier rom and it involves downloading a stock rom.
How can I get s-on with my current status
Cheers hopefully I didn't confuse the hell out of everyone
Will the htc one m9 optus work with this method before i try
LTERNATE revone binary (v0.2.1-wlj)
Alternate revone binary for the HTC J One (m7_wlj) only, if the main one crashes, reboots or otherwise does not work.
Download: revone-0.2.1-wlj
UPDATED revone binary (v0.2.1)
* Safety update: No longer allows -s 3 since this can lead to bricks with custom HBOOTs, use: fastboot oem writesecureflag 3 (which is safer - and checks such things)
* Fix: delusions of grandeur - revone now no longer reports success when it fails.
* Outside chance some previous failures will now be successful but most likely they will just correctly report failure.
Please note that due to the safety update ALL previous versions have been replaced with v0.2.1 and are hence no longer supported.
YOU WILL NOT RECEIVE SUPPORT FOR A VERSION LESS THAN v0.2.1
Download (and any previous link): revone-0.2.1
UPDATED revone binary (v0.2)
* Remove the random reboot feature.
* Vastly reduce the error -6 probability.
Download: revone-0.2
Use as per OP instructions renaming or name substituting as appropriate.
Reverting to S-ON (updated)
* ./revone -l
* fastboot oem writesecureflag 3
Instructions updated since stating "fastboot oem lock" was a fail - my bad! xD
Stuck with error: -1?
When initiating a reboot after "./revone -P" please press and hold the power button for 15 seconds.
To start the entire process from scratch please power off the device and wait 30 seconds, turn it on and continue to ."/revone -P".
Redistribution/Bundling revone
Permission is not given to redistribute and/or bundle revone into "one click" utilities (or similar). Please only obtain revone directly from us, this allows us to ensure the most up to date version is available in case of any critical issues.
Many thanks for your understanding.
Hi,
im currently stuck on the step of changing the CID on a smartphone of a friend. the Current CID is T-MOB101 with an unlocked bootloader ( HBOOT 2.15) S-On and an old CM running)
Id like to update to HBOOT 2.16 but im failing at step one, chaning the CID to the SCID.
Ive tried many times to flash mmcblk0p4 with the modified data (yes, ive done that) but it doesnt stick. No matter what i do i always get
fastboot oem readcid
...
(bootloader) cid: T-MOB101
Ive even verified the uploaded file, its fine.
https://i.imgur.com/nGBDEul.png
Take a look at moonshine or rumrunner.
If I remember correctly, facepalm isn't usable, anymore, with the t-mobile version of the One S if the latest official firmware got installed.
Sent from my HTC One M9 using XDA Labs
Well, both dont seem to work with the CM installed.
I guess i have to roll back to an official FW and try again
Also ive just noticed, im unable to mount /sdcard, in both recovery and rom.
Kinda strange
Facepalm and moonshine definitely don't work with CM. They're both meant to be used with a sense rom.
Rumrunner, on the other hand, should be usable with CM11.
The storage issue should be solvable by flashing a RUU.
Sent from my HTC One M9 using XDA Labs
Well, RR seems to not like my device. All i get is this
==================== 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 (7/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 (7/120)
FATAL: Download updated package at www.rumrunner.us
Press ENTER to exit
The RRU ive found for my device ( TMO_DE ) doenst like it either, propably because its severy behind the actual FW on the device (2.38.111.10 is the latest RUU ive found, but the current version on the phone is detected as 3.16.111.11)
With S-ON you can only use RUUs that have the same or a higher firmware version than your phone. Downgrading is only possible with S-OFF.
The latest RUU for T-Mobile Germany that I could find euqals version 3.16.111.7. I know that the One M9 accepts older RUUs as long as only the digits behind the last dot mismatch. I'm not sure whether the same applies to the One S, though, since I set my One S S-OFF before I used RUUs for the first time.
Alternatively, you could contact Llabtoofer's RUU service. Be aware that it's not for free.
Rumrunner (like all methods for older devices like the One S) isn't perfect. It might happen that you need to try them up to twenty times before they actually work as intended. Double check whether you followed the prerequisites & instructions on the official website. The HTC Sync Manager still being installed and the usage of an USB 3.0 port instead of an 2.0 port are only two of the possibles reasons why Rumrunner might fail.
Thanks for the RUU
and for trying an USB 2.0 port: My devices dont have them anymore :/
Anyways, im very grateful for your help