Develop Bugs

[Q] Gnex stucks on Nexus logo

Hello guys, I need your help with the Gnex.
My friend gave me the phone hoping that I can do something. It stucks on nexus logo while booting. USB debugging is turned off, cwm or twrp is not installed. All I can is to enter Android system recovery with the following options: apply update from adb; apply update from usb drive; wipe data factory reset; wipe cache partition.
I've tried wiping cache partition but is doesn't help. Please advice whether wiping data/factory reset will delete the data from internal SD card - I am afraid to lose the photos.
Please advice what should I do to extract data (photos) in my situation?
Thanks in advance to everyone.

Sync???
were photos synced to google????

tosradde for
Wajeeh4616 said:
were photos synced to google????
Click to expand...
Click to collapse
No, they weren't.

fastboot? try it first..
change ur boot.img /kernel
Sent from my Galaxy Nexus using XDA Premium 4 mobile app

memaro_maro said:
fastboot? try it first..
change ur boot.img /kernel
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Can you please explain - I'm new in this. I can enter fasrboot mode, the status is FAILBootloader locked. What should I do next?

3n3r said:
Can you please explain - I'm new in this. I can enter fasrboot mode, the status is FAILBootloader locked. What should I do next?
Click to expand...
Click to collapse
?? learn about adb & fastboot..
or use this toolkit
http://forum.xda-developers.com/showthread.php?t=2389107
try use modified boot.img
Sent from my Galaxy Nexus using XDA Premium 4 mobile app

wiping
I don't think that anything can help you except that tool because as you are saying that USB debugging is not enabled

Wajeeh4616 said:
I don't think that anything can help you except that tool because as you are saying that USB debugging is not enabled
Click to expand...
Click to collapse
Made wipe data - android loaded but photos are gone.. sad

3n3r said:
Made wipe data - android loaded but photos are gone.. sad
Click to expand...
Click to collapse
before using device too much, quick go to galaxy nexus general section here, and find thread "internal data recovery, yes we can"
you might be able to recover deleted photos.
the way it works when you delete things, is it just tells os that the space isnt being used, so the actual data might still be there and some may still be recoverable.
it is quite a process though. good luck

3n3r said:
Made wipe data - android loaded but photos are gone.. sad
Click to expand...
Click to collapse
You should install a recovery fast as it will help you in future

ashclepdia said:
find thread "internal data recovery, yes we can"
you might be able to recover deleted photos.
Click to expand...
Click to collapse
Thanks a lot for your suggestion. I'm trying to recover. By the way, do you know what does the phrase from the recover guide "ADB (make sure adb.exe is in your path)" mean? Which path?

3n3r said:
Thanks a lot for your suggestion. I'm trying to recover. By the way, do you know what does the phrase from the recover guide "ADB (make sure adb.exe is in your path)" mean? Which path?
Click to expand...
Click to collapse
The directory from which you are using adb command
As an example if I am using cmd and typing this command then it should be like
E:/>adb fastboot *********
Then my adb file must be in E drive

Wajeeh4616 said:
The directory from which you are using adb command
As an example if I am using cmd and typing this command then it should be like
E:/>adb fastboot *********
Then my adb file must be in E drive
Click to expand...
Click to collapse
Thank you for your help. I've followed to step 6, but unfortunalely, RAW file is 0 b after creation. I've tried different numbers in this name mmcblk0p12.raw - but with no effect.. Tried to reinstall cygwin, used NetCat file insted of NC - all the same.
Maybe anyone faced this problem with 0 b size of the RAW file? Maybe it's because I have less than 15 Gb of free space on my disk C?
Would be grateful for your advices.

3n3r said:
Thank you for your help. I've followed to step 6, but unfortunalely, RAW file is 0 b after creation. I've tried different numbers in this name mmcblk0p12.raw - but with no effect.. Tried to reinstall cygwin, used NetCat file insted of NC - all the same.
Maybe anyone faced this problem with 0 b size of the RAW file? Maybe it's because I have less than 15 Gb of free space on my disk C?
Would be grateful for your advices.
Click to expand...
Click to collapse
Cant answer your question but can give you an advice....
Leave all this and dont play with your mobile they were only pictures so forget them or else after sometime you will be following a guide to unbrick your phone.

3n3r said:
Thanks a lot for your suggestion. I'm trying to recover. By the way, do you know what does the phrase from the recover guide "ADB (make sure adb.exe is in your path)" mean? Which path?
Click to expand...
Click to collapse
I'd like to try explaining this a little better. Basically when using a program from the command prompt in any OS the OS needs to know where the program is (this is not just for command prompt, but I digress). There are a few ways of telling the OS where the program you want to use is located.
For example, lets say you have ADB in the folder "android_stuff" on your E drive.
Option 1: Change Directory to the folder, IE: "cd android_stuff"
Option 2: Provide the "full path name" of the program, "e:\android_stuff\adb"
Option 3: Add the folder location to the system "path"
Options 1 and 2 are fairly easy and straightforward, whereas Option 3 can be done in a few ways.
My suggestion is to go with Option 1, its the easiest and all you would have to do is put all of the files you will be using into a single folder.

Pattern unlock after TWRP restore

Nexus 5X
TWRP 2.8.7.2
- Backup included: Boot, System, Vendor, Vendor image, Data, Recovery & EFS
- Stock ROM rooted
I created this backup because I wanted to try out the Pure Nexus ROM. Followed instructions before flashing (wipe data system etc..) everything was working fine but I later decided that I wanted to revert back for the time being. Booted into recovery, wiped data, system and so on before restoring backup. Once restored and at the lockscreen I placed my finger on the fingerprint scanner and was prompted for a pattern. Tried the only pattern I always use multiple times but it didnt work (as well as others) and it never locked me out. Did some reading online, followed an article on how to bypass-androids-pattern-lock-screen-access-its-files-from-pc, when i typed in adb shell rm /data/system/gesture.key I got this error "rm: can't remove '/data/system/gesture.key': No such file or directory. Don't know what to do from here.
Any help would be much appreciated.

bobcee said:
Nexus 5X
TWRP 2.8.7.2
- Backup included: Boot, System, Vendor, Vendor image, Data, Recovery & EFS
- Stock ROM rooted
I created this backup because I wanted to try out the Pure Nexus ROM. Followed instructions before flashing (wipe data system etc..) everything was working fine but I later decided that I wanted to revert back for the time being. Booted into recovery, wiped data, system and so on before restoring backup. Once restored and at the lockscreen I placed my finger on the fingerprint scanner and was prompted for a pattern. Tried the only pattern I always use multiple times but it didnt work (as well as others) and it never locked me out. Did some reading online, followed an article on how to bypass-androids-pattern-lock-screen-access-its-files-from-pc, when i typed in adb shell rm /data/system/gesture.key I got this error "rm: can't remove '/data/system/gesture.key': No such file or directory. Don't know what to do from here.
Any help would be much appreciated.
Click to expand...
Click to collapse
Hmmm. Try to follow this steps:
1: boot into TWRP
2: Mount /system ; /data and others
3: Go to Advanced-File Manager
4: Go to /data/system/
5: If exist the gesture.key file, copy it in your internal/external memory (in case of bootloop)
6: Delete the gesture.key file from /data/system/
7: Reboot and view if the pattern is removed

Giovix92 said:
Hmmm. Try to follow this steps:
1: boot into TWRP
2: Mount /system ; /data and others
3: Go to Advanced-File Manager
4: Go to /data/system/
5: If exist the gesture.key file, copy it in your internal/external memory (in case of bootloop)
6: Delete the gesture.key file from /data/system/
7: Reboot and view if the pattern is removed
Click to expand...
Click to collapse
Hey thanks for the reply, im up to step 5 at the moment currently looking in data/system and cannot find a gesture.key in there. The only .key files present are:
1. gatekeeper.password.key and
2. gatekeeper.pattern.key
There is also locksettings.db, locksettings.db-shm and locksettings.db-wal. Im guessing they are to do with the lockscreen?
Im under the impression that the TWRP restore somehow created a 'ghost' pattern that doesnt seem to exist, hence its not accepting any pattern that i try and is also not limiting the number of tries. (sorry for the terminology im learning haha).

bobcee said:
Hey thanks for the reply, im up to step 5 at the moment currently looking in data/system and cannot find a gesture.key in there. The only .key files present are:
1. gatekeeper.password.key and
2. gatekeeper.pattern.key
There is also locksettings.db, locksettings.db-shm and locksettings.db-wal. Im guessing they are to do with the lockscreen?
Im under the impression that the TWRP restore somehow created a 'ghost' pattern that doesnt seem to exist, hence its not accepting any pattern that i try and is also not limiting the number of tries. (sorry for the terminology im learning haha).
Click to expand...
Click to collapse
Hmmm... Try (via TWRP) to follow this steps:
1: Go to /data/system/
2: Copy in your internal/external sd card these files: gatekeeper.password.key and gatekeeper.pattern.key
3: After you have pasted this files, return to /data/system/
4: Delete (from /data/system) gatekeeper.password.key and gatekeeper.pattern.key
5: Reboot
6: If the nexus will stuck in bootloop, restore these files.
Edit: locksettings.db.... I need to verify this file... I'll give you an update about this file asap.

Giovix92 said:
Hmmm... Try (via TWRP) to follow this steps:
1: Go to /data/system/
2: Copy in your internal/external sd card these files: gatekeeper.password.key and gatekeeper.pattern.key
3: After you have pasted this files, return to /data/system/
4: Delete (from /data/system) gatekeeper.password.key and gatekeeper.pattern.key
5: Reboot
6: If the nexus will stuck in bootloop, restore these files.
Edit: locksettings.db.... I need to verify this file... I'll give you an update about this file asap.
Click to expand...
Click to collapse
Hi again, so i tried the following steps and it booted up all fine and didnt ask me for a pattern! However when i try to change the sceen lock it crashes and says "unfortunately, settings has stopped". But atleast i can get into the phone now! Thanks so much for the help.

bobcee said:
Hi again, so i tried the following steps and it booted up all fine and didnt ask me for a pattern! However when i try to change the sceen lock it crashes and says "unfortunately, settings has stopped". But atleast i can get into the phone now! Thanks so much for the help.
Click to expand...
Click to collapse
Good! Now, if you find the clean version (without patterns) of these files, you are ok. You're welcome.

I've got the same problem, and the same solutions works (thanks @Giovix92)
But at the end of the process, I can not put another pattern or something else
So my phone is open to everybody => that's bad
Does some can provide a know gesture with both files (gatekeeper.password.key and gatekeeper.pattern.key) ?
please @bobcee , did you find a way ?
PS : my device is a Nexus 5X, under rooted MMB29Q

greee said:
I've got the same problem, and the same solutions works (thanks @Giovix92)
But at the end of the process, I can not put another pattern or something else
So my phone is open to everybody => that's bad
Does some can provide a know gesture with both files (gatekeeper.password.key and gatekeeper.pattern.key) ?
please @bobcee , did you find a way ?
PS : my device is a Nexus 5X, under rooted MMB29Q
Click to expand...
Click to collapse
You're welcome. You should get a nandroid backup of another Nexus 5X without pattern. Then use nandroid manager to manage the system.img file and extract the two files. Then reboot into TWRP and replace these files. And you are done.

boot Twrp run file manager
only delete locksettings.db in /data/system/locksettings.db
reboot and it works!
Heisenberg wrote:
"Note: If you happened to forget to remove lockscreen security (PIN/Pattern/Fingerprint) before creating your backup, and you cannot get into your OS after restoring, you can do the following to fix the issue. Boot into TWRP and use the built in file manager to delete /data/sytem/locksettings.db. This should be enough to get you into your OS again. If it isn't you can also try deleting /data/system/locksettings.db-shm and /data/system/locksettings.db-wal. If this still doesn't fix your issue you can delete /data/system/gatekeeper.password.key and /data/system/gatekeeper.pattern.key."

Giovix92 said:
You're welcome. You should get a nandroid backup of another Nexus 5X without pattern. Then use nandroid manager to manage the system.img file and extract the two files. Then reboot into TWRP and replace these files. And you are done.
Click to expand...
Click to collapse
Seems complicated, I really don't know where to get such files :crying:
And I think a pattern is now mandatory on Marshmallow setup, no ?
---------- Post added at 05:26 PM ---------- Previous post was at 05:05 PM ----------
I just find another way !
First I've asked for a device lock on android manager website https://www.google.com/android/devicemanager
Then after unlocking my Nexus 5X with the given password, I was able to change (parameters/security) to a new pattern.
Great !

glehel said:
boot Twrp run file manager
only delete locksettings.db in /data/system/locksettings.db
reboot and it works!
Heisenberg wrote:
"Note: If you happened to forget to remove lockscreen security (PIN/Pattern/Fingerprint) before creating your backup, and you cannot get into your OS after restoring, you can do the following to fix the issue. Boot into TWRP and use the built in file manager to delete /data/sytem/locksettings.db. This should be enough to get you into your OS again. If it isn't you can also try deleting /data/system/locksettings.db-shm and /data/system/locksettings.db-wal. If this still doesn't fix your issue you can delete /data/system/gatekeeper.password.key and /data/system/gatekeeper.pattern.key."
Click to expand...
Click to collapse
You should only delete gatekeeper.password.key and gatekeeper.pattern.key and you'll be able to enter in your phone. Isn't needed to delete locksettings.db and other.
---------- Post added at 05:02 PM ---------- Previous post was at 05:00 PM ----------
greee said:
Seems complicated, I really don't know where to get such files :crying:
And I think a pattern is now mandatory on Marshmallow setup, no ?
---------- Post added at 05:26 PM ---------- Previous post was at 05:05 PM ----------
I just find another way !
First I've asked for a device lock on android manager website https://www.google.com/android/devicemanager
Then after unlocking my Nexus 5X with the given password, I was able to change (parameters/security) to a new pattern.
Great !
Click to expand...
Click to collapse
Good! I explain the process: When you unlock the bootloader, all your files will be deleted because the operation works as the factory reset. In fact: Unlock BL=Factory reset. Doing a factory reset=Restore ALL system files.

Giovix92 said:
You should only delete gatekeeper.password.key and gatekeeper.pattern.key and you'll be able to enter in your phone. Isn't needed to delete locksettings.db and other.
---------- Post added at 05:02 PM ---------- Previous post was at 05:00 PM ----------
Good! I explain the process: When you unlock the bootloader, all your files will be deleted because the operation works as the factory reset. In fact: Unlock BL=Factory reset. Doing a factory reset=Restore ALL system files.
Click to expand...
Click to collapse
I just tried it and it was good as I wrote.

glehel said:
I just tried it and it was good as I wrote.
Click to expand...
Click to collapse
Bho. Sincerely, I had a Nexus 5X, hardbricked by a error of locking bl (CM11, my mistake), now i have a cheap SM-G350 aka Core Plus with CM11. I remember that is needed only delete these files, and not locksettings. But, if you say that lock... should be deleted, ok man )

greee said:
Seems complicated, I really don't know where to get such files :crying:
And I think a pattern is now mandatory on Marshmallow setup, no ?
---------- Post added at 05:26 PM ---------- Previous post was at 05:05 PM ----------
I just find another way !
First I've asked for a device lock on android manager website https://www.google.com/android/devicemanager
Then after unlocking my Nexus 5X with the given password, I was able to change (parameters/security) to a new pattern.
Great !
Click to expand...
Click to collapse
I was not able to set a pattern lock after deleting the 2 files. But i just wanted to get into the phone so that i could backup apps using titanium backup. I factory reset, which fixed the patten lock issue, and restored my apps.

Did you already tried this??
The easy way to fix that issue:
1) Restore from Nandroid Backup
2) Go into ADB and use the following commands:
rm /data/system/locksettings.db
rm /data/system/*.key
Or delete them via the TWRP Filemanager
3) Boot and voila!
Note, it is recommended for you to restore your pin code afterwords.

Vulkaistos said:
Did you already tried this??
The easy way to fix that issue:
1) Restore from Nandroid Backup
2) Go into ADB and use the following commands:
rm /data/system/locksettings.db
rm /data/system/*.key
Or delete them via the TWRP Filemanager
3) Boot and voila!
Note, it is recommended for you to restore your pin code afterwords.
Click to expand...
Click to collapse
He already deleted these files by my steps, he don't need to redelete it.

Ooh didnt saw that
Gesendet von meinem Nexus 5X mit Tapatalk

Vulkaistos said:
Ooh didnt saw that
Gesendet von meinem Nexus 5X mit Tapatalk
Click to expand...
Click to collapse
Ohh my bad xD

glehel said:
boot Twrp run file manager
only delete locksettings.db in /data/system/locksettings.db
reboot and it works!
Heisenberg wrote:
"Note: If you happened to forget to remove lockscreen security (PIN/Pattern/Fingerprint) before creating your backup, and you cannot get into your OS after restoring, you can do the following to fix the issue. Boot into TWRP and use the built in file manager to delete /data/sytem/locksettings.db. This should be enough to get you into your OS again. If it isn't you can also try deleting /data/system/locksettings.db-shm and /data/system/locksettings.db-wal. If this still doesn't fix your issue you can delete /data/system/gatekeeper.password.key and /data/system/gatekeeper.pattern.key."
Click to expand...
Click to collapse
This has worked well for me. i was able to bypass pattern security screen and reset a new one without any problems.
Thanks

For me, when deleting the "*.key" files I cannot set a new pattern as the system config craches.
When deleting "locksettings.db" I can set a new pattern but I lost the smart lock features.
I did not find any other sollution until now.
Will just Titanium Backup everything and format the phone.

A request to official/unofficial TWRP developers

Hi All!
As plenty of people know by now that the latest modified twrp that we have does not work with encrypted storage when flashing official nougat oos. And there must be many people like me who due to reasons dont have time to copy n move everything back or don't want to decrypt their storage. So me and all of op3 community would appreciate if anyone can take some time out of their schedule and build an updated twrp version so that we can flash official nougat without screwing with storage or encryption. Because nougat is the future now and we'll start receiving nougat update from now onwards. And its a shame tha such an active dev device like op3 does not even have an updated twrp version. Thanks!

+1

A reason for this issue is probably OnePlus not releasing any Kernel Source code yet.
https://github.com/OnePlusOSS/android_kernel_oneplus_msm8996/issues/27
eng.stk was releasing a couple twrp mods but doing so is a pita with users on your back who constantly want 247 support.

AcmE85 said:
A reason for this issue is probably OnePlus not releasing any Kernel Source code yet.
https://github.com/OnePlusOSS/android_kernel_oneplus_msm8996/issues/27
eng.stk was releasing a couple twrp mods but doing so is a pita with users on your back who constantly want 247 support.
Click to expand...
Click to collapse
Totally agree to that. I was also assuming that an updated kernel sources are required to build a compatible twrp recovery for nougat. Waiting eagerly for the same. And considering the feedback of people on official OOS, i don't feel it's really a must have update as of now.
I also agree to the point about users. People need to stop taking developers for granted, and give them their space to release updates, and they should understand the dev is doing this in his/her free time not as a full time job. I hope we'll see an updated TWRP soon. Until then, MM is serving me well. No hurry

He is only asking, stop crying dude
To many ladies with balls here

fanbogo said:
He is only asking, stop crying dude
To many ladies with balls here
Click to expand...
Click to collapse
Sorry for the confusion what is it intended for me?

TWRP password, please help.
As first i wasn't able to flash any twrp files at all as after flashing it shows some black screen so not even from the official TWRP site the files were helpful, then after ages of serching I found some thread in XDA where a guy posted the link to this twrp https://forum.xda-developers.com/on...nity-build-t3461648/post68691560#post68691560, then I was able to successfully install it and boot into TWRP recovery.
So here I am now stuck with the ****** password to decrypt data and I simply want to root my OP 3 but due to this situation I am unable to so any solutions on this will be much helpful and any way to remove the dumb password for the TWRP.
Thanks.

Dude even if twrp shows encrypted you can still flash supersu. Just mount the /system partition in Mount options and flash supersu via otg.

Dude that is a mess n upon that I don't have otg, and really isn't there any way for this to encryption to get decrypt ?

samyj22 said:
Dude that is a mess n upon that I don't have otg, and really isn't there any way for this to encryption to get decrypt ?
Click to expand...
Click to collapse
You can flash SuperSU without TWRP being able to decrypt your DATA partition:
- Boot into TWRP
- cancel the password prompt
- push the supersu.zip to your phone via adb push supersu.zip / (notice the blank between zip and /!).
- go to INSTALL, navigate to the root directory and flash it
- reboot
Worked without issues on my device.

samyj22 said:
Dude that is a mess n upon that I don't have otg, and really isn't there any way for this to encryption to get decrypt ?
Click to expand...
Click to collapse
Connect your phone to your pc, boot TWRP via fastboot from the PC and flash SuperSu via adb under advanced in TWRP.
Gesendet von meinem ONEPLUS A3003 mit Tapatalk

AcmE85 said:
You can flash SuperSU without TWRP being able to decrypt your DATA partition:
- Boot into TWRP
- cancel the password prompt
- push the supersu.zip to your phone via adb push supersu.zip / (notice the blank between zip and /!).
- go to INSTALL, navigate to the root directory and flash it
- reboot
Worked without issues on my device.
Click to expand...
Click to collapse
Didn't knew that at all part from ya we can push files via side load, but just to confirm my internal storage shows as 0mb as it is encrypted n even if I push the files to internal storage so just wanted to make sure will it show up in two file manager?
Next thing so if I have any ROM files to flash can they be pushed as well with the command adb push file.zip /right?
N yah I have to enter sideload mode for this right.

samyj22 said:
Didn't knew that at all part from ya we can push files via side load, but just to confirm my internal storage shows as 0mb as it is encrypted n even if I push the files to internal storage so just wanted to make sure will it show up in two file manager?
Next thing so if I have any ROM files to flash can they be pushed as well with the command adb push file.zip /right?
N yah I have to enter sideload mode for this right.
Click to expand...
Click to collapse
I just booted into twrp, canceled the password prompt and pushed the file while being in the main menu.
The file will be stored in your devices root folder, not "internal storage" or "sdcard".
So when you go to "install", you have to go all the way up your folder structure. This is were you will find the supersu.zip.

AcmE85 said:
You can flash SuperSU without TWRP being able to decrypt your DATA partition:
- Boot into TWRP
- cancel the password prompt
- push the supersu.zip to your phone via adb push supersu.zip / (notice the blank between zip and /!).
- go to INSTALL, navigate to the root directory and flash it
- reboot
Worked without issues on my device.
Click to expand...
Click to collapse
Can we perform an adb sideload rather than adb push to directly flash SuperSU zip? Or does sideload only works for rom zips?

AcmE85 said:
I just booted into twrp, canceled the password prompt and pushed the file while being in the main menu.
The file will be stored in your devices root folder, not "internal storage" or "sdcard".
So when you go to "install", you have to go all the way up your folder structure. This is were you will find the supersu.zip.
Click to expand...
Click to collapse
Just a little confusion, as the internal storage is the same as root directory or the one level back to the SD card is the root directory?

abhibnl said:
Can we perform an adb sideload rather than adb push to directly flash SuperSU zip? Or does sideload only works for rom zips?
Click to expand...
Click to collapse
Yes you can directly sideload.

Bro just need confirmation on the commands for the push and sideload as well correctly, that will be really helpful...... ?

samyj22 said:
Bro just need confirmation on the commands for the push and sideload as well correctly, that will be really helpful......
Click to expand...
Click to collapse
Mount system in recovery,
adb sideload sample.zip
adb push <source-path> <target-path>
If file is in the adb folder already, then
adb push sample.zip /system or whatever path you want to send it to.
Edit: While pushing, make sure you mount system as RW first. But i guess when you mount system in TWRP, it's automatically in RW mode. But please do check with someone who has done it or an expert. I have limited knowledge, so sharing as far as i know

abhibnl said:
Mount system in recovery,
Click to expand...
Click to collapse
Hello thank you, but in twrp i can't mount /system
in mount i can select system but i have
Decrypt data
Select Storage
Disable/enable MTP.

acetone802000 said:
Hello thank you, but in twrp i can't mount /system
in mount i can select system but i have
Decrypt data
Select Storage
Disable/enable MTP.
Click to expand...
Click to collapse
Do you have all those 3 options in the mount menu? I don't think that should be there. I'm sorry, your statement is a bit unclear actually.

Offical update to Nougat for N920A step by step. Enjoy !!!!

From The Moderator Oka1 - There are no viable links in this OP therefore, I am closing
Thanks
OK. As i promise to some nice people here, then i get it so here it is.
ADB sideload only update S4CQB2-to-U4EQC6. 1.41 GB file seems to me like nougat update.
Nougat Update Here S4CQB2-to-U4EQC6
MD5 checksum : 903aa5c5f26f430133481c4a2cfcdb69
Thanks for ABD instruction @ColoMtn
Make sure you know how to ADB sideload. I'm not responsible for any damage to your phone.
Steps:
1. Backup everything of importance on your phone!!!
2. Now, make sure you have "show file extension" enabled in Windows, and file is ready for ADB as you download SS-N920AUCS4CQB2-to-U4EQC6-UP.zip
3. Shutdown your phone
4. Enter recovery mode by pressing volume up, home and power button together
* A green Droid will appear on screen with the text Installing system update…
5. Using the Volume Button Navigate and the Power button to select ‘Apply Update from ADB’
6. Connect your phone via USB to your computer
7. Open a CMD prompt from your PC. Type cd
in my case: cd C:\Users\Norbarb\Desktop\Note5
8. Navigate to the directory that contains the update ‘SS-N920AUCS4CQB2-to-U4EQC6-UP.zip’
*Note I had issue when the directory contained a space. Moving the update to a directory with no spaces resolved the issue.
Also moved the adb driver to the same directory 'C:\Users\Norbarb\Desktop\Note5'
9. Type adb devices. You should see 1 device listed
10.Type adb sideload SS-N920AUCS4CQB2-to-U4EQC6-UP.zip
11. This took around 25 minutes to complete
12. Phone will now be updated Nougat
EDIT: Please post mirrors if you can. Thanks
For who may need it this is S4CQA1 to U4QC6 update. File is around 1.5 GB and MD5 is 23d4d4c58330b618001e76fc468732d9

Congratulations! Hopefully 928a will have it soon

vista1984 said:
Congratulations! Hopefully 928a will have it soon
Click to expand...
Click to collapse
You are talking about G928A ? I check but only what i get is security update to 4CQB1. If you want i can post it on S6E+ forum.

I just wanted to thank you for this, going to do it now!!!! This day keeps getting better and better!!!!!

norbarb said:
OK. As i promise to some nice people here, then i get it so here it is.
ADB sideload only update S4CQB2-to-U4EQC5. 1.41 GB file seems to me like nougat update.
Nougat Update Here
Thanks for ABD instruction @ColoMtn
Steps:
1. Backup everything of importance on your phone!!!
2. Now, make sure you have "show file extension" enabled in Windows, and file is ready for ADB as you download SS-N920AUCS4CQB2-to-U4EQC5.zip
3. Shutdown your phone
4. Enter recovery mode by pressing volume up, home and power button together
* A green Droid will appear on screen with the text Installing system update…
5. Using the Volume Button Navigate and the Power button to select ‘Apply Update from ADB’
6. Connect your phone via USB to your computer
7. Open a CMD prompt from your PC. Type cd
in my case: cd C:\Users\Norbarb\Desktop\Note5
8. Navigate to the directory that contains the update ‘SS-N920AUCS4CQB2-to-U4EQC5.zip’
*Note I had issue when the directory contained a space. Moving the update to a directory with no spaces resolved the issue.
Also moved the adb driver to the same directory 'C:\Users\Norbarb\Desktop\Note5'
9. Type adb devices. You should see 1 device listed
10.Type adb sideload SS-N920AUCS4CQB2-to-U4EQC5.zip
11. This took around 25 minutes to complete
12. Phone will now be updated Nougat
EDIT: Please post mirrors if you can. Thanks
Click to expand...
Click to collapse
Can anyone show a screen shot of the "About Device" section of the phone settings after applying this update? Thank you in advance!

Have you tried it yourself?I got this in recovery when adb it.
" failed to verify whole-file signature", "signature verification failed
"E:failed to verify whole-life signature" "E:signature verification failed"
Installation aborted.

ifanr said:
Have you tried it yourself?I got this in recovery when adb it.
" failed to verify whole-file signature", "signature verification failed
"E:failed to verify whole-life signature" "E:signature verification failed"
Installation aborted.
Click to expand...
Click to collapse
On what firmware currently are you? This update is only from baseband N920AUCS4CQB2. Also you may have corrupted recovery. To fix this you have to ODIN back to latest firmware and try again.
Anyway just in case i'm uploading raw file w/o .zip extension to another place.

norbarb said:
On what firmware currently are you? This update is only from baseband N920AUCS4CQB2. Also you may have corrupted recovery. To fix this you have to ODIN back to latest firmware and try again.
Anyway just in case i'm uploading raw file w/o .zip extension to another place.
Click to expand...
Click to collapse
It's S4CQB2.Could you please give me the md5?And I'm gonna to flash the recovery to work it out.

ifanr said:
It's S4CQB2.Could you please give me the md5?And I'm gonna to flash the recovery to work it out.
Click to expand...
Click to collapse
I post it MD5 in first post.

norbarb said:
I post it MD5 in first post.
Click to expand...
Click to collapse
Matched.I'll try some other ways to work it out.Tks.

ifanr said:
Matched.I'll try some other ways to work it out.Tks.
Click to expand...
Click to collapse
You may try removing .zip extension and try again. Sometimes works

i get cannot read SS-N920AUCS4CQB2-to-U4EQC5.zip

jerrycoffman45 said:
i get cannot read SS-N920AUCS4CQB2-to-U4EQC5.zip
Click to expand...
Click to collapse
Two resons :
1. corrupted file
2. file in wrong place

norbarb said:
Two resons :
1. corrupted file
2. file in wrong place
Click to expand...
Click to collapse
The file may corrupted.When I use winrar to unzip this file.It says there is a checksum error occurred in system\priv-app\Lookout_ATT\oat\arm\Lookout_ATT.odex. The file is corrupt.
I tried your ways but did not work out.

norbarb said:
Two resons :
1. corrupted file
2. file in wrong place
Click to expand...
Click to collapse
thats what i thought too but md5 checks and the files in the same folder as adb and fastboot

ifanr said:
The file may corrupted.When I use winrar to unzip this file.It says there is a checksum error occurred in system\priv-app\Lookout_ATT\oat\arm\Lookout_ATT.odex. The file is corrupt.
I tried your ways but did not work out.
Click to expand...
Click to collapse
I post it link to raw file try other one or re-download.

ifanr said:
The file may corrupted.When I use winrar to unzip this file.It says there is a checksum error occurred in system\priv-app\Lookout_ATT\oat\arm\Lookout_ATT.odex. The file is corrupt.
I tried your ways but did not work out.
Click to expand...
Click to collapse
jerrycoffman45 said:
thats what i thought too but md5 checks and the files in the same folder as adb and fastboot
Click to expand...
Click to collapse
Most of the time it is problem do to recovery. You may have to ODIN firmware back and try again.
Anybody flash this file w/o problems? I'm sorry but only Note 5 i have it is my wife's work phone and i can't mess with it.

norbarb said:
Most of the time it is problem do to recovery. You may have to ODIN firmware back and try again.
Anybody flash this file w/o problems? I'm sorry but only Note 5 i have it is my wife's work phone and i can't mess with it.
Click to expand...
Click to collapse
I'll try it. Looks I already messed up my phone.Lucky it's weekend.lol.

ifanr said:
I'll try it. Looks I already messed up my phone.Lucky it's weekend.lol.
Click to expand...
Click to collapse
ALL WHO TRY PLEASE STOP. Seems like uploaded file got corrupted. I'm uploading once more

norbarb said:
You are talking about G928A ? I check but only what i get is security update to 4CQB1. If you want i can post it on S6E+ forum.
Click to expand...
Click to collapse
It's very thoughtful of you. If you have time please post it at your convenience.

Prevent installation (Redmi Note 5 AI Global)

Hi folks,
I got my RN5 AI Global a couple of days ago and I want to give Lineage OS a spin. Then I read about this dreaded feature of Google called "ARB" - a developer's nightmare!
My current version is 9.5.17 on my phone. When I change into settings I can see that 9.5.19 has been downloaded and is ready for installation, the only action I have to do is reboot. Since 9.5.19 carries ARB feature, I do not power down my phone in order not to install this fix.
So guys, here is my question: Is there any way I can prevent this update from installing on my phone?
Best wishes,
DFahren

Don't install it?
Just power down and go straight to fastboot (power+voldown) then use mi unlock to unlock then flash lineage after doing twrp.
Not that it would matter too much having 9.5.19 since you can bypass it blocking fastboot commands with the arbypass.img file

Nice idea. However my Mi account is not (yet) eligible for unlocking .... This will take 14 days, I suppose.

Delete the update from internal storage/downloaded_rom
And also turn off automatic updates so you don't get it again.
"If you are on MIUI 9, then:
- Go to Settings
- About Phone
- System Updates
- Click on 3 dots above right
- Turn Off both "Download Automatically" and "Download using Mobile Data"."
And you should be able to reboot your device.

Ok, what you are basically saying is: open a CMD on Windows, issue an "adb shell" and in this shell do a "cd xxx/storage/downloaded_rom; rm *", right?!
I have to do this because I do not see this folder downloaded_rom when using MIUI's filemanager. Correct?
Cheers, Dfahren
corkiejp said:
Delete the update from internal storage/downloaded_rom
And also turn off automatic updates so you don't get it again.
"If you are on MIUI 9, then:
- Go to Settings
- About Phone
- System Updates
- Click on 3 dots above right
- Turn Off both "Download Automatically" and "Download using Mobile Data"."
And you should be able to reboot your device.
Click to expand...
Click to collapse

@dfahren
Maybe try a different file manager than stock.
Someone else reported on another forum that they deleted the downloaded update.
Not sure how exactly, I will message them and find out how.

dfahren said:
Ok, what you are basically saying is: open a CMD on Windows, issue an "adb shell" and in this shell do a "cd xxx/storage/downloaded_rom; rm *", right?!
I have to do this because I do not see this folder downloaded_rom when using MIUI's filemanager. Correct?
Cheers, Dfahren
Click to expand...
Click to collapse
corkiejp said:
@dfahren
Maybe try a different file manager than stock.
Someone else reported on another forum that they deleted the downloaded update.
Not sure how exactly, I will message them and find out how.
Click to expand...
Click to collapse
I deleted the update zip file using solid explorer.
Sent from my Redmi Note 5 using Tapatalk

....deleted ....

gsmyth said:
I deleted the update zip file using solid explorer.
Click to expand...
Click to collapse
Yeah, that's also a good way to get rid of the update.
I used ADB with installed drivers. However path to the update was ..../sdcard/downloaded_rom , but that's a minor. Just wanted to let you guys know.