Develop Bugs

[Q] S-OFF Problems [Marvelc]

Before we start, I'll tell you what my HBOOT says:
Code:
*** UNLOCKED ***
MARVELC EVT1 SHIP S-ON RL
HBOOT-1.09.0000
MICROP-0354
RADIO-0.94.00.0824
Dec 21 2011, 12:14:03
I am trying to install the latest OTA update from HTC as a PG76IMG from the dev section so I can also have the most up-to-date HBOOT and Radio for the Marvelc. To that, I need S-OFF. However for S-OFF I need a lower version'd HBOOT. So, I tried to flash the RUU from Football's thread, however it fails (even after running theq86's Superversion utility.)
Can I do anything or I am forever stuck with only an unlocked bootloader?
What if I re-flashed HTCDev unlock RUU, then I did Superversion, then I did the stock RUU?
Any ideas/suggestions?

Problem trying to unlock bootloader

My Wildfire S is:
*** LOCKED ***
MARVEL PVT SHIP S-ON RL
HBOOT-1.09.0099
MICROP-0451
RADIO-7.57.39.10M
Feb 8 2012, 18:29:31
I've followed the instructions at http://www.htcdev.com/bootloader/ruu-downloads which, for my network (O2UK), instructs me to "update" my ROM to 2.13.206.1. So I've updated OTA and find I have 2.26.401.3.
The problem is that the RUU from the above website won't recognise this 2.26.401.3 ROM as 2.13.206.1 and insists I "update" to 2.13.206.1 which I do not know how to do.
Is there any other way I can unlock the bootloader? Or can I get the 2.13.206.1 ROM from somewhere else and install that?

Just proceed to step 1..............If your version is higher than specified,you can unlock your phone's bootloader

You cannot install other ROM into your phone without bootloader unlocked.root permissions and CWM recovery.
If i helped you,click the "Thanks" button.Sorry for my English and have a nice night !

P1ngP1ng said:
My Wildfire S is:
*** LOCKED ***
MARVEL PVT SHIP S-ON RL
HBOOT-1.09.0099
MICROP-0451
RADIO-7.57.39.10M
Feb 8 2012, 18:29:31
Click to expand...
Click to collapse
I think you're already have HBOOT unlockable (xxxx99)
Go to steps unlock bootloader without download ruu from htcdev.
Sent from MARVEL

You really don't need to update the boot loader and search for RUU when the HBoot ver is 1.08.xxx or later.
Just go thru this guide, will help you
http://androidforums.com/wildfire-s-all-things-root/480954-guide-how-root-wildfire-s-s-finally.html
Hope this may be useful.

Senthamil said:
You really don't need to update the boot loader and search for RUU when the HBoot ver is 1.08.xxx or later.
Just go thru this guide, will help you
*Androidforums-link*
Hope this may be useful.
Click to expand...
Click to collapse
Hi
I have the exact same Phone values and I got threw the prozess(the one behind the link above) and i got my wfs to ***UNLOCKED*** and i'm able to install new ROM's
buuuuuuuut
every Rom i installed is not capable to make or receive phone calls. Every time i try to do a call, the wfs says:
android.phone.prozess is shutting down
Did i forget anything or did anything wrong?
Got any help?

@clusternate, if your phone is MarvelC (cdma) then you have to flash ROM that suits your model.

Senthamil said:
@clusternate, if your phone is MarvelC (cdma) then you have to flash ROM that suits your model.
Click to expand...
Click to collapse
I've got the europe (germany) version. so i think i need the GSM version.
I'm quiet new to rooting this devices. Are there different versions of every ROM?
I tried about 6-7 ROM's and not one of them worked. (MIUI, CM7, CM9, everyone from the wfs section of this forum)
A co-worker told me something about updating the modem of my wfs.
Is this true and is there a way to do it?
PS. Which ROM should work on my device?
PPS. There is another prozess that is failing.
Prozess.android.acore is also crashing.

Wildfire S RUU Issue

The Wildfire S will default boot to the HBOOT menu even when just pressing the power button alone. The volume buttons are functioning. The phone has no rom at all from what I can tell. I have tried to re-flash the original Virgin Mobile RUU but it will not work. (RUU_Marvel_Virgin_Mobile_1.37.35.1.1_Radio_47.10.35.3029H_7.46.35.08_release_188032_signed)
I am getting Error 132: Signature error. I have tried multiple RUU's and all the other ones have given me Error 130: Model ID Error. Am I using the wrong RUU? I cannot for the life of me find any other VM RUU's anywhere. Prior to attempting to re-flash the original RUU, I re-locked bootloader. Here are the current specs.
*** RELOCKED ***
MARVELC EVT1 SHIP S-ON RL
HBOOT-1.10.000
RADIO-0.94.00.0109
DEC 30 2011, 16:47:36
I need to re-flash original RUU to this phone with S-ON. Unless someone knows of a way to get S-OFF with the phone having no rom. The current image version according to the RUU installation wizard is newer then the one I am trying to flash. There are no recovery images. Thank you.

Fix
Try to make a goldcard

tried to use ruu to update, phone stuck in bootloader

So my phone is currently on a custom rom and I was trying to take it back to stock. I downloaded a ruu from htc dev because a bunch of guides I saw pointed me to do that and click a few buttons during the process it said my phone can't be updated and now i am stuck on a screen that looks like the bootloader but says this
***tampered***
***unlocked***
m8_UL PVT SHIP S-ON
HBOOT- 3.18.0.0000
Radio - 1.19.213311491.03g
OPENDSP - V382.2-00542-m8974.0311
OS-
EMMC-Boot 2048MB
Jul 16 @014, 03:33:24.0
SECURITY Fail!
RUU
I cant do anything from this screen. I tried to use another tool to get me into recovery but it says device not found. I also tried going through revovery through the ruu but nothing happens there. What else can i try to save my phone?

jayrocc said:
So my phone is currently on a custom rom and I was trying to take it back to stock. I downloaded a ruu from htc dev because a bunch of guides I saw pointed me to do that and click a few buttons during the process it said my phone can't be updated and now i am stuck on a screen that looks like the bootloader but says this
***tampered***
***unlocked***
m8_UL PVT SHIP S-ON
HBOOT- 3.18.0.0000
Radio - 1.19.213311491.03g
OPENDSP - V382.2-00542-m8974.0311
OS-
EMMC-Boot 2048MB
Jul 16 @014, 03:33:24.0
SECURITY Fail!
RUU
I cant do anything from this screen. I tried to use another tool to get me into recovery but it says device not found. I also tried going through revovery through the ruu but nothing happens there. What else can i try to save my phone?
Click to expand...
Click to collapse
nvm i fixed that problem and now I'm back to square one. maybe someone could point me in the right direction from here.
I'm currently on 4.4.3 kk and am trying to get back to stock from my custom rom. clearly the ruu I used was the incorrect method and the other method I was going to try which involves using hasoon's toolkit appears to not be the answer because when i went to check the cid the version number was not available ( unless im missing something here)
any assistance that someone is willing to offer would be appreciated.

You have to re-lock your bootloader before you run the RUU.

VolcanicSkunk said:
You have to re-lock your bootloader before you run the RUU.
Click to expand...
Click to collapse
thanks, the guide i was looking at failed to mention that.

jayrocc said:
thanks, the guide i was looking at failed to mention that.
Click to expand...
Click to collapse
How did you get back to where you were previously? Did you re-flash your custom ROM?

(HELP) Upgrade android from 4.4.4 to newest and possible for my device

Thanks for coming to this thread,i need help to upgrade my device to newest and possible android
i not get any OTA upgrade ( i recently buy this phone from online seller at my country Indonesia ) this phone work perfectly with 4G lte and another function ,but i want newest android for my device
this is my device information :
android version=4.4.4
sense version=-6.0
software version=3.31.512.2
htc sdk api level 6.25
pri version-2.87_002
prl version-00000
kernal version 3.4.0-g3e2305b [email protected] #1 SMP PREEMPT
Baseband version-1.09.20.0926
build number-3.31.512.2 CL395691 release-keys
BOOTLOADER ;
***UNLOCKED***
M8_WLV PVT SHIP S-OFF
CID-11111111
HBOOT-3.19.0.0000
RADIO-1.09.20.0926
OpenDSP-v46.2.-00564-M8974_FO.0811
OS-3.28.605.4
eMMC-boot 2048MB
Sep 30 2014,01:16:07.90023198

Check that any custom recovery is installed?

kiregnwn said:
....but i want newest android for my device
this is my device information :
android version=4.4.4
sense version=-6.0
software version=3.31.512.2
htc sdk api level 6.25
pri version-2.87_002
prl version-00000
kernal version 3.4.0-g3e2305b [email protected] #1 SMP PREEMPT
Baseband version-1.09.20.0926
build number-3.31.512.2 CL395691 release-keys
BOOTLOADER ;
***UNLOCKED***
M8_WLV PVT SHIP S-OFF
CID-11111111
HBOOT-3.19.0.0000
RADIO-1.09.20.0926
OpenDSP-v46.2.-00564-M8974_FO.0811
OS-3.28.605.4
eMMC-boot 2048MB
Sep 30 2014,01:16:07.90023198
Click to expand...
Click to collapse
Lollipop is the latest Android version for your device variant which is a LRA.
You can get the 4.21.512.4 RUU here : https://forum.xda-developers.com/showpost.php?p=66044439&postcount=37
then OTA to 4.21.512.5 but most probably you need to change the CID from SuperCID 11111111 back to stock LRA__001 for OTA to install successfully as explained here : https://forum.xda-developers.com/showpost.php?p=67516629&postcount=26
Then you can install any Marshmallow GSM ROM with Verizon support.
Note : Never ever install any Verizon stock firmware or any GSM firmware to your device, it'll brick the radio and you'll lose network & data.

Think about it before you do it...
ckpv5 said:
Lollipop is the latest Android version for your device variant which is a LRA.
You can get the 4.21.512.4 RUU here : https://forum.xda-developers.com/showpost.php?p=66044439&postcount=37
then OTA to 4.21.512.5 but most probably you need to change the CID from SuperCID 11111111 back to stock LRA__001 for OTA to install successfully as explained here : https://forum.xda-developers.com/showpost.php?p=67516629&postcount=26
Then you can install any Marshmallow GSM ROM with Verizon support.
Note : Never ever install any Verizon stock firmware or any GSM firmware to your device, it'll brick the radio and you'll lose network & data.
Click to expand...
Click to collapse
It's awesome you actually got great advice and refrences to how to do what you need to do. I'd like to add this though: Consider whether getting Lollipop is worth re-locking and doing the things you need to do, including putting your device from s-off to s-on is worth it. And yes, you can run a RUU executable and extract the rom.zip from your computer's temporary files, but unless you have some mad coding and manual programming experience, with the version of HBOOT you have listed if you want to be s-off again you may be out of luck. or find yourself in a bootloop or your computer unable to find your device, or even unable to access stock recovery even with the correct button sequences. At best, you may find yourself unable to access mms apn settings (not even sure if you need or care about that), and if you can access them (apn and mms settings), unable to get the settings to stick (or actually apply themselves so your phone even uses them at all), or only have internet access but no mms even with the exact settings for mms you need put into a third-party texting app such as textra. etc.
if you are already or end up s-on and updated to the "latest and greatest" for your M8, maybe everything will work out perfectly for you . But, just something to thing about before doing all of those things. If you are lucky enough to get a bonafide XDA member's attention and help, as you have already, you are still by default expected to think of these things and do your own research. What you probably won't find out along the way is that when you run into some strange problem, there's no one knowledgeable to help you decipher it. There's tons of unanswered posts on this forum alone that have been viewed many times, that go unanswered.

kissyhot said:
I'd like to add this though: Consider whether getting Lollipop is worth re-locking and doing the things you need to do, including putting your device from s-off to s-on is worth it.
Click to expand...
Click to collapse
That's a wrong advise and wrong understanding.
Once a device is S-Off, there is NO NEED to relocking bootloader and there is NO NEED to change S-Off to S-On.
Only S-On device needs relocking bootloader to install signed firmware and signed RUU. S-On device can't install unsigned firmware or RUU.
S-Off device can install any unsigned or signed firmware and RUU (no relocking is needed and not advisable)

ckpv5 said:
That's a wrong advise and wrong understanding.
Once a device is S-Off, there is NO NEED to relocking bootloader and there is NO NEED to change S-Off to S-On.
Only S-On device needs relocking bootloader to install signed firmware and signed RUU. S-On device can't install unsigned firmware or RUU.
S-Off device can install any unsigned or signed firmware and RUU (no relocking is needed and not advisable)
Click to expand...
Click to collapse
thanks,so my device will still ***UNLOCKED*** after i install RUU right?
btw we dont have verizon provider on my country ,thats mean i cant do OTA update ?
so i guess RUU if my only option to update my device,?it is possible for my device to use marsmallow or nougat?

kiregnwn said:
thanks,so my device will still ***UNLOCKED*** after i install RUU right?
btw we dont have verizon provider on my country ,thats mean i cant do OTA update ?
so i guess RUU if my only option to update my device,?it is possible for my device to use marsmallow or nougat?
Click to expand...
Click to collapse
Leave it UNLOCKED so it will still be UNLOCKED after RUU is installed.
Whatever you do now or later ... no need to relock it, leave it UNLOCKED.
You can do OTA as this is not a Verizon device but LRA. Now you can't OTA because you have a Verizon ROM running. RUU 4.21.512.4 is stock LRA, you'll get OTA notification once you install it.
The only thing is you need to change SuperCID 11111111 to LRA__001 to proceed OTA (as experience by other user in the above link I gave you).
Frankly speaking I don't see any good reason to have SuperCID on this variant.
Once you updated to Lollipop you can use Marshmallow ROM which support Verizon (there are a few of them). Nougat .. not so sure but you can always try later after you updated to lollipop but definitely won't work on your current firmware which is a KitKat.