Related
Hi there,
I have a UK WiFI xoom, and everything was working fine. I installed the ICS AOSP rom, and no issues.
The problem started when I updated the AOSP ICS rom, and the gapps, Now I DONT HAVE MARKET access. The loading circle just goes round and round till it says 'connection timed out - retry'. The GTALK doesnt connect either, it just says 'signing in' till it goes 'offline'.
Right now, I am on the EOS Wifi ICS rom.
Here's what I HAVE done so far to fix it based on ideas in this forum and others (trust me, I search before I post:
- Factory reset, wipe cache, dalvik before every rom install
- Installed every single ICS rom there is, with the recommended google apps
- wiped data on the google services framework
- Installed different version of gapps
- Shut down the firewall on the HOME NETWORK.
It just doesnt work anymore. It used to connect fine to the home Wifi earlier but something just went wrong somewhere and i cant track it down.
Any help would be appreciated.
you have any more info like does your xoom show you are connected to your wifi? do you have any other wireless devices and are they accessing the internet fine? are you flashing the right gapps package?
yea, Wifi is connected fine. Alternate markets like 'slideme', and browser, gmail, maps app etc work fine without problems.
I have flashed the latest gapps package as recommended by EOS rom makers (v. 10 i believe)
after installing the eos mod, did u restart before installing the gaps?
load a stock backup then reinstall your current flavor and gapps
pr1vate piles said:
after installing the eos mod, did u restart before installing the gaps?
Click to expand...
Click to collapse
No I Didn't restart.
load a stock backup then reinstall your current flavor and gapps
Unfortunately, I didnt make a backup. I am an idiot I know!
Just quickly, 10.4 is the latest Gapps to use with EOS.
TheStickMan said:
Just quickly, 10.4 is the latest Gapps to use with EOS.
Click to expand...
Click to collapse
Yes, sorry for not clarifying. 10.4 (the latest as of yesterday) is the one I used
inshadesofgrey said:
Yes, sorry for not clarifying. 10.4 (the latest as of yesterday) is the one I used
Click to expand...
Click to collapse
First, take a deep breath. It's probably something small that's causing the problem, no doubt.
Some of the EOS Nightly are more stable than others. I would recommend wingray nightly build #56 (very smooth and stable) with the 10.4 GAPPS flashed immediately afterward. First wipe cache partitions, then dalvik cache (in advanced) then flash the rom and the GAPPS, then reboot. This should work very well for you. If you feel the need to do another data wipe, do that before anything else.
IMHO, no need to flash stock images 1st. Just flash on top of your current rom.
Good luck!
ok- will try and respond with results. thanks for the patience/
okantomi said:
First, take a deep breath. It's probably something small that's causing the problem, no doubt.
Some of the EOS Nightly are more stable than others. I would recommend wingray nightly build #56 (very smooth and stable) with the 10.4 GAPPS flashed immediately afterward. First wipe cache partitions, then dalvik cache (in advanced) then flash the rom and the GAPPS, then reboot. This should work very well for you. If you feel the need to do another data wipe, do that before anything else.
IMHO, no need to flash stock images 1st. Just flash on top of your current rom.
Good luck!
Click to expand...
Click to collapse
Hi - I did the steps exactly as you said (with a full data wipe). Still getting nowhere?
Any more ideas?
Go back to stock US recovery ROM. Start again.
Also no idea how to fix it (as nothing previously worked), but the symptoms seem similar to when you haven't accepted the agreement that pops up on new google framework (?) version. Won't let you use market or gtalk.. has happened to me before.
Before flashing, try an extra wipe: wipe system (in some recoveries also called "format system" ). I have been saved by this more than once.
Tapatalking
I always wipe dalvick and cache partition. Install ROM from SD card, followed by latest Gapps and then use the fix permissions in advanced settings before rebooting. I have never had a single problem and have been using EOS Wingray nightly since release 11. I am sure the fix permissions is the key to this. No need to do a full wipe if you are on the same ROM!
Sent from my ZTE-BLADE using Tapatalk
Krypt2Nyte said:
I always wipe dalvick and cache partition. Install ROM from SD card, followed by latest Gapps and then use the fix permissions in advanced settings before rebooting. I have never had a single problem and have been using EOS Wingray nightly since release 11. I am sure the fix permissions is the key to this. No need to do a full wipe if you are on the same ROM!
Sent from my ZTE-BLADE using Tapatalk
Click to expand...
Click to collapse
i will try that now.
Also, if i should move back to stock - which rom should I go to? HC or ICS? any links would help. thx guys, for the patience.
j
You can only go back to 3.0 or whatever it is. t will update to 3.2, and then hopefully ICS.
On tablet, so can't quickly find original motorola dev website - try Googling. Here is link to post with hosted firmwares anyway..
http://forum.xda-developers.com/showthread.php?t=1049485
Also check second post there, for using fast boot to install.
inshadesofgrey said:
i will try that now.
Also, if i should move back to stock - which rom should I go to? HC or ICS? any links would help. thx guys, for the patience.
j
Click to expand...
Click to collapse
yea it didnt work. I guess i have to flash back honeycomb. Funny thing is, after I tried this - the GTALK staed working!!! just not the market. Its just hat i can't get to the user agreement page the first time we open the market.
inshadesofgrey said:
yea it didnt work. I guess i have to flash back honeycomb. Funny thing is, after I tried this - the GTALK staed working!!! just not the market. Its just hat i can't get to the user agreement page the first time we open the market.
Click to expand...
Click to collapse
Have you tried accessing the market through the browser? You will need to sign in...that may reestablish your link. I can't see why you need to go back to stock Honeycomb. It gets complicated getting cwm recovery back on (to stick).
I had a similar issue on my DHD. It turned out that your language needs to be US English.
Hope this helps
okantomi said:
Have you tried accessing the market through the browser? You will need to sign in...that may reestablish your link. I can't see why you need to go back to stock Honeycomb. It gets complicated getting cwm recovery back on (to stick).
Click to expand...
Click to collapse
this is very very strange. I can open all other google services and sign in from the browser but not the market.android.com, its just NOT opening the signin page
I got a Nexus 5 been using CM on it for a while now. Currently i have 11-20140708-SNAPSHOT-M8
the build date is july 8. I've been getting CM update for a new version for like a month now, tried installing it a couple of times, when i press to reboot and install it says it installed it, and after the phone reboots, it's still the same old version, and i keep getting the notification to upgrade, but i can't.
So I waited for another new build, thinking this is just some bug in the update. Yesterday a new version prompted for a update, but the same happened. So i tried to download the zip from CM website and flash it on recovery manually. And i got an error:
Can't install this package on top of incompatible data. (Status 7) installation aborted.
I used to update with no problems, but I seem to be stuck on the july 8 build.
Anyone else dealing with this, or know how to fix this?
Is your bootoader up-to-date? CM often require you to have latest bootloader
No. I haven't upgraded it. I've found multiple threats about it, I'm not sure which one is the right to do so. As i'm not really familiar with this kind of stuff.
EDIT: My BL version is HHZ11K. From what i gathered it's the most recent one.
TheSidiO said:
Can't install this package on top of incompatible data. (Status 7) installation aborted.
Click to expand...
Click to collapse
Sounds like you're dirty flashing but something in your current set up has been corrupted. You may need to factory reset or do a clean install.
Wakamatsu said:
Sounds like you're dirty flashing but something in your current set up has been corrupted. You may need to factory reset or do a clean install.
Click to expand...
Click to collapse
Was thinking if I can salve the problem without doing that. But i did a factory reset and it fixed the problem.
Thanks for the responses.
problems updating monthly snapshots of CM
Hi, I have been looking everywhere to see why I am having difficulties updating Cyanogen snapshots every month. I found this post but I don't really know if it pertains to my problem. I have a google rooted nexus 5 and every month when I try to update my phone begins acting up. It starts saying unfortunately google play services has stopped working. I see my apps trying to install but all I get are error notification icons at the top and they won't download. I posted on g+ and someone says it has to do with titanium. Im at a loss. Its very frustrating as I've tried almost everything I can think of to no avail. I try to go to the playstore and it's like I have no connection. I do have and use titanium backup for the apps I want to restore. I spoke to someone that has the same phone and he tells me to just flash the update without wiping but it doesn't work for me. I don't know if its a setting I'm missing on titanium or what it is but it sucks. With the 2 last updates this has happened. Leaving me with no option but to download the CM snapshot along with gapps. Wipe my phone and flash both the snapshot and gapps and start from scratch. I hope you can help me. Hopefully I'm in the right place. Tx you
acf150 said:
Hi, I have been looking everywhere to see why I am having difficulties updating Cyanogen snapshots every month. I found this post but I don't really know if it pertains to my problem. I have a google rooted nexus 5 and every month when I try to update my phone begins acting up. It starts saying unfortunately google play services has stopped working. I see my apps trying to install but all I get are error notification icons at the top and they won't download. I posted on g+ and someone says it has to do with titanium. Im at a loss. Its very frustrating as I've tried almost everything I can think of to no avail. I try to go to the playstore and it's like I have no connection. I do have and use titanium backup for the apps I want to restore. I spoke to someone that has the same phone and he tells me to just flash the update without wiping but it doesn't work for me. I don't know if its a setting I'm missing on titanium or what it is but it sucks. With the 2 last updates this has happened. Leaving me with no option but to download the CM snapshot along with gapps. Wipe my phone and flash both the snapshot and gapps and start from scratch. I hope you can help me. Hopefully I'm in the right place. Tx you
Click to expand...
Click to collapse
So here is what i would try to do. reboot into recovery. do a factory reset, make sure you backup your files as this cleans them. And then make the update from the updater or download it manually from cm website.
updating CM snapshot monthly problems
TheSidiO said:
So here is what i would try to do. reboot into recovery. do a factory reset, make sure you backup your files as this cleans them. And then make the update from the updater or download it manually from cm website.
Click to expand...
Click to collapse
Almost what I did, i l always do a nandroid backup before flashing anything in recovery, I downloaded the snapshot and the gapps, wiped, and installed snapshots along with gapps. So your telling me to just do a backup in recovery before updating that it cleans my files, then without wiping to try to update just the CM update from either my phone or their website? No gapps? Will try next time thanks.
I followed the instructions given to me in my "new here" thread and was able to wipe my OS and install resurrection remix 7.1.2 last night. However, I was only able to install gapps mini and now I can't take a screenshot or install other items like google chrome or facebook. However, I was able to install other apps like firefox. I've tried a factory reset, removing my google account from the play store and re-adding it. It should definitely not be a cache problem as the install is brand new. I even used twrp wipe on all folders and reinstalled RR and still no change. Do I need to repartition or just try another mod?
*edit*
I found another thread here through a search that had a very similar issue to mine, but it looks like they were able to resolve theirs by uninstalling some app (they didn't say what). I'm having this with a fresh install, every time. So that fix didn't work for me, and I couldn't find anything else.
As an update to this issue, I have been able to install OkCupid (I'm a single girl, what can I say?) and the Android WebService that it required to function. Still have original issue though.
briannam said:
As an update to this issue, I have been able to install OkCupid (I'm a single girl, what can I say?) and the Android WebService that it required to function. Still have original issue though.
Click to expand...
Click to collapse
That's strange.Try Clean flashing the rom with opengapps.org .
Mr.Ak said:
That's strange.Try Clean flashing the rom with opengapps.org .
Click to expand...
Click to collapse
Yeah, I think it might be the resurrection remix mod. I think after I get off work tonight I'm going to try the newest CM13? mod listed here and see if that doesn't help
briannam said:
Yeah, I think it might be the resurrection remix mod. I think after I get off work tonight I'm going to try the newest CM13? mod listed here and see if that doesn't help
Click to expand...
Click to collapse
It ain't no mod.I'm taking about using open gapps instead of whatever gapps you were using before.
The mod I'm referring to is the resurrection remix which is the OS mod. I used the open gapps mini with that OS, so I've tried that.
briannam said:
The mod I'm referring to is the resurrection remix which is the OS mod. I used the open gapps mini with that OS, so I've tried that.
Click to expand...
Click to collapse
What does PS say when you try to install facebook,etc?
It just says downloading and never changes. I also don't get the notification in the status area indicating it's downloading. It doesn't ask for permissions either, I don't know is that's normal for a rooted phone or not
briannam said:
It just says downloading and never changes. I also don't get the notification in the status area indicating it's downloading. It doesn't ask for permissions either, I don't know is that's normal for a rooted phone or not
Click to expand...
Click to collapse
I'm rooted,and downloading works fine for me.Umm,try clearing data and cache of play services and play store?
Mr.Ak said:
I'm rooted,and downloading works fine for me.Umm,try clearing data and cache of play services and play store?
Click to expand...
Click to collapse
One of the first things I did yep. It's almost as if the system storage is somehow full or locked or something.
briannam said:
One of the first things I did yep. It's almost as if the system storage is somehow full or locked or something.
Click to expand...
Click to collapse
Try with flashing different gapps(bean,dynamic etc) then.
Mr.Ak said:
Try with flashing different gapps(bean,dynamic etc) then.
Click to expand...
Click to collapse
Well, here's why I don't think that's it. After flashing the OS, I tried to flash the super version of the open gapps. That was a huge file, almost a gig I think, so when that errored out I wasn't surprised. So when I tried the stock at 700 mb, and that failed, I tried the mini. That was 200 mb, and when that flashed successfully, I got suspicious. So I do think it's an issue with the system partition. I know the resurrection remix was a few GB in size, so perhaps it was too big. I haven't tried downloading CM13 or any others yet, so I don't know if there's a huge size difference or not. But I think that may be what it was. Just too big for our phones.
briannam said:
Well, here's why I don't think that's it. After flashing the OS, I tried to flash the super version of the open gapps. That was a huge file, almost a gig I think, so when that errored out I wasn't surprised. So when I tried the stock at 700 mb, and that failed, I tried the mini. That was 200 mb, and when that flashed successfully, I got suspicious. So I do think it's an issue with the system partition. I know the resurrection remix was a few GB in size, so perhaps it was too big. I haven't tried downloading CM13 or any others yet, so I don't know if there's a huge size difference or not. But I think that may be what it was. Just too big for our phones.
Click to expand...
Click to collapse
System partition has a size,just like internal storage has.Though,in the former case,you can increase it,but there's no point in increasing it,as you can just flash mini/nano/pico gapps and install all the other G-Apps you need after that.Infact,stock/heavy gapps is nothing but bloatware.
Anyway,what I meant was, flash other gapps except opengapps:
https://www.google.co.in/amp/s/foru...id/software/gapps-dynamic-gapps-t3487192/amp/
https://forum.xda-developers.com/android/general/gapps-gapps-7-0-nougat-minimal-t3474980
https://androidfilehost.com/?w=files&flid=124631
https://www.google.co.in/amp/s/foru...d-slim-gapps-6-0-7-0-unofficial-t3462088/amp/
https://plus.google.com/+DaanST/posts/ZMo18YATkc4
Okay,enuff spam for now.
Mr.Ak said:
System partition has a size,just like internal storage has.Though,in the former case,you can increase it,but there's no point in increasing it,as you can just flash mini/nano/pico gapps and install all the other G-Apps you need after that.Infact,stock/heavy gapps is nothing but bloatware.
Anyway,what I meant was, flash other gapps except opengapps:
https://www.google.co.in/amp/s/foru...id/software/gapps-dynamic-gapps-t3487192/amp/
https://forum.xda-developers.com/android/general/gapps-gapps-7-0-nougat-minimal-t3474980
https://androidfilehost.com/?w=files&flid=124631
https://www.google.co.in/amp/s/foru...d-slim-gapps-6-0-7-0-unofficial-t3462088/amp/
https://plus.google.com/+DaanST/posts/ZMo18YATkc4
Okay,enuff spam for now.
Click to expand...
Click to collapse
I think I just figured it out. I went outside on break and went to take a selfie to test the camera for this OS, and voila, it told me to enter an SD card. So it looks like it may be some sort of permissions issue. I'll just re-flash it with a different OS later. I'm not really attached to this one anyway. Brand new phone, nothing to back up.
briannam said:
I think I just figured it out. I went outside on break and went to take a selfie to test the camera for this OS, and voila, it told me to enter an SD card. So it looks like it may be some sort of permissions issue. I'll just re-flash it with a different OS later. I'm not really attached to this one anyway. Brand new phone, nothing to back up.
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-one/development/official-dotos-v1-0-t3703159
Kthnxbye.
Mr.Ak said:
https://forum.xda-developers.com/oneplus-one/development/official-dotos-v1-0-t3703159
Kthnxbye.
Click to expand...
Click to collapse
Looks good to me, I'll give it a shot tonight, thanks!
So, I flashed DotOS last night, everything is working. Looks like Resurrection Remix was the problem. Thanks again!
briannam said:
So, I flashed DotOS last night, everything is working. Looks like Resurrection Remix was the problem. Thanks again!
Click to expand...
Click to collapse
Feel free to drop by the thread when you run into any issues.
Change-log:
2018-01-08: First release.
2018-01-10: Removed the camera app. Slim-ovation-4.4.4.build.9.14-UNOFFICIAL-20180110-1016.zip
2018-01-23: Updated the SlimKat apps. Slim-ovation-4.4.4.build.9.14-UNOFFICIAL-20180123-1611.zip
2018-02-08: Updated the SlimKat apps, removed Chromium apk, updated the security patch, and updated the webview stuff. Slim-ovation-4.4.4.build.9.15-UNOFFICIAL-20180208-0028.zip
XDA:DevDB Information
[ROM][4.4.4][Ovation][EMMC][UNOFFICIAL] SlimKat, ROM for the Barnes & Noble Nook HD, HD
Contributors
secretwolf98, SlimKat (for the latest sources)
Source Code: https://drive.google.com/drive/folders/1YkPtDKPvoVbU1CP3VjgRS0yNYR_c9EC-?usp=sharing
ROM OS Version: 4.4.x KitKat
Based On: SlimKat
Version Information
Status: Stable
Current Stable Version: SlimKat
Stable Release Date: 2018-02-08
Created 2018-01-09
Last Updated 2018-02-24
Glad to see you're working on the ovation version as well. I've upgraded from your 14.1 version to this one but I've been getting an error on the slimkat boot. I've used the twrp 3.1.1, factory reset, fresh install. The error was about data mounting. In the 14.1 I had both data and cache under the f2f system. When I installed back your 14.1 version, everything was back to normal, no errors. Do I need to format data and cache to ext4 for this slimkat version to work?
zspeciman said:
Glad to see you're working on the ovation version as well. I've upgraded from your 14.1 version to this one but I've been getting an error on the slimkat boot. I've used the twrp 3.1.1, factory reset, fresh install. The error was about data mounting. In the 14.1 I had both data and cache under the f2f system. When I installed back your 14.1 version, everything was back to normal, no errors. Do I need to format data and cache to ext4 for this slimkat version to work?
Click to expand...
Click to collapse
What build are you using?
I used this one Slim-ovation-4.4.4.build.9.14-UNOFFICIAL-20180108-1016.zip and this one lineage-14.1-20171216-UNOFFICIAL-ovation.zip as well as open_gapps-arm-4.4-pico-20180110.zip.
I saw you've put a 01-10 build today, I will try it and report back.
I tried the 01-10 build and it didn't work for me either. But this time I took a photo of the error. Hopefully this will help.
update:
went straight back to twrp and format data and cache to ext4 and it worked. I didn't do a factory reset or reinstall, just changed the formats and reboot.
Looks good so far, thank you for all the hard work #secretwolf98
zspeciman said:
I tried the 01-10 build and it didn't work for me either. But this time I took a photo of the error. Hopefully this will help.
update:
went straight back to twrp and format data and cache to ext4 and it worked. I didn't do a factory reset or reinstall, just changed the formats and reboot.
Looks good so far, thank you for all the hard work #secretwolf98
Click to expand...
Click to collapse
Your welcome.
Google play seem to gives me problems, either crushes, or exists often. Also the nook button doesn't seem to work. Otherwise this new interface is beautiful and this rom looks very promising.
zspeciman said:
I tried the 01-10 build and it didn't work for me either. But this time I took a photo of the error. Hopefully this will help.
update:
went straight back to twrp and format data and cache to ext4 and it worked. I didn't do a factory reset or reinstall, just changed the formats and reboot.
Looks good so far, thank you for all the hard work #secretwolf98
Click to expand...
Click to collapse
Could I have some feedback, so I can see if I could try to fix it within the next build?
secretwolf98 said:
Could I have some feedback, so I can see if I could try to fix it within the next build?
Click to expand...
Click to collapse
Testing Slim-ovation-4.4.4.build.9.14-UNOFFICIAL-20180123-1611.zip, this is a logcat with amaces TWRP, all partitions wiped, and only the rom installed:
https://pastebin.com/LW6QFY27
This is the same as above, but with with verygreen cwm and I opened more apps:
https://pastebin.com/FQnTR1c2
This is the same as above after switching to art:
https://pastebin.com/4vJE7miZ
The biggest issue is with Chromium, it crashes with this strange error:
java.lang.UnsatisfiedLinkError: Couldn't load chromium_android_linker from loader dalvik.system.PathClassLoader[DexPathList[[zip file "/system/app/Chromium.apk"],nativeLibraryDirectories=[/vendor/lib, /system/lib]]]: findLibrary returned null
The graphics seem unstable with hardware overlays, you can really see it when opening/closing Downloads and DSP Manager.
fddm said:
Testing Slim-ovation-4.4.4.build.9.14-UNOFFICIAL-20180123-1611.zip, this is a logcat with amaces TWRP, all partitions wiped, and only the rom installed:
https://pastebin.com/LW6QFY27
This is the same as above, but with with verygreen cwm and I opened more apps:
https://pastebin.com/FQnTR1c2
This is the same as above after switching to art:
https://pastebin.com/4vJE7miZ
The biggest issue is with Chromium, it crashes with this strange error:
java.lang.UnsatisfiedLinkError: Couldn't load chromium_android_linker from loader dalvik.system.PathClassLoader[DexPathList[[zip file "/system/app/Chromium.apk"],nativeLibraryDirectories=[/vendor/lib, /system/lib]]]: findLibrary returned null
The graphics seem unstable with hardware overlays, you can really see it when opening/closing Downloads and DSP Manager.
Click to expand...
Click to collapse
A new build is currently being tested. And released soon.
Anyone using this as their daily? Currently on 7.1.2 and wondering if anyone has an opinion on performance as I probably need another rom as alot of background apps are slow like hangouts/voice.
xdause said:
Anyone using this as their daily? Currently on 7.1.2 and wondering if anyone has an opinion on performance as I probably need another rom as alot of background apps are slow like hangouts/voice.
Click to expand...
Click to collapse
Performance is awesome.
Recovery Version
I haven't done much with my HD+ since loading up CM a while back (I'm on 4.4.4 I think). Wanted to give this ROM a try since the CM one likes to reboot every day or two when it get's thinking too hard.
Question is, can I flash this with my current recovery? I'm using CWM 6.0.4.6 right now. Not sure if I needed to switch to TWRP and if so what version?
Other then wiping Data / Cache and installing the zip, anything else off hand I need to know?
Thanks all!
findmike said:
I haven't done much with my HD+ since loading up CM a while back (I'm on 4.4.4 I think). Wanted to give this ROM a try since the CM one likes to reboot every day or two when it get's thinking too hard.
Question is, can I flash this with my current recovery? I'm using CWM 6.0.4.6 right now. Not sure if I needed to switch to TWRP and if so what version?
Other then wiping Data / Cache and installing the zip, anything else off hand I need to know?
Thanks all!
Click to expand...
Click to collapse
It should work.
secretwolf98 said:
It should work.
Click to expand...
Click to collapse
Yup got brave and gave it a try once I got a backup done. Installed just fine but didn't seem to like the gapps package I installed too much. Going to play around with it a bit now that I feel slightly more confident I won't brick the thing. Thanks!
findmike said:
Yup got brave and gave it a try once I got a backup done. Installed just fine but didn't seem to like the gapps package I installed too much. Going to play around with it a bit now that I feel slightly more confident I won't brick the thing. Thanks!
Click to expand...
Click to collapse
Your welcome. Nooks can't get bricked.
Gapps
Which gapps do I use with this ROM? All that I've tried crash. I've used Open gapps and I dug up a zip from Slimroms.
Aside from the inability to use google play services, this rom is looking great.
jaydeedid said:
Which gapps do I use with this ROM? All that I've tried crash. I've used Open gapps and I dug up a zip from Slimroms.
Aside from the inability to use google play services, this rom is looking great.
Click to expand...
Click to collapse
I'm having the same problem.
open GAPPS - play store partially loads then FCs
PA - fails to install "incompatible gapps already installed" even though there isn't any.
slim gapps from the old site - can't sign in, play services FCs
Also, why isn't there a browser built in?
EDIT: It seems CWM doesn't completely clear my previous attempts when wiping. Is there a recovery that'll do an actual full wipe? Latest TWRP is broken for older android versions.
JerichoKru said:
I'm having the same problem.
open GAPPS - play store partially loads then FCs
PA - fails to install "incompatible gapps already installed" even though there isn't any.
slim gapps from the old site - can't sign in, play services FCs
Also, why isn't there a browser built in?
EDIT: It seems CWM doesn't completely clear my previous attempts when wiping. Is there a recovery that'll do an actual full wipe? Latest TWRP is broken for older android versions.
Click to expand...
Click to collapse
use twrp 3.1.1
Is there a root or magisk alternative for this that works with netflix?
News :
Starting today, i'll just upload the firmware if it has a change in it.
So you know there's no need to update the firmware if there's no change in it, save the hassle.
Tips :
* I've added checksum file for each firmware-only files in google drive, so you guys can see what's changed on every firmware-only release.
* If you experience sim card not detected after flashing firmware, don't worry, it's normal. do this, plug out and plug in your sim card tray, and restart your device.
[FIRMWARE-ONLY]
Recommended : 9.2.21
Latest : 9.2.21
https://drive.google.com/drive/folders/1PGmzEcmgG0XhRB7110CDDTgMwmw4N3MM
[ROMS - CHINA]
http://www.miui.com/download-323.html
[ROMS - GLOBAL]
http://en.miui.com/download-317.html
yep i believe the Miui10 is in Alpha and currently being tested by a closed group of users. we should see public Beta releases towards the end of June.
Im just curious if there is any difference in battery consumption to previous version of MIUI.
I've tried it a couple of days ago. There are some visual changes like new notifications panel UI, recents UI, In-call UI etc. A bit more IOS-ish as some say.
First of all, if you consider flashing it;
- You need the Raupe/Blunden twrp to flash it, other recoveries end up with error 7.
- After flashing this build; twrp will ask for a decrypt password and no password will be correct. So your internal storage won't be mounted on twrp no way to fix it at the moment.
- Magisk 16.4 is able to root it, don't know about previous ones.
- If you consider flashing other roms, you have to do factory reset(format data) to get your internal be able to mount on twrp again.
- It doesn't have google apps as it's China specific, so you need to install google apps manually by Google installer apk or there are zip files for miui 10 ported gapps which give force closes randomly.
- Can be a daily driver since all is working.
- Xposed won't work.
Other than these hick ups, it's good initial build. Fast and smooth, can't tell about battery life since I haven't used it for a long time. There are secondary releases(8.6.5) for some devices so can be around for Mix too. Cheers.
Sent from my Xiaomi Mi Mix using XDA Labs
Konstantine34 said:
I've tried it a couple of days ago. There are some visual changes like new notifications panel UI, recents UI, In-call UI etc. A bit more IOS-ish as some say.
First of all, if you consider flashing it;
- You need the Raupe/Blunden twrp to flash it, other recoveries end up with error 7.
- After flashing this build; twrp will ask for a decrypt password and no password will be correct. So your internal storage won't be mounted on twrp no way to fix it at the moment.
- Magisk 16.4 is able to root it, don't know about previous ones.
- If you consider flashing other roms, you have to do factory reset(format data) to get your internal be able to mount on twrp again.
- It doesn't have google apps as it's China specific, so you need to install google apps manually by Google installer apk or there are zip files for miui 10 ported gapps which give force closes randomly.
- Can be a daily driver since all is working.
- Xposed won't work.
Other than these hick ups, it's good initial build. Fast and smooth, can't tell about battery life since I haven't used it for a long time. There are secondary releases(8.6.5) for some devices so can be around for Mix too. Cheers.
Click to expand...
Click to collapse
I'm willing to give this a shot, thanks for the input ??
Ok trying it now and everything seems to be working good. A little laggy at the moment so I'm just letting it set in. I was hoping the camera would've gotten updated but same old crappy camera software from previous MIUI firmware. Hopefully when they do release the final version we'll get a updated camera but all in all this is a keeper till we get updated version on here, hopefully...
juggaknot77 said:
Ok trying it now and everything seems to be working good. A little laggy at the moment so I'm just letting it set in. I was hoping the camera would've gotten updated but same old crappy camera software from previous MIUI firmware. Hopefully when they do release the final version we'll get a updated camera but all in all this is a keeper till we get updated version on here, hopefully...
Click to expand...
Click to collapse
Have face unlock maybe?
zrzatore said:
Have face unlock maybe?
Click to expand...
Click to collapse
Haven't tried that but I'll look into it today and report back.
---------- Post added at 04:27 PM ---------- Previous post was at 03:36 PM ----------
Ok going through settings and as far as I can tell I don't see face unlock feature. I highly doubt the mix will get seeing as how old it is now, I never use it anyway on other devices so it's not a big deal to me. Everything is running very smooth and fast, I'm liking the Android P style look a lot, more than how it looks on the pixel but that's just me.
How did you go past decrypt after flashing via TWRP?
Wmateria said:
How did you go past decrypt after flashing via TWRP?
Click to expand...
Click to collapse
You just cancel it and internal storage will be unable to use on twrp. If you flash other things, you need to do it by an OTG.
Sent from my Xiaomi Mi Mix using XDA Labs
Konstantine34 said:
You just cancel it and internal storage will be unable to use on twrp. If you flash other things, you need to do it by an OTG.
Click to expand...
Click to collapse
Oh yes yes, I always use OTG just in case. Thanks for the info.
I installed it, but I keep loosing the recovery, when I reboot it goes to the Miui recovery.
Is there a way to disable the factory recovery overwriting the twrp.
Appreciate any help.
Thanks.
Konstantine34 said:
You just cancel it and internal storage will be unable to use on twrp. If you flash other things, you need to do it by an OTG.
Sent from my Xiaomi Mi Mix using XDA Labs
Click to expand...
Click to collapse
doesn't it will be solved just by formatting data?
fatouraee said:
I installed it, but I keep loosing the recovery, when I reboot it goes to the Miui recovery.
Is there a way to disable the factory recovery overwriting the twrp.
Appreciate any help.
Thanks.
Click to expand...
Click to collapse
i think you should flash this file in twrp :
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
after that the recovery shouldn't get replaced anymore.
That's weird I don't have any issues seeing my storage in TWRP, everything works.
juggaknot77 said:
That's weird I don't have any issues seeing my storage in TWRP, everything works.
Click to expand...
Click to collapse
really? can you show us the screenshot of the storage in twrp? what twrp version did you use? what other procedure did you perform in order not to encrypt storage? thanks
Thanks. That seems to have worked.
fatouraee said:
I installed it, but I keep loosing the recovery, when I reboot it goes to the Miui recovery.
Is there a way to disable the factory recovery overwriting the twrp.
Appreciate any help.
Thanks.
Click to expand...
Click to collapse
You need to delete
- system/etc/recovery-resource.dat
- system/bin/install-recovery.sh
- system/recovery-from-boot.p
rhong said:
really? can you show us the screenshot of the storage in twrp? what twrp version did you use? what other procedure did you perform in order not to encrypt storage? thanks
Click to expand...
Click to collapse
Honestly I didn't do anything different, followed the instructions on the 1st post, everything works on my end.
juggaknot77 said:
Honestly I didn't do anything different, followed the instructions on the 1st post, everything works on my end.
Click to expand...
Click to collapse
i think he should need to format his Data and Internal Storage.
i can't remember the detail, but i once encountered this too, and i read that something about F2FS not supported or whatsoever.
heindrix said:
i think he should need to format his Data and Internal Storage.
i can't remember the detail, but i once encountered this too, and i read that something about F2FS not supported or whatsoever.
Click to expand...
Click to collapse
It's weird I didn't format anything, just updated twrp, backed up my rom, wiped everything, installed new miui 10, installed magisk, wiped cache and dalvik and everything works perfectly...