Develop Bugs

[Q] Restoring Radio/Service

Hello,
So I tried flashing a ROM for the first time (Android HD 8.0) and after getting it on my phone, I can't get service on my phone. The baseband, network, mobile network type, phone number, IMEI, and IMEI SV are all unknown (The phone is supposed to be Sprint).
When I tried flashing the ROM with the firmware update.zip that is on the Android HD Revolution page, CWM comes up with the error:
assert failed: getprop("ro.product.device") == "maguro" || getprop("ro.build.product") == "maguro"
E: Error in /sdcard/0/update.zip
(Status 7)
Installation aborted
After this, I tried restoring the radio using the FC12 Radio Images (I reinstalled Android HD and then flashed using this after). It appeared to install correctly, but it still didn't fix the problem.
So what should I do now?

silentdeath113 said:
Hello,
So I tried flashing a ROM for the first time (Android HD 8.0) and after getting it on my phone, I can't get service on my phone. The baseband, network, mobile network type, phone number, IMEI, and IMEI SV are all unknown (The phone is supposed to be Sprint).
When I tried flashing the ROM with the firmware update.zip that is on the Android HD Revolution page, CWM comes up with the error:
assert failed: getprop("ro.product.device") == "maguro" || getprop("ro.build.product") == "maguro"
E: Error in /sdcard/0/update.zip
(Status 7)
Installation aborted
After this, I tried restoring the radio using the FC12 Radio Images (I reinstalled Android HD and then flashed using this after). It appeared to install correctly, but it still didn't fix the problem.
So what should I do now?
Click to expand...
Click to collapse
Sprint 4G? Are you sure the ROM is for your device?
Sprint LTE = toroplus
Verizon = toro
GSM International = Maguro
Swype'ed on my CM10 Galaxy Nexus

Herman76 said:
Sprint 4G? Are you sure the ROM is for your device?
Sprint LTE = toroplus
Verizon = toro
GSM International = Maguro
Click to expand...
Click to collapse
I'm pretty sure. I mean, the rom is listed in the Samsung Galaxy Nexus Development forum, so unless there is a hidden fine print label I'm missing, I don't see why it shouldn't be compatible.
I restored my phone to the stock firmware using odin and managed to get back service, but when I tried to download a second ROM that was specifically for the Sprint version of the galaxy nexus(AOKP), I get two problems. What happens is that the rom gets stuck in boot-up, and the only way to remedy this is to do a factory reset from CWM or any other recovery, but in doing so, I get the same radio problems as before. So now, its more of "Why don't ROMS read/detect/use my radio/baseband correctly?" rather than restoring it.

silentdeath113 said:
I'm pretty sure. I mean, the rom is listed in the Samsung Galaxy Nexus Development forum, so unless there is a hidden fine print label I'm missing, I don't see why it shouldn't be compatible.
I restored my phone to the stock firmware using odin and managed to get back service, but when I tried to download a second ROM that was specifically for the Sprint version of the galaxy nexus(AOKP), I get two problems. What happens is that the rom gets stuck in boot-up, and the only way to remedy this is to do a factory reset from CWM or any other recovery, but in doing so, I get the same radio problems as before. So now, its more of "Why don't ROMS read/detect/use my radio/baseband correctly?" rather than restoring it.
Click to expand...
Click to collapse
That's for the gsm your in the WRONG forum. The one for sprint (toroplus) says SPRINT GALAXY NEXUS ANDROID DEVELOPMENT... Your flashing a rom for a gsm Galaxy Nexus. It will never work
ROMs are not compatible from carriers to carrier only Kernels are. All roms are specific to their device carriers.
Odin back to stock make sure it's all fixed and working and go to the right forum.
Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2

Download a new ROM for sprint (toroplus), factory reset and format system, flash it and you'll be all fixed.

Flash the latest radio(FH05).
Sent from my Galaxy Nexus using xda premium

silentdeath113 said:
I'm pretty sure. I mean, the rom is listed in the Samsung Galaxy Nexus Development forum, so unless there is a hidden fine print label I'm missing, I don't see why it shouldn't be compatible.
I restored my phone to the stock firmware using odin and managed to get back service, but when I tried to download a second ROM that was specifically for the Sprint version of the galaxy nexus(AOKP), I get two problems. What happens is that the rom gets stuck in boot-up, and the only way to remedy this is to do a factory reset from CWM or any other recovery, but in doing so, I get the same radio problems as before. So now, its more of "Why don't ROMS read/detect/use my radio/baseband correctly?" rather than restoring it.
Click to expand...
Click to collapse
You have no business flashing your device. Pretty sure...? You don't even know what you're flashing...? Wow.
*The Ninj-ESS*

If you're meid is unknown you've erased your serial from phone. You're jacked. You need to do a repair.
*The Ninj-ESS*

JediNinjafication said:
If you're meid is unknown you've erased your serial from phone. You're jacked. You need to do a repair.
*The Ninj-ESS*
Click to expand...
Click to collapse
Not necessarily. If mismatching files get flashed to the device it may report unknown or generic as long as the files remain mismatched. If the MEID is visible in stock ROM then at least it's not permanently borked.
Is it possible the OP has been installing custom recoveries for the wrong type of GNex? That could explain why tinkering in recovery causes problems.

I really don't know. I know I'm sitting this one out. Having enough troubles setting up my environment without someone who doesn't take time to pay attention to what doing. Not trying to be rude but someone linked me here. You people really need to start reading and paying attention.
I really don't know much about android when in comparison with others but i do know enough to read and find out what I'm flashing onto my device.
*The Ninj-ESS*

Help - Cannot Find Answer on Flashing t-mobile modem on at&t phone

POSTED IN ANY QUESTION THREAD - CAN DELETE THIS AND PLEASE REPLY TO MY Q THERE THANKS - SAME Q JUST FIGURED EASIER TO POST IT THERE
Have a stock non-unlocked (no unlock) at&t phone with 4.2 android.
Could I use the 4.3 "no-knox" modem.bin I see in these forums that's for t-mobile and just ODIN it over top of the at&t 4.2 modem (mdl modem for at&t that came on the phone when it was purchased) and then use CWM to install a t-mobile rom and have the phone work under t-mobile?

drtechnology said:
POSTED IN ANY QUESTION THREAD - CAN DELETE THIS AND PLEASE REPLY TO MY Q THERE THANKS - SAME Q JUST FIGURED EASIER TO POST IT THERE
Have a stock non-unlocked (no unlock) at&t phone with 4.2 android.
Could I use the 4.3 "no-knox" modem.bin I see in these forums that's for t-mobile and just ODIN it over top of the at&t 4.2 modem (mdl modem for at&t that came on the phone when it was purchased) and then use CWM to install a t-mobile rom and have the phone work under t-mobile?
Click to expand...
Click to collapse
Just because someone else is going to find this thread and start getting ideas...
NO!!!!
No one should EVER do this. Never flash a modem that was not SPECIFICALLY made for your SPECIFIC device.

Skipjacks said:
Just because someone else is going to find this thread and start getting ideas...
NO!!!!
No one should EVER do this. Never flash a modem that was not SPECIFICALLY made for your SPECIFIC device.
Click to expand...
Click to collapse
Ok so tell me please what you mean? Do you mean specific device hardware or ???
Because the only difference I see in the 2 phones, At&t S4 and T-Mobile S4 is all in the software for modem and rom. They are 100% identicle in hardware, even being factory set for bands both carriers use. I would never attempt this on Verizon or Sprint S$'s lol - but I am cinfused other than a different modem bin file and different rom, and different model number since its 2 diff companies, what is the difference?
I am confused.
If I cannot do what I noted, then how does one use an at&t phone on a t-mobile network? I am great at flashing modems, roms, recoveries - but my 1st time switching carriers on an exact same model phone. The phone itself is same model far as samsung makes it - only changes to different model when its branded at&t ot t-mobile and uses that companies rom and mode,m files. But isnt the hardware the exact same both places and couldn't the rom and modem files be swapped to allow it to work on the other one's system?
Please help what I need to do - if I cannot do what I asked about then what?

re: tmobile-att
drtechnology said:
Ok so tell me please what you mean? Do you mean specific device hardware or ???
Because the only difference I see in the 2 phones, At&t S4 and T-Mobile S4 is all in the software for modem and rom. They are 100% identicle in hardware, even being factory set for bands both carriers use. I would never attempt this on Verizon or Sprint S$'s lol - but I am cinfused other than a different modem bin file and different rom, and different model number since its 2 diff companies, what is the difference?
I am confused.
If I cannot do what I noted, then how does one use an at&t phone on a t-mobile network? I am great at flashing modems, roms, recoveries - but my 1st time switching carriers on an exact same model phone. The phone itself is same model far as samsung makes it - only changes to different model when its branded at&t ot t-mobile and uses that companies rom and mode,m files. But isnt the hardware the exact same both places and couldn't the rom and modem files be swapped to allow it to work on the other one's system?
Please help what I need to do - if I cannot do what I asked about then what?
Click to expand...
Click to collapse
If the two phones ATT i337 and Tmobile M919 were as identical as you say they are and even use the same bands then
why is the gsm baseband (modem.bin) and the lte modem (non-hlos.bin) different enough not to be interchangeable?
Not even the STOCK 4.3 firmware or any of the zipfile custom roms here in xda are not identical enough
so we would not need to have two different and separate forums for these two phones.
First thing you need to do is to get your phone on the Tmobile network is to unlock it or have it unlocked.
Then you need to get a tmobile sim card and root the phone if it's not already rooted.
You will also need to flash cf-autoroot to root the phone and then flash a custom recovery like cwm or twrp.
Then last but not least you will need to flash a Tmobile custom rom from the Tmobile M919 forum.
None of the custom roms found here in xda contain modem.bin or hlos-bin images.
Those you already have in your phone will work fine even though they are NOT identical.
The two .bin images are setup so the two networks can establish GSM and LTE communications
between your phone and their towers using different bands and different frequencies.
Good luck.

Misterjunky said:
If the two phones ATT i337 and Tmobile M919 were as identical as you say they are and even use the same bands then
why is the gsm baseband (modem.bin) and the lte modem (non-hlos.bin) different enough not to be interchangeable?
Not even the STOCK 4.3 firmware or any of the zipfile custom roms here in xda are not identical enough
so we would not need to have two different and separate forums for these two phones.
First thing you need to do is to get your phone on the Tmobile network is to unlock it or have it unlocked.
Then you need to get a tmobile sim card and root the phone if it's not already rooted.
You will also need to flash cf-autoroot to root the phone and then flash a custom recovery like cwm or twrp.
Then last but not least you will need to flash a Tmobile custom rom from the Tmobile M919 forum.
None of the custom roms found here in xda contain modem.bin or hlos-bin images.
Those you already have in your phone will work fine even though they are NOT identical.
The two .bin images are setup so the two networks can establish GSM and LTE communications
between your phone and their towers using different bands and different frequencies.
Good luck.
Click to expand...
Click to collapse
Thanks Got her phone working ok. So the key was if unlocked, the at&t phone will work on t-mobile even with an at&t modem file on it I knew the 2 companies could be used on the other's network just did not know the modem file works both ways if unlocked. I assumed the hardware is the same on both phones so just flash a tmobile modem lol - I learned I was wrong thanks for ur help. Years of rooting and never had an issue with using one carrier on another carrier's network, was my 1st time
Thanks a lot for your help. Its working great now!

[Q] T-Mobile branded S3 somehow became AT&T.

When I received my S3, it was on a T-Mobile branded stock firmware 4.1.1. I wanted to try CyanogenMod, so I installed it, but didn't like it.
Here's where my problem begins. Upon wiping my phone back to stock to get rid of CyanogenMod, I find that it's now AT&T branded, despite the physical phone being a T-Mobile T999.
I tried rooting it and using CSC changers, but those tell me that the PreconfigUI is SingleCSC, and thus apparently unchangeable.
What I want to do is somehow get my phone back to T-Mobile branded stock.
P.S. I do not have a MicroSIM yet.

GraphicsApathy said:
When I received my S3, it was on a T-Mobile branded stock firmware 4.1.1. I wanted to try CyanogenMod, so I installed it, but didn't like it.
Here's where my problem begins. Upon wiping my phone back to stock to get rid of CyanogenMod, I find that it's now AT&T branded, despite the physical phone being a T-Mobile T999.
I tried rooting it and using CSC changers, but those tell me that the PreconfigUI is SingleCSC, and thus apparently unchangeable.
What I want to do is somehow get my phone back to T-Mobile branded stock.
P.S. I do not have a MicroSIM yet.
Click to expand...
Click to collapse
Can you go to your phone's settings => about device and check what the firmware settings are? Let's see what you have under firmware version, baseband version & build number. If possible, you may post a screen shot. Did you say you returned to stock by wiping your phone? Hardly seems likely and you would have probably needed to flash some firmware. Would you recall what you flashed?

Thanks for stepping up. My phone's info is:
Android Version is 4.1.1
Baseband is I747UCDLK3
Build is JRO03L.I747UCDLK3
I did not flash any firmware, as I had no reason to.

GraphicsApathy said:
Thanks for stepping up. My phone's info is:
Android Version is 4.1.1
Baseband is I747UCDLK3
Build is JRO03L.I747UCDLK3
I did not flash any firmware, as I had no reason to.
Click to expand...
Click to collapse
It's definitely on AT&T firmware. Apologies if I sound like I'm doubting you but are you certain it had T-Mobile firmware when you acquired it? I'd guess it was probably already an AT&T phone. If you bought it in the secondary market, there could have been some previous repairs involving parts swaps. Your safest bet may be to leave it as is and unlock for you use on T-Mobile. Trying to force on T-Mobile firmware now could result in a brick. As it is on 4.1.1, you can easily free unlock it by following the well tested method you'll find elsewhere in this forum.

No apologies needed. I forgot to state that the phone was purchased with the T-Mobile boot animation and bloatware already present, and that the model number printed below the battery is T999. I've got no clue if there was a parts swap or not. Is the method to unlock that's posted elsewhere that you're referring to the one that begins with you dialing *#197328640#? If so, i've tried it but never got the unlock message to show.

GraphicsApathy said:
No apologies needed. I forgot to state that the phone was purchased with the T-Mobile boot animation and bloatware already present, and that the model number printed below the battery is T999. I've got no clue if there was a parts swap or not. Is the method to unlock that's posted elsewhere that you're referring to the one that begins with you dialing *#197328640#? If so, i've tried it but never got the unlock message to show.
Click to expand...
Click to collapse
There could have been a previous JTag operation involving forced firmware installation on the MB. I've seen previous hybrid firmware involving one or other partition belonging to a different model - e.g. the modem, bootloader or something else but not the complete system.
Yes, that's the unlock method I was referring to. You won't get any confirmation that the process worked at the end. However, if you did it correctly, you would know it worked when you insert a non-compatible SIM card and it works. You should also be able to install T-Mobile apps especially the Wi-Fi calling app which is a really nice feature of T-Mobile.

I'm getting it microSIM'ed tomorrow. I'll see how that goes.
UPDATE: Successfully obtained and installed T-Mobile microSIM. Still wish to replace AT&T boot animation and bloatware with T-Mobile's, though.

GraphicsApathy said:
I'm getting it microSIM'ed tomorrow. I'll see how that goes.
Click to expand...
Click to collapse
OK. I'd be interested in knowing the outcome but I'll be surprised if it isn't unlocked already. Did some further research and there have been some reports of people successfully 'flashing' AT&T firmware on T-Mobile phones, and vice versa. Not sure why this should happen and conventional logic suggests the result should be a hard brick which is indeed the most common outcome. I'll also suggest you boot into download mode and see the information under bootloader. If the device has a T-Mobile bootloader, it may be possible to remove the OS via custom recovery and re-flash T-Mobile firmware.

Download mode currently gives Product Name as SGH-I747. Wiping AT&T OS via custom recovery and then installing the proper one sounds like a good lead. I eagerly await your instruction

GraphicsApathy said:
Download mode currently gives Product Name as SGH-I747. Wiping AT&T OS via custom recovery and then installing the proper one sounds like a good lead. I eagerly await your instruction
Click to expand...
Click to collapse
If download mode info shows secure bootloader enabled, the phone is, to all intents and purposes, now an AT&T phone. Attempting to flash T-Mobile firmware may likely result in a brick which would require a JTag fix. I was hoping download mode would show it still had a T-Mobile bootloader which could have allowed for safe firmware installation but this does not appear to be the case. Likely the motherboard was previously replaced or it suffered a brick and AT&T firmware was JTagged on. Either way, it would be safer to leave it as is.

Bummer. I'll leave it as is then. Thank you for all the help.

[Q] Change baseband version from CA to US on S3 i747

I just bought a Samsung Galaxy S3 i747 from Amazon. It is an unlocked GSM version.
Problem is it has a Canadian baseband version, and I am in the US on AT&T.
I have a problem with data connectivity, and according to Samsung tech support, it is because of the Canadian firmware/baseband version.
Can I change the firmware/baseband version from Canadian build to US build?
If so, how would I do it?
Thank you for any help.

What is the ROM and baseband on your phone? Can you make phone calls?

I could be wrong, but based on my experience with the T999, that shouldn't be working. While flashing a T999V baseband won't hurt it, it simply won't work.
Please tell us your current baseband, current rom, and current firmware build. Enter this in terminal emulator to determine base firmware build,
getprop ro.bootloader
Also, can you verify by the sticker under the battery that it is an I747 and not an I747M?
Sent from my SAMSUNG-SGH-T999 using Tapatalk

DocHoliday77 said:
I could be wrong, but based on my experience with the T999, that shouldn't be working. While flashing a T999V baseband won't hurt it, it simply won't work.
Please tell us your current baseband, current rom, and current firmware build. Enter this in terminal emulator to determine base firmware build,
getprop ro.bootloader
Also, can you verify by the sticker under the battery that it is an I747 and not an I747M?
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Yes, I can make phone calls. I get 4G data connection, but it is slow and keeps dropping, even though it still shows 4G.
If I swap the sim to my old phone, all data connections work great, so I know it's not the sim or the network.
It is in fact an i747M
device name: SGHi747M
Android version: 4.3
Baseband version: I747MVLUEND2
Kernel version: 3.0.31-2140838
[email protected]#1
Sat Apr 12 21:40:34 KST 2014
Build number: JSS15JI747MVLUEND2
SE for Android status: Enforcing
SEPF SGH-I747M 4.3 0029
From getprop ro.bootloader:
I747MVLUEND2
[email protected]
Thanks!

Ok! Everything looks like it should. You could try updating to the 4.4.2 build, but keep in mind you cannot go back to 4 3 afterwards. (You can flash older ROMs but not firmware). And do not flash a 4.4 2 modem on what you are running now.
You can flash the ROMs built for the i747, but for the modem you can only use the I747M.
If the store you got it from told you it was an I747, you might be able to return or exchange it due to incorrect listing.
Sent from my SAMSUNG-SGH-T999 using Tapatalk

DocHoliday77 said:
Ok! Everything looks like it should. You could try updating to the 4.4.2 build, but keep in mind you cannot go back to 4 3 afterwards. (You can flash older ROMs but not firmware). And do not flash a 4.4 2 modem on what you are running now.
You can flash the ROMs built for the i747, but for the modem you can only use the I747M.
If the store you got it from told you it was an I747, you might be able to return or exchange it due to incorrect listing.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Click to expand...
Click to collapse
It was sold as an i747, not i747M, so I will just return it.
The modem is what connects me to the network, so if it remains the Canadian version, changing the firmware won't solve my issue, right?
Thank you for your help!

All I can say on that is you should never flash any firmware that is for any other model device. Its just not safe to do and will almost always cause a hard brick.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
---------- Post added at 05:16 PM ---------- Previous post was at 05:10 PM ----------
So basically, if you're unable to use it as it currently is, I personally think the best option would be to return it and try to get the US I747 model. If you go in and try changing the firmware and it ends up bricking, you'd probably lose the ability to return it, so IMO its just not worth the risk.
Sent from my SAMSUNG-SGH-T999 using Tapatalk

I am going to send it back tomorrow. I don't want to have to flash anything. It should have worked right out of the box, so I'll just return it.
Strange that the Canadian version didn't work as it should. I have an HTC Desire A8182 that is a Telus version, unlocked, and it works just fine on AT&T. No data issues at all. I rooted that one as it only has 100MB internal memory, and I wanted to get rid of bloatware and use Link2SD plus to move apps to the SD card.I didn't use a custom rom, just rooted stock firmware. It's still running 2.2 FroYo, and I love it! It's only 3G, and a tad small, which is why I decided to go with the S3.
Thanks again for your help!

Seemed a little odd to me as well, but there have been a lot of upgrades and enhancements done to many US networks that may not have been done in Canada. Its just a theory, but I747 firmware may have been built to take advantage of that and the I747M might be made to work better with older or just different networks. Kinda hard to explain what I'm thinking here...
Its also possible that the US and Canadian 3g networks are more similar than their 4g ones, which might explain the different experience with your older device.
And then again, you might have simply received a device that had something wrong with it, which you'd want to return anyway I'm sure.
Sent from my SAMSUNG-SGH-T999 using Tapatalk

DocHoliday77 said:
Seemed a little odd to me as well, but there have been a lot of upgrades and enhancements done to many US networks that may not have been done in Canada. Its just a theory, but I747 firmware may have been built to take advantage of that and the I747M might be made to work better with older or just different networks. Kinda hard to explain what I'm thinking here...
Its also possible that the US and Canadian 3g networks are more similar than their 4g ones, which might explain the different experience with your older device.
And then again, you might have simply received a device that had something wrong with it, which you'd want to return anyway I'm sure.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I sent it back today and the seller will refund me when they receive it.
I found an interesting tidbit on the AT&T forum regarding the S3.
"The international edition won't support LTE bands"
Ordered a US version (presumably, lol) today.

How to know the exact version or carrier because a custom ROM replaced it?

I747 sometimes restarts itself and gets stuck on the custom rom boot screen. I have tried multiple ROMs and multiple kernels by now but the problem persists. The only thing that gets it out is that I have to manually remove the battery and put it back in. Also sometimes the WiFi stops connecting and when I try to turn it off and on again, it gets stuck on "WiFi is turning on".
The only thing I want to do now is go back to the original firmware however the because I have a ROM installed, I don't know exactly what the VERSION (the version shown in the settings doesn't match any of these). I also don't remember the exact carrier. Can anyone help regarding this?

Did you make a nandroid backup before installing the custom ROM? If not, I suggest using ODIN to flash the stock NE4 firmware. You can find the NE4 4_file tar file thread in this forum.

StoneyJSG said:
Did you make a nandroid backup before installing the custom ROM? If not, I suggest using ODIN to flash the stock NE4 firmware. You can find the NE4 4_file tar file thread in this forum.
Click to expand...
Click to collapse
No backup at all. I was also thinking of the Odin way however as I mentioned in the post, I can't find a version of the software that matches that on the phone. I also don't know the phone carrier (it is from Canada i747m with 2gb RAM, thats all I know). Is it okay to just do any version of the firmware or do I need a specific version?

Boot into download mode and confirm the model # there.

sCell_ said:
No backup at all. I was also thinking of the Odin way however as I mentioned in the post, I can't find a version of the software that matches that on the phone. I also don't know the phone carrier (it is from Canada i747m with 2gb RAM, thats all I know). Is it okay to just do any version of the firmware or do I need a specific version?
Click to expand...
Click to collapse
If it's an i747m then you need firmware for that model. Firmware for the i747 won't work on i747m.

sCell_ said:
No backup at all. I was also thinking of the Odin way however as I mentioned in the post, I can't find a version of the software that matches that on the phone. I also don't know the phone carrier (it is from Canada i747m with 2gb RAM, thats all I know). Is it okay to just do any version of the firmware or do I need a specific version?
Click to expand...
Click to collapse
If it's a Canadian i747m, it may be a Telus, Bell, Rogers, [email protected], or SaskTel phone. Check the back --- oh wait, Telus doesn't have custom backs (I have a S3 from Telus).
It doesn't matter what VERSION, it matters what MODEL it's for. I could flash CM10 and it would run, BUT it has to be for the EXACT SAME DEVICE! (d2can if you wanted to know.)

Rogers, Telus, bell, fido, Koodo all use the same stock base rom with slight customization for each carrier. You can install the rogers rom to a Telus phone and bell phone. I've done this many times.