Develop Bugs

Looking to be pointed in the direction of a root for Galaxy Tab A6 sm-t280

Hey guys,
Been searching for a few days now ive tried several root methods
the ones from playstore like
Kingroot
Kingoroot
Kingoroot desktop
Its a galaxy tab a6 running android 5.1.1
Build number LMY47V.T280XXU0APB6
All of the above say they can root it but they all failed
I have seen posts on forums such as this one offering custom roms for the device so I must assume there is a root somewhere and I just cant find it.
Any help would be extremely apreceated

ilikenoodles321 said:
Hey guys,
Been searching for a few days now ive tried several root methods
the ones from playstore like
Kingroot
Kingoroot
Kingoroot desktop
Its a galaxy tab a6 running android 5.1.1
Build number LMY47V.T280XXU0APB6
All of the above say they can root it but they all failed
I have seen posts on forums such as this one offering custom roms for the device so I must assume there is a root somewhere and I just cant find it.
Any help would be extremely apreceated
Click to expand...
Click to collapse
Nope, no root for this device until an exploit is found.
Where is this custom rom you speak of?

I don't remember sorry
Is it likely one will be found a exploit I mean ?

ilikenoodles321 said:
I don't remember sorry
Is it likely one will be found a exploit I mean ?
Click to expand...
Click to collapse
I've tried everything possible so far to obtain root.
Hopefully eventually one of the apps like Kingroot will work.
Why the heck Samsung locked the bootloader on this device I have no bloomin idea!

Me either no contactless pay as no cellular so why ?
I got mine direct from Samsung and the bloat is horrific
8gb model and over half of it is unusable and without a root an sd card isent really much help
In essence I have gta sa installed and can't put anything else on its infuriating!

ilikenoodles321 said:
Me either no contactless pay as no cellular so why ?
I got mine direct from Samsung and the bloat is horrific
8gb model and over half of it is unusable and without a root an sd card isent really much help
In essence I have gta sa installed and can't put anything else on its infuriating!
Click to expand...
Click to collapse
It's still possible to customize the stock rom.
I have made some modifications to it and flashed no issues.
This means it can at least be debloated.

How would I do that exactly nothing I have tried has worked

Did you try with kingroot desktop?

mihailrusia said:
Did you try with kingroot desktop?
Click to expand...
Click to collapse
I did indeed.

mihailrusia said:
Did you try with kingroot desktop?
Click to expand...
Click to collapse
Like I said I have already tried all methods.
---------- Post added at 10:29 AM ---------- Previous post was at 10:28 AM ----------
ilikenoodles321 said:
How would I do that exactly nothing I have tried has worked
Click to expand...
Click to collapse
Tried what?

Like all the things in android to move data and apps they all greyed out.
Cant u download the stock rom for a device modify it on your computer then flash it to your device ?
IS that a thing?

ilikenoodles321 said:
Cant u download the stock rom for a device modify it on your computer then flash it to your device ?
IS that a thing?
Click to expand...
Click to collapse
That's what I'm referring to. I have modified the stock rom image and reflashed it.

sweet! is there a guide to doing this im confident I can its just ive never done it before.

ilikenoodles321 said:
sweet! is there a guide to doing this im confident I can its just ive never done it before.
Click to expand...
Click to collapse
You're going to need to use Linux, recommend Ubuntu.

ashyx said:
That's what I'm referring to. I have modified the stock rom image and reflashed it.
Click to expand...
Click to collapse
ashyx said:
You're going to need to use Linux, recommend Ubuntu.
Click to expand...
Click to collapse
I've just bought a SN 280 Tab A6 and I've been looking to root it to be able to take off some of the apps I don't use.
Is there any root, twrp or cusmom ROM for this device?
Thanks
---------- Post added at 13:51 ---------- Previous post was at 13:50 ----------
ilikenoodles321 said:
sweet! is there a guide to doing this im confident I can its just ive never done it before.
Click to expand...
Click to collapse
Any news ?

gugas123 said:
I've just bought a SN 280 Tab A6 and I've been looking to root it to be able to take off some of the apps I don't use.
Is there any root, twrp or cusmom ROM for this device?
Thanks
---------- Post added at 13:51 ---------- Previous post was at 13:50 ----------
Any news ?
Click to expand...
Click to collapse
Did you even read this thread? :banghead:

ashyx said:
It's still possible to customize the stock rom.
I have made some modifications to it and flashed no issues.
This means it can at least be debloated.
Click to expand...
Click to collapse
Hello ashyx
I have the sm-T285m. Yes, I could not root it using the usual programs out there. Any way to inject root into the system image and then reflash it through odin? (as you mentioned you have managed to debloat it-maybe a dumb question as am sure you already looked into it) I recall trying to do such a thing on Huawei Mediapad x2 when there was no root but ran into issues after I accidentally overwrote my entire windows o/s and disk with linux and then gave up (had to extract files from image, add the su then recompile something like that?...from memory over a year back and was only my first and only foray into linux) The odin tar files are separate ones for modem, system, bootloader etc.
Thanks

mac231us said:
Hello ashyx
I have the sm-T285m. Yes, I could not root it using the usual programs out there. Any way to inject root into the system image and then reflash it through odin? (as you mentioned you have managed to debloat it-maybe a dumb question as am sure you already looked into it) I recall trying to do such a thing on Huawei Mediapad x2 when there was no root but ran into issues after I accidentally overwrote my entire windows o/s and disk with linux and then gave up (had to extract files from image, add the su then recompile something like that?...from memory over a year back and was only my first and only foray into linux) The odin tar files are separate ones for modem, system, bootloader etc.
Thanks
Click to expand...
Click to collapse
I already tried prerooting the system image.
It wont boot because the boot.img needs to be patched and you can't patch the boot.img on a bootloader locked device.
I even asked Chainfire if there was any other way and he said no.

ashyx said:
I already tried prerooting the system image.
It wont boot because the boot.img needs to be patched and you can't patch the boot.img on a bootloader locked device.
I even asked Chainfire if there was any other way and he said no.
Click to expand...
Click to collapse
Thanks Ashyx...you mentioned you managed to debloat it. I tried ext4unpacker (maybe archaic now though recall it worked on 5.0.2) to separate the system.img into components but could not. I am interested in editing system image
(A) change dpi (increase the lcd density to 380 or so to get things bigger),
(B) change system font (put in a preferred ttf font),
(C) remove many unneeded (for me) google apps from the system folder, and
(D) enable mobile data auto on off for mms via the features.xml or others.xml. Do you think these could be done (you already mentioned the debloat).
typically i managed to get all of the above done if rooted.
Any advice appreciated on how to do this unpacking and repacking.
Thanks
does this help? opensouce kernel?
(again maybe preaching to the choir but thought I'd ask-not knowledgeable here but posting if it helps in getting to a semi-rooted type state somehow)
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=sm-t285
btw i 'managed' to get oem unlock to show as checked permanently...does that mean the bootloader is unlocked now? (cross flashed through odin the 285 on my 285m the system CP file...and reverted back to 285m-no difference though in network as modem was still 285m as was partition and BL-reflashed the BL as well separately for 285m-after all this shows oem unlock checked-when i got the device new it was unchecked)
edit...from what it appears, it means it CAN be unlocked, yes? but not actually unlocked?
http://forum.xda-developers.com/showpost.php?p=67361863&postcount=9

mac231us said:
Thanks Ashyx...you mentioned you managed to debloat it. I tried ext4unpacker (maybe archaic now though recall it worked on 5.0.2) to separate the system.img into components but could not. I am interested in editing system image
(A) change dpi (increase the lcd density to 380 or so to get things bigger),
(B) change system font (put in a preferred ttf font),
(C) remove many unneeded (for me) google apps from the system folder, and
(D) enable mobile data auto on off for mms via the features.xml or others.xml. Do you think these could be done (you already mentioned the debloat).
typically i managed to get all of the above done if rooted.
Any advice appreciated on how to do this unpacking and repacking.
Thanks
does this help? (again maybe preaching to the choir but thought I'd ask-not knowledgeable here but posting if it helps in getting to a semi-rooted type state somehow)
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=sm-t285
btw i 'managed' to get oem unlock to show as checked permanently...does that mean the bootloader is unlocked now? (cross flashed through odin the 285 on my 285m the system CP file...and reverted back to 285m-no difference though in network as modem was still 285m as was partition and BL-reflashed the BL as well separately for 285m-after all this shows oem unlock checked-when i got the device new it was unchecked)
edit...from what it appears, it means it CAN be unlocked, yes? but not actually unlocked?
http://forum.xda-developers.com/showpost.php?p=67361863&postcount=9
Click to expand...
Click to collapse
It wont make any difference. Enabling OEM unlock doesn't unlock the bootloader.
You still wont be able to flash unsigned boot or recovery images.
It will only allow you to flash an unsigned system image.
I use Ubuntu to mount and edit Ext4 images.
You can use the windows or Linux version of simg2img to convert the sparse image to raw then mount in Linux
Tbh Samsung need to provide an unlock for this device like they do for the Chinese devices as there is no reason why this device should have a locked bootloader.

Can I flash project treble?

Hello,
I have a device that I obtained through beta testing that has not been released yet. I am allowed to keep the device now that testing is over. I am not happy with the stock rom and some of the apps it forces you to keep. I cannot remove them through ABD either. There is no stock ROM image available yet. Therefore, I cannot port TWRp or root.
I stumbled on project treble. I ran treble check and it says my phone is supported as it came with android 11. It supports systemless updates and has A/B system partition. I really like stock android ASOP. Is there anyway I can flash a generic image? What's the odds of it working correctly? Since there is no image available yet and I cannot port TWRP I have to worrying about not being able to recover the device if things go wrong. I know you can flash without TWRP which is why I decided to ask about this. Would I have a better chance flashing roms for supported devices with similar hardware? How should I proceed?
Thanks,
Rocky

as long as you have a compatible custom recovery AND the stock rom in case something go wrong, you can flash any GSI according to your device's architecture

Roizoulou said:
as long as you have a compatible custom recovery AND the stock rom in case something go wrong, you can flash any GSI according to your device's architecture
Click to expand...
Click to collapse
Since it is a beta unit I have neither as it has not been officially released. I have never flashed one of these roms so I do not know how well they work after flashing. I know the device has a pretty popular SOC which is a snapdragon 750g so I would assume if a gai runs good on another device using the 750g then it should work.

bigroc2223 said:
Since it is a beta unit I have neither as it has not been officially released. I have never flashed one of these roms so I do not know how well they work after flashing. I know the device has a pretty popular SOC which is a snapdragon 750g so I would assume if a gai runs good on another device using the 750g then it should work.
Click to expand...
Click to collapse
best you can do is dump the whole rom, make a backup before going any further

Roizoulou said:
best you can do is dump the whole rom, make a backup before going any further
Click to expand...
Click to collapse
I don't think I can dump it without root right?

bigroc2223 said:
I don't think I can dump it without root right?
Click to expand...
Click to collapse
an unlocked bootloader first and just search for how to dump system on google. it usually just need a pc and ADB

bigroc2223 said:
I don't think I can dump it without root right?
Click to expand...
Click to collapse
[GUIDE] Making Dump Files Out of Android Device Partitions
Use: The main purpose is to make a file that contains all data in android specific partition. This is really handy in case of dumping leak firmwares. Pr-requirement: - Rooted device. - Knowledge of how to use adb or Terminal Emulator. The...
forum.xda-developers.com

Roizoulou said:
[GUIDE] Making Dump Files Out of Android Device Partitions
Use: The main purpose is to make a file that contains all data in android specific partition. This is really handy in case of dumping leak firmwares. Pr-requirement: - Rooted device. - Knowledge of how to use adb or Terminal Emulator. The...
forum.xda-developers.com
Click to expand...
Click to collapse
I tried this before it requires root. I just double checked and the prereqs say root required too. This sucks because the device has decent specs. It's just the ROM and software on it are crappy. After doing some reading the biggest thing I'm worried about is flashing and not having mobile data since it is a 5g phone. I read about someone else flashing and not being able to get their mobile data to work.

bigroc2223 said:
I tried this before it requires root. I just double checked and the prereqs say root required too. This sucks because the device has decent specs. It's just the ROM and software on it are crappy. After doing some reading the biggest thing I'm worried about is flashing and not having mobile data since it is a 5g phone. I read about someone else flashing and not being able to get their mobile data to work.
Click to expand...
Click to collapse
what is the device?

Roizoulou said:
what is the device?
Click to expand...
Click to collapse
It's a beta device from TCL. It has not been released yet. I read that phh GSI should be compatible with all android phones with treble support. Therefore, I think I might just go for it. The only thing is if I end up with a bug I more than likely will probably have to figure it out on my own.

bigroc2223 said:
It's a beta device from TCL. It has not been released yet. I read that phh GSI should be compatible with all android phones with treble support. Therefore, I think I might just go for it. The only thing is if I end up with a bug I more than likely will probably have to figure it out on my own.
Click to expand...
Click to collapse
just try phh's first and if you encounter issues, try other custom roms

Roizoulou said:
just try phh's first and if you encounter issues, try other custom roms
Click to expand...
Click to collapse
I think I might of found a solution. I am pretty sure there is a way to boot a ROM before flashing it. I could of sworn I read this somewhere. It was an adb command. It allowed you too boot the ROM instead of flashing it. This would allow me to preview the ROM before officially flashing it to the device. I just cannot remember where I saw this at or the command.
My goal is to get a working gsi installed. From there I would like to get TWRP flashed on the device so it can be rooted. If I would need to port TWRP I think I could figure it out. This way when the device is officially released it will have TWRP ready to go for it. Also, since it will have TWRP I will be able to start porting roms as soon as they release the system image.

bigroc2223 said:
I think I might of found a solution. I am pretty sure there is a way to boot a ROM before flashing it. I could of sworn I read this somewhere. It was an adb command. It allowed you too boot the ROM instead of flashing it. This would allow me to preview the ROM before officially flashing it to the device. I just cannot remember where I saw this at or the command.
My goal is to get a working gsi installed. From there I would like to get TWRP flashed on the device so it can be rooted. If I would need to port TWRP I think I could figure it out. This way when the device is officially released it will have TWRP ready to go for it. Also, since it will have TWRP I will be able to start porting roms as soon as they release the system image.
Click to expand...
Click to collapse
like DSU loader?

Roizoulou said:
like DSU loader?
Click to expand...
Click to collapse
Never heard of that this was just an adb command.
I just downloaded ASOP 11.0 v309. Treble info says my device requires system-arm64-ab.img.xz. So I downloaded system-roar-arm64-ab-gapps.img.xz and system-roar-arm64-ab-vanilla.ikg.gz so hopefully those are the right ones. One has Gapps and one does not. Was going to flash the Gapps version first and see how things go. Then if need be flash vanilla.

I got a problem with phone calls. When I dial out I get call ended. Incoming calls I can hear them ring but get no way to answer. Also I am not getting text messages.

Roizoulou said:
like DSU loader?
Click to expand...
Click to collapse
I got it all working bro thanks for your help

bigroc2223 said:
I got it all working bro thanks for your help
Click to expand...
Click to collapse
gapps or vanilla?

Roizoulou said:
gapps or vanilla?
Click to expand...
Click to collapse
I was able to get them both to work. However, I am trying to use the gapps version, but I am getting an error that the device is not google certified. I cannot find a workaround unless I unroot which I do not want to do =(

bigroc2223 said:
I was able to get them both to work. However, I am trying to use the gapps version, but I am getting an error that the device is not google certified. I cannot find a workaround unless I unroot which I do not want to do =(
Click to expand...
Click to collapse
rooted with magisk?

Roizoulou said:
rooted with magisk
Click to expand...
Click to collapse
It comes rooted with phh superuser. I'm trying to find a way to pull my boot.img from the device so I can use it to flash magisk since it has a workaround for non Google certified devices.

{SOLVED} Downgrading to a previous Android version

Hello community, I need some explanation first if my approach is incorrect. I am trying to downgrade to Android 10, but i was soul-crashed after reading some information about the bit/binary value that samsung uses on its firmware(basically you cant downgrade if this value is not equal to your targeted frimware). However even though i feel scammed by Samsung, i would like to ask you the community as my final resort to guide me.
Is there some way i can trick SW REV checker or delete this partition containing this binary file?. Does "deleting" it affect my ability to boot into the download mode?

{Temp_User} said:
Hello community, I need some explanation first if my approach is incorrect. I am trying to downgrade to Android 10, but i was soul-crashed after reading some information about the bit/binary value that samsung uses on its firmware(basically you cant downgrade if this value is not equal to your targeted frimware). However even though i feel scammed by Samsung, i would like to ask you the community as my final resort to guide me.
Is there some way i can trick SW REV checker or delete this partition containing this binary file?. Does "deleting" it affect my ability to boot into the download mode?
Click to expand...
Click to collapse
you can downgrade by simply flashing system,kernel and vendor from android 10 on twrp

JuanTamqd21 said:
you can downgrade by simply flashing system,kernel and vendor from android 10 on twrp
Click to expand...
Click to collapse
Hi, thank you for the reply.
Sorry for the late reply. I will try this today

JuanTamqd21 said:
you can downgrade by simply flashing system,kernel and vendor from android 10 on twrp
Click to expand...
Click to collapse
Okay. I am may be misunderstanding something because this way did not work for me. Do I have to manually extract files from the lz4 files?

{Temp_User} said:
Okay. I am may be misunderstanding something because this way did not work for me. Do I have to manually extract files from the lz4 files?
Click to expand...
Click to collapse
well, I can provide vendor and kernel in telegram. You can also get them by extracting lz4 files
make sure its from Android 10/Q/one ui 2.x firmware

I have with me the latest (previous) android 10 . I have extracted correctly ( used 7-zip zstd ) the lz4 files and flashed the vendor, system and kernel in that order.
upon reboot, I can not get past the splash screen. However i do see that an error appears on top left of my screen as CHECK FAIL binary 7(BOOT). The words are not clear though.
What did i do wrong?

JuanTamqd21 said:
well, I can provide vendor and kernel in telegram. You can also get them by extracting lz4 files
make sure its from Android 10/Q/one ui 2.x firmware
Click to expand...
Click to collapse
please provide an in-depth process?

Okay, so after a number of attempts i finally have android 10/Q on my phone. Keep in mind that i am not tech savvy, as all this was a guessing game(well not all of it)
I will share my story and hope it may be useful to others who intend to downgrade their android version.
SW REV ERRORS​You cannot and you should not change the bit version. If you see this error, it means you tried to flash a firmware or maybe just a boot file that is outdated or incompatible with the current secure boot loader.
With my limited knowledge, I went with what was easier for me at the time of writing this,
Flash latest firmware for model A505F,(yours may differ) using Odin.(SUCCESS)​Boot into system normally.(make sure the OEM unlock is greyed out.​Flash the latest custom recovery(TWRP or 'sky hawk recovery project', I chose the latter. )​Boot into your recovery and Format data., also make advanced wipes. System kernel vendor Dalvik Cache Data.​Pay attention to what exactly you are wiping.​With your targeted firmware (A10) somewhere nearby, I recommend to use a reliable tool to extract the lz4 compressed file. I used this to get 'system.img' 'vendor.img' 'boot.img' . If you are on windows, look at the type column in your file explorer or enable 'view filename extension'.​Flash/Install the image files in your recovery. Be patient.​
Here is the tricky part for me. the boot loader wont accept this older kernel.(thus the boot loops).
A faster way to work around this, is installing a custom kernel that supports android 10. e.g. quantum kernel.
You may have to reboot a number of times before you can get past the splash screen. Be patient.​Success, you now have a weird but working system. (I call it weird because the kernel you will use will carry along with its bugs e.g. camera fails, random reboots.)​​You can not update the system. this may be due to the different AP/CP/CSC/ match. This is not a step by step guide, i am only sharing with the public what i did to get my final point.
Of course this goes without saying that you are attempting a risky route and you the user shall carry all responsibility.
​​

{Temp_User} said:
Okay, so after a number of attempts i finally have android 10/Q on my phone. Keep in mind that i am not tech savvy, as all this was a guessing game(well not all of it)
I will share my story and hope it may be useful to others who intend to downgrade their android version.
SW REV ERRORS​You cannot and you should not change the bit version. If you see this error, it means you tried to flash a firmware or maybe just a boot file that is outdated or incompatible with the current secure boot loader.
With my limited knowledge, I went with what was easier for me at the time of writing this,
Flash latest firmware for model A505F,(yours may differ) using Odin.(SUCCESS)​Boot into system normally.(make sure the OEM unlock is greyed out.​Flash the latest custom recovery(TWRP or 'sky hawk recovery project', I chose the latter. )​Boot into your recovery and Format data., also make advanced wipes. System kernel vendor Dalvik Cache Data.​Pay attention to what exactly you are wiping.​With your targeted firmware (A10) somewhere nearby, I recommend to use a reliable tool to extract the lz4 compressed file. I used this to get 'system.img' 'vendor.img' 'boot.img' . If you are on windows, look at the type column in your file explorer or enable 'view filename extension'.​Flash/Install the image files in your recovery. Be patient.​
Here is the tricky part for me. the boot loader wont accept this older kernel.(thus the boot loops).
A faster way to work around this, is installing a custom kernel that supports android 10. e.g. quantum kernel.
You may have to reboot a number of times before you can get past the splash screen. Be patient.​Success, you now have a weird but working system. (I call it weird because the kernel you will use will carry along with its bugs e.g. camera fails, random reboots.)​​You can not update the system. this may be due to the different AP/CP/CSC/ match. This is not a step by step guide, i am only sharing with the public what i did to get my final point.
Of course this goes without saying that you are attempting a risky route and you the user shall carry all responsibility.
​​
Click to expand...
Click to collapse
Hello, you will not be able to downgrade your phone to Android 11, if it is not on theese firmware updates:

Of course, the reason is, that the binaries of newer updates are higher, than 7 (A505FNPUU7CUC2).

vmirrimv said:
Of course, the reason is, that the binaries of newer updates are higher, than 7 (A505FNPUU7CUC2).
Click to expand...
Click to collapse
So long as we both happy and got what we wanted. I finally have a working android 10 on my device(coming from a11)

vmirrimv said:
Hello, you will not be able to downgrade your phone to Android 11, if it is not on theese firmware updates:
Click to expand...
Click to collapse
You are correct. I gave up on changing the binaries after seeing it was impossible.

Camera should still work on custom android 10 one ui roms and GSI. I think I tested them before.

Question Anyone bricked/EDL/9008 their ROG 6?

Follow and complain here.
Let ASUS know their bootloader implementation is VERY NOT FRIENDLY to us. I've been modding my Android devices since the Android 2 era and this is the first time I encountered an UNOFFICIALLY UNRECOVERABLE state which is a HORRIBLE experience.
Me? Have played with
Samsung(S5 to S9 and Tab/Odin is a good thing)
XiaomiRedmiPoco(Main device for me today, very modder friendly and robust)
Huawei(Remember when they allow applying for BL unlock?)
Apple(LOL jailbreak from A4 SoC until iPhone X(meantime Samsung S8 looks gorgeous) lost my interest)
And various small brands or exited market big brands(honorable mention Lenovo LePhone C101. My first smart device/Android and received big community support at the good old time)
ASUS. Fix your buggy BL. Fix your policy. Release everything we need to fix OUR DEVICES of OURSELVES. Just ONE step closer to perfect.

Just imagine how stupid is this:
Everytime you want to update you operating system, your UEFI/BIOS firmware might break.
And worse, that you don't have free official resources to fix it?
And can it be worse? Yes! Your Warranty is maybe void because you may unlocked bootloader, now supposedly only ASUS service center have the file to fix it.
Ha now it's interesting. That's the era of ANTITRUST. Even Apple won't do it(Worst case DFU, easily fixable using OFFICIAL iTunes).
WT*?

yeah dude i'm bricked up rn

Paid here, paid there.
Yeah sure.
Exploit people.

Perhaps instead of ranting about asus, you could tell us what you have done exactly to brick your device, and someone might be able to help you ? can you get into fastboot at all?

EDIT: quoted content removed.
Never use this firmware, because it has not been modified, 100% of fingerprints and IMEI will be lost after use. You need to modify the firmware before you can flash it.

mahdibassam said:
Perhaps instead of ranting about asus, you could tell us what you have done exactly to brick your device, and someone might be able to help you ? can you get into fastboot at all?
Click to expand...
Click to collapse
Trying to flash img unpacked from update zip. Which you should NOT do. Because Android 12 dynamic partition.

iMoc said:
Trying to flash img unpacked from update zip. Which you should NOT do. Because Android 12 dynamic partition.
Click to expand...
Click to collapse
Ok, yes you definitely should not do that
So just wondering, you went and grabbed some img files and made the decision to flash them, why is this any fault of asus?

mahdibassam said:
Ok, yes you definitely should not do that
So just wondering, you went and grabbed some img files and made the decision to flash them, why is this any fault of asus?
Click to expand...
Click to collapse
1\ The fastboot code in their bootloader have bugs, any CORRECT command you type can easily break bootloader then stuck you in 9008.
2\ The normal update method failed because THEIR UPDATER did do things wrong.
3\ They refuse to provide official ROM to let yourself fix it. SEND IT TO ME TO FIX IT, AND I MIGHT CHARGE YOU SOME.
....\
N\ You go talk to Apple about it because they are experts about saying YOU USED IT WRONG.

Anyone asked for help gets it for free so far.
All devs on my chat group agree at least fastboot flashable should be available on the official download page.
MOD EDIT: off topic content removed

Did you manage to unbrick your phone?
I managed to semi hard brick my phone. Can get into fastboot but unable to start recovery mode from fast boot and phone doesn't show up from adb devices.
I guess I'll start a new thread but any tips?

insideoft said:
Did you manage to unbrick your phone?
I managed to semi hard brick my phone. Can get into fastboot but unable to start recovery mode from fast boot and phone doesn't show up from adb devices.
I guess I'll start a new thread but any tips?
Click to expand...
Click to collapse
If you can boot into fastboot you can just flash the RAW ROM file available a few days ago. It's not bricked in this case.

Moderator Information
Hello everyone,
I have cleaned the thread from off topic contents and posts. Please focus on problem solving related discussion, not finger pointing or flaming each other. We all come here to solve the issues and learn some new stuffs.
Thanks.

iMoc said:
If you can boot into fastboot you can just flash the RAW ROM file available a few days ago. It's not bricked in this case.
Click to expand...
Click to collapse
Sorry long time ago since I was into this stuff previosly.
That fixed it, thanks for the help!

same here

General Would be nice if....

Would be nice if we could get rid of the bootloader and unofficial software warnings from the A52S. I have searched through most of the firmware for the images to no avail... will keep seeking.

bobfrantic said:
Would be nice if we could get rid of the bootloader and unofficial software warnings from the A52S. I have searched through most of the firmware for the images to no avail... will keep seeking.
Click to expand...
Click to collapse
I've heard rumors it's located in the actual bootloader, so messing something up there could result in a dead device

ShaDisNX255 said:
I've heard rumors it's located in the actual bootloader, so messing something up there could result in a dead device
Click to expand...
Click to collapse
I decompiled boot.img and found no images

bobfrantic said:
I decompiled boot.img and found no images
Click to expand...
Click to collapse
boot.img is not bootloader. I don't really know which "image" it is exactly but it's definitely not boot.img
Try searching in the BL_ file and decompiling everything there idk

Used to be located it up_param.bin or param.bin (idk anymore if it was in AP or CP) but those files don't exist anymore for some reason. Also wanted to remove it like i used to do on my A50

JanBoyGamer23 said:
Used to be located it up_param.bin or param.bin (idk anymore if it was in AP or CP) but those files don't exist anymore for some reason. Also wanted to remove it like i used to do on my A50
Click to expand...
Click to collapse
up_param.bin don't exsist in snapdragon chipsets. That's what makes finding the warning images so difficult...

I'm genuinely asking, why do you root your A52s? I rooted all my phones in the past but with this one I haven't felt the necessity.

1812CE said:
I'm genuinely asking, why do you root your A52s? I rooted all my phones in the past but with this one I haven't felt the necessity.
Click to expand...
Click to collapse
I can install apps that let me modify things on my phone. Give easy access to root partion to be able to push files to. Also getting ad blocking with AdAway with root instead of vpn which is slow.

1812CE said:
I'm genuinely asking, why do you root your A52s? I rooted all my phones in the past but with this one I haven't felt the necessity.
Click to expand...
Click to collapse
There's some features that Samsung disables on A-series phones. You can activate most with a rooted phone.

bobfrantic said:
Would be nice if we could get rid of the bootloader and unofficial software warnings from the A52S. I have searched through most of the firmware for the images to no avail... will keep seeking.
Click to expand...
Click to collapse
By the way, the image is located in abl.elf

ShaDisNX255 said:
By the way, the image is located in abl.elf
Click to expand...
Click to collapse
great and how to access it?? LOL

bobfrantic said:
great and how to access it?? LOL
Click to expand...
Click to collapse
That's the mistery

ShaDisNX255 said:
That's the mistery
Click to expand...
Click to collapse
how do you know then that is where the image(s) are. curious. any kitchen to decompile the file?

bobfrantic said:
how do you know then that is where the image(s) are. curious. any kitchen to decompile the file?
Click to expand...
Click to collapse
There was a discussion going on here: discussion on SD devices
After going through it, everyone reached a dead end
According to this post, even if you're able to unpack, replace and repack the abl file you won't be able to flash it back to the phone. It looks like Odin and the phone still check for valid Samsung signatures on the bootloader files (like abl) even if you have an actual unlocked bootloader to accept custom files. You break Samsung's signature of abl with any edit to it, so you won't be able to flash with Odin. And no type of current root method (be it TWRP or Magisk) have access to replace this afaik. So yeah, it's a dead end.

ShaDisNX255 said:
There was a discussion going on here: discussion on SD devices
After going through it, everyone reached a dead end
According to this post, even if you're able to unpack, replace and repack the abl file you won't be able to flash it back to the phone. It looks like Odin and the phone still check for valid Samsung signatures on the bootloader files (like abl) even if you have an actual unlocked bootloader to accept custom files. You break Samsung's signature of abl with any edit to it, so you won't be able to flash with Odin. And no type of current root method (be it TWRP or Magisk) have access to replace this afaik. So yeah, it's a dead end.
Click to expand...
Click to collapse
I took a "brief" look at those threads, didn't read about just deleting the abl.elf file from the bl_xxxx.tar

would be nice if this phone have a AKG speakers ^^

bobfrantic said:
I took a "brief" look at those threads, didn't read about just deleting the abl.elf file from the bl_xxxx.tar
Click to expand...
Click to collapse
I already gave you a tldr, it's simply not possible

ShaDisNX255 said:
I already gave you a tldr, it's simply not possible
Click to expand...
Click to collapse
Tis indeed a dead end at this time. But maybe someone can figure it out...

ShaDisNX255 said:
There was a discussion going on here: discussion on SD devices
After going through it, everyone reached a dead end
According to this post, even if you're able to unpack, replace and repack the abl file you won't be able to flash it back to the phone. It looks like Odin and the phone still check for valid Samsung signatures on the bootloader files (like abl) even if you have an actual unlocked bootloader to accept custom files. You break Samsung's signature of abl with any edit to it, so you won't be able to flash with Odin. And no type of current root method (be it TWRP or Magisk) have access to replace this afaik. So yeah, it's a dead end.
Click to expand...
Click to collapse
There was some release post on XDA thought of a "modded/patched Odin" which apparently "bypasses all signature checks" or something like that. I wonder if it applies to the bootloader.

SevastianXDA said:
There was some release post on XDA thought of a "modded/patched Odin" which apparently "bypasses all signature checks" or something like that. I wonder if it applies to the bootloader.
Click to expand...
Click to collapse
The phone also checks for stuff, so even if you can bypass Odin's checks, you can't bypass the phone's checks