Related
Already tired of this Full Wipe. When it can simply be updated?: Смущен:
What?! I don't know what you're asking.
kotofei13 said:
Already tired of this Full Wipe. When it can simply be updated?: Смущен:
Click to expand...
Click to collapse
Hi,
You need to give information about your phone,your situation,and your problem.
update
Sense 4.1 v.3.5.0 phone sensation. Latest update from 3.4.0 without Full VIPe not updated. I have to constantly make Full VIPe and re set all the programs and make all the settings.
update
Sorry for bad English
kotofei13 said:
Sense 4.1 v.3.5.0 phone sensation. Latest update from 3.4.0 without Full VIPe not updated. I have to constantly make Full VIPe and re set all the programs and make all the settings.
Click to expand...
Click to collapse
Hi,
What does the [OP] say?
If he says you are recommended to wipe before you update,then,that is the best thing to do.
If you do a "Dirty flash" (without wiping) then, you run the risk of running into errors.
You cannot report these because it is a dirty flash.
So,no one will be able to help you with them.
The choice is yours...
update
understood. thanks
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:
Tried searching but couldn't really find a definite answer. I'm coming from the world of nexus devices where the nexus 6 and 9 both force encryption. Since the shield tablet is fairly close to stock android I wanted to know if it forces encryption on lollipop or is it optional?
Also if encryption is optional does it provide an option to decrypt (like most samsung devices) if you do decide to encrypt it or do you just have factory reset it to get rid of encryption?
Thanks
Anyone? Just want to know if encryption is mandatory or optional on lollipop for the shield tablet. Any insight would be helpful.
ikecomp said:
Anyone? Just want to know if encryption is mandatory or optional on lollipop for the shield tablet. Any insight would be helpful.
Click to expand...
Click to collapse
I've done the update a few days ago, and haven't been forced to encrypt yet.
durgis said:
I've done the update a few days ago, and haven't been forced to encrypt yet.
Click to expand...
Click to collapse
Thanks! What I needed to know.
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...
I am having an issue work my car stereo connecting to "media audio" on my phone. The phone always connects and media audio works fine with all other Bluetooth devices except my car. I can get it to work after the stereo says no connection I toggle media audio and then it connects. It used to auto connect no problem. Any help would be appreciated.
Stereo: Standard 2015 Mitsubishi Outlander Sport
ROM: OOS 10 Stable
Phone Mods: FDE.AI, rooted, bootloader unlock
Magisk modules: Oxytweaker, Google dialer framework, YouTube vanced
I had a similar issue suddenly appear. The first saved Bluetooth device auto connected. None of the others would. Couldn't figure out what to do. In the end I rebooted to TWRP and restored.
RogerNZ said:
I had a similar issue suddenly appear. The first saved Bluetooth device auto connected. None of the others would. Couldn't figure out what to do. In the end I rebooted to TWRP and restored.
Click to expand...
Click to collapse
Were you on 10?
jac0b said:
Were you on 10?
Click to expand...
Click to collapse
Yes, 10.0 with xxxNoLimits
To get the Bluetooth to work right will I need to downgrade back to 9.5.11
RogerNZ said:
Yes, 10.0 with xxxNoLimits
Click to expand...
Click to collapse
What are you running now the same 10.0
10.0.1 with xxxNoLimts
RogerNZ said:
10.0.1 with xxxNoLimts
Click to expand...
Click to collapse
I have updated to 10.0.1 and same issue could you know I am doing wrong i don't use xXx or custom kernel but would like to use 10
SirFronts said:
could you know what I am doing wrong
Click to expand...
Click to collapse
No sorry, I wish I could. But I am not clever with phones.
I restored system. That did not fix it.
I restored vendor. That did not fix it.
I restored data. That fixed it.
It doesn't make sense to me. But that is what I did.
I hope someone else more knowledgeable than you or I can chip into the conversation here.
RogerNZ said:
No sorry, I wish I could. But I am not clever with phones.
I restored system. That did not fix it.
I restored vendor. That did not fix it.
I restored data. That fixed it.
It doesn't make sense to me. But that is what I did.
I hope someone else more knowledgeable than you or I can chip into the conversation here.
Click to expand...
Click to collapse
How do you just restore data I may try that after work today
Thank you not a lot of people will even give me new ideas other then reinstall it or going thru and resetting my Bluetooth, WiFi and mobile data
Or deleting cache and storage under the Bluetooth app
SirFronts said:
How do you just restore data
Click to expand...
Click to collapse
TWRP > Restore > Data
Of course, if you have not previously backed up Data in TWRP, then it will not be possible.
With regards to all those other suggestions you mentioned, none of them worked for me. But if you have not yet tried them, I would still suggest you do.
Good luck!
RogerNZ said:
TWRP > Restore > Data
Of course, if you have not previously backed up Data in TWRP, then it will not be possible.
With regards to all those other suggestions you mentioned, none of them worked for me. But if you have not yet tried them, I would still suggest you do.
Good luck!
Click to expand...
Click to collapse
Bet so I should do a back up of my 9.5.11 and the update to 10.0.1 keep root and then use twrp hit restore and just restore the data right
SirFronts said:
Bet so I should do a back up of my 9.5.11 and the update to 10.0.1 keep root and then use twrp hit restore and just restore the data right
Click to expand...
Click to collapse
There is no point in restoring Data unless your backup was done prior to the issue arising.
If you already have 9.5.11 System, Vendor and Data backed up, and you know at the time of back up there were no Bluetooth issues - then yes restore that. But I don't know the process to downgrade like that. If you are successful in that, then you should be able to upgrade from there afterward. Hopefully without further Bluetooth error.
But I need to remind you. I am not good with phones and can't be sure restoring Data is what actually worked. It doesn't make sense to me that it would.
RogerNZ said:
There is no point in restoring Data unless your backup was done prior to the issue arising.
If you already have 9.5.11 System, Vendor and Data backed up, and you know at the time of back up there were no Bluetooth issues - then yes restore that. But I don't know the process to downgrade like that. If you are successful in that, then you should be able to upgrade from there afterward. Hopefully without further Bluetooth error.
But I need to remind you. I am not good with phones and can't be sure restoring Data is what actually worked. It doesn't make sense to me that it would.
Click to expand...
Click to collapse
No I understand I've already downgraded and upgraded and downgraded the software a few times so I think I got that under control but yeah I'll try restoring data after I update because Bluetooth works on the 9.5.11 update no problem
Thank you again
RogerNZ said:
There is no point in restoring Data unless your backup was done prior to the issue arising.
If you already have 9.5.11 System, Vendor and Data backed up, and you know at the time of back up there were no Bluetooth issues - then yes restore that. But I don't know the process to downgrade like that. If you are successful in that, then you should be able to upgrade from there afterward. Hopefully without further Bluetooth error.
But I need to remind you. I am not good with phones and can't be sure restoring Data is what actually worked. It doesn't make sense to me that it would.
Click to expand...
Click to collapse
Just wanted to update restoring my data put me in a bootloop it's cool IDK what it could be
I don't have this issue... I'm on OSS 10.0.1 stock
SirFronts said:
in a bootloop
Click to expand...
Click to collapse
Sorry to hear that
spinoza23 said:
I don't have this issue... I'm on OSS 10.0.1 stock
Click to expand...
Click to collapse
I'm running 10.0.1
Do you think if I install a new kernel it might start working again that's the only thing I have not tried
RogerNZ said:
Sorry to hear that
Click to expand...
Click to collapse
It happens lol but thanks for the looking out I rather try something then nothing kinda out look just thank God for the MSM Tool lmao ?
SirFronts said:
I'm running 10.0.1
Do you think if I install a new kernel it might start working again that's the only thing I have not tried
Click to expand...
Click to collapse
I don't know, but you have the same model like me...
I'm in completely stock ROM no root, no magisk, no bootloader unlocked.
My car SUV Renault Koleos 2019... Aptx, Aptx-HD works great