Related
Hi There,
Sorry misleading title, it's a P5100 (wifi+3G tab)
I know this has been asked many times on these forums, but I couldn't find anything to help.
Following this guide: http://forum.xda-developers.com/show....php?t=1722745
I tried to restore the P5100 to stock from CM (This is the firmware I downloadad: http://samsung-updates.com/details/1...100UBDMD2.html)
Now my device is stuck in charging boot loop. I can enter stock download mode via holding up and power on boot (however Odin 3.07 fails at the "setupConnection" and Odin 1.85 fails at Can't open the specified file. (Line: 1876)) I tried this on several computers.
I am able to turn the device of when it's plugged in to power, it then goes to the battery charging screen and if I take out the power the device remains off.
I cannot enter stock recovery, maybe I am doing something wrong, but when holding the down volume and tapping the power button the device simply boots.
Any help appreicated
Think you have same issue as me. I can get to download mode but not recovery, only difference is I can flash the firmware with no errors but tablet still wont boot always stuck on samsung logo and will not go to recovery either.
Have you tried a different usb cable, I also got that message few times I just rebooted it back to download mode and it fixed up after that. Good luck.
No luck
I have managed to use odin and flash a different stock firmware. Now the device simply gets stuck on the Samsung Logo on boot. How'd you fix this?
I have already tried all cwm recoveries some bootloaders and different stock firmwares. I think the chip that holds the firmware might be faulty and doesnt let the device boot up.
Anyone had same issue that can help us get a solution to this problem or at least an explanation of whats going on would be highly apreciated.
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
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.
I tried to use chainroot, and got stuck on the logo screen. normally you'd battery pull, go to recovery and wipe data. but i can't find any way to shut down the phone, before doing power-upVol-home.
And now i've tried to odin a stock recovery to undo chainroot, odin fails. could re-run odin with auto-reboot off, but again, no way to shut off and go to recovery.
at this point i'm stuck with the blue screen asking me to use smart switch on PC to do emergency recovery. but smartswitch says the device is not recognized.
thoughts? thanks!
I was stuck rooting on the boot logo too. Had to use odin 3.10 and did "run as administrator". Also if this helps to reboot the stuck phone press vol down+power together until the screen blanks out. If you need to get into download mode, as soon as the screen blanks out, press and hold the Home button ( Don't let go of the vol down and power though ).
Good grief.... the non-removable battery has made these recovery tricks so difficult
thanks twisted_mind. at this point, i only get the blue screen asking me to do smartswitch recovery, and the one thing i CAN seem to do is volDown-power-home and it easily goes to download mode. i have not been able to get to recovery mode no matter what i do (including volUp-power-home, even before this smartswitch message came up after i tried to odin a stock recovery).
so i can still go to dload mode, and stick in a stock rom. the ones i've tried are from sammobile, and a potential issue is that i don't know the exact one to pick (this phone is a demo here in europe and i didn't note the details under settings when it was working). so the ones i try end in an odin FAIL. again, i've also tried odin unchecking auto-reboot, but then the phone is stuck at the very end of dload ("don't turn off target", etc), and i have no way to battery pull, etc.
Instead of holding power to shut off you have to hold power and vol down
jasonastley said:
I tried to use chainroot, and got stuck on the logo screen. normally you'd battery pull, go to recovery and wipe data. but i can't find any way to shut down the phone, before doing power-upVol-home.
And now i've tried to odin a stock recovery to undo chainroot, odin fails. could re-run odin with auto-reboot off, but again, no way to shut off and go to recovery.
at this point i'm stuck with the blue screen asking me to use smart switch on PC to do emergency recovery. but smartswitch says the device is not recognized.
thoughts? thanks!
Click to expand...
Click to collapse
Hello
I'm stucked on the same corner, i used Chainroot with odin 3.10.6 with no luck, just as what
happened with you, my S6 international module stucked on logo screen.
where did you get S6 stock recovery from?
Thanks
ktetreault14 said:
Instead of holding power to shut off you have to hold power and vol down
Click to expand...
Click to collapse
I have the turquoise screen that says "an error has occurred... use the emergency recovery function in smart switch...". if i do power + volDown there OR when the phone is stuck in download mode after the odin fail, the phone turns off but then comes right back on with the turquoise error screen. i've tried quickly going to the recovery key combo right when or right after the screen goes dark, but to no avail.
I can easily do power +volDown + home and go to dload mode. i just can't get into recovery mode no matter what i've tried so far.
if i could just find a stock rom that wouldn't fail in odin, or something else to use as AP/PDA in odin, i'd be set i think. wish i knew how to do this. hitting nand erase all in odin doesn't do the trick by the way.
ammsamm said:
Hello
I'm stucked on the same corner, i used Chainroot with odin 3.10.6 with no luck, just as what
happened with you, my S6 international module stucked on logo screen.
where did you get S6 stock recovery from?
Thanks
Click to expand...
Click to collapse
got the stock rom from the sammobile site. but a problem is that they have many rom's listed for the G925F and i am not certain which variety i have, or if that matters: http://www.sammobile.com/firmwares/database/SM-G925F/
jasonastley said:
got the stock rom from the sammobile site. but a problem is that they have many rom's listed for the G925F and i am not certain which variety i have, or if that matters
Click to expand...
Click to collapse
I managed to root my G920F after "odin flashing" the UK version from Sammobile, release date 11-4-2015,
Then i flashed back the CF-Auto-Root.
Know my device is booting fine and rooted
ammsamm said:
I managed to root my G920F after "odin flashing" the UK version from Sammobile, release date 11-4-2015,
Then i flashed back the CF-Auto-Root.
Know my device is booting fine and rooted
Click to expand...
Click to collapse
is the version you flashed the same version that you had prior (do the apps look the same, etc)?
so odin passed? (mine FAILs, with 4 different sammobile stock recoveries). I have the S6 Edge, maybe the S6 works fine and I just need the correct S6 Edge firmware.
jasonastley said:
is the version you flashed the same version that you had prior (do the apps look the same, etc)?
so odin passed? (mine FAILs, with 4 different sammobile stock recoveries). I have the S6 Edge, maybe the S6 works fine and I just need the correct S6 Edge firmware.
Click to expand...
Click to collapse
No its not the same version, mine was G920FZDAXSG and i flashed G920FXXU1AOCV, its a UK version, some Version
store apps was pre installed in the rom nothing more.
Odin passed normally with no issue.
i used two identical Odin v3.10.6 versions the second one i used is the one i flashed the rom and the root with.
Download the odin from this link:
samsungodindownload. com
ammsamm said:
No its not the same version, mine was G920FZDAXSG and i flashed G920FXXU1AOCV, its a UK version, some Version
store apps was pre installed in the rom nothing more.
Odin passed normally with no issue.
i used two identical Odin v3.10.6 versions the second one i used is the one i flashed the rom and the root with.
Download the odin from this link:
samsungodindownload. com
Click to expand...
Click to collapse
umm, hey ammsamm, i went to the link you just mentioned, installed it and GOT SOME NASTY SPAMWARE INSTALLED on my machine from it. I'd normally flag you immediately as a bad user, but your other comments sound legit. do you have anything to say about this?
jasonastley said:
umm, hey ammsamm, i went to the link you just mentioned, installed it and GOT SOME NASTY SPAMWARE INSTALLED on my machine from it. I'd normally flag you immediately as a bad user, but your other comments sound legit. do you have anything to say about this?
Click to expand...
Click to collapse
Actually this is not the link i downloaded the odin from i tried to
Atthach the one i have but faced with the upload limit, even
After ziping and spilting the the odin, upload failed,
So, you better find another odin 3.10.6 a version with all the buttons
are enabled.
Hi all,
So I got soft bricked Samsung Galaxy S6.
Here are the issues:
- The person got it when he tried to root it
- Stuck in boot logo (Samsung S6, Powered by Android) and does not go further
- I can flash original firmware (Vodafone, Australia) through ODIN successfully, but the problem remains
- Cannot access recovery mode, tried to flash both stock recovery and custom (TWRP, all versions available at twrp.me)
- Have tried both Kies3 and SmartSwitch, emergency recovery went smooth, flashed successfully, but the problem remains
- After each successful flashing, I try to boot into recovery mode in order to clear cache, but it does not boot into recovery at all
- Tried all versions of ODIN and used all cables at home
- Another strange behavior, it can power on only when it is connected to cable. So it either stuck or can boot into Download mode when I press combination. But if I disconnect, after some time it switches off and cannot power on unless you connect it to the cable. Does it mean that the person ticked NAND erase as it is also related to energy dependency of the memory? I don't believe it to be battery issues as I saw this issue on another phone too (Samsung A9)
It is weird. I just want to understand, why I am not able to boot into recovery mode even after successful flashing stock ROM?
Any help is appreciated
Hi, I too have similar issue. Would like to know how you got it resolved.
tanzeeb210 said:
Hi, I too have similar issue. Would like to know how you got it resolved.
Click to expand...
Click to collapse
I could not solve it. Sold the phone for spare parts
Seems like motherboard issue
oscar_ferreiro said:
I could not solve it. Sold the phone for spare parts
Seems like motherboard issue
Click to expand...
Click to collapse
its seems like battery issue more for me than the board!
you should replace or disconect her first before selling the device... could worth the try...
oscar_ferreiro said:
Hi all,
So I got soft bricked Samsung Galaxy S6.
Here are the issues:
- The person got it when he tried to root it
- Stuck in boot logo (Samsung S6, Powered by Android) and does not go further
- I can flash original firmware (Vodafone, Australia) through ODIN successfully, but the problem remains
- Cannot access recovery mode, tried to flash both stock recovery and custom (TWRP, all versions available at twrp.me)
- Have tried both Kies3 and SmartSwitch, emergency recovery went smooth, flashed successfully, but the problem remains
- After each successful flashing, I try to boot into recovery mode in order to clear cache, but it does not boot into recovery at all
- Tried all versions of ODIN and used all cables at home
- Another strange behavior, it can power on only when it is connected to cable. So it either stuck or can boot into Download mode when I press combination. But if I disconnect, after some time it switches off and cannot power on unless you connect it to the cable. Does it mean that the person ticked NAND erase as it is also related to energy dependency of the memory? I don't believe it to be battery issues as I saw this issue on another phone too (Samsung A9)
It is weird. I just want to understand, why I am not able to boot into recovery mode even after successful flashing stock ROM?
Any help is appreciated
Click to expand...
Click to collapse
Same issue here, any idea to solve that? (I'm Brazilian, sorry for some typing wrong)
I don't opened the device (yet), but if is a battery issue, someone tried to fix?
My device is SM-G920I, i tried to flash this FW: G920IDVU3FQD1_G920IXSA3FQC3_XSA without sucess, i will try with a "pit" file that i've found here on XDA and update here, but until the moment, the problem remains
Update: The PIT file does not solved the problem, after this I decided to open the device and swap the battery, but the problem remained, i'm buying a new board today, i think this board can't be saved
I've had similar problem with my Note4. It would sucessfuly apply firmware via Odin but refuse to boot. (tried multiple times)
I then did a flash via SmartSwitch (takes forever) but the phone worked again.
any update for this ? i have the same issue
Hi, I've had a rooted android for a couple of years now. Today I wanted to run the new Magisk root so that I could use apps that prevent rooted phones from using them. Following the instructions here (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445) I went to SuperSU and clicked 'Wipe Root' which then sent my device into constant bootlooping.
I can only get the blue screen saying 'Odin Mode' and a big down arrow saying 'Downloading... Do not turn off target' or a constant bootlooping.
I followed the instructions here though when I have put the four BL, AP, CP and CSC files and click Start, all that happens is in the log on the left it says: <OSM> All threads completed . (succeed 0/ failed 0). From what I can make out, the Odin software on the laptop is not communicating at all with the Samsung S6 in Download mode.
Could someone please help!
bestfootie said:
Hi, I've had a rooted android for a couple of years now. Today I wanted to run the new Magisk root so that I could use apps that prevent rooted phones from using them. Following the instructions here (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445) I went to SuperSU and clicked 'Wipe Root' which then sent my device into constant bootlooping.
I can only get the blue screen saying 'Odin Mode' and a big down arrow saying 'Downloading... Do not turn off target' or a constant bootlooping.
I followed the instructions here though when I have put the four BL, AP, CP and CSC files and click Start, all that happens is in the log on the left it says: <OSM> All threads completed . (succeed 0/ failed 0). From what I can make out, the Odin software on the laptop is not communicating at all with the Samsung S6 in Download mode.
Click to expand...
Click to collapse
Had to come back and add on to my previous post - I sorted it. It was simply a driver issue... Make sure you download all the correct Samsung USB Drivers people if you're having similar issues...
I finally restored my Android to Stock Android (albeit the latest Android system 7.1).