Since nougat was released for our XZ I noticed that even stock ROMs Miracast feature broken from the jump, hell even nougat update on Nexus 5x and 6p broke Miracast as well. This is a guide to fix that.
SPECIAL THANKS TO @maksim_kw FOR SHOWING ME THE WAY AWHILE BACK.
REQUIREMENTS:
Root
ADB set up on a Computer
Root File explorer/text editor
INSTALLATION:
Go to system/etc and find file wfdconfig.xml
Then find this line and change
- enable HDCP by default -->
<ContentProtection>
<Valid>1</Valid>
To
- enable HDCP by default -->
<ContentProtection>
<Valid>0</Valid>
Then save
Then go to system/ and find build prop
Find this block
#property to enable user to access Google WFD settings
persist.debug.wfd.enable=1
##property to choose between virtual/external wfd display
persist.sys.wfd.virtual=0
Then add this line
persist.sys.wfd.appmonitoring=1
So it looks like this
#property to enable user to access Google WFD settings
persist.debug.wfd.enable=1
persist.sys.wfd.appmonitoring=1
##property to choose between virtual/external wfd display
persist.sys.wfd.virtual=0
Then save
Then connect to adb and run theses codes
Adb shell
Su
setprop persist.debug.wfd.appmonitoring 1
Reboot
And it's working again ! ?
Leave a thanks if this worked for you
I did this yesterday on my Xperia XZ running 39.2.A.0.417
and the phone was bricked. It was stuck in a bootloop. It never got past the SONY logo.
Then I tried to undo the mod by replacing the 2 files with the originals
/system/build.prop
/system/etc/wfdconfig.xml
And it is still stuck in the bootloop.
Should I just run the command:
setprop persist.debug.wfd.appmonitoring 0
to undo this mod ?
I hope it will boot again then.
I don't know what I did wrong. I didn't use adb and the computer. I did all the steps on the phone itself. Maybe that's what caused the bootloop?!
lebigmac said:
I did this yesterday on my Xperia XZ running 39.2.A.0.417
and the phone was bricked. It was stuck in a bootloop. It never got past the SONY logo.
Then I tried to undo the mod by replacing the 2 files with the originals
/system/build.prop
/system/etc/wfdconfig.xml
And it is still stuck in the bootloop.
Should I just run the command:
setprop persist.debug.wfd.appmonitoring 0
to undo this mod ?
I hope it will boot again then.
I don't know what I did wrong. I didn't use adb and the computer. I did all the steps on the phone itself. Maybe that's what caused the bootloop?!
Click to expand...
Click to collapse
I dont think thay would brivk your device, and you should have a backup
All I had to do to fix my screen mirroring disconnection issue in Nougat was to simply flash the device keys DK.ftf using the old Flashtool 0.9.22.3
Now that my FIDO keys are provisioned, the screen mirroring works again.
@Smacksmack206
Working fine with my sony xz dual
Confirmed still working in latest FW 7.1.1.
tried your procedure on my nexus 6 nougat 7.1.1
unfortunately casting still doesn't work
tried with sony and Samsung smart tvs
it gets as far as preparing screen mirroring
and then after a while it disconnects
marisaleh said:
tried your procedure on my nexus 6 nougat 7.1.1
unfortunately casting still doesn't work
tried with sony and Samsung smart tvs
it gets as far as preparing screen mirroring
and then after a while it disconnects
Click to expand...
Click to collapse
Well you can try to download the version on my GitHub maybe that might work. I never tried this on my 5x since I got my xz 3 months ago
sorry I don't understand, what version
and how do I access your GetHub
once again I am on nexus 6 running Nougat version 7.1.1
tried your instructions for screen cast and didn't work
marisaleh said:
sorry I don't understand, what version
and how do I access your GetHub
once again I am on nexus 6 running Nougat version 7.1.1
tried your instructions for screen cast and didn't work
Click to expand...
Click to collapse
https://github.com/Smacksmack206/Sony-Xperia-XZ/blob/master/wfdconfig.xml
You can try it not sure if it will work on n6 but it works on xz
thank you for that
I've just tried it on my nexus 6 and unfortunately it didn't work
marisaleh said:
thank you for that
I've just tried it on my nexus 6 and unfortunately it didn't work
Click to expand...
Click to collapse
It was worth a shot, makes me wonder what they did and how to fix it in your end, on the xz it was kinda easy to fix
WOW man @Smacksmack206 thank you so much!
Confirmed working on XZ running Existenz 7. Now I can mirror my screen with Miracast
Cheers!
Does anyone success on XZ Premium?
I think they are same but I failed......
I got my miracast 4 days ago
And its 100% working
Using stock room
Nougat 7.1.1
Should this method still works on Oreo?
---------- Post added at 10:42 AM ---------- Previous post was at 10:18 AM ----------
Answer IS YES!!!!
I've spoken a bit too fast... the casting works for a few seconds, then the phone disconnect form the TV. Any hint on how to be able to cast phone screen to TV with Oreo?
Thanks.
edit: OK... it seems that casting works, but is limited to music, settings, and xperia launcher... if I try to go to anything else, it automatically disconnects. some king of locking of any other content. is there any solution? Is this related to DRM?
sensei_sai said:
I've spoken a bit too fast... the casting works for a few seconds, then the phone disconnect form the TV. Any hint on how to be able to cast phone screen to TV with Oreo?
Thanks.
edit: OK... it seems that casting works, but is limited to music, settings, and xperia launcher... if I try to go to anything else, it automatically disconnects. some king of locking of any other content. is there any solution? Is this related to DRM?
Click to expand...
Click to collapse
You did it wrong some where in the procedure redo it again, double check the config file you made edits to, double check the adb commands, simply do it over lol you shouldn't get restrictions if you do it correctly. I no longer have an XZ but I can somewhat assist u
Smacksmack206 said:
You did it wrong some where in the procedure redo it again, double check the config file you made edits to, double check the adb commands, simply do it over lol you shouldn't get restrictions if you do it correctly. I no longer have an XZ but I can somewhat assist u
Click to expand...
Click to collapse
Unfortunately it doesn't work on Oreo. It worked on Nougat but I'm guessing something's missing in Oreo that we need to edit.
iArvee said:
Unfortunately it doesn't work on Oreo. It worked on Nougat but I'm guessing something's missing in Oreo that we need to edit.
Click to expand...
Click to collapse
I'm aware of this, hopefully someone can find a new way to fix it in Oreo. I would try but I no longer have my XZ and Samsung has smart view feature that works on nougat and Oreo to Miracast so I don't have that problem on my note 8. But just now thinking about it, maybe someone can port smart view app over to the XZ somehow lol
Related
DISCLAIMER: YOU WILL BE FLASHING YOUR PHONE AT YOUR OWN RISK. YOU ARE SOLELY RESPONSIBLE FOR ANYTHING YOU DO TO YOUR PHONE, SO MAKE SURE YOU ARE WELL INFORMED AND WELL PREPARED BEFORE DECIDING TO FLASH OR INSTALL ANYTHING ON YOUR DEVICE.
I created this thread with the sole aim of helping the owners of the Japanese SAMSUNG GALAXY ALPHA SC-03E NTT DOCOMO to install the latest version of Android (LOLLIPOP) on their devices without much hassle. All updates will be provided in the future.
All THANKS GO TO @ma34S :good: FOR COMPILING THIS ROM FOR US WE HAVE BEEN WAITING FOR THIS FOR A LONG TIME AND FINALLY ITS HERE.
REQUIREMENTS
1. A properly functioning SAMSUNG GALAXY ALPHA SC-03E NTT DOCOMO. We don’t want to receive any feedback from users with faulty phones.
2. PERMANENT ROOT WITH SU INSTALLED
IF YOU ARE RUNNING A CUSTOM ROM 4.X AND HAVE A CUSTOM RECOVERY INSTALLED SKIP TO “THINGS TO DOWNLOAD”
If you don’t have root and you are running on the stock android 4.3 or 4.x here is a simple way to root your device. All the CF Auto Root methods I found never worked for me.
a. Firstly, you are probably on an older OS like 4.1, 4.2 or 4.3. You might loose all your data depending on your OS(I was running the 4.3 SC03EOMUBND2 and I didn’t loose anything, not sure of 4.1 and 4.2)
b. Download one of these stock rooted roms.
4.3 SC03EOMUBND2 or 4.3 SC03EOMUBNH2
c. Download Samsung drivers here and install it
d. Download Odin on your PC and open it
e. Make sure USB debugging is enabled on your phone in developer settings.
f. Hold the Power Button + Volume Down + Home at the same time. Your phone will enter Download Mode.
g. Now connect your phone to the PC via USB cable whiles Odin is opened.
h. Now in Odin click the PDA button and open the Rom that you downloaded earlier.
i. Make sure F.Reset time and Auto reboot are all ticked
j. Now click Start button and wait for it to display PASS at the top left corner. Your Phone might restart a few times.
k. After the Last restart and the Display of the Pass you should have root now with super su installed.
l. Congrates you have root.
m. If you have an NK2 rom go check this thread on how to root it.
3. FULLY CHARGED BATTERY. This is to prevent the phone from going off in the flashing process
4. A CUSTOM RECOVERY installed.
If you don’t have one download Sc03e-KK-KBC-CWM-v6.0.5.1_r2-recovery and install with Odin with same procedure.
NOTE: If you have an older CWM installed, update to this one.
THINGS TO DOWNLOAD
1. ANDROID LOLLIPOP ROM 5.0.2 CM12.0 UNOFFICIAL
2. GOOGLE APP(GAPPS)
INSTALLING THE LOLLIPOP ROM
1. Copy the downloaded files and place them in the phone memory or SD card(recommended)
2. BACKUP your current OS in the recovery menu so that you can restore it if you encounter any problems in the flashing process.
3. To Enter the recovery menu, turn off your phone completely. PRESS and HOLD the POWER button + Volume UP + HOME button at the same time . When DOCOMO is displayed leave the power button and still keep holding the other buttons.
4. In recovery, use volume buttons to navigate and Power to select. Now go to wipe data/factory reset and wipe data, then wipe cache partition , then go to advanced and wipe Dalvic cache.
5. When all is done go to install zip and install the cm-12-20150213-UNOFFICIAL-sc03e.zip first.
6. When done install the GAPPS package.
NOTE: IF YOU HAVE CWM 6.0.4.7 THE GAPPS PACKAGE WONT INSTALL.
7. Now go back and wipe data , cache partition and Dalvic cache again then reboot. Upon exiting CWM you will be asked to fix your root binaries... say yes!
8. Your phone will boot into Android L with a Cyanogen boot animation.
9. Set up you phone and make sure to update all your Google apps and viola! :good:
NOTE: You will have to enable root in developer options.. enable it by tapping build number several times
CURRENT PROBLEMS
The keyboard.. i found a fix for it.. when you try to type something and it shows the Input method icon in the notification area... just tap on it and disable Hardware keyboard.. it should work fine .
Again remember to UPDATE Google apps else smart lock won't work
If you Discover any problems apart from the ones already stated above feel free to post a reply. Double check your errors before posting the reply.
Once Again thanks to @ma34S for providing this rom for us.
Thank you.
IN [OFFICIAL] Japanese SGS III (SC-03E) Rooting, ROMs, Kernels & Guides
.
Bugs: NFC, osaifu keitai, oneseg, music player force close, keyboard not appearing at first, unstable usb connection.
.
Click to expand...
Click to collapse
osaifu keitai, oneseg
I will not fix it right now.
next, I will remove osaifu keitai, oneseg support (it caused error now)
music player force close
My device is not so. it works well.
keyboard not appearing at first,
Cyanogenmod's nightly is same (t0lte),
when they fix it , this device is fix too.
unstable usb connection
I think this is including base framework.
because my all device is same as sc03e. (sc02e,sc04e,sc01f,lgl22)
but it seemed it was in boot time only.
I think it is not big problem for normal use. don't you think so?
Thank you.
yhh.. i also didn't notice any sort of problems with the USB.. and the keyboard.. i found a fix for it.. when you try to type something and it shows the Input method icon in the notification area... just tap on it and disable Hardware keyboard.. it should work fine
and its good to remove those app too.. also is it possible to make facelock preinstalled?..
Does your faceunlock work?
Sent from my SC-03E using XDA Free mobile app
ma34S said:
Thank you.
IN [OFFICIAL] Japanese SGS III (SC-03E) Rooting, ROMs, Kernels & Guides
.
osaifu keitai, oneseg
I will not fix it right now.
next, I will remove osaifu keitai, oneseg support (it caused error now)
music player force close
My device is not so. it works well.
keyboard not appearing at first,
Cyanogenmod's nightly is same (t0lte),
when they fix it , this device is fix too.
unstable usb connection
I think this is including base framework.
because my all device is same as sc03e. (sc02e,sc04e,sc01f,lgl22)
but it seemed it was in boot time only.
I think it is not big problem for normal use. don't you think so?
Thank you.
Click to expand...
Click to collapse
MY Faceunlock is not working.. i want to know if yours is working.. How do i fix it says trusted face has stopped
donsleeq said:
MY Faceunlock is not working.. i want to know if yours is working.. How do i fix it says trusted face has stopped
Click to expand...
Click to collapse
Sorry, I never used Faceunlock. please tell me how to use it.
Thank you.
ma34s
---------- Post added at 09:14 PM ---------- Previous post was at 08:39 PM ----------
SC03E has a issue by using chrome browser.
this is able to fix (just workaround?) with below.
http://forum.xda-developers.com/showpost.php?p=57072138&postcount=1556
Thank you very much @TokedUp!!
ma34S said:
Sorry, I never used Faceunlock. please tell me how to use it.
[/MENTION]!!
Click to expand...
Click to collapse
go to settings
go to lock screen
set a pin lock or pattern lock..
if you already have a pin lock then go to smart lock in the lock screen settings.
then then go to trusted face..
when you try to set it up , it just crashes..
I try it but TV and Faceunlock did not work and the androids keyboard did not work also
Right now back to CM11 last update
poopha said:
I try it but TV and Faceunlock did not work and the androids keyboard did not work also
Right now back to CM11 last update
Click to expand...
Click to collapse
face unlock and tv wont work.. true but the keyboard is working fine .. check the post for the fix.
"The keyboard.. i found a fix for it.. when you try to type something and it shows the Input method icon in the notification area... just tap on it and disable Hardware keyboard.. it should work fine"
donsleeq said:
go to settings
go to lock screen
set a pin lock or pattern lock..
if you already have a pin lock then go to smart lock in the lock screen settings.
then then go to trusted face..
when you try to set it up , it just crashes..
Click to expand...
Click to collapse
Thank you
I found the menu.
Face unlock did not work too.
(But it seemd did not crash)
ma34S said:
Thank you
I found the menu.
Face unlock did not work too.
(But it seemd did not crash)
Click to expand...
Click to collapse
mine said trusted face had stopped..
Can you fix it please..
anyway what is felica lock and what does it do?
and can you please add onscreen buttons support
donsleeq said:
mine said trusted face had stopped..
Can you fix it please..
anyway what is felica lock and what does it do?
and can you please add onscreen buttons support
Click to expand...
Click to collapse
"felica lock" needs for Osaifu. But it does not work in Lolipop right now.
And then I removed it since cm-12-20150227-UNOFFICIAL-sc03e.
Thank you.
donsleeq said:
mine said trusted face had stopped..
Can you fix it please..
anyway what is felica lock and what does it do?
and can you please add onscreen buttons support
Click to expand...
Click to collapse
I think this is not problem in ROM .
It depend on Google service(I don't knot what effects)
I tried below:
1. Factory reset
1. install cm12 ( I installed cm-12-20150309-UNOFFICIAL-sc03e.zip)
2. install GAPPS( I installed gapps-lp-20141114-signed.zip )
---> Smart lock did not work
3. update all Google app & Google Play services by Google play
---> Smart lock start to work.
* see attachment images (my screen shot).
Thank you
ma34s
cm-12-20150309-UNOFFICIAL-sc03e
http://site.kbc-brick.org/samsung/sc03e/recovery-kernel-rom
My changes
-Fix color LED notification
CM changes
please see http://www.cmxlog.com/12/t0lte/ .
this is for t0lte , but it almost same as my build for sc03e except android_device_samsung_t0lte.
Thanks man.. I'm trying that now.
And is it possible to get on screen buttons.. I will be glad to get it.
donsleeq said:
Thanks man.. I'm trying that now.
And is it possible to get on screen buttons.. I will be glad to get it.
Click to expand...
Click to collapse
it is possible for you to enable on screen key by writing following in /system/build.prop
Code:
qemu.hw.mainkeys=0
it works in my device,
please try it
Thank you
cm-12-20150310-UNOFFICIAL-sc03e
Download:
http://site.kbc-brick.org/samsung/sc03e/recovery-kernel-rom
My changes:
-Fix GPS
CM changes:
please see http://www.cmxlog.com/12/t0lte/ .
this is for t0lte , but it almost same as my build for sc03e except android_device_samsung_t0lte.[/QUOTE]
---------- Post added at 06:59 PM ---------- Previous post was at 06:57 PM ----------
@amakuramio post at here
bugs
1. keyboard on first install
2. contents on sd card not properly displayed
Click to expand...
Click to collapse
bugs
2. contents on sd card not properly displayed
Click to expand...
Click to collapse
I don't understand what means.
Thank you.
2015/03/10 bugs:
1. keyboard on boot
初期化した際、キーボードは表示されません。(設定→言語・入力でハードウェアをONすることで使えます)
2. When connected to USB, it takes a long time to display all files when connected.
USB経由でケータイがパソコンと接続した際、ストレージ内のファイルの読み込みのは長い時間がががります。
また、一部のファイルは表示されません。
3. baseband unknown
ベースバンド不明
amakuramio said:
Thank you.
2015/03/10 bugs:
1. keyboard on boot
初期化した際、キーボードは表示されません。(設定→言語・入力でハードウェアをONすることで使えます)
2. When connected to USB, it takes a long time to display all files when connected.
USB経由でケータイがパソコンと接続した際、ストレージ内のファイルの読み込みのは長い時間がががります。
また、一部のファイルは表示されません。
3. baseband unknown
ベースバンド不明
Click to expand...
Click to collapse
Oh thank you, I don't say that can't understand English.
But thank you.
about 1 and 2:
I posted at #2
It will fix by Cyanogenmod maybe.
about 3:
really? my device recognize the baseband. I think no problem.
I asked to other guy on twitter.
he said that baseband is OK.
please check your operation and flash again.
thank you
Okay guys was running android mm on moto x pure and I tried the settings put global tether_dun_required 0 using ADB, and I also added the net.tethering.noprovisioning=true build.prop file. As soon as I did this my wifi stoped working, if I try to turn wifi on it turns right back off.
I have tried removing the lines in build.prop and in settings.db, ive tried turning wifi on in settings.db and wiping the phone in twrp and a fresh install of android 5.1 Nothing seems to work, I actually think that this may have somehow broke my phones wifi adapter.
Please Help
Thanks
mozndtb said:
Okay guys was running android mm on moto x pure and I tried the settings put global tether_dun_required 0 using ADB, and I also added the net.tethering.noprovisioning=true build.prop file. As soon as I did this my wifi stoped working, if I try to turn wifi on it turns right back off.
I have tried removing the lines in build.prop and in settings.db, ive tried turning wifi on in settings.db and wiping the phone in twrp and a fresh install of android 5.1 Nothing seems to work, I actually think that this may have somehow broke my phones wifi adapter.
Please Help
Thanks
Click to expand...
Click to collapse
see this link http://www.gammerson.com/2015/11/download-marshmallow-60-for-moto-x-pure.html ...it's for 6.0, but you could essentially do the same using the 5.1 bin file...pretty sure the 5.1 modem file is floating around on the site, or you could download the stock image and extract it.
Well darn that was the problem, I would have thought that if you flashed a fresh stock rom it would have replaced everything.
Thank you so much!
Glad you got that fixed man..can U please tell me tho about the actual trick to get around the tether cap?
Will adding that build prop line do the trick? Or is there another way?
I was searching on the Tapatalk app then went to my pc and was searching Google for 'how to by pass tmob tether block moto x pure' and I haven't found much. I was really hoping it would indeed just be a simple buid prop edit. Can u give me some info on that? Thanks
Sent from my XT1575 using Tapatalk
Well, I configured my 6P with the fingerprint/pin combo at startup and was using it like that...
I then disabled any security, and that meant wiping off my fingerprints.
I then tried to set everything up again, that means fingerprint+PIN. It set up correctly, I even set up to ask for PIN each time I reboot the device... This is where it gets weird.
When I booted up for thr first time, and went through Imprint+PIN setup, whenever I'd restart the phone, it would greet me with the secure startup screen , asking for my PIN in order to continue starting up the device. It would then boot me to my lockscreen. Where I'd have to input my PIN/fingerprint in order to unlock to desktop.
Now that I re-set it up, it will ask me for my PIN before booting up, but now it won't boot me to my lockscreen, but directly to desktop.
If I disable asking for PIN at boot, I get booted to lockscreen.
How can I restore functionality? Is this normal?
Since this is an Android N Dev Preview regarding issue, you should report it to Google if at all. Dev Preview is not meant to be used as a daily driver and some bugs should be expected to experience.
neisor said:
Since this is an Android N Dev Preview regarding issue, you should report it to Google if at all. Dev Preview is not meant to be used as a daily driver and some bugs should be expected to experience.
Click to expand...
Click to collapse
But it was working accordingly on N. I bet it's an issue even on MM.
benleonheart said:
But it was working accordingly on N. I bet it's an issue even on MM.
Click to expand...
Click to collapse
I do not think this issue is affecting MM.
Anyway, was the security working before on Dev Preview 4? Or it worked on previous Dev Previews and on the 4th it's not?
neisor said:
I do not think this issue is affecting MM.
Anyway, was the security working before on Dev Preview 4? Or it worked on previous Dev Previews and on the 4th it's not?
Click to expand...
Click to collapse
Workes on previous and on 4.
Disabled PIN/fingerprints and re enabled them and set them up again but to no avail...
https://download.mokeedev.com/?device=zoom
Does someone try this rom? If u ever on this rom, can u give a feedback about the rom..? I would like to know your opinion..
X10MINISTER said:
Does someone try this rom? If u ever on this rom, can u give a feedback about the rom..? I would like to know your opinion..
Click to expand...
Click to collapse
Rom works but it wasn't maintained. No new bug correction from february.
stuccamelo said:
Rom works but it wasn't maintained. No new bug correction from february.
Click to expand...
Click to collapse
Thanks for sharing ur opinion/experiences on this rom.. Im running on latest build of this mokee rom, i think it is suitable for daily driver..but I got some problem with hotspot(maybe it is because of mod that i've installed).. Maybe u got some solution on this
X10MINISTER said:
Thanks for sharing ur opinion/experiences on this rom.. Im running on latest build of this mokee rom, i think it is suitable for daily driver..but I got some problem with hotspot(maybe it is because of mod that i've installed).. Maybe u got some solution on this
Click to expand...
Click to collapse
Sorry no solution I have big problem with gmaps doesn't recalculate path after initial path and play store give "not compatible device" error in some apps.
Good thing battery drain is very very good
stuccamelo said:
Sorry no solution I have big problem with gmaps doesn't recalculate path after initial path and play store give "not compatible device" error in some apps.
Good thing battery drain is very very good
Click to expand...
Click to collapse
So, it mean that u also facing the hotspot problem.?
Can u change/install fonts in mokee roms? Cause I have an issue with changing font style using iFont apps..its say installed but after reboot font style doesnt change. Any solution?
linux shall eternally bloat all search engines with expired ?=
as it is stated in the title: the internet is full of long expired conversations about issues which are gone, along with hardware.
back in the beginning i recall only one distro Dev, SimplyMepis, who always, promptly warned, that most if not all information online about Linux is outdated or incorrect.
now on mokee, has anyone tested mokee naugat on vibe shot as recent as September/October 2017? The reason I ask is because there are no reviews or any useful feedback on mokee download/changelog page. I used it in August and each time the phone disconnect from WiFi it would reboot with an ugly, annoying double beep.
Apart from this issue everything would work pefectly well, including both sim loaded.
Thanks for taking time to respond.
Dr Tungsten said:
as it is stated in the title: the internet is full of long expired conversations about issues which are gone, along with hardware.
back in the beginning i recall only one distro Dev, SimplyMepis, who always, promptly warned, that most if not all information online about Linux is outdated or incorrect.
now on mokee, has anyone tested mokee naugat on vibe shot as recent as September/October 2017? The reason I ask is because there are no reviews or any useful feedback on mokee download/changelog page. I used it in August and each time the phone disconnect from WiFi it would reboot with an ugly, annoying double beep.
Apart from this issue everything would work pefectly well, including both sim loaded.
Thanks for taking time to respond.
Click to expand...
Click to collapse
There are a lot of recent updates for this rom. I flashed the most recent (2017-11-21 date). I didn't make a lot of testing but the problem you refered has been solved and the performance and stability seems good.
The only issue I noticed so far is that the phone does not start automatically from the shutdown state when an alarm is set.
@piccolo2k2 Was your device flagged as certified? When I flushed the rom I wasn't able to pass the SafetyNet test and I would appear as uncertified in play store, meaning I couldn't download most apps like Messenger or Facebook. I installed a third party app store which worked fine, but YouTube wouldn't play any video, because it couldn't load any ads... I even tried Magisk with no luck..
GeorgeTsak said:
@piccolo2k2 Was your device flagged as certified? When I flushed the rom I wasn't able to pass the SafetyNet test and I would appear as uncertified in play store, meaning I couldn't download most apps like Messenger or Facebook. I installed a third party app store which worked fine, but YouTube wouldn't play any video, because it couldn't load any ads... I even tried Magisk with no luck..
Click to expand...
Click to collapse
This is not my main phone right now so I spend very limited time using or testing it but you are right, I have just checked that with this ROM the device is unable to pass the SafeNet test so far. On the other hand I have not problems at all playing videos with youtube app or rooting the device. I'm using supersu v2.82 and TRWP-3.0.2-0 for lenovo 6.0 by wzsx150 (didn't try Magisk)
has anyone managed to install this ROM?
i tried to install it but failed.
I unlocked the bootloader using the method described here, and installed TWRP recovery as described here
when i try to install it - the flashing is stopped by a long vibration and the device went off, i tried to debug the flashing process, it seems that the step of mounting "\system" fails, i tried to replace the mount/unmount calls from updater_script with respective run_program(busybox) commands, but had no success with that. when i'm using the TWRP build in funcitonlity to wipe the system partition, TWRP claims the operation was successful, but checking the system partition details shows that the partition still contains data.
ohh, and also - the device model seems strange, the script checked that the model is zoom_tdd (or something like that) but the device (the bootloader?) return Z90a40... (i also updated the script to check for Z90a40)
the current state is that the device won't boot, but i can get into recovery.
Anyone have an idea how to proceed?
Thanks.
mrtowel said:
i tried to install it but failed.
I unlocked the bootloader using the method described here, and installed TWRP recovery as described here
when i try to install it - the flashing is stopped by a long vibration and the device went off, i tried to debug the flashing process, it seems that the step of mounting "\system" fails, i tried to replace the mount/unmount calls from updater_script with respective run_program(busybox) commands, but had no success with that. when i'm using the TWRP build in funcitonlity to wipe the system partition, TWRP claims the operation was successful, but checking the system partition details shows that the partition still contains data.
ohh, and also - the device model seems strange, the script checked that the model is zoom_tdd (or something like that) but the device (the bootloader?) return Z90a40... (i also updated the script to check for Z90a40)
the current state is that the device won't boot, but i can get into recovery.
Anyone have an idea how to proceed?
Thanks.
Click to expand...
Click to collapse
I think you need a different TWRP version. Try this one:
https://drive.google.com/file/d/0B1Sms71Oe6FIQnl4STlhSk96b0E/view?usp=sharing
Help me!
I'm new to these things. Installing roms and ****s. Can someone help me with the step by step procedure of installing this room on my Lenovo vibe shot. Thanks in advance.
The same probvlem with TWRP
piccolo2k2 said:
I think you need a different TWRP version. Try this one:
Click to expand...
Click to collapse
I have exactly the same problem.
Did you resolved it? Tried also mentioned "Twrp by rahul.rar", but the same problem - unable to mount /system partition.
Thanks for reply,
st
bug fix?
does anybody tested it?
is it still any bug on release version MK71.2-zoom-180914-RELEASE?
hhaekal said:
does anybody tested it?
is it still any bug on release version MK71.2-zoom-180914-RELEASE?
Click to expand...
Click to collapse
Im using it right now.. Im still have the problem with:
-hotspot tethering,bluetooth tethering
-usb mtp
-suddenly shutdown when on wifi
Have someone had the problem with delay in receiving whatsapp messages?
Hello,
has anyone tested the MK71.2-zoom-181107-RELEASE version? Is the bug with the WiFi still there?
Alex_135 said:
Hello,
has anyone tested the MK71.2-zoom-181107-RELEASE version? Is the bug with the WiFi still there?
Click to expand...
Click to collapse
Hi,
I'm using the release and there is no bug with WIFI.
Linaxx said:
Hi,
I'm using the release and there is no bug with WIFI.
Click to expand...
Click to collapse
How about wifi tethering problem? Does it remain error when wifi tethering are enabled?
Hello all!
I have been struggling for a couple of weeks now with my MXP, it suddenly stopped auto rotating everything (All stock apps, desktop, installed apps), tried several fixes including cache cleaning, uninstalling recent updates, sensor fix tool apps (like Quick TuneUp), the issue appeared after the Nougat 7.1.1 update (NDP26.48-24-1) but I don't think it is related to it because it was working fine after I patched with the OTA.
Update: I found out that the accelerometer works correctly using Spirit Level app, I already factory reset my device 2 times with no change.
Hope someone can give me some light!
My x play in that all sensors are not working pls provide some solution....
Silverian said:
[...] my MXP, it suddenly stopped auto rotating everything[...]
Click to expand...
Click to collapse
Did you check settings/display/rotate screen?
Don't know the exact wording, my device shows German.
Awesome kernel. Everything works fine. LOS 14.1
tag68 said:
Did you check settings/display/rotate screen?
Don't know the exact wording, my device shows German.
Click to expand...
Click to collapse
I did, that was the first thing to check.