Database Users

[OP5, encrypted] Open Beta 3 broke my display!

Tried to flash OB3 and SuperSu on my encrypted OP5 with TWRP. Was stuck at OP logo.
Tried to go back to stable Oreo build for OP5. Again, was stuck at OP logo.
Now the screen is unresponsive in TWRP (can't even swipe to allow modifications on the first screen!).
If I install stock recovery, I can navigate recovery with buttons. I tried installing OOS 5 with stock recovery from internal storage. It doesn't work. I tried to adb sideload. The computer throws a bad_alloc error.
Anyone in the same boat, or good enough to advice?

pentruexperiment said:
Tried to flash OB3 and SuperSu on my encrypted OP5 with TWRP. Was stuck at OP logo.
Tried to go back to stable Oreo build for OP5. Again, was stuck at OP logo.
Now the screen is unresponsive in TWRP (can't even swipe to allow modifications on the first screen!).
If I install stock recovery, I can navigate recovery with buttons. I tried installing OOS 5 with stock recovery from internal storage. It doesn't work. I tried to adb sideload. The computer throws a bad_alloc error.
Anyone in the same boat, or good enough to advice?
Click to expand...
Click to collapse
but u'll lost your data
i had this too, you need to flash stock recovery from cmd in yor pc by:
"fastboot flash recovery recovery_name.img"
then wipe everything,
reboot again into recovery
click on adb
and then download the stable firmware oreo 5
in adb mode with stock recovery put firmware in the same folder
and input - adb sideload name_of_firmware.zip
That fixed my phone, i'll hope and yours will be fixed

sk.c0de said:
but u'll lost your data
i had this too, you need to flash stock recovery from cmd in yor pc by:
"fastboot flash recovery recovery_name.img"
then wipe everything,
reboot again into recovery
click on adb
and then download the stable firmware oreo 5
in adb mode with stock recovery put firmware in the same folder
and input - adb sideload name_of_firmware.zip
That fixed my phone, i'll hope and yours will be fixed
Click to expand...
Click to collapse
Thanks,
The device is recognized well by the computer (when I write 'adb devices'). But when I try to sideload ('adb sideload OOS5.zip'), it gives me an error with bad_alloc. any ideas?

pentruexperiment said:
Thanks,
The device is recognized well by the computer (when I write 'adb devices'). But when I try to sideload ('adb sideload OOS5.zip'), it gives me an error with bad_alloc. any ideas?
Click to expand...
Click to collapse
Try unbrick method I think it's the quickest way to get back your device.

How to flash a custom rom in stock pie as base. tUtORIAL

How to flash a custom rom in stock pie as base,using adb sideload
The twrp still does not work well in android 9 just the adb sideload function in twrp's advanced options.
First make sure you have the bootloader unlocked.
Second put all the files need in adb past rom kernel magisk etc...
1-put the mobile phone in fastboot mode
2-Boot twrp through adb using the command bellow
fastboot boot TWRP-3.2.3-jasmine-20181201.img
donwload twrp https://t.me/XiaomiMiA1ClouD/810
3- Make format data and make all wipes in the 2 slots
4-now go twrp advanced option and turn on adb sideload
5-for example for flash last pixel rom gapps included you use this adb comand
adb sideload PixelExperience_jasmine-9.0-20181219-0813-OFFICIAL.zip
6-reboot to bootloader and boot twrp again
7- check slots in twrp if on a change to b
8- reboot to sys done !!!
note:
9- you can flash magisk using same method
adb sideload magisk.zip

I will update the post for How to update a custom ROM after an update.
Sent from my Poco F1 beryllium using Tapatalk Pro

"3- Make format data and make all wipes in the 2 slots"
What u mean by that 2 slots? should I have to go to twrp and format & wipe A partition then change to B then format & wipe? after 2 slots/2partitions again back to A then adb sideload on?

hugor671 said:
How to flash a custom rom in stock pie as base,using adb sideload
note:
9- you can flash magisk using same method
adb sideload magisk.zip
Click to expand...
Click to collapse
when do we do this step ?

xxqxpxx said:
when do we do this step ?
Click to expand...
Click to collapse
Yes

xxqxpxx said:
when do we do this step ?
Click to expand...
Click to collapse
After installing the gapps Or after booting once to rom and then back to twrp

When flashing magisk and hex by adb method, next we change slot like flashing the rom?
Flash magisk/hex/gapps by adb
Changing slot
Reboot
Like that?

Is it possible to install twrp if my phone is on Android 9 ?
If yes how to do it?
Thanks in avance

hugor671 said:
How to flash a custom rom in stock pie as base,using adb sideload
Click to expand...
Click to collapse
Please make a tutorial on how to revert back to stock ROM.

[email protected] said:
Please make a tutorial on how to revert back to stock ROM.
Click to expand...
Click to collapse
Yes I also want

razahaider03 said:
Yes I also want
Click to expand...
Click to collapse
I think we can use Xiaomi MiFlashTool or extract the fastboot rom and install in bootloader using fastboot commands

satti8893 said:
I think we can use Xiaomi MiFlashTool or extract the fastboot rom and install in bootloader using fastboot commands
Click to expand...
Click to collapse
I can't do that 0s succeed but nothing happened

when i try to boot in twrp via fastboot the it boots in twrp (the pc recognize the phone as mtp devices) but the screen remains black. any solution? (i was on stock pie)

Mw too when i try to boot in twrp via fastboot the it boots in twrp it say okay but just black screen...

[GUIDE] Flashing ROMs with TWRP black screen

Hello,
Many people report, that their TWRP/PBRP is black and they can't install custom ROM or flash stock ROM by recovery.
Problem occurs in devices with Jdi display.
It is recommended to flash Oreo, then recovery work, but if you want use Android Pie you must be on this stock firmware (I tried Oreo and flash Havoc (Pie) = bootloop).
We need:
Unlocked bootloader
Turned on android debugging
ADB (minimum 1.4.3)
TWRP/PBRP (.img file)
ROM, GAPPS,...
YOUR DATA/PHOTOS/DOWNLOADS WILL BE REMOVED, SO MAKE A BACKUP!
Let's get started:
1. FLASHING ROM
/the phone is on/
1. Use cmd and type: adb reboot-bootloader
<phone will turn on in fastboot mode>
2. Type: fastboot set_active b
Then: fastboot boot <your_recovery.img>, e.g. fastboot boot twrp.img
<phone will reboot, the screen will be black>
<wait to Windows new device sound>
3. Type: adb shell
twrp wipe cache
twrp wipe dalvik
twrp wipe system
twrp wipe data <- NOW YOUR DATA WILL BE REMOVED, SO MAKE A BACKUP BEFORE!
twrp sideload
adb sideload <location_of_your_ROM.zip>, e.g. adb sideload C:\Havoc.zip
When the installation is completed you will see "Total xfer X.XXx".
2. FLASHING GAPPS
Now: adb reboot-bootloader
<phone will turn on in fastboot mode>
fastboot set_active a
fastboot boot <your_recovery.img>, e.g. fastboot boot twrp.img
<phone will reboot, the screen will be black>
<wait to Windows new device sound>
adb shell
twrp wipe cache
twrp wipe dalvik
twrp sideload
adb sideload <location_of_your_GApps.zip>, e.g. adb sideload C:\GApps.zip
When the installation is completed you will see "Total xfer X.XXx".
3. FLASHING PATCHED BOOT IMAGE (MAGISK + ROOT)
adb reboot-bootloader
fastboot flash boot <your_patched_boot.img>, e.g. fastboot flash patched_boot.img
fastboot reboot
<phone will start, the first start may take some time>
It's instruction for performing these three steps sequentially.
System will be installed on slot B, the Gapps and patched boot on slot A.
Now you can enjoy custom ROM
Greetings

Flash999 said:
Hello,
Many people report, that their TWRP/PBRP is black and they can't install custom ROM or flash stock ROM by recovery.
Problem occurs in devices with Jdi display.
It is recommended to flash Oreo, then recovery work, but if you want use Android Pie you must be on this stock firmware (I tried Oreo and flash Havoc (Pie) = bootloop).
We need:
Unlocked bootloader
Turned on android debugging
ADB (minimum 1.4.3)
TWRP/PBRP (.img file)
ROM, GAPPS,...
YOUR DATA/PHOTOS/DOWNLOADS WILL BE REMOVED, SO MAKE A BACKUP!
Let's get started:
1. FLASHING ROM
/the phone is on/
1. Use cmd and type: adb reboot-bootloader
<phone will turn on in fastboot mode>
2. Type: fastboot set_active b
Then: fastboot boot <your_recovery.img>, e.g. fastboot boot twrp.img
<phone will reboot, the screen will be black>
<wait to Windows new device sound>
3. Type: adb shell
twrp wipe cache
twrp wipe dalvik
twrp wipe system
twrp wipe data <- NOW YOUR DATA WILL BE REMOVED, SO MAKE A BACKUP BEFORE!
twrp sideload
adb sideload <location_of_your_ROM.zip>, e.g. adb sideload C:\Havoc.zip
When the installation is completed you will see "Total xfer X.XXx".
2. FLASHING GAPPS
Now: adb reboot-bootloader
<phone will turn on in fastboot mode>
fastboot set_active a
fastboot boot <your_recovery.img>, e.g. fastboot boot twrp.img
<phone will reboot, the screen will be black>
<wait to Windows new device sound>
adb shell
twrp wipe cache
twrp wipe dalvik
twrp sideload
adb sideload <location_of_your_GApps.zip>, e.g. adb sideload C:\GApps.zip
When the installation is completed you will see "Total xfer X.XXx".
3. FLASHING PATCHED BOOT IMAGE (MAGISK + ROOT)
adb reboot-bootloader
fastboot flash boot <your_patched_boot.img>, e.g. fastboot flash patched_boot.img
fastboot reboot
<phone will start, the first start may take some time>
It's instruction for performing these three steps sequentially.
System will be installed on slot B, the Gapps and patched boot on slot A.
Now you can enjoy custom ROM
Greetings
Click to expand...
Click to collapse
Work well.. buuuut.... i think tha hard drive of phone is encrypted... and inwritable, so... works! but is not functional

Wormboymx said:
Work well.. buuuut.... i think tha hard drive of phone is encrypted... and inwritable, so... works! but is not functional
Click to expand...
Click to collapse
The data partition is encrypted. If you want to access this partition you have to format it by TWRP. When you start system with forced encryption, the data will be again encrypted (or use custom ROM without encryption or install script to disable it on stock software).

Flash999 said:
The data partition is encrypted. If you want to access this partition you have to format it by TWRP. When you start system with forced encryption, the data will be again encrypted (or use custom ROM without encryption or install script to disable it on stock software).
Click to expand...
Click to collapse
Ok, can you help me with that? I think with you excellent guide maybe is missing one step to avoid this.
Thanks!

Wormboymx said:
Ok, can you help me with that? I think with you excellent guide maybe is missing one step to avoid this.
Thanks!
Click to expand...
Click to collapse
I had a similar problem while using twrp to copy files to the phone storage, try this command before doing anything:
fastboot -w
Note: This wipes all data.
This made the phone storage accessible.

mma_1494 said:
I had a similar problem while using twrp to copy files to the phone storage, try this command before doing anything:
fastboot -w
Note: This wipes all data.
This made the phone storage accessible.
Click to expand...
Click to collapse
Doesn´t work too =(
"fastboot -w
wiping userdata...
CreateProcess failed: El sistema no puede encontrar el archivo especificado. (2)
error: Cannot generate image for userdata"
i Will back to stock rom Pie...
P.D. the encryption is when finishi whole process in the installed custom rom the hard drive doesn't work e.g... Open the camera and system say "Don't have sd card to save the files"

where will get patched_boot.img for mi a2 10.0.2 or 10.0.4
where will get patched_boot.img for mi a2 10.0.2 or 10.0.4

asad0181 said:
where will get patched_boot.img for mi a2 10.0.2 or 10.0.4
Click to expand...
Click to collapse
On this Youtube channel https://www.youtube.com/channel/UCuEtuySiR1DDYCRerutqvnA/videos
You can get some files...

Hello! How do I know if my device has a Jdi display panel? If it does have, do I need to follow this guide every time I flash or update a rom?

chrisdlc119 said:
Hello! How do I know if my device has a Jdi display panel? If it does have, do I need to follow this guide every time I flash or update a rom?
Click to expand...
Click to collapse
Try to boot TWRP on Pie, if you see TWRP GUI mean you don't have Jdi display. You don't have to flash anything, only boot by fastboot.
It depends of your ROM and system updater, I follow the guide to flash new version and all is working ok.

Flash999 said:
Try to boot TWRP on Pie, if you see TWRP GUI mean you don't have Jdi display. You don't have to flash anything, only boot by fastboot.
It depends of your ROM and system updater, I follow the guide to flash new version and all is working ok.
Click to expand...
Click to collapse
I think my display is tianman (ss atached). Is that right? Do you know if any display is affected with burning effect? It's just that I had a RN5 and I changed from MIUI to a custom ROM and one day the display just got the burning effect
Thanks for your reply.

Wormboymx said:
Doesn´t work too =(
"fastboot -w
wiping userdata...
CreateProcess failed: El sistema no puede encontrar el archivo especificado. (2)
error: Cannot generate image for userdata"
i Will back to stock rom Pie...
Click to expand...
Click to collapse
I'm getting the same error when doing fastboot -w, and the ROM I flashed (Resurrection Remix) is stuck on startup splash screen.
Any idea what can cause this, and how I can recover?

mma_1494 said:
I had a similar problem while using twrp to copy files to the phone storage, try this command before doing anything:
fastboot -w
Note: This wipes all data.
This made the phone storage accessible.
Click to expand...
Click to collapse
Thanks! Now I could install Havoc and have access to my files!
Op you should include ,,fastboot -w" in your guide.

Finally i can boot PitchBlack recovery without Blackscreen in JDI panels::
Boot this recovery file: https://sourceforge.net/projects/pitchblack-twrp/files/jasmine_sprout/
Only one difference between the guide of this Thread....
I can´t change the partitions in PitchBlack recovery... i used the command in the op to change the partitions.... NOW i can flashed the Resurection remix rom in my phone

hlg1 said:
I'm getting the same error when doing fastboot -w, and the ROM I flashed (Resurrection Remix) is stuck on startup splash screen.
Any idea what can cause this, and how I can recover?
Click to expand...
Click to collapse
So, I was able to recover from this by using Xiaomi Flash Tool (v20170425) to flash the V10.0.7.0 stock rom. That got me back to a working stock Android.
I then retried the steps from this guide (except Gapps and patched boot), and this time I was able to get my Resurrection Remix started. However, the userdata file structure looks like rubbish, and none of the apps can write to or read from it. I tried to do a factory reset (from within custom rom) to fix this, but then the phone turned off and would not boot to custom rom again. fastboot -w still doesn't work.
Any ideas how to make the userdata partition great again?

hlg1 said:
So, I was able to recover from this by using Xiaomi Flash Tool (v20170425) to flash the V10.0.7.0 stock rom. That got me back to a working stock Android.
I then retried the steps from this guide (except Gapps and patched boot), and this time I was able to get my Resurrection Remix started. However, the userdata file structure looks like rubbish, and none of the apps can write to or read from it. I tried to do a factory reset (from within custom rom) to fix this, but then the phone turned off and would not boot to custom rom again. fastboot -w still doesn't work.
Any ideas how to make the userdata partition great again?
Click to expand...
Click to collapse
I made it work by doing the first 2 steps from the OP and then after booting into system the first time I booted into bootloader and then used fastboot -w. I did this with Havoc OS though so it might not work for everyone.
When I wanted root and didn't know how to get a patched boot image for my ROM, I just followed the steps to access TWRP through ADB again and then wiped cache and dalvik, afterwards I used the sideload command to flash Magisk on my phone.

hlg1 said:
Any ideas how to make the userdata partition great again?
Click to expand...
Click to collapse
I eventually figured out that all my problems occurred because I was using old versions of ADB and fastboot. After updating to latest platform-tools (currently r28.0.2) I was able to run fastboot -w without problems. And once that worked I was able to set up a fully working system following the steps of this guide.
Thanks for a very useful guide, it saved my day!

i got failed command write failed. any suggestion?

I was also having the black screen problem
Can i flash twrp recovery while keeping the stock rom? If can sombody please help me

Sarath_sh said:
I was also having the black screen problem
Can i flash twrp recovery while keeping the stock rom? If can sombody please help me
Click to expand...
Click to collapse
I'm not entirely sure I understand your question, but please note that by following the OP instructions you never flash TWRP, you just boot right into it from RAM. So should be no problem to do that while keeping stock ROM.

flashing oneplus one

howto flash the one without working volume controls??
is this possible?

Yes, it is possible. LineageOS has an option to boot to recovery or fastboot via the standard reboot dialogue.
You can also use adb commands "adb reboot recovery" or "adb reboot fastboot".

kekerosberg said:
Yes, it is possible. LineageOS has an option to boot to recovery or fastboot via the standard reboot dialogue.
You can also use adb commands "adb reboot recovery" or "adb reboot fastboot".
Click to expand...
Click to collapse
thanks for the reply. is there any manual to do so?
for im´m an absolute newbie on this. adb and faastboot are installed on my ubuntu machine.

Depends on what you are trying to accomplish.
Flash TWRP recovery? You may also use LineageOS recovery instead of TWRP if you want. Follow their instructions https://twrp.me/oneplus/oneplusone.html
Flash LineageOS? Follow the wiki instructions https://wiki.lineageos.org/devices/bacon/install
Beware that unlocking the bootloader will erase all data on the phone.

kekerosberg said:
Yes, it is possible. LineageOS has an option to boot to recovery or fastboot via the standard reboot dialogue.
You can also use adb commands "adb reboot recovery" or "adb reboot fastboot".
Click to expand...
Click to collapse
yes i tried but failed because in the last step i had to reboot in recovery with the volume control and start button, because at that point iḿ in fastboot mode and adb reboot recovery won work?!

yes i tried but i failed because in the last step i had to reboot in recovery with the volume control and start button, because at that point i'm in fastboot mode and adb reboot recovery won't work?!

While in fastboot mode, you may boot into recovery using "fastboot reboot recovery". Almost there, good luck!

kekerosberg said:
While in fastboot mode, you may boot into recovery using "fastboot reboot recovery". Almost there, good luck!
Click to expand...
Click to collapse
doesn't work on my ubuntu machine. "unkown rebbot target recvery..
i tried .guess i check it on my win machine.

You can also reboot to recovery from within the OS by using "adb reboot recovery". It should work if you were able to reboot to fastboot using this method.

unfortunately it does not work while being in fastboot mode.
adb says device 'null'not found..

Yes, you are supposed to use adb from whatever OS you have installed, CM, CyanogenOS, LOS, ...

but?
is flashing possible without being in fastboot mode? just using adb?

I understood that you had already flashed the recovery. Now you need to boot into the recovery to flash an OS.
Fastboot is used to flash the recovery.
Recovery is used to flash the OS.

yes i think that's it and therefore i had to reboot to recovery without working controls..

koeskemc said:
yes i think that's it and therefore i had to reboot to recovery without working controls..
Click to expand...
Click to collapse
any idea?

kekerosberg said:
I understood that you had already flashed the recovery. Now you need to boot into the recovery to flash an OS.
Fastboot is used to flash the recovery.
Recovery is used to flash the OS.
Click to expand...
Click to collapse
yes, and that's my prob how to boot into recovery without using any controls?
or is there another way?e.g adb sideload??

You have a working operating system installed? Cyanogenmod, LineageOS or something similar?
Use the power button to boot into the operating system. Then connect the phone to your PC and "adb reboot recovery".

hello again.
i got a new prob. i've istalled twrp(don know how!)
with terp i imstalled lineage 18.1...zip.
but after booting i alwasy get twrp and not the os.
whats my fault

or do ihavr to istall the .img file??instead of.zip?

hello again,
everything's fine so far. i got lineage os on boot up! but how to get back to twrp again to install gapps??

All Custom ROM installations fail the same way.

I am trying to get a custon ROM to work on my Oneplus 8 Pro (instantnoodlep)
ROMs I tried installing:
Cherish OS 3.9.5
Nameless-AOSP_instantnoodlep-12.1-20220708-0935-Official
What I do:
1. Download recovery provided with the ROM
2. Reboot to bootloader and flash recovery
'fastboot flash recovery recovery.img'
'fastboot reboot recovery'
3. Select apply update/apply from ADB
4. Connect device to PC
5. Sideload rom.zip
'adb sideload rom.zip'
6 Do Factory reset/format data from recovery
7. Restart to system
What happens:
Phone goes to fastboot and stays there.
When I try
fastboot reboot system
or
fastboot reboot recovery
I also land in fastboot again.
The only way to get out of fastboot again is fastboot boot recovery.img, which boots into recovery. When I then reboot into system, my old OOS11 boots up.
Because this is independent of the Custon ROM, there might be another issue. But which one?

You made sure you have latest OOS11 on BOTH slots?

xtcislove said:
You made sure you have latest OOS11 on BOTH slots?
Click to expand...
Click to collapse
Thanks for the response! How do i check that? Both slots of what?

Infraviored said:
Thanks for the response! How do i check that? Both slots of what?
Click to expand...
Click to collapse
When you're booted in OOS 11 just do a local install of the same OOS version that you're on. That will install OOS to the other slot, meaning you'll have the same OOS version on both slots and "should" be able to flash a custom rom.

Infraviored said:
I am trying to get a custon ROM to work on my Oneplus 8 Pro (instantnoodlep)
ROMs I tried installing:
Cherish OS 3.9.5
Nameless-AOSP_instantnoodlep-12.1-20220708-0935-Official
What I do:
1. Download recovery provided with the ROM
2. Reboot to bootloader and flash recovery
'fastboot flash recovery recovery.img'
'fastboot reboot recovery'
3. Select apply update/apply from ADB
4. Connect device to PC
5. Sideload rom.zip
'adb sideload rom.zip'
6 Do Factory reset/format data from recovery
7. Restart to system
What happens:
Phone goes to fastboot and stays there.
When I try
fastboot reboot system
or
fastboot reboot recovery
I also land in fastboot again.
The only way to get out of fastboot again is fastboot boot recovery.img, which boots into recovery. When I then reboot into system, my old OOS11 boots up.
Because this is independent of the Custon ROM, there might be another issue. But which one?
Click to expand...
Click to collapse
U don't need the command fastboot reboot recovery. U can just use the volume buttons to select recovery and press power button to boot to recovery

Nimueh said:
When you're booted in OOS 11 just do a local install of the same OOS version that you're on. That will install OOS to the other slot, meaning you'll have the same OOS version on both slots and "should" be able to flash a custom rom.
Click to expand...
Click to collapse
Another way to set your phone up for a custom rom can be found here. https://wiki.lineageos.org/devices/instantnoodlep/install
Just make sure your booting from a good 00S11 install when you do this.

I had a heck of a time with this two days ago. OP pushed c33, A12 on my phone. It took forever to corrupt both a and b enough to get twrp recovery installed and working to install A11 again. I had to load the recovery on both slots, a and b and I used twrp install to install the OTA to slot a. Right now I have nothing on slot b other that twrp recovery.

king_xerxes said:
I had a heck of a time with this two days ago. OP pushed c33, A12 on my phone. It took forever to corrupt both a and b enough to get twrp recovery installed and working to install A11 again. I had to load the recovery on both slots, a and b and I used twrp install to install the OTA to slot a. Right now I have nothing on slot b other that twrp recovery.
Click to expand...
Click to collapse
Sorted it out by this. Thank you!