Develop Bugs

new bootloader for jasjar v1.1

hi
tray it
http://forum.xda-developers.com/download.php?id=11271

BL 1.1 JJ
Any advantage to BL 1.0 ?
Cheers
hrb

just my 2 cents on the "updating bootloader issue":
i suggest (for people owning sim-locked universals) not to update bootloader before there is a working method for unlocking them as the sim-lock is closely linked to the bootloader. buzz mentioned he is able to unlock universals having bootloader <1.00 installed (not by an easy automatic and comfortable procedure, still manually but possible). but you never know what is included in an updated bootloader and what maybe prevents your device from getting unlocked successfully.
i personally collect and keep those new bootloaders on my harddisk but i do not update the device and stay with mine (unfortunately v1.00) until the "brick" is unlocked.
regards
peter
ps: if you never plan to unlock your device by a great software tool from any of our developers here, just don't care about my writing ;-)

I think the devise is faster now and more stabel than befor

alisultan said:
I think the devise is faster now and more stabel than befor
Click to expand...
Click to collapse
Do you mean the the startup process (e.g. softreset) ?
I can't imagine, that the BL is active during normal operation.
But maybe I am wrong.
Cheers
hrb

I have some questions before I upgrade...
Will it recover my Jasjar to come out of coma (flash screen)?
Do I lose my warranty?
Is there any way to downgrade to v0.6?
THanks for your help guys :wink:

hrb said:
alisultan said:
I think the devise is faster now and more stabel than befor
Click to expand...
Click to collapse
Do you mean the the startup process (e.g. softreset) ?
I can't imagine, that the BL is active during normal operation.
But maybe I am wrong.
Cheers
hrb
Click to expand...
Click to collapse
yes it's faster after softrest and i notice that the operating system is more stable now

shaytaan said:
I have some questions before I upgrade...
Will it recover my Jasjar to come out of coma (flash screen)?
Do I lose my warranty?
Is there any way to downgrade to v0.6?
THanks for your help guys :wink:
Click to expand...
Click to collapse
for the firest question you have to try but firest remove the sd card, fore the warranty i don't think so,downgrade to v0.6 i didn't try if you have it ubload it hear and i will try

Does upgrading the Bootloader need a hard reset ??I mean do I have to reinstall everything after I update the bootloader?
Also I have previously downloaded somewhere her the following file: BL10_RUU_UNI_V11.exe is that Version 1.0 or 1.1
this file here is jasjar_bl1.01_ruu_v1.2.exe which is that 1.01.or.version 1.2
I am a bit confused as you see, Any help will be appreciated

No hard-reset needed!
To be honest, I came from 0.6 and see no difference in speed, booting up of whatever.

alfamini said:
No hard-reset needed!
To be honest, I came from 0.6 and see no difference in speed, booting up of whatever.
Click to expand...
Click to collapse
Same for me
Cheers
hrb

After I upgraded my jasjar with the new 1.1 bootloader my jasjar boots in 3 seconds!!!!---------plus 20 lol There is no speed difference. But the new boot loader seems that there may be a hint of a major os update in the future. Going from .6 to 1.1 is just insane.
Mike

problems upgraging rom after installing bl 1.01
hi all,ive just installed bl 1.01 and now cant seem to install any other roms apart from o2?.before i had 1.00 and could use any rom with maupdate etc.now that doesnt work,it says its flashed it but hasnt?has anyone else had the same problem with the new bootloader,i cant even dowgrade the damn bootloader back to 1.00.bugger cause i wanted to try the imate rom.any ideas?

Downgrade BL
How to downgrade from v1.01?
thanx

Problem. I was use this new bootloader, but before finish a see the Connection error. But now i my universal deat. I cant enter into bootloader, i cant do hardreset... only if I hold the two softkeys and use softreset, then see the displej with "press 0 to MR or X to continue". But 0 and X now has no effect.
Please help, thanks for any solutions !

jerrry said:
Problem. I was use this new bootloader, but before finish a see the Connection error. But now i my universal deat. I cant enter into bootloader, i cant do hardreset... only if I hold the two softkeys and use softreset, then see the displej with "press 0 to MR or X to continue". But 0 and X now has no effect.
Please help, thanks for any solutions !
Click to expand...
Click to collapse
Please read this http://forum.xda-developers.com/showthread.php?t=259003
You get one of the problem posted there!

ufff
thank you. Flashed and works...

How ?
How to flashed bootloader ?
Thanks !!

I got my Qtek 9000 back from repair (stuck in splash screen) and I now find version 2.01 of the bootloader on the machine. This then seems to be the latest.

I bought my new JasJar a week ago and it has Bootloader V2.01 on it just as an FYI =0)

Radio 1.18 Update

Hi All,
Radio Upgrade Version 1.18 now available.
The only fixes/tweaks I am aware of over 1.15 are fixes to roaming.
I have been using for three weeks now and don't notice any difference over 1.15 par slightly better UMTS signal at home (poor coverage in my area)
NBF only download.
For those that don't know the process to update, read here http://wiki.xda-developers.com/index.php?pagename=UNI_Radio
http://rapidshare.com/files/44169648/radio_1.18.rar.html
cktlcmd said:
Here is an alternate download site: http://www.megaupload.com/?d=UTNWU68C
---
Click to expand...
Click to collapse
Thanks for the mirror Cktlcmd!
Cheers,
Beast

beast0898 said:
Hi All,
Radio Upgrade Version 1.18 now available.
The only fixes/tweaks I am aware of over 1.15 are fixes to roaming.
I have been using for three weeks now and don't notice any difference over 1.15 par slightly better UMTS signal at home (poor coverage in my area)
NBF only download.
http://rapidshare.com/files/44169648/radio_1.18.rar.html
Cheers,
Beast
Click to expand...
Click to collapse
Thanks very much.
Where did you get this from or what manufacturer released this? IMate, Orange, TMobile, etc...????
Is this an official radio ROM or customized by someone???
---

cktlcmd said:
Thanks very much.
Where did you get this from or what manufacturer released this? IMate, Orange, TMobile, etc...????
Is this an official radio ROM or customized by someone???
---
Click to expand...
Click to collapse
Cannot reveal the source, only that it is a very reliable source, and the stack is safe and fine for use.
Cheers,
Beast

hmm possible to upload in megaupload too?? rapidshare seems problem from the place im fowloading from

beast0898 said:
Cannot reveal the source, only that it is a very reliable source, and the stack is safe and fine for use.
Cheers,
Beast
Click to expand...
Click to collapse
I assume probably OFFICIAL??? Does this mean we are to see a new OFFICIAL ROM???
and thanks for sharing...
---

Alternate Dowload Site Radio 1.18.00
Here is an alternate download site: http://www.megaupload.com/?d=UTNWU68C
---

1.15 gives me a No GSM, so I think I'll stay at 1.09.

anyone upgraded?

omega_ said:
anyone upgraded?
Click to expand...
Click to collapse
Both myslef and Laurentius have been using for some weeks without any noticeable difference over 1.15.
cktlcmd said:
I assume probably OFFICIAL??? Does this mean we are to see a new OFFICIAL ROM???
and thanks for sharing...
---
Click to expand...
Click to collapse
Nope you won't be seeing any official Rom upgrade for the Uni (Not for WM6 anyway) and I doubt very much there will be any more WM5 releases, it's far too old and providers have moved on, there is no economic beneift for them to do any more work on the Universals.
Cheers,
Beast

I will stick to 1.15, the most stable ROM for me for now.
Thanks beast0898 for your prompt answer.

I wasn't expecting ROMUpgradeUt to hard reset my device after this upgrade, have always used MaUpgradeUt_noID before... At least I have a 1-month old SPB backup image
As for radio 1.18, this seems fine - no problems with 3G calls or internet use. I haven't noticed any difference from 1.15, but like many here I like to be on the bleeding edge of updates
Many thanks to beast for bringing this to us, you are the best!

what? ROMUpgradeUt hard resetted your device?
thats wierd. it did that without asking?
anyone else had this?
im about to flash myself. i guess i'll use the old no_id flash util...

I flashed mine using the NO ID Tool. Have been using that proceedure ever since it was released and no problems with it. Mine did not hard reset.
---

cktlcmd said:
I flashed mine using the NO ID Tool. Have been using that proceedure ever since it was released and no problems with it. Mine did not hard reset.
---
Click to expand...
Click to collapse
I'm not sure where the NoID tool resides... I see in some other ROM folders a "MaUpgradeUT_noID.exe" and a "ROMUpgradeUt.exe". If I take one of those older ROM files, replace the radio_.nbf file with the one from 1.18, and run the MaUpgradeUT_noID executable (without any ms_.nbf and nk.nbf files in the folder), will that result in the NoID radio upgrade method without the hard reset?
Sorry to ask, just that the Radio Only upgrade section of the wiki shows only an upgrade method using the ROMUpgradeUT method, I want to avoid screwing this up.
http://wiki.xda-developers.com/index.php?pagename=UNI_Radio

galt said:
I'm not sure where the NoID tool resides... I see in some other ROM folders a "MaUpgradeUT_noID.exe" and a "ROMUpgradeUt.exe". If I take one of those older ROM files, replace the radio_.nbf file with the one from 1.18, and run the MaUpgradeUT_noID executable (without any ms_.nbf and nk.nbf files in the folder), will that result in the NoID radio upgrade method without the hard reset?
http://wiki.xda-developers.com/index.php?pagename=UNI_Radio
Click to expand...
Click to collapse
Yes, that was what I did. But be sure to backup just to be in the safe side.
---

Backup of course, thanks.

shlomki said:
what? ROMUpgradeUt hard resetted your device?
thats wierd. it did that without asking?
anyone else had this?
im about to flash myself. i guess i'll use the old no_id flash util...
Click to expand...
Click to collapse
Yes ROMUpgradeUt did indeed hard reset my device, without warning or asking me. This may have been caused by it crashing after it made my phone enter the bootloader, windows said "USB device not recognized" and ROMUpgradeUt tried to correct this "error", then it crashed with a windows exception error (I'm not using any USB hub, and device was ActiveSync'd fine at the start).
My phone was now in the bootloader at this point, so I just re-launched ROMUpgradeUt and this time it successfully performed the radio upgrade, but on booting up I noticed it had been hard reset I did have a 1 month old SPB backup image, so it only took me 2 hours to set everything back the way I like it.
You should probably use ROMUpgradeUt anyway as I seem to recall it being a lot safer than MaUpgradeUT_noID - just remember to always take a backup before doing any kind of ROM flashing
Anyway after half a day of using 1.18, it seems fine and stable. As good as (if not better than) 1.09 and 1.15, which I have used previously. Thanks again beast man!

MaUpgradeUT_noID worked fine, no hard reset. 1.18 seems fine so far.

can i use this to upgrade on my blue angel radio rom too??

Does anybody have a working link for this?
Neither of the two work for me. Thanks.

NO GSM problem! any solution?

Hi All,
I am facing the dreaded 'No GSM' error and unable to flash radio rom problem.
tried to flash every possible rom including original O2 one. All failed on radio ram flash.
Went through various threads and there seems to be no solution yet for universal (though there seems to be a solution for Hermes).
So all, please help me if there is some light in the end of this tunnel
regards
Topgun

i have tried all the possible things but no luck so far.....
please help

I just bought a used XDA with this same problem. Thought if i flash it it would work... any suggestions on what I can do? i havent touched it yet. Thanks

has ANYONE been able to solve this problem?!!!! Pls what did u do step by step.... I spent so much money on this %&%$& Phone!!! pulllleeeessssss

I haven't had this problem, however it sounds like you phone may be SIM locked? If so, you will need to flash it with the native ROM from it;'s origin. If it is SIM and CID locked, it will only take the OEM signed ROM.
Quote from POF (Moderator)
"Not in 100% of the cases... there are some situations where the radio bootloader is intact, but the radio is screwed, this causes all bootloader commands that require radio seclevel to be queried to hang the device (like 'task 32' or 'info 2'), thus not being able to flash it with the usual RUUs.
If this happens, it can easily be fixed with hermflasher by flashing the raw radio without prior authenticating to bootloader."
If this is of any help. It is from a thread on CID Unlocking RUU for Uni

Thanks.
i have been through that thread.
well the question on that is 'Is hermflasher okay to flash Universal as well'?

Where is this thread? i can try it.... but cant find the thread on cid unlocking ruu for universal in mermes section....
raskell said:
I haven't had this problem, however it sounds like you phone may be SIM locked? If so, you will need to flash it with the native ROM from it;'s origin. If it is SIM and CID locked, it will only take the OEM signed ROM.
Quote from POF (Moderator)
"Not in 100% of the cases... there are some situations where the radio bootloader is intact, but the radio is screwed, this causes all bootloader commands that require radio seclevel to be queried to hang the device (like 'task 32' or 'info 2'), thus not being able to flash it with the usual RUUs.
If this happens, it can easily be fixed with hermflasher by flashing the raw radio without prior authenticating to bootloader."
If this is of any help. It is from a thread on CID Unlocking RUU for Uni
Click to expand...
Click to collapse

Here is the thread
http://forum.xda-developers.com/showthread.php?t=301662&highlight=radio+error
Let me know if you have any luck with this.
cheers

topgunarindam said:
http://forum.xda-developers.com/showthread.php?t=301662&highlight=radio+error
Let me know if you have any luck with this.
cheers
Click to expand...
Click to collapse
no, hermflasher wont work with universal (I dont think) ill consult with some others and report back here our consensus on what to try

I am facing the same 'No GSM' error in xda exec, plz can somebody tell me step by step how to solve it.

Thanks Midget
shall wait for your word.

Midget
topgunarindam said:
shall wait for your word.
Click to expand...
Click to collapse
I'm waiting too.

Good News at Last
atleast it worked for me.
flashed using a different pc with radio 1.18 and it worked.
the radio is working fine with laurentius26's WM6 rom.
atleast my brick comes live again.

LUCKY YOU!!!!!!!!
topgunarindam said:
atleast it worked for me.
flashed using a different pc with radio 1.18 and it worked.
the radio is working fine with laurentius26's WM6 rom.
atleast my brick comes live again.
Click to expand...
Click to collapse
lucky you, I tried that same WM6 ROM (with radio 1.18) and still same problem. I've tried falshing with 2 different desktops and a laptop. Still same problem! Topgun, did u have active sinc installed ? was the PC u used fresh? (no apps installed). do u think if i format my PC it could flash the radio? DID u flash radio only? or the whole laurentious v3 WM6 package (that is at the same time)?
Pls reply

Tbaba said:
lucky you, I tried that same WM6 ROM (with radio 1.18) and still same problem. I've tried falshing with 2 different desktops and a laptop. Still same problem! Topgun, did u have active sinc installed ? was the PC u used fresh? (no apps installed). do u think if i format my PC it could flash the radio? DID u flash radio only? or the whole laurentious v3 WM6 package (that is at the same time)?
Pls reply
Click to expand...
Click to collapse
Him
well it was a laptop dell to be precise.
it was never used for window mobile usage previously and hence fresh Active sync 4.5 was installed.
only radio rom 1st (using the RUU check bypassing)......
once succesful, then laurentiius rom was tried.
one more thing i had entered bootloader manually after disabling AS 4.5
i used the original USB cable as well
hope this helps....
suggest get hold of some friends "win mobile virgin" pc/laptop.
P.S>- i am not sure but this prob might be somewhat related to COM ports available on your machine.

My HERM Is Running Without Radio (GSM)?!

PLZ help me, while trying to upgrade my HERM I lost the Radio, there is a message (No GSM) appearing during the boot.
I've tried many unofficial ROMs, but still getting the same message!!!
And when I tried to use the official ROM, the upgrade stopped on 11%!!??
To solve the hangup problem, I used unofficial ROM again, and after the upgrade I found the same GSM problem again.

FirasKB said:
PLZ help me, while trying to upgrade my HERM I lost the Radio, there is a message (No GSM) appearing during the boot.
I've tried many unofficial ROMs, but still getting the same message!!!
And when I tried to use the official ROM, the upgrade stopped on 11%!!??
To solve the hangup problem, I used unofficial ROM again, and after the upgrade I found the same GSM problem again.
Click to expand...
Click to collapse
What "official" ROM? You've given absolutely NO info regarding anything friend...
Myself, I'd click the green link in my signature... but that's me

My problem is clear, there is No GSM in my HERM, I've tried WM 5, WM 6 and WM 6.1, but no way, I couldn't success??!!
Kindly, advice if you have any solution or ask for a specific info.

FirasKB said:
My problem is clear, there is No GSM in my HERM, I've tried WM 5, WM 6 and WM 6.1, but no way, I couldn't success??!!
Kindly, advice if you have any solution or ask for a specific info.
Click to expand...
Click to collapse
Yes your problem is clear, you have no GSM. I don't know where you hail from, which exact PDA you have, your provider, what ROM you last used before this happened, etc..

Dr Puttingham said:
Yes your problem is clear, you have no GSM. I don't know where you hail from, which exact PDA you have, your provider, what ROM you last used before this happened, etc..
Click to expand...
Click to collapse
Fine,,,
Device: at&t 8525
ROM: Original WM5 ROM, and while trying to upgrade it my device hanged up on the colored screen. To fix that, I've installed schap's 4.31 WM6 ROM using the MicroSD Card (HERMIMG). Now the device can boot but with No GSM at all (even there's no information about the GSM under Device Info).
The device now can accept any modified ROM (like schap's, faria, etc...) but unable to accept the official (original) ROMs. When I try to install any official ROM the upgrade process will stack on 11% every time.
So, the device still having no GSM.
Thank You....

FirasKB,
Most roms on her DO NOT come with a radio included. Usually only the manufacturer roms do.
There are 2 things you need to do:
- Consult the MrVanx guides which will help you understand what you are doing (google search for this).
- go to the wiki in this forum and search for a radio rom to upload.
In summary, reflash, say, Scahps rom then flash a radio rom from the wiki (I suggest radio 1.47, which is pretty reliable).
Hope this helps.
WB

FirasKB said:
Fine,,,
Device: at&t 8525
ROM: Original WM5 ROM, and while trying to upgrade it my device hanged up on the colored screen. To fix that, I've installed schap's 4.31 WM6 ROM using the MicroSD Card (HERMIMG). Now the device can boot but with No GSM at all (even there's no information about the GSM under Device Info).
The device now can accept any modified ROM (like schap's, faria, etc...) but unable to accept the official (original) ROMs. When I try to install any official ROM the upgrade process will stack on 11% every time.
So, the device still having no GSM.
Thank You....
Click to expand...
Click to collapse
Ahhh, a little info.
First download the official AT&T 3.62 ROM which includes the 1.54.07.00 radio.
Reboot the pc with the PDA disconnected.
(Oh, make sure that you have ActiveSync 4.5 insttalled of course)
Put the device into bootloader mode (hold power and OK button while pressing reset with stylus, nice tri color screen will appear)
Connect the PDA to the USB cable and run the RUU_Inside.exe file.
wacky.banana is correct, most chef's don't include a radio. You've got a corrupted ROM (due to the incomplete flash) The RUU_Inside.exe will typically talk directly to the hardware when nothing else can and fix. I've personally recovered around 10 or so 8525's that I've "bricked" with bad flashes and then repaired with this method.
I can't guarantee that this will work but it IS your best shot friend.
Good luck!

Dr Puttingham said:
Ahhh, a little info.
First download the official AT&T 3.62 ROM which includes the 1.54.07.00 radio.
Reboot the pc with the PDA disconnected.
(Oh, make sure that you have ActiveSync 4.5 insttalled of course)
Put the device into bootloader mode (hold power and OK button while pressing reset with stylus, nice tri color screen will appear)
Connect the PDA to the USB cable and run the RUU_Inside.exe file.
wacky.banana is correct, most chef's don't include a radio. You've got a corrupted ROM (due to the incomplete flash) The RUU_Inside.exe will typically talk directly to the hardware when nothing else can and fix. I've personally recovered around 10 or so 8525's that I've "bricked" with bad flashes and then repaired with this method.
I can't guarantee that this will work but it IS your best shot friend.
Good luck!
Click to expand...
Click to collapse
Thanks to your support friends,,
I've done as you mentioned, but the upgrade process stopped on 11% again and couldn't complete!!?? (the message ERROR [262]: UPDATE ERROR appeared on my P.C)!!??
Kindly, advice...

I can't remeber what error 262 is about; however is your device unlocked? If it is not then you need to address that issue first (its in the wiki)
Secondly have you installed hard spl to your device BEFORE attempting to upgrade your rom? If the answer to this question is no then that will confirm that you have not read up on this before jumping in, which is hugely dangerous.
WB

Stuck.... completely stuck
My fiances phone is stuck in the tri color bootloader screen. I am in the US and i have tried everything from flashing the original RUU to a hard reset and everthing, but nothing seems to work. the IPL is 4. 10. 0002 and the SPL is 4. 10. 0000. Can someone please help me. I know there has to be a way to fix this.

I had the same problem. After trying to fix it myself for about a week I gave up and sent it to AT&T Repair center. Got it back functional.
I haven't tried the Himalaya ROM method, though.
Check this thread:
http://forum.xda-developers.com/showthread.php?t=372895
Good luck!

wacky.banana said:
I can't remeber what error 262 is about; however is your device unlocked? If it is not then you need to address that issue first (its in the wiki)
Secondly have you installed hard spl to your device BEFORE attempting to upgrade your rom? If the answer to this question is no then that will confirm that you have not read up on this before jumping in, which is hugely dangerous.
WB
Click to expand...
Click to collapse
Thanks again to your support,
The problem happened when I tried to unlock the device to upgrade it (it was fine befor), I don't know whether it was already locked or not, but usualy when I buy any Pocket P.C I'm preparing to unlock it first (I've done that many times on HERMES before, but this is the first time I'm facing such problem!!). So, while unlocking the device it's stucked on the tri color screen.
I've done many things after that to solve the problem (updating the hard SPL to v2.10 successfully, flashing many ROMs -not including Radio- successfully).
So, I can flash any ROM now but it must be without Radio, otherwise the flashing process will stuck on 11%.

try reading the wiki:
http://wiki.xda-developers.com/index.php?pagename=Hermes_Unbrick

More than 2 days and I couldn't success to bring the Radio back??!! I think I've really lost my device.

FirasKB,
What steps exactly have you taken to solve the problem? Try and outline them here; that will help people on here to identify what else you need to do to bring the device back to life.
WB

FirasKB said:
More than 2 days and I couldn't success to bring the Radio back??!! I think I've really lost my device.
Click to expand...
Click to collapse
Schap´s Rom has NO Radio. Flash this one BUT u must have HardSPL
http://forum.xda-developers.com/showthread.php?t=348435&highlight=Radio

wacky.banana said:
FirasKB,
What steps exactly have you taken to solve the problem? Try and outline them here; that will help people on here to identify what else you need to do to bring the device back to life.
WB
Click to expand...
Click to collapse
wacky.banana,
As I wrote above, my problem still not solved and my device still running with (No GSM).
I've done the following:
- Updating the ROM (O.S only as the device not accepting any Radio ROM)
- Updating the SPL to Version 7.
- Trying to update the radio (separately) but I didn't success??!!
It seems there is no solution to fix this problem???!!!

Abo Forat said:
Schap´s Rom has NO Radio. Flash this one BUT u must have HardSPL
http://forum.xda-developers.com/showthread.php?t=348435&highlight=Radio
Click to expand...
Click to collapse
No way, I tried it but my device can't accept any Radio version.

FirasKB said:
wacky.banana,
As I wrote above, my problem still not solved and my device still running with (No GSM).
I've done the following:
- Updating the ROM (O.S only as the device not accepting any Radio ROM)
- Updating the SPL to Version 7.
- Trying to update the radio (separately) but I didn't success??!!
It seems there is no solution to fix this problem???!!!
Click to expand...
Click to collapse
Frisk,
Read this thread and try the solutions metioned in it. It tells you what error 262 is all about....http://forum.xda-developers.com/archive/index.php/t-298516.html
Cheers
WB

wacky.banana said:
Frisk,
Read this thread and try the solutions metioned in it. It tells you what error 262 is all about....http://forum.xda-developers.com/archive/index.php/t-298516.html
Cheers
WB
Click to expand...
Click to collapse
Unfortunately, but that's also didn't help, because the main problem now is how to install the Radio on the device??!!
The device is not accepting the Radio installation at all, NO WAY....

updating t-mo ruu manually.

So i was trying to install the latest nougat roms and realized i need to be on 4.xx for them.
I am on 3.xx
So i tried to update via the latest ruu from htc.
http://www.htc.com/us/support/rom-downloads.html
Did not work.
Then i realized that the rom was for a developers edition phone which mine is not.
So i downloaded the latest 3.xx rom. for the non developer phone.
After i downloaded it, I realized it was the same 4.xx ruu that i downloaded before. So i thought my mistake.
Go back and download AGAIN and yup, the link they provide in the "details and instuctions" section for the 3.xx rom is definitely for the 4.xx ruu.
When i click the download link without going into details. the link does not work.
Weird thing. on this page http://www.htc.com/us/support/updates.aspx
They do not specify developer edition.
So now the question is. IS 4.xx the latest update for all t-mo m9 phones and i am just having a problem installing.
Or do i need to find the 3.xx rom from a different source.

So i checked on a friends stock m9 and indeed it has the 4.47 update.
So i guess i am just doing something wrong. I am rooted but i never chose the option in twrp to modify files.
I can connect to the ruu in download mode. I tells me the correct rom that i have on the phone and offers to update. Once i choose update it seems to work fine. Reboots my phone then gives me error 123.
I cant seem to find a zip for it. Or a copy of the older ruu.
If anybody can point me in the direction of a database somewhere that would be super helpful. I know the mods used to keep them stickied at the top.
I do have a ruu and zip on my computer from a couple years ago that i will try too.

Tried to flash the last ruu i flashed before. got error 155 and now am stuck in flashing mode. With a half flashed phone. no way to reset it. 10 second power button does not work. cant pull the battery as the ruu advises me to do.
Guess im waiting for the phone to die from 100%
I think the problem is simple and something i totally forgot in the last couple years.
I NEED TO RE LOCK MY BOOTLOADER. but who knows. apparently its just me on here.
SO LONG FOR GOOD ADVICE FROM XDA.
BOOOO.

Please don't forget that this is a forum and not a support-hotline/-chat where people get payed for replying immediately. Most of us are doing this as their hobby and aren't able to be online 24/7. It might take some time till you get a reply. Especially if you post in a section that shows almost no activity aside from some new questions being asked. Most (former) users have already moved on to other devices due to the age of the M9 and many devs left the development scene due to the end users on xda that became more and more toxic and demanding during the last couple of years.
myphonesbetter said:
So i was trying to install the latest nougat roms and realized i need to be on 4.xx for them.
I am on 3.xx
Click to expand...
Click to collapse
You actually don't need firmware 4.x. Firmware 3.x is compatible with the latest custom roms, as well. They only run "better" on firmware 4.x.
myphonesbetter said:
So i tried to update via the latest ruu from htc.
http://www.htc.com/us/support/rom-downloads.html
Did not work.
Then i realized that the rom was for a developers edition phone which mine is not.
So i downloaded the latest 3.xx rom. for the non developer phone.
After i downloaded it, I realized it was the same 4.xx ruu that i downloaded before. So i thought my mistake.
Go back and download AGAIN and yup, the link they provide in the "details and instuctions" section for the 3.xx rom is definitely for the 4.xx ruu.
When i click the download link without going into details. the link does not work.
Click to expand...
Click to collapse
HTC is a bit lazy in regard to updating their webpage. You're always only able to download the latest RUU. However, you don't mention which variant you own. There is more than just one non-dev edition variant. Nevermind, you mentioned it in one if your following posts.
myphonesbetter said:
Weird thing. on this page http://www.htc.com/us/support/updates.aspx
They do not specify developer edition.
So now the question is. IS 4.xx the latest update for all t-mo m9 phones and i am just having a problem installing.
Or do i need to find the 3.xx rom from a different source.
Click to expand...
Click to collapse
Firmware 4.x is the latest version for all SKUs/variants and there won't be any further updates since the M9 reached the EOL stage almost a year ago.
myphonesbetter said:
So i checked on a friends stock m9 and indeed it has the 4.47 update.
Click to expand...
Click to collapse
Is that a typo? I only know about firmware 4.27.531.6 for the T-Mobile US variant.
myphonesbetter said:
So i guess i am just doing something wrong. I am rooted but i never chose the option in twrp to modify files.
Click to expand...
Click to collapse
It's possible to break the OTA-update function by modifying the system via a root file explorer, as well.
myphonesbetter said:
I can connect to the ruu in download mode. I tells me the correct rom that i have on the phone and offers to update. Once i choose update it seems to work fine. Reboots my phone then gives me error 123.
Click to expand...
Click to collapse
Is that another typo? I'd have expected error 132 since firmware 3.x and 4.x are using different encryption keys. You can't update using a RUU. You need to use the software update function of the system settings.
myphonesbetter said:
I cant seem to find a zip for it. Or a copy of the older ruu.
If anybody can point me in the direction of a database somewhere that would be super helpful. I know the mods used to keep them stickied at the top.
Click to expand...
Click to collapse
The "database" is still stickied (in not only one but two subforums of the M9 section - the general and the q&a section). Therefore, I'm a bit surprised that you weren't able to find what you're looking for. In addition the thread I'm talking about is not only a database, it even contains all information you would have needed for solving your issues, already.
myphonesbetter said:
I do have a ruu and zip on my computer from a couple years ago that i will try too.
Click to expand...
Click to collapse
If the RUU is older than your current firmware then you won't be able to use it.
myphonesbetter said:
Tried to flash the last ruu i flashed before. got error 155 and now am stuck in flashing mode. With a half flashed phone. no way to reset it. 10 second power button does not work. cant pull the battery as the ruu advises me to do.
Guess im waiting for the phone to die from 100%
Click to expand...
Click to collapse
Error 155 means that you either try to flash a RUU that is too old or made for a different variant than the one you own. The key combination you're looking for is the power button plus volume down up and you need to keep them pressed for about 30 seconds. HTC changed that on one of the devices that came out before the M9. Letting the battery die is a bad idea, though. You'll damage it this way.
myphonesbetter said:
I think the problem is simple and something i totally forgot in the last couple years.
I NEED TO RE LOCK MY BOOTLOADER. but who knows. apparently its just me on here.
Click to expand...
Click to collapse
No you don't. I can't discourage people enough from relocking this phone's bootloader if the phone is S-ON and not 100% stock and you don't have a RUU at hand that you already used successfully on your phone. HTC's security checks will prevent the device from booting if anything is modified (e.g. TWP being installed) while the bootloader is locked or relocked. They don't differentiate between "broken" and "custom" files and think that the modified software is broken. Therefore, the checks are trying to prevent the hardware from getting damaged by preventing the device from booting. In addition, if OEM Unlock isn't activated in the developer settings of the currently installed rom then there is no way to re-unlock the phone. That's an FRP (factory reset protection) Google introduced with android 5.1 (which equals firmware 2.x of the M9).

Flippy498 said:
Please don't forget that this is a forum and not a support-hotline/-chat where people get payed for replying immediately. Most of us are doing this as their hobby and aren't able to be online 24/7. It might take some time till you get a reply. Especially if you post in a section that shows almost no activity aside from some new questions being asked. Most (former) users have already moved on to other devices due to the age of the M9 and many devs left the development scene due to the end users on xda that became more and more toxic and demanding during the last couple of years.
Click to expand...
Click to collapse
Yah. I get it. Was kind of just shouting to get some attention.
Ive noticed that not just this forum but many other forums that i used to use have lossed a lot of popularity.
I think because facbook groups and things like reddit that cover all subjects.
The problem with those places is that they are so unorganized.
Maybe thats also part of why its become so unorganized here. just what people are used to.
I honestly wasnt expecting actual info. Thank you.
Flippy498 said:
You actually don't need firmware 4.x. Firmware 3.x is compatible with the latest custom roms, as well. They only run "better" on firmware 4.x.
Click to expand...
Click to collapse
Well i was afraid to brick it so i figured out (accidentally) how to update.
Flippy498 said:
Firmware 4.x is the latest version for all SKUs/variants and there won't be any further updates since the M9 reached the EOL stage almost a year ago.
Is that a typo? I only know about firmware 4.27.531.6 for the T-Mobile US variant It's possible to break the OTA-update function by modifying the system via a root file explorer, as well..
Click to expand...
Click to collapse
Yes that was. it is 4.27.
I could not find any older ruu's on their site. Or anywhere for that matter. none with active links at least.
Flippy498 said:
Is that another typo? I'd have expected error 132 since firmware 3.x and 4.x are using different encryption keys. You can't update using a RUU. You need to use the software update function of the system settings.
Click to expand...
Click to collapse
Yes 132. I did not realize that. Do you mean i would need to update via ota? by searching for updates.
Flippy498 said:
If the RUU is older than your current firmware then you won't be able to use it.
Error 155 means that you either try to flash a RUU that is too old or made for a different variant than the one you own. The key combination you're looking for is the power button plus volume down and you need to keep them pressed for about 30 seconds. HTC changed that on one of the devices that came out before the M9. Letting the battery die is a bad idea, though. You'll damage it this way.
Click to expand...
Click to collapse
So i was originally trying to flash the latest frimware 4.27.xxx but i kept getting error 132.
And on the htc website it has 2 sections for ruu's m9 ans m9 developer. So i just figured it was the wrong one.
So i figured i would try the last ruu that i flashed before installing the rom that i ran for almost 2 years (lee droid)
when i flashed that, it got halfway through and gave me error 155. but left my phone in the middle of an update. Apparently the power button is disabled during this process.
it tell you to pull the battery or hold the power button for 10 seconds then try to recover from the boot using the ruu.
Well i could not reboot the phone so i just started the recover process. This rebooted my phone a few times then just started flashing the rom. To my surprise it worked.
It also re-locked my phone.
After that, now that im stock, i tried to flash the 4.27 ruu. still 132.
So i tried to run the ota's and they worked.
Took about 4 hours and 7 updates or so. probably 5 gigs on the data plan but finally it finshed with a 1.1 gig update to 4.27.
Im not sure why the first flash failed or why it worked, but eventually it did work.
Flippy498 said:
No you don't. I can't discourage people enough from relocking this phone's bootloader if the phone is S-ON and not 100% stock and you don't have a RUU at hand that you already used successfully on your phone. HTC's security checks will prevent the device from booting if anything is modified (e.g. TWRP being installed) while the bootloader is locked or relocked. They don't differentiate between "broken" and "custom" files and think that the modified software is broken. Therefore, the checks are trying to prevent the hardware from getting damaged by preventing the device from booting. In addition, if OEM Unlock isn't activated in the developer settings of the currently installed rom then there is no way to re-unlock the phone. That's an FRP (factory reset protection) Google introduced with android 5.1 (which equals firmware 2.x of the M9).
Click to expand...
Click to collapse
Ive always relocked my htcs before running an ruu. If not then they never seem to work. I dont mind it because it takes about 10 seconds. and i already hae the token. I actually remembered the majority of the commands.
Maybe its causing another problem that i dont know about.
I did see the oem unlock in developer options if that is what you are talking about.
I was using the last ruu that i had used. but i also flashed a rom and it was a long time in between.
Also i installed the old version of lee droid on 4.27.xxx and it seemed to work fine. I did this on accident though. Flashed the wrong zip. Re-flashed the latest 4.0 and it seems to be working great. Noticing a couple little lags. Might go to the stock rom just rooted and debloated. It seemed to run a little smoother than leedroid for the time i was using it. but i felt like they were trying to extract my stem cells via confusing TOS agreements.

myphonesbetter said:
Apparently the power button is disabled during this process.
it tell you to pull the battery or hold the power button for 10 seconds then try to recover from the boot using the ruu.
[...]
It also re-locked my phone.
After that, now that im stock, i tried to flash the 4.27 ruu. still 132.
So i tried to run the ota's and they worked.
Ive always relocked my htcs before running an ruu. If not then they never seem to work. I dont mind it because it takes about 10 seconds. and i already hae the token. I actually remembered the majority of the commands.
Maybe its causing another problem that i dont know about.
I did see the oem unlock in developer options if that is what you are talking about.
Click to expand...
Click to collapse
The power button isn't disabled. As said in my last post, you need to press the power button and the volume down button for 30 seconds. It's always been like that on the M9 since HTC already changed that on the M7 or M8 (can't tell you which one exactly it was).
Relocking was only needed on HTC phones that are older than the M9. HTC changed that with the M9. And as said in my last post, re-locking the M9 if you don't have a RUU at hand that you already used successfully is more than dangerous due to Google's FRP. You might end with a non-booting non-unlockable phone.
In addition, a relocked dootloader doesn't change the fact, that your phone is missing the needed encryption keys. That's why the 4.x RUU still failed.
However, it's nice to hear that you could solve your problems now. ?
Sent from my HTC One M9 using XDA Labs

Ah, I made a mistake while writing my posts. It's power and volume up. Not power and volume down. :silly: