Database Users

Create Stock Recovery.img from FTF File

Hi, I am in the process of preparing for upgrading from 7.0 to 7.1.1
I know I need to replace the Custom Kernel with the Stock Kernel. And I have to replace TWRP with Stock Recovery.
Can anybody tell me, which file inside the FTF is the stock recovery? I already found the kernel. Need help to find the stock recovery, thank you!

tempurastyle said:
Need help to find the stock recovery, thank you!
Click to expand...
Click to collapse
We don't have one which is why we have to use TWRP.

So my only way is to flash via Flashtool without wipe?

tempurastyle said:
So my only way is to flash via Flashtool without wipe?
Click to expand...
Click to collapse
Do that then mod your own kernel. [How To] make your own XPERIA DRM-fix kernel.
And flash a TWRP.img to the recovery partition.

fotakernel.sin reside's where we flash twrp on stock. you do not need to flash it to upgrade, contrary you can exclude it in flashtool and keep twrp between updates.

realtuxen said:
fotakernel.sin reside's where we flash twrp on stock. you do not need to flash it to upgrade, contrary you can exclude it in flashtool and keep twrp between updates.
Click to expand...
Click to collapse
this is real knowledge, thanks! so just to be sure, this is what i will do in flashtool:
1) wipe: nothing selected
2) exclude: fotakernel.sin selected
can anybody confirm this is correct?
then after this, i will flash a custom kernel via fastboot and magisk via twrp.
one question regarding magisk: will it be deleted during the flashtool update?

So I ran into a problem...
The Upgrade to 7.1.1 via flashtool was smooth. Then, i flashed twrp via fastboot as usual. When I tried to enter twrp, i get a password prompt to decrypt the phone. So i don't know which password i need to type in. I tried the unlock PIN, doesnt work. Any suggestions?

tempurastyle said:
Any suggestions?
Click to expand...
Click to collapse
To get round that you need to run the following commands...
Code:
fastboot format userdata
fastboot format cache
...so you'll need to backup all your data first.

XperienceD said:
To get round that you need to run the following commands...
Code:
fastboot format userdata
fastboot format cache
...so you'll need to backup all your data first.
Click to expand...
Click to collapse
Ok, so I decided to keep my data and don't install twrp. Now I got another issue, is it possible to install Magisk without TWRP? I already got my kernel using my ta backup according to the instructions a few posts above, which really works great.

tempurastyle said:
Ok, so I decided to keep my data and don't install twrp. Now I got another issue, is it possible to install Magisk without TWRP? I already got my kernel using my ta backup according to the instructions a few posts above, which really works great.
Click to expand...
Click to collapse
I thought you excluded fotakernel so you did not have to flash twrp again. Oh well anyway you can use twrp to flash zips just fine although /data is encrypted, most flash zips do not write to /data anyway some like supersu use /cache (which is not encrypted contrary to the info above) to get around encryption at next boot. And like magisk also patch the boot.img live on your phone, some write to /system which is not encrypted either, I never seen a flash zip that did write to /data. Only backup/browsing/etc on /data is affected.
So when presented with the password screen in twrp just press cancel and make sure the zip you want to flash is located on the external sd card (do not encrypt this in phone settings, your card will be unreadable from pcs to) then choose flash zip and choose the external sdcard to pick the zip from and flash magisk or whatever. You need to run your kernel through ta poc or rootkernel first and disable dm verity and sony ric. (you write you did this so just install twrp and flash away) Do not wipe cache before rebooting just in case magisk uses this in a similar way to supersu (I have no idea)

Also if you do the above fastboot format commands suggested in post#8 without disabling 'forceencrypt' for /data (fstab in the kernel image or with a tool) the phone will encrypt itself again as soon as you turn it on.
If forceencrypt is disabled the same can be achieved (clearing encryption) with a factory reset btw.
So if you did not bump into the password in twrp before you likely did a factory reset with a kernel with encryption disabled. Then, maybe after updating you rebooted stock and the phone encrypted itself again, then now you can not access /data in twrp. Thats also because we have no version of it that supports encryption on the X-compact though. Again do not worry, I have not meet a zip I could not flash, supersu, magisk, etc because they do not access /data anyway.

realtuxen said:
I thought you excluded fotakernel so you did not have to flash twrp again. Oh well anyway you can use twrp to flash zips just fine although /data is encrypted, most flash zips do not write to /data anyway some like supersu use /cache (which is not encrypted contrary to the info above) to get around encryption at next boot. And like magisk also patch the boot.img live on your phone, some write to /system which is not encrypted either, I never seen a flash zip that did write to /data. Only backup/browsing/etc on /data is affected.
So when presented with the password screen in twrp just press cancel and make sure the zip you want to flash is located on the external sd card (do not encrypt this in phone settings, your card will be unreadable from pcs to) then choose flash zip and choose the external sdcard to pick the zip from and flash magisk or whatever. You need to run your kernel through ta poc or rootkernel first and disable dm verity and sony ric. (you write you did this so just install twrp and flash away) Do not wipe cache before rebooting just in case magisk uses this in a similar way to supersu (I have no idea)
Click to expand...
Click to collapse
Yes, after the first upgrade attempt, i let twrp untouched. then when entering twrp, i didnt have a password, so i skipped it. i couldn't find the sd card in the file browser, and after i hit reboot in twrp the phone restarted and got stuck in boot.
So I flashed again, this time deleting twrp. the initial boot up went fine. Then i flashed twrp again and once again, without having a password, i just skipped the password prompt. still couldnt find the sd card, and i rebooted out of twrp. and the phone got stuck again.
after 2-3 trials, i figured out that everytime i rebooted out of twrp, the phone gets stuck during boot. even after turning it off and on, so a reflash was needed.
now i have given up using twrp, so i have an unrooted phone with an unlocked bootloader. which does not allow me to use android pay. i think to solve my problem is:
1) i need to know which twrp version really works, i have tried
this version
and this version
both cause a boot failure for me
2) i need to find the sd card location in the twrp file browser (all the folders show empty for me)
if nothing works, i guess i need to wipe my phone, but that's what i would like to avoid. thanks for your help guys!

tempurastyle said:
Yes, after the first upgrade attempt, i let twrp untouched. then when entering twrp, i didnt have a password, so i skipped it. i couldn't find the sd card in the file browser, and after i hit reboot in twrp the phone restarted and got stuck in boot.
So I flashed again, this time deleting twrp. the initial boot up went fine. Then i flashed twrp again and once again, without having a password, i just skipped the password prompt. still couldnt find the sd card, and i rebooted out of twrp. and the phone got stuck again.
after 2-3 trials, i figured out that everytime i rebooted out of twrp, the phone gets stuck during boot. even after turning it off and on, so a reflash was needed.
now i have given up using twrp, so i have an unrooted phone with an unlocked bootloader. which does not allow me to use android pay. i think to solve my problem is:
1) i need to know which twrp version really works, i have tried
this version
and this version
both cause a boot failure for me
2) i need to find the sd card location in the twrp file browser (all the folders show empty for me)
if nothing works, i guess i need to wipe my phone, but that's what i would like to avoid. thanks for your help guys!
Click to expand...
Click to collapse
The 2. issue with the sdcard is easy. After pressing 'install' button in twrp at the bottom left press the "select storage' button, a small window will pop up then select the 'micro sdcard' and press 'ok", you should see your files now.
The 1. ssue is really odd! I use the second twrp you posted, for some wierd reason the first one does not boot for me (twrp does not start). But I talked with another guy for him it was the other way around. It was really strange. I think most can use both though without problems
There is one more twrp 3.1 from bambamx, but I really do not get this, twrp boots from its own partition with its own kernel. They should be separated unless twrp does something to system ofcause which it very well shouldn't unless you ask it to, deleting a important file or flashing something. I have never heard of this sorry. One thing is certain our device sure could use a stable nougat encryption compatible twrp!
I will let you know if I find something, you can try the last available version, I have no idea if it will exhibit the same strange behaviour. But maybe its worth a shot although it seems something else is at play.
A couple of stupid questions sorry; You disabled dm verity and sony ric in ta poc right, and it does not happen if you boot your phone normal a couple of times.
Edit: sorry Mr. Sandman had not left so I did not read properly here from the morning. I will edit my post to actually answer as best as I can lol.

Just to let you know:
1. You do not need to install TWRP to use it! You can just do
Code:
fastboot boot <TWRP image>
to run TWRP on the phone (instead of
Code:
fastboot flash boot <TWRP image>
). The only drawback of this method is that you will always need a computer to enter TWRP. Btw. with this method you can also try out a custom kernel image before flashing it.
2. You do not need write access to /data partition to install Magisk. It was explained in another thread that Magisk can use /cache temporary when access to /data is not available. It will write to /data on first boot instead.
3. While using TWRP you can use adb to transfer files onto the phone, so you don't need to have them ready on the internal storage.

realtuxen said:
The 2. issue with the sdcard is easy. After pressing 'install' button in twrp at the bottom left press the "select storage' button, a small window will pop up then select the 'micro sdcard' and press 'ok", you should see your files now.
Click to expand...
Click to collapse
I did, but the SD card can't be selected, and the size shows as 0kb. I did a workaround though: i formatted a spare sd card and copied magisk on it. it was instantly recognized and selectable.
ypnos42 said:
Just to let you know:
1. You do not need to install TWRP to use it! You can just do
Code:
fastboot boot <TWRP image>
to run TWRP on the phone (instead of
Code:
fastboot flash boot <TWRP image>
). The only drawback of this method is that you will always need a computer to enter TWRP. Btw. with this method you can also try out a custom kernel image before flashing it.
3. While using TWRP you can use adb to transfer files onto the phone, so you don't need to have them ready on the internal storage.
Click to expand...
Click to collapse
GREAT advice! I launched TWRP from ADB and successfully flashed Magisk using ADB sideload. Thanks, my phone is rooted again!

Stuck in recovery with no image to flash

First of all, I read this thread, but no luck.
Situation:
* I unlocked bootloader, installed TWRP 3.1.1-1 and flashed Freedom OS, succeding.
* Then I decided to try the Oreo open beta, but had a problem (error 7 flashing it), so I wanted to get back to Freedom OS
* After flashing Freedom OS again (with success) I rebooted but I was stuck at boot logo.
* I decided to flash again OOS 4.5.14, but I misclicked something and I found my self in TWRP with no ROM to flash on SDcard (I think I have checked also internal storage while wiping).
* PANIC!
So, 3 questions:
1) given that I want to stay encrypted (if still possible at this point) should I decrypt data or not at TWRP boot?
2) if I chose decrypt with the unlock code (read that I did) I have to go with decrypt or formatting is enough to keep crypt?
3) MORE IMPORTANT: how do I get a ROM to flash into the phone. Reeboting in TWRP sometimes I see the internal storage, but when I drop a firmware in it I get the transfer windows stuck at 0% and it disappear after a few seconds.
Thanks in advance to who will help me!

this might help - https://forum.xda-developers.com/showthread.php?t=2318497

chris4500uk said:
this might help - https://forum.xda-developers.com/showthread.php?t=2318497
Click to expand...
Click to collapse
Thanks for the suggestion and... it's a beginning.
The problem is that if I sideload a small file like Magisk upload is ok, even if (obviously) it can't install.
When it comes to Oxygen OS I get I cannot read file error.
I doubleclicked the file and it opens in PC, so it isn't corrupted.

I'd be tempted to try another USB cable and maybe another computer if you have one. Failing that, if it's a problem with TWRP your last resort may be a complete low level flash. A good guide is here - https://forum.xda-developers.com/oneplus-5/how-to/unbrick-tool-oneplus-5-t3648169
Edit: I should say be careful if you do have connectivity problems, as flashing using unbrick tools while your connection is bad would not be a good idea at all since it could make things even worse (maybe even hard brick)

I finally got it working. I am a bit ashamed of what the problem was, but I share in case someone else does this stupid error.
The point is: I was formatting /data inside Advanced wipe instead of using "Format Data", so ( I think) I was not rebuilding the sd card allocation table.
After formatting with "Format data" I was able to put the firmware with drag and drop from the PC and I could finally have mu OP5 working again.

Can't you press reboot to recovery and decrypt with your code so your device gets mounted on a PC? Otherwise you can adb sideload the oxygenos file. I had the same error, but Google gave me this:
https://forum.xda-developers.com/showpost.php?p=69648733&postcount=47
Use the program on all the files in the adb directory and reboot.

Zocker1304 said:
Can't you press reboot to recovery and decrypt with your code so your device gets mounted on a PC? Otherwise you can adb sideload the oxygenos file. I had the same error, but Google gave me this:
https://forum.xda-developers.com/showpost.php?p=69648733&postcount=47
Use the program on all the files in the adb directory and reboot.
Click to expand...
Click to collapse
No; i couldn't. But I solved simply by using "Format data".
SOLVED

UncleDan said:
I finally got it working. I am a bit ashamed of what the problem was, but I share in case someone else does this stupid error.
The point is: I was formatting /data inside Advanced wipe instead of using "Format Data", so ( I think) I was not rebuilding the sd card allocation table.
After formatting with "Format data" I was able to put the firmware with drag and drop from the PC and I could finally have mu OP5 working again.
Click to expand...
Click to collapse
Format data is necessary on the OP5 when moving between Nougat and Oreo. I hope you flashed the Oreo Open Beta rather than Freedom. It's far superior.

jhs39 said:
Format data is necessary on the OP5 when moving between Nougat and Oreo. I hope you flashed the Oreo Open Beta rather than Freedom. It's far superior.
Click to expand...
Click to collapse
[O/T ON]
I didn't at the moment, but I did right now, reverting to stock recovery. Do you now if an Oreo-ready TWRP is around yet?
[O/T OFF]

UncleDan said:
[O/T ON]
I didn't at the moment, but I did right now, reverting to stock recovery. Do you now if an Oreo-ready TWRP is around yet?
[O/T OFF]
Click to expand...
Click to collapse
There are two with download links included in the instructions thread for flashing Oreo. I recommend the Blu Spark TWRP over the Chinese TWRP. It will be updated more often.

A2017G V1.2 0B09 - Cannot install ROMs without Gapps

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.

Probably soft bricked my OP5, is this fixable?

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'

Phone asking for password to open the phone after flashing liquid remix pie

I tried formatting Data I tried formatting internal storage, didn't work. I tried putting the password "default_password" it worked but then the phone said my phone is broken and if to format it. If I say yes it boots to twrp and shows an error message and auto restarts quickly after. And goes to the same password screen. I tried only flashing the ROM and twrp and that also didn't work. I tried flashing stock via the mi tool and then the custom ROM, that didn't work either and ofc only flashing stock works. Can somebody help me? How can I fix this??
SOLVE: wipe data, and if that didn't work (which it didn't this time for me) flash stock and then use a pass code, boot into twrp and you'll probably need to enter the pass code, press on back then wipe then advanced wipe and then wipe data and storage. Reboot recovery, if you don't see the pass code any more that's good, that means you removed the encryption. Liquid remix requires the device to not be encrypted to flash the rom without problems and maybe your rom does too.

I had this issue, the only way (at least for me) is you need to wipe internal storage in twrp as well.

Boot into twrp, there should be an option to format data(it is not the same as wipe data) and after selecting it you need to type yes and then reboot.

WhatzIt2Ya said:
I had this issue, the only way (at least for me) is you need to wipe internal storage in twrp as well.
Click to expand...
Click to collapse
Already did that, didn't work

Will people ever start reading the OP of each thread?
Find out on the next episode of the XDA Developers forum!

michkost858 said:
Will people ever start reading the OP of each thread?
Find out on the next episode of the XDA Developers forum!
Click to expand...
Click to collapse
Yeah, when the NOTES say "And most importantly DONT READ THE OP" ?
---------- Post added at 02:10 PM ---------- Previous post was at 02:10 PM ----------
YayJohn said:
Already did that, didn't work
Click to expand...
Click to collapse
And format data? Not in advanced wipe, it's besides it.

WhatzIt2Ya said:
Yeah, when the NOTES say "And most importantly DONT READ THE OP"
---------- Post added at 02:10 PM ---------- Previous post was at 02:10 PM ----------
And format data? Not in advanced wipe, it's besides it.
Click to expand...
Click to collapse
When he said "Will people ever start reading the OP of each thread?" I think he was talking about you XD because you told me to format internal storage and that was one of the first things I said I done in the post and I fixed the issue before the guy told me to format data in a different way

Here is what i wrote as a step by step :
21vm said:
Hi guys,
...
As i've compiled durong days and weeks all the necessary information before doing anything, i share here for everyone who not sure how to proceed the steps i've followed and the links to the resources.
Feel free to correct, complete or delete wrong steps or make it easier to understand, the goal is to help people as we liked someone do/did it for us.
-- if this can help, use this in other threads, copy it, share it : it's useless if we don't use it --
0. Remove screen locks before flashing (pin, fingerprint...)
1. Download the ROM and Gapps (Gapps package is : arm64 / 9.0 / nano), TWRP installer and Magisk
2. Move your ROM.zip + GApps + TWRP-Installer.zip + magisk to your EXTERNAL storage
3. Enable developer option in ur device and enable oem unlocking in developer option.
4. Make sure drivers are installed correctly on your pc and adb install
5. Save the cosmic dan TWRP fastboot_boot_only.zip in the adb folder (check twice to download the right twrp !!!)
5. Turn off ur phone.
6. Now press and hold voume down+power button to start on download mode
7. connect the phone to the pc/laptop
8. Open command prompt on your pc/laptop and run the following command: fastboot oem unlock
9. Your phone will be unlocked.
10. if your phone reboot, restart it on download mode as previously and enter adb again
11. in order to reboot on twrp, run the following command : fastboot boot boot-recovery.img (the file must be on adb's folder)
12. in twrp -> Wipe->Format data : type YES. Then, go to wipe -> advanced wipe and wipe cache, data and system
13. return to Reboot menu in twrp and change partitions, wipe as previously
14. Flash the ROM zip and the TWRP-Installer.zip
15. Reboot to Recovery via TWRP (Reboot -> Recovery), Flash GApps and Magisk
16. Reboot to System
17. Enjoy !
Click to expand...
Click to collapse

21vm said:
Here is what i wrote as a step by step :
Click to expand...
Click to collapse
if people have this problem they probably are not on stock so that means no need for all that unlocking bootloader process, It's very simple, just format data and storage if that doesnt work do what I did and I know formatting data and storage works because it worked for me once

YayJohn said:
if people have this problem they probably are not on stock so that means no need for all that unlocking bootloader process, It's very simple, just format data and storage if that doesnt work do what I did and I know formatting data and storage works because it worked for me once
Click to expand...
Click to collapse
I think more is better : it's not that hard for people to read my post and start in the point they want, in that case, point 12. But you're right, you said exactly the same as me but your comment i better...