Related
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/
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,
Couple days ago, I decided to root my unused android phone. Everything was working great. Yesterday, I had a OTA update file. I pressed cancelled/put it on hold, but when I woke up this morning, i see my phone installing 29% with the samsung logo, then it said failed. It would be loop this over and over again. I managed to get access to recovery boot using flash rom. I wiped my cache, full factory reset. Now, it just reboots and keeps on entering recovery mode. I did not know that even after wiping data, my phone is still rooted. I tried unrooting using this method using a MD5 file. I couldnt link the site, but I used this method ""[Guide UPDATED] How to Unroot your AT&T Galaxy S3 (Return To Stock I747UCDLK3 JellyBean )""' but it said failed when I tried to write the flash rom onto the phone. Is my phone completely done? How can i fix this? Please help. Thank you
My s3 is an AT&T variant. SGH-I747
What bootloader was on the phone before the OTA update?
You could try flashing a custom recovery and then flashing a custom ROM. This should at least get your phone booted.
audit13 said:
What bootloader was on the phone before the OTA update?
You could try flashing a custom recovery and then flashing a custom ROM. This should at least get your phone booted.
Click to expand...
Click to collapse
Sorry, I am not really sure. I am new to this. Is there a way to check? My phone was stock. I did a full factory reset before I rooted the phone. Next day, it try auto updated and here I am now.
Do you have a custom rom you recommend?
I managed to flash the CWM recovery into the phone, but when I tried to flash a custom rom which is stock rooted, it says failed. Even with CWM on the phone, I can only access CWM recovery or download mode. Restarting phone loops CWM recovery
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Does cwm have a built in terminal emulator like twrp? If so, use it and enter this:
getprop ro.bootloader
If it is a newer version, it is probably why Odin is failing. (Depending on the version it may also explain why it won't flash your custom rom. What error does it show when it fails BTW? ) If it is not, make sure kies is NOT on your computer. Try a different USB cable and USB port.
Also, What version of cwm are you using and what rom did you try?
Sent from my SGH-T999 using Tapatalk
Looks like you are using Odin to flash a custom ROM which cannot be done. Use CWM to flash the custom ROM.
DocHoliday77 said:
Does cwm have a built in terminal emulator like twrp? If so, use it and enter this:
getprop ro.bootloader
If it is a newer version, it is probably why Odin is failing. (Depending on the version it may also explain why it won't flash your custom rom. What error does it show when it fails BTW? ) If it is not, make sure kies is NOT on your computer. Try a different USB cable and USB port.
Also, What version of cwm are you using and what rom did you try?
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I am using CWM 6 touch. I tried flashing the stock rom from sanmobile but it keeps failing. My odin version is 3.10.7. I am trying cwm flashing now.
Edit: There's only an option to flash from a zip file so I kept my stock rom in a zip filed. Tried it and it says can't open file. Aborted
Oh OK, you're referring to the stock firmware. Sorry, I'm used to differentiating between the two. Stock firmware is what you are using, and I've always considered stock rom to be just the system and kernel like custom roms.
Odin is primarily just for flashing the full stock firmware. You cannot flash that in recovery. You'll need to figure out exactly what build you were on previously by using the terminal emulator command I mentioned before. If cwm doesn't have a built in terminal emulator, you can flash twrp instead and use it.
I suspect you may be on a newer build than LK3, which may explain why odin won't flash it.
I do not suggest trying to flash a custom rom at this point. If any part of the base firmware was corrupted due to the incomplete ota, it is possible for it to hard brick if you try to boot into the system before flashing it correctly. This is still possible no matter what you try to do. It just depends on where the OTA failed. with a little luck this won't happen, but I thought you should be aware of the possibilty anyway.
The safest way to proceed is to first find out exactly what build is on the device. Then we will be able to determine what you should be trying to flash and how.
I hope I'm not confusing things even more for you BTW! If you need anything cleared up just let us know.
Sent from my SGH-T999 using Tapatalk
I have flashed the newest twrp onto the phone. Is the terminal emulator the "terminal command"? How would I check which build am I on?
Sorry, really new to this.
Yes, that's it. I think you might need to select a folder or something, if so just stay at the root directory. At the command line, enter
getprop ro.bootloader
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
Yes, that's it. I think you might need to select a folder or something, if so just stay at the root directory. At the command line, enter
getprop ro.bootloader
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
It gave me I1747UCUFNE4
Ok, it sounds like it's updated at least partially to NE4. You cannot flash anything older than that which is why you couldn't get Odin to work.
Your best bet is to go to enewman17's thread for NE4 and flash following his instructions. This will finish what the OTA started and should fix the device.
http://forum.xda-developers.com/showthread.php?p=53984772
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
Ok, it sounds like it's updated at least partially to NE4. You cannot flash anything older than that which is why you couldn't get Odin to work.
Your best bet is to go to enewman17's thread for NE4 and flash following his instructions. This will finish what the OTA started and should fix the device.
http://forum.xda-developers.com/showthread.php?p=53984772
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
How do I flash the zip flash? I unzipped and did not see any files I can load on odin. I tried using external sd on twrp but it failed. This is what it said.
Checking for MD5 file..
Skipping MD5check: no MD5 file found
assert failed: getprop("ro.bootloader") == "I747UCALEM"
[] getprop("ro.bootloader") == "I747UCALG1"
[] getprop("ro.bootloader") == "I747UCDLK3"
[] getprop("ro.bootloader") == "I747UCDMG2"
[] getprop("ro.bootloader") == "I747UCUEMJ2"
[] getprop("ro.bootloader") == "I747UCUEMJB"
E: error executing updater binary in zip '/external_sd/d2att_I747UCUEMJB_bootloader_modem_4.3.zip'
error flashing
updating partition details...
done
I think you got the wrong one. That says you are trying to flash MJB. You need to flash the NE4 bootloader/modem package, and probably the system/kernel one too.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
I think you got the wrong one. That says you are trying to flash MJB. You need to flash the NE4 bootloader/modem package, and probably the system/kernel one too.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I have just tried the NE4 file on twrp, it gives me a
Checking for MD5 file..
Skipping MD5check: no MD5 file found
assert failed: getprop("ro.bootloader") == "I747UCUEMJB"
E: error executing updater binary in zip '/external_sd/d2att_I747UCUEMJB_bootloader_modem_4.3.zip'
error flashing
updating partition details...
done.
Not sure what is going on
Can you give me the link you used to download it. I'll download and take a look at it. (I'd go get it myself but I want to make sure I am getting exactly the same thing you got.)
Sent from my SGH-T999 using Tapatalk
I got it from the link you posted about enewman17's thread. It has the MJB link for precaution and the NE4 link. I downloaded both them. Tried both and it gave me those 2 messages as you see
Not sure if I can post links yet.
The MJB one
http://www.androidfilehost.com/?fid=23269279319197285
The NE4 one
http://www.androidfilehost.com/?fid=23501681358559161
Are you sure you didn't accidentally download the wrong one? Double check the file name if you would.
The reason I am asking is because according to the log you posted above, it's trying to flash d2att_I747UCUEMJB_bootloader_modem_4.3.zip
That file can't be flashed because it is older than your current build, NE4.
Sent from my SGH-T999 using Tapatalk
File name for the MJB I have in my download folder:
d2att_I747UCUEMJB_bootloader_modem_4.3.zip
NE4:
UCUEMJB_to_UCUFNE4_Firmware_update.zip
I just noticed you said i am using an old file. Could you link me to an updated file? I downloaded everything exactly in the first page of that thread
Ok, do not flash the MJB package or it'll make things worse. You're device says it's already on NE4, but because the OTA failed part way through, we can't be sure what exactly got flashed. This means you need to reflash only the NE4 package to rewrite the firmware so we can be sure of what is on the device.
I just took a look at the NE4 file though, and as-is, it will not work because it doesn't write the full modem. Instead it patches the MJB modem to bring it to NE4. Since you may not have the MJB modem, this cannot work.
I'll try to redo that portion so instead of patching MJB, it will flash the full NE4 modem. Doing it this way should work. I'm going to shoot a pm to enewman17 too. We did have some issues with NE4 and i want to make sure we don't make things worse! The NJ1 and NJ2 packages include the full modem, so since those are confirmed working we can probably use the script from there with the NE4 files.
I will work on that while waiting to hear back from @enewman17.
I am sorry for not being more clear on what to flash earlier. I know this is probably getting a bit frustrating by now....
Sent from my SGH-T999 using Tapatalk
---------- Post added at 06:22 AM ---------- Previous post was at 05:33 AM ----------
Well it looks like he already had one!
From this post in one of his NE4 threads: http://forum.xda-developers.com/showpost.php?p=55206211&postcount=268
This is the package linked to in that post: https://www.androidfilehost.com/?fid=23578570567720263
So download that file. ( d2att_I747UCUFNE4_bootloader_modem_4.4.2_7-29-14.zip)
Also download the stock/rooted system and kernel package (I747UCUFNE4_Stock_Rooted_3-31-15.zip):
https://www.androidfilehost.com/?fid=24052804347765735
Flash the bootloader/modem first, then flash the stock rooted zip. (Don't reboot between them)
After flashing both reboot. Hopefully everything will be working again!
Now reboot twrp and flash the NJ1 file.
Reboot
Do the same for NJ2
This will leave you with NJ2 as your base firmware and modem. The Android O/S will still be NE4. You can download and flash the NJ2 system to be fully up to date!
If you plan on flashing a custom rom, don't bother with the NJ2 system. You can go straight to flashing whatever rom you want instead.
let me know if I wasn't clear on anything or if you have any questions.
Sent from my SGH-T999 using Tapatalk
I flashed both the bootloader and stock rooted files onto the phone. The phone finally booted to the OS. I am now on the NJ1/NJ2 step. Where could I find these 2 files?
I cannot seem to find a definitive answer.
Can this be done?
I picked up a 'new' T-Mobile Galaxy S4 M919TMBFOK3 unlocked. It will be going to someone who will be on Wind Mobile in Canada and I'd like to put that ROM on it or even their (Wind Mobile) Lollipop 5.01 on it. The T-Mob seems to have a lot of bloat on it that they'll never use on the Wind service.
Unless I'm missing something, everything I've read indicates it can be done. Tried it with Odin and it immediately 'nand write fail auth' message. Reflashed the stock M919TMBFOK3 from Sammobile and it worked so I know Odin is working and every thing seems alright. What has to be done different to get a M919V ROM on an M919?
Anyone please? Cannot afford to spend another week on this. It was supposed to be a gift and that already is not going to happen by Oct. 2.
Thank you.
Two possible solutions I know:
flash TWRP on the phone and flash a "wind-like" custom ROM onto the phone;
root the stock T-Mobile ROM and use titanium backup to either freeze or remove the apps.
Which file failed to flash in Odin? Was it something like sboot.bin or aboot.mbn?
audit13 said:
Two possible solutions I know:
flash TWRP on the phone and flash a "wind-like" custom ROM onto the phone;
root the stock T-Mobile ROM and use titanium backup to either freeze or remove the apps.
Which file failed to flash in Odin? Was it something like sboot.bin or aboot.mbn?
Click to expand...
Click to collapse
Hello,
Yes, it fails at aboot.mbn
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've tried Towel Root. Didn't work. I've tried CM13.xx for the S4 via .zip using TWRP. Nothing. Cannot flash any ROM at all except for the original T-Mob. For 'Stock' roms I do not need to be rooted do I? Didn't think so. ?
I've never seen such a PITA. Nothing will flash for anything..
It's failing in Odin because the bootloader in the rom doesn't match the phone.
Here's a link to TWRP for the sgh-m919: https://twrp.me/devices/samsunggalaxys4tmobile.html
CM13 for the sgh-m919: http://forum.xda-developers.com/galaxy-s4/general/official-cm13-sgh-m919-jfltetmo-t3354792
Are these the files your tried?
BTW, no need to root if you're going to flash CM13.
audit13 said:
It's failing in Odin because the bootloader in the rom doesn't match the phone.
Here's a link to TWRP for the sgh-m919: https://twrp.me/devices/samsunggalaxys4tmobile.html
CM13 for the sgh-m919: http://forum.xda-developers.com/galaxy-s4/general/official-cm13-sgh-m919-jfltetmo-t3354792
Are these the files your tried?
BTW, no need to root if you're going to flash CM13.
Click to expand...
Click to collapse
Yes sir. The TWRP is on the phone. No problem there. Downloaded the 'Snapshot' rather than a nightly. Failed to install from External SD. No subfolders. Root of the card. I don't play with custom roms too much but I was under the impression CM was already rooted.
I've since tried one Wind 4.4.2 rom but that may not work since the phone is 4.4.4 and there are apparently issues with downgrades unless I'm misunderstanding. Also tried a Wind 5.0.1 for their S4. Also tried some Black Edition UK 9505 ROMs, both 4.4.x and 5.x.x.
All fail identically but the T-Mobile installs no issues.
Have you tried flashing with TWRP 2.87?
You're flashing cm13 for the jfltetomo?
Custom ROMs do not flash a bootloader or modem so I would not worry about flashing a 4.4.4 custom ROM on a phone with a 4.4.2 bootloader.
audit13 said:
Have you tried flashing with TWRP 2.87?
You're flashing cm13 for the jfltetomo?
Custom ROMs do not flash a bootloader or modem so I would not worry about flashing a 4.4.4 custom ROM on a phone with a 4.4.2 bootloader.
Click to expand...
Click to collapse
No. What's the significance of 2.87? I'll check it out.
Actual file name;
cm-13.0-20160820-SNAPSHOT-ZNH5YAO0J3-jfltetmo.zip
The ROM was saved to a micro SD card and 3.07 failed to see the external card? Definitely try 2.87.
audit13 said:
The ROM was saved to a micro SD card and 3.07 failed to see the external card? Definitely try 2.87.
Click to expand...
Click to collapse
To be clear, I did try running the .zip from the external SD card using v3.0.2.0 TWRP.
I just tried 2.8.7 and ran the CM13 zip from the external SD after wiping the cache and data folder. This time it installed.
That was odd. Can't flash anything else though.
Just flashed back to the Stock TMO.
Thanks so much for the help so far. Have to step out.
Sorry for being a noob but I'm a bit lost as to why this thing will not accept an i9505 LTE Unbranded ROM or Wind Mobile or Mobilicity ROM which I'm quite sure has less bloat... or at least none of the T-Mobile bloat AND there is at least 5.0.1.
What am I missing?
The i9505 ROM may be failing to install because you may need to edit the updater script to include the jfltetmo as a valid device.
The i9505 is a jfltexx.
audit13 said:
The i9505 ROM may be failing to install because you may need to edit the updater script to include the jfltetmo as a valid device.
The i9505 is a jfltexx.
Click to expand...
Click to collapse
In the CM13.x .zip, I found the updater script but with other full ROMs that are .tar.md5, is there an updater script? Didn't think there was.
Still not understanding why the aboot.mbn fails and how or if this can be remedied.
I've read all kinds of posts about people running unbranded or stock roms from other carriers. What's up with this? TMO do something to these that others do not? I was under the impression the I9505, SGH-M919 and SGH-M919V were the same phone for different areas or markets?
I'm missing a real basic piece to the puzzle.
Tar.md5 ROMs are made for flashing via Odin and there is no updater script as Odin doesn't use these updater scripts.
The abootmbn is a bootloader file. I'm assuming that Odin compares the bootloader file to the phone's bootloader. If there is a mismatch, Odin will halt the flash process to prevent bricking the phone. You can't force-flash the bootloader file and, even if you could, there is a chance the phone would become hard-bricked.
You may be able to flash a stock Wind ROM to a T-Mobile phone by removing the bootloader and re-packing the ROM for flashing via Odin; however, I have never done this myself and don't recommend it in the slightest. There may be braver people out these that have gone through with this procedure but I am not one of them.
These unbranded ROMs may have been loaded onto carrier-free phones but I'm not sure.
The hardware may be very similar or identical in the 9505, m919, and 919v; however, each of these phones support different radio frequencies. For example, a stock i9505 will not connect to LTE networks in North America. The m919 and 919v are made for carriers that support AWS frequencies in North America. The S4 from AT&T and Telus/Bell/Rogers will not connect to Wind networks.
I may try to eliminate some of the bloat. I'll root if necessary to see what I can clean up. This is a new user to Android and I'd prefer they have as close to stock a look as possible so they can easily reference 'How To's'.
Thanks again.
This thread may help: http://forum.xda-developers.com/galaxy-s4-tmobile/general/i9505oa7tw5-0leak-t3045729
audit13 said:
The i9505 ROM may be failing to install because you may need to edit the updater script to include the jfltetmo as a valid device.
The i9505 is a jfltexx.
Click to expand...
Click to collapse
Yeah I had read that thread. I was really hoping or looking for something a bit more, single ROM/Odin done in 7 minutes and it all works solution.
I'll be trying it. Why not? If I can arrive at a vanilla looking/operating Android device that's fairly lean with basics, where at least online reference will be close to what they are seeing, which is often not the case with custom roms as cool or well done as they may be, then why not. The T-Mobile stock has so much junk on it. Too bad because I've heard the build is otherwise decent.
Then again, I'm just half efficient at flashing whole roms, parts of things like radios, setting up dual format sdcards, using bootloaders and other things that work etc. Otherwise, I'm a noob. Cheers.
You could also flash the i9505 version of twrp to the phone, then flash an i9505 custom rom.