Related
To mods, sorry, but I checked the "is this a question" box my mistake, the following is not a question but asking for assistance.
Hello, first off apologies if this has been asked before and thanks in advance for any assistance offered.
The good folks at HTC decided to make a few changes from ICS to JB that have seriously in my view are a downgrade.
So here are the specs:
Current:
HBOOT is now 2.14
ROM: 3.70 (Telstra variant)
I downloaded the RUU_Evita_Telstra_1.89 but get error 140: Wrong bootloader, and I cant find the previous 4.0.4 stock firmware which I think from memory was RUU_Evita_UL_Telstra_WWE_2.70
So after doing some research I found that I need the 1.14 bootloader as the upgrade from ICS to JB changed the bootloader.
Since I have no idea how to change the bootloader I need some help (never had these issues with Samsung galaxy S II, much easier using odin to flash what ever firmware you wanted).
From memory, the previous version firmware was:
- 4.0.4 2.70 (Telstra)
Note: I have not rooted or unlocked the bootloader, I am not into using CFW all I want to use is the stock firmware.
If anyone can provide assistance then thank you very much.
I look forward to reading all replies and all help provided.
Again apologies if this has been brought up before but after 3 days of searching and not finding anything relevant its time to ask for assistance.
Thread still belongs in Q&A moved
Previous version before the Jelly Bean update is 2.40 with hboot 1.14
I think you might be stuck unless the jet application works on the new hboot but even for that to work (I'm not saying it will, I'm not sure if anybody knows yet) you already need to be unlocked with SU and a custom recovery.
Seeing as you're completely stock I think you're more than likely stuck with it - why would you wanna downgrade from Jelly Bean goodness anyways?
Bump to ask what's better in ics then jb for yourself?
I would have to be loco to go back to ics after this smoothness that jb has brought us.
So loco or what?
WR
Sent from my Jelly Bean One XL
WarRaven said:
Bump to ask what's better in ics then jb for yourself?
I would have to be loco to go back to ics after this smoothness that jb has brought us.
So loco or what?
WR
Sent from my Jelly Bean One XL
Click to expand...
Click to collapse
Whats better?
Well I cant use the apps I mentioned in JB, but that is a 3rd party reason, the other main thing is use of MTP over proper USB Mass Storage Mode connection.
HTC have removed the "Connect to PC" option which allowed the One XL to mount as a USB Mass Storage device which which great for the car audio system I use, my Sony deck (touch screen) cant read MTP mode.
So yeah hence why I am asking for assistance to downgrade back to ICS, preferably ICS 4.0.4 2.70 for the One XL also the modem radio is is now worse in both 3G dual band 850/2100 and in 4G 1800 ...
I used to get RSCP -55 HSPA+ at home now I am lucky to get RSCP -105 HSDPA and its not the network as my Galaxy S II (the I9100T variant) with actually the stock I9100 XSA 4.0.4 firmware gets RSCP -55 HSPA+ here.
So yeah While JB is smooth and all that to me its a downgrade in performance hence why I am asking for help to change the bootloader back to HBOOT 1.14 and thus re-instal the RUU_EVITA_UL_Telstra_WWE_2.70 firmware again.
Any help is very much appreciated as HTC have told me to basically they are not going to help.
I cant find where you mentioned apps that do not work. I can understand your issue with the change to USB. Perhaps that can be overcome with a build.prop change?
Eg:
persist.sys.usb.config=mass_storage,adb
Or get a rooted 3.17 and try some of the usb mass storage enabling apps on the Play Store.
Or wait for a dev to make a kernel that will make this work
There was no 2.70 version, it was 2.40 previously with Telstra.
You have all the below available to you.
Perhaps with Jet and some other trickery you could get back to 1.89 then update forwards to 2.40. You would really be one of the first users to try it and may kill your phone. You need to manage the hboot and current software version checks at very least.
1.81.841.1
RUU - RUU_Evita_UL_Telstra_WWE_1.81.841.1_R_Radio_0.17a.32.09.03_2_10.85.32.16L_release_259804_signed.exe
1.89.841.9
OTA - http://fotadl.htc.com//OTA_Evita_UL...81.841.1_R_release_266785ap9qro3i4pvkmhv0.zip
RUU - RUU_Evita_UL_Telstra_WWE_1.89.841.9_Radio_0.18c.32.09.01_10.93a.32.20L_release_266699_signed.exe
2.40.841.4
OTA - http://fotadl.htc.com/OTA_EVITA_UL_...1.89.841.9_release_279477r07a3nyy05j4vcis.zip
RUU - Not leaked
3.17.841.2
OTA - http://fotadl.htc.com/OTA_EVITA_UL_...128.32.34a_release_2997538hizl4svcm80o4g1.zip
RUU - Not leaked
twistedddx said:
I cant find where you mentioned apps that do not work. I can understand your issue with the change to USB. Perhaps that can be overcome with a build.prop change?
Eg:
persist.sys.usb.config=mass_storage,adb
Or get a rooted 3.17 and try some of the usb mass storage enabling apps on the Play Store.
Or wait for a dev to make a kernel that will make this work
There was no 2.70 version, it was 2.40 previously with Telstra.
You have all the below available to you.
Perhaps with Jet and some other trickery you could get back to 1.89 then update forwards to 2.40. You would really be one of the first users to try it and may kill your phone. You need to manage the hboot and current software version checks at very least.
Ah ok, no wonder I could not find RUU_Evita_UL_Telstra_WWE_2.70 ... my mistake, I am not that much into modding my One XL as much as the Galaxy S II, Note I and Note II that I have so I dont pay that much attention to it.
I dont want to root and unlock the One XL as its not mine (company) hence why I need stock ROM, but what annoyed me was HTC not mentioning that several the changes made which to me are a downgrade for what I need to handset for.
I will try to the 2.40 ROM as from the research I have done so far suggests that it should work with HBOOT 2.14 version.
Just another question if I may, so this file is a ZIP file and not an exe file, so in order to install it I will need to use something like clockworkmod?
If so I am not that good at being able to figure that out (again its not like using ODIN for Samsung), I hate to ask but how is that done again?
Again many thanks and as its 2013 here in Sydney happy new year!
2013!
Click to expand...
Click to collapse
You can't use the ota to roll back like this. It does not even help much going forwards versions with your phone locked. You would need the phone to get the download itself.
Ruu would be your only hope, and your 2.14 hboot will not accept the 2.40 Ruu (which is not publically available) as it only has 1.14 hboot.
There is 100% no chance you can downgrade your phone without unlocking it even if the 2.40 Ruu was available, which it isn't.
There is only very minimal chance you can downgrade even after unlocking it.
Ps your OP says you are running 3.70, is that right or is it just 3.17?
twistedddx said:
You can't use the ota to roll back like this. It does not even help much going forwards versions with your phone locked. You would need the phone to get the download itself.
Ruu would be your only hope, and your 2.14 hboot will not accept the 2.40 Ruu (which is not publically available) as it only has 1.14 hboot.
There is 100% no chance you can downgrade your phone without unlocking it even if the 2.40 Ruu was available, which it isn't.
There is only very minimal chance you can downgrade even after unlocking it.
Click to expand...
Click to collapse
Thats what I thought, stupid HTC and Telstra for screwing up, the phone in short is screwed with the JB update, tonight could not get any signal from the network to it whereas with ICS 4.0.4 it worked 100% in the same spot the previous month and again its not the network as my other Andorid devices are working A1.
One XL RSCP -110 UMTS v Galaxy Note RSCP -60 HSPA+, and this is supposed to be a blue tick (means works in regional/rural areas without need for external antenna) handset.
Do you have any idea if and when the public RUU 2.40 will be able to download? then again if it wont work with HB 21.4 then how do I go about changing the HBOOT back to 1.14? Again I have no idea with HTC, they have to make it hard unlike Samsung, hell I would rather make changes to LG Qualcomm based Brew OS and install that firmware using Qualcomm Tools 4.5 or use Phoenix to change firmwares on my spare Nokia N8 then try to figure out how to mod this HTC device.
HTC advised me to go back to the dealer (it was bought online so that rules that out), made a call to Telstra, they said not our problem go to HTC, HTC said go back to dealer, in other words chasing my tail like a dog would going in circles, as a last resort I made a call to a authorized service centre, they said cant be done under warranty but can be done for a price, they want something like *$350 AUD to downgrade it (seriously fonebiz), obviously my company said no and I cant change the handset either as need 4G support.
So you can see why I am trying to find a solution to fixing HTC and Telstra created issues via these forums.
Again any assistance would be greatly appreciated
*the $350 would b e to replace the mainboard with a new mainboard that has 4.0.4 ICS on it already but with a blank IMEI and as such they would flash the NAND NV with the numbers from the replaced mainboard ... also this would also end Warranty for the handset by HTC and only provide warranty by Fonebiz for 3 months on the replaced mainboard ...
As I dont own the handset I cant take that option, which is why I cant root or unlock it to use CFW, believe me if I did I would of done it ages ago, which is why I dont know anything about HTC as my personal handsets are from Samsung (much easier to modd IMHO).
I have uploaded two screen grabs.
ARGHHHH, To many numbers going through my head right now,
According to the Software info:
Version: Android 4.1.1
Sense: Sense 4+
Software Number: 3.17.841.2
HTC SDK API Level: 4.63
All the other numbers don't matter. Just the hboot 2.14 and the build 3.17.
It is unlikely the 2.40 Ruu will leak. Not all always leak. You could ask in places that Ruu leaks are found though. Often they need to be purchased on the black market. Plus the Ruu is useless to you unless you unlock and start forcefully downgrading things.
You are wasting your time unless you unlock, use jet to downgrade the hboot and alter the software build to 1.00.
Or buy a new main board.
Or live with the new update. Use a usb stick for $7 for the radio or Bluetooth or buy a new head unit.
No idea about coverage personally I did not see it decrease because of the update. But it is what it is. If you purchased from Telstra you would have a leg to stand on complaining.
Samsung devices are not all rosey and good. There is a long list of variants of s2 and s3 which you can't do squat with.
Your HTC one xl has options you can try but you are choosing not to do them.
Simply call the complaints dept at Telstra, explain that the latest ota has made the phone useless to you (not support they're useless). They will most likely credit the account or offer to swap you to a different blue tick device, it's a shame they're aren't any good ones
Sent from my HTC One XL using xda app-developers app
The one xl is a blue tick device. The user has supplied their own phone, it was not purchased from Telstra. I doubt they will offer a new handset.
Where do I find JET from?
The handset is from Telstra it was purchased online though Telstra website so there is no dealer, Telstra have said they don't help neither will HTC.
The One XL over the Galaxy Note? The Gnote other than not having 4G radio is simply better and again much easier to flash what ever stock ROM you want, simply use the new updates Check_Fus program find your model and download straight from Samsung server then use either old ODIN or need ODIN and flash what ever firmware or modem you want.
So being where XDA is supposed to be be great at providing technical advice and such I would of thought that people here would be willing and some have to help out and that others Herr with the One XL have been able to downgrade or go back to stock firmware and then help out those who don't know how ...
As for the USB options, putting on a USB KEY/PASSPORT device iss not a viable option at all, if that were the case I would not have brought it up here, I do a lot of driving way to much and am on the road a lot thus I need power and since 4G consumes vast ammounts the old way of USB would charge the handset (much faster than using cigarette lighter plug) also I don't get the static in the audik playback from the aux/lighter connection method.
So again is there anyone who can further help me out or do I simply sell the HTC and go buy another GNote (forget GNote2 no proper USB option and again apps that I use do not work in 4.1.1)
???
I have been trying to help. I have said what you could try to do several times, but you have never attempted to do it.
Comparing a Nexus device with a non-Nexus device when it comes to ease of customizing is pointless. That is the point of Nexus devices, if you wanted one you should have bought one??
If you purchased from Telstra, you have every right to complain to them that an update that they approved has significantly reduced the coverage of your phone without warning. Just claim you purchased the device due to it being blue ticked by Telstra and the range it offered in the areas you are using it in. Demand they offer a way to return your phone to its original coverage via a downgrade or another update.
1)You need to unlock. You have no chance of performing this unofficial software downgrade path without unlocking. If that is unacceptable, sell the phone.
http://www.htcdev.com
2)You likely want to use Jet to attempt to downgrade the hboot back to 1.09. You also get the bonus of supercid allowing using any RUU you want not just Telstra, so the lack of Telstra 2.40 RUU becomes less important, just use HK 2.42 RUU instead.
http://forum.xda-developers.com/showthread.php?t=1982442
3)I believe you also need to fix up another version sitting on another partition that the RUU will check
http://forum.xda-developers.com/showthread.php?t=1671135
4)Flash a RUU
Telstra 1.89 if you like:
RUU_Evita_UL_Telstra_WWE_1.89.841.9_Radio_0.18c.32.09.01_10.93a.32.20L_release_266699_signed.exe
Personally I would flash Hong Kong 2.42. It is 4.0.4 and should be able to install with hboot 1.09.
The Hong Kong 2.42 ROM is almost identical to Telstra 2.40.
RUU_EVITA_UL_ICS_40_S_hTC_Asia_HK_2.42.708.3_Radio_0.20os.32.09.15_10.113.32.28L_release_286715_signed.exe
I dont think anyone else has attempted downgrading the hboot 2.14 back to 1.09.
That is why there is no long list of users with previous experiences in doing it. You are the first, once you have got the answer you could tell everyone else how you went.
Good luck.
EDIT: Apparently someone else has tried this, it allowed him to flash 1.81 RUU (would not have been my pick but whatever) and it ended in bricking the phone.
Just a big fat warning
twistedddx said:
I have been trying to help. I have said what you could try to do several times, but you have never attempted to do it.
Comparing a Nexus device with a non-Nexus device when it comes to ease of customizing is pointless. That is the point of Nexus devices, if you wanted one you should have bought one??
If you purchased from Telstra, you have every right to complain to them that an update that they approved has significantly reduced the coverage of your phone without warning. Just claim you purchased the device due to it being blue ticked by Telstra and the range it offered in the areas you are using it in. Demand they offer a way to return your phone to its original coverage via a downgrade or another update.
1)You need to unlock. You have no chance of performing this unofficial software downgrade path without unlocking. If that is unacceptable, sell the phone.
http://www.htcdev.com
2)You likely want to use Jet to attempt to downgrade the hboot back to 1.09. You also get the bonus of supercid allowing using any RUU you want not just Telstra, so the lack of Telstra 2.40 RUU becomes less important, just use HK 2.42 RUU instead.
http://forum.xda-developers.com/showthread.php?t=1982442
3)I believe you also need to fix up another version sitting on another partition that the RUU will check
http://forum.xda-developers.com/showthread.php?t=1671135
4)Flash a RUU
Telstra 1.89 if you like:
RUU_Evita_UL_Telstra_WWE_1.89.841.9_Radio_0.18c.32.09.01_10.93a.32.20L_release_266699_signed.exe
Personally I would flash Hong Kong 2.42. It is 4.0.4 and should be able to install with hboot 1.09.
The Hong Kong 2.42 ROM is almost identical to Telstra 2.40.
RUU_EVITA_UL_ICS_40_S_hTC_Asia_HK_2.42.708.3_Radio_0.20os.32.09.15_10.113.32.28L_release_286715_signed.exe
I dont think anyone else has attempted downgrading the hboot 2.14 back to 1.09.
That is why there is no long list of users with previous experiences in doing it. You are the first, once you have got the answer you could tell everyone else how you went.
Good luck.
Click to expand...
Click to collapse
I would totally agree with this,take it up with Telstra if they don't come to the party lodge a complaint with the TIO .I have had issues with them with this phone, they replaced the first one because it did not perform to blue tick performance, This one was crap until I unlocked the boot loader and rooted,they offered to send it away and repair it but I told them what I had done to fix it, and they said if it was still no good in the future to let them know and the offer still stands.
After a very heated conversation with HTC they have agreed that they have a made an error in removing "Connect to PC" option thus proper USB Mass Storage Mode, in the future 4.1.2 update it will be returned, so success on that end, for the time being they have emailed me a letter to take to FoneBiz which advises FoneBiz that the One XL is to be reset to stock 4.0.4 2.40 Telstra ICS firmware free of charge to the owner.
It took 2 goes with HTC for HTC to admit they screwed up, as a sign of good faith they are also sending me a new One X+ since i took time to basically verbally belt the crap out them, which I have no intention of using as it will be up on Ebay for sale once it arrives.
So now I have to take One XL to FoneBiz to get it back to the way it was.
You can also thank for getting HTC to reverse a most silly decision of forcing owners to use MTP mode, it will still be there but proper USB Mass Storage mode will return in the next update (when ever that might be).
For the time being I am using my work Telstra SIM in my Galaxy Note and that SIM is being used in the One XL.
I'm running stock RUU on Verizon's latest 1.55.605.2. All radios, etc are current. I'm rooted with s-off. Now my question is am I able to flash a rom like a GPE that is based off the 4.4.4 update even though it hasn't been rolled out yet to Verizon. I am very confused because I see some roms based on that update despite the Ota not being available. I've tried flashing a couple of roms that are 4.4.4 based but was unable to. Why can't I run a 4.4.4 rom even though I am s-off? And how are developers basing their roms off of it when it hasn't been released to Verizon. I am just completely lost.
I think you're confusing Sense with Android (GPE). Sense is currently at 4.4.2 and about to be 4.4.3 later this week. (HTC is going to skip 4.4.4 because the updates to 4.4.4 are rolled into Sense's 4.4.3.)
You are able to flash GPE based on 4.4.4 or 4.4.3 because the Android version is unrelated to the baseband version. Don't hold me to that though. With Samsung (what I had before this) baseband enforced a minimum Android API level (OS version) but not a maximum. For example, when I flashed MJA, I had to use 4.3 and later. Could not go back to 4.2 or prior. But never mind that, that's Samsung talk. But I assume it's the same. Samsung uses alphanumeric, HTC uses what looks like IP addresses but aren't. 1.55.605.2 is indeed the latest for the VZW One M8.
I don't know why you were unable to flash 4.4.4 ROMs. Sometimes an older version of your recovery (e.g. TWRP) can make it impossible to flash recent ROMs. Check and make sure your recovery is current.
You can definitely flash either of our GPEs, but be warned they are not ready for prime time just yet. The current issue is that signal will drop irregularly in both of them. But we have some smart people working on figuring that out. GPE is typically only available for GSM phones (e.g. AT&T, T-Mobile, International unlocked) and making it work with CDMA (i.e. Verizon) is a nontrivial task. But they're trying. And for some, the issues are forgivable. For me... I'm patiently watching and waiting.
Lastly, you won't get the OTA because you're S-Off and/or because you're rooted and/or because you have a custom recovery. You'll never officially have Sense based on 4.4.4 because HTC's not doing it. Next week or by the weekend, we'll probably start seeing Sense ROMs based on 4.4.3 since that's what's coming.
You're able to flash GPE simply because you're s-off. Once you have s-off, you can flash anything you desire. No guarantees it's going to work though. If the rom isn't ported for Verizon, it's not going to work. You have to do a little homework before you flash a given rom. Read through the thread. If nothing else, search the rom thread for Verizon. More than likely somebody has asked if it will work on Verizon and if so, you'll find your answer.
As to flashing back to an earlier version, once again, you're s-off. You should be able to flash anything you want. I'm somewhat new to HTC also but from what I've read, I don't think you'd have any problem going back. I know with Moto phones it wasn't possible but that was because the bootloader wasn't unlocked and the newer version came with a new bootloader. Since it was locked and the new bootloader had a different signature than the old, you couldn't go back. You're unlocked on here though and it should take anything you throw at it. Old bootloader should be no problem. Should be able to go back. Somebody can correct me if I'm wrong but from what I've read, that's how I see it.
There are two gpe ROMs in the Verizon Android development thread which have been specifically ported and catered to the Verizon devices. Both sjould suffice. Under NO circumstance would I recommend that you flash a GPE ROM from the unbranded HTC development. Same goes for GPE/SENSE kernels.
Hello!
I have a Verizon HTC ONE M8 that no matter what it won't download the new update. I've bought 3 of them (identical) 1 month ago from Ebay. One of them was able to receive the update. On the other two i keep receiving the following message: "We were not able to download this update. To retry, go to Settings > Software update. "
My device is S-off (after a lot of effort). I've tried to get rid of all the bloatware and many more by flashing a new ROM. I have tried flashing ViperROM, ARHD, Clean ROM using TWRP Recovery, without any success. All of my attempts got stuck at the booting screen for more than 30 minutes without any success of booting into the OS. Clean ROM even refused to flash properly. Keep in mind that all the ROMs that I've flashed were based on 4.4.2 firmware, the one that my phone came with, not 4.4.3. I've searched on this forum for a flashable 4.4.3 OTA update, but no success either. What's to be done !?!? All my attempts of installing a new OS failed. Please HELP!
P.S: I'm a newbie when it comes to all of this stuff. First time doing S-off/ installing custom ROMs.
hgpt said:
Hello!
I have a Verizon HTC ONE M8 that no matter what it won't download the new update. I've bought 3 of them (identical) 1 month ago from Ebay. One of them was able to receive the update. On the other two i keep receiving the following message: "We were not able to download this update. To retry, go to Settings > Software update. "
My device is S-off (after a lot of effort). I've tried to get rid of all the bloatware and many more by flashing a new ROM. I have tried flashing ViperROM, ARHD, Clean ROM using TWRP Recovery, without any success. All of my attempts got stuck at the booting screen for more than 30 minutes without any success of booting into the OS. Clean ROM even refused to flash properly. Keep in mind that all the ROMs that I've flashed were based on 4.4.2 firmware, the one that my phone came with, not 4.4.3. I've searched on this forum for a flashable 4.4.3 OTA update, but no success either. What's to be done !?!? All my attempts of installing a new OS failed. Please HELP!
P.S: I'm a newbie when it comes to all of this stuff. First time doing S-off/ installing custom ROMs.
Click to expand...
Click to collapse
You probably won't be able to take the OTA with a custom recovery, it has to be stock. Best bet is to flash the 4.4.3 firmware from the development section since you're s-off, then flash an already rooted stock 4.4.3 rom. It's been a while since I've done this stuff so if I mentioned some incorrect info, my apologies.
dynofrk666 said:
You probably won't be able to take the OTA with a custom recovery, it has to be stock. Best bet is to flash the 4.4.3 firmware from the development section since you're s-off, then flash an already rooted stock 4.4.3 rom. It's been a while since I've done this stuff so if I mentioned some incorrect info, my apologies.
Click to expand...
Click to collapse
I flashed back again the stock ROM and i keep receiving the same message over and over again. No TWRP recovery this time, just the red triangle. I guess my best bet is to try and flash the CleanROM ODEX 4.4.3 as mentinoned here: @branmuffin17
I'll come back with the results.
hgpt said:
I flashed back again the stock ROM and i keep receiving the same message over and over again. No TWRP recovery this time, just the red triangle. I guess my best bet is to try and flash the CleanROM ODEX 4.4.3 as mentinoned here: @branmuffin17
I'll come back with the results.
Click to expand...
Click to collapse
If you are on the old firmware you need to update firmware separately.
And btw, if you freeze just one system app that can cause a Vzw ota to fail.
Question.....Is the phone active on your account? I also had one in the drawer and got the same error till I switched it to the active device on my account.
It honestly sounds like there is something preventing the ota to even download, if that's the case use dottat's ruu to return to a clean slate, if it still won't download the OTA then I would be willing to bet money that they are defective or not genuine Verizon M8s And if I were to guess it's more of the latter that would be the only valid reason every Rom you've tried fails no matter what.
sent from space
runandhide05 said:
It honestly sounds like there is something preventing the ota to even download, if that's the case use dottat's ruu to return to a clean slate, if it still won't download the OTA then I would be willing to bet money that they are defective or not genuine Verizon M8s And if I were to guess it's more of the latter that would be the only valid reason every Rom you've tried fails no matter what.
sent from space
Click to expand...
Click to collapse
Based on what you said i went on some websites to check the IMEI/ESN of the device it seems to be OK. After that i went to the Verizon Wireless website to try an activate my phone and when it comes to "Enter your Device ID to check eligibility", I type in the IMEI and the following message apears: "The phone associated with the Device ID you entered is not compatible with the Verizon Wireless network." To me is strange because on the back of the phone it says Verizon 4G LTE. When it comes to the identity of the phone it is a HTC6525LVW. The phone is GSM Unlocked (I use my phone in Europe so i needed it to be GSM unlocked). More strange it is to me that i don't receive the same message when i type in the IMEI of the others Verizon GSM unlocked HTC's ONE M8 that i bought along with this one.
I guess my only chance is to flash the new firmware @here[and after that flash the Deoxed 4.4.3 Stock Clean ROM @here. If it's not going to work i really don't know what's else it's to be done.
hgpt said:
Based on what you said i went on some websites to check the IMEI/ESN of the device it seems to be OK. After that i went to the Verizon Wireless website to try an activate my phone and when it comes to "Enter your Device ID to check eligibility", I type in the IMEI and the following message apears: "The phone associated with the Device ID you entered is not compatible with the Verizon Wireless network." To me is strange because on the back of the phone it says Verizon 4G LTE. When it comes to the identity of the phone it is a HTC6525LVW. The phone is GSM Unlocked (I use my phone in Europe so i needed it to be GSM unlocked). More strange it is to me that i don't receive the same message when i type in the IMEI of the others Verizon GSM unlocked HTC's ONE M8 that i bought along with this one.
I guess my only chance is to flash the new firmware @here[and after that flash the Deoxed 4.4.3 Stock Clean ROM @here. If it's not going to work i really don't know what's else it's to be done.
Click to expand...
Click to collapse
The message from the vzw site tells me something is not right.
Google goophone or knock off gs4, the goophone also has an m8 now too... Even with all the branding and everything. And I've seen some gs4s that run what appears to be TouchWiz cloned to a T.
I'd try calling vzw and talk to a rep and it's possible that they could give you more info other than just what the site said.
sent from space
So I did what I've said:
1. Installed firmware provided here @Tigerstown
2. Installed the Odex Stock Rooted ROM proivede here: @scrosler
I am pleased to announce you that everything is fully functional now
Phone is showing:
Android Version: 4.4.3
Software number: CleanROM 2.0.0 (after flashing it from @here)
Baseband version: 1.09.20.0702
Bulid number: 2.21.605.2 CL362279 release-keys
After managing to flash the 4.4.3 version of Android all went up without any problem. Tried to ARHD but it's still not booting. After that installed ViperROM which went up all, but to me it is not the pure HTC Sense 6 experience i was looking about and all that customization is to much for me, so i flashed CleanROM 2.0.0 and here I am. Everything is as it should be: no bloatware, pure HTC Sense 6, optimized performance... and above all the mobile hotspot is now fully functional, not to mention the EXT SAVER.
As a conclusion, to all that guys that are not able to update to the 4.4.3 version via the OTA updates provided by Verizon do what I did above (steps 1 and 2).
ATTENTION: Your device needs to be S-Off and bootloader unlocked + custom recovery!!!
Another thing worth to be mentioned: it would be great if the admins could flag this thread, cause I've seen so many users on different forums that are not able to update via the OTAs.
In the end i would like to thank to all the devs out there for their work and to the users for their support. Cheers!:highfive:
I have a VZW htc one m8, Firmware 2.21.605.2 and am trying to update the firmware to 3.28.
Every time I try to update to 3.28 i get the error FAILED (remote: 41 model id check fail).
I have super CID on and tried everything i can think of.
I would love to check out some of the roms but I dont have much luck with them.....might be a different issue all together but They get stuck on the HTC screen and do not load.
Can anyone offer any help as to get the firmware updated.
I tried this on ADB fastboot
Wrong software Update
blackdrag0n said:
I have a VZW htc one m8, Firmware 2.21.605.2 and am trying to update the firmware to 3.28.
Every time I try to update to 3.28 i get the error FAILED (remote: 41 model id check fail).
I have super CID on and tried everything i can think of.
I would love to check out some of the roms but I dont have much luck with them.....might be a different issue all together but They get stuck on the HTC screen and do not load.
Can anyone offer any help as to get the firmware updated.
I tried this on ADB fastboot
Click to expand...
Click to collapse
You can not Update your HTC M8 Verizon with this Update who is specific for the HTC M8 Developer Edition *
new software update will come soon to our Verizon model HTC M8, we have to wait.
You have the latest updated software version 2.21.605.2 no need to update.
Another question then, why the heck would several roms just get stuck on the HTC screen and never load into them?
for example the Android Revolution HD 21. Installs just fine but get stuck on the HTC screen and never moves.
Thanks for the reply
blackdrag0n said:
Another question then, why the heck would several roms just get stuck on the HTC screen and never load into them?
for example the Android Revolution HD 21. Installs just fine but get stuck on the HTC screen and never moves.
Thanks for the reply
Click to expand...
Click to collapse
You need to have the latest firmware for that ROM to boot...We don't have that just yet...should be soon. Only flash firmware specific to Verizon or you will hard brick your phone. SuperCID is pretty useless for the Verizon model for that reason.
brholt6 said:
You need to have the latest firmware for that ROM to boot...We don't have that just yet...should be soon. Only flash firmware specific to Verizon or you will hard brick your phone. SuperCID is pretty useless for the Verizon model for that reason.
Click to expand...
Click to collapse
That would explain a lot, thank you very much.
blackdrag0n said:
Another question then, why the heck would several roms just get stuck on the HTC screen and never load into them?
for example the Android Revolution HD 21. Installs just fine but get stuck on the HTC screen and never moves.
Thanks for the reply
Click to expand...
Click to collapse
You are getting stuck in those rom because you are trying to flash incompatible Roms* for the M8 Verizon, you should stick
with the right VZW HTC m8 thread here http://forum.xda-developers.com/verizon-htc-one-m8/development
also if you still having problems with any rom here then flash other Custom recovery
http://techerrata.com/browse/twrp2/m8_wlv
user reporting version 2.7.1 0 TWRP as working in all roms. but you can try the new one first.
You have the lastest build software VZW 2.21.605.2 , check your (firmware) Baseband version should be 1.09.20.0702 (new)
if you got that you will able to flash any Rom in the thread above
(From later on in this thread)
Jaxas said:
Hello again, sorry to bother you guys but I'm seeing a surprising amount of conflicting information about this...
So I'm trying to upgrade to Nougat, but I'm having some troubles figuring out what I need to do for that.
I know I need to get my phone back to stock so I can accept the OTA update, but I'm not sure how to go about that.
My phone currently:
- Phone Model: HTC One A9 (Sprint - 2PQ93)
- Android Version: 6.0.1
- Software Version: 1.60.651.4
- Root: Yes
- Recovery: TWRP v2.8.8.2_CPTB-TEST2
- S: ON
- Bootloader: Unlocked
- Software Status: Modified
So as far as I'm aware, I need to restore the Stock recovery (how?), re-flash the RUU for my current software version, and then... relock the bootloader? Maybe?
So my questions are...
- How do I actually restore the stock recovery?
- Are there any steps I'm missing?
- Do I need to re-lock the bootloader, or does that not matter?
(- Is there anything I need to do once I get Nougat to root besides flash TWRP 3.0.3 & SuperSU through that?)
Thanks!
Click to expand...
Click to collapse
=============== ORIGINAL POST ===============
Hello,
I'm basically at my wit's end and I'd just like to see if anyone knows whether it's actually possible to get Android 7.0 Nougat on my phone?
I currently have a rooted, RUU-updated 6.0.1 build of Android (Version Number: 1.60.651.4) running on a Sprint (so CDMA) HTC One A9 (Model Number: 2PQ9300). My phone is still S-On (I'm willing to pay for Sunshine if it'll actually work for me, but I'd like to confirm that first), and due to the updating process I do not currently have TWRP - that's easily fixed, however.
Mostly, I'd just like to know if there's a way to get Android 7.0 on my phone, as it is not the International version, while also retaining things like mobile data and calling.
So far, I've looked into simply flashing the RUU (seems to be both not compatible with my phone version, and also has the signing issue mentioned Here), however with the signing issue I'd have to OTA update first so that's not relevant.
I've looked into Sunshine for S-OFF as well as This thread to convert to the "Unlocked" version that has the update, however I'm seeing comments about it not being compatible with the Sprint edition.
I've most recently tried to follow This guide, however I've had no luck and I'm still seeing talk of random reboots, dropped calls, and the like.
Basically, if there's any way I can get Android 7.0 Nougat on my phone, I would love to know how - if I can't (reasonably), then I'd also like to know that so I can stop beating my head into the wall, so to speak
Thanks!
Jaxas said:
Basically, if there's any way I can get Android 7.0 Nougat on my phone, I would love to know how - if I can't (reasonably), then I'd also like to know that so I can stop beating my head into the wall, so to speak
Thanks!
Click to expand...
Click to collapse
So far, the CDMA versions of the A9 can't run Nougat. As you know, HTC hasn't updated it for Nougat, and our phones run different enough firmware from the GSM-Locked and Dev versions that we can't use theirs. And so far, HTC's Dev Nougat requires Nougat firmware. So... we're boned.
Hopefully this won't be forever; HTC should eventually update American phones, so we'll just have to factory reset from system image (and maybe RUU) and OTA. For now, we can only hope guys like Captain_Throwback figure out how to backport Nougat to the 1.60.651.4 firmware.
Jaxas said:
Hello,
I'm basically at my wit's end and I'd just like to see if anyone knows whether it's actually possible to get Android 7.0 Nougat on my phone?
I currently have a rooted, RUU-updated 6.0.1 build of Android (Version Number: 1.60.651.4) running on a Sprint (so CDMA) HTC One A9 (Model Number: 2PQ9300). My phone is still S-On (I'm willing to pay for Sunshine if it'll actually work for me, but I'd like to confirm that first), and due to the updating process I do not currently have TWRP - that's easily fixed, however.
Mostly, I'd just like to know if there's a way to get Android 7.0 on my phone, as it is not the International version, while also retaining things like mobile data and calling.
So far, I've looked into simply flashing the RUU (seems to be both not compatible with my phone version, and also has the signing issue mentioned Here), however with the signing issue I'd have to OTA update first so that's not relevant.
I've looked into Sunshine for S-OFF as well as This thread to convert to the "Unlocked" version that has the update, however I'm seeing comments about it not being compatible with the Sprint edition.
I've most recently tried to follow This guide, however I've had no luck and I'm still seeing talk of random reboots, dropped calls, and the like.
Basically, if there's any way I can get Android 7.0 Nougat on my phone, I would love to know how - if I can't (reasonably), then I'd also like to know that so I can stop beating my head into the wall, so to speak
Thanks!
Click to expand...
Click to collapse
hey,
can you try this ...
https://forum.xda-developers.com/one-a9/general/htc-one-a9-android-7-nougat-t3546557
New info: Nougat is now available via OTA. Now we just need to... get back to full stock.
Woo! Just saw the notification. So now the question is if TWRP will work with 7.0 on our phones.. I think I'd rather keep root than upgrade and lose it if there's a choice.
JohnRogers23 said:
Woo! Just saw the notification. So now the question is if TWRP will work with 7.0 on our phones.. I think I'd rather keep root than upgrade and lose it if there's a choice.
Click to expand...
Click to collapse
TWRP 3.0.3 beta is available for nougat
MGfusion said:
TWRP 3.0.3 beta is available for nougat
Click to expand...
Click to collapse
I saw, but I'm not sure what's going on in the thread right now. It seems it sometimes bootloops? I'm hesitant to upgrade until there's either an RUU for 2.whatever out or I'm sure TWRP is reliable. I'm resigning myself to living without Xposed, but I at least need root and Magisk.
JohnRogers23 said:
Woo! Just saw the notification. So now the question is if TWRP will work with 7.0 on our phones.. I think I'd rather keep root than upgrade and lose it if there's a choice.
Click to expand...
Click to collapse
Whelp.
I'm upset, lol.
Time to re-reset my phone (finally got it set back up the way I wanted it yesterday on 6.0.1)
Oh well, thanks for the heads up!
I have the Sprint a9. I flashed the ruu and flashed TWRP 3.0.3-1 I believe, with no issues
Okay, so before I go re-wipe my phone and upgrade, I have a few quick questions...
1) Can this update be flashed with S-ON? (I'm assuming so, but always good to check) and
2) Can the Sprint A9 be rooted on Nougat yet?
Thanks!
I used TWRP 3.0.3.-4 and root with Magisk. Still miss Xposed, but the N features are pretty nice too. All seems to be working well.
Hello again, sorry to bother you guys but I'm seeing a surprising amount of conflicting information about this...
So I'm trying to upgrade to Nougat, but I'm having some troubles figuring out what I need to do for that.
I know I need to get my phone back to stock so I can accept the OTA update, but I'm not sure how to go about that.
My phone currently:
- Phone Model: HTC One A9 (Sprint - 2PQ93)
- Android Version: 6.0.1
- Software Version: 1.60.651.4
- Root: Yes
- Recovery: TWRP v2.8.8.2_CPTB-TEST2
- S: ON
- Bootloader: Unlocked
- Software Status: Modified
So as far as I'm aware, I need to restore the Stock recovery (how?), re-flash the RUU for my current software version, and then... relock the bootloader? Maybe?
So my questions are...
- How do I actually restore the stock recovery?
- Are there any steps I'm missing?
- Do I need to re-lock the bootloader, or does that not matter?
(- Is there anything I need to do once I get Nougat to root besides flash TWRP 3.0.3 & SuperSU through that?)
Thanks!
Jaxas said:
So as far as I'm aware, I need to restore the Stock recovery (how?), re-flash the RUU for my current software version, and then... relock the bootloader? Maybe?
So my questions are...
- How do I actually restore the stock recovery?
- Are there any steps I'm missing?
- Do I need to re-lock the bootloader, or does that not matter?
(- Is there anything I need to do once I get Nougat to root besides flash TWRP 3.0.3 & SuperSU through that?)
Thanks!
Click to expand...
Click to collapse
If you don't have an unmodified system image from before you mounted the system partition then yes, you do have to use an RUU, which will also give you stock recovery. No, you don't need to do anything with the bootloader.
Flash the RUU for the version you're on now, start up normally and take the OTA. No, I didn't have to do anything special besides making double checking /system is mounted read-only in TWRP. Personally I like using Magisk for root, etc, but I've heard SuperSU works fine. too. I'm S-on as well and it was all very easy.
I have a modified htc one a9 sprint, i want to get back to fully stock so i can update my device by using RUU side load. Please help
samweli benjamin said:
I have a modified htc one a9 sprint, i want to get back to fully stock so i can update my device by using RUU side load. Please help
Click to expand...
Click to collapse
What is your CID, MID and version-main? Is your bootloader locked or unlocked? S-ON or S-OFF?
I have attached a screenshot of getvar all for my device, when i was attemping to update it by using RUU its status was LOCKED and S-OFF but currently its status is **RE-LOCKED** and S-OFF
samweli benjamin said:
I have attached a screenshot of getvar all for my device, when i was attemping to update it by using RUU its status was LOCKED and S-OFF but currently its status is **RE-LOCKED** and S-OFF
Click to expand...
Click to collapse
What ruu version were you trying to flash and what was the error?
It was RUU_HIA_AERO_WHL_N70_SENSE80GP_SPCS_MR_Sprint_WWE_2.18.651.2 and the ERROR that I received was SIGNARURE ERROR: 132
samweli benjamin said:
It was RUU_HIA_AERO_WHL_N70_SENSE80GP_SPCS_MR_Sprint_WWE_2.18.651.2 and the ERROR that I received was SIGNARURE ERROR: 132
Click to expand...
Click to collapse
You can't flash a nougat ruu (2.xx.xxx.x) on a phone running the marshmallow firmware (1.xx.xxx.x). You need to manually update your firmware to 2.xx.651.x before being able to flash the 2.18.651.2 RUU. This is because the new signature key implemented in all 2.xx.xxx.x ruu, explained here at faq #4
Or you can flash the older 1.60.651.4 ruu and after, update your phone using OTA updates. Probably the easiest way for you :good:
http://dl3.htc.com/application/RUU_HIA_AERO_WHL_M60_SENSE7GP_SPCS_MR_Sprint_WWE_1.60.651.4.exe
This seems to be of great help to me, but am afraid i can't install the OTA in my device, b'se I received it and i did downloaded it but when i click to install it finish unzipping file and then fail and the phone boots in TWRP recovery so i thought i can update it by running a RUU side load