Database Info

[Q] P6810 Problem! - Won't go to Recovery - Bootloop

Hi, I'm having and issue with my Galaxy Tab 7.7 (P6810) and don't know what is the problem, so I'm looking for assistance here. (Thanks in advance).
Let me describe my issue(s):
1. A friend went to flash the Tab and apparently used the wrong firmware, in Odin mode shows GT-P7560.
2. I already tried flashing different firmwares but when I use ICS the Tab goes into a bootloop. I can go to download (odin) mode, but can't go to recovery mode (volume up + power).
3. I flashed it with a stock firmware (P6810DTKL5_P6810XSAKL2_XSA) and got it to boot, but is asking for a password it never had.
So I'm thinking there's an issue with the partition or bootloader. Already tried a "p6810-16g.pit" file with no luck
Tried flashing different CWM versions and nothing works. So at this point I'm stuck on this issue.
What can I do to bring back my device to a functional state? Any advice would be appreciated! THANKS A LOT!! :good::laugh:
I'm attaching the images describing the issues.

edwing29 said:
Hi, I'm having and issue with my Galaxy Tab 7.7 (P6810) and don't know what is the problem, so I'm looking for assistance here. (Thanks in advance).
Let me describe my issue(s):
1. A friend went to flash the Tab and apparently used the wrong firmware, in Odin mode shows GT-P7560.
2. I already tried flashing different firmwares but when I use ICS the Tab goes into a bootloop. I can go to download (odin) mode, but can't go to recovery mode (volume up + power).
3. I flashed it with a stock firmware (P6810DTKL5_P6810XSAKL2_XSA) and got it to boot, but is asking for a password it never had.
So I'm thinking there's an issue with the partition or bootloader. Already tried a "p6810-16g.pit" file with no luck
Tried flashing different CWM versions and nothing works. So at this point I'm stuck on this issue.
What can I do to bring back my device to a functional state? Any advice would be appreciated! THANKS A LOT!! :good::laugh:
I'm attaching the images describing the issues.
Click to expand...
Click to collapse
You don't need a bootloader, it was already "flashed" when he flashed the stock official firmware - bootloader would have been included in that and PIT
If done correctly, the PIT should work, if not - unfortunately, most likely back for repair............ bummer
Without actually checking the above is HC, have you tried the official HoneyComb firmware ? Just don't factory reset in HC recovery

P6810 ICS LPP Bootloader
Here you go............
I have packaged my P6810 ICS LPP bootloader files into an ODIN flashable .tar.mD5 format.
Flashing Instructions :
Extract the Sbl.bin.zip and boot.bin.zips so that you have Sbl.bin.tar.md5 & boot.bin.tar.md5
Ensure you have the latest Samsung USB drivers installed
Disable KIES
Disable KIES process in Task Manager
Run ODIN
Ensure ONLY "auto reboot" and "reset time" are checked
Device in Download mode
Connect device to PC USB port
ODIN - Flash Sbl.bin.tar.md5 in either "bootloader" -or- "PDA" option (choose one only)
Then repeat above same method to flash boot.bin.tar.md5
** After that, try reflash the COMPLETE official stock ICS LPP package with ODIN
Best of luck
UITA
.

UpInTheAir said:
Here you go............
I have packaged my P6810 ICS LPP bootloader files into an ODIN flashable .tar.mD5 format.
Flashing Instructions :
Extract the Sbl.bin.zip and boot.bin.zips so that you have Sbl.bin.tar.md5 & boot.bin.tar.md5
Ensure you have the latest Samsung USB drivers installed
Disable KIES
Disable KIES process in Task Manager
Run ODIN
Ensure "auto reboot" and "reset time" are checked
Device in Download mode
Connect device to PC USB port
ODIN - Flash Sbl.bin.tar.md5 in either "bootloader" -or- "PDA" option (choose one only)
Then repeat above same method to flash boot.bin.tar.md5
** After that, try reflash the COMPLETE official stock ICS LPP package with ODIN
Best of luck
UITA
.
Click to expand...
Click to collapse
Hi, thanks for your assistance... here's what I just did:
1. I downloaded the bin files you attached and both are appearing as invalid md5 in ODIN, apparently the hash is invalid.
2. I renamed them from .tar.md5 to just .tar and flashed my device with both files as you described.
3. Rebooted twice, went to Download mode again.
4. Flashed with P6810XXLPP_P6810XSALJ2 (stock firmware).
5. Got bootloop again.
6. Re-flashed the "Sbl.bin" & "boot.bin" again, and still got bootloop.
7. Download mode still shows "P7560" as the installed firmware.
Any other advice?
Thanks again! :good:

edwing29 said:
Hi, thanks for your assistance...
I downloaded the bin files you attached and both are appearing as invalid md5 in ODIN, apparently the has is invalid.
Can you check them and re-upload if there's no problem?
Thanks again! :good:
Click to expand...
Click to collapse
I'll have a play around on my device first, and see if I can get them to work. Those were untested.
Sent from my GT-I9500 using xda premium

UpInTheAir said:
I'll have a play around on my device first, and see if I can get them to work. Those were untested.
Sent from my GT-I9500 using xda premium
Click to expand...
Click to collapse
Hi, I just edited the previous reply.
Check it out, Thanks.

edwing29 said:
Hi, thanks for your assistance... here's what I just did:
1. I downloaded the bin files you attached and both are appearing as invalid md5 in ODIN, apparently the hash is invalid.
2. I renamed them from .tar.md5 to just .tar and flashed my device with both files as you described.
3. Rebooted twice, went to Download mode again.
4. Flashed with P6810XXLPP_P6810XSALJ2 (stock firmware).
5. Got bootloop again.
6. Re-flashed the "Sbl.bin" & "boot.bin" again, and still got bootloop.
7. Download mode still shows "P7560" as the installed firmware.
Any other advice?
Thanks again! :good:
Click to expand...
Click to collapse
Very strange, particularly if the flash was successful.....................
Try flashing both the files at once. boot.bin in "bootloader" and SBl.bin in "PDA".
Maybe something else we haven't thought of..
If I think of anything else, will let you know, but try the stock HC firmware too, just in case.

UpInTheAir said:
Very strange, particularly if the flash was successful.....................
Try flashing both the files at once. boot.bin in "bootloader" and SBl.bin in "PDA".
Maybe something else we haven't thought of..
If I think of anything else, will let you know, but try the stock HC firmware too, just in case.
Click to expand...
Click to collapse
Tried the steps above and still the same.
I had to flash back to the stock HC firmware because the ICS led into an infinite loop, at least HC let me turn off the device.
I'll wait for any other suggestions, thanks!
Sent from my GT-I9100 using xda app-developers app

All I can suggest is to send it away for repair.
JTag (riff box) by a 3rd party or Samsung.
If it's NOT a hardware issue, JTag should be much cheaper, and if successful, faster.
http://www.jtagbox.com/riff-jtag-bo...s-unbrick-bricked-phone-riff-box-owners-list/
Sent from my GT-I9500 using xda premium

[Q] Need help! Can't unroot/unbrick Galaxy S3!

So let me start from the beginning;
I have Verizon's Galaxy S3 and had CyanogenMod 10.2 installed on it. After installing CM 10.2, I no longer had 4G/3G connection. After some research, I had discovered that it had to do with my device's APN. Anyways, what I found online was to unroot, and flash to a stock ROM, and wipe/reset factory settings, etc.
I started by flashing a stock ROM found on this site (don't remember the name) however, after rebooting, my phone had gotten stuck in the white Verizon logo loop. After pulling the battery, I tried flashing the image again in ODIN, but the same thing happened, I figured this is what was known as a "soft brick". I followed another guide on here to unroot/unbrick the phone, which had me download another stock rom (stock.vzw_root66), as well as VRALEC.bootchain.tar.md5, and BOOTLOADER-I535VRALF2-618049-REV09-user-low-ship.tar-2-.md5. Following the instructions had me PDA flash the VRALEC-bootchain.tar.md5 first, followed by the bootloader, and finally the stock image. However, I continued to get "FAIL!" after attempting to flash the VRALEC-bootchain.tar.md5.
Following another guide, it said to just try flashing the stock.vzw_root66 file, which I had done, and it succeeded, however, after the phone reboots, it says that I am using unauthorized firmware on my device, and to bring my phone to the nearest Verizon store.
Now, I have no idea what to do.
I'm using ODIN3 v3.07
Both the VRLEC.bootchain.tar.md5 and BOOTLOADER-I535VRALF2-618049-REV09-user-low-ship.tar-2-.md5 fails when trying to flash them onto my phone, and I don't want to proceed from here unless I know how to fix it, as to not damage the phone any further. Any help would be greatly appreciated!
The phone still boots into a stock recovery, and can still enter download mode. At this point, I just want my phone completely stock, as if I had just purchased it.

You shouldn't be getting the "unauthorized firmware" warning after flashing root66, as that is a stock image. You could try to boot into stock recovery and perform a factory reset from there. I'm not even sure if that's possible I haven't used stock recovery in so long .
Besides that I don't know what would help you. Maybe try reflashing the root66 file or try a different stock image. Do you have a link to the exact root66 file you are using?

Boot into download mode and post what it says on the top left corner.
Sent from my SCH-I535 using Tapatalk 2

BattsNotIncld said:
You shouldn't be getting the "unauthorized firmware" warning after flashing root66, as that is a stock image. You could try to boot into stock recovery and perform a factory reset from there. I'm not even sure if that's possible I haven't used stock recovery in so long .
Besides that I don't know what would help you. Maybe try reflashing the root66 file or try a different stock image. Do you have a link to the exact root66 file you are using?
Click to expand...
Click to collapse
Sorry, I meant that it says unauthorized software, and it has the yellow triangle. I've tried reflashing the root66 file, which is the only thing that actually "PASS"'s in ODIN, whilst everything else consistently fails.
Since then, I've followed this tutorial (Specifically section 5)
http://forum.xda-developers.com/showthread.php?t=1762709
And downloaded that "VRALG1 4.0 ICS-http://www.mediafire.com/download/kk...w_ship.tar.zip" file that was recommended, and after trying to flash it in the PDA box of ODIN (With auto-reboot and F. Reset Time checked), it FAIL's.
BadUsername said:
Boot into download mode and post what it says on the top left corner.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
After looking at the screen with download mode still on, right after the above file failed in ODIN, it reads:
_______________________________
ODIN MODE
Product Name: SCH-I535
Custom Binary Download: Yes (3 counts)
Current Binary: Samsung Official
System Status: Custom
Qualcomm Secureboot: Enable
Warranty Bit: 0
Bootloader AP SWREV: 1
SW Rev Check Fail : Fused 1 > Binary 0 **(This part I believe was added after the FAIL of trying to flash the VRALG1 4.0 ICS file.)
_______________________________
So far, the only file I've been able to successfully flash in ODIN is the stock.vzw_root66 file. Everything else constantly FAILs. Thanks for the ongoing help!

I'm pretty sure those download mode stats you have are from the new bootloader. When you said this:
I started by flashing a stock ROM found on this site (don't remember the name) however, after rebooting, my phone had gotten stuck in the white Verizon logo loop.
Click to expand...
Click to collapse
... I'm thinking you flashed a stock 4.3 ROM in ODIN and therefore locked your bootloader. This would also explain the yellow triangle when trying to flash root 66 afterwards. If I am correct, the good news is all you have to do is flash a stock 4.3 ROM to get back up and running. The bad news is you re-locked your bootloader and are stuck with TouchWiz.

WildWildWest42 said:
Sorry, I meant that it says unauthorized software, and it has the yellow triangle. I've tried reflashing the root66 file, which is the only thing that actually "PASS"'s in ODIN, whilst everything else consistently fails.
Since then, I've followed this tutorial (Specifically section 5)
http://forum.xda-developers.com/showthread.php?t=1762709
And downloaded that "VRALG1 4.0 ICS-http://www.mediafire.com/download/kk...w_ship.tar.zip" file that was recommended, and after trying to flash it in the PDA box of ODIN (With auto-reboot and F. Reset Time checked), it FAIL's.
After looking at the screen with download mode still on, right after the above file failed in ODIN, it reads:
_______________________________
ODIN MODE
Product Name: SCH-I535
Custom Binary Download: Yes (3 counts)
Current Binary: Samsung Official
System Status: Custom
Qualcomm Secureboot: Enable
Warranty Bit: 0
Bootloader AP SWREV: 1
SW Rev Check Fail : Fused 1 > Binary 0 **(This part I believe was added after the FAIL of trying to flash the VRALG1 4.0 ICS file.)
_______________________________
So far, the only file I've been able to successfully flash in ODIN is the stock.vzw_root66 file. Everything else constantly FAILs. Thanks for the ongoing help!
Click to expand...
Click to collapse
OK, you need to follow this guide, then your phone will be back to normal.
http://forum.xda-developers.com/showthread.php?t=2586319
Then read this entire thread to understand what you can do with the update.
http://forum.xda-developers.com/showthread.php?t=2639337
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
OK, you need to follow this guide, then your phone will be back to normal.
http://forum.xda-developers.com/showthread.php?t=2586319
Then read this entire thread to understand what you can do with the update.
http://forum.xda-developers.com/showthread.php?t=2639337
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
You're a life-saver! I just did this and my phone now works again! I couldn't thank you enough!

flashing stock with latest odin failed writing system.img to System Partition

I am using the latest stable nightly build for me, the one released in 04-04 of the LineageOS.
The build is working fine, however, I need to go back to stock firmware.
Last time I tried to do it using newest Odin, I was on latest build (the one that has all those crashes) and right at the beginning of the flashing process, the writing of system.img to System partition fails and the device was bricked.
Bricked up to the point where a restore using Samsung Switch was the only apparent solution. So I went for it. I have to say it is a really annoying procedure, you will need your device serial number and a good internet connection. When the download was finished, the software instructed me to go into download mode. The installation started and seemed to be doing fine, but sadly the process has failed at 67%.
As a workaround, I flashed TWRP and then another more stable version of LineageOS. Before flashing the OS, i did a file system repair on the System partition, which had a strange small size.
I'm afraid that the same thing could happen again.
Could you please help me out?
Thanks.

Extract system.img from software and flash it alone

Or use samsung kies to flash back the orig firmware.

RiTCHiE007 said:
Or use samsung kies to flash back the orig firmware.
Click to expand...
Click to collapse
I did, and it has failed at 67%.

hemp_invader said:
I did, and it has failed at 67%.
Click to expand...
Click to collapse
Try flashing the PIT file with Repartition enabled in ODIN first
https://www.s a m m ob i l e.com/forum/showthread.php?t=30609

*Detection* said:
Try flashing the PIT file with Repartition enabled in ODIN first
https://www.s a m m ob i l e.com/forum/showthread.php?t=30609
Click to expand...
Click to collapse
Thanks mate, I will take a look at this.
I have been looking for a solution and ran into this alternative in other communities. The problem is, I don't have that much experience with Odin rather than flashing the usual files in order to install a ROM.
When the device became bricked, it wouldn't even boot to download mode. The only solution was recovering with Samsung Switch, which took a while to download the build by the way. Then the software allows you to boot into download mode. The automated install process seemed to be doing just fine, until it failed at 67%. So I booted into download mode and flashed latest TWRP, that allowed me to repair the system partition (which had a strange small size) and then flashing a more stable version of the LineageOS and here I am now.

hemp_invader said:
Thanks mate, I will take a look at this.
I have been looking for a solution and ran into this alternative in other communities. The problem is, I don't have that much experience with Odin rather than flashing the usual files in order to install a ROM.
When the device became bricked, it wouldn't even boot to download mode. The only solution was recovering with Samsung Switch, which took a while to download the build by the way. Then the software allows you to boot into download mode. The automated install process seemed to be doing just fine, until it failed at 67%. So I booted into download mode and flashed latest TWRP, that allowed me to repair the system partition (which had a strange small size) and then flashing a more stable version of the LineageOS and here I am now.
Click to expand...
Click to collapse
Well CSC contains the PIT file, so using CSC & Checking 'Repartition' in ODIN while flashing the full 4 sections of the ROM 'should' in theory do the same thing, so give both a try
PIT = Deletes and recreates the partitions on the internal storage before flashing the ROM, so if one of them is messed up size wise from Lineage or something, then the PIT should fix it
There could also be a hardware problem, but still a few options to try with firmware and flashing first

TWRP refuses to flash on Galaxy S7 G930U

I have an unlocked CDMA/GSM Galaxy S7 rooted using the guide at https://forum.xda-developers.com/ve...to-notes-root-install-xposed-unroot-t3411039/ and I'm trying to download TWRP for it. I've tried using the official TWRP app to try to flash twrp-3.1.0-0-heroqltechn to recovery and first I flashed the one that wasn't a tar because I thought it was the one that was a tar, but apparently the ones that are a tar simply don't show up when you attempt to select a file so I can't use them. That and I forgot to unlock OEM. Of course that caused it to get stuck at the boot failure screen so I just reflashed the rooted boot it was using and it worked fine again. Then I tried to install manually using Odin3.12 and when I try, it failed and the log says
1: Added!!
2: Odin engine v(ID:3.1203)
3: File analysis..
4:SetupConnection..
5: Initialzation..
6: Get PIT for mapping..
7: Firmware update start..
8: SingleDownload.
9: recovery.img
10: RQT_CLOSE !!
11: (nothing)
12: Complete(Write) operation failed.
<OSM> All Threads Completed. (succeed 0 / failed 1)
Then I try flashify to flash the tar to recovery and it says File could not be loaded.
I'm pretty much at an impasse here, so I'm posting here. By the way if anyone has any solid guides on how to pass safetynet for pokemon go with root that would be great too, thanks.

Pretty sure the U variant have locked bootloader dispite being carrier unlocked.

Colonel Kernel said:
I have an unlocked CDMA/GSM Galaxy S7 rooted using the guide at https://forum.xda-developers.com/ve...to-notes-root-install-xposed-unroot-t3411039/ and I'm trying to download TWRP for it. I've tried using the official TWRP app to try to flash twrp-3.1.0-0-heroqltechn to recovery and first I flashed the one that wasn't a tar because I thought it was the one that was a tar, but apparently the ones that are a tar simply don't show up when you attempt to select a file so I can't use them. That and I forgot to unlock OEM. Of course that caused it to get stuck at the boot failure screen so I just reflashed the rooted boot it was using and it worked fine again. Then I tried to install manually using Odin3.12 and when I try, it failed and the log says
s.
Click to expand...
Click to collapse
Eric1084 said:
Pretty sure the U variant have locked bootloader dispite being carrier unlocked.
Click to expand...
Click to collapse
Hi +1 Eric1084
Bootloader is locked impossible to get TWRP in the USA version
On Chinese Snapdragons is possible...
https://forum.xda-developers.com/ga...gon/recovery-official-twrp-galaxy-s7-t3458579

MAX 404 said:
Hi +1 Eric1084
Bootloader is locked impossible to get TWRP in the USA version
On Chinese Snapdragons is possible...
https://forum.xda-developers.com/ga...gon/recovery-official-twrp-galaxy-s7-t3458579
Click to expand...
Click to collapse
Well thats just groovy. Everytime I try to reboot it goes into recovery boot failure. Any way to fix?
I'm going to try to flash the stock firmware for this phone from sammobile, G930UOYM4APL2_XAA and pray it fixes the recovery boot. If that doesn't work I might try to hard reset the phone, but I'm not sure if that will damage it in any way so I'm a little reluctant. If neither work I have a specialist man who usually knows what he's doing, so I'll take it to him after that. Any advice would be greatly appreciated

Looks like flashing the stock firmware worked. Unrooted and everything, no bootloop or anything anymore. Shame though, wish I could have root and pass safetynet

Any ODIN flashable Rom Request

hi all, I've managed to brick my SM-P900.
Could someone point me to where I can get an Odin flashable rom please, with all the individual bits such as PDA / Phone / CSC.
I can't flash normal roms, it's not working with just the md5. Ideally stock, but happy with any rom as I can flash something else with TWRP.
I can't use any of the normal samsung sites as they're paid, and I'm broke =(
I would really appreciate it if you could help me fix this.
Many thanks

Google
SM-P900 - Samsung Firmware | Samsung Updated
---------- Post added at 03:14 AM ---------- Previous post was at 03:09 AM ----------
https://forum.xda-developers.com/galaxy-note-pro-12/general/firmware-firmware-t3038178

Where you able to solve your problem?

bmwdroid said:
Where you able to solve your problem?
Click to expand...
Click to collapse
x2 for me also

sp000n said:
x2 for me also
Click to expand...
Click to collapse
Sorry, don't understand.
Problems or just interested as well?

Nope, not solved, tried for ages, but ODIN doesn't flash it, just gets stuck on initialising.... I'm completely out of ideas!

Zophixan said:
Nope, not solved, tried for ages, but ODIN doesn't flash it, just gets stuck on initialising.... I'm completely out of ideas!
Click to expand...
Click to collapse
Did you get the multiple part ROM using samfirm_reborn tool?

bmwdroid said:
Did you get the multiple part ROM using samfirm_reborn tool?
Click to expand...
Click to collapse
Just tried downloading it and I get .tar.md5 file, not sure how i did it but from a previous attempt at fixing it, I have the same thing but in seperate files, with boot, cache, hidden, recovery s boot and system. Do i need to put them into odin? where do they go? I get stuck on initialising, tried pulling out cable and putting it back in, then it says it can't find a pit partition... tried flashing a pit file but still stuck on initiailising so pit doesn't flash.

@Zophixan the files you see, are in the opened archive.
Where did you get the file from?
You should have downloaded and decrypted 3 (P900) or 4-5(P905) separate files all ending md5 when using samfirm.
When there is only one you obviously have NOT the multiple part stock ROM.
Which Odin using?

bmwdroid said:
@Zophixan the files you see, are in the opened archive.
Where did you get the file from?
You should have downloaded and decrypted 3 (P900) or 4-5(P905) separate files all ending md5 when using samfirm.
When there is only one you obviously have NOT the multiple part stock ROM.
Which Odin using?
Click to expand...
Click to collapse
I've tried odin 3.07 and 1.85. I downloaded samfirm_reborn and upon use it downloaded just one file "SM-P900_1_20170222195126_gly008r5gf.zip" and inside it is the tar md5. Where can I get the separate items?
Even if I am not using the seperated one, shouldn't odin flash? It's always stuck on intiailising, I don't know if this matters but it says knox warranty 0500 on the download screen, and custom kernal / binary.
I remember having a similiar problem years ago on the same tablet but no idea how I fixed it, vaguely remember downloading seperate files to flash in each of the odin sections.
thanks.
EDIT, found the binary option nature option, will download now and try flashing each bit and report back...

bmwdroid said:
@Zophixan the files you see, are in the opened archive.
Where did you get the file from?
You should have downloaded and decrypted 3 (P900) or 4-5(P905) separate files all ending md5 when using samfirm.
When there is only one you obviously have NOT the multiple part stock ROM.
Which Odin using?
Click to expand...
Click to collapse
Still stuck on initializing, tried samsung drivers, even tried heimdall (and installed it's drivers), is there anything else I can try?
It says AP SWREV A1 and know warranty voide 0500, and current binary / system status as custom on the tablet.

Try a newer Odin.
I recommend at least 3.09.
What it says in DL mode is just information and no failure afaik.

bmwdroid said:
Try a newer Odin.
I recommend at least 3.09.
What it says in DL mode is just information and no failure afaik.
Click to expand...
Click to collapse
I tried both 3.10 and 3.09 but still stuck on initialisation... (do i need to do anything with CP or UMS field?),
does the current binary/ system status as custom ,or AP SWREV A1, or knox warranty mean anything?
Do you have any other suggestions, I can't think of anything else! =(

Knox was triggered when flashing other than stock.
Forget about it.
Other is shown on mine as well.
CP stays empty at WiFi models.
UMS I've never did anything with.
Try to use other cables and USB ports.