Need Help - Shield 2015 16GB no booting anymore - Shield Android TV Q&A, Help & Troubleshooting

To start at the beginning.
The shield was running flawless unitl I got the Update to nougat. After that all the time network (LAN) crashed and even my router got problems. This just happened when the shield was on. Without everything was fine. The shield lost all the time the IP adress provided from the router. Setting it to static was not much better.
I decided to make a recovery flash as descripted here, because I thought the update crashed somehow.
https://developer.nvidia.com/gameworksdownload
I just made those changes which are written in the instructions. Everything seems to worked out. Files were copied and flashed.
After the reboot command. I just get a black screen. Nothing happens. I can load fastboot again with no problem, but the OS will not boot. Unpluging doesn't help either. Tried a different tv too. Still black screen
I even locked the bootloader again.
Can somebody please help me to get the shield fixed?

Did you use the flash-all.bat script?
If so then try to flash each part manually using these commands in fastboot. Do not reboot device until you flashed all those img files.
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot reboot
Funky-Fab-4Strings said:
To start at the beginning.
The shield was running flawless unitl I got the Update to nougat. After that all the time network (LAN) crashed and even my router got problems. This just happened when the shield was on. Without everything was fine. The shield lost all the time the IP adress provided from the router. Setting it to static was not much better.
I decided to make a recovery flash as descripted here, because I thought the update crashed somehow.
https://developer.nvidia.com/gameworksdownload
I just made those changes which are written in the instructions. Everything seems to worked out. Files were copied and flashed.
After the reboot command. I just get a black screen. Nothing happens. I can load fastboot again with no problem, but the OS will not boot. Unpluging doesn't help either. Tried a different tv too. Still black screen
I even locked the bootloader again.
Can somebody please help me to get the shield fixed?
Click to expand...
Click to collapse

Yes i did all parts manually. Dont even know there is a flash all script. I followede the instructions in nvidia page.

Same thing happened to me.
However mine will not flash the boot.img it just hangs

so you dont have any boot at all? You still get into fastboot???

Just an FYI I got mine RMA'd by Nvidia, I had to go through the chat and do all the fixes, none worked so I had to dig up the receipt, take a pic of the serial # and give them my tv model number. Pretty painless overall. Should get replacement in 3 days.

I just got contact to nvidia too. Hope they gonna rma mine too.

Just got the instructions for rma via E-Mail and already sent all documenta back.

I had the same issue, did the chat, was told I'm getting RMa'd but for two days now there has been no further discussions or emails. Did your Rma confirmation take a bit to come? thanks

Didn't get anything back until now. Keep fingers crossed

when you submitted receipt and sn / pn, did you change to Do you want a response? I had originally put no. Also its more like 4 days now.

I just got all information via E-Mail. It was an offline chat Mord less. Nvidia just wrote me back in this second. The guy passes everything over to their waranty Departement and will get back to me after he has some news.
Edit. Just got my rma documenta and shopping label.

I did mine through the chat and got an email today that they are sending mine out.
We value you as a customer and for your convenience; I have raised an advance replacement of the device, meaning you'll be receiving the replacement unit before you have to send back the defective to us. We'll also provide you with a prepaid shipping label to send the defective back to us.
I would go through the chat rather than email. I also filled out the survey after the chat and gave glowing remarks about my rep I think that helped speed up the process.

AS mentioned. Got my shipping Labels already but i have to send it out first i guess. Worst thing is FedEx is 50 km away Form my place to drop it off.

chrissurra said:
I did mine through the chat and got an email today that they are sending mine out.
We value you as a customer and for your convenience; I have raised an advance replacement of the device, meaning you'll be receiving the replacement unit before you have to send back the defective to us. We'll also provide you with a prepaid shipping label to send the defective back to us.
I would go through the chat rather than email. I also filled out the survey after the chat and gave glowing remarks about my rep I think that helped speed up the process.
Click to expand...
Click to collapse
when did you start the chat? Its now 4 days with nothing further in comments other then he said he would rma.

I did my chat yesterday and it was shipped today I will receive it next Tuesday. Very simple process.
Heres the link I used:
http://nvidia.custhelp.com/app/chat/chat_launch/session/L3RpbWUvMTQ4NTkxMzE4My9zaWQvTFBXb1o1YW4=

maybe you flashed something incorrect ... but then locked the bootloader. the bootloader should never be locked when there is file corruption because the only way to fix it is by unlocking the bootloader and flashing. but if its locked and fried your screwed.
maybe you locked it for rma

So I got a new or refurbished Shield today. I set everything up and now I am back at my first problem before i tried to flash a recovery rom with my old shield.
The unit always loosing ethernet network connection. It says its connected, but no internet. The funny thing is, that I updated the software via the same line. to 3.3 and then to 5.0(2). So the Internet is working fine on other devices with the same wire.
Maybe it just starts when i install kodi... but why? My old Shield was running just fine with kodi and Software 3.3.
Any ideas?

Related

Balance's Bell I9000M Internal Storage Fail?

sigh brought phone since Aug 2010, always thought I was a lucky one with no internal SD problems
Jan. 11/ 2011 my SGS officially dies
Aug 2010 - Jan. 11/2011 I remember having to go to store to store to find a SGS with a working recovery/downloading mode
so whats the fastest process in getting your phone fix?
deal with bell or future tel directly?
is bell still offering the $100
I remember a year back I try to get a 2 year old phone fix by bell, bell would charge me "fees"
call future tel directly, they had a UPS box sent to my door step ship to them for a quote, if I decide to not have it fix, they would send me the phone back no charges
mobo version 10.08
today at work pull out my phone saw black screen after trying to wake it still no response so pull out battery (had to do this a few times before) this time when it boot it was logo boot loop, couldn't enter recovery mode but download mode works
come home try to flash with JL2, try the jm9 from DOC's thread boots into recovery with can't mount SD card
Click to expand...
Click to collapse
So I been rage flashing like crazy
some how I was successful in somehow getting the recovery back on and then installing speedmod-kernel-k12k-500hz with Clockworkmod recovery
disable the lag fix? try to reformat still does not work but.. I was some how able to boot pass the S Logo Check internal storage shows nothing still can make call LOL
tonight I try lots of combos Odin1.0, 1.3, 1.7 (1.7 seems to do the job)
I tried JM9 from Doc's thread, I9000UGJH2, I9000UGJG8 I9000XXJPU.exe
After lots of Odin flash the phone would logo try to restart and you can see it trying to load the battery charging icon with USB connected or Logo boot loop, I didn't understand that you HAD to pull out the battery when odin said reset or else you couldnt boot the recovery mode, download mode always work
lets seem if i can install dark's rom lol
so try to flash with JL2...
in the logo boot loop again...
After lots of Odin flash the phone would logo try to restart and you can see it trying to load the battery charging icon with USB connected or Logo boot loop, I didn't understand that you HAD to pull out the battery when odin said reset or else you couldnt boot the recovery mode, download mode always work
Click to expand...
Click to collapse
It's dead. Flash a stock JL2 and call it in to Bell.
No one has been able to recover from that error message. The best you'll get is booting into Android with no internal/external memory available.
gtg2 said:
It's dead. Flash a stock JL2 and call it in to Bell.
No one has been able to recover from that error message. The best you'll get is booting into Android with no internal/external memory available.
Click to expand...
Click to collapse
Agreed. If you are a Bell customer, call up tech support and tell them your problem (Don't mention flashing, kernels... ect.) and say your phone died while upgrading to Android 2.2 - from there you should expect a $100 credit and the rep to start the replacement/repair process. Good Luck!
you can also call Samsung directly to get your UPS shipping label
then you can send in your phone for direct replacement
AllGamer said:
you can also call Samsung directly to get your UPS shipping label
then you can send in your phone for direct replacement
Click to expand...
Click to collapse
The latest I have read is that most phones are not getting replaced but just having the motherboard replaced.. Mind you I hope YOU are right since mine is in for repair right now lol.
most people that received their phone back either from Bell or Samsung, got a new IMEI # and new phone
or in the worse case scenario, you get your old phone back same IMEI with a new motherboard
called bell tech support
rep got me setup for a replacement
asked them should I bring my phone to the store and he said "they have been order to do phone replacement and not to redirect to any store and 100 credit to my account for all the trouble"
also ask if they're doing repairs and he said from what he was told they're suppose to do replacement only
update on my status
I don't know if either I'm sure lucky or Bell is awesome
Call Bell Wednesday received replacement phone today (Friday)
Its a 10.12 brand new phone, comes with all its original accessories (I read somewhere that you only get the phone in bubble wrap)
You have to return the defective phone by 5 Business days, with original battery and charger, also it states if failure is due to client damages there could be $499 repair charge and if not return by 5 business days will be charged full value of the devices.
This process was painless!
Many thanks to arr0ww for his hard work in getting us (I9000M owners) compensation and making this super easy thank him here -> http://forum.xda-developers.com/showthread.php?t=883820
Also many thanks to gtg2 for his replacement information and steps thank him here -> http://forum.xda-developers.com/showthread.php?t=894025
Also thank AllGamer for keeping up dated on I9000M news thank him here -> http://forum.xda-developers.com/showthread.php?t=886158
And other user for posting their status and testing results XDA FTW!!!
now I will let my phone warm up a bit and let the flashing beginning!!!!!

Nexus 7 Bricked, No response

Ok well skip this first part if you don't want a story,
I got my nexus around febuary as a gift for my birthday as a little toy and music, I went right ahead and unlocked the bootloader and rooted it for future use as well as going ahead and putting TWRP on it with multirom for ubuntu tinkering but never bothered flashing a new android and only flashed a new kernal to be able to tweek the clock speeds and never bothered with that ether becuase the nexus was fast enfough for everything i could throw at it.
Now a few days ago I decided to do a factory reset from TWRP to put a stock rom on it and clean everything off it, Then it just refused to boot BUT i still had bootloader access so all was well and i used the lazy option and oppted to use the nexus toolkit and told it to just flash the stock rom onto it. It finished then i went to restart it and it died.
Now since that death it will not boot, it will not get to the bootloader or recovery menu, it wont respond to any buttons at all, It won't dispaly the chargeing icon when pluged it nor will the screen turn on at all and to top it all off even when i plug it into my laptop it will not even notace it at all.
I have seen simlar problems but none exactly the same, I tryed to return it today but to put it lightly pc world are a bunch of asshats who woudent exchange or repair it becuase the receipt was slightly damaged so returning it isent an option.
Feel free to call me an idiot and everything but for any help at all I thank you in advance.
You should still be covered under the 12 month warranty from Asus with the warranty card you got along with your device.
Username invalid said:
You should still be covered under the 12 month warranty from Asus with the warranty card you got along with your device.
Click to expand...
Click to collapse
Will they not not just tell me to go to the resaler?
My headset from asus broke and they told me I had to set up the rma with the online resaler i bought it from here.
There's no harm in atleast going to the Asus website and make an account then register your tablet.
Username invalid said:
There's no harm in atleast going to the Asus website and make an account then register your tablet.
Click to expand...
Click to collapse
I've done so now, but I hold no hope with the support asus offers

[Q] Nexus 7 bricked

Hi guys, I'm having what looks like a big problem on my Nexus 7 (2012). I've tried to flash the stock 4.4 on it, since I already did that with 4.3. Followed all the instructions on a thread posted here: http://forum.xda-developers.com/showthread.php?t=1907796
When i made it to the final step, the screen turned off, but instead of rebooting, it got stuck in black screen. I've tried to enter fastboot, but it doesn't respond... Any suggestions?
Is the backlight on and just the screen black? If so I would try adb commands.
Sent from my Nexus 7 using Tapatalk
brndnddge said:
Is the backlight on and just the screen black? If so I would try adb commands.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
The screen is completely off, doesn´t respond to any combination of buttons, whether to turn on, access fastboot... I've tried adb, but the devices isn't listed in adb devices
I still have a nandroid backup, but I'm not even sure how to use it, since the Nexus doesn't respond connected through usb
Try plugging the N7 into its OEM charger for a little while, then discoonect - hold Volume Down button & press Power button for at least 15 to 30 seconds, a minute or so if necessary to see if it will boot back into bootloader and/or recovery.
It had unlocked bootloader, rooted and which recovery did you have - CWM or TWRP ?
Do you have a spare / different PC or borrow one - plug it in with the oem cable, does it beep or install drivers - see the N7 ??
Letitride said:
Try plugging the N7 into its OEM charger for a little while, then discoonect - hold Volume Down button & press Power button for at least 15 to 30 seconds, a minute or so if necessary to see if it will boot back into bootloader and/or recovery.
It had unlocked bootloader, rooted and which recovery did you have - CWM or TWRP ?
Do you have a spare / different PC or borrow one - plug it in with the oem cable, does it beep or install drivers - see the N7 ??
Click to expand...
Click to collapse
Just tried that, still doen't respond it had unlocked bootloader, rooted and with CWM as recovery.
I'm gonna try with a different PC, and I'll let you know.
Thanks
Carvalheira24 said:
Just tried that, still doen't respond it had unlocked bootloader, rooted and with CWM as recovery.
I'm gonna try with a different PC, and I'll let you know.
Thanks
Click to expand...
Click to collapse
I'm in the EXACT same boat. No screen and it won't get recognized by the PC anymore. I think it's bricked.
I have an RMA number but I don't know if I should send it in because they might come back say it was "modified" (unlocked bootloader). Hopefully, they can't tell and will just replace it. I don't care about the data. I backed it up before this all happened because I was going to go bac to 4.3 (Kit Kat broke flash video streaming so I was going back to 4.3).
Well, they apparently replaced the motherboard and it's in a "SHIP" status, but it's been that way since Thanksgiving week. Haven't received an email from them stating it's shipped, so I have no way of tracking it.
When I contacted support about it, that's when they told me the motherboard was replaced and they shipped it out, but they didn't give me a shipping date. I emailed them back about getting a tracking number, etc. Have yet to hear back from them. They have a slow turn around on email/support questions (48+ hours it seems).
Just hope I get it back soon.
iBolski said:
Well, they apparently replaced the motherboard and it's in a "SHIP" status, but it's been that way since Thanksgiving week. Haven't received an email from them stating it's shipped, so I have no way of tracking it.
When I contacted support about it, that's when they told me the motherboard was replaced and they shipped it out, but they didn't give me a shipping date. I emailed them back about getting a tracking number, etc. Have yet to hear back from them. They have a slow turn around on email/support questions (48+ hours it seems).
Just hope I get it back soon.
Click to expand...
Click to collapse
Looks like I also have to send it, also hope they don't care about the bootloader being modified or not... Good luck with yours too
Cheers
Carvalheira24 said:
Looks like I also have to send it, also hope they don't care about the bootloader being modified or not... Good luck with yours too
Cheers
Click to expand...
Click to collapse
Just got the email from them that it was shipped and it has already arrived at my place of employment as of today. Now just waiting for the mail room to deliver it. Hurry up!!!
UPDATE: Finally. At about 11:30 am EST the mail room delivered my repaired Nexus 7. Now I just have to get it updated and restore my backup.
iBolski said:
Just got the email from them that it was shipped and it has already arrived at my place of employment as of today. Now just waiting for the mail room to deliver it. Hurry up!!!
UPDATE: Finally. At about 11:30 am EST the mail room delivered my repaired Nexus 7. Now I just have to get it updated and restore my backup.
Click to expand...
Click to collapse
This is excellent to read!! Just RMA'd mine and was worried they wouldn't fix because of mods. ASUS status shows "repair" so I am hopeful for a working N7 in a couple weeks. Thanks.
D3KT said:
This is excellent to read!! Just RMA'd mine and was worried they wouldn't fix because of mods. ASUS status shows "repair" so I am hopeful for a working N7 in a couple weeks. Thanks.
Click to expand...
Click to collapse
Looks like you'll be good to go then. With mine, you couldn't even get the Nexus logo to show up. Nothing ever came on the screen. In fact, I never saw the screen flash like it does when you hold power+vol up+vol down to reset it, so I think with mine, they couldn't tell I unlocked the BL.
In any case, the new machine is running fine with the new motherboard, but I can't restore my backup from my previous tablet. I did the backup with the N7 toolkit, but the /data backup won't restore. Logcat shows something about a key not being found or not being matched so it just aborts.
I'm wondering if when I did the backup on my previous machine, if it generated a key based off of something on my previous N7 motherboard, like the serial number? So, when it tries to restore the backup, it generates the key based off of the NEW motherboard which won't match with the key in the .tar backup? Is there a way to tell it to SKIP checking the key?
I just don't know. Anyways, glad to see yours is getting repaired. Hopefully, mine lasts a good long time before it dies out. My warranty expires next month in January as that will be a year from when I purchased it.
Love my tablet.

Random boot loop, can't get anywhere in recovery

I was on the latest CM13 nightly (was waiting a bit to go to 14.1) So I went to bed last night and my phone did a reboot as I was setting my alarm. Didn't think too much of it, crap happens. I waited for it to come back fully into the OS, which it did, checked my alarm. Noticed something strange I got the CM Updater notification in the statusbar ("There are new updates available" - CM14.1-12-02 or something), which I thought was weird that's the first time it's said that, and I've checked the CM Updater before and since the 14.1 switch there's been nothing there. As it should, I imagine, not try to update major versions like that. Anyways I dismissed it and went to bed (this entire thing is PROBABLY entirely unrelated, but I found it's timing interesting at least).
Woke up a few hours later to my phone getting really hot, and stuck in an infinite boot loop. It never gets passed the first Google screen. If I let it go it'll sit there for several minutes and maybe reboot. I was able to get into the bootloader, choosing Boot Recovery though sends me back to the Google bootup screen where it never progresses, doesnt have the blue text in the top that says booting into recovery..
Was able to get into the phone with fastboot so I tried flashing the latest recovery I had installed TWRP-3.0.2-2-angler. Still wouldn't boot into it, sometimes it would get to the TWRP recovery loading page, and then sit there for a couple minutes, then reboot.Tried flashing it a few times with fastboot with no success.
Erased userdata with fastboot, then did a full factory reflash of several images, MDB081 - MTC20l (factory images I know I've used in the past to recover, had them saved). Rebooted and I still can't get into the OS (stuck at first Google logo). Interesting the stock recovery though loads.
Flash an older TWRP recovery I had saved twrp-2.8.7.2-angler . Was able to get into recovery finally - kind of. Sometimes it still locks up and wont let me swipe to enter TWRP. The first time it let me in it asked me for my decryption password - I didn't have a password - had a swipe and fingerprint setup only. Got in again and first thing I tried doing honestly is erasing (formating) all my data, thinking if I'm going to have to warranty this phone or sell it broken, I want to make sure my data is wiped. Also I figure after that I can try to reinstall CM etc like I would a completely fresh build. It complained about not being able to mount the partition and locked up in TWRP then eventually auto rebooted. Got in again and tried to do a basic wipe, it said it cant find /sdcard then said it wiped, and then froze, auto rebooted again after a few seconds.
To note : All fastboot commands seem to execute with "OKAY" status, no errors reported anywhere, it always finds the device too.
I can't seem to get anywhere with this phone. Everything I try to do in recovery is met with freezes and reboots. It seems like maybe the internal emmc has taken a dump.
Problem is I'm literally 3 days out of the 1 year warranty from when I received my phone, and having tried to work with Huawei support previously, I'm 100% certain they won't help. I came across a few threads on here similar to mine recently without any real resolution other then RMA'ing it. I figured I'd post here for a last desperate attempt if anyone has any other suggestions, because I don't know what I'll do. The Pixel XL is ungodly expensive, and conveniently out of stock. And I don't think I could talk myself into buying another Huawei anytime soon after this.
Any suggestions?
the.root said:
I was on the latest CM13 nightly (was waiting a bit to go to 14.1) So I went to bed last night and my phone did a reboot as I was setting my alarm. Didn't think too much of it, crap happens. I waited for it to come back fully into the OS, which it did, checked my alarm. Noticed something strange I got the CM Updater notification in the statusbar ("There are new updates available" - CM14.1-12-02 or something), which I thought was weird that's the first time it's said that, and I've checked the CM Updater before and since the 14.1 switch there's been nothing there. As it should, I imagine, not try to update major versions like that. Anyways I dismissed it and went to bed (this entire thing is PROBABLY entirely unrelated, but I found it's timing interesting at least).
Woke up a few hours later to my phone getting really hot, and stuck in an infinite boot loop. It never gets passed the first Google screen. If I let it go it'll sit there for several minutes and maybe reboot. I was able to get into the bootloader, choosing Boot Recovery though sends me back to the Google bootup screen where it never progresses, doesnt have the blue text in the top that says booting into recovery..
Was able to get into the phone with fastboot so I tried flashing the latest recovery I had installed TWRP-3.0.2-2-angler. Still wouldn't boot into it, sometimes it would get to the TWRP recovery loading page, and then sit there for a couple minutes, then reboot.Tried flashing it a few times with fastboot with no success.
Erased userdata with fastboot, then did a full factory reflash of several images, MDB081 - MTC20l (factory images I know I've used in the past to recover, had them saved). Rebooted and I still can't get into the OS (stuck at first Google logo). Interesting the stock recovery though loads.
Flash an older TWRP recovery I had saved twrp-2.8.7.2-angler . Was able to get into recovery finally - kind of. Sometimes it still locks up and wont let me swipe to enter TWRP. The first time it let me in it asked me for my decryption password - I didn't have a password - had a swipe and fingerprint setup only. Got in again and first thing I tried doing honestly is erasing (formating) all my data, thinking if I'm going to have to warranty this phone or sell it broken, I want to make sure my data is wiped. Also I figure after that I can try to reinstall CM etc like I would a completely fresh build. It complained about not being able to mount the partition and locked up in TWRP then eventually auto rebooted. Got in again and tried to do a basic wipe, it said it cant find /sdcard then said it wiped, and then froze, auto rebooted again after a few seconds.
To note : All fastboot commands seem to execute with "OKAY" status, no errors reported anywhere, it always finds the device too.
I can't seem to get anywhere with this phone. Everything I try to do in recovery is met with freezes and reboots. It seems like maybe the internal emmc has taken a dump.
Problem is I'm literally 3 days out of the 1 year warranty from when I received my phone, and having tried to work with Huawei support previously, I'm 100% certain they won't help. I came across a few threads on here similar to mine recently without any real resolution other then RMA'ing it. I figured I'd post here for a last desperate attempt if anyone has any other suggestions, because I don't know what I'll do. The Pixel XL is ungodly expensive, and conveniently out of stock. And I don't think I could talk myself into buying another Huawei anytime soon after this.
Any suggestions?
Click to expand...
Click to collapse
It's an ongoing thing with these 6P's and 5X's. Some have been able to fully recover and others like myself were not. Here is a guide that might be able to help you if you haven't come across it yet. Good luck..
http://forum.xda-developers.com/android/help/guide-revive-angler-bootloop-t3454938/page6
Check Warranty Status:
http://consumer.huawei.com/us/support/warranty-query/index.htm
BIGSAMDA1ST said:
It's an ongoing thing with these 6P's and 5X's. Some have been able to fully recover and others like myself were not. Here is a guide that might be able to help you if you haven't come across it yet. Good luck..
http://forum.xda-developers.com/android/help/guide-revive-angler-bootloop-t3454938/page6
Check Warranty Status:
http://consumer.huawei.com/us/support/warranty-query/index.htm
Click to expand...
Click to collapse
Thanks. I came across that. I tried flashing MMB29P as well as several other factory images without success. My problem now it seems no matter what I flash I cannot get back into recovery anymore. Even if it's stock or if it's TWRP (any version - including 3.0.2.0 as they suggest), so I don't really get passed step 4-5 in that guide. I guess she only had so many reads left in her, sigh.
WEIRD @ warranty link. It says from my S/N that it's valid until 2017-02-17. I don't know how, I purchased it 2015-10-22, it shipped 2015-11-24, and I got it 2015-11-30. Unsure how/why that would've gotten extended until February. I'm concerned they'll get it back then deny it once they figure that out, or figure out it's been unlocked/flashed. When I first got the phone i had issues with it charging, I narrowed it down to the USB C->C cable being faulty, and contacted Huawei. They absolutely refused to replace just the cable. Said I had to ship the whole phone back and it'd take AT LEAST 3-4 weeks to get it back. I argued with several people on the phone there (their support 100% refuses to give you their name or transfer to their supervisors btw), and finally asked google support to pull some strings and get in contact with someone there to replace a simple freaking cable - no one cared at all - spent several hours trying and got nowhere. I'm /done with Huawei. I think my best bet is to probably find out how well that American Express extended warranty claim works, I've never actually had to use it before. IDK what I'll do after that. Sad this is a common problem with these phones exactly one year out, so even if I wanted to buy a used one on eBay I'd risk the same thing shortly thereafter.
I'll keep the phone powered off for a while and try some more flashing later see if I can get back into recovery to try the rest of his steps in that article. It's not looking promising anymore.
Well being that it's a known issue, like I said, I myself ran into this fiasco, had phone rooted and running custom rom. I myself couldn't get into recovery but was able to flash all factory images and relock bootloader manually. I then called Huawei and played dumb telling them that I had updated my phone to the latest firmware via OTA and then it went into bootloop. They never asked if it was unlocked and I never volunteered to tell them either. I had bought my 6P through Best Buy and still had receipt Incase they'd asked for it which they didn't. All they did was ask for IMEI # along with Ser # and verified that it was still under warranty, then they emailed me a return label. I shipped phone to them and in a matter of like a week or so I had a brand new device in hand. Build date on it was August, 16, 2016. So far running good but let's see for how long.
BIGSAMDA1ST said:
Well being that it's a known issue, like I said, I myself ran into this fiasco, had phone rooted and running custom rom. I myself couldn't get into recovery but was able to flash all factory images and relock bootloader manually. I then called Huawei and played dumb telling them that I had updated my phone to the latest firmware via OTA and then it went into bootloop. They never asked if it was unlocked and I never volunteered to tell them either. I had bought my 6P through Best Buy and still had receipt Incase they'd asked for it which they didn't. All they did was ask for IMEI # along with Ser # and verified that it was still under warranty, then they emailed me a return label. I shipped phone to them and in a matter of like a week or so I had a brand new device in hand. Build date on it was August, 16, 2016. So far running good but let's see for how long.
Click to expand...
Click to collapse
Hmm interesting. Maybe their US support has improved since last year. So it was brand new not refurbished? Did you get the full retail box set? I bought mine directly through Huawei, so I would like to think that they would have accurate warranty data, but perhaps not. I will consider RMA'ing it to them if it's really a new one. It's either that or a 550$ refund from my credit card company. I haven't tried fastboot lock yet, will do that when I give up on all else lol (and need to return it), but hopefully that will work if the rest of the emmc is hosed.
Yeah, mine came in a new box, sealed like day one. I was surprised thought I'd be getting a refurbished device but I can honestly say it was a brand new one. And I don't blame you on trying to get the device to a working state. I tried everything and it's mother before giving up and finally relocking bootloader and sending it in.
BIGSAMDA1ST said:
Yeah, mine came in a new box, sealed like day one. I was surprised thought I'd be getting a refurbished device but I can honestly say it was a brand new one. And I don't blame you on trying to get the device to a working state. I tried everything and it's mother before giving up and finally relocking bootloader and sending it in.
Click to expand...
Click to collapse
Just called them. They won't accept it back without a proof of purchase. I have to send in the proof of purchase before they'll approve the RMA and then I get the shipping label/information. And "they can't look it up by S/N, doesn't matter if the website says it's in warranty". LOL. Sounds about right from what I remember of their support. They say their website is inaccurate, and cant ever verify/lookup that I bought the product directly from them. Maybe I'll try back tomorrow to see if someone else will help but it's unlikely from the sounds of it. She did say this is very common problem however, knew all about it.
Damn, That truly sucks..I would definitely give them a call again and see if I get a different rep. I was lucky with the one I got, he basically knew it was an ongoing thing and really didn't give me a hard time. He didn't even ask for a receipt, about the only thing he asked was that if the bootloader was locked or unlocked and when I told him it was locked, he then proceeded with the RMA procedure.
BIGSAMDA1ST said:
Damn, That truly sucks..I would definitely give them a call again and see if I get a different rep. I was lucky with the one I got, he basically knew it was an ongoing thing and really didn't give me a hard time. He didn't even ask for a receipt, about the only thing he asked was that if the bootloader was locked or unlocked and when I told him it was locked, he then proceeded with the RMA procedure.
Click to expand...
Click to collapse
Yeah I played dumb and all, didn't help. She didn't ask me any real questions she was convinced of the problem just from my description. She also said it's 12 months from the date I purchased it and not when I received it in the mail (so since they took 5-6 weeks to get it to me - preorder madness - I don't get that time back in the warranty) lol. Not like it matters now, just to further comment on how crappy their support/warranty is (in my experience).
I'll follow up if I have any more luck unbricking the device or warrantying it for that matter.
Good luck on either with the warranty or bringing it back to life.
I also have problems such as your support Huawei says four weeks of waiting
Got a recovery image to boot finally (after like 10x attempts at flashing one). Tried doing the nandroid backup as that guide suggests, says it cannot find/mount /sdcard and freezes/reboots. Tried going into wipe -> advanced and repairing internal storage and data and it was an invalid partition or something. Tried repairing system and it locked up again. Tried formatting them with fastboot and didn't work. Tried installing the latest 7.0 factory image for the hell of it, nadda. Relocked the bootloader successfully. Giving up. Filed an claim online with my credit card company (most do a +1 year extended warranty), we'll see how that goes, if I get lucky they'll approve the claim and let me keep the phone. May pick up a used 5x or something.
the.root said:
Got a recovery image to boot finally (after like 10x attempts at flashing one). Tried doing the nandroid backup as that guide suggests, says it cannot find/mount /sdcard and freezes/reboots. Tried going into wipe -> advanced and repairing internal storage and data and it was an invalid partition or something. Tried repairing system and it locked up again. Tried formatting them with fastboot and didn't work. Tried installing the latest 7.0 factory image for the hell of it, nadda. Relocked the bootloader successfully. Giving up. Filed an claim online with my credit card company (most do a +1 year extended warranty), we'll see how that goes, if I get lucky they'll approve the claim and let me keep the phone. May pick up a used 5x or something.
Click to expand...
Click to collapse
I would stay away from the 5X as well..lol They are going through the same thing the 6P is going through. It's all over Reddit and XDA as well. I'm currently using the 6P but I'm waiting on the One Plus 3T to arrive. I have a few other devices to play with but I'm still using the 6P waiting for the 7.1.1 update to drop in a few days to see how that goes.
BIGSAMDA1ST said:
I would stay away from the 5X as well..lol They are going through the same thing the 6P is going through. It's all over Reddit and XDA as well. I'm currently using the 6P but I'm waiting on the One Plus 3T to arrive. I have a few other devices to play with but I'm still using the 6P waiting for the 7.1.1 update to drop in a few days to see how that goes.
Click to expand...
Click to collapse
Oh what the **** . That sucks. My wife owns a 6P and my son has a 5x. So our house is a ticking time bomb of failure. Maybe I'll buy a Note 7 and finish the job. I have my old Nexus One and Tmobile G1, both still power on last time I checked. I've gotten rid of all other past cell phones we've had unfortunately. Used to have so much trust in the Nexus lineup
the.root said:
Oh what the **** . That sucks. My wife owns a 6P and my son has a 5x. So our house is a ticking time bomb of failure. Maybe I'll buy a Note 7 and finish the job. I have my old Nexus One and Tmobile G1, both still power on last time I checked. I've gotten rid of all other past cell phones we've had unfortunately. Used to have so much trust in the Nexus lineup
Click to expand...
Click to collapse
Lmao.. Yeah I would stay away. Also you have to throw in the fact that the devices only have support until at least Sept. of 2017, then unless you're flashing custom roms your basically stuck.
BIGSAMDA1ST said:
Lmao.. Yeah I would stay away. Also you have to throw in the fact that the devices only have support until at least Sept. of 2017, then unless you're flashing custom roms your basically stuck.
Click to expand...
Click to collapse
Yeah I mean I've always liked the Nexus devices because they always seem to have a good strong developer/modding community. I don't know the definition of a stock - anything. I recently converted my wife & son over to Nexus from Samsung's because I got frustrated with how they now lock down their phones. I have no doubt the 6P/5x (if they survive that long lol) will still be one of primary devices in this community to receive new OS/etc (cyanogenmod/whatever) well past the September EOL. Just look at the older Nexus phones still some of the first to receive the CM14.1 builds.
the.root said:
Yeah I mean I've always liked the Nexus devices because they always seem to have a good strong developer/modding community. I don't know the definition of a stock - anything. I recently converted my wife & son over to Nexus from Samsung's because I got frustrated with how they now lock down their phones. I have no doubt the 6P/5x (if they survive that long lol) will still be one of primary devices in this community to receive new OS/etc (cyanogenmod/whatever) well past the September EOL. Just look at the older Nexus phones still some of the first to receive the CM14.1 builds.
Click to expand...
Click to collapse
Exactly.. That's why I'm still keeping mine and hoping it doesn't decide to go on the fritz again.

Endless bootloop on nexus 6p

Hi!
I was using my phone normally, then it suddenly switched off. I got the corrupted data message as I always do when booting up. Then the Google logo came with the "Unlocked" sign under. Then the screen turns black for a few seconds before starting over. It does this endlessly. I am able to get into Fastboot mode, but from here I can't access Recovery mode. When I tried this, it continues with the first bootloop.
I've tried to "fastboot erase" everything from the fastboot screen, and flashing everything over again. This does not work. I've tried using Nexus Root Toolkit, which does not work.
I'm really lost here, and would appreciate if someone could help me out.
I feel that I've tried everything
I'm afraid you're going to have to RMA your device. I fell
victim to this also and tried everything there is to try and get it fixed but no go. Had to RMA after all the troubleshooting methods did not bring it back to life. This is an ongoing condition with the 6P's and 5X's as well. I'll give you a link you can check out.
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page41
BIGSAMDA1ST said:
I'm afraid you're going to have to RMA your device. I fell
victim to this also and tried everything there is to try and get it fixed but no go. Had to RMA after all the troubleshooting methods did not bring it back to life. This is an ongoing condition with the 6P's and 5X's as well. I'll give you a link you can check out.
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page41
Click to expand...
Click to collapse
Thanks!
What is RMA? Could I get a detailed instruciton on how to fix it, or is it unfixable? How does two year warranty from google work when I bought it from a reseller such as Telia? (I live in Norway) Do I get a completely new device from Google? I've rooted but am able to relock the bootloader. Will this get through the warranty thing?
Thanks again!
RMA is a Return Merchandise Authorization.. Now you live in Norway, I really don't know what the process is for you out there and also you might need to have a proof of purchase receipt to get an RMA under warranty. I would contact Google if that's where the device was purchased and be guided by them.
Edit: I just realized you said you got it from Telia. I would contact them and be guided by them. If all fails then contact Google, although I don't know how much help they would be.
BIGSAMDA1ST said:
RMA is a Return Merchandise Authorization.. Now you live in Norway, I really don't know what the process is for you out there and also you might need to have a proof of purchase receipt to get an RMA under warranty. I would contact Google if that's where the device was purchased and be guided by them.
Edit: I just realized you said you got it from Telia. I would contact them and be guided by them. If all fails then contact Google, although I don't know how much help they would be.
Click to expand...
Click to collapse
Thank you! I will try this when they open up tomorrow!
[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

Categories

Resources