Related
I was hoping to try out one of the 4.2 builds tonight, but every time I try to flash one through TWRP it just says "Failed"; I've tried CM10.1 and Eclipse ROM and they both had the same result. Also tried redownloading ROMs and re-copying them to my SD card, still no change. Can anyone tell me what I'm doing wrong here? I've never had a problem flashing any ROM before.
Devilicus said:
I was hoping to try out one of the 4.2 builds tonight, but every time I try to flash one through TWRP it just says "Failed"; I've tried CM10.1 and Eclipse ROM and they both had the same result. Also tried redownloading ROMs and re-copying them to my SD card, still no change. Can anyone tell me what I'm doing wrong here? I've never had a problem flashing any ROM before.
Click to expand...
Click to collapse
What version of TWRP are you running?
If you haven't done it lately, I would suggest updating your twrp to the latest and trying again.
I'm running the newest TWRP (I think), version 2.4.1.0
Devilicus said:
I'm running the newest TWRP (I think), version 2.4.1.0
Click to expand...
Click to collapse
Weird. I am on that same version and have been flashing 4.2 roms for the last few weeks without any issues.
A few things I would try:
-Double check the md5 of the rom you are flashing
-Make sure it is a d2vzw rom
-Wipe caches, delete user data and wipe system
-Put the rom on the internal sdcard before flashing.
Other than that, I got nothing
Relentless D said:
Weird. I am on that same version and have been flashing 4.2 roms for the last few weeks without any issues.
A few things I would try:
-Double check the md5 of the rom you are flashing
-Make sure it is a d2vzw rom
-Wipe caches, delete user data and wipe system
-Put the rom on the internal sdcard before flashing.
Other than that, I got nothing
Click to expand...
Click to collapse
Damn, yeah I can't figure it out; all the ones I've tried were Verizon ones, made sure to wipe everything as usual, tried putting it on the internal SD card and the external, won't work on either one. Very frustrating. But thanks for the help anyway
Ok, I think I figured out the problem (won't be sure until I try it), but I think what happened is I edited my build.prop to the Sprint GS3 to get Google Wallet to work, forgot to change it back, and updated TWRP (which installed the Sprint version, not Verizon), and that's why the flashes are failing. So if any other people are having the same problem, that might be why. Yes I'm an idiot lol. Hopefully this fixes it
Try carbon ROM.
First to work for me.
Sent from my SCH-I535 using xda app-developers app
Devilicus said:
Ok, I think I figured out the problem (won't be sure until I try it), but I think what happened is I edited my build.prop to the Sprint GS3 to get Google Wallet to work, forgot to change it back, and updated TWRP (which installed the Sprint version, not Verizon), and that's why the flashes are failing. So if any other people are having the same problem, that might be why. Yes I'm an idiot lol. Hopefully this fixes it
Click to expand...
Click to collapse
What baseband [modem] do you have installed? ...and some more info if build prop wasn't the issue. Would also be interested if, "but I think what happened is I edited my build.prop", was the issue and you fixed it. Let us know. Goodluck
JohnAreBee said:
What baseband [modem] do you have installed? ...and some more info if build prop wasn't the issue. Would also be interested if, "but I think what happened is I edited my build.prop", was the issue and you fixed it. Let us know. Goodluck
Click to expand...
Click to collapse
Yeah it turns out that was the problem. I edited my build.prop to match the Sprint GS3, so I could download Google Wallet from the Play Store and use it. I just never bothered to change the build.prop back. And when I updated TWRP through GooManager, it assumed I had a Sprint GS3 and installed the wrong recovery. When I flashed the correct Verizon version of TWRP everything worked fine. Thanks for the suggestions everyone
Devilicus said:
Yeah it turns out that was the problem. I edited my build.prop to match the Sprint GS3, so I could download Google Wallet from the Play Store and use it. I just never bothered to change the build.prop back. And when I updated TWRP through GooManager, it assumed I had a Sprint GS3 and installed the wrong recovery. When I flashed the correct Verizon version of TWRP everything worked fine. Thanks for the suggestions everyone
Click to expand...
Click to collapse
Good call. Might be worth mentioning over in the wallet thread. It could save someone the headache you just experienced. Congrats on getting it working.
Sent from my SCH-I535 using Tapatalk 2
Had anybody seen a situation where the recovery won't keep the correct date and time? I've flashed TWRP 2.7.1.0, 2.8.0.1, and the latest Philz, and all of them kept changing the time, the timezone, and the date... and they were acting a little buggy in their responsiveness.
Thoughts?
WarAxe said:
Had anybody seen a situation where the recovery won't keep the correct date and time? I've flashed TWRP 2.7.1.0, 2.8.0.1, and the latest Philz, and all of them kept changing the time, the timezone, and the date... and they were acting a little buggy in their responsiveness.
Thoughts?
Click to expand...
Click to collapse
I've experienced the same issue since I got my S5. KT TWRP 2.8.1.0 doesn't have that problem. It also fixes the backup to extSD problem, if you were experiencing that.
Ramer84015 said:
I've experienced the same issue since I got my S5. KT TWRP 2.8.1.0 doesn't have that problem. It also fixes the backup to extSD problem, if you were experiencing that.
Click to expand...
Click to collapse
THANKS! I had KT's downloaded but didn't flash it yet... I certainly will now. And yes, the extSD issue bit me, too.
Nope... date is 1/1/2014 and the time is 3 hours lagging for the timezone.
Let's hope at the very least my nandroid backups won't disappear.
WarAxe said:
Nope... date is 1/1/2014 and the time is 3 hours lagging for the timezone.
Let's hope at the very least my nandroid backups won't disappear.
Click to expand...
Click to collapse
Try this: Using something like Root Explorer, look for the TWRP folder on your internal SD card. There's a file called ".twrps". It's the config file for TWRP. Delete it and then boot back into TWRP. You'll have to redo your setting (timezone, screen timeout etc.). See if that fixes it. If that doesn't do it, not sure what else will.
Ramer84015 said:
Try this: Using something like Root Explorer, look for the TWRP folder on your internal SD card. There's a file called ".twrps". It's the config file for TWRP. Delete it and then boot back into TWRP. You'll have to redo your setting (timezone, screen timeout etc.). See if that fixes it. If that doesn't do it, not sure what else will.
Click to expand...
Click to collapse
I had tried peeking into the file with Notepad++ but nothing jumped out at me. Now I feel silly for not trying what you suggested.
I deleted it and it had no effect. The one I deleted and the one it created had the wrong date/time stamps on them... as did the two backups I created (both in metadata and filename convention).
On the bright side... my two backups are as yet undeleted.
WarAxe said:
I had tried peeking into the file with Notepad++ but nothing jumped out at me. Now I feel silly for not trying what you suggested.
I deleted it and it had no effect. The one I deleted and the one it created had the wrong date/time stamps on them... as did the two backups I created (both in metadata and filename convention).
On the bright side... my two backups are as yet undeleted.
Click to expand...
Click to collapse
Very strange, I was sure that was it. My date/time have been correct since using it. The only other thing I may have done was using KT Kernel as well, but I don't think that was it. If you decide to try KT Kernel and want to go back to stock kernel, here's a link for stock: http://forum.xda-developers.com/showpost.php?p=54632862&postcount=1702
Another thought: What version is your firmware? Should be NE5. If not, here's that link: http://forum.xda-developers.com/showthread.php?t=2798079
Ramer84015 said:
Very strange, I was sure that was it. My date/time have been correct since using it. The only other thing I may have done was using KT Kernel as well, but I don't think that was it. If you decide to try KT Kernel and want to go back to stock kernel, here's a link for stock: http://forum.xda-developers.com/showpost.php?p=54632862&postcount=1702
Another thought: What version is your firmware? Should be NE5. If not, here's that link: http://forum.xda-developers.com/showthread.php?t=2798079
Click to expand...
Click to collapse
Thanks for the links.
I didn't flash the KT Kernel because the post said it needed to be flashed onto a TouchWiz based ROM... and right now I have PacMan (AOKP). I had MOAR (NE5) installed for a bit but I'm not used to stock. Truthfully, MOAR had everything I could want... I may just have to get over my snootiness.
Oh, it's coming back to me... with MOAR I was getting a lot of error popups of processes stopping running. i think "acore" was a common one. I could have troubleshot but didn't.
WarAxe said:
Oh, it's coming back to me... with MOAR I was getting a lot of error popups of processes stopping running. i think "acore" was a common one. I could have troubleshot but didn't.
Click to expand...
Click to collapse
Make sure your backup works and come on over I'm a big supporter of MOAR! Do a clean install though and I bet 99.9% of your problems will be solved
Ramer84015 said:
Make sure your backup works and come on over I'm a big supporter of MOAR! Do a clean install though and I bet 99.9% of your problems will be solved
Click to expand...
Click to collapse
There's the main install 2.1, and the new stuff 1.7, and of course Gapps. Do folks typically flash them all together... Or separately sequentially?
My clean install is usually wiping cache, dalvik, data, and system.
WarAxe said:
There's the main install 2.1, and the new stuff 1.7, and of course Gapps. Do folks typically flash them all together... Or separately sequentially?
My clean install is usually wiping cache, dalvik, data, and system.
Click to expand...
Click to collapse
MOAR is TW, so gapps is included. My FAQ and guide for MOAR may help you get a feel for it.
Ramer84015 said:
MOAR is TW, so gapps is included. My FAQ and guide for MOAR may help you get a feel for it.
Click to expand...
Click to collapse
Okay... MOAR's on there now. I'll read up and tweak to the extent I'm able and see if I have any questions.
WarAxe said:
Okay... MOAR's on there now. I'll read up and tweak to the extent I'm able and see if I have any questions.
Click to expand...
Click to collapse
Feel free to post any questions on the Q&A thread. :good:
EDIT: Mounted system as R/W and i'm now restoring my stock unrooted backup of the system. But My "System Image" backup gives me ERROR=2?
So I had the xposed disabler zip on my SD, I had a system image backup from before I rooted, a full normal backup as well.
It wouldn't boot after I flashed the Xposed Zip from here: http://forum.xda-developers.com/showthread.php?t=3034811
I flashed the one for SDK21-arm64.
I was like okay, and flashed the disabler, it said no backup of something made so no way to restore.
I sighed and tried restoring the system image, error, I tried restoring the full normal backup, mounted read only can't restore?
What should I do?
I have TWRP installed so I can boot into bootloader and recovery, not sure how to fix this.
Found out how to mount the system as read/write. Trying to restore again.
"Process ended with ERROR=2"
Mounted system as R/W and i'm now restoring my stock unrooted backup of the system. But My "System Image" backup gives me ERROR=2?
Yep. It doesn't work. Basically I just booted twrp, installed the uninstall zip and wiped cache to fix.
I think there's a version 22 that also didn't work. It gave an error trying to install. Here's the thread if you want to try it.
http://forum.xda-developers.com/xposed/super-alpha-posted-permission-xposed-t3072979
Xposed Framework for Alcatel Idol 3
Was there any error when installing xposed? Did anyone do an adb logcat on bootup to a text file to catch the error? Did anyone report the issue to the Xposed for Lollipop thread? (not sure why you'd be looking in the xposed for 5.1 thread since we are still on 5.0.2 but I found no sign of the words "alcatel" or "idol" in either thread. They can't fix it if they don't know about it.
oh man i wouldnt risk installing it hope theres a build compatible for us
gecko702 said:
oh man i wouldnt risk installing it hope theres a build compatible for us
Click to expand...
Click to collapse
Oh I don't plan on installing it till it's known to work but for folks who already did they should report as much as possible to the xposed thread so it can be corrected although we now have system images to revert to if necessary. http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745
neilownz said:
Yep. It doesn't work. Basically I just booted twrp, installed the uninstall zip and wiped cache to fix.
I think there's a version 22 that also didn't work. It gave an error trying to install. Here's the thread if you want to try it.
http://forum.xda-developers.com/xposed/super-alpha-posted-permission-xposed-t3072979
Click to expand...
Click to collapse
don't even try this one it's 5.1 ONLY!!!!
i'll test v68 from romracer as soon as the ****in post office will bring me my phone
famewolf said:
Oh I don't plan on installing it till it's known to work but for folks who already did they should report as much as possible to the xposed thread so it can be corrected although we now have system images to revert to if necessary. http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745
Click to expand...
Click to collapse
well i went to the xposed unofficial build thread and it says its for 5.1 though still im not going to risk it lol im a very cautious person ><
gecko702 said:
well i went to the xposed unofficial build thread and it says its for 5.1 though still im not going to risk it lol im a very cautious person ><
Click to expand...
Click to collapse
As mentioned multiple times by me and others...no one should be going to the unoffical xposed for android 5.1 thread...if it was gonna work it would be the offical "android for lollipop thread (5.0)". Of course if no one reports the errors then it will never get fixed. Oh well...will re-evaluate it in a few months.
Hopefully this will work soon, I miss Xposed. There was a guy that posted a logcat from his Idol in the Xposed 5.0 thread, but I don't seen any responses to him.
KryPTiCk0d3 said:
Hopefully this will work soon, I miss Xposed. There was a guy that posted a logcat from his Idol in the Xposed 5.0 thread, but I don't seen any responses to him.
Click to expand...
Click to collapse
i miss it too i had once on my htc one sv it was great plus the adblocker for youtube was phenomenal
edit: well heres something for 5.0 maybe should work? http://forum.xda-developers.com/showthread.php?p=62065892#post62065892
gecko702 said:
i miss it too i had once on my htc one sv it was great plus the adblocker for youtube was phenomenal
edit: well heres something for 5.0 maybe should work? http://forum.xda-developers.com/showthread.php?p=62065892#post62065892
Click to expand...
Click to collapse
The OP had a different error, so I'm not sure if that newer version would help... I would try it out, but I have too many things to do this weekend other than fix my phone :laugh::laugh:
Ill give it a shot ill post results later im busy now going to have my coffee now
Edit: i flashed the xposed arm64 version rebooted and i got stuck in the white alcatel logo that says smart move i left it alone for a few minutes and nothing so i flashed the uninstaller and went back to normal not sure if i need to wipe the dalvik after i install the xposed hmmm might retry again
So I flashed xposed-v69-sdk21-arm64.zip, wiped Dalvik & Cache, and it still hung at boot, I did get an adb logcat on boot for it, and I have attached that in the Xposed thread. Hopefully it will help us get this resolved. I was able to revert back with the uninstaller.
KryPTiCk0d3 said:
So I flashed xposed-v69-sdk21-arm64.zip, wiped Dalvik & Cache, and it still hung at boot, I did get an adb logcat on boot for it, and I have attached that in the Xposed thread. Hopefully it will help us get this resolved. I was able to revert back with the uninstaller.
Click to expand...
Click to collapse
oh yeah i havent thought about making a logcat...have you gotten any responses?
gecko702 said:
oh yeah i havent thought about making a logcat...have you gotten any responses?
Click to expand...
Click to collapse
No, I haven't.
had just one answer after posting logcat, they said it was something with odexed rom
tested r70 and still no luck
keyra74 said:
had just one answer after posting logcat, they said it was something with odexed rom
tested r70 and still no luck
Click to expand...
Click to collapse
so we basically need to have a deodexed rom huh?
Hey guys, I'm having a problem here.two days ago I had a problem with my play store which would not open, so I thought of flashing my ROM and gapps again in hopes of getting the problem solved. I wiped my cache partitions along with my system partition and flashed it, everything went well, play store started working again but this time I got a couple of different problems. My ringtones and notification tones are missing, when I click on the options for changing them there's just one option (none). My music player can't read any music files, even though I have many of them. And gallery has some albums missing. I was on cm12.1 and I flashed to liquid smooth v4.1 in hopes of fixing the problem. But the problem still persists, what should I do to fix it. Please help me on this one.
mohdfahad47 said:
Hey guys, I'm having a problem here.two days ago I had a problem with my play store which would not open, so I thought of flashing my ROM and gapps again in hopes of getting the problem solved. I wiped my cache partitions along with my system partition and flashed it, everything went well, play store started working again but this time I got a couple of different problems. My ringtones and notification tones are missing, when I click on the options for changing them there's just one option (none). My music player can't read any music files, even though I have many of them. And gallery has some albums missing. I was on cm12.1 and I flashed to liquid smooth v4.1 in hopes of fixing the problem. But the problem still persists, what should I do to fix it. Please help me on this one.
Click to expand...
Click to collapse
What version of the phone do you have? Also which gapps did you flash?
TrypelZ said:
What version of the phone do you have? Also which gapps did you flash?
Click to expand...
Click to collapse
Well Im using note 3 sm n9005 the international version. And the gapps I downloaded it from highonandroid.com, max lee's site. I'll attach the screen shots.
mohdfahad47 said:
Well Im using note 3 sm n9005 the international version. And the gapps I downloaded it from highonandroid.com, max lee's site. I'll attach the screen shots.
Click to expand...
Click to collapse
Try this gapps : https://www.androidfilehost.com/?fid=24052804347785468
Also try to clean flash your rom again and flash gapps right aftet installing. Im using the same gapps package.
TrypelZ said:
Try this gapps : https://www.androidfilehost.com/?fid=24052804347785468
Also try to clean flash your rom again and flash gapps right aftet installing. Im using the same gapps package.
Click to expand...
Click to collapse
Thanks bud, ill give it a go. So this problems are caused because of the gapps package?
mohdfahad47 said:
Thanks bud, ill give it a go. So this problems are caused because of the gapps package?
Click to expand...
Click to collapse
The playstore problem for sure.
Maybe you can consider updating your bootloader and modem to the latest version if that does not help.
TrypelZ said:
The playstore problem for sure.
Maybe you can consider updating your bootloader and modem to the latest version if that does not help.
Click to expand...
Click to collapse
Well i flashed it all again with the gapps package you told me. The problem still persists. Upgrading the bootloader and modem...how do i do that ? Im new in all this rooting and flashing.and yeah i read some forums on this issue and i read that restoring an old nandroid backup might solve the problem. What do you say, should i try doing that?? And yeah one more thing, do you think that some how a rom can slow up the cellular data speed?? Cuz i think after installing liquidsmooth my data is kinda slow even on lte.
mohdfahad47 said:
Well i flashed it all again with the gapps package you told me. The problem still persists. Upgrading the bootloader and modem...how do i do that ? Im new in all this rooting and flashing.and yeah i read some forums on this issue and i read that restoring an old nandroid backup might solve the problem. What do you say, should i try doing that?? And yeah one more thing, do you think that some how a rom can slow up the cellular data speed?? Cuz i think after installing liquidsmooth my data is kinda slow even on lte.
Click to expand...
Click to collapse
Hmm i don't know that for sure,i only knoe that on some rom's my wifi works better or worse
About your problem : i never had this kind of problems,i had a google play problem once,but after reinstalling gapps it was gone,although im on the latest bootloader and modem : https://www.androidfilehost.com/?fid=24052804347759102
I can't find my guide for flashing it so i can explain a bit :
-Download odin 3.09 on your computer
-unzip modem.zip
-shut down your phone and pull the battery out
- in odin untick auto reboot
- put the battery back in and go straight to download mode ( home,power and vol up i think,if not that vol down ^^ )
- in odin put the modem file in the 'cp' slot or what so called ( it should be cp but better look it up )
-Start flashing and wait untill it's finished ( green button lights up )
-Then reboot your phone and under phone info it should be allright.
TrypelZ said:
Hmm i don't know that for sure,i only knoe that on some rom's my wifi works better or worse
About your problem : i never had this kind of problems,i had a google play problem once,but after reinstalling gapps it was gone,although im on the latest bootloader and modem : https://www.androidfilehost.com/?fid=24052804347759102
I can't find my guide for flashing it so i can explain a bit :
-Download odin 3.09 on your computer
-unzip modem.zip
-shut down your phone and pull the battery out
- in odin untick auto reboot
- put the battery back in and go straight to download mode ( home,power and vol up i think,if not that vol down ^^ )
- in odin put the modem file in the 'cp' slot or what so called ( it should be cp but better look it up )
-Start flashing and wait untill it's finished ( green button lights up )
-Then reboot your phone and under phone info it should be allright.
Click to expand...
Click to collapse
Thanks buddy, ill give it a go. By the way i didn't flash the arter 97 kernel. Ill try flashing that too. Quick question...if i flash the kernel i should flash the latest version right??
mohdfahad47 said:
Thanks buddy, ill give it a go. By the way i didn't flash the arter 97 kernel. Ill try flashing that too. Quick question...if i flash the kernel i should flash the latest version right??
Click to expand...
Click to collapse
Yeah of course. But only flash the AOSP version
TrypelZ said:
Yeah of course. But only flash the AOSP version
Click to expand...
Click to collapse
Hmmm, the version on lord ekos note 3 liquidsmooth thread is aosp right?
mohdfahad47 said:
Hmmm, the version on lord ekos note 3 liquidsmooth thread is aosp right?
Click to expand...
Click to collapse
Yes it is. Resurrection Remix,Blisspop,CM12 by temasek,euphoria os,AICP and liqiudsmooth are all aosp,in the threads of the rom there usually is an indicator of that the rom is like. Touchwiz roms for examble are often more than 1gb files where aosp are only 200-300mb. But the battery on touchwiz for me often is a ton better.
TrypelZ said:
Yes it is. Resurrection Remix,Blisspop,CM12 by temasek,euphoria os,AICP and liqiudsmooth are all aosp,in the threads of the rom there usually is an indicator of that the rom is like. Touchwiz roms for examble are often more than 1gb files where aosp are only 200-300mb. But the battery on touchwiz for me often is a ton better.
Click to expand...
Click to collapse
Ok...well i figured out that the cellular speed issue isdue to the Carrier server problems.so flashing the modem is not necessary i guess? My current baseband version is N9005XXUGNG1. And just out of curiosity, say i flashed the arter kernel and later on for some reason i want to change the rom like i go to cm12.1. The kernel version will change automatically right?
mohdfahad47 said:
Ok...well i figured out that the cellular speed issue isdue to the Carrier server problems.so flashing the modem is not necessary i guess? My current baseband version is N9005XXUGNG1. And just out of curiosity, say i flashed the arter kernel and later on for some reason i want to change the rom like i go to cm12.1. The kernel version will change automatically right?
Click to expand...
Click to collapse
Yes it will. Apparently you have a kitkat modem and bootloader but that SHOULDN'T cause problems,although it can. I can't tell i am flashing newest bootloader and modem every time one comes out.
TrypelZ said:
Yes it will. Apparently you have a kitkat modem and bootloader but that SHOULDN'T cause problems,although it can. I can't tell i am flashing newest bootloader and modem every time one comes out.
Click to expand...
Click to collapse
Hmmm...cool. Can i flash the modem through my phone or it can be done only by odin?
mohdfahad47 said:
Hmmm...cool. Can i flash the modem through my phone or it can be done only by odin?
Click to expand...
Click to collapse
I don't know exactly cause i only flash through Odin on my PC. But it's the easiest way i know.
TrypelZ said:
I don't know exactly cause i only flash through Odin on my PC. But it's the easiest way i know.
Click to expand...
Click to collapse
Hmmm...ok, flashing the modem wipes the data and stuff? Anyways bud thanks for keeping up with me, really appreciate it.
mohdfahad47 said:
Hmmm...ok, flashing the modem wipes the data and stuff? Anyways bud thanks for keeping up with me, really appreciate it.
Click to expand...
Click to collapse
Nah it just updates your radio device. Nothing won't wipe at all. And no problem man,it's a tech forum,you can expect at least a little help
TrypelZ said:
Nah it just updates your radio device. Nothing won't wipe at all. And no problem man,it's a tech forum,you can expect at least a little help
Click to expand...
Click to collapse
Cool. And thanks again.
mohdfahad47 said:
Cool. And thanks again.
Click to expand...
Click to collapse
No problem
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...