I bought a used HTC Flyer 3g and it was been working ok and making phone calls too, then I decide to upgrade it to HC but sadly it stop at the middle of steps and now when it boot it show the screen with HTC on it and then go to a black screen and nothing more, I go to boot loader and try every command there but nothing happened
so can any body tell me what I should do to fix it
Boot Loader before do any thing was shows that info
-Revolutionary-
FLYER PVT SHIP S-OFF RL
HBOOT-6.10.1002
MICROP-0950
RADIO-3809.05.04.10_M
eMMC-boot
May 4 2011, 11:04:45
now after the attempt to upgrade it shows :
*** UNLOCKED ***
FLYER PVT SHIP S-ON RL
HBOOT-1.11.0011
MICROP-0950
RADIO-3822.10.08.07_M
eMMC-boot
Oct 25 2011, 16:55:07
What process are you using to upgrade? Looks like official means like the RUU?
Did you change it to S-on, or did that happen automatically?
redpoint73 said:
What process are you using to upgrade? Looks like official means like the RUU?
Did you change it to S-on, or did that happen automatically?
Click to expand...
Click to collapse
I just follow this : http://forum.xda-developers.com/showthread.php?t=1409296
and the S-ON just happened automatically
thank you for your care
Just flashing a custom ROM would not make you S-on, nor change the hboot version. You must have done something else also. Are there perhaps some steps you did, that you forgot to mention?
redpoint73 said:
Just flashing a custom ROM would not make you S-on, nor change the hboot version. You must have done something else also. Are there perhaps some steps you did, that you forgot to mention?
Click to expand...
Click to collapse
I really don't remember that I did something more , except that I do install revolutionary v6 ( I think ) then when I did not find the Power Off option in it I do reinstall revolutionary v4, that's all I do remember
I am sorry for my bad memory, but I really do thank you for your help
When you mention revolutionary v4 and v6, I believe you are talking about the revolutionary version of the Clockworkmod recovery. Flashing different recoveries would not have made you S-on, would not have unlocked the bootloader, and would not have upgraded your hboot. You must have done some other steps you are forgetting, for these things to have happened. Steps you really shouldn't have done, as you are in a much worse position now than before (when you were s-off).
S-off will not go back to S-on by itself. It is only changed if you specifically make it S-on. Similarly with hboot, it won't change by itself, by flashing a custom ROM or custom recovery (its usually changed by running an RUU or installing an OTA). You did something to change the hboot version.
In the future, I recommend being much more methodical about what steps you take. Keep track of the steps, understand what you are doing, and don't try anything unless you are confidant its correct. Its very difficult to help you, if you don't even remember what you did. And not remembering what you did implies that you might have been rushing a bit, and trying things without fully understanding what you are doing. As I mentioned, the result now is that you have done much more harm than good. Modding the phone without fully understanding what you are doing can also easily result in a bricked device. Although I sympathize that its hard on this device in particular, since this forum has become very quiet these days, with not many users here to get advice from.
You options at this point are:
1) Try to downgrade hboot, so you can get S-off again. Your current hboot is not compatible with the evolutionary S-off method. I can't personally vouch for this method, but it seemed to at least work for the OP: http://forum.xda-developers.com/showthread.php?t=2070140
2) Live with S-on and an unlocked bootloader. You can still flash ROMs. All it means is that you have to flash boot.img seperately using fastboot (with Flyer connected to computer), every time you flash a custom ROM. You also can't flash radios with S-on (may or may not be important to you).
This is the easier option in your present condition, as you are already bootloader unlocked (based on the UNLOCKED flag in hboot). As long as you have CWM installed, you are already set to flash custom ROMs. If you are having problems flashing the ROM you linked, I believe the steps of flashing boot.img using fastboot is all you are missing. See my post here for details on how to do this: http://forum.xda-developers.com/showpost.php?p=37898551&postcount=2
redpoint73 said:
When you mention revolutionary v4 and v6, I believe you are talking about the revolutionary version of the Clockworkmod recovery. Flashing different recoveries would not have made you S-on, would not have unlocked the bootloader, and would not have upgraded your hboot. You must have done some other steps you are forgetting, for these things to have happened. Steps you really shouldn't have done, as you are in a much worse position now than before (when you were s-off).
S-off will not go back to S-on by itself. It is only changed if you specifically make it S-on. Similarly with hboot, it won't change by itself, by flashing a custom ROM or custom recovery (its usually changed by running an RUU or installing an OTA). You did something to change the hboot version.
In the future, I recommend being much more methodical about what steps you take. Keep track of the steps, understand what you are doing, and don't try anything unless you are confidant its correct. Its very difficult to help you, if you don't even remember what you did. And not remembering what you did implies that you might have been rushing a bit, and trying things without fully understanding what you are doing. As I mentioned, the result now is that you have done much more harm than good. Modding the phone without fully understanding what you are doing can also easily result in a bricked device. Although I sympathize that its hard on this device in particular, since this forum has become very quiet these days, with not many users here to get advice from.
You options at this point are:
1) Try to downgrade hboot, so you can get S-off again. Your current hboot is not compatible with the evolutionary S-off method. I can't personally vouch for this method, but it seemed to at least work for the OP: http://forum.xda-developers.com/showthread.php?t=2070140
2) Live with S-on and an unlocked bootloader. You can still flash ROMs. All it means is that you have to flash boot.img seperately using fastboot (with Flyer connected to computer), every time you flash a custom ROM. You also can't flash radios with S-on (may or may not be important to you).
This is the easier option in your present condition, as you are already bootloader unlocked (based on the UNLOCKED flag in hboot). As long as you have CWM installed, you are already set to flash custom ROMs. If you are having problems flashing the ROM you linked, I believe the steps of flashing boot.img using fastboot is all you are missing. See my post here for details on how to do this: http://forum.xda-developers.com/showpost.php?p=37898551&postcount=2
Click to expand...
Click to collapse
I know that I give u a big headache with my silly questions and I really value your help
I think what's make it S-ON that I use HCT site to unlock the device and the Hboot change when I start the proses of upgrading to HC( that's what come up to my mind) any way to flow the way in step 1 I believe I should be on Android but as u know that the device is just start with HTC on a white screen and the a black screen with backlight ( like it try to start the rom but it can't) so can that way work
According to step 2, I really don't care if it S-ON or S-OFF as long as it work and I can install a custom rom
abayoumi said:
I know that I give u a big headache with my silly questions and I really value your help
I think what's make it S-ON that I use HCT site to unlock the device and the Hboot change when I start the proses of upgrading to HC
Click to expand...
Click to collapse
Unlocking at HTCDev.com won't make you S-on, and I don't think changing the hboot would, either.
You're not giving me a headache. But I just don't understand why people mod their phones without really understanding what they are doing. If you were S-off, there is no reason why you should have tried to unlock the bootloader via HTCDev.com.
abayoumi said:
According to step 2, I really don't care if it S-ON or S-OFF as long as it work and I can install a custom rom
Click to expand...
Click to collapse
I agree, this is probably the easiest way to get the device on HC. Just flash a HC ROM and flash the boot.img using fastboot.
Thank you, now it's working ok with this info:
*** UNLOCKED ***
FLYER PVT SHIP S-ON RL
HBOOT-1.11.0011
MICROP-0950
RADIO-3022.10.00.07_M
eMMC-boot
Oct 25 2011,16:55:07
FASTBOOT 9V AC
and it run Android version :3.2 with LeeDrOiD HC V4.3.0 rom
My question is can I install another rom like this on
Cool3D Honey v6 3.63.708
http://forum.xda-developers.com/showthread.php?t=1409296
thank you very much for all you help and support
Sure, you can flash any HC, ICS or JB custom ROM that you see in the Development section. They are all flashed the same way. Just put the ROM on your SD, boot recovery, wipe user data (factory reset) wipe Dalvik, wipe cache, and flash the ROM. GB ROMs require a different hboot. So if you want to flash any of those, you would have to downgrade back to the GB hboot (guide can be found in Development forum). Probably not worth the hassle, unless you really want to revert to GB and stay there.
Your welcome. Please click the "Thanks" button for any posts that helped you.
Any HC rom
after I install Cool3D-Honey-v6-Flyer rom I discover that I can't make the Bluetooth headset work, it is " connected but not paired " and after searching hear and there I can't find a rom support the Bluetooth headset
So is there is any HC rom get that fix and work?
Related
Followed the guide from Paul on Modac, while attempting to unlock the bootloader I ran into an error that was resolved by updating fastboot. I successfully rooted,flashed custom rom and booted. I noticed that while in bootloader I went from S-OFF to S-ON. The fast boot error came attempting " 'fastboot flash recovery revolutionary-cwm-4.0.1.4-flyer.newhboot.img' " The error 'Locked' the bootloader. After I updated fastboot above command worked, BUT I was now back to S-On.
What part of the process should I redo in order to get S-OFF back?
What are my limitations with S-ON?
Any thoughts, comments, suggestions and especially solutions are appreciated.
Also the haptic buttons ( same row as pen button) do NOT work. They do not light and are not usable
Yeah the buttons don't work in honeycomb because you have the on screen buttons to do the job.
And It's normal to have s-on. HTC's method only unlocks the bootloader. I'm pretty sure you aren't able to flash kernels or something like that.
Sent from my HTC Evo 3D using XDA App
Gumby63 said:
Yeah the buttons don't work in honeycomb because you have the on screen buttons to do the job.
And It's normal to have s-on. HTC's method only unlocks the bootloader. I'm pretty sure you aren't able to flash kernels or something like that.
Sent from my HTC Evo 3D using XDA App
Click to expand...
Click to collapse
I was able to flash a custom rom.
Just got home from work. Revolutionary does not support the HC bootloader version 1.11.0006.
My question is, what part of the process caused my device to go from S-ON->S-OFF-> Back to S-ON?
I know I'm limited now, can I downgrade my bootloader version 1.11.0003 or 1.11.0000?
Thank for your help
ATownI20 said:
I was able to flash a custom rom.
Just got home from work. Revolutionary does not support the HC bootloader version 1.11.0006.
My question is, what part of the process caused my device to go from S-ON->S-OFF-> Back to S-ON?
I know I'm limited now, can I downgrade my bootloader version 1.11.0003 or 1.11.0000?
Thank for your help
Click to expand...
Click to collapse
When you first used revolutionary you got complete s-off, and then during the process of upgrading to honeycomb you flashed a new hboot which gave you s-on again because well..It's a new hboot. Lol. And the only way you can downgrade your hboot is to run the ruu for your model flyer to revert back to gingerbread. If you have the US 16gb version then you cannot go back to gingerbread because there isn't a ruu yet.
Hopefully I'm not confusing you more
Revolutionary does not support the HC bootloader version 1.11.0006.
but after unlock bootloader go htc dev.com and unlock bootloader from step by step guaid....after you see in fastboot
"""""""unlocked""""""""
FLYER PVT SHIP S-ON
And flash castom recovery
copy revolutionary-cwm-4.0.1.4-flyer.newhboot.img in to dir (you create dir ,by htc dev guaid)
and run command in cmd
fastboot flash recovery revolutionary-cwm-4.0.1.4-flyer.newhboot.img' this recovery support all castom Rom based on Honeycomb
S-Off not needed for you.
Sorry my bad English...
Gumby63 said:
When you first used revolutionary you got complete s-off, and then during the process of upgrading to honeycomb you flashed a new hboot which gave you s-on again because well..It's a new hboot. Lol. And the only way you can downgrade your hboot is to run the ruu for your model flyer to revert back to gingerbread. If you have the US 16gb version then you cannot go back to gingerbread because there isn't a ruu yet.
Hopefully I'm not confusing you more
Click to expand...
Click to collapse
No not really confused by your explanation. What confuses me if is the process was suppose to give me S-OFF in the first place. I understand the logic of the new hboot being S-ON. But if you're following me you kinda see where I'm thinking 0_o lol.
piramida13 said:
Revolutionary does support the HC bootloader version 1.11.0006.
but only after unlock bootloader , go htc dev.com and unlock bootloader from step by step guaid....after you see in fastboot
"""""""unlocked""""""""
FLYER PVT SHIP S-ON
copy revolutionary-cwm-4.0.1.4-flyer.newhboot.img in to dir (you create dir ,by htc dev guaid)
and run command in cmd
fastboot flash recovery revolutionary-cwm-4.0.1.4-flyer.newhboot.img'
Click to expand...
Click to collapse
So I'm not suppose to have S-OFF after running that command?
I think that's what he is saying. My bootloader was a totally different one. So I don't really have any knowledge. What I would do is go into the development forum and do a quick search and see if anyone answered the question or had a similar problem and fixed. It helps out a lot. I don't want to give you knowledge and mess anything up on your end.
ATownI20 said:
No not really confused by your explanation. What confuses me if is the process was suppose to give me S-OFF in the first place. I understand the logic of the new hboot being S-ON. But if you're following me you kinda see where I'm thinking 0_o lol.
Click to expand...
Click to collapse
haha the process of going to honeycomb was not supposed to give you s-off, simply an unlocked bootloader. I think i'm following you
My understanding of the situation is the hboot that is required to install HC sets s-on, and currently it is not possible to change it back to s-off without reverting back to the original hboot using the RUU. Even if you changed back to the original hboot, honeycomb would no longer boot.
At least, that's my understanding.
The only way right now to get S-OFF is with HBOOT versions 1.11.0000 and 1.11.0003. Since you have 1.11.0006, needed for running HC on the Flyer, Revolutionary doesn't support it, so right now you can only have the unlocked boot loader and S-ON. If you run the Revolutionary tool with HBOOT 1.11.0006, it will tell you it is not supported, and won't run.
The only way it would be supported is when the AlphaRev/Unrevoked team update their tool to support it. So running that command listed above does cause this, but it is required in order to run HC on the Flyer. Without it, I don't know if you'd have a $300 brick or what.
Parastie said:
My understanding of the situation is the hboot that is required to install HC sets s-on, and currently it is not possible to change it back to s-off without reverting back to the original hboot using the RUU. Even if you changed back to the original hboot, honeycomb would no longer boot.
At least, that's my understanding.
Click to expand...
Click to collapse
Thanks chief... I was just a little confused as the guides talked about permanent S-OFF... But if S-ON is how I'm suppose to be right now, then S-ON it is! lol...
I am in the same boat
Just Upgraded and noticed S-on as well...
what am I limited to with S-ON.. and whats the *UNLOCKED* mean?
*UNLOCKED*
FLYER PVT SHIP S_ON RL
HBOOT 1.11.006
MICROP 0850
Radio-3821.08.00.26
eMM-BOOT
*UNLOCKED*
FLYER PVT SHIP S_ON RL
HBOOT 1.11.006
MICROP 0850
Radio-3821.08.00.26
eMM-BOOT
I have exactly the same issue.
is there anyway out of S-ON?
Hey all,
I've been trying to figure out whether my phone can be rooted/s-off.
From my understanding of processes I think I've screwed myself with an OTA but figured I would ask this anyways.
In my Hboot screen it claims I have HBoot- 1.12.0000 which from everything I've read has the ability to achieve S-off.
(My Hboot screen)
*** Locked ***
JEWEL PVT SHIP S-ON RL
HBoot -1.12.0000
Radio -1.02.12.0427
OpenDSP -v25.1.0.32.0405
eMMC-boot
Apr 26 2012, 19:54:01
(End Hboot screen)
Now the problem comes in since I accepted the OTA that put my phone's version to 1.22.651.3 710RD
From what I've read I'll be unable to root without using HTC's dev system.
So my questions are these:
1. Can I achieve root without using HTC's system? (From what I've read the answer is no, but hey no harm in asking it’s the q&a section after all. XD )
2. If not can I use HTC's system can I still achieve S-off?
3. If not do you think there will be a chance to see a root that doesn't use HTC's method?
4. If I can still achieve S-off using HTC's system can I then revert my phone to a RUU of 1.22.651.1 and reroot it from there?
Bonus questions:
5. From what I've read it seems like I'm unable to use RUUs unless I'm already rooted/s-offed but I'll ask it anyways can I use a RUU to restore back to 1.22.651.1 without rooting or being s-offed?
6. Can I perform a factory reset on the phone to get the phone to revert to version 1.22.651.1? (I'm assuming no here or everyone would've done it already. XD)
7. If yes, can I then use the non-HTC system to root my phone followed by s-offing my phone?
Thank you for your time.
ksharks
ksharks said:
Hey all,
I've been trying to figure out whether my phone can be rooted/s-off.
From my understanding of processes I think I've screwed myself with an OTA but figured I would ask this anyways.
In my Hboot screen it claims I have HBoot- 1.12.0000 which from everything I've read has the ability to achieve S-off.
(My Hboot screen)
*** Locked ***
JEWEL PVT SHIP S-ON RL
HBoot -1.12.0000
Radio -1.02.12.0427
OpenDSP -v25.1.0.32.0405
eMMC-boot
Apr 26 2012, 19:54:01
(End Hboot screen)
Now the problem comes in since I accepted the OTA that put my phone's version to 1.22.651.3 710RD
From what I've read I'll be unable to root without using HTC's dev system.
So my questions are these:
1. Can I achieve root without using HTC's system? (From what I've read the answer is no, but hey no harm in asking it’s the q&a section after all. XD )
2. If not can I use HTC's system can I still achieve S-off?
3. If not do you think there will be a chance to see a root that doesn't use HTC's method?
4. If I can still achieve S-off using HTC's system can I then revert my phone to a RUU of 1.22.651.1 and reroot it from there?
Bonus questions:
5. From what I've read it seems like I'm unable to use RUUs unless I'm already rooted/s-offed but I'll ask it anyways can I use a RUU to restore back to 1.22.651.1 without rooting or being s-offed?
6. Can I perform a factory reset on the phone to get the phone to revert to version 1.22.651.1? (I'm assuming no here or everyone would've done it already. XD)
7. If yes, can I then use the non-HTC system to root my phone followed by s-offing my phone?
Thank you for your time.
ksharks
Click to expand...
Click to collapse
you should search the lazypanda thread to see if v1.22.651.3 will work or go to unlimited.io
http://forum.xda-developers.com/showthread.php?t=1737123
If your hboot is 1.12 you're good to go for s-off. Weird that you still have 1.12 after taking the ota though. I'd say go ahead and go for it...the worst that could happen is it won't recognize your phone or you soft brick and have to run the unbricker. That happened to me but I was back up and running in a few minutes.
Once you're s-off, you can flash any base you want...and firmware as well. Just avoid flashing older firmware than what you're currently running since others have bricked from doing that.
If s-off doesn't work for you, you can still htc dev unlock and be able to flash roms and kernels from any base. You just won't be able to flash firmware. RegawMOD should do the trick, just make sure to read about when to manually reboot the phone if you decide to go that route.
Sent from my EVO LTE
yea man your good.. i see u got hboot 1.12. then u can s-off all day!! read up in the lazy panda thread easy as pie!
i have an htc flyer 3g/wifi with gingerbread..,and it was S-ON and the Hboot was 1.10.0000
So Recently there was a problem using the facebook App so to solve that problem i had to root it
and i did a S-OFF through that http://forum.xda-developers.com/showthread.php?t=1194709
and i did all the procedures ..,and the Status of the flyer Right now is the Following:
-Revolutionary-
FLYER PVT SHIP S-OFF RL
HBOOT-6.10.1002
MICROP-xxxx
RADIO-xxxxxxxxxxx
eMMC-boot
May 4 2011, 11:04:45
So After Rooting i made some changes in the rom to fix the facebook problem and it completely ruined it ! and now facebook is working again in the normal rom .,but not working with me .,so i want to get back to the stock status and install new unrooted stock g.b rom
so i tried to follow this http://forum.xda-developers.com/showpost.php?p=19339909&postcount=1 and i understood all the procedures but i can't get an hboot downgrade to 1.10.0000 and i don't know from where to get it + i don't really know where to get a stock rom that is compatible
Please i know i'm a noob and probably will be a huge pain in the ass but please someone help me ...,as this matter killing me !!
That hboot number looks weird, you sure its right? Did you do anything besides the S-Off procedure that changed your hboot (S-Off should not have changed that, I don't believe).
I'm assuming you didn't to a nandroid backup through Clockworkmod before messing with the ROM? If you did, just restore it. If not, you should always always always do a nandroid before messing with the ROM and/or doing any mods.
I don't see how returning to S-on is going to help your case at all. Its just a flag that basically allows all security measure to be bypassed. Going back to S-On isn't going to fix the mistakes you made, doesn't get you anything you don't already have, and will actually limit your options. I don't recommend it for that reason.
You can try to flash the stock rooted GB ROM here: http://forum.xda-developers.com/showthread.php?t=1175589
Normally I'd say to just run the correct RUU for your current hboot/firmware. But if you hboot version is messed up, that might be easier said than done.
I have read pages and pages from the Android Development forum for the HTC Evo 4G LTE and I can't seem to find a solution that works for me because going S-OFF or re-locking bootloader and loading RUU does not seem feasible for my situation.
The phone has custom recovery (TWRP) and we successfully loaded Viperboy's deodexed 3.15 stock ROM.
Baseband is 1.02.12.0427 (super outdated)
This phone was bought second hand and is a HTC dev unlocked phone, S-ON
I would like to update the baseband to 1.12.11.1200 and update the firmware to 3.16
Caveats: I don't have access to the phone, my friend can reload custom ROMs through TWRP, but beyond that I don't think we can go through Dirty Racun and S-Off, I don't know how we can easily check the HBOOT version to determine if the HBOOT version is 1.12
What would happen if we accepted the Sprint OTA? Are we SOL with the baseband because we are S-ON?
Is there any way we can get on MeanBean 3 or stock rooted 3.16?
Any advise would be greatly appreciated.
I wouldnt accept the OTA update to 3.16
I actually did just that when I relocked my phone on Saturday and had all sort of problems after that. Now, I'm not too sure you would even be able to install the update being that your phone is unlocked *citation needed*.
http://forum.xda-developers.com/showthread.php?t=2135670 - talks about the 3.16 OTA problems
thanks, I've definitely advised my friend to stay away from the OTA and disregard it. I think we are experiencing call/wifi issues due to the old baseband. I wonder what are the next possible steps to move forward from here...
BaconMunch said:
thanks, I've definitely advised my friend to stay away from the OTA and disregard it. I think we are experiencing call/wifi issues due to the old baseband. I wonder what are the next possible steps to move forward from here...
Click to expand...
Click to collapse
1. Stay on this baseband and deal with it.
2. Relock and RUU your way up to 3.15 (stay away from 3.16)
3. S-off and Flash a couple full firmware zips.
Sadly I think those are your only option. And to check your hboot just boot into bootloader. Hold volume down when powering on.
tilltheend714 said:
1. Stay on this baseband and deal with it.
2. Relock and RUU your way up to 3.15 (stay away from 3.16)
3. S-off and Flash a couple full firmware zips.
Sadly I think those are your only option. And to check your hboot just boot into bootloader. Hold volume down when powering on.
Click to expand...
Click to collapse
Thanks, I think that seems realistic, I'm concerned that if I relock through HTCDev, I read that some email/password might go to the original seller of the phone (ebay) for confirmation code, so I don't want to get stuck halfway
I am definitely crossing my fingers for HBoot v1.12, to confirm, once I check my version in the bootloader, I guess I can escape without taking any of the menu options (checking YouTube, I'll just go to recovery, enter TWRP, reboot, system).
BaconMunch said:
Thanks, I think that seems realistic, I'm concerned that if I relock through HTCDev, I read that some email/password might go to the original seller of the phone (ebay) for confirmation code, so I don't want to get stuck halfway
I am definitely crossing my fingers for HBoot v1.12, to confirm, once I check my version in the bootloader, I guess I can escape without taking any of the menu options (checking YouTube, I'll just go to recovery, enter TWRP, reboot, system).
Click to expand...
Click to collapse
Relocking the phone is done through fastboot on the computer. Nothing to do with HTC. And Dev unlocked means you get an unlock token from HTC to the email that you signed up with. So if you make your own account on HTC dev and request a token, it should send nothing to the other owner.
And sorry, but I don't understand what you mean by having Hboot 1.12. You mean only flashing the radio through recovery? If that's what you mean than I can't help with that. Not sure how that works or if there are problems with that.
great news! I had someone take screen shots of the HBoot (v.1.12.0000) and TWRP (v2.2.1) menu
Bootloader shows:
Code:
*** TAMPERED ***
*** UNLOCKED ***
JEWEL PVT SHIP S-ON RL
HBOOT-1.12.0000
RADIO-1.02.12.0427
OpenDSP-v25.1.0.32.0405
eMM-boot
So as far as I know, I'm going to make sure there's nothing wrong with the TAMPERED, and then I can flash 1.12.11.1210 through Captain_Throwbacks Radio Only zip and then looks for a 3.16 custom firmware compatible with S-On since I'm on build number 3.15.651.16 CL124461.
I'd appreciate anyone to chime in if I'm going down a bad path here. Cheers!
BaconMunch said:
great news! I had someone take screen shots of the HBoot (v.1.12.0000) and TWRP (v2.2.1) menu
Bootloader shows:
Code:
*** TAMPERED ***
*** UNLOCKED ***
JEWEL PVT SHIP S-ON RL
HBOOT-1.12.0000
RADIO-1.02.12.0427
OpenDSP-v25.1.0.32.0405
eMM-boot
So as far as I know, I'm going to make sure there's nothing wrong with the TAMPERED, and then I can flash 1.12.11.1210 through Captain_Throwbacks Radio Only zip and then looks for a 3.16 custom firmware compatible with S-On since I'm on build number 3.15.651.16 CL124461.
I'd appreciate anyone to chime in if I'm going down a bad path here. Cheers!
Click to expand...
Click to collapse
You've indeed unlocked the bootloader properly but this only let's you flash recoveries and custom roms. You have to S-OFF the phone to update firmware via bootloader. You're other option would be to RUU which would upgrade the firmware and software and that CAN be done with S-ON, however there is a problem with the update which disables touch input so you should either wait for a dev to make custom 3.16 rom and forget about the firmware OR wait for a fix from HTC and run that RUU whenever it comes out.
xlxcrossing said:
You've indeed unlocked the bootloader properly but this only let's you flash recoveries and custom roms. You have to S-OFF the phone to update firmware via bootloader. You're other option would be to RUU which would upgrade the firmware and software and that CAN be done with S-ON, however there is a problem with the update which disables touch input so you should either wait for a dev to make custom 3.16 rom and forget about the firmware OR wait for a fix from HTC and run that RUU whenever it comes out.
Click to expand...
Click to collapse
Thanks xlxcrossing! I messaged Captain for a a recovery flash for the baseband only and he said my approach is no good either. So seems like I have to RUU to get off 1.12 anyways since LazyPanda is not supported and DirtyRacun starts at 1.15
So I am looking at the UNLIMITED.IO site now
step 1) relock via fastboot
step 2) RUU 1.15 or 1.19 (so this means my firmware/software/hboot will be updated as well?)
From here if I stop, I will be S-ON so I can...
option 1) RUU 2.09 and stay on 3.15
option 2) unlock bootloader from HTCDev and stay S-ON
option 3) unlock bootloader from HTCDev and DirtyRacun S-OFF (which actually seems like a very simple process once unlocked)
BaconMunch said:
Thanks xlxcrossing! I messaged Captain for a a recovery flash for the baseband only and he said my approach is no good either. So seems like I have to RUU to get off 1.12 anyways since LazyPanda is not supported and DirtyRacun starts at 1.15
So I am looking at the UNLIMITED.IO site now
step 1) relock via fastboot
step 2) RUU 1.15 or 1.19 (so this means my firmware/software/hboot will be updated as well?)
From here if I stop, I will be S-ON so I can...
option 1) RUU 2.09 and stay on 3.15
option 2) unlock bootloader from HTCDev and stay S-ON
option 3) unlock bootloader from HTCDev and DirtyRacun S-OFF (which actually seems like a very simple process once unlocked)
Click to expand...
Click to collapse
My advice is get s-off it will save alot of headaches down the road
Sent from my PoS MoPho
BaconMunch said:
Thanks xlxcrossing! I messaged Captain for a a recovery flash for the baseband only and he said my approach is no good either. So seems like I have to RUU to get off 1.12 anyways since LazyPanda is not supported and DirtyRacun starts at 1.15
So I am looking at the UNLIMITED.IO site now
step 1) relock via fastboot
step 2) RUU 1.15 or 1.19 (so this means my firmware/software/hboot will be updated as well?)
From here if I stop, I will be S-ON so I can...
option 1) RUU 2.09 and stay on 3.15
option 2) unlock bootloader from HTCDev and stay S-ON
option 3) unlock bootloader from HTCDev and DirtyRacun S-OFF (which actually seems like a very simple process once unlocked)
Click to expand...
Click to collapse
Sent you a PM
The advice is free....the bandwidth, not so much
Just wanted to say thank you all for the support and advice.
I finally walked my friend over gtalk and successfully achieved S-OFF after relock, 1.15 RUU, unlock with HTC DEV, dirtyracun
Then updated full firmwares incrementally to 3.16
Then while trying to load MeanBean, realized we lost TWRP (and possibly root, need to confirm), I can only guess that went away with the RUU? That's not really documented anywhere unless that's a known thing.
TWRP installation via goomanager failed (maybe due to lack of root), I was able to find TWRP v2.3.1 bootloader, installed that and installed MeanBean 3.0.4
I think that makes us up to date, however we will likely install SuperSU via TWRP once we customize and ensure the phone is running smoothly.
Thanks again all!
Super su is included with the ROM
Sent from my EVO using xda premium
Hi all,
I have been using my Rezound running Plain Andy as a wifi only single purpose device to play Pokemon Duel. This worked fine until I tried to do a software reboot the other day, and the device wouldn't come back up. I was only able to get into fastboot and recovery.
Being less than wise, I went through a series of steps that I cannot fully recount. My first hiccup was that I could not mount /cache, etc. and every attempt to flash anything was failing. I tried going through any number of recoveries to see if any would resolve my problems. Nothing seemed to be making any difference.
Most of the old threads that I was reading were pointing to flashing an RUU. I resisted doing this for some time, but I was unable to work around it. Everything said that I had to be S-on to flash an RUU, so I relocked.
Now, I think that I made a big mistake there, because I cannot unlock with the normal process. Every attempt fails. I suspect that this might have to do with my device being in a non-standard state that the website will not generate accept a token from. Perhaps this is mistaken.
My current state is:
*** RELOCKED ***
VIGOR PVT SHIP S-OFF RL
HBOOT-2.28.0000
RADIO-2.23.10.0123r/2.23.10.0124r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Sep 20 2012,17:40:22
Recovery is PhilZ Touch 6.19.3 Clockwork Mod 6.0.4.7
I feel like I have made wrong turns at every step. If I am not mistaken, this recovery makes charging not work properly in a power-off state. Also, this HBOOT (same as mainver?) prevents me from running any available RUU. Finally, my current state does not seem to be allowing me to unlock my device again.
I hope that someone is still around who is able to help me. I saw one thread discussing using a shell into the system to modify the mainver, but the last thing I want to do is go one more step in the wrong direction before I seek help. I fear it may already be too late.
Thank you in advance for any assistance.