First off, I just wanted to thank you guys for always being so helpful. It's really nice to have people like you to discuss things with.
I just bought a used Nexus 6P, and it seems to suffer from the battery shutoff issue once it gets below ~10%. The original owner bought directly from the Google Play store in Sept 2016, so it's still under warranty with Google, and I believe that means I should be able to RMA it.
Before I do anything, I'd like to have as much info as possible to make this go as smoothly as possible; I'm traveling out of the country at the end of May and I need a device that works pretty much flawlessly by then, so timing is a factor.
Question 1
If I make a Nandroid backup in TWRP, move it to my computer's Hard Drive, copy it onto the RMA replacement, and restore it, that would very quickly restore me to where I was with my current phone without any issues, correct?
If it matters, I'm unlocked, stock-rooted on 6.0.1 (MTC20L), stock kernel, and TWRP (v3.0.3.0 iirc.) I used Nexus Root Toolkit for all of this.
Question 2:
Besides the ones I've listed below, what common Nexus 6P issues do I need to watch for when I get my RMA device?
Device overheating
Bootlooping
Random Reboots
Powers down once battery is below __%
Microphone / call quality issues
Screen discoloration issues
Bent / broken volume buttons
Screen separating from device
Wifi / radio / bluetooth / gps issues? (not sure if this is relevant)
Question 3:
How does the RMA process actually work?
To RMA, do I just call the Nexus / Google support line, give them my IMEI, explain that I'm having the battery shutoff issue and request they send me a warranty replacement?
Are there additional steps I'll need to take because I'm not the original owner?
Do I have to send Google my phone for them to send me the replacement, or do they send me the replacement first and then I send them my current device once the replacement arrives?
What's the typical turnaround time between making the RMA request and receiving the new device?
Anything else I should know?
kwest12 said:
First off, I just wanted to thank you guys for always being so helpful. It's really nice to have people like you to discuss things with.
I just bought a used Nexus 6P, and it seems to suffer from the battery shutoff issue once it gets below ~10%. The original owner bought directly from the Google Play store in Sept 2016, so it's still under warranty with Google, and I believe that means I should be able to RMA it.
Before I do anything, I'd like to have as much info as possible to make this go as smoothly as possible; I'm traveling out of the country at the end of May and I need a device that works pretty much flawlessly by then, so timing is a factor.
Question 1
If I make a Nandroid backup in TWRP, move it to my computer's Hard Drive, copy it onto the RMA replacement, and restore it, that would very quickly restore me to where I was with my current phone without any issues, correct?
If it matters, I'm unlocked, stock-rooted on 6.0.1 (MTC20L), stock kernel, and TWRP (v3.0.3.0 iirc.) I used Nexus Root Toolkit for all of this.
Question 2:
Besides the ones I've listed below, what common Nexus 6P issues do I need to watch for when I get my RMA device?
Device overheating
Bootlooping
Random Reboots
Powers down once battery is below __%
Microphone / call quality issues
Screen discoloration issues
Bent / broken volume buttons
Screen separating from device
Wifi / radio / bluetooth / gps issues? (not sure if this is relevant)
Question 3:
How does the RMA process actually work?
To RMA, do I just call the Nexus / Google support line, give them my IMEI, explain that I'm having the battery shutoff issue and request they send me a warranty replacement?
Are there additional steps I'll need to take because I'm not the original owner?
Do I have to send Google my phone for them to send me the replacement, or do they send me the replacement first and then I send them my current device once the replacement arrives?
What's the typical turnaround time between making the RMA request and receiving the new device?
Anything else I should know?
Click to expand...
Click to collapse
I recently did and RMA for a bad screen.
1. You can do the restore, but I would only restore the data partition. No need to restore the partitions.
2. Check for screen response everywhere on the screen. In the developer option turn on "show screen touch". Make sure all points on the screen are good. My first replacement had a ¼ inch band that showed no response.
3 You can do it online. They will ask for a credit card and the will send an advance replacement with a shipping return label.
kwest12 said:
First off, I just wanted to thank you guys for always being so helpful. It's really nice to have people like you to discuss things with.
I just bought a used Nexus 6P, and it seems to suffer from the battery shutoff issue once it gets below ~10%. The original owner bought directly from the Google Play store in Sept 2016, so it's still under warranty with Google, and I believe that means I should be able to RMA it.
Before I do anything, I'd like to have as much info as possible to make this go as smoothly as possible; I'm traveling out of the country at the end of May and I need a device that works pretty much flawlessly by then, so timing is a factor.
Question 1
If I make a Nandroid backup in TWRP, move it to my computer's Hard Drive, copy it onto the RMA replacement, and restore it, that would very quickly restore me to where I was with my current phone without any issues, correct?
If it matters, I'm unlocked, stock-rooted on 6.0.1 (MTC20L), stock kernel, and TWRP (v3.0.3.0 iirc.) I used Nexus Root Toolkit for all of this.
Question 3:
How does the RMA process actually work?
To RMA, do I just call the Nexus / Google support line, give them my IMEI, explain that I'm having the battery shutoff issue and request they send me a warranty replacement?
Are there additional steps I'll need to take because I'm not the original owner?
Do I have to send Google my phone for them to send me the replacement, or do they send me the replacement first and then I send them my current device once the replacement arrives?
What's the typical turnaround time between making the RMA request and receiving the new device?
Anything else I should know?
Click to expand...
Click to collapse
1) You can restore boot, system, and data. I suggest manually flashing the Vendor.img. However, you must remove the lock screen security completely. Due to the security measures regarding fingerprint sensor integrity, anything related to it's functionality is not covered by a TWRP backup. Restoring a TWRP nandroid on another device will make its fingerprint sensor malfunction. Perform the steps in post #9 of the thread linked below to have a working fingerprint sensor on the replacement device after restoring a TWRP nandroid:
https://forum.xda-developers.com/showthread.php?t=3307734
3) From what I've read on XDA, you need the original receipt from the Google Play transaction. So email the buyer and ask for their receipt.
Sent from my Nexus 5X using Tapatalk
can anybody confirm that when you send your device to Google we need to lock the bootloader flash stock recovery and img?
Also when chatting with google support should i tell them i am unlocked bootloader?
can somebody link the google chat support messaging I don't want to call them by phone.
AndrewM3 said:
can anybody confirm that when you send your device to Google we need to lock the bootloader flash stock recovery and img?
Also when chatting with google support should i tell them i am unlocked bootloader?
can somebody link the google chat support messaging I don't want to call them by phone.
Click to expand...
Click to collapse
You need to go completely stock including flashing stock images and lock your bootloader. Don't tell them you unlocked it, there is no need to bring up something like that if they don't ask.
Related
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
[ABANDONED] My worries have been aliviated by the people posting here that T-Mobile did not check for an unlocked bootloader. That's enough for me to close the issue. If someone does need to find the answer to this question, feel free to pursue it otherwise I consider this [CLOSED]
-----edit above-----
I've already searched for this EXTENSIVELY and need more help. I have a similar problem to this thread (which wasn't resolved), but didn't want to revive a dead thread from Dec '10 to ask this.
First and most important question is: WILL I NEED TO DO THIS?> Will T-Mobile check for the unlocked bootloader on a broken-screen phone and will they notice my MIUI rom? (I'm REALLY worried about this because rooting my phone does void the warranty, but honestly I didn't break it. The screen just stopped working. Really worried = the search for a solution).
Is HTC warranty a better option? (I'm actually the second owner and the original owner is going to try to do the replacement)
I've realized that I can use Android Screencast to see what the phone is showing, and touch input still works on my phone (though Android Screencast isn't letting me use my computer mouse/keyboard to use my phone). This is only available on a rom/backup with USB debugging enabled, and shows CWM Recovery (using the latest version).
Can someone please help me go through all the steps needed to restore everything to stock? I am cursed by this issue and realize that someone would need to take over an hour to figure all this out.
>>I know I'm asking for a lot, but this is a great community to be involved in and I've searched all over for help before posting.<<
__________________
P.S. I've also looked at [Guide] Remove permanent root, and I need to know what extra steps I will need to know with a broken screen. CWM 3.0+ presents a problem for stock rom, and I need one with USB debugging enabled already.
Also, fyi I used the Rage/Gfree latest version available as of Jan 24 (when I rooted). I did not flash the Engineering HBoot, which would probably help.
What i found was they dont care about the software. confirmed twice. Apparently it is a known defect in the phone that the screen stops working, they will admit it now. We have done 2 warranty replacements and the first one at the time of the post, they tried to charge me for breaking the screen (we did a better business bur Complaint) and got refunded. The second time they didnt even question it and we werent even charged.
So no they dont care, dont worry about it.
I just so happen to have the exact problem as you, i stepped on my phone leavng the screen internally broken put the touch screen still worked. I was running CM7 and i called them and just sent it in with no problems. there not there to look at the software and are not going to take the time to replace screens on all the phones they get in first to see if there rooted or not. If you cant tell its rooted by looking at the screen (i mean it is broken) then theres no way they will. Just send it in and you'll get it in about weeks time
I had this problem and submitted it to warrenty, anyway. They asked me three questions, is the screen cracked. Is there any external damage, and any water damage. All were no's, so they replaced the phone without ever checking for root.
Thanks for all the responses. All three of you have reassured me to the point that I'm not going to worry about it either. While I appreciate that T-Mobile is not going to charge me for rooting my device (which I should be able to do), I am annoyed that as a secondary owner I do not get warranty support and need to have the original owner take care of it.
daboma said:
Thanks for all the responses. All three of you have reassured me to the point that I'm not going to worry about it either. While I appreciate that T-Mobile is not going to charge me for rooting my device (which I should be able to do), I am annoyed that as a secondary owner I do not get warranty support and need to have the original owner take care of it.
Click to expand...
Click to collapse
Actually no, even if you are a second owner u can still get it replaced. I am also a second owner but I know a way to get it replaced. Pm me
Sent from my HTC Vision using Tapatalk
First than nothing, sorry for my bad english.
My N4 got bricked, the problem seems to be the battery because when plug in to the AC charger the LED blinks red and nothing else happens, other members have the same problem.
There is few post about it
- http://forum.xda-developers.com/showthread.php?t=2050811
- http://forum.xda-developers.com/showthread.php?t=2011328
- http://forum.xda-developers.com/showthread.php?t=2048066
- http://forum.xda-developers.com/showthread.php?t=2077331
So after try everything my nexus 4 seems to be dead, I decide to RMA but I don't know some details, and maybe you can help me
First, what I think I have to do:
I live out of USA, so I shipped my N4 to my cousin, he was who bought the N4, when he get my N4 then he will do the steps that Google tell him.
My doubt is:
1 - My bootloader is unlocked when my N4 start with the issue, perhaps Google can not turn on the device and be aware of it because the phone is fried, so if they can not detect that the bootloader is unlocked my RMA is free? (Assuming you have the bootloader unlocked means forfeiting RMA)
2- If they detect that my bootloader is unlocked, they will ignore this? Google will send me a replacement device? Although i going to be charged again (Assuming that Google is left with the charge of money they make to your account which remain in hold)
3- The replacement device is now yours? Or is just four use while Google check the original device?
4- How long take the whole process ?
So, this is all my questions by the moment, thank you and sorry for bad english, I used a little bit of Google Traductor.
D3m0x said:
First than nothing, sorry for my bad english.
My N4 got bricked, the problem seems to be the battery because when plug in to the AC charger the LED blinks red and nothing else happens, other members have the same problem.
There is few post about it
- http://forum.xda-developers.com/showthread.php?t=2050811
- http://forum.xda-developers.com/showthread.php?t=2011328
- http://forum.xda-developers.com/showthread.php?t=2048066
- http://forum.xda-developers.com/showthread.php?t=2077331
So after try everything my nexus 4 seems to be dead, I decide to RMA but I don't know some details, and maybe you can help me
First, what I think I have to do:
I live out of USA, so I shipped my N4 to my cousin, he was who bought the N4, when he get my N4 then he will do the steps that Google tell him.
My doubt is:
1 - My bootloader is unlocked when my N4 start with the issue, perhaps Google can not turn on the device and be aware of it because the phone is fried, so if they can not detect that the bootloader is unlocked my RMA is free? (Assuming you have the bootloader unlocked means forfeiting RMA)
2- If they detect that my bootloader is unlocked, they will ignore this? Google will send me a replacement device? Although i going to be charged again (Assuming that Google is left with the charge of money they make to your account which remain in hold)
3- The replacement device is now yours? Or is just four use while Google check the original device?
4- How long take the whole process ?
So, this is all my questions by the moment, thank you and sorry for bad english, I used a little bit of Google Traductor.
Click to expand...
Click to collapse
1.you have to call google for an rma
2.in my case, the send me a new one, including an envelope and the freightpapers for the old one
3. they authorize 349 euro on your credit card, but they just authorize it,they dont take it
4.if you receive the new device, you have to send the old device back to them within 21 days, otherwise they will take the 349 euros from your credit card
5. pray that they cant turn it on and you are good to go and you dont have to pay for it
6. in betwen 14 days you can keep the new device, dont know how they handle it over 14 days sorry
hope i could clearify some things lol
I live in Germany, had similar problems and doing the rma rightnow, too.
The replacement nexus 4 that you will get is yours. Until they checked your first nexus 4, they block the money for your replacement.
If your warranty isn't valid or the defect isn't covered by the warranty they will charge you for the replacement device.
Let's hope they cannot turn our devices on to check for an open bootloader
pa.pn2 said:
1.you have to call google for an rma
2.in my case, the send me a new one, including an envelope and the freightpapers for the old one
3. they authorize 349 euro on your credit card, but they just authorize it,they dont take it
4.if you receive the new device, you have to send the old device back to them within 21 days, otherwise they will take the 349 euros from your credit card
5. pray that they cant turn it on and you are good to go and you dont have to pay for it
6. in betwen 14 days you can keep the new device, dont know how they handle it over 14 days sorry
hope i could clearify some things lol
Click to expand...
Click to collapse
Qin-Root said:
I live in Germany, had similar problems and doing the rma rightnow, too.
The replacement nexus 4 that you will get is yours. Until they checked your first nexus 4, they block the money for your replacement.
If your warranty isn't valid or the defect isn't covered by the warranty they will charge you for the replacement device.
Let's hope they cannot turn our devices on to check for an open bootloader
Click to expand...
Click to collapse
Thank you guys! Really helped
Lesson learned: After root, ALWAYS block your bootloader
D3m0x said:
Thank you guys! Really helped
Lesson learned: After root, ALWAYS block your bootloader
Click to expand...
Click to collapse
Dont take a chance ! If you didn't send your device yet...
plug it into PC while holding ( VOL - )! JUST VOLUME DOWN ! no POWER KEY !
and when in fastboot mode, do :
Code:
fastboot oem lock
Dont take any chances ! ... They are super genuis ! I guess they can do anything to check the LOCK status !
miku3191 said:
Dont take a chance ! If you didn't send your device yet...
plug it into PC while holding ( VOL - )! JUST VOLUME DOWN ! no POWER KEY !
and when in fastboot mode, do :
Code:
fastboot oem lock
Dont take any chances ! ... They are super genuis ! I guess they can do anything to check the LOCK status !
Click to expand...
Click to collapse
Well bro, my phone its on the way to USA, but when my cousin get it, I'll tell that and lets see what happends...
I had no issues on 1836. I was on it all late last night. It was until I opened that benchmark app that went haywire.
Mentioned this in the other thread as well, but any idea what bin your CPU is?
Hey guys im in the same boat currently doing RMA. I have no red LED phone wont charge or turn on so hoping that Google cant either and Warranty holds.
No idea what bin I am im afraid. I have a hunch its fast or faster as I couldn't run matr1x v4.0 kernel and other people who also couldnt were fast bin (think it was due to the voltage tables).
RED LED fixed
hey guys, i've read a lot of threads about this red led issue and having the only solution was to RMA it.
just remebered the time when i had a RED LED after replacing my framework.apk that i have found in one the forums, after replacing the framework.apk, my phone cant respond to anything (screen touches and even power and volume button was not working) and after a minute my phone turned off. and i cant get it to turn on so i was panicking a bit knowing that i cant RMA my phone cause i only had my phone from my mother in UK and i'm in philippines so i plug my phone on the wall then the LED flashes RED ......
to make the long story short i tried everything to revive my phone and wugfresh's toolkit saved it, after a couple things the toolkit manages to flash the stock rom on my phone i was relieved.
that was just my experience, hope it help you guys
dannaoj said:
hey guys, i've read a lot of threads about this red led issue and having the only solution was to RMA it.
just remebered the time when i had a RED LED after replacing my framework.apk that i have found in one the forums, after replacing the framework.apk, my phone cant respond to anything (screen touches and even power and volume button was not working) and after a minute my phone turned off. and i cant get it to turn on so i was panicking a bit knowing that i cant RMA my phone cause i only had my phone from my mother in UK and i'm in philippines so i plug my phone on the wall then the LED flashes RED ......
to make the long story short i tried everything to revive my phone and wugfresh's toolkit saved it, after a couple things the toolkit manages to flash the stock rom on my phone i was relieved.
that was just my experience, hope it help you guys
Click to expand...
Click to collapse
Exactly what did you do in Wugfresh's toolkit to save it?
reaper000 said:
Exactly what did you do in Wugfresh's toolkit to save it?
Click to expand...
Click to collapse
i used the "flash stock +unroot"
shaded the soft-bricked/boot loop
Sent my device in for RMA over a week ago. Bootloader was unlocked and custom rom loaded. Same red light problem everyone else is having. Also ordered my replacement device which is still on back order.Charges have now cleared my credit card so no worries just in case anyone is worried they will not honor the warranty because you have unlocked and rooted the phone .Called google to find out where my replacement device is yesterday and they said that even the rma devices are on back order for 1 to 2 more weeks which really sucks!
So basically everyone here crashed their car ,it was their own fault, car not had an insurance and you expect to get a new one pretending it was manufacturing fault ?
Sent from my Nexus 4 using xda premium
You make too many assumptions, friend.
1. Not everyone browsing this topic has crashed their phone. I popped in while searching for Wug and toolkit, for instance.
2. It's their own fault: you know what "everyone here" did? Their phone use, their setup?
2a. It may not be manufacturing issue as much as a design flaw. Microsoft's Xbox "circle of death" comes to mind; this could be LG's version of that.
The Nexus line is known as the dev's phones, and devs push limits; that's inherent to development. Even experienced devs like Faux have had red LEDs.
The inability to yank the battery as a hard reset has always troubled me in this kind of environment. I hope Google's next phone corrects this
Sent from my Galaxy Nexus using Tapatalk 2
MattSkeet said:
So basically everyone here crashed their car ,it was their own fault, car not had an insurance and you expect to get a new one pretending it was manufacturing fault ?
Click to expand...
Click to collapse
Mine Nexus got the red led just now, never rooted, everything stock
[Update: after sometime connected to the computer the battery charging icon appeared and it booted]
Update on my RMA process. I noticed today that I have a new pending $299 authorization on my card and I am trying to find out why. The original $299 authorization that was placed on my card when I first started the RMA has now cleared because I had already sent the defective device back for repair and a few days later the pending charge went away. Now I am wondering why in the hell they placed a new $299 charge again even though my replacement device has not even shipped! Google has really dropped the ball on this whole nexus 4 situation!
If you take it apart and actually take the battery out, as a proper hardware reset, will that work? Anyone tried this?
Meleagru said:
If you take it apart and actually take the battery out, as a proper hardware reset, will that work? Anyone tried this?
Click to expand...
Click to collapse
Well, here's a thread that I started that addresses that question directly:
http://forum.xda-developers.com/showthread.php?t=2103451
Here's an update; it seems one brave soul did pull the Nexus 4 battery. Check out this thread : http://forum.xda-developers.com/showthread.php?t=2111947
Sent from my Nexus 4 using Tapatalk 2
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.
hello, my first post, I bought a Nexus 6P from ebay. It has an unlocked bootloader (I get the warning when I turn it on) and the os build number is "angler-userdebug 8.1.0 OPM3.171019.01445.3998 dev-keys". there are applications that are not uninstallable: Better Bug, Nexus Logger, Traceur, and Volta. My question is, is this device suitable for personal use the way it is? any other information and/or suggestions are appreciated.
sarmid said:
hello, my first post, I bought a Nexus 6P from ebay. It has an unlocked bootloader (I get the warning when I turn it on) and the os build number is "angler-userdebug 8.1.0 OPM3.171019.01445.3998 dev-keys". there are applications that are not uninstallable: Better Bug, Nexus Logger, Traceur, and Volta. My question is, is this device suitable for personal use the way it is? any other information and/or suggestions are appreciated.
Click to expand...
Click to collapse
I am not sure about the rom version.
https://developers.google.com/android/images#angler
It sounds like somebody sold you a former test model from Huawei.
I can obly assume, that they sold remaining units, but after I searched a bit about those applications I can, like I said, only give you a vague assumption.
The important questions are -
Is the phone functional?Meaning: bootloop, sudden reboots, battery problems?
Are you able to use adb/fastboot? - > Is your phone being recognized by the command 'fastboot devices'?
Did you get a notification that is your system can be updated?
The unlocking of a bootloader isn't a reason to be distinctively suspicious?
But, if you are not satisfied with the phone in whatever way, you can demand to be refunded in regard of the unlocked bootloader with the argument, that the seller has tampered with it and should wrote it in the description.
I bought a phone a while ago and were unsatisfied with it, so I argued with the above mentioned and got my money back.
This was even from somebody private and there are no refund policies, besides the buyer protection.
If you have not passed thr chance and don't want to have a phone, which somebody has used most likely to flash a custom rom or recovery to root same phone, then go for it.
It is not a 100% bulletproof argument, but ebay excepted it, at leat in my case.
If you are okay with the device and adb/fastboot are working, in a way that you for example can test some commands, whicj you have to look up, but __don't flash anything__ as long as you are unsure of the condition.
If you want to remove these apps, you have to look them up, which is expandable and which isn't, before removing them.
And lastly - if you want to remove them, you have to root your phone (tutorials find you here en mass, the same goes for adb/fastboot usage).
But the same goes here for testing a ADB and fastboot usability, please.
If you decide to keep it, then you can remove system apps (>before a search if you phone goes boom..), aith this app for example
https://www.apkmirror.com/apk/jumobile/system-app-remover-root/system-app-remover-root-7-1-release/
With this, you are able to backup the apps if you want to remove them.
Some apps, especially the so-called 'bloatware' is from now on then, quite resistant.Just empty the trash, which you find in the app's menu.
Titanium Backup, a very, very versatile application, is fir example capable of backing up your entire apps including data, but I think, you have "some" pointers now and can give it (with carefulness) your own try.
Have fun & good luck