I just sent back the N6 that had the screen burn out, I got my RMA device and its on just 5.1 not 5.1.1 should I update it or keep it does it matter? Also this N6 is doing some of the same issues that the other device did before it burned out. The screen has a lot of flickering and triangle flashes but only when I'm using my web browser, also, today I got off of a phone call and the proximity sensor failed to turn the screen on. What's up with that? I'm starting to wonder about these N6's man. Any ideas guys. I think I may need to just flash the s#-t out of this thing
electrojas said:
I just sent back the N6 that had the screen burn out, I got my RMA device and its on just 5.1 not 5.1.1 should I update it or keep it does it matter? Also this N6 is doing some of the same issues that the other device did before it burned out. The screen has a lot of flickering and triangle flashes but only when I'm using my web browser, also, today I got off of a phone call and the proximity sensor failed to turn the screen on. What's up with that? I'm starting to wonder about these N6's man. Any ideas guys. I think I may need to just flash the s#-t out of this thing
Click to expand...
Click to collapse
If it was mine, I'd RMA this one too.
Unlock it. Fastboot flash the updated 5.1.1 factory image and see what you have. If bad send it back. If good it all good.
---------- Post added at 12:47 PM ---------- Previous post was at 12:39 PM ----------
What browser. It may be the problem. There were proximity sensor fixes in one of the updates. Not sure which.
prdog1 said:
Unlock it. Fastboot flash the updated 5.1.1 factory image and see what you have. If bad send it back. If good it all good.
---------- Post added at 12:47 PM ---------- Previous post was at 12:39 PM ----------
What browser. It may be the problem. There were proximity sensor fixes in one of the updates. Not sure which.
Click to expand...
Click to collapse
I'm using adblock browser. I just updated to Windows 10 so now my adb is all jacked up for some reason. When I turned on the phone it said that there was a 5.1.1 update ready to be installed. Should I just take that one before I unlock the BL and root or do the unlock first? Thanks to all of you who are helping me out. Good people.
electrojas said:
I'm using adblock browser. I just updated to Windows 10 so now my adb is all jacked up for some reason. When I turned on the phone it said that there was a 5.1.1 update ready to be installed. Should I just take that one before I unlock the BL and root or do the unlock first? Thanks to all of you who are helping me out. Good people.
Click to expand...
Click to collapse
Unlock first. Too many been bricked on that update with bootloader locked. I wouldn't take it. Win 10 didn't jack with my adb. I have full SDK tho. Some are using the 15 minute adb/fastboot. I would search and try to reinstall it. Does your usb debug work as far as showing device MTP on PC. If not you lost the Google driver.
---------- Post added at 03:13 PM ---------- Previous post was at 03:10 PM ----------
More than likely that browser is the flicker problem. I use Chrome but with Adaway and MOAB. No adds anywhere. lol
I'll have to check. I'm so gunshy now I only hooked this to pc just to put music on it. I'll unlock BL and try the update after. Thanks
electrojas said:
I'll have to check. I'm so gunshy now I only hooked this to pc just to put music on it. I'll unlock BL and try the update after. Thanks
Click to expand...
Click to collapse
If able to put music on your driver is good. Need ADB/Fastboot working or you are already dead in the water.
prdog1 said:
Unlock first. Too many been bricked on that update with bootloader locked. I wouldn't take it. Win 10 didn't jack with my adb. I have full SDK tho. Some are using the 15 minute adb/fastboot. I would search and try to reinstall it. Does your usb debug work as far as showing device MTP on PC. If not you lost the Google driver.
---------- Post added at 03:13 PM ---------- Previous post was at 03:10 PM ----------
More than likely that browser is the flicker problem. I use Chrome but with Adaway and MOAB. No adds anywhere. lol
Click to expand...
Click to collapse
15 minute adb? What is that like a tool that does all of that for you?
electrojas said:
15 minute adb? What is that like a tool that does all of that for you?
Click to expand...
Click to collapse
It the lazy man ADB/Fastboot for those that don't want to install full SDK and edit the environmental path.
http://forum.xda-developers.com/showthread.php?t=2588979
So I just follow the unlock procedure in the how to post like normal now right
electrojas said:
So I just follow the unlock procedure in the how to post like normal now right
Click to expand...
Click to collapse
Enable unlock in developers options. Boot to bootloader. in command prompt type "fastboot devices" to make sure your device id shows up. If shows device type "fastboot oem unlock". Will see prompt on phone to agree.
It's just finished so now does it matter which 5.1.1 I take, and do I have to put TWRP on this in order to do it
I suppose now I can take the downloaded one or do you recommend a better file. I really would like to keep this Damn phone
electrojas said:
It's just finished so now does it matter which 5.1.1 I take, and do I have to put TWRP on this in order to do it
Click to expand...
Click to collapse
Latest for all carriers is I version unless you are on TMobile then it is the one that says TMobile only. They don't have the security update yet. No need for TWRP yet as long as unlocked. Get it booted and see if everything works. Do NOT relock. DO NOT use toolkit. Do it manually with fastboot commands.
prdog1 said:
Latest for all carriers is I version unless you are on TMobile then it is the one that says TMobile only. They don't have the security update yet. No need for TWRP yet as long as unlocked. Get it booted and see if everything works. Do NOT relock.
Click to expand...
Click to collapse
Mine is unbranded factory unlocked. It's restoring all my backed up poo right now. I guess I have 2 options. 1 take the Ota they send down or install the one I downloaded yesterday. It says for all carriers except tmobile. I got it from Google yesterday. It's the exact one that was on the phone I sent back. Do you have any particular preference or reccomendation?
electrojas said:
Mine is unbranded factory unlocked. It's restoring all my backed up poo right now. I guess I have 2 options. 1 take the Ota they send down or install the one I downloaded yesterday. It says for all carriers except tmobile. I got it from Google yesterday. It's the exact one that was on the phone I sent back. Do you have any particular preference or reccomendation?
Click to expand...
Click to collapse
The new I version has the Stagefright security fix otherwize the Z version is fine. That is what I am on. Haven't updated yet.. You can try OTA as long as unlocked. Have seen posts that say OTA won't work unlocked. Not sure. If it bootloops and it is locked you are hosed again and have to RMA.
prdog1 said:
The new I version has the Stagefright security fix otherwize the Z version is fine. That is what I am on. Haven't updated yet.. You can try OTA as long as unlocked. Have seen posts that say OTA won't work unlocked. Not sure. If it bootloops and it is locked you are hosed again and have to RMA.
Click to expand...
Click to collapse
The new I version? Is the best place to get it on here or Motorola? Also your gonna think this is a stupid question but what is I version? I'm coming from Sammy to LG back to Sammy, now this. Learning about fastboot its all new to me. Thanks bro
Sent from my Nexus 6 using XDA Forums Pro.
electrojas said:
The new I version? Is the best place to get it on here or Motorola? Also your gonna think this is a stupid question but what is I version? I'm coming from Sammy to LG back to Sammy, now this. Learning about fastboot its all new to me. Thanks bro
Sent from my Nexus 6 using XDA Forums Pro.
Click to expand...
Click to collapse
https://developers.google.com/android/nexus/images
Related
Just received my Moto X AT&T shipped from Costco, system version is 139.9.51.ghost_ATT.en.US -so would appear I can root? (and then hopefully take the update without losing root? I recall seeing a thread, hopefully for the version I have)
Can the update be "pushed" onto the device without my accepting it, as to whether I would need to root (if I wanted to root) quickly to block it?
Thanks
M973 said:
Just received my Moto X AT&T shipped from Costco, system version is 139.9.51.ghost_ATT.en.US -so would appear I can root? (and then hopefully take the update without losing root? I recall seeing a thread, hopefully for the version I have)
Can the update be "pushed" onto the device without my accepting it, as to whether I would need to root (if I wanted to root) quickly to block it?
Thanks
Click to expand...
Click to collapse
no but you will get continual pop ups unless you the phone then disable motorola ota 1.0 and updater.apk (i think just updater.apk will suffice) with Titanium back up.
jayboyyyy said:
no but you will get continual pop ups unless you the phone then disable motorola ota 1.0 and updater.apk (i think just updater.apk will suffice) with Titanium back up.
Click to expand...
Click to collapse
Thanks, I thought that was the case, but wanted to confirm quickly (with some, SGS4, it's pushed to the phone whether you accept or not, unless you're rooted.)
Thanks for the quick reply
M973 said:
Thanks, I thought that was the case, but wanted to confirm quickly (with some, SGS4, it's pushed to the phone whether you accept or not, unless you're rooted.)
Thanks for the quick reply
Click to expand...
Click to collapse
not sure if it downloads it automatically or not (i don't think it does but it may). Even if it does download automatically it won't update it unless you click ok when it prompts you. I would root and disable OTiA until you figure out what you are going to do about it.
rooting
looks like it's either with PwnMyMoto, or Motoroot, appears the first is better? Looks like both are done with ADB which was a bit difficult, have only used it once, used it to remove safestrap from the SGS4 I had so I could return it
M973 said:
looks like it's either with PwnMyMoto, or Motoroot, appears the first is better? Looks like both are done with ADB which was a bit difficult, have only used it once, used it to remove safestrap from the SGS4 I had so I could return it
Click to expand...
Click to collapse
You can just install pwnmymoto on your device and run it. Make sure to have unknown sources checked
---------- Post added at 05:56 PM ---------- Previous post was at 05:55 PM ----------
Also it is wise to get familiar with adb and fastboot!
shane1 said:
You can just install pwnmymoto on your device and run it. Make sure to have unknown sources checked
---------- Post added at 05:56 PM ---------- Previous post was at 05:55 PM ----------
Also it is wise to get familiar with adb and fastboot!
Click to expand...
Click to collapse
Cool, thanks!
Hello,
Sorry if this question is really stupid, but are there any root methods for the Nexus 6 on Android 5.0.1? Would any root for Lollipop 5.0 work for 5.0.1 as well? Please reply with what methods have worked for you. Thanks a lot!
http://forum.xda-developers.com/showthread.php?p=56913254
I use this for absolutely everything I do with my phone. Works flawlessly.
saddog5523 said:
http://forum.xda-developers.com/showthread.php?p=56913254
I use this for absolutely everything I do with my phone. Works flawlessly.
Click to expand...
Click to collapse
Thank you so much! I just found this coincidentally SECONDS before you responded. Hopefully it works great. Now, when I lose root each time I update, I can just come back to this application and see if there is a new version?
rmx36 said:
Thank you so much! I just found this coincidentally SECONDS before you responded. Hopefully it works great. Now, when I lose root each time I update, I can just come back to this application and see if there is a new version?
Click to expand...
Click to collapse
Wug keeps everything up to date. Shouldn't be a problem. Also, you won't be able to update when you're rooted. The update checks for any modifications and will error out. You will have to flash the update manually, or via the toolkit under advanced. There is a guide under general about how to update manually via fastboot, which is a pretty simple thing. I'm a bit cautious about flashing anything manually and I was able to do it without any hiccups. I'll grab a link for it.
---------- Post added at 11:37 PM ---------- Previous post was at 11:35 PM ----------
http://forum.xda-developers.com/showthread.php?p=57063390
This guide is what I used to flash from 5.0.0 to 5.0.1 when it was released. Just make sure you read all the way through once before you start. And do the long method, the short method doesn't work for some reason.
saddog5523 said:
Wug keeps everything up to date. Shouldn't be a problem. Also, you won't be able to update when you're rooted. The update checks for any modifications and will error out. You will have to flash the update manually, or via the toolkit under advanced. There is a guide under general about how to update manually via fastboot, which is a pretty simple thing. I'm a bit cautious about flashing anything manually and I was able to do it without any hiccups. I'll grab a link for it.
---------- Post added at 11:37 PM ---------- Previous post was at 11:35 PM ----------
http://forum.xda-developers.com/showthread.php?p=57063390
This guide is what I used to flash from 5.0.0 to 5.0.1 when it was released. Just make sure you read all the way through once before you start. And do the long method, the short method doesn't work for some reason.
Click to expand...
Click to collapse
Thanks. Everything worked well, now going to go use Viper4Android. Anything you recommend over it for sound quality and audio boosting?
rmx36 said:
Thanks. Everything worked well, now going to go use Viper4Android. Anything you recommend over it for sound quality and audio boosting?
Click to expand...
Click to collapse
Viper is my favorite and nothing really comes close to it.
Sent from my Nexus 6 using Tapatalk
Hi, my Nexus is on Android 5.0.1 (LRX22C). I haven't rooted or unlocked the bootloader; everything is totally stock. But I'm unable to successfully install the Android 5.1 OTA update. My phone downloads it, verifies it, then reboots to begin the installation process. After working on the update for a while, I see an error message (with an android on its back and a red "X"). The phone stays on that screen for a while, then eventually reboots without having installed the update. I've tried clearing cache, and it doesn't help. Anyone have any ideas?
carrot34 said:
Hi, my Nexus is on Android 5.0.1 (LRX22C). I haven't rooted or unlocked the bootloader; everything is totally stock. But I'm unable to successfully install the Android 5.1 OTA update. My phone downloads it, verifies it, then reboots to begin the installation process. After working on the update for a while, I see an error message (with an android on its back and a red "X"). The phone stays on that screen for a while, then eventually reboots without having installed the update. I've tried clearing cache, and it doesn't help. Anyone have any ideas?
Click to expand...
Click to collapse
Some more info please. What carrier are you using? Was your phone purchased from that carrier or somewhere else?
Evolution_Freak said:
Some more info please. What carrier are you using? Was your phone purchased from that carrier or somewhere else?
Click to expand...
Click to collapse
Thanks! I'm on T-Mobile, and bought the phone from Google Play.
carrot34 said:
Thanks! I'm on T-Mobile, and bought the phone from Google Play.
Click to expand...
Click to collapse
Are you familiar with sideload?
---------- Post added at 09:42 PM ---------- Previous post was at 09:37 PM ----------
Check out my thread on OTA's.
http://forum.xda-developers.com/showthread.php?t=2992919
In post #2, there's a link to the OTA files thread. Take the one that is specifically for T-Mobile. LRX22C to LMY47M.
Evolution_Freak said:
Are you familiar with sideload?
Click to expand...
Click to collapse
Yeah, I've sideloaded before with other devices, but I'd like not to have deal with wiping my phone to unlock the bootloader right now. I'd thought that by not rooting or messing with the bootloader, I'd keep things simple and be able to easily apply OTA updates. So I'm very frustrating that this isn't working. Any idea why this might be happening?
Thanks!
Alan
carrot34 said:
Yeah, I've sideloaded before with other devices, but I'd like not to have deal with wiping my phone to unlock the bootloader right now. I'd thought that by not rooting or messing with the bootloader, I'd keep things simple and be able to easily apply OTA updates. So I'm very frustrating that this isn't working. Any idea why this might be happening?
Thanks!
Alan
Click to expand...
Click to collapse
No, you do not need to wipe or unlock to sideload. Post #3 in the thread I linked, simple instructions on sideloading.
As for why this is happening, anyone's guess but it could, somehow, have something to do with your device having the T-Mobile Sim and being from Google play.
Evolution_Freak said:
No, you do not need to wipe or unlock to sideload. Post #3 in the thread I linked, simple instructions on sideloading.
As for why this is happening, anyone's guess but it could, somehow, have something to do with your device having the T-Mobile Sim and being from Google play.
Click to expand...
Click to collapse
OK, I'll give it a shot. Thanks! Any idea which OTA I want? I'm guessing it's LMY47M, since I'm on a T-Mobile SIM, even though the device was bought from Google? Need I worry that that build isn't up on Google's "Factory Images for Nexus Devices" page? And is there any risk that installing an update this way will make it more complicated to get OTA updates in the future? (I was hoping that by doing things the official way this time, I could avoid having to monkey around with stuff like this.)
Thanks!
Alan
carrot34 said:
OK, I'll give it a shot. Thanks! Any idea which OTA I want? I'm guessing it's LMY47M, since I'm on a T-Mobile SIM, even though the device was bought from Google? Need I worry that that build isn't up on Google's "Factory Images for Nexus Devices" page? And is there any risk that installing an update this way will make it more complicated to get OTA updates in the future? (I was hoping that by doing things the official way this time, I could avoid having to monkey around with stuff like this.)
Thanks!
Alan
Click to expand...
Click to collapse
Yes, you want the LRX22C to LMY47M OTA as I said before. No, you don't need to worry about it not being on the images page. Also a no for it affecting your ability to get OTA's in the future. On a Nexus, this is pretty much as official as getting the OTA natively.
OK, an update: got an error installing the update any way I tried, even after a factory reset. Called Google support, and they're replacing the phone for me.
Hey guys,
Recently, I have been trying to re-root my LG G2 VS980 that was returned to lollipop stock (LG Firmware). However, all the tools I knew that previously worked, (Ioroot, Towelroot, Stumproot, Kingoroot, etc..) did not work. After months of testing, I finally found one app that currently works called KingRoot.
As far as I know, it is the only root method that acutally still works after LG patched most of the exploits so I thought I would share the info with you guys in case some of you are still interested in rooting your G2.
Instructions:
1. Install Kingroot: http://kingroot.net/ (the APK doesn't work for the G2)
2. Go to settings in your phone and click the build number 7-10 times to enable Developer Options
3. Go to Developer Options and enable USB Debugging
4. plug the phone into your computer and launch the program. Make sure you see the USB Debugging card that will pop up on your phone.
Launch the program and allow the program to root your phone.
Sidenote: The only downside to the app is it is all in Korean but it is very easy to tell what it is asking due to excellent pictures
After you receive root, download the app RootChecker just to make sure.
To Install TWRP:
1. Instructions: Go to Play Store and type in the search window, "AUTOREC".
2. Select the correct variant: ex. VS980=Verizon etc...
3. Install the app.
4. Watch TWRP Install on your phone.
5. Reward yourself on your hard work with a pat on the back.
So that's it; A fast easy, and trouble free method on getting root and installing TWRP
Thanks for this. I recently acquired a G2, and will be trying this out tonight.
tribalartgod said:
Thanks for this. I recently acquired a G2, and will be trying this out tonight.
Click to expand...
Click to collapse
No problem. Have fun with your custom ROM of choice.
Can you share the setup files? I also need to re-root my Verizon phone. The kingroot ownload links looks dead
i downlaoded it from here. I have usb dev enabled. now what? http://kingroot-pc.en.uptodown.com/download
Stuck on that step. I know its telling me to enable USB debuggin which I have, it doens' do anythong when I click Go in Korean
I managed to enable debugging mode which was by setting the 'USB Type" on the phone to "Internet -> Ethernet"
But Kingroot isn't managing to root the phone. It goes 100 percent and nothing.
Ioroot managed to get the phone into the reboot phase but the phone no longer processed the splash screen of the recover/bootloader. The splash screen which has the android mascot on its back with abdomen open.
"LG G2 One lick Tool" makes the phone go to "download mode" but its stuck at 0 percent. I disconnect and replug in hope of kickstarting it, doesn't work.
What can I do now?
y300owner said:
I managed to enable debugging mode which was by setting the 'USB Type" on the phone to "Internet -> Ethernet"
But Kingroot isn't managing to root the phone. It goes 100 percent and nothing.
Ioroot managed to get the phone into the reboot phase but the phone no longer processed the splash screen of the recover/bootloader. The splash screen which has the android mascot on its back with abdomen open.
"LG G2 One lick Tool" makes the phone go to "download mode" but its stuck at 0 percent. I disconnect and replug in hope of kickstarting it, doesn't work.
What can I do now?
Click to expand...
Click to collapse
Where you able to get it to work? I am running into the same problems.
Sent from my SM-N920V using Tapatalk
y300owner said:
Can you share the setup files? I also need to re-root my Verizon phone. The kingroot ownload links looks dead
i downlaoded it from here. I have usb dev enabled. now what? http://kingroot-pc.en.uptodown.com/download
Stuck on that step. I know its telling me to enable USB debuggin which I have, it doens' do anythong when I click Go in Korean
Click to expand...
Click to collapse
Hmm... Sorry for the late response. Try this link and see if it works: http://www.kingroot.org/
mach01 said:
Hmm... Sorry for the late response. Try this link and see if it works: http://www.kingroot.org/
Click to expand...
Click to collapse
Thanks I tried almost almost everything.
Stumbled upon Stump root last night and it brute forced it way in.
---------- Post added at 12:46 PM ---------- Previous post was at 12:44 PM ----------
Jshokamp said:
Where you able to get it to work? I am running into the same problems.
Sent from my SM-N920V using Tapatalk
Click to expand...
Click to collapse
What problem? Check one of the thread I started. Posted everything on it.
y300owner said:
Thanks I tried almost almost everything.
Stumbled upon Stump root last night and it brute forced it way in.
---------- Post added at 12:46 PM ---------- Previous post was at 12:44 PM ----------
What problem? Check one of the thread I started. Posted everything on it.
Click to expand...
Click to collapse
You on 39aa or just 39a?
Lawlrus said:
You on 39aa or just 39a?
Click to expand...
Click to collapse
No idea. I was on a downgraded stock ROM, VS980_27A or was it VS980_24A. Can't remember; 4.4.2
Whatever it was, none of the popular rooting method was working. They were managing to do 'semi root' as in root message was displayed in "hard reset mode" and in 'download mode' but there was no root when the OS fully booted. The 'stock recovery' was also corrupted as in it showed a dead android with red exclamation mark. From the searching I did, people were saying there was no recovery installed so I needed one but I could not install. No stock recovery means no 'adb'.
Stump root gave 'complete' root. I hope you understand what I'm trying to say.
Will this work if I am on the 39aa update from Verizon? I am skeptical about this because this is my only phone and don't need to mess it up.
UserofAndroid1813 said:
Will this work if I am on the 39aa update from Verizon? I am skeptical about this because this is my only phone and don't need to mess it up.
Click to expand...
Click to collapse
I don't think I've seen a way to root 39aa as of yet. One of our developers was asking about it as well, if you do find a way, please @ me so I can hook him up
I'm still looking around for a way.
Lawlrus said:
I don't think I've seen a way to root 39aa as of yet. One of our developers was asking about it as well, if you do find a way, please @ me so I can hook him up
I'm still looking around for a way.
Click to expand...
Click to collapse
I tried and failed at it. I am downgrading to VS98039A_05 and going from there. it seems VS9803AA was meant to patch root and also SF security patches.
This XML file does not appear to have any style information associated with it.
The document tree is shown below.
<Error><Code>AccountProblem</Code><Message>
Your Google account is not currently enabled for this operation. Please check https://code.google.com/apis/console/#:billing to see if you have a past due balance or if the credit card (or other payment mechanism) on your account is expired. You can find additional information at https://developers.google.com/storage/docs/signup</Message></Error>
Thanks for this. For people who don't want to mess with Korean, or if Kingroot doesn't work, LG One Click Root still works on VS9803AA, although you may have to run it 3 or 4 times. Here's the original post: http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
And here's a good guide: http://webtrickz.com/how-to-root-lg-g2-running-lollipop-with-lg-one-click-root/
Interesting... I've tried that method four times and it never worked for me. Good to hear it works for other people though. I agree not to many people want to use
Korean deciphering skills just to root their phone but its just an option.
marathonjon said:
Thanks for this. For people who don't want to mess with Korean, or if Kingroot doesn't work, LG One Click Root still works on VS9803AA, although you may have to run it 3 or 4 times. Here's the original post: http://forum.xda-developers.com/lg-g...lipop-t3056951
And here's a good guide: http://webtrickz.com/how-to-root-lg-...ne-click-root/
Click to expand...
Click to collapse
Both of these links are dead.
CruelSun said:
Both of these links are dead.
Click to expand...
Click to collapse
Links are fixed. The whole URLs don't show in the post, but if you click on them, they should work.
those with the issue of kingroot not reading your phone plugged in. put your usb option on phone to PTP camera mode and it will work now.
Even doing all, i m still unable to get my phone recognized. Switched many times befween ptp
Sent from my VS980 4G using Tapatalk
---------- Post added at 05:55 AM ---------- Previous post was at 05:54 AM ----------
Furqan Ullah said:
Even doing all, i m still unable to get my phone recognized. Switched many times befween ptp
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
And other file transfer option. USB picture is displaying sometimes or sometimes circle
Sent from my VS980 4G using Tapatalk
I can confirm that the latest update for the Verizon Moto Z Force patches the quadrooter vulnerabilities.
I took the risk and updated to see if it would and it did.
I would bet money that if you want to root this phone then DO NOT TAKE THIS UPDATE!
I figured this would happen, thank god I trusted my instincts and have been postponing the update since it came out.
Quadrooter doesn't help with unlocking the bootloader that we'd need for root on MM though(?).
Right, but still might have been useful for a soft root...
Sent from my XT1650 using Tapatalk
Why would you softroot anyway? We have a BL unlock. Just wait for a recovery and flash su
We do?
Sent from my XT1650 using Tapatalk
Soft root to hide soft keys in build prop to use lmt launcher for a full screen experience.
Sirshark10 said:
Why would you softroot anyway? We have a BL unlock. Just wait for a recovery and flash su
Click to expand...
Click to collapse
For Moto unlocked devices (developer editions) which have not been released yet.
This is a Verizon OTA for the Verizon Moto Z Force which have locked bootloaders with Verizon signed keys. Unless some amazing leak happens our bootloaders won't be unlocked anytime soon.
derrickmehaffy said:
For Moto unlocked devices (developer editions) which have not been released yet.
This is a Verizon OTA for the Verizon Moto Z Force which have locked bootloaders with Verizon signed keys. Unless some amazing leak happens our bootloaders won't be unlocked anytime soon.
Click to expand...
Click to collapse
Does anyone know what to disable to disable the OTA updates?
Thanks
Smithfolk4 said:
Does anyone know what to disable to disable the OTA updates?
Thanks
Click to expand...
Click to collapse
Need root for that. And with android 6.0 last time i check there is no way to root without a custom recovery. That requires an unlocked bootloader what will not happen.
Take the update root will never come.
bignazpwns said:
Need root for that. And with android 6.0 last time i check there is no way to root without a custom recovery. That requires an unlocked bootloader what will not happen.
Take the update root will never come.
Click to expand...
Click to collapse
Thanks. I took the update. Actually 2. I guess my phone was a bit behind. But, I have been able in the past, using the Debloater tool, to disable the apk for updates. I just don't know what it is for this phone and none of them seem to sound like an update package. If we can identify the apk we can turn it off. Maybe it is done some other way on this phone.
bignazpwns said:
Need root for that. And with android 6.0 last time i check there is no way to root without a custom recovery. That requires an unlocked bootloader what will not happen.
Take the update root will never come.
Click to expand...
Click to collapse
u can disable it without root lol just need to know what
hwy @jcase , was wondering if your new write is able to be utilized on the moto z force droid from verizon?
http://bbqand0days.com/Pork-Explosion-Unleashed/
elliwigy said:
hwy @jcase , was wondering if your new write is able to be utilized on the moto z force droid from verizon?
http://bbqand0days.com/Pork-Explosion-Unleashed/
Click to expand...
Click to collapse
Full details of both detecting possible vulnerable devices, as well as exploitation are in the post. Doing both is trivial.
jcase said:
Full details of both detecting possible vulnerable devices, as well as exploitation are in the post. Doing both is trivial.
Click to expand...
Click to collapse
haha ok, i guess i need to learn more anyways, i will reread it again and again until i understand it lol
thanks for publishing if course, crazy im just barely hearing about it lol seems like a really serious issue on exploitable devices for sure
---------- Post added at 06:57 PM ---------- Previous post was at 06:28 PM ----------
lol my phone says access denied trying to check any system files and the phone doesnt come with a usb cord to plug into the computer to check the commands but i do have an adapter from my note 7 so i will try it here in a bit when i get back home unless someone smarter than me or already checked it wants to chime in...
---------- Post added at 06:59 PM ---------- Previous post was at 06:57 PM ----------
i did research that foxconn does work with moto mobility on some level but wasnt able to narrow it down further than that, most news about foxconn is how they treat their employees and their suicides lol
---------- Post added at 06:59 PM ---------- Previous post was at 06:59 PM ----------
i did also notice they do work on the ps4 which is interesting...
well, there goes that idea.. i cant even get the pc to recognize the phone as an adb device
---------- Post added at 09:34 PM ---------- Previous post was at 09:03 PM ----------
i dont think our phone has adb or fastboot.. no matter what i try i cant get it to be recognized by adb or fastboot unless i am missing something
elliwigy said:
well, there goes that idea.. i cant even get the pc to recognize the phone as an adb device
---------- Post added at 09:34 PM ---------- Previous post was at 09:03 PM ----------
i dont think our phone has adb or fastboot.. no matter what i try i cant get it to be recognized by adb or fastboot unless i am missing something
Click to expand...
Click to collapse
ADB works fine for me. Haven't had a use for fastboot yet, but I'm sure it works.
Sent from my XT1650 using Tapatalk
PiousInquisitor said:
ADB works fine for me. Haven't had a use for fastboot yet, but I'm sure it works.
Click to expand...
Click to collapse
what drivers did you use during install?
elliwigy said:
what drivers did you use during install?
Click to expand...
Click to collapse
None. I use Linux.
Sent from my XT1650 using Tapatalk
PiousInquisitor said:
None. I use Linux.
Click to expand...
Click to collapse
oh lol i got it to work, had to install drivers