I just bought a Nexus 5 recently but it's flash memory go corrupt so I request a RMA and got a new one already. However, as the flash memory is corrupted, I can not restore the device to it's original state. I have not flashed a custom rom, but I have unlocked the boot loader, flash custom recovery, root it and flash a new boot animation. What would be the worst thing to happen?
nerodarknight said:
I just bought a Nexus 5 recently but it's flash memory go corrupt so I request a RMA and got a new one already. However, as the flash memory is corrupted, I can not restore the device to it's original state. I have not flashed a custom rom, but I have unlocked the boot loader, flash custom recovery, root it and flash a new boot animation. What would be the worst thing to happen?
Click to expand...
Click to collapse
Unless they can prove that you broke the flash memory by unlocking the bootloader, it'll be fine
rootSU said:
Unless they can prove that you broke the flash memory by unlocking the bootloader, it'll be fine
Click to expand...
Click to collapse
Thank u, it has been troubling me ever since
So, you bought a new nexus 5 before sending the other to RMA and, you want to "clean" the old before sending it ?
Well, can you boot it in fastboot ? If so, try flashtool and flash factory images ?
Charlus97 said:
So, you bought a new nexus 5 before sending the other to RMA and, you want to "clean" the old before sending it ?
Well, can you boot it in fastboot ? If so, try flashtool and flash factory images ?
Click to expand...
Click to collapse
No they sent me a new one alreadt, and now I have to return the broken one to them. About your suggestion, I did try but because the flash memory is corrupted, u can't write or read anything from it, including the OS
Wow. Google sent you a new phone before you've sent them your old ? Never seen that before
But like rootSU said, unless they're able to prove that it's your fault, there's no problem.
But, if you're able to boot into recovery/fastboot, you should be able to restore the orignal recovery & relock the bootloader, no ?
Charlus97 said:
Wow. Google sent you a new phone before you've sent them your old ? Never seen that before
But like rootSU said, unless they're able to prove that it's your fault, there's no problem.
But, if you're able to boot into recovery/fastboot, you should be able to restore the orignal recovery & relock the bootloader, no ?
Click to expand...
Click to collapse
This is how Google does RMA's they send you a new device and put a hold on your credit card equivalent to the price of the device. The hold is removed upon them receiving your old device.
Oh, ok. I used to see RMA like Asus : We pick your device, you wait 3 weeks and, if you're lucky, we will sent it back to you for free.
Just had a doubt about the RMA?
I purchased the device from India and the RMA process is like they pick up the device inspect it and send the replacement.
They collected mine yesterday.
They did mention that the device will be inspected by a technical team,now when i requested them for a replacement over telephone they asked me to send them pictures of the phone and then after reviewing them they notified me that they could now initiate a replacement,so what do they inspect for exactly?
and will they be sending me a new device?
well, I relock it but as soon as I turn it off, it got unlock again, I don't know why
Sonone said:
Just had a doubt about the RMA?
I purchased the device from India and the RMA process is like they pick up the device inspect it and send the replacement.
They collected mine yesterday.
They did mention that the device will be inspected by a technical team,now when i requested them for a replacement over telephone they asked me to send them pictures of the phone and then after reviewing them they notified me that they could now initiate a replacement,so what do they inspect for exactly?
and will they be sending me a new device?
Click to expand...
Click to collapse
They're checking for anything that could would void the warranty, such as user damage or a colourized water damage indicator.
LG RMA works differently from Google RMA. It's the traditional wait a few weeks until your phone is fixed, versus cross shipping of the device so you're never without a phone.
Related
http://www.fotosik.pl/pokaz_obrazek/pelny/7ebe08a2b2e135ea.html
http://forum.android.com.pl/attachment.php?attachmentid=95985&d=1413954853
http://forum.android.com.pl/attachment.php?attachmentid=95987&d=1413958300
http://www.fotosik.pl/pokaz_obrazek/pelny/d08020e375678c25.html
please help. Do RMA repair motherboard? is a way to repair this phone? can lock the bootloader and clean templar flag through fastboot??
Link 2 and 3 don't work.
Please write full description of problem here. Do not link to external sources as we probably wont read them
I see from link 1 you're using Wugfresh to flash stock. Most of us discourage use of toolkits, particularly when flashign stock is so easy.
Please click the link in my signature and read 2 threads. The adb and fastboot thread and the return to stock thread.
If you get the same error doing things properly, your NAND is fried and needs to be sent for repair. That is usually what "write failure" means. However since you are using toolkit, I cannot say that the error is genuine or not... So please use fastboot to flash stock
http://www.fotosik.pl/pokaz_obrazek/pelny/6ffdde1cca5a3865.html
up
tuningsea said:
http://www.fotosik.pl/pokaz_obrazek/pelny/6ffdde1cca5a3865.html
up
Click to expand...
Click to collapse
Unfortunately, it looks like the emmc is toast. You'll need to send it in for repairs. Contact Google if you've bought from the playstore. Bought from a retailer? Contact LG.
Good Luck!
I bought the LG. If I have unlocked bootloader + root means that for the repairs I have to pay?
Did you flash something recently? Because EMMC failure can be if you flash something not for your device (e.g kernel,rom and etc) or did got wet or fallen down? Or it's just happened out of sudden?
It happened suddenly, even I do not know how. I used a flashlight for 30 minutes the phone is restarted and died. I can enter fastboot mode only
tuningsea said:
I bought the LG. If I have unlocked bootloader + root means that for the repairs I have to pay?
Click to expand...
Click to collapse
If your warranty falls under LG, you might need to pay up since the bootloader is unlocked. Try to lock the bootloader and reset the tamper flag if you can.
Follow the last part of this tutorial:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
"fastboot boot path / to / TWRP.img" and stands on the logo teamwin. nothing can be done
http://www.fotosik.pl/pokaz_obrazek/pelny/ac67c81c2b162108.html
Motherboard die? whether it is for sure the motherboard?
tuningsea said:
http://www.fotosik.pl/pokaz_obrazek/pelny/ac67c81c2b162108.html
Motherboard die? whether it is for sure the motherboard?
Click to expand...
Click to collapse
You cannot write the bootloader, which means teh device (NAND Chip) that you are writing to is likely failed. This is in turn attached to the motherboard, so yes - probably needs a new Motherboard. Probably.
GOD
tuningsea said:
It happened suddenly, even I do not know how. I used a flashlight for 30 minutes the phone is restarted and died. I can enter fastboot mode only
Click to expand...
Click to collapse
How hot was the phone when it happened? I'm wondering if it has anything to do with the phones overheating (for some reason, like too high thermal throttling - remember the Xbox RROD)?
http://forum.xda-developers.com/google-nexus-5/help/stuck-google-boot-screen-fix-flashing-t2910842
Look at my thread
AndreIrawan97 said:
http://forum.xda-developers.com/google-nexus-5/help/stuck-google-boot-screen-fix-flashing-t2910842
Look at my thread
Click to expand...
Click to collapse
I do not think you have read THIS thread.
Hi all, first post to the forums so forgive me if I'm forgetting some sort of forum etiquette.
My brother's Nexus 5 stopped working a while ago, it'd just go straight to the Google screen on start up and sit there indefinitely. Recovery mode? Non-existent. I could get into the bootloader easy as, but selecting recovery mode just resulted in a black screen that would not accept any commands. So since I've reflashed my own Nexus 5 with various flavours of Android before I decided to just reflash his too, as I figured there's no reason that shouldn't work.
500 attempts later and uh, yeah, I don't think it's working.
I've tried installing the official versions of 4.3, 4.4, and 5.0, but Fastboot results in "failure to write" errors. I even tried sideloading with TWRP and Clockwork, but both of those give me error messages saying failure to mount /cache or /recovery or whatever.
I've spent an entire day (that should have been spent working on certain assignments :s) trying to fix this and looking around forums for a solution yet can't seem to find anything.
If anyone has any idea on how to fix this it would be greatly appreciated, I'm not too sure Google would honor the warranty on this anymore...
D0UBLEJUMP said:
Hi all, first post to the forums so forgive me if I'm forgetting some sort of forum etiquette.
My brother's Nexus 5 stopped working a while ago, it'd just go straight to the Google screen on start up and sit there indefinitely. Recovery mode? Non-existent. I could get into the bootloader easy as, but selecting recovery mode just resulted in a black screen that would not accept any commands. So since I've reflashed my own Nexus 5 with various flavours of Android before I decided to just reflash his too, as I figured there's no reason that shouldn't work.
500 attempts later and uh, yeah, I don't think it's working.
I've tried installing the official versions of 4.3, 4.4, and 5.0, but Fastboot results in "failure to write" errors. I even tried sideloading with TWRP and Clockwork, but both of those give me error messages saying failure to mount /cache or /recovery or whatever.
I've spent an entire day (that should have been spent working on certain assignments :s) trying to fix this and looking around forums for a solution yet can't seem to find anything.
If anyone has any idea on how to fix this it would be greatly appreciated, I'm not too sure Google would honor the warranty on this anymore...
Click to expand...
Click to collapse
Is your bootloader unlocked?
Are you getting the images from here, and following all the instructions: https://developers.google.com/android/nexus/images
krs360 said:
Is your bootloader unlocked?
Are you getting the images from here, and following all the instructions
Click to expand...
Click to collapse
Yes, yes and yes.
Like I said, everything went fine with reflashing my own Nexus 5, but my brother's one is just being so, so, so uncooperative.
D0UBLEJUMP said:
Yes, yes and yes.
Like I said, everything went fine with reflashing my own Nexus 5, but my brother's one is just being so, so, so uncooperative.
Click to expand...
Click to collapse
Try locking the bootloader in fastoot. Reboot to bootloader. If the bootloader still says unlocked you have a bad emmc chip.
theesotericone said:
Try locking the bootloader in fastoot. Reboot to bootloader. If the bootloader still says unlocked you have a bad emmc chip.
Click to expand...
Click to collapse
Bootloader always relocks when the phone restarts :/
It's a hardware error, a bad emmc chip. Your only choice is to exchange it under the warranty.
BirchBarlow said:
It's a hardware error, a bad emmc chip. Your only choice is to exchange it under the warranty.
Click to expand...
Click to collapse
Do you know if Google will still exchange it? It's within the warranty period, but I have been reflashing it and unlocking the bootloader which I doubt they're too excited about. Or is this a sort of special case since it's a hardware error?
D0UBLEJUMP said:
Do you know if Google will still exchange it? It's within the warranty period, but I have been reflashing it and unlocking the bootloader which I doubt they're too excited about. Or is this a sort of special case since it's a hardware error?
Click to expand...
Click to collapse
if your emmc is corrupt i don't think they will be able to find out you have been messing with your device and if your bootloader is locked that should do fine. Only thing that i'm not able to confirm is about the tamper flag
nexus.freak said:
if your emmc is corrupt i don't think they will be able to find out you have been messing with your device and if your bootloader is locked that should do fine. Only thing that i'm not able to confirm is about the tamper flag
Click to expand...
Click to collapse
I believe you can reset the tamper flag with a bit of luck by booting twrp from fastboot ( fastboot boot twrp.img ) then sideload and flash the tamper resetter.
That being said , anyone know what's the incidence of bad emmc chips on our devices ? And/or if there's a trigger to them ?
Niflheimer said:
I believe you can reset the tamper flag with a bit of luck by booting twrp from fastboot ( fastboot boot twrp.img ) then sideload and flash the tamper resetter.
That being said , anyone know what's the incidence of bad emmc chips on our devices ? And/or if there's a trigger to them ?
Click to expand...
Click to collapse
Woohoo! Flag reset!
Judging by what I found when I was looking around it doesn't seem like bad emmc is too common, couldn't find many suffering the same issues as me.
As for triggers, my brother's Nexus worked completely fine just like mine, then powered off, powered on, and broken. So...I guess the message of the story is to never turn them off (or try reflash) and they'll be fine?
If you bought phone of play store you can send it to google, there was a tread here some time ago and it said that google accept to replace phones with temper flag and unlocked bootloader.
Good luck
Hey Nexus 5 users, I have a problem with my N5, and the title pretty much sums it all up. I was running stock 5.02, and my WiFi was stuck on "Turning On WiFi" and my Bluetooth would attempt to turn on, but just revert to off after about five seconds. I rooted and flashed TWRP and CM 12, but the problem still remains. Anyone had problems with this? Any solutions apart from sending my phone back to Google, and if I have to, do they still accept N5's?
Clean flash factory images. If it still happens then it's likely a hardware issue.
Google accepts RMA if the device is still in it's warranty period. If it is not, then you will have to send the device to LG and pay for a repair.
Elluel said:
Clean flash factory images. If it still happens then it's likely a hardware issue.
Google accepts RMA if the device is still in it's warranty period. If it is not, then you will have to send the device to LG and pay for a repair.
Click to expand...
Click to collapse
I'll try sideloading some factory images, and I'm not sure as to whether I can RMA or not because I bought my N5 around this time last year. I should really RMA as I would like a new device anyway as there is a tiny little chip out of one of the corners of my device, and it's worth a shot I guess. Do you just call Google or go to a website or something?
EDIT: Should I sideload, or just flash with TWRP?
TrinityTechTutorials said:
I'll try sideloading some factory images, and I'm not sure as to whether I can RMA or not because I bought my N5 around this time last year. I should really RMA as I would like a new device anyway as there is a tiny little chip out of one of the corners of my device, and it's worth a shot I guess. Do you just call Google or go to a website or something?
Click to expand...
Click to collapse
Call Google. You will need your proof of purchase.
Elluel said:
Call Google. You will need your proof of purchase.
Click to expand...
Click to collapse
Ok thanks. I'm going to try flashing XtraSmooth now first. If that fails, the RMA is happening :good:
TrinityTechTutorials said:
Ok thanks. I'm going to try flashing XtraSmooth now first. If that fails, the RMA is happening :good:
Click to expand...
Click to collapse
You should be clean flashing factory images if you have an issue, not another custom ROM.
Elluel said:
You should be clean flashing factory images if you have an issue, not another custom ROM.
Click to expand...
Click to collapse
Alright, I'll flash a stock 5.1 image, it may fix this as we all know that 5.0x was a buggy mess
As a friendly reminder to those unfamiliar with unlocking/re-locking their bootloaders;
Unless your on 100% stock, and planning on reselling your phone, don't re-lock the bootloader.
For some reason re-locking the bootloader while you have a custom ROM installed will cause the phone not to boot (in a way, soft bricking it.)
And, leave "OEM unlocking" in the "Developer Options" CHECKED, once that is unchecked you cannot unlock the phone once a soft brick happens.
The official advice from Essential about re-locking your phone is ONLY for the official firmware. Pretend they never said that on their site, it has caused more trouble then necessary. It's even dangerous to re-lock while running the Oreo beta.
Concerning un-bricking the device, at the moment there is no known way.
And it will be this way until someone figures out a way to exploit the bootloader or reverse engineer it.
So please don't flood this thread with asking for help to un-brick your device, I nor anyone else can help you on that at this given time, all I'm doing is trying to is prevent that happening.
So, safe unlocking! And happy holidays!
EDITS:
1) According to some reports, when you lock your bootloader it will also automatically untoggle the "OEM Unlocking" option.
2) It appears when re-locking the phone on a non-stock ROM some partitions are becoming corrupt, and resulting in the "red boot warning" screen. Under most circumstances you can fix that screen, but not while the bootloader is locked (since you need the fastboot flash command.)
3) When the partitions become corrupt you cannot boot into any mode, including the stock recovery. This is why Essential's suggestions are pointless at this stage of the brick.
Should be pinned and in the OP of every mod thread
Sent from my PH-1 using XDA Labs
avd said:
Should be pinned and in the OP of every mod thread
Click to expand...
Click to collapse
totally agree, i made this "trick" with one of my first android phone and it never happen me again. But new user who would flash Los or other rom should be aware of this issue, specially when jtag is not an option. As far we'll make some powerfull 500$ brick :crying:. it's our duty to make people aware of this. @invisiblek you guy made an incredible work and so fast but like he said i think you should warn people of the risk in the OP
avd said:
Should be pinned and in the OP of every mod thread
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
I wouldn't even know how to go about to ask to pin this.
But besides this I'm also thinking about making a thread for new users regarding common issues when installing roms at our current stage.
I'm firejackal on discord, I'm just trying to reduce the amount of people asking the same questions on there and to prevent bricked units.
Ellises said:
I wouldn't even know how to go about to ask to pin this.
But besides this I'm also thinking about making a thread for new users regarding common issues when installing roms at our current stage.
I'm firejackal on discord, I'm just trying to reduce the amount of people asking the same questions on there and to prevent bricked units.
Click to expand...
Click to collapse
It's very easy to ask for a thread to get stuck to the top.
Just use the report post button, and ask, whether or not becomes a sticky is up to the Mods.
How to Report a Post.
Sent from my XT1254 using XDA Labs
Wish I saw this earlier, my phone is already bricked few weeks ago after re-lock the boot loader. When I ask Essential support for help, they said this in the email:
"Hi Eric,
I can appreciate your concern if the device is not able to be used.
I am sorry though, we are not able to provide support for ADB or issues that you will run into with sideloading builds. We have no remote tools that will recover the device.
Although I haven't run into that same error, you might still be able to re-flash the Oreo/production build again using ADB.
I would recommend following the Oreo Beta sideload instructions available on Essential.com/developer that will walk you through the process of getting the device recognized and communicating with ADB. There are also instructions for re-flashing the current build available here. If you are still running into issues, I would recommend visiting online forums like XDA for assistance from other developers for that issue that you are noticing.
Thank you for your understanding.
Sincerely,
Erich
Essential Customer Experience Team"
That sounds like a generic reply since it's not mentioning anything about the brick.
But I have a question regarding this; when you use the locked bootloader to boot into the stock recovery to try to sideload an official signed image, what does it do? Does it give an error, or is not able to connect to the computer?
ericzhf said:
Wish I saw this earlier, my phone is already bricked few weeks ago after re-lock the boot loader. When I ask Essential support for help, they said this in the email:
"Hi Eric,
I can appreciate your concern if the device is not able to be used.
I am sorry though, we are not able to provide support for ADB or issues that you will run into with sideloading builds. We have no remote tools that will recover the device.
Although I haven't run into that same error, you might still be able to re-flash the Oreo/production build again using ADB.
I would recommend following the Oreo Beta sideload instructions available on Essential.com/developer that will walk you through the process of getting the device recognized and communicating with ADB. There are also instructions for re-flashing the current build available here. If you are still running into issues, I would recommend visiting online forums like XDA for assistance from other developers for that issue that you are noticing.
Thank you for your understanding.
Sincerely,
Erich
Essential Customer Experience Team"
Click to expand...
Click to collapse
Ellises said:
That sounds like a generic reply since it's not mentioning anything about the brick.
But I have a question regarding this; when you use the locked bootloader to boot into the stock recovery to try to sideload an official signed image, what does it do? Does it give an error, or is not able to connect to the computer?
Click to expand...
Click to collapse
I'm not able to boot in to stock recovery any more, it gives this error when I try recovery "Your device is corrupted. It can't be trusted and will not boot". I think that was because I rooted and installed TWRY before.
Now with locked bootloader, I can't get in to recovery and I can't flash TWRY either. I can't unlock bootloader too because I'm not able to boot so not able to enable USB-DEBUG and OEM-UNLOCK.
I tried pretty much everything and no luck at this point, I don't know what else I can do.
ericzhf said:
I'm not able to boot in to stock recovery any more, it gives this error when I try recovery "Your device is corrupted. It can't be trusted and will not boot". I think that was because I rooted and installed TWRY before.
Now with locked bootloader, I can't get in to recovery and I can't flash TWRY either. I can't unlock bootloader too because I'm not able to boot so not able to enable USB-DEBUG and OEM-UNLOCK.
I tried pretty much everything and no luck at this point, I don't know what else I can do.
Click to expand...
Click to collapse
You have bricked your phone.
Locking the bootloader with non-factory ROM causes secure boot to fail.
An unlocked bootloader doesn't care about secure boot.
If the ROM images is not signed there isn't a problem unless you have a locked bootloader.
The one thing I don't understand is why relook the BL anyway?
You have TWRP installed so you already can't take an OTA.
tech_head said:
You have bricked your phone.
Locking the bootloader with non-factory ROM causes secure boot to fail.
An unlocked bootloader doesn't care about secure boot.
If the ROM images is not signed there isn't a problem unless you have a locked bootloader.
The one thing I don't understand is why relook the BL anyway?
You have TWRP installed so you already can't take an OTA.
Click to expand...
Click to collapse
I bought the phone for about 2 weeks, then there was a promotion that buy phone give camera 360 for free with Sprint, so I was thinking about return this and buy again to get the free stuff. To return it I have to get it back to stock, so I factory reset my phone and try to re-lock boot loader without thinking. Turns out I didn't get the free camera and bricked my phone too, perfect example of "NOTHING IS FREE":good:
ericzhf said:
I bought the phone for about 2 weeks, then there was a promotion that buy phone give camera 360 for free with Sprint, so I was thinking about return this and buy again to get the free stuff. To return it I have to get it back to stock, so I factory reset my phone and try to re-lock boot loader without thinking. Turns out I didn't get the free camera and bricked my phone too, perfect example of "NOTHING IS FREE":good:
Click to expand...
Click to collapse
FDR is not "back to stock".
You must to a full flash to get back to stock.
I updated the top post with some additional information.
Also, if anyone is to contact Essential I wouldn't recommend mentioning that you tried to install custom ROMs, that's just walking into a mess like if you mentioned that to any other phone company.
I would instead say that you tried to install [their] oreo beta, went to re-lock the phone and your presented with a corruption message and unable to do anything including their instructions. Because installing their oreo beta does not void your warranty.
Ellises said:
I updated the top post with some additional information.
Also, if anyone is to contact Essential I wouldn't recommend mentioning that you tried to install custom ROMs, that's just walking into a mess like if you mentioned that to any other phone company.
I would instead say that you tried to install [their] oreo beta, went to re-lock the phone and your presented with a corruption message and unable to do anything including their instructions. Because installing their oreo beta does not void your warranty.
Click to expand...
Click to collapse
Well, to install their Oreo beta builds you don't need to unlock the bootloader.
It's an adb side load through stock recovery
I could also mention on their stock build page it wants you to unlock the bootloader to manually update through the bootloader. But on the oreo beta page it mentions nothing about having to be unlocked, or locked to do it via the stock recovery. So the average user could presume they need to be unlocked.
NaterTots said:
Well, to install their Oreo beta builds you don't need to unlock the bootloader.
It's an adb side load through stock recovery
Click to expand...
Click to collapse
Am I'm safe to re-lock if I'm on stock rooted 7.1.1 NMK24B? I have a dead pixel and I need to send it back.
WiddleyScudds said:
Am I'm safe to re-lock if I'm on stock rooted 7.1.1 NMK24B? I have a dead pixel and I need to send it back.
Click to expand...
Click to collapse
No.
WiddleyScudds said:
Am I'm safe to re-lock if I'm on stock rooted 7.1.1 NMK24B? I have a dead pixel and I need to send it back.
Click to expand...
Click to collapse
If you are rooted, you are not stock.
The boot image is modified.
Locking will brick the phone.
You must be completely stock!! No root. Nothing.
Obamaloominaty said:
No.
Click to expand...
Click to collapse
tech_head said:
If you are rooted, you are not stock.
The boot image is modified.
Locking will brick the phone.
You must be completely stock!! No root. Nothing.
Click to expand...
Click to collapse
Thanks for clearing that up. If I have any more questions before returning to stock, I will ask here first.
WiddleyScudds said:
Thanks for clearing that up. If I have any more questions before returning to stock, I will ask here first.
Click to expand...
Click to collapse
Was not trying to be harsh but it can't be stressed enough that you must be completely stock to lock the boot loader and not have issues.
I wouldn't lock the BL on a side loaded beta.
Only lock if you have done a complete flash of stock, released firmware, immediately after the install.
I might be sounding like an alarmist but I don't want anyone to brick their phone.
tech_head said:
Was not trying to be harsh but it can't be stressed enough that you must be completely stock to lock the boot loader and not have issues.
I wouldn't lock the BL on a side loaded beta.
Only lock if you have done a complete flash of stock, released firmware, immediately after the install.
I might be sounding like an alarmist but I don't want anyone to brick their phone.
Click to expand...
Click to collapse
I just got an ota notification for OPM1. 180104.092. think I'll be safe I I take it, then factory reset and then lock? Because I can't seem to locate stock NMK24B to flash. Maybe I'm not looking hard enough .
Okay, so my phone is bricked and there's no recovering it. RMA is already ordered and on it's way. Essentially I'm in the same situation as this poor soul (and many others, from the results of searching for this error in the forums).
What I want to know is if I did this or if this was something I couldn't have foreseen. The phone had an unlocked boot loader with the latest OS (Pie) & security updates (November). No custom ROM or kernel - stock everything, though I did have Magisk installed. Today I decided to re-lock my bootloader. While the device was in fastboot mode I issued the command "fastboot flashing lock" and followed the phone's on-screen directions. When it finished and tried to reboot, it would only go the fastboot mode with the message "ERROR: Slot Unbootable: Load Error".
I recognize that locking the bootloader may have been the last straw for some present flaw - like a weak engine finally giving out after long service. Is that the case here or is there some step I missed that would have prevented this from happening? I ask because I don't want to repeat a mistake in the future.
u found any way to unbrick your phone?
yuva_cool said:
u found any way to unbrick your phone?
Click to expand...
Click to collapse
Nope. The RMA was approved and I'm using a new (refurbished) device.
U had an unlocked bootloader and yet your RMA was approved? @computerslayer
yuva_cool said:
U had an unlocked bootloader and yet your RMA was approved? @computerslayer
Click to expand...
Click to collapse
The error showed up when I relocked the bootloader, so it was locked when I submitted the RMA. They approved it (and didn't demand a payment when they received the RMA'd phone), so I suppose they accepted that it was a warrantied issue.
computerslayer said:
The error showed up when I relocked the bootloader, so it was locked when I submitted the RMA. They approved it (and didn't demand a payment when they received the RMA'd phone), so I suppose they accepted that it was a warrantied issue.
Click to expand...
Click to collapse
Did you flash the stock boot image before you relocked? If not, Magisk was still installed and that's where you went wrong. You need to be completely stock when you relock the phone.
If you ever relock the phone you have now, to be on the safe side, I'd flash the factory image and leave the -w in the flashall batch file. Your phone will get wiped when you relock it anyway so you won't be out anything if you do so.
robocuff said:
Did you flash the stock boot image before you relocked? If not, Magisk was still installed and that's where you went wrong. You need to be completely stock when you relock the phone.
If you ever relock the phone you have now, to be on the safe side, I'd flash the factory image and leave the -w in the flashall batch file. Your phone will get wiped when you relock it anyway so you won't be out anything if you do so.
Click to expand...
Click to collapse
I am abashed to have to report that I did not flash the stock boot image. I wondered if Magisk was the cause, but assumed that the wipe caused by relocking would take care of that too.
computerslayer said:
I am abashed to have to report that I did not flash the stock boot image. I wondered if Magisk was the cause, but assumed that the wipe caused by relocking would take care of that too.
Click to expand...
Click to collapse
If that's the case, it's a certainty that that's the cause of your problem. You have to be completely stock when you relock it. Flashing the factory boot image should take care of that if all you have done is installed Magisk. That said, I'd still flash the factory image and let it do the wipe, just to be sure.
computerslayer said:
Okay, so my phone is bricked and there's no recovering it. RMA is already ordered and on it's way. Essentially I'm in the same situation as this poor soul (and many others, from the results of searching for this error in the forums).
What I want to know is if I did this or if this was something I couldn't have foreseen. The phone had an unlocked boot loader with the latest OS (Pie) & security updates (November). No custom ROM or kernel - stock everything, though I did have Magisk installed. Today I decided to re-lock my bootloader. While the device was in fastboot mode I issued the command "fastboot flashing lock" and followed the phone's on-screen directions. When it finished and tried to reboot, it would only go the fastboot mode with the message "ERROR: Slot Unbootable: Load Error".
I recognize that locking the bootloader may have been the last straw for some present flaw - like a weak engine finally giving out after long service. Is that the case here or is there some step I missed that would have prevented this from happening? I ask because I don't want to repeat a mistake in the future.
Click to expand...
Click to collapse
I have this issue and now my pixel 2 cant boot. It stuck. Cant enter fastboot. This is my last experience with pixel series devices. Its expensive phone, but its too sensitive to brick. I dont know why, an update or a flashing stock rom can make your phone totally unuseable. I just cant accept it
I had exactly the same issue. just keep holding the power button with or without the vol- for a good 30~ seconds or so (it will restart several times) but keep holding.
and make sure you are connected to the PC until you hear the ding that the phone got recognized, then the phone will accept fastboot commands.
This worked for me before I was going to throw the phone in the garbage!