Related
Hi everyone! I'm new here so apologies for any mistakes, wrongs etc.
I needed some help with my HTC desire S, I'm new to all this rooting, flashing stuff, but i'm not too thick so understand some things. So heres the story/problem.
About a month ago I S-OFF my phone to try out some awesome custom ROMS, Granted i had some fun with them, I installed an unofficial 2.3.5 gingerbread with sense 3.0, just to see what the new sense was like, As I didn't receive the OTA update on my phone. But now i'd like to restore my phone back to the original ROM that came on the phone. I'm not to fused weather its S-OFF, all I really wanted was my original ROM as Sense 3.0 is running so slow on my phone, and its made a big difference in performance. I'm one of these guys who says please search the forum and google for help. And I did just this and found some great information yet of which i have had no luck with.
I've tried running an RUU whilst my phone is switch on and connected via HTC Sync, No luck. Model ID error 130....Please use the correct ROM (or something along those lines) So i found that u could flash the RUU after extracting the rom.zip and renaming it to PG88IMG.zip. So i did just this, still no luck, Updating was being processed and at the end of the update I got the message Wrong model ID and again Please use correct ROM (something like that anyway!)
Now your probably laughing at me by now thinking rialcniS you thick so and so, your using the wrong RUU. Which to anyone else sounds correct. But surely if i'm trying to convert back to the original stock ROM then 2.3.3 Gingerbread is the one to go for? as this was what my phone was running from the box!
So I did a little bit more research and found out that maybe its to do with my Hboot version. Below are my phones detail.
SAGA PVT ENG S-OFF
HBOOT-6.98.2000 (PG8810000)
RADIO-3822.09.08.20_M
eMMC-BOOT
FEB 24 2011,21:19:05
Software Information:
Android version - 2.3.5
HTC Sense Version - 3.0
Software Number - Desire S 2.10.401.4 [PROXUSER]
Kernel version - 2.6.35.10-g9ac6c7a
Baseband version - 20.48.30.0922U_3822.09.08.20_M
Build Number 2.10.401.4 CL156318 release-keys
Browser version - WebKit/533.1
From my research I found (or at least this is how it translates in my brain) is that I cant install an original stock ROM on Hboot 6.98.2000. Is this correct?
Anyway, for some more information to you guys when I load my phone up in fastboot, it starts searching for the PG88IMG.zip and also something along the lines of PG88DIAG, yet all it says underneath is Wrong or no image?
Am I being a complete idiot, or does this seem strange to some of you more advanced android rooters
If anyone can point me in the right direction to where i might be going wrong, id much appreciate it!
Thanks in advanced
Rialcnis!
rialcnis said:
Hi everyone! I'm new here so apologies for any mistakes, wrongs etc.
I needed some help with my HTC desire S, I'm new to all this rooting, flashing stuff, but i'm not too thick so understand some things. So heres the story/problem.
About a month ago I S-OFF my phone to try out some awesome custom ROMS, Granted i had some fun with them, I installed an unofficial 2.3.5 gingerbread with sense 3.0, just to see what the new sense was like, As I didn't receive the OTA update on my phone. But now i'd like to restore my phone back to the original ROM that came on the phone. I'm not to fused weather its S-OFF, all I really wanted was my original ROM as Sense 3.0 is running so slow on my phone, and its made a big difference in performance. I'm one of these guys who says please search the forum and google for help. And I did just this and found some great information yet of which i have had no luck with.
I've tried running an RUU whilst my phone is switch on and connected via HTC Sync, No luck. Model ID error 130....Please use the correct ROM (or something along those lines) So i found that u could flash the RUU after extracting the rom.zip and renaming it to PG88IMG.zip. So i did just this, still no luck, Updating was being processed and at the end of the update I got the message Wrong model ID and again Please use correct ROM (something like that anyway!)
Now your probably laughing at me by now thinking rialcniS you thick so and so, your using the wrong RUU. Which to anyone else sounds correct. But surely if i'm trying to convert back to the original stock ROM then 2.3.3 Gingerbread is the one to go for? as this was what my phone was running from the box!
So I did a little bit more research and found out that maybe its to do with my Hboot version. Below are my phones detail.
SAGA PVT ENG S-OFF
HBOOT-6.98.2000 (PG8810000)
RADIO-3822.09.08.20_M
eMMC-BOOT
FEB 24 2011,21:19:05
Software Information:
Android version - 2.3.5
HTC Sense Version - 3.0
Software Number - Desire S 2.10.401.4 [PROXUSER]
Kernel version - 2.6.35.10-g9ac6c7a
Baseband version - 20.48.30.0922U_3822.09.08.20_M
Build Number 2.10.401.4 CL156318 release-keys
Browser version - WebKit/533.1
From my research I found (or at least this is how it translates in my brain) is that I cant install an original stock ROM on Hboot 6.98.2000. Is this correct?
Anyway, for some more information to you guys when I load my phone up in fastboot, it starts searching for the PG88IMG.zip and also something along the lines of PG88DIAG, yet all it says underneath is Wrong or no image?
Am I being a complete idiot, or does this seem strange to some of you more advanced android rooters
If anyone can point me in the right direction to where i might be going wrong, id much appreciate it!
Thanks in advanced
Rialcnis!
Click to expand...
Click to collapse
Can't say much but I will point you to see this guide if it helps .
www.freeyourandroid.com/guide/flashing-ruu-htc
Sent from a darkly dreaming freak named Ray with a hTC Desire S in his hand which's rom is changed by the owner more than his clothes !
More useful info will be not the current state of your device, but what it was before the S-Off and customizing.
Setup the adb and fastboot commands on your PC /there is guide in my signature.
Then connect the device and type the following commands:
Code:
adb devices ([I]your device serial number should be displayed[/I])
adb shell [I](there should be a command prompt with the # symbol in front if not type "su" without the quotes[/I])
dd if=/dev/block/mmcblk0p17 of=/sdcard/misc.img ([I]this will create a misc.img file on your SDcard[/I])
Then copy the misc.img to your PC and open it with HEX editor (XVI32 is free, you can google it)
Open the misc.img with HEX Editor. There will be a number like 1.28.401.1 on line 6. This is the number of your original software.
Search in this thread for the proper RUU and install it.
Important! Before flashing the RUU change your hboot with this one
Maybe sounds complicated but nothing scary about it, just follow the steps carefully.
Good luck
use search there is a whole thread about downgrading the hboot ON THE FIRST PAGE.
Sorry, I had searched and searched everywhere for about 3 hours straight, and every time I found something that seemed promising i would get errors and have no luck.
@amidabuddha, Thankyou so much, this seems very promising. I'll give it ago tonight and keep you posted on the progress!
Thanks again!!
look for a thread called downgrading the new hboot.theres a guide ,it works fine as i have used it myself.
djisgod said:
use search there is a whole thread about downgrading the hboot ON THE FIRST PAGE.
Click to expand...
Click to collapse
djisgod said:
look for a thread called downgrading the new hboot.theres a guide ,it works fine as i have used it myself.
Click to expand...
Click to collapse
Hey, his problem is not the hboot, he needs his Stock configuration for his region (which is wise in order to keep the warranty). The only thing he needs for this is the proper RUU and overwrittable hboot, no downgrades, no other stuff
amidabuddha said:
Hey, his problem is not the hboot, he needs his Stock configuration for his region (which is wise in order to keep the warranty). The only thing he needs for this is the proper RUU and overwrittable hboot, no downgrades, no other stuff
Click to expand...
Click to collapse
So, thanks to you mate i've got it all back to stock! Fantastic! Thankyou very much for your help and keep up the good work!
rialcnis said:
So, thanks to you mate i've got it all back to stock! Fantastic! Thankyou very much for your help and keep up the good work!
Click to expand...
Click to collapse
Glad that you solved your issue.
Just out of curiosity - which one was your RUU?
And for your information (there was a complain in your first post about sense 3 performance) - if you receive the 2.10.x.x OTA update notification, the stock sense 3 runs pretty good on my device, no lagging, no bugs so far. So maybe you can give it a try when the time comes.
Enjoy your "new" phone
amidabuddha said:
Glad that you solved your issue.
Just out of curiosity - which one was your RUU?
And for your information (there was a complain in your first post about sense 3 performance) - if you receive the 2.10.x.x OTA update notification, the stock sense 3 runs pretty good on my device, no lagging, no bugs so far. So maybe you can give it a try when the time comes.
Enjoy your "new" phone
Click to expand...
Click to collapse
Yeah I'm not to sure, it was running slow and not nice and fresh like it is now! but i reckon now i know how to solve the problem if it occurs again i might give it a try my original RUU was the one u listed in your post 1.28.401.1. Nice and simple instructions you gave, so thanks very much again!!
I have been flashing for a while, and although not a pro by any means, I'm not a noobie either. I've looked for similar issues from others and have yet to find one that addresses this point specifically: I downloaded and attempted to utilize the PG58IMG.ZIP and repeatedly get the PU Fail. I saw another post relating to the issue being when you either accidentally or purposely try to flash it MORE THAN ONCE. I believe this is the mistake I made ( I was dumb enough to flash while riding in a car ). The issue is this: If I try to enter recovery from the 'outside' ; i.e. a completely turned off phone, with vol and on/off, I cannot use recovery. It will repeatedly make me go through the process of trying and failing to install this over and over. So, am I screwed? To tell the truth, I have no other issues with the phone, running ARHD 3.6.9, 4.1.9, or 5.0.2 as well as RCmix 3.5 v10 or ICS. BUt, if something happens to keep me from accessing recovery from within 4EXT, I will have a real problem. Now, I've seen the new RUU posting for ICS and would like to try it. Will this fix my problem? Is updating my HBOOT the answer? Is there any other way that I'm not thinking of? I don't often start threads with questions becuase I'm willing to find the answer through searching, but haven't found any direct answers to this particular part of the problem. Any help would be appreciated...
HTC Sensation 4G
HBOOT 1.17.1111
Radio 10.14.9035.01
Baseband 10.56.9035.000
Currently running:
RCMix 3.5 V010
2.3.5 w/ sense 3.5
Bricked XE 2.6.35.14
o/c to 1.78
So if you flash a lot of RUU ,you must have supercid?
Sent from my HTC Sensation 4G using XDA Premium App
Silly question perhaps but have you deleted PG58IMG from your SD card and tried then?
wmoore said:
Silly question perhaps but have you deleted PG58IMG from your SD card and tried then?
Click to expand...
Click to collapse
No, as a matter of fact, I re-downloaded it to be sure the one I had wasn't corrupted somehow. Still, no luck.
epsix said:
So if you flash a lot of RUU ,you must have supercid?
Sent from my HTC Sensation 4G using XDA Premium App
Click to expand...
Click to collapse
I don't believe I do. Tried accomplishing that this morning, but permission denied. I flash many ROMs and add-ons, but have only flashed the original RUU to S-off and root.
Just to update, I activated the superCID from my laptop, no problems. Went with the new ICS RUU, and so far everything is sweet! Going to re-flash my ARHD 5.0.2 and then see what I have.
Well, ICS RUU, re-rooted, clockworkmod re-installed, busybox, and 4EXT. Flashed my ARHD 5.0.2 restore, and now I'm running HBOOT 1.20, Android 4.0.1, and it's all very smooth. Impressed! Apparently, if you get an update fail on your HBOOT, you can solve it by going to the next level, so to speak. Anyone out there have any viable suggestions on how to 'recover' their recovery without having to resort to this, I'm sure it would be good information to have. Otherwise, case closed!
Phone: HTC Sensation
ROM: Revolution HD 5.0.2 ICS
Kernel: Stock
Radio: 11.59.3504.00U_11.16.3504.16_M
BMP7777 said:
Well, ICS RUU, re-rooted, clockworkmod re-installed, busybox, and 4EXT. Flashed my ARHD 5.0.2 restore, and now I'm running HBOOT 1.20, Android 4.0.1, and it's all very smooth. Impressed! Apparently, if you get an update fail on your HBOOT, you can solve it by going to the next level, so to speak. Anyone out there have any viable suggestions on how to 'recover' their recovery without having to resort to this, I'm sure it would be good information to have. Otherwise, case closed!
Phone: HTC Sensation
ROM: Revolution HD 5.0.2 ICS
Kernel: Stock
Radio: 11.59.3504.00U_11.16.3504.16_M
Click to expand...
Click to collapse
Delete PG58 file or pull sd card out
tinky1 said:
Delete PG58 file or pull sd card out
Click to expand...
Click to collapse
Tried both with no success. Even thought about downgrading to utilize an older HBOOT like some recommended. Decided if I had to go 'up' or 'down', I'd rather go up. Glad it worked out well. I saw some had a serious problem with other recent releases. Mike1986 is at the top of his game, so I'm grateful! Long Live ARHD! Just to be fair, RCMix does great work as well, its just an apples and oranges thing I guess. (No disrespect to any other developers, these are the only ones I've used )
UPDATE: The ROM itself is good and obviously has great potential, but I am having quite a few issues. It was suggested that System Tuner Pro would force open CPU 2 and give a boost, but it would not view my system as rooted,even after re-boots and permission fixes. 4EXT would freeze and FC in any operation, as would SD Speed Increase, Set CPU, and even Superuser. Font Installer didn't freeze the way some complained it did, but for me it would go through the required re-boot and have no change. Tried to backup with Clockworkmod (since 4EXT was failing), and the backup failed. SOooooo, in my opinion, it is good at this point for a daily user if you do JUST THAT, use it for common daily functions. But, for me at least, anything having to do with increasing performance or customization creates a problem. Not the end of the world, except that I'm a customization junkie, so its a bit of a deal breaker for me. One thing, a lot of people complained of wallpaper issues and failures; the DIY ownskin I was using had no issues. Then again, the wallpaper for the lockscreen DID fail. Oh well.... I know it'll get better. Restoring back for a while ....Mike 1986, RCMix, and all other hard working devs, keep up the good work, Getting better every day...
The last post was by no means any kind of a critique, I dabble but have no experience at this point as to what it takes to create these works, so I hope no one takes it as such. Just thought I would share my various experiences so others can gauge their own. I think that those who take the time to work these out are very talented and deserve praise regardless of glitches that happen without warning.
HTC Sensation 4G
HBOOT 1.20.1111
Radio 11.59.3504.00U_11.16.3504.16_M
Currently running:
RCMix 3.5 V010
2.3.5 w/ sense 3.5
Bricked XE 2.6.35.14
o/c to 1.78
BMP7777 said:
The last post was by no means any kind of a critique, I dabble but have no experience at this point as to what it takes to create these works, so I hope no one takes it as such. Just thought I would share my various experiences so others can gauge their own. I think that those who take the time to work these out are very talented and deserve praise regardless of glitches that happen without warning.
Click to expand...
Click to collapse
All fair comments. The devs do a great job on here but the sharing of experience and information by non-devs like you and me is also important
I have the same problem with Fail-PU
Hi Guys,
Apologies if this has been discussed before. I have looked for answers everywhere and i could not find any.
Ok, I have a Desire S which is branded to Telstra (Australia), I was sick of all the useless app that Telstra had put in and wanted to get rid of all those.
I used revolutionary method to get it s-off and install Generic Firmware. After that i was happy not having any of Telstra's bloatware on the phone. Then came the update of 2.3.5 and as usual downloaded the firmware and used RRU to Update. Big mistake on my part, i didn't read anything and just tried to push RRU on the phone, the result was White screen with HTC logo and nothing past that. Tried everything no luck, then looking for answers, i found a solution to remove revolutionary, I could see revolutionary gone in HBOOT but the phone would not start.
to solve this i went to telstra to send it to repair, warranty was there and when telstra asked what happened, i said i was updating an app and it went to this screen, Tech guys said this is the similar 3rd problem in a day. so after 5 days the phone got repaired, New IMEI number and logic board had to be replaced.
Now all over again i have bunch of telstra bloatware on the phone. I want to get Generic 2.3.5 with sense 3.0. what is the process to follow so that i don't make the same mistake again?
All i want to do is get it s-off and install generic Firmware, the easiest way possible something like revolutionary. I tried going with ADB but found a bit risky.
Any advice in getting Generic HTC Desire S (2.3.5 with Sense 3.0) the easiest way would be helpful. Thanks in advance.
HBOOT info:
SAGA PVT SHIP s-ON RL
HBOOT-0.98.0002
RADIO-3805.04.02.01_M
eMMC-boot
Mar 30 2011,17:29:31
Thanks
To get a generic firmware from some other area, you need to get Super CID. I don't know much about it, just that CID's like a region code, Super CID enables you to get generic ROMs from any region. Only XTC Clip can do that on a Desire S as far as i know. Flashing a custom ROM after Revolutionary S-OFF is a better option....
Listen, I really recommend you to use a Custom ROM based on the update if you are ready to S-OFF. Hyperion is much faster and has a lot more features. Hell, if you do S-OFF, why settle for Sense 3? Get Sense 3.5. I recommend endymion.
@shrome99: Thanks dude, correct me if i am wrong, to get a generic firmware onto the desire s there is no option but to go for s-off and customs roms are better than stock ones, the reason i am asking is i have not used custom roms and willing to stick to stock.
What is the easiest way to get the rom sorted, I know how to get the custom rom installed there are too many posts everywhere that you can read through and make a decision and find roms of your choice, but there seems to be nothing about stock roms, i am sure there are people who are willing to get stock rom and their carrier is not rolling out the update coz they want more junk to be added.
Steps on how to get generic stock rom would be really helpful.
Thanks again
zryvffn said:
@shrome99: Thanks dude, correct me if i am wrong, to get a generic firmware onto the desire s there is no option but to go for s-off and customs roms are better than stock ones, the reason i am asking is i have not used custom roms and willing to stick to stock.
What is the easiest way to get the rom sorted, I know how to get the custom rom installed there are too many posts everywhere that you can read through and make a decision and find roms of your choice, but there seems to be nothing about stock roms, i am sure there are people who are willing to get stock rom and their carrier is not rolling out the update coz they want more junk to be added.
Steps on how to get generic stock rom would be really helpful.
Thanks again
Click to expand...
Click to collapse
+1 to above
IMO, if you're considering making a change then put on a decent custom (see my sig) you won't regret it
ben_pyett said:
+1 to above
IMO, if you're considering making a change then put on a decent custom (see my sig) you won't regret it
Click to expand...
Click to collapse
Hey Ben, Thanks for this, I went ahead and got the ROM as you suggested. Installed the base verison, then the add-on and the update. I have been palying around with it and so far loving it.
Only problem tough, I cannot use Market. I can open market look for apps and download, but when it starts to install, the phone re-boots. any known issues with this and is there a workaround to sort this out.
Ok, so here is what i did, Flashed Base version again and market started working again with no issues. Another issue which is not so much of an issue but only at night, why does the soft keys don't lit up on Desire S?. any way to fix these. Thanks guys.
Sometimes firing up and signing into Google talk makes the market start working again
Sent from my HTC Desire S using xda premium
sadsac said:
Sometimes firing up and signing into Google talk makes the market start working again
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
Thanks for that, I did a search for the issue and did the same thing as you had advised, but didn't work. Then I flashed the base version again and then the update, which worked. Don't know what had happened there.
But yeah loving the new rom and i would say was a better move to be on a custom ROM and getting rid of Carrier's junk installed.
Cheers!
Ok, so instead of creating a new post i have decided to post it here since it is already been discussed.
I was happy with rooted phone and endymion Rom and was happy until my phone started heating up and restarted on its own as if it had a mind of its own, I called HTC and they advised to send it for repair, i had to unroot the phone and sent for repair. Got the phone back with updated version and i need help rooting the phone.
when i boot the phone in fast boot this is what i get:
****LOCKED****
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.10.08.04_M
eMMC-BOOT
Aug 22 2011, 15:22:13
Android Version 2.3.5
HTC Sense Verison 3.0
Software Number: 2.14.841.4
Baseband Version: 2.14.841.4 CL 184593 Release-Keys
Now i need to Root the phone again so i can be another happy user of endymion.
I am looking at this guide and needed help.
http://forum.xda-developers.com/showthread.php?t=1443636&page=1
The oldest RUU i can find for my provider is RUU_Saga_Telstra_WWE_1.36.841.3_Radio_20.28d.30.0805U_3805.04.02.01_M_release_184558_signed.exe
I was reading the guide and this is where i am confused.
6.This command will gets you out of adb shell.. so we need to get back to adb shell and you will see "#" sign..meaning you are temp rooted and we can then proceed to changing MISC_VERSION:
Code:
adb shell
cd /data/local/tmp
./misc_version -s 1.27.405.6 .
./misc_version -s 1.27.405.6 do i change this to 1.36.841.3 or leave it as it is?
Any help will be greatly appreciated.
Thanks.
IMO you can leave it as it is. 1.27.xxx is older than your RUU version so I think it will work fine.
chninkel said:
IMO you can leave it as it is. 1.27.xxx is older than your RUU version so I think it will work fine.
Click to expand...
Click to collapse
Thanks for that, yes i did follow the guide, and then got stuck again. The problem i am facing is after pushing all the files as of the guide, i run tacoroot the phone restarts and all i get is a red triangle with exclamation mark in it and nothing else happens.
then to get rid of it, i pull out the battery and do a complete factory reset. I have done this about 5 times now but still the same.
Also tried using super one click but that dint work either and freezes on waiting for device.
anything i have missed or is there any other solutions, any GUI programs or video to help if i am missing something.
any help is appreciated.
Thanks
I believe that you have to boot the original recovery before using tacoroot to get it working ( I mean boot it once, then boot normally).
After using tacoroot --root, your phone will probably go in bootloop, don't worry about that and change your misc_version as described in the tutorial.
And please, stop pulling out the battery, you will brick your phone this way.
chninkel said:
And please, stop pulling out the battery, you will brick your phone this way.
Click to expand...
Click to collapse
+1
You can pull it out as often as you want..but at least you should know the risk.
Sent by my fingers to your head
chninkel said:
I believe that you have to boot the original recovery before using tacoroot to get it working ( I mean boot it once, then boot normally).
After using tacoroot --root, your phone will probably go in bootloop, don't worry about that and change your misc_version as described in the tutorial.
And please, stop pulling out the battery, you will brick your phone this way.
Click to expand...
Click to collapse
I don't understand,"boot into original recovery". To try i booted the phone in HBOOT and pressed recovery and same thing the triangle shows. am i missing something here.
EDIT: I went till the last step and this is what i get "Patching and backing up partition 17...
Error Opening backup file.
#"
any idea
zryvffn said:
To try i booted the phone in HBOOT and pressed recovery
Click to expand...
Click to collapse
That's what I meant.
You can try misc_version_universal to avoid error patching partition 17 (see attachment below).
chninkel said:
That's what I meant.
You can try misc_version_universal to avoid error patching partition 17 (see attachment below).
Click to expand...
Click to collapse
Thanks dude, this worked and going thru revolutionary. i did some changes in the steps and will update what i did in a while after i get a rom installed.
Thank you everyone for help and support. i was able to downgrade my HBOOT and install a custom ROM. It would not have been possible if you guys had not supported.
one thing i have learnt is the more you read the more you find things useful and you actually learn how ti weigh your risk and benefits and avoid ending up with an expensive paper weight.
so this is what i did.
after using universal misc version file i was getting 140 error in RUU, boot loader version error, tried 3 time but would not let me get past that, then out of frustration i thought about giving it a last try for good or for worse, in the misc version section i changed a bit.
adb shell
cd /data/local/tmp
./misc_version -s 1.36.841.3 (Same number as my RUU)
then RUU went fine and then revolutionary.
well, if any kind of newbie person in trying to root the phone i would suggest to read and if you think you have read enough, its probably you haven't.
special thanks to @chninkel, @eyahl. Thanks Guys for all the support.
Cheers!
Hey all, I'm sorry if this seems an odd question, but I'm still trying to get my head wrapped around the process of how the One S gets different features flashed to the device.
I don't have my One S yet (Hopefully it'll arrive later today, 7/27) but I wanted to be prepared when it arrives.
It seems the links are broken in this post and it's stating that this thread is outdated.
If I'm going to flash a new ROM on the device, are the radios generally included in that ROM already? I see that you often times need to manually flash BOOT.IMG on a per-ROM basis due to not having s-off? I'm comfortable with all of that, I just want to make sure that I'm not missing anything, and unfortunately it seems as though there is little information in some of the threads on XDA that clearly answer my question.
Call it a personality defect, I just like to 100% understand something in every possible way before being able to attempt it. Unfortunately when I don't have the device in front of me, it prevents me from being able to do that, but that's what forums are for, right?
Cheers all, I appreciate anyone taking the time to answer my question.
TooSlo said:
Hey all, I'm sorry if this seems an odd question, but I'm still trying to get my head wrapped around the process of how the One S gets different features flashed to the device.
I don't have my One S yet (Hopefully it'll arrive later today, 7/27) but I wanted to be prepared when it arrives.
It seems the links are broken in this post and it's stating that this thread is outdated.
If I'm going to flash a new ROM on the device, are the radios generally included in that ROM already? I see that you often times need to manually flash BOOT.IMG on a per-ROM basis due to not having s-off? I'm comfortable with all of that, I just want to make sure that I'm not missing anything, and unfortunately it seems as though there is little information in some of the threads on XDA that clearly answer my question.
Call it a personality defect, I just like to 100% understand something in every possible way before being able to attempt it. Unfortunately when I don't have the device in front of me, it prevents me from being able to do that, but that's what forums are for, right?
Cheers all, I appreciate anyone taking the time to answer my question.
Click to expand...
Click to collapse
The latest radio with android 4.0.4 rom is said to be much better in terms of performace of wifi and cellular data signal then all previous versions, unfortunately buying a phone at this stage means that you probably will have a later hboot version 1.13 and this hboot doesnt allow flashing radio from recovery like the previous versions. You can find out more info about the radio in this thread: http://forum.xda-developers.com/showthread.php?t=1781033
To answer your other question the radio has to be flashed separately from the ROM. Hopefully your phone comes with a lower hboot so flashing wont be a problem, make sure you dont accept the ota update out of the box like i did so u dont accidently get an upgraded hboot. Makes life more diificult ;p.
Its a used phone and is already running CM9, so I'm hoping its the older boot. I already made sure it was the S4, but I just realized that the unlocked phones don't support TMOUS bands, so I'm a bit screwed at the moment.
I don't know what the next step is for me, so I may be forced to move to Straight Talk until I can get another 100% compatible TMOUS phone. I saw it has 2100 HSPA radio frequencies so I had assumed it would work on TMOUS. Needless to say I feel pretty stupid now.
Thanks again for the links, they were exactly what I was looking for!
Sent from my MB860 using Tapatalk 2
just boot into bootloader it will tell you hboot. i think .06 is stock one
there are radio links here .10 latest for us--if you want 4.0.4 one--research needed
http://ville.giev.de/?page_id=42
flash thru twrp or if cwr you must boot into recovery thru fastboot then flash
Radio from 4.04 update and hboot 1.13
rugmankc said:
just boot into bootloader it will tell you hboot. i think .06 is stock one
there are radio links here .10 latest for us--if you want 4.0.4 one--research needed
http://ville.giev.de/?page_id=42
flash thru twrp or if cwr you must boot into recovery thru fastboot then flash
Click to expand...
Click to collapse
Sorry for putting this question another time, but the answers concerning this are treated in a lot of different threads, just to confirm:
I am on Leedroid 2.1, Radio Version 0.1631501S.17_2_10.23.31501S.10L; i have Hboot 1.13,
I there a possibility for me to flash this new radio radio from update 4.04??
Regards, Dwino
Dwino said:
Sorry for putting this question another time, but the answers concerning this are treated in a lot of different threads, just to confirm:
I am on Leedroid 2.1, Radio Version 0.1631501S.17_2_10.23.31501S.10L; i have Hboot 1.13,
I there a possibility for me to flash this new radio radio from update 4.04??
Regards, Dwino
Click to expand...
Click to collapse
If you want to get this new radio, the only way to do it at this moment is to change to SuperCID and follow the steps from this thread http://forum.xda-developers.com/showthread.php?t=1781033
Hi, please let me know if this should me moved to another section.
I am coming from Samsung phones, and building and installing ROMs for them. I got an HTC A9 a while back and I am having cyanogenmod withdrawals lol. I have the Sprint model so there doesn't seem to be any compatible builds, please let me know if I am wrong.
So basically I am breaking my dev shoes back out and going to attempt to build a CM ROM for the Sprint A9, but some things around still confuse me for HTC. I already have S-Off and unlocked bootloader, running a rooted stock image. But I am not sure I fully understand this RUU stuff? Also, if anyone else could fill in the blanks for me regarding differences between working with samsung vs htc. I already know you can't use Odin, that was one thing I really hated about samsung anyway, I am far more comfortable using fastboot lol. But any advice would be appreciated.
Thanks!
miked63017 said:
Hi, please let me know if this should me moved to another section.
I am coming from Samsung phones, and building and installing ROMs for them. I got an HTC A9 a while back and I am having cyanogenmod withdrawals lol. I have the Sprint model so there doesn't seem to be any compatible builds, please let me know if I am wrong.
So basically I am breaking my dev shoes back out and going to attempt to build a CM ROM for the Sprint A9, but some things around still confuse me for HTC. I already have S-Off and unlocked bootloader, running a rooted stock image. But I am not sure I fully understand this RUU stuff? Also, if anyone else could fill in the blanks for me regarding differences between working with samsung vs htc. I already know you can't use Odin, that was one thing I really hated about samsung anyway, I am far more comfortable using fastboot lol. But any advice would be appreciated.
Thanks!
Click to expand...
Click to collapse
I don't know much about the differences between dev'ing for HTC/Samsung, but an R.U.U is a Rom Update Utility, it includes 100% stock Rom, firmware, radios, etc. Flashing it will wipe ALL data on device (internal/SD card ) as well, so back Up any saved pics/data
Sent from my HTC One A9 using XDA Labs
So I got a flashable CM image, but it boot loops and I think I need to work on the kernel since I was using the one from hiaeul and I need hiaewhl. I pulled the sources from HTC and will start on that, but I have a question. Does anybody know what causes the "This build is for development purposes only" message?
I don't have the message on the stock rooted rom, but the message popped up after flashing CM, and coincidentally is where it bootloops at. I thought this pops up once you unlock the bootloader, but I haven't seen it until now.
miked63017 said:
So I got a flashable CM image, but it boot loops and I think I need to work on the kernel since I was using the one from hiaeul and I need hiaewhl. I pulled the sources from HTC and will start on that, but I have a question. Does anybody know what causes the "This build is for development purposes only" message?
I don't have the message on the stock rooted rom, but the message popped up after flashing CM, and coincidentally is where it bootloops at. I thought this pops up once you unlock the bootloader, but I haven't seen it until now.
Click to expand...
Click to collapse
It's built into the hboot/boot loader. Only way to change it is to hex edit the boot, which is risky. All HTC phones get that red msg after flashing (I forget exactly what causes it, I think custom boot.img, kernel, or something like that)
Sent from my HTC One A9 using XDA Labs
I could be wrong...but i remember only getting that red message about build being dev purposes only...when i was flashing or attempting to flash a different firmware meant originally for international handset versions after changing my CID/MID. It has been awhile since those days when i first got the A9 and nearly bricked it but i think that was the cause. If so, perhaps its the boot or kernel that is the issue? I also came from Samsung to HTC and it was quite the learning curve. ONly differences ive seen is...well...everything lol. Using RUUs, flashing via fastboot/adb sans odin, encryption of the internal memory, S-on/S-off and unlocking the bootloader. I am sure you know all these as well lol but just mean in general its a real b*tch working with this handset and it is picky on little things like specific order of events like flashing order......if you have several things to flash ive seen it mess up from just one part out of sequence when flashing. Anyhoo, still pretty new on a lot myself so I could be off but its what ive experienced so far. Good luck though and Ill be looking out your results for sure.
P.S - I also have sprint so I posted these elsewhere since no one else really looks out for our version much haha and you may need these for some reason later.
Sprint 1.60.651.4
http://www.mediafire.com/download/ki...1.60.651.4.exe
also
http://www.mediafire.com/download/d5...1/firmware.zip - for the Firmware zip to be flashed via RUU mode
System/recovery/boot images for stock are below:
http://www.mediafire.com/download/xe...zfh3x/boot.img
http://www.mediafire.com/download/oa...p/recovery.img
http://www.mediafire.com/download/48...g7j/system.img
mcbright80 said:
P.S - I also have sprint so I posted these elsewhere since no one else really looks out for our version much haha and you may need these for some reason later.
Sprint 1.60.651.4
http://www.mediafire.com/download/ki...1.60.651.4.exe
also
http://www.mediafire.com/download/d5...1/firmware.zip - for the Firmware zip to be flashed via RUU mode
System/recovery/boot images for stock are below:
http://www.mediafire.com/download/xe...zfh3x/boot.img
http://www.mediafire.com/download/oa...p/recovery.img
http://www.mediafire.com/download/48...g7j/system.img
Click to expand...
Click to collapse
Psst, none of your links are working. Looks like Mediafire deleted them.
help htc one a9
I recently updated my HTC One A9 to the new Marshmallow 6.01 version and now the wifi does not work at all (missing wifi module (8)) and the battery is at 4000%. My software number is 1.56.709.70, i believe this is the taiwan variant but it is unlocked. How do I fix this? Please help, do I flash an ruu or something? How do I know which ruu works for this phone?
JohnRogers23 said:
Psst, none of your links are working. Looks like Mediafire deleted them.
Click to expand...
Click to collapse
Ah damn! Ok ill upload them elsewhere...
JohnRogers23 said:
Psst, none of your links are working. Looks like Mediafire deleted them.
Click to expand...
Click to collapse
NEW LINK to Sprint 1.60.651.4
https://1drv.ms/f/s!AtVcVcbLOGTdgP9-e2NAN2fNHHIKVQ