My Nexus 6p was definitely one of the batches that should not have passed QC... soft power button, phone shutting down with plenty of battery left and today all of a sudden, while I was using the phone, phone restarts and get stuck in a bootloop...
Phone is not rooted and the bootloader locked... its out of warranty but I called google support anyway and they directed me to Huawei .. luckily, they will fix it for free..
IF you are having the same problem, call google up and hold them accountable for this bull****
Same deal here but i bought my 6p from best buy along with geek squad protection plan. Rather than send me another 64gb 6p, they've given me a gift card for the price at the time of purchase. At the moment only 32gb versions are available on best buy dot com. I'm not totally opposed to the 32gb version but I'm not excited about it. It took 3 days from the time I submitted my RMA request to get an email telling me this gift card b.s.
I haven't returned anything yet. Not sure what to do. I really liked that phone.
i had my first bootloop today. i just did a force restart and it booted normal. should i be concerned ?
ps.
phone is only 2 weeks old, and with stock ota update 7.1.1 (rooted)
puddi said:
i had my first bootloop today. i just did a force restart and it booted normal. should i be concerned ?
ps. phone is only 2 weeks old, and with stock ota update 7.1.1 (rooted)
Click to expand...
Click to collapse
I wouldn't be. Sounds like you are unlocked and rooted. Just keep a good backup on your PC (including EFS) and enjoy your phone.
puddi said:
i had my first bootloop today. i just did a force restart and it booted normal. should i be concerned ?
ps.
phone is only 2 weeks old, and with stock ota update 7.1.1 (rooted)
Click to expand...
Click to collapse
Rooted or not and having a backup or not won't fix this unfixable bootloop. I have one in my possession I'm trying to restore and nothings working. Random reboots a week prior to it going into this bootloop. I've done a bunch of research and it's not good.
thesparky007 said:
My Nexus 6p was definitely one of the batches that should not have passed QC... soft power button, phone shutting down with plenty of battery left and today all of a sudden, while I was using the phone, phone restarts and get stuck in a bootloop...
Phone is not rooted and the bootloader locked... its out of warranty but I called google support anyway and they directed me to Huawei .. luckily, they will fix it for free..
IF you are having the same problem, call google up and hold them accountable for this bull****
Click to expand...
Click to collapse
Do you have the Huawei contact info? I have tried to go through the online support but I have yet to hear anything in a number of days. Same problem here, bootloop out of no where.
galakanokis said:
Do you have the Huawei contact info? I have tried to go through the online support but I have yet to hear anything in a number of days. Same problem here, bootloop out of no where.
Click to expand...
Click to collapse
Call them here 1-888-5HUAWEI
thesparky007 said:
Call them here 1-888-5HUAWEI
Click to expand...
Click to collapse
Thanks, much appreciated.
I just went through the same thing. Waiting on the RMA box to arrive so it can be sent back.
Sent from my Nexus 6 using XDA-Developers Legacy app
Same here...happened just this morning. I can't get into recovery and I can ONLY boot into bootloader. I am on full stock with a locked bootloader running 7.1.1. I got off the phone with a Huawei rep and she stated it could be due to a Google update and that they will try and downgrade it on their end. Strange cause I was already running the latest 7.1.1 (unless a new update was released his morning).
Here's what I tried to no avail:
-unlocked bootloader and tried to flash stock rom/recovery
-tried flashing custom recovery (twrp)
-tried booting into temp customer recovery (twrp)
-tried flashing 7.0 stock
I have re-locked the bootloader and will have to send it in. What a real bummer, I have managed to get out of a softbrick (unless this device is truly bricked ???) on many, many device since the T-Mobile G1, but I am at wits end with this device.
Going through the RMA process now, thanks again for the number.
I have heard it mentioned that flashing back to 6.0.1 might work, has anyone tried? I did flash all the way back to 7.0 with no luck.
tried flashing back to 6, 6.01 and 7.0 but it still persists. get it exchanged or repaired
It's now several phones a day... At what point does either Huawei or Google fess up to root cause? The one question I have is are all of these hard bricks on phones running nougat??
Sent from my Nexus 6 using XDA-Developers Legacy app
uzi132 said:
Same here...happened just this morning. I can't get into recovery and I can ONLY boot into bootloader. I am on full stock with a locked bootloader running 7.1.1. I got off the phone with a Huawei rep and she stated it could be due to a Google update and that they will try and downgrade it on their end. Strange cause I was already running the latest 7.1.1 (unless a new update was released his morning).
Here's what I tried to no avail:
-unlocked bootloader and tried to flash stock rom/recovery
-tried flashing custom recovery (twrp)
-tried booting into temp customer recovery (twrp)
-tried flashing 7.0 stock
I have re-locked the bootloader and will have to send it in. What a real bummer, I have managed to get out of a softbrick (unless this device is truly bricked ???) on many, many device since the T-Mobile G1, but I am at wits end with this device.
Click to expand...
Click to collapse
You aren't alone obviously. These phones seem to be little time bombs where the boot loop issue is concerned. Mine goes into bootloops every time I flash an update or new ROM or attempt to restore a backup. I expect to hardbrick this phone at some point. It just hasn't happened yet.
Completely forgot about this thread. Huawei swapped out my motherboard with a 128 Gb (I had sent a 64 Gb). I actually quite happy my phone bricked itself. Haha
My 6p started rebooting last night and no matter what I did, couldn't get it to boot. Only bl mode worked. This thing has been one problem after another, so I went and got an iPhone this morning. Maybe one day Google will finally start making products that last more than one year, but hasn't happened yet and I'm tired of it.
andrewnelson23 said:
My 6p started rebooting last night and no matter what I did, couldn't get it to boot. Only bl mode worked. This thing has been one problem after another, so I went and got an iPhone this morning. Maybe one day Google will finally start making products that last more than one year, but hasn't happened yet and I'm tired of it.
Click to expand...
Click to collapse
On the same boat. Mine's stuck on bootloop, no recovery. 1 year is pretty good considering I've only had the device for 3 months...
Nexus 6p here in the UK, Got the OTA update yesterday and it caused crashes immediately. Had two crashes when it immediately rebooted and seemed ok. A third one soon followed and got stuck in a boot loop, a few minutes after it fixed it self and seemingly working fine. An hour later i was playing a game and it just locked, screenfroze and a buzzing noise from the speakers before going into a boot loop. Left it for a few hours while at the cinema and nothing.
Bought directly from Google and still under warranty. Interestingly though, i bought my 6p in March 2016, I then had to RMA it a few months later as the USB C port randomly broke I will be doing my second RMA in less than a year. When checking my IMEI the google support operative actually stated I was under warranty till August 2018. So a 30 month warranty. Got a new one coming out so if anyone develops this problem give them a ring.
New phone received, sent old one off. Checked it just before i did, still stuck in boot loop.
Narom88 said:
New phone received, sent old one off. Checked it just before i did, still stuck in boot loop.
Click to expand...
Click to collapse
That's way too common with this phone. Thinking about moving on to something else.
Related
This afternoon my S7 Edge entered a boot loop. All I was doing was reading the news, in the same app I have been for the past couple of months. The device is untouched in terms of modifications since purchase, so unrooted stock rom. I can get into download mode, and occasionally, recovery mode. I wiped the cache as my first attempted fix - no change. Then did a factory reset - no change. I then thought I'd try loading twrp so I could flash a custom rom, but Odin was unable to flash it due to FRP Lock blocking it. I then downloaded the latest stock rom from sammobile, and was able to flash this via Odin. On first boot the device did start to load, and reached 10/19 in optimising the apps, before starting the boot loop again. I am kinda out of ideas now. Any help would be greatly appreciated.
re: bootloops
whitebloodcell said:
This afternoon my S7 Edge entered a boot loop. All I was doing was reading the news, in the same app I have been for the past couple of months. The device is untouched in terms of modifications since purchase, so unrooted stock rom. I can get into download mode, and occasionally, recovery mode. I wiped the cache as my first attempted fix - no change. Then did a factory reset - no change. I then thought I'd try loading twrp so I could flash a custom rom, but Odin was unable to flash it due to FRP Lock blocking it. I then downloaded the latest stock rom from sammobile, and was able to flash this via Odin. On first boot the device did start to load, and reached 10/19 in optimising the apps, before starting the boot loop again. I am kinda out of ideas now. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Go into settings>developer's options and ENABLE OEM UNLOCK then
go into settings>general management>reset>factory data reset and
reset the phone.
Once you have done that the phone will work properly without rebooting
provided that you have successfully odin flashed the official samsung
G935F S7 Edge firmware prior to doing a factory data reset.
Good luck, have a great day!
Thanks for replying. Unfortunately I can't get into the phone at all. Only screen I have access to a recovery and downloader.
So I left the phone alone for a while and tried booting into safemode. This time it worked - sort of. It is asking me for a password, but I have never set one. I only ever set a pin and fingerprints. But since wiping everything that doesn't seem to apply anymore. What is the default password? I am referring to the phone password, rather than a google account obviously. I am not at that stage of the boot up.
Update: found the password (default_password), still boot looping on the optimising apps screen.
If you still can't get into the phone like the person above said, I would use Oden to reparation and reflash your stock rom. If it still gives you issues, I'd suspect hardware fault.
vsn4 said:
If you still can't get into the phone like the person above said, I would use Oden to reparation and reflash your stock rom. If it still gives you issues, I'd suspect hardware fault.
Click to expand...
Click to collapse
I have flashed stock rom (initially the version that matches my carrier, although my phone was bought sim free and unlocked, and then the version for unlocked phones (BTU in sammobile I think)) but it still just boot loops. The phone can remain in download mode as long as it wants, and previously, when it was asking for the password, it was able to remain on that screen indefinitely. I would have thought if it was a hardware problem the boot looping would happen regardless of the action on screen. Immediately after flashing the stock rom, it did start to load before ooting. Now it just boots immediately at the Samsung Logo.
vsn4 said:
If you still can't get into the phone like the person above said, I would use Oden to reparation and reflash your stock rom. If it still gives you issues, I'd suspect hardware fault.
Click to expand...
Click to collapse
Just to be clear, do you mean repartition here? I have not checked that option before, will try it.
Even without the PIT file. Flashing stock rom should have fixed you... which carrier do you have? If Verizon, they have a recovery assistant software that works in these situations. Or if not try "samsung kies". If all else fails I'd give Sammy a call.
vsn4 said:
If you still can't get into the phone like the person above said, I would use Oden to reparation and reflash your stock rom. If it still gives you issues, I'd suspect hardware fault.
Click to expand...
Click to collapse
vsn4 said:
Even without the PIT file. Flashing stock rom should have fixed you... which carrier do you have? If Verizon, they have a recovery assistant software that works in these situations. Or if not try "samsung kies". If all else fails I'd give Sammy a call.
Click to expand...
Click to collapse
I am in the UK, and my carrier is Three, although the phone was purchased sim free. I tried samsung kies (phone not compatible apparently), samsung switch (phone does not support initialization). I may have to call Samsung, but I purchased the phone on eBay, so no warranty (never doing that again!), so I guess it'll be expensive to get them to sort it. I've taken it to a phone repair shop this afternoon and the guy reckoned he could fix it based on what I said. We shall see. I don't have to pay unless he fixes it, so worth a shot.
You can wipe your phone by entering recovery. Default recovery has the wipe option.
alehawk said:
You can wipe your phone by entering recovery. Default recovery has the wipe option.
Click to expand...
Click to collapse
Was the first thing I tried. Didn't help.
I got the bootloop thingy and was the cache, I wiped and the phone booted up
alehawk said:
I got the bootloop thingy and was the cache, I wiped and the phone booted up
Click to expand...
Click to collapse
Thanks for trying to help, but, again, already tried that.
whitebloodcell said:
I am in the UK, and my carrier is Three, although the phone was purchased sim free. I tried samsung kies (phone not compatible apparently), samsung switch (phone does not support initialization). I may have to call Samsung, but I purchased the phone on eBay, so no warranty (never doing that again!), so I guess it'll be expensive to get them to sort it. I've taken it to a phone repair shop this afternoon and the guy reckoned he could fix it based on what I said. We shall see. I don't have to pay unless he fixes it, so worth a shot.
Click to expand...
Click to collapse
Hope all goes well, let us know if you get it sorted out.
Hi
Just curious...why do u say u don't have warranty just because u brought from eBay?
Surely it doesn't matter where u brought it and it still has warranty.
Have u tried contacting Samsung?
AnubuRe said:
Hi
Just curious...why do u say u don't have warranty just because u brought from eBay?
Surely it doesn't matter where u brought it and it still has warranty.
Have u tried contacting Samsung?
Click to expand...
Click to collapse
Pretty much all warranties (including Samsung - I checked) are contracts with the original purchaser only. Even if you have proof of purchase, you then need to match the records they have of the identity of the original purchaser. Whilst some manufacturers will be more lenient, others will follow the official policy strictly. Speaking from experience here.
whitebloodcell said:
Pretty much all warranties (including Samsung - I checked) are contracts with the original purchaser only. Even if you have proof of purchase, you then need to match the records they have of the identity of the original purchaser. Whilst some manufacturers will be more lenient, others will follow the official policy strictly. Speaking from experience here.
Click to expand...
Click to collapse
For those perhaps in similar situation in the future, Samsung didn't care that it was purchased second hand, despite what the fine print says. They just looked at the serial number. In the course of trying my own repairs I flashed a custom rom, which of course tripped the knox warranty void bit. When I took it into the service centre they saw this and then wanted to charge £225 for an out of warranty repair. I refused at the time. I later called Samsung support and explained the situation (I said a phone repair shop must have done the flashing). Again on the phone I was told it would be an out of warranty repair, and this time I agreed. They collected my phone and returned it to me today however, with no invoice or mention of charges, so it looks like they just did the repair no questions asked.
I have the same issues, so far I'm getting by with flashing a stock rom with pit file and doing repartition and nand erase, normal cache/ factory reset doesn't help, it sometimes even boot loops while in twrp.
Somehow Odin flashing helps for a random amount of time, but it has thus far, crashed after a month, or a couple weeks since the last flash, etc. So far it's been my 5th boot loop event in the last 6 months
It sucks but as I got mine from another country (/win), didn't get the warranty ;( plus I tripped Knox by rooting.
sounds hardware related to me..
i had a friend with a note 4 who had similar problems it would hardly ever boot sometimes boot straight into download mode..
if by chance it did boot it would boot once the device was locked for a short time it would reboot and start over again bootlooping..
it was the emmc flash memory that was failing...
a workaround i found for this was the first thing i did when finally getting it to boot was install "Wake Lock - CPU Awake" and set it to never let the device sleep and to startup on boot...
this "fixed" it as long as your phone does not turn off... he had insurance though and sent it off and they sent him a new refirb
again this note 4 was untouched never rooted or anything
vsn4 said:
If you still can't get into the phone like the person above said, I would use Oden to reparation and reflash your stock rom. If it still gives you issues, I'd suspect hardware fault.
Click to expand...
Click to collapse
im having pretty much the exact same problem except ive been unsuccesful at flashing the stock firmware for my galaxy s7 active (SM-G891A). the active series isnt the most saute after, so finding the right firmware is alil more difficult. which im pretty sure is how i got into this situation! my question is what exacly does checking the "reparation" option do. i read to leave to leave it unchecked/unticked. maybe thats why ive been unsuccessful. and someone told me awhile ago not to fill in the "bt" box becuz i have a locked bootloader. this correct or no?
Hey guys!
After few days trying to fix the problem on my Nexus 6P, I still can't make it run properly so I decide to create a new thread asking you guys and this is my last hope for it. I had been using stock android 6.0.1 until I decided to upgrade to OTA 7.1.1 because I hate the notification on the statusbar. My phone worked fine, everything was OK on 6.0.1. After upgrading to android 7.1.1, my phone couldn't get any mobile signal. It still can detect the simcard, the sim toolkit app still shows but I can't use the network. Everything else works properly just like before upgrading. I tried to flash stock 7.1.2 n2g47o image from google; some custom roms like chroma, pure nexus, ressurection remix, flyme, ... and also tried to select automatic band but it is still the same. When I select automatic or any other band, it shows "select [band] unsuccessful". The service state shows "radio off" and I can't turn it back on in *#*#4636#*#*. Please help me! Thank you guys a lot.
tbmoc96 said:
Hey guys!
After few days trying to fix the problem on my Nexus 6P, I still can't make it run properly so I decide to create a new thread asking you guys and this is my last hope for it. I had been using stock android 6.0.1 until I decided to upgrade to OTA 7.1.1 because I hate the notification on the statusbar. My phone worked fine, everything was OK on 6.0.1. After upgrading to android 7.1.1, my phone couldn't get any mobile signal. It still can detect the simcard, the sim toolkit app still shows but I can't use the network. Everything else works properly just like before upgrading. I tried to flash stock 7.1.2 n2g47o image from google; some custom roms like chroma, pure nexus, ressurection remix, flyme, ... and also tried to select automatic band but it is still the same. When I select automatic or any other band, it shows "select [band] unsuccessful". The service state shows "radio off" and I can't turn it back on in *#*#4636#*#*. Please help me! Thank you guys a lot.
Click to expand...
Click to collapse
Try the flash all bat with stock rom and then relock your boot loader
Sent from my Pixel XL using Tapatalk
Are you with verizon, 7.1.1 has images for verizon only and except, may flashing one of those will fix your issue and use the flash all bat to wipe completely your phone.
bennyboy2120 said:
Try the flash all bat with stock rom and then relock your boot loader
Click to expand...
Click to collapse
coremania said:
Are you with verizon, 7.1.1 has images for verizon only and except, may flashing one of those will fix your issue and use the flash all bat to wipe completely your phone.
Click to expand...
Click to collapse
Thank you guys and sorry for not saying, I flashed both 7.1.1 (NUF26N, Mar 2017, Verizon Only) and 7.1.2 (N2G47O, May 2017) with flash-all.bat follow the instruction here https://developers.google.com/android/images but it remains the same. I read on Nexus Community that Google developers released images that fix signal problems from Feb 2017. I'm downloading this 7.1.1 (NMF26F, Dec 2016. All carriers except Verizon) and will give it a try even when it was released on Dec 2016.
tbmoc96 said:
Thank you guys and sorry for not saying, I flashed both 7.1.1 (NUF26N, Mar 2017, Verizon Only) and 7.1.2 (N2G47O, May 2017) with flash-all.bat follow the instruction here https://developers.google.com/android/images but it remains the same. I read on Nexus Community that Google developers released images that fix signal problems from Feb 2017. I'm downloading this 7.1.1 (NMF26F, Dec 2016. All carriers except Verizon) and will give it a try even when it was released on Dec 2016.
Click to expand...
Click to collapse
Again try relock on the boot loader and tell me if it helps
Sent from my Pixel XL using Tapatalk
tbmoc96 said:
Thank you guys and sorry for not saying, I flashed both 7.1.1 (NUF26N, Mar 2017, Verizon Only) and 7.1.2 (N2G47O, May 2017) with flash-all.bat follow the instruction here https://developers.google.com/android/images but it remains the same. I read on Nexus Community that Google developers released images that fix signal problems from Feb 2017. I'm downloading this 7.1.1 (NMF26F, Dec 2016. All carriers except Verizon) and will give it a try even when it was released on Dec 2016.
Click to expand...
Click to collapse
Hope you will fix it, if you got no success may you try flashing back to 6.0.0
Edit: check you imei, I will hope for you it doesn't show 0, then may you're f****d without a backup of your efs partition.
bennyboy2120 said:
Again try relock on the boot loader and tell me if it helps
Click to expand...
Click to collapse
The guide has the re-lock part so I'm 100% sure I tried to re-lock the bootloader. Not only the Google guide but on other topics on xda and Nexus Community someone re-locked the bootloader and they fixed the problem. Therefor, I followed them to re-lock but still no service
coremania said:
Hope you will fix it, if you got no success may you try flashing back to 6.0.0
Click to expand...
Click to collapse
I also tried to flash back to 6.0.0 first release firmware and 6.0.1 to get vendor for chroma / purenexus , still the same
coremania said:
Hope you will fix it, if you got no success may you try flashing back to 6.0.0
Edit: check you imei, I will hope for you it doesn't show 0, then may you're f****d without a backup of your efs partition.
Click to expand...
Click to collapse
My imei still there, I also have EFS backup ;(
tbmoc96 said:
My imei still there, I also have EFS backup ;(
Click to expand...
Click to collapse
I guess you flashed the backup, apn reset? Or flashing lineage?
Edit: take a look here, maybe deleting via fastboot and restoring with twrp will help
http://www.theandroidsoul.com/fix-e...d-wifibluetooth-issues-restoring-twrp-backup/
Sadly this problem ends up to hardware on other threads, hoping not for you
coremania said:
I guess you flashed the backup, apn reset? Or flashing lineage?
Edit: take a look here, maybe deleting via fastboot and restoring with twrp will help
http://www.theandroidsoul.com/fix-e...d-wifibluetooth-issues-restoring-twrp-backup/
Sadly this problem ends up to hardware on other threads, hoping not for you
Click to expand...
Click to collapse
I lost the network right after I upgraded my phone through OTA ;( I flashed stock firmware right after that so I guess it's not come from EFS partition. I backed up all things with TWRP after I had finished the flash-all.bat process. I'm checking out the thread, maybe there's a way out?
Yesterday I brought my phone to Huawei service center in my country but they don't officially sell the Nexus 6P in my country so they didn't take the phone because they don't have anything to fix its problem.
I would try, seems that you got nothing to loose
I'm having the same problem.
I've tried everything you did and when I select automatic bands in 4636 it does successfully, but still no signal.
Also, when I search for network in the mobile settings it always error.
I noticed that my GPS also stopped working. I only can use apps like Maps if I'm connected to a Wi-Fi.
Since the GPS stopped working this makes me believe it's an antenna problem.
If I selected WDCMA Only my network goes to Global instead of what I've selected.
I have the xt1511 (US Nexus Version), but since Nexus is always unlocked I know it isn't a CDMA/GSM trouble.
My wife's 6P started doing this about a month ago where she would randomly lose service for a minute. Today she lost it completely and it seems like there is an issue internally with the radio. I've tried multiple sim cards, factory resets, flashing the latest factory image, trying an old radio version etc. It seems like there has to be some kind of defect. I would hang on to the phone just in case there ends up being a class action lawsuit. Her phone is exactly one year and one month old.
Im frustrated...
I bought my nexus 6p six months ago from a guy on ebay. I love the phone really, but one month later i had the battery problem, and i said well, it could happen, i bought a battery and changed it.
and yesterday, i lost signal. its dead. i tried everything in the forums, i locked it, got it back to stock. and nothing...
Now what?, we dont know if its a hardware problem or is it a software one.
Should I take it to a service center in the us? I have no warranty.
Update 06-12-17: so i kept readying and I saw someone solved the issue installing a factory image from febuary. I did it flashed it, then went into recovery and made factory reset. and it worked!!!! signal is backkkk! im soo happy!!!
Update 2 06-12-17: yeah i was happy, and soo i was going back to normal, i installed twrp, and root, phone boot up and again bye bye signal.
Update 06-14-17: Turns out that since I got to Colombia a month ago, this country has like a national IMEI list. Since I didn't subscribe my device the carrier blowies my phone and that why I had no service... Soo this ends my journey with the no service problem. They fixed it
Humanreflect said:
Im frustrated...
I bought my nexus 6p six months ago from a guy on ebay. I love the phone really, but one month later i had the battery problem, and i said well, it could happen, i bought a battery and changed it.
and yesterday, i lost signal. its dead. i tried everything in the forums, i locked it, got it back to stock. and nothing... Now what?, we dont know if its a hardware problem or is it a software one. Should I take it to a service center in the us? I have no warranty.
Click to expand...
Click to collapse
Is your phone a H1511 or 1512? You didn't mention it explicitly but you may have changed the LTE bands using a hidden menu. Apparently this is a known bug with the hidden menu itself. Several people have had luck flashing an older version of Chroma and switching the band back to Auto. There is a link to the ROM for the 6P in this Nexus Help Forum. If you never used this menu before, you may just be able to access the menu and try setting to Auto first before flashing the ROM. You should get a confirmation that AUTO mode is selected. You also didn't explicitly mention whether the phone worked properly for a while AFTER your battery repair, OR was a direct result of your repair... which could mean it was damaged.
v12xke said:
Is your phone a H1511 or 1512? You didn't mention it explicitly but you may have changed the LTE bands using a hidden menu. Apparently this is a known bug with the hidden menu itself. Several people have had luck flashing an older version of Chroma and switching the band back to Auto. There is a link to the ROM for the 6P in this Nexus Help Forum. If you never used this menu before, you may just be able to access the menu and try setting to Auto first before flashing the ROM. You should get a confirmation that AUTO mode is selected. You also didn't explicitly mention whether the phone worked properly for a while AFTER your battery repair, OR was a direct result of your repair... which could mean it was damaged.
Click to expand...
Click to collapse
In my case I have a 1511 and I've tried this Chroma fix. No success.
v12xke said:
Is your phone a H1511 or 1512? You didn't mention it explicitly but you may have changed the LTE bands using a hidden menu. Apparently this is a known bug with the hidden menu itself. Several people have had luck flashing an older version of Chroma and switching the band back to Auto. There is a link to the ROM for the 6P in this Nexus Help Forum. If you never used this menu before, you may just be able to access the menu and try setting to Auto first before flashing the ROM. You should get a confirmation that AUTO mode is selected. You also didn't explicitly mention whether the phone worked properly for a while AFTER your battery repair, OR was a direct result of your repair... which could mean it was damaged.
Click to expand...
Click to collapse
its the 1511 version. Yes the phone worked perfectly after the repair. I was in the US, and three weeks ago I came to colombia. Suddenly it stoped working a couple of days again. I tried the chroma rom. Selected the Auto band. but it did nothing, rebooted and everything but didnt work.
Earlier today i installed a older factory image and it work, i thought it was solved, then i flashed twrp, rooted and lost service again... tried the factory images again and nothing...
Humanreflect said:
Im frustrated...
I bought my nexus 6p six months ago from a guy on ebay. I love the phone really, but one month later i had the battery problem, and i said well, it could happen, i bought a battery and changed it.
and yesterday, i lost signal. its dead. i tried everything in the forums, i locked it, got it back to stock. and nothing...
Now what?, we dont know if its a hardware problem or is it a software one.
Should I take it to a service center in the us? I have no warranty.
Update 06-12-17: so i kept readying and I saw someone solved the issue installing a factory image from febuary. I did it flashed it, then went into recovery and made factory reset. and it worked!!!! signal is backkkk! im soo happy!!!
Update 2 06-12-17: yeah i was happy, and soo i was going back to normal, i installed twrp, and root, phone boot up and again bye bye signal.
Update 06-14-17: Turns out that since I got to Colombia a month ago, this country has like a national IMEI list. Since I didn't subscribe my device the carrier blowies my phone and that why I had no service... Soo this ends my journey with the no service problem. They fixed it
Click to expand...
Click to collapse
Well, I've just checked your latest update today.
What did you do to include your device in this national list? And how did you find out about this list? I need to check if Brazil has it as well. Do you still have signal without problem?
Thanks.
Debuffer said:
Well, I've just checked your latest update today.
What did you do to include your device in this national list? And how did you find out about this list? I need to check if Brazil has it as well. Do you still have signal without problem?
Thanks.
Click to expand...
Click to collapse
Hey, i went to my carrier. And they tol me it was blocked. And they un blocked it.
It was imei blocked because ut wasebt in that imei national list. Soo it didnt work with any carrier.
you've fixed your phone
Humanreflect said:
Im frustrated...
I bought my nexus 6p six months ago from a guy on ebay. I love the phone really, but one month later i had the battery problem, and i said well, it could happen, i bought a battery and changed it.
and yesterday, i lost signal. its dead. i tried everything in the forums, i locked it, got it back to stock. and nothing...
Now what?, we dont know if its a hardware problem or is it a software one.
Should I take it to a service center in the us? I have no warranty.
Update 06-12-17: so i kept readying and I saw someone solved the issue installing a factory image from febuary. I did it flashed it, then went into recovery and made factory reset. and it worked!!!! signal is backkkk! im soo happy!!!
Update 2 06-12-17: yeah i was happy, and soo i was going back to normal, i installed twrp, and root, phone boot up and again bye bye signal.
Update 06-14-17: Turns out that since I got to Colombia a month ago, this country has like a national IMEI list. Since I didn't subscribe my device the carrier blowies my phone and that why I had no service... Soo this ends my journey with the no service problem. They fixed it
Click to expand...
Click to collapse
I can not have a case if you are not resolve. Im vietnames my english very bad sory!. Help me
Hello all,
Earlier today, I was browsing a website for a game on my phone when it rebooted. It continued into a reboot loop at which point no matter what I did, nothing worked. TWRP wasn't working, and I wound up flashing the phone several times with both stock Android as well as Pure Nexus. While I was able to fix TWRP, whenever I attempt to flash Beans G'Apps, the phone reboots again and stays in the reboot loop. I'm unfortunately unable to flash the image using that means. I feel like I've made progress on this issue, but everything else isn't working.
Does anyone have any suggestions on what I can do in order to be able to stop the boot loop and save my device?
Thanks!
Flash stock firmware
DanPLewis said:
Hello all,
Earlier today, I was browsing a website for a game on my phone when it rebooted. It continued into a reboot loop at which point no matter what I did, nothing worked. TWRP wasn't working, and I wound up flashing the phone several times with both stock Android as well as Pure Nexus. While I was able to fix TWRP, whenever I attempt to flash Beans G'Apps, the phone reboots again and stays in the reboot loop. I'm unfortunately unable to flash the image using that means. I feel like I've made progress on this issue, but everything else isn't working.
Does anyone have any suggestions on what I can do in order to be able to stop the boot loop and save my device?
Thanks!
Click to expand...
Click to collapse
Maybe start from scratch flash the factory image threw fastboot and start over.
pacods61 said:
Maybe start from scratch flash the factory image threw fastboot and start over.
Click to expand...
Click to collapse
I had tried that but to no success. I will try this again. Do you have any guides or anything for that?
Edit: I have gone through and attempted to use fastboot to flash two different images... N2G47H and N2G47W. I'm still getting the same result. Since doing this, I've also attempted going back into Recovery (non-TRWP) and doing factory reset that way. Nothing.
So apparently this has been a known issue possibly. I don't know if for a fact this is the hardware issue, or the fact I had Pure Nexus installed on it... it would also explain why Google is so readily going to give me a new phone even though my warranty is expired.
I can't post the reddit links due to new XDA account, but they are there.
DanPLewis said:
So apparently this has been a known issue possibly. I don't know if for a fact this is the hardware issue, or the fact I had Pure Nexus installed on it... it would also explain why Google is so readily going to give me a new phone even though my warranty is expired.
I can't post the reddit links due to new XDA account, but they are there.
Click to expand...
Click to collapse
How did you get Google to replace your phone? I bought mine from Swappa and warranty just expired in April
ornwilson said:
How did you get Google to replace your phone? I bought mine from Swappa and warranty just expired in April
Click to expand...
Click to collapse
This is DanPLewis under my account account (Wasn't able to remember credentials initially!). So my phone was purchased from Google for Google Fi. I reached out to their support chat. First they informed me that my phone warranty expired 3 months ago in March. I asked what options I have right now for replacement, and they voluntarily told me that they will go ahead and do a one time refurbished replacement.
The reasoning I feel as though they replaced it out of warranty was because they're aware of the issue with the phone... but they could've just been nice about it.
Punkrulz24 said:
This is DanPLewis under my account account (Wasn't able to remember credentials initially!). So my phone was purchased from Google for Google Fi. I reached out to their support chat. First they informed me that my phone warranty expired 3 months ago in March. I asked what options I have right now for replacement, and they voluntarily told me that they will go ahead and do a one time refurbished replacement.
The reasoning I feel as though they replaced it out of warranty was because they're aware of the issue with the phone... but they could've just been nice about it.
Click to expand...
Click to collapse
OK, thanks. That does seem good of them.
hello to all, my Nexus 6p, after an official update, restarted and stopped on the Google logo. i tried to flesh a firmware stock via fastboot but it does not work. the phone is original with bootloader locked, i can handle it in fastboot mode. is there a way to flesh the stock firmware? In the Nexus with locked bootloader
Thanks
ADB sideload the OTA
I cant enter in recovery only fastboot mode
BLOD?? If you can enter fastboot but not recovery and it never boots passed the google screen you might be boned.
bootloop. logo loop...
I have the same problem does not pass the logo and restart, but I can enter the recovery and fastboot.
all this with the oem blocked.
I clarify that I did not find the system of the dryer nor freezing the telephone.
exp.:crying:
I do not know how you define it ... but my nexus 6p, never unlocked, always kept original, after an ota update, has remained fixed on the google logo, with the key combination i go only in fastboot mode .. ...strange? but it is so...
how do you call it? hard brick? soft brick?
for me it's hard brick since i can not flesh the firmware ...
Fun with Warranties
iaio72 said:
hello to all, my Nexus 6p, after an official update, restarted and stopped on the Google logo. i tried to flesh a firmware stock via fastboot but it does not work. the phone is original with bootloader locked, i can handle it in fastboot mode. is there a way to flesh the stock firmware? In the Nexus with locked bootloader
Thanks
Click to expand...
Click to collapse
I was a die hard and avid 6P fan. It was literally the best phone I have ever used...when it worked.
When I was still under Huawei's 1 year manufacturer warranty I ended up sending it in twice. Each time they sent me a new handset as they couldn't fix it.
Once I was off of Huawei's warranty I had to deal with my Square Trade insurance. They couldn't fix it either and opted to send me a check. I only bought the phone once but ended up owning three different handsets over the course of less than a year and a half.
Your best bet, in my experience, is if you're still under warranty send it in and get a new one. Huawei's US based customer service was nothing but excellent every time I interacted with them.
Good Luck,
Ben
thanks for your message, my nexus is still under warranty, sent to huawei italia, the phone I picked up after a month, they could not fix it because it is not an Italian guarantee but a European guarantee, they told me to contact the shop where I bought it, but the store is closed for bankruptcy ...
my only way to resuscitate the phone, I think I'm getting a tools that installs the firmware, having the bootloader locked ...
iaio72 said:
thanks for your message, my nexus is still under warranty, sent to huawei italia, the phone I picked up after a month, they could not fix it because it is not an Italian guarantee but a European guarantee, they told me to contact the shop where I bought it, but the store is closed for bankruptcy ...
my only way to resuscitate the phone, I think I'm getting a tools that installs the firmware, having the bootloader locked ...
Click to expand...
Click to collapse
That sound sketchy!
Don't accept such an answer that your phone is still under guaranty but not in Italy!
Huawei are an international company.
Use this link with your IEMI to verify your device is under warranty and if it is simply contact Huawei UK for instance.
http://consumer.huawei.com/us/support/warranty-query/
Checked with them last week and they agreed to fix my device free of charge.
http://consumer.huawei.com/en/contact-us/
So a few weeks ago I posted this Thread, where I described, that I had this problem, where my phone just gets stuck suddenly and wont do nothing, but bootlooping. I downloaded a stock rom and flashed it via Odin, but it still wouldn't boot, so I put it aside, cause I couldnt handle it while having examns.
Yesterday I went ahead and charged it and gave it a shot and it started. First things first, I activated USB-Debugging and OEM-Unlock.
Now to my question. In the other post I mentioned, that OEM wasnt unlocked, but now it is.
If the problem still occurs, do I have another possibility now with OEM unlocked, which I could try to solve the problem of having bootloops all the damn time? (At the end it wouldnt start at all, only bootlooping)
I really think this is a hardware defect, but maybe there is still the possibility, that it might be another kind of software problem, which could be solved?
Thank you guys in advance!
Hayalamm
I had the same problem, so i rooted my phone and installed a custom rom. Still had the problem of phone suddenly freezing and looping, also froze on the boot samsung logo. I took it to a shop and they said motherboard problem. Since the repair cost was too much, i went and bought a used s7 edge instead, i still have the old somewhere in the store room.
fahad_sikder said:
I had the same problem, so i rooted my phone and installed a custom rom. Still had the problem of phone suddenly freezing and looping, also froze on the boot samsung logo. I took it to a shop and they said motherboard problem. Since the repair cost was too much, i went and bought a used s7 edge instead, i still have the old somewhere in the store room.
Click to expand...
Click to collapse
Basically, I'll never buy a Samsung again, until there are no such problems anymore... Never had such a problem with oneplus or huawei..