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.
Related
Ok so here is the situation. I have a GS3 i747. About a week ago it randomly shut off and entered a bootloader loop. I went into CWM and tried to flash to a new rom and I kept getting a Status 7 error. So I edited the ROM to not check for assets and I eventually got the ROM to install... Everything was going fine until last night. The phone entered another loop and this time when I go into CWM I get lots of errors...
E: can't mount /cache/ recovery/ command
E: can't mount /cache/ recovery/ log
E: cant open /cache/ recovery/ log
E: can't mount /cache/ recovery/ last_log
E: can't open /cache/ recovery/ last_log
E: can't mount /cache/ recovery/ last_install
E: can't open /cache/ recovery/ last_install
In addition I cannot mount cache or data but I can mount system.
When I try to install a ROM via CWM it gives a status 7 error even with I delete the assets.
When i try to flash using ODIN it gets to NAND write start --> failed
I did get a pass when I ran a new pit and re-partitioned however it didn't do anything on the phone (i'm not sure if i would notice a difference or not though.)
Oh and the download on the phone still lists the model number and everything, if that is helpful...
If anyone has any idea what I can do to fix this I would greatly appreciate it!
Status 7 error can happen if your recovery is out of date. If you are flashing KK ROMs, you need the latest CWM. I like Philz Touch which can be installed via Odin.
What error are you getting in Odin? If you have a 4.3 bootloader and you are trying to install a stock ROM, the stock ROM will try to downgrade the bootloader which may brick the phone. The AT&T 4.3 bootloader cannot be downgraded so do not attempt to flash with Odin until you confirm your bootloader version.
audit13 said:
Status 7 error can happen if your recovery is out of date. If you are flashing KK ROMs, you need the latest CWM. I like Philz Touch which can be installed via Odin.
What error are you getting in Odin? If you have a 4.3 bootloader and you are trying to install a stock ROM, the stock ROM will try to downgrade the bootloader which may brick the phone. The AT&T 4.3 bootloader cannot be downgraded so do not attempt to flash with Odin until you confirm your bootloader version.
Click to expand...
Click to collapse
I am on the latest CWM listed for my phone, 6.0.4.7 I believe. The last ROMs I had installed were KK and CM 11, which I assume means my bootloader is 4.4? All that is happening in Odin is when I try to flash a ROM it starts normal but once it gets to the "Nand Write start" part it says failed.
In addition if I try to flash CWM via Odin. It says passed, but I don't think it's actually changing. For example, i tried to change the CWM that i have which is the touch version into the non-touch version and it says passed but when I go onto the phone touch still works.
Flashing a 4.4 custom ROM does not update your bootloader.
Boot into download mode. What is shown on the download screen?
Did you select re-partition in Odin or just Auto-Reboot and F.Reset?
audit13 said:
Flashing a 4.4 custom ROM does not update your bootloader.
Boot into download mode. What is shown on the download screen?
Did you select re-partition in Odin or just Auto-Reboot and F.Reset?
Click to expand...
Click to collapse
Download mode says:
Odin mode
Product Name: SGH-I747
Custom Binary Download: Yes (2 counts)
Current Binary: Custom
System Status: Custom
Qualcomm Secureboot: enable
and has the android icon in the middle. With "Downloading...Do not turn off target!!"
Only Auto-reboot and F. reset.
Based on the download screen, it does not look like you have the 4.3 bootloader.
Did you get the stock ROM from here: http://forum.xda-developers.com/sho...mctr=(not provided)&__utmv=-&__utmk=269060210 ?
audit13 said:
Based on the download screen, it does not look like you have the 4.3 bootloader.
Did you get the stock ROM from here: http://forum.xda-developers.com/sho...mctr=(not provided)&__utmv=-&__utmk=269060210 ?
Click to expand...
Click to collapse
No should I try to install that one?
I'm having the exact same issue, only I don't have a ROM on the device to try and install from CWRM. No luck loading the factory recovery with odin (says success, but still have CWRM). I can't see the phone with adb or fastboot either so I feel like I'm SOL. Hopefully someone knows a fix.
I was running CM11 before it quit working.
Similar problem. Was on 4.3 official then installed CM11 4.4.2. Now when trying to go back to 4.3, process fails using twrp or cwm. I also tried odin to flask the tmo 4.3 md5 file but it fails.
Please help.
ctbartolillo said:
No should I try to install that one?
Click to expand...
Click to collapse
Make sure you install the ROM that is for your carrier and phone.
audit13 said:
Make sure you install the ROM that is for your carrier and phone.
Click to expand...
Click to collapse
Nope, that didn't work I get the same error.
<ID:0/005> Added!!
<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/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!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
Any other ideas?
ctbartolillo said:
Nope, that didn't work I get the same error.
<ID:0/005> Added!!
<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/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!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
Any other ideas?
Click to expand...
Click to collapse
Is the phone an i747 from AT&T?
audit13 said:
Is the phone an i747 from AT&T?
Click to expand...
Click to collapse
Yes it is.
If you have the 4.3 att bootloader on your phone, you can't use Odin to flash a stock ROM.
ctbartolillo said:
Nope, that didn't work I get the same error.
<ID:0/005> Added!!
<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/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!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
Any other ideas?
Click to expand...
Click to collapse
Dude I am pretty much in the same situation. This thread is probably our only hope now.
http://forum.xda-developers.com/showthread.php?t=2658486
UPDATE: Tried today and worked perfectly!!!! Give it a shot.
Deleted.
I tried but it didn't work. I got Symlink: some symlinks failed, status 7
Hi all, so I installed the cyanogenmod's new update, I used its in the system update, thought it will be pretty safe just like a stock android update, but then my phone stuck at boot screen. and I really don't have time to mingle with the system right now. I need the phone like 3 hours ago!! i downloaded the stock rom and try to use odin to flash it. then it gives me this error message.
I tried, change the cable, change usb port, change odin version, but nothing works so far. (((
Please help !!
<ID:0/008> 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/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> aboot.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<ID:0/008> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
You have the 4.3 bootloader on your phone? If you do, you can't use Odin to flash a stock ROM because it may brick your phone. You can only use Odin to flash a 4.3 stock ROM that had specifically been compiled for use with Odin.
audit13 said:
You have the 4.3 bootloader on your phone? If you do, you can't use Odin to flash a stock ROM because it may brick your phone. You can only use Odin to flash a 4.3 stock ROM that had specifically been compiled for use with Odin.
Click to expand...
Click to collapse
Is there a 4.3 rom we can flash with odin? I attempted (stupidly) to flash stock after a CM11 nightly caused a bootloop and would not allow me to enter recovery. All I can do for the moment is enter download mode. Every rom I try to flash I get the same error along with the error on my phone reading:
SW REV CHECK FAIL : Fused 2 > Binary 0
Is there anything I can do?
EDIT: Finally found a fix. I flashed a rom from this thread.
http://forum.xda-developers.com/showthread.php?t=1980683
Just go to their website and download the file for your specific model. After flashing my phone booted up in CM11 (what I previously had installed) but it crashed upon loading the lockscreen. Luckily I could enter recovery mode and do a factory reset. This fixed everything!
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
TLDR: My phone is softbricked, I've tried ODIN flashing Stock, I've tried flashing ROMS I've used before in TWRP... Nothin' workin'
fI was using Task's AOKP with no issues. Yesterday my phone was taking way longer to boot, but eventually made it, but my battery was draining like crazy... I rebooted my phone and it was stuck in boot loop. I tried reflashing the ROM/GAPPS but got an error during the GAPPS install that told me that system/build.prop was missing. I figured I should just try to revert to stock through ODIN and start from scratch. Here's what ODIN gives me when I try to flash the latest Samsung firmware:
<ID:0/004> 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/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas? Are all soft-bricks eventually recoverable? I'm a phone addict...
Uggo said:
TLDR: My phone is softbricked, I've tried ODIN flashing Stock, I've tried flashing ROMS I've used before in TWRP... Nothin' workin'
fI was using Task's AOKP with no issues. Yesterday my phone was taking way longer to boot, but eventually made it, but my battery was draining like crazy... I rebooted my phone and it was stuck in boot loop. I tried reflashing the ROM/GAPPS but got an error during the GAPPS install that told me that system/build.prop was missing. I figured I should just try to revert to stock through ODIN and start from scratch. Here's what ODIN gives me when I try to flash the latest Samsung firmware:
<ID:0/004> 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/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas? Are all soft-bricks eventually recoverable? I'm a phone addict...
Click to expand...
Click to collapse
The exact error I get when I try to flash GAPPS is:
file_getprop: failed to stat "/system/build.prop": No such file or directory
E:Error executing updater binary in zip '/external_sd/pa_gapps-stock-4.4.4-20140916-signed.zip
Error flashing zip '/external_sd/pa_gapps-stock
Updating partition details...
It's also worth noting that flashing the ROM (I'm going with the latest CM nightly) takes way too short of a time to complete
Sounds like your recovery may not like the binary used by the package.
For Odin though, do you have kids on your computer? If so uninstall it, reboot and try again.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
DocHoliday77 said:
Sounds like your recovery may not like the binary used by the package.
For Odin though, do you have kids on your computer? If so uninstall it, reboot and try again.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Thanks, but it didn't help. I'm still getting the same problems.
Try a different version of twrp, or try cwm or philz recoveries too.
For that Odin flash, how big is the firmware you're trying to flash? I just noticed the "single download" line. Also, which version of Odin are you using and where are you putting the firmware? Looks like you might be putting it in the bootloader slot?
Sent from my SAMSUNG-SGH-T999 using Tapatalk
DocHoliday77 said:
Try a different version of twrp, or try cwm or philz recoveries too.
For that Odin flash, how big is the firmware you're trying to flash? I just noticed the "single download" line. Also, which version of Odin are you using and where are you putting the firmware? Looks like you might be putting it in the bootloader slot?
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Thanks for all the help. I'm not sure what the issue was, but I ended up solving it by using the latest CWM recovery to install a flashable version of stock. I'm not a huge fan of stock, but I'm up for an upgrade in January so I'm going to just have to cool it on the ROM front to ensure I have a working phone.
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