Related
Hi, my headphone jack has always been pick about having things plugged in just right, usually the slightest bit of ling screws it up. Finally today, it just started giving serious static in right side. when music or any sound starts it goes away, but the volume is very low on that side. It only does it when there is power (battery is in), so I think it is a bad connection in there. I have some questions regarding this.
1. How horrible is the Motorola service? they say 5-7 days, but is that really the case (In the U.S.). My warranty is still good, I'll just flash back to stock.
2. will opening the phone up void my warranty? I am somewhat experienced with electronics, so I could probably fix it, but I don't wantt to void the warranty in case it doesn't work.
3. I also have a stuck pixel on my screen that has been there since I got the phone (New). Will they fix that as well even though I can only select one problem on the application form? Should I mention it as well so that they might fix it?
Thank you,
-lkrasner
P.S. Unfortunately this means that I might be unable to do much for a while when I send my phone away. I hope you guys get ICS without me, and I will be waiting to try it out myself.
lkrasner said:
Hi, my headphone jack has always been pick about having things plugged in just right, usually the slightest bit of ling screws it up. Finally today, it just started giving serious static in right side. when music or any sound starts it goes away, but the volume is very low on that side. It only does it when there is power (battery is in), so I think it is a bad connection in there. I have some questions regarding this.
1. How horrible is the Motorola service? they say 5-7 days, but is that really the case (In the U.S.). My warranty is still good, I'll just flash back to stock.
2. will opening the phone up void my warranty? I am somewhat experienced with electronics, so I could probably fix it, but I don't wantt to void the warranty in case it doesn't work.
3. I also have a stuck pixel on my screen that has been there since I got the phone (New). Will they fix that as well even though I can only select one problem on the application form? Should I mention it as well so that they might fix it?
Thank you,
-lkrasner
P.S. Unfortunately this means that I might be unable to do much for a while when I send my phone away. I hope you guys get ICS without me, and I will be waiting to try it out myself.
Click to expand...
Click to collapse
Just do a mis-flash or delete the system partition and take it into a store and tell/show them it does not boot, that you picked it up off the charger and it was like that, and you need a replacement. They will send you a replacement and you have 30 days to return your "broken" phone. I have done this 4 times with my A2s.
jimbridgman said:
Just do a mis-flash or delete the system partition and take it into a store and tell/show them it does not boot, that you picked it up off the charger and it was like that, and you need a replacement. They will send you a replacement and you have 30 days to return your "broken" phone. I have done this 4 times with my A2s.
Click to expand...
Click to collapse
But my AT&T warranty is up?!?! will it still work? I still have my 1 year moto warranty.
Edit: If this does work I owe you something huge, plus I would get my screen problem fixed
EDIT 2: would I be better off just deleting something that would just stop if from booting past the boot logo (big M) so it wouldn't be so obvious that I just killed it with is basically sayins so on the fastboot screen. If so what could I delete that wouldn't prove I had rooted, probably nothing now that I say that.
lkrasner said:
But my AT&T warranty is up?!?! will it still work? I still have my 1 year moto warranty.
Click to expand...
Click to collapse
That is the Moto warranty, AT&T will just help you "file" it since it is done through them anyhow.
Just don't call moto yourself.
jimbridgman said:
That is the Moto warranty, AT&T will just help you "file" it since it is done through them anyhow.
Just don't call moto yourself.
Click to expand...
Click to collapse
sweet, I will try that, what should I do to brick just erase system with fastboot? isn't that really obvious? or are all the employees just stupid. Obviously I need to do something recoverable so that i can get it back if it doesn't work.
lkrasner said:
sweet, I will try that, what should I do to brick just erase system with fastboot? isn't that really obvious? or are all the employees just stupid. Obviously I need to do something recoverable so that i can get it back if it doesn't work.
Click to expand...
Click to collapse
Do anything that will make it either boot loop or stick on the dual core/moto boot screen. Whacking system/boot should do that, and you can still flash it back to stock before you send it back if you really want to.... they are just going to fully refurb it and re-sell it...
The secret is to act dumb, pretend like you know nothing bout flashing and this site... just act like it just went nuts and started this, and it will not boot.
Ask for the advanced replacement.
jimbridgman said:
Do anything that will make it either boot loop or stick on the dual core/moto boot screen. Whacking system/boot should do that, and you can still flash it back to stock before you send it back if you really want to.... they are just going to fully refurb it and re-sell it...
Click to expand...
Click to collapse
OK, and they will not be able to see root then, and if they flash it back to stock it will no longer be rooted, so I should be fine. I opened a service request with Moto earlier, do you think that will be a problem? Should I wait until it expires so they don't get suspicious that I bricked it on purpose.
lkrasner said:
OK, and they will not be able to see root then, and if they flash it back to stock it will no longer be rooted, so I should be fine. I opened a service request with Moto earlier, do you think that will be a problem? Should I wait until it expires so they don't get suspicious that I bricked it on purpose.
Click to expand...
Click to collapse
if it is borked when you take it to the store they can't see that it is rooted cause it won't boot... all they are going to do it call their 1-800 number and help you file a support request... then the person the phone will let you know of the "requirements" and ask if the phone has any visible water damage, yadda yadda...
Then they will send you a new phone and you should get it in 3 or so days and you are supposed to send the old one back in the SAME box... so you will already have flashed the fxz and been using the phone the whole time you waited for the new one to show up... just don't forget to send it back... I did and waited until 25 days later, and I was bugged mercillessly by att...
Just make sure you factory wipe and take out your sim and SDcard, and battery door... they do not send anything but the core of the phone, no batt or batt door or anything.
lkrasner said:
OK, and they will not be able to see root then, and if they flash it back to stock it will no longer be rooted, so I should be fine. I opened a service request with Moto earlier, do you think that will be a problem? Should I wait until it expires so they don't get suspicious that I bricked it on purpose.
Click to expand...
Click to collapse
@jim on playing dumb,hilarious ..i do that when i upgrade my phone.im such an ass when i upgraded to a2 from xperia x10 that i didnt even bother restoring it to stock, i left cm7 on it,custom bootlogo ,said "free xperia team" on boot.i just pretended i didnt know what happend. it was so enjoyable.
service rep - "it appears to be rooted"
My response - "What do you mean rooted? It has roots like a plant?".
@krasner
You worry to much,they cant prove anything.just brick it and youll be fine.u could even play dumb as u crack a smile while doing so and they still really cant do anything to prove u did it and have to exchange it.
Sent from my MB865 using xda premium
worked beautifully! I deleted build.prop and default.prop, so it just went to a black screen after the moto logo. when the guy called the warranty center he said it was "extremely defective and clearly in need of replacement."
After I walked out, I went home, booted into bp tools, taking me to cwm and used adb to push the two files back. The phone already shipped.
However I am thinking of selling it BNIB and getting something else, any ideas what I could get for it
lkrasner said:
worked beautifully! I deleted build.prop and default.prop, so it just went to a black screen after the moto logo. when the guy called the warranty center he said it was "extremely defective and clearly in need of replacement."
After I walked out, I went home, booted into bp tools, taking me to cwm and used adb to push the two files back. The phone already shipped.
However I am thinking of selling it BNIB and getting something else, any ideas what I could get for it
Click to expand...
Click to collapse
Maybe 150. It wont be "NIB" you will not get a box, batt, back cover, etc. With the replacement.
Sent from my SAMSUNG-SGH-I747, running CM9, using xda premium
So I have a droid Bionic my friend went through much pains to root. Fast forward a year and I probably got a virus on it and it ran like crap. So I went ahead and reset it to factory default. I have no phone plan or data plan anymore.
After the factory restore, when I boot up the droid, it says -Safe Strap: Disabled- in bold red text with the little robot lower down. Next I get a screen that says -Welcome; Select your language:- I select English and hit -Start- and I'm then greeted with a new screen -A SIM card is needed to operate this phone. Please turn off your phone and insert you SIM card.- and I get two options -Emergency Call- and -Power Off- and that's it.
So it's safe to assume my phone is still rooted and I'm pretty certain I need to trick my phone into thinking it has a SIM so that it boots up. I have tried putting in other SIM cards with data plans and it gives me the same crap. I'm not a complete techno noob I just know next to nothing about modding phones in any capacity. Any advise or direction would be much appreciated. Thank you.
RAKATIKA said:
So I have a droid Bionic my friend went through much pains to root. Fast forward a year and I probably got a virus on it and it ran like crap. So I went ahead and reset it to factory default. I have no phone plan or data plan anymore.
After the factory restore, when I boot up the droid, it says -Safe Strap: Disabled- in bold red text with the little robot lower down. Next I get a screen that says -Welcome; Select your language:- I select English and hit -Start- and I'm then greeted with a new screen -A SIM card is needed to operate this phone. Please turn off your phone and insert you SIM card.- and I get two options -Emergency Call- and -Power Off- and that's it.
So it's safe to assume my phone is still rooted and I'm pretty certain I need to trick my phone into thinking it has a SIM so that it boots up. I have tried putting in other SIM cards with data plans and it gives me the same crap. I'm not a complete techno noob I just know next to nothing about modding phones in any capacity. Any advise or direction would be much appreciated. Thank you.
Click to expand...
Click to collapse
you put a sim in from the carrier the bionic was made for or is compatible with and it didnt work?
do you have the old sim you used to use in the bionic?
i get a new sim every time i get a new phone and keep the burned one, as it will still activate the phone even though it doesnt work otherwise.
im pretty sure there is a trick that will get you past that screen. it involves tapping the 4 corners of the screen counter clockwise. i dont recall where to start, try searching for more info on it.
as for the root, yea, i remember rooting my bionic last time, and it sucked a lot lol. anyways, it "should" still be rooted, just put a superuser app back on and confirm. the su app is gone, thats why ss is disabled.
bweN diorD said:
you put a sim in from the carrier the bionic was made for or is compatible with and it didnt work?
do you have the old sim you used to use in the bionic?
i get a new sim every time i get a new phone and keep the burned one, as it will still activate the phone even though it doesnt work otherwise.
im pretty sure there is a trick that will get you past that screen. it involves tapping the 4 corners of the screen counter clockwise. i dont recall where to start, try searching for more info on it.
as for the root, yea, i remember rooting my bionic last time, and it sucked a lot lol. anyways, it "should" still be rooted, just put a superuser app back on and confirm. the su app is gone, thats why ss is disabled.
Click to expand...
Click to collapse
Yeah the original sim is in the bionic. I haven't had a phone plan in my bionic for years and just used it off wifi to get great apps when I have wifi. I've tried new sims and old.
So today(5-15) I saw online that T-Mobile USA released the 5.1.1 OTA for there branded Galaxy S6/S6 Edge, so any info on when the Verizon branded version is coming out? I'm having multiply major bugs(wifi, memory, and lagging) across 3 different S6 devices(original device and 2 replacements) since launch day. Also, the Verizon Branded OTA that just came out brought me new bugs like with Google voice to text giving me 2 new bugs and making it unusable. Also, apps are freezing like crazy and ends up freezing the whole phone and when I try to lock the phone with the power button when an app is freezing it opens up the camera instead of locking the phone and most of the time I have to restart the phone when this happens and it happens quite often, but only started after the Verizon OTA. Also, from launch day(across all 3 devices) I been having memory issues with the phone, it tells me it has between 1GB-1.2GB of total memory on the phone and I only have 748MB total available with only very few apps on the phone at the moment, everything closed and all the bloatware gone off the phone. I herd that the Verizon OTA we just got was suppose to fix the memory issue, but apparently for me it did nothing at all with the memory on my phone. and lastly I'm having the major wifi bug a lot of us are having witch for me started on the 6th day after launch and never worked again even after I had 3 different devices and still the same thing is still ongoing, and in fact the Verizon OTA we just got made the wifi bug even worst then before.
So the 5.1.1 OTA is really needed for me to fix these ongoing and new bugs I'm having and after 2 months I'm getting sick and tired of waiting for patches to come out!
You probably should go into your system recovery and clear cache. That will probably help a majority of your bugs.
charlesvw9 said:
You probably should go into your system recovery and clear cache. That will probably help a majority of your bugs.
Click to expand...
Click to collapse
I already did that and nothing changed at all, and like I said I had 3 different devices and nothing changed at all. In fact the 3rd device I got which I still have was giving me problems from very first time I turned it on and during the initial setup as soon as I turned it on from the FedEx box and the keyboard was slow and not putting the letters I clicked in the box and to click next/skip, restart or power off I had to use my pointer finger and press multiple times and fast like a woodpecker would on a tree in order for those functions to respond, and before I can even finish the initial setup I had to already do a factory reset on the phone. Even typing right now in this box responding to you the phone is lagging just typing now.
Don't think Verizon has announced anything yet. The current G920VVRU1A0E2 works fine for me.
To help with keyboard lag - go into settings and make sure the proper language is intalled and updated. Have you tried different keyboards? Swiftkey?
krelvinaz said:
Don't think Verizon has announced anything yet. The current G920VVRU1A0E2 works fine for me.
Click to expand...
Click to collapse
Same here and I'm in no hurry to lose root.
krelvinaz said:
Don't think Verizon has announced anything yet. The current G920VVRU1A0E2 works fine for me.
Click to expand...
Click to collapse
Well 3 different phones since launch day have been giving me all different kinds of problems and never had a device with out a major problem in it and the new Verizon OTA that just came out in June made the phone even worst then before. The Build for the update is G920VVRU1A0E2, and in fact I even had problems getting the update on my phone because from launch day of the OTA-4days after it came out the OTA would not fully download and give me error code 503 and it wasn't until the 5th day that it worked and then when I finally got it installed on my phone it just brought more bugs to the phone like I talked about in the OP
bigj0110 said:
Well 3 different phones since launch day have been giving me all different kinds of problems and never had a device with out a major problem in it and the new Verizon OTA that just came out in June made the phone even worst then before. The Build for the update is G920VVRU1A0E2, and in fact I even had problems getting the update on my phone because from launch day of the OTA-4days after it came out the OTA would not fully download and give me error code 503 and it wasn't until the 5th day that it worked and then when I finally got it installed on my phone it just brought more bugs to the phone like I talked about in the OP
Click to expand...
Click to collapse
Have you tried using Odin to flash back to stock with the full tar file instead of the update? If not go here and give it a shot. If you use the OE2 one you will have to factory data reset to wipe your phone clean either after or before you flash.
charlesvw9 said:
To help with keyboard lag - go into settings and make sure the proper language is intalled and updated. Have you tried different keyboards? Swiftkey?
Click to expand...
Click to collapse
yea I tired that, but this started as soon as I turned on my phone for the very 1st time trying to do the initial set up, plus like I said even pressing next/skip, power off or reset in the initial setup was a hassle. I had to take my pointer finger and point it down and press fast and many times like a woodpecker in order for the buttons functions to work and I could not even finish the initial setup and had to already do a factory reset before the initial setup was even finished on the 3rd device I have now. The phone is so bad that even clicking the home button some of the apps, Google search and weather is not on screen right away and takes second or 2 to show up, its lagging to show up.
Misterxtc said:
Have you tried using Odin to flash back to stock with the full tar file instead of the update? If not go here and give it a shot. If you use the OE2 one you will have to factory data reset to wipe your phone clean either after or before you flash.
Click to expand...
Click to collapse
Thanks, but I already did that last night and still the same thing nothing different at all changed for me, it was a complete waste of time!
bigj0110 said:
Thanks, but I already did that last night and still the same thing nothing different at all changed for me, it was a complete waste of time!
Click to expand...
Click to collapse
That stinks, hopefully the next update will fix things for you. Mine has been running fine for the most part.
Misterxtc said:
That stinks, hopefully the next update will fix things for you. Mine has been running fine for the most part.
Click to expand...
Click to collapse
3 different devices and still the same exact major things plus new things on each device are going on with the phone. Switching out the device should fix it all, but I guess this is not the case here. Plus about the wifi issues I'm in a XDA forum 13 pages long about the phones wifi not working(I know it says edge, but it's the same problems with the S6 and S6 edge so no difference)
http://forum.xda-developers.com/galaxy-s6-edge/help/wifi-dropping-t3079504
I would not be surprised to see that the new upgrade to lollipop was to foil or prevent root. Kind of like the s4. screwed up everything now I have no root.
THANKS SAMSUNG !!!!!!
traco1 said:
I would not be surprised to see that the new upgrade to lollipop was to foil or prevent root. Kind of like the s4. screwed up everything now I have no root.
THANKS SAMSUNG !!!!!!
Click to expand...
Click to collapse
They already said that the new update(5.1.1) is taking away root
My 1st phone which arrived on Sat came with G920VVRU1A0E2 out of the box.
Other than normal setups, and uninstalling Google Play Services and Google Play it has not had any problems.
Perhaps you should go into a store and show them how it is not working?
traco1 said:
I would not be surprised to see that the new upgrade to lollipop was to foil or prevent root. Kind of like the s4. screwed up everything now I have no root.
THANKS SAMSUNG !!!!!!
Click to expand...
Click to collapse
Ya you're thanking the wrong company here. You need to thank Verizon...
krelvinaz said:
My 1st phone which arrived on Sat came with G920VVRU1A0E2 out of the box.
Other than normal setups, and uninstalling Google Play Services and Google Play it has not had any problems.
Perhaps you should go into a store and show them how it is not working?
Click to expand...
Click to collapse
I did on launch day, I went back to the same corporate store a few hours later and got into a fight with the sales rep who sold me the phone a few hours earlier and the store GM because they were Ignorant because my phone was hot as fuc k at 90F and hotter and they said nothing was wrong. On top of that they even lied to me about having the edge devices in stock on launch day and even pulled out the normal S6 trying to trick me and it was not until I said something did he say oh this is not an edge and then said there was no edge's in stock, but while I was waiting in line I asked him and 2 other reps and they all said they had the white 64GB edge in stock. They rather lie to there customers to make a sale then tell the truth(at least this corporate store location), and then when you have problems with the phone they don't care to help you at all. Even 611 said this was very wrong and made a complaint on mine and 611's behalf on the corporate store and the sales rep.
Misterxtc said:
Have you tried using Odin to flash back to stock with the full tar file instead of the update? If not go here and give it a shot. If you use the OE2 one you will have to factory data reset to wipe your phone clean either after or before you flash.
Click to expand...
Click to collapse
Here is an update, as of recently my phone is getting really really hot and temperatures of 120F+ and even Verizon technical support saw that through their diagnostic system as it was actually on those temperatures at that very moment when they were looking. Also, from me just being tech savvy and Verizon technical support confirming it as well this phone is also supposed to have a safeguard in the phone and if it gets too hot the device is upposed to power off on its own, but apparently the safeguard is not working because when the phone gets very hot the battery starts flashing and in the middle of the screen it tells me the phone is very hot and it only lets me click OK. If I'm charging the phone the battery flashes and say the same thing but just adds unable to charge, & I can unplug the charger and immediately plug it back in to the phone and it will start charging again and then a few minutes later it will give me the same message. When it's doing that its not supposed to tell me anything it's supposed to just shut off and its not doing so.
So there overheating policy states that I have to bring my phone too a corporate store and they're going to replace the device right on spot. So Sunday I went to the corporate store to do that, but for some reason their system wouldn't allow them to process this because it didn't have an option to do it and the general manager and the store representative we're booth trying together for at least 45 minutes. They ultimately ended up just sending me a replacement device via Fedex to my house and when the phone arrives today(7-2) I have to bring the overheating device that I currently have to the store so they can do what they need to do to send it back because by law I'm not allowed to send an overheating device back. Verizon corporate store processed my order on Sunday and I was supposed to get the device on Tuesday but I'm getting it today due to inclement weather at the FedEx Memphis Tennessee hub and so Fedex at the Memphis Tennessee hub was at a complete standstill and my package was part of it.
Once I get my 4th replacement device and start using it for a while I will let you know how it's working
Hi all. I need help, or opinions, or both. I'm here because my husband used to tell me these forums were helpful. (Pleasebehelpful,pleasebehelpful)
I have an At&t Lg G4, the H810 model. It randomly shut itself down and refuses to start up again. It will load up to the LG logo, then shuts off and tries again. It's been doing that for a few days, as I keep hoping it will randomly make it all the way through and actually start up. I've read some of the many threads about the bootloop issues, but they all seem to be people who've been experimenting with mods.
I haven't rooted, or anything. It's still running on whatever it had when I walked out of the store with it. I've talked with At&T, and LG, and have the option to either fix it or get a refurb to replace it. I'm anxious about the refurb, as it seems that this is not an uncommon issue with the G4s. Is there a way to tell when the refurb was made, or what they've done to make it "like new?"
I'm feeling like it's a bit of a crapshoot. Last time I went through warranty replacement was with a Samsung Galaxy, and that was a hideous ordeal. Is LG better? Anybody have any experience, or sage wisdom to impart? Nifty tricks to get the thing to start back up?
TIA!
Google search "Lg g4 return to stock" and flash the h81010o firmware in the instructions. This provided you can enter download mode.
Sent from my LG-H810 using Tapatalk
That's exactly what happened to mine. It randomly shut down and now it is stuck in a bootloop. Usually it won't pass the LG splash screen, but a few times I've seen the AT&T logo briefly. Twice it showed the "Configuring apps" screen as if it had been updated. I didn't allow an OTA update but that's what it looked like.
After 20 minutes on (another) phone with tech support they decided to send a warranty replacement.
I wish I knew what was wrong but it is essentially bricked. Can't hard reboot, get to download/recovery mode or even power off.
The phone is not rooted or otherwise modded.
I just wanted you to know you're not alone. All of this just happened today.
Sent from my SAMSUNG-SM-G920A using Tapatalk
redeyss said:
Google search "Lg g4 return to stock" and flash the h81010o firmware in the instructions. This provided you can enter download mode.
Sent from my LG-H810 using Tapatalk
Click to expand...
Click to collapse
Thanks, but not dice. There's nothing there. The only thing I could get to was the *push start and volume down buttons* factory reset mode, which then didn't do anything. Boo.
ccbutterfly said:
That's exactly what happened to mine. It randomly shut down and now it is stuck in a bootloop. Usually it won't pass the LG splash screen, but a few times I've seen the AT&T logo briefly. Twice it showed the "Configuring apps" screen as if it had been updated. I didn't allow an OTA update but that's what it looked like.
After 20 minutes on (another) phone with tech support they decided to send a warranty replacement.
I wish I knew what was wrong but it is essentially bricked. Can't hard reboot, get to download/recovery mode or even power off.
The phone is not rooted or otherwise modded.
I just wanted you to know you're not alone. All of this just happened today.
Sent from my SAMSUNG-SM-G920A using Tapatalk
Click to expand...
Click to collapse
ccbutterfly--how long have you had your phone? It's a frustrating thing to have it just *pfft* like that, isn't it? I bought mine the weekend they came out in June, and having read up for a while, it looks like there's a defect in some of the phones that were made before May. Just my luck. I went for the refurb. Hope it doesn't have the same problem in a few months.
circetwo - I got it in June also. I bought it for my son's birthday on 6/29. It really was a surprise and a huge disappointment as the phone is otherwise everything we hoped it would be. I wish I had ordered one for myself instead of getting the GS6. I've had to warranty replace it after only a few months also.
Best wishes for your refurb. I hope we both have better luck this time around.
You know what really gets me is AT&T's shipping policy. My oldest son upgraded to the Note 5 this week. They sent it overnight at no extra charge. He already had a working phone, but they got the new one to him the next day. My other son had the LGG4 and when it randomly decided to be stupid they offered him expedited shipping at *our* expense. We opted for standard free shipping and he's without a phone til it gets here. That seems backwards to me.
Incidentally, I slipped his SIM card into my oldest son's *old* phone so he has something to use in the meantime. But really, doesn't it seem like the warranty replacement should be the one that gets expedited?
Okay, stepping off my soapbox now.
Hey, thanks for the info that the "May" date seems to be the key. That gives me more hope for the replacement phone.
Sent from my SAMSUNG-SM-G920A using Tapatalk
After giving the V10 a month, I decided to swap it out (why is for another thread, I suppose). I had rooted and installed TWRP, so I used the stock files provided in the dev threads to go back to stock and relock the bootloader. I did a factory reset to make sure everything was working properly.
When I went to turn in the device, the guy at the store ran a phone code and got a code back from the network. Apparently, it does a check to make sure the device is the same one that I originally purchased and that it hasn't been rooted (in a Samsung phone's case, it checks Knox status as well). If it comes back as rooted or having ever been rooted, he said the system will deny the exchange. Mine passed (since thankfully LG's stuff can be completely reset), and I didn't volunteer that I had rooted it.
Just be aware that you need to go completely to stock in order to return the phone to swap out for a new one. I'll assume if your phone get's flagged in the system once, you can't ever return it, even if you try to flash back to stock again.
I love Jump on Demand, but I think it's going to keep me stuck unrooted for the most part - can't risk blowing $700.
Thanks for the heads up! With JUMP it shouldn't matter, but a device exchange may flag.
Sent from my LG-H901 using Tapatalk
I rooted my Note 4 and 5 with twrp aswell.... Did jump from both with no problem! My last jump was Nov. 15th for the V10 and the promo and had no problem, must be a new policy!!! But yes, always go back to stock before upgrade lol
That's good you passed the network check, I wonder how that works? When you rooted, did you freeze that weird pr.adapt app that kept requesting root access?
YrrchSebor said:
That's good you passed the network check, I wonder how that works? When you rooted, did you freeze that weird pr.adapt app that kept requesting root access?
Click to expand...
Click to collapse
I did freeze it, but the T-mobile app (which I use to check my data usage) still saw that my device was rooted, even though I never gave that app root access. However, when I start the app, I told it I didn't want it to share any info with T-mobile, so it shouldn't have had permission to report my root status to T-mobile (and apparently it didn't).
daveeckert said:
I did freeze it, but the T-mobile app (which I use to check my data usage) still saw that my device was rooted, even though I never gave that app root access. However, when I start the app, I told it I didn't want it to share any info with T-mobile, so it shouldn't have had permission to report my root status to T-mobile (and apparently it didn't).
Click to expand...
Click to collapse
Ahh OK, I guess that could be an important point then! I always disallow sending the diagnostics and such in the my T-Mobile app... Thank god. Hopefully it'll be OK. Thanks for the heads up!
I just jumped from a Note 5 to the V10. I reset the Note 5 using Kies, but knox was still tripped. No issue at the store. The G4 that I jumped from to go to the Note 5 also had been rooted/bootloader unlock, no issue when I did that either.
That's weird. I called a store and asked them this exact question before turning in my G3. She said it didn't matter and they were gonna wipe the phone. It's possible she didn't understand the question, but I turned it in with no issues and haven't received any calls over the few days I've had the V10. I'm on the basis Jump plan too.
No issues trading in my Knox-tripped Note 4 a couples months ago. Maybe just that one store is getting a little wacky with the checking lol
Unheard said:
I just jumped from a Note 5 to the V10. I reset the Note 5 using Kies, but knox was still tripped. No issue at the store. The G4 that I jumped from to go to the Note 5 also had been rooted/bootloader unlock, no issue when I did that either.
Click to expand...
Click to collapse
Just curious how you like the V10 vs. the Note 5? I kinda like the V10 hardware, but it seems there will be very little development done on this phone (I'm dying for CM in particular). Doesn't seem as popular as I had hoped it would be with the dev community. I'm considering the Note 5 as a JoD exchange (and thanks to OP for the heads up here), since there seems to be a lot of dev activity for it. Just don't know if I'll be able to deal with that hardware home button. Guess I'm picky.
I can't tell the number of rooted phones I've sent back to Verizon and T-mobile, never a word.
Sent from my LG-H901 using Tapatalk
YrrchSebor said:
Ahh OK, I guess that could be an important point then! I always disallow sending the diagnostics and such in the my T-Mobile app... Thank god. Hopefully it'll be OK. Thanks for the heads up!
Click to expand...
Click to collapse
Okay you could also block it with root cloak...
Sent from my LG-H901 using Tapatalk
Been on Verizon, Alltel, Sprint, and Ma'Bell. always rooted, never had e Problem. Just make shure you return to stock. I even exchanged a couple of Samsungs with Knox trip, Lucky I guess. I've heard Stories but never met anyone that has been returned or charged a device.
spg900ny said:
Just curious how you like the V10 vs. the Note 5? I kinda like the V10 hardware, but it seems there will be very little development done on this phone (I'm dying for CM in particular). Doesn't seem as popular as I had hoped it would be with the dev community. I'm considering the Note 5 as a JoD exchange (and thanks to OP for the heads up here), since there seems to be a lot of dev activity for it. Just don't know if I'll be able to deal with that hardware home button. Guess I'm picky.
Click to expand...
Click to collapse
Currently have the Note 5. I wouldn't say there is a lot of dev activity. Then again, I came from a Nexus 6. [emoji2]
I can tell you that this policy was implemented just a few weeks ago. I work for T-Mobile (Corporate Store) and every time you take a phone for Jump, Jump 2 or Jump on demand; the system is asking for a code (it doesn't matter if its android or ios) that the phone displays (usually a 3-4 characters) when you enter a "##" code. Then we enter it on the system and we either get a "thumbs up" or a "denied". I haven't seen a denial at my store, but when I saw this policy, the first thing that I thought was that it was looking for a modified system.
Cool, so no more Jump for me. Looks like a steady stream of Priv's, 950XL's, Moto's, or Nexuses.
xxdjvalexx said:
I can tell you that this policy was implemented just a few weeks ago. I work for T-Mobile (Corporate Store) and every time you take a phone for Jump, Jump 2 or Jump on demand; the system is asking for a code (it doesn't matter if its android or ios) that the phone displays (usually a 3-4 characters) when you enter a "##" code. Then we enter it on the system and we either get a "thumbs up" or a "denied". I haven't seen a denial at my store, but when I saw this policy, the first thing that I thought was that it was looking for a modified system.
Click to expand...
Click to collapse
I just got the V10 and traded in my rooted and ROM'd Galaxy S6 for it. She did the code thing, didn't bat an eye.
Sent from my LG-H901 using Tapatalk
xxdjvalexx said:
I can tell you that this policy was implemented just a few weeks ago. I work for T-Mobile (Corporate Store) and every time you take a phone for Jump, Jump 2 or Jump on demand; the system is asking for a code (it doesn't matter if its android or ios) that the phone displays (usually a 3-4 characters) when you enter a "##" code. Then we enter it on the system and we either get a "thumbs up" or a "denied". I haven't seen a denial at my store, but when I saw this policy, the first thing that I thought was that it was looking for a modified system.
Click to expand...
Click to collapse
What ## code do you enter?
I would imagine that code is more of a quick IMEI/"is the phone stolen" verification rather than checking for root.
daveeckert said:
After giving the V10 a month, I decided to swap it out (why is for another thread, I suppose). I had rooted and installed TWRP, so I used the stock files provided in the dev threads to go back to stock and relock the bootloader. I did a factory reset to make sure everything was working properly.
When I went to turn in the device, the guy at the store ran a phone code and got a code back from the network. Apparently, it does a check to make sure the device is the same one that I originally purchased and that it hasn't been rooted (in a Samsung phone's case, it checks Knox status as well). If it comes back as rooted or having ever been rooted, he said the system will deny the exchange. Mine passed (since thankfully LG's stuff can be completely reset), and I didn't volunteer that I had rooted it.
Just be aware that you need to go completely to stock in order to return the phone to swap out for a new one. I'll assume if your phone get's flagged in the system once, you can't ever return it, even if you try to flash back to stock again.
I love Jump on Demand, but I think it's going to keep me stuck unrooted for the most part - can't risk blowing $700.
Click to expand...
Click to collapse
No, he was pulling your leg. I turned in my note 4 with twrp and a custom rom in October and I had to do the same check, it's just a service code check to make sure it's the same one you bought from tmo, if it checked for root I would never be able to get a phone again because I flashed that phone so much. I talk to the guys at the store and told them I rooted do they.