Database Develop

[Q] Root

Hello XDA,
I think I messed up my phone pretty bad. Firstly, I tried putting in CWM kernel, my device was at 2.2.? that time and it was a 2.3 kernel. Device wouldnt boot, tried installing some 2.2 kernels but that simply didn't work (with Heimdall).
I tried installing I9000XWJVH_ODKJV3_XXJVO with Odin. It managed to get to the Galaxy S video but not any futher. And this is where it starts to get strange; I ticked "Phone Bootloader update" and "Phone ESF clear" and right now it has a black screen... but all the sound is working, and I still can get into download mode.
Ive tried most things, but without succes. Does any of you have an idea?
edit: so after 10 minutes of pretending to be dead, it resurrected. I tried rebooting (the fw was 2.3.3 and kernal was something rooted) to install CWM but now it wont respond anymore?

If you can access Download mode with 3-buttons combo you can odin-flash a stock rom (JVT for example), reboot and flash a custom kernel to have root and CWM recovery.

http://forum.xda-developers.com/showthread.php?t=1134975

cabessius said:
If you can access Download mode with 3-buttons combo you can odin-flash a stock rom (JVT for example), reboot and flash a custom kernel to have root and CWM recovery.
Click to expand...
Click to collapse
Problem is that I cant acces the CWM. Well, atleast I can't see it. I tried flashing CWM on it, Heimdall said it went OK. When I boot, I get a black screen, hear the boot music and see the touchbuttons lit up. The only thing that wont respond is the screen, I can only to get it to work when I check my pit using Heimdall fronted and let that program reboot my device.
OK, the result:
<ID:0/008> 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> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> boot.bin
<ID:0/008> NAND Write Start!!
<ID:0/008> Sbl.bin
<ID:0/008> param.lfs
<ID:0/008> factoryfs.rfs
<ID:0/008> dbdata.rfs
<ID:0/008> cache.rfs
<ID:0/008> zImage
<ID:0/008> modem.bin
<ID:0/008> Transmission Complete..
<ID:0/008> Now Writing.. Please wait about 2 minutes
<ID:0/008>
<ID:0/008> Receive Response form LOKE
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/008> Removed!!
Does anyone have a clue?

Still noone has a clue?

Do like above poster said and try to access download mode, done by either volume down, home, power, all together or by using a jig if that doesnt work. Even if you screen is not displaying anything hook it up to odin and see if odin detects it. Youll know if it does because a com port will turn yellow. If it does flash back to stock and repartition with 512pit.

stuck at samsung galaxy note n-7000

after i wrongly flshed criskelo rom(isntantly flashed rom in cmw whit out anything i forgoted ) my phone can't boot!
stuck at samsung galaxy notetryed every rom and...
after wrongly..! i followed root galaxy note .com steps exactly
event can't boot whit parandroid rom that i did tryed befor that!
trying too unroot to STOCK GB whit ODIN http://rootgalaxynote.com/galaxy-note-unroot/how-to-unroot-galaxy-note-gt-n7000/

kamranhaghighi said:
after i wrongly flshed criskelo rom(isntantly flashed rom in cmw whit out anything i forgoted ) my phone can't boot!
stuck at samsung galaxy notetryed every rom and...
after wrongly..! i followed root galaxy note .com steps exactly
event can't boot whit parandroid rom that i did tryed befor that!
trying too unroot to STOCK GB whit ODIN http://rootgalaxynote.com/galaxy-note-unroot/how-to-unroot-galaxy-note-gt-n7000/
Click to expand...
Click to collapse
Flash gb rom by using PC ODIN. After flashing gb rom go to recovery and wipe data and cache. Try this method.

ty but can u give me a link? i jsut founded this http://forum.xda-developers.com/showthread.php?t=1424997
i can't download but i did 1 time and can't pause and download speed is 2kb/s:| its 3:50 am and i jsut waiting for linK plz somone give me one tomarow i most go for my wimax because it had delay for 8 days and still waiting

any GB/\ ROM? i tryed a rocket rom GB from CWM but still stuck anyway im download ODIN version and waiting to download!
or stock?

kamranhaghighi said:
any GB/\ ROM? i tryed a rocket rom GB from CWM but still stuck anyway im download ODIN version and waiting to download!
or stock?
Click to expand...
Click to collapse
You must flash stock GB rom only, using odin.

jeetu1981 said:
You must flash stock GB rom only, using odin.
Click to expand...
Click to collapse
+1, yes PC ODIN only
Dont flash ics rom and do the wiping in data, it will hardbrick your phone. WARNING DONT WIPE IN ICS RECOVERY DATA OR FACTOCRY RESET OR DO NANDROID IT WILL SUPERBRICK YOUR PHONE.o

ok can u give me a link plz fast! and superbrick is unfixable?

kamranhaghighi said:
ok can u give me a link plz fast! and superbrick is unfixable?
Click to expand...
Click to collapse
This link might be helpful....its a pre rooted gb rom thread, can b used in pc odin....
All d best...!!!:good::good::good:
XDA Thread:
http://forum.xda-developers.com/showthread.php?t=1535025

thanks downloading no wipe

GOD WHY? all links are from hotfile ;( unluky badly unluky

this http://forum.xda-developers.com/showpost.php?p=25289773&postcount=207 saved me
i'm following this video now whit my 4-10kb/s net speed:| it takes 1h to load i can't wait for my wimax!
http://www.youtube.com/watch?v=ehXcnqntsro

afte that i see someting like isntalling updates than it stuck at galaxy note n7000 again
can i return my phone? some 1 help me plz

<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Rooted_Stock_Odex_N7000XXLA6.tar.md5 is valid.
<OSM> MODEM.tar.md5 is valid.
<OSM> CSC_N7000XEULA1_XEU.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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> factoryfs.img
<ID:0/003> NAND Write Start!!
<ID:0/003> hidden.img
<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> cache.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
thats log but still stuck at samsung galaxy note n-700 logo
PLZ i wont lose my 1300$ expancive device

kamranhaghighi said:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Rooted_Stock_Odex_N7000XXLA6.tar.md5 is valid.
<OSM> MODEM.tar.md5 is valid.
<OSM> CSC_N7000XEULA1_XEU.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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> factoryfs.img
<ID:0/003> NAND Write Start!!
<ID:0/003> hidden.img
<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> cache.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
thats log but still stuck at samsung galaxy note n-700 logo
PLZ i wont lose my 1300$ expancive device
Click to expand...
Click to collapse
Stuck at Samsung logo is normal if you flash GB rom over ICS, just go to recovery (vol up+ home + power) and perform wipe and reboot.
As you are on Gingerbread now, it is safe to perform full wipe in stock recovery.

jeetu1981 said:
Stuck at Samsung logo is normal if you flash GB rom over ICS, just go to recovery (vol up+ home + power) and perform wipe and reboot.
Click to expand...
Click to collapse
This will solve your issue
Sent from my GT-N7000 using xda premium

THANKS REALLY but if not work can i pm u?^_^

did a wipedata/factory reset in stock recovery but still stuck at samsung galaxy note GT-N7000

kamranhaghighi said:
did a wipedata/factory reset in stock recovery but still stuck at samsung galaxy note GT-N7000
Click to expand...
Click to collapse
replied to your pm, please check it.

and one mroe thing
i did this! Nandroid Backup and Restore:
You are able to do Full Nandroid Backups on CF-Root Kernel. But you have to restore them using Abyss Kernel 4.2!!!
If you try to Restore with CF-Root, your Restore will hang up and you will at least lose Root
(befor lfashing GB whit odin!

waiting to recive ur repalay! it takes long time whit irans net:S

Note Hung On Samsung Logo Screen - Stock ROM

I have a Galaxy Note which has never been rooted and has the factory Gingerbread ROM running.
This morning it worked fine, then a couple of hours later the screen was black and I couldn't turn it on. So I removed and replaced the battery and turned the phone on. Ever since then, and no matter how many times I turn it off/on, it just freezes on the Samsung logo screen with the logo fading in/out.
What's the solution and what has gone wrong with it?

EViS said:
I have a Galaxy Note which has never been rooted and has the factory Gingerbread ROM running.
This morning it worked fine, then a couple of hours later the screen was black and I couldn't turn it on. So I removed and replaced the battery and turned the phone on. Ever since then, and no matter how many times I turn it off/on, it just freezes on the Samsung logo screen with the logo fading in/out.
What's the solution and what has gone wrong with it?
Click to expand...
Click to collapse
I would suggest booting into recovery and doing a factory reset. If that doesn't work use Odin to reflash the stock firmware, and see if that fixes things.
Sent from my SCH-I535 using xda premium

My phone is still in warranty. Am I right in thinking that using ODIN will void the warranty?
How do you boot into recovery on a factory ROM?

instal a stok rom with odin

EViS said:
My phone is still in warranty. Am I right in thinking that using ODIN will void the warranty?
How do you boot into recovery on a factory ROM?
Click to expand...
Click to collapse
Get a stock rom from dr. Ketan's thread in the original development. Press volume down+power+home buttons to boot into download mode then you can flash the rom you got using pc odin. It won't affect the warranty as it will not raise the counter and because you are flashing a stock rom
Sent from my GT-N7000 using xda app-developers app

What could have caused this crash? My only concern is that it could be a hardware memory fault, hence it would be worth sending it out to Samsung just in case.

Just flashed a stock UK ROM via PC Odin.
It showed Pass with the following Messages:
Code:
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLA6_N7000XXLA4_N7000XEULA1_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..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> cache.img
<ID:0/009> NAND Write Start!!
<ID:0/009> factoryfs.img
<ID:0/009> hidden.img
<ID:0/009> modem.bin
<ID:0/009> zImage
<ID:0/009> RQT_CLOSE !!
<ID:0/009> RES OK !!
<ID:0/009> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/009> Removed!!
<ID:0/007> Added!!
<ID:0/007> Removed!!
However, upon booting the phone is still stuck on the Samsung logo . Any further suggestions?

EViS said:
Just flashed a stock UK ROM via PC Odin.
It showed Pass with the following Messages:
Code:
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLA6_N7000XXLA4_N7000XEULA1_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..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> cache.img
<ID:0/009> NAND Write Start!!
<ID:0/009> factoryfs.img
<ID:0/009> hidden.img
<ID:0/009> modem.bin
<ID:0/009> zImage
<ID:0/009> RQT_CLOSE !!
<ID:0/009> RES OK !!
<ID:0/009> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/009> Removed!!
<ID:0/007> Added!!
<ID:0/007> Removed!!
However, upon booting the phone is still stuck on the Samsung logo . Any further suggestions?
Click to expand...
Click to collapse
Now that you have flashed the stock image, boot into recovery and try a factory reset again.

A factory reset fixed it! Why did I have to do a factory reset AFTER installing the new ROM? Why didn't the new ROM installation work on its own? Looking for a technical answer here .

May be the battery went dead because of which the some data got corrupted.
If I am not wrong it was stuck at the Samsung glowing logo?
data corruption causes boot loops and a factory reset will solve it
the rom you installed was a non wipe rom which does not do a wipe and just upgrades the os to stock so the corrupted data still remained. thus required a reset

Thank you for the explanation .

nokiamodeln91 said:
May be the battery went dead because of which the some data got corrupted.
If I am not wrong it was stuck at the Samsung glowing logo?
data corruption causes boot loops and a factory reset will solve it
the rom you installed was a non wipe rom which does not do a wipe and just upgrades the os to stock so the corrupted data still remained. thus required a reset
Click to expand...
Click to collapse
good explanation:good:

[q] gt-n7000 need help!!!!

Hay guys.Sorry to open new thread,but I really need help.I got galaxy note (N7000) and the problem is that is stuck ob samsung boot logo.I have tried every single solution I could find on the web,but with no luck.I dont even know on what rom is ATM because i got it in this condition.All I know is that it was bought in Austria
PLEASE HELP!!!!

Have you tried booting it into recovery mode or download mode?
Recovery: Press Home + Volume Up + Power On. Stay pressed until GT-N7000 logo comes up.
Download: Press Home + Volume Down + Power On. Stay pressed until GT-N7000 logo comes up.

Nibb31 said:
Have you tried booting it into recovery mode or download mode?
Recovery: Press Home + Volume Up + Power On. Stay pressed until GT-N7000 logo comes up.
Download: Press Home + Volume Down + Power On. Stay pressed until GT-N7000 logo comes up.
Click to expand...
Click to collapse
i can only get it in download mode.when i try to start recovery mode the phone stops at samsung logo and just hangs there all day

Go to the download mode, flash a stock ROM for your region using PC ODIN and go thru dr.ketan's thread in the original Android development forum. Flash a stock ROM and then flash a kernel like the PhilZ kernel that you'll find in the thread on how to root and this boot loop bug will be out forever.

thanks for your effort Varad,but still not luck.I guess I got a pretty expensive paper weight :crying:

bizzare187 said:
thanks for your effort Varad,but still not luck.I guess I got a pretty expensive paper weight :crying:
Click to expand...
Click to collapse
post the result or screenshot of pc odin or just mention where is it getting stuck while flashing.

flashing goes without problem,but when the phone reboots it stucks on samsung logo

bizzare187 said:
flashing goes without problem,but when the phone reboots it stucks on samsung logo
Click to expand...
Click to collapse
do you get message on pc oding saying success1/failed0?

yes i get that message and then phone reboots.and it stucks

bizzare187 said:
yes i get that message and then phone reboots.and it stucks
Click to expand...
Click to collapse
have you tried flashing again?

treacherous_hawk said:
have you tried flashing again?
Click to expand...
Click to collapse
yes i did.i will do it again now and post odin messages
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLQ3_N7000OXXLP7_N7000XXLPT_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> cache.img
<ID:0/008> NAND Write Start!!
<ID:0/008> hidden.img
<ID:0/008> factoryfs.img
<ID:0/008> zImage
<ID:0/008> modem.bin
<ID:0/008> RQT_CLOSE !!
<ID:0/008> RES OK !!
<ID:0/008> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/008> Removed!!

And yet it is stuck on the boot logo? Well that thing about the paperweight seems to be right now

Varad297 said:
And yet it is stuck on the boot logo? Well that thing about the paperweight seems to be right now
Click to expand...
Click to collapse
friend told me to try a full wipe rom.is it a good idea?if it is,i just wanna know if it is flashable via odin.

Look haven't you wiped data before flashing ROMs? And yes any full wipe ROM with a .tar file is flashable via odin. But a full wipe ROM is of no use if you wipe data and cache before a flash, it's the same.

Varad297 said:
Look haven't you wiped data before flashing ROMs? And yes any full wipe ROM with a .tar file is flashable via odin. But a full wipe ROM is of no use if you wipe data and cache before a flash, it's the same.
Click to expand...
Click to collapse
no i havent wiped anything.i got the phone in this condition.i can only enter download mode.when i try to enter recovery mode the phone stucks at logo.same thing if i just try to turn it on.

Yes try a full wipe ROM then, no harm in trying...

tried the wipe ROM.still no luck
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_N7000XXKL8_CL840182_REV02_user_low_ship.tar.md5 is valid.
<OSM> MODEM_N7000XXKL8_REV_05_CL1089796.tar.md5 is valid.
<OSM> GT-N7000-MULTI-CSC-OXAKL8.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> boot.bin
<ID:0/008> NAND Write Start!!
<ID:0/008> Sbl.bin
<ID:0/008> param.lfs
<ID:0/008> zImage
<ID:0/008> factoryfs.img
<ID:0/008> data.img
<ID:0/008> cache.img
<ID:0/008> hidden.img
<ID:0/008> modem.bin
<ID:0/008> Transmission Complete..
<ID:0/008> Now Writing.. Please wait about 2 minutes
<ID:0/008> Receive Response form LOKE
<ID:0/008> cache.img
<ID:0/008> RQT_CLOSE !!
<ID:0/008> RES OK !!
<ID:0/008> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/008> Removed!!

still under warranty?

Get to the service center...that's the only way i see out of this...

treacherous_hawk said:
still under warranty?
Click to expand...
Click to collapse
no,warranty is expired
Varad297 said:
Get to the service center...that's the only way i see out of this...
Click to expand...
Click to collapse
thanks a lot everybody for trying

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?