Hello,
Explain my experience with the BQ E6 (more info bq.com/es/support/aquaris-e6/support-sheet)
You need to be root to use an application, I did this with the following procedure provided by the manufacturer, installing a Recovery custom:
mibqyyo.com/comunidad/discussion/37470/recovery-custom-y-root-e6/p1
At the end of the process received an error "PMT changed for rom, must be downloaded" and no longer started android, it was constantly restarting.
I tried to reinstall the recovery but get the same error.
I looked for another solution, to make a Hard Reset and to reinstall all the firmware according to these indications of the manufacturer:
mibqyyo.com/articulos/2014/06/04/hard-reset-smartphone-gama-aquaris-e/
The procedure I did without problems and then started the mobile with the factory parameters, I configured some things and left, after a while I wanted to continue but the mobile was off. When I started it again it was on the white screen of BQ and it did not start.
I went back to make a Hard Reset in case I had done something wrong, the whole process was correct and then started the system again, I configured some parameters but after a while it was the same, turned off and it did not start.
I repeated the Hard Reset a third time, but after 20 seconds of starting it goes off.
Commenting that a forum partner told me that when connecting the mobile to the usb to start the copy from Flash Tools did so by pressing the + button of the volume (without getting better result).
I installed another recovery (TWRP) and other rooms (CyanogenMod13 / Miui-7), everything installs correctly but in all cases within 20 seconds of starting it goes off.
The TWRP recovery is accessed correctly and for a long time you use it does not shut down, it is when android starts.
Has anyone ever had something similar and know what I can do?
Thank you very much
jucuegas said:
Hello,
Explain my experience with the BQ E6 (more info bq.com/es/support/aquaris-e6/support-sheet)
You need to be root to use an application, I did this with the following procedure provided by the manufacturer, installing a Recovery custom:
mibqyyo.com/comunidad/discussion/37470/recovery-custom-y-root-e6/p1
At the end of the process received an error "PMT changed for rom, must be downloaded" and no longer started android, it was constantly restarting.
I tried to reinstall the recovery but get the same error.
I looked for another solution, to make a Hard Reset and to reinstall all the firmware according to these indications of the manufacturer:
mibqyyo.com/articulos/2014/06/04/hard-reset-smartphone-gama-aquaris-e/
The procedure I did without problems and then started the mobile with the factory parameters, I configured some things and left, after a while I wanted to continue but the mobile was off. When I started it again it was on the white screen of BQ and it did not start.
I went back to make a Hard Reset in case I had done something wrong, the whole process was correct and then started the system again, I configured some parameters but after a while it was the same, turned off and it did not start.
I repeated the Hard Reset a third time, but after 20 seconds of starting it goes off.
Commenting that a forum partner told me that when connecting the mobile to the usb to start the copy from Flash Tools did so by pressing the + button of the volume (without getting better result).
I installed another recovery (TWRP) and other rooms (CyanogenMod13 / Miui-7), everything installs correctly but in all cases within 20 seconds of starting it goes off.
The TWRP recovery is accessed correctly and for a long time you use it does not shut down, it is when android starts.
Has anyone ever had something similar and know what I can do?
Thank you very much
Click to expand...
Click to collapse
Wysłane z mojego HUAWEI CUN-L21 przy użyciu Tapatalka
Hello,
After a week I have good news,
I omitted content because I thought it was not relevant, but it was.
I recently broke the screen and I changed it.
Everything worked fine, but in the process the camera was damaged and only focused on infinity.
It seems that the problem was bigger and it was the fault that caused not being able to start the system.
Start the cell with the power and volume (-) button, then I entered the test menu and I passed the test, until I got to the camera and then suddenly the cell phone turned off.
I opened the phone and I removed the camera and now starting normally.
Many thanks to those who have interested you and those who can serve you in the future, although it is rare that damage the camera.
How u fix ur BQ E6 ? What firmware u flash ?
plzz help me
BQ E6 flash
zazi1991ix said:
Wysłane z mojego HUAWEI CUN-L21 przy użyciu Tapatalka
Click to expand...
Click to collapse
Hello,
it's been some years ago now, but do you still have the instructions from page mibqyyo.com/articulos/2014/06/04/hard-reset-smartphone-gama-aquaris-e/
to install a different ROM? That page isn't available anymore.
Related
I am pretty sure I know the answer but want to make sure its true as its a costly issue: I did some searching and found a lot of threads with different options over the last few years, so just want to confirm; I have:
Asus Transformer Prime TF201, unlocked with latest ICS official (WW) installed via SD Card
I was intending on giving the tablet away to a family member, so decided to factory reset the device. I went to the PWR+VOL Down menu, and selected wipe which I read was the way to perform a factor reset. After a long time of this process, the tablet powered off (was plugged into mains with full batteries). I powered on by pressing PWR button some time later. Now the tablet just boots onto the screen that states "The device is UnLocked" in the top left, ASUS in the middle (and some lies about perfection), and the bottom right "Powered by Nvidia TEGRA".
If I power on:
1. PWR + VOL Down, nothing happens, it boots to the same screen, no menu
2. PWS + VOL UP, the screen is black, the tablet vibrates and if i have it plugged into a PC it detects it in APX mode.
I've tried a full power cycle, and read about the nvflash tool. I unfortunately have no nvflash backups, I'm not sure that tool was around when I unlocked the tablet, and as i'd not been flashing any custom roms (although I had intended) I'd not seen that tool before.
As I understand the state of affairs is:
1. Somehow the bootloader is jiggered, i guess the wipe didn't work right
2. APX is useless if you don't have some backups created with a tool
3. The only current solution is to send it to ASUS and pay almost exactly the same price as a new tablet costs
Is there any other options I can do with an unlocked tablet and only access to APX?
Any likelihood that there is anything that can be done with nvflash in the future without needing a custom backup that is unique per tablet?
I have exactly the same problem please someone help us :angel:
virus4o said:
I have exactly the same problem please someone help us :angel:
Click to expand...
Click to collapse
I have the same problem too. Only apx.
Please, Anyone knows any solution for this issue?
Same problem while flashing CM
Aduniel said:
I have the same problem too. Only apx.
Please, Anyone knows any solution for this issue?
Click to expand...
Click to collapse
My tf is in the same state. Got there when trying to install CM's nightly build.
Bricked TF201 - Stuck in bootscreen
I have the exact same problem. :crying:
Please, I know that there are many brilliant minds in this forum, help us n00bs get out of this mess and lead us into the light. Oh, and bump this thread
I hate to be the bearer of bad news, but I hate hit and run thread posters so I will provide an update.
I am afraid that my tablet was bricked. No way back from that state after reading the entire internet. I have purchased a replacement motherboard, popped open the case and replaced this. After replacing the motherboard, I now have a working tablet. I wish someone would have documented the NVFlash process requirements previously, but that's the risk of following guides on android sites I guess.
So to summarise the initial post, if you are in that state, at current and likely forever, you are hardbricked and the tablet can not be recovered in that states without a previous backup. The only way for it to be repaired is to send it to Asus who have a database of firmware, etc. and will charge you for repairs (~200€), or to go on ebay and purchase this motherboard:
0K0AMBA000
This will cost you ~80€ + shipping, and you must be comfortable working with electronics. Its mostly very clear when you pop off the case, everything has its place. You will need some plastic case pries and a small screw driver.
spudthedestroyer said:
I hate to be the bearer of bad news, but I hate hit and run thread posters so I will provide an update.
I am afraid that my tablet was bricked. No way back from that state after reading the entire internet. I have purchased a replacement motherboard, popped open the case and replaced this. After replacing the motherboard, I now have a working tablet. I wish someone would have documented the NVFlash process requirements previously, but that's the risk of following guides on android sites I guess.
So to summarise the initial post, if you are in that state, at current and likely forever, you are hardbricked and the tablet can not be recovered in that states without a previous backup. The only way for it to be repaired is to send it to Asus who have a database of firmware, etc. and will charge you for repairs (~200€), or to go on ebay and purchase this motherboard:
0K0AMBA000
This will cost you ~80€ + shipping, and you must be comfortable working with electronics. Its mostly very clear when you pop off the case, everything has its place. You will need some plastic case pries and a small screw driver.
Click to expand...
Click to collapse
This sucks, I did the same exact thing last night factory resetting it to give it to my brother. I still don't understand what exactly I did wrong as I've factory reset this thing before. I had CM on it before but have been using the stock rooted ROM & recovery for the past 6+ months.
bricked?
I've been scouring that internet and haven't been able to find a case exactly like mine, but most are similar. From what I can remember (it's been months since I initially 'bricked' it), I was upgrading a cm nightly and did the data/cache/dalvik wipe like the instructions said and I became stuck in a bootloop after leaving recovery. When I tried volume-down and power, I was left with the original 3 options and after some reboots and shutdowns I ended up doing a factory data wipe. From there, when I rebooted the phone I was left with just 'Wipe Data' and 'Fastboot.' Wipe data does nothing more and when I choose fastboot I am left a message 'Starting fastboot usb download protocol' which never changes.
I have tried to push TWRP onto the device but I can't get into recovery (unless I'm doing something wrong of course). Sorry if I missed a duplicate of my post somewhere on here, but if so can someone at least point me in the right direction? Thanks!
i.imgur.com/LEHNREw.jpg
try another ROM
This has worked for me everytime, possibly due to dud bootloader install or some other thing: so long as I was able to recover to CWM with pwr+vol down, I installed virtuous prime rom. This rom was on sdcard already, not sure if you can get from adb if machine in this state. Anyhow, this virtuous prime rom replaced the booting sequence, restored OS and machine worked again.
Asus TF201 stuck on Asus Logo
My Asus Tablet was slow while browsing, and it had JB 4.1.1 with stock rom, so i tried to unlock the device, which was successful and was planning to push the CM11 Kit Kat. I booted in to recovery mode as i could see the 4 icons and then tried to do wipe data/factory reset and then it rebooted and got stuck on the asus logo and at the right bottow with the message powered by NVIDIA Tegra. I tried all the options to get into recovery and also downloaded drivers on my laptop for APX, but no luck at all. What are my options or if any one was successful to get it fixed. Appreciate any help here from smart guys out there. Thanks
spudthedestroyer said:
I am pretty sure I know the answer but want to make sure its true as its a costly issue: I did some searching and found a lot of threads with different options over the last few years, so just want to confirm; I have:
Asus Transformer Prime TF201, unlocked with latest ICS official (WW) installed via SD Card
I was intending on giving the tablet away to a family member, so decided to factory reset the device. I went to the PWR+VOL Down menu, and selected wipe which I read was the way to perform a factor reset. After a long time of this process, the tablet powered off (was plugged into mains with full batteries). I powered on by pressing PWR button some time later. Now the tablet just boots onto the screen that states "The device is UnLocked" in the top left, ASUS in the middle (and some lies about perfection), and the bottom right "Powered by Nvidia TEGRA".
If I power on:
1. PWR + VOL Down, nothing happens, it boots to the same screen, no menu
2. PWS + VOL UP, the screen is black, the tablet vibrates and if i have it plugged into a PC it detects it in APX mode.
I've tried a full power cycle, and read about the nvflash tool. I unfortunately have no nvflash backups, I'm not sure that tool was around when I unlocked the tablet, and as i'd not been flashing any custom roms (although I had intended) I'd not seen that tool before.
As I understand the state of affairs is:
1. Somehow the bootloader is jiggered, i guess the wipe didn't work right
2. APX is useless if you don't have some backups created with a tool
3. The only current solution is to send it to ASUS and pay almost exactly the same price as a new tablet costs
Is there any other options I can do with an unlocked tablet and only access to APX?
Any likelihood that there is anything that can be done with nvflash in the future without needing a custom backup that is unique per tablet?
Click to expand...
Click to collapse
I had messrd up my tf101 with cm nightly to. I did manage to get it working again with adb tool of sorts. When im home i will tr y to find it on my comp. Th
Hello everybody,
as of yesterday I am in the Stone Age again using an old phone of mine.
What happend? No clue - the phone went off after recieving a SMS message in power saving.
When trying to put on: No reaction.
Connect to Energy Outlet: LED RED - leave hours - LED OFF
Retry on Button: No reaction.
Tryed following I read here: Press Red Reset before conecting to Laptop - It did something good! I hear the sound of connection. No Icons apear though! No recognition of device on the File Manager. Sound comes frequently, connect - disconnect - loop I guess.
Strange Symtoms received days before: I was in Japan on visit. Recieved about 30 messages of the program Google App, that it had to shut down. Asking confirmation. It never ended, so I turned phone of. After turning on, everything ok. Thought it had to do with local google in Japan.
Battery: loading felt very hot, phone felt hot. But after disconection worked.
Returning form Japan to home: google.app close down problem again. Endless confirmation. Stoped loop with disconection again.
Made reboot with red button on back.
PHONE lifeless.....no reaction, help! How to acces, so I can flash? or is it a battery problem? (ordered just one just to try)
Rom Installed: SLXROM_v11-Lenovo_P780 - in the year 2013.
101Maclaren said:
Hello everybody,
as of yesterday I am in the Stone Age again using an old phone of mine.
What happend? No clue - the phone went off after recieving a SMS message in power saving.
When trying to put on: No reaction.
Connect to Energy Outlet: LED RED - leave hours - LED OFF
Retry on Button: No reaction.
Tryed following I read here: Press Red Reset before conecting to Laptop - It did something good! I hear the sound of connection. No Icons apear though! No recognition of device on the File Manager. Sound comes frequently, connect - disconnect - loop I guess.
Strange Symtoms received days before: I was in Japan on visit. Recieved about 30 messages of the program Google App, that it had to shut down. Asking confirmation. It never ended, so I turned phone of. After turning on, everything ok. Thought it had to do with local google in Japan.
Battery: loading felt very hot, phone felt hot. But after disconection worked.
Returning form Japan to home: google.app close down problem again. Endless confirmation. Stoped loop with disconection again.
Made reboot with red button on back.
PHONE lifeless.....no reaction, help! How to acces, so I can flash? or is it a battery problem? (ordered just one just to try)
Rom Installed: SLXROM_v11-Lenovo_P780 - in the year 2013.
Click to expand...
Click to collapse
Seems to be a motherboard problem!
Hi stympy
Need to to identify if this is motherboard issur or ROM.
My phone purchased in Jan 2014. It has been updated to official rom 4..2.2 using OTA. No other unofficial ROM being install before. In Jan 2015 the screen broken so we send in to local repair shop.
Problem started here, after repaired (just change lcd screen) the phone behave restart/blank once a while. Due to different problem the workshop does not cover the warranty (due to different issue). But the workshop recheck if problem with connection of lcd and motherboard. No problem here. In March 2015 it become unusable because once power on P780 8GB (international version), it keep bootloop at lenovo startup and the logo yet to flip it gets reboot again.
In an attempt to revive it (hope it is ROM issue), hard reset done but still the same. Try to flash with v5 (manually install drivers MTK and USB) but v5 cant detect the phone. Device manager shows the driver installed successfully but with a warning sign. Properties says something like "the device does not start correctly". FYI, I cant access the phone's SD card from My Computer. Sometimes it appear a Lenovo logo to install some software (red icon)
So is there any "hard reset" i can do or it is the motherboard issue? Worse come to worse, Is it advisable to change motherboard?
expzero said:
Hi stympy
Need to to identify if this is motherboard issur or ROM.
My phone purchased in Jan 2014. It has been updated to official rom 4..2.2 using OTA. No other unofficial ROM being install before. In Jan 2015 the screen broken so we send in to local repair shop.
Problem started here, after repaired (just change lcd screen) the phone behave restart/blank once a while. Due to different problem the workshop does not cover the warranty (due to different issue). But the workshop recheck if problem with connection of lcd and motherboard. No problem here. In March 2015 it become unusable because once power on P780 8GB (international version), it keep bootloop at lenovo startup and the logo yet to flip it gets reboot again.
In an attempt to revive it (hope it is ROM issue), hard reset done but still the same. Try to flash with v5 (manually install drivers MTK and USB) but v5 cant detect the phone. Device manager shows the driver installed successfully but with a warning sign. Properties says something like "the device does not start correctly". FYI, I cant access the phone's SD card from My Computer. Sometimes it appear a Lenovo logo to install some software (red icon)
So is there any "hard reset" i can do or it is the motherboard issue? Worse come to worse, Is it advisable to change motherboard?
Click to expand...
Click to collapse
Hi. Before i give a verdict with your phone i need to see something. Can we do a team viewer sesion?
Send me an PM with id and pass in 7 hours from this message! .
I need an information about your PC or notebook. What windows do you use?
This happened to me several times exactly the same condition
What you have to do: Do not never charge it and left it for several days until the battery is discharged -With pressing the power button from time to time-
Then recharged I think this work
I advise you to use STOCK ROM
Hi sym,
We need another time to teamviewer. Just saw your reply.
But i believe u cant get anything as from my side i cant even get any respond from the phone with drivers installed.
u got pm
Hey guys, please forgive me for any bad etiquette or lack of information (any information I can provide is available upon request if I leave anything out). I am new to forums in general and especially to XDA, which seems like a good place to get help.
I recently purchased a Sony Xperia Z2 Tablet from Craigslist under the assumption it was a fully unlocked tablet not associated to a carrier. Turns out it was a Verizon Z2 tablet. I dislike Verizon with a firey passion and without getting into too many details, I'm fairly certain they won't help me because a) this tablet wasn't purchased through them as a customer and b) Verizon and I have bad history (unauthorized account modification, shady charges, etc.)
So I thought I'd do my best to make the tablet mine since the asshole who sold it to me has ceased all contact and I don't know how to get a hold of him anymore. No receipt and a data-less tablet.
Anyway, I successfully rooted the tablet and began installing apps that I installed for my G4 when I rooted it (SuperSU, Adaway, Greenify, etc.)
Things were going well but I realised I wanted anything that had to do with Verizon removed from the tablet so I was going to flash Cyanogenmod onto it with a guide I found online. Now rooting and installing custom recoveries was familiar territory and I did these flawlessly. It had TWRP and I made a backup of the system -no Nandroid, sadly-and I began the flashing process. The process said it completed without issue and I went to reboot my device. Enter my current situation:
The device, when I attempted to turn it on, all it did was vibrate constantly until I let go of the power button. Attempting to enter recovery mode (green LED, power + vol down) it showed me, instead of TWRP, a very basic recovery mode with basic options. "Continue booting up", "enter safe mode", "system recovery", and "power down". I tried entering safe mode and it just shut back down, I tried doing a system recovery and it shut down. The only time I ever see the "SONY" logo is if I'm entering this mode. I can enter what I assume is "fastboot mode" (power + vol up and plugging the device into a PC). Nothing on the screen but the LED is blue. I am trying to find guides to restore it if I can and it all looks promising but the only things I know how to really do are root and install custom recovery. I know there are PC tools I can use to send commands to it while it's in fastboot, or send commands in general I just don't know where to begin.
Does anyone know how to fix this? I know it was from Verizon, which sucks, and I know the problem most likely occurred with the attempted flashing of Cyanogenmod. I think I read somewhere I might have done something regarding mismatching kernal numbers. I couldn't find a way to unlock the bootloader so I assume that had something to do with it too.
If someone could give me a guide to restore it to at least its stock ROM where I can begin rooting and installing a custom recovery again, that would be great. Even better would be just flashing a ROM on there that doesn't need Verizon or being able to take it to a stage where it's unlocked and the only evidence it was ever with a carrier is the Verizon logo on the back. I'd really hate to think I wasted money on this and now I'm at a dead end because of a mistake I made. This was supposed to be a gift for my mom on her birthday which is coming up soon. So if anyone knows anything, or has a guide where we can at least get the thing bootable again and I'll just try and deal with a rooted locked device, that would be great.
Thanks for considerations,
Marmalade_Shaws
I have spent time on that screen too.
2 things
1. .. If you installed dual recovery, there is an up, down sequence to select the recovery.
2. Find a downgrade guide, use flashtool to flash. Ft back to stock.
Also you need to know what hardware you are running..511, 561.. And use the proper version.
There are some options with the flashtool and prf maker that can remove branding and vendor stuff. I have not tried those options.
Ez-go said:
I have spent time on that screen too.
2 things
1. .. If you installed dual recovery, there is an up, down sequence to select the recovery.
2. Find a downgrade guide, use flashtool to flash. Ft back to stock.
Also you need to know what hardware you are running..511, 561.. And use the proper version.
There are some options with the flashtool and prf maker that can remove branding and vendor stuff. I have not tried those options.
Click to expand...
Click to collapse
Sorry if this is late... But where can I find the stock? I've searched everywhere and I would need to do it from a flash tool on my PC? I could use all the help I can get.
I just had a very similar experience to the OP, seemingly identical in every way, and am curious if anyone has a solution.
ADB won't function at all, and the bootloader has blocked any sort of flashing via fastboot. Can't boot into TWRP, it goes into a very minimal "recovery," which I imagine is the stock tool, and the Factory Restore option there does absolutely nothing. Flashtool would work great if ADB / Flashmode was at all functional (device blinks and vibrates in a fashion typical of something bricked, and no connection is picked up).
Verizon Z2 Tablets are 561s.
This thing dead or is there some way to push back onto it?
Hi guys, sorry if I posted this at the wrong place.
I have a Lenovo s860 and it went into a bootloop. It was stock and all so I thought that I can have my files recovered if I just bring it to a service center so they can get the files first before wiping it or maybe even fixing the bootloop without wiping the device. Well, the thing is, the guy at the service center screwed up and now, when I try to turn it on, I still see the boot screen (Lenovo, powered by Android) but the next screen is like an television with bad signal.
I'm familiar with rooting and flashing ROMs, I've tried it on my Galaxy S2 (yeah I know, it was way back), but I think things are still more or less the same: I need to be able to boot into recovery mode in order to root the device. However, when I tried the Power Button + Volume Up, or any combinations of the Power Button and the Volume Buttons, it just goes straight to the dead screen, I get no response whatsoever.
I also tried to check if adb can detect it, however, it didn't seem to be able to do so. I'm using a MacBook Pro so I know I don't have to install any drivers, I also code Android Apps so I have a background on this.
I think my only option would be to flash the ROM on this dead device but I don't know how to do that. I've also seen some posts that suggest doing some things (I forgot the specifics) while the battery is drained, so what I'm doing for the mean time is to leave the phone open and let it drain which might take ~2 days.
Does anyone know how to flash a ROM on a bricked device? Thanks for any leads.
I have a pixel 6a that I successfully rooted but when I tried to unroot it something went wrong. When I restarted the phone I got a message saying
Your device is corrupt. It can’t be trusted and may not work properly.” then it was stuck on the Google logo. I managed to get it unstuck but then when it restarted I got the error message again and it shut off. Now the phone will not turn on at all. I tried charging it for hours. I tried forcing it to turn on with every ossible button configuration I could think of. It is completely unresponsive. Please help. I literally just reviewed it from Google Fi a week ago
Cheesymatt661 said:
I have a pixel 6a that I successfully rooted but when I tried to unroot it something went wrong. When I restarted the phone I got a message saying
Your device is corrupt. It can’t be trusted and may not work properly.” then it was stuck on the Google logo. I managed to get it unstuck but then when it restarted I got the error message again and it shut off. Now the phone will not turn on at all. I tried charging it for hours. I tried forcing it to turn on with every ossible button configuration I could think of. It is completely unresponsive. Please help. I literally just reviewed it from Google Fi a week ago
Click to expand...
Click to collapse
Are you on A13?
Did you have, at the minimum, the A13 bootloader on both slots?
What method did you use to uninstall Magisk?
What happens when you connect phone to computer?
Will Android Flash Tool recognize it? If so, use that to flash back to stock.
Try holding the power button down for at least 30 seconds?
If you were on A13 and didn't have the A13 bootloader on both slots, when bootlooping your phone may have reverted to the A12 slot. If so, your device may be a brick due to the new ARB and you should probably RMA it.
Yes it was A13. And nothing happens when I connect it to my laptop. And I'm not sure what you mean by "both slots". My apologies... This is my very first time rooting and trying to unroot a device
I am also using Linux. So I don't really know what other tools I could or should try other than sdk platform tools.
Cheesymatt661 said:
Yes it was A13. And nothing happens when I connect it to my laptop. And I'm not sure what you mean by "both slots". My apologies... This is my very first time rooting and trying to unroot a device
Click to expand...
Click to collapse
Did you do this after updating to A13?
It's a hard brick as per the link in the above post.
But why root, then unroot?
What steps did you take?
It would be helpful to others to find out where you went wrong.
Cheesymatt661 said:
I have a pixel 6a that I successfully rooted but when I tried to unroot it something went wrong. When I restarted the phone I got a message saying
Your device is corrupt. It can’t be trusted and may not work properly.” then it was stuck on the Google logo. I managed to get it unstuck but then when it restarted I got the error message again and it shut off. Now the phone will not turn on at all. I tried charging it for hours. I tried forcing it to turn on with every ossible button configuration I could think of. It is completely unresponsive. Please help. I literally just reviewed it from Google Fi a week ago
Click to expand...
Click to collapse
Why not post this in Pixel 6a forum?
@Cheesymatt661 Okay so you have unlocked bootaloder + fastboot is working right? One of my friend also faced this and what he did was flashed latest (A13) factory images to both A & B slots separately and that's it. It was simple as that for him.