I'm on 4.4.4 AOKP and I accidentally formatted something in recovery and got stuck in bootloop. Downloaded stock TW for S3 but everytime ODIN keeps giving me an error.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<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> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Also, can't seem to be able to get CWM or TWRP back on but I can get the stock recovery. Tried Kies but that didn't work. Been looking for stuff for a couple hours and can't seem to find an answer. Any help is appreciated, thanks.
I'm in a similar situation but in my case I have cwm but can't switch recovery or even upgrade it, and flashing roms doesn't stick.
Sent from my SM-N900T using XDA Premium 4 mobile app
TheAccomplisher said:
I'm on 4.4.4 AOKP and I accidentally formatted something in recovery and got stuck in bootloop. Downloaded stock TW for S3 but everytime ODIN keeps giving me an error.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<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> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Also, can't seem to be able to get CWM or TWRP back on but I can get the stock recovery. Tried Kies but that didn't work. Been looking for stuff for a couple hours and can't seem to find an answer. Any help is appreciated, thanks.
Click to expand...
Click to collapse
Are you able to boot in recovery? (home + vol up + power) - You could just reflash from there.
Do you know what you formatted in recovery?
I can get to recovery and download mode but I'm on stock recovery and can't flash anything. I must have formatted /system or /data
TheAccomplisher said:
I can get to recovery and download mode but I'm on stock recovery and can't flash anything. I must have formatted /system or /data
Click to expand...
Click to collapse
Have you tried flashing a custom recovery through Odin?
Also, if you're on 4.4.4, chances are that your bootloaders are on 4.3+. You'll need the MJB (4.3) or NE4 (4.4.2) stock to flash through Odin.
Downgrading bootloaders will result in a brick, therefore it's a good thing it's not going through!
I flashed TWRP and got a pass but every time I get into recovery mode I just get a black screen.
Where can I get NE4?
Thanks
TheAccomplisher said:
I flashed TWRP and got a pass but every time I get into recovery mode I just get a black screen.
Where can I get NE4?
Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2789917
If already on the MJB bootloaders/modem: http://forum.xda-developers.com/galaxy-s3-att/general/ucuemjb-to-ucufne4-firmware-update-t2808654
Since I'm on 4.4.4 I already have the MJB right?
TheAccomplisher said:
Since I'm on 4.4.4 I already have the MJB right?
Click to expand...
Click to collapse
I think so but you only can be sure if you updated your bootloaders to 4.3 (or up to the new NE4 4.4.2).
All right thanks I'll have to try it in a couple hours
TheAccomplisher said:
Since I'm on 4.4.4 I already have the MJB right?
Click to expand...
Click to collapse
The error at aboot.mbn tells me you have the 4.3 bootloader on your phone. By trying to flash a stock Samsung ROM in Odin means Odin will try and downgrade the bootloader to an older version which cannot be done once you are on a stock 4.3 bootloader. Don't keep using Odin to flash a stock Samsung ROM as it may brick your phone.
TheAccomplisher said:
I'm on 4.4.4 AOKP and I accidentally formatted something in recovery and got stuck in bootloop. Downloaded stock TW for S3 but everytime ODIN keeps giving me an error.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<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> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Also, can't seem to be able to get CWM or TWRP back on but I can get the stock recovery. Tried Kies but that didn't work. Been looking for stuff for a couple hours and can't seem to find an answer. Any help is appreciated, thanks.
Click to expand...
Click to collapse
Any update on this?
Sent from my SM-N900T using XDA Premium 4 mobile app
Everything is working perfect now and I'm on 4.4.2
TheAccomplisher said:
Everything is working perfect now and I'm on 4.4.2
Click to expand...
Click to collapse
What did you do to fix your problem?
Sent from my SM-N900T using XDA Premium 4 mobile app
Related
Hello, I downloaded the installer and it did help me flash the rom but now i would like to go back to the stock rom, i have tried it with odin but it keeps stating that it fails. I also have the correct .tar file. This is the error it gives me. Thanks in advanced!
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<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)
Stock backup?
jayyfresh said:
Hello, I downloaded the installer and it did help me flash the rom but now i would like to go back to the stock rom, i have tried it with odin but it keeps stating that it fails. I also have the correct .tar file. This is the error it gives me. Thanks in advanced!
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<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)
Click to expand...
Click to collapse
WHen you first rooted and installed your custom recovery, did you make a backup in that program before anything else?
electrojas said:
WHen you first rooted and installed your custom recovery, did you make a backup in that program before anything else?
Click to expand...
Click to collapse
I used the cyanogen mod installer on my nexus 7 and it never gave an option to backup. It was an automated process that installed without any way of going back.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Cyanogen
bellifritz said:
I used the cyanogen mod installer on my nexus 7 and it never gave an option to backup. It was an automated process that installed without any way of going back.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I guess Im not experienced with that mod installer but in order to even get that far didnt you have to root, and install a custom recovery? Or is that a totally different thing?
electrojas said:
WHen you first rooted and installed your custom recovery, did you make a backup in that program before anything else?
Click to expand...
Click to collapse
i backed it up with kies
CWM or TRWP?
jayyfresh said:
i backed it up with kies
Click to expand...
Click to collapse
Do you have a custom recovery installed on your device?
electrojas said:
Do you have a custom recovery installed on your device?
Click to expand...
Click to collapse
im not sure actually, im kinda new to flashing roms, how can i tell?
im in a bit of a pickle here.
so i had android 4.3 stock rom but then switched to cyanogemod 10.2.. today i decided i wanted to go back to stock rom so i tried using odin 3.07 and flashing I747UCALG1_I747ATTALG1_I747UCALG1_HOME.tar.md5 (i cant find 4.3 firmware anywhere). i go into download mode, put that file in PDA, and odin tells me:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCALG1_I747ATTALG1_I747UCALG1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<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> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
and on my phone is says SV REV Check Fail : Fused 2 > Binary 0
i was trying to find stuff out online and they said something about a bootloader and i have no clue what that means. also, cyanogenmod is no longer even going to the home screen so my phone is not functioning at all. and since it isnt loading, my computer isnt detecting a device so i cant add any files to my phone.
can someone please help me? using english please, not computer hacker language. im not that advanced in this kind of stuff.
camerondobbs said:
im in a bit of a pickle here.
so i had android 4.3 stock rom but then switched to cyanogemod 10.2.. today i decided i wanted to go back to stock rom so i tried using odin 3.07 and flashing I747UCALG1_I747ATTALG1_I747UCALG1_HOME.tar.md5 (i cant find 4.3 firmware anywhere). i go into download mode, put that file in PDA, and odin tells me:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCALG1_I747ATTALG1_I747UCALG1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<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> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
and on my phone is says SV REV Check Fail : Fused 2 > Binary 0
i was trying to find stuff out online and they said something about a bootloader and i have no clue what that means. also, cyanogenmod is no longer even going to the home screen so my phone is not functioning at all. and since it isnt loading, my computer isnt detecting a device so i cant add any files to my phone.
can someone please help me? using english please, not computer hacker language. im not that advanced in this kind of stuff.
Click to expand...
Click to collapse
Unfortunately my friend, Odin will not work to return back to stock. By chance did you make a nandroid backup before you switched from 4.3 to CyanogenMod? If not I'd suggest finding a TW based rom from one of the devs on here under the Android Development thread and flash it manually via CWM or TWRP. I'm looking myself for a 4.3 TW Odin tar but nothing has surfaced to my knowledge. You're trying to flash a 4.0 rom in Odin it looks like which won't work since 4.3 updates the baseband and bootloader which will cause Odin to fail every time you try flashing a rom that isn't 4.3
camerondobbs said:
im in a bit of a pickle here.
so i had android 4.3 stock rom but then switched to cyanogemod 10.2.. today i decided i wanted to go back to stock rom so i tried using odin 3.07 and flashing I747UCALG1_I747ATTALG1_I747UCALG1_HOME.tar.md5 (i cant find 4.3 firmware anywhere). i go into download mode, put that file in PDA, and odin tells me:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCALG1_I747ATTALG1_I747UCALG1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<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> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
and on my phone is says SV REV Check Fail : Fused 2 > Binary 0
i was trying to find stuff out online and they said something about a bootloader and i have no clue what that means. also, cyanogenmod is no longer even going to the home screen so my phone is not functioning at all. and since it isnt loading, my computer isnt detecting a device so i cant add any files to my phone.
can someone please help me? using english please, not computer hacker language. im not that advanced in this kind of stuff.
Click to expand...
Click to collapse
if you still can go into downloadmode, you can unroot your device and put it back to stock with Kies 3.
Download Kies 3 from samsung web site and download Samsung USB Drivers too
Unplug your phone from the PC
After on Kies 3 click on tools>emergency firmware update and inisialitazion.
Now they will ask for your phone model so if you are on at&t its : SGH-I747 (Rogers bell .. tis : SGH-I747M
After, Kies 3 will ask you your S/N (this can be found under your battery the sticker) so remove your battery and write it down
Know if it work they gonna tell you to put your phone into download mode
To go into download mode hold : Volume Down + Home Button + Power button
After on your phone you should see a Yellow triangle with some warning (jUst ignore that and press the volume up button)
And Kies 3 will automaticly unroot your phone, flash the new 4.3 update and flash the new bootloader too.
!!!***WATCH OUT! DO A BACK UP OF YOUR INTERNAL MEMORY BECAUSE YOU ARE GOING TO LOSE EVERYTHING***!!!
And after you just have to wait.... Kies 3 will download automaticly 4.3 Firmware and flash it on your phone.
Make shure that your battery is charged at least at 30% before doing that.
And after enjoy your phone unrooted and on stock rom and after you will be still able to update your phone for futurer update availble.
Tell me if it worked for you after!
Hello!
So i've been failing at getting this SGS4 SCH-M919 back to stock firmware. I have CM11 nightly installed. (This is my bosses phone that i'm trying to get back to stock) So far, I've downloaded two stock firmware images (just in case firs was corrupt) and they both haven't worked.
My process goes like:
-Download drivers (or Kies, i've tried both)
-Set into recovery mode
-Start Odin (i've tried in a few versions)
-Plug phone in
-Odin recognizes
-choose file to flash
-Start the flash then I'll always get this error
<ID:0/005> 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/005> Odin v.3 engine (ID:5)..
<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> sbl2.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> aboot.mbn
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
After that, i'm in a little brick mode that I can easily get out of my flashing CWM Recovery on there, and it'll boot me back into CM11.
So, any ideas? I've tried two computers, restarted...idk what to do anymore.
Thank you to anyone who tries to help me!
Looks like you're trying to flash older firmware which will never work if the device has been updated to 4.3 and up.. You need to flash either 4.3 or 4.4.2. 4.3 will work if that was the firmware they had before flashing cm11.. Otherwise you need to flash 4.4.2
Sent from my SGH-M919 using Tapatalk
I updated my i317M (Telus) via OTA and the next day it rebooted and went into boot loop.
I've tried flashing the phone with 4 different stock roms (from 4.1.2 to 4.4.2) but they all fail.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I317MVLBMA3_I317MOYABMA3_I317MVLBMA3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've tried flashing Philz Touch recovery but that fails as well.
I've tried to boot it into recovery mode but it shows a dead Android with error logs like "E:failed to mount"
Help?
goyagoyago said:
I updated my i317M (Telus) via OTA and the next day it rebooted and went into boot loop.
I've tried flashing the phone with 4 different stock roms (from 4.1.2 to 4.4.2) but they all fail.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I317MVLBMA3_I317MOYABMA3_I317MVLBMA3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've tried flashing Philz Touch recovery but that fails as well.
I've tried to boot it into recovery mode but it shows a dead Android with error logs like "E:failed to mount"
Help?
Click to expand...
Click to collapse
Try flashing with odin again but before flashing open the tar and remove the bootloader out of it.
Hi, thanks for the reply cnote.
Would the bootloader be sboot.bin or boot.img or both?
thanks again
edit: or rather, how do you remove the bootloader and remake the tar file?
goyagoyago said:
Hi, thanks for the reply cnote.
Would the bootloader be sboot.bin or boot.img or both?
thanks again
edit: or rather, how do you remove the bootloader and remake the tar file?
Click to expand...
Click to collapse
I believe it;s both. Just retrieve the tar file only.
sboot is the bootloader boot.img is the kernel .Have you tried the latest NH2 for your phone also maybe try using a pit file
The nh2 you will have to get from sammobile and the pit file can be found here http://forum.xda-developers.com/showthread.php?t=2609871
Also after odin is finished go into factory recovery and do a factory reset or its just going to sit at the boot screen
flashing pit file also gives an error :S
I haven't done any ROM updates for a couple of weeks, and I was sound asleep when the phone rebooted. It sat 'rebooting' for two hours before I woke up.
I'm able to reboot into Download Mode, but have been unable to install anything that has worked. I tried flashing both TWRP2.7.0.0 and the stock ROM, but neither have worked. TWRP is still showing as 2.6.3.1 on my phone, and I get a failure when loading the Stock rom that looks like this:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747MVLUFNH2_I747MOYBFNH2_I747MVLUFNH2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
I'm also able to boot into Recovery mode, but it appears that the phone is encrypted (it asks for a password, even though I've never encrypted it!) and when I try to factory reset or wipe dalvik or anything else, I get: E: Unable to mount '/cache'
Can you help? Phone is a rooted SGS-I7474M on Telus, and was running Slim 4.4.4 build 7.0 Official 5979. I'm using TWRP as my recovery.
Maybe try loading a stock from image using Odin? You can download the stock images from sammobile
Tony_YYZ said:
Maybe try loading a stock from image using Odin? You can download the stock images from sammobile
Click to expand...
Click to collapse
I think that's what I've been doing? I've downloaded this stock firmware: sammobile.com/firmwares/download/34793/I747MVLUFNH2_I747MOYBFNH2_TLS.zip/ and then tried loading it via ODIN?
Perhaps I'm missing something... Appreciate your thoughts!
hardidu said:
I think that's what I've been doing? I've downloaded this stock firmware: sammobile.com/firmwares/download/34793/I747MVLUFNH2_I747MOYBFNH2_TLS.zip/ and then tried loading it via ODIN?
Perhaps I'm missing something... Appreciate your thoughts!
Click to expand...
Click to collapse
Oh, my mistake. That's what I was suggesting. Sorry...I don't know what else to try.
What bootloader is on your phone?
You're trying to alter the bootloader which is causing the error after trying to flash aboot.mbn.
audit13 said:
What bootloader is on your phone?
You're trying to alter the bootloader which is causing the error after trying to flash aboot.mbn.
Click to expand...
Click to collapse
You've lost me... I have no idea. I don't think I've ever touched the bootloader unless that's packaged with Slimkat or TWRP,
How do I find out and what's my next step?
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
The aboot.mbn file is a bootloader that Odin is trying to load onto your phone. but the current bootloader is preventing this because the bootloader your are trying to load is not compatible with your phone or the current bootloader is newer than the bootloader Odin wants to flash.
Does your phone still boot into download mode? You're sure your phone is an i747m (Canadian version of s3)?
If your phone can boot into download mode, I recommend you flash the latest version of Philz Touch for the d2lte, copy a custom ROM to your external SD card, boot into Philz, and flash the custom ROM so you can at least get your phone booted. Once booted, install the Samsung Phone info app. This app will tell you the baseband and bootloader on your phone.
audit13 said:
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
The aboot.mbn file is a bootloader that Odin is trying to load onto your phone. but the current bootloader is preventing this because the bootloader your are trying to load is not compatible with your phone or the current bootloader is newer than the bootloader Odin wants to flash.
Does your phone still boot into download mode? You're sure your phone is an i747m (Canadian version of s3)?
If your phone can boot into download mode, I recommend you flash the latest version of Philz Touch for the d2lte, copy a custom ROM to your external SD card, boot into Philz, and flash the custom ROM so you can at least get your phone booted. Once booted, install the Samsung Phone info app. This app will tell you the baseband and bootloader on your phone.
Click to expand...
Click to collapse
I tried loading I747MVLDLK4_aio.tar.md5 and here's the log from the fail I ended up with:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747MVLDLK4_aio.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Loading Philz also failed.
Are you flashing the latest Philz tar.md5 file? You can't flash the zip in Odin. You should be able to flash the Philz zip in TWRP.
audit13 said:
Are you flashing the latest Philz tar.md5 file? You can't flash the zip in Odin. You should be able to flash the Philz zip in TWRP.
Click to expand...
Click to collapse
I was using Skips Toolkit to try and load Philz... I'll try using TWRP
Flash Philz tar.md5 in Odin or the zip in TWRP. I prefer not to using any tool kits.
audit13 said:
Flash Philz tar.md5 in Odin or the zip in TWRP. I prefer not to using any tool kits.
Click to expand...
Click to collapse
The process all looks good, log:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.07.9-d2att.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> RQT_CLOSE !!
<ID:0/007> RES OK !!
<ID:0/007> Removed!!
But still boots with TWRP... despite a PASS in Odin.