Database Info

Help! Galaxy S2 won't boot (Phone--!--PC)

Hey, i am new here i used to get helps lot in this forum but now i am facing a problem that i didn't found a solution for it yet..
first off i tried to change from android 2.3.6 to 2.3.5 (Arabic support) using Odin v1.83 when i put the .tar file into PDA then i run it. gave me failed and the phone won't work again when i restarted it gave me result are like this : Phone--!--PC
please help me i cannot do anything.. i tried to remove the battery using usb cable go to recovery mode,,, download mode but nothing it keep appearing even it i turned off the phone just in one click to power button it appear again.. i am going to crazy and the phone has warranty expired please is there anyway to solve this problem?

I don't know if your phone is the same, but with my Nexus if stuck in bootloop I can plug the usb cable in and use adb to enter command "adb reboot bootloader" and get to fastboot and flash the stock images. Maybe you can try something like that. That's why I love the nexus I thought I bricked it a couple times but I always got back to stock images. or if you have a cwm restore you can get to that once in fastboot.

Thanks for your reply! but where i can find stock images?? and can i make it without formatting everything on it? plus when i did that i wasn't have the sd card inside it and without a sim card also

i found on the web that i need to install default kernel.. i did that and put it to bootloader in Odin and the operation succeed but now i am facing looping on Samsung logo with yellow triangle ... see the picture.. it always loop can't do anything tried recovery mode download mode but nothing.. is there any fast solution please? i beg you guys please

Try to wipe everything trough recovery, and flash another rom.

Just google for Heimdall recovery

Does Heimdall perform anything different than Odin?

try to install leaked original rom ics for gs2. i try it and yellow triangle is out

No download mode, no recovery, detected by odin, not kies

Hi,
I rooted my brandnew GT-P3110 with cf, flashed pacman and cwm recovery. I do not blame anybody alse for my issues but myself. I guess I messed up the restoring of NON-system-apps:
After a day of troublefree use the tablet randomly rebooted and came back with the message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.". No booting into recovery possible, no booting into download mode, no regular boot. Just the same message over and over again. Battery is unremovable.
I installed Kies, updated it, it downloaded drivers but under "emergency recovery" my tablet didn't appear. I then followed the "Firmware Upgrade and Initialization" procedure wich downloaded the necessary files but aborted with a korean text shown in the attachment after replugging the tablet. I tried this with 2 different USB-cables on several USB-ports. Kies btw asked me to remove the battery (not possible) after entering device number and serial-number. I turned off by pressing the off button instead and it turned on again.
I uninstalled Kies, rebooted, installed the samsung drivers manually, rebooted. I installed odin 1.85 (and later 1.3) and downloaded my contry's stock firmware (and later a newer version of the same firmware and another country's stock) from sammobile. I tried to flash them first without "repartition" ticked, later with it ticked but without a pit file (i can't find it!). I got four different errors, two are attached, the third was somethign like "cant write (line 1876)" and "cant write (line 1440)".I tried three stock firmwares with two version of odin with two USB cords on everal ports on ONE computer. I remove the tablet every time, exited odin every time, run it as admin, disabled firewall, xp-antispy and antivirus. I'm on Windows 7.
Besides a million other threads I found this one, but I wasn't able to solve my issue with it: http://forum.xda-developers.com/showthread.php?t=1652398
For 48 hours i tried to solve this problem by myself. Now I hope to find out if there's a point in continuing or if I can give up and throw away the piece of samsung.
Cheers,
404

android404 said:
Hi,
I rooted my brandnew GT-P3110
404
Click to expand...
Click to collapse
Try odin 1.61 1.85 sometimes itll jar it loose

vizionforever said:
Try odin 1.61 1.85 sometimes itll jar it loose
Click to expand...
Click to collapse
I am having the same problem with a P5113. Started with stuck at the Samsung logo. Then I tried a flash from Odin that didn't work. That led to the "Firmware error" screen telling me to use Keis. Keis fails to find the tablet. Odin still sees it but doesn't get a good write.
Now all I get is the battery icon when plugged in but that's it.
Things I have tried:
1) Two versions of Odin
2) Different USB ports
3) Different PC
I also let the device sit over the weekend to completely discharge. Still nothing.
Did you (or anyone else) resolve this issue?

vizionforever said:
Try odin 1.61 1.85 sometimes itll jar it loose
Click to expand...
Click to collapse
Thanks but it didn't work.
wd5gnr said:
I am having the same problem with a P5113. Started with stuck at the Samsung logo. Then I tried a flash from Odin that didn't work. That led to the "Firmware error" screen telling me to use Keis. Keis fails to find the tablet. Odin still sees it but doesn't get a good write.
Now all I get is the battery icon when plugged in but that's it.
Things I have tried:
1) Two versions of Odin
2) Different USB ports
3) Different PC
I also let the device sit over the weekend to completely discharge. Still nothing.
Did you (or anyone else) resolve this issue?
Click to expand...
Click to collapse
Mine is still bricked. Good luck.

facing same problem in my samsung tab 2 p3100 after root

wd5gnr said:
I am having the same problem with a P5113. Started with stuck at the Samsung logo. Then I tried a flash from Odin that didn't work. That led to the "Firmware error" screen telling me to use Keis. Keis fails to find the tablet. Odin still sees it but doesn't get a good write.
Now all I get is the battery icon when plugged in but that's it.
Things I have tried:
1) Two versions of Odin
2) Different USB ports
3) Different PC
I also let the device sit over the weekend to completely discharge. Still nothing.
Did you (or anyone else) resolve this issue?
Click to expand...
Click to collapse
Dude had the same issue on my galaxy S2 and resolved it. I downloaded the
The .pit file for my gt-i9100g (http://data.hu/get/4697903/omap4_all_20110627_emmc.pit)
The stock ROM from sammobile. (http://www.sammobile.com/firmwares/2/)
The JB Bootloader
The stock JB kernel.
Opened odin v1.85.
Then i used the vol down+home+lock keys together to try to open the download mode ( but ended up in the "Firmware error " page) and connected phone to the pc. It shows "Added!" in the message box.
Repartition with the .pit and it will reboot.
Disconnect
Get into download mode and install the bootloader and it should reboot when done. Disconnect.
Get into download mode and connect
Installed the kernel through odin and reboot
Download mode again and install the ROM through odin.
If the phone gets stuck in boot loop (samsung logo over and over),
get into recovery mode ( for s2, vol up+home+lock, it needs to be pressed intermittently)
Then do a full format along with wipe cache.
And then the phone finally booted completely. :laugh: . Good Luck.
Note: I'm not sure to boot into recovery and download are the same key combos as it was for the i9100g.

novjean said:
Dude had the same issue on my galaxy S2 and resolved it. I downloaded the
The .pit file for my gt-i9100g (http://data.hu/get/4697903/omap4_all_20110627_emmc.pit)
Click to expand...
Click to collapse
Thanks. Well, I understand the theory. I have had trouble finding a PIT file that I am sure is for my device. I did save a PIT file but I think it is corrupt because using it requires me to let the battery die afterwards to get back to download mode. Same for the bootloader. I have a few things I've tried, but not sure I have one that is exactly for the GT-P5113 (in fact, I never did find a JB for the 5113 just the 5110 and it never would load).

Well no amount of coaxing has put life back into the tab
I may try again out of curiosity, but rather than invest more time I went out and bought a 32G Nexus 7 (2013 version). I would still like to get the Galaxy Tab alive again -- it has corrupted the flash twice before and each time I was able to bring it back to life. Not sure if this is an actual hardware failure or if it is just beyond partitioning.
I have a feeling if I had the right PIT and the right bootloader I could get back in business.

I can do each thing you mentioned, but my device is not getting detected by my PC. When I insert USB it says USB not recognized and it is not detected by Odin, adb and anything else. I am stuck on Boot Logo for my P3100 and when I go into recovery, it says USB not recognized. Fully messed up. Can you help me out here.
novjean said:
Dude had the same issue on my galaxy S2 and resolved it. I downloaded the
The .pit file for my gt-i9100g (http://data.hu/get/4697903/omap4_all_20110627_emmc.pit)
The stock ROM from sammobile. (http://www.sammobile.com/firmwares/2/)
The JB Bootloader
The stock JB kernel.
Opened odin v1.85.
Then i used the vol down+home+lock keys together to try to open the download mode ( but ended up in the "Firmware error " page) and connected phone to the pc. It shows "Added!" in the message box.
Repartition with the .pit and it will reboot.
Disconnect
Get into download mode and install the bootloader and it should reboot when done. Disconnect.
Get into download mode and connect
Installed the kernel through odin and reboot
Download mode again and install the ROM through odin.
If the phone gets stuck in boot loop (samsung logo over and over),
get into recovery mode ( for s2, vol up+home+lock, it needs to be pressed intermittently)
Then do a full format along with wipe cache.
And then the phone finally booted completely. :laugh: . Good Luck.
Note: I'm not sure to boot into recovery and download are the same key combos as it was for the i9100g.
Click to expand...
Click to collapse

2 years later .... did you ever unbrick this? I'm dealing with a P5113 now that's stuck at the "Firmware upgrade encountered an issue" screen. <sigh>
wd5gnr said:
Well no amount of coaxing has put life back into the tab
I may try again out of curiosity, but rather than invest more time I went out and bought a 32G Nexus 7 (2013 version). I would still like to get the Galaxy Tab alive again -- it has corrupted the flash twice before and each time I was able to bring it back to life. Not sure if this is an actual hardware failure or if it is just beyond partitioning.
I have a feeling if I had the right PIT and the right bootloader I could get back in business.
Click to expand...
Click to collapse

No. I finally sent it to one of these ebay guys who will JTAG it since I was too lazy to wire up one of my JTAG probes. They worked on it and said it was simply dead and the only alternative would be to replace the flash chips.
Bought a Nexus 7.

I've got the pit files for P311x and P3100 on my website https://sites.google.com/site/jrc2swebsite/downloads/samsung-galaxy-tab-2-70-p31xx

[Q] tab 2 7.0 P3110 stuck at Samsung Tab 2 7.0 screen unable to boot to recovery

Please can you help I bought this samsung tab 2 7.0 P3110 with it only powering on to the samsung tab 2 7.0 logo screen.
I am unable to get to recovery screen using the power and the vol up button all this does is power it off even if I hold for over one minute.
I can get to the download screen (power and vol down doing so is easy as it works) I have been able to use odin (failed many times) and download firmwares.
Last night I was able to download and gain a pass in Odin for CF-Auto-Root-espressowifi-espressowifixx-gtp3110 this I ran fist then 4.1.1 P3110XXCLK7_P3110OXACLK7_BTU. the problem after that is when odin tells it to reboot it hangs at the logo screen everytime. I have tried without the reboot and reboot manually it staill hangs.
is it a bootloader problem? corrupted partition? I think it needs the whole boot process reinstalled or rewritten if someone knows how
I am not looking for a custom rom All i want it to do is to power on into the stock recovery and to power on into the sofware by using something that works either by reformat or re partition the tab to get that part of the tab working before looking at firmware. sometime I have seen write fail when in odin.
simple instructions for how to get it back is all I am looking for.
I have browsed your site and watched youtube for hours no light at the end of the tunnel
thanks in advance for your help

tab 2 7.0 P3110 stuck at Samsung Tab 2 7.0 screen unable to boot to recovery
tab2noob said:
Please can you help I bought this samsung tab 2 7.0 P3110 with it only powering on to the samsung tab 2 7.0 logo screen.
I am unable to get to recovery screen using the power and the vol up button all this does is power it off even if I hold for over one minute.
I can get to the download screen (power and vol down doing so is easy as it works) I have been able to use odin (failed many times) and download firmwares.
Last night I was able to download and gain a pass in Odin for CF-Auto-Root-espressowifi-espressowifixx-gtp3110 this I ran fist then 4.1.1 P3110XXCLK7_P3110OXACLK7_BTU. the problem after that is when odin tells it to reboot it hangs at the logo screen everytime. I have tried without the reboot and reboot manually it staill hangs.
is it a bootloader problem? corrupted partition? I think it needs the whole boot process reinstalled or rewritten if someone knows how
I am not looking for a custom rom All i want it to do is to power on into the stock recovery and to power on into the sofware by using something that works either by reformat or re partition the tab to get that part of the tab working before looking at firmware. sometime I have seen write fail when in odin.
simple instructions for how to get it back is all I am looking for.
I have browsed your site and watched youtube for hours no light at the end of the tunnel
thanks in advance for your help
Click to expand...
Click to collapse
forgot to add the above was using Odin 3.07 and laptop is win 7. did try pc on xp and failed loads.

tab2noob said:
forgot to add the above was using Odin 3.07 and laptop is win 7. did try pc on xp and failed loads.
Click to expand...
Click to collapse
I am not too sure about the partition/repartition thing, but I think you should use said Odin to flash CWM 6.0.45. It doesn't mean you have to install a ROM, but try attempting a factory reset (at this point, not being able to boot up, you might need to use Cwm to create some sort of backup).
However, I suggest waiting until you receive more than one reply, as I may be wrong

For going into recovery, try holding the buttons at the same time. When you see the first samsung bootscreen, release the power button and continue to hold the other button.

jccarbon said:
I am not too sure about the partition/repartition thing, but I think you should use said Odin to flash CWM 6.0.45. It doesn't mean you have to install a ROM, but try attempting a factory reset (at this point, not being able to boot up, you might need to use Cwm to create some sort of backup).
However, I suggest waiting until you receive more than one reply, as I may be wrong
Click to expand...
Click to collapse
Hi thanks for your suggestion. I am thinking until I can get to the recovery screen putting on firmware isnt getting tab into recovery

tab 2 7.0 P3110 unable to boot into recovery or past samsung tab 2 7.0 screen
swrght13 said:
For going into recovery, try holding the buttons at the same time. When you see the first samsung bootscreen, release the power button and continue to hold the other button.
Click to expand...
Click to collapse
Thanks for your reply I probably didnt explain myself. I have always been holding down the power and the vol up button at the same time.
I have access to another tab 2 7.0 P3110 that is working in stock mode (a trusted friend allowed me to check how to get to the download and recovery screens ) I have noted the time it takes to boot into recovery from power off and from the samsung tab 2 7.0 screen and also going into recovery from the download screen. mine dont do any it just goes to the download screen or power off. the screen is black no life lol.
just a thought I dont think it actually powers off although the screen is black because I left it for over 10 hours I felt the back and it was warm battery was low as I couldnt power it on it was fully charged when I tried to get into recovery 10 hours earlier.
will try to explain one step at a time
because of the problem I am thinking I have to start from scratch instead of jumping into the middle of what is already possibly corrupt files. (I have probably built a house out of my bricked Tab)
1. what do I have to do to get a totally clean 8gb space for recovery and firmware to go onto?
2. what has to be installed via Odin to get to recovery (can recovery be tested on its own before the firmware is installed)
3. I have tried a PIT file before all I had was 0 completed and 0 failed???? is that good or bad? didnt see a PASS at the top left. did I have the correct PIT file?
4. are PIT files dependant on which version of Odin I run or recovery or firmware? if they are can someone point my in the right direction for everything that is compatible with each other
I read on this forum of splitting the MD5 files into bootloader pit by extracting it twice I tried that in winRAR I only had one chance it left a tar.md5 file which is the file I used to upload in Odin.
Thanks again for everyones help

2. You need to install Clockwork Mod Recovery version 6.0.4.5. It can be found in the development forum, made by Android-Andi
As for the rest, I'm not familiar

jccarbon said:
2. You need to install Clockwork Mod Recovery version 6.0.4.5. It can be found in the development forum, made by Android-Andi
As for the rest, I'm not familiar
Click to expand...
Click to collapse
I have tried the above it passes and reboots to samsung tab 2 7.0 and thats as far as it goes. I waited 15 minutes no change tried the usual to get into recovery not happening. went back to download screen and ran gtab2P311x8g.pit below is a snippet of the important bits from Odin output screen bottom left I had auto reboot, repartition and f reset time all selected
set pit file
get pit for mapping
theres no pit for mapping
all threads completed succeed 0 failed 1
I have also ran philz touch 6.008 universal root also pass with reboot and without reboot
all tar md5 files installs and with a pass reboots but no blue bar on the bottom of download screen and no access to recovery screen.
I think the internal 8gb memory needs to be wiped and partitioned.
maybe someone can tell me how to extract all the files that are needed to get the os onto the tab from the tar md5 file like the partition, recovery and bootloader etc and the order of installing in Odin

tab2noob said:
I have tried the above it passes and reboots to samsung tab 2 7.0 and thats as far as it goes. I waited 15 minutes no change tried the usual to get into recovery not happening. went back to download screen and ran gtab2P311x8g.pit below is a snippet of the important bits from Odin output screen bottom left I had auto reboot, repartition and f reset time all selected
set pit file
get pit for mapping
theres no pit for mapping
all threads completed succeed 0 failed 1
I have also ran philz touch 6.008 universal root also pass with reboot and without reboot
all tar md5 files installs and with a pass reboots but no blue bar on the bottom of download screen and no access to recovery screen.
I think the internal 8gb memory needs to be wiped and partitioned.
maybe someone can tell me how to extract all the files that are needed to get the os onto the tab from the tar md5 file like the partition, recovery and bootloader etc and the order of installing in Odin
Click to expand...
Click to collapse
Help needed anybody somebody.
I have tried with Heimdall and ADB not working. Now back to Odin

tab2noob said:
Help needed anybody somebody.
I have tried with Heimdall and ADB not working. Now back to Odin
Click to expand...
Click to collapse
Am now running with Odin 3.07 and CF Auto Root espressowifi....md5
it all run through with pass at the end. It doesnt show the blue line running across the bottom of the download screen on the tab. I have never seen this in all the 20 + times I have tried with Odin. All the you tube vids show this as part of the installation process. If I have auto reboot on the tab reboots when Odin send the request to the tab to reset.

tab2noob said:
Am now running with Odin 3.07 and CF Auto Root espressowifi....md5
it all run through with pass at the end. It doesnt show the blue line running across the bottom of the download screen on the tab. I have never seen this in all the 20 + times I have tried with Odin. All the you tube vids show this as part of the installation process. If I have auto reboot on the tab reboots when Odin send the request to the tab to reset.
Click to expand...
Click to collapse
ADB devices does not attach itself to the tab. ADB just says its waiting for device when in download mode and fastboot returns nothing. I think its because I am unable to run USB debugging due to no firmware.
Is there a way to get into the tab if theres no os?
I have taken the back off thinking the volume or power key might be faulty, there not. Pressing the power button and the up vol does nothing apart from putting the tab in a reboot loop or power off. I can get into download mode no prob. I have tried pressing the up and down vol keys with the power button to try to put the tab into shock no change.

I was searching the forum for a similar problem as mine.
And you have the exact same problem as I do.
At some point when I used Odin 3.07 and flashing an official firmware from samsung I got past the first boot screen.
But right after that it shows an android robot with a dedacahedron in front of it showing an animation and a loading bar.
Soon I discovered the next loop, since this animation would loop over and over again.
Now I waited for the battery to run out and charge it up till its full.
By the way:
When the tablet is off and I plug it in with the original cable and charger the tablet shows the battery icon, but it doesnt show the charging animation. The battery icon shows a "waiting" circle. So I cant really see if its charging or not.
Have you had any progress?
Would be so awesome to fix this, this galaxy tab is not mine. Its my brothers and I broke it by trying to root it and install cwm xD

Eureka
Dude I totally got into recovery mode.
I downloaded CWM (clockwordmod) 6.0.1.1 SuperSU 0.96 Busybox 1.2.0.2 md5 file.
You can find it here:
http://forum.xda-developers.com/showthread.php?t=1880010
In the first post there are attached files.
The right one is in that list.
Then I tried flashing it with Odin3 Version 3.09
I googled for a newer version of Odin and found this version 3.09
First time rebooting didnt work.
But the seccond time I succesfully got into CWM recovery.
Hope this works for you 2!
Cheers.

Amlan90 said:
Dude I totally got into recovery mode.
I downloaded CWM (clockwordmod) 6.0.1.1 SuperSU 0.96 Busybox 1.2.0.2 md5 file.
You can find it here:
http://forum.xda-developers.com/showthread.php?t=1880010
In the first post there are attached files.
The right one is in that list.
Then I tried flashing it with Odin3 Version 3.09
I googled for a newer version of Odin and found this version 3.09
First time rebooting didnt work.
But the seccond time I succesfully got into CWM recovery.
Hope this works for you 2!
Cheers.
Click to expand...
Click to collapse
Thanks for the detailed guide and everyone's responses.. I was SOL also and re-flashing CWM helped get me back to where I can flash again.

Trying to recover bricked P5113 for friend

I haven't been on the xda forums since the early WP7 days but im back now with a android question.
My friend bricked her p5113 and I thought I may be able to fix it. But Im a little confused with all the different things that need to be done to flash a stock rom on an android. Flash Kernel, mobile odin, which firmware, which rom etc
Right now I get stuck on the "WARNING custom rom installation screen, volume down to download a custom rom, volume up to restart phone" screen. My computer will not recognize the device. Once I got my computer to make the device connected noise but then immediately after it made the device disconnected noise and kept repeating.
Can someone point me in the correct direction here? I just want to restore it back to factory settings.
THANKS

What happened that it bricked? tryed to flash a stockrom using odin?
maybe try drivers from here:
Microsoft Windows XP / Vista / 7 / 8 - x86 / x64
Version: 1.5.27.0
Date: 21. Juni 2013
Source: taken from KIES 2.6.0.13074_14_00
14,6 MiB (15.365.072 Bytes)
MD5: AB24028EBA28A444D9BCC9E836C6FF40
Download: via ZippyShare

Android-Andi said:
What happened that it bricked? tryed to flash a stockrom using odin?
maybe try drivers from here:
Microsoft Windows XP / Vista / 7 / 8 - x86 / x64
Version: 1.5.27.0
Date: 21. Juni 2013
Source: taken from KIES 2.6.0.13074_14_00
14,6 MiB (15.365.072 Bytes)
MD5: AB24028EBA28A444D9BCC9E836C6FF40
Download: via ZippyShare
Click to expand...
Click to collapse
Not sure what did it. She said she turned it on one day and it was like that. I more of a windows guy so im not really familiar with the android setups.

Floods7 said:
I haven't been on the xda forums since the early WP7 days but im back now with a android question.
My friend bricked her p5113 and I thought I may be able to fix it. But Im a little confused with all the different things that need to be done to flash a stock rom on an android. Flash Kernel, mobile odin, which firmware, which rom etc
Right now I get stuck on the "WARNING custom rom installation screen, volume down to download a custom rom, volume up to restart phone" screen. My computer will not recognize the device. Once I got my computer to make the device connected noise but then immediately after it made the device disconnected noise and kept repeating.
Can someone point me in the correct direction here? I just want to restore it back to factory settings.
THANKS
Click to expand...
Click to collapse
You need to install Samsung Kies on the pc for the correct driver. Be sure to keep Kies closed when flashing through Odin.
Sent from my GT-P5100 using XDA Premium 4 mobile app

Im just not sure of the process and in what order they go in.
I can look up all the downloads but can someone tell me what order to do all the steps in ?

Floods7 said:
Im just not sure of the process and in what order they go in.
I can look up all the downloads but can someone tell me what order to do all the steps in ?
Click to expand...
Click to collapse
The first thing to try is a factory reset. If you hold the power and volume down button (volume up on most other Samsung Android devices), you will enter recovery mode (which is not the download mode you describe in your first post). You can navigate with the volume buttons and enter with the power button. Navigate to the factory reset option and press enter. You will lose all data on the internal sd card.
If that doesn't work, you can try to flash the original firmware through Odin. There are many step by step tutorials on the internet and YouTube, so no need for me to elaborate here. Download the firmware here: http://www.sammobile.com/firmwares/. It is a generic process for all Samsung devices, so not Tab specific.
Sent from my GT-P5100 using XDA Premium 4 mobile app

eejee said:
The first thing to try is a factory reset. If you hold the power and volume down button (volume up on most other Samsung Android devices), you will enter recovery mode (which is not the download mode you describe in your first post). You can navigate with the volume buttons and enter with the power button. Navigate to the factory reset option and press enter. You will lose all data on the internal sd card.
If that doesn't work, you can try to flash the original firmware through Odin. There are many step by step tutorials on the internet and YouTube, so no need for me to elaborate here. Download the firmware here: http://www.sammobile.com/firmwares/. It is a generic process for all Samsung devices, so not Tab specific.
Sent from my GT-P5100 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks so much for the info. But im still having problems. I got odin running and it connected. but now im in "Firmware upgrade encountered an issue" screen and cant get anywhere else. I started odin and the first time it said "RESTART!" so I restarted and ran it again, this time it said PASS! but im still stuck on the "Firmware upgrade encountered an issue" screen and cant get anywhere else" screen. Whats my next move lol ??

and btw, I cannot enter download mode

Floods7 said:
Thanks so much for the info. But im still having problems. I got odin running and it connected. but now im in "Firmware upgrade encountered an issue" screen and cant get anywhere else. I started odin and the first time it said "RESTART!" so I restarted and ran it again, this time it said PASS! but im still stuck on the "Firmware upgrade encountered an issue" screen and cant get anywhere else" screen. Whats my next move lol ??
Click to expand...
Click to collapse
Where do you get that screen? Odin, Kies, phone? Remember that Kies should be installed, but not active. To be sure, also stop the Kies entries in Windows task manager.
Sent from my GT-I9505 using XDA Premium 4 mobile app

eejee said:
Where do you get that screen? Odin, Kies, phone? Remember that Kies should be installed, but not active. To be sure, also stop the Kies entries in Windows task manager.
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I get that screen on odin. I have tried running kies but it never connects.

Floods7 said:
I get that screen on odin. I have tried running kies but it never connects.
Click to expand...
Click to collapse
That Kies never connects doesn't mean anything: in the past six years I almost never got it to work and I never use it. Besides, it doesn't work anyway if a custom rom has been installed, which is understandable. You just have to have it on your pc because of the USB driver.
Did you try the factory reset in recovery mode that I mentioned earlier?
Are you sure you've downloaded the correct firmware?
Is the present installation stock firmware or a custom rom?
Have you tried different USB ports?
Sent from my GT-P5100 using XDA Premium 4 mobile app

eejee said:
That Kies never connects doesn't mean anything: in the past six years I almost never got it to work and I never use it. Besides, it doesn't work anyway if a custom rom has been installed, which is understandable. You just have to have it on your pc because of the USB driver.
Did you try the factory reset in recovery mode that I mentioned earlier?
Are you sure you've downloaded the correct firmware?
Is the present installation stock firmware or a custom rom?
Have you tried different USB ports?
Sent from my GT-P5100 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried the factory reset method. Was not able to get that working. At one point I was able to get to the odin download screen, so I tried to flash, it said pass, but did not work. Now I cant get to the odin download screen at all, all I can get is the "Firmware upgrade encountered an issue" screen and cant get anywhere else" screen. Literally no other screen than that one. I thought I used the correct firmware but im not on the same computer right now so I cant check. Can someone point me to the correct firmware? Am I skipping any steps?
I turn the tablet on and get to the "Firmware upgrade encountered an issue" screen and cant get anywhere else" screen. Connect to odin, the device is detected by odin and then i begin to flash. I usually gets stuck when odin says to "RESTART".

"Firmware upgrade encountered an issue" = Black-Screen-Of-Death, download-mode running in background, flashing with Odin will work there.
Maybe uncheck "Auto-Reboot" in Odin, if Odin says "Pass!" Wait 1 Minute to be sure. Now reboot directly into recovery, restart the device from there and see if it works.

Maybe you could try another version of Odin. That worked for me when i got stuck with my tab

Android-Andi said:
"Firmware upgrade encountered an issue" = Black-Screen-Of-Death, download-mode running in background, flashing with Odin will work there.
Maybe uncheck "Auto-Reboot" in Odin, if Odin says "Pass!" Wait 1 Minute to be sure. Now reboot directly into recovery, restart the device from there and see if it works.
Click to expand...
Click to collapse
I have tried a few versions of odin. I got one to work and it said pass, then went to restart and I could not restart the device.

[Q] Am I bricked err?

I got my GNP 12.2 (SM-P900) a few weeks ago and just tried to root it using Odin and download.chainfire.eu/384/CF-Root/CF-Auto-Root/CF-Auto-Root-v1awifi-v1awifixx-smp900.zip
However it paused at cache.img and after 10 minutes or so it just failed.
I've tried it a few times, but same thing, and on start up all I get is "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I tried Kies 3 and Kies 2.6 but they both say my device is not supported, even if I try to go into Tools and do it it says the model name is incorrect and doesn't even give me an option to enter the serial number :-\
I looked around for a stock ROM but the closest I could find was the P901 and P905 (But I am the P900)
I don't really know what to do, so any advice would be much appreciated :angel:

Actually got Kies working, was just entering the model # wrong
This could probably be deleted / etc, not really sure how to do that

jns20 said:
Actually got Kies working, was just entering the model # wrong
This could probably be deleted / etc, not really sure how to do that
Click to expand...
Click to collapse
bump?
I'm having the same exact issue. I can get it into download mode. I've tried Kies several times and it keeps failing. Originally, I was using odin 3.07 to auto root on the sm-p900. During the process, the screen got this weird rainbow pixelated look, and odin told me the process has failed. It is now stuck on the error message "Firmware update has encountered an issue..."
Now I'm not really sure what to do. I've tried to reboot from download mode, and that sends me right back to the error message.
Any ideas?

ChampagneFerret said:
bump?
I'm having the same exact issue. I can get it into download mode. I've tried Kies several times and it keeps failing. Originally, I was using odin 3.07 to auto root on the sm-p900. During the process, the screen got this weird rainbow pixelated look, and odin told me the process has failed. It is now stuck on the error message "Firmware update has encountered an issue..."
Now I'm not really sure what to do. I've tried to reboot from download mode, and that sends me right back to the error message.
Any ideas?
Click to expand...
Click to collapse
IIRC you need to reflash recovery and you should be able to boot up again.

muzzy996 said:
IIRC you need to reflash recovery and you should be able to boot up again.
Click to expand...
Click to collapse
I'm sorry if I sound stupid but how do I reflash the recovery? I keep searching for a recovery ROM but I can't find anything, so I must be misunderstanding something here.

ChampagneFerret said:
I'm sorry if I sound stupid but how do I reflash the recovery? I keep searching for a recovery ROM but I can't find anything, so I must be misunderstanding something here.
Click to expand...
Click to collapse
TWRP 2.7.0.0 is available now! http://forum.xda-developers.com/showthread.php?t=2706982 :good:

icem237 said:
TWRP 2.7.0.0 is available now! http://forum.xda-developers.com/showthread.php?t=2706982 :good:
Click to expand...
Click to collapse
Thank you very much. In case anyone else is wondering. I ended up asking the problem with Samsung kies, using the upgrade feature rather than emergency recovery. Wiped all my data but u have my tablet back.
Kind of wondering what went wrong with the root attempt. I followed the instructions to the T.

ChampagneFerret said:
Kind of wondering what went wrong with the root attempt. I followed the instructions to the T.
Click to expand...
Click to collapse
Did you use Odin 3.0.7 or 3.0.9? 3.0.7 is included with CF and MUST be used even though 3.0.9 is the latest. If odin was already installed on your PC and you used 3.0.9 bad things are going to happen.

ChampagneFerret said:
Thank you very much. In case anyone else is wondering. I ended up asking the problem with Samsung kies, using the upgrade feature rather than emergency recovery. Wiped all my data but u have my tablet back.
Kind of wondering what went wrong with the root attempt. I followed the instructions to the T.
Click to expand...
Click to collapse
I myself have tried odin 3.07 and .09 and mine just hangs when cache is being written to. A full green bar but will not move pass the cache portion of the install.

icem237 said:
I myself have tried odin 3.07 and .09 and mine just hangs when cache is being written to. A full green bar but will not move pass the cache portion of the install.
Click to expand...
Click to collapse
I tried both as well, and that's exactly what happened to me. During the process, my screen went all screwy and that's when it told me the process had failed.

I had some of the problems mentioned above. My attempt to flash CF-Auto-Root-v1awifi-v1awifixx-smp900.tar.md5 failed using Odin3-v3.07.exe.
It tries for several minutes and then says failed.
I then used Kies (not Kies 3) to reflash the tablet to factory settings. Here its important to know that Kies will never "connect" you have to ignore that and go to tools and "firmware upgrade and initialization". Google "Firmware upgrade encountered an issue” – Got This Error While", the first result on "droidviews" is the guide i used to fix this.
I then went into the settings and enabled "USB Debugging". Something i had forgotten before. I tried to flash the root file again, but it still failed.
Given that i was able to reflash the firmware with kies, i would say my USB port / cable / drivers must all be good.
What else should i try?

Flash Stock Recovery
davschm said:
I had some of the problems mentioned above. My attempt to flash CF-Auto-Root-v1awifi-v1awifixx-smp900.tar.md5 failed using Odin3-v3.07.exe.
It tries for several minutes and then says failed.
I then used Kies (not Kies 3) to reflash the tablet to factory settings. Here its important to know that Kies will never "connect" you have to ignore that and go to tools and "firmware upgrade and initialization". Google "Firmware upgrade encountered an issue” – Got This Error While", the first result on "droidviews" is the guide i used to fix this.
I then went into the settings and enabled "USB Debugging". Something i had forgotten before. I tried to flash the root file again, but it still failed.
Given that i was able to reflash the firmware with kies, i would say my USB port / cable / drivers must all be good.
What else should i try?
Click to expand...
Click to collapse
For those getting stuck or failing root, Make sure your usb drivers are updated in Kies 3 then flash stock recovery in Odin 3.07. Don't get mixed up with stock firmware (over 1GB) and stock recover (only around 20MB).
Stock recovery is here:
http://download.chainfire.eu/384/CF-Root/CF-Auto-Root/CF-Auto-Root-v1awifi-v1awifixx-smp900.zip
Thread is here:
http://forum.xda-developers.com/showthread.php?p=50492301&nocache=1

Russbad said:
For those getting stuck or failing root, Make sure your usb drivers are updated in Kies 3 then flash stock recovery in Odin 3.07. Don't get mixed up with stock firmware (over 1GB) and stock recover (only around 20MB).
Stock recovery is here:
http://download.chainfire.eu/384/CF-Root/CF-Auto-Root/CF-Auto-Root-v1awifi-v1awifixx-smp900.zip
Thread is here:
http://forum.xda-developers.com/showthread.php?p=50492301&nocache=1
Click to expand...
Click to collapse
Question, what is the purpose of the Stock recovery and CWM recovery?
Also, after trying three times, i was able to get the flash to work. After each failier i used Kies (not kies 3) to flash back to factory. Would these recoveries have helped? Maybe i wouldn't have lost data?

davschm said:
Question, what is the purpose of the Stock recovery and CWM recovery?
Also, after trying three times, i was able to get the flash to work. After each failier i used Kies (not kies 3) to flash back to factory. Would these recoveries have helped? Maybe i wouldn't have lost data?
Click to expand...
Click to collapse
Stock recovery is what your device originally comes with. CWM recovery is a modified version of that and it allows you more functionality.
When I messed up my update and root, my device would not boot up at all. I flashed the stock recovery and that enabled me to successfully root. No data was lost, no factory reset was needed and all my apps and settings were unchanged.

Don't mean to bump this thread, but I'm having the same issue. Odin 3.07 hangs up when it gets to cache.img, and it's non-responsive. I don't care about rooting it, I just want a stock firmware back. I've tried the files that Russbad posted, same issue. Running Note Pro 12. SM-P900 on 4.4.2.

bioncorp said:
Don't mean to bump this thread, but I'm having the same issue. Odin 3.07 hangs up when it gets to cache.img, and it's non-responsive. I don't care about rooting it, I just want a stock firmware back. I've tried the files that Russbad posted, same issue. Running Note Pro 12. SM-P900 on 4.4.2.
Click to expand...
Click to collapse
Try this: With your device unplugged from your PC, open Kies 3, go to tools tab and uninstall the drivers. Then plug your device in and reinstall drivers.
I don't know if it makes a difference but if you get your device to boot up, enable developer options and check USB debugging.
Also make sure you are using the cables that came with your Tablet.
Then flash stock recovery and flash stock firmware.
If it still fails, check that your downloaded firmware and recovery are not corrupted, download them again.
Also try these procedures using different USB ports.
Good luck!

Russbad said:
Try this: With your device unplugged from your PC, open Kies 3, go to tools tab and uninstall the drivers. Then plug your device in and reinstall drivers.
I don't know if it makes a difference but if you get your device to boot up, enable developer options and check USB debugging.
Also make sure you are using the cables that came with your Tablet.
Then flash stock recovery and flash stock firmware.
If it still fails, check that your downloaded firmware and recovery are not corrupted, download them again.
Also try these procedures using different USB ports.
Good luck!
Click to expand...
Click to collapse
I found the issue, it should work with everyone with it. Some people don't have the .md5 extension enabled in their archive viewer, so by simply removing the .md5 (left with CF_XXXX.tar), and flashing that it works 100% fine.

bioncorp said:
I found the issue, it should work with everyone with it. Some people don't have the .md5 extension enabled in their archive viewer, so by simply removing the .md5 (left with CF_XXXX.tar), and flashing that it works 100% fine.
Click to expand...
Click to collapse
I finally got mine rooted by simply trying over and over. I re-downloaded the CF flash tool and used 7zip to extract it several times, and used a different usb port at least once. Not that I really thought there was a problem with my extraction or the download or my USB port. But from what i have seen posted, you just have to try it 3 or 4 (maybe even 10) times until you get lucky and it works.
I did at one point try to recover my Note 12.2 with the "recovery.img" instead of flashing it with a full factory re-image (which causes data loss) but that didn't work for me ether. But I later had good luck with using Odin 3.09 to flash TWRP. So at least I now have a good custom recovery and backup tool.

okay everyone, I'm going to try these methods and report on what happened. Thank you for being so helpful. :cyclops:

ChampagneFerret said:
okay everyone, I'm going to try these methods and report on what happened. Thank you for being so helpful. :cyclops:
Click to expand...
Click to collapse
FINALLY! :laugh: I got it to root!
I ended up using a different computer in the end and used Kies 2.6 for the drivers. I tried this a total of maybe 8 or 9 times, and it worked on the second attempt on the second attempt.
For the record, I left "md5" in the file when rooting, and that's when it worked.