Develop Bugs

Bricked SM-T807a

Friend gave me this tablet for free cuz he said he tried rooting it via kingroot and it worked then he tried doind a TWRP recovery but it bricked... so i found some files from a previous bricked thread and i flashed the recovery and system files via odin and they passed but tablet still boots and shows "System software not authorized by AT&T has been found on your tablet" im at a lost right now and was wondering if there are any other options. It'll boot into download mode says knox tripped:1 i tried samsung smart switch but it crashes after i enter the s/n...any help would be appreciated.
Thanks

What recovery did you try? 805? Have you tried to connect it to kies? Won't boot into recovery at all? I have a 807a myself I used kingroot... The problem with this variant is it has a locked bootloader

Ask someone with root to pull the recovery from their device.

wojo797 said:
What recovery did you try? 805? Have you tried to connect it to kies? Won't boot into recovery at all? I have a 807a myself I used kingroot... The problem with this variant is it has a locked bootloader
Click to expand...
Click to collapse
Yeah, I tried the 805 recovery it said it passed but still comes up with that att screen...yeah i told him he should have asked me first before he tried flashing twrp woulda saved him a lot lol... like the quote below states...would you be able to pull the recovery from your device and upload it to mega or dropbox for me? youd be a lifesaver
ashyx said:
Ask someone with root to pull the recovery from their device.
Click to expand...
Click to collapse
Thanks i asked above. Do you know anyone with root that could pull it for me?

yankeefreak924 said:
Yeah, I tried the 805 recovery it said it passed but still comes up with that att screen...yeah i told him he should have asked me first before he tried flashing twrp woulda saved him a lot lol... like the quote below states...would you be able to pull the recovery from your device and upload it to mega or dropbox for me? youd be a lifesaver
Thanks i asked above. Do you know anyone with root that could pull it for me?
Click to expand...
Click to collapse
Yo tengo esa tableta, t807a AT&T en Lollipop y está roteada. Si me dicen cómo extraer la recuperación lo hago y se los paso.

Need Rooted patched image after 10.0.7 aka 10.0.3

Just Updated to 10.0.7 via full ota update lost root access

mytechtb said:
Just Updated to 10.0.7 via full ota update lost root access
Click to expand...
Click to collapse
If you bothered to do a 5min search you would have found it by now. If you'd spent 15min to learn how to do it yourself... you would be rooted by now.

Kirahvi said:
If you bothered to do a 5min search you would have found it by now. If you'd spent 15min to learn how to do it yourself... you would be rooted by now.
Click to expand...
Click to collapse
I'd like to agree with u on that second part but it keeps telling me path not found sadly...not sure what I'm doing wrong got the image in c drive in my atform tools and still happening read the instructions 10 plus times myself. I've actually had to do the same process on my xiaomi a2 lite and worked easily but not this time for OnePlus

rob420p said:
I'd like to agree with u on that second part but it keeps telling me path not found sadly...not sure what I'm doing wrong got the image in c drive in my atform tools and still happening read the instructions 10 plus times myself. I've actually had to do the same process on my xiaomi a2 lite and worked easily but not this time for OnePlus
Click to expand...
Click to collapse
Do you have some data plan with your carrier? Just boot a patched boot.img from the previous OOS version. WiFi will not work but you can still use LTE to direct install magisk then reboot.

Kirahvi said:
If you bothered to do a 5min search you would have found it by now. If you'd spent 15min to learn how to do it yourself... you would be rooted by now.
Click to expand...
Click to collapse
so cold time FYI i did downloaded the ota file and patched it with magisk and flashed through the cmd...but i didnt worked at all even i cant able to boot my device until i flash stock boot

morback said:
Do you have some data plan with your carrier? Just boot a patched boot.img from the previous OOS version. WiFi will not work but you can still use LTE to direct install magisk then reboot.
Click to expand...
Click to collapse
Thanks I'll give it a try that way I have unlimited data luckily

mytechtb said:
so cold time FYI i did downloaded the ota file and patched it with magisk and flashed through the cmd...but i didnt worked at all even i cant able to boot my device until i flash stock boot
Click to expand...
Click to collapse
Did you remember to tick the "Preserve AVB 2.0/dm-verity" when patching the boot image in magisk?

This method work for me https://www.reddit.com/r/oneplus/co...twrp/?utm_medium=android_app&utm_source=share
One plus 7t pro McLaren 10.0.6 update to 10.0.0.7 without lose root privileges

Question Dsu working..

Hey idk if it's just me. Cause I was late finding out bout the android 12 beta. And I failed to read everything. So I got the tmo converted to eu. So ya needless to say bootlooped. But I noticed in developers options dsu had both slots filled and it actually worked I can go back and forth to android gms gsi. Or just pure asop. So check see if anyone else has that working?

I'm sorry can you explain little more, the beta loaded DSU with both asop and android gms images?

Ya it did. I didn't know at the time I posted this that the gsi was out also. It was the first time I seen dsu working. I have been following treble since day one. I am glad google did not scrap it. Just got excited when I posted that.

amaroney55 said:
Ya it did. I didn't know at the time I posted this that the gsi was out also. It was the first time I seen dsu working. I have been following treble since day one. I am glad google did not scrap it. Just got excited when I posted that.
Click to expand...
Click to collapse
I see the two options in my developer settings. How does it work exactly? Will being rooted cause any problem loading it? Does it only stay loaded only until next reboot?

Shooter7889 said:
I see the two options in my developer settings. How does it work exactly? Will being rooted cause any problem loading it? Does it only stay loaded only until next reboot?
Click to expand...
Click to collapse
I get an error message when selecting

Oh. I haven't tried clicking on either. I'll try

When I clicked on one w/gms it asked for my fingerprint then started downloading. I cancelled it (untill I find out if it is just for one boot or if it cld wipe my phone or what have you)

I wouldn't bt

It doesn't. Will just flip over the beta the gms is with google other is pure android when you get ready to go back to stock or whatever your using look in the notifications.

amaroney55 said:
It doesn't. Will just flip over the beta the gms is with google other is pure android when you get ready to go back to stock or whatever your using look in the notifications.
Click to expand...
Click to collapse
Cool thanks I'll check it out

Your bootloader has to be unlocked tho.

amaroney55 said:
Your bootloader has to be unlocked tho.
Click to expand...
Click to collapse
I'm unlocked and rooted..le2125 on EU rom

amaroney55 said:
Your bootloader has to be unlocked tho.
Click to expand...
Click to collapse
I'm unlocked and rooted..le2125 on EU rom

Says it is working on mine , but it just boots to an un-setup OnePlus Android OOS 11...US Unlocked.

I tried it too then someone on telegram tols me that dsu on oneplus phones used vendor of oos 11.but i saw a video guide of someone that has the nord and he used the dsu method and he got android 12 gsi..strange thing

Ya see that is what I am not understanding. Treble was only to change the system.img. and nothing else. Then they started messing with the vendor and that defeated the purpose of a generic img. To me if your going to change the system and vendor and recovery might as well be OEM only. But I didn't have a problem with it on oneplus 9 pro using 11. But my oneplus 7 pro it will install it but will not boot to it. Using 10 or 11.

Oh I am using a tmo converted to eu.

Is flashing a custom ROM worth anymore?

I would really like to try xiaomi.eu on mi 10T, but it needs open boot loader, which can be detected, and then all app's don't work.
Yes I know you can use magisk and have an eternal battle with safety net while some apps still refuse to work (Mcdonalds is a good example).

rajatapaus00 said:
I would really like to try xiaomi.eu on mi 10T, but it needs open boot loader, which can be detected, and then all app's don't work.
Yes I know you can use magisk and have an eternal battle with safety net while some apps still refuse to work (Mcdonalds is a good example).
Click to expand...
Click to collapse
I have an mtk phone which i upgraded to android 10(q) when I flashed pixel 10 gsi my bootloader was set to locked, so you just need to find the line for it in a build.prop (search the internet) and add it in a module or something
that way system thinks bootloader is locked even if its not

flairepathos.info said:
I have an mtk phone which i upgraded to android 10(q) when I flashed pixel 10 gsi my bootloader was set to locked, so you just need to find the line for it in a build.prop (search the internet) and add it in a module or something
that way system thinks bootloader is locked even if its not
Click to expand...
Click to collapse
I heard that modifying that requires rooting.

rajatapaus00 said:
I heard that modifying that requires rooting.
Click to expand...
Click to collapse
Yes or
you can just flash twrp
copy the needed file to pc edit what you want
overwrite the old one in phone
flash stock recovery and voila

Question A possible solution for OOS Stock Cam to work on Custom A12 roms

Guys, I have experienced and heard a lot from others that they come back to stock rom after enjoying the custom ROM for a week or two
just because they missed the OOS Stock cam application performance and features. And we all know, there isnt a custom ROM in which
OOS Cam works flawlessly. I might have a possible solution for this. To be frank, I havent tried this solution yet and I m no expert on
developing ROMS. This is just an idea. Therefore, to confirm this, I m putting forward my idea to the community.
Normally, GCAM works fine for me in Custom ROMS for taking few PICS here n there. But the problem arises when I goto a Vacation trip
or attend a party/function where Camera is an essential requirement. And GCAM just cant beat the shear video and photo performance
of stock OOS CAM. So, my solution might help guys in similar situations.
The possible solution maybe:-
1) Install an awesome Custom ROM of choice primarily on device.
2) Select DSU loader from the developer options
3) Choose the suitable Stock DSU Image. This will install the Stock ROM without affecting the primary custom ROM.
Just go thru normal step process and leave it at that. Remember we only need Stock OOS camera app from this ROM.
Therefore, during normal usage days. just use the CUstom ROM which doesnt require clicking videos or many photos.
However, during trips/vacations/functions, just quickly restart your device to switch to the DSU Image.
and voila, USE THE STOCK OOS CAM as usual and save all photos/videos.
Please let me know if this idea will work theoretically and practically?

I was actually wondering if dual boot was possible. I had no idea about DSU Loader before.
Is it possible to install OOS into the DSU Loader though? I did some quick research and it's meant for GSIs.
Would be cool if we had a tool like this that allowed OOS to be the secondary so we have a fully working custom ROM and OOS when needed.

I have tried dsu loader and it sent me to the your devuce is corrupt red screen.had to start from scratch.also the dsu loader will relock your bootloader.

gillim74 said:
I have tried dsu loader and it sent me to the your devuce is corrupt red screen.had to start from scratch.also the dsu loader will relock your bootloader.
Click to expand...
Click to collapse
lol, what? DSU doesn't lock your bootloader. Actually, in order to use DSU, your bootloader needs to be unlocked.
Please, double-check before spreading false information.

EtherealRemnant said:
I was actually wondering if dual boot was possible. I had no idea about DSU Loader before.
Is it possible to install OOS into the DSU Loader though? I did some quick research and it's meant for GSIs.
Would be cool if we had a tool like this that allowed OOS to be the secondary so we have a fully working custom ROM and OOS when needed.
Click to expand...
Click to collapse
I have seen that a custom DSU loader is also present which can easily install custom ROMS.
If we make OOS primary and custom ROM secondary and use that secondary ROM as primary. Wont that work?
i assume secondary DSU Custom ROMS dont have limited functionality.

sunny1689gupta said:
I have seen that a custom DSU loader is also present which can easily install custom ROMS.
If we make OOS primary and custom ROM secondary and use that secondary ROM as primary. Wont that work?
i assume secondary DSU Custom ROMS dont have limited functionality.
Click to expand...
Click to collapse
I was reading that calls don't work on the secondary ROM but maybe that was in that specific instance. I didn't spend a lot of time on reading.
The custom loader I saw seemed to only be for GSIs too which is why I asked if it can be used for regular ROMs.

Hmm.. nice point. Lets see if an expert can reply here

ekin_strops said:
lol, what? DSU doesn't lock your bootloader. Actually, in order to use DSU, your bootloader needs to be unlocked.
Please, double-check before spreading false information.
Click to expand...
Click to collapse
It did mine so i do know what i am talking about.i wouldnt post something i didnt experience personally.i did it both ways with it locked and unlocked and both times put me at the red your device is corrupt screen.

gillim74 said:
It did mine so i do know what i am talking about.i wouldnt post something i didnt experience personally.i did it both ways with it locked and unlocked and both times put me at the red your device is corrupt screen.
Click to expand...
Click to collapse
which option did u choose? Did u choose the right GSI DSU file. How much I know there are 4 to 5 options.

That could have been the issue choosing the wrong one.i didnt think they would give you the option to install one if it didnt work but that very well could have been the issue.i believe i chose the last option.
sunny1689gupta said:
which option did u choose? Did u choose the right GSI DSU file. How much I know there are 4 to 5 options.
Click to expand...
Click to collapse

gillim74 said:
It did mine so i do know what i am talking about.i wouldnt post something i didnt experience personally.i did it both ways with it locked and unlocked and both times put me at the red your device is corrupt screen.
Click to expand...
Click to collapse
You do know that that screen is always present when you have an unlocked bootloader, right? Lol

TheKnux said:
You do know that that screen is always present when you have an unlocked bootloader, right? Lol
Click to expand...
Click to collapse
Yes its not the yellow screen when you boot.it was a red screen that says your device is corrupt and cannot boot please visit the link from another device.

@gillim74 that's literally the screen I have every time I boot or restart my phone and it still successfully boots.

@sunny1689gupta could you PM if you don't mind? Either on here or telegram. Same username.

TheKnux said:
@gillim74 that's literally the screen I have every time I boot or restart my phone and it still successfully boots.
Click to expand...
Click to collapse
What os are you running

gillim74 said:
What os are you running
Click to expand...
Click to collapse
OOS.

TheKnux said:
OOS.
Click to expand...
Click to collapse
I think i have a messed up a slot.someone deleted the logical partition to try and flash a gsi and it dont flash roms right.i cant find a backup of one and ive done the whole msm thing.

gillim74 said:
I think i have a messed up a slot.someone deleted the logical partition to try and flash a gsi and it dont flash roms right.i cant find a backup of one and ive done the whole msm thing.
Click to expand...
Click to collapse
If you have a fully working slot with no issues, flash this via adb sideload or twrp. Just letting you know that the screen you're referring to is a known issue when having an unlocked bootloader when using OOS11 as a base. I DID NOT have this screen when running A12 Open Betas, even with an unlocked bootloader.

TheKnux said:
If you have a fully working slot with no issues, flash this via adb sideload or twrp. Just letting you know that the screen you're referring to is a known issue when having an unlocked bootloader when using OOS11 as a base. I DID NOT have this screen when running A12 Open Betas, even with an unlocked bootloader.
Click to expand...
Click to collapse
Cool thanks for the help and info

gillim74 said:
It did mine so i do know what i am talking about.i wouldnt post something i didnt experience personally.i did it both ways with it locked and unlocked and both times put me at the red your device is corrupt screen.
Click to expand...
Click to collapse
"It did mine, therefore it must be a fact that it's how it works". NO. Again, the DSU loader needs an unlocked bootloader. What happened or what it didn't happen to your device is irrelevant. It's a FACT that your DSU doesn't LOCK your bootloader because it would self-corrupt itself by doing that since the DSU needs an unlocked Bootloader.
Imagine developers making DSU that requires an unlocked bootloader, but in the process of flashing a GSI (Generic System Image), it will lock the bootloader by itself and brick itself. That absolutely makes no sense, and neither it is coded to work like that.