Related
so i was on cataclysm from the beginning and everything worked great. I flashed stock 4.4.4 cause i want to use just xposed with a nice vanilla rom. everything works great except i cant get or place calls. i have sprint lte full bars, can get data and everything send texts/mms, go on facebook, dl stuff, just no calls. wifi or not doesnt matter either. everytime i try to place one it just sits on dialing and i lose all bars and then says can t make call, no connection. once i hang up the bars and lte come back.
I have noticed my network ends up on global sometimes instead of LTE but even when i switch it to LTE it still doesnt work. i have updated prl and profile too. Any ideas? thanks
EDIT: yeah i still cant seem to fix it. I was going to go back to a 4.4.2 rom but for some reason it fails in twrp everytime now... :/ but this is the exact problem i am having in this thread https://productforums.google.com/forum/#!topic/nexus/Or6_6zCtBwc
seems like it might be sprints fault
Did you wipe?
Sent from my Nexus 5 using Tapatalk
rootSU said:
Did you wipe?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
yep cache, dalvik, data. never had this problem with any other roms before? might it be a 4.4.4 issue? cataclysm was 4.4.2
fergdizzle9090 said:
yep cache, dalvik, data. never had this problem with any other roms before? might it be a 4.4.4 issue? cataclysm was 4.4.2
Click to expand...
Click to collapse
did you update the bootloader and radio?
Zepius said:
did you update the bootloader and radio?
Click to expand...
Click to collapse
no i did not, just twrp. would that be the problem?
possibly. you should do it to be safe.
Zepius said:
possibly. you should do it to be safe.
Click to expand...
Click to collapse
do you have to do it when you upgrade android versions? is there any quick link you can post to help me out with it? im not all that familiar with updating those. Ill search around and see what I can find. thanks for the suggestion though
Im thinking about RMAing my nexus 5 though because the power button is very loose and rattles loudly when i tap the screen, dont want a crappy refurb in place of my mint pristine nexus though :/ lol
Rma is always new
Sent from my Nexus 5 using Tapatalk
rootSU said:
Rma is always new
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
oh i didnt know that. well great thanks. Ill give the updates a shot and consider the rma more now i know ill be getting a new phone. just dont want to be without it for a while lol
yeah i still cant seem to fix it. I was going to go back to a 4.4.2 rom but for some reason it fails in twrp everytime now... :/ but this is the exact problem i am having in this thread https://productforums.google.com/fo...ce=footer#!msg/nexus/Or6_6zCtBwc/j5CP8vy4jGAJ
Install 4.4.4 using fastboot. And after make sure you are using the latest version of twrp.
Lokke9191 said:
Install 4.4.4 using fastboot. And after make sure you are using the latest version of twrp.
Click to expand...
Click to collapse
ill have to look up some stuff on fastboot and recovery updates. been a while since ive done anything out of recovery
fergdizzle9090 said:
ill have to look up some stuff on fastboot and recovery updates. been a while since ive done anything out of recovery
Click to expand...
Click to collapse
Section 3 #1 and Section 4 #1
[Resource] All Guides and Info Threads
Lethargy said:
Section 3 #1 and Section 4 #1
[Resource] All Guides and Info Threads
Click to expand...
Click to collapse
oh yeah ok thanks. so you are suggesting just completely restarting and rerooting from absolute stock?
fergdizzle9090 said:
oh yeah ok thanks. so you are suggesting just completely restarting and rerooting from absolute stock?
Click to expand...
Click to collapse
Personally I would flash the factory images again just to rule out software being the issue, if it still happens then I guess RMA or whatever.
Lethargy said:
Personally I would flash the factory images again just to rule out software being the issue, if it still happens then I guess RMA or whatever.
Click to expand...
Click to collapse
yeah i'll give that a try. weird thing is this happened only after i flashed 4.4.4 from cataclysm 4.4.2. i am waiting to hear if an RMA fixes the issue since someone else is already going that route. it sounds to me like it might be sprint
fergdizzle9090 said:
yeah i'll give that a try. weird thing is this happened only after i flashed 4.4.4 from cataclysm 4.4.2. i am waiting to hear if an RMA fixes the issue since someone else is already going that route. it sounds to me like it might be sprint
Click to expand...
Click to collapse
I doubt it is sprint causing this, or it would be all over these forums. I'd definitely install 4.4.4 via fastboot it'll give you the newest radio and the stock recovery. I'm betting this will fix your issue. Then just use fastboot or flashify to install the newest twrp, and flash su in recovery. If this doesn't fix it, it's a hardware issue.
Lokke9191 said:
I doubt it is sprint causing this, or it would be all over these forums. I'd definitely install 4.4.4 via fastboot it'll give you the newest radio and the stock recovery. I'm betting this will fix your issue. Then just use fastboot or flashify to install the newest twrp, and flash su in recovery. If this doesn't fix it, it's a hardware issue.
Click to expand...
Click to collapse
thanks ill try it out when i got a spare moment. now that im thinking of it this all happened after i updated twrp, so could that be the root of all this you think? because i used the twrp app to update it instead of flashing, and i noticed it has been acting extremely weird lately.
You might check your APN settings. I had issues with MMS after flashing 4.4.4.
hsas.69 said:
You might check your APN settings. I had issues with MMS after flashing 4.4.4.
Click to expand...
Click to collapse
ill look into it. people who have this problem said its not the apn though because i get data just fine and i can recieve calls. its only when i am placing a call it goes crazy and disconnects me
EDIT: so anyone know how to get to apn for sprint? its not under mobile networks. is it buried in a dialer menu or something?...
Lokke9191 said:
I doubt it is sprint causing this, or it would be all over these forums. I'd definitely install 4.4.4 via fastboot it'll give you the newest radio and the stock recovery. I'm betting this will fix your issue. Then just use fastboot or flashify to install the newest twrp, and flash su in recovery. If this doesn't fix it, it's a hardware issue.
Click to expand...
Click to collapse
well full reflash of 4.4.4 stock from google through fastboot didnt work :/ i noticed also that it hasnt been connecting during initial setup, i have to connect to wifi. think my phone might be borked :crying:
Hey!
It's really hard to explain my issue, but I'll try my best.
So here it goes..
My Nexus 5 keeps telling me I have a system update to download and install, so I wait for it to download and then it tells me to install the update from CM-Hammerhead-46e2abd61c to 1f023a4eca-signed.
It shows the Install update option right below, and everything seems fine till now.
When I press this Install update button, it reboots the phone, shows me an android popped open and something indicating that there're being changes which are not shown in normal reboots ofc.
The phone reboots and start, tells me it;s optimizing apps since I use Android Run-time Cache instead of Dalvik.
Now the issue is, it's not updated at all.
It shows me the same Cyan and Android version, 4.4.2 and 46e2abd61c, and when I check for update, it shows me the same thing that I have to update from CM-Hammerhead-46e2abd61c to 1f023a4eca-signed.
I tried this like 10 times and it happens over and over again.
This is bugging me for like a day now.
Any solutions to this?
Thanks.
What recovery are you using?
Sent from my Nexus 5 using Tapatalk
If you're using cwm I don't think it'll work
Lethargy said:
If you're using cwm I don't think it'll work
Click to expand...
Click to collapse
I think it ONLY works with CWM :/
It's that whole, lazy /sdcard/0 thing.
Sent from my Nexus 5 using Tapatalk
rootSU said:
I think it ONLY works with CWM :/
It's that whole, lazy /sdcard/0 thing.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Dunno then, I guess OP can try a different recovery to the one he's using now
Lethargy said:
Dunno then, I guess OP can try a different recovery to the one he's using now
Click to expand...
Click to collapse
Maybe. Thats why I'm trying to find out which one he is using
Sent from my Nexus 5 using Tapatalk
HeyIamSmiley said:
Hey!
The phone reboots and start, tells me it;s optimizing apps since I use Android Run-time Cache instead of Dalvik.
Thanks.
Click to expand...
Click to collapse
Not that it matters, but I'm kind of curious which runtime you're using =P
I'm having the same problem as well.
californiamaki said:
I'm having the same problem as well.
Click to expand...
Click to collapse
Then can you answer my question also please?
Sent from my Nexus 5 using Tapatalk
Try to download the latest update on your PC and flash it on your phone and if that doesn't work change recoveries.
rootSU said:
What recovery are you using?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I'm not even sure, really new to this rooting stuff.
How do I check?
ClockworkMod
rootSU said:
What recovery are you using?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I'm using ClockworkMod.
And if it doesn;t work with Cwm, then what should I do to install that update?
Lethargy said:
If you're using cwm I don't think it'll work
Click to expand...
Click to collapse
Yes, I'm using ClockworkMod, so what do I do now?
rootSU said:
I think it ONLY works with CWM :/
It's that whole, lazy /sdcard/0 thing.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
http://www.cyandelta.com/index2213.html?q=FAQ
HeyIamSmiley said:
Yes, I'm using ClockworkMod, so what do I do now?
Click to expand...
Click to collapse
Try flashing one of these two recoveries with fastboot in bootloader
TWRP: http://techerrata.com/browse/twrp2/hammerhead
PhilZ Touch: http://forum.xda-developers.com/goo...t/hammerhead-philz-touch-6-43-6-f2fs-t2565174
Read a couple threads in the first linked thread of my signature if you're not sure how.
Lethargy said:
http://www.cyandelta.com/index2213.html?q=FAQ
Try flashing one of these two recoveries with fastboot in bootloader
TWRP: http://techerrata.com/browse/twrp2/hammerhead
PhilZ Touch: http://forum.xda-developers.com/goo...t/hammerhead-philz-touch-6-43-6-f2fs-t2565174
Read a couple threads in the first linked thread of my signature if you're not sure how.
Click to expand...
Click to collapse
Guess they've updated it recently then. This certainly was not the case recently, because Phil threads often get asked why it doesn't work and teh answer is the /sdcard/0.
Who knows, Maybe CM finally saw the light, 12 months after everyone else? I wont hold my breath though. Until very recently, it only worked in CWM. It was written that way
rootSU said:
Guess they've updated it recently then. This certainly was not the case recently, because Phil threads often get asked why it doesn't work and teh answer is the /sdcard/0.
Who knows, Maybe CM finally saw the light, 12 months after everyone else? I wont hold my breath though. Until very recently, it only worked in CWM. It was written that way
Click to expand...
Click to collapse
Dunno. Omni says OpenDelta only works with TWRP: http://omnirom.org/general/opendelta-brings-incremental-system-updates-omni/
I've never used Delta since I build my ROMs myself
Edit: CyanDelta seems to be 3rd party, not CyanogenMod's version of OpenDelta. Does the same thing though, I guess using TWRP is most likely to work for this? But you say it only worked in CWM.. so I have no idea lol
Lethargy said:
Dunno. Omni says OpenDelta only works with TWRP: http://omnirom.org/general/opendelta-brings-incremental-system-updates-omni/
I've never used Delta since I build my ROMs myself
Edit: CyanDelta seems to be 3rd party, not CyanogenMod's version of OpenDelta. Does the same thing though, I guess using TWRP is most likely to work for this? But you say it only worked in CWM.. so I have no idea lol
Click to expand...
Click to collapse
The whole thing came about where when 4.2 came out, they moved /sdcard from /data/media/ to /data/media/0. CWM left it as /data/media - which even today, is why you cant see your nandroids taken with CWM in /sdcard
So what the updater app did was put in the updater-script /sdcard/0 as the path, leaving the /data/media mountpoint in CWM in tact... In Philz and TWRP, you would see the error in recovery log (cannot find /sdcard/0/whatever.zip) because on proper recoveries, that is actually /data/media/0/0/whatever.zip).
So Kudos if they changed it to support real recoveries instead of legacy, antiquated CWM builds.
rootSU said:
The whole thing came about where when 4.2 came out, they moved /sdcard from /data/media/ to /data/media/0. CWM left it as /data/media - which even today, is why you cant see your nandroids taken with CWM in /sdcard
So what the updater app did was put in the updater-script /sdcard/0 as the path, leaving the /data/media mountpoint in CWM in tact... In Philz and TWRP, you would see the error in recovery log (cannot find /sdcard/0/whatever.zip) because on proper recoveries, that is actually /data/media/0/0/whatever.zip).
So Kudos if they changed it to support real recoveries instead of legacy, antiquated CWM builds.
Click to expand...
Click to collapse
Yeah, it's probably something related to that.. Several people I know had related issues with certain recoveries and complained about it. Solution was using a different recovery lol
Anyways, if it doesn't work for the OP in one recovery he can try another.
Lethargy said:
Anyways, if it doesn't work for the OP in one recovery he can try another.
Click to expand...
Click to collapse
How many euros will you bet that we never find out the answer?
rootSU said:
How many euros will you bet that we never find out the answer?
Click to expand...
Click to collapse
Euros? Psh :silly:
So I received my One a couple of weeks ago. This week, I received the OTA 38R update. The phone was great for about 6 hours until I was listening to a podcast and it reboots. It goes into the bootloop and so I go to the internet to look for options on how to fix it. I found the instructions for going into fastboot and running the command which is supposed to fix. Unfortunately, I can't get into fastboot on my phone. Also, I haven't replaced the recovery with TWRP. So am I SOL now? Is there anything else I can try?
Thanks!
How are you attempting to get into fastboot mode? Can you get into the stock recovery?
Transmitted via Bacon
I appreciate the reply. I've got it fixed now. I was using the volume up + power. I guess I just wasn't holding it long enough. Once I got it in fast boot, I used a guide from here to replace the recovery with twrp and them, using another guide, I installed The Franco kernel and mahdi ROM on the advice from a friend of mine that's currently at the android BBQ in tx. So it appears to be MUCH more responsive and stable than 38r lol.
Again, thanks for the reply!
Cool, glad you got it sorted.
Transmitted via Bacon
darknephilim said:
I appreciate the reply. I've got it fixed now. I was using the volume up + power. I guess I just wasn't holding it long enough. Once I got it in fast boot, I used a guide from here to replace the recovery with twrp and them, using another guide, I installed The Franco kernel and mahdi ROM on the advice from a friend of mine that's currently at the android BBQ in tx. So it appears to be MUCH more responsive and stable than 38r lol.
Again, thanks for the reply!
Click to expand...
Click to collapse
I am having the bootloop issue too, it does that after the "CM lockscreen has stopped" message. After you replace the recovery with TWRP, did you lose all the files in the internal storage?
Sad to say I did... Luckily pictures were the only thing I cared about and they had been backed up to Google. Good luck!
What guide did you used? All I find require acces to android....
Hi Pawer8. I'll see if I can find it and post it back in here.
Hi pawer8. Here is the thread I used. http://forum.xda-developers.com/showthread.php?t=2879061
You'll have to read through and you may need to make a few jumps based on any prior experience you have with rooting android and the like.
Good luck!
thank you!!!
no root experience though....
It works perfectly. No need to change rom or anything, just do the persist part
I bought a TF700 On amazon as a gift for my son. I want to have this all setup for him by Christmas. I love the one I have with CROMI-X 5.4 on it. Trying to do the same for him. Received it and starting working on it only to find out after starting the process that the bootloader says WW in it . Let me just say this version has been a much larger challenge than the previous one. I can't the the .10 bootloader to take. Tried flashing multiple times no go its stuck at .4 .
Chromi-X says it needs the .8 but seems to be working fine. However I would really like to get this thing updated to the newest one as I know it has several fixes in it. Any ideas ? Not used to the WW version.
Another question is will I have issues with getting US apps in the app store because of the WW designation?
Thanks in advance
DrClaw
Claw22000 said:
I bought a TF700 On amazon as a gift for my son. I want to have this all setup for him by Christmas. I love the one I have with CROMI-X 5.4 on it. Trying to do the same for him. Received it and starting working on it only to find out after starting the process that the bootloader says WW in it . Let me just say this version has been a much larger challenge than the previous one. I can't the the .10 bootloader to take. Tried flashing multiple times no go its stuck at .4 .
Chromi-X says it needs the .8 but seems to be working fine. However I would really like to get this thing updated to the newest one as I know it has several fixes in it. Any ideas ? Not used to the WW version.
Another question is will I have issues with getting US apps in the app store because of the WW designation?
Thanks in advance
DrClaw
Click to expand...
Click to collapse
You could try to do a factory reset and the update it to the latest version. Or Unlock the device and then install the TWRP. When you have the TWRP running, you can install the latest firmware in the TWRP that you want. Goood luck....:fingers-crossed:
LetMeKnow said:
You could try to do a factory reset and the update it to the latest version. Or Unlock the device and then install the TWRP. When you have the TWRP running, you can install the latest firmware in the TWRP that you want. Goood luck....:fingers-crossed:
Click to expand...
Click to collapse
TWRP is installed. Cromi-x 5.4 is installed. Tried the WW TWRP With. 10 in it doesn't take. More suggestions please.
Thanks
DrClaw
Claw22000 said:
TWRP is installed. Cromi-x 5.4 is installed. Tried the WW TWRP With. 10 in it doesn't take. More suggestions please.
Thanks
DrClaw
Click to expand...
Click to collapse
Have you tried install sbdags bootloader zip on the first post of cromi x? What is the error message?
Yes
LetMeKnow said:
Have you tried install sbdags bootloader zip on the first post of cromi x? What is the error message?
Click to expand...
Click to collapse
I have but for some reason it doesn't take. says it completes successfully but nothing changes. I have the newest TWRP. Don't know what more to try.
Thanks for the interest in helping..
Dr Claw
Claw22000 said:
I have but for some reason it doesn't take. says it completes successfully but nothing changes. I have the newest TWRP. Don't know what more to try.
Thanks for the interest in helping..
Dr Claw
Click to expand...
Click to collapse
You seem to know your way around, but I just have to ask: You are checking your BL version in the bootloader menu, right?
You did reboot to system after the bootloader flash? Didn't flash anything else in the same recovery session?
That bL/TWRP package from the CROMi-X OP is still packaged with TWRP 2.6.1. So you should be on the .10 BL with TWRP 2.6.1 if the flash goes through ok.
If it doesn't, download the file again and try with a fresh copy.
The bootloader is universal, the rom (or kernel) is regional AFAIK... If you flash the US edition of CROMi-X you should be ok.
I will do that. Right now is in a gift wrap under the tree. So it will have to wait till after Christmas now. Wife said put it under the tree since it's his only present and he didn't have any yet. Small box he feels cheated compared to his little brother should be neat to see his face when he realizes how wrong he is.
I guess you already flashed the ROM but if not do really think it is necessary to do so for a kid? He probably wouldn't even notice that it's sluggish. There are probably a lot of people out there that are happy with their TF700 the way it comes. People on these XDA forums tend to be more demanding then the average users who may not know or don't care that their tablet doesn't perform as good as others. I would have left it as it was and maybe flash a ROM if he complained about the performance.
Eddie Hicks said:
I guess you already flashed the ROM but if not do really think it is necessary to do so for a kid? He probably wouldn't even notice that it's sluggish. There are probably a lot of people out there that are happy with their TF700 the way it comes. People on these XDA forums tend to be more demanding then the average users who may not know or don't care that their tablet doesn't perform as good as others. I would have left it as it was and maybe flash a ROM if he complained about the performance.
Click to expand...
Click to collapse
Well battery life is better. On those long road trips it will make a difference. With all the bloat gone it runs much nicer and having a launcher overlay like kids place doesn't affect it. After having done the process a few times I didn't think it would take long. It's working fine with .4 and my wife uses it to so she wants it the way it is. So I guess for now I'm done.
DrClaw sent with Tapatalk on my s4
Claw22000 said:
Well battery life is better. On those long road trips it will make a difference. With all the bloat gone it runs much nicer and having a launcher overlay like kids place doesn't affect it. After having done the process a few times I didn't think it would take long. It's working fine with .4 and my wife uses it to so she wants it the way it is. So I guess for now I'm done.
DrClaw sent with Tapatalk on my s4
Click to expand...
Click to collapse
Glad it worked out for you. The Dev's here are very good and the reason I kept my TF700 as long as I did. Longer battery life and getting rid of bloat are very good reasons to flash a ROM. I have a Samsung Tab S now and it's loaded with way more bloat than ASUS.
Eddie Hicks said:
Glad it worked out for you. The Dev's here are very good and the reason I kept my TF700 as long as I did. Longer battery life and getting rid of bloat are very good reasons to flash a ROM. I have a Samsung Tab S now and it's loaded with way more bloat than ASUS.
Click to expand...
Click to collapse
Completely agree. That's funny I got the tab s 10.5 too about a month ago. Did you root and use TiBu?
DrClaw sent with Tapatalk on my s4
Claw22000 said:
Completely agree. That's funny I got the tab s 10.5 too about a month ago. Did you root and use TiBu?
DrClaw sent with Tapatalk on my s4
Click to expand...
Click to collapse
I got my Tab S 10.5 soon after they were first available in July. It's a great tablet. Much better then the ASUS TF201 and TF700 I owned. I did root my Tab S so I could use Titanium Backup and a couple of other apps that require root. I am still on the stock ROM. I'm OK with the stock ROM and Nova launcher.
Has anyone else given it a go on this phone yet? So far I think its working pretty well, with only a couple slowdowns.
Has anyone else noticed a bit of a slowdown with wifi? Sometimes I have to kick it over to LTE to login to apps, even though I can run speed tests and things.
Just wanted to see what other people were experiencing with the beta, sorry if this the wrong place for this.
Other than poor "stand by" battery drainage for me, I think it works pretty good.
But, Android Q it's not on Pixel 3A, isn't it?
Xtremeviper said:
But, Android Q it's not on Pixel 3A, isn't it?
Click to expand...
Click to collapse
Not via OTA, you can pick up the system image from the website and flash it manually though.
As to the OP, I gave it a shot for a couple days but I kept getting a bug where I'd unlock the phone and just get a black screen so I got frustrated and flashed back lol I hope the OTA thats supposedly coming next month fixes it up so it could be a daily driver.
Thanks antp121
I tried to find from official website the Android Q image for Pixel 3A and flash it via sideload or similar.
Can you help me how to do?
Xtremeviper said:
Thanks antp121
I tried to find from official website the Android Q image for Pixel 3A and flash it via sideload or similar.
Can you help me how to do?
Click to expand...
Click to collapse
You know how to use fastboot? I believe the instructions are right on the Google factory image site where you grab the beta 3 image.
Sent from my Pixel 3a using Tapatalk
Thats the point...
I can't found it on Google Factory image, the Beta 3.
Hello,
Do you know if Android Q will brings face unlock ?
Even if it's not safe as the finger print sensor
Xtremeviper said:
Thats the point...
I can't found it on Google Factory image, the Beta 3.
Click to expand...
Click to collapse
Here you go bud. They took it down.
https://mega.nz/#!iWhFXaIL!O0fIHTWivEZR8My9q2C9AtEVO7uxJIPQIf51sKUFrTc
And if you need any instructions:
https://forum.xda-developers.com/pixel-3a/how-to/how-to-install-android-q-beta-3-june-t3930217
jmtjr278 said:
You know how to use fastboot? I believe the instructions are right on the Google factory image site where you grab the beta 3 image.
Sent from my Pixel 3a using Tapatalk
Click to expand...
Click to collapse
crackedvenom2 said:
Here you go bud. They took it down.
https://mega.nz/#!iWhFXaIL!O0fIHTWivEZR8My9q2C9AtEVO7uxJIPQIf51sKUFrTc
And if you need any instructions:
https://forum.xda-developers.com/pixel-3a/how-to/how-to-install-android-q-beta-3-june-t3930217
Click to expand...
Click to collapse
Many Thanks!!! I succeed!
antp121 said:
Not via OTA, you can pick up the system image from the website and flash it manually though.
As to the OP, I gave it a shot for a couple days but I kept getting a bug where I'd unlock the phone and just get a black screen so I got frustrated and flashed back lol I hope the OTA thats supposedly coming next month fixes it up so it could be a daily driver.
Click to expand...
Click to collapse
I've actually been getting the same thing. I also keep having an issue with wifi, I think I'm going go back to pie and see if it's still doing it. I just really like the new gestures and don't wanna give them up lol
I've been running it for a few weeks. Side loaded the OTA as soon as I got the phone. They took down the OTA file but it's posted in this thread. I've had no issues other than a few apps not being comparable yet and there is no working Magisk out for Pixels 3/3a with Q beta.
When i factory reset my phone, will i still be on the beta? Im currently enrolled on beta 4 and want zo stay on it, but need to re setup the phone again.
Thanks!
bejunk said:
When i factory reset my phone, will i still be on the beta? Im currently enrolled on beta 4 and want zo stay on it, but need to re setup the phone again.
Thanks!
Click to expand...
Click to collapse
Yes
sd_N said:
Yes
Click to expand...
Click to collapse
bejunk said:
When i factory reset my phone, will i still be on the beta? Im currently enrolled on beta 4 and want zo stay on it, but need to re setup the phone again.
Thanks!
Click to expand...
Click to collapse
On a related note, does anyone know if opting out of the Beta will delete any esim profiles?
Axe_L_Thief said:
On a related note, does anyone know if opting out of the Beta will delete any esim profiles?
Click to expand...
Click to collapse
Simply "opting out" of the beta by pressing the button on the web page will not change anything. But as soon as you (download and) install Pie, my guess is that it will erase everything including any esim profiles. When you go from one major release to another - especially a downgrade - the phone is typically going to be wiped completely. It purposefully erases all information to ensure there isn't any conflicts between the two OS versions.
Just enrolled in the beta myself, does anyone know if it is being pushed OTA yet?
Sent from my Pixel 3a using Tapatalk
upinsmoke7610 said:
Just enrolled in the beta myself, does anyone know if it is being pushed OTA yet?
Click to expand...
Click to collapse
DP4 was pulled iirc. You can still sideload it.
Anybody having any issues with it so far?
Sent from my Pixel 3a using Tapatalk
So far I'm having no issues with the beta, but did anyone else get a small update today? Any idea why?