Database Users

5.0.1 factory image!

It's out guys!
https://developers.google.com/android/nexus/images

jarjar124 said:
It's out guys!
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Thanks for the heads up!

if anyone is going to flash this, could you please benchmark it encrypted?
i saw a bench today where someone had fullspeed even encrypted. is this on 5.0.1?

Interesting that it is the exact same build as the other 5.0.1 updates. No major Shamu specific changes? Hopefully the new binaries provide significant improvements at least.

So I wondering, do we need to unroot the device in order to update using factory images, I had read sometime back how updates in Lolipop now checks all system files and if they are patched/altered the update will fail, but have not ready any issues updating the nexus 7 to 5.0.1 or the nexus 10 when they are root.

wolfnumba1 said:
So I wondering, do we need to unroot the device in order to update using factory images, I had read sometime back how updates in Lolipop now checks all system files and if they are patched/altered the update will fail, but have not ready any issues updating the nexus 7 to 5.0.1 or the nexus 10 when they are root.
Click to expand...
Click to collapse
No need to unroot to flash the new images..
Sent from my Nexus 4 using Tapatalk

ohhdavid said:
Interesting that it is the exact same build as the other 5.0.1 updates. No major Shamu specific changes? Hopefully the new binaries provide significant improvements at least.
Click to expand...
Click to collapse
There might be as there are new binaries I believe. I'll need to check when I'm home.

BRKotucs said:
No need to unroot to flash the new images..
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Right that was only for flashing OTA update files right? Doing it through fastboot should just work, taking nandroid and then flashing after will post status

Flashed it, but manually disabled force encryption in kernel.
Interesting that I'm not getting 200+/60+ as before, it is 160/140 with no encryption, will check other benchmarks and may be some background load in progress as I just first booted after flash.

Can someone tell me how to flash this right?
im on stock, decrypted and rooted+TRWP on it.
do i need to start all over after flashing?

XorZone said:
Flashed it, but manually disabled force encryption in kernel.
Interesting that I'm not getting 200+/60+ as before, it is 160/140 with no encryption, will check other benchmarks and may be some background load in progress as I just first booted after flash.
Click to expand...
Click to collapse
How did you disable the encryption in kernel, before I remember just using a modified boot image, dont know if that one will work for the new 5.0.1 factory image though, did you use the same boot image from this link to do this before updating?
http://forum.xda-developers.com/nexus-6/development/disable-forced-encryption-gain-root-t2946715
---------- Post added at 06:59 AM ---------- Previous post was at 06:57 AM ----------
Silentsoul said:
Can someone tell me how to flash this right?
im on stock, decrypted and rooted+TRWP on it.
do i need to start all over after flashing?
Click to expand...
Click to collapse
So I was same, root with decrypted kernel and TWRP. I updated manually but forgot I had it decrypted, its encrypting right now, good thing I took a nandroid before so I am going to restore back to that image and try again with that modified boot image like I did before when I decrypted it and will let you know.

Silentsoul said:
Can someone tell me how to flash this right?
im on stock, decrypted and rooted+TRWP on it.
do i need to start all over after flashing?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2954008
Sent from my Nexus 4 using Tapatalk

wolfnumba1 said:
How did you disable the encryption in kernel, before I remember just using a modified boot image, dont know if that one will work for the new 5.0.1 factory image though, did you use the same boot image from this link to do this before updating?
http://forum.xda-developers.com/nexus-6/development/disable-forced-encryption-gain-root-t2946715
Click to expand...
Click to collapse
Nope, I took 5.0.1 kernel, unpacked it, changed from force encrypt to encryptable and repacked. Will post it in that thread as soon as I'll get back to PC.

XorZone said:
Flashed it, but manually disabled force encryption in kernel.
Interesting that I'm not getting 200+/60+ as before, it is 160/140 with no encryption, will check other benchmarks and may be some background load in progress as I just first booted after flash.
Click to expand...
Click to collapse
I have noticed the same thing on 5.0
I got the amazing speeds upon first boot after flashing then never again. 160/140 is similar to what i'm getting now. was that the same as encrypted?
Maybe it was all a placebo.

No force encryption boot img here:
http://forum.xda-developers.com/showpost.php?p=57406510&postcount=360

XorZone said:
No force encryption boot img here:
http://forum.xda-developers.com/showpost.php?p=57406510&postcount=360
Click to expand...
Click to collapse
Thanks!

wolfnumba1 said:
So I was same, root with decrypted kernel and TWRP. I updated manually but forgot I had it decrypted, its encrypting right now, good thing I took a nandroid before so I am going to restore back to that image and try again with that modified boot image like I did before when I decrypted it and will let you know.
Click to expand...
Click to collapse
Curious to see if root will still work? I am not sure if we will need an updated img to fastboot flash boot to get root again.
---------- Post added at 03:17 PM ---------- Previous post was at 03:16 PM ----------
XorZone said:
Flashed it, but manually disabled force encryption in kernel.
Interesting that I'm not getting 200+/60+ as before, it is 160/140 with no encryption, will check other benchmarks and may be some background load in progress as I just first booted after flash.
Click to expand...
Click to collapse
What app are you using to measure?

joderme said:
Curious to see if root will still work? I am not sure if we will need an updated img to fastboot flash boot to get root again.
Ill let you know, its updating now after flashing however I am going to reflash like I said before, I will check root status first though, I am sure the root is gone now.
Click to expand...
Click to collapse

joderme said:
Curious to see if root will still work? I am not sure if we will need an updated img to fastboot flash boot to get root again.
What app are you using to measure?
Click to expand...
Click to collapse
1. cf-autoroot after flashing and 1 time booting works fine
2. androbench

Is the kernel the same? I'm curious if they changed it.

[Q] Unusual bootloop won't quit

So, I was running stock kitkat on a refurbished Nexus 7. After some months it just suddenly restarted and entered a bootloop. I can turn the device off and enter fastboot mode, but the recovery just seems to be broken. I've tried using the Nexus root kit utility, and "successfully" flashed 5.0.2. It said I should wait even more than 10 minutes, and that the device would seem to be on a boot loop (again), I let it do its magic all night but nothing happened. I unlocked the device and flashed 4.4.4 and I'm having the same problem, after "succesfully" flashing, the device enters the bootloop. Any ideas are much appreciated Thanks!

Please try to reflash the bootloader manually using fastboot

zzzkaushal said:
Please try to reflash the bootloader manually using fastboot
Click to expand...
Click to collapse
I tried it, but when I need to flash /system, it gave me this first:
FAILED <remote: bogus Chunk size for Chunk type Raw>
On later attempts, it gave me this one:
FAILED <remote: bogus Chunk size for Chunk type Raw>
I'm still on a bootloop, recovery gives me a bootloop as well :/

Try manually flashing twrp latest recovery for your nexus 7
---------- Post added at 09:40 AM ---------- Previous post was at 09:30 AM ----------
Are u using the latest version of fastboot and adb

zzzkaushal said:
Try manually flashing twrp latest recovery for your nexus 7
---------- Post added at 09:40 AM ---------- Previous post was at 09:30 AM ----------
Are u using the latest version of fastboot and adb
Click to expand...
Click to collapse
Don't really know, I downloaded it more than 6 months ago... I think I'll re-download it and give it a try, if it doesn't, I'll try the recovery you told me. Sorry for the late reply, I don't get much free time nowadays :/ And thanks for all your support, if this gets me to a fully operable Nexus 7, I'll definitely make sure to get you a coffee! Cheers!
---[EDIT]---
I tried twrp recovery, it installs successfully but it keeps getting in a bootloop :/ I'll re-download ADB, hopefully this will help 'cause I'm running out of solutions

So..
Any progress now

zzzkaushal said:
So..
Any progress now
Click to expand...
Click to collapse
I have not been able to re download adb, that's my last resource. hopefully I'll try in a few days.

Hey! Sorry for the late reply. I just downloaded the most recent ADB and TWRP recovery image. I manually flashed it with no problems, but my device keeps getting in the google bootloop

try to flash official .img rom and do it again

rickliu said:
try to flash official .img rom and do it again
Click to expand...
Click to collapse
I'm using NRT, so I assume the rom it downloads is an official .img rom, isn't it? Should I download it from somewhere else?

May 2016 Security Factory images released (MTC19T)

Google just released May 2016 factory images for Nexus devices.
Factory Images for Nexus Devices
Android Security Bulletin—May 2016

Anyone flashed it?

OTA zip file link?
Sent from my Nexus 5X using XDA-Developers mobile app

We probably need to wait a little bit for OTA zip.

following for ota link

new radio is out with this update, radio-bullhead-m8994f-2.6.32.1.13

miksontije said:
new radio is out with this update, radio-bullhead-m8994f-2.6.32.1.13
Click to expand...
Click to collapse
Hopefully it's a good update. Sometimes they're hit-or-miss.

mxrider97 said:
Anyone flashed it?
Click to expand...
Click to collapse
Flashed it yesterday, haven't noticed anything new. However, I also haven't noticed anything bad or broken; which is just as important.
Sent from my Nexus 5X using Tapatalk

Flashed using the factory images and nothing is broken. It did trigger a Google Camera update and it has been improved a bit more. Faster startup and snappier response when changing between portrait and landscape mode. Battery life stayed the same.

waiting for ota zip :good:

I updated using fastboot. Rooted and everything is working fine. Even Android Pay with the latest SuperSU.

I cant get TWRP working, I've flashed 3.0.2-0 to recovery partition using fastboot but when trying to reboot to recovery I just get the android exclamation mark icon (which I think is default recovery?). I upgraded by flashing all images but userdata from April security image.

Just installed! You have any advice about a compatible kernel?

Andr006 said:
Just installed! You have any advice about a compatible kernel?
Click to expand...
Click to collapse
I like EX Kernel. It has not been update with the new patches but will still work well.
---------- Post added at 06:20 PM ---------- Previous post was at 06:18 PM ----------
chispynexus said:
I cant get TWRP working, I've flashed 3.0.2-0 to recovery partition using fastboot but when trying to reboot to recovery I just get the android exclamation mark icon (which I think is default recovery?). I upgraded by flashing all images but userdata from April security image.
Click to expand...
Click to collapse
I update all the images with fastboot then just use WugFresh to root and add TWRP.

65coupei6 said:
I update all the images with fastboot then just use WugFresh to root and add TWRP.
Click to expand...
Click to collapse
This worked in the end, thanks for your help tip!

chispynexus said:
I cant get TWRP working, I've flashed 3.0.2-0 to recovery partition using fastboot but when trying to reboot to recovery I just get the android exclamation mark icon (which I think is default recovery?). I upgraded by flashing all images but userdata from April security image.
Click to expand...
Click to collapse
if you boot using stock kernel (boot.img) android will replace whatever recovery you have flashed with stock recovery.
to prevent this from happening, PRIOR to first boot after flashing update, flash twrp in fastboot, scroll down in fastboot menu and boot into recovery/twrp, and apply supersu update.zip
after that you'll be rooted again and boot.img will no longer try and replace your recovery with stock recovery.

OTA posted:
http://forum.xda-developers.com/showpost.php?p=66781159&postcount=124

May images up. SU may be broke.

I just downloaded and flashed the May security update.
Booting into TWRP and then installing SU throws it into a bootloop. Still testing and investigating, would be great if some others could test to see if it is universal or just me.

TonikJDK said:
I just downloaded and flashed the May security update.
Booting into TWRP and then installing SU throws it into a bootloop. Still testing and investigating, would be great if some others could test to see if it is universal or just me.
Click to expand...
Click to collapse
It's not just you.

TonikJDK said:
I just downloaded and flashed the May security update.
Booting into TWRP and then installing SU throws it into a bootloop. Still testing and investigating, would be great if some others could test to see if it is universal or just me.
Click to expand...
Click to collapse
ME too. TWRP installer for sure.

Tulsadiver said:
ME too. TWRP installer for sure.
Click to expand...
Click to collapse
Installing SuperSU from the RC1 img or installing RC2 and then installing SuperSU from there?

Looks like I'll wait on May factory images ...

sliding_billy said:
Installing SuperSU from the RC1 img or installing RC2 and then installing SuperSU from there?
Click to expand...
Click to collapse
After booting into TWRP, flashing twrp pixel installer, then trying to boot back into TWRP bootloops without even getting to supersu.

The reasons to stay stock, are starting to out weigh the reasons to root.

Tulsadiver said:
After booting into TWRP, flashing twrp pixel installer, then trying to boot back into TWRP bootloops without even getting to supersu.
Click to expand...
Click to collapse
Gotcha. That stinks! I have never booted back into TWRP after installing. I have just went straight to SuperSU installer after RC2 install. I imagine that would have just created a different issue.

sliding_billy said:
Gotcha. That stinks! I have never booted back into TWRP after installing. I have just went straight to SuperSU installer after RC2 install. I imagine that would have just created a different issue.
Click to expand...
Click to collapse
They will probably figure something out. Nexus 5X didn't have any problems with their May update.

Tulsadiver said:
They will probably figure something out. Nexus 5X didn't have any problems with their May update.
Click to expand...
Click to collapse
I'm sure. I am in no hurry for what is most likely just a security update.

Sideloading the correct image now. Pisses me off there is a separate image for Verizon. I flashed the Verizon version instead of the standard one.
---------- Post added at 04:42 PM ---------- Previous post was at 04:35 PM ----------
Loaded the May images on the 5x. Magisk is good to go for the 5X. Pixel is stock right now.

Glad I came here before installing the May update.....

TonikJDK said:
I just downloaded and flashed the May security update.
Booting into TWRP and then installing SU throws it into a bootloop. Still testing and investigating, would be great if some others could test to see if it is universal or just me.
Click to expand...
Click to collapse
Definitely not just you. I thought it was an issue with SuperSU, but it's actually an issue with TWRP?

CatThief said:
Definitely not just you. I thought it was an issue with SuperSU, but it's actually an issue with TWRP?
Click to expand...
Click to collapse
Both

CatThief said:
Definitely not just you. I thought it was an issue with SuperSU, but it's actually an issue with TWRP?
Click to expand...
Click to collapse
Tulsadiver said:
Both
Click to expand...
Click to collapse
Just use April's bootloader and everything works fine. Thanks to a user in the XL therad for the info. I'm rooted on the May L version with April's K bootloader.

Misterxtc said:
Just use April's bootloader and everything works fine. Thanks to a user in the XL therad for the info. I'm rooted on the May L version with April's K bootloader.
Click to expand...
Click to collapse
Works for me. Thanks Misterxtc!

Misterxtc said:
Just use April's bootloader and everything works fine. Thanks to a user in the XL therad for the info. I'm rooted on the May L version with April's K bootloader.
Click to expand...
Click to collapse
How did you do that?
UPDATE: Problem solved...

Swerner1975 said:
How did you do that?
UPDATE: Problem solved...
Click to expand...
Click to collapse
If you didn't figure it out or anyone else needs help I downloaded both the K and L updates, installed L, rebooted to bootloader and ran the following command with the K bootloader then reboot bootloader. After that you can install TWRP and root.
Code:
fastboot flash bootloader bootloader-sailfish-8996-012001-1702151126

Misterxtc said:
If you didn't figure it out or anyone else needs help I downloaded both the K and L updates, installed L, rebooted to bootloader and ran the following command with the K bootloader then reboot bootloader. After that you can install TWRP and root.
Code:
fastboot flash bootloader bootloader-sailfish-8996-012001-1702151126
Click to expand...
Click to collapse
THX!

If you flash manually you just skip the first step. The bootloader part.

unresponsive touch screen

A strange thing happened today. I flashed twrp on my s8+( SM-G955FD ) but i had the problem that internal storage could not be mounted. Tried several things but nothing happened. I found a fix on this https://forum.xda-developers.com/galaxy-s8/samsung-galaxy-s8--s8-cross-device-development/fix-data-mount-fix-s8-twrp-oreo-t3769254#post76036701 on post #6. I flashed the fix and when i rebooted, touch screen was not working. Any suggestions? I also tried wiping data but no luck still

Flash nx kernel for s8 search and download anf flash through twrp.... Thank me later

khawarjaved said:
Flash nx kernel for s8 search and download anf flash through twrp.... Thank me later
Click to expand...
Click to collapse
This worked but when it booted up, says that magisk is not installed. I assume flashing it will resolve it, right?

smavr said:
this worked but when it booted up, says that magisk is not installed. I assume flashing it will resolve it, right?
Click to expand...
Click to collapse
flash magisk again no problem

khawarjaved said:
flash magisk again no problem
Click to expand...
Click to collapse
Well it stuck on samsung logo

did u wipe cache/delvik cache

khawarjaved said:
did u wipe cache/delvik cache
Click to expand...
Click to collapse
Yes. no luck still

which rom?

khawarjaved said:
which rom?
Click to expand...
Click to collapse
Stock rom. with nx kernel you suggested before

samsung-antiroot-removal-2.4
RMM-State_Bypass_Mesa
download these 2
flash along with magisk my selecting multiple zip options
then let me know
---------- Post added at 10:21 PM ---------- Previous post was at 10:21 PM ----------
http://dl.techxero.com/Android/samsung-antiroot-removal-4.1.zip

khawarjaved said:
samsung-antiroot-removal-2.4
RMM-State_Bypass_Mesa
download these 2
flash along with magisk my selecting multiple zip options
then let me know
---------- Post added at 10:21 PM ---------- Previous post was at 10:21 PM ----------
http://dl.techxero.com/Android/samsung-antiroot-removal-4.1.zip
Click to expand...
Click to collapse
Still nothing. Any other proposal?

did u try to reset it?

khawarjaved said:
did u try to reset it?
Click to expand...
Click to collapse
What do you mean?

flash twrp again and flash stock kernel....try it

khawarjaved said:
flash twrp again and flash stock kernel....try it
Click to expand...
Click to collapse
that worked. thank you for your time

no problem always here to help.