Good Morning
passage through the forum to see if someone can help me with a problem I have since I started with custom roms. My problem is that the cell is left without sound when I have headphones on and the cell is hot. the strange thing is that the sound is full, even if I unplug the headphones. I have to reboot the phone and wait for the temperature to normalize again to plug headphones and the sound is heard.
Another fact is that my cell phone can be on fire and the sound will be perfect as long as you do not have headphones plugged
Does anyone know why this happens and how to fix it?:crying:
Unfortunately it sounds like you have a rather unique problem there. I've never encountered it anyway.
Have you tried other roms or kernels? If not, I think that would be the first thing to try. What rom and kernel are you currently using? Try flashing a stock based rom, factory reset, and see if it still occurs.
If the problem persists on different roms and kernels, it will likely be a hardware issue.
Have you also tried different headphones?
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
Unfortunately it sounds like you have a rather unique problem there. I've never encountered it anyway.
Have you tried other roms or kernels? If not, I think that would be the first thing to try. What rom and kernel are you currently using? Try flashing a stock based rom, factory reset, and see if it still occurs.
If the problem persists on different roms and kernels, it will likely be a hardware issue.
Have you also tried different headphones?
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
ow it is the cyanogenmod 12.1, before used the slimkat and both have had that problem. I have not tried with stock rom because when I try to flash it with Odin leaves me in soft brick. and I find the rom that works. and hardware problem not think it's, as you never give me problems, unless the cell phone is hot
frank461 said:
ow it is the cyanogenmod 12.1, before used the slimkat and both have had that problem. I have not tried with stock rom because when I try to flash it with Odin leaves me in soft brick. and I find the rom that works. and hardware problem not think it's, as you never give me problems, unless the cell phone is hot
Click to expand...
Click to collapse
One reason Odin could be causing problems is if you are attempting to flash software with bootloader and modem that is older than what is on the phone. You have had CM12.1 on the phone, but what is your current bootloader and modem? You can use these commands in Terminal Emulator to find out:
Code:
getprop ro.bootloader
getprop | grep version.baseband
I may have missed it, but do you have the i747 or the i747M? Both will work with the same roms, however they use different bootloaders and modems. Odin should stop you from loading ROMs from the wrong device, most times anyway.
dawgdoc said:
One reason Odin could be causing problems is if you are attempting to flash software with bootloader and modem that is older than what is on the phone. You have had CM12.1 on the phone, but what is your current bootloader and modem? You can use these commands in Terminal Emulator to find out:
Code:
getprop ro.bootloader
getprop | grep version.baseband
I may have missed it, but do you have the i747 or the i747M? Both will work with the same roms, however they use different bootloaders and modems. Odin should stop you from loading ROMs from the wrong device, most times anyway.
Click to expand...
Click to collapse
Well my baseband AMD modem is I747mvlufne6 I for this model as I was going down the roms
frank461 said:
Well my baseband AMD modem is I747mvlufne6 I for this model as I was going down the roms
Click to expand...
Click to collapse
NE6 would indicate the i747M. The soft brick could be a factor of returning to stock KitKat after having been on Lollipop, either CM or AOSP and their derivatives. If you want to try a stock 4.4.2 ROM, the fix for the soft brick is either:
1) Flash the stock ROM from your custom recovery, then flash the stock recovery before rebooting, boot into the stock recovery and do a factory reset. OR -
2) Place the stock ROM on an external sdcard, boot into your custom recovery, format the internal sdcard, flash the stock ROM, reboot.
Needless to say, you will lose everything you have not backed up. Of course, I don't know that the stock ROM will fix your sound and overheating issues.
Ok i trying this and leter i tell you what happen
Thanks
If I'm not mistaken, the i747m firmware is available from http://sammobile.com/firmwares
So you can just flash NE6 full firmware (or newer), boot recovery and factory reset.
(Might be a little more straightforward that way...eliminates some extra steps)
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
If I'm not mistaken, the i747m firmware is available from http://sammobile.com/firmwares
So you can just flash NE6 full firmware (or newer), boot recovery and factory reset.
(Might be a little more straightforward that way...eliminates some extra steps)
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
You are correct, it is on sammobile and it would eliminate some steps. I think he would lose root, but it would be easy enough to afterwards flash a custom recovery and then root with the supersu.zip.
I probably suggest the two steps I do because they are the same for the i747M and the i747. With the i747 there is no 4.4.2 stock from sammobile to flash, so that third option isn't present.
good to fix the sound problem may work because i was investigated and found that the kernel could be problems because it was not compatible with Android 4.4 or newer. So I wanted to try to return to rom stock and see if it is true.
Now I'm downloading the rom is SamMobile (after a few problems of my own) and later, say if the sound repair
dawgdoc said:
You are correct, it is on sammobile and it would eliminate some steps. I think he would lose root, but it would be easy enough to afterwards flash a custom recovery and then root with the supersu.zip.
I probably suggest the two steps I do because they are the same for the i747M and the i747. With the i747 there is no 4.4.2 stock from sammobile to flash, so that third option isn't present.
Click to expand...
Click to collapse
I downloaded the firmware file SamMobile but it Odin file is not to flash in recovery what do to work in recovery?
frank461 said:
I downloaded the firmware file SamMobile but it Odin file is not to flash in recovery what do to work in recovery?
Click to expand...
Click to collapse
@DocHoliday77 would it be safe for him to flash one of the At&T stock 4.4.2 ROMs made available by @enewman17 as long as he was very careful to not flash the bootloader and modem? I'm thinking it would, but I prefer hearing another voice confirm this.
frank461 said:
I downloaded the firmware file SamMobile but it Odin file is not to flash in recovery what do to work in recovery?
Click to expand...
Click to collapse
You have to be in Download Mode to flash with Odin, not recovery. (Same buttons but volume down instead of up.)
dawgdoc said:
@DocHoliday77 would it be safe for him to flash one of the At&T stock 4.4.2 ROMs made available by @enewman17 as long as he was very careful to not flash the bootloader and modem? I'm thinking it would, but I prefer hearing another voice confirm this.
Click to expand...
Click to collapse
That would be safe to do. The main reason I still suggest flashing the full official firmware though is in case something currently on the device got corrupted somehow. Plus if he flashes the NE4 system and it still isn't fixed, the next step would be to flash full official stock anyway. Imo, it's the only true way to know if you have a hardware or a software issue.
That said though, I have a feeling things would end up working with either one of those solutions.
Sent from my SGH-T999 using Tapatalk
Sorry for the delay, I have already flashed the official ROM and as the sound problem is arrangement. however I have one more question, I'm from mexico but to flash the rom NE6 cell did not recognize the Spanish language. it is the only detail, as I pass the phone to Spanish without rooting the phone
As I said everything works fine, signal, wifi, everything. I guess because it is released. But I would like this in Spanish.
for now thank everyone who attended my problem.
Related
I was on stock, un-rooted firmware version MD5. Went ahead with the official 4.3 upgrade through KIES. Don't like it, want to go back to stock MD5. Trying to ODIN back with official FW file (not the first time I've used this) and when I start, it fails and what is weird is that it appears the bootloader is changed as well from the 4.3 update. It has 2 new lines in the upper left corner (Warranty Bit: 0 and BOOTLOADER RP SWREV: 1) Now, once the ODIN failed, another line, in all red letters on the download screen underneath those previous mentioned lines, states
SW REV CHECK FAIL : Fused 1 > Binary 0. Any ideas? Phone works 100% on this new 4.3 from TMO, just cant seem to ODIN back to 4.1.2. Any help would be super. Thanks!
phoenix98 said:
I was on stock, un-rooted firmware version MD5. Went ahead with the official 4.3 upgrade through KIES. Don't like it, want to go back to stock MD5. Trying to ODIN back with official FW file (not the first time I've used this) and when I start, it fails and what is weird is that it appears the bootloader is changed as well from the 4.3 update. It has 2 new lines in the upper left corner (Warranty Bit: 0 and BOOTLOADER RP SWREV: 1) Now, once the ODIN failed, another line, in all red letters on the download screen underneath those previous mentioned lines, states
SW REV CHECK FAIL : Fused 1 > Binary 0. Any ideas? Phone works 100% on this new 4.3 from TMO, just cant seem to ODIN back to 4.1.2. Any help would be super. Thanks!
Click to expand...
Click to collapse
Is not possible for right now, until devs will create a new root app or something like superSU or I don't know ! :crying: Same to me ...
Your Boot loader is probably secured.
Try Root66 image and get back to UVDMD5 Rooted. From there, use Doc Holiday's thread to get 4.3 upgrade.
As it stands, right now if you flashed the official firmware or OTA, you will not be able to Odin flash any previous firmware. Maybe if you were never rooted....
For now though, you shoukd still be able to flash cwm/twrp and flash another rom. you will be limited to the 4.3 modem, but otherwise should be ok to run a 4.1.2 rom.
We are working on it.
Sent from my T-Mobile MyTouch 3G Slide(HTC Espresso) using Tapatalk 2
I had the same problem
I just had this same problem and was lucky enough to fix it!!!!
vTizzle said:
I just had this same problem and was lucky enough to fix it!!!!
Click to expand...
Click to collapse
How/ What did you do you fix it? I'm stuck in a rut :l
I was trying to few things. But essentially I was trying to get back to a custom recovery so that I can flash a compatible rom. try flashing a recovery in Odin, stay away from the CWM. Flash to TW RP or something like that. I will try to help out more as soon as I get to my laptop
Sent from behind you
vTizzle said:
I was trying to few things. But essentially I was trying to get back to a custom recovery so that I can flash a compatible rom. try flashing a recovery in Odin, stay away from the CWM. Flash to TW RP or something like that. I will try to help out more as soon as I get to my laptop
Sent from behind you
Click to expand...
Click to collapse
Hm... Interestingly enough it worked! I flashed CWM 6.3.0 though, sent me straight into stock hehe :good::good: Though I'm still curious how long until I can root it
Have you tried the auto root course??
Sent from behind you
Boot recovery, then reboot system. It should ssk if you want to root.
Better yet, flash one of our roms. Or, download the supersu zip file from chainfires thread. (Or in my sig, but its not up to date)
---------- Post added at 09:12 PM ---------- Previous post was at 09:11 PM ----------
There are several ways to root. But if you don't get rid of knox iits almost pointless.
Co-author root didn't work, and nor did Root66
I'm on the same boat
Same here,
Mine was rooted, then
I Updated to Factory 4.3
Same red letters and can't get it back,
I want to 'cause it's unstable and
it has weird partition, "emulated/0"
Any Help Please !!
This is why everyone should try to search for information on anything and everything before flashing it to your device. Even if its an official update.
As stated many, many times, once you flash the 4.3 update, you cannot flash older firmware again. Roms are ok, older firmware can brick you. Your weird folder is androids implementation of user profiles if I understand it right. May as well get used to it now, I don't think its going away.
And for those interested, the root66 firmware works fine now as far as I can tell.
If you experience instability, you need to factory reset.
DocHoliday77 said:
This is why everyone should try to search for information on anything and everything before flashing it to your device. Even if its an official update.
As stated many, many times, once you flash the 4.3 update, you cannot flash older firmware again. Roms are ok, older firmware can brick you. Your weird folder is androids implementation of user profiles if I understand it right. May as well get used to it now, I don't think its going away.
And for those interested, the root66 firmware works fine now as far as I can tell.
If you experience instability, you need to factory reset.
Click to expand...
Click to collapse
If I did softbrick it, is there anyway to restore it?
You can try first wiping just dalvik and cache, then try factory reset.
Other ROMs
DocHoliday77 said:
This is why everyone should try to search for information on anything and everything before flashing it to your device. Even if its an official update.
As stated many, many times, once you flash the 4.3 update, you cannot flash older firmware again. Roms are ok, older firmware can brick you. Your weird folder is androids implementation of user profiles if I understand it right. May as well get used to it now, I don't think its going away.
And for those interested, the root66 firmware works fine now as far as I can tell.
If you experience instability, you need to factory reset.
Click to expand...
Click to collapse
Thank you Doc , It has been said ..Over and over and over.. OTA 4.3 update means you cannot flash older firmware again! I was one of the lucky that waited and installed you ROM and it has been stable . I placed a few Mods like Apps For 4.3 TW
For those just refused to READ and have NOT done a OTA update to 4.3 Like DocHoliday77 and and many have said .. here goes one more time..
WARNING!!!
If you have NOT updated via the official firmware or OTA update, it is highly recommended that you do NOT do so at this time!
You can still run these roms and gain every advantage, with none of the problems!
There so many other 4.3 ROMs to play with DocHolidays, Sarahai, mrRobinson and now aamir123. . YOu just to READ before run in head first into the OTA.
I have been trying to keep up with all the 4.3 update stuff but its just so hard with 15 different threads and it being updated everyday. I stupidly updated OTA 4.3 before coming on here and reading and it blows! Samsung is stupid for releasing such a unpolished update. But besides the point, I have been having a problem with out going calls, and battery life. When I will press to call someone the call ends instantly and I have to restart phone for it to allow me to call out. Has anyone else had this problem?
Also, are we any closer to getting 4.3 rooted? I know developers are having problems with Knox etc? If not is there anything I can do to make this update better or do I just have to suck it up? Thanks for the help guys.
I alrdy talked to people at samsung and complained beyond belief, but I dont think the out sourced help desk person understood me.
I made it !!
How ?
1. Uninstall KNOX with Titanium.
2. Flash CWM twice (first one failed), Now I have CWM.
3. Download T999UVDMD5 (Deodexed)
4. Flash it via CWM.
5. Voilà !!
Now It has the partition as it comes from Factory !.
It's there a version similar to this one, running on Android 4.3 (Stock Deodexed, Without KNOX) ?
DocHoliday77 said:
You can try first wiping just dalvik and cache, then try factory reset.
Click to expand...
Click to collapse
So I have a question Doc, I know I posted about this in the CM11 unofficial thread as well, but I am running your Non-Knox, CiQ free version and I have CWM installed, and I'm perfectly rooted after I updated SuperSU from the Play Store, but when I try to CWM Flash a rom it throws an error about the ro.bootloader and it lists out all the older bootloaders. So what I guess I'm getting to is what would it take to use the new bootloaders with any of the ROMs?
bentheexo said:
So I have a question Doc, I know I posted about this in the CM11 unofficial thread as well, but I am running your Non-Knox, CiQ free version and I have CWM installed, and I'm perfectly rooted after I updated SuperSU from the Play Store, but when I try to CWM Flash a rom it throws an error about the ro.bootloader and it lists out all the older bootloaders. So what I guess I'm getting to is what would it take to use the new bootloaders with any of the ROMs?
Click to expand...
Click to collapse
If you have updated to official 4.3 by any means then don't try to downgrade your boot loader and rom as it may brick device
If you have not taken official update then it depends what is your current boot loader and what rom you are trying to flash
So if you are sure that you haven't gone for official update then you flash dmd5 firmware then try to flash rom
Be sure before doing anything
Sent from my SGH-T999 using Tapatalk
I tried to downgrade from 4.3 to 4.1.1 and it soft-bricked my phone after flashing Slim ROM I could use the phone again but nothing works at all.
I don't have audio and can't play video and I can't flash anything with any recovery except certain 4.3 ROMs.
I've been dealing with this for weeks now and still no one has helped me here on XDA if you could please give me a walk through so I can have a useable phone again I'd appreciate it. If I can't get this fixed I'm just going to toss the phone in the trash because it doesn't do anything, play games, videos, music, flash roms, nada.
Update: I tried to "unbrick" it with instructions in the forum and now it's hard bricked. It's already in the trash. No more Samsungs for me.
I hate efuses.
can you get into d/l mode and recovery?
Sent from my SGH-I747M using Tapatalk
Did you try any stock based ROMs? If I can recall right, slim bean is pure android based.
jimchee said:
can you get into d/l mode and recovery?
Sent from my SGH-I747M using Tapatalk
Click to expand...
Click to collapse
Yes I can use the phone and it boots up but everything is broken on it software wise. It's like I flashed an "international" build and now nothing works except I didn't flash international.
diablo009 said:
Did you try any stock based ROMs? If I can recall right, slim bean is pure android based.
Click to expand...
Click to collapse
Every time I try to flash anything but pure android it fails to flash. I tried to odin 4.3 stock and it failed, tried CWM stock 4.3/4.4 flash which failed, tried TWRP stock 4.3 flash which failed. I can't access root yet I installed root. It's a whole list of issues that I have no clue how to fix. It was working perfect before this crap 4.3 bootloader which screwed up my phone.
I forgot to mention that when trying to flash stock it always fails to open the partition and then stops. It's the same for Odin.
Nabbu said:
I forgot to mention that when trying to flash stock it always fails to open the partition and then stops. It's the same for Odin.
Click to expand...
Click to collapse
If I have picked up on the tidbits while surfing, I'd say that you ran afoul of knox.
can you reflash the bootloader?
I seem to recall that there was someone on ebay selling a unbricking service. It involved him doing some soldering inside the back cover and using a piece of machinery (not a PC) to re-flash a basic software package into it. I can't remember where it was, but the service wasn't much
I don't recall specifically what caused this, I'm quite sure it didn't happen after a flash of anything though, which is quote odd.
ATT i747
ROM: http://forum.xda-developers.com/showthread.php?t=1766684
Keneral: http://forum.xda-developers.com/showthread.php?t=1756776
Firmware: I747UCUEMJ2 (As far as I can recall)
I've already tried flashing multiple modems though TWRP. No Luck.
I've gone into recovery (TWRP) and tried a "Factory Reset" and flashing a rom/kernel. No Luck.
I've gone into recovery and tried a very full wipe (pretty much everything except USB-OTG and External SD) and flashing a rom/kernel. No Luck.
I've already tried both of the last two and restoring various backups I had. No Luck.
What additional information would you need to assist me?
Any idea on what I could do to repair this?
I've searched and come across a lot of dead ends.
YoHoJo said:
I don't recall specifically what caused this, I'm quite sure it didn't happen after a flash of anything though, which is quote odd.
ATT i747
ROM: http://forum.xda-developers.com/showthread.php?t=1766684
Keneral: http://forum.xda-developers.com/showthread.php?t=1756776
Firmware: I747UCUEMJ2 (As far as I can recall)
I've gone into recovery (TWRP) and tried a "Factory Reset" and flashing a rom/kernel. No Luck.
I've gone into recovery and tried a very full wipe (pretty much everything except USB-OTG and External SD) and flashing a rom/kernel. No Luck.
I've already tried both of the last two and restoring various backups I had. No Luck.
What additional information would you need to assist me?
Any idea on what I could do to repair this?
I've searched and come across a lot of dead ends.
Click to expand...
Click to collapse
Your modem is probably lost or corrupt. You may try downloading the modem from the link below and flashing via (custom) recovery.
http://www.androidfilehost.com/?fid=23212708291680823
Larry2999 said:
Your modem is probably lost or corrupt. You may try downloading the modem from the link below and flashing via (custom) recovery.
http://www.androidfilehost.com/?fid=23212708291680823
Click to expand...
Click to collapse
Ah forgot to mention, already tried flashing multiple modems with no luck :'(
Thanks for the tip!
YoHoJo said:
Ah forgot to mention, already tried flashing multiple modems with no luck :'(
Thanks for the tip!
Click to expand...
Click to collapse
Why don't you try a full (stock) firmware restore then? If you have MJ2 , you can upgrade to full stock 4.3JB. I also learnt from a very reliable source that you can Odin safely to 4.1.1 from the (modified) MJ2 as long as you don't have the MJB bootloader.
Larry2999 said:
Why don't you try a full (stock) firmware restore then? If you have MJ2 , you can upgrade to full stock 4.3JB. I also learnt from a very reliable source that you can Odin safely to 4.1.1 from the (modified) MJ2 as long as you don't have the MJB bootloader.
Click to expand...
Click to collapse
That's a bit of my question, I'm, not sure what firmware I'm on currently, how can I check?
OR which one is the newest, I can flash from anything to the newest one correct?
I'm ready to do that, but worried on what bootloader I have, and which to flash to safely.
I've seen a lot of old guides, dead guides, 404 DL links, etc :/.
I just don't want to flash anything incorrect in my attempts to repair it, and brick it. :silly:
Boot into download mode and tell us what it says on the screen. This information will determine whether you have a stock 4.3 bootloader on your phone.
Larry2999 said:
Why don't you try a full (stock) firmware restore then? If you have MJ2 , you can upgrade to full stock 4.3JB. I also learnt from a very reliable source that you can Odin safely to 4.1.1 from the (modified) MJ2 as long as you don't have the MJB bootloader.
Click to expand...
Click to collapse
audit13 said:
Boot into download mode and tell us what it says on the screen. This information will determine whether you have a stock 4.3 bootloader on your phone.
Click to expand...
Click to collapse
ODIN MODE
PRODUCT NAME: SGH-I747
CUSTOM BINARY DOWNLOAD: Yes (8 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
QUALCOM SECUREBOOT: ENABLE
Warrenty Bit: 1
BOOTLOADER AP SWEV: 2
Click to expand...
Click to collapse
No bootloader info on there?
That's all it says on download mode.
It looks like you are running the stock 4.3 AT&T bootloader. I based this conclusion of the fact that your warranty counter has been changed to 1 from 0.
I suggest installing the latest version of Philz TOuch via Odin and flash a custom Kit Kat ROM. Try that and see if the modem works.
BTW, you should use the mjb modem as other modems probably won't work.
audit13 said:
It looks like you are running the stock 4.3 AT&T bootloader. I based this conclusion of the fact that your warranty counter has been changed to 1 from 0.
I suggest installing the latest version of Philz TOuch via Odin and flash a custom Kit Kat ROM. Try that and see if the modem works.
BTW, you should use the mjb modem as other modems probably won't work.
Click to expand...
Click to collapse
I've tried flashing a few different ROMs and Modems w/o any luck, I'll try specifically an MJB modem and see what's up.
Mind linking to a thread w/ more info about Philz Touch for att i747? What exatly is this?
Edit:
Seems like Philz Touch is a custom recovery? Why install this when I have latest TWP already?
Edit:
Flashing MJ2 bootloader via TWRP right now, seeing how that goes.
YoHoJo said:
I've tried flashing a few different ROMs and Modems w/o any luck, I'll try specifically an MJB modem and see what's up.
Mind linking to a thread w/ more info about Philz Touch for att i747? What exatly is this?
Edit:
Seems like Philz Touch is a custom recovery? Why install this when I have latest TWP already?
Click to expand...
Click to collapse
I recommend Philz Touch because it is easy to flash it using Odin. I used to have TWRP and had problems flashing ROMs. Once I switched to Philz, I didn't have anymore problems.
The best modem in your case would be the mjb version. Even though the Canadian and US versions of the s3 are identical hardware wise, the bootloaders and modems are not interchangeable.
audit13 said:
I recommend Philz Touch because it is easy to flash it using Odin. I used to have TWRP and had problems flashing ROMs. Once I switched to Philz, I didn't have anymore problems.
The best modem in your case would be the mjb version. Even though the Canadian and US versions of the s3 are identical hardware wise, the bootloaders and modems are not interchangeable.
Click to expand...
Click to collapse
I've used TWRP for a long time/flashed many files without issue, thanks for the suggestion.
So what exactly would you like me to flash though (links would be nice if you could)?
As I've said, I've already tried various ROMs/Modems etc, the problem is deeper than that.
Edit: Flashed MB2
All of the same issues still occur. :'(
SOLVED:
Flashed Firmware:
I747UCUEMJB_2024954_REV04_user_low_ship.tar.md5.zip (I guess this is what you were telling me to do all along huh?)
All good.
Thanks everyone!
YoHoJo said:
I've used TWRP for a long time/flashed many files without issue, thanks for the suggestion.
So what exactly would you like me to flash though (links would be nice if you could)?
As I've said, I've already tried various ROMs/Modems etc, the problem is deeper than that.
Edit: Flashed MB2
All of the same issues still occur. :'(
Flashed Firmware:
I747UCUEMJB_2024954_REV04_user_low_ship.tar.md5.zip (I guess this is what you were telling me to do all along huh?)
All good.
Thanks everyone!
Click to expand...
Click to collapse
Maybe I had issues with TWRP because mine was outdated or perhaps it's just my phone, I'm not sure. I use TWRP on my Nexus 4 and it's perfect.
Glad you got things working:good:
YoHoJo said:
I've used TWRP for a long time/flashed many files without issue, thanks for the suggestion.
So what exactly would you like me to flash though (links would be nice if you could)?
As I've said, I've already tried various ROMs/Modems etc, the problem is deeper than that.
Edit: Flashed MB2
All of the same issues still occur. :'(
SOLVED:
Flashed Firmware:
I747UCUEMJB_2024954_REV04_user_low_ship.tar.md5.zip (I guess this is what you were telling me to do all along huh?)
All good.
Thanks everyone!
Click to expand...
Click to collapse
I flashed the same firmware with Odin and was then able to successfully root and flash my s3 with 4.4.2 PACman. Was having the same issue before this where I had no service, no sound, and YouTube, etc.. wouldn't play.
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!
It's been another few months and still the same problems with all ROMS i try, when the screen is off i lose connection to the mobile network, When i turn the screen back on it will connect and start buzzing and alerting me to every unread message and e-mail Which gets annoying very quickly let alone missing messages and calls.
This happens on CM 12, Pac man rom, GPE and others. Both with 4.4.4 and 5.0. CM 11 works fine for me without this issue.
I see people say they are using these roms without this issue so something is definitely wrong but I can figure out what.
I'm using an Unlocked T mobile s4 on the Wind network In canada
Model SGH-M919
Baseband M919UVUAMDL
You may need to update the baseband a bootloader in order for the phone to work properly with the latest ROMs.
http://www.sammobile.com/firmwares/database/SGH-M919/
audit13 said:
You may need to update the baseband a bootloader in order for the phone to work properly with the latest ROMs.
http://www.sammobile.com/firmwares/database/SGH-M919/
Click to expand...
Click to collapse
Thanks for the reply, before i screw anything up there doesn't appear to be any explicit guides. I'm assuming i use this guide http://forum.xda-developers.com/showthread.php?t=2678774 with the OK3 Rom. beyond this is there anything i should know, like will i have to unlock and root my phone again, or anything like that?
The stock ROMs for the sgh-m919 are here: http://www.sammobile.com/firmwares/database/SGH-M919/
The simplest way to update to the latest bootloader and modem would be to flash the phone back to stock using the above-linked software.
Once you are on the latest stock ROM, flash the latest TWRP to the phone. Once TWRP has been installed, you can flash a custom ROM. Rooting first is not necessary if you intend to run a custom ROM.
audit13 said:
The stock ROMs for the sgh-m919 are here: http://www.sammobile.com/firmwares/database/SGH-M919/
The simplest way to update to the latest bootloader and modem would be to flash the phone back to stock using the above-linked software.
Once you are on the latest stock ROM, flash the latest TWRP to the phone. Once TWRP has been installed, you can flash a custom ROM. Rooting first is not necessary if you intend to run a custom ROM.
Click to expand...
Click to collapse
Sorry for the late update but I got it working thank you.
The FOK3 and FOH3 didn't work for me, once installed it still showed the MDL version. Once i did the FNK2 it worked.
Is there a reason to upgrade to the FOH3 or FOK3 from the FNK2 versions provided i can get them to work?
I always recommend running the latest bootloader and rom but, if the bootloader and modem work without issue, you can hold off.