Database Info

Honor 6A - Help needed

Hi,
I have just attempted to root my Honor 6A (which is no easy task, given its popularity) using TWRP installed via adb & fastboot.
Though when I got to Wipe my phone using TWRP, all the remaining files and folder were I believe encrypted (random strings of numbers and letters), therefore I couldn't find whatever image I was looking for.
I then attempted to reboot my phone and see what's going on, and only the navigation buttons are there, the rest of the screen being black, no android system.
I then attempted to use Huawei's eRecovery, but no luck, it can't find the "package" it needs to restore.
I also tried the fastboot + HiSuite option, it says the phone is not supported.
So what to do? What can I do? I have TWRP, unlocked bootloader.
I thought about flashing the stock rom but I can't find it anywhere, this phone literally has the worst support I've ever seen.
I'm thinking of just bringing this phone to after-sale services but not sure they'll help given the phone is unlocked and everything.

Yuuteru said:
Hi,
I have just attempted to root my Honor 6A (which is no easy task, given its popularity) using TWRP installed via adb & fastboot.
Though when I got to Wipe my phone using TWRP, all the remaining files and folder were I believe encrypted (random strings of numbers and letters), therefore I couldn't find whatever image I was looking for.
I then attempted to reboot my phone and see what's going on, and only the navigation buttons are there, the rest of the screen being black, no android system.
I then attempted to use Huawei's eRecovery, but no luck, it can't find the "package" it needs to restore.
I also tried the fastboot + HiSuite option, it says the phone is not supported.
So what to do? What can I do? I have TWRP, unlocked bootloader.
I thought about flashing the stock rom but I can't find it anywhere, this phone literally has the worst support I've ever seen.
I'm thinking of just bringing this phone to after-sale services but not sure they'll help given the phone is unlocked and everything.
Click to expand...
Click to collapse
I didn't understand really well what happened. Did you successful install the TWRP? can you put here the download link? What did you do to brick your phone?
As you have already discovered there isn't enough "modding" on our phone (I have the same model). As far as I know the Honor 6A's stock rom is not published on internet yet. The only methods that I know to obtain the rom are: ask to Huawei/Honor for it (I've tried to contact them, but they didn't reply) or dump it using a custom recovery.
I dumped an official update, it is for the model DLI-L22 and you can download it following this link (size: ~400MB). The update contains several files, in particular there is the update.app archive that you can open with this tool, the files inside update.app are the following:
Code:
ABOOT.img CMNLIB64.img ERECOVERY.img MODEM.img SBL1.img
AMSS_VER.img CMNLIB.img GPT.img MSADP.img SHA256RSA.img
AMSS_VERLIST.img CRC.img KEYMASTER.img PACKAGE_TYPE.img TZ.img
APDP.img DEVCFG.img LKSECAPP.img RECOVERY.img
BOOT.img DSP.img MDTP.img RPM.img
It seems to contain the original recovery and other stuff that maybe can help you. Please pay attention, because it is not the full rom, it is just an incremental update, for example SYSTEM.img and USERDATA.img are missing.
The best solution is that someone with the TWRP makes a dump of the official rom, unfortunately I have still the stock rom and I'm not sure to install the TWRP. The reason is because I don't want to lose the official updates, so you should wait for some other user with the same phone that shares the rom.
Maybe you can try to flash some of the component from the update that I've dumped, but it is risky.
In my opinion, the eRecovery is completely useless., because it simply doesn't work. Maybe you can also try to flash the RECOVERY.img on the eRecovery partition (it should be called recovery2), but I'm not sure it is possible to do it on our phone. Then, you can try to install the full update through the official recovery. However, those images don't seem to be very helpful.
EDIT:
Some progresses have been made since the last time I checked, see this thread. Another possibility is to try some stock ROMs from other phones with similar specs (e.g. Honor 4X/5X), but probably it doesn't work.

Nrin said:
I didn't understand really well what happened. Did you successful install the TWRP? can you put here the download link? What did you do to brick your phone?
As you have already discovered there isn't enough "modding" on our phone (I have the same model). As far as I know the Honor 6A's stock rom is not published on internet yet. The only methods that I know to obtain the rom are: ask to Huawei/Honor for it (I've tried to contact them, but they didn't reply) or dump it using a custom recovery.
I dumped an official update, it is for the model DLI-L22 and you can download it following this link (size: ~400MB). The update contains several files, in particular there is the update.app archive that you can open with this tool, the files inside update.app are the following:
Code:
ABOOT.img CMNLIB64.img ERECOVERY.img MODEM.img SBL1.img
AMSS_VER.img CMNLIB.img GPT.img MSADP.img SHA256RSA.img
AMSS_VERLIST.img CRC.img KEYMASTER.img PACKAGE_TYPE.img TZ.img
APDP.img DEVCFG.img LKSECAPP.img RECOVERY.img
BOOT.img DSP.img MDTP.img RPM.img
It seems to contain the original recovery and other stuff that maybe can help you. Please pay attention, because it is not the full rom, it is just an incremental update, for example SYSTEM.img and USERDATA.img are missing.
The best solution is that someone with the TWRP makes a dump of the official rom, unfortunately I have still the stock rom and I'm not sure to install the TWRP. The reason is because I don't want to lose the official updates, so you should wait for some other user with the same phone that shares the rom.
Maybe you can try to flash some of the component from the update that I've dumped, but it is risky.
In my opinion, the eRecovery is completely useless., because it simply doesn't work. Maybe you can also try to flash the RECOVERY.img on the eRecovery partition (it should be called recovery2), but I'm not sure it is possible to do it on our phone. Then, you can try to install the full update through the official recovery. However, those images don't seem to be very helpful.
EDIT:
Some progresses have been made since the last time I checked, see this thread. Another possibility is to try some stock ROMs from other phones with similar specs (e.g. Honor 4X/5X), but probably it doesn't work.
Click to expand...
Click to collapse
le firmware intégrale pour le Huawei Honor 6A DLI-L22 se trouve a cette adresse
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G2094/g1650/v120299/f1/full/update.zip (thanks www.4pda.ru)
the complete firmware for the Huawei Honor 6A DLI-L22 is located at this address
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G2094/g1650/v120299/f1/full/update.zip (thanks on 4pda.ru)

[DEV] OnePlus 6, no luck with Treble, seeking help

So me and Phhusson spent a good part of yesterday and today trying to get the Treble GSI to boot on the OnePlus 6 but no luck.
Only got the device recognised as Qualcomm HS-USB Diagnostics 900E (COM3), no ADB so no logcat
Which means no /system boot at all, black screen after the bootloader unlocked warning.
there are some dm-verity/fec errors, but using a modified vbmeta image did not change anything
If any other dev out here has any ideas you are welcome, me and phh are out of ideas.
PS, find here stock vendor, system and boot images, plus the dump of /sys/fs/pstore
https://drive.google.com/open?id=1J_sROd5AYVmvVTOGfMBuazoVWx4bSkTe

Update 1:
The black screen and no boot issue seems to be much more widespread and it's not specific to the Treble GSI, I have seen a lot of users experiencing the same exact behaviour when flashing other images too, even some stock images from OnePlus.
No clue yet about the exact cause, waiting for more devs to join in on this.

I assume you guys have contacted 1+?
Fingers crossed they could help

Same problem here.. No idea why OP6 boots into EDL mode when You try to boot Phh GSI. I noticed that sometimes when I boot into TWRP, it freezes and boots into EDL too.
Edit: And just like Exelios said, even with stock OP6 system.img it refuses to boot and boots into EDL instead.

ProtoDeVNan0 said:
Same problem here.. No idea why OP6 boots into EDL mode when You try to boot Phh GSI. I noticed that sometimes when I boot into TWRP, it freezes and boots into EDL too.
Edit: And just like Exelios said, even with stock OP6 system.img it refuses to boot and boots into EDL instead.
Click to expand...
Click to collapse
Yeah, you might have to re-flash the entire device with fastboot -w flashall, only way I got back to stock.
https://forum.xda-developers.com/showpost.php?p=76620386&postcount=60

Interesting...who knows what kind of weird stuff OnePlus did when implementing Treble. Did you try Updating to OnePlus Android P beta and going from there?

Exelios said:
Yeah, you might have to re-flash the entire device with fastboot -w flashall, only way I got back to stock.
https://forum.xda-developers.com/showpost.php?p=76620386&postcount=60
Click to expand...
Click to collapse
Managed to get it to boot after I used those commands (Thanks for telling me though )
fastboot flash boot_a
fastboot flash boot_b
fastboot flash system_a
fastboot flash system_b
fastboot flash vendor
fastboot -w flash vbmeta
And I used latest OOS zip from OP website. Just had to extract payload etc.
My guess is that we either need a different vbmeta or ramdisk is not compatible with our OP6. I never worked on A/B so it's all new to me. But I will do some "reverse engineering" soon. I'm surprised to see OP mess up Treble though, they are very developer friendly so why did they mess it up?

ProtoDeVNan0 said:
Managed to get it to boot after I used those commands (Thanks for telling me though )
fastboot flash boot_a
fastboot flash boot_b
fastboot flash system_a
fastboot flash system_b
fastboot flash vendor
fastboot -w flash vbmeta
And I used latest OOS zip from OP website. Just had to extract payload etc.
My guess is that we either need a different vbmeta or ramdisk is not compatible with our OP6. I never worked on A/B so it's all new to me. But I will do some "reverse engineering" soon. I'm surprised to see OP mess up Treble though, they are very developer friendly so why did they mess it up?
Click to expand...
Click to collapse
What I suspect is that the software is just unfinished, not messed up.
Here is the VBMETA.img that made it possible to boot on the pixel 2 xl, but causes the OP6 not to boot at all, not even stock system.
https://drive.google.com/open?id=1ifnXCIdkqKnk_a1HII9RqQd5CVFWz1xR

Bought and shipped a OP6 to Phhusson, hopefully he manages to figure out something with the device in his hands.
Are there really no other devs interested in getting this working? Just me and Phhusson?

Little update
Different OP6 devices are failing to boot differently, some go to EDL and some in PDL, when flashed the same files in the same way.
(Emergency Download Mode
Primary Download Mode)
Sent from my OnePlus 6 using XDA Labs

Hey buddy,
Not sure if you have seen this thread:
https://forum.xda-developers.com/oneplus-6/how-to/guide-how-to-flash-treble-roms-oneplus-6-t3797858
Is this what you're talking about?
Regards,
Ravi
Sent from my OnePlus6 using XDA Labs

See, I really wish I knew how to get started learning about Android Development like this, I would love to help lol.
I've tried dabbling in Custom ROMs but I don't know enough Java to add useful features lol, and even understanding the build system is kind of hard lol.
Like where would one go to learn how to make Treble ROMs boot and fix errors like this, and just dev stuff like this in general haha.

i was able to boot flashing boot_a, boot_b, system_a, system_b, vbmeta and vendor. i didn't used any dm-verify commands....
ps: it feels really smoother and snappier.... dont know why yet..... lol.....
TURBO

TURBO2012 said:
i was able to boot flashing boot_a, boot_b, system_a, system_b, vbmeta and vendor. i didn't used any dm-verify commands....
ps: it feels really smoother and snappier.... dont know why yet..... lol.....
TURBO
Click to expand...
Click to collapse
What are you talking about? Your screenshot shows stock ROM, not any of the GSI

Exelios said:
What are you talking about? Your screenshot shows stock ROM, not any of the GSI
Click to expand...
Click to collapse
My bad.... I flashed the files in OP. Thinking those were a gsi rom. Lol... My apologies.....
this is the correct one:
TURBO

This thread is almost 3 years old but leaving this here since it is the top google search for OnePlus 6 HS-USB Diagnostics 900E hopefully my solution in the link below helps someone else in the future.
[GUIDE] Mega Unbrick Guide for A Hard Bricked OnePlus 6
Similar to the previous threads for OnePlus 5 or OnePlus 5T, here are the necessary packages to unbrick/revive a hard bricked OnePlus 6. Download: https://www.androidfilehost.com/?w=files&flid=271466 OnePlus 6_180513_氢OS线刷包.rar After using it...
forum.xda-developers.com

Dynamic "super" partitions and Fastboot

Does anyone know anything about the "super" partition we have on our phones?
What I've found out so far is that it's a newish thing developed for Android 10, where the big partitions like system and vendor sit within this new super partition as "groups". Hence why in Fastboot if you run 'Fasboot getvar all' you'll see no system or vendor partition, only super. A key difference is that it sits in the "user-space".
The super partition has a header to tell the system what's in it and I think this is what the vbmeta_system and vbmeta_vendor images are for.
This explains it a little better : https://source.android.com/devices/tech/ota/dynamic_partitions/implement
Basically I'm attempting to flash the Global firmware onto my Chinese device. With most phones the images are just there in the downloaded ROM and even give you a flash all script to run, but Oppo do a couple of things to make our life more difficult.
Firstly you have to decrypt the ozip file to get a regular zip that you can then extract. Then there's no recovery image, so you have to make one using UR-Tool and a simple Linux command (will post the how to below). So now I have what I think are the key images to flash.
BUT, the system and vendor images sit in the super partition and I have no idea how to flash these. It appears to need a program called fastbootd , which I don't have and I think my only eat hooded in pixel phones?
I can even see the script that puts these images into the super partition, but have no idea how to run it.
Any Android experts out there?

Please - i'm begging you :d

klanbo78 said:
Please - i'm begging you :d
Click to expand...
Click to collapse
i think you should go to some another device's forums which have more devs, like Samsung ? They maybe know something

Thanks for the suggestion, certainly had more luck in other forums but information is pretty sketchy.
Will keep digging as I really don't need a paperweight this expensive!

I'd suggest trying some Xiaomi forums, they're the similar to Oppo in that flashing Global on to Chinese is either really difficult or impossible as of late.

I have this super partition to in my poco X3, basicly i'm new with this partition because not have in my old poco f1. This partition eat 2x more system storage.

Alvian_P said:
I have this super partition to in my poco X3, basicly i'm new with this partition because not have in my old poco f1. This partition eat 2x more system storage.
Click to expand...
Click to collapse
But the Super partiton contains various "logical" partitions like system, product, vendor, etc - so it will be bigger. The actual point of it is to actually save space on the phone and have resizeable partitions.

I managed to find a super.img anyway that I extracted from an ofp file I found. Tried to flash through fastboot but didn't sove the issue. Seems the only way to flash system, product, vendor, etc is by using fastbootd (the new version of fastboot that operates in userspace).
It's not available on the Find X2 with Android 10 models but Oppo have now included it in android 11 build. If you have ColorOS11 then goto ADB and run 'adb reboot fastboot', it'll get you into fastbootd mode (must have the latest fastboot and adb version from google). From there if you had the correct images I assume you could flash them.
Thankfully, Oppo UK have agreed to flash it for me, it's currently at the repair centre and they said they'd probably have to do a remote flash from China. Wondering if it will come back with Android 10 or 11

Recovery??????

sush1101 said:
Recovery??????
Click to expand...
Click to collapse
I'll need a bit more than that unfortunately....

how can we check if a device is currently using the dynamic super partition system or if it's got the older a/b set up instead?

Hi buddy,i'm a Chinese oppo user .I've been trying to flash a custom rom on my find x2 pro and it's the first time i see someone who has the same experience. I failed and bricked my phone several days ago,luckily oppo store helped me reset it to factory for free, so it's android10 now ,and it reboots to its official recovery interface instead of fastbootd when i run "adb reboot fastboot". It will succeed in entering fastbootd mode if it's with android11, right?what does the fastbootd mode look like,the same of fastboot or a new look?with fastbootd i can flash system.img to the system area under the super partition,right?thanks if you could help me out.

klanbo78 said:
Does anyone know anything about the "super" partition we have on our phones?
What I've found out so far is that it's a newish thing developed for Android 10, where the big partitions like system and vendor sit within this new super partition as "groups". Hence why in Fastboot if you run 'Fasboot getvar all' you'll see no system or vendor partition, only super. A key difference is that it sits in the "user-space".
The super partition has a header to tell the system what's in it and I think this is what the vbmeta_system and vbmeta_vendor images are for.
This explains it a little better : https://source.android.com/devices/tech/ota/dynamic_partitions/implement
Basically I'm attempting to flash the Global firmware onto my Chinese device. With most phones the images are just there in the downloaded ROM and even give you a flash all script to run, but Oppo do a couple of things to make our life more difficult.
Firstly you have to decrypt the ozip file to get a regular zip that you can then extract. Then there's no recovery image, so you have to make one using UR-Tool and a simple Linux command (will post the how to below). So now I have what I think are the key images to flash.
BUT, the system and vendor images sit in the super partition and I have no idea how to flash these. It appears to need a program called fastbootd , which I don't have and I think my only eat hooded in pixel phones?
I can even see the script that puts these images into the super partition, but have no idea how to run it.
Any Android experts out there?
Click to expand...
Click to collapse
did you ever find a solution to this issue? I am facing an issue where I cannot flash my stock rom (oneplus 9 pro user) because twrp reports that I have no product, system_ext, and odm partitions on slot B, yet my phone boots fine on slot A, therefore my slot B is f'd up. I have been searching everywhere for a way to flash these partitions in fastbootd, but when I attempt to flash they report as "file/folder not found" even though I am literally flashing them to the slot. this is driving me crazy and I do not want to MSM my phone, I just want to repair slot B. how the fck do we flash these partitions, and how would my phone boot if they were even missing??

thirtythr33 said:
did you ever find a solution to this issue? I am facing an issue where I cannot flash my stock rom (oneplus 9 pro user) because twrp reports that I have no product, system_ext, and odm partitions on slot B, yet my phone boots fine on slot A, therefore my slot B is f'd up. I have been searching everywhere for a way to flash these partitions in fastbootd, but when I attempt to flash they report as "file/folder not found" even though I am literally flashing them to the slot. this is driving me crazy and I do not want to MSM my phone, I just want to repair slot B. how the fck do we flash these partitions, and how would my phone boot if they were even missing??
Click to expand...
Click to collapse
Afraid not, I sent the phone back to Oppo and they flashed it. TWRP wasn't available for the X2 pro and didn't work for Android 10/11 anyway, although I heard there has been some progress on that front. You should stand a chance on OnePlus though as not locked down and more tools out there.

klanbo78 said:
Afraid not, I sent the phone back to Oppo and they flashed it. TWRP wasn't available for the X2 pro and didn't work for Android 10/11 anyway, although I heard there has been some progress on that front. You should stand a chance on OnePlus though as not locked down and more tools out there.
Click to expand...
Click to collapse
yeah bro thanks anyway, this is quite a clusterfck here, it blows my mind that my phone boots find on slot A yet I cannot update my rom because apparently I am missing those critical partitions, and when I try to flash them they tell me they are not found. lol wtf man

I hope I'm not too late to say this but you can boot to fastbootd from fastboot with command:
for linux/mac fastboot reboot fastboot or ./fastboot reboot fastboot I have little experience in both
for windows "Powershell only" ./fastboot reboot fastboot this aint working for cmd for unknown reason, ig it recognize the second "fastboot" in "reboot fastboot" as an invoke to the command "fastboot" and not as a parameter sent to fastboot.exe

thirtythr33 said:
did you ever find a solution to this issue? I am facing an issue where I cannot flash my stock rom (oneplus 9 pro user) because twrp reports that I have no product, system_ext, and odm partitions on slot B, yet my phone boots fine on slot A, therefore my slot B is f'd up. I have been searching everywhere for a way to flash these partitions in fastbootd, but when I attempt to flash they report as "file/folder not found" even though I am literally flashing them to the slot. this is driving me crazy and I do not want to MSM my phone, I just want to repair slot B. how the fck do we flash these partitions, and how would my phone boot if they were even missing??
Click to expand...
Click to collapse
use the command above to boot to fastbootd, but beware not to flash the partitions to the A slot as it's the active one ig. You have to switch to slot B before flashing and switch it again to A afterwards.
use command fastboot getvar all and look for "current-slot" in the result.
if "current-slot" is A, then use command fastboot set_active b
or if it's B then fastboot set_active a
Then switch the slot back as it was before.
Good luck with it

This whole slot _a/_b and super partition thing is super confusing right?
To flash super partition you can do
fastboot flash super super_patched.img
And as @L0ND0NB0Y already mentioned you can easily switch boot slots like this:
fastboot --set-active=b
Good luck!

lebigmac said:
This whole slot _a/_b and super partition thing is super confusing right?
To flash super partition you can do
fastboot flash super super_patched.img
And as @L0ND0NB0Y already mentioned you can easily switch boot slots like this:
fastboot --set-active=b
Good luck!
Click to expand...
Click to collapse
Do you know how to flash a GSI rom onto a phone that has a super partition ? i was successful on a G8 that had system and vendor product partition separate

Hello mates can help me I am using LG v60 I unlocked the bootloader and rooted the device successfully and created the super partition I took backup of IMG file to my memory card after sometimes when I try to restart my mobile my mobilegot bricked and my memory card also corrupted. I am unable to retrieve the backup files now I want to remove the super partion from my mobile...
I want to go back to original factory firmware with locked bootloader..i need to erase dynamic partition...

Flashed Pixel 4a with Pixel 5 image by mistake

Hello,
I'm desperate and i hope to find here any kind of help to get my phone works again.
By mistake i flashed my Phone pixel 4a with a pixel 5 image, now my phone pixel 4a is stuck in QDL mode, and not responding to any of recovery/fastboot key combination "power+volume up or down or both".
For the last 2 days i was surfing online, and i found out that, that i need a factory mbn file to flash the phone using QFiL to regain fastboot mode and be able to flash the phone with the right stock image.
Could anyone please help me or guide me, where can i find the pixel 4a mbn file, or maybe build it from google source code, or maybe another solution i don't know about to get my phone working again?!
Any help would be so appreciated.
Thank you

Maybe you can use Android Image Kitchen (https://forum.xda-developers.com/t/...kernel-ramdisk-win-android-linux-mac.2073775/) and find the mdn file in one of the stock Pixel 4a images.

JohnC said:
Maybe you can use Android Image Kitchen (https://forum.xda-developers.com/t/...kernel-ramdisk-win-android-linux-mac.2073775/) and find the mdn file in one of the stock Pixel 4a images.
Click to expand...
Click to collapse
Thank you for your reply.
Just to make sure, it's mbn file what I'm looking for, not mdn.

Anyone could help me please with Android Image Kitchen, I tried it, but I don't know how exactly to get the mbn file, as far as i know, mbn file is some kind of factory image that in hex format file with .mbn extension.
The main cause of this issue, that the bootloader.img which get flashed first, is the one caused the phone to reboot and stuck into QDL mode.

Run the "unpackimg.bat" file on the stock bootloader.img and see if that file is in the extracted files of the bootloader.

JohnC said:
Run the "unpackimg.bat" file on the stock bootloader.img and see if that file is in the extracted files of the bootloader.
Click to expand...
Click to collapse
That is what i get:
Android Image Kitchen - UnpackImg Script
by osm0sis @ xda-developers
Supplied image: bootloader-sunfish-s5-0.3-7062598.img
Setting up work folders...
Unrecognized format.
Error!

I've used it to unpack a TWRP image, and it extracted all the files of it fine.
I guess google is using some other format for their img.

JohnC said:
I've used it to unpack a TWRP image, and it extracted all the files of it fine.
I guess google is using some other format for their img.
Click to expand...
Click to collapse
It is working fine with boot.img, system.img, but not with this one bootloader-sunfish-s5-0.3-7062598.img, and that file when i run imjtool, it extracted the following files:
abl
aop
cmnlib
cmnlib64
devcfg
hyp
keymaster
logfs
qupfw
tz
uefisecapp
xbl
xbl_config
and sure none of them is not mbn file.

How do you know you phone is stuck in this "QDL" mode?
Can you shut off the phone?
And when you press and hold vol-down and power on - what happens?
Also, I found this thread that the last post seems to say that it took 5 full minutes for the phone to be accessible:
Possibly bricked Pixel 4a
Hello, so I tried to flash the rooted boot image for my Pixel 4a Sunfish from HolyAngel's thread, and I got stuck in a bootloop; I reckon it is because the boot image build number was incorrect, I did a cursory glance, did not verify character by...
forum.xda-developers.com

JohnC said:
How do you know you phone is stuck in this "QDL" mode?
Can you shut off the phone?
And when you press and hold vol-down and power on - what happens?
Also, I found this thread that the last post seems to say that it took 5 full minutes for the phone to be accessible:
Possibly bricked Pixel 4a
Hello, so I tried to flash the rooted boot image for my Pixel 4a Sunfish from HolyAngel's thread, and I got stuck in a bootloop; I reckon it is because the boot image build number was incorrect, I did a cursory glance, did not verify character by...
forum.xda-developers.com
Click to expand...
Click to collapse
The phone does not respond to power+volume key combination, and when i connected to windows machine it shows up in device manager "qualcomm HS-USB 9008" and on Linux when i run lsusb command it shows Qualcomm QDL mode.
I'll go through that post and give it a try.
I really appreciate the help, and thank you so much for your time.

Man that sucks, maybe this still works. I know it's helped others
[TOOL] Deuces Bootloop-Recovery & Flashing Script v5.0 [05/29/2019]
This script is written for UNLOCKED BOOTLOADER Google Pixel devices Fix Bootloops Work with any Google factory image Unlock Bootloader (Optional): Format Userdata...
forum.xda-developers.com

Edmontonchef said:
Man that sucks, maybe this still works. I know it's helped others
[TOOL] Deuces Bootloop-Recovery & Flashing Script v5.0 [05/29/2019]
This script is written for UNLOCKED BOOTLOADER Google Pixel devices Fix Bootloops Work with any Google factory image Unlock Bootloader (Optional): Format Userdata...
forum.xda-developers.com
Click to expand...
Click to collapse
That will not help him because its for the pixel 2 xl and he has a pixel 4a

TheSayaMan said:
That will not help him because its for the pixel 2 xl and he has a pixel 4a
Click to expand...
Click to collapse
Any pixel device

I believe the file is in the super_empty.img ,which can't be extracted or viewed ,check pixal 4a guides I have a post with info and pictures and files of imgs extracted there ,I sent my phone back for rreplacement

I would like to thank everyone who tried to help me here, I really appreciate your time trying to do so.
Please allow me to explain it again, because none of the solutions above can solve my issue:
I flashed my phone pixel 4a with a pixel 5 image by mistake, as you can see in flash-all.sh script, the first step is to flash the bootloader.img file, and then reboot, my phone did that flash for bootloader.img and rebooted to QDL mode, and stuck there, black screen of death, none of the key combinations work, power+volume up or down or both. The only thing that shows my phone is still alive is when i connect it to a Linux machine and run lsusb command it shows this:
Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
and on Windows, the device manager shows:
Qualcomm HS-USB 9008
My phone pixel 4a has no fastboot mode or recovery mode, only QDL mode, and as far as i know from the research i did on the last 3 days, that i need a factory image mbn file for pixel 4a, which i can use it to flash my phone using QFiL(qualcomm flash image loader) and regain fastboot mode, and that mbn file i do not know where can i get it or how to generate it.
Thank you and may God bless you all

miko12312 said:
I believe the file is in the super_empty.img ,which can't be extracted or viewed ,check pixal 4a guides I have a post with info and pictures and files of imgs extracted there ,I sent my phone back for rreplacement
Click to expand...
Click to collapse
Thank You for your help, but unfortunately it is not.

ahmed.elsersi said:
Thank You for your help, but unfortunately it is not.
Click to expand...
Click to collapse
If you can get a donor device and place the phone in download mode you should be able to extract and pull the data and files to fix the phone , all it takes is the mdm file which just creates the partitions ,and the qpst program from qualcomm

miko12312 said:
If you can get a donor device and place the phone in download mode you should be able to extract and pull the data and files to fix the phone , all it takes is the mdm file which just creates the partitions ,and the qpst program from qualcomm
Click to expand...
Click to collapse
Do you know how to do the extract?, I have QPST program, but i do not know the extract option.
Thank You.

ahmed.elsersi said:
Do you know how to do the extract?, I have QPST program, but i do not know the extract option.
Thank You.
Click to expand...
Click to collapse
I am unsure first time I've used the program but there is a one called emmc software download that seems useful , also the files need are in super_empty.img , if you can find a way to extract it ,it will have the files needed to fix it , I already got my replacement device so I can not test anything only try to obtain files ,super_empty.img is the partition layout to restore the system and include the radio firmware to give you service

Coming from an OP3T need help regarding the new partitions

I own a 3T currently and am planning to get an 8T as it is getting good custom rom traction. One thing I am really confused about the is the new partitioning scheme. Can someone please link me an article where I can read more about it? Also what's with the specific twrp's and installer zips for each rom and how does one flash magisk, xposed and other things?
What I am used to doing on my 3t is, wipe data, system, cache and then flash rom zip + gapps + magisk. I would really appreciate it if anyone can explain the additional steps that would be required to do this on the 8T

It's a very different world with the 8T (I also come from a 3T).
The 8T has A/B partitions as well as virtual A/B partitions. It also supports streaming OTA and seamless OTA updates. It has fastboot and fastbootd.
There's lots of good information on all of this in:
Virtual A/B Overview | Android Open Source Project
source.android.com
A/B (Seamless) System Updates | Android Open Source Project
source.android.com
platform/system/update_engine - Git at Google
Moving Fastboot to Userspace | Android Open Source Project
source.android.com
And more on this at the same site.
And, if you get into serious trouble, the unbricking tool is really easy to use and works wonderfully.

pratyush28 said:
I own a 3T currently and am planning to get an 8T as it is getting good custom rom traction. One thing I am really confused about the is the new partitioning scheme. Can someone please link me an article where I can read more about it? Also what's with the specific twrp's and installer zips for each rom and how does one flash magisk, xposed and other things?
What I am used to doing on my 3t is, wipe data, system, cache and then flash rom zip + gapps + magisk. I wouls really appreciate it if anyone can explain the additional steps that would be required to do this on the same thing on an 8T.
Click to expand...
Click to collapse
I'm going to try to give you a brief, yet precise enough guide to doing the basics on a device with partitions like the 8T.
Okay, so basically, the 8T custom ROMs, when flashed, are going to consist of the following partitions:
boot
dtbo
system
system_ext
product
recovery
vendor
odm
vbmeta
vbmeta_system
So when performing fastboot/adb commands with these newer devices, you're going to start off in the normal bootloader (i use the volume +/- and power at the same time command to enter this from a powered off state).
Now there's also a mode called fastbootd mode. It's often just called fastboot, especially when booting from bootloader (fastboot reboot fastboot now takes you to this fastbootd mode). This is where you're going to do the majority of flashing/modding from.
So to start off, enter bootloader, then perform this command in terminal to do a wipe of data:
fastboot -w
Then, flash recovery partition:
fastboot flash recovery recovery.img (this is the recovery.img from the ROM zip you are attempting to flash)
Then, reboot to fastbootd:
fastboot reboot fastboot
Next, I like to make sure I'm on partition A for flashing. This is just something I've been told to do and it works so I stick with it. So do this by:
fastboot set_active a
Now you can start flashing the paritions:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash product product.img
fastboot flash vendor vendor.img
fastboot flash odm odm.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
Then, boot up the ROM:
fastboot reboot
So that's the basic rundown.
Now for a few things to keep in mind:
Always make sure you're on the latest version of OxygenOS before doing any of this. I like to start off by unlocking bootloader, then setting up phone. Then I do an update to both partitions to the latest version of OOS (must be on both partitions. Not just on one). So I just put the latest OOS zip on my phone via USB transfer from PC, do an upgrade with that file (Settings > System > Update > Top right menu button > Select Internal Storage or whatever it says like that, then select the file (make sure the OOS zip file is in the MAIN root directory of your phone. So basically, the folder that contains the Pictures, Downloads, Music, etc. folders.
So after you do this system update, it will prompt you to reboot phone. Do this. Then, go to settings and do the same thing again. Select the OOS zip and do an internal storage update, let it do its thing, it'll ask to reboot, go ahead and do so. Now this second update you do will either start from 0% and go to 100% like the first time, or it will go from 0% directly to 99%, then 100% after a few seconds. This is okay, it just means you already had the latest OOS on one of your partitions. So anyway, go ahead and do that reboot when it tells you. Now you are unlocked and on the latest firmware and ready to flash.
Oh, and btw, to unlock bootloader, do the normal steps through developer options, then reboot to bootloader and this is the command used:
fastboot flashing unlock
That will let you confirm to unlock bootloader, etc. like I'm sure you've done on the 3T.
So anyway, after unlocking and updating to latest OOS (Open Beta or Stable usually both work fine btw), you can reboot to bootloader, then do the steps I told you above for wiping, flashing recovery, flashing partitions, booting, etc.
Oh, and to get these partition images from the custom ROM zip you choose to flash, you need to first unzip the ROM zip file, then take the payload.bin file that will result of the unzip, and use a payload_dumper script. Those are linked all over or can be found on a google search or Github. It'll take your payload.bin and turn it into these .IMG files that I list in the flashing steps. Each partition will have a file named PARTITIONNAME.img. These are all you need to flash a custom ROM over OOS.
To flash an update to a rom, do all the same stuff but don't do the
fastboot -w
and you also don't need to do the
fastboot flash recovery recovery.img
part because the recovery partition is already there from the ROM when you originally flashed.
I realize this is all a bunch of random notes and guides, and my brain kind of works in a weird way, but it's pretty much all there I think. If you need help clarifying any of this or just have any questions in general, PM me or respond back here and tag me. I'll help as much as I can or point you to someone who can help if I can't.
Hope this helps. Take care.

dpryor88 said:
I'm going to try to give you a brief, yet precise enough guide to doing the basics on a device with partitions like the 8T.
Okay, so basically, the 8T custom ROMs, when flashed, are going to consist of the following partitions:
boot
dtbo
system
system_ext
product
recovery
vendor
odm
vbmeta
vbmeta_system
So when performing fastboot/adb commands with these newer devices, you're going to start off in the normal bootloader (i use the volume +/- and power at the same time command to enter this from a powered off state).
Now there's also a mode called fastbootd mode. It's often just called fastboot, especially when booting from bootloader (fastboot reboot fastboot now takes you to this fastbootd mode). This is where you're going to do the majority of flashing/modding from.
So to start off, enter bootloader, then perform this command in terminal to do a wipe of data:
fastboot -w
Then, flash recovery partition:
fastboot flash recovery recovery.img (this is the recovery.img from the ROM zip you are attempting to flash)
Then, reboot to fastbootd:
fastboot reboot fastboot
Next, I like to make sure I'm on partition A for flashing. This is just something I've been told to do and it works so I stick with it. So do this by:
fastboot set_active a
Now you can start flashing the paritions:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash product product.img
fastboot flash vendor vendor.img
fastboot flash odm odm.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
Then, boot up the ROM:
fastboot reboot
So that's the basic rundown.
Now for a few things to keep in mind:
Always make sure you're on the latest version of OxygenOS before doing any of this. I like to start off by unlocking bootloader, then setting up phone. Then I do an update to both partitions to the latest version of OOS (must be on both partitions. Not just on one). So I just put the latest OOS zip on my phone via USB transfer from PC, do an upgrade with that file (Settings > System > Update > Top right menu button > Select Internal Storage or whatever it says like that, then select the file (make sure the OOS zip file is in the MAIN root directory of your phone. So basically, the folder that contains the Pictures, Downloads, Music, etc. folders.
So after you do this system update, it will prompt you to reboot phone. Do this. Then, go to settings and do the same thing again. Select the OOS zip and do an internal storage update, let it do its thing, it'll ask to reboot, go ahead and do so. Now this second update you do will either start from 0% and go to 100% like the first time, or it will go from 0% directly to 99%, then 100% after a few seconds. This is okay, it just means you already had the latest OOS on one of your partitions. So anyway, go ahead and do that reboot when it tells you. Now you are unlocked and on the latest firmware and ready to flash.
Oh, and btw, to unlock bootloader, do the normal steps through developer options, then reboot to bootloader and this is the command used:
fastboot flashing unlock
That will let you confirm to unlock bootloader, etc. like I'm sure you've done on the 3T.
So anyway, after unlocking and updating to latest OOS (Open Beta or Stable usually both work fine btw), you can reboot to bootloader, then do the steps I told you above for wiping, flashing recovery, flashing partitions, booting, etc.
Oh, and to get these partition images from the custom ROM zip you choose to flash, you need to first unzip the ROM zip file, then take the payload.bin file that will result of the unzip, and use a payload_dumper script. Those are linked all over or can be found on a google search or Github. It'll take your payload.bin and turn it into these .IMG files that I list in the flashing steps. Each partition will have a file named PARTITIONNAME.img. These are all you need to flash a custom ROM over OOS.
To flash an update to a rom, do all the same stuff but don't do the
fastboot -w
and you also don't need to do the
fastboot flash recovery recovery.img
part because the recovery partition is already there from the ROM when you originally flashed.
I realize this is all a bunch of random notes and guides, and my brain kind of works in a weird way, but it's pretty much all there I think. If you need help clarifying any of this or just have any questions in general, PM me or respond back here and tag me. I'll help as much as I can or point you to someone who can help if I can't.
Hope this helps. Take care.
Click to expand...
Click to collapse
I cannot thank you enough for taking out so much time and explaining everything in detail. I really appreciate it and this will be very very helpful for me.
Unfortunately, I purchased the 8T from OnePlus' official website and they sent me a refurbished piece with a cracked back panel and scratched screen. I was stupid to opt for OnePlus' site just because there was a small discount, now to get a replacement I have to go through a painful process of contacting their incompetent support and an eternal wait until they decide to revert. I'm glad that I recorded the unboxing video, so at least they cannot blame this on me.

pratyush28 said:
I cannot thank you enough for taking out so much time and explaining everything in detail. I really appreciate it and this will be very very helpful for me.
Unfortunately, I purchased the 8T from OnePlus' official website and they sent me a refurbished piece with a cracked back panel and scratched screen. I was stupid to opt for OnePlus' site just because there was a small discount, now to get a replacement I have to go through a painful process of contacting their incompetent support and an eternal wait until they decide to revert. I'm glad that I recorded the unboxing video, so at least they cannot blame this on me.
Click to expand...
Click to collapse
Ah man! I'm so sorry to hear that! Their support is horrible I must admit. Not as bad as Google Fi's support haha (that's another story), but it's bad yeah.
I got mine from the OP website also (North America model as I live in California) but I got it shortly after the phone was released. I can't believe they're selling refurbished, broken devices now. That's horrible. The company has been going a bit downhill with some aspects I've realized in the past few years.
Anyway, I really hope you get that sorted out (sooner than later hopefully). It's a nice device. Software support/updates are a little iffy with OP these days, but no one's perfect. But once you start flashing some custom goodness on the phone, it really shines. Nothing wrong with Oxygen in my opinion, but choice is nice
Let me know if/when you get the device if you need any help with anything.

dpryor88 said:
Ah man! I'm so sorry to hear that! Their support is horrible I must admit. Not as bad as Google Fi's support haha (that's another story), but it's bad yeah.
I got mine from the OP website also (North America model as I live in California) but I got it shortly after the phone was released. I can't believe they're selling refurbished, broken devices now. That's horrible. The company has been going a bit downhill with some aspects I've realized in the past few years.
Anyway, I really hope you get that sorted out (sooner than later hopefully). It's a nice device. Software support/updates are a little iffy with OP these days, but no one's perfect. But once you start flashing some custom goodness on the phone, it really shines. Nothing wrong with Oxygen in my opinion, but choice is nice
Let me know if/when you get the device if you need any help with anything.
Click to expand...
Click to collapse
Thanks mate, I won't hesitate to ask if I need help once I get the new device

@dpryor88 Finally after a 21 day battle with the OnePlus support, today I received my replacement device.
It happens to have LPDDR5 ram. I checked this xda article where they mentioned that the unbrick tool fails on this variant.
https://www.xda-developers.com/oneplus-8t-oneplus-9r-shipping-faster-ram/amp/
Which variant do you have? Also, did you try using the unbrick tool?

pratyush28 said:
@dpryor88 Finally after a 21 day battle with the OnePlus support, today I received my replacement device.
It happens to have LPDDR5 ram. I checked this xda article where they mentioned that the unbrick tool fails on this variant.
https://www.xda-developers.com/oneplus-8t-oneplus-9r-shipping-faster-ram/amp/
Which variant do you have? Also, did you try using the unbrick tool?
Click to expand...
Click to collapse
I have the other model. Unbrick tool works fine on mine.

pratyush28 said:
@dpryor88 Finally after a 21 day battle with the OnePlus support, today I received my replacement device.
It happens to have LPDDR5 ram. I checked this xda article where they mentioned that the unbrick tool fails on this variant.
https://www.xda-developers.com/oneplus-8t-oneplus-9r-shipping-faster-ram/amp/
Which variant do you have? Also, did you try using the unbrick tool?
Click to expand...
Click to collapse
My 8T has ddr_type of 1 and I've had no problems using the unbrick tool (and I've used it a lot as I've been testing/learning lots of stuff with TWRP) on my KB2000.

BillGoss said:
My 8T has ddr_type of 1 and I've had no problems using the unbrick tool (and I've used it a lot as I've been testing/learning lots of stuff with TWRP) on my KB2000.
Click to expand...
Click to collapse
That's some good news, mine is KB2001 I wonder if that will make a difference. Also, have you tried flashing custom roms? If yes, was there any firmware incompatibility?

pratyush28 said:
That's some good news, mine is KB2001 I wonder if that will make a difference. Also, have you tried flashing custom roms? If yes, was there any firmware incompatibility?
Click to expand...
Click to collapse
Yes, I installed a couple of custom ROMs and they were fine.
The only place I know that matters is the xbl and xbl_config partitions. The full OOS ROMs have an extra -lp5 set of files that get flashed on lp5 phones instead of the "normal" xbl files.
But since this only applies to firmware and the xbl partitions are never touched by custom ROMs, there cannot, therefore, be incompatibilities due to lp4 vs lp5.