Related
Hello all,
I have this Vibrant I’m trying to get to run JB 4.1.2 or 4.1.1 I’ve tried 5 ROMS and none of them seem to find a network... When I go back to my Backed up Stock ROM I get network no problem. And yes I’m wiping both letting sit for 10 to 15 before first reboot.
You are either losing baseband, or losing your imei. I don't know why this happens to some people?? It can be fixed but you will have to fix after you flash the JB ROM of your choice. Because I don't know if its baseband alone, I have to assume its your imei. You need to backup your /efs folder. This might already be done. You can check by going to /sdcard/backup/efs, if you have efs folder in backup, you are good. If not you need to use a root file explorer app to copy /efs and put it on your /sdcard.
The efs folder holds important phone/network specific info including imei.
Once you get a JB ROM up and running,
Go to settings>about phone what is your Baseband-????
Check imei as well
If only baseband is missing just flash a modem
If imei is missing you will need to copy and paste the efs backup you created to the root of your phone and reboot. There are some more detailed guides on this.
I approve this message.
xXy3kXx said:
... When I go back to my Backed up Stock ROM I get network no problem ...
Click to expand...
Click to collapse
What do you flash after you odin back to stock? I lose IMEI, APN, &, baseband if I go directly from stock rom to JB.
What works for me is: stock » GB BL (optional) » update.zip » CM7 (vibrantmtd) » CM10 (optional, I only use the kernel to full wipe) » JB.
yosup said:
What do you flash after you odin back to stock? I lose IMEI, APN, &, baseband if I go directly from stock rom to JB.
What works for me is: stock » GB BL (optional) » update.zip » CM7 (vibrantmtd) » CM10 (optional, I only use the kernel to full wipe) » JB.
Click to expand...
Click to collapse
When was the last time you tried? The issue where going from a non/old Cwm recovery would break your efs was fixed a while back (with the assistance of a user who was kind enough to send me the rundown of why it was not restoring)
Although you may still need to flash again once in a new recovery.
Sent from my Galaxy Nexus using xda premium
FaultException said:
When was the last time you tried? The issue where going from a non/old Cwm recovery would break your efs was fixed a while back (with the assistance of a user who was kind enough to send me the rundown of why it was not restoring)
Although you may still need to flash again once in a new recovery.
Click to expand...
Click to collapse
FE, always spreading solid wisdom throughout the Vibrant forum. Really appreciate all you do for our ancient rigs.
As for the IMEI issue, it was from a crack-flashing & Odin session - ie. I was testing out whether I could jump from an Odin .tar straight to Semaphore kernel .tar then to Slim Bean. I should mention that my phone is one of those post-EU (Encryption Unsuccessful) ones, so it wouldn't surprise me if that alone plays a hearty role.
IIRC, I had tried the T959UVJFD, GBBOOT-T959UVJFD, and Bionix-FishmanMod_odin tar's ... but none of those roms would boot up on my phone after the flash. Again, most likely EU related.
I then flashed Eugene_2E_JK2_Froyo.tar (+ 512 pit). IMEI, APN, & Baseband all fine once booted. Then, Odin'd a Semaphore JB 2.4.0sv.tar (CWM 6.0.1.4), wiped, and then flashed Slim Bean 2.7.0 (4.1.2). Once booted, there was no APN or Baseband, and IMEI was now the generic one (004999...).
What eventually worked was Eugene .tar > GB BL's > update.zip (s15274n's CWM 2.5.1.2) > cm-7.2.0-vibrantmtd > CM10 nightly (kernel only to do a full wipe) > Slim Bean 2.7.0.
For some reason if I don't flash cm7.2.0 before jb...My phone is off and then plugged into the charger it will reboot, its not 'stay awake during charging,' its just a fluke on my phone.
No two vibrators are the same...
I approve this message.
I also have one Vibrant that has a very strange issue that it can't keep its bootloader and the only way to fix it was flashing the Eugene odin file. Even with the factory odin and updating to Froyo via Kies. The bootloader retains with cm7, cm10 and aokp, but with any other roms like Paranoid and SlimBean the bootloader gone missing, even if the modem.bin is still in /radio. Not sure why the Eugene odin fixed this issue.
Here's the link if anyone need it: http://d-h.st/users/Big%20Dog%20KMc
Longtime XDA'er here with a problem.
I was rooted on stock 4.1.2 for over a year but wanted to update to take advantage of newer features such as chromecast mirror on kitkat. I had a perfectly working phone until I tried flashing updates. I followed instructions and only flashed the MJ9 baseband on roms that tell me too, and even flashed ND7 baseband for other ports. I was able to install multiple variants of 4.4.2 with both twrp and philz recoveries with the same result. I can't get sms/mms to come in. What's weird is upon bootup I will get the same test message only once, then nothing. I even tried flashing agni kernel with no luck. The phone works great with the exception of text messaging. Calls work, GPS locks, and no issues with wifi. APN settings look fine (compared to my wife's note 2 which is identical model still on 4.1.2). I popped my sim into an LG lucid I had as a backup and the text's sitting in limbo start streaming in, so I know my sim isn't bad. I even made sure to disable hangouts with no luck. Even tried Go Sms Pro with same result. I have since decided to go to 4.3 and am having the same issue on those roms on the MJ9 baseband and MJ9 stock kernel.
I'm pulling my hair out because I can't figure this out and I'm a pretty smart fella, this just has me stumped.
Ideas anyone? I have been researching like mad and nothing I try seems to resolve.
Thanks in advance!
timber03 said:
Longtime XDA'er here with a problem.
I was rooted on stock 4.1.2 for over a year but wanted to update to take advantage of newer features such as chromecast mirror on kitkat. I had a perfectly working phone until I tried flashing updates. I followed instructions and only flashed the MJ9 baseband on roms that tell me too, and even flashed ND7 baseband for other ports. I was able to install multiple variants of 4.4.2 with both twrp and philz recoveries with the same result. I can't get sms/mms to come in. What's weird is upon bootup I will get the same test message only once, then nothing. I even tried flashing agni kernel with no luck. The phone works great with the exception of text messaging. Calls work, GPS locks, and no issues with wifi. APN settings look fine (compared to my wife's note 2 which is identical model still on 4.1.2). I popped my sim into an LG lucid I had as a backup and the text's sitting in limbo start streaming in, so I know my sim isn't bad. I even made sure to disable hangouts with no luck. Even tried Go Sms Pro with same result. I have since decided to go to 4.3 and am having the same issue on those roms on the MJ9 baseband and MJ9 stock kernel.
I'm pulling my hair out because I can't figure this out and I'm a pretty smart fella, this just has me stumped.
Ideas anyone? I have been researching like mad and nothing I try seems to resolve.
Thanks in advance!
Click to expand...
Click to collapse
Odin back to stock should fix this issue.
DreamFX said:
Odin back to stock should fix this issue.
Click to expand...
Click to collapse
flashing stock 4.1.2 via Odin does fix it, but when I try to upgrade to any rom from there I have same problem. Pretty much all of the roms 4.3+ specify flashing with MJ9 firmware, which I have done. I have tried 4 roms today and same problem every time.
So annoying, it's like I can't get higher than 4.1.2
timber03 said:
flashing stock 4.1.2 via Odin does fix it, but when I try to upgrade to any rom from there I have same problem. Pretty much all of the roms 4.3+ specify flashing with MJ9 firmware, which I have done. I have tried 4 roms today and same problem every time.
So annoying, it's like I can't get higher than 4.1.2
Click to expand...
Click to collapse
I'm really surprised I'm the only one having this issue. After much research and countless attempts, it seems the most I can do is run stock 4.1.2 rooted, and can apply the MJ9 firmware... but if I try to update to any rom 4.3 or above, my text messaging stops working, otherwise the ROM's work great and phone calls, 4G Data, Wifi, GPS, etc all work perfect... only the sms/mms doesn't.
If I run the stock, rooted 4.1.2, with MJ9 radio everything runs great, including sms/mms, so my feeling is that I need a rom that doesn't flash kernel, or baseband, but jsut system, data, etc... then I might have a shot but it's a long shot at this point. I have even tried beans build 26 which is 4.3 and have EXACTLY the same problem.
The only other thing I've noticed is I have hardware version I605.07 whereas most people it seems have I605.06 from what I've noticed while browsing similar threads.
got it working with no help from anyone... a lot of steps but worth it. Definitely not the normal path everyone has been posting.
timber03 said:
got it working with no help from anyone... a lot of steps but worth it. Definitely not the normal path everyone has been posting.
Click to expand...
Click to collapse
Timber any chance you would be ale to point me to the fix? This has been driving me nuts
sugarfunk said:
Timber any chance you would be ale to point me to the fix? This has been driving me nuts
Click to expand...
Click to collapse
Absolutely... I will type up instructions in the morning. As for driving you nuts I know exactly what you mean... I was pulling my hair out and almost gave up hope but I tried something and it worked. It involves using beans 26 rom and a combination of Twrp and Philz recoveries and backup/restores... if you are having this problem, the main problem is the flashing of the MJ9 firmware.
I'll clue you in tomorrow
sugarfunk said:
Timber any chance you would be ale to point me to the fix? This has been driving me nuts
Click to expand...
Click to collapse
as promised, here's the steps it took for me to get working... It may seem a little bit of a long process but almost 4 days now and no more issues, so I trust this process. It must be something different in my hardware versus other, and I'm assuming yours is like mine.
Let me know if you have any questions
Start with 4.1.2 stock rooted
1. Install latest TWRP Recovery v2.7
2. Backup EFS and Modem as separate backups to your external SD card
3. In Recovery, Wipe.. Advanced Wipe and wipe everything (including Internal Storage) except external SD and USB-TG partitions
The next set of steps is to ensure you have a clean base to work with...
4. Reboot to download mode and using Odin 3.07 flash stock 4.1.2 firmware
in Pit select Sch-i605-16gb.pit
in PDA, select the stock 4.1.2 MC3 firmware
make sure only the following checkboxes are selected: "Auto Reboot", "Re-Partition" and "F. Reset Time"
Hit Start, wait till process completes and boots into o/s. Then skip all wizard options to get to home screen.
5. Root phone using casual
I had no issues using version "NoYouVerizon-GalaxyNote2-CASUAL R515.jar"
6. After root is successful, boot to Recovery and install latest TWRP recovery again since you will have twrp v2.5 due to the root process
7. Repeat step #3 (3 times to make sure everything is wiped clean)
8. IMPORTANT as this is what seemingly fixed the sms issue for me: using twrp recovery, restore the EFS backup you took in step #2 (do not restore the modem)
9. Install Beans 26 rom (Alliance 4.3) which will now give you a proper MJ9 base and kernel to work with. Again, skip all wizard prompts after it loads just so you can get to home screen.
10. Boot into recovery and now backup the new 4.3 EFS and modem partitions to your external SD.
You are not actually going to need the modem backup for the next steps, but if you have a problem installing a rom,
you now have working MJ9 EFS and Modem partitions should you have a problem with any roms from this point forward
11. Repeat step 7 & 8 (restore only the EFS 4.3 partition)
12. Important.. Now install latest Philz recovery
13. Install 4.4.2 rom using Philz recovery
At step 13 is where I installed the Ditto Note 3 rom v5.2, and chose "do not wipe" during the aroma install process.
14. once installed allow it to reboot, if it hangs on samsung boot animation for more than 5 minutes do the following:
a) pull battery and boot into philz recovery, then wipe only the following: Data, Cache, and dalvik cache
b)Install Agni Kernel (PSN_AGNi_pureSTOCK-v4.2.5_I605_4.4.2_AROMA-signed.zip)
c)reboot and you should get the android wizard for the rom in 2 or 3 minutes
If you have a problem like I did with regards to the Camera not working in the new rom, dirty flash the rom again (do not do any wiping)
Then re-install Agni Kernel since the rom installs it's own, otherwise it will break wifi, at least it did on mine.
There are a few more fixes to get tethering, etc working but I can provide those steps if needed. It basically involves installing xposed framework and the moto-x module.
timber03 said:
as promised, here's the steps it took for me to get working... It may seem a little bit of a long process but almost 4 days now and no more issues, so I trust this process. It must be something different in my hardware versus other, and I'm assuming yours is like mine.
Let me know if you have any questions
Start with 4.1.2 stock rooted
1. Install latest TWRP Recovery v2.7
2. Backup EFS and Modem as separate backups to your external SD card
3. In Recovery, Wipe.. Advanced Wipe and wipe everything (including Internal Storage) except external SD and USB-TG partitions
The next set of steps is to ensure you have a clean base to work with...
4. Reboot to download mode and using Odin 3.07 flash stock 4.1.2 firmware
in Pit select Sch-i605-16gb.pit
in PDA, select the stock 4.1.2 MC3 firmware
make sure only the following checkboxes are selected: "Auto Reboot", "Re-Partition" and "F. Reset Time"
Hit Start, wait till process completes and boots into o/s. Then skip all wizard options to get to home screen.
5. Root phone using casual
I had no issues using version "NoYouVerizon-GalaxyNote2-CASUAL R515.jar"
6. After root is successful, boot to Recovery and install latest TWRP recovery again since you will have twrp v2.5 due to the root process
7. Repeat step #3 (3 times to make sure everything is wiped clean)
8. IMPORTANT as this is what seemingly fixed the sms issue for me: using twrp recovery, restore the EFS backup you took in step #2 (do not restore the modem)
9. Install Beans 26 rom (Alliance 4.3) which will now give you a proper MJ9 base and kernel to work with. Again, skip all wizard prompts after it loads just so you can get to home screen.
10. Boot into recovery and now backup the new 4.3 EFS and modem partitions to your external SD.
You are not actually going to need the modem backup for the next steps, but if you have a problem installing a rom,
you now have working MJ9 EFS and Modem partitions should you have a problem with any roms from this point forward
11. Repeat step 7 & 8 (restore only the EFS 4.3 partition)
12. Important.. Now install latest Philz recovery
13. Install 4.4.2 rom using Philz recovery
At step 13 is where I installed the Ditto Note 3 rom v5.2, and chose "do not wipe" during the aroma install process.
14. once installed allow it to reboot, if it hangs on samsung boot animation for more than 5 minutes do the following:
a) pull battery and boot into philz recovery, then wipe only the following: Data, Cache, and dalvik cache
b)Install Agni Kernel (PSN_AGNi_pureSTOCK-v4.2.5_I605_4.4.2_AROMA-signed.zip)
c)reboot and you should get the android wizard for the rom in 2 or 3 minutes
If you have a problem like I did with regards to the Camera not working in the new rom, dirty flash the rom again (do not do any wiping)
Then re-install Agni Kernel since the rom installs it's own, otherwise it will break wifi, at least it did on mine.
There are a few more fixes to get tethering, etc working but I can provide those steps if needed. It basically involves installing xposed framework and the moto-x module.
Click to expand...
Click to collapse
Whatever works for you. Glad your back up and running.
Would like some help. I have flashed CM 11 and can't make calls. It says mobile network not available. Tried flashing AOKP rom as well and same thing. Mobile data works fine, although i have gotten a popup twice that says 'Google Play Services not supported by your device, please contact your manufacturer' (no noticible issues from this, google stuff i've tried so far works). I have included a screenshot so you can see my baseband and rom version, etc.
Now, i had a great deal of trouble getting a rom flashed to start with, CWM put me into a bootloop and TWRP wouldn't flash anything because it said it couldn't mount /storage when i tried. Used Philz advanced CWM (love it btw, will be using it from now on). Still wouldnt flash the hltespr specific CM11 version so had to use the unified hlte version (it gave me the status 7 asserts issue, but editing the asserts out just gave me a bad file error when flashing). I wiped data/cache/dalvik between each flashing. I don't know if any of that would have bearing on this problem, just including any details i can. Any advice?
Verilin said:
Would like some help. I have flashed CM 11 and can't make calls. It says mobile network not available. Tried flashing AOKP rom as well and same thing. Mobile data works fine, although i have gotten a popup twice that says 'Google Play Services not supported by your device, please contact your manufacturer' (no noticible issues from this, google stuff i've tried so far works). I have included a screenshot so you can see my baseband and rom version, etc.
Now, i had a great deal of trouble getting a rom flashed to start with, CWM put me into a bootloop and TWRP wouldn't flash anything because it said it couldn't mount /storage when i tried. Used Philz advanced CWM (love it btw, will be using it from now on). Still wouldnt flash the hltespr specific CM11 version so had to use the unified hlte version (it gave me the status 7 asserts issue, but editing the asserts out just gave me a bad file error when flashing). I wiped data/cache/dalvik between each flashing. I don't know if any of that would have bearing on this problem, just including any details i can. Any advice?
Click to expand...
Click to collapse
Have you upgraded your bootloader to NH7? I know most of the newly-updated CM-based ROMs require you to be on NH7 before flashing. That's most-likely why you weren't able to flash the htlespr ROMs. The unified ROMs no longer include the correct APNs for Sprint, so that's why you don't get service on it. I don't know why mobile data works on it.
topherk said:
Have you upgraded your bootloader to NH7? I know most of the newly-updated CM-based ROMs require you to be on NH7 before flashing. That's most-likely why you weren't able to flash the htlespr ROMs. The unified ROMs no longer include the correct APNs for Sprint, so that's why you don't get service on it. I don't know why mobile data works on it.
Click to expand...
Click to collapse
No, didnt realize that i needed to do that. I'll do some research on it because i don't have any idea how to update the bootloader. If you have a link to a good tutorial that would be wonderful! Thanks!
Ok so i tried that, found this tutorial, followed it, no luck. Tried full wipe/reset after that to see if it would let me install the hltespr versions, still no dice. Same situation, mobile data works, calls don't. Will have to wait till daylight to try texting so i don't wake anyone up but i suspect that texting won't work either. Has anyone experienced this and fixed it? Lol i really didn't drop $100 on a phone to be saddled with all the Samsung and Sprint baloney that it comes with, don't wanna unroot....
Bump
Anyone have ideas on this? Have continued to try fooling around with the udater-script file to resolve the status 7 problem so I can install the hltespr variant, still no dice. Please someone help!
Bump!
Sorry, I typically don't have access to XDA forums on the weekend, so couldn't answer your question till now.
You flashed only the baseband/modem, not the Bootloader. If you want to update the Bootloader, you need to use ODIN to flash the Complete OTA NH7 Update.
In order to update the Bootloader, you need to make sure that you use the PC ODIN (not the mobile one) and that you completely power off the phone before you enter download mode (don't access download mode by using the extended power menu when shutting down the phone). I don't think you need to do the battery pull that Freeza had in his instructions (I didn't do it when I ODIN-flashed the NH7 OTA update), but it wouldn't hurt to do it.
Thanks for that, I will try it as soon as I get home tonight! The next thing I had decided to try was to unroot, to back to stock, then try flashing that before I start with the custom recovery and ROM. Do you think I should do that first before doing the whole thing or could that work just flashing that with my phone as-is?
Verilin said:
Thanks for that, I will try it as soon as I get home tonight! The next thing I had decided to try was to unroot, to back to stock, then try flashing that before I start with the custom recovery and ROM. Do you think I should do that first before doing the whole thing or could that work just flashing that with my phone as-is?
Click to expand...
Click to collapse
Well, I always recommend a full wipe (data, system, cache, dalvik) when flashing ROMs. I haven't wiped my internal storage or external storage since I got the phone, so that's not really necessary.
I don't think that unrooting your current ROM is necessary. Flashing the ODIN OTA update will automatically remove root access, so that's not an issue. Here's the steps I took when I updated to NH7 and installed my current ROM (see my sig):
Make a Nandroid backup.
I always do this just so I have a "record" of what I left behind. It also allows me to have all of my app data that I can restore via Titanium Backup (you have to buy the Pro version in order to restore specific apps from a Nandroid backup). I always store a copy on my ext. storage and on dropbox.
Do a full wipe
As I mentioned above, I always wipe data, system, and the caches when flashing ROMs. While I have to take some time to get the new ROM exactly as I like it, it minimizes any potential FCs and errors that some people get when dirty flashing.
Install NH7 all-in-one via ODIN
I installed the NH7 via ODIN. Please note that this is the fully stock, unrooted ROM and will also install the stock recovery.
Let the phone boot and connect to Sprint. Update Profile and PRL.
I do this periodically whenever I go back to stock (from AOSP). I rarely have connection issues, but updating the PRL an profile can help with those.
Install a custom recovery using ODIN.
My recovery of choice is TWRP, but others have found just as much success with CWM and Philz. Just make sure that you're installing the correct version of the recovery (4.4.X version, not the 4.2.X version). I always reboot to the main system after installing a recovery, but that's up to you. In the rest of this post, I'll say "TWRP," but I really mean "custom recovery."
[OPTIONAL] Make a Nandroid backup of the stock ROM
I always do this, but I recognize that it's not necessary, especially since we can just ODIN back to this image at any time. I just like having the option of having a stock backup on the device (in case catastrophe strikes while I'm away from a computer).
Use TWRP to flash your AOSP ROM of choice.
If you haven't installed any apps or messed around with the settings, you shouldn't have to wipe before flashing, but (in case you haven't noticed by now), I tend to err on the side of caution, specifically: wiping everything (data, system, and the caches) before I flash anything.
Set up the ROM how you like it and [OPTIONAL] make one last Nandroid Backup
Whenever I set up a new ROM to the exact way I like it (statusbar settings, accounts set up, apps installed and configured, etc), I make a nandroid backup of my device. This allows me to go back to that "fresh" image whenever something happens to the device and I don't have to muddle around fixing those minor tweaks. Again, I tend to err on the side of wiping the phone too often and taking too many backups, but I've rarely had issues with my phone and ROMs because of it (to the point where I can spend most of my XDA time helping others with their phones), so it might be prudent to follow the advice.
Anyways, that's how I upgraded to NH7 and installed a custom ROM. Others may take a less conservative approach and you're welcome to adjust any of the optional steps.
Hope this helps!
-Topher
OK, did all that successfully, when it went back to stock stiil had the same issue. Mobile data functions, mobile network for calls/SMS doesn't. Did the whole update prl/profile and even tried reactivating from settings, still nothing. Was able to install custom recovery (Philz) and the hltespr CM11 variant instead of the unified generic version. Still has the same problem, mobile network not available. Everything else works perfectly. I did verify in settings that it still wound up as the NH7 after everything I did. Note I did a full reset before each thing that got flashed in this process, and one more for good measure after. Let it boot to the system between steps too.
Lol I've been rooting and switching between ROMs for years and have never encountered anything like this. I'm stumped....
Verilin said:
OK, did all that successfully, when it went back to stock stiil had the same issue. Mobile data functions, mobile network for calls/SMS doesn't. Did the whole update prl/profile and even tried reactivating from settings, still nothing. Was able to install custom recovery (Philz) and the hltespr CM11 variant instead of the unified generic version. Still has the same problem, mobile network not available. Everything else works perfectly. I did verify in settings that it still wound up as the NH7 after everything I did. Note I did a full reset before each thing that got flashed in this process, and one more for good measure after. Let it boot to the system between steps too.
Lol I've been rooting and switching between ROMs for years and have never encountered anything like this. I'm stumped....
Click to expand...
Click to collapse
Dumb question but are you a Verizon customer or Sprint?
Sent from my SM-G900P using Tapatalk
Sprint, I've had big red before but when they did away with unlimited data it wasn't worth paying their high rates.
Bump!
Anyone have any ideas on this? I am just confounded as to why this continues even after being reset to stock.
Same Issue!!!
I have the exact same issue and have been trying to resolve it for the last 2 days... Did you find a solution?
I have the same problem on a Samsung Mega. LTE and 3G data work but phone won't dial if LTE is active. It WILL voice dial if only 3G is active. Sprint. CM11.
I had this problem after flashing ROMs as well, but went into Settings>Connections>More Networks>Mobile Networks>Network Mode and selected LTE/CDMA....no network had been selected. That fixed me right up. Weird part is, I could still avcess the web without WiFi....but couldn't make calls or ise my bluetooth headset until I had performed the above steps. Hope that helps.
thanks forget the little things reset wifi and sprint cell extender
GAPO said:
I had this problem after flashing ROMs as well, but went into Settings>Connections>More Networks>Mobile Networks>Network Mode and selected LTE/CDMA....no network had been selected. That fixed me right up. Weird part is, I could still avcess the web without WiFi....but couldn't make calls or ise my bluetooth headset until I had performed the above steps. Hope that helps.
Click to expand...
Click to collapse
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.
Hey guys
I need some guru help here :/
I've flashed cyanogenmod 13 with android 6.0.1 on my i9300 along with some gapps (stock version). Everything works well, besides the cell reception.
I've been able to see other networks around but couldn't connect to neither of them. (i'm on roaming, in germany, while my sim card and the phone are from poland)
I have applied no signal fix from here which didn't change anything.
Then I've flashed this (the one with "Poland" next to it), but that only made things worse, as the whole "cellular network" menu in settings is greyed out.
What I've figured out is that when typing *#06# the phone app makes some noise and hangs, and in the settings there is no IMEI number.
This leads me to the conclusion that EFS (seems empty in the TWRP file browser) is broken/cleared.
I've seen many instructions on bringing it back to life, non of them are clear to me, and all use Windows. Is there a way to do that on Mac OS, or.. basically is it THE way to go for?
I would appreciate all the help as I need that phone in the next days :/ thanks!
@krecio4:
1. Look for efs-backup. Some kernels create this. Or as part of TWRP-backup. Restore it.
2. Flash latest firmware with Odin. If IMEI is still gone afterwards, try KIES repair function.
3. Let it repair in service center.
rp158 said:
@krecio4:
1. Look for efs-backup. Some kernels create this. Or as part of TWRP-backup. Restore it.
2. Flash latest firmware with Odin. If IMEI is still gone afterwards, try KIES repair function.
3. Let it repair in service center.
Click to expand...
Click to collapse
thanks a lot @rp158!
I've tried searching for an efs backup but no luck :/ any idea where do they create it? restore option only has those files that I've backed up.
latest firmware you mean the official one, right? Is there a way to do it on mac os?
cheers
@krecio4: TWRP backup contains efs-partition, if you chose/ticked it. Kernels (Boeffla, Agni) store it in sdcard0, but if you never flashed a special kernel, it's over.
Firmware means Samsung's stock 4.3 from sammobile.com. Look there, if they offer Odin and KIES for Mac. Otherwise lean a Windows pc. It's useless to make it more complicated by struggling software.
@krecio4: read this. That's not the solution, but if that all caused by actual CM13-nightly, there comes perhaps any...
I have the same problem with latest nightly. This work fine: "cm-13.0-20160523-NIGHTLY-i9300.zip".
@krecio4 I think that you have to first flash latest firmware then root your phone and then you have to use z3x box, hope it will fix :good:
thanks for your sugestions guys
What I did is to get the latest firmware from sammobile, restored it with Odin, phone was working, I was receiving calls and texts.
So I installed TWRP, backed up EFS, System, Data, and one more thing that was marked.
Then i did a factory reset and installed latest CM13 + gapps in one run (as a batch of files, selected the CM13 first, than the gapps in the que)
rebooted
Again - CM13 works well, but it says "please insert SIM card" :/
No IMEI, IMEI SV (Unknown)
Cellular networks in settings are off, and greyed out inside, "preferred network type" is "Invalid Network Mode (-1). Ignore"
Do you think there is any hope?
I noticed that EFS is empty, after restoring it from backup, and rebooting, it's empty again.
so tired of everything, I went back to the original software using this method (even easier than Odin) http://forum.xda-developers.com/galaxy-s3/general/how-to-factory-installed-firmware-sgs3-t1838480
If you come up with some solution, I'd love to try Cynanogenmod for longer and.. for real
1. Be happy, that your efs-data are ok. Make in TWRP a backup of this partition only, for worst cases.
2. Try @mexit's advice.
Can I with no problem have a custom recovery installed while using original firmware?
So you are saying that it might be with the last 3 nightlies that they are messing up with backed up EFS? If so, I'll try installing the one you've mentioned, but now I've list 2-3 days for the whole crap so I will wait until I have too much time But thank you very much for your support!
BTW, I found this as well: http://forum.xda-developers.com/galaxy-s3/general/tool-backup-restore-efs-imei-sgsiii-t1901098
Posting for anybody, as I digged the whole internet for any answers
Install this: https://download.cyanogenmod.org/get/jenkins/162926/cm-13.0-20160524-NIGHTLY-i9300.zip
http://forum.xda-developers.com/showpost.php?p=67034195&postcount=5968
Click to expand...
Click to collapse
ok, as I don't give up easily, as you can see, I did another approach. Backup, backp EFS only.
Installed the edition from 23rd of mai. All good! But during the "installing apps" during the initial boot, close to the end, the battery died (after the screen flickering). but reboot and it all seems to work well Any issues that could appear after an unexpected reboot during the first boot? Do you suggest to do factory reset and flash CM13 + gapps again?
If I understand well, battery died during compiling Dalvik/ART. Should be happen again after cleaning both caches. But to avoid any mess, I would clean flash the ROM again.
So you suggest to do the factory reset, install CM13, install gapps, reboot ?
No.
Wipe system, data, cache, Dalvik cache.
Flash CM13. Wipe cache, Dalvik cache.
and gapps installation shouold be along the CM13 in a que right?
@krecio4: flash GApps afterwards. Read the last posts of CM-thread: your problem was probably caused by a modem-bug in CM, should be gone now.
after the wipe cache & Dalvik?
so CM13, wipe, gapps, reboot?
Ok, very precisely:
flash cm13, wipe 2 cashes, reboot
if net and wifi ok, make a backup of this state
flash GApps, wipe 2 cashes, reboot
case closed