Related
Hi,
sorry if that question has been already answered, but I cannot find an clear answer
I need to encrypt my cell phone, however each time I try I get an error telling that the encryption
did not finished correctly, and my cell phone is corrupteur and need to Factory reset
Is there a 7.1.2 Rom that exists with encryption working ?
if not do you know if a 6.x Rom exist that's support encryption.
Many thanks for your help.
I finely found a way to have ZUK Z1 encrypted under 7.1.2.
Below steps used:
Factory restore using All in One tool
Flash TWRP Official 3.0.2
Using TWRP installation of a 6.0 ROM
After boot and setup, enter Preference/Security/Encrypt
At this point ZUK Z1 appears encrypted
The issues are that under TWRP unable to mount or see files
I flashed lineage and open_gapps using the “adb sideload” option.
After a reboot, ZUK Z1 appears as encrypted
For the time being all is working fine, except the fact that TWRP cannot mount the device, because it’s encrypted. I guess that’s an issue with TWRP itself. I don’t know if a version exists to fix this ….
I tried to do it same way with several 6.0 ROMs still available here (a lot of dead links...) but each try using device encryption ends with an
automatic reboot and back to welcome screen without encryption.
At the moment I am using TWRP 3.1.0 (comming fomr 3.0.2) with 7.1.2 Nuclear ROM.
Any ideas? Device Encryption is important for me.
Ecoka said:
I tried to do it same way with several 6.0 ROMs still available here (a lot of dead links...) but each try using device encryption ends with an
automatic reboot and back to welcome screen without encryption.
At the moment I am using TWRP 3.1.0 (comming fomr 3.0.2) with 7.1.2 Nuclear ROM.
Any ideas? Device Encryption is important for me.
Click to expand...
Click to collapse
The 6.0 ROM that's worked for me was " Temasek-20160217-NIGHTLY-ham "
Make sure you fully factor restore using the All In One tool
boot your phone on V5 and setup your cell phone account
Then using TWRP install V6 ROM with the Temasek one.
then Encrypt your phone .... that's should work ok
then us "adb sideload" to inject the V7 Lineage ROM
Let me know at which step you are stuck !
Hey, sorry for long delay ...
It will work up to "Temasek-20160217-NIGHTLY-ham", flashing AOSP 4.6 (Android 7) by sideload will cause "Password wrong" problems while booting
decrypting data partition. Still hope to get a way working zu install AOSP 5.1 (Android 8.1) with full encryption. Tried TWRP 3.02 and newer 3..2.1.
no worry about "password", I already installed nightly build of Lineage without issues using sideload.
Of course I got the message about password, I just ignore it
the only point is that I had to install TWRP V2.8.7 and not 3.x. because with 3.x sometimes I was not able
to boot recovery mode.
Before each install I fully backup my cell phone in case of .... SMS, Pictures etc...
Good luck,
The problem is not the password while starting to recovery 3.x.x, its the password while booting...
1. Factory restore using All in One tool (okay, works)
2. Setup Phone and encrypt (works, okay - Password will be accepted)
3. Flash TWRP (3.02 / 3.2.1.0) - tried both (okay, works - Password for encryption Recovery will not be accepted
4. I skip that and sideload flash (clearing cache etc.) "Temasek-20160217-NIGHTLY-ham.zip" (okay, Recovery = not, While Booting = Password accepted) (I choosed PIN and something like : OfferMe#1963ZU several times)
5. I skip Password in Recovery and sideload flash (clearing cache) "lineage-14.1-20180124-nightly-ham-signed.zip" (okay, Recovery still not, While Booting = Password NOT accepted)
Seems no matter if Lineage ROM 14.1 or higher...
Still confused
I am not using password at boot. I only set a password to unlock the phone after boot.
Hi there folks!
Sorry if i open a thread, probably you've discussed somewhere before about this problem that i'm experiencing.
My OnePlus 5 basically works only with omniROM, it doesn't boot at all when i try to install another one.
I tried with this:
https://forum.xda-developers.com/oneplus-6/development/rom-aospextended-rom-v5-7-t3825642
and this one:
https://forum.xda-developers.com/oneplus-5/development/rom-crdroid-android-5-0-t3836886
I followed every step (About CRAndroid), radio firmware 5.1.5 + TWRP 3.2.3 + Gapps + Magisk 17.1 and No Verity v3 (First try without noverity, second using it)
and i followed also every step neeeded in AOSPExtended rom.
When i try to boot the phone, after the OnePlus logo, nothing happens. The phone reboots in recovery mode, that's it.
If i repeat the same steps with OmniROM it works all fine, except Magisk. If i flash Magisk on the Omni it doesn't boot, if i flash SU it works.
Could it be something related to the encryption/Decription of the device?
When i go into TWRP it doesn't ask me for a pattern or a code. It should be decrypted, right? (i'm a bit confused about that).
I purchased the phone on Gearbest, could it be a particular version of the phone that doesn't allow me to work properly with roms?
Help
did you tried old stock ROMs, 4.* versions ? then 5.0.0 and then the others
Sometimes the partitions need to be wiped. Try a fastboot format userdata; fastboot format system.
azretier said:
did you tried old stock ROMs, 4.* versions ? then 5.0.0 and then the others
Click to expand...
Click to collapse
Actually when the phone arrived i've just unlocked the bootloader and installed a custom rom....what's the purpose of this?
moffa~ said:
Sometimes the partitions need to be wiped. Try a fastboot format userdata; fastboot format system.
Click to expand...
Click to collapse
You....you're a good guy.
I did the command you said, then i booted into TWRP, flashed AospExtended, Gapps Pico and Magisk 17.1 - after reboot it has been stuck @ 1+ logo, then it rebooted again (as always when it doesn't work) and i said "ok here we go again in the TWRP-loop" and INSTEAD it booted rom! Yes!
As the title says, i can't to seen successfully boot any android pie/android 10 based rom on max pro m1.
>bootloader already unofficially unlocked.
but during erasing process, i accidentally booted into recovery from where i booted into system , where encryption started again.
>so i booted back to twrp, format data then flashed decrypt.zip
> then flashed havoc 9.0 based rom, gapps then >wipe from twrp itself.
> rom boots fine after boot logo,but after welcome screen, google loading screen comes after which screen goes blank black and finally shutdowns after few minutes.
>tried force shutdown, multiple times, data wipe,format data,decrypt.zip after mountung vendor as well.
Still same issue, just after rom boot logo finished loading, the phone just goes blank black.
what should i do ? Asked many threads,telegram groups, nobody is replying /helping, everyone is just ignoring it.
Same problem here but goes off when connected to WiFi. Please reply If anyone got a fix for this
CHGR1999 said:
Same problem here but goes off when connected to WiFi. Please reply If anyone got a fix for this
Click to expand...
Click to collapse
my problem is solved by flashing stock pie which was twrp flashable .
akhil17kr said:
my problem is solved by flashing stock pie which was twrp flashable .
Click to expand...
Click to collapse
So you don't use havoc anymore? Or did you first flash stock, update to pie, then flash havoc? I'm stuck too... Won't let me flash havoc, need to get firmware 16 or something.
Try factory reset or wipe data
i got the same issue and still can't not flash any custom rom, the same thing happen to my phone when i flash any custom rom 8 9 or 10, i changed recovery already but it didn't work
Hi all
I experience kinda weird behaviour with my OP6T.
I wiped and upgraded to Android 10 a few days ago (10.3.1). I installed TWRP and immediatyl flashed Magisk using @mauronofrio all-in-one tool. I boot up, installed what I needed and all was going good.
By using the phone I noticed that in drawer there was 2 file manager app: one I think was from Google. So I downloaded an uninstaller and deleted it. After that I discovered that, without "File" (app name) I was unable to give folder access to Poweramp scan function (it was just saying the File app keep crashing).
I tried to install it again but nothing.
Now, the good stuff. Keep in mind root was working good. I also successfuly rebooted phone multiple time with no issues.
After I tried to install File app, I restarted my phone and, surprise, it keep stuck on bootloader warning screen for like 30 seconds and after it goes into recovery (TWRP).
I tried to flash recovery again together with Magisk but nothing. Same result (sometimes it wasn't even boot in TWRP but standard fastboot screen). In the end, I tried just flashing TWRP without Magisk and surprise: it booted. Without root of course.
I did some other tests, tried again (including trying to boot from slot B but that doesn't work and no decrypt message appear).
I don't understand what is going on.
What can I do further ? On Android 9 I experienced something like that but with a normal TWRP/Magisk flash it was returning all normal. It's strange because the advice from AIO says to flash TWRP and Magisk otherwise I brick the phone.
Recap:
Only TWRP installed on partiton A/B -> Phone boot with no root
TWRP (partion A/B) + Magisk (only partition A ?) -> Phone doesn't boot and go in recovery
Thanks
Maybe some modules? It's not a problem related to the tool, to the TWRP or Magisk, maybe you added some module that made the device crash at the start
mauronofrio said:
Maybe some modules? It's not a problem related to the tool, to the TWRP or Magisk, maybe you added some module that made the device crash at the start
Click to expand...
Click to collapse
Any way to see the installed modules from TWRP ? I also used Magisk Uninstaller but still nothing.
BTW, going to /data/adb/ I don't have any modules folder so I think nothing is installed.
rootgen said:
Any way to see the installed modules from TWRP ? I also used Magisk Uninstaller but still nothing.
BTW, going to /data/adb/ I don't have any modules folder so I think nothing is installed.
Click to expand...
Click to collapse
So maybe is something else
mauronofrio said:
So maybe is something else
Click to expand...
Click to collapse
Something or not, I think I will stick back to previous android version.
Just a question: why while flashing TWRP it says partion A/B are being patched while only A (or current boot) seems to correctly work (where by correctly work I mean asking for decrypt message is shown) ?
Any help is appreciated.
Thanks
rootgen said:
Something or not, I think I will stick back to previous android version.
Just a question: why while flashing TWRP it says partion A/B are being patched while only A (or current boot) seems to correctly work (where by correctly work I mean asking for decrypt message is shown) ?
Any help is appreciated.
Thanks
Click to expand...
Click to collapse
The installer patch both slots regardless of everything
Hmm, I might have missed it but after you flashed trwp to your phone did you reboot back to recovery then install root.. just asking..
Hello everybody.
Twice I tried to install LineageOS 18 on my 6T, equipped with latest OxygenOS/Android 11 version, without any success despite having followed several tutorials on Youtube and on websites.
Two days ago I unlocked the bootloader, I restarted the phone from the PC in Fastboot mode and I tried to install the TWRP recovery, always getting an error and when it seemed that I had succeeded the phone restarted showing the message "Qualcomm Crashdump" and the phone was dead.
Fortunately, a Wipe Data from the Recovery allowed me to get the 6T working again.
Last night I tried again by installing the LineageOS recovery first, I restarted the phone and I realized that it was in bootloop.
At this point I could only restart it in Recovery or Fastboot mode, without being able to start the 6T correctly; not even a wipe data helped me.
At that point I used the MSM download Tool, with which I was able to reinstall OxygenOS v9.xx and restart the 6T, then updating it to OxygenOS 11.
The drawback now is that when I turn on the phone it takes over a minute to boot (the two dots around the OnePlus symbol make a good 37 laps, after which the phone starts up and works perfectly).
How can I fix this slow boot problem?
And why has it become so difficult to install a custom ROM on the 6T? It occurs to me that OnePlus has deliberately complicated things to hinder modding.
dequadim said:
Hello everybody.
Twice I tried to install LineageOS 18 on my 6T, equipped with latest OxygenOS/Android 11 version, without any success despite having followed several tutorials on Youtube and on websites.
Two days ago I unlocked the bootloader, I restarted the phone from the PC in Fastboot mode and I tried to install the TWRP recovery, always getting an error and when it seemed that I had succeeded the phone restarted showing the message "Qualcomm Crashdump" and the phone was dead.
Fortunately, a Wipe Data from the Recovery allowed me to get the 6T working again.
Last night I tried again by installing the LineageOS recovery first, I restarted the phone and I realized that it was in bootloop.
At this point I could only restart it in Recovery or Fastboot mode, without being able to start the 6T correctly; not even a wipe data helped me.
At that point I used the MSM download Tool, with which I was able to reinstall OxygenOS v9.xx and restart the 6T, then updating it to OxygenOS 11.
The drawback now is that when I turn on the phone it takes over a minute to boot (the two dots around the OnePlus symbol make a good 37 laps, after which the phone starts up and works perfectly).
How can I fix this slow boot problem?
And why has it become so difficult to install a custom ROM on the 6T? It occurs to me that OnePlus has deliberately complicated things to hinder modding.
Click to expand...
Click to collapse
Did you get twrp installed? Wipe data by typing yes after flashing?
dequadim said:
Hello everybody.
Twice I tried to install LineageOS 18 on my 6T, equipped with latest OxygenOS/Android 11 version, without any success despite having followed several tutorials on Youtube and on websites.
Two days ago I unlocked the bootloader, I restarted the phone from the PC in Fastboot mode and I tried to install the TWRP recovery, always getting an error and when it seemed that I had succeeded the phone restarted showing the message "Qualcomm Crashdump" and the phone was dead.
Fortunately, a Wipe Data from the Recovery allowed me to get the 6T working again.
Last night I tried again by installing the LineageOS recovery first, I restarted the phone and I realized that it was in bootloop.
At this point I could only restart it in Recovery or Fastboot mode, without being able to start the 6T correctly; not even a wipe data helped me.
At that point I used the MSM download Tool, with which I was able to reinstall OxygenOS v9.xx and restart the 6T, then updating it to OxygenOS 11.
The drawback now is that when I turn on the phone it takes over a minute to boot (the two dots around the OnePlus symbol make a good 37 laps, after which the phone starts up and works perfectly).
How can I fix this slow boot problem?
And why has it become so difficult to install a custom ROM on the 6T? It occurs to me that OnePlus has deliberately complicated things to hinder modding.
Click to expand...
Click to collapse
You can follow this. If you want to install lineage os and want Google service make sure follow the "non gapp version" under installation method.
Havoc Flashing Notes for OnePlus 6 /6T from OOS 11 [Using TWRP Recovery]
1. Clean Flash : 2. Dirty Flash 3. Update oos base 1. Clean Flash : 🔊 Make sure you've backed up whatever data you want to keep to somewhere that's not on your phone; we're going to format the data partition and you're going to lose everything from internal storage. Basic requirements ○...
telegra.ph
Thanks for replies.
I must add this point: my 6T has OxygenOS v11.1.1.1; maybe this the reason of the problem? Maybe OnePlus did something that screws any modding attempt?
I simply followed the instructions found on YouTube, in the LineageOS' Fajita page and installed TWRP, but my 6T went in "Qualcomm Crashdump" and TWRP was not working → phone bricked.
Then I've tried installing, in the same way via ADB and Fastoot commands the Lineage Recovery, that has worked but when I tried to boot system, keeping OxygenOS, the phone went in bootloop.
So where is the error/fault?
Please, help me with a step-by-step tutorial that lead me to successfully install TWRP and LineageOS on my 6T.
dequadim said:
Thanks for replies.
I must add this point: my 6T has OxygenOS v11.1.1.1; maybe this the reason of the problem? Maybe OnePlus did something that screws any modding attempt?
I simply followed the instructions found on YouTube, in the LineageOS' Fajita page and installed TWRP, but my 6T went in "Qualcomm Crashdump" and TWRP was not working → phone bricked.
Then I've tried installing, in the same way via ADB and Fastoot commands the Lineage Recovery, that has worked but when I tried to boot system, keeping OxygenOS, the phone went in bootloop.
So where is the error/fault?
Please, help me with a step-by-step tutorial that lead me to successfully install TWRP and LineageOS on my
Click to expand...
Click to collapse
OnePlus definitely didn't do anything to make it harder. You need to fastboot boot twrp.img then flash the twrp installer zip. I'll attach both In next post. Reboot to recovery. Then install OOS, twrp installer, reboot to recovery. Install oos again, twrp installer again, reboot to recovery. Now install lineage, twrp installer, reboot to recovery. Install lineage again, twrp installer again, reboot to recovery. Factory reset and wipe data by typing yes. Boot to system
The img is for fastboot boot
The zip is for installing in twrp
Thanks for your reply.
I'm still wondering how to speed up the boot.
dequadim said:
Thanks for your reply.
I'm still wondering how to speed up the boot.
Click to expand...
Click to collapse
If everything is installed correctly it won't take long to boot
Brettroth said:
If everything is installed correctly it won't take long to boot
Click to expand...
Click to collapse
There is clearly something wrong, as my 6T's boot is slow.
Furthermore, the Recovery of the previous message is the one I downloaded three days ago and that made me go to the 6T in Qualcomm Crashdump.
I repeat my request: where can I find a safe and updated guide that explains how to install LineageOS without risk?
If you can't fastboot boot into that twrp on a11 without crash dumping there is something really wrong
If you can't fastboot boot into that twrp on a11 without crash dumping there is something really
dequadim said:
There is clearly something wrong, as my 6T's boot is slow.
Furthermore, the Recovery of the previous message is the one I downloaded three days ago and that made me go to the 6T in Qualcomm Crashdump.
I repeat my request: where can I find a safe and updated guide that explains how to install LineageOS without risk?
Click to expand...
Click to collapse
You sure you didn't try 3.6.0_9?
Clearing your cache might help with current boot. But once you install a new os everything will run smooth like it should
Thank you for the advice.
1) I've downloaded "twrp-3.6.0_9-0-fajita.img" and tried to install it several times, getting errors and then bricking my phone.
2) I have already cleared the cache several times from Recovery, without anything having changed; the two white dots on the boot screen continue to rotate 37 times around the red dot before the phone starts up and then works perfectly.
It occurred to me that the MSM Download Tool program uses a decrypted image of the original firmware; could this possibly be the cause of the long boot?
dequadim said:
Thank you for the advice.
1) I've downloaded "twrp-3.6.0_9-0-fajita.img" and tried to install it several times, getting errors and then bricking my phone.
2) I have already cleared the cache several times from Recovery, without anything having changed; the two white dots on the boot screen continue to rotate 37 times around the red dot before the phone starts up and then works perfectly.
It occurred to me that the MSM Download Tool program uses a decrypted image of the original firmware; could this possibly be the cause of the long boot?
Click to expand...
Click to collapse
That twrp version always will crash dump on a11. Use the one I sent
I followed these steps:
after having managed to make MSM Download Tool detect the phone in EDL mode, I proceeded by reinstalling OOS v9.0.13, after which I reconfigured the phone and restored the apps backup stored in my Google account.
Later, I don't remember the details well, I received the update notification for OOS v10 and later for OOs v11.1.2.2.
I don't remember exactly where the boot started to stretch, however this is more or less the process I followed to bring my 6T back to life.
Brettroth said:
That twrp version always will crash dump on a11. Use the one I sent
Click to expand...
Click to collapse
Are you sure that this TWRP will work without problems?
I've tried also with Lineage Recovery for Fajita, resulting with the 6T in bootloop :-(
dequadim said:
Are you sure that this TWRP will work without problems?
I've tried also with Lineage Recovery for Fajita, resulting with the 6T in bootloop :-(
Click to expand...
Click to collapse
I promise it works. I do t know what happened with your previous updating and msm tool but something sounds messed up. Just get twrp running and ease all your problems. Clean flashing and getting everything fresh
Brettroth said:
I promise it works. I do t know what happened with your previous updating and msm tool but something sounds messed up. Just get twrp running and ease all your problems. Clean flashing and getting everything fresh
Click to expand...
Click to collapse
Keep your finger crossed...
Another question: assuming I can install TWRP and make it working, LineageOS image must be copied in the 6T's internal SD and proceeding to install from TWRP?
dequadim said:
Another question: assuming I can install TWRP and make it working, LineageOS image must be copied in the 6T's internal SD and proceeding to install from TWRP?
Click to expand...
Click to collapse
Or you could use USB OTG. Or a PC and use adb sideload