I think I soft bricked my phone, but I don't know how to get it resolved. I can get into my recovery and download mode, which leads me to believe that it is soft bricked. I'm trying to flash a stock rom using Odin and I am getting an error:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_L710VPALEN_L710SPRALEN_618049_REV03_user_low_ship.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> sbl2.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas on how I can fix this?
dasignz said:
I think I soft bricked my phone, but I don't know how to get it resolved. I can get into my recovery and download mode, which leads me to believe that it is soft bricked. I'm trying to flash a stock rom using Odin and I am getting an error:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_L710VPALEN_L710SPRALEN_618049_REV03_user_low_ship.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> sbl2.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas on how I can fix this?
Click to expand...
Click to collapse
Go here...... http://www.sxtpdevelopers.com/showthread.php?t=233. Download the one-click rooted no data and try again. If that doesn't work, you can always try using a different cable. Do you have TWRP as the recovery or CWM? If you have TWRP, you can always boot into recovery, connect your phone to the computer via USB, mount the USB drive and then push any ROM to your external SD card and then just flash from there.
tkepk181 said:
Go here...... http://www.sxtpdevelopers.com/showthread.php?t=233. Download the one-click rooted no data and try again. If that doesn't work, you can always try using a different cable. Do you have TWRP as the recovery or CWM? If you have TWRP, you can always boot into recovery, connect your phone to the computer via USB, mount the USB drive and then push any ROM to your external SD card and then just flash from there.
Click to expand...
Click to collapse
I have CWM installed. It's having trouble mounting things, such as
cache/recovery
/sdcard/.android_secure
/data
I had just installed CM10.1 on it, and it suddenly started rebooting in a loop and I received these errors when trying to anything with the phone.
Your trying to use odin correct? But you have kies also set up?
Also do you have the MD4 updated bootloader installed?
Sent from the future via Tapatalk 4
edfunkycold said:
Your trying to use odin correct? But you have kies also set up?
Also do you have the MD4 updated bootloader installed?
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
I believe I am using Odin correctly, I have flashed other things with it in the past, I am running it in administrator mode. I do not have Kies set up. And I don't entirely know what you mean by MD4 Updated Bootloader.
dasignz said:
I believe I am using Odin correctly, I have flashed other things with it in the past, I am running it in administrator mode. I do not have Kies set up. And I don't entirely know what you mean by MD4 Updated Bootloader.
Click to expand...
Click to collapse
In order to flash any of the new 10.1 cm it is required that the bootloader be updated to the latest release MD4. There us a script which checks for it. Can you boot into CWM? If yes then boot into CWM and flash this first. http://db.tt/Qt6NcH0a
Sent from the future via Tapatalk 4
edfunkycold said:
In order to flash any of the new 10.1 cm it is required that the bootloader be updated to the latest release MD4. There us a script which checks for it. Can you boot into CWM? If yes then boot into CWM and flash this first. http://db.tt/Qt6NcH0a
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
You'll have to forgive me, I am a little new to this. Where would I get the MD4 bootloader?
dasignz said:
You'll have to forgive me, I am a little new to this. Where would I get the MD4 bootloader?
Click to expand...
Click to collapse
I just gave you the flashable update zip. Also why are you not flashing g the rom via CWM? It's much easier to flash roms through recovery in their zip format?
Sent from the future via Tapatalk 4
edfunkycold said:
I just gave you the flashable update zip. Also why are you not flashing g the rom via CWM? It's much easier to flash roms through recovery in their zip format?
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
Sorry, I got it. I have tried to flash through CWM, but I am having a problem with mounting as I mentioned in previous comments. I can flash CM10.1 in CWM and it says updated successfully, but it's stuck in a bootloop because the /data and /.android_secure are missing. So I am trying to go back to stock with the firmware to start over, but odin is not working as I thought it would.
Flash the update i gave you then flash 10.1 again and try to boot up. Make sure you wipe cache and dalvik and do a factory reset before flashing
Sent from the future via Tapatalk 4
edfunkycold said:
I just gave you the flashable update zip. Also why are you not flashing g the rom via CWM? It's much easier to flash roms through recovery in their zip format?
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
I tried to flash that modem you sent me. It failed saying
Updating SBL1 OTA
assert failed: package_extract_file("sbl1.mbn","/dev/block/mmcblk0p2")
dasignz said:
I tried to flash that modem you sent me. It failed saying
Updating SBL1 OTA
assert failed: package_extract_file("sbl1.mbn","/dev/block/mmcblk0p2")
Click to expand...
Click to collapse
That shouldn't happen at all. Try reinstalling CWM via odin.
Sent from the future via Tapatalk 4
edfunkycold said:
That shouldn't happen at all. Try reinstalling CWM via odin.
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
This thing is all messed up. This is what happens when I try to use Odin to flash CWM
<ID:0/008> Added!!
<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> recovery.img
<ID:0/008> NAND Write Start!!
<ID:0/008> FAIL! (Write)
<OSM> All threads completed. (succeed 0 / failed 1)
edfunkycold said:
That shouldn't happen at all. Try reinstalling CWM via odin.
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
Is there a .PIT file that I can use to re-partition my phone? Seems like the partition is bad or corrupted. All attempts to install stock firmware have failed. CWM works fine, but I cannot mount anything. The only thing I can mount is my external SD card.
dasignz said:
Is there a .PIT file that I can use to re-partition my phone? Seems like the partition is bad or corrupted. All attempts to install stock firmware have failed. CWM works fine, but I cannot mount anything. The only thing I can mount is my external SD card.
Click to expand...
Click to collapse
Does anyone know where I can get a .PIT file for a Sprint Galaxy S3? I have tried just about everything, and the failure keeps happening when it tries to write an .img to the phone in odin 3.0.7. I want to try and re-partition the phone to see if that fixes any corrupt partitions to be able to write to the phone.
dasignz said:
Does anyone know where I can get a .PIT file for a Sprint Galaxy S3? I have tried just about everything, and the failure keeps happening when it tries to write an .img to the phone in odin 3.0.7. I want to try and re-partition the phone to see if that fixes any corrupt partitions to be able to write to the phone.
Click to expand...
Click to collapse
http://invisiblek.org/sph-i710/ (sic)
Related
Cannot boot into my backup...just loops
Can get into recovery mode but ODIN does not see my phone
Cannot perform a wipe just hangs at Formatting /chache... then nothin??
Nothing has worked on this today wish I hadn't even tried a custom rom and I followed all the instructions...
While performing a recovery it gets to this line
Restoring cache...
Then the phone cuts off
And reboots to the Samsung blue swirl....but half way through that it cuts out and reboots...and so on
Can someone please help
I have downloaded N7105XXDMC3_N7105OLBDMD1_N7105DXDMC1_HOME.tar
But when I use ODIN I get following
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7105XXDMC3_N7105OLBDMD1_N7105DXDMC1_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> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any help is much appreciated
Thanks
Try and use a different usb port or cable .
Sent from my GT-N7100 using xda premium
have you tried installing a different rom by placing it on sdcard from recovery?
iam123 said:
have you tried installing a different rom by placing it on sdcard from recovery?
Click to expand...
Click to collapse
I dont have any links....the only 2 ZIP roms I could find both failed
Now it looks like my note 2 is bricked
Currently trying ODIN with an official MD5 rom...will know if its working in few mins
EFCLEE said:
I dont have any links....the only 2 ZIP roms I could find both failed
Now it looks like my note 2 is bricked
Currently trying ODIN with an official MD5 rom...will know if its working in few mins
Click to expand...
Click to collapse
EFCLEE could you please tell me if you are able to go in to Recovery Mode ?
I provide the link to ROM ,
and which Version of Note to is this please confirm it is it N7100 International Version or Carrier Based ?
aukhan said:
EFCLEE could you please tell me if you are able to go in to Recovery Mode ?
I provide the link to ROM ,
and which Version of Note to is this please confirm it is it N7100 International Version or Carrier Based ?
Click to expand...
Click to collapse
Recovery mode YES
Restoring backup >>>> Restoring cache...(i see this line for about 1 minute then phone cuts off reboots...then just loops)
Will try your link now - thanks for your help
EFCLEE said:
Recovery mode YES
Restoring backup >>>> Restoring cache...(i see this line for about 1 minute then phone cuts off reboots...then just loops)
Will try your link now - thanks for your help
Click to expand...
Click to collapse
Download the Rom place it on SD and flash it you will be good to go , make sure while the download is going on to read the Steps carefully and understand them on how to flash it ,
I would also suggest you to slow down the pace and go calm as your trying to do so many things at the same time rather follow the protocol ,
Your phone is not Bricked :good:
Hi all, i have a n7100 and the problem was that it just rebooted from nothing and was stuck on samsung logo, then i took it to the official repair center and they couldn do anything and told me that they needed to send it to samsung for repair but they will not do that due to root... so i took it to samsung autorized repair center and the same, they just tried to upload the stock rom but nothing... wont boot, buy a new board will cost me around $600 with those guys... so the problem is this
I can enter download mode and recovery:good:, so:
using odin, all roms (4 dif roms) fail to upload at sboot.bin
<ID:0/011> sboot.bin
<ID:0/011> FAIL!
(using 2 dif machines and 2 dif cables, all 4 roms)
then i tried to reformat using pit "N7100_t03g_0907-stock.pit" and
checking [Re-Partition] then it says there is no pit partition
<ID:0/003> Get PIT for mapping..
<ID:0/003>
<ID:0/003> There is no PIT partition.
the only rom i was able to fully upload was N7100UBALJ2_N7100TCEALJ1_TCE
but because it contains not the sboot.bin file...
still not booting
also using CWM recovery 6.0.1.4 i can't mount cache, system, data, sdcard neither format
[Error mounting /cache!] etc etc etc
i even used aromafm http://forum.xda-developers.com/showthread.php?t=1646108 to see files on internal sdcard but all those mentioned folders-partitions apear as empty folders but folders like dev, etc, lib, proc, res, sbin, sys, tmp apear ok (files inside)
and one final thing i cant replace CWM recovery for TWRP or stock recovery, i have both odin and sdcard versions but after finishing succesfully, rebooting and entering recovery again there is CWM...
so my questions are:
is there any other way to repartition not using odin+PIT
is there any utility to check internal sdcard integrity?
what about sboot.bin not being able to flash
any ideas?
At download mode is it writing the model of the phone?
Sent from my GT-N7100 using Tapatalk 2
vagsvag said:
At download mode is it writing the model of the phone?
Sent from my GT-N7100 using Tapatalk 2
Click to expand...
Click to collapse
yes it says:
odin mode
prod name: GT-N7100
cus bin downloads: yes (1 counts)
curr binary: custom
sys status: custom
mrshdw said:
yes it says:
odin mode
prod name: GT-N7100
cus bin downloads: yes (1 counts)
curr binary: custom
sys status: custom
Click to expand...
Click to collapse
Ok you have not sds for sure
You had install before 4.3 leak or mj5 bootloader?
vagsvag said:
Ok you have not sds for sure
You had install before 4.3 leak or mj5 bootloader?
Click to expand...
Click to collapse
nope still dont know much about bootloaders, will you please show me steps or thread
willing to do anything before emmc chip replacement, thanks!
mrshdw said:
nope still dont know much about bootloaders, will you please show me steps or thread
willing to do anything before emmc chip replacement, thanks!
Click to expand...
Click to collapse
I don't think you need replacement something didn't went well
I saw that cwm gave you message for broken cache partition etc
Take a look here chainfire has a fix for broken cache partition
http://forum.xda-developers.com/showthread.php?t=1932327
---------- Post added at 11:38 AM ---------- Previous post was at 11:15 AM ----------
It is not necessary to flash bootloader if you didn't touch it.
Also is dangerous if something happens you can't recover after.
vagsvag said:
I don't think you need replacement something didn't went well
I saw that cwm gave you message for broken cache partition etc
Take a look here chainfire has a fix for broken cache partition
http://forum.xda-developers.com/showthread.php?t=1932327
---------- Post added at 11:38 AM ---------- Previous post was at 11:15 AM ----------
It is not necessary to flash bootloader if you didn't touch it.
Also is dangerous if something happens you can't recover after.
Click to expand...
Click to collapse
yaep already tried that before, and now green button says PASS
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> cache.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Completed..
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 1 / failed 0)
but still cache cant mount in CWM, some messages [Can't mount /cache/recovery/command] and [Error mounting /cache] as those msgs appears always
Try this recovery it has 2 versions tar to flash via pc odin or zip to flash via cwm. Prefer odin, maybe cwm is broken.
http://forum.xda-developers.com/showthread.php?t=2028103
You are sure also when you try to flash that any kies process is not running at background.
vagsvag said:
Try this recovery it has 2 versions tar to flash via pc odin or zip to flash via cwm. Prefer odin, maybe cwm is broken.
http://forum.xda-developers.com/showthread.php?t=2028103
You are sure also when you try to flash that any kies process is not running at background.
Click to expand...
Click to collapse
via odin it passes - green button
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_5.15.0-n7100.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Removed!!
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Added!!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
after rebooting same CWM 6.0.1.4 appears
the zip file installed file via cwm also passes it took a while but at the end all ok
reboot but again same CWM
and yes sure kies is not in the system as only installed and uninstalled for the drivers
tried few different recoverys - different versions - oding & cwm install zip file from sdcard but all refuses to stay
Seems at reboot cwm installs its self or i don't know what.
Here are rescue firmwares uploaded by a xda member
http://forum.xda-developers.com/showpost.php?p=32273406&postcount=5
If it is work maybe you have problem with efs because samsung updated efs 2 or 3 times i think.
I hope you have an efs backup
Post when you try
---------- Post added at 01:22 PM ---------- Previous post was at 12:51 PM ----------
Also 6.0.1.4 is old cwm and has not been patched with the Sudden Death Syndrome fix.
This problem is 6.0.1.4 problem and the same had other people with other devices
http://forum.xda-developers.com/showthread.php?t=2231928
http://forum.xda-developers.com/showthread.php?t=1937539
See, I had the EXACT same problem, including the "can't mount" messages on recovery and inability to boot.
I ended up fixing it this way:
http://forum.xda-developers.com/showthread.php?p=43760271
Try and see if it helps at all.
Cheers!
Sent from my GT-N7100
vagsvag said:
Seems at reboot cwm installs its self or i don't know what.
Here are rescue firmwares uploaded by a xda member
http://forum.xda-developers.com/showpost.php?p=32273406&postcount=5
If it is work maybe you have problem with efs because samsung updated efs 2 or 3 times i think.
I hope you have an efs backup
Post when you try
---------- Post added at 01:22 PM ---------- Previous post was at 12:51 PM ----------
Also 6.0.1.4 is old cwm and has not been patched with the Sudden Death Syndrome fix.
This problem is 6.0.1.4 problem and the same had other people with other devices
http://forum.xda-developers.com/showthread.php?t=2231928
http://forum.xda-developers.com/showthread.php?t=1937539
Click to expand...
Click to collapse
already tried before with those 3 roms, first 2 failing on sboot.bin
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> modem.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> sboot.bin
<ID:0/005> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
and third one 4 parts + PIT stoping at PIT when ticking [Re-Partiton]
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005>
<ID:0/005> There is no PIT partition.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
and if not, stopping like first 2 on sboot.bin
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
and yes i have efs backup, the first time you select "mount /efs" in cwm it mounts, then if you unmount and mount again, it wont, it says "Error mounting /efs!" (works only for efs folder, but cache system data etc always unable to mount) so i restarted cwm and mount efs folder then using aroma fm copied to external sd cool!
also have some backup that i made with cwm, 3 files "system.ext4.dup" "boot.img" "recovery.img"
vladeco said:
See, I had the EXACT same problem, including the "can't mount" messages on recovery and inability to boot.
I ended up fixing it this way:
http://forum.xda-developers.com/showthread.php?p=43760271
Try and see if it helps at all.
Cheers!
Sent from my GT-N7100
Click to expand...
Click to collapse
im reading... thats an alternative to odin -> HEIMDALL, but before that im just curious about NAND erase all in odin.. will it make the difference? i mean will i be able to continue repartition using PIT file... if so, ill try...
did you were unable to flash sboot.bin also??
This tool you had try?
http://forum.xda-developers.com/showthread.php?t=1923956
He had remove the download link, you can find it here
http://www.skipsoft.net/?page_id=1099
Also take a look and here drketan's tool
http://forum.xda-developers.com/showthread.php?t=2445480
Sent from my GT-N7100 using Tapatalk 2
vagsvag said:
This tool you had try?
http://forum.xda-developers.com/showthread.php?t=1923956
He had remove the download link, you can find it here
http://www.skipsoft.net/?page_id=1099
Also take a look and here drketan's tool
http://forum.xda-developers.com/showthread.php?t=2445480
Sent from my GT-N7100 using Tapatalk 2
Click to expand...
Click to collapse
ok great tools, i have the toolkit but haven't tried all options, going to check more on that and also dr ketans tool
really appreciate all your help, tell you if a have any advance
mrshdw said:
im reading... thats an alternative to odin -> HEIMDALL, but before that im just curious about NAND erase all in odin.. will it make the difference? i mean will i be able to continue repartition using PIT file... if so, ill try...
did you were unable to flash sboot.bin also??
Click to expand...
Click to collapse
For me it only worked when I checked that box. I couldn't flash anything before that. Try not ticking that box and see if it works for you. It didn't for me so it was like a last resort in my case!
About SBOOT: Only the current version at the time, since I had already updated to it and it doesn't support downgrading. Just use the one you're currently using (included in your stock rom) and you should be fine.
I will be more than happy to guide you if you need any help.
Cheers!
Sent from my GT-N7100
vladeco said:
For me it only worked when I checked that box. I couldn't flash anything before that. Try not ticking that box and see if it works for you. It didn't for me so it was like a last resort in my case!
About SBOOT: Only the current version at the time, since I had already updated to it and it doesn't support downgrading. Just use the one you're currently using (included in your stock rom) and you should be fine.
I will be more than happy to guide you if you need any help.
Cheers!
Sent from my GT-N7100
Click to expand...
Click to collapse
ok i get it, if i find the same rom that i had, ill be able to fully flash rom, including sboot.bin, but no -older- roms as "it doesn't support downgrading", well i need to find that rom, dont remember which one i had, but i can keep trying, stock rom is not in the phone anymore, but remember flashing one a few month ago, but dont remember which one i had (sad & sorry)
for now after some downloads ill try to flash again, with and without PIT + Reformat, and if everything fails then use the NAND Erase all option.... seems clear! ill keep you posted
My girlfriends S3 (Bell, I747M, d2can) is currently boot looping. It had a custom ROM on it, but I'll be damned if I could tell you which one. It was working, then it wasn't. No updates, no flash/wipe/etc.
Now I turn on her phone, and it gets to the ROM's boot screen, and just as it's about to complete, it restarts again. I can enter TWRP (2.6.3.1) but it requires a password (which is a bug, afaik). I can press "cancel" and try to reset/wipe, but it won't mount or reset the cache partition, so it fails.
I used Odin (3.07, 3.09) to try and flash TWRP 2.6.3.0 and 2.7.0.0, and both failed. The result was Odin would reboot the phone, then it would enter the same bootloop, and the recovery would still be TWRP 2.6.3.1.
I tried downloading a stock S3 firmware and flashing it with Odin. Same problem.
I've tried new drivers. New cable. New USB port. I've tried using a different computer. Always the same result.
So a summary of what I can/can't do:
Can't use TWRP to reset/wipe
Can't use ADB Sideload
Can't modify device via ADB
CAN see the device via ADB
CAN enter download mode
Any help?
I pulled DMESG at some point during all this. Maybe it can help shed some light: http://pastebin.com/4c2uL3Qq
Dont know how much help it is but I quit using TWRP because of that bug, now I use CWM the philz touch version and haven't seen that again. When you are flashing the rcovery with ODIN you must absolutely uncheck the box for auto reboot. when you get the message that says the flash was successful you should then unplug the USB cable and do a battery pull, reinsert the battery, press the volume up key and the home key, press the power button until it vibrates then release the power button only, once the phone boots into recovery you may release the volume up and home buttons.
If you are trying to flash Stock roms be darn sure you have the right stuff IE AT&T phone using 4.3 you find here on XDA the correct odin flashable tar or for any other use www.sammobile.com if you have a canadian I747M go to www.sammobile.com and find the right one for the bootloaders currently on the phone. If you flash a phone that has 4.3 bootloaders on it with older bootloaders you will have an instant Hard Brick. Use Extreme Caution with bootloaders and ODIN tars. you could also use custom recovery to flash some stock or custom roms too those are alot safer and less likely to hard brick.
I think you are on the right track to trying to fix your ahem her phone, a little patience and reading go a long way IIRC the recovery thread instructions outline the need to uncheck the auto reboot box, with that being said you aren't the first one to over look it I have done it myself a few months ago. I wish you the best of luck and hope that a cache wipe will fix what you have going on if not try a factory reset, Good Luck.
theramsey3 said:
Dont know how much help it is but I quit using TWRP because of that bug, now I use CWM the philz touch version and haven't seen that again. When you are flashing the rcovery with ODIN you must absolutely uncheck the box for auto reboot. when you get the message that says the flash was successful you should then unplug the USB cable and do a battery pull, reinsert the battery, press the volume up key and the home key, press the power button until it vibrates then release the power button only, once the phone boots into recovery you may release the volume up and home buttons.
If you are trying to flash Stock roms be darn sure you have the right stuff IE AT&T phone using 4.3 you find here on XDA the correct odin flashable tar or for any other use www.sammobile.com if you have a canadian I747M go to www.sammobile.com and find the right one for the bootloaders currently on the phone. If you flash a phone that has 4.3 bootloaders on it with older bootloaders you will have an instant Hard Brick. Use Extreme Caution with bootloaders and ODIN tars. you could also use custom recovery to flash some stock or custom roms too those are alot safer and less likely to hard brick.
I think you are on the right track to trying to fix your ahem her phone, a little patience and reading go a long way IIRC the recovery thread instructions outline the need to uncheck the auto reboot box, with that being said you aren't the first one to over look it I have done it myself a few months ago. I wish you the best of luck and hope that a cache wipe will fix what you have going on if not try a factory reset, Good Luck.
Click to expand...
Click to collapse
Appreciate all the help! I've tried pretty much every combination.
I've turned off auto-reboot, flashed, but Odin stops at:
<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> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
Click to expand...
Click to collapse
I assume that's where it's supposed to be. Then I enter recovery and it's still the same TWRP 2.6.3.1. Very strange.
I don't think her phone is using 4.3 bootloaders, as I don't remember them being available when I flashed this phone. I'm a Nexus guy, so maybe I'm doing something wrong this time.
EDIT: I also seem to recall on my phones that when I flashed something in Download/Fastboot mode, there was a progress bar of sorts on the phone itself indicating it was receiving something. On this phone it doesn't display anything to imply something's happening.
Boot into download and let us know what it says on the download screen. If you have the 4.3 bootloader, try flashing a pre-rooted 4.3 Bell ROM using Odin 3.07. If you have a lower version bootloader, try flashing a pre-rooted 4.1.1 or 4.1.2 ROM.
http://forum.xda-developers.com/sho...mctr=(not provided)&__utmv=-&__utmk=139036464
In Odin, don't check auto reboot. When you see reset in the status windows, disconnect the USB cable and pull the battery. Boot into recovery and wipe cache, data, and reboot.
Thanks for the reply! I'm 99% sure it's a pre-4.3 bootloader. Here's what it shows in DL mode:
ODIN MODE
PRODUCT NAME: SHG-I747M
CUSTOM BINARY DOWNLOAD: Yes (2 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
DUALCOMM SECUREBOOT: ENABLE
If I recall correctly, a 4.3 bootloader would show two more lines at the bottom.
Tried installing a 4.1.1 ROM (root66_BMC_I747MVLDLK4)
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_BMC_I747MVLDLK4.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> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
4.1.2 (root66_BMC_I747MVLDMF1.7z)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_BMC_I747MVLDMF1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I feel it's worth mentioning again: At no point, while using Odin, does the phone display a transfer bar of any sort.
Try installing Philz Touch recovery via Odin and see if you can boot into recovery. Copy a custom ROM on an external SD card and see if you can flash that ROM from recovery.
audit13 said:
Try installing Philz Touch recovery via Odin and see if you can boot into recovery. Copy a custom ROM on an external SD card and see if you can flash that ROM from recovery.
Click to expand...
Click to collapse
Tried Philz and Odin still doesn't seem to have flashed it.
I'll try with an SD card.
X04D said:
Tried Philz and Odin still doesn't seem to have flashed it.
I'll try with an SD card.
Click to expand...
Click to collapse
Try this: when you flash with Odin, uncheck auto reboot, start the flash process. When you see the word reset in the status window, remove the USB cable, pull the battery, and boot into recovery.
Hello!
I had a S3 i747 which receive OTA to latest update. Everything was fine except lagging interface and not working wifi\tethering so I did factory reset from "Settings". After that it is stuck on Samsung logo. So I tried to flash CWM 6.0.4.7 (guide on CM wiki, via Heimdall ) and CM 11 which failed then i tried CM 10.2 and then different ROMs from development thread, nothing worked...(all of these via CWM)
CWM refused to flash any of them except CM-11. Result of flsahing CM-11 is a phone stuck on Cyanogenmod screen(rotating and blinking LED).
What is my problem? Is it recovery or ???
ODIN Log:
<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)
Since you updated via OTA to the latest ROM, which would be Kit Kat, do not use Odin to flash any stock ROM unless that ROM has been specifically compiled for flashing in Odin. With the 4.4 bootloader, attempts to downgrade the bootloader or modem can brick the phone.
Do not flash the LK3 firmware as this is 4.1.1 and you have 4.4.2.
Were you able to flash CWM onto your phone?
audit13 said:
Since you updated via OTA to the latest ROM, which would be Kit Kat, do not use Odin to flash any stock ROM unless that ROM has been specifically compiled for flashing in Odin. With the 4.4 bootloader, attempts to downgrade the bootloader or modem can brick the phone.
Do not flash the LK3 firmware as this is 4.1.1 and you have 4.4.2.
Were you able to flash CWM onto your phone?
Click to expand...
Click to collapse
Yes. CWM-Touch is working nice but can not access internal sdcard and any partition on it..
Can you access the external SD card? You could try flashing a ROM from there.
Have you looked here for a possible solution: http://forum.xda-developers.com/galaxy-s3-att/general/ucuemjb-to-ucufne4-firmware-update-t2808654
audit13 said:
Can you access the external SD card? You could try flashing a ROM from there.
Have you looked here for a possible solution: http://forum.xda-developers.com/galaxy-s3-att/general/ucuemjb-to-ucufne4-firmware-update-t2808654
Click to expand...
Click to collapse
I can and I did try flash another ROM from there from CWM. But all of them are beeing aborted (except CM-11) which is sticking at boot animation...
If it hangs at boot you probably just need to factory reset.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
elnurmen said:
I can and I did try flash another ROM from there from CWM. But all of them are beeing aborted (except CM-11) which is sticking at boot animation...
Click to expand...
Click to collapse
What error is CWM reporting when flashing a ROM?
audit13 said:
What error is CWM reporting when flashing a ROM?
Click to expand...
Click to collapse
I don't exactly remember but basically output is like:
1) Selected zip file...
2) Opening zip file
3) Installation aborted...
Nothing special...no error reported...
But I should add that when i try to format \system it said that internal sdcard is unavailable...
It's weird that CWM doesn't give an error. Without an error code, it's difficult to determine exactly what is causing the error.
What ROMs did you try?
Could've sworn I replied to this earlier! Anyway, flash again, and after it fails, do not reboot, but go back to the Advanced menu and copy log to sdcard. (in TWRP, if the external card is selected to flash from, the recovery.log will be copied there. Internal sd if you are flashing from the internal one. Not sure if it's the same in CWM)
Then attach the log here. It will usually have more detailed information about the failure/error.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
So newb questions and might have been answered but I have been unable to find the answer I'm looking for.
Background:
SGH T999
Original I was on 4.1 stock. I used towelroot and was able to root and all that jazz. I uploaded an old version of CWM to my phone and was unable to flash and ROMs, they would all hang on the Samsung Galaxy SIII screen.
I updated CWM to put on a Cyanogen Mode ROM and all was good. I tried out a couple other ROMs then decided I wanted to go back to stock and see how stock 3.3 or 3.4 was. I tried using Odin to bring back to stock and no luck. I then installed PhilZ recovery and booted to Wicked ROM for 4.1. After this I got current TWRP and tried to update other roms. I went into ROM manager switched over to CWM 6.0.4.5 then updated my kernel. At some point along the way I noticed that on the internal sd card I have a 0 directory inside my 0 directory.
Now when I reboot my phone into Recovery mode I see a Samsung Galaxy SIII screen with the Cyanogen guy on it, then it loads to CWM but nothing is on the screen but the hat, then after a couple of seconds it loads to a Samsung screen quickly, then to the Samsung Galaxy SIII and hangs indefinitely. I'm still able to get the phone to go into download mode fine. Now I'm trying to just bring back to stock but not having any luck. Here's my repro:
1. Put hardware into download mode (HOME + Vol Down + Lock).
2. Open Odin 3.09 as Admin (I'm using Win 7).
3. Connect hardware to computer (Odin recognizes 0:Com5).
4. Place "T999UVDMD5_T999TMBDMD5_T999UVDMD5_HOME.tar.md5" in AP field.
5. With only "Auto Reboot" and "F.Reset Time" selected press Start button.
RESULT:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVDMD5_T999TMBDMD5_T999UVDMD5_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
Then on my hardware I get
ODIN MODE
PRODUCT NAME: SGH-T999
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Offical
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 1
BOOTLOADER AP SWREV: 1
SW REV CHECK FAIL : Fused 1 > Binary 0
Click to expand...
Click to collapse
Any idea's how I can bring this back?
tiger_johnson said:
*snip*
Any idea's how I can bring this back?
Click to expand...
Click to collapse
Hmm, if the device is recognized in your PC by ODIN there's still hope. I personally recommend TWRP (LINK for latest ODIN flashable version) for everything as CWM has caused havoc with my phone before. Stay away from it. IF you can still access recovery, do format everything, including the internal SDcard. Also please use the PIT file when trying to use ODIN for the MD5 firmware you're choosing. LINK for the PIT file (choose your model's PIT and put it on the PIT part of ODIN then proceed on flashing the MD5 firmware - credit goes to DocHoliday for the PIT files). That little file can sometimes fix stuff when trying to ODIN the device back to stock firmware. Just giving ideas, don't give up and best of lucks!
You can't flash MD5. It looks like you are currently running MJC base firmware which means you can ONLY flash MJC or NC2 with Odin. Do not try to downgrade via any method or it will hard brick your device.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
---------- Post added at 12:25 AM ---------- Previous post was at 12:23 AM ----------
"SW REV CHECK: Fused 1" means you currently have MJC. It will change to Fused 2 if you update to NC2. (If I'm remembering all those nemesis right).
Just FYI in case anyone was wondering.
Sent from my SAMSUNG-SGH-I747 using Tapatalk