yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Tab A series Questions & Answers] ashyx:
I think the actual crux of the problem is the region this tablet is from. The system partition is denoted as revision 2, so it cannot be downgraded. Probably the reason why the combo firmware doesn't work either.

What's needed is the correct firmware.

I suggest you try the firmware below:

https://samfrew.com/download/Galaxy__Tab__A⑥__/9q2e/KOO/T580XXU4CRJ9/T580KOO4CRK1/
[Samsung Galaxy Tab A series Questions & Answers] saznat:
Thanks for staing with me on this. I'll give this a try.
[Samsung Galaxy Tab A series Questions & Answers] saznat:
Yes, I tried that ROM and nearly half of the other regions that are on there and they

all fail as soon as it tries to flash system.img.

I've also managed to extract the PIT file from the tablet and it doesn't match the ones in the ROMS I've downlooaded. It seems to have two extra entries, STEADY and CARRIER, also, many of the addresses and block sizes are wrong. I guess this might be the system problem, because the system partition is not the right size.

I'm guessing that if I could flash the correct PIT, then I stand a chance of flashing a combination ROM or Stock ROM. Unfortunately, I can't flash any PIT file or CSC because the FRP Lock

prevents it. And I can't flash any stock AP or even just system.img until the partitions are fixed.

Are there any options left without sending it to Samsung who insist that regardless of anything, they won't touch it without replacing the motherboard, as that's policy with any modded device. The cost wouldn't be much less than just getting a new one!

Is there something a high street repairer can do, which I can't?
[Samsung Galaxy Tab A series Questions & Answers] ashyx:
Like I mentioned earlier in this thread I suspected that this device may be from a carrier and the system partition may be a different size.

Ok so let's go back to basics and see if we can work out what's needed.

Can you provide me with that PIT and the serial number of the device and any other info on the device itself?

Where did you purchase this device and in which country?

Also how did you manage to extract the PIT?

Another thing that confuses is how this initially happened.

At some point OEM_UNLOCK must have been enabled for TWRP to have been installed in the first place.

Somehow flashing that modified rom flipped the switch and re-enabled FRP.

I think all we need do is find the correct firmware. If you can provide the details above there's half a chance to fix this.

No point sending to Samsung. As for a third party repair shop? I'm not sure what they could do without having the correct firmware.

It seems it all comes down to finding that carrier based firmware.
[Samsung Galaxy Tab A series Questions & Answers] ashyx:
Did you ever make a backup of the stock rom with TWRP before installing anything custom?

The PIT error about line 1892 will be a line of code in Odin itself that cannot execute because the PIT is wrong

Have you tried any other versions of ODIN? I would work my way down in the versions and see if any can overcome the issue.

Also all that information above seems to come from the custom roms you flashed not the original.
[Samsung Galaxy Tab A series Questions & Answers] saznat:
Yes I did make a stock backup as soon as I had installed TWRP. That was the original Marshmallow ROM. Since then I have flashed a number of different custom ROMS, so I never got OTA updates and the device hasn't been flashed back to stock since 2016. The bootloader back then was version 1, I now have version 4.

I would love to be able to flash twrp homehow and then just restore my last image, but without a system, I can't use adb or fastboot and odin won't flash a custom recovery. I'm guessing that any backups I have are useless until I can disable FRP, get back to stock and install TWRP again.

I have tried other odin versions 3.13.2, 3.10.7, 3.11.1, 3.12.3 and 3.09 and 3.12.3 Prince Comfy. They either hang because I'm flashing Android 8.1.0 or they say they succeeded, but the tablet screen shows that really annoying pink message "FRP is enabled, Ignore PIT download". Even if I flash the pit file from T580XXU4CSA1_BTU via the Pit Tab on its own, I get the same pink message.

I assume this pink message originates from the tablet itself, rather than the Odin on the PC, sending it to the tablet to display. If that's right, then I'm guessing there's no software I can use on the PC that'll flash a PIT without the tablet refusing to allow it.
[Samsung Galaxy Tab A series Questions & Answers] ashyx:
That's good news you have the original stock backup.

Can you post the boot image from it and if possible the recovery image from it too?
[Samsung Galaxy Tab A series Questions & Answers] saznat:
The original ROM was T580XXU1APG1

I downloaded that stock ROM back in 2016, so I had it (just in case)

The zip file contains the boot and recovery from that downloaded ROM. As I recall, I did reflash that ROM

a few days later as I had removed some bloat, causing problems.

The Twrp backup I did at the time wasn't as comprehensive as I thought. Here's what is in it.

31/03/2019 15:53 <DIR> .

31/03/2019 15:53 <DIR> ..

30/11/2016 08:48 33,554,432 boot.emmc.win

30/11/2016 08:48 48 boot.emmc.win.md5

30/11/2016 08:53 453,068 recovery.log

30/11/2016 08:51 1,613,701,632 system.ext4.win000

30/11/2016 08:53 53 system.ext4.win000.md5

30/11/2016 08:52 1,317,662,720 system.ext4.win001

30/11/2016 08:53 53 system.ext4.win001.md5

30/11/2016 08:52 65 system.info

9 File(s) 2,965,372,071 bytes

I'll put the boot portion of it in the attached zip file too.

/system/cscVersion.txt says:

T580BTU1APH1

Is that what you wanted?
[Samsung Galaxy Tab A series Questions & Answers] ashyx:
Did you pull that csc info from the backup or the stock firmware?
[Samsung Galaxy Tab A series Questions & Answers] saznat:
Hi. That came from the TWRP Backup.

Which seems confirmed by the stock ROM as this is what the zip contains

AP_T580XXU1APG1_CL8761055_QB10400895_REV00_user_low_ship_meta.tar.md5

BL_T580XXU1APG1_CL8761055_QB10400895_REV00_user_low_ship.tar.md5

CSC_BTU_T580BTU1APH1_CL8845067_QB10531358_REV00_user_low_ship.tar.md5

HOME_CSC_BTU_T580BTU1APH1_CL8845067_QB10531358_REV00_user_low_ship.tar.md5
[Samsung Galaxy Tab A series Questions & Answers] ashyx:
This rom that you installed that broke the device, how did you install it because from what you've said regarding it suddenly booting into recovery it suggests you installed it via ODIN?

If that is the case then was it completely stock or custom?
[Samsung Galaxy Tab A series Questions & Answers] saznat:
I started back in 2016 with stock ROM T580XXU1APG1

which I had reflashed to the device with odin once. Again, that was back in 2016.

Since then, I have had several custom ROMS which were also flashed with odin. Most were also Marshmallow as I didn't like Nougat.

In december I found [T580]_Stock-DBT-8.1.0-XXU4CRK5-FW_v1.3_by_hanspampel.zip which I flashed by installing the zip in TWRP. And that worked fine. Then a couple of weeks ago I noticed the update to this ROM with the January security update. so I downloaded [T580]_Stock-DBT-8.1.0-XXU4CSB1-FW_v1.4_by_hanspampel.zip

and proceeded to install that via TWRP. TWRP started the install, then within about 2 seconds the device restarted. It showed a blue screen with the little android man and "Installing updates" underneath. It then showed a blue screen with a leaning over android man and the text underneath was "No command".

After a couple of minutes it reboots itself, gets to the "no command" message and then it just keeps looping through this reboot sequence again.

I tried flashing stock ROM but couldn't, because of the FRP lock preventing the flashing of the PIT file or any custom binary. I tried combination Rom, same problem.

That's pretty much the life of the tablet since I bought it.
[Samsung Galaxy Tab A series Questions & Answers] ashyx:
This is what confuses me a little.

Initially you had twrp installed. You used it to install the zip of this custom rom that failed. This then causes it to boot to recovery to try and complete the update. However the recovery is now the stock recovery which suggests to me that zip also contained the stock recovery.

What I can't understand is why, why did it have the stock recovery also in the zip?

So putting all this together I believe that zip got so far as installing everything except the system.img which bombed out.

It is the CSC that causes the reboot to recovery to finish the update which couldn't complete.

However it seems the partial installation of the system.img has flipped the revision to 2.

This cannot be downgraded. Only another rev 2 ir higher system image can be flashed.

It is likely all the other firmwares that fail have revision 1 system images that are prevented from being flashed or are the wrong region or size.

Having said this then it should be possible to flash that exact same firmware that contains the rev 2 system image, but from the stock untouched firmware.

Now here's the kicker, even though the revision may be correct, because FRP is now somehow in force it may get rejected because of it being the wrong region. Catch 22!

The only way I can see to fix this is to flash a revision 2 system.img from the correct region.

How to find this is gonna be the problem?

First I would download the stock firmware of that exact rom that caused the issue and try it.

If that doesn't work then hopefully Samsung will release another update for BTU that bumps the revision and allows the system image to flash.
[Samsung Galaxy Tab A series Questions & Answers] saznat:
AAh. Sorry I donfused you. I flashed the zip in TWRP and then it rebooted. But not to recovery.

It tried to boot to system, but there is no system partition, hence the "no command" thing.

I did then try rebooting to TWRP thinking I'd restore the last image, but I couldn't get into any recovery either, because that partition was screwed too. So all I had available was Odin Mode. It appears that my PIT got screwed and destroyed sll the partitions except /data.

Flashing a the ARJ1 combination ROM without system.img gave me the stock recovery, but all that's really achieved is that I can wipe cache and data and power the device off.
[Samsung Galaxy Tab A series Questions & Answers] saznat:
Thanks for all your help with this.

So to recap. If I dowmloaded the latest (or even all the bootloader 4) ROMS for this device and then extract the system.img for each in turn, repackage it and flash it. I might get lucky with one of them?

Then if I do get lucky, with one, try booting into it and OEM unlock it.

is it just a system.img I need. Wouldn't I need to flash the CSC that goes with the system.img

and check to repartition option to load the PIT?
[Samsung Galaxy Tab A series Questions & Answers] ashyx:
This is my point though. The little android and no command image is part of stock recovery.

It says no command because it didn't find the update command that gets placed in cache to execute the wipe and update of the CSC. Basically there was nothing to update.

If there was no recovery installed it would have simply continually boot looped to the Samsung logo.

So at some point stock recovery replaced twrp during the custom rom install.

---------- Post added at 08:39 PM ---------- Previous post was at 08:29 PM ----------

Well yes that's what I assume is required which is why I suggested the system image from the absolute stock firmware of the same custom DBT image that started all this.

So to be clear, download the stock DBT firmware with the same build number as the one that broke your device and then try the system image from that as that should have the rev. 2 system.img.

It might also be an idea to ask other T580 owners what revision their system image is at.

If f any one else has rev. 2 then they may be able to shed some light on which firmware they flashed.
[Samsung Galaxy Tab A series Questions & Answers] saznat:
Is there an easy way I can tell what revision the ROMS I already downloaded are?

Does the REV00 in the file name refer to software revision?

eg AP_T580XXU4CSA1_CL15260192_QB21717304_REV00_user_low_ship_meta.tar.md5

Again. Thanks for your help with this. I'd be groping in the dark without it. Your time is much appreciated.
[Samsung Galaxy Tab A series Questions & Answers] ashyx:
Tbh I'm not sure what rev00 refers to or how to deduce what revision the system image is as this seems to be hidden in the encrypted signature itself.

All I know is the first part is the revision of the boot loader. E.g. XXU4 is rev 4.

CL refers to Change list. Not sure what QB refers to.
[Samsung Galaxy Tab A series Questions & Answers] saznat:
I'll spend some time tomorrow night trying to find and flash the original system.img

I'll let you know how it goes.

Thanks again. Good Night
[Samsung Galaxy Tab A series Questions & Answers] saznat:
Just an update for anyone interested.

I've downloaded every stock ROM for the T580 and ran compare tests of every one so that I can rule out totally identical ROMS. From what's left, I have extracted every system.img and PIT file and then done similar comparisions, ruling out identical files again.

Then I've tried flashing every system.img and they all fail because of the "FRP is enabled, ignore PIT download" block on the tablet.

I then tried flashing every PIT in turn, hoping I might hit one with a signature it accepts. That failed too because of the same error.

I used Chimera to save my PIT file from the device to PC. I don't know how reliable that is, but the saved file was 8k which is obviously worrying as the PIT should be 4k. However. Once I open it with PIT Magic and just save it without any changes, iit becomes a 4k file. I don't know if PIT Magic just saves the first 4k and truncates the rest or whether there is something odd about chimera, that it saves an 8K file.

Looking at that PIT file with PIT magic, there are 2 entries that are not in the standard T580 PIT file. CARRIER and STEADY. Many of the addresses and block sizes differ too, including system partition.

As the T580 is Wifi only, I thought that maybe I'd somehow flashed a T585 PIT at some point, so I downloaded a few T585 ROMS and extracted their PIT files. They were all identical to each other, except for the last (signature?) part. But they didn't match the PIT that chimera extracted.

So I'm left wondering whether the PIT chimera says it extracted is actually what's on the device or not. I could try flashing it to see if the FRP prevents it. But if it doesn't, I will have flashed an incorrect PIT for sure, which won't help me at all.

So I have now come to a total stop. It seems to need some software other than odin to flash a stock ROM including PIT, without triggering the device to reject it, but I suspect that whatever was used, the device would realise the PIT is about to be updated and prevent it.

So that only leaves getting rid of the FRP Lock. Which I haven't found a way to do. Without the ability to flash any system.img from stock ROM or combination ROM, I can't reset it through download mode. I can't use ADB or any other method, without having a functining android system.

So unless anyone has any idea TWRP Jedi and I haven't tried so far, then I'm beginnig to think that the only option is a new motherboard.

That's really annoying as Samsung say it'll cost a lot, making it uneconomical. I might just as well buy a new one. which is all really annoying as there is nothing mechanically wrong with the device, and if I got the chance to enter the details, I know the google account and password it was last signed in to.
[Samsung Galaxy Tab A series Questions & Answers] ashyx:
Might be worth trying post #40:

https://xdaforums.com/galaxy-tab-a/help/samsung-sm-t580-frp-lock-t3619870/page4
[Samsung Galaxy Tab A series Questions & Answers] saznat:
Hiya again.

I'll give that a go

No go I'm afraid. The dreaded pink "FRP is enabled, ignore PIT download" message appears on the device and the flash fails.

<ID:0/003> Added!!

<ID:0/003> Odin engine v(ID:3.1301)..

<ID:0/003> File analysis..

<ID:0/003> Total Binary size: 1831 M

<ID:0/003> SetupConnection..

<ID:0/003> Initialzation..

<ID:0/003> Set PIT file..

<ID:0/003> DO NOT TURN OFF TARGET!!

<ID:0/003> Get PIT for mapping..

<ID:0/003> Firmware update start..

<ID:0/003> NAND Write Start!!

<ID:0/003> SingleDownload.

<ID:0/003> boot.img

<ID:0/003> cm.bin

<ID:0/003> modem.bin

<ID:0/003> param.bin

<ID:0/003> recovery.img

<ID:0/003> sboot.bin

<ID:0/003> system.img

<ID:0/003> FAIL!

<ID:0/003>

<ID:0/003> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1
[Samsung Galaxy Tab A series Questions & Answers] saznat:
Will Octoplus FRP Lock solve my problem

Hi TWRP Jedi. I hope you're still monitoring this thread.

I have found references to the Octoplus FRP Tool

https://octoplusbox.com/en/products/frp-tool/

I know that getting rid of the FRP lock, so I can flash a PIT and then hopefully a system.img is just not going to happen using download mode and Odin.

I'm not sure how Uart works or if it can bypass the blocks on the deice to reset the FRP, so I can use Odin to get a stock ROM on it with correct partitioning.

Do you have any knowledge of how Octoplus works and whether it's likely to solve my problem?

It'd be nice to have an expert opinion before I fork out for a solution that might be pointless.

Thanks as always for your help.
[Samsung Galaxy Tab A series Questions & Answers] saznat:
If anyone is following this link. The Octoplus FRP Tool is useless for the T580. It's an expensive waste of money and time. Maybe it does work on other devices, but for the T580, The UART options are greyed out. This means that I have the options to flash a combi ROM or stock ROM. Options that I've already tried for free without having to fork out £70 for a dongle that just does the same thing.

What I want to do seems dead simple, but it's proving impossible to achieve. I think this could be a working tablet, but the cost of achieving it is just not economically viable. It's probably cheaper to just buy a new one.
[Samsung Galaxy Tab A series Questions & Answers] GastonC:
Where can we find the revision 4 combination firmwate
[Samsung Galaxy Tab A series Questions & Answers] Leboboy19:
Guys I'm having the exact same problem, does any one have any fix for it, my tab is still brand new not a scratch on it. ?
[Samsung Galaxy Tab A series Questions & Answers] akohle:
I got a similar problem. Stuck on 32% with "no command".

For usual, I frozen the emergency service, but I unfrozen all to update apps in samsungs store.

After a restart I got a frp lock, rom was a modified stock of T580XXS5CTK1 and twrp.

I was surprised that I can't solve it this time.

I bought another Tablet, but the A6 is a unique one, I would be very thankful for some help,

don't know a tablet is solid, stable and easy to repair like A6, some games it still can handle.

Original packaging, invoice, all available, passwords, acc details n pin known, help me please.

This was my first own tablet and I love it.
[Samsung Galaxy Tab A series Questions & Answers] Piscofull:
Encontre la solucion

El problema esta en en recovery del frimware. Despues de tenerlo en el servicio tecnico y querer cobrarme 150€ por el arreglo decidi de nuevo probar lo consegui reparar.

Mod translation: I found the solution

The problem is in firmware recovery. After having it in the technical service and wanting to charge me €150 for the fix, I decided to try again and managed to repair it.
[Samsung Galaxy Tab A series Questions & Answers] Badger50:
Greetings, and welcome to XDA. As a friendly reminder, we ask all members to please post in English as stipulated by XDA Rule #4:

Spoiler content hidden.

Thank you for your cooperation, and enjoy your stay on XDA.

-Regards: Badger50
[Huawei Mate 20 Pro Questions & Answers] odino77:
I need a little help.

I removed some boatware from my Mate 20 Pro using adb shell etc ...

Now, however, there is no longer any video player.

Could you link to the stock app to play videos?

Or can you tell me the name com.xxxxx.yyyyy?

At least I try to reinstall it ....

Best regards!
[Huawei Mate 20 Pro Questions & Answers] Darkat70:
You can try this.

https://www.apkmirror.com/apk/huawe...huawei-video-8-2-10-310-android-apk-download/

Com.huawei.himovie.overseas ?
[Huawei Mate 20 Pro Questions & Answers] zolaisugly:
From stock .187 UK

https://mega.nz/#!ygxVkAZY!Nhg9QWryycgI84QYavtN5AsCdjWgnlIjCi_BW1crYmU
[Huawei Mate 20 Pro Questions & Answers] odino77:
Many thanks to everyone, solved.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Q&A, Help & Trouble] thew-tab:
I bought a galaxy tab pro 12.2 sm-t900 on ebay, the listing said wifi was lost once the seller improperly installed a custom rom. I tried flashing various stock roms thru Odin to try and fix the wifi not working (couldn't find any firmwares earlier than 5.1.1). once that didn't work, I tried a few customs with the same results. Today, I finally downloaded a build prop. editor (thru an ethernet cable) and noticed that is said the tablet was a sm-t900 (which, I knew), but it also said it was a v1awifi, instead of the v2awifi that this tablet actually is. Which build prop. can I change in order to get the tablet recognized as the v2awifi. Or is there any other way to get this tablet recognized properly? I am hoping this may fix the wifi issue. Any help will be greatly appreciated.
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] SimplyJeevS:
• Changelog •

23/07/19 bday update

Dot source updated to 3.1

Los upstream

Kernel updated to (derp) illusion 3.7

Added few fixes and removed junk for smoother ui navigation

• Future Plans •

Thermal engine

Adjust notch padding to have proper height

*maybe* Swap vibration pattern from pixel 2 (current) to the once used in miui

*maybe* Increase max number of notification counts

*maybe* add livedisplay and all patches needed

*maybe* Include dirac from miui

Any suggestion from you guys (if its realistic :p)

• Legacy Changelog •

• Changelog •

• Initial [24/03] •

• Device side stuff •

• Added proper padding for notch and rounded corners •

• Added an overlay for the notch •

• Enable proximity check on wake •

• Pixel 2 vibration patterns •

• Inital DotOs bring up •

• Device side bugs •

• Ir cam is not working currently •

• DotOS 3.0 [25/03] •

• Device side stuff •

• Fixed IR cam on face unlock! enjoy seeing yourself as a ghost again :p •

• Los-kernel upstream •

• Device side bugs •

• You will have to tell me! •

• Planned for next update •

• Adding thermal configs •

• Going official •

• DotOS 3.0 [OFFICIAL] [26/03] •

• Device side stuff •

• Now Official! •

• Updated Device tree, sdm845-common •

• Bunch of kernel upstreams •

• Device side bugs •

• You will have to tell me! •

• Planned for next update •

• Adding thermal configs (some time soon its more complicated then i tought) •

• Adding any suggestions you guys might leave in the thread •

Some SS attached

​
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] SimplyJeevS:
Reserved

If you enjoy my work consider donating to my personal paypal. (if you have some spare chain at least :p) https://www.paypal.me/SimplyJeevS

Special thanks

xZeeshan my PERU tester

All devs i bothered + the onces listed under here

abhishek987

akhilnarang

wajidkh08

​
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] Glassgg:
damn sir you on fire :svetius:
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] Mohammed779:
Oh man, waiting for the IR camera,

thanks!
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] SimplyJeevS:
Working on it
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] Adyatan:
Thermal Profiles?
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] dmenaze:
Bro,could you add pocket mode?...bcs my screen is quite sensitive to touch in the pocket....it goes to Emergency or opening apps
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] SimplyJeevS:
thats a source thing i cant add that sorry
[Xiaomi Poco F1 ROMs, Kernels, Recoveries, & Other ] SimplyJeevS:
will be looking to add them in oen of the future updates for sure