Related
I DO NOT TAKE CREDIT FOR THE WORK. I ONLY TRANSLATED THE SCRIPTS TO ENGLISH .
I AM NOT RESPONSIBLE IF YOU BRICK OR BREAK YOUR FUJITSU.
I have managed to find a bat file which will allow you to root your F-02E japanese phone.
I have also found a script to allow system R/W made by kikuhare
Steps Involved:
Make sure your phone has 100% charge.
Download the Root + System Mount
Extract the zip's to different folders.
Enable USB debugging under Menu > Settings > Developer Options.
Point to the folder where you extracted drivers from "usb_driver_F-02E_1.0.zip". Wait for drivers to install.
Make sure the phone is connected as PTP not MTP.
CMD into the folder "f-02e_oneclick_su_installer". It is inside the "Root + System Mount_1" files folder.
Run the runme.bat.
Download "Root Checker by joeykrim" from the Play Store.
Run the "Root Checker" app
Wait for the process to finish.
UPDATE System R/W
Connect phone to computer
Download the System Read Write Mounter_1.zip <<<<<< Only need to download if you did not download the "Root + System Mount_1.zip" file.
CMD into the "F-02E_system-mounter" It is inside the "Root + System Mount_1" files folder.
Extract the file and run the"START.bat"
Run everytime the system restarts to mount system as R/W.
Enjoy root .
NOTE: This method does not give full root permissions. You will still be able to underclock the CPU to some degree and use the CoreControl app to disable cores. I will have to run start.bat inside F-02E_system-mounter folder everytime the phone restarts to get system R/W
Drivers: usb_driver_F-02E_1.0.zip
Root Includes System Mount: Root + System Mount_1.zip
System R/W Mounter: System Read Write Mounter_1.zip
Screenshots:
Feel free to ask questions.
anaschillin said:
Hi, I have managed to find a bat file which will allow you to root your F-02E japanese phone. I do NOT take CREDIT for the work. I have merely found the zip. I have tested it and it works. I AM NOT RESPONSIBLE IF YOU BRICK OR BREAK YOUR FUJITSU.
Steps Involved:
Make sure your phone has 100% charge.
Extract the zip's to different folders.
Enable USB debugging under Menu > Settings > Developer Options.
Point to the folder where you extracted drivers from usb_driver_F-02E_1.0.zip. Wait for drivers to install.
CMD into the folder where you extracted the f-02e_oneclick_su_installer.zip files.
Run the runme.bat.
Download RootChecker from the Play Store. https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en
Reboot the phone.
Run the RootChecker app
Wait for te process to finish.
Enjoy root .
NOTE: This method does not give full root permissions. You will still be able to underclock the CPU to some degree and use the CoreControl app to disable cores.
Drivers:
http://www.4shared.com/zip/kGmw0Suu/usb_driver_F-02E_10.html?
Root: http://www.4shared.com/zip/D90h9kH2/f-02e_oneclick_su_installer.html?
Feel free to ask questions.
Click to expand...
Click to collapse
I havent even got the phone yet but are there any custom roms that work on this phone? Thanks
the-blind-bandit said:
I havent even got the phone yet but are there any custom roms that work on this phone? Thanks
Click to expand...
Click to collapse
No, not enough developers and interest for the phone outside Japan. I doubt anyone will be willing to put in effort as well
Oh well, but it is a very good phone, i think ill still get it though. I just wanted to know is half of it in Chinese even if you select english, i just heard this on youtube about another one of fujitsu's phones?
Sent from my Xperia T
the-blind-bandit said:
Oh well, but it is a very good phone, i think ill still get it though. I just wanted to know is half of it in Chinese even if you select english, i just heard this on youtube about another one of fujitsu's phones?
Sent from my Xperia T
Click to expand...
Click to collapse
Only Docomo and Fujistu apps are in Japanese. Everything else is in English.
Thats fine i suppose with root explorer i can delete those apps by deleting the apk in system app? Also if you have xposed app settings you can change the language per app would that also work?
Sent from my Xperia T
the-blind-bandit said:
Thats fine i suppose with root explorer i can delete those apps by deleting the apk in system app? Also if you have xposed app settings you can change the language per app would that also work?
Sent from my Xperia T
Click to expand...
Click to collapse
I have just frozen them, just incase if the phone needs the at somepoint. Xposed framework doesnt work as it need system R/W and the root method has not allowed system R/W mainly because the phone bootloader not unlocked. Secondly make sure you do not uninstall/disable the Phonebook and Phonebook Service provided by Docomo. Its key to allowing you to add and sync contacts.
So Xposed wont work at all then, thats a shame what about lucky patcher, does that need R/W?
Sent from my Xperia T
Improved the .bat file. Now you will have system R/W
Download the root file again and run it. Follow the steps starting at 10 if you have already rooted. :good:
Thanks
Sent from my Xperia T
anyone else besides the OP got their f02 rooted with this?
I may not be able to help any further. I have boot looped my phone. I cannot get it past the NTT Docomo screen. I think I know what is causing it but I cannot get the phone connected to the PC. I may need to send it into Fujitsu.
Good luck on fixing it
Sent from my Xperia T
I tried the following OP method didnt work for me
Thank! i just got the F-02e today. will try to root it.
btw, have you overcome a heating and self-shutting off prob on this phone?
anaschillin said:
Hi, I have managed to find a bat file which will allow you to root your F-02E japanese phone. I do NOT take CREDIT for the work. I have merely found the zip. I have tested it and it works. I AM NOT RESPONSIBLE IF YOU BRICK OR BREAK YOUR FUJITSU.
Steps Involved:
Make sure your phone has 100% charge.
Extract the zip's to different folders.
Enable USB debugging under Menu > Settings > Developer Options.
Point to the folder where you extracted drivers from usb_driver_F-02E_1.0.zip. Wait for drivers to install.
CMD into the folder where you extracted the f-02e_oneclick_su_installer-improved.zip files.
Run the runme.bat.
Download RootChecker from the Play Store. https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en
Run the RootChecker app
Wait for the process to finish.
UPDATE
Download ES File Explorer. Run it.
Press Menu then scroll down the list and click Root Explore.
Change the directory to root. (Meaning where you can see all system folders)
Look for system and hold the folder, then press more then properties.
Press Change in permissions.
Tick all the boxes at the bottom.
Enjoy root .
NOTE: This method does not give full root permissions. You will still be able to underclock the CPU to some degree and use the CoreControl app to disable cores. I have not been able to mount system as R/W and I had trouble installing BusyBox.
Drivers: usb_driver_F-02E_1.0.zip
Root: f-02e_oneclick_su_installer-improved.zip
Screenshots:
Feel free to ask questions.
Click to expand...
Click to collapse
anaschillin said:
I may not be able to help any further. I have boot looped my phone. I cannot get it past the NTT Docomo screen. I think I know what is causing it but I cannot get the phone connected to the PC. I may need to send it into Fujitsu.
Click to expand...
Click to collapse
i hope they can fix it immedietly, only you have work for this device (i hope any other)
question:
anyone have a stock rom for this device? may show me that's link?
Click to expand...
Click to collapse
Hi I am in the same situation, uninstall many applications in Japanese that I have the phone now in its box sirbe not all, send email to the seller took days with him and a solution is supposedly looking for me if I were to fix it passeth forums or sbrire a new post with the solution that would not be other than the original rom flaseo greetings
GattacaWroclaw said:
Hi I am in the same situation, uninstall many applications in Japanese that I have the phone now in its box sirbe not all, send email to the seller took days with him and a solution is supposedly looking for me if I were to fix it passeth forums or sbrire a new post with the solution that would not be other than the original rom flaseo greetings
Click to expand...
Click to collapse
You can reset the factory settings. Reboot the phone and hold the volume up, the phone will boot into recovery mode. You will be able to do a factory recovery.
armei said:
Thank! i just got the F-02e today. will try to root it.
btw, have you overcome a heating and self-shutting off prob on this phone?
Click to expand...
Click to collapse
I have not been able to overcome the issue. It is a design issue. Because it is waterproof phone the heat cannot disperse.
The only thing I have been able to do is keep the CPU frequency down to lower the time it takes for the phone to heat up.
garynsa said:
I tried the following OP method didnt work for me
Click to expand...
Click to collapse
What does it, when you run the root file?
Could you also tell your build number. Is it VR17xxx or VR16xxx?
Hi friends;
I have HTC M8 Marshmallow with Sense 7.
I rooted my device with SuperSU 2.65.
But;
I can't edit build.prob file in system folder.
I can't put apk and lib files to system->priv-app folder.
In fact ;
I edited build.prob file in system folder. (I used Root Explorer)
I put apk and lib files to system->priv-app folder.
But, after I rebooted device edited build.prob file returned original and
deleted apk and lib file that I put to system->priv-app folder.
Before these applications I mounted system folder R/W
Why did this happen?
How can i solve this?
musti35 said:
Hi friends;
I have HTC M8 Marshmallow with Sense 7.
I rooted my device with SuperSU 2.65.
But;
I can't edit build.prob file in system folder.
I can't put apk and lib files to system->priv-app folder.
In fact ;
I edited build.prob file in system folder. (I used Root Explorer)
I put apk and lib files to system->priv-app folder.
But, after I rebooted device edited build.prob file returned original and
deleted apk and lib file that I put to system->priv-app folder.
Before these applications I mounted system folder R/W
Why did this happen?
How can i solve this?
Click to expand...
Click to collapse
Flash disable WP mod. http://forum.xda-developers.com/attachment.php?attachmentid=3564071&d=1449168286
Thank you very much.
Now everything is OK
musti35 said:
Thank you very much.
Now everything is OK
Click to expand...
Click to collapse
Add [SOLVED] to the title, so that other people can find this solution.
Imotep95 said:
Flash disable WP mod. http://forum.xda-developers.com/attachment.php?attachmentid=3564071&d=1449168286
Click to expand...
Click to collapse
I got same problem...Can I get this zip for HTC Desire 630 phone plzzz....
skshakeel said:
I got same problem...Can I get this zip for HTC Desire 630 phone plzzz....
Click to expand...
Click to collapse
Because super su is system less root, you won't be able to edit the system files. I don't even know how that mod worked
Sent from my htc_m8 using XDA Labs
justinchao740 said:
Because super su is system less root, you won't be able to edit the system files. I don't even know how that mod worked
Click to expand...
Click to collapse
You can't edit system files while your device s-on,you need wp module or custom kernel with wp module to edit system
Some m8 roms have this module implemented ( if not all roms )
Sent from my HTC M8 using XDA Labs
skshakeel said:
I got same problem...Can I get this zip for HTC Desire 630 phone plzzz....
Click to expand...
Click to collapse
Hi
Earlier i see a post by @ckpv5 about adb manager Qtadb i can't find the post right now ( on mobile and it's hard to find )
https://qtadb.wordpress.com/download/
You can use this tool to remove system files
Reboot to twrp and mount system then connect the device with pc ( usb ) and start the tool from your pc
Give it a try
Sent from my HTC M8 using XDA Labs
justinchao740 said:
Because super su is system less root, you won't be able to edit the system files. I don't even know how that mod worked
Click to expand...
Click to collapse
You've got it wrong. Systemless root isn't the reason system is not writable. The same will occur with traditional root.
The system is write protected on this device (regardless of root method). You need the kernel mode to disable the write protection.
redpoint73 said:
You've got it wrong. Systemless root isn't the reason system is not writable. The same will occur with traditional root.
The system is write protected on this device (regardless of root method). You need the kernel mode to disable the write protection.
Click to expand...
Click to collapse
well thats what happened to me. I rooted with super su, it won't let me edit any build.prop or system files. But after i rooted with system root, it worked
Hi need help
Same problem in my device my device is not in too development
So I try to find solution on Google and find this thread..
Can I flash this file in my device my device is HTC desire 630 and also running in mm version.
So can I try to flash this file...???
vaibhav1 said:
Same problem in my device my device is not in too development
So I try to find solution on Google and find this thread..
Can I flash this file in my device my device is HTC desire 630 and also running in mm version.
So can I try to flash this file...???
Click to expand...
Click to collapse
No, it won't work. Kernels (and therefore kernel mods) are device specific. It won't work, and may harm your phone.
If the phone is rooted, you can try to mount system in a file explorer app, and apply the desired changes, to see if they stick (survive a reboot). Some folks have had success with that approach.
Be careful, and backup files accordingly. Or otherwise know how to return to stock, if anything goes wrong. Changes to system under root can result in unpredicted problems.
Further than that, I probably can't help; as I have no specific knowledge of your device.
redpoint73 said:
No, it won't work. Kernels (and therefore kernel mods) are device specific. It won't work, and may harm your phone.
If the phone is rooted, you can try to mount system in a file explorer app, and apply the desired changes, to see if they stick (survive a reboot). Some folks have had success with that approach.
Be careful, and backup files accordingly. Or otherwise know how to return to stock, if anything goes wrong. Changes to system under root can result in unpredicted problems.
Further than that, I probably can't help; as I have no specific knowledge of your device.
Click to expand...
Click to collapse
I try script but not working..
Thanks for you help
THIS IS NOT FOR FAINT OF HEART. DON'T BLAME ME IF YOU BREAK SOMETHING.
Mount system as RW in TWRP. (this took mounting, unmounting, then remounting for me)
Use the following commands CAREFULLY from a computer.
cat /system/build.prop > /sdcard/build.prop
Open the build.prop from the sdcard and edit the following line numbers: 25, 26
You are changing:
ro.product.name=perseus
ro.product.device=perseus
To this:
ro.product.name=perseus_global
ro.product.device=perseus_global
save the file on the sdcard
Go back to ADB session and do this:
cat /sdcard/build.prop > /system/build.prop
IF THIS FAILS YOUR SYSTEM IS NOT RW, UNMOUNT AND REMOUNT IN THE MOUNTS MENU.
Go back to the mounts menu and unmount /system
Flash Magisk 17.3 (18.0 seems to be having intermittent issues with passing checks)
Reboot, and enjoy your CN device running Global with ROOT.
out-file : Could not find a part of the path 'C:\sdcard\build.prop'.
I got that error above. How do i know twrp mounted system correctly?
nvm... i went into advance and did via terminal
Great find, works!!
Thanks!!
You're welcome. I may try to make a flashable zip to do this automatically, but I haven't had a chance to look at it.
Work so well, Thanks @PWn3R!
xterminater07 said:
out-file : Could not find a part of the path 'C:\sdcard\build.prop'.
I got that error above. How do i know twrp mounted system correctly?
nvm... i went into advance and did via terminal
Click to expand...
Click to collapse
Here is the clue. " 'C:\sdcard\build.prop'."
What is a Windows drive letter doing on an Android? Adb session?
@PWn3R YOU ARE THE MAN
Has anyone tried a custom kernel on the latest global? I tried androplus v 0.6 and it didnt really work. It allows me to replace files in system but not rename because when I overwrite it still says there is an existing file with same name.
Any kernel that works please let me know. I am working with defcomg to get gcam modded more than the current ones.
I would like to try, i already had install last global, and this rtemove my twrp instead the official recovery.... Can you give me all the steps to do from this position? Thank you
I have a problem with camera, force close no matter what I've done. may be build.prop change?
kbello said:
I have a problem with camera, force close no matter what I've done. may be build.prop change?
Click to expand...
Click to collapse
i got this as well... oh well going back to xiaomi eu rom
Hi the change to the build.prop did not break the camera. Mine is working fine. Maybe clear app data for that app?
I do many times, didn't work,
---------- Post added at 11:45 PM ---------- Previous post was at 11:23 PM ----------
This is the error:
java.lang.RuntimeException: unSupported Saturation
at com.android.camera2.compat.MiCameraCompatBaseImpl.applySaturation(MiCameraCompatBaseImpl.java:248)
at com.android.camera2.compat.MiCameraCompat.applySaturation(MiCameraCompat.java:49)
at com.android.camera2.MiCamera2.applySaturation(MiCamera2.java:2486)
at com.android.camera2.MiCamera2.applyCommonSettings(MiCamera2.java:2858)
at com.android.camera2.MiCamera2.applySettingsForCapture(MiCamera2.java:2971)
at com.android.camera2.MiCamera2ShotNormal.generateRequestBuilder(MiCamera2ShotNormal.java:141)
at com.android.camera2.MiCamera2ShotNormal.startShot(MiCamera2ShotNormal.java:59)
at com.android.camera2.MiCamera2.captureStillPicture(MiCamera2.java:2042)
at com.android.camera2.MiCamera2.triggerCapture(MiCamera2.java:1892)
at com.android.camera2.MiCamera2.takePicture(MiCamera2.java:991)
at com.android.camera.module.Camera2Module.startNormalCapture(Camera2Module.java:1130)
at com.android.camera.module.Camera2Module.onWaitingFocusFinished(Camera2Module.java:406)
at com.android.camera.module.loader.camera2.FocusManager2.capture(FocusManager2.java:767)
at com.android.camera.module.loader.camera2.FocusManager2.doSnap(FocusManager2.java:326)
at com.android.camera.module.Camera2Module.onShutterButtonClick(Camera2Module.java:1057)
at com.android.camera.fragment.bottom.FragmentBottomAction.onSnapClick(FragmentBottomAction.java:1653)
at com.android.camera.ui.CameraSnapView$1.handleMessage(CameraSnapView.java:67)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:201)
at android.app.ActivityThread.main(ActivityThread.java:6806)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:547)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:873)
@PWn3R, the root is working but there are some functionalities that disappeared in the setting menu such as slider settings, screen color.
For those who wants to revert to CN rom, revert the changes you have done and DO NOT forget to remove Magisk by flashing the uninstaller zip otherwise the device will bootloop.
I restore the original build.prop and boot.img, the camera came back to work. Any workaround?
kbello said:
I have a problem with camera, force close no matter what I've done. may be build.prop change?
Click to expand...
Click to collapse
I didn't notice if the slider settings were there before changing the build.prop. The problem here is that when you flash magisk it's enabling secure boot, which is triggering a check that normally runs when the device is locked. I think we can probably fix that by modifying the file that causes it and then this will work without build.prop changes. I have not had a chance to look into that, but will try to do so.
So, grabbed the latest OTA, and went through the usual re-root cycle, but was unable to edit the build.prop. While /root is mountable, /root/system is not, which means no tethering for me.
Anyone else running into the same issue?
I have the same issue, I've been fighting with it all day.
I patched the boot.img with Magisk Manager and flashed it, Magisk Manager show's I'm installed and Root Checker says I'm rooted, I was even able to install Adaway. But i cannot use any root app that needs to mount /System
I tried using Root Uninstaller and it says it has root access but cannot mount /system as R/W
It seems Magisk is only able to partially root on Android 10
I tried this with the Canary version and the standard version of Magisk and the same issue both times
Same issue on regular pixel:
sailfish:/ # mount -o remount,rw /system
'/dev/block/sda33' is read-only
lame
bbarnes1 said:
Same issue on regular pixel:
sailfish:/ # mount -o remount,rw /system
'/dev/block/sda33' is read-only
lame
Click to expand...
Click to collapse
if all you want to do is edit a prop in build.prop, just use the Magisk module MagiskHidePropsConfig....works like a charm (at least it did on Android 9 - assume it would work on 10....it sounded like it worked on the betas)....
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228
This has been a problem since the Q beta came out, with each update I tried to figure something out. With no luck! I tried the Magisk Mod but it didn't seem to work.
suggestions would be most appreciated!!
Thinkin about a clean install....maybe.....
Edit: It was also a problem with the P beta until it was out of beta (That was my hope for this)
sb1893 said:
if all you want to do is edit a prop in build.prop, just use the Magisk module MagiskHidePropsConfig....
Click to expand...
Click to collapse
I'm trying to add a prop, which seems like a different need, but will look into it.
tufyuma said:
Thinkin about a clean install....maybe.....
Click to expand...
Click to collapse
Was thinking about this, but realized a clean install for every update isn't worth a hotspot to me.
sb1893 said:
if all you want to do is edit a prop in build.prop, just use the Magisk module MagiskHidePropsConfig....works like a charm (at least it did on Android 9 - assume it would work on 10....it sounded like it worked on the betas)....
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228
Click to expand...
Click to collapse
I gave this a whirl, its doesn't appear to actually be change build.prop
bbarnes1 said:
I gave this a whirl, its doesn't appear to actually be change build.prop
Click to expand...
Click to collapse
It doesn't physically change anything in system. The intent is to offer the same functionality as physically editing the build.prop without modifying that file. It creates the prop and value setting and loads into into memory at boot time.....(similar to the way the build.prop file is read at boot time for those settings.) At least that is my understanding. It works for me on Android 9 for setting the prop for tethering...for example. You can confirm it works by using the getprop command to verify the prop you set is set as you intended.
Welp, still can't mount /system or edit the file directly, but PropsConfig seems to be good enough for my needs.
somethingsomethingroot said:
Welp, still can't mount /system or edit the file directly, but PropsConfig seems to be good enough for my needs.
Click to expand...
Click to collapse
Can you tell me what the process is that got you tethering capability?
Having the same issue on my P2XL which was upgraded via flash of full image minus -w. Using latest canary build of Magisk. I couldn't mount system or anything under it.
I then downgraded Magisk to v19.3 and had no issues mounting system using FX File Explorer, etc. and still had root. But I couldn't mount anything under system so I still can't edit build.prop.
For those who are just trying to find a way to get hotspot working (via build.prop edit), try this...worked for me on a dirty upgrade (A9 -> A10 via full image flash without -w) + latest Magisk Canary:
https://forum.xda-developers.com/showpost.php?p=75238542&postcount=59
IlyaKol said:
For those who are just trying to find a way to get hotspot working (via build.prop edit), try this...worked for me on a dirty upgrade (A9 -> A10 via full image flash without -w) + latest Magisk Canary:
https://forum.xda-developers.com/showpost.php?p=75238542&postcount=59
Click to expand...
Click to collapse
Thanks for posting this, it worked great on my Pixel XL on Sprint. I had about given up on being able to edit the build.prop.
You no longer need the canary version of Magisk. Version 20.00 will rebuild your boot.img and if you load busybox and use a terminal type "props" and follow the onscreen menu. you can get your tethering back. My output:
Your prop
DebianDog said:
You no longer need the canary version of Magisk. Version 20.00 will rebuild your boot.img and if you load busybox and use a terminal type "props" and follow the onscreen menu. you can get your tethering back. My output:
Click to expand...
Click to collapse
Are you sure that your screenshot of the props output is correct? Because it looks like you have the value set to "net.tethering.noprovisioning" and the prop name has =true in it. I'm just trying to figure this out because I've tried this and everything else trying to get my hotspot to work. My hotspot will turn on and devices can connect to it, but they don't have internet access. Any ideas at all?
Edit: Nevermind, I had the custom prop set to post fs data when it was supposed to be set at boot stage (default). My hotspot is working now. Thank you all.
DebianDog said:
You no longer need the canary version of Magisk. Version 20.00 will rebuild your boot.img and if you load busybox and use a terminal type "props" and follow the onscreen menu. you can get your tethering back. My output:
Click to expand...
Click to collapse
Confirming that this works on rooted pixel 4. Thank you for this btw
IlyaKol said:
For those who are just trying to find a way to get hotspot working (via build.prop edit), try this...worked for me on a dirty upgrade (A9 -> A10 via full image flash without -w) + latest Magisk Canary:
https://forum.xda-developers.com/showpost.php?p=75238542&postcount=59
Click to expand...
Click to collapse
This seems to have worked for me, though I don't really understand why or what did it.
For any dummies like me that happen to fall on this post after their build.prop seems to fail to save. The link above to: https://forum.xda-developers.com/showpost.php?p=75238542&postcount=59 worked for me.
download
https://forum.xda-developers.com/attachment.php?attachmentid=4392434&d=1516234353
to the device > run TWRP
I have to run twrp from cmd line since my Pixel XL refuses to install it using command::
.... fastboot boot twrp.img
and installing the zip file above > rebooting
back to cmd line
> adb shell
> settings put global tether_dun_required 0
> reboot
swipe notifications bar and turn on hotspot and wamo she's kicking.
Thanks guys
I haven't been beating my head too hard this time around. Many thanks to the brains that are keeping the rest of us dummies excited to keep tinkering about with our androids!
wolvmarine said:
For any dummies like me that happen to fall on this post after their build.prop seems to fail to save. The link above to: https://forum.xda-developers.com/showpost.php?p=75238542&postcount=59 worked for me.
download
https://forum.xda-developers.com/attachment.php?attachmentid=4392434&d=1516234353
to the device > run TWRP
I have to run twrp from cmd line since my Pixel XL refuses to install it using command::
.... fastboot boot twrp.img
and installing the zip file above > rebooting
back to cmd line
> adb shell
> settings put global tether_dun_required 0
> reboot
swipe notifications bar and turn on hotspot and wamo she's kicking.
Thanks guys
I haven't been beating my head too hard this time around. Many thanks to the brains that are keeping the rest of us dummies excited to keep tinkering about with our androids!
Click to expand...
Click to collapse
Why need to turn on Hotspot for build.Prop editing? What's wamo?
truelies1 said:
Why need to turn on Hotspot for build.Prop editing? What's wamo?
Click to expand...
Click to collapse
Does anyone know a way to enable gestures on 3rd party launchers on stock rom
Until TWRP is available for this device, root must be done by flashing patched boot image via fastboot. I'm still in the waiting period for the bootloader unlocking, but I prepared files in the meantime. Maybe someone will find them useful. Attached are stock boot and patched image with Magisk 21.1, EEA ROM version. Just unzip them and flash from fastboot.
Full version: V12.0.6.0.QJSEUXM_20201117
Edit: patched boot image reuploaded, the previous one didn't work (at least on my phone). This one has been tested and is working fine.
hello,
having the EEA version 12.0.6.0, as a boot patch can I immediately give the modded boot, in fastboot?
carabot said:
hello,
having the EEA version 12.0.6.0, as a boot patch can I immediately give the modded boot, in fastboot?
Click to expand...
Click to collapse
You can flash patched boot image directly, or just hotboot it (fastboot boot patched_image.img) and install Magisk from Magisk manager.
hello,
I did and at the moment everything is ok.
thanks
but there is a strange thing, Mixplorer, it does not change the permissions of the files, yet it has root permissions
I think the root is not perfect, I can't change the permissions of the files
carabot said:
I think the root is not perfect, I can't change the permissions of the files
Click to expand...
Click to collapse
Which files on which partition with what kind of permissions? RO partitions must be remounted as RW, but it's not always possible and using Magisk is usually a better and safer approach.
hello
let's talk about system partition files how can I remount as RO?
using Mixplorer, if I click comeback as RO, it tells me failed
carabot said:
hello
let's talk about system partition files how can I remount as RO?
using Mixplorer, if I click comeback as RO, it tells me failed
Click to expand...
Click to collapse
I keep my system partition RO so I can apply OTA updates, so I haven't tried it. You could try another app (for example Total commander), but you will be probably out of luck because of Android 10 limitation. Read more detailed explanation here https://android.stackexchange.com/q...m-partition-locked-to-read-only-in-android-10
I would suggest using Magisk module for system modifications.
hi
i tried other app manager like root explorer and es explorer, but the result is the same. i also installed magiskhideprops module, but my phone is not supported as fingerprint yet
What are you trying to achieve?
the terminal command to try to mount as RO would you know?
_mysiak_ said:
What are you trying to achieve?
Click to expand...
Click to collapse
full root to modify root files
carabot said:
full root to modify root files
Click to expand...
Click to collapse
I meant which files do you want to modify and why..
carabot said:
the terminal command to try to mount as RO would you know?
Click to expand...
Click to collapse
It's in the link above, along with explanation why it might be impossible to do.
I wanted to change the audio files regarding the volume, I wanted it a little higher
carabot said:
I wanted to change the audio files regarding the volume, I wanted it a little higher
Click to expand...
Click to collapse
Why don't you do it with a Magisk module? Once you install a module, you can edit it directly in /data/adb/modules folder.
i read android 10 problem, would you recommend me to mount with termux, installing vim?
_mysiak_ said:
Why don't you do it with a Magisk module? Once you install a module, you can edit it directly in /data/adb/modules folder.
Click to expand...
Click to collapse
i don't know about magisk modules that can affect volume controls
carabot said:
i don't know about magisk modules that can affect volume controls
Click to expand...
Click to collapse
If you know how to edit system mixer files, you should be able to build your own module (or adapt one of the existing ones). But of course it's up to you, I'm just offering a well known and working solution to your problem.
_mysiak_ said:
If you know how to edit system mixer files, you should be able to build your own module (or adapt one of the existing ones). But of course it's up to you, I'm just offering a well known and working solution to your problem.
Click to expand...
Click to collapse
unfortunately no, I edit the audio value of the system files, but I don't know how to build a module
Hello
the twrp for gauguin is online, to mount it i have to go back to the stock boot?