Flashed Incompatible Rom Over Old Firmware - S-ON - HTC One A9

Details:
kernel: lk
product: htc_hiaeul
version: 1.0
imei: 352637070568673
version-main: 1.10.502.3
boot-mode: download
version-baseband: [email protected]
version-bootloader: 1.0.0.0000
mid: 2PQ912000
cid: CWS__001
I flashed a rom which depends on a newer firmware than the one my A9 is on, I had no idea about s-on or how it affected or limited flashing roms or firmware upgrades and downgrades, but now I do.
My only choice here is to flash the exact same firmware that the phone has right now or newer, with a matching CID. There is only one, 1.27.502.5 that I found the .exe for, but it takes a long time to open and when it does always fails to recognize my device and I definitely have all of the right drivers installed.
The zip which I have found mentioned on here several times over for my exact firmware version I am unable to download because Android File Host has such horrible download speeds, I haven't made it past 146mb before the file corrupts and marks itself as complete and I've tried for hours, many different methods to only reach the same outcome. Its very frustrating that the only mirror available is from California (I'm in Florida) but that despite still being located in the US, it doesn't break 600kbps for the greater duration of any attempts to wait it out.
Had I known about this limitation, I would have never bought this phone, but I've always wanted an HTC and thoroughly enjoyed it until now. It has cost me many hours but I have given them willingly, despite my inexperience about this subject or the processes involved.
If anyone can help me out with a mirror to this firmware (1.10.502.3) in zip format, I would be so grateful. If anyone has any suggestions besides recommending that I pay for sunshine, then converting my phone to a developer version, because I'm barely able to afford my rent as it is it would be so appreciated!

Related

[Q] Legend de-brand Firmware help please :-)

Hi, being an almost total novice i need a little help!
I seem to have hit a brick wall while attemping to de-brand my UK Vodaphone branded HTC Legend!
I just tried with two with different goldcards and three different ROM files (thats six seperate attempts)
each time it failed the same way: ERROR [140]: BOOTLOADER VERSION ERROR
If anyone can offer any advice I would be very gratefull - I really need to get rid of all the Vodaphone bloatware that doesnt even work properly.
BTW - I made a new Goldcard each time but can a goldcard be used more than once?
I created a goldcard using a 2gb MicroSD card made by Kingston and i followed the process at:
How To: Create a Goldcard | TheUnlockr
I downloaded file:
RUU_Legend_HTC_WWE_2.03.405.3_Radio_47.39.35.09_7. 08.35.21_release_130330_signed.exe from Index of /shipped/Legend/
I turned my phone on with the goldcard inserted and connected my phone to my PC with the USB cable and ran the RUU - Result =
ERROR [140]: BOOTLOADER VERSION ERROR
Here are all the numbers from my HTC Legend
Information from: Menu -> Settings -? About Phone -> Software Information
Firmware Version: 2.1 update 1
Baseband Version: 47.39.35.09u_7.08.35.21
Kernel Version: 2.6.29-5f084974 [email protected]#1
Build Number: 2.05.161.1 CL191838 release-keys
Software Number: 2.05.161.1
Browser version: Webkit 3.1
When I start the device by pressing vol down + power button I get the information below:
LEGEND UNKNOWN SHIP S-ON
HBOOT-0.43.0001
MICROP-0816
TOUCH PANEL-SYN07_0105
RADIO-7.08.35.21
Feb 18 2010,16:29:10
Any suggestions would be greatly appreciated.
So far I have tried to load the following RUU files - they all failed with the same error!
RUU_Legend_HTC_WWE_1.23.405.1_Radio_47.26.35.04_7. 05.35.26L_release_120393_signed.exe
RUU_Legend_HTC_WWE_1.31.405.4_R_Radio_47.26.35.04_ 7.05.35.26L_release_123853_signed.exe
RUU_Legend_HTC_WWE_1.31.405.5_R_Radio_47.26.35.04_ 7.05.35.26L_release_126592_signed.exe
RUU_Legend_HTC_WWE_2.03.405.3_Radio_47.39.35.09_7. 08.35.21_release_130330_signed.exe
:-((
I guess I am missing something, can anyone point me in the right direction?

First timer rooted my EVO phone now have all kinds of problems. Expert advice needed!

My friend did not have time to root my phone and simply told me to follow some directions and it ended up messing up my EVO 4G. I was working on getting revolutionary and something got messed up. I then tried to put on Cyanogenmod and it worked extremely quirky.
We ended up putting several ROMs on it and they all made it constantly bootloop.
Eventually I found a way to get it to its stock RUU rom and it still messes up. I am in constant roaming with Verizon which doesn't allow me to get service most places I go. So basically my phone is useless as a phone.
Also, certain areas of my phone screen when pressed does not work. For instance i cannot ever type the letter "s" or even activate the text box to put in names for new contacts.
Anybody know how I can get it back to using Sprint towers with no roaming and to be able to enter in all numbers and letters entry via keyboard and text etc? I basically want it to be completely stock and downloading the RUU stock ROM didn't do it all they way unfortunately.
I would eventually like to get FRESH ROM installed after I get this figured out so anybody with good directions or tutorials please share!
**********EVO 4G ***************
Model #: PC36100
MEID: A1000017FFE46B
IMSI: 31000913568291
HARDWARE VERSION: 0004
ANDROID VERSION: 2.2
BASEBAND VERSION: 2.15.00.11.19
KERNEL VERSION: 2.6.32.17
BUILD #: 3.70.651.1
BROWSER VERSION: 3.1
PRI VERSION: 2.15_003
PRL VERSION: 60690

[Q] flakey data connection after cyanogenmod rom flash

So I finally took the jump and rooted my T-mobile Sensation 4G (including unlocking the bootloader, sim-unlock, S-OFF, root, SuperCID, did I forget anything??). Flashed Cyanogenmod 9.1. Have CWM ROM Manager installed, and Titanium backup.
It works MUCH better than the stock ROM, and I'm very happy with it, EXCEPT, the radio's data connection (very fast when working) stops working for hours at a time. There does not seem to be any trigger for this. The regular non-data connection (phone calls and texts) continues to work. The H by the signal strength indicator will flash on periodically, maybe every few to 10 seconds at best, but you never actually get a connection. (3D and E do not appear at all). The signal strength is full. This happens both at home and out.
I thought it might be the radio, and after looking into that, decided to flash some new firmware. Initially (after the rooting/update), it was reporting firmware (from fastboot getvar version-main) of 1.24.401.1. On the boot screen, it said Juopunutbear (I used that method to get S-off). It was reporting baseband of 11.69A...
So I flashed the 3.33 universal firmware, and used the GetRIL app to update the RIL. It now reported firmware 3.33.401.106 and baseband 11.76A...
But no difference in data connection - not working at all.
So I flashed the 3.32 stock TMO firmware, used GetRIL again to get the right RIL. Now reporting firmware 3.32.531.14 and baseband 11.69A again.
But again, no dice on the data connection.
Wifi connection works fine, so I use that when in range.
Other current info:
bootloader screen:
HBOOT 1.27.1100 (this went down from 1.27.1111 version, which I think the HTC bootloader unlock installed).
Radio 11.23.3504.07_M2
eMMC-boot
firmware version:
3.32.531.14
From the running phone itself:
Android version: 4.0.4
baseband: 11.69A.3504.00U_11.23.3504.07_M2
kernel: 3.0.36-g7290c7f
Cyanogenmod version: 9.1.0-pyramid
The one thing I have not tried is to flash a different ROM than the Cyanogen...worth trying (any recommendations?) or another other ideas of what might be going on?
thanks!

[Completed] HTC One M8 DEAD after successful RUU Flash

So I had accidentally flashed a T-Mobile radio to my Sprint device. I got it back on a Sense ROM and flashed via RUU the stock rooted firmware. Everything was going great. Fastboot reboot and a black screen. No response from any buttons. No charging light-NADA NOTHING ZIP ZILCH Device not recognized by windows now. Is showing up on my device manager as a QHSUB_BULK and makes my computer see it for about 3 seconds then it is not visible to windows then just keeps repeating this over and over and over... Is this able to be fixed or is it a nice expensive paper weight to add to my collection? ( I probably have at least 30 phone bricked, broken, destroyed and one that caught fire LOL) I have read a few posts pointing at a bad motherboard? If this is the case where can I get one for not the same price as a new phone? If this can be fixed, any one know how? Maybe later I will post my Cell phone JUNKYARD of Used and scrapped phone parts. LOL I even have old motorola Huge back pack stuff from when A cell phone and service cost as much as a economy car and weighed about the same. Basically a Army Radio for the rich. We sure have come a long way. Oh I forgot its a HK if that makes a diffrence?
M8_WHL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.09.20.0209
OpenDSP-v56.2.2-00564-M8974_HM.1212
OS-4.25.654.14
eMMC-boot 2048MB
Mar 18 2015,12:45:47.7928
MEID Hex:xxxxxxxxxxx
SN:xxxxxxxxxx
MB:41X3544H15632
MEID Dec:xxxxxxxxxxxxxxxx
Image CRC
rpm: 0x68A7FB02
sbl1: 0xE3DB0B9A
sbl2: 0x0
sbl3: 0x0
tz: 0x6F642CFB
radio: 0x266896CF
hboot: 0xFC7816A3
boot: 0xF4FDF762
recovery: 0x20A216E0
system: 0x9A1EFAB0
Recovery TWRP v2.8.1.0
Hardware version 0005
Model number 831c
IMEI xxxxxxxxxxxxxx
IMSI xxxxxxxxxxxxxxx
wi-fi MAC 00:ee:bd:ba:6f:e9
Android version 4.4.2
HTC sense version 6.0
HTC SDK API level 6.17
Baseband version 1.09.20.0209
Build number 1.54.651.8 CL326598 RELEASE-KEYS
PRI Version 2.62_003
PRL 51104
Kernel 3.4.0--master+
SMP PREEMPT
Mobile network type EvDo-rev-A
TWRP version 2.8.1.0
:crying:
This is a expensive brick if so.....
Hi there,
You'd be best served asking for help from the experts who own your device here:
Sprint One (M8) Q&A, Help & Troubleshooting
Good luck

XT1548 "Failed to Validate Carrier Image"

So I don't even know where to begin with this XT1548 that refuses to flash. We've had the phone for over a year and while we think it did boot then, something happened along the way that left it in a non-booting state, and it's been this way for so long that neither of us remember what the original problem that got us here even was, or exactly what all has been tried since then. The situation as of now is that it only goes to the "Software Repair Assistant" screen (no recovery either) and seemingly no stock ROM available will flash. And here's the kicker - we're not even sure what carrier this phone is *supposed* to be. (We've had a loooooooot of phones in and out of here, it's easier to lose track than you'd think, heh). I think what's happened is that bits and pieces of the ROM are mixed up - a 5.1 RW here, a 6.0.1 USCC there - and now it's as confused as we are. But there has to be a way to fix this, right?
So I'll start with what the Fastboot screen shows, and see if that information is of any use
AP Fastboot Flash Mode (Secure)
BL: 80.C1 (sha-af65d85, 2015-07-31 11:05:06)
Baseband: M8916_2020614.27.03.21.36R OSPREY_REPUB_CDMA_CUST
Product/Variant: osprey XT1548 16GB P2B
Serial Number: ZY222WVNR6
CPU: MSM8916
eMMC: 16GB Samsung RV=07 PV=01 TY=57
DRAM: 1024MB Samsung S8 SDRAM DIE=4Gb
Console [NULL]: null
Device is LOCKED. Status Code: 0
Software status: Official
Click to expand...
Click to collapse
Now, you'd think based on what you can see there that this should be the Republic Wireless variant, and going by the errors I get, one would think I was attempting to downgrade from 6 to a LP ROM... but if this is a RW phone, then that's not even possible - there's only one RW ROM around and it's LP. So I must really be looking at a Sprint or USCC model that's been incorrectly flashed right? ...Except I can't flash the LP or MM ROMs from those carriers either. I can flash everything from the Sprint/USC MM ROMs except boot, recovery and system without issue, but no amount of different flash attempts or different flash orders seems to work.
So what *can* I do? Any ideas? Thanks.

Categories

Resources