Database Users

[Q] Nexus 7 Update Problem

Today I got a shiny new Nexus 7 32GB and was eager to get using it. Knowing of the 4.1.2 update I decided to get that installed ASAP and enjoy the benefits.
I went to Settings/ About Tablet/ System Update
There it appeared, 4.1.2 update available, so it downloaded the update and I clicked Restart & Install.
It rebooted and about a third of the way across the progress bar, it stopped, showing a green android lying on its back with a red triangle and exclamation mark on it.
I've tried updating through this method several times with the same problem every time. Does anyone know why this could be and a possible solution?
I would prefer to install this update through the device if possible without installing CWM Recovery or any other extra recovery tools.

GAKB said:
Today I got a shiny new Nexus 7 32GB and was eager to get using it. Knowing of the 4.1.2 update I decided to get that installed ASAP and enjoy the benefits.
I went to Settings/ About Tablet/ System Update
There it appeared, 4.1.2 update available, so it downloaded the update and I clicked Restart & Install.
It rebooted and about a third of the way across the progress bar, it stopped, showing a green android lying on its back with a red triangle and exclamation mark on it.
I've tried updating through this method several times with the same problem every time. Does anyone know why this could be and a possible solution?
I would prefer to install this update through the device if possible without installing CWM Recovery or any other extra recovery tools.
Click to expand...
Click to collapse
I have also recently received my shiny new Nexus 7 32gb and have been unable to update to Android 4.1.2 - the update downloads, seems to install, but after restarting Settings still shows I've got 4.1.1.
Anyone got any idea what is going wrong?

Solution
ceefercat said:
I have also recently received my shiny new Nexus 7 32gb and have been unable to update to Android 4.1.2 - the update downloads, seems to install, but after restarting Settings still shows I've got 4.1.1.
Anyone got any idea what is going wrong?
Click to expand...
Click to collapse
I found a solution. The boot loader in stock 4.1.1 is different to those in the updates to 4.1.2 and 4.2 (apparently, I'm not 100% sure) and this prevents a straight forward update. As far as I can tell, the only way around it is to flash the Google stock image for 4.1.2 or 4.2.
Thankfully this is easy to do since you can use this incredibly useful toolkit to do it for you: http://forum.xda-developers.com/showthread.php?t=1809195
Just read through the instructions and make sure to backup your apps and personal files as you will loose all data!
If you choose to donate it'll let you download and install the latest stock image, 4.2, or you can just flash the stock 4.1.2 image for free and wait for the standard OTA update to reach you (which will now work, I tried it).
I chose to donate as the toolkit is superb and makes everything so much easier when fiddling with custom ROM's and backing up apps, and I prefer flashing the complete stock image of a new version rather than updating.
Hope this works out for you and helps anyone else who gets the same problem!

GAKB said:
I found a solution. The boot loader in stock 4.1.1 is different to those in the updates to 4.1.2 and 4.2 (apparently, I'm not 100% sure) and this prevents a straight forward update. As far as I can tell, the only way around it is to flash the Google stock image for 4.1.2 or 4.2.
Thankfully this is easy to do since you can use this incredibly useful toolkit to do it for you: http://forum.xda-developers.com/showthread.php?t=1809195
Just read through the instructions and make sure to backup your apps and personal files as you will loose all data!
If you choose to donate it'll let you download and install the latest stock image, 4.2, or you can just flash the stock 4.1.2 image for free and wait for the standard OTA update to reach you (which will now work, I tried it).
I chose to donate as the toolkit is superb and makes everything so much easier when fiddling with custom ROM's and backing up apps, and I prefer flashing the complete stock image of a new version rather than updating.
Hope this works out for you and helps anyone else who gets the same problem!
Click to expand...
Click to collapse
I don't think this is a solution that I want to try on my brand new Nexus 7. Clearly there is something wrong with it so I think I'll return it to PCWorld for a replacement. Though I might try a 'factory reset' first and see if after that the 4.1.2 update will install properly.

It's worth a try!
ceefercat said:
I don't think this is a solution that I want to try on my brand new Nexus 7. Clearly there is something wrong with it so I think I'll return it to PCWorld for a replacement. Though I might try a 'factory reset' first and see if after that the 4.1.2 update will install properly.
Click to expand...
Click to collapse
That's fair enough, I tried a factory reset first myself to no avail. If you do get your nexus replaced, please let me know if the update works!

ceefercat said:
I don't think this is a solution that I want to try on my brand new Nexus 7. Clearly there is something wrong with it so I think I'll return it to PCWorld for a replacement. Though I might try a 'factory reset' first and see if after that the 4.1.2 update will install properly.
Click to expand...
Click to collapse
You'r taking it back because it wont update due to the bootloader?
Thats jokable.
No offence but it is.

Wilks3y said:
You'r taking it back because it wont update due to the bootloader?
Thats jokable.
No offence but it is.
Click to expand...
Click to collapse
I'm considering taking it back because it is not updating as it is supposed to, as it is designed to. A message comes up on the screen that a system update is available. I go through the procedure to download and install said update. The update doesn't install, though the system now says that it is up-to-date.
Bootloader? I don't even know what that is. I don't know that the problem is caused by the bootloader and neither do you. It may be a joke to you but to me its just a pain in the neck.

Wilks3y said:
You'r taking it back because it wont update due to the bootloader?
Thats jokable.
No offence but it is.
Click to expand...
Click to collapse
Bootloader issues are a pain in the neck. My bootloader is locked and i cannot erase, flash, format ANYTHING on my Nexus 7... :S

Wilks3y said:
You'r taking it back because it wont update due to the bootloader?
Thats jokable.
No offence but it is.
Click to expand...
Click to collapse
obviously the guy doesn't have working knowledge of ADB, rooting/unlocking or any other development terms we use to describe what we are doing to our devices.
The only jokable premise here is some nerd in his mother's basement thumbing his nose at random people because the world he lives in is so narrow it couldn't possibly comprehend the existence of someone honestly asking for advice and then doing the only logical thing he can think of to do as a consumer unfamiliar with a product at a developmental standpoint.
Not everyone wants to root. And not everyone who owns a Nexus has background experience in tinkering with electronics. I've been rooting since my Dinc and I actually want to keep mine as stock as possible. I find more problems come to me when I start messing with the device instead of just leaving it alone.
---------- Post added at 12:58 AM ---------- Previous post was at 12:46 AM ----------
GAKB said:
I found a solution. The boot loader in stock 4.1.1 is different to those in the updates to 4.1.2 and 4.2 (apparently, I'm not 100% sure) and this prevents a straight forward update. As far as I can tell, the only way around it is to flash the Google stock image for 4.1.2 or 4.2.
Thankfully this is easy to do since you can use this incredibly useful toolkit to do it for you: http://forum.xda-developers.com/showthread.php?t=1809195
Just read through the instructions and make sure to backup your apps and personal files as you will loose all data!
If you choose to donate it'll let you download and install the latest stock image, 4.2, or you can just flash the stock 4.1.2 image for free and wait for the standard OTA update to reach you (which will now work, I tried it).
I chose to donate as the toolkit is superb and makes everything so much easier when fiddling with custom ROM's and backing up apps, and I prefer flashing the complete stock image of a new version rather than updating.
Hope this works out for you and helps anyone else who gets the same problem!
Click to expand...
Click to collapse
I appreciate the fix. trying it out now to see if I can get stock 4.2 to update properly
Edit: Worked like a charm thanks bro for the advice

[Q] 4.2.2 OTA killed touch screen

Hey,
So I received the Nexus 10 this morning, signed into my Google account, downloaded a few app updates, then it said the 4.2.2 update was ready. I let it install and reboot, but ever since touch is not working at all on the device. It boots fine, but it won't unlock as it doesn't register the touch.
I've used the Recovery menu to restore it to factory defaults, which it did, but touch still doesn't work (I can't change language etc). I've downloaded the official 4.2.2 ROM, the SDK, installed the USB drivers, but ADB Devices doesn't find it. I guess this is because I can't enable Debugging Mode.
Can anyone offer some advice? Yes, I could return the tablet to Google, but I head back to the Middle East in a few days and I should imagine the turn around time will be much longer than that.
I'm happy to install any custom kernel, recovery mode etc. to try and restore it. When booted, Windows Explorer will allow me access.
I've Googled as much as I can, but most things rely on being able to enable the ADB link.
Many thanks.

You dont need ADB to install the stock firmware, it uses Fastboot. See here:
http://nexus10root.com/nexus-10-unroot/how-to-unrootunbrick-nexus-10-factory-firmware/

EniGmA1987 said:
You dont need ADB to install the stock firmware, it uses Fastboot. See here:
http://nexus10root.com/nexus-10-unroot/how-to-unrootunbrick-nexus-10-factory-firmware/
Click to expand...
Click to collapse
Thank you for your help. Although the above process did re-flash the tablet with the downloaded 4.2.2 firmware, the touch screen is still not accepting any input.
Google only host the 4.2.2 image on their site, but the post here: http://forum.xda-developers.com/showthread.php?t=2003731 has the 4.2 version. I shall download that and try again.

Sinker_UK said:
Thank you for your help. Although the above process did re-flash the tablet with the downloaded 4.2.2 firmware, the touch screen is still not accepting any input.
Google only host the 4.2.2 image on their site, but the post here: http://forum.xda-developers.com/showthread.php?t=2003731 has the 4.2 version. I shall download that and try again.
Click to expand...
Click to collapse
4.2 downloaded and flashed; still no joy.
I guess this will have to go back to Google / Samsung. I don't know what the 4.2.2 update did, but it appears to have completely killed the touch screen!

Sinker_UK said:
Hey,
So I received the Nexus 10 this morning, signed into my Google account, downloaded a few app updates, then it said the 4.2.2 update was ready. I let it install and reboot, but ever since touch is not working at all on the device. It boots fine, but it won't unlock as it doesn't register the touch.
I've used the Recovery menu to restore it to factory defaults, which it did, but touch still doesn't work (I can't change language etc). I've downloaded the official 4.2.2 ROM, the SDK, installed the USB drivers, but ADB Devices doesn't find it. I guess this is because I can't enable Debugging Mode.
Can anyone offer some advice? Yes, I could return the tablet to Google, but I head back to the Middle East in a few days and I should imagine the turn around time will be much longer than that.
I'm happy to install any custom kernel, recovery mode etc. to try and restore it. When booted, Windows Explorer will allow me access.
I've Googled as much as I can, but most things rely on being able to enable the ADB link.
Many thanks.
Click to expand...
Click to collapse
Sorry for not providing any help, however it's a bit strange that flashing a firmware break the screen.
I just received my tab yesterday then flash 4.2.2 OTA without any issues

FredC94 said:
Sorry for not providing any help, however it's a bit strange that flashing a firmware break the screen.
I just received my tab yesterday then flash 4.2.2 OTA without any issues
Click to expand...
Click to collapse
Please don't worry about not providing any help; I appreciate that this one is an oddity. I was just hoping that the OTA had goosed the drivers or some-such, and that re-flashing it would help, but alas no.

Grab the original stock image 4.2.1 and try flashing back to that. Never heard of this before!

brees75 said:
Grab the original stock image 4.2.1 and try flashing back to that. Never heard of this before!
Click to expand...
Click to collapse
Well, as above, I tried the original 4.2 and that didn't work. I haven't seen the 4.2.1 image anywhere, but can't believe that would make a difference when the other two haven't. I've also just tried a touch-based recovery and that also doesn't respond to touches (TWRP). Oh well. :crying:
I'm at a loss of what to do now so will have to send it back. Pity, it was great when it did work!
Thanks for all the help.

I've contacted Google Play. They went through a reset then agreed to replace it. Will return it as faulty for a refund, and purchase another to save time. 32GB this time, seeing as they are now in stock!
Sent from my GT-N7000 using XDA Premium HD app

Phewwwww...scary...The 4.2.2 has been sitting on my task bar forever now but I am still resisting actually installing it. This thread might scare me away even more...Why fix things if they are not broken.

A better topic for your post: "My touch screen happened to stop working after I installed the 4.2.2 OTA" .. but it may not have caused it.
Hardware can break at any time.

I'm holding off on letting 4.2.2 install itself because I read that it breaks Adblock in Firefox. Not sure what 4.2.2 will do for me, but I want Adblock to work!
Edit to add: also just read the thread here about 4.2.2 causing sloooow scrolling problems in Firefox. So if you use Firefox, don't let 4.2.2 install!

Tablet unusable (systemUI crashloop) after the OTA 5.0.2 > 5.1

Well, what a surprise.
After sideloading the OTA (as usual, no errors or anything strange) and waiting for the "Updating android app 1/1xx", the screen goes black. I can't do absolutely anything but to press the power on button to turn on/off the screen (which is black illuminated), and if I hold the button I clearly see the "Power Off?" message in the white box as usual over the black background, and the animation of "Android is turning off" if I turn it off..
Sometimes a SystemUI error appears and after pressing OK it reappears again and again, sometimes showing the live wallpaper behind it. It ends up with an infinite loop of SystemUI crashes.. It may be a prob loading the launcher? it's not even showing status/navigation bars..
This sideloading the OTA on an stock N7. Really google??
When cleaning cache on recovery, it does the updating apps again, then shows for few secs that some app failed and goes black again.
This N7 is stock with the bootloader locked, any way to fix this without needing to unlock (and so wipe)?
Thanks in advance.
EDIT: I'm definitely in a SystemUI crash loop. Even rebooting to safe mode doesn't work at all.

MD5?
I've just downloaded the OTA myself, and thought I'll check out xda just to be sure there is nothing to worry about, and then I see This!
First thing ofcourse would be to make sure the OTA file was not incomplete/damaged. Would you mind confirming the MD5 you've got? Mine is "d394ba9a61f8f6a206b8c427844b5427", file size 106,509,760 bytes.

Silver-Hawk said:
I've just downloaded the OTA myself, and thought I'll check out xda just to be sure there is nothing to worry about, and then I see This!
First thing ofcourse would be to make sure the OTA file was not incomplete/damaged. Would you mind confirming the MD5 you've got? Mine is "d394ba9a61f8f6a206b8c427844b5427", file size 106,509,760 bytes.
Click to expand...
Click to collapse
Hello,
Using "HashMyFiles",
MD5 is d394ba9a61f8f6a206b8c427844b5427,
SHA1 is 9f163586073265c54d86679efd63513a4477cfd8.
Size: 106,509,760 bytes
So yeah, good download file.
And there is no problem with the cable or "Minimal ADB and Fastboot" version since I used it to flash the partitions directly in my other N7 (rooted and such) and also tested applying the N5 5.1 OTA on my N5 and both results were good.
There is no bad stuff here, the REAL file ota 5.0.2 to 5.1 "semi-bricked" my not rooted n7 in 5.0.2..
Google really has QA? I still don't believe an ota did this to a pure n7 stock rom that used otas since the real first 4.1 build to these days.

S**t happens!??
Well, don't know what happened in your case, but all I can tell here (for someone else in a similar situation maybe) is that it worked perfectly fine for me. I updated using adb sideload on a totally stock device as well. Never rooted, no custom recovery, only difference being mine was already bootloader unlocked (don't know if that's why it didn't work for you, though I doubt it). Unlocking the bootloader was the first thing I did out of the box actually, for situations exactly like u're describing.
As for you, I hope it's still being recognized on USB connection so you can pull most of your data atleast. All the best

adb logcat gives me:
[ 03-12 20:52:48.421 29480:29480 E/AndroidRuntime ]
FATAL EXCEPTION: main
Process: com.android.systemui, PID: 29480
java.lang.NullPointerException: Attempt to invoke virtual method 'boolean com.android.systemui.statusbar.phone.PhoneStatusBar.isKeyguardSecure()' on a null object reference
at com.android.systemui.statusbar.phone.KeyguardBottomAreaView.isCameraDisabledByDpm(KeyguardBottomAreaView.java:260)
at com.android.systemui.statusbar.phone.KeyguardBottomAreaView.updateCameraVisibility(KeyguardBottomAreaView.java:237)
at com.android.systemui.statusbar.phone.KeyguardBottomAreaView.onFinishInflate(KeyguardBottomAreaView.java:168)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:814)
at android.view.LayoutInflater.parseInclude(LayoutInflater.java:916)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:802)
at android.view.LayoutInflater.parseInclude(LayoutInflater.java:916)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:802)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:809)
at android.view.LayoutInflater.inflate(LayoutInflater.java:504)
at android.view.LayoutInflater.inflate(LayoutInflater.java:414)
at android.view.LayoutInflater.inflate(LayoutInflater.java:365)
at android.view.View.inflate(View.java:18532)
at com.android.systemui.statusbar.phone.PhoneStatusBar.makeStatusBarView(PhoneStatusBar.java:638)
at com.android.systemui.statusbar.phone.PhoneStatusBar.addStatusBarWindow(PhoneStatusBar.java:3047)
at com.android.systemui.statusbar.phone.PhoneStatusBar.createAndAddWindows(PhoneStatusBar.java:3043)
at com.android.systemui.statusbar.BaseStatusBar.start(BaseStatusBar.java:561)
at com.android.systemui.statusbar.phone.PhoneStatusBar.start(PhoneStatusBar.java:588)
at com.android.systemui.statusbar.SystemBars.createStatusBarFromConfig(SystemBars.java:106)
at com.android.systemui.statusbar.SystemBars.onNoService(SystemBars.java:58)
at com.android.systemui.statusbar.ServiceMonitor.startService(ServiceMonitor.java:228)
at com.android.systemui.statusbar.ServiceMonitor.access$000(ServiceMonitor.java:49)
at com.android.systemui.statusbar.ServiceMonitor$1.handleMessage(ServiceMonitor.java:73)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:135)
at android.app.ActivityThread.main(ActivityThread.java:5254)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:903)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:698)
[ 03-12 20:52:48.425 468: 484 W/ActivityManager ]
Process com.android.systemui has crashed too many times: killing!
Silver-Hawk said:
Well, don't know what happened in your case, but all I can tell here (for someone else in a similar situation maybe) is that it worked perfectly fine for me. I updated using adb sideload on a totally stock device as well. Never rooted, no custom recovery, only difference being mine was already bootloader unlocked (don't know if that's why it didn't work for you, though I doubt it). Unlocking the bootloader was the first thing I did out of the box actually, for situations exactly like u're describing.
As for you, I hope it's still being recognized on USB connection so you can pull most of your data atleast. All the best
Click to expand...
Click to collapse
Yeah I saved all the stuff via adb, but it SUCKS to have to format because an OFFICIAL OTA did this. Thanks mate!
And I now recognize the error of not having the bootloader unlocked. I NEVER suspected to get in such a situation only sideloading otas on a device never unlocked. Google really fails at delivering an stable platform.

Have same problem after sideload update. No root, no unlock and same problem in the logs. I have updated wife's nexus 5 and it works well, but mine stuck on start-up.
Any ideas how to fix it w\o full wipe ?
---------- Post added at 11:20 AM ---------- Previous post was at 10:24 AM ----------
Btw @RusherDude, have you used something like 'Lockscreen Policy' app to disable camera or lock screen ?

Kaspian said:
Have same problem after sideload update. No root, no unlock and same problem in the logs. I have updated wife's nexus 5 and it works well, but mine stuck on start-up.
Any ideas how to fix it w\o full wipe ?
---------- Post added at 11:20 AM ---------- Previous post was at 10:24 AM ----------
Btw @RusherDude, have you used something like 'Lockscreen Policy' app to disable camera or lock screen ?
Click to expand...
Click to collapse
Same prob? So we may not be alone on this.. Google really messed up this OTA.
No, I didn't do anything of that to this N7, it was pure stock lock screen and nova launcher.

@Kaspian
EDIT:
Yes now I remember I had one from the 4.2 times, Lockscreen Policy
https://play.google.com/store/apps/details?id=com.wordpress.chislonchow.deviceadminkeyguard&hl=es
Now I should be able to uninstall it via adb but I get this:
adb uninstall com.wordpress.chislonchow.deviceadminkeyguard
Failure [DELETE_FAILED_DEVICE_POLICY_MANAGER]
Checking the doc:
static int DELETE_FAILED_DEVICE_POLICY_MANAGER
Uninstall return code
uninstall fail if the system failed to delete the package because it is the active DevicePolicy manager.
Any way I can delete this app or deactivate his DeviceAdmin status with ADB and no root? :S I can't find any way.. this is frustrating.

I'm not sure uninstall will help now. I think you need to revert the changes made by "Lockscreen Policy".
I didn't find the solution quick enough and just wiped my nexus 5

Kaspian said:
I'm not sure uninstall will help now. I think you need to revert the changes made by "Lockscreen Policy".
I didn't find the solution quick enough and just wiped my nexus 5
Click to expand...
Click to collapse
It seems that I just need to disable it from the Device Admin rights window (the same reason why you need to disable its device admin rights before uninstalling it normally), but the prob is seems that there is not a way to do that without UI interaction. I can lauch the system activity or even the device admin activity from ADB, but I don't see them in the tablet so I can't interactuate.
It is really, really frustrating. This is the last non-rooted Android device I own, for sure. What a traition....

Yep, this time I unlocked bootloader also...

Kaspian said:
Yep, this time I unlocked bootloader also...
Click to expand...
Click to collapse
Same, just wiped it, unlocked the bootloader and rooted it.. never had this intention but it's terrible that on Android you're forced to wipe because an OTA made an app ruin the tablet (and thank god I had ADB debugging enabled before, otherwise I even wouldn't had be able to save the data via ADB before wiping), it's incredible, Google epic sucks compared to Apple on this.

RusherDude said:
And I now recognize the error of not having the bootloader unlocked. I NEVER suspected to get in such a situation only sideloading otas on a device never unlocked. Google really fails at delivering an stable platform.
Click to expand...
Click to collapse
if you go to the android factory image website
https://developers.google.com/android/nexus/images
in the flashing instructions they give you they specifically tell show and tell you to unlock the boot loader before applying an update. after the update they also instruct you on how to lock the bootloader again. do not start to bash google because you do not follow their instructions.

phrozenstare said:
if you go to the android factory image website
https://developers.google.com/android/nexus/images
in the flashing instructions they give you they specifically tell show and tell you to unlock the boot loader before applying an update. after the update they also instruct you on how to lock the bootloader again. do not start to bash google because you do not follow their instructions.
Click to expand...
Click to collapse
I was NOT flashing a factory image, I was SIDELOADING an OTA.Nothing to do with that.
In fact, my problem would be reproduced if anyone being pure stock on 5.1 downloaded that app and gave it device admin.

Please help stuck on teamwin screen, can't enter into Recovery

I just got my brand new Aluminum Nexus 6P last night, I wanted to test out the new Developer Preview #4 right away, so enrolled in the program and got the OTA update which I took, and rebooted running Android N, looks pretty neat, and nice tweaks, and some new features. But I always like to run Rooted and install custom ROM's, but Root is #1 for me.
Ok so I need a little help, I am following the excellent video by Rootjunky ( thank you ), and got through the unlocked bootloader part easily, and now installed TWRP Recovery easily too, but upon first time booting into TWRP, it's just sitting at the Blue and Gray teamwin screen, and not doing anything else, it's not actually entering into the Recovery, to see the list of options, etc...
I powered the device down, and started up again in Fastboot mode, then chose Recovery, and does the same again, just sits at the blue gray colored teamwin screen, and does nothing.
What happened ?
UPDATE:
I powered the device down / off. Then started up again, it went and booted up, to the fresh clean Android N DP 4. But I am not rooted at all yet, due not being able to fully enter Recovery and flash the SuperSU zip yet.

The issue is because of encryption... you would need to run fastboot format userdata... and then flash twrp... you would then be able to use it... p.s use the latest twrp version
SENT... isn't that enough

rohit25 said:
The issue is because of encryption... you would need to run fastboot format userdata... and then flash twrp... you would then be able to use it... p.s use the latest twrp version
SENT... isn't that enough
Click to expand...
Click to collapse
Can you spell that out a little bit for me please ?
So right now I am on the Android N beta 4, I have an unlocked bootloader, and TWRP not booting up for me, so do I need to restart the whole rooting and Recovery method all over again ? I do have a modified boot.img from another thread here dated 06-15, but at what point am I supposed to run the command for format data ? And what is the exact correct sentence and spelling of that command I should enter ?

Download Wugfresh Toolkit. It'll carry you through the process with no problem.
Best part, a Nexus is hard to brick. ?

Curiousn00b said:
Download Wugfresh Toolkit. It'll carry you through the process with no problem.
Best part, a Nexus is hard to brick. ��
Click to expand...
Click to collapse
Wow thanks, but never heard of this thing before. Is it like a all-in-one root kit, that does it all for you ? I have normally followed the YouTube videos on how to do it the long way with command prompt and pushing files to the phone, etc...
Silly question, but with this toolkit, is this something I download and install on the phone itself, or run through my PC ?

Zorachus said:
Wow thanks, but never heard of this thing before. Is it like a all-in-one root kit, that does it all for you ? I have normally followed the YouTube videos on how to do it the long way with command prompt and pushing files to the phone, etc...
Silly question, but with this toolkit, is this something I download and install on the phone itself, or run through my PC ?
Click to expand...
Click to collapse
Could you stop posting the same question in multiple threads? It's inconsiderate of people's time.
Sent from my Nexus 5X using Tapatalk

Holy crap, that Nexus Root Toolkit, is like something from Star Trek future. Did Commander Data write this amazing program ? UNBELIEVABLY FANTASTIC PROGRAM.
I was just on the stock phone, not rooted or TWRP or anything, I then install this nexus Toolkit, run the program, and it totally rooted and installed custom TWRP Recovery on my phone, while still being on the Android N 4 preview. I am blown away at how it did all of this, in like 5 minutes.
Couple questions please;
- Android N doesn't have Xposed, so that kind of sucks, but totally expected with this being a beta preview obviously.
- Seems like some root programs not even working, like my classic AdAway, is that due to this being N ?
- How hard is it to revert back to a MM ROM ? Let's say I want to install Pure Nexus ROM, which is already on my SD Card, can I just boot into TWRP Recovery, wipe system, and flash Pure Nexus + GAPPS and reboot ? Or do I need to do something special first to downgrade to MM coming from N now ?

Zorachus said:
Holy crap, that Nexus Root Toolkit, is like something from Star Trek future. Did Commander Data write this amazing program ? UNBELIEVABLY FANTASTIC PROGRAM.
I was just on the stock phone, not rooted or TWRP or anything, I then install this nexus Toolkit, run the program, and it totally rooted and installed custom TWRP Recovery on my phone, while still being on the Android N 4 preview. I am blown away at how it did all of this, in like 5 minutes.
Couple questions please;
- Android N doesn't have Xposed, so that kind of sucks, but totally expected with this being a beta preview obviously.
- Seems like some root programs not even working, like my classic AdAway, is that due to this being N ?
- How hard is it to revert back to a MM ROM ? Let's say I want to install Pure Nexus ROM, which is already on my SD Card, can I just boot into TWRP Recovery, wipe system, and flash Pure Nexus + GAPPS and reboot ? Or do I need to do something special first to downgrade to MM coming from N now ?
Click to expand...
Click to collapse
Adaway does work you need systemless one? no just wipe everything other then internal flash rom gapps and vendor

wifi not working on android p

I've upgraded to Android p and a few minutes ago I've rooted my phone
Since then my wifi won't work, what can I do?
Ok the root did not work

TheZadok42 said:
I've upgraded to Android p and a few minutes ago I've rooted my phone
Since then my wifi won't work, what can I do?
Ok the root did not work
Click to expand...
Click to collapse
Kernel or firmware mismatch
Sent from my PH-1 using Tapatalk

Reflash it
TheZadok42 said:
I've upgraded to Android p and a few minutes ago I've rooted my phone
Since then my wifi won't work, what can I do?
Ok the root did not work
Click to expand...
Click to collapse
Rooting a Beta Rom is usually a bad thing. My only suggestion is reflash following Essential's steps...

Wolfhawke said:
Rooting a Beta Rom is usually a bad thing. My only suggestion is reflash following Essential's steps...
Click to expand...
Click to collapse
Why? Root works fine with it, this has nothing to do with that.

crixley said:
Why? Root works fine with it, this has nothing to do with that.
Click to expand...
Click to collapse
Root works fine with what? A dev preview OS.
If someone is having issues then it must not be working ok.

jmill75 said:
Root works fine with what? A dev preview OS.
If someone is having issues then it must not be working ok.
Click to expand...
Click to collapse
Yes it works fine and the issue has nothing to do with root. Probably half of us using it are rooted without issue

Bit of a thread-dig here, but I just got a PH1 and went straight to P (not rooted yet) and saw no WiFi. Wouldn't even turn on.
The phone came with 7.1.1 and I flashed P via fastboot. Tried rebooting and monkeying with it, but never saw any progress, no list of networks, etc.
7.1.1 did see WiFi for the 5 minutes I ran it.
Flashed latest stable 8.1 and it WiFi worked again immediately.
Then flashed 9 a second time and now WiFi works fine.
My best guess is the 7.1.1->9 transition has some kind of issue (doesn't quite make sense to me, given that I think EVERYTHING is being flashed by the 9 update, but this did fix it).

tliebeck said:
Bit of a thread-dig here, but I just got a PH1 and went straight to P (not rooted yet) and saw no WiFi. Wouldn't even turn on.
The phone came with 7.1.1 and I flashed P via fastboot. Tried rebooting and monkeying with it, but never saw any progress, no list of networks, etc.
7.1.1 did see WiFi for the 5 minutes I ran it.
Flashed latest stable 8.1 and it WiFi worked again immediately.
Then flashed 9 a second time and now WiFi works fine.
My best guess is the 7.1.1->9 transition has some kind of issue (doesn't quite make sense to me, given that I think EVERYTHING is being flashed by the 9 update, but this did fix it).
Click to expand...
Click to collapse
Just got my Essential Phone today as well and did the exact same thing, flashed straight from 7.1.1 to P. I thought I was seriously going to have to send the phone back due to a broken Wi-Fi chip or something. You are seriously a lifesaver!

rignfool said:
Kernel or firmware mismatch
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
What can be done about this? I am having the same issue, but I have flashed the whole "Back to Stock" set for P beta 2 from the other thread.

Saundersmtt said:
What can be done about this? I am having the same issue, but I have flashed the whole "Back to Stock" set for P beta 2 from the other thread.
Click to expand...
Click to collapse
If I take your post at face value... You have a bad flash and need to try again... Or blame your cable... And go buy a new one...
Otherwise... You have a bad download... Or there is something wrong wrong with your zip or batch/script... Or you're not completely unlocked

Listen guys, the issue is bc the ota zip for p doesnt flash both slots and the fastboot images zip doesnt either. If u look at the script (flashall. Bat) with a text editor it specifically shows only flashing one slot. To fix the wifi issue, u need the july oreo images file and that flashall. Bat flashes both slots and will fix the lost wifi and or Bluetooth. Once u do that, it reboots twice and go back to dev options and renable usb debugging. Now u reboot bootloader and flash p. Now it should all work. Also, in doing this, you will have to lose your data.

Same here but can't roll back to Oreo
See.issue here but I seem.to not be able.to resolve wifi issue or roll back to Oreo. When I try to reflash it just says it expects a newer version of is. Any ideas?

1jason said:
See.issue here but I seem.to not be able.to resolve wifi issue or roll back to Oreo. When I try to reflash it just says it expects a newer version of is. Any ideas?
Click to expand...
Click to collapse
Yes flash the july oreo flashall. Bat

Saundersmtt said:
What can be done about this? I am having the same issue, but I have flashed the whole "Back to Stock" set for P beta 2 from the other thread.
Click to expand...
Click to collapse
I had the same problem. went back to stock on July's build (was on January's stock build previously) and reflashed P. Been smooth sailing ever since

jacksummers said:
Listen guys, the issue is bc the ota zip for p doesnt flash both slots and the fastboot images zip doesnt either. If u look at the script (flashall. Bat) with a text editor it specifically shows only flashing one slot. To fix the wifi issue, u need the july oreo images file and that flashall. Bat flashes both slots and will fix the lost wifi and or Bluetooth. Once u do that, it reboots twice and go back to dev options and renable usb debugging. Now u reboot bootloader and flash p. Now it should all work. Also, in doing this, you will have to lose your data.
Click to expand...
Click to collapse
The reason is because one of the OTAs did not have the partition you're looking for... And it created a mismatch somewhere...
You DO NOT need to have the same software on A and B... It just makes troubleshooting easier from our perspective... And... It forces you to reflash and probably fix the problem...
As intended... There should ALWAYS be a mismatch between A and B... At least a monthly security update... If not an Android versioning difference

Edited. We are all just trying to help others. Lets keep it that way.

so, uhmmm like yea...... there is this thread here, called the stock images thread (link for posterity https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681 ) this is firmware images, directly from essential. I have added the remaining images that you dont get from essential, so that way you can reflash, and get the same version of software on both sides. there are wipe and no wipe bat files in there, twrp11 (the working twrp we have), and the fix red boot (in case you broke verity), and a stockboot.img (coincidentally the same file as called boot in the zip, but renamed for your twrp/rooting pleasure).
These images work great, many many many people have used them to go back and forth between O and P, OTA, or recover from catastrophe. As usual, beware of dragons, make SURE SURE SURE SURE you have a working adb/fastboot environment (use the version that comes with essentials drivers) (you can always do ADB VERSION or FASTBOOT --VERSION ) to check your version and where its working out of. It is 1 stop shopping. I also know the guy that makes the zips

jacksummers said:
Edited. We are all just trying to help others. Lets keep it that way.
Click to expand...
Click to collapse
Sorry if my post came off as harsh... I'll edit it... But this forum is literally littered with VAST amounts of guessing and misinformation...

rignfool said:
Sorry if my post came off as harsh... I'll edit it... But this forum is literally littered with VAST amounts of guessing and misinformation...
Click to expand...
Click to collapse
No prob, i understand the frustration.i assure you i was not guessing. I only post what i know is for sure. When faced with the exact same issue as OP i was forced to flash both slots to fix it. Yes, they could boot up with slightly different partitions, but the wifi was broken still. I believe the whole phone needed both slots flashed with each corresponding img simultaneously in order to resolve said issue. For whatever reason, i had both a and b screwed up. At the time i was trying to fix the ril and camera issues on the pixel 2 system image after flashing it on my essential. I want to get that working fully to release as a port.

jacksummers said:
No prob, i understand the frustration.i assure you i was not guessing. I only post what i know is for sure. When faced with the exact same issue as OP i was forced to flash both slots to fix it. Yes, they could boot up with slightly different partitions, but the wifi was broken still. I believe the whole phone needed both slots flashed with each corresponding img simultaneously in order to resolve said issue. For whatever reason, i had both a and b screwed up. At the time i was trying to fix the ril and camera issues on the pixel 2 system image after flashing it on my essential. I want to get that working fully to release as a port.
Click to expand...
Click to collapse
Wouldn't it be easier to attempt to port the 2 or 3 features we don't have as a separate systemui.apk or framework-res.apk?
And use Magisk?
Since we don't have that fancy hardware photo rendering thingymabob