Question regarding warranty - Nexus 7 Q&A, Help & Troubleshooting

Hi guys, I recently had the misfortune of getting my Nexus 7 bricked.
Right. So if I claim warranty, how do I go about it? I don't mean the contacting htem and stuff. But what do I say to them to ensure maximum chance of getting the warranty?
I mean, I have voided the warranty by installing custom software on my Nexus. But is there any way I could actually logically persuade them to give me warranty? Or is it just luck? Hoping you get a not-so-smart technician to verify it is suitable for warranty?
Sent from my GT-S5570 using xda app-developers app

nobody_nowhere said:
Hi guys, I recently had the misfortune of getting my Nexus 7 bricked.
Right. So if I claim warranty, how do I go about it? I don't mean the contacting htem and stuff. But what do I say to them to ensure maximum chance of getting the warranty?
I mean, I have voided the warranty by installing custom software on my Nexus. But is there any way I could actually logically persuade them to give me warranty? Or is it just luck? Hoping you get a not-so-smart technician to verify it is suitable for warranty?
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
Just call & request an RMA number. If it's truly bricked, they will not be able to ascertain that you installed a custom ROM.

Thank you for that answer but I thought RMAs were for when you returned the device within the first 15days?
And sadly, its obvious that there is a custom rom instAlled. Its hardbricked with an unstoppable bootloop, showing Clockworkmod recovery
Sent from my GT-S5570 using xda app-developers app

What if i do specify some hardware fault that my nexus did have? Like the ghost touch issue. could i get it replaced under that pretext?
Sent from my GT-S5570 using xda app-developers app

Sorry for bumping but I really do need some help. Please?
Sent from my GT-S5570 using xda app-developers app

nobody_nowhere said:
Thank you for that answer but I thought RMAs were for when you returned the device within the first 15days?
And sadly, its obvious that there is a custom rom instAlled. Its hardbricked with an unstoppable bootloop, showing Clockworkmod recovery
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
Why do you say that it is hard bricked? It's near impossible to hard brick a Nexus device. If you see the Google logo when the device powers on, you should be able to go into fastboot mode. Then just use fastboot commands to flash TWRP or CWM recovery and then just flash a ROM from recovery.

veeman said:
Why do you say that it is hard bricked? It's near impossible to hard brick a Nexus device. If you see the Google logo when the device powers on, you should be able to go into fastboot mode. Then just use fastboot commands to flash TWRP or CWM recovery and then just flash a ROM from recovery.
Click to expand...
Click to collapse
Yea, it is hard-bricked. As it is stuck in a bootloop involving CWM-Fastboot-CWM------
It's a long story, which is actually in this thread. http://forum.xda-developers.com/showthread.php?t=2468392
The circumstances of my bootloop are eerily similar, right down to the name of rom I flashed. Or it's probably because of that.
I flashed a new ROM (Kaos Droid 7.0.0) and the fitting gapps some minutes ago from CWM Touch. Everything worked as supposed, no errors, no warnings, nothing. Then I rebooted the Nexus 7 and now it's stuck in the worst bootloop I have seen so far:
The Google Screen appears, stays for some seconds, then I see a screen with the CWM Logo and the text "ClockworkmodRecovery 6.0.38", after this the device seems to reboot and the sequence starts from the beginning again.
I can not get into recovery, I can connect to my PC via USB but connection and disconnection happens every few seconds (because of the bootloop).
Click to expand...
Click to collapse
But I'd rather you answered my questions about warranty since this problem seems totally unfixable. It doesn't respond to any keypress I make except for long-press power.

nobody_nowhere said:
Yea, it is hard-bricked. As it is stuck in a bootloop involving CWM-Fastboot-CWM------
It's a long story, which is actually in this thread. http://forum.xda-developers.com/showthread.php?t=2468392
The circumstances of my bootloop are eerily similar, right down to the name of rom I flashed. Or it's probably because of that.
But I'd rather you answered my questions about warranty since this problem seems totally unfixable. It doesn't respond to any keypress I make except for long-press power.
Click to expand...
Click to collapse
Weird. But if it's rather obvious that you voided the warranty, I don't think they'll send you a new one.

That's the problem. The Google logo does appear and technically I'm supposed to be able to use my fastboot commands to undo the issue. But it doesn't work. Since the nexus doesn't respond to a single button press. So I cannot enter fastboot mode proper.
Yea, I knew that. But what if I get it replaced on some other reason than that?
Sent from my GT-S5570 using xda app-developers app

BrianXP7 said:
Did you somehow interrupted a bootloader flash or wrote "fastboot erase bootloader"? If not and the "Google" logo still appears, you really don't need an RMA.
Click to expand...
Click to collapse
No. It's like when you type reboot recovery. It just goes directly into cwm. And then it reboots and again. And again.
https://dl.dropboxusercontent.com/u/12668781/Nexus7_bootloop.mkv

BrianXP7 said:
Since you can't access MTP, you can try ADB Sideload. (It's a feature in later versions of ClockworkMod Recovery and Team Win Recovery. Why are you still using CWM by the way?) It'll transfer the flashable ZIP to the root of /sdcard and it'll flash immediately after.
RMAs should be only used for last resort bootloader bricks if you don't have access to the proprietary blobs. Luckily, you're fine.
Click to expand...
Click to collapse
Mate, my nexus does not respond in any way to the keypresses I make. So I cannot access clockworkmod, or fastboot mode, or even try to force a regular boot. It just bootloops on and on, completely unimpressed by my presses

BrianXP7 said:
Oh, my mistake. I didn't see your video. Sorry about that. (Bootlooping might be incorrect terminology for recovery. I'm not sure.) Try reflashing another recovery image like TWRP instead? That's the best I can give you for now.
Click to expand...
Click to collapse
Okay, I love that you're atleast trying to help. But the point is I literally have no way of flashing anything on it. I cannot do anything to it, bro. Whatever I do it just keeps bootlooping on and on. If I could access fastboot, I could easily fix this problem but I can't so.
I'd love your feedback concerning what I should do with regards to warranty

BrianXP7 said:
Again, it's not a bootloader brick. You don't need an RMA. In the video, you simply left it booting normally (then falling back to recovery). Also, it's not recovery's issue. It's probably the internal ROM that's made unbootable by some kind of OTA update.
To enter Fastboot mode, turn off your device completely. After, hold Power + Volume Down. Release Power (keep holding Volume Down) when "Google" displays. If done successfully, it'll display an Android lying down. That's Fastboot mode.
Unless you somehow damaged your hardware keys, you might be completely screwed. In order for your RMA to be accepted, you need to remove any trace of modification and relocking the bootloader. If you did restore it to an RMA acceptable state, it's already usable. (Screwing with the bootloader completely, or APX mode, will be accepted as they can't detect if you unlocked the bootloader or not.)
Click to expand...
Click to collapse
hmmmm. Is there a way of completely disabling the bootloader or something?

BrianXP7 said:
Yes, but you need access to Fastboot. If you did have access Fastboot, might as well fix it yourself. Basically, you flashed an incorrect bootloader image or interrupt the writing process. (Just don't think about it unless you have a bootloader backup.)
Click to expand...
Click to collapse
Okay, Can you do something for me?
Type su and then reboot recovery on the terminal.
Now when the Google Image is shown in the beginning, can you try to put it in Fastboot mode instead? Power + Volume Down, like you said.
Tell me if it works

BrianXP7 said:
What? I think you're over-complicating things. You don't even seem to try.
Just turn your device off. (Forced, normally, however you want.) Hold Power + Volume Down until "Google" appears. (That's when you release the power button but keep holding Volume Down.) If you see an Android laying down with a few options such as "Reboot normally", you're in Fastboot mode.
After that, just flash the stock factory images. It's as simple as that.
Click to expand...
Click to collapse
Did you try to do that for me?
I need You to do that for me. And tell me if it works. My Nexus 7 simply cannot be saved. Whatever I do, It doesn't respond. I know all about Fastboot mode, and recovery mode, and flashing factory images. I'm not a n00b like you seem to think. I do have a problem, but it seems to have been caused by random hardware fault rather than a fault on my part. But the result is the same.

nobody_nowhere said:
Did you try to do that for me?
I need You to do that for me. And tell me if it works. My Nexus 7 simply cannot be saved. Whatever I do, It doesn't respond. I know all about Fastboot mode, and recovery mode, and flashing factory images. I'm not a n00b like you seem to think. I do have a problem, but it seems to have been caused by random hardware fault rather than a fault on my part. But the result is the same.
Click to expand...
Click to collapse
@GedBlake;, you're the only person who understood my problem and tried to help me before. Could you perhaps do the same again?

nobody_nowhere said:
@GedBlake;, you're the only person who understood my problem and tried to help me before. Could you perhaps do the same again?
Click to expand...
Click to collapse
Hi, nobody_nowhere..
I will try, but I'm not quite what it is you're asking of me...
If it's concerning RMA, then I don't think I'm going to be of much help, I'm afraid... as I don't know the procedure for claiming under warranty (ie., RMA), having never done it myself.
My own Nexus 7 is just a liitle over a year old now, and I've so far been fortunate in having only had minor, and easily recoverable softbrick/bootloop type situations.
In your second post on this thread, you suggest that RMAs were time limited to just 15 days. I'm not completely sure, but I think this is incorrect. In most countries/jurisdictions, warranties usually run for 12 months. This is certainly the case here in the UK.
The thread you mention, well, having read it yourself, you'll know that I attempted to resolve the problem experienced by the OP of that thread... and it all came to nothing in the end.
There seems to be two recognisable categories of 'brick'... hardbrick, typically caused by a damaged, corrupt or wholly erased bootloader... and softbrick, which can have any number of causes, but is usually always resolvable - principally by accessing fastboot mode. Fastboot mode, is a sort of a 'get-out-of-jail' free card... and I've used it many times in the past.
But if you can't access fastboot mode (apropos of your current predicament), but the bootloader still works (if it didn't, NOTHING AT ALL would happen), your technically not hardbricked.
You have an unrecoverable soft brick... semi-hardbrick maybe? - a third category of 'brick'??
With regard to claiming under warranty... as I've already said, I really have no idea how to go about doing this, but I assume some sort of 'phone conversation would initially start the ball rolling and some questions would be asked of the owner of the Nexus 7...
...but, if it is unambiguously clear (and it sounds like it is, with CWM boot looping), that you've installed custom software, then there's no point in being disingenuous. As soon as they receive the device, they'll know. It you're honest with them, you might have a fair chance of them fixing it. If you lie outrightly, your credibility suffers.
Your best bet, I think, is to emphasize that's it's a hardware issue - emphasize the buttons aren't working properly. Emphasize that you're a knowledgeable Android user, and you're familiar with fastboot, and flashing custom software. The idea, here, is to make it more of a hardware problem, than a software problem - because it then throws the ball back into their court. And personally, I happen to think it is a hardware problem. I have no idea if this will work or not - I'm really just guessing here.
Whether installing custom software itself is sufficient to void warranty is a discussion that could fill an entire thread many pages over, such is the ambiguity of the issue.
It's generally considered, though, that unlocking the bootloader alone, is enough to leave your warranty in tatters... but flashing a Google factory stock image requires the bootloader to be unlocked anyway. So, I'm not quite sure how that contradiction squares itself away!
Indeed the flash-all.* script, that ships with factory stock images, unlocks the bootloader as matter of course. Of course, Google recommend re-locking the bootloader afterwards.
And what of Nexus 7 Jellybean 4.2.2 users, several months ago, who could root without unlocking the bootloader at all, using the motochopper "exploit".
Does rooting with an exploit count as installing custom software... you're messing with /system after all?
Ultimately though, I think that you may have to face an unpalatable truth - that tinkering with your device, does sometimes go wrong... in ways that leave even the most experienced users baffled (and I'm not even close to that level of knowledge and expertise).
There are some posters, here on XDA, who have in their sig., a list of previously owned devices... crossed out... and the word BRICKED next to them. These are the guys with thousands of posts to their name... and their 'graveyard' of dead devices are their metaphorical battlescars.
As soon as you type fastboot oem unlock, you're tacitly accepting that this may happen to you some day... you've effectively 'removed the back' of of that expensive clock/watch/HiFi system or Nexus 7... in the belief you can make it 'go' faster or perform better. Most of the time, you will be successful, and you will make it perform better, with whatever Custom ROM or kernel you've chosen to install.
But sometimes, something will go so horribly wrong... that there is no way back.
And all that is then left is the capriciousness of the company you have warranty with (via RMA)... and you're own negotiating skills.
I really do wish there was some button sequence, or command line I could suggest... but when dealing with the warranty people... you're on your own, sorry to say. Ultimately, and essentially... they may choose to repair it, or not. And beyond that, there's not much else I can add.
Except... best of luck.
Rgrds,
Ged.

Related

[Q] How (im)possible is it to brick the N4?

As long as you can get into fastboot mode, you haven't bricked your device
Click to expand...
Click to collapse
Is this statement true?
I know it isn't impossible to brick your device to the point of no return. I've actually done it myself (huray!) with my Nexus S. It was declared dead even by AdamOutler himself, the maker of the Unbrickable Resurrector. After trying to unbrick it myself, I sent it to him. Apparently I screwed up the radio, a mistake which is impossible to recover from. Don't ask me how I did it... I did flash something before, but my phone worked fine for a while. Only then the battery drained really quickly. When it was dead and I plugged in the charger, it booted up fine, but the moment I started the browser my Nexus S died. Forever. RIP.
I guess it's no different with the N4. If you screw up the radio, you have a problem. Can somebody confirm this? And are there other ways to brick your phone to the point of no return?
I think it's kind of stupid that you are able to brick your phone. You can't brick a PC, can you? That's just impossible. You can ALWAYS completely reset everything. Well, not with Android apparently. I think it's weird that even with Nexus devices, there's still a way to brick it. I guess you need to be stupid like me to brick a Nexus device, but still... it shouldn't be possible.
Yes as long as bootloader mode is able to be started! You cannot brick. Just flash google stock factory images.
Sent from my Nexus 4 using xda premium
Its because Android phones are dependant on the Bootloader, whereas a PC is dependant on the BIOS and CMOS. If you fail at flashing a BIOS then you brick the motherboard. So you technically can brick a PC.
Hah, I've bricked PC's with BIOS flash fails.
But as for the phone, as long as you can enter fastboot, you are able to recover.
Harry GT-S5830 said:
Its because Android phones are dependant on the Bootloader, whereas a PC is dependant on the BIOS and CMOS. If you fail at flashing a BIOS then you brick the motherboard. So you technically can brick a PC.
Click to expand...
Click to collapse
You can? Ah, then I rest my case.
I did screw up the radio though, and not the bootloader. I was able to get into download mode using the resurrector tool, only the screen stayed black.\
by the way, I don't think the Bootloader is the same as the BIOS. If it was, then you would technically be able to flash anything on your phone, even Windows. It isn't split up like the BIOS and Windows. Correct me if I'm talking nonesense by the way ;p.
You could think of it as the bootloader = the BIOS and Android = Windows
Androyed said:
[snip]
by the way, I don't think the Bootloader is the same as the BIOS. If it was, then you would technically be able to flash anything on your phone, even Windows. It isn't split up like the BIOS and Windows. Correct me if I'm talking nonesense by the way ;p.
Click to expand...
Click to collapse
You technically could flash anything on your phone, assuming you had the right bootloader and partition table and the right drivers. The issue is that the bootloader on an Android device is designed to boot (i.e., load into RAM ) a Linux kernel. It isn't designed to (and hence, won't) boot a Windows, or any other, kernel.
You could always delete your bootloader, thall brick your device pretty fast
efrant said:
You technically could flash anything on your phone, assuming you had the right bootloader and partition table and the right drivers. The issue is that the bootloader on an Android device is designed to boot (i.e., load into RAM ) a Linux kernel. It isn't designed to (and hence, won't) boot a Windows, or any other, kernel.
Click to expand...
Click to collapse
Very true. For an example, Check out the HD2 phone and the various bootloaders available for it. I have booted Windows Mobile 6 and 7, Ubuntu, oh.. and Android on it. It was originally a WM6 phone. It also has the ability to change partition sizes, and has an sBoot partition so it can do a true dual boot. One from Nand memory and one from SD card with just a reboot.
I waiting to see if we get a way to flash unsigned bootloaders on Nexus 4 (or get a key).
I seem to recall a few devices being bricked in the few days after release. There was a problem with the faux kernel that caused the device to totally and irreparably brick if one overclocked (to 1.8Ghz I think) and then ran an antutu benchmark.
The few could not recover from the brick despite a lot of suggestions thrown around and some even from the dev of the kernel. Ultimately, they RMA'd.
Have a look at this thread: http://forum.xda-developers.com/showthread.php?t=2011328
Many users seen to have bricked their devices by overclocking their CPUs and running benchmarks.
Heck, I even see people talking about the red LED problem daily. Something's clearly not right...
Sent from my Nexus 4 using Tapatalk 2
The red led problem clearly appears too frequently... it really has to be cleared up what the heck is causing it.
Lownita said:
The red led problem clearly appears too frequently... it really has to be cleared up what the heck is causing it.
Click to expand...
Click to collapse
The red led bug is most likely hardware related.
Just think about it. Overclocking draws significantly more power. The nexus 4 isn't even able to supply the power for USB host, so it might be some kind of power failure.
Or simply a shorted circuit.
Nuu~ said:
The red led bug is most likely hardware related.
Just think about it. Overclocking draws significantly more power. The nexus 4 isn't even able to supply the power for USB host, so it might be some kind of power failure.
Or simply a shorted circuit.
Click to expand...
Click to collapse
There is the point.
Bricking by software alone will be almost impossible. I have seen a few flashing bricks recovered already.
Bricking by damaging the hardware, well, that is probably unrecoverable. Over Clocking or O/C + Over-Heat is causing what seems to be permanent damage in some phones.
fastboot mode on nexus 4 says "secure boot: on" --- anyone knows what that means? afair i havent seen that on my old gnex and nex7.
and is it possible to use download mode to flash a new bootloader in case the old one is corrupted?
I don't think anyone has the QCOM_USB_DLD mode figure out yet and I don't think anyone knows what secure boot does either, I know originally people blamed it for custom recoveries being reverted, but that's just a script that's called on bootup.
molesarecoming said:
fastboot mode on nexus 4 says "secure boot: on" --- anyone knows what that means? afair i havent seen that on my old gnex and nex7.
and is it possible to use download mode to flash a new bootloader in case the old one is corrupted?
Click to expand...
Click to collapse
I've seen that on my Nexus S... after I had bricked it completely ;p. I don't think it had anything to do with the brick though. It's something from HTC devices: http://www.addictivetips.com/mobile...on-htc-android-phones-with-unrevoked-forever/. At least I think so.
When I tried to repair my bricked Nexus S, I asked if it had something to do with secure: on. They didn't know what it was exactly, so maybe it isn't the same as s-on on HTC devices.
molesarecoming said:
fastboot mode on nexus 4 says "secure boot: on" --- anyone knows what that means? afair i havent seen that on my old gnex and nex7.
Click to expand...
Click to collapse
Pure speculation on my part: I think that the "secure boot: on" relates to the boot chain of the Snapdragon SoC. When it's on, I think that it will not boot an unsigned bootloader, and hence you cannot boot the device. Similar to, but not quite the same as, S-ON for HTC devices as was mentioned above.
molesarecoming said:
and is it possible to use download mode to flash a new bootloader in case the old one is corrupted?
Click to expand...
Click to collapse
More speculation: I haven't had much time to look into it yet, but I'm guessing that you should be able to flash a .tot file (an LG "factory image" I think like the ones found here) while you are in download mode. I think it requires something like the LGNPST tool with the right .dll. This is my first LG device (and my first Snapdragon SoC), so I'm still in the reading/learning stages.

[Q] Unable to unlock bootloader. RMA my only option?

As title suggests, my bootloader is locked and my N7 will not boot past the Google logo. If i try Recovery, it says "booting failed" so I can only assume that it was lost/erased. Is an RMA through Asus my only choice at this point?
If you can boot into bootloader mode (which you can) you can use fastboot to flash a stock image. Here is a fine guide. It seems like something on your data and/or recovery partition got corrupted. If you still have a warranty, you should send it to RMA. But it's your choice.
Erovia said:
If you can boot into bootloader mode (which you can) you can use fastboot to flash a stock image. Here is a fine guide. It seems like something on your data and/or recovery partition got corrupted. If you still have a warranty, you should send it to RMA. But it's your choice.
Click to expand...
Click to collapse
I can get to bootloader but I am unable to unlock it. When I try to unlock it, it gives me the prompt, I click YES and then it just goes back to bootloader but still locked.
Well, that's interesting. I don't know what could it be. I guess, RMA is your best option.
engagedtosmile said:
I can get to bootloader but I am unable to unlock it. When I try to unlock it, it gives me the prompt, I click YES and then it just goes back to bootloader but still locked.
Click to expand...
Click to collapse
Hi, engagedtosmile...
This seems to be a common problem... inability to unlock the bootloader... I've come across it a few times, both here on XDA and on other forums.
As I suggested a while ago with this guy who had a similar problem... it could potentially be an eMMC chip gone bad, a corrupted partition structure (very unlikely though, since both his and your Nexus 7 boots and works fine otherwise) or a corrupted bootloader (extremely unlikely, as the Nexus 7 wouldn't boot at all).
As a bit of a last ditch 'clutching-at-straws' suggestion, I advised him to try a different USB port on his PC and/or a different USB cable... my experiences of using fastboot, is that it can be remarkably fussy about such things at times.
Anyway, it appears to have worked for him.
So, it might be worth a shot... change to a different USB port, and/or maybe try a different USB cable.
Good luck... and hope you have as much success as the guy whose post I referenced above.
Rgrds,
Ged.

[Q] Stuck on boot, cannot reset, cannot mount cache error

Hi everybody, I enjoyed my stock N4 for almost a year and today several apps started to crash suddenly, after that the device rebooted itself and never got out of the bootloop. I immediatly booted into recovery and tried to wipe the cache memory and perform a factory reset but I cannot do either of the two, the error I get is something like "can't mount cache partition".
What should I do? How did this happen?!? I really need my phone back asap.
Thanks everybody!
Flash the stock images.
Chromium_ said:
Flash the stock images.
Click to expand...
Click to collapse
Ok I will but...How can this happen? A fully stock phone who never had a problem suddenly corrupts it's partitions?! (This is my understanding of the situation, correct me if I am wrong)
Thanks again for the link
Update: unlocking the bootloader works but when I reboot it appears to be locked again.
flashing the bootloader img file fails.
chikosneff said:
Update: unlocking the bootloader works but when I reboot it appears to be locked again.
flashing the bootloader img file fails.
Click to expand...
Click to collapse
sounds like your storage itself fails. thats the same issue that happens when the storage goes bad.
simms22 said:
sounds like your storage itself fails. thats the same issue that happens when the storage goes bad.
Click to expand...
Click to collapse
Thanks for helping, yes it looks like..so I can throw away my phone or there's something more I can try?
It feels so weird because it's one of the few phones I always kept stock, never fell, never had a single problem. Damn.
chikosneff said:
Thanks for helping, yes it looks like..so I can throw away my phone or there's something more I can try?
It feels so weird because it's one of the few phones I always kept stock, never fell, never had a single problem. Damn.
Click to expand...
Click to collapse
You could give this a try, but I really doubt it'll do much. I guess its worth a shot though.
chikosneff said:
Ok I will but...How can this happen? A fully stock phone who never had a problem suddenly corrupts it's partitions?! (This is my understanding of the situation, correct me if I am wrong)
Thanks again for the link
Click to expand...
Click to collapse
chikosneff said:
Update: unlocking the bootloader works but when I reboot it appears to be locked again.
flashing the bootloader img file fails.
Click to expand...
Click to collapse
Tried to Toolkit yet ? http://forum.xda-developers.com/showthread.php?t=1766475
Why did it happen? A phone is basically a mini computer, same as when you have to reload a computer OS sometimes,(failing hardware, bad app???)
Timboe73 said:
Tried to Toolkit yet ? http://forum.xda-developers.com/showthread.php?t=1766475
Why did it happen? A phone is basically a mini computer, same as when you have to reload a computer OS sometimes,(failing hardware, bad app???)
Click to expand...
Click to collapse
I'll give it a shot thanks, but I am afraid that the fastboot flash error is pretty clear :crying:
I get the phone being a computer, and I am totally ready to reload an OS...but I am not so ready to see the storage fails so suddenly leaving me with no phone, especially because this phone has received more care than any other phone I ever had..
Timboe73 said:
Tried to Toolkit yet ? http://forum.xda-developers.com/showthread.php?t=1766475
Click to expand...
Click to collapse
If its failing when he does it manually via fastboot commands, its very unlikely that using a toolkit will change anything. A toolkit simply runs the same fastboot commands behind a GUI.
Switched to windows to give the toolkit a try, then I will follow the unbrick procedure...I still cannot believe that this phone is lost without even having experienced the fun to mess it up with my own hands
chikosneff said:
Switched to windows to give the toolkit a try, then I will follow the unbrick procedure...I still cannot believe that this phone is lost without even having experienced the fun to mess it up with my own hands
Click to expand...
Click to collapse
As expected: toolkit not working. Since the bootloader " relocks" itself after rebooting the toolkit is unable to flash it afterwards.
Will try to contact google support but I am currently living in Europe I don't think it will be easy to get help.
Any other help is greatly appreciated. Thanks everybody.
1. if its within the warrenty period, this is something that would be covered.
2. its fixable. it can be professionally repaired, or you can try to do it yourself with the right parts.
but you will lose whatever you had in your storage, if you havent already.
another case reported :/
i think some batches of nexus 4 contains emmc brick bugs
just see this thread, more then 5 or 6 have been reported here.
http://forum.xda-developers.com/showthread.php?t=2259334
so after reading that thread i **** my self, because if this occured to my nexus i will have no warranty no google claims no nothing because i live in Pakistan.
So i ran emmc check app on my phone to check what it shows.
my emmc check shows i have "NO, Sane chip"
this means i am safe? if it give me "Yes, Insane chip" then i,m not safe according the my theory.
EMMC check app also shows the chip type, my chip type is "016g92"
googling this chip type i came across no specific results, one from S3 sudden death thread discussion. one person reports he have the 016g92 type and it is a safe chip according to other folks.
and one person having a galaxy s3 bricked his emmcs chip and claim the warranty. after the phone returns his chip type change to 016g92
http://smartphone.usofttech.com/t85915.html
so they change the emmc chip to 016g92.
can i surely assume that my nexus is safe from this serious hardware defect?
also any one here run the emmc chip and do give there chips type here, as i want to confirm if i,m safe or not. if not i,m going to sale my phone here. because the lose will be unbearable for me if the brick did occured
---------- Post added at 11:48 AM ---------- Previous post was at 11:37 AM ----------
simms22 said:
1. if its within the warrenty period, this is something that would be covered.
2. its fixable. it can be professionally repaired, or you can try to do it yourself with the right parts.
but you will lose whatever you had in your storage, if you havent already.
Click to expand...
Click to collapse
Dear Sir do advice me
simms22 said:
1. if its within the warrenty period, this is something that would be covered.
2. its fixable. it can be professionally repaired, or you can try to do it yourself with the right parts.
but you will lose whatever you had in your storage, if you havent already.
Click to expand...
Click to collapse
I still have 2 weeks of warranty left but I'll be in Europe till next year..I will try to ask the warranty service if I can send it in at my own expense.
Damn a worldwide warranty service doesn't look so useless now as it looked when I bought it :laugh:
PHONE BACK FROM THE DEAD!!!
So I got in touch with google's customer care to arrange the RMA and just to show them that my phone was impossible to recover I jumped ahead and told 'em: ok let's do a factory reset together so that I can show you what's the problem....
Fastboot>recovery>>data wipe....COMPLETED!
I cannot understand why did it work, I tried to wipe it at least ten times yesterday.
So now I have my N4 back working. What's your opinion on what happened? Do you feel like the problem is going to show up again soon? Is there anything I should do now that it's working? I just did a factory reset, not the cache wipe.
Just FYI: RMA from oversea is a pain in the ass, you have to ship the phone back to somebody in the U.S. and THEN ask for the RMA.
I wish I had your luck, mine did the same thing about 2 weeks ago. Couldn't get it to factory reset either. Mounting issue. My RMA came in yesterday. I'm enjoying the new phone though. It's even got the little nubs on the back. Mine original was a creaky 1st or 2nd batch one, I think. I will miss all the memories, pics, and data on my old one though.
SefEXE said:
I wish I had your luck, mine did the same thing about 2 weeks ago. Couldn't get it to factory reset either. Mounting issue. My RMA came in yesterday. I'm enjoying the new phone though. It's even got the little nubs on the back. Mine original was a creaky 1st or 2nd batch one, I think. I will miss all the memories, pics, and data on my old one though.
Click to expand...
Click to collapse
Since I feel this problem is hardware related I do not feel completely safe and I believe you were the lucky one getting the RMA
I had no choice, I should have sent the phone back to the US and then ask for the RMA...big pain in the ass
:fingers-crossed: let's hope this thing holds

Nexus 6P stuck on boot screen

Hi guys,
Right so I really need some help right now,
My nexus 6p is enrolled with the beta program but I am unsure which particular version of nougat it is on...
So I was sending a snapchat last night, and the phone randomly crashed and restarted. It then did it again when I attempted to do the same again. It kept on repeating do to this till the point where it wont boot anymore, it gets to the google logo and crashes or occasionally gets to the part of the boot with the shapes and crashes. So its stuck in some kind of bootloop?
So the phone is enrolled in the Beta, but I have not done anything else to it such as rooting etc.
This is a really stressful situation for me right now, my phone is essential for me right now, as a student from the UK studying abroad in Canada, I cant do any exchanges or afford to buy a new phone.
I was wondering if someone could help me fix this, I really dont know anything about Android when it comes to this kind of thing, and if possible I really don't want to void the warranty.
A guide on what to do would be really appreciated, keeping in mind Im not experienced in doing this kind of thing on androids.
Thanks,
Ben
Can you boot into the bootloader/fastboot mode?
benhawley2711 said:
Hi guys,
Right so I really need some help right now,
My nexus 6p is enrolled with the beta program but I am unsure which particular version of nougat it is on...
So I was sending a snapchat last night, and the phone randomly crashed and restarted. It then did it again when I attempted to do the same again. It kept on repeating do to this till the point where it wont boot anymore, it gets to the google logo and crashes or occasionally gets to the part of the boot with the shapes and crashes. So its stuck in some kind of bootloop?
So the phone is enrolled in the Beta, but I have not done anything else to it such as rooting etc.
This is a really stressful situation for me right now, my phone is essential for me right now, as a student from the UK studying abroad in Canada, I cant do any exchanges or afford to buy a new phone.
I was wondering if someone could help me fix this, I really dont know anything about Android when it comes to this kind of thing, and if possible I really don't want to void the warranty.
A guide on what to do would be really appreciated, keeping in mind Im not experienced in doing this kind of thing on androids.
Thanks,
Ben
Click to expand...
Click to collapse
i have the same issue, i have tried using toolkits and even using fastboot commands and the phone just keeps getting stuck on the google logo screen. at this point i think i might have to get a replacement. unless some can offer a solution
Same issue
I have exactly the same issue. I am on Angler 7.1.1 Beta/NPF10C. Since the OTA came out everything was fine, until yesterday while trying to send a picture on Hangouts the phone froze and rebooted, and rebooted and rebooted. The bootloader is locked and no USB debugging enabled. So far I tried:
- wipe data/factory reset through recovery - first try, the phone reset and let me set it up, but then froze after 5 minutes and kept rebooting; after that any factory reset just get's stuck at Google logo at boot
- tried to adb sideload rescue OTA - previous build NBD90X starts verification and fails at 50% with the error: can't flash older over newer (duh!); and the ota build npf10c can't be read. I tried on Mac and Windows. No matter what I do adb can't read zip file. Also tried updated sdk tools and everything, no luck.
Read on Google forums that there is a chance of hardware issue and the phone must be returned for exchange if still under warranty.
Update: I was able to sideload rescue OTA on Linux, but the phone is still in bootloop. Only showing Google logo and reboots. I'll wait till next DP2 comes out and I will try to sideload it and see if it fixes the issue.
redduc900 said:
Can you boot into the bootloader/fastboot mode?
Click to expand...
Click to collapse
Yes I can, any suggestions as to what I can do?(sorry im a noob, but the bootloader is the power button and volume down menus right? haha)
Is there any way I can get my data off the phone?
.
So I followed these instructions for the rescue OTA (I cant post the links because im new to the site)
You can find it by going to the google help forums
Well I Got to Step 9 and it didnt work and it says a warranty or repair is the only recourse.
Is there no other way of fixing this? As I said before, a warranty replacement is not possible for me as I'm in the wrong country
benhawley2711 said:
Yes I can, any suggestions as to what I can do?(sorry im a noob, but the bootloader is the power button and volume down menus right? haha)
Is there any way I can get my data off the phone?
Click to expand...
Click to collapse
I don't think there is a way, since the phone is encrypted, boot-loader locked and oem unlocking is disabled. I think that is the whole purpose of having device secured, so none can get files from your phone.
---------- Post added at 01:29 AM ---------- Previous post was at 01:26 AM ----------
benhawley2711 said:
So I followed these instructions for the rescue OTA (I cant post the links because im new to the site)
You can find it by going to the google help forums
Well I Got to Step 9 and it didnt work and it says a warranty or repair is the only recourse.
Is there no other way of fixing this? As I said before, a warranty replacement is not possible for me as I'm in the wrong country
Click to expand...
Click to collapse
Looks like your recovery is bad and that is when warranty suppose to be used. However, even if there is warranty, Huawei website states that they won't cover improper testing of the devices, which I think falls under beta testing category.
denys2000 said:
I don't think there is a way, since the phone is encrypted, boot-loader locked and oem unlocking is disabled. I think that is the whole purpose of having device secured, so none can get files from your phone.
---------- Post added at 01:29 AM ---------- Previous post was at 01:26 AM ----------
Looks like your recovery is bad and that is when warranty suppose to be used. However, even if there is warranty, Huawei website states that they won't cover improper testing of the devices, which I think falls under beta testing category.
Click to expand...
Click to collapse
At this point, I'm not too bothered about my data, because all my photos have backed up to google photos.
Should I just attempt a factory restore? I know someone above said their phone just froze after 5 mins, but I suppose I could try and unenroll from the beta in that time and hopefully take me back to a stable release without the bug.
- I'm not sure if that will work though :/
benhawley2711 said:
At this point, I'm not too bothered about my data, because all my photos have backed up to google photos.
Should I just attempt a factory restore? I know someone above said their phone just froze after 5 mins, but I suppose I could try and unenroll from the beta in that time and hopefully take me back to a stable release without the bug.
- I'm not sure if that will work though :/
Click to expand...
Click to collapse
If you have no worries about losing data then you should try a factory reset, after all it might help. IMO you should definitely unenroll from beta at this point.
denys2000 said:
If you have no worries about losing data then you should try a factory reset, after all it might help. IMO you should definitely unenroll from beta at this point.
Click to expand...
Click to collapse
Yeah, so it wont let me go into recovery mode just bootloops, safe to say its pretty f***ed.
Suppose trying to claim warranty is all I can do, but can't do that for two months.
At this point, I'm gonna have to admit defeat and buy a new phone until I can claim the warranty back in the UK when I return.
benhawley2711 said:
Yeah, so it wont let me go into recovery mode just bootloops, safe to say its pretty f***ed.
Suppose trying to claim warranty is all I can do, but can't do that for two months.
At this point, I'm gonna have to admit defeat and buy a new phone until I can claim the warranty back in the UK when I return.
Click to expand...
Click to collapse
Good luck with the warranty. Unfortunately, mine has ended and I am currently using my girlfriend's old iphone 5s with a tiny tiny tiny screen
I used adb and sidecar and all the stuff mentioned by others. it says 100% and i rebooted my device and still google logo occuring and its not fixed. Any other option that i can try now?
[Guide] Fool/Noob proof way to do clean installs on Nexus Devices
http://forum.xda-developers.com/nexu...talls-t3518311
try this clean install should work
KKPGAME said:
I used adb and sidecar and all the stuff mentioned by others. it says 100% and i rebooted my device and still google logo occuring and its not fixed. Any other option that i can try now?
Click to expand...
Click to collapse
use these commands in bootloader.
adb shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384
adb shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384

Nexus 6P will not boot when boot loader is locked!

After using the megapixel rom. I tried flash back to stock with root tool kit.
During the process it told me I had to manual boot in recovery to a factory restore. That would not work so I ended up soft bricking my phone. I was able to side load twrp and the latest build and flash it (thank god). No when I do oem lock boot loader, my nexus 6p won't boot. As soon as I oem unlock, it will boot. Any ideas what could be cause that?
If you did not restore the recovery it probably throws a flag and says the configuration is invalid. You need to restore completely (recovery, boot, system, vendor, etc) through fastboot so that it is truly stock.
Cheers,
B.D.
This is a perfect time to remind folks that "locking" the bootloader is something that should be done with great care. There are dozens, if not hundreds of "my phone is bricked" threads centered around locking their bootloader without understanding the requirements and risks. If you don't have a reason to do it, leave it unlocked. If I need to do it, I flash 100% back to stock using a full factory image before locking.
Sent from my Nexus 6 using XDA-Developers Legacy app
BostonDan said:
If you did not restore the recovery it probably throws a flag and says the configuration is invalid. You need to restore completely (recovery, boot, system, vendor, etc) through fastboot so that it is truly stock.
Cheers,
B.D.
Click to expand...
Click to collapse
So you wouldn't recommend using the Nexus toolkit to flash factory? Can you give me the string in order that I would use to flash factory via fastboot? Fast boot is also hit or miss with the commands for me.
Blackfish77 said:
So you wouldn't recommend using the Nexus toolkit to flash factory? Can you give me the string in order that I would use to flash factory via fastboot? Fast boot is also hit or miss with the commands for me.
Click to expand...
Click to collapse
No offense intended, but this always irks me quite a bit.
Absolutely DO NOT use toolkits for anything at all, ever. They're not easier, they're not faster. It's just doing fastboot / adb with a UI that has buttons you can click instead of typing in fastboot.
This. This is the exact reason you shouldn't use toolkits. Especially if you don't know the manual way. It borks something up and now you need to wait possibly hours to get a working phone again when the solution would only take about 15 seconds to fix.
You need to fully familiarize yourself with this guide here;
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
ADB/Fastboot is absolutely not "hit or miss." If you have trouble with it then you need to make sure that your drivers are properly installed and you're entering commands correctly. Also make sure to ALWAYS keep your ADB & fastboot drivers up to date via the Android SDK. All of this is covered in the link above.
As far as your bootloader issue. You cannot return to a locked bootloader with anything other than 100% complete unadulterated stock factory images. No TWRP, no root, no Xposed, no Magisk, no build.prop edits etc., ...Nothing.
Use fastboot to flash your factory images you downloaded. You can use the flash all bat file or individually flash each separate. Again it's all covered in the link I posted above.
Also, what do you mean you couldn't wipe/reset from stock recovery? When you flash stock recovery and boot to it, you will see an Android on its back with an exclamation mark in a red triangle. You may or may not see text that reads "No Command". Either way, from that point hold down the power button and then press and release volume up. You will boot to stock recovery where you can wipe your data.
Not for nothing, but as mentioned above, people have hard bricked their 6P from locking bootloader's on combos besides stock. You got extremely lucky you didn't as well. Please take some time to read and fully understand what you're doing with your ~600$ device.
This is also, for the most part, pretty standard stuff as far as flashing / modding goes. At least since 2010 when I got into it. If you want to know the exact string of fastboot commands please read and use the guide I linked. It teaches you literally everything. There's nothing it doesn't cover and once you get used to it you will never use a toolkit again.
Hope I didn't come off rude, but basically since 2010 when I got into this across all my devices I try to help out in the Q+A sections. I've probably participated in hundreds and hundreds of "help, I used a toolkit and my phone is bricked and I have no idea how to fix it, I just wanted cool stuff on my phone" threads. They're absolutely 100% not worth the trouble and headaches from them. Especially if you have no idea what they're doing on the back end. Know Fastboot and ADB like the back of your hand and just prefer to use them? That's a different story, if something fails then you fix it yourself in 10 seconds. But for the love of God, please please please please please stop using toolkits if you don't know how to fix issues on your own. You will eventually hard brick. I've seen it happen dozens of times. Thread turns into a circlej*rk about whether toolkits are bad or not, OP hard bricks their phone and commits fraud, which is illegal by trying to RMA it. Just don't use them. It's simple enough without them. Why reinvent the wheel when it works just fine?
You should only lock bootloader when you are on stock factory image from nexus developers site. Either use flash_all script or flash everything manually. As others said keep away from toolkits.. You never know what can go wrong or what they re doing in background.
As I understand you restored TWRP and Megapixel rom and tried to lock the bootloader when you had that combination installed on your phone? That can not be done. You are either full stock (rom, kernel, recovery...) and locked bootloader or unlocked bootloader and any combo of kernel, rom, recovery that you want.
RoyJ said:
No offense intended, but this always irks me quite a bit.
Absolutely DO NOT use toolkits for anything at all, ever. They're not easier, they're not faster. It's just doing fastboot / adb with a UI that has buttons you can click instead of typing in fastboot.
This. This is the exact reason you shouldn't use toolkits. Especially if you don't know the manual way. It borks something up and now you need to wait possibly hours to get a working phone again when the solution would only take about 15 seconds to fix.
You need to fully familiarize yourself with this guide here;
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
ADB/Fastboot is absolutely not "hit or miss." If you have trouble with it then you need to make sure that your drivers are properly installed and you're entering commands correctly. Also make sure to ALWAYS keep your ADB & fastboot drivers up to date via the Android SDK. All of this is covered in the link above.
As far as your bootloader issue. You cannot return to a locked bootloader with anything other than 100% complete unadulterated stock factory images. No TWRP, no root, no Xposed, no Magisk, no build.prop edits etc., ...Nothing.
Use fastboot to flash your factory images you downloaded. You can use the flash all bat file or individually flash each separate. Again it's all covered in the link I posted above.
Also, what do you mean you couldn't wipe/reset from stock recovery? When you flash stock recovery and boot to it, you will see an Android on its back with an exclamation mark in a red triangle. You may or may not see text that reads "No Command". Either way, from that point hold down the power button and then press and release volume up. You will boot to stock recovery where you can wipe your data.
Not for nothing, but as mentioned above, people have hard bricked their 6P from locking bootloader's on combos besides stock. You got extremely lucky you didn't as well. Please take some time to read and fully understand what you're doing with your ~600$ device.
This is also, for the most part, pretty standard stuff as far as flashing / modding goes. At least since 2010 when I got into it. If you want to know the exact string of fastboot commands please read and use the guide I linked. It teaches you literally everything. There's nothing it doesn't cover and once you get used to it you will never use a toolkit again.
Hope I didn't come off rude, but basically since 2010 when I got into this across all my devices I try to help out in the Q+A sections. I've probably participated in hundreds and hundreds of "help, I used a toolkit and my phone is bricked and I have no idea how to fix it, I just wanted cool stuff on my phone" threads. They're absolutely 100% not worth the trouble and headaches from them. Especially if you have no idea what they're doing on the back end. Know Fastboot and ADB like the back of your hand and just prefer to use them? That's a different story, if something fails then you fix it yourself in 10 seconds. But for the love of God, please please please please please stop using toolkits if you don't know how to fix issues on your own. You will eventually hard brick. I've seen it happen dozens of times. Thread turns into a circlej*rk about whether toolkits are bad or not, OP hard bricks their phone and commits fraud, which is illegal by trying to RMA it. Just don't use them. It's simple enough without them. Why reinvent the wheel when it works just fine?
Click to expand...
Click to collapse
I ended up using fastboot to flash factory. I then re locked bootloader and everything booted without and issue. I was happy about that. I re rooted and everything is working great. :good:
I can say I learned a lot from this experience. Thanks to everyone for your advice. I am now comfortable using the fastboot method. Almost bricking my phone was scary but it taught me a lesson. Cheers everyone.

Categories

Resources