So my phone is stuck on this issue. I haven't done anything wrong. My phone was just peacefully charging then the phone switches off by itself then the bootloop happened.
This showed on the screen:
dm-verity corruption
your device is corrupt.
it can't be trusted and my not work properly.
press enter button to continue.
Or, device will power off in 5s.
(written in white)
Although it does turn off by itself if I ignore it, after I turn it on again and press enter or power button it boot until lockscreen and if I try to do something like unlocking, scrolling down notifs bar, and sliding through different page on home screen it will turn off again. It seem like it's crashing. The thing is I am not trying to root or flash something. I haven't done anything on my phone. I only have one phone and I badly need your help. I hope wiping or reformatting the phone is my last resort. My phone is updated to Android 11 and lateset MIUI (provided by the system itself and not downloaded somewhere). Thank you.
Well seems like something is corrupt.
It reboots when you touches the screen(or do anything)?
LR7875 said:
It reboots when you touches the screen(or do anything)?
Click to expand...
Click to collapse
It's more like it turns itself off again and if I try to press again power button if the problem show again, same thing happen. Sometimes MIUI logo appears and shuts down again it can't even go to lock screen.
Is there any chance you can unlock it?
It seems like your internal storage is corrupted.
LR7875 said:
Is there any chance you can unlock it?
It seems like your internal storage is corrupted.
Click to expand...
Click to collapse
At some point I did manage to unlock it but it happened only once and when I tried to open the notifs by scrolling down or tried to different part of homescreen it just shuts down. After that, it can't even go to the lockscreen after reboot. It's a never ending cycle. I can go to fastboot mode but I don't know if I can do miracle with that.
Well immediately plug into a computer and pull photos amd videos from it if you get it unlocked.
LR7875 said:
Well immediately plug into a computer and pull photos amd videos from it if you get it unlocked.
Click to expand...
Click to collapse
I reformatted it hoping that it will fix the problem. I was wrong. *sigh*
hyung_z said:
I reformatted it hoping that it will fix the problem. I was wrong. *sigh*
Click to expand...
Click to collapse
Well most likely your EMMC internal storage chip went bad R.I.P. (well maybe you sending those emojis will be more appropriate, but, oh well)
Maybe search more on google, I can't help you more
LR7875 said:
Well most likely your EMMC internal storage chip went bad R.I.P. (well maybe you sending those emojis will be more appropriate, but, oh well)
Maybe search more on google, I can't help you more
Click to expand...
Click to collapse
Do you think service center can help me with this or they'll probably just say to replace the phone if a bad chip is the case?
Maybe they will replace the motherboard with some fee. Or they will try to convince you to buy a new fancy phone just purely because xiaomi could earn more.
Thats all about luck (and problem is on xiaomi side, not your fault)
what's the smartphone model?
Redmi note 8 pro is the OP's phone.
Wait Wait just found some interesting lead.
Xiaomi needs a better way to unbrick its devices instead of Authorized Mi Accounts
Xiaomi has locked down the EDL mode on all of its devices, making it nigh impossible to unbrick a device without an Authorized Mi Account. Read on for more!
www.xda-developers.com
Patched SP flash tool!
heh, i have the same phone. reflash yours with the firmware that was on it before everything that happened. but don't flash userdata if you want your data on it
flashing it is simple process
LR7875 said:
Redmi note 8 pro is the OP's phone.
Wait Wait just found some interesting lead.
Xiaomi needs a better way to unbrick its devices instead of Authorized Mi Accounts
Xiaomi has locked down the EDL mode on all of its devices, making it nigh impossible to unbrick a device without an Authorized Mi Account. Read on for more!
www.xda-developers.com
Patched SP flash tool!
Click to expand...
Click to collapse
there is already a way to flash it with SPFT without authorization
also he must try to flash it in fastboot because it's not bricked
AsyJAIZ said:
there is already a way to flash it with SPFT without authorization
also he must try to flash it in fastboot because it's not bricked
Click to expand...
Click to collapse
He probably doesn't have his bootloader unlocked.
Fastboot OEM unlock wont work as oem unlock is probably not enabled in settings dev options.
LR7875 said:
He probably doesn't have his bootloader unlocked.
Fastboot OEM unlock wont work as oem unlock is probably not enabled in settings dev options.
Click to expand...
Click to collapse
ok i got it, then he should somehow put it in download mode...
Do you guys think I need to go to the service center because I don't know what to do. I really don't want to brick my phone. But a while ago my phone booted. I set it up just like buying a new phone but after I finished setting up, I just wait for the phone to catch up because I was afraid the phone will just shut down suddenly. And then, it happened again the phone shut downs without me doing anything. Now I tried to boot it up again but it is currently stuck at Redmi logo (plus "powered by android" at the bottom").
hyung_z said:
Do you guys think I need to go to the service center because I don't know what to do. I really don't want to brick my phone. But a while ago my phone booted. I set it up just like buying a new phone but after I finished setting up, I just wait for the phone to catch up because I was afraid the phone will just shut down suddenly. And then, it happened again the phone shut downs without me doing anything. Now I tried to boot it up again but it is currently stuck at Redmi logo (plus "powered by android" at the bottom").
Click to expand...
Click to collapse
SPFT enables when phone is a brick, so there's no need in service center.
they will flash it like we are going to do
Help, does anyone know how to fix dm-verity corruption? I was using my tab normally, then it suddenly shuts down and this error keeps popping up whenever my device boots. It goes on a loop unless I press the power button again.
deleted
Related
I seem to be having tons of problems with this new phone =( HTCdev unlock failed work and now the phone has bricked while trying to do an update.
It is stuck on the "HTC powered by android" splash screen. The screen wont turn off and the phone does not change. Is there some way to fix this or am I farked? The phone is literally 3 days old and I hope there is a way to save it.
I can shut it down with Power and vol+ but when it restarts it just locks up. computer does not recognize it though it did install some form of driver.
Dlome said:
I seem to be having tons of problems with this new phone =( HTCdev unlock failed work and now the phone has bricked while trying to do an update.
It is stuck on the "HTC powered by android" splash screen. The screen wont turn off and the phone does not change. Is there some way to fix this or am I farked? The phone is literally 3 days old and I hope there is a way to save it.
I can shut it down with Power and vol+ but when it restarts it just locks up. computer does not recognize it though it did install some form of driver.
Click to expand...
Click to collapse
I would return it
Since I cant do anything until Monday I decided to mess with the phone a little more, I was able to get a custom recovery installed finally so hopefully all I need to do is install a new rom but the problem is the recovery is unable to mount my SD card to perform the install. I can read the sd card when it is in my old phone but not on the HTC One. Currently have Philz Touch installed as the recovery.
Is there any way to fix this or even bypass it all together?
Edit: I have been able to side load CM11 Nightly onto the phone so now it is functioning. I am having an issue with sound though so hopefully I can fix that.
clsA said:
I would return it
Click to expand...
Click to collapse
Warranty returns are for manufacturing defects, not botched mods done by the owner. The phone is completely recoverable.
redpoint73 said:
Warranty returns are for manufacturing defects, not botched mods done by the owner. The phone is completely recoverable.
Click to expand...
Click to collapse
This sounded like a hardware problem to me
I seem to be having tons of problems with this new phone =( HTCdev unlock failed work and now the phone has bricked while trying to do an update.
Click to expand...
Click to collapse
it's hard to mess the phone up when you can't even get the bootloader unlocked
clsA said:
it's hard to mess the phone up when you can't even get the bootloader unlocked
Click to expand...
Click to collapse
User error. The phone wasn't bricked (if the screen comes on, its not bricked) and 99% of the time when folks here say the phone is bricked, its just not booting. As you can see from his subsequent post, he was obviously able to get bootloader unlocked, custom recovery and custom ROM. Of course, you could have not known that when you made your previous post. But failed bootloader unlock, and then the phone won't boot, is a big red flag that the user just did something wrong.
redpoint73 said:
User error. The phone wasn't bricked (if the screen comes on, its not bricked) and 99% of the time when folks here say the phone is bricked, its just not booting. As you can see from his subsequent post, he was obviously able to get bootloader unlocked, custom recovery and custom ROM. Of course, you could have not known that when you made your previous post. But failed bootloader unlock, and then the phone won't boot, is a big red flag that the user just did something wrong.
Click to expand...
Click to collapse
Fair enough ... I read it wrong I guess
clsA said:
Fair enough ... I read it wrong I guess
Click to expand...
Click to collapse
Naw, really looks more like a matter of the OP needs being clear enough, and not giving enough info. If anything, best to get clarification before suggesting warranty service (especially once mods have been started - but again it was hard from the OP's description to know how far it got). Although if it was in fact a hardware defect, of course a warranty claim is valid.
Hello.
Yesterday I was trying to get Ubuntu Touch on this and due to some inconveniences, I decided to go back to android.
I was flashing the stock firmware when I got an error that said it was waiting for the device.
I turned off the phone as I had to leave and returned to it a few hours later.
The phone won't turn on at all, not even vibrating. I plugged into my battery and it is charging at 5v and 0.5A.
I tried getting it into EDL, but no luck.
I think the phone might be dead, or at least the battery, but I don't know how to check or how to save it.
Is there anything I can do?
stickstuck said:
Hello.
Yesterday I was trying to get Ubuntu Touch on this and due to some inconveniences, I decided to go back to android.
I was flashing the stock firmware when I got an error that said it was waiting for the device.
I turned off the phone as I had to leave and returned to it a few hours later.
The phone won't turn on at all, not even vibrating. I plugged into my battery and it is charging at 5v and 0.5A.
I tried getting it into EDL, but no luck.
I think the phone might be dead, or at least the battery, but I don't know how to check or how to save it.
Is there anything I can do?
Click to expand...
Click to collapse
did you reboot to EDL the soft way (comand) or hard way (open the case) ?
loopypalm said:
did you reboot to EDL the soft way (comand) or hard way (open the case) ?
Click to expand...
Click to collapse
I finally managed to get it into EDL. Only the hard way is possible as the phone gives no sign of life(no screen flash, no vibration, nothing).
Upon attempting to flash I get either a firehose error or a Sahara error. I tried both with the original and with a no authentification programmer. This was with QFIL.
I also wanna try QDL on my arch, but I'll get to that tomorrow.
It's still kind of a hassle to get it into EDL as it sometimes works, sometimes doesn't.
Do you think there still is a chance with this, or should I be looking for a motherboard replacement instead?
stickstuck said:
Do you think there still is a chance with this, or should I be looking for a motherboard replacement instead?
Click to expand...
Click to collapse
depend on what you did before
if you mess with the standard partitions (boot/dtbo/system/vendor), that can be solved with EDL
if you mess with hidden partition then look for replacment
try with what you have first ...
loopypalm said:
depend on what you did before
if you mess with the standard partitions (boot/dtbo/system/vendor), that can be solved with EDL
if you mess with hidden partition then look for replacment
try with what you have first ...
Click to expand...
Click to collapse
The mi flash tool keeps failing at "Sending configure cimmand".
What does that mean?
stickstuck said:
The mi flash tool keeps failing at "Sending configure cimmand".
What does that mean?
Click to expand...
Click to collapse
Ask in EDL thread
Hello! I think I've bricked my Pixel 6 Pro using Android 13, I rooted with Magisk successfuly but when I flashed kirisakura kernel using EXKM and rebooted it gave me a bootloop, after bootloop tried flashing patched boot.img from factory in Pixel Flasher but didn't work, also tried using adb and nothing. I think I have flashed the wrong file or something after kirisakura because it would show on Pixel Flasher with a ? at the beginning of the ADB connected devices.
It only would boot to Google logo and then restart, did it a few times but then the screen became black and unresponisive, I've tried vol down power and vol down power and vol down only and vol up power any combination for more than 30 seconds and nothing works, doesn't show on adb devices or wants to boot into any mode.
Did I completely brick my device flashing a wrong boot file after my bootloop? Is there any way to recover my Pixel 6 or should I try to return and ask for a new one and see if they accept it?
Sad thing, my Pixel arrived yesterday and I hard bricked it in the same day.
willing to pay anyone here if someone helps me to boot my pixel again.
Thanks in advance.
PunkOz said:
Hello! I think I've bricked my Pixel 6 Pro using Android 13, I rooted with Magisk successfuly but when I flashed kirisakura kernel using EXKM and rebooted it gave me a bootloop, after bootloop tried flashing patched boot.img from factory in Pixel Flasher but didn't work, also tried using adb and nothing. I think I have flashed the wrong file or something after kirisakura because it would show on Pixel Flasher with a ? at the beginning of the ADB connected devices.
It only would boot to Google logo and then restart, did it a few times but then the screen became black and unresponisive, I've tried vol down power and vol down power and vol down only and vol up power any combination for more than 30 seconds and nothing works, doesn't show on adb devices or wants to boot into any mode.
Did I completely brick my device flashing a wrong boot file after my bootloop? Is there any way to recover my Pixel 6 or should I try to return and ask for a new one and see if they accept it?
Thanks in advance.
Click to expand...
Click to collapse
Reflash the entire android 13 image
DespairFactor said:
Reflash the entire android 13 image
Click to expand...
Click to collapse
How if it doesn't boot into fastboot or anything, PC won't recognize anything since my Pixel's screen is completely black, won't do a single thing, just a sandwich glass, won't even show if it's charging, nothing.
Read this thread if you haven't...
blackhawk said:
Read this thread if you haven't...
Click to expand...
Click to collapse
Everything downloaded to my PC belongs to Android 13, factory image, kernel, everything, didn't rollback, I was in a bootloop where my device went into fastboot mode everytime but then it went to google logo and stopped working at all. Nothing shows on my screen, I've read somewhere on reddit that a guy had the same problem and had to return his device.
PunkOz said:
Everything downloaded to my PC belongs to Android 13, factory image, kernel, everything, didn't rollback, I was in a bootloop where my device went into fastboot mode everytime but then it went to google logo and stopped working at all. Nothing shows on my screen, I've read somewhere on reddit that a guy had the same problem and had to return his device.
Click to expand...
Click to collapse
Yeah I've been watching this out of curiosity as I run Samsung's on 9 and 10. That thread has a lot of good information and links. Someone there may be able to help.
I thought 13 be fubar, it hasn't disappointed
I know you said you tried all combinations of buttons, but when pressing power+volume down, have you tried "fastboot devices" in terminal to see if the device ID shows?
If you can get into fastboot even with no display, you should be able to reflash the factory images.
Edit:
Also, if you're going to try flash custom kernels and want an easy app to use, I'd recommend installing Kernel Flasher as it'll backup all of the modified images and allows you to check the partitions.
lottarake said:
I know you said you tried all combinations of buttons, but when pressing power+volume down, have you tried "fastboot devices" in terminal to see if the device ID shows?
If you can get into fastboot even with no display, you should be able to reflash the factory images.
Click to expand...
Click to collapse
Yes, went to platform tools and used cmd adb devices and nothing shows. It's like stuck booting maybe (?) but with a black screen and won't let me do anything, I'm not even sure if it's charging, I think the only way to reset is remove battery and put it back but it may void my warranty, waiting for it to discharge is impossible as it was 95% charge.
Edit: Will try kernel flasher if I ever get it to boot again. I think my last option is to return it and hope to get a new one, it's my first time hard bricking a device and I've done countless kernels and custom roms since Galaxy S2 and Nexus devices
@PunkOz can you describe exactly how you updated? Did you attempt to flash the custom kernel immediately after the update, or did you let Android 13 boot normally on the stock kernel?
PunkOz said:
Yes, went to platform tools and used cmd adb devices and nothing shows. It's like stuck booting maybe (?) but with a black screen and won't let me do anything, I'm not even sure if it's charging, I think the only way to reset is remove battery and put it back but it may void my warranty, waiting for it to discharge is impossible as it was 95% charge.
Edit: Will try kernel flasher if I ever get it to boot again. I think my last option is to return it and hope to get a new one, it's my first time hard bricking a device and I've done countless kernels and custom roms since Galaxy S2 and Nexus devices
Click to expand...
Click to collapse
ADB and fastboot display different device IDs. You'll want fastboot vs adb when in fastboot mode.
If you can't get it to display and want to get a new pixel, hopefully you're within the return window and can exchange it easily.
Edit:
Reread your OP and the reason you bootlooped from what I gather is that you manually flashed the stock boot.img and kernels now modify more than just the boot.img, so you're in conflict with dtbo, vendor_boot, and vendor_dlkm images. When returning to stock with a custom kernel, you'll need to be sure reflash all of these from the factory zip.
PunkOz said:
Yes, went to platform tools and used cmd adb devices and nothing shows. It's like stuck booting maybe (?) but with a black screen and won't let me do anything, I'm not even sure if it's charging, I think the only way to reset is remove battery and put it back but it may void my warranty, waiting for it to discharge is impossible as it was 95% charge.
Edit: Will try kernel flasher if I ever get it to boot again. I think my last option is to return it and hope to get a new one, it's my first time hard bricking a device and I've done countless kernels and custom roms since Galaxy S2 and Nexus devices
Click to expand...
Click to collapse
it seems like you may have booted a kernel that didn't work, failed boot a few times and threw you onto the A12 bootloader. Would need to verify how you installed android 13
Following....
I have the same problem...blackscreen. All I did was use the command " fastboot flash boot patched_magisk.img”.
Easy solution: using chrome on your pc or mac go to pixel factory firmware and find the the newest update. Plug in your phone and click "flash", select your device, wipe everything and flash all partitions.
rajchelu said:
Following....
I have the same problem...blackscreen. All I did was use the command " fastboot flash boot patched_magisk.img”.
Click to expand...
Click to collapse
If you manage to fix it, I recommend booting the magisk image, instead of flashing it with the 'fastboot boot /patched_boot.img' command
Then direct install in magisk app
If it fails when booting the image, device will just reboot into normal mode.
PunkOz said:
Did I completely brick my device flashing a wrong boot file after my bootloop? Is there any way to recover my Pixel 6 or should I try to return and ask for a new one and see if they accept it?
Sad thing, my Pixel arrived yesterday and I hard bricked it in the same day.
willing to pay anyone here if someone helps me to boot my pixel again.
Click to expand...
Click to collapse
The good news is that your phone is still under warranty!
The bad news is that you now have to USE the warranty.
A13 includes anti-rollback code for the bootloader. Unfortunately, the anti-rollback code BRICKS the device instead of putting you into a recoverable state.
The sequence that killed you is this; you installed A13 and the updated bootloader to one slot, but not the other. You successfully booted A13 at least one time, which advanced the anti-rollback version. You then installed a kernel/boot that was incompatible with A13, which failed to boot a few times, causing it to switch to the other slot (with the old bootloader). Because it tried to run the old bootloader with the updated anti-rollback version, it immediately went into BRICK mode.
DespairFactor said:
it seems like you may have booted a kernel that didn't work, failed boot a few times and threw you onto the A12 bootloader. Would need to verify how you installed android 13
Click to expand...
Click to collapse
I think that's what happened, I installed Android 13 via OTA, had to apply for beta in order to receive the update faster because it wasn't available in my country yet.
Than installed patched boot - magisk - custom kernel via EXKM app and then bootloop and then flashed a few times boot stock and patched and nothing worked. @V0latyle
96carboard said:
The good news is that your phone is still under warranty!
The bad news is that you now have to USE the warranty.
A13 includes anti-rollback code for the bootloader. Unfortunately, the anti-rollback code BRICKS the device instead of putting you into a recoverable state.
The sequence that killed you is this; you installed A13 and the updated bootloader to one slot, but not the other. You successfully booted A13 at least one time, which advanced the anti-rollback version. You then installed a kernel/boot that was incompatible with A13, which failed to boot a few times, causing it to switch to the other slot (with the old bootloader). Because it tried to run the old bootloader with the updated anti-rollback version, it immediately went into BRICK mode.
Click to expand...
Click to collapse
Yeah, I haven't been around XDA community as much as before, it was 100% my fault, didn't read that much before starting to flash custom kernel and boot. Didn't know there were 2 slots. My phone is 100% dead now, I bought it through amazon from a third party store, do you think I voided my warranty? Screen won't turn on at all with any combination of keys (Pwr+Vol) and won't even display when it's charging, completely bricked
If anyone out there has an answer to fixing this problem. Please let us know! I'm also on the same boat. Didn't flash to both slots so now I have a paperweight. Really don't wanna spend money on a new phone so I'll try to be patient and hope someone can be my saviour
So does anyone have an update about this problem? I'v eread somewhere that it could be in EDL mode when the screen doesn't turn on. Could that be the case and could we do something with that?
Markelijk said:
So does anyone have an update about this problem? I'v eread somewhere that it could be in EDL mode when the screen doesn't turn on. Could that be the case and could we do something with that?
Click to expand...
Click to collapse
We don't have tools to deal with this processor's EDL mode, so unfortunately it's likely the only fix is to reach out to Google to have it repaired under warranty.
Shot in the dark here...but this reminds me of people only flashing to one slot and the phone rebooting into the other "okd OS" slot and the phone bricking. So this is a little different...the phone MIGHT be on, just on a big black screen that just shows nothing. So yes it IS "bricked".
But UNPLUG the phone, give it about 10 seconds, then press and hold power, volume up and volume down, preferably OUT of the case, and just hold it for like a minute. After thirty seconds or so it might forcefully reboot, if it does, then we need to get into fastboot and reflash A13, but then ALSO flash it to the other slit. This is why it is SO IMPORTANT to flash BOTH SLOTS.
I had THIS problem on my Oneplus 6T, yes...a different phone...but it my phone was DEAD for a week before I discovered that I could force boot it.
But if you have the phone connected to the pc, the bootloader or whatever is trying to talk will not allow the phone to do anything.
Also, plug the phone into the charger. If it is in a hard soft brick and the phone DIES it can be a NIGHTMARE to get it back to life, usually involving you JUMPING the battery manually....like I said. A shot in the dark. But worth a shot.
Hi all;
I writing to ask if I can get support from you in order to recover data from my phone. This is the situation I have a Xiaomi 10T 5G device that 4 days ago suddenly reboot and get stuck on MI logo screen. I have try entering in Recovery mode and test Reboot, Safe Mode and Repair Mode with no luck. I have try also to connect it to MIPC suit but the phone get not detected, only if I put it in fastboot mode I got a message from PC suite telling that I should change to Normal mode and reconnect.
I have installed ADB drivers and my usb drivers of my device.
The issue and before sending it back for reparation I want to backup the photos, all the other data is not relevant. The phone is with the fabric ROM. Is there any way that I can recover the data??
Thanks in advance for your support.
locked bootloader? unlocked?
GizmoTheGreen said:
locked bootloader? unlocked?
Click to expand...
Click to collapse
I assume is blocked as nothing g has been done to it since the purchase.
That happened to me twice. I was pushing it to recovery, fastboot, safemode for over and hour untill it turned on. It was after update last spring. Never happened again. I cant remember what happened (i know i realized it than, but i was on a business trip and pissed, just remember that prior to that it was a problem with unlocking it/power button/sensor, maybe not the same thing as you have, since it was looping),i think it was some bug
Hi thanks for the reply but I assume is not the same case as I have try to fastboot, safe mode and repair mode a lot of times and nothing happened.
Hope to find a way to get the data from the device.
zepo88 said:
Hi thanks for the reply but I assume is not the same case as I have try to fastboot, safe mode and repair mode a lot of times and nothing happened.
Hope to find a way to get the data from the device.
Click to expand...
Click to collapse
it may be stuck in some kind of recovery loop because it crashed and think it couldn't boot. like windows does.
try turn it completely off then start it.
I'm sorry if you did not unlock before hand, there is nothing you can do.
flashing rom requires unlocked bootloader. running TWRP requires unlocked bootloader.
flashing stock rom/ recovery rom from SD will I think wipe your data
unlock bootloader will wipe your data.
if you can't get it to boot you are SoL for the data friend :/
Thanks Sir. Seen that there is no option I have wipe all the data and the phone has come back again to normal operation. Now I will try to root to use some data recovery tool to see what I can get. Any recomendations??
My device went into brick while flash android14 fail .At the beginning,it can boot to fastboot mode,but now it's no response at all& can't get into fastboot.The google help center need original purchase email ID for further help,i can't find it due to I bought the pixel6 pro from second hand market .
How to rescue the pixel6pro brick without fastboot?
Google pixel flash tool online and boot into fast boot follow instructions and you should be able to bring it back
Here's the link:
Android Flash Tool
flash.android.com
thelostsoul89 said:
Google pixel flash tool online and boot into fast boot follow instructions and you should be able to bring it back
Here's the link:
Android Flash Tool
flash.android.com
Click to expand...
Click to collapse
thanks for your advice,but the device can't boot to fastboot mode
ok6669 said:
thanks for your advice,but the device can't boot to fastboot mode
Click to expand...
Click to collapse
I apologize your original post said that it can... not that it can't
thelostsoul89 said:
I apologize your original post said that it can... not that it can't
Click to expand...
Click to collapse
thelostsoul89 said:
I apologize your original post said that it can... not that it can't
Click to expand...
Click to collapse
^_^
Can you boot into the recovery? You could sideload an ota
Code:
adb sideload "path to ota.zip"
Tip: right click on the ota.zip and select 'copy as path' and paste it
fil3s said:
Can you boot into the recovery? You could sideload an ota
Code:
adb sideload "path to ota.zip"
Tip: right click on the ota.zip and select 'copy as path' and paste it
Click to expand...
Click to collapse
nope,brick deeply
ok6669 said:
My device went into brick while flash android14 fail .At the beginning,it can boot to fastboot mode,but now it's no response at all& can't get into fastboot.The google help center need original purchase email ID for further help,i can't find it due to I bought the pixel6 pro from second hand market .
How to rescue the pixel6pro brick without fastboot?
Click to expand...
Click to collapse
Did you hold power and volume up for 15-30 seconds? Also, did you try and charge it? Could be dead
Let's put it this way, you're phone won't awaken until it's internal signature can be re verified. It uses ACM as an initial protocol then goes into a serial gadget mode. At the current moment someone straight up stole my Pixel 6 or else I would still be working on a unbrick solution. If anyone's willing to donate a bricked one I'm all for putting in the effort to continuing development.
The nature of the dead brick is to ensure that no data on your phone can be compromised. So the the method to unbricking also requires you to a sort of NAND erase, as seen on previous Exynos devices. I had just gotten all the tools set up and even made my own ACM handshake in coordinance with the Open Source Vendor Code and someone just decided, oh hey, look it's a nice phone let's take it. And now I have to continue making payments on it. Life sucks sometimes.
NonStickAtom785 said:
Let's put it this way, you're phone won't awaken until it's internal signature can be re verified. It uses ACM as an initial protocol then goes into a serial gadget mode. At the current moment someone straight up stole my Pixel 6 or else I would still be working on a unbrick solution. If anyone's willing to donate a bricked one I'm all for putting in the effort to continuing development.
The nature of the dead brick is to ensure that no data on your phone can be compromised. So the the method to unbricking also requires you to a sort of NAND erase, as seen on previous Exynos devices. I had just gotten all the tools set up and even made my own ACM handshake in coordinance with the Open Source Vendor Code and someone just decided, oh hey, look it's a nice phone let's take it. And now I have to continue making payments on it. Life sucks sometimes.
Click to expand...
Click to collapse
I think you are the one unbrick the pixel 6pro who is the most closest.i fell that you are very humor person.Life can't be as good as you think, but it won't be as bad as you think
So I have the same problem. It restarted and said something about your files are corrupt and cannot be trusted. I got it to boot to bootloader, used android tool online and it did the same thing. Now I cannot get the phone to turn on at all. So now I need help please!!! I cannot afford to buy a new phone currently.
did you try plugging in for 30 mins? If can’t boot to anything after that, only Google can fix it.
Arealhooman said:
did you try plugging in for 30 mins? If can’t boot to anything after that, only Google can fix it.
Click to expand...
Click to collapse
Yeah Google's fix is $600. Which is ridiculous. I had it plugged in all day, now I just have it sitting on my dresser hopefully it will just start on it's own. I don't know what else to try. I tried pressing the power button for 60 seconds. I tried power volume up for 60 seconds. I tried power button volume down for 60 seconds. Nothing seems to work. Yet if I plug it in to my laptop, you can hear the ding as if it connected. So I don't know what to think.
Jdemio said:
Yeah Google's fix is $600. Which is ridiculous. I had it plugged in all day, now I just have it sitting on my dresser hopefully it will just start on it's own. I don't know what else to try. I tried pressing the power button for 60 seconds. I tried power volume up for 60 seconds. I tried power button volume down for 60 seconds. Nothing seems to work. Yet if I plug it in to my laptop, you can hear the ding as if it connected. So I don't know what to think.
Click to expand...
Click to collapse
Sounds like a dead display, especially if its being recognized by a laptop
ok6669 said:
My device went into brick while flash android14 fail .At the beginning,it can boot to fastboot mode,but now it's no response at all& can't get into fastboot.The google help center need original purchase email ID for further help,i can't find it due to I bought the pixel6 pro from second hand market .
How to rescue the pixel6pro brick without fastboot?
Click to expand...
Click to collapse
If your phone is recognized as Pixel Rom recovery, then I am very sorry to you. only the official Google service will save you, or you will find the same phone with a broken screen in the trash that you can take a fee from there and put it on yourself
Jdemio said:
Yeah Google's fix is $600. Which is ridiculous. I had it plugged in all day, now I just have it sitting on my dresser hopefully it will just start on it's own. I don't know what else to try. I tried pressing the power button for 60 seconds. I tried power volume up for 60 seconds. I tried power button volume down for 60 seconds. Nothing seems to work. Yet if I plug it in to my laptop, you can hear the ding as if it connected. So I don't know what to think.
Click to expand...
Click to collapse
What is it recognized as?
Arealhooman said:
它被认为是什么？
Click to expand...
Click to collapse
pixel cdc -amc device! and then disappear
idark11 said:
If your phone is recognized as Pixel Rom recovery, then I am very sorry to you. only the official Google service will save you, or you will find the same phone with a broken screen in the trash that you can take a fee from there and put it on yourself
Click to expand...
Click to collapse
Google is not serve in our country,asking google for help is not convenient for me
ok6669 said:
pixel cdc -amc device! and then disappear
Click to expand...
Click to collapse
Pic?
Jdemio said:
Yeah Google's fix is $600. Which is ridiculous. I had it plugged in all day, now I just have it sitting on my dresser hopefully it will just start on it's own. I don't know what else to try. I tried pressing the power button for 60 seconds. I tried power volume up for 60 seconds. I tried power button volume down for 60 seconds. Nothing seems to work. Yet if I plug it in to my laptop, you can hear the ding as if it connected. So I don't know what to think.
Click to expand...
Click to collapse
i think google have the secret weapon to recover the brick pixel,it 's a simple software problem for google. a piece of cake