Related
As the title says, I'm having problems trying to copy files from my PC to the phone. It's only 4 gb stuff, on the phone I have the 4.4 factory image installed yesterday and I've only installed twrp recovery and superSU to have root. Now, every time I try to copy the files to the phone I get the message "the process android.process.media has stopped" what can I do? I've tried both enabling and disabling debug USB but nothing changed.
Inviato dal mio Nexus 4 utilizzando Tapatalk
Android N Preview 3 beta npd35k (flashable & image, no encryption & dm verification)
This thread is for the third Android N Preview.
For Android N Preview 4 see: http://forum.xda-developers.com/nexus-6/general/android-n-preview-4-beta-npd56n-t3399473
** DISCLAIMER: I AM NOT A DEVELOPER. I DO THIS AS A HOBBY AND SHARE MY FINDINGS IN CASE SOMEONE ELSE FINDS THEM USEFUL. **
** THIS WORKED ON MY DEVICE BUT IT MAY NOT WORK ON YOURS. APPLY AT YOUR OWN RISK **** The following are instruction for installing Android N Preview 3 image released by Google on 5/18/2016. After the installation you will have TWRP recovery 3.0.2-0 with the data partition erased and unencrypted if you use method 2, which means you will have ~ 3GB more space and ~ 10 seconds faster boot speed **Always backup your data before flashing something a total stranger gives you!
Method 1: Flash update through TWRP recovery (keeps your data and current recovery)
1- You need to have TWRP 3.0.2-0 installed on your phone.
2- Download this flashable zip..
3- Copy to the phone internal storage and flash via recovery.
4- Reboot. Your data should still be intact and your OS is upgraded to N Preview 3 beta. If your internal storage is unencrypted before flashing it remains unencrypted.
Method 2: Flash update using a computer (wipes everything, unencrypts data, and upgrades TWRP)
1- ALL of your data including the internal storage will be lost so make a backup. (If you know what you are doing and you are coming from unencrypted Marshmallow you can modify the instructions to not lose data but I won't help you with that).
2- Download this file. Note that it is NOT a flashable zip.
3- Unzip into a folder of your choice on your PC.
4- Open a command window (cmd) and cd to this directory. then run the following:
Code:
flash-all
5- Wait until prompted, then press key to reboot the phone.
6- Your data is wiped and your OS is upgraded to N 3 beta with unencrypted internal storage. Your TWRP is also upgraded to 3.0.2-0.
Technical details: this is a repacking of the Google image with a modified Kernel and removed userdata and recovery images. Everything else is stock.
Problem downloading from Mega on a mobile browser? Change the page setting to "Request desktop site".
About root and other issues
To obtain root after installing this update you should flash SuperSU 2.72 (or higher) in recovery. Get it from here: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133.
Can confirm that I followed Method 1, coming from unencrypted Preview 2, and that it worked perfectly and I'm happily running Preview 3 with all of my data intact.
Edit: Removed an inadvertent "not" that made it look like it didn't work for me. Worked perfectly!
BaumerS4 said:
Can confirm that I followed Method 1, coming from unencrypted Preview 2, and that it worked perfectly and I'm not happily running Preview 3 with all of my data intact.
Click to expand...
Click to collapse
It's running perfectly with all your data intact but somehow you're unhappy with it? :lol:
benleonheart said:
It's running perfectly with all your data intact but somehow you're unhappy with it? :lol:
Click to expand...
Click to collapse
Was enjoying the Preview so much I couldn't type coherently.
BaumerS4 said:
Was enjoying the Preview so much I couldn't type coherently.
Click to expand...
Click to collapse
Haha!! I know! It's a nice preview! Or ..honestly it feels Beta, almost ready for launch...
Can I come from the latest chroma 6.0.1 using method 1 without a hitch?
sartau87 said:
Can I come from the latest chroma 6.0.1 using method 1 without a hitch?
Click to expand...
Click to collapse
Most likely yes. In the off chance that things give you a hard time you may have to clear the cache, clear the data for apps that crash, or worst case do a factory reset.
I love how fast you people work, great work and very much thanks for this. Just came out today and already a flashable in twrp zip, YEA BUDDY!
If im going from a custom rom what steps should I take to wipe it?
So it's pretty stable how's the kernel and overall performance? Is it up to par with MM stock?
Sent from my Nexus 6 using Tapatalk
Does this release have WiFi Calling? It's super important to me.
I did method 2 and just booted into my recovery and it seems to be the stock recovery
SuperSU = safe mode for me
Sent from my Nexus 6 using Tapatalk
Used TWRP to flash in method 1.
Flashed SU 2.72
Used root explorer to edit build.prop for tethering by adding "net.tethering.noprovisioning=true" . (Works for VZW. Your mileage may vary )
Zero issues, rooted with 2.72 and even the latest preview 2 elementalx kernel works without issues. Running great so far with directions in op post.
Flashed using method one. I was running stock marshmallow rooted with the latest TWRP. I did a full factory reset and wipe in TWRP before flashing cause I wanted to start fresh. All went well and after about 3 minites I was booted into N!! Running very smooth after some sluggishness while setting up my apps. Loving N, thanks devs!
Does this preview work with TiBu or still no dice?
SageWilliams said:
Does this preview work with TiBu or still no dice?
Click to expand...
Click to collapse
i eventually got it to work but you need to go into preferences and change app processing mode to interactive- it's time consuming this way but until i install a permissive kernel/flash the unpermissive zip if i can find one for N6.. it'll have to do.
Someone tried to flash on multirom?
Thanks
Inviato dal mio Nexus 6 utilizzando Tapatalk
I am not able to download apps from play store...stuck on download pending
Hallo.
I had unlock bootloader, install twrp and supersu: my honor 8 is rooted, but why i don't have encryption on it? When i enter in twrp, i can see all file of device.. i don't understand why.
Thank you all
djhuzi said:
Hallo.
I had unlock bootloader, install twrp and supersu: my honor 8 is rooted, but why i don't have encryption on it? When i enter in twrp, i can see all file of device.. i don't understand why.
Thank you all
Click to expand...
Click to collapse
Because either TWRP decrypts it, or because it isn't really encrypted.
I'd say it's still encrypted.
When i power on the h8, a message appears for restore the device: if i Press vol UP, i enter in a HUAWEI (special) recovery: it tell me to download last update and restore all. But this, lock the bootloader too?
Inviato dal mio FRD-L09 utilizzando Tapatalk
djhuzi said:
When i power on the h8, a message appears for restore the device: if i Press vol UP, i enter in a HUAWEI (special) recovery: it tell me to download last update and restore all. But this, lock the bootloader too?
Inviato dal mio FRD-L09 utilizzando Tapatalk
Click to expand...
Click to collapse
If you flash a stock rom on a Nexus it doesn`t lock the bootloader, so my guess with Honor is that it doesn`t lock the bootloader either unless you lock it yourself in fastboot.
djhuzi said:
When i power on the h8, a message appears for restore the device: if i Press vol UP, i enter in a HUAWEI (special) recovery: it tell me to download last update and restore all. But this, lock the bootloader too?
Inviato dal mio FRD-L09 utilizzando Tapatalk
Click to expand...
Click to collapse
Probably won't lock it
XePeleato said:
Because either TWRP decrypts it, or because it isn't really encrypted.
I'd say it's still encrypted.
Click to expand...
Click to collapse
TWRP can not decrypt your internal storage unless you give it the correct password. That means, if you can browse your /data directory in TWRP without having to enter your PIN/password, then your device is definitely not encrypted. The whole point of encryption is that you can not just boot into TWRP and look at your data!
I have the same issue on my Honor 8 and have tried a lot to get the device to encrypt the internal storage. No luck so far, unfortunately.
I don't know if the Honor 8's internal storage was decrypted before unlocking, and I don't see how one could test this (without unlocking
xor2000 said:
TWRP can not decrypt your internal storage unless you give it the correct password. That means, if you can browse your /data directory in TWRP without having to enter your PIN/password, then your device is definitely not encrypted. The whole point of encryption is that you can not just boot into TWRP and look at your data!
I have the same issue on my Honor 8 and have tried a lot to get the device to encrypt the internal storage. No luck so far, unfortunately.
I don't know if the Honor 8's internal storage was decrypted before unlocking, and I don't see how one could test this (without unlocking
Click to expand...
Click to collapse
That's the #1 mistake that people usually make. The device is encrypted, and the password is secret to you, I recommend you not to post such statements without researching a bit into Android's encryption.
Even after unlocking the bootloader, the device remains encrypted because there's a flag at the Fstab that tells vold that the data partition is encrypted, so that has nothing to do with unlocking the bootloader.
For obvious reasons, encryption is handled in such a way that the end user would never realize that it's encrypted.
I don't understand very well english, so Sorry if i reply mistake. After one full update, the smartphone wipe all and lock the bootloader. This because It enable the encryption, and is full stock with recovery stock too. When we go to made root, we need to unlock bootloader: It wipe all and don't enable encryption. For this motivazion, we can install twrp and see all file of primary Memory.
We need to by-pass the wipe when lock-unlock bootloader
Inviato dal mio FRD-L09 utilizzando Tapatalk
XePeleato said:
That's the #1 mistake that people usually make. The device is encrypted, and the password is secret to you, I recommend you not to post such statements without researching a bit into Android's encryption.
Even after unlocking the bootloader, the device remains encrypted because there's a flag at the Fstab that tells vold that the data partition is encrypted, so that has nothing to do with unlocking the bootloader.
For obvious reasons, encryption is handled in such a way that the end user would never realize that it's encrypted.
Click to expand...
Click to collapse
I am not sure I understand what you are trying to say, but if the /data partition is encrypted, the user must enter the password, otherwise it can not be decrypted. The password is either entered during a normal boot (and is usually the same as your lock code, so you will not get prompted twice), or, if you boot into TWRP recovery, you must enter the password in TWRP. I have seen this myself on a Nexus 7.
What I found out meanwhile is that SuperSU is in fact patching the /fstab so that encryption is no longer enforced after a wipe of the /data partiton. I am still struggling to re-enable it.
---------- Post added at 01:14 AM ---------- Previous post was at 01:09 AM ----------
djhuzi said:
I don't understand very well english, so Sorry if i reply mistake. After one full update, the smartphone wipe all and lock the bootloader. This because It enable the encryption, and is full stock with recovery stock too. When we go to made root, we need to unlock bootloader: It wipe all and don't enable encryption. For this motivazion, we can install twrp and see all file of primary Memory.
We need to by-pass the wipe when lock-unlock bootloader
Inviato dal mio FRD-L09 utilizzando Tapatalk
Click to expand...
Click to collapse
In fact, I found that SuperSU is patching the /fstab to remove forced encryption.
What I am currently trying is: to change the "encryptable" flag in /fstab back to "forceencrypt", then wipe /data in the hope that Android will again encrypt the /data partition. It does not work on my Honor 8 though.
aah, ok.. So we need other support about.. Thank you anyway for the work you made If there are news, post here!!
djhuzi said:
aah, ok.. So we need other support about.. Thank you anyway for the work you made If there are news, post here!!
Click to expand...
Click to collapse
If you are interested, I have posted my findings here: http://forum.xda-developers.com/honor-8/help/internal-storage-encryption-t3452737/post69689317#post69689317
This guide was almost directly taken out of XIAOMI.EU website. I just wanted to spead the wisdom and grow Mi Max 2 community.
If your device is not locked:
Install TWRP via Fastboot mode, then install XIAOMI.EU ROM.
Code:
fastboot flash recovery twrp.img
fastboot boot twrp.img
For root install SuperSU 2.82 in TWRP
If your device is locked:
Unlock your first bootloader here http://en.miui.com/unlock/. You will need a PC and it might take about 72 hours.
Install TWRP via Fastboot mode, then install our ROM.
Code:
fastboot flash recovery twrp.img
fastboot boot twrp.img
Wipe /data partition
Copy XIAOMI.EU ROM to the internal storage
Install the ROM with TWRP
Reboot
How on earth do you know which rom to download they cant all be suitable for mi max 2 (Oxygen)
Chipster69 said:
How on earth do you know which rom to download they cant all be suitable for mi max 2 (Oxygen)
Click to expand...
Click to collapse
Seems like newest weekly is missing Mi Max 2. This is the older one, which I got.
https://www.androidfilehost.com/?fid=745425885120743705
Unlocked Bootloader Hassle?
Hi all, I am considering buying the Mi Max 2 (sale today, they finally have a black version).
And of course TWRP/root it. I already own the Mi Pad 2, and the issue I see here is that after bootloader unlocking I get confronted with this nasty warning screen on every boot. Even worse, it does not continue booting until I confirm (press volume up key). This is even true for battery loading animation. Extremely annoying.
Do you see that same behavior on your unlocked Mi Max 2?
Thank you for quick reply!
No such issue
gen.san said:
Hi all, I am considering buying the Mi Max 2 (sale today, they finally have a black version).
And of course TWRP/root it. I already own the Mi Pad 2, and the issue I see here is that after bootloader unlocking I get confronted with this nasty warning screen on every boot. Even worse, it does not continue booting until I confirm (press volume up key). This is even true for battery loading animation. Extremely annoying.
Do you see that same behavior on your unlocked Mi Max 2?
Thank you for quick reply!
Click to expand...
Click to collapse
I do not have such issues after TWRP+root. I listed some of the other issues that I have in my review. However, I think none of those are very major and most of them can be fixed be software update (or possible me finding the right settings for the phone).
wwwwe said:
I do not have such issues after TWRP+root. I listed some of the other issues that I have in my review. However, I think none of those are very major and most of them can be fixed be software update (or possible me finding the right settings for the phone).
Click to expand...
Click to collapse
Thanks, I placed an order, at USD 249 for a black Mi Max 2, cannot really go wrong. Let's see how this SD625 performs in real life. I have a Letv X900 with an excellent display and super-smooth experience, so I am somewhat spoiled. But it does have limited battery life, so I expect this to be drastically better with the new Mi Max architecture. Not sure though if I prefer smooth performance or longer SOT.
wwwwe said:
Seems like newest weekly is missing Mi Max 2. This is the older one, which I got.
https://www.androidfilehost.com/?fid=745425885120743705
Click to expand...
Click to collapse
Thank you for that i'll see what version mine arrives with but twrp and root is a must lol I can't help myself
Chipster69 said:
Thank you for that i'll see what version mine arrives with but twrp and root is a must lol I can't help myself
Click to expand...
Click to collapse
Cow be
Here is twrp for xiaomi Mi max 2
XN Logos said:
Here is twrp for xiaomi Mi max
Click to expand...
Click to collapse
Will this work on mine??
trowa0830 said:
Will this work on mine??
Click to expand...
Click to collapse
Yes This is Work For you
hey how backup stock recovery?
1. boot twrp recovery, do not flash it permanently, like so:
fastboot boot "name of twrp recovery.img"
2. while in twrp, do a nandroid backup including the stock recovery.
3. if you wish you can then flash permanently the twrp recovery within twrp itself or else reboot to system.
I have mine unlocked today. Recovery is on the Max 2 but when I flash the latest Miui 8 Global - the phone stuck at the bootlogo...
Does it need Internet connection while unlocking the bootloader?
Can I use the phone while unlocking it? Does it need Internet connection and what is the requirements by doing this? Does it need to be always connected on a PC?
What if I just want root while keeping the stock ROM, how would I go about doing that? Do I still need to install TWRP?
alexep said:
What if I just want root while keeping the stock ROM, how would I go about doing that? Do I still need to install TWRP?
Click to expand...
Click to collapse
to get root you need to flash either SuperSU or Magisk. it can be done via TWRP only.. there are other methods you can root without TWRP recovery but TWRP is the easiest and safest way..
after flashing root solution you can always go back to stock recovery over TWRP recovery but it is just pointless doing so
anyone playing pokemon go on mi max 2
Has anyone playing po go and spofing on mi max 2,
i didnot find compatibility in twrp for mi max? under devices
do you can use magisk?
thank you
Hi
I'm stuck on Mi logo after flashing TWRP. The only thing that appears on the screen is Mi logo and "Unlocked". I downloaded "TWRP Oxygen2".
What shall I do? Anyone?
Edit: solved via MiFlash
Started the update, phone rebooted to TWRP. Selected system reboot.
It rebooted correctly. Now Magisk appears not to be installed, Magisk Manager asks me if I want to install Magisk 14.0 (the install button is active) but at the same time it says I have 14.0 installed.
I have no root anymore and the system update says "Verification problem", in red, and offers the option to "Try again".
Clearly I did something quite wrong. How can I go back to have Magisk installed correctly, with root, but at the same time take advantage of security updates?
Thanks in advance. I'm starting a new thread because I keep on seeing posts related to Nougat or earlier and I don't know if something has changed with Oreo (plus I'm actually not finding clear instructions on how to proceed, anyway).
Hmmm... ok, I'm back to where I started. I reinstalled Magisk from Magisk Manager, now I'm back to root enabled and Safety Net Check Success.
If there's a clear guide on how to update for monthly security patches, I'd really appreciated a link. Thanks again.
gorman42 said:
Hmmm... ok, I'm back to where I started. I reinstalled Magisk from Magisk Manager, now I'm back to root enabled and Safety Net Check Success.
If there's a clear guide on how to update for monthly security patches, I'd really appreciated a link. Thanks again.
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?t=3206928
Option #9
Inviato dal mio Nexus 6P utilizzando Tapatalk
Is it correct to follow point 9 of this guide? https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
I am probably simply too thick to understand but when I read "new build of stock ROM" I did not think it could apply to simple monthly security updates.
CyberZeus1977 said:
https://forum.xda-developers.com/showthread.php?t=3206928
Option #9
Click to expand...
Click to collapse
Thanks. So I need to do this for every monthly security update, correct? Sorry for the previous message but I wrote while you were writing.
gorman42 said:
Thanks. So I need to do this for every monthly security update, correct? Sorry for the previous message but I wrote while you were writing.
Click to expand...
Click to collapse
You're welcome. It is what I did every month.
Use thanks button if I helped you! [emoji16]
Inviato dal mio Nexus 6P utilizzando Tapatalk
Things I've discovered that might be useful for people reaching this discussion through a search:
1) Contrary to what the guide linked in previous posts here states, there's no userdata.img file in the factory download. I have angler-opr5.170623.007-factory-b4c75d12.zip and the included image-angler-opr5.170623.007.zip file does not contain userdata.img. This is not so important, considering that you do NOT want to flash that file. But still, if you read the guide and wonder what's wrong, the answer is nothing wrong. I completed the process without any problem.
2) If you follow the guide you'll lose custom recovery (you flash recovery.img after all) and root. I used adb and fastboot to reinstall TWRP (downloaded the latest from here: https://eu.dl.twrp.me/angler/) by using:
adb reboot bootloader
and then once in the bootloader (which must be unlocked):
fastboot flash recovery C:\angler\twrp-3.1.1-0-angler.img
After the custom recovery has been flashed you want to restart the device directly in recovery, otherwise it gets overwritten at first boot (you do that by keeping VOL+ and POWER pressed).
3) After flashing back Magisk, and having Magisk Manager already installed, I found all the modules I had installed were there, root permissions were kept, etc. It's quite likely normal and expected. But, for somebody going through the process for the first time, it was a nice surprise.
I write all this not because it's something new or special... I realize that I might have gathered the relevant information first by searching more thoroughly and being a little bit more brave. But I'm always scared to do something irreparable, so... my findings above are simply a way for me to give something back to the community.
Cheers!
I've found that flashfire from chainfire to be the easiest (not that adb and fastboot are difficult) way to update month to month. I'd still recommend being familiar with adb and fastboot. Having the current factory image on a pc and your device is a good idea as well.
Flashfire
https://forum.xda-developers.com/general/paid-software/flashfire-t3075433
ffejy462 said:
I've found that flashfire from chainfire to be the easiest (not that adb and fastboot are difficult) way to update month to month. I'd still recommend being familiar with adb and fastboot. Having the current factory image on a pc and your device is a good idea as well.
Flashfire
https://forum.xda-developers.com/general/paid-software/flashfire-t3075433
Click to expand...
Click to collapse
Yup, I use flashfire along with 4core boot image fix for bootlooping devices.
It is an absolute delight to be able to flash inbuilt ota without downloading 1gb of stuff just for a security patch.