[Q] baseband unknown, trying to downgrade rom - T-Mobile Samsung Galaxy S II SGH-T989

Hey guys, so I finally decided to go back to a stock rom for the t989 (4.1.2)
i downloaded tiberus for the kernel
uvmc6 stock for the rom via this thread <<is that even a legitimate stock? i'm not sure because that's the only one i could find that doesn't seem to be tampered with.
and uvmc6 for the radio
for some reason, after flashing, everything works great but i have no signal. the baseband in the "about phone" reads "unknown"
I don't know what i did wrong because it seems like I did everything right by getting the same version, kernel and radio for it but it's still not working.
even tried going to an earlier radio but still no success.
can someone tell me if i'm missing a step? did i do something wrong? can i even downgrade (specifically coming from this ROM and i want to go back to stock)

I am facing the exact same issue. Can anyone please share any pointers. Thanks so much.
umchriswho said:
Hey guys, so I finally decided to go back to a stock rom for the t989 (4.1.2)
i downloaded tiberus for the kernel
uvmc6 stock for the rom via this thread <<is that even a legitimate stock? i'm not sure because that's the only one i could find that doesn't seem to be tampered with.
and uvmc6 for the radio
for some reason, after flashing, everything works great but i have no signal. the baseband in the "about phone" reads "unknown"
I don't know what i did wrong because it seems like I did everything right by getting the same version, kernel and radio for it but it's still not working.
even tried going to an earlier radio but still no success.
can someone tell me if i'm missing a step? did i do something wrong? can i even downgrade (specifically coming from this ROM and i want to go back to stock)
Click to expand...
Click to collapse

umchriswho said:
Hey guys, so I finally decided to go back to a stock rom for the t989 (4.1.2)
i downloaded tiberus for the kernel
uvmc6 stock for the rom via this thread <<is that even a legitimate stock? i'm not sure because that's the only one i could find that doesn't seem to be tampered with.
and uvmc6 for the radio
for some reason, after flashing, everything works great but i have no signal. the baseband in the "about phone" reads "unknown"
I don't know what i did wrong because it seems like I did everything right by getting the same version, kernel and radio for it but it's still not working.
even tried going to an earlier radio but still no success.
can someone tell me if i'm missing a step? did i do something wrong? can i even downgrade (specifically coming from this ROM and i want to go back to stock)
Click to expand...
Click to collapse
Not sure about the rom you linked, it's not official stock is about all I can see just from the filename.
If you really want to go back to official stock 4.1.2 ROM, then you need to download either one of these, this is for T-mobile/T989 or this is for Telus/Koodo/T989D
Either of those I linked are flashed through Odin in Download mode. unpack and flash in Odin, If you need a re-fresher on how to use Odin check here, at Step 9 just replace that with the rom you downloaded/unzipped.

Related

Is it dangerous to downgrade from NFSFAN GPS rom to original Bell Rom?

I've read on the other site that its dangerous
http://forum.ppcgeeks.com/showthread.php?t=26082
I have NFSFAN Latest rom with GPS, I want to go back to the original bell rom because bell world said they can't change my cell phone number with the custom rom.
Thanks
I have done it so many times......nothing hard nor dangerous.
Just use the latest bell firmware (with the GPS) and flash it.....
xeongx said:
I've read on the other site that its dangerous
http://forum.ppcgeeks.com/showthread.php?t=26082
I have NFSFAN Latest rom with GPS, I want to go back to the original bell rom because bell world said they can't change my cell phone number with the custom rom.
Thanks
Click to expand...
Click to collapse
Hmm sounds kinda weird, I don't see why the need the stock bell ROM to change your number. Just re flash it with the bell ROM, go get it changed, then flash your custom ROM back. Just don't try to return your phone until you have downgraded the bootloader and flashed the stock bell ROM, but in your situation it does not sound like there is a need to downgrade.
just make sure that the Official Bell Rom has the 3.xx Radio or more,, and you will be fine.
Well I flashed to NFSFAN's ROM hand had nothing but trouble after that. Now, to be honest I couldn't say if it was the ROM or the flashing that caused the problem, as I unlocked as I was supposed to first, but I could not reflash back to OEM after that using active sync, I had to do it from the storage card. And now after trying it yet once again, my phone shows No Service...
So I would say that your mileage may definitely vary... I'd say if you're able to downgrade to the Bell 3.09.666 ROM from activesync you should be fine.
Keep us posted!

[Q] HELP!!

Hello everyone i have an galaxy s3 at&t version and i was trying to install a rom and the rom said it needed a certain bootloader so i download it and flash it and now my phone won reconize my sim or network state nor imei and i need help please !!!
!!!!!
ive tried odin and try reflashing back to stock but odin failed
ImJusDatGuy said:
Hello everyone i have an galaxy s3 at&t version and i was trying to install a rom and the rom said it needed a certain bootloader so i download it and flash it and now my phone won reconize my sim or network state nor imei and i need help please !!!
!!!!!
Click to expand...
Click to collapse
Definitely more info needed.
What ROM is on your device?
What bootloader did you install?
What modem/baseband/radio is on your device?
What method did you use to try to install the bootloader?
Is your phone still showing the correct IMEI in settings or 0 ? (Compare between that shown in settings and under the battery.)
It may be as simple as updating your modem, but I/we can't tell yet.
dawgdoc said:
Definitely more info needed.
What ROM is on your device?
What bootloader did you install?
What modem/baseband/radio is on your device?
What method did you use to try to install the bootloader?
Is your phone still showing the correct IMEI in settings or 0 ? (Compare between that shown in settings and under the battery.)
It may be as simple as updating your modem, but I/we can't tell yet.
Click to expand...
Click to collapse
the rom i have at the moment is the restored verison of the rooted rom i have which is stock 4.1.1 with root
the bootloader i install is I747UCUEMJB
my phone says baseband verison is unknown
i install the bootloader through cwm
the imei is unknown also my phone number to and network and roaming says not roaming mobile network state is disconnected.
everything is messed up thanks for the quick reply man i need help.
ImJusDatGuy said:
the rom i have at the moment is the restored verison of the rooted rom i have which is stock 4.1.1 with root
the bootloader i install is I747UCUEMJB
my phone says baseband verison is unknown
i install the bootloader through cwm
the imei is unknown also my phone number to and network and roaming says not roaming mobile network state is disconnected.
everything is messed up thanks for the quick reply man i need help.
Click to expand...
Click to collapse
I'm new at this, in fact I have flashed by old Captivate several times but yet to flash my SGS3. Anyhow, I have spent many hours reading. Before doing anything I suggest, read, and read some more.
Don't flash back to 4.1.1 or 4.1.2 at this point. They will install an older bootloader than is currently on your phone. From what I have read, you narrowly escaped bricking your phone. You might want to read some of the threads regarding the 4.3 stock ROM and unbricking before making any changes in restoring your device.
You can probably fix this by flashing the modem that goes with the 4.3 series ROMs. It would also be the MJB flavor, although the MJ2 would probably work. Several of the 4.3 TouchWiz ROMs in the development forum have download links for the MJB modem. I would guess you were probably going to install one of them. I would recommend flashing the modem to see if that solves your issues before going ahead with the ROM flash.
dawgdoc said:
Definitely more info needed.
What ROM is on your device?
What bootloader did you install?
What modem/baseband/radio is on your device?
What method did you use to try to install the bootloader?
Is your phone still showing the correct IMEI in settings or 0 ? (Compare between that shown in settings and under the battery.)
It may be as simple as updating your modem, but I/we can't tell yet.
Click to expand...
Click to collapse
dawgdoc said:
I'm new at this, in fact I have flashed by old Captivate several times but yet to flash my SGS3. Anyhow, I have spent many hours reading. Before doing anything I suggest, read, and read some more.
Don't flash back to 4.1.1 or 4.1.2 at this point. They will install an older bootloader than is currently on your phone. From what I have read, you narrowly escaped bricking your phone. You might want to read some of the threads regarding the 4.3 stock ROM and unbricking before making any changes in restoring your device.
You can probably fix this by flashing the modem that goes with the 4.3 series ROMs. It would also be the MJB flavor, although the MJ2 would probably work. Several of the 4.3 TouchWiz ROMs in the development forum have download links for the MJB modem. I would guess you were probably going to install one of them. I would recommend flashing the modem to see if that solves your issues before going ahead with the ROM flash.
Click to expand...
Click to collapse
Could you provide an link by any chance please i dont want to install anything wrong and btw im on jb 4.1.1 do i need to install a 4.3 rom also ? or ?
ImJusDatGuy said:
Could you provide an link by any chance please i dont want to install anything wrong and btw im on jb 4.1.1 do i need to install a 4.3 rom also ? or ?
Click to expand...
Click to collapse
The reason I didn't put a link in the previous posts was to get you to read about what you were doing as you searched for the modem. I am offering advice on things I have yet to experience on this device and only speaking second hand. My advice is only based on what I have read not on anything I have had to correct myself.
In truth I think you just stopped too soon in the process of what you were doing earlier. You said you installed the 4.3 bootloader in preparation to installing a 4.3 or later ROM that required the up to date bootloader. You didn't mention installing the current modem/baseband. You didn't mention trying to flash whatever ROM you had been considering.
You may be able to correct your device simply by installing the 4.3 modem. HERE is the modem thread, it is in the General Forum for our device. Make sure you pick the correct one. I don't know if your device will work well on the MJB bootloader and modem with a 4.1.1 ROM, from something I seem to recall reading I suspect it will.
Take this in steps. Install the correct modem, the one that matches your bootloader. See if that corrects you sim, data, and IMEI problems. If it does correct the issues, the next step is to decide if you want to stay on the 4.1.1 ROM or change to whatever ROM you had been considering. If you decide to change, make backups first. If it doesn't fix the problem while on 4.1.1 you may want to flash the version of the official 4.3 ROM enewman17 has provided on the development thread.
Take it one step at a time. Read about what you are about to do until you understand it well, all before doing anything. Make backups sequentially as you make each corrective step.
HTH.
dawgdoc said:
The reason I didn't put a link in the previous posts was to get you to read about what you were doing as you searched for the modem. I am offering advice on things I have yet to experience on this device and only speaking second hand. My advice is only based on what I have read not on anything I have had to correct myself.
In truth I think you just stopped too soon in the process of what you were doing earlier. You said you installed the 4.3 bootloader in preparation to installing a 4.3 or later ROM that required the up to date bootloader. You didn't mention installing the current modem/baseband. You didn't mention trying to flash whatever ROM you had been considering.
You may be able to correct your device simply by installing the 4.3 modem. HERE is the modem thread, it is in the General Forum for our device. Make sure you pick the correct one. I don't know if your device will work well on the MJB bootloader and modem with a 4.1.1 ROM, from something I seem to recall reading I suspect it will.
Take this in steps. Install the correct modem, the one that matches your bootloader. See if that corrects you sim, data, and IMEI problems. If it does correct the issues, the next step is to decide if you want to stay on the 4.1.1 ROM or change to whatever ROM you had been considering. If you decide to change, make backups first. If it doesn't fix the problem while on 4.1.1 you may want to flash the version of the official 4.3 ROM enewman17 has provided on the development thread.
Take it one step at a time. Read about what you are about to do until you understand it well, all before doing anything. Make backups sequentially as you make each corrective step.
HTH.
Click to expand...
Click to collapse
i've read this one thread and ive downloaded the modem and the rom ive tried to instal was a kitkat version of quatom v3.3 and it say get prop bootloader and i looked up the error everyone said to update your bootloader and thats how i got into this mess. :'( but thank you bro i really appreciate you took the time out of your day to help me.
ImJusDatGuy said:
i've read this one thread and ive downloaded the modem and the rom ive tried to instal was a kitkat version of quatom v3.3 and it say get prop bootloader and i looked up the error everyone said to update your bootloader and thats how i got into this mess. :'( but thank you bro i really appreciate you took the time out of your day to help me.
Click to expand...
Click to collapse
thanks man for telling me what was wrong your an amazing human being and i love you (no homo) and thanks again a million thanks bro.
Did that modem fix some of the problems?
If your on 4.1.1 shouldn't you flash the DKL3 version or can't you just flash thru Odin the DLK3 stock ROM thru Odin Amd start all over again
I've been on 4.3 with that bootloader Amd have flashed back to 4.1 back to the baseband version DLK3 firmware. I would think being on 4.1 you should be able to reflash using Odin to fix the issue or flash the modem for 4.1 .

[Q] Not registering on Network / Wrong IMEI after flashing stock 4.3

Hi, I have just flashed Rooted Note 2 on 4.3 to the latest stock ROM which I downloaded from the SamMobile and now it will not register on the network.
The new version I flashed was the same as the old as i found it with the CSC N7100BTUEMK2 on sam mobile.
I checked the IMEI and it says 00499010640000 in status menu which is different from the one under the battery.
I did not perform a backup of anything as I was not worried about losing any data.
Any ideas what has happened to it and how to get the IMEI correct again?
I understand this is something to do with an efs file but in what way it has become faulty from flashing the same rom I cannot decipher
Any help much appreciated! :good:
stevelav said:
Hi, I have just flashed Rooted Note 2 on 4.3 to the latest stock ROM which I downloaded from the SamMobile and now it will not register on the network.
The new version I flashed was the same as the old as i found it with the CSC N7100BTUEMK2 on sam mobile.
I checked the IMEI and it says 00499010640000 in status menu which is different from the one under the battery.
I did not perform a backup of anything as I was not worried about losing any data.
Any ideas what has happened to it and how to get the IMEI correct again?
I understand this is something to do with an efs file but in what way it has become faulty from flashing the same rom I cannot decipher
Any help much appreciated! :good:
Click to expand...
Click to collapse
From my experience:
1) Reflash the ROM.
2) Flash a custom ROM.
Both worked for me.
N7105 rocking AOSB with AGNi kernel,
Click "Thanks" if I was of any help!
Thanks, I have reflashed the current 4.3 rom UEMK9 and a slightly older UEMK4 with a DEMJ9 radio.
I have tried lots of radios - DM3, XXDME4, XXMI6, XXMJ5, XXMJ2, and some other modem.bin
From what I understand its when you go from newer to older roms that you get IMEI problems, so its prob useless to try pre 4.3
Its all a bit confusing to me and which rom has which radio seems like an arcane mystery.
It is quite possible that I flashed a same version 4.3 rom but my old radio was different and not knowing it was such a minefield on Galaxy phones I never checked that or bothered with a back up.
I may have to resort to paying the people at unlocksamsung online £26 to reset my IMEI
Can anyone tell me, is it just the radio that causes the IMEI problem and should I just trawl through flashing radio zips until my IMEI comes back so I can save the efs file?
BTY everything else seems ok SN is correct and wifi works fine, I just can't get on a network without my correct IMEI
Thx
i also have the same issue on my note 2 gt-n7100 and now phone does no respond to the touch post rooting and all..i am tired of rooting and unrooting the phone like 100 times allready and now my phone is stuck in loop

Wifi problem

okay so I understand that wifi is the kernel problem
and a lot of people are having problem with the wifi after FNE4 update
but so far I've looked around and couldn't find any fix, or one that does not guarantee on an AOSP rom so please help =)
this is what i did
I was on MJB and flashed this 4.4.2 from http://forum.xda-developers.com/showthread.php?t=2788357
however, it did not update my bootloader to NE4, it stayed MJB, and I noticed Wifi wouldn't turn on on stock rom, so I flashed KT Kernel, but it did not fix the wifi problem.
So i thought it was just the stock rom problem, then i flashed PA 4.4.2 rom, which fixed half of the problem... can turn wifi on and off and there are wifi networks, but can't connect (though some time i got lucky and wifi connect, which is rarely)
so any way to fix?
Bumpz
Can you verify your current firmware build? Install terminal emulator and enter this:
getprop ro.bootloader
This will tell you your current base firmware/bootloader version.
Have you considered updating to the full NE4 firmware?
DocHoliday77 said:
Can you verify your current firmware build? Install terminal emulator and enter this:
getprop ro.bootloader
This will tell you your current base firmware/bootloader version.
Have you considered updating to the full NE4 firmware?
Click to expand...
Click to collapse
the current bootloader is FNE4, i just updated it yesterday and no hope either
currently on dpk kernel, Rom is AOSPA 7/9
Really not sure what could be the problem. Maybe this thread will help:
http://forum.xda-developers.com/showthread.php?t=2808654
Its for updating firmware via recovery, but maybe by refreshing it this way could help. Im thinking maybe something got messed up when you originally updated, and if so rewriting known good firmware could help.
Ask in thst thread before flashing though. I haven't looked at the file myself so im not sure if theres something I dont know about since they say to only flash if you're on MJB. If its a simple firmware flash it should be fine though. But like I said, ask first, just to be safe.
DocHoliday77 said:
Really not sure what could be the problem. Maybe this thread will help:
http://forum.xda-developers.com/showthread.php?t=2808654
Its for updating firmware via recovery, but maybe by refreshing it this way could help. Im thinking maybe something got messed up when you originally updated, and if so rewriting known good firmware could help.
Ask in thst thread before flashing though. I haven't looked at the file myself so im not sure if theres something I dont know about since they say to only flash if you're on MJB. If its a simple firmware flash it should be fine though. But like I said, ask first, just to be safe.
Click to expand...
Click to collapse
I already flashed that yesterday, and other than the bootloader/modem changed from MJB to NE4, nothing else changed
and of course still can't connect to any wifi network
i guess i'll pull the last trick.. back to stock and see
since the last time i flashed, even though the rom is tw4.4.2, but the bootloader remained MJB, so this time i'll go back to stock with NE4 and see how it'll go
Probably the best option at this point. Good luck and let me know if that finally solves it!
DocHoliday77 said:
Probably the best option at this point. Good luck and let me know if that finally solves it!
Click to expand...
Click to collapse
well my last ditch fixed the problem.. so it's all about the bootloader/modem with the incorrect rom
So you just flashed the stock rom, right? Thats still really odd. If you feel like continuing you could try flashing a different rom and whatever kernel is supposed to work for WiFi. Sometimes starting over at the beginning is all it takes...
DocHoliday77 said:
So you just flashed the stock rom, right? Thats still really odd. If you feel like continuing you could try flashing a different rom and whatever kernel is supposed to work for WiFi. Sometimes starting over at the beginning is all it takes...
Click to expand...
Click to collapse
indeed it's really odd.. now i'm back on aosp and for some reason, wifi works but sometimes it wouldn't at all.. so im thinking it's the wifi chip or the driver that is damaged..

[Q] Virgin Mobile update to cm11 m11 help

Hey guys. I just got a galaxy s3 from virgin mobile SPH-L710 last week and I managed to install cyanogenmod 11 m10 on it. But to go to cm11 m11 asI've recently learned needs the latest bootloader and baseband.
I know there's two threads in the development section on how to get the latest stock nd8 update.
One had a link to download and open in Odin however the link doesn't seem to be good anymore.
The second thread is for the Odin one click full restore but when I run it it fails on aboot.nbm. I've tried using different USB cables too but it doesn't seem to do any good. Any ideads on how else to upgrade?
I can assure you this is false. I have a Virgin Mobile SPH-L710 on baseband MK5 and I am running a nightly build that is newer than M11 and have no issues.
You should be fine with a dirty flash over M10. Just wipe the cache before flashing.
OK that's intriguing. How did you get MK5 baseband? I just got my s3 last week and its on NF4 which I have no idea where that is in relation to any of the others i've seen around.
I've used the cm updator in settings to try one of the m11 nightlys earlier last week but I had no service so I restored a recovery of m10. Would performing a dirty flash of a nightly build be any different?
Erunur said:
OK that's intriguing. How did you get MK5 baseband? I just got my s3 last week and its on NF4 which I have no idea where that is in relation to any of the others i've seen around.
I've used the cm updator in settings to try one of the m11 nightlys earlier last week but I had no service so I restored a recovery of m10. Would performing a dirty flash of a nightly build be any different?
Click to expand...
Click to collapse
My phone came with MK5 on it, when the phones were shipping with 4.3 installed.
To be honest with you, I would disregard the modem/baseband concerns altogether if I were you. These phones do come with KNOX on them and flashing bootloaders and modems is seriously a huge risk. Flashing a bootloader older than the one you are currently on will trip the killswitch and you will have an irreparable hard brick.
The only time I could possibly think considerations with the bootloader would need to be made is if you were looking to flash a rooted stock TouchWIZ ROM that needed newer bootloaders/modems. But, I really can't speak to that, as I am trying to avoid TouchWIZ and am only familiar with AOSP ROMs.
You may need to flash an APN fix in addition to the ROM and GAPPs. I also use @decimalman's custom kernel, the DKP kernel and have no issues. Basically, when I am clean flashing nightlies the order goes like this:
In PhilZ Recovery found here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
ROM
GAPPs
Kernel
APN fix
Re-Root system for SuperSU
Reboot
I sent you the link for the APN fix, available in another active VM S3 forum, in your inbox. Download and flash the zip and that should fix any service-related issues you're having.
OK I did a clean flash of the latest nightly, flashed the apn fix then booted. Still no service. No apn are on the device nor is it able to save any I manually put in. And settings shows the baseband version as unknown as well as anything else that has to do with cell service.
Erunur said:
OK I did a clean flash of the latest nightly, flashed the apn fix then booted. Still no service. No apn are on the device nor is it able to save any I manually put in. And settings shows the baseband version as unknown as well as anything else that has to do with cell service.
Click to expand...
Click to collapse
And, you tried flashing all of those with the lateat version of PhilZ recovery?
Yes. I tried it with the latest version of philz and flashed all the zips you had listed in order but still the same old issues. However I noticed that WiFi still works. I can also go back to M10 and have no service issues. The other thing im noticing is that CyanogenMod thinks this is a SPH-L710 but apperently its really a SPH-L710T. The difference being that my phone has a tri-band radio for something to do with Sprints Spark.
Erunur said:
Yes. I tried it with the latest version of philz and flashed all the zips you had listed in order but still the same old issues. However I noticed that WiFi still works. I can also go back to M10 and have no service issues. The other thing im noticing is that CyanogenMod thinks this is a SPH-L710 but apperently its really a SPH-L710T. The difference being that my phone has a tri-band radio for something to do with Sprints Spark.
Click to expand...
Click to collapse
When you're on M11, have you checked in system root --> /etc folder to see if the apns-conf.xml is there? You might tru copying that over from the M10 build.
In the meantime, I'll look into the modem a bit more. The CM forum users all seemed to agree on that as a fix.

Categories

Resources