So this is all thanks to @tomiga and developer of Magisk and Odin. I’m not even tryin to take any credit for any of this.
Also, it's a rough draft, let me know if things need to be changed or clarified, though I'm not intending to keep this updated in the future.
1. Booted up, checked for firmware updates, got none, stuck on Jun security patch with firmware version T830XXU1ARGH/T830OXM1ARGH/
2. Settings>about tablet>tap on build number to get into developer settings.
3. Check OEM unlock, tablet resets and erases everything
4. Installed Samsung Windows USB Drivers from here: https://www.samsung.com/us/support/downloads/ on Windows 10 pc
5. Booted up, installed Magisk Manager v 5.9.1 from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
6. Downloaded boot image modified with Magisk 16.7 from here: https://forum.xda-developers.com/showpost.php?p=77439510&postcount=35
7. Installed Odin 3 from here: https://forum.xda-developers.com/galaxy-tab-s4/how-to/sm-t830-t830xxu1arh1-t3831918
8. Started Odin, checked AP and selected location of the BootImage from above as location of AP
9. Connected tab to PC, opened command prompt, adb reboot bootloader
10. Loading screen comes up on TAB, Odin says “Added!” to mean it recognizes the Tab
11. Hit “start” in Odin
12. After it’s done, Tab says something about a problem booting, Click “reset” on, tablet gets erased again
13. Booted up finally, on boot it says something about warranty and kernel and a bit being triggered
14. Connect tab to PC, command prompt, adb shell, “pm uninstall -k --user 0 com.samsung.android.securitylogagent”
15. Open Magisk Manager, it says tablet isn’t rooted.
16. ADB reboot bootloader, Repeat the flashing in Odin. Just don’t close Odin so it’s all ready to go, hit start
17. Tab rebooted fine
18. Open Magisk, Magisk says it’s rooted but want’s to install 17.1 which is the current stable version of Magisk.
19. Agree to install the Stable Magisk (17.1), choose direct install as it is “recommended”.
20. Reboot.
21. ???
22. Profit?
mistermojorizin said:
So this is all thanks to @tomiga and developer of Magisk and Odin. I’m not even tryin to take any credit for any of this.
Also, it's a rough draft, let me know if things need to be changed or clarified, though I'm not intending to keep this updated in the future.
1. Booted up, checked for firmware updates, got none, stuck on Jun security patch with firmware version T830XXU1ARGH/T830OXM1ARGH/
2. Settings>about tablet>tap on build number to get into developer settings.
3. Check OEM unlock, tablet resets and erases everything
4. Installed Samsung Windows USB Drivers from here: https://www.samsung.com/us/support/downloads/ on Windows 10 pc
5. Booted up, installed Magisk Manager v 5.9.1 from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
6. Downloaded boot image modified with Magisk 16.7 from here: https://forum.xda-developers.com/showpost.php?p=77439510&postcount=35
7. Installed Odin 3 from here: https://forum.xda-developers.com/galaxy-tab-s4/how-to/sm-t830-t830xxu1arh1-t3831918
8. Started Odin, checked AP and selected location of the BootImage from above as location of AP
9. Connected tab to PC, opened command prompt, adb reboot bootloader
10. Loading screen comes up on TAB, Odin says “Added!” to mean it recognizes the Tab
11. Hit “start” in Odin
12. After it’s done, Tab says something about a problem booting, Click “reset” on, tablet gets erased again
13. Booted up finally, on boot it says something about warranty and kernel and a bit being triggered
14. Connect tab to PC, command prompt, adb shell, “pm uninstall -k --user 0 com.samsung.android.securitylogagent”
15. Open Magisk Manager, it says tablet isn’t rooted.
16. ADB reboot bootloader, Repeat the flashing in Odin. Just don’t close Odin so it’s all ready to go, hit start
17. Tab rebooted fine
18. Open Magisk, Magisk says it’s rooted but want’s to install 17.1 which is the current stable version of Magisk.
19. Agree to install the Stable Magisk (17.1), choose direct install as it is “recommended”.
20. Reboot.
21. ???
22. Profit?
Click to expand...
Click to collapse
What directory is fastboot and ADB in????
ScottBroker said:
What directory is fastboot and ADB in????
Click to expand...
Click to collapse
Honestly, I don't think the directory should matter as long as adb and fastboot are in your environmental variables. And if they aren't, then just open a terminal in the directory you DO have adb and fastboot in....and run the commands from there.
https://www.xda-developers.com/15-s...ng-fast-adb-fastboot-and-driver-installation/
ScottBroker said:
What directory is fastboot and ADB in????
Click to expand...
Click to collapse
I already had adb/fastboot setup on my PC for my other phones, but didn't have the Samsung drivers. I installed the android SDK at some point to get the adb and fastboot drivers. Note, that unlike all of my other android devices, the tab S4 didn't respond to fastboot commands (for example, "fastboot devices" command in bootloader/download mode didn't return anything, which was unexpected). But Odin recognized it in that mode. So this doesn't rely on using any fastboot commands, just ADB.
Thanks for making a more user-friendly guide. I was considering doing so myself but got caught up with a lot of other stuff, so much appreciated.
mistermojorizin said:
1. Booted up, checked for firmware updates, got none, stuck on Jun security patch with firmware version T830XXU1ARGH/T830OXM1ARGH/
2. Settings>about tablet>tap on build number to get into developer settings.
3. Check OEM unlock, tablet resets and erases everything
4. Installed Samsung Windows USB Drivers from here: https://www.samsung.com/us/support/downloads/ on Windows 10 pc
5. Booted up, installed Magisk Manager v 5.9.1 from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
6. Downloaded boot image modified with Magisk 16.7 from here: https://forum.xda-developers.com/showpost.php?p=77439510&postcount=35
7. Installed Odin 3 from here: https://forum.xda-developers.com/galaxy-tab-s4/how-to/sm-t830-t830xxu1arh1-t3831918
8. Started Odin, checked AP and selected location of the BootImage from above as location of AP
9. Connected tab to PC, opened command prompt, adb reboot bootloader
10. Loading screen comes up on TAB, Odin says “Added!” to mean it recognizes the Tab
11. Hit “start” in Odin
12. After it’s done, Tab says something about a problem booting, Click “reset” on, tablet gets erased again
13. Booted up finally, on boot it says something about warranty and kernel and a bit being triggered
14. Connect tab to PC, command prompt, adb shell, “pm uninstall -k --user 0 com.samsung.android.securitylogagent”
15. Open Magisk Manager, it says tablet isn’t rooted.
16. ADB reboot bootloader, Repeat the flashing in Odin. Just don’t close Odin so it’s all ready to go, hit start
17. Tab rebooted fine
18. Open Magisk, Magisk says it’s rooted but want’s to install 17.1 which is the current stable version of Magisk.
19. Agree to install the Stable Magisk (17.1), choose direct install as it is “recommended”.
20. Reboot.
21. ???
22. Profit?
Click to expand...
Click to collapse
It should be possible to avoid the second system reset in step 12 by flashing a modified system.img with the offending package(s) removed.
tomiga said:
Thanks for making a more user-friendly guide. I was considering doing so myself but got caught up with a lot of other stuff, so much appreciated.
Click to expand...
Click to collapse
I was able to root my Tab S4, but now my camera does not work. I tried installin xposed, and it didnt work, so I did a factory data reset and now when I set it up it was still rooted, but the camera does not work. Any suggestions before I flash the stock firmware back to it?????
ScottBroker said:
I was able to root my Tab S4, but now my camera does not work. I tried installin xposed, and it didnt work, so I did a factory data reset and now when I set it up it was still rooted, but the camera does not work. Any suggestions before I flash the stock firmware back to it?????
Click to expand...
Click to collapse
It sounds as if the kernel you flashed isn't compatible with the vendor.img of the firmware that you're on.
The rooting procedure described here uses a modified boot.img that may now be too old for the updated firmware that a lot of us have since received on our devices.
If that's the issue, you will either need to downgrade your firmware to match the one your kernel was built against (flashing vendor.img from that version is probably sufficient), or upgrade your kernel to match the firmware you're running now. That will entail modifying the new boot image for root in the same way as the one you downloaded as part of the rooting process.
This is why, in spite of feeling tempted, I'm personally holding off on rooting this device until I or someone else gets TWRP working on it.
ianmacd said:
It sounds as if the kernel you flashed isn't compatible with the vendor.img of the firmware that you're on.
The rooting procedure described here uses a modified boot.img that may now be too old for the updated firmware that a lot of us have since received on our devices.
If that's the issue, you will either need to downgrade your firmware to match the one your kernel was built against (flashing vendor.img from that version is probably sufficient), or upgrade your kernel to match the firmware you're running now. That will entail modifying the new boot image for root in the same way as the one you downloaded as part of the rooting process.
This is why, in spite of feeling tempted, I'm personally holding off on rooting this device until I or someone else gets TWRP working on it.
Click to expand...
Click to collapse
I just reflashed the stock image and I am back to normal
ScottBroker said:
I just reflashed the stock image and I am back to normal
Click to expand...
Click to collapse
Which will also align your camera firmware with your kernel again, but now you don't have root, right?
ianmacd said:
Which will also align your camera firmware with your kernel again, but now you don't have root, right?
Click to expand...
Click to collapse
No, and I have the wifi version
ScottBroker said:
No, and I have the wifi version
Click to expand...
Click to collapse
I have both root and camera working fine. Only difference I can tell from your software version is under Build Number mine has t830XXU1ARGH. Have you disabled any apps by chance? On one of my phones camera would crash if i disabled NFC service.
mistermojorizin said:
I have both root and camera working fine. Only difference I can tell from your software version is under Build Number mine has t830XXU1ARGH. Have you disabled any apps by chance? On one of my phones camera would crash if i disabled NFC service.
Click to expand...
Click to collapse
His problem was almost certainly due to his having ARH5 firmware on the device (specifically the vendor.img component) but an ARH1 kernel. Such mismatches usually present themselves in the form of a non-functional camera.
After upgrading the firmware past ARH5, the new boot image should be rooted, rather than flashing the older one given in the rooting instructions of this thread.
Please also note that @ashyx has started work on TWRP and even released an initial test build for the T820. I intend to give that a try this afternoon when I get home.
Sent from my SM-G965F using XDA Labs
ianmacd said:
His problem was almost certainly due to his having ARH5 firmware on the device (specifically the vendor.img component) but an ARH1 kernel. Such mismatches usually present themselves in the form of a non-functional camera.
After upgrading the firmware past ARH5, the new boot image should be rooted, rather than flashing the older one given in the rooting instructions of this thread.
Please also note that @ashyx has started work on TWRP and even released an initial test build for the T820. I intend to give that a try this afternoon when I get home.
Sent from my SM-G965F using XDA Labs
Click to expand...
Click to collapse
Do you have a rooted image??? It was nice to be rooted for a while. I'm pretty sure flashfire would work until twrp is available.....
ScottBroker said:
Do you have a rooted image??? It was nice to be rooted for a while. I'm pretty sure flashfire would work until twrp is available.....
Click to expand...
Click to collapse
flashfire won't open. i went through something like this on my fire hd 10, had to install an xposed module to trick flashfire into thinking we're back in an older time and install a really old version of flashfire. Otherwise, the newer version of flashfire would just close/won't open.
hope this all settles down to a working version soon
ScottBroker said:
Do you have a rooted image??? It was nice to be rooted for a while. I'm pretty sure flashfire would work until twrp is available.....
Click to expand...
Click to collapse
TWRP is on the way. @ashyx is working on it. This thread is tracking the progress.
ianmacd said:
TWRP is on the way. @ashyx is working on it. This thread is tracking the progress.
Click to expand...
Click to collapse
Exciting stuff ?
Will this work for LTE? I don't see the option to oem unlock on my Verizon version. Does that mean locked bootloader?
machx1111 said:
Will this work for LTE? I don't see the option to oem unlock on my Verizon version. Does that mean locked bootloader?
Click to expand...
Click to collapse
Most likely. Verizon normally make them unlockable
Related
If you are on Lollipop, this guide is NOT for you!
Almost none of this is my work, I just collect it and put it together in one place and I'm writing a small how-to get things done.
PLEASE ONLY PROCEED AT YOUR OWN RISK!!!!!!!!!
ONLY FOR ZX551ML
Bootloader unlock:
Currently the only way I was able to get ROOT on the phone was by installing it from TWRP which required an unlocked bootloader, so the first step is to get the bootloader unlocked, to do this please follow this steps:
1) Enable USB debugging - If you do not know what is that and how to do it, you should probably STOP right here.
2) Download and extract: Unlock 6_ZX551ML.ZIP
3) From the extracted folder run unlock.bat (This will restart your phone into fastboot mode, downgrade the bootloader and unlock it)
4) When step 3 is completed, you need to run restore.bat
If everything went on correctly your boot screen should be inverted (white background, black Asus text). This was the most risky part. I only have my phone and it worked, but if something goes wrong here you might end up bricking your phone, so please take extreme care, always read the messages on the screen!!!!!
Custom Recovery:
1) Now to get a custom recovery, please download TWRP-3.0.2-M1-Z00A.img.
2) Put your phone into bootloader mode, if your phone is currently in use, just use the following commands:
Code:
adb reboot bootloader
Alternatively you can power off the phone, remove the USB cable. Power it back on while holding the volume up button.
3) once your phone if in bootloader mode please use the following command:
Code:
fastboot flash recovery TWRP-3.0.2-M1-Z00A.img
4) Use the vol up & down to select "RECOVERY"
5) Use the power button (short press) to reboot to TWRP
ROOTING
1) Download BETA-SuperSU-v2.74-2-20160519174328-patch-by-shakalaca-for-zenfone2-6.0_(1).zip
2) In recovery select Advanced -> Sideload
3) From your computer use the following commands:
Code:
adb sideload "BETA-SuperSU-v2.74-2-20160519174328-patch-by-shakalaca-for-zenfone2-6.0_(1).zip"
4) Once it's completed installing, restart the phone to system
FLASHABLE STOCK ROM
If you have TWRP installed and you want to flash the latest stock ROM, you will need to, make sure you un-root your phone from the supersu app, reboot to recovery and sideload the zip. You can also copy the zip to your phone and install it from twrp. When installing the stock rom, your bootloader will be locked again, so you will need to unlock it (if you wish), also you will need to root again, because the root is lost. However the modified stock rom will NOT remove the custom recovery giving you freedom to flash whatever you like in the future...
XPOSED
Xposed on our device won't work if we have SuperSu installed. If you want to use Xposed modules you will need to use PHH's SuperUser instead. All files required for Xposed/Magisk/Phh's SuperUser are available in the Xposed folder.
Available modified stock rom versions:
UL-Z00A-WW-4.21.40.141-user-TWRP.zip - Updated: 2016-Oct-07
UL-Z00A-WW-4.21.40.197-user-TWRP.zip - Updated: 2016-Dec-16
Files can be downloaded from: here
Again, please proceed on your own risk.
Special tanks and credits to all the guys who made this possible, namely:
@sorg @social-design-concepts @shakalaca - For bootloader unlock
@jrior001 for the TWRP
@shakalaca - For the modified SuperSU package.
Magisk / systemless should also work?
any way to get back the noninverted Bootscreen?
Tr4sHCr4fT said:
Magisk / systemless should also work?
any way to get back the noninverted Bootscreen?
Click to expand...
Click to collapse
Yes I'm using Magisk, but even with it I wasn't able to use Google Pay. To get back to non inverted, you will need to flash the locked bootloader.
Emil Borconi said:
Yes I'm using Magisk, but even with it I wasn't able to use Google Pay. To get back to non inverted, you will need to flash the locked bootloader.
Click to expand...
Click to collapse
While essentially true the user can always use a different boot animation by flashing one via twrp. There might even be one somewhere of the unmodified asus screen.
Can anyone confirm the flashable Rom mentioned in Post #1 is MM 6.0.1? I ask because my phone upgraded itself right after I booted it up and I wondered if it was on a newer version than the downloadable one. Pretty sure the update was only security updates given it was only around 80mb.
The actuall boot screen is only a couple of seconds long while the boot animation shown
---------- Post added at 10:00 PM ---------- Previous post was at 09:02 PM ----------
Well as usual the linux users drew the short straw. The shell script is for mac users. I decided to see about running the lines manually but never even reached the "danger zone". As soon as I did an "adb reboot bootloader" I followed up with "sudo fastboot devices" (some linux distro's need sudo..some don't)....and nothing shows up although I can clearly see the device is hooked up and in fastboot mode as well as the fact the adb reboot bootloader worked. I swap out one of my other devices and check things...they show up fine in fastboot....ok...so what's missing from this picture?
*update* solved by updating the ubuntu adb and fastboot binaries from here: https://github.com/simmac/minimal_adb_fastboot/tree/master/linux
*update2* bootloader unlocked, supersu flashed and verified. Much appreciated.
I ran the bootloader unlock and it appeared to work. Now it keeps booting back into the bootloader. I can't seem to get it to boot normal. Suggestions?
Nevermind, I didn't realize that I needed to run restore.bat while still in the bootloader. It is booting now! I was able to follow your guide and it is now rooted.
Regarding the marshmallow zip you include. I have a couple questions.
- For the modified stock version that will keep the recovery do I just need to flash it from recovery?
- Do I need to unroot before flashing this modified stock marshmallow?
Thanks!
slgooding said:
I ran the bootloader unlock and it appeared to work. Now it keeps booting back into the bootloader. I can't seem to get it to boot normal. Suggestions?
Nevermind, I didn't realize that I needed to run restore.bat while still in the bootloader. It is booting now! I was able to follow your guide and it is now rooted.
Regarding the marshmallow zip you include. I have a couple questions.
- For the modified stock version that will keep the recovery do I just need to flash it from recovery?
- Do I need to unroot before flashing this modified stock marshmallow?
Thanks!
Click to expand...
Click to collapse
Happy to read you got it booting, by the time I got to answer you seemed to git it figured out.
Regarding the zip, yes flash from recovery and you don't need to unroot before, but you will need to root after flashing.
However I do suggest you make a backup before flashing jsut in case....
Emil Borconi said:
Happy to read you got it booting, by the time I got to answer you seemed to git it figured out.
Regarding the zip, yes flash from recovery and you don't need to unroot before, but you will need to root after flashing.
However I do suggest you make a backup before flashing jsut in case....
Click to expand...
Click to collapse
I'm assuming the file is just for folks who are on lollipop who want to upgrade? Didn't see any need to flash it since already on 6.0.1 and have it rooted...unless I'm missing something again.
I read this after I went to 6.0.1 from Asus's manual download and update process. I can't get ADB to connect in the OS (developer mode never displays, even though it tells me I'm a developer after doing kernel ver. button process). I tried to get adb devices -l in fastboot and recovery, and it wont discover it. I've tried multiple windows drivers (including the one that worked when I flashed the firmware the first time) to no avail. Any ideas?
Irishman2020 said:
I read this after I went to 6.0.1 from Asus's manual download and update process. I can't get ADB to connect in the OS (developer mode never displays, even though it tells me I'm a developer after doing kernel ver. button process). I tried to get adb devices -l in fastboot and recovery, and it wont discover it. I've tried multiple windows drivers (including the one that worked when I flashed the firmware the first time) to no avail. Any ideas?
Click to expand...
Click to collapse
If windows doesn't see the phone when in recovery there is something wrong, this can be:
1) Wrong driver
2) Damaged USB cable
3) Damaged USB port.
When you are in recovery you should see the phone with adbm if you are in fastboot you should see the phone with:
Code:
fastboot devices
If nothing works you have the nuclear option.
Manually download the original firmware from Asus website: https://www.asus.com/support/Download/39/1/0/26/BXbNqJplzZiLmk6G/32/
copy the zip to an Sd card.
1) Now Turn Off your phone and boot into recovery mode by pressing Power+Volume UP.
2) Now in recovery mode choose to apply update from sdcard.
3) Now select the zip file.
4) Now wait until the process complete and then Reboot the phone.
5) Done!
famewolf said:
I'm assuming the file is just for folks who are on lollipop who want to upgrade? Didn't see any need to flash it since already on 6.0.1 and have it rooted...unless I'm missing something again.
Click to expand...
Click to collapse
More or less true, but somehow I was on a 6.0.1 version which is now gone from the firmware list of Zenfone, meaning I have updated from 6.0.1 to 6.0.1
Again now I see there is a new firmware released yesterday if I have the time I will patch that system image as well so it can be upgraded with TWRP.
famewolf said:
I'm assuming the file is just for folks who are on lollipop who want to upgrade? Didn't see any need to flash it since already on 6.0.1 and have it rooted...unless I'm missing something again.
Click to expand...
Click to collapse
Just for you I've just uploaded the 4.21.40.197 release as well... so now there is a point of the TWRP rom's
Emil Borconi said:
Just for you I've just uploaded the 4.21.40.197 release as well... so now there is a point of the TWRP rom's
Click to expand...
Click to collapse
Typical....now you've given me work I need to do on the phone. ;P
Appreciate your work!
Out of curiosity have you tried xposed?
famewolf said:
Typical....now you've given me work I need to do on the phone. ;P
Appreciate your work!
Out of curiosity have you tried xposed?
Click to expand...
Click to collapse
Yes and it works. I tried a few modules, but generally speaking I'm not a big xposed user myself. Nify doesn't work to well because of all the asus software on it and I wasn't able to get google assistant either. Android audo mod worked perfectly, so yeah generally speaking xposed work's
Emil Borconi said:
Yes and it works. I tried a few modules, but generally speaking I'm not a big xposed user myself. Nify doesn't work to well because of all the asus software on it and I wasn't able to get google assistant either. Android audo mod worked perfectly, so yeah generally speaking xposed work's
Click to expand...
Click to collapse
Thanks...that answers all my questions except for figuring out what's safe to disable. I put a post in q&a but no replies..the zoom appears to have a very small group on xda. I'll figure it out eventually.
famewolf said:
Thanks...that answers all my questions except for figuring out what's safe to disable. I put a post in q&a but no replies..the zoom appears to have a very small group on xda. I'll figure it out eventually.
Click to expand...
Click to collapse
Actually most if them can be. Here is a print screen of the ones I have disabled on my phone hover I have a zenpad z380c which I use as my car dashboard and on that one o have disabled almost of all of the apps, except zenhome, audio manager and the file manager.
Yes I was surprised to find out that there is almost no zoom community.
Emil Borconi said:
Actually most if them can be. Here is a print screen of the ones I have disabled on my phone hover I have a zenpad z380c which I use as my car dashboard and on that one o have disabled almost of all of the apps, except zenhome, audio manager and the file manager.
Yes I was surprised to find out that there is almost no zoom community.
Click to expand...
Click to collapse
I'm actually enjoying mobile managers auto startup managing...it's done a good job of keeping 10000 things from running at startup that don't need to although "Startup Manager" would do a similar job for free. I'm liking the zenui launcher and calling screen so don't want to break anything related to that...the phone's been performing exceptionally well for days on end with no required reboots. Been very impressed. Previously been fighting with a T-mobile V10 and an Alcatel Idol 3...the v10 had spontaneous reboots...the idol had a stock rom with a bunch of lag in it....tiny to nothing development on both of those.
What about Zentalk, ZenChoice, PhotoCollage, MyAsus Service center, Clean Master, Audiowizard and Bug Reporter?
famewolf said:
I'm actually enjoying mobile managers auto startup managing...it's done a good job of keeping 10000 things from running at startup that don't need to although "Startup Manager" would do a similar job for free. I'm liking the zenui launcher and calling screen so don't want to break anything related to that...the phone's been performing exceptionally well for days on end with no required reboots. Been very impressed. Previously been fighting with a T-mobile V10 and an Alcatel Idol 3...the v10 had spontaneous reboots...the idol had a stock rom with a bunch of lag in it....tiny to nothing development on both of those.
Click to expand...
Click to collapse
I use tasker for that, but yes I agree as a whole is not bad, this is my 4rd Asus product (Zenfone 4, Zenfone 2, Zoom and Zenpad) and overall I'm quite impressed with how they perform, just the support from Asus isn't really the top of the cream... they released MM when other were releasing N... so yeah a bit of sour taste, otherwise happy. And the camera, I think it's brilliant, not the best on the market, but the optical zoom is cool, as well as the camera app which allows you to do some nice manual shooting.
Emil Borconi said:
I use tasker for that, but yes I agree as a whole is not bad, this is my 4rd Asus product (Zenfone 4, Zenfone 2, Zoom and Zenpad) and overall I'm quite impressed with how they perform, just the support from Asus isn't really the top of the cream... they released MM when other were releasing N... so yeah a bit of sour taste, otherwise happy. And the camera, I think it's brilliant, not the best on the market, but the optical zoom is cool, as well as the camera app which allows you to do some nice manual shooting.
Click to expand...
Click to collapse
I listed a few apps in my previous post I wondered if you had looked at..it was a last minute addition so you may have missed it. I own tasker...I'm unaware of using it to stop tasks from running at bootup although I have used it to MAKE some apps run after "Boot Completed".
famewolf said:
I listed a few apps in my previous post I wondered if you had looked at..it was a last minute addition so you may have missed it. I own tasker...I'm unaware of using it to stop tasks from running at bootup although I have used it to MAKE some apps run after "Boot Completed".
Click to expand...
Click to collapse
Generally tasker can be used for almost anything.... but I'm doing most of the thing with root+shell scripts, but yes nothing wrong with the app provided by Asus. I think everybody uses the setup/software he/she is most comfortable using... and there is no right or wrong.... that's until you are NOT and iCrap user, because that is the ultimate WRONG! )
Emil Borconi said:
Generally tasker can be used for almost anything.... but I'm doing most of the thing with root+shell scripts, but yes nothing wrong with the app provided by Asus. I think everybody uses the setup/software he/she is most comfortable using... and there is no right or wrong.... that's until you are NOT and iCrap user, because that is the ultimate WRONG! )
Click to expand...
Click to collapse
Well from the lack of posts it appears you and I ARE the zenfone zoom community. Any idea where the system updates get stored after downloading? I thought in /cache based on regular zenfone posts but was unable to see it. I've got one available but it has to be modified for twrp compatibility as well as unrooting temporarily.
Official updates for our M2 tablet,
although having installed another
recovery and root access, already.
- Disclaimer
Well, whatever you do with this guide is all up to you and in your own responsibility. You
should have basic knowledge about ADB and flashing, which is explained in many other
threads here on our beloved XDA.
- Issue
When you used this guide (https://goo.gl/r04XjJ) or any other one to give your M2 tablet
another recovery and therefore root rights, you have now the problem, that EMUI will show
you new updates, but you are not able to install them, because of the missing stock recovery,
of course.
- Solution
So, you have to flash back the original stock recovery, getting the official update and then you
can flash back your TWRP recovery.
- Guide
1. You should start your EMUI update programme/app and start the download of your update.
When it is finished, it will ask you to reboot into recovery and install automatically. As you have
no stock recovery I strongly advise not to do so. Usually nothing happens, but there is one case
reported, where it somehow ****ed up the guy's tablet. I am not sure, if that story is true, but
well, I have warned you.
2. Just turn your tablet off after you have finished downloading the update (it will wait now in
the directory "HwOUC" on your tablet and it is called "update.zip" - just let it sleep there).
3. Start the tablet in the fastboot recovery mode, meaning plugging in the USB cable (connected
to the computer) and hold the buttons "power" and "volume down", immediately, until a white
screen appears, which is the fastboot recovery screen. It should tell you, it has the bootloader
unlocked, which is normal, because you did that earlier on with any of the other guides (see above).
4. Copy the downloaded stock recovery of your choice to your ADB directory. In my case this is
"c:\ADB", but this depends on your way of installation.
5. Now open up a command line in Windows (with Windows key + R) and type "cmd") and go to
your ADB directory, using commands like "cd .." and "cd adb".
6. When having arrived in the ADB directory, you have to enter these commands one after the other:
fastboot flash recovery stock-recovery.img
fastboot reboot
If you renamed the recovery file, then you have to consider that in the command, of course.
7. The device will reboot directly into the recovery, because it "sees" the update in the update
directory et voila ... you are getting your awaited update. Sometimes it will boot not into the EMUI
recovery directly, but then you hast have to start the tablet normally, open up the EMUI app and
download the update again and do the OTA update properly with the reboot it tells you to do,
when it is finished.
8. Okay, now you have received your update, but if you want to have back your TWRP, you just
have to turn off your tablet and boot into the fastboot recovery again (see 3.).
9. You have to copy your TWRP recovery to your ADB directory (in my case "twrp.img" in "c:\ADB").
10. Now open up a command line in Windows (with Windows key + R and type "cmd") and go to
your ADB directory, using commands like "cd .." and "cd adb".
11. When having arrived in the ADB directory, you have to enter these commands one after the other:
fastboot flash recovery twrp.img
fastboot reboot
12. The tablet will reboot and you are back to a working lovely updated M2 tablet.
- Root:
If you want to have root rights, I strongly recommend flashing Magisk within TWRP, because it is
just a nice and more modern approach to having root. It works very fine on my M2 10 tablet. The
link for the files and guide is here:
https://goo.gl/UXYk4d
It is very easy. You just flash Magisk 12 in TWRP and then install the Magisk Manager app from the
Play store.
- Files for M2-802L and M2-A01L:
https://ufile.io/0df492 (all four recoveries here)
https://files.fm/u/aajdmadr (all four recoveries here)
https://www.file-upload.net/download-12438839/HuaweiM2recoveries.rar.html (all four recoveries here)
Have fun with your updated tablet. ... and I am happy, if I could help you - any coffee appreciated.
...
..
.
+++ saved +++
Additionally, I can offer you the updates B007 and B010 (most current one) for the
M2 10 LTE (M2-A01L), because I managed to save them/back them up. These are the
European versions of B007 and B010 with all language files, I believe.
So, who is having a M2-A01L and is still sitting on B006 or B007, might try a manual
update, which is as easy as pie. It is just one simple step.
Also, an update from B009 to B010 might be possible.
Of course, I cannot give any guarantee for Huawei's update files, which you will
understand, I guess.
what android version ?? M2-801L, thanks
Eagle-no1 said:
what android version ?? M2-801L, thanks
Click to expand...
Click to collapse
M2-A01L, not M2-801L. For all 8 models you find your ROMs here:
https://forum.xda-developers.com/me...om-8-0-models-stock-marshmallow-roms-t3535466
or
https://forum.xda-developers.com/me...-b207-android-6-0-marshmallow-emui-4-t3533572
or
https://forum.xda-developers.com/mediapad-m2/development/rom-stock-rooted-xposed-t3519031
xsycox said:
Additionally, I can offer you the updates B007 and B010 (most current one) for the
M2 10 LTE (M2-A01L), because I managed to save them/back them up. These are the
European versions of B007 and B010 with all language files, I believe.
So, who is having a M2-A01L and is still sitting on B006 or B007, might try a manual
update, which is as easy as pie. It is just one simple step.
Also, an update from B009 to B010 might be possible.
Of course, I cannot give any guarantee for Huawei's update files, which you will
understand, I guess.
Click to expand...
Click to collapse
I'd greatly appreciate it, if you could share. Got the problem that my A-01L got corrupted. The only official ROM I've been able to find has been B005 what is somewhat old. As it seems to be a pre-release version the tablet doesn't find any updates. Thus I'd like to try to upgrade to B007, or even B010 manually when I'm back home. Currently I'm on a weekend trip as friends of mine are going to marry tomorrow. Thus I'd be able to download them on Sunday evening if you'd provide them.
Regards
Sent from my htc_pmeuhl using XDA Labs
Tried Magisk but can't pass Safetinet test even with Magisk hide enable...
is it working for you?
5m4r7ph0n36uru said:
I'd greatly appreciate it, if you could share. Got the problem that my A-01L got corrupted. The only official ROM I've been able to find has been B005 what is somewhat old. As it seems to be a pre-release version the tablet doesn't find any updates. Thus I'd like to try to upgrade to B007, or even B010 manually when I'm back home. Currently I'm on a weekend trip as friends of mine are going to marry tomorrow. Thus I'd be able to download them on Sunday evening if you'd provide them.
Regards
Click to expand...
Click to collapse
https://forum.xda-developers.com/me...om-official-manual-updates-m2-tablet-t3595211
zedoc said:
Tried Magisk but can't pass Safetinet test even with Magisk hide enable...
is it working for you?
Click to expand...
Click to collapse
I have Magisk running on several devices, including the M2-A01L, but I must admit,
I never got the Safetynet passed, even with Magisk hide enabled.
I just use it as systemless root and with systemless Xposed, which is great.
zedoc said:
Tried Magisk but can't pass Safetinet test even with Magisk hide enable...
is it working for you?
Click to expand...
Click to collapse
xsycox said:
I have Magisk running on several devices, including the M2-A01L, but I must admit,
I never got the Safetynet passed, even with Magisk hide enabled.
I just use it as systemless root and with systemless Xposed, which is great.
Click to expand...
Click to collapse
After enabling magisk hide, you have to reboot your device. Got the 801L working with that and safetynet passes.
Noob Question on recovery files
Hi, and thanks for a incredible well detailed guide for updating. Came here because I haven't found any good recovery files for the wifi model. I've been trying (unsuccessfully may I add...) to install TWRP and magisk. So, my question is: can the recovery files for the LTE model be used on the wifi model? (M2-A01w). Thanks for your help!
myst771 said:
Hi, and thanks for a incredible well detailed guide for updating. Came here because I haven't found any good recovery files for the wifi model. I've been trying (unsuccessfully may I add...) to install TWRP and magisk. So, my question is: can the recovery files for the LTE model be used on the wifi model? (M2-A01w). Thanks for your help!
Click to expand...
Click to collapse
Sorry, I have been on vacation.
To be honest, I am not sure, if the recovery for M2-A01L works on M2-A01w, too, but you can just try it.
I think, there should not be that big a problem, because the recovery has nothing to do with Wi-Fi or LTE, at all. It is just important, that partition tables and drives are accessible the same way and well, I really think, there is not much difference in between the M2 10 models.
From M2 8 to 10 there is a difference, of course. That is why I uploaded both recoveries (for 802L and A01L).
Just use that guide (https://forum.xda-developers.com/mediapad-m2/how-to/guide-unlock-bootlader-twrp-root-huawei-t3322340) without the SuperSU flashing and my recoveries in this guide.
Hi guys,
I need help, I have a M2 10 LTE previously modded with TWRP for root and I've just followed this guide to update from 007 to 010 version.
So I've flashed the stock-recovery, rebooted the tablet, requested the firmware update (I don't know if I got any error during the process) and the tablet has rebooted. Now it's stuck on HUAWEI logo..
I use this tablet for work so I really need to recover it asap.
Please help.
Shocker580 said:
Hi guys,
I need help, I have a M2 10 LTE previously modded with TWRP for root and I've just followed this guide to update from 007 to 010 version.
So I've flashed the stock-recovery, rebooted the tablet, requested the firmware update (I don't know if I got any error during the process) and the tablet has rebooted. Now it's stuck on HUAWEI logo..
I use this tablet for work so I really need to recover it asap.
Please help.
Click to expand...
Click to collapse
Could upload the B010 fullstock ROM/firmware. Thus you could reset the device to the latest stock ROM using the /dload method and gain a factory rested Huawei, as if out of the box. Just quote me if you'd want me to upload and I'll share the link asap. Took that way myself as soon as I found the full stock ROM.
Sent from my htc_ocnuhl using XDA Labs
thanx
Dear xsycox
I have an issue where I updated my W version tablet to L version accidentally and I am having issue getting it back..
I am currently trying to get some help in this thread: https://forum.xda-developers.com/me...-m2-installed-wrong-update-zip-t3563105/page2
Can you please help me out? do you have any idea what ican do to get back to W version?
Thanks!
First things first. I surrender. I'm a noob with android. I had windows phone previously and only now came to android.
Here's the scenario:
1. My z2 force was properly rooted with magisk and twrp. I followed the guide in xda only.
2. My device was brought from India so carriers like sprint, t-mobile are not applicable I think.
What I Did:
0. Wanted to unroot my device. So, I decided to first uninstall the modules in magisk that I had installed.
1. Tried to uninstall magisk modules and rebooted from the magisk application.
2. Got into Boot loop, so went to recovery mod and wiped everything. Hard reset was done.
3. Installed magisk app again and clicked uninstall to remove root. I wanted to install the latest security update. Update kept failing so I decided to unroot. I choose uninstall completely option.
4. Rebooted the phone manually after clicking uninstall in magisk manager. Using the 'root checker' app I checked if unrooting was successful but it said, 'root was not properly installed' or something like that. So, I installed magisk manager again and again uninstalled root completely.
5. Still same issue. Root checker said the same thing again. So, installed magisk manager again and this time I wanted to remove root using ES file manager as I saw in an online guide. But I couldn't give it root permission because it was not properly installed as said by root checker. So, I decided to root my phone properly but stupid me, clicked 'install' in magisk manager and chose the recommended option (don't remember exactly what it was). It downloaded magisk zip and did some changes and asked to reboot. After rebooting, my phone went straight to the black screen with an android icon and 'no command' written below it. It kept going there again and again.
6. I assume that is the recovery mode. I press volume up and power button and choose the wipe everything again(Like I did before) to hard reset phone. Wiping was successful but it still kept booting to that black screen.
Additional Info:
1. Phone wasn't carrier version. It was bought in India. It is running Oreo 8.0.
2. In bootloader menu : (Not stating all)
BL: MBM-3.0-nash_retail-641a15b-180306
Product/Variant: nask xt1789-06 64GB PVT
Console[NULL] :null
Tools Mode Config: DISABLED
Power OK
flashing_unlocked
Software Status : Modified
Transfer Mode : USB Connected.
3. Yes, Bootloader menu is accessible.
4. Choosing recovery mode in bootloader menu reboots phone and takes me to that blank screen I mentioned before.
5. Connecting to USB to my PC when in bootloader menu, it connects as 'Fastboot nash S'. ADB terminal says no devices found.
What I want:
1. Boot into OS.
2. Remove root completely so I can install system update.
Please help or offer suggestions as I do not have a secondary device with me. If I have to absolutely go to a service center, I will.
You should flash it back to stock.
You posted that your phone is nash xt1789-06 64GB PVT, you can grab the latest firmware here.
The flashing instructions are here in post #5, and any question you might have is most likely answered in that thread.
Just download the firmware, boot into bootloader mode, and follow the instructions.
FYI in fastboot mode adb commands don't work, it's fastboot. To verify that you're connected and ready type
Code:
fastboot devices
and you should see your serial# like you do in adb.
That should put you back to stock and good to go.
41rw4lk said:
You should flash it back to stock.
You posted that your phone is nash xt1789-06 64GB PVT, you can grab the latest firmware here.
The flashing instructions are here in post #5, and any question you might have is most likely answered in that thread.
Just download the firmware, boot into bootloader mode, and follow the instructions.
FYI in fastboot mode adb commands don't work, it's fastboot. To verify that you're connected and ready type
Code:
fastboot devices
and you should see your serial# like you do in adb.
That should put you back to stock and good to go.
Click to expand...
Click to collapse
Thank you for the reply. I figured it out and went ahead with it. But now, I'm not seeing the May security update. The device shows it has March update and that no other update is available. Any idea why? Also, root checker still says 'root not properly installed'. How to unroot completely? Thanks a lot!
Sparkzz27 said:
You should flash it back to stock.
You posted that your phone is nash xt1789-06 64GB PVT, you can grab the latest firmware here.
The flashing instructions are here in post #5, and any question you might have is most likely answered in that thread.
Just download the firmware, boot into bootloader mode, and follow the instructions.
FYI in fastboot mode adb commands don't work, it's fastboot. To verify that you're connected and ready type
Thank you for the reply. I figured it out and went ahead with it. But now, I'm not seeing the May security update. The device shows it has March update and that no other update is available. Any idea why? Also, root checker still says 'root not properly installed'. How to unroot completely? Thanks a lot!
Click to expand...
Click to collapse
Did you look to see if the May Security Update has been released for your specific device? When you downloaded the stock firmware did you look to see what month security patch it contained? Have you tried to perform a system update to see if you can OTA to the latest security patch?
Now, if you completely flashed back to stock then root is removed. Root checker says that because root access is not installed at all. Flashing back to stock removes any trace of root, IIRC.
Sent from my Moto Z2 Force using XDA Labs
Don't forget, if you followed the flashing instructions from the other post they were omitting the gpt.bin and bootloader. So if you didn't flash those then that's why you're probably not seeing any updates, you need to be on full stock all matched up. Just reflash the firmware you downloaded in its entirety. @fast69mopar is right, once you flash a new boot.img root is gone, and since you flashed back to stock it's definitely gone.
Sparkzz27 said:
Thank you for the reply. I figured it out and went ahead with it. But now, I'm not seeing the May security update. The device shows it has March update and that no other update is available. Any idea why? Also, root checker still says 'root not properly installed'. How to unroot completely? Thanks a lot!
Click to expand...
Click to collapse
If you flash with factory image you should be unroot completely and root checker will keep telling you "root not properly installed" if you are not rooted just ignore root checker if you not planning to be rooted.
Hi there I have a xt1789-06 I was not getting updates and flashed the first Oreo update from here https://mirrors.lolinet.com/firmware/moto/nash/official/RETAIL/
My phone now does the updates and everything works fine.
However I did try to flash a custom ROM and root I made a mistake and ended up both a hard brick, because I was on Oreo I thought that flashing the Oreo blank flash would rectify the problem, but it was not working so I tried flashing the N blank flash and it worked.
I've come from using Samsung phones so I'm use to Odin and have not used fastboot commands. After reading many threads I know what I had done was not decrypting my device which ended up with a hard brick I will in the future flash a custom ROM now I know a little bit more.
Blank flash files are here
https://mirrors.lolinet.com/firmware/moto/nash/blankflash/
Then once back to fastboot flash the flash all from the link at the top of my post.
41rw4lk said:
Don't forget, if you followed the flashing instructions from the other post they were omitting the gpt.bin and bootloader. So if you didn't flash those then that's why you're probably not seeing any updates, you need to be on full stock all matched up. Just reflash the firmware you downloaded in its entirety. @fast69mopar is right, once you flash a new boot.img root is gone, and since you flashed back to stock it's definitely gone.
Click to expand...
Click to collapse
Hi, sorry I was busy with work. I managed to use my phone that way. I didn't use the instructions in that post. Instead, I download flashallutilities (In how to return to stock post in xda for z2 force), then ran the batch file which did all the work. I noticed other problems too,
1. My Jio sim(4g LTE) does not show 'enhanced LTE mode' in options. Also when I call someone, it fails immediately saying 'call failed. try another method.' However, internet connection works from the sim. My other sim works fine for calls and data.
2. I'm seeing other keyboards in manage keyboards section. I don't recall seeing google pinyin input, zhuyin input, etc before. What's worse is my office's app shows option to switch to chinese version of the website for logging in. My language and time zone are set correctly though - English India and GMT +5:30.
3. The web browser I used before couldn't be found in the play store anymore. My launcher still shows the icon with a green arrow in left bottom of the icon to direct me to playstore to download it but playstore says item not found. The app name is simply 'browser'. I searched for it on desktop website too (without logging in), still couldn't find it. Guess it's a coincidence,
Also: Herehttps://www.getdroidtips.com/moto-z2-z2-play-z2-force-stock-rom/#Moto_Z2_Force_Android_80_Oreo_Firmware, the carrier global version says 'OCX' instead of 'OPX'. Any idead about that?
Sparkzz27 said:
Hi, sorry I was busy with work. I managed to use my phone that way. I didn't use the instructions in that post. Instead, I download flashallutilities (In how to return to stock post in xda for z2 force), then ran the batch file which did all the work. I noticed other problems too,
1. My Jio sim(4g LTE) does not show 'enhanced LTE mode' in options. Also when I call someone, it fails immediately saying 'call failed. try another method.' However, internet connection works from the sim. My other sim works fine for calls and data.
2. I'm seeing other keyboards in manage keyboards section. I don't recall seeing google pinyin input, zhuyin input, etc before. What's worse is my office's app shows option to switch to chinese version of the website for logging in. My language and time zone are set correctly though - English India and GMT +5:30.
3. The web browser I used before couldn't be found in the play store anymore. My launcher still shows the icon with a green arrow in left bottom of the icon to direct me to playstore to download it but playstore says item not found. The app name is simply 'browser'. I searched for it on desktop website too (without logging in), still couldn't find it. Guess it's a coincidence,
Also: Herehttps://www.getdroidtips.com/moto-z2-z2-play-z2-force-stock-rom/#Moto_Z2_Force_Android_80_Oreo_Firmware, the carrier global version says 'OCX' instead of 'OPX'. Any idead about that?
Click to expand...
Click to collapse
Your Z2 is a xt1789-06 correct? It's an international version, the flashall in the utilities zip from the return to stock thread is for US based phones, TMO and Sprint specifically. What was or wasn't flashed using that flashall I couldn't tell you, I don't have an international phone. That's why I linked to the post that deals with that version of the Z2 and has all the answers and links you need to sort your phone. Others in that thread might be better suited to help you along. This is the thread that deals with the xt1789-06.
As for calling and sim, might be related to how you flashed or simply an apn issue. You can go to network settings, mobile, access point names, and reset those to default. That should pull the apns from your sim so you'll have the correct apns.
As for keyboards and browsers, I don't know what is included in the international stock versions, but they are subject to change based on initial setup/default language and rom version. As for the OCX vs OPX, I'm not sure what the difference is. I know 'O' is for Oreo but for the rest I don't know. Maybe one is gsm one is cdma? I don't know. I do know that the thread I linked to will have more info and be able to help you better since it's for your version of the Z2. Sorry I can't help you more, but post any questions you have over there and they should be able to sort you out.
Hi all,
As you have probably seen Android 10 is beginning to roll out with firmware 53.1..A.2.2. Currently 2 available versions one is for Ireland with 3 branding and the second is for South Africa. I have flashed the 3IE one today. Seems very good. Everything working and snappy to navigate. Downside is a 3 splashscreen at boot.
I can also report latest magisk works for root and with magiskhide Google Pay is working.
If you want to install then this guide will show you how. https://www.xperiablog.net/2018/01/28/newflasher-guide-to-install-new-firmware-for-xperia-xz-premium-xz1-and-more/
How did you root in Android Q, i cant do it in android Q
lucaszhaoting said:
How did you root in Android Q, i cant do it in android Q
Click to expand...
Click to collapse
Just used latest Magisk and magisk manager.
Is someone already using Android 10?
Have you found some weird issues with it?
xXqepXx said:
Is someone already using Android 10?
Have you found some weird issues with it?
Click to expand...
Click to collapse
Yes!! Battery drains well quick! Apart from that no issues!!
This is the generic instructions I used to get root to work on my Sony Xperia 10 (Model I3123) - Build 53.1.A.2.2.
Download TWRP (twrp-3.3.1-3-kirin.img) on PC.
Download Magisk Manager 7.5.1 on phone. Run. Download the latest Magisk 20.4 (20400) through app.
Put phone into fastboot mode - Power off. Hold Volume Up while plugging USB into PC. Phone LED will be Blue.
via ADB command prompt on PC, run "fastboot boot twrp-3.3.1-3-kirin.img"
Phone should automatically reboot into TWRP Recovery. Select Read Only. Click Install. Install the Magisk app.
Once rebooted, you should have root.
Thanks for your post OP. I didn't know it was going to be so easy to get root on Android 10.
bluelemonzz said:
This is the generic instructions I used to get root to work on my Sony Xperia 10 (Model I3123) - Build 53.1.A.2.2.
Download TWRP (twrp-3.3.1-3-kirin.img) on PC.
Download Magisk Manager 7.5.1 on phone. Run. Download the latest Magisk 20.4 (20400) through app.
Put phone into fastboot mode - Power off. Hold Volume Up while plugging USB into PC. Phone LED will be Blue.
via ADB command prompt on PC, run "fastboot boot twrp-3.3.1-3-kirin.img"
Phone should automatically reboot into TWRP Recovery. Select Read Only. Click Install. Install the Magisk app.
Once rebooted, you should have root.
Thanks for your post OP. I didn't know it was going to be so easy to get root on Android 10.
Click to expand...
Click to collapse
Just did this in about 5 minutes, no problem! Thank you for the info!
bluelemonzz said:
This is the generic instructions I used to get root to work on my Sony Xperia 10 (Model I3123) - Build 53.1.A.2.2.
Download TWRP (twrp-3.3.1-3-kirin.img) on PC.
Download Magisk Manager 7.5.1 on phone. Run. Download the latest Magisk 20.4 (20400) through app.
Put phone into fastboot mode - Power off. Hold Volume Up while plugging USB into PC. Phone LED will be Blue.
via ADB command prompt on PC, run "fastboot boot twrp-3.3.1-3-kirin.img"
Phone should automatically reboot into TWRP Recovery. Select Read Only. Click Install. Install the Magisk app.
Once rebooted, you should have root.
Thanks for your post OP. I didn't know it was going to be so easy to get root on Android 10.
Click to expand...
Click to collapse
Worked a treat but the phone is not recognising my sd card! Any ideas? I think it may have something to do with twrp
Chronic2k13 said:
Worked a treat but the phone is not recognising my sd card! Any ideas? I think it may have something to do with twrp
Click to expand...
Click to collapse
I recall in the past, I lost a few SD cards during rooting or upgrading a rom. I don't know why it happened. Could you check another sd card? Or maybe try this SD card on another phone to pin point where the issue is. Was the SD card working prior to rooting? FYI My SD card works fine. Everything is working as it is on Android 9.0.
bluelemonzz said:
I recall in the past, I lost a few SD cards during rooting or upgrading a rom. I don't know why it happened. Could you check another sd card? Or maybe try this SD card on another phone to pin point where the issue is. Was the SD card working prior to rooting? FYI My SD card works fine. Everything is working as it is on Android 9.0.
Click to expand...
Click to collapse
I unrooted, flashed back stock rom and it works fine. I believe sd card encryption is broken on twrp
Did the update ends? I brought Xperia 10 secound hand just now and my device cannot find anything moore than Pie Everyone here get it?
MrCzAjNiK said:
Did the update ends? I brought Xperia 10 secound hand just now and my device cannot find anything moore than Pie Everyone here get it?
Click to expand...
Click to collapse
You can download it through Xperifirm and then flash it using Newflasher!!
Yep but i need to unlock bl before it.? Did custom software is smother or there is no adventages of inistalling it? I mean los or treble one aosp sw.
MrCzAjNiK said:
Yep but i need to unlock bl before it.? Did custom software is smother or there is no adventages of inistalling it? I mean los or treble one aosp sw.
Click to expand...
Click to collapse
You don't need to have your bootloader unlocked!!
Thanks ill try to install it today after work.
Just need to get a new high class USB-c for flashing.
"https://xperiafirmware.com/sony-xperia-10/"
that's all very easy......
MrCzAjNiK said:
Did the update ends? I brought Xperia 10 secound hand just now and my device cannot find anything moore than Pie Everyone here get it?
Click to expand...
Click to collapse
Hi, what variant do you have. If you have i4193 its HK and TW variant and they are late when it comes to update. But they already have android 10 update just couple of days ago buid number is 53.1.a.3.8
---------- Post added at 09:21 PM ---------- Previous post was at 09:18 PM ----------
Any new features or shared experience for new update android 10 buid 53.1.a.3.34?
New build release 53.1.A.3.57. Probably security patch. Anyone here installed the latest build?
nitrams said:
New build release 53.1.A.3.57. Probably security patch. Anyone here installed the latest build?
Click to expand...
Click to collapse
I installed it yesterday. Security patch August 1, all good.
bluelemonzz said:
This is the generic instructions I used to get root to work on my Sony Xperia 10 (Model I3123) - Build 53.1.A.2.2.
Download TWRP (twrp-3.3.1-3-kirin.img) on PC.
Download Magisk Manager 7.5.1 on phone. Run. Download the latest Magisk 20.4 (20400) through app.
Put phone into fastboot mode - Power off. Hold Volume Up while plugging USB into PC. Phone LED will be Blue.
via ADB command prompt on PC, run "fastboot boot twrp-3.3.1-3-kirin.img"
Phone should automatically reboot into TWRP Recovery. Select Read Only. Click Install. Install the Magisk app.
Once rebooted, you should have root.
Thanks for your post OP. I didn't know it was going to be so easy to get root on Android 10.
Click to expand...
Click to collapse
Hi there, thank you for this easy short guide. My xperia 10 runs ok with android 10 53.1.a.2.2 and twrp 3.4.0.0 and i can confirm sd card works too, but i have encryption problems. I ve set password in android but nothing is asked in recovery mode. Do you have same problem? any solution?
I'm trying to install Lineage OS on my phone and I have followed all the steps (plus many more they just assume you'll know) from this site, up to configuration because adb no longer discovers my phone.
.\adb devices
.\adb fastboot bootload
literally anything to do with adb doesn't work but it did an hour ago. Now I'm worse off because my phone will only upload to bootload and not to the actual homescreen so there's no going in and double checking if my USB debugging is on (it was before the reset) and I can't access my phone at all, nor can I get things configured. I've updated the drivers via web, deleted and retried the drivers, and restarted the computer. I don't know what I'm supposed to have on my computer that would better upload the drivers. I don't have a clue what any of this is supposed to mean, I was forced to do all of this **** because of the recent Adroid 12 update that I couldn't get rid of without just getting a different OS. Please please please make it dumb for me and tell me how I can get my phone back and download this OS.
Try fastboot commands in bootloader
yesca213 said:
Try fastboot commands in bootloader
Click to expand...
Click to collapse
Yes fastboot commands work but I need to copy this in the command prompt
.\adb sideload copy-partitions-20210323_1922.zip
The tutorial says it isn't an optional step. When I try doing this with fastboot, it tells me:
fastboot: usage: unknown command sideload
Try "fastboot reboot" or "fastboot reboot bootloader"
yesca213 said:
Try "fastboot reboot" or "fastboot reboot bootloader"
Click to expand...
Click to collapse
Thanks! I tried it with no change. adb can still not discover my phone and it doesn't start back up, only brings me to FastBoot mode screen.
If it's Windows your using it may be a driver issue.
yesca213 said:
If it's Windows your using it may be a driver issue.
Click to expand...
Click to collapse
Yes I'm on Windows 10. I have uninstalled and reinstalled the Android and Portable devices drivers with no luck. Do you know what I might be able to do to fix it from that end?
johnmtrowbridge said:
Yes I'm on Windows 10. I have uninstalled and reinstalled the Android and Portable devices drivers with no luck. Do you know what I might be able to do to fix it from that end?
Click to expand...
Click to collapse
hi, bro.
once you connected phone on fastboot mode, check device manager if any device is not recognized - try to manually install it from HERE.
if you still have any problems - contact me on telegram terry_222
heyhowyoudoin said:
hi, bro.
once you connected phone on fastboot mode, check device manager if any device is not recognized - try to manually install it from HERE.
if you still have any problems - contact me on telegram terry_222
Click to expand...
Click to collapse
So I checked in device manager and didn't see any exclaimation points anywhere which is what I assume you meant. Nothing out of the ordinary and Android looks fine. I'd like to message you on telegram and I guess I will in a few hours but it's blocked on my work wifi and I don't have a VPN and my hotspot it obviously bricked at the moment
johnmtrowbridge said:
So I checked in device manager and didn't see any exclaimation points anywhere which is what I assume you meant. Nothing out of the ordinary and Android looks fine. I'd like to message you on telegram and I guess I will in a few hours but it's blocked on my work wifi and I don't have a VPN and my hotspot it obviously bricked at the moment
Click to expand...
Click to collapse
just i'm sure what i can fix all that thing fast and want to help you
i have signal too
heyhowyoudoin said:
just i'm sure what i can fix all that thing fast and want to help you
i have signal too
Click to expand...
Click to collapse
Yeah I'm gonna just have to try in a few hours because the only way Signal works on my desktop is if I verify it on my phone lol. Again, the phone is completely stuck on FastBoot mode and anytime I restart it it takes me right back, which I think is probably because of the recovery mode I just installed.
bro, I just read what you wrote, if you had version 12 of android, then you already ruined everything and there is nothing left but to reinstall the firmware using MSM tool
heyhowyoudoin said:
bro, I just read what you wrote, if you had version 12 of android, then you already ruined everything and there is nothing left but to reinstall the firmware using MSM tool
Click to expand...
Click to collapse
I had the most recent update from last week. I didn't catch the name specifically, I assumed it was Android 12. I already did a factory reset on my phone last week trying to get rid of the update or at least revert back to the previous one but that didn't help and it was because my phone version is the wrong one for the revert package they had or something like that. So with that info, you're saying I have to reinstall everything all over again and try again? There's no way to get Lineage on this phone at all?
i
if you were on version 12, then you need to flash to version 11 using the MSM TOOL program, then upgrade to the latest 11.2.10.10, and only then open the bootloader, flash the recovery and then flash the firmware
heyhowyoudoin said:
i
if you were on version 12, then you need to flash to version 11 using the MSM TOOL program, then upgrade to the latest 11.2.10.10, and only then open the bootloader, flash the recovery and then flash the firmware
Click to expand...
Click to collapse
There wasn't a recovery version of 11 at the time that I could find, not for the 9 Pro. So what do I do now, do you know how I at least get my phone off of FastBoot mode to try this **** all over again?
johnmtrowbridge said:
I had the most recent update from last week. I didn't catch the name specifically, I assumed it was Android 12. I already did a factory reset on my phone last week trying to get rid of the update or at least revert back to the previous one but that didn't help and it was because my phone version is the wrong one for the revert package they had or something like that. So with that info, you're saying I have to reinstall everything all over again and try again? There's no way to get Lineage on this phone at all?
Click to expand...
Click to collapse
if you flashed the boot file through a fastboot being on the 12th version of android, you will never be able to do anything but very tricky manipulations that a small number of people own, so you have one path that I indicated above. and by the way, I do not advise you lineageos 11 version, better derpfest 12 version, 11 version is obsolete and you will understand it yourself
can you tell me which version your phone have? IN/CN/GLOBAL/INDIA
Index of /list/Unbrick_Tools/OnePlus_9_Pro
or download version for your phone from link above
heyhowyoudoin said:
if you flashed the boot file through a fastboot being on the 12th version of android, you will never be able to do anything but very tricky manipulations that a small number of people own, so you have one path that I indicated above. and by the way, I do not advise you lineageos 11 version, better derpfest 12 version, 11 version is obsolete and you will understand it yourself
Click to expand...
Click to collapse
Ok dude what I hear you saying is that 1.) Android 12 can't have Lineage OS installed because the version doesn't jive well with the OS, 2.) the instructions will only help on version 11 that I have to get first and 3.) I don't want Lineage anyways because derpfest 12 is better. Is that what you're saying?
heyhowyoudoin said:
can you tell me which version your phone have? IN/CN/GLOBAL/INDIA
Click to expand...
Click to collapse
NA I'm in America
johnmtrowbridge said:
Ok dude what I hear you saying is that 1.) Android 12 can't have Lineage OS installed because the version doesn't jive well with the OS, 2.) the instructions will only help on version 11 that I have to get first and 3.) I don't want Lineage anyways because derpfest 12 is better. Is that what you're saying?
NA I'm in America
Click to expand...
Click to collapse
yes, that's what I mean. is your phone linked to t mobile?
at the moment it is not possible to install any custom OS from version 12 of android, not only lineageos