Followed instructions to the T I'm pretty sure, and since then all incoming calls go straight to voicemail.. Now I want to revert back to stock, do the sunshine s off and then try revolution hd again to see if the problem goes away.
homthtrnut said:
Followed instructions to the T I'm pretty sure, and since then all incoming calls go straight to voicemail.. Now I want to revert back to stock, do the sunshine s off and then try revolution hd again to see if the problem goes away.
Click to expand...
Click to collapse
This issue has been reported by a couple folks now (also on Euro based LP ROMs); although I don't think the exact cause and fix has been determined definitely yet. http://forum.xda-developers.com/att-htc-one-m8/help/m8-skydragon-incoming-calls-t3042091
First off, if you have the AT&T version of the M8 and are s-on, you aren't on the right firmware (hboot, radio, and several other critical modules that don't flash with the ROM) for the an recent (Lollipop) version of ARHD. For now, s-off is needed to update to LP firmware; until AT&T releases LP officially by OTA, RUU.
Although I'm not sure its just a firmware issue (so that may or may not fix the issue). "International" ROMs often don't play well with AT&T's network; since the devs (often Euro) don't understand the nuances of AT&T's network. Not to knock those fine devs, but they can't know what they don't know (or can't test, since they aren't on that particular network). Plus, AT&T is probably mostly to blame, as they seem to do some things differently from just about every other carrier in the world.
The quick fix would be return to a stock AT&T ROM, as you have already figured out. You don't need s-off to do that. Restore your nandroid (that you should always make before messing with flashing new ROMs). Or find a stock AT&T ROM corresponding to your firmware, and flash in recovery. Another option is to relock the bootloader and RUU to stock.
Just need to dig in and get it done!
redpoint73 said:
This issue has been reported by a couple folks now (also on Euro based LP ROMs); although I don't think the exact cause and fix has been determined definitely yet. http://forum.xda-developers.com/att-htc-one-m8/help/m8-skydragon-incoming-calls-t3042091
First off, if you have the AT&T version of the M8 and are s-on, you aren't on the right firmware (hboot, radio, and several other critical modules that don't flash with the ROM) for the an recent (Lollipop) version of ARHD. For now, s-off is needed to update to LP firmware; until AT&T releases LP officially by OTA, RUU.
Although I'm not sure its just a firmware issue (so that may or may not fix the issue). "International" ROMs often don't play well with AT&T's network; since the devs (often Euro) don't understand the nuances of AT&T's network. Not to knock those fine devs, but they can't know what they don't know (or can't test, since they aren't on that particular network). Plus, AT&T is probably mostly to blame, as they seem to do some things differently from just about every other carrier in the world.
The quick fix would be return to a stock AT&T ROM, as you have already figured out. You don't need s-off to do that. Restore your nandroid (that you should always make before messing with flashing new ROMs). Or find a stock AT&T ROM corresponding to your firmware, and flash in recovery. Another option is to relock the bootloader and RUU to stock.
Click to expand...
Click to collapse
I can do anything that is new to me with good instructions. I WAS able to unlock, root, and flash a ROM with good success following the steps. What I would like to do now is put it back the way it was, then s off using sunshine, and then go ahead and flash the Revo HD ROM again and whatever else I need to do, maybe the firmware too idk. Before I started anything , I backed it up using HTC SYNC on my laptop. Is that useful in returning it to stock? Or is that just for media and texts and such? Maybe what I should do is check the forum where the Revo users are and see what they say. Sorry if it sounds like Im thinking out loud but Im a noob at forums and flashing. And Im getting burnt out on having a phone that doesnt receive calls properly. Not to mention burnt out from working all day and coming home to try and solve this mystery. OK I wont mention it. Thanks to those who have attempted to give me input here to try to figure this thing out.
Just a lil something to think about...,youll not have dialer, vvm messages,contacts integrated,signal will probably be not as good,and no VoLTE when using euro ROM's. Stand alone vvm app may or may not install from playstore if you use it. My suggestion,flash back to stock,wait alil while and get an official Lollipop release from ATT.
Flash a twrp backup of latest 4.4.4
Flash stock recovery from latest 4.4.4
Steps above will put you back to as close to stock as possible,without relocking bootloader and reflashing the exe ruu file.
homthtrnut said:
What I would like to do now is put it back the way it was, then s off using sunshine, and then go ahead and flash the Revo HD ROM again and whatever else I need to do, maybe the firmware too idk.
Click to expand...
Click to collapse
If you don't flash the firmware, I don't think the above will help you in any way. You'll just be back to where you are now, just with s-off. Which is just a permission/security change; and won't change the functionality of the phone or address the issue with calls.
Either you need to change firmware, or ROM, or both, in order to fix the problem.
Flashed firmware successfully.........darn .zip.zip tricksters!!!! Anyway!
redpoint73 said:
If you don't flash the firmware, I don't think the above will help you in any way. You'll just be back to where you are now, just with s-off. Which is just a permission/security change; and won't change the functionality of the phone or address the issue with calls.
Either you need to change firmware, or ROM, or both, in order to fix the problem.
Click to expand...
Click to collapse
After several attempts getting cannot load error I figured out I needed to back off the .zip from the renamed folder (its already a damn .zip)! duh....so finally got that done. Wondering what to do about relock now. Guess I will have to google it like everything else. Usually throws me right back in here when I do. I found a guy with the exact same problem I was having and it was just cuz he renamed it firmware.zip. Even the dude on youtube tells you to do it! Us noobs are this close to pulling our eyes out from that one!!!! But after trying this and trying that we finally flashted our firmwares on our little precious. Now to see if I can receive calls again. Whats the procedure for unlocking a relocked phone now? Can it now be done by a cmd prompt? Thanks people!
homthtrnut said:
After several attempts getting cannot load error I figured out I needed to back off the .zip from the renamed folder (its already a damn .zip)! duh....so finally got that done.
I found a guy with the exact same problem I was having and it was just cuz he renamed it firmware.zip. Even the dude on youtube tells you to do it! Us noobs are this close to pulling our eyes out from that one!!!! But after trying this and trying that we finally flashted our firmwares on our little precious.
Click to expand...
Click to collapse
Do yourself a huge favor, and turn off the Windows option (if you haven't already) to hide known file extensions. The option is usually enabled by default. I suspect its mainly meant to prevent non-tech savvy PC users from deleting or modifying file extensions and rendering files unusable (or at least not associated with a program to open it).
For most folks who are going to be messing with things like modding phones, and even halfway familiar with the file extensions, the option to hide them is counter-productive and confusing.
The recommendation to rename the file to firmware.zip is valid. This is done since the files are often named things like 4.16.401 to differentiate the firmwares from each other (such as in firmware collections). Technically, you didn't rename the file to firmware.zip (although Windows make it look like you did), you actually named it firmware.zip.zip, even though Windows didn't display it that way.
homthtrnut said:
Wondering what to do about relock now. Guess I will have to google it like everything else. Usually throws me right back in here when I do.
Whats the procedure for unlocking a relocked phone now? Can it now be done by a cmd prompt? Thanks people!
Click to expand...
Click to collapse
To unlock the bootloader again, simply go through the HTCDev.com process to get another unlock bin token, then run the fastboot command with that token again (like you did the first time).
On past devices, it was sometimes possible to reuse the original token (run the fastboot command with it). But an XDA user commented that doesn't work on this device (and that you need to get a new token). But you can always try it, if you want.
Flashed firmware and now stuck in HBOOT! I REALLY NEED HELP NOW
redpoint73 said:
This issue has been reported by a couple folks now (also on Euro based LP ROMs); although I don't think the exact cause and fix has been determined definitely yet. http://forum.xda-developers.com/att-htc-one-m8/help/m8-skydragon-incoming-calls-t3042091
First off, if you have the AT&T version of the M8 and are s-on, you aren't on the right firmware (hboot, radio, and several other critical modules that don't flash with the ROM) for the an recent (Lollipop) version of ARHD. For now, s-off is needed to update to LP firmware; until AT&T releases LP officially by OTA, RUU.
Although I'm not sure its just a firmware issue (so that may or may not fix the issue). "International" ROMs often don't play well with AT&T's network; since the devs (often Euro) don't understand the nuances of AT&T's network. Not to knock those fine devs, but they can't know what they don't know (or can't test, since they aren't on that particular network). Plus, AT&T is probably mostly to blame, as they seem to do some things differently from just about every other carrier in the world.
The quick fix would be return to a stock AT&T ROM, as you have already figured out. You don't need s-off to do that. Restore your nandroid (that you should always make before messing with flashing new ROMs). Or find a stock AT&T ROM corresponding to your firmware, and flash in recovery. Another option is to relock the bootloader and RUU to stock.
Click to expand...
Click to collapse
I picked a version that was made for the cid 001 according to android file host https://www.androidfilehost.com/?w=files&flid=24258 and after numerous attempts to flash I finally got it to go by getting rid of the renamed .zip at the end. ( It was already a zip file) I think a lot of people have had that problem. Anyway I have now a sort of bricked phone that wont leave HBOOT. My son bought an M8 that should be getting here in a day or so and I was wondering if I made a nandroid of that one, maybe it could pull me out of the hole. I still have fastbboot usb so maybe theres a procedure that will get me going again. Can anyone point me? I'll buy you a beer! or 12
homthtrnut said:
I picked a version that was made for the cid 001 according to android file host https://www.androidfilehost.com/?w=files&flid=24258
Click to expand...
Click to collapse
401 firmware is Euro based firmware. AT&T is 501.
homthtrnut said:
Anyway I have now a sort of bricked phone that wont leave HBOOT. My son bought an M8 that should be getting here in a day or so and I was wondering if I made a nandroid of that one, maybe it could pull me out of the hole. I still have fastbboot usb so maybe theres a procedure that will get me going again.
Click to expand...
Click to collapse
Probably making it more complicated than need be. Also, depending on what firmware you now have on the phone, and whether it corresponds to the "new" nandroid, you might not be in any better place than you are now.
I can think of at least 2 (rather simple) ways to get the phone up and running:
1) Flash a stock or custom ROM that corresponds to your firmware. You can adb push the ROM to your phone; or alternately move it to a removable SD using a card reader connected to your computer.
What hboot and radio numbers are currently on the device?
2) Relock the bootloader and RUU back to stock.
hboot and radio numbers currently on m8
redpoint73 said:
401 firmware is Euro based firmware. AT&T is 501.
Probably making it more complicated than need be. Also, depending on what firmware you now have on the phone, and whether it corresponds to the "new" nandroid, you might not be in any better place than you are now.
I can think of at least 2 (rather simple) ways to get the phone up and running:
1) Flash a stock or custom ROM that corresponds to your firmware. You can adb push the ROM to your phone; or alternately move it to a removable SD using a card reader connected to your computer.
What hboot and radio numbers are currently on the device?
2) Relock the bootloader and RUU back to stock.
Click to expand...
Click to collapse
HBOOT-3.19.0.0000 [email protected] OS-3.42.502.1 eMMC-boot 2048MB
homthtrnut said:
HBOOT-3.19.0.0000 [email protected] OS-3.42.502.1 eMMC-boot 2048MB
Click to expand...
Click to collapse
Dude, all you have to do is relock the bootloader using the fastboot command "fastboot oem lock" and download the HTC One M8 file from here http://www.htc.com/us/support/rom-downloads.html . With the phone plugged in to the computer, run the RUU file. It will bring the phone back to the most recent 4.4.4 OTA. Takes ten minutes. You're making this wayyyyyyy harder on yourself than it should be.
homthtrnut said:
HBOOT-3.19.0.0000 [email protected] OS-3.42.502.1 eMMC-boot 2048MB
Click to expand...
Click to collapse
That is the Android 4.4.4 radio. Meaning the 401 firmware you linked and tried to flash didn't take. And it won't with s-on, unless its signed and hacked to accept AT&T's CID (which I don't think there is any 401 firmware that meets those requirements).
Agree with the above response, in that the easiest way to get the phone up and running again is relock the bootloader and RUU to stock.
Since your device is hboot 3.19, you are stuck with s-on and that means you are stuck on KitKat firmware until AT&T releases Lollipop officially.
That also means you can only run ROMs that support 4.4.4 firmware (no LP based Sense ROMs), otherwise you will run into various serious bugs like the call issue on ARHD (or broken WiFi). There are some LP GPE and AOSP ROMs that support the 4.4.4 firmware, if you want to go that route.
Was just starting out, not enough experience.
bford152 said:
Dude, all you have to do is relock the bootloader using the fastboot command "fastboot oem lock" and download the HTC One M8 file from here http://www.htc.com/us/support/rom-downloads.html . With the phone plugged in to the computer, run the RUU file. It will bring the phone back to the most recent 4.4.4 OTA. Takes ten minutes. You're making this wayyyyyyy harder on yourself than it should be.
Click to expand...
Click to collapse
The above phone was eventually returned. Now I have an unlocked, s off M8. With help from PearlyMon I was able to do it all about a month ago. Now I'm just waiting to work up the nerve to flash a customer Rom and also add in the H/K sound feature. Really liked the HD Revolution Rom, I just didn't have the wherewithall to find and install the proper firmware. This time around will be better. On third M8 now. First one, brand new slipped out of workshirt pocket and faceplanted on a tile floor. First damn day! Didn't have the otter box defender case like I should've. 2nd and 3rd ones have been refurbs. So who knows how much use the battery saw before? So I'd like a nice Rom that has built in low battery drain. Every day it seems to drain off a little sooner. Went to black background today to help it out a little. Anyway, haven't been on this forum much since the above problem and thought I'd touch base with you and say thanks. Have a nice one.
I have the same problem as the OP with ATT using any custom ROM since i got the OTA lollipop update in early April. Firmware is 4.28.xx and it appears that no one has been able to work around it without flashing back to 4.16.xx
Anyone come across a ROM that will receive calls on ATT with s-on and 4.28?
jon145 said:
I have the same problem as the OP with ATT using any custom ROM since i got the OTA lollipop update in early April. Firmware is 4.28.xx and it appears that no one has been able to work around it without flashing back to 4.16.xx
Anyone come across a ROM that will receive calls on ATT with s-on and 4.28?
Click to expand...
Click to collapse
Some folks have been having issues with "international" based custom ROMs on AT&T's LTE network. It seems that AT&T has been making some changes to LTE, possibly in preparation for Voice over LTE (VoLTE, which AT&T calls "HD Voice"), that are messing up voice calls on "international" ROMs.
Some folks have this trouble, while others don't. I can only assume its location dependent; and the mentioned "changes" have only been implemented in some areas. I've been running SkyDragon Sense 7 fine on AT&T in my home area of Massachusetts, as well as travelling to a couple other areas (Chicago and Green Bay) with none of the LTE issues.
You might try WNC's ROM here: http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
Its based on the Lollipop Developer's Edition ROM, which is intended for use on AT&T's network. He's working on a version based on the AT&T 4.28 update, but its still in testing and not posted yet.
Yeah I've been running the SD 9.0 for several days and no love here in Dallas ... I could speculate for days since D is AT&T's home city.
Thanks for the info, I will definitely keep an eye out for WNC's next release. Does he usually do beta releases?
jon145 said:
Thanks for the info, I will definitely keep an eye out for WNC's next release. Does he usually do beta releases?
Click to expand...
Click to collapse
He has a beta in testing right now. Just ping him, and he will probably send you a link to the test build. Probably the only reason he would say "no" is if he is going to release soon anyway.
redpoint73 said:
Some folks have this trouble, while others don't. I can only assume its location dependent; and the mentioned "changes" have only been implemented in some areas. I've been running SkyDragon Sense 7 fine on AT&T in my home area of Massachusetts, as well as travelling to a couple other areas (Chicago and Green Bay) with none of the LTE issues.
Click to expand...
Click to collapse
Interestingly, I'm in Chicago and did have that problem with SkyDragon. Having reverted back to the stock ROM, everything works again. In my thread, I think you mentioned that you are using the "other GSM" option, rather than the AT&T specific option in AROMA. I wonder if it could be some of these AT&T specific "optimizations" or whatever that could be part of the problem.
rhughes93 said:
Interestingly, I'm in Chicago and did have that problem with SkyDragon. Having reverted back to the stock ROM, everything works again. In my thread, I think you mentioned that you are using the "other GSM" option, rather than the AT&T specific option in AROMA. I wonder if it could be some of these AT&T specific "optimizations" or whatever that could be part of the problem.
Click to expand...
Click to collapse
Interesting, indeed. Did you pick AT&T from the AROMA options? If not, try the "other GSM" option (or whatever its called).
I was just in the Chicago area a few weeks ago to visit family. Not the city proper, but the suburbs of Arlington Heights and Batavia. I was on SD 7.0 at the time (there was no AT&T option for that version, so I had picked the "other GSM"). Everything seemed to be working fine.
redpoint73 said:
Interesting, indeed. Did you pick AT&T from the AROMA options? If not, try the "other GSM" option (or whatever its called).
I was just in the Chicago area a few weeks ago to visit family. Not the city proper, but the suburbs of Arlington Heights and Batavia. I was on SD 7.0 at the time (there was no AT&T option for that version, so I had picked the "other GSM"). Everything seemed to be working fine.
Click to expand...
Click to collapse
So I re-flashed SkyDragon, and I think I was not understanding the difference between AROMA installer and the software itself. When I did it the first time, I think I did select T-mobile with wifi calling in AROMA, but AT&T within the software SIM setup. It did not work. Now after getting the stock ROM working, I re-flashed, chose the Other GSM/WWE/whatever option within AROMA, AT&T within the software, and all is right in the world. I may also try the same with Venom this weekend now that I have good restore options, though I don't recall if it had similar options in AROMA or not.
So I just got a new moto e 2nd gen just a few days ago.
Currently running 5.0.2.
Hardware SKU XT1511.
As far as I understand the 5.1 OTA came out a few months ago, correct?
But when I go to the system update, it just says "Your device's software is up to date"
What's going on here? Is there a link to download the ota zip so I can just run adb and flash it myself???
Sent from my MotoE2 using XDA Free mobile app
Same thing happening here, but with XT1526 I live in another region, so I don't know if that has anything to do.
For what it's worth, I live in the USA and purchased this device brand new from best buy just a few days ago.
So yeah, not sure what is going on with the update.
This phone is the 3G version, the retail US model that has LTE connectivity is the one with the 5.1 update.
This phone model has been seemingly neglected by Motorola, this thread in the Motorola Forum has info about the updates of the Moto E 2015, no updates at all for the 3G model
I just purchased the XT1527 LTE model off Amazon for $100 for my grandma to use instead of her crappy ZTE flip phone. She is on my aunt's AT&T 60GB plan for her small business and when the phone first arrived, I signed into her Google account and got everything setup but when I tried to pull the 5.1 update, it wasn't getting it yet and said it was already up-to-date with 5.0.2.
Later that day we finally went to the AT&T store to get a SIM put in it and her number transferred over, but still, no 5.1 update for it yet.
Does anyone know why my XT1527 model can't pull the update yet? I thought for sure it would have been able to pull it when I first turned it on, before even getting the SIM for it.
Is there anyway for me to manually install the OTA without unlocking the bootloader or flashing TWRP or are we just stuck waiting?
dabug91 said:
I just purchased the XT1527 LTE model off Amazon for $100 for my grandma to use instead of her crappy ZTE flip phone. She is on my aunt's AT&T 60GB plan for her small business and when the phone first arrived, I signed into her Google account and got everything setup but when I tried to pull the 5.1 update, it wasn't getting it yet and said it was already up-to-date with 5.0.2.
Later that day we finally went to the AT&T store to get a SIM put in it and her number transferred over, but still, no 5.1 update for it yet.
Does anyone know why my XT1527 model can't pull the update yet? I thought for sure it would have been able to pull it when I first turned it on, before even getting the SIM for it.
Is there anyway for me to manually install the OTA without unlocking the bootloader or flashing TWRP or are we just stuck waiting?
Click to expand...
Click to collapse
Same thing here. I'm not getting 5.1 or any other update. XT1527 from Amazon. System version is 22.36.1.surnia_retus.retus.en.US Build LXI22.50-24.1.
Kernel is dated Feb 7 2015. Does anybody know why this is happening? Sorry to bump an old thread but I firmly believe this is relevant today.
By the way, I contacted Motorola support but they gave me a nonsense answer (i.e. that my phone is fine as it is with no 5.1.)
I have the XT1528 model and it says I have 5.1, but my phone still seems to be affected by stagefright 2.0. I assumed that 5.1 would fix that problem, but I am worried Motorola isnt even going to fix the issue.
That guy earlier said look at the link to see who is getting the 5.1 update rollup.
Don't expect to get it if your not only the list.
Also i seen myself that there was more than 1 stage fright update for 5.0.2
because there was more versions of the exploit that needed to be patched as time went on.
SO there was separate stage-fright updates for 5.0.2 and 5.1 respectively.
in other words you did not have to have 5.1 installed to get stage fright patched with an update.
They probably did that because they know most carriers are not pushing out 5.1 to their customers.
Which leads me to my next point..
It's not up to Motorola..
They can offer the update to any specific carrier but it's up to the carrier to decide if it is rolled out to customers.
It's been a long time now and most carriers did not get the 5.1 update.
It is doubtful i think anyone new is going on that list of who gets it.
For example my carrier in Canada Telus never rolled it out.
I had to get a stock firmware package for another carrier for 5.1 and put it on myself.
I chose to use the generic USA Retail Firmware package.
All has worked well but my phone model is suppose to be using LTE/cdma (surnia_umts)
But i have struggled to get it back on cdma.. with nobody out there with any suggestions on how to fix it.
Had i not tried to switch it over manually to GSM after install i would have given up.
Luckily my Carrier Telus supports CDMA and GSM.
I only found 1 guy who left a comment i seen way back saying he fixed his radio issue
by having his stock 5.0.2 Radio left intact then flashing all else to update.
That did not do me any good.. i have tried many variations with no difference.
I can confirm i was getting a new recent stage fright update OTA prmpt.
And there was a new updated firmware package shared recently that included this newer update.
I installed it and used a Stagefright checker App that scanned for about 10 variations of the exploit
and my phone was reported by the app as safe. (patched)
This version was just recently put on the web by someone..
XT1527_SURNIA_RETUS_5.1_LPI23.29-18.9_cid9_subsidy-DEFAULT_CFC.xml
MD5: 586d4a4888a570e6119c60d7437b6bcc
It has this OTA patch update integrated..
Blur_Version.23.11.15.surnia_retus.retus.en.US
MD5: 7b74752978545ccd0100c3d236cc88f6
xpmule said:
That guy earlier said look at the link to see who is getting the 5.1 update rollup.
Don't expect to get it if your not only the list.
Click to expand...
Click to collapse
My phone is on that list but it's not getting the 5.1 OTA.
xpmule said:
in other words you did not have to have 5.1 installed to get stage fright patched with an update.
They probably did that because they know most carriers are not pushing out 5.1 to their customers.
Which leads me to my next point..
It's not up to Motorola..
They can offer the update to any specific carrier but it's up to the carrier to decide if it is rolled out to customers.
Click to expand...
Click to collapse
It's not getting Stagefright patches either. Regarding the carrier, XT1527 is factory unlocked, which means it's not tied to a specific carrier.
Motorola should provide the updates since they say they do have a 5.1 update on their support site.
xpmule said:
I had to get a stock firmware package for another carrier for 5.1 and put it on myself.
All has worked well but my phone model is suppose to be using LTE/cdma (surnia_umts)
But i have struggled to get it back on cdma.. with nobody out there with any suggestions on how to fix it.
Click to expand...
Click to collapse
Did you try with 4G LTE Switch app? Its ID is com.tapbase.LTEswitcher
xpmule said:
I can confirm i was getting a new recent stage fright update OTA prmpt.
And there was a new updated firmware package shared recently that included this newer update.
XT1527_SURNIA_RETUS_5.1_LPI23.29-18.9_cid9_subsidy-DEFAULT_CFC.xml
It has this OTA patch update integrated..
Blur_Version.23.11.15.surnia_retus.retus.en.US
Click to expand...
Click to collapse
Interesting. Do you know if I can do this update to my phone without unlocking the bootloader? I don't want to void the warranty.
yituge said:
My phone is on that list but it's not getting the 5.1 OTA.
It's not getting Stagefright patches either. Regarding the carrier, XT1527 is factory unlocked, which means it's not tied to a specific carrier.
Motorola should provide the updates since they say they do have a 5.1 update on their support site.
Did you try with 4G LTE Switch app? Its ID is com.tapbase.LTEswitcher
Interesting. Do you know if I can do this update to my phone without unlocking the bootloader? I don't want to void the warranty.
Click to expand...
Click to collapse
Don't count on what i am saying i am a noob eh..
But yeah i think you can just flash that version i did.
Even if your bootloader is locked.
From the sounds of it i think that firmware i used on my Telus carrier phone
was actually originally intended for YOUR phone !
And 4G LTE Switch app?
Hmm no i have not seen that.. i should check it out thanks.
---------- Post added at 08:30 PM ---------- Previous post was at 08:16 PM ----------
I checked out that APP and all it does is open the settings menu for you.
You can just use the dialer instead..
*#*#INFO#*#*
That gives the same thing as that APP
I also have found it to be -read only- on my phone.
So if you change the option it actually doesn't work.
If you REALLY want to change it for real you have to use an alternate method such as..
connect with ADB using your computer.
then use this command..
Code:
adb shell
settings put global preferred_network_mode 9
settings put global preferred_network_mode1 9
Note: That will force LTE/GSM (auto PRL)
you don't need root to do that in the cmd prompt either.
and most guys out there say do another cmd line..
Code:
settings put global preferred_network_mode2 9
But i had checked and that line did not exist so i doubt adding it will do anything.
Change those lines to "get" and look at the value currently set before changing them.
When i ran the 3rd line it said that key does not exist.
Also the number 9 is LTE/GSM (auto PRL)
SO if you use that dialer command or that app you can count down the drop down list
to see what option is what number (to force it via command line)
For example..
no. 8 is..
LTE/cdma (auto PRL)
xpmule said:
Don't count on what i am saying i am a noob eh..
But yeah i think you can just flash that version i did.
Even if your bootloader is locked.
From the sounds of it i think that firmware i used on my Telus carrier phone
was actually originally intended for YOUR phone !
Click to expand...
Click to collapse
Don't worry, I'm a noob too, just trying to read a lot before doing anything.
I checked my phone and everything matches to this ROM:
SURNIA_RETUS_5.0.2_LXI22.50-24.1_cid9_subsidy-DEFAULT_CFC.xml.zip
I also installed CID Getter for further confirmation and ro.boot.cid is 0x9 (i.e. CID9.)
Which ROM I should flash to my phone:
the older SURNIA_RETUS_5.1_LPI23.29-15_cid9_subsidy-DEFAULT_CFC.xml.zip
or the newer XT1527_SURNIA_RETUS_5.1_LPI23.29-18.9_cid9_subsidy-DEFAULT_CFC.xml.zip ?
Does the last one contain Stagefright patches?
My main concern is -if I'm not mistaken- that either one should be 100% official Motorola or it won't flash with a locked bootloader.
xpmule said:
I checked out that APP and all it does is open the settings menu for you.
You can just use the dialer instead..
*#*#INFO#*#*
That gives the same thing as that APP
I also have found it to be -read only- on my phone.
So if you change the option it actually doesn't work.
Click to expand...
Click to collapse
I see. I thought it could work for you, but at least you know a workaround. Thanks for sharing.
Question for those of you with experience on the V10. I just upgraded to the V20 (love it btw). My V10 is probably the first phone I never rooted, or loaded a ROM on. I've had many devices with custom roms in the past, however they were always carried branded (not unlocked) phones. Here is my question:
I'm giving my V10 to a friend in Europe in a few weeks. Already confirmed that it supports all the necessary bands and channels, plus I've used it over there in the past without issue. Being that it's a VS990, is there an official "LG" factory ROM that I can load so that all the verizon branded crap is gone, apps etc, and so that it works like what most Europeans would expect? Just a plain "unlocked" V10 that gets OTA updates? Or is it not possible, or worth the effort?
Thanks in advance..
X
Can't flash roms to VS990. Locked bootloader does not allow TWRP to be installed, which you need to flash roms.
xarius76 said:
I'm giving my V10 to a friend in Europe in a few weeks. Already confirmed that it supports all the necessary bands and channels, plus I've used it over there in the past without issue. Being that it's a VS990, is there an official "LG" factory ROM that I can load so that all the verizon branded crap is gone, apps etc, and so that it works like what most Europeans would expect? Just a plain "unlocked" V10 that gets OTA updates? Or is it not possible, or worth the effort?
Click to expand...
Click to collapse
There is no such thing endorsed by LG. How important is it to remove the Verizon crud and how much risk are you willing to deal with? Are you adverse to voiding your warranty? Are you willing to pay a repair fee for "accidentally" flashing the wrong KDZ file?
According to multiple reports the KDZ files from the various V10s are pretty compatible with each other. Given this you could download a H901 (T-Mobile) KDZ file and install that and it should be free of bloat, there is even speculation this could be used to unlock the bootloader.
Aside from bricking your device, my biggest worry is the cell modem may have slightly different hardware and the firmware for the H901 might not drive it correctly, though that may merely mean it cannot connect to CDMA networks. Much of the cell modem configuration is left untouched by KDZ files, but there is always a first time for an unpleasant surprise.
So, how comfortable are you with risk? I'm cautiously optimistic this method will work, but this is risky! If you do try this, could you please report back whether it succeeded or not? (more reports good)
beavis5706 said:
Can't flash roms to VS990. Locked bootloader does not allow TWRP to be installed, which you need to flash roms.
Click to expand...
Click to collapse
I was unaware the boot loader on this had not been unlocked yet. Seeing as it's been out a year, I just assumed it had been by this point. My bad!
emdroidle said:
There is no such thing endorsed by LG. How important is it to remove the Verizon crud and how much risk are you willing to deal with? Are you adverse to voiding your warranty? Are you willing to pay a repair fee for "accidentally" flashing the wrong KDZ file?
According to multiple reports the KDZ files from the various V10s are pretty compatible with each other. Given this you could download a H901 (T-Mobile) KDZ file and install that and it should be free of bloat, there is even speculation this could be used to unlock the bootloader.
Aside from bricking your device, my biggest worry is the cell modem may have slightly different hardware and the firmware for the H901 might not drive it correctly, though that may merely mean it cannot connect to CDMA networks. Much of the cell modem configuration is left untouched by KDZ files, but there is always a first time for an unpleasant surprise.
So, how comfortable are you with risk? I'm cautiously optimistic this method will work, but this is risky! If you do try this, could you please report back whether it succeeded or not? (more reports good)
Click to expand...
Click to collapse
It's really not so important, but there's always some risk with you change bootloaders or flash anything to the device. I just know that with this being a Verizon device running in EU, any OTA updates from Verizon (I assume) would never get installed. I was really just looking for a way to keep OTA updates flowing, and as a plus, remove the Verizon bloatware.
I appreciate your candid and informational response! I might just give this a try while I'm over there. =)
X
xarius76 said:
I was unaware the boot loader on this had not been unlocked yet. Seeing as it's been out a year, I just assumed it had been by this point. My bad!
Click to expand...
Click to collapse
This is a substantial annoyance to many people, though there are some hopes of working around this...
xarius76 said:
It's really not so important, but there's always some risk with you change bootloaders or flash anything to the device. I just know that with this being a Verizon device running in EU, any OTA updates from Verizon (I assume) would never get installed. I was really just looking for a way to keep OTA updates flowing, and as a plus, remove the Verizon bloatware.
Click to expand...
Click to collapse
I won't swear to it, but I was under the impression the updates come from LG, at which point it should still nominally update if brought to the EU. Failing that, LG Bridge should be able to get updates.
xarius76 said:
I appreciate your candid and informational response! I might just give this a try while I'm over there. =)
Click to expand...
Click to collapse
Remember, this is risky though hopeful.
You may need to use Odin3_v3.12_PrinceComsy
- G930UUEU4BQD2_G930UOYM4BQD2_ATT.zip
Thanks a bunch! I've been trying to download it with no success
Thank you. Time to tinker again...haha
Yeah I'm gonna get this rooted and hopefully get some performance back after UPDATE: i rooted successfully but after i tried to fix the fingerprint sensor issue my phone would only boot to recovery and download mode so i flashed to stock
It turns out that when I flashed those files it kept trying to activate my phone on the sprint network instead of att and also it made my settings go wonky so I'm downloading the u firmware with the att product code again because it messed it all up
Just a heads up, I was unable to get the EngBoot Kernel working on this ROM. It would reboot on its own every 2-3 minutes. I spent about 6 hours on this until I gave up and flashed the ATT ROM and then EngBoot. That worked just fine (except for the performance issues).
fatbas202 said:
Just a heads up, I was unable to get the EngBoot Kernel working on this ROM. It would reboot on its own every 2-3 minutes. I spent about 6 hours on this until I gave up and flashed the ATT ROM and then EngBoot. That worked just fine (except for the performance issues).
Click to expand...
Click to collapse
Can you link to ATT Nougat EngBoot rom? I wanted to upgrade to Nougat, wipe, and then get Nougat EngBoot rom on their, but I don't want to use Sprint or whatever that other carrier was. (Prefer to use ATT on ATT devices, ya know?)
Hey I finally was able to get my phone working right I forgot to flash the csc
loganbeck14 said:
Hey I finally was able to get my phone working right I forgot to flash the csc
Click to expand...
Click to collapse
Glad to hear it.
muniz_ri said:
Glad to hear it.
Click to expand...
Click to collapse
Hey can you get the usc product code version for me I have tried to download that specific version but it always corrupts itself and i could only use this version but I had my phone unlocked which means I need a different version so that I can detect my sim card and hopefully set the apn settings acordingly
loganbeck14 said:
Hey can you get the usc product code version for me I have tried to download that specific version but it always corrupts itself and i could only use this version but I had my phone unlocked which means I need a different version so that I can detect my sim card and hopefully set the apn settings acordingly
Click to expand...
Click to collapse
I will try to download it from Sammobile at some point but they seem to be doing maitenance on the site this weekend.
Ok I just want to make sure I'm not going crazy over this so thanks
If I'm using a G930T but using Cricket at my carrier should I flash this or.the TMO variant that you posted in the T-Mobile S7 forum?
A0425A said:
If I'm using a G930T but using Cricket at my carrier should I flash this or.the TMO variant that you posted in the T-Mobile S7 forum?
Click to expand...
Click to collapse
I don't know if it will make any difference but I would try the t-mo version to match your device.
Help!!! I went ahead and flashed the TMO version of the 930u code. I downloaded the ZIP. Placed all the right files in the correct place in Odin (comsey odin) and finished the process. The phone didn't reboot even though reboot was checked. Now I'm in a boot loop. Help!!
Update:. For it to work after flashing a second time. Not sure what happened the first time.
Sent from my Nexus 7 using Tapatalk