Related
Here is the OTA Kitkat update
https://drive.google.com/file/d/0B7UQWkPdlFVDbHdQc1EzdTEyR1k/edit?usp=sharing
not work witch cwm or other custom recovery, if tried not working, need stock recovery, and stock rom us.
share it if you find the solution.
Click to expand...
Click to collapse
Note: Dont worry if dont see icon H+ when you flashes Stock Rom US, I Test Velocity, is HSPA +. You can see the screenshot int attached.
1.- For Install just flash stock rom IMPORTANT umts.Retail.en.US http://sbf.droid-developers.org/phone.php?device=14
2.- Copy the OTA KITKAT 4.4.2 to sdcard or use adb sideload
3.- Apply update from sdcard
4.- Enjoy :laugh:
Root Working method:
http://forum.xda-developers.com/showthread.php?t=2583652
Merry Christmas
Best regards Amigos
Downloading, testing on a UK XT1032
Fails to apply over UK firmware due to incorrect device id. I guess I'll need to flash 4.3 US first...
---------- Post added at 09:35 AM ---------- Previous post was at 09:18 AM ----------
nupi said:
Downloading, testing on a UK XT1032
Fails to apply over UK firmware due to incorrect device id. I guess I'll need to flash 4.3 US first...
Click to expand...
Click to collapse
Now I get mismatch between expected falcon_umts and existing xt1032. Guess I'll have to see about hacking the install script.
nupi said:
Downloading, testing on a UK XT1032
Fails to apply over UK firmware due to incorrect device id. I guess I'll need to flash 4.3 US first...
---------- Post added at 09:35 AM ---------- Previous post was at 09:18 AM ----------
Now I get mismatch between expected falcon_umts and existing xt1032. Guess I'll have to see about hacking the install script.
Click to expand...
Click to collapse
yep, you need modified script or install stock rom us
ZealotRush said:
yep, you need modified script or install stock rom us
Click to expand...
Click to collapse
Even stock US didn't seem to help.
Flashed stock US again and wiped data this time round, the device still identifies as xt1032 instead of the required falcon_umts
Playing around with the script now... Actually, come to think of it, would you be able to post a CWM backup of the applied OTA? that ought to be much easier
I just tried to flash this update over official US global fw (http://forum.xda-developers.com/showthread.php?t=2578997) on a fr Moto G. I got an error during the verification of the curre,t system: "not enough free space on /system to appl patches. Installation aborted."
F***...
Any idea?
-----Update-----
The first try was with the original recovery.
I just tried with cwm, it says the device is xt1032 but the package is for falcon_umts...
When attempting to flash via CWM on UK XT1032, the following is returned:
Package expects build fingerprint of motorola/falcon_retuglb/falcon_utms:4.3/14.10.0Q3.X-84-16/6:user/release-keys or motorla/falcon_retuglb/falcon_utms:4.4.2/KXB20.9-1.8-1.1/4:user/release-keys; this device has motorola/cm_xt1032:4.3.1/JLS36I/126
Click to expand...
Click to collapse
lost101 said:
When attempting to flash via CWM on UK XT1032, the following is returned:
Click to expand...
Click to collapse
Did you flash US stock firmware first? (though for me that didn't help, either)
No, UK GSM XT1032 with Stock Retail Rom. What to see if it can be forced onto non-US XT1032. Changing device name from 'falcon_retgb' to 'falcon_retuglb' using Android Model Changer makes no difference.
EDIT: Forgot to change build number.
lost101 said:
No, UK GSM XT1032 with Stock Retail Rom. What to see if it can be forced onto non-US XT1032. Changing device name from 'falcon_retgb' to 'falcon_retuglb' using Android Model Changer makes no difference.
EDIT: Forgot to change build number.
Click to expand...
Click to collapse
Since the OTA is a patch rather than a full firmware, I doubt forcing it onto another base would work (UK and US do not behave entirely the same, even after initial boot up!)...
Has anybody tried flashing this over the telus/koodo version of the moto G?
It appears the device name is stored somewhere outside of android. So to flash the US ROM is not enough. Two obvious choices: Find that location and change it, if that's even possible, or attempt to modify the install script.
You must be doing something wrong. The OTA flashes fine here onto a UK device running US Global ROM.
You must be running the US_retail_XT1032_14.10.0Q3.X-84-16_CFC.xml.zip ROM on your device with an unlocked bootloader. Ignore the errors whilst flashing the ROM. Let the phone boot up once, then turn it off. Open bootloader menu then go to recovery and open it. Now use adb sideload to push the Blur_Version.14.14.16.falcon_umts.Retail.en.US.zip OTA over to the phone and flash it. Wait for the patching to finish and you'll be on US global kitkat.
Before anyone asks.. sorry but I don't have the time to extract the system as it's Christmas and I have family stuff to deal with.
1. I am not a "noob" I am flashing roms, kernel and recovery since the begining of Android.
2. I have done exactly what you said:
I followed the other thread, i am in US_retail_XT1032_14.10.0Q3.X-84-16_CFC (i verified it in settings)
I tried to flash the file by sideload, by copy and flash from the original recovery and cwm and it does not work!
SouSoulebarbu said:
1. I am not a "noob" I am flashing roms, kernel and recovery since the begining of Android.
2. I have done exactly what you said:
I followed the other thread, i am in US_retail_XT1032_14.10.0Q3.X-84-16_CFC (i verified it in settings)
I tried to flash the file by sideload, by copy and flash from the original recovery and cwm and it does not work!
Click to expand...
Click to collapse
Agreed and even removing the falcon_umts check in the install script does nothing, the update never actually proceeds on my device.
SouSoulebarbu said:
1. I am not a "noob" I am flashing roms, kernel and recovery since the begining of Android.
2. I have done exactly what you said:
I followed the other thread, i am in US_retail_XT1032_14.10.0Q3.X-84-16_CFC (i verified it in settings)
I tried to flash the file by sideload, by copy and flash from the original recovery and cwm and it does not work!
Click to expand...
Click to collapse
All the update checks for is the correct build fingerprint in build.prop so I don't quite understand why you are having problems. You do have an XT1032 device right?
Excellent!!! Installed without problems
Enviado desde mi XT1032 mediante Tapatalk
m_loaiza said:
Excellent!!! Installed without problems
Enviado desde mi XT1032 mediante Tapatalk
Click to expand...
Click to collapse
From which software versión did you come from?
newdeal99 said:
Has anybody tried flashing this over the telus/koodo version of the moto G?
Click to expand...
Click to collapse
Yes I have this phone and have flashed the US Global. All works but you will lose HSPA+ and only get 3G!
psychodogg said:
Yes I have this phone and have flashed the US Global. All works but you will lose HSPA+ and only get 3G!
Click to expand...
Click to collapse
You still get HSPA. It's just shown as '3G' on US devices rather that 'H'.
---------- Post added at 05:57 PM ---------- Previous post was at 05:32 PM ----------
Gone back to the UK ROM myself. Keep losing cell signal with the US global ROM which is weird as I thought the US Global was supposed to be pretty much the same as the European global?.. I'm on EE.
flibblesan said:
You still get HSPA. It's just shown as '3G' on US devices rather that 'H'.
---------- Post added at 05:57 PM ---------- Previous post was at 05:32 PM ----------
Gone back to the UK ROM myself. Keep losing cell signal with the US global ROM which is weird as I thought the US Global was supposed to be pretty much the same as the European global?.. I'm on EE.
Click to expand...
Click to collapse
i test velocity dont worry for an icon, is nesesary an stock rom us and recovery for the moment.
I have been reading these two threads closely:
http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
http://forum.xda-developers.com/google-nexus-5/help/faq-to-android-read-post-root-t2508292
But one thing I am yet to understand, is how do you go about flashing a baseband? What I've learned so far, is not to rely on toolkits. I will follow the directions from the first link, which seem pretty straightforward.
I downloaded the factory image "KOT49H" which corresponds with the baseband I want to flash, that being from 4.4.2. If I want to flash the baseband only, would the command be something like this?
fastboot flash radio radio-hammerheadx.x.x.x.x.x.x..img
Click to expand...
Click to collapse
darksome123 said:
I have been reading these two threads closely:
http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
http://forum.xda-developers.com/google-nexus-5/help/faq-to-android-read-post-root-t2508292
But one thing I am yet to understand, is how do you go about flashing a baseband? What I've learned so far, is not to rely on toolkits. I will follow the directions from the first link, which seem pretty straightforward.
I downloaded the factory image "KOT49H" which corresponds with the baseband I want to flash, that being from 4.4.2. If I want to flash the baseband only, would the command be something like this?
Click to expand...
Click to collapse
almost all the radios are available in zip format(check the xda thread for the zips. all you do is download one, then go into your custom recovery and flash it there. it takes seconds, then boot up after that. btw, radio and baseband is the same thing in this conversation.
---------- Post added at 03:41 PM ---------- Previous post was at 03:39 PM ----------
darksome123 said:
I have been reading these two threads closely:
http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
http://forum.xda-developers.com/google-nexus-5/help/faq-to-android-read-post-root-t2508292
But one thing I am yet to understand, is how do you go about flashing a baseband? What I've learned so far, is not to rely on toolkits. I will follow the directions from the first link, which seem pretty straightforward.
I downloaded the factory image "KOT49H" which corresponds with the baseband I want to flash, that being from 4.4.2. If I want to flash the baseband only, would the command be something like this?
Click to expand...
Click to collapse
if you are using fastboot to flash a radio then that is the correct command. but, as i said, its much easier to download a zipped up version and flash in recovery.
darksome123 said:
I have been reading these two threads closely:
http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
http://forum.xda-developers.com/google-nexus-5/help/faq-to-android-read-post-root-t2508292
But one thing I am yet to understand, is how do you go about flashing a baseband? What I've learned so far, is not to rely on toolkits. I will follow the directions from the first link, which seem pretty straightforward.
I downloaded the factory image "KOT49H" which corresponds with the baseband I want to flash, that being from 4.4.2. If I want to flash the baseband only, would the command be something like this?
Click to expand...
Click to collapse
yes that's how it would look like if you want to flash a .img radio file via fastboot
http://forum.xda-developers.com/goo...t/modem-nexus-5-flashable-modems-efs-t2514095
or just download the radio zip you want and flash in recovery,
simms22 said:
almost all the radios are available in zip format(check the xda thread for the zips. all you do is download one, then go into your custom recovery and flash it there. it takes seconds, then boot up after that. btw, radio and baseband is the same thing in this conversation.
---------- Post added at 03:41 PM ---------- Previous post was at 03:39 PM ----------
if you are using fastboot to flash a radio then that is the correct command. but, as i said, its much easier to download a zipped up version and flash in recovery.
Click to expand...
Click to collapse
That was the other question I had. So simply download the zipped file to my phone and flash it in recovery mode, right?
darksome123 said:
That was the other question I had. So simply download the zipped file to my phone and flash it in recovery mode, right?
Click to expand...
Click to collapse
right, that easy. if you want to be safe, make a backup in recovery before flashing. that way if the new radio gives you issues, all you have to do is restore the backup.
I've never flashed anything, but have been doing my research for the last few months. Everything seems pretty easy to follow. I guess the coward in me never really gave it a chance. I'll give it a go and do a follow up on the results.
Thank you so much for the help.
darksome123 said:
I've never flashed anything, but have been doing my research for the last few months. Everything seems pretty easy to follow. I guess the coward in me never really gave it a chance. I'll give it a go and do a follow up on the results.
Thank you so much for the help.
Click to expand...
Click to collapse
are you not happy with your current radio? i do it occasionally, to check if another radio is better. if so, ill keep it, if not, ill flash to the previous radio i had. but anything you flash, if you make a backup in recovery first, itll save what you had before flashing, rom as well. when i first rooted ages ago(g1), it also took me month of reading before doing anything. but once familiar with it, it doesnt take any thought anymore, and ive been helping others with it here on xda since.
After the update from 4.4.2 to 4.2.3 and then to 4.4.4...reception kept getting worse. And then there was the battery issue, I used to be able to keep a charge for over 24 hours...now it doesn't last more than 5 hours. Some individuals from another forum have attributed it to the baseband. Several of them went back to the 4.4.2 version and say the battery issue is gone. I've tried everything and this seems like the last resort.
darksome123 said:
After the update from 4.4.2 to 4.2.3 and then to 4.4.4...reception kept getting worse. And then there was the battery issue, I used to be able to keep a charge for over 24 hours...now it doesn't last more than 5 hours. Some individuals from another forum have attributed it to the baseband. Several of them went back to the 4.4.2 version and say the battery issue is gone. I've tried everything and this seems like the last resort.
Click to expand...
Click to collapse
the radio that came with L gave me issues, the radio before that worked fine, so i went back to that. it would all depend on your location, in how well they work for you.
OK so on an unrelated note, now that I'm unlocked what does this mean now that Android Lollipop is about to be released? How will an OTA update affect my phone? The modifications I've made so far is installed CWM recovery and SuperSU, reverted baseband to previous 4.4.2 version, and changed the kernel to Franco Kernel. All other system apps are intact.
Sent from my Nexus 5 using XDA Free mobile app
darksome123 said:
OK so on an unrelated note, now that I'm unlocked what does this mean now that Android Lollipop is about to be released? How will an OTA update affect my phone? The modifications I've made so far is installed CWM recovery and SuperSU, reverted baseband to previous 4.4.2 version, and changed the kernel to Franco Kernel. All other system apps are intact.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
You won't get OTA because you're too modified. But now you're rooted, you owe it to yourself to learn how to manage your modified phone. OTA is the worst way to update in your situation.
Learn about flashing ROMs. All info and guides are in my signature
darksome123 said:
OK so on an unrelated note, now that I'm unlocked what does this mean now that Android Lollipop is about to be released? How will an OTA update affect my phone? The modifications I've made so far is installed CWM recovery and SuperSU, reverted baseband to previous 4.4.2 version, and changed the kernel to Franco Kernel. All other system apps are intact.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
you cant get a flashable ota. you might get an ota, but it wont flash. only the original rom with all of its files intact can receive and apply an ota. a day or two after source is released, youll be able to flash a rooted version. or you can flash the factory img and reroot.
I think I may write a thread about this.
So it sounds like a rooted version would be the easiest thing for me then. Now, it won't delete all my data will it? As in a typical OTA update all the data remains intact. Any suggestions as to where I should be looking for a rooted versiob when it is released?
darksome123 said:
So it sounds like a rooted version would be the easiest thing for me then. Now, it won't delete all my data will it? As in a typical OTA update all the data remains intact. Any suggestions as to where I should be looking for a rooted versiob when it is released?
Click to expand...
Click to collapse
I'm positive you'll have to do a full wipe to flash the 5.0 rom. So, yes you'll lose your data. You could try just flashing the system.img and boot.img from 4.4.4 then taking the ota. But back up everything off your device. 5.0 is a different animal and most likely will require a full wipe before working correctly.
Sent from my Nexus 5 using XDA Free mobile app
Say I were to reinstall the previous baseband along with the stock kernel, I still have stock android running, couldn't I just flash the ROM through fastboot or through CWM?
Sent from my Nexus 5 using XDA Free mobile app
darksome123 said:
Say I were to reinstall the previous baseband along with the stock kernel, I still have stock android running, couldn't I just flash the ROM through fastboot or through CWM?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Could you expand on your question please?
rootSU said:
Could you expand on your question please?
Click to expand...
Click to collapse
I have stock Android 4.4.4, but the baseband from 4.4.2 along with Franco Kernel. If I were to revert these to the originals found in 4.4.4, would it be enough to fastboot a rooted version of Lollipop, without running into trouble? As I understand it, even if I were to revert these I still wouldn't be able to get OTA because of CWM recovery. Am I correct?
Sent from my Nexus 5 using XDA Free mobile app
darksome123 said:
I have stock Android 4.4.4, but the baseband from 4.4.2 along with Franco Kernel. If I were to revert these to the originals found in 4.4.4, would it be enough to fastboot a rooted version of Lollipop, without running into trouble? As I understand it, even if I were to revert these I still wouldn't be able to get OTA because of CWM recovery. Am I correct?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
You wouldn't need to revert to fastboot. Fastboot will replace these so it doesn't care what's there now.
Have a read of the thread in my signature about rooted users updating.
I bought a Motorola XT925 on ebay branded Orange France and loaded with Jelly Bean 4.1.1 firmware.
The phone was sold to me as a 4G/LTE capable device. Not seeing an option for 4G/LTE in the phones menu, I then dug around the Orange France web portal. There it says the phone is not 4G/LTE compatible. This was confirmed by Motorola France.
So my big question: is the radio hardware in this Orange France phone the same as an XT925 that I would by from Rogers Canada, but just not initialized for 4G/LTE? Or is the actual Radio hardware different? Even Motorola France was not able to tell me over the phone about the exact hardware.
Do I have a hope to get 4G/LTE working on this phone?
I want to try a Rogers firmware on this phone, but don't want a 200,00$ paperweight.
Thanks for reading.
is the bootloader unlocked? check by booting into apfast mode. Moto website can unlock your BL if needed, after that you can test any firmware and flah any radio of course with caution .There is hope.
hbenz2008 said:
is the bootloader unlocked? check by booting into apfast mode. Moto website can unlock your BL if needed, after that you can test any firmware and flah any radio of course with caution .There is hope.
Click to expand...
Click to collapse
I have a custom recovery utility installed after rooting and unlocking the bootloader and just completed a backup on the phone. I figure since the phone is wearing jelly bean 4.1.1 I ought to be able to take the Rogers firmware jellybean 4.1.2 and flash that onto the phone. Just not sure how to make sure that the modem gets flashed when I do fastboot flash system system.img. So I am looking around to piece together the instructions on how to flash the modem or does the system image contain all I need for the modem and all else?
I kinda like the lock screen on the Orange.fr firmware -- has a sliding mute feature that might not stick around after a system flash. minor detail though as all I really want is a working LTE device.
Thanks
Rsd lite 6.1 to flash
hbenz2008 said:
Rsd lite 6.1 to flash
Click to expand...
Click to collapse
RSD Lite is a windows utility and at the present time I do not have a windows computer. I have unlocked the bootloader and flashed the recovery successfully with mfastboot for linux. So that;s where I am at. ( I find it ironic that a phone OS based oin linux should be largely dependent on a non-linux OS. Strange but true.
@hbenz2008 tell me about flashing the modem so that I can have LTE/4G access. What do I need to do?
excellent man, did you update to kitkat yet? you are free to try firmware from any carrier now. Look here for some Jelly Bean downloads to try:
http://sbf.droid-developers.org/phone.php?device=6
Then there are many ways to get on kitkat if you wish.
hbenz2008 said:
excellent man, did you update to kitkat yet? you are free to try firmware from any carrier now. Look here for some Jelly Bean downloads to try:
http://sbf.droid-developers.org/phone.php?device=6
Then there are many ways to get on kitkat if you wish.
Click to expand...
Click to collapse
I have downloaded the 4.1.2 Rogers firmware but to be honest I don't know exactly what or how to do with the zip file. I've opened the archive -- I even flashed the modem and all the rest of the blobs onto the phone, one by one based on a batch file from another archive. What happened was I lost my patience waiting for the phone to reboot as it appeared to be stuck on the Motorola boot logo. (Maybe it was rebuilding the cache??) I used the recovery to get the phone back. So if you can give me a clue as to what to do exactly with the firmware zip -- much appreciate your council.
i dont have a mac but i will try to get you some instructions. Under windows, we just rsd the xml file after extracting the firmware. This may help
http://forum.xda-developers.com/showthread.php?t=1165672
http://forum.xda-developers.com/showthread.php?t=994918
hbenz2008 said:
i dont have a mac but i will try to get you some instructions. Under windows, we just rsd the xml file after extracting the firmware. This may help
http://forum.xda-developers.com/showthread.php?t=1165672
http://forum.xda-developers.com/showthread.php?t=994918
Click to expand...
Click to collapse
I dug up an old netbook with xp on it and managed to use RDSlite it to flash the Rogers firmware and voila! Full service phone. except for one tiny snag. Earlier I had installed a custom recovery utility cwm6.2.2.8-XT925(epinter) and it worked. Now though the cwm recovery util got wiped and my subsequent attempts to re-install fail. I speak: "linux-fastboot flash recovery cwm.img. response: Max 30M sending recovery.
Weird it never progresses or finishes. Beginning to think I have the syntax wrong.
Try mfasboot
---------- Post added at 08:28 AM ---------- Previous post was at 08:26 AM ----------
Fastboot flash recovery recovery.img is the right cmd
hbenz2008 said:
Try mfasboot
---------- Post added at 08:28 AM ---------- Previous post was at 08:26 AM ----------
Fastboot flash recovery recovery.img is the right cmd
Click to expand...
Click to collapse
Thats what I have as a linux version (mfastboot). Got it from a link posted by @ATTACK and it worked properly before I flashed 4.1.2 today. I'll work on it at least now I have a phone that works and shows the options I was sold. Just wondering if RSDLite does something crippling when it writes the flash to the phone.
Rsd is clean. You can always try other recoveries. Cmw6.0.4.4 if I remember correctly works
---------- Post added at 09:20 AM ---------- Previous post was at 09:19 AM ----------
And twrp 6.0.
hbenz2008 said:
Rsd is clean. You can always try other recoveries. Cmw6.0.4.4 if I remember correctly works
---------- Post added at 09:20 AM ---------- Previous post was at 09:19 AM ----------
And twrp 6.0.
Click to expand...
Click to collapse
So something does seem to have changed. I no longer have permission to erase with the mfastboot utility. And I am refering to permission on the device not in my local shell. I sudo to the shell locally then run fastboot which returns the following:
gryphon platform-tools # fastboot erase recovery
(bootloader) Variable not supported!
erasing 'recovery'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.034s
gryphon platform-tools
the device status code is 3 and unlocked so I am baffled.
i have fought that error before but dont recall what solved it. Either another recovery or flashing with fastboot, or mfastboot.
hbenz2008 said:
i have fought that error before but dont recall what solved it. Either another recovery or flashing with fastboot, or mfastboot.
Click to expand...
Click to collapse
If you think of another possible solution let me know. As of now no fastboot utility works on my phone now.
At one point I also downloaded android sdk from Google and used fastboot tools/platform to flash things up.
hbenz2008 said:
At one point I also downloaded android sdk from Google and used fastboot tools/platform to flash things up.
Click to expand...
Click to collapse
I have the android-sdk installed and the fastboot included is known to cause problems with image files that are large. Thats where mfastboot comes in handy.
Now everytime I powercycle the phone fastboot appears on the screen and shows a failed flash notice. I'd like to clear up this issue pronto. what a pain . An adventurous pain
Maybe flash a different recovery with it hopefully overwrite what's in the phone. If not, flashing 4.1.2 with rsd and a fresh recover maybe an easier way. Even European 4.1.2 rtfr modified to get kk update. There is a thread:make your xt 925 updatable. Check it out, you may kill two birds with 5 stones
while you at it man, can you please grab "gps.conf " from system/etc and post here .It is about 2kb size. Merci
hbenz2008 said:
Maybe flash a different recovery with it hopefully overwrite what's in the phone. If not, flashing 4.1.2 with rsd and a fresh recover maybe an easier way. Even European 4.1.2 rtfr modified to get kk update. There is a thread:make your xt 925 updatable. Check it out, you may kill two birds with 5 stones
Click to expand...
Click to collapse
Good news! I got the fastboot flash failure flag cleared away and cwm recovery reinstalled. Still can't flash anything with fastboot of any stripe and I am betting this is because the image files in the sbf archive are signed. My phone is now vritualy identical to any Fido branded phone, complete with a Fido boot logo. Cute.
There ought to be a way to overwrite signed images, besides waiting for a new firmware release. The bootloader is unlocked and phone rooted yet fastboot flashing is not currently possible.
How can I unlock the signed images on my phone?
BTW heres my gps.conf. Whats your interest in this file?
Code:
#Test
#NTP_SERVER=time.gpsonextra.net
#Asia
# NTP_SERVER=asia.pool.ntp.org
#Europe
# NTP_SERVER=europe.pool.ntp.org
#North America
NTP_SERVER=north-america.pool.ntp.org
XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra2.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra2.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra2.bin
# DEBUG LEVELS: 0 - none, 1 - Error, 2 - Warning, 3 - Info
# 4 - Debug, 5 - Verbose
DEBUG_LEVEL = 2
# Intermediate position report, 1=enable, 0=disable
INTERMEDIATE_POS=0
# supl version 1.0
SUPL_VER=0x10000
Hi guys! I flashed the cm12.1 rom and then the gapps zip. Everything worked fine but with no LTE. So I flashed a 6045l 6.x modem radio and now the sim card is undetected. I flashed back to stock MM and my sim card is still undetected. Is there a fix for this?
I'm on the cricket USA michigan service on the 6945l model.
You flashed back using mobile upgrade software?
I had the same problem and had to reflash the Panasonic Eluga firmware to get my SIM to detect again (then had to restore a TWRP backup after another failed attempt to get LTE back). It seems the 6045i_6.0.1_K7VAUEB0BG00_radio_update_usa.zip from famewolf's Mega folder breaks SIM detection (or I failed to flash it properly ). After coming across this thread, I'm now looking for those referenced files to hopefully restore LTE to my phone.
KJMagnum said:
I had the same problem and had to reflash the Panasonic Eluga firmware to get my SIM to detect again (then had to restore a TWRP backup after another failed attempt to get LTE back). It seems the 6045i_6.0.1_K7VAUEB0BG00_radio_update_usa.zip from famewolf's Mega folder breaks SIM detection (or I failed to flash it properly ). After coming across this thread, I'm now looking for those referenced files to hopefully restore LTE to my phone.
Click to expand...
Click to collapse
I have the 5.02 files from an untouched 6045I, that I use on cricket, it fixed my sim and lte issues, I'm not at home right now but if you think they can help, I can post them when I get home. I flashed them via fastboot, then ran mobile upgrade q and everything was fixed, I'm pretty sure I would not have had to use mobile q, and simply flashing those files allowed eluga switch even to see cricket lte, they just are not 6.0.1 versions so not sure how they would work on a MM rom. Let me know if you want them......
Edit: I see you were flashing CM 12.1, they should work fine just enter fastboot and flash the files after installing 12.1
kal250 said:
I have the 5.02 files from an untouched 6045I, that I use on cricket, it fixed my sim and lte issues, I'm not at home right now but if you think they can help, I can post them when I get home. I flashed them via fastboot, then ran mobile upgrade q and everything was fixed, I'm pretty sure I would not have had to use mobile q, and simply flashing those files allowed eluga switch even to see cricket lte, they just are not 6.0.1 versions so not sure how they would work on a MM rom. Let me know if you want them......
Edit: I see you were flashing CM 12.1, they should work fine just enter fastboot and flash the files after installing 12.1
Click to expand...
Click to collapse
I would appreciate those files when you get a chance. Mobile Q did not restore those files/partitions so I'm running the Eluga lollipop files with a 6.0.1 Project Material build from The Marionette and everything works aside from LTE.
KJMagnum said:
I would appreciate those files when you get a chance. Mobile Q did not restore those files/partitions so I'm running the Eluga lollipop files with a 6.0.1 Project Material build from The Marionette and everything works aside from LTE.
Click to expand...
Click to collapse
here ya go just execute the following
https://mega.nz/#!2c9UVZiA!dxnaFqBgaxi-mp4TrOowD7Qx6AkcPHG7cmUZL4_i1LU
adb reboot bootloader
fastboot -i 0x1bbb flash fsg fsg
fastboot -i 0x1bbb flash modem modem
fastboot -i 0x1bbb flash modemst1 modemst1
fastboot -i 0x1bbb flash modemst2 modemst2
this worked for me and my 6045I variant, you have the 6045O(cricket) variant, I don't see any issues with it working, the radios cant be any different, but you do assume all risk.....
same problem here
kal250 said:
here ya go just execute the following
adb reboot bootloader
fastboot -i 0x1bbb flash fsg fsg
fastboot -i 0x1bbb flash modem modem
fastboot -i 0x1bbb flash modemst1 modemst1
fastboot -i 0x1bbb flash modemst2 modemst2
this worked for me and my 6045I variant, you have the 6045O(cricket) variant, I don't see any issues with it working, the radios cant be any different, but you do assume all risk.....
Click to expand...
Click to collapse
i have the same problem , please can you share key encryption for mega? thanks for your work
vicman2085 said:
i have the same problem , please can you share key encryption for mega? thanks for your work
Click to expand...
Click to collapse
Sorry about that see post above link has been updated with key....
---------- Post added at 07:52 AM ---------- Previous post was at 07:16 AM ----------
gamerlady96 said:
Hi guys! I flashed the cm12.1 rom and then the gapps zip. Everything worked fine but with no LTE. So I flashed a 6045l 6.x modem radio and now the sim card is undetected. I flashed back to stock MM and my sim card is still undetected. Is there a fix for this?
I'm on the cricket USA michigan service on the 6945l model.
Click to expand...
Click to collapse
See fix a few posts above.... You will have to downgrade to eluga switch firmware to do this fix
http://forum.xda-developers.com/idol-3/general/guide-repair-idol-3-t3372076
Also see...
http://forum.xda-developers.com/idol-3/help/warning-eluga-switch-rom-disables-s-lte-t3470543/page1
lte is working
thank you lte is working now
vicman2085 said:
thank you lte is working now
Click to expand...
Click to collapse
Yeah, I was so relieved when it fixed mine, lol but now I have a backup phone, I could not afford, I guess I could always return it to amazon but for 100$ with the JBL earbuds, i may just keep it. Glad it helped you out.
KJMagnum said:
I would appreciate those files when you get a chance. Mobile Q did not restore those files/partitions so I'm running the Eluga lollipop files with a 6.0.1 Project Material build from The Marionette and everything works aside from LTE.
Click to expand...
Click to collapse
Did you get a chance to see if these helped your issue?
kal250 said:
Did you get a chance to see if these helped your issue?
Click to expand...
Click to collapse
I was swamped with work and had to wait until my phone could be down (just in case). Thanks a bunch for the files and adb commands; I loaded them tonight and LTE is back. :good:
KJMagnum said:
I was swamped with work and had to wait until my phone could be down (just in case). Thanks a bunch for the files and adb commands; I loaded them tonight and LTE is back. :good:
Click to expand...
Click to collapse
Glad, everything worked out for you. I was so panicked when I lost LTE, I just assumed using Alcatels upgrade Q software it would fix things, but apparently it does not restore all partitions, which is strange, but at least there is a solution for it now. I have seen posts as far back as June where people have lost LTE, and we are just now finding out how to fix it, thanks to @Mario223 for providing the solution!!
kal250 said:
Did you get a chance to see if these helped your issue?
Click to expand...
Click to collapse
I sent this device to Europe,used eluga to downgrade and then installed Aleks OS and sim card is not detected at all. You think this would fix the issue? don't matter if LTE works as long as H+ is ok.
EDIT: service restored with these radio images.
Now i would like to try maybe European radio to see if LTE will work? does anyone have it?
patt2k said:
I sent this device to Europe,used eluga to downgrade and then installed Aleks OS and sim card is not detected at all. You think this would fix the issue? don't matter if LTE works as long as H+ is ok.
EDIT: service restored with these radio images.
Now i would like to try maybe European radio to see if LTE will work? does anyone have it?
Click to expand...
Click to collapse
Sorry I didn't get back with you sooner, it was a rough day... I have had that happen once, I had to flash those files with sim inserted. Glad things worked out...
Would you happen to have European radio for Europe lte bands? Just to try out both. But I'm guessing eluga baseband didn't work so it's better to keep it with USA lte radios. At least it works.
patt2k said:
Would you happen to have European radio for Europe lte bands? Just to try out both. But I'm guessing eluga baseband didn't work so it's better to keep it with USA lte radios. At least it works.
Click to expand...
Click to collapse
I don't have a backup of those, but anyone with a Y variant may be able to help...
delete
---------- Post added at 08:13 PM ---------- Previous post was at 08:12 PM ----------
kal250 said:
I don't have a backup of those, but anyone with a Y variant may be able to help...
Click to expand...
Click to collapse
I have the same problem on 6045Y variant after phanasonic Eluga I lost some bands. The very strange thing and that if I install with phanasonic Eluga leaving inside the sim card of my operator (Tim Ita) recognizes the sim and everything worked, when I try to put a different sim type Vodafone Wind H3G are not recognized. I have to use it again phanasonic EUGA With Inside operator sim that I will want to use then.
I also tried using panasonic EUGA without any sim in the phone but in the end did not recognize any.
I tried with MobileQ update but ninte to do the situation remains as it exits the panasonic EUGA.
Pi would love to restore my phone as it was before I could put any SIM of any operator and was recognized.
Does anyone have the right partitions of the model 6045Y mono sim 16GB thanks in advance.
Thanks to kal250, i can confirm this worked on my mothers phone, which is a 6045Y , and restoring those files and installing 6.0.1 on top worked out well.
What is not good was the panasonic recovery which started this mess ;( but thanks again to kal250
kal250 said:
here ya go just execute the following
https://mega.nz/#!2c9UVZiA!dxnaFqBgaxi-mp4TrOowD7Qx6AkcPHG7cmUZL4_i1LU
adb reboot bootloader
fastboot -i 0x1bbb flash fsg fsg
fastboot -i 0x1bbb flash modem modem
fastboot -i 0x1bbb flash modemst1 modemst1
fastboot -i 0x1bbb flash modemst2 modemst2
this worked for me and my 6045I variant, you have the 6045O(cricket) variant, I don't see any issues with it working, the radios cant be any different, but you do assume all risk.....
Click to expand...
Click to collapse
This killed my wifi. Anyhelp? But i got 4g back
I've put together some stock flashable TWRP zips which will install firmwares for the US996. Since this is a TWRP flashable ZIP this assumes you've already got access to TWRP. I use these to update or restore the stock image easily. Wiping data so far has not been required but if you experience issues you may want to consider it.
These zips flash every partition included in the latest firmware. If you want to err on the safe side (which is what I do before testing these) you could dump images of you current partitions to roll back to in case of an issue. (dd if=/dev/block/bootdevice/by-name/{partition} of=/external_sd/backup/{partition}.img). You'll find all partitions in the updater-script.
Download:
10f - SPL 2016-12-01 - Download (md5: 5c5241beb05385f1bb62cd9931d16675)
10h - SPL 2017-04-01 - Download (md5: 9516ecc55cc3b167154ab184fb419c4b)
10k - SPL 2017-09-01 - Download (md5: 075a5bae7201bc08cc3238a64fc9882a)
10l - SPL 2017-11-01 - Download (md5: 80560956009ac459cef5d4b48e934625)
10n - SPL 2017-11-01 - Download (md5: efbb74d3cc8e688cdabdf60e63a30792)
10o - SPL 2018-02-01 - Download (md5: e52e820b9a908e4b0c19727aadd113a6)
10p - SPL 2018-04-01 - Download (md5: d10f6b5b5e4372ff1577df2fe91830b0)
SPL = Security Patch Level
Instructions:
Boot into TWRP ("reboot recovery" from shell)
Put us99610*.zip onto /external_sd/
TWRP -> Install -> /external_sd/us99610*.zip
Install your desired root: Magisk or SuperSU
TWRP -> Reboot -> System
Your device may reboot a couple times and this is normal. You will then boot into the system.
What does it do?
Flashes partition images (skipping recovery) from the kdz - http://lg-firmwares.com/lg-us996-firmwares/
Moves /system/recovery-from-boot.p to /system/recovery-from-boot.bak to prevent stock recovery from being installed on boot
Wipes cache & dalvik-cache
Note
These firmwares are a mix between USA (Unlocked US996), UCL (US Cellular), and BPT (Brightpoint) but have not had problems running cross-variants. However, one thing I'd like to point out is an issue I saw reported by another user. They stated that after they flashed US Cellar US996 updates (10h/10k/10l) their Unlocked US996 device was being picked up as the US Cellular device when attempting to use the LG website bootloader unlock. This is most likely due to the US Cellular bootloader being flashed and the device reporting a US Cellular device ID. This hasn't caused any issues when your device has already been bootloader-unlocked but I would not suggest that users re-lock their bootloader when running this US Cellular firmware as you may risk running into problems unlocking. The same user had also reported that they just flashed the 10f kdz with LGUP to correct the problem but not a risk I'd like to see anyone take. Just a word of caution.
Special thanks to,
@bullghost for the kdz extractor (https://forum.xda-developers.com/showthread.php?t=2600575)
@Tilde88 for the updater-script template w/root (https://forum.xda-developers.com/v20/development/us996-nrd90m-modded-notsostock-rom-v5-1-t3526542)
Thanks for this! Just curious, is there an actual reason we would need to format data and factory reset? Isn't this just basically the same as updating, just more manually than taking the OTA? Like the same as extracting factory images and manually flashing them on Nexus devices?
jeston said:
Thanks for this! Just curious, is there an actual reason we would need to format data and factory reset? Isn't this just basically the same as updating, just more manually than taking the OTA? Like the same as extracting factory images and manually flashing them on Nexus devices?
Click to expand...
Click to collapse
I'm just not sure that if during the OTA update there are special steps to migrate data to be compatible with the new firmware. To err on the safe side I just suggested you format. Considering it's 7.0 -> 7.0 I don't see why there would be an issue leaving your data in place so if anyone tries it, definitely report back! I personally like starting fresh slate when upgrading.
McNutnut said:
I'm just not sure that if during the OTA update there are special steps to migrate data to be compatible with the new firmware. To err on the safe side I just suggested you format. Considering it's 7.0 -> 7.0 I don't see why there would be an issue leaving your data in place so if anyone tries it, definitely report back! I personally like starting fresh slate when upgrading.
Click to expand...
Click to collapse
Cool, I'll probably give it a try after work tomorrow. I'll let you know how it goes.
Thanks for this. Any word whether 10i that could get this treatment?
The_FNG said:
Thanks for this. Any word whether 10i that could get this treatment?
Click to expand...
Click to collapse
Has the unlocked US996 gotten 10i? I was only aware of 10f. That is the only .kdz I've got access to.
Alright, finally flashed it without wiping anything. Went just fine :good:
jeston said:
Alright, finally flashed it without wiping anything. Went just fine :good:
Click to expand...
Click to collapse
Great to hear!
Link is dead
Sent from my LG-US996 using Tapatalk
mr pnut said:
Link is dead
Sent from my LG-US996 using Tapatalk
Click to expand...
Click to collapse
Working for me. Anyone else having issues?
McNutnut said:
Working for me. Anyone else having issues?
Click to expand...
Click to collapse
Ok I got it bro it's working thru chrome not thru Tapatalk app thx bud
Sent from my LG-US996 using Tapatalk
Just ran this myself-no data wipe, just followed the rest of the directions. Worked like a charm, no problems. THANK YOU!!
Added 10h. This time without the automatic root to allow users to install their own preference (SuperSU or MagiskSU).
McNutnut said:
Added 10h. This time without the automatic root to allow users to install their own preference (SuperSU or MagiskSU).
Click to expand...
Click to collapse
Awesome... since I'm new here, may I ask if there's anything that a KDZ can do that this can't? Other than "prepare the phone for a warranty return" or "sell on Swappa as stock" ??? As you know from the other thread... I'm trying to recover from some problems I was having, and I suspect that I have some corruption. I need to burn it down and hope it rises from the ashes.
DrPhant0m said:
Awesome... since I'm new here, may I ask if there's anything that a KDZ can do that this can't? Other than "prepare the phone for a warranty return" or "sell on Swappa as stock" ??? As you know from the other thread... I'm trying to recover from some problems I was having, and I suspect that I have some corruption. I need to burn it down and hope it rises from the ashes.
Click to expand...
Click to collapse
There are three files in the KDZ which aren't used in the zip: "BackupGPT", "PrimaryGPT", and "recovery". The first two appear to be the partition table structure and the last being the stock recovery. So if your partition layout got messed up, LGUP+KDZ would be able to fix that where the zip won't. I don't know for sure what else LGUP has to offer on top of that, but from what it sounds like, LGUP + KDZ can restore a bricked phone to stock. I've never had to use LGUP myself...fortunately.
What are the MD5 hashes of the zip files? I downloaded the US996-10h file, and tried to flash it, and TWRP says it's invalid. Did I do something wrong?
DrPhant0m said:
What are the MD5 hashes of the zip files? I downloaded the US996-10h file, and tried to flash it, and TWRP says it's invalid. Did I do something wrong?
Click to expand...
Click to collapse
I've got an MD5 of 9516ecc55cc3b167154ab184fb419c4b on 10h. I went ahead and downloaded the file from the link and it matches the source file I uploaded. Possibly a bad download? Give it another shot if the MD5 doesn't match. If it does match...let me know ha.
CONFIRMED! successfully flashed your US996-10h package, followed by Magisk 11.6 and it's booted and rooted! thanks for all your work and help! btw, Magisk v13.0 (0b4baad) also works in case anyone was curious. 12.0 seems to be fscked for all LGV20...
EDIT: with 10d, 10f, and now 10h whenever I reboot the screen brightness always resets to 100% even after I've set it to auto. does this happen to anyone as well?
McNutnut said:
I've got an MD5 of 9516ecc55cc3b167154ab184fb419c4b on 10h. I went ahead and downloaded the file from the link and it matches the source file I uploaded. Possibly a bad download? Give it another shot if the MD5 doesn't match. If it does match...let me know ha.
Click to expand...
Click to collapse
Yep. Bad download. It was 0.2GB shy.
I flashed the new one... and I can't thank you enough that it actually worked! Magisk v13 is installed and SafetyNet passes! I really like some of the bonuses that WETA ROM offered (bandwidth monitor and other battery/clock choices)... but I might stick with this for a while just because I've tried so long to get that crazy issue fixed.
A TWRP-flashable solution was exactly what I needed because LGUP was *not* working for me. It wouldn't even run on my PC, let alone get to the point where it would recognize my phone and flash a full fw.
:good::good::good:I wish I could thank the OP 1000x.:good::good::good:
nice, thanks for this. i'm gonna flash to just go back to a stock rooted 10f rom.
---------- Post added at 03:53 PM ---------- Previous post was at 03:49 PM ----------
wait, this won't wipe internal storage or anything right?