Hello,
I tried to flash the mediapad with the official European B006 Rom. It won't work, I always got the error Software install failed. So I unlocked the pad, unzipped the official rom and flashed the Pad via fastbbot. (boot.img, User.img, recovery.img and system.img). After reboot the pad worked and shows the B006 version on the about the tablet app.
There are two things that are not working.
1. Fingerprint
After installing one print during the first configuration, I can't start the setting pof fingerpront. If I choose it, the settings app ends.
2. Auto-rotate
Auto-Rotation works in all the apps, but not on the homescreen
Any suggestions?
Thanks,
Michael
schmulx said:
Hello,
I tried to flash the mediapad with the official European B006 Rom. It won't work, I always got the error Software install failed. So I unlocked the pad, unzipped the official rom and flashed the Pad via fastbbot. (boot.img, User.img, recovery.img and system.img). After reboot the pad worked and shows the B006 version on the about the tablet app.
There are two things that are not working.
1. Fingerprint
After installing one print during the first configuration, I can't start the setting pof fingerpront. If I choose it, the settings app ends.
2. Auto-rotate
Auto-Rotation works in all the apps, but not on the homescreen
Any suggestions?
Thanks,
Michael
Click to expand...
Click to collapse
2. auto rotate
long press the main screen> other settings> enable auto rotate. should be there. look around.
Sorry, but that won't work. On other units I had this switch but not here.
Related
Hello,
I had just flashed CM10.1, and to reiterate the title, experiencing issues that I could not find answers for.
First: Why is Auto Rotation not working? (have already looked into settings, all check out)
Second: Where is the button(the one with three dots on the bottom bar in the right corner that appears in apps, i think it was made to open in app settings) not there?
Third: (may or may not be because of rom) Kindle Fire does not connect to computer and be detected whatsoever( it did work when i had and older version of TWRP, just had to mount usb in recovery, but when i did update TWRP, it stopped appearing in computer even when mounted)
I Flashed this build:cm-10.1-20130611-0025-otter-sgt7, which i downloaded from this thread:http://forum.xda-developers.com/showthread.php?t=20513
If anyone can help, thank you, my frustration is starting to get the better of me.
1. Not sure about this one. When I used the 6-11 build rotate worked. Now I'm on cm 10.1 official "stable" and rotate doesn't work.
2. Go to settings - system -hardware keys, and check "show action overflow".
3. Try reinstalling the drivers you used to root your kf. Try reinstalling multiple times if it doesn't work at first. Eventually it showed up for me.
Cheers!
Sent from my ADR6400L using Tapatalk 2
same here. when I flashed the official cm10.1 2013 otter, my auto rotation would not work. This also happen on the last RC zips. When I flash the latest Nightlies 0624, all is well.
Not sure about this one.
Rotation works on smooth ROM (cm 10.1)
Sent from my Amazon Kindle Fire using xda app-developers app
I'm having the same issue with my KF regarding PC recognition. I've tried installing the drivers a million times and I just can't install them again for some reason. I'm stuck at this point.
Try and wipe the cache, dalvik, etc. and do a fresh install of the .zip, because mine works fine. I had trouble before with connecting to PC via USB, but re-installed and enabled USB debugging and now it is working fine!
probs with kindle 1stgen&cm10.1&playstore
hi, i´ve installed cm-10.1.0-otte.zip (run´s perfect, but playstore not run´s) - and afterwards (playstore probs) i installed also gapps-jb-2013ß3ß1-signed.zip. now i received the message "device wizard ends" .. permanantly...
pls help
thx cosmic
Model : Lenovo Vibe K5
Running on : Lineage os 14.1
Flashed with : TWRP
The issue is the phone is showing strange behaviour. It worked fine for a couple of days after flashing.
If I boot into bootloader or recovery, phone stucks on LENOVO LOGO screen and nothing happens even after few hours.
If we boot it normally,
1) No camera option on lock screen. If opened from drawer, no front camera option.
2) Status bar pulls down only half way.
3) Nothing on status bar except mobile data.
4) Home & recent apps button doesn't work
5) Settings >> Users (frozen)
6) If developer settings opened, "developer options are not available for this user"
7) Factory Reset button Frozen.
8) No root access!!
manaspustake said:
Model : Lenovo Vibe K5
Running on : Lineage os 14.1
Flashed with : TWRP
The issue is the phone is showing strange behaviour..
If I boot into bootloader or recovery, phone stucks on LENOVO LOGO screen and nothing happens even after few hours.
If we boot it normally,
1) No camera option on lock screen. If opened from drawer, no front camera option.
2) Status bar pulls down only half way.
3) Nothing on status bar except mobile data.
4) Home & recent apps button doesn't work
5) Settings >> Users (frozen)
6) If developer settings opened, "developer options are not available for this user"
7) Factory Reset button Frozen.
8) No root access!!
Click to expand...
Click to collapse
It is better to address these issues to the developer who made your lineage os 14.1 or u might have dirty flashed it. I recommend you to make full wipes and install it again.
Sent from my Galaxy j5 using Tapatalk
Aadars said:
It is better to address these issues to the developer who made your lineage os 14.1 or u might have dirty flashed it. I recommend you to make full wipes and install it again.
Sent from my Galaxy j5 using Tapatalk
Click to expand...
Click to collapse
It was working fine a few hours ago, without those issues mentions above. It suddenly came up with the following issues.
How can I full wipe and install, as I have no access to recovery or bootloader.
manaspustake said:
It was working fine a few hours ago, without those issues mentions above. It suddenly came up with the following issues.
How can I full wipe and install, as I have no access to recovery or bootloader.
Click to expand...
Click to collapse
You should search/post this question within the following Official LineageOS thread for your device.
[ROM][OFFICIAL][7.1] LineageOS/CM14.1 for the Lenovo K5/K5 Plus [VoLTE][Weeklies] by scritch007
Good Luck!
"Live Long and Prosper..."
~Ambassador S'chn T'gai Spock
Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise
I'm trying to get dialler funtionality on my Huawei M2 802L.
I now realised I ***** myself by manually upgrading to Marshmallow.
1.
Marshmallow removed the "Enable OEM Unlock" option.
2.
I can't update to this ROM: https://forum.xda-developers.com/me...-b207-android-6-0-marshmallow-emui-4-t3533572
In Settings -> Update -> Menu the "update locally" button is replaced by "Download latest full package".
3.
I can't find a Huawei M2 rollback package. Is there one?
What's my next move guys?
Update: I found the dial *#*#2846579#*#* trick to update thru SD card.
The problem is dialer is still down. I'm not sure how to verify the ROM install properly either.
Does anyone know an alternative way to do this: http://www.modaco.com/forums/topic/...enable-calls-on-your-vodafone-mediapad-m2-80/
RE : When you upgrade to Marshmallow...
calLsOLoIsNOob said:
I'm trying to get dialler funtionality on my Huawei M2 802L.
I now realised I ***** myself by manually upgrading to Marshmallow.
1.
Marshmallow removed the "Enable OEM Unlock" option.
2.
I can't update to this ROM: https://forum.xda-developers.com/me...-b207-android-6-0-marshmallow-emui-4-t3533572
In Settings -> Update -> Menu the "update locally" button is replaced by "Download latest full package".
3.
I can't find a Huawei M2 rollback package. Is there one?
What's my next move guys?
Update: I found the dial *#*#2846579#*#* trick to update thru SD card.
The problem is dialer is still down. I'm not sure how to verify the ROM install properly either.
Does anyone know an alternative way to do this: http://www.modaco.com/forums/topic/...enable-calls-on-your-vodafone-mediapad-m2-80/
Click to expand...
Click to collapse
Hello calLsOLoIsNOob,
Would you mind to specify what kind of issues you have with the dialer please ?
I bought my M2-801L tablet 6-8 months ago, updated it through various OTA updates until the last B208 one (if you need links check my post here -> https://forum.xda-developers.com/showpost.php?p=77201067&postcount=163 ), and never had issues of any kind with the stock dialler. I use it for daily basis calls (in and outgoing) with all features and advanced settings needed to have an optimized dialling module and HQ calls.
Indeed, what goes on Dev. options, "OEM Unlock" has disappeared from it, and agree with you it's a shame. Does the Huawei's Bootloader unlock might replace this function ?
What goes about rollback procedure, can't help much, never had to use it so far.
NB : My M2 8.0 model is EU one, don't know if there are any major differences with same model from other countries / continents / GSM Providers.
Thank you in advance for your reply.
Have a nice day.
Kind Regards.
Global Update is there.
For those who installed it already, give us some feedback.. and one question, should factory rested be done before or after installing update? What is better, because i never did reset before, just apply update, but now would like to do reset also..
Works fine without reset. Smartphone was very hot during update. After installation I made a reboot. All Apps are working and Dark Mode is now available for most Apps.
This update broke my GooglePay, no longer passing ctsProfile in safetynet.
Seems to work fine. Before this update I was getting more and more bugs, but they seem to be gone now. Rebooting after the update took a long time, however. I was stuck on the Mix logo for 5-10 minutes.
There are some visual tweaks here and there, but that's all I can notice.
Themes available, region uk!
Latest update has caused my home launcher to crash. Am only able to use it cause of 3rd party launcher.
Does Magisk patched boot work with this? I was stuck a boot screen for over 10 mins before I had to reflash stock boot.img.
*update*
I had an out of date version of exposed installed that caused boot loop.
I can't install work email, and because my phone is CN region, of course, Google Pay not working. Not sure if boot options for the kernel changed, going to look and see if I need to update my flashable patcher zip.
blue1978 said:
Does Magisk patched boot work with this? I was stuck a boot screen for over 10 mins before I had to reflash stock boot.img.
Click to expand...
Click to collapse
Yes...work perfectly.
blue1978 said:
Does Magisk patched boot work with this? I was stuck a boot screen for over 10 mins before I had to reflash stock boot.img.
Click to expand...
Click to collapse
Not with the latest stable version. Take a look here so solve your problem: https://github.com/topjohnwu/Magisk/issues/2492#issuecomment-593149828
Any updates on anyone getting magisk to work on this? Can I use magisk patch with just the boot.img extracted from the OTA update .zip file?
I have the international not a china model.
Anybody found a solution for viper4android? I tried rootless 2.7 but driver will not install.
Quality_con_troll said:
Any updates on anyone getting magisk to work on this? Can I use magisk patch with just the boot.img extracted from the OTA update .zip file?
I have the international not a china model.
Click to expand...
Click to collapse
Magisk works.
But my ctsProfile fails on the safetynet.
Rendering GooglePay and PokemonGo unusable, which wasn't an issue for me before.
Also am international model.
After this update,
I was struggling to boot TWRP at first,
But my issue stemmed from trying to use adb / fastboot commands to boot into TWRP recovery, which only took me to stock recovery.
I got my Magisk back by doing a "fastboot flash recovery TWRP.img"
And then manually used the volume up + power button to boot TWRP (I used the unofficial mauronofrio)
And from there just install the Magisk zip.
spyke180 said:
Magisk works.
But my ctsProfile fails on the safetynet.
Rendering GooglePay and PokemonGo unusable, which wasn't an issue for me before.
Also am international model.
After this update,
I was struggling to boot TWRP at first,
But my issue stemmed from trying to use adb / fastboot commands to boot into TWRP recovery, which only took me to stock recovery.
I got my Magisk back by doing a "fastboot flash recovery TWRP.img"
And then manually used the volume up + power button to boot TWRP (I used the unofficial mauronofrio)
And from there just install the Magisk zip.
Click to expand...
Click to collapse
Just went through this process myself and came back here now to report on it.
This was my process for anyone also looking for guidance.
This will work for the new android 10 updated. I came from MIUI10 (10.0.3.2.0) using system update to go to MIUI11 and android 10 (11.0.3.0) via OTA update, which reverted to stock recovery and obviously lost root as well.
1. Saved most recent twrp 3.3.1-7-recovery.img for perseus by mauronofrio found in these XDA threads, magisk 20.3.zip found on magisk site and repository, and just to be sure disable forced encryption-treble.zip (just search for it) to my phone AND adb directory on Windows 10 computer.
ENSURE USB IS PLUGGED INTO 2.0 or 2.0 COMPATABILE HUB (Flashing recovery failed when connected to a USB3.0 port) and ADB/FASTBOOT is installed on your computer.
2. Booted into fastboot. (Power + Volume down)
3. Ran cmd.exe and entered "cd C:/(wherever you installed/platform-tools" without quotes.
4. Entered "fastboot devices" to ensure fastboot is connected. It should show device_id# and fastboot next to that.
5. Flashed TWRP3.3.1-7 for MiMix3 perseus (latest unofficial TWRP) by entering "fastboot flash recovery twrp3.3.1-7-recovery.img"
6. Entered "fastboot reboot recovery" the phone will reboot now, ENSURE YOU HOLD VOL+ ASAP or you will lose TWRP with stock recovery.
7. After booting into TWRP, entered password, wiped data and cache only.
8. In TWRP go to install and choose your disable_forced_encryption-treble.zip and flash it but do not select reboot device, it is selected by default.
(NOTE: Don't know if #8 is a necessary step especially for Global devices but did it anyways and it didn't hurt anything)
9. Go to install again and choose magisk20.3.zip, this time you can select reboot device.
10. After completing android setup download magisk manager 7.5.1 from play store and verify 20.3 is installed, if it is then congrats, you're rooted.
That's it! Like the above post said ctsProfile is reading false meaning you most likely will not be able to use Pay apps like Google Pay, etc.
Other apps that use google play services for verification may not work as well like Pokemon GO, Mario Kart, Harry Potter, or other banking/security apps. (Not sure about this one yet, try MagiskHide in the manager. Spyke180 is reporting above they do not work currently.) So if you can't live without Samsung Pay, or one of these games wait until a ctsProfile:true/SafetyNet passes solution is available.
Hopefully the next magisk update or someone in the community will be able to solve these issues in a timely manner, shouldn't be much of a wait.
Hope this made sense and can help some peeps out there perhaps.
CTSProfile is failing on my device as well. I tried using the boot cmdline patcher I made and it's still failing. I am wondering if Xiaomi released this update before getting the fingerprint in the CTS approved list. I can't think of anything else. My device is a CN device, so the BL is unlocked. I don't know if flashing Magisk with CN device and Global software still results in a boot loop but may try it.
Also, Magisk is detected through some methodology. I read all the posts made in both the release and beta threads in the last 3 days and it seems broken for everyone.
MMS stopped automatically sending and receiving on Google Messages app. But somehow works flawlessly on stock texting app. Notification tells me "Can't send MMS message. Tap to allow MMS messaging on (Carrier) when mobile data is off". Tapping the notification yields nothing. Even a factory reset does nothing.
siuyan187 said:
MMS stopped automatically sending and receiving on Google Messages app. But somehow works flawlessly on stock texting app. Notification tells me "Can't send MMS message. Tap to allow MMS messaging on (Carrier) when mobile data is off". Tapping the notification yields nothing. Even a factory reset does nothing.
Click to expand...
Click to collapse
If you go into settings, and then to "SIM cards & mobile networks", is the "Always receive MMS" toggle in the on position (blue)?
spyke180 said:
If you go into settings, and then to "SIM cards & mobile networks", is the "Always receive MMS" toggle in the on position (blue)?
Click to expand...
Click to collapse
Yep. Both in system settings and also in the app settings. Tried turning one on and the other off in different combinations, but still doesn't work.
siuyan187 said:
Yep. Both in system settings and also in the app settings. Tried turning one on and the other off in different combinations, but still doesn't work.
Click to expand...
Click to collapse
I see.
If you're rooted, you could try using the systemize module to make it a system app.
I verified my Google Messages and its notifications are working for me, even with both Wi-Fi and mobile data turned off.
Hi there. I'm new to Xiaomi/MIUI and would appreciate any help with the following issues.
Mi 10T – Global Stable 12.0.8 – stock launcher – MIUI optimization ON – de-bloated with ADB
I can't see how much storage space is being taken up by each installed app/package. They all show a "0" value.
I can't find Running Services under Developer Options.
I can't permanently disable usage access for System Launcher. It re-enables itself once I exit the settings menu.
App icons aren't updating. For example, Gmail, Maps, Photos and FB Messenger still display their old icons, despite me using the latest versions of those apps.
Google Play still displays the older menu style, despite me using the latest version of that app.
System Apps Updater doesn't detect OTA updates, despite several newer versions of MIUI 12 system apps existing on APK Mirror. This issue presented itself before I began de-bloating.
Updater doesn't detect OTA updates. I had to sideload 12.0.8 in order to update from the phone's original OS version (12.0.7). This issue presented itself before I began de-bloating.
Full disclosure: I'd rather not turn off MIUI optimization to see if that resolves any of these issues, as I'm not keen on resetting permissions (again).
Edit:
When I uninstall an app via the app drawer, a gap is left in its place. The icon of the uninstalled app is still there, it just turns invisible. I can uninstall it over and over, but it doesn't go away until I reboot the phone.
There doesn't appear to be a way to turn off the phone's equalizer. I can't use Blackplayer's equalizer until I do so. I don't know if the same applies to other music players.
Edit:
There doesn't appear to be a way to add emergency contacts or access them via the lockscreen emergency dialer. Emergency information (com.android.emergency) exists within the list of installed apps.
I'm on Global 12.0.7, unlocked, rooted and debloated. Stock recovery. What did you exactly do to update to 12.0.8? I do not want to wipe and I'm a little confused with the procedure...
sergio_sant said:
I'm on Global 12.0.7, unlocked, rooted and debloated. Stock recovery. What did you exactly do to update to 12.0.8? I do not want to wipe and I'm a little confused with the procedure...
Click to expand...
Click to collapse
I downloaded it from here, went to About Phone in Settings, clicked on the OS version number in the top left, clicked on the 3-dot menu in the top right and installed it via Mi File Manager.
AFAIK, you can only use Mi File Manager to install the update via this method. If you've disabled or uninstalled it, nothing will happen when you click that menu option – even if you've installed another file manager.
Dagabix said:
I downloaded it from here, went to About Phone in Settings, clicked on the OS version number in the top left, clicked on the 3-dot menu in the top right and installed it via Mi File Manager.
AFAIK, you can only use Mi File Manager to install the update via this method. If you've disabled or uninstalled it, nothing will happen when you click that menu option – even if you've installed another file manager.
Click to expand...
Click to collapse
I just tried this. It reboots and starts updating... but goes from 0.X% to 100% in two seconds, then it boots and it's still 12.0.7
sergio_sant said:
I just tried this. It reboots and starts updating... but goes from 0.X% to 100% in two seconds, then it boots and it's still 12.0.7
Click to expand...
Click to collapse
That sucks. It worked just fine for me. Don't know what else to suggest.
Dagabix said:
That sucks. It worked just fine for me. Don't know what else to suggest.
Click to expand...
Click to collapse
Finally I booted into TWRP and flashed 12.0.9 from there, no issues.