Related
My phone is bootlooping and I can't access recovery. I can't restore the phone's stock software because I edited build.prop and it's not showing up as a Verizon phone. I decided to bite the bullet and just pay LG to reset it. However, when I contacted them to do this they told me I need to mail the phone in and they will tell me how much it costs after their tech looks at it. I'm worried if I do this that they'll charge me an exorbitant amount to fix it... Does anyone have any idea how much they usually charge to do this?
Sending the phone off to LG should be your last resort. It sounds like you've not tried everything!
Send it in to warranty. As long as there's no physical damage Verizon isn't going to give a rats a$$
06stang said:
Send it in to warranty. As long as there's no physical damage Verizon isn't going to give a rats a$$
Click to expand...
Click to collapse
Well, in another thread a Sprint tech said that LG did not give them a method to flash the stock software if the model check failed. I assumed this was the case for Verizon as well. I'll call them tomorrow and ask, I may have misunderstood what he wrote. I can't seem to find his post now. I'll update this post after work tomorrow if they can recover the phone.
theoneofgod, what is it that you think I haven't tried yet? If you have a suggestion which would save me the trouble of sending this phone in I would be super happy. To recap, here's what I've tried:
1. Using hard keys to factory reset (on TWRP 2.6.3.1 so it actually factory resets instead of booting into recovery)
2. Hitting "adb reboot recovery" over and over as TWRP loads and performs factory reset (this worked for people on 2.6.3.1 on AT&T but doesn't seem to be working on my Verizon phone for some reason. I've tried it dozens of times and even wrote a batch file which spams "adb reboot recovery" many, many times faster than I could type it)
3. Flashing the .tot file through download mode (Model check fails)
4. Flashing the .kdz file through download mode (Hangs at either 4% or 10% and asks me to restart. Never gets past 10%)
5. Entering my IMEI into the LG update tool, letting it download the software for the phone, and letting it try to flash the software (it fails)
What was the reason for bootloop? i also change my model name to make camera app show pics in menu, but it didn't help, and i returned to stock build.prop. So whats your story? Its good to know what i should NOT do with the phone.
Yea a good idea if you share what you've done so readers can be aware of it. Goodluck to your G2 pal and we're sorry for you..
marshygeek said:
Yea a good idea if you share what you've done so readers can be aware of it. Goodluck to your G2 pal and we're sorry for you..
Click to expand...
Click to collapse
Np don't mind sharing, thanks for the sympathy this definitely sucks aha. I usually add in qemu.hw.mainkeys=1 to get rid of the software keys when I put a new ROM on. It worked the first time I did it on this phone, my best guess is that I mistyped something. I'm not 100% sure why this is making my phone not show up as a Verizon model during the model recovery check...someone more knowledgeable than me would have to explain that.
Melodycd, I think you should be fine doing that as long as you're careful. I was pretty careless and made a lot of mistakes to get in my position. As long as you don't do ALL of the following things you should be safe:
1. Not have the latest recovery
2. Not have USB debugging enabled
3. Mess up while editing a build.prop file so you bootloop
It doesn't matter what they can or can't do with the phone. They don't care what you did to it as long as it's not physically damaged or have water damage. Software issues can be fixed. If they couldn't flash new software they wouldn't have CLN devices to send out for warranty.
I've sent in several dozen phones that I left rooted (for legitimate defect concerns) and none were charged back. They don't need to know what happened to the phone when you call all they need to know is its not working and to send you out a device. They'll receive yours, flash it or send it back to LG to flash, then send it out to someone else as a warranty device.
06stang said:
It doesn't matter what they can or can't do with the phone. They don't care what you did to it as long as it's not physically damaged or have water damage. Software issues can be fixed. If they couldn't flash new software they wouldn't have CLN devices to send out for warranty.
I've sent in several dozen phones that I left rooted (for legitimate defect concerns) and none were charged back. They don't need to know what happened to the phone when you call all they need to know is its not working and to send you out a device. They'll receive yours, flash it or send it back to LG to flash, then send it out to someone else as a warranty device.
Click to expand...
Click to collapse
Okay I'll send it in tomorrow. Thanks man, I was just worried that since the phone says "rooted" in download mode they would flip out about it. Appreciate the reassurance.
ccmbr002 said:
Okay I'll send it in tomorrow. Thanks man, I was just worried that since the phone says "rooted" in download mode they would flip out about it. Appreciate the reassurance.
Click to expand...
Click to collapse
I'm just sharing my experience. Over the past 5 years I've been rooting and returning. I can't guarantee anything but i can tell you my experiences and what I've been told by vzw people I know.
I had my g2 repaired when it was rooted. My camera wasn't working atall would just show up black when i opened the app. I sent it in rooted w CWM recovery as i stupidly forgot to remove it. And i had a replacement within 5 days no questions asked.
Not sure if this is because i am in UK or not, but they didn't blink an eye.
Swanseatom said:
I had my g2 repaired when it was rooted. My camera wasn't working atall would just show up black when i opened the app. I sent it in rooted w CWM recovery as i stupidly forgot to remove it. And i had a replacement within 5 days no questions asked.
Not sure if this is because i am in UK or not, but they didn't blink an eye.
Click to expand...
Click to collapse
Yep I was just worried because the Verizon phone explicitly states that it is rooted. Just to follow up for those who are on Verizon and are stuck bootlooping and with no way to flash the stock ROM, what 06stang said held true for me (so far). The Verizon rep on the phone couldn't help me (she said she needed me to put my SIM card in my G2 when I was calling her from my old phone) so I took it to a Verizon store. The dude checked it for physical damage, tried to turn it on, and when he saw it bootloop he put in an order to get me a replacement phone. I'll report back in a week or two after I send in my rooted phone and let people know what happens, it seems like they won't charge me as of right now though.
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.
Hello everyone! So my problem aroused a few days ago when I noticed my phone would randomly reboot and get stuck on the boot screen. I would have to mess around and finally only to get a few minutes of usage. I had King Rom installed which I believe was the issue. Fortunately, while trying to use Odin to recovery to stock, it shuts off in the middle of recovery mode. Now I am getting the screen that says: an error has occurred while updating the device software. please use the emergency recovery function in the smart switch pc software. I have been up all night trying to fix this with no results. I am so upset because I rely on my phone for my job as I am a delivery driver. I can't afford a new phone right now and I don't know what to do. It seems like I am pretty much SOL. I am hoping someone will be able to help me! Thanks so much
Somehow I was actually able to restore it to stock successfully in Odin. But before it will finish the initiation process it reboots over and over and the issue persists. Could there be another factor as to why this has happened?
slimspittle said:
Somehow I was actually able to restore it to stock successfully in Odin. But before it will finish the initiation process it reboots over and over and the issue persists. Could there be another factor as to why this has happened?
Click to expand...
Click to collapse
Well, if you're unlucky it might as well be a hardware related failure.
If you look through XDA, there are more and more people having the boot loop problem right now (me included).
Especially after the latest December FW update.
I would try to do a emergency restore through SmartSwitch, then factory reset.
That's the last thing I tried, although it didn't help me in the end and now my mobile is back at Samsung for repair.
If it still bootloops after these steps I think you're out of luck and have to contact a Samsung repair center.
slimspittle said:
aroused
Click to expand...
Click to collapse
Arose is the word i think you were looking for!!
MisterKanister said:
Well, if you're unlucky it might as well be a hardware related failure.
If you look through XDA, there are more and more people having the boot loop problem right now (me included).
Especially after the latest December FW update.
I would try to do a emergency restore through SmartSwitch, then factory reset.
That's the last thing I tried, although it didn't help me in the end and now my mobile is back at Samsung for repair.
If it still bootloops after these steps I think you're out of luck and have to contact a Samsung repair center.
Click to expand...
Click to collapse
Well my phone is the International from Kenya and I'm not sure if Samsung will honor the warranty. I am able to get to the point where you add your Google account. From that point, it gets stuck at ''just a sec''. From that point, it starts to freeze. I guess somehow the phone is still messed up. Think I should try flashing it again?
Do you have TWRP or any custom recovery, does it freeze when your in that menu? Do you have an external SD inside?
dude9946 said:
Do you have TWRP or any custom recovery, does it freeze when your in that menu? Do you have an external SD inside?
Click to expand...
Click to collapse
No I do not anymore and it freezes when the firmware has loaded and it says optimizing apps. And yes I do have a an SD Card
Long shot... have you tired booting up the phone without the card in? It's really sounding like a hardware problem, maybe GPU if it gets triggered reliably...
dude9946 said:
Long shot... have you tired booting up the phone without the card in? It's really sounding like a hardware problem, maybe GPU if it gets triggered reliably...
Click to expand...
Click to collapse
So this time I actually retried Odin with stock restored from a different website. Then bypassed adding a google account. From that point, I no longer got to the ''just a sec'' screen. I was actually able to fully set up the device. I am assuming it will still have issues occasionally. We will see though. I am very lucky because I go to work in a few hours and would miss out on so much tips! Thanks everyone for your support! If the phone still has problems after a restore how do you get a hold of Samsung if its an International phone. Do you have to send it back to the country of origin?
Samsung may decide that you need to contact the country of origin, I know for example Sony stopped supporting international phones in their repair centers last year... While you have the phone up and running try to get some diagnostic info on why its happening.
dude9946 said:
Samsung may decide that you need to contact the country of origin, I know for example Sony stopped supporting international phones in their repair centers last year... While you have the phone up and running try to get some diagnostic info on why its happening.
Click to expand...
Click to collapse
How would I go about doing that?
slimspittle said:
How would I go about doing that?
Click to expand...
Click to collapse
you could get CPU-Z from the app store and take screenshots.
Although i dont thing that would help, just call the samsung support line and select to go to phones and explain whats happening. you wont have to send the phone back to the country of origin.
Cyber5hark said:
you could get CPU-Z from the app store and take screenshots.
Although i dont thing that would help, just call the samsung support line and select to go to phones and explain whats happening. you wont have to send the phone back to the country of origin.
Click to expand...
Click to collapse
I agree you should call Samsung, However you might* still need to send it back to its Origin... It's totally up to Samsung's current policy on supporting international phones. Due to cost, a lot of repair centers really only keep parts/new phones for the ones locally available. However, It's also possible that they are able to contact their international warehouse for parts... So who knows ¯\_(ツ)_/¯ Keep us updated though, other users in your situation would love to know what happens!
dude9946 said:
I agree you should call Samsung, However you might* still need to send it back to its Origin... It's totally up to Samsung's current policy on supporting international phones. Due to cost, a lot of repair centers really only keep parts/new phones for the ones locally available. However, It's also possible that they are able to contact their international warehouse for parts... So who knows ¯\_(ツ)_/¯ Keep us updated though, other users in your situation would love to know what happens!
Click to expand...
Click to collapse
Okay so now it is stuck in a bootloop even after restoring to Odin again. I will try to get a hold of Samsung to see what they say. If not, I paid for my phone with my Wells Fargo Credit card and they have insurance. May get a replacement through them if Samsung won't help
So I just called them and they said to go into my local Samsung store within Best Buy to have them reflash the firmware lol. Going to take it their now to see what happens. Wish me luck
slimspittle said:
So I just called them and they said to go into my local Samsung store within Best Buy to have them reflash the firmware lol. Going to take it their now to see what happens. Wish me luck
Click to expand...
Click to collapse
Ha! did you tell them you already tried... good luck, keep us updated!
@slimspittle dont let us down, we need an update!
Okay so to send it in to Samsung(No charge for software issue as they said) they want a receipt with the IMEI on it. I bought the phone from Amazon and their is no IMEI on the receipt.
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?
Hello all!
A few weeks ago I updated my Google Nexus 6P to the 7.1.2 Public Beta (angler 03.68) OTA. Everything seemed fine. But yesterday my the phone started rebooting when trying to scroll any webpage in chrome. Last night it rebooted again and got stuck on the Google logo (white letters). I went into recovery mode and wiped the cache - still stuck on the white letters. I then went and did a data wipe and factory reset. Same problem - white letters only.
I called Google Support and they said I had to call Hauwei Support, since I purchased my phone from a third party vendor (Best Buy). I called Hauwei Support but they told me there is nothing they can do because my phone's warranty is up. I purchased the phone 12-20-2015. They said they don't even have a place for me to send the phone in to repair it.
I have phone insurance through Verizon. However, before I drop the $100 down for a refurb or similar model replacement, I wanted to know if anyone on here has a possible solution for me. Any information or assistance is greatly appreciated. Thanks in advance!
-William
Nope, sounds like the bootloop of death. If you want, you can Google the class action lawsuit that is being filed against Google & Huawei both, and have attorneys get in touch with with you. A simple Google search can get you to the sign up list. If that's not your thing, pull the trigger on the replacement.
Only thing to try before that is a full fastboot flash (assuming you're bootloader unlocked) if not, get the RMA.
Okay. I assumed it was dead. I also just found out that when I signed up for the new "unlimited" data plan through Verizon, they didn't continue my insurance. So, no replacement for me. I'm taking the lawsuit approach. Can't believe a (previous) flagship phone can just die, for so many customers, and Google/Huawei won't take responsibility for it. Hopefully justice will be served. Thanks for the reply!