Related
Hey guys. Just got this phone yesterday. Rooted and unlocked the bootloader last night. Love the phone! I wake up this morning to an OTA update request. I haven't installed any recovery yet. I'm on a 926 and the phone is running 4.1.2.... Honestly, I haven't figured out how to install a recovery yet. I don't want to brick this thing on day 2. I've done quite a bit of stuff and I realize now I need to get more educated before I screw something up. Heck I haven't even taken the time to understand the difference between the 925 and 926. So will it hurt anything taking the OTA?
It's not worth it to take it. Better off going with a custom rom.
Sent from my PACMAN MATRIX HD MAXX
So I guess I need to work on installing a custom recovery.. Just curious, what is wrong with the OTA update?
jeph0r3 said:
So I guess I need to work on installing a custom recovery.. Just curious, what is wrong with the OTA update?
Click to expand...
Click to collapse
The OTA disables the hack that allows you to unlock the bootloader, but from everything I read if you have already unlocked the bootloader then you have nothing to worry about. It is still recommended to use a root keeper before taking the OTA update. The big advantage of the OTA is update radio drivers (better GPS, etc.)
OK, so, I'm rooted, unlocked, have rootkeeper installed and enabled, made a backup. If I take the OTA, can I get back to where I am now with my phone. I looked at each of the roms and they look OK.. Kinda happy with stock right now...
jeph0r3 said:
OK, so, I'm rooted, unlocked, have rootkeeper installed and enabled, made a backup. If I take the OTA, can I get back to where I am now with my phone. I looked at each of the roms and they look OK.. Kinda happy with stock right now...
Click to expand...
Click to collapse
The stock is surprisingly okay from Motorola (once you freeze the Verizon bloatware), but I really enjoy having 4.2.2 (dashclock widget alone makes it worth the upgrade), customizable lockscreen (I was using WidgetLocker but it's never as smooth as built in), and the phablet UI with the quick settings panel. Have I tempted you enough to try a ROM? Also, stock icons and not the ugly Moto icons!
bananapeapod said:
The stock is surprisingly okay from Motorola (once you freeze the Verizon bloatware), but I really enjoy having 4.2.2 (dashclock widget alone makes it worth the upgrade), customizable lockscreen (I was using WidgetLocker but it's never as smooth as built in), and the phablet UI with the quick settings panel. Have I tempted you enough to try a ROM? Also, stock icons and not the ugly Moto icons!
Click to expand...
Click to collapse
care to save me some time and let me know which is your favorite ROM so far? I'll end up trying a few just curious
jeph0r3 said:
care to save me some time and let me know which is your favorite ROM so far? I'll end up trying a few just curious
Click to expand...
Click to collapse
I've really only spent time with CM10.1 and have been very happy... a friend of mine has been going through the ROMs and he was excited about AOKP but now he's switching to Liquid can't remember why, some problems. From what I understand the CM ROM is likely to become official and that would be great so you can get the advantages of a fairly large eco system and constant development. Feel free to play around and try a ROM with halo (Pacman, Xenon, and some others seem to have it integrated) it looks really cool, but I'm not sure I would use it all the time.
@jeph0r3
So on Sunday, I made the mistake of "checking" to see if there was software update. There was. I did not want to update the phone, because I knew there was a good chance there was a root and unlock method out there for the current software version and wanted to investigate further. My only option was to "download now" or "download later" 12 hours.
12 hours came and went and I did not have the option to stop it. So I put it in WiFi mode and connected it to one of my WAPs that doesn't have internet access, which put a stop to the download. I did find a root/unlock method and went forward with it. Then the next question, what will happen when the download completes?
After rooting/unlocking the phone, I let the download complete, hoping that I didn't have to apply it. I got the option to postpone it once, but then it basically forced me. BegrudgingIy, I let it go before I could figure out a suitable root-keeper. Let me know what you use if you take the OTA and manage to keep root.
When it came back up after applying the patch, it seems I no longer have root access, but at least I have an unlocked bootloader so I can push ROMs if I want. I'm sure it will only be a matter of time before Dan Rosenberg figures out a way around the new OTA patches. He has a reputation around here of being a Android ninja!
Can you get a custom recovery installed? You could flash a super user zip then.
Sent from my PACMAN MATRIX HD MAXX
erikoink said:
@jeph0r3
So on Sunday, I made the mistake of "checking" to see if there was software update. There was. I did not want to update the phone, because I knew there was a good chance there was a root and unlock method out there for the current software version and wanted to investigate further. My only option was to "download now" or "download later" 12 hours.
12 hours came and went and I did not have the option to stop it. So I put it in WiFi mode and connected it to one of my WAPs that doesn't have internet access, which put a stop to the download. I did find a root/unlock method and went forward with it. Then the next question, what will happen when the download completes?
After rooting/unlocking the phone, I let the download complete, hoping that I didn't have to apply it. I got the option to postpone it once, but then it basically forced me. BegrudgingIy, I let it go before I could figure out a suitable root-keeper. Let me know what you use if you take the OTA and manage to keep root.
When it came back up after applying the patch, it seems I no longer have root access, but at least I have an unlocked bootloader so I can push ROMs if I want. I'm sure it will only be a matter of time before Dan Rosenberg figures out a way around the new OTA patches. He has a reputation around here of being a Android ninja!
Click to expand...
Click to collapse
If you flash a custom recovery through fastboot, you can then flash a super user zip using the custom recovery. No need to wait for a hack to the ota.
Sent from my DROID RAZR HD using xda premium
With an unlocked boot loader you have a lot of options, way to get the update from applying!
The craziest thing is that I'm really enjoying stock on the moto. Guys I have run every rom in the business. I've had the OG, the Droid X, NeXuS and a Razr, and now finally the RAZR HD.. I must say, I have had no lag, great connection and I've yet to find anything the phone has let me down on... I'm confused as to why this phone hasn't taken off!.. Have I forgotten to mention tha ti has an unlocked bootloader? Whats the deal?? I have not taken the OTA but I have gotten a message about it every 12 hours.. I know there is a way you can RSD back to the stock if you want it erikoink..
I may take the OTA.. If its better than this Stock Rom.. I'd be crazy not to
How do you like it erikoink????
I took the update without unrooting and used voodoo to restore it. I also had to install superuser then uninstalled it and supersu worked as normal.
No big changes with the update. The messages app doesn't display an incorrect unread message count which is nice.
I was a crack flasher with the gnex. But like you said, the phone just works. The only reason I unlocked my bootloader and rooted was to tinker with display resolution for an atrix lapdock.
I also don't know why the phone hasn't taken off. The lack of cases is irritating but I deal with it.
Been using my phone since March. Only important thing to remember is to restart the phone every few days or it looses some of its snap.
I decided to install "one power guard" but it's not really making that big of a difference. At first I was able to make it 2 days between charges and get almost 7 hours of screen on time. Now I can go a day and a half. I only have used a car charger three times and ALWAYS use the stock charger. Too risky.
This phone basically performs like my galaxy nexus but gets great battery life. I might get the note 3 in September but only if my battery life worsens.
Sent from my DROID RAZR MAXX HD
jeph0r3 said:
I've had the OG, the Droid X, NeXuS and a Razr, and now finally the RAZR HD..
Click to expand...
Click to collapse
jfriend33 said:
Been using my phone since March...
I might get the note 3 in September but only if my battery life worsens.
Click to expand...
Click to collapse
How do you guys afford to upgrade so often?! Do you have family plans and steal upgrades?
bananapeapod said:
How do you guys afford to upgrade so often?! Do you have family plans and steal upgrades?
Click to expand...
Click to collapse
I actually have been lucky on my upgrades. I had the Original Droid, I flashed sooooo many roms on it that it started getting buggy. Found a Droid X for 200 and snatched it up.. When my contract was up for the Orig Droid, I got the NeXus.. The volume on it was so bad that I couldn't stand it, so I went back to Verizon and traded it in on the Rezound. It was an AWESOME phone.. It has/had some GREAT devs.. I then found a Droid RAZR HD on craigslist because I will not upgrade and lose my unlimited data.. If I lose my unlimited on Verizon, it will be because they make me. I will then go to another provider as I am really pissed with VZW about this...
I freaking love this RAZR HD.. Might be my favorite phone so far.. Not sure why it doesn't have more Developers and ports....
bananapeapod said:
How do you guys afford to upgrade so often?! Do you have family plans and steal upgrades?
Click to expand...
Click to collapse
Yes, 2 smartphones with grandfathered unlimited data, and 3 feature phones. Why on earth people with a similar setup would blow an upgrade on a feature phone is beyond me.
I'm sure this won't go on forever though.
My razr maxx hd was purchased at full retail but was then reimbursed because my phone at the time was damaged and did not have a comparable replacement available.
I find it completely hysterical that verizons new upgrade payment plan called edge is only for share everything plans. BS!
Sent from my DROID RAZR MAXX HD
jfriend33 said:
Yes, 2 smartphones with grandfathered unlimited data, and 3 feature phones. Why on earth people with a similar setup would blow an upgrade on a feature phone is beyond me.
I'm sure this won't go on forever though.
My razr maxx hd was purchased at full retail but was then reimbursed because my phone at the time was damaged and did not have a comparable replacement available.
I find it completely hysterical that verizons new upgrade payment plan called edge is only for share everything plans. BS!
Sent from my DROID RAZR MAXX HD
Click to expand...
Click to collapse
Verizon loves you.
Sent from my DROID RAZR HD using Tapatalk 4 Beta
mentose457 said:
Verizon loves you.
Sent from my DROID RAZR HD using Tapatalk 4 Beta
Click to expand...
Click to collapse
It's a love hate relationship. Verizon is very inconsistent with their CS. If I ever have a problem I basically prep myself to make 5 calls.
Sent from my DROID RAZR MAXX HD
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.
So I had an interesting thing happen today. My phone's audio stopped working entirely. Any app that had or used sound causes my device to lock up entirely. Went through the standard steps, all the way to flashing back to stock, with the same issue. Called Google, and they informed me that it is 100% a hardware issue, and I need to RMA. Great. So I am in need of some advice. Since I have to send this to Google, I will want to be stock. I know that locking the bootloader is problematic, and will ultimately cause me to not be able to unlock. Should I lock the bootloader? It is going back to Google, but if they see it is a Verizon device with an unlocked bootloader, they may not like it. Also, while I know the people on XDA aren't mindreaders, maybe someone else will have dealt with this. What are the odds of getting a device with an exploitable build? Has anyone gotten a replacement from Google, and if so, what build was it running? I know I shouldn't expect to be able to unlock, but I can hope.
You have to wipe the device anyways and send it in. So why not just take the extra minute to lock the bootloader as a precautionary step?
dymmeh said:
You have to wipe the device anyways and send it in. So why not just take the extra minute to lock the bootloader as a precautionary step?
Click to expand...
Click to collapse
The only thing I am worried about is if something happens before locking. I know that locking the bootloader has been heavily advised against by beaups, and I just don't want anything to happen during the locking process.
stompysan said:
So I had an interesting thing happen today. My phone's audio stopped working entirely. Any app that had or used sound causes my device to lock up entirely. Went through the standard steps, all the way to flashing back to stock, with the same issue. Called Google, and they informed me that it is 100% a hardware issue, and I need to RMA. Great. So I am in need of some advice. Since I have to send this to Google, I will want to be stock. I know that locking the bootloader is problematic, and will ultimately cause me to not be able to unlock. Should I lock the bootloader? It is going back to Google, but if they see it is a Verizon device with an unlocked bootloader, they may not like it. Also, while I know the people on XDA aren't mindreaders, maybe someone else will have dealt with this. What are the odds of getting a device with an exploitable build? Has anyone gotten a replacement from Google, and if so, what build was it running? I know I shouldn't expect to be able to unlock, but I can hope.
Click to expand...
Click to collapse
Dealing with this exact problem right now on my wife's Verizon Pixel.
It was bootloader unlocked and rooted, but still auto updated for the Feb update. Soon after, audio broke just as you described. I was able to get it back working for a little bit after a couple factory image flashes, but it broke again for good.
I contacted Google and they set me up with an RMA. I flashed an exploitable factory image, relocked the bootloader, and sent it in last Wednesday. The replacement should be delivered tomorrow. I'm really hoping it was on the shelf at Google since launch and depixel. The phone was useless otherwise, so I had no choice but to send it back. I wish they'd just send me a non-Verizon.
"Your replacement Pixel Phone Silver 32 GB (Verizon) was shipped on February 20, 2017 via FXG"
I'll try to update after the replacement comes tomorrow.
jsbeagle said:
Dealing with this exact problem right now on my wife's Verizon Pixel.
It was bootloader unlocked and rooted, but still auto updated for the Feb update. Soon after, audio broke just as you described. I was able to get it back working for a little bit after a couple factory image flashes, but it broke again for good.
I contacted Google and they set me up with an RMA. I flashed an exploitable factory image, relocked the bootloader, and sent it in last Wednesday. The replacement should be delivered tomorrow. I'm really hoping it was on the shelf at Google since launch and depixel. The phone was useless otherwise, so I had no choice but to send it back. I wish they'd just send me a non-Verizon.
"Your replacement Pixel Phone Silver 32 GB (Verizon) was shipped on February 20, 2017 via FXG"
I'll try to update after the replacement comes tomorrow.
Click to expand...
Click to collapse
I went ahead and did the same thing. Let me know what build your replacement is. I still have my fingers crossed.
They all say they're Verizon models but almost everyone on this forum who has done this got a Google Play edition (it just has a Verizon SIM).
When I went through it, they said locking the bootloader was not necessary. Also, I got a brand new device with all accessories but they told me not to send the accessories in since I'd only be getting a phone back. Great experience for me. Props to Google for great service.
stompysan said:
I went ahead and did the same thing. Let me know what build your replacement is. I still have my fingers crossed.
Click to expand...
Click to collapse
YES!!!!!
Replacement Pixel just delivered. Appears to be brand new. All accessories included (they told me to only return the phone)
Verizon SIM was installed (I removed before booting it up).
Android Version 7.1
October 5 security patch
Build NDE63P
OEM unlocking toggle was greyed out until I connected to wifi, then I was able to toggle it to allow the bootloader to be unlocked. It does appear to be a google play edition in every way except the sim card that is included.
This is awesome. I'm now jealous of my wife and her non Verizon version. (We both still have the old grandfathered unlimited data and used the best buy trick to get Pixels on subsidized upgrades)
PsiPhiDan said:
They all say they're Verizon models but almost everyone on this forum who has done this got a Google Play edition (it just has a Verizon SIM).
When I went through it, they said locking the bootloader was not necessary. Also, I got a brand new device with all accessories but they told me not to send the accessories in since I'd only be getting a phone back. Great experience for me. Props to Google for great service.
Click to expand...
Click to collapse
jsbeagle said:
YES!!!!!
Replacement Pixel just delivered. Appears to be brand new. All accessories included (they told me to only return the phone)
Verizon SIM was installed (I removed before booting it up).
Android Version 7.1
October 5 security patch
Build NDE63P
OEM unlocking toggle was greyed out until I connected to wifi, then I was able to toggle it to allow the bootloader to be unlocked. It does appear to be a google play edition in every way except the sim card that is included.
This is awesome. I'm now jealous of my wife and her non Verizon version. (We both still have the old grandfathered unlimited data and used the best buy trick to get Pixels on subsidized upgrades)
Click to expand...
Click to collapse
You have no idea how excited this makes me. I have been extremely worried, but looks like I didn't need to be. Thanks!
stompysan said:
You have no idea how excited this makes me. I have been extremely worried, but looks like I didn't need to be. Thanks!
Click to expand...
Click to collapse
For the record, the only person who got a Verizon model still was able to unlock the bootloader (it was a new device with old 7.1 software) using dePixel8 so I think you're set regardless! Google is good!
For those who had the audio-craps-out problem, can I ask when you ordered you phones?
My wife & I have Google Store devices. I ordered mine in the first week after launch, and it's been great. I ordered my wife's in early January and she has audio-craps-out disease.
So I'm wondering if there's a bad batch of Pixels?
UnusualSuspect said:
For those who had the audio-craps-out problem, can I ask when you ordered you phones?
My wife & I have Google Store devices. I ordered mine in the first week after launch, and it's been great. I ordered my wife's in early January and she has audio-craps-out disease.
So I'm wondering if there's a bad batch of Pixels?
Click to expand...
Click to collapse
I got a Verizon version in January and it had an issue I haven't seen too many have, but it was audio related and apparently a hardware defect: mine had awful sound through the headphone jack only. Sounded like hissing and scratching beneath all the music. As if you didn't have the connection tight (but I did). Got the replacement and all is well!
UnusualSuspect said:
For those who had the audio-craps-out problem, can I ask when you ordered you phones?
My wife & I have Google Store devices. I ordered mine in the first week after launch, and it's been great. I ordered my wife's in early January and she has audio-craps-out disease.
So I'm wondering if there's a bad batch of Pixels?
Click to expand...
Click to collapse
Mine was ordered through Verizon on November 12, and shipped the next day. I am going to assume that it was a launch device.
Mine was purchased from bestbuy.com in mid November. It actually shipped from a local Best Buy store.
I believe there is a bad batch of pixels. I'm currently on my second one.
A couple weeks ago my pixel crashed and shutdown and well never turned on again. Basically the phone was bricked. Idk how or why. I was running perfectly and I only had the bootloader unlocked.
Long story short. I contacted my provider (Project Fi) and they sent me a new one. Received it the next day. (Great customer service!!)
So yes I believe there is a bad batch of pixels out there.
Ok more specifically I'm pretty used to the stock android experience (modded of course) but I read about that audio issue and I'm pretty terrified of it because music and calls are the main things I need a phone for. I've been out of the modded android loop since CM10 so I don't really know present day standards or processes for unlocking/rooting let alone standards for ROMs etc. Anyone got any advice?
WhenSuddenly said:
Ok more specifically I'm pretty used to the stock android experience (modded of course) but I read about that audio issue and I'm pretty terrified of it because music and calls are the main things I need a phone for. I've been out of the modded android loop since CM10 so I don't really know present day standards or processes for unlocking/rooting let alone standards for ROMs etc. Anyone got any advice?
Click to expand...
Click to collapse
just go to the guides subforum of a8 2018 and press on the thread that can help u flash twrp lol, all you gotta do is just follow the instructions word by word
WhenSuddenly said:
Ok more specifically I'm pretty used to the stock android experience (modded of course) but I read about that audio issue and I'm pretty terrified of it because music and calls are the main things I need a phone for. I've been out of the modded android loop since CM10 so I don't really know present day standards or processes for unlocking/rooting let alone standards for ROMs etc. Anyone got any advice?
Click to expand...
Click to collapse
my words of advice would be to make sure that you need root before you root it. what i mean by that is think about what you stand to gain by rooting it vs the PITA it is to root this thing. Pay close attention to the 168 hour thing as its been a thorn in many a persons side and caused many a headache. Ive had dozens of android phones and all have been rooted with the exception of the HTC Rezound, which required the OMG PITA "wire trick" to root properly. These phones run very well as stock and dont have much bloatware, so rooting them is becoming less necessary. I got mine in july '18 and have been happy with its performance overall so far. Ive reflashed the stock tar.img a few times for varying reasons, and even rooted it. But after losing SPay capability with root, i flashed back to stock as the gains werent worth the losses to me. Also, SHealth is a task to get working after you trip knox btw.
youdoofus said:
my words of advice would be to make sure that you need root before you root it. what i mean by that is think about what you stand to gain by rooting it vs the PITA it is to root this thing. Pay close attention to the 168 hour thing as its been a thorn in many a persons side and caused many a headache. Ive had dozens of android phones and all have been rooted with the exception of the HTC Rezound, which required the OMG PITA "wire trick" to root properly. These phones run very well as stock and dont have much bloatware, so rooting them is becoming less necessary. I got mine in july '18 and have been happy with its performance overall so far. Ive reflashed the stock tar.img a few times for varying reasons, and even rooted it. But after losing SPay capability with root, i flashed back to stock as the gains werent worth the losses to me. Also, SHealth is a task to get working after you trip knox btw.
Click to expand...
Click to collapse
Yeah tbh I'm ok with the interface now and aside from making the volume buttons change tracks when you hold them down the only things id need root for is clearing out bloatware etc. I think I'll take your advice and not root it for now (until something breaks) but what is this 168 hour thing?
WhenSuddenly said:
Yeah tbh I'm ok with the interface now and aside from making the volume buttons change tracks when you hold them down the only things id need root for is clearing out bloatware etc. I think I'll take your advice and not root it for now (until something breaks) but what is this 168 hour thing?
Click to expand...
Click to collapse
there has been a great deal of discussion about how to get the OEM unlock toggle to show up in the developer options, many suggest that its only obtainable by leaving the phone powered off for 168 hours and then rebooting, not connecting to any network (including cellular) and then enabling developer options and then the toggle should be there.
youdoofus said:
there has been a great deal of discussion about how to get the OEM unlock toggle to show up in the developer options, many suggest that its only obtainable by leaving the phone powered off for 168 hours and then rebooting, not connecting to any network (including cellular) and then enabling developer options and then the toggle should be there.
Click to expand...
Click to collapse
Your wrong your suppose to keep phone on for 168 hours no reboots then oem should show up again.
mchlbenner said:
Your wrong your suppose to keep phone on for 168 hours no reboots then oem should show up again.
Click to expand...
Click to collapse
youre*
and youre correct, i said it backwards.
youdoofus said:
there has been a great deal of discussion about how to get the OEM unlock toggle to show up in the developer options, many suggest that its only obtainable by leaving the phone powered off for 168 hours and then rebooting, not connecting to any network (including cellular) and then enabling developer options and then the toggle should be there.
Click to expand...
Click to collapse
So wait. My phone is showing the OEM unlock toggle and I can change it. Does that mean I can root? Or would trying to root then make me wait 168 hours? I never tried any custom stuff with it btw. Just bought and installed Lawnchair lol.
Amirk365 said:
So wait. My phone is showing the OEM unlock toggle and I can change it. Does that mean I can root? Or would trying to root then make me wait 168 hours? I never tried any custom stuff with it btw. Just bought and installed Lawnchair lol.
Click to expand...
Click to collapse
Hit the toggle and it'll ask for your pw, then you can flash a custom recovery via Odin
Amirk365 said:
So wait. My phone is showing the OEM unlock toggle and I can change it. Does that mean I can root? Or would trying to root then make me wait 168 hours? I never tried any custom stuff with it btw. Just bought and installed Lawnchair lol.
Click to expand...
Click to collapse
be careful with starting down the root rabbit hole tho. if you flash anything in download mode, youll trip the knox security counter and that is 100% irreversible without sending it to samsung. Root is cool and allows you to do stuff, but honestly ive not found too much reason to root this phone yet. Ive literally had over 20 android phones and i rooted and modded all of them (except the rezound, if you want to know why that one wasnt fully rooted, just google "rezound wire trick" and youll see) and this one just really doesnt need root IMO. Sure it would be nice to have a few root things, but its not worth the trade off of losing samsung pay so i can pay for stuff with my watch. That feature is just waaaay too valuable to me
youdoofus said:
be careful with starting down the root rabbit hole tho. if you flash anything in download mode, youll trip the knox security counter and that is 100% irreversible without sending it to samsung. Root is cool and allows you to do stuff, but honestly ive not found too much reason to root this phone yet. Ive literally had over 20 android phones and i rooted and modded all of them (except the rezound, if you want to know why that one wasnt fully rooted, just google "rezound wire trick" and youll see) and this one just really doesnt need root IMO. Sure it would be nice to have a few root things, but its not worth the trade off of losing samsung pay so i can pay for stuff with my watch. That feature is just waaaay too valuable to me
Click to expand...
Click to collapse
If his oem is showing and if he marks it and follow the directions he will be fine I have been rooted since day one of having it.
I never got locked out.
mchlbenner said:
If his oem is showing and if he marks it and follow the directions he will be fine I have been rooted since day one of having it.
I never got locked out.
Click to expand...
Click to collapse
ill never trade my SPay on my watch for root
youdoofus said:
be careful with starting down the root rabbit hole tho. if you flash anything in download mode, youll trip the knox security counter and that is 100% irreversible without sending it to samsung. Root is cool and allows you to do stuff, but honestly ive not found too much reason to root this phone yet. Ive literally had over 20 android phones and i rooted and modded all of them (except the rezound, if you want to know why that one wasnt fully rooted, just google "rezound wire trick" and youll see) and this one just really doesnt need root IMO. Sure it would be nice to have a few root things, but its not worth the trade off of losing samsung pay so i can pay for stuff with my watch. That feature is just waaaay too valuable to me
Click to expand...
Click to collapse
Thanks for the advice,but this isn't my first rodeo with Samsung lol. I messed around with the Verizon S5 alot and was lucky to have the version able to unlock it's bootloader.
Amirk365 said:
Thanks for the advice,but this isn't my first rodeo with Samsung lol. I messed around with the Verizon S5 alot and was lucky to have the version able to unlock it's bootloader.
Click to expand...
Click to collapse
np, the G900V was a major disappointment with its locked bootloader. i recall spending several hours bricking one and having to restore it with the stock tar.img file. total PITA
youdoofus said:
np, the G900V was a major disappointment with its locked bootloader. i recall spending several hours bricking one and having to restore it with the stock tar.img file. total PITA
Click to expand...
Click to collapse
Will you stop telling people that you will mess up phone if you try to root it.
If people follow directions they have nothing to worry about.
You where bootloop not bricked a brick device is usually a unfix able.
If is fine you what to keep Sam pay but your info you are telling is wrong.
I recently unroot my phone guess what Sam pay work fine.
Then root phone again no lock out and enable treble and flashed gsi image.
So their nothing wrong with rooting if you want to do that.
mchlbenner said:
Will you stop telling people that you will mess up phone if you try to root it.
If people follow directions they have nothing to worry about.
You where bootloop not bricked a brick device is usually a unfix able.
If is fine you what to keep Sam pay but your info you are telling is wrong.
I recently unroot my phone guess what Sam pay work fine.
Then root phone again no lock out and enable treble and flashed gsi image.
So their nothing wrong with rooting if you want to do that.
Click to expand...
Click to collapse
dude, i dont think youre reading what im saying right. Ive never said that rooting your phone will mess it up. the stuff about the G900V is a DIFFERENT PHONE. FFS. This isnt my first rodeo rooting and modding. Hell, i even was writing mods back in the Evo and S3 days. Im refamiliarizing myself with some of this, but i havent ever said youd mess your phone up if you follow the root instructions. Ill even go as far as saying as long as you dont Odin flash the tar.img for a completely different phone, these things are virtually impossible to hard brick. And yes, a bootloop is referred to as a soft brick. But, it is important to know that if you do root your phone, it WILL make samsung health not work as it did when stock and there is NO WAY of bringing it back without swapping the motherboard
youdoofus said:
np, the G900V was a major disappointment with its locked bootloader. i recall spending several hours bricking one and having to restore it with the stock tar.img file. total PITA
Click to expand...
Click to collapse
Unlocking the bootloader was completely dependent on the type of EMMC chip that the G900V that you had was using. I got three of those and only one was able to unlock after the Marshmallow update.
Amirk365 said:
Unlocking the bootloader was completely dependent on the type of EMMC chip that the G900V that you had was using. I got three of those and only one was able to unlock after the Marshmallow update.
Click to expand...
Click to collapse
the last tinkering i did with the G900V was several years ago and that was at the point when all hope was lost on the locked bootloader. I havent looked into it since as the G900's i had were G900P's which were FAR easier to work with. I did also root and ROM a couple G900VL's, but again was years ago
youdoofus said:
the last tinkering i did with the G900V was several years ago and that was at the point when all hope was lost on the locked bootloader. I havent looked into it since as the G900's i had were G900P's which were FAR easier to work with. I did also root and ROM a couple G900VL's, but again was years ago
Click to expand...
Click to collapse
Good times. Anyways I'm not rooting for now. Waiting for Pie and see how it goes.
Amirk365 said:
Good times. Anyways I'm not rooting for now. Waiting for Pie and see how it goes.
Click to expand...
Click to collapse
good times, yeah LOL!!! major waste of time on those friggin G900V's is more like it yeah, i wouldnt root yet, keep the stock recovery so it automagically updates to pie in a few weeks and manually check for updates every so often to force its hand. Also sammobile.com posts them too if you want to force it on via Odin and trip knox. Anyways, if you get the update in the near future, let us know!
Last phone I ever rooted was my old Galaxy S6. Years ago. In the end I ended up flashing back to stock. Cant remember why.
But yesterday morning after I got the android pie / one ui OTA .. I cannot use substratum and andromeda anymore!! I hate the themes from the galaxy store with a passion.
Is it worth rooting just to theme? I guess losing Knox ain't a problem. My phone isnt under warranty, it's a tmobile phone unlocked with different cell carrier.
Any opinions ?? :highfive:
bump
turbolaceup said:
Last phone I ever rooted was my old Galaxy S6. Years ago. In the end I ended up flashing back to stock. Cant remember why.
But yesterday morning after I got the android pie / one ui OTA .. I cannot use substratum and andromeda anymore!! I hate the themes from the galaxy store with a passion.
Is it worth rooting just to theme? I guess losing Knox ain't a problem. My phone isnt under warranty, it's a tmobile phone unlocked with different cell carrier.
Any opinions ?? :highfive:
Click to expand...
Click to collapse
I tried pie on my wifes phone. Its cool. I like it. But nothing compares to a rooted device even if you dont have custom roms or that good stuff. Even a 1.5 year old s8 still get better battery life than a new stock one with all my tweaks. I even kind of broke the 80% charge barrier litrelly last night. Got a 90% charge. So imo if your a smart fellar and can follow the root mwthod instructions to a t i would always pick root over updates. Im still on a revision 2 bootloader and plan to be til the death of my device
I see you say tmobile. The US devices or U models cannot trip knox. You lose samsung pay while rooted but you can always restore back stock. Secure folder and pay will work after. Since we have locked bootloaders. And no way to unlock them since they are signed with 256 bit sha keys.
I got dual speaker mods, modded touchwiz, deodexed. Completely themed out. I try all kinds. I push root to its limits for a locked bootloader.
TheMadScientist said:
I tried pie on my wifes phone. Its cool. I like it. But nothing compares to a rooted device even if you dont have custom roms or that good stuff. Even a 1.5 year old s8 still get better battery life than a new stock one with all my tweaks. I even kind of broke the 80% charge barrier litrelly last night. Got a 90% charge. So imo if your a smart fellar and can follow the root mwthod instructions to a t i would always pick root over updates. Im still on a revision 2 bootloader and plan to be til the death of my device
I see you say tmobile. The US devices or U models cannot trip knox. You lose samsung pay while rooted but you can always restore back stock. Secure folder and pay will work after. Since we have locked bootloaders. And no way to unlock them since they are signed with 256 bit sha keys.
I got dual speaker mods, modded touchwiz, deodexed. Completely themed out. I try all kinds. I push root to its limits for a locked bootloader.
Click to expand...
Click to collapse
Just the fact of losing Samsung pay, I will not root my phone. Thank you so much for reminding me of that downfall!!!
Yeah my phone is sm-g955u tmobile s8+ but unlocked and I use metro pcs.
And what is the 80% barrier? I read something earlier trying to find a rom if I were to root... I got parallels installed on my computer so I could have used Odin. (I sadly own a hackintosh, built from scratch mac in a PC tower)
I miss using substratum sense the pie update, but This equally Black & Red Samsung theme along with This awesome Samsung icon set is doing okay..
I do miss blacked out gmail, play store, etc... lol
Sent from my Samsung Galaxy S8+ using XDA Labs
turbolaceup said:
Just the fact of losing Samsung pay, I will not root my phone. Thank you so much for reminding me of that downfall!!!
Yeah my phone is sm-g955u tmobile s8+ but unlocked and I use metro pcs.
And what is the 80% barrier? I read something earlier trying to find a rom if I were to root... I got parallels installed on my computer so I could have used Odin. (I sadly own a hackintosh, built from scratch mac in a PC tower)
I miss using substratum sense the pie update, but This equally Black & Red Samsung theme along with This awesome Samsung icon set is doing okay..
I do miss blacked out gmail, play store, etc... lol
Sent from my Samsung Galaxy S8+ using XDA Labs
Click to expand...
Click to collapse
The kernel we have from Samsung the they do graciously left open to use for permissive root. Has a80% charge cap set in place from Samsung. Its a safety thing.
TheMadScientist said:
The kernel we have from Samsung the they do graciously left open to use for permissive root. Has a80% charge cap set in place from Samsung. Its a safety thing.
Click to expand...
Click to collapse
Weird. Lol.