[MOTOROLA ONE] About Multi-user increase over 5 accounts without rooting - Motorola One Questions & Answers

Hello guys, im facing this problem and maybe u all can help me,
actually i got motorola one (not power) and i noticed this function multi-user with up to 5 users isollated. so i wanna increase this number of accounts up to 10, i know its possible, but can i do it without rooting?
or if only rooting is possible, is there a way to unroot 100%? because some apps detect im rooting.
can i acess "build.pro" and edit it without rooting too?
i also own a samsung j7 prime and followed tutorial below and worked very well with a little downsides, its detectable by some apps including banks apps
Any help is welcome
https://forum.xda-developers.com/galaxy-j7/how-to/multi-user-samsung-galaxy-j7-j5-t3217939
Step 1. Open FileExplorer (Es file explorer, preferable)
Step 2. Go to "Device"
.
Search for "build.prop"
Edit and add the below string at the end of the editor and save and reboot !
fw.max_users=10
fw.show_multiuserui=1

You'll need root to edit build.prop.

Amaterasus said:
Hello guys, im facing this problem and maybe u all can help me,
actually i got motorola one (not power) and i noticed this function multi-user with up to 5 users isollated. so i wanna increase this number of accounts up to 10, i know its possible, but can i do it without rooting?
or if only rooting is possible, is there a way to unroot 100%? because some apps detect im rooting.
can i acess "build.pro" and edit it without rooting too?
i also own a samsung j7 prime and followed tutorial below and worked very well with a little downsides, its detectable by some apps including banks apps
Any help is welcome
https://forum.xda-developers.com/galaxy-j7/how-to/multi-user-samsung-galaxy-j7-j5-t3217939
Step 1. Open FileExplorer (Es file explorer, preferable)
Step 2. Go to "Device"
.
Search for "build.prop"
Edit and add the below string at the end of the editor and save and reboot !
fw.max_users=10
fw.show_multiuserui=1
Click to expand...
Click to collapse
Yes you need root to find build.prop. But you can extract build prop using adb pull location in twrp and edit it on PC, then reinstall firmware *DONT UNROOT VIA MAGISK ALMOST HARDBRICKED MY MOTO ONE* when your done reinstalling firmware then use adb push location build.prop

borksek said:
Yes you need root to find build.prop. But you can extract build prop using adb pull location in twrp and edit it on PC, then reinstall firmware *DONT UNROOT VIA MAGISK ALMOST HARDBRICKED MY MOTO ONE* when your done reinstalling firmware then use adb push location build.prop
Click to expand...
Click to collapse
"But you can extract build prop using adb pull location in twrp and edit it on PC, then reinstall firmware *DONT UNROOT VIA MAGISK ALMOST HARDBRICKED MY MOTO ONE* when your done reinstalling firmware then use adb push location build.prop"
With this method root is needed? is there any tutorial so i can follow your instruction and put it to work? i know how to use adb and insert commands at cmd.
Baseband: M8953_16.15.02.19R DEEN_LATAMDSDS_CUST
Product/Variant: DEEN XT1941-3 64GB PVT1

i found this firmware https://www.getdroidtips.com/motorola-one-android-pie-update/ , this one is the correct for my mobile. can i edit this rom (build.prop) and flash it to work with above 5 users? what you think?

with my searchs i found the pull push command, https://www.**********.com/push-pull-files-android-using-adb-commands/
so basically, run adb look for the build.prop and pull it to adb folder, edit the file into pc to 10 users (fw.max_users=10) save, adb push command and done, reboot? thats right ?

Amaterasus said:
"But you can extract build prop using adb pull location in twrp and edit it on PC, then reinstall firmware *DONT UNROOT VIA MAGISK ALMOST HARDBRICKED MY MOTO ONE* when your done reinstalling firmware then use adb push location build.prop"
With this method root is needed? is there any tutorial so i can follow your instruction and put it to work? i know how to use adb and insert commands at cmd.
Baseband: M8953_16.15.02.19R DEEN_LATAMDSDS_CUST
Product/Variant: DEEN XT1941-3 64GB PVT1
Click to expand...
Click to collapse
If your rooted, please search using es file explorer for build prop location since idk where it is located but I know the command

borksek said:
If your rooted, please search using es file explorer for build prop location since idk where it is located but I know the command
Click to expand...
Click to collapse
i dunno if its safe to root my mobile, is there a tutorial for my model? can be unrooted? if not using magisk?

Solved with pull/push command though adb.
@Close Request

Amaterasus said:
Solved with pull/push command though adb.
@Close Request
Click to expand...
Click to collapse
See if you wanna close the thread, report it as non-urgent then say close thread.

Thread closed by OP request

Related

[Q] Rooting WM8850 Android 4.0 Tablet

I've got a cheap Chinese tablet (WM8850-MID) running Android 4.0.3 based on WonderMedia 8850 processor.
It's not rooted.
Here's what i found:
/system/xbin/su is present:
-rwsr-xr-x 1 0 0 68528 May 14 11:07 su
But I can't run su in a terminal:
su uid 10064 not allowed to su
Using adb.exe I have the same problem with uid 2000.
There is a script /system/etc/init.sh which is called a boot time, but If I modify and push it via adb it won't execute (lost execute permission)
adb reboot-bootloader does reboot the device, but it does not stay in bootloader mode and just go straight to Android.
I'm not sure where to go from here. Is there a way to root that device ?
Try ./adb root to run as root.
Use oneclickroot.
Daniel120201 said:
Try ./adb root to run as root.
Use oneclickroot.
Click to expand...
Click to collapse
I forgot to mention "adb root" says I'm already root.
If I copy files with adb push, the owner is root, but If I use "adb shell" I'm user uid 2000.
This is a new tablet, but I'll give oneclick a try anyway. Thanks.
I've just tried SuperOneClick 2.3.1.0. It says it's already rooted because it can find /system/xbin/su, but I continued anyway. It can copy busybox (temp) but cannot change the permissions and it stops there.
Try resetting your tablet and if the su binary is stil there remove it. After resetting retry with superoneclick.
Sent from my MID7C using xda app-developers app
Daniel120201 said:
Try resetting your tablet and if the su binary is stil there remove it. After resetting retry with superoneclick.
Sent from my MID7C using xda app-developers app
Click to expand...
Click to collapse
Thanks, but how do I delete it since I don't have the permissions? In case it's possible, is it safe to remove the su binary? I have no way to recover my firmware...
Use ./adb root to remove it because you will be root.After removing it reset your tablet to factory settings. It is safe because the su binary is not part of the os.
Then try rooting with oneclickroot.
Hope it works for you.
i also bought wm8850 tablet in china..can you teach me how to root in detailed its my first android device....i dont understand the other terms u are using....
Hi jallaine12gil,
I think that you should first try to root with oneclickroot. Post if it worked or not. Oneclickroot is a rooting program for android devices.
download the firmware. then find the android4.0.tgz file open it with 7zip, add the su file to system/bin folder and system/xbin manually.... then put the superuser.apk in the system/app folder then save changes.... then flash firmware from sdcard
if camera is in the top centre of the wm8850 tablet: in txt file
if camera is in top right of the wm8850 tablet: in txt file
download the firmware. then find the android4.0.tgz file open it with 7zip, add the su file to system/bin folder and system/xbin manually.... then put the superuser.apk in the system/app folder then save changes.... then flash firmware from sdcard
Attachment is the links to firmwares
Hi i was brick my 8850 ekenw70 flashing this
WM8850_MID7_PuZhi_W01_8223_FT5206_W70_WMC1579
i was buy it here:
http://www.aliexpres...holesalers.html
can sugest something to debrick??
All what i have is one black screen, i try to reflash but no luck.
WM8850 RootBurner
How root the WM8850 tablet without firmware update :RootBurner on "nanospic.ro/?p=327" !
cnxsoft said:
I've just tried SuperOneClick 2.3.1.0. It says it's already rooted because it can find /system/xbin/su, but I continued anyway. It can copy busybox (temp) but cannot change the permissions and it stops there.
Click to expand...
Click to collapse
Hi friends,
I also used this device...any results ??...working or not ?..pls help guys..
Br
Zaki..
ellisondavid said:
download the firmware. then find the android4.0.tgz file open it with 7zip, add the su file to system/bin folder and system/xbin manually.... then put the superuser.apk in the system/app folder then save changes.... then flash firmware from sdcard
Attachment is the links to firmwares
Click to expand...
Click to collapse
Hi, friend
How to put manually ?? file read only!...any MOD..pls help..
RootBurner
basodiodoh said:
Hi, friend
How to put manually ?? file read only!...any MOD..pls help..
Click to expand...
Click to collapse
Hi!
why not use RootBurner for WM8850? The rooting procces is similary to firmware update!
Extract the archive into sd card and insert into tablet and Power ON!
ellisondavid said:
download the firmware. then find the android4.0.tgz file open it with 7zip, add the su file to system/bin folder and system/xbin manually.... then put the superuser.apk in the system/app folder then save changes.... then flash firmware from sdcard
Attachment is the links to firmwares
Click to expand...
Click to collapse
Hi, friend..this firmware compatible for version below??
Model Number : WM8850-mid
Build number : 4.0.3 ICS Ver. 1.2.0-20120824.044231
* camera - top right hand side*
Thanks.
How to get adb working on the wm8850?
Hi, sorry to interject with something semi-unrelated, but how did you guys get adb working with the wm8850? I've added the vendor id to the ~/.android/adb_usb.ini on mac, but adb still can't find the device. I used 0x0ea0, is this what you guys used?
Any advice would be great!
have the same tablet
i have the same tablet WM8850-mid ihave my rooted but i dont know haw to flash roms and what should i use CWM recovery version for this tablet pls help me thanks...
thank you XDA pls help..
how to root ??
MarionSabido said:
i have the same tablet WM8850-mid ihave my rooted but i dont know haw to flash roms and what should i use CWM recovery version for this tablet pls help me thanks...
thank you XDA pls help..
Click to expand...
Click to collapse
Hi, friend
Sorry, how do you root??

Can't Backup'ing EFS Partition

My phone lost his Imei after restoring to factory settings. I have root, and I was trying to do it because I have root so unrooted&wipe but after wipe my imei lost again, (once happened again, that time i sent it to service and came in good condition) but I found the EFS backup ing and editing with a hex editor will set things to order but even I have root and giving permissions to any program wont see SU.
Galaxy Toolbox prog. can't find any EFS and I could not be able to edit it. There is no Galaxytoolbox folder (or YGSxyz folder) in sdcard. And if I look with root explorers, there is no things in efs folder.
I mean to use this method but I do not have anything in my efs folder.
Any Ideas?
SweetyVolty said:
My phone lost his Imei after restoring to factory settings. I have root, and I was trying to do it because I have root so unrooted&wipe but after wipe my imei lost again, (once happened again, that time i sent it to service and came in good condition) but I found the EFS backup ing and editing with a hex editor will set things to order but even I have root and giving permissions to any program wont see SU.
Galaxy Toolbox prog. can't find any EFS and I could not be able to edit it. There is no Galaxytoolbox folder (or YGSxyz folder) in sdcard. And if I look with root explorers, there is no things in efs folder.
I mean to use this method but I do not have anything in my efs folder.
Any Ideas?
Click to expand...
Click to collapse
try to do this tutorial http://forum.xda-developers.com/showthread.php?t=1968360 there is a
guide with adb but you have to root youe device then for me it?s normal that root explorer doesn't see
efs partition for security i think and so you see that is empty...
flash stock kernel..u will get your imei back..works for me every time
Sent from my GT-S5830i using xda app-developers app
angel.sea said:
try to do this tutorial http://forum.xda-developers.com/showthread.php?t=1968360 there is a
guide with adb but you have to root youe device then for me it?s normal that root explorer doesn't see
efs partition for security i think and so you see that is empty...
Click to expand...
Click to collapse
My device is rooted and its giving permission to applications but applications can't read the given SU permission. Somehow weird situation, oh by the way my phone could not connect to wifi on by own, i have to enter values of my wifis parimeters of ip gateway etc. and I could not update SU binary.
srt99 I'm not a professional android user, not linux anyway, so I dont want to interact with changing roms because there is no Turkish rom in sammobile or any like (I do not use Turkish language on my phone, but still my guarantine is continue and will send if I could not make it. )
AW: Can't Backup'ing EFS Partition
SweetyVolty said:
I'm not a professional android user, not linux anyway, so I dont want to interact with changing roms because there is no Turkish rom in sammobile or any like (I do not use Turkish language on my phone, but still my guarantine is continue and will send if I could not make it. )
Click to expand...
Click to collapse
You don't have to be a professional, like everybody can do this. Just flash this through cwm and you have stock kernel again.
¿U mad bro¿
SweetyVolty said:
My phone lost his Imei after restoring to factory settings. I have root, and I was trying to do it because I have root so unrooted&wipe but after wipe my imei lost again, (once happened again, that time i sent it to service and came in good condition) but I found the EFS backup ing and editing with a hex editor will set things to order but even I have root and giving permissions to any program wont see SU.
Galaxy Toolbox prog. can't find any EFS and I could not be able to edit it. There is no Galaxytoolbox folder (or YGSxyz folder) in sdcard. And if I look with root explorers, there is no things in efs folder.
I mean to use this method but I do not have anything in my efs folder.
Any Ideas?
Click to expand...
Click to collapse
try this new script http://forum.xda-developers.com/showthread.php?t=2177118..bml15 is the partition that contain the imei
or write this code on terminal emulator
su press enter
busybox dd if=/dev/bml15 of=/sdcard/bml15.img press enter
a line at a time
and see the sd card try with hexeditor like the guide http://forum.xda-developers.com/show....php?t=1968360
Thanks for posting with this much helpful contains. But my device can not gain root acces even have the app superuser in main menu. I couldnt figure out why, while I'm trying to update binary it couldn't gain root access even given permission to superuser inself. Tried to install SuperSU from chainfire but it does not install it. even with ccw mod installer.
SweetyVolty said:
Thanks for posting with this much helpful contains. But my device can not gain root acces even have the app superuser in main menu. I couldnt figure out why, while I'm trying to update binary it couldn't gain root access even given permission to superuser inself. Tried to install SuperSU from chainfire but it does not install it. even with ccw mod installer.
Click to expand...
Click to collapse
you tried to do the Unroot with cwm and redo the root process?
if you type in terminal emulator su on what you said?
angel.sea said:
you tried to do the Unroot with cwm and redo the root process?
if you type in terminal emulator su on what you said?
Click to expand...
Click to collapse
Uhm i do with normal recovery mode, not with cwm. If I write "su" "$" changes to "#" but if I write "whoami" returns with this line "whoami: not found"
SweetyVolty said:
Uhm i do with normal recovery mode, not with cwm. If I write "su" "$" changes to "#" but if I write "whoami" returns with this line "whoami: not found"
Click to expand...
Click to collapse
what is whoami?
so if with su changes with # you are in root.....so try the command that wrote before for bml15
and to upgrade su bin try super user fix by chainsdd in playstore if forse fix then you have to remove the battery
angel.sea said:
what is whoami?
so if with su changes with # you are in root.....so try the command that wrote before for bml15
and to upgrade su bin try super user fix by chainsdd in playstore if forse fix then you have to remove the battery
Click to expand...
Click to collapse
whoami - who am i
However, this is used on Linux to check the username of the User
It is useless for s5830i
If your phone gets #
Then it's rooted
Try my Tool In Development section for backing up EFS partition
angel.sea said:
what is whoami?
so if with su changes with # you are in root.....so try the command that wrote before for bml15
and to upgrade su bin try super user fix by chainsdd in playstore if forse fix then you have to remove the battery
Click to expand...
Click to collapse
Yes i have the bml15 and when open it with hex editor at line 0x80000 I can see my imei number, what should I do now?
dd if=/sdcard/bml15.img of=/dev/block/bml15 line prints "dd: not found" how ever, the opposite command token the bml15.img to sd card.
SweetyVolty said:
Yes i have the bml15 and when open it with hex editor at line 0x80000 I can see my imei number, what should I do now?
dd if=/sdcard/bml15.img of=/dev/block/bml15 line prints "dd: not found" how ever, the opposite command token the bml15.img to sd card.
Click to expand...
Click to collapse
if you can see your emei that's a problem of incompatibility between your firmware....but you had installed cronemode's scripts?
try to reflash stock kernel and will see that your emei wiill come back....LINK [STOCK KERNEL] ----- http://www.mediafire.com/?8amfqkqq28v1h9f
stock kernel modules ---- http://www.mediafire.com/?7tckgiclaq80aoc
flash with cwm that take from this thread http://forum.xda-developers.com/showthread.php?t=1551156
angel.sea said:
if you can see your emei that's a problem of incompatibility between your firmware....but you had installed cronemode's scripts
Click to expand...
Click to collapse
Hm.. My firmware is in its orginal state, I only rooted my phone and OS started to flikering so I decided to wipe data, delvik clean cache wipe etc. after that my imei is became unknown...
Edit: I didnt install any scripts, or cronemode?
SweetyVolty said:
Hm.. My firmware is in its orginal state, I only rooted my phone and OS started to flikering so I decided to wipe data, delvik clean cache wipe etc. after that my imei is became unknown...
Edit: I didnt install any scripts, or cronemode?
Click to expand...
Click to collapse
try to use the file of this thread http://forum.xda-developers.com/show....php?t=1551156 to unroot and root then reflash stock kernel that there were a mistake in os
your rom will be the same....try and tell me if work fine...for me work fine
no you have to use a little apk bmlunlock and then to use the command to mount the partition or viceversa and then
busybox dd if=/sdcard/bml15.img of=/dev/block/bml15 but i don t remember if you have to use chmod command also
My dear sir, I have complated my mission with odin and lastest sammobile rom. Thank you all for your greatest effords and helps. :angel:
SweetyVolty said:
My dear sir, I have complated my mission with odin and lastest sammobile rom. Thank you all for your greatest effords and helps. :angel:
Click to expand...
Click to collapse
iM happy to you....
I have a weird problem
I tried restoring IMEI with every possible method
But it didn't get restored
Even flashed stock firmware
Didn't help
Though after some retries, I was able to restore it back but then too, I disappears after some reboots
iamareebjamal said:
I have a weird problem
I tried restoring IMEI with every possible method
But it didn't get restored
Even flashed stock firmware
Didn't help
Though after some retries, I was able to restore it back but then too, I disappears after some reboots
Click to expand...
Click to collapse
Using any cronmod scripts?
Sent from my GT-S5830i using xda premium
uchihachi said:
Using any cronmod scripts?
Sent from my GT-S5830i using xda premium
Click to expand...
Click to collapse
Yes
But I was using them for last 5 months without a problem

[Q] How can i install the settings apk

I deleted the settings and i cant install this. Please help me
otalha12 said:
I deleted the settings and i cant install this. Please help me
Click to expand...
Click to collapse
setting.apk is part of system, you can't delete it(except you rooted), and you can't install it like other normal apk.
i suggest you to back to your stock rom, and delete anything if you don't know what's the function.
Quick workaround, look for adb (android debug bridge) on google.
Basically, you need to extract the settings.apk from another rom/firmware of the same version as yours and use adb shell to push it to system/app adress with rw-r-r permissions. (Alternatively, use a root explorer to put it there).
The other solution is to flash a stock firmware with the corresponding flash tool.
Good luck

[TUTORIAL] How to FULLY root China Variants MATE 2 on 4.4.2

DISCLAIMER : You attempt the following at your own risk !
I'm not responsible if your phone blows up, bricks, you travel back in time or go bald or something!
Background :
I have the MT2-L05 Mate 2 from China.
When I received my Mate 2 last Thursday, the phone was on 4.2.2
After much hunting and downloading and flashing of ROMS, I managed to finally update to 4.4.2 KitKat.
Great ! I was happy. But I didn't have root access.
After trying and failing to use the various bootloader unlock tools on these forums, I Emailed Huawei, and politely asked them if I could have the 16 digit code for my Mate 2. An hour later an Email arrived with my bootloader unlock code, so I fastbooted, used the code and unlocked the Bootloader.....Cool ! Thanks Huawei, great customer service.
I then went to root my phone, and here the problems started. I tried at least 20 different Root tools, both via phone and over the pc, but no joy.
Nothing worked ! Vroot, Kingoroot, Towelroot, srs root, root genius 1.8.7, etc they all failed.
I was at the point of giving up, when I found a Chinese version of rootgenius 2.0.1.3......I ran it via pc........and Success ! I was finally rooted.
Supersu was installed, the binaries updated fine and all was good with the world. I tried wakelock detector first ( Yeah, I know, I REALLY need more battery life from the Mate 2 ! ), and Supersu asked for permission and it worked no problem.
I then tried to install adaway, and then I ran into problems, I was unable to edit my hosts file....ummm...odd. OK, then I tried to install xposed......Impossible to install.
I then read on these forums to edit build.prop and change a simple setting to get xposed running.......ok, no problem, yet when I edited my build.prop file, it would NEVER EVER save the edits. Weird? what's going on?.......after much searching and much reading I finally found the problem.................
Root Genius 2.0.1.3 :
http://www.shuame.com/root/
The Problem :
The 4.4.2 update adds a file to your System folder called :
set_immutable.list
this file contains :
Code:
/system/bin
/system/build.prop
/system/etc
/system/fonts
/system/framework
/system/isp.bin
/system/lib
/system/ons.bin
/system/usr
/system/vendor
/system/xbin
/system/app/HwLauncher6.apk
/system/app/HwLauncher6.odex
/system/app/systemUI.apk
/system/app/systemUI.odex
Any location listed above is IMPOSSIBE to mount as rw. Every file explorer or emulator you try will tell you it is rw, but it's not.
It's locked down completely...................and it's REALLY annoying.
This is why I could never edit my build.prop or Install Adaway etc..................
But I found a solution...... ( I think ! )..........
The Solution :
I spent the afternoon at work using google translate to find a fix for my problem and found a post from a guy called :
**** wire His Royal Highness Prince czx ( I cannot post the first 4 letters as it will probably be banned....It must be a Google translate error but it made me laugh ! )
His guide never worked for me until I made a few edits and added STEP 4. Then I got it to work.
The Solution :
1, First Root your Phone ( I suggest trying Root Genius 2.0.1.3 from my first post )
2, install busybox (I suggest BusyBox ( Stericson ) as I couldn't get this to work with the Jrummy BusyBox installer )
3, Install Rom Toolbox Pro ( I know it's payware and I tried other programs, but this is the only one that worked for me. I had already purchased ages ago. The free version may contain the following tools too, but I genuinely don't know )
4, open Scripter from Rom Toolbox pro and click " Mount System R/W "
5, open Terminal Emulator from Rom Toolbox Pro
Type: su then press enter
Type: mount -o rw, remount / system then press enter
Type: cd system then press enter
Type: chattr -R -i * then press enter
(On step 5 there is a space between remount forward slash and system and also between i and *)
6, Leave Terminal Emulator open, Hit your Home Button
7, then delete the file :system / set_immutable.list with Root Explorer. Other File managers with root access may work, I haven't tried
If you can not delete it, the above steps haven't worked, I can only suggest you try from step 4 after rebooting your phone.
If you are successful and manage to delete the set_immutable.list file then reboot your phone.
Job Done !
You now have full Root Access.
This has been tested by myself on my MT2-L05, it should work on ALL China Variants and presumably on the US MT2-L03 if this file is included in a 4.4.2 update, but I obviously cannot guarantee this.
I'm also curious as to whether anyone thinks this has left my phone open to exploits by the deleting this file....? Remember, if I have done something stupid by doing this, then so will you if you follow the above!
All I know is Xposed has installed perfectly after finally being able to edit my build.prop file and Adaway is running like a charm.
Feedback very welcome.
4L0M said:
The Solution :
Snip
5, open Terminal Emulator from Rom Toolbox Pro
Type: su then press enter
Type: mount -o rw, remount / system then press enter
Type: cd system then press enter
Type: chattr -R -i * then press enter
(On step 5 there is a space between remount forward slash and system and also between i and *)
Snip
Click to expand...
Click to collapse
I followed your guide, the part I bolded didn't seem to work for me, but after a few attempts I just kept going with the rest of the guide and I was still able to delete the file at the end of the day Thank you so much! I always felt like the root I had with 4.2 was kind of a pseudo root since I was limited by my root access, this is exactly what I needed!
I manage to get root and delete that file. Hooray and thanks! But after editing the build.prop, I still can't get xposed to install. I keep getting this error on the install screen.
scpion said:
I manage to get root and delete that file. Hooray and thanks! But after editing the build.prop, I still can't get xposed to install. I keep getting this error on the install screen.
Click to expand...
Click to collapse
Install xposed 2.5.1, it's the safest option for now and you will not get this error message.
I haven't tried too many xposed apps yet, but wanam works if you want circle battery etc
Experimental features of Greenify work too.
Gravity box Kitkat will not run properly for me.. I suggest you do not attempt to install it at the moment.
Let me know if you find anymore cool xposed modules to try!
4L0M said:
Install xposed 2.5.1, it's the safest option for now and you will not get this error message.
I haven't tried too many xposed apps yet, but wanam works if you want circle battery etc
Experimental features of Greenify work too.
Gravity box Kitkat will not run properly for me.. I suggest you do not attempt to install it at the moment.
Let me know if you find anymore cool xposed modules to try!
Click to expand...
Click to collapse
Thanks dude. Btw does your device support Google search by swiping up from home?
scpion said:
I manage to get root and delete that file. Hooray and thanks! But after editing the build.prop, I still can't get xposed to install. I keep getting this error on the install screen.
Click to expand...
Click to collapse
Same issue for me
janrck said:
Same issue for me
Click to expand...
Click to collapse
Install xposed 2.5.1, it's the safest option for now and you will not get this error message.
Cool xposed apps for 2.5.1 :
wanam kit : adds circle battery, expanded notifications, 4-way reboot menu etc etc
Android L Navbar : adds Android L navbar and Android L shapes Navbar
Both work flawlessly for me and have NEVER crashed once.
Hi, I followed your steps but in the step 5, when i type this : mount -o rw, remount / system it doesnt work.
4L0M said:
DISCLAIMER : You attempt the following at your own risk !
Nothing worked ! Vroot, Kingoroot, Towelroot, srs root, root genius 1.8.7, etc they all failed.
I was at the point of giving up, when I found a Chinese version of rootgenius 2.0.1.3......I ran it via pc........and Success ! I was finally rooted.
Supersu was installed, the binaries updated fine
I then tried to install adaway, and then I ran into problems, I was unable to edit my hosts file....ummm...odd. OK, then I tried to install xposed......Impossible to install.
Click to expand...
Click to collapse
I then read on these forums to edit build.prop and change a simple setting to get xposed running.......ok, no problem, yet when I edited my build.prop file, it would NEVER EVER save the edits. Weird? what's going on?.......after much searching and much reading I finally found the problem.................
/QUOTE]
How was SU installed if you had no rw privs?
vroot, kingroot, kingoroot, kinguser, srs root and rootgenius were created for a select few... it was a side effect of massive social engineering via the internet that they'd leak to so many others who weren't the target.
magicpromise said:
I then read on these forums to edit build.prop and change a simple setting to get xposed running.......ok, no problem, yet when I edited my build.prop file, it would NEVER EVER save the edits. Weird? what's going on?.......after much searching and much reading I finally found the problem.................
/QUOTE]
How was SU installed if you had no rw privs?
vroot, kingroot, kingoroot, kinguser, srs root and rootgenius were created for a select few... it was a side effect of massive social engineering via the internet that they'd leak to so many others who weren't the target.
Click to expand...
Click to collapse
I'm guessing because I could write rw to system folder. Set-immutable-list blocks folders inside system folder, not the basic system folder itself. ie/ system/xbin or system/etc they are blocked. /system on its own isn't.
4L0M said:
I'm guessing because I could write rw to system folder. Set-immutable-list blocks folders inside system folder, not the basic system folder itself. ie/ system/xbin or system/etc they are blocked. /system on its own isn't.
Click to expand...
Click to collapse
yes, and the instructions worked great.
i made a script with it in totalrom and set it to load on boot along with total rom itself to keep a strangle hold on the permissions.
magicpromise said:
yes, and the instructions worked great.
i made a script with it in totalrom and set it to load on boot along with total rom itself to keep a strangle hold on the permissions.
Click to expand...
Click to collapse
Can you please upload the script you made?
You'll make things easy for me, 'cause commands in terminal don't seem to work in my case.
Thank's !

Delete please

This thread is now defunct. I have moved to iPhone. Sorry about this.
Take care everybody.
Regards,
Magnetox
Appreciate this! If I'm already unlocked, is it possible to remove the -w in the flash-all script before running for a rooted install without wiping user data?
Wi1son said:
Appreciate this! If I'm already unlocked, is it possible to remove the -w in the flash-all script before running for a rooted install without wiping user data?
Click to expand...
Click to collapse
I would leave it as is, but if you want to try it, go ahead (might brick).
Hi ! Thanks for it.
Just a question After flash the Rom when the phone reboot before copy magisk manager can restore my Google backup ?
And how I do when they had an update ?
Thanks
ggkameleon said:
Hi ! Thanks for it.
Just a question After flash the Rom when the phone reboot before copy magisk manager can restore my Google backup ?
And how I do when they had an update ?
Thanks
Click to expand...
Click to collapse
Yes that should be fine. Just restore normally. But don't forget magisk otherwise it won't have proper root.
Might be a silly question, but, does this stock image work with Google Fi?
Also, a little confused with some of the directions...
In step 1 it says "Download the appropriate rar package for your system and install."
Does this mean download my stock image from Google and install it with Magisk, or... ?
In step 9 it says, " Once in fastboot, and the bootloader, run "fastboot devices" from the "BRAMBLE" folder. "
Does this mean to run "fastboot devices" as a command inside the command prompt from the "BRAMBLE" folder or to open one of the tools inside the platform tools folder?
Also, in step 11, where do I find the "appropriate flash-all command on your operating system"?
These are just a bit confusing to me. Don't want to brick my phone, so any help is appreciated.
Thanks
SpecialKCF22 said:
Also, a little confused with some of the directions...
...
Thanks
Click to expand...
Click to collapse
Download the WinRAR package in the mega.nz folder for your OS.
Both, platform tools should be in that BRAMBLE folder. Example fastboot.exe should be in BRAMBLE.
You will find this in your BRAMBLE folder when you properly extract platform tools and the .rar into the BRAMBLE folder.
SpecialKCF22 said:
Might be a silly question, but, does this stock image work with Google Fi?
Click to expand...
Click to collapse
It's just stock with root, so if the Pixel 4a 5g works normally it will too.
Magnetox said:
Download the WinRAR package in the mega.nz folder for your OS.
Both, platform tools should be in that BRAMBLE folder. Example fastboot.exe should be in BRAMBLE.
You will find this in your BRAMBLE folder when you properly extract platform tools and the .rar into the BRAMBLE folder.
Click to expand...
Click to collapse
You're not very detailed and you didn't answer the questions. I'll pass on this method. Thanks
SpecialKCF22 said:
You're not very detailed and you didn't answer the questions. I'll pass on this method. Thanks
Click to expand...
Click to collapse
Feel free to PM
Magnetox said:
Yes that should be fine. Just restore normally. But don't forget magisk otherwise it won't have proper root.
Click to expand...
Click to collapse
So, will update delete the magisk app? Or what do you mean when write "don't forget magisk"?
Ryav said:
So, will update delete the magisk app? Or what do you mean when write "don't forget magisk"?
Click to expand...
Click to collapse
I mean don't forget to install it and assure you have proper root after.
Does this one works with Google pay. My rooted build of RD1A.200810.022.A4 doesn't pass the safety check on magisk manager. Thank you
imFonk said:
Does this one works with Google pay. My rooted build of RD1A.200810.022.A4 doesn't pass the safety check on magisk manager. Thank you
Click to expand...
Click to collapse
MAGISK MODULE ❯ Universal SafetyNet Fix 1.1.0
Thanks for this! FYI for anyone curious the newest Magisk 8.07 does work, you don't need to use the linked file.
dadozer said:
Thanks for this! FYI for anyone curious the newest Magisk 8.07 does work, you don't need to use the linked file.
Click to expand...
Click to collapse
Yes feel free to do this. The APK that is linked works fine as well and will update itself with your permission.
Magnetox said:
Hey everybody,
Here is the latest Android 11 January 2021 update rooted (I will keep it updated). It's all clean. It is the Google stock system image with root applied (comes with GAPPS). You can cleanly flash your device with this as long as your fastboot (bootloader) is working.
Download LINK:
File folder on MEGA
mega.nz
Steps:
1) Download the appropriate rar package for your system and install.
2) Download the appropriate platform-tools package for your operating system (this contains ADB and Fastboot) and extract it in a folder we'll call "BRAMBLE" (we will use this folder for the install).
3) Download the bramble-rq1a.210105.003.rar file (this is the stock rom). Extract it to the "BRAMBLE" folder. You will want to see all the files (ie. the flash-all.sh) all in the folder the same folder that contains the ADB and Fastboot tools.
4) Download MagiskManager-v8.0.4.apk, this will be used after the install and installed on the device.
5) Enable USB debugging and OEM unlocking (the bootloader unlock) in developer options (smash on build a bunch of times in a row real fast to enable developer options in about phone).
7) Navigate to the "BRAMBLE" folder with a terminal or command prompt (depending on your operating system) and run "adb devices" with root or administrator access in your terminal or command prompt on your computer (respectively there). Allow the USB debugging to connect to your computer forever on your phone, something should pop up. It should appear in the terminal or command prompt. If not you need to accept USB debugging on your phone (forever).
8) Put in the command "adb reboot bootloader" once your device appears.
9) Once in fastboot, and the bootloader, run "fastboot devices" from the "BRAMBLE" folder. This should return your device. If not, something is wrong and restart. Another way of reaching fastboot is restarting your phone and holding VOLUME DOWN.
10) Make sure your device is unlocked, run "fastboot flashing unlock".
11) In the "BRAMBLE" folder, run the appropriate flash-all command on your operating system. This will take a while and completely reflash the system with the Stock ROM with root. You will see the progress as it appears.
12) Once it's done, your phone will reboot. Just wait for it to start up and do as you normally would on a new flash.
13) Move the MagiskManager-v8.0.4.apk onto the phone, and install it. It will confirm you have partial root and ask you to apply something more and reboot. Do so.
14) When rebooted, your phone will be fully flashed and rooted. Feel free to download a root verification app, I recommend this one. It should be working fine. Grant root permission forever to it.
If you have any questions, feel free to ask. You can install the ElementalX kernel on this rom for Pixel 4a 5g. Download this. It's a great kernel tool and it will help you with full root access download and install the kernel. It's the kernel I'm using.
Regards,
Magnetox
Click to expand...
Click to collapse
i could not install magisk, the 13th step in your guide might not be complete.
i managed to root, and got to pass safety net, and google pay working.
i have to move the boot.img from the zip file included in the package you provided, move it to internal storage, patch it in magisk manager.
then i moved the patched boot.img to my pc, did adb reboot bootloader, then fastboot flash [patched boot.img] and then only i was fully rooted.
i also flash the safetynet-fix-v1.1.1.zip module in magisk to pass satefynet.
hope it could help out, i digged all night yesterday to get this done lol.
MegaJuif said:
i could not install magisk, the 13th step in your guide might not be complete.
i managed to root, and got to pass safety net, and google pay working.
i have to move the boot.img from the zip file included in the package you provided, move it to internal storage, patch it in magisk manager.
then i moved the patched boot.img to my pc, did adb reboot bootloader, then fastboot flash [patched boot.img] and then only i was fully rooted.
i also flash the safetynet-fix-v1.1.1.zip module in magisk to pass satefynet.
hope it could help out, i digged all night yesterday to get this done lol.
Click to expand...
Click to collapse
I updated it with the latest 8.0.7 magisk. Hope this fixes it. (Uploading now)
Upload complete! (Magisk 8.0.7)

Categories

Resources