Related
Bought refurbished LG G4 ( Did nt knew earlier)
ROM - H81510C -
Unstable, Device got stuck with dual windows.
Freezes quite often.
Thought of flashing and used send command terminal.
It got bricked and went to Q9008 mode.
When I checked the board it says MODEL VS986
Tried SD card method---might be using wrong dump file
Tried QFIL.
Nothing working.
Help will be appreciated.
You're screwed. Hopefully you have insurance.
Spookymyo said:
You're screwed. Hopefully you have insurance.
Click to expand...
Click to collapse
No, I don`t have
Did you try LGUP software to reflash a VS986 KDZ?
Thanks
Can u send me the link for procedure
whats the current state of your device?
-> can you boot into Android?
-> can you boot into Download mode?
.
https://drive.google.com/file/d/0B41...ew?usp=sharing Extract folder / Move folder into QFIL folder as a folder not as individual files / load the firehoseprogrammer, patch, & raw / Flash / Remove battery / insert battery / hold volume up and plug in at same time until "download mode" appears on device / wait for drivers to install ? flash vs98627C.kdz with LGUP.
This will only work if the device bricked on 27C or earlier. If you know what FW version you bricked on the extract that FW and replace the appropriate files in the recovery image folder.
LINK not working
gratefuldeaddougie said:
https://drive.google.com/file/d/0B41...ew?usp=sharing Extract folder / Move folder into QFIL folder as a folder not as individual files / load the firehoseprogrammer, patch, & raw / Flash / Remove battery / insert battery / hold volume up and plug in at same time until "download mode" appears on device / wait for drivers to install ? flash vs98627C.kdz with LGUP.
This will only work if the device bricked on 27C or earlier. If you know what FW version you bricked on the extract that FW and replace the appropriate files in the recovery image folder.
Click to expand...
Click to collapse
Link not working !!!!!
I had to fix a couple of bricked selfie phones (z00ud and z00udb but i assume this works on any selfie zd551kl model), that were probably bricked by autoflashing wrong firmware, so after spending a few days going thru many different tutorials, this is my tested method on how to fix them (or if you wanna get a cheap phone from taobao and turn it into a decent one), obviously it wasn't extensively tested, so take it as is . Some steps MIGHT be unnecessary but i didn't want to skip them as i was just glad i found a way how to get the phones to completely stable, latest firmware from useless paperweight.
A. if fone doesnt accept any firmware,or bricked,bootlooped etc. flash basic CN firmware, regardless is recovery WW or CN
- Instructions:
1. go to phone recovery (PWR button + VolDwn, release PWR on logo)
2. on phone select adb bootloader, it switches to fastboot mode (or hold PWR button + VolUp, release PWR on logo)
3. on PC unzip archive and start the autoflash .bat file
4. start the phone
files: archive (Asus Zenfone Selfie Z00UDB ZD551KL 3+16 here )
B. upgrade CN/WW firmare to latest version
- Instructions:
1. on PC install adb drivers
2. go to phone recovery (PWR button + VolDwn, release PWR on logo)
3. on phone select adb sideload
4. on PC, copy firmwares into adb folder
5. on PC go to adb folder and start cmd in that folder (shift+Rclk)
6. type adb devices to check connection, then adb sideload firmwarename.zip
7. start the phone
8. repeat all steps until latest CN/WW firmware is installed
files: adb drivers adb-setup-1.4.3 here , firmwares here(UL-Z00T-CN-1.13.40.661-user,UL-Z00T-CN-1.14.40.695-user,UL-Z00T-CN-1.15.40.1548-user)
C.swap CN firmware for WW, upgrade to Android 6
- Instructions: (also someone elses crappy YT video instructions here )
1. on PC install vc x86 and x64 redist packages for 2010,2012,2013 to prevent .ddl missing errors when running flashtool
1. on PC install asus flash tool
3. on fone turn on usb debugging in developer settings (click on about>sw info>build number)
4. turn off fone then start it in fastboot mode (hold PWR button + VolUp, release PWR on logo)
5. connect the fone to PC, start the autoflash .bat file from the firmware folder (CSC_ZD550KL_1_2_0_70_fac_eng_20150905_secure)
6. disconnect usb, wait for fone to reboot, then disconnect the battery on boot logo (remove back cover in advance)
7. return the battery, and start the fone again in fastboot mode, check for extra info on screen
8. on PC start the flashtool, connect the fone in fastboot mode, check if connected, select the model (ZD551KL), select wipe data
9. on PC, browse to firmware (WW_ZD551KL_1.15.40.1582-bsp-user-20160510203701-secured-release) in flashtool, click start, chose Yes for both options (wipe and image promt), wait until flashing is over
10. disconnect and start the fone
11. connect the fone to PC, copy the firmware (UL-Z00T-WW-21.40.0.1692-user) to internal memory or SD card and wait for the fone to recognize the package and auto-update to Android 6
12. connect the fone to PC, copy any newer firmware to internal memory or SD card (no need to copy next iteration or 2156 build, you can go to for ex. 2214 build right away) wait for the fone to recognize the package and auto-update to newer build of Android 6
files: vc redist packages here , firmwares (WW_ZD551KL_1.15.40.1582-bsp-user-20160510203701-secured-release here,CSC_ZD550KL_1_2_0_70_fac_eng_20150905_secure here), Android 6 firmwares here
Are those steps A,B and C and we should follow everything or methods and just follow only 1? I have a Z00UD Asus Model phone, should I still use the firmware Z00UDB from step A? Thank you!!
jasonch said:
Are those steps A,B and C and we should follow everything or methods and just follow only 1? I have a Z00UD Asus Model phone, should I still use the firmware Z00UDB from step A? Thank you!!
Click to expand...
Click to collapse
Depending on your issues, you should pick the step you need, in case nothing works on your phone start with step A, otherwise start with the step that is appropriate for your problem.
Thanks for this guide. Tried this but get stuck at FRP of ASUS. Google mail was on previous owner. Any solutions?
can flash .zip via TWRP?
dhonxean said:
Thanks for this guide. Tried this but get stuck at FRP of ASUS. Google mail was on previous owner. Any solutions?
Click to expand...
Click to collapse
not sure i understand, are you saying your phone is locked with the account from the previous owner ? if so then just do a factory reset from recovery and setup with your own account.
witopanjoel said:
can flash .zip via TWRP?
Click to expand...
Click to collapse
What zip exactly, some should be done like in the tutorial, others can be flashed from recovery
I use the bootloader from your archive on a Z00UD and it is bricked (will remain on Asus screen)...
Do you have a Z00UD bootloader?
may phone is bricked itry this and now my phone is in boot loop..
z00ud ZD551KL
firmwares are not already available on the websites, do you have any other website that has those files?
asus z00ud, soft bricked by wrong flash, now not turning on, display black, only vibrate when plug in charger or press the power button. Please help.
My asus zenfone selfie model become asus zenfone go. How do i fix this? Any help please.
Need Asus Zenfone Selfie Z00UD Hard Brick/Dead Boot Repair Solution
Z00UD Flash After set dead show Qualcomm HS-USB QDLoader 9008 How To Solve? Help Me
How to Flash TWRP & Root Samsung Galaxy A10 series (Unlocked Exynos Only, A10s (A107F/M) not supported)
NOTICE :
Before you move further, make clear that rooting device -
- Your warranty will be void
- Some of functions may not work on rooted device, some function may get back with un rooting, some may never.
- All your data on device will be lost
- Flashing custom binaries may brick (Usually soft but can be hard brick too) your device, so follow it on your own risk!
If you are ready with condition, move further -
Click to expand...
Click to collapse
Before moving to root device, must read every single instruction given below as any small mistake can lead to fail to achieve root or may brick the device.
A. Unlocking Bootloader
This is a basic step to root device. Go to settings - about phone - Software Information - tap multiple times on "Build number" - This will open developer option.
Now in settings at the end, you will have new option "Developer options" - look for OEM unlocking - Enable it.
(PS : If you don't see this option then you may need to wait up to 7 days or more to appear or may be on some operator you will get it never. Without this option you can not root your device, sorry!).
How to get OEM Unlock option back?
1. Open the Settings app. Tap on General Management → Date and time.
2. Use the toggle button to disable Automatic date and time.
3. Set date option will be enabled now. Tap on it, and set the date to about 10-20 days earlier.
4. Enable developer options.
4.a Go to your device Settings.
4.b Select ‘About phone’ » tap seven times on ‘Build number’.
└ This will enable Developer options under Settings.
4.c Go back to Settings » scroll down to the bottom and you’ll see Developer options menu.
5. Open developer options (in the Settings app itself), and find the option called ‘Auto update system‘. Use the toggle button to disable it.
6. Now, go back to the main screen of Setting, and then tap on Software update.
7. Disable the option ‘Download updates automatically‘.
8. Tap on ‘Download updates manually‘ option, but it will give you an error because of the wrong date, so it’s fine.
9. Restart the device.
10. Go to Settings > Developer options. The OEM unlock option should be enabled now.
Once you have enable OEM unlock option, switch off your device and reboot to download mode.
To put device in download mode - Press Volume Up & then Press Volume Down (Keep holding both) and connect device to PC with USB cable
When device start to download mode, long press volume up to unlock the bootloader. This will wipe your data and automatically reboot
Now let finish setup and again enable developer options (as said above), and confirm that the OEM unlocking option exists and grayed out!
If it is not then you can not root device!
Once you see this option and greyed out, you are ready to flash custom binary and root your device.2. setup the phone by skipping the wizard.
B. Disabling Android Verified Boot
1. Reboot to DOWNLOAD mode.
2. Download Odin 3.14.4 or newer and make sure Samsung USB drivers are installed.
3. Open Odin and put the vbmeta_disabled.tar into USERDATA slot and click "Start"
4. Your device will reboot but it will not boot into system as vbmeta signature has changed.
5. Your device will reboot into RECOVERY mode automatically and prompt "You have to reset your device to factory settings". Use "Volume Up" or "Volume Down" button to move and "Power" button to select. Confirm and reset the device to factory settings.
6. This is the last time the data on the device has to be cleared. Afterwards, if you don't re-lock bootloader or re-enable the Android Verified Boot, you will not lose your data. Be aware, a stock firmware package contains a Android Verified Boot Metadata Image (vbmeta.img) with verifications enabled. You will need to flash the vbmeta_disable image (put into USERDATA slot) along with the stock firmware (use BL, AP, CP, CSC slots) to make sure AVB is not re-enabled and the data is preserved.
C. Flashing TWRP/Magisk
link
Important :
Due to the fact that some devices no longer uses ramdisk in boot images, Magisk has no choice but to be installed in the recovery partition. For these devices, you will have to boot to recovery every time if you want Magisk. Since both Magisk and recovery lives in the same partition, what you actually end up getting when you choose to boot to recovery will be determined by how long you press volume up.
(Powering up normally) → (System with NO Magisk)
(OEM Recovery Key Combo) → (Splash screen) → (Release all buttons) → (System with Magisk)
(OEM Recovery Key Combo) → (Splash screen) → (Keep pressing volume up) → (Actual recovery)
Thanks and credit
For more details read Installation guide by @topjohnwu from Here.
All credit and thanks go to @topjohnwu for magisk & guide.
@dr.ketan for this guide from Here
@jesec for rooting guide Here
@ianmacd for multidisabler from here
Me
reserved.
Hi
Thanks for putting out the details guide!
I followed the steps carefully but got stuck at step 12 - the device boots to download mode and says: "error verifying vbmeta image..."
Luckily I was able to flash it back to stock - but the magisk_patched.tar looks faulty (I copied it using adb) so no root for me
Any ideas?
dani3ltony said:
Hi
Thanks for putting out the details guide!
I followed the steps carefully but got stuck at step 12 - the device boots to download mode and says: "error verifying vbmeta image..."
Luckily I was able to flash it back to stock - but the magisk_patched.tar looks faulty (I copied it using adb) so no root for me
Any ideas?
Click to expand...
Click to collapse
Unplug USB and replug it then make sure the size of tar file almost the same as origin.
for step 6, can we transfer the file via SD card?
afaneh92 said:
Unplug USB and replug it then make sure the size of tar file almost the same as origin.
Click to expand...
Click to collapse
Hi
I triple did it, but no luck
s_ryan said:
for step 6, can we transfer the file via SD card?
Click to expand...
Click to collapse
Sure.
dani3ltony said:
Hi
I triple did it, but no luck
Click to expand...
Click to collapse
Flash AP file only for some reason the BL tar include vbmeta.img but you can patch it too.
I also hit the same problem that soft-brick my phone.. just to confirm, the AP.md5 file u said to use, its name is this? AP_A105GDXU2ASE3_CL15918313_QB23932289_REV00_user_low_ship_meta_OS9.tar
afaneh92 said:
Sure.
Flash AP file only for some reason the BL tar include vbmeta.img but you can patch it too.
Click to expand...
Click to collapse
s_ryan said:
I also hit the same problem that soft-brick my phone.. just to confirm, the AP.md5 file u said to use, its name is this? AP_A105GDXU2ASE3_CL15918313_QB23932289_REV00_user_low_ship_meta_OS9.tar
Click to expand...
Click to collapse
yes
will try to make patched tar for all bootloaders when I got some free time.
Guide updated with more details
Hey dude,
Thanks for the update, I have a problem with step 7
7) Open Magisk Manager - Magisk (first one) - Install - select to "Select and Patch file" - Navigate file you have copied to device (BL_[device_model_sw_ver].tar.md5).
I followed but magisk says No Boot image found, process error, installation failed
afaneh92 said:
Guide updated with more details
Click to expand...
Click to collapse
s_ryan said:
Hey dude,
Thanks for the update, I have a problem with step 7
7) Open Magisk Manager - Magisk (first one) - Install - select to "Select and Patch file" - Navigate file you have copied to device (BL_[device_model_sw_ver].tar.md5).
I followed but magisk says No Boot image found, process error, installation failed
Click to expand...
Click to collapse
My bad I didnt test this, the BL file contain vbmeta.img and need to be patched. Will try to find better solution.
You can flash stock BL file only then reboot again to bootloader and flash the rest files.
I see.. no worries.. I tried to flash the patched ap file with the stock bl, it soft brinked my phone the last time I did it.. anyway, I will wait for your workaround..
Appreciate your help!
s_ryan said:
I see.. no worries.. I tried to flash the patched ap file with the stock bl, it soft brinked my phone the last time I did it.. anyway, I will wait for your workaround..
Appreciate your help!
Click to expand...
Click to collapse
Can you replace vbmeta.img from patched AP with BL using 7zip.
remove md5 extension from BL file.
Guide updated and added flash TWRP instructions
afaneh92 said:
2.Download A10_multidisabler-*-1.41.zip from here and copy to Ext Storage (Because once you flash TWRP, Int storage will not be readable)
Click to expand...
Click to collapse
I think it would be helpful to users if there were a single multi-disabler for all Samsung devices. To that end, I've incorporated your changes for the A10 into my multidisabler and attached a test version to this posting.
Will you please test it? If it works for you, I'll issue a new release.
ianmacd said:
I think it would be helpful to users if there were a single multi-disabler for all Samsung devices. To that end, I've incorporated your changes for the A10 into my multidisabler and attached a test version to this posting.
Will you please test it? If it works for you, I'll issue a new release.
Click to expand...
Click to collapse
Thanks for the update, I was thinking to make pull request with changes. After make sure every thing is working as it should.
afaneh92 said:
Thanks for the update, I was thinking to make pull request with changes. After make sure every thing is working as it should.
Click to expand...
Click to collapse
Thanks. In your case, it's easier now if you just verify that the script I attached is working, since I've already integrated the changes you made in your clone.
Anyone who wants multidisabler support for a new device, however, can either send me a pull request against the latest code, or run the following script on a live, rooted device:
Code:
#!/bin/sh
getprop ro.boot.bootloader
echo --
ls -l /vendor/etc/init/pa_daemon*.rc /vendor/etc/fstab.exynos*
echo --
cat /vendor/etc/fstab.exynos*
echo --
su -c cat /init.rc
Hi dude..
I tried it.. unfortunately I still have problems.. here are some of the problems
1) my 7zip does not allow me to mod the BL files within the md5 extension, so I extracted them out and replaced the file manually then zip it to Tar.. (the VBmeta file is only 1kb) is that right?
2) after flashing via odin, I did a reboot, I encountered a VBMEta error, "Error verifying vbmeta image" Verification_disabled bit is (cant see it, block by the camera module)
In the end, i restored the firmware and got everything back.
s_ryan said:
Hi dude..
I tried it.. unfortunately I still have problems.. here are some of the problems
1) my 7zip does not allow me to mod the BL files within the md5 extension, so I extracted them out and replaced the file manually then zip it to Tar.. (the VBmeta file is only 1kb) is that right?
2) after flashing via odin, I did a reboot, I encountered a VBMEta error, "Error verifying vbmeta image" Verification_disabled bit is (cant see it, block by the camera module)
In the end, i restored the firmware and got everything back.
Click to expand...
Click to collapse
Try using this vbmeta.img (inside the tar file). It worked for me on the A20 with similar error. This file normally seems to be a checksum checker and if it doesn't match what the phone wants to see it gives you that error. But this file was modified to essentially be blank so there is nothing to give the phone an error.
Redmi Note 8 Pro
[Begonia]
[Global Version Only]
WARNING: Before attempting to root your device, do note that by unlocking your bootloader and modifying your device with root, ROMs, etc... you are risking voiding your warranty! I am NOT responsible for what you do to your device either, so follow these instructions at your own risk. Make sure you know what you're doing, it's best to understand the process rather than just copy and paste commands and such.
Firmwares
Global Stable
V10.4.1.0.PGGMIXM
V10.4.2.0 to V11.0.10
V11.0.1.0 PGGMIXM
V11.0.3.0 PGGMIXM
V11.0.4.0 PGGMIXM
V11.0.6.0
China Stable
V10.4.4.0.PGGCNXM
V10.4.6.0.PGGCNXM
V10.4.8.0.PGGCNXM
V10.4.9.0.PGGCNXM
V10.4.10.0.PGGCNXM
V10.4.11.0.PGGCNXM
V11.0.1.0QGGCNXM
China Beta
V9.9.25
V9.10.17
India Stable
V10.4.3.0.PGGINXM
V11.0.1.0 PGGINXM
Europe (EEA)
V10.4.5.0.PGGEUXM
Indonesia
V10.4.2.0.PGGIDXM
V11.0.1.0PGGIDXM
Russia
V10.4.2.0.PGGRUXM
USB Drivers
Download
Unlock Bootloader
Enable OEM Unlocking
Unlock Here
Installing TWRP Recovery and ROOT
Enable USB Debugging - Goto Settings / Additional settings / Developer options / USB Debugging & USB debugging (Security settings) - Enable (If you have not activated Developer options, then Goto Settings / About phone / tap MIUI version 7 times - now developer options enabled.
Global Version
GLOBAL firmware V10.4.5.0.PGGEUXM only
Drivers installed properly
Enabled USB Debugging (enabled developers menu)
1. Turn Off
2. Go to Fastboot mode (Volume - + Power)
3. Connect to the PC
4. Download and extract in C drive, "Run as administrator" and execute "ifelixit+FLASHER+TOOLKIT+Begonia.bat".
5. Choose 1 (TWRP recovery) and enter or Choose 2 (Root Only)
Immediately disconnect the phone from the PC, otherwise it will go to reboot on command and the stock recovery will be restored.
6. Put the Minimal ADB and Fastboot in C: of your PC.
Transfer the Recovery.img in Fastboot folder
Open Fastboot folder and Press Shift+Right Click and Select Open Command Window Here at the CMD type fastboot devices and enter (check if it's recognized the device).
7. Type fastboot flash recovery recovery.img and enter (TWRP will be installed)
8. Disconnect the phone from the PC, hold the Power button as the screen goes blank immediately hold Volume + the TWRP splash screen will appear and disappear still hold the button when the TWRP splash screen appears a second time release Volume +. If Chinese language change to English. If TWRP will ask you the password (this means that there is DATA encryption)click on CANCEL and get to the main screen.
We go to the mount, put check on data, system, vendor, nvdata and MicroSD card (if the phone has a memory card).
Press home to return to the main screen Choose Advanced-File Manager item >system_root / system / folder at the bottom there is a recovery_fromboot.p file delete it.
Go back to Advanced and select Close AVB2.0 and flash the archive with a swipe to the right.
Again, we go along the Advanced-File Manager path in the root, look for the supersu folder in it, select the SuperSu_installer.zip fileand flash it with a swipe to the right. This is an archive from Magisk_19.4 it will patch boot. The firmware of this archive should go WITHOUT a single error, all lines should be white and at the end of DONE. If everything was done without errors in the TWRP select the Reboot-System. The first boot will be a little long and Don't Panic when boot up check the Magisk Manager>Settings>Update Settings>Stable Channel.
Stock boot IMG for V10.4.5.0.PGGEUXM just in case bootloop
TWRP for Begonia
If error occurs..
1. Go to Minimal ADB and Fastboot in C: of your PC. Open Fastboot folder and Press Shift+Right Click and Select Open Command Window Here at the CMD type fastboot devices and enter (check if it's recognized the device).
2. Enter the following commands: fastboot flash boot boot.img and Enter then fastboot flash recovery recovery.img and Enter. We have flashed clean boot and TWRP.
3. Disconnect the phone from the PC, hold the Power button as the screen goes blank immediately hold Volume + the TWRP splash screen will appear and disappear still hold the button when the TWRP splash screen appears a second time release Volume +. The recovery_fromboot.p file is already deleted earlier.
5. Go to Mount in TWRP check data, system, vendor, nvdata and now you can decrypt DATA by formatting in TWRP Wipe-Fotmat Data, write yes and swipe.
6. Disconnect the phone from the PC, hold the Power button as the screen goes blank immediately hold Volume + the TWRP splash screen will appear and disappear still hold the button when the TWRP splash screen appears a second time release Volume +. If Chinese language change to English. If TWRP will ask you the password (this means that there is DATA encryption)click on CANCEL and get to the main screen.
We go to the mount, put check on data, system, vendor, nvdata and MicroSD card (if the phone has a memory card).
Press home to return to the main screen Choose Advanced-File Manager item >system_root / system / folder at the bottom there is a recovery_fromboot.p file delete it.
Go back to Advanced and select Close AVB2.0 and flash the archive with a swipe to the right.
Again, we go along the Advanced-File Manager path in the root, look for the supersu folder in it, select the SuperSu_installer.zip fileand flash it with a swipe to the right. This is an archive from Magisk_19.4 it will patch boot. The firmware of this archive should go WITHOUT a single error, all lines should be white and at the end of DONE. If everything was done without errors in the TWRP select the Reboot-System. The first boot will be a little long and Don't Panic when boot up check the Magisk Manager>Settings>Update Settings>Stable Channel.
Proof of Video that Redmi Note 8 Pro Rooted
https://www.youtube.com/watch?v=P4rBUT9qR-0&feature=youtu.be
Contributors
Nikas
esleer
Xakep1993
SPIRITic
m3lbrunton
Lyelik74
@topjohnwu
TWRP Community
XDA Community
Xiaomi Community
How to Root Redmi Note 8 Pro Chinese Version
Redmi Note 8 Pro
[Begonia]
[Chinese Version Only]
How to Root and installing Google Pay
Download
Magisk-release.zip
Magisk-uninstaller
Magisk app release apk
1. Download magisk-uninstaller.zip and magisk-release.zip and transfer in MicroSD
2. Reboot to TWRP Recovery
3. Install and look for the supersu folder>select the file SuperSu_instsller.zip and install.
4. Make Wipe, Advanced Wipe, Dalvik/Art Cache, Data and Cache and swipe
5. Make Wipe and Format Data
6. Mount the SD card, install magisk-uninstaller.zip to remove the old Magisk
7. Install magisk-release.zip Install the new Magisk v20.2
8. Advanced > File Manager >system_root / system > Delete the recovery_fromboot.p file
9. Advanced (put 2 checkmarks) Close AVB2.0
10. Advanced (put 2 ticks) RM Force encrypt
11. Reboot System
12. Pass authorization, install the Magisk app-release.apk
13. Click in the application: Check SafeNet status
Installing Google Pay
Download
Google Pay Module
1. Download in the Google Pay market
2. Download the Gpay.zip module for Magisk.
3. Open Magisk Manager>Modules and install Gpay.zip module and reboot
4. Open Magisk Hide
5. Look for Google Pay and Google Services Framework and check then close the application
6. Launch Google Pay and enter your data and card details.
7. The bank will check and wait for the confirmation code via SMS.
9. For GPay to work you must configure the lock with a password or pattern.
Gcam Stable for Redmi Note 8 Pro
GCam Stable for Redmin Note 8 Pro
Download:
GCam Stable
Changelog:
Stable release for Redmi Note 8 Pro!
-> Fixed excessive noise on aux cameras (thanks to Savitar).
-> Separate AWB settings for lenses.
-> Opening settings from aux cameras is not crashing anymore but lens will be reseted to main after exiting settings (need to use proper config wyroczen_rn8pro_3.xml)
Settings:
- Configs for this version
GCam for Redmi Note 8 Pro
There are two versions of Google camera available:
Google camera mode
Night Sight
PhotoSphere
Photobooth
Slow Motion
RAW support
HDR+
Motion
Panorama
Lens Blur
Google Lens
Portrait
What's not working
Google Camera 6.1.021
Portrait mode
Video mode
Slow Motion
Night Sight
Google Camera 5.1.018
All working
Download 6.1.021
Download 5.1.018
Contributors
Arnova8G2
BSG
GPay in Redmi Note 8 Pro
Instructions
1. Download GPay in Playstore (Don't open it)
2. Go to Magisk Manager > Magisk Hide > GPay
3. Install GPay Magisk Module and reboot
4. Open GPay and Bind a card.
Nice
Not working, bootloop. To fix bootloop, need to flash original boot.img - need to put original boot.img from ROM we have in adb folder and run command "fastboot flash boot boot.img".
Before posting such tutorials I suggest to check is it even working, because on chinese version of device this will NOT WORK.
chudy88 said:
Not working, bootloop. To fix bootloop, need to flash original boot.img - need to put original boot.img from ROM we have in adb folder and run command "fastboot flash boot boot.img".
Before posting such tutorials I suggest to check is it even working, because on chinese version of device this will NOT WORK.
Click to expand...
Click to collapse
And this is not a Chinese version tutorials.
Read above before doing some things.
WARNING: Before attempting to root your device, do note that by unlocking your bootloader and modifying your device with root, ROMs, etc... you are risking voiding your warranty! I am NOT responsible for what you do to your device either, so follow these instructions at your own risk. Make sure you know what you're doing, it's best to understand the process rather than just copy and paste commands and such.
Did you read about it?
madsponge26 said:
And this is not a Chinese version tutorials.
Click to expand...
Click to collapse
Where do you wrote it? I don't see. You'd better fix this guide, bacause now everyone with chinese device, if they do what u wrote here, will have a bootloop cause of you.
Did't work. Still loop the boot screen.
After do that ,it couldn't boot to system because the boot.img.
wuxeon said:
Did't work. Still loop the boot screen.
After do that ,it couldn't boot to system because the boot.img.
Click to expand...
Click to collapse
You have chinese device, or global or EU? Or other?
wuxeon said:
Did't work. Still loop the boot screen.
After do that ,it couldn't boot to system because the boot.img.
Click to expand...
Click to collapse
You should indicate Global or CN version? What boot.img?
chudy88 said:
Where do you wrote it? I don't see. You'd better fix this guide, bacause now everyone with chinese device, if they do what u wrote here, will have a bootloop cause of you.
Click to expand...
Click to collapse
It clearly states: [Global Version Only]
Can someone confirm it's working on global though? Including rooting?
donkyshot said:
It clearly states: [Global Version Only]
Click to expand...
Click to collapse
Yeah yeah, OP added it after my post. And it's not true - should work also on EU version.
That's why amateurs shouldn't make such threads.
chudy88 said:
Where do you wrote it? I don't see. You'd better fix this guide, bacause now everyone with chinese device, if they do what u wrote here, will have a bootloop cause of you.
Click to expand...
Click to collapse
And what's your contribution towards fixing the problem ? ?
Do some work instead of whining and waiting for others to give you the solution on a plate.
chudy88 said:
donkyshot said:
It clearly states: [Global Version Only]
yeah yeah, OP added it after my post
Click to expand...
Click to collapse
Okay sorry I didn't know.
This thread is obviously taken from here : http://c.mi.com/thread-2529429-1-0.html
I think it should be clearly stated in the thread as it is a more complete guide than this copy.
Click to expand...
Click to collapse
robbie_lpl said:
And what's your contribution towards fixing the problem ? ?
Do some work instead of whining and waiting for others to give you the solution on a plate.
Click to expand...
Click to collapse
Still better than breaking peoples phones. I'm warning potential users to not do this if they have chinese device, that's my contribution.
chudy88 said:
Still better than breaking peoples phones. I'm warning potential users to not do this if they have chinese device, that's my contribution.
Click to expand...
Click to collapse
When signing up for this website you sign a waiver that you are the sole person responsible for your device. Bootloops too.
Don't wanna have it bricked ? Don't mess with it.
Nobody's telling you to do that.
How about some gratitude and appreciation for those who take the time and trouble looking for a solution. Sponging off others work and whingening about it ?
Show some manners.
robbie_lpl said:
When signing up for this website you sign a waiver that you are the sole person responsible for your device. Bootloops too.
Don't wanna have it bricked ? Don't mess with it.
Nobody's telling you to do that.
How about some gratitude and appreciation for those who take the time and trouble looking for a solution. Sponging off others work and whingening about it ?
Show some manners.
Click to expand...
Click to collapse
What time, what solution?! Method posted by OP for this device is known for weeks already... And its just copied solution from other tutorials for older Xiaomi phones... I can bet that OP even didn't check it and I won't be surprised if he even don't have this phone... Besides, I still don't have solid proof that it works, even on global/EU version of device.
in the end this tutorial is working or not on global?
holymoz said:
in the end this tutorial is working or not on global?
Click to expand...
Click to collapse
Not working.
Hey, I have rooted a few of these and helped a few people as well and feel confident I can help most anyone with the problems they face rooting this beast. Also I'm posting this to have a place I can send people I help so I don't have to keep retyping stuff. From what I can tell the steps to root this phone are almost the same as the last model.
For now I will just post rough steps and use this as a place to provide support to people.
STEPS: (Rough guide/ please use other sources of information also)
1.) Fully update your phone
2.) Download the bootloader unlock app from asus official website. Also download and install Magisk. I recommend canary release.
3.) Get a patched boot.img or learn with a search engine how to extract the boot.img from payload.bin which can be found inside the large firmware zip files on the asus website (same link as unlock app but click firmware). Follow a tutorial.
4.) Turn on adb settings, and roboot into fastboot. adb reboot bootloader
For me for windows I needed to download fastboot drivers and go to device manager and install/update them.
5.) Unlock the bootloader with: fastboot flashing unlock
6.) Flash the patched boot image with: fastboot flash boot magisk_patched####.img
7.) Download safteynetfix and go to Magisk -> Modules and install safteynetfix.zip. Then go to Magisk -> Settings and enable Zygisk, and Enforce Denylist. Then turn on airplane mode and click on Configure deny list. add apps that are not working with root here, then delete their storage in App->Settings and reboot, remove airplane mode, and force close the apps in question.
For example select Show -> system apps. and add Google Play Store and Google play services to the deny list. Then go to App->Settings and delete both of those app's storage. Then when you reboot and remove airplane mode and force close google play and reopen it and go to Google Play -> Settings -> About you should see at the bottom "Device is certified".
If this last step does not show certified you did something wrong or I described it bad, check with a tutorial how to set up safteynet + configure deny list. Or post here and I will help you.
FINAL NOTE: After this the OTA updates that ASUS pushes will not be downloaded by our phone. We need to go to the same website we downloaded the unlock app from and we need to download the firmware files (WW for me) and put them in /sdcard/UL-ASUS-Al2201....zip and reboot. We then need to repeat the root process and the Magisk module process. Also I think we need to do this for every update along the way and cannot skip to the most recent update but not sure.
Hi! Thank you very much for sharing and helping. I have Tencent edition, from CN to WW, but a couple of things don't work properly:
- Android Auto does not communicate with my car (phone detected and bluetooth connected) bit app stops.
- Gboard voice dictation does not work (google assistant yes)
Country is WW. Safetynet passed. Play certified.
..I followed your guide.
I flashed the posted xda raw throuh fastboot and the the Magisk patched .img
When I tried TO apply latest updates (160) the Same message error appeared.
There is spmething strange (or are least I think It strange):
When I start in "fastboot" (black screen with capital text single line) my device isn'r recognized by PC. Then I switch to "recovery" and then to "fastboot" and a menu (several lines) with title "fastbootd" appears and the phone is recognized by PC (fastboot devices). If I choose bootloader the first screen appears.
I tried to reflash the raw but either the phone isn't recognized or a message appears on the cmd window showing "not rog 6" (more or less) and stops. But the phone is recognized everywhere as rog6...
I miss my broken rog2, it was much easier to root
Do you have any idea what's going on? Or when the twrp boot will be released so that I can brutally flash any zip?
leathan said:
Hey, I have rooted a few of these and helped a few people as well and feel confident I can help most anyone with the problems they face rooting this beast. Also I'm posting this to have a place I can send people I help so I don't have to keep retyping stuff. From what I can tell the steps to root this phone are almost the same as the last model.
For now I will just post rough steps and use this as a place to provide support to people.
STEPS: (Rough guide/ please use other sources of information also)
1.) Fully update your phone
2.) Download the bootloader unlock app from asus official website. Also download and install Magisk. I recommend canary release.
3.) Get a patched boot.img or learn with a search engine how to extract the boot.img from payload.bin which can be found inside the large firmware zip files on the asus website (same link as unlock app but click firmware). Follow a tutorial.
4.) Turn on adb settings, and roboot into fastboot. adb reboot bootloader
For me for windows I needed to download fastboot drivers and go to device manager and install/update them.
5.) Unlock the bootloader with: fastboot flashing unlock
6.) Flash the patched boot image with: fastboot flash boot magisk_patched####.img
7.) Download safteynetfix and go to Magisk -> Modules and install safteynetfix.zip. Then go to Magisk -> Settings and enable Zygisk, and Enforce Denylist. Then turn on airplane mode and click on Configure deny list. add apps that are not working with root here, then delete their storage in App->Settings and reboot, remove airplane mode, and force close the apps in question.
For example select Show -> system apps. and add Google Play Store and Google play services to the deny list. Then go to App->Settings and delete both of those app's storage. Then when you reboot and remove airplane mode and force close google play and reopen it and go to Google Play -> Settings -> About you should see at the bottom "Device is certified".
If this last step does not show certified you did something wrong or I described it bad, check with a tutorial how to set up safteynet + configure deny list. Or post here and I will help you.
FINAL NOTE: After this the OTA updates that ASUS pushes will not be downloaded by our phone. We need to go to the same website we downloaded the unlock app from and we need to download the firmware files (WW for me) and put them in /sdcard/UL-ASUS-Al2201....zip and reboot. We then need to repeat the root process and the Magisk module process. Also I think we need to do this for every update along the way and cannot skip to the most recent update but not sure.
Click to expand...
Click to collapse
Sorry, I messed with the reply: it's my previous post.
fux1976 said:
Hi! Thank you very much for sharing and helping. I have Tencent edition, from CN to WW, but a couple of things don't work properly:
- Android Auto does not communicate with my car (phone detected and bluetooth connected) bit app stops.
- Gboard voice dictation does not work (google assistant yes)
Country is WW. Safetynet passed. Play certified.
..I followed your guide.
I flashed the posted xda raw throuh fastboot and the the Magisk patched .img
When I tried TO apply latest updates (160) the Same message error appeared.
There is spmething strange (or are least I think It strange):
When I start in "fastboot" (black screen with capital text single line) my device isn'r recognized by PC. Then I switch to "recovery" and then to "fastboot" and a menu (several lines) with title "fastbootd" appears and the phone is recognized by PC (fastboot devices). If I choose bootloader the first screen appears.
I tried to reflash the raw but either the phone isn't recognized or a message appears on the cmd window showing "not rog 6" (more or less) and stops. But the phone is recognized everywhere as rog6...
I miss my broken rog2, it was much easier to root
Do you have any idea what's going on? Or when the twrp boot will be released so that I can brutally flash any zip?
Click to expand...
Click to collapse
I cant really help as I can't reproduce those problems. My phone was originally WW, but did you try to apply the non latest update? Then work your way up to 160?
fux1976 said:
Hi! Thank you very much for sharing and helping. I have Tencent edition, from CN to WW, but a couple of things don't work properly:
- Android Auto does not communicate with my car (phone detected and bluetooth connected) bit app stops.
- Gboard voice dictation does not work (google assistant yes)
Country is WW. Safetynet passed. Play certified.
..I followed your guide.
I flashed the posted xda raw throuh fastboot and the the Magisk patched .img
When I tried TO apply latest updates (160) the Same message error appeared.
There is spmething strange (or are least I think It strange):
When I start in "fastboot" (black screen with capital text single line) my device isn'r recognized by PC. Then I switch to "recovery" and then to "fastboot" and a menu (several lines) with title "fastbootd" appears and the phone is recognized by PC (fastboot devices). If I choose bootloader the first screen appears.
I tried to reflash the raw but either the phone isn't recognized or a message appears on the cmd window showing "not rog 6" (more or less) and stops. But the phone is recognized everywhere as rog6...
I miss my broken rog2, it was much easier to root
Do you have any idea what's going on? Or when the twrp boot will be released so that I can brutally flash any zip?
Click to expand...
Click to collapse
To answer some other stuff, did you try looking in Device manager and maker sure your android device/asus rog is listed without an exclamation? I was having similar issues on windows until I installed the usb drivers. You should be able to run fastboot devices from within the bootloader menu.
leathan said:
I cant really help as I can't reproduce those problems. My phone was originally WW, but did you try to apply the non latest update? Then work your way up to 160?
Click to expand...
Click to collapse
Hi there! I flashed raw .134 and then the magisk patched boot .img as dedcribed in one forums guide, then tried to upgrade to .160 when I saw it on the asus support page. I was thinking of using edl and hard reset the phone and start again (in the next few days as it take times). I found a guide and tools (don't know if I can post the external link here). Do you think that could work? I downloaded raw .160 from the asus site (then i'll reflash the magisk patched boot).
To be honest it tickles me to try out this things (hoping not to end up with a brick of course)
leathan said:
I cant really help as I can't reproduce those problems. My phone was originally WW, but did you try to apply the non latest update? Then work your way up to 160?
Click to expand...
Click to collapse
Hi there! I flashed raw .134 and then the magisk patched boot .img as dedcribed in one forums guide, then tried to upgrade to .160 when I saw it on the asus support page. I was thinking of using edl and hard reset the phone and start again (in the next few days as it take times). I found a guide and tools (don't know if I can post the external link here). Do you think that could work? I downloaded raw .160 from the asus site (then i'll reflash the magisk patched boot).
To be honest it tickles me to try out this things (hoping not to end up with a brick of course
leathan said:
To answer some other stuff, did you try looking in Device manager and maker sure your android device/asus rog is listed without an exclamation? I was having similar issues on windows until I installed the usb drivers. You should be able to run fastboot devices from within the bootloader menu.
Click to expand...
Click to collapse
I fortunately have several pcs so i switched to the one with no drivers issues. As written I can only use fastboot commands when the phone is in fastbootd mode (sort of recover looking screen). The bootloader mode (one line, capital letters) is not recognized by pc..that's why I was thinking about EDL and reflashing the first level boot. Is it hazardous?
fux1976 said:
Hi there! I flashed raw .134 and then the magisk patched boot .img as dedcribed in one forums guide, then tried to upgrade to .160 when I saw it on the asus support page. I was thinking of using edl and hard reset the phone and start again (in the next few days as it take times). I found a guide and tools (don't know if I can post the external link here). Do you think that could work? I downloaded raw .160 from the asus site (then i'll reflash the magisk patched boot).
To be honest it tickles me to try out this things (hoping not to end up with a brick of course
I fortunately have several pcs so i switched to the one with no drivers issues. As written I can only use fastboot commands when the phone is in fastbootd mode (sort of recover looking screen). The bootloader mode (one line, capital letters) is not recognized by pc..that's why I was thinking about EDL and reflashing the first level boot. Is it hazardous?
Click to expand...
Click to collapse
I would continue to try to get my PC to recognize my Phone in bootloader mode using the drivers I linked. After helping 2 people who had windows, on both of their machines, I had to install the drives. On linux is just worked.
Also the raw image that I linked is of 93 so you should have needed to download 95, 97, 134, and 160 from asus. Then after 160 I repatched the boot img and re-rooted.
There is another person who said after tencent -> WW she was able to update to 134 where she had some problem. But I don't know how to reproduce that stuff Hope you figure it out though.
leathan said:
I would continue to try to get my PC to recognize my Phone in bootloader mode using the drivers I linked. After helping 2 people who had windows, on both of their machines, I had to install the drives. On linux is just worked.
Also the raw image that I linked is of 93 so you should have needed to download 95, 97, 134, and 160 from asus. Then after 160 I repatched the boot img and re-rooted.
There is another person who said after tencent -> WW she was able to update to 134 where she had some problem. But I don't know how to reproduce that stuff Hope you figure it out though.
Click to expand...
Click to collapse
Phone looks certified, country WW, safetynet passed and upgraded to .160. Only 2 problema left: voice dictation of GBoaed and Android auto not working.
I tried several ways but they didn't solve. Voice dictation worked and then stopped: I guess something interferes... Android Auto app crashes although phone connects to car and is recognised.
Very strange behaviour...
Do you have any idea on how to reflash last .160 zip without twrp? Once installed it gets ignored by system when saved in home directory...
Everything else is working properly.
Isn't Android Auto no more (i.e discontinued).....?
elmor0 said:
Isn't Android Auto no more (i.e discontinued).....?
Click to expand...
Click to collapse
what?!? where did you hear that? It'just something causing problems (compatibility issues with app or setting: magisk, modules, adaway, skipad, disabled system apps and so on). If I could manage to reflash the stock rom it'll work again (I hope)
fux1976 said:
Hi! Thank you very much for sharing and helping. I have Tencent edition, from CN to WW, but a couple of things don't work properly:
- Android Auto does not communicate with my car (phone detected and bluetooth connected) bit app stops.
- Gboard voice dictation does not work (google assistant yes)
Country is WW. Safetynet passed. Play certified.
..I followed your guide.
I flashed the posted xda raw throuh fastboot and the the Magisk patched .img
When I tried TO apply latest updates (160) the Same message error appeared.
There is spmething strange (or are least I think It strange):
When I start in "fastboot" (black screen with capital text single line) my device isn'r recognized by PC. Then I switch to "recovery" and then to "fastboot" and a menu (several lines) with title "fastbootd" appears and the phone is recognized by PC (fastboot devices). If I choose bootloader the first screen appears.
I tried to reflash the raw but either the phone isn't recognized or a message appears on the cmd window showing "not rog 6" (more or less) and stops. But the phone is recognized everywhere as rog6...
I miss my broken rog2, it was much easier to root
Do you have any idea what's going on? Or when the twrp boot will be released so that I can brutally flash any zip?
Click to expand...
Click to collapse
Keep spamming flashall_aft.cmd until it works or try flashing other raw.
This worked for me if your able to get fastboot devices listed in adb firstly
finallau said:
Keep spamming flashall_aft.cmd until it works or try flashing other raw.
This worked for me if your able to get fastboot devices listed in adb firstly
Click to expand...
Click to collapse
I only have raw for .143 but I updated to .160*...can I use the previous version or do I get bricked? I don't trust anti roll back mechanism. I can live with this 2 "limitations" waiting for twrp and then be able to flash zip with no hassle.
*I downloaded source code from the Asus site but not sure how to use it (and unzipped is around 10 gb )
Thank you for this! I've been out of the root game for years but noticed with your post that I can hide root from Google Pay and my banking apps, so thinking of trying this. One question though - you mentioned that official updates need to be manually downloaded and the phone re-rooted. Would this wipe the phone each time?
fastboot driver doesnt support win64
Will the phone do a factory reset after unlocking the bootloader?
Anyone know if I root my phone following these instructions, will it factory reset or wipe my data partition? Sorry it's been a while since I rooted any phone, and I am excited about going this route
MrKioFLow said:
Anyone know if I root my phone following these instructions, will it factory reset or wipe my data partition? Sorry it's been a while since I rooted any phone, and I am excited about going this route
Click to expand...
Click to collapse
Yes, if you unlock the bootloader using the bootloader unlock app (which is a step that is missing in the original post), your phone will perform factory reset.
Troubleshooting
Once you boot into the bootloader with the adb reboot bootloader command, stay on the screen with the green START. Do not navigate to the fastbootd.
Use the side USB port to connect to your computer - not the bottom one.
Run the adb and fastboot commands in Command Prompt as Administrator.
Before you reboot into bootloader, remove Lock screen in Settings.
If you execute fastboot flashing unlock and you got FAILED (remote: 'permission denied'), just ignore it.
It's always better to install the latest updates, then download the firmware to your PC from ASUS Webpage and extract the boot.img and patch it in Magisk in the phone using this tutorial.
Thanks for the guide! Should add that you have to use the side port for fastboot to see the device. Was stuck for a while trying to figure out why neither mac nor pc couldn't find it when it was in bootloader mode - it was because I was using the bottom port lol!
Also if you want to disable verity and verification for the verified boot images, you have to do for both vbmeta.img and vbmeta_system.img. Didn't boot for me until I did that, and had to do an additional factory reset from recovery because of this.