Hi all.. I just totally lost radio signal after reverting 4.3 to 4.2.2.
Tried everything like flashing .532 ftf, restoring nand backups (stock, cm10.2, omni 4.4) even factory reset with no result.
The signal bars did exist but in grey with red 'x' over the bars.
Well the solution is re-flash with FlashTool the 14.2.A.0.290 FTF and the radio signal back to normal.
EDIT: Screenshoot attached.
Interesting info. Others have also reported that downgrade to .532 removed their IMEI too.
I wonder, has anyone been able to successfully revert from .590 (4.3) once upgraded?
stiggy2012 said:
Interesting info. Others have also reported that downgrade to .532 removed their IMEI too.
I wonder, has anyone been able to successfully revert from .590 (4.3) once upgraded?
Click to expand...
Click to collapse
I attached the SS on the first post..
Also I noticed that baterry bar sometimes drop fast, also when connected to charger it grow rapidly : (
Still no solution to get out from 4.3 tough, I tried these:
from 4.3 >flash 532 FTF, signal gone
from 4.3 restoring stock .257 nandroid backup > signal gone
from 4.3 >flash CM10.2 > signal gone
Is this solved? If so, please share what you did so other people with the same issue can get help.
i went from from .290 to a CM 10.2 nandroid and lost radio signal... i think it is a baseband incompatibiity, but i restored everything from a .257 FTF except system and kernel, and it was fine after that. i don't think i have lost IMEI at any time tho
lmemma16 said:
i went from from .290 to a CM 10.2 nandroid and lost radio signal... i think it is a baseband incompatibiity, but i restored everything from a .257 FTF except system and kernel, and it was fine after that. i don't think i have lost IMEI at any time tho
Click to expand...
Click to collapse
Restoring everything from .257 FTF from .290? Still stuck with 4.3 here : p
LordManhattan said:
Is this solved? If so, please share what you did so other people with the same issue can get help.
Click to expand...
Click to collapse
Only to get the radio signal back is solved. And to escape from .290 (4.3) > unsolved yet (will try the above method.. still nandroiding)
EDIT:
while on .290 (4.3) I did these:
Stage 1:
I make .290 nandorid backup with this kernel (v5)
http://forum.xda-developers.com/showthread.php?t=2426736
enter CWM recovery (by pressing volume-up while purple LED sign), go to 'advance' and hit 'turn-off'
Stage 2:
FashTool .257 FTF with:
[Wipe Column]
APPSLOG = checked
CHACHE = checked
DATA = unchecked
[Exclude Column]
KERNEL = checked
SYSTEM = checked
others = unchecked
this will make the phone bootlooping with CWM, enter CWM recovery (by pressing volume-up while purple LED sign), go to 'advance' and hit 'turn-off'
Stage 3:
FashTool .257 FTF with:
[Wipe Column]
APPSLOG = unchecked
CHACHE = unchecked
DATA = unchecked
[Exclude Column]
KERNEL = unchecked
SYSTEM = unchecked
others = checked
(this process took longer than stage 2 above)
after done, I reflash this kernel (v5)
http://forum.xda-developers.com/showthread.php?t=2426736
then enter CWM and restore .257 nandroid backup..
Now I am on rooted .257 with fully working radio signal : )
Edit #2:
From rooted 257 I flash Central Europe 290 FTF back (wipe ALL and exclude NOTHING) everything runs smooth.
Then from 290 I flashed back to Europe 257 FTF (wipe ALL and exclude NOTHING), no signal lost and IMEI still there.
Back again to 290, I tried both central Europe (CE) and Singapore (SG) FTF, no more problem.
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
Been trying to flash Cyanogenmod and I hit the wall with a IMIE number that becomes all zeros. I've tried going back to 4.2 and also tried not flashing the baseband. But I can't flash back or install Cyanogenmod without loosing mobile connection.
I'm running generic EU c6833 LTE. Any pointers?
Have a read of this thread http://forum.xda-developers.com/showthread.php?t=2575359, but I think the gist of it is to downgrade to an earlier ftf (.532?) and exclude baseband then flash a recovery boot.ing from the rom then flash the rom...
I think that is it, not tried it though.
I'm not sure why all of the sudden this is such a problem. The issue is that I only have a good signal when in 4G mode. When I'm not in 4G the signal is either extremely weak (1x) or gone completely! When I first flashed MJ9 everything seemed to work fine, this is not he case anymore. I also noticed that when using anything GPS related it goes completely nuts when not on 4G...
What can I do to get my phone to work when I'm not in a 4G area?
I'm running 4.1.2
I605VRAMC3
James Mac said:
"... When I first flashed MJ9 everything seemed to work fine, this is not he case anymore.... I'm running 4.1.2 I605VRAMC3..."
Click to expand...
Click to collapse
So, it sounds like you're on the 4.1.2 build , but you've ODIN'd Beanstown106's MJ9 firmware to update your modem.... and it's not working right anymore?
If you made a full nandroid backup, (including the modem), of your current ROM when it was working without problems, then you might try restoring it to see if that would help.
You could also try reflashing Beanstown106's MJ9 firmware to see if that would help. Or... if you want to try to go back to the VRAMC3 modem, then this link with recovery flashable modems might be helpful : http://forum.xda-developers.com/showthread.php?p=36942418. (It would be a good idea to make a backup of your EFS if you haven't done that yet before starting to mess around with the modem).
Dr. Droidberg gave instructions in this (thread) for flashing the new modem in your custom recovery... He says, "... Download the desired modem...Reboot into recovery...Wipe cache & Dalvik cache...Install modem. If you don't like that one for some reason you can repeat the process to go back or try a different one..."
If all else fails, you could ODIN back to stock 4.1.2 and reroot with Casual to start over again.... hopefully that would fix things.
Good luck! :good:
mattnmag said:
So, it sounds like you're on the 4.1.2 build , but you've ODIN'd Beanstown106's MJ9 firmware to update your modem.... and it's not working right anymore?
If you made a full nandroid backup, (including the modem), of your current ROM when it was working without problems, then you might try restoring it to see if that would help.
You could also try reflashing Beanstown106's MJ9 firmware to see if that would help. Or... if you want to try to go back to the VRAMC3 modem, then this link with recovery flashable modems might be helpful : http://forum.xda-developers.com/showthread.php?p=36942418. (It would be a good idea to make a backup of your EFS if you haven't done that yet before starting to mess around with the modem).
Dr. Droidberg gave instructions in this (thread) for flashing the new modem in your custom recovery... He says, "... Download the desired modem...Reboot into recovery...Wipe cache & Dalvik cache...Install modem. If you don't like that one for some reason you can repeat the process to go back or try a different one..."
If all else fails, you could ODIN back to stock 4.1.2 and reroot with Casual to start over again.... hopefully that would fix things.
Good luck! :good:
Click to expand...
Click to collapse
Thanks for the advice! I just got around to flashing the new modem and it worked great! It's so nice to have service again when I'm at work...
Thanks agian!
James Mac said:
Thanks for the advice! I just got around to flashing the new modem and it worked great! It's so nice to have service again when I'm at work...
Thanks agian!
Click to expand...
Click to collapse
Cool. Glad you got it fixed. :thumbup:
Hey i have a problem my nerwork always give me emergency call only i tried all fix from xda but nothing sloved im back to 4.3 from 4.4.2 ana backup the efs and flash via odin in 4.4.2 still same problem any solution plz help
tareq-hakeem said:
Hey i have a problem my nerwork always give me emergency call only i tried all fix from xda but nothing sloved im back to 4.3 from 4.4.2 ana backup the efs and flash via odin in 4.4.2 still same problem any solution plz help
Click to expand...
Click to collapse
Depends on what you have tried more details/list of what you have tried "all fix" doesn't really help. If not you will get lots of replies from people suggesting things you have already done.
There is what i did:
-Try alot of patched modem
-flash 4.3 stock backup efs then restore in 4.4.2
-tried different custom rom
-changed csc to be compitable with my country BTW i live in middle east
And another thing i select my network manually
tareq-hakeem said:
There is what i did:
-Try alot of patched modem
-flash 4.3 stock backup efs then restore in 4.4.2
-tried different custom rom
-changed csc to be compitable with my country BTW i live in middle east
Click to expand...
Click to collapse
Looks like you have tried all the obvious solutions sorry I can't understand your first post about 4.3 have you connectivity on 4.3 stock rom?
Yes and in 4.4.2 but i get random emergency call only and still no connectivity must restart phone to get network back
tareq-hakeem said:
Yes and in 4.4.2 but i get random emergency call only and still no connectivity must restart phone to get network back
Click to expand...
Click to collapse
If you are getting network/calls in 4.3 without any problems then your efs and modem are correct and have been upgraded to efs v2 unless you are on a patched modem and this is what is making your 4.3 rom work . If you are getting partial calls/internet in 4.4.2 but then have to reboot then something else is going on.Are you sure your apn settings are correct for you region? If they are then I am at a loss to what's going on,the patched modems and kernels that are in the forum are for 4.3 roms only not 4.4 so are you on a patched modem and kernel at the moment?maybe that's interfering with 4.4.
Try another sim card.
Thx for help still happening to me
If this error is happening on totally stock 4.3, before you install or restore any settings or apps, but works normally sometimes then it's probably a hardware failure.
Now im using back to noot v5 it seem the problem is fixed i donno
hello,
I have a problem with my s6edge. From the moment i got it, the phone was lagging, halting, restarting, loosing signal randomly. I thought an update would fix it so I updated OTA to mm6.0.1. but this didn't worked as expected. I remeber that when it was installing the new android, the progress bar stopped somewhere at 1/3 and the phone rebooted and then the status "erasing..." appeard. After it finished the update, I did a factory reset and then, after restart, i found that there was no network. I cheked the baseband: unknown imei: null. I think the EFS partition is corrupted. Since then I tried the following: flashing with odin [ap] different stock roms from 5.11 to 6.01 from different carriers in my region. No luck. I even tried to flash [cp] only modem.bin. Every time I flash a new rom, and I go to recovery, a broken android appears. If i restart and go again to recovery, it goes to recovery as it should go without the error.
I also mention that the phone was not rooted. I running now 5.1.1 G925FXXU3COI9_G925FOXX3COJ1.
What can I do to get back both imei and baseband? Any help will be greatly appreciated. 10x.
It's still in warranty and you've not messed it up. Get them to solve. Sounds like main board is dodgy with the signal issues
it would've been so easly.
unfortunatly, this is not an option. the legal owner is a friend witch is not in the country right now.
Now it runs latest 6.01 very smoothly (the lagging and halting are gone, with no errors at recovery) after I flashed the PIT file along with the rom with repartition enabled, but still, Imei is Null and Baseband is Unknown
Any sugggestions? 10x.
I can't belive I have to go to samservice with this problem witch i think it has a very easy solution....
Can you teach me how to flash along with pit file?? Please thanks in advance
any good news know? I would like to know that man
ferdeenandxda said:
any good news know? I would like to know that man
Click to expand...
Click to collapse
this worked for me
https://www.youtube.com/watch?v=TzGJDHmKx4o