Hello everyone,
I have an OG Pixel 5'', the stock Android was 7.1.2 and I updated it to Android 8.1 Oreo. Bootloader is unlocked, and I am able to install a TWRP 3.2.1-0 no problems. Phone at the time worked well. Now I have tried to flash an ElementalX Kernel on my device. This worked and I managed to boot. However, a message "There is an internal problem with your device, please contact the manufacturer". There is a thread to fix this and I should have done my research better.
Anyway, I went into TWRP and did a complete wipe of the phone, thinking that I could have just boot into TWRP again and copy the stock flashable zips to reflash the ROM.
It turns out that:
a) TWRP doesnt work. I.e when I got into fastboot mode (Power + Volume Down) and selected Recovery, the phone flashed to screen with Google image and then flashed back into the one with the green Android.
b) I managed to boot twrp via fastboot from my computer. So I booted into fastboot mode, and then on my computer, did: fastboot boot <twrp3.2.1.zip>. This worked and I managed to get into TWRP again. However, I cannot transfer file to flash. I.e when the phone showed up on my computer in TWRP, I cannot drag and drop anything into mounted folder.
I have tried the following to get stock ROM from this website: https://developers.google.com/android/images
a) I decided to look at ADB Sideload. So from the above website, I downloaded the zip files under Full OTA Images and then in TWRP, I went into Advance and chose ADB SIdeload. On my computer, I did "adb sideload name_of_zip_file_downloaded". The process started but ended very quickly, the finished time was 0.00 second, which means that nothing happened. Clearly, TWRP console showed that it is unable to mount /data and other folders. I guess the reason is that I am running a "live" TWRP? I checked by going back to TWRP mainscreen and tried to mount. However, all hard drives show 0MB (OTA USB and the main drive).
b) I used factory images approach by downloading zip from the same website, but this time under Factory Images. For this one, I unzip the files to a separate folder. Then I did flash-all.sh script but it said that my fastboot is too old.
So... to fix fastboot, I tried: (I am on Ubuntu 16.04.02)
a) Remove whole android fastboot with sudo apt-get remove, then reinstalled => Did not work. Still fastboot is too old
b) Download entire Android SDK from here: https://developer.android.com/studio/install.html. Fastboot still didnt work
c) From the Android Studio website, I tried to download just the command line tools. However, I could not find the folder with fastboot in it. A Google search shows that the fastboot and adb should be in platform-tools folder. Couldnt find any
Once again, I apologize for a very very long thread (It's 5am and I am trying to figure this thing out). Please, let me know if you guys can offer any help. Any help is greatly appreciated. FYI, I am coming from a Moto Z Play, and if things happen I would just boot into TWRP and copy the zip over. Clearly, this is not the case. This is my 1st Pixel as well.
Please let me know and thank you very very much.
Installing ex messes with the boot.IMG you need to reflash twrp after. Also don't manually flash stock zips that doesn't even make any sense. Download the latest android sdk or base platform tools then get the latest factory image and extract it into platform tools. Then go into fastboot and manually flash the official factory image
To use fastboot on ubuntu you have to put sudo infront of the command: sudo fastboot ........, Because of a permissions thing.
Sent from my Google Pixel using XDA Labs
Thank you everyone. I have managed to reflash the OS. Gonna stay with stock kernel
maxwell0312 said:
Thank you everyone. I have managed to reflash the OS. Gonna stay with stock kernel
Click to expand...
Click to collapse
I personally recommend using a custom kernel just make sure to follow the OP exactly. As the kernel and twrp are usually stored in the boot.img together and the kernel overwrites the boot.img the problem was likely that you just did things in the wrong order which would cause twrp to be removed. Typically the order of installing custom stuff from stock goes this way: flash_all to restore stock boot.img, boot twrp, factory wipe, flash rom, flash twrp, boot rom, reboot into recovery, flash kernel, flash twrp, reboot system, reboot recovery, flash magisk. Some rooms vary as they may require you to do things like flash a vendor img or delete the vendor overlay folder(always follow OP).
I was following instructions from XDA to root my Pixel 2 XL using Magisk. At one point magisk started compaining that it needed BootBridge-SonyELF.zip in order to continue, so I downloaded it and flashed it, and from that point on my Pixel will not start up. (yeah, I know, I'm an idiot)
During normal boot, it just shoes the G logo for hours. If I try recovery, it shows the TWRP intro screen but will not continue into the TWRP menu.
I tried adb sideload to flash the taimen factory image, but I get an "error: closed" error from the sideload command.
If I run adb devices while in the TWRP intro screen, my device shows up OK, so I guess there is still some hope.
Please help!
norad73 said:
I was following instructions from XDA to root my Pixel 2 XL using Magisk. At one point magisk started compaining that it needed BootBridge-SonyELF.zip in order to continue, so I downloaded it and flashed it, and from that point on my Pixel will not start up. (yeah, I know, I'm an idiot)
During normal boot, it just shoes the G logo for hours. If I try recovery, it shows the TWRP intro screen but will not continue into the TWRP menu.
I tried adb sideload to flash the taimen factory image, but I get an "error: closed" error from the sideload command.
If I run adb devices while in the TWRP intro screen, my device shows up OK, so I guess there is still some hope.
Please help!
Click to expand...
Click to collapse
Fastboot flash stock boot image
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
We received a new 8t and proceeded to do root and unlock on it.
Here is my process and problem.
Unlocked bootloader.
Updated phone to recent version via OTA update.
Downloaded update via Oneplus website.
Extracted payload.bin VIA python.payload dumper.
Moved boot.img to phone and patched it with magisk (select and patch a file)
Moved patched image to PC and ran adb
Fastboot flash boot patched image name.img
rebooted , now its caught in bootloop.
Tried fastboot --set-active=a and it didnt make a difference.
When looking at adb devices it shows the attached phone as unauthorized.
Dont know if this helps
Can get into fastboot
You flashed the OS to the bootloader. Not sure how to help you, man. Maybe try the EDL Tool. That worked for me. Also, always install TWRP and flash magisk zip through TWRP. It's foolproof.
TWRP doesnt work with android 11 or the oneplus 8 as far as I know, last time I looked.
Did a tool and fixed the crashes and bootloop, then followed a youtube video and guide.
Found out I ended up doing a different OS version that didnt match.
eracet said:
TWRP doesnt work with android 11 or the oneplus 8 as far as I know, last time I looked.
Did a tool and fixed the crashes and bootloop, then followed a youtube video and guide.
Found out I ended up doing a different OS version that didnt match.
Click to expand...
Click to collapse
TWRP for the 8T works reasonably well. See https://forum.xda-developers.com/t/...recovery-project-8t-kebab-2021-09-04.4302449/