Related
Q&A for [EXP][DEV] Lollipop for Xperia Z
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [EXP][DEV] Lollipop for Xperia Z. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Good start
Had no problems installing via fastboot. Very nice and smooth, but needs some google play sevice files, so to test properly. Unable to call out - APN settings look okay, but signal icon on status bar has exclamation mark (?). SOme sort of recovery would be invaluable.
My Q&A: not definitive, but hopefully this will ease question duplication
I've decided to update this post to be an informal Q&A-link-list in the desperate hope that people will come across it before asking the same questions again and again. Look here to see if your question has already been answered. If you think something needs to be added to this post, then post it in thread.
INFO CURRENT AS OF ~1AM UTC 13 Nov 2014.
There are two versions of the Xperia Z Lollipop rom: one by thomas, and one by pabx. Installation instructions differ in places between the two, as do the prerequisites. I will list note when they are different.
How do I install?
Prerequisites:
An unlocked bootloader. If not unlocked, see 'Bootloader unlocking' below
The fastboot and adb command line tools. For more on them, see 'Adb and Fastboot' below
Additional prerequisites for thomas's version if you want gapps or SuperSU:
A kernel including a recovery: I suggest HodorKernel
The SuperSU update package
A Gapps package (such as these ones suggested a while back by @_infected). If you find these gapps don't work for you, but find others that do, then post in the thread so this can be updated.
If you have the prerequisites, then you can continue. Note that installation will wipe your phone completely, including the internal SD.
PABX's version: downloads and installation instructions can be found here.
Thomas's version: see this post.
Regarding Root
Pabx's build doesn't support root. If you need root, use Thomas's build.
Regarding recovery
Thomas's build doesn't include a recovery. Pabx's includes CWM recovery.
If you need a recovery on thomas's, you'll need to temporarily flash a boot image which includes a recovery. That would be the HodorKernel I suggested earlier.
To temporarily add a recovery to Thomas's build, take the following steps:
Enter fastboot by unplugging the USB, powering the device off, and holding the up volume button when plugging in a USB cable connected to your PC. The light on your phone will turn red, then blue. When it is blue, your phone is in fastboot mode.
On your PC, extract the HodorKernel zip file, and locate the boot.img
Flash the boot.img using the following command: fastboot flash boot boot.img
Unplug the USB cable
Press the power button
When the indicator light on your phone turns on, press the volume-down button repeatedly. You will eventually enter recovery. For some reason, you may need to touch the screen (rather than the power button) to actually turn the screen on once the recovery has loaded
Do what you need to do with the recovery (e.g. flash, etc)
Power off the device (I believe the option is in the 'reboot' menu)
Go back into fastboot (i.e. hold up volume, plug in, etc)
Flash the original boot.img from thomas's rom
Unplug USB
Boot
Bootloader unlocking
Unlocking your bootloader allows you to install unofficial ROMs on your Xperia Z. See here for how to unlock. Read the warnings.
this adb tutorial and this guide to fastboot. You can download these tools for Mac here and Windows here. If you're having problems with Windows, particularly Windows 8, look here.
If the links don't work, go find links that do and post them here. I can then update these links.
This isn't the fastboot or adb Q&A thread. If you don't understand how to use fastboot and adb, this isn't the place to ask. XDA is scattered with more guides than I can point a pointy thing at for fastboot and adb.
Post-original post:
EDIT: Don't use the GApps I've mentioned. They kind of work, but are pretty flakey for the XZ.
EDIT 2: PABX has posted a new build, but more importantly also some GAPPS. (http://www.blinkenlights.ch/ccms/android/yuga-l.html)
However, the GAPPS are a .tgz which means (I think) they can't be flashed using recovery. Thus, you'll more or less need to follow the procedure in this post.
NOTE: you only need to flash them using the procedure below if you are not using PABX's build. If you are, then you just need to follow the installation instructions on his page.
An alternative set of gapps linked by _infected is https://www.androidfilehost.com/?w=files&flid=20902
(_infected's post is http://forum.xda-developers.com/showpost.php?p=56623436&postcount=314)
Original post:
I've used the GApps from here: http://forum.xda-developers.com/google-nexus-5/orig-development/illusionrom-lollipop-lrx21m-t2929192
Because there is no recovery (that I know of) you have to manually copy them on using ADB, but once they are on you can create an account, access the play store, and thus install the other Google apps.
(I have barely tested them, though)
To install thees Gapps, I did the following (in brackets is description, don't enter it. Number is sequence of events, don't enter it.
1. adb shell (open a shell)
2. su (become root user)
3. mount -o rw,remount /system (make the /system file system writeable)
4. mkdir /tmp/gapps (make a directory to put the gapps in temporarily without losing the file system privileges on them)
5. chmod 777 /tmp/gapps (make the /tmp/gapps folder writeable to all)
6. exit (leave su)
7. exit (leave adb shell)
8. Unzip the file downloaded from the link above
9. adb push /system /tmp/gapps (push the gapps /system folder to the temp directory we created)
10. adb shell (back to the shell on the phone)
11. su (root again)
12. chown -R root.root /tmp/gapps (change ownership of all the gapps file to root)
13. cp -r /tmp/gapps/* /system/. (copy the gapps files into the /system partition file system)
14. exit (leave su)
15. exit (leave adb shell)
16. adb reboot (reboot device)
17. ???
18. Profit!!!
I'm not certain all these steps are necessary, and I'm writing them from memory not as I do them but I am pretty sure they are correct.
---------- Post added at 05:52 AM ---------- Previous post was at 05:26 AM ----------
By the way, GPS seems to work fine. Getting a good lock (4m accuracy) outdoors.
cant install gapps
i cant boot into my recovery to install gapps
is the adb way supposed to work in fastboot mode? since it says device not found
please help me get my gapps installed
Thanks in advance
xixhxix said:
i cant boot into my recovery to install gapps
is the adb way supposed to work in fastboot mode? since it says device not found
please help me get my gapps installed
Thanks in advance
Click to expand...
Click to collapse
EDIT: look at Post 3 (http://forum.xda-developers.com/showpost.php?p=56536436&postcount=3) for a link to PABX's most recent gapps and a (rough) procedure to install them. If you are using Thomas's builds, read on.
If you're trying to flash a zip-based set of GAPPS, then follow the instructions below *but using your own GAPPS package, not the one I've linked). If you *want* to flash a zip-based set of GAPPS but don't have them, then you can grab them from this post by _infected: http://forum.xda-developers.com/showpost.php?p=56623436&postcount=314.
Original post:
Hi,
The ADB way you do in normal mode (i.e. when the phone is running), not in fastboot mode, but there is a better way (which I will describe below).
I am now using these GAPPS and they seem to be working well.
http://forum.xda-developers.com/goo.../gapps-google-apps-flashable-package-t2930260
The better way to install the GAPPS (compared to my ADB method above)
1. Install the rom (using fastboot) and start it up once.
2. Shut down and go back into fastboot mode
3. Download HodorKernel (http://forum.xda-developers.com/xperia-z/orig-development/kernel-hodorkernel-t2865648)
4. Extract the HodorKernel ZIP, and flash the boot.img (fastboot flash boot boot.img)
5. Reboot and go into recovery (pressing down on the volume while booting)
6. Sideload the Gapps linked above
7. Power off (in TWRP, 'reboot'/'power off')
8. Go back into fastboot mode
9. Reflash the lollipop boot.img (fastboot flash boot boot.img)
10. Reboot
12. Do a happy dance
Note: other kernels may well work; I just used Hodor because I had it lying around.
Note 2: #9 is not an optional step. You *must* reflash the original boot.img or your rom will not work.
how did you guys managed to install gapps?
Pablosch23 said:
how did you guys managed to install gapps?
Click to expand...
Click to collapse
easy pizzy
download doom kernel
fastboot via adb
boot recovery
flash zip
go to advance
turn off phone
fast boot 5.0 boot
done
No
chauhanjayc said:
hi all
its been almost 12 hrs last night near 10:00 PM i had CM12 installed and here are my results .
00000000 LAGS(GOD FATHER OF PROJECT BUTTER)
1.5 Free RAM all the time :laughrunning all the gapps like gmail, map, location, google now, hangout, sync, and other...)
no huge battery drops(testing on going)
crystal clear sound in calls
NOOOOOOOOOOOOO HEATINGGGG:victory:
super fast installation of any apps
and much much much moreeeeeeeeee:victory:
check this out
Click to expand...
Click to collapse
How did u fix calling bug bro
Nd is audio bug fixed
iKillCypher said:
@pabx and @thomas1991_12
what blobs are you guys using cause sony seems to have their own blobs for AOSP (strange)
http://forum.xda-developers.com/showpost.php?p=56540160&postcount=25
Click to expand...
Click to collapse
I'm using the 283 blobs: https://github.com/adrian-bl-yuga/yuga-blobs-a806
vpn client on android L
Hey there, I live in a country where most of the websites are filtered by the government and it seems like I cant get any of the vpn clients apps to be working on this Android L build such as the "hotspot shield" or "psiphon", I hardly logged in to my google account and cant get my contacts to be synced. Any supposed solutions?
so no one is going to help me!!????
Thanks
I followed your guide and it worked perfectly for me. Though I used a different boot.img with recovery.
I guess older boot.img with custom recoveries should all work then.A BIG THANKS
---------- Post added at 02:51 PM ---------- Previous post was at 02:46 PM ----------
xixhxix said:
so no one is going to help me!!????
Click to expand...
Click to collapse
Great contributors are there to help in every step of the way.Big ups to pabx,R:goodejeev and the others
xixhxix said:
so no one is going to help me!!????
Click to expand...
Click to collapse
What do you want, magic? Right now the device can't transmit mobile data: I am not sure that VPN clients not working is going to stack up as top priority.
First, you need to be more clear about what you tried. What specific clients did you try? Did you try Cyberghost? Did you try ProXPN? Did you try using a generic OpenVPN client as well as VPN-specific apps?
Re: Google contact syncing: it isn't clear whether you're saying that it isn't syncing because the VPN isn't working, or it isn't syncing at all. Be specific.
If you want a fully functional phone right now, don't use Lollipop builds. If you want to use Lollipop, then accept that some things will be broken and either work out how to fix them and tell others, or report the issue and live with the fact that it takes time for people to test and respond.
thanks anyway
vo4LG said:
What do you want, magic? Right now the device can't transmit mobile data: I am not sure that VPN clients not working is going to stack up as top priority.
First, you need to be more clear about what you tried. What specific clients did you try? Did you try Cyberghost? Did you try ProXPN? Did you try using a generic OpenVPN client as well as VPN-specific apps?
Re: Google contact syncing: it isn't clear whether you're saying that it isn't syncing because the VPN isn't working, or it isn't syncing at all. Be specific.
If you want a fully functional phone right now, don't use Lollipop builds. If you want to use Lollipop, then accept that some things will be broken and either work out how to fix them and tell others, or report the issue and live with the fact that it takes time for people to test and respond.
Click to expand...
Click to collapse
I dont think I asked for such an answer, thanks for your attitude but any way I'll answer your questions so that maybe somebody could help me
First you could say I've already tried every possible way of a proxy
second, according to google contacts syncing its because that server is already blocked here so you cant sync those except if you got a working vpn (although I found a way to get them, but not with the normal sync way)
actually the main purpose of my post was reporting that this vpn stuff isn't working so that they even try fixing it
Is there a flashable zip or something for this?
Or something to flash this without wiping internal sdcard?
Help!!
I have already install this rom and working for one day .
it is awesome .
but today battery less then 2% and i plug the power quickly and the red led light for 1hour and cannot power on or even reboot the devices when the power didn't plug .
i try to use adb/fastboot to reboot the devices but nothing happen the red light still light and no display
how can i fix it?
.zip compile?
Why there aren't a .zip file (easier to flash for me) of this rom?
Sorry for my bad english.
How can I install Gapps?
How can I flash Gapps? I can't reboot in recovery.
gapps
Pleaseeeeee
Anyone give me a link of working gapps.
leonso26 said:
I have already install this rom and working for one day .
it is awesome .
but today battery less then 2% and i plug the power quickly and the red led light for 1hour and cannot power on or even reboot the devices when the power didn't plug .
i try to use adb/fastboot to reboot the devices but nothing happen the red light still light and no display
how can i fix it?
Click to expand...
Click to collapse
__________________
and i finally use all the battery until the red led light goes on . and plug and power and let it to charge and it working now.
(other thread here)
It seems that a Magisk module that I have recent installed (no idea which one) is preventing my phone to boot correctly. I know that because reflashing the latest OTA update removes Magisk and then it works perfectly. As soon as I flash Magisk, it doesn't boot anymore.
Even after flashing SuperSU, Magisk Manager doesn't let me see/remove installed modules.
Is there a way to do that?
zdimension said:
(other thread here)
It seems that a Magisk module that I have recent installed (no idea which one) is preventing my phone to boot correctly. I know that because reflashing the latest OTA update removes Magisk and then it works perfectly. As soon as I flash Magisk, it doesn't boot anymore.
Even after flashing SuperSU, Magisk Manager doesn't let me see/remove installed modules.
Is there a way to do that?
Click to expand...
Click to collapse
Use mount-magisk.zip found in collection of modules thread and delete the folder via twrp in /magisk
@duxishere Thanks so much!
I searched for "Magisk module offline uninstall" but did find anything. This was exactly what I needed! The culprit was App Systemizer. I've had it installed for some time and it didn't cause any problems. I uninstalled it, and it worked! Flashing it again restored the boot problem.
zdimension said:
@duxishere Thanks so much!
I searched for "Magisk module offline uninstall" but did find anything. This was exactly what I needed! The culprit was App Systemizer. I've had it installed for some time and it didn't cause any problems. I uninstalled it, and it worked! Flashing it again restored the boot problem.
Click to expand...
Click to collapse
How did you uninstalled the troubled module?
I'm having the same problem with a module but I don't even have a /magisk folder.
gonsa said:
How did you uninstalled the troubled module?
I'm having the same problem with a module but I don't even have a /magisk folder.
Click to expand...
Click to collapse
Start reading the thread from the beginning and you'll find it.
gonsa said:
How did you uninstalled the troubled module?
I'm having the same problem with a module but I don't even have a /magisk folder.
Click to expand...
Click to collapse
Install "Uninstaller Mod Magisk" from TWRP. Then go in the TWRP terminal and type uninmod_magisk and follow the instructions.
please post the link to thread unistaller magisk module, to other users follow the solution!
edit:
there is https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242
nodio said:
please post the link to thread unistaller magisk module, to other users follow the solution!
edit:
there is https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242
Click to expand...
Click to collapse
Not working for me!
I will uninstall "Audio Compatibility Patch" V1.0 from zackptg5 & ahrion
In Magisk Manger Status is always " Module will be updated at the next start"
If i use the "TWRP-Uninstaller" the Modul is not in List!
dewois said:
Not working for me!
I will uninstall "Audio Compatibility Pach" V1.0 from zackptg5 & ahrion
In Magisk Manger Status is always " Module will be updated at the next start"
If i use the "TWRP-Uninstaller" the Modul is not in List!
Click to expand...
Click to collapse
https://www.didgeridoohan.com/magisk/Magisk#hn_Module_will_be_updated_at_next_reboot
Didgeridoohan said:
https://www.didgeridoohan.com/magisk/Magisk#hn_Module_will_be_updated_at_next_reboot
Click to expand...
Click to collapse
".... Go the module folder under /sbin/.core/img ..."
I dont have this folder in /sbin!
tobi14 said:
".... Go the module folder under /sbin/.core/img ..."
I dont have this folder in /sbin!
Click to expand...
Click to collapse
If you have a current version of Magisk installed, yes you do. Enable viewing hidden files and folders in your file explorer. The dot at the beginning of the folder name means it's hidden...
zdimension said:
(other thread here)
It seems that a Magisk module that I have recent installed (no idea which one) is preventing my phone to boot correctly. I know that because reflashing the latest OTA update removes Magisk and then it works perfectly. As soon as I flash Magisk, it doesn't boot anymore.
Even after flashing SuperSU, Magisk Manager doesn't let me see/remove installed modules.
Is there a way to do that?
Click to expand...
Click to collapse
If you can launch TWRP then :
Check magisk.img exist
1. Go to "advanced" and then click on "File Explorer".
2. Check there is "magisk.img" file under "/data"
Backup magisk.img
1. Go to "advanced" and then click on "terminal command".
2. type following command
Code:
cp /data/magisk.img /data/magisk.img.bk
Mount magisk.img
1. Make a temp folder
Code:
mkdir /mktmp
2. Mount magisk.img to /mktmp
Code:
mount -o loop /data/magisk.img /mktmp
3. Navigate to mktmp and remove your module
Code:
cd /mktmp
rm -rf /mktmp/xxxx
Unmount magisk.img and reboot to check if it's work
1. Unmount magisk.img
Code:
umont /mktmp
2. Leave terminal and reboot the phone
3. Enjoy!
mklee11224 said:
If you can launch TWRP then :
Check magisk.img exist
1. Go to "advanced" and then click on "File Explorer".
2. Check there is "magisk.img" file under "/data"
Backup magisk.img
1. Go to "advanced" and then click on "terminal command".
2. type following command
Code:
cp /data/magisk.img /data/magisk.img.bk
Mount magisk.img
1. Make a temp folder
Code:
mkdir /mktmp
2. Mount magisk.img to /mktmp
Code:
mount -o loop /data/magisk.img /mktmp
3. Navigate to mktmp and remove your module
Code:
cd /mktmp
rm -rf /mktmp/xxxx
Unmount magisk.img and reboot to check if it's work
1. Unmount magisk.img
Code:
umont /mktmp
2. Leave terminal and reboot the phone
3. Enjoy!
Click to expand...
Click to collapse
Thanks mate ! it worked like a charm !
just use "ls" command on step 3 after changing directory to mktmp , to show installed modules.:silly:
My Phone Specification : Moto X Play ------ 7.1.1 Stock Firmware -------- Squid kernel --------- rooted using Magisk ------ systemless xposed module "xposed_25" installed using magisk module(Uninstalled by this method !) .:victory:
Tanks a lot!
Crossbreeder lite made my phone unusable. Working fine again!
magisk.img not found in /data
This works like charm, if you can't find the magisk.img in `/data` check `/data/adb` ... I hope this work .
Didgeridoohan said:
https://www.didgeridoohan.com/magisk/Magisk#hn_Module_will_be_updated_at_next_reboot
Click to expand...
Click to collapse
Own domain huh? Business growing? Hehehe I only came for the uninstall zip, hey quick question, I'm on a micro sd-less phone (big news), still a flashaholic, kinda, but my phone so happens to require a data format every time for gsi's, where would you recommend keeping the "things to keep on your device" (Magisk related) so i don't have to carry an otg and drive everywhere i go? Thank you sir, you almost get more thanks than posts! Talk about reputation!
culiacanazo said:
Own domain huh?
Click to expand...
Click to collapse
I keep a few of them around. It was nice to finally find a good use for that one...
but my phone so happens to require a data format every time for gsi's, where would you recommend keeping the "things to keep on your device" (Magisk related) so i don't have to carry an otg and drive everywhere i go?
Click to expand...
Click to collapse
Do you have to completely wipe the device? Or can you keep internal storage intact? If not, it sounds like you're out of luck.
Nice thread hijack, by the way... :laugh:
Didgeridoohan said:
Do you have to completely wipe the device?
Click to expand...
Click to collapse
Well i do a factory reset, flash system img and reboot, let it loop because it will, and then do a data format before it will boot, so system, caches, and data go... (Huawei, see)
Didgeridoohan said:
Nice thread hijack, by the way... :laugh:
Click to expand...
Click to collapse
I kinda stayed on topic didn't i? :crying:
You linked to your help guide which i read the beginning of that by the way has nothing to do with the help you offered to the op and reminded me of my struggles with a totally different device and problem!!
It's like how I'm related to my grandma's cousin's wife's sister's doctor's neighbor's son's friend, ain't it?
Sent from my Huawei Mate 10 Pro using XDA Labs
Would be cool if someone could share the adb solution. In the FAQ is just written "email me for this" wtf?!? It is ****ing anoying to reflash the whole system everytime a module isnt working (yeah thats what you need to do if your device doesnt have twrp, and a lot of a/b devices dont have twrp). Also you need to delete all user datas because you flashed the system new and the new system doesnt know the encryption key for the user datas. There need to be a better solution than using twrp or email the dev for adb solution.
The easiest way would be to make it possible that magisk manager can manage (remove/deactivate) the modules while there is no patched boot.img installed. This would solve all problems related to a/b devices without twrp and magisk modules (not booting or anything else) just flash stock boot.img remove the problematic module flash patched boot.img and done. This is not possible because the module section in magisk manager is hidden when there is no patched boot.img installed.
Second thing i noticed, magisk manager doesnt reset the active modules when you wipe the app data. This should be a MUST. Would also solve the problem of not booting modules without wiping the whole system on a/b devices without twrp.
Apply .disable_magisk
saturday_night said:
Would be cool if someone could share the adb solution. In the FAQ is just written "email me for this" wtf?!? It is ****ing anoying to reflash the whole system everytime a module isnt working (yeah thats what you need to do if your device doesnt have twrp, and a lot of a/b devices dont have twrp). Also you need to delete all user datas because you flashed the system new and the new system doesnt know the encryption key for the user datas. There need to be a better solution than using twrp or email the dev for adb solution.
The easiest way would be to make it possible that magisk manager can manage (remove/deactivate) the modules while there is no patched boot.img installed. This would solve all problems related to a/b devices without twrp and magisk modules (not booting or anything else) just flash stock boot.img remove the problematic module flash patched boot.img and done. This is not possible because the module section in magisk manager is hidden when there is no patched boot.img installed.
Second thing i noticed, magisk manager doesnt reset the active modules when you wipe the app data. This should be a MUST. Would also solve the problem of not booting modules without wiping the whole system on a/b devices without twrp.
Click to expand...
Click to collapse
Hi!. I have this user of XDA Dev. hanging out for a time... well the fact is I'm new. My problem (not the only one) maybe merge a kind of solution to this. And this could be putting the ".disable_magisk" blank file inside the cache partition as an ADB Sideload update.
Next to this. I've found that to do that it's not as simply as it seems to be cause I'm on a Samsung Galaxy S7 Nougat 7.0 Version. And all the examples with update-binary file I have, are from downgrade versions...
I'm stuck in a bootloop due to the Magisk Xposed SDK 24 module. I think this module & encription is not good (as I've read on the Xpose module thread).
So, here I'm asking how to make an script to run directly on the Stock recovery using ADB Sideload, which will put the blank ".disable_magisk" file inside the /cache partition. I need just this, and I think this could help some people who are stuck on this issue.
Now, I have this Thread. But really I need the advice of an expert telling me what to do in order to achieve this. As I think this is an easy labor, but you have to know how to do it... If someone is able to clarify please, I will appreciate so much.
Thanks!
---------- Post added at 05:51 PM ---------- Previous post was at 05:41 PM ----------
neromanello said:
Hi!. I have this user of XDA Dev. hanging out for a time... well the fact is I'm new. My problem (not the only one) maybe merge a kind of solution to this. And this could be putting the ".disable_magisk" blank file inside the cache partition as an ADB Sideload update.
Next to this. I've found that to do that it's not as simply as it seems to be cause I'm on a Samsung Galaxy S7 Nougat 7.0 Version. And all the examples with update-binary file I have, are from downgrade versions...
I'm stuck in a bootloop due to the Magisk Xposed SDK 24 module. I think this module & encription is not good (as I've read on the Xpose module thread).
So, here I'm asking how to make an script to run directly on the Stock recovery using ADB Sideload, which will put the blank ".disable_magisk" file inside the /cache partition. I need just this, and I think this could help some people who are stuck on this issue.
Now, I have this Thread. But really I need the advice of an expert telling me what to do in order to achieve this. As I think this is an easy labor, but you have to know how to do it... If someone is able to clarify please, I will appreciate so much.
Thanks!
Click to expand...
Click to collapse
I need to know how to locate the mount point of my /cache partition at the stock recovery ADB Sideload. Then, to mount it, transfer the blank file to it, and then unmount /cache. I think it's an easy labor. So here my incomplete updater-script:
ui_print("Trying to make an script with ADB Sideload..."); CRLF
ui_print("Creating file to disable Magisk Modules..."); CRLF
I NEED THE MOUNT POINT HERE CRLF
ifelse package_extract_file(".disable_magisk", "/cache/.disable_magisk") == "t", ui_print("OK!"), ui_print("Failed!"); CRLF
UNMOUNT COMMAND HERE. CRLF
--last blank line--
So, I need to complete that, BUT things gets difficult when I need the update-binary for my Nougat 7.0 version, and to sign the whole .zip file in order my stock recovery recognizes it. I think this last thing could be made by this Thread. But really I don't know. Please help.
Thanks!.
Good evening from Spain.
I tried to flash Magisk onto my SM-J530F (Samsung Galaxy J5 2017) but not successfully.
Here's the log:
Updating partition details...
...done
Full SELinux support is present.
MTP Enabled.
Installing zip file '/sdcard/MAGISK/Magisk-v16.0.zip'
Checking for Digest file...
Skipping Digest check: no Digest file found
********************
* Magisk v16.0 Installer
********************
- Mounting /system, /vendor
- Found boot/ramdisk image: /dev/block/mmcblk0p10
- Device platform: arm
- Constructing environment
- Unpacking boot image
- Checking ramdisk status
! Boot image patched by other programs.
! Please restore stock boot image
- Unmounting partitions
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/MAGISK/Magisk-v16.0.zip'
Updating partition details...
Failed to mount '/system' (Device or resource busy)
...done
Consider that I did the following:
- Flashed stock rom (J530FXXU2ARB3_J530FPHE2ARB3_PHE.zip content)
- Flashed "CF-Auto-Root-j5y17lte-j5y17ltexx-smj530f.tar" in Download mode via Odin, to root and install SuperSU, since it's needed
for flashing TWRP to avoid any bootloop.
- Flashed TWRP.
- Since I already have TWRP, I tried to uninstall SuperSU from the very app, in Options > Full unroot but gave "Uninstallation error", so then I tried to uninstall SuperSU by flashing "UPDATE-unSU.zip" on TWRP.
- Once that is done, I tried to flash "Magisk-v16.0.zip" and it throwed the log I've above mentioned.
- Since it says: "! Boot image patched by other programs.
! Please restore stock boot image", I rebooted it onto Download Mode, and flashed ONLY the BL (bootloader/boot) slot. Came back to TWRP, I flashed again "Magisk-v16.0.zip" but still have the same problem.
Hope there's any solution to install Magisk onto my SM-J530F. Thank you.
Your issue is that the boot image still is patched by SuperSU. Until you restore the stock boot image you won't be able to install Magisk.
https://www.didgeridoohan.com/magisk/Magisk#hn_Boot_image_patched_by_other_programs
Edit: I don't do Samsung, but from what I remember, you might need to flash AP (or something like that).
Didgeridoohan said:
Your issue is that the boot image still is patched by SuperSU. Until you restore the stock boot image you won't be able to install Magisk.
https://www.didgeridoohan.com/magisk/Magisk#hn_Boot_image_patched_by_other_programs
Edit: I don't do Samsung, but from what I remember, you might need to flash AP (or something like that).
Click to expand...
Click to collapse
Well, something changed!!!
The problem related with the boot image is solved but I still have the " Failed to mount '/system' "
Updating partition details...
...done
Full SELinux support is present.
MTP Enabled.
Installing zip file '/sdcard/MAGISK/Magisk-v16.0.zip'
Checking for Digest file...
Skipping Digest check: no Digest file found
********************
* Magisk v16.0 Installer
********************
- Mounting /system, /vendor
- Found boot/ramdisk image: /dev/block/mmcblk0p10
- Device platform: arm
- Constructing environment
- Unpacking boot image
- Checking ramdisk status
- Stock boot image detected
- Backing up stock boot image
- Patching ramdisk
- Repacking boot image
- Flashing new boot image
- Unmounting partitions
- Done
Updating partition details...
Failed to mount '/system' (Device or resource busy)
...done
Thank you very much.
EDIT: Despite this problem: "Failed to mount '/system' (Device or resource busy)", your solution was correct! Now I have Magisk correctly installed.
Thank you
Nice to hear it worked. Just for the record, the "Failed to mount /system" message is a TWRP thingy. The Magisk installation is done at the "-Done" line.
Hi, I have the same problem of error 1 while trying to install Magisk from TWRP.
I looked everywere and they say that it is related to a boot image that have to be reinstalled. I did that and no luck, I tryed with boot.img, no working, I even restored ALL the ROM Stock from Samsung ( AP, BL, CP and CSC) and it is not working. I dont know what to do anyware...
Regeet the time was easy to root Samsung with CF autoRoot,
I tried that and ask me to restore all thephone, so still no root??
Some can help please??
Thx
saoudien07 said:
Hi, I have the same problem of error 1 while trying to install Magisk from TWRP.
I looked everywere and they say that it is related to a boot image that have to be reinstalled. I did that and no luck, I tryed with boot.img, no working, I even restored ALL the ROM Stock from Samsung ( AP, BL, CP and CSC) and it is not working. I dont know what to do anyware...
Regeet the time was easy to root Samsung with CF autoRoot,
I tried that and ask me to restore all thephone, so still no root??
Some can help please??
Thx
Click to expand...
Click to collapse
Provide a recovery log or it's going to be impossible to say what the issue is...
Didgeridoohan said:
Provide a recovery log or it's going to be impossible to say what the issue is...
Click to expand...
Click to collapse
Thx for the reply, I am trying to open the content and upload the report here, but no luck. how can I open the log??? can not get a program to do so .......
saoudien07 said:
Thx for the reply, I am trying to open the content and upload the report here, but no luck. how can I open the log??? can not get a program to do so .......
Click to expand...
Click to collapse
The log is just a text file. Did you check the link I posted? In TWRP: Advanced - Copy log, and then post the resulting file.
Didgeridoohan said:
The log is just a text file. Did you check the link I posted? In TWRP: Advanced - Copy log, and then post the resulting file.
Click to expand...
Click to collapse
I got a file "recovery.log" thats why I can not open it, maybe change the extention to "txt" ???
saoudien07 said:
I got a file "recovery.log" thats why I can not open it, maybe change the extention to "txt" ???
Click to expand...
Click to collapse
That would work, but you should be able to open it directly with pretty much any text editor as well. If you're going to post the log text directly, please at least use HIDE tags...
So here what I just did:
I wanted to do a last try to get that error 1 msg and get the repport directly to publicate it here...
So I decide to go to a clean basis. So,
1- Install all the stock ROM with odin. I choose the Home_CSC
Was another just CSC without Home, dont know exactly which one I had to choose, I choose Home_CSC.
2- Turn the fone off
3- Turn it back to download mode
4- Install the TWRP recovery, and I did not reboot.
5- Turn off the fone.
6- Turn on to recovery mode.
7- Format the data (yes)
8- Reboot to Recovery mode.
9- Install Magisk!
AT MY BIG SURPRISE I DID NOT GET ANY ERROR MSG!!! The installation finished without error!
So I continued...
10- install No verity
11- install SuperUS 2.82
13- Reboot the phone.
I was thinking that the root was ok, now I have a new pb. When I tryed to verify with Root Checker, it says no root. When I entered the app, it said BINARY OCCUPIED.
So any suggestion?
saoudien07 said:
9- Install Magisk!
...
11- install SuperUS 2.82
Click to expand...
Click to collapse
Say what...? You've misunderstood something, somewhere. Use Magisk OR SuperSU. Magisk is it's own root solution...
Are you by any chance using some old and outdates guides? Previously you could use SuperSU with Magisk, but that has not been the case since v13.0, well over a year ago, and MagiskSU has been around since v11.0, introduced a year and a half ago.
Didgeridoohan said:
Say what...? You've misunderstood something, somewhere. Use Magisk OR SuperSU. Magisk is it's own root solution...
Are you by any chance using some old and outdates guides? Previously you could use SuperSU with Magisk, but that has not been the case since v13.0, well over a year ago, and MagiskSU has been around since v11.0, introduced a year and a half ago.
Click to expand...
Click to collapse
You guessed right, I am not using a so old tuto, it says it is for oreo...
So I have to use or Magisk or SuperSU,right?
The thing is that i thought SuperSu is to install the SuperSU app, I did notknow that it root also the phone...
I am kind of newby to Android world, u figured it already...
So what are insterest of using Magisk or no-verity??
---------- Post added at 08:22 PM ---------- Previous post was at 08:17 PM ----------
Didgeridoohan said:
Say what...? You've misunderstood something, somewhere. Use Magisk OR SuperSU. Magisk is it's own root solution...
Are you by any chance using some old and outdates guides? Previously you could use SuperSU with Magisk, but that has not been the case since v13.0, well over a year ago, and MagiskSU has been around since v11.0, introduced a year and a half ago.
Click to expand...
Click to collapse
Can I put a link to the tuto here??
For you guys to have a lock at it?
saoudien07 said:
You guessed right, I am not using a so old tuto, it says it is for oreo...
So I have to use or Magisk or SuperSU,right?
The thing is that i thought SuperSu is to install the SuperSU app, I did notknow that it root also the phone...
I am kind of newby to Android world, u figured it already...
So what are insterest of using Magisk or no-verity??
---------- Post added at 08:22 PM ---------- Previous post was at 08:17 PM ----------
Can I put a link to the tuto here??
For you guys to have a lock at it?
Click to expand...
Click to collapse
The root management app for Magisk/MagiskSU is the Magisk Manager. SuperSU and it's accompanying app is a whole different root solution (that has been sold by @Chainfire and seemingly abandoned by it's new owners).
Magisk usually takes care of dm-verity itself, so there shouldn't be any need for an extra no-verity zip. Sometimes it is needed, but I would skip it until you've tried using Magisk only. If you don't know, dm-verity is used by Android to determine if your device has been tampered with. If you wan't to root your device (tampering), you usually have to disable dm-verity or the device won't boot at all.
If you want root with Magisk, do your list again, but skip step 10 and 11. If it doesn't boot after that, go back to TWRP and flash the no-verity zip.
Didgeridoohan said:
The root management app for Magisk/MagiskSU is the Magisk Manager. SuperSU and it's accompanying app is a whole different root solution (that has been sold by @Chainfire and seemingly abandoned by it's new owners).
Magisk usually takes care of dm-verity itself, so there shouldn't be any need for an extra no-verity zip. Sometimes it is needed, but I would skip it until you've tried using Magisk only. If you don't know, dm-verity is used by Android to determine if your device has been tampered with. If you wan't to root your device (tampering), you usually have to disable dm-verity or the device won't boot at all.
If you want root with Magisk, do your list again, but skip step 10 and 11. If it doesn't boot after that, go back to TWRP and flash the no-verity zip.
Click to expand...
Click to collapse
I just repeated all the procedure, this time just with Magisk, like you said. its installation finished without any error.
I just tryed ROOT Checker, any I finally have the root on my fone!! Thanx you very much for the support, and the explanation.
Can I use Backup/Restoration with TWRP knowing that I rooted with Magisk??
saoudien07 said:
I just repeated all the procedure, this time just with Magisk, like you said. its installation finished without any error.
I just tryed ROOT Checker, any I finally have the root on my fone!! Thanx you very much for the support, and the explanation.
Can I use Backup/Restoration with TWRP knowing that I rooted with Magisk??
Click to expand...
Click to collapse
Great to hear! :good:
You can use TWRP without any issues. Magisk has no impact on it and TWRP has it's own su.
Didgeridoohan said:
Great to hear! :good:
You can use TWRP without any issues. Magisk has no impact on it and TWRP has it's own su.
Click to expand...
Click to collapse
Thx you one more time. Going to install some of my app and configure my new fone then do a backup, for a clean restoration in some months...
I have a problem for the Backup with TWRP. When I want to do a Backup, I get this msg:
failed to mount /data (Invalid argument)
I ve looked on google to fix it, the solution I found is to change data to ext2, then back to ext4.
The pb is that it is removing everything from my phone?
Anyone is having the same issue??
Didgeridoohan said:
Your issue is that the boot image still is patched by SuperSU. Until you restore the stock boot image you won't be able to install Magisk.
https://www.didgeridoohan.com/magisk/Magisk#hn_Boot_image_patched_by_other_programs
Edit: I don't do Samsung, but from what I remember, you might need to flash AP (or something like that).
Click to expand...
Click to collapse
Hi, i am rooting samsung a5 a520w. I am following the steps in the instructions (https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535).
Now I met a problem like this:
! Boot image patched by other programs!
! Please restore stock boot image
Updater process ended with ERROR:1
Error installing zip file '/sdcard/MagiskManager/Magisk-v17.1.zip'
I have no idea where is the boot.img located. All documents in the external card is:
RMM-State_Bypass;
no-verity-opt-encrypt-6.0;
Magisk_17.1
@imcn001 Your answer is in the link from the post you quoted.
While waiting for a working TWRP for all those needful of the possibility to access their file system from recovery, e.g. for removing an offensive magisk extension preventing boot I repackaged the Stock OOS recovery but with ADB enabled.
Prerequisites:
Oneplus 8 Pro
unlocked bootloader
access to fastboot on the phone
adb and fastboot
Installation:
Reboot the phone to fastboot, then flash the recovery from fastboot with the command
Code:
fastboot flash recovery <filename>
(with <filename> being the name of the recovery in the format of "recovery.img" you wish to flash)
Uninstall:
Same as installation, but flash the original stock recovery instead.
Usage:
Boot up recovery, enter encryption key if file system is encrypted. Then connect the phone to PC and you are ready to go with adb. E.g. by using
Code:
adb shell
to open a shell and access the file system. Magisk modules are located in /data/adb/modules, deleting the corresponding directory there will remove the module in question.
Step-by-step this would be:
Code:
cd /data/adb/modules
to change to the Magisk modules directory
Code:
ls
to list the content of this directory, each module has its own directory, usually with a well-recognizable name
Code:
rm -r <directory>
to delete the directory in question. Tip: in console TAB-autocomplete works
Downloads:
10.5.4 BA Recovery
Modified 10.5.4 BA recovery from GDrive
Original 10.5.4 BA recovery from Gdrive
10.5.5 BA Recovery
Modified 10.5.5 BA recovery from GDrive
Original 10.5.5 BA recovery from Gdrive
10.5.6 BA Recovery
Modified 10.5.6 BA recovery from GDrive
Original 10.5.6 BA recovery from Gdrive
Notes of caution:
ADB security is disabled as I could not get the recovery to allow for authorizing a connected computer. As a consequence any computer connected is automatically authorized in ADB, although with encrypted filesystem at least no data is accessible without the key.
with direct ADB access to your file system you can easily wreck you phone requiring a factory reset or even reinstallation of the OS from fastboot - please be careful on what you are doing
Credits: Thanks to osm0sis for Android kitchen and all great developers for the Oneplus devices, specifically mauronofrio for his TWRP efforts.
Description of method to modify recovery by yourself:
Prerequisites:
Android Image Kitchen (credit to osm0sis for providing this tool)
the original recovery image file (henceforth called "recovery.img"). You can extract this yourself from an update zip file by unpacking "payload.bin" and then use a tool like payload_dumper (credit to vm03 for providing this) to extract the recovery.img file
Now do the following:
unpack image with Image Kitchen --> this will create a "ramdisk" and a "Split_img" directory with the unpacked content within
navigate into the "ramdisk" folder and use a text editor (on windows preferably Notepad++) to edit the file "prop.default"
look for entry "ro.adb.secure" and change entry value from "1" to "0". Note this entry can occur multiple times (I noticed twice), change each --> this will prevent adb from asking for authorization (the recovery does not provide such a dialogue)
look for entry "ro.debuggable" and change this from "0" to "1" --> this actually enables adb
look for entry "ro.secure" and change this from "1" to "0" --> may be unnecessary but I wanted to avoid brick in case a modified recovery would result in such a behaviour
save textfile
repack the image with Android Image Kitchen and voila:
you have a new modified recovery image you can flash
Thanks for this...
On fastboot we have to flash the modified recovery img?
EDIT : Nevermind haven't read the whole OP
I have a noob question: this won't affect data or magisk right?
To remove a module , command should not be :
( rm -rf < directory> ) ?...
cultofluna said:
To remove a module , command should not be :
( rm -rf < directory> ) ?...
Click to expand...
Click to collapse
Thanks for your comment, but technically no
The - f flag is used to omit prompts before each removal, which may or may not be helpful - depending in how sure the user is on what he does
I chose the safer variety in my example, confident that users with more knowledge can always look at the "rm" man page to decide what command they want to use...
But again thanks, I do appreciate your help!
HottieLinus said:
I have a noob question: this won't affect data or magisk right?
Click to expand...
Click to collapse
Correct, the recovery resides in a separate partition and flashing it doesn't do anything anywhere else.
In fact the recovery looks and behaves the same when booting into it, the change only becomes apparent by being able to use adb in recovery.
@s3axel can we use this recovery to escape bootloop due to install unsupported theme or any issue from substratum?
Or maybe just flashing stock boot IMG on fastboot is enough...
cultofluna said:
@s3axel can we use this recovery to escape bootloop due to install unsupported theme or any issue from substratum?
Or maybe just flashing stock boot IMG on fastboot is enough...
Click to expand...
Click to collapse
It should be possible as the recovery gives you full access to your file system and so, given you know what to remove/change, it should also be possible to recover from issues as you mentioned.
My problem: I have no idea where themes or substratum additions are installed directory-location wise, will need to research a bit. Or maybe someone else can chime in on this, then I could update OP with info on that as well...
Ok one more question..
Can we flash zips through the recovery?...
Via ADB sideload?.. maybe..
cultofluna said:
..Can we flash zips through the recovery?...Via ADB sideload?..
Click to expand...
Click to collapse
I don't know but I doubt it as to my knowledge ADB sideload is a special mode that needs to be activated e.g. in TWRP. So far I didn't have the need to use such a functionality and thus haven't tried it :angel:
s3axel said:
I don't know but I doubt it as to my knowledge ADB sideload is a special mode that needs to be activated e.g. in TWRP. So far I didn't have the need to use such a functionality and thus haven't tried it :angel:
Click to expand...
Click to collapse
Ok...
Because on pixel4 XL you can reboot to stock recovery and choose the the option ADB sideload...
And from there you can flash a custom ROM...etc..
Updated OP with 10.5.5 recovery..
s3axel said:
Updated OP with 10.5.5 recovery..
Click to expand...
Click to collapse
That recovery looks like it's for BA. Does that recovery work on AA as well?
---------- Post added at 08:50 PM ---------- Previous post was at 08:48 PM ----------
s3axel said:
I don't know but I doubt it as to my knowledge ADB sideload is a special mode that needs to be activated e.g. in TWRP. So far I didn't have the need to use such a functionality and thus haven't tried it :angel:
Click to expand...
Click to collapse
Is the OnePlus 8 pro system partition dynamic? Meaning it'll be an absolute nightmare to ever get TWRP like the OP 7T series? I really hope not, flashing through ADB for everything sucks.
Burt Squirtz said:
That recovery looks like it's for BA. Does that recovery work on AA as well?
---------- Post added at 08:50 PM ---------- Previous post was at 08:48 PM ----------
Is the OnePlus 8 pro system partition dynamic? Meaning it'll be an absolute nightmare to ever get TWRP like the OP 7T series? I really hope not, flashing through ADB for everything sucks.
Click to expand...
Click to collapse
Yep..
Definitely dynamic partitions...
Don't expecting a fully working twrp...
You can find a chinese twrp that boots and decrypt..
But sources are unknown...
cultofluna said:
Yep..
Definitely dynamic partitions...
Don't expecting a fully working twrp...
You can find a chinese twrp that boots and decrypt..
But sources are unknown...
Click to expand...
Click to collapse
do you have a link to that Chinese TWRP by chance? And how would I initially flash it, adb? Or Could I probably go through magisk manager?
Burt Squirtz said:
do you have a link to that Chinese TWRP by chance? And how would I initially flash it, adb? Or Could I probably go through magisk manager?
Click to expand...
Click to collapse
That Chinese TWRP violates glp so it cannot be shared here on xda..And if were you I woulnd be using that anyway..Just my two cents
pyry666 said:
That Chinese TWRP violates glp so it cannot be shared here on xda..And if were you I woulnd be using that anyway..Just my two cents
Click to expand...
Click to collapse
What an incredibly helpful response. Sorry but if there's something that'll decrypt and allow me to backup and recover, of course I'm going to try and find it. And I suspect most other people here would too.
Burt Squirtz said:
That recovery looks like it's for BA. Does that recovery work on AA as well?
Click to expand...
Click to collapse
I don't know presently, usually I compare recoveries or I (or other users) add recoveries for other regions which they made by themselves. When recoveries are the same of course they can be used
RIght now I cannot download the 10.5.5 AA firmware (download aborts after some time), I'll add the recovery once this is working... EDIT: seems OP pulled the downloads, so no luck at the moment...
If there is a working twrp in China then perhaps it's worth making contact with them to see if either:
A) they can let you have it
B) they can help you fix this one?
It's presume the former would make the most sense, with permission I see no problem in obtaining it or linking it, certainly not taking about it. Makes no sense to just avoid an obvious assist whilst we all struggle without twrp.
purpose of this post is to share an alternative method for those who fail to root using @topjohnwu recommended method or the method posted by @Grarak here on A70 forum that involves patching recovery.img in magisk and then flashing that in twrp>install to boot.
failing to root means either bootloops or unstable magisk root or magisk root disappearing randomly or after a module installation.
this is not my original guide , i was told this method by @raeumler via PM and i am sharing it on A70 forums incase other methods dont work.Some of the steps may not be neccesary , but i did them ritually anyway
my phone model is SM-A705FN /DS and firmware version is A705FNXXU5ASL4( with 1st jan 2020 updates) . country is PAK
do this at your own risk! i will not be responsible for any negative consequences
appropiate links and files will be posted as attachments
rooting procedure( read each step twice)
1- UNLOCKING BOOTLOODER= this will factory reset device . backup your data
read step 02 of this linked guide https://forum.xda-developers.com/galaxy-a70/development/recovery-twrp-galaxy-a70-t3955984
DOWNLOAD FIRMWARE AND ATTACHMENTS= now i am assuming you have stock samsung android 9. if not, download your firmware via SamFirm windows program and flash in odin to go to stock[ program available in attachements]. Download other attachements too
2-Find vbmeta.tar in downloaded attachments and unpack it. you will get vbmeta.img file.
3. unzip stock Samfirm downloaded firmware. you will get 5 files in it (BL,AP,CP,CSC and CSC_HOME).open the AP File from the factory rom with 7zip
4. remove userdata.img, vendor.img and system.img from the AP file
5. replace vbmeta.img with the one you have downloaded in step 2.
6. repack AP as AP.tar [ use 7zip or peazip. i used peazip windows program, ensure file type is TAR]. transfer this AP.tar to your phone
7. install magisk manager 7.5.1 on your phone and open it. connect your phone to internet.
8. hit the upper install button and choose "patch a file"
9. choose the repacked AP file and patch it[ this requires active internet as magisk needs to download its zip file]
10. copy the AP file which magisk creates in internal storage/download/magisk_patched.tar back to your pc (better keep it named as such for differentiation, its irrelevant how the file is named as long its a tar file)
11. download,unzip and open Odin 3.1.3.1[available in attachements]. i used Odin3+v3.13.1_3B_PatcheD.exe , there is a simple version too inside the zip
12. go into download mode on your phone (shut down completely then hold vol+ vol- togather and plug in cable connected to PC ). Odins should show Com port X as blue
13. in odin: put the BL, CP and HOME_CSC in its place (the files from the factory firmware you downloaded in step 1 from SamFirm windows program) and place the magisk patched AP on AP
16. check if you want autoreboot or not, its your own taste (some feel safer with autoreboot unchecked, both works)[ i kept autoreboot checked]
15. hit start and let it finish (when it stucks on something try another cable and install latest samsung adb driver.)
16. let the system reboot
17. if you get stuck in bootloop or freeze >10 min on samsung logo, try to force reboot.press volume down + power till screen turns blank then press volume + and power till bootloader unlock screen appears and then let go of all keys.
if still it doesnt boot, then press volume down and power togather to force shutdown and then press volume up and power till stock recovery boots up. Mine at this stage said firmware is corrupt ,factory reset needed so thats what i did in stock recovery. power off system in stock recovery and then press volume+ and power till bootloader warning screen , let go of all buttons, it should now boot up fine with magisk manager app in app drawer. DONT OPEN IT YET
download this app from play store https://play.google.com/store/apps/details?id=fr.petrus.tools.reboot&hl=en_US. open app and press reboot. No need to press any keys
on reboot complete ,connect to internet,open magisk, let it check for updates, it should say installed in both portions. magisk will do additional enviromental steps and then reboot. on booted up, use the linked reboot app to reboot again.
now magisk should be installed all fine
for viper4android>open magisk>swipe left and tap downloads> installed 2.7.1.6> reboot with linked app
on reboot check if app is installed, if not > install and login on xda labs and download viper4android 2.7.1.6> open app> give it root accesss> let it reboot device on installtion> on bootied up reboot again with linked app and then check drivers on viper4android[ make sure master switch is on and then play some music ,tap the chip icon to see driver status and processing status
from here onward, always use the linked reboot app to reboot device. if an app or module reboot device automatically( like viper4android does ) then on boot complete,reboot again with the linked app
Credits to @Grarak for his original work and files
@raeumler for his guide.
Unfortunately, it doesn't work on Android 10.
There is an error in Odin when flashing files.
The error is when flash the AP file, more specifically vbmeta.
kac222 said:
Unfortunately, it doesn't work on Android 10.
There is an error in Odin when flashing files.
The error is when flash the AP file, more specifically vbmeta.
Click to expand...
Click to collapse
This is for stock android 9 as the title says.
Follow @MarvinMod guide to root android 10
Yes i know but i tried for yourself. I know how rooted on Android 10. Regards.
Wysłane z mojego SM-A705FN przy użyciu Tapatalka
Looks like a useful guide, thank you for putting it up. I'm really not sure how to get the firmware though from the SamFirm program. I found this ( https://androidmtk.com/use-samfirm-tool - might be useful info?) since I have never used the samfirm tool before I am lost at that step. I don't know if there's a list of region codes somewhere? I have an 'international version' A70. Using SM-A705MN, baseband version A705MNXXU3ASI1 .. Since I'm in the US, should I look to getting that type of ROM or should I find out what region this particular ROM already on the phone is, and use that?
I've done rooting before (Samsung S4, HTC M9, LG V20) but these phones seem even more complicated.
Even if all this works, then the root is not 'permanent'? I'm not sure why a different 'reboot app' would be needed if the system is modified in a way to enable things like magisk/super su?
DelphisDoofer said:
Looks like a useful guide, thank you for putting it up. I'm really not sure how to get the firmware though from the SamFirm program. I found this ( https://androidmtk.com/use-samfirm-tool - might be useful info?) since I have never used the samfirm tool before I am lost at that step. I don't know if there's a list of region codes somewhere? I have an 'international version' A70. Using SM-A705MN, baseband version A705MNXXU3ASI1 .. Since I'm in the US, should I look to getting that type of ROM or should I find out what region this particular ROM already on the phone is, and use that?
I've done rooting before (Samsung S4, HTC M9, LG V20) but these phones seem even more complicated.
Even if all this works, then the root is not 'permanent'? I'm not sure why a different 'reboot app' would be needed if the system is modified in a way to enable things like magisk/super su?
Click to expand...
Click to collapse
Download phone info app and note pda, csc and phone codes.
Use these codes to Google your exact firmware and download that ( you may have to visit various websites that offer better speed)
The samfirm, frija only allows latest firmware to be download, not the currently installed one.
One you have the stick firmware file, then you can proceed with rooting.
If you are on android 9 use this guide
If you are on Android 10 use MarvinMod guide.
This reboot app is what I currently use. Haven't experimented with other apps.
The root is permanent as long as your reboot with the mentioned key combination or the reboot app.
The reboot app simple allows you to reboot without the key combination. If you don't want to use this app then you must reboot with the mentioned key combination to retain root. Otherswise you wouldn't have root unless you reboot again with correct combination.
To make this easy I suggested that reboot app
Yes I feel you bro, I had Samsung note 2 then note 4 phone and they were easier to root.
But with Google changing things the best way to root is to use magisk and this complicated methods
i think you can make a little script for rebooting. should work. i really want to know how the bootpartition is corrected, at boot its recovery-from-boot.p as image and install-recovery.sh for reenabling stockrecovery. if you rename this files bootup should work without reflashing boot or recovery. there have to be something similar to the rebootprocess, a script that flashes a sparse image (the *.p file to delete su binary or something like that..) or it just kills the su binary in the folders itself. im to stupid for dmesg and logcat i couldnt find out whats going on at reboot. also the petrus reboot app reboots instant, keys doesnt. seems to be that adb reboot deletes root too. yesterday, somehow my fone did sonething last night, which crashes root again.....i need twrp urgent to make backup. but the binary let not decrypt it. U5 is android 10 bootloader and there are some issues with twrp (decrypt). last time it has saved my backuptry to /data/backupfolder as internal is encrypted. i dont want to factoryreset this phone....is it complicated to build a recovery ? or is there something like a clickitalltogetherapp?
---------- Post added at 09:46 AM ---------- Previous post was at 09:24 AM ----------
following reboot variants keeping root:
hold all keys for 10 seconds
reboot via terminal or script
petrus app
following kills root:
standartreboot with hw-keys
adb reboot (on a dosprompt from pc)
boot to stockrecovery
magisk module reboot
but thats is such a XXXX .. i dont have a word for it, in the beginning computers and so are working logical....seems that samsungs security trends are not that logical as needed... i hate samsung :/. there have to be someone who find the "unsu"-files...cannot be....
raeumler said:
i think you can make a little script for rebooting. should work. i really want to know how the bootpartition is corrected, at boot its recovery-from-boot.p as image and install-recovery.sh for reenabling stockrecovery. if you rename this files bootup should work without reflashing boot or recovery. there have to be something similar to the rebootprocess, a script that flashes a sparse image (the *.p file to delete su binary or something like that..) or it just kills the su binary in the folders itself. im to stupid for dmesg and logcat i couldnt find out whats going on at reboot. also the petrus reboot app reboots instant, keys doesnt. seems to be that adb reboot deletes root too. yesterday, somehow my fone did sonething last night, which crashes root again.....i need twrp urgent to make backup. but the binary let not decrypt it. U5 is android 10 bootloader and there are some issues with twrp (decrypt). last time it has saved my backuptry to /data/backupfolder as internal is encrypted. i dont want to factoryreset this phone....is it complicated to build a recovery ? or is there something like a clickitalltogetherapp?
---------- Post added at 09:46 AM ---------- Previous post was at 09:24 AM ----------
following reboot variants keeping root:
hold all keys for 10 seconds
reboot via terminal or script
petrus app
following kills root:
standartreboot with hw-keys
adb reboot (on a dosprompt from pc)
boot to stockrecovery
magisk module reboot
but thats is such a XXXX .. i dont have a word for it, in the beginning computers and so are working logical....seems that samsungs security trends are not that logical as needed... i hate samsung :/. there have to be someone who find the "unsu"-files...cannot be....
Click to expand...
Click to collapse
I didn't messed with boot or recuvery files like the way you DM me.
But I have been noticing strange behavior with petrus app.
Reboot option in petrus app is kinda of like fast reboot or reboot UI. Because all apps opened and present in task manager remain so after reboot with petrus app.
Also once you power off with petrus app,
1= booting up with root key combination results in phone getting freeze Or bootlooping
2=. Force shutting phone again bootloop phone.
3= Going to stock recovery and rebooting system bootloop.
4= going to stock recuvery and shutting off phone from there and then simply pressing power button without key combination, successfully bootup phone with root intact.
This is such a bizzare behaviour
Oh and i am still on Android 9 pie.