I mistakenly downloaded and attempted to flash the latest factory image for a Pixel 4 (5G) to my Pixel 4a.
My phone is now stuck on a black screen and I'm unable to boot into the bootloader so that I can flash the correct factory image.
The device does some to be on in some fashion as when I plug it into my computer windows alerts me that it's setting up a USB device.
i dont know what to do ?
please help me as i saw in one of the threads you had the same problem so please can you help me
It's worth a shot to try the stuff in this thread - maybe you luck out and have better results:
[Help Wanted] [Bricked] Accidentally Flashed Factory Image for Pixel 4a (5G)
I mistakenly downloaded and attempted to flash the latest factory image for a Pixel 4 (5G) to my Pixel 4a. My phone is now stuck on a black screen and I'm unable to boot into the bootloader so that I can flash the correct factory image. I've...
forum.xda-developers.com
I am not sure if you saw the following thread where just recently Spaceminer posted an *.mbn file for the Pixel 4a.
Related
I have a moto x pure edition running android 6.0 that I am attempting to root. I managed to unlock the boot loader without incident and found a guide for rooting http://forum.xda-developers.com/mot...e-edition-superboot-style-root-motox-t2889264 i downloaded the boot image and used cmd to boot my phone with that image. the image transferred and my phone started booting. The only problem is my phone can't get passed the load screen. I have tried factory reset, normal boot and recovery all to no avail. Could anyone be able to tell me what I am doing wrong or recommend a different boot image? Any help would be amazing!
[UPDATE] I found the correct boot image and managed to boot into my phone. I installed superSU and tried to update the binary but it continually fails. Any ideas?
tedkoch00 said:
I have a moto x pure edition running android 6.0 that I am attempting to root. I managed to unlock the boot loader without incident and found a guide for rooting http://forum.xda-developers.com/mot...e-edition-superboot-style-root-motox-t2889264 i downloaded the boot image and used cmd to boot my phone with that image. the image transferred and my phone started booting. The only problem is my phone can't get passed the load screen. I have tried factory reset, normal boot and recovery all to no avail. Could anyone be able to tell me what I am doing wrong or recommend a different boot image? Any help would be amazing!
[UPDATE] I found the correct boot image and managed to boot into my phone. I installed superSU and tried to update the binary but it continually fails. Any ideas?
Click to expand...
Click to collapse
Hi and thank you for using XDA Assist
If you still couldn't find anything then
Try asking here
You will find for sure the answer from the other users
Good luck!
I was on DP2, with root and unofficial twrp-3.0.2-3-angler(previous versions had problems). And had google assistant too with modified build.prop. Today I flashed a zip file for pixel features. But after reboot, it stuck on the new pixel boot animation. I then applied a rollback zip file, now it is showing the old boot animation, but still stuck. I have wiped cache/dalvik.
I had a password set during boot. Previously, it used to ask for password, but not now. TWRP is now showing unable to mount storage. I don't know where the problem is. Is it the boot password? Please help. Thanks in advance.
Importantly if I wish to flash factory image, then can I flash the final build of 7.1.1(NMF26F)? Earlier I was on DP2. (npf26f).
ikaushalsha said:
I was on DP2, with root and unofficial twrp-3.0.2-3-angler(previous versions had problems). And had google assistant too with modified build.prop. Today I flashed a zip file for pixel features. But after reboot, it stuck on the new pixel boot animation. I then applied a rollback zip file, now it is showing the old boot animation, but still stuck. I have wiped cache/dalvik.
I had a password set during boot. Previously, it used to ask for password, but not now. TWRP is now showing unable to mount storage. I don't know where the problem is. Is it the boot password? Please help. Thanks in advance.
Importantly if I wish to flash factory image, then can I flash the final build of 7.1.1(NMF26F)? Earlier I was on DP2. (npf26f).
Click to expand...
Click to collapse
Greetings and welcome to assist. It appears you have already asked your question in the correct place here
http://forum.xda-developers.com/showthread.php?t=3517583
So I will close this one up
Good Luck
Sawdoctor
Bootloader: mw998-002.0072.00
Product Revision walleye MP1
I have been trying, unsuccessfully, to flash a clean build (no changes) of AOSP 9.0.0_r10 (walleye) for the Pixel 2. I'm not building any differently for the Pixel 2 than when I was building for the Pixel so I doubt this is a build problem.
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash vendor vendor.img
After finishing the flashing I reboot and the phone goes back to the bootloader and displays an error in yellow at the bottom:
ERROR: LoadImageAndAuth Failed: Load Error
Happens every time. I have no trouble going back to the Factory image but when I try to flash this AOSP one I get the error.
I've done some reading both on XDA and elsewhere and I know other people have run into this error message, though for different scenarios (custom ROM flashing, Android 8 flashing, OTA side loading, etc) but I haven't seen anyone report a problem flashing straight unmodified AOSP builds.
I tried switching boot partitions. Didn't help. I tried both Lunch options for Walleye builds. Didn't help. I haven't been able to side load any build/zip file...not without getting this error.
One thing I did discover this morning. I was cleaning up the Pixel 2 and putting Factory back on it since I had run out of ideas on getting around this issue. I was on Partition A at the time. I flashed the Factory on to A and set it up the device. I then remembered I had the busted AOSP on B so I switched to B and flashed Factory on that partition. I rebooted and set up the device. Then just for giggles I switched back over to A again (which I had already set up for Factory) and rebooted. BANG! I got that error. I had successfully put Factory on A but after switching to B and putting Factory on there and then switching back to A and rebooting, A was now failing. I have no idea of the significance, if any, of this but I thought I would mention it.
Using TWRP or Magisk is not a path I want to go down if at all possible. By rights, flashing AOSP should work on an unlocked non carrier Pixel 2. I've heard that flashing on the Pixel 2 is more convoluted than on the Pixel and I believe it. Hopefully Pixel 3 won't be even worse.
As always if anyone has any ideas or guidance, I'm all ears. Thanks in advance.
Hi all,
You guys might have some more insights.
Recently the phone has been acting up and won't boot past the Google Logo (not even getting to Android Logo)
First of all I've tried the wipe data and factory reset. Didn't work, same issue.
I did enter the recovery mode and sideloaded the latest OTA sargo for my device found here :
[link removed]
The phone won't boot past google logo then turn off.
The bootloader is locked and I don't know how to unlock since I can't access the OS.
I was thinking about flashing it with a stock image from Google found here
[link removed]
Any help is much appreciated.
Thanks
I had the same issue. My issue was probably that after unlocking bootloader I did not reboot, but just flashed magisk patched boot.img. As a result my phone was boot looping with G-logo. The way out was to
a) flash stock boot.img
b) wipe data and cache
c) reboot and initialize, enable dev options...
d) flash magisk patched boot.img
e) success
I got a pixel 4a and attempted to flash calyx os but got stuck in fastbootd.
I waited for 15 mins and nothing happened so i tried to reboot.
Now my device is bricked and flashing stock firmware isn't working.
Also says no valid slot to boot in fastboot mode. Pls help, i have been trying to fix this for hours.
EDIT: Solved - turned out to be a bad usb cable.
I just want to return to stock android.
technoph0bian said:
I got a pixel 4a and attempted to flash calyx os but got stuck in fastbootd.
I waited for 15 mins and nothing happened so i tried to reboot.
Now my device is bricked and flashing stock firmware isn't working.
Also says no valid slot to boot in fastboot mode. Pls help, i have been trying to fix this for hours.
Click to expand...
Click to collapse
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Fixed the issue, will be flashing calyx again when the android 11 version comes out.
Calyx has a device flasher tool which u can find on their subreddit. Makes flashing calyx really easy