Database Info

[A511/A510] [01-07-2012] Root is possible!

Dear all,
I managed to create a script that enables root!
** WARNINGS **
This has not been tested much... any problems are @ own risk
** Download **
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ROOT-A51x.zip (679.1 KB) or http://www.multiupload.nl/8QVEMO3P0R
** Install instructions **
1. First install CWM Recovery (or any other you can find for your device)
2. Upload ROOT-A51x.zip to your external sdcard
3. Run the following command to enter recovery (or power off your device, press Volume- and then Poweron your device):
Code:
adb reboot recovery
4. In the recovery select "install zip from sdcard"
5. Then select "choose zip from sdcard"
6. Choose your "ROOT-A51x.zip" file
7. Choose yes - install ROOT-A51x.zip
8. Wait till the script is ready and reboot your device
If something fails, you can run "adb shell" from the recovery and use "cat /tmp/recovery.log" to provide the output of the scripts.
Enjoy & good luck
Regards,
Nika.

Here's some instructions how to unlock boot loader:
Code:
adb reboot-bootloader
** wait for it to load
fastboot oem unlock
** press Volume- (two dots button) and then Volume+ (one dot button) to unlock
fastboot reboot-bootloader
** you're in the unlocked bootloader :)

I have tried several memory offsets and all return a non-rooted-shell (ie. $ instead of #):
mempodroid 0xd6c4 0xad33
mempodroid 0xd7cc 0xad27
mempodroid 0xd7f4 0xad4b
mempodroid 0xd9ec 0xaf47
mempodroid 0xd9f0 0xaf47

Hi,
i just got the A511 out of the box.
Im very interested if theres a way to root.

mongocliqque said:
Hi,
i just got the A511 out of the box.
Im very interested if theres a way to root.
Click to expand...
Click to collapse
I haven't found a way yet what build number does your device have?

nikagl said:
I haven't found a way yet what build number does your device have?
Click to expand...
Click to collapse
Hi,
I also got an A511. Root is also not working for me
My build number is Acer_AV041_A511_1.028.00_EMEA_DE
I really hope someone will get root working on the A511

Its just annoying that root is still difficult like that.
There are so many things like lbe or pdroid (on other devices) that i never want to miss again on every Android Device.
ACER_AV041_A511_1.028.00_EMEA_DE , @ Kernel 2.6.39.4+

Well... While building a new recovery I killed my recovery and cannot install update.zip's anymore... luckily no brick, but does make it harder to test stuff.
Therefore I cannot test attached root script. It's based on someone else's script to unlock the bootloader first, and then install an update.zip that contains all root files.
Anyone care to test it? It cannot brick your device or kill your recovery, so don't worry. It will probably not work, but doesn't hurt to test it
Furthermore. If there's still someone with a rooted A510, can you dd your recovery and upload it? I can try the stock recovery of A510 to see whether it works on A511
I can think of two commands that may work for exporting recovery on an A510:
Try this:
Code:
dd if=/dev/block/platform/sdhci-tegra.3/by-name/SOS of=/mnt/sdcard/recovery.img
Or try this:
Code:
dd if=/dev/block/mmcblk0p1 of=/mnt/sdcard/recovery.img
Or possibly even this:
Code:
dd if=/recovery of=/mnt/sdcard/recovery.img
Regards,
If one of them is successful it will export the recovery to your internal sd...
Nika.

Well, turns out my recovery is not corrupted. Tried installing the 1.011 ROM and it worked without a problem (although I wanted to wait till root would be available so I could do a full backup)... so I guess that root zip provided in the previous post still has some error in it...sorry, will continue investigation, somehow, sometime, somewhere we'll find a way

Would be nice.
Atm im not rly use my Tab, too many Spy Aps around that are confirmed via pdroid.
lbe first for me

Well... my tab is now rooted!! See first post (OP) for the root script & instructions how to do it...
Good luck!
Regards,
Nika.

Sounds nice.
But im waiting if its really secure, that tablet was too expensive to brick

nikagl said:
Well... my tab is now rooted!! See first post (OP) for the root script & instructions how to do it...
Good luck!
Regards,
Nika.
Click to expand...
Click to collapse
Well done, Nika!

mongocliqque said:
Sounds nice.
But im waiting if its really secure, that tablet was too expensive to brick
Click to expand...
Click to collapse
It's never safe if you want safe - don't root, that's what it's for
And yes, first install cwm recovery, then install root-zip from this thread through cwm-recovery.

nikagl said:
It's never safe if you want safe - don't root, that's what it's for
And yes, first install cwm recovery, then install root-zip from this thread through cwm-recovery.
Click to expand...
Click to collapse
Nah, i know that, but first i want to see more rooted devices.
Can this cause issues?
Acer_AV041_A511_1.028.00_EMEA_DE

it really works
Hi nikagl,
thanks, i got root on my brand new, long time awaited A511.
For the bootloader-recovery i had to use the vol button with the two dots (it´s the vol down (-) button in my A511) no matter what direction the turn-look switch had.
Right now did the needed Stock (rooted su 3.1) Backup successfully with the CWM touch.
Really Great Job!

hey guys, i rooted my a511 too thx nikagl
but i did it a lil bit diffrent from your manual

Ah great to hear.
I think that i got issues then with my VB.
So i have to get a real windows pc for flashing recovery, it looks like.

blgblade said:
hey guys, i rooted my a511 too thx nikagl
but i did it a lil bit diffrent from your manual
Click to expand...
Click to collapse
It would be helpful to everyone if you could list what you did.
Thanks.

hmm, i have a problem i can use the su shell, but root applications wont work
EDIT: now it works, with superuser from market

[GUIDE] Enable Multi-Window Mode on Android 6.0 Marshmallow

There's a hidden feature in Android 6.0, multi window. It has its warnings:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So decide if this is actually for you before following these steps
It's not shown in user builds, so we have to do some messing. You'll either need root or a custom recovery to do this, but as not everyone wants root, here's how you do it with TWRP, a USB cable, and a PC with ADB:
1. Boot your device into recovery
2. Mount your system by going to Mounts > Tick System
3. On your PC open a command line, somewhere like your desktop is useful
4. Type the following command:
HTML:
adb pull /system/build.prop
5. Open the build.prop file with your favourite (decent) editor, I recommend using Notepad++ on Windows
6. Find the "ro.build.type" line
7. Change the text after = to "userdebug" from "user"
BONUS: If you want a nicer DPI here, change the line "ro.sf.lcd_density" to your preferred DPI
8. Save the file
9. Go back to the command line and enter the following command:
HTML:
adb push build.prop /system/
10. Now open a shell doing:
HTML:
adb shell
11. Now a adb shell will open, enter these commands:
HTML:
cd system
chmod 644 build.prop
12. Reboot the device as normal
13. When the device has booted, go to the developer options
14. Scroll down to the bottom of the "Drawing" category
15. Enable multi-window and have some fun!
If you're rooted...
1. Download "Build.prop editor"
2. Find "ro.build.type"
3. Edit it to have the value "userdebug" from "user"
4. Reboot when prompted
5. When the device has booted, go to the developer options
6. Scroll down to the bottom of the "Drawing" category
7. Enable multi-window and have some fun!

Worked ! Thanks
Such a shame the Keynote didn't introduce such feature, it's stable enough. Just think of the use of the feature on a 10" tablet.

works perfect thank you !

How do you use it after enabling?

Chahk said:
How do you use it after enabling?
Click to expand...
Click to collapse
Go recent menu, on the apps beside the x there's a button to choose the top half or second half.
Multirom users can go /data/media/multirom/roms/ and edit the build prop directly there, no need to use adb. I did it without using a PC

I flashed the latest hammerhead twrp with fastboot command, it was successful, but when I reboot bootloader and choose recovery, it keeps loads forever and sometimes the screen flashes black. I tried CWM after that, it said root needed. How do you guys got recovery on M?

Chahk said:
How do you use it after enabling?
Click to expand...
Click to collapse
I get how to use it, but how do you consistently pick the two apps that you want to appear?
---------- Post added at 11:28 AM ---------- Previous post was at 11:26 AM ----------
elreydenj said:
I get how to use it, but how do you consistently pick the two apps that you want to appear?
Click to expand...
Click to collapse
It seems to be all over the place. I cant figure out how to always get the two apps that i want in multiwindow to show....

prwnd said:
I flashed the latest hammerhead twrp with fastboot command, it was successful, but when I reboot bootloader and choose recovery, it keeps loads forever and sometimes the screen flashes black. I tried CWM after that, it said root needed. How do you guys got recovery on M?
Click to expand...
Click to collapse
This is the wrong place to ask this question . Check your pm i have given you the solution and please ask your questions in the right thread next time onwards

is it possible to do that with Wugfresh Nexus Root Toolkit?

jonathanxx1 said:
is it possible to do that with Wugfresh Nexus Root Toolkit?
Click to expand...
Click to collapse
Nope. I tried doing the "push/pull files" and it didn't work. You can install custom Recovery with WugFresh then follow these instructions.

drgonzo712 said:
Nope. I tried doing the "push/pull files" and it didn't work. You can install custom Recovery with WugFresh then follow these instructions.
Click to expand...
Click to collapse
I tried also ,,and it doesn't work.

Adr990 said:
I got this message from ADB:
Anything?
Click to expand...
Click to collapse
Open terminal, type
su
cd system
chmod 644 build.prop
exit
and do stages again

Adr990 said:
When I do that, in adb shell:
Click to expand...
Click to collapse
Ow, i forgot ,my mistake sorry can you try this ?
cd system
chmod 777 build.prop
exit

damn.. is there a way to do it if it is a secondary rom on multiboot?

Adr990 said:
Oh and I also tried this:
Kinda wierd how it is not working for some, while we all flashed according to Google's adb flashing method.
Click to expand...
Click to collapse
Can you send your build.prop to me via pm. I can make a flashable zip for you

Hello people, I have multirom installed on my nexus 5, the primary rom is 5.1.1 (LMY48B), and my secondary rom is the developer preview MPZ44Q. I want to know if it's possible to enable multi-window mode since the M preview is installed as secondary rom.

I did it. Reboot into recovery. Swap the Roms. Don't reboot . reboot into recovery again from the reboot tab. Select multiboot tab just to ensure you are OK and the M ROM is the internal.. Mount system and do what the op says. Reboot into recovery again swap Roms again . reboot system and you should be OK. Takes like a half an hour to do though
PS. NEVER FIX SU. ALWAYS SKIP

I understood that if i try to install su on the M rom, it will result in bootloop. And my internal rom is stock ROOTED. So do you think it will work ?
When i will swap the roms, the fact that my primary rom is rooted, will it cause any problem ? Thanks in advance.

Nope my primary is still rooted. And I an typing this from my secondary M ROM with multi window enabled. All you have to do is never fix su for either ROM and never boot the system with M as your primary ROM and you are ok

Help me too
hsay said:
This is the wrong place to ask this question . Check your pm i have given you the solution and please ask your questions in the right thread next time onwards
Click to expand...
Click to collapse
This is the worst thing to do here but could u please guide me too to the recovery as i searched all i could but still got no answer. Even the Guys in the Discussion group had no answer. Please Help ME,.

[GUIDE] How to root zenfone 3 (ZE552KL / ZE520KL)

Original Article : https://www.asus.com/zentalk/tw/thread-177291-1-1.html
[email protected] post the root guild for zenfone 3.
I translate his article to English version.
I didn't try this method yet, but I think it should work.
If you want to root your zenfone 3, you can following this guide to root your device.
============================
[Update] All-in-one zip (unlock App+driver+adb+fastboot+twrp+SuperSU.zip) :
https://github.com/snowwolf725/RootZenfone3/archive/master.zip
Firstly, you should use the following official unlock tool to unlock Boot-loader.
[Update] If you want to receive OTA notify, you should use Un-official bootloader unlock method.
Un-official bootloader unlock method
ZE552KL
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE552KL/ZE552KL_SIGNED_Android_M_UnlockTool_2016_0715.zip
ZE520KL
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE520KL/ZE520KL_SIGNED_Android_M_UnlockTool_2016_0715.zip
After you unlock your device, you can download the TWRP recovery image, and follow the guide to root your device.
TWRP recovery img ：https://mega.nz/#F!kl8lmKRL!ZbLvz1b4YgLMr_n09vRrTA
twrp-3.0.2-Z012D.img (TWRP for ZE552KL)
twrp-3.0.2-Z017D.img (TWRP for ZE520KL)
dot.supersu (.supersu)
If your device is ZE552KL, then you should download twrp-3.0.2-Z012D.img + dot.supersu
If your device is ZE520KL, then you should download twrp-3.0.2-Z017D.img + dot.supersu
If you want to build recovery image by yourself, you can clone the git source tree, and compile by yourself.
https://github.com/shakalaca/android_device_asus_ze520kl
https://github.com/shakalaca/android_device_asus_ze552kl
How to root your device:
1. Boot your zenfone 3 to boot-loader mode (you should firstly turn the phone off, then press and hold the volume up and power buttons )
2. Install android tools on your pc. (http://forum.xda-developers.com/showthread.php?t=2588979)
3. Connect your mobile to PC, then use following command to flash TWRP image to your zenfone.
Code:
fastboot flash recovery twrp-3.0.2-xxx.img
4a. Hold the volume down button, and use following command to boot into recovery mode. (if menu appears, please select recovery mode)
Code:
fastboot reboot
4b. Boot your zenfone 3 to recovery mode (you should firstly turn the phone off, then press and hold the volume down and power buttons )
5. After boot into TWRP recovery, select "keep system read only" in TWRP recovery menu.
6. Use following command to push .supersu file into /data .
Code:
adb push dot.supersu /data/.supersu
7. Select "ADB Sideload" in TWRP menu, then use following command to push root files.
(SuperSu.zip http://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703)
Code:
adb sideload SuperSU.zip
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
8. reboot and enjoy your rooted device.
PS. If you got OTA notify, you can flash the stock image to un-root your device.
Stock boot.img and recovery.img files can be find in following URL:
https://mega.nz/#F!ok0V0RIA!5WKtHe98opzjVI3NPbM7Ww

Who can test ?

superuser.pm said:
Who can test ?
Click to expand...
Click to collapse
its 100% working bro

Does the unlock tool really wipe the data on the device??

aelzki said:
Does the unlock tool really wipe the data on the device??
Click to expand...
Click to collapse
yes its wiping entire phone.

can i root the phone without uncloking the bootloader ?

BentotKulangot said:
its 100% working bro
Click to expand...
Click to collapse
Are u trying? 7up screenshot for everybody . ..

superuser.pm said:
Are u trying? 7up screenshot for everybody . ..
Click to expand...
Click to collapse
This is work.. now i have rooted phone and installed xposed

after rooted? we can get OTA? or no? if not how to get the OTA?

i must unlock bootloader before flash twrp ?
on phone turn on or off USB debugging mode ?

100% working
I have been waiting and waiting for this post. worked instantly, with no headaches. Well just remember to back up your stuff first.
Thanks to OP for the translation!
Won't allow me to post the image or link being so new. Just try it out.
drive.google.com/open?id=0B08xanlQWY50UHhEZlBfM1BncWs
sorry mods if this is bypassing the spam guards.

i cant get OTA UPDATES after unlock the bootloader LOL

They do warn you specifically that pushed updates will no longer happen.
I think the solution is to find the updates from ASUS and use an app like FlashFire

There is a request for a Rom on the cyanogen forums.
Xposed worked like a charm.
It also appears that the kernel source is available although I'm not sure from where.
Still not sure where to find the ASUS updates

Thank you very much it works perfect, but how do you flash the recovery.img and boot.img to un-root?

TWRP Decrypted and Couldnt Mount Storage
Thanks for the guide, its 100% worked!
But I have a problem. I couldnt mount storage to instal ZIP file. Also my TWRP said its encrypted, and i dont what password to decrypt is.
Anybody know how to solve this?

Is there any CN stock recovery to download?

i got error device 'null' not found when trying to sideload the supersu. help me please

Chandro-ID said:
i got error device 'null' not found when trying to sideload the supersu. help me please
Click to expand...
Click to collapse
I got this problem too, just install the super su from twrp solved my problem

Will it work for ZS570KL?

[X553] recowvery, unlock, root Infinix HOT 3 LTE potential - with TWRP

Team Win Recovery Project 3.0.2-0
How it looks :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Notice : I don't own the device my self, so i need some one to test this method.
This will allow you to install TWRP and flash SuperSU!
Step 1 : Unlocking your bootloader
You need unlock bootloader first before installing twrp.
You will also need adb and fastboot. You can download them in a portable small form factor here :
[ADB FASTBOOT][LINUX&WINDOWS]
Start by turning on developer options in Settings -> About device -> Software info -> Build number. (tap 7 times until it's enabled)
Now navigate to Settings -> Developer options -> OEM unlock. (turn it on)
Don't ever turn OEM unlock or Developer options off when using a custom ROM or recovery. This could lose to loss of all your data.
Enable usb debugging on developer option, and extract adb and fastboot to a folder on your PC.
Type adb start-server and make sure to check the notification on your phone to accept debugging authorization.
You can reboot into fastboot mode with adb reboot bootloader once authorized.
If it fails to authorize or show the notification on your phone, you may need to try other USB ports.
You can check the status of your bootloader lock with the fastboot getvar all command.
ex. (bootloader) unlocked:yes
Step 2 : Running recowvery
You can find the recowvery binaries (you need to download all of these) at :
Here
You're now ready to follow the recowvery installation instructions.
See here (running section)
Bonus: There's also a full write up on that page on how recowvery works if you're into that kind of stuff.
Step 3 : Flashing TWRP & Rooting
Once you've got your permissive shell in adb, you will have access to your partitions via dd.
You should transfer TWRP to your internal storage (name in twrp.img) using MTP, or you can also just use adb push. (mentioned here)
Download TWRP build here.
This step requires that you've used dirtycow to replace /system/bin/run-as with recowvery-run-as. If you've rebooted since doing that, you will need to go back and do that again.
Code:
adb push twrp-3.0.2-x-xxxx.img /sdcard/twrp.img
adb shell
$ run-as exec dd if=/sdcard/twrp.img of=/dev/block/bootdevice/by-name/recovery
"<wait for it to complete>"
$ reboot recovery
You should be inside TWRP now. It will ask you if you want to enable system modifications. You should swipe yes, otherwise your OS will replace TWRP on next boot.
Flash the latest zip from here to turn off forced encryption at boot and allow you to boot a modified system. If you're flashing SuperSU.zip, it will also do this for you so this won't be necessary.
Warning: If you don't flash either no-verity-opt-encrypt or SuperSU, you will probably end up in a horrifying never-ending boot loop of "corruption"!
Latest SuperSU : here
To disable encryption after flashing SuperSU or the no-verity-opt-encrypt zip, you must use the [Format Data] button on the Wipe page in TWRP. No other options will work.
Back up all your internal storage and apps data that you can to your PC. You can use Titanium Backup with SuperSU before doing this step if you like.
Warning: Using [Format Data] will wipe all your apps and data (including internal storage) off the phone, giving you the out-of-the-box experience of a new phone!
Once this is done, you should be able to backup/restore/use any function of TWRP without any issues.
Flashed SuperSU? You're done! Boot up (it will reboot a few times) and set up your SuperSU Manager to your liking and give this post a thanks!
Step 4 : Have fun!

Thanks for this great work brother
But sorry i can't try any thing right now because I have exams nowadays
I want to tell you also that I just rooted successfully my hot 3 lte now using kingoroot apk with out using pc 😄😄😄

ModaAli said:
Thanks for this great work brother
But sorry i can't try any thing right now because I have exams nowadays
I want to tell you also that I just rooted successfully my hot 3 lte now using kingoroot apk with out using pc 😄😄😄
Click to expand...
Click to collapse
so root is done, then time to try twrp just if u not busy

And then for custom rom ??
But later, I'm so busy sorry ? ?

ModaAli said:
And then for custom rom ??
But later, I'm so busy sorry ? ?
Click to expand...
Click to collapse
Don't hope too much this is still for testing but probably soon will have a custom rom, well good luck for your exam bro :good:

It will be sure
Thanks bro ?

Thread closed per OP request.

[AIO][ROOT][MODS] All-in-one thread for the Starmobile Up Prime

Starmobile Up Prime
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SOME INFO:
MT6737/M (they seem to be the same thing)
Antutu Score: 30052 [source]
As of Jan 6 2018, latest official firmware is v13 06292017.
A. Root
Disclaimer: YOU ARE DOING THIS AT YOUR OWN RISK. I will not assume any responsibility for your own actions on your phone. Follow the instructions carefully, and ask questions if you're unsure.
Tested way: Magisk Manager patched boot method
Other option: SRS Root reports to root the v12 firmware, though I didn't use this method so I don't know if it works.
Magisk Manager Patched Boot Method
1. Unlock your bootloader (Note: this will factory reset your phone and you will lose all your personal data) To do this:
Enable bootloader unlock inside developer options, accessed by pressing build number 7 times in settings. Thanks @Nao Tomori !
Install adb and fastboot on a computer (Search it, it's available)
Reboot to fastboot mode (Switch off phone, press power and volume up simultaneously. Choose fastboot mode from the menu that appears)
Connect to computer by USB Cable provided
Open a command prompt or terminal and check if fastboot detects your device by typing
Code:
fastboot devices
A device number should appear. If nothing appears, it's a most likely driver problem. Click this button to know more.
Linux doesn't need drivers so try using fastboot in linux. If you really want to do it in windows, try PDANET drivers while connected in fastboot mode. No guarantees. I'm using a linux machine to specifically avoid this hassle
​
We're now gonna unlock your bootloader. Type
Code:
fastboot oem unlock
and confirm unlock by clicking volume up on your phone.
Reboot and go through all the necessary set-up.​2. Download Magisk Manager from here and install the APK.
Make sure you download the latest apk version provided.
Note it says that Magisk itself is not yet installed.
We've only installed the helper app.
3. Flash Patched Boot Image
At this point you have two options: extract and patch your own boot image, or just use my patched boot image. I will assume you pick the second but this REQUIRES that you are on the same v13 06292017 official firmware. PM me if you want to do the first one. Download my patched boot image.
Download​
Move the file to a known location that's easy to type (home directory or C Drive)
Reboot to fastboot mode, same as before
Flash with fastboot then reboot
Code:
fastboot flash boot /path/to/patched_boot.img
Code:
fastboot reboot
​CONGRATS! Magisk should now be installed and along with it, Magisk's Superuser
Press thanks if it helped you! And/or leave feedback if it worked for you, and if your setup differed from mine. Thanks

MODS
B. Mods
1. Xposed Framework (systemless)
Install Xposed framework from within Magisk. Install API24.
Then reboot. This first boot takes really long. I pulled out my battery once, then the next time it successfully booted after a while.
Install topjohnwu's Xposed apk from his systemless Xposed thread.
It will tell you that Xposed is installed but not active yet.
Reboot one last time
2. Dolby Atmos (systemless)
Install from within Magisk. Confirmed working!

RECOVERY
Reserved

If you get fail operation
If you get
Code:
FAILED (remote:
Unlock operation is not allowed
)
Just go to Developer Settings > OEM Unlocking and enable it.
I used PDAnet for Windows and it worked

Nao Tomori said:
If you get
Code:
FAILED (remote:
Unlock operation is not allowed
)
Just go to Developer Settings > OEM Unlocking and enable it.
I used PDAnet for Windows and it worked
Click to expand...
Click to collapse
Oh yes, I forgot about that! Thanks. Will add and credit you

hi there bro. i just want to know, is there a custom rom that we can use for this phone? i have the same exact phone but i cannot find any articles about any other custom roms that has been used on this phone. hoping to hear from you. thanks.
And another thing, can we use TWRP for this phone?

Hello. Is there anyone here who has a clean stock rom for Starmobile UP Prime? The phone keeps popping up ads and redirecting to chrome/google play. Contact names sometimes disappear too. I ran the malwarebytes app and it said that "Settings" app is the malware. I downloaded and flashed another rom before (I forgot from what website), but same experience. Hoping for helpful response.