So I had CM11 working flawlessly on my phone but I was going to switch to T-Mobile and the phone can't be unlocked from AT&T unless it's a stock rom. So last night I looked up how to flash it back to stock through Odin and that failed (Loading I747UCDLK3) so then I followed a method posted by Mrhayley30705 (http://forum.xda-developers.com/showpost.php?p=46954804&postcount=119) and that still didn't work. Now I'm stuck at a firmware screen that tells me the firmware upgrade encountered an issue. Kies doesn't do anything for me and when I try to use heimdall to re-flash the recovery.img it tells me "ERROR: Failed to access device. libusb error: -12".
I spent about four hours reading and looking different things up but I can't find anything. I don't care about any of the warranty counts or data stored on the phone I just need it back up and running, either stock or CM11 like I had. I can still access the download mode. I would really appreciate any help!
Can you boot into download mode and have access to a Windows machine? If you do, use Odin to flash Philz Touch for the d2lte and see if you can boot into recovery. If you can boot into recovery, copy CM11 back onto your phone to make sure if can boot to the phone's desktop and get a signal.
Once that works, try this thread to flash back to stock 4.3 (assuming you never had stock 4.4 on your phone): http://forum.xda-developers.com/showthread.php?t=2540998
I just got to class but I will try this when I get home and let you know the results!
Okay so I managed to get Philz on there, got into recovery and did a reset/wipe, reinstalled CM and I'm up and running but I've got no service. I appreciate the help so far!! This is great!
Okay so upgrading to the CM nightly I was using prior to this it restored basically everything except the IMEI which is preventing me from getting service.
So the digitizer works? What is the baseband on your phone? Do you have an imei #?
audit13 said:
So the digitizer works? What is the baseband on your phone? Do you have an imei #?
Click to expand...
Click to collapse
Phone works fine from what I can tell, outside of not getting a signal it's back to the way it was before I even started playing with it. Baseband is Unknown and my IMEI # is blank.
http://forum.xda-developers.com/showthread.php?t=1784877 I was going to test that, will that help?
Lesson learned, don't mess around with this stuff unless I learn more about it..
The link is not for the ATT s3, it is for the T-mobile version so I would not follow that guide.
Try flashing an older version of CM like 10.2. If you still don't have an imei or baseband, you may need to reflash the mjb bootloader and modem.
audit13 said:
The link is not for the ATT s3, it is for the T-mobile version so I would not follow that guide.
Try flashing an older version of CM like 10.2. If you still don't have an imei or baseband, you may need to reflash the mjb bootloader and modem.
Click to expand...
Click to collapse
I just tried to install 10.2 and it tells me it failed, (Status 7) it spammed a bunch of getprop("ro.bootloader") == I747(then a bunch of different letters for each one). I'm assuming that means I need to reflash the mjb bootloader and modem?
You may need to reflash to the mjb bootloader and modem in order to get your imei back.
Do you by chance have a link to the proper one that I need to install? The one I found shows 4.3 but says it will brick my phone if I'm trying to downgrade from 4.4.
It also seems I have no sound either.
Once you have a 4.4 bootloader on your phone, you cannot flash back to a 4.3 or 4.1 bootloader.
Do you have terminal emulator on your phone? If you do, run this in a terminal window: getprop ro.bootloader (you need the spaces and press enter).
audit13 said:
Once you have a 4.4 bootloader on your phone, you cannot flash back to a 4.3 or 4.1 bootloader.
Do you have terminal emulator on your phone? If you do, run this in a terminal window: getprop ro.bootloader (you need the spaces and press enter).
Click to expand...
Click to collapse
I747UCUFNE4 is the response it gave.
You have a 4.4 bootloader.
http://www.sammobile.com/2014/06/18...to-att-and-canadian-variants-of-galaxy-s-iii/
Did you try flashing a stock KK ROM?
http://forum.xda-developers.com/galaxy-s3-att/general/modem-4-4-2-modems-i747-i747m-t2856577
I didn't, I'll give that a try now!
It worked! Yaaaaaaaaaaaaaay. I love you!!
DextarRogue said:
It worked! Yaaaaaaaaaaaaaay. I love you!!
Click to expand...
Click to collapse
Excellent :highfive:
What did the trick? Updating the modem or flashing a new KK ROM?
It's important to share your knowledge with other XDA members.
So I followed the Philz recovery from Download mode through Odin, then through that recovery I installed CM11, booted the phone, upgraded to the newest CM nightly then I grabbed the modem, adb pushed it to the phone in recovery, installed the zip and boom! IMEI is back as is calling. Signal continues to be really low but it's always been like that!
Related
I was on CM 10.2.1
I upgraded to CM11 - I get no wireless data. My phone works but I have no APNs and I could not add them.
I tried SlimKat 9.0 same issue with the APN
I upgraded my CWM to 6.4.0.7 as I heard that caused issues when upgrading to CM11.
I bought Mobile Odin and flashed that way as I thought it might help.
Ive done the following to fix my APN
1) Loaded an old one from working CM 10.2.1
2) Run Root Tweak with the fix APN for CM11 checked
3) Done the airplane mode trick
4) Attempt to add one manually
Does anyone know why this is happening and more importantly how to correct this issue?
Yes I did pore through other threads on how to fix this but no avail.
Thank you
What is your bootloader and modem? Do you get data if you re-install your previous ROM?
audit13 said:
What is your bootloader and modem? Do you get data if you re-install your previous ROM?
Click to expand...
Click to collapse
Bootloader = I747UCDLK3
Modem = I747UCDLK3
Yes I get data when I load a backup of CM 10.2.1
Thanks
Data does not work on ROMs beyond cm10.2 because your bootloader and modem to too old.
I recommend flashing back to stock 4.1.1, sim unlock your phone if it is not already sim unlocked, and run OTA updates to at least 4.3, then install recovery and CM11.
audit13 said:
Data does not work on ROMs beyond cm10.2 because your bootloader and modem to too old.
I recommend flashing back to stock 4.1.1, sim unlock your phone if it is not already sim unlocked, and run OTA updates to at least 4.3, then install recovery and CM11.
Click to expand...
Click to collapse
Thanks for the quick reply. That sounds hard. From what I'm reading going back is treacherous.
So these are the steps.
1. Load this firmware via ODIN -> I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.zip -- What about gapps? Is that in this zip?
2. Run triangle away. (Do I need to do this?)
3. Contact my carrier to unlock my sim. (If this is carrier unlocking ie taking my att phone to Sprint etc, why is this needed?)
4. Get OTA updates. Will this come automagically because I'm on 4.1.1 and does it matter if my flash counter is gt 1?
5. Root phone via Odin with this file CF-Auto-Root-d2att-d2uc-samsungsghi747.tar.md5.
6. Install CWM if it went away when I went back to firmware - Of course it would because I'll factory reset my phone in step 1.
7. Flash away to a 4.4.4 Rom
Did I miss anything?
Step 4 is the one that scares me -- That one is out of my control. Either I get the OTA or I dont. Anyway I can "request" the OTA?
Thanks again
Be Well
From your custom ROM, run triangle away to reset counter and change things back to official.
Now flash back to stock 4.1.1 using Odin. If your phone does not boot, you need to get into recovery, do a factory reset, and reboot the phone and go through the set up routine.
After loading stock 4.1.1, do this to sim unlock your phone for free: http://forum.xda-developers.com/showthread.php?t=2529200. If you have a code from ATT, you must be running a stock ROM or a custom ROM that is based on a stock Samsung ROM in order to enter the unlock code.
You must be on a stock ROM in order to take OTA updates. OTA updates are the safest way to obtain an updated bootloader and modem.
After updating to 4.3, you cannot downgrade the bootloader as doing so may brick the phone.
The choice is yours in terms of what you want to do. As you found out, some ROMs will not function properly without an updated bootloader and modem. Mixing modem and bootloader versions may also result in a bricked phone.
audit13 said:
From your custom ROM, run triangle away to reset counter and change things back to official.
Now flash back to stock 4.1.1 using Odin. If your phone does not boot, you need to get into recovery, do a factory reset, and reboot the phone and go through the set up routine.
After loading stock 4.1.1, do this to sim unlock your phone for free: http://forum.xda-developers.com/showthread.php?t=2529200. If you have a code from ATT, you must be running a stock ROM or a custom ROM that is based on a stock Samsung ROM in order to enter the unlock code.
You must be on a stock ROM in order to take OTA updates. OTA updates are the safest way to obtain an updated bootloader and modem.
After updating to 4.3, you cannot downgrade the bootloader as doing so may brick the phone.
The choice is yours in terms of what you want to do. As you found out, some ROMs will not function properly without an updated bootloader and modem. Mixing modem and bootloader versions may also result in a bricked phone.
Click to expand...
Click to collapse
To stick with 10.2 or not to that is the question. Everytime I flash or do anything like this on my phone - I get a small lump in my throat knowing I'm dancing in the razors edge of bricking it.
I know how you feel, but I've done it enough times and just accept the fact that I may brick the phone. Jtag service would cost me around $75 so I'm willing to take the chance. I'd be less willing if the phone still has warranty.
Flashing back to stock and running OTA updates is the safest route.
If you don't sim unlock while on stock 4.1.1 and you want to sim unlock your phone in the future, you will need to be on a stock or virtually stock ROM in order to enter the unlock code.
Used ODIN to go back to stock 4.1.1.
Got the OTA update to 4.3
I have my MMS and cellular data back
I'll stick on stock, unrooted 4.3 for a minute.
I should be available to root and update to CM11 or SlimKat or any 4.4 rom whenever I so desire and still keep cellular data.
My baseband is I747UCUEMJB. How can I find out my bootloader and modem versions on UNROOTED device?
Your help is much appreciated and your instructions were flawless.
ddunleavy2 said:
Used ODIN to go back to stock 4.1.1.
Got the OTA update to 4.3
I have my MMS and cellular data back
I'll stick on stock, unrooted 4.3 for a minute.
I should be available to root and update to CM11 or SlimKat or any 4.4 rom whenever I so desire and still keep cellular data.
My baseband is I747UCUEMJB. How can I find out my bootloader and modem versions on UNROOTED device?
Your help is much appreciated and your instructions were flawless.
Click to expand...
Click to collapse
In a terminal or adb shell you can enter this to check your bootloader:
Code:
getprop ro.bootloader
In a terminal or adb shell you can enter this to check your modem (should match the baseband your phone reports in About):
Code:
getprop gsm.version.baseband
I don't believe either of these commands require root unless stock has getprop locked down tighter that AOSP ROMs; I just entered them in a user shell.
There are a couple of firmware updates for your device beyond MJB, NE4 and NJ1. Some users, myself included, had GPS problems that were a bit of a pain to fix on newer 4.4 AOSP based ROMs with the MJB firmware, but data was ok with MJB. Also, you'll need newer firmware if you decide to test drive the lollipop alphas that are floating around. There are custom recovery flashable firmware updates on XDA from a trusted developer if you decide you need that, or you might want to take a couple more OTAs if you're more comfortable going that route. You're already on MJB so there's no going back
The terminal worked
Bootloader and baseband = I747UCUEMJB
What???? I might need more updates for all the roms out there.....ugggh.
"There are custom recovery flashable firmware updates on XDA from a trusted developer if you decide you need that, or you might want to take a couple more OTAs if you're more comfortable going that route."
If I decide to use these flashable firmware updates on XDA from a trusted developer or OTA its same as this: going forward and NEVER going backward when getting firmware updates?, yes?
yes. downgrading bootloader will almost certainly cause a brick.
"all i can really do , is stay out of my own way and let the will of heaven be done"
---------- Post added at 10:09 PM ---------- Previous post was at 10:07 PM ----------
audit13 said:
Data does not work on ROMs beyond cm10.2 because your bootloader and modem to too old.
I recommend flashing back to stock 4.1.1, sim unlock your phone if it is not already sim unlocked, and run OTA updates to at least 4.3, then install recovery and CM11.
Click to expand...
Click to collapse
+1
"all i can really do , is stay out of my own way and let the will of heaven be done"
You guys are on point.
Last night I received another OTA to 4.4.2.
Baseband now at NE4.
Thanks again for taking the time to answer all this -- Really really appreciate it.
EDIT: Can I still use this to root my phone via ODIN or is there a different process for this baseband?
CF-Auto-Root-d2att-d2uc-samsungsghi747.tar.md5
I load this into ODIN, plug my phone in download mode and root away. Does either the file I use change or do I have to use something other than ODIN?
Thanks again
To get root, I would flash a custom recovery and flash supersu from recovery, then let supersu disable know.
The file you named looks to be outdated as it refers to the s3 as d2att. Since unified builds were released, the s3 is now referred to as the d2lte.
I have ROM Manager installed. It has an option to "Flash Clockworkmod Recovery". I just tried it and it failed and I think thats because I dont have root. In the past I've had to root my phone via ODIN, then flash custom recovery then MOD away.
In the past I rooted the S3 via ODIN. With this new 4.4.2 version do I still root via ODIN provide I find the correct file because -> CF-Auto-Root-d2att-d2uc-samsungsghi747.tar.md5 this one is probably for a 4.1.1 version phone?
I would not flash anything for the d2att at this point.
Try this:
Download the latest tar.md5 file from here: https://goo.im/devs/philz_touch/CWM_...Edition/d2lte/
Download supersu zip from here and place it onto an external SD card or copy it to the phone's internal storage: http://download.chainfire.eu/695/SuperSU/
In Odin, uncheck everything except f.reset time. Flash Philz. When you see reset in the status window, remove USB cable, pull battery, replace battery, boot into recovery, flash supersu, reboot.
I am fairly certain that AOSP, or at least CM, de-unified in the past few months. Not that it matters much, other than for the confusion it causes.
I updated to Cyanogenmod 11's latest nightly of 4/26/2015 and my phone started behaving badly.
I kept losing signal and having trouble making calls and in my attempts to resolve the issue by flashing back to a previous nightly it seems I lost my IMEI and with it connectivity.
I found a video on youtube that says to access the service menu to fix it but CyanogenMod doesn't do anything when I enter the codes in the dialer so I was attempting tro go back to stock but having trouble finding a good stock rom I can use and the 2 I"ve tried both fail in odin. Then I read something about needed a pit file but flashing that fails to.
So right now I went back stop recovery but still on Cyanogenmod but the phone doesn't do anything when it boots...just no connection.
Someone told me the pros in this forum could help so here I am, help me Cell Phone Gods!!!:crying:
Got this phone info app that says bootloader is I747UCUEMJB
Update 5/5/2015 I'm on latest bootloader and running stock rom but have no data and both calling and text work randomly. 4G symbol comes on once in a while but most of the service I do get when it works is on edge network.
Sounds like your modem may be messed up.
Load a terminal app and use the app to verify the bootloader on your phone.
audit13 said:
Sounds like your modem may be messed up.
Load a terminal app and use the app to verify the bootloader on your phone.
Click to expand...
Click to collapse
how do I do that? with my pc? what's a good app to use?
Try this: boot into download and read the screen. Do you see anything about warranty bit on the phone?
audit13 said:
Try this: boot into download and read the screen. Do you see anything about warranty bit on the phone?
Click to expand...
Click to collapse
Yes, says Warranty bit 1
system status official.
What's that tell you?
btw i just went back to CWM
got this phone info app that says bootloader is I747UCUEMJB
Odin is failing with the stock ROM from sammobile because the phone has at least a 4.3 bootloader on your phone. Do not flash anything from sammobile because attempting to do so could brick your phone.
Since you're back on cwm with an mjb bootloader, try flashing the mjb modem via cwm.
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23
audit13 said:
Odin is failing with the stock ROM from sammobile because the phone has at least a 4.3 bootloader on your phone. Do not flash anything from sammobile because attempting to do so could brick your phone.
Since you're back on cwm with an mjb bootloader, try flashing the mjb modem via cwm.
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23
Click to expand...
Click to collapse
I tried flashing the modem before...I'll do it again...is that going to get me my IMEI number back or allow me to flash stock rom to recover my IMEI?
fausto412 said:
I tried flashing the modem before...I'll do it again...is that going to get me my IMEI number back or allow me to flash stock rom to recover my IMEI?
Click to expand...
Click to collapse
I did flash the modem you linked and that improved things a bit...I'm back to the original problem, I was having where my phone was having trouble staying on the network. I had even lost all my APNs in my attempts to fix. Now my APNs are back. Still showing unkown IMEI and phone isn't getting on the cell phone network.
So the baseband is now mjb?
Try flashing the latest release of CM10.2. It's possible you need to update the modem and bootloader together in order to support the newest release of CM11. I don't have an s3 so i can't confirm my theory.
You may have to try nvwriter to inject the imei as a last resort: http://forum.xda-developers.com/showthread.php?t=1804117
audit13 said:
So the baseband is now mjb?
Try flashing the latest release of CM10.2. It's possible you need to update the modem and bootloader together in order to support the newest release of CM11. I don't have an s3 so i can't confirm my theory.
You may have to try nvwriter to inject the imei as a last resort: http://forum.xda-developers.com/showthread.php?t=1804117
Click to expand...
Click to collapse
Yes baseband is MJB.
I'll install 10.2 real quick. In the past that didn't help but who knows this time.
OK. Installed 10.2.1 and still have null imei. Connects to cell networks unreliably but no data and texting.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
fausto412 said:
OK. Installed 10.2.1 and still have null imei. Connects to cell networks unreliably but no data and texting.
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
Click to expand...
Click to collapse
not as smart as @audit13 , but might find some help here. good luck.
http://forum.xda-developers.com/showthread.php?t=1804117
"all i can really do , is stay out of my own way and let the will of heaven be done"
Did you confirm that your modem and bootloader match? Did you try nvwriter to inject the imei?
I believe modem and bootloader match. Haven't tried nvwriter...can't access service mode on cyanogen apparently.
What do I do now?
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
audit13 said:
Did you confirm that your modem and bootloader match? Did you try nvwriter to inject the imei?
Click to expand...
Click to collapse
The NV Writer method, I get stuck at this point in the instructions
"*If you are running a aosp rom (cm9,cm10,aokp etc) you can use the diag method described HERE"
The link is dead so I've no idea what I'm supposed to do.
Since your imei is null, I'm not sure what else to suggest except to re-flash the existing bootloader and modem or flash a newer bootloader and modem.
audit13 said:
Since your imei is null, I'm not sure what else to suggest except to re-flash the existing bootloader and modem or flash a newer bootloader and modem.
Click to expand...
Click to collapse
There is a newer bootloader and modem?
I sure wish I had an easier time with finding out this info plus the files.
http://forum.xda-developers.com/galaxy-s3-att/general/modem-4-4-2-modems-i747-i747m-t2856577
OK, about to try to update to ne4 bootloader and modem. wish me luck!
Updated to NE4 firmware but modem file failed due to being on NE4 firmware(wth!)...obtained a different file that installed ok.
Result...still having null IMEI and no LTE...inconsistent connection issues.
I wonder if I was on NJ1 before I started messing around....
I have Pac Rom Android 5.1.1 installed on my rooted sg3 and I need to do a carrier unlock. I contacted ATT to get the unlock code and the code they provided didn't work. Now I want to downgrade to Android 4.1 and try the UMTS menu trick as described here http://forum.xda-developers.com/showthread.php?t=2176719
I have tried Odin many times (with many versions, different computers, USB cables, etc) and every time Odin fails to flash Android 4.1. with a Fail AUTH error. I have used Odin successfully in the past many times with this phone but am unable to get it to work this time around.
Does anyone know how to downgrade the sg3 from 5.1.1 to 4.1? Or even better does anyone how to carrier unlock the sg3 when it has 5.1.1 installed on it?
Thanks!
Odin is probably failing because you have a 4.3 or 4.4.2 bootloader on your phone. I recommend you not flash anymore ROMs using Odin as repeat attempts to flash the 4.1.1 ROM via Odin may hard brick the phone.
Once a phone is running and 4.3 or 4.4.2 bootloader, you cannot use the free/hidden menu method to unlock the phone.
You cannot use a custom ROM to enter an unlock code. You'll have to go back to a stock ROM, enter the code, and return to a custom ROM.
Thanks for the reply. Do you know how I can go back to stock 4.1.1 without using Odin?
You need the 4.1.1 bootloader in order to use the free method. Once a phone is on 4.3 bootloader or higher, you can't go back to 4.1.1. Don't try because attempts to do so could brick the phone.
A stock 4.1.1 rom on a 4.3 bootloader will not work.
So you're saying once the sg3 is on a version above 4.3 there is no way to go back to 4.1.1?
slipnslider said:
So you're saying once the sg3 is on a version above 4.3 there is no way to go back to 4.1.1?
Click to expand...
Click to collapse
Once it is on the 4.3 or higher bootloader, there is no going back to an older bootloader and it is the older 4.1.1 bootloader and stock 4.1.1 ROM that is required to unlock using the free method.
Since you have the code, you can flash a stock ROM from recovery.
audit13 said:
Once it is on the 4.3 or higher bootloader, there is no going back to an older bootloader and it is the older 4.1.1 bootloader and stock 4.1.1 ROM that is required to unlock using the free method.
Since you have the code, you can flash a stock ROM from recovery.
Click to expand...
Click to collapse
Thanks. What do you mean by free method?
Also you suggesting if I put the 4.1.1 stock rom .zip on my sg3 I can flash it via CWM just like I would the latest 5.1.1 Pac Rom release?
The free method is the method you linked in your original post. This is the only free method available and it requires a 4.1.1 bootloader that your phone doesn't have. Installing 4.1.1 via cwm is not going to help you unlock it.
Since you have the code, you can flash a stock ROM from recovery.
Click to expand...
Click to collapse
How would I do this? Do I just flash 4.1.1 from cwm?
Flashing 4.1.1 onto your phone will not allow you to enter the code.
Before flashing anything, you need to verify the bootloader that is running on your phone. Until you do that, I would not flash any bootloaders or modems. An incompatible modem/bootloader combination can also brick your phone.
Sorry, one last question.
You'll have to go back to a stock ROM, enter the code, and return to a custom ROM.
Click to expand...
Click to collapse
How can I go back to the stock rom?
You can flash a stock rom from the general thread using twrp or cwm.
Awesome, thanks again. I was worried about going that route since I'm on 5.1.1 but I'll give it a shot
slipnslider said:
Awesome, thanks again. I was worried about going that route since I'm on 5.1.1 but I'll give it a shot
Click to expand...
Click to collapse
When you pick a stock ROM, make sure you pick one with the same bootloader and modem that are currently on your device. You probably have either the NE4 or NJ1 bootloader and modem pair. You DO NOT have a 5.1.1 bootloader and modem, they do not exist for the SGS3. Check your versions from a Terminal Emulator app or check them with the Phone Info - Samsung - app from the PlayStore.
Both NE4 and NJ1 stock ROMs are available in the forum. enewman17 posted them form image dumps, they have been used successfully by many.
The Terminal Emulator commands are:
Code:
getprop ro.bootloader
getprop | grep version.baseband
Thanks, I did this and both the bootloader and modem ended with NJ1 so I downloaded UCUFNJ1_Rooted.zip from enewman17's thread using CWM 6.0.4. The flash was successful but now the phone is frozen at the AT&T logo when I turn it on.
Any thoughts as to why its stuck booting up?
slipnslider said:
Thanks, I did this and both the bootloader and modem ended with NJ1 so I downloaded UCUFNJ1_Rooted.zip from enewman17's thread using CWM 6.0.4. The flash was successful but now the phone is frozen at the AT&T logo when I turn it on.
Any thoughts as to why its stuck booting up?
Click to expand...
Click to collapse
More than once I have seen reports of this happening when going from a 5.x.x ROM back to 4.4.x. The most common solution has been to include formating the internal sdcard before flashing the stock ROM.
If I flash the sd card as well I will lose the UCUFNJ1_Rooted.zip file. So in that case should I use adb via CWM to flash it?
slipnslider said:
If I flash the sd card as well I will lose the UCUFNJ1_Rooted.zip file. So in that case should I use adb via CWM to flash it?
Click to expand...
Click to collapse
Put the zip file on the external sdcard and then flash it with your recovery.
I actually didn't have an external SD card. I wound up taking it to the ATT store that had an ATT repair shop inside it and they reset it back to stock 4.4 for me and now everything works great! After unlocking the carrier on the phone I did have to manually enter the t-mobile APN to get the data connection working but that was simple (the info is listed on t-mobile's site)
slipnslider said:
I actually didn't have an external SD card. I wound up taking it to the ATT store that had an ATT repair shop inside it and they reset it back to stock 4.4 for me and now everything works great! After unlocking the carrier on the phone I did have to manually enter the t-mobile APN to get the data connection working but that was simple (the info is listed on t-mobile's site)
Click to expand...
Click to collapse
Glad to see you are up and running. Also glad to hear the AT&T guys helped out.
Hey, sup?
I need your help, I'm trying to go back to stock firmware on my i747, currently I'm running CM11 latest snapshot.
Background: Some time ago, I accidently erased my imei. Took the phone to a guy who restored it but the phone doesn't work with 3G now, only 2G. So I wanted to try going back to stock firmware to see if that fixes the issue.
I tried downloading the CUEMJB file from here, but it doesn't work (keeps looping the same page) http://androidromupdate.com/att-samsung-galaxy-s3-sgh-i747-odin-stock-firmware/
Can you help me? Also, it is safe what I'm trying to do?
Thank you!
Triple check to make sure the imei displayed in About Device matches exactly to the one on the sticker under the battery.
If it does, and after you get stock working again, PM me and I can probably help.
As for the looping, do you mean the Web page? Just get the stock files from enewman17's thread. It's either in General or Development, can't remember for sure. Probably General.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
Triple check to make sure the imei displayed in About Device matches exactly to the one on the sticker under the battery.
If it does, and after you get stock working again, PM me and I can probably help.
As for the looping, do you mean the Web page? Just get the stock files from enewman17's thread. It's either in General or Development, can't remember for sure. Probably General.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Thank you. Yes the IMEI matches.
I was able to download the file.
Unfortunately, the thing didn't went ok. After flashing my phone is unresponsive, black screen, no more boot
If I connect it to the computer at this point, it tries to search for a QHSUSB_DLOAD driver. Not sure what is that, I think I bricked my phone.
I've seen some guides for unbricking by placing a sd card in the phone at boot but so far it haven't worked
Going to one of the 4.4.2 bootloaders and modems for your device may fix the issue, maybe without going back to stock. But I do recall that a return to stock has been required by many. If you are on newer bootloader and modem than 4.3, do not use a 4.3 (MJB) file no matter the source. As Doc said use one of the releases by enewman17 that you can flash in your custom recovery, NE4 is here. enewman17 also has threads for MJB, NJ1, and NJ2 stock ROMs; all of these are flashed in a custom recovery. With the i747 I have continually seen it recommended that you upgrade bootloader and modem sequentially, that is upgrade to NE4 before going to NJ1, and NJ1 before going to NJ2. I can provide links to enewmans other threads if necessary.
BTW, the 4.3 release was not a full rom, it was an update/patch. Files I have seen run 100 mb or less. If that is the file you want, and can use w/o bricking your device see this thread http://forum.xda-developers.com/showthread.php?t=2722660 Only use it if you are on 4.1.1, 4.1.2, or 4.3 bootloader and modem.
Another way to get a 4.3 Odin flashable update is here. You must be on 4.1.1 or 4.1.2 bootloader and modem to use this as instructed.
dawgdoc said:
Going to one of the 4.4.2 bootloaders and modems for your device may fix the issue, maybe without going back to stock. But I do recall that a return to stock has been required by many. If you are on newer bootloader and modem than 4.3, do not use a 4.3 (MJB) file no matter the source. As Doc said use one of the releases by enewman17 that you can flash in your custom recovery, NE4 is here. enewman17 also has threads for MJB, NJ1, and NJ2 stock ROMs; all of these are flashed in a custom recovery. With the i747 I have continually seen it recommended that you upgrade bootloader and modem sequentially, that is upgrade to NE4 before going to NJ1, and NJ1 before going to NJ2. I can provide links to enewmans other threads if necessary.
BTW, the 4.3 release was not a full rom, it was an update/patch. Files I have seen run 100 mb or less. If that is the file you want, and can use w/o bricking your device see this thread http://forum.xda-developers.com/showthread.php?t=2722660 Only use it if you are on 4.1.1, 4.1.2, or 4.3 bootloader and modem.
Another way to get a 4.3 Odin flashable update is here. You must be on 4.1.1 or 4.1.2 bootloader and modem to use this as instructed.
Click to expand...
Click to collapse
Thank you very much.
But I'm with a phone that doesn't boot now. What would you recommend to do if there's something to bring it back
Alright! I just tried the SD card method w/ one of the files in the threads linked. Phone boots!
So it seems my bootloader is bad right?
japi2000 said:
Thank you very much.
But I'm with a phone that doesn't boot now. What would you recommend to do if there's something to bring it back
Click to expand...
Click to collapse
Can you get into recovery? If so you can flash the appropriate stock rom by enewman17.
Do you recall what bootloader and modem you were on? If you have TWRP as your recovery there are terminal commands you can use within the recovery to determine your bl/modem versions. This may also hold true for CWM and Philz Recoveries, but I don't know for certain.
If you can not get to recovery you may need to put a debrick image on an external sdcard to boot and then restore your device.
dawgdoc said:
Can you get into recovery? If so you can flash the appropriate stock rom by enewman17.
Do you recall what bootloader and modem you were on? If you have TWRP as your recovery there are terminal commands you can use within the recovery to determine your bl/modem versions. This may also hold true for CWM and Philz Recoveries, but I don't know for certain.
If you can not get to recovery you may need to put a debrick image on an external sdcard to boot and then restore your device.
Click to expand...
Click to collapse
Yes sir. With the SD card method I managed to boot the phone. Yay!
I don't recall bootloader and modem unfortunately. I know I was using CM11 one of the latest snapshots for d2lte.
I have access to download mode. Screen reads bootloader RP SWREV:2
I have access to recovery (its a basic one though). Reads Android system recovery <3e>
What do you recommend from here?
japi2000 said:
Yes sir. With the SD card method I managed to boot the phone. Yay!
I don't recall bootloader and modem unfortunately. I know I was using CM11 one of the latest snapshots for d2lte.
I have access to download mode. Screen reads bootloader RP SWREV:2
I have access to recovery (its a basic one though). Reads Android system recovery <3e>
What do you recommend from here?
Click to expand...
Click to collapse
That is the stock recovery. If you were successfully running one of the latest CM11 snapshots, you were probably on one of the three 4.4.2 bootloaders ( and modems ), they are NE4, NJ1, and NJ2. This would explain why the MJB (4.3) image you downloaded and flashed would soft brick your phone. It looks like that flash may be responsible for you being back on stock recovery, at best guess. Before anything else, do a factory reset from the stock recovery. This is frequently necessary to boot when going from a CM/AOSP LP rom back to stock.
Since you can get to download mode, I think the best bet would be to install a custom recovery. TWRP for the i747 is here, the top image is flashable with Odin while in download mode. Remember not to reboot from Odin. Instead remove the cable, pull the battery, then boot straight to recovery. Once you have TWRP loaded, boot into recovery and use the terminal emulator in it to determine bootloader and modem with these commands:
Code:
getprop ro.bootloader
getprop | grep version.baseband
Once you know the version of bootloader and modem you had been on, reflash that version from TWRP you will probably need the file on an external sdcard to do so. After this you can flash your rom of choice from TWRP, stock or otherwise. Since you were having imei issues go with one of enewman's stock roms, as @DocHoliday77 suggested. He can then help you with the imei issues if still necessary. Any other ideas Doc?
Ok, so
Bootloader = I747UCUEMJB
I don't get anything when running getprop | grep version.baseband in the recovery.
This is what I've done so far.
Booted w/ the sdcard trick (bootloader in the sdcard).
Installed twrp
Installed the following files:
AT&T_I747UCUEMJB.zip
d2att_I747UCUEMJB_bootloader.zip
d2att_I747UCUEMJB_modem.zip
d2att_Kernel_Stock_init.d_4_3_MJB_v1.0.zip
That brought the phone to life again (w/ stock 4.3). Then I flashed CM12 from the recovery. All went ok.
Problem is, I still don't have 3G connectivity, only edge.
What would you recommend try next?
Thank you
Alright, I was able to upgrade to UCUFNJ1 for both the bootloader and baseband. Still no 3G. Ideas?
Pm me. As I said before, if the imei is correct, I might be able to help. I can't do it here though because it's against forum rules to post the info publicly. (Too many people want it for illegal use).
When you pm me, include your current bootloader and baseband. (Just so I don't have to keep coming back here for reference). Also include how it was lost and if you know how it was restored.
I know you've already posted some of this, but I get lots of PM's so it'll help me keep track of everything without going back and forth between here and there.
Also, you need to be stock for this to work, so don't flash anything else just yet.
Glad to hear you got it running again BTW!
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
Pm me. As I said before, if the imei is correct, I might be able to help. I can't do it here though because it's against forum rules to post the info publicly. (Too many people want it for illegal use).
When you pm me, include your current bootloader and baseband. (Just so I don't have to keep coming back here for reference). Also include how it was lost and if you know how it was restored.
I know you've already posted some of this, but I get lots of PM's so it'll help me keep track of everything without going back and forth between here and there.
Also, you need to be stock for this to work, so don't flash anything else just yet.
Glad to hear you got it running again BTW!
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Alright thank you
Alright, I'm happy to say that with the help of our fellow DocHoliday77 I was able to solve the issue !
Thanks everyone!
Glad you have it working.
Way to go Doc.
Damn japi2000. You did that quick good job.
Thank you!
I can't believe I went from a almost dead phone to a fully working one in only a few days, even with the 3G/4G working again !
This forum and people are amazing! Thank you!
good afternoon, I have a Galaxy S3 SGH-I747 Model using ClockworkMod install the [ROM] [4.4.4] SlimKat d2att (at & t) Stable 9.0 and [Gapps] [4.4.x] Official Slim GApps TRDS (Slimkat) and now not recognize me the sim card. i bought this phone in amazon for use it here in Madrid. i dont know if is a Modem issue. I appreciate all the help you can give me. Thank you. (sorry for my english)
Does your sim card have a pin code that you enter each time you boot the phone? If yes, does the phone ask for the pin before unlocking the sim? What bootloader and modem are currently on the phone? Did the phone work before installing a custom ROM?
@audit13 , mine said "no service available" after moving from KK to lolli and i flashed a "write to extsdcard fix zip" and it fixed the issue , i.e. can now make and recieve calls. dont know if is same issue (or why exactly that fixed mine) but i have a KK "write to extsdcard fix.zip" if you think it would help.
"err on the side of kindness"
audit13 said:
Does your sim card have a pin code that you enter each time you boot the phone? If yes, does the phone ask for the pin before unlocking the sim? What bootloader and modem are currently on the phone? Did the phone work before installing a custom ROM?
Click to expand...
Click to collapse
Thank you, audit13, my Sim card have a pin code, but doesn't ask for the pin, and yes, the phone work well before installing the custom rom. Where can I look the bootloader and modem?.
you can download the "samsung info app" from here http://forum.xda-developers.com/showthread.php?t=2609045
and it will tell you bootloader and modem.
(p.s. as always audit13 , not trying to butt-in ; just trying to help out/save you a step )
"err on the side of kindness"
Hey I have sgh-i747m canadian on stock jb . I flashed to CM 12.1 and my phone doesn't recognize sim. That means I can make calls and receive but no mobile data. Please help me
Sent from my SAMSUNG-SGH-I747 using XDA-Developers mobile app
For the i747, sounds to me like the bootloader and modem are too old for the rom.
For theni747m, is the phone running the latest bootloader and modem?
@mrrocketdog, I've never heard about that zip until your helpful post. I must keep that in mind for the future even though I haven't had an s3 for quite a while.
audit13 said:
Does your sim card have a pin code that you enter each time you boot the phone? If yes, does the phone ask for the pin before unlocking the sim? What bootloader and modem are currently on the phone? Did the phone work before installing a custom ROM?
Click to expand...
Click to collapse
Ok, use the app that mrrocketdog ,so nicely share to us, and the bootloader is I747UCDLK3 and the módem is MSM8960. Something call my atention, the kernel is 3.4.104-cyanogenmod-g38a4g52 [email protected] #1 32-bit. I hope this information can help. Thank you
mrrocketdog said:
@audit13 , mine said "no service available" after moving from KK to lolli and i flashed a "write to extsdcard fix zip" and it fixed the issue , i.e. can now make and recieve calls. dont know if is same issue (or why exactly that fixed mine) but i have a KK "write to extsdcard fix.zip" if you think it would help.
HI, where can I find that zip to see if fix my problem. Thanks in advance.
Click to expand...
Click to collapse
The problem is the bootloader and modem. They need to be updated to work with the latest ROMs.
If the phone is sim unlocked, I recommend flashing back a stock rom using Odin and the firmware from sammobile, set up the phone, run ota updates until the phone is running the latest bootloader and modem. This is tedious and takes the most time but it is the safest method in my opinion.
If you don't want to go this route, just flash the latest modem and bootloader using twrp, flash the custom rom, flash gapps.
@Budare , here is the thread to upgrade bootloaders and modem if you decide on this route rather than flashing back to stock and running ota updates as @audit13 suggested , which IS the safest route. (always always always a certain % of risk ; no matter how small , to flash anything. not trying to scare you , just being honest)
http://forum.xda-developers.com/showthread.php?t=2808654
p.s. you might want to think about changing to twrp recovery as cwm has not been updated in quite a long time.
p.s.s. here's the latest twrp DL page for sghi747 att
https://dl.twrp.me/d2att/
"err on the side of kindness"
audit13 said:
The problem is the bootloader and modem. They need to be updated to work with the latest ROMs.
If the phone is sim unlocked, I recommend flashing back a stock rom using Odin and the firmware from sammobile, set up the phone, run ota updates until the phone is running the latest bootloader and modem. This is tedious and takes the most time but it is the safest method in my opinion.
If you don't want to go this route, just flash the latest modem and bootloader using twrp, flash the custom rom, flash gapps.
Click to expand...
Click to collapse
thank you audit13, but how i run ota updates??
To run ota updates, you need to use Odin to flash the stock att 4.1.1 rom using Odin. After setting up the phone, check for software update under the phone settings.
audit13 said:
To run ota updates, you need to use Odin to flash the stock att 4.1.1 rom using Odin. After setting up the phone, check for software update under the phone settings.
Click to expand...
Click to collapse
i dont know if is because im in Madrid, but the phone doesnt get updates, thats why i want to use another rom. what can i do?
Not sure but I have received OTA updates even when the phone is not in the phone's original country. The OTA updates came over wifi.
If you want to use another ROM, you can install TWRP, boot into TWRP, flash bootloader, flash modem, flash custom ROM, flash gapps. If flashing the modem bootloader in TWRP, DO NOT reboot the phone in between flashing this files and make sure the bootloader and modem version are made for each other.