Related
My phone is bootloader unlocked & rooted + TWRP but still using the original Nougat firmware from ZTE. Now, for some unexplained reason I cannot install any custom ROM that does NOT have Gapps incuded, like Resurrection Remix or similar slim ROMs without Gapps. TWRP just gives the usual can't install error.
Moreover, even if I install a ROm with Gapps successfully I cannot go past the 'Google verifying account' (have to wait for 24 hours) nonsense.
Any advise appreciated.
xectis said:
My phone is bootloader unlocked & rooted + TWRP but still using the original Nougat firmware from ZTE. Now, for some unexplained reason I cannot install any custom ROM that does NOT have Gapps incuded, like Resurrection Remix or similar slim ROMs without Gapps. TWRP just gives the usual can't install error.
Moreover, even if I install a ROm with Gapps successfully I cannot go past the 'Google verifying account' (have to wait for 24 hours) nonsense.
Any advise appreciated.
Click to expand...
Click to collapse
What's your TWRP version?
I guess you are installing the Universal Bootloader, right? Do you install a newer TWRP img after that?
Which are the ROMs that fail?
What's the failure error?
Have you ever formatted data? What's its filesystem?
Choose an username... said:
What's your TWRP version?
I guess you are installing the Universal Bootloader, right? Do you install a newer TWRP img after that?
Which are the ROMs that fail?
What's the failure error?
Have you ever formatted data? What's its filesystem?
Click to expand...
Click to collapse
Thanks for the response. I used Axon7 Toolkit for all actions, including boot unlocking (no idea which version Axon Toolkit installed). It also installed TWRP 3.1.1.0 alisa which I've had all the time.
The ROMs that failed were 'XenonHD-170609-Unofficial.zip' and 'Resurrection Remix' (RR-N-v5.8.5-20171108-axon7-Official.zip). Also I installed successfully 'A2017G(N-B06)_AROMA_SL!M2+DF!NR_by_raystef66.zip' which has Gapps included....but the problem was that I could not get past the google account verification, even though I know my google details. It says I had to wait 24 hours before signing in.
The failure error from XenonHD and Resurrection Remix ROMs was: Updater process ended with error: 7
Yes I formatted data each time I installed a ROM.
I don't know how to find out what the file system is.
xectis said:
Thanks for the response. I used Axon7 Toolkit for all actions, including boot unlocking (no idea which version Axon Toolkit installed). It also installed TWRP 3.1.1.0 alisa which I've had all the time.
The ROMs that failed were 'XenonHD-170609-Unofficial.zip' and 'Resurrection Remix' (RR-N-v5.8.5-20171108-axon7-Official.zip). Also I installed successfully 'A2017G(N-B06)_AROMA_SL!M2+DF!NR_by_raystef66.zip' which has Gapps included....but the problem was that I could not get past the google account verification, even though I know my google details. It says I had to wait 24 hours before signing in.
The failure error from XenonHD and Resurrection Remix ROMs was: Updater process ended with error: 7
Yes I formatted data each time I installed a ROM.
I don't know how to find out what the file system is.
Click to expand...
Click to collapse
I believe you forgot to flash the Universal Bootloader. That's an error on your end.
Basically, what the Universal Bootloader does is change your device's info to something 'universal' (it somewhat standardizes A2017s, A2017Us and A2017Gs into an intermediate so that you can flash any custom ROM on any of the 3). It also installs TWRP 3.0.2-N or sth like that. So basically you need to have TWRP-3.1.1-0.img on your phone, then flash the Universal Bootloader, then the modem for your device (get the latest from Raystef66's download center), then the ROM and whatever ZIPs you want to install (ALWAYS install SuperSU or Magisk or you'll get the internal storage encrypted and you'll have to format the internal storage every time you want to change ROM), and lastly Install Image - the TWRP.img - install to recovery partition.
You can get the Universal Bootloader from the LOS thread. There are also modem files for the 3 models but they are rather old, so just get the B09 modem from the download center
Choose an username... said:
I believe you forgot to flash the Universal Bootloader. That's an error on your end.
Basically, what the Universal Bootloader does is change your device's info to something 'universal' (it somewhat standardizes A2017s, A2017Us and A2017Gs into an intermediate so that you can flash any custom ROM on any of the 3). It also installs TWRP 3.0.2-N or sth like that. So basically you need to have TWRP-3.1.1-0.img on your phone, then flash the Universal Bootloader, then the modem for your device (get the latest from Raystef66's download center), then the ROM and whatever ZIPs you want to install (ALWAYS install SuperSU or Magisk or you'll get the internal storage encrypted and you'll have to format the internal storage every time you want to change ROM), and lastly Install Image - the TWRP.img - install to recovery partition.
You can get the Universal Bootloader from the LOS thread. There are also modem files for the 3 models but they are rather old, so just get the B09 modem from the download center
Click to expand...
Click to collapse
Thanks for your help and your suggestions. Will try a few things as I go along. Thanks again.
xectis said:
Thanks for your help and your suggestions. Will try a few things as I go along. Thanks again.
Click to expand...
Click to collapse
Just two things, you mentioned "and lastly Install Image - the TWRP.img - install to recovery partition". I already have TWRP 3.1.1.0 installed so did you mean to install it again after flashing the Universal Bootloader and modem?
Also, is this the correct link for the LOS thread you mentioned: https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547
xectis said:
Just two things, you mentioned "and lastly Install Image - the TWRP.img - install to recovery partition". I already have TWRP 3.1.1.0 installed so did you mean to install it again after flashing the Universal Bootloader and modem?
Also, is this the correct link for the LOS thread you mentioned: https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547
Click to expand...
Click to collapse
Yes and no
The Universal bootloader flashes an old TWRP version. After you reboot and enter the recovery again you will get an old TWRP. So to avoid this you have to flash the Universal Bootloader and then TWRP 3.1.1 or 3.2.1
That's the download center... I mean the LineageOS thread over at the ROMs section. By Unjustified Dev
Choose an username... said:
Yes and no
The Universal bootloader flashes an old TWRP version. After you reboot and enter the recovery again you will get an old TWRP. So to avoid this you have to flash the Universal Bootloader and then TWRP 3.1.1 or 3.2.1
That's the download center... I mean the LineageOS thread over at the ROMs section. By Unjustified Dev
Click to expand...
Click to collapse
I see. All clear now. You've been most helpful, thank you again.
[/QUOTE]
xectis said:
I see. All clear now. You've been most helpful, thank you again.
Click to expand...
Click to collapse
Hi again, almost everything worked as per your suggestions except installing ROMs without Gapps as mentioned previously such as Resurrection Remix. I get the dreaded 'To Start Android, Enter Password' notice (pic attached). Even after putting a random password it comes up with 'The password you entered is correct, but unfortunately your data is corrupt'. I did a factory reset but no joy. So it looks like I have to install Gapps also?. By the way my device is not encrypted.
On a different note, do you know of a link that has a mod for increasing the volume in the ear speaker so I can hear callers with a louder volume.
Hi again, almost everything worked as per your suggestions except installing ROMs without Gapps as mentioned previously such as Resurrection Remix. I get the dreaded 'To Start Android, Enter Password' notice (pic attached). Even after putting a random password it comes up with 'The password you entered is correct, but unfortunately your data is corrupt'. I did a factory reset but no joy. So it looks like I have to install Gapps also?. By the way my device is not encrypted.
On a different note, do you know of a link that has a mod for increasing the volume in the ear speaker so I can hear callers with a louder volume.[/QUOTE]
You have to format the internal storage, because it is encrypted. Do this:
You need to have Magisk 15.1 or 14 or SuperSU 2.79 ready. I recommend the latest Magisk. If you have an SD card, put it there. If not, leave it on your PC and have the phone connected.
Go to TWRP, Wipe, Advanced Wipe, Format data. Be sure that it formats as ext4 (it will say 'formating using make-ext4fs or something, if it says f2fs then leave it format and then use Change filesystem to ext4).
Right after that, install Magisk. If you have the SD card it's easy, if you don't, try to connect the phone to the PC, if it appears as a mass storage option then put it there and flash it with Install. If it doesn't appear as mass storage use adb sideload
NEVER leave the phone without SuperSU or Magisk! If you change the ROM, ALWAYS install Magisk or SuperSU right after you install the ROM. Otherwise you'll have to format the internal storage again the next time you change the ROM.
Choose an username... said:
Hi again, almost everything worked as per your suggestions except installing ROMs without Gapps as mentioned previously such as Resurrection Remix. I get the dreaded 'To Start Android, Enter Password' notice (pic attached). Even after putting a random password it comes up with 'The password you entered is correct, but unfortunately your data is corrupt'. I did a factory reset but no joy. So it looks like I have to install Gapps also?. By the way my device is not encrypted.
On a different note, do you know of a link that has a mod for increasing the volume in the ear speaker so I can hear callers with a louder volume.
Click to expand...
Click to collapse
You have to format the internal storage, because it is encrypted. Do this:
You need to have Magisk 15.1 or 14 or SuperSU 2.79 ready. I recommend the latest Magisk. If you have an SD card, put it there. If not, leave it on your PC and have the phone connected.
Go to TWRP, Wipe, Advanced Wipe, Format data. Be sure that it formats as ext4 (it will say 'formating using make-ext4fs or something, if it says f2fs then leave it format and then use Change filesystem to ext4).
Right after that, install Magisk. If you have the SD card it's easy, if you don't, try to connect the phone to the PC, if it appears as a mass storage option then put it there and flash it with Install. If it doesn't appear as mass storage use adb sideload
NEVER leave the phone without SuperSU or Magisk! If you change the ROM, ALWAYS install Magisk or SuperSU right after you install the ROM. Otherwise you'll have to format the internal storage again the next time you change the ROM.[/QUOTE]
I did everything you suggested but I still get the 'To start Android use your password'. No wories I'll go back to my old ROM. Thanks anyway.
***Update*** I made a mistake in formatting SYSTEM instead of DATA. Now it works fine installing the ROM's I mentioned. You are a champ!
Now all I need is to somehow find a way to raise the in-call volume (ear speaker).
xectis said:
Now all I need is to somehow find a way to raise the in-call volume (ear speaker).
Click to expand...
Click to collapse
Try this
https://forum.xda-developers.com/axon-7/how-to/patch-enable-ak4490-hifi-dac-custom-rom-t3707738
It'll probably not work but you'll end up with the AK4490 anyways
Choose an username... said:
Try this
https://forum.xda-developers.com/axon-7/how-to/patch-enable-ak4490-hifi-dac-custom-rom-t3707738
It'll probably not work but you'll end up with the AK4490 anyways
Click to expand...
Click to collapse
Thanks for the link, however I recently discovered that with the 'XenonHD-170609-Unofficial' ROM the in-call volume is pretty loud as well as the sound from the normal sounding speakers. It also has just about everything I'd want in a lite ROM. So far it's the ROM I'll keep.
xectis said:
Thanks for the link, however I recently discovered that with the 'XenonHD-170609-Unofficial' ROM the in-call volume is pretty loud as well as the sound from the normal sounding speakers. It also has just about everything I'd want in a lite ROM. So far it's the ROM I'll keep.
Click to expand...
Click to collapse
Use the zip anyways
Choose an username... said:
Use the zip anyways
Click to expand...
Click to collapse
Ok I'll give it a try.
Dear XDA,
I screwed up... I think my device is now soft bricked.... :crying:
It all started good on a sunny saturday. I thought this was a good day to try another custom rom. Namely Codename Phoenix.
My device was already rooted so i started with upgrading my TWRP to the latest Blu_Spark TWRP 3.2.1. After flashing the recovery i continued with the ROM. It all went downhill from there....
The install finished and i booted my device. Knowing this could take a while i got into the shower thinking it would finish when i got back. But when i got back it was still booting. Knowing the first boot can take a while so I let it be. After an hour or so it was still stuck on the google logo and the weather and my mood changed for the worse.
I figured something in the process went wrong and tried to boot into recovery. That worked so I thought 'Cool, let's fix it there'. But the recovery was encrypted so i couldn't get to my data. Normally you put in your pincode and it decrypts your phone. This was not the case.... I couldn't put in my pincode so decrypting was out of the question.
Luckily ADB was still working so I downloaded the original Oxygen OS rom and tried to side-load it... This got stuck on 47% for no reason at all. Phone had 100% battery and didn't time-out..
I was really confused, but I let the device do it's thing and maybe things would work out... I was wrong. Everything was worse. Because i tried installing the original firmware it removed the custom recovery....
So now i have a device with no OS and I can't get into recovery. Luckily there is a unbrick tool for OnePlus 5. Following those steps i got stuck on the part that it does not show in my device-manager.
Currently i'm really grumpy and have no idea how to fix this.
I humbly ask for advice. Is this solvable or do i have a wasted OnePlus 5?
Thanks in advance,
Lennard
can you reboot to bootloader?
if yes, you can flash original or custom recovery...
---------- Post added at 09:39 AM ---------- Previous post was at 09:38 AM ----------
[/COLOR]
len.asdf said:
Dear XDA,
I screwed up... I think my device is now soft bricked.... :crying:
It all started good on a sunny saturday. I thought this was a good day to try another custom rom. Namely Codename Phoenix.
My device was already rooted so i started with upgrading my TWRP to the latest Blu_Spark TWRP 3.2.1. After flashing the recovery i continued with the ROM. It all went downhill from there....
The install finished and i booted my device. Knowing this could take a while i got into the shower thinking it would finish when i got back. But when i got back it was still booting. Knowing the first boot can take a while so I let it be. After an hour or so it was still stuck on the google logo and the weather and my mood changed for the worse.
I figured something in the process went wrong and tried to boot into recovery. That worked so I thought 'Cool, let's fix it there'. But the recovery was encrypted so i couldn't get to my data. Normally you put in your pincode and it decrypts your phone. This was not the case.... I couldn't put in my pincode so decrypting was out of the question.
Luckily ADB was still working so I downloaded the original Oxygen OS rom and tried to side-load it... This got stuck on 47% for no reason at all. Phone had 100% battery and didn't time-out..
I was really confused, but I let the device do it's thing and maybe things would work out... I was wrong. Everything was worse. Because i tried installing the original firmware it removed the custom recovery....
So now i have a device with no OS and I can't get into recovery. Luckily there is a unbrick tool for OnePlus 5. Following those steps i got stuck on the part that it does not show in my device-manager.
Currently i'm really grumpy and have no idea how to fix this.
I humbly ask for advice. Is this solvable or do i have a wasted OnePlus 5?
Thanks in advance,
Lennard
Click to expand...
Click to collapse
Don't worry! Your device is safe. At most, you'll be required to wipe your data.
Try using the official twrp recovery here:
https://twrp.me/oneplus/oneplus5.html
If this doesn't work, let me know.
canteo said:
can you reboot to bootloader?
if yes, you can flash original or custom recovery...
Click to expand...
Click to collapse
I can go into fastboot and managed to install TWRP with the comment below!
Zohair.ul.hasan said:
---------- Post added at 09:39 AM ---------- Previous post was at 09:38 AM ----------
[/COLOR]
Don't worry! Your device is safe. At most, you'll be required to wipe your data.
Try using the official twrp recovery here:
https://twrp.me/oneplus/oneplus5.html
If this doesn't work, let me know.
Click to expand...
Click to collapse
Thanks for these words! That's a big relieve
With your link I managed to install TWRP through fastboot. So now i have a custom recovery. The current problem is that my data is encrypted and I cannot decrypt it. There is no option to fill in a password since there is no OS that requires a password. So it's sort of a neverending cycle . Although fastboot, recovery and sideload should work now.
The thing is, previously I tried installing the original firmware and that failed at 47%. So i'm not sure what to do now.
I tried installing 'codeworkx universal twrp 3.2.1-0 recovery' since he seems to have fixed the encrypt issue. But when I tried sideloading the file it says "Zip file is corrupt!". So no succes there yet.
To be precise, this is the threat for Codeworkx Universal TWRP : https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
And i downloaded and tried installing: twrp-3.2.1-0-universal-codeworkx-cheeseburger.img
I was thinking about downloading the latest Codename Phoenix ROM, but when I try to download the latest release the file is name "Codename-Phoenix-NOS-8.1-oneplus5t-20180303.zip". That implies it's only for the 5t and not for the 5. So that could be my original problem? That i downloaded the wrong ROM?
That aside.
Should I try to get the download link for CNP and download the latest release for the OP5 and install that.
Or
Should i try to install the original firmware. Reset everything and start over from the beginning (unlocking, rooting, etc..)
Thanks again for all the help
len.asdf said:
I can go into fastboot and managed to install TWRP with the comment below!
Thanks for these words! That's a big relieve
With your link I managed to install TWRP through fastboot. So now i have a custom recovery. The current problem is that my data is encrypted and I cannot decrypt it. There is no option to fill in a password since there is no OS that requires a password. So it's sort of a neverending cycle . Although fastboot, recovery and sideload should work now.
The thing is, previously I tried installing the original firmware and that failed at 47%. So i'm not sure what to do now.
I tried installing 'codeworkx universal twrp 3.2.1-0 recovery' since he seems to have fixed the encrypt issue. But when I tried sideloading the file it says "Zip file is corrupt!". So no succes there yet.
To be precise, this is the threat for Codeworkx Universal TWRP : https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
And i downloaded and tried installing: twrp-3.2.1-0-universal-codeworkx-cheeseburger.img
I was thinking about downloading the latest Codename Phoenix ROM, but when I try to download the latest release the file is name "Codename-Phoenix-NOS-8.1-oneplus5t-20180303.zip". That implies it's only for the 5t and not for the 5. So that could be my original problem? That i downloaded the wrong ROM?
That aside.
Should I try to get the download link for CNP and download the latest release for the OP5 and install that.
Or
Should i try to install the original firmware. Reset everything and start over from the beginning (unlocking, rooting, etc..)
Thanks again for all the help
Click to expand...
Click to collapse
Nice to hear that!
To be clear, does the TWRP decrypt you data? When you click install in TWRP, is it a bunch of randomly named files?
I think you should go ahead with installing CNP, you shouldn't have any problems with it now that you've got the correct version.
Good luck!
Zohair.ul.hasan said:
Nice to hear that!
To be clear, does the TWRP decrypt you data? When you click install in TWRP, is it a bunch of randomly named files?
I think you should go ahead with installing CNP, you shouldn't have any problems with it now that you've got the correct version.
Good luck!
Click to expand...
Click to collapse
Yeah it's a bunch of random file names. Like "2TAjnCI8CpHDL38Oh684DuTSgaO".
Alright, i'll let you know if I succeed. Thanks for the help
len.asdf said:
Yeah it's a bunch of random file names. Like "2TAjnCI8CpHDL38Oh684DuTSgaO".
Alright, i'll let you know if I succeed. Thanks for the help
Click to expand...
Click to collapse
Wait! Staying encrypted is a bunch of trouble. I recommend u to follow these steps:
Go to recovery
Select wipe
Select advanced wipe
Clear dalvik and cache
Go back
Select wipe
Click "Format Data"
Type in yes
Go back
Select wipe
Swipe to factory reset
Reboot recovery
Transfer the ROM from PC to phone
Install it
Zohair.ul.hasan said:
Wait! Staying encrypted is a bunch of trouble. I recommend u to follow these steps:
Go to recovery
Select wipe
Select advanced wipe
Clear dalvik and cache
Go back
Select wipe
Click "Format Data"
Type in yes
Go back
Select wipe
Swipe to factory reset
Reboot recovery
Transfer the ROM from PC to phone
Install it
Click to expand...
Click to collapse
Haha thanks! Just in time. Was still downloading the latest CNP .
Whew! Update me after flashing.
Zohair.ul.hasan said:
Whew! Update me after flashing.
Click to expand...
Click to collapse
Hmm, the installation should be a succes. But when i tried to reboot and start up the OS / System it just reboots into TWRP.... ? It's sort of boot looping into recovery.
I tried installing a couple of times with and without wiping dalvik/cache/system.
Could the install file not be complete?
On a side note, my data is not encrypted
len.asdf said:
Hmm, the installation should be a succes. But when i tried to reboot and start up the OS / System it just reboots into TWRP.... ? It's sort of boot looping into recovery.
I tried installing a couple of times with and without wiping dalvik/cache/system.
Could the install file not be complete?
On a side note, my data is not encrypted
Click to expand...
Click to collapse
Did you factory reset by going into wipe>swipe to factory reset?
If not then do that and flash it
Zohair.ul.hasan said:
Did you factory reset by going into wipe>swipe to factory reset?
If not then do that and flash it
Click to expand...
Click to collapse
YES! It work. Many thanks
len.asdf said:
YES! It work. Many thanks
Click to expand...
Click to collapse
Congrats! Please like my replies if you don't mind
Zohair.ul.hasan said:
Congrats! Please like my replies if you don't mind
Click to expand...
Click to collapse
But of course! Already did that. But i'm not sure if it shows or not. Tried clicking multiple times on the thanks button but it doesn't highlight. It should do that right?
len.asdf said:
But of course! Already did that. But i'm not sure if it shows or not. Tried clicking multiple times on the thanks button but it doesn't highlight. It should do that right?
Click to expand...
Click to collapse
Yes it should but that's okay
Zohair.ul.hasan said:
Yes it should but that's okay
Click to expand...
Click to collapse
installed the xda app and there I could give you a 'thanks'
Hello, I have an OP 5 with unlocked bootloader and i was rooted. So, I'm in 4.5.13, and i'm trying to install 5.1.5 but i need to be unrooted for this.
Somehow when i removed root (magisk) my phone entered in bootloop mode (i think that magisk lost the original boot img). I flashed the stock boot img and the phone booted normally and without root. However i think that some "crumbs" of the magisk or adway stayed in my system or phone partitions and my phone continues to say that he can´t install the OTA. I've already wiped cache and data in the recovery and tried to install with adb sideload but it fails.
I still have my OOS and is working fine, but I can't update... Any ideas?
Do you think that if I do the normal settings > restore factory settings will it work? Or that option will be also damaged?
Should i boot TWRP in fastboot, and try to do a factory reset and then flash 5.1.5?
For your information, i've never flashed anything besides magisk and the attempts to update. The rom is the original as also the recovery. To flash the magisk i always booted twrp connected by usb to my PC.
I apreciate all the help!!
pdalvares said:
I apreciate all the help!!
Click to expand...
Click to collapse
https://downloads.oneplus.com/oneplus-5/oneplus_5_oxygenos_5.1.5/
This is the full OOS ROM Zip with instructions to flash with either stock Recovery, or TWRP.
Dirk said:
This is the full OOS ROM Zip with instructions to flash with either stock Recovery, or TWRP.
Click to expand...
Click to collapse
Yo, i already tried it different ways, but thank you :/
pdalvares said:
Yo, i already tried it different ways, but thank you :/
Click to expand...
Click to collapse
Fastboot flash TWRP, format partitions and flash full OOS ROM and Magisk. What's the difficulty?
https://www.xda-developers.com/how-to-install-twrp/
Dirk said:
Fastboot flash TWRP, format partitions and flash full OOS ROM and Magisk. What's the difficulty?
https://www.xda-developers.com/how-to-install-twrp/
Click to expand...
Click to collapse
Ok i'm gonna try it i'm sorry for my noobish but you know the smartphone was expensive and i'm afraid to brick it someway :/
Just one question: when you say formating partitions you mean wipe data, cache, system and dalvik / ART cache right?
thanks alot for your help and im sorry for being noob xD
I've my nexus 7 with root and PureNexus rom and had an moto g with custom rom, twrp and root but somehow I'm afraid with the OP5 because it was very expensive to my pocket xD :silly:
pdalvares said:
Ok i'm gonna try it i'm sorry for my noobish but you know the smartphone was expensive and i'm afraid to brick it someway :/
Just one question: when you say formating partitions you mean wipe data, cache, system and dalvik / ART cache right?
thanks alot for your help and im sorry for being noob xD
I've my nexus 7 with root and PureNexus rom and had an moto g with custom rom, twrp and root but somehow I'm afraid with the OP5 because it was very expensive to my pocket xD :silly:
Click to expand...
Click to collapse
Even if you tried really hard it would be almost impossible to 'Brick' a Oneplus phone. We even have unbrick tools to revive dead devices. Oneplus phones are like zombies. Really hard to keep down. The price we usually pay for messing up is nothing more than having to do a clean install and having to set the phone up again. We've all been there!
Once you have TWRP installed you could try a simple swipe-to-wipe from the 'Wipe' menu in TWRP and then flash the full OOS ROM & Magisk. I would recommend going into the 'Advanced' sub menu from 'Wipe' and select every partition. This will erase your Internal Storage, so make sure you have a backup of everything on your PC. Once you've done this you should use the TWRP 'Reboot' menu to reboot back into Recovery. Copy the ROM and Magisk zips back to Internal Storage from PC and Install them from TWRP 'Install' menu.
Dirk said:
Even if you tried really hard it would be almost impossible to 'Brick' a Oneplus phone. We even have unbrick tools to revive dead devices. Oneplus phones are like zombies. Really hard to keep down. The price we usually pay for messing up is nothing more than having to do a clean install and having to set the phone up again. We've all been there!
Once you have TWRP installed you could try a simple swipe-to-wipe from the 'Wipe' menu in TWRP and then flash the full OOS ROM & Magisk. I would recommend going into the 'Advanced' sub menu from 'Wipe' and select every partition. This will erase your Internal Storage, so make sure you have a backup of everything on your PC. Once you've done this you should use the TWRP 'Reboot' menu to reboot back into Recovery. Copy the ROM and Magisk zips back to Internal Storage from PC and Install them from TWRP 'Install' menu.
Click to expand...
Click to collapse
I've made what you said but it gives me the error "Updater process ended with error: 7"
pdalvares said:
I've made what you said but it gives me the error "Updater process ended with error: 7"
Click to expand...
Click to collapse
Which TWRP are you using? It should be the latest Official version, or you could try the latest codeworkx from here:
https://sourceforge.net/projects/cheeseburgerdumplings/files/15.1/cheeseburger/recovery/
Error 7 is a generic error code. The useful information about the error is usually in the body of text.
If you can't get TWRP to play nicely you can use it to format partitions as mentioned before, and then use it to install the stock OOS recovery from the bottom of this page:
https://downloads.oneplus.com/oneplus-5/oneplus_5_oxygenos_5.1.5/
The stock recovery is an .img, so in the TWRP 'Install' menu you need to select Image instead of Zip at the bottom of the screen. Move the stock recovery .img to Internal Storage and flash it. Reboot into Stock Recovery and flash full OOS zip.
Dirk said:
Even if you tried really hard it would be almost impossible to 'Brick' a Oneplus phone. We even have unbrick tools to revive dead devices. Oneplus phones are like zombies. Really hard to keep down. The price we usually pay for messing up is nothing more than having to do a clean install and having to set the phone up again. We've all been there!
Once you have TWRP installed you could try a simple swipe-to-wipe from the 'Wipe' menu in TWRP and then flash the full OOS ROM & Magisk. I would recommend going into the 'Advanced' sub menu from 'Wipe' and select every partition. This will erase your Internal Storage, so make sure you have a backup of everything on your PC. Once you've done this you should use the TWRP 'Reboot' menu to reboot back into Recovery. Copy the ROM and Magisk zips back to Internal Storage from PC and Install them from TWRP 'Install' menu.
Click to expand...
Click to collapse
YO BRO i've made it. I installed other version of the OS and it's working! Now im gonna see if i can update it to the newest version
Thank you for encouraging me!
pdalvares said:
YO BRO i've made it. I installed other version of the OS and it's working! Now im gonna see if i can update it to the newest version
Thank you for encouraging me!
Click to expand...
Click to collapse
Let me know how you get on. :good:
Dirk said:
Let me know how you get on. :good:
Click to expand...
Click to collapse
It all works fine but when doing the OTA in the OOS to 5.1.4 the device reboots, enters in oxygenos recovery but it fails...
EDIT:
Could it be because the bootloader is unlocked?? Is it safe to lock it like i unlocked it? No problem?
pdalvares said:
It all works fine but when doing the OTA in the OOS to 5.1.4 the device reboots, enters in oxygenos recovery but it fails...
Click to expand...
Click to collapse
Work through the steps in post #8. Begin with the latest codeworkx TWRP and go from there.
Check this guide if you think you might be missing something:
https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877
Dirk said:
Work through the steps in post #8. Begin with the latest codeworkx TWRP and go from there.
Check this guide if you think you might be missing something:
https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877
Click to expand...
Click to collapse
It failed that way
ok so im gonna write here what it says:
" Installing zip file...
Checking for Digest file...
Skipping Digest check: no Digest file found vendor partition is not existed, exit ota!!
Updater process ended with ERROR: 7
error installiong...
Updating partition details...
Failed to mount '/vendor' (Invalid argument)
...done "
pdalvares said:
It failed that way
ok so im gonna write here what it says:
" Installing zip file...
Checking for Digest file...
Skipping Digest check: no Digest file found vendor partition is not existed, exit ota!!
Updater process ended with ERROR: 7
error installiong...
Updating partition details...
Failed to mount '/vendor' (Invalid argument)
...done "
Click to expand...
Click to collapse
Are you trying to OTA or full ROM? OTA is not going to work. Only full ROM .zip will get the job done.
Have you considered giving up on OOS for now and just try flashing a Custom ROM from TWRP? I'd recommend Dirty Unicorns Oreo for now until Pie ROMs mature. You can get their ROM from their website.. Should be no issue at all flashing it. Opengapps ARM64, 8.1 Nano is the Gapps i'd recommend.
Wipe in TWRP, Flash Firmware/ROM/Gapps/Magisk. Job done.
pdalvares said:
It failed that way
ok so im gonna write here what it says:
" Installing zip file...
Checking for Digest file...
Skipping Digest check: no Digest file found vendor partition is not existed, exit ota!!
Updater process ended with ERROR: 7
error installiong...
Updating partition details...
Failed to mount '/vendor' (Invalid argument)
...done "
Click to expand...
Click to collapse
One more thing dude, i've flashed the 5.1.1 on top of the 4.5.14 without wiping, and it is taking along time to boot. I should wipe it? :/
pdalvares said:
One more thing dude, i've flashed the 5.1.1 on top of the 4.5.14 without wiping, and it is taking along time to boot. I should wipe it? :/
Click to expand...
Click to collapse
Initial boot can take some time.
I'm at a loss why your phone hates OOS, but it might love Custom ROMs. Give it some thought.
pdalvares said:
One more thing dude, i've flashed the 5.1.1 on top of the 4.5.14 without wiping, and it is taking along time to boot. I should wipe it? :/
Click to expand...
Click to collapse
MY BROTHER, i really needed to lock the bootloader, wiped everything and adb sideloaded 5.1.1. It booted at android 8 and then i ran the OTA's until the newest one and now i have my phone fully functional, with the latest update, and running all stock. Thank's alot for all the help. I don´t know how to thank you! Peace and see you one day!
EDIT:
Maybe one day I will try some custom ROM, like lineage or other best than that. For now im gonna stay like this for a while, just because yes
pdalvares said:
MY BROTHER, i really needed to lock the bootloader, wiped everything and adb sideloaded 5.1.1. It booted at android 8 and then i ran the OTA's until the newest one and now i have my phone fully functional, with the latest update, and running all stock. Thank's alot for all the help. I don´t know how to thank you! Peace and see you one day!
EDIT:
Maybe one day I will try some custom ROM, like lineage or other best than that. For now im gonna stay like this for a while, just because yes
Click to expand...
Click to collapse
Good news! :good:
You can see how resilient OP phones are. You can pretty much always get them back to a working condition. I can only guess but it sounds like you were right. Something was wrong with your Bootloader after the initial problems. Glad you got it sorted.
I'm using the tutorial on the LineageOS wiki for the Us996. I've unlocked the bootloader via official means from LG, but when it comes time to send the recovery via fastboot, it successfully sends and writes it, it even let's me boot into it, after pulling the battery, and using the correct button commands. But if I restart and try to enter again I'm greeted by the official erase everything recovery.
Does anyone know what I'm doing wrong? Do I need to flash root to get the recovery to stick?
Take a look at this video. If you have TWRP installed right, and are going to it through a battery pull and the power button volume down combination, then the screen that comes up looks scary and looks like you'll "format" your phone, but as you see in this video, you don't.
baldybill said:
Take a look at this video. If you have TWRP installed right, and are going to it through a battery pull and the power button volume down combination, then the screen that comes up looks scary and looks like you'll "format" your phone, but as you see in this video, you don't.
https://www.youtube.com/watch?v=https://www.youtube.com/watch?v=tDq0qMbgjL4
Click to expand...
Click to collapse
See I've gotten into TWRP, then I reboot system(actual Android not just restarting recovery).the problem is When I power off my phone and tried to get back into TWRP, I clicked yes and yes and it proceeded to wipe my phone. TWRP wasn't there just factory reset lol
lowsnamebrand said:
See I've gotten into TWRP, then I reboot system(actual Android not just restarting recovery).the problem is When I power off my phone and tried to get back into TWRP, I clicked yes and yes and it proceeded to wipe my phone. TWRP wasn't there just factory reset lol
Click to expand...
Click to collapse
Not sure why it isnt happening automatically (it usually does when flashing things like magisk to root) but when you get into twrp or with root rename /system/recovery-from-boot.p to /system/recovery-from-boot.bak. If in twrp first go into the mount page and uncheck the box at the bottom that says something about system read only first, then you can use the file manager.
Or since it sounds like you want to flash lineage, just flash the lineageos zip (and then optionally opengapps and root). Be sure to format data too (wipe->format data->yes). Then if you dont have lineage on an sdcard ready to go you could reboot recovery so that the formatted data is ready then connect to pc and send the zips over by using adb push C:\path\to\lineage.zip /sdcard/
Phoenix591 said:
Not sure why it isnt happening automatically (it usually does when flashing things like magisk to root) but when you get into twrp or with root rename /system/recovery-from-boot.p to /system/recovery-from-boot.bak. If in twrp first go into the mount page and uncheck the box at the bottom that says something about system read only first, then you can use the file manager.
Or since it sounds like you want to flash lineage, just flash the lineageos zip (and then optionally opengapps and root). Be sure to format data too (wipe->format data->yes). Then if you dont have lineage on an sdcard ready to go you could reboot recovery so that the formatted data is ready then connect to pc and send the zips over by using adb push C:\path\to\lineage.zip /sdcard/
Click to expand...
Click to collapse
What I'm thinking about doing is flashing TWRP again, on first boot(of TWRP) backing up my current rom(stock) and trying to boot into recovery again, because if it doesn't stick again, it'll wipe but at least I'll have a backup.
I've noticed a lot of different root files which would you recommend?
lowsnamebrand said:
What I'm thinking about doing is flashing TWRP again, on first boot(of TWRP) backing up my current rom(stock) and trying to boot into recovery again, because if it doesn't stick again, it'll wipe but at least I'll have a backup.
I've noticed a lot of different root files which would you recommend?
Click to expand...
Click to collapse
Sorry for the double post but does the "LG factory reset" stay even after having TWRP installed? Like will I always have to answer yes twice to enter TWRP?
lowsnamebrand said:
Sorry for the double post but does the "LG factory reset" stay even after having TWRP installed? Like will I always have to answer yes twice to enter TWRP?
Click to expand...
Click to collapse
Yes thats always the same.
If you don't flash lineage or something to root stock (I reccommend magisk since the alternative, Supersu, is owned by some Chinese company, and magisk has various modules that do many things) and don't rename /system/recovery-from-boot.p manually (theres a file manager under advanced in twrp) the stock rom will use that file to reflash stock recovery any time it boots.
Phoenix591 said:
Yes thats always the same.
If you don't flash lineage or something to root stock (I reccommend magisk since the alternative, Supersu, is owned by some Chinese company, and magisk has various modules that do many things) and don't rename /system/recovery-from-boot.p manually (theres a file manager under advanced in twrp) the stock rom will use that file to reflash stock recovery any time it boots.
Click to expand...
Click to collapse
Awesome I think my issue is not renaming that file and the stock rom reinstalling stock recovery. I've used SuperSU, never used magisk, is there a stickied release thread for it?
lowsnamebrand said:
Awesome I think my issue is not renaming that file and the stock rom reinstalling stock recovery. I've used SuperSU, never used magisk, is there a stickied release thread for it?
Click to expand...
Click to collapse
Its got more than a thread, has a whole section. Anyway heres the main release thread
Phoenix591 said:
Its got more than a thread, has a whole section. Anyway heres the main release thread
Click to expand...
Click to collapse
You've been a huge help, thank you! I'll report back later tonight, when I can actually work on my phone
So i was able to obtain root aswell as installed twrp, the only issue I had was every rom I tried refused to boot. They just hung at the loading screen, that includes the back up I'd made of stock, is there something I missed?
lowsnamebrand said:
So i was able to obtain root aswell as installed twrp, the only issue I had was every rom I tried refused to boot. They just hung at the loading screen, that includes the back up I'd made of stock, is there something I missed?
Click to expand...
Click to collapse
If you mean the boot animation, the very first time can take a good while, like 20 minutes. Also make sure you've formatted /data if you havnt yet especially going to lineage.
Phoenix591 said:
If you mean the boot animation, the very first time can take a good while, like 20 minutes. Also make sure you've formatted /data if you havnt yet especially going to lineage.
Click to expand...
Click to collapse
Sorry for the late reply, yeah I think I just let the boot animation go for around 5, I'm gonna have to try reflashing it and hoping for the best, I'll be sure to answer back when I get a chance
OK, I know this is an old thread - but I just got a replacement US996 phone; my old standby has a charger plug problem so I decided to get another one and put a rooted stock Oreo ROM on it. However, I'm having the same issue as the OP. Get into fastboot, flash TWRP (I have the 3.3.1-0 version, as the newer 3.3.1-1 version does not have any download mirrors). The flash appears to go just fine, it says the write was completed. However, when I reboot into adb mode and do "adb reboot recovery" I get "no command" and the little droid with his belly hatch open. So obviously TWRP wasn't flashed. The OP says he eventually was able to get it to work and install root. How did you fix the issue?
Do I still need to do the old recowvery shenanigans that we had to do back when the phone first came out?
Thanks!
I believe you MUST use the button combo to reboot into twrp.
See here:
https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239/post78513963
pistacios said:
I believe you MUST use the button combo to reboot into twrp.
See here:
https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239/post78513963
Click to expand...
Click to collapse
I've done that. The problem is that TWRP hasn't actually been installed via fastboot flash recovery - it goes through the motions, SAYS it's been installed, but when I do the button combo, it actually does reset my phone rather than booting into TWRP.
---------- Post added at 09:36 AM ---------- Previous post was at 08:55 AM ----------
Disregard the above. Flashed it again (4th time), and it finally took.
The same happened with my wife's US996 now that you mention it. Took a few tries and was a bit frustrating.
When I flashed TWRP on mine it was a "one and done".
Glad you got it sorted.
Thanks - all good. Rooted stock Oreo ROM installed, working great.
so, my phone was MIUI 10 , i decided to go 11, so i downloaded and installed via recovery.
thing is, when i rebooted and tried to flash magisk the recovery - TWRP - asked for a password, which i didn't put..
why is that?
is any ROM installation does that? is it the recovery's fault?
U read this?
https://forum.xda-developers.com/re...ngefox-recovery-project-t3941822/post79771468
joke19 said:
U read this?
https://forum.xda-developers.com/re...ngefox-recovery-project-t3941822/post79771468
Click to expand...
Click to collapse
i guess you meant for this?
11. If you experience a situation where you have set a PIN, but the recovery asks for a password (or vice versa, etc), then you must ask your ROM devs to fix their ROM by applying this patch. This is not a recovery issue, so please do not ask us to "fix" it. Alternatively, you can always open a terminal in the recovery (or via "adb shell") and run "twrp decrypt password".
1. thank you.
2. i dont have orangeFox though i guess it's the same
arik100 said:
i guess you meant for this?
11. If you experience a situation where you have set a PIN, but the recovery asks for a password (or vice versa, etc), then you must ask your ROM devs to fix their ROM by applying this patch. This is not a recovery issue, so please do not ask us to "fix" it. Alternatively, you can always open a terminal in the recovery (or via "adb shell") and run "twrp decrypt password".
1. thank you.
2. i dont have orangeFox though i guess it's the same
Click to expand...
Click to collapse
No, I am sure he was referring to points #6, #7, and #8.
i was at stock rooted miui, with custom recovery.
just flashed the eu miui via recovery , of course i did format data and got to this state.
now i just did format data, and instead of installing rom rebooting and then root, i did install rom and root in the same session.
probably if i enter the recovery it will still give me the encrypt message? dunno, maybe because i didn't re-install the recovery..
arik100 said:
i was at stock rooted miui, with custom recovery.
just flashed the eu miui via recovery , of course i did format data and got to this state.
now i just did format data, and instead of installing rom rebooting and then root, i did install rom and root in the same session.
probably if i enter the recovery it will still give me the encrypt message? dunno, maybe because i didn't re-install the recovery..
Click to expand...
Click to collapse
Same happened with me. Whatever you do your recovery is not gonna decrypt, i tried everything that i can found but nothing worked.
This is only when you flash 10.0 roms no 9.0 rom is gonna cause problem, still searching for a fix. Dont even know what causing this, maybe because it is indian variant or i dont know. Anybody....???
Same issue with an Android 10 Rom.
mr.badman said:
Same happened with me. Whatever you do your recovery is not gonna decrypt...
Click to expand...
Click to collapse
Really! Which OrangeFox version did you try, which did not decrypt?
---------- Post added at 10:38 AM ---------- Previous post was at 10:37 AM ----------
Roster42 said:
Same issue with an Android 10 Rom.
Click to expand...
Click to collapse
Did you use OrangeFox recovery?
DarthJabba9 said:
Really! Which OrangeFox version did you try, which did not decrypt?
---------- Post added at 10:38 AM ---------- Previous post was at 10:37 AM ----------
Did you use OrangeFox recovery?
Click to expand...
Click to collapse
i used TWRP
why?
arik100 said:
i used TWRP
why?
Click to expand...
Click to collapse
Because OrangeFox recovery can decrypt quite fine.
DarthJabba9 said:
Really! Which OrangeFox version did you try, which did not decrypt?
---------- Post added at 10:38 AM ---------- Previous post was at 10:37 AM ----------
Did you use OrangeFox recovery?
Click to expand...
Click to collapse
I have tried everything, si yes I have tried with orangeFox
Roster42 said:
I have tried everything, si yes I have tried with orangeFox
Click to expand...
Click to collapse
I should like to see the OrangeFox logs (they will be in the /sdcard/Fox/logs/ folder), because I am yet to see a single situation where OrangeFox cannot decrypt (especially if you formatted data).
Thank you for your answer. I will provide this tonight sir.
The thing is, if I format /data of course I can use my internal storage, but if I re flash the ROM, it will encrypt again. It's like a loop.
I heard it's an issue with android 10, recovery don't know how to manage it.
Roster42 said:
Thank you for your answer. I will provide this tonight sir.
The thing is, if I format /data of course I can use my internal storage, but if I re flash the ROM, it will encrypt again. It's like a loop.
I heard it's an issue with android 10, recovery don't know how to manage it.
Click to expand...
Click to collapse
Yes, the ROM will encrypt again, unless you disable forced-encryption before flashing it (there is a setting in OrangeFox for that). However, lavender has serious issues if it is not encrypted (pin/password/fingerprint will not work). So I do not recommend disabling forced-encryption.
The point is that OrangeFox will automatically decrypt when you boot it up, so that the recovery has full access to internal storage and the data partition. Since 99.9% of lavender devices are encrypted, there is absolutely no problem running OrangeFox on them. This is the best you can hope for. What else would you want?
But if you really insist on running the device unencrypted (you will be running your device with absolutely no security if you do this), then you need to do the following;
1. Format (not just wipe) the data partition;
2. Reboot OrangeFox;
3. Go to the OTA settings, and tick "Disable Forced-Encryption";
4. Flash the ROM;
5. Boot the ROM.
All things being equal, the ROM will remain unencrypted - but you can kiss goodbye to any possibility of having any security on your ROM. If anybody gets a hold of your phone, he will have full access to everything on it, without any restriction of any kind. Clearly, you really don't want this situation, so I am not sure why you would want the phone to be unencrytped.
Note: some ROMs will simply ignore all efforts to disable forced-encryption, and will happily encrypt anyway. If you have such a ROM, then I would add "4A" to the above list - "Flash magisk before booting the ROM"
DarthJabba9 said:
Yes, the ROM will encrypt again, unless you disable forced-encryption before flashing it (there is a setting in OrangeFox for that). However, lavender has serious issues if it is not encrypted (pin/password/fingerprint will not work). So I do not recommend disabling forced-encryption.
The point is that OrangeFox will automatically decrypt when you boot it up, so that the recovery has full access to internal storage and the data partition. Since 99.9% of lavender devices are encrypted, there is absolutely no problem running OrangeFox on them. This is the best you can hope for. What else would you want?
But if you really insist on running the device unencrypted (you will be running your device with absolutely no security if you do this), then you need to do the following;
1. Format (not just wipe) the data partition;
2. Reboot OrangeFox;
3. Go to the OTA settings, and tick "Disable Forced-Encryption";
4. Flash the ROM;
5. Boot the ROM.
All things being equal, the ROM will remain unencrypted - but you can kiss goodbye to any possibility of having any security on your ROM. If anybody gets a hold of your phone, he will have full access to everything on it, without any restriction of any kind. Clearly, you really don't want this situation, so I am not sure why you would want the phone to be unencrytped.
Note: some ROMs will simply ignore all efforts to disable forced-encryption, and will happily encrypt anyway. If you have such a ROM, then I would add "4A" to the above list - "Flash magisk before booting the ROM"
Click to expand...
Click to collapse
I just saw the option OTA -*> disable forced-encryption. I will try that if I have some time this week, if I don't find other work around.
And just to be clear, yes I want my phone encrypted. Yes I know security is important.
But what I prefer is to have up to date ROM with security patchs and new features.
Because my recovery (OrangeFox and TWP) wasn't able to decrypt my phone I wasn't able to wipe cache and delvik and to do updates.
The thing is there is a unknown password asked when I boot in recovery (I tried every operations I have found on every forums).
Will give some updates later on this thread.
Again, thanks for your answers.
Roster42 said:
I just saw the option OTA -*> disable forced-encryption. I will try that if I have some time this week, if I don't find other work around.
And just to be clear, yes I want my phone encrypted. Yes I know security is important.
But what I prefer is to have up to date ROM with security patchs and new features.
Because my recovery (OrangeFox and TWP) wasn't able to decrypt my phone I wasn't able to wipe cache and delvik and to do updates.
The thing is there is a unknown password asked when I boot in recovery (I tried every operations I have found on every forums).
Will give some updates later on this thread.
Again, thanks for your answers.
Click to expand...
Click to collapse
As I have said, OrangeFox is most definitely able to decrypt. I am yet to come across a single lavender ROM where OrangeFox has not been able to decrypt (and I have tested on virtually all Q ROMs out there) - unless there is something that you are doing (or not doing) , or (which would be very strange indeed) there is something about your own specific phone that makes it particularly impervious to OrangeFox decryption in a way that the phones of several thousands of OrangeFox lavender users are not.
delete
I tried yesturday a clean install, still having the same issue with this ROM : https://forum.xda-developers.com/redmi-note-7/development/rom-havoc-os-2-6-t3938288
I have tried to :
- Format data
- Reboot Recovery
- Wipe all
- Reboot Recovery
- Flash ROM
- Boot ROM (encryption done)
- Reboot recovery OrangeFox : Still asking a password
I tried also to disable forced-encryption with the same step and it's not changing anything.
Is that an issue with the ROM (HavocOS 3.0) ?
Roster42 said:
I tried yesturday a clean install, still having the same issue with this ROM : https://forum.xda-developers.com/redmi-note-7/development/rom-havoc-os-2-6-t3938288
I have tried to :
- Format data
- Reboot Recovery
- Wipe all
- Reboot Recovery
- Flash ROM
- Boot ROM (encryption done)
- Reboot recovery OrangeFox : Still asking a password
I tried also to disable forced-encryption with the same step and it's not changing anything.
Is that an issue with the ROM (HavocOS 3.0) ?
Click to expand...
Click to collapse
Did do you anything else between these two steps ;
- Boot ROM (encryption done)
[ ??? ]
- Reboot recovery OrangeFox : Still asking a password
If you did nothing in-between those two steps, then I would imagine that the issue is with the ROM (probably its device tree).
BTW: I should also like to see the recovery logs.
DarthJabba9 said:
Did do you anything else between these two steps ;
- Boot ROM (encryption done)
[ ??? ]
- Reboot recovery OrangeFox : Still asking a password
If you did nothing in-between those two steps, then I would imagine that the issue is with the ROM (probably its device tree).
BTW: I should also like to see the recovery logs.
Click to expand...
Click to collapse
When ROM boot for the first time it get encrypted, when the encryption process is finished the phone reboot to system and then the android startup process is starting like a new fresh phone. So I just press volume up + shutdown to go in recovery mode and then it asking me a password.
So no I havn't done anything more, I think.
Thank you anyway for your answers.
I think I will go on others ROM, this one seems broken.
I am not the only one havn't this issue.