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.
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
Dear All,
Before I start, please forgive the repetition, as I know this issue comes up a lot but I've searched all over and can't find a solution for my circumstance. If there's a post I've missed, please direct me there...:fingers-crossed:
I recently received a Lumia 800 with a Qualcomm bootloader, sim-locked to a UK network. The first thing I did was use NSSPro to remove the simlock, which was successful, but I also wanted to debrand and try a custom ROM..
I read round the issue a fair bit and was going to go down the Linux 'dd' route when I spotted the Windows flashing utilties. Ever keen for an easy life, I went ahead and flashed my handset with FunkyRom, apparently making two fatal errors; not backing up my partitions in Linux and not using Linux to do the flash. Laziness stopped me backing up and I'm aware I deserve what I get for that, but the warnings about flashing in Windows were a little harder to spot and I only found those after the event.
ANYWAY....
Unsurpisingly it turns out, the Windows flash bricked the 'phone. I can get it into Qualcomm bootloader mode in Windows and Linux, I can read the partition map (attached), flash it in NSSPro, 'dd' it in Linux and flash it with the Windows tools, but it won't boot past the Nokia logo. After initial flashing the battery went haywire as well and wouldn't hold it's charge much beyond ten minutes. The battery is fine, I have swapped it out for a new one and it works fine in another 'phone, so I'm not sure what that was about. One other thing to note is I've never been able to hard reset it after flashing, the combination of button presses does nothing, no matter how long I hold them down, all that happens is the 'phone reboots if I release the power button.
I've tried many reflashes, replacing the third partition etc but I think I'm just laying s**t on top of s**t now and would appreciate some guidance. I don't think it's terminally bricked because I can still read/write from/to it in Linux, NSSPro etc, but I'm normally a Nokia N9 man, so this partition structure is unknown, I don't know what I'm looking for.
Any help much appreciated, with the note that I realise I ballsed up not making a backup, so you can skip telling me I'm a fool, I'm getting that enough from the missus..!
Sorry for the looong first post,
Squid
Not sure about fixing it as I have the 710, but Im pretty sure you could RMA to the place you bought it, and they would be too lazy to do full checks on what you did to it, send it back to Nokia and send you a replacement
I've bricked tablets and GPUs and phones and RMA'd, and not once have they ever questioned what I did
One phone I RMA'd I'd flashed a German ROM to and everything was stuck in German, UK company just walked me through factory resetting it on the phone, didn't work obviously, so they gave me a new one
Just an idea if you can't fix it yourself
Other options would be taking it to a local phone repair store who have tools to flash bricked phones, there have been a few here who didn't read the "DO NOT FORMAT" posts, and hit the format button bricking their phones, took it to a repair store who flashed it back to a working state for them
Good luck
Hi and thanks for the reply.
I'll be honest, I'm a Nokia N9 man myself, I was hoping to unlock this one as a spare's spare (it looks and feels familiar), so I'm unlikely to be taking it for repair if I can't get it going myself, but it's interesting to hear you've never been questioned about any DIY work you may have done, I've always thought they'd be hot on that...?
I am holding out for a technical hint or two on something I may have borked during the flash itself, and whether that might be recoverable, after all I can get to the bootloader, just whatever I flash on top (FunkyRom, Rainbow Mod etc) just don't load. Also, why doesn't hard reset work on this 'phone? I have questions but I've run out of brains for answers.
Are there generic full partition dumps available to dd in Linux that would be like a vanilla image? Are there specific partitions that may be the problem? If it gets to the Nokia logo but no further, how far in the booting process has it come?
Squid
Hi John,
Maybe you can try this: http://forum.xda-developers.com/showpost.php?p=47076870&postcount=2
Otherwise I can download an original rom for you, maybe you can flash that with nss, just let me/us know.
Greetz,
Rataplan said:
Hi John,
Maybe you can try this: http://forum.xda-developers.com/showpost.php?p=47076870&postcount=2
Otherwise I can download an original rom for you, maybe you can flash that with nss, just let me/us know.
Greetz,
Click to expand...
Click to collapse
Brilliant, I'll take a look at the NSU first, thanks!
Rataplan,
No joy with the NSU Retail I'm afraid. Do you think you could let me have an original ROM please as mentioned? After that, I guess it goes to the bin..
John
Ok, gonna download and upload this evening, keep you informed.
Greetz,
Rataplan said:
Ok, gonna download and upload this evening, keep you informed.
Greetz,
Click to expand...
Click to collapse
Great, thanks!
john smash said:
Great, thanks!
Click to expand...
Click to collapse
Ok John, you can download the rom here: https://dl.dropboxusercontent.com/u/9417919/rm-801.7z , the rom is based on RM801_059L8M3_1750.0805.8773.12220, I also suggest to read this: http://forum.xda-developers.com/showthread.php?t=1457341 and
this: http://forum.dailymobile.net/index.php?topic=77419.0
Greetz,
Many thanks, I'll try it later. I have actually tried those threads you linked previously but I'll take another look.
Cheers,
John
Hey there Rataplan,
No dice I'm afraid. I can't get the phone connected in anything other than Qualcomm mode, so I can't use NCS to flash. I can use NSSPro to flash a file with .nb extension but not the files you uploaded. NSU Retail asks me to connect in Qualcomm mode then doesn't recognise the phone once I do that.
I just don't understand how if I can get to the Qualcomm bootloader, why flashing RainbowMod or FunkyRom/FunkyRom lite doesn't work, do you have any suggestions? Is there a way to check if any of my partitions are corrupted?
JS
EDIT - Just read this post - http://forum.xda-developers.com/showpost.php?p=29583840&postcount=2 and renamed the boot.img of the ROM you uploaded. Now my 'phone shows a 'Three UK' splash screen, then the nokia logo, but still doesn't load. Is there a way to know what stage of the boot the 'phone is getting to before it hangs?
Ha! Got it!
Using the extract and rename method I flashed the 11412 firmware (oldest one in Navifirm) for product code 059M062 and bingo! It boots and there's no simlock...
Thanks for all your help Rataplan, 'phone revived!
:victory:
Great, I know it had to work, that's why I gave you an copy of an older rom, I'm glad you solved it yourself , take care next time.
Greetz,
Rataplan said:
Great, I know it had to work, that's why I gave you an copy of an older rom, I'm glad you solved it yourself , take care next time.
Greetz,
Click to expand...
Click to collapse
Will do..
I've changed my product code with NSSPro but if I try to flash any later ROMS then it goes back to being borked. I can always recover to this ROM now but I'm wondering why I can't upgrade?
john smash said:
Will do..
I've changed my product code with NSSPro but if I try to flash any later ROMS then it goes back to being borked. I can always recover to this ROM now but I'm wondering why I can't upgrade?
Click to expand...
Click to collapse
I have to take a look at your product code, did you try Nokia Update Retrailer.
The original product code was 059L7C6, I've successfully flashed it with a ROM for product code 059M062 and confusingly, I've written the product code 059L7C2 with NSSPro..
Does it bork it if you try to update it through Zune ?
*Detection* said:
Does it bork it if you try to update it through Zune ?
Click to expand...
Click to collapse
Hey,
Just plugged it into Zune now and it's offering me 7.10.7740.16. Question: Does using Zune overwrite the Qualcomm bootloader? Once that's gone I know I can't get any custom ROMS loaded on here..
Thanks,
JS
For those who may be interested:
I've got a working Lumia now, flashed with a 12220 firmware on a UK product code but that's it, I can't get anything more up to date on there. Every time I flash something more recent I get stuck at the Nokia screen. In addition, I get the same result with any of the custom ROMs, they just won't load. Could my hardware version be preventing the upgrade? Any ideas..?
JS
john smash said:
Hey,
Just plugged it into Zune now and it's offering me 7.10.7740.16. Question: Does using Zune overwrite the Qualcomm bootloader? Once that's gone I know I can't get any custom ROMS loaded on here..
Thanks,
JS
Click to expand...
Click to collapse
No the update doesn't overwrite the bootloader, I flashed the unlocked bootloader to mine and have flashed custom & stock & custom & stock in that order and everything stayed unlocked
I dont know why but I did the Stock 4.3 update via Odin. I was rooted and unlocked 4.1.2
Now I've been stuck on the samsung logo since last night (not the bootloop, just frozen)
I've tried to install older stock roms and they all succeed thru Odin. Ive tried with and without pit files. Ive looked at most of the threads and I feel like Ive tried everything...is there anything else I can do?
Thanks :*(
choobacca80 said:
I dont know why but I did the Stock 4.3 update via Odin. I was rooted and unlocked 4.1.2
Now I've been stuck on the samsung logo since last night (not the bootloop, just frozen)
I've tried to install older stock roms and they all succeed thru Odin. Ive tried with and without pit files. Ive looked at most of the threads and I feel like Ive tried everything...is there anything else I can do?
Thanks :*(
Click to expand...
Click to collapse
Welcome to the ranks of regretful upgraders. We're a sorrowful bunch, it seems.
(I also upgraded, so eager to get the latest official update that I forgot about losing my unlocked bootloader. Sigh...)
Your best bet is Verizon's software. Assuming you have the new bootloader (go into Download mode, look for the KNOX flag - if there, you have it), this won't make things any worse.
If you don't have the latest bootloader, DON'T use Verizon's software, as it will apply the latest bootloader and lock you up tight.
With that caveat, here's Verizon's software: http://www.mediafire.com/?887h2dm4d20dk43
Steps are simple:
- install the software
- boot into Download mode (Power+Home+VolDown)
- start the Verizon software
- plug your phone into your computer (wait for driver install, detection)
- click on the 'repair' option in the left column
- click on your phone in the device section
- click on repair button in the bottom right (or next, or start - I don't recall)
- wait for the OTA to download and be installed
You can obtain root, though there is some risk depending on the method you choose (privacy issues with one program).
Good luck!
- Computerslayer
sweet, ill try this as soon as i get home!
quick question about knox...mine says "knox warranty void: 0", im assuming i do have knox then?
thanks again cmputerslayer
choobacca80 said:
sweet, ill try this as soon as i get home!
quick question about knox...mine says "knox warranty void: 0", im assuming i do have knox then?
thanks again cmputerslayer
Click to expand...
Click to collapse
That is, indeed, what that means.
Yup, you've got KNOX and the new bootloader. My condolences.
Don't try to flash other bootloader or ROMs - you'll trip the counter and get a softbrick ('Unauthorized Software' message, phone won't boot).
On the flip side, you can still get your phone back to working condition. Verizon Software to the rescue.
(Glad to help, by the way. Nice to be able to offer help!)
computerslayer said:
Yup, you've got KNOX and the new bootloader. My condolences.
Don't try to flash other bootloader or ROMs - you'll trip the counter and get a softbrick ('Unauthorized Software' message, phone won't boot).
On the flip side, you can still get your phone back to working condition. Verizon Software to the rescue.
(Glad to help, by the way. Nice to be able to offer help!)
Click to expand...
Click to collapse
dang i feel so helpless...
so i installed the verizon app but the app wont launch. its there in the tab next to the clock but nothing happens when i plug my phone in while download mode, argh!!
I had that happen too.
The way around it is to launch the application from the Start Menu or Desktop a second time. Then it will actually come up, instead of just having an icon in the notification center.
computerslayer said:
I had that happen too.
The way around it is to launch the application from the Start Menu or Desktop a second time. Then it will actually come up, instead of just having an icon in the notification center.
Click to expand...
Click to collapse
still no luck here, does it matter that im on 64bit? ill try some other computers i guess
Hmm. What comes up when you right-click on the taskbar icon next to the clock?
I have a 64-bit system as well - no issues to report. I don't think that's your problem.
computerslayer said:
Hmm. What comes up when you right-click on the taskbar icon next to the clock?
I have a 64-bit system as well - no issues to report. I don't think that's your problem.
Click to expand...
Click to collapse
dang noob status haha, have to wait five minutes...
check for new device software
launch assistant
options>
close
nothing happens when i click launch
Have you rebooted your computer since you installed the software?
computerslayer said:
Have you rebooted your computer since you installed the software?
Click to expand...
Click to collapse
i did, and i just did again
still no action
choobacca80 said:
i did, and i just did again
still no action
Click to expand...
Click to collapse
Hmm.
So I just installed the software on my 64-bit system here. I didn't reboot and when I right-clicked on the taskbar icon and selected 'Launch Assistant', it did right away. When I closed that window and tried to launch from the Start Menu icon, it also opened the application.
I'm wondering if its a goofy install. Care to uninstall and try again?
In the meantime, what version of Windows are you running? If Vista or higher, there could be an administrator access prompt that was denied, which might keep the application from launching.
powers airtsom
just tried another usb port also...nothing
computerslayer said:
Hmm.
So I just installed the software on my 64-bit system here. I didn't reboot and when I right-clicked on the taskbar icon and selected 'Launch Assistant', it did right away. When I closed that window and tried to launch from the Start Menu icon, it also opened the application.
I'm wondering if its a goofy install. Care to uninstall and try again?
In the meantime, what version of Windows are you running? If Vista or higher, there could be an administrator access prompt that was denied, which might keep the application from launching.
Click to expand...
Click to collapse
I apologize, but I've got to go to work for a couple hours. Hopefully uninstalling & re-installing will solve it. Post the results here! Plenty of good folks here at XDA to help
Try disabling your Anti Virus.
TonikJDK said:
Try disabling your Anti Virus.
Click to expand...
Click to collapse
so now im on another computer (windows 7 32bit), installed verizon software, still wont launch...hrmmmmmmm!
restarted...nothing
disabled anti virus...nothing
ok soo...
for sh*ts and giggles, i decided to run odin again and install stock 4.3. as usual it passed.
however i got passed the samsung logo this time and currently on verizon logo
just waiting now, hopefully its gets passed this!!
thank you tonikjdk and computerslayer for all your help!!!
for some reason when i did odin again, it passed as usual but got passed the samsung logo. got stuck on verion logo but at least i was able to get into stock recovery and wipe everything. now im passed verizon logo and starting to use my phone again, WHOO HOO!!!!
i guess now im waiting for the unlock of the bootloader. unless there i a way to downgrade (which i dont think there is)
again, thank you!!
<happy camper
I am having the same problem what firmware file did you use?
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.
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.