Hi all,
I recently tried upgrading my Samsung Galaxy S from Eclair to Froyo through Samsung Kies, but however it would not move past 1% for a long time (1 hour?), and would not cancel the update so had no choice but to disconnect my USB. Since then, it would only show the Phone ! Computer sign.
I bought myself a jig which set it on into download mode. First I accidently hit start on Odin without loading any firmware which kick started my phone back to how it was before this accident. I then downloaded the I9000XWJS3|2.2.1|2011 January (not actually knowing the stock firmware type on my phone). I loaded the file as a PDA, and got a Pit file, 512. No luck it would not load. It would get stuck and modem.ini or something like that. After a few tries of unplugging, using jug and replugging back to usb, I tried again, but Odin accidentally started up with "re-partition" aswell and after loading the PDA file and PIT file I clicked start with repartition ticked.
Since then the phone won't even start, even plugged into a charger, not even the Phone ! Computer sign anymore. Just a blank screen. However using the Jig still puts it in download mode, but since my Phone is of the o2 network (UK), Ive even tried downloading and trying to flash Eclair firmware, I9000XXJM1, by loading the 512 pit file, loading the PDA, Phone and CSC files. Again, nothing, it gets stuck at:
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> Enter CS for MD5..
<ID:0/004> Check MD5.. Do not unplug the cable..
<ID:0/004> Please wait..
<ID:0/004> Checking MD5 finished Sucessfully..
<ID:0/004> Leave CS..
<ID:0/004> Enter CS for MD5..
<ID:0/004> Check MD5.. Do not unplug the cable..
<ID:0/004> Please wait..
<ID:0/004> Checking MD5 finished Sucessfully..
<ID:0/004> Leave CS..
<ID:0/004> Enter CS for MD5..
<ID:0/004> Check MD5.. Do not unplug the cable..
<ID:0/004> Please wait..
<ID:0/004> Checking MD5 finished Sucessfully..
<ID:0/004> Leave CS..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> factoryfs.rfs
and thats it, the blue bar on my phone moves a little, but gets stuck at factoryfs.rfs.
I literally have no idea what to do anymore and I feel I may of taken more than I can chew and worried I have perma bricked my phone or corrupted something. Should I send it in to Samsung for repair? Will they even repair it or be able to? My phone wont start up at all, and when I say that I mean you hold the power button and nothing comes on. It's not like before, not even the Phone ! Computer sign shows or anything, its just black. They only way I can get anything out of it is by plugging the Jig, which puts it in download mode.
Any idea's or help would be GREATLY appreciated.
PS: I tried runing Odin 1.3 in admin mode and under XP service pack 2 compatibility, no luck!
http://forum.xda-developers.com/showthread.php?t=853950
TRY
jje
Thanks but that post is for the firmware [JL2] Bell I9000M, which is for the samsung vibrant. I have the bog standard Samsung galaxy S. I'm not sure it will flash.
Any more advice and information really REALLY appreciated!
http://forum.xda-developers.com/showthread.php?t=818556
Odin section
jje
Nope even tried that post and downloaded the firmware, did exactly as he instructed. Phone is in download mode, the blue bar goes the same distance (like 2mm full) and stops for the rest of the time.
It gets stuck on:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9000XXJPU-REV03-PDA-low-CL747761.tar.md5 is valid.
<OSM> MODEM_I9000XXJPU.tar.md5 is valid.
<OSM> GT-I9000-CSC-MULTI-OXAJPU.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.bin
help please i got this unit stuck on upgrade screen
history:
the unit had too many pattern attempts then i tried hard resetting it by using the combination keys, but then after accessing the menu for hard resetting, when i press vol - to choose the reformat or factory reset (somthing like that i forgot) then it displayed forced uplaod mode by pressing keys. then i removed the battery and turned it on with just the power button, but it entered the hard reset menu again. i thought the volume keys were shorted so i removed them, but even if i have removed all the keys still stuck on the hard reset screen. then i tried connecting it to kies and one time it was detected, but it turned off then i showed that screen. it can be detected by my computer but not by kies or odin or any other flashers i have here.
up for this post can anybody help me pls?
Stuck on Upgrade Logo
chunkiebone said:
up for this post can anybody help me pls?
Click to expand...
Click to collapse
Mine got this problem too, any help guys?? thanks in advance
asukaragnaboy said:
Mine got this problem too, any help guys?? thanks in advance
Click to expand...
Click to collapse
if you are getting an "UPGRADE" screen, it means you have failed/unsusessfull flash and you are still in download mode, so just connect to fresh/reboot Odin and flash again recovery or flash WF07 ROM to recover
xsenman said:
if you are getting an "UPGRADE" screen, it means you have failed/unsusessfull flash and you are still in download mode, so just connect to fresh/reboot Odin and flash again recovery or flash WF07 ROM to recover
Click to expand...
Click to collapse
nope. my phone fully flashes whenever i flash it. odin always says completed. problem is that when the phone restarts, it's working ok until i remove it from cable. when i unplug it to cable, after a few minutes it turns off and goes to the never ending loop again (samsung logo, the first one with circle) or if i unplug it and charge it on a wall charger it turns off and guess what, it returns to the same loop again.
EDIT:
odin logs for reference
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXELL4_I9300H3GELL1_I9300NELK2_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> system.img
<ID:0/006> NAND Write Start!!
<ID:0/006> boot.img
<ID:0/006> cache.img
<ID:0/006> hidden.img
<ID:0/006> recovery.img
<ID:0/006> modem.bin
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/006> Removed!!
<ID:0/007> Added!!
I'm new here and I couldnt find a thread which had the same problem as me solved so here we go!
I tried manually installing the official jellybean firmware on my N7000 following the steps exactly (usb debugging on, download mode etc) Once I started to run Odin everything was fine until a massive FAIL occured. This is what Odin said
"<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000ZSLM5_N7000OZSLM5_N7000XXLSO_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> cache.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)"
Anyway now my phone won't start, it will turn on and but it gets stuck on the Samsung Logo, I booted it into recovery mode, wiped cache, user data and rebooted but it was still stuck on the Samsung logo. How do I fix my phone from here??
Have you installed the drivers on your pc?
64 bit - http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-USB-Driver-for-Windows-x64.shtml
32 bit - http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-USB-Driver-for-Windows-x86.shtml
Install the driver and then try again
Sent from my GT-N7000 using Tapatalk 2
check if kies is running.. close it from task manager... run odin as admin.. aslo before flashing again.. you need to power off and reboot into download mode
Thank you!!
Thanks, that's what I hadn't done, install the drivers. All working good now and have to say its great to finally have jellybean on 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?
Hi there.
My galaxy note 5 (unlocked) was working very well until yesterday
Some apps start crashing and start to slow down
And after it suddenly restarted and stuck in a restart boot
I tried a lot of ways to fix it began of:
- Boot it in safe mode (the apps still crashing)
- Wipe the cache partition
- Wide data factory
- And after that i treid to install stock firmware with odin i followed all the instruction. But Odin still showing FAILED
and this message :
-----------------------------------------------------------
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1203)..
<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> sboot.bin
<ID:0/005> cm.bin
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
---------------------------------------------------------------------
I activated the USB debugging and OEM unlocking btw.
Your help will be highly a appreciated
And thakns.
if you are rooted then you cannot fash it with odin now try smart switch. this software is samsung's official and will flash official firmware on your note 5.
No, I never rooted my phone !
And for the smart switch that was my try.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Try
Android Recovery
- Wide data factory
- Wipe the cache partition
-reboot to bootloader
itthipon555 said:
Try
Android Recovery
- Wide data factory
- Wipe the cache partition
-reboot to bootloader
Click to expand...
Click to collapse
I tried the first two ! and still have the same issue.
But what is the reboot to bootloader
Flash a custom Rom from twrp
godkingofcanada said:
Flash a custom Rom from twrp
Click to expand...
Click to collapse
Can you please give me a guide on how to do that ?
Yahya Joud said:
Can you please give me a guide on how to do that ?
Click to expand...
Click to collapse
You download twrp recovery here on xda for your device and flash it via Odin. Then put a custom Rom ( I recommend Dr ketan note 5 Rom). Also found here on xda, put it onto sdcard or if you have the usb flash drive adapter or you can probably even adb connect and push the zip if the other two aren't options. Then you flash the zip from twrp recovery menu(it takes the place of stock recovery. The one you hold power and volume up to get to.
note 5 920T need help
coolsongs95 said:
if you are rooted then you cannot fash it with odin now try smart switch. this software is samsung's official and will flash official firmware on your note 5.
Click to expand...
Click to collapse
i have the same problem,my phone is not rooted when i installed the firmware for 920T
it keeps turning on and off,i tried to install the firmware again in vain but it did not work .let me know please
If anyone says something about "if you are rooted you can't use odin" don't believe it!
I was rooted with TWRP installed and even xposed and still i could use odin to flash stock.
Are you flashing everything like bootloader and all this stuff? Do it if you didn't.
Else if you need backup rom i recommend "[ROM][7.0][MYSTYLEROM][N920CGI][RL3][19-01-19]".
It's the best backup rom in my opinion.
Try downloading the stock rom from different site again. Maybe rom is damaged.
And also try to
Yahya Joud said:
Hi there.
My galaxy note 5 (unlocked) was working very well until yesterday
Some apps start crashing and start to slow down
And after it suddenly restarted and stuck in a restart boot
I tried a lot of ways to fix it began of:
- Boot it in safe mode (the apps still crashing)
- Wipe the cache partition
- Wide data factory
- And after that i treid to install stock firmware with odin i followed all the instruction. But Odin still showing FAILED
and this message :
-----------------------------------------------------------
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1203)..
<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> sboot.bin
<ID:0/005> cm.bin
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
---------------------------------------------------------------------
I activated the USB debugging and OEM unlocking btw.
Your help will be highly a appreciated
And thakns.
Click to expand...
Click to collapse
Put the firmware in "AP" in odin. make sure you download the latest stock firmware because when i tried flashing a one month old firmware few months ago it said 'failed' so go on sammobile and check the latest version for your country and model number
Boot into download mode by holding power, volume down and home button together.
This will get you to download mode (odin mode)
Now connect to your pc and open odin
select AP and choose the md5 file you downloaded and click Start.
Then your phone will restart
Sent from my Note 5 using XDA Labs
Try this. Worked for me on n920c
my sm-n920c binary 3 was working properly however the phone crushed with OEM & Debug all switched off.
firstly i wiped data, factory reset because it was saying "custom rom blocked by frp".
second i tried installing new firmware but frp is on.
third i used smart key tool to remove frp but it resulted in removing the custom rom and drk.
fourth i installed new eng boot file
now im stuck at trying to installing new sboot file therefore i cant install new firmware.
please help atleast link me to any sboot.tar.md5 and perharps a latest n920c binary 3 file