Okay, so it's been a while and the saga is finally over. I'll try to summarize the whole story but if anyone is reading this with the same issue, the TLDR is that I had it replaced/serviced under warranty by Comspot Repair Germany. I'll leave the OP for archival purposes.
After seemingly exhausting all my options, in the end i decided to reach out to one of Google's authorized service partners. I wrote to Comspot Repair Germany and to my surprise they said they would take a look at it. I sent it back in November 2022, they had it for about a month and some, because of apparent part shortages on Google's side. I just received it today (January 2023), however the delay seems to have been mostly caused by the delivery company getting my address wrong. Apparently they replaced the whole board, the screen and battery too, as well as the sim tray which i find kind of funny. It works as it should now and the repair itself cost me nothing, I just paid for shipping to Germany.
Overall experience dealing with Comspot is a strong 4/5. They were able to fix my issue, unlike Google which I really shouldn't have to say, but I'd take one point off for communication management. And for anyone else that has a pixel 6 or later, and lives within an EU country, I'd suggest looking Comspot up and giving them a shot.
---- original post bellow ----
Hi,
I have a pixel 6 and it's stuck in fastboot mode. Does not boot, or go into any other mode than fastboot. Adb doesn't recognize it, only fastboot does but I can't flash it since it appears that the bootloader is locked. Bootloader menu lists the following:
Product version: oriole MP1.0
Bootloader version: slider-1.2-8318357
---
Secure boot: PRODUCTION
NOS production: error!
---
Device state: error!
Boot slot: b
Enter reason: boot failure
URAT: disabled
So far, I've tried the pixel recovery tool and flashing OTA/full images but to no avail.
Any chance it may be fixable or it's bricked forever?
Does anyone know what causes this state?
Only thing I know (not much) is 'fastboot reboot' but urs keeps powering up in fastboot mode?
Zaxx32 said:
Only thing I know (not much) is 'fastboot reboot' but urs keeps powering up in fastboot mode?
Click to expand...
Click to collapse
Yep. Already tried with the key combo and with command too.
Maybe you can try to change the boot slot to a, maybe this could work out.
Cheers
tom1807 said:
Maybe you can try to change the boot slot to a, maybe this could work out.
Cheers
Click to expand...
Click to collapse
Well I tried but I get an error failed to get unlock ability -1 or something like that.
Unfortunately, if your bootloader is locked, there isn't much you can do.
If you were able to get into recovery mode, you could sideload the OTA. But, flashing partitions directly from bootloader requires an unlocked bootloader.
You can try to unlock the bootloader using fastboot flashing unlock but this will likely fail because get_unlock_ability=0; the only way to change this value is by turning on OEM Unlocking in Developer Options.
V0latyle said:
Unfortunately, if your bootloader is locked, there isn't much you can do.
If you were able to get into recovery mode, you could sideload the OTA. But, flashing partitions directly from bootloader requires an unlocked bootloader.
You can try to unlock the bootloader using fastboot flashing unlock but this will likely fail because get_unlock_ability=0; the only way to change this value is by turning on OEM Unlocking in Developer Options.
Click to expand...
Click to collapse
That sucks, especially the last part.
So essentially it's a brick.
Thank you for the reply tho. Do you at least have any idea why this error happens?
CoolKitty said:
That sucks, especially the last part.
So essentially it's a brick.
Thank you for the reply tho. Do you at least have any idea why this error happens?
Click to expand...
Click to collapse
It's hard to say.
Try unlocking your bootloader just in case.
@CoolKitty
What were you doing prior the the phone getting into this state?
CoolKitty said:
Hi,
I have a pixel 6 and it's stuck in fastboot mode. Does not boot, or go into any other mode than fastboot. Adb doesn't recognize it, only fastboot does but I can't flash it since it appears that the bootloader is locked. Bootloader menu lists the following:
Product version: oriole MP1.0
Bootloader version: slider-1.2-8318357
---
Secure boot: PRODUCTION
NOS production: error!
---
Device state: error!
Boot slot: b
Enter reason: boot failure
URAT: disabled
So far, I've tried the pixel recovery tool and flashing OTA/full images but to no avail.
Any chance it may be fixable or it's bricked forever?
Does anyone know what causes this state?
Click to expand...
Click to collapse
Did your battery happen to die before this happened?
V0latyle said:
It's hard to say.
Try unlocking your bootloader just in case.
Click to expand...
Click to collapse
If you mean through fastboot command, I did and it doesn't work, as expected...
shoey63 said:
What were you doing prior the the phone getting into this state?
Click to expand...
Click to collapse
Just setting up and then it ran out of battery and rebooted to this, when I plugged it in.
Lughnasadh said:
Did your battery happen to die before this happened?
Click to expand...
Click to collapse
Pretty much yeah.
CoolKitty said:
Pretty much yeah.
Click to expand...
Click to collapse
Yeah, seen this happen before. Almost everyone had to RMA it. May try letting it run out of battery again and then plugging it in to a charger and then hold the power button down for a while. I think I've seen one person who had that work successfully, but most likely will have to RMA it.
Google Pixel - Update and Software Repair
this may or may not help
justauserthatusesaphone said:
Google Pixel - Update and Software Repair
this may or may not help
Click to expand...
Click to collapse
This only helps when the user is able to enter Rescue Mode from bootloader. If the bootloader doesn't start, Rescue Mode is of no help.
Lughnasadh said:
Yeah, seen this happen before. Almost everyone had to RMA it. May try letting it run out of battery again and then plugging it in to a charger and then hold the power button down for a while. I think I've seen one person who had that work successfully, but most likely will have to RMA it.
Click to expand...
Click to collapse
That would suck a lot, because I'm in a country that's not on Google's good list, had to import the phone here. I'm pretty sure they'll not handle it gracefully but I guess we'll see.
justauserthatusesaphone said:
Google Pixel - Update and Software Repair
this may or may not help
Click to expand...
Click to collapse
Yes, thanks for the suggestion but unfortunately it doesn't work because it doesn't want to go into rescue mode. :\
CoolKitty said:
That would suck a lot, because I'm in a country that's not on Google's good list, had to import the phone here. I'm pretty sure they'll not handle it gracefully but I guess we'll see.
Click to expand...
Click to collapse
Well, that went about as good as expected.
After a lot of troubleshooting with the support agent, they suggested I could RMA it, I told them I'm not in a country where they have repair services and they politely told me to fu*k off basically.
So I'm stuck with a bricked phone that i can't have serviced unless 'i have a friend who can send it for me, from a supported county'
CoolKitty said:
Well, that went about as good as expected.
After a lot of troubleshooting with the support agent, they suggested I could RMA it, I told them I'm not in a country where they have repair services and they politely told me to fu*k off basically.
So I'm stuck with a bricked phone that i can't have serviced unless 'i have a friend who can send it for me, from a supported county'
Click to expand...
Click to collapse
Sorry to hear that. Hope you're able to find support. You could still try taking it to a repair facility, I don't see why they wouldn't be able to get a new main board but I've been wrong before too, so...
V0latyle said:
Sorry to hear that. Hope you're able to find support. You could still try taking it to a repair facility, I don't see why they wouldn't be able to get a new main board but I've been wrong before too, so...
Click to expand...
Click to collapse
Problem is, since Google doesn't officially sell pixel phones where I live, they also don't have any service centers and they don't sell parts either. Which sucks, I don't see why this artificial limitation has to exist, since Google has a mail in repair program and service centers across several EU countries.
Their excuse is that they can't ship it back to you because their shipping partners don't work anywhere outside the countries where they sell pixels.
CoolKitty said:
Hi,
I have a pixel 6 and it's stuck in fastboot mode. Does not boot, or go into any other mode than fastboot. Adb doesn't recognize it, only fastboot does but I can't flash it since it appears that the bootloader is locked. Bootloader menu lists the following:
Product version: oriole MP1.0
Bootloader version: slider-1.2-8318357
---
Secure boot: PRODUCTION
NOS production: error!
---
Device state: error!
Boot slot: b
Enter reason: boot failure
URAT: disabled
So far, I've tried the pixel recovery tool and flashing OTA/full images but to no avail.
Any chance it may be fixable or it's bricked forever?
Does anyone know what causes this state?
Click to expand...
Click to collapse
Yes when flashing partitions there is a needed boot in-between some operations that doing what you did skipped one.
I fixed this same problem and many other crazy yellow warnings and etc by toying with the change boot slot etc. i do not recall what worked but some of this might help:
Code:
fastboot --set-active=a
or this depending on what is set:
Code:
fastboot --set-active=b
So if it's A then set to B and vice versa. then let it do a reboot.
you could also try the hard reset keys to interrupt the boot. (the system check for previous successful boot status)
Give it a shot i will do my best to check and get back to you once you have tested that.
Related
on boot "Signature mismatched Unrecoverable Bootloader error"
only 12 hours after receiving my tf201.
I've installed the stock ICS and it was ok for few hours.
hard reset is not helping (VOL DOWN+POWER),
I'm stuck in the boot screen. What should I do ?
RMA is probably your best bet. the hidden, signed partition seems to be corrupted - which means no fix without nvflash, and that requires the encryption key.
tshoulihane said:
RMA is probably your best bet. the hidden, signed partition seems to be corrupted - which means no fix without nvflash, and that requires the encryption key.
Click to expand...
Click to collapse
Thanks
does the encryption key is NVIDIA or mine ?
I didn't encrypted anything.
RMA will be problematic, cause I live outside USA.
is there anything I can do by myself ?
galr10 said:
Thanks
does the encryption key is NVIDIA or mine ?
I didn't encrypted anything.
RMA will be problematic, cause I live outside USA.
is there anything I can do by myself ?
Click to expand...
Click to collapse
Best thing is to not even have to deal with it. You deserve a new working device. Since you only had it 12hrs. Or so, just exchange it immediately. Whatever store you got it from warranty still good on it. Tell them n less than 12 hrs this happened and now you either want an exchange or a refund.
demandarin said:
Best thing is to not even have to deal with it. You deserve a new working device. Since you only had it 12hrs. Or so, just exchange it immediately. Whatever store you got it from warranty still good on it. Tell them n less than 12 hrs this happened and now you either want an exchange or a refund.
Click to expand...
Click to collapse
is this a common error ?
I'm afraid from buying a new one
galr10 said:
is this a common error ?
I'm afraid from buying a new one
Click to expand...
Click to collapse
No, actually your case of bootloader error is the first I've ever heard of this. To be honest, there are other possible issues some have had in other areas, but alot also have fully capable working devices also. I wouldn't be too worried about getting a new device. I'd be more worried having to send my brand new one in for a repair when I haven't even had it 24hrs. Yet.
this means that the "blob" flash has faild at flashing bootloader
this is unrecoverable without nvflash
Apache14 said:
this means that the "blob" flash has faild at flashing bootloader
this is unrecoverable without nvflash
Click to expand...
Click to collapse
Exactly. Which is why its inexcusable and needs to be returned to store for an exchange. He just got the device n less than 12hrs and needs to send it in for repair. No way. He deserves a new device St least able to boot up out the box..lol. plus Asus would make him pay to send it in. Hell nawww...lol
indeed get a replacement ASAP
on a side note this is a very good argument for nvflash .... if we had that this would be fixable
ohh one thing you could try is
1) power off the device
2) hold volume-dwn + power untill the screen shows text
3) press volume up
4) look for on screen errors (if you see an android the recovery image may be bootable)
Apache14 said:
ohh one thing you could try is
1) power off the device
2) hold volume-dwn + power untill the screen shows text
3) press volume up
4) look for on screen errors (if you see an android the recovery image may be bootable)
Click to expand...
Click to collapse
the same fu**ing error
Hi everyone. I got a problem with my HTC M8.
First of all, I didn't make with it any changes (as unlock bootloader, root or installing any custom OS or recovery etc.) Week ago I left device, connected to PC for all night, and, I gess, with "bad" micro-USB cable.
Next day I couldn't boot this phone. I connected it to charger and after little time it was loaded to fastboot. But up today I can't do anything with phone: I can't unlock it, can't factory reset, can't boot to recovery etc...
I tried to find any same simptomes in google, but found nothing
As you can see on screenshots, I made steps for unlock bootloader but on device I didn't see notification about unlocking.
Is this an AT&T version M8? If so, try an RUU.
Other than that, if the phone stopped working spontaneously without being modded, I wouldn't then try to mod it by unlocking the bootloader. I don't see how the cable or leaving it plugged to computer can cause this. If the phone is defective and stock condition, your best bet may be to get warranty service (or exchange for new, if the phone is still very recently purchased).
I though that I lost recovery in some way and should simply unlock bootloader, install custom recovery and got success ))
I don't see how the cable or leaving it plugged to computer can cause this. If the phone is defective and stock condition, your best bet may be to get warranty service (or exchange for new, if the phone is still very recently purchased).
Click to expand...
Click to collapse
Yes, but next day I connected another phone, Nexus 5, and it was fully discharged (connected to enabled PC with this cable). And I though that the reason the same... With one exeption - Nexus 5 just was charged and ok, HTC M8 - lost data or corrupted it in some way...
Warranty it's the last chance. Phone arrived from Canada) I'm from Ukraine. In all cases it will cost money. At first I want to find the solution by myself (and with help of xda community and internet)
MaggiMag363 said:
I though that I lost recovery in some way and should simply unlock bootloader, install custom recovery and got success ))
Click to expand...
Click to collapse
Are you aware that stock recovery appears as a red triangle with exclamation? It doesn't look the same as custom recovery (TWRP, CWM). When you see the red triangle, press vol (down or up, can't remember) to see the recovery menu selections.
I asked if you have the AT&T version or not (this section is AT&T specific) and you never answered that.
redpoint73 said:
Are you aware that stock recovery appears as a red triangle with exclamation? It doesn't look the same as custom recovery (TWRP, CWM). When you see the red triangle, press vol (down or up, can't remember) to see the recovery menu selections.
I asked if you have the AT&T version or not (this section is AT&T specific) and you never answered that.
Click to expand...
Click to collapse
It should be international.
About recovery - I tried to open it from fastboot. Ineffectually. And I tried to boot it with vol. and power buttons. I don't see any icons with exclamations - fastboot loads after black screen, no matter, buttons were pressed or not.
MaggiMag363 said:
It should be international.
About recovery - I tried to open it from fastboot. Ineffectually. And I tried to boot it with vol. and power buttons. I don't see any icons with exclamations - fastboot loads after black screen, no matter, buttons were pressed or not.
Click to expand...
Click to collapse
This forum section is specific to the US AT&T version. You would most likely get better help on the international forum (more users there).
Do you get the phone ID in response if you type the command: fastboot devices
redpoint73 said:
This forum section is specific to the US AT&T version. You would most likely get better help on the international forum (more users there).
Do you get the phone ID in response if you type the command: fastboot devices
Click to expand...
Click to collapse
Yes I have. And I can open menu "Barcode" from fastboot and see IMEI, SN and MB.
I think that is your serial number, so you should delete it (personal info).
I didn't actually want to know the output, I just wanted to make sure fastboot connectivity was working.
You might try to find the stock recovery for your CID and re-install it to see if that helps: http://forum.xda-developers.com/showthread.php?t=2701376
redpoint73 said:
I think that is your serial number, so you should delete it (personal info).
I didn't actually want to know the output, I just wanted to make sure fastboot connectivity was working.
You might try to find the stock recovery for your CID and re-install it to see if that helps: http://forum.xda-developers.com/showthread.php?t=2701376
Click to expand...
Click to collapse
oo, thanks) I thought that you can recognise mobile provider via SN
I looked at general topic http://forum.xda-developers.com/htc-one-m8/help and found somekind of the same simptomes, but all of them were after rooting, installing custom ROM etc. I did nothing One more thing came to me now - phone could start upgrading and then discharged battery.
You might try to find the stock recovery for your CID and re-install it to see if that helps: http://forum.xda-developers.com/show....php?t=2701376
Click to expand...
Click to collapse
thanks. Tomorrow I will try this topic
MaggiMag363 said:
oo, thanks) I thought that you can recognise mobile provider via SN
I looked at general topic http://forum.xda-developers.com/htc-one-m8/help and found somekind of the same simptomes, but all of them were after rooting, installing custom ROM etc. I did nothing One more thing came to me now - phone could start upgrading and then discharged battery.
Click to expand...
Click to collapse
My advice is to post to the international forum. Your situation is pretty unique, so I'd say it justifies a new thread. And there are a lot of folks on that forum section that are smarter than me, and may have some better ideas.
http://forum.xda-developers.com/htc-one-m8/help/htc-m8-phone-boots-fastboot-factory-t2953795
I created topic in main theme. Thanks.
I'm interested in running a custom Rom on my mpcs LG f6 (ms500). I'm a part timer at this, my understanding of code is devastatingly deficient.
I have a an l9 and another f6 that won't even turn on and I'm wondering where, even, to begin.
All are mpcs.
All three, including the one I'm writing this on presently, were/are rooted.
An update took out the non-working f6, and the l9 was my bad.
I'm now on a rooted f6 running battery booster pro, overclocked with freedom kernal, with roehsoft ram expander doubling my ram to 1608.
I realize my circumstances are all over the place, but, if anyone has the genuine benevolence to help me where they can; my gratitude will be unquantifiable.
findrome said:
I'm interested in running a custom Rom on my mpcs LG f6 (ms500). I'm a part timer at this, my understanding of code is devastatingly deficient.
I have a an l9 and another f6 that won't even turn on and I'm wondering where, even, to begin.
All are mpcs.
All three, including the one I'm writing this on presently, were/are rooted.
An update took out the non-working f6, and the l9 was my bad.
I'm now on a rooted f6 running battery booster pro, overclocked with freedom kernal, with roehsoft ram expander doubling my ram to 1608.
I realize my circumstances are all over the place, but, if anyone has the genuine benevolence to help me where they can; my gratitude will be unquantifiable.
Click to expand...
Click to collapse
I'll give a shot at trying to help you with the L9 but I'm going to need some details about what happened. :/
Thank you AshIndigo
L9 rooted and running system tuner pro. I turned on the oem battery function, kernal, doo-hicky (highly technical terminology). The unit ceased recognizing the battery after reboot. It stated, at boot, to insert oem battery and will not take a charge.
I'm considering a wipe and a new bootlaoder with a custom Rom if possible, but I'll settle with just getting it working.
findrome said:
Thank you AshIndigo
L9 rooted and running system tuner pro. I turned on the oem battery function, kernal, doo-hicky (highly technical terminology). The unit ceased recognizing the battery after reboot. It stated, at boot, to insert oem battery and will not take a charge.
I'm considering a wipe and a new bootlaoder with a custom Rom if possible, but I'll settle with just getting it working.
Click to expand...
Click to collapse
Thats a new one. But what modes can you get into. S/W, fastboot, recovery, the wipe combination? If you can get into s/w mode just use the lg mobile tool and that should fix it. Otherwise we may need to reflash the phone. and is your bootloader unlocked?
It doesn't power up in the slightest. And it won't charge.
Bootloader was not unlocked, I'm still trying to wrap my skull jelly around that. I'm thinking flash might be the best option, but I'd prefer to preserve the data (not likely if flashed). I've downloaded LG flash tool, but the manual data entry is a mystery, excluding imei and serial.
findrome said:
Bootloader was not unlocked, I'm still trying to wrap my skull jelly around that. I'm thinking flash might be the best option, but I'd prefer to preserve the data (not likely if flashed). I've downloaded LG flash tool, but the manual data entry is a mystery, excluding imei and serial.
Click to expand...
Click to collapse
Alright I'm presuming s/w mode doesnt work but if it does then that would be nice. Next thing is to try fastboot. Here is a link to a fastboot for the l9
http://forum.xda-developers.com/showthread.php?t=2292828
If you manage to get into fastboot. We can reflash things. Truth to be told I dont know if we reflash we might have to wipe the device. :/
I've resolved myself to things being what they are.
What's s/w mode?
AshIndigo said:
Alright I'm presuming s/w mode doesnt work but if it does then that would be nice. Next thing is to try fastboot. Here is a link to a fastboot for the l9
http://forum.xda-developers.com/showthread.php?t=2292828
If you manage to get into fastboot. We can reflash things. Truth to be told I dont know if we reflash we might have to wipe the device. :/
Click to expand...
Click to collapse
Downloaded, followed instructions. Device booted once and quit while playing around with it, consistent with initial failure as I recall (if only vaguely), now on s/w update screen. Says please wait while upgrading.
Update:
Can enter s/w update. Now takes charge, will likely be 100% by the time you read this.
Lastly, can power on but powers off after entering screen unlock code.
Thank you again AshIndigo.
After some more dabbling, I've made it past the lock screen. The result is a message " please use genuine LG battery" before the unit shuts down and goes into what might might questionably be a bootloop. It's the system tuner pro app, set to start on start-up, that's the thorn in my side.
What are your orders captain?
findrome said:
After some more dabbling, I've made it past the lock screen. The result is a message " please use genuine LG battery" before the unit shuts down and goes into what might might questionably be a bootloop. It's the system tuner pro app, set to start on start-up, that's the thorn in my side.
What are your orders captain?
Click to expand...
Click to collapse
Sorry for replying late but if you have adb enabled we can uninstall the app easily. This should be the command to remove it.
adb uninstall ccc71.pmw.pro
AshIndigo said:
Sorry for replying late but if you have adb enabled we can uninstall the app easily. This should be the command to remove it.
adb uninstall ccc71.pmw.pro
Click to expand...
Click to collapse
No apologies needed, your time is greatly appreciated.
I ran the command, with what appears to be success. It seems though, the kernal remains intact.
A wipe seems imminent.
findrome said:
No apologies needed, your time is greatly appreciated.
I ran the command, with what appears to be success. It seems though, the kernal remains intact.
A wipe seems imminent.
Click to expand...
Click to collapse
(I just deleted everything I wrote and have to write it again )
Ok so before we try to re-flash the kernel. Lets just try the lg mobile support tool. If that doesn't work then heres instructions
1. If you have the p760 then heres the stock kernel
http://www.mediafire.com/download/87i322233ev36k8/stock-kernel.zip
3. Download it
4. extract the boot.img from the zips and put it into the "yours" folder in the fastboot folder
5. Get into fastboot
6. Make sure the device is connected by typing "fastboot devices"
(It should look like this) http://cdn.teamandroid.com/wp-content/uploads/2012/07/fastboot-devices-600x302.jpg
6a. Pray to Google
7. type "fastboot flash boot boot.img"
8. Pray again.
If you don't have the p760 then tell me which device you have so I can get the kernel
@ AshIndigo
P769BK
AshIndigo said:
(I just deleted everything I wrote and have to write it again )
6a. Pray to Google
8. Pray again.
If you don't have the p760 then tell me which device you have so I can get the kernel
Click to expand...
Click to collapse
Golden, you missed your calling.
It's a P769(bk). Not that the color makes a difference. It's also a T-mo, not mpcs. If that matters.
findrome said:
Golden, you missed your calling.
It's a P769(bk). Not that the color makes a difference. It's also a T-mo, not mpcs. If that matters.
Click to expand...
Click to collapse
I dont think I've missed it yet
Alright so there are 2 options right now.
1. You resign the kernel or wait for me to get on a windows computer so I can resign it.
2. You unlock your bootloader.
If you choose option 1 then and you want to try then here's the link.
http://forum.xda-developers.com/optimus-l9/general/guide-install-custom-roms-locked-t3249828
And here's the link to the kernel
http://d-h.st/pdM
1. Follow the manual instructions in the post except just do it for the boot.img and flash that instead.
"fastboot flash boot boot_bumped.img"
If you choose option 2 then here's a link with instructions. (My phone is perma-locked so I never got to try this)
http://forum.xda-developers.com/showthread.php?t=2601480 (Wish you luck if you try this)
If anything is unclear let me know.
I hope I am in the right area for this post. I apologize if I'm not.
My Motorola One 5G Ace (XT2113-2) is stuck in a bootloop. I was trying to root it and apparently did something wrong. First, I couldn't get it into recovery mode after trying to install TWRP. Out of a lack of options, I did a factory reset through the Settings menu. It reset but then got stuck in a bootloop. I get a message stating the bootloader is unlocked and then the Motorola logo appears, then it starts over.
I can get it to fastboot but that's it. I was hoping to use Moto Auto Flash or RSD Lite to flash the original firmware on the phone in an effort to get things correct. The last phone I rooted was my Note4 years ago. This isn't going as easy as the Note did.
Any suggestions will be most appreciated. Thanks in advance for reading.
fosgate3 said:
I hope I am in the right area for this post. I apologize if I'm not.
Click to expand...
Click to collapse
Well your Motorola One 5G Ace is not a Motorola One, so you are not in the correct category. But no need to apologize.
fosgate3 said:
My Motorola One 5G Ace (XT2113-2) is stuck in a bootloop. I was trying to root it and apparently did something wrong. First, I couldn't get it into recovery mode after trying to install TWRP. Out of a lack of options, I did a factory reset through the Settings menu. It reset but then got stuck in a bootloop. I get a message stating the bootloader is unlocked and then the Motorola logo appears, then it starts over.
Click to expand...
Click to collapse
I am only a newbie in all this, but my clue is that your phone is doing the boot loop probably because the wrong boot slot is selected.
Have you tried with asb.exe or fastboot.exe to select the other boot slot, A instead of B or B instead of A? Let us know if this helps.
fosgate3 said:
I can get it to fastboot but that's it. I was hoping to use Moto Auto Flash or RSD Lite to flash the original firmware on the phone in an effort to get things correct. The last phone I rooted was my Note4 years ago. This isn't going as easy as the Note did.
Click to expand...
Click to collapse
If manually selecting the other boot slot does not help, you could use the Lenovo Rescure and Smart Assistant. It can read device information from several phone states, download the stock firmware and reinstall everything.
fosgate3 said:
Any suggestions will be most appreciated. Thanks in advance for reading.
Click to expand...
Click to collapse
My pleasure.
seven.seas said:
Well your Motorola One 5G Ace is not a Motorola One, so you are not in the correct category. But no need to apologize.
I am only a newbie in all this, but my clue is that your phone is doing the boot loop probably because the wrong boot slot is selected.
Have you tried with asb.exe or fastboot.exe to select the other boot slot, A instead of B or B instead of A? Let us know if this helps.
If manually selecting the other boot slot does not help, you could use the Lenovo Rescure and Smart Assistant. It can read device information from several phone states, download the stock firmware and reinstall everything.
My pleasure.
Click to expand...
Click to collapse
This is already beyond my knowledge. I don't recall seeing anything about different boot slots so I'm not sure how to reply to that. I will try Smart Assistant and see what that does. Thanks for the suggestion.
fosgate3 said:
This is already beyond my knowledge. I don't recall seeing anything about different boot slots so I'm not sure how to reply to that. I will try Smart Assistant and see what that does. Thanks for the suggestion.
Click to expand...
Click to collapse
Right out of the gate, I don't know if I can use Smart Assistant. The first set of instructions states to put the phone into USB debugging. I can't get the phone to boot so that I can do that part. I can try without doing that and see what happens I guess.
fosgate3 said:
Right out of the gate, I don't know if I can use Smart Assistant. The first set of instructions states to put the phone into USB debugging. I can't get the phone to boot so that I can do that part. I can try without doing that and see what happens I guess.
Click to expand...
Click to collapse
What happens when you turn the device off completely, then press the 'power' button and the 'volume down' button at the same time for 3-10 seconds. It should not do any bootup but only show the fastboot menu. From there your phone can get recognized via USB by fastboot (from a command prompt on your computer) and as well as by the Lenovo Rescue and Smart Assistant.
Thank you for all the help. I am now rooted.
So I may have bricked my phone and need some serious help right now...
I was ready to flash October's monthly update. I had downloaded the factory image, and extracted everything from the factory image. I patched the magisk image and had it ready in the same directory. I edited the flash_all.bat script and removed the "-w" flag. I disabled all modules on magisk, and had got the phone to bootloader mode. I then ran the flash_all.bat script, and then for some reason the bootloader flashing failed. My phone now won't turn on and is a complete black screen. I need some major help here.
EDIT: My PC cannot see it on EITHER ADB or Fastboot devices
Can you boot manually into bootloader mode?
Cheers
tom1807 said:
Can you boot manually into bootloader mode?
Cheers
Click to expand...
Click to collapse
No I can't. Holding power and volume down gets me nothing.
Toronadian said:
No I can't. Holding power and volume down gets me nothing.
Click to expand...
Click to collapse
How long are you holding it? I have found that it takes a *really long time* (like, a full minute) of holding that power button to get any response. But if still nothing, "black screen with no response" does sound like the "bad bootloader" brick. :x Might be fixable under warranty, I'm not sure.
.......I'm getting a feeling that I did the wrong device's bootloader and it failed. Now it's stuck....
Toronadian said:
So I may have bricked my phone and need some serious help right now...
I was ready to flash October's monthly update. I had downloaded the factory image, and extracted everything from the factory image. I patched the magisk image and had it ready in the same directory. I edited the flash_all.bat script and removed the "-w" flag. I disabled all modules on magisk, and had got the phone to bootloader mode. I then ran the flash_all.bat script, and then for some reason the bootloader flashing failed. My phone now won't turn on and is a complete black screen. I need some major help here.
EDIT: My PC cannot see it on EITHER ADB or Fastboot devices
Click to expand...
Click to collapse
Did you have the A13 bootloader flashed to both slots before trying to update today?
Maybe try the phone support? Flash a rom to Sd card even?
Lughnasadh said:
Did you have the A13 bootloader flashed to both slots before trying to update today?
Click to expand...
Click to collapse
Yes I did. OK...so I screwed up HARD and I think I might have did the Pixel 5's bootloader, or at least it tried. It just said failed and that was it. Now I'm just getting a black screen.
Both slots have the September 2022 A13 bootloader. I was on September 2022 update. Is there anyway to get to the other slot and at least get bootloader from there??
Toronadian said:
Yes I did. OK...so I screwed up HARD and I think I might have did the Pixel 5's bootloader, or at least it tried. It just said failed and that was it. Now I'm just getting a black screen.
Click to expand...
Click to collapse
Have you tried to see if Android Flash Tool will recognize your phone?
Lughnasadh said:
Have you tried to see if Android Flash Tool will recognize your phone?
Click to expand...
Click to collapse
Yep, doesn't recognize it.
Toronadian said:
Yep, doesn't recognize it.
Click to expand...
Click to collapse
May want to try to RMA it. Can't think of anything else. Sounds like it's pretty dead if it's not turning on and not recognizing anything.
What hurts hard is that I've taken exceptional care of this, like battery was still at 100%. Ugghh. Traded in my 4a 5G for this at launch.
Unfortunately , if you flash bootloader from another model.. you're f***d...
RMA only option
cultofluna said:
Unfortunately , if you flash bootloader from another model.. you're f***d...
RMA only option
Click to expand...
Click to collapse
Except ur not...
Toronadian said:
What hurts hard is that I've taken exceptional care of this, like battery was still at 100%. Ugghh. Traded in my 4a 5G for this at launch.
Click to expand...
Click to collapse
Well if you're willing I'm trying to start a small team for testing existing methods to unbricking.
I've come to the conclusion that all you need to talk to the phone is a USB c to 2.0 cable then hold vol up/dwn. This exposes the bootROM output and messages from the phone in serial output on COMM5, and if you're on Unix then it's on ttyACM0. Interestingly enough it's in Exynos downloading mode. The computer gives us the USB descriptor and a bulk in and bulk out endpoint.
I believe Exynos uses Syn/Ack/Dwn/Up
So an update, I took it today to a UBreakIFix location since here in Canada they're an authorized repair place. I fortunately still had 2 weeks warranty on it (of a year) so the repair is supposedly covered (they emailed Google and got authorization on it). After doing the diagnosis, they said the issue is with the motherboard or something (I'm assuming it flashed the wrong thing and bricked) so they had to replace it. They have the part in stock so I'm getting the phone back tomorrow. Hoping this gets everything back in place and repair holds up. Nothing was wrong with it otherwise, just hope their repair handiwork is good and all the pieces are placed correctly. I did lose all my data and messages though as I had been choosing not to save a number of things to my Google account (I had it on pause) so it will take quite a bit of time to just get it back to the way I like it. Also hoping that they don't then also prevent the bootloader from being unlocked, which I've read has happened after Google RMA's your device.
Thank you everyone. And @NonStickAtom785 , hope for all the best in your testing into unbricking methods and look forward to having you share your findings, in case for whatever reason others or hopefully NOT me runs into that situation.