Database Users

Nexus 6p stuck on Google screen during boot due to replacing build.prop

I Replaced the build.prop on my rooted Google nexus 6p running Android 7.0 with the build.prop file from the pixel to run Google Assistant.The phone is now stuck on the Google logo during boot,PLEASE HELP.

Did you make a backup copy of the file before replacing it, are you rooted, and have TWRP installed?
If so, reboot to recovery, use TWRP Terminal function to copy the backup of the build.prop to the modified one.

dratsablive said:
Did you make a backup copy of the file before replacing it, are you rooted, and have TWRP installed?
If so, reboot to recovery, use TWRP Terminal function to copy the backup of the build.prop to the modified one.
Click to expand...
Click to collapse
I did not make a back up but I am rooted and have Twrp installed.What can i do from here?

If you can boot to bootloader you should be able to replace the file with a standard one.

Alden1227 said:
I Replaced the build.prop on my rooted Google nexus 6p running Android 7.0 with the build.prop file from the pixel to run Google Assistant.The phone is now stuck on the Google logo during boot,PLEASE HELP.
Click to expand...
Click to collapse
same here please help.....freaking out

1. The build.prop contains the settings for a specific build for a specific phone. You can't just replace it from another build, not to mention another phone. Well, I guess, you already know this.
2. You should know exactly which build you were on. Exactly. Then:
* What I would do, is download the factory image from https://developers.google.com/android/nexus/images#angler
o Extract it, extract the image-angler-...zip, and mount the system.img, find the build.prop and adb push it to the phone.
o Reboot
* But you can also ask somebody who has the exact build as you do, and ask for the build.prop. Then push it to the phone.

Either restore from backup or edit the buildprop (if possible) I guess.
You only needed to edit 2 lines in the buildprop though, why replace the whole thing?

Alden1227 said:
I did not make a back up but I am rooted and have Twrp installed.What can i do from here?
Click to expand...
Click to collapse
First thing's first. Since you didn't just edit your build.prop, but replaced it with another, try setting permissions.
Step 1: Boot to TWRP > Mount > Select "System"
Step 2: Advanced > File Manager
Step 3: Navigate to /system/build.prop
Step 4: Select "chmod" and type "644" (don't include quotation marks)
Reboot and see if it works. If the permissions weren't right and you didn't change them, you'd most likely be in a boot loop. If this doesn't work you can just flash your system.img again. It won't wipe your internal storage, data (installed apps, etc.) If you have custom host files for ad blocking, you may need to apply them again.
If that does not work;
I'm going to assume you were on stock Nougat. Download the factory image (same build you were on before) and unzip the file. You'll end up with a folder with another zip archive in it. Unzip that as well. Inside you'll find a file named "system.img"
Move that system.img file to your ADB/fastboot folder. Shift+Right Click that folder and select "Open command window here"
Hold volume down + power to boot into the bootloader. Connect the phone to the PC and in the command prompt, type "fastboot devices" (no quotes again. ) It should show your devices serial number. If it does, perfect. If not, check your ADB/fastboot installation.
Once you get fastboot to show your serial number all you need to do is type;
Code:
fastboot flash system system.img
That should do it. If you need any more help, just reply back.
Edit: @istperson, AFAIK, you cannot pick out files from a .img file like that. When I right click it on my system and choose mount it tells me the image file is corrupted. Tried downloading again and hashes match. Windows 10. I use 7zip as well, and that can't open it either. Is there another program to use or is something whacky on my end? Wouldn't doubt it. Just took a Win10 update yesterday and it's been acting up on me all day. :/

RoyJ said:
Edit: @istperson, AFAIK, you cannot pick out files from a .img file like that. When I right click it on my system and choose mount it tells me the image file is corrupted. Tried downloading again and hashes match. Windows 10. I use 7zip as well, and that can't open it either. Is there another program to use or is something whacky on my end? Wouldn't doubt it. Just took a Win10 update yesterday and it's been acting up on me all day. :/
Click to expand...
Click to collapse
It's a sparse image, you have to convert it to normal mage with simg2img. Then you can mount it normally.

istperson said:
It's a sparse image, you have to convert it to normal mage with simg2img. Then you can mount it normally.
Click to expand...
Click to collapse
Awesome, thanks!

Fixed the issue
frreak said:
same here please help.....freaking out
Click to expand...
Click to collapse
I got mine to work by flashing Android 7.0

same thing happened to me.... stuck on google even after flashing stock....

dadoc04 said:
same thing happened to me.... stuck on google even after flashing stock....
Click to expand...
Click to collapse
Flash stock boot, system and vendor img files.
Sent from my Pixel XL using XDA-Developers mobile app

Same thing happened to me at first (though I did not use the build prop from a Pixel). I just dirty flashed my ROM (Octo N) and it then got passed the Google screen and loaded with no problem. I updated my build prop manually in order to get Google Assistant to work, and it's been working great ever since.

RoyJ said:
First thing's first. Since you didn't just edit your build.prop, but replaced it with another, try setting permissions.
Step 1: Boot to TWRP > Mount > Select "System"
Step 2: Advanced > File Manager
Step 3: Navigate to /system/build.prop
Step 4: Select "chmod" and type "644" (don't include quotation marks)
Reboot and see if it works. If the permissions weren't right and you didn't change them, you'd most likely be in a boot loop. If this doesn't work you can just flash your system.img again. It won't wipe your internal storage, data (installed apps, etc.) If you have custom host files for ad blocking, you may need to apply them again.
If that does not work;
I'm going to assume you were on stock Nougat. Download the factory image (same build you were on before) and unzip the file. You'll end up with a folder with another zip archive in it. Unzip that as well. Inside you'll find a file named "system.img"
Move that system.img file to your ADB/fastboot folder. Shift+Right Click that folder and select "Open command window here"
Hold volume down + power to boot into the bootloader. Connect the phone to the PC and in the command prompt, type "fastboot devices" (no quotes again. ) It should show your devices serial number. If it does, perfect. If not, check your ADB/fastboot installation.
Once you get fastboot to show your serial number all you need to do is type;
That should do it. If you need any more help, just reply back.
Edit: @istperson, AFAIK, you cannot pick out files from a .img file like that. When I right click it on my system and choose mount it tells me the image file is corrupted. Tried downloading again and hashes match. Windows 10. I use 7zip as well, and that can't open it either. Is there another program to use or is something whacky on my end? Wouldn't doubt it. Just took a Win10 update yesterday and it's been acting up on me all day. :/
Click to expand...
Click to collapse
Chmod 755 worked too

*UPDATED**UNLOCK TOOL (4-2019) for ALL Versions of BLU R1-HD

BLU R1-HD bootloader unlock script tool, and TWRP install tool.
Download is a zip file, unpack it to somewhere you will remember. Run the dirty-cow-tool.bat // mtk-su-tool.bat
The included files and folders are set to hidden, in effort to keep them safe from accidental delete.
Must have adb+fastboot + drivers installed and setup prior to using tool
Easiest method to install adb + fastboot on windows is with "15 second adb + fastboot install TOOL"
LINK==>ADB+FASTBOOT
It is for windows
In linux :
"sudo apt-get install android-tools-adb"
"sudo apt-get install android-tools-fastboot" Some fastboot commands were missing when i used this one ie "fastboot flashing get_unlock_ability"
"sudo apt-get install fastboot" worked better when I tried. ( i used that command as a check before doing the unlock, so it was needed only for that check)
Using Tool
On Windows?
Unzip the downloaded file to a new folder, open new
folder and click on "dirty-cow-tool.bat". // "mtk-su-tool.bat"
Do the steps in order (1-2-3-4) to be unlocked, then
Step (5) to get to second page where step (1) is root
The rest is optional
On Linux?
Unzip downloaded file to new folder folder .
Open folder. Then open R1-Linux-tool-v2 folder
Open terminal from that folder and type
" . R1-HD-TOOL.sh "
Same order of steps (1,2,3,4) step (5) for extra
Steps (1 on second menu) for superSU root.
Second menu steps (2,3,4,5,6,7,8) are optional.
**Linux Note**
The tool uses "fastboot flashing get_unlock_ability" as one of the methods to check before doing the unlock.
The version of fastboot that installed with "apt-get install android-tools-fastboot" did not recognize
this command. But "apt-get install fastboot" updated some version and then the command was recognized.
******OTHER NOTES****
--- this has been mentioned in the general thread and the modified v17 thread, but It has come up again so I wanted to make note of it.----
--- The newest blu versions (V7.4.2 and V17) Have made changes to "toolbox" and this effects things like "adaway" and "titanium backup"
--- The suggested fix is to install busy-box. I have had success with the version from play store, some prefer to use f-droid version. Either one will do. Install it and open the app. From in the app you need to do an install.
CHANGE LOG
V1:. Initial release : removed
V2:. : fixed typos preventing proper function
V3:.: switch file verification to md5 check instead of "ls-l" comparison.
V4: current version: add extras page, add SU flash, de-bloat script, Added Fm Radio, Added pre-loader roll back
V5: Fixed wrong loop "goto" line that made preloader rollback do "MTK_BLU Debloat v2" instead
V6: Added manual pause to script for mods that need recovery (Extra's 5) . Added redundent recovery flash command .
Few reports of recovery "not Sticking" and needed to run the flash commands manually one by one. Maybe the redundent
flash will make it survive. If still having problem with recovery "staying install" try manually flashing
here is link to the steps needed. FLASH RECOVERY
V7 Improved logs Added line to make batch run as sub-process so if error occurs , will not close
V7.1 : Updated the fm radio install zip and include the needed selinux mode changer app
V8: fixed dependency of needing to be unzipped to location w/o spaces in name. (when used from location with spaces, tool used to fail to push needed files).
.. added more time to allow dirtycow to "spawn" its root shell. Recent testing has shown sometimes it takes longer than the 60 seconds allowed in the script. Now it is looped 3 times.
V9 Added full path to abd push lines for recovery flash files. included fastboot.exe file to address some version issue where user s version would not output text file I coded into script for a verification ( included file is called by script, no need to do anything different with it)
V10: Moved zip file to included folder to help preserve locations when unpacked, added device check before running tool; So tool not used on wrong device, Rearranged order of operations on extra's page. (recovery installed options) Push files while in android before rebooting to recovery( should improve reliability for multiple reports of not automatically installing options for some)
******I have received some reports that some devices are reporting "ro.build.product =R1_HD and not "BLU_R1_HD" like mine, so the added device check is blocking tool from starting If this happens to you , you can make edit to the .bat file like below.
Change this line
Code:
:next_check
find "BLU_R1_HD" "%~dp0workingproduct.txt"
To this
Code:
:next_check
find "R1_HD" "%~dp0workingproduct.txt"
it is line #23
V11: Updated device model verification lines
MTK-SU: Replaced all dirty-cow part with New MTK-SU binary(elf) from @diplomatic
source
Click to expand...
Click to collapse
Credits to @Diplomatic for his work on the Mtk_su that I used used to make this tool work again after Dirty-Cow was patched.
DOWNLOAD LINK
Preferred to use the Downloads tab of this thread.
Archived downloads on android file host also == link
XDA:DevDB Information
R1-HD Dirty-cow Unlock Tool, Tool/Utility for the BLU R1 HD
Contributors
mrmazak, vampirefo for his recovery, lopestom for his recovery, emc2cube for his debloat zips, christianrodher for his dirtycow method,
Source Code: https://github.com/mrmazakblu/DirtyCow-R1_HD
Version Information
Status: Testing
Current Stable Version: V11
Stable Release Date: 2017-04-11
Current Beta Version: MTK-SU
Beta Release Date: 2019-04-14
Created 2017-02-22
Last Updated 2019-04-18

Reserved
Items planed to be addressed in next release:
--Add few more file integrity checks to the extra's page
--Add copy log to clipboard option so it is easier to post log entry if needed-------*********----already-_added to github copy of batch file
--Add a verification step that checks what recovery is installed( to prevent trying to do steps on extra's page with stock recovery)
--Possibly move to a "fastboot boot recovery" instead of "adb reboot recovery" for the same reason as above
--Add wget or similar to the extra's items so initial "TOOL" size is smaller (not that 40-50MB is big, but to some it may be )
--Add additional "selinux mode changer apk" for fm radio install rather than just the note that says it needs to be found.

Reserved

Works great on OEM 6.6, thanks for the tool!

So I got the one-click-root.sh done, maybe. Can some linux users go over it, make sure I didn't do anything stupid? I don't exactly have a device to check it with atm, and I am not pro with scripting, barely novice, so it is a pretty basic conversion of the batch file. Still, it might work . Just would like a few eyes on first.
https://github.com/theredbaron1834/Scripts/blob/master/one-click-root.sh
Also, I looked at dirty-cow-tool.bat. However, wow, more an advanced batch file, and I am not sure what the first half does, so not sure how to convert . However, it seems if anyone does get it, the eqiv of goto for linux is funtions. simple cheatsheet:
Code:
function stuff {
echo "this stuff is run via the function"
{
stuff #goes to stuff and runs function

theredbaron1834 said:
So I got the one-click-root.sh done, maybe. Can some linux users go over it, make sure I didn't do anything stupid? I don't exactly have a device to check it with atm, and I am not pro with scripting, barely novice, so it is a pretty basic conversion of the batch file. Still, it might work . Just would like a few eyes on first.
https://github.com/theredbaron1834/Scripts/blob/master/one-click-root.sh
Also, I looked at dirty-cow-tool.bat. However, wow, more an advanced batch file, and I am not sure what the first half does, so not sure how to convert . However, it seems if anyone does get it, the eqiv of goto for linux is funtions. simple cheatsheet:
Code:
function stuff {
echo "this stuff is run via the function"
{
stuff #goes to stuff and runs function
Click to expand...
Click to collapse
thank you for your input.
As far as the begining of the batch, It is adding a few folders to the "path" variable so help ensure the "adb push" commands find the files it is trying to push. Then it sets some folder "flags" to hidden so that the files the batch needs don't get accidentally moved or changed. Then the large section with mostly "echo" that is to set up the "simulated" G.U.I.
The lines of just "::::::::::" are simply used to help with reading the batch file. i use them to seperate functions. They are not needed.
The lines with only 2 "::" are standard windows comment / remark line entries
The lines with 1 ":" are the beginning line of the loop/ function == the line that "goto *" searches for

Does Works to unlock 7.4.2?

khyr said:
Does Works to unlock 7.4.2?
Click to expand...
Click to collapse
It is supposed to. It is the same base codes used from original script, and that one was confirmed to work. I Do not have first hand use of V7.4.2 so it is only confirmed through other users.
The dirty-cow being used has been patched by google in Dec but blu has not rolled out the patch. So there is no reason for it not to work.

edit:
I have the linux version ready.
-the first step, (ADB Push) is ready. including md5 file checks
-step 2 is ready= running dirty-cow with md5 check before final writing to mmcblk device
-step 3 is ready unlocking bootloader = including check if unlock is done, but need to fix the "unlock_adility" check
I can make to file to compare and grep the line needed, but cannot "sed" the extra information or do a > < comparison
-step 4 is ready .--flash twrp
Finished 90% of tool.
still need to tweek the log feature.
I ran tests on the lop back to menu and test ran
1. push files for dirty-cow and md5 check . then made push fail to verify the check method was valid ==pass
2. run dirty cow commands and md5 verification on resulting file. ==pass
3.unlock bootloader --- I ran it (needed to fake the already unlocked check) it works == pass
4 . flash twrp --installed both version i have, both install fine ===pass
5 extra menus -- ran . install su-----debloat---rebloat--- add fm radio--- preloader roll back =====all pass
(bootloader roll back needs manual intervention to re-enter fastboot during the boot loop that is unavoidable)
6. instruction ====not written yet
7. exit yes it closes == pass
8. logs --- needs completeing

I just loaded this on my OTA updated 7.4.2 device. I would note that the batch file does not actually create the /sdcard/Download folder so you might need to go into the terminal and actually create this on your sdcard... also worth noting that this batch file **requires** an sd card in the device to do any of the loads in the "5" menu.

torchredfrc said:
I just loaded this on my OTA updated 7.4.2 device. I would note that the batch file does not actually create the /sdcard/Download folder so you might need to go into the terminal and actually create this on your sdcard... also worth noting that this batch file **requires** an sd card in the device to do any of the loads in the "5" menu.
Click to expand...
Click to collapse
no it does not.
the /sdcard is the internal memory and the Download folder is already there.
you might be having issues but the folder is already part of normal system

mrmazak said:
no it does not.
the /sdcard is the internal memory and the Download folder is already there.
you might be having issues but the folder is already part of normal system
Click to expand...
Click to collapse
Fair enough, my restore didn't have /sdcard/Download and I made an assumption that /sdcard was my mounted card. Thanks for the insight.

OOPS
found typo on V4 of tool. batch files sets variables for "return", from loop functions. And two returns were set to same label9, so if you had tried to do extra's menu option #8. "ROLL Back Preloader" , instead it was running option # 5. " MTK_BLU Debloat v2"
fixed and still reading and re-reading to search for errors.
This looks bad.
The reason I put together this tool was I felt it was important to make a way to minimize the problems usually associated with android modifications. By making "typo's" a thing of the past, and I found them in my own script.
re-posted V5 combined with linux V2--

torchredfrc said:
I just loaded this on my OTA updated 7.4.2 device. I would note that the batch file does not actually create the /sdcard/Download folder so you might need to go into the terminal and actually create this on your sdcard... also worth noting that this batch file **requires** an sd card in the device to do any of the loads in the "5" menu.
Click to expand...
Click to collapse
I'm a total noob, and I'd like to know how to proceed with the supersu and all the other parts of step 5. Thank you

gabriel986 said:
I'm a total noob, and I'd like to know how to proceed with the supersu and all the other parts of step 5. Thank you
Click to expand...
Click to collapse
Ok. After you have completed upto twrp install. You can do the options on #5. It is all programed and automatic. What is does is put zip files onto the phone and reboots phone into recovery, then recovery installs them.

mrmazak said:
Ok. After you have completed upto twrp install. You can do the options on #5. It is all programed and automatic. What is does is put zip files onto the phone and reboots phone into recovery, then recovery installs them.
Click to expand...
Click to collapse
I get up to the recovery installation, but then I can not access such recovery on the phone, If I turn it on with power+vol up, it takes me to the default factory recovery by blu.
And If I try to the super su step with the phone on, it resets it, and get it to the screen with the dead android, while the script just shows the ADB DETECTED message.
In case it's needed, my R1 HD is running on
BLU_R0010UU_V7.4.2_GENERIC 09-11-2016 13:38

gabriel986 said:
I get up to the recovery installation, but then I can not access such recovery on the phone, If I turn it on with power+vol up, it takes me to the default factory recovery by blu.
And If I try to the super su step with the phone on, it resets it, and get it to the screen with the dead android, while the script just shows the ADB DETECTED message.
Click to expand...
Click to collapse
You missed a step in the process.
As tool finishes the recovery install it comes to a "pause" in the script, you need to hold the volume up button on phone "before" pressing button on pc keyboard to continue.
If phone does a normal reboot at this point then the system will replace the newly installed recovery with the stock one.
Giving you the situation you have now.
This step I cannot control, you must press volume button on phone to get the boot menu, and directly boot into recovery to ensure that the install sticks.

mrmazak said:
You missed a step in the process.
As tool finishes the recovery install it comes to a "pause" in the script, you need to hold the volume up button on phone "before" pressing button on pc keyboard to continue.
If phone does a normal reboot at this point then the system will replace the newly installed recovery with the stock one.
Giving you the situation you have now.
This step I cannot control, you must press volume button on phone to get the boot menu, and directly boot into recovery to ensure that the install sticks.
Click to expand...
Click to collapse
trying again....
for how long should I press the volume up key?

gabriel986 said:
trying again....
for how long should I press the volume up key?
Click to expand...
Click to collapse
When tool says Hold button , keep it held. Then continue the script. Phone should reboot to the boot menu. Then let go of volume
Some phones do not accept the fastboot reboot command, on those phones need to hold power to shut off. Then volume and power together to come on, release power when screen come on

mrmazak said:
When tool says Hold button , keep it held. Then continue the script. Phone should reboot to the boot menu. Then let go of volume
Some phones do not accept the fastboot reboot command, on those phones need to hold power to shut off. Then volume and power together to come on, release power when screen come on
Click to expand...
Click to collapse
ok.. trying again
---------- Post added at 02:00 PM ---------- Previous post was at 01:46 PM ----------
gabriel986 said:
trying again....
for how long should I press the volume up key?
Click to expand...
Click to collapse
it beat me!
I get stuck in that part of the process, If anyone uploads a video to check what i'm doing wrong, I'll be grateful.

Eunavi head unit t8 android 8.1 root of stock rom

Some one can helpme about root recovery mode or stock rom.install.
Because i want to install official tomtom go.
Its not in play store.
I tried many thinks but not success

ufoss said:
Some one can helpme about root recovery mode or stock rom.install.
Because i want to install official tomtom go.
Its not in play store.
I tried many thinks but not success
Click to expand...
Click to collapse
I'm currently trying to get firmware for my Eunavi radio direct from Eunavi but am struggling at the moment. I will let you know if I do get it.

thanks

No answer?

ufoss said:
Some one can helpme about root recovery mode or stock rom.install.
Because i want to install official tomtom go.
Its not in play store.
I tried many thinks but not success
Click to expand...
Click to collapse
Hey. Here is the firmware for your HU.
https://drive.google.com/file/d/1DrxnbYQeyid7gNZWPFC8TsrX65cwxNSh
How to get root:
Enter the engineering menu. Record or photograph all settings!
Install Magisk manager on HU.
Extract firmware from archive to folder.
Take the file boot.img from firmware.
Patch boot.img using Magisk manager.
Replace the original boot.img with the patched boot.img (name must remain "boot.img").
Open the folder with the firmware.
Select everything in the folder and zip it (Do not archive the folder with the firmware!).
Rename zip archive to update.zip.
Need to sign the firmware
1. Install the latest jre from java.com (reboot may be required).
2. Extract files from the SingApkV2.zip archive. https://yadi.sk/d/HkS6APFt3Sb4Ek
3. Place update.zip in the same folder.
4. Run SingerScript.bat
Copy update_signed.zip to usb flash drive (format must be a FAT32) and rename to os_update.zip
Start the engine. Turn on HU. Wait for the HU to boot.
Insert usb flash drive.
Agree to update.
Wait for the update to complete (Do not touch anything! Do not stop the engine!). HU will reboot itself. Be patient. It will take a lot of time.
The first start after reboot lasts about 15 minutes!
At one's own risk.
I do not have such a HU. If you get a brick, I don’t know what to do next ...

****-jones said:
Hey. Here is the firmware for your HU.
https://drive.google.com/file/d/1DrxnbYQeyid7gNZWPFC8TsrX65cwxNSh
How to get root:
Enter the engineering menu. Record or photograph all settings!
Install Magisk manager on HU.
Extract firmware from archive to folder.
Take the file boot.img from firmware.
Patch boot.img using Magisk manager.
Replace the original boot.img with the patched boot.img (name must remain "boot.img").
Open the folder with the firmware.
Select everything in the folder and zip it (Do not archive the folder with the firmware!).
Rename zip archive to os_update.zip.
Remove all from usb flash drives (format must be a FAT32).
Copy os_update.zip to usb flash drive.
Start the engine. Turn on HU. Wait for the HU to boot.
Insert usb flash drive.
Agree to update.
Wait for the update to complete (Do not touch anything! Do not stop the engine!). HU will reboot itself. Be patient. It will take a lot of time.
The first start after reboot lasts about 15 minutes!
At one's own risk.
I do not have such a HU. If you get a brick, I don’t know what to do next ...
Click to expand...
Click to collapse
Thansk for answer.. i did all steps but installation aborted... ( see attachment)
Also in recovery mode cannor chose other menu

ufoss said:
Thansk for answer.. i did all steps but installation aborted... ( see attachment)
Also in recovery mode cannor chose other menu
Click to expand...
Click to collapse
Try to sign the file os_update.zip
Use SingApkV2.zip
https://yadi.sk/d/HkS6APFt3Sb4Ek
You need to install JRE from java.com
In recovery, try using a usb keyboard or mouse. May not work...

****-jones said:
Try to sign the file os_update.zip
Use SingApkV2.zip
https://yadi.sk/d/HkS6APFt3Sb4Ek
You need to install JRE from java.com
In recovery, try using a usb keyboard or mouse. May not work...
Click to expand...
Click to collapse
Thanks but i dont now how to that..
has a instruction??

ufoss said:
Thanks but i dont now how to that..
has a instruction??
Click to expand...
Click to collapse
1. Install the latest jre from java.com (reboot may be required).
2. Extract files from the SingApkV2.zip archive.
3. Place os_update.zip in the same folder.
4. Run from the command line
Code:
java -jar signapkv2.jar -w -v testkey.x509.pem testkey.pk8 os_update.zip os_update_signed.zip
Or edit the SingerScript.bat file and execute it.
5. Copy os_update_signed.zip to usb flash drive and rename to os_update.zip
6. Try to flash.

****-jones said:
1. Install the latest jre from java.com (reboot may be required).
2. Extract files from the SingApkV2.zip archive.
3. Place os_update.zip in the same folder.
4. Run from the command line
Code:
java -jar signapkv2.jar -w -v testkey.x509.pem testkey.pk8 os_update.zip os_update_signed.zip
Or edit the SingerScript.bat file and execute it.
5. Copy os_update_signed.zip to usb flash drive and rename to os_update.zip
6. Try to flash.
Click to expand...
Click to collapse
Thanks a lot... mission completed
After signed. update success - root success

ufoss said:
Thanks a lot... mission completed
After signed. update success - root success
Click to expand...
Click to collapse
Is that the only way to install 3d-party apps not from the playstore? (want to install my own application)
Another question - does it have any API for developers that would allow to receive CAN messages and/or get the IGN signal?

Hi ****-jones!
Can you give me the link to download this Eunavi 913 head unit please. Thank you.
https://www.aliexpress.com/item/4000674983866.html?spm=2114.12010612.8148356.6.2edc363cb3o8df

****-jones said:
Hey. Here is the firmware for your HU.
https://drive.google.com/file/d/1DrxnbYQeyid7gNZWPFC8TsrX65cwxNSh
How to get root:
Enter the engineering menu. Record or photograph all settings!
Install Magisk manager on HU.
Extract firmware from archive to folder.
Take the file boot.img from firmware.
Patch boot.img using Magisk manager.
Replace the original boot.img with the patched boot.img (name must remain "boot.img").
Open the folder with the firmware.
Select everything in the folder and zip it (Do not archive the folder with the firmware!).
Rename zip archive to update.zip.
Need to sign the firmware
1. Install the latest jre from java.com (reboot may be required).
2. Extract files from the SingApkV2.zip archive. https://yadi.sk/d/HkS6APFt3Sb4Ek
3. Place update.zip in the same folder.
4. Run SingerScript.bat
Copy update_signed.zip to usb flash drive (format must be a FAT32) and rename to os_update.zip
Start the engine. Turn on HU. Wait for the HU to boot.
Insert usb flash drive.
Agree to update.
Wait for the update to complete (Do not touch anything! Do not stop the engine!). HU will reboot itself. Be patient. It will take a lot of time.
The first start after reboot lasts about 15 minutes!
At one's own risk.
I do not have such a HU. If you get a brick, I don’t know what to do next ...
Click to expand...
Click to collapse
Thank you so much I finally rooted my Atoto S8 Ultra Plus Gen 2 but I still have a problem with google uncertified & Safetynet if you have a solution please help I’ve already tried most of magistrates module but no success again thank you

****-jones said:
Try to sign the file os_update.zip
Use SingApkV2.zip
https://yadi.sk/d/HkS6APFt3Sb4Ek
You need to install JRE from java.com
In recovery, try using a usb keyboard or mouse. May not work...
Click to expand...
Click to collapse
Hi, after trying to flash from a bootable SD card, I now have a black screen, sometimes it turns white. From the beginning, it was not possible to enter recovery in any way because the radio caught the bootloop, the connection by shorting the t8 processor resistor does not connect to the phoenix suite or is there any unbrick and putting it back on Android 8.1? Eunavi I noticed that the flash mode is blocked by shorting key 1 to ground when I try to enter recovery via the keyboard alt preent screeen " i " with a booted sd card white screen. I have run out of ideas. Do you have options to help somehow? I will be grateful

OneUI 4 Beta Update Link - India (Beta 2 Update is live - Dec Security Patch)

Hello Everyone. The update is gradually getting live in all the regions. I just got it in India. Below is the link which I captured via Canary app.
Beta 1:
http://fota-secure-dn.ospserver.net/firmware/INS/SM-N986B/nspx/3d15912c7dec47678d26b7f03f722ebe.bin?px-time=61da7eb1&px-hash=d04c3cb435cad6937673908c12244c90&px-wid=6204308-WSA211110062027&px-wctime=2021-11-10%2006:20:27&px-unum=&px-nb=UGtezEZ854jbmFcvWGxLEA==
Beta 1 Mirror: https://klisza1993.synology.me:1000.../J4ukGm08evreR1dYWbOQxngvuPTbTvJh-qb4gj3eTDgk
Beta 1 Mirror:
Note 20 Ultra One UI 4 Beta - Google Drive
drive.google.com
Checksum to verify corrupt downloads:
MD5 : 54db93183aa24ecdfaa7134891022094
Beta 2 Update: http://fota-secure-dn.ospserver.net/firmware/INS/SM-N986B/nspx/698c78dfebf8472d9e1691413b9af2f2.bin?px-time=61ed489c&px-hash=5f86741823355625dacb429abc4ff6cf&px-wid=3281729-WSA211124122250&px-wctime=2021-11-24 12:22:50&px-unum=&px-nb=UGtezEZ854jbmFcvWGxLEA==
Prerequisite to flash beta on N20U (N986B) thanks to
dr.ketan​
You need to be on November Security patch before moving ahead.
Dial *#1234#
If your info is ditto same as said below then only you can flash beta 1 for N986B
AP : N986BXXS3DUJ6
CSC : N986BOXM3DUH5
CP : N986BXXS3DUIF
Also if your device is rooted/modified, it will fail. (unlocked bootloader isn't issue but firmware must be complete stock)
TLDR instructions, thanks to pernodpepper
0. Create backup of your device (SmartSwitch)
1. Download .bin
2. Rename update.zip
3. Place file on SDCard
4. Go to recovery (No odin/download mode required)
5. Select Apply update from SDCard and choose update.zip
6. Profit
Detailed instructions along with multiple methods to install. Thanks to Evil_Smiley_za and @AhmedMomen
UPDATE:
-This thread will be for sharing tips and help and update.zip/.bin files (when/if available) for the OneUI 4.0 Android 12 Beta for the Galaxy Note 20 series (Unlocked/Exynos)
Installation Methods:
ADB-method:
1. Download SDK platform tools https://developer.android.com/studio/releases/platform-tools
2. Extract the file in your desktop.
3. Inside the extracted folder put the update.zip file
4. Inside this folder, holding left shift, right click the mouse and select "open command prompt here". The command prompt will open.
5. Shutdown your phone and connect it to the pc
6. Holding Power and volume+ and enter into recovery mode.
7. Select "update via ADB". (scroll down using the volume buttons and select using the power button).
8. Connect the phone to a PC using an original samsung USB cable.
9. In the command prompt run the following command:
./adb devices
10. Wait to see that the daemon has started and that your device is found.
11. If you device is found, run the following command:
./adb sideload update.zip
SD-card method:
1. Download the bin file and rename it to update.zip (by going to file options on your pc you can select to view the file extensions. This makes the renaming process much easier and safer, and avoids renaming the file to update.zip.zip)
2. Copy it to the root directory of your SDcard.
3. Shut down your phone.
4. Connect any USB device to your device, AKG earphones could work, then press Power and volume+ buttons to get into recovery mode.
5. Using your volume keys navigate to "update via sdcard" and press power button to select it.
6. Again using volume keys navigate to the file "update.zip" and press power button to select it.
7. Update will start. Leave it till it completes installing. It will take some time.
8. Phone will reboot by itself and load android.
The update process will start. You will see a percentage counting. First it will verify, then patch etc. Do not move the cable, disconnect the phone or power off the PC.
Once the process is completed (it takes some time) the phone will boot itself, update the apps and log into your home screen.
There are two methods that you can use to get into recovery mode
Method 1:
1. Connect your phone to your PC (Make sure USB debugging is on).
2. Using ADB, enter the command ./adb reboot recovery
3. Wait a little and you should be in recovery mode.
Method 2:
1. Power off your device
2. Connect your device to a PC or use the AKG earphones.
3. Hold down Power+VolumeUp buttons and keep pressing them until you enter recovery mode.
This will not trip knox if done by the methods above
Don't install a beta unless you are fully aware what you are going into.
Don't install the beta if you want your phone to be stable, IT'S a BETA.
It's recommended to make a backup of your data before updating to the Android 12 Beta.
Important Notes:
-Rename the .bin file to update.zip in order to be able to flash it from recovery.
-A common mistake done by some people is that they see the file named update while its a WinRAR.zip file already, then they add another .zip making the name of the file update.zip.zip which will not be flashed successfully, So make sure you do it right.
-Updating to the beta is AT YOUR RISK, No one is responsible if anything goes wrong.
You will not receive OTAs again UNTIL you are on a firmware that gets released later for your original CSC, thats most likely not happening before the BETA is over.
Note: AngryPixel89 is my reddit alias.

is it OXM?
antisocialbratt said:
Hello Everyone. The update is gradually getting live in all the regions. I just got it in India. Below is the link which I captured via Canary app. its a 2.5gb update. Use it at your own risk and please ask other senior members if you have doubts. I just followed instructions someone else shared to grab that link for you guys.
http://fota-secure-dn.ospserver.net/firmware/INS/SM-N986B/nspx/3d15912c7dec47678d26b7f03f722ebe.bin?px-time=61da7eb1&px-hash=d04c3cb435cad6937673908c12244c90&px-wid=6204308-WSA211110062027&px-wctime=2021-11-10%2006:20:27&px-unum=&px-nb=UGtezEZ854jbmFcvWGxLEA==
OXM
Click to expand...
Click to collapse

Yes. It is INS OXM

antisocialbratt said:
Yes. It is INS OXM
Click to expand...
Click to collapse
Awesome

Can someone share the installation process please

Most probably you will have to flash it using Odin but I wouldn't guarantee that. Wait for some time till some modders here figure out a way.

waseem.gani said:
Can someone share the installation process please
Click to expand...
Click to collapse
First make sure you are on November patch
0. Create backup of your device (SmartSwitch)
1. Download .bin
2. Rename update.zip
3. Place file on SDCard
4. Go to recovery (No odin/download mode required)
5. Select Apply update from SDCard and choose update.zip
6. Profit

Maybe this help

Just rename it to update.zip and intall from recovery mode (i was in the latest build with november security patch)
works fine, thank you for the upload.

Do you have to be on October patch (DUIF) or November patch (DUJ6)?

Inxteros said:
Do you have to be on October patch (DUIF) or November patch (DUJ6)?
Click to expand...
Click to collapse
November

Does reguset full wipe or is not needed ?

My bad I was not able to flash it via recovery,any help would be appreciated. I am on October patch.

pernodpepper said:
0. Create backup of your device (SmartSwitch)
1. Download .bin
2. Rename update.zip
3. Place file in internal storage
4. Go to recovery (No odin/download mode required)
5. Flash update.zip
6. Profit
Click to expand...
Click to collapse
I can't see internl storge in the recovery

B.Gaboo said:
(i was in the latest build with november security patch)
You was on DUJ6/DUH5/DUIF?
Click to expand...
Click to collapse

N986BXXS3DUJ6
and installed from the external storage

waseem.gani said:
I can't see internl storge in the recovery
Click to expand...
Click to collapse
You need to use an sdcard and place the zip there

By any chance do you have Update.zip file for SM-G986B??

Rapier said:
You need to use an sdcard and place the zip there
Click to expand...
Click to collapse
Tried that as well, but don't know what the issue is

Amittey said:
By any chance do you have Update.zip file for SM-G986B??
Click to expand...
Click to collapse
This tread is for the SM-N986B. The note 20 Ultra only....

How to root OxygenOS 12?

Hello there, I've never rooted a phone before but would love to try it with Android 12 finally coming out as stable on the OnePlus 8 Pro. So as a complete noob, can anyone walk me through it, or does anyone have a handy thread that takes me through all of it? Thank you!

Same method with OOS11 (other thread), u need full OTA OOS 12 to detached the boot.img and patch it with magisk.
- Or easier just on OOS11 rooted => update to OSS 12 (after install finished, dont reboot, go to magisk select install to inactive slot, now reboot)

dangtoi1993 said:
Same method with OOS11 (other thread), u need full OTA OOS 12 to detached the boot.img and patch it with magisk.
- Or easier just on OOS11 rooted => update to OSS 12 (after install finished, dont reboot, go to magisk select install to inactive slot, now reboot)
Click to expand...
Click to collapse
Thank you! Although as I said I'm very new So if you could explain in a biiiit more noob friendly words, that would be appreciated!

andylmfao said:
Thank you! Although as I said I'm very new So if you could explain in a biiiit more noob friendly words, that would be appreciated!
Click to expand...
Click to collapse
As i know, there is still no downloadable full OTA file for stable OOS 12,
then root method is root at OOS 11 then update after.
to do that, imo, u need to find read and research some old thread to know about that phone before.
its easier than someone will write here for you.

dangtoi1993 said:
As i know, there is still no downloadable full OTA file for stable OOS 12,
then root method is root at OOS 11 then update after.
to do that, imo, u need to find read and research some old thread to know about that phone before.
its easier than someone will write here for you.
Click to expand...
Click to collapse
Ah okay, thank you! Do you know how long it usually takes for an OTA file to come out? Or, if you could, help me through going back to OOS11, rooting it, and then updating to OOS12 and keeping root?

andylmfao said:
Ah okay, thank you! Do you know how long it usually takes for an OTA file to come out? Or, if you could, help me through going back to OOS11, rooting it, and then updating to OOS12 and keeping root?
Click to expand...
Click to collapse
I posted the patched boot img from latest OO12 Ota to another thread.
Flash it via fastboot and your are good.
BootIMG-Magisk24.3_IN2025_11_C.11
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com

xtcislove said:
I posted the patched boot img from latest OO12 Ota to another thread.
Flash it via fastboot and your are good.
BootIMG-Magisk24.3_IN2025_11_C.11
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Click to expand...
Click to collapse
Oh wow, thank you! How do i flash it via fastboot?

andylmfao said:
Oh wow, thank you! How do i flash it via fastboot?
Click to expand...
Click to collapse
I guess you already setup adb/fastboot on your pc. If not google it.
-connect phone to the pc and activate usb debugging in your phones developer settings(unlock developer settings by tapping 5 times about phone)
-run a windows shell in the folder where you setup adb and fastboot.exe
-type the following in shell
adb reboot bootloader
Your phone will boot into the bootloader
type:
fastboot flash boot BootIMG-Magisk24.3_IN2025_11_C.11.img

xtcislove said:
I guess you already setup adb/fastboot on your pc. If not google it.
-connect phone to the pc and activate usb debugging in your phones developer settings(unlock developer settings by tapping 5 times about phone)
-run a windows shell in the folder where you setup adb and fastboot.exe
-type the following in shell
adb reboot bootloader
Your phone will boot into the bootloader
type:
fastboot flash boot BootIMG-Magisk24.3_IN2025_11_C.11.img
Click to expand...
Click to collapse
And that's just it? Wow! Thank you!
Edit- It just say "Waiting for the device in the Shell. What do I do? And it doesn't show up with "fastboot devices" It also says there's no driver under windows device manager.
edit 2 - nvm I figured it out, turns out I hadn't installed the USB drivers

andylmfao said:
And that's just it? Wow! Thank you!
Edit- It just say "Waiting for the device in the Shell. What do I do? And it doesn't show up with "fastboot devices" It also says there's no driver under windows device manager.
edit 2 - nvm I figured it out, turns out I hadn't installed the USB drivers
Click to expand...
Click to collapse
I hope it works for you now. Have fun.

Hi, will this boot.img work for 11 C.16? If not, do you know where i can get it? Thanks

paq1170 said:
Hi, will this boot.img work for 11 C.16? If not, do you know where i can get it? Thanks
Click to expand...
Click to collapse
IDk but i installed C.16 lately and have the patched image on my pc.
boot_11.C16
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Extracted from OnePlus8ProOxygen_11_C.16_15.E.16_OTA_1036_all_2204222258_57eced36 and patched with Magisk24.3.

I'm guessing that it's not a good idea to OTA root from oos11 to 12?

omega552003 said:
I'm guessing that it's not a good idea to OTA root from oos11 to 12?
Click to expand...
Click to collapse
What do you mean? To preserve root with the inactive slot method within magisk?
I root my device with flashing a patched boot img.

xtcislove said:
What do you mean? To preserve root with the inactive slot method within magisk?
I root my device with flashing a patched boot img.
Click to expand...
Click to collapse
Well that how yo'd normally do it, but for some reason when you do that on the OOS12 upgrade its get really weird.

xtcislove said:
IDk but i installed C.16 lately and have the patched image on my pc.
boot_11.C16
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Extracted from OnePlus8ProOxygen_11_C.16_15.E.16_OTA_1036_all_2204222258_57eced36 and patched with Magisk24.3.
Click to expand...
Click to collapse
Do you have C.20 version?

gzyms said:
Do you have C.20 version?
Click to expand...
Click to collapse
No.
Simply download the Prebuild binaries from here.
[TOOL] A QUICK Android OTA payload dumper
Made with Go. By utilizing goroutines, this can extract img files from (full) OTA payload.bin really quickly. See how fast this is: https://i.imgur.com/adpijqf Source Code: https://github.com/ssut/payload-dumper-go Prebuilt binaries...
forum.xda-developers.com
Edit: That is the payload dumper im using.
(ROOT) Android 11 / Latest stock and patched img's / payload dumper / magisk_patched guides
Hi all, Have seen a lot of requests for patched boot images on these threads so thought i'd share a guide on how to get it yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it...
forum.xda-developers.com
6.58 MB folder on MEGA
4 files and 3 subfolders
mega.nz
And download the C.20 update from here.
[OnePlus 8 Pro][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com
Use payload dumper to extract the boot image and copy it to yout device
Install Magisk apk on your device (does not matter if it has root or not)
patch the boot image, copy the patched image to your pc and you have a patched boot image for C.20.

xtcislove said:
No.
Simply download the Prebuild binaries from here.
[TOOL] A QUICK Android OTA payload dumper
Made with Go. By utilizing goroutines, this can extract img files from (full) OTA payload.bin really quickly. See how fast this is: https://i.imgur.com/adpijqf Source Code: https://github.com/ssut/payload-dumper-go Prebuilt binaries...
forum.xda-developers.com
And download the C.20 update from here.
[OnePlus 8 Pro][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com
Use payload dumper to extract the boot image and copy it to yout device
Install Magisk apk on your device (does not matter if it has root or not)
patch the boot image, copy the patched image to your pc and you have a patched boot image for C.20.
Click to expand...
Click to collapse
This is not as easy as you might think. The default payload dumper (and the Go version) cannot handle these incremental OTAs:
Processing boot partitionUnsupported type = 9 · Issue #10 · vm03/payload_dumper
Hi, @vm03! :) Is there a solution to this problem? Only boot.img didn't succeed. I have Nokia 4.2 Thanks! Log: (.py) PS D:\Downloads\1> python payload_dumper.py --diff payload.bin Processing aboot ...
github.com
Instead you need to use this:
GitHub - mrslezak/update_payload_extractor
Contribute to mrslezak/update_payload_extractor development by creating an account on GitHub.
github.com
Unfortunately, this payload extractor fork is broken on windows. I had to set up a Ubuntu VM to run it.
The entire process took the majority of my afternoon
Attached is the extracted boot.img, both magisk patched and unpatched. Hopefully it saves others some time.

Swap_File said:
This is not as easy as you might think. The default payload dumper (and the Go version) cannot handle these incremental OTAs:
Processing boot partitionUnsupported type = 9 · Issue #10 · vm03/payload_dumper
Hi, @vm03! :) Is there a solution to this problem? Only boot.img didn't succeed. I have Nokia 4.2 Thanks! Log: (.py) PS D:\Downloads\1> python payload_dumper.py --diff payload.bin Processing aboot ...
github.com
Instead you need to use this:
GitHub - mrslezak/update_payload_extractor
Contribute to mrslezak/update_payload_extractor development by creating an account on GitHub.
github.com
Unfortunately, this payload extractor fork is broken on windows. I had to set up a Ubuntu VM to run it.
The entire process took the majority of my afternoon
Attached is the extracted boot.img, both magisk patched and unpatched. Hopefully it saves others some time.
Click to expand...
Click to collapse
You are right. I posted the wrong payload dumper.
I am using the one from here and it worked with every payload i tried.
(ROOT) Android 11 / Latest stock and patched img's / payload dumper / magisk_patched guides
Hi all, Have seen a lot of requests for patched boot images on these threads so thought i'd share a guide on how to get it yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it...
forum.xda-developers.com
6.58 MB folder on MEGA
4 files and 3 subfolders
mega.nz
I guess the other one is quicker but im using this and it works. I edit my old post.

Swap_File said:
This is not as easy as you might think. The default payload dumper (and the Go version) cannot handle these incremental OTAs:
Processing boot partitionUnsupported type = 9 · Issue #10 · vm03/payload_dumper
Hi, @vm03! :) Is there a solution to this problem? Only boot.img didn't succeed. I have Nokia 4.2 Thanks! Log: (.py) PS D:\Downloads\1> python payload_dumper.py --diff payload.bin Processing aboot ...
github.com
Instead you need to use this:
GitHub - mrslezak/update_payload_extractor
Contribute to mrslezak/update_payload_extractor development by creating an account on GitHub.
github.com
Unfortunately, this payload extractor fork is broken on windows. I had to set up a Ubuntu VM to run it.
The entire process took the majority of my afternoon
Attached is the extracted boot.img, both magisk patched and unpatched. Hopefully it saves others some time.
Click to expand...
Click to collapse
Can we use this attached boot img on IN2011_11_C.20 (India)?