does brinking only happen when you install a unsupported rom. all i wanna do is unlock the boot loader and root my gnex but dont want it to brink as im doing it i dont wanna install custom roms i just wanna be able to use apps that need root . i tryed the root with out unlock method it dont work for me. thanks
If you're not doing anything there isn't really any way you could possibly mess up your phone. Just read the directions.
No, you won't brick your phone unlocking and rooting it. Just follow directions.
android.4.0 said:
does brinking only happen when you install a unsupported rom. all i wanna do is unlock the boot loader and root my gnex but dont want it to brink as im doing it i dont wanna install custom roms i just wanna be able to use apps that need root . i tryed the root with out unlock method it dont work for me. thanks
Click to expand...
Click to collapse
Read, read, read and fully understand what you are about to do. Also study up on how to fully restore your device before proceeding. It is tempting, but the more you read, the more confident you will feel when you run into an issue. Trust me, you will have issues. We all had them when we started messing with our devices.
http://forum.xda-developers.com/showthread.php?t=1892807
You can flash whatever you want that isn't a bootloader from another phone (or corrupt -- check those MD5s) you will never brick, even if it is a ROM for another phone.
Sent from my Galaxy Nexus using Tapatalk 2
Type fastboot erase boot ........ you'll brick it quick lol.
Otherwise like someone said above if you flashed the wrong boot loader, although I think it checks it I'm not sure, or maybe a corrupted one then yeah your baked. But otherwise you pretty much can't break it
Sent from my Nexus 7 using Tapatalk HD
altimax98 said:
Type fastboot erase boot ........ you'll brick it quick lol.
Otherwise like someone said above if you flashed the wrong boot loader, although I think it checks it I'm not sure, or maybe a corrupted one then yeah your baked. But otherwise you pretty much can't break it
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
'fastboot erase boot' erases kernel, not bootloader. Try erasing it. The device will boot up to fastboot mode, directly.
Sent from my i9250
bk201doesntexist said:
'fastboot erase boot' erases kernel, not bootloader. Try erasing it. The device will boot up to fastboot mode, directly.
Sent from my i9250
Click to expand...
Click to collapse
He is trying to say booloader, someone on he N7 forum pulled it off.
Beamed from my Grouper.
Mach3.2 said:
He is trying to say booloader, someone on he N7 forum pulled it off.
Beamed from my Grouper.
Click to expand...
Click to collapse
this is the maguro/toro/toroplus forums.
even so, even erasing bootloader, it should be possible to recover it through omapflash. i don't think erasing the bootloader can be called a brick. if you erased it, it means you can write it again. corrupting emmc would be what i call a brick.
and on grouper, it will probably will be possible to use nvflash, if it's not available right now.
bk201doesntexist said:
this is the maguro/toro/toroplus forums.
even so, even erasing bootloader, it should be possible to recover it through omapflash. i don't think erasing the bootloader can be called a brick. if you erased it, it means you can write it again. corrupting emmc would be what i call a brick.
and on grouper, it will probably will be possible to use nvflash, if it's not available right now.
Click to expand...
Click to collapse
Well, I guess no one sane is going to try fastboot erase bootloader.
Will the next nexus have a longer screen?
Mach3.2 said:
Well, I guess no one sane is going to try fastboot erase bootloader.
Will the next nexus have a longer screen?
Click to expand...
Click to collapse
Shhh, we do not speak that phrase!
My current ROM:http://forum.xda-developers.com/showthread.php?t=1892807
For the nexus it really really really hard to brick this phone and if you do it might not be a brick it might be more of a hardware fail then anything . Lol I have messed up some serious software upgrade and flashes and it never bricked
Sent from my Galaxy Nexus using xda premium
Related
Hi,
1. For a month ago i've learned how to root my galaxy s2, and since then i've flashed new ROM's and kernels almost every week, and thats because almost everyone told me that it was almost impossible to brick the phone.
In 2 days i will recive my new Galaxy Nexus, and i don't know if i will Root it or not, is it worth doing this to this phone?
thanks
People say it's almost impossible.. Just search the threads where people think they bricked their phones
It is EXTREMELY hard to brick the Galaxy Nexus.
And it is definitely worth rooting. There are some amazing ROMs and kernels available
Learning to root and use android from scratch, I bricked this fella at least six times, but mostly due to bad file transfers and user error.
Use a toolkit, wugfresh's makes it excessivlely easy.
Sent from my Galaxy Nexus using xda premium
I did not wipe data out before flashing, my phone could not start. I thought i bricked my phone but after went to recovery mode to wipe data, my phone worked fine.
As far as I know, the only time that you can brick this phone is when flashing bootloaders. For example, the lights go out during the 2 secs required to flash it. But the window of opportunity is so small you have to really be unlucky, and if you have UPS or do it on a laptop, that won't be a problem at all. The more probable scenario is flashing a corrupted image of the bootloader (that's what md5 checksums are for) or, god forbid, a bootloader for a completely different device (that's what intelligence is for). Besides, you shouldn't be flashing bootloaders all the time. Maybe once every time a new version of ICS comes out.
TwilightSparkle said:
I bricked this fella at least six times
Click to expand...
Click to collapse
So what you really mean, is that you didn't actually brick it once?
Lol - interesting thread...
I'll bet that I can brick one in a few minutes, so it can't be that hard... xD
I was under the impression that bricking can also occur by mismatching radios/kernels/roms, not just the wrong bootloader. Like using a 4.0.2 version of one with a 4.0.3 version of another, for instance. I want to upgrade from 4.0.2 to 0.3 or 0.4 but I'm not sure of the correct order of updating everything, since I've customized all of them. Unless I'm just mistaken altogether...
thirtynation said:
I was under the impression that bricking can also occur by mismatching radios/kernels/roms, not just the wrong bootloader. Like using a 4.0.2 version of one with a 4.0.3 version of another, for instance. I want to upgrade from 4.0.2 to 0.3 or 0.4 but I'm not sure of the correct order of updating everything, since I've customized all of them. Unless I'm just mistaken altogether...
Click to expand...
Click to collapse
No. As long as your volume button and power button are not broken, you can start into the bootloader and start over.
Bricking is a very final thing that one can not repeat on the same device. Once bricked, it's only good as a paperweight. If you can revive the device, then it was never bricked in the first place
Wrong radio will brick your device for certain. Kernel and ROM not so much...
danger-rat said:
Wrong radio will brick your device for certain. Kernel and ROM not so much...
Click to expand...
Click to collapse
I thought CWM just gives an error and doesn't complete the flash in that scenario, no..?
danger-rat said:
Wrong radio will brick your device for certain. Kernel and ROM not so much...
Click to expand...
Click to collapse
I thought I remembered reading that in some /r/android comments a few months ago. Thanks for confirming.
So since I'm on 4.0.2 running the leaked 4.0.3 radios, if I wanted to run 4.0.4 everything would you recommend just reverting back to pure stock 4.0.2 via this thread or similar method, and then going from there?
Vangelis13 said:
I thought CWM just gives an error and doesn't complete the flash in that scenario, no..?
Click to expand...
Click to collapse
Not confirmed with this phone, but typically the bootloader will do an md5 type check, but recovery doesn't. If you disable signature verification in recovery, then it's all in your hands...
j.go said:
[snip]
The more probable scenario is flashing a corrupted image of the bootloader (that's what md5 checksums are for) or, god forbid, a bootloader for a completely different device (that's what intelligence is for). Besides, you shouldn't be flashing bootloaders all the time. Maybe once every time a new version of ICS comes out.
Click to expand...
Click to collapse
Not sure if the bootloader flow is the same on the Galaxy Nexus (probably not), but on the Nexus One, the bootloader will not flash a bootloader that is not signed. Period. Unless of course there is no NAND lock (i.e., S-OFF for HTC devices).
Afaik,you have to screw up fast boot to truly brick the device. Not even messed up boot loaders will brick it. You can always go to fastboot and factory restore.
Sent from my Galaxy Nexus
psycho2097 said:
Afaik,you have to screw up fast boot to truly brick the device. Not even messed up boot loaders will brick it. You can always go to fastboot and factory restore.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Dare you to flashable radio from another phone...
danger-rat said:
Dare you to flashable radio from another phone...
Click to expand...
Click to collapse
LOL!!!!!
Sent from my Galaxy Nexus using Tapatalk
I Dare y'all to flash the 4.0.4 update on a GSM phone. ;P
Sent from my Galaxy Nexus using xda premium
I have a L700 and it's refusing to let me re-lock the bootloader. It shows that it locks, but if I restart fastboot it shows unlocked again. if I restart the phone, it shows that it's unlocked. i've tried to flash a new build using ODIN and Fastboot but it still is acting up. Also, if i flash CWM and restart the phone, TWPR shows up which is currently on the phone. It's like updates aren't actually working!!!
Any ideas?
(It won't let me update my bootloader/radio's or recovery which is why I want to relock it, I think that might solve something)
Thanks,
Why do you need to relock your bootloader?
It's pretty much pointless.
electro` said:
Why do you need to relock your bootloader?
It's pretty much pointless.
Click to expand...
Click to collapse
I believe it will fix my issue. I feel as if I can lock it then unlock it, i'll be able to flash what I need. Since it's pointless, can you explain why my bootloader and radio's won't update?
This is going to be really stupid but did you do the command prompt relock bootloader in fastboot?
This seems kind of unusual.
Did you reflash the bootloader or anything else?
If not, try that.
electro` said:
This is going to be really stupid but did you do the command prompt relock bootloader in fastboot?
This seems kind of unusual.
Did you reflash the bootloader or anything else?
If not, try that.
Click to expand...
Click to collapse
I did relock the bootloader as stated in the OP. It goes back to unlocked with a restart or bootloader restart which shouldn't happen. I know it seems unusual. I've flashed everything (system, recovery, radio, bootloader) to no avail.
This might be a really stupid question but you say you have a L700???
What's that? These are the Google Galaxy Nexus forums.
Sent from my Nexus
bk201doesntexist said:
This might be a really stupid question but you say you have a L700???
What's that? These are the Google Galaxy Nexus forums.
Sent from my Nexus
Click to expand...
Click to collapse
http://www.samsung.com/us/support/owners/product/SPH-L700ZKASPR
Sprint GNex
bk201doesntexist said:
This might be a really stupid question but you say you have a L700???
What's that? These are the Google Galaxy Nexus forums.
Sent from my Nexus
Click to expand...
Click to collapse
Way to be an anus and look like an idiot doing it. I've read other threads with the same issue, I think it's a hardware issue and I'm just out a phone.
Thanks anyway.
Sooppex said:
Way to be an anus and look like an idiot doing it. I've read other threads with the same issue, I think it's a hardware issue and I'm just out a phone.
Thanks anyway.
Click to expand...
Click to collapse
He was trying to help you.
No need to be a **** about it.
You could try the Nexus Root Toolkit by WugFresh. I think that has a bootloader relocking facility in it.
http://goo.im/devs/WugFresh/NexusRootToolkit
Edit: Whoops, sorry, didn't fully read the thread, my bad
My son wanted to root his brand new phone. i have rooted 8 phones from different phones before with success..... but this time i f***d up...
Accedently installed this on his phone.
http://wccftech.com/flash-and-root-nexus-5-on-android-6-0-1-mmb29k/
executed flash-all.bat and it flashed the bootloader.
For the wrong phone...
It should have been this one..
http://wccftech.com/flash-and-root-nexus-5x-android-6-0-1/
Missed the X......
Now the phone will not even boot any more at all....cant enter bootloader.......does not power up at all.!!!
Jesus...what have i done.......
It here any chance at all to fix this somehow?
Hello and thank you for using Q/A,
because you can't enter bootloader, you can't do anything. You can try to send the phone to Google. Say: It didn't boot after OTA Update.
Kind regards
Trafalgar Square
Yeah it's most likely a paperweight. Try sending it to Google. Flashing the wrong firmware destroys a phone as you probably already know
well
hopesrequiem said:
Yeah it's most likely a paperweight. Try sending it to Google. Flashing the wrong firmware destroys a phone as you probably already know
Click to expand...
Click to collapse
I am totally aware of that....
but somehow one must be able to flash the bootloader from scratch....
Normally via special software etc.
That´s what i was hoping for....
Only thing I know to use is a riff box to jtag it. Not sure if they have one for 5x.
crowhater said:
I am totally aware of that....
but somehow one must be able to flash the bootloader from scratch....
Normally via special software etc.
That´s what i was hoping for....
Click to expand...
Click to collapse
Your use of the period seems rather condescending. And no, you as the end user cannot fix that. You did one of the few things that is unrecoverable unless you manage to get the bootloader to accept adb commands somehow.
crowhater said:
I am totally aware of that....
but somehow one must be able to flash the bootloader from scratch....
Normally via special software etc.
That´s what i was hoping for....
Click to expand...
Click to collapse
Didn't you say the phone won't turn on? The above scenario is not possible.
Well
bobby janow said:
Didn't you say the phone won't turn on? The above scenario is not possible.
Click to expand...
Click to collapse
Well. the bootloader is flashed into the phone from the beginning aswell during manufacturing. I work with electronics and software and i know there is always a way to reflash the bootloader. All the electronics comes in the beginning with no software at all, one only needs the proper software/hardware. Most probably by jtag....or if they have some other special tool for snapdragon 808.
Stupid of me not to see that the version i flashed was not for nexus 5X...and only for nexus 5
sight...
Good luck. Will Google not rma it?
i mean its been 10 minutes, but still stuck on bootloop any ideas?
iKenta said:
i mean its been 10 minutes, but still stuck on bootloop any ideas?
Click to expand...
Click to collapse
Out of date ADB can cause this. I have seen it a few times reported by other people.
Try rebooting PC then reboot phone back to boot loader and use THESE adb and fastboot apps. I copied the from the latest SDK Manager
If that does not resolve then post back
iKenta said:
i mean its been 10 minutes, but still stuck on bootloop any ideas?
Click to expand...
Click to collapse
You should probably include a screenshot of everything you did in the command prompt... boot-to-root cannot be flashed with adb. This is done in fastboot.
Sent from my Pixel XL using Tapatalk
david.degraw54 said:
boot-to-root cannot be flashed with adb. This is done in fastboot.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Good point!
Scott said:
Good point!
Click to expand...
Click to collapse
Likewise! His adb and fastboot are probably out of date if he did in fact fastboot boot the correct images, but I'm not sure that the phone would even be detected in fastboot mode if the updated files/drivers aren't installed on his PC.
Sent from my Pixel XL using Tapatalk
david.degraw54 said:
Likewise! His adb and fastboot are probably out of date if he did in fact fastboot boot the correct images, but I'm not sure that the phone would even be detected in fastboot mode if the updated files/drivers aren't installed on his PC.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
It would be but the old ADB / Fastboot would not flash properly because of the new "Slots". I have seen a lot of people with this issue and generally the updated ADB and fastboot fixes it.
Hopefully OP will chime back in on what worked for him so I can make a mental note.
Scott said:
It would be but the old ADB / Fastboot would not flash properly because of the new "Slots". I have seen a lot of people with this issue and generally the updated ADB and fastboot fixes it.
Hopefully OP will chime back in on what worked for him so I can make a mental note.
Click to expand...
Click to collapse
Ahhh I see. Same, extra info always helps, I'd prefer to keep away from bricking my new phone. But besides that I wanna help this guy! Sad to see people are bricking their phones and stuff. Never hurts to read as much as you possibly can before getting into flashing.
Sent from my Pixel XL using Tapatalk
david.degraw54 said:
Ahhh I see. Same, extra info always helps, I'd prefer to keep away from bricking my new phone. But besides that I wanna help this guy! Sad to see people are bricking their phones and stuff. Never hurts to read as much as you possibly can before getting into flashing.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Agreed! But on the same note, in the OP's defense there is not a very clear Q/A thread that tells you what you need to do. Everything is scattered. However, that is not anyones fault. This device is new to "ALL" of us. The whole SLOT thing, etc. Its all new unless you had a Google Chromebook. So I cant much blame people with issues. The good thing... 99.99% of the issues posted can be fixed with some patients. :good:
i apologize ahah, yes i did fastboot boot-to-boot , and for some reason it caused this problem .. but i did a full image restore, and bootloader was unlocked still, i fastbooted ROOT-MARLIN-PIXELXL-SR3.ZIP , the SR3 one and it worked perfect, my pixel xl verizon is now rooted, and bootloader unlocked, i never messed with any nexus (google) phone before.
thank you all for help
one more question, everytime my phone restarts, an annoying screen shows saying "cant check device for corruption, please lock your bootloader" ... is it suppose to be there? or just ignore it?
iKenta said:
i apologize ahah, yes i did fastboot boot-to-boot , and for some reason it caused this problem .. but i did a full image restore, and bootloader was unlocked still, i fastbooted ROOT-MARLIN-PIXELXL-SR3.ZIP , the SR3 one and it worked perfect, my pixel xl verizon is now rooted, and bootloader unlocked, i never messed with any nexus (google) phone before.
thank you all for help
one more question, everytime my phone restarts, an annoying screen shows saying "cant check device for corruption, please lock your bootloader" ... is it suppose to be there? or just ignore it?
Click to expand...
Click to collapse
Just ignore it, it's due to the unlocked bootloader
Sent from my Pixel XL using Tapatalk
anyway guys, i wouldnt mess with SR2 .. i think it was caused the bootloop , SR3 im assuming more stable.. now about the TWRP , what do you guys suggest? or wait for stable one because cant find one at all .
iKenta said:
i apologize ahah, yes i did fastboot boot-to-boot , and for some reason it caused this problem .. but i did a full image restore, and bootloader was unlocked still, i fastbooted ROOT-MARLIN-PIXELXL-SR3.ZIP , the SR3 one and it worked perfect, my pixel xl verizon is now rooted, and bootloader unlocked, i never messed with any nexus (google) phone before.
thank you all for help
one more question, everytime my phone restarts, an annoying screen shows saying "cant check device for corruption, please lock your bootloader" ... is it suppose to be there? or just ignore it?
Click to expand...
Click to collapse
Nothing you can do about that at this time. I am sure someone will hack the aboot or hboot, which ever on an HTC device to remove it. For now wear it as a badge of pride :highfive:
iKenta said:
anyway guys, i wouldnt mess with SR2 .. i think it was caused the bootloop , SR3 im assuming more stable.. now about the TWRP , what do you guys suggest? or wait for stable one because cant find one at all .
Click to expand...
Click to collapse
Could have been. I would recommend you not install TWRP at this time. Its finicky but being worked on. I know for fact it will be great soon.
I hope @Chainfire updates his Flash Fire. Easier to use than TWRP!
I was on 8.1 with Flash Kernel installed using images...I wanted to get back to stock...so unchecked OEM Unlocking in Developer Options, went to bootloader and locked bootloader using fastoboot flashing lock..and now I am getting "Can't find valid operating system. The device will not start". I can't unlock the bootloader now as I unchecked OEM unlocking in Developer Options and can't flash factory images also as it says Flashing is not allowed in Lock State, Did I brick the device?
Update: I have returned my device to Google and they processed a replacement
i am just curious, how were planning on flashing a rom with locked bootloader?
ram4ufriends said:
I was on 8.1 with Flash Kernel installed using images...I wanted to get back to stock...so unchecked OEM Unlocking in Developer Options, went to bootloader and locked bootloader using fastoboot flashing lock..and now I am getting "Can't find valid operating system. The device will not start". I can't unlock the bootloader now as I unchecked OEM unlocking in Developer Options and can't flash factory images also as it says Flashing is not allowed in Lock State, Did I brick the device?
Click to expand...
Click to collapse
Yea, I think you may have turned it into a fancy paperweight. Been there, done that. You should have waited to uncheck OEM unlocking until after you locked the bootloader, which wiped your phone. About the only thing I can suggest is to try and run Deuces script to see if you can rescue your device. Best of luck to you.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
ram4ufriends said:
I was on 8.1 with Flash Kernel installed using images...I wanted to get back to stock...so unchecked OEM Unlocking in Developer Options, went to bootloader and locked bootloader using fastoboot flashing lock..and now I am getting "Can't find valid operating system. The device will not start". I can't unlock the bootloader now as I unchecked OEM unlocking in Developer Options and can't flash factory images also as it says Flashing is not allowed in Lock State, Did I brick the device?
Click to expand...
Click to collapse
Sorry for your loss, but you indeed have a fancy paperweight.
However I wonder if there isnt the QCom USB mode or something like that that exist on older devices, where you can access the phone partitions at a lower level and then restore whatever partitions is broken.
Paradoxxx said:
Sorry for your loss, but you indeed have a fancy paperweight.
However I wonder if there isnt the QCom USB mode or something like that that exist on older devices, where you can access the phone partitions at a lower level and then restore whatever partitions is broken.
Click to expand...
Click to collapse
With the new partitioning no idea if it still works. But OP has nothing to loose anyway i guess.
gee2012 said:
With the new partitioning no idea if it still works. But OP has nothing to loose anyway i guess.
Click to expand...
Click to collapse
Yeah at that point... Not sure what is Google saying about that. Maybe RMA it ?
Saying something like that should work.
"I was using my device, and suddenly it froze and nothing responded. It suddenly rebooted and shown this error message."
gee2012 said:
With the new partitioning no idea if it still works. But OP has nothing to loose anyway i guess.
Click to expand...
Click to collapse
Sorry didn't get, What do you mean by OP has nothing to loose?
Badger50 said:
Yea, I think you may have turned it into a fancy paperweight. Been there, done that. You should have waited to uncheck OEM unlocking until after you locked the bootloader, which wiped your phone. About the only thing I can suggest is to try and run Deuces script to see if you can rescue your device. Best of luck to you.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
How did you recover your devices from that state earlier when you did the same thing?
ram4ufriends said:
Sorry didn't get, What do you mean by OP has nothing to loose?
Click to expand...
Click to collapse
since your phone is now essentially a brick, you can try just about anything without worry of bricking your phone.
ram4ufriends said:
I was on 8.1 with Flash Kernel installed using images...I wanted to get back to stock...so unchecked OEM Unlocking in Developer Options, went to bootloader and locked bootloader using fastoboot flashing lock..and now I am getting "Can't find valid operating system. The device will not start". I can't unlock the bootloader now as I unchecked OEM unlocking in Developer Options and can't flash factory images also as it says Flashing is not allowed in Lock State, Did I brick the device?
Click to expand...
Click to collapse
You cannot flash full images, but you can still flash OTAs... download the full OTA instead, and install (sideload) it from the stock recovery. Be sure to select the SAME build number you were on to begin with- eg. If you were on 8.1, use the 8.1 OTA. There will be a mode there for "Apply update from ADB". You put the phone into "sideload mode" and then send the OTA to the phone via adb. This will work regardless whether you have usb debugging enabled or not. Follow the directions given on the included link.
ram4ufriends said:
How did you recover your devices from that state earlier when you did the same thing?
Click to expand...
Click to collapse
I didn't. They are still paperweights sitting in a drawer!
I got the same message yesterday after doing... God knows what. I can't even remember what went wrong.
My first thought was to flash a factory image. But it didn't helped at first. Probably, because i was trying to flash another factory image and not the one that came as stock on my phone.
So if you don't remember, which image it was, try all of them Hopefully, you'll get your phone booted again.
My first reaction was, is this april fools day? Is this an xda style joke? unchecked oem unlock?
dontbeweakvato said:
My first reaction was, is this april fools day? Is this an xda style joke? unchecked oem unlock?
Click to expand...
Click to collapse
Meh...you know how it is bro....**it happens!
Call google and just tell them your device wont boot all of a sudden; they will probably ask you to factory restore in the recovery, say the phone wont get past the google image. They will RMA that boy for you. You totally bricked. For future reference if you unlock the bootloader, dont waste your time trying to lock it again. Should have just fastboot flashed a factory image in the bootloader and called it a day. Having a unlocked bootloader doesn't effect you in anyway negatively.
ArminasAnarion said:
Call google and just tell them your device wont boot all of a sudden; they will probably ask you to factory restore in the recovery, say the phone wont get past the google image. They will RMA that boy for you. You totally bricked. For future reference if you unlock the bootloader, dont waste your time trying to lock it again. Should have just fastboot flashed a factory image in the bootloader and called it a day. Having a unlocked bootloader doesn't effect you in anyway negatively.
Click to expand...
Click to collapse
Why is this Google's problem? This guy is at fault. Google shouldn't have to pay for it.
This is part of the reason these phones are so expensive.
Sent from my taimen using XDA Labs
mitchdickson said:
Why is this Google's problem? This guy is at fault. Google shouldn't have to pay for it.
This is part of the reason these phones are so expensive.
Sent from my taimen using XDA Labs
Click to expand...
Click to collapse
Well I never said it was the moral thing to do haha; but this guys best bet is to call Google and see if they will RMA it. They RMA'ed my Nexus 6p after the Android 7 twrp brick; and I told them my pone wouldn't boot anymore; they asked me to go to recovery and factory restore, I told them I couldn't boot into recovery and they RMA'ed it. It was my fault for the brick but they didn't care.
ArminasAnarion said:
Well I never said it was the moral thing to do haha; but this guys best bet is to call Google and see if they will RMA it. They RMA'ed my Nexus 6p after the Android 7 twrp brick; and I told them my pone wouldn't boot anymore; they asked me to go to recovery and factory restore, I told them I couldn't boot into recovery and they RMA'ed it. It was my fault for the brick but they didn't care.
Click to expand...
Click to collapse
Did you tell them it was your fault for the brick?
Sent from my taimen using XDA Labs
mitchdickson said:
Did you tell them it was your fault for the brick?
Sent from my taimen using XDA Labs
Click to expand...
Click to collapse
I told them I had an unlocked boot-loader and installed twrp. I had to send them back my old phone and they put a $500 hold on my account, once they received the device and determined the issue was real, they released the hold on my account. In that period of time they could have determined "Oh he bricked the device with twrp" lets charge him $500 for a new one, but they didn't. I mean whats wrong with calling Google and seeing if they will RMA it; sure the OP made a bad mistake but you have not because you ask not.
ArminasAnarion said:
I told them I had an unlocked boot-loader and installed twrp. I had to send them back my old phone and they put a $500 hold on my account, once they received the device and determined the issue was real, they released the hold on my account. In that period of time they could have determined "Oh he bricked the device with twrp" lets charge him $500 for a new one, but they didn't. I mean whats wrong with calling Google and seeing if they will RMA it; sure the OP made a bad mistake but you have not because you ask not.
Click to expand...
Click to collapse
What's wrong with it? You're telling him to call Google and say that for some reason, all the sudden his device won't boot.
This is why I don't fault Verizon for selling bootloader locked phones.
Sent from my taimen using XDA Labs