Related
Hi!
I just had the weirdest experience with my sgsii
I have been using the unofficial vsync patched cm10 rom for this modelfor the last month or so.
I have been updating at least one per week but this week I decided to give my phone a break and not flash it... i am actually really busy at job.
Suddenly tonight, the phone looked like when you have a SOD... so i just pulled the battery.
Now, it does not pass from the first logo stage, just prior to start booting.
I cannot access cwm recovery either, but download mode seems to work-
Now the odd thng is that i am attempting to flash somethng to get the phone working but it gets stuck in the step "NAND Write start!".... it goes no furter than that...
I have chosen the options auto reboot and f.reset time.
a pda file, phone and csc file from the eaked jb rom.....
The system I am attempting to flash from is a windows 7 pro 64 bit.... and odin is Odin3 v1.85...
Please, tell me i didnt get a brick and there is a way tofix it... :crying:
EDIT: Desperated, i tried to flash latest jb leak again, and chose the pit file that comes with it, which re-partitions the phone...
After 20 minutes not responding, i pulld the battery out... now i cannot even enter download mode....nothing....nada....
Sounds like you bricked it, good job.
Sent from my GT-I9100 using Forum Runner
GFXi0N said:
EDIT: Desperated, i tried to flash latest jb leak again, and chose the pit file that comes with it, which re-partitions the phone...
After 20 minutes not responding, i pulld the battery out... now i cannot even enter download mode....nothing....nada....
Click to expand...
Click to collapse
too bad never repartition unless you make your own pit file with heimdall .. if you would've wait a couple hours I just pmed you.
and for other people instead of flashing samsung's bricksquadroms you can flash CM9 resurrection edition. http://forum.xda-developers.com/showthread.php?t=1419102
Make a pit file with heimdall of your own device. Don't trust pitfile that comes with a rom.
I re-partitioned my device and i got like 3GB intern memory back.
There's probably a way to get your device alive. it isn't the mmc cap bug so. search some threads on xda about brickbugs etc of galaxy phones and you'll find people who hardbricked and unbricked their device.
Probably usb jig could get you into download mode i'm not sure though. Or else jtag. Ask some people over there they will know it
I will try to revive it with jig.... i must find the thingy though.,..... if not.. i will send it to the service but i'm not sure i'm on warranty....
Being not patient made me f*ck it up bad....
Any clue on how to recover a phone after re-partitioning.... i really don't know where to start...
EDIT: JIG does not switch it on either... why did i have to re-partition?!??!?!?!?!?!
That was a dumb move....... any more ideas?
If you cant enter recovery or download mode you have no choice but to JTAG repair or mobo replacement.
Hard brick.... on its way to service
Wish me luck..
Mobo replacement it is, this incident will at least teach you to be patient, I explained you my problem in PM, I waited for 1 week for USB jig to arrive from eBay then flashed stock ROM. I trust the f/w it came with the most.
Sent from my GT-I9100 using xda app-developers app
Sh4Dy said:
Mobo replacement it is, this incident will at least teach you to be patient, I explained you my problem in PM, I waited for 1 week for USB jig to arrive from eBay then flashed stock ROM. I trust the f/w it came with the most.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
USB JIG didn't work at all..... I have one and it was not able to boot the phone ....
Isn't this kind of brick fixable with Jtag?
Sent from my GT-I9100
Ok, before I repartitioned, making the problem worse, I was experiencing some kind of R/W problem..... there was something odd with the nand because I was able to boot in download mode, but not in recovery (CWM) mode....
Then, when I plugged the phone to the computer, Odin was able to recognize the phone.
I followed some thread around XDA to flash 4.1.2 leak from sammy and when I hit the "Start" button in Odin, it would not pass from the first stages, revealing that R/W or I/O problem.... the internal nand was, somehow broken.... it didn't read or write properly.... so, even If i could find a workaround, I would have lost some internal storage (some posts talk about around 3 Gb or something similar as lost space in these cases).... that is IF i had been able to fix it..... but then, that's what warranty is for..... so I gave it a last (dumb) try..... including the pit file, which attempted a format, which ended messing (i would say the f. word) everything up.
The good side is that unable to even boot, at least i lost the blue loading bar the vsync patched cm10 mod has in the first bootup screen.... which could have revealed to sammy that I was tempering with unofficial roms....
Lesson learned: Be patient people: But also, don't think this could not happen to you: The phone was perfectly working the last time I saw it... and I even was making some phone calls and browsing the internet.... I mean... it gave no prior symptoms or warnings... I t just died..... I guess I have to be glad I'm not one of those people whose phone gets caught up on fire on their pockets for malfunctioning.....
Now waiting for it to come back revived from samsung..... I have hope
hope it will be able to recover
Great: After losing the phone and past almost three months, samsung says the phone has been manipulated and the warranty is voided....
I wasn't able to flash back an original firmware prior to sending it to the tech service.....
What do you recommend me to do?
I guess paying for the repair would be quite expensive....
GFXi0N said:
Great: After losing the phone and past almost three months, samsung says the phone has been manipulated and the warranty is voided....
I wasn't able to flash back an original firmware prior to sending it to the tech service.....
What do you recommend me to do?
I guess paying for the repair would be quite expensive....
Click to expand...
Click to collapse
Well what is it you expect us to say, some secret magic word that will fix it for free?
The choice is pay for it to be fixed or dont.
So no magic word or secret passphrase so they will upgrade my device to a SGSIV for free?
Damn.....
I'm asking for advice, since I'm convinced the brick was not caused by flashing anything.....
Does anyone have any experience with this in the past to know more or less how expensive bill could I be facing for the repair?
GFXi0N said:
So no magic word or secret passphrase so they will upgrade my device to a SGSIV for free?
Damn.....
I'm asking for advice, since I'm convinced the brick was not caused by flashing anything.....
Does anyone have any experience with this in the past to know more or less how expensive bill could I be facing for the repair?
Click to expand...
Click to collapse
Dude, it WAS caused by flashing something.
Initially your device wasn't "bricked" and was likely a kernel issue and possibly a dirty usb data connection.
The point when it was bricked was when you tried flashing the pit file, had bad connection and you then pulling battery. This f**ked your nand chip up and only way to fix it is to replace motherboard.
You will need to either purchase a mobo replacement and replace it yourself or pay somebody to purchase/replace it for you. Probably looking at around £100.
When bricks happen, you really need to BRICK it before claiming warranty.
I've got a couple of guys here that own a PhD in bricking.
Brick is the new flash.
Sent from the little guy
Jig wasn't working
Flashing anyting.. even just a recovery wasn't working
FLashing official didnt work
Flashing CM didnt work either
Tested different cables and different ports
It was f*cked up already... anyway: 4 samsung devices owned: 3 gave problems of hardware..... that cannot be a coincidence...
Repartitioning erased my tracks, if anything... because the 3 key combo for recovery was working until then..... but either way they managed to access the memory somehow, I guess.....
GFXi0N said:
anyway: 4 samsung devices owned: 3 gave problems of hardware..... that cannot be a coincidence....
Click to expand...
Click to collapse
Maybe a PEBCAK?
GFXi0N said:
Jig wasn't working
Flashing anyting.. even just a recovery wasn't working
FLashing official didnt work
Flashing CM didnt work either
Tested different cables and different ports
It was f*cked up already... anyway: 4 samsung devices owned: 3 gave problems of hardware..... that cannot be a coincidence...
Repartitioning erased my tracks, if anything... because the 3 key combo for recovery was working until then..... but either way they managed to access the memory somehow, I guess.....
Click to expand...
Click to collapse
Don't blame the phone, blame the user.
Yeah, sure... anyway... thanks for the help... I hope some day you need it and someone will come not trying to mocking you..... anyway... this is the trend around here lately...
Happy trolling
Hey guys i have read hundreds of posts and just want to know if i am missing anything before i count this as a total loss.
I was about to upgrade from Hairy Bean 3.5 to 4.2 I am rooted and unlocked.
First i have done many roms on many devices.
What i did was tried to get into clockwork, 2 times i shutdown and did the vol down and power and then hit vol up and it would say loading recovery kernel but never made it anywhere, so i held power down until it reboot into android, the i did the reboot into recovery from android and it did the same them, next i opened rom manager did the latest clockwork recovery and then rebooted into recovery from rom manager, it shut off and made it back to the Asus logo with the "the device is unlocked" in upper left corner and the Nvidi Tegra in lower right corner. Thats as far as i can get. i have tried the vol down and power again and nothing. it always gets back to that screen.
I can hold both power buttons and connect the usb and computer will see a APX and Unknown device in windows manager, but no drivers, i have tried the universal drivers but they dont work. i also download the asus stuff from asus and nothing helped either.
Any help would be great. Thanks to this great forum and great people as i have used it for years.
soloblazer said:
Hey guys i have read hundreds of posts and just want to know if i am missing anything before i count this as a total loss.
I was about to upgrade from Hairy Bean 3.5 to 4.2 I am rooted and unlocked.
First i have done many roms on many devices.
What i did was tried to get into clockwork, 2 times i shutdown and did the vol down and power and then hit vol up and it would say loading recovery kernel but never made it anywhere, so i held power down until it reboot into android, the i did the reboot into recovery from android and it did the same them, next i opened rom manager did the latest clockwork recovery and then rebooted into recovery from rom manager, it shut off and made it back to the Asus logo with the "the device is unlocked" in upper left corner and the Nvidi Tegra in lower right corner. Thats as far as i can get. i have tried the vol down and power again and nothing. it always gets back to that screen.
I can hold both power buttons and connect the usb and computer will see a APX and Unknown device in windows manager, but no drivers, i have tried the universal drivers but they dont work. i also download the asus stuff from asus and nothing helped either.
Any help would be great. Thanks to this great forum and great people as i have used it for years.
Click to expand...
Click to collapse
You have bricked your device.
You have installed an ics recovery onto the jellybean bootloader. There are warnings everywhere on xda saying not to use cwm on the prime.
If you cannot get back to the bootloader menu where the icons are or you cannot boot back into android it is game over I'm afraid.
flumpster said:
You have bricked your device.
You have installed an ics recovery onto the jellybean bootloader. There are warnings everywhere on xda saying not to use cwm on the prime.
If you cannot get back to the bootloader menu where the icons are or you cannot boot back into android it is game over I'm afraid.
Click to expand...
Click to collapse
So am i stuck? i didnt know it was a ICS recovery? i have used CW on the unit for almost a year and half, and never had a issue until today. Is there somewhere i can send the prime to, to get it fixed? or is it back to ASUS and pay them big bucks to fix it? Is there anything at all i could try before giving up on it?
thanks
soloblazer said:
So am i stuck? i didnt know it was a ICS recovery? i have used CW on the unit for almost a year and half, and never had a issue until today. Is there somewhere i can send the prime to, to get it fixed? or is it back to ASUS and pay them big bucks to fix it? Is there anything at all i could try before giving up on it?
thanks
Click to expand...
Click to collapse
You have not used cwm on that device since that nvidia logo has been bottom right. You updated the bootloader with a ROM at some point to jellybean and that is why you had no recovery there. You then tried putting cwm back on which was not for jellybean and you killed it sorry.
Only hope now Is Asus who could charge you up to 200 dollars to fix it.
Edit. there was a custom cwm at one point made by Wookie for his port of the tf300 ROM to the prime originally. This was never given out for long but the versions you say of hairybean in your first post never existed. We are only on 2.2 now and you are talking about 3.5 and 4.2.
flumpster said:
You have not used cwm on that device since that nvidia logo has been bottom right. You updated the bootloader with a ROM at some point to jellybean and that is why you had no recovery there. You then tried putting cwm back on which was not for jellybean and you killed it sorry.
Only hope now Is Asus who could charge you up to 200 dollars to fix it.
Edit. there was a custom cwm at one point made by Wookie for his port of the tf300 ROM to the prime originally. This was never given out for long but the versions you say of hairybean in your first post never existed. We are only on 2.2 now and you are talking about 3.5 and 4.2.
Click to expand...
Click to collapse
Sorry i was on 1.5 and was going to go to 2.11. Not sure were i got the other numbers. I guess i will try to send it back to ASUS and see what happens if there is nothing else to do.
So is it a software or hardware isssue? I am assuming is software issue and there is just not a way to reflash it?
thanks again for the help.
soloblazer said:
Sorry i was on 1.5 and was going to go to 2.11. Not sure were i got the other numbers. I guess i will try to send it back to ASUS and see what happens if there is nothing else to do.
So is it a software or hardware isssue? I am assuming is software issue and there is just not a way to reflash it?
thanks again for the help.
Click to expand...
Click to collapse
Most times Asus will try to replace the motherboard which is not needed.
If you be straight with them and tell them you messed up the recovery partition when flashing it and that there is nothing wrong with the hardware and could they please reflash it you might get lucky and have less of a bill.
flumpster said:
Most times Asus will try to replace the motherboard which is not needed.
If you be straight with them and tell them you messed up the recovery partition when flashing it and that there is nothing wrong with the hardware and could they please reflash it you might get lucky and have less of a bill.
Click to expand...
Click to collapse
Ok i will see what happens, so is it just a flash they have to do? I am assuming you need a special machine to flash it or is it done from a computer to flash it?
Update:
So i sent my prime back to Asus, after a week they said it was customer induced damaged and was not covered under warranty. They said it need to have the motherboard replaced at a cost of almost $300.
I told them what i did, as someone here told me to, and said i mess up the recovery partition and it just needed to be flashed and didnt need a new motherboard.
This is there response:
There are limitations to what we can do on the service side and the service dept does not have the capability to flash the unit so all we can offer is hardware replacement. Please advise.
Not sure what to do next, am i just out of luck? i can buy another one for less then $300?
Thanks for the help again.
buy a motherboard on eBay - $80 - $100, I just did, I replaced
I just did the same thing to mine; installed CMW on my TF201 latest stock JellyBean. Unlocked and rooted. Only had the thing for about a week. Can you tell me if the "mainboard" they are selling on ebay will work? Also did you find a tutorial to follow with replacing the board - if so where? Thanks - Bill
Yes does anyone know of, or have a video tutorial on how to take these apart and replace, i changed the digitize on my TF101, not a big deal.
Hey guys !
Well...
Yesterday, I decided to flash a new ROM on my aunt's SII...
It wasn't the first time I did this : my own phones have all been flashed, I know how it works !
But... I got a problem ! While I was wiping the data/cache, the phone got stuck on this step. Then, shut down. And now, it doesn't boot anymore. Screen stays black. I did everything I found on the web : tried to boot on recovery and on download mode, tried to press the buttons to get into these modes and inserting the battery while pressing, tried to connect it on USB (not even detected)...
After some researches, I found out that it was a eMMC problem...
Anyway, in a nutshell, my phone is hard bricked. What can I do ?
Thanks.
rohecla said:
Hey guys !
Well...
Yesterday, I decided to flash a new ROM on my aunt's SII...
It wasn't the first time I did this : my own phones have all been flashed, I know how it works !
But... I got a problem ! While I was wiping the data/cache, the phone got stuck on this step. Then, shut down. And now, it doesn't boot anymore. Screen stays black. I did everything I found on the web : tried to boot on recovery and on download mode, tried to press the buttons to get into these modes and inserting the battery while pressing, tried to connect it on USB (not even detected)...
After some researches, I found out that it was a eMMC problem...
Anyway, in a nutshell, my phone is hard bricked. What can I do ?
Thanks.
Click to expand...
Click to collapse
what stock firmware version was the Phone when u did the wipe from recovery (if it was on ICS 4.0.4 then ur phone will be bricked because of the kernel of ICS4.0.4 being plagued with the 'EMMMC' brick bug and only a JTAG or a MB replacement is the solution for it) .
JTAG won't work; motherboard replacement or bin.
I think it was 4.0.4...
Motherboard replacement is the only thing I can do ?
Mate.... Samsung KNOWS this is a problem.......I'd try for warranty repair/replacement.....if the phone is less than two years old, you have a good chance......
Just remember to 'act dumb' at the service center..... Tell them you were trying to use kies to update from ICS and the phone died...... If it is the emmc brickbug, there's NO WAY they can check what os was on ur phone or whether you'd rooted or modified it in any way.....right now it's an unrecoverable (expensive) paperweight........
This might be my S2, or it might be my W...but it's definitely CM
Yeah, I saw this is a quite common problem... But often, it's just a soft brick. In my case, it's a hard brick...
And warranty expired two months ago...
Well, it's unlikely to succeed, but you could try emailing Samsung explaining your situation regarding expired warranty and going on to explain that updating with kies is a 'normal' procedure and that it's that 'normal' Samsung provided procedure plus the 'unstable' OS version (having read on the internet about 4.0.4 brickbug) that have killed a phone that would otherwise be working today. Stress the point that the ICS firmware AND kies were both supplied by Samsung for official (end user) use on Samsung devices......see what they say.....can't hurt right?
This might be my S2, or it might be my W...but it's definitely CM
Yeah, they're going to honour an expired warranty. That happens all the time
Mb....I *did* say right at the start that it probably wouldn't work..... But what has he got to lose?
Lol.....they *might* be suffering from an excess of Xmas and new year goodwill.......
This might be my S2, or it might be my W...but it's definitely CM
I have twice super bricked my two SGS-2s.... EMMC bug is one hell of a pain in ass. You have to let go some SD card space, but u can revive you phone using the URL in my signature. I revived both my phones losing about a GB space in one and a couple GBs in other. Good Luck
alvinasnow said:
but u can revive you phone using the URL in my signature
Click to expand...
Click to collapse
People have said he needs a new motherboard.Do you know something they dont?.
S4 victim
The problem is that I can't flash anything ! The phone simply doesn't turn on ! No recovery mode, no download mode, nothing ! It doesn't even charge !
Yes try this link from alvinasnow
http://forum.xda-developers.com/showthread.php?t=1667886
So far as I know if you only connect your phone normally if it os charging then it already has some kind of connection with the pc I believe its adb.
But since you dont have warranty you can give it a shot to save money so just give it a try and read carefully. I was surprised when I got this phone, that samsung would make a big mistake like that its a just shame.
Edit: i dont know or you need jtag or riff and I will not test it cause I dont have a superbrick phone with mmc cap erase.
But just open device manager on the pc and connect the phone and see if there is a new device connected.
In my opinion my previous phone has one of the best options to make it unbrickable
It was nvflash but it sucked.nvidia wouldnt release sources.
Gooodluck with your phone
Sent from my GT-I9100 using Tapatalk
Which part of this phone needs a motherboard replacement are you lot having trouble comprehending ?
OK...For all the slow kids who keep posting to this thread (including the OP); this phone needs a new motherboard. No threads promising magical fixes are going to work, there is no other way to fix this.
Is this clear now or do I have to make another post in bolded caps to make it really clear ?
There is a SLIGHT chance that if a JTAG recovery house can boot a kernel via JTAG (I do not know if RIFFBox can do this or not), they can use the solution that the Kindle Fire community used. (This was a recent discovery 2-3 months ago)
The problem is, I have attempted to provide information on this solution to these JTAG houses with no response. I don't know if they can boot a modified kernel via JTAG or not.
Currently:
All Exynos4 devices that are Superbricked are unrecoverable, as Samsung refuses to provide any way to boot these from USB, and anyone who could develop a solution hasn't responded (since most dead devices are long gone at this point...)
All Qualcomm-based Samsungs that are Superbricked are hosed too
Kindle Fires that are Superbricked are recoverable as of 2-3 months ago thanks to some discoveries by Oranav that were used by Hashcode to develop a recovery solution. This solution can't be used on Samsung Exynos4 devices as it depends on the ability to boot the device from USB.
And folks...... @Entropy512 needs to be listened to.......he is the dev who has done the most research into this issue and (somebody cmiiw) was the one who discovered the "emmc cap erase" command was the culprit. I think he also wrote the original (much copied) 'got brickbug' app which tells you if your phone is affected or not. If what he says doesn't work, then as @MistahBungle says, the ONLY OTHER OPTION is a new motherboard........
This might be my S2, or it might be my W...but it's definitely CM
Well...
I think I'm just going to call the insurance, and see what they can do ! Even if my warranty is now void, they may replace the phone !
Thank you all !
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.
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.