I searched and read most of the help and troubleshooting section, but found no answer to the problem I face:
After uninstalling several games (and chrome) I rebooted. I swiped to be prompted for the pin entry.
The cursor blinks in the pin field, but there is no keyboard to type the pin.
I would really like to avoid a full reset (power+voldown hold),
0. because this wipes all data (pictures, videos a.s.o), is that right?
I read a lot about upgrading, rooting the x2.
1. I assume going to GEM 702L and so on would preserve all data. Is that right?
2. Will this (upgrading to GEM 702L) provide me with a keyboard when reaching the pin entry after reboot?
3. Is there a way to get my personal data off the x2 on a sd-card or the like before I make this update?
4. Would HiSuite only give me access to the device after entering the pin?
5. Is there a method of accessing the device with linux? (x2, switched on and switched off both give me a device (harddisk), only one I can mount and acces some license files)
I hope these questions can be answered, thank you
mic
Go to settings keyboard and uncheck save keyboard.
My device: 701->703 B211 xposed 86
audioralf said:
Go to settings keyboard and uncheck save keyboard.
My device: 701->703 B211 xposed 86
Click to expand...
Click to collapse
thanks, audioralf,
but I cannot "Go to settings keyboard and uncheck save keyboard" because right after booting I first have to type the pin because the phone is naturally locked and the pin-entry-field is presented.
And for typing I need a keyboard but this is just vanished, I never get to see it even if I point/klick to the pin-entry-field.
So this is my dilemma.
I hope I clarified the point: I have to unlock but have no keyboard.
Ever heard about sth like this?
You can do a Nandroid.
Which version did you use until last?
Then flash just system.img for your version.
My device: 701->703 B211 xposed 86
---------- Post added at 04:38 PM ---------- Previous post was at 04:35 PM ----------
Maybe restore system from an older Nandroid of the same version could bring back the keyboard.
My device: 701->703 B211 xposed 86
audioralf said:
You can do a Nandroid.
Which version did you use until last?
Then flash just system.img for your version.
My device: 701->703 B211 xposed 86
---------- Post added at 04:38 PM ---------- Previous post was at 04:35 PM ----------
Maybe restore system from an older Nandroid of the same version could bring back the keyboard.
My device: 701->703 B211 xposed 86
Click to expand...
Click to collapse
I'm gonna look into Nandroid, if flashing of system.img is possible without unlocking the tablet and preserving the data, which is vital. Thanks, I'll let you know.
Which version did you had before?
My device: 701->703 B211 xposed 86
Boot into TWRP and make sure data is mounted. Then go into file manager and into data/system and find locksettings.db and delete it. There may be two more locksettings files right above or below those. Delete them as well then restart. Your lock screen pin/code will be gone.
Related
This guide will help you to bypass every app locker which include gallery locker, cm locker etc etc.
For this you should be able to access the phone settings .
Go to App section .
Select the app locker.
Click Force Stop.
Now you can open the app which is locked by the app locker without password.
Best way to protect from this is to lock settings.
Note:- Some antivirus app allow to force stop app. Lock such app to protect your self.
doesn't work because Applock advanced protection activated administrator. doest allow to force stop. if you disable device administrator. it required passwork
---------- Post added at 08:40 AM ---------- Previous post was at 08:38 AM ----------
I have already tried it !!!. I have and idea I'd you have custom recovery like twrp. access file manager in recovery goto data/app find Applock/select it /then delete it/ reboot. it works.
apoorvpandey41 said:
doesn't work because Applock advanced protection activated administrator. doest allow to force stop. if you disable device administrator. it required passwork
Click to expand...
Click to collapse
Most people doesn't allow that
ok since that is the case then my guide is more effective, and smaller, and smarter
uninstall the applocker.
END.
Sorry but this is not that useful. Does anyone know how to unlock the device without damaging the data and without previous set up like this one?
apoorvpandey41 said:
doesn't work because Applock advanced protection activated administrator. doest allow to force stop. if you disable device administrator. it required passwork
---------- Post added at 08:40 AM ---------- Previous post was at 08:38 AM ----------
I have already tried it !!!. I have and idea I'd you have custom recovery like twrp. access file manager in recovery goto data/app find Applock/select it /then delete it/ reboot. it works.
Click to expand...
Click to collapse
Literally This is an hacking guide.
andrewKode said:
Sorry but this is not that useful. Does anyone know how to unlock the device without damaging the data and without previous set up like this one?
Click to expand...
Click to collapse
I am not sure. I found an app in this forum which can unlock the device whose password is forgotten. It is for Android tabs. Check that out it might help
I just purchased a Huawei Mediapad x2 Gem702-L from Amazon. I like this phone very much. It came with Android Lollipop and I would like to have Marshmallow. I do not even know where to begin with such a process and even wondered if it is possible to pay someone to do it remotely? If not, where does a newbie begin?
Grateful for any help I can receive.
Were are you located?
All guides are here, where is the problem?
My device: 701->703 B211 KangVIP AJ Xposed
I am in Millsboro, Delaware. I am new to the forum and have done a lot of digging around but am concerned that I might damage the device if I do something wrong. I see references to B211 but don't know how to determine what my device currently has. I have never rooted a device.
My build number is: GEM-702LV100R001C209B006
Android 5.0.1
EMUI: 3.0.5
Thank you for taking the time to respond to me.
702 gets ota update to marshmallow. Just use the update menue.
My device: 701->703 B211 xposed 86
audioralf said:
702 gets ota update to marshmallow. Just use the update menue.
My device: 701->703 B211 xposed 86
Click to expand...
Click to collapse
Huawei told me that the phone will not receive the update because I am in the U. S.
Alternatively you can create a folder named dload on sd and put update.app from unzipped https://www.androidfilehost.com/?fid=457095661767114936 inside.
Then tap on update and select local update. Then the file will will be shown as full update package. Then tap on install.
My device: 701->703 B211 xposed 86
Thank you for your help and patience. After clicking the folder it begins to "download resource" gets all the way to the end then displays:
"Cannot display PDF (. archivetempupdate_vendor.app is of invalid format)
Sorry indeed: the unpacked dload folder contains 4 files.
In this case all 4 files have to be present in dload when you start the update.
My device: 701->703 B211 xposed 86
audioralf said:
Sorry indeed: the unpacked dload folder contains 4 files.
In this case all 4 files have to be present in dload when you start the update.
My device: 701->703 B211 xposed 86
Click to expand...
Click to collapse
It worked! Thank you so much for helping me, I am grateful. Might I trouble you to ask if there are any updates after this one? I also own a Samsung Galaxy Note 5 running 6.0.1. I really like the stock calendar and clock as opposed to those that come from Huawei. Do you know if it is possible to install those on the Huawei?
B202 is the newest update so far for your model.
Make a Nandroid fist.
It's not rooted, so install TWRP 3.02, install supersu app and do the systemless root command: see my last post
But if it's too complicated you can install KANGVIP B211 on this B202. In this case: root and supersu app is included.
A B203 official update is now available for 702L :
http://forum.xda-developers.com/mediapad-x2/general/rom-b203-gem-702l-t3524889
audioralf said:
Sorry indeed: the unpacked dload folder contains 4 files.
In this case all 4 files have to be present in dload when you start the update.
My device: 701->703 B211 xposed 86
Click to expand...
Click to collapse
I try this and it reboots but boots into TWRP. I tried installing the zip from there but it doesn't work. I also tried with the files extracted but TWRP doesn't see any of the files when I try "install". Any help appreciated.
Edit: Nevermind, found that I needed to reinstall stock recovery to update.
Can someone point me to a b202 compatible superSU or other root method? I keep softbricking and having to restore from a backup.
Thanks
techspy said:
Can someone point me to a b202 compatible superSU or other root method? I keep softbricking and having to restore from a backup.
Thanks
Click to expand...
Click to collapse
the systemless method is effective with this super SU file:
To root install TWRP 3.02 and start the integrated TWRP terminal modus
then type
echo SYSTEMLESS=true>>/data/.supersu
and press retrurn
Then install supersu with TWRP install routine
Click to expand...
Click to collapse
yon can also try with very last super SU file (stable or not, your choice):
http://forum.xda-developers.com/apps/supersu
Djiban said:
the systemless method is effective with this super SU file:
yon can also try with very last super SU file (stable or not, your choice):
http://forum.xda-developers.com/apps/supersu
Click to expand...
Click to collapse
Thanks. That method worked
Hi, is there any solution to the push notifications such as Facebook, WhatsApp etc without locking them in the task manager?
I made sure they wont close when the screen is locked and dont know if there are more things to do.
Thanks
Many apps need google services for push.
Check if you have it via https://play.google.com/store/apps/details?id=com.weberdo.apps.serviceinfo
My device: Mate 9 superroot, Mediapad X2 GEM 701->703 B212 KangVIP (AJ mod)
Liranzukz said:
Hi, is there any solution to the push notifications such as Facebook, WhatsApp etc without locking them in the task manager?
I made sure they wont close when the screen is locked and dont know if there are more things to do.
Thanks
Click to expand...
Click to collapse
in addition to lock the app you need to enable the notifications and also enable full permissions to the apps you want to get notifications that is the only way I can get notifications without rooting or rebranding
audioralf said:
Many apps need google services for push.
Check if you have it via https://play.google.com/store/apps/details?id=com.weberdo.apps.serviceinfo
My device: Mate 9 superroot, Mediapad X2 GEM 701->703 B212 KangVIP (AJ mod)
Click to expand...
Click to collapse
I have the latest version. It seems like the app locking is the only solution at the moment without rooting/rebranding.
Hi all!
This is my bundle of some tweaks and fix for daisy.
All tested. Any fix (if it need) make autobackup original files with suffix .bck.
Install it from TWRP and have fun
Fix sim-card after change Android version
fix sims and mobile cells after downgrade from pie to oreo
Disable force encryption
you know it
Tuning fingerprint's gestures
disable annoying gestures and using new: swipe from left2right is "paste-text-from-buffer", swipe from up2down is "wakeup-screen"
25 steps in volume regulators
fine tuning volume
AdAway replacement (hosts)
anti prn-spam-ads-scram for all apps (very conservative blocking!!!)
.
Selinux changer?
blue4 said:
Selinux changer?
Click to expand...
Click to collapse
i don't want remake it
use Permissiver_v2.zip from xda
.
Thanks
---------- Post added at 05:35 AM ---------- Previous post was at 04:50 AM ----------
Can you use modemfix run.sh in fastboot mode? Just wondering.
locovibe said:
Thanks
---------- Post added at 05:35 AM ---------- Previous post was at 04:50 AM ----------
Can you use modemfix run.sh in fastboot mode? Just wondering.
Click to expand...
Click to collapse
i don't know how work fastboot to run shell command or anything else
give me a point for information
My fingerprint don't complete the register. How to solve this? Thanks for the fix
Vitor00 said:
My fingerprint don't complete the register. How to solve this? Thanks for the fix
Click to expand...
Click to collapse
it is not possible if you using pie stock with gsi
you need oreo stock for complete fp works
sorry if this sounds like a stupid quesiton, but why do we need to disable force encryption?
xiujk71 said:
sorry if this sounds like a stupid quesiton, but why do we need to disable force encryption?
Click to expand...
Click to collapse
i do it on oreo for twrp to work it fully
some gsi need this
with forceencrytion disabled phone works a little faster
eremitein said:
i do it on oreo for twrp to work it fully
some gsi need this
with forceencrytion disabled phone works a little faster
Click to expand...
Click to collapse
icic, thanks for reply
disable encryption for twrp to work, is it for the mounting of internal storage?
Will removing encryption force a data wipe?
xiujk71 said:
is it for the mounting of internal storage?
Click to expand...
Click to collapse
yep
bast525 said:
Will removing encryption force a data wipe?
Click to expand...
Click to collapse
not sure
as i know you need format data after disabling enc
Modem Fix 10.0.3
THX
Disable encryption
Just in case, is worth to say, disable encryption worked for me flashing it before the first boot, or you have to format data
Are these fix permanent? In the sense, sorry for ignorance, if I format the system will the fixes remain?
Henki98 said:
Are these fix permanent? In the sense, sorry for ignorance, if I format the system will the fixes remain?
Click to expand...
Click to collapse
only two first fixes will be remained
Anyone have the fix for the overlay on treble? , i found it on "4pda.ru" forum , is called "treble-overlay-xiaomi-daisy.apk" but i cant download it, link is broken.
I have flash disable force encryption after format data by twrp, successfully installs it, but why when I restart the phone it is encrypted again and twrp does not recognize the internal memory again
I'm on oreo, tell me what passage I forget?
Henki98 said:
I have flash disable force encryption after format data by twrp, successfully installs it, but why when I restart the phone it is encrypted again and twrp does not recognize the internal memory again
I'm on oreo, tell me what passage I forget?
Click to expand...
Click to collapse
if you on stock then you need flash magisk after formated data and installed disabler
Hi all,
I have a Huawei Mate 9 (MHA-L09C432) with EMUI 9.1 on it and an unlocked booloader with Magisk installed.
Because I want to modify root settings I would like to have full root access...
Is there a method now to get full root access with EMUI 9.1?
Thank you for your answers in advance!
htcdesire-hd said:
Hi all,
I have a Huawei Mate 9 (MHA-L09C432) with EMUI 9.1 on it and an unlocked booloader with Magisk installed.
Because I want to modify root settings I would like to have full root access...
Is there a method now to get full root access with EMUI 9.1?
Thank you for your answers in advance!
Click to expand...
Click to collapse
You have Magisk and that's the root. 'Classic/full root' is no more possible because of EROFS. Only systemless root functionality provided by Magisk
zgfg said:
You have Magisk and that's the root. 'Classic/full root' is no more possible because of EROFS. Only systemless root functionality provided by Magisk
Click to expand...
Click to collapse
Ok thats bad, hoped that there is a solution now...
Is that EMUI related or will no future Android phone have "real" root?
But a SW downgrade would bring back real root?
htcdesire-hd said:
Ok thats bad, hoped that there is a solution now...
Is that EMUI related or will no future Android phone have "real" root?
But a SW downgrade would bring back real root?
Click to expand...
Click to collapse
EROFS means read-only file system, developed by Huawei, used in EMUI 9.1 and 10.
Google is pushing that system must not be changed, and it is similarly enforced in other phones with Android 10.
Read discussions in Magisk and Magisk Canary threads on XDA, even better topjohnwu's (developer of Magisk) blog on Reddit, to understand in which direction (systemless) it goes and why.
By HiSuite you should be able to downgrade from EMUI 9.1 to 9.0 (prior to EROFS)
zgfg said:
EROFS means read-only file system, developed by Huawei, used in EMUI 9.1 and 10.
Google is pushing that system must not be changed, and it is similarly enforced in other phones with Android 10.
Read discussions in Magisk and Magisk Canary threads on XDA, even better topjohnwu's (developer of Magisk) blog on Reddit, to understand in which direction (systemless) it goes and why.
By HiSuite you should be able to downgrade from EMUI 9.1 to 9.0 (prior to EROFS)
Click to expand...
Click to collapse
Ok thanks for the explanation. Doesn't sound good for me... But maybe there will be a solution like reformatting in future I hope to get "real" root!
Thanks for the tip, I will do so.
Good I will do that!
htcdesire-hd said:
Ok thanks for the explanation. Doesn't sound good for me... But maybe there will be a solution like reformatting in future I hope to get "real" root!
Thanks for the tip, I will do so.
Good I will do that!
Click to expand...
Click to collapse
It's unlikely that you'd be able to change the partition types back to ext4 - one of the other things to note about EROFS is that at least some of the contents are compressed, and as a result the system partition is smaller than it was with ext4. It's likely the same is true of all of the other partitions though I haven't checked. But in any case, there likely isn't enough physical space to store a repacked EMUI 9.1 image set in the new partitions.
irony_delerium said:
It's unlikely that you'd be able to change the partition types back to ext4 - one of the other things to note about EROFS is that at least some of the contents are compressed, and as a result the system partition is smaller than it was with ext4. It's likely the same is true of all of the other partitions though I haven't checked. But in any case, there likely isn't enough physical space to store a repacked EMUI 9.1 image set in the new partitions.
Click to expand...
Click to collapse
Ok I understand...
I saw that you can unpack the EROFS partition in a virtual environment, remove or modify system files and repack it...
But that's to complicated for my purpose...
irony_delerium said:
It's unlikely that you'd be able to change the partition types back to ext4 - one of the other things to note about EROFS is that at least some of the contents are compressed, and as a result the system partition is smaller than it was with ext4. It's likely the same is true of all of the other partitions though I haven't checked. But in any case, there likely isn't enough physical space to store a repacked EMUI 9.1 image set in the new partitions.
Click to expand...
Click to collapse
I tried to downgrade but it failed (probably because I have a Magisk patched recovery).
So I tried to install the stock recovery but I can't boot into Fastboot... (I shut down my phone, hold down volume and plugged in USB ... also rebooting to fastbood via ADB did not work -> always booting to system).
What can I do about that? Factory reset? Or is this a known issue with EMUI 9.1?
htcdesire-hd said:
I tried to downgrade but it failed (probably because I have a Magisk patched recovery).
So I tried to install the stock recovery but I can't boot into Fastboot... (I shut down my phone, hold down volume and plugged in USB ... also rebooting to fastbood via ADB did not work -> always booting to system).
What can I do about that? Factory reset? Or is this a known issue with EMUI 9.1?
Click to expand...
Click to collapse
Let it boot to system and use Magisk manager to uninstall it. The 9.1 fastboot doesn't pay attention to the button state if it thinks it should be booting into recovery, and that flag persists as long as stock recovery hasn't booted.
irony_delerium said:
Let it boot to system and use Magisk manager to uninstall it. The 9.1 fastboot doesn't pay attention to the button state if it thinks it should be booting into recovery, and that flag persists as long as stock recovery hasn't booted.
Click to expand...
Click to collapse
Unfortunatelly Magisk says "stock backup does not exist" when I try to uninstall ...
htcdesire-hd said:
Unfortunatelly Magisk says "stock backup does not exist" when I try to uninstall ...
Click to expand...
Click to collapse
Then instead, take your stock recovery image, and from a PC:
adb push recovery_ramdisk.img /sdcard/recovery_ramdisk.img
adb shell
su
dd if=/sdcard/recovery_ramdisk.img of=/dev/block/bootdevice/by-name/recovery_ramdisk
irony_delerium said:
Then instead, take your stock recovery image, and from a PC:
adb push recovery_ramdisk.img /sdcard/recovery_ramdisk.img
adb shell
su
dd if=/sdcard/recovery_ramdisk.img of=/dev/block/bootdevice/by-name/recovery_ramdisk
Click to expand...
Click to collapse
Thank you very much, that worked!
I was not able to do that via ADB but I used the Android App "Termius" which has a local terminal.
Now I was able to remove Magisk, downgrade and root my phone again decently!
One last question: how can I prevent update notifications now?
htcdesire-hd said:
One last question: how can I prevent update notifications now?
Click to expand...
Click to collapse
Code:
adb shell pm disable-user com.huawei.android.hwouc
For that, even root is not required.
And you can always re-enable System Update by:
Code:
adb shell pm enable
com.huawei.android.hwouc
zgfg said:
Code:
adb shell pm disable-user com.huawei.android.hwouc
For that, even root is not required.
And you can always re-enable System Update by:
Code:
adb shell pm enable
com.huawei.android.hwouc
Click to expand...
Click to collapse
Thank you very much, that worked!
htcdesire-hd said:
Thank you very much, that worked!
I was not able to do that via ADB but I used the Android App "Termius" which has a local terminal.
Now I was able to remove Magisk, downgrade and root my phone again decently!
Click to expand...
Click to collapse
Apparently, you had root still working (if I correctly understand your long story).
In that case you could have also flashed stock Recovery by EMUI Flasher apk from post #1 at:
https://forum.xda-developers.com/mate-20-pro/how-to/guide-manual-updating-firmware-t3893171
zgfg said:
Apparently, you had root still working (if I correctly understand your long story).
In that case you could have also flashed stock Recovery by EMUI Flasher apk from post #1 at:
https://forum.xda-developers.com/mate-20-pro/how-to/guide-manual-updating-firmware-t3893171
Click to expand...
Click to collapse
Thank you for the tip!
zgfg said:
Code:
adb shell pm disable-user com.huawei.android.hwouc
For that, even root is not required.
And you can always re-enable System Update by:
Code:
adb shell pm enable
com.huawei.android.hwouc
Click to expand...
Click to collapse
I have one problem after setting up my phone again completely:
I can't connect to WIFI hotspots anymore... It tries to connect but ends in "connection timed out"...
What could cause this problem?
I restored my WIFI connections via Titanium Backup, could that cause a problem?
htcdesire-hd said:
I have one problem after setting up my phone again completely:
I can't connect to WIFI hotspots anymore... It tries to connect but ends in "connection timed out"...
What could cause this problem?
I restored my WIFI connections via Titanium Backup, could that cause a problem?
Click to expand...
Click to collapse
I would not restore by Titanium (specially if changing a firmware) but lby the stock Backup app (or HiSite, it's PC counterpart).
It can also backup/restore WiFi connections and with that I even successfully transfered my WiFi passwords from P9 Oreo to Mate 9 Pie
(You can select which parts you want to restore and if there are incompatible settings, it will not offer that part for restoring to the new Huawei device/firmware)
zgfg said:
I would not restore by Titanium (specially if changing a firmware) but lby the stock Backup app (or HiSite, it's PC counterpart).
It can also backup/restore WiFi connections and with that I even successfully transfered my WiFi passwords from P9 Oreo to Mate 9 Pie
(You can select which parts you want to restore and if there are incompatible settings, it will not offer that part for restoring to the new Huawei device/firmware)
Click to expand...
Click to collapse
I didn't make a backup with HiSuite...
But I solved the problem by resetting the network settings:
Settings -> System -> Reset -> Reset Network Settings