Develop Bugs

RUU_Hero_HTC_WWE_2.73.405.38

New shipped ROM for Hero
http://rapidshare.com/files/290153350/RUU_Hero_HTC_WWE_2.73.405.38_WWE_release_signed_NoDriver.exe
Enjoy!

Football said:
New shipped ROM for Hero
http://rapidshare.com/files/290153350/RUU_Hero_HTC_WWE_2.73.405.38_WWE_release_signed_NoDriver.exe
Enjoy!
Click to expand...
Click to collapse
What's new?

Ehh, It´s the same build as before. HTC Hero_2.73.405.5 for what I understand the last nr .38 is just the mobile providers rom build version.

this seems to be an update for a limited number of carriers:
android-info.txt for this one:
ModelID: HERO10000
CIDNUM: HTC__001
CIDNUM: HTC__N34
CIDNUM: 11111111
MainVer: 2.73.405.38
the "official" htc update has this:
ModelID: HERO10000
CIDNUM: HTC__001
CIDNUM: HTC__032
CIDNUM: HTC__203
CIDNUM: HTC__102
CIDNUM: HTC__405
CIDNUM: HTC__E11
CIDNUM: HTC__Y13
CIDNUM: HTC__304
CIDNUM: HTC__506
CIDNUM: HTC__N34
CIDNUM: 11111111
MainVer: 2.73.405.5
So, from which provider did you get this ?

Has anyone tested RUU_Hero_HTC_WWE_2.73.405.38?
I can´t find any info at all about the realease.

Maybe this is Sprints' Update? Has anyone tried it?
Well someone in Androidcommunity posted the following :
Sprint Hero Firmware Update
I cannot give out versions or anything, but I can say the Sprint Hero had an update pushed out to it yesterday, the training handsets that is.
Lag is almost gone. Out of the box the Hero had almost no lag, but after installing a few apps is started lagging. This new update makes it zippy. I'm not sure if the phones will come preloaded or will require an update when purchased,, but its great.
So any of those reviews that complained about the lag can eat it. Some people will find any reason at all to complain anyway.
Click to expand...
Click to collapse

Her is the update.zip.
It is stock WWE version. Récent build.
Has new contact widget.
Rooted.

Rooted and unrooted update.zip versions posted in my update thread.
P

also uploaded here:
http://forum.xda-developers.com/showthread.php?t=559622

I find this version really fast

indeed it is quick, but i notice that it seems to have removed the option for 'current location' in weather and clock. or at least it seemed to do so on mine.
Have gone back to 405.5 for that reason. little thing i know, but i don;t really want the weather in london when the other ROM does it for me automatically and updates as i travel.

rhedgehog said:
indeed it is quick, but i notice that it seems to have removed the option for 'current location' in weather and clock. or at least it seemed to do so on mine.
Have gone back to 405.5 for that reason. little thing i know, but i don;t really want the weather in london when the other ROM does it for me automatically and updates as i travel.
Click to expand...
Click to collapse
I am running 2.73.405.38 and "current location" option is still there :-/

Is it possible to install this but then replace the new contacts widget with the older one? I kinda like the older one Please guide!!
One more thing... will installing it change the kernel in such a way that flashrec will no longer be supported?? There are some people on the forum with Asian builds who are already complainig about the flashrec not working at all on their phones. I can see that the kernel# after installing this 405.38 ROM is somewhat different from my current one i.e. 405.5
My kernel:
2.6.27-8dd6deee
[email protected] )
Kernel with this ROM:
2.6.27-0078c992
[email protected] #851

salmanbodla said:
Is it possible to install this but then replace the new contacts widget with the older one? I kinda like the older one Please guide!!
One more thing... will installing it change the kernel in such a way that flashrec will no longer be supported?? There are some people on the forum with Asian builds who are already complainig about the flashrec not working at all on their phones. I can see that the kernel# after installing this 405.38 ROM is somewhat different from my current one i.e. 405.5
My kernel:
2.6.27-8dd6deee
[email protected] )
Kernel with this ROM:
2.6.27-0078c992
[email protected] #851
Click to expand...
Click to collapse
flashrec doesnt work with this one, so if you can't use an official RUU from before the kernel patch to downgrade to, don't use this

Jesterz said:
flashrec doesnt work with this one, so if you can't use an official RUU from before the kernel patch to downgrade to, don't use this
Click to expand...
Click to collapse
Thanks for your reply Jesterz
I do have the UNLOCKED white UK hero and can install the WWE version ROMs via RUU like the latest official release 2.73.405.5. Does that mean it will be safe for me to try this ROM (405.38) and still be able to go back to 405.5 if desired, and regain the flashrec support.
BTW, if I flash this new ROM using update.zip method, will that also make flashrec and my RA-Hero recovery image non-functional? Please help on this.
Cheers!

salmanbodla said:
Thanks for your reply Jesterz
I do have the UNLOCKED white UK hero and can install the WWE version ROMs via RUU like the latest official release 2.73.405.5. Does that mean it will be safe for me to try this ROM (405.38) and still be able to go back to 405.5 if desired, and regain the flashrec support.
BTW, if I flash this new ROM using update.zip method, will that also make flashrec and my RA-Hero recovery image non-functional? Please help on this.
Click to expand...
Click to collapse
Havn't tested the 405.38 SPL myself. I don't see any reason to do so.... And yes it may block your device from rooting.
I would suggest you to use update.zip as it does exactly what you want the RUU to do: replace kernel and system.
You may then flash the 405.5 RUU when you wish.
Regards

gecka said:
Havn't tested the 405.38 SPL myself. I don't see any reason to do so.... And yes it may block your device from rooting.
I would suggest you to use update.zip as it does exactly what you want the RUU to do: replace kernel and system.
You may then flash the 405.5 RUU when you wish.
Regards
Click to expand...
Click to collapse
OK, thanks gecka
I suppose I am pretty safe since the 2.73.405.5 RUU works just fine for me... kind of a good fall-back if I am stuck with the newer kernel. Will give 405.38 a go soon.
You said it is really quick... what exactly are the major improvements? And how about the new radio? Any appreciable difference from the previous one?

salmanbodla said:
OK, thanks gecka
I suppose I am pretty safe since the 2.73.405.5 RUU works just fine for me... kind of a good fall-back if I am stuck with the newer kernel. Will give 405.38 a go soon.
You said it is really quick... what exactly are the major improvements? And how about the new radio? Any appreciable difference from the previous one?
Click to expand...
Click to collapse
I personally find it more responsive, about perfect.
Kernel is exactly the same (md5sum). Just do a nandroid backup and try it. A nandroid restore will restore it at its exact state.
About the radio, I have never been able to tell if one is better than another.

cTnko said:
I am running 2.73.405.38 and "current location" option is still there :-/
Click to expand...
Click to collapse
must just have been a screw up on mine then. Maybe i'll try it again later.

I can also confirm that the Current Location feature is still working fine ;-)
Definately more responsive than the 405.5 ROM, it's a pleasure to use!
rhedgehog said:
must just have been a screw up on mine then. Maybe i'll try it again later.
Click to expand...
Click to collapse

S-Off might be difficult - but maybe we can work around

Hi,
nobody knows me, thats just fine . What I m currently doing is I m trying to find out if there´s a suitable software-way to work around that messy S-Off problem.
Whats the idea?:
The idea is quite simple, the current hboot 1.31 already supports all branded devices.
Seriously?
Yea, seriously.
If you unpack the current hboot and open it using a text-editor like Windows editor you´ll find the following lines
NORMAL RECOVERY_UPDATE_RADIO RECOVERY_UPDATE_HBOOT RECOVERY_UPDATE_ZIP RECOVERY_UPDATE_COMBO HTCBL BOOTPROFILING SDUPDATE RECOVERY_MANUAL POWERTEST RECOVERY_POWERTEST OFFMODE_CHARGING RECOVERY_OFFMODE_CHARGING MFGKERNEL MFGKERNEL_DEBUG MFGKERNEL_58 SECURITY_RESET REBOOT_BOOTLOADER POWER_DOWN HBOOT_USB FACTORYRESET SYSINFO IMGCRC NORMAL_DIAG RAMDUMP2EMMCDUM RAMDUMP2USB RAMDUMP2SD 9KRAMDUMP 9KRAMDUMP2SD MODEMPATHON MODEMPATHOFF LOGGERSETTING LOGGERON LOGGEROFF LOGGERTOINTERNAL LOGGERTOSD DIAG MODEM_CALIBRATION Dopod-China DOPOD701 Open-Channel HTCCN701 CT HTCCN702 CU HTCCN703 CMCC-TD HTCCN704 TMUS T-MOB010 TMD T-MOB101 TMA T-MOB102 TMNL T-MOB003 TMCZ T-MOB004 TMUK T-MOB005 TMHR T-MOB006 TMH T-MOB007 TMSK T-MOB008 Era T-MOB009 TMMK T-MOBL11 VODA-UK VODAP001 VODA-Germany VODAP102 VODA-Italy VODAP405 VODA-SFR VODAP203 VODA-Spain VODAP304 VODA-Netherland VODAPE17 VODA-Ireland VODAP019 VODA-Greece VODAP006 VODA-Portugal VODAPD18 VODA-Swisscom-WWE VODAP015 VODA-Swisscom-DE VODAP110 VODA-Swisscom-FR VODAP212 VODA-Swisscom-IT VODAP416 VODA-Australia VODAP021 VODA-New-Zealand VODAP022 VODA-Mobilkom VODAP120 VODA-Proximus VODAP024 VODA-TR VODAPM27 ORANGE-French ORANG202 ORANGE-UK ORANG001 ORANGE-ES ORANG309 ORANGE-BE ORANG012 ORANGE-PO ORANG008 ORANGE-CH-FRA ORANG203 ORANGE-CH-GER ORANG104 ORANGE-SK ORANG006 ORANGE-PL ORANGB10 ORANGE-AT ORANG113 GOOGLE GOOGL001 TELEF-Spain TELEF301 TELUS TELUS001 DCM DOCOM801 ATT CWS__001 Brightstar-SPA BSTAR301 Brightstar-PTB BSTAR502 VIRGIN-UK VIRGI001 O2-UK O2___001 HTC-Czech HTC__C24 HTC-Denmark HTC__F08 HTC-Norway HTC__H10 HTC-Sweden HTC__G09 HTC-Poland HTC__B25 HTC-Russia HTC__A07 HTC-Turkey HTC__M27 HTC-GCC HTC__J15 HTC-Australia HTC__023 HTC-Singapore HTC-FRA HTC__203 StarHub-Singapore VODA-Africa-South AirTel-India TIM-Italy TIM__401 H3G-Italy H3G__402 Optus-Australia OPTUS001 Hutch-Australia HUTCH001 SMC-Voda-HK SMCVD001 Chunghwa-Taiwan CHT__601 Rogers ROGER001 HTC-EastEurope HTC__032 HTC-GER HTC__102 HTC-ITA HTC__405 HTC-Dutch HTC__E11 HTC-Nor HTC__Y13 HTC-WWE HTC
You see - all there.
So, Vodafone and all the others can stopp telling is their branded devices are not yet supported - bull****.
So, I´m trying to find a way to edit files in a way that the installer believes the currently plugged device is supported - even in case its got a totally different CID.
Dunno if this will work in any possible way...but hey, at least a try.
Regards
*Edit: If anyone found an HOX RUU from Asia for JB - that would be quite helpful.

Of course it supports every single HTC One X, regardless of CID, but:
If you change any file the signature will be broken, will not work. If you look at the header of the zip file in a hex editor, there is a 256-byte long signature that no one knows how to decrypt.
(I'm talking about the firmware.zip)

tomascus said:
Of course it supports every single HTC One X, regardless of CID, but:
If you change any file the signature will be broken, will not work. If you look at the header of the zip file in a hex editor, there is a 256-byte long signature that no one knows how to decrypt.
(I'm talking about the firmware.zip)
Click to expand...
Click to collapse
Well...yea...so I tried to change some files in the temp folder of windows during the installation - and that worked. Dunno what I can make of that but I ll keep u updated. So much for now:
Current version: 2.xxx
Version to install: strange asian signes
Ok.
Finished - device not bricked.
I keep working
*Update: Hmpf...not working the way I hoped it would. I can install using the stock ruu with hboot 1.31....but its still not starting :/

I don't mean to be a downer, and good on you for giving it a go. But this has already been tried long ago.
Any modification you make will break the signature. The only way to get around it is to decrypt the signature so we can sign whatever zip files we want. Then we could flash an S-OFF HBOOT.

Illux said:
Well...yea...so I tried to change some files in the temp folder of windows during the installation - and that worked. Dunno what I can make of that but I ll keep u updated. So much for now:
Current version: 2.xxx
Version to install: strange asian signes
Ok.
Finished - device not bricked.
I keep working
*Update: Hmpf...not working the way I hoped it would. I can install using the stock ruu with hboot 1.31....but its still not starting :/
Click to expand...
Click to collapse
hello your hox has the cid VODAAP102???
you can make a small guide on how to do?

Sentinel196 said:
I don't mean to be a downer, and good on you for giving it a go. But this has already been tried long ago.
Any modification you make will break the signature. The only way to get around it is to decrypt the signature so we can sign whatever zip files we want. Then we could flash an S-OFF HBOOT.
Click to expand...
Click to collapse
Why is everyone so quick to shut down new attempts to achieve S-Off? The Church of Xmoo will only get you so far, especially when Xmoo doesn't even have a HOX any more.
Sent from my HTC One X using Tapatalk 2

Exactly 1 person attempting something is better than everyone just keeping quiet and whining about no S-Off.

New attempts with old techniques is not new attempts, it's confirming what we already know.
I'm not sure anybody would complain about new threads with new information or actual progress.

Exactly.
All I'm saying is that this idea has already been tried and verified as not working, and pointing this out so no-one wastes time trying something old when they could be trying something new.

Well he is trying .. Let him do it. No one can directly go to advance mathematics until he learns the basics.

Forget the zip file...
The 'new' bootloader is signed, and the 'existing bootloader' will verify the signature on the phone itself, before reflashing itself.
Sadly, and 'hack' on the PC side is wasted... a fully intact 'signed' package has to be sent to the phone/device.
The zip is irrelevant, it's opened by the RUU and the contents sent to the device in individual signed packages.
The procedure goes like this:
RUU / PC unpacks the zip.
The components of the zip are sent one by one to the phone ... i.e. Bootloader, Recovery, ROM etc.
Some of those components, particularly bootloader are signed, and the signature is checked on the phone.
You can change the files as much as you like on the PC... modifying the ROM image should still work (but of course, you'll create a corrupt ROM).
If you try to change the bootloader package (which is signed) then it will be rejected by the phone. A single byte change will result in an entirely new checksum / signature.
To generate the correct signature you need two things....
1) The algorithm for generating a new signature for the modified file
2) The 'key' which is used to encrypt the data (top secret!)
Statistically, it would take many years to 'brute force' guess the key, and you'd probably ruin your handset flashing it so many times too.
They key isn't likely to be leaked.
So, there's another way:
HTC allow some service centers to reflash the devices, but this requires special hardware and software that's not easy to replicate and hasn't been leaked yet. The presence of this hardware will 'permit' full reflashing of the device, and therefore S-OFF.

Have you guys see this?
--see below--

farhanito said:
Have you guys see this?
http://forum.xda-developers.com/showthread.php?p=5
Click to expand...
Click to collapse
broken link

Sentinel196 said:
broken link
Click to expand...
Click to collapse
arrgh, sorry.. darn tapatalk
http://forum.xda-developers.com/showpost.php?p=34888895&postcount=57
it's about Flash Image GUI by joeykrim

Based on my understanding, it simplifies the "fasboot flash recovery/boot" commands. Anything else I've missed?
Sent from my HTC Desire S using xda app-developers app

Skanob said:
Based on my understanding, it simplifies the "fasboot flash recovery/boot" commands. Anything else I've missed?
Sent from my HTC Desire S using xda app-developers app
Click to expand...
Click to collapse
It doesn't look like it's helping with the OP's objective....

Not s-off, i know...
But the possibility of flashing kernels without fastboot and plugging to a computer is nice enough i think..
Sent from my HTC One X using Tapatalk 2

I wish I knew how to link a post from another discussion area. There is a Russian dev in HTC DNA General who's posted subject S-Off Is Possible While its specific to the Snapdragon CPU and consensus is his claim is legit and to be made available soon, on pg 5, the dev mentions he's getting a HOX to try and get S-Off. Important point here is another dev taking an interest in a HOX. So someone here can kindly point out to him the challenges already attempted.
Sent from my Desire HD using xda app-developers app

Y2KoaS said:
I wish I knew how to link a post from another discussion area. There is a Russian dev in HTC DNA General who's posted subject S-Off Is Possible While its specific to the Snapdragon CPU and consensus is his claim is legit and to be made available soon, on pg 5, the dev mentions he's getting a HOX to try and get S-Off. Important point here is another dev taking an interest in a HOX. So someone here can kindly point out to him the challenges already attempted.
Sent from my Desire HD using xda app-developers app
Click to expand...
Click to collapse
Here you go. He says the method for achieving s-off on the DNA will work on a rate of 80% on the hox too. Sounds....strange. Anyways, heres the link to his post and thread.
http://forum.xda-developers.com/showthread.php?p=34960158
http://forum.xda-developers.com/showthread.php?t=2026033
-----------update-----------
Nevermind, he is talking about the At&t one x.
Sent from my HTC One X using xda premium

So close, but so far.
Sent from my HTC One X using Tapatalk 2

RUU for my phone

hello Guys i have an HTC ONE M9 CID NUM : VODAP304 and MID NUM : 0PJA10000 ..........where can i find an RUU for my phone??? thanks

When I go to HTC's RUU download page (http://www.htc.com/us/support/rom-downloads.html) I don't see anywhere to download for Vodafone - which is what I'm assuming you have from your CID.
What country are you in? HTC may be only showing me the options that are applicable to the USA, given the 'us' reference in the URL.

computerslayer said:
When I go to HTC's RUU download page (http://www.htc.com/us/support/rom-downloads.html) I don't see anywhere to download for Vodafone - which is what I'm assuming you have from your CID.
What country are you in? HTC may be only showing me the options that are applicable to the USA, given the 'us' reference in the URL.
Click to expand...
Click to collapse
I'm from Morocco but i think my phone is from Vodafone spain ( i think) .....

From your CID, it is Vodafone Spain (I should have Googled that first thing - sorry).
The only place that seems to offer file downloads for your phone is HTCdev (http://www.htcdev.com/devcenter/downloads). When I filter the files, I get different possible downloads. The thing is, I don't know enough to tell you which file (MR 1 or CSC) is the one you would want, or what you are supposed to do with it - they're both zip files.
I'm downloading one of them to open it and see what's inside. But it's a sign of hope that HTC is providing something. Unfortunately, I can't find any RUU files for Vodafone Spain. But maybe someone with more experience can help us from here.
I'll post what I find once the download finishes. My connection is slow, so it'll be a bit.
---------- Post added at 07:19 PM ---------- Previous post was at 06:27 PM ----------
Well, I learn something new each day - the files are for the radio and kernel. Unfortunately, that doesn't do anything for finding you a RUU file.

Byakuya88 said:
hello Guys i have an HTC ONE M9 CID NUM : VODAP304 and MID NUM : 0PJA10000 ..........where can i find an RUU for my phone??? thanks
Click to expand...
Click to collapse
computerslayer said:
From your CID, it is Vodafone Spain (I should have Googled that first thing - sorry).
The only place that seems to offer file downloads for your phone is HTCdev (http://www.htcdev.com/devcenter/downloads). When I filter the files, I get different possible downloads. The thing is, I don't know enough to tell you which file (MR 1 or CSC) is the one you would want, or what you are supposed to do with it - they're both zip files.
I'm downloading one of them to open it and see what's inside. But it's a sign of hope that HTC is providing something. Unfortunately, I can't find any RUU files for Vodafone Spain. But maybe someone with more experience can help us from here.
I'll post what I find once the download finishes. My connection is slow, so it'll be a bit.
---------- Post added at 07:19 PM ---------- Previous post was at 06:27 PM ----------
Well, I learn something new each day - the files are for the radio and kernel. Unfortunately, that doesn't do anything for finding you a RUU file.
Click to expand...
Click to collapse
If the file is not here >> http://www.androidruu.com/?developer=M9
you can request it here >> http://forum.xda-developers.com/one-m9/general/htc-one-m9-dump-t3060545

Fix Brick/Return To Stock

This thread is being started for those who have had the same issue as me. Around four days ago I made a very noob mistake of flashing a GSM firmware to get the latest Android Nougat firmware (do not do this by the way unless you know what you are doing, you will brick your phone) If you are using a Verizon HTC One M9 you are on CDMA not GSM if you don't now the difference please do your research. To continue, after flashing the firmware my phone would no longer recognize the sim card, boot looped, and I had no data connection. To solve the issue I asked about how to fix the problem and with the patience of a Developer/Contributor sandtod040 I was able to get my phone back to working order. Please visit his post and give him a thanks for me and donate if you can you will not regret it. Now too the solution part (Please keep in mind I am not an expert but I do care about helping people so I will do my best to help or give links for solutions).
You can use this file with S-off and S-on.
Step 1: Download this file from this link and please thank sandtod040 for his work. Rename it to 0PJAIMG.zip to make it easy ( Its a 0 not an O) and move it to your SD card. SD card needs to be formatted to FAT32 but FAT worked fine for me using TWRP to change the format if your using a computer and TWRP to move the file from your computer to your phone.
Step 2: If you are using TWRP (Please search other threads if you are using CWM as I am not familiar with it) boot into your boot loader by pressing volume down and power button and then select recovery.
Step 3: Once in go to Wipe and format data and select Yes (This will wipe everything).
Step 4: Using TWRP boot into download mode or repeat step 2 and scroll down to download mode. Once in download mode your phone should recognize the file you put on the SD card. Push volume up button to start flash and let the process complete fully until your phone boots up and your in the setup screen. It may not boot automatically( This happened for me so just wait a minute and then power it back on and let it do its thing).
Step 5: Congratulations your phone is back to 100% stock if you didn't run into any issues. Now OTA your phone to the latest security update and firmware and re-root if you want too Note: you will still be s-off and unlocked, this process does not change that.
If you have any questions or run into any errors please ask and I will try my best to help. And I am new to this so suggestions to the steps or any information I left out is welcomed thanks all and good luck!

does anyone no if the 4.14.617.6 | NOUGAT--VERIZON update has rolled out as of yet -
i am using cm-13 rite now and been waiting for nougat official firmware thanks 4 any info
jus noticed Dang sorry i posted in wrong location

Dayliter said:
does anyone no if the 4.14.617.6 | NOUGAT--VERIZON update has rolled out as of yet -
i am using cm-13 rite now and been waiting for nougat official firmware thanks 4 any info
jus noticed Dang sorry i posted in wrong location
Click to expand...
Click to collapse
It's cool your my first comment lol I haven't seen or heard anything yet I think it might be awhile before we get that.

Stock rom olmuyor
merhaba benim cihaz htc_himawl android 7.1.1 yükledim bazı dosyalar çalışmadığı için marsmallow geri dönmek istedim ama ne yaptıysam olmadı flaşlama ile firmware yükledim twrp yüklüydü oda gitti suan hangi romu yüklesem açılmıyor cihaz sadece dowload moda giriyor nasıl düzeltebilirim şimdiden teşekkürler.

gokhan534534 said:
merhaba benim cihaz htc_himawl android 7.1.1 yükledim bazı dosyalar çalışmadığı için marsmallow geri dönmek istedim ama ne yaptıysam olmadı flaşlama ile firmware yükledim twrp yüklüydü oda gitti suan hangi romu yüklesem açılmıyor cihaz sadece dowload moda giriyor nasıl düzeltebilirim şimdiden teşekkürler.
Click to expand...
Click to collapse
Could you please translate to English?

Gmoney1988 said:
Could you please translate to English?
Click to expand...
Click to collapse
I find using this tool for anything foreign unamerican international non-english works. (I'm poking fun, only in part towards you but generally towards xenophobic users)
The translated text:
"Hi i have installed htc_himawl android 7.1.1 on my device i wanted to go back to marsmallow because some of the files did not work but i didnt install firmware with flashing twrp i installed the room which isnt loading roms i am just loading the dowload mode,"

Gmoney1988 said:
Could you please translate to English?
Click to expand...
Click to collapse
Ignore this post I accidentally quoted myself.

gokhan534534 said:
merhaba benim cihaz htc_himawl android 7.1.1 yükledim bazı dosyalar çalışmadığı için marsmallow geri dönmek istedim ama ne yaptıysam olmadı flaşlama ile firmware yükledim twrp yüklüydü oda gitti suan hangi romu yüklesem açılmıyor cihaz sadece dowload moda giriyor nasıl düzeltebilirim şimdiden teşekkürler.
Click to expand...
Click to collapse
After getting the translation from the other poster. You don't use TWRP to flash the Ruu, you have to do it from download mode, just follow my instructions and flash the latest Ruu to return back to stock which will be on latest marshmallow and then just OTA to latest firmware. Hope that helps.

I made the mistake of many inexperienced, who do not investigate enough before playing.
I want to correct my mistake, and for this reason I have been reading this thread for a long time. I am downloading the files but, for security, I leave my information here, as long as I confirm that I am doing well, regarding the smartphone I have ...
These are the getvar data:
(Bootloader) kernel: lk
(Bootloader) product: htc_himauhl
(Bootloader) version: 1.0
(Bootloader) serialno: I'll reserve it
(Bootloader) current-slot:
(Bootloader) imei: I'll reserve it
(Bootloader) version-main: 4.14.401.7
(Bootloader) boot-mode: download
(Bootloader) version-baseband: 01.01_U114401011_117.00.61117G_2_F
(Bootloader) version-bootloader: 1.0.0.0000
(Bootloader) mid: 0PJA30000
(Bootloader) cid: 11111111​
Click to expand...
Click to collapse
---------- Post added at 10:24 AM ---------- Previous post was at 10:12 AM ----------
One question, what does roms recommend, after resetting the smartphone?

Fix the rename:
You have in this instructions ''0PJAIGM'', correct form: ''0PJAIMG''...

zalazdev said:
I made the mistake of many inexperienced, who do not investigate enough before playing.
I want to correct my mistake, and for this reason I have been reading this thread for a long time. I am downloading the files but, for security, I leave my information here, as long as I confirm that I am doing well, regarding the smartphone I have ...
These are the getvar data:
---------- Post added at 10:24 AM ---------- Previous post was at 10:12 AM ----------
One question, what does roms recommend, after resetting the smartphone?
Click to expand...
Click to collapse
https://forum.xda-developers.com/verizon-one-m9/help/rom-advanced-calling-t3550901
Scroll down in the thread. I am using Leedroid at the moment while I wait for @santod040 Nougat. Rom 4.23.617.1

how about to fix other version? i have M9 Dev Edition, done RUU, but nothing change, any idea??
---------- Post added at 09:30 AM ---------- Previous post was at 08:39 AM ----------
is noone have m9 anymore??

test

is this forum dead?

Halo

Sound quality

How to restore the boomsound sound quality after flashing a custom rom?
I'm experiencing crackling.

A Sense ROM presumably (otherwise you wouldn't have Boomsound, and won't)? What ROM?
Firmware might need do be updated. Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).

redpoint73 said:
A Sense ROM presumably (otherwise you wouldn't have Boomsound, and won't)? What ROM?
Firmware might need do be updated. Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Click to expand...
Click to collapse
INFOversion: 0.5
INFOversion-bootloader: 3.19.0.0000
INFOversion-baseband: 1.29.214500021.12G
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 6.15.720.2
INFOversion-misc: PVT SHIP S-ON
INFOmeid: 00000000000000
INFOproduct: m8_ul
INFOplatform: hTCBmsm8974
INFOmodelid: 0P6B65000
INFOcidnum: HTC__038
INFObattery-status: good
INFObattery-voltage: 0mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 205bdca3
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
Using aicp 7.1.2 currently

utkarsh102 said:
INFOversion-baseband: 1.29.214500021.12G
INFOversion-main: 6.15.720.2
Using aicp 7.1.2 currently
Click to expand...
Click to collapse
Your firmware is up to date, based on the details (main version, and also radio baseband) above.
AICP is a AOSP ROM. It doesn't have the Sense framework, and therefore doesn't have Boomsound, and you can't get it.
But crackling is also not normal. I don't use AOSP ROMs on this device, so can't give much advice on the crackling problem. You should check the thread for that particular ROM, to see if anyone else reported audio issues.
If you want better audio (Boomsound type experience), you might look at Viper4Android, ARISE, etc. I personally use V4ARISE, and like it better than Boomsound, as ARISE has a lot of options and customization, which allow me to tailor the sound to my liking.
But I don't think audio mods will address the crackling issue. That sounds more ROM related, and should be addressed first.

redpoint73 said:
Your firmware is up to date, based on the details (main version, and also radio baseband) above.
AICP is a AOSP ROM. It doesn't have the Sense framework, and therefore doesn't have Boomsound, and you can't get it.
But crackling is also not normal. I don't use AOSP ROMs on this device, so can't give much advice on the crackling problem. You should check the thread for that particular ROM, to see if anyone else reported audio issues.
If you want better audio (Boomsound type experience), you might look at Viper4Android, ARISE, etc. I personally use V4ARISE, and like it better than Boomsound, as ARISE has a lot of options and customization, which allow me to tailor the sound to my liking.
But I don't think audio mods will address the crackling issue. That sounds more ROM related, and should be addressed first.
Click to expand...
Click to collapse
Thanks a lot. I think so too. That crackling is not hardware based. Since i was using the official sense rom before this and there was no such issue.
I shall try flashing a sense rom again and see if the issue still persists. Thanks for helping.