Database Develop

Samsung Galaxy S i9000 E: unknown volume for path

Hello everyone,
I have a major problem that all started with bootlooping. I was about to recover my phone in CWM in several ways and suddenly one of the times I went back in CWM, my phone couldn't read, mount or open any file on its storage. Nor internal or external memory, nothing. I have been troubleshooting for two days now and still no luck. I have restored kernels, flashed stock rom with/without pit files (.512) and again - still no luck.
Does ANYONE have a clear answer for this problem? I will be very grateful for any tries or suggestions and I hope it will help people in the future aswell.

do you have or had something like E: Can't mount /dev/block/stl10 (invalid Argument) ??
good luck, and start from using a search button here

Sorry, no, only the can't mount/open and unkown volume.
That's also a weird thing that there are "uncomplete" tutorials to get rid of /dev/block and no tutorials at all to get rid of the problem that I (and probably a lot of other people) have. Thanks for you suggestion though, it's highly appreciated.
Does anyone else have any ideas?

ODIN + repartition
If you can go into "Download mode" using the keys combo and ODIN recognizes the device, I think that you should try flashing a stock rom with using the pit file and the "re-partition" option.

As mentioned in post above you need to flash a stock rom. I had this issue after trying to restore my stock backup straight from CM7. They use different file systems hence the issue (I think). Anyway I used odin with re-partition checked using all four files (pit, csc etc) Worked perfectly although I had to first flash the four files with re-partition and then flash a second time without checking re-partion and using only the three files (did not use pit file on second flash) after this everything ok - flashed cf-root & now team icssgs 4.2 with no major issues

Ok but I tried to flash the PDA& .512 pit file with re-partition on but it gets stuck. Though I haven't tried with modem and CSC along. Could you guys help me with finding these files altogether? I am not so experienced with ODIN

you need all files. pit file, pda, modem & csc. I also found that although a lot of people recommended Odin 1.3 (?? not sure) I found this got stuck & I used 1.85(??not sure but I think 1.85) with no issues.

K I found something here, I'm going to try it now. Will update you with news afterwards

Problem solved.
Link to thread: http://forum.xda-developers.com/showthread.php?t=1195335
My log from odin:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9000XXJVR_CL425308_REV03_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9000XXJVR_REV_00_CL1044379.tar.md5 is valid.
<OSM> CODE_I9000XXJVR_CL425308_REV03_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.bin
<ID:0/003> Sbl.bin
<ID:0/003> param.lfs
<ID:0/003> factoryfs.rfs
<ID:0/003> dbdata.rfs
<ID:0/003> cache.rfs
<ID:0/003> zImage
<ID:0/003> modem.bin
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response form LOKE
<ID:0/003> boot.bin
<ID:0/003> Sbl.bin
<ID:0/003> param.lfs
<ID:0/003> factoryfs.rfs
<ID:0/003> dbdata.rfs
<ID:0/003> cache.rfs
<ID:0/003> zImage
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
Scubadude, I personally thank you for your time and support. It was highly appreciated in every way, you certainly deserve a click on the "Thanks button"
If anyone needs help with the link (If it disappears or something) from the linked thread, PM me and Ill upload it for you
Cheers

Personally, I'd recommend you use the last 2.3.6, Ramad's deodexed version

[Q] I kill my galaxy tab gt-p1000,need help

I receive new firmware over Samsung Kies application,and i accidently pull of cable in the middle of flashing.Now my tab is dark.It wont boot or power on.I I searched the forum and find some answers but still i did not find soluitions for my problem. Odin application see my tab on port 0:[COM9] , and i try to flash with different roms but everything i got is this :<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P1000XWJQ8_P1000XXJPZ_P1000DBTJQ1_HOME.tar.md5 is valid.
<OSM> P1000XWJQ8_P1000XXJPZ_P1000DBTJQ1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
Then i wait,and wait, nothing happers for hours...
If anyone has tip what to do,I would be very grateful. Tab FCC ID :A3LGTP1000
Thanks in advance!

Try overcome Stock Save v5 method.
There is a long thread in section for Overcome 4.1 ROM.
or head to
http://www.teamovercome.net
follow their guide but you can stop after flashing the Stock Safe from Odin.
Or if you want, you can continue and end up with Overcome custom ROM which is excellent.
The guide has broken image, but follow this link and you will get the cached image copy:
http://forum.xda-developers.com/showthread.php?p=20974872

Thank you very much!!!

Make sure you enter Download Mode (volume+power buttons).
Once you do that, make sure your tab is detected in the COM port of Odin. It should be marked in yellow. Also make sure you use Odin 1.7 (this version works best for the tab!).
The behavior you describe suggests Odin cannot connect to your Tab in download mode!
If all of the above are in order, use the Overcome giude as priyana suggested, it should work fine. And be careful what you flash! Odin is not a toy...
Peace,
C.

Thanks for advice Cheatman,but i can't power on my tab. I can't get downlad mode.But when i connect tab to pc odin recognizes it some port 0:[COM9]
.Should I continue with flashing by the Overcome giude? I can certainly try my tab is dark anyway.

problem solved
"It's Alive!!!!!!!!!!!!!!!!!!!" Thank you very much!!!!! You make me happy !!!
Many thanks to priyana and cheatman!!!!
All the best!!!!

Thank you so very much !
priyana said:
Try overcome Stock Save v5 method.
There is a long thread in section for Overcome 4.1 ROM.
or head to
http://www.teamovercome.net
follow their guide but you can stop after flashing the Stock Safe from Odin.
Or if you want, you can continue and end up with Overcome custom ROM which is excellent.
The guide has broken image, but follow this link and you will get the cached image copy:
http://forum.xda-developers.com/showthread.php?p=20974872
Click to expand...
Click to collapse
Thank you so very much for the " overcome " link - I accidently soft bricked my GT-P1000 and after days of searching the web for a solution I found this post .... and I've just finished downloading and installing - and YES my TAB is alive again !!!!!!

hello,
i have a problem with my gt p1000 - i tried flashing new overcome 4 kernel with odin and heimdall and it did not work.
now the tab cant boot anymore, it only shows a mobile, an exklamation mark and a pc.
i tried flashing kernel with odin 1.85 and odin 1.7; device is being detected (yellow COM display) and all i recieve is the following message:
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> zImage
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
anyone has a clue? help would be appreciated!
edit: oh well thanks i already figured it out by myself

sruf said:
hello,
i have a problem with my gt p1000 - i tried flashing new overcome 4 kernel with odin and heimdall and it did not work.
now the tab cant boot anymore, it only shows a mobile, an exklamation mark and a pc.
i tried flashing kernel with odin 1.85 and odin 1.7; device is being detected (yellow COM display) and all i recieve is the following message:
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> zImage
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
anyone has a clue? help would be appreciated!
edit: oh well thanks i already figured it out by myself
Click to expand...
Click to collapse
Can you explain how you did it?
I have the same problem with less messages:
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)

I am having issues with galaxy tab p1000. Currently stock on a phone PC logo. Have tried Odin 3 but it stops at all trend succeed 0 failed 1

Added!!
Odin v.3
File analysis..
SetupConnection..
All threads completed. (succeed 0 / failed 1)

[PROBLEM SOLVED]Odin keep failed

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

Bootloop, no Recovery possible S3 Mini GT-I8190N NFC

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?

Need Help, I may have bricked my SM-T900

Hi,
I got myself a Samsung Galaxy SM-T900.
it originally would boot up into GREY battery icon and then apparently switch off although I could see the backlight was dimly on.
( So may have battery or USB charging port problems as well)
It was reporting a custom rom state so I thought I would put it back to stock and actually managed to flash it with Odin 3.10 ( which worked i.e. reported GREEN)
Rom file is T900XXSBPL3_T900OXABOH4_HOME.tar.md5 from Sam Mobile.
Although I got a GREEN light from Odin.... on tablet boot up, the tablet reported " Firmware upgrade encountered an issue...……….in Kies and try again"
Kies (2.6) would not connect to the tablet, nor could I do an emergency firmware recovery as no device comes up in the device list.
So I decided to reflash the stock rom with Odin 3.10 which was a bad move. For some unknown reason it stopped flashing at about halfway.
So I restarted the flash and now always get stuck on
<ID:0/013> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T900XXSBPL3_T900OXABOH4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/013> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/013> sboot.bin
<ID:0/013> NAND Write Start!!
<ID:0/013> FAIL!
<ID:0/013>
<ID:0/013> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Could someone please help... I am a casual ROM updater and just follow instructions , but now I am completely stuck.
Thanks

Hi,
Could someone please point me to the PIT file for this SM-T900 UK ROM i.e. BTU
T900XXSBPL3_T900OXABOH4_HOME.tar.md5 from SamMobile for SM-T900
I suspect its in there, but I think I may have corrupted my partitions, so need a PIT file...… I think?
Thanks