Database Develop

Phone not booting after FlashFire flash.

Hello,
Thanks for taking the time to look at this. I ran into a bootloop issue after updating my nexus 6 to a higher version of android. After I flashed the new version everything worked just fine but I kept getting the error message "Google play services has stopped" so I decided to re-flash something I thought I needed but after I flashed the file called "Modem firmware" it made me get stuck in a bootloop. The error I got during flashing in FlashFire was "IOException: write failed: ENOSPC (No space left on device)" and then after that infinite bootloop. I have TWRP installed but for some reason, I can't access my backup because it's asking for a decrypt code I didn't even setup. So is there a way to fix this? Possibly wipe the phone and install a custom ROM?
Thanks.

Wipe the phone, connect the N6 to your PC, and using ADB flash a stock ROM. Where the components are mismatched, flashing a stock ROM will resolve that issue and probably all your others. You will however need to flash your recovery and then your custom ROM - if you use one - as well as your root solution. Finally, whatever you do from now on, don't use Flashfire for the baseband.

irontaco1 said:
... so I decided to re-flash something I thought I needed but after I flashed the file called "Modem firmware" it made me get stuck in a bootloop. The error I got during flashing in FlashFire was "IOException: write failed: ENOSPC (No space left on device)" and then after that infinite bootloop. I have TWRP installed but for some reason, I can't access my backup because it's asking for a decrypt code I didn't even setup. So is there a way to fix this? Possibly wipe the phone and install a custom ROM?
Click to expand...
Click to collapse
Since I "routinely" flash modem zips through FF, I'm wondering if what you did was try to extract the modem img from the full software update? That is not a direction I would go in [emoji4]
There are modem flashable zips for the N6 that can be flashed through FF.
I also think the issue with accessing your back up is due to the user data partition being encrypted. What version of TWRP are you using? If not the newest (as of this writing 3.1.1-0), then that can also give you trouble.

irontaco1 said:
Hello,
Thanks for taking the time to look at this. I ran into a bootloop issue after updating my nexus 6 to a higher version of android. After I flashed the new version everything worked just fine but I kept getting the error message "Google play services has stopped" so I decided to re-flash something I thought I needed but after I flashed the file called "Modem firmware" it made me get stuck in a bootloop. The error I got during flashing in FlashFire was "IOException: write failed: ENOSPC (No space left on device)" and then after that infinite bootloop. I have TWRP installed but for some reason, I can't access my backup because it's asking for a decrypt code I didn't even setup. So is there a way to fix this? Possibly wipe the phone and install a custom ROM?
Thanks.
Click to expand...
Click to collapse
Read this for information on how to bypass the password that your backup is asking for https://www.google.com/amp/s/www.ho...fter-restoring-from-twrp-android-backups/amp/

Strephon Alkhalikoi said:
Wipe the phone, connect the N6 to your PC, and using ADB flash a stock ROM. Where the components are mismatched, flashing a stock ROM will resolve that issue and probably all your others. You will however need to flash your recovery and then your custom ROM - if you use one - as well as your root solution. Finally, whatever you do from now on, don't use Flashfire for the baseband.
Click to expand...
Click to collapse
Hey thanks for the help phone is running just fine now. I grabbed the factory image from the Google dev page and flashed it the hard way. For some reason ADB wouldn't mount /system after it was finished so I used fastboot to flash system, boot, radio, etc. Guess I won't use Flashfire for baseband anymore :laugh:

ktmom said:
Since I "routinely" flash modem zips through FF, I'm wondering if what you did was try to extract the modem img from the full software update? That is not a direction I would go in [emoji4]
There are modem flashable zips for the N6 that can be flashed through FF.
I also think the issue with accessing your back up is due to the user data partition being encrypted. What version of TWRP are you using? If not the newest (as of this writing 3.1.1-0), then that can also give you trouble.
Click to expand...
Click to collapse
Phone is working fine now. The files were encrypted because the stock kernel I was using was obviously non-permissive so it automatically encrypted my files upon reboot before it bootlooped. Really appreciate the help though.

TWRP always lost

Hi!
I did a rebrand and updated my P10 to VTR-L29C432B180.
But every time I try to reboot to recovery, I boot with Huawei recovery.
If I want to boot to TWRP I need to reload it from bootloader mode and restart with adb command.
I would like to restart recovery without reload it each time.
Could you help me to fix this please?
I've got another problem with TWRP. I can't access to internal memory because the file name are changed. They are changed to code as if they were secured. I must have missed something ?
Thanks for your help!

anremi said:
Hi!
I did a rebrand and updated my P10 to VTR-L29C432B180.
But every time I try to reboot to recovery, I boot with Huawei recovery.
If I want to boot to TWRP I need to reload it from bootloader mode and restart with adb command.
I would like to restart recovery without reload it each time.
Could you help me to fix this please?
I've got another problem with TWRP. I can't access to internal memory because the file name are changed. They are changed to code as if they were secured. I must have missed something ?
Thanks for your help!
Click to expand...
Click to collapse
Twrp is not able to manage Huawei encryption scheme, that is the reason FromFuture (the only custom ROM around) request to format /data while installing, he managed to avoid re-encryption, which usually happens compulsively whenever EMUI boots. It's a forced function (and useless to me) that has no management (at all), but there it is...
Probably (not 100% sure about this), the same system overwrites the recovery as part of the process. If that is the case, FF ROM is the only solution I know (there is kangvip ROM too, but it's not published here and even when there is a specific kernel to avoid re-encryption, it didn't work for me).

Thanks for your reply. I understand the encryption stuff...
I'm going to try to fix my problem with SD card and flash SU. I hope the ROM rooted will satisfy myself.

Did you disconnect the USB cable when you try to start TWRP?

I did... Ko !
I managed to root the phone and I installed TWRP from Flashify and now it's ok.
Thanks for the help.
The subject can be closed.

Verification Failed - Bootloop. Brand new Note9, twrp + magisk flash....

Hi all - Australian here with Optus Note 9.
Got my Note9 this morning. Flashed twrp (from https://forum.xda-developers.com/ga...t/recovery-twrp-galaxy-note-9-exynos-t3833933). Flashed magisk from page 1 in same thread.
Now can't boot. Stuck on a black screen saying;
VERIFICATION FAILED
unable to restart your device. The ingerity verification has failed. You need to reset your device to factory default settings. This will erase your data
[ RESET].
Click on 'reset', it goes to twrp then loops around.
Anyone know how to fix?

Im with optus too. If you can get back into twrp just flash stock rom or a custom rom.

ciaox said:
Im with optus too. If you can get back into twrp just flash stock rom or a custom rom.
Click to expand...
Click to collapse
I just tried flashing a custom rom - stuck with it in boot loop.
So whilst I re-download the stock stuff, I tried deleting my data in twrp and I'm just about to try a no-verity-opt-encrypt6.zip with custom pie rom. Fingers crossed .

hmm strange. first boot takes a good 5mins tho. good luck

Worked fine.
Not sure whats changed, but I needed to flash the no-verity-ope-encrypt6.zip, and now it boots just fine.
Very strange. Oh well, onwards and upwards to Pie goodness (like my old Huawei mate10pro)

Mod feel free to close this one. ty

Toldorn said:
Worked fine.
Not sure whats changed, but I needed to flash the no-verity-ope-encrypt6.zip, and now it boots just fine.
Very strange. Oh well, onwards and upwards to Pie goodness (like my old Huawei mate10pro)
Click to expand...
Click to collapse
flashing magisk v16 and up would have also fixed it. but format data and factory wipe in twrp was a required step before flashing custom rom.

Please help me downgrade from Pie to Oreo

Hi guys, I have a OnePlus 3T which I have been using since 2017 and it worked perfectly. But a few months ago it updated to Android 9 Pie and ever since then my phone has gotten far slower, keeps hanging on certain things and sometimes I can't even make a call directly from contacts. I have to click call then it seems like the call is starting up but then just freezes and cuts off. Afterward, I have to go to call history and make the call again and it works.
I waited a while to see if a newer update will fix this slowdown and issues but after 2 or 3 more Pie updates it's still unresponsive and crashes the dialer. So I just want to know if anyone can tell me where I can find a ROM for final Oreo version that is compatible with OnePlus 3T and the best way I can downgrade.
I tried following a guide already but I ran into issues simply flashing TWRP. I Installed the ABD drivers, unlocked bootloader and rebooted.
Then in fastboot mode, I tried to flash it and it seemed to work because in the ABD PowerShell windows it said "Okay" after I used the cmd to flash.
But when I reboot and go into recovery, I still have the default recovery options.
This is the first time I am trying to flash my phone and I'm only doing it because it went from a phone that ran super smooth to one that is barely usable...I mean Contacts and the actual Phone apps are hanging and crashing. It even crashes when I try to answer incoming calls sometimes. The phone keeps ringing and I get a message saying the program is unresponsive, giving me options to "wait" or "close"

TT-Twister said:
...
I tried following a guide already but I ran into issues simply flashing TWRP. I Installed the ABD drivers, unlocked bootloader and rebooted.
Then in fastboot mode, I tried to flash it and it seemed to work because in the ABD PowerShell windows it said "Okay" after I used the cmd to flash.
But when I reboot and go into recovery, I still have the default recovery options.
...
Click to expand...
Click to collapse
Something you need to know: stock OOS will always reinstall the stock recovery when the phone boots into system.
So if you
1. Booted into fastboot
2. Flashed TWRP
3. Booted your phone
4. Booted into recovery
then TWRP got overwritten in step 3.
What you should have done after flashing TWRP was boot into recovery directly (use the volume keys while in fastboot mode to select that option then press the power button).
Sent from my OnePlus 3T using XDA Labs

BillGoss said:
Something you need to know: stock OOS will always reinstall the stock recovery when the phone boots into system.
So if you
1. Booted into fastboot
2. Flashed TWRP
3. Booted your phone
4. Booted into recovery
then TWRP got overwritten in step 3.
What you should have done after flashing TWRP was boot into recovery directly (use the volume keys while in fastboot mode to select that option then press the power button).
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Thanks for the reply...and it got me a step further. But when it got to TWRP it starts at "Mount Decrypt Data" I assumed this was my phone pin...and when I tried that it opens up a cmd window which said "unable to mount storage" then says "updating partition details" but it sort of freezes then the phone turns off and powers on with the notification LED being "white" but the screen is black and the phone just stays like this for ages. Only thing I could do is hold down the power button to power down the phone and restart it. At least TWRP seems to have flashed because even when I go into recovery from the boot menu it goes to TWRP.

TT-Twister said:
Thanks for the reply...and it got me a step further. But when it got to TWRP it starts at "Mount Decrypt Data" I assumed this was my phone pin...and when I tried that it opens up a cmd window which said "unable to mount storage" then says "updating partition details" but it sort of freezes then the phone turns off and powers on with the notification LED being "white" but the screen is black and the phone just stays like this for ages. Only thing I could do is hold down the power button to power down the phone and restart it. At least TWRP seems to have flashed because even when I go into recovery from the boot menu it goes to TWRP.
Click to expand...
Click to collapse
Personally I would not downgrade to Oreo. Pie works fine. The problems your were having could have probably been solved by simply doing a factory reset.
Since you've unlocked your bootloader, you've effectively done a factory reset. So try just booting the system and set up your phone again. It'll probably be fine now that you're doing a clean install.
Sent from my OnePlus 3T using XDA Labs

BillGoss said:
Personally I would not downgrade to Oreo. Pie works fine. The problems your were having could have probably been solved by simply doing a factory reset.
Since you've unlocked your bootloader, you've effectively done a factory reset. So try just booting the system and set up your phone again. It'll probably be fine now that you're doing a clean install.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Yea...I have done several factory resets in the process of unlocking the bootloader and flashing twrp. So it didn't fix the issue. The main issue is linked to "contacts" which basically freezes most times I try to make a call. It makes the call but crashes contacts and the "Phone" app. Which is stupid because that's the main purpose of a phone.
Also, another key reason for wanting to downgrade to Oreo is the ability to record phone calls. This is very useful to me and those apps stopped working with Pie I think.

TT-Twister said:
Yea...I have done several factory resets in the process of unlocking the bootloader and flashing twrp. So it didn't fix the issue. The main issue is linked to "contacts" which basically freezes most times I try to make a call. It makes the call but crashes contacts and the "Phone" app. Which is stupid because that's the main purpose of a phone.
Also, another key reason for wanting to downgrade to Oreo is the ability to record phone calls. This is very useful to me and those apps stopped working with Pie I think.
Click to expand...
Click to collapse
If I was to go back to Oreo I would:
Download the full Oreo OOS ROM and backup everything you need onto your PC. Then in TWRP:
1. Do a factory reset
2. Flash OOS 5.0.4
3. Wipe>format data (to get rid of encryption)
4. Reboot system, which will also encrypt the data again and replace TWRP with the stock recovery
5. Use ADB to restore the data on your phone
6. Flash TWRP and restore your Oero backup.
Sent from my OnePlus 3T using XDA Labs

BillGoss said:
If I was to go back to Oreo I would:
Download the full Oreo OOS ROM and backup everything you need onto your PC. Then in TWRP:
1. Do a factory reset
2. Flash OOS 5.0.4
3. Wipe>format data (to get rid of encryption)
4. Reboot system, which will also encrypt the data again and replace TWRP with the stock recovery
5. Use ADB to restore the data on your phone
6. Flash TWRP and restore your Oero backup.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Did you read what I said? I did what you said and manage to boot into TWRP but I told you the issue about encryption and my phone freezing.
So I don't know how I'm supposed to flash any OS if I can't get TWRP to work in the first place.

TT-Twister said:
Did you read what I said? I did what you said and manage to boot into TWRP but I told you the issue about encryption and my phone freezing.
So I don't know how I'm supposed to flash any OS if I can't get TWRP to work in the first place.
Click to expand...
Click to collapse
In that case, I hope you've got backups on your PC because you're going to have to format your phone. TWRP>Wipe>Format data. You'll need to cancel out of the password screen to do the wipe.
Then reboot into recovery and use ADB to copy the files to your phone and flash Oreo.
Sent from my OnePlus 3T using XDA Labs

BillGoss said:
In that case, I hope you've got backups on your PC because you're going to have to format your phone. TWRP>Wipe>Format data. You'll need to cancel out of the password screen to do the wipe.
Then reboot into recovery and use ADB to copy the files to your phone and flash Oreo.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
I got my data backed up using some software called "dr.fone" but how do I use ADB to copy files to the phone?
As I said at the start, this is literally the first time I'm trying to do this. I never flashed my phone before and never used ADB or TWRP before.
I'm literally just following instructions in guides and forums. So please don't assume I know how all of this works.

Hmm. I've been thinking about your problem and I have some questions/suggestions.
1. What version of TWRP are you using? (I would use the latest one from https://dl.twrp.me/oneplus3/ )
2. Can you boot your phone normally? If so, try setting a new password and say Yes for secure start up. Then verify that when you reboot you are prompted for a password (Starting Android screen, not just the lock screen). If that works, boot into TWRP. Does the new password work?

BillGoss said:
Hmm. I've been thinking about your problem and I have some questions/suggestions.
1. What version of TWRP are you using? (I would use the latest one from https://dl.twrp.me/oneplus3/ )
2. Can you boot your phone normally? If so, try setting a new password and say Yes for secure start up. Then verify that when you reboot you are prompted for a password (Starting Android screen, not just the lock screen). If that works, boot into TWRP. Does the new password work?
Click to expand...
Click to collapse
I'm using the latest version of TWRP (top one on that list)
I can boot the phone, and it works obviously. But I was having serious issues and slowdowns after updating to Pie.
Changing the password didn't work...but doing what you said before and formatting the device and rebooting into TWRP seems to have worked.
It's recognizing the storage and I can choose zip files to install.
Do you know the last version of Oreo that was compatible with the 3T? I think it's either 5.0.8 but they may have released 5.1.8 for it...I can't remember and can't seem to find the info anywhere.

TT-Twister said:
I'm using the latest version of TWRP (top one on that list)
I can boot the phone, and it works obviously. But I was having serious issues and slowdowns after updating to Pie.
Changing the password didn't work...but doing what you said before and formatting the device and rebooting into TWRP seems to have worked.
It's recognizing the storage and I can choose zip files to install.
Do you know the last version of Oreo that was compatible with the 3T? I think it's either 5.0.8 but they may have released 5.1.8 for it...I can't remember and can't seem to find the info anywhere.
Click to expand...
Click to collapse
Glad you can now get into TWRP.
5.0.8 was the last stable Oreo version (I never used betas).
Sent from my OnePlus 3T using XDA Labs

I would second the suggestion that you don't downgrade to Oreo. I was having the same issues you mentioned on Pie, but have since sorted them out. Pie is now running very nicely for me.
A good deep cleaning did it for me, even after a previous factory reset had failed to fix it.

ataft said:
I would second the suggestion that you don't downgrade to Oreo. I was having the same issues you mentioned on Pie, but have since sorted them out. Pie is now running very nicely for me.
A good deep cleaning did it for me, even after a previous factory reset had failed to fix it.
Click to expand...
Click to collapse
Well, it seems like downgrading to Oreo is going to be a huge task. Because my research I need to flash some stock firmware before being able to flash Oreo again.
Which I tried, but for some reason, it's not flashing it. So now I need to download the latest stable version of Pie for 3T again?
Can any of you tell me what version that is?

TT-Twister said:
Well, it seems like downgrading to Oreo is going to be a huge task. Because my research I need to flash some stock firmware before being able to flash Oreo again.
Which I tried, but for some reason, it's not flashing it. So now I need to download the latest stable version of Pie for 3T again?
Can any of you tell me what version that is?
Click to expand...
Click to collapse
What is the latest stable of Pie? 9.0.5
But Bill has already given you the steps for downgrading if you want.

TT-Twister said:
Well, it seems like downgrading to Oreo is going to be a huge task. Because my research I need to flash some stock firmware before being able to flash Oreo again.
Which I tried, but for some reason, it's not flashing it. So now I need to download the latest stable version of Pie for 3T again?
Can any of you tell me what version that is?
Click to expand...
Click to collapse
I decided to test downgrading to Oreo from Pie. And I learnt that it's basically the same process as upgrading from Oreo to Pie. Since my phone is unlocked and encrypted I had to remove the encryption using TWRP>Wipe>Format data: yes when going from Oreo to Pie and the same when going from Pie to Oreo.
So my process to downgrade is:
- Backup everything I want to keep from my phone.
- Flash OOS 5.0.8 full stock zip in TWRP. This completely overwrites the 9.0.5 firmware and system.
- Remove encryption: TWRP>Wipe>Format data: yes. (You'll lose everything on your phone)
- Reboot system (it re-encrypts the phone and replaces TWRP with stock recovery).
- Restored phone data, and so on.
Sent from my OnePlus 3T using XDA Labs

One more thing that I'd forgotten about: you can run OOS Oreo on the Pie firmware. So if you still have the Pie firmware installed, just restore an Oreo backup and you should be ok.
See point at the end of https://forum.xda-developers.com/on...ageos-16-0-oneplus-3-3t-t3866517/post79378447
Sent from my OnePlus 3T using XDA Labs

BillGoss said:
I decided to test downgrading to Oreo from Pie. And I learnt that it's basically the same process as upgrading from Oreo to Pie. Since my phone is unlocked and encrypted I had to remove the encryption using TWRP>Wipe>Format data: yes when going from Oreo to Pie and the same when going from Pie to Oreo.
So my process to downgrade is:
- Backup everything I want to keep from my phone.
- Flash OOS 5.0.8 full stock zip in TWRP. This completely overwrites the 9.0.5 firmware and system.
- Remove encryption: TWRP>Wipe>Format data: yes. (You'll lose everything on your phone)
- Reboot system (it re-encrypts the phone and replaces TWRP with stock recovery).
- Restored phone data, and so on.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Do you have a link for the OOS 5.0.8 full stock zip with the firmware?
I downloaded files from these links:
https://www.getdroidtips.com/oxygenos-5-0-8-oneplus-3-3t/
https://www.androidjungles.com/oneplus-3t-flash-file/
But neither of them are flashing in TWRP.

TT-Twister said:
Do you have a link for the OOS 5.0.8 full stock zip with the firmware?
I downloaded it from here https://www.getdroidtips.com/oxygenos-5-0-8-oneplus-3-3t/ but it's not flashing in TWRP.
Click to expand...
Click to collapse
https://otafsg1.h2os.com/patch/amaz...n_28_OTA_070_all_1812060053_d75f3be1db2be.zip
Sent from my OnePlus 3T using XDA Labs

ataft said:
I would second the suggestion that you don't downgrade to Oreo. I was having the same issues you mentioned on Pie, but have since sorted them out. Pie is now running very nicely for me.
A good deep cleaning did it for me, even after a previous factory reset had failed to fix it.
Click to expand...
Click to collapse
What do you mean by deep cleaning?. I tried hard reset but after using apps phone again became dead slow.

Xiaomi Note 9 is still bootlooping even after installing stock firmware

Hello! Just created an account in this forum to seek help because this is driving me nuts.
I have a Xiaomi Redmi Note 9 (Merlin) which has no system (Android), but I still can access fastboot and recovery menu, so I went ahead and unlocked the bootloader and flashed MIUI without any issue. To my surprise, when I booted the phone back up, it was like I didn't do anything as it still bootlooped, it didn't even show the MIUI logo, so I tried again; still nothing.
So, I tried the following:
- I followed the guide in this forum for hard-bricked Note 9 phones (https://forum.xda-developers.com/t/...icked-redmi-note-9-merlin-hard-brick.4347025/), and I can tell the firmware flashes because the starting menu and the fastboot logo changed from the rabbit to FASTBOOT in orange letters, but still no system.
- I flashed stock firmware, but still no system.
- I flashed the MIUI version that the phone came with through fastboot, but still no system
- I tried to flash the newest version of MIUI the phone came with through TWRP using the recovery version, but still no system (and when I try to reboot, TWRP says there is no system)
- I tried installing Pixel Experience to see if MIUI was the issue but, still no system. The phone just keeps bootlooping endlessly.
- I tried running https://github.com/Zackptg5/Disable_Dm-Verity_ForceEncrypt to see if the encryption was the problem, but no progress.
I would appreciate any help to at least have my phone working, even if it's not with MIUI but with a custom ROM. At this point I don't care anymore, just want a useable phone.
Thank you.

Hi. Just flash the whole stock MIUI ROM of your choice and then
In TWRP you must format /data (you did first make a backup of your personal data right?)
Then phone should boot again.
I hope this helps. Good luck!

lebigmac said:
Hi. Just flash the whole stock MIUI ROM of your choice and then
In TWRP you must format /data
I hope this helps. Good luck!
Click to expand...
Click to collapse
I've tried that a couple of times but it's like I didn't do anything, when I reboot I still get no system

bump

bump - really desperate about this matter

I can't believe reflashing stock ROM + formatting the /data partition didn't fix your issue
You are using the flash_all.sh script that comes with the stock MIUI firmware right?
well your only option it seems is to check the bootloop log and then try to find out the reason for bootloop that way. Maybe somewhere inside TWRP you can find some kind of bootloop log? Good luck!

lebigmac said:
I can't believe reflashing stock ROM + formatting the /data partition didn't fix your issue
You are using the flash_all.sh script that comes with the stock MIUI firmware right?
well your only option it seems is to check the bootloop log and then try to find out the reason for bootloop that way. Maybe somewhere inside TWRP you can find some kind of bootloop log? Good luck!
Click to expand...
Click to collapse
Yeah, I even tried with other PCs to see if that was the issue. Will try looking in the logs. Thank you!