Related
Hey I just want to make sure of a few things before I try this... I saw the thread below but it doesn't saying anything about being able to downgrade later on. I have a Bell incS with the stock 2.3.3 version 2.28.666.3. My phone is not rooted or S-Off but I have made a gold card and was going to flash the WWE RUU 2.30.405.1 to get rid of the bloat. Is it as simple as that? Would it be possible to downgrade back to the original Bell 2.28.666.3 RUU later if I needed warranty with the gold card or not? Also any issues to worry about with debranding like radio/wifi problems or anything else? Thanks
patrick92260 said:
Hey I just want to make sure of a few things before I try this... I saw the thread below but it doesn't saying anything about being able to downgrade later on. I have a Bell incS with the stock 2.3.3 version 2.28.666.3. My phone is not rooted or S-Off but I have made a gold card and was going to flash the WWE RUU 2.30.405.1 to get rid of the bloat. Is it as simple as that? Would it be possible to downgrade back to the original Bell 2.28.666.3 RUU later if I needed warranty with the gold card or not? Also any issues to worry about with debranding like radio/wifi problems or anything else? Thanks
Click to expand...
Click to collapse
If you don't have S-OFF on your BM IncS, then you won't be able to flash the WWE 2.30.405.1 RUU because that ROM is for the S710E model (model id PG321300) and the BM Incs is a S710A model (model id PG321200) and it will fail with 'wrong model id' error.
If you go ahead and S-OFF, then you can take the WWE 2.30.405.1 RUU and extract the ROM.zip and modify the android-info.txt file in the ROM.zip to change the model id. After that process, you would copy the modified ROM.zip file to the root of your SD card and rename it PG32IMG.zip. Then boot into HBOOT and it will find the PG32IMG.zip file and ask if you want to apply the update. You will then have an unbranded, unrooted IncS. The second advantage of S-OFF is that it will allow you to reflash the BM 2.28.666.3 RUU.
I'm looking at doing the same thing. Wondering if patrick92260 has had any success. I have the Virgin IS and want to debrand it as its loaded with useless BELL apps. Will be attempting this myself, let you know how it goes.
Q: First question is, now that I have the .exe of RUU. How do I go about getting the ROM.zip file.
Figured it out on my own, but for others who are curious.
A:Windows > Run > %TEMP%
Then list by 'last modified folder' and it should be the first one there.
I decided not to debrand the phone because of the different model ID for the Canadian IncS. If you debrand the phone to a WWE RUU it most likely won't ever be able to get an OTA update because when it's tries to update the phone's model ID will still be different. If there is no RUU for that new update then you'll probably be stuck with what you have.
Maybe if the IncS ever gets an actual radio S-Off I will try it.
If you still tried to debrand it though, how did it go?
patrick92260 said:
I decided not to debrand the phone because of the different model ID for the Canadian IncS. If you debrand the phone to a WWE RUU it most likely won't ever be able to get an OTA update because when it's tries to update the phone's model ID will still be different. If there is no RUU for that new update then you'll probably be stuck with what you have.
Maybe if the IncS ever gets an actual radio S-Off I will try it.
If you still tried to debrand it though, how did it go?
Click to expand...
Click to collapse
Just a point of clarification. When I debranded my Bell IncS, I put the original WWE GB 2.12.405.7 ROM on it. I then received the OTA notification that 2.30.405.1 was available, so even though you won't get a Bell OTA, you do get the WWE unbranded OTAs.
tpbklake said:
Just a point of clarification. When I debranded my Bell IncS, I put the original WWE GB 2.12.405.7 ROM on it. I then received the OTA notification that 2.30.405.1 was available, so even though you won't get a Bell OTA, you do get the WWE unbranded OTAs.
Click to expand...
Click to collapse
Hmm maybe I'll go ahead and give it a try then. You didn't have any issues upgrading to the WWE OTA or have problems once it was debranded? I ask just because I know if you debranded the original Desire it would kill the WiFi and I think it caused reception issues.
patrick92260 said:
Hmm maybe I'll go ahead and give it a try then. You didn't have any issues upgrading to the WWE OTA or have problems once it was debranded? I ask just because I know if you debranded the original Desire it would kill the WiFi and I think it caused reception issues.
Click to expand...
Click to collapse
I have not had any issues of debranding my Bell IncS with the WWE roms.
The OTA downloaded fine, but like all OTAs, it checks to make sure you have a stock version of the previous ROM, in this case 2.12.405.7. If you have ClockworkMod installed, the OTA will fail because that isn't the stock recovery. I could have flashed the stock recovery and ran the OTA, but I choose to take the 2.30.405.1 RUU and make a rooted version of it using dsi's XDA Android kitchen and ended up flashing that.
Debranding went smoothly. Flashed the WWE just fine after editing the file.
Then went ahead and installed 4EXTRecovery and Virtuous Unity over that though.
Whether doing the debranding helped or not, I'm not sure. Either way I'm down to just essential apps in this rom, no bloatware.
As for OTA updates, who cares really. If you're on this forum, you've got enough knowledge to flash yourself and not have to wait for OTA updates to arrive.
Original Bell Incredible S rom
Any one have the OEM "stock" rom/radio/kernel from Bell in case of warranty?
I did not think about this when I flashed mine and it would be great in case the hardware fail..
everything is working perfectly fine right now so it's just a "in case" question.
neurobrake said:
Any one have the OEM "stock" rom/radio/kernel from Bell in case of warranty?
I did not think about this when I flashed mine and it would be great in case the hardware fail..
everything is working perfectly fine right now so it's just a "in case" question.
Click to expand...
Click to collapse
Yes, the shipped Bell Mobile stock Gingerbread RUU can be found here:
RUU_Vivo_Gingerbread_S_BM_2.28.666.3_Radio_20.2805 .30.085AU_3805.04.03.27_M_release_199657_signed.
http://www.filefactory.com/file/cc9d...657_signed.exe
Thanks to football for posting the shipped ROMs in the Development section.
The file is gone.
tpbklake said:
Yes, the shipped Bell Mobile stock Gingerbread RUU can be found here:
RUU_Vivo_Gingerbread_S_BM_2.28.666.3_Radio_20.2805 .30.085AU_3805.04.03.27_M_release_199657_signed.
http://www.filefactory.com/file/cc9d...657_signed.exe
Thanks to football for posting the shipped ROMs in the Development section.
Click to expand...
Click to collapse
justaway2 said:
The file is gone.
Click to expand...
Click to collapse
Use the link that is in this thread (must have been a bad copy and paste):
http://forum.xda-developers.com/showthread.php?t=1033922
I need this file
tpbklake said:
Use the link that is in this thread (must have been a bad copy and paste):
http://forum.xda-developers.com/showthread.php?t=1033922
Click to expand...
Click to collapse
I need this file. Can you please update the link? Point me to it.
digitzgal said:
I need this file. Can you please update the link? Point me to it.
Click to expand...
Click to collapse
Go to the site HTCDEV.com and you can download the final ICS RUU.
Followup question
Thanks a tonne for responding.
I''ve an HTC Incredible S, it was at Bell's stock version, RUU_Vivo_Gingerbread_S_BM_2.28.666.3_Radio_20.2805 .30.085AU_3805.04.03.27_M_release_199657_signed. I followed this guide(http://forum.xda-developers.com/showthread.php?t=2118187) to root, install recovery-clockwork-5.0.2.0-vivo.img and soff my phone. I did not install any custom images on it.
In order to unroot and install the HTC OTA update/RUU:
Can I directly run this zip from HTC site and will it work? OR do I need to follow some other procedure to downgrade my phone to the default image(v2.3) and then upgrade to v4.0 ?
I found this v4.0 for Incrediable S for NAM (Canada) listed on HTCDEV site. Nothing else v2.3 or anything for Bell is listed there.
Incredible S
HTC
NAM (Canada)
RUU
N/A
v4.0 374.4 MB
4.14.405.2
digitzgal said:
Thanks a tonne for responding.
I''ve an HTC Incredible S, it was at Bell's stock version, RUU_Vivo_Gingerbread_S_BM_2.28.666.3_Radio_20.2805 .30.085AU_3805.04.03.27_M_release_199657_signed. I followed this guide(http://forum.xda-developers.com/showthread.php?t=2118187) to root, install recovery-clockwork-5.0.2.0-vivo.img and soff my phone. I did not install any custom images on it.
In order to unroot and install the HTC OTA update/RUU:
Can I directly run this zip from HTC site and will it work? OR do I need to follow some other procedure to downgrade my phone to the default image(v2.3) and then upgrade to v4.0 ?
I found this v4.0 for Incrediable S for NAM (Canada) listed on HTCDEV site. Nothing else v2.3 or anything for Bell is listed there.
Incredible S
HTC
NAM (Canada)
RUU
N/A
v4.0 374.4 MB
4.14.405.2
Click to expand...
Click to collapse
No, if you have BlackRose S-OFF, you will not be able to flash the 4.14.405.2 RUU. There is a link in my signature that is a stock, rooted ROM based on this RUU that you can safely install. I would recommend that along with poondog's kernel that is also linked in my signature.
Followup
Thanks tpbklake,
I didn't perform Step11, to install Blackrose.
I followed, Step 1, Skipped 2. Couldn't follow Step3, since I had bootrom HBOOT 1.13.0000, I could never get the OEM identifier token. Then I directly performed Step 9 to get revolutionary soff. Then I followed Step 4,5 to install clockwork recovery and root my phone. Then I performed Step 6. That's it. No other steps or flashing of custom rom.
Can I go ahead with the 4.0 RUU from HTCDev?
digitzgal said:
Thanks tpbklake,
I didn't perform Step11, to install Blackrose.
I followed, Step 1, Skipped 2. Couldn't follow Step3, since I had bootrom HBOOT 1.13.0000, I could never get the OEM identifier token. Then I directly performed Step 9 to get revolutionary soff. Then I followed Step 4,5 to install clockwork recovery and root my phone. Then I performed Step 6. That's it. No other steps or flashing of custom rom.
Can I go ahead with the 4.0 RUU from HTCDev?
Click to expand...
Click to collapse
No. Run the blackrose tool. (Make sure you have CM7 or another rooted ROM for this). Fully run it so that now, in the bootloader, instead of Revolutionary, You should see Blackrose. Then run the tool again but this time select Uninstall Blackrose and at the end of that, you should have HBOOT 1.13.0000. Relock bootloader and then run the RUU.
Or you can just use tbpklake's stock rooted ROM. That was built off the lateset WWE RUU I believe.
072665995 said:
No. Run the blackrose tool. (Make sure you have CM7 or another rooted ROM for this). Fully run it so that now, in the bootloader, instead of Revolutionary, You should see Blackrose. Then run the tool again but this time select Uninstall Blackrose and at the end of that, you should have HBOOT 1.13.0000. Relock bootloader and then run the RUU.
Or you can just use tbpklake's stock rooted ROM. That was built off the lateset WWE RUU I believe.
Click to expand...
Click to collapse
Thanks I can't use rooted ROM for a test I am doing.
So keep following the previous guide(http://forum.xda-developers.com/showthread.php?t=2118187) to perform Steps 10,11 for flashing CM7 and Blackrose. Then re-run Blackrose utility to uninstall it. Then lock the bootloader and run RUU from htcdev. Correct?
How do I lock the bootloader again?
digitzgal said:
Thanks I can't use rooted ROM for a test I am doing.
So keep following the previous guide(http://forum.xda-developers.com/showthread.php?t=2118187) to perform Steps 10,11 for flashing CM7 and Blackrose. Then re-run Blackrose utility to uninstall it. Then lock the bootloader and run RUU from htcdev. Correct?
How do I lock the bootloader again?
Click to expand...
Click to collapse
Ok now I'm just freaking confused. What are you trying to do?? Are you trying to root?? Or what??
After an upgrade to android 2.3.5 and Sense 3.0, i decided to downgrade and s-off my phone to try custom roms.
Now i decided to go back to stock rom's. I managed to flash 2.12.405.7 Ruu and s-on my phone, but i can't manage to update my phone with OTA function.
My cid is 038 and the original firmware was 2.12.720.5. I can't find that version of ruu(if someone has it please share it).
If i create a gold card and use it to flash for example RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1 can i update by OTA to the latest version available?
Your region and your RUU must match for it to get OTA's.
If your CID hasn't changed since the start, you need to run the RUU of what you started with
markj338 said:
Your region and your RUU must match for it to get OTA's.
If your CID hasn't changed since the start, you need to run the RUU of what you started with
Click to expand...
Click to collapse
Can i change the CID number?
I can't find any 2.12.720.5 ruu version, Football seams to have it, but i can't reach him. And i will first try to find a free version
I managed to find this RUU, but i think the radio is to old, and i will like to avoid a brick. What do you think?
PG32IMG_Vivo_hTC_Asia_India_1.36.720.1_Radio_Radio_20.23.30.0802U_38.02.01.11_M_release_172022_signed.zip
uqadwe said:
I managed to find this RUU, but i think the radio is to old, and i will like to avoid a brick. What do you think?
PG32IMG_Vivo_hTC_Asia_India_1.36.720.1_Radio_Radio_20.23.30.0802U_38.02.01.11_M_release_172022_signed.zip
Click to expand...
Click to collapse
If you have a 2.x ROM then DO NOT attempt to flash that 1.X RUU. The radio is TOO OLD and you will BRICK YOUR DEVICE.
ok, thought so, but i really can't find any solution
i can see the next posibilities :
1. gold card + wwe ruu(don't know if ota update will work)
2. cid change (don't know how and if ota update will work)
3. pay for 2.12.720.5 ruu
4. find some 3.**720.* ruu (don't know where)
could you please tell me your point of view?
uqadwe said:
ok, thought so, but i really can't find any solution
i can see the next posibilities :
1. gold card + wwe ruu(don't know if ota update will work)
2. cid change (don't know how and if ota update will work)
3. pay for 2.12.720.5 ruu
4. find some 3.**720.* ruu (don't know where)
could you please tell me your point of view?
Click to expand...
Click to collapse
Make a goldcard and flash the 3.11.405.x WWE RUU.
i made the gold card, everything works, i am now on 3.11.405.2.
Is it normal, that the first row in the bootloader is ***LOCKED*** or
is this one of the downsides of downgrading and restocking.
I don't remember if it was originally here.
Another questions is, when the ICS OTA will be here, can i update
by OTA
uqadwe said:
i made the gold card, everything works, i am now on 3.11.405.2.
Is it normal, that the first row in the bootloader is ***LOCKED*** or
is this one of the downsides of downgrading and restocking.
I don't remember if it was originally here.
Another questions is, when the ICS OTA will be here, can i update
by OTA
Click to expand...
Click to collapse
Yeah this is normal. I'm not sure if the ICS update will come as an OTA, but as long as the bootloader is locked you should be fine installing any official updates.
I've currently got Android Revolution HD 12.1 installed, however I need to return the phone to Vodafone UK Stock, due to returning the phone.
I found this link, which seems to give instructions on restoring the HTC ONE, however apart from downloading the OTA_M7_UL_JB_50_Vodafone_UK.......zip file from here, I'm really not sure which method to follow.
This is the information I have from the Software Information on my phone:
Android version: 4.2.2
Kernel version: 3.4.10-g445d072
Baseband version: 4A.14.3250.13_10.33.1150.01L
Build number: 2.24.401.1.CL211355
I would really appreciate some assistance
robot1000 said:
I've currently got Android Revolution HD 12.1 installed, however I need to return the phone to Vodafone UK Stock, due to returning the phone.
I found this link, which seems to give instructions on restoring the HTC ONE, however apart from downloading the OTA_M7_UL_JB_50_Vodafone_UK.......zip file from here, I'm really not sure which method to follow.
This is the information I have from the Software Information on my phone:
Android version: 4.2.2
Kernel version: 3.4.10-g445d072
Baseband version: 4A.14.3250.13_10.33.1150.01L
Build number: 2.24.401.1.CL211355
I would really appreciate some assistance
Click to expand...
Click to collapse
Here is a link to all RUU`s, zips and CWM/TWRP recovery rom`s http://forum.xda-developers.com/showthread.php?t=2207874. You`ll need S-Off however to downgrade the Hboot. If you`re not S-Off you cannot Flasha RUU with a older Hboot. Guess you`re on HBoot 1.54.000 now. Till the revone devs find a way to modify the S-Off exploit you`re stuck, link http://forum.xda-developers.com/showthread.php?t=2314582.
gee2012 said:
Here is a link to all RUU`s, zips and CWM/TWRP recovery rom`s http://forum.xda-developers.com/showthread.php?t=2207874. You`ll need S-Off however to downgrade the Hboot. If you`re not S-Off you cannot Flasha RUU with a older Hboot. Guess you`re on HBoot 1.54.000 now. Till the revone devs find a way to modify the S-Off exploit you`re stuck, link http://forum.xda-developers.com/showthread.php?t=2314582.
Click to expand...
Click to collapse
Thanks for responding
I've already downloaded the OTA's: Vodafone UK file from that link, however I'm really not sure what I should be doing with it
Edit
Just curious, if my phone is S-ON, how have I been able to install a custom ROM and recovery?
robot1000 said:
Thanks for responding
I've already downloaded the OTA's: Vodafone UK file from that link, however I'm really not sure what I should be doing with it
Edit
Just curious, if my phone is S-ON, how have I been able to install a custom ROM and recovery?
Click to expand...
Click to collapse
If the bootloader is unlocked but you`re S-On you can flash a custom recovery and roms, you however cannot downgrade or flash a newer Hboot afaik. You can`t do anything with the OTA atm, not even flash a Vodafone CWM recovery i`am afraid.
gee2012 said:
If the bootloader is unlocked but you`re S-On you can flash a custom recovery and roms, you however cannot downgrade or flash a newer Hboot afaik.
Click to expand...
Click to collapse
With regards to the Vodafone zip file, is it possible to flash that somehow and give the impression that's in factory state?
robot1000 said:
With regards to the Vodafone zip file, is it possible to flash that somehow and give the impression that's in factory state?
Click to expand...
Click to collapse
No mate, you don`t have a Vodafone rom, you have a custom recovery and you would need to lock the bootloader. It is not possible atm, stick with the rom you`re on for now and do not lock bootloader. Wait for revone to modify the bootloader xploit to get S-Off.
gee2012 said:
No mate, you don`t have a Vodafone rom, you have a custom recovery and you would need to lock the bootloader. It is not possible atm, stick with the rom you`re on for now and do not lock bootloader. Wait for revone to modify the bootloader xploit to get S-Off.
Click to expand...
Click to collapse
I've just gone into Bootloader and it's showing Hboot as 1.44.0000 !!
Would you mind giving me a brief outline on what I should be doing to get my phone back to vodafone stock?y
Many Thanks
Would flashing the Vodafone OTA zip file in recovery be safe or do I need to S-Off the device?
Please can someone advise
Thanks
Wow, you have quite the adventure in front of you my friend if you want to return your phone to a pure stock state. I'll outline the steps and you can do some work and find the guides to complete them. Assuming you're on hboot 1.44 you'll need to go ahead and s-off, you can then remove the tampered flag. After you're s-off you're then going to need to double check you're using a stock unmodified hboot (you should be) and flash the pertinent RUU based on your phone - there are plenty of guides on how to select this. You'll then need to s-on again, google the command "fastboot oem writesecureflag 3" to find some information on how to do that.
Basically you've got your work cut out mate, sorry I can't be more help but the process I've mentioned aren't as simple or as safe as unlocking the bootloader. You'll need to put some effort and most importantly care as any one of them can brick your phone. Once you're s-off you've opened up very sensitive partitions which if changed or written to wrongly can instantly brick your phone. As such I'd do a lot of research before you undertake any of these steps, this is just off the top of my head to give you some guidance so I'd also check them, you really can't be too careful when playing around with £500 worth of tech. Good luck!
postfatal said:
Wow, you have quite the adventure in front of you my friend if you want to return your phone to a pure stock state. I'll outline the steps and you can do some work and find the guides to complete them. Assuming you're on hboot 1.44 you'll need to go ahead and s-off, you can then remove the tampered flag. After you're s-off you're then going to need to double check you're using a stock unmodified hboot (you should be) and flash the pertinent RUU based on your phone - there are plenty of guides on how to select this. You'll then need to s-on again, google the command "fastboot oem writesecureflag 3" to find some information on how to do that.
Basically you've got your work cut out mate, sorry I can't be more help but the process I've mentioned aren't as simple or as safe as unlocking the bootloader. You'll need to put some effort and most importantly care as any one of them can brick your phone. Once you're s-off you've opened up very sensitive partitions which if changed or written to wrongly can instantly brick your phone. As such I'd do a lot of research before you undertake any of these steps, this is just off the top of my head to give you some guidance so I'd also check them, you really can't be too careful when playing around with £500 worth of tech. Good luck!
Click to expand...
Click to collapse
Thanks for you response
I'm now S-Off, however what I can't get my head around is the RUU part. The Vodafone ROM that I require seems to be an OTA zip update, however I'm unsure on how to flash this as it doesn't seem to be RUU
robot1000 said:
Thanks for you response
I'm now S-Off, however what I can't get my head around is the RUU part. The Vodafone ROM that I require seems to be an OTA zip update, however I'm unsure on how to flash this as it doesn't seem to be RUU
Click to expand...
Click to collapse
You cannot do it with an OTA zip... you need a full RUU but unfortunately there doesn't seem to be one available for Vodafone UK.
This one seems to be the closest one for you.... it's stock HTC Europe. I don't think at this time that returning to stock Vodafone is a possibility.
If you're sending it back for repair or replacement you could take a chance on sending it as it is.
postfatal said:
Wow, you have quite the adventure in front of you my friend if you want to return your phone to a pure stock state. I'll outline the steps and you can do some work and find the guides to complete them. Assuming you're on hboot 1.44 you'll need to go ahead and s-off, you can then remove the tampered flag. After you're s-off you're then going to need to double check you're using a stock unmodified hboot (you should be) and flash the pertinent RUU based on your phone - there are plenty of guides on how to select this. You'll then need to s-on again, google the command "fastboot oem writesecureflag 3" to find some information on how to do that.
Basically you've got your work cut out mate, sorry I can't be more help but the process I've mentioned aren't as simple or as safe as unlocking the bootloader. You'll need to put some effort and most importantly care as any one of them can brick your phone. Once you're s-off you've opened up very sensitive partitions which if changed or written to wrongly can instantly brick your phone. As such I'd do a lot of research before you undertake any of these steps, this is just off the top of my head to give you some guidance so I'd also check them, you really can't be too careful when playing around with £500 worth of tech. Good luck!
Click to expand...
Click to collapse
rider5512 said:
You cannot do it with an OTA zip... you need a full RUU but unfortunately there doesn't seem to be one available for Vodafone UK.
This one seems to be the closest one for you.... it's stock HTC Europe. I don't think at this time that returning to stock Vodafone is a possibility.
If you're sending it back for repair or replacement you could take a chance on sending it as it is.
Click to expand...
Click to collapse
Thank you for replying.
I've run that RUU from the link you provided and it stated that it's updating from 1.29.161.11 to 1.28.401.7, however an Error [131] message appeared stating 'Customer ID Error'.
Any ideas?
robot1000 said:
Thank you for replying.
I've run that RUU from the link you provided and it stated that it's updating from 1.29.161.11 to 1.28.401.7, however an Error [131] message appeared stating 'Customer ID Error'.
Any ideas?
Click to expand...
Click to collapse
Ok... you need to change that ID in the phone.
Reboot the phone to bootloader then fastboot and connect to pc then from your ADB directory on PC issue the command "fastboot oem writecid HTC__001" this will then give you the right ID for the RUU.
Note it's HTC__001.... 2 underscores !
Hey gals,
I want to ask a noobish question:
I'v done S-OFF to my US Developer Edition device.
Hboot now 1.44
android 4.1.2
I'd like to know, if i would like to flash ViperOne rom that have 4.2.2 base, do i need to update the hboot or someting else?
Thanks
oksagi said:
Hey gals,
I want to ask a noobish question:
I'v done S-OFF to my US Developer Edition device.
Hboot now 1.44
android 4.1.2
I'd like to know, if i would like to flash ViperOne rom that have 4.2.2 base, do i need to update the hboot or someting else?
Thanks
Click to expand...
Click to collapse
You Can update Hboot boot via a firmware update (which I recommend if you are still on the original 4.12 firmware, as there have been some touch driver updates that really helped the capacitive buttons, look here for a great guide and firmware packages: http://forum.xda-developers.com/showthread.php?t=2316726 ), but you don't Have to update Hboot to flash Viper 2.1, it will work fine either way
dgtiii said:
You Can update Hboot boot via a firmware update (which I recommend if you are still on the original 4.12 firmware, as there have been some touch driver updates that really helped the capacitive buttons, look here for a great guide and firmware packages: http://forum.xda-developers.com/showthread.php?t=2316726 ), but you don't Have to update Hboot not flash Viper 2.1, it will work fine either way
Click to expand...
Click to collapse
Thanks for reply,
As i know there is no new HBOOT for DEVELOPER EDITION. maybe i'm wrong?
Or i need just to take a latest HBOOT and flash it?
Will i still have S-OFF?
oksagi said:
Thanks for reply,
As i know there is no new HBOOT for DEVELOPER EDITION. maybe i'm wrong?
Or i need just to take a latest HBOOT and flash it?
Will i still have S-OFF?
Click to expand...
Click to collapse
It would be a good idea to update your firmware/Hboot to the 2.24 (4.22) version, so it matches the rom and you get the touch fixes I talked about. It's a good idea, but you do not have to, it's up to you. Hboot will change to 1.54, but you will stay S-off, no worries. Read that thread I linked, and I recommend this firmware https://mega.co.nz/#!nZoVXKpD!Iki5KkvxxhL9jZgJkegv_iHLbp0eHQALxAz5Nc50_rc from that thread if that's what you want to do. If that's the route you go, first update the firmware/Hboot, then flash the rom, then any custom kernels if desired
dgtiii said:
It would be a good idea to update your firmware/Hboot to the 2.24 (4.22) version, so it matches the rom and you get the touch fixes I talked about. It's a good idea, but you do not have to, it's up to you. Hboot will change to 1.54, but you will stay S-off, no worries. Read that thread I linked, and I recommend this firmware https://mega.co.nz/#!nZoVXKpD!Iki5KkvxxhL9jZgJkegv_iHLbp0eHQALxAz5Nc50_rc from that thread if that's what you want to do. If that's the route you go, first update the firmware/Hboot, then flash the rom, then any custom kernels if desired
Click to expand...
Click to collapse
is this firmware good for developer edition?
oksagi said:
is this firmware good for developer edition?
Click to expand...
Click to collapse
Yes! It is fine, and your phone will work better with the new touch drivers. I am not sure what the CID of the Developer's edition is, you might want to check that. Will definitely flash if Super CID (fastboot oem writecid 11111111), worked for me.
Look, before you flash firmware, you better read that guide I linked you to at the very least, I mean it. This is pretty routine, non-scary stuff, but you are S-off, and that means something. Read the thread, make sure you understand what you're doing, and I'm here to help. But I'm not trying to or going to convince you to do anything, read and decide for yourself, ok? I'm telling you it will work, but you have to decide and be comfortable
dgtiii said:
Yes! It is fine, and your phone will work better with the new touch drivers. I am not sure what the CID of the Developer's edition is, you might want to check that. Will definitely flash if Super CID (fastboot oem writecid 11111111), worked for me.
Look, before you flash firmware, you better read that guide I linked you to at the very least, I mean it. This is pretty routine, non-scary stuff, but you are S-off, and that means something. Read the thread, make sure you understand what you're doing, and I'm here to help. But I'm not trying to or going to convince you to do anything, read and decide for yourself, ok? I'm telling you it will work, but you have to decide and be comfortable
Click to expand...
Click to collapse
do i need to upgrade only HBOOT or the firmware too?
oksagi said:
do i need to upgrade only HBOOT or the firmware too?
Click to expand...
Click to collapse
You don't "need" to update Hboot at all, but it will update to 1.54 with the firmware update. In my opinion, you " want" to update the firmware to: get the new, much improved touch drivers, be on the same firmware as your rom (ViperOne 2.1), and get whatever other updates are in the new firmware
oksagi said:
Hey gals,
I want to ask a noobish question:
I'v done S-OFF to my US Developer Edition device.
Hboot now 1.44
android 4.1.2
I'd like to know, if i would like to flash ViperOne rom that have 4.2.2 base, do i need to update the hboot or someting else?
Thanks
Click to expand...
Click to collapse
ViperOne will run just fine on the stock US Dev Ed firmware!
You do not NEED to upgrade the firmware, unless you want the updated touch screen drivers.
guyd said:
ViperOne will run just fine on the stock US Dev Ed firmware!
You do not NEED to upgrade the firmware, unless you want the updated touch screen drivers.
Click to expand...
Click to collapse
Can you please explain what is the problem with touch s on old hboot?
oksagi said:
Can you please explain what is the problem with touch s on old hboot?
Click to expand...
Click to collapse
The H-Boot has nothing to do with the touch screen.
The touch screen drivers were updated in the 2.17 and 2.24 firmware release.
Many people feel that the touch screen is more responsive with the updated drivers/firmware.
You do not NEED to update the firmware to run a 4.2.2 ROM. It will run fine on the older firmware.
I ran ViperOne on the older firmware up until very recently. No problems.
oksagi said:
Can you please explain what is the problem with touch s on old hboot?
Click to expand...
Click to collapse
Oksagi,
I told you yesterday, you don't Need to flash anything to run Viper, I thought that was clear, your Hboot is fine. If you Want to update your firmware, I gave you links to a very good guide, and to the firmware you should use, IF YOU WANT. Again, you are fine on your Hboot, go ahead and flash Viper, I think you will love it, I do. I think updating firmware may be too much for you at this point. Good luck sir....
Sorry For my newbie-ness but what advantages has S-OFF and what can i do with it ?
Hello all I am a noob getting into the game, I am trying to get my m7 to update with no luck. I have an AT&T branded One running on versio 1.26.502.15 . I have tried all the little tricks to get it to find them, but nadda. I have been reading into all the resets, RUUs, and OTAs and honestly I'm just more confused. From what I read about manually installing OTAs, I haven't been able to find the right one to upgrade my version. I just want to get up to date with Android and Sense. If anybody could just point me in the right direction I would be so thankful. If there's any other info needed I'll get it up here.
Locked
S_on
Hboot 1.44
Android v.1.26.502.15
Sense 5.0
dirtrider129 said:
Hello all I am a noob getting into the game, I am trying to get my m7 to update with no luck. I have an AT&T branded One running on versio 1.26.502.15 . I have tried all the little tricks to get it to find them, but nadda. I have been reading into all the resets, RUUs, and OTAs and honestly I'm just more confused. From what I read about manually installing OTAs, I haven't been able to find the right one to upgrade my version. I just want to get up to date with Android and Sense. If anybody could just point me in the right direction I would be so thankful. If there's any other info needed I'll get it up here.
Locked
S_on
Hboot 1.44
Android v.1.26.502.15
Sense 5.0
Click to expand...
Click to collapse
do you have adb and fastboot installed on your computer? If yes, post the output of fastboot getvar all except the imei # and the serialno #
at&t phone must be connected to the at&t network to receive ota update, are you on at&t?
manually installing ota update require s-off, your phone is currently s-on. good new is its "pretty easy" to s-off on hboot 1.44, ok maybe not that easy for a new user but you should be able to s-off if you need to by following revone s-off guide.
if you are not on at&t network:
easiest solution (imo):
unlock the bootloader (this void warranty)
flash twrp recovery 2.6.3.3
flash the guru reset rom 5.12.502.2
or
more complicated but better (imo):
unlock bootloader
flash twrp recovery 2.6.3.3
root
s-off using revone
flash the latest ruu (4.18.502.7)
manually flash ota updates from 4.18.502.7 to 5.12.502.2
update issue
Thank you for the info I don't have adb fastboot installed guess I'll need to start there, I am using the new cricket gsm network which if I'm correct uses AT&T towers but I guess that's why I was unable to get the updates because I'm not actually on AT&T. Will I still need to get s-off with the first solution or not ? Thanks again for the help, I'll get on it and let you know how it goes.
dirtrider129 said:
Thank you for the info I don't have adb fastboot installed guess I'll need to start there, I am using the new cricket gsm network which if I'm correct uses AT&T towers but I guess that's why I was unable to get the updates because I'm not actually on AT&T. Will I still need to get s-off with the first solution or not ? Thanks again for the help, I'll get on it and let you know how it goes.
Click to expand...
Click to collapse
alray said:
do you have adb and fastboot installed on your computer? If yes, post the output of fastboot getvar all except the imei # and the serialno #
at&t phone must be connected to the at&t network to receive ota update, are you on at&t?
manually installing ota update require s-off, your phone is currently s-on. good new is its "pretty easy" to s-off on hboot 1.44, ok maybe not that easy for a new user but you should be able to s-off if you need to by following revone s-off guide.
if you are not on at&t network:
easiest solution (imo):
unlock the bootloader (this void warranty)
flash twrp recovery 2.6.3.3
flash the guru reset rom 5.12.502.2
or
more complicated but better (imo):
unlock bootloader
flash twrp recovery 2.6.3.3
root
s-off using revone
flash the latest ruu (4.18.502.7)
manually flash ota updates from 4.18.502.7 to 5.12.502.2
Click to expand...
Click to collapse
Could you tell me where to find the 5.12.502.2 reset Rom, I went to HTC guru and could not find it in the list, also what are your thoughts on the twrp 2.7, I read a few comments about it and seemed like people were having trouble with it on their One's, I wondered if it would be better to have the new version or if I should just stick with the other one. Thanks again for the help.
dirtrider129 said:
Could you tell me where to find the 5.12.502.2 reset Rom, I went to HTC guru and could not find it in the list, also what are your thoughts on the twrp 2.7, I read a few comments about it and seemed like people were having trouble with it on their One's, I wondered if it would be better to have the new version or if I should just stick with the other one. Thanks again for the help.
Click to expand...
Click to collapse
http://www.htc1guru.com/dld/guru_reset_m7_5-12-502-2_clsa-zip/
better to stick with 2.6.3.3 or 2.6.3.4 unless you want to experiment. there is a charging bug with 2.7.0.0 and it looks like there are also some other bugs with 2.7.1.0 for flashing roms, not sure if it was solved in 2.7.1.1. use 2.6.3.3 or .3.4 and youll be fine.
and no, you dont need s-off to use the reset rom. but a reset rom will not update all the firmware, you'll get an updated rom(software), on the hardware side, only recovery and radio will be updated (if you choose to flash stock radio and recovery at the reset rom installation). hboot will not be updated using this solution.
do a nandroid backup of your current config, just in case you need to restore if something goes wrong.
update question
[/Quote]better to stick with 2.6.3.3 or 2.6.3.4 unless you want to experiment. there is a charging bug with 2.7.0.0 and it looks like there are also some other bugs with 2.7.1.0 for flashing roms, not sure if it was solved in 2.7.1.1. use 2.6.3.3 or .3.4 and youll be fine.
and no, you dont need s-off to use the reset rom. but a reset rom will not update all the firmware, you'll get an updated rom(software), on the hardware side, only recovery and radio will be updated (if you choose to flash stock radio and recovery at the reset rom installation). hboot will not be updated using this solution.
do a nandroid backup of your current config, just in case you need to restore if something goes wrong.[/QUOTE]
After lots and lots of research into this before doing I've decided to go with viperone custom Rom, if I understand it right I won't have to mess with s-off for this,please correct me if I'm wrong. But I have found some conflicting instructions, I read somewhere that I will have to copy the boot.img from the Rom and flash it before flashing the Rom then others without that step, so I'm confused, I wanna male sure I do this right the first time. Also are there any files that I need to have updated before flashing a 4.4 sense 6 custom Rom or will it all be included in the Rom?
Thank you
Dirtrider
Hi there
Been a long time since I've posted and hope I'm in the right place. Did a search for my question and wound up here.
My phone is stock and s-on, I haven't done anything to it, it's exactly the same as when it came out the box, but I haven't been able to update the software in settings>about>software updates for a while now, it just keeps coming back with download unsuccessful. Any ideas how I can sort this, or do it another way?
Thanks in advance
Sent from my HTC One using XDA Free mobile app