Database Develop

Rumrunner not working on 1.55 / 3.62.206.1 after OTA - O2-UK

I received an O2 HTC One that had had some messing.
Device was S-ON, Tampered, Relocked with FW 3.62.401.1, custom ROM and HBOOT 1.55.
I unlocked the bootloader using HTVDev and ran rumrunner over it to get it S-OFF.
Plan was to return it to stock. I followed a guide on here to return it which entailed:
S-OFF
Downgrade to HBOOT 1.44
Change CID to HTC__032
Run RUU for FW 1.28.401.1
Change CID to O2___001
Restore Nandroid 1.28.206.1
Lock bootloader
Remove tampered
OTA updates to 3.62.206.1
S-ON
Because I am a fool I forgot to Lock the bootloader and remove tampered before I went S-ON. I am now on 3.62.206.1 and rumrunner does not seem to work. I get to the same point every time...
Code:
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
Test 2: Booting device
Waiting for ADB (35/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
and then I get the FATAL error.
Things I have tried so far, all get to the same point:
1. Windows 7 w/ HTC Drivers provided with phone
2. Windows 7 w/ HTC Drivers downloaded
3. Windows 7 w/ CWM Drivers
4. Windows 8.0 w/ HTC Drivers provided from phone
5. Windows 8.0 w/ HTC Drivers downloaded
6. Windows 8.0 w/ CWM Drivers
7. Windows 8.1 w/ HTC Drivers provided with phone
8. Ubuntu 13.10
I am absolutely stumped. I can only assume that after the OTA update to 1.55 my phone is no longer vulnerable to whatever exploit Rumrunner uses.
Unless anyone else knows any reason for it to fail at this point?
Oh, and each OS was a clean install. I have spent a lot of time today on this!

Comedy- said:
Plan was to return it to stock. I followed a guide on here to return it which entailed:
S-OFF
Downgrade to HBOOT 1.44
Change CID to HTC__032
Run RUU for FW 1.28.401.1
Change CID to O2___001
Restore Nandroid 1.28.206.1
Lock bootloader
Remove tampered
OTA updates to 3.62.206.1
S-ON
Click to expand...
Click to collapse
That sound's awfully familiar, do I have anything to do with that?
If yes, then I said to S-On after 1st OTA ... not after OTA to 3.62
is you bootloader unlocked, or can you unlock bootloader using HTCdev?

nkk71 said:
That sound's awfully familiar, do I have anything to do with that?
If yes, then I said to S-On after 1st OTA ... not after OTA to 3.62
is you bootloader unlocked, or can you unlock bootloader using HTCdev?
Click to expand...
Click to collapse
The boot loader is unlocked. I can flash custom recovery and roms and also have the current rom rooted. It just appears that my HBOOT doesn't want to play ball.
It did indeed say to S-On after 1st OTA but also had a note that it may not be necessary. I read through and figured I would skip it as I was
, ironically, worried if I would successfully be able to S-OFF the next time around. I guess it was a kind of trial run and I was trying to play it safe.

Comedy- said:
The boot loader is unlocked. I can flash custom recovery and roms and also have the current rom rooted. It just appears that my HBOOT doesn't want to play ball.
It did indeed say to S-On after 1st OTA but also had a note that it may not be necessary. I read through and figured I would skip it as I was
, ironically, worried if I would successfully be able to S-OFF the next time around. I guess it was a kind of trial run and I was trying to play it safe.
Click to expand...
Click to collapse
Have you tried http://firewater-soff.com/

I didn't even know about that one. Thanks very much. It did the job!

Comedy- said:
I didn't even know about that one. Thanks very much. It did the job!
Click to expand...
Click to collapse
:laugh::laugh::victory::victory::victory:

[q] hboot 1.55 os: 3.63.69.3 s-off help!

Is already way to make S-OFF in my HTC One with 3.63.69.3 (Android 4.3)??? My device has got CID: ORANGB10, branded Orange POLAND. I've got unlocked & rooted phone with flag TAMPERED UNLOCKED. Firewater doesn't work. Please programmers help me, I need my guarantee back!
I tried revone, rumrunner and firewater but both of this doesn't work

ziareks93 said:
Is already way to make S-OFF in my HTC One with 3.63.69.3 (Android 4.3)??? My device has got CID: ORANGB10, branded Orange POLAND. I've got unlocked & rooted phone with flag TAMPERED UNLOCKED. Firewater doesn't work. Please programmers help me, I need my guarantee back!
I tried revone, rumrunner and firewater but both of this doesn't work
Click to expand...
Click to collapse
Hi, try to flash 3.62 firmware with Hboot 1.54. Then, rumrunner should work. Then you should change your CID to SuperCID 11111111.
Lucas (from Lodz)
PS
From whis City of Poland Are You ?

help
petrusconsult said:
Hi, try to flash 3.62 firmware with Hboot 1.54. Then, rumrunner should work. Then you should change your CID to SuperCID 11111111.
Lucas (from Lodz)
PS
From whis City of Poland Are You ?
Click to expand...
Click to collapse
DEBICA (podkarpackie)

ziareks93 said:
DEBICA (podkarpackie)
Click to expand...
Click to collapse
Hi again.
I've been looking a little and in my opinion, the rumrunner should work on h1.55. But, it depends on the system that you have on your PC.
If you are running on Windows 8/8.1 - there's a problem with usb drivers delivered by Microsoft.
On Windows 7, there are Intel drivers.
So, assuming that you are running on Win7, to verify if there is correct conection between PC and your HTC One, download adb an fastboot, for ex HTCOneRoot pack from here : https://mega.co.nz/#!dcZTDDzQ!SCd73VExhwCviFTWljDrtiW4EvFp161DsFpo443-aLs
I use it without any problem. The unpack, and run CMD as Administrator. Go to the folder with HTCOneRoot, connect your phone (in normal mode) wait until system installs drivers and type : "adb devices". After a few seconds, you shold see a list of connected devives. Something like 3HXXXXXXX. If you don't see it after about 10 sec., it means, that you have problem withe device drivers in your system. Try then to install the included drivers.
If everytnig is OK, I mean if your device is listed after adb command, try to run rumrunner, but you shold run it from normal workig mode of your One. Not fastboot or bootloader.
One I had a HTC One with Orance CID and a simlock, I've spent 2 day but finally I've won !
Let me know, how it's working. (by evening)

help with going back to stock euro

My device is Super CID. I have a CWN nandroid thats got loads of CIDs so was going to just use CID HTC__102 once I have flashed the OS. Then removed tampered, Lock bootloader then S-on.. Will this work or does it have to go back to the vodaphone CID? regards

anarchyuk said:
My device is Super CID. I have a CWN nandroid thats got loads of CIDs so was going to just use CID HTC__102 once I have flashed the OS. Then removed tampered, Lock bootloader then S-on.. Will this work or does it have to go back to the vodaphone CID? regards
Click to expand...
Click to collapse
Your CID will remain SuperCID only. If you want to go back to the Vodafone CID, you will have to use the 'writecid' command. If you're giving the phone for repair, then you'll have to change to the HTC_102. If not, stay on SuperCID. The RUU will work perfectly on SuperCID
Next, i would never recommend you to go back S-ON. Stay S-OFF. However, if you insist on going S-ON, S-ON ONLY AFTER YOU'RE SUCCESSFULLY ON STOCK FIRMWARE AND HBOOT VERSION IS 1.44/1.54.
Do not S-ON before the RUU is flashed. Do not S-ON if HBOOT is 1.55/1.56. Otherwise, the TAMPERED flag will re-appear

raghav kapur said:
Your CID will remain SuperCID only. If you want to go back to the Vodafone CID, you will have to use the 'writecid' command. If you're giving the phone for repair, then you'll have to change to the HTC_102. If not, stay on SuperCID. The RUU will work perfectly on SuperCID
Next, i would never recommend you to go back S-ON. Stay S-OFF. However, if you insist on going S-ON, S-ON ONLY AFTER YOU'RE SUCCESSFULLY ON STOCK FIRMWARE AND HBOOT VERSION IS 1.44/1.54.
Do not S-ON before the RUU is flashed. Do not S-ON if HBOOT is 1.55/1.56. Otherwise, the TAMPERED flag will re-appear
Click to expand...
Click to collapse
thanks for the reply. Its hboot 1.44.. I am selling it and its supposed to be getting sold as stock... I have just pushed a nandroid for the euro over but had a md5 check error. think this may be because i opened one of the rars to make sure it was for my model id so im re pushing it.. My main concern is.. Can i flash say a ruu exe. leave super cid. lock bootloader and then s-on without a brick?

anarchyuk said:
thanks for the reply. Its hboot 1.44.. I am selling it and its supposed to be getting sold as stock... I have just pushed a nandroid for the euro over but had a md5 check error. think this may be because i opened one of the rars to make sure it was for my model id so im re pushing it.. My main concern is.. Can i flash say a ruu exe. leave super cid. lock bootloader and then s-on without a brick?
Click to expand...
Click to collapse
Look, if you're gonna sell the phone as stock, don't sell it as SuperCID. Sell it with the HTC__102 CID
If for some reason, you still want to sell it as SuperCID, then ignore the first step. Follow these steps in order
1. Change your CID to the stock Vodafone CID (HTC__102)
2. Flash this in TWRP 2.6.3.3 (ive had personal experience, none with CWM):
http://www.htc1guru.com/dld/guru_bootloader_reset_1-0-zip/
Choose "Lock Bootloader" and "remove TAMPERED"
3. Once you choose these 2 options and flash the zip, go back to the bootloader and check that the bootloader is now LOCKED and no TAMPERED
4. Now, flash this RUU.exe:
http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
5. Once the phone boots up successfully, the last thing left is to S-ON. Remember, S-ON the phone before you install any OTA's. Technically, as soon as the phone boots. To S-ON:
Get the phone to fastboot mode, open command prompt on ur PC in the fastboot folder and type:
fastboot oem writesecureflag 3
Then, reboot the phone thrice. It will be S-ON again

raghav kapur said:
Look, if you're gonna sell the phone as stock, don't sell it as SuperCID. Sell it with the HTC__102 CID
If for some reason, you still want to sell it as SuperCID, then ignore the first step. Follow these steps in order
1. Change your CID to the stock Vodafone CID (HTC__102)
2. Flash this in TWRP 2.6.3.3 (ive had personal experience, none with CWM):
http://www.htc1guru.com/dld/guru_bootloader_reset_1-0-zip/
Choose "Lock Bootloader" and "remove TAMPERED"
3. Once you choose these 2 options and flash the zip, go back to the bootloader and check that the bootloader is now LOCKED and no TAMPERED
4. Now, flash this RUU.exe:
http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
5. Once the phone boots up successfully, the last thing left is to S-ON. Remember, S-ON the phone before you install any OTA's. Technically, as soon as the phone boots. To S-ON:
Get the phone to fastboot mode, open command prompt on ur PC in the fastboot folder and type:
fastboot oem writesecureflag 3
Then, reboot the phone thrice. It will be S-ON again
Click to expand...
Click to collapse
I think I have already done most of it, i got the md5 check error to go away, and installed a standard HTC that had the CID HTC_002 available in the build prop. I then flashed stock recovery. Fastboot booted in to CWM and ran the remove tampered. Lock bootloader.. I have just changed the CID From 111111 to HTC__002 and its booted fine. So The bootloader shows locked, no tampered or HTC red developer message under the logo but still hs S-OFF on bootloader screen? what would happen If i s-on now?
edit: Not to worry I done the secuirty flag 3 command and its now s-on and still boots, ty to you both.. really appreciate it
edit: 2 the tampered has came back
edit: 3 back to s-off and bootloader unlocked, tamp flag back too

[Q] HTC One stuck in bootloader with relocked bootloader, s-on and custom recovery

​my htc one is stuck in the bootloader with the tampered banner on it, RELOCKED bootloader and also s-on. I have a viper one ROM on it an a twrp custom recovery.. now funny story I guarantee you will laugh. I knew the htc oem update was coming soon so I could get lollipop but I was rooted and couldn't do it. So I was trying to get s-off on my device but I missed a step on some gadget hacks tutorial and locked the bootloader (thats the funny part) then I tried unlocking it again but it didn't work. I tried going into recovery but it just rebooted back to the bootloader. I tried everything in the bootloader options and nothing worked.
​my Hboot is version 1.57 and my OS is 6. 10.531.9
​I tried flashing a recovery again and I cant do it it says "error cannot load--" and the same with the Unlock_code.bin it just wasn't working? what am I doing wrong and how can i fix it. please its urgent
​if you have any answers you can comment here and also e-mail me at [email protected] (I would usually say text me :crying: ) once again please help I don't know what to do next.

kage_outram said:
​my htc one is stuck in the bootloader with the tampered banner on it, RELOCKED bootloader and also s-on. I have a viper one ROM on it an a twrp custom recovery.. now funny story I guarantee you will laugh.
I knew the htc oem update was coming soon so I could get lollipop but I was rooted and couldn't do it. So I was trying to get s-off on my device but I missed a step on some gadget hacks tutorial and locked the bootloader (thats the funny part) then I tried unlocking it again but it didn't work. I tried going into recovery but it just rebooted back to the bootloader. I tried everything in the bootloader options and nothing worked.
​my Hboot is version 1.57 and my OS is 6. 10.531.9
​I tried flashing a recovery again and I cant do it it says "error cannot load--" and the same with the Unlock_code.bin it just wasn't working? what am I doing wrong and how can i fix it. please its urgent
​if you have any answers you can comment here and also e-mail me at [email protected] (I would usually say text me :crying: ) once again please help I don't know what to do next.
Click to expand...
Click to collapse
Since, you are S-ON with a locked bootloader run this RUU 6.10.531.10. It will put you back at stock, then you can try to unlock you bootloader. To get S-OFF you will need to use Sunshine with your hboot 1.57.

majmoz said:
Since, you are S-ON with a locked bootloader run this RUU 6.10.531.10. It will put you back at stock, then you can try to unlock you bootloader. To get S-OFF you will need to use Sunshine with your hboot 1.57.
Click to expand...
Click to collapse
What commands do I put in to add the RUU

kage_outram said:
What commands do I put in to add the RUU
Click to expand...
Click to collapse
Download the RUU to your Windows computer
Connect the phone to the computer via USB
Boot into Bootloader/FASTBOOT USB on your phone
Double-click the RUU on your computer

majmoz said:
Download the RUU to your Windows computer
Connect the phone to the computer via USB
Boot into Bootloader/FASTBOOT USB on your phone
Double-click the RUU on your computer
Click to expand...
Click to collapse
what should happen next

[Q] Hard bricked VZM HTC M7

Hey guys, so I tried to unlock my phone to switch over to T-mobile and in the process, I believe I bricked my phone. I followed some very misleading guide, and due to this, my phone is stuck on the RUU screen with the four triangles. To make things worse, my computer (running win 8.1) stopped being able to recognize my phone, so adb and fastboot won't recognize it either (I feel like this happened due to me trying to flash a RUU). I tried several times to re-install drivers to no avail. I don't think I can get to the recovery screen either. Is there any hope in saving this or is it a goner? Thanks.
What I've done so far before this state:
S-OFF
Rooted
changed the CID and MID to T-mobile relevant IDs

kiweewee said:
Hey guys, so I tried to unlock my phone to switch over to T-mobile and in the process, I believe I bricked my phone. I followed some very misleading guide, and due to this, my phone is stuck on the RUU screen with the four triangles. To make things worse, my computer (running win 8.1) stopped being able to recognize my phone, so adb and fastboot won't recognize it either (I feel like this happened due to me trying to flash a RUU). I tried several times to re-install drivers to no avail. I don't think I can get to the recovery screen either. Is there any hope in saving this or is it a goner? Thanks.
What I've done so far before this state:
S-OFF
Rooted
changed the CID and MID to T-mobile relevant IDs
Click to expand...
Click to collapse
if you have used a 1.xx.xxx.x RUU with windows 8.1, thats the problem. When flashing a 1.xx.xxx.x ruu, your bootloader will downgrade to version 1.44. This bootloader version isn't compatible with windows 8.1 (fastboot won't work).
The ruu screen with 4 triangles = incomplete ruu flash. Most likely caused by the computer not being able to flash the entire RUU after hboot 1.44 was flashed.
If using a ruu.exe, you'll need to find a winXP or 7 pc. If using a ruu.zip, you can either use winXP, win7, Linux (recommand ubuntu 12.04 32 bits version) or MacOS.
Btw why did you flashed a ruu to unlock your phone? You know that sim-unlock can be done simply by using a paid code? Or if you have s-off you can sim-unlock for free using the sieempi method.
can you post all the information you can see on the bootloader screen here?

Uh I don't think I can get to the bootloader screen as it is stuck on the RUU screen. Would connecting my phone on linux get some response?

kiweewee said:
Uh I don't think I can get to the bootloader screen as it is stuck on the RUU screen. Would connecting my phone on linux get some response?
Click to expand...
Click to collapse
hold volume down and power until the phone reboot in bootloader mode. can you confirm the ruu version used?

I've done that and the screen just turns off and on with the RUU screen with the four triangles still there.
I've also tried connecting my phone on linux, after installing adb and fastboot, but it has given me a "HTC unknown usb device( device failed enumeration) " warning.

I used this ruu after hearing my phone should be using this ruu, I changed the cid to 11111111 and mid to tmobile on the android.info file so it would work
RUU Zip M7_WL_JB_50_VZW_1.10.605.10_decrypted
After flashing this once it gave me the hboot error thing to boot again, but that is when my phone stopped responding to fastboot.

kiweewee said:
I used this ruu after hearing my phone should be using this ruu, I changed the cid to 11111111 and mid to tmobile on the android.info file so it would work
RUU Zip M7_WL_JB_50_VZW_1.10.605.10_decrypted
After flashing this once it gave me the hboot error thing to boot again, but that is when my phone stopped responding to fastboot.
Click to expand...
Click to collapse
I'm pretty sure your totally wasting your time you can't turn a CDMA Verizon phone into a GSM t-mobile phone by flashing a RUU
your going to end up with a bunch of screwed up partitions
this is how you get fastboot working on windows 8.1 hboot 1.44
http://forum.xda-developers.com/htc-one-s/general/guide-fix-fastboot-windows-8-1-t2858337