Related
Enclosed is the latest Find 7a X9006 OTA
Build: 140419
NOTE: I am only posting this here for users to download and devs to use. I will most likely not be updating with new versions and will not be supporting this as it is OPPO's
NOTE2: You must use stock recovery in order to flash this update.
Changelog from OPPO:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DOWNLOAD: See Above for Downloads or click here
XDA:DevDB Information
Oppo Find 7a X9006 140419 OTA, a ROM for the Oppo Find 7
Contributors
jerdog
ROM OS Version: 4.3.x Jellybean
Version Information
Status: Stable
Created 2014-04-30
Last Updated 2014-04-30
Think there's any chance of this being rebundled to work with TRWP?
seanpr123 said:
Think there's any chance of this being rebundled to work with TRWP?
Click to expand...
Click to collapse
Issue is that right now TWRP looks for the device to be called "find7a" due to it actually being a Find 7a - but Oppo is shipping it as "FIND7" which is certainly to cause all sorts of issues going forward when the real find 7 comes out.
As soon as I can test it out I will be pushing a TWRP ready version of the OTA - or you can remove the ASSERT lines in the updater-script
jerdog said:
Issue is that right now TWRP looks for the device to be called "find7a" due to it actually being a Find 7a - but Oppo is shipping it as "FIND7" which is certainly to cause all sorts of issues going forward when the real find 7 comes out.
As soon as I can test it out I will be pushing a TWRP ready version of the OTA - or you can remove the ASSERT lines in the updater-script
Click to expand...
Click to collapse
No need to remove the Assert lines as I just change one of the FIND7 entries to X9007 for my Find 7a phone and it installs no problems.
Hmm, I installed TWRP and SuperSU, fastbooted the stock recovery.img back and the update file fails to flash in stock recovery for me... I've verified MD5. Not sure what it could be but a TWRP flashable.zip would be very appreciated anybody?
Someone got the international rom to download ( not coloros 2 beta) , i want to flash my chinese x9007 with it?
Well, I made the update, but I noticed that the screen is turning on in my pocket. My phone has the pre-ordered cover So I guess they didn't fix it very well (10.) Except if there is a cover option to tick somewhere.
farfromovin said:
Hmm, I installed TWRP and SuperSU, fastbooted the stock recovery.img back and the update file fails to flash in stock recovery for me... I've verified MD5. Not sure what it could be but a TWRP flashable.zip would be very appreciated anybody?
Click to expand...
Click to collapse
updates fails for me too after flashing stock recovery back via fastboot
OTA Update
Chevyguy85 said:
updates fails for me too after flashing stock recovery back via fastboot
Click to expand...
Click to collapse
Did you make any significant changes to /system? I got the update to work with stock recovery but the only difference I had from stock was that the OS was rooted. I also uninstalled Xposed Framework before installing the update. I didn't continue using the updated ROM though because I could not get Titanium Backup restores to work. Funny, because it worked of the previous version of ColorOS 1.2. Right now I'm running the ColorOS 2.0 beta. It's less glitchy than 1.2. I still don't like ColorOS and can't wait for an alternative.
-Andy
Doc Ames said:
Did you make any significant changes to /system? I got the update to work with stock recovery but the only difference I had from stock was that the OS was rooted. I also uninstalled Xposed Framework before installing the update. I didn't continue using the updated ROM though because I could not get Titanium Backup restores to work. Funny, because it worked of the previous version of ColorOS 1.2. Right now I'm running the ColorOS 2.0 beta. It's less glitchy than 1.2. I still don't like ColorOS and can't wait for an alternative.
-Andy
Click to expand...
Click to collapse
all I did was root it and flash TWRP. Then flashed stock recovery back.
Do you still get LTE with 2.0 beta? Did you get LTE before going to 2.0b?
ColorOS 2.0b
Chevyguy85 said:
all I did was root it and flash TWRP. Then flashed stock recovery back.
Do you still get LTE with 2.0 beta? Did you get LTE before going to 2.0b?
Click to expand...
Click to collapse
Yeah I got LTE before and am still receiving LTE. I haven't found any glitches of note except that some apps installed to the "phone" storage don't work properly which was also the case with 1.2. Bear in mind I've only used 2.0b for a little over a day. Give 2.0b a try. It can't be much worse. Note that you'll need to either edit the .zip file as mentioned previously or use stock recovery. I used stock recovery.
-Sent from my Sega Dreamcast
Doc Ames said:
Yeah I got LTE before and am still receiving LTE. I haven't found any glitches of note except that some apps installed to the "phone" storage don't work properly which was also the case with 1.2. Bear in mind I've only used 2.0b for a little over a day. Give 2.0b a try. It can't be much worse. Note that you'll need to either edit the .zip file as mentioned previously or use stock recovery. I used stock recovery.
-Sent from my Sega Dreamcast
Click to expand...
Click to collapse
Yeah I was going to edit the zipfile for the OTA update but didn't have a clue what file I was supposed to change the wording of/in. I might try it Sunday. I'm going to need a working phone tomorrow and saturday, plus I won't have the time until saturday afternoon anyway.
Because of not having a Find 7a right now and not using ColorOS i would be not able to mirror OTA updates, so nice that someone does this. If someone need the FULL package you would find it also in the forum.
http://forum.xda-developers.com/showthread.php?t=2738788
I tried to flash on stock recovery and just get update failed it also does this for any other file i try to flash like the root file and such. Does anyone know how to fix this?
mr2guy18 said:
I tried to flash on stock recovery and just get update failed it also does this for any other file i try to flash like the root file and such. Does anyone know how to fix this?
Click to expand...
Click to collapse
You have to install stock recovery mod.
I got it form here.
http://forum.xda-developers.com/devdb/project/?id=4528#downloads
I tried v.3, it'swork fine for me.
I can update stock firmware with rooted.
memooffon said:
You have to install stock recovery mod.
I got it form here.
http://forum.xda-developers.com/devdb/project/?id=4528#downloads
I tried v.3, it'swork fine for me.
I can update stock firmware with rooted.
Click to expand...
Click to collapse
I have tried that and it fails and I've tried to flash twrp and the stock recovery in fastboot and they say they install but it remains the same when I go into it. I have the stock recovery now but anything I try to flash says update failed. I have been doing this stuff for a years but this has got me confused.
Update failed
mr2guy18 said:
I have tried that and it fails and I've tried to flash twrp and the stock recovery in fastboot and they say they install but it remains the same when I go into it. I have the stock recovery now but anything I try to flash says update failed. I have been doing this stuff for a years but this has got me confused.
Click to expand...
Click to collapse
I had the same issue. I resolved it by downloading V1.2.1i and doing a Local update, after this I was able to download and install all the OTA's.
[Q&A] ★ ☆ [ROM|RADIO|FIRMWARE][4.4.3] Stock-Rooted | Sense 6 | m7wlv | 09-17-14
Q&A for ★ ☆ [ROM|RADIO|FIRMWARE][4.4.3] Stock-Rooted | Sense 6 | m7wlv | 09-17-14
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Making sure I'm doing this right
Hi all,
I just want to make sure I'm doing this right. I'm relatively new to rooting. Updating the firmware / radio is something I've never done before, so I'm just going to guess at the information I need to provide. Sorry if I leave anything out.
I have an m7vzw running SlimKat version 8.0. It's android 4.4.4 and the baseband version is 1.12.41.1112_2. My phone is S-OFF and I have TWRP installed. Can I just keep SlimKat installed, download the latest firmware / radio.zip in the second post, and follow the fastboot instructions there to update? Or do I need to revert to stock, then update, then return to custom?
Thanks so much for your help.
(I just realized it made a new thread for me. The post I'm referring to is here: http://forum.xda-developers.com/showthread.php?t=2485319)
Kbrotkowski said:
Hi all,
I just want to make sure I'm doing this right. I'm relatively new to rooting. Updating the firmware / radio is something I've never done before, so I'm just going to guess at the information I need to provide. Sorry if I leave anything out.
I have an m7vzw running SlimKat version 8.0. It's android 4.4.4 and the baseband version is 1.12.41.1112_2. My phone is S-OFF and I have TWRP installed. Can I just keep SlimKat installed, download the latest firmware / radio.zip in the second post, and follow the fastboot instructions there to update? Or do I need to revert to stock, then update, then return to custom?
Thanks so much for your help.
(I just realized it made a new thread for me. The post I'm referring to is here: http://forum.xda-developers.com/showthread.php?t=2485319)
Click to expand...
Click to collapse
Yes, it has been discussed in that thread. When you flash firmware only, you do not need to change roms. I would personally do a "fastboot erase cache" command before rebooting into system after firmware flash
Sent from my HTC6500LVWBLU using XDA Free mobile app
Uzephi said:
Yes, it has been discussed in that thread. When you flash firmware only, you do not need to change roms. I would personally do a "fastboot erase cache" command before rebooting into system after firmware flash
Sent from my HTC6500LVWBLU using XDA Free mobile app
Click to expand...
Click to collapse
Awesome. I just wanted to get another opinion because I found some instructions elsewhere that said it was fine and some that said it would brick my phone, etc... Anyway, I really appreciate the help. I'll clear the cache too like you suggested.
Thanks again!
With the release of the GPE edition is a firmware update for our M7 close or do we have to wait until Verizon releases our official Lollipop update?
calash said:
With the release of the GPE edition is a firmware update for our M7 close or do we have to wait until Verizon releases our official Lollipop update?
Click to expand...
Click to collapse
We will have to wait for HTC to release the next version of sense.
I am having issues flashing the firmware. I flash the firmware as directed in the thread and flash 5.28.605.2 through Fastboot. Fastboot appears to work as the bar fills up to the last 1/10th of the progress bar. After that the instruction is to use Fastboot reboot bootloader From there I reboot the phone.
When I reboot back into the Bone Stock ROM after flashing the firmware it looks like the firmware remains as the 4.10.605.3 version in the "about" page of the phone. It does not update to 5.28.605.2
Can anyone help me?
Reboot to the bootloader / hboot screen and read the text there. OS-######.
Any way to disable one Mic? It seems one of mine is broken and it is not in warranty anymore. I'd just need for calls, elsewhere it's working. Thank you.
Hi guys,
I'm a new here and I have some questions about updating. Sorry for stupid questions. I've red many instructions and now in my mind mixed all of them. )
I could't find full instruction for updating (HTC One M7 from Verizon), step by step. Always all instructions begins from the middle, missing many things.
I have used HTC One M7 m7lvw from Verizon with Android 4.4.3
I'd like to update up Lolilop 5.02 (6.22.605.3_M7_WL_L50_SENSE60_MR_Debloated.zip) from Santod040.
But I confused about steps of updating. There are a lot different things, I'm just lost.
Steps to upgrade firmware and ROM (as I understood):
1) Nandroid. What is it? No information on first page. I guess this is saving your own info but not sure. If I don't have my own info can I skip this step?
2) Unlock bootloader with custom recovery. How? No information on first page. I guess TWRP 2.7.0.8 or newer is related to this section.
3) Wipe everything. For what? If I'm going to install new ROM why I need to wipe? And it doesn't info how to wipe.
4) Update firmware (downloaded: m7vzw_6.22.605.3_LP_Firmware_NoBoot-NoRecovery-combo.zip). The instruction is clear on page 1.
5) Update ROM (downloaded: 6.22.605.3_M7_WL_L50_SENSE60_MR_Debloated.zip). Flash the ROM and reboot. How? No info.
If I did mistakes (for sure I did) please correct me.
Thank you.
argument777 said:
Hi guys,
I'm a new here and I have some questions about updating. Sorry for stupid questions. I've red many instructions and now in my mind mixed all of them. )
I could't find full instruction for updating (HTC One M7 from Verizon), step by step. Always all instructions begins from the middle, missing many things.
I have used HTC One M7 m7lvw from Verizon with Android 4.4.3
I'd like to update up Lolilop 5.02 (6.22.605.3_M7_WL_L50_SENSE60_MR_Debloated.zip) from Santod040.
But I confused about steps of updating. There are a lot different things, I'm just lost.
Steps to upgrade firmware and ROM (as I understood):
1) Nandroid. What is it? No information on first page. I guess this is saving your own info but not sure. If I don't have my own info can I skip this step?
2) Unlock bootloader with custom recovery. How? No information on first page. I guess TWRP 2.7.0.8 or newer is related to this section.
3) Wipe everything. For what? If I'm going to install new ROM why I need to wipe? And it doesn't info how to wipe.
4) Update firmware (downloaded: m7vzw_6.22.605.3_LP_Firmware_NoBoot-NoRecovery-combo.zip). The instruction is clear on page 1.
5) Update ROM (downloaded: 6.22.605.3_M7_WL_L50_SENSE60_MR_Debloated.zip). Flash the ROM and reboot. How? No info.
If I did mistakes (for sure I did) please correct me.
Thank you.
Click to expand...
Click to collapse
Are you s-off and rooted? If not, just install HTC sync and plug your phone until your PC. If the phone is sick it will update automagically
Hi Guys,
In your opinion what is the best ROM for M7WLV? I have HTC One from Verizon with version 4.4.3 and it has never updated. Now I'm trying to figure out what version of Android to choose for updating. I don't know how will work the phone with new updates. I mean may be it will work with low speed, lags, loose stability, and etc. Could you please to share with your experience to make me right choice. Thank you.
argument777 said:
Hi Guys,
In your opinion what is the best ROM for M7WLV? I have HTC One from Verizon with version 4.4.3 and it has never updated. Now I'm trying to figure out what version of Android to choose for updating. I don't know how will work the phone with new updates. I mean may be it will work with low speed, lags, loose stability, and etc. Could you please to share with your experience to make me right choice. Thank you.
Click to expand...
Click to collapse
The FAQ thread has the answer for you. It also has other odd frequent questions asked. It having slow downs lag and instability is because of the apps you install or maybe power saver enabled? My wife's phone is stock and only had slow downs with apps that clogged her phone's memory up. I didn't know which did it and just factory reset the thing and the lag was gone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my HTC6500LVW using Tapatalk
Can't find my firmware but I do see a baseland and it's number is no where In line with any firmware versions numbers. I'm trying to see my HTC One Verizon firmware is up to date. Any help would appreciate
---------------
Admin Note: this thread has a dedicated questions and answers section which you can access here -->.
Sent from my HTC6500LVW using Tapatalk
Can't find my firmware but I do see a baseland and it's number is no where In line with any firmware versions numbers. I'm trying to see my HTC One Verizon firmware is up to date. Any help would appreciate
Okay so quick question I haven't flashed a Rom in a while, if I flash this Rom with the firmware and radio update will I be able to use other carrier bands? Cause I'm stuck on metro right now with edge and I want 4G LTE on another carrier, I've heard straight talk but some say it doessnt work I'm on a VZW Branded M7 I JUST WANT 4GLTE!!! PLEASE HELP
rickey95 said:
Okay so quick question I haven't flashed a Rom in a while, if I flash this Rom with the firmware and radio update will I be able to use other carrier bands? Cause I'm stuck on metro right now with edge and I want 4G LTE on another carrier, I've heard straight talk but some say it doessnt work I'm on a VZW Branded M7 I JUST WANT 4GLTE!!! PLEASE HELP
Click to expand...
Click to collapse
You won't get 4G or hspa on US Carriers on the Verizon Branded HTC one.
My phone wont turn on wifi. I tried factory reset multiple times. nothing is working. help.
233AK said:
My phone wont turn on wifi. I tried factory reset multiple times. nothing is working. help.
Click to expand...
Click to collapse
Did you flash any roms or make any other changes to your phone ?
clsA said:
Did you flash any roms or make any other changes to your phone ?
Click to expand...
Click to collapse
yeah im using the Android Revolution HD rom.
Wild guess: you are on latest ARHD and you didn't update your firmware to 3.28.401.x, aren't you
Lol, we really need a sticky or something for the latest update. Or the ROM devs need to include a warning. (Not that im saying its any of their responsibility)
bloodhawk said:
Lol, we really need a sticky or something for the latest update. Or the ROM devs need to include a warning. (Not that im saying its any of their responsibility)
Click to expand...
Click to collapse
Not going to help mate, the people don't bother to read, that's the problem.
All the developers can put a warning in THIS BIG and the majority of the people will still scroll past it to just download the ROM in their rush to be "cool hackerz"
There is plenty enough proof of that already, developers clearly state in RED in their first post, THIS WILL NOT WORK WITH VERIZON and within the first 10 replies an idiot will come out and ask "Will this work with Verizon?"
Always read the last several pages on any rom you flash. You will always see any current issues or hot topics that way.
Read read read. That's a requirement for this hobby. ?
update post. I switched roms and still having the same problems. I'm using venom now.
KJ said:
Always read the last several pages on any rom you flash. You will always see any current issues or hot topics that way.
Read read read. That's a requirement for this hobby. ?
Click to expand...
Click to collapse
First 2 pages and last 3 is a must definitely! :good:
---------- Post added at 06:03 AM ---------- Previous post was at 06:01 AM ----------
233AK said:
update post. I switched roms and still having the same problems. I'm using venom now.
Click to expand...
Click to collapse
What version of venom?
233AK said:
update post. I switched roms and still having the same problems. I'm using venom now.
Click to expand...
Click to collapse
Ok first thing, goto the bootloader and check what the OS field says. If it is anything under 3.XX.XXX.X, then your need to update your firmware. Otherwise the problem is something else.
bloodhawk said:
Ok first thing, goto the bootloader and check what the OS field says. If it is anything under 3.XX.XXX.X, then your need to update your firmware. Otherwise the problem is something else.
Click to expand...
Click to collapse
Won't it give the OS version for the ROM he has on which might be 3.x anyways?
I also think it's outdated firmware on his part, radio firmware needs to be updated in order for data, mobile, wifi, bluetooth etc to function properly. This guy can't be bothered so I don't know why we bother either.
ARHD - 10 to 1 he used 21.0
Venom - 10 to 1 it's 3.0
But we should guess these things because he doesn't answer anyone when asked. What version was he on before? Most likely a 2.x but we won't know that either because
He didn't take note of it before he flashed away
He doesn't want to make the effort
It's easier to just expect others to do everything for you.
BerndM14 said:
Won't it give the OS version for the ROM he has on which might be 3.x anyways?
I also think it's outdated firmware on his part, radio firmware needs to be updated in order for data, mobile, wifi, bluetooth etc to function properly. This guy can't be bothered so I don't know why we bother either.
ARHD - 10 to 1 he used 21.0
Venom - 10 to 1 it's 3.0
But we should guess these things because he doesn't answer anyone when asked. What version was he on before? Most likely a 2.x but we won't know that either because
He didn't take note of it before he flashed away
He doesn't want to make the effort
It's easier to just expect others to do everything for you.
Click to expand...
Click to collapse
:cyclops:
I think when i flashed IC 5.0.0 without updating the firmware, my OS version still said 2.XX.XXX.X.Though It is as you say the radio firmwares need to be updated.
Changed to the new one once i flashed the update.
But yeah, you'r right, not many people willing to search the forums. The same issue has been discussed at least 20 times now. With 5 threads on the 2-3 pages of the Q&A section. I found my solution within maybe 2 mins and after reading less than 2 pages of the ROM i was updating. to.
bloodhawk said:
:cyclops:
I think when i flashed IC 5.0.0 without updating the firmware, my OS version still said 2.XX.XXX.X.Though It is as you say the radio firmwares need to be updated.
Changed to the new one once i flashed the update.
But yeah, you'r right, not many people willing to search the forums. The same issue has been discussed at least 20 times now. With 5 threads on the 2-3 pages of the Q&A section. I found my solution within maybe 2 mins and after reading less than 2 pages of the ROM i was updating. to.
Click to expand...
Click to collapse
Oh ok, I thought maybe it took that information from the build as well which would show the ROM's version(3.28.401.7) kinda like doing a getprop
I only flashed a custom ROM once and honestly, didn't even have a look at the OS in bootloader and even if I did happen to look at it the version probably wouldn't have shown what we're looking for now(I was updated to latest firmware so didn't have issues)
BerndM14 said:
Oh ok, I thought maybe it took that information from the build as well which would show the ROM's version(3.28.401.7) kinda like doing a getprop
I only flashed a custom ROM once and honestly, didn't even have a look at the OS in bootloader and even if I did happen to look at it the version probably wouldn't have shown what we're looking for now(I was updated to latest firmware so didn't have issues)
Click to expand...
Click to collapse
The bootloader pulls it probably from the hardware chip or something and then matches, if it doesn't, it shows up in RED. I could be wrong though.
Getprop pulls it from a .ro file on one of the partitions.
I had a massive heart attack when i first got the phone though. Couldn't unlock the bootloader as well since some partition detail was messed up. Talked to some Dev at HTC, and a day later a very convenient 'GPS' OTA shows up and all is good after that. But before i contacted HTC, i thought maybe flashing over some OTA is gonna sort it for me, the phone was on 2.22.1540.4 and i flashed over the 2.22.1540.3 OTA. Was stuck in RUU flash mode for a few hours and couldn't find anything on the forums, the only way to boot the phone was to use fastboot oem boot string. But it would get stuck in the RUU mode after every restart. That is when i noticed the differences on what the OS field says.
Once the correct OTA was flashed all was golden.
Im now waiting for the Dev edition or GPE to get Lollipop and im gonna convert to that SKU.
bloodhawk said:
The bootloader pulls it probably from the hardware chip or something and then matches, if it doesn't, it shows up in RED. I could be wrong though.
Getprop pulls it from a .ro file on one of the partitions.
I had a massive heart attack when i first got the phone though. Couldn't unlock the bootloader as well since some partition detail was messed up. Talked to some Dev at HTC, and a day later a very convenient 'GPS' OTA shows up and all is good after that. But before i contacted HTC, i thought maybe flashing over some OTA is gonna sort it for me, the phone was on 2.22.1540.4 and i flashed over the 2.22.1540.3 OTA. Was stuck in RUU flash mode for a few hours and couldn't find anything on the forums, the only way to boot the phone was to use fastboot oem boot string. But it would get stuck in the RUU mode after every restart. That is when i noticed the differences on what the OS field says.
Once the correct OTA was flashed all was golden.
Im now waiting for the Dev edition or GPE to get Lollipop and im gonna convert to that SKU.
Click to expand...
Click to collapse
Yeah perhaps it does get it from boot.img or something similar, even then the new ROM flashed already contains those version numbers so I just figured it'll show the ROMs number and not the old OS version. Either way... It's cool. Like I said I never actually bothered to look at the OS Version there when I flashed Venom, had it on for 2 days and went back to stock(converted to Dev Edition).
GPE Will no doubt have it faster but I don't want to convert to GPE. Personally I'm not a major fan of "vanilla android". I actually like Sense. So hopefully it won't be too long after GPE gets the update that it'll roll out for Dev Edition.
That said, I'll probably do the exact opposite of what I just said and convert to GPE anyways just to see what Lollipop is like
BerndM14 said:
Yeah perhaps it does get it from boot.img or something similar, even then the new ROM flashed already contains those version numbers so I just figured it'll show the ROMs number and not the old OS version. Either way... It's cool. Like I said I never actually bothered to look at the OS Version there when I flashed Venom, had it on for 2 days and went back to stock(converted to Dev Edition).
GPE Will no doubt have it faster but I don't want to convert to GPE. Personally I'm not a major fan of "vanilla android". I actually like Sense. So hopefully it won't be too long after GPE gets the update that it'll roll out for Dev Edition.
That said, I'll probably do the exact opposite of what I just said and convert to GPE anyways just to see what Lollipop is like
Click to expand...
Click to collapse
Big sense fan here myself.. But cant wait for thr sense update. Let's see how fast they do it.
In the mean time hope the OP UPDATED his firmware.
bloodhawk said:
Big sense fan here myself.. But cant wait for thr sense update. Let's see how fast they do it.
In the mean time hope the OP UPDATED his firmware.
Click to expand...
Click to collapse
:laugh: I was just thinking that... yet somehow I doubt it, next post will probably be to ask how he does that.
Oh well, we should probably stop high jacking his thread even though he started it and doesn't say anything in it himself.
I've never seen so many people not read the threads before blindly flashing things, seriously.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Guys,
I've got the Gunmetal Dev Edition M9 and I can't seem to get VoLTE to work on AT&T. Works fine on my iPhone 6 Plus, but when I pop the SIM into the M9, no VoLTE and my AT&T account still has it provisioned. Any help is appreciated guys!
Y2J
Interestting. Didn't Des' recent tweet confirm the DE M9 had VoLTE?
I think it does, I just think it has to be activated somehow, probably via a software update. Hopefully this isn't an issue for those of us with unlocked/developer editions running on AT&T.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Nobody else has this? Stock...
Sent From My HTC One (M9)
Rydah805 said:
View attachment 3243666
Nobody else has this? Stock...
Sent From My HTC One (M9)
Click to expand...
Click to collapse
Nope. Looks like you have the T-Mobile version. I have the unlocked version. That setting isn't there.
MattMJB0188 said:
Nope. Looks like you have the T-Mobile version. I have the unlocked version. That setting isn't there.
Click to expand...
Click to collapse
Are you rooted?
Sent From My HTC One (M9)
Rydah805 said:
Are you rooted?
Sent From My HTC One (M9)
Click to expand...
Click to collapse
No. I really don't need that with this phone. Lol.
y2jdmbfan said:
Guys,
I've got the Gunmetal Dev Edition M9 and I can't seem to get VoLTE to work on AT&T. Works fine on my iPhone 6 Plus, but when I pop the SIM into the M9, no VoLTE and my AT&T account still has it provisioned. Any help is appreciated guys!
Y2J
Click to expand...
Click to collapse
Its disabled in system/customize/acc/default.xml. Can edit it with root.
Well, in System/Customize/ACC/default.XML, my device has this line that stands out to me:
Code:
<item type="boolean" name="voLteEnabled">true</item>
Yours may possibly be set to false? If so, try changing it to "true" and see if that works.
Sent From My HTC One (M9)
Rydah805 said:
Well, in System/Customize/ACC/default.XML, my device has this line that stands out to me:
Code:
<item type="boolean" name="voLteEnabled">true</item>
Yours may possibly be set to false? If so, try changing it to "true" and see if that works.
Sent From My HTC One (M9)
Click to expand...
Click to collapse
Does that need root? Maybe someone can post a tutorial on how to accomplish that edit?
MattMJB0188 said:
Does that need root? Maybe someone can post a tutorial on how to accomplish that edit?
Click to expand...
Click to collapse
Yes, and it's simple, use root explorer, navigate to the file, press and hold on the file and select: open in text editor and find the line.
Probably easier to do it on a computer where you can Ctrl+f and find that specific line. If you post that file, I can do it for you.
Sent From My HTC One (M9)
Rydah805 said:
Yes, and it's simple, use root explorer, navigate to the file, press and hold on the file and select: open in text editor and find the line.
Probably easier to do it on a computer where you can Ctrl+f and find that specific line. If you post that file, I can do it for you.
Sent From My HTC One (M9)
Click to expand...
Click to collapse
Thanks. I'm good. I'm not rooted. Not sure if I want to do it just yet.
I've currently got the gunmetal dev edition as well, and in my default.xml it's actually set to "true" but the option does not appear in phone settings. The ROM on the phone right now is Viper 1.7 and I'm wondering if something in their ROM has that feature 'hidden'. I'm not sure what to check next. I'd be much more interested in getting VoLTE working than Wi-Fi Calling. I'm switching back and forth between T-Mo and AT&T sim cards at the moment.
Any news??
2.8 firmware and VoLTE
Has anyone gotten VoLTE to work on the latest 2.8 dev edition rom. It worked on the older firmware, but I wasn't able to use the same method on the new firmware. Was anyone else successful in enabling VoLTE? Using T-Mobile M9 on TMO converted to dev edition.
effortless said:
Has anyone gotten VoLTE to work on the latest 2.8 dev edition rom. It worked on the older firmware, but I wasn't able to use the same method on the new firmware. Was anyone else successful in enabling VoLTE? Using T-Mobile M9 on TMO converted to dev edition.
Click to expand...
Click to collapse
You sure about it working on 1.32 developer edition? I had problems receiving calls and the only rom it would work on was the 1.32 AT&T edition (and now the 2.6 AT&T edition). I tried the 1.32 dev ruu and volte still wouldn't work.
As far as I know, 2.8 Developer edition still doesn't support it. Not only do the dev roms not support it, but if it somehow gets turned on on your account, you won't receive calls.
Anyway, all that said, I think it will work on the 2.8 firmware, but it's just that the rom doesn't support it.
ICE (custom) defiitely supports it as I've been using that for about a week with no issues.
Either that, or flash the AT&T 2.6 rom (only currently available in the form of an RUU.exe, so you'll have to be s-off for that option to work.
Or, if you're rooted, I can send you the files from the AT&T rom that should get it working, but it's going to be dirty. You'll need to just copy the AT&T files to the same location in your rom (overwriting the existing files). I got it working by doing this after the AT&T update came out but before ICE added support for it. Obviously, the easiest would be to just flash ice 3.1.1 or later.
jollywhitefoot said:
You sure about it working on 1.32 developer edition? I had problems receiving calls and the only rom it would work on was the 1.32 AT&T edition (and now the 2.6 AT&T edition). I tried the 1.32 dev ruu and volte still wouldn't work.
As far as I know, 2.8 Developer edition still doesn't support it. Not only do the dev roms not support it, but if it somehow gets turned on on your account, you won't receive calls.
Anyway, all that said, I think it will work on the 2.8 firmware, but it's just that the rom doesn't support it.
ICE (custom) defiitely supports it as I've been using that for about a week with no issues.
Either that, or flash the AT&T 2.6 rom (only currently available in the form of an RUU.exe, so you'll have to be s-off for that option to work.
Or, if you're rooted, I can send you the files from the AT&T rom that should get it working, but it's going to be dirty. You'll need to just copy the AT&T files to the same location in your rom (overwriting the existing files). I got it working by doing this after the AT&T update came out but before ICE added support for it. Obviously, the easiest would be to just flash ice 3.1.1 or later.
Click to expand...
Click to collapse
Thanks for responding. It worked fine on the 1.32 dev edition ROM on T-Mobile. I'm already S-Offed and cid/mid converted to full dev edition. When I enable it on the 2.8 rom, the option doesn't show in settings and when I receive calls, it switches to H instead of 4G/LTE. I'll just wait till next week for the official T-mobile rom I guess. I'd rather keep the Dev edition though for the faster updates and less bloat, but I'd like VoLTE back as well.
effortless said:
Thanks for responding. It worked fine on the 1.32 dev edition ROM on T-Mobile. I'm already S-Offed and cid/mid converted to full dev edition. When I enable it on the 2.8 rom, the option doesn't show in settings and when I receive calls, it switches to H instead of 4G/LTE. I'll just wait till next week for the official T-mobile rom I guess. I'd rather keep the Dev edition though for the faster updates and less bloat, but I'd like VoLTE back as well.
Click to expand...
Click to collapse
So you had the setting on the 1.32 dev edition? That's so weird. The settings for me were the exact same in both 1.32 and 2.8 dev editions.
jollywhitefoot said:
So you had the setting on the 1.32 dev edition? That's so weird. The settings for me were the exact same in both 1.32 and 2.8 dev editions.
Click to expand...
Click to collapse
All I did was enable <item type="boolean" name="voLteEnabled">true</item> (changed it to true) like it said earlier in the thread and it enabled the VoLTE setting on the 1.32 Dev edition ROM for me and calls remained on LTE.
effortless said:
All I did was enable <item type="boolean" name="voLteEnabled">true</item> (changed it to true) like it said earlier in the thread and it enabled the VoLTE setting on the 1.32 Dev edition ROM for me and calls remained on LTE.
Click to expand...
Click to collapse
Gotcha. I don't think I checked that setting when I was on the dev edition. They were all set to true on the custom rom I was using though and it didn't make a difference. I didn't even think to try it with the dev edition.
Hello guys ..i have htc 10 i think asian version with unlocked bootloader ans s-on , is there any nougat RUU available to flash? And can i flash it with s-on ? And how to flash .. And i am sorry for being noob
Sent from my HTC 10 using XDA-Developers mobile app
Akhayev said:
Hello guys ..i have htc 10 i think asian version with unlocked bootloader ans s-on , is there any nougat RUU available to flash? And can i flash it with s-on ? And how to flash .. And i am sorry for being noob
Sent from my HTC 10 using XDA-Developers mobile app
Click to expand...
Click to collapse
A custom rom or just stock Nougat? Viper here
http://forum.xda-developers.com/htc-10/development/rom-21-02-viper10-1-0-0-tweaks-hub-t3379151
US Unlocked stock Nougat here
https://www.htc.com/us/support/htc-10/news/
Try to find out exactly which phone you have.
comstockload said:
A custom rom or just stock Nougat? Viper here
http://forum.xda-developers.com/htc-10/development/rom-21-02-viper10-1-0-0-tweaks-hub-t3379151
US Unlocked stock Nougat here
https://www.htc.com/us/support/htc-10/news/
Try to find out exactly which phone you have.
Click to expand...
Click to collapse
I want stock nougat, will viper work with s-on? I have unlocked boooader and TWRP , and on my phone the model number says just htc10
Sent from my HTC 10 using XDA-Developers mobile app
Akhayev said:
I want stock nougat, will viper work with s-on? I have unlocked boooader and TWRP , and on my phone the model number says just htc10
Sent from my HTC 10 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes, Viper will work but its complicated right now. Nougat with updated firmware breaks TWRP. Some of us are waiting for Captain Throwback to update TWRP for Nougat so that we can also flash other apps like V4A etc. Others can't wait and are using Magisk with phh superuser and so on. Pick your poison. I'm waiting on the Captain.
BTW, I use the safest and cleanest way to flash roms (IMHO) as follows:
1. I get the RUU.exe file directly from HTC, download to my computer and run the self-executing file. This gives me a pristine stock rom.
2. I then flash TWRP.
3. Finally, I flash the custom rom with TWRP.
That's it, simple and (relatively) safe. The custom rom already has SuperSU so no need to flash seperately unless I want a rooted stock rom. I don't do the extracting boot images, downgrading firmware to get TWRP to work, and all that schtick.
comstockload said:
Yes, Viper will work but its complicated right now. Nougat with updated firmware breaks TWRP. Some of us are waiting for Captain Throwback to update TWRP for Nougat so that we can also flash other apps like V4A etc. Others can't wait and are using Magisk with phh superuser and so on. Pick your poison. I'm waiting on the Captain.
BTW, I use the safest and cleanest way to flash roms (IMHO) as follows:
1. I get the RUU.exe file directly from HTC, download to my computer and run the self-executing file. This gives me a pristine stock rom.
2. I then flash TWRP.
3. Finally, I flash the custom rom with TWRP.
That's it, simple and (relatively) safe. The custom rom already has SuperSU so no need to flash seperately unless I want a rooted stock rom. I don't do the extracting boot images, downgrading firmware to get TWRP to work, and all that schtick.
Click to expand...
Click to collapse
You went to some length trying to help this guy. I'll give you an upvote even though he didn't bother. Thx :good:
Some people are rude like that.
comstockload said:
Yes, Viper will work but its complicated right now. Nougat with updated firmware breaks TWRP. Some of us are waiting for Captain Throwback to update TWRP for Nougat so that we can also flash other apps like V4A etc. Others can't wait and are using Magisk with phh superuser and so on. Pick your poison. I'm waiting on the Captain.
BTW, I use the safest and cleanest way to flash roms (IMHO) as follows:
1. I get the RUU.exe file directly from HTC, download to my computer and run the self-executing file. This gives me a pristine stock rom.
2. I then flash TWRP.
3. Finally, I flash the custom rom with TWRP.
That's it, simple and (relatively) safe. The custom rom already has SuperSU so no need to flash seperately unless I want a rooted stock rom. I don't do the extracting boot images, downgrading firmware to get TWRP to work, and all that schtick.
Click to expand...
Click to collapse
Thank you very much dude .. I tried what you told me and it did work ..thank you again very much :*
Sent from my HTC 10 using XDA-Developers mobile app
comstockload said:
Yes, Viper will work but its complicated right now. Nougat with updated firmware breaks TWRP. Some of us are waiting for Captain Throwback to update TWRP for Nougat so that we can also flash other apps like V4A etc. Others can't wait and are using Magisk with phh superuser and so on. Pick your poison. I'm waiting on the Captain.
BTW, I use the safest and cleanest way to flash roms (IMHO) as follows:
1. I get the RUU.exe file directly from HTC, download to my computer and run the self-executing file. This gives me a pristine stock rom.
2. I then flash TWRP.
3. Finally, I flash the custom rom with TWRP.
That's it, simple and (relatively) safe. The custom rom already has SuperSU so no need to flash seperately unless I want a rooted stock rom. I don't do the extracting boot images, downgrading firmware to get TWRP to work, and all that schtick.
Click to expand...
Click to collapse
Im sorry i thought it worked ..but it gives me that msg when i try to flash RUU
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my HTC 10 using XDA-Developers mobile app
This Rom only works for US carrier versions. Europe and Asian handsets will display the above error code using this RUU
RUU wont work for you. Nougat for HTC WWE (World Wide English) as well as most other regions has not been released yet, just the US Unlocked.
The US version may work in general with your phone, but installing it any other way besides Custom ROM's will be a PITA.
BaggyBizzle said:
This Rom only works for US carrier versions. Europe and Asian handsets will display the above error code using this RUU
Click to expand...
Click to collapse
Thank you for your help ..i will try viper ROM and see
silegeek said:
RUU wont work for you. Nougat for HTC WWE (World Wide English) as well as most other regions has not been released yet, just the US Unlocked.
The US version may work in general with your phone, but installing it any other way besides Custom ROM's will be a PITA.
Click to expand...
Click to collapse
Sent from my HTC 10 using XDA-Developers mobile app