Related
Every time I try to go to my security settings to put in my security code, I get a FC. I've done a factory reset, cleared cache, manually FC the settings and even flashed the 4.2.0 and 4.2.1 factory images, which allowed me to get into my security settings, yet once I update to 4.2.2 it force closes. Anyone have this issue. I'm stock rooted and used OTA root keeper to restore root. I tried getting into my settings before restoring and got a FC too. I've done everything I can think of
IS this happening to anyone else?
Found a fix! other than flashing system.img, you can do this as well. Cedit go to Reddit user Tastler
This is what helped me: ( I got this solution from android-hilfe.de)
I have a rooted Nexus 4 and got my OTA update yesterday...
(german) 1. Terminal Emulator öffnen (bei Bedarf im Play Store herunterladen - kostenlos) 2. In das Feld "su" eingeben und Dialog von SuperSU oder SuperUser mit Ja schließen. 3. In das Feld "mount -o rw,remount /system" eingeben. 4. In das Feld "cd /vendor/firmware/keymaster" eingeben. 5. In das Feld "chmod 0644 *" eingeben.
Let me try to translate it:
You need root for this solution
Open a Terminal Emulator (If neccessary get it from Play Store for free)
type "su" and answer permission dialog from SuperSU or SuperUser
type "mount -o rw,remount /system" exactly as stated here including the spaces -> followed by enter
type "cd /vendor/firmware/keymaster" -> followed by enter
type "chmod 0644 *" -> followed by enter
You may have to restart your phone.
Alternative: If you have root explorer or ES File Explorer you can set the folder permissions (chmod) also directly.
I hope it helps in your case.
source: http://www.reddit.com/r/nexus4/comm...ter_updating_to_android_422/c8gbjhf?context=3
Same problem here. Cant get into my security settings. Rooted out of the box, installed rootkeeper, updated to 4.2.2. an restored root.
Do you have the problem when you do NOT restore root once you upgrade to 4.2.2?
have u disabled any settings???
like me..im disable faceunlock..so everytime i go for face unlock setting..its FC...
[V]endetta said:
have u disabled any settings???
like me..im disable faceunlock..so everytime i go for face unlock setting..its FC...
Click to expand...
Click to collapse
All my settings are default since i upgraded out of the box. Do you use rootkeeper?
Re: Upgraded to 4.2.2 through the OTA and now I get a settings FC...
I just upgraded.. Bone stock, no FC's in security settings
<sent from my Nexus 4>
Re: Upgraded to 4.2.2 through the OTA and now I get a settings FC...
I'm having same issues guess there is some incompatibility apps maybe those that set as admin rights? I have VPN set also Fc..my workaround is to flash factory 4.2.2 img no longer fc
Sent from my Nexus 4 using xda premium
Exact same problem. I used OTA Rootkeeper too.
Farq, is there a surefire fix?
Edit: temp un-root doesn't help
I had this as well, what I did was go into fastboot and flash only system.img (this img file is in Google's 4.2.2 Factory image). No need to do a full wipe/flash.
Code:
fastboot flash system system.img
reboot
All your apps, settings, and data stays untouched, but you will however need to re-root so SuperSU is put back into /system again.
Re: Upgraded to 4.2.2 through the OTA and now I get a settings FC...
Sorry for the late response, I've tried everything completely stock and rooted. I'm currently rooted stock amend still have the same issue. I'll have to try that system image thing when I get back from the gym. I wonder if this is something Google forgot to test like the December bug
Sent from my Nexus 7 using xda app-developers app
Salty Wagyu said:
I had this as well, what I did was go into fastboot and flash only system.img (this img file is in Google's 4.2.2 Factory image). No need to do a full wipe/flash.
Code:
fastboot flash system system.img
reboot
All your apps, settings, and data stays untouched, but you will however need to re-root so SuperSU is put back into /system again.
Click to expand...
Click to collapse
Thanks! That did the trick, i can access security again. Did lose my root though and i cant use rootkeep to restore my root, stupid me didnt backup root before flashing the image
-edit: sweet, i rooted again with the nexus root toolkit, and all my apps and data are still there. Security setting work fine now!
plaktoets said:
Thanks! That did the trick, i can access security again. Did lose my root though and i cant use rootkeep to restore my root, stupid me didnt backup root before flashing the image
-edit: sweet, i rooted again with the nexus root toolkit, and all my apps and data are still there. Security setting work fine now!
Click to expand...
Click to collapse
I have the same problem; I upgraded to 4.2.2 and used Voodoo OTA Root Keeper. Can someone let me know what program to use to run "fastboot flash system system.img" or how to do it?
EDIT: I figured it out. Thanks!
grayson73 said:
I have the same problem; I upgraded to 4.2.2 and used Voodoo OTA Root Keeper. Can someone let me know what program to use to run "fastboot flash system system.img" or how to do it?
EDIT: I figured it out. Thanks!
Click to expand...
Click to collapse
I have the same problem.
Can u tell me how u sorted it?
Thanks
iggy111 said:
I have the same problem.
Can u tell me how u sorted it?
Thanks
Click to expand...
Click to collapse
These are the steps i followed:
1. As described in post #8: download this file and extract the system.img file to the same folder that contains the fastboot utility
2: Power down your Nexus 4 and reboot into fastboot mode. You can do this by holding down the the Volume Down and Power buttons simultaneously.
3: Connect your device to your computer. Open up a terminal or command prompt, and navigate to the folder containing the fastboot program.
4. Type the command as described in #8:
Code:
fastboot flash system system.img
This will flash stock 4.2.2 without loosing your apps and setting.
5. When done reboot your phone. Security settings should work now.
5. FInally, root your device using the Root toolkit. Follow the instructions describing the workaround for rooting 4.2.2:
Yes, I am aware that this isn’t working on 4.2.2 right now. This will be fixed in v1.6.3 which will be released ASAP (within a few days or sooner if possible). As a temporary fix you can replace the old adb/fastboot/dll files in the toolkits /data directory with the new ones: new_adb_and_fastboot.zip just download that zip and extract/unzip its contents into the toolkits /data directory and agree to overwrite those files
Click to expand...
Click to collapse
Since your bootloader should still be unlocked, theres no need to unlock again so you can skip all steps and go to Root immediately.
All your apps & settings should be kept.
Can we use the above steps but use OTA Rootkeeper to preserve root?
Hero_Guy said:
Every time I try to go to my security settings to put in my security code, I get a FC. I've done a factory reset, cleared cache, manually FC the settings and even flashed the 4.2.0 and 4.2.1 factory images, which allowed me to get into my security settings, yet once I update to 4.2.2 it force closes. Anyone have this issue. I'm stock rooted and used OTA root keeper to restore root. I tried getting into my settings before restoring and got a FC too. I've done everything I can think of
IS this happening to anyone else?
Found a fix! other than flashing system.img, you can do this as well. Cedit go to Reddit user Tastler
This is what helped me: ( I got this solution from android-hilfe.de)
I have a rooted Nexus 4 and got my OTA update yesterday...
(german) 1. Terminal Emulator öffnen (bei Bedarf im Play Store herunterladen - kostenlos) 2. In das Feld "su" eingeben und Dialog von SuperSU oder SuperUser mit Ja schließen. 3. In das Feld "mount -o rw,remount /system" eingeben. 4. In das Feld "cd /vendor/firmware/keymaster" eingeben. 5. In das Feld "chmod 0644 *" eingeben.
Let me try to translate it:
You need root for this solution
Open a Terminal Emulator (If neccessary get it from Play Store for free)
type "su" and answer permission dialog from SuperSU or SuperUser
type "mount -o rw,remount /system" exactly as stated here including the spaces -> followed by enter
type "cd /vendor/firmware/keymaster" -> followed by enter
type "chmod 0644 *" -> followed by enter
You may have to restart your phone.
Alternative: If you have root explorer or ES File Explorer you can set the folder permissions (chmod) also directly.
I hope it helps in your case.
source: http://www.reddit.com/r/nexus4/comm...ter_updating_to_android_422/c8gbjhf?context=3
Click to expand...
Click to collapse
This worked for me, thanks!
I used nexus toolkit to unlock bootloader and root
Then OTA rootkeeper to restore root.
Can I still use the solution a few posts up?
I'm just not sure how?
Edit - I used the method using terminal emulator and all good now.
I solved my problem by using terminal emulator too. Phew!
How would it have worked using a file explorer (I use Solid)?
mlj11 said:
I solved my problem by using terminal emulator too. Phew!
How would it have worked using a file explorer (I use Solid)?
Click to expand...
Click to collapse
Idk the file manager method didn't work for me. I set the permissions to rw-r-r and still FC!
Sent from my Nexus 4 using xda app-developers app
Using the Terminal Emulator worked for me. Just be VERY careful with the punctuation and spaces, caught me out multiple times.
plaktoets said:
These are the steps i followed:
1. As described in post #8: download this file and extract the system.img file to the same folder that contains the fastboot utility
2: Power down your Nexus 4 and reboot into fastboot mode. You can do this by holding down the the Volume Down and Power buttons simultaneously.
3: Connect your device to your computer. Open up a terminal or command prompt, and navigate to the folder containing the fastboot program.
4. Type the command as described in #8:
Code:
fastboot flash system system.img
This will flash stock 4.2.2 without loosing your apps and setting.
5. When done reboot your phone. Security settings should work now.
5. FInally, root your device using the Root toolkit. Follow the instructions describing the workaround for rooting 4.2.2:
Since your bootloader should still be unlocked, theres no need to unlock again so you can skip all steps and go to Root immediately.
All your apps & settings should be kept.
Click to expand...
Click to collapse
does this method work if im on 4.2.1 stock rom + franco kernel? or its only for stock rom + stock kernel? only
CyanogenMod's file manager seems to be stuck in safe mode, even though I have a rooted device and even have a modified kernel. I've not been able to figure out exactly what's happening. It says that only the accessible file systems are the storage volumes.
Anyone else have this problem, or does anyone know how to fix it?
RogueSly said:
CyanogenMod's file manager seems to be stuck in safe mode, even though I have a rooted device and even have a modified kernel. I've not been able to figure out exactly what's happening. It says that only the accessible file systems are the storage volumes.
Anyone else have this problem, or does anyone know how to fix it?
Click to expand...
Click to collapse
The default for the CM file manager is for root access to be turned off. With the file manager open go into settings and allow root access. Once you exit settings you'll have full access.
Nut_House said:
The default for the CM file manager is for root access to be turned off. With the file manager open go into settings and allow root access. Once you exit settings you'll have full access.
Click to expand...
Click to collapse
That's the problem. It won't allow root access, even though the phone has root access. The menu for the access mode is disabled.
RogueSly said:
That's the problem. It won't allow root access, even though the phone has root access. The menu for the access mode is disabled.
Click to expand...
Click to collapse
Have you tried clearing cache and Dalvik and fixing permissions? The other thing to try, if you haven't already, is downloading the latest nightly and performing a clean install rather than dirty flashing. Good luck.
If you accidentally refused root access the first time you have to go into the SU app and clear out the File manager permission and start over.
Nut_House said:
Have you tried clearing cache and Dalvik and fixing permissions? The other thing to try, if you haven't already, is downloading the latest nightly and performing a clean install rather than dirty flashing. Good luck.
Click to expand...
Click to collapse
I've already tried installing the latest nightly version and ran a permission fix on it, but end up with the same result. I'll try clearing cache, dalvik, and then fixing again.
gharlane00 said:
If you accidentally refused root access the first time you have to go into the SU app and clear out the File manager permission and start over.
Click to expand...
Click to collapse
The file manager doesn't have any permissions in SuperSU and never asks for any since it's not in root access mode. :\
Nut_House said:
Have you tried clearing cache and Dalvik and fixing permissions? The other thing to try, if you haven't already, is downloading the latest nightly and performing a clean install rather than dirty flashing. Good luck.
Click to expand...
Click to collapse
Yeah, still the same result. Clearing dalvik and cache didn't work.
Just grab es file explorer.
Sent from my SPH-L720 using xda app-developers app
RogueSly said:
Yeah, still the same result. Clearing dalvik and cache didn't work.
Click to expand...
Click to collapse
same problem.
tried to install supersu, reinstall busy box on bin and xbin, fix permissions, no luck, option still greyed out.
file manager always worked for me as root, both on cm-based ROMs and aosp.
this time it is not working with the combo saberMod and matrix on N4.
(i think this is a device-independent issue)
---------- Post added at 08:20 PM ---------- Previous post was at 08:07 PM ----------
After a lot of tentatives I solved it.
I am not 100% sure of which change made it though
I think it was by using ES root manager and resetting system as R/W.
Sent from my Nexus 4 using xda app-developers app
Alternate fix
I also had the same issue and resolved it by tapping the menu button on the top left corner. when you do this, another menu button appears in the top right corner. Hit that, then settings, and choose root mode. Took me a while to figure out!!!
solved...
Installing busy box should resolve the issue...
Sorry for bumping, I have busybox and su installed, init.d support as well, but Cyanogen's File manager still cannot access root (option is grayed out). I'm on a stock Prestigio rom. It worked previously, but I reflashed firmware and now it doesn't work on this new firmware. Any thoughts?
Hi terirem and everybody,
I had this issue recently and I've managed to fix it. This is what You should do:
Short run:
Type in rooted phone terminal:
su
am start com.cyanogenmod.filemanager.ics
done
Long run:
1. Of course You need rooted phone, I've installed also BusyBox but I am not sure if it's necessary.
2. Install Terminal application
3. Install (if it's not installed yet) and run cyanogenmod file manager then minimize it by pressing home button (make sure You don't do anything else on Your phone to don't kill file manager process, it needs to be alive for 4th point)
4. I will make all commands bold for easier reading. run your terminal app and type: top -n 1 (this command will list all your running applications just once).
5. Find cyanogenmod in last "name" column, mine has name: com.cyanogenmod.filemanager.ics (if you can't find it you can try the one I had for 7th step, should probably work)
6. Type: su You will be asked to give superuser permissions to terminal, agree. Now instead of $ an # should appear, this means all commands from now on have root privilage.
7. Now we will finally rerun filemanager again with superuser permissions, type: am start com.cyanogenmod.filemanager.ics (if you had different name of filemanager just write the one you got after am start)
8. Go to cyanogenmod filemanager general settings and change access mode to root (it should be finally available, if not make sure again You typed am start with root permissions in terminal, if still doesn't work then forget about point 9).
9. Give me a beer, or actually simple thanks is enough, I need to stop drinking.
My SuperSU is kept auto-granting and system storage is kept read-written, also I cleared the every caches.
The CM file manager is still not shown a root mode to me.
I have J-rummy’s ROM toolbox as an alternative root explorer, but sometimes is less readable than CM file manager.
There is a guy forgetting to let the system storage read-written to remind him.
I did this with CM file manager - make sure you have root access not just safe mode in general settings. When you open filemanger it is granted super U access and then you can edit and save without issues
CM Dev Settings
In Dev options is Root access set to Apps and ADB?
For anyone else still having this problem, just erase the File Manager data (Settings | Apps | File Manager | Storage | Clear Data) with SU turned on in developer options. Then press the hamburger icon in the top-right of the app, press the settings icon on the bottom, click on General settings and you will see Access Mode
bsevcenk said:
For anyone else still having this problem, just erase the File Manager data (Settings | Apps | File Manager | Storage | Clear Data) with SU turned on in developer options. Then press the hamburger icon in the top-right of the app, press the settings icon on the bottom, click on General settings and you will see Access Mode
Click to expand...
Click to collapse
I am on CM13, now with SuperSU installed since I couldn't get the root option there to work well with some other apps for some reason.
File Manager now doesn't show any option for 'safe mode' or otherwise at all in settings. I cleared the data. I started it as in the earlier post. Nothing.
In the Developer options root is allowed, although only for ADB (the apps option has gone).
passtim said:
I am on CM13, now with SuperSU installed since I couldn't get the root option there to work well with some other apps for some reason.
File Manager now doesn't show any option for 'safe mode' or otherwise at all in settings. I cleared the data. I started it as in the earlier post. Nothing.
In the Developer options root is allowed, although only for ADB (the apps option has gone).
Click to expand...
Click to collapse
same here for me.
I'm working on a fix for now.
EDIT
If you're on a systemless SuperSU, use a terminal or ADB shell to input the following lines:
Code:
su
mount -o remount,rw /system
ln -s /su/bin/su /system/xbin/su
id74em8 said:
same here for me.
I'm working on a fix for now.
EDIT
If you're on a systemless SuperSU, use a terminal or ADB shell to input the following lines:
Code:
su
mount -o remount,rw /system
ln -s /su/bin/su /system/xbin/su
Click to expand...
Click to collapse
Apologies, but I'm no expert at these things. What is a 'systemless' SuperSU?
Is making a link as you suggest safe?
Hi all,
has anyone been able to do this? Following the guide here, no longer works for Android N. The phone boots, but ignores all changes to system. How do I modify both build.prop and hosts? It seems that there are now possibly two system partitions?
Thanks!
Same issue on Nexus 5X
No answer on this? How is it that nobody else seems to be having this issue?
What I've done
It looks to me like everyone has moved to systemless and the /system partition cannot be adequately modified in this way anymore.
Maybe this will help others:
I was modifying the system directory for two reasons: 1. modify /system/etc/hosts to remove ads and modifying build.prop to increase lcd.density. I found that here are the alternatives for each:
Removing Ads
Using something similar to AdAway_systemless_hosts_v2.zip (google it for a copy) and modifying the hosts file in that zip file to be the one I use (and rezipping, deploying on the Android device). This basically mounts over /system/etc/hosts with a custom hosts file instead of actually modifying the system specific hosts file which is no longer writable.
The alternative is to use Netguard which routes non https network traffic through a private VPN where you can block ads according to a hosts file. This seems to work OK, but I have noticed that websites seem to take longer to load.
Modifying lcd.density
You can use the same trick as AdAway_systemless_hosts_v2.zip uses, but modify it to also mount a modified copy of build.prop. Alternatively just use the Android N Display settings that are small (what I did anyhow).
I have been able to edit build.prop and still maintain systemless root.
Sent from my Nexus 6P using XDA-Developers mobile app
I was able to modify my system partition; by installing busy box to /su/xbin and running "su busybox mount -o rw,remount system" (no quotes) in material terminal with root
ArminasAnarion said:
I was able to modify my system partition; by installing busy box to /su/xbin and running "su busybox mount -o rw,remount system" (no quotes) in material terminal with root
Click to expand...
Click to collapse
Have you been able to do this with simply fastboot boot <twrp-image>, mounting system in rw mode and modifying it? I did that as I didn't want to root the phone, and while it looks like it did the write, it does not affect the system partition that is used by the phone after boot. I think there are two system partitions, and twrp mounts only one in rw mode. It does seem like it may be possible to do what you say using adb though after the phone is fully booted up. I'll try that!
dontblinkwatchout said:
Have you been able to do this with simply fastboot boot <twrp-image>, mounting system in rw mode and modifying it? I did that as I didn't want to root the phone, and while it looks like it did the write, it does not affect the system partition that is used by the phone after boot. I think there are two system partitions, and twrp mounts only one in rw mode. It does seem like it may be possible to do what you say using adb though after the phone is fully booted up. I'll try that!
Click to expand...
Click to collapse
I had the same problem. I don't want to root but I do make a few changes to my /system partition through adb in recovery such as the hosts file and some font files (namely the Emoji font file). I had modified stock boot image to not enforce encryption. I would boot back up into the system and couldn't see any changes made. The only thing I found that worked was installing a custom kernel (I use ElementalX). After that, changes I made to /system in TWRP were reflected in the OS. I don't know enough about kernel development to understand why on (mostly) stock kernel my changes couldn't be seen but on a custom one they were.
I never had this "problem" prior to Nougat.
Same issue here. Something has changed with how this is handled in Nougat.
I don't want to root just to overwrite the hosts file...
I'll keep debugging but my capability in this is definitely limited!
I use a similar approach as described in the OP's linked guide except I use my own recovery image that I compiled as an engineering build from source, and I am also experiencing the same behavior. Modifying the hosts file seems to have no impact on the system though the changes persist. Comparing the host file I installed and the host file from the latest Nexus 5X image with 'ls -lZ' the SELinux info looks to be the same. The only information that appears to differ is the modified date and one additional line in the file itself for testing. I thought I was doing something wrong with my hosts file, even though I have been using this approach since Android 6.0. However, I agree, it appears that changes to system are being ignored. Further, changing the system partition no longer shows the red warning at boot about the system being corrupted.
---------- Post added at 09:58 PM ---------- Previous post was at 09:38 PM ----------
DanRyb;68654939 I would boot back up into the system and couldn't see any changes made.[/QUOTE said:
Oooh. You're right. Neither /etc/hosts or /system/etc/hosts is modified in the booted OS after I modify it from live image, but the change is retained when I reboot into live image and mount system. Hmm, so either:
1) Need to figure out where the the system files are being loaded from and modify them from live image if possible
2) Use a mechanism similar to what dontblinkwatchout described AdAway is using of having a custom mount setup (have to reverse engineer AdAway I guess to see what it's doing)
3) ?
Click to expand...
Click to collapse
There's absolutely no way to modify or mount system partition r+w unless you disable dm-verity
Enviado desde mi Nexus 6P mediante Tapatalk
alexiuss said:
There's absolutely no way to modify or mount system partition r+w unless you disable dm-verity
Enviado desde mi Nexus 6P mediante Tapatalk
Click to expand...
Click to collapse
dm-verity has been around since Android 4.4. Are you saying there is something new around this in Android 7.0?
You can modify the system partition by compiling an engineering build of Android and booting it, then mounting the system partition and modifying it. I've been doing this to update the hosts file since Android 6.0 for every OTA update (since more recently OTA updates bomb out unless you reflash the clean "uncorrupted" system.img first). Changing the system image before Android 7.0 did result in an extra screen with a red warning about a corrupted something or other (I'm sure because dm-verity checking failed). Regardless, you can still change the system partition, the information just no longer seems to be used, which is a bit perplexing to me atm.
crashenx said:
dm-verity has been around since Android 4.4. Are you saying there is something new around this in Android 7.0?
Click to expand...
Click to collapse
Android 7.0 introduced redundant bits for reed solomon forward error correction into the system and vendor partitions and code in the kernel to perform the error correction.
Your changes are being written to emmc but when you boot with 7.0 kernel with dm-verity enabled your changes are being treated as data corruption and on-the-fly error corrected back to original.
You can see your changes if you boot into twrp because it has dm-verity disabled. However if you boot into android with dm-verity enabled it will look like original image again even though your changes are technically still there.
It took me a day to figure out what was really going on because i initially had no idea they added this feature to Android N.
The simple way to disable dm-verity is to install SuperSU, but you can also accomplish the same patching your own kernel, installing pre-patched kernel, installing custom kernel, etc.
sfhub said:
Android 7.0 introduced redundant bits for reed solomon forward error correction into the system and vendor partitions and code in the kernel to perform the error correction.
Your changes are being written to emmc but when you boot with 7.0 kernel with dm-verity enabled your changes are being treated as data corruption and on-the-fly error corrected back to original.
You can see your changes if you boot into twrp because it has dm-verity disabled. However if you boot into android with dm-verity enabled it will look like original image again even though your changes are technically still there.
It took me a day to figure out what was really going on because i initially had no idea they added this feature to Android N.
The simple way to disable dm-verity is to install SuperSU, but you can also accomplish the same patching your own kernel, installing pre-patched kernel, installing custom kernel, etc.
Click to expand...
Click to collapse
That's good info and makes total sense. Thanks! Pretty neat actually, just a bummer for me.
Yeah so SuperSU path is not really one I want to pursue. I could learn how to update the dm-verity shas used for verification. That'd probably be the most secure, but it's gonna be a PITA I bet. I imagine I'd need to compile my own image similar to how I made my live image and update a few things. Might have to deal with encryption which is probably an even bigger headache. Also, I bet it would break OTA and have to reflash to update, though that's true now.
I'm really curious what AdAway is doing. Maybe I should pursue reverse engineering that.
I really appreciate you pointing us in the right direction.
I am glad found this thread..willing to assist here without permanent root..
Ericarthurc said:
I was able to modify my system partition; by installing busy box to /su/xbin and running "su busybox mount -o rw,remount system" (no quotes) in material terminal with root
Click to expand...
Click to collapse
I was trying to create a /system/xbin/post-boot but couldn't remount /system, and so I added busybox to the front of my command. I am not using adb so I cut that part off. Thanks a lot!
I have here, two packages.
The twrp one is meant for those who have already flashed twrp, the other is for first time root via EDL.
Both flash System RW, updated TWRP and magisk.
TWRP package will not wipe Data, You will loose no data
NOTE - You may have to mount the system RW.
NOTE - The above will be fixed via a future custom rom.
Without further ado, here are the instructions.
Initial Root Instructions
Prep: You must have a Pin screen lock set on your device to prevent data loss.
On your phone go to
Settings>Security>Screen Lock>PIN
and set a pin.
USB Debugging and OEM Unlocking have to be enabled to make this work.
On Your phone go to
Setting>About phone
Then tap on build number 10 time to unlock Developer Settings
Now go to
Settings>Developer Options
Then toggle usb debugging and oem unlocking.
1. Download this package B20 Via QFIL
2. Unzip the file to your desktop.
3. Right click on RunasAdmin_TestSignON.bat and run as administrator.
4. Let your machine reboot.
5. Run Run This.bat
6. Install everything it tells you to install.
NOTE Select WWAN-DHCP when asked
7. RTFM and flash (All the files your need for qfil are in the B20 Folder!!!!)
8. Profit
Then
9.Press and hold Vol+ and Power
10.Once the ZTE screen shows, let go of power while continuing to hold vol+
This will get you into twrp
11.Plug you phone into your computer and from your adb directory, run these commands.
12.adb shell
13.setenforce 0
14.exit
Now on your phone, in twrp
15.Swipe to allow midification
16.Tap Backup
17.check data
18.tap select storage
19.Select microsdcard
20.tap ok
21.Swipe to backup
22.Tap home
23.Tap wipe
24.Tap Format Data
25.Enter yes and tap the blue checkmark
26.Tap home
27.Tap Power off
28.Turn your phone on.
For those who have TWRP already on their device, follow these instructions.
1. Download this package. B20 via TWRP
2. Extract it to your desktop
3. Run "Flash full B25.bat"
4. Profit
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Update 5/253/19
Updated boot.img z982_boot_magisk.img
Update Magisk root "Already obsolete"
Fixes ADB not authorized issues
Update twrp recovery.img z982_recovery_twrp.img
Fixes selinux enforcing related issues related to /data folder
Fixes backup related issues
Fixes zip install related issues
Do you think this will work with my hard bricked phone?
so if our system is still ro, all we have to do is mount rw every time? I was hoping that we would only need to mount it like one time, because im basically doing the same thing I was doing before.
https://drive.google.com/file/d/1YsOFbKcca2GTc6K77vD6-hh4qtk5O3mv/view?usp=sharing
test this. you might need to rename the zip file to bootanimtion.zip.
Chickenaa said:
https://drive.google.com/file/d/1YsOFbKcca2GTc6K77vD6-hh4qtk5O3mv/view?usp=sharing
test this. you might need to rename the zip file to bootanimtion.zip.
Click to expand...
Click to collapse
will do. are all the files already in place.
bootanimation worked, but sound still didnt
evtoofly said:
will do. are all the files already in place.
bootanimation worked, but sound still didnt
Click to expand...
Click to collapse
Upload the build.prop
Chickenaa said:
Do you think this will work with my hard bricked phone?
Click to expand...
Click to collapse
As long as you get the driver working, it should no problem.
xxMoon said:
As long as you get the driver working, it should no problem.
Click to expand...
Click to collapse
Im thinking about reinstalling windows. Do you think i should give it a try?
Chickenaa said:
Im thinking about reinstalling windows. Do you think i should give it a try?
Click to expand...
Click to collapse
I would.
Before you reinstall.. if ur able try on another PC.
xxMoon said:
1. Download this package. B20 via TWRP
2. Extract it to your desktop
3. Run "Flash full B25.bat"
4. Profit
Click to expand...
Click to collapse
Appreciate the update, same problem as before though RO /system and a mount -o rw,remount /system command results in the phone freezing and then restarting.
JasonSec said:
Appreciate the update, same problem as before though RO /system and a mount -o rw,remount /system command results in the phone freezing and then restarting.
Click to expand...
Click to collapse
thought I was the only one, I just stopped trying, if I need to go mount rw, i just use root explorer . Even that freezes sometimes though smh. Some people just got it better than we do
B25
Hello sir,
My phone is running B25. Will this cause issues? Do I need to downgrade?
AjtheLAF said:
Hello sir,
My phone is running B25. Will this cause issues? Do I need to downgrade?
Click to expand...
Click to collapse
No issues for me.
Emerl said:
No issues for me.
Click to expand...
Click to collapse
Did your system become rw?
evtoofly said:
Did your system become rw?
Click to expand...
Click to collapse
I use ES File Explorer. Open the app, wait for su to grant it access, then change the system to RW. I've noticed that the phone will freeze if I tried to switch to RW before the File Explorer was granted su access.
Emerl said:
I use ES File Explorer. Open the app, wait for su to grant it access, then change the system to RW. I've noticed that the phone will freeze if I tried to switch to RW before the File Explorer was granted su access.
Click to expand...
Click to collapse
I noticed that too. I also tried to see if root explorer would mount rw after I used es to mount rw, and it turns out that u still have to mount system separately in both file managers. Bummer because I was looking for a way to always have my system mounted as rw between both file managers.
evtoofly said:
I noticed that too. I also tried to see if root explorer would mount rw after I used es to mount rw, and it turns out that u still have to mount system separately in both file managers. Bummer because I was looking for a way to always have my system mounted as rw between both file managers.
Click to expand...
Click to collapse
I'm guessing once a custom rom is available, the whole system RW situation will be situated. Is there an advantage of root explorer over es explorer?
Emerl said:
I'm guessing once a custom rom is available, the whole system RW situation will be situated. Is there an advantage of root explorer over es explorer?
Click to expand...
Click to collapse
I personally use root explor to chmod files, I dont think es can do it, however es has its own perks as well, so I just keep both just in case
Emerl said:
I'm guessing once a custom rom is available, the whole system RW situation will be situated. Is there an advantage of root explorer over es explorer?
Click to expand...
Click to collapse
Lol, actually you can put init.d scripts in /sbin/.magisk/img/.core/service.d/ and they will do it on boot.
Try my attachment.
I
Don't ask me how, but I somehow set pattern and forgot it in one hour. I use face rec. as well but after reboot I need to unlock with pattern.
For last 10h I tried all methods how to unlock phone, but no success.
I'm using original, ROM, my G6 model is H870, running Pie, unlocked bootloader, so I can use TWRP. I spent most of my time and knowledge to unlock phone with adb/twrp. Best option I found is to delete gesture.key file which is located under /data/system.
Problem is, that /data is encrypted ...
Is there anyone who managed to remove pattern/lock without loosing data?
Thank you for your time!
akulp said:
Don't ask me how, but I somehow set pattern and forgot it in one hour. I use face rec. as well but after reboot I need to unlock with pattern.
For last 10h I tried all methods how to unlock phone, but no success.
I'm using original, ROM, my G6 model is H870, running Pie, unlocked bootloader, so I can use TWRP. I spent most of my time and knowledge to unlock phone with adb/twrp. Best option I found is to delete gesture.key file which is located under /data/system.
Problem is, that /data is encrypted ...
Is there anyone who managed to remove pattern/lock without loosing data?
Thank you for your time!
Click to expand...
Click to collapse
Maybe this will work: https://************/delete-android-security-pin/
Edit: link gets truncated... Just search 'Remove pin twrp' on Google and click the first result.
krilok said:
Maybe this will work: https://************/delete-android-security-pin/
Edit: link gets truncated... Just search 'Remove pin twrp' on Google and click the first result.
Click to expand...
Click to collapse
Non of this solutions work.
This is pretty the same as I said. My problem is that /data is encrypted and I can't find/see any .key files.
Also I can't do "su" command inside adb shell because of "insuff. privileges" ...
I tried all this solutions:
https://forum.xda-developers.com/showthread.php?p=49666433#post49666433
For method 1 -5 there is a problem with .key files which are not seen to my TWRP/Aroma browser. I don't know If I'm doing anything wrong in method 7, but also after mount I can't access /data/system (/data is empty).
In method 6 I'm stucked on
"Run pull settings.db.cmd inside By-pass security Hacks folder to pull out the setting file out of your phone." step.
I get "insuff. privileges" error.
akulp said:
Non of this solutions work.
This is pretty the same as I said. My problem is that /data is encrypted and I can't find/see any .key files.
Also I can't do "su" command inside adb shell because of "insuff. privileges" ...
I tried all this solutions:
https://forum.xda-developers.com/showthread.php?p=49666433#post49666433
For method 1 -5 there is a problem with .key files which are not seen to my TWRP/Aroma browser. I don't know If I'm doing anything wrong in method 7, but also after mount I can't access /data/system (/data is empty).
In method 6 I'm stucked on
"Run pull settings.db.cmd inside By-pass security Hacks folder to pull out the setting file out of your phone." step.
I get "insuff. privileges" error.
Click to expand...
Click to collapse
Have you tried this?
https://forum.xda-developers.com/android/software-hacking/remove-lockscreen-recovery-t3530008
Basically, the files you have to delete in the /data/system folder in TWRP are:
password.key
pattern.key
locksettings.db
locksettings.db-shm
locksettings.db-wal
It happened to me a while ago and I didn't have any '.key' files either; I just deleted the rest and when I booted up, I had no lock screen security PIN nor registered fingerprints but could re-set them again through security settings. I didn't need to flash any files nor fiddle around with adb commands, and all my data remained untouched...
If you can't find all those five files or the '.key' files, just delete the ones you can find and it should work. Otherwise, you'll probably have to do a full reset and reinstall...
krilok said:
Have you tried this?
https://forum.xda-developers.com/android/software-hacking/remove-lockscreen-recovery-t3530008
Basically, the files you have to delete in the /data/system folder in TWRP are:
password.key
pattern.key
locksettings.db
locksettings.db-shm
locksettings.db-wal
It happened to me a while ago and I didn't have any '.key' files either; I just deleted the rest and when I booted up, I had no lock screen security PIN nor registered fingerprints but could re-set them again through security settings. I didn't need to flash any files nor fiddle around with adb commands, and all my data remained untouched...
If you can't find all those five files or the '.key' files, just delete the ones you can find and it should work. Otherwise, you'll probably have to do a full reset and reinstall...
Click to expand...
Click to collapse
Problem is, that I don't have any files/folders at all in my /data. I even don't see system folder inside data.
akulp said:
Problem is, that I don't have any files/folders at all in my /data. I even don't see system folder inside data.
Click to expand...
Click to collapse
Sounds like your data folder is not mounted when you boot to TWRP... Have you checked? Reboot to TWRP, select the Mount option; data should be ticked by default. It it isn't, select it, go back to TWRP file manager, and see if you can now browse folders and files...
krilok said:
Sounds like your data folder is not mounted when you boot to TWRP... Have you checked? Reboot to TWRP, select the Mount option; data should be ticked by default. It it isn't, select it, go back to TWRP file manager, and see if you can now browse folders and files...
Click to expand...
Click to collapse
Unfortunately it's checked ... It's seems from this post:
https://forum.xda-developers.com/android/software-hacking/remove-lockscreen-recovery-t3530008/page12
nobody managed to get to (encrypted) /data on Pie.
akulp said:
Unfortunately it's checked ... It's seems from this post:
https://forum.xda-developers.com/android/software-hacking/remove-lockscreen-recovery-t3530008/page12
nobody managed to get to (encrypted) /data on Pie.
Click to expand...
Click to collapse
Last comment on that thread says the solution also works on Havoc Os 2.9, which is based on Pie... Maybe that person wasn't encrypted to begin with, but, if it doesn't work for you, I guess then the only way to go is a full reset... Good luck!
krilok said:
Last comment on that thread says the solution also works on Havoc Os 2.9, which is based on Pie... Maybe that person wasn't encrypted to begin with, but, if it doesn't work for you, I guess then the only way to go is a full reset... Good luck!
Click to expand...
Click to collapse
Yep, I saw that post ... I relly don't have any more ideas. Should be inside "mount modul" in TWRP /data listed?
I only have System, Cache and SD ... and i can check System only if i check bottom "mount system partition read-only" option.
But that's nothing to do with /data.
akulp said:
Yep, I saw that post ... I relly don't have any more ideas. Should be inside "mount modul" in TWRP /data listed?
I only have System, Cache and SD ... and i can check System only if i check bottom "mount system partition read-only" option.
But that's nothing to do with /data.
Click to expand...
Click to collapse
Data option should show. At least it does on mine... You can maybe try updating Twrp version?
I'm on last TWRP.... Meantime I already made full reset ....
If you have encrypted data partition, you're pretty much banned from messing with it, unless you manage to exploit your way through the adb, which requires you to have it enabled and in trust relation with your PC to begin with.
The way I'd go around this is to place an "always yes su" binary and perform pattern removal process through init.d or similar solution. In case if su commands are restricted, kernel with permissive SELinux needs to be flashed.
On a side note, isn't this Q&A?
I also had a problem with data folder not being mounted when booting to TWRP. I tried a full reset and immediately i have access to the Data folder (but theres nothing left inside so this is kinda useless). Then later when i did a reboot into the TWRP it happened again, couldnt access to anything even when the "mount Data" option is ticked, only until i did the full reset again that it could finally work.
It turned out the problem is with the TWRP itself, i flashed another custom recovery (OrangeFox-R10-Stable-h870, which is btw a better recovery than TWRP in my opinion) and the problem never occurred again.
So either try out that new Recovery or a different version of TWRP and see if it solves the problem. And always, ALWAYS, make a full backup of all your data before messing with anything (i had to learn that the hard way so trust me).
Do this,
- you should know that I am using "orange fox recovery" not "twrp",and stock "pie"
- reboot to recovery and go to system/data
- delete this files:
gatekeeper.password.key
gatekeeper.pattern.key
locksettings.db
-reboot the phone and that's it.