Related
Recently I tried out the Nougat preview on my EVA-L09C636. It was ok but seeing as there was a problem with fonts and I'd lost root access, I began thinking about going back to MM.
To prepare for downgrade I tried using srktool to bring TWRP back (and I think this is my big mistake as srktool uses a TWRP made for MM, not N, is that right?). After I tried to restore TWRP I noticed "not recognised" errors when I connected my phone to PC again.
System recovery using hajuuk's Firmware Updater and HiSuite looked like it would complete but near the end of the process (the restoring system part) HiSuite aborted itself saying my device wasn't supported. This has left my P9 is in an unusable state where the only thing I can access is fastboot. Also I can't turn off my phone - holding down power simply makes it reboot then get stuck at the "Your device ... can't be trusted / Your device is booting now" screen.
Reading around a bit I attempted to unbrick it without any luck:
1. downloaded EVA-L09C636B152 update.zip from http://forum.xda-developers.com/p9/development/rom-stock-rom-eva-l19c636b168-t3419586 and installed Snoop05's 15 seconds ADB Installer.
2. extracted images from update.zip using Huawei Update Extractor and did
Code:
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash cust cust.img
then tried rebooting holding volume up + power several times (but never got past untrusted device boot screen).
3. extracted contents of update.zip to folder 'dload' on a blank sd card, trying to force update several times by rebooting and holding down power + volume up + volume down (still never get past the screen saying my device is booting).
At this point I'd be happy to get anything happening on my phone - Marshmallow, Nougat or even some other ROM so I can use my device again.
Any ideas? I'm on EVA-L09 C636.
i2ectcf said:
Recently I tried out the Nougat preview on my EVA-L09C636. It was ok but seeing as there was a problem with fonts and I'd lost root access, I began thinking about going back to MM.
To prepare for downgrade I tried using srktool to bring TWRP back (and I think this is my big mistake as srktool uses a TWRP made for MM, not N, is that right?). After I tried to restore TWRP I noticed "not recognised" errors when I connected my phone to PC again.
System recovery using hajuuk's Firmware Updater and HiSuite looked like it would complete but near the end of the process (the restoring system part) HiSuite aborted itself saying my device wasn't supported. This has left my P9 is in an unusable state where the only thing I can access is fastboot. Also I can't turn off my phone - holding down power simply makes it reboot then get stuck at the "Your device ... can't be trusted / Your device is booting now" screen.
Reading around a bit I attempted to unbrick it without any luck:
1. downloaded EVA-L09C636B152 update.zip from http://forum.xda-developers.com/p9/development/rom-stock-rom-eva-l19c636b168-t3419586 and installed Snoop05's 15 seconds ADB Installer.
2. extracted images from update.zip using Huawei Update Extractor and did then tried rebooting holding volume up + power several times (but never got past untrusted device boot screen).
3. extracted contents of update.zip to folder 'dload' on a blank sd card, trying to force update several times by rebooting and holding down power + volume up + volume down (still never get past the screen saying my device is booting).
At this point I'd be happy to get anything happening on my phone - Marshmallow, Nougat or even some other ROM so I can use my device again.
Any ideas? I'm on EVA-L09 C636.
Click to expand...
Click to collapse
did you wiped data, cache, dalvik?
snapdesign said:
did you wiped data, cache, dalvik?
Click to expand...
Click to collapse
Hi! I'm not sure how to wipe data, cache or dalvik, because when I upgraded to Nougat this apparently removed TWRP.
Also I'm wondering if trying to use srktool to reinstall TWRP for 6.0 might have corrupted my 7.0 phone?
Is there any way to wipe data, cache, and/or dalvik now? Or are there other things I could try to unbrick?
Although my phone was in a pretty bizarre state - it would get hot and sit on the booting now screen until battery died - I was able to use DC Phoenix to make it boot up again. At that point it had no themes and only KitKat-esque icons. A reset and upgrade later icons and themes work and I'm back on stock Marshmallow. Here's an outline:
1. Google "Huawei Bricked phone repair guide with DC Phoenix", go to the first result and look at the instructions (I can't post URLs yet).
I used Method 1. But note! The newer versions of DC Phoenix are missing a feature that the instructions make clear you have to use. To get the original version used in their guide, you have to download the latest version of DC Phoenix, open it on your PC, then click "Enter Support Area" which logs you in to a download section. Find "DC Unlocker Softwares", "DC_Phoenix", then download DC_Phoenix_v14.rar and run that instead. Whether it's Method 1 or 2 make sure you complete it - i.e. the fastboot flash step AND a step they call "flashing in upgrade mode."
(Also note that for DC Phoenix you want to feed it the oldest version of firmware available for your phone, in my case b152. This is because themes and icons won't be fixed until it receives the next version of firmware as an update.)
2. Once I did the fastboot and upgrade flash, I did a system reset from the Settings app trying to get themes and current icons again. (This didn't work but doesn't do any harm or might have helped somehow further down the line).
3. I used hajuuk's Firmware Updater and HiSuite to upgrade to the next version of firmware available (in my case b168).
3. All fine and your phone is back to stock - icons look nice again and local themes are back. To get the original icons layout, go to Recents, hold down on the Trash Icon, show system apps, and Clear Data for Huawei Home.
i2ectcf said:
Although my phone was in a pretty bizarre state - it would get hot and sit on the booting now screen until battery died - I was able to use DC Phoenix to make it boot up again. At that point it had no themes and only KitKat-esque icons. A reset and upgrade later icons and themes work and I'm back on stock Marshmallow.
Click to expand...
Click to collapse
Thanks for sharing! You saved me!
I have a European Huawei P9 EVA-L09 model which I adore. It was running Marshmallow and EMUI 4.1. I found a Nougat beta ROM and I tried to install it but have left it in an unusable state.
I don't think the phone is rooted but I do think the bootloader is unlocked.
I can boot into 3 modes.
Mode 1 - Just reboot
Huawei eRecovery where I get the options to download latest version and recovery, Reboot and Shutdown. If I select the Download latest version and recovery it setups my Wifi and then fails with the message Getting package info failed.
Mode 2 - Power + Vol Up
It boots into a screen that gives me the option to Reboot your System Now, Wipe data / factory Reset , Wipe Cache partition. Selecting Wipe Data/Factory reset returns back to this screen with an error - Red Exclamation mark. Selecting Wipe Cache partition seems to perform a wipe and returns to the original screen with the 3 options again.
Mode 3 - Connect to PC with Hisense and power + vol down
This goes into an android recovery screen which is white with a green android displayed
I have the USB drivers installed on my PC but I cannot see the phone in Windows explorer when I plug it in via USB. I do hear the recognition tone that Windows has recognised that a USB device has been attached. The Huawei PC software doesn't recognise it unless I go into the white android screen and select recover. This always fails saying it cannot find a package.
I have installed stock P9 Marshmallow firmware on my SD card in a dload folder (which is how I bricked it in the first place. When I hold Vol up and Vol Down and power it starts installing but then fails about 40% - 50% through. I have tried multiple versions of the L09 firmware but none of them install successfully.
I am not very technical and not an android expert so cannot say I have done everything perfectly correctly. #
Is my phone bricked or is it possible get my phone back working?
You can get your phone back, search the forums for dc phoenix, which has helped people including myself.
The other option is to go the huawei website, and look under downloads for p9. Find the two firmwares for beta rollback and follow the instructions, although i am not 100% confident that will work for you
use dc phoneix ... i was the in tha same condition
So I have installed and tried install a few different ROMs to the phone. DC Phoenix recognizes the phone as it comes up with the IMEI and version in the left hand window. It seems to install the ROM sucessfully.
I get a message at the end saying it finished successfully but when I boot back up it just goes straight into the same eRecovery screen I have tried B166 and B322 and no luck. Is there anything different I should be doing?
...and now I have a new issue
Thanks for everyone's help. After downloading and trying about 10 different ROMs I was able to get a Nougat ROM to install. Now I have a different problem
1. When I reboot I get a verification failed message. I get an option to go to eRecovery (which works the same as above and doesn't find a package)
So what I really want now is just to get back to stock Marshmallow and not have a verification message and not have some Nougat version that doesn't look like the official Huawei ROM.
So what next folks?
I encountered the exact same problem a few days ago. I didn't try DC Phoenix, instead sent it to Huawei for repair, claiming the phone was in a boot-loop I couldn't recover from.
They have fixed it now and the P9 is on its way back to me. What's strange is that they have swapped the whole motherboard for a new one! Didn't expect that.
Exynos variants such as International (F), International Dual(Hybrid)-SIM (F/DS),
i am not responsible if anything goes wrong. You are still the one who tryed to flash the files. Even tough this should work as it worked for me and some friends.
Hello XDA
This is my first post (sorry if one already exists)
Today i am going to tell you how to root the Galaxy S9 International on android 9 Pie on stock touchwiz rom.
First of all download all these files;
Prince comsy odin: https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Team win recovery https://forum.xda-developers.com/ga...cross-device-development/twrp-exynos-t3763464
ElementalX Kernel https://elementalx.org/devices/samsung-galaxy-s9/
No verity encrypt: https://androidfilehost.com/?fid=962187416754474353
Magisk 18.0 https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Now for the root
First you need to unlock OEM, you can do this in developer options,
If there is no developer options you need to enable this
you can do this in: Settings>About Phone > software information > click 5 times on build number.
When you unlock OEM everything on your phone gets wiped so make a backup!!
When the wiping is complete, turn off your phone and go to download mode (Vol down + Bixby + Power)
Then connect the phone to your pc and start odin
In odin go to options, and disable f.reset and auto reboot.
Then press the AP button and select the TWRP image you downloaded.
When TWRP is flashed, force reboot your phone (Vol down+ Power) when it is powered off quickly press Vol Up + Bixby + Power to get into recovery
Swipe to allow modifications. And format /data
Then reboot into recovery.
When rebooted mount USB Storage and connect the phone to the PC
Then you can click&Drag the other files (elemental, Magisk, No verity)
When the files are on the phone, go to install and search for the files you just put on the phone.
Install in this order:
Flash No-Verity-Encrypt
Then flash the custom kernel (ElementalX)
And as last flash Magisk.
When you did this, you want to Factory reset, Wipe cache and Dalvik.
Then you can reboot the phone, and install it.
(It is possible that you stay at the boot logo for a long time (Not the galaxy s9 one but the next one) What you need to do then is let it boot for 5 minutes, then force reboot (vol down+Power) and then the phone boots fine)
Again, just to make sure check if OEM is still unlocked (sometimes this get locked again)
Please note that when you do this, you lose secure folder and other functions, also is the knox tripped (0x1)
But the Fingerprint, Irisscanner and samsung account works.
SOMETIMES IT IS NEEDED TO INSTALL THE MAGISK MANAGER MANUALLY, YOU CAN JUST DOWNLOAD THE FILE FROM THE LINK IN THIS POST
Hope this helps.
If you do have any questions, please do the following first;
Note any errors that odin or your phone gives you. I want to help you, but i do need to know what is going wrong.
(Sorry for my bad english)
reserved
So you won't need RMM-state_bypass on pie anymore?!? Seems hard to believe...
And why exactly you need to flash that custom kernel, which benefits does this bring with it?
sarius02 said:
So you won't need RMM-state_bypass on pie anymore?!? Seems hard to believe...
And why exactly you need to flash that custom kernel, which benefits does this bring with it?
Click to expand...
Click to collapse
If you dont use the custom kernel, you will get RMM error.
Iris scanner wont work, Fingerprint wont work, Samsung account wont work. When you reboot the phone you get a little "Bootloop" at the lockscreen (Screen flashes and is unusable and your pattern isn't saved)
I dont know what else breaks because i cant even get past the lockscreen with stock kernel
(Also you get better performace and battery life)
Hope this helps
work it with s9+?
Sorry for my English...
Yes, but you want to use tgpkernel then otherwise it will not work (problems described abovel
https://www.androidfilehost.com/?w=files&flid=288240
Last samsung phone i rooted was the note 3, and i remember that doing that "tripped" knox 0x1 and this basically voided the warranty. It's the same with S9? is there some non-reversible change that happens to the phone when rooting?
effry said:
Last samsung phone i rooted was the note 3, and i remember that doing that "tripped" knox 0x1 and this basically voided the warranty. It's the same with S9? is there some non-reversible change that happens to the phone when rooting?
Click to expand...
Click to collapse
Yes, the knox will still trip (0x1).
In europe, when you can show that the root is not the cause of the problem, they have to fix it under warranty.
Also there are some functions you will lose (forever)
Knox,
Samsung pass,
Samsung Pay,
S-Health(you can fix this one with a build.prop tweak)
Secure folder
If you plan to use one of these (exceptpt s-health) It is better not to root your phone (there are still external app's you can use if you plan to root your phone)
Is there a way to update the stock firmware when you have root? Or do i have to do all over again?
I have this lock screen flashing bootloop issue, what is the fix? I have tried factory restores but get the same results once I set a lock/passcode and reboot. Samsung Account and Bixby also do not work as you mentioned.
You can use TGPkernel then,
Some phones have this issue, some not.
I have seen that 3 friends of mine it worked, and also on 3 not, so this is a very weird issue
What was the fix with them is to install TGPkernel
@co9
The only way i know is to install a custom kernel,
Otherwise you have to download latest stock rom, and flash this using odin.
wich changes your recovery.img and boot.img, aswell as the kernel. so you have to flash this all over again
Thanks for the answer. I already have a custom kernel. So if i always want to have the latest Samsung firmware i have to flash it through odin and do the whole root procedure again?
I tried this method but now everytime I reboot the phone my bluetooth paired device are lost. They also get deleted if I turn ON and OFF the Airplane mode. Anyone else having the same issue ?
Is anyone else experiencing an issue where the password, pin, or pattern set before setting up fingerprint scanning acts like what was entered is incorrect, not allowing you to setup fingerprint scanning?
I've tried setting up fingerprint scanning on initial setup as well as skipping and trying after the phone has been setup but had no luck. What ever I set initially will not work when I'm prompted later on when trying to setup fingerprint scanning or tying to access other secure features. The phone just prompts to try again acting like I entered in the wrong password, pin, or pattern. I've even tested by setting up a REALLY simple password with no luck.
I have confirmed in the settings that Elemental is installed.
Edit: I did find this thread https://forum.xda-developers.com/galaxy-s9/help/root-galaxy-s9-exynos-9-0-android-pie-t3884267. I tried the no-verity-opt-encrypt-6.0.zip that was suggested in some posts but had no success. I've also tried the TGPKernel but had not change in the issue. I am able to setup fingerprint scanning on fresh firmware install but after installing TWRP and everything else the above issue happens.
Install steps Magisk 18 for Samsung S8/S9 Android Pie 9
Install steps Magisk 18 for Samsung S8/S9 Android Pie 9
See lot of people have trouble, here are the steps to do, dont get confused keep it simpel nothing more
1 Flash the last pie build (sammobile.com) with Odin, restart mobile, let system install
2 Enable unlock OEM (settings->about phone->softare information-> tap a few times on build so developer options tab is in settings go there and enable oem unlock)
3 Flash TWRP (twrp.me/) with Odin and immediately after the flash hold bixby+volume up+ powerbutton to go to TWRP
4 In TWRP, swipe to allow modifications.
5 Go to Wipe - Format (yes). Press the back button all the way to home of TWRP
6 Reboot recovery
7 In TWRP, swipe to allow modifications, click on install button and flash dm-verity v1 and press the back button all the way to home of TWRP
8 Click on install button and flash magisk v18
9 Reboot system and let system (android 9) install enter pin, google account and so on...
10 Install magisk app
11 Open Magisk, if you see there is no root/magisk installed, no worry!! Just download Magisk from the Magisk app to the download folder on your phone, restart your phone adn go to TWRP and install Magisk again.
Done!
Used Software:
Odin3_v3.13.1
Twrp 3.2.3.2
no-verity-opt-encrypt-samsung-1.0
Magisk-v18.1
MagiskManager-v7.0.0
menhammer said:
Install steps Magisk 18 for Samsung S8/S9 Android Pie 9
See lot of people have trouble, here are the steps to do, dont get confused keep it simpel nothing more
1 Flash the last pie build (sammobile.com) with Odin, restart mobile, let system install
2 Enable unlock OEM (settings->about phone->softare information-> tap a few times on build so developer options tab is in settings go there and enable oem unlock)
3 Flash TWRP (twrp.me/) with Odin and immediately after the flash hold bixby+volume up+ powerbutton to go to TWRP
4 In TWRP, swipe to allow modifications.
5 Go to Wipe - Format (yes). Press the back button all the way to home of TWRP
6 Reboot recovery
7 In TWRP, swipe to allow modifications, click on install button and flash dm-verity v1 and press the back button all the way to home of TWRP
8 Click on install button and flash magisk v18
9 Reboot system and let system (android 9) install enter pin, google account and so on...
10 Install magisk app
11 Open Magisk, if you see there is no root/magisk installed, no worry!! Just download Magisk from the Magisk app to the download folder on your phone, restart your phone adn go to TWRP and install Magisk again.
Done!
Used Software:
Odin3_v3.13.1
Twrp 3.2.3.2
no-verity-opt-encrypt-samsung-1.0
Magisk-v18.1
MagiskManager-v7.0.0
Click to expand...
Click to collapse
Don't root this phone without flashing a custom kernel or a modified stock kernel. It will drain battery and reduce the performance or even crash the system.
Look in the TWRP thread there it is explained why you shouldn't do it.
Emre67511 said:
Don't root this phone without flashing a custom kernel or a modified stock kernel. It will drain battery and reduce the performance or even crash the system.
Look in the TWRP thread there it is explained why you shouldn't do it.
Click to expand...
Click to collapse
My personal experience is i have rooted using this method and have had no problems
Hi all,
I tried to flash twrp but never succed.
S9+ last firmware from samsun android 9 pie (update from smart switch)
Then option developper activated, no oem unlock menu found,
boot into download mode and there is written oem unlock desactivated so ok
with odin try to flash (ap, reboot freset unchecked)
then fails and message in red on the phone :
"only official released binaries are allowed to be flashed recovery"
History :
I was in galaxy project oreo, i wanted to upgrade with pie, but reboot cycle
so rescue with odin and original oreo firmware, then update to pie
thanks for help
regards
To get the oem unluck button visible.
After fresh install, go to time/date in settings, choose manual and set the date 1 mount prior (march will be februar)
Than go to software update, choose manual en click on dowload updates manually.
Restart your phone and the oem unlock button in developer options will be there
Cheers
thank's for answering,
Update done, reboot ok but still not oem options in developpers section
Hi guys, Im using the A2 for almost 6 months now and it is realy the worst phone I've ever had.
(and I'm a Xiaomi fan since the mi3)
And as it seems that Xiaomi wont fix the bugs as the said, I was wondering if flashing some other rom will help?
I'm talking about the approximately sensor bugs and the general lagginess bugs (unlocking the device etc..).
And if so, is there recommended rom?
Im just looking for clean, fast and reliable rom.
(I thought the Android One will be good, but ahh...)
lsd95 said:
Hi guys, Im using the A2 for almost 6 months now and it is realy the worst phone I've ever had.
(and I'm a Xiaomi fan since the mi3)
And as it seems that Xiaomi wont fix the bugs as the said, I was wondering if flashing some other rom will help?
I'm talking about the approximately sensor bugs and the general lagginess bugs (unlocking the device etc..).
And if so, is there recommended rom?
Im just looking for clean, fast and reliable rom.
(I thought the Android One will be good, but ahh...)
Click to expand...
Click to collapse
Afaik aosp roms will fix the issues. Didnt notice those until now im on aex. Before pe also running nicely
Sent from my Xiaomi MI A2 using XDA Labs
I am on havoc + hex, and honestly it feels like a completely different phone.
Battery life is almost doubled, geekbench multicore score increased 1500 points, I am able to run pubg HDR at stable very playable fps, gcam never crashes and it takes excellent pictures, also audio in videos is dramatically improved
I highly recommended you go custom
lukezainn said:
I am on havoc + hex, and honestly it feels like a completely different phone.
Battery life is almost doubled, geekbench multicore score increased 1500 points, I am able to run pubg HDR at stable very playable fps, gcam never crashes and it takes excellent pictures, also audio in videos is dramatically improved
I highly recommended you go custom
Click to expand...
Click to collapse
At this point I'll try anything.
Can you reply with a good tutorial (for absolute noob) for how to install this rom?
Thanks in advance
Definitely go for custom rom for all already mentioned reasons. Totally different phone, as it should have been with stock. Now first you need to understand how a b slot partitions that this phone have, work. Let's say now that you have stock rom with December update your active slot is a. When you get notification for new update and download it the installation starts while you continue using the phone, cause the update is being installed in the other b slot which at the moment is inactive. When it finishes the installation and you get a notification for restart, then you boot to the newly updated software which is installed on b slot. So now b slot becomes active and a slot with the old software becomes inactive. You have to understand that so you will never have any question about how to install a custom rom. Now the bad thing is that unfortunately we still don't have a permanent twrp custom recovery. First thing you have to do is unlock bootloader (search how to do that and if course install drivers and adb fastboot on your PC). Then you have to choose which rom you want to install and download it. Download twrp as well. Fastboot boot twrp.img go to wipe and perform a factory reset with the option that you have to write "yes" to proceed. Then if you go to reboot menu you will see that it has option to change slots a and b and it says which one is active at the moment. What ever you install it will be installed to the inactive slot. Go again to wipe and advanced wipe and choose art and system and data and proceed then go to reboot and change slot. Reboot recovery and again wipe system art and data. Then you can change slot again (or just stay to the slot you already are). Now you have to go to advanced and start adb sideload, connect your phone to the pc and on your PC go to the adb folder, shift + right click and open cmd here. Type adb devices, if you see a listing (numbers) then you are ready to go. (On the same adb folder put your rom that you have downloaded and rename it to something short lets say rom.zip). Now type adb sideload rom.zip and press enter. When the installation is finished on your phone don't reboot, go back and go to reboot menu and change slot (don't worry about error) then reboot system and wait for your new phone to boot. If you choose a rom with separated gapps you have to adb sideload gapps as well.
A small tip before you wipe anything you can first try to adb sideload the rom so if you get any kind of error or problem you can still boot stock system. If it starts installation, when it finishes act like it never happened and follow all the steps from step one.
Sent from my Mi A2 using Tapatalk
Hello guys, decide to mount this tutorial because I still see a lot of people with doubts, yes we already have how to root our device
I did it on mine and it worked, do it at your own risk, neither I nor anyone else on the forum is responsible for any loss
A tutorials too complex for some users, teaching you how to create your own Magisk modified Img boot, but I like simplicity, so if you don't want to break your head too much, here's a tip, use a successfully modified img boot , what you need is to install the rom stock that was used to create the modified boot first.
let's go to the tutorial, warning that the files posted here are not my own, and if it doesn't work, check if you're not commenting on any flaws, don't try to memorize the tutorial, follow it step by step. come on!:dedos cruzados:
1 - first follow these steps to unlock the bootloader:
This is a basic step to root device. Go to settings - about phone - Software Information - tap multiple times on "Build number" - This will open developer option.
Now in settings at the end, you will have new option "Developer options" - look for OEM unlocking - Enable it.
(PS : If you don't see this option then you may need to wait up to 7 days or more to appear or may be on some operator you will get it never. Without this option you can not root your device, sorry!)
Once you have enable OEM unlock option, switch off your device and reboot to download mode.
To put device in download mode - Press Volume Up & then Press Volume Down (Keep holding both) and connect device to PC with USB cable
When device start to download mode,long press volume up to unlock the bootloader. This will wipe your data and automatically reboot
Now let finish setup and again enable developer options (as said above), and confirm that the OEM unlocking option exists and grayed out!
If it is not then you can not root device!
Once you see this option and greyed out, you are ready to flash custom binary and root your device.
Now let's go to the next step, reinstall an outdated system, I did it on mine and it worked, do it at your own risk, neither I nor anyone else on the forum is responsible for any loss
2 - installing the stock ROM that we will use:
download this rom: https://samfrew.com/ru/download/Gal..._Wi-Fi-__/rue3/KOO/T290KSU3BUE1/T290KOO3BUE2/
OBS: a little detail about this firmware, it is made in arm32, which apparently makes it "lighter", but also has a more acidic use of RAM memory. This was the last software I installed on tab A, and I can say that the use has become better with it, but if you want to stay in the stock rom, even custom gsi didn't get such a good performance. It's worth testing, but be aware of the risks, I'm not responsible for errors.
Updating: use a modified version of Odin, to do the installations, be careful with downgrades, I managed, I was in the most current version of March, and I managed anyway using this modified Odin, but do it at your own risk, download the most current version here:
https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
And install via Odin, if you need more details just a Google, there are already millions of tutorials for that lol
when you get here you should already be aware that you have lost all your data, but it is necessary that the OEM option is enabled in the options, so in the CSC session use Home CSC, so that you leave the data saved, and do not lose the initial settings : )
once with successful installation, we will now install the file modified by magisk
3 - magisk Installation:
Intall TWRP: https://forum.xda-developers.com/t/...-2-for-2019-galaxy-tab-a-8-0-sm-t290.4185235/
just follow our friend's tutorial, with a little observation, after starting the process in odin, be sure to hold the volume up button + turn on, to be redirected to the TWRP.
follow the standard steps to install magisk, if it doesn't work, you will have to manually modify the system boot.img along with magisk maneger.
if case of problem:
The process of entering recovery on the SM-T290 using buttons is really finicky, unlike the 10.1" version. My best result has been with holding Power + Vol Up on startup, quickly switching to hit Power to dismiss the bootloader unlock warning page, and then immediately holding Power + Vol Up again for 6 seconds. (Holding longer will cause a hard reset.)
If you miss on the first attempt and haven't installed Multidisabler, it will revert your custom recovery to the stock OEM recovery.
I haven't had the tablet in my hands for a few months, so unfortunately I can't help more than that, as I said this was the last system I used, just because GSI are not very functional and are not always light, sometimes they crash more and it has more annoying bugs to fix that discourage daily use. my tip is, stay in stock Koo, excuses for those who can't, the most I can do now is guide them.
As a gift for you, I will teach you how to use Xposed :3
remembering, I did several tests that several times I faced bootlooops but in the end it worked for me, so notice, do it at your own risk.
5 - How to install end use EDexposed with Magisk
these versions were the ones that worked without problems in this rom
Install Riru - (Riru core) V21.0
Install Riru - Edxposed v 0.4.6.1(4510) YAHFA
Reboot, after reboot, install Edxposed Manager
and you can be happy
I thank you all for your help, and remembering that this was just a compilation of tips, to facilitate everyone, take due care to avoid problems, and don't forget to thank: 3 ?
Has anyone attempted this yet?
I am attempting to apply this root and I have run into a minor issue.
The AP Patched file from magisk isn't compressed correctly. Maybe I don't understand, but using 7zip, i can see that all the compressed files inside the AP file are LZ4's, but after patching with magisk, some become .IMG and odin errors our whenever I hit modem.Bin.
Any Ideas?
EngineeNerd said:
I am attempting to apply this root and I have run into a minor issue.
The AP Patched file from magisk isn't compressed correctly. Maybe I don't understand, but using 7zip, i can see that all the compressed files inside the AP file are LZ4's, but after patching with magisk, some become .IMG and odin errors our whenever I hit modem.Bin.
Any Ideas?
Click to expand...
Click to collapse
is the topic dead
EngineeNerd said:
is the topic dead
Click to expand...
Click to collapse
Hi friend, sorry but there are more current ways of routing, even already working on a TWRP, but now you can do the following, try using the same Firmware in the same version of the bootloader, otherwise there will always be an error, the file compressed this modified to work with Odin, I tested it myself on my T290, but I cannot guarantee its effectiveness if I try to use it in another version, I do not recommend doing this even.
I had trouble unlocking the bootloader until I did this:
After enabling OEM unlocking and turning the device off, plug in the USB cable. Hold both Vol + and Vol - at the same time, then unplug and replug the USB cable. The bootloader unlock screen should come up.
I posted this on twrp thread, but seems no one wants to answer , thought give it a try here?
Anyone know of a fix for the blank screen?
Not sure why they would lock down this tablet but not others?
Whats the point of unblocking the bootloader if you can not do custom roms , root etc?
My firmware is on T290XXU3BUC1
I can successfully installed twrp via Odin.
I reboot, instantly blank screen. I have rebooted into twrp with blank screen.
I was able to install the nexus rom, with adb twrp command line and works but all is blank screen.
I go back to stock and the display is back.
I have tried another twrp on this forum but that gives me security error.
I have also tried to patch ap tar with Magiskt but that flashes but when restart get security error.
Twrp is the only thing that works but complete blank screen with back light.
Tab is unlocked bootloader and oem unlocking on.
does this work if you're on a11?
themace51 said:
I posted this on twrp thread, but seems no one wants to answer , thought give it a try here?
Anyone know of a fix for the blank screen?
Not sure why they would lock down this tablet but not others?
Whats the point of unblocking the bootloader if you can not do custom roms , root etc?
My firmware is on T290XXU3BUC1
I can successfully installed twrp via Odin.
I reboot, instantly blank screen. I have rebooted into twrp with blank screen.
I was able to install the nexus rom, with adb twrp command line and works but all is blank screen.
I go back to stock and the display is back.
I have tried another twrp on this forum but that gives me security error.
I have also tried to patch ap tar with Magiskt but that flashes but when restart get security error.
Twrp is the only thing that works but complete blank screen with back light.
Tab is unlocked bootloader and oem unlocking o
Click to expand...
Click to collapse
themace51 said:
I posted this on twrp thread, but seems no one wants to answer , thought give it a try here?
Anyone know of a fix for the blank screen?
Not sure why they would lock down this tablet but not others?
Whats the point of unblocking the bootloader if you can not do custom roms , root etc?
My firmware is on T290XXU3BUC1
I can successfully installed twrp via Odin.
I reboot, instantly blank screen. I have rebooted into twrp with blank screen.
I was able to install the nexus rom, with adb twrp command line and works but all is blank screen.
I go back to stock and the display is back.
I have tried another twrp on this forum but that gives me security error.
I have also tried to patch ap tar with Magiskt but that flashes but when restart get security error.
Twrp is the only thing that works but complete blank screen with back light.
Tab is unlocked bootloader and oem unlocking on.
Click to expand...
Click to collapse
what are you specifically asking? the TWRP here is very functional, but custom roms are not very stable for this tablet, some GSI behave well, but it's still better to stock debloated
WillisD said:
isso funciona se você estiver em a11?
Click to expand...
Click to collapse
I do not think so
Hi, maybe you can help me.
i rooted my SM-T290 MXO with Android 10 but the system always asked me about a new patch update (May 1 Update) and i dont know how to apply updates so i downladed the firmware update via ODIN, long story short after applying the firmware and updating trough Smart Switch (because now my tablet say that the SO has been modified and now i can´t update trought OTA) and now i have Android 11 with One 3.1 so my questions are:
Can install TWRP like before in his version of Android?
In case i need to downgrade to Android 9, do i need to be the exact carrier (XAR = United States) in the file you put or should i use my carrier (MXO = Mexico) and is the same result?
I hope anyone can help me because i dont know much about rooting and is the second time im dealing with rooting a Samsung Device (My first attempt was a Galaxy 4 and was frustrating that KNOX detected my bad root)
Thanks in Advance.
MythoAegis said:
Hi, maybe you can help me.
i rooted my SM-T290 MXO with Android 10 but the system always asked me about a new patch update (May 1 Update) and i dont know how to apply updates so i downladed the firmware update via ODIN, long story short after applying the firmware and updating trough Smart Switch (because now my tablet say that the SO has been modified and now i can´t update trought OTA) and now i have Android 11 with One 3.1 so my questions are:
Can install TWRP like before in his version of Android?
In case i need to downgrade to Android 9, do i need to be the exact carrier (XAR = United States) in the file you put or should i use my carrier (MXO = Mexico) and is the same result?
I hope anyone can help me because i dont know much about rooting and is the second time im dealing with rooting a Samsung Device (My first attempt was a Galaxy 4 and was frustrating that KNOX detected my bad root)
Thanks in Advance.
Click to expand...
Click to collapse
yes, you can go back to previous versions, but it gets harder when you upgrade bootloader version.
In order not to crash the downgrade, you need to look for the latest Android version you want, from your region you are in now.
An example:
I'm on the latest version ZTO - Brazil - Android 11
to get back to Android 10 I need to download the latest ZTO version with Android 9, of course you can try between different regions, but it will be a little more complicated.
Hello
I was asking, how do i root this thing lol, it has been a nightmare
I can not root with custom magisk patched rom, as get boot error, and i can install Twrp, which works, but i just get a blank screen.
Was wondering if there was a work around?
themace51 said:
Hello
I was asking, how do i root this thing lol, it has been a nightmare
I can not root with custom magisk patched rom, as get boot error, and i can install Twrp, which works, but i just get a blank screen.
Was wondering if there was a work around?
Click to expand...
Click to collapse
You mentioned it's on Android 11, didn't you?!
well, I don't have Tab A with me anymore, but the suggestion I give you is to try to go back to Android 10, then install TWRP, and then try to install magisk, I can give you the last firmware I installed,
currently he is with my brother.
The firmware is Koreano, as I said, it is 32bits, and super functional.
Samsung SM-T290/T295 Galaxy Tab A 8.0 (2019) - Прошивки - 4PDA
Samsung SM-T290/T295 Galaxy Tab A 8.0 (2019) - Прошивки
4pda.to
take a look here, search for the firmware I told you about, very good by the way
Hey
I am on T290XXU3BUC1 and i do not understand the language on the link you post
I tried your tutorial , but i am getting
sw rev check fail [aboot] Fused 3 > binary 3
hello, about that, but lately I don't have much time, but I'll update it today if I can, you probably got this error because this firmware is old.on 4pda there is a newer version with root, remembering that currently you can root through twrp, I'm going to port my last attempts here, but I notice that I don't have the tablet in my hands. use translation tools, the site is in Russian
I updated the guide as I could, any doubts I'm still here, but I can only guide, it's no longer possible to test.
Thanks for the update. The only problem is, is that i have the newer tab and when I flash TWRP, i get a blank screen
I need a way to patch the firmware without failing, as i do not think anyone is trying to fix the blank screen bug with TWRP, unless they are on 4pad.to , but no idea due to the language barrier hehe.
themace51 said:
Thanks for the update. The only problem is, is that i have the newer tab and when I flash TWRP, i get a blank screen
I need a way to patch the firmware without failing, as i do not think anyone is trying to fix the blank screen bug with TWRP, unless they are on 4pad.to , but no idea due to the language barrier hehe.
Click to expand...
Click to collapse
have you tried to put the firmware I mentioned? this tutorial probably won't work on android 11 one ui 3.1, i say this because the TWRP is a bit old, so as long as it's on the updated firmware it's really hard to do anything.
if you don't want the specific KOO Firmware, you can get the latest firmware version for your region which is on android 10.