Related
So I'm running completely stock, never rooted Android 5.0 on my Nexus 5. I got the 5.0.1 update today and when I go to install, it gives me the dead android pic with "error". Anybody else having the same issue? Also, would me enabling developer options have anything to do with it?
P.S. Already cleared my cache partition and it's still giving me the error.
Oh sweet jesus, how many more threads like this we going to have.
You modified /system in some way. Read one of the million threads already here on the forum with similar problem.
beekay201 said:
Oh sweet jesus, how many more threads like this we going to have.
You modified /system in some way. Read one of the million threads already here on the forum with similar problem.
Click to expand...
Click to collapse
or just give it out so we noobs can easily be guided?
beekay201 said:
Oh sweet jesus, how many more threads like this we going to have.
You modified /system in some way. Read one of the million threads already here on the forum with similar problem.
Click to expand...
Click to collapse
Except, like I said, I didn't. I did not root or unlock the bootloader or play around with the phone at all, strictly for this reason. I didn't want to go through the struggle of factory resetting my device every now and then. The closest thing to "modifying" the phone was me unlocking developer settings and I was asking if that could have something to do with it.
Every other thread on the forums has to do with people rooting so no, it's not like one of the millions of other threads.
Describe more.
The best way to update is by flashing the factory image in fastboot, i don`t trust/hate OTA`s personaly
I updated from kitkat to Lollipop with no issues from the OTA update. That was really recent and I haven't changed anything having to do with the system since then. Yet the 5.0.1 update is giving me the error message.
I'm trying to avoid doing a factory reset as that was the main reason that I've kept the phone completely stock. I figured not rooting the phone would let me update in peace and, since it's a nexus, it's been enough to handle my needs without any customization.
kubus908 said:
I updated from kitkat to Lollipop with no issues from the OTA update. That was really recent and I haven't changed anything having to do with the system since then. Yet the 5.0.1 update is giving me the error message.
I'm trying to avoid doing a factory reset as that was the main reason that I've kept the phone completely stock. I figured not rooting the phone would let me update in peace and, since it's a nexus, it's been enough to handle my needs without any customization.
Click to expand...
Click to collapse
Is your bootloader unlocked? I don't know why the ota isn't working but something must have changed on your device
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Is your bootloader unlocked? I don't know why the ota isn't working but something must have changed on your device
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Just double checked and nope, bootloader is locked. Yeah :/ I was trying to see if it's an issue with anybody else on completely stock devices. So far mine is a no go, even though the 5.0 update worked flawlessly. Why would the 5.0 update go through, yet the 5.0.1 believes the system has been modified..?
kubus908 said:
Just double checked and nope, bootloader is locked. Yeah :/ I was trying to see if it's an issue with anybody else on completely stock devices. So far mine is a no go, even though the 5.0 update worked flawlessly. Why would the 5.0 update go through, yet the 5.0.1 believes the system has been modified..?
Click to expand...
Click to collapse
Well, there's a way to get the ota but it is going to be tedious. It involves rooting with towelroot, then using bootunlocker from the play store. That'll allow you to unlock the bootloader without wiping your device. Then you'll need to flash the system, boot, and recovery image with fastboot from the 5.0 factory image. Then do the ota.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Well, there's a way to get the ota but it is going to be tedious. It involves rooting with towelroot, then using bootunlocker from the play store. That'll allow you to unlock the bootloader without wiping your device. Then you'll need to flash the system, boot, and recovery image with fastboot from the 5.0 factory image. Then do the ota.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
May as well skip the ota if you're going to go through this process.
---------- Post added at 07:06 PM ---------- Previous post was at 07:05 PM ----------
digitLIX said:
or just give it out so we noobs can easily be guided?
Click to expand...
Click to collapse
Or wait for the next time the question is asked.
Should be any minute now.
Thanks! I may just wait until the next update and see if there's a chance it'll work. Or I may just have to do a fresh new install which I am not looking forward to at all Lol. But thank you for your help!
Uhhhh, ok. So I'm not exactly sure what happened. I figured I'd give the OTA another try because why not...and it worked I noticed it downloaded a bigger file too, 30ish mb as opposed to the 13mb OTA that would give me an error. Not sure if I got sent a wrong update file or what, but if your issue comes close to what I experienced, just keep trying the OTA update. I'm also on T-Mobile (phone bought directly from T-Mobile) in case that makes any difference.
So AT&T and LG released a new update to 21r two days ago. Has anyone gotten it yet, and if so, are you able to root it?
shxrm_ said:
So AT&T and LG released a new update to 21r two days ago. Has anyone gotten it yet, and if so, are you able to root it?
Click to expand...
Click to collapse
I have the same question. According to the release notes for 21r, the purpose was to update security. It appears that this is the stagefright patch.
EDIT: Appears to still be rootable.
There have been a number of security issues of a magnitude that require patches. Whether rooting is a primary reason is debatable but based on the small % that root I doubt it is a major concern.
aybarrap1 said:
I have the same question. According to the release notes for 21r, the purpose was to update security. I hate to think that AT&T might have intentionally worked to prevent rooting and Bump'd. Would not surprise me. AT&T has strangely been releasing a lot of updates over the last 6 months or so which is very unlike them. I have to wonder if they have not been working to prevent rooting as rooting has become harder and harder.
Click to expand...
Click to collapse
That's literally the only reason why I'm still on 20f, and usually I would just update my phone right away to get the security. I just wanted to know if it's possible
autosurgeon said:
There have been a number of security issues of a magnitude that require patches. Whether rooting is a primary reason is debatable but based on the small % that root I doubt it is a major concern.
Click to expand...
Click to collapse
I see your point.
21r has made. Usb debugging and usb tethering permanently greyed out. Have not been able to root. Yet.
Sent from my LG-D850 using Tapatalk
---------- Post added at 12:33 PM ---------- Previous post was at 11:52 AM ----------
False alarm. McAfee had phone locked down. Got usb debug. Haven't tried rooting yet.
Sent from my LG-D850 using Tapatalk
The short answer is: yes, it is rootable.
The long answer: It took me many hours to wipe and update my phone. I had to try the factory reset a few times for it to finally work (I got stuck at "stage 2"), it was almost two hours waiting for the updates to download, and then I had to try the one-click root script a few times, but finally I have 21R with SuperSU on my phone. Yay. Also, the Zimperium stagefright detector says that my phone is no longer vulnerable. Yay.
pigrew said:
The short answer is: yes, it is rootable.
The long answer: It took me many hours to wipe and update my phone. I had to try the factory reset a few times for it to finally work (I got stuck at "stage 2"), it was almost two hours waiting for the updates to download, and then I had to try the one-click root script a few times, but finally I have 21R with SuperSU on my phone. Yay. Also, the Zimperium stagefright detector says that my phone is no longer vulnerable. Yay.
Click to expand...
Click to collapse
Hopefully it works for me, cause people said root worked for them on 21q, but it never worked for me
pigrew said:
The short answer is: yes, it is rootable.
The long answer: It took me many hours to wipe and update my phone. I had to try the factory reset a few times for it to finally work (I got stuck at "stage 2"), it was almost two hours waiting for the updates to download, and then I had to try the one-click root script a few times, but finally I have 21R with SuperSU on my phone. Yay. Also, the Zimperium stagefright detector says that my phone is no longer vulnerable. Yay.
Click to expand...
Click to collapse
Looks like I will go through the long process of unrooting now. Been avoiding the OTAs since lollipop update because of the hassle of having to unroot. I am glad to see that AT&T actually worked quickly with LG on patching stagefright. Being able to root again was a main concern.
UPDATE: Thus far, after backing up all my data and apps (I use both LGs backup and TiBu to do batch backups), I have downgraded to stock unroot, and it took 3 OTAs (21f, 21q, and 21r) to get to where I am at. The unroot method only took about 10 minutes but I already had everything set up from my previous upgrade to Lollipop. The OTA updates were painful as they took a while to download and install (700+mB, 205mB, and 23mB respectively so about 1gig of wifi data) along with the optimization of apps each time. I have now successfully rooted.
Hey everyone 21r is rootable. I was on 21q and rooted i went back to stock went through all the updates, and then used this method here:
http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197
and I cant stresss this enough, YOU HAVE TO USE METHOD 2 WHERE TO TYPE OUT THE COMMANDS.
I used that first time with no issues
Firebourne said:
Hey everyone 21r is rootable. I was on 21q and rooted i went back to stock went through all the updates, and then used this method here:
http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197
and I cant stresss this enough, YOU HAVE TO USE METHOD 2 WHERE TO TYPE OUT THE COMMANDS.
I used that first time with no issues
Click to expand...
Click to collapse
Thanks for the confirmation of root as well as the the exact method that worked for you. I will be giving this a shot this afternoon. I want to take advantage of the stagefright patch while keeping root.
UPDATE: This root method worked. Had to do it twice but got it working.
Mjengles said:
21r has made. Usb debugging and usb tethering permanently greyed out. Have not been able to root. Yet.
Sent from my LG-D850 using Tapatalk
---------- Post added at 12:33 PM ---------- Previous post was at 11:52 AM ----------
False alarm. McAfee had phone locked down. Got usb debug. Haven't tried rooting yet.
Sent from my LG-D850 using Tapatalk
Click to expand...
Click to collapse
I noticed that USB Debugging is greyed out when connected to USB. However upon disconnecting it was able to be checked. On my second go round to root, I had to disconnect, uncheck USB debugging, reenable then plug in.
It still refuses to work for me. I didn't change the diag port from when I restored back to stock, and I've tried it a few times just now, all to no effect.
Edit: the thing finally worked for me! I just closed the command prompt after the "send_command" part didn't work for me, and just did that part over, and it worked!!
CAUTION!!!!
To anyone who has succesfully rooted 21r, don't flash TWRP! After I used AutoRec to flash it, went to TWRP, and flashed the Xposed framework, I went to reboot, and my phone wouldn't boot up! It kept giving the LG logo, with security error under it! I am currently in the process of flashing back to do it all over smh
shxrm_ said:
To anyone who has succesfully rooted 21r, don't flash TWRP! After I used AutoRec to flash it, went to TWRP, and flashed the Xposed framework, I went to reboot, and my phone wouldn't boot up! It kept giving the LG logo, with security error under it! I am currently in the process of flashing back to do it all over smh
Click to expand...
Click to collapse
if you go here http://forum.xda-developers.com/att-lg-g3/orig-development/bump-unlock-lg-g3-twrp-t2900569 and download the bump'd twrp and flash it through flashify on the phone it will work and then you can use flashify to download and flash the newest twrp the new update doesnt have to be bump'd as long as the first flash is. I did this after getting that stupid error multiple times lol
shxrm_ said:
To anyone who has succesfully rooted 21r, don't flash TWRP! After I used AutoRec to flash it, went to TWRP, and flashed the Xposed framework, I went to reboot, and my phone wouldn't boot up! It kept giving the LG logo, with security error under it! I am currently in the process of flashing back to do it all over smh
Click to expand...
Click to collapse
You don't need to start all over. Just install the Gabriel kernel in twrp and you are good.
Sent from my LG-D850 using XDA Free mobile app
---------- Post added at 12:25 PM ---------- Previous post was at 12:21 PM ----------
Firebourne said:
if you go here http://forum.xda-developers.com/att-lg-g3/orig-development/bump-unlock-lg-g3-twrp-t2900569 and download the bump'd twrp and flash it through flashify on the phone it will work and then you can use flashify to download and flash the newest twrp the new update doesnt have to be bump'd as long as the first flash is. I did this after getting that stupid error multiple times lol
Click to expand...
Click to collapse
That only refers to secure boot errors booting twrp not booting the phone.
Sent from my LG-D850 using XDA Free mobile app
Link please? I searched the development threads, but didn't find the kernel you mentioned
shxrm_ said:
Link please? I searched the development threads, but didn't find the kernel you mentioned
Click to expand...
Click to collapse
http://forum.xda-developers.com/lg-g3/development/lollipopstockkernelgabriel5-d855-t3120893
aybarrap1 said:
I noticed that USB Debugging is greyed out when connected to USB. However upon disconnecting it was able to be checked. On my second go round to root, I had to disconnect, uncheck USB debugging, reenable then plug in.
Click to expand...
Click to collapse
Second method of rooting worked for me. Hello control.....goodbye warranty
Sent from my ASUS MeMO Pad 7 using Tapatalk
Is there a bootable zip of the lastest stock Att ROM? Thanks.
Computerfreek274 Turbopop Android Pay
11/07/2015 Update This Android pay build has been updated to the newest tweaks it is running clean and wifi tether is working great. Android pay is also working 100% I just tested it at 3 stores today. Please remember this IMG has no root! however it is clean of junk and tweaked for speed with WIFI tether. For most users looking to root it was just to get wifi tether for the unlimited users. This rom is great if you like an clean stock android phone with working android pay and wifi tether.
Please ReadThis is an un-rooted Img to Support for android pay.This system image Is for users looking for a tweaked system better battery life and boosted audio and removed bloatware and Android Pay!
So if you looking to still have a tweaked and clean phone but still you like to use android pay then this img is for you. Google android pay is checking for root all the time and unlocked boot loaders. So we can only hope to get an patched ver of android pay one day for rooted phones. So for now I am going to work on this IMG it will be lean and clean with some great tweaks and boosted audio.
Whats in this IMG ?
. (SU4TL-44) Please Update the IMG files read the readme file in zip on an how to.
. Wifi Tether HotSpot
. Ios emoji REMOVED!
. Removed Junk AKA bloatware
. Internet Tweaks
. Battery Tweaks
. Android Pay Support
. Boosted Audio Boosted phone audio.
. Faster Ring time on outgoing calls
. Ad blocking Coming soon.
Whats not in this IMG ?
Root
V4A
What is next for this IMG ?
Advanced Power menu.
Better Audio
And more.
Download 1.1 Of Computerfreek274_TurboPOP_AndroidPay Here
Uploading now 11/07/2015 @ 10:15 AM Please give it an hour or so to show up on the server.
Help And Support
Please Backup data! Photos and stuff you need just in case! I am not to be help responsible for data loss or if your phone dies.
This IMG has been tested on 4 phones today 2 of them needed a full wipe to get it it boot so please keep this in mine that you may have to do a full data wipe.
Please read the readme file to upgrade your modem and kernel to the newest ver.
Preparing to install this img when coming from an img with root xposed stuff like this. 1. Uninstall xposed and any mods reboot when done. Step 2 Flash via mofo let it try and boot if it hangs on the moto screen. Hold down power enter recovery and wipe cache and reboot. 3. Download android pay and update android services VIA google market setup android pay update remove cards it will not matter at this point. Just remember android pay only supports some cards and the ones you already have on your account. Also you now have to add you google wallet credit card to android pay as wallet and android pay are split up now.
If you can not boot no matter what you do and you forgot to backup your data then flash back the img you where on and boot BACK UP YOU DATA! Then start over with step 1. and when you get to step 2. Wipe cache and data.
ill be first to jump on this, can we add cards?
Michaelmansour1997 said:
ill be first to jump on this, can we add cards?
Click to expand...
Click to collapse
Yeah supported card and cards that you already had on your account also you google wallet card can be added. Wifi tether will also still work for users that need this. Just remember there will be no root so what i add is what you get.
Would you be willing to drop in the latest AdAway host file, and then I'm personally at 98% of why I run root on my phone?
Thanks again for all the hard work!!!
Anybody else getting an "Access Denied" when clicking on the link?
GeoFX said:
Anybody else getting an "Access Denied" when clicking on the link?
Click to expand...
Click to collapse
Yes, looks like he didn't switch the permissions on the folder yet
GeoFX said:
Anybody else getting an "Access Denied" when clicking on the link?
Click to expand...
Click to collapse
i put the 30th on the forum as I am still testing. I will release soon maybe in a bit ran into a bug I had to fix.
rgerrans said:
Would you be willing to drop in the latest AdAway host file, and then I'm personally at 98% of why I run root on my phone?
Thanks again for all the hard work!!!
Click to expand...
Click to collapse
Already done will work with adaway just as you did with my rooted img's.
computerfreek274 said:
Already done will work with adaway just as you did with my rooted img's.
Click to expand...
Click to collapse
Great news, thanks!!
So now I have to choose between gravitybox and Android Pay?
gqskrub said:
So now I have to choose between gravitybox and Android Pay?
Click to expand...
Click to collapse
For me it is easy as soon as I am done testing and tweaking this build I will be back on my rooted 493 img. I can always pull out a credit card to pay for somthing not like any of us walk around with your phone only and not you real wallet.
Help and Support Update
For android Pay I will post updates on my website and on XDA and remember android pay is an unrooted tweaked img with ad blocking and more.
On my website Computerfreek.com Now has updated help and support how to setup stuff like adaway,Boot anamation, Dpi and more.
I will also be posting Pre-Release images there days before there on XDA for testing. There will also be images some custom images that will not ever be listed on here on XDA. So please check out the site it is still a work in progress but it is getting there. As of right now I did not get custom IMG listed and the newest ver is still 1.6 and it is listed below. I hope to clean up OP this week with some of the same info found on my website. I maybe doing an order page where you can order an custom IMG for a fee with 3 free Updates per IMG.
I have tried everything and cannot get audio to work at all. Is anyone else having this issue or know of a fix?
Anybody using this ROM verify it still works since the security net update?
mrkhigh said:
Anybody using this ROM verify it still works since the security net update?
Click to expand...
Click to collapse
Dude this is a old image from before we had bootloader unlock and real root. This is useless now.. do your research
Sent from my DROID Turbo using Tapatalk
computerfreek274 said:
For me it is easy as soon as I am done testing and tweaking this build I will be back on my rooted 493 img. I can always pull out a credit card to pay for somthing not like any of us walk around with your phone only and not you real wallet.
Click to expand...
Click to collapse
Right. You have to pull out SOMETHING -- whether your phone or your credit card. It's the same action. Using the phone is not really any easier.
And in the real world, no one leaves the house without their wallet. Occasionally going to work, I have left my phone at the house, but I've never left my wallet.
---------- Post added at 09:10 AM ---------- Previous post was at 09:08 AM ----------
PILLMUZIK3600 said:
Dude this is a old image from before we had bootloader unlock and real root. This is useless now.. do your research
Sent from my DROID Turbo using Tapatalk
Click to expand...
Click to collapse
Argghhh. I wish people would STOP digging up old threads. STOP IT. THIS is from September 2015! NOTHING from back then for the XT1254 is relevant for now. And Safety Net has been updated many, many times since then to block people. Anything that worked over a year ago sure wouldn't work now.
However, usually it's people who won't believe you need to pay for Sunshine to unlock their XT1254 bootloader. They dig up year old threads to ask the same question over and over like they are going to get a different answer.
Wow, you are really upset there buddy. Sorry that it bothers you. But to me, this is relevant. I have mofo root not sunshine, and i dont see the point in going through all the effort of sunshine and new roms, when moforoot works perfect. Furthermore i surely might be wrong, but i didn't see a lollipop or marshmallow ROM with these features (tweaked, tether, android pay).
I was simply asking if there was anyone who know how to get the audio working with this ROM. If you don't know, then just don't reply. What's the point in posting just to complain?
ChazzMatt said:
Right. You have to pull out SOMETHING -- whether your phone or your credit card. It's the same action. Using the phone is not really any easier.
And in the real world, no one leaves the house without their wallet. Occasionally going to work, I have left my phone at the house, but I've never left my wallet.
---------- Post added at 09:10 AM ---------- Previous post was at 09:08 AM ----------
Argghhh. I wish people would STOP digging up old threads. STOP IT. THIS is from September 2015! NOTHING from back then for the XT1254 is relevant for now. And Safety Net has been updated many, many times since then to block people. Anything that worked over a year ago sure wouldn't work now.
However, usually it's people who won't believe you need to pay for Sunshine to unlock their XT1254 bootloader. They dig up year old threads to ask the same question over and over like they are going to get a different answer.
Click to expand...
Click to collapse
BriCo84 said:
Wow, you are really upset there buddy. Sorry that it bothers you. But to me, this is relevant. I have mofo root not sunshine, and i dont see the point in going through all the effort of sunshine and new roms, when moforoot works perfect. Furthermore i surely might be wrong, but i didn't see a lollipop or marshmallow ROM with these features (tweaked, tether, android pay).
I was simply asking if there was anyone who know how to get the audio working with this ROM. If you don't know, then just don't reply. What's the point in posting just to complain?
Click to expand...
Click to collapse
If you are still on Moforoot (with Kitakat 4.4.4 base installing a "Lollipop" image), you are 1 in a million. You're a year behind all the dev work.
And the ROM will NOT work with Android Pay -- due to all the Android Pay/Safety Net updates the past year. SafetyNet will detect Moforoot. It's obsolete, out of date ROM that will no longer work.
5th May 2016, 02:43 PM
TheSt33v said:
Getting Android Pay to work on a modified device is a constant cat and mouse game. A few workarounds were found and promptly patched by Google in Android Pay/Google Play Services/ Google App updates. If you use it frequently, unlocking is a bad idea. Android Pay might still work on an unlocked device, but any change that you make to any system files will cause it to not work, so there's no point in unlocking.
Even if you managed to root without unlocking (via moforoot or through the terrible kingroot method), you would break Android Pay because root is one of the first things that it looks for, and none of the apps/xposed modules designed to fool it are successful at doing so.
Click to expand...
Click to collapse
It isn't a miracle..
If this is a very stock ROM it should still make it past safety net.
mrkhigh said:
It isn't a miracle..
If this is a very stock ROM it should still make it past safety net.
Click to expand...
Click to collapse
It won't. Please let the year old thread die. It was dead for a reason.
This was back 6 months ago and Safetynet has been updated several times since then.
5th May 2016, 02:43 PM
TheSt33v said:
Getting Android Pay to work on a modified device is a constant cat and mouse game. A few workarounds were found and promptly patched by Google in Android Pay/Google Play Services/ Google App updates. If you use it frequently, unlocking is a bad idea. Android Pay might still work on an unlocked device, but any change that you make to any system files will cause it to not work, so there's no point in unlocking.
Even if you managed to root without unlocking (via moforoot or through the terrible kingroot method), you would break Android Pay because root is one of the first things that it looks for, and none of the apps/xposed modules designed to fool it are successful at doing so.
Click to expand...
Click to collapse
I had been reading up on the Dirty Cow exploit/root method, and it seemed to be compatible with all Android devices, so I took a little chance with my v10, and it worked perfectly! I was on the stock unrooted 20l update, and followed all the steps here: https://github.com/jcadduono/android_external_dirtycow#running
Notes:
-I put our TWRP image and SuperSu zip on the root of my sdcard
-For the very last command, replace 'twrp.img' with the name of your TWRP image file(or change the name of your TWRP fiile to twrp.img ).
-Like it says in the instructions, the phone did look like maybe it bricked at one point, with a strange backlighting on the Tmobile boot screen. It worked out tho!
-My boot loader was unlocked prior to doing these steps
Info thread, v20: http://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
Got all the files here: https://build.nethunter.com/android-tools/dirtycow/arm64/
YrrchSebor said:
I had been reading up on the Dirty Cow exploit/root method, and it seemed to be compatible with all Android devices, so I took a little chance with my v10, and it worked perfectly! I was on the stock unrooted 20l update, and followed all the steps here: https://github.com/jcadduono/android_external_dirtycow#running
Notes:
-I put our TWRP image and SuperSu zip on the root of my sdcard
-For the very last command, replace 'twrp.img' with the name of your TWRP image file(or change the name of your TWRP fiile to twrp.img ).
-Like it says in the instructions, the phone did look like maybe it bricked at one point, with a strange backlighting on the Tmobile boot screen. It worked out tho!
Info thread, v20: http://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
Got all the files here: https://build.nethunter.com/android-tools/dirtycow/arm64/
Click to expand...
Click to collapse
Great job. You know technically these same instructions should work for ANY of the v10 variants ..verizon...at&t etc....including the ones that up till now didn't have root at all.
Thanks. Doesn't it require an unlocked boot loader tho, or no?
Sent from my LG-H901 using XDA-Developers mobile app
YrrchSebor said:
Thanks. Doesn't it require an unlocked boot loader tho, or no?
Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Click to collapse
It requires an unlocked boot loader.
YrrchSebor said:
Thanks. Doesn't it require an unlocked boot loader tho, or no?
Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes but for example verizon's comes with an unlocked bootloader...they just only had root for the 5.x rom's and none for the 6.0.
famewolf said:
Yes but for example verizon's comes with an unlocked bootloader...they just only had root for the 5.x rom's and none for the 6.0.
Click to expand...
Click to collapse
Gotcha yeah, it seems like good news for all phones with unlockable bootloaders until Google, and then the OEMs, patch the exploit.
Sent from my LG-H901 using XDA-Developers mobile app
will this factory reset my phone?
CrimsonSaber5G said:
will this factory reset my phone?
Click to expand...
Click to collapse
Nope. Unlocking your bootloader will but this won't in itself.
Sent from my LG-H901 using XDA-Developers mobile app
thank you, and i have the tmobile variant, that means my bootloader is already unlocked??
CrimsonSaber5G said:
thank you, and i have the tmobile variant, that means my bootloader is already unlocked??
Click to expand...
Click to collapse
No, it means it's unlockable, but you have to actively unlock it. There should be a thread here somewhere if you haven't done that yet, but it's just boot into bootloader and then 'fastboot oem unlock'
Edit: in case you need it there are great instructions in the v20 thread that I linked in the first post.
Sent from my LG-H901 using XDA-Developers mobile app
YrrchSebor said:
Gotcha yeah, it seems like good news for all phones with unlockable bootloaders until Google, and then the OEMs, patch the exploit.
Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Click to collapse
The cow method means copy on write...
This means as anything is written it is copied (or flashed or burned; whatever you want to call your desired definition)
You could in theory copy dummy files to a temp location and actually write to a permanent location...
Or am I thinking wrong about it?
If this is a viable option to ALL phones I don't think Google or manufactures could (or would for that matter) actually patch this kind of exploit as it would be super time consuming.
just confirming that Root 20l w/Dirty Cow does work.
Finally got my replacement V10 back, and all is a go again. Stock rooted,
Not sure the novice should try this, as its pretty nerve racking. If you follow the directions correctly it does work great.
Surprised they have closed this backdoor yet,
thanks for being the first to try this on a V10.
je2854 said:
The cow method means copy on write...
This means as anything is written it is copied (or flashed or burned; whatever you want to call your desired definition)
You could in theory copy dummy files to a temp location and actually write to a permanent location...
Or am I thinking wrong about it?
If this is a viable option to ALL phones I don't think Google or manufactures could (or would for that matter) actually patch this kind of exploit as it would be super time consuming.
Click to expand...
Click to collapse
I think it's considered a very serious vulnerability that must and will be patched soon. They can't have root access so easily obtained on any device.
Amd4life said:
just confirming that Root 20l w/Dirty Cow does work.
Finally got my replacement V10 back, and all is a go again. Stock rooted,
Not sure the novice should try this, as its pretty nerve racking. If you follow the directions correctly it does work great.
Surprised they have closed this backdoor yet,
thanks for being the first to try this on a V10.
Click to expand...
Click to collapse
You're welcome, and thanks for confirming. That one step where the screen goes weirdly backlit with the Tmo splash screen is a bit nerve-wracking, and so is writing recovery this way, but I was comforted by the fact that you can just tell it to to write to the recovery partition rather than having to know the more technical name/location(not sure if this was possible a few years back?)
Anyway, if I did brick I was gonna go straight to the store and buy a ZTE Zmax Pro for $180 haha.
Which reminds me, does anyone know if there is a way to simply push su into /system once you have the root shell, instead of writing recovery to flash SuperSu? Just curious. I sorta wanted to do that but then I just went with TWRP.
YrrchSebor said:
Which reminds me, does anyone know if there is a way to simply push su into /system once you have the root shell, instead of writing recovery to flash SuperSu? Just curious. I sorta wanted to do that but then I just went with TWRP.
Click to expand...
Click to collapse
No. The shell has limited access...it has just enough permissions to write recovery and access some things on boot...you need to get it a recovery where you can then flash a zip to install superuser.
Thanks so much for this info, I was actually about to post a new thread to see if root for 20L had been achieved.
But a few questions:
Is there a KDZ/TOT available for 20L? Or is it delivered in update.zip format via OTA?
Is there a way to root 20L without touching system partition? Like, you know, systemless root? I was thinking that maybe it might be possible to flash Magisk from TWRP then install systemless phh Superuser or (less preferable for me) SuperSU. This way I can still take the official Nougat OTA when it hits, without losing root. But the catch is, TWRP needs to be accessible first.
Well, time to sleep for now, it's been a long 3 days, subsisting on Monster and cigs. I'll tackle this when I eventually wake up.
Like the last guy, I've got a million questions on this. I need to find the changelog on 20L to begin with, because if they didn't fix the VoLTE silence on calling, then it's useless to me. I wonder where the OP was with his existing V10.. because I'm currently on 20J rooted with twrp. Seems with the instructions posted, I would have to use LG bridge to go back to 100% stock, then upgrade to 20L then hope this works. Again, the radios are probably modified so there's probably some kind of anti-rollback involved as well.
Great post though! Great work discovering this! Definitely in the right direction!
AnonVendetta said:
Thanks so much for this info, I was actually about to post a new thread to see if root for 20L had been achieved.
But a few questions:
Is there a KDZ/TOT available for 20L? Or is it delivered in update.zip format via OTA?
Is there a way to root 20L without touching system partition? Like, you know, systemless root? I was thinking that maybe it might be possible to flash Magisk from TWRP then install systemless phh Superuser or (less preferable for me) SuperSU. This way I can still take the official Nougat OTA when it hits, without losing root. But the catch is, TWRP needs to be accessible first.
Well, time to sleep for now, it's been a long 3 days, subsisting on Monster and cigs. I'll tackle this when I eventually wake up.
Click to expand...
Click to collapse
There is a 20l KDZ floating around in some other threads. Not sure if there is or will be a systemless root, never even done it myself [emoji4]
Sent from my LG-H901 using XDA-Developers mobile app
joesee said:
Like the last guy, I've got a million questions on this. I need to find the changelog on 20L to begin with, because if they didn't fix the VoLTE silence on calling, then it's useless to me. I wonder where the OP was with his existing V10.. because I'm currently on 20J rooted with twrp. Seems with the instructions posted, I would have to use LG bridge to go back to 100% stock, then upgrade to 20L then hope this works. Again, the radios are probably modified so there's probably some kind of anti-rollback involved as well.
Great post though! Great work discovering this! Definitely in the right direction!
Click to expand...
Click to collapse
The Volte silence bug is fixed in 20l, as many have reported. I had updated officially to 20l and was stock unrooted prior to this. But for people who are rooted on 20j or earlier, I believe Eliminator has released a pre-rooted update, so maybe you'd wanna do that instead.
Sent from my LG-H901 using XDA-Developers mobile app
Hi everyone,
I have a the Google edition of Pixel, and have unlocked the bootloader successfully. I would like to root the device somethow, as well as get tether working. I am on Vzw's original unlimited data plan, and this phone has replaced my wife's Samsung Galaxy S3 phone on verizon. We held on to the S3 for so long as it is rooted and with the ROM we could tether using Vzw's tether and pay nothing extra.
What can I do to get back into a similar situation with this Google Pixel?
Thanks so much in advance.
statustray said:
Hi everyone,
I have a the Google edition of Pixel, and have unlocked the bootloader successfully. I would like to root the device somethow, as well as get tether working. I am on Vzw's original unlimited data plan, and this phone has replaced my wife's Samsung Galaxy S3 phone on verizon. We held on to the S3 for so long as it is rooted and with the ROM we could tether using Vzw's tether and pay nothing extra.
What can I do to get back into a similar situation with this Google Pixel?
Thanks so much in advance.
Click to expand...
Click to collapse
Install twrp and flash magisk for root. Any root tether app should be able to treat your tether data as standard data
KittyRgnarok said:
Install twrp and flash magisk for root. Any root tether app should be able to treat your tether data as standard data
Click to expand...
Click to collapse
Thanks KittyRgnarok,
Do you have a link for Twrp for Google Pixel and also one for majisk? It seems some threads are old, and I don't want to mess things up.
Thanks so much in advance.
statustray said:
Thanks KittyRgnarok,
Do you have a link for Twrp for Google Pixel and also one for majisk? It seems some threads are old, and I don't want to mess things up.
Thanks so much in advance.
Click to expand...
Click to collapse
Haha good on you for asking cuz quite a few people have gotten close to bricking their devices using the boot-to-root method from the day the phone released lmao. A quick Google search for "twrp sailfish" will bring u to the latest version of official twrp. As far as magisk just look up magisk on XDA and the official thread will have the dl link (don't download magisk from anywhere else)
There's a Magisk "Tethering Enabler" module which I recommend you try, after you're rooted.
KittyRgnarok said:
Haha good on you for asking cuz quite a few people have gotten close to bricking their devices using the boot-to-root method from the day the phone released lmao. A quick Google search for "twrp sailfish" will bring u to the latest version of official twrp. As far as magisk just look up magisk on XDA and the official thread will have the dl link (don't download magisk from anywhere else)
Click to expand...
Click to collapse
mike.s said:
There's a Magisk "Tethering Enabler" module which I recommend you try, after you're rooted.
Click to expand...
Click to collapse
Thanks fur the info KittyRgnarok and mike.s,
I will try to do that tomorrow. Got sidetracked by a few other honey dos. Will try my very best to get back on this tomorrow. I hope you don't mind me reaching tomorrow evening after I get off work.
TIA
statustray said:
Thanks fur the info KittyRgnarok and mike.s,
I will try to do that tomorrow. Got sidetracked by a few other honey dos. Will try my very best to get back on this tomorrow. I hope you don't mind me reaching tomorrow evening after I get off work.
TIA
Click to expand...
Click to collapse
No problem man and no worries. If you find yourself needing any help feel free to quote me in the thread or pm me.
KittyRgnarok said:
No problem man and no worries. If you find yourself needing any help feel free to quote me in the thread or pm me.
Click to expand...
Click to collapse
Hi KittRgnarok,
I have downloaded the following to my computer:
twrp-3.2.1-2-sailfish.img
twrp-pixel-installer-sailfish-3.1.1-2.zip
Magisk-v16.0.zip
My computer is a macbook pro so I don't believe I need any additional drivers as supposedly they are already available in the Mac OS. I was able to unlock my bootloader using a terminal session & adb.
How should I now proceed?
Thanks in advance.
statustray said:
Hi KittRgnarok,
I have downloaded the following to my computer:
twrp-3.2.1-2-sailfish.img
twrp-pixel-installer-sailfish-3.1.1-2.zip
Magisk-v16.0.zip
My computer is a macbook pro so I don't believe I need any additional drivers as supposedly they are already available in the Mac OS. I was able to unlock my bootloader using a terminal session & adb.
How should I now proceed?
Thanks in advance.
Click to expand...
Click to collapse
Correct MacBook shouldn't needed additional drivers. Put the magisk and twrp zip files on your phone. Then reboot into bootloader. From there use the command fastboot boot twrp-3.2.1-2-sailfish.img which should put you into ram version of twrp. From here decrypt your device and install the twrp installer zip file. Once that's done reboot into recovery and flash magisk and you should be good to go
I finally got it figured out I have installed TWRP, as well as Majisk. I've tested root using a root tester, and now I need to see about the module that mike.s was referring to- specifically "tethering enabler".
All this stuff is totally new to me, so I am creeping along at a slow pace... lol
statustray said:
I finally got it figured out I have installed TWRP, as well as Majisk. I've tested root using a root tester, and now I need to see about the module that mike.s was referring to- specifically "tethering enabler".
All this stuff is totally new to me, so I am creeping along at a slow pace... lol
Click to expand...
Click to collapse
In magisk manager there is a downloads tab and a modules tab. Go to the downloads tab and look for tether and you'll find it
KittyRgnarok said:
Correct MacBook shouldn't needed additional drivers. Put the magisk and twrp zip files on your phone. Then reboot into bootloader. From there use the command fastboot boot twrp-3.2.1-2-sailfish.img which should put you into ram version of twrp. From here decrypt your device and install the twrp installer zip file. Once that's done reboot into recovery and flash magisk and you should be good to go
Click to expand...
Click to collapse
You must've been posting as I was typing my message to you. I'm just now seeing that you provided some steps. Yes, I had figured that out and got it done. Life's good now.
I am doing some searching trying to figure out tethering, that's the last piece of the equation for now... hehehe..... On the old vzw unlimited data plan and I don't want to switch over to their new plans. If I can get this going, then my better half will be super happy, and then I will look into getting me a Google Pixel (but the XL version).
KittyRgnarok said:
In magisk manager there is a downloads tab and a modules tab. Go to the downloads tab and look for tether and you'll find it
Click to expand...
Click to collapse
Thanks so much KittyRgnarok,
You pointed me in the right direction and I really appreciate that. It worked with no problems as I tested it and all's well. I then demonstrated it to my better half and she is super happy!!
Now I will order me one as well, but I am going to get the Google Pixel XL. I see the screen is larger on the Pixel 2, but heard there's been some "screen issues"? For me the lack of a phone jack is not all that big of a deal as I never hookup a wired headset and only use the bluetooth. *Ahem* on my phone I've only used a wired headset once or twice years ago when my bluetooth messed up. Lol....
Thanks again for everything!
:good:
statustray said:
Thanks so much KittyRgnarok,
You pointed me in the right direction and I really appreciate that. It worked with no problems as I tested it and all's well. I then demonstrated it to my better half and she is super happy!!
Now I will order me one as well, but I am going to get the Google Pixel XL. I see the screen is larger on the Pixel 2, but heard there's been some "screen issues"? For me the lack of a phone jack is not all that big of a deal as I never hookup a wired headset and only use the bluetooth. *Ahem* on my phone I've only used a wired headset once or twice years ago when my bluetooth messed up. Lol....
Thanks again for everything!
:good:
Click to expand...
Click to collapse
Glad to hear both you and her are happy with the results . As far as the pixel 2 xl a lot of the screen issues were software side but there are also issues with burn in(which I've experienced a decent amount of on the og as well) I have a friend with the pixel 2 and I highly recommend it but be aware that it is modding hell if you intend to be messing with a lot of that. As far as staying on stock rom+magisk+Xposed though it works great.
Hi everyone
Can anyone please let me know if the files he downloaded is the same files i need to do the same procedure, i have a normal google pixel 32gb from verizon which i unlocked the bootloader on 7.1 then upgraded to 8.1
S7sadly said:
Can anyone please let me know if the files he downloaded is the same files i need to do the same procedure, i have a normal google pixel 32gb from verizon which i unlocked the bootloader on 7.1 then upgraded to 8.1
Click to expand...
Click to collapse
Same files.
Thank you
KittyRgnarok said:
Glad to hear both you and her are happy with the results . As far as the pixel 2 xl a lot of the screen issues were software side but there are also issues with burn in(which I've experienced a decent amount of on the og as well) I have a friend with the pixel 2 and I highly recommend it but be aware that it is modding hell if you intend to be messing with a lot of that. As far as staying on stock rom+magisk+Xposed though it works great.
Click to expand...
Click to collapse
Thanks for the heads up on the Pixel 2 issues. I will probably stay with stock like on my better half's phone, and just want to root and tether. Now the burn ins, that kind of worries me. Hmmmm... decisons, decision... hehe...
To prevent burn in you can get the magisk module that hides the navbar and toggle that occasionally as that's the only place I really notice it aside from the statusbar which idk a way to hide. I've also heard inverting colours often can help prevent it
KittyRgnarok said:
To prevent burn in you can get the magisk module that hides the navbar and toggle that occasionally as that's the only place I really notice it aside from the statusbar which idk a way to hide. I've also heard inverting colours often can help prevent it
Click to expand...
Click to collapse
Thanks for that information. I did not realize that. And sorry for the delay in responding. I didn't get on xda yesterday as I got back home late last night. I will certainly look for that magisk module you mentioned.
Oh and by the way, I just got me a Google Pixel XL today
Now I need to work the same magic on this one. I've already got it activated at the VZW Store near where I live. *Woohoo*