[DEV][Solved]Need advanced help with HBOOT... Unique S-Off situation - Sprint HTC One (M7)

Hey guys... Ok I am in a very unique situation. I was recently testing to get 4.2.2 ROMs to work on sprint with a kernel...
Well, it ended up not working, and a few things ended up getting jittery. So i relocked bootloader, did a fastboot oem rebootRUU, and went ahead and ruu'd the phone. Here is where it gets weird...
After the RUU finished succesfully, I went into bootloader, and it showed "RELOCKED S-OFF", and figured that cant be good, so i proceeded to do a fastboot oem writesecureflag 3, and re-relocked via RevONE. Bootloader now showed "LOCKED S-ON", so RUU'd again. Now, my CID is still unlocked which has nothing to do with hboot i know. Either way, I did the fastboot flash unlocktoken......, and got HTCDEV unlocked. I then proceed to unlock via RevONE with all successful. I even flashed the boot_unsecure.img (kernel) on the stock RUU rom.
Bootloader shows "UNLOCKED S-OFF"... But I am not S-Off, simply my flag shows it. I cannot flash a different hboot, nor can i flash a radio (and yes i tried flashing within rebootRUU). It gives me the stupid "remote - not allowed".
Would there be a way to DD the mmcblk? Does anyone on an ENG S-Off bootloader have the mmcblk partition number? Mine does not show the hboot label... cat /proc/emmc.
Anyone ideas? Moonshine does not work either.
Update... MMCBLK0P12 hboot
Solved
Lol that was easy... Just had to do a low level overwrite (DD) to an ENG hboot, so that i could then truely S-Off, and flash other hboots and radios... sheesh...

Tilde88 said:
Hey guys... Ok I am in a very unique situation. I was recently testing to get 4.2.2 ROMs to work on sprint with a kernel...
Well, it ended up not working, and a few things ended up getting jittery. So i relocked bootloader, did a fastboot oem rebootRUU, and went ahead and ruu'd the phone. Here is where it gets weird...
After the RUU finished succesfully, I went into bootloader, and it showed "RELOCKED S-OFF", and figured that cant be good, so i proceeded to do a fastboot oem writesecureflag 3, and re-relocked via RevONE. Bootloader now showed "LOCKED S-ON", so RUU'd again. Now, my CID is still unlocked which has nothing to do with hboot i know. Either way, I did the fastboot flash unlocktoken......, and got HTCDEV unlocked. I then proceed to unlock via RevONE with all successful. I even flashed the boot_unsecure.img (kernel) on the stock RUU rom.
Bootloader shows "UNLOCKED S-OFF"... But I am not S-Off, simply my flag shows it. I cannot flash a different hboot, nor can i flash a radio (and yes i tried flashing within rebootRUU). It gives me the stupid "remote - not allowed".
Would there be a way to DD the mmcblk? Does anyone on an ENG S-Off bootloader have the mmcblk partition number? Mine does not show the hboot label... cat /proc/emmc.
Anyone ideas? Moonshine does not work either.
Update... MMCBLK0P12 hboot
Solved
Lol that was easy... Just had to do a low level overwrite (DD) to an ENG hboot, so that i could then truely S-Off, and flash other hboots and radios... sheesh...
Click to expand...
Click to collapse
I thought once soff always soff I have ruu 2 times already after soff revone and was still able to flash the radio from the newest firmware. After every ruu it always said soff
Sent from my GT-P3113 using xda app-developers app

Just out of curisosity, could anyone explain why that happened? What made the security flag change?
Also, why did you say "this cannot be good" when you saw "RELOCKED S-OFF"? Were you S-OFF to begin with? You can lock the bootloader and still remain S-Off, correct?

karn101 said:
Just out of curisosity, could anyone explain why that happened? What made the security flag change?
Also, why did you say "this cannot be good" when you saw "RELOCKED S-OFF"? Were you S-OFF to begin with? You can lock the bootloader and still remain S-Off, correct?
Click to expand...
Click to collapse
Yes, but I figured that while it was relocked, it would overwrite the hboot to stock if I RUU'd, thus making the flag S-On. however, this needed to be manually done with fastboot apparently.
Tbh, I think this all started from a ROM flash, it was an international ROM, and I hadn't bothered to check to know the partition layouts were different. Kernel ended up flashing to recovery, and system almost went to radio, lol idk how it didn't brick.... but yea.

Tilde88 said:
Yes, but I figured that while it was relocked, it would overwrite the hboot to stock if I RUU'd, thus making the flag S-On. however, this needed to be manually done with fastboot apparently.
Tbh, I think this all started from a ROM flash, it was an international ROM, and I hadn't bothered to check to know the partition layouts were different. Kernel ended up flashing to recovery, and system almost went to radio, lol idk how it didn't brick.... but yea.
Click to expand...
Click to collapse
Oh, so you were more concerned that it said relocked than S-OFF. S-OFF was bolded so I thought you were saying "Uh oh" to the S-Off.

Related

I think I messed up my One...

So I was fine yesterday, went through all the steps to get a full GE One. Was very curious
I like sense better though personally, so I wanted to go back. I have changed my MID back to it's original values and the CID to HTC__001.
In RUU mode after entering fastboot, it will no longer allow me to flash anything, with a 'unknown 99 error.' I also wanted to get S-on again, so I went through the steps and all was well. Or so I thought. Kept getting error -6 and error -1. I also relocked the bootloader. But now I can't boot into Android, and there are three tags over the Bootloader now. **TAMPERED** **RELOCKED** and **Security Warning**. If I try to boot to the OS or recovery it brings me straight back to HBOOT. Anything I can do to resolve this mess? Thanks in advance.
EDIT: I forgot to mention that I flashed back to an original HBOOT before attempting any of this. 1.54.
I think this has happened because you've relocked your bootloader, whilst having a custom recovery installed.
Just use htcdev.com to unlock your boatloader

[Q] Re-locked, s-on, Security Warning, and cannot boot into Recovery. My options?

Hi guys.
First time posting, but have used the site extensively over the past 6-8 months. I have an AT&T HTC One. I had unlocked it, s-off, rooted, installed GPe, and decided to go back. The ROM I went back to was supposed to be MY stock ROM, but it turns out it was unbranded 4.2.2. I thought nothing of it, and as of yesterday, had sold my phone on ebay. I decided to wipe my phone to get ready to ship. I locked my bootloader and went to s-on, but when I went to factory reset, I got a "security warning" and it won't reboot into recovery. I've tried everything- tried to re-unlock it with htcdev, which freezes at the bootloader. I've tried to unlock via revone, since I still have root (root checker verified this to be the case), but get the -6 error when using terminal emulator in ROM Toolbox, and get the same error when doing it via adb commands. I've tried probably 50 different things about 10 different times, and am about to pull my hair out! I've read and searched probably hundreds of threads over the past 24 hours. Trying to flash stock RUU (the exe) just freezes as well. Any help would be appreciated! Let me know what info you need from me.
Android 4.2.2
Hboot 1.44
Software number 2.24.401.8
HTC SDK API level 5.34
Kernel version 3.4.10-g28df0d6 [email protected] #1 SMP PREEMPT
Baseband version 4A.18.3263.15_10.38h.1157.04L
Build number 2.24.401.8 CL235216 release-keys
Thanks guys! Awesome community!
I think you need to read Vomers guide and install using the ADB Method
http://forum.xda-developers.com/showthread.php?t=2365506&page=4
but also Read Mike 1986's Return to stock Guide before - this will ensure you are aware of what needs doing before you start to do it
http://forum.xda-developers.com/showthread.php?t=2265618
:fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:
The search option would have found these for you and saved some time and heartache :highfive:
L0rdNels0n said:
I think you need to read Vomers guide and install using the ADB Method
http://forum.xda-developers.com/showthread.php?t=2365506&page=4
Click to expand...
Click to collapse
I have (almost) the same problem as OP: bootloader (HBOOT 1.44) shows "locked", "tampered" and "S-ON". The radio is apparently broken and I want a new unit, so I installed mike1986's "stock 4.2.2" ROM, because htc1guru.com is broken and androidruu.com apparently has corrupt RUU downloads (every RUU I've tried fails miserably, and extracted rom.zips don't work either). It's rooted, with SuperSU. I relocked and S-ONed the bootloader with revone, but then found a stock backup and tried to unlock/S-OFF so I could install TWRP back.
Unfortunately for me (and OP), revone -P fails with error -6. revone -s 0 -u fails with error -1. revone -t reports success, but the tampered flag remains there. Trying to flash TWRP with a market app freezes Android. Trying to unlock the bootloader with HTCDev reports success in fastboot, but the unlock prompt never shows up, and the bootloader freezes.
Read again: revone fails. That guide, as well as the other 4 or so similar ones floating around, are useless in this case.
If anyone has any ideas (or an HTC EastEurope RUU download that doesn't fail), I'm open to hearing them.
AndyM3 said:
I have (almost) the same problem as OP: bootloader (HBOOT 1.44) shows "locked", "tampered" and "S-ON". The radio is apparently broken and I want a new unit, so I installed mike1986's "stock 4.2.2" ROM, because htc1guru.com is broken and androidruu.com apparently has corrupt RUU downloads. It's rooted, with SuperSU. I relocked and S-ONed the bootloader with revone, but then found a stock backup and tried to unlock/S-OFF so I could install TWRP back.
Unfortunately for me (and OP), revone -P fails with error -6. revone -s 0 -u fails with error -1. revone -t reports success, but the tampered flag remains there. Trying to flash TWRP with a market app freezes Android. Trying to unlock the bootloader with HTCDev reports success in fastboot, but the unlock prompt never shows up, and the bootloader freezes.
Read again: revone fails. That guide, as well as the other 4 or so similar ones floating around, are useless in this case.
If anyone has any ideas (or an HTC EastEurope RUU download that doesn't fail), I'm open to hearing them.
Click to expand...
Click to collapse
What's the date of your hboot? If it's after May 2013, it might be a patched version (applies to AT&T and T-Mobile), otherwise revone will work.
Read here: http://forum.xda-developers.com/showthread.php?t=2431515 for the prerequisites to get S-Off.
Try that, and report back and we'll go from there.
PS: keep S-Off, no need to ever to back S-On even for repair because some devices are shipped S-Off. The repair center can't prove you've done anything to your phone, unless they see "LOCKED / RELOCKED / TAMPERED"
nkk71 said:
What's the date of your hboot? If it's after May 2013, it might be a patched version (applies to AT&T and T-Mobile), otherwise revone will work.
Read here: http://forum.xda-developers.com/showthread.php?t=2431515 for the prerequisites to get S-Off.
Try that, and report back and we'll go from there.
PS: keep S-Off, no need to ever to back S-On even for repair because some devices are shipped S-Off. The repair center can't prove you've done anything to your phone, unless they see "LOCKED / RELOCKED / TAMPERED"
Click to expand...
Click to collapse
Bootloader date is May 3, 2013. It's a downloaded "stock unmodified" 1.44 HBOOT. I'm not in the US.
On the other hand, I'm on a 4.2.2 ROM right now. Should I try to downgrade? If yes, can anyone point me in the direction of an HTC RUU that actually works? (CID is HTC__032)
AndyM3 said:
Bootloader date is May 3, 2013. It's a downloaded "stock unmodified" 1.44 HBOOT. I'm not in the US.
On the other hand, I'm on a 4.2.2 ROM right now. Should I try to downgrade? If yes, can anyone point me in the direction of an HTC RUU that actually works? (CID is HTC__032)
Click to expand...
Click to collapse
May 3 is good, revone should work. If it's not working on your ROM now, try downgrading to a 4.1.2 ROM to try to make it work.
For the RUU, have you looked here: http://forum.xda-developers.com/showthread.php?t=2158151
Otherwise try to get @Mike1986 odexed ROM, it worked a couple of days ago for someone else: http://forum.xda-developers.com/showthread.php?t=2457354 (read last post)
nkk71 said:
May 3 is good, revone should work. If it's not working on your ROM now, try downgrading to a 4.1.2 ROM to try to make it work.
For the RUU, have you looked here: http://forum.xda-developers.com/showthread.php?t=2158151
Otherwise try to get @Mike1986 odexed ROM, it worked a couple of days ago for someone else: http://forum.xda-developers.com/showthread.php?t=2457354 (read last post)
Click to expand...
Click to collapse
I downloaded a 1.20.401 RUU (should be 4.1.2, probably), and I am on mike1986's odexed ROM right now. I'd downgrade, but how? I can't install a custom recovery.
Edit: RUU exited with a "bootloader version error". Could I have downloaded a corrupt HBOOT or something? revone gave success messages about five times now, but the bootloader still says "LOCKED" and "S-ON".
AndyM3 said:
the bootloader still says "LOCKED" and "S-OFF".
Click to expand...
Click to collapse
So S-Off achieved great.
What's still the problem?
nkk71 said:
So S-Off achieved great.
What's still the problem?
Click to expand...
Click to collapse
Typo, sorry. It's S-ON.
AndyM3 said:
Typo, sorry. It's S-ON.
Click to expand...
Click to collapse
Hi Andy,
I just re-read your original post, and am getting a bit confused cause you said "bootloader (HBOOT 1.44) shows "locked", "tampered" and "S-ON"." you mean RELOCKED?
Probably best if you post your "fastboot getvar all" (remove IMEI and serial number) , full details of the ROM you're using, and a screenshot of your bootloader.
As for "HTCDev reports success in fastboot, but the unlock prompt never shows up", maybe you should try the process from the beginning again and get a new unlocktocken.
nkk71 said:
Hi Andy,
I just re-read your original post, and am getting a bit confused cause you said "bootloader (HBOOT 1.44) shows "locked", "tampered" and "S-ON"." you mean RELOCKED?
Probably best if you post your "fastboot getvar all" (remove IMEI and serial number) , full details of the ROM you're using, and a screenshot of your bootloader.
As for "HTCDev reports success in fastboot, but the unlock prompt never shows up", maybe you should try the process from the beginning again and get a new unlocktocken.
Click to expand...
Click to collapse
I did mean "locked". I used revone -l to restore the lock status. On the other hand, now I accidentally installed HBOOT 1.54 instead (figured the bootloader may be broken and installed a 2.24 firmware package). I tried HTCDev Unlock twice (the whole process), and it... still doesn't work. To be more specific, fastboot flash unlocktoken reports success, but the next fastboot command, whatever that may be (getvar, reboot, etc), errors out with something to the effect of "could not load custom splash". Trying to flash any sort of different HBOOT (older/newer) complains about signatures, or maybe that's just my downloads.
Of course, revone doesn't work with 1.54, so I'm pretty much ****ed. Might as well take the damn thing back to Orange.
AndyM3 said:
I did mean "locked". I used revone -l to restore the lock status. On the other hand, now I accidentally installed HBOOT 1.54 instead (figured the bootloader may be broken and installed a 2.24 firmware package). I tried HTCDev Unlock twice (the whole process), and it... still doesn't work. To be more specific, fastboot flash unlocktoken reports success, but the next fastboot command, whatever that may be (getvar, reboot, etc), errors out with something to the effect of "could not load custom splash". Trying to flash any sort of different HBOOT (older/newer) complains about signatures, or maybe that's just my downloads.
Of course, revone doesn't work with 1.54, so I'm pretty much ****ed. Might as well take the damn thing back to Orange.
Click to expand...
Click to collapse
Sometimes a factory reset can help with the unlock token, but since you're on 1.54 now it would make little difference.
Sorry & good luck
Sent from my HTC One using xda app-developers app
Yep. I'm in exactly the same boat. Actually, I am on 1.44 HBOOT, dated May 3rd, and none of the available options worked. And yes, I've tried the links included in subsequent posts. And I'm "locked" via same way as above. Since I was selling the phone and trying to revert to stock, my only option was to manually erase everything and send it off. I couldn't do a factory reset, because it just kicked me to bootloader with a "security warning" error. Couldn't install older RUU, as it would just hang at the HTC black screen with no green progress bar.
AndyM3 said:
Bootloader date is May 3, 2013. It's a downloaded "stock unmodified" 1.44 HBOOT. I'm not in the US.
On the other hand, I'm on a 4.2.2 ROM right now. Should I try to downgrade? If yes, can anyone point me in the direction of an HTC RUU that actually works? (CID is HTC__032)
Click to expand...
Click to collapse
Same problem
Hey guys, I have a same problem, and I'm pissed off and depressed :crying:
I tried GPE, but then I wanted to go back to Sense, and then everything went wrong. I have HBOOT 1.54, S-ON, RELOCKED, TAMPERED. I can't unlock the bootloader, although cmd writes that writing was successful, and the phone still says "RELOCKED". I can't get to system and recovery because always get into bootloader with the message "Security Warning". I can't upload any RUU, recovery, nothing ... always cmd writes "failed", in case RUU (1.28.401.7 - my regional which should work) writes "Error 155".
Please guys, help me. I do not know what to do and I'm clueless.
PlaviiCZ said:
Hey guys, I have a same problem, and I'm pissed off and depressed :crying:
I tried GPE, but then I wanted to go back to Sense, and then everything went wrong. I have HBOOT 1.54, S-ON, RELOCKED, TAMPERED. I can't unlock the bootloader, although cmd writes that writing was successful, and the phone still says "RELOCKED". I can't get to system and recovery because always get into bootloader with the message "Security Warning". I can't upload any RUU, recovery, nothing ... always cmd writes "failed", in case RUU (1.28.401.7 - my regional which should work) writes "Error 155".
Please guys, help me. I do not know what to do and I'm clueless.
Sorry for my bad english, but I hope hope you'll understand.
Click to expand...
Click to collapse
You have google CID and s-on and relocked .. your pretty much screwed near as i can tell. did you try fastboot oem unlock ?
clsA said:
You have google CID and s-on and relocked .. your pretty much screwed near as i can tell. did you try fastboot oem unlock ?
Click to expand...
Click to collapse
Yeah, I'm dumbass...Yes, I did, and nothing...just "failed" in cmd. Should I try again to tell you, what is in cmd exactly written?
EDIT: Please help (
No one knows anything?

Failed: Return to stock and unrooted (Verizon)

I posted in the Verizon forums a day ago, but have received little to no help. Now I hope that someone can help me here.
Original post http://forum.xda-developers.com/showthread.php?t=2599610
I used this thread to unroot and return to stock http://forum.xda-developers.com/show...highlight=s-on
I had done this before with one of CM 10 and I kept the files used in this thread.
I switched to AOKP kitkat 12-30-13. I wanted to return to stock and unrooted.
I got to the oem ruu and kept receiving this message. FAILED (remote: 90 hboot pre-update! please flush image again immediately)
I did this repeatedly as followed. It went over 5 times. I figured this was a problem. Now I am stuck in the bootloader where my phone is locked and S-on. I tried to flash it again and now I get remote: 12 signature verify failed.
It also says ***TAMPERED*** at the top of bootloader, above ***LOCKED***
Edit: I wanted to mention that I do have a backup of my kitkat state at the beginning of all of this. It is in twrp, but I can't flash install the twrp.img, signature verify failed.
What exactly was the order you did this in? When I set my phone back to stock, I did it in the following order:
1. run RUU
2. lock bootloader
3. S-ON
I'm guessing you did not do it in that order, since you are trying to flash the RUU with a locked bootloader and S-ON.
Since the RUU failed to flash, you should still have TWRP. You said signature verification failed, but I believe there is an option in TWRP that lets you toggle signature verification. Once you have turned off signature verification, try restoring your backup.
If your backup restores successfully, you need to S-OFF your phone and unlock your bootloader, as you will need the unlocked bootloader later on.
The following is the gist of what you need to do. Check here for a more detailed explanation:
http://forum.xda-developers.com/showthread.php?t=2358738
Once you S-OFF your phone, set your CID to stock and run the RUU. You should be back with stock ROM and stock recovery. However, to lock the bootloader and S-ON your phone, you need superuser. You need to flash TWRP (which is why the bootloader needs to be unlocked at this point) so that you can flash superuser (SuperSU).
Once you have superuser, flash the stock recovery through fastboot. This will only work with an unlocked bootloader, which is why you must flash the stock recovery before you lock the bootloader.
Superuser is still functional with stock recovery. Run through the commands to reset the tamper flag, lock the bootloader, and set your phone back to S-ON. You can then unroot through the SuperSU app.
sweetnsour said:
What exactly was the order you did this in? When I set my phone back to stock, I did it in the following order:
1. run RUU
2. lock bootloader
3. S-ON
I'm guessing you did not do it in that order, since you are trying to flash the RUU with a locked bootloader and S-ON.
Since the RUU failed to flash, you should still have TWRP. You said signature verification failed, but I believe there is an option in TWRP that lets you toggle signature verification. Once you have turned off signature verification, try restoring your backup.
If your backup restores successfully, you need to S-OFF your phone and unlock your bootloader, as you will need the unlocked bootloader later on.
The following is the gist of what you need to do. Check here for a more detailed explanation:
http://forum.xda-developers.com/showthread.php?t=2358738
Once you S-OFF your phone, set your CID to stock and run the RUU. You should be back with stock ROM and stock recovery. However, to lock the bootloader and S-ON your phone, you need superuser. You need to flash TWRP (which is why the bootloader needs to be unlocked at this point) so that you can flash superuser (SuperSU).
Once you have superuser, flash the stock recovery through fastboot. This will only work with an unlocked bootloader, which is why you must flash the stock recovery before you lock the bootloader.
Superuser is still functional with stock recovery. Run through the commands to reset the tamper flag, lock the bootloader, and set your phone back to S-ON. You can then unroot through the SuperSU app.
Click to expand...
Click to collapse
Using the procedure shown, I followed the steps exactly stated in the post. However you are right, about switching the methods 2 and 3. I didn't realize what using the last step, switching to s-on would do. I failed to flash the stock rom, and then proceeded to s-on, and during that I guess the bootloader locked, or it locked before when it was trying to flash stock.
Anyways...I only briefly read the links you posted, but it seems most of the stuff, and the download files are for sprint, att, t-mobile, google, etc but not Verizon. I'm not sure if these methods will help much with a verizon phone, or I might get stuck along the way looking for Verizon actions.
Also in the very red for the s-off revone it says that it does not support hboot 1.54, which is what I have.
geeibara said:
Using the procedure shown, I followed the steps exactly stated in the post. However you are right, about switching the methods 2 and 3. I didn't realize what using the last step, switching to s-on would do. I failed to flash the stock rom, and then proceeded to s-on, and during that I guess the bootloader locked, or it locked before when it was trying to flash stock.
Anyways...I only briefly read the links you posted, but it seems most of the stuff, and the download files are for sprint, att, t-mobile, google, etc but not Verizon. I'm not sure if these methods will help much with a verizon phone, or I might get stuck along the way looking for Verizon actions.
Also in the very red for the s-off revone it says that it does not support hboot 1.54, which is what I have.
Click to expand...
Click to collapse
The method should work no matter the carrier; just be sure you have the appropriate files. What I mean is, the only time you need to consider the carrier is for the RUU file.
hboot 1.54 is not be supported by revone, but it is supported by rumrunner.
I think for now, you should just try to get your phone booted. Were you able to restore your backup?
sweetnsour said:
The method should work no matter the carrier; just be sure you have the appropriate files. What I mean is, the only time you need to consider the carrier is for the RUU file.
hboot 1.54 is not be supported by revone, but it is supported by rumrunner.
I think for now, you should just try to get your phone booted. Were you able to restore your backup?
Click to expand...
Click to collapse
I couldn't access twrp, when I try to go to recovery from the bootloader, it takes me back to fastboot. So I was unable to do that.
I don't know how to gain s-off from my point. You said rumrunner should support it, but I tried running it, and it failed, it didn't get to the first step because it had to recognize the device, where adb commands cant recognize it.
Anyways, I gave up and asked for a warranty replacement.
geeibara said:
I couldn't access twrp, when I try to go to recovery from the bootloader, it takes me back to fastboot. So I was unable to do that.
I don't know how to gain s-off from my point. You said rumrunner should support it, but I tried running it, and it failed, it didn't get to the first step because it had to recognize the device, where adb commands cant recognize it.
Anyways, I gave up and asked for a warranty replacement.
Click to expand...
Click to collapse
to be able to reflash twrp you need to unlock your bootloader that is why you are getting signature fail error

Unlocking 'relocked' bootloader with hboot 1.55 and S-OFF

Well, I'm usually able to dig myself out of messes I get myself into but this one has had me hunting a few hours. Here's the run-down.
1) S-OFF with 1.44 a while ago, rooted and unlocked bootloader
2) Got camera problem, would like to return phone to stock for warranty
3) Flashed a stock RUU, went fine. Stock recovery and bootloader work fine, hboot was upgraded to 1.55 (my mistake, should have noticed this)
4) Got sidetracked when trying to lock the bootloader and entered fastboot oem lock
So now I have a 're-locked' bootloader on 1.55 with S-OFF. I don't want to unlock through HTCDev, I can't use revone to unlock because I'm on 1.55, and I don't have a custom recovery, and can't flash one because I'm relocked.
Any ideas how I can unlock the bootloader here (or downgrade hboot, I have the zip but can't flash it)? I can probably handle the rest myself, after I smack myself over the head a few times.
The goal here is to have the bootloader 'LOCKED', and I'll then take my chances with S-ON, with the latest firmware but a downgraded (1.44) bootloader before handing it over for warranty purposes.
OK, it looks as though I can patch hboot files OK. Will take a look around for a patched one.
Hboot 1.44 will unlock using revone. Make sure to be on 1.x.x based ROM right after
sent from my mobile device
SaHiLzZ said:
Hboot 1.44 will unlock using revone. Make sure to be on 1.x.x based ROM right after
sent from my mobile device
Click to expand...
Click to collapse
Sorted, thanks. Found an older ROM that flashed fine with supercid. Think I'll keep S-OFF and just lock the bootloader. With this being a likely hardware issue I'm hoping I'll be fine with just that.

[Q] Active cmdline overflow after S-off

Hi,
After flashing a stock recovery to Update the OTA, I flashed back the custom recovery, I past S-Off to use FREEDOM everything worked nice, then I wanted to format my phone and I accidentally deleted anything!
Then I downloaded One_4.19.401.11_odexed.zip RUU somewhere, I flashed it back everything is okey, I tried to boot the phone but it always show me the fastboot screen and I can just go to the bootloader screen With a red message :
"active cmdline overflow 10XX", I couldn't access neither the recovery nor the system!
I triend to S-on from the fastboot mod : "fastboot oem writesecureflag 3" It worked and my phone is Working fine
I tried to s-off again but always I face the same problem until I S-on it again...
The question is from where I got this problem ? and Why ? and how can I S-off my phone with safety to escape this problem and use FREEDOM ?
and thanks
UP!
FYI, you did something bad... to enable S-On when your firmware is not 100% working perfectly ensures that you probably can't fix it.
But can you clarify what is the problem now? Did you say your phone's OS is working, but that you can't boot to the bootloader?
fenstre said:
FYI, you did something bad... to enable S-On when your firmware is not 100% working perfectly ensures that you probably can't fix it.
But can you clarify what is the problem now? Did you say your phone's OS is working, but that you can't boot to the bootloader?
Click to expand...
Click to collapse
When my phone is S-Off I can just boot to the bootloader I can't access the OS! But when S-on I can access both of them like I could do before, but always with a message on Fastboot : Active cmdline overflow ... and I can make S-off/S-on whenever I want ! and now it's S-on so I can work fine with my phone
Now I just want to S-Off again after fixing the problem to boot into the OS as the bootloader without any problem !
This thread implies you may have flashed a system that doesn't match your CID (which is probably obvious, considering that that's the main reason people get S-Off). I suggest changing your CID to match the new system, or change it to the SuperCID value. But it would be even better to install the right RUU for your phone and region, if it exists.
fenstre said:
This thread implies you may have flashed a system that doesn't match your CID (which is probably obvious, considering that that's the main reason people get S-Off). I suggest changing your CID to match the new system, or change it to the SuperCID value. But it would be even better to install the right RUU for your phone and region, if it exists.
Click to expand...
Click to collapse
Ow, Really! Can you explain more please ? Why changing the CID ? How to find the good one ? what are the consequences ? Why it's better to install the right RUU instead changing the CID ?
Then, I think I already changed the CID someday to 111111111....
xsodia said:
Ow, Really! Can you explain more please ? Why changing the CID ? How to find the good one ? what are the consequences ? Why it's better to install the right RUU instead changing the CID ?
Then, I think I already changed the CID someday to 111111111....
Click to expand...
Click to collapse
S-off your phone and flash 1.44 hboot RUU. That's how I got my phone to boot up. I'm still getting that "active cmdline overflow" message, but I managed to update to 1.54 hboot (4.19.401.8 firmware) and now running ARHD 62. I can't flash Elemental kernel, but I flashed Faux kernel succesfully. My guess is that aroma installer somehow provoques active cmdline overflow. Anyway, downgrading to 1.44 hboot saved my phone
donkeykong1 said:
S-off your phone and flash 1.44 hboot RUU. That's how I got my phone to boot up. I'm still getting that "active cmdline overflow" message, but I managed to update to 1.54 hboot (4.19.401.8 firmware) and now running ARHD 62. I can't flash Elemental kernel, but I flashed Faux kernel succesfully. My guess is that aroma installer somehow provoques active cmdline overflow. Anyway, downgrading to 1.44 hboot saved my phone
Click to expand...
Click to collapse
Lots of people can't flash ElementalX. I couldn't flash it when I had hboot 1.54, but after HTC repaired a hardware issue and the phone was upgraded to hboot 1.56, the Aroma installer bugs went away.
fenstre said:
Lots of people can't flash ElementalX. I couldn't flash it when I had hboot 1.54, but after HTC repaired a hardware issue and the phone was upgraded to hboot 1.56, the Aroma installer bugs went away.
Click to expand...
Click to collapse
I know that, but I was flashing Elemental just fine before this error and I was on 1.56 hboot
To now, I don't know what to do --'
xsodia said:
To now, I don't know what to do --'
Click to expand...
Click to collapse
Whats wrong?
xsodia said:
To now, I don't know what to do --'
Click to expand...
Click to collapse
active cmdline overflow is caused by a messed misc partition, there is a nice guide in the general section how to fix this: http://forum.xda-developers.com/showthread.php?t=2739126

Categories

Resources