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.
Related
I have a Galaxy S as shipped by Bell Canada. It doesn't have the 3 button download mode so I'm staying away from 3rd party roms for now.
It is unlocked and rooted. All has been well until today. I had it off for a while to use the SIM in another phone. When I turned it back on it asked for the SIM unlock code. I Dismissed that and checked the phone, all seemed well other than no SIM activation. I turned it off and removed the SIM and now it won't boot. I get the usual logo, the song, and for a long time the S logo. If I wait long enough it then appears to be off. If I press the back or menu key they will light up but that's it. I can't do anything else other than pull the battery.
I tried the hard reset with holding volume down and tap the power button. That only turns it back on with the same problem. The actual SIM is fine and working in another phone.
Is there anything I can do? If I could hard reset it I'd take it back to the store but I hesitate for now while it still contains my data.
this is a problem i have just posted about a couple of mins ago
but i can get it recovery mode and fatory reset with the vol up, home and power
then it will boot but obviously i have to then reset everything from scratch which is really annoying so anyone got any idea re this
lucky for you that you can get into recovery. Right now I'd be happy with a hard reset, it doesn't take long to rebuild the setup. I'd like to know who decided to remove the recovery mode, that's evil and keeps me from simply resetting the device.
its all the apps re downloading and installing them and resetting up accounts and swype and all that lot need a fix asap
do you know what version of andoid you are running
yes but at least you can get a working phone again, I can't without being able to get into any boot menus. Honestly it only takes 30 minutes to setup again from scratch. I'm on 2.1 and what I find at least on my HTC when it had 2.1 is that I setup the google account, let it sync contacts etc, then from Market Downloads I'll see listed all my apps that were previously installed. As long as I don't leave that screen I can install each app one after the other. Or a proper backup....
Any other magic key combos to reset this thing???
did you try hooking up to kies?
Yes but that does nothing since it never fully boots.
3rdcoast said:
I have a Galaxy S as shipped by Bell Canada. It doesn't have the 3 button download mode so I'm staying away from 3rd party roms for now.
It is unlocked and rooted. All has been well until today. I had it off for a while to use the SIM in another phone. When I turned it back on it asked for the SIM unlock code. I Dismissed that and checked the phone, all seemed well other than no SIM activation. I turned it off and removed the SIM and now it won't boot. I get the usual logo, the song, and for a long time the S logo. If I wait long enough it then appears to be off. If I press the back or menu key they will light up but that's it. I can't do anything else other than pull the battery.
I tried the hard reset with holding volume down and tap the power button. That only turns it back on with the same problem. The actual SIM is fine and working in another phone.
Is there anything I can do? If I could hard reset it I'd take it back to the store but I hesitate for now while it still contains my data.
Click to expand...
Click to collapse
Same thing happened to my phone, but a factory reset did nothing. The internal SD card gave out. Phone is now sent away for 3 - 6 weeks awaiting repair.
my phone did this to me today too, I was just about to post about this when I saw this thread.
So its an SD Card problem? theres no hope of getting it fixed without sending it in?
Yes I think it is the internal card meaning there isn't anything good enough to reset to. I walked the phone over to the store and I'll have to wait for new stock next week. Actually I'm lucky they will exchange it since I bought it outright which apparently is "against policy" even though they list a no contract full price. We'll see how it goes next week but overall I despise the telco industry in this country.
3rdcoast said:
Yes I think it is the internal card meaning there isn't anything good enough to reset to. I walked the phone over to the store and I'll have to wait for new stock next week. Actually I'm lucky they will exchange it since I bought it outright which apparently is "against policy" even though they list a no contract full price. We'll see how it goes next week but overall I despise the telco industry in this country.
Click to expand...
Click to collapse
i went to best buy today to try and exchange it, and apparently they only have a 14 day exchange policy with phones despite it saying 30 day on the receipt, anyhow i phoned samsung and they said i have to go through bell, even though im using the phone on telus, so that should be interesting.
So all the people that are having this problem have the Bell model?
Today i got mine off eBay, as soon a i turned it on, i get exactly the same thing.
It wont load into Android, i see that galaxy S logo and then black screen.
If i go into recovery i see "cant mount SD Card".
The more is search this forum the more i see that all the people with this problem are owners of the Bell i9000M model.
I seriously think they have some defect with the manufacturing line of the phone.
Have you guys installed any firmware on your phone before this happened?
mine is like that out of the box.
Mine is the same Bell model. There seems to be some issues with them which makes the lack of download mode even more dangerous. Right now it doesn't feel like the warranty is going to cover us for problems not our fault. I hope they replace it next week but if it still lacks download mode I'll remain nervous.
Seems like everyone is with the Bell model but my questions is:
Have you guys installed another firmware than the factory one which caused this to happen?
Are you running Stock?
We need to try and narrow this down as i am seeing too many posts about this issue, and they are with the Bell model.
clubtech said:
Seems like everyone is with the Bell model but my questions is:
Have you guys installed another firmware than the factory one which caused this to happen?
Are you running Stock?
We need to try and narrow this down as i am seeing too many posts about this issue, and they are with the Bell model.
Click to expand...
Click to collapse
i put new firmware on it last week, can't remember what it was but it was upgraded through kies so it's one samsung pushed to me, not a froyo unstable one.
bigc_13 said:
i put new firmware on it last week, can't remember what it was but it was upgraded through kies so it's one samsung pushed to me, not a froyo unstable one.
Click to expand...
Click to collapse
Thanks. if it was pushed to you via Kies i assume you were running stock JH2.
So it just stopped booting out of the blue?
To the OP: have you install any firmware on your device before this happened?
clubtech said:
Seems like everyone is with the Bell model but my questions is:
Have you guys installed another firmware than the factory one which caused this to happen?
Are you running Stock?
We need to try and narrow this down as i am seeing too many posts about this issue, and they are with the Bell model.
Click to expand...
Click to collapse
I haven't flashed any 3rd party roms. I did do the official update via Keis which even at the store today they reminded me that I should do the update.. That update seemed to go well and has been working for over a week until I turned it off for an hour. It still isn't clear if the disabled 3 button mode is hardware or software related but we all seem to have that in common too. So before they dismiss the whole thing and we get hosed over technicalities such as unlocking it should be clear that there are clear defects in these phones as far as I can tell.
I want to be comfortable that I'm not left out of hundred of dollars just because I choose to buy it outright and not be tied to contracts. Samsung has to play nicely because it is their phone. Bell has to play nicely because they are bringing them in and distributing to retail. What carrier I use should be irrelevant because the problems are not related to usage.
FYI, the clerks went off for conference to decide if I somehow got the phone against policy. Either they trust my story or I got mine moments before they got the memo about not selling outright.
clubtech said:
Thanks. if it was pushed to you via Kies i assume you were running stock JH2.
So it just stopped booting out of the blue?
To the OP: have you install any firmware on your device before this happened?
Click to expand...
Click to collapse
Same here, stock JH2 from Kies. Not rooted. Boots to Galaxy S logo, then black screen. Mine is sent in for repair... Almost two weeks now.
Seeing more and more of this being posted. There is obviously some issues with this phone.
clubtech said:
Thanks. if it was pushed to you via Kies i assume you were running stock JH2.
So it just stopped booting out of the blue?
To the OP: have you install any firmware on your device before this happened?
Click to expand...
Click to collapse
Our posts crossed..
Yes I believe mine had the JH2, the official keis offered firmware. I was looking forward to the biggie update at the end of the month so wasn't about to risk bricking before then. Irony stepped in anyway.
I'm a bit nervous until I get a new one. At that point if the 3 button mode still doesn't work I'll remain nervous that I'll get another potential brick.
edit-> yes, I simply shut it down for an hour or two to use the SIM in another phone to test that phone. At next boot it died. I knew something was wrong when the logo stayed up for much longer.
I have the 3 buttons enabled so it is not related to the 3buttons being disabled, however when i boot into recovery it clearly displays an error that it can not find the internal SD.
There is definitely something wrong with the Bell Galaxy S corrupting itself.
I bought mine from an eBay seller, he is saying the phone booted fine when he shipped it but when i opened the box today i only got this black screen after logo.
Gladly the seller will take it back.
Maybe this is why there are shortages everywhere in Canada. I hope the caught this up and are fixing it with the new batch.
Hello XDA Community!
I made a post about this issue before, but have more details so hopefully someone can help me figure out this issue.
My phone even when unplugged from my PC continuously says USB Connected/ USB Debugging in the notification menu.
Also, when I try and reboot the phone, instead of booting even to the Vibrant logo screen, the loading circle continuously blinks on and off, without actually booting.
As I type this, I am not holding down the power button, and the loading circle is blinking on and off by itself....
I used to be able to turn the phone on into recovery mode in the past, but now when I try to reboot into recovery I get a big yellow picture that says "Downloading"
The only way the phone will turn on is if it is plugged in.
I am fairly certain that this reboot issue and the USB issue are correlated in some way.
Did anyone else have this issue with their phones? And if so, how did you solve it?
Another thing I have just discovered...
When the phone is on and idle, the USB Connection notification will constantly blink on and off, which is why I think the phone would do the same when trying to power on!
Is this a hardware issue or a software issue?
I have not flashed anything in a very long time before this issue started happening so I believe a restore is unnecessary .
Someone please help me! This is very annoying, not only do I have NO notification bar because of the constant USB Connection notification turning on and off, I cannot turn on my phone at all unless it is plugged in!
ACK!
Take it back
I carry the insurance, so personally if this was happening to me I would not even mess with it. It sounds like you have a genuine problem with the phone and it needs to be replaced.
If it is possible to do try a nandroid backup of your phone to make getting back to where you are on your new device easier. Then take your phone back to stock with the recovery image here -->
http://forum.xda-developers.com/showthread.php?t=734475 (Thank you justanothercrowd)
One you have a stock device see if you are still having the issue. If you are take it back as defective. Even if you don't have the insurance, that sounds like a factory defect and should be covered by the factory warranty. The insurance just makes the process easier and makes sure they just give you a swap out at the store rather than having to wait for repairs. It also covers things the warranty does not, such as screen breakage - which is the specific reason I carry the insurance.
Ah crap wish I had insurance.... Do I have to do that whole odin procedure or is there a one click un root procedure as well?
Sent from my SGH-T959 using XDA App
Nevermind i just read through that link you posted. So when i go to a t mobile store do i have to unroot or can i just hide my root applications until i get a new phone?
Sent from my SGH-T959 using XDA App
I actually have not had reason to go back to stock, or even use odin yet at this point. My only roms were .zip files that I flashed via clockwork recovery.
I would say that your best best it to just follow the instructions on justanothercrowd's thread very carefully and deliberately. You are already having issues with reboots and your USB port, so this is not the time to deviate into experiments.
So to cut you off and just answer you next three questions:
Q) Can I just . . .
A) No! Just follow the directions exactly.
Q) But can I . . .
A) No! Just follow the directions exactly.
Q) Do I have to . . .
A) Hey look, Just follow the damn directions exactly!
Sorry, I can't help much beyond that. You chose to modify your phone and risk that you would not have issues, just like the rest of us here. In your case you did have issues. Now you have to get it back to stock so they don't have any reason to claim you caused this or that your warranty is void. I hope all goes well and it works out for you. Let as know and keep us posted. Good luck.
Lo N Slo said:
Nevermind i just read through that link you posted. So when i go to a t mobile store do i have to unroot or can i just hide my root applications until i get a new phone?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
We must have been typing at the same time LOL.
There is a thread on unrooting, and basically it is just deleting a few things. After doing this you should not have any non-stock applications on the phone and there would be no reason to think it was rooted unless they went digging on the file system. Personally, I would delete those telltale files just in case, it looks a little suspicious to bring in a phone that looks like it has not been used since you bought it, but they have no proof you did anything and you can claim that you first did a factory reset to see if it would fix the problem.
Just want to keep this thread going, as I am having the exact same issue as the OP as of today. It happened out of the blue, and I haven't flashed anything new to my phone since JI6 was released, other than that, it's just a stock, rooted phone.
Hoping someone has an idea, but I will likely get it replaced under warranty, since the GPS has never worked either.
damnit damnit damnit I really wish I had warranty.
Random question about clockword mod recoveries.
If I were to do a backup right now, and save that file to my computer, could I restore that file later on a different phone after I root my replacement?
I don't have that many mods flashed, and I know all of the apps can be synced, but still it would be sooo convenient .
I believe that is how it works, so yes. It should be no different then when you clone a hard drive to put the image on multiple computers for easy distribution.
It is (just like the cloning metaphor) hardware specific. Just like I could not purchase a upgrade computer and expect a cloned image to work, don't expect to create a Vibrant backup and restore it on a Captivate.
That said, you should be able to restore your backup to new (identical) hardware.
By the way, what is the warranty on these? I thought it was a year for defects. I didn't think the Vibrant had been around long enough yet for anyone to be off warranty.
it should be a year, but there was also the option for a purchased warranty. I did not purchase a warranty, so I should be good on just my manufacturer's defect warranty
Being discussed here:
http://forum.xda-developers.com/showthread.php?t=817643
As it says I broke my G2 stepped on so the screen lights up but all black I can't see anything its fully rooted and nothing erased. Just got my replacement bout to send broke 1 back but should i worry cause it s-off fully rooted oh and i did tell the i woke up and my screen wouldn't work so get new phone. Should i worry or is there anything i can do before sending PLEASE HELP......
Are you replacing through Asurion or through a warranty exchange? If its an insurance replacement there's nothing to worry about.
If you're doing in through the warranty, they're going to be able to figure out that it has physical damage if you stepped on it and broke the screen.
You'll probably get hit with the out of warranty fee.
Sent from my T-Mobile G2 using XDA Premium App
Assuming that you have it rooted, you already have USB debugging on, google for a program called Android Screencast. You can use to it control your phone with your mouse and keyboard on your pc. The screen will be displayed on that program and you can click on the display on that and control it. So you can unroot with that. If you have a custom rom, you can then restore your old stock rom.
When you are doing all of this, you have to remember that while its doing restore, you cant see the screen doing the restore on the program as your phone isnt fully booted in android. But just leave it and keep an eye on it, it will vibrate when the phone reboots after restore.
How do I know this? I stepped on my desire z and had it rooted with CM7! I managed to unroot, get S-on, and restore my old rom!
Final thing I will tell you, is that if you after restoring your old rom, you decide to format it back to factory settings, usb debugging will be put back to off so the android screencast wont work and you cant actually tell if it has succeeded. But if you do a factory reset, let the phone boot up and put your volume up and down, you should be able to hear the beeps, which means android has booted perfectly fine.
Oh and even thought i stepped on mine, HTC themselves couldnt tell i stepped on it and they fixed mine for free in warranty!
Good luck mate
don't sweat it. if you can't see anything, neither can they. all you really have to worry about is if the water mark thing is red or not. i've sent mines with the same problem, screen won't show anything but turns on, rooted and s-off. i didn't have a problem.
don't tell them you rooted it though. happy days!!!
cdreamworld said:
don't sweat it. if you can't see anything, neither can they. all you really have to worry about is if the water mark thing is red or not. i've sent mines with the same problem, screen won't show anything but turns on, rooted and s-off. i didn't have a problem.
don't tell them you rooted it though. happy days!!!
Click to expand...
Click to collapse
Or do that
Thinking about it, since it isnt a repair, and its only t mobile not htc themselves you are dealing with, you dont have to worry. Tmob probably just see if its broken as you say and then toss it in a pile to send to HTC. My situation was different because it was a repair and HTC will defo look at it.
I wouldnt take any chances 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.