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,
so i read the PSA and all the other info about bricking/ what not to load etc and took the plunge to update my kernel
Using odin, i flash the safe kernel DAFUQ_N7000_05272012.tar and everything went well and rebooted. Well this is where i'm stuck now
Reboots, i get the samsung screen with the yellow triangle now but that's it. nothing after that.
Read abit more and grab this kernel cm9_safe_kernel.tar and flash this. same thing.
I cannot get into recovery but i can get into download mode.
I read a few things about looking at repartitioning but as i didn't do a full wipe nor did a flash any roms, i don't think that is my issue.
Any suggestions?
flash a full GB firmware with ODIN and you should be fine
Once done, Root and use Triangle Away app to reset counter and remove the triangle
denti said:
Hi all,
so i read the PSA and all the other info about bricking/ what not to load etc and took the plunge to update my kernel
Using odin, i flash the safe kernel DAFUQ_N7000_05272012.tar and everything went well and rebooted. Well this is where i'm stuck now
Reboots, i get the samsung screen with the yellow triangle now but that's it. nothing after that.
Read abit more and grab this kernel cm9_safe_kernel.tar and flash this. same thing.
I cannot get into recovery but i can get into download mode.
I read a few things about looking at repartitioning but as i didn't do a full wipe nor did a flash any roms, i don't think that is my issue.
Any suggestions?
Click to expand...
Click to collapse
Try flash gb rom. http://androidadvices.com/update-galaxy-note-n7000-gingerbread-xxlc1-236-firmware/
Moved To Q&A
Please post all questions in the Q&A section
azzledazzle said:
flash a full GB firmware with ODIN and you should be fine
Once done, Root and use Triangle Away app to reset counter and remove the triangle
Click to expand...
Click to collapse
Do this....
thanks for the replies but wee confused...
isnt' DAFUQ_N7000_05272012.tar a GB firmware?
also isn't the CM9_safe_kernel.tar a GM firmware to use?
might you be able to suggest a firmware?
without going into much detail, what's the differences between the DAFUQ, CM9_safe firmware vs the GB firmware?
take care
denti said:
thanks for the replies but wee confused...
isnt' DAFUQ_N7000_05272012.tar a GB firmware?
also isn't the CM9_safe_kernel.tar a GM firmware to use?
might you be able to suggest a firmware?
without going into much detail, what's the differences between the DAFUQ, CM9_safe firmware vs the GB firmware?
take care
Click to expand...
Click to collapse
Flash Full GB STOCK ROM via PC ODIN and start again...
Also sounds a little bit like you were on ICS an have flashed a GB Kernel and rebooted....
denti said:
thanks for the replies but wee confused...
isnt' DAFUQ_N7000_05272012.tar a GB firmware?
also isn't the CM9_safe_kernel.tar a GM firmware to use?
might you be able to suggest a firmware?
without going into much detail, what's the differences between the DAFUQ, CM9_safe firmware vs the GB firmware?
take care
Click to expand...
Click to collapse
Its a kernel only.. Download full GB rom here.
http://forum.xda-developers.com/showthread.php?t=1424997
Sent from my GT-N7000 using XDA Premium App
Ok, so i downloaded N7000XXLC1_N7000OXALC1_N7000XXLB2_HOME.tar.md5 and tried to flash via odin and it failed
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLC1_N7000OXALC1_N7000XXLB2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> factoryfs.img
<ID:0/006> NAND Write Start!!
<ID:0/006> zImage
<ID:0/006> hidden.img
<ID:0/006> modem.bin
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
is the log.
any suggestions? I got firmware DAFUQ_N7000_05272012.tar
thank you
denti said:
Ok, so i downloaded N7000XXLC1_N7000OXALC1_N7000XXLB2_HOME.tar.md5 and tried to flash via odin and it failed
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLC1_N7000OXALC1_N7000XXLB2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> factoryfs.img
<ID:0/006> NAND Write Start!!
<ID:0/006> zImage
<ID:0/006> hidden.img
<ID:0/006> modem.bin
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
is the log.
any suggestions? I got firmware DAFUQ_N7000_05272012.tar
thank you
Click to expand...
Click to collapse
Read this carefully and understand. Is your device 16 gig? If yes. http://nguyenkieuhung1984.blogspot.com/2012/01/how-to-installflash-samsung-galaxy-note_09.html?m=1
Read 3C
azzledazzle said:
flash a full GB firmware with ODIN and you should be fine
Once done, Root and use Triangle Away app to reset counter and remove the triangle
Click to expand...
Click to collapse
Triangle away won't work on GB roms.
Try to reflash CF kernal using PC odin..
Fix it?
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?
I have searched for about the past 3-4 hours which is a lot longer than it usually takes for me to get to the bottom of these dang things. My phone (Galaxy S5 G900A Lollipop 5.0) has been really screwy on the WiFi lately (home, out in public, family members homes) so I decided (after a factory reset, safe mode, etc failing) to go ahead and try to downgrade my phone. So I went online and found out you can do it with Odin (3.09, 3.10, 3.06) and attempted it. I downloaded a stock 4.4.4 firmware and went to work. Immediately it failed with the error I am still getting which is the following:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_G900AUCU1ANCE_964333_REV00_user_low_ship_MULTI_CERT.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> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<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
Example of the firmware update screen: Unable to post outside link, just google "firmware update encountered an issue galaxt s5" it's the first image.
Example of the download screen I use with Odin (as instructed): Unable to post outside link, just google "download mode glaaxy s5" it's the first image.
I have attempted using both the old and new version of Kies to perform the emergency and normal firmware update procedures. My phone does not show in the emergency firmware recovery screen and the firmware update mode ends in an error telling me to use the emergency firmware update, which as mentioned does not work.
With Odin I have attempted: Multiple computers, multiple USB ports on each computer, reinstalling Samsung drivers, restarting computer, multiple Odin versions, multiple firmware files (4.4.4, 4.4.2), running as administrator
Windows 8.1
Update on errors: My screen shows the following error on my phone in RED under "UDC Start" when Odin Fails:
SYS REV CHECK FAIL : Refer 2 > Binary 1
SECURE CHECK FAIL : system
You can't downgrade from 5.0. Flash 5.0 and you will be fine. If I'm not mistaken, the new bootloader is not backwards compatible and therefore won't let a downgrade happen.
Took to Best Buy, flashed and resolved in less than 10 minutes at Samsung center.
daddynexxus said:
Took to Best Buy, flashed and resolved in less than 10 minutes at Samsung center.
Click to expand...
Click to collapse
You won't be able to downgrade and that was your problem in the beginning
Same issue
I have having the same issue, I tried flashing Odin 4.4 back to the S5 once it has 5.0. It now errors out in Odin and in Kies, I really dont know what to do. Error: SW Rev Check Fail : Aboot Fused 3 > Binary
Rayman3030 said:
I have having the same issue, I tried flashing Odin 4.4 back to the S5 once it has 5.0. It now errors out in Odin and in Kies, I really dont know what to do. Error: SW Rev Check Fail : Aboot Fused 3 > Binary
Click to expand...
Click to collapse
Go here and follow direction. Do the last section of the OP.
http://forum.xda-developers.com/showthread.php?p=60012961
Sent from my SAMSUNG-SM-G900A
For the past couple of days I've been unable to unroot my device using Odin, which I have done many of times on the past. I went to Sammobile and got the latest firmware to flash back to stock, but everytime I attempt to do so the process Fails. USB Debugging is enabled so I don't have a clue what the problem could be. I will list some general information as well as the results of the Odin process below:
Baseband Version: N910TUVUD0K2
Odin process result:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910T3UVU1DOK2_N910T3TMB1DOK2_N910T3UVU1DOK2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks
Updated: I've stumbled across a thread here on XDA which has a mirror link to Stock TW Firmware/Bootloader/Modem N910TUVU2DOK2, and after flashing this mirror link using Odin... my phone now is unrooted and back to stock. Many thanks to ShrekOpher for posting the mirror link and here is a link to his post: http://forum.xda-developers.com/note-4-tmobile/development/mirror-stock-tw-t3260858
Same issue
I just posted about this same issue a couple of days ago, if you go to my only post ive done so far you can see how we are in the same boat. What were you using before you got to your problem, which custom ROM?
I had this problem on the note edge. What helped me was flashing cwm recovery and wiping everything
Trebor313 said:
For the past couple of days I've been unable to unroot my device using Odin, which I have done many of times on the past. I went to Sammobile and got the latest firmware to flash back to stock, but everytime I attempt to do so the process Fails. USB Debugging is enabled so I don't have a clue what the problem could be. I will list some general information as well as the results of the Odin process below:
Baseband Version: N910TUVUD0K2
Odin process result:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910T3UVU1DOK2_N910T3TMB1DOK2_N910T3UVU1DOK2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks
Click to expand...
Click to collapse
make sure u didn't check in settings the reactivation lock,
use twrp, wipe everything except sdcard... then boot into downloader mode, and it should work, I do know the reactivation lock should be the only thing to stop you.
hope that helps...
Catfish197621 said:
I just posted about this same issue a couple of days ago, if you go to my only post ive done so far you can see how we are in the same boat. What were you using before you got to your problem, which custom ROM?
Click to expand...
Click to collapse
I'm currently using [DOK2] TEKXodus HYBRID N4 URv7
mdiaz33685 said:
make sure u didn't check in settings the reactivation lock,
use twrp, wipe everything except sdcard... then boot into downloader mode, and it should work, I do know the reactivation lock should be the only thing to stop you.
hope that helps...
Click to expand...
Click to collapse
I check and made sure that the reactivation lock was disabled, but it still didn't work. I guess I will keep an eye open to see if this issue can get resolved sometime in the near future
mdiaz33685 said:
make sure u didn't check in settings the reactivation lock,
use twrp, wipe everything except sdcard... then boot into downloader mode, and it should work, I do know the reactivation lock should be the only thing to stop you.
hope that helps...
Click to expand...
Click to collapse
What are the odin settings for doing this install? I can't get it to recognize the file
Nevermind, quick google showed i should extract the file which im not used to doing for roms and use "AP"
waywardfrantz said:
What are the odin settings for doing this install? I can't get it to recognize the file
Nevermind, quick google showed i should extract the file which im not used to doing for roms and use "AP"
Click to expand...
Click to collapse
U have to unziip the firmware and in Odin u need to goto AP and point to the firmware... sometimes i have to remove the extention .md5 after u unzip the firmware depending on which Odin u use...
make sure u have the samsung drivers installed..
mdiaz33685 said:
U have to unziip the firmware and in Odin u need to goto AP and point to the firmware... sometimes i have to remove the extention .md5 after u unzip the firmware depending on which Odin u use...
make sure u have the samsung drivers installed..
Click to expand...
Click to collapse
I can't Odin to stock unless I change the name of the firmware file to .tar. it skips the md5 check I believe.
---------- Post added at 06:17 PM ---------- Previous post was at 06:14 PM ----------
Also go to supersu and do a full unroot before. I'm thinking maybe the supersu backup script could cause issues too