Related
I have a xda to repair.
problem is that the radio stack upgrade failed.
i have installed the pcc2003 rom wich lets me boot into windows
(ppc2002 roms dont allow this. They seem to wait on the gsm to turn on)
now i could install the radio update. each update fails (latest series)
i know from way back that the older radio updates had a different radio update procedure. I also know i fixed a lot of radio update errors with the old update
where can i find old radio updates?
older then Radio_Unit_Upgrade_v31703.exe
Let me know if you find it, I need it also, I found the stack previous to 4.21 but it gets to 1% and fails.
have a look here
http://www.sourceo2.com/O2_Developers/Devices/O2_Xda/xda_ROM_Archive.htm
Radio_Stack_Upgrade_V416.exe.exe
i tried this one already
it is an older version, you have to press start to start the radio update
newer ones start directly
i think we still need a little older
Read until post 4#
Ive tried to download a rom, and i used its update tool and used mine nk.nbf, but when i click upgrade, i get the error "Error [238]: File read"
I have a G4 device - Cid unlocked
Now rom: Touch no evil (Lang: English)
Required: Normal WM5 rom (Lang: Danish)
What to do
Go to your phone's service provider website. You will find the latest update there.
It will probably be older (like, last year sometime), but it should be a single (albiet large) executable. No need for additional software, and you can remove the CID unlock, because it won't care.
If your Service Provider doesn't have it, you can download the Cingular 8125 ROM here: http://www.america.htc.com/support/8125/software-downloads.html
The TMobile MDA ROM is here: http://www.t-mobile.com/wmupgrade/
I'm sure you can find it. Use Google. Don't be lazy.
I have already downloaded the rom i want (Yes, from my provider).
But i cant update with it because it says "Invalid update tool" (I did it before)
So when i try to use another update tool it gives me an error reading the file
Remove the CID unlock. It may be hindering the default ROM from loading (it's a a crap-shoot, but it's worth a try...)
What actually is the status of your phone ? is it working normally ? what do you exactly mean by CID unlocked ? cuz a G4 device cannot be CID unlocked.Have you got it 'SoftSPL or HardSPL' ? which Rom exactly you are trying to upgrade with ?, Post your present IPL/SPL...? here,to determine the status of your phone,in order to provide you with any advise or suggestion,if you have downloaded latest official carrier's rom from it's website,there shudn't be any problem upgrading with,ok
Cheers !
Hi XDA,
i'm experiencing a not very cool no-update
I just go to the check OS update screen on my G2 and I can see a "Android Update 1.5" (4.2Mb)
I push the download button, it DL well and ... I can't install it ! The Download button is here again with the "Android Update 1.5" (Reboot required but the reboot actually does nothing)
I root my G2, but don't know if it's the reason of this
The very not cool part is that my version is CRB17 ... So the update isn't done !
Please help me, Donut is coming !
Is this a new update released today?
No it's an old one ...
No one had this problem before ?
Hard reset doesn't resolve the problem, stills stuck on displaying "Android Update 1.5" 4.2Mb, the phone doesn't ask me to install after I download it
Update Problem
I have this exact same problem on my rooted UK Voda Magic. No solution but one question. How do you know the update has not been applied you referred to the CRB17 number, my build number is exactly the same but the firmware version reads as 1.5. What is the latest build number????
The FW is firmed with releasekeys and if you flashed a custom recovery it won't accept it.
Cant Update
Any way around this particular problem? Does this also mean when donut is released we will be unable to update through the "update feature" on the phone?
So nobody has any suggestions, is there another recovery version which we could flash that would allow updates? Or maybe un root update and re root? I am assuming this problem will prevent me from updating to 1.6 when it is released.
I recently bought a used Verizon HTC Trophy. I registered it on Verizon and it works fine, both voice and data.
I suspect it may have been a developer phone. If it is I don't mind, but I do mind that I cannot update it using Zune. It keeps telling me that an Update is available (Mango), but when I try to update via Zune it fails with error 80180048.
The phone particulars are as follows:
OS version 7.0.7403.0
Firmware revision number 2305.06.10310.605
Hardware revision number 0003
Radio software version 1.52.00.01.16_23.13w.05.06U
Radio hardware version 3.2.3.D4
Bootloader version 1.3.230506.10
Chip SOC 2.3.0.5.6
The phone also has the following apps installed, which is why I think it may be a developer device.
zGestureBester
zSensorView
zServiceTools
zStartKIGL
Finally, when I turn the phone on it shows the bootloader version and the modem version in the uper left corner of the HTC splash screen.
I am wondering if the bootloader version (or firmware version) is keeping me from upgrading. I took a look around the internet and did not see any references to the .10 version of the bootloader, but I did see post which mentioned that the wrong bootloader can mess up Zune updates.
My preference would be to revert to a simple consumer phone, but at a minimum I'd at least like to be able to get the Mango and HTC radio updates onto the phone. Any suggestions would me much appreciated, and sorry for the noob post.
Thanks
Edit: I worked out my issues, I'll leave this here in case others have similar trouble:
I needed to manually add in the RAW F53XX files from the github (https://github.com/Androxyde/devices/tree/master/F53XX), this allowed Flashtool to correctly detect the type of phone and apply the fsc. I was then able to flash my desired firmware, I chose the 6.0.1 release for Journalists to begin with as a test. This confirmed my suspicion that it was a software update issue causing the proximity sensor to malfunction (stuck on) and also fixed up the FACTORY STARTUP SERVICE-POWER OFF bug and the Warrantytimeservice permanent notification. I can now look at updating to later versions of Android and find the latest version before I have issues again.
---
tl;dr - I need a guide that actually works on downgrading the F5321 to a specific stock Android version with a locked bootloader.
I recently received a new, old stock version of the X Compact (F5321) that appears to be a HK variant as it started up with the Chinese language selected.
It was initially stock Android 6.0.1 with no apparent problems. After OTA updating all the way through to 7.1.x and onward to the latest 8.0, I now receive the "FACTORY STARTUP SERVICE" problem. Even if I'm quick enough to disable the service for the service flag, the proximity sensor does not work as well after updating, making phone calls impossible. I believe the issue is all related to software, not hardware. I want to downgrade to 6.x and go from there before I have to send it back for another replacement.
I'm having trouble with getting Flashtool to correctly detect and identify the firmware files that I want to flash. I want a completely stock version of Android, so keeping the bootloader locked is fine for me.
After downloading the firmware that I want to try, XperiFirm will close and Flashtool will successfully build the FTF. After clicking the lightning bolt > flashmode > the firmware list is blank.
I'm using Flashtool 0.9.26 (I have tried older versions as well with the same problems) with driver signature enforcement disabled and correct drivers installed to detect the phone.
The last time I used Flashtool was to flash my older Z5 Compact, I didn't have any issues then and it was all done within 10 minutes. I've already spent more than 5 hours on this phone and would appreciate any help.
I seem to have the exact same problem with a Hong Kong-sourced X Compact. I am familiar with Flashtool, and have used it for basic flashing of firmware. This time, however, I am experiencing the dreaded "FACTORY STARTUP SERVICE" problem. Was wondering if Flashtool could be used to circumvent the problem. I simply want the USA Android 8.0 firmware on the phone. I am not familiar with the various options that Flashtool offers. I note that you mention a specific script(?) that can be installed. Do you have any advice? Thanks
pseudonym58 said:
I seem to have the exact same problem with a Hong Kong-sourced X Compact. I am familiar with Flashtool, and have used it for basic flashing of firmware. This time, however, I am experiencing the dreaded "FACTORY STARTUP SERVICE" problem. Was wondering if Flashtool could be used to circumvent the problem. I simply want the USA Android 8.0 firmware on the phone. I am not familiar with the various options that Flashtool offers. I note that you mention a specific script(?) that can be installed. Do you have any advice? Thanks
Click to expand...
Click to collapse
The "FACTORY STARTUP SERVICE" and to a lesser extent, "Warrantytimeservice" problems surface only in the later version of Android. The only way I could remove them was by staying on 6.0.x only. Anything higher, and the problems show up again. It seems to be a byproduct of upgrading the HK variant that wasn't designed to actually be software upgraded - you won't be able to have the US 8.x firmware on the phone.
Sorry to say, but you'll be stuck on 6.0.x if you want a usable phone. I should mention that I was never able to maintain a newer firmware on that particular phone.
I've since sent the Compact X back (it was meant to be a gift) and replaced it with a Samsung A20.
h
I'm using SO-O2J and a sim card not docomo. Use the "Repair" in Xperia Companion and it auto flash Android 7.0
..
PioneerSeeker said:
Try different region's roms on www.xperiablog.net and I hope you'll be successful to find nougat or oreo at last for your phone.
Remember xperia devices do not need to unlock bootloader for downgrade...
Click to expand...
Click to collapse
Thanks; I was able to obtain an X Compact originally for the UK market, and was able to successfully flash the US Oreo firmware. All seems to be in order.