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 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?
Hi, I have been reading all sorts of threads for hours trying work out the correct way to root the Evo 3D I just got. Every single guide and tutorial is about unlocking the bootloader and rooting etc with S-on to make it S-off. Mine is already S-off and I cant work out what's next.
This is a new phone I got from ebay but I believe they network unlocked it first or something. In its current state:
*** LOCKED ***
SHOOTER_U PVT SHIP S-OFF RL
HBOOT-1.53.0007
eMMC-boot
It is GSM
It is unrooted
When I try to go to recovery it just shows a picture of the phone with a red "!" on it and I have to pull the battery.
What do I need to do to root it? I have read that once its S-off you shouldn't need to unlock the bootloader or anything ever again, but every root guide starts with unlocking the bootloader...
Also is there a custom rom that's best to use, where everything (including 3D) works? I assume development has stopped for this device, is there a particular rom thats ideal?
Thanks! I have always had samsung devices so all this s-off stuff and locked bootloaders is new to me...
ivant said:
Hi, I have been reading all sorts of threads for hours trying work out the correct way to root the Evo 3D I just got. Every single guide and tutorial is about unlocking the bootloader and rooting etc with S-on to make it S-off. Mine is already S-off and I cant work out what's next.
This is a new phone I got from ebay but I believe they network unlocked it first or something. In its current state:
*** LOCKED ***
SHOOTER_U PVT SHIP S-OFF RL
HBOOT-1.53.0007
eMMC-boot
It is GSM
It is unrooted
When I try to go to recovery it just shows a picture of the phone with a red "!" on it and I have to pull the battery.
What do I need to do to root it? I have read that once its S-off you shouldn't need to unlock the bootloader or anything ever again, but every root guide starts with unlocking the bootloader...
Also is there a custom rom that's best to use, where everything (including 3D) works? I assume development has stopped for this device, is there a particular rom thats ideal?
Thanks! I have always had samsung devices so all this s-off stuff and locked bootloaders is new to me...
Click to expand...
Click to collapse
You need custom recovery. My recomendation is 4ext. After you flash recovery you might want to downgrade your hboot to 1.49.0007 so you can flash any ROM out there. If you want fully working ROM (with 3d) just flash any Sense 3.6 ROM, they all work fine.
I was migrating from an older HTC LTE to a different one due to a cracked screen. I tried to use one nandroid from one to the other.. This failed. I believe it was due to partition sizes being different (that is guess based on what is coming).
Since then I have tried many different RUUs each fail to finish with a 159 error.
Here are the RUUs I have tried:
Code:
RUU_JEWEL_CL_ICS_40_Sprint_WWE_1.12.651.2_Radio_1.02.11.0423_2_NV_SPCS_2.28_003_release_257970_signed.exe
RUU_JEWEL_CL_ICS_40_Sprint_WWE_1.13.651.1_Radio_1.02.12.0427_NV_SPCS_2.28_003_release_259183_signed.exe
RUU_JEWEL_CL_ICS_40_Sprint_WWE_1.22.651.3_Radio_1.05.11.0606_NV_SPCS_2.45_003_release_268323_signed.exe
RUU_JEWEL_CL_JB43_SENSE50_MR_Sprint_WWE_4.13.651.4_Rƒ?Ýigned_one_step.exe
RUU_JEWEL_CL_JB_45_S_Sprint_WWE_3.17.651.9_R_Radio_1.13.11.0830_NV_3.02_003_PRL25007_release_393631_signed.exe
Manually I can fastboot and flash the boot image.
Trying to flash system gives me an error about the img being too big.
Is there any way to force the partitions to resize? Or what are the next steps?
Here are my current versions:
***Tampered***
***UNLOCKED***
JEWEL PVT SHIP S-ON RL
HBOOT-1.15.000
RADIO-1.05.11.0606
OpenDSP-v25.1.0.32.0405
eMMC-boot
Jun 18,2012,17:05:37
Thanks in advance. At this point I just want to get a out of the box rom to load so the phone can boot. Do not even care about root or anything other than booting a rom.
Rick
Since you are s-on you need to re-lock your bootloader.
I assume you mean I need to unlock (S-OFF) the phone? I am not sure why to flash a RUU? Or are you suggesting something else?
Crazy, strange that I never knew that you had to be S-ON to flash an RUU. Seems like a stupid requirement. It is flashing now, getting much farther, so I guess it should work this time.
Thanks for the heads up!
Rick
rfryar said:
Crazy, strange that I never knew that you had to be S-ON to flash an RUU. Seems like a stupid requirement. It is flashing now, getting much farther, so I guess it should work this time.
Thanks for the heads up!
Rick
Click to expand...
Click to collapse
You don't have to be s-on to flash an RUU but you do have to re-lock the bootloader.
How can I get my hboot to 2.10 to work with windroid? Have no root boot loader loocked on a HTC evo 4g lte. Just learning how to do all this hope to root my m8 later on
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.