Database Users

[Q] Invalid Percent of Drawing download progress bar

Hey guys
Could really appreciated some advice please?
Tried to install the Vodafone UK lollipop image I downloaded from sammobile on sat night and tried flashing it. I have the unbranded UK Note3 32gb Lte. I got Odin fail and on the screen of the phone there was a constantly repeated line of red text that said 'invalid percent of drawing download progress bar'
This is what Odin said
<ID:0/006> modem.bin
<ID:0/006> cache.img.ext4
<ID:0/006> hidden.img.ext4
<ID:0/006> FAIL! (Size)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
Can anyone advise on what happened please? Do you think my vodafone uk lollipop image is broken? Would I be safe to try the Polish rom? Or is there something wrong with the phone?
I do not have root or a custom recovery on my device.
Im back on 4.4.2 and the phone is running fine - but OTA updates arnt out for the unbranded 4.4.2 uk handset.
Thank you in advance for your help

Try the Poland ONE coz your device is unbranded.

Do you think that is the reason it didnt work? Purely due to branding? Thank you for your help

Yep tried installing poland file as recommended above all back to normal now thank you Running the lovely lollipop

Odin refuses to install modem

Hello there.
I've had this problem with Odin. I have a Galaxy S4 and I've been trying to change it's baseband, however, when I try to flash a modem on Odin this is what happens:
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing..
Please wait about 2 minutes
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Receive Response from boot-loader
<OSM> All threads completed. (succeed 0 / failed 1)
I've tried to flash modems with TWRP, it says success but it doesn't actually change anything. Please, is there a way to forcefully flash the modem with Odin? Am I making a mistake with the recovery and that's why nothing changes?
I'm not looking for advice about risk of bricking, this phone is already useless to me unless I change it's modem. I MUST enable GSM bands.
The model is SCH-R970. Help me out please :'(

happened with me before once
i enabled usb debugging in settings -> developer mode
it fixed the issue for me

It's already enabled. Without that I think Odin wouldn't even try.

Why do you even think that you can unlock gsm? You cannot flash modems from a different version of the s4. And on a sidenote you cannot flash modems true the recovery anymore.

I think I'll just wipe efs and see if I can do something else. If anything goes wrong I'll have to buy an I9505/6 board. But still, does anybody here know how to forcefully flash a new modem/baseband? I asume the risk of bricking, just tell me how.

I already gave you the answer. It's impossible.

If you want to enable GSM bands, you need to enter the service menu of the phone and enable them there. Search Google, because I did find a post explaining how to do it along with any pitfalls involved. But that was a year ago, and it was in the midst of searching for a solution to my issues I had with the device back then.
As @Lennyz1988 mentioned already, flashing a modem from another model will not work. Odin will always reject it.

Menu + Back keys not working after Upgrade to Lollipop 5.0?? READ THIS!!

This post is to help anyone that upgraded to Lollipop 5.0 from KitKat 4.4.2 with any newer 2012+ devices (Not just the Note 3, but also s4 etc.) exhibiting the symptoms in the title of this post.
So i picked up a Galaxy Note 3 SM-N900W8 and got the OTA update from KitKat 4.4.2 to Lollipop 5.0 and thought "Cool!" but alas, was I to be sadly informed of a major issue when I rebooted.
It started up fine but when I hit the back button it didn't respond. Then I hit the menu button and "Search" came up instead. I freaked, I lost my cool. Then my technical mind took hold and I started digging through XDA with their search tool thinking "Maybe i'm not the only one that is having this problem" and WOAH! Did I ever find a load of trouble.
Here's what i found out:
Ebay and Aliexpress sellers of replacement screens for alot (and i mean ALOT) of samsung phones from 2012 and newer used a compatible chip from a company called Cypress who makes the touchkeys chip for samsung (and other phone makers) and that OEM part number is CY8C20065. The sellers/manufacturers of replacement screens are using the compatible Cypress chip part which is the CY8C20236A.
The upgrade to 5.0 installs new firmwares throughout the phone INCLUDING the IC that controls the capacitive keys (Menu + Back) to version 0x12, from the KitKat version 0x10. The IC CY820236A is NOT compatible with the newer 0x12 firmware and gets hosed.
Now for a Solution that you may or may not like: The only way thusfar that I have found that works is to DOWNGRADE back to Kitkat 4.4.2 as anything higher screws the IC controller up and you will have to replace your LCD+digitizer (at $180+ this is not an option, cheaper to go get a phone online used with the original screen and everything stock) This is a fully STOCK recovery to a 100% working unit. No Root, other add-ons etc.
Now, unless someone (BIG HINT HERE to devs) can figure out this issue, alot of people are stuck with a paperweight. You can try and add the softkeys onto the screen, or flash this kernel but it WILL trip your Knox counter and set you to "Custom" Binary and Status.
I take NO credit for this post at all, I just almagamated the information from this and this post.

Do you wipe factory reset after flashing your rom???

jemis1983 said:
Do you wipe factory reset after flashing your rom???
Click to expand...
Click to collapse
Yes, if you read the threads, wiping the unit before primary boot has no effect on this issue at all. once you upgrade to Lollipop, the IC is written to and is corrupted after that. Nothing can stop this process save for a non-stock update/upgrade that has the 0x12 firmware altered/downgraded and that's where the kernel flash I listed comes in to restore (but void the warranty) the keys to proper working state.

Error in Odin
repherb said:
Yes, if you read the threads, wiping the unit before primary boot has no effect on this issue at all. once you upgrade to Lollipop, the IC is written to and is corrupted after that. Nothing can stop this process save for a non-stock update/upgrade that has the 0x12 firmware altered/downgraded and that's where the kernel flash I listed comes in to restore (but void the warranty) the keys to proper working state.
Click to expand...
Click to collapse
I recently udpated from 4.4.2 to lollipop on my Note 3 SM-N900A (Build N900AUCUEOC1) and have the soft key problem.
I tried the idlekernel option but that errors out in Odin.
<ID:0/006> Odin engine v(ID:3.1203)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> boot.img
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On the phone it says
SYS REV CHECK FAIL : No Version
SECURE MAGICODE CHECK FAIL : boot
I am novice at this, so how can I get around this.

i found a fix no root no kernel mod
The issue has been resolved!
http://forum.xda-developers.com/galaxy-note-3/help/to-fix-softkey-note-3-t3446134

Sprint S7 locks out other firmwares due to version fuses

I recently discovered the hard way that S7s have version fuses. These prevent you from installing certain older firmwares. This is convenient for Sprint as it prevents you from switching your SM-G930P to another carrier.
If you look at a Samsung firmware's release ID, such as G930UUEU4BQJ5, look at the 5th place from the right, in this case a 4. That is what I'm calling the firmware version.
I am on Sprint, and that carrier incremented its firmware version to 5 starting with QJ3 (Nov. 12, 2017). See https://www.sammobile.com/firmwares/galaxy-s7/SM-G930P/SPR/ for a firmware list.
A few weeks after that, I tried changing my phone from the Sprint SM-G930P to the unlocked SM-G930U. If you check https://www.sammobile.com/firmwares/galaxy-s7/SM-G930U/, you'll see that all variants of the U were and still are on firmware version 4. Also, T-Mobile is on 4, Verizon is on 4, and AT&T is on 4. (Why is AT&T's SM-G930A not on sammobile.com?)
Anyway, I got this error during the SM-G930U firmware install: SW REV CHECK FAIL : [ABOOT]FUSED 5 > BINARY 4.
Not appreciating what this meant at the time, I managed to get the CP (modem software) from the SM-G930U on my phone as I tried the four files one at a time. It turns out you can put some older software on the phone. However, you need to have your current firmware around so that you can put things back if they don't work. Unfortunately for me, the firmware download for SM-G930P (Sprint) QJ3 didn't become available for about a week after I did this. I couldn't use a prior Sprint firmware because all before QJ3 had a lower firmware number. While the phone worked fine with this version mismatch, I had to endure repeated Knox security warning messages.
I since put the phone back on the SM-G930P firmware (once QJ3 became available for download!), and everything's happy now. No warranty fuse issues or anything, and I'm two OTA releases newer now than QJ3.
A more detailed write-up is here: https://www.arencambre.com/blog/2018/01/01/fused-firmware-version-locks-samsung-s7/
I may not be searching on the right keywords, but I can't find anyone else reporting this. As mentioned at top, it's really convenient for Sprint that it incremented its firmware version. This lock out Sprint S7 owners from switching to another carrier. I can assure that you really need to change firmware to do that: I switched to T-Mobile for one month over the summer but kept the Sprint firmware on the (unlocked!) Sprint phone. Several bands were missing until I switched to the T-Mobile firmware. For now, Sprint S7 owners cannot do that unless there is some way to increment the firmware version number, but even then, I'd guess we'd have trouble installing the other carrier's OTA updates.

All US model S7s (Snapdragon) have locked bootloaders, this is why you cannot downgrade to older firmware

*Detection* said:
All US model S7s (Snapdragon) have locked bootloaders, this is why you cannot downgrade to older firmware
Click to expand...
Click to collapse
Is that version number (5 digit from right on version string) really for the bootloader version?

novasource said:
Is that version number (5 digit from right on version strong) really for the bootloader version?
Click to expand...
Click to collapse
Not sure what the numbers / letters mean in firmware versions
But that's the reason you can't downgrade

*Detection* said:
Not sure what the numbers / letters mean in firmware versions
But that's the reason you can't downgrade
Click to expand...
Click to collapse
Still, you typically don't downgrade to switch carriers (I didn't going from VZW to T-Mobile, for example)
(I was avoiding a network lock due to shens of the previous owner of the handset -hence the move to the UnCarrier from BigRed) - I also gained VoLTE and wi-fi calling; neither of which I could have kept on BigRed for some rather odd reason).

PGHammer said:
Still, you typically don't downgrade to switch carriers (I didn't going from VZW to T-Mobile, for example)
Click to expand...
Click to collapse
You are generally correct when it comes to Android software version (occasionally, you may need to jump back a minor Android release or two if the carrier you're going to isn't as up to date on releases as the carrier you're coming from).
However, Android software is just one of four files in a firmware package. The problem is the version number embedded in the firmware package itself, which might correspond to the bootloader version. This number prevents Sprint S7 owners from going to any other firmware: at this point as it appears that Sprint is the only one whose firmware (or bootloader?) version is at 5. All others appear to be 4 or lower.

The 4 and the 5 is the binary correct? I'm assuming that because that's where Odin always has the problem when I was pointlessly trying to root my SM-G935P on QL1 firmware.

Brianmagoon said:
The 4 and the 5 is the binary correct? I'm assuming that because that's where Odin always has the problem when I was pointlessly trying to root my SM-G935P on QL1 firmware.
Click to expand...
Click to collapse
The 4 and 5 are numbers I see in the firmware version strings that may correspond to the bootloader version. Regardless, if you've installed a firmware with a 5 in that version digit, then you cannot install any firmware with a lower version. So if you are on a Sprint-branded S7 and up to date, then you cannot install any other firmware until they also have a 5 in the firmware version string.

Yeah that sucks. I was really looking forward to rooting this beast. Looks like that won't be happening any time soon

Nobody incremented their bootloader revision except Sprint.
Everyone is still on bootloader 4 (VZW/ATT/TMO)
Sprint is now on bootloader 5
Also, none of this is a downgrade, they released identical versions with different bootloader revision
Example
Latest Sprint software
G930PVPU5BQL1
Latest OEM software
G930UUES4BQL1
They are basically identical softwares
This was done intentionally to stop unbranded G930U flashing which also results in European LTE bands 3/7/20 to be enabled
Sprint does not want these items to leave the United States.

sins07 said:
...
Also, none of this is a downgrade, they released identical versions with different bootloader revision
...
This was done intentionally to stop unbranded G930U flashing which also results in European LTE bands 3/7/20 to be enabled
Sprint does not want these items to leave the United States.
Click to expand...
Click to collapse
Confirms my suspicion, if you are sure the binaries are functionally the same.

Sadly I just picked up a sprint 7 edge last night with oct 1 2017 patch ..I neglected to do my homework on this device and of course its on 5b ..does anyone know the possibility or likeliness that other carriers would feel the need to go to 5B
Sincerely,
A screwed buyer

So question.. how did you manage to get the image for the S7 930P? I tried two different 930U images and now left with a cycling device. I can't seem to download the 930P image using sammobile. I've tried 4 different sites. Some say free downloads for 2gb or less and the image size is 2.3gb. Any working link would be greatly appreciated.

Hey Guys, I have the tmobile version and went through this when the phone first came out. I am rather certain that number does correspond to the bootloader version. At the time I wanted to install the U firmware on my stock tmobile phone and couldn't because tmobile version had a higher bootloader version. At the time tmobile was the only one with the higher bootloader iirc. Eventually all the carriers, including U, caught up to tmobile and I was able to downgrade.

Hey, would you gents mind helping me out. I had a failed root attempt, and ****s been a little crazy with my 930p. Currently I get this while trying to get back to anything which will make my phone work. I understand about the SW versions, and F sprint for that. However, would any of you be so kind as to simply tell me which files I need to get this thing to not be in a constant state of boot loading either in recovery or anything else. I get this on the download screen SW REV CHECK FAIL : [ABOOT]FUSED 5 > BINARY 4 while Odin says this:
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> emmc_appsboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> lksecapp.mbn
<ID:0/004> xbl.elf
<ID:0/004> FAIL! (Auth

tonysak said:
Hey, would you gents mind helping me out. I had a failed root attempt, and ****s been a little crazy with my 930p. Currently I get this while trying to get back to anything which will make my phone work. I understand about the SW versions, and F sprint for that. However, would any of you be so kind as to simply tell me which files I need to get this thing to not be in a constant state of boot loading either in recovery or anything else. I get this on the download screen SW REV CHECK FAIL : [ABOOT]FUSED 5 > BINARY 4 while Odin says this:
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> emmc_appsboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> lksecapp.mbn
<ID:0/004> xbl.elf
<ID:0/004> FAIL! (Auth
Click to expand...
Click to collapse
Had the same issue. After much trial and error (and a few boot loops and soft bricks) I was able to get the phone back to factory with firmware G930PVPU5BQL1 from another site (not sure if I'm allowed to link, but it has the words Samsung and firmware in the address, and it's a .org). Make sure you factory reset and wipe cache afterwards in recovery (hold power, home, volume up), and I'd recommend flashing the CSC rather than HOME_CSC to avoid duplicates in the settings menu. I unchecked auto reboot in Odin to make it easier to get to recovery without having to watch the whole install like a hawk. Also, don't sweat it if you get "Installing system update" and then "No command" when you boot into recovery mode. Just wait for a few minutes and it'll take you to the recovery menu. After the factory reset and cache partition wipe, you should be able to reboot and be have a squeaky clean install. YMMV but it worked for me. Good luck.

jessemcstew said:
Had the same issue. After much trial and error (and a few boot loops and soft bricks) I was able to get the phone back to factory with firmware G930PVPU5BQL1 .
Click to expand...
Click to collapse
Wanted to say thanks. I've been struggling with this issue for a couple of weeks on and off as I play with this S7. Really frustrating to be on my like 8th firmware download and still running into issues prior to the above.
Now that I have the phone back up and running, anyone know how to move to stock non-sprint android given the issues with the sprint bootloader? My preference would be to debloat and de-gaps but from all the reading in the past week or so it doesn't sound likely.
My hope was that given the rollout of oreo now that someone would have a v5 bootloader for sm-930U (generic S7 - non carrier version)

schmism said:
My hope was that given the rollout of oreo now that someone would have a v5 bootloader for sm-930U (generic S7 - non carrier version)
Click to expand...
Click to collapse
Your hopes are likely dashed.
1. Every US carrier has updated to Oreo and none of them have updated the bootloader to v5, except for Sprint. So if you have the latest Sprint firmware, you can't switch to anything else.
2. As of this writing, the US unlocked version (SM-930U) still has not been updated to Oreo. There is no announcement when it will be released. And there is no reason to think it will be v5.

Friends, until there is an upgrade to the bootloader of the G930U Firmware, i believe it is not possible to convert the sprint device with binary 5 to G930U
At the moment, what seems to work is doing it via flashfire. There is a tutorial posted on the youtube link here

No Samsung Apps
borispavlov said:
Friends, until there is an upgrade to the bootloader of the G930U Firmware, i believe it is not possible to convert the sprint device with binary 5 to G930U
At the moment, what seems to work is doing it via flashfire. There is a tutorial posted on the youtube link here
Click to expand...
Click to collapse
Yes, but you will see on their linked site that Samsung Apps will not run on this version. Probably should wait if you care about this.

FRP locked tab a, need some "special" help

So, i recently (like a month or so ago) bought a tab a (from Ger, since i live here) and directly rooted it.
Now since i have some rooting exp from rooting my samsung s4 and my xperia play (who remembers that phone lol) and i didnt find anything new during my (rather short) research, i directly got odin, got twrp and just went right ahead. I did NOT read about the fact that there is a FRP lock and that i have to do the OEM unlock thing in the dev options. This went well a few weeks until i started my tab a yesterday and got the FRP msg on boot. I did some more research, banged my head against a wall for not reading enough beforehand and got a (to my knowledge) stock firmware with recovery ( T580ZCU2AQH2_T580CHN2AQH2_CHN )
and tried to flash that over Odin. It didnt work and i get this
<ID:0/008> Added!!
<ID:0/008> Odin engine v(ID:3.1207)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> NAND Write Start!!
<ID:0/008> SingleDownload.
<ID:0/008> sboot.bin
<ID:0/008> param.bin
<ID:0/008> cm.bin
<ID:0/008> boot.img
<ID:0/008> recovery.img
<ID:0/008> FAIL!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
in the command line thingy with the text
FRP is enabled, ignore PIT download
SW REV. Invalid type.
FRP is enabled, not allow download non-FRP BOOTLOADER binary
can anyone tell me whats wrong, and suggest what to do instead?

same issue.. Did you manage to get a fix for this?

RenVilo said:
same issue.. Did you manage to get a fix for this?
Click to expand...
Click to collapse
actually yes, i did this a few months ago already, but iirc i flashed a stock rom from the web (just google it theyre not hard to find), without any rooting shenanigans and disabled the lock and then went through the whole process again
you might need to boot into the rom a few times to make it install the stock recovery tho

FRP lock should not prevent you from flashing a stock ROM via Odin. But you have to flash the correct Android 6 ROM. Go to Sammobile and enter SM-580 and then chose your region. Then download the ROM ending in PL4. When it boots, it will ask for your Google login and password. It is only if you don't know those that the FRP becomes a problem. If you can't flash the PL4 ROM, your problem is NOT the FRP lock, even if Odin says it is. Also, once you get Android 6 to boot, your tablet will automatically update to the latest version from Samsung so long as you don't try to root or install TWRP before it has a chance to update.
edit: BTW, when flash the PL4 ROM, flash only the AP and BL modules.

Yeah i did some research following all that up and noticed i had the wrong ROM because some sites on the internet are very non descriptive, but like i said above i got it working shortly after and i now have a linageOS rom with a more recent android version, all working, thank you anyways for responding how to properly resolve this ^^

New user in need of help
lewmur said:
FRP lock should not prevent you from flashing a stock ROM via Odin. But you have to flash the correct Android 6 ROM. Go to Sammobile and enter SM-580 and then chose your region. Then download the ROM ending in PL4. When it boots, it will ask for your Google login and password. It is only if you don't know those that the FRP becomes a problem. If you can't flash the PL4 ROM, your problem is NOT the FRP lock, even if Odin says it is. Also, once you get Android 6 to boot, your tablet will automatically update to the latest version from Samsung so long as you don't try to root or install TWRP before it has a chance to update.
edit: BTW, when flash the PL4 ROM, flash only the AP and BL modules.
Click to expand...
Click to collapse
Hello, I was trying to Root my Samsung SM-T510 10.1 Tablet. I am now stuck in the Download Mode in Odin & only have red writing up in the left hand corner. Any Help or advice is much appreciated. I've tried holding the buttons and it pops right back up to the same screen saying Don't power down. with the android logo! Any Advice?
---------- Post added at 05:45 PM ---------- Previous post was at 05:27 PM ----------
johnnyonetime said:
Hello, I was trying to Root my Samsung SM-T510 10.1 Tablet. I am now stuck in the Download Mode in Odin & only have red writing up in the left hand corner. Any Help or advice is much appreciated. I've tried holding the buttons and it pops right back up to the same screen saying Don't power down. with the android logo! Any Advice?
Click to expand...
Click to collapse
The error codes I'm getting are
VBMETA: ERROR VERIFYING VBMETA IMAGE: OK_NOT_SIGNED (3)
CUSTOM VBMETA
VBNETA : NO SIGN INFO
VBNETA ,
It's all in red letters.
Thanks for any advice!

Hallo @ all. I hope your can help me with a Problem.
I bought last week from Amzon a Samsung Galaxy Tab S6 Lite P610.
I do not can Setup this Tablet why the WiFi Switch turn off by selfe. It is so fast that I am not able to put in the WiFi password. So I set up the Tablet with cable connection between the Tab and my Galaxy note 10 +. Only my accounts are not copied why for that it needed WiFi.
I searched for this Problem on Google and it seems a lot of People has this Problem after the Update to Android 11 but nowhere is a Way to solve this Bug. Also Bluetooth crashes with the Message App will be end.
So I thought it is a Problem with the OTA and when not all People has the Problem than I will flash the Rom new through Odin.
So I loaded Frija (SamFirm are not able to download a Rom). I typed in SM-P610 and csc is DBT.
It loaded the Rom.
In the zip are no CP File but I never flashed a Tab so maybe it is ok.
I restarted the Tab in the download Mode.
In Odin I set up BL, AP, and in CSC I set CSS Tar not Home CSC.
Than I started the Flash Process.
Odin still Flash and hung on download File (system.img).
On the Tab comes the Message:
FRP Lock
FRP Lock Pit File ignored Download.
On the Tab are no changes. I can still reboot in system. So I google and thought ok I reset the Tab. So I did it and repeated the Prozedure but the same Problem, FRP block the flash of the Firmware. Samsung can not help. The customer service only says do a reset. The Android 12 Update comes in May 22. But without Internet the Tab is useless.
Anybody maybe has a Idea?
I do not has make changes. I do not turn on USB debugging, do not activate OEM Unlock and do not activated the Developer Option.

wulfgardodin said:
Hallo @ all. I hope your can help me with a Problem.
I bought last week from Amzon a Samsung Galaxy Tab S6 Lite P610.
I do not can Setup this Tablet why the WiFi Switch turn off by selfe. It is so fast that I am not able to put in the WiFi password. So I set up the Tablet with cable connection between the Tab and my Galaxy note 10 +. Only my accounts are not copied why for that it needed WiFi.
I searched for this Problem on Google and it seems a lot of People has this Problem after the Update to Android 11 but nowhere is a Way to solve this Bug. Also Bluetooth crashes with the Message App will be end.
So I thought it is a Problem with the OTA and when not all People has the Problem than I will flash the Rom new through Odin.
So I loaded Frija (SamFirm are not able to download a Rom). I typed in SM-P610 and csc is DBT.
It loaded the Rom.
In the zip are no CP File but I never flashed a Tab so maybe it is ok.
I restarted the Tab in the download Mode.
In Odin I set up BL, AP, and in CSC I set CSS Tar not Home CSC.
Than I started the Flash Process.
Odin still Flash and hung on download File (system.img).
On the Tab comes the Message:
FRP Lock
FRP Lock Pit File ignored Download.
On the Tab are no changes. I can still reboot in system. So I google and thought ok I reset the Tab. So I did it and repeated the Prozedure but the same Problem, FRP block the flash of the Firmware. Samsung can not help. The customer service only says do a reset. The Android 12 Update comes in May 22. But without Internet the Tab is useless.
Anybody maybe has a Idea?
I do not has make changes. I do not turn on USB debugging, do not activate OEM Unlock and do not activated the Developer Option.
Click to expand...
Click to collapse
There is no CP because it is a tablet and not a phone. The CP is for the phone modem. You must enable Dev Options and OEM unlock to flash anything. Even stock. But before I'd try flashing a new ROM, I'd factory reset the tablet via recovery to see if that would fix the wifi and bluetooth problems.

Ok. I have solved the Problem. My Odin Version was to old. I User Odin 3.7.x
But to new flash the Rom solved not the Problem. Wifi still turns off by selfe. I send the Tqb back to Amazon. Friday I get a new one not from Amazon Warehous. Still lower Space, the 64 GB Variant. I hope it has still Android 10. When it has Android 10 and WiFi works, I do not update for the Moment.