Develop Bugs

[Q] stock update S-OFF phone

I've used the search but frankly, the vBulletin search still sucks after all these years.
I rooted the phone following this guide. Now my phone says a system update is available.
Since I would like to install it (my phone is still 1.34, I think. The latest version should be 1.72, right?) and installing a stock update onto a S-OFF phone is highly inadvisable (I've read), how do I go about this?
I have Visionary installed but it says the phone does not appear rooted, even though it is (just checked).
I'm sure there have been others with similar questions and I just couldn't find the right thread. If so, please point me in the right direction.
Regards and thank you,

Kokuyo said:
I've used the search but frankly, the vBulletin search still sucks after all these years.
I rooted the phone following this guide. Now my phone says a system update is available.
Since I would like to install it (my phone is still 1.34, I think. The latest version should be 1.72, right?) and installing a stock update onto a S-OFF phone is highly inadvisable (I've read), how do I go about this?
I have Visionary installed but it says the phone does not appear rooted, even though it is (just checked).
I'm sure there have been others with similar questions and I just couldn't find the right thread. If so, please point me in the right direction.
Regards and thank you,
Click to expand...
Click to collapse
Why did you root your phone? There is no need to update your phone to the latest OTA update if you are wanting to install custom ROMs.

Because I was testing custom mods and wanted to go back to stock?

Kokuyo said:
Because I was testing custom mods and wanted to go back to stock?
Click to expand...
Click to collapse
ahhh, I thought you had just rooted it. I updated the day after I received my new phone. I had problems with bluetooth (music wouldn't resume after ending phone calls) and wound up here on the XDA forums looking for answers. I ended up rooting my phone, installing CM6 and now CM7 and never looked back. There is no bluetooth switching problems using CM builds so I'm happy.

Found this:
http://www.thinkthinkdo.com/trac/project1/wiki/back_to_stock

Thanks, that looks interesting. Now the only question: Do I need my original CID? And if so, how do I find it now that the CID has been changed by gfree?

That link is about a procedure to restore the stock G2 ROM. Since you seem to have a DZ ROM, I'm not sure if you want to flash a G2 ROM (though the other bits might be useful).
The 1.72 OTA update has been rootable for some time now, so you can safely accept the update if you want. But it might be easier just to flash the 1.72 ROM in its entireity (you can get it from the dev forum).
With SuperCID and S-OFF you should have no problems flashing 1.72.

steviewevie said:
With SuperCID and S-OFF you should have no problems flashing 1.72.
Click to expand...
Click to collapse
Really? Then I don't quite understand the stickied warning thread that says to never, ever attempt that.
Anyhow, I gave the Virtuous mod another go. Since it has sense and 1.72 I'm thinking of testing this one out a bit more, before I go flashing stock.
Thanks for the replies, though.

[Q] Desire Z first time root questions, please help

Hi, I am have just got my HTC Desire Z/Vision and I am very new to rooting.
I checked on a lot of thread on how to root, s-off the phone before I can install custom ROM.
Some of the tread mention that I need to do firmware downgrade if my device has firmware version higher than 1.34, but I am not sure on my version and therefore I include my information below.
What is the easier way to root my phone?
If I use gfree, do I need to downgrade my firmware? Is there any side effect when I downgrade my firmware?
If I use VISIONary, do I need to downgrade my firmware?
Do I need to do S-Off in order to install custom ROM? or is rooting enough?
Hell a lot of question but I hope you guys can help me out with it.
Android version: 2.2.1
Baseband version: 12.28e.60.140fU_26.04.02.17_M2
Kernel version: 2.6.32.21-g6e170e7
Build number: 1.82.707.1 CL317545
Software number: 1.82.707.1

cruxiality said:
Hi, I am have just got my HTC Desire Z/Vision and I am very new to rooting.
I checked on a lot of thread on how to root, s-off the phone before I can install custom ROM.
Some of the tread mention that I need to do firmware downgrade if my device has firmware version higher than 1.34, but I am not sure on my version and therefore I include my information below.
What is the easier way to root my phone?
If I use gfree, do I need to downgrade my firmware? Is there any side effect when I downgrade my firmware?
If I use VISIONary, do I need to downgrade my firmware?
Do I need to do S-Off in order to install custom ROM? or is rooting enough?
Hell a lot of question but I hope you guys can help me out with it.
Android version: 2.2.1
Baseband version: 12.28e.60.140fU_26.04.02.17_M2
Kernel version: 2.6.32.21-g6e170e7
Build number: 1.82.707.1 CL317545
Software number: 1.82.707.1
Click to expand...
Click to collapse
First, welcome to the boards, it's always nice to welcome people into the world of rooting and flashing (the android kind!).
To start, you will have to get ADB installed and working. To do this, download the Android SDK from here: http://developer.android.com/sdk/index.html . make sure you have the Java SDK and JDK installed as well as the Android SDK requires that as a requirement.
Based on your information, you have the 1.82 system software and will need to downgrade. I am not 100% sure if this guide will be applicable to you since it was written for the 1.72, but look at this guide here: http://forum.xda-developers.com/showthread.php?t=905261
The above guide will help you in downgrading to 1.34, gaining root with gfree/rage, SIM-Unlock and S-OFF, installing ClockWordMod (a.k.a CWM) and flashing a new and shiny ROM for you.
I can completely understand how confusing alot of these guides can be, I spent about 3 hours trying to do the same thing as you a month ago. A year ago, I did the same thing with my old HTC Hero! So if you have any questions, just ask away. XDA is a great community.
Have fun

Thank you for your reply. It does help me to go through the right direction.
Understood that I need to downgrade my build to 1.34, but is there any major difference between my current build and the older build?
After following the guide to downgrade and install CWM, will it also allow me to backup my current official ROM?
As I love HTC Sense too much such a pity that I need to let it go. I am thinking of flashing back to the official ROM when I have the need to.
XDA is indeed to a great community. Great helps from great people

cruxiality said:
Thank you for your reply. It does help me to go through the right direction.
Understood that I need to downgrade my build to 1.34, but is there any major difference between my current build and the older build?
After following the guide to downgrade and install CWM, will it also allow me to backup my current official ROM?
As I love HTC Sense too much such a pity that I need to let it go. I am thinking of flashing back to the official ROM when I have the need to.
XDA is indeed to a great community. Great helps from great people
Click to expand...
Click to collapse
There are alot of fixes and improvements that HTC made between the 1.34 version and the newest 1.84 version. Those would be found with HTC in their changelogs. Also, each of these upgrades breaks the root access that the devs have created. Similar to that of iOS breaking each jailbreak method with each new version of iOS that is released (you will understand this analogy if you have an iPod Touch or something along those lines).
After gaining root, SIM-Unlock and S-OFF, installing CWM would allow you to perform a NANDroid backup (an EXACT image of your current installed ROM) so that you can go back to it at a later time.
If you are like myself (and seems that you are) you love how HTC's Sense overlay works and it just gets you. Keeps things simple while being infinitely customizable. When you do get around to flashing, I would recommend Virtuous as your ROM of choice. It is what I am running right now with no ill effects. The link to Virtuous is in my signature below.
If this is your first time flashing a custom ROM on an Android device, I can promise you that you will NEVER have a reason to go back to the stock ROM unless your phone is damaged physically and needs warranty repair. Even then, it is sometimes cheaper and easier for you to order the parts online and DIY your repairs (did it for my brother's BB Storm when he broke the screen).
Going back to my Hero, I have the stock Android 1.5 image saved somewhere, but I have never had to go back to it. Always found another newer/better custom ROM to flash. With my current DZ, I was fortunate enough to have stumbled onto Virtuous.
Have fun!

Yes, you're right. I like HTC Sense so I don't know if I will get used to the custom ROM without it.
I have checked on the Virtuous ROM previously and I will give it a try.
Yes, I saw plenty of decent ROM, they have nice UI but as you know first time rooting does give me goosebumps.
Will try it and I hope everything goes smooth.
Thanks a lot for your kind explanation, it does save me time in putting up all the pieces together

I bumped into a problem as I try to downgrade my firmware.
I followed the guide on this thread http://forum.xda-developers.com/showthread.php?t=905261 and I encountered error on step 11, when the phone goes into bootloader mode and tries to scan PC10IMG.zip file that I copied into the SDCard.
It said 'CID' incorrect!, Update Fail!
Anybody knows why I might have this issue? Is this because of the firmware difference as mentioned by Athrun88?

cruxiality said:
I bumped into a problem as I try to downgrade my firmware.
I followed the guide on this thread http://forum.xda-developers.com/showthread.php?t=905261 and I encountered error on step 11, when the phone goes into bootloader mode and tries to scan PC10IMG.zip file that I copied into the SDCard.
It said 'CID' incorrect!, Update Fail!
Anybody knows why I might have this issue? Is this because of the firmware difference as mentioned by Athrun88?
Click to expand...
Click to collapse
As stated in the thread you are using to downgrade, your CID must be one of the following:
g4rb4g3 said:
If your INFOCID is NOT one of these you need to make a goldcard to downgrade!
HTC__001
HTC__032
HTC__E11
HTC__203
HTC__Y13
HTC__102
HTC__405
HTC__304
HTC__A07
HTC__N34
HTC__J15
Click to expand...
Click to collapse
IF its not in the above list you must make a gold card first then use the thread that you listed to downgrade. To check your CID run the following commands:
check with:
Code:
adb reboot bootloader
fastboot oem boot
Click to expand...
Click to collapse
There is a link in the thread you listed on how to make a gold card. The method you are trying is comfirmed to also work with 1.82. So the reason you are having problems is NOT because your on 1.82 firmware, more than likely your CID is not listed above. Solution = GOLDCARD.

Thank you for the reply.
I have looked into the Goldcard method (http://forum.xda-developers.com/showthread.php?t=832503) and actually spent my time trying to accomplish the result.
Part 1 and part 2 are pretty straightforward but now I bumped into another problem when I tried to do part 3 as it requires me to have root access to execute the command.
I have tried to get the root access by following methods from different threads such as using rage (http://forum.xda-developers.com/showthread.php?t=834228).
For this method, I tried to do temp root and I am stucked on step 5. After launching 'Terminal Emulator' and running 'rage'. I can't seem to run the 'Terminal Emulator' again. When I launched it, it Force Closes. Tried to launch it again, my phone just displayed black screen and keys doesn't seem to be responding not till I off and on the phone (not reboot).
I also tried to use Visionary too but doesn't seem to have any luck.
Is there any other method I can try to get the root access?
Another question is after I followed Part 1 of the steps in http://forum.xda-developers.com/showthread.php?t=832503, when I boot up my computer, I can't seem to go to Windows. I am sure I selected physical disk instead of logical disk but I don't know why this happen. Anybody encounter the same problem?

I'm currently in the situation of wanting to root and S-off my Desire Z in order to update, either to official or (more likely) Virtuous ROM.
However before I do so I have a couple of questions.
1) How do I back up everything on my phone? I know my contacts and calendar will be fine as they are from my google account, also my email will be ok as that is also my google account. Photos etc I can just copy to my PC but what about all the apps I've installed, and my progress in them, my pair bluetooth devices, my wifi access points, my mesage apn settings etc etc?
I have tried Titanium Backup but not having paid for the full version, the info it gives you is a little limited so i'm not sure what it's backed up etc?
2) I currently have root via using Visionary, do I need to unroot and then go through the process with all the adb stuff? Also, will i need to uninstall the SuperUser I have installed?
3) I think my ADB is setup as I managed to get it to boot the phone into the bootloader, but when Itried to check my INFOCID using
Code:
fastboot oem boot
I got an error message saying that fastboot was not a recognised function (or something similar to that) Is this a problem?
ANy help really really appreciated as I am a total newb with Android but would love to move to a more up-to-date software version as I am currently on 1.34.
Thanks in advance.

valve90210 said:
I'm currently in the situation of wanting to root and S-off my Desire Z in order to update, either to official or (more likely) Virtuous ROM.
However before I do so I have a couple of questions.
.......................... lots of questions...............
ANy help really really appreciated as I am a total newb with Android but would love to move to a more up-to-date software version as I am currently on 1.34.
Thanks in advance.
Click to expand...
Click to collapse
You could wait until HTC releases a OTA update for your phone. Or as a alternative and avoiding being impatient, you could do a lot of reading and learning on this site to apply a custom rom. It is not that difficult at all, but do not expect a step by step walking trough the minute you ask for something here.

HLeenders said:
You could wait until HTC releases a OTA update for your phone. Or as a alternative and avoiding being impatient, you could do a lot of reading and learning on this site to apply a custom rom. It is not that difficult at all, but do not expect a step by step walking trough the minute you ask for something here.
Click to expand...
Click to collapse
Wow, thanks for your helpful post...
I've done loads of reading on the forum and have gone rather round in circles. I think I know what I'm doing but seeing as someone else who is new to it had posted a thread I thought I'd also ask a couple of questions that I had which were pertinent to the discussion, to firstly find out for myself and secondly to help anyone else that might be finding the thread otherwise useful.
I think I have sorted the abd problem I was having, it seems that various tools have moved to different folders in the latest version of the android sdk so when I was trying the "fastboot" line it was nt findint fastboot.exe as it was in a different folder.
Secondly I'm fairly happy to give the gfre stuff a whirl but before I do I just wanted a little confirmation about backing everything up...not a huge ask really and fairly essential I would say!

valve90210 said:
Wow, thanks for your helpful post...
I've done loads of reading on the forum and have gone rather round in circles. I think I know what I'm doing but seeing as someone else who is new to it had posted a thread I thought I'd also ask a couple of questions that I had which were pertinent to the discussion, to firstly find out for myself and secondly to help anyone else that might be finding the thread otherwise useful.
I think I have sorted the abd problem I was having, it seems that various tools have moved to different folders in the latest version of the android sdk so when I was trying the "fastboot" line it was nt findint fastboot.exe as it was in a different folder.
Secondly I'm fairly happy to give the gfre stuff a whirl but before I do I just wanted a little confirmation about backing everything up...not a huge ask really and fairly essential I would say!
Click to expand...
Click to collapse
You can use Astro File Explorer to back up your apps, Call Logs Backup and SMS backup will backup the sms threads and call logs or if you want to spend a couple of bucks Root explorer works well for me also. Once you have CWM you can make a Nandroid backup and will have an exact image of you phone at that point in time that you can go back to. I am waiting for my DZ to arrive and currently using an Inspire and 2 Captivates that other than minor differences in the procedures the backup maintenance is the same. The problem is that if you downgrade to a rom that allows CWM you cant back up the existing newer one. There are copies of it out there though. Just be careful if trying to go back to it and read carefully as I understand there are possible problems going back if the correct procedures are not followed. Good luck to you and as the previous poster stated about educating yourself, I fully agree. Read until you understand then read again to make sure you are not missing something. Follow directions EXACTLY and it usually avoids problems.
Sorry I see you are on 1.34 which I think means that once you get S-Off and root you can download rom manager from the market, install clockworkmod and you will be good to go with Nandroid backups.

[Q] Downgraded to 2.1, Rooted successfully, now low space problem,Can't update new v.

Hi,
Sorry I am a new to android and to this forum also. I have some questions which I need your expert opinion.
I have downgraded using [HOWTO] Downgrade Froyo (2.2) to Stock 2.1 (ANY HBOOT | WIN/LINUX/MAC | ROOT) and rooted successfully with Unrevoked because other method did not work.
I have installed some programs, to my surprise it has occupied all the space and application can't be transferred to SD. Later, I found App2SD is not working with this version 2.1.
Update phone popped out & I tried to download and install but in vain. It shows some triangular shape with exclamation mark inside that triangle.
What is the solution now ? can I transfer my app2SD like before with 2.2.2 version ? How to unroot now & update from the server and revert back to the same because I found downgrade is outdated ?
Did I make mistake choosing downgrade method? What are the choices do I have to work like before ?
Thank you in advance.

oh god what on earth have you been doing.
If you have another android phone then make a goldcard and stick it into the broken desire.
boot into fastboot mode (hold back & power), plug in via usb, download and install the latest WWE RUU (can find on my guide).
If you can't make a goldcard, look for the RUU for your network provider (e.g. vodafone, tmobile etc.) and use that. Make sure it's a 2.2 Froyo RUU and its not just the OTA update!!
if that's too hard for you, go on my guide and download the 2.3 RUU and use that.
Once the phone's been updated go to revolutionary.io and use the tool. It works every time.
Then flash recovery, look at my guide on how to do so.
Then backup your current ROM and flash away with anything you want. Just make sure to do a full wipe between flashes (boot, system, data, cache, dalvik)

Dear bortak,
Thank you for the reply.
I do not have another android so it looks that I won't be able to make a goldcard. Among other options you gave me ?RUU I will look at your guide how to make. Hope that 2.3 will works.
Is gold card necessary ? Can I make it after 2.3 installation ?
Will do accordingly as per you advice.
How to back up current ROM and flash anything ???
Sorry I am totally new to this androind. Has been using like a layman.
Thank you much appreciated.

unless your phone was bought unbranded, it will have a Customer ID that links it to a particular network. If you try to use a RUU (ROM Update Utility) that was not released for your phone, you will receive a CID Error. A goldcard makes the phone ignore the CID, and therefore you can use any RUU you want, so you don't have to worry about getting the right one.
So, if you got your phone with Vodafone like I did, you need to download a Vodafone RUU.
The 2.3 RUU is the 2.3 Gingerbread released by HTC, and it was not given as an OTA (Over The Air) update. The 2.3 RUU de-brands your phone, and it doesn't matter where you got the phone from, you can use that one regardless.
It is recommended that you use the RUU for your network provider, as if that goes wrong, you can try it again, or use the 2.3 RUU.
If you use the 2.3 RUU and something goes wrong, you have nothing to fall back on, because you cannot simply roll-back software versions using RUU's, you can only update.
So, if I were you, I'd go to shipped-roms.com and try to find the right RUU for you. If you bought the phone unbranded (i.e. you din't get it from a network) you can just use the latest WWE RUU. If you got it on contract or PAYG from a network e.g. Vodafone, then you need to download the Vodafone RUU. (Make sure it's the 2.2 Froyo one, and it doesn't say "OTA", because that's just an update, not the full RUU).

It is not branded (no network). What ever is best I try to do. Which one is the l latest WWE RUU ?
Do I need to follow this full:
S-OFF
[STEP1]- download "Bravo Stock" from Alpharev
[STEP2]- download Android Flasher
[STEP3]- use android flasher to flash "Bravo Stock"
[STEP4]- run the RUU again and wait for it to finish
Thanks.

drmg said:
It is not branded (no network). What ever is best I try to do. Which one is the l latest WWE RUU ?
Do I need to follow this full:
S-OFF
[STEP1]- download "Bravo Stock" from Alpharev
[STEP2]- download Android Flasher
[STEP3]- use android flasher to flash "Bravo Stock"
[STEP4]- run the RUU again and wait for it to finish
Thanks.
Click to expand...
Click to collapse
Nono, you only need to use that guide when something goes wrong.
Find the WWE RUU in #resources, boot into fastboot, plug it in and run the RUU. Then you can look on S-OFF problems.

Thanks & Need to explore android more
Dear bortak,
Thanks for your guidance.
While exploring the abilities of android, I was lost. Without you it would not have possible.
I have installed 2.3.3 accordingly. It has upgraded perfectly.
I had problem with rooting
I did according to revolutionary. io It worked with ease, S-Offed but not rooted.
In my desperation I have tried Unrevoked. It also did not work. It says "Your firmware is too new" . Did all the methods from changing version of Unrevoked and uninstalling one program. Still did not work. No ROOT
Finally, I found that I have not done complete task. I re-tried revolutionary. io and browse through different resources about it. Revolutionary was explained in a simple & efficient way in theunlockrdotcom. I followed that those steps & finally root was successfully.
It would not have possible without your support.
Now, I have done rooting. What wanted to see other aspects ? What can be done now to make the android works without restrain ? Flashing ?? ROM ?
Now, do I have to make a goldcard ?
Please advice me what are the other things I can do to work with android above the usual layman. Thanks.

drmg said:
Dear bortak,
Thanks for your guidance.
While exploring the abilities of android, I was lost. Without you it would not have possible.
I have installed 2.3.3 accordingly. It has upgraded perfectly.
I had problem with rooting
I did according to revolutionary. io It worked with ease, S-Offed but not rooted.
In my desperation I have tried Unrevoked. It also did not work. It says "Your firmware is too new" . Did all the methods from changing version of Unrevoked and uninstalling one program. Still did not work. No ROOT
Finally, I found that I have not done complete task. I re-tried revolutionary. io and browse through different resources about it. Revolutionary was explained in a simple & efficient way in theunlockrdotcom. I followed that those steps & finally root was successfully.
It would not have possible without your support.
Now, I have done rooting. What wanted to see other aspects ? What can be done now to make the android works without restrain ? Flashing ?? ROM ?
Now, do I have to make a goldcard ?
Please advice me what are the other things I can do to work with android above the usual layman. Thanks.
Click to expand...
Click to collapse
Since you already upgraded to the 2.3 RUU, the 2.2 RUU's go out of the window, so you don't need a goldcard.
Flashing is basically the process of replacing the entire Android OS for a different version.
Key subgroups are:
Sense 2.0/2.1
Sense 3.0/3.5
Stock AOSP Gingerbread
Customised AOSP Gingerbread
MIUI AOSP Gingerbread
AOSP ICS (UNSTABLE)
AOSP: Android Open Source Project
If you have not already done so, you need to flash a recovery image to your device. You can either do this by installing the 4EXT recovery control from the Play Store, or you can look at my guide for guidance on how to do so manually.
Remember to backup before flashing anything.
Some ROMs take advantage of custom bootloaders. Custom bootloaders basically change the partition sizes of the nand memory of your device (its internal memory). It changes the /system /data and /cache partitions, and because many ROMs only require smaller /system partitions, more memory can be freed up in /data. Go to alpharev.nl for more information, there is a guide on how to flash bootloaders on my guide also, and read on the thread what hboot the ROM needs.
Before you flash, it is good to do a full wipe (boot, system, data, cache, dalvik) as this helps to prevent any errors from occurring.

Looks complicated though I will try. Thank you very much.

drmg said:
Looks complicated though I will try. Thank you very much.
Click to expand...
Click to collapse
It's really not.. you can find tutorials for all of this on my guide, some even with videos.

Great !
You have a great tutorial & help attitude. I didn't know anything about the android after using Desire for more than 1 years. I feel good & content that I have achieved something with the help of your tutorials & feedback.
With the help of your guide I was able to flash the rom. It is called cyanogen 7.1.
I flashed this stable version and worried that the latest won't work on my android.
It's very good but I am have big time problem since it has no market and not able to download anything since market can't be downloaded.
I had backup my original ROM . Now if I want to flash another ROM than do I need to do the same process with wipe out data ?
Do I need to backup this cyanogen also ?? What if I want to use my original ROM, in that case how to recover/restore my original ROM ? What are the others good ROM you suggest to flash ? I have no choices, nor I can choose. Cyanogen is good but that problem with market.
Lastly the root is there, will it remain if I flash another ROM?
Thank you for your wonderful guidance, feedback & tutorial. God bless.

drmg said:
Great !
You have a great tutorial & help attitude. I didn't know anything about the android after using Desire for more than 1 years. I feel good & content that I have achieved something with the help of your tutorials & feedback.
With the help of your guide I was able to flash the rom. It is called cyanogen 7.1.
I flashed this stable version and worried that the latest won't work on my android.
It's very good but I am have big time problem since it has no market and not able to download anything since market can't be downloaded.
I had backup my original ROM . Now if I want to flash another ROM than do I need to do the same process with wipe out data ?
Do I need to backup this cyanogen also ?? What if I want to use my original ROM, in that case how to recover/restore my original ROM ? What are the others good ROM you suggest to flash ? I have no choices, nor I can choose. Cyanogen is good but that problem with market.
Lastly the root is there, will it remain if I flash another ROM?
Thank you for your wonderful guidance, feedback & tutorial. God bless.
Click to expand...
Click to collapse
No, you don't need to backup when you're restoring your old ROM, however do a wipe whenever moving to another ROM (with backup or new flash).
The reason you don't have market and other google apps is because cyanogen is so big, google has disallowed them to include google apps with their ROMs, and they need to be flashed seperately, like I mentioned in the previous post.
Click the gapps link (from the previous post) and flash it the same way you did Cyanogen

Thanks.
You mean I need to flash google market as well like a cyanogen or I can install it or with the android flasher?
BTW, what is gapps link ? Thanks..

drmg said:
Thanks.
You mean I need to flash google market as well like a cyanogen or I can install it or with the android flasher?
BTW, what is gapps link ? Thanks..
Click to expand...
Click to collapse
oh my bad I got confused with another post, link wasn't there.
gapps - Google Apps - Play store, gmail, setup wizard etc. etc.
You flash the gapps.zip like cyanogenmod - through recovery. This is only needed with Cyanogenmod, all* other ROMs have them.
http://goo.im/gapps/gapps-gb-20110828-signed.zip
*well most do at least, those that don't tell you.

Excellent. Market has finally worked. Thank you

[Q[ Questions on RUU

Hey Guys,
I just had some questions regarding RUU's and sort of trying to understand them.
Do RUU's update everything that normal custom ROM's cannot, i.e. like the OTA's? So updating drivers and hboot etc?
Main reason is that if it does update everything then on the next big update I would probably want to do an RUU install even if it means loosing all data.
With regards to the RUU do I need all three of the following:
- Stock ROM
- Stock Recovery
- Locked bootloader
Or do I need JUST a locked bootloader?
Thanks

Yes you will get updates if you flash a ruu and ruu 's are pure stock ruu's are used when we need to put the stock Rom back on our device when we need to send it in for repair's and also when we prefer the stock Rom over a custom Rom I my self prefer custom Rom over a stock Rom and sometimes when a custom Rom isnt performing the way it should some people will simply go back to stock by flashing a ruu
Sent From My Viper S 1.2.0 with true s off by alpha revolutionary

jslim38 said:
Yes you will get updates if you flash a ruu and ruu 's are pure stock ruu's are used when we need to put the stock Rom back on our device when we need to send it in for repair's and also when we prefer the stock Rom over a custom Rom I my self prefer custom Rom over a stock Rom and sometimes when a custom Rom isnt performing the way it should some people will simply go back to stock by flashing a ruu
Sent From My Viper S 1.2.0 with true s off by alpha revolutionary
Click to expand...
Click to collapse
Thanks, my main reason is actually not to say on an RUU but I was hoping to install an RUU, get all the updates to my firmware and drivers, then unlock bootloader again and install a custom ROM.

They should be updated by a custom rom. Only thing that isnt touched is the HBOOT i think. But reflash stock recovery relock the bootloader then run the ruu.

Flashing an RUU first if available is the way to go personally
Sent from my HTC One X using xda premium

I readin a lot on here and I read somewhere updateing with ruu updates hboot and hboot is some sort of security so updateing it could make getting s-off harder
Sent from my HTC One X using xda premium

Updating the HBoot means adding more layers of security, which imo is not something we enjoy here on XDA
Personally, I prefer going with a custom ROM that is almost like stock (preferably ARHD) which with every update brings the improvements brought to us by HTC and even more.
Also with ARHD for example, upgrading from one version to a newer one rarely requires you to wipe all your data which is very annoying imo.

I've been on Custom roms since I had my phone so I had missed the OTA update for 1.xxx.11 and the 2.xx versions, now with the a big 3.xx version on the horizon, my main concern is if my Custom ROM's are not updating some critical firmware drivers and such that would have benefitted my phone.
Tbh it's still not clear to me what Custom ROM's cannot update, at first I thought it was just the HBOOT but then I read on a recent thread that apparently things like GPU drivers and other essential hardware firmware drivers may not get updated either which sounds like a big deal. Hence I was thinking with the release of 3.xx I should do an RUU install just to be sure and then go ahead to a Custom ROM.
I understand that having my HBOOT updated could mean S-OFF is harder but the way things are, it doesn't look like were any close to getting it either, who knows maybe even a future HBOOT update might have an easier S-OFF is HTC decide to relax it a bit from consumer pressure?

When developers get their hands on new RUUs they base their custom Roms on them, and therefore you will get the new updates in terms of drivers and other software related things.
Also, kernels bring new improvements as they are updated, and developers also build their ROMs on these kernels. However, you can flash custom kernels separately if you find one that has additional "improvements" you like.
In short, custom ROMs that are maintained/updated regularly (ARHD is one of the best imo) is all you need to stay up to date with all the new improvements.
The only reason I ever download any RUU is in case something went wrong with my phone, and I wanted to temporarily return to stock.

Ah right, I was thinking more of the S-ON security restriction not letting custom ROM's fully update everything except radio, kernel and ROM but RUU's are given the full access to update everything?

iq-dot said:
Ah right, I was thinking more of the S-ON security restriction not letting custom ROM's fully update everything except radio, kernel and ROM but RUU's are given the full access to update everything?
Click to expand...
Click to collapse
I don't think there is consensus on what can be updated and what cannot.
Here's my take: an OTA has access to everything, as does an RUU, but the point is that they flash signed images, and the phone will allow signed images to be flashed (subject to matching CID, etc.).
It's possible to flash kernel with the boot.img, and also possible to flash kernel modules, which means that drivers can be updated.
It's possible to flash "radios" (often as part of the ROM), and there is an app to get updated RILs, so it would seem that the RIL has not been confused with the radio. However, since the bootloader appears to get the radio version from a text file, rather than the radio, there's some doubt as to whether the radio is really updated (since the bootloader disagrees).
Obviously we can unlock and gain access to flashing unsigned recovery, boot (kernel/ramdisk) and ROM images.
Outside of this, it's not impossible that there are areas of the phone that still require flashing of signed images, such as for firmware updates of other bits of hardware not previously mentioned (speculatively: lower level bits of "radio", cpu microcode, gpu firmware, etc.), which may or may not be flashable with an RUU (or maybe even an OTA). However, there is nothing in an RUU that cannot be done with tools we already have, so if there was a "fastboot flash cpu_microcode" option, somebody would have found it. I haven't looked at full list of fastboot commands, but I don't recall coming across anything like that.

xbiggyl said:
When developers get their hands on new RUUs they base their custom Roms on them, and therefore you will get the new updates in terms of drivers and other software related things.
Also, kernels bring new improvements as they are updated, and developers also build their ROMs on these kernels. However, you can flash custom kernels separately if you find one that has additional "improvements" you like.
In short, custom ROMs that are maintained/updated regularly (ARHD is one of the best imo) is all you need to stay up to date with all the new improvements.
The only reason I ever download any RUU is in case something went wrong with my phone, and I wanted to temporarily return to stock.
Click to expand...
Click to collapse
There are some parts of the firmware/drivers that custom ROMs cannot change so flashing an RUU first does have it's benefits to get a true experience of a custom ROM

EddyOS said:
There are some parts of the firmware/drivers that custom ROMs cannot change so flashing an RUU first does have it's benefits to get a true experience of a custom ROM
Click to expand...
Click to collapse
Do you know what, specifically?

I don't, no, it's just a personal preference I suppose. I updated to the 2.17 RUU (UK unbranded) and then went onto a custom ROM based on the same RUU so I know everything is compatible. Whether it has any real affect I don't know but seeing as Mike used to have 'firmware' packages for other HTC handsets it would lead me to believe he would with the One X if we had S-OFF

EddyOS said:
Mike used to have 'firmware' packages for other HTC handsets it would lead me to believe he would with the One X if we had S-OFF
Click to expand...
Click to collapse
...there are a lot of masked partitions, eh? Who knows.

A lot of the partitions were listed in the S-OFF thread but as to what they actually contain/do is open to discussion - it could be a custom ROM it's own is enough but without S-OFF we'll never really know

EddyOS said:
There are some parts of the firmware/drivers that custom ROMs cannot change so flashing an RUU first does have it's benefits to get a true experience of a custom ROM
Click to expand...
Click to collapse
Have you read anywhere of any improvements offered exclusively by RUUs or you're simply speculating?
I know some partitions (that appeared to be in the HOX) are not accessible by Custom Roms, but has anyone ever claimed to have experienced an improvement in any way by flashing an RUU that people flashing custom Roms haven't?
Sent from my HTC One X using Tapatalk 2

[Q] WiFi wont turn on

So I installed a new rom recently and i noticed after doing so my wifi stopped working and my data disconnects at random times.
Here is information about my phone . Thank you for anyhelp
Android Version:
5.0.1
HTC Sense Version:
7.0
Software Version:
LeeDrOiD_One_M8_S7_V7.0.2
PRI Version:
2.62_003
PRL Version:
55025
Kernal Version:
3.4.0-g53c7f19
[email protected] #1
SMP PREEMPT
Baseband Version:
1.08.20.0612_4
Build Number:
4.20.654.10 CL476182 release-keys
HBOOT:
3.18.0.0000
Radio:
1.08.20.062_4
OpenDSP:
v45.2.2-00542-M8974_HM.0422
OS:
2.16.654.4
MID:
0P6B70000
CID:
SPCS_004
My phone is S-ON

You need to update your firmware, as discussed on many different threads.

And by updating your firmware, he means the "baseband", not the rom itself. You will most likely need to S-Off.

smknutson said:
And by updating your firmware, he means the "baseband", not the rom itself. You will most likely need to S-Off.
Click to expand...
Click to collapse
Firmware is not the ROM itself, that is true (and a common source of confusion). But it includes a variety of partitions/modules not contained in the ROM, only one of which is the radio baseband:
hboot
radio
WiFi (and its this one that is causing the issue)
Bluetooth
Media
Stock recovery
boot.img
Others
Updating firmware is possible with s-on by returning to stock ROM and stock recovery, and updating via OTA to the current Lollipop software and firmware. After that, the OP can flash custom recovery again, and the custom ROM of choice.

Could you possibly show the right direction in doing that, im having trouble finding stuff for this specific model

MrZackFX said:
Could you possibly show the right direction in doing that, im having trouble finding stuff for this specific model
Click to expand...
Click to collapse
Did you try to flash the stock Lollipop ROM for your version (CID)?
What you probably need to do is flash the 2.16.654 stock ROM, corresponding stock recovery, than OTA up to Lollipop to update the firmware. Finding the stock 2.16.654 ROM may be the challenge here.
You didn't happen to make a nandroid (TWRP backup) of your stock ROM before flashing any other ROMs?

redpoint73 said:
Did you try to flash the stock Lollipop ROM for your version (CID)?
What you probably need to do is flash the 2.16.654 stock ROM, corresponding stock recovery, than OTA up to Lollipop to update the firmware. Finding the stock 2.16.654 ROM may be the challenge here.
You didn't happen to make a nandroid (TWRP backup) of your stock ROM before flashing any other ROMs?
Click to expand...
Click to collapse
No sadly i didnt, would it make things easier if i s-off then go to stock?

MrZackFX said:
No sadly i didnt, would it make things easier if i s-off then go to stock?
Click to expand...
Click to collapse
With s-off, you can flash a firmware package without having to jump through the hoops of returning to stock and OTA updates.
But if its not the Lollipop firmware for your CID (for instance, you can't find it), you'll need to make sure its one that has a radio baseband that plays well with your local carrier.
The one hitch, is that you may need to restore to stock in order to run sunshine s-off. Sunshine may or may not work with LeeDroid. It might be "stockish" enough for sunshine to work.

redpoint73 said:
With s-off, you can flash a firmware package without having to jump through the hoops of returning to stock and OTA updates.
But if its not the Lollipop firmware for your CID (for instance, you can't find it), you'll need to make sure its one that has a radio baseband that plays well with your local carrier.
The one hitch, is that you may need to restore to stock in order to run sunshine s-off. Sunshine may or may not work with LeeDroid. It might be "stockish" enough for sunshine to work.
Click to expand...
Click to collapse
I dont care what rom i use as long as the phone fully works. Then i will work on making it look pretty. The only reason why im using LeeDroid is because its the least buggy rom i found with my phone in its current position.

MrZackFX said:
I dont care what rom i use as long as the phone fully works. Then i will work on making it look pretty. The only reason why im using LeeDroid is because its the least buggy rom i found with my phone in its current position.
Click to expand...
Click to collapse
I'm not talking about your ROM preference. I'm referring to the fact that stock ROM (and also stock recovery) is the best configuration for sunshine s-off to work. But you are in kind of a Catch-22, in that you are trying to get back to stock. And by the time you return to stock ROM and stock recovery, you are pretty close to just updating the firmware by OTA, anyway (and in that case, s-off isn't needed).
Some folks have had success doing s-off with certain custom Sense ROMs (while other ROMs will interfere with sunshine). I think InsertCoin and Maximus are the ones I've seen mentioned, and LeeDroid might be close enough to stock for sunshine to work, also. Its worth trying, anyway (if s-off is indeed what you want). The sunshine app will tell you whether your phone is compatible or not (and if not, then you can try a different ROM), and you won't be charged any money unless it works.

redpoint73 said:
I'm not talking about your ROM preference. I'm referring to the fact that stock ROM (and also stock recovery) is the best configuration for sunshine s-off to work. But you are in kind of a Catch-22, in that you are trying to get back to stock.
What I'm saying is that some folks have had success doing s-off with certain custom Sense ROMs (while other ROMs will interfere with sunshine). I think InsertCoin and Maximus are the ones I've seen mentioned, and LeeDroid might be close enough to stock for sunshine to work, also. Its worth trying, anyway. The sunshine app will tell you whether your phone is compatible or not (and if not, then you can try a different ROM), and you won't be charged any money unless it works.
Click to expand...
Click to collapse
Is there anyway with out being charged money?

MrZackFX said:
Is there anyway with out being charged money?
Click to expand...
Click to collapse
Any way to s-off besides sunshine? NO.
If you are asking if there is a way to update firmware without paying (therefore with s-on), I've already described that process in Post #6 above. But as I already mentioned there, you might have trouble finding the 2.16.654 stock nandroid. You may need to ask for it to be posted, or look around.

redpoint73 said:
I'm not talking about your ROM preference. I'm referring to the fact that stock ROM (and also stock recovery) is the best configuration for sunshine s-off to work. But you are in kind of a Catch-22, in that you are trying to get back to stock. And by the time you return to stock ROM and stock recovery, you are pretty close to just updating the firmware by OTA, anyway (and in that case, s-off isn't needed).
Some folks have had success doing s-off with certain custom Sense ROMs (while other ROMs will interfere with sunshine). I think InsertCoin and Maximus are the ones I've seen mentioned, and LeeDroid might be close enough to stock for sunshine to work, also. Its worth trying, anyway (if s-off is indeed what you want). The sunshine app will tell you whether your phone is compatible or not (and if not, then you can try a different ROM), and you won't be charged any money unless it works.
Click to expand...
Click to collapse
I just changed to stock using the tool in this thread. About to setup my phone and do the ota updates
http://forum.xda-developers.com/showthread.php?t=2729173

MrZackFX said:
I just changed to stock using the tool in this thread. About to setup my phone and do the ota updates
http://forum.xda-developers.com/showthread.php?t=2729173
Click to expand...
Click to collapse
Ah, yes. I don't think it even occurred to me that your version was Sprint, and that it had RUUs. While I'm in the US (AT&T) I'm so used to helping folks outside the US (and most variants outside the US don't have RUUs).
If you used the RUU to update to version 4.25 firmware, that is already up to date, and there won't be an OTA at this time.

redpoint73 said:
Ah, yes. I don't think it even occurred to me that your version was Sprint, and that it had RUUs. While I'm in the US (AT&T) I'm so used to helping folks outside the US (and most variants outside the US don't have RUUs).
If you used the RUU to update to version 4.25 firmware, that is already up to date, and there won't be an OTA at this time.
Click to expand...
Click to collapse
Yeah i didnt think to use the updated one until i was finished flashing. But non the less i got it working once again.