Hi to all, until December update VPN on my P7P is fylly working. After January update it hasn't worked anymore. Today i have updated to February patch, the result is the same. Anyone have the same problem? Any solutions? Thanks in advance.
We all have this problem, Im pretty sure it is Google Server side.
schmeggy929 said:
We all have this problem, Im pretty sure it is Google Server side.
Click to expand...
Click to collapse
so any fix for the moment?
franco985 said:
so any fix for the moment?
Click to expand...
Click to collapse
No, not unless you can change Google's server config
franco985 said:
so any fix for the moment?
Click to expand...
Click to collapse
See this thread - clearing data for Google One app seems to temporarily fix it for some folks, but it stops working again soon after.
google can detect if you are rooted and have a unlocked bootloader, the vpn will only work with a locked bootloader on stock. it didnt work when i was on a custom rom or rooted on stock. hope that helps this is only my opinion tho from my own research.
funkybear34 said:
google can detect if you are rooted and have a unlocked bootloader, the vpn will only work with a locked bootloader on stock. it didnt work when i was on a custom rom or rooted on stock. hope that helps this is only my opinion tho from my own research.
Click to expand...
Click to collapse
While it may be true that they can detect a unlocked bootloader and a rooted device. They are Google! As they can probably detect pretty much anything and everything you do on a "Google device". Even while using a Google VPN to block it lol. For now though, they do allow us and tell you exactly how to unlock the bootloader and very easily I might add "Thankfully" and they don't punish you for it. Yey. I've heard it was a Google 1 issue and not an end user issue. VPN worked perfectly fine for me on the November and December firmware builds while being on stock, unlocked bootloader, rooted and running Kiri kernel and I used it quite frequently. Once I updated to the January build it quit working and I was hopeful that the February build fixed it. Still we all face the same "VPN is disabled" problem. I did just send a help ticket to Google 1 about the VPN not working issue. Curious as to what they have to say about it, not working for us Pixel users in the last 2 builds. I'll post their reply when I get one back.
Related
Bought my GS4 yesturday, this morning around 10am i got an OTA that was about 28mb. Not sure what that OTA did because i cant find any change log anywhere or anybody else talking about it...does anybody know anything?
Build Number is JDQ39.I337MVLUAMDL
On Rogers in Canada
You should probably have put down Rogers on the thread title. I didn't receive anything but I am no AT&T. But one more thing, I was talking in this other thread with the Canadian carrier guys. Is your Contacts and phone app white or black / blue?
Even though I'm on AT&T, I am happy for Rogers customers. Can anyone elaborate on what this update does? Hopefully it addresses the lag?
On US AT&T and no OTA. I wouldn't download any OTA's though just in-case they address the hacked bootloader.
@geoldr: The OTA was launched by Samsung globally.
Good to see you again P-Pat! I got the notification, but rooted before installing in case there was patch to stop root. After I tried to install and it said my phone has been modified and updates are not available. I am now searching to figure out how to install this....
For news on the update, see here: http://gadgets.ndtv.com/mobiles/news/samsung-galaxy-s4-receives-first-software-update-362298
David Dee said:
@geoldr: The OTA was launched by Samsung globally.
Good to see you again P-Pat! I got the notification, but rooted before installing in case there was patch to stop root. After I tried to install and it said my phone has been modified and updates are not available. I am now searching to figure out how to install this....
For news on the update, see here: http://gadgets.ndtv.com/mobiles/news/samsung-galaxy-s4-receives-first-software-update-362298
Click to expand...
Click to collapse
I'm a bit confused at this. Even if Samsung releases an update, we won't get it instantly because the carriers have to test it out and everything right? Hasn't this always been the case or am I missing something?
geoldr said:
I'm a bit confused at this. Even if Samsung releases an update, we won't get it instantly because the carriers have to test it out and everything right? Hasn't this always been the case or am I missing something?
Click to expand...
Click to collapse
From what I have read, so far it has been launched on Sprint, Rogers and the international version. I am sure AT&T will come soon. Samsung launches the updates, but the carriers distribute them...that is why Android version updates have different timing for different carriers.
David Dee said:
From what I have read, so far it has been launched on Sprint, Rogers and the international version. I am sure AT&T will come soon. Samsung launches the updates, but the carriers distribute them...that is why Android version updates have different timing for different carriers.
Click to expand...
Click to collapse
I see. Now just to find out what this update does.
For now I will be staying away from it. I don't want anything locking up the chance of unlocking the bootloader.
geoldr said:
I see. Now just to find out what this update does.
For now I will be staying away from it. I don't want anything locking up the chance of unlocking the bootloader.
Click to expand...
Click to collapse
This! I just rooted my phone this morning finally and froze the AT&T Software Update and FWUpdater. Should protect me from the OTA when it comes over to AT&T correct?
Thermalwolf said:
This! I just rooted my phone this morning finally and froze the AT&T Software Update and FWUpdater. Should protect me from the OTA when it comes over to AT&T correct?
Click to expand...
Click to collapse
Yeah. I dont think the firmware installs without the user accepting it anyways.
geoldr said:
Yeah. I dont think the firmware installs without the user accepting it anyways.
Click to expand...
Click to collapse
Somewhere I read they can force push security updates onto the phone without you even having to accept it. This is something I think they would do over the bootloader to prevent people from stopping the patch.
Thermalwolf said:
This! I just rooted my phone this morning finally and froze the AT&T Software Update and FWUpdater. Should protect me from the OTA when it comes over to AT&T correct?
Click to expand...
Click to collapse
It will save you from an annoying notification, but you have to click to initiate the install. Also, if you are are rooted, the ota won't work. You are safe.
Thermalwolf said:
Somewhere I read they can force push security updates onto the phone without you even having to accept it. This is something I think they would do over the bootloader to prevent people from stopping the patch.
Click to expand...
Click to collapse
Really? Well in that case I need to root and block those services. I've been waiting for an unlock and then was gonna root it.
David Dee said:
It will save you from an annoying notification, but you have to click to initiate the install. Also, if you are are rooted, the ota won't work. You are safe.
Click to expand...
Click to collapse
I figured with this method of root it wouldn't effect the update since we weren't messing with the firmware.
Thermalwolf said:
I figured with this method of root it wouldn't effect the update since we weren't messing with the firmware.
Click to expand...
Click to collapse
This is Sammy's doing, seems like they are taking a harder line this time around. I used the exact same method on my TF300 and OTAs work like a charm.
geoldr said:
You should probably have put down Rogers on the thread title. I didn't receive anything but I am no AT&T. But one more thing, I was talking in this other thread with the Canadian carrier guys. Is your Contacts and phone app white or black / blue?
Click to expand...
Click to collapse
its black blue
David Dee said:
@geoldr: The OTA was launched by Samsung globally.
Good to see you again P-Pat! I got the notification, but rooted before installing in case there was patch to stop root. After I tried to install and it said my phone has been modified and updates are not available. I am now searching to figure out how to install this....
For news on the update, see here: http://gadgets.ndtv.com/mobiles/news/samsung-galaxy-s4-receives-first-software-update-362298
Click to expand...
Click to collapse
Thanks Bud!! Nice to see you too. On the screenshot you posted, it doesnt match up to mine. It was 28mb and it didnt have any mention of ''improved stability''. Im really wondering what that was, maybe the canadien version of that european release. Also the build number doesnt match up
geoldr said:
I'm a bit confused at this. Even if Samsung releases an update, we won't get it instantly because the carriers have to test it out and everything right? Hasn't this always been the case or am I missing something?
Click to expand...
Click to collapse
not always, i received 2 updates on the GS3 that were released from sammy and did not go through carrier testing, unless they did it so uniformly that it didnt seem like it, but then again, telus and bell got it the same day rogers did, but those updates were stability and securtiy related, they didnt bring any features, so i guess it really depends on what the updates changes
This link confirms what David Dee was saying, it also matches my build number and size of update
http://www.androidpolice.com/2013/0...iving-its-first-ota-update-build-l720vpuamdl/
I wouldnt worry too much about OTAs anymore since AdamOutler has an Odin flashable current firmware up in the dev forums.
polish_pat said:
its black blue
Click to expand...
Click to collapse
Now see thats weird. AT&T version everything is white. Messaging app is white dialer is white contacts are white.
I wonder why...
David Dee said:
This is Sammy's doing, seems like they are taking a harder line this time around. I used the exact same method on my TF300 and OTAs work like a charm.
Click to expand...
Click to collapse
So what you're saying is I can still install OTA's if I rooted with motochopper? But as long as I have the ota update files frozen I shouldn't have to worry?
Thermalwolf said:
So what you're saying is I can still install OTA's if I rooted with motochopper? But as long as I have the ota update files frozen I shouldn't have to worry?
Click to expand...
Click to collapse
No, once rooted the otas will not work because it detects device modification.
Heres the issue. I am no noob at this whatsoever and have tried EVERYTHING. I have used every program I could find to attempt root and none can seem to gain root access. The install SuperUser or SuperSU and every time root fails even if said app is installed. Please help Im doing a talk on August 20th that I NEED this device for. All help appreciated. Thanks!
Im slightly confused as your sig says rooted stock
But anyway I recently got myself a Razr HD and I used http://forum.xda-developers.com/showthread.php?t=2241788 to root and unlock bootloader
My device was 4.1.2 and I did not want to downgrade but this one worked :victory:
More info needed. Is your bootloader unlocked? If not, which firmware are you on?
killrhythm09 said:
More info needed. Is your bootloader unlocked? If not, which firmware are you on?
Click to expand...
Click to collapse
Nothings been modified. Plus I hope you know that to unlock the bootloader it requires root
dr_strangetrick said:
Im slightly confused as your sig says rooted stock
But anyway I recently got myself a Razr HD and I used http://forum.xda-developers.com/showthread.php?t=2241788 to root and unlock bootloader
My device was 4.1.2 and I did not want to downgrade but this one worked :victory:
Click to expand...
Click to collapse
Thank you, I think I may have worked out my issue! I was using 1.2 of that program. I think thats why. Let me give this a go
Tried again with this guy and still got failure. I always get this:
[*]This May Take A Few Minutes
[-]Failure
Ok well what do you know. 3rd times the charm eh? I tried a third time this time after reflashing stock firmware, antennas, etc... Thanks!
Well done and welcome to the club
dr_strangetrick said:
Well done and welcome to the club
Click to expand...
Click to collapse
Thanks haha xD Coming from a Galaxy Nexus GSM Dev Edition, this is oddly restraining. There seem to be only a few ROMs available for this device.
Quality is better than quantity
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
Am i not getting OTA of 6.0 cause my bootloader is unlocked or is 6.0 not out yet for OTA? I know the images are i just want the OTA and ill wait for it or is unlocked BL keeping me from getting the OTA?
cell2011 said:
Am i not getting OTA of 6.0 cause my bootloader is unlocked or is 6.0 not out yet for OTA? I know the images are i just want the OTA and ill wait for it or is unlocked BL keeping me from getting the OTA?
Click to expand...
Click to collapse
No, it's not because the bootloader is unlocked.OTA are sent in "waves" so the servers won't get overwhelmed.So it's just a matter of time until you will gey it too.
Pretoriano80 said:
No, it's not because the bootloader is unlocked.OTA are sent in "waves" so the servers won't get overwhelmed.So it's just a matter of time until you will gey it too.
Click to expand...
Click to collapse
Great ty what if phone was rooted would that stop OTA`s? Just curious im not rooted. Is the OTA suppose to be released with Gapps included do you know? There are an awful lot of people not being able to recieve gapps the right way. I hear location doesnt work and some other stuff but maybe thats a handful of people
I don't think the root prevent a device receiving the OTA,but it might cause the OTA installation to fail,so it's always best to disable root before updating.
I didn't used the OTA to update my device,so I can't say if there's any issue with it,but I know people that updated via OTA and it was all fine.
I have a rooted device with twrp recovery. Despite of what people think, I get this update. I just replace twrp recovery to stock and flash . This is amaze me. In general, my location also doesn't work also. There is solution?
The Joke(r) said:
I have a rooted device with twrp recovery. Despite of what people think, I get this update. I just replace twrp recovery to stock and flash . This is amaze me. In general, my location also doesn't work also. There is solution?
Click to expand...
Click to collapse
That seems to be a major bug there are so many talking about location not working or its in another place in settings. Not sure where cause i dont have my phone right now. Im sure there will be a workaround soon
Sent from my Pixel using XDA Free mobile app
Has any on with A VZW PIXEL with an unlocked bootloader taken the NOVEMBER UPDATE AND if so what was the result????
Sent from my Unlocked Pixel
key Hole said:
Has any on with A VZW PIXEL with an unlocked bootloader taken the NOVEMBER UPDATE AND if so what was the result????
Sent from my Unlocked Pixel
Click to expand...
Click to collapse
That's a good question. I unlocked my bootloader and immediately disabled automatic system updates. Really curious if anyone has tried it. I know there are supposedly issues if you unlock then try to run custom firmware and then relock the bootloader (don't know why one would do that, but to each their own). I'm sure someone will tell us soon.
In the November update discussion on the XL forum, dePixel8 is reported to still work. They're expecting the next update will stop it from working.
http://forum.xda-developers.com/showpost.php?p=69513504&postcount=182
Just completed the November update with no adverse effects... Way cool
Sent from my Pixel using XDA Free mobile app
Sent from my Still unlocked Pixel
It's time to look at ROOT
Been reading all the threads here about this before I install the update.
I know this is a repeat, but I figured I might save some people the time digging.
My Device: Pixel XL Verizon NDE63P , Unlocked Bootloader, Root SU 2.78 SR3, ElementalX 0.05, WETA Battery, Center Clock, NavBar Height 36px
My Findings: Things should be fine. WETA just verified in a reply to me that the mods still work.
Update: Kernel update went fine kept root too.
Working on Installing the OTA now. I might make a guide for this if I don't get to frustrated. Right now its almost winning.
Feel free to PM me for help or directions. If there is interest I will write it all up. I just feel like maybe I'm the n00b here and everyone else is better than me. Been out of android for about 2 years...
jp712 said:
Been reading all the threads here about this before I install the update.
I know this is a repeat, but I figured I might save some people the time digging.
My Device: Pixel XL Verizon NDE63P , Unlocked Bootloader, Root SU 2.78 SR3, ElementalX 0.05, WETA Battery, Center Clock, NavBar Height 36px
My Findings: Things should be fine. WETA just verified in a reply to me that the mods still work.
Update: Kernel update went fine kept root too.
Working on Installing the OTA now. I might make a guide for this if I don't get to frustrated. Right now its almost winning.
Feel free to PM me for help or directions. If there is interest I will write it all up. I just feel like maybe I'm the n00b here and everyone else is better than me. Been out of android for about 2 years...
Click to expand...
Click to collapse
I'd be interested in a write up if you have time. Or even just a PM would be greatly appreciated. I tried sending a PM but apparently it's not going through. I'm currently unlocked and rooted using the same methods as you and also running EX-P-0.07 kernel. I currently have the OTA zip downloaded and ready to side load. Just wondering if I can just side load it normally without doing anything else. Or should I sideload, then install EX-P-0.07 kernel, then boot to root again? Thanks in advance.
Alphonse
I too would be interested in written out directions just to verify what I think I know because I'm not always right
key Hole said:
I too would be interested in written out directions just to verify what I think I know because I'm not always right
Click to expand...
Click to collapse
+1
ihierbal said:
I'd be interested in a write up if you have time. Or even just a PM would be greatly appreciated. I tried sending a PM but apparently it's not going through. I'm currently unlocked and rooted using the same methods as you and also running EX-P-0.07 kernel. I currently have the OTA zip downloaded and ready to side load. Just wondering if I can just side load it normally without doing anything else. Or should I sideload, then install EX-P-0.07 kernel, then boot to root again? Thanks in advance.
Alphonse
Click to expand...
Click to collapse
You will have to reinstall the kernel after the OTA runs. I shut down after the OTA finished instead of booting and then installed the kernel and root again. I also had to add the weta mods again too.
I made notes for a write-up as I did it. I can send them to you when I get home later this evening.
If you could send me a copy of that also I would greatly appreciate it.
key Hole said:
If you could send me a copy of that also I would greatly appreciate it.
Click to expand...
Click to collapse
I ended up just winging it and was able to sideload, install custom kernel, and root with no problems. Let me know if you still need a simple write up.