Hi together, before i try to use a "last exit" by buying me an "Unbrick - JTAG", i thought if one could may help me, it will be found here or nowhere.
I started with a new S3 Mini (Telekom Branding Android 4.1.2 Germany). Using the SAMSUNG GALAXY S3 MINI TOOLKIT Pro, (mskip) i rooted it and flashed also the CMW Recovery. Within the CMW Recovery i made a Backup before i flashed a CUSTOM-ROM ( "enox reVenge one" ROM ).
Flashing went trough without Errors, afterwards i did a "wipe factory reset", a "wipe cache" and a "wipe dalvik cache". Then after a reboot the "disaster" was there with a permanent bootloop (Samsung starting Screen with model, etc.) and i couldn´t get into Recovery mode anymore. As i found out, the Download mode still worked and i could still flash using ODIN. So i studied some articles here and i followed procedures to re install a common Stock-Rom together with a PIT file for the I8190N (! found also her specific for the "N" option). The flashes went trough without errors, but unfortunately without positive effects to come over the bootloop. I read some articles about ADB, i downloaded the Android SDK, and tried to use some shell commands to get into recovery mode with no success, because i got allways the message "device not found". Within the SDK package also the USB Drivers were installed and when i connected the S3 via USB, Drivers were installed under "WXP" without any errors (I use WXP instead of W7 or W8 which i have also available). At a certain time i recognised that the SAMSUNG GALAXY S3 MINI TOOLKIT Pro, give me an ADB environment just on a selectable menuelevel, which can be used more comfortable as the native ADB environment. I recognised that i could use there just a function like "reboot in recovery mode".
The problem just ist, that of coarse also there the "device not found" problem is just the same (same Environment on Laptop). I just have any idee anymore what to do, and either i can solve the problem finaly here with your support (maybe something else could be tried out using ODIN flashing), or i take the last exit "and buy me the mentioned Unbrick - JTAG.
Instead of this i would more like to buy you a beer or to donate for a beer for someone of you.
We will see what happens, anyway my best wishes to you.
reflash the firmware (make sure that it is the right firmware for your variant) with pit file.
if you stuck in bootloop, flash param file with odin http://forum.xda-developers.com/attachment.php?attachmentid=1937012&d=1367738404 (it works also for N)
Unfortunately no success
Did it as recommended with no success, files used within flashing:
First ODIN Flash,
I8190NXXAMD3_I8190NOXAAMD3_DBT.zip
i8190N_goldenxx.pit
Second ODIN Flash,
PARAM_I8190.tar.md5
The loop still remains. here the logs (copied in one file) from ODIN (two separate runs):
<ID:0/015> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I8190XXAMB3_I8190DTMAMB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Set PIT file..
<ID:0/015> DO NOT TURN OFF TARGET!!
<ID:0/015> Get PIT for mapping..
<ID:0/015> Firmware update start..
<ID:0/015> boot.img
<ID:0/015> NAND Write Start!!
<ID:0/015> STE_boot1.img
<ID:0/015> STE_boot2.img
<ID:0/015> modem.bin
<ID:0/015> system.img
<ID:0/015> cache.img
<ID:0/015> hidden.img
<ID:0/015> RQT_CLOSE !!
<ID:0/015> RES OK !!
<ID:0/015> Removed!!
<ID:0/015> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
New Start of ODIN as Admin
<ID:0/015> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PARAM_I8190.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Get PIT for mapping..
<ID:0/015> Firmware update start..
<ID:0/015> param.lfs
<ID:0/015> NAND Write Start!!
<ID:0/015> RQT_CLOSE !!
<ID:0/015> RES OK !!
<ID:0/015> Removed!!
K.r. Heinz :crying:
samersh72 said:
reflash the firmware (make sure that it is the right firmware for your variant) with pit file.
if you stuck in bootloop, flash param file with odin http://forum.xda-developers.com/attachment.php?attachmentid=1937012&d=1367738404 (it works also for N)
Click to expand...
Click to collapse
htruempler said:
Did it as recommended with no success, files used within flashing:
First ODIN Flash,
I8190NXXAMD3_I8190NOXAAMD3_DBT.zip
i8190N_goldenxx.pit
Second ODIN Flash,
PARAM_I8190.tar.md5
The loop still remains. here the logs (copied in one file) from ODIN (two separate runs):
<ID:0/015> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I8190XXAMB3_I8190DTMAMB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Set PIT file..
<ID:0/015> DO NOT TURN OFF TARGET!!
<ID:0/015> Get PIT for mapping..
<ID:0/015> Firmware update start..
<ID:0/015> boot.img
<ID:0/015> NAND Write Start!!
<ID:0/015> STE_boot1.img
<ID:0/015> STE_boot2.img
<ID:0/015> modem.bin
<ID:0/015> system.img
<ID:0/015> cache.img
<ID:0/015> hidden.img
<ID:0/015> RQT_CLOSE !!
<ID:0/015> RES OK !!
<ID:0/015> Removed!!
<ID:0/015> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
New Start of ODIN as Admin
<ID:0/015> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PARAM_I8190.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Get PIT for mapping..
<ID:0/015> Firmware update start..
<ID:0/015> param.lfs
<ID:0/015> NAND Write Start!!
<ID:0/015> RQT_CLOSE !!
<ID:0/015> RES OK !!
<ID:0/015> Removed!!
K.r. Heinz :crying:
Click to expand...
Click to collapse
Try reflashing param as .tar not .tar.md5
serophia said:
Try reflashing param as .tar not .tar.md5
Click to expand...
Click to collapse
md5 is valid so I don't think there would be any difference except from removed security from flashing bad files.
Try to first flash stock recovery then firmware.
Stock recovery
Still no change in Bootloop
Hi, thanks to all of you for your participation and supporting me :good:
Well, did it as recommended, unfortunately still no success.
Three flash runs, first, stock recovery, then Firmware. checking if successfull, bad result. Third flash again param, bad result.
Still bootloop, no opportunity to launch recovery.
First Flash Stock Recovery Log of ODIN:
<ID:0/015> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I8190_stock-recovery.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Get PIT for mapping..
<ID:0/015> Firmware update start..
<ID:0/015> recovery.img
<ID:0/015> NAND Write Start!!
<ID:0/015> RQT_CLOSE !!
<ID:0/015> RES OK !!
<ID:0/015> Removed!!
<ID:0/015> Removed!!
<ID:0/015> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Second Flash Firmware
<ID:0/015> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I8190XXAMB3_I8190DTMAMB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Get PIT for mapping..
<ID:0/015> Firmware update start..
<ID:0/015> boot.img
<ID:0/015> NAND Write Start!!
<ID:0/015> STE_boot1.img
<ID:0/015> STE_boot2.img
<ID:0/015> modem.bin
<ID:0/015> system.img
<ID:0/015> cache.img
<ID:0/015> hidden.img
<ID:0/015> RQT_CLOSE !!
<ID:0/015> RES OK !!
<ID:0/015> Removed!!
<ID:0/015> Removed!!
<ID:0/015> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Third Flash PARAM
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PARAM_I8190.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/015> Added!!
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Get PIT for mapping..
<ID:0/015> Firmware update start..
<ID:0/015> param.lfs
<ID:0/015> NAND Write Start!!
<ID:0/015> RQT_CLOSE !!
<ID:0/015> RES OK !!
<ID:0/015> Removed!!
<ID:0/015> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
K.r. Heinz :crying::crying:
htruempler said:
Hi, thanks to all of you for your participation and supporting me :good:
Well, did it as recommended, unfortunately still no success.
Three flash runs, first, stock recovery, then Firmware. checking if successfull, bad result. Third flash again param, bad result.
Still bootloop, no opportunity to launch recovery.
K.r. Heinz :crying::crying:
Click to expand...
Click to collapse
if you can not boot into recovery to wipe, flash this .tar.md5 as pda (the same for I8190 and I8190N) http://forum.xda-developers.com/attachment.php?attachmentid=1540051&d=1354753346
No success, Bootloop remains
Many thanks, but no success. I have the impression it might have to do with the bootloader itself. K.r. Heinz :crying:
samersh72 said:
if you can not boot into recovery to wipe, flash this .tar.md5 as pda (the same for I8190 and I8190N) http://forum.xda-developers.com/attachment.php?attachmentid=1540051&d=1354753346
Click to expand...
Click to collapse
Did you try the 3 button combo for recovery: http://forum.xda-developers.com/showthread.php?t=2157105?
Start in recovery and do a factory reset after you flash a stock rom in Odin.
Still no success
Hi, i tried the I8190.tar.md5, unfortunately without success, because i´m not sure about the effect and the battery load, i decided not to try as well the I8190 серв. укр.rar package (might be i don´t have enough battery load and within the permanent bootloop, loading doesn´t seem to work). I think i will stop at that stage with this huge amount of attemps and buy me a jtag unbrick as mentioned when i started this thread. In case somebody would know how charge the battery in this stage, i would give the I8190 серв. укр.rar a final try out. Anyway i would like to say thanks to all of you because of your participation and support to me. Great community here!!!
deconectat said:
Did you try the 3 button combo for recovery: http://forum.xda-developers.com/showthread.php?t=2157105?
Start in recovery and do a factory reset after you flash a stock rom in Odin.
Click to expand...
Click to collapse
Doesn't the phone charge when it's off? Try to unplug the battery, plug it back in and connect the charger.
Same here! I have TWRP recovery and it shows TeamWin splash screen for 1 second and shuts off!
KoolKid98189 said:
Same here! I have TWRP recovery and it shows TeamWin splash screen for 1 second and shuts off!
Click to expand...
Click to collapse
go to download mode and flash param.tar (search in forum).
if this isn´t successful, download This ROM (LaFleur) and follow This Instructions.
After that you can flash every ROM you like
I flashed a wrong script one time - nothing worked. So i did it like i described and everything worked
JackoMJ said:
go to download mode and flash param.tar (search in forum).
if this isn´t successful, download This ROM (LaFleur) and follow This Instructions.
After that you can flash every ROM you like
I flashed a wrong script one time - nothing worked. So i did it like i described and everything worked
Click to expand...
Click to collapse
What's so special about the LaFleur ROM though?
I have the same problem and no way to make get it out of bootloop
htruempler said:
Hi together, before i try to use a "last exit" by buying me an "Unbrick - JTAG", i thought if one could may help me, it will be found here or nowhere.
I started with a new S3 Mini (Telekom Branding Android 4.1.2 Germany). Using the SAMSUNG GALAXY S3 MINI TOOLKIT Pro, (mskip) i rooted it and flashed also the CMW Recovery. Within the CMW Recovery i made a Backup before i flashed a CUSTOM-ROM ( "enox reVenge one" ROM ).
Flashing went trough without Errors, afterwards i did a "wipe factory reset", a "wipe cache" and a "wipe dalvik cache". Then after a reboot the "disaster" was there with a permanent bootloop (Samsung starting Screen with model, etc.) and i couldn´t get into Recovery mode anymore. As i found out, the Download mode still worked and i could still flash using ODIN. So i studied some articles here and i followed procedures to re install a common Stock-Rom together with a PIT file for the I8190N (! found also her specific for the "N" option). The flashes went trough without errors, but unfortunately without positive effects to come over the bootloop. I read some articles about ADB, i downloaded the Android SDK, and tried to use some shell commands to get into recovery mode with no success, because i got allways the message "device not found". Within the SDK package also the USB Drivers were installed and when i connected the S3 via USB, Drivers were installed under "WXP" without any errors (I use WXP instead of W7 or W8 which i have also available). At a certain time i recognised that the SAMSUNG GALAXY S3 MINI TOOLKIT Pro, give me an ADB environment just on a selectable menuelevel, which can be used more comfortable as the native ADB environment. I recognised that i could use there just a function like "reboot in recovery mode".
The problem just ist, that of coarse also there the "device not found" problem is just the same (same Environment on Laptop). I just have any idee anymore what to do, and either i can solve the problem finaly here with your support (maybe something else could be tried out using ODIN flashing), or i take the last exit "and buy me the mentioned Unbrick - JTAG.
Instead of this i would more like to buy you a beer or to donate for a beer for someone of you.
We will see what happens, anyway my best wishes to you.
Click to expand...
Click to collapse
Seems like a soft brick, nothing to worry about as of yet. Try using Unified Android Toolkit to flash stock firmware following the on screen instructions.
uvedovle said:
I have the same problem and no way to make get it out of bootloop
Click to expand...
Click to collapse
Discharge the battery and return it to the seller and get a replacement. This is last resort and that's what I did and got a free replacement in sacrifice of my data.
samersh72 said:
if you can not boot into recovery to wipe, flash this .tar.md5 as pda (the same for I8190 and I8190N) http://forum.xda-developers.com/attachment.php?attachmentid=1540051&d=1354753346
Click to expand...
Click to collapse
Thanks for the WIPE_I8190.zip
I was stuck in bootloop, and after i flashed this file in Odin as PDA, my phone works. Thanks ! :good:
resolve
hi mate got one for u to try worked on mine as had same problem dowload odim 3.07 then registure on samfirmware website then look for the uk o2 stock firmware list hope this helps and u get phone back on
let me nw how u get on
htruempler said:
Hi together, before i try to use a "last exit" by buying me an "Unbrick - JTAG", i thought if one could may help me, it will be found here or nowhere.
I started with a new S3 Mini (Telekom Branding Android 4.1.2 Germany). Using the SAMSUNG GALAXY S3 MINI TOOLKIT Pro, (mskip) i rooted it and flashed also the CMW Recovery. Within the CMW Recovery i made a Backup before i flashed a CUSTOM-ROM ( "enox reVenge one" ROM ).
Flashing went trough without Errors, afterwards i did a "wipe factory reset", a "wipe cache" and a "wipe dalvik cache". Then after a reboot the "disaster" was there with a permanent bootloop (Samsung starting Screen with model, etc.) and i couldn´t get into Recovery mode anymore. As i found out, the Download mode still worked and i could still flash using ODIN. So i studied some articles here and i followed procedures to re install a common Stock-Rom together with a PIT file for the I8190N (! found also her specific for the "N" option). The flashes went trough without errors, but unfortunately without positive effects to come over the bootloop. I read some articles about ADB, i downloaded the Android SDK, and tried to use some shell commands to get into recovery mode with no success, because i got allways the message "device not found". Within the SDK package also the USB Drivers were installed and when i connected the S3 via USB, Drivers were installed under "WXP" without any errors (I use WXP instead of W7 or W8 which i have also available). At a certain time i recognised that the SAMSUNG GALAXY S3 MINI TOOLKIT Pro, give me an ADB environment just on a selectable menuelevel, which can be used more comfortable as the native ADB environment. I recognised that i could use there just a function like "reboot in recovery mode".
The problem just ist, that of coarse also there the "device not found" problem is just the same (same Environment on Laptop). I just have any idee anymore what to do, and either i can solve the problem finaly here with your support (maybe something else could be tried out using ODIN flashing), or i take the last exit "and buy me the mentioned Unbrick - JTAG.
Instead of this i would more like to buy you a beer or to donate for a beer for someone of you.
We will see what happens, anyway my best wishes to you.
Click to expand...
Click to collapse
Hello everybody. Yesterday Im trying to upgrade to my s3 mini to kitkat 4.4.4. but then my phone is on bootloop. And then I try to boot to recovery mode and wipe dalvik cache. but it still not working, and then I tried to flash again with recovery tar md5. And now after samsung logo appear, its only black screen. Can you help me?
Related
I was trying to root my galaxy note, I download the rooted stock rom (N7000DXLC2) from here http://forum.xda-developers.com/showthread.php?t=1535025
but the odin failed and showing this
<ID:0/013> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Rooted_Stock_Odex_N7000DXLC2.tar.md5 is valid.
<OSM> MODEM.tar.md5 is valid.
<OSM> CSC_N7000OLBLC2.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/013> Odin v.3 engine (ID:13)..
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Get PIT for mapping..
<ID:0/013> Firmware update start..
<ID:0/013> factoryfs.img
<ID:0/013> NAND Write Start!!
<ID:0/013>
<ID:0/013> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
then my phone can't boot anymore, it jus stuck at the samsung n7000 screen,
i tried to download stock rom and flash again, but it failed like above,
and when i go try to flash the kernel, it success to go to the recovery mode,
but it showing error like
E:Error in /cache/recovery/sec_csc.zip (status 7)
And i maybe forgot to enable usb debugging before i root, is this the cause? how i enable it now?
what can i do now? I tried to change port, change pc, uninstall kies, reinstall driver, close antivirus, and all doesn't work, please help...
To be sure, take out all unnecessary USB devices and use a USB port that's directly attached to your motherboard. Without your phone attached load Odin and load all files. Put the phone in Download mode and hook it up to your pc. When Odin recognizes it then try and flash again.
Make sure there's not a trace of Kies on the pc, just have the drivers installed.
USB debugging should not have to be enabled. There's no way of enabling it without booting up the phone and setting it in the options anyway.
bioweb said:
To be sure, take out all unnecessary USB devices and use a USB port that's directly attached to your motherboard. Without your phone attached load Odin and load all files. Put the phone in Download mode and hook it up to your pc. When Odin recognizes it then try and flash again.
Make sure there's not a trace of Kies on the pc, just have the drivers installed.
USB debugging should not have to be enabled. There's no way of enabling it without booting up the phone and set it in the options anyway.
Click to expand...
Click to collapse
I tried that, and I uninstalled the kies,
but the odin still showing the same error.
PROBLEM SOLVED
for who facing the same problem, just include a pit file in PIT,u can find it here
http://forum.xda-developers.com/showpost.php?p=23234683&postcount=10
solving this for whole day,thanks god it worked......
17n337 said:
PROBLEM SOLVED
for who facing the same problem, just include a pit file in PIT,u can find it here
http://forum.xda-developers.com/showpost.php?p=23234683&postcount=10
solving this for whole day,thanks god it worked......
Click to expand...
Click to collapse
CAUTION : Just dont go on blindly flashing the PIT file. Its a repartitioning file. To be used only when your partition is corrupted.
Galaxy Note stuck
hello,
I was running stock ICS 4.0.4 on my GT-N7000. I rooted my device. Took the titanium backup.
After this, i opened odin. Under phone i provided the path to my downloaded ICS 4.0.4 file. Odin started flashing the device but operation failed showing:
<ID:0/010> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000DDLRB_N7000ODDLR4_N7000DDLR1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> factoryfs.img
<ID:0/010> NAND Write Start!!
<ID:0/010> Transmission Complete..
<ID:0/010> Now Writing.. Please wait about 2 minutes
<ID:0/010>
<ID:0/010> Receive Response form LOKE
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Tried many times but showing the same error everytime.
I am not able to go into the recovery mode......although i can go into the download mode.
When i reboot it says "Firmware upgrade encountered an issue. Please select recovery mode in kies & try again." There is no samsung logo or GT-N7000 logo when you reboot your phone. You only see this warning.
I have some imp data on my internal memory(Phone storage). I have to save that data. Please please please help me out. Is there any way to recover phone storage data???
Can anyone explain my current situation...???
vinay28761 said:
I was running stock ICS 4.0.4 on my GT-N7000. I rooted my device. Took the titanium backup.
...
After this, i opened odin. Under phone i provided the path to my downloaded ICS 4.0.4 file. Odin started flashing the device but
...
<OSM> N7000DDLRB_N7000ODDLR4_N7000DDLR1_HOME.tar.md5 is valid.
...
Can anyone explain my current situation...???
Click to expand...
Click to collapse
First: this thread is marked as solved since april. Chances are very low for a reaction (but at least I did)
Second: Make a new one in Q&A
Third: What do you mean with "Took the TB"? Especially when you flash a new Stock Rom after
Fourth: Did you put the tar-file under "Phone"? Should be "PDA".
Fifth: Read a lot in the stickies here - good start for handling Odin is Dr. Ketan's thread
Sixth: your current situation might result from not reading enough. I hope you didn't brick your device and can restore a running Rom with the instructions from the stickies. Good Luck
how exactly did you reach this situation?
Did you resolve this ?
vinay28761 said:
hello,
I was running stock ICS 4.0.4 on my GT-N7000. I rooted my device. Took the titanium backup.
After this, i opened odin. Under phone i provided the path to my downloaded ICS 4.0.4 file. Odin started flashing the device but operation failed showing:
<ID:0/010> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000DDLRB_N7000ODDLR4_N7000DDLR1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> factoryfs.img
<ID:0/010> NAND Write Start!!
<ID:0/010> Transmission Complete..
<ID:0/010> Now Writing.. Please wait about 2 minutes
<ID:0/010>
<ID:0/010> Receive Response form LOKE
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Tried many times but showing the same error everytime.
I am not able to go into the recovery mode......although i can go into the download mode.
When i reboot it says "Firmware upgrade encountered an issue. Please select recovery mode in kies & try again." There is no samsung logo or GT-N7000 logo when you reboot your phone. You only see this warning.
I have some imp data on my internal memory(Phone storage). I have to save that data. Please please please help me out. Is there any way to recover phone storage data???
Can anyone explain my current situation...???
Click to expand...
Click to collapse
@vinay28761
I have your exact problem. Phone came to me with problem of hanging on Samsung N7000 Logo.
After flash everything, it shows error, exactly like yours.
Were you able to fix it? How ?
dannyogolo said:
@vinay28761
I have your exact problem. Phone came to me with problem of hanging on Samsung N7000 Logo.
After flash everything, it shows error, exactly like yours.
Were you able to fix it? How ?
Click to expand...
Click to collapse
Yes, i resolved it. I just followed dr. ketan's guide to flash through ODIN properly and exactly as described. I would request you to do the same.
Hope it solves your error too. If not, please post your screenshots.
could you jst give me details about dis nand write fail problem?i m having same problem in my gt n7000
Does anyone know where i can download PIT file for samsung gts6802 and a bootloader?
It woulb be very helpful. Thank You
Hi all,
Before I return this device back to Samsung i wanted to check here if anyone had similar Problems or can possibly help with this.
I've never had the Luxury of personally using this Device, the Original Owner bought it and during the OTA it appears something went wrong. Rather than returning it to Samsung directly (they have a notoriously bad reputation of turn around time here) she asked me to have a look at it
Originally it was stuck in a Bootloop of The Intro of the boy looking through the telescope and appearing with the Samsung logo in a recurring Bootloop. Kies (the terrible software it is) is stuck at the connecting screen and doesn't move further than that.
To the jist;
I cant enter Recovery Mode, it takes me directly to the "downloading" screen. I can however boot manually into the Downloading mode. I've tried reflashing the stock recovery with Odin but still won't allow me to get into it, it boots to download mode before I even get a chance to do anything else.
I've tried multiple full firmware's from samsung-updates/sammobile and all drop me back to the same screen (with Odin)
Naturally, I will turn this in to Samsung and wait the time that it takes to have it repaired/replaced for her. I just wanted to know if anyone had any great ideas i could go through before going ahead with this
Thanks in advance
kartoffelpower said:
Hi all,
Before I return this device back to Samsung i wanted to check here if anyone had similar Problems or can possibly help with this.
I've never had the Luxury of personally using this Device, the Original Owner bought it at Duty Free here in Dubai and during the OTA it appears something went wrong. Rather than returning it to Samsung directly (they have a notoriously bad reputation of turn around time here) she asked me to have a look at it
Originally it was stuck in a Bootloop of The Intro of the boy looking through the telescope and appearing with the Samsung logo in a recurring Bootloop. Kies (the terrible software it is) is stuck at the connecting screen and doesn't move further than that.
To the jist;
I cant enter Recovery Mode, it takes me directly to the "downloading" screen. I can however boot manually into the Downloading mode. I've tried reflashing the stock recovery with Odin but still won't allow me to get into it, it boots to download mode before I even get a chance to do anything else.
I've tried multiple full firmware's from samsung-updates/sammobile and all drop me back to the same screen (with Odin)
Naturally, I will turn this in to Samsung and wait the time that it takes to have it repaired/replaced for her. I just wanted to know if anyone had any great ideas i could go through before going ahead with this
Thanks in advance
Click to expand...
Click to collapse
What's the screen you get on Odin? What does it say?
robb13 said:
What's the screen you get on Odin? What does it say?
Click to expand...
Click to collapse
Hi Robb,
Thank you for the reply,
Odin is fine, it flashes without any issues but upon restarting without booting into any special mode, it comes up immediately with "downloading... do not turn of target!!"
When I flash with what i presume would be the correct firmware i get an error (it's bought in Dubai so i figured it was the XSG firmware)
When using the "official XSG" from samsung-updates (zip file EK-GC100_XSG_1_20121121162346) which extracts to GC100XXALK6_GC100OJVALK1_GC100XXALJG_HOME.tar i get this error;
Code:
<ID:0/016> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GC100XXALK6_GC100OJVALK1_GC100XXALJG_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/016> Odin v.3 engine (ID:16)..
<ID:0/016> File analysis..
<ID:0/016> SetupConnection..
<ID:0/016> Initialzation..
<ID:0/016> Get PIT for mapping..
<ID:0/016> Firmware update start..
<ID:0/016> system.img
<ID:0/016> NAND Write Start!!
<ID:0/016> boot.img
<ID:0/016> cache.img
<ID:0/016> hidden.img
<ID:0/016> recovery.img
<ID:0/016> modem.bin
<ID:0/016>
<ID:0/016> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
However if i flash with GC100XXALJF_GC100OXAALJF_GC100XXALJG_HOME.tar it is successful but after rebooting, its stuck in download mode,
here from Odin;
Code:
<ID:0/016> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GC100XXALJF_GC100OXAALJF_GC100XXALJG_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/016> Odin v.3 engine (ID:16)..
<ID:0/016> File analysis..
<ID:0/016> SetupConnection..
<ID:0/016> Initialzation..
<ID:0/016> Get PIT for mapping..
<ID:0/016> Firmware update start..
<ID:0/016> boot.img
<ID:0/016> NAND Write Start!!
<ID:0/016> cache.img
<ID:0/016> hidden.img
<ID:0/016> modem.bin
<ID:0/016> recovery.img
<ID:0/016> system.img
<ID:0/016> RQT_CLOSE !!
<ID:0/016> RES OK !!
<ID:0/016> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/016> Removed!!
<ID:0/016> Added!!
When i boot into download mode/recovery mode myself i'm presented with;
"Odin Mode"
Product Name: EK-GC100_EUR_XX
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Custom
kartoffelpower said:
Hi Robb,
Thank you for the reply,
Odin is fine, it flashes without any issues but upon restarting without booting into any special mode, it comes up immediately with "downloading... do not turn of target!!"
When I flash with what i presume would be the correct firmware i get an error (it's bought in Dubai so i figured it was the XSG firmware)
When using the "official XSG" from samsung-updates (zip file EK-GC100_XSG_1_20121121162346) which extracts to GC100XXALK6_GC100OJVALK1_GC100XXALJG_HOME.tar i get this error;
Code:
<ID:0/016> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GC100XXALK6_GC100OJVALK1_GC100XXALJG_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/016> Odin v.3 engine (ID:16)..
<ID:0/016> File analysis..
<ID:0/016> SetupConnection..
<ID:0/016> Initialzation..
<ID:0/016> Get PIT for mapping..
<ID:0/016> Firmware update start..
<ID:0/016> system.img
<ID:0/016> NAND Write Start!!
<ID:0/016> boot.img
<ID:0/016> cache.img
<ID:0/016> hidden.img
<ID:0/016> recovery.img
<ID:0/016> modem.bin
<ID:0/016>
<ID:0/016> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
However if i flash with GC100XXALJF_GC100OXAALJF_GC100XXALJG_HOME.tar it is successful but after rebooting, its stuck in download mode,
here from Odin;
Code:
<ID:0/016> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GC100XXALJF_GC100OXAALJF_GC100XXALJG_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/016> Odin v.3 engine (ID:16)..
<ID:0/016> File analysis..
<ID:0/016> SetupConnection..
<ID:0/016> Initialzation..
<ID:0/016> Get PIT for mapping..
<ID:0/016> Firmware update start..
<ID:0/016> boot.img
<ID:0/016> NAND Write Start!!
<ID:0/016> cache.img
<ID:0/016> hidden.img
<ID:0/016> modem.bin
<ID:0/016> recovery.img
<ID:0/016> system.img
<ID:0/016> RQT_CLOSE !!
<ID:0/016> RES OK !!
<ID:0/016> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/016> Removed!!
<ID:0/016> Added!!
When i boot into download mode/recovery mode myself i'm presented with;
"Odin Mode"
Product Name: EK-GC100_EUR_XX
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Custom
Click to expand...
Click to collapse
This might help (again, this is why my thread should be a sticky) http://forum.xda-developers.com/showthread.php?t=2086636
Flash the firmware that fails on modem.
Let it fail. Turn off and boot into download mode again.
Then root the camera via odin with the root method Adam gave us.
That flash should go all the way 100%
After this, the camera should work again.
Try it, let us know if it helped.
robb13 said:
This might help (again, this is why my thread should be a sticky) http://forum.xda-developers.com/showthread.php?t=2086636
Flash the firmware that fails on modem.
Let it fail. Turn off and boot into download mode again.
Then root the camera via odin with the root method Adam gave us.
That flash should go all the way 100%
After this, the camera should work again.
Try it, let us know if it helped.
Click to expand...
Click to collapse
Thanks Robb, i've given it a try but it reboots back into Download Mode again
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GC100XXALK6_GC100OJVALK1_GC100XXALJG_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/016> Odin v.3 engine (ID:16)..
<ID:0/016> File analysis..
<ID:0/016> SetupConnection..
<ID:0/016> Initialzation..
<ID:0/016> Get PIT for mapping..
<ID:0/016> Firmware update start..
<ID:0/016> system.img
<ID:0/016> NAND Write Start!!
<ID:0/016> boot.img
<ID:0/016> cache.img
<ID:0/016> hidden.img
<ID:0/016> recovery.img
<ID:0/016> modem.bin
<ID:0/016>
<ID:0/016> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/016> Removed!!
<ID:0/016> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-gd1-gd1xx-ekgc100.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/016> Odin v.3 engine (ID:16)..
<ID:0/016> File analysis..
<ID:0/016> SetupConnection..
<ID:0/016> Initialzation..
<ID:0/016> Get PIT for mapping..
<ID:0/016> Firmware update start..
<ID:0/016> recovery.img
<ID:0/016> NAND Write Start!!
<ID:0/016> cache.img
<ID:0/016> RQT_CLOSE !!
<ID:0/016> RES OK !!
<ID:0/016> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/016> Removed!!
<ID:0/016> Added!!
I even did a further step of removing modem.bin from the failed tar and repackaging it and reflashing, still returns back to downloading mode.
I do however now have Custom Binary Download: Yes
Downloading Adam's suggested JellyBean 4.1.1 build:GC100XXALK1 and will see if that works for me.
Have you tried getting into recovery?
Sent from my GT-N7100 using Tapatalk 2
RavenY2K3 said:
Have you tried getting into recovery?
Sent from my GT-N7100 using Tapatalk 2
Click to expand...
Click to collapse
I wish i could enter recovery but it no longer works, it takes me straight into downloading mode (even when using the Recovery mode combo when turning the camera on). This download mode is slightly different from the Download Mode launched with the combination, it only shows the Android Avatar + Downloading.... do not turn off target !!. (No odin, no flash counters, etc)
kartoffelpower said:
I wish i could enter recovery but it no longer works, it takes me straight into downloading mode (even when using the Recovery mode combo when turning the camera on). This download mode is slightly different from the Download Mode launched with the combination, it only shows the Android Avatar + Downloading.... do not turn off target !!. (No odin, no flash counters, etc)
Click to expand...
Click to collapse
What about trying to reflash just the recovery alone, stock that is and see if it kicks it into booting into it, to try a wipe perhaps, I've got the stock recovery if you want to give it a try?
Sent from my GT-N7100 using Tapatalk 2
RavenY2K3 said:
What about trying to reflash just the recovery alone, stock that is and see if it kicks it into booting into it, to try a wipe perhaps, I've got the stock recovery if you want to give it a try?
Sent from my GT-N7100 using Tapatalk 2
Click to expand...
Click to collapse
I tried the stock recovery recovery-stock-bll7-EKGC100 without any luck. Now after recent reflashing the camera boots to a white screen rather than downloading mode.I can still boot to download mode with the combination, the flashing counter has been reset but now also i can't flash ANYTHING onto it, got some new nifty error
Code:
<ID:0/017> Added!!
<ID:0/017> Odin v.3 engine (ID:17)..
<ID:0/017> File analysis..
<ID:0/017> SetupConnection..
<ID:0/017> Initialzation..
<ID:0/017> Get PIT for mapping..
<ID:0/017>
<ID:0/017> There is no PIT partition.
I tried using the PIT file from Adam over at thispost but it throws me
Code:
<ID:0/017> Odin v.3 engine (ID:17)..
<ID:0/017> File analysis..
<ID:0/017> SetupConnection..
<ID:0/017> Initialzation..
<ID:0/017> Set PIT file..
<ID:0/017> DO NOT TURN OFF TARGET!!
<ID:0/017>
<ID:0/017> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Having some fun with this device, will return it after the weekend if nothing works out, happy to any suggestions though
Thanks to everyone for the help so far
Sounds completely FUBAR, how did you clear the counter or did it do on it's own/by accident? haha.
Sent from my GT-N7100 using Tapatalk 2
RavenY2K3 said:
Sounds completely FUBAR, how did you clear the counter or did it do on it's own/by accident? haha.
Sent from my GT-N7100 using Tapatalk 2
Click to expand...
Click to collapse
Yeah, now that i can't flash roms at all withotu a valid PIT this camera has definitely reached its point where I will be turning it in to the Service center after the weekend.
The Counter Reset itself, i'm guessing once the partitions disappeared it took the count with it too ;-P
kartoffelpower said:
The Counter Reset itself, i'm guessing once the partitions disappeared it took the count with it too ;-P
Click to expand...
Click to collapse
Well..... Every cloud and all that haha
Sent from my GT-P7500 using Tapatalk HD
My GC2 EK-GC200 has same issue
I cant flash any firmware on my GC2, odin alway failed on system.img ... Please give me PIT file of Samsung EK-GC200
Hello,
Just flashed my GT-I9070 according to the how-to of qzem with the recommended settings.
This worked out once, then I was trying another firmware, this didn't work out (phone was hanging at the Samsung GT-I9070 start-screen), so I thought: "OK, lets do the other firmware again".
So entered the download mode and tried to flash the "old" firmware again (XXLD1.tar) but it just does something very fast (not really installing) and reboots again with hanging at the start screen.
OK, so lets got to the "recovery-mode"... not possible!
Did this now a few times, but everytime the same result, just a quick full download bar and restarting with hanging.
Did I kill my phone? :crying:
ODIN look also fine...
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> xxld1.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> kernel.bin.md5
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/005> Removed!!
PLEASE HELP ME!!!
Thanks so much
Thomas
UPDATE:
After installing a stock ROM everything worked fine again, also recovery mode.
BUT on installing the rrotkernel.tar of qzem it again hangs at the start-screen.
So problem is reduced on that step.
So how to unlock my phone without that rootkernel???
I was also struggling with qzem's method, didn't brick it but I couldn't root it. Would be nice if someone could clarify this, I'm curious.
So I ended up with a pre-rooted firmware from diego's thread. Many links are down but since you're voiding your warranty
by rooting then what's the point in having a firmware for your country? Just keep in mind that pre-rooted should match the base one, if you're gonna do this.
tommym74 said:
Hello,
Just flashed my GT-I9070 according to the how-to of qzem with the recommended settings.
This worked out once, then I was trying another firmware, this didn't work out (phone was hanging at the Samsung GT-I9070 start-screen), so I thought: "OK, lets do the other firmware again".
So entered the download mode and tried to flash the "old" firmware again (XXLD1.tar) but it just does something very fast (not really installing) and reboots again with hanging at the start screen.
OK, so lets got to the "recovery-mode"... not possible!
Did this now a few times, but everytime the same result, just a quick full download bar and restarting with hanging.
Did I kill my phone? :crying:
ODIN look also fine...
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> xxld1.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> kernel.bin.md5
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/005> Removed!!
PLEASE HELP ME!!!
Thanks so much
Thomas
UPDATE:
After installing a stock ROM everything worked fine again, also recovery mode.
BUT on installing the rrotkernel.tar of qzem it again hangs at the start-screen.
So problem is reduced on that step.
So how to unlock my phone without that rootkernel???
Click to expand...
Click to collapse
Try flashing JB Roms , rooting JB is easy , download root.zip by Shaan and just flash it through recovery and u ve a rooted phone now..
Link is http://forum.xda-developers.com/showthread.php?t=2087424
Hi all. Well, i have a Samsung Galaxy S3 mini (i8200), wich it was given to me to fix it.
I want to clarify that i don't know how did the phone came into this state, i mean, i don't know if the user tried to flash a new rom or what, the thing is that the phone, right now, when i turn ON, it gets stuck on Samsung logo.
I can only enter the download mode.
I can't enter Recovery mode
I've tryed so many things. I've tryed to flash the stock rom (downloaded from Sammobile) with ODIN, but it always shows this error:
<ID:0/026> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I8200XXUAOA2_I8200OXAAOA2_I8200XXUAOA2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/026> Odin v.3 engine (ID:26)..
<ID:0/026> File analysis..
<ID:0/026> SetupConnection..
<ID:0/026> Initialzation..
<ID:0/026> Get PIT for mapping..
<ID:0/026> Firmware update start..
<ID:0/026> timh.bin
<ID:0/026> NAND Write Start!!
<ID:0/026> obm.bin
<ID:0/026> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
(I've tryed with differents Odin versions, 3.04, 3.07 , 3.09 , also with different USB ports, and a different PC)
I add a quote i read:
The Problem: Sometimes when you flash a ROM (TouchWiz or AOSP), there is a risk of the /system and /data partitions not wiping correctly thus leading them to be formatted with R/O permissions rather than R/W. This makes it impossible for the phone to boot up because no data can be written. Not even a typical ODIN flash back to stock or rooted stock will fix this. Using CWM to flash another ROM will yield the same no boot results. Furthermore, the stock recovery will not work and it becomes impossible to perform a factory reset. Sound frustrating? It is.
So, i read also, that a pit file its supposed to fix my issue ( this rewrites the PIT tables with the proper permissions).
I get the pit file, and i tried... the results:
<ID:0/026> Added!!
<ID:0/026> Removed!!
<ID:0/026> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I8200XXUAOA2_I8200OXAAOA2_I8200XXUAOA2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/026> Odin v.3 engine (ID:26)..
<ID:0/026> File analysis..
<ID:0/026> SetupConnection..
<ID:0/026> Initialzation..
<ID:0/026> Set PIT file..
<ID:0/026> DO NOT TURN OFF TARGET!!
<ID:0/026> Get PIT for mapping..
<ID:0/026> Firmware update start..
<ID:0/026> timh.bin
<ID:0/026> NAND Write Start!!
<ID:0/026> obm.bin
<ID:0/026> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
So, why i keep trying and keep giving an opportunity to this phone?, if im correct, its not a hard brick because i still can enter the Download mode, and in PRODUCT NAME, it still saying GT-I8200 , so, i still have hope.
Im looking for some help, i need help to fix this, im sure im missing something. What can i do?
Thanks in advance.
i have a problem
Sasaoy said:
Hi all. Well, i have a Samsung Galaxy S3 mini (i8200), wich it was given to me to fix it.
I want to clarify that i don't know how did the phone came into this state, i mean, i don't know if the user tried to flash a new rom or what, the thing is that the phone, right now, when i turn ON, it gets stuck on Samsung logo.
I can only enter the download mode.
I can't enter Recovery mode
I've tryed so many things. I've tryed to flash the stock rom (downloaded from Sammobile) with ODIN, but it always shows this error:
<ID:0/026> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I8200XXUAOA2_I8200OXAAOA2_I8200XXUAOA2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/026> Odin v.3 engine (ID:26)..
<ID:0/026> File analysis..
<ID:0/026> SetupConnection..
<ID:0/026> Initialzation..
<ID:0/026> Get PIT for mapping..
<ID:0/026> Firmware update start..
<ID:0/026> timh.bin
<ID:0/026> NAND Write Start!!
<ID:0/026> obm.bin
<ID:0/026> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
(I've tryed with differents Odin versions, 3.04, 3.07 , 3.09 , also with different USB ports, and a different PC)
I add a quote i read:
The Problem: Sometimes when you flash a ROM (TouchWiz or AOSP), there is a risk of the /system and /data partitions not wiping correctly thus leading them to be formatted with R/O permissions rather than R/W. This makes it impossible for the phone to boot up because no data can be written. Not even a typical ODIN flash back to stock or rooted stock will fix this. Using CWM to flash another ROM will yield the same no boot results. Furthermore, the stock recovery will not work and it becomes impossible to perform a factory reset. Sound frustrating? It is.
So, i read also, that a pit file its supposed to fix my issue ( this rewrites the PIT tables with the proper permissions).
I get the pit file, and i tried... the results:
<ID:0/026> Added!!
<ID:0/026> Removed!!
<ID:0/026> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I8200XXUAOA2_I8200OXAAOA2_I8200XXUAOA2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/026> Odin v.3 engine (ID:26)..
<ID:0/026> File analysis..
<ID:0/026> SetupConnection..
<ID:0/026> Initialzation..
<ID:0/026> Set PIT file..
<ID:0/026> DO NOT TURN OFF TARGET!!
<ID:0/026> Get PIT for mapping..
<ID:0/026> Firmware update start..
<ID:0/026> timh.bin
<ID:0/026> NAND Write Start!!
<ID:0/026> obm.bin
<ID:0/026> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
So, why i keep trying and keep giving an opportunity to this phone?, if im correct, its not a hard brick because i still can enter the Download mode, and in PRODUCT NAME, it still saying GT-I8200 , so, i still have hope.
Im looking for some help, i need help to fix this, im sure im missing something. What can i do?
Thanks in advance.
Click to expand...
Click to collapse
I have the same problem.
I installed several ROM. Finally, I wanted to go back to the Stock ROM and I could not. Error in the memory. Odin stops in the middle of the wash and the phone oběvují different red numbers. He gets into Download Mode, but it does not install it. or I do not get Recavery. I found a tutorial on repairing large S3, but I need my stuff on S3 Mini (GT-I8190). If someone finds something, or would even help it would have been nice. Thank you.
http://forum.xda-developers.com/galaxy-s3/general/samsung-s3-i9300-note2-n7100-i9500-s4-t2647558
Hello,
I had the exact same problem,
messed with R W permissions,
So you should try Heimdall,
I managed to read my PIT file, so it is somehow alive,
but could'nt write a new PIT file on the phone,
I stopped searching and ended buying an old (but working) motherboard for my phone.
But you should really continue, and give it a try.
I need urgent help, I was using TWRP manager and tried to install that over the clockword mod recovery, now the phone is n a booting into recovery loop and wont boot at all.
I was using resurrection remix as a custom rom and that was 6.0.1. Is there anyway I can go back to 5.1.1 stock? I get SW REV Check Failed:Fused 2>Binary 1
Want to help
darksarken said:
I need urgent help, I was using TWRP manager and tried to install that over the clockword mod recovery, now the phone is n a booting into recovery loop and wont boot at all.
Click to expand...
Click to collapse
If you remember what version of android were you on?
Can you boot into download mode?
If you can answer those 2 questions then my best guess is you can ODIN back to stock with out an issue.
Just download ODIN 3.09 from some where shouldn't be to hard to find.
and download the top link from here: http://forum.xda-developers.com/note-4-tmobile/development/mirror-stock-tw-t3260858
unzip the samsung firmware(only once), put your phone in download mode, plug it into your computer, open odin, click "AP" and find the file that you just unzipped
make sure you click no boxes but "AP" and hit start and let odin do its thing.If yu have any questions Id be glad to answer
Help
BoiBundy said:
If you remember what version of android were you on?
Can you boot into download mode?
If you can answer those 2 questions then my best guess is you can ODIN back to stock with out an issue.
Just download ODIN 3.09 from some where shouldn't be to hard to find.
and download the top link from here: http://forum.xda-developers.com/note-4-tmobile/development/mirror-stock-tw-t3260858
unzip the samsung firmware(only once), put your phone in download mode, plug it into your computer, open odin, click "AP" and find the file that you just unzipped
make sure you click no boxes but "AP" and hit start and let odin do its thing.If yu have any questions Id be glad to answer
Click to expand...
Click to collapse
Okay after this passed my phone is still rebooting in a loop for some reason? Do you know why?
darksarken said:
Okay after this passed my phone is still rebooting in a loop for some reason? Do you know why?
Click to expand...
Click to collapse
Factory reset from recovery should fix it.
Sent from my SM-N910T using XDA Free mobile app
darksarken said:
Okay after this passed my phone is still rebooting in a loop for some reason? Do you know why?
Click to expand...
Click to collapse
Raptor is right, pull your battery for about 20 seconds replace it and hold volume+up and home while powering on. And you should be presented with a dead android. From there I believe you factory reset your phone.
Sorry, in literally always busy but here is the exact step by step method of resetting from recovery:
Turn off the phone. If the phone will not turn off, remove and re-insert the battery.
Press and hold the following three buttons at the same time:
Volume Up key
Home key
Power key.
When the phone vibrates, release the Power key.
When the Android System Recovery screen appears, release all keys.
Press the Volume down key several times key to highlight 'wipe data / factory reset.'
Press Power button to select.
Press the Volume down key until 'Yes -- delete all user data' is highlighted.
Press Power button to select and start the master reset.
When the master reset is complete, 'Reboot system now' is highlighted.
Press the Power key to restart the device
I'm actually having the same issue, but seems more complicated.
I was using resurrectionremix, and bluetooth/lte wasn't working so well so I decided to factory reset it and install the stock factory image.
But when I try to flash using Odin (3.07, 3.09 tried both) it gives me this error.
<ID:0/015> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910TUVU1ANK4_N910TTMB1ANK4_N910TUVU1ANK4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Get PIT for mapping..
<ID:0/015> Firmware update start..
<ID:0/015> SingleDownload.
<ID:0/015> aboot.mbn
<ID:0/015> NAND Write Start!!
<ID:0/015> sbl1.mbn
<ID:0/015> rpm.mbn
<ID:0/015> FAIL! (Auth)
<ID:0/015>
<ID:0/015> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And on the phone
UDC START
SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1
[1]eMMC write fail : ABOOT
And teh firmwares I tried are
NIH, NK4, COD
MTP Isn't working, the phone isn't recognizing my microSD card either so there's no way for me to flash anything through zip TWRP.
Can somebody help me out? Thanks
Stiria said:
I'm actually having the same issue, but seems more complicated.
I was using resurrectionremix, and bluetooth/lte wasn't working so well so I decided to factory reset it and install the stock factory image.
But when I try to flash using Odin (3.07, 3.09 tried both) it gives me this error.
<ID:0/015> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910TUVU1ANK4_N910TTMB1ANK4_N910TUVU1ANK4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Get PIT for mapping..
<ID:0/015> Firmware update start..
<ID:0/015> SingleDownload.
<ID:0/015> aboot.mbn
<ID:0/015> NAND Write Start!!
<ID:0/015> sbl1.mbn
<ID:0/015> rpm.mbn
<ID:0/015> FAIL! (Auth)
<ID:0/015>
<ID:0/015> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And on the phone
UDC START
SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1
[1]eMMC write fail : ABOOT
And teh firmwares I tried are
NIH, NK4, COD
MTP Isn't working, the phone isn't recognizing my microSD card either so there's no way for me to flash anything through zip TWRP.
Can somebody help me out? Thanks
Click to expand...
Click to collapse
By chance are you already on 5.1.1 firmware, if you are you can't downgrade back to those lower fws and the stock factory Odin is dok2. Try that 1 instead.
Sent from my SM-N920T using Tapatalk