Related
Hello,
I need a bit of help with my nexus s. I was trying to install ICS on it the other day and something went wrong so it is now stuck at the google logo with the unlocked padlock underneath. I would just go into recovery mode but the power button is broken, now i can get into fastboot mode but for some reason i cant do anything in it for example the volume buttons dont move the selection up or down and obviously i cant select anything because the power button doesn't work. If anyone could help me out with this I would greatly appreciate it!
Thanks,
Alex
Well you cant get into recovery except from the boot loader I think
If you can somehow manage to get the power button working even once, you should be able to fix your phone by flashing a new ROM, for ICS I first installed GB 2.3.6 and then went into the stock recovery mode, held power + volume up and selected the ICS update zip file, which I had renamed to update.zip
I hope that will help you if you manage to get into recovery, maybe send it to the company, or try pressing the button somehow I dunno, sorry :S
Sent from my Nexus S using XDA App
You can also try flashing a ICS compatible kernel using fastboot, that is if the kernel is responsible for you being stuck...
Sent from my Nexus S using XDA App
I havn't had much personal experience, though you might be able to find some information searching around for flashing a rom via adb, or something of the sort.
been there before
what i did is, flash a Custom ROM like MIUI 2.3.7 then flash stock 2.3.6 and then flash ICS stock 4.0.3
I think this app will help you:
http://www.mediafire.com/?2jx8xtx2602hi23
extract it and click bat.run
if your phone is at the 'google' kernel splash screen, it should auto-boot the phone into bootloader, if I remember correctly, and if you use command line adb to boot into recovery you should be able to use the capacitive buttons to navigate & select so you can get a rom installed. back=back, home=up, menu=down, search=select
Hey guys
i just wiped all my data and tried to reboot my nexus, but now it's been stuck on the google logo for ages...
trying to flash to stock + unroot with nexus toolkit doesn't work, any way to unbrick it?
please help...
do you have fastboot driver installed?
Step 1: Power down your Nexus 4 (hold the power button until it shuts off) before rebooting into fastboot mode. You can do this by holding down the the Volume Down and Power buttons simultaneously.
Step 2: Connect your device to your computer. Open up a terminal or command prompt, and navigate to the folder containing the fastboot program.
Step 3: Type fastboot devices into the command line, and you should then see your device’s ID, which means fastboot is setup correctly.
now go back to Nexus 4 toolkit. Flash back to stock.
badboy47 said:
do you have fastboot driver installed?
Step 1: Power down your Nexus 4 (hold the power button until it shuts off) before rebooting into fastboot mode. You can do this by holding down the the Volume Down and Power buttons simultaneously.
Step 2: Connect your device to your computer. Open up a terminal or command prompt, and navigate to the folder containing the fastboot program.
Step 3: Type fastboot devices into the command line, and you should then see your device’s ID, which means fastboot is setup correctly.
now go back to Nexus 4 toolkit. Flash back to stock.
Click to expand...
Click to collapse
works
thank you very much
fabian.m said:
works
thank you very much
Click to expand...
Click to collapse
Then, press on his THANKS button. That's the way we have to measure who contributes or not in xda-developers. Please, let's follow rules...
luiseteyo said:
Then, press on his THANKS button. That's the way we have to measure who contributes or not in xda-developers. Please, let's follow rules...
Click to expand...
Click to collapse
well.. technically thanking isn't in the rules.
exb0 said:
well.. technically thanking isn't in the rules.
Click to expand...
Click to collapse
It is in the good behaviour and politeness rules. Not everything is written.
Hi guys i got a similar problem, i flashed a walkman .zip wiped cache and dalvik cache. Then the phone booted into google logo, and it went all black. The display is on but its all black. The problem is i cannot power off the device. Holding all buttons just restarts the phone. What can i do?
I was on latest PA rom
Qbsti said:
Hi guys i got a similar problem, i flashed a walkman .zip wiped cache and dalvik cache. Then the phone booted into google logo, and it went all black. The display is on but its all black. The problem is i cannot power off the device. Holding all buttons just restarts the phone. What can i do?
I was on latest PA rom
Click to expand...
Click to collapse
reflash your rom. reboot your device, hold volune down before it reboots to get into the bootloader then recovery.
simms22 said:
reflash your rom. reboot your device, hold volune down before it reboots to get into the bootloader then recovery.
Click to expand...
Click to collapse
Thanks simms, i managed to get into fast boot between the reboots, and I flashed the rom and gapps.
Damn it scared me even more then the red light issue that happened to me last month.
Qbsti said:
Thanks simms, i managed to get into fast boot between the reboots, and I flashed the rom and gapps.
Damn it scared me even more then the red light issue that happened to me last month.
Click to expand...
Click to collapse
not booting after flashing something or modding something is the easiest of all to fix, just reflash the rom(gapps and kernel too if need be), no need to wipe anything. since i test all the trinity kernels before any get released, and pre-kernels, i get many that dont boot my device or bootloop(among some other funky behaviors), reflashing a good kernel always works
I left my phone for a few minutes, and when I picked it up it was bootlooped again, and i had to use fastboot again. What should I do now? Maybe a factory reset would help me. I don't want more unexpected bootloops. :/
swyped from my nexus 4
Qbsti said:
I left my phone for a few minutes, and when I picked it up it was bootlooped again, and i had to use fastboot again. What should I do now? Maybe a factory reset would help me. I don't want more unexpected bootloops. :/
swyped from my nexus 4
Click to expand...
Click to collapse
Try another rom. You might have downloaded corrupted zips. Also, make sure you flash the things you need first. Eg, flash rom and gapps. Don't restore anything if you're using titanium backup. Try restarting the phone, see if it gets into a bootloop. If it doesn't, then try restoring apps from TB. (if you use TB.)
Hi!
I´ve got a big problem. Today i flashed the new PA version, but it seems that the download had some issue. I could install it but after a while, I wanted to reboot the phone and it got stuck at the Google logo. I can only access fastboot mode and recovery.
So the problem is, i made a full wipe, so i have no rom on the sdcard anymore. Also I am now able to enable the debbuging mode. I tried every toolkit i couzld find, but everyone needs debugging mode enabled. windows doesnt recognize the phone ( it says unkown device). So i tried to install the adb drivers, but nothing happens.
i wanted to try to push a rom with adb on the phone but it says no device found. i am such a noob, i hope some can help me.
thx
Hello, I tried searching for this but came up empty. I have a completely stock Nexus 4, received the OTA push for 4.3. Phone has never been rooted. After going through the install process it showed the android on it's back with a red triangle and said error. After a restart the phone just sits at the Google screen!!! I'm I boned or is there a fix for this? Any info would be greatly appreciated! Thank you!
Jesmuris said:
Hello, I tried searching for this but came up empty. I have a completely stock Nexus 4, received the OTA push for 4.3. Phone has never been rooted. After going through the install process it showed the android on it's back with a red triangle and said error. After a restart the phone just sits at the Google screen!!! I'm I boned or is there a fix for this? Any info would be greatly appreciated! Thank you!
Click to expand...
Click to collapse
Try going into fastboot and flashing the stock rom from google.
gmaxpwnage said:
Try going into fastboot and flashing the stock rom from google.
Click to expand...
Click to collapse
Not sure what mode I entered, Held vlm down + power. Says Fastboot Mode in red with a big green Start at the top. Options it gives me is Start, restart bootloader, recovery mode, and power off. If I try to enter Recovery mode it says no command. Don't see anything that allows me to reinstall
Jesmuris said:
Not sure what mode I entered, Held vlm down + power. Says Fastboot Mode in red with a big green Start at the top. Options it gives me is Start, restart bootloader, recovery mode, and power off. If I try to enter Recovery mode it says no command. Don't see anything that allows me to reinstall
Click to expand...
Click to collapse
Ok, found out on the no command screen I can hold power and hit vlm up and it brings me to system recovery with these options. Reboot system, apply update from ADB, wipe data/factory reset, wipe cache partition.
Not sure what to do sadly
Try following step:
1. Press Vol up and down and powerbutton same time to get to the fastboot mode as you mention.
2. Choice Recovery Mode and press power button. If you got luck you will see an android guy with red mark on the screen.
3. Press Vol Up and Power button same time for while don't let go it will pop up a list of option clean the cache and do factory reset, then reboot system.
If this method not working. Then hard method is flash your Nexus 4 with fastboot. Search the forum there few people already post how to flash 4.3 ROM with fastboot
Johnsonyc said:
Try following step:
1. Press Vol up and down and powerbutton same time to get to the fastboot mode as you mention.
2. Choice Recovery Mode and press power button. If you got luck you will see an android guy with red mark on the screen.
3. Press Vol Up and Power button same time for while don't let go it will pop up a list of option clean the cache and do factory reset, then reboot system.
If this method not working. Then hard method is flash your Nexus 4 with fastboot. Search the forum there few people already post how to flash 4.3 ROM with fastboot
Click to expand...
Click to collapse
Ok thank you, trying this now will update:good:
Didn't work Will try other method
Jesmuris said:
Didn't work Will try other method
Click to expand...
Click to collapse
Sorry to hear this bad news Hope the other method work for you!
Well, first try, couldn't get my PC to recognize fastboot in adb. Was getting frustrated beyond hell and had to walk away for a bit. Came back about an hour later and for some reason it finally recognized it... Back to the start screen like when I first bought the phone. So far working ok, except for being able to log into my google account... 2-step verification giving me issues now lol. Thank you again for your assistance. Very much appreciated!!:good::good:
Jesmuris said:
Well, first try, couldn't get my PC to recognize fastboot in adb. Was getting frustrated beyond hell and had to walk away for a bit. Came back about an hour later and for some reason it finally recognized it... Back to the start screen like when I first bought the phone. So far working ok, except for being able to log into my google account... 2-step verification giving me issues now lol. Thank you again for your assistance. Very much appreciated!!:good::good:
Click to expand...
Click to collapse
I had a similar experience (kind of). I had issues side-loading 4.2.2 -> 4.3 on my N4. After it finished update and rebooted I got a black screen and nothing more. I ran through it and tried to update to 4.3 again, and then it worked.
Even though it worked I've been noticing issues with it. For example, I now can no longer uninstall anything. When I attempt to uninstall any app, the phone reboots. I'm backing up now with Titanium and am about to flash. I was hoping there would be a quick fix here, but such is life. Viva la impatience.
I have same problem my stock 4.2.2 stuck x boot load , did vol up+dwn +power now stuck in "Download Mode" do not unplug the device until the process is complete .
oneguy77 said:
I have same problem my stock 4.2.2 stuck x boot load , did vol up+dwn +power now stuck in "Download Mode" do not unplug the device until the process is complete .
Click to expand...
Click to collapse
This is what I eventually followed to get mine working. I just did scenario 2 and that worked perfectly for me, so far no issues, just having to get things back to where I had them before. The second link is actually more detailed. Just make sure you follow step by step. I guess i could have not done step D10 but wanted to make sure this route worked for me. Thank you again for those who pointed me in the right direction
http://www.androidpolice.com/2013/0...-to-android-4-3-jwr66v-and-root-it-right-now/
http://forum.xda-developers.com/showpost.php?p=34552123&postcount=1
Jesmuris said:
Well, first try, couldn't get my PC to recognize fastboot in adb. Was getting frustrated beyond hell and had to walk away for a bit. Came back about an hour later and for some reason it finally recognized it... Back to the start screen like when I first bought the phone. So far working ok, except for being able to log into my google account... 2-step verification giving me issues now lol. Thank you again for your assistance. Very much appreciated!!:good::good:
Click to expand...
Click to collapse
I have the exact same problem but not sure how to get my PC to recognize fastboot in adb mode...
FYI if you flash to stock android 4.3 and you have the 16 GB Nexus 4, make sure that after you re-flash you have the full 16 GB and not 8 GB (unless you want to re-setup your phone twice like me). If you get this problem you can wipe cache and data from recovery and voila, all of your free space is back.
---------- Post added at 10:52 PM ---------- Previous post was at 10:44 PM ----------
zpilot said:
I have the exact same problem but not sure how to get my PC to recognize fastboot in adb mode...
Click to expand...
Click to collapse
If this is what I think it is, I was having the same problem. If I went into Control Panel on my PC and it would say that the driver is failing to load. To fix this I uninstalled the driver, rebooted, reinstalled Google USB Driver from the Android SDK Manager, restarted, and all was well after that.
I really have no explanation for why this fixed it, or it didn't work before, because other than fastboot, everything was working flawlessly with getting my phone to communicate with my PC.
Hey all, completely new to this forum and my Oneplus Two that I've had for a little over two weeks.
I recently got a OTA update for Oxygen 2.2.0 but I can't seem to install it. Everytime I download it and click the "install" option, the phone reboots (probably to go to recovery) but after a very brief splash screen and a vibration, it vibrates again and displays the standard boot splash screen, boots into the OS and offers me to download the update again.
I've done a little troubleshooting in the past two-three days and from what I understand, the phone doesn't seem to be able to boot into recovery or fastboot. I've enabled the advanced options in the "reboot" menu and when selecting "recovery" the phone reboots and does the same behavior described above. I tried powering off the phone and booting with the volume up button pressed (while pressing power) and the phone boots and displays a "Fastboot Mode" splash screen but it seems to hang there forever until I actually shut it off again and power it back on. Also, I've tried booting it into recovery from ADB, connected to my PC and I get the same behavior: brief splash screen with a vibrate and then the phone seems to reboot again normally.
I haven't tampered with the phone yet, it is brand new out of the box, not rooted and nothing other than simply installing a few games, Nova Launcher, changing the wallpaper and using it as you would normally use your phone.
Anyone has an idea how I could actually get the Recovery functioning on this phone?
Best regards and thanks in advance for any help!
redbay1 said:
Hey all, completely new to this forum and my Oneplus Two that I've had for a little over two weeks.
I recently got a OTA update for Oxygen 2.2.0 but I can't seem to install it. Everytime I download it and click the "install" option, the phone reboots (probably to go to recovery) but after a very brief splash screen and a vibration, it vibrates again and displays the standard boot splash screen, boots into the OS and offers me to download the update again.
I've done a little troubleshooting in the past two-three days and from what I understand, the phone doesn't seem to be able to boot into recovery or fastboot. I've enabled the advanced options in the "reboot" menu and when selecting "recovery" the phone reboots and does the same behavior described above. I tried powering off the phone and booting with the volume up button pressed (while pressing power) and the phone boots and displays a "Fastboot Mode" splash screen but it seems to hang there forever until I actually shut it off again and power it back on. Also, I've tried booting it into recovery from ADB, connected to my PC and I get the same behavior: brief splash screen with a vibrate and then the phone seems to reboot again normally.
I haven't tampered with the phone yet, it is brand new out of the box, not rooted and nothing other than simply installing a few games, Nova Launcher, changing the wallpaper and using it as you would normally use your phone.
Anyone has an idea how I could actually get the Recovery functioning on this phone?
Best regards and thanks in advance for any help!
Click to expand...
Click to collapse
That is the norm for fastboot, it doesn't go past that screen.
It may not make a difference, did you try to boot to recovery via Power+Volume Down buttons?
Greetings Khaos64,
Yes, I've tried booting with Vol-Down+Power but the phone does not start.
With volume-up+power, I get the Fastboot splash screen but the phone does not respond to any input.
I tried selecting "bootloader" from the reboot menu but I get the same thing: Reboots and after a second, the phone reboots again normaly and into OxygenOS.
Is there a way to verify if the bootloader or recovery is corrupt and maybe reflash the stock recovery onto the phone?
Thanks for your input!
You may just want to go straight to oneplus support since everything is stock and only 2 weeks they should be able to get you updated or replace it.
If you'd like to be more hands on... maybe something below can help.
So your phone isn't recognized/no commands acceptred from your computer when booted to fastboot?
Such as unlocking your bootloader and booting into twrp... "fastboot boot yourfilename.img" or maybe flashing it.
Make sure OEM unlocking is selected in Developer options.
If you can't do that then this may not work but is worth a shot.
http://forum.xda-developers.com/showpost.php?p=62973446&postcount=2
These may also be something to look into:
http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449
I did try to contact Oneplus for support but I am not the one who purchased the phone. Long story short, it was a gift from my girlfriend that she bought off of someone. The phone was new in box and was a warranty replacement. I would have to contact the seller and go trough him for support unfortunately.
Thanks for the different suggestions!, I will fiddle around with it this afternoon while the kids are having their mid-day nap and I'll get back with the results
Thanks again for the help, it's greatly appreciated!
Hello,
I eventually started fiddling around with fasboot and tried unlocking the bootloader. This sent the phone into a bootloop where it would try to boot into recovery and reboot right away.
I found an article on how to restore the phone to Oxygen 2.1.1. It would wipe user data but I did it anyway and it actually did restore the phone and now I have a worling recovery.
Here is a link to the guide I used:
http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
Thanks again for the help in solving my issue
Congratulations hope you enjoy the phone
Sent from my ONE A2005 using Tapatalk
redbay1 said:
Hello,
I eventually started fiddling around with fasboot and tried unlocking the bootloader. This sent the phone into a bootloop where it would try to boot into recovery and reboot right away.
I found an article on how to restore the phone to Oxygen 2.1.1. It would wipe user data but I did it anyway and it actually did restore the phone and now I have a worling recovery.
Here is a link to the guide I used:
http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
Thanks again for the help in solving my issue
Click to expand...
Click to collapse
Glad one was able to help you do it. :good:
redbay1 said:
Hello,
I eventually started fiddling around with fasboot and tried unlocking the bootloader. This sent the phone into a bootloop where it would try to boot into recovery and reboot right away.
I found an article on how to restore the phone to Oxygen 2.1.1. It would wipe user data but I did it anyway and it actually did restore the phone and now I have a worling recovery.
Here is a link to the guide I used:
http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
Thanks again for the help in solving my issue
Click to expand...
Click to collapse
HI there,
I am having the exact same issue with my oneplus 2. Unfortunately i know almost nothing regarding these android thingy. I know it has been almost 2 years, would you mind guide me through the steps? I would appreciate it so much.
Thanks.
I'm stuck in a tough place and I'm not sure where to go.
I was trying to return my phone to stock and I can boot into Android (Though I can't go past the 'Checking Connection Page' due to living in China (even though I'm trying through a VPN) and my recovery now has a little Android bot with a sign.
Since this happened my ADB/fastboot doesn't recognize my device anymore, I can't log into Android because of the Firewall situation, I can't reload a custom ROM because TWRP is no longer on my system & the recovery is corrupt and I can't access ADB/fastbook.
Any ideas how I can flash a ROM w/o GApps and fix my recovery? It seems all the tutorials say I have to turn on debugging mode in Android, but I can boot up to Android because for some reason Android isn't accepting my VPNed wifi connection (though it allowed to be access the internet when I didn't install GApps).
Nexicovx said:
I'm stuck in a tough place and I'm not sure where to go.
I was trying to return my phone to stock and I can boot into Android (Though I can't go past the 'Checking Connection Page' due to living in China (even though I'm trying through a VPN) and my recovery now has a little Android bot with a sign.
Since this happened my ADB/fastboot doesn't recognize my device anymore, I can't log into Android because of the Firewall situation, I can't reload a custom ROM because TWRP is no longer on my system & the recovery is corrupt and I can't access ADB/fastbook.
Any ideas how I can flash a ROM w/o GApps and fix my recovery? It seems all the tutorials say I have to turn on debugging mode in Android, but I can boot up to Android because for some reason Android isn't accepting my VPNed wifi connection (though it allowed to be access the internet when I didn't install GApps).
Click to expand...
Click to collapse
Your recovery is not corrupt. That is the stock recovery boot that you are seeing.
Anyways, how come you can't access ADB or fastboot? Because right now, that would be the easiest and fastest way to install TWRP back.
Nexicovx said:
I'm stuck in a tough place and I'm not sure where to go.
I was trying to return my phone to stock and I can boot into Android (Though I can't go past the 'Checking Connection Page' due to living in China (even though I'm trying through a VPN) and my recovery now has a little Android bot with a sign.
Since this happened my ADB/fastboot doesn't recognize my device anymore, I can't log into Android because of the Firewall situation, I can't reload a custom ROM because TWRP is no longer on my system & the recovery is corrupt and I can't access ADB/fastbook.
Any ideas how I can flash a ROM w/o GApps and fix my recovery? It seems all the tutorials say I have to turn on debugging mode in Android, but I can boot up to Android because for some reason Android isn't accepting my VPNed wifi connection (though it allowed to be access the internet when I didn't install GApps).
Click to expand...
Click to collapse
I am guessing the android man image you can see in recovery is laying on its back with its front flap open? Also says No Command?
If so, when on that page, hold the power button in and while holding it click up volume.
You'll see the stock recovery then.
Good luck
dadvs1 said:
I am guessing the android man image you can see in recovery is laying on its back with its front flap open? Also says No Command?
If so, when on that page, hold the power button in and while holding it click up volume.
You'll see the stock recovery then.
Good luck
Click to expand...
Click to collapse
When you get that Android lying down, press the Power Button followed by Volume Up. That will put you into recovery.
Could you not live boot the recovery? fastboot boot twrp.img.
Nexicovx said:
I'm stuck in a tough place and I'm not sure where to go.
I was trying to return my phone to stock and I can boot into Android (Though I can't go past the 'Checking Connection Page' due to living in China (even though I'm trying through a VPN) and my recovery now has a little Android bot with a sign.
Since this happened my ADB/fastboot doesn't recognize my device anymore, I can't log into Android because of the Firewall situation, I can't reload a custom ROM because TWRP is no longer on my system & the recovery is corrupt and I can't access ADB/fastbook.
Any ideas how I can flash a ROM w/o GApps and fix my recovery? It seems all the tutorials say I have to turn on debugging mode in Android, but I can boot up to Android because for some reason Android isn't accepting my VPNed wifi connection (though it allowed to be access the internet when I didn't install GApps).
Click to expand...
Click to collapse
Maybe im not fully understanding you, but it sounds like you can boot recovery and you can boot Android to the welcome screen. If I was you I would try
1.) Take out your sim and skip the full setup process to get straight to your home screen. Then turn on debugging in dev options > adb reboot bootloader
2.) Boot to android welcome screen, turn off phone turn back on holding volume down and power to get to the bootloader.
Fastboot wont work while you're in recovery. The main idea is to get to the bootloader so you can fastboot flash stock ROM and start from scratch
tonystarks260 said:
Maybe im not fully understanding you, but it sounds like you can boot recovery and you can boot Android to the welcome screen. If I was you I would try
1.) Take out your sim and skip the full setup process to get straight to your home screen. Then turn on debugging in dev options > adb reboot bootloader
2.) Boot to android welcome screen, turn off phone turn back on holding volume down and power to get to the bootloader.
Fastboot wont work while you're in recovery. The main idea is to get to the bootloader so you can fastboot flash stock ROM and start from scratch
Click to expand...
Click to collapse
Hello, we appreciate your help
But from what I read and understand, the user, Nexicovx thinks that the Android bot with the exclamation mark, is a sign of corrupt recovery. While it is only the regular behaviour of the stock recovery.
When you boot into stock recovery, he would not be taken to it straight away. It will first show the screen, where the Android bot with some sort of warning sign appears. At that point, he would just have to press the Volume up key, and tap the power button once. This will trigger the stock recovery.
Now, to what you can do @Nexicovx. You need to access a PC and the USB cable. Boot your 6P into bootloader mode by powering it off first, and then press and hold the Volume Down and Power keys altogether until you see the bootloader mode. From there, you can flash the TWRP recovery. Download the latest image from here: https://dl.twrp.me/angler/
And now use the following command to flash it:
Code:
fastboot flash recovery twrp-3.0.2-0-angler.img
Once that is done, you can reboot into TWRP and flash your desired ROM.
Thanks everyone. I misunderstood what the stock recovery looked like and surprisingly I didn't see much information related to this. I have since gotten my phone up and running thanks to your replies.
I forgot exactly what the problem was but I did get it sorted. Thank you.
Nexicovx said:
Thanks everyone. I misunderstood what the stock recovery looked like and surprisingly I didn't see much information related to this. I have since gotten my phone up and running thanks to your replies.
I forgot exactly what the problem was but I did get it sorted. Thank you.
Click to expand...
Click to collapse
Good to know that. :highfive:
I do have one final issue that I haven't resolved yet but I'm going to do another test next week. I live in China and with the latest update I can't install GApps (when the phone reboots after flashing my phone can't connect to the internet even though I'm through a VPN Wifi connection which works perfectly if I don't install GApps).
I'm going to try the last known security update I was using on Pure Nexus from 2/18 and see if this works. I don't remember which Vendor image I used then but I'm not sure if it is too important. I'll post here if it fixes my troubles. I'm having wifi troubles on the latest build and this is what is making me think I'm having my GApps trouble.
Nexicovx said:
I do have one final issue that I haven't resolved yet but I'm going to do another test next week. I live in China and with the latest update I can't install GApps (when the phone reboots after flashing my phone can't connect to the internet even though I'm through a VPN Wifi connection which works perfectly if I don't install GApps).
I'm going to try the last known security update I was using on Pure Nexus from 2/18 and see if this works. I don't remember which Vendor image I used then but I'm not sure if it is too important. I'll post here if it fixes my troubles. I'm having wifi troubles on the latest build and this is what is making me think I'm having my GApps trouble.
Click to expand...
Click to collapse
It could be a vendor issue.
Good to know!