Related
Hi all,
Long time lurker of XDA and Android user/modder since before Gingerbread. I want to apologize in advance if this post is either in the wrong section, and/or if something similar has already been answered/solved in another thread. I did multiple searches with nothing coming up as a direct hit, or even close for that matter.
I recently purchased an S4 from VZW (Mid-Late July). I rooted and installed TWRP 5.2.0.2 (Forgive me if that's not the exact version...) and flashed AOSP ROMs here and there. After a month or so, I started coming across an issue within all ROMs where I couldn't receive or make calls without my phone either freezing or rebooting. Anything I flashed, or modded, failed to remedy this. I tried different GApps packages, 4.2.2 and 4.3 ROMs, different kernels, and both radios, and absolutely NOTHING solved this. I searched everywhere (Even rootzwiki, forgive me fellow XDA members!), and could not find anyone with the same issue.
I attempted upgrading to TWRP 2.6.0.0 and even tried CWM, and that didn't help either. Eventually, things got so bad that I couldn't boot into ANY ROM, 4.2.2 or 4.3. After nearly 10 hours of trying to unbrick my phone, I finally managed to install Beanstalk 4.3, and while it was working incredibly buggy (Not Beanstalk's fault, the developer is a great developer!) nor could I make calls, I could still send texts and emails. I was able to FINALLY get the Odin3 application to work when I got home from work, and was able to flash the stock MDK image. From there I followed the steps to properly root and install TWRP 2.6.0.0. I installed Slim's Beta 5 4.3 ROM and GApps and everything was working properly! Calling, everything! However, when I made a reboot, it froze. Stuck in the "Samsung Unlocked" screen for over an hour. I pulled the battery, booted into recovery and did a factory reset/cache and dalvik wipe. It still didn't boot. From there I did a full wipe, and data format, installed Beanstalks newest 4.3 ROM and GApps, and everything loaded properly. Then I couldn't make or receive calls without the same issue. I then did the superwipe/format and installed PAC's newest nightly and GApps package, and was able to make calls, but then got stuck when rebooting, even after factory resets and cache/dalvik wipes. After multiple attempts, I gave up and reflashed the stock MDK Samsung image in Odin3 and am leaving it as is until someone here can help me.
I know this post was incredibly wordy, and I apologize for that, but I wanted to give you guys as much information as possible and explain where this all started, as it may lead to why I'm having these problems. I appreciate any and all responses and I will answer any question any of you have to the best of my ability. Please someone save me from the horror that is TouchWiz!
-Travis
First, make a NANDROID if it is working perfect on the stock ROM. This is my first step after root and recovery so that I can always fall back on something to check if there is a hardware problem, or just some sort of (system) file problem. Plus, it'll save you time if you have to go back.
Not sure that it matters, but is the stock ROM odexed, or deodexed?
The calling thing reminds me of when you use the phone overseas but it has yet to be unlocked. When you root, do you check with Root Checker? Do you have SuperSU installed? How about BusyBox? I know some items require BusyBox in order to work, but SuperSU should be installed.
As far as SuperSU, do you update it before switching back to the original kernel? One thing I noted is to be absolutely sure you do so in order to not lose your root when completing the rooting steps. I imagine this could cause other problems too.
I also suggest not using TWRP 2.6, which many people will tell you is quite buggy. Best to use the previous version.
The only other things I can suggest is ALWAYS doing a full wipe of everything before adding a new ROM. I used to do this to be sure I incurred no problems on my SGS3, because if I didn't there would always be something buggy happening.
Hope this helps.
Heatshiver said:
First, make a NANDROID if it is working perfect on the stock ROM. This is my first step after root and recovery so that I can always fall back on something to check if there is a hardware problem, or just some sort of (system) file problem. Plus, it'll save you time if you have to go back.
Not sure that it matters, but is the stock ROM odexed, or deodexed?
The calling thing reminds me of when you use the phone overseas but it has yet to be unlocked. When you root, do you check with Root Checker? Do you have SuperSU installed? How about BusyBox? I know some items require BusyBox in order to work, but SuperSU should be installed.
As far as SuperSU, do you update it before switching back to the original kernel? One thing I noted is to be absolutely sure you do so in order to not lose your root when completing the rooting steps. I imagine this could cause other problems too.
I also suggest not using TWRP 2.6, which many people will tell you is quite buggy. Best to use the previous version.
The only other things I can suggest is ALWAYS doing a full wipe of everything before adding a new ROM. I used to do this to be sure I incurred no problems on my SGS3, because if I didn't there would always be something buggy happening.
Hope this helps.
Click to expand...
Click to collapse
Thank you, Heatshiver!
I always do a full wipe unless I'm doing a dirty flash for a ROM update. I will try reverting back to TWRP 2.5.0.2 (Whichever version that happens to be, I think it's .0.2) tonight and report my results. Also, just to clarify, I always make sure I have the most updated SuperSU/Superuser (Usually the former) and BusyBox.
I appreciate the suggestion.
-Travis
teemunknee said:
Hi all,
Long time lurker of XDA and Android user/modder since before Gingerbread. I want to apologize in advance if this post is either in the wrong section, and/or if something similar has already been answered/solved in another thread. I did multiple searches with nothing coming up as a direct hit, or even close for that matter.
I recently purchased an S4 from VZW (Mid-Late July). I rooted and installed TWRP 5.2.0.2 (Forgive me if that's not the exact version...) and flashed AOSP ROMs here and there. After a month or so, I started coming across an issue within all ROMs where I couldn't receive or make calls without my phone either freezing or rebooting. Anything I flashed, or modded, failed to remedy this. I tried different GApps packages, 4.2.2 and 4.3 ROMs, different kernels, and both radios, and absolutely NOTHING solved this. I searched everywhere (Even rootzwiki, forgive me fellow XDA members!), and could not find anyone with the same issue.
I attempted upgrading to TWRP 2.6.0.0 and even tried CWM, and that didn't help either. Eventually, things got so bad that I couldn't boot into ANY ROM, 4.2.2 or 4.3. After nearly 10 hours of trying to unbrick my phone, I finally managed to install Beanstalk 4.3, and while it was working incredibly buggy (Not Beanstalk's fault, the developer is a great developer!) nor could I make calls, I could still send texts and emails. I was able to FINALLY get the Odin3 application to work when I got home from work, and was able to flash the stock MDK image. From there I followed the steps to properly root and install TWRP 2.6.0.0. I installed Slim's Beta 5 4.3 ROM and GApps and everything was working properly! Calling, everything! However, when I made a reboot, it froze. Stuck in the "Samsung Unlocked" screen for over an hour. I pulled the battery, booted into recovery and did a factory reset/cache and dalvik wipe. It still didn't boot. From there I did a full wipe, and data format, installed Beanstalks newest 4.3 ROM and GApps, and everything loaded properly. Then I couldn't make or receive calls without the same issue. I then did the superwipe/format and installed PAC's newest nightly and GApps package, and was able to make calls, but then got stuck when rebooting, even after factory resets and cache/dalvik wipes. After multiple attempts, I gave up and reflashed the stock MDK Samsung image in Odin3 and am leaving it as is until someone here can help me.
I know this post was incredibly wordy, and I apologize for that, but I wanted to give you guys as much information as possible and explain where this all started, as it may lead to why I'm having these problems. I appreciate any and all responses and I will answer any question any of you have to the best of my ability. Please someone save me from the horror that is TouchWiz!
-Travis
Click to expand...
Click to collapse
sorry for your troubles, but I am always baffled the way people just toss that word "brick" round
Your phone was no anywhere NEAR being a brick...
You simply are playing with fire flashing AOSP ROMs and not knowing how to fix the issues.
AOSP ROMs aren't technically "made" for our phones, the developers do a great job at making it seem like they are, though.
On the SG3 we had an EFS backup that Synergy discovered incase you flash an AOSP and get stuck in roaming which was quite often at first with AOSP, that was easy to fix, but with this phone I would be careful with AOSP ROMs, even myself, with a locked bootloader wouldn't flash anything besides TW, although I am biased as AOSP is my flavor.
I am sorry if this post comes off harsh or any other bad word. It's not meant for that..
Just to kindly ask you to do some research on what a "bricked phone" truly is.
it's a brick.. meaning won't power on, won't get a light when charging, nothing, your phone is just that, a $600 brick. and the only way to bring back to life IIRC is Jtagging the phone.. which requires taking the phone apart and jtagging the motherboard.
I hope you the best my friend.
As much as I love AOSP, I would have to agree with the poster above. I know TW is a pain but there are some pretty good ROMs in that flavor that you shouldn't have any problems with. I've had the no call issue on AOSP, and even though they are nice and free up quite a bit of room it's not worth missing calls over or constantly flashing. Maybe once our bootloader is unlocked things will become different but I'd stick with TW until that happens. I can confirm that TWRP 2.6 is very buggy...you'll have to download the 2.5 version and flash it instead of goomanager they install they latest version everytime I believe.
andybones said:
sorry for your troubles, but I am always baffled the way people just toss that word "brick" round
Your phone was no anywhere NEAR being a brick...
You simply are playing with fire flashing AOSP ROMs and not knowing how to fix the issues.
AOSP ROMs aren't technically "made" for our phones, the developers do a great job at making it seem like they are, though.
On the SG3 we had an EFS backup that Synergy discovered incase you flash an AOSP and get stuck in roaming which was quite often at first with AOSP, that was easy to fix, but with this phone I would be careful with AOSP ROMs, even myself, with a locked bootloader wouldn't flash anything besides TW, although I am biased as AOSP is my flavor.
I am sorry if this post comes off harsh or any other bad word. It's not meant for that..
Just to kindly ask you to do some research on what a "bricked phone" truly is.
it's a brick.. meaning won't power on, won't get a light when charging, nothing, your phone is just that, a $600 brick. and the only way to bring back to life IIRC is Jtagging the phone.. which requires taking the phone apart and jtagging the motherboard.
I hope you the best my friend.
Click to expand...
Click to collapse
Next time, I'll just say "Soft-bricked". Thank you for your reply.
-Travis
You also may want to try CWM recovery if everything else fails. I like TWRP but I kept having the exact problem you have. I switched and haven't had a problem since.
Sent from my SCH-I545
slim6596 said:
You also may want to try CWM recovery if everything else fails. I like TWRP but I kept having the exact problem you have. I switched and haven't had a problem since.
Sent from my SCH-I545
Click to expand...
Click to collapse
Would you mind telling me which version of CWM you're using? I haven't gone back to CWM since I went back to stock two nights ago.
Thank you for the idea!
-Travis
I also forgot to mention that I haven't been able to connect to 4G radios since before I started having issues with AOSP ROMs. Currently I'm on Eclipse's TW (With AOSP Styling) ROM. Everything appears to be working fine, other than 4G.
I've tried the SIM pull and reset, and nothing. I've tried manually setting it to LTE only, at least when I was able to do so when AOSP ROMs would boot for me, and nothing. I have a Galaxy Nexus that I booted up with this SIM in and I get 4G signal. Any Ideas?
Also, when I was on the stock image (MDK) I didn't have 4G either.
Has anyone else run across this issue? (MODS: Let a me know if I should create another thread, or search more intensively. I haven't seen a thread with this exact same situation. Plenty of 4G issue threads, but none with the same issues I've previously had, and I think it may have something to do with my past modding.)
-Travis
teemunknee said:
Would you mind telling me which version of CWM you're using? I haven't gone back to CWM since I went back to stock two nights ago.
Thank you for the idea!
-Travis
Click to expand...
Click to collapse
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
slim6596 said:
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
Click to expand...
Click to collapse
Thanks! I installed CWM 6.0.3.6 Touch and flashed Eclipse's TW/AOSP ROM and everything works well, but it's still no AOSP ROM.
-Travis
Hi all,
I'd like to thank everyone for the suggestions.
An update: Currently I'm on Eclipse's TW v2.0 ROM (TW, with AOSP Styling) and everything works properly. My current recovery is CWM 6.0.3.6 Touch, and I'm not experiencing any booting or calling issues. 4G is the only thing I don't have working.
I'm hoping that someone with my same problem can give me another idea so I can get an AOSP ROM working, preferably with 4G. I'm sure some, if not most, understand my dislike of TouchWiz and strong preference towards stock Android/stock Android based ROMs. Slim6596 said that he uses Philz Modded CWM Recovery and has no issues anymore. Could that really be my solution?
Again, thank you all for your help and ideas. I love XDA for this reason.
-Travis
slim6596 said:
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
Click to expand...
Click to collapse
Hi Slim,
Sorry to bother, but I was curious if you were specifically using the LOKI patched version, or just the regular version?
-Travis
teemunknee said:
Hi Slim,
Sorry to bother, but I was curious if you were specifically using the LOKI patched version, or just the regular version?
-Travis
Click to expand...
Click to collapse
Loki patched, I believe.
Sent from my SCH-I545
slim6596 said:
Loki patched, I believe.
Sent from my SCH-I545
Click to expand...
Click to collapse
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
teemunknee said:
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
Click to expand...
Click to collapse
I have stuck to TW ROMs. Pretty soon I'm probably not going to be flashing anything. Switching to Motorola and giving Vz my MDK S4 back. (Reception and dropped call issues.)
Sent from my SCH-I545 using Tapatalk 2
teemunknee said:
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
Click to expand...
Click to collapse
I believe you have to do the extended phone function. Its a code on the dial pad and select cdma. I have read this but don't recall where.
Sent from my SCH-I545 using Tapatalk 4
egore93 said:
I believe you have to do the extended phone function. Its a code on the dial pad and select cdma. I have read this but don't recall where.
Sent from my SCH-I545 using Tapatalk 4
Click to expand...
Click to collapse
Are you referring to the *#*#4636#*#* dialer code? I didn't even try that because in my settings, everything was set to CDMA, but that's something I can try. I have everything backed up, so I can just wipe, install, and try that. If it doesn't work, I can always revert back.
Thanks for the suggestion!
-Travis
teemunknee said:
Are you referring to the *#*#4636#*#* dialer code? I didn't even try that because in my settings, everything was set to CDMA, but that's something I can try. I have everything backed up, so I can just wipe, install, and try that. If it doesn't work, I can always revert back.
Thanks for the suggestion!
-Travis
Click to expand...
Click to collapse
Yes that's it give it a go.
Sent from my SCH-I545 using Tapatalk 4
Hello,
As per the thread title, I would appreciate someone sending me a copy of an IMEI-removed NV items backup from a Note 2 N7105. (Ideally both .qcn and text formats.)
Long story short I'm spending a month somewhere where LTE is on bands 3, 7 and 20 instead of my usual 4, 7 and 17. So, maybe (just a teeny tiny maybe, mind you) there's the possibility that feeding my franken-Note 2 (see the T889V LTE guide) some N7105 NV items would make it work on LTE here instead of just DC-HSPA. I'm thinking along the lines of the AWS mod.
And, along this strenuous path of uncertainties, I just might have the time to give this a shot. Of course, I do have an acceptable backup device on hand or I wouldn't be trying this.
Posting the files here could also help others who have had issues that can be solved by flashing NV items again.
(If you have the files but are unsure how to anonymize them, you could always send them privately if you don't mind me seeing your IMEI.)
Please specify the modem in use at the time the backup was taken, just in case.
Thanks in advance,
Darkshado
XDA:DevDB Information
N7105 NV items backup, Device Specific App for the Samsung Galaxy Note II
Contributors
Darkshado
Version Information
Status: Testing
Created 2015-08-22
Last Updated 2015-08-22
Darkshado said:
Hello,
As per the thread title, I would appreciate someone sending me a copy of an IMEI-removed NV items backup from a Note 2 N7105. (Ideally both .qcn and text formats.)
Long story short I'm spending a month somewhere where LTE is on bands 3, 7 and 20 instead of my usual 4, 7 and 17. So, maybe (just a teeny tiny maybe, mind you) there's the possibility that feeding my franken-Note 2 (see the T889V LTE guide) some N7105 NV items would make it work on LTE here instead of just DC-HSPA. I'm thinking along the lines of the AWS mod.
And, along this strenuous path of uncertainties, I just might have the time to give this a shot. Of course, I do have an acceptable backup device on hand or I wouldn't be trying this.
Posting the files here could also help others who have had issues that can be solved by flashing NV items again.
(If you have the files but are unsure how to anonymize them, you could always send them privately if you don't mind me seeing your IMEI.)
Please specify the modem in use at the time the backup was taken, just in case.
Thanks in advance,
Darkshado
Click to expand...
Click to collapse
Hi Darkshado,
Did you happen to get your hands on a backup? If yes, would you be kind enough to share it here. My GPS has stopped working and I think I need a copy of the NV data backup.
Thanks in advance.
Unfortunately no, good luck with your GPS.
Ah okay. Thanks for your reply.
sidxda said:
Ah okay. Thanks for your reply.
Click to expand...
Click to collapse
have you re-partitioned by chance?
bootloader 4.3?
did you ever flash 2014-05-01 Nordic countries 4.4.2 N7105XXUFND3 by chance?
random questions I know. just trying to pinpoint / eliminate issues I have along the timeline of events.
Hi Rob,
I just replied to your PM. But yes I did try flashing with a PIT file. I am on 4.3 bootloader. I've flashed custom Nordic ROMs, not stock from sammobile.
I believe something happened to the GPS when I flashed mr.nth.na.vn's RR CM12.1
At the moment it seems GPS is not working on any other ROM except mr.nth.na.vn's RR CM12.1
R0B3RTF1SH3R said:
have you re-partitioned by chance?
bootloader 4.3?
did you ever flash 2014-05-01 Nordic countries 4.4.2 N7105XXUFND3 by chance?
random questions I know. just trying to pinpoint / eliminate issues I have along the timeline of events.
Click to expand...
Click to collapse
sidxda said:
Hi Rob,
I just replied to your PM. But yes I did try flashing with a PIT file. I am on 4.3 bootloader. I've flashed custom Nordic ROMs, not stock from sammobile.
I believe something happened to the GPS when I flashed mr.nth.na.vn's RR CM12.1
At the moment it seems GPS is not working on any other ROM except mr.nth.na.vn's RR CM12.1
Click to expand...
Click to collapse
I am in the same situation with u. Did all that u mentioned. Actually for some reason all the 5.1.1 Rom works for me.
---== N7105 ==---
yeah , i figured it would be something along those lines.
mine was borked well and before any of remix. i use daily in my sig and have done for a long time, and now im testing out RR, different cook but yeah. its not remix cm11 or 12. that borked gps.
After talking with you in pm, I have a new theory.
that is;
we probably need to go back and flash a 4.1.2 or what ever your phone was shipped with.
because i have a feeling that any thing later 4.3 / 4.4 all the tw roms. never did anything to the gps anyway. so its remained the same since factory release.
along the way it got broken during bootloader or specific rom flash's that tried to take into account peoples GPS problems. which was a bandaid on a gaping wound..
and the ones that did work, probably picked up on some specifics that would still work with modified gps data... ?
what u think?
Correct me if I'm wrong, but we cannot downgrade the bootloader, can we?
I really have no clue what changed and broke the GPS, but I'm just glad GPS is working again, and RR CM12.1 is good enough as a daily driver with ShiftLP kernel.
@leanhtai was kind enough to provide the backup file of his N7105's NV data. I will give it a go again when I get a bit more time. I have spent a ridiculous amount of time just trying to get GPS working, I will give it a go over the weekend.
Here is the link if any of you want to try it out.
https://drive.google.com/file/d/0ByCI3hH8BBJyX0xlM1hJbl9rZlU/view
I believe you will need to use this method - http://forum.xda-developers.com/gal...warning-guide-backup-restore-imei-nv-t1946915
Good luck and please be sure to report what you find. I hope we can figure this out once and for all.
kohmax said:
I am in the same situation with u. Did all that u mentioned. Actually for some reason all the 5.1.1 Rom works for me.
---== N7105 ==---
Click to expand...
Click to collapse
R0B3RTF1SH3R said:
yeah , i figured it would be something along those lines.
mine was borked well and before any of remix. i use daily in my sig and have done for a long time, and now im testing out RR, different cook but yeah. its not remix cm11 or 12. that borked gps.
After talking with you in pm, I have a new theory.
that is;
we probably need to go back and flash a 4.1.2 or what ever your phone was shipped with.
because i have a feeling that any thing later 4.3 / 4.4 all the tw roms. never did anything to the gps anyway. so its remained the same since factory release.
along the way it got broken during bootloader or specific rom flash's that tried to take into account peoples GPS problems. which was a bandaid on a gaping wound..
and the ones that did work, probably picked up on some specifics that would still work with modified gps data... ?
what u think?
Click to expand...
Click to collapse
Progress
Okay so I flashed Jedi X20 (4.1.2), GPS didn't work as expected. Then I restored the NV Data from leanhtai's back. GPS locked on straight away in 9 seconds with 3 meters of accuracy! So that's great and thanks leanhtai for your files. But another problem has come up now, my 4G has stopped working and I'm stuck on Edge (E). I guess I need the NV data from someone in Australia for the 4G to work?
sidxda said:
Okay so I flashed Jedi X20 (4.1.2), GPS didn't work as expected. Then I restored the NV Data from leanhtai's back. GPS locked on straight away in 9 seconds with 3 meters of accuracy! So that's great and thanks leanhtai for your files. But another problem has come up now, my 4G has stopped working and I'm stuck on Edge (E). I guess I need the NV data from someone in Australia for the 4G to work?
Click to expand...
Click to collapse
[emoji29] any idea which part of the world is leanhtai in?
kohmax said:
[emoji29] any idea which part of the world is leanhtai in?
Click to expand...
Click to collapse
He lives in Vietnam. So currently I can only use Edge on my Note 2 but GPS is working perfectly. I don't understand why someone with an Australian Note 2 can't just provide us with a copy of their backed up QCN file. It would solve all the issues.
Silly suggestion: buy an used Note 2, pull the data, resell.
Also, converted thread into a "project" so we don't have an auto split Q&A thread.
sidxda said:
He lives in Vietnam. So currently I can only use Edge on my Note 2 but GPS is working perfectly. I don't understand why someone with an Australian Note 2 can't just provide us with a copy of their backed up QCN file. It would solve all the issues.
Click to expand...
Click to collapse
Guess the vn baseband is not compatible with yours...
---== N7105 ==---
Cant you just get your LTE back some other way.
tried the USSD codes?
Rob, I've tried a lot of other things but it seems NV data is independent of everything else. Flashing stock ROMs etc does nothing. I tried the USSD codes as well but I just lose signal completely. Given that you are in NZ, any chance I could try restore your NV Data onto my phone?
Thanks,
Sid
R0B3RTF1SH3R said:
Cant you just get your LTE back some other way.
tried the USSD codes?
Click to expand...
Click to collapse
sidxda said:
Rob, I've tried a lot of other things but it seems NV data is independent of everything else. Flashing stock ROMs etc does nothing. I tried the USSD codes as well but I just lose signal completely. Given that you are in NZ, any chance I could try restore your NV Data onto my phone?
Thanks,
Sid
Click to expand...
Click to collapse
if your NV data is the same data that is related to broken GPS. then im afraid i have broken GPS also.
on device only. it takes up to 3 minutes to lock. even then. its probably just a google network or something TAG sync because its a grey and not a blue dot in maps.
I have an old backup of the phone i made ages ago but even that would not suffice. its seperate.
how do I know if its do-able ?
Yeah had a feeling it wont fix anything. I have some more bad news, I made a stupid move and flashed this on recommendation of someone else on this forum - http://galaxynote2root.com/galaxy-n...3g4g-aws-bands-on-att-galaxy-note-2-sgh-i317/
now my phone's SPC has somehow changed and I have no idea what it is or how to get it. I have tried all the conventional ways after reading for hours on the net but they are all for Sprint/ATT Note 2 and none of them will get me my SPC.
So I'm pretty much stuck now. Can't restore any other QCN backups or anything till I enter the right SPC in QPST
R0B3RTF1SH3R said:
if your NV data is the same data that is related to broken GPS. then im afraid i have broken GPS also.
on device only. it takes up to 3 minutes to lock. even then. its probably just a google network or something TAG sync because its a grey and not a blue dot in maps.
I have an old backup of the phone i made ages ago but even that would not suffice. its seperate.
how do I know if its do-able ?
Click to expand...
Click to collapse
sidxda said:
Yeah had a feeling it wont fix anything. I have some more bad news, I made a stupid move and flashed this on recommendation of someone else on this forum - http://galaxynote2root.com/galaxy-n...3g4g-aws-bands-on-att-galaxy-note-2-sgh-i317/
now my phone's SPC has somehow changed and I have no idea what it is or how to get it. I have tried all the conventional ways after reading for hours on the net but they are all for Sprint/ATT Note 2 and none of them will get me my SPC.
So I'm pretty much stuck now. Can't restore any other QCN backups or anything till I enter the right SPC in QPST
Click to expand...
Click to collapse
what do you need?
Actually I lost my EFS partition couple months ago. I was upgrading bootloader and modem to latest versions and after that i lost my IMEI, MACadresses and other things. I did EFS backup, but that time i didn't know it's not possible to make a valid EFS backup on N7105.
After 6days of fighting with EFS partition on my N7105 (i tried every possible solution), I discovered, that on Exynos devices there are 3 EFS partitions. One is used as normal /efs mount. Second is used as a migration temp during Samsung OTA update and third is something called gold backup. On this third hidden partition there is an original EFS partition from original stock rom. I tried making image of this partition and restoring it on /efs, but it didn't work. Then i read somewhere, that efs partition are in mulitple formats depending on rom version (actually modem version to be specific). So I did one thing i didn't tried during these 6 long days - i flashed ROM I had on my phone originally (it was some early JB release from my operator -tried 2 or 3 of them, cause i didn't remember what version it was).
I flashed original ROM using Odin with enabled options AutoReboot, Re-Partition, F. Reset Time and Phone EFS Clear. When phone booted up and i saw 3G icon - i almost jizzed my pants ;P
Finally I slowly upgraded my phone through couple versions of JB and 2 versions of KK to be completely sure that my EFS partition has migrated successfully to the newest version of modem (XXUFNI2).
I think this is important solution, which can help a lot of people with Exynos-based Note2 problems.
Hello all,
My partner bought a Galaxy S3 (GT-i1900) International (I live in the UK) off a friend .
We noticed that the network connection periodically failed. I noticed that the software was some of the earliest on this phone, and so i thought I'd better update it, as it was suggested that sometimes if the phone is running some of it's earliest software it can cause problems with the network connection, and as it works 95% of the time, surely it can't be the antenna? I went to software update and tried to update it there, it's then I realised the phone had been rooted, and even Kies would not update it. I came to the conclusion that perhaps my friend had tried to mess with the phone some how, and may have caused this network problem, or perhaps was trying to cure it? Who knows
I decided to flash the latest stock rom (i9300XXUGMK6_I9300OXAGMK6_I9300XXUGMK6_HOME.tar.md5) I found on Sammobile. Everything went well, the phone booted up perfectly, the only minor worry being that the first screen was in Polish, quickly remedied by changing the language to English UK. All seemed fine, until we tried to make a call. it was then we realised that there was no network connection whatsoever. I tried other sim cards with other networks - still no connection. It only shows the signal bars.
I read the forums for a couple of days and tried:
Going in Network Settings and searching for my network, 3, which it found amongst all others. it said 'Registered on Network' but then immediately flashed up '3 network not connected' or similar. fail.
Installing CWM recovery, then flashing the 2 modem zips (DDEMG2 & XXDME4) all went fine, but the phone still says 'disconnected' under Device settings Mobile network state
Using the Ariza patch. I tried this, but on the last step where it says 'just click patch' mine gets stuck on a downloading state, possibly as I'm using a stock rom I read some kernel has to be changed first? - Beyond me.
It was then I decided to scrutinize every difference between my working S3, exactly same phone on same network, and my partners.
The IMEI number was correct, something I see people have problems with. The signal strength reading are the same, suggesting the antenna at least is fine.
The serial number - Now this is the ONLY thing I can see that seems to have been changed, from the correct format, to one starting with 4df1 ...... Is this the problem, that has made the phone not register with network? In the UK phones are not locked into a specific phone number /contract and so I don't see how the network would decline a differing serial number?
Anyway that's where I'm at a phone that has no network connection, with a differing serial number.
Any help would be GREATLY appreciated.
extra[/ATTACH]
Screenshots of the device status in case that helps . SCREENSHOTS REMOVED DUE TO PRIVATE INFO
I've noticed after Googling the baseband version, it says 'New modem DDEMG2 (16/07/13) India,Sri Lanka,Bangladesh'
I live in the UK and have a network free unlocked unbranded International S3!
Surely the steps I followed to flash the modems as stated above are incorrect?!
Do I need to flash the UK one?
Anyone know which one for 4.3?
How do I do it and where would I find it?
Any help greatly appreciated!
ricrea said:
extra[/ATTACH]
Screenshots of the device status in case that helps .
I've noticed after Googling the baseband version, it says 'New modem DDEMG2 (16/07/13) India,Sri Lanka,Bangladesh'
I live in the UK and have a network free unlocked unbranded International S3!
Surely the steps I followed to flash the modems as stated above are incorrect?!
Do I need to flash the UK one?
Anyone know which one for 4.3?
How do I do it and where would I find it?
Any help greatly appreciated!
Click to expand...
Click to collapse
Go to Samsungmobile and download 4.3 BTU ( it's for Uk,simfree phones.) Flash via Odin,maybe that will help
Sent from my GT-I9300 using XDA Free mobile app
thanks so much for the response!
Im sure that romwas the btu one? Does it not seem correct? I will check again.
ricrea said:
thanks so much for the response!
Im sure that romwas the btu one? Does it not seem correct? I will check again.
Click to expand...
Click to collapse
I don't think so since setup started in Polish
Sent from my GT-I9300 using XDA Free mobile app
Attached is the screenshot the latest 4.3 btu. It wants me to download. Ive just looked on the phone, and it is the same
name exactly, and this is where I got it from. What could have gone wrong?
many thanks
ricrea said:
Attached is the screenshot the latest 4.3 btu. It wants me to download. Ive just looked on the phone, and it is the same
name exactly, and this is where I got it from. What could have gone wrong?
many thanks
Click to expand...
Click to collapse
You mean Pda,Csc and Modem are the same? Or md5 is the same?
Sent from my GT-I9300 using XDA Free mobile app
YOU ARE CORRRECT. Im downloading and the file name is different. No idea what i did.
Thanks for your help.
ricrea said:
YOU ARE CORRRECT. Im downloading and the file name is different. No idea what i did.
Thanks for your help.
Click to expand...
Click to collapse
Report back if you get your network back:thumbup:
Sent from my GT-I9300 using XDA Free mobile app
ricrea said:
YOU ARE CORRRECT. Im downloading and the file name is different. No idea what i did.
Thanks for your help.
Click to expand...
Click to collapse
Hi couple of things first you have posted screen shots with your mobile no and Imei no on I would delete them
I am pretty sure flashing another rom won't fix your issue you can easily use roms from a different region and still have full network connection but you can give it a try as suggested above.
First thing first because you have upgraded your phone your efs as changed from efs v1 to efs v2 (which you probably already know) flashing the (DDEMG2 & XXDME4) modems would not work because you need a modem later than mg4 for 4.3 roms.
What you need to try is flash a patched mk6 modem and kernel from here >> https://drive.google.com/folderview...sharing&tid=0B6MIUd7HJudAbU5YaGkzOUowMG8#list << flash then reboot if you get stuck in a bootloop factory reset and wipe cache in recovery.You could also try this >> http://forum.xda-developers.com/gal...ii-network-problem-update-sn-t1918601/page199 << look at post 1984 this is basically the same thing with a rom included and as had some success.
If the patched modems do not work and you don't have a efs backup then I would suggest you need to send for repair.
tallman43 said:
Hi couple of things first you have posted screen shots with your mobile no and Imei no on I would delete them
I am pretty sure flashing another rom won't fix your issue you can easily use roms from a different region and still have full network connection but you can give it a try as suggested above.
First thing first because you have upgraded your phone your efs as changed from efs v1 to efs v2 (which you probably already know) flashing the (DDEMG2 & XXDME4) modems would not work because you need a modem later than mg4 for 4.3 roms.
What you need to try is flash a patched mk6 modem and kernel from here >> https://drive.google.com/folderview...sharing&tid=0B6MIUd7HJudAbU5YaGkzOUowMG8#list << flash then reboot if you get stuck in a bootloop factory reset and wipe cache in recovery.You could also try this >> http://forum.xda-developers.com/gal...ii-network-problem-update-sn-t1918601/page199 << look at post 1984 this is basically the same thing with a rom included and as had some success.
If the patched modems do not work and you don't have a efs backup then I would suggest you need to send for repair.
Click to expand...
Click to collapse
Thanks. I have absolutely no idea what EFS is or how to back up. I would never have usually played with a phone like this it's just my partner was getting fed up of the connection disapearing every now and again, forcing her to reset. I have about 12 hours worth of knowledge on root access, flashing and modifying phones. I am worried I'm going to completely brick the phone. Is there anyway I can make a back of the phone as it is so that if I mess things up I can some how reset it, as at the moment I have Nothing as such. I am going to read up on EFS, I suspect due to the fact the phone was already rooted when I bought it, yet still stuck on the original software and and not updated in anyway, with a pre-exsisting network connection issue, that the phone was already un fixable. I hope not.
I will try all the steps suggested and post results.
Thanks a lot people
ps i hardly have any experience of using forums so sorry if i'm making a mess of this
ricrea said:
Thanks. I have absolutely no idea what EFS is or how to back up. I would never have usually played with a phone like this it's just my partner was getting fed up of the connection disapearing every now and again, forcing her to reset. I have about 12 hours worth of knowledge on root access, flashing and modifying phones. I am worried I'm going to completely brick the phone. Is there anyway I can make a back of the phone as it is so that if I mess things up I can some how reset it, as at the moment I have Nothing as such. I am going to read up on EFS, I suspect due to the fact the phone was already rooted when I bought it, yet still stuck on the original software and and not updated in anyway, with a pre-exsisting network connection issue, that the phone was already un fixable. I hope not.
I will try all the steps suggested and post results.
Thanks a lot people
ps i hardly have any experience of using forums so sorry if i'm making a mess of this
Click to expand...
Click to collapse
Don't worry just take your time and read all the guides if you install a custom recovery you can do a nandroid backup which is basically a full backup of everything on your phone and will restore your phone to how it was before (if you do it right) I recommend using PhilZ recovery and flash it with Odin.
tallman43 said:
Don't worry just take your time and read all the guides if you install a custom recovery you can do a nandroid backup which is basically a full backup of everything on your phone and will restore your phone to how it was before (if you do it right) I recommend using PhilZ recovery and flash it with Odin.
Click to expand...
Click to collapse
I have cwm recovery will this suffice?
I'm using Samsungtool as we speak to back up the EFS folder.
ricrea said:
I have cwm recovery will this suffice?
I'm using Samsungtool as we speak to back up the EFS folder.
Click to expand...
Click to collapse
Yep that will do fine although you are backing up a partially corrupt efs that's the reason you are not getting a signal because the efs v2 can't read the modern correctly that's why you may need a patched modem & kernel to help read it.But back it up anyway in case the efs gets any worse and gets totally corrupt.
tallman43 said:
Yep that will do fine although you are backing up a partially corrupt efs that's the reason you are not getting a signal because the efs v2 can't read the modern correctly that's why you may need a patched modem & kernel to help read it.But back it up anyway in case the efs gets any worse and gets totally corrupt.
Click to expand...
Click to collapse
That was my thinking, the IMEI isn't corrupt yet so I thought best to back up what I have. Ive also backed up using CWM.
Im now trying to flash the proper version of 4.3 for my unlocked uK S3, so im at least using the correct os.
Im flashin zip from cwm, but when i select it on my sd card, it says the following:
Finding update package...
Opening update package...
Installing update...
Installation aborted.
Any ideas why it won't install? Iv'e been Googling it
for 2 hours.
cheers
update - I spent ten hours downloading the proper rom 4.3 btu uk unlocked one, finally flashed it using mobile odin.....
started in Polish again - with no network. I think that this is standard.
Next, I am going to try to flash the patched modem.
tallman43 - do you think my strange serial number needs to be corrected? Is this possible or necessary?
Many thanks - one very tired migraine creating finger-nail biter.
Update:
I finally got the phone to work by following the instructions on the page below;
http://forum.xda-developers.com/galaxy-s3/help/guide-fixing-gt-i9300-network-4-3-stock-t2609635
The patched kernel didn't work on it's own, but the kernel I installed from this thread, along with the other two files, seemed to work, and though the phone is now registered using a much better Android 4.3, it still disconnects every now and again forcing a restart. I really wish I could work out why it does this, I'm starting to believe it may be a hardware issue now.
Is there a program that I could use to test the part of the phone that malfunctions and loses signal completely, to try and work out what is happening when the phone suddenly loses all signal and shows only a circle with a line on it (no sign)
Many thanks to all the people who helped me with this I really appreciate it.
I want to close this thread now as what I require now is off topic from the original post so many thanks for your help people.
I am in NO WAY affiliated with any of the ROM developers mentioned below nor am I a developer at all. I discovered this by trial and error and decided to share with the community. I AM NOT RESPONSIBLE FOR YOU BRICKING YOUR DEVICE!!!!!!!!!!!!!!! Everything mentioned worked for me and me alone. I will NOT guarantee it will work for you. I cannot offer any support concerning why it will not work for you and NEITHER DOES THE DEVS AND THEIR VZW ROMs!!!! SO DO NOT CLOG THEIR THREADS WITH QUESTIONS ABOUT WHY THEIR ROM WON'T WORK WITH YOUR SPRINT NOTE 3!!!!!
THIS IS FOR 4.4.X ONLY!!! I am currently on NC5 baseband so I have no idea if it will work with NH7. It should, but again, I can only speak for me and my setup. SMS, MMS (with 3rd party app to send possibly) and GPS all work for me. Calls are working as well.
EDIT: Ok folks, I have decided to go ahead and post the how to anyway even though I have gotten no response from any of the devs of the Verizon ROMs mentioned below. I assume they are working on new projects and do not have time to mess with this discovery. They also do this for free and have lives to live just like the rest of us. If at any time they want me to remove this I will, purely out of respect for what they have done for all of us. With that in mind, THE DEVS HAVE NO TIME TO SUPPORT THIS SO PLEASE DO NOT CLOG UP THEIR THREADS WITH QUESTIONS RELATED TO THEIR VZW ROMS WORKING ON SPRINT DEVICES!
What you will need: A rooted N900P Note 3 device with a custom recovery installed. I am currently using the latest Philz Recovery so I cannot say for sure if using TWRP will cause this not to work on your device. I don't think it will matter, but to be safe I can only speak for Philz Recovery right now.
If you are on TWRP and want to switch to Philz (many have suggested doing so regardless if you try this or not) keep in mind Philz is not being updated now ( I think ) so the latest build for KitKat is 6.12.9 as far as I know and can be found HERE for the N900P. If you don't know how to change recoveries you probably shouldn't be trying this at all. Research it and you will find out how to do it. Or ask around. You will also need to use a 3rd party MMS app possibly to send MMS messages. On Eclipse it seems to work using the stock Messenger, but on Alliance I had to use Textra to send MMS.
Step 1: BACK UP YOUR CURRENT SETUP!!!! I cannot stress how important this is with ANY ROM flashing or file changing. I have been caught with my pants down before and it really sucks when you have to Odin back to stock because you did not do a Nandroid backup. That is the main purpose of having a custom recovery like Philz or TWRP or CWM is to completely back up your device. Most or all offer EFS backups as well. Also keep a copy of said backup on an external device in case you accidentally wipe your EXT card. Don't think it's not possible, I have done it on other devices because I thought I was cool and could wipe real fast and flash.
Step 2: Acquire the stock kernel for your build/baseband ( Mine is NC5 ) in a flashable .zip. The NCS stock kernel can be found HERE OR you can use Lean Kernel 3.10 ( which I am using) that can be found HERE. MAKE SURE YOU GRAB THE HTLESPR version!!!
Step 3: Download the Verizon Touchwiz ROM of your choice. I have successfully tested this on Eclipse and Alliance. Eclipse can be found HERE Make sure you use the correct build ( 4.4.X ) because it needs to match your baseband. In other words, if you are currently on 4.4.2 or 4.4.4 use the same ROM build that they offer. Eclipse 2.0.1 is what I am using. Alliance ROM is HERE Those are the only 2 I have tried thus far. Experiment if you dare, but the others should work as well ( in theory).
Step 4: Grab the flashable app APN Backup and Restore provided HERE THANKS TO FREEZA!!!! You will need this to get the Sprint APNs on your device. More on how do do this later.
Step 5: Take a deep breath. While still on your Sprint ROM, update your PRL and Profile for good measure because those options will not be in settings on the VZW ROMs. Relax, it will be ok.
Step 6: Boot into recovery, do a full wipe like you would any other time flashing a new ROM. Flash the ROM of choice, then flash the Sprint kernel of choice. If you do not get any errors, reboot system and wait...........and wait some more. It will take a few min for either ROM to boot. If you see the Eclipse or Alliance splash screen (boot animation) you are probably ok. Do not panic at the 3 min mark and shut down. Just let it do it's thing. You should eventually see the beginning setup screen. If after 8-10 min you still are seeing the animation it probably is in a bootloop. It may not work but you can simply power down and boot back into recovery and restore your backup, or try again flashing the kernel first, then ROM, then kernel again then boot into system and wait again. Just use some patience.
Step 7: If you made it to this step, congrats, you have booted a VZW ROM onto your Sprint Note 3. But we have more to do. After you set up wifi and gone through the setup menu you may see some Verizon related errors pop up. Just ignore them for now. Those apps can be frozen using TiBu after completely done as a cleanup measure. Boot back into recovery ( On Eclipse you will have to do this using vol up/home/power buttons because there is no 4 way reboot menu. This can be added with Xposed and Wanam later as well). Flash the APN Backup and Restore app ( this could also be done when you flashed the ROM I suppose) and reboot. which will put the APN backup & restore app into your /system/app directory and the SprintAPNxXML file onto your sdcard. Once done installing, boot back up and launch the application, Ignore the warning screen you get from first launch, then press menu and select "Disable ICS check." Once done, exit the app and load it again, then choose "Delete APNs" and select yes to the following prompt. Once done, go ahead and tap Restore APNs, and select the SprintAPNsXML from the prompt and select no to the duplicate check. IF THIS DOES NOT WORK THE FIRST TIME- Move the app from /system/app directory to /system/priv-app/ directory and change permissions to rwx/rwx/rwx and reboot. Then try to Delete APN, then try to Add APNs using the provided SprintAPNxXML file in the app. This will add Sprint APNs.
Step 8: Go into settings/more settings/Mobile Networks/Access Point Names and choose the appropriate one for your area. I chose APN2 LTE Internet n.ispsn. You should now have data icon showing. This worked for me, hopefully it worked for you. I have seen it switch between LTE and 3G so I know it is handing off correctly. Make sure Network Mode is CDMA/LTE/EVDO as well. I haven't tested on the road yet, but will tonight. But it has been working flawlessly for me on local towers.
Step 9: You will need to add Sprint apps you were using, including voicemail. Install Titanium Backup and freeze Verizon related apps if you want. Also you will notice in settings your phone will show to be a N900V instead of N900P due to the Verizon ROM. Don't panic.
Step 10: Profit! At this point you should be able to tinker with the ROMs according to what the threads offer. I know Eclipse has it's own app to customize some things. But Xposed will work as well. I have no idea if Hotspot works or any of that stuff, I do not use it. Alliance has a ton of customization settings and apps built in, including themes. Some minor tweaks haven't worked, but most have. Eclipse has actual AOSP functionality baked in. ENJOY!! I will try to answer as many questions as i can, but again, please DO NOT clog up the threads of those great ROMs with questions, the devs do not, as far as I know, support this method and will not be able to help you with your Sprint device.
EDIT: When you connect to your PC via USB for the first time you may have to toggle MTP on and off to get it to be recognized in Explorer. It will most likely say N900V when you get connected. Also on Alliance a couple of Verizon apps will try to install on your PC. You can cancel them.
Screenshots
MUCH THANKS!!!
Sprint side: Freeza for the APN Backup and Restore app as well as all you have done for the Sprint Note 3!! LMMT for the NC5 kernel thread! Phil3759 for Philz Recovery for the N900P
Verizon Side: Nitroglycerine33 for all he has done for the community. My first attempt at flashing was an Eclipse ROM. Cannot say enough about what he has done! Beanstown106 for the hard work on all the Verizon devices and now along with Team Alliance they continue to dominate!
Multiple Devices: Imoseyon for his great Lean Kernels!! I have run them on every device so far. They just get better and better.
All the devs on all the devices deserve a huge thanks from all of us! Without them none of this would be possible!!
this would be cool to know, and give us more choices at ROM flashing time
Is it me or is XDA running real slow today?? Even on Tapatalk.
Anyway, so far I have SMS, MMS and GPS working smooth. Really was simple. No need to decompile or change the ROM itself. As long as the bootloaders match (4.4.2 to 4.4.2 etc) it works. Thanks to an earlier post by Freeza dealing with APN restore everything works thus far. Really hope Nitro gives me the go ahead to create a thread or at least post a how to with links to his site. If you want real AOSP feel on a TW ROM, Eclipse is the way to go. I ran this all the time on my VZW Note 3.
Also will be trying the same with a couple of other VZW ROMs I once loved as well. Stay tuned. :good:
Looks like I will have to post the How To here anyway so I am testing another VZW ROM now (Alliance) and if all goes well I will add the directions to this thread in the OP.
All the way to Chicago and back with no data issues. Have a hard time believing nobody knew we could do this.
Real_JESRadio said:
All the way to Chicago and back with no data issues. Have a hard time believing nobody knew we could do this.
Click to expand...
Click to collapse
I had no clue! I knew the devices were very similar but figured if it were possible to use VZW ROMs across devices, I'd have started months ago! Thanks for the How To, I'll be giving it a shot this evening. Cheers! :beer:
Sent from my SM-G900P using XDA Free mobile app
sixshooterz said:
I had no clue! I knew the devices were very similar but figured if it were possible to use VZW ROMs across devices, I'd have started months ago! Thanks for the How To, I'll be giving it a shot this evening. Cheers! [emoji481]
Sent from my SM-G900P using XDA Free mobile app
Click to expand...
Click to collapse
Cool. Hope it goes well. Must be the CDMA thing. At least it gives us more options. Eclipse is working so good I can't get away from it lol
Jasmine 2.4.1 works
---------- Post added at 07:23 PM ---------- Previous post was at 07:22 PM ----------
Hyperdrive RLS8
Vzw lte b4 on/off
are you able to get new LTE Bands (4 ,13) so that n900p can operate on verizon network on MVNO?
or are you able to VZW LTE B4 ON/OFF to enable band 4 on?
This sounds awesome! Thank you for posting! I will have to try this out this weekend.
Latest one I tried was vn Rom 7.2 and Norma beta 6 both good.
Sorry these 2 are not Verizon but are for 9005 and they do work.
Anyone flash T-Mobile roms on this phone?
twisteddroid said:
Anyone flash T-Mobile roms on this phone?
Click to expand...
Click to collapse
Ive flashed this rom selecting the tmobile version in aroma runs with no problems just no data and messaging
Ok, i'm fairly new to this stuff but have successfully rooted and modified several of my devices over the years. I've been attempting to upgrade my vs985 to as close to stock 5.1.1 as i can and after much reading decided on jasmine. I was rooted on kk 4.4.2 12b and I had no problems. the main reason i wanted to upgrade was for compatibility with my android play car stereo. I didn't have twrp so first i downloaded flashify and quickboot then flashed twrp from flashify. All good so far. Next I downloaded jasmine 9.0 and 9.1 or at least i thought lol. As it so happened i mistakenly ended up with one of the files being just the kernel for 5.1.1 35b. Must of been a long day cause I mistakenly failed to backup my current system and proceeded wipe data, cache, dalvik, and flashed the kernel file. As you might imagine it didn't turn out very good. I was stuck in boot loop. Fortunately I could still get into download mode so I was able to use the lg flash tool and I brought it all the way back to 10b stock firmware. Then i grabbed stump and rooted and flashed twrp again. at some point i noticed my cell signal was all over the place, up, down , no signal and it roamed almost constantly if there was any signal. I've had this phone and service for well over a year and never had anything like this at all. I knew it was something I did. I checked the back cover to be sure it was on properly and had good connection with the antenna and all checked out. I decided to go ahead and do the upgrade to jasmine 9.1 hoping this would correct the issue. Well no dice. I did create a backup this time and proceeded to wipe everything and flash 9.0 reboot then wipe nothing and flash 9.1, i guess as you call it "dirty" then reboot again. Here is a link to where i got the zips and instructions
http://forum.xda-developers.com/showpost.php?p=63305722&postcount=4842
in the instructions it says "RESET factory from within ROM (in Settings) - REQUIRED" . this step seemed strange as why would i do a factory reset on my device and erase everything i just did? would it not return it to original? I wasn't even sure if that was what he meant so i skipped that. After all was finished my signal was still all over the place could hardly make a call. it was bad. So once again I used lg flash tool and returned it to stock 4.4.2 10b, this time I wiped the data, cache, delvik and system. To my complete surprise the signal had not improved, in fact it could have actually been worse. As I said waaaaaay at the top of this post before i started all this i was running 4.4.2 12b, not sure how i ended up with 12b as i don't remember any upgrades after i downgraded to 10b and rooted. I froze the ota's with titanium backup but maybe 12b was pushed before i was able to freeze them. Anyway I couldn't figure out how to get 12b back now so I just flashed the 4.4.2 12b modem instead, This time I wiped cache and delvik before and after the flash then rebooted. This fixed my signal, everything seems normal now. no roaming and good signal. my software build however still shows 10b, but I guess thats correct since I only flashed the modem.
I really want 5.1.1 on my G3 but I need my signal too lol. can any one help me figure out how to get this done, can I flash the 12b modem on 5.1.1 this is where i got the file
http://forum.xda-developers.com/verizon-lg-g3/development/rom-jasminerom-v1-0-t2904641 it is way down the bottom of the page. Sorry for the extremely long post i just wanted to make sure i didn't leave any details out.
Any help would be greatly appreciated,
thanks in advance
@Allen227
i dont know if jasmine flashes the L modem when you flash it, but if it doesnt, that would be why you are having issues after flashing the rom.
other than that, i dont know what would cause modem issues.
bweN diorD;4132606 [user=7106818 said:
@Allen227[/user]
i dont know if jasmine flashes the L modem when you flash it, but if it doesnt, that would be why you are having issues after flashing the rom.
other than that, i dont know what would cause modem issues.
Click to expand...
Click to collapse
@Allen227
TL;DR but yes, JasmineROM flashes the appropriate modem. v9.0 only flashes the 24B modem because it doesn't contain a fuller set of the necessary partitions to allow the 35B modem to work by simply replacing the 24B modem with the 35B one.
You can flash the 35B bootstack after flashing JasmineROM 9.0 and the 9.1 update, or SkyDragon 6.x, but you must not be on the 35B bootstack before flashing either UNLESS you also flash the 35B bootstack again after flashing the ROM.
For reasons why: http://forum.xda-developers.com/showthread.php?p=64064555
Edit: I meant to add, the 35B boostack contains the 35B modem and everything needed for it to work with JasmineROM 9.0/9.1.
Hi, anybody from bosses ,plz help, sorry for noob querry... using g3 stock rom 4.4.2 and want to upgrade to lollipop and find jasmine ROM most votes. rooted my device with king root and installed twrp 2.8.7.0 recovry. downloaded jasmin ROM9.0, back up my current rom.
can u please guide me steps,
have i too flash kernal before jasmine ROM? or my existing stock kernal will work fine with jasmine 9.1
placed downloaded ROM in my download folder in phone memory [not in sd Card] , when i would boot in recovry in wipe cache delvik etc will it erase this rom and phone data too???
what if something gone rom? in my g3 there is no option of adb , adb does not work on my g3 dont know why.....
if something gone wrong , can i recover phone?
please see attached pics for some clarification...
sorry for,long post, actualy want to be safe ,,, as i am new for these things ..
tAheEr73 said:
Hi, anybody from bosses ,plz help, sorry for noob querry... using g3 stock rom 4.4.2 and want to upgrade to lollipop and find jasmine ROM most votes. rooted my device with king root and installed twrp 2.8.7.0 recovry. downloaded jasmin ROM9.0, back up my current rom.
can u please guide me steps,
have i too flash kernal before jasmine ROM? or my existing stock kernal will work fine with jasmine 9.1
placed downloaded ROM in my download folder in phone memory [not in sd Card] , when i would boot in recovry in wipe cache delvik etc will it erase this rom and phone data too???
what if something gone rom? in my g3 there is no option of adb , adb does not work on my g3 dont know why.....
if something gone wrong , can i recover phone?
please see attached pics for some clarification...
sorry for,long post, actualy want to be safe ,,, as i am new for these things ..
Click to expand...
Click to collapse
In the future, please do not post the same thing in two different threads. This is against XDA's forum rules. Also, no reason to hijack an only partially related thread. I answered you in the JasmineROM thread.
Sorry for rule breaking, actually i did not aware of that. will avoid surely next time and thanks for reply. hats off to you.
Thanks for your help guys. Last night I figured out my phone was allowing me to send and receive text messages and make outgoing calls but was completely unable to receive any calls. Signal still terribly inconsistent, it would be on 4g one minute then you could watch as it dropped then no service. There'd be no service for 3 or 4 minutes then it would repeat that cycle again. If I switch from global to cdma/let in settings it would immediately regain full signal. Then the cycle of it dropping out would start again. I got to looking through about phone in settings and realized my imei number was missing, all zeros. I'm assuming that probably is the root of my problems. Not sure what to do, I doubt Verizon can help. Phones not insured or under warranty anymore. I haven't researched this New development on te forums yet it got to late last night. If anyone knows of this problem I could use your help. Thanks
Allen227 said:
Thanks for your help guys. Last night I figured out my phone was allowing me to send and receive text messages and make outgoing calls but was completely unable to receive any calls. Signal still terribly inconsistent, it would be on 4g one minute then you could watch as it dropped then no service. There'd be no service for 3 or 4 minutes then it would repeat that cycle again. If I switch from global to cdma/let in settings it would immediately regain full signal. Then the cycle of it dropping out would start again. I got to looking through about phone in settings and realized my imei number was missing, all zeros. I'm assuming that probably is the root of my problems. Not sure what to do, I doubt Verizon can help. Phones not insured or under warranty anymore. I haven't researched this New development on te forums yet it got to late last night. If anyone knows of this problem I could use your help. Thanks
Click to expand...
Click to collapse
If you go into the main Verizon G3 section or possibly the non-Verizon G3 section and use the search field to search for "IMEI" you'll probably find a helpful thread. I think it involves the QPST program on a Windows PC. You'll need the IMEI that it's supposed to have, so hopefully have that on the box or Verizon's website lists it.
Sometimes that's seemed to happen for some people when flashing TOTs, KDZs or ROMs. I've been lucky, it hasn't happened to me through all my flashing over the past year. Once you get it fixed, rooted and put TWRP on, you can back up the IMEI partition in TWRP. It's called something else in TWRP like EI or something - I forget.
Good luck!
roirraW "edor" ehT said:
If you go into the main Verizon G3 section or possibly the non-Verizon G3 section and use the search field to search for "IMEI" you'll probably find a helpful thread. I think it involves the QPST program on a Windows PC. You'll need the IMEI that it's supposed to have, so hopefully have that on the box or Verizon's website lists it.
Sometimes that's seemed to happen for some people when flashing TOTs, KDZs or ROMs. I've been lucky, it hasn't happened to me through all my flashing over the past year. Once you get it fixed, rooted and put TWRP on, you can back up the IMEI partition in TWRP. It's called something else in TWRP like EI or something - I forget.
Good luck!
Click to expand...
Click to collapse
Thanks again I will check that out now
Allen227 said:
Thanks again I will check that out now
Click to expand...
Click to collapse
I have spent sooooo many hours on this. The qpst apk wont see my phone I have done everything the tutorials suggest. the instructions are only applicable if there are no issues, in other words, in a perfect world. I'm sure its something stupid and very simple but I don't even have a place to start. First, its hard to believe this works on all OS's, but it doesn't state anywhere what it is and isn't compatible with. that info would be helpful. i have spent 4 hours a day for over a week trying to get this fixed and I'm no closer than i was when I started. Very frustrating. I'm still open to suggestions or any help that can be offered.