[FIXED] Pixel 4a bricked after flashing Calyx OS - Google Pixel 4a Questions & Answers

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

Related

Stuck on one plus 6 fastboot screen

Hi guys,
I was trying to switch OS in my oneplus 6 and accidentally did something. All i can see now is fastboot mode screen. need help restoring.
i got same problem today when switching from Open beta 2 . something is broke with ob2 i think . anyway download latest rom from this link
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
use flash-all-partitions-fastboot.bat to get your phone back . beware it format all partitions .
i did the same at a point, fixed it by fastbooting twrp and started flashing all over again
edit: actually this might've worked only because i was running a custom rom with usb-debugging enabled by default

My OP 7 PRO(GM21AA) is being completely stuck at Fastboot.

Hey,
It's been always a huge headache since when the Android 10 beta and stables updates are out to root and install twrp. I've tried almost every way possible but every-time, end up being stuck at TWRP or being half way rooted. This time I've tried doing that again :
* I was at OxygenOs Android 10 stable version,
* My bootloader was unlocked as well as OEM unlocking and usb debugging was on,
* I turned my phone into fastboot, and flash the twrp image as:
fastboot flash boot file.img
Then after my phone booted into TWRP since once or twice showing that 0mb internal storage, I flashed the Magisk.zip from adb command, and rebooted it.
Since then, my phone is completely stucked at fastboot, I've tried and followed almost every xda suggestion and everything, I've tried flashing flash.bat file, I've tried flashing stock recovery, In fact I've tried flashing complete fastboot Rom (with all in one app)and it everytime boots me into Fatboot.
Please, help me out guys. I'm stressed out of this problem since yesterday's night.
Let me know your suggestions.
Maybe THIS can help you?
Actually this thread helped me just now in the same situation:
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
That thread Jonsat mentioned didn't help me either, at all. Its not very clear that thread, telling in the thread to unbrick a OP7 to look at the thread of the OP6, there send them to OP5 and so on, eventually having to use a short written manual for the OP3 which mentions different versions and so on, its not the best for inexperienced people like me, it just send me on a wild chase downloading drivers and other things that eventually didnt work at all. Maybe I will try to rewrite it, as soon as I have enough experience to do so, i own this device for just a week.
Next time, read before you peform the install steps. It's nowhere like the older devices due to the A/B Recovery.
1. Use MSM Downloader to put you back to stock.
2. Upgrade to Android 10
3. Factory Reset to Clean out your phone (don't forget to unlock bootloader)
4. Initialize phone
5. Boot twrp (specific to Android Q + OP7 Pro)
6. Install TWRP and Magisk from TWRP
7. reboot and enjoy your rooted phone
lloydlim996 said:
Next time, read before you peform the install steps. It's nowhere like the older devices due to the A/B Recovery.
1. Use MSM Downloader to put you back to stock.
2. Upgrade to Android 10
3. Factory Reset to Clean out your phone (don't forget to unlock bootloader)
4. Initialize phone
5. Boot twrp (specific to Android Q + OP7 Pro)
6. Install TWRP and Magisk from TWRP
7. reboot and enjoy your rooted phone
Click to expand...
Click to collapse
What is MSM download tool? I'm going to try using All in One.
On searching for MSM tool, I found https://www.techoxygen.com/msm-download-tool/ is that correct?
Scratch this, MSMdownload is part of zip, I'll read through https://forum.xda-developers.com/showpost.php?p=79972789&postcount=50 and see how it goes

Bricked oneplus 6

It's been 10 days since my oneplus 6 bricked itself and matter of fact i didn't do anything in it although i was gonna flash a custom rom on it and for flashing when i rebooted it into bootloader mode and then connected it to my laptop it just restarted itself and since then it is stuck on oneplus logo i have tried every possible flashing guide available for this device and every flashing getting completed perfectly but result is same it just stuck on logo an by now i have understand the problem is related to hardware until unless some angel in disguise help me out
are u try MsmDownloadTool ? what happen after ? could access to stock rom ?
metrixx02 said:
are u try MsmDownloadTool ? what happen after ? could access to stock rom ?
Click to expand...
Click to collapse
I have tried that too and my device got successfully flashed with bootloader relocked again but device is stuck on logo
Did you try fastboot stock roms?
°Washy said:
Did you try fastboot stock roms?
Click to expand...
Click to collapse
Yup
In that case it would be possible to open the botloader again? If so, try this, it is obvious that you flashed an Android 10 rom ..
step 1: reinstall the twrq maunofrio Q and flash a rom oxygen of android pie the last one if possible 9.0.9 (this only to be able to change twrp, the same will still be in bootlop, but now if you get the twrp of android 9 )
step 2: flashea twrp enchilada 3.3.1-2 img, already in recovery flashea twrp 3.3.1-2.zip and restart in recovery.
step 3: download exactly the rom 34 that would be the rom 9.0.6 I think (OnePlus6Oxygen_22_OTA_032_all_1906251226_0033d1285cf04df0.zip) you flash and do not install anything else you just start the system .. nothing more as long as I stay in bootloop I do that and it has always saved me. pdt, I speak Spanish sorry for my translation
Have you got backup of your EFS partition? If yes you can try use MSM tool and SMT Donwload mode. As password use: te123. It will reflash your phone completely, but there will be no modem, imei, wifi, bluetooth, etc. Don't do that if you didn't backup your modem/efs.
To use SMT Donwload mode you have to click Verify and after that select SMT. After that MSM change border to red. Check also SMT menu in the upper left corner and set checkboxes of all your COM ports in new opened window.
Why not format data. That will fix phone!

Lenovo Tab 4 10 plus 30 second boot loop

How can in get out of this boot loop, any advice, answers, help appreciated?
As background my Lenovo Tab 4 10 plus (stock 7.1 rom) had a failed SD card so I replaced the card and factory reset and thought I would try TWRP, Linageos 17.1 with magisk and relevent gapps - this all worked fine other than a Skype issue. I then found an 18.1 rom and tried that and this is where it seems to have gone wrong I set it up in the same ways as the 17.1 rom but with Andriod 11 gapps to suit, did a factory reset and 30 seocnds in I got the boot loop.
To fix it I tried going back to the 17.1 rom set-up that had worked but this then boot looped even with a full recovery reset. I have gone back to the stock rom backup in TWRP again with a recovery reset same boot loop. I have even used the Lenovo recovery tool to EDL mode flash a newly downloaded stock rom and it's still boot looping. I can only think that the 18.1 andriod 11 rom changed something fundimental but I can't find what?
Further I have another problem, the EDL flash worked but it locked the bootloader, however as I can't get in to Andriod with the boot loops, I can't switch ADB mode on so I can't unlock the bootloader to get TWRP up again.
So is there a way to start ADB without access to develeoper settings maybe through fastboot or recovery which I can get in to? Unlock the bootloader without ADB? Does anyone know why after the 18.1 Andriod 11 based rom, I have this continous boot loop?
I have a tb-x704f wich was totally caught in a boot loop, but I manisched to get back to working stock.
I was running firmware s000056 when I flashed twrp without backing up anything. I thought I never would have to go back to nougat, but standby time on lineage os was just not good for me, as I only use my tablet maybe half an hour a day, and I had to charge several times a week nevertheless.
So I tried to get back to stock and awesome standby time.
It was not easy bootloop after bootloop.
Tried Lenovo rescue and smart assistant multiple times, factory reset before and after flash, without SD card inserted etc, but bootloop.
Tried flashing the rom downloaded from the rescue tool with qfil but same result.
I then tried flashing the files with miflash 2016.08.30.0 still the same rom as I thought it had to be s000056. Miflash stopped halfway with some kind of error.
I then downloaded a stock rom from lenovo-forums.ru http://lenovo-forums.ru/topic/24135-lenovo-tab4-a10-plus-proshivka-tb-x704f_s000037_170703_row_qfil/
from the link in the discussion in the bottom of the site.
I had twrp still so from there I got into terminal and wrote "reboot edl" to get into emergency download mode and then flashed away. I presume that I could just as well had gotten in to edl mode by pressing vol+ and vol- simultaneously and then connected to PC holding those to buttons pressed. When the tablet was finished it was off, so I started going to recovery and wipeed cache and did a factory reset. Then booted and instead of bootloop it showed the Lenovo screen with a progress bar underneath. I successfully booted and took a update and then i am back to stock s000056.
The rom I got from lenovo-forums.ru stated it was only for EU and wi-fi model only. I am in Denmark and my tablet is WiFi only.
I think chances for success is greater using miflash than other tools when recovering from bootloop, but then again I don't know. Maybe I could just have flashed the s000037 rom with qfil or maybe I was just lucky, who knows.
But this what worked for me.
I hope this can help someone as I could not with the help of god find any useful help regarding this problem.
pallep said:
I hope this can help someone as I could not with the help of god find any useful help regarding this problem.
Click to expand...
Click to collapse
Thanks kind man You helped finish my struggle!
The only thing I want to add is that the ROM from the original link is no longer available, so I found the correct ROM using Google from the original filename here https://firmware247.com/lenovo-tab4-a10-plus-tb-x704f-firmware/

Can't boot to recovery, want custom ROM

Hi everyone,
Currently I can only boot to fastboot mode - i.e. not recovery or the system. I don't want to go back to OOS. When I try to flash or boot to recovery, nothing happens and the boot does not work. I'm not sure where to go to from here - do I need to flash stock ROM? I don't even know what version of Android the phone was on...
Edit: Partly fixed, as per below.
I ended up flashing the stock ROM using the MSMDownloadTool:
How To Unbrick OnePlus 6/6T
Download %
networktips.in
At some point I'm going to try using Magisk to flash LineageOS.
OK, got onto LineageOS using this:
Install LineageOS on enchilada | LineageOS Wiki
wiki.lineageos.org
I used this the first time around, so I'm not sure what went wrong. I suspect it was either the fact that it was on Android 11 or that I might have somehow messed up flashing the recovery file.
Anyone doing the sideload with ADB should be aware that it reports a 47% completion rate with success. The flashing has still completed successfully, read the last comment here:
https://www.reddit.com/r/LineageOS/comments/af12lu

Categories

Resources