Hi everyone. As an obsessed flasher from my old HTC one 7 i couldnt wait much longer to unlock and root my beloved Nexus 6P.
I have a few questions as i keep seeing the words encrypted and decrypted flying around alot. I understand what encryption is, and what it is there for. What i don't understand is how to know when my phone is encrypted or not. For example, i have unlocked, flashed mod boot img. and then had to factory reset my phone to flash TWRP 2.7.8.1 ( which said decryption not needed) i then installed SuperSU for root. I have read that factory reset can remove decryption... but i have no idea how to check.
Do i need to re-encrypt my device, if so, how do i do this? Will encryption stop root or make TWRP not work properly in regards to flashing and backups.? Can i install custom kernels with a decrypted device or again shall i re-encrypt it?
I also see a screen when entering recovery and rebooting phone "Your device software cannot be checked for corruption, please lock bootloader". Is this normal or have i done something wrong?
Thanks in advance for your help!
so ive managed to find out that the message when in recovery or rebooting is normal for marshmallow. Can anyone help me in terms of the encyrption/decryption issue please?
Long-short: I bricked the phone flashing Exodus ROM. TWRP wants a password and nothing works: yes I typed the password in correctly. (TWRP version 3.0.2.0 clark)
Phone is encrypted. Exodus had a weird issue where even though I set it to no security on boot, it still required my pin. Even after I changed it to pattern. So it would boot, ask for PIN, boot, then pattern.
TWRP cannot install anything as it is read only and won't accept any password. For some odd reason, it no longer has pattern unlock.
I tried to restore to stock (5.1.1 and 6.0) following http://forum.xda-developers.com/moto-x-style/general/guides-how-to-guides-beginners-t3200808/page17.
RSDLite would fail: "Failed flashing process. 18/22 flash modem "NON-HLOS.bin" -> phone return fail."
Both 5.1.1 and 6.0 fails at this point.
Boy, do I need some help!
sunNsnow said:
Long-short: I bricked the phone flashing Exodus ROM. TWRP wants a password and nothing works: yes I typed the password in correctly. (TWRP version 3.0.2.0 clark)
Phone is encrypted. Exodus had a weird issue where even though I set it to no security on boot, it still required my pin. Even after I changed it to pattern. So it would boot, ask for PIN, boot, then pattern.
TWRP cannot install anything as it is read only and won't accept any password. For some odd reason, it no longer has pattern unlock.
I tried to restore to stock (5.1.1 and 6.0) following http://forum.xda-developers.com/moto-x-style/general/guides-how-to-guides-beginners-t3200808/page17.
RSDLite would fail: "Failed flashing process. 18/22 flash modem "NON-HLOS.bin" -> phone return fail."
Both 5.1.1 and 6.0 fails at this point.
Boy, do I need some help!
Click to expand...
Click to collapse
It sounds like one of your partitions is messed up, same thing happened to me (my thread is in this forum, about a week old if you want to read)
Long story short, I could not fix this. I sent it to Motorola despite not having a warranty and it sounds like they fixed it by flashing factory software, I'll find out Tuesday.
Sent from my m8wl using Tapatalk
I managed to get the phone working. I decided to boot the phone (after RSDLite failed) to see if it worked: it did. It ran setup, failing to see wifi, but got through without crashing.
I did lots of things attempting to restore to stock, RSDLite restore, a manual way for the prior Moto X (it was late, I was tired), I was several lines into the command line when I realized the instructions is for the prior Moto X. I'm not sure if it helped that I was using the correct Stock file from for the Pure.
My last attempt was the easy stock restore "ROM" to 5.1.1. The phone booted, I re-rooted the phone, installed TWRP, nandroid back to the last stable save.
What borked the phone was the a dirty flash from Exodus ROM 2016-08-16 to 2016-08-18. Exodus started the TWRP issues with the password despite a pattern lock. My password worked before dirty flash, and the phone bricked, afterwards.
I got lucky: I would have had to buy a new phone (need it for work).
--
sunNsnow
Hey Guys,
I just bought the s8 yesterday and realised I did not have the OEM unlock and tried flashing the rom from the guide posted here but it didn't flash via odin because downgrading is not possible. I found the date trick on xda's portal and that worked for me and I flashed TWRP by odin.
I allowed system modifications and wiped all data and install no-verity-opt as well as magisk for root. Phone booted up fine and everything was working, I wanted to go to twrp to just check if it was working and it returned with Only official released binaries are allowed to be flashed and well the phone is soft bricked. I was wondering is there any other way other than restoring stock firmware via odin to fix this?
OEM lock shows off in download mode still, I am waiting for the sammobile firmware (5 more hours lol) to download and just wanted to know this time around, is there a fix that I am missing or a step that I missed out so that I could reboot and twrp stays as well as the phone doesn't get soft bricked as this is my daily driver
ItsmYarD said:
Hey Guys,
I just bought the s8 yesterday and realised I did not have the OEM unlock and tried flashing the rom from the guide posted here but it didn't flash via odin because downgrading is not possible. I found the date trick on xda's portal and that worked for me and I flashed TWRP by odin.
I allowed system modifications and wiped all data and install no-verity-opt as well as magisk for root. Phone booted up fine and everything was working, I wanted to go to twrp to just check if it was working and it returned with Only official released binaries are allowed to be flashed and well the phone is soft bricked. I was wondering is there any other way other than restoring stock firmware via odin to fix this?
OEM lock shows off in download mode still, I am waiting for the sammobile firmware (5 more hours lol) to download and just wanted to know this time around, is there a fix that I am missing or a step that I missed out so that I could reboot and twrp stays as well as the phone doesn't get soft bricked as this is my daily driver
Click to expand...
Click to collapse
Install rmm by pass after root before reboot. This will keep oem unlocked.
So I loved this phone long time ago, but after I got a new one, I decided to play with P9 Lite. I installed installed lineage, I had fun for a while, but I decided I want the stock soft once again. During 'rollback', something has happened and possibly bricked the phone. I forgot about it because I had some things to do in life, but now I came back to fix it...but I don't know how. It is still on a bootloop, but I can launch fastboot. I flashed some of twrp's out there, but I still cannot enter any of them. I can't use dload method, because it doesn't work either. Can anyone help me, please?
Try to go into the stock recovery , and if is possible do a cache wipe. Check if the bootloader is locked or not ( because after some operations it may be locked again ) and then try to flash a recovery in recovery and also in the Erecovery partitions.
i have same situation, flashed a lot of twrp, still cant enter none
Return back stock recoveries. I really don't think that TWRP will help you now. With stock recoveries reinstalled, try to flash B160/B161 (depending on if you have dual/single SIM) (you can choose pretty much any stock A6 version, but I think that B160/B161 is the best of all.). After a successful flash, a factory reset should start.. I think that you don't even need an unlocked bootloader or FRP.
NEVER EVER flash the rollback package two times in a row. And also, DO NOT flash Android 7 (B3xx/B5xx). Both of these actions will result in the need of DC Phoenix. Or even into a useless brick.
First of all why did this happen, presumably I wasn't doing anything wrong or uninformed. I just unlocked the bootloader successfully, afterward as many threads claimed I flashed twrp-3.3.1-2-davinci-fix, and now it simply wont boot neither to system nor twrp. Why did this happen?
Does anyone know how to fix this? Thank you!
Mi 9T (M1903F10G)
Did you try to power off and then turn back on holding power and volume up? I had this issue yesterday but doing the vol up and power got me to twrp then did format and it booted up
cmlucht said:
Did you try to power off and then turn back on holding power and volume up? I had this issue yesterday but doing the vol up and power got me to TWRP then did format and it booted up
Click to expand...
Click to collapse
Thank you for your reply. You can't even power off, it will simply bootloop forever into fastboot. Nonetheless I managed to fix it by flashing fastboot ROM using MIFlash, but man, didn't expect root solutions to be this complicated, unstable, and outdated for our beloved Mi 9T. I simply want to achieve root in the stock rom, and wasted 7 hours yesterday and still got nowhere. I come from a classic LG G2, when things were much simple and straight forward back then. You can stop reading here, but now I had to:
Wait 1 week for bootloader unlock.
Flash TWRP, which soft bricked my phone right away. Why on earth, a recovery image provided in many reliable tutorials from multiple sources cause soft-brick in the second step is beyond my comprehension. I am still genuinely curious why did this happen, and why such a broken image is still circulating here?
Then I had to inform myself all about Anti Rollback, in order to prevent it happening, and concluded that MiFlash is safe, so I got MiFlash and a fastboot rom.
Apparently Mi Flash is terribly buggy and kept showing .net error exceptions because a "LOG" folder was missing in root folder, so let's waste one hour scratching our heads what the hell is happening because the developer missed a simple MkDir line during development.
After creating LOG folder, and installing drivers, couldn't flash any fastboot ROM because my 9T antiroll back number is 1 while fastboot rom ARB index was 0.
Then it appears that this error has actually nothing to do with ARB, but it is because I had to a) start MiFlash from C:\, b) remove name spaces in target address and c) shorten fastboot ROM folder name. So I had to get all these 3 variables right in order to resurrect my phone. MiFlash terrible programming didn't stop at step 4) but it extends into showing entirely confusing ARB errors that have nothing to with the real problem, rather petty programming bugs such as folder naming.
Finally managed to boot up 9T, and we're back at square one.
Afterward successfully flashed mauronofrio TWRP including vbmeta and got recovery working.
I decided to try out few custom ROMs since all my data were erased anyway, but it appears my system was encrypted and TWRP showed encrypted alphanumeric characters, so I had to format data in order to flash files.
Now every-time I flash stock ROM .zip I lose TWRP, and every-time I reflash mauronofrio TWRP I end up in recovery bootloop, and so I can't manage to have both at same time in order to move with the Magisk flash.
10 steps and 7 hours later and still got nowhere, just risked bricking my phone.
Now we have to deal with
a) bootloader wait,
b) twrp encryption mess,
c) anti roll back risk,
d) buggy MiFlash
e) safety net measures
f) no custom ROMs that are pre-rooted and simple
g) dependency of stock ROM files - meaning you can't wipe everything including system and just flash custom ROM .zips, like I used to do with 5 android phones before this one. Now you are somehow dependent on original ROM files which probably means you will have to base install stock MI before you flash anything Xiaomi.EU, Evolution X, PixelExperience etc. When did things get so complicated? It seems every year new limitations are introduced and the sheer combination to get them all right give headaches.
Anyway, all I want is to install latest stock ROM from TWRP and keep TWRP so I can also flash Magisk. In other words, how to simply have a rooted stock?
Your mistake is to not use Official TWRP instead of an old TWRP version...
Micdu70 said:
Your mistake is to not use Official TWRP instead of an old TWRP version...
Click to expand...
Click to collapse
Thanks for your reply! Yes, that must have been it. Those outdated tutorials should be removed.
Now I flashed miui_DAVINCIEEAGlobal_V11.0.4.0.QFJEUXM through latest TWRP, but it removed TWRP. When I reflash latest TWRP then it ends up in bootloop.
EDIT: Ended up reflashing all over again using MiFlash. Now the only problem remaining is which version of Magisk is compatible with miui_DAVINCIEEAGlobal_V11.0.4.0.QFJEUXM?
What are you flashing with? I am now using xiaomitools v2 and it installed twrp and magisk with no problems.
I flashed the EU custom stable, I was global but I wanted to compare the 2 and I like the EU better.
I came from a non rootable lg g7.
I have not flashed custom ROMs since my old Galaxy note days.
cmlucht said:
What are you flashing with? I am now using xiaomitools v2 and it installed twrp and magisk with no problems.
I flashed the EU custom stable, I was global but I wanted to compare the 2 and I like the EU better.
I came from a non rootable lg g7.
I have not flashed custom ROMs since my old Galaxy note days.
Click to expand...
Click to collapse
Never heard of XiaomiTools v2, it seems like a great alternative. I used buggy MiFlash to flash fastboot ROM, flashed TWRP, then got a bootloop, formatted data from TWRP and flashed Magisk. It seems everything is working fine now, but in the future I'll make sure to check XiaomiTools v2.
I never used stock ROMs in any of my past phones, first thing I did when I bought a new phone is unlock bootloader and install Lineage or Cyanogenmod back in the days. But somehow I like MIUI so all I needed was root.
It is hard to believe that there are actually phones that have no root at all.
blackmatrix64 said:
Thank you for your reply. You can't even power off, it will simply bootloop forever into fastboot. Nonetheless I managed to fix it by flashing fastboot ROM using MIFlash, but man, didn't expect root solutions to be this complicated, unstable, and outdated for our beloved Mi 9T. I simply want to achieve root in the stock rom, and wasted 7 hours yesterday and still got nowhere. I come from a classic LG G2, when things were much simple and straight forward back then. You can stop reading here, but now I had to:
Wait 1 week for bootloader unlock.
Flash TWRP, which soft bricked my phone right away. Why on earth, a recovery image provided in many reliable tutorials from multiple sources cause soft-brick in the second step is beyond my comprehension. I am still genuinely curious why did this happen, and why such a broken image is still circulating here?
Then I had to inform myself all about Anti Rollback, in order to prevent it happening, and concluded that MiFlash is safe, so I got MiFlash and a fastboot rom.
Apparently Mi Flash is terribly buggy and kept showing .net error exceptions because a "LOG" folder was missing in root folder, so let's waste one hour scratching our heads what the hell is happening because the developer missed a simple MkDir line during development.
After creating LOG folder, and installing drivers, couldn't flash any fastboot ROM because my 9T antiroll back number is 1 while fastboot rom ARB index was 0.
Then it appears that this error has actually nothing to do with ARB, but it is because I had to a) start MiFlash from C:\, b) remove name spaces in target address and c) shorten fastboot ROM folder name. So I had to get all these 3 variables right in order to resurrect my phone. MiFlash terrible programming didn't stop at step 4) but it extends into showing entirely confusing ARB errors that have nothing to with the real problem, rather petty programming bugs such as folder naming.
Finally managed to boot up 9T, and we're back at square one.
Afterward successfully flashed mauronofrio TWRP including vbmeta and got recovery working.
I decided to try out few custom ROMs since all my data were erased anyway, but it appears my system was encrypted and TWRP showed encrypted alphanumeric characters, so I had to format data in order to flash files.
Now every-time I flash stock ROM .zip I lose TWRP, and every-time I reflash mauronofrio TWRP I end up in recovery bootloop, and so I can't manage to have both at same time in order to move with the Magisk flash.
10 steps and 7 hours later and still got nowhere, just risked bricking my phone.
Now we have to deal with
a) bootloader wait,
b) twrp encryption mess,
c) anti roll back risk,
d) buggy MiFlash
e) safety net measures
f) no custom ROMs that are pre-rooted and simple
g) dependency of stock ROM files - meaning you can't wipe everything including system and just flash custom ROM .zips, like I used to do with 5 android phones before this one. Now you are somehow dependent on original ROM files which probably means you will have to base install stock MI before you flash anything Xiaomi.EU, Evolution X, PixelExperience etc. When did things get so complicated? It seems every year new limitations are introduced and the sheer combination to get them all right give headaches.
Anyway, all I want is to install latest stock ROM from TWRP and keep TWRP so I can also flash Magisk. In other words, how to simply have a rooted stock?
Click to expand...
Click to collapse
Hey, I'm facing the same issue you faced here. Waited 7 days to unlock bootloader, after unlocking it, flashed a twrp i found on one of the youtube tutorials. Immediate bootloop. Im fairly new to all of this, and dont understand what certain words even mean tbh. Do you mind guiding me in fixing my phone? Any help would be really appreciated. Thank you.
blackmatrix64 said:
Never heard of XiaomiTools v2, it seems like a great alternative. I used buggy MiFlash to flash fastboot ROM, flashed TWRP, then got a bootloop, formatted data from TWRP and flashed Magisk. It seems everything is working fine now, but in the future I'll make sure to check XiaomiTools v2.
I never used stock ROMs in any of my past phones, first thing I did when I bought a new phone is unlock bootloader and install Lineage or Cyanogenmod back in the days. But somehow I like MIUI so all I needed was root.
It is hard to believe that there are actually phones that have no root at all.
Click to expand...
Click to collapse
i miss the Cyanogenmod days