Hello everyone.
sorry my English writing is not very well
I have a samsung galaxy gt-p3110 with a defect When I put the power button on he is starting and i'll see the samsung logo on the screen.
After a view seconds the tablet is getting off.
the power button + volume up does not work.
when i put the power button + volume button down it is going in the download modus.
When i open odin3 and plugged the USB cable in to my pc,the samsung connect with odin but i dont no what to do.
I dont no what rom was on the tablet before,
so who can help me
With compliments, Raymon
raymon nijenhuis said:
Hello everyone.
sorry my English writing is not very well
I have a samsung galaxy gt-p3110 with a defect When I put the power button on he is starting and i'll see the samsung logo on the screen.
After a view seconds the tablet is getting off.
the power button + volume up does not work.
when i put the power button + volume button down it is going in the download modus.
When i open odin3 and plugged the USB cable in to my pc,the samsung connect with odin but i dont no what to do.
I dont no what rom was on the tablet before,
so who can help me
With compliments, Raymon
Click to expand...
Click to collapse
Did you download the lastest firmware available for P-3110 on samfirmware?
If yes, when you connect your tablet to your PC, ODIN says something like "0:[COM4]" with a blue blackground?
If yes, put the .md5 file taken from lastest firmware downloaded before and add it into PDA..Then check the "Auto-Reboot" and "F.reset Time" boxes and click start! Wait 5 min and when a green background with a text "PASS!" appears, your Tab will reboot itself.
Hope this helps you )
Thank you
I gonna try it out.
I'm letting you know
:good:
Ive tried what you said but everything seems to be going good but after installing the rom the samsung is getting on and a few secs later (the samung logo is vissible)it's going of.
Odin saids
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P3110XXDNE1_P3110PHNDNE1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> system.img
<ID:0/005> NAND Write Start!!
<ID:0/005> boot.img
<ID:0/005> cache.img
<ID:0/005> hidden.img
<ID:0/005> recovery.img
<ID:0/005> MLO
<ID:0/005> param.lfs
<ID:0/005> Sbl.bin
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
power button + volume up nothing(only the samsung screen for a couple of secs)
What I'm doing wrong?
raymon nijenhuis said:
Ive tried what you said but everything seems to be going good but after installing the rom the samsung is getting on and a few secs later (the samung logo is vissible)it's going of.
Odin saids
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P3110XXDNE1_P3110PHNDNE1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> system.img
<ID:0/005> NAND Write Start!!
<ID:0/005> boot.img
<ID:0/005> cache.img
<ID:0/005> hidden.img
<ID:0/005> recovery.img
<ID:0/005> MLO
<ID:0/005> param.lfs
<ID:0/005> Sbl.bin
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
power button + volume up nothing(only the samsung screen for a couple of secs)
What I'm doing wrong?
Click to expand...
Click to collapse
Did you unplug the cable when there was a text box with a green background saying "PASS!"?
I think no, because there is no "PASS" in your log..So re-flash the ROM.
P.s. And then..After the RES OK text did the tab reboot itself?
Did you unplug the cable when there was a text box with a green background saying "PASS!"? yes
I think no, because there is no "PASS" in your log..So re-flash the ROM. OKE
After the RES OK text did the tab reboot itself?yes for a few seconds and then its of again
Shall i try another rom?I dont no what happens before with this tab.
Thanks for helping me
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P3110XXDMH1_P3110OXADMH1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> cache.img
<ID:0/005> hidden.img
<ID:0/005> recovery.img
<ID:0/005> system.img
<ID:0/005> Sbl.bin
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
raymon nijenhuis said:
Did you unplug the cable when there was a text box with a green background saying "PASS!"? yes
I think no, because there is no "PASS" in your log..So re-flash the ROM. OKE
After the RES OK text did the tab reboot itself?yes for a few seconds and then its of again
Shall i try another rom?I dont no what happens before with this tab.
Thanks for helping me
Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
P3110XXDMH1_P3110OXADMH1_HOME.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Odin v.3 engine (ID:5)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
boot.img
NAND Write Start!!
cache.img
hidden.img
recovery.img
system.img
Sbl.bin
RQT_CLOSE !!
RES OK !!
Removed!!
Completed..
All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
Mmm..The log seems great for me.
I mean, it should works.
But what happened to this Tab? Why it went to bootloop?
P.s. Anyways, try another firmware.
SlimShady's said:
Mmm..The log seems great for me.
I mean, it should works.
But what happened to this Tab? Why it went to bootloop?
P.s. Anyways, try another firmware.
Click to expand...
Click to collapse
I dont know what happend to this tab,I bought this thing with the problem.
I tried other roms but everytime with the same result.
What does bootloader do?
what can I do :crying:
raymon nijenhuis said:
I dont know what happend to this tab,I bought this thing with the problem.
I tried other roms but everytime with the same result.
What does bootloader do?
what can I do :crying:
Click to expand...
Click to collapse
I think is a motherboard problem..With that successfully log, it MUST work..
raymon nijenhuis said:
Did you unplug the cable when there was a text box with a green background saying "PASS!"? yes
I think no, because there is no "PASS" in your log..So re-flash the ROM. OKE
After the RES OK text did the tab reboot itself?yes for a few seconds and then its of again
Shall i try another rom?I dont no what happens before with this tab.
Thanks for helping me
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P3110XXDMH1_P3110OXADMH1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> cache.img
<ID:0/005> hidden.img
<ID:0/005> recovery.img
<ID:0/005> system.img
<ID:0/005> Sbl.bin
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
you try to press the power button and volume up to enter the system recovery after that you select menu factory reset so select.
after which your phone will reboot itself. and wait 5-10 minutes at the start of entry of boot logo.
if it still fails try to open the back cover of your phone and remove the battery let stand until 10-20 minutes.
and put again the battery in place.try to trun on your phone...
Related
I got a Samsung Galaxy Tab (GT-P5110) of which the tablet did not startup anymore, and know nothing about the prehistory.
I downloaded stock firmware from samsung site: http://samsung-updates.com/device/?id=GT-P5110
and downloaded the latest EUR version named : P5110XXDMI1_P5110OXXDMJ1_HOME.tar.md5
With Odin 3.07 I installed that image in download mode with default options left on. After that I got the following screen message on the tablet:
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
Probably something went wrong. Then I downloaded Kies from samsung site, installed it with all extra drivers and I got the problem that Kies never recognized the tablet. Reinstalled many times, tried different options, but the problem persisted (took me 8 hours totally). Battery of the tablet was fully loaded and before this problem I saw that it was loading correctly.
Then I read this excellent document : http://forum.xda-developers.com/showthread.php?t=1652398
Tried again with Odin 3.07 and 1.85 and could install the image with only the reboot option on in Odin, flashed successfully the image, but still the problem:
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
I do not have much options left to look for. I was thinking about:
- driver issue
- wrong image
- wrong method
Can somebody help me to have this problem fixed ? I am willing to reinstall Windows 7 on this laptop.
Really nobody knows ?
never had problems here on Windows 8.
Maybe try flashing using Heimdall
But will I need a Heimdall image for that, because it does not accept the samsung image.
proconsoles said:
But will I need a Heimdall image for that, because it does not accept the samsung image.
Click to expand...
Click to collapse
But will I need a Heimdall image for that, because it does not accept the samsung image.
But when I use Odin 3.07 it looks like everything went fine:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P5110XXDMI1_P5110OXXDMJ1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> system.img
<ID:0/005> NAND Write Start!!
<ID:0/005> boot.img
<ID:0/005> cache.img
<ID:0/005> hidden.img
<ID:0/005> recovery.img
<ID:0/005> MLO
<ID:0/005> param.lfs
<ID:0/005> Sbl.bin
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
But when I disconnect the usb cable after that, and hold the power button for a couple of seconds I still see:
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
What could be the cause of this ?
proconsoles said:
But will I need a Heimdall image for that, because it does not accept the samsung image.
But when I use Odin 3.07 it looks like everything went fine:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P5110XXDMI1_P5110OXXDMJ1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> system.img
<ID:0/005> NAND Write Start!!
<ID:0/005> boot.img
<ID:0/005> cache.img
<ID:0/005> hidden.img
<ID:0/005> recovery.img
<ID:0/005> MLO
<ID:0/005> param.lfs
<ID:0/005> Sbl.bin
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
But when I disconnect the usb cable after that, and hold the power button for a couple of seconds I still see:
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
What could be the cause of this ?
Click to expand...
Click to collapse
I am located in The Netherlands, and downloaded the specific image for the Netherlands, region PHN, used Odin 3.07 to install it, but still the same problem.
What can I do, wait for somebody who can give me a hint ? This is the first time I do a recovery of a Samsung tablet, and don't know how to continue with it.
Your help will be very much appreciated.
Maybe not the ideal situation, but try installing a custom recovery and a custom rom
If this works, it's no hardware problem.
You can use this guide to install a custom recovery
Joery360 said:
Maybe not the ideal situation, but try installing a custom recovery and a custom rom
If this works, it's no hardware problem.
You can use this guide to install a custom recovery
Click to expand...
Click to collapse
I got still the same problem, did exactly this procedure : http://forum.xda-developers.com/showpost.php?p=50174804&postcount=3
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GT-P5110_CWM_6.0.4.7_Swipe-Edition.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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
Even reinstalled the drivers, but the problem remains the same, still keeping the message:
Firmware upgrade encountered and issue. Please select recovery mode in Kies & try again.
proconsoles said:
I got still the same problem, did exactly this procedure : http://forum.xda-developers.com/showpost.php?p=50174804&postcount=3
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GT-P5110_CWM_6.0.4.7_Swipe-Edition.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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
Even reinstalled the drivers, but the problem remains the same, still keeping the message:
Firmware upgrade encountered and issue. Please select recovery mode in Kies & try again.
Click to expand...
Click to collapse
Do you think that this problem is hardware related ??
Nobody knows ?
Same for me
I'm dealing with almost the same issue, except for my ODIN flashes it doesn't even succeed. I know this happened to it after I tried to use heimdall to update my CWM, but I have had no success getting anything to work. I've been without a tablet for like a week now, doing everything I can think of or find a walk through for. I mean for me, I wouldn't mind going back to stock as long as it works again. Here's what my ODIN is doing:
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I'm about to try the TWRP someone recommended above, I'll let you know how it goes
---------- Post added at 08:25 PM ---------- Previous post was at 08:20 PM ----------
I tried flashing a different version of TWRP and it looked like it was going to do something, but it isn't going. Here's what it did this time:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GT-P5110_TWRP_2.7.0.1.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> SingleDownload.
<ID:0/008> recovery.img
<ID:0/008> NAND Write Start!!
<ID:0/008> FAIL!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Forgot to mention that I'm using Odin 3.09 on a p5113. Not that it makes huge difference.
Two things to try:
If you can boot into recovery, try the factory reset.
If not, have you tried Kies recovery mode?
The problem is that I can only boot into the special download mode, if I could get into recovery I think I could figure it out. I have tried the kies recovery, but it won't even read the device.
Maybe because Samsung / KIES Process running in background on your PC?
A Case of bad partitions
Deucethehero said:
The problem is that I can only boot into the special download mode, if I could get into recovery I think I could figure it out. I have tried the kies recovery, but it won't even read the device.
Click to expand...
Click to collapse
Try flashing with .pit file, partitioning set to on. Should correct partition problems. Somebody might have installed a non-android OS that botched. Look for a .pit file around the forum, you should find one. Good luck.
Thank you
Thanks for the tip, I'll give it a shot and post back with results!
Sorry for the late reply
Hey guys, I could have sworn that I posted back on Friday, but it's not here. Anyway, it's been a crazy few days for me traveling and school starting and all that.
About the tablet, I downloaded a pit file and it looked like it was going to work, but unfortunately it did not. I'm working on getting the tablet charged and set up to try again because I got a zip that had 2 pit files, so I'll try the other one soon. I'll post the results when I get them, thanks again for all the help!
Still not working, but I think some progress
Sorry to take so long responding, it's been a busy week.
So I just attempted to flash the .pit again, and it failed. Here's what Odin gave:
<ID:0/006> Added!!
<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> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006>
<ID:0/006> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
It says, "There is no PIT," but that's what I'm trying to flash, right? I'm a little confused, but I hope someone knows what that means.
Thanks for all the help guys!
New info!
So today I was messing around with the .pit file that I had, and I used an editor to make it exactly the same as one I found in another forum. After Odin told me that it failed, I went to reset the tablet, and it showed me the Galaxy Tab 2 screen, which it has not done for a few weeks now. Then I plugged it in and it shows the battery charging symbol. Currently it is a 18%, so I'm going to let it charge and then try booting it up again and see what I get. Hopefully all is well now, but we shall see here in a few hours.
I also was not aware that I needed to flash the system along with the pit, and once I had that going it made a little more sense to me.
I'm going to try to post that pit here if anyone wants it. Hopefully it will help someone else in the future.
Odin Flashed, but failed
So I got into normal old download mode on the device using that .pit file. Yay! However upon attempting to flash the stock os back on Odin gave me this:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P5113UEBLH3_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> SingleDownload.
<ID:0/006> boot.img
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I'm going to look into other avenues, but this did set me back to the "Firmware upgrade encountered an issue... blah blah"
Hi, i have a Norwegian Samsung Galaxy S6 and tried to root it using the SM-G920F files from CF-Auto-Root but it didnt work and now my phone wont start with the message: "Recover is not seandroid enforcing" where it says "Samsunng Galaxy S6
Powered by Android". I have tried all the SM-G920F Stock firmwares here but unable to install them, maybe my device should have been rooted before this? Is there i way i can fix my phone now? I cant even shut it down anymore :/
I have tried to follow this guide: autoroot.chainfire but it didnt work and now i have tried to use the UK/spain/Every-Stock-Firmware-for-the-G920F-i-Can-Find.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920FXXU1AOCZ_G920FVFG1AOC4_G920FXXU1AOCW_HOME.tar .md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1005)..
<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> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
On the phone itself it says "SW REV. CHECK FAIL. DEVICE:2 BINARY:1
With red text.
Is what ODIN3 v3.10 is saying.
To shut down S6 from download mode press volume down + power button at the same time and hold until screen turns off.
After this you have an option to:
1. Bring your S6 bacck to Samsung for warranty repair.
2. Use a different USB cable or try a different USB port then reflash again.
I hope this helps.
roydok said:
To shut down S6 from download mode press volume down + power button at the same time and hold until screen turns off.
After this you have an option to:
1. Bring your S6 bacck to Samsung for warranty repair.
2. Use a different USB cable or try a different USB port then reflash again.
I hope this helps.
Click to expand...
Click to collapse
It Says KNOX warranty void 1, this means that warranty is broken? I am going to get my original samsung s6 USB cable tomorrow to try.
Install twrp and port any costum room and you will fix your s6...
Or download newest version in sammobile of g920f stock firmware. You are failing at sboot. That mean bootloader in the phone os newer than the one you trying to install
Now it does not fail right away, but it still fails after a short while. Will the process fail if i don't do anything on the device itself? Because now it starts doing something in Odin, but returns fail after a while, but i am not with the phone as it is home right now.
This is what ODIN says now:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920FXXU2BOFL_G920FOJV2BOEE_G920FXXU2BOFJ_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1005)..
<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> NAND Write Start!!
<ID:0/005> cm.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img
<ID:0/005> modem.bin
<ID:0/005> cache.img
<ID:0/005> hidden.img
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Try redownloading your ROM. There might be errors in the file resulting from the download.
Hi all!
I recently got a used S6 from the UK and it was lagging and crashing all the time. So I decided to install the original ROM again. Got it from Sammobile and Odin failed:
<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> boot.img
<ID:0/005> cache.img
<ID:0/005> cm.bin
<ID:0/005> hidden.img
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Now I'm starting to think that it's maybe not from the UK but I guess it's to late to use the codes to get my CSC or even region/operator information, since I have the light blue notification about using Smart Switch on the PC to restore the device. The Smart Switch tells me that S6 is not supported Kies 3 does the same. I decided to simply get another FW from sammobile but the problem comes to as to which one to download since I have no notification about the phone.
Any ideas? To answer before; I cannot go into download mode or anything like that.
Hello, i am having a problem flashing the stock rom on GT-i9105P, i tried alot of roms but still none of them works.
I tried 4 Files repair firmware 4.1.2 and this is the log:
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> BcmBoot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> HEDGE_RF_LE_SS_CAPRI_00.bin
<ID:0/005> sysparm_dep.img
<ID:0/005> sysparm2_dep_blob.img
<ID:0/005> sboot.bin
<ID:0/005> param.lfs
<ID:0/005> dt-blob
<ID:0/005> vc-firmware.img
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
---------------------------------------------------------------
4.1.2 Stock rom 1 file, flash log:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9105PXXAMC2_I9105POXXAMB5_I9105PXXAMC1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> vc-firmware.img
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> BcmCP.img
<ID:0/005> dt-blob
<ID:0/005> cache.img
<ID:0/005> system.img
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
-------------------------------------------------------
4.2.2 Stock rom 1 file, flash log:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9105PXXUBNB1_I9105POXABNA1_I9105PXXUBNB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I also trie alot of Odin versions, but none works :/
Help me please, i've been trying to flash it from 2 days ago
Have you tried flashing RedRom, made by me?
It's stock 4.2.2 + extra optimizations.
Johnny TDN said:
Have you tried flashing RedRom, made by me?
It's stock 4.2.2 + extra optimizations.
Click to expand...
Click to collapse
First, thanks for replying.
No, i didn't try it..i would like to ask if you can give me it!
Goat678 said:
First, thanks for replying.
No, i didn't try it..i would like to ask if you can give me it!
Click to expand...
Click to collapse
Check my threads on my.profile. You will find RedRom there.
Johnny TDN said:
Check my threads on my.profile. You will find RedRom there.
Click to expand...
Click to collapse
Well, thx i already found it..
But still having a problem in odin while flashing TWRP/CWM recoveries...
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> TWRP-2.6.30_4.2.2_ODIN-s2vep.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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
Can you help me please?
Goat678 said:
Well, thx i already found it..
But still having a problem in odin while flashing TWRP/CWM recoveries...
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> TWRP-2.6.30_4.2.2_ODIN-s2vep.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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
Can you help me please?
Click to expand...
Click to collapse
If you have root on your phone, use Flashify.
...
Johnny TDN said:
If you have root on your phone, use Flashify.
Click to expand...
Click to collapse
Well, the phone is not turning on.
While turning on shows this message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
and i cannot boot to recovery mode on my device and cannot flash any thing :/
Goat678 said:
Well, the phone is not turning on.
While turning on shows this message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
and i cannot boot to recovery mode on my device and cannot flash any thing :/
Click to expand...
Click to collapse
Try this one
https://m.youtube.com/watch?v=7zEhC4kvMUE
Goat678 said:
Well, the phone is not turning on.
While turning on shows this message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
and i cannot boot to recovery mode on my device and cannot flash any thing :/
Click to expand...
Click to collapse
You fixed your problem?
Johnny TDN said:
You fixed your problem?
Click to expand...
Click to collapse
Unfortunately, no.
I still can't fix it
Goat678 said:
Unfortunately, no.
I still can't fix it
Click to expand...
Click to collapse
Then i'm afraid that you must buy a new motherboard. Sorry.
Johnny TDN said:
Then i'm afraid that you must buy a new motherboard. Sorry.
Click to expand...
Click to collapse
Well, i kept trying till i just flashed TWRP recovery, then installed your RedRom
and its very good!
Thanks ♥
Hi everyone.
My Galaxy Tab 2 10.1 was running on LineageOS 13 but it was very slow. I wanted to go back to official rom.
I used Odin 3.14.4 and flashed P5100XXDMD1_P5100DBTDMD1_P5100XXDLL2_HOME.tar.
Everything seemed fine (see log below) exept it doesn't boot!
It loops on the blue circle turning into the Samsung logo.
Re-flashing did not help.
The log:
Code:
<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> Added!!
<ID:0/005> Odin engine v(ID:3.1401)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 1126 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> system.img
<ID:0/005> boot.img
<ID:0/005> cache.img
<ID:0/005> hidden.img
<ID:0/005> recovery.img
<ID:0/005> modem.bin
<ID:0/005> MLO
<ID:0/005> param.lfs
<ID:0/005> Sbl.bin
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
wasThere said:
Hi everyone.
My Galaxy Tab 2 10.1 was running on LineageOS 13 but it was very slow. I wanted to go back to official rom.
I used Odin 3.14.4 and flashed P5100XXDMD1_P5100DBTDMD1_P5100XXDLL2_HOME.tar.
Everything seemed fine (see log below) exept it doesn't boot!
It loops on the blue circle turning into the Samsung logo.
Re-flashing did not help.
The log:
Code:
<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> Added!!
<ID:0/005> Odin engine v(ID:3.1401)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 1126 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> system.img
<ID:0/005> boot.img
<ID:0/005> cache.img
<ID:0/005> hidden.img
<ID:0/005> recovery.img
<ID:0/005> modem.bin
<ID:0/005> MLO
<ID:0/005> param.lfs
<ID:0/005> Sbl.bin
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
Force tab to recovery and do factory reset!
drnightshadow said:
Force tab to recovery and do factory reset!
Click to expand...
Click to collapse
I can't.
Power + volume up = reboot
Power + volume down = download mode
wasThere said:
I can't.
Power + volume up = reboot
Power + volume down = download mode
Click to expand...
Click to collapse
Try to redownload firmware... Something was wrong, if you can't access to recovery... Are you sure your downloading the right firmware for your tab?
And try using older odin... just an idea.
drnightshadow said:
And try using older odin... just an idea.
Click to expand...
Click to collapse
Good guess. Odin 3.09 worked better.
Now, power + volume up leads to recovery. I did the factory reset and then reboot.
It's fine.
Thank you very much (as I am too stupid to find the Thanks button!).
wasThere said:
Good guess. Odin 3.09 worked better.
Now, power + volume up leads to recovery. I did the factory reset and then reboot.
It's fine.
Thank you very much (as I am too stupid to find the Thanks button!).
Click to expand...
Click to collapse
Lol haha ... Thanks button he he .. I'm to lazy to update it
Anyway, it's nice to hear that you bring your tab back to life.
Try clicking like button instead of thanks