Develop Bugs

Recovering Possibly Bricked OnePlus 3

Hi Everyone,
Does anyone have any instructions as of right now on how to recover a potentially bricked OnePlus 3? Doing some googling around yielded me to the conclusion that my OnePlus 3 bricked itself.
Thanks!

ManagerJosh said:
Hi Everyone,
Does anyone have any instructions as of right now on how to recover a potentially bricked OnePlus 3? Doing some googling around yielded me to the conclusion that my OnePlus 3 bricked itself.
Thanks!
Click to expand...
Click to collapse
do you have fastboot on your device???
can u enter fast boot by key combination vol down and power???
if yes then just install twrp recovery or stock recovery with following command
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
flash cm 13, beanstock,tipsy or RR rom if you use twrp
flash stock firmware if you use stock recovery

ManagerJosh said:
Hi Everyone,
Does anyone have any instructions as of right now on how to recover a potentially bricked OnePlus 3? Doing some googling around yielded me to the conclusion that my OnePlus 3 bricked itself.
Thanks!
Click to expand...
Click to collapse
Contact support.... you're the first one with a bricked device....
And it would be great if you could share the support e-mail.... it would help me get unbrick files for this device
---------- Post added at 22:17 ---------- Previous post was at 22:16 ----------
i.snehal.kiran said:
do you have fastboot on your device???
can u enter fast boot by key combination vol down and power???
if yes then just install twrp recovery or stock recovery with following command
flash cm 13, beanstock,tipsy or RR rom if you use twrp
flash stock firmware if you use stock recovery
Click to expand...
Click to collapse
Fastboot on op2 is already a mess and we don't have enough info of what could happen in op3... best avoid fastboot except for flashing twrp
Flash the stock ROM through twrp

ManagerJosh said:
Hi Everyone,
Does anyone have any instructions as of right now on how to recover a potentially bricked OnePlus 3? Doing some googling around yielded me to the conclusion that my OnePlus 3 bricked itself.
Thanks!
Click to expand...
Click to collapse
Your oneplus bricked itself?
are you sure there wasn't a human involved in the process?
As other people says, you're the first one with a " bricked" device, so please tell everyone what your device status is, and how it got bricked.
did you unlock bootloader, did you have root? as much info as possible..

anupritaisno1 said:
Contact support.... you're the first one with a bricked device....
And it would be great if you could share the support e-mail.... it would help me get unbrick files for this device
---------- Post added at 22:17 ---------- Previous post was at 22:16 ----------
Fastboot on op2 is already a mess and we don't have enough info of what could happen in op3... best avoid fastboot except for flashing twrp
Flash the stock ROM through twrp
Click to expand...
Click to collapse
I already have the link for that file. Someone shared. But, what next ?
Sent from my OnePlus2 using XDA Labs

anupritaisno1 said:
Fastboot on op2 is already a mess...
Click to expand...
Click to collapse
Why a mess?
Fastboot itself is very simple.
fastboot flash <<partition you need to flash>> <<file patch>>.
Is it different from the "common" fastboot we can find on a Nexus?

When I try to do this I get the following message:
target reported max download size of 536870912 bytes
sending 'recovery' (18677 KB)...
OKAY [ 0.568s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.590s
Any way I can force this to happen?
Thanks in advance

CyberCROC said:
When I try to do this I get the following message:
target reported max download size of 536870912 bytes
sending 'recovery' (18677 KB)...
OKAY [ 0.568s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.590s
Any way I can force this to happen?
Thanks in advance
Click to expand...
Click to collapse
You did 'fastboot oem unlock' first, correct?

I tried yes but that results in the following:
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.011s

CyberCROC said:
I tried yes but that results in the following:
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.011s
Click to expand...
Click to collapse
And have you enabled OEM Unlocking in Developer Options ?
BTW Please reply to my PM ASAP if possible.
Thanks.
Best Regards,
Naman.

I can't OEM unlock in developer options as I no longer have access to my device
PM answered

Experiencing the same problem here.

I had the same in other thread. OEM unock was disabled. Do You have working stock recovery or TWRP? If stock works You can flash stock rom by ADB sideload.

My bootloader is locked so it's showing FAILED (remote: Partition flashing is not allowed) and cannot get into recovery.

cepheid46e2 said:
My bootloader is locked so it's showing FAILED (remote: Partition flashing is not allowed) and cannot get into recovery.
Click to expand...
Click to collapse
I am experiencing the same problem right now. Cannot boot into recovery mode or flash something...stuck in fastboot mode. .
Any ideas?

I have the same problem too
sino84 said:
I am experiencing the same problem right now. Cannot boot into recovery mode or flash something...stuck in fastboot mode. .
Any ideas?
Click to expand...
Click to collapse
Only can acces to fastboot,i can´t write anything ,flash rom,flash recovery
FAILED (remote: Partition flashing is not allowed)
I have TWRP Recovery and my device unlocked and rooted and i want to lock my device and retunrn to stock OS but i make a mistake before flashing stock recovery i lock my OP3 this is the result
I tried
fastboot boot recovery.img
fastboot flash recovery recovery.img
fastboot flash TWRP_recovery TWRP_recovery.img
fastboot oem unlock
fastboot flash zip ota.zip
fastboot format userdata
I tried too to decrypt my op3 with OnePlus3-ToolKit with the same result
FAILED (remote: Partition flashing is not allowed)
I can´t enter to recovery or system
How we can solve it
Thanks

x___treme said:
Only can acces to fastboot,i can´t write anything ,flash rom,flash recovery
FAILED (remote: Partition flashing is not allowed)
I have TWRP Recovery and my device unlocked and rooted and i want to lock my device and retunrn to stock OS but i make a mistake before flashing stock recovery i lock my OP3 this is the result
I tried
fastboot boot recovery.img
fastboot flash recovery recovery.img
fastboot flash TWRP_recovery TWRP_recovery.img
fastboot oem unlock
fastboot flash zip ota.zip
fastboot format userdata
I tried too to decrypt my op3 with OnePlus3-ToolKit with the same result
FAILED (remote: Partition flashing is not allowed)
I can´t enter to recovery or system
How we can solve it
Thanks
Click to expand...
Click to collapse
try this:
http://www.androidbrick.com/unbrick-oneplus-one-two-3-qualcomm-hs-usb-qdloader-9008/

you need the OnePlus3_Unbrick_Tool_Full.rar to unbrick your phone, i was also in your situation,
you need also the Qualcomm_Diag_QD_Loader_2016_driver.exe with this two tools you can flash to restore the OP3
me helped al lot this thread http://forum.xda-developers.com/onep...icked-t3405700
a had a success with this part How to Make the device show as Qualcomm 9008
it is important that you have the correct driver installed on your pc that the phone will be recognized as Qualcomm 9008

I did the exact same stupid thing... locked bootloader before flashing stock recovery.
This post saved me:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I used method 2 in the post which wiped everything but at least i got the phone back.
x___treme said:
Only can acces to fastboot,i can´t write anything ,flash rom,flash recovery
FAILED (remote: Partition flashing is not allowed)
I have TWRP Recovery and my device unlocked and rooted and i want to lock my device and retunrn to stock OS but i make a mistake before flashing stock recovery i lock my OP3 this is the result
I tried
fastboot boot recovery.img
fastboot flash recovery recovery.img
fastboot flash TWRP_recovery TWRP_recovery.img
fastboot oem unlock
fastboot flash zip ota.zip
fastboot format userdata
I tried too to decrypt my op3 with OnePlus3-ToolKit with the same result
FAILED (remote: Partition flashing is not allowed)
I can´t enter to recovery or system
How we can solve it
Thanks
Click to expand...
Click to collapse

ManagerJosh said:
Hi Everyone,
Does anyone have any instructions as of right now on how to recover a potentially bricked OnePlus 3? Doing some googling around yielded me to the conclusion that my OnePlus 3 bricked itself.
Thanks!
Click to expand...
Click to collapse
Since im a new member I cannot post links so ill have to give you directions.
Search google for Hard Bricked OnePlus 3 and it will be the first one called Mega Unbrick guide.
Use method 2. Ive used it multiple times when flashing goes wrong on my oneplus 3.
Another step, download the latest stock recovery from OnePlus and name it recovery.img and replace the one in the folder. You should understand more when you have all of the files.
You can download the latest recovery from OP at the bottom of the page linked here:
Google OnePlus 3 beta download and it should be the first one saying community build.

oxygen OS 4.0 no twrp possible

Installed oxygen OS 4.0 everything seems to become OK
but after flashing twrp 3.0.2 to the phone it is just hanging in a black screen.
I tried several twrp alternatives from XDA: always same result.
After some seconds up to some minutes it is possible to reboot but no twrp has been flashed.
The twrp 3.0.2 works fine in the old version of OS oxygen

RoFrie said:
Installed oxygen OS 4.0 everything seems to become OK
but after flashing twrp 3.0.2 to the phone it is just hanging in a black screen.
I tried several twrp alternatives from XDA: always same result.
After some seconds up to some minutes it is possible to reboot but no twrp has been flashed.
The twrp 3.0.2 works fine in the old version of OS oxygen
Click to expand...
Click to collapse
Hi, you can fix it. Flash OnePlus3_OpenBeta7-FIRMWARE+MODEM-flashable.zip
https://www.androidfilehost.com/?fid=457095661767116249
I use this twrp and works!

You need PC to see youre phone in FASTBOOT. ADB + drivers instaled.
Reboot youre phone in Fastboot (Boot loader), then flash recovery. After flashing reboot to recovery.

sakarya1980 said:
Hi, you can fix it. Flash OnePlus3_OpenBeta7-FIRMWARE+MODEM-flashable.zip
https://www.androidfilehost.com/?fid=457095661767116249
I use this twrp and works!
Click to expand...
Click to collapse
I'd like to know some details before installing:
FIRMWARE+MODEM what is this? Is firmware the whole oxygen OS? Modem is for mobile connection like LTE?
What are the advantages in comparison of using the originals?
Can you give me the origin of the twrp you attached?

null0seven said:
You need PC to see youre phone in FASTBOOT. ADB + drivers instaled.
Reboot youre phone in Fastboot (Boot loader), then flash recovery. After flashing reboot to recovery.
Click to expand...
Click to collapse
I think I did exactly what you described. But nothing in the newly flashed TWRP resulted must in a black screen.

Install the modified TWRP v 3.0.2.1-28. Search in XDA you should find it. Flash it and boot into recovery. I installed it and flashed OOS 4.0 OTA through this recovery. Everything is working fine.

Black screen means you did not flash it.
Open Command Promt. Type:
fastboot flash recovery "recovery".img. (name of the recovery between commas)
reboot bootloader.
reboot to recovery.

Because we don't have any twrp updated to support Nougat oos roms. The ones we have can only read decrypted storage. I'm too waiting for someone to pick up the development and build an updated twrp.

Flashing this one works

null0seven said:
Black screen means you did not flash it.
Open Command Promt. Type:
fastboot flash recovery "recovery".img. (name of the recovery between commas)
reboot bootloader.
reboot to recovery.
Click to expand...
Click to collapse
But the log said the flash was ok:
fastboot flash recovery twrp-3.0.2-1-oneplus3.img
target reported max download size of 440401920 bytes
sending 'recovery' (18964 KB)...
OKAY [ 0.432s]
writing 'recovery'...
OKAY [ 0.160s]
finished. total time: 0.594s
---------- Post added at 12:43 PM ---------- Previous post was at 12:33 PM ----------
mavidser said:
Flashing this one works
Click to expand...
Click to collapse
YES
This one works.
But my phone is encrypted and as written by abhibnl decrypting is not possible right now.

RolfFrie said:
But the log said the flash was ok:
fastboot flash recovery twrp-3.0.2-1-oneplus3.img
target reported max download size of 440401920 bytes
sending 'recovery' (18964 KB)...
OKAY [ 0.432s]
writing 'recovery'...
OKAY [ 0.160s]
finished. total time: 0.594s
---------- Post added at 12:43 PM ---------- Previous post was at 12:33 PM ----------
YES
This one works.
But my phone is encrypted and as written by abhibnl decrypting is not possible right now.
Click to expand...
Click to collapse
Yeah, I noticed that too, after writing the comment.
For me though, I only needed to create the Nandroid backup and flash SuperSU, so I flashed the recovery, cancelled the decryption, formatted the data (removing the encryption), adb push'd the zip and installed it.
Any idea how I can turn the encryption back on now?

@RoFrie I originally had the same problem as you but with the difference that my phone was on OOS 3.2.8 and it upgrade to N. after that I tried TWRP but the phone would replace it every time I rebooted. Once I got the right TWRP I can boot to it but the internal drive was encrypted so TWRP was useless. I said forget this crap I'm going back to CM14.1. And as always I felt that I had to get this done. So once on CM14.1 I used TWRP to switch the file system to s2fs flash OOS3.2.8 than I let it do the upgrade yet again. This time when I flashed the TWRP .28 the phones was no longer encrypted,I rooted than its all good now.
Sent from my ONEPLUS A3000 using Tapatalk

What was the file?

RolfFrie said:
But the log said the flash was ok:
fastboot flash recovery twrp-3.0.2-1-oneplus3.img
target reported max download size of 440401920 bytes
sending 'recovery' (18964 KB)...
OKAY [ 0.432s]
writing 'recovery'...
OKAY [ 0.160s]
finished. total time: 0.594s
---------- Post added at 12:43 PM ---------- Previous post was at 12:33 PM ----------
YES
This one works.
But my phone is encrypted and as written by abhibnl decrypting is not possible right now.
Click to expand...
Click to collapse
You need the unreleased beta twrp. Encrypted and rooted OOS 4.0.3 here
Sent from my ONEPLUS A3000 using Tapatalk

i want to go back stock recovery and relock the bootloader

Plss help me i unlocked the bootloader and installed twrp after that my system app deleted like Huawei care and not applying themes and font i formated the phone but not worked i wamt to go back on nougt or oreo beta rom currently twrp working fine pls help me my model number is bnd al10

moinkazi said:
Plss help me i unlocked the bootloader and installed twrp after that my system app deleted like Huawei care and not applying themes and font i formated the phone but not worked i wamt to go back on nougt or oreo beta rom currently twrp working fine pls help me my model number is bnd al10
Click to expand...
Click to collapse
delete

allrockedout said:
This is stock recovery. Flash in twrp as image. Select recovery ramdisk as partition.
After flash. Reboot to recovery from twrp. That should take you to stock recovery. There you can do a factory reset.
https://drive.google.com/file/d/1IylCAhGs304boVkSXnSRrQQ1B5ozHwcX/view?usp=sharing
If you also flashed magisk or root. You will need to flash kernel as well. I was able to flash in fastboot mode. https://drive.google.com/file/d/1hYHlyNpJUfvYzM9EOli2ASKp3cnx98_L/view?usp=sharing
Click to expand...
Click to collapse
When i hve to flash kernal bro after flash stock recovery or before ? And how to flash? Through twrp or fastboot mood and bro i don't understand this line ( Select recovery ramdisk as partition) pls tell me step by step

moinkazi said:
When i hve to flash kernal bro after flash stock recovery or before ? And how to flash? Through twrp or fastboot mood and bro i don't understand this line ( Select recovery ramdisk as partition) pls tell me step by step
Click to expand...
Click to collapse
The recovery I posted before was for bl24 usa version ORRRREEEEEOOOOO ONNNNLLYYY. You need to get correct recovery_ramdisk.img and kernel.img for your device. First flash stock recovery_ramdisk in twrp as img. When you select the recovery img twrp will ask you where you want to install it. Select ramdisk recovery. If you rooted your device than you need kernel. You need to flash that in fastboot. Make sure your frp is unlocked. If you don't flash kernel your device won't reboot. To extract those img for your device. You need to download update.zip for your device. Google Huawei update extractor. Download that. Select update zip in application then update.app. Extract kernel.img and recovery_ramdisk.img.
To get update.zip for your device download Huawei firmware finder in play store. Download only update.zip
In Huawei update extractor you will get an error when trying to open update.zip. go to settings and unclick first box in settings and try open. You will see like 20 or 30 files.

allrockedout said:
The recovery I posted before was for bl24 usa version. You need to get correct recovery_ramdisk.img and kernel.img for your device. First flash stock recovery_ramdisk in twrp as img. When you select the recovery img twrp will ask you where you want to install it. Select ramdisk recovery. If you rooted your device than you need kernel. You need to flash that in fastboot. Make sure your frp is unlocked. If you don't flash kernel your device won't reboot. To extract those img for your device. You need to download update.zip for your device. Google Huawei update extractor. Download that. Select update zip in application then update.app. Extract kernel.img and recovery_ramdisk.img.
To get update.zip for your device download Huawei firmware finder in play store. Download only update.zip
In Huawei update extractor you will get an error when trying to open update.zip. go to settings and unclick first box in settings and try open. You will see like 20 or 30 files.
Click to expand...
Click to collapse
Thnks bro

Perfect time to find this post. I am getting the OTA update notification but it won't install on TWRP. My strategy is to return to stock (unrooted and stock recovery) to get the OTA. Once I am on that, get TWRP and Resurrection Remix.

allrockedout said:
The recovery I posted before was for bl24 usa version...
Click to expand...
Click to collapse
BND-L24 you mean?

duckredbeard said:
BND-L24 you mean?
Click to expand...
Click to collapse
Si

allrockedout said:
Si
Click to expand...
Click to collapse
Is there any way I could flash the kernel in twrp recovery before or after the stock recovery is flashed?

duckredbeard said:
Is there any way I could flash the kernel in twrp recovery before or after the stock recovery is flashed?
Click to expand...
Click to collapse
I tried flash recover ramdisk than kernel in twrp, rebooted to stock recovery and factory reset. But wouldn't boot, than booted to fastboot and flashed kernel, fastboot flash kernel kernel.img and it rebooted and was all good. Just my experience.

Just trying to avoid using adb.

duckredbeard said:
Just trying to avoid using adb.
Click to expand...
Click to collapse
You could try flashing kernel in twrp just saying wouldn't boot for me. You could try flashing kernel in twrp reboot to twrp than flash stock ramdisk. Not sure

allrockedout said:
You could try flashing kernel in twrp just saying wouldn't boot for me. You could try flashing kernel in twrp reboot to twrp than flash stock ramdisk. Not sure
Click to expand...
Click to collapse
Think I just might flash both in fastboot. If I put the files in my folder with my adb, what would the commands be?
fastboot flash recovery RECOVERY_RAMDIS.img
fastboot flash kernel KERNEL.img
Would that be right?

duckredbeard said:
Think I just might flash both in fastboot. If I put the files in my folder with my adb, what would the commands be?
fastboot flash recovery RECOVERY_RAMDIS.img
fastboot flash kernel KERNEL.img
Would that be right?
Click to expand...
Click to collapse
Fastboot flash recovery_ramdisk recovery_ramdis.img

allrockedout said:
Fastboot flash recovery_ramdisk recovery_ramdis.img
Click to expand...
Click to collapse
Going to do this one then the kernel...
Not super worried, seems there are unbrick tools out there.
---------- Post added at 09:41 PM ---------- Previous post was at 09:40 PM ----------
What state should the phone be in for this? TWRP recovery? Bootloader? Booted to Android?

duckredbeard said:
Going to do this one then the kernel...
Not super worried, seems there are unbrick tools out there.
---------- Post added at 09:41 PM ---------- Previous post was at 09:40 PM ----------
What state should the phone be in for this? TWRP recovery? Bootloader? Booted to Android?
Click to expand...
Click to collapse
You can boot to fastboot from twrp than start flashing

allrockedout said:
You can boot to fastboot from twrp than start flashing
Click to expand...
Click to collapse
My reboot options in TWRP are System, Power off, Recovery, and Bootloader.
Assuming Bootloader is the one I am to select?
Sorry for all the questions...i have never restored stock kernel or recovery. Just trying to get it back to stock to take the OTA so I can get back to TWRP and install Resurrection Remix.

duckredbeard said:
My reboot options in TWRP are System, Power off, Recovery, and Bootloader.
Assuming Bootloader is the one I am to select?
Sorry for all the questions...i have never restored stock kernel or recovery. Just trying to get it back to stock to take the OTA so I can get back to TWRP and install Resurrection Remix.
Click to expand...
Click to collapse
Yeah bootloader is correct. Good luck.

allrockedout said:
Yeah bootloader is correct. Good luck.
Click to expand...
Click to collapse
PS C:\adb> Fastboot flash recovery_ramdisk recovery_ramdis.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (32768 KB)...
OKAY [ 1.135s]
writing 'recovery_ramdisk'...
FAILED (remote: partition length get error)
finished. total time: 1.167s
Didn't see the fail. Flashed kernel just after the above...
PS C:\adb> fastboot flash kernel KERNEL.img
target reported max download size of 471859200 bytes
sending 'kernel' (24576 KB)...
OKAY [ 0.853s]
writing 'kernel'...
FAILED (remote: Command not allowed)
finished. total time: 0.868s
So they both failed. At least it rebooted to android!

duckredbeard said:
PS C:\adb> Fastboot flash recovery_ramdisk recovery_ramdis.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (32768 KB)...
OKAY [ 1.135s]
writing 'recovery_ramdisk'...
FAILED (remote: partition length get error)
finished. total time: 1.167s
Didn't see the fail. Flashed kernel just after the above...
PS C:\adb> fastboot flash kernel KERNEL.img
target reported max download size of 471859200 bytes
sending 'kernel' (24576 KB)...
OKAY [ 0.853s]
writing 'kernel'...
FAILED (remote: Command not allowed)
finished. total time: 0.868s
So they both failed. At least it rebooted to android!
Click to expand...
Click to collapse
Is frp and bootloader unlocked when rebooting to fastboot both are red?

TWRP Writing Failed Please Help !

Hello i am writing here the very first time.
This is what happened :
I unlocked the bootloader.
Downloaded Twrp for Honor 7x from xda
Tried to flash it using ADB but it showed this :
C:\android-sdk-windows platform-tools>fastboot flash recovery twrp_Honor_7x.img
target reported max download size of 471859200 bytes
sending 'recovery' (25158 KB)...
OKAY [ 0.9695)
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 1.000s
Please someone help, and if possible provide me a link to the working twrp img
Thanks

If you're on oreo, the partition names have changed.
Use this command instead:
fastboot flash recovery_ramdisk twrpname.img
TWRP for oreo: https://forum.xda-developers.com/devdb/project/dl/?id=28883

crayonicle said:
If you're on oreo, the partition names have changed.
Use this command instead:
fastboot flash recovery_ramdisk twrpname.img
Click to expand...
Click to collapse
Okk let me check using this command and thanks for replying I will let you know in a bit

MeChiku said:
Okk let me check using this command and thanks for replying I will let you know in a bit
Click to expand...
Click to collapse
I also attached the link for a working TWRP for oreo, don't go flashing the nougat TWRP on oreo lol

crayonicle said:
I also attached the link for a working TWRP for oreo, don't go flashing the nougat TWRP on oreo lol
Click to expand...
Click to collapse
Thank you so much dear?

crayonicle said:
I also attached the link for a working TWRP for oreo, don't go flashing the nougat TWRP on oreo lol
Click to expand...
Click to collapse
Thanks a ton bro Twrp Installed Successfully, Please can you suggest the best treble rom for honor 7x i am looking for DOT OS or Lineage

XA2 PLUS Custom Rom !!!

Could anyone have experimented with this model of phone about other rom's !!??
no information found conserning the custom rom such as lineage, aospextented, resurection remix, miui and others ... ????

No news ?!!

itmasen1 said:
No news ?!!
Click to expand...
Click to collapse
Maybe it has something to do with the low number of people using Sony's mobile phones.

On the getdroidtips site there is a new update for xa2 plus (OMNIROM) created based on android 9 pie. Someone installed this custom rom?

Sure. It works (well for me it does). For now only H4413 variant.
But you better download from http://dl.omnirom.org/voyager/

scanno said:
Sure. It works (well for me it does). For now only H4413 variant.
But you better download from http://dl.omnirom.org/voyager/
Click to expand...
Click to collapse
Hi Scanno thank you !
How did you root your phone?
I found a problem of flash recovery it does not pass, I tried twrp-3.2.3-0-voyager.img and twrp-3.3.0-0-voyager.img by command adb it did not succeed , maybe with twrp zip but I do not find twrp voyager in format zip .can you help me ?? thank's

itmasen1 said:
Hi Scanno thank you !
How did you root your phone?
I found a problem of flash recovery it does not pass, I tried twrp-3.2.3-0-voyager.img and twrp-3.3.0-0-voyager.img by command adb it did not succeed , maybe with twrp zip but I do not find twrp voyager in format zip .can you help me ?? thank's
Click to expand...
Click to collapse
What problems did you get?
I presume you unlocked the bootloader?
What exactly did you do?
What firmware are you on?
What device do you have... H4413?

scanno said:
What problems did you get?
I presume you unlocked the bootloader?
What exactly did you do?
What firmware are you on?
Click to expand...
Click to collapse
Device xa2 plus dual (H4413)
yes bootloder unlocked
i am in pie 9.0
when i lunch commad adb :
C:\ADB>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (27916 KB)...
OKAY [ 0.783s]
writing 'recovery'...
FAILED (remote: No such partition.)
finished. total time: 0.798s

itmasen1 said:
yes bootloder unlocked
i am in pie 9.0
when i lunch commad adb :
C:\ADB>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (27916 KB)...
OKAY [ 0.783s]
writing 'recovery'...
FAILED (remote: No such partition.)
finished. total time: 0.798s
Click to expand...
Click to collapse
Dont do that.....
do fastboot boot twrp-3.2.3-0-voyager.img
XA2 devices are so called A/B devices and do not have a recovery partition.
That is why you should use fastboot boot [recovery image] to boot into twrp/recovery
Then you can do a adb sideload of the rom zip.
But you are better off by using 50.1.A.13.123 (Oreo) since there are problems with TWRP on 50.2.A.352

scanno said:
Dont do that.....
do fastboot boot twrp-3.2.3-0-voyager.img
XA2 devices are so called A/B devices and do not have a recovery partition.
That is why you should use fastboot boot [recovery image] to boot into twrp/recovery
Then you can do a adb sideload of the rom zip.
But you are better off by using 50.1.A.13.123 (Oreo) since there are problems with TWRP on 50.2.A.352
Click to expand...
Click to collapse
yes it work with this method :
C:\ADB>fastboot boot twrp-3.2.3-0-voyager.img
downloading 'boot.img'...
OKAY [ 0.796s]
booting...
OKAY [ 5.304s]
finished. total time: 6.115s
and now , when i reboot in recovery mode twrp disappears. is this normal?
can I flash the omnirom on the first shot ?? .

itmasen1 said:
yes it work with this method :
C:\ADB>fastboot boot twrp-3.2.3-0-voyager.img
downloading 'boot.img'...
OKAY [ 0.796s]
booting...
OKAY [ 5.304s]
finished. total time: 6.115s
and now , when i reboot in recovery mode twrp disappears. is this normal?
can I flash the omnirom on the first shot ?? .
Click to expand...
Click to collapse
Yes that is normal TWRP is not flashed, it is just booted.
You can flash omnirom like you normally would, but you will need to format the data partition.
I usually use adb sideload, but flashing the zip from sdcard is also possible.
If you want to use gapps, use open gapps nano.
But after flashing omni, reboot to bootloader from TWRP and run fastboot boot twrp-3.2.3-0-voyager.img again
then flash gapps.

scanno said:
Yes that is normal TWRP is not flashed, it is just booted.
You can flash omnirom like you normally would, but you will need to format the data partition.
I usually use adb sideload, but flashing the zip from sdcard is also possible.
If you want to use gapps, use open gapps nano.
But after flashing omni, reboot to bootloader from TWRP and run fastboot boot twrp-3.2.3-0-voyager.img again
then flash gapps.
Click to expand...
Click to collapse
YES:good: but wifi not worked

Can you give a logcat. Working fine here.
Verstuurd vanaf mijn ASUS_Z01RD met Tapatalk

The flash of this rom is successful, just some bugs and also the wifi does not work anymore, it turns round does not capture any network, Probably the cause comes from the pie9 version. I will go back to the version oreo8 and reflash the omnirom and I'll keep you informed.
Thank you for all the infos scanno

itmasen1 said:
The flash of this rom is successful, just some bugs and also the wifi does not work anymore, it turns round does not capture any network, Probably the cause comes from the pie9 version. I will go back to the version oreo8 and reflash the omnirom and I'll keep you informed.
Thank you for all the infos scanno
Click to expand...
Click to collapse
That WiFi is not working is strange. I flashed pie and then Omni, but WiFi was still working.
Like I said please provide a logcat / dmesg. There is an app included in the rom for that
Verstuurd vanaf mijn ASUS_Z01RD met Tapatalk

Can anyone confirm if it can used on H4493 also. Thanks!

https://drive.google.com/file/d/1bgUrUcEUrdkRtIIcoe_7ehCmPlYP5sQ4/view?usp=sharing
scanno said:
That WiFi is not working is strange. I flashed pie and then Omni, but WiFi was still working.
Like I said please provide a logcat / dmesg. There is an app included in the rom for that
Verstuurd vanaf mijn ASUS_Z01RD met Tapatalk
Click to expand...
Click to collapse
finaly backed to oreo and booting with twrp-3.3.0-0-voyager.img,flashing omni rom with sideloader
and rebooting in mode recovery with cmd fastboot boot twrp, install gapps and all done fine !!!!!
:good:

hamirali said:
Can anyone confirm if it can used on H4493 also. Thanks!
Click to expand...
Click to collapse
It can be used. Guess the only difference is memory/storage..
But i would need some info because I might need to add something in init.
I need to value of:
/proc/cei_project_id
Just to be sure.
Verstuurd vanaf mijn ASUS_Z01RD met Tapatalk

Thanks scanno for confirming so promptly.
I am quite a. novice at this... I am minimally experienced with twrp and have used it to flash custom rom on another device.
Thanks for trying to assist, but I have no clue how to get you the info you asked. Apologies.
scanno said:
It can be used. Guess the only difference is memory/storage..
But i would need some info because I might need to add something in init.
I need to value of:
/proc/cei_project_id
Just to be sure.
Verstuurd vanaf mijn ASUS_Z01RD met Tapatalk
Click to expand...
Click to collapse

provide a logcat / dmesg.
Not anderstand !!!!