I had rooted and set up my dad with CM on his AT&T S III a long time ago. I also had nightly updates enabled and he always updated at least once a week. This went on for months until about a week and a half ago that he updated and the phone never came back on.
I have since tried many things and can't get the phone to its original state.
First of all, he had TWRP 2.6 installed and I have downloaded and tried to flash several 4.3 and 4.4 ROM's (including the latest CM nightly) and I always get the error saying the ROM is for a d3att and this device is a "" (just like that). Why? This is a d2att. Bad bootloader?
I then decided to use Kies to go to stock 4.1.2 and start there. First thing I noticed was there was no way to get to Download mode using the vol down + home + power method. I could only get there by removing battery, plugging USB and holding vol down + vol up while reinserting the battery.
Kies flashed 4.1.2 successfully. I then enabled unknown sources and USB debugging and decided to root, install custom recovery and custom ROM, for which I got the latest version of the S3 Toolkit (v7.5).
I am able to flash a custom bootloader (I have tried both "boot-insecure-dlk3-SGHI747.tar" and "boot-insecure-dlk3-recovery-SGHI747.tar" that the Toolkit automatically downloads. However, once this is done and I am getting ready to flash a custom recovery, Odin either crashes or fails. I have tried 3 different versions of Odin (3.04, 3.07, 3.09) with the same results. It does see the device, but it just doesn't work after the bootloader is flashed.
The phone is in Download mode and looks good (CUSTOM BINARY DOWNLOAD: YES(1 count), CURRENT BINARY: CUSTOM). However, there is no flashing a recovery. I have tried a couple of versions of CWM, touch and non touch, as well as TWRP. All with the same results.
So I decided to go start over with Kies. I did and the same exact thing happened.
Can anyone please help me troubleshoot this problem for my dad?
Thanks a lot!
Nobody? =\
Razor1973 said:
I had rooted and set up my dad with CM on his AT&T S III a long time ago. I also had nightly updates enabled and he always updated at least once a week. This went on for months until about a week and a half ago that he updated and the phone never came back on.
I have since tried many things and can't get the phone to its original state.
First of all, he had TWRP 2.6 installed and I have downloaded and tried to flash several 4.3 and 4.4 ROM's (including the latest CM nightly) and I always get the error saying the ROM is for a d3att and this device is a "" (just like that). Why? This is a d2att. Bad bootloader?
I then decided to use Kies to go to stock 4.1.2 and start there. First thing I noticed was there was no way to get to Download mode using the vol down + home + power method. I could only get there by removing battery, plugging USB and holding vol down + vol up while reinserting the battery.
Kies flashed 4.1.2 successfully. I then enabled unknown sources and USB debugging and decided to root, install custom recovery and custom ROM, for which I got the latest version of the S3 Toolkit (v7.5).
I am able to flash a custom bootloader (I have tried both "boot-insecure-dlk3-SGHI747.tar" and "boot-insecure-dlk3-recovery-SGHI747.tar" that the Toolkit automatically downloads. However, once this is done and I am getting ready to flash a custom recovery, Odin either crashes or fails. I have tried 3 different versions of Odin (3.04, 3.07, 3.09) with the same results. It does see the device, but it just doesn't work after the bootloader is flashed.
The phone is in Download mode and looks good (CUSTOM BINARY DOWNLOAD: YES(1 count), CURRENT BINARY: CUSTOM). However, there is no flashing a recovery. I have tried a couple of versions of CWM, touch and non touch, as well as TWRP. All with the same results.
So I decided to go start over with Kies. I did and the same exact thing happened.
Can anyone please help me troubleshoot this problem for my dad?
Thanks a lot!
Click to expand...
Click to collapse
First of all, I'd say (from my experience) screw Kies. Go straight to flashing the STOCK ROOTED S3 files. Do NOT load any custom bootloaders or anything. This is step one, using Odin to get back to stock root. Here is a link to a tutorial (in case you need it, it has the files too): Click Here
Now once you finish that, go ahead and use Odin to flash the latest CWM or TWRP (up to your preference, I use TWRP). To get the latest TWRP for Odin, go HERE.
After you have the custom recovery, you should make a Nandroid backup in TWRP. Also, at this step, for the love of your sanity teach your dad how to make a backup. This might save you down the road
Now that you have a backup and are rooted, you can start flashing the roms. Make sure that you do NOT flash any bootloader OR modem unless they are the I747UCDMG2 ones. IF you flash those you will be fine.
Hope this helps!
Well, I had no choice by to use Kies because ODIN would always fail or crash. Only after I flashed using Kies could I use ODIN successfully. So I just flashed using Kies again, which allowed me to ODIN (3.07) the AT&T file in that thread you gave me. However, ODIN fails a few seconds into the flash with the following error. Any other ideas? Thank you for the help.
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_ATT_I747UCDLK3.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> boot.img
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
By the way, phone won't boot up and ODIN will crash or any other attempt, as you can see in my second screenshot (same condition I was describing in my OP). It looks like it goes past the boot flash, but crashes on cache. So I need to flash via Kies again. It's been the only way I can start all this over.
In case it makes a difference, before the first ODIN attempt, the download mode read "CURRENT BINARY: SAMSUNG" and after it failed, download mode read "CURRENT BINARY: CUSTOM".
Here's a link to the latest 4.3 stock image for the d2att (Always have it on my desktop) [use the first download link]
http://forum.xda-developers.com/showthread.php?t=2498233 try flashing that in Odin I'm the PDA and you should be stock 4.3 with no root and you can start over from there
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
xSharpi said:
Here's a link to the latest 4.3 stock image for the d2att (Always have it on my desktop) [use the first download link]
http://forum.xda-developers.com/showthread.php?t=2498233 try flashing that in Odin I'm the PDA and you should be stock 4.3 with no root and you can start over from there
Click to expand...
Click to collapse
These are flashabe through recovery, not ODIN. Both bootloader and ROM files are ZIP's and ODIN expects TAR, MD5, SMD, GZ or TGZ in the PDA section.
As I had mentioned, I cannot flash anything through a custom recovery (and I've tried several, including TWRP and CWM) because the recovery complains that the ROM is for a d2att and my device isn't. My device *is* a d2att, only that CM nightly flashed something to it that makes it identify itself as something different, it sounds like.
I really am stuck. So far, the only ROM I have been able to flash is stock 4.1.2 using Kies and nothing after that.
Any other ideas please???
Maybe you should use Kies, go full stock and then root stock. From there, use GooManager or ROM Manager (I think that's the name) to get custom recovery
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4
A couple things to try. Try using an older Odin I think it was 1.85 and see if that will work for you. Then flash the 4.1.2 stock Odin package. Once it is done reboot to stock recovery and do a FULL WIPE and then flash with Odin again. Let it boot up completely without touching anything. Then install twrp via Odin. Then flash the LEAKED 4.3 bootloader. I would suggest NOT to flash the MJB bootloader if at all possible. Then flash a 4.3 MJB ROM (WITHOUT FLASHING BOOTLOADERS). Also you will need to flash a modem to MJB in recovery to get WiFi and such to work.
I think the first time that you were able to flash the Odin 4.1.2 you missed doing a factory reset/full wipe. I believe that is needed when coming from CM.
IF ALL ELSE FAILS you may need to find the correct pit file and flash that in Odin. I think CM changes some partitions and why it did not boot up the first time you flashed stock 4.1.2
Sent From My Spiderman,Ironman,Red,Dark Blue,Green, GreyedOut BadAss Themed I337
xXshur1kenXx said:
Maybe you should use Kies, go full stock and then root stock. From there, use GooManager or ROM Manager (I think that's the name) to get custom recovery
Click to expand...
Click to collapse
I just used Kies to flash to stock 4.1.2 successfully (which has always been the case) and then the S3 Toolkit 7.5 to root (screenshots). After the last step, the phone doesn't boot up (same thing always happens when I try to root), so I can't install GooManager or ROM Manager. However, I am able to get into stock recovery, so I will try to follow steps RockRatt recommends and report again. Thank you.
RockRatt said:
A couple things to try. Try using an older Odin I think it was 1.85 and see if that will work for you. Then flash the 4.1.2 stock Odin package. Once it is done reboot to stock recovery and do a FULL WIPE and then flash with Odin again. Let it boot up completely without touching anything. Then install twrp via Odin. Then flash the LEAKED 4.3 bootloader. I would suggest NOT to flash the MJB bootloader if at all possible. Then flash a 4.3 MJB ROM (WITHOUT FLASHING BOOTLOADERS). Also you will need to flash a modem to MJB in recovery to get WiFi and such to work.
I think the first time that you were able to flash the Odin 4.1.2 you missed doing a factory reset/full wipe. I believe that is needed when coming from CM.
IF ALL ELSE FAILS you may need to find the correct pit file and flash that in Odin. I think CM changes some partitions and why it did not boot up the first time you flashed stock 4.1.2
Click to expand...
Click to collapse
I think I just bricked my dad's d2att. I tried everything under the sun and decided to flash the pit, which I searched all over the place and could find in this thread, where it reads "16gb AT&T SGSIII PIT." I flashed it successfully through ODIN and that's it. Phone won't do anything else. No way to get it to download mode, no SAMSUNG logo, no vibration, no flash. After attempting for 3 days in a row, I think I finally screwed the phone.
Razor1973 said:
I think I just bricked my dad's d2att. I tried everything under the sun and decided to flash the pit, which I searched all over the place and could find in this thread, where it reads "16gb AT&T SGSIII PIT." I flashed it successfully through ODIN and that's it. Phone won't do anything else. No way to get it to download mode, no SAMSUNG logo, no vibration, no flash. After attempting for 3 days in a row, I think I finally screwed the phone.
Click to expand...
Click to collapse
Yikes. Tbh I've never heard of a pit file so I can't tell you what that did. Have you tried forcing into download mode with a battery pull? Also does the phone still charge?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
xXshur1kenXx said:
Yikes. Tbh I've never heard of a pit file so I can't tell you what that did. Have you tried forcing into download mode with a battery pull? Also does the phone still charge?
Click to expand...
Click to collapse
The battery pull was the only method I could get to download mode and it no longer works. I also don't know if the phone charges, as it shows no signals of life. Damn pit file! I may have no choice but to send it for JTAG repair ($).
Razor1973 said:
The battery pull was the only method I could get to download mode and it no longer works. I also don't know if the phone charges, as it shows no signals of life. Damn pit file! I may have no choice but to send it for JTAG repair ($).
Click to expand...
Click to collapse
I'd say that's the safe bet. Or you can get a new phone if it costs less to just do a new contract or line
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Sorry to hear that. That is why I said AT LAST RESORT. The pit file should fix part I on issues and the only reason I mentioned it. I haven't used CM since my S2 days so not sure what they change as far as the partitions but I have read enough issues with people trying to come back to tw from cm and having issues.
As far as JTAG I recommend MobileTechVideos. I used them on my S1 back in the day and then when I screwed up my S4 when it was not even 7 days old I screwed up with a kernel that hard bricked my phone. Sent it to MobileTechVideos and they brought it back to life for me.
Sent From My Spiderman,Ironman,Red,Dark Blue,Green, GreyedOut BadAss Themed I337
xXshur1kenXx said:
I'd say that's the safe bet. Or you can get a new phone if it costs less to just do a new contract or line
Click to expand...
Click to collapse
It's my dad's phone. LOL
RockRatt said:
Sorry to hear that. That is why I said AT LAST RESORT. The pit file should fix part I on issues and the only reason I mentioned it. I haven't used CM since my S2 days so not sure what they change as far as the partitions but I have read enough issues with people trying to come back to tw from cm and having issues.
As far as JTAG I recommend MobileTechVideos. I used them on my S1 back in the day and then when I screwed up my S4 when it was not even 7 days old I screwed up with a kernel that hard bricked my phone. Sent it to MobileTechVideos and they brought it back to life for me.
Click to expand...
Click to collapse
What are you apologizing for??? God, no. It was me who bricked the phone, not you!
I'm about to leave the house and go to this really good cellular repair shop very close to me to see if they do JTAG repairs. I was going anyways to take my original Nexus 7 for a screen replacement. I tried to do it and screwed it up too. hahahaha
Razor1973 said:
It's my dad's phone. LOL
Click to expand...
Click to collapse
My mistake. Meant to say if he could haha. Sorry i couldn't help more. Hope the JTAG works!
Sent from my SAMSUNG-SGH-I747 using Tapatalk
You have been very helpful. Guy doesn't do JTAG repairs. I will keep calling shops in town. If none does, I will ship it. Thanks!
For JTAG repair, have you checked this site? You still have to send the phone in, though.
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-iii/
Related
my phone is stuck on the "firmware update issue, use kies" screen, those arent the exact words but thats the gist of that screen. cant access recovery so i went to download mode and tried to flash a bunch of stock firmware tar,md5's different stock versions incuding the recommended root66 version, everytime i try to flash a pda with odin it says fail after modem.bin, so i thought after like 30 tries that its having issues with the modem.bin, so i went on tesh's stock modem page and tried to flash the modem.bin through phone section of odin, once again it starts and then says fail. i really dont know what the issue is i just cant seem to go back to stock, i feel is just bricked, even though im able to use odin and download mode
Tanvirul said:
my phone is stuck on the "firmware update issue, use kies" screen, those arent the exact words but thats the gist of that screen. cant access recovery so i went to download mode and tried to flash a bunch of stock firmware tar,md5's different stock versions incuding the recommended root66 version, everytime i try to flash a pda with odin it says fail after modem.bin, so i thought after like 30 tries that its having issues with the modem.bin, so i went on tesh's stock modem page and tried to flash the modem.bin through phone section of odin, once again it starts and then says fail. i really dont know what the issue is i just cant seem to go back to stock, i feel is just bricked, even though im able to use odin and download mode
Click to expand...
Click to collapse
What version of ODIN? Should be version 3-something I think - I feel like earlier versions of ODIN run into the modem.bin fail though.
That screen will still work the same as the other screen.. it has a pic of a pc and phone... As for the error try a different usb cable and/or port. Also like dwith said make sure your using the 3.xx version of odin
Sent from my SGH-T889 using Tapatalk 2
Let me just say I have been in this business long enough and it has been a while since I have been in a situation like this. So I'm running the project x port. And I want to upgrade to official 4.4. I download the tar and try to Odin it. I get this PIT error, like it requires the PIT file for something. Long story short I have been trying to flash the stock 4.3 rom and original PIT, stock 4.4 and kk Pit file. So they all keep failing and I tried ode and heimdall. Every time there is a Pit error and it won't go further.
I thought I had a 800 dollar brick with all this flashing but it boots up fine and works fine. I did not expect that to happen. And I can't boot to recovery.
So my question is:Anyone else have this experience?
Anyone have a solution?
Know why or what caused this?
How to go from project x to the newest ota?
Thanks
Sent from my SM-N900T using xda app-developers app
midnight93933 said:
Let me just say I have been in this business long enough and it has been a while since I have been in a situation like this. So I'm running the project x port. And I want to upgrade to official 4.4. I download the tar and try to Odin it. I get this PIT error, like it requires the PIT file for something. Long story short I have been trying to flash the stock 4.3 rom and original PIT, stock 4.4 and kk Pit file. So they all keep failing and I tried ode and heimdall. Every time there is a Pit error and it won't go further.
I thought I had a 800 dollar brick with all this flashing but it boots up fine and works fine. I did not expect that to happen. And I can't boot to recovery.
So my question is:Anyone else have this experience?
Anyone have a solution?
Know why or what caused this?
How to go from project x to the newest ota?
Thanks
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
It simple download stock 4.3 flash that. Wipe wipe wipe. Then download the official 4.4.2 then root and so forth. Don't cheat and get modded 4.4.2. Go to sammymobile and download original and install thru Odin. A few videos in threads show how
TWEAKED 2.0 ELEMENT V3.0 NOTE 3
midnight93933 said:
Let me just say I have been in this business long enough and it has been a while since I have been in a situation like this. So I'm running the project x port. And I want to upgrade to official 4.4. I download the tar and try to Odin it. I get this PIT error, like it requires the PIT file for something. Long story short I have been trying to flash the stock 4.3 rom and original PIT, stock 4.4 and kk Pit file. So they all keep failing and I tried ode and heimdall. Every time there is a Pit error and it won't go further.
I thought I had a 800 dollar brick with all this flashing but it boots up fine and works fine. I did not expect that to happen. And I can't boot to recovery.
So my question is:Anyone else have this experience?
Anyone have a solution?
Know why or what caused this?
How to go from project x to the newest ota?
Thanks
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
Go to dev section and download the tar. Put phone in download mode. Odin 3.7 or 3.9 your choice load the tar in the "AP" section and hit start. It may fail the first time. Did for me, and pretty much everybody else. Don't freak. If at first you don't succeed. So boot back into download mode and run the process a second time, this time it will go all the way through and you will have a nice clean Kitty Kat Phone.
When I flash in odin I NAND write start! then a big FAIL
So i think my phone is a zombie.. I can boot into recovery and into the system and actually do stuff its just really slow and bugs out. I have never seen a phne do this before help?
Alright I figured out my bonehead move. It flashed fine now.
Well, I used have Cyanogenmod but then my 4g wasn't working so I tried to flash stock rom on Odin but it didn't work so my friend helped me get it some other way and currently I have stock rom with root access, but the problem is I noticed recently that my battery life sucks! I was at the store and I checked my phone and it was at 60% then I pressed the sleep button and when I checked 15 minutes later I was at 5%! Today, I downloaded and flashed Clockworkmod via Rom Manager and when that I rebooted, at first it showed Samsung Galaxy S III and under that it was the little Cyanogenmod dude then it turned off and rebooted by itself but then the little guy didn't appear again, my best guess is that stock rom is running under Cyanogenmod which causes battery loss (also when im using it, it seems that 1% goes down every minute) can someone tell me if i'm wrong? I want to get Cyanogenmod again and see if it still has problems with 4g because Cyanogenmod is 1000 times better than stock rom, please help me?
EDIT: So I flashed TWRP since my friend told me it was better and the little Cyanogenmod dude came up while rebooting into recovery mode, then I was in the TWRP menu after that, I then rebooted back onto the system and the little dude didn't come up, so my guess that stock running over cyanogenmod still stands.
C'mon! Nobody has any answers, tips, or anything?
Not sure what you mean when you say "stock rom is running under Cyanogenmod" but you are either running a stock ROM or CM. I've never seen a situation where the operating system was a combination of stock and CM after flashing.
audit13 said:
Not sure what you mean when you say "stock rom is running under Cyanogenmod" but you are either running a stock ROM or CM. I've never seen a situation where the operating system was a combination of stock and CM after flashing.
Click to expand...
Click to collapse
yeah, my friend is helping me get complete stock again, but I got a fail in Odin - <ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
do you know what it is?
I'm assuming the 'dude' you're talking about is the clockworkmod boot animation... It only appears when booting into clockworkmod recovery in order to flash something. You won't see it when booting into system or at all now that you're on twrp instead of clockworkmod. To find out what ROM you're on (can't be both) go into system settings and click 'About Device'. The build number will have your ROM version.
As for the battery issue it sounds like you have a bad wakelock problem. An app called betterbatterystats can help you find out what's causing it. Probably something to do with flashing back and forth between stock and cyanogenmod without doing a factory reset.
Sent from my SAMSUNG-SGH-I747 running TMS3KK-2.0
Viper67857 said:
I'm assuming the 'dude' you're talking about is the clockworkmod boot animation... It only appears when booting into clockworkmod recovery in order to flash something. You won't see it when booting into system or at all now that you're on twrp instead of clockworkmod. To find out what ROM you're on (can't be both) go into system settings and click 'About Device'. The build number will have your ROM version.
As for the battery issue it sounds like you have a bad wakelock problem. An app called betterbatterystats can help you find out what's causing it. Probably something to do with flashing back and forth between stock and cyanogenmod without doing a factory reset.
Sent from my SAMSUNG-SGH-I747 running TMS3KK-2.0
Click to expand...
Click to collapse
The battery part was good info to me, thanks. Now, the dude is the blue cyanogenmod android guy, i'm 100% sure. I also downloaded and flashed TWRP and the blue cyanogenmod android dude still appears before going into recovery mode. My model number is JSS15J.1747UCUEMJB if that helps. :/
That's the 4.3 stock rom that you're running. What are you trying to flash in Odin? If it's below 4.3 it will fail, fortunately for you, because downgrading the bootloader from mjb or above will brick your phone. Try downloading a recovery flashable rom, either stock 4.3, 4.4.2, or cm11. Wipe system, dalvik, cache, and data and flash in twrp. If you go with stock 4.4.2 you'll also need ktoonsez kernel for wifi to work on your mjb bootloader.
As for the blue dude, I was thinking of the green animated android in cwm. I get the blue dude too when booting to recovery, but only for like a second and I don't use cyanogenmod. I can't remember if that was there with stock recovery or not, I've been on custom and rooted since I got the phone, but I do know it's there no matter if you're on touchwiz or aosp.
Sent from my SAMSUNG-SGH-I747 running TMS3KK-2.0
Viper67857 said:
That's the 4.3 stock rom that you're running. What are you trying to flash in Odin? If it's below 4.3 it will fail, fortunately for you, because downgrading the bootloader from mjb or above will brick your phone. Try downloading a recovery flashable rom, either stock 4.3, 4.4.2, or cm11. Wipe system, dalvik, cache, and data and flash in twrp. If you go with stock 4.4.2 you'll also need ktoonsez kernel for wifi to work on your mjb bootloader.
As for the blue dude, I was thinking of the green animated android in cwm. I get the blue dude too when booting to recovery, but only for like a second and I don't use cyanogenmod. I can't remember if that was there with stock recovery or not, I've been on custom and rooted since I got the phone, but I do know it's there no matter if you're on touchwiz or aosp.
Sent from my SAMSUNG-SGH-I747 running TMS3KK-2.0
Click to expand...
Click to collapse
Haha, I will try tomorrow thank you!
This message appears in Odin when trying to downgrade the bootloader:
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
audit13 said:
This message appears in Odin when trying to downgrade the bootloader:
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
Click to expand...
Click to collapse
Viper67857 said:
That's the 4.3 stock rom that you're running. What are you trying to flash in Odin? If it's below 4.3 it will fail, fortunately for you, because downgrading the bootloader from mjb or above will brick your phone. Try downloading a recovery flashable rom, either stock 4.3, 4.4.2, or cm11. Wipe system, dalvik, cache, and data and flash in twrp. If you go with stock 4.4.2 you'll also need ktoonsez kernel for wifi to work on your mjb bootloader.
As for the blue dude, I was thinking of the green animated android in cwm. I get the blue dude too when booting to recovery, but only for like a second and I don't use cyanogenmod. I can't remember if that was there with stock recovery or not, I've been on custom and rooted since I got the phone, but I do know it's there no matter if you're on touchwiz or aosp.
Sent from my SAMSUNG-SGH-I747 running TMS3KK-2.0
Click to expand...
Click to collapse
Well I successfully have CM11 20140217 Nightlies and my mobile data was not working, so I messed around in the APNs settings and I changed from the LTE one (my sim card doesnt support lte) onto all the other ones and only one works but I get H, sometimes H+, and very very rarely 3g for like a second. Is there any way for me to get 4G again? Please help me..
H+ is 4g
Sent from my SAMSUNG-SGH-I747 running TMS3KK-2.0
Viper67857 said:
H+ is 4g
Sent from my SAMSUNG-SGH-I747 running TMS3KK-2.0
Click to expand...
Click to collapse
oh how dumb of me, so it seems everything is fine! thank you all so much!
I tried rooting my phone on 4.2.2 but ended up bricking without having a nandroid backup. So i downloaded stock UVUAMDB tar from k0nane thread and it flashed without any issues through odin. However, my baseband version now is UVUAMBF and my build number is UVUAMDB. Is this normal? I also can't connect to wifi and every other rom i flash fails on ODIN. I can flash any recovery but can't flash any other rom except the MDB tar file. Also tried downloading the UVUAMDL and flashed it but still failed on ODIN. Can someone please help with this? I have been trying to fix for 2 days now. Please help!!
What is your model number?
serio22 said:
What is your model number?
Click to expand...
Click to collapse
It is SGH-M919. Thanks for responding. Hope my phone is not totally useless now.
Can you link to the firmware you flashed? That build and baseband isn't even for the M919.. Have you tried flashing latest NB4 firmware?
serio22 said:
Can you link to the firmware you flashed? That build and baseband isn't even for the M919.. Have you tried flashing latest NB4 firmware?
Click to expand...
Click to collapse
I flashed the stock tar from this thread:
http://forum.xda-developers.com/showthread.php?t=2258628
I have attached a screenshot of the about device section of my phone.
hyperenigma said:
I flashed the stock tar from this thread:
http://forum.xda-developers.com/showthread.php?t=2258628
I have attached a screenshot of the about device section of my phone.
Click to expand...
Click to collapse
Go to Sammobile.com.........get the Official MDL 4.2.2 Firmware. Then you will be fine.
The Sickness said:
Go to Sammobile.com.........get the Official MDL 4.2.2 Firmware. Then you will be fine.
Click to expand...
Click to collapse
Alright. Thanks very much. I'm downloading right now and I'll post back regarding the outcome.
The Sickness said:
Go to Sammobile.com.........get the Official MDL 4.2.2 Firmware. Then you will be fine.
Click to expand...
Click to collapse
So i tried installing the official MDL 4.2.2 via odin but failed. I got this;
<ID:0/010> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> sbl2.mbn
<ID:0/010> NAND Write Start!!
<ID:0/010>
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any reason why? Thanks once again
Do you have kies installed? It could also be because of your firmware that I have no idea how it was flashed. What does it show when you enter download mode?
serio22 said:
Do you have kies installed? It could also be because of your firmware that I have no idea how it was flashed. What does it show when you enter download mode?
Click to expand...
Click to collapse
In download mode, it says,
ODIN MODE
PRODUCT NAME: SGH-M919
CUSTOM BINARY DOWNLOAD: YES
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
QUALCOMM SECUREBOOT: ENABLE
That's all it says. Recovery and everything else flashes in ODIN except modems and roms. Also in custom recovery using TWRP, it says error can't mount system. Don't know what's wrong. Plug into kies and says that's the latest firmware. Trying to update ota but can't because of my flash counter I think.
serio22 said:
Do you have kies installed? It could also be because of your firmware that I have no idea how it was flashed. What does it show when you enter download mode?
Click to expand...
Click to collapse
Also, something weird happened in that I tried rooting using CF ROOT and I succeeded but when I click superuser, it says KNOX is enabled and that it will disable it. Am I supposed to have KNOX on 4.2.2? These all makes no sense to me.
serio22 said:
Do you have kies installed? It could also be because of your firmware that I have no idea how it was flashed. What does it show when you enter download mode?
Click to expand...
Click to collapse
Please help. I don't even know what else to do right now. Can I flash a kernel or pit file or something. Just bought this 3 days ago.
Uninstall kies and flash MDL firmware, also try different Odin versions, USB ports, even computer if that doesn't work. What was the initial root method you used?
serio22 said:
Uninstall kies and flash MDL firmware, also try different Odin versions, USB ports, even computer if that doesn't work. What was the initial root method you used?
Click to expand...
Click to collapse
I downloaded the CF root file for the tmobile s4. I'll try your suggestions above and get back to you. Thanks.
serio22 said:
Uninstall kies and flash MDL firmware, also try different Odin versions, USB ports, even computer if that doesn't work. What was the initial root method you used?
Click to expand...
Click to collapse
I just tried everything you suggested above and stil no luck. Switched USB ports, switched computers and switched USB cables. Guess I am stuck with this.
hyperenigma said:
I just tried everything you suggested above and stil no luck. Switched USB ports, switched computers and switched USB cables. Guess I am stuck with this.
Click to expand...
Click to collapse
Is all that you want root or do you intend on flashing custom ROM?
serio22 said:
Is all that you want root or do you intend on flashing custom ROM?
Click to expand...
Click to collapse
I just want a ROM that could work with my Samsung gear since it doesn't work on 4.2.2.
hyperenigma said:
I just want a ROM that could work with my Samsung gear since it doesn't work on 4.2.2.
Click to expand...
Click to collapse
Ok and you say you can't flash ROMs with any recovery correct? And they are latest? If so then only thing I can suggest is to see if you can flash 4.4.2 with Odin, search for fenny's NB4 firmware and flash that, after that you can flash recovery and hopefully be able to flash ROMs without issue.. Just remember that it will trip Knox counter once you flash recovery
Im extremely curious where that baseband came from. Cause MDB was the firmware that shipped with the m919 on release. And according to your last 2 Letters of your baseband you have a modem from a firmware that came before MDB that was never shipped with the m919 but the rest MDB. I mean MBF isnt even on Samsungs open source site for ANY m919 variant. So that means MBF wasnt even released to the public or someone like me would of emailed for release of the source like I just did for GNG8.
You said you got it 3 days ago right? Did it come from a Samsung or Tmobile employee or something?
Anyways. Your getting the notification about knox cause theres a few knox files on 4.2.2 just basically not doing anything and SuperSu is detecting them. Your odin is failing on the bootloader (SBL/Samsung Boot Loader) Just for curiosity purposes can you download android terminal emulator and type getprop ro.bootloader and press enter post what version it says?
Since odin is failing, Id try Heimdall.
ShinySide said:
Im extremely curious where that baseband came from. Cause MDB was the firmware that shipped with the m919 on release. And according to your last 2 Letters of your baseband you have a modem from a firmware that came before MDB that was never shipped with the m919 but the rest MDB. I mean MBF isnt even on Samsungs open source site for ANY m919 variant. So that means MBF wasnt even released to the public or someone like me would of emailed for release of the source like I just did for GNG8.
You said you got it 3 days ago right? Did it come from a Samsung or Tmobile employee or something?
Anyways. Your getting the notification about knox cause theres a few knox files on 4.2.2 just basically not doing anything and SuperSu is detecting them. Your odin is failing on the bootloader (SBL/Samsung Boot Loader) Just for curiosity purposes can you download android terminal emulator and type getprop ro.bootloader and press enter post what version it says?
Since odin is failing, Id try Heimdall.
Click to expand...
Click to collapse
I bought it from a guy brand new. The phone was working perfectly fine when I purchased and there was no issues at all. I tried to flash a custom rom with 4.4.2 on the phone after rooting and everything just got messed up. Didn't check the baseband version then so I am not 100 percent sure about that as well. When I downloaded terminal emulator and did as you suggested, I got
M919UVUAMBF
I tried heimdall but don't know where to get the firmware package for the m919. Please any assistance will be very much appreciated at this point. Thank you very much
Hi everyone, looking for some guidance here. Ive checked different solutions but I think I've got a unique combination of "dun goof'd"
History:
I have a Canadian (Bell) SGH-I747M that is rooted and was running the latest cyanogen.
Wanted to lend it to a friend who lost his job and needed a phone but he had a deal through rogers and my phone was locked to Bell.
I tried a few of the unlock code steps but I needed to be 4.1.2 or lower for it to work I heard so I tried installing 4.1.2 and thats where it went wrong. I did a firmware update to back it down and mid update it failed.
I can get it into download mode but not recovery. Letting it boot normally gives the message "Firmware upgrade encountered an issue. Please select recovery mode in Keys and try again" I don't think Keys works with cyanogen and even if it did, there is no serial # sticker behind the battery and since I can't boot into settings, I don't know the SN.
When I put it in download mode and try Odin using stockROMS.net oldest or newest image, Odin fails and the phone message is:
ODIN SW REV CHECK FAIL : Fused 2 > Binary 0
So long story short, any help is sincerely appreciated, my ideal state would be a working phone thats unlocked so my buddy can use it. IF that means an older OS, all good. Can I even fix this?? If you need more info I'll keep checking in... THANKS!
You cannot downgrade if your phi e has ever had the 4.3 or higher bootloader.
Fix the phone by booting into download mode and flashing the latest stock rom from sammobile.com.
I can boot into download mode but Odin is erroring out.
I tried the sam mobile stock rom and another, I tried another usb cable and different port.
SGH-I747M (Canada) Bell 4.4.2 KitKat I747MVLUFNH2 2014 July
The error on ODIN is:
<ID:0/004> Firmware update start..
<ID:0/004> sbl2.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl3.mbn
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1
Error on the phone is SW REV CHECK FAIL : FUSED 2 > Binary 0
You must be flashing an older bootloader because it fails when it gets to aboot.mbn.
Im following this thread... Odin still errors out and I'm using the most current bootloader (I think) for the S3 I747M on Bell
http://forum.xda-developers.com/showthread.php?t=2549068
Are your trying to flash a 4.1.1 or 4.1.2 rom? Can't be done if you have a 4.3 or newer bootloader.
audit13 said:
Are your trying to flash a 4.1.1 or 4.1.2 rom? Can't be done if you have a 4.3 or newer bootloader.
Click to expand...
Click to collapse
4.3 ROM, newest one.
The newest ROM is 4.4.2.
What bootloader version is on your phone?
How do I tell??
Try flashing a stock 4.3 ROM from sammobile.com for your i747m.
If Odin fails when flashing aboot.mbn, it's probably because the 4.3 ROM you are trying to flash has an older bootloader that the one currently on your phone.
If flashing the 4.3 ROM via Odin fails, copy the latest CM11 ROM and the corresponding Gapps to your internal or external memory, flash the latest Philz Touch recovery for the d2lte via Odin, boot into recovery, flash CM11, Gapps, boot, install Samsung Phone Info App, run app, look for the bootloader and modem version.
audit13 said:
Try flashing a stock 4.3 ROM from sammobile.com for your i747m.
If Odin fails when flashing aboot.mbn, it's probably because the 4.3 ROM you are trying to flash has an older bootloader that the one currently on your phone.
If flashing the 4.3 ROM via Odin fails, copy the latest CM11 ROM and the corresponding Gapps to your internal or external memory, flash the latest Philz Touch recovery for the d2lte via Odin, boot into recovery, flash CM11, Gapps, boot, install Samsung Phone Info App, run app, look for the bootloader and modem version.
Click to expand...
Click to collapse
I tried Philz and I can boot into recovery now Progress!
That being said the CM11 is stuck on the boot logo animation, tried re-installing as well as the CM Nightly same result.
Did full wipe etc still stuck.
Are you wiping the cache, system, and data before flashing CM11 for the d2lte? Are you running the latest version of Philz?
Try CM12 if CM11 doesn't work.