Related
Hi, can modems for 4.3 be patched? I know that currently Ariza patch supports all 4.1.2 except ones with MG4 modem because it uses the new efs v2, and i am asking that because i'd like to upgrade from 4.1.2 to 4.3, but, i got to have patched modem, because i'll get emergency calls only, so, is there anything yet to succesfully patch efs v2 modems on 4.3? Thanks in front.
lsalamun said:
Hi, can modems for 4.3 be patched? I know that currently Ariza patch supports all 4.1.2 except ones with MG4 modem because it uses the new efs v2, and i am asking that because i'd like to upgrade from 4.1.2 to 4.3, but, i got to have patched modem, because i'll get emergency calls only, so, is there anything yet to succesfully patch efs v2 modems on 4.3? Thanks in front.
Click to expand...
Click to collapse
Hi, do you have serial no 00000?
or imei 0049?
hierarchy666 said:
Hi, do you have serial no 00000?
or imei 0049?
Click to expand...
Click to collapse
No, everything is fine with imei and serial number, the thing is, my phone is repaired with z3x box, and now i can only change 4.1.2 roms, and then patch them with ariza patch (only 0.4 working) and i cannot use efs v2 roms/modems because i will have Emergency calls only (i will have the signal, imei, and serial number), so i have to patch modem to connect it to network (it says succesfully conected to network, but emergency calls only), i have read that i can patch with zuluman, but i am not 100% sure about that.
lsalamun said:
No, everything is fine with imei and serial number, the thing is, my phone is repaired with z3x box, and now i can only change 4.1.2 roms, and then patch them with ariza patch (only 0.4 working) and i cannot use efs v2 roms/modems because i will have Emergency calls only (i will have the signal, imei, and serial number), so i have to patch modem to connect it to network (it says succesfully conected to network, but emergency calls only), i have read that i can patch with zuluman, but i am not 100% sure about that.
Click to expand...
Click to collapse
Man if you have z3x box everything is allright im not sure why u needed ARIZA patch anyway. It's only for S/N 00000.
But if you're looking for patched 4.3
http://forum.xda-developers.com/showpost.php?p=47502714&postcount=1136
This thread would lead you there.
hierarchy666 said:
Man if you have z3x box everything is allright im not sure why u needed ARIZA patch anyway. It's only for S/N 00000.
But if you're looking for patched 4.3
http://forum.xda-developers.com/showpost.php?p=47502714&postcount=1136
This thread would lead you there.
Click to expand...
Click to collapse
The thing is, z3x currently patches and fixes only to 4.1.2, when my imei gets broken i have to downgrade to 4.0.4, patch, then upgrade again to 4.1.2, z3x doesn't support 4.3 android yet, and the thing is, when rhe phone is repaired with z3x, every single time when rom changes, or just reflashes, i get Emergency calls only, and i have to use ariza patch to reroute modem, and if you understand, i don't want to have risk fixing my phone again if something get's messed up, i'll look up to the thread you gave me.
P.S. i have read that ARIZA patch doesn't fix SN 0000 but only network issues like Emergency calls only after flashin (that says in one thread that has tutorial).
Edit: About this thread you gave me, i tried flashing stock XXEMJ9 and MK6, tried with both, patched MG4 modem, nothing, emergency calls only, also tried zuluman modem patcher v2, extracted original modem.bin, patched, also nothing, Emergency calls only, i am almost sure that z3x has messed something up, like i am stuck forever now, i'll consult with some specialist in service center
Same here...but z3x can now works with 4.3...i have the new repaired efs backed up..so no problem if IMEI gets messed up...but everytime i flash a new ROM, even if the imei is correct..it won't connect to network..so i need to take it to the repair shop and patch the modem. The guy who fixed is really pissed off at me
Should've taken it to samsung service centre(they asked 2500 in my local currency but the shop did it for 1500) Oh..the price i pay for being cheap :/
Sent from my GT-N7100 using XDA Free mobile app
update : i don't have to go to the shop anymore...i do it at home. the patched modems created with modem patcher v2 work fine. everytime i flash a rom (always stock) the imei stays correct but the "emergency calls only" appears. PC Odin doesn't let me flash the patched modem for some reason. so i root the phone and install mobile odin and flash patched modem with it...and voila!! everything works just fine! i'm running 4.4.2 ....hope this process will also work when the lollipop update arrives.
I am rooted, TWRP, on 4.3 build 2.22.xx, and I got s-off on firewater even after the newest AT&T update. I installed ViperOne yesterday and thought my phone had froze on the bootscreen, as it just sits on the HTC "This version is for development use only..." screen, for several minutes before the screen just turns off and at that point everything is fine, I just have to unlock it. I went to the Viper IRC to see if anyone could help, but they didn't seem to know what was wrong, seemed to think maybe I was on the wrong hboot version but I've always been on 3.16. So I thought I would ask here to see if anyone had any ideas. Thanks.
Fallen Advocate said:
I am rooted, TWRP, on 4.3 build 2.22.xx, and I got s-off on firewater even after the newest AT&T update. I installed ViperOne yesterday and thought my phone had froze on the bootscreen, as it just sits on the HTC "This version is for development use only..." screen, for several minutes before the screen just turns off and at that point everything is fine, I just have to unlock it. I went to the Viper IRC to see if anyone could help, but they didn't seem to know what was wrong, seemed to think maybe I was on the wrong hboot version but I've always been on 3.16. So I thought I would ask here to see if anyone had any ideas. Thanks.
Click to expand...
Click to collapse
Same for me, i updated my Viper 1.8.0 to 2.1.0 and now booting takes a long time and like described there is no boot animation
Regards,
Thomas
This also happend to me after flashing the latest build of insertcoin.
I thought it was some sort of bug and flashed back to GPE
Don't know about the missing boot animation, but long boot time and hboot 3.16 means you are on 1.XX based firmware. 2.22 based firmware is needed to fix long boot time. For AT&T in particular, 2.22.1540 firmware is recommended.
The firmware issue has been discussed in quite a few threads to this point. But good instructions here:
http://forum.xda-developers.com/showpost.php?p=54408500&postcount=9592
And also, the firmware is packaged with the following ROM, and with great instruction on how to flash (this is the one I used):
http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
redpoint73 said:
Don't know about the missing boot animation, but long boot time and hboot 3.16 means you are on 1.XX based firmware. 2.22 based firmware is needed to fix long boot time. For AT&T in particular, 2.22.1540 firmware is recommended.
The firmware issue has been discussed in quite a few threads to this point. But good instructions here:
http://forum.xda-developers.com/showpost.php?p=54408500&postcount=9592
And also, the firmware is packaged with the following ROM, and with great instruction on how to flash (this is the one I used):
http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
Click to expand...
Click to collapse
I'm on firmware 2.22.401.5 and I still get the ridiculous boot times. Do I need to update the firmware too?
EchelonBarney said:
I'm on firmware 2.22.401.5 and I still get the ridiculous boot times. Do I need to update the firmware too?
Click to expand...
Click to collapse
if you can see this version in Setting - Info - SoftwareInformation then this is wrong. This is not the real firmware version.
I also did an upgrade from Venom 1.8.0 (4.4.2) to Venom 2.1.0 (4.4.3) and Setting - Info - SoftwareInformation showed me 2.22.401.5.
You have to do a manual firmware update or go back to stock rom and let the stock rom do the firmware update.
That means: Wipe in every case!
That solved my problem.
Regards,
Thomas
funfactor71 said:
if you can see this version in Setting - Info - SoftwareInformation then this is wrong. This is not the real firmware version.
I also did an upgrade from Venom 1.8.0 (4.4.2) to Venom 2.1.0 (4.4.3) and Setting - Info - SoftwareInformation showed me 2.22.401.5.
You have to do a manual firmware update or go back to stock rom and let the stock rom do the firmware update.
That means: Wipe in every case!
Click to expand...
Click to collapse
Truth. There is some confusion about "firmware" as the term is a bit vague. In fact "firmware" can mean any software you flash to solid-state type memory; and "firmware" has often been used interchangeably with the ROM.
However, this is not what is being referred to when "updating the firmware package" (or similar recommendation) is discussed in terms of long boot times, broken WiFi, etc. when using a 2.22 based ROM. In fact, these are modules that reside on separate partitions from the ROM, and not touched when a ROM is flashed. These include hboot, radio, media, WiFi, and other modules. And its these software modules that will not play well with a 2.22 based ROM, if the firmware is not up to date.
Looking at software or build number is Settings does not tell you if your firmware is up to date. It simply tells you the software number for the ROM. There is in fact no actual "firmware number" per se; so folks will often refer to the software number that it deployed with (2.22.401, etc.) for lack of a better description/terminology. However, to confirm if the firmware was properly installed, its actually much more useful to look at hboot number and radio baseband. If you are on hboot 3.16, you do not have the updated firmware. The updated firmware will have installed hboot 3.18. The radio will also have been updated, but I'm not personally familiar with all the possible radio numbers associated with the various firmware package (although I suspect the newer firmware packages contain 1.19xxx basebands).
---------- Post added at 10:27 AM ---------- Previous post was at 10:22 AM ----------
EchelonBarney said:
I'm on firmware 2.22.401.5 and I still get the ridiculous boot times. Do I need to update the firmware too?
Click to expand...
Click to collapse
Make sure you firmware is actually updated, per my long-winded comments above.
Also, be aware that 2.22.401 firmware is not recommended for US users, but rather then 2.22.1540:
http://forum.xda-developers.com/showpost.php?p=54408500&postcount=9592
Not sure if this can cause long boot times, but US users have experienced cell connectivity issues using 2.22.401
redpoint73 said:
Don't know about the missing boot animation, but long boot time and hboot 3.16 means you are on 1.XX based firmware. 2.22 based firmware is needed to fix long boot time.
The firmware issue has been discussed in quite a few threads to this point. But good instructions here:
http://forum.xda-developers.com/show...postcount=9592
Click to expand...
Click to collapse
My duhhh. No boot animation is mentioned right in the post I linked:
The issues you will see without the new firmware include long boot times with no boot animations and some users on 9.1 reported wifi and bluetooth issues.
I knew long boot times was an issue, but no boot animation is definitely caused by outdated firmware, also.
redpoint73 said:
...
Not sure if this can cause long boot times, but US users have experienced cell connectivity issues using 2.22.401
Click to expand...
Click to collapse
I am on 2.22.401.4 and I do experience odd 4G issues (phone says it is connected but I get no data.) Switching airplane mode off and on usually fixes the issue. Are you on 2.22.1540? If so, have you experienced any dropouts? I will drop down to that firmware if it could hold a solid connection for my M8. Thanks.
revoltech said:
I am on 2.22.401.4 and I do experience odd 4G issues (phone says it is connected but I get no data.) Switching airplane mode off and on usually fixes the issue. Are you on 2.22.1540? If so, have you experienced any dropouts? I will drop down to that firmware if it could hold a solid connection for my M8. Thanks.
Click to expand...
Click to collapse
I'm on 2.22.1540 and reception is perfect.
Connection issues is a known problem with the "international" firmware 2.22.401, so I highly recommend flashing 2.22.1540.
Some AT&T folks don't even get service on 2.22.401: http://forum.xda-developers.com/att-htc-one-m8/help/service-upgrade-to-firmware-firmware2-t2834076
redpoint73 said:
I'm on 2.22.1540 and reception is perfect.
Connection issues is a known problem with the "international" firmware 2.22.401, so I highly recommend flashing 2.22.1540.
Some AT&T folks don't even get service on 2.22.401: http://forum.xda-developers.com/att-htc-one-m8/help/service-upgrade-to-firmware-firmware2-t2834076
Click to expand...
Click to collapse
Hello again, sorry to threadcrap but I just flash the 2.22.1540 firmware as recommended and all is well. However, I am curious on why the radio version did not downgrade. From the bootloader, the radio list: 1.19.21331147A1.09G which is the same radio version on 2.22.401.4 firmware. Can you please do me a favor and verify your radio version? I have a suspicion that both firmwares carry the same radio version. Thanks!
revoltech said:
Hello again, sorry to threadcrap but I just flash the 2.22.1540 firmware as recommended and all is well. However, I am curious on why the radio version did not downgrade.
Click to expand...
Click to collapse
You may have to flash the firmware twice for everything to install. This is a common issue.
redpoint73 said:
You may have to flash the firmware twice for everything to install. This is a common issue.
Click to expand...
Click to collapse
I installed the 2.22.1540.3 firmware again but it still reports the same radio version, 1.19.21331147A1.09G, and I do see in the CLI output that an radio.img is being flashed onto the device. I downloaded the firmware from mike1986. website. So, does this mean that the 2.22.401.4 firmware and the 2.22.21540.3 share the same radio.img?
This is the stock developer build radio string...compare all number's/letter's... It is possible that radio is unchanged....
revoltech said:
I installed the 2.22.1540.3 firmware again but it still reports the same radio version, 1.19.21331147A1.09G, and I do see in the CLI output that an radio.img is being flashed onto the device. I downloaded the firmware from mike1986. website. So, does this mean that the 2.22.401.4 firmware and the 2.22.21540.3 share the same radio.img?
Click to expand...
Click to collapse
Wonders_Never_Cease said:
This is the stock developer build radio string...compare all number's/letter's... It is possible that radio is unchanged....
Click to expand...
Click to collapse
Thank you for the screenshot. My radio number is identical to the one in the screenshot. There is a possibility that the version number has a slight difference on the 2.22.401.4 which I previously had installed. I appreciate the help :good:
I have been dealing with this problem for about three weeks now, and nowhere have I been able to find a workable solution to the problem. I've gone the route of wiping cache, dalvik, system and data, let the phone boot to "No OS" then attempt the flash, but so far I have just wasted time and achieved no viable ends from these various means.
Is there anyone who actually know what the problem is with this? The device is a rooted LG G3 VS985. I'm running TRWP v2.8.6.0. I would really like to get to the root of this problem (slight pun intended) so that I can get back to upgrading my ROMs as BlissRom releases them.
MoparOso said:
I have been dealing with this problem for about three weeks now, and nowhere have I been able to find a workable solution to the problem. I've gone the route of wiping cache, dalvik, system and data, let the phone boot to "No OS" then attempt the flash, but so far I have just wasted time and achieved no viable ends from these various means.
Is there anyone who actually know what the problem is with this? The device is a rooted LG G3 VS985. I'm running TRWP v2.8.6.0. I would really like to get to the root of this problem (slight pun intended) so that I can get back to upgrading my ROMs as BlissRom releases them.
Click to expand...
Click to collapse
Most likely you are failing a baseband check that CM based ROMs started doing a few weeks ago. Flash this modem before you try and flash the ROM: https://www.androidfilehost.com/?fid=95916177934553732
It should flash after that. If not, please post a screenshot of your recovery screen(vol down + power at the same time) so we can see the error.
And here's a link to our modems: http://forum.xda-developers.com/showpost.php?p=56005257&postcount=4
If you don't like the 23c modem you can flash whichever one you want after you get your ROM flashed.
startswithPendswithOOH said:
Most likely you are failing a baseband check that CM based ROMs started doing a few weeks ago. Flash this modem before you try and flash the ROM: https://www.androidfilehost.com/?fid=95916177934553732
It should flash after that. If not, please post a screenshot of your recovery screen(vol down + power at the same time) so we can see the error.
And here's a link to our modems: http://forum.xda-developers.com/showpost.php?p=56005257&postcount=4
If you don't like the 23c modem you can flash whichever one you want after you get your ROM flashed.
Click to expand...
Click to collapse
Thank you so much for an intelligent and more important workable solution to my problem. I used your modem, version 23C. It worked great. I can't thank you enough.
startswithPendswithOOH said:
Most likely you are failing a baseband check that CM based ROMs started doing a few weeks ago. Flash this modem before you try and flash the ROM: https://www.androidfilehost.com/?fid=95916177934553732
It should flash after that. If not, please post a screenshot of your recovery screen(vol down + power at the same time) so we can see the error.
And here's a link to our modems: http://forum.xda-developers.com/showpost.php?p=56005257&postcount=4
If you don't like the 23c modem you can flash whichever one you want after you get your ROM flashed.
Click to expand...
Click to collapse
This also worked for me, 23c modem prior to rom and all is well. Thank you!
startswithPendswithOOH said:
Most likely you are failing a baseband check that CM based ROMs started doing a few weeks ago. Flash this modem before you try and flash the ROM: https://www.androidfilehost.com/?fid=95916177934553732
It should flash after that. If not, please post a screenshot of your recovery screen(vol down + power at the same time) so we can see the error.
And here's a link to our modems: http://forum.xda-developers.com/showpost.php?p=56005257&postcount=4
If you don't like the 23c modem you can flash whichever one you want after you get your ROM flashed.
Click to expand...
Click to collapse
Hi all, incredibly noon here. I faced the same error but it's still present after I flashed the modem. Anyone can help? I tried to screencap but I don't think it worked in recovery mode.
help
having same problem after trying to install cm13 on lg g3 verzon tryed flashing modem 23c still no luck please help
lazy445 said:
having same problem after trying to install cm13 on lg g3 verzon tryed flashing modem 23c still no luck please help
Click to expand...
Click to collapse
You probably need the 35b modem to get past the baseband check. But the 35b modem alone may have some issues if you don't flash the whole bootstack with it. So flash this 35b bootstack 1st( https://www.androidfilehost.com/?fid=24052804347843993 ), then flash the ROM & MM gapps.
OR - if you really like the 23c or 24b modem and don't want to use the 35b, you can flash just the 35b modem( http://forum.xda-developers.com/showpost.php?p=56005257&postcount=4) to get past the check, flash the ROM, and then flash whatever modem you prefer. I use the 24b modem/boostack on MM ROMs and it works fine...not sure about 23c.
startswithPendswithOOH said:
You probably need the 35b modem to get past the baseband check. But the 35b modem alone may have some issues if you don't flash the whole bootstack with it. So flash this 35b bootstack 1st( https://www.androidfilehost.com/?fid=24052804347843993 ), then flash the ROM & MM gapps.
OR - if you really like the 23c or 24b modem and don't want to use the 35b, you can flash just the 35b modem( http://forum.xda-developers.com/showpost.php?p=56005257&postcount=4) to get past the check, flash the ROM, and then flash whatever modem you prefer. I use the 24b modem/boostack on MM ROMs and it works fine...not sure about 23c.
Click to expand...
Click to collapse
I got it to work with 35b but don't have data? Any sugestions
lazy445 said:
I got it to work with 35b but don't have data? Any sugestions
Click to expand...
Click to collapse
K...that's a bummer. I'm not on cm13 rt now...I'm on candy6(which is very nice BTW) so if there is a ROM issue that is causing the no data - I would have no idea about it. Best to check the CM threads and see if anyone else has the issue. It could be something simple like changing your apns or whatever normally causes data issues...or maybe you just got a bad build.
But if you think it's a radio issue - did you flash the whole 35b bootstack, or just the modem? If just the modem then try flashing the 35b bootstack as well - or just downgrade your modem to 24b.
If you flashed the 35b bootstack and want to downgrade to 24b you'll need to downgrade the entire bootstack and not just the modem because it will probably give you issues. For ex, as an experiment, I just flashed Temasek cm13 with 35b bootstack and have data working (if you want to try that build instead... http://forum.xda-developers.com/ver...aseks-unofficial-build-lollipop-5-01-t2965501 ) & the 24b boostack also worked normally as well. But if I mix bootstacks and modems(35b bootstack with 24b modem, & vice versa) the phone won't boot past the LG splash screen. You can find the 24b bootstack here if you need it(and read post #2 if you want to know more about bootstacks)... http://forum.xda-developers.com/verizon-lg-g3/development/xdabbeb-s-vs980-2-0-0-t3231279
Personally I find the whole bootstack thing annoying and don't see any significant benefit from using the newer modem which is why I stick with using the 24b modem/bootstack, flash the 35b modem to pass the initial check if I need to, and flash the 24b modem and reboot. It just makes life easier when restoring my nandroid backups. But that's just me & to each his own
startswithPendswithOOH said:
You probably need the 35b modem to get past the baseband check. But the 35b modem alone may have some issues if you don't flash the whole bootstack with it. So flash this 35b bootstack 1st( https://www.androidfilehost.com/?fid=24052804347843993 ), then flash the ROM & MM gapps.
OR - if you really like the 23c or 24b modem and don't want to use the 35b, you can flash just the 35b modem( http://forum.xda-developers.com/showpost.php?p=56005257&postcount=4) to get past the check, flash the ROM, and then flash whatever modem you prefer. I use the 24b modem/boostack on MM ROMs and it works fine...not sure about 23c.
Click to expand...
Click to collapse
startswithPendswithOOH said:
K...that's a bummer. I'm not on cm13 rt now...I'm on candy6(which is very nice BTW) so if there is a ROM issue that is causing the no data - I would have no idea about it. Best to check the CM threads and see if anyone else has the issue. It could be something simple like changing your apns or whatever normally causes data issues...or maybe you just got a bad build.
But if you think it's a radio issue - did you flash the whole 35b bootstack, or just the modem? If just the modem then try flashing the 35b bootstack as well - or just downgrade your modem to 24b.
If you flashed the 35b bootstack and want to downgrade to 24b you'll need to downgrade the entire bootstack and not just the modem because it will probably give you issues. For ex, as an experiment, I just flashed Temasek cm13 with 35b bootstack and have data working (if you want to try that build instead... http://forum.xda-developers.com/ver...aseks-unofficial-build-lollipop-5-01-t2965501 ) & the 24b boostack also worked normally as well. But if I mix bootstacks and modems(35b bootstack with 24b modem, & vice versa) the phone won't boot past the LG splash screen. You can find the 24b bootstack here if you need it(and read post #2 if you want to know more about bootstacks)... http://forum.xda-developers.com/verizon-lg-g3/development/xdabbeb-s-vs980-2-0-0-t3231279
Personally I find the whole bootstack thing annoying and don't see any significant benefit from using the newer modem which is why I stick with using the 24b modem/bootstack, flash the 35b modem to pass the initial check if I need to, and flash the 24b modem and reboot. It just makes life easier when restoring my nandroid backups. But that's just me & to each his own
Click to expand...
Click to collapse
Do you think the 24b boot stack will fix data. If so can you link that. Also if you find apn fixed for cm13 lg g3 data
lazy445 said:
Do you think the 24b boot stack will fix data. If so can you link that. Also if you find apn fixed for cm13 lg g3 data
Click to expand...
Click to collapse
It is already linked in the last post...xdabbebs vs985 thread has 35b, 24b, and 12b bootstack links.
And I don't use cm13(too many bugs) so I'm not familiar, but if you Google Verizon APN settings you'll find what you need.
MoparOso said:
I have been dealing with this problem for about three weeks now, and nowhere have I been able to find a workable solution to the problem. I've gone the route of wiping cache, dalvik, system and data, let the phone boot to "No OS" then attempt the flash, but so far I have just wasted time and achieved no viable ends from these various means.
Is there anyone who actually know what the problem is with this? The device is a rooted LG G3 VS985. I'm running TRWP v2.8.6.0. I would really like to get to the root of this problem (slight pun intended) so that I can get back to upgrading my ROMs as BlissRom releases them.
Click to expand...
Click to collapse
I have LG G3 D858HK (D858HK20e-HKG-XX) and I'm having the same problem when trying to flash Android 6.0 ROM to my phone with TWRP Recovery, anyone knows what's this and how to fix it, please HELP!!!
Dear i have the same problem, my cell fone is LG g3 vs985, it was running on stock Rom 4.4.2 kitkat, then i tried to upgrade it, i managed to upgrade it on Fulmics 6.5, i used it fot month, but it seems that its a bit slow, i checked out for other Custom Roms, LineageOS or Ressurection Remix 7.0 are my choices, but unfortunatly, i could not manage to flash them, i had to downgrade my fone to stock using TOT method, then i installed recovery n root it, as it is required to flash a custom ROm but i get error while flashing n now i m Operationg system less plz some one help....
Sent from my HUAWEI ALE-L21 using XDA Labs
---------- Post added at 12:02 PM ---------- Previous post was at 11:59 AM ----------
ASGH93 said:
I have LG G3 D858HK (D858HK20e-HKG-XX) and I'm having the same problem when trying to flash Android 6.0 ROM to my phone with TWRP Recovery, anyone knows what's this and how to fix it, please HELP!!!
Click to expand...
Click to collapse
Dear i think u must try to flash Fulmics.7.0, its the only ROM which i found to flash with no hurdle, try it its also ful of almost extra features
Sent from my HUAWEI ALE-L21 using XDA Labs
Hey there, I just flashed 35b bootstack on lg g3 vs98510B on stock ROM 4.4.2 just check what impact does it put, I dont see any change on system about page, but I see Sim & data go on & of like its creating some problem with sim, rest is working fine. What do u say shud I it a try n flash cm based MM or N&N ROM. Will it work.
Sent from my HUAWEI ALE-L21 using XDA Labs
I am trying to repair my nephews i9300 with imei showing the fake 0049. I have been using smartphones for a decade now and it usually takes about 4hrs to 2days to solve a problem.
The first few things i read were the *#4636#* code which was not working on 4.3, so i flashed 4.0.4 but after flashing i realized it was not for reparing imei so i did not go through with it.
now the problem here is that 1), there is a galore of methods for fixing this 2), i dont wanna do anything too risky and brick the mobile of my nephew.
If it was my own phone i would have been done trying about everything by now but i am still reading around to see the surest and relative fix to my dev/prob.
Btw unlike from what i have read, his Imei got corrupted while he was asleep not flashing any custom roms etc.
Atm i am downloading the XXUGMK6 and will go through with flashing it before i install XXUGMK6 Modem.zip
XXUGMK6 Kernel.zip.
(i could not find the firmware for my country btw currently downloading one with OXA at the end.)
I hope it works out but any clear advise would really be helpful here.
Thanks.
@the boy plunger: I guess, there's no efs-backup.
What modem is actually installed?
rp158 said:
@the boy plunger: I guess, there's no efs-backup.
What modem is actually installed?
Click to expand...
Click to collapse
No backup, im currently flashing xxugmk6, let me get back to you.
.
Baseband is now i9300XXUGMK6. (thats the modem?)
Tried this method
http://www.androidveterans.com/solve-registered-network-galaxy-s3-i9300-issue-restore-imei/
First time with only PDA option, after ODIN was done, it gave me null/null IMEI, after flashing the patched Kernel and modem it went back to 0049. I checked CSC with *1234# and it was UNKNOWN.
Tried again with ODIN with PDA,CSC and Modem this time. After Odin the IMEI was 0049 instead of Null. After patched files flashing nothing chanded. (though CSC shows in *1234# menu).
Used this for flashing in Recovery.
CF-SGS3-CWM-v5.5-v1.2.zip
@the boy plunger: settings…info…baseband views your modem.
MK6 isn't actual, neither build nor modem. So try to update via OTA or KIES. (If they deny, you've to reset counter & status by TriangleAway first.) There's a little chance, that you get your IMEI back during update. Otherwise, let it repair by Samsung-service. All these witchy IMEI-procedures are either outdated or didn't work generally.
rp158 said:
@the boy plunger: settings…info…baseband views your modem.
MK6 isn't actual, neither build nor modem. So try to update via OTA or KIES. (If they deny, you've to reset counter & status by TriangleAway first.) There's a little chance, that you get your IMEI back during update. Otherwise, let it repair by Samsung-service. All these witchy IMEI-procedures are either outdated or didn't work generally.
Click to expand...
Click to collapse
I am at 4.3 currently will it update any further from Kies?
Btw 1 thing, He said he woke up in the morning it was saying "NOT REGISTERED ON NETWORK". He dint do any flashing or anything.
I think phone was working with the fake IMEI (0049) for more than a year and just stopped working when casue conflict between Wifi and Network radios etc.
What if i goo back to 404 and try the *#4636#* or similer methods?
Going back to 4.0 is worthless. IF there ever was a valid IMEI/efs-package, you messed it up in the meantime.
Either update-procedure repairs or service-center or going on without telephone-functions.
What about these methods?
http://www.sammobile.com/forum/showthread.php?t=15196
@the boy plunger: these are the witchy things. I only read about and didn't try, so go your way.
Maybe, the patched modem helps.
Everytime i upgrade to an international marshmallow rom i lose 4g signal and becuz of it i get "cell stanby" draining my battery heavily. I tried flashing all the basebands and bootstacks even backedup my efs from an older rom or marshmallow rom on verizon becuz my data works perfect on verizon roms. The right apns looks to be in tact. I just really want this to work becuz this is the lg g5 rom im on. (Fulmics 5.0) i can also still text and call. Just no 4g and bars.
MonstaSaleens said:
Everytime i upgrade to an international marshmallow rom i lose 4g signal and becuz of it i get "cell stanby" draining my battery heavily. I tried flashing all the basebands and bootstacks even backedup my efs from an older rom or marshmallow rom on verizon becuz my data works perfect on verizon roms. The right apns looks to be in tact. I just really want this to work becuz this is the lg g5 rom im on. (Fulmics 5.0) i can also still text and call. Just no 4g and bars.
Click to expand...
Click to collapse
If it's not specifically for the VS985, I wouldn't flash it. You'll have to either fully TOT or KDZ flash it back to fix all your partitions just to be on the safe side.
You should never flash a non-VS985 ROM on the VS985. If you do, you're taking a risk to brick it.
If this was for the VS985, then my apologies, but you didn't specify which ROM it was and I'm assuming since you're postin ghere in the Verizon G3 forums, you have the VS985 G3 and not some other variety.
iBolski said:
If it's not specifically for the VS985, I wouldn't flash it. You'll have to either fully TOT or KDZ flash it back to fix all your partitions just to be on the safe side.
You should never flash a non-VS985 ROM on the VS985. If you do, you're taking a risk to brick it.
If this was for the VS985, then my apologies, but you didn't specify which ROM it was and I'm assuming since you're postin ghere in the Verizon G3 forums, you have the VS985 G3 and not some other variety.
Click to expand...
Click to collapse
Yes it is for verizon, its fulmicsROM 5.0 i chose vs985 in aroma. Other verizon users are saying thier data works without even touching apns. Mine worked in the bigginning but after a couple hours it just did what it did in the pics and havnt worked since.
MonstaSaleens said:
Yes it is for verizon, its fulmicsROM 5.0 i chose vs985 in aroma. Other verizon users are saying thier data works without even touching apns. Mine worked in the bigginning but after a couple hours it just did what it did in the pics and havnt worked since.
Click to expand...
Click to collapse
When you flashed this ROM, what boot partition to you flash from? I did find one in the generic G3 Development forum so I'm assuming the following link is where you probably found it:
http://forum.xda-developers.com/lg-g3/development/rom-fulmics-rom-1-0-tweaks-ota-v20u-t3232340
You might have flashed it with the wrong boot and modem partition. I believe 12B is the last one that works with the current version of TWRP that is bumped for the VS985. Anything above that will not work as they haven't released a new bumped TWRP for the more recent OTAs.
I would find one of the revert back to stock threads, flash it back to a version such as 10B (via TOT or KDZ) and see if your LTE signal comes back. If so, then you should be able to root from there, flash TWRP and then hopefully flash the fulmicsROM at that point and it should hopefully work. If it doesn't work on 10B, then it sounds like your LTE antenna may be going bad.
Otherwise, I'm not sure what is going on.
Hope that helps!
I have same problem. Seems vs985 is updated to 47a witch there is no bumped boot loader for 47a. That may be our problem.
Sent from my VS985 4G using XDA-Developers mobile app
iBolski said:
When you flashed this ROM, what boot partition to you flash from? I did find one in the generic G3 Development forum so I'm assuming the following link is where you probably found it:
http://forum.xda-developers.com/lg-g3/development/rom-fulmics-rom-1-0-tweaks-ota-v20u-t3232340
You might have flashed it with the wrong boot and modem partition. I believe 12B is the last one that works with the current version of TWRP that is bumped for the VS985. Anything above that will not work as they haven't released a new bumped TWRP for the more recent OTAs.
I would find one of the revert back to stock threads, flash it back to a version such as 10B (via TOT or KDZ) and see if your LTE signal comes back. If so, then you should be able to root from there, flash TWRP and then hopefully flash the fulmicsROM at that point and it should hopefully work. If it doesn't work on 10B, then it sounds like your LTE antenna may be going bad.
Otherwise, I'm not sure what is going on.
Hope that helps!
Click to expand...
Click to collapse
Theres nothing wrong with my data when i flash any verizon rom. So when i go back to it it works perfectly. But when i go to any marshmallow rom for multiple variants my data seems it cant connect. Ive tried the kdz method like 3 times and flashed from there but it didnt work. Im not sure about what you mean by what boot partition i flashed from
MonstaSaleens said:
Theres nothing wrong with my data when i flash any verizon rom. So when i go back to it it works perfectly. But when i go to any marshmallow rom for multiple variants my data seems it cant connect. Ive tried the kdz method like 3 times and flashed from there but it didnt work. Im not sure about what you mean by what boot partition i flashed from
Click to expand...
Click to collapse
Depending on the version of Android you used KDZ'd from, that determines what your modem and boot partition are set up as. In order to flash any Marshmallow ROM, you cannot be on the current 72A boot and modem partitions. They do not work with TWRP for the G3. So based on what you've told me, where your LTE signal is fine on stock, that to me suggests one of two things:
You're flashing the custom ROM with an incorrect modem and/or boot partition (later than 10B)
The ROM itself is bad
So, you have to KDZ or TOT back to 10b and flash your ROM from there. I'm assuming that's what you've done, but I wanted to make sure.
The directions in that thread do not give the specifics for the VS985 version.
Here are directions on downgrading to 10B properly so that you can flash custom ROMs properly:
http://forum.xda-developers.com/verizon-lg-g3/general/lg-g3-downgrade-to-10b-t3354834
Here's another thread on doing the same:
http://forum.xda-developers.com/verizon-lg-g3/general/lg-g3-downgrade-to-10b-t3354834
@iBolski From what I read in the Fulmics v5.0 thread, the 12B bootstack is the one that's necessary to have data working on Verizon (for most people). The OP said he tried all the bootstacks though so no idea there.
roirraW "edor" ehT said:
@iBolski From what I read in the Fulmics v5.0 thread, the 12B bootstack is the one that's necessary to have data working on Verizon (for most people). The OP said he tried all the bootstacks though so no idea there.
Click to expand...
Click to collapse
@roirraW "edor" ehT Thanks! I must have missed that somewhere in the thread.
@MonstaSaleens, there's your answer. Make sure you TOT or KDZ back to 12B (I would flash the entire thing). @roirraW "edor" ehT has links in his sig that can point you to all the correct images and instructions you need. The first two links in his sig are what you want.
iBolski said:
@roirraW "edor" ehT Thanks! I must have missed that somewhere in the thread.
@MonstaSaleens, there's your answer. Make sure you TOT or KDZ back to 12B (I would flash the entire thing). @roirraW "edor" ehT has links in his sig that can point you to all the correct images and instructions you need. The first two links in his sig are what you want.
Click to expand...
Click to collapse
Ive done this multiple times before. I even formated internal storage. Went bakc down to 12b used stump root to root and still no data on fulmics. Ive been had problems with the data on roms that are for all varients and are marshmallow. It just doesnt like my phone. But hey, data is doing the same thing on my brothers g3 when he flashed this rom cuz he wanted the new g5 ui too.
roirraW "edor" ehT said:
@iBolski From what I read in the Fulmics v5.0 thread, the 12B bootstack is the one that's necessary to have data working on Verizon (for most people). The OP said he tried all the bootstacks though so no idea there.
Click to expand...
Click to collapse
Do we have any flashable marshmallow radios yet?
MonstaSaleens said:
Do we have any flashable marshmallow radios yet?
Click to expand...
Click to collapse
Short answer: No.
There's technical reasons why we can't use the 46A and 47A modems, at least if you want to be able to use TWRP. There's nothing to stop you from flashing the modem extracted out of the 47A KDZ, but you won't have a signal or data with the modem alone. The 46A and 47A modem require the 46A or 47A sbl1 partition.
Putting the 46A or 47A sbl1 on the phone when you already have working TWRP will cause a QHSUSB_BULK 9008 mode brick because those sbl1 really don't like the 12B (or older) bootloader, and the 12B (or 11C or 10B) bootloader is required to get into TWRP.
So...you can have either:
1. TWRP along with the 12B bootloader, but only up to 35B sbl1 and modem.
Or
2. The Marshmallow bootloader, sbl1 and modem.
I haven't tried or tested getting rid of TWRP and re-upgrading the bootloader, sbl1 and modem, but that should in theory work, at least on stock 46A and 47A ROMs - don't know about international or CM13 ROMs.