Develop Bugs

Unbricking after a hard brick not working out.

So my OP3 got bricked and I used @Naman Bhalla guide to unbrick my phone using the second method which flashes an old OOS after unbrick. I was successful in unbricking my phone, however once the phone restarts after the unbrick tool it gets stuck in the OOS boot animation (The rotating O animation) and then it reboots and this continues.
I've tried,
1) Sideloading another Stock ROM (OOS 5.0.1.) via stock recovery: Just rebricks my phone
2) Flashing TWRP 3.1.0-0 and tried to install zip for 5.0.1 : TWRP does't recognize phone, (ERROR 7, This ROM is for OnePlus 3, This device is " ") and thus it doesn't flash.
3) Tried upgrading TWRP to 3.2.1. : could'nt do it - Lost recovery, phone just restarts to a black screen with white notification light.
4) Tried flashing OOS 4.5.1 (Nougat) via TWRP 3.1.: Does't boot up. Doesn't even go to the animation and restarts after OnePlus Logo.
Yes, I was stupid enough to not have done a nandroid backup. Desperately need help.

yawarkhalid said:
So my OP3 got bricked and I used @Naman Bhalla guide to unbrick my phone using the second method which flashes an old OOS after unbrick. I was successful in unbricking my phone, however once the phone restarts after the unbrick tool it gets stuck in the OOS boot animation (The rotating O animation) and then it reboots and this continues.
I've tried,
1) Sideloading another Stock ROM (OOS 5.0.1.) via stock recovery: Just rebricks my phone
2) Flashing TWRP 3.1.0-0 and tried to install zip for 5.0.1 : TWRP does't recognize phone, (ERROR 7, This ROM is for OnePlus 3, This device is " ") and thus it doesn't flash.
3) Tried upgrading TWRP to 3.2.1. : could'nt do it - Lost recovery, phone just restarts to a black screen with white notification light.
4) Tried flashing OOS 4.5.1 (Nougat) via TWRP 3.1.: Does't boot up. Doesn't even go to the animation and restarts after OnePlus Logo.
Yes, I was stupid enough to not have done a nandroid backup. Desperately need help.
Click to expand...
Click to collapse
Try with eng.stk's TWRP: https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Item 5 in the list.

tnsmani said:
Try with eng.stk's TWRP: https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Item 5 in the list.
Click to expand...
Click to collapse
Gave this a shot. Not booting up again. Goes to blank screen with white notification light.

Update: I've even tried rooting phone and flashing custom rom: Doesn't even go to animation
I've also tried method 1, erased the system via fastboot and reflashed the official OOS 3.1.2. zip file via adb sideload. Still the same result on official zip.

yawarkhalid said:
Update: I've even tried rooting phone and flashing custom rom: Doesn't even go to animation
I've also tried method 1, erased the system via fastboot and reflashed the official OOS 3.1.2. zip file via adb sideload. Still the same result on official zip.
Click to expand...
Click to collapse
If Method 2 doesn't work, Method 1 will definitely not work.
After flashing TWRP, are you able to boot to it (without flashing any ROM)? Flashing OOS or Open Beta will overwrite TWRP. So try this: wipe everything and flash TWRP, boot to TWRP and flash ROM and again TWRP, then flash Magisk and boot to system.
When you get white LED, hold power button for 7 to 10 seconds, it will switch off. Then press power button again and you will boot to the options menu to choose bootloader, recovery etc. You may not have to use Method 2 every time if this works for you.

tnsmani said:
If Method 2 doesn't work, Method 1 will definitely not work.
After flashing TWRP, are you able to boot to it (without flashing any ROM)? Flashing OOS or Open Beta will overwrite TWRP. So try this: wipe everything and flash TWRP, boot to TWRP and flash ROM and again TWRP, then flash Magisk and boot to system.
When you get white LED, hold power button for 7 to 10 seconds, it will switch off. Then press power button again and you will boot to the options menu to choose bootloader, recovery etc. You may not have to use Method 2 every time if this works for you.
Click to expand...
Click to collapse
Hey thanks for the help. Will give this a shot now. Can you tell me what method I should use to flash magisk?
Also, I am able to access TWRP but when flashing a rom via TWRP it gives me error 7 i.e. can't install this since because it is for OnePlus 3 this device is " ". Also, with method 2 I already have a stock rom installed, I've tried wiping system via fastboot and sideloading another ROM too, that doesn't work.

yawarkhalid said:
Hey thanks for the help. Will give this a shot now. Can you tell me what method I should use to flash magisk?
Also, I am able to access TWRP but when flashing a rom via TWRP it gives me error 7 i.e. can't install this since because it is for OnePlus 3 this device is " ". Also, with method 2 I already have a stock rom installed, I've tried wiping system via fastboot and sideloading another ROM too, that doesn't work.
Click to expand...
Click to collapse
Magisk to be flashed through TWRP.
If you know how, remove this first line from the updater script and then flash it: getprop("ro.build.product") == "OnePlus3" || abort("This package is for "OnePlus3" devices; this is a "" + getprop("ro.build.product") + ""."); This is what is preventing TWRP from flashing the ROM. Removing this line will result in no checks for device type while flashing the ROM.

tnsmani said:
Magisk to be flashed through TWRP.
If you know how, remove this first line from the updater script and then flash it: getprop("ro.build.product") == "OnePlus3" || abort("This package is for "OnePlus3" devices; this is a "" + getprop("ro.build.product") + ""."); This is what is preventing TWRP from flashing the ROM. Removing this line will result in no checks for device type while flashing the ROM.
Click to expand...
Click to collapse
Hi, already did that, still is't flashing.
Lastly, I managed to lock my bootloader now somehow by running the 3.0.8 version of the MSMTool. Now I have no working OS, A locked bootloader and no way to flash TWRP. I should should throw my phone in the garbage now. Shouldnt I? :crying:

yawarkhalid said:
Hi, already did that, still is't flashing.
Lastly, I managed to lock my bootloader now somehow by running the 3.0.8 version of the MSMTool. Now I have no working OS, A locked bootloader and no way to flash TWRP. I should should throw my phone in the garbage now. Shouldnt I? :crying:
Click to expand...
Click to collapse
NEVER GIVE UP, atleast not so soon. Contact OnePlus and ask them for a remote session, they may be able to restore it.
Though you are not able to flash TWRP, you can boot TWRP by using the adb command "fastboot boot twrp.img" and then play with it. Place the TWRP within the adb folder while trying this. (Replace twrp.img with the name of your TWRP or rename your TWRP as twrp.img)
Either you have encryption issues or you have a hardware issue if you are not able to flash anything successfully.
This is the end of my knowledge.

Take a look here:
https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
or here:
https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/

jeffrey268 said:
Take a look here:
https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
or here:
https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/
Click to expand...
Click to collapse
ummm thanks jeffery. But that tool is exactly what i've been using and what isn't working for me in ways i mentioned above. Thanks though.

tnsmani said:
NEVER GIVE UP, atleast not so soon. Contact OnePlus and ask them for a remote session, they may be able to restore it.
Though you are not able to flash TWRP, you can boot TWRP by using the adb command "fastboot boot twrp.img" and then play with it. Place the TWRP within the adb folder while trying this. (Replace twrp.img with the name of your TWRP or rename your TWRP as twrp.img)
Either you have encryption issues or you have a hardware issue if you are not able to flash anything successfully.
This is the end of my knowledge.
Click to expand...
Click to collapse
Gives me the error, "Unlock device to use this command"
I am able to flash rom via MSMTool, it even dash charges and all. But I can't boot into the system. It gets stuck in OOS animation while booting. Been at it for 3 days. Can it really be a hardware issue if my bootloader and recovery both are working?
Lastly, do you have any way I could unlock the bootloader without system permissions?

Putting an end to this madness. after 4 days in front of my laptop. Had a remote session with a OnePlus tech support team. Discarding my phone unfortunately. Thinking of shifting to a Xiaomi Redmi Note 5 Pro since I can't afford a OnePlus 5T anymore. Thanks to everyone who helped. This thread can be closed now.

Unable to Install any custom rom.

So I've been following DavidRocher's tutorial to install a custom rom (the one that's linked around here the most), I've followed it before installing his RR official rom but as the room started showing a lot of issues, I decided to wipe everything and install something a little more stable such as lineage. I didn't care for Gcam or etc so I wouldn't have minded not having those at all.
However, even after following these steps now once again, even flashing the stock rom as asked for a brand new, clean install, twrp (offain) is hitting me with Error 1s on *any* custom rom that I try installing. I can seemingly flash the stock rom without any issues, but anything else and it's a solid no from TWRP.
Am I missing something?
The error itself is Error applying update: 28 (ErrorCode:: kDownloadOperationExecutionError) Updater process ended with Error: 1 error installing zip file.
I've been wiping, booting, rebooting, re-installing the custom rom, checking the unlocked bootloader and I have had no progress at all. I do not know why this is happening, could anyone please help me?

So, I found out that the -only- rom I can install is the one I originally installed, DavidRocher's official RR which seems to be no longer maintained. Which is also the rom I'm trying to get rid of... This doesn't sem to make any sense, does anyone have -any advice- at all?

JumboTSB said:
So, I found out that the -only- rom I can install is the one I originally installed, DavidRocher's official RR which seems to be no longer maintained. Which is also the rom I'm trying to get rid of... This doesn't sem to make any sense, does anyone have -any advice- at all?
Click to expand...
Click to collapse
Please can you describe exactly the steps that you did from boot to recovery and so?

SubwayChamp said:
Please can you describe exactly the steps that you did from boot to recovery and so?
Click to expand...
Click to collapse
Steps followed were:
Flashing stock daisy_global_images_V10.0.3.0.PDLMIXM_9.0 (flash_all.bat from bigota.d.miui.com/V10.0.3.0.PDLMIXM/daisy_global_images_V10.0.3.0.PDLMIXM_20190114.0000.00_9.0_e8d8d4a6d0.tgz)
Turning the phone off after it booted successfully;
Turning it on in fastboot;
Booting offain's twrp-daisy-3.3.0-0-offain.img through fastboot (fastboot boot twrp-daisy-3.3.0-0-offain.img);
No password entered;
Format Data;
Pushing custom rom & twrp;
Attempting to flash custom rom in any of the slots. At this point, it fails and gives me the error on any rom except the official Resurrection Remix rom from DavidRocher, which I can successfully install alongside twrp and force encryption disabler, change slots, install gapps and magisk and boot.
*Any* other rom just fails with that specific error code.

JumboTSB said:
Steps followed were:
Flashing stock daisy_global_images_V10.0.3.0.PDLMIXM_9.0 (flash_all.bat from bigota.d.miui.com/V10.0.3.0.PDLMIXM/daisy_global_images_V10.0.3.0.PDLMIXM_20190114.0000.00_9.0_e8d8d4a6d0.tgz)
Turning the phone off after it booted successfully;
Turning it on in fastboot;
Booting offain's twrp-daisy-3.3.0-0-offain.img through fastboot (fastboot boot twrp-daisy-3.3.0-0-offain.img);
No password entered;
Format Data;
Pushing custom rom & twrp;
Attempting to flash custom rom in any of the slots. At this point, it fails and gives me the error on any rom except the official Resurrection Remix rom from DavidRocher, which I can successfully install alongside twrp and force encryption disabler, change slots, install gapps and magisk and boot.
*Any* other rom just fails with that specific error code.
Click to expand...
Click to collapse
Try after to reboot to recovery, before of doing nothing or flash anything:
- Flash the TWRP installer.
- Then Wipe cache/dalvik, system and data
- Then Format data.
- Then change slot and reboot to recovery again.
- Now try to follow the usual steps by flashing rom, TWRP, changing slot, etc.
- If didn´t work change the place where it is the rom, extSDCard instead of internal memory or instead adb sideload.

SubwayChamp said:
Try after to reboot to recovery, before of doing nothing or flash anything:
- Flash the TWRP installer.
- Then Wipe cache/dalvik, system and data
- Then Format data.
- Then change slot and reboot to recovery again.
- Now try to follow the usual steps by flashing rom, TWRP, changing slot, etc.
- If didn´t work change the place where it is the rom, extSDCard instead of internal memory or instead adb sideload.
Click to expand...
Click to collapse
Attempted the following steps and adb sideload, error apparently still persists, sadly. This is just... So weird. It doesn't make any sense at all, maybe the official RR altered the partition sizes in some manner? I tried resizing/repairing them through TWRP and it also didn't change anything... ****.

JumboTSB said:
Attempted the following steps and adb sideload, error apparently still persists, sadly. This is just... So weird. It doesn't make any sense at all, maybe the official RR altered the partition sizes in some manner? I tried resizing/repairing them through TWRP and it also didn't change anything... ****.
Click to expand...
Click to collapse
The message through TWRP still the same? Try erasing boot partition where is allocated TWRP through
Code:
fastboot erase boot
then boot to offain TWRP, flash other recovery like Orange and see if this recovery can flash the rom and later flash again TWRP through Orange I don´t think that RR did that so I flashed both versions on my device and I don´t have this issue but if you sometime resized your partition I don´t guess that TWRP can restore it well, you could resize it again through the same method.

SubwayChamp said:
The message through TWRP still the same? Try erasing boot partition where is allocated TWRP through
Code:
fastboot erase boot
then boot to offain TWRP, flash other recovery like Orange and see if this recovery can flash the rom and later flash again TWRP through Orange I don´t think that RR did that so I flashed both versions on my device and I don´t have this issue but if you sometime resized your partition I don´t guess that TWRP can restore it well, you could resize it again through the same method.
Click to expand...
Click to collapse
I guess I'll try it with orange when I have a little more time then.. Spent the last 10-12 hours trying different procedures with twrp and they were pretty fruitless... It's still so weird, I'm definitely not new to flashing roms, I've done it so many times in the past and this is the very first time I get this sort of behavior. I'll update this once I try out OrangeFox.

hi!
your method has always worked for me, but this time I always get error 1.
I tried to install the pixel experience and lineage and nothing works, can you help me?
:good:

Impossible to install custom rom with TWRP

Hi, earlier, I wanted to change the rom of my mi 5s. I've got an error 7 on twrp during the flash. I tried many things: edit the installation script, format all the data, update and downgrade TWRP, and finally perform a fastboot flash using mi flash and the last one worked. But I am not longer able to flash a custom rom without getting error 7 after the "Patching system image unconditionally" message. I've tested lineage, havoc, pixel experience, miui, even 8.1 rom but same result. I'm stuck with fastboot global miui 10
Btw, I think that after the error the partition are corrupted since I can't repair them with TWRP.
I don't know what I can do more.
edit: I tried to lock and relock bootlander, still geting the same error. I'm stuck on Oreo

bob_bricoleur said:
Hi, earlier, I wanted to change the rom of my mi 5s. I've got an error 7 on twrp during the flash. I tried many things: edit the installation script, format all the data, update and downgrade TWRP, and finally perform a fastboot flash using mi flash and the last one worked. But I am not longer able to flash a custom rom without getting error 7 after the "Patching system image unconditionally" message. I've tested lineage, havoc, pixel experience, miui, even 8.1 rom but same result. I'm stuck with fastboot global miui 10
Btw, I think that after the error the partition are corrupted since I can't repair them with TWRP.
I don't know what I can do more.
edit: I tried to lock and relock bootlander, still geting the same error. I'm stuck on Oreo
Click to expand...
Click to collapse
I think that i figured out something, I am able to flash system.img file using fastboot but I can't flash zip rom using recovery.
As anyone encounter this ?

Did you try reflash twrp latest version?

Cannot flash any rom ERROR:7 please help !

Sorry for my bad English grammar,
I have stucked in TWRP for all this day, flashed many different roms and got the same message :
"E1001: Failed to update system/vendor image.
Updater process ended with ERROR:7
Error installing zip file '...' "
My base is 11.0.4 xiaomi.eu rom (MIUI 11, Android 10), start flashing 11.0.3 custom rom (MIUI 11, Android 9) and got that ERROR, then flashed Havoc/ASOiP rom, end up with flashing STOCK MIMAX3Global_V11.0.2.0.QEDMIXM on Mi offficial site via TWRP but still no luck, samething.
I have already tried lastest TWRP 3.3.1, 3.2.3, PitchBlack Recovery, and modified Updater-Script aswell (Delete 1st line).
Thank you for your help ! :crying:

Have you tried any of these tips?

Did you tried any android 10 ROMs?
I'm not sure if the downgrade from 10 to 9 is possible at all

I had wiped my system partition at one point and got this as well. Fixed by using the mi flash tool and the full system image (not a twrp / orange fox rom) and then wiped my data partition to get rid of the boot password. I don't know if anti rollback effects 10 to 9. Look into it though. You're looking for a fastboot rom. Just make sure to not "clean and lock". I'm having trouble finding the fastboot rom I found to fix it but it should come in a .tgz file. Good luck

Question Can't resolve error 70 with Gapps

Hello,
I have a Poco F3 wanted to install a custom rom (i have bluetooth problem with Miui rom), but, to install TWRP, I made the mistake with this doing :
"fastboot flash recovery MyTWRP_File.img" :/
I read (too late) that ESPECIALLY we should not do this command on recent devices (with A / B partition) like Poco F3. With this device, we had to type this command :
"fasboot boot MyTWRP_File.img".
Result, I am unable to install the Gapps (including pico), I have an error 70 (not enough storage space available on the system partition).
I tried to do a lot of things and tutorials (formatting and reinstalling an official rom with Mi Flash to try to start from zero).
But my problem still persists, I cannot install Gapps because I have error 70.
Does anyone have a solution for me to fix my mistake?
Thanks in advance.

chtivain said:
Hello,
I have a Poco F3 wanted to install a custom rom (i have bluetooth problem with Miui rom), but, to install TWRP, I made the mistake with this doing :
"fastboot flash recovery MyTWRP_File.img" :/
I read (too late) that ESPECIALLY we should not do this command on recent devices (with A / B partition) like Poco F3. With this device, we had to type this command :
"fasboot boot MyTWRP_File.img".
Result, I am unable to install the Gapps (including pico), I have an error 70 (not enough storage space available on the system partition).
I tried to do a lot of things and tutorials (formatting and reinstalling an official rom with Mi Flash to try to start from zero).
But my problem still persists, I cannot install Gapps because I have error 70.
Does anyone have a solution for me to fix my mistake?
Thanks in advance.
Click to expand...
Click to collapse
Did "fastboot flash recovery MyTWRP_File.img" actually flash TWRP onto Recovery?
It's not your fault, because several websites (like Xiaomi.eu) still list this command, which is outdated, and many people get confused why that doesn't work, including me.
What Custom ROM are you using?
Flashing Stock ROM with Mi Flash wipes the entire phone, including Recovery. I don't know why you still get this error.
Are you sure that error is related to this? I think it may be something else... I mean you used Mi Flash.

Hi,
Currently, I am back under the stock rom of the Poco F3 (miui global 12.5.3), which I installed with miflash after doing a full wipe.
Before that, i tried the official roms of Lineage and ArrowOS.
with both rom i had the same problem. An error 70, when I flash the Gapps under their respective reecovery.
I tried with the twrp recovery, but I have the same problem

chtivain said:
Hi,
Currently, I am back under the stock rom of the Poco F3 (miui global 12.5.3), which I installed with miflash after doing a full wipe.
Before that, i tried the official roms of Lineage and ArrowOS.
with both rom i had the same problem. An error 70, when I flash the Gapps under their respective reecovery.
I tried with the twrp recovery, but I have the same problem
Click to expand...
Click to collapse
TWRP allows you to save Recovery log for further analysis. Can you upload it here?

dreamytom said:
TWRP allows you to save Recovery log for further analysis. Can you upload it here?
Click to expand...
Click to collapse
I'll put it tomorow (phone call => need to go to work now :/ ).

Did you solve the Problem? Because i got the Same Problem. No matter how i Install twrp. Using Fastboot Boot twrp.img, or flash Boot twrp.img. System Partition is to small and need to be resized.

Got the same thing, cannot Install GApps, errpr 70. What can I do?