downgrading to kitkat - Galaxy Tab S Q&A, Help & Troubleshooting

hi guys. I wanted to downgrade back to kitkat because of the constant rebooting problem and I stumbled upon this warning message. is this true? please peruse the attachment.

You can downgrade back. Ive done it before. But why downgrade when MM is coming? Have you tried disconnecting and reconnecting battery? Or even resoldiering it?

Downgrading to KitKat works just fine. I've done it many times. I wouldn't worry too much about MM coming out soon. I mean, we've only had ONE article saying it's coming soon, but it still technically isn't an official source. A reliable one, but not official. KitKat is easier to deal with than Lollipop though in regards to Xposed and viper4android. The UI looks, and IS, better for the OLED display.

thank you friends. what was the deal with that screenshot of that warning anyway? is it outdated info?

NightShadow02 said:
thank you friends. what was the deal with that screenshot of that warning anyway? is it outdated info?
Click to expand...
Click to collapse
I think it's more of a warning that something could go wrong if you don't know what you're doing. That's the first I've seen any kind of message like that though.
Sent from my SM-T700 using Tapatalk

noxarcana said:
I think it's more of a warning that something could go wrong if you don't know what you're doing. That's the first I've seen any kind of message like that though.
Sent from my SM-T700 using Tapatalk
Click to expand...
Click to collapse
cool cool. got my tab s back to stock kit kat. oh so stable. what ROM are you currently running on your device noxarcana?

NightShadow02 said:
cool cool. got my tab s back to stock kit kat. oh so stable. what ROM are you currently running on your device noxarcana?
Click to expand...
Click to collapse
I'm on Lollipop right now waiting for Marshmallow. If MM isn't released by the end of August, I'll be going back to KitKat. KitKat is very stable in all ways! For me, viper4android works without issue, Xposed doesn't require you to be deodexed, and it just looks better.
Sent from my SM-T700 using Tapatalk

noxarcana said:
I'm on Lollipop right now waiting for Marshmallow. If MM isn't released by the end of August, I'll be going back to KitKat. KitKat is very stable in all ways! For me, viper4android works without issue, Xposed doesn't require you to be deodexed, and it just looks better.
Sent from my SM-T700 using Tapatalk
Click to expand...
Click to collapse
is lollipop giving you the random flickering screen then reboot problem? because i'm a sufferer of said problem ever since I updated.

NightShadow02 said:
is lollipop giving you the random flickering screen then reboot problem? because i'm a sufferer of said problem ever since I updated.
Click to expand...
Click to collapse
Only when my battery drops below 50% and it becomes more and more frequent the lower it gets. It becomes unbearable around 30%. Flickers with a green light, random reboots, and false power offs. The false power offs are when the screen goes black but the device is still on and reacts to volume buttons and home button. Pushing the power button would seem to do nothing but it's actually locking the device but you wouldn't know that because the device seems to be off. Pushing the power button again unlocks the device and the screen comes back on but will turn off again randomly within a few minutes.
I'm on my second Tab S right now. The display on my first got a hairline fracture in the digitizer so the screen had this temporary, at first, green/yellow tint which could be temporarily "fixed" by holding the corners and bending inward. Not the best fix as you can imagine. Everything else on it worked just fine but it was going to cost the same price as a new one just to fix the screen so I gave it to a friend and bought myself a new one. I had for just over a year.
Sent from my SM-T700 using Tapatalk

noxarcana said:
Only when my battery drops below 50% and it becomes more and more frequent the lower it gets. It becomes unbearable around 30%. Flickers with a green light, random reboots, and false power offs. The false power offs are when the screen goes black but the device is still on and reacts to volume buttons and home button. Pushing the power button would seem to do nothing but it's actually locking the device but you wouldn't know that because the device seems to be off. Pushing the power button again unlocks the device and the screen comes back on but will turn off again randomly within a few minutes.
I'm on my second Tab S right now. The display on my first got a hairline fracture in the digitizer so the screen had this temporary, at first, green/yellow tint which could be temporarily "fixed" by holding the corners and bending inward. Not the best fix as you can imagine. Everything else on it worked just fine but it was going to cost the same price as a new one just to fix the screen so I gave it to a friend and bought myself a new one. I had for just over a year.
Sent from my SM-T700 using Tapatalk
Click to expand...
Click to collapse
yes same symptoms! i can't use a tablet which goes crazy when below 50%. I tried an AOSP rom once which limited the CPU to about 400mhz and the flickering and shutdowns are minimized. but. what can you do with such a slowpokey device these days haha. when I was still on stock lollipop, enabling power saving mode helped a bit as well.
people keep saying it is a battery connector issue or something but I've replaced the battery and it still does the same thing. doesn't seem to happen on kitkat so far. so I hope the rumored marshmallow update will get that issue fixed. and I'm surprised samsung didn't develop a patch for this widely reported shutting down issue.
does your second tab S work like a charm on lollipop though? perhaps it's a different batch with a different motherboard or something.

I never believed it to be the battery connector. I'll admit I'm not electrical engineer or anything like that, but I've been playing around with devices since I was 5 by taking them apart and a battery connector just doesn't make sense to me. I think it's a OS and device (a certain batch or something) issue. None of these issues were on KitKat. My first Tab S had NONE of these issues whatsoever! Only this current Tab has shown these issues. It "works like a charm"....as long as I stay above 50%.
Sent from my SM-T700 using Tapatalk

noxarcana said:
Downgrading to KitKat works just fine. I've done it many times. I wouldn't worry too much about MM coming out soon. I mean, we've only had ONE article saying it's coming soon, but it still technically isn't an official source. A reliable one, but not official. KitKat is easier to deal with than Lollipop though in regards to Xposed and viper4android. The UI looks, and IS, better for the OLED display.
Click to expand...
Click to collapse
Do you have to unlock the bootloader to install any custom/stock room?
i'm kinda new with this

IsaacXDA said:
Do you have to unlock the bootloader to install any custom/stock room?
i'm kinda new with this
Click to expand...
Click to collapse
I know nothing of bootloaders. I have a WiFi only device and don't have to deal with a bootloader.

Related

Do you get ghost screen touches with new leaked Froyo and/or when charging via cable?

It only happens when I use any ROM based off the .47 OTA and now the newer froyo 2.2 versions that have been released. I realize they are not final but a final version is obviously not going to fix my problem.
I feel I am probably a very small number of people with this issue. If I run any other ROM I don't have the issue but obviously there is something either with my phone or in the kernel or something effecting my phone.
What do I mean by ghost screen touch? Randomly using the phone it will register touches at the top of my screen. Bad enough to make the screen unusuable and I have to turn the screen off and on multiple times till it goes away.
If it is happening in my app tray it will always select the first top left icon on my screen.
This is on a completely stock ROM without me adding any software or anything. I also have no screen protectors etc. I have eliminated everything I can.
The only thing I can think of is I know before the .47 OTA some people complained about a grounding issue. I never had that problem personally but whatever they changed I think may be causing this because any ROM before that is fine.
This also does happen to me more when the phone is plugged into the charger.
thanks for reading.
I have gotten it when I'm charging, to the extent I have to disconnect my phone to use it without the screen going crazy.
Have you tried running dotty to see if anything is registering?
Sent from my PC36100 using XDA App
SharkUW said:
Have you tried running dotty to see if anything is registering?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Installed dotty and nothing was showing. decided to touch it and when i stopped touching it 3 points were still showing as registered(i can max at 5 points) they are still showing as i look at the phone now not evening touching it. now they are flashing as if i was touching them both!
update..it seems like its normal for there to be points after you stop touching the screen in dotty i dunno..however when my screen does start going crazy in dotty it will show two touches parallel to each other on the top left corner just down a bit. it will actually flash between the two as if i was cycling my fingers back and forth.
MrDSL said:
It only happens when I use any ROM based off the .47 OTA and now the newer froyo 2.2 versions that have been released. I realize they are not final but a final version is obviously not going to fix my problem.
I feel I am probably a very small number of people with this issue. If I run any other ROM I don't have the issue but obviously there is something either with my phone or in the kernel or something effecting my phone.
What do I mean by ghost screen touch? Randomly using the phone it will register touches at the top of my screen. Bad enough to make the screen unusuable and I have to turn the screen off and on multiple times till it goes away.
If it is happening in my app tray it will always select the first top left icon on my screen.
This is on a completely stock ROM without me adding any software or anything. I also have no screen protectors etc. I have eliminated everything I can.
The only thing I can think of is I know before the .47 OTA some people complained about a grounding issue. I never had that problem personally but whatever they changed I think may be causing this because any ROM before that is fine.
This also does happen to me more when the phone is plugged into the charger.
thanks for reading.
Click to expand...
Click to collapse
the only time I saw something like this on my phone, the screen shaking, icons moving, like delayed touches, vibrating movements, ghost screen touches, etc. etc. and unresponsive, was when I ate a "Subway" sandwich, I had mayonnaise on my fingers, and I tried to use the phone, it looked like it was experiencing a seizure. I really worried that day. I even though of pulling the battery. It went away when I wiped the screen....
I can confirm the odd touch behavior while charging.
This may be unrelated but I recall seeing a post saying the HTC Music widget was causing scroll lag and touch issues on the new OTA over in the dev forum.
So does that mean you ruled out the fps hack?
I woudlnt worry much.. been getting this every once in a blue moon since the first OTA (while charged to PC.. not the wall)
I also have this issue, but its rare when it happens... I've seen this exact issue with my old pre as well...
Sent from my PC36100 using XDA App
baiatul said:
the only time I saw something like this on my phone, the screen shaking, icons moving, like delayed touches, vibrating movements, ghost screen touches, etc. etc. and unresponsive, was when I ate a "Subway" sandwich, I had mayonnaise on my fingers, and I tried to use the phone, it looked like it was experiencing a seizure. I really worried that day. I even though of pulling the battery. It went away when I wiped the screen....
Click to expand...
Click to collapse
Seriously? So you're what 12 then?
AssassinsLament said:
So does that mean you ruled out the fps hack?
Click to expand...
Click to collapse
Correct..I am not sure what has changed since the .47 OTA but from there on up the issue is there even stock.
DataDork said:
I woudlnt worry much.. been getting this every once in a blue moon since the first OTA (while charged to PC.. not the wall)
Click to expand...
Click to collapse
I'd love to not worry about it but it happens to me without it being plugged in also. Often enough to be very annoying.
You should take your phone back.
Sent from my PC36100 using XDA App
Are you using the stock htc USB cable? I know that certain cheap (i.e. Monoprice) chargers/cables cause people's screens to become unresponsive and just basically act weird. Though it doesn't explain why it is only doing this with Froyo. Okay nevermind, just throwing some ideas out there. =)
My screen is less responsive to touch when charging via A/C adapter sometimes. Probably a grounding issue. Doesnt bother me.
I am also having this issue, except it happens w/o it being plugged in and it is happening to the point that my phone is completely un-usable. I bought it on launch day, I am trying to get back to stock 2.2 using the OTA and take it into sprint and play dumb I dont know what to do at this point.
Update: I was able to roll back to 1.32.651.1 (initial release) and I did not have any "ghost input" issues at all, loaded up dotty (which interestingly only let me use *2* multi-touch inputs at a time, if I put three fingers down the 3rd wouldn't show) played with it for 10 minutes. Usually I encounter these symptoms within a minute or two. Then I started updating, It loaded that very small update 1.32.651.6 i think, again no problems at all. Next up was 1.47.651.1. This update is the one that is causing the problem for me. Within 45 seconds of getting into the OS after 1.47 I started encountering the issue and Dotty is showing the same symptoms that MrDSL is having (two dots flashing in the top left handish corner). For ****s I then installed the official 2.2, in hopes that it would resolve the issue, but I still have the same problems. So, at this point I can either run pre 1.47 which really isn't an options for me, or deal with the ghost input issue which also really isn't an option for me, it literally drives me insane and I can't even use my phone as it just does it's own thing, or take it back to sprint.
At this point since I purchased this phone on launch day from Radio Shack what should I do? I want to exchange it but I don't know if Sprint or Radio shack will take it back (we're coming up on two months since launch). I should not have to use Insurance for something that is their problem. Suggestions?
Anyone else having this issue besides me and DSL ? DSL what have you done to remedy this or are you just living with the hell?
nvous23 said:
Anyone else having this issue besides me and DSL ? DSL what have you done to remedy this or are you just living with the hell?
Click to expand...
Click to collapse
Since the offical 2.2 has come out I emailed Sprint to let them know and they created a ticket for me and told me to bring it to the nearest Sprint store who has a tech on site.
I played dumb and said the issue started at the .47 OTA and that I was hoping the 2.2 OTA would fix it but instead it actually got worse. So when I need to go to the Sprint store I'll just flash the offical 2.2 OTA.
I really don't have much of a choice other then that unfortunately
Do you have a screen cover?
Sent from my PC36100 using XDA App
I do not have a screen cover. Even if i did and it was causing the issue it would happen on pre 1.47...
No screen cover! Nothing!
This is even without adding any software..Completely stock!!
Yep, got the same thing here. It's some of the most annoying stuff in the world. I'll be typing on the keyboard, and it'll give me a triple-tap, then it'll flip down the notification panel, and it just does strange stuff. And then it'll be fine for the rest of the day. And then, it'll do it again. It's such a pain. I figured it was the FPS hack, since it runs everything at 110Hz or something, but then I noticed, like you guys, that it happens on stock as well. Pretty much a total pain.

Anyone's Nexus(CDMA) powering itself off randomly?

Mine does this about 10 times a day. I pull it from my pocket after not using it for a while and find that it is powered down. I then have to power it on by holding the power button. I have no idea what could be causing this. I know two other people that have the nexus and haven't had a single random power down or reboot. I have factory reset it three times in hopes of fixing the issue. Do I maybe have a defective device?
I had a few of these when on the stock Rom. After rooting and switching to rootzboat Rom I've had no more random reboots.
No issues at all and im happy about that. When got my droid incredible at launch it would reboot ask the time due to having issues connecting to cell towers.
WilliamStern said:
I had a few of these when on the stock Rom. After rooting and switching to rootzboat Rom I've had no more random reboots.
Click to expand...
Click to collapse
I'm using the stock rom and I would be thrilled if that was the reason because it would mean my device isn't defective.
MrBigFeathers said:
I'm using the stock rom and I would be thrilled if that was the reason because it would mean my device isn't defective.
Click to expand...
Click to collapse
I'd say your device is fine. If you're gonna stay stock just wait for a fix maybe with an upcoming update, or just root now and take care of the issue. Once I rooted my phone performs 100 times better in every way, plus no more reboots. Look around they have some great Roms out already. I'm running a 4.0.3 and its fantastic!
WilliamStern said:
I'd say your device is fine. If you're gonna stay stock just wait for a fix maybe with an upcoming update, or just root now and take care of the issue. Once I rooted my phone performs 100 times better in every way, plus no more reboots. Look around they have some great Roms out already. I'm running a 4.0.3 and its fantastic!
Click to expand...
Click to collapse
Cool, I'll hold off til the next update from Google and if it hasn't resolved the issue I'll flash a custom rom.
Or is it possible to have a bad flash of the stock rom? I wonder if it would help to reflash it.
I definately think this is a problem. My nexus has been completely fine for a week and just starting yesterday it freezes and restarts constantly. It seems like it does it everytime there is more than one thing happening at the same time.
Like a text message rolling in at the same time Im trying to play a youtube video. Or hitting the volume rocker when I get a text...
It is absolutely crazy tbh - like I said phone has been completely fine.. and now its getting worse by the hour.
I am completely stock - no way im waiting for an update because there is no way my unit is not defective.
---------- Post added at 07:32 PM ---------- Previous post was at 06:48 PM ----------
Yeah, so I think my issue is different than OP's.
I have no idea what could have happened to make it this bad.
I decided to try a factory reset and now I cant even get through the activation without it freezing and rebooting... lol - so the phone at this point is completely useless - cant use it at all.
i have a gsm galaxy nexus which has been playing up since the last 2 days . random reboots and now its gone into a bootloop . the phone wont go beyond the google splash screen.
I think it randomly shut off when you're multitasking? I had it happen twice but can't quite figure out the cause.
I think I may have figured out whats going on with mine. It looks like the battery is a little loose inside the cover and if it moves too much it loses contact and the phone powers off. I tested this by dropping the phone from one hand into the other. I kind of threw it down at my other hand and when it hit it powered off. It doesn't power off every time but it powered down maybe 3 out of 20 tries. That makes me think that may be the issue.
Anyone that wants to try it out let me know your results. I may just have a defective device.

New OTA just pushed out

I just received a OTA push from AT&T. I'll update firmware version once my Note5 reboots.
Ends in OAH5
anyone know what it does?
Samsung pay?
Sent from my SAMSUNG-SM-N920A using XDA Free mobile app
ekerbuddyeker said:
Ends in OAH5
anyone know what it does?
Samsung pay?
Sent from my SAMSUNG-SM-N920A using XDA Free mobile app
Click to expand...
Click to collapse
Actually, it's AOH5, but I haven't figured out the changes yet.
Not sure if it's the fact that my phone was rebooted during the update, but it's very smooth after the update.
Same here. Anyone knows the changelog?? :\
54 packages updated. I didn't get a chance to pull the update. Probably just the stagefright stuff, samsung fixes, and at&t making their preloads more annoying. I don't see anything new popping up at me.
New APK: /system/priv-app/AmazonInstaller_ATT/AmazonInstaller_ATT.apk (this is in addition to the previous amazon shopping apk.)
Mine is rebooting now. ..
done12many2 said:
Actually, it's AOH5, but I haven't figured out the changes yet.
Click to expand...
Click to collapse
Mine's installing now....it just said performance and security enhancements. If that's actually true, I won't mind....Couldn't find it anywhere on the ATT website either. Anyone have any luck finding any background info on this?
quordandis said:
Mine's installing now....it just said performance and security enhancements. If that's actually true, I won't mind....Couldn't find it anywhere on the ATT website either. Anyone have any luck finding any background info on this?
Click to expand...
Click to collapse
I'm believing the performance part. I can't put my finger on it, but the phone is running nicely post update.
Mine's been having issues connecting to and keeping connected to LTE, maybe this fixes it?
Or maybe Carrier Aggregation??? Hey i can dream
Great update. Phone faster, smoother, more responsive with all bugs fixed AND it's solved the world famine problem.
Sent from my SAMSUNG-SM-N920A using XDA Free mobile app
so update now? or hold off for the tiny chance of rooting pre-update software...damn it
maximus96 said:
so update now? or hold off for the tiny chance of rooting pre-update software...damn it
Click to expand...
Click to collapse
I would just Update my friend!
This is going to sound really strange...but can anyone who has updated their phone -and- has a Samsung wireless charging pad that has been unreliable with maintaining a charging status see if it works better now?
I have read others who have Note 5s say that a software update helped fix the problems they were having with their Samsung wireless charging pads so I was wondering if this update helped ATT Note owners.
I'm trying to induce a flashing blue error in my pad right now, but so far I've re-positioned my phone about four times and it's stayed solid blue each time. Kind of frustrating because I just processed a refund for it via Amazon.
May just be my imagination but it seems that my fingerprint reader is a lot quicker and more accurate. I had been having issues since installing a tempered glass screen protector, but now works the first time every time.
Mr Orthoclase said:
This is going to sound really strange...but can anyone who has updated their phone -and- has a Samsung wireless charging pad that has been unreliable with maintaining a charging status see if it works better now?
I have read others who have Note 5s say that a software update helped fix the problems they were having with their Samsung wireless charging pads so I was wondering if this update helped ATT Note owners.
I'm trying to induce a flashing blue error in my pad right now, but so far I've re-positioned my phone about four times and it's stayed solid blue each time. Kind of frustrating because I just processed a refund for it via Amazon.
Click to expand...
Click to collapse
You know, now that you mention it, my Koolpad is working much better where before the update was very specific on where the phone sat. Weird...
czechpunk said:
You know, now that you mention it, my Koolpad is working much better where before the update was very specific on where the phone sat. Weird...
Click to expand...
Click to collapse
Not only that but hit dialer a few times look how fast it pop-up.
Running On Samsung Galaxy Note 5 N920A
Wonder if it fixes this.
http://arstechnica.com/security/201...ives-attackers-full-access-to-locked-devices/
czechpunk said:
You know, now that you mention it, my Koolpad is working much better where before the update was very specific on where the phone sat. Weird...
Click to expand...
Click to collapse
Yeah, It's like a complete reversal now. Before I had to struggle to find a position that kept the wireless charger blue (charging) but now I can't seem to get it to switch to flashing blue (not or minimal charging). Very strange. I mean, it's awesome...but I'm still hoping to get some more feedback before I cancel my Amazon refund.
I'm still waiting on a miracle root. I'm gonna hold off for a little bit. Lol
Sent from my SAMSUNG-SM-N920A using Tapatalk

Do we has unlocked bootloader?

After root came out for G4 i never heard that unlocked bootloader came out. Im looking through the threads, but most are old or got off topic, so to keep it simple
Is there unlocked bootloader for VZ G4 yet?
No
We don't even have a fully working phone..People with 12a has broken WiFi notifications and people without it have touch screen issues.
^^ So much this. It's depressing.
Read somewhere that a lot of first batch phones have faulty circuit boards, that's what is causing the issues. I'm still on 10b and wanted to hold out for the bootloader unlock, but it doesn't look like it's gonna happen anytime soon. Might bite the bullet and try to do a warranty replacement through LG so I get a new phone vs a certified pre owned from Verizon...
Sent from my VS986 using Tapatalk
Not everybody with pre 12a have touchscreen issues. I'm on 11a and I have absolutely no touchscreen issues. It's smooth, fast, and responsive.
chubbrock said:
Read somewhere that a lot of first batch phones have faulty circuit boards, that's what is causing the issues. I'm still on 10b and wanted to hold out for the bootloader unlock, but it doesn't look like it's gonna happen anytime soon. Might bite the bullet and try to do a warranty replacement through LG so I get a new phone vs a certified pre owned from Verizon...
Sent from my VS986 using Tapatalk
Click to expand...
Click to collapse
Please let me know how that turns out. It's so pathetic that I can't even use the phone. I need to get it replaced/fixed or ...... the wall is where it might end up with.
Spookymyo said:
Not everybody with pre 12a have touchscreen issues. I'm on 11a and I have absolutely no touchscreen issues. It's smooth, fast, and responsive.
Click to expand...
Click to collapse
X2 mine is perfectly fine, and is also on 11a rooted and with a lot of stuff freezed / uninstalled.
This made me laugh pretty good man
Thank you for your answer, straight to the point mate.
CyberManiaK said:
X2 mine is perfectly fine, and is also on 11a rooted and with a lot of stuff freezed / uninstalled.
Click to expand...
Click to collapse
X's three, mine seems to be doing fine but when I download an app from xposed and reboot it, it takes hours to load when I reboot. I don't know if I can attribute that toward this issue.
1NOLASaints1 said:
X's three, mine seems to be doing fine but when I download an app from xposed and reboot it, it takes hours to load when I reboot. I don't know if I can attribute that toward this issue.
Click to expand...
Click to collapse
How are you rebooting -- selecting reboot from the power menu? My reboot lag was resolved once I stopped selecting reboot and just shut down the phone entirely then used the power button to turn it back on. No idea why that worked, but it worked for someone else here at XDA too, so it's worth a shot.

Random Reboots Since June Update?

Pixel XL, stock ROM/ kernel, rooted with Magisk, TWRP recovery. Getting random reboots about every day or two, usually while it's sleeping in my pocket. This all started right after the June update with no other software changes. Anyone else seeing the same?
Been happening to me as well. I'm not on stock, but it seems to have smoothed out for now.
Search for your issue here https://issuetracker.google.com/ if someone has reported it Star it so gets more attention if it's not reported make a report yourself
Unless it's an issue by Magisk then obviously no support
Gulfstream 650 said:
Pixel XL, stock ROM/ kernel, rooted with Magisk, TWRP recovery. Getting random reboots about every day or two, usually while it's sleeping in my pocket. This all started right after the June update with no other software changes. Anyone else seeing the same?
Click to expand...
Click to collapse
Purely academic question - your phone comes fully encrypted, unbreakable, yet you chose to root/unlock bootloader to break that privacy protection. Is it worth it to you?
nabbed said:
Purely academic question - your phone comes fully encrypted, unbreakable, yet you chose to root/unlock bootloader to break that privacy protection. Is it worth it to you?
Click to expand...
Click to collapse
You just install security right back in phone, no breach
fiverings said:
You just install security right back in phone, no breach
Click to expand...
Click to collapse
Yeap. When you fall off a cliff, just come right back to life. No prob. Keep smoking them, bro!
nabbed said:
Yeap. When you fall off a cliff, just come right back to life. No prob. Keep smoking them, bro!
Click to expand...
Click to collapse
Well, it sounded plausible to me. If I'm wrong I'm wrong. Thanks for your imput.
nabbed said:
Purely academic question - your phone comes fully encrypted, unbreakable, yet you chose to root/unlock bootloader to break that privacy protection. Is it worth it to you?
Click to expand...
Click to collapse
I could be wrong, but I doubt he rooted it/unlocked its bootloader just to break a "privacy protection". He probably rooted it/unlocked its bootloader so he could get more functionality out of it.
fiverings said:
Well, it sounded plausible to me. If I'm wrong I'm wrong. Thanks for your imput.
Click to expand...
Click to collapse
No you are correct. There are far more benefits to being unlocked then locked.
Gulfstream 650 said:
Pixel XL, stock ROM/ kernel, rooted with Magisk, TWRP recovery. Getting random reboots about every day or two, usually while it's sleeping in my pocket. This all started right after the June update with no other software changes. Anyone else seeing the same?
Click to expand...
Click to collapse
Going back to the point on the topic, I also got my phone rebooting several times a day after the latest update. And now, it just stops ... booting*

*AT ALL!!
I have a brick! It slightly vibrates after 30 seconds of combining Power and Vol Down buttons, but I can't get it into bootloader or any other booting sequence. The screen doesn't turn on, not even when charging. I can feel the phone is charging because is slightly warm (as usual) while charging.
I tried living the phone all night discharging the battery (unplugged) but still not able to recover it. I tried again charging it today, but still nothing. No chance to do fastboot or any adb, the phone is not even turning on. What should I do? RMA? Mine is a Pixel XL 128Gb (Verizon) with stock ROM not rooted.
infinito0174 said:
Going back to the point on the topic, I also got my phone rebooting several times a day after the latest update. And now, it just stops ... booting*

*AT ALL!!
I have a brick! It slightly vibrates after 30 seconds of combining Power and Vol Down buttons, but I can't get it into bootloader or any other booting sequence. The screen doesn't turn on, not even when charging. I can feel the phone is charging because is slightly warm (as usual) while charging.
I tried living the phone all night discharging the battery (unplugged) but still not able to recover it. I tried again charging it today, but still nothing. No chance to do fastboot or any adb, the phone is not even turning on. What should I do? RMA? Mine is a Pixel XL 128Gb (Verizon) with stock ROM not rooted.
Click to expand...
Click to collapse
Try holding down power about 8 or so seconds
Then while still holding it down, hold down the volume up for 6 seconds, then let it go if nothing, let power go.
nabbed said:
Purely academic question - your phone comes fully encrypted, unbreakable, yet you chose to root/unlock bootloader to break that privacy protection. Is it worth it to you?
Click to expand...
Click to collapse
Yes, very much worth it for the additional functionality. I use layered security that will keep the vast majority of snoops out so it strikes a good balance.

Categories

Resources