Database Develop

Update problem redmi9

Please anyone can help me
I have tried to download it from the website as well but manual and auto both gives me this message. I even asked this question in mi community but still that are unable to help.

Can you explain what's your problem because I didn't understand what you mean exactly.

Abdullah.Csit said:
Can you explain what's your problem because I didn't understand what you mean exactly.
Click to expand...
Click to collapse
It gives me error of try again or cancel

Bump

6425001939offered By https://unofficialtwrp.COM
fastboot flash recovery recovery.img
fastboot flash vbmeta vbmeta.img
for ab:
fastboot flash recovery_a recovery.img
fastboot flash recovery_b recovery.img
flash magisk & encryption disabler via twrp

6425001939offered By https://unofficialtwrp.COM
fastboot flash recovery recovery.img
fastboot flash vbmeta vbmeta.img
for ab:
fastboot flash recovery_a recovery.img
fastboot flash recovery_b recovery.img
flash magisk & encryption disabler via twrp

QPDS30.114-80-2 december moto security update and whatnot

Woke to a failed motorola security update. Root, of course. I wanted the update, so, I removed root. I know... In any case took the update. Yay. It was all good. I then wiped my phone, I was just looking for an excuse. However, in ordinary circumstances, it's simply necessary to reflash a newly patched (updated with new firmware/update) boot.img file following the security update. YOu can grab the new firmware (direct) here.
I flashed the new firmware:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear (completely unnecessary, d'oh!)
fastboot reboot
set up the phone, installed magisk manager, patched the new boot.img, flashed it (fastbootd) and rebooted into a rooted phone. Cool.

Yea i just ROOTed w/ Magisk 21.4 and passing Saftey Net with Ease. I cheated by using TWRP 3.5.0
*Edit*
Magisk Manager v3.6.0 NOT 3.5.0

Nice. I never tried to install twrp on the edge after a dismal failure on the g power. I miss full system dumps.

Security Update to february is out. Still no update to 11.

reggjoo said:
Security Update to february is out. Still no update to 11.
Click to expand...
Click to collapse
2nd

after flash patched boot.img device stuck in bootloop

my device is vivo s1 android 11 version...
After Flashing patch boot.img my device stuck in bootloop...boot.img is dump by mtk client

I'm not sure in Android 11 but in Android 10 you have to flash an empty vbmeta file otherwise you have a bootloop.
Vbmet contains the crc check of boot.img, is a part of the safe boot.

Harlock1978 said:
I'm not sure in Android 11 but in Android 10 you have to flash an empty vbmeta file otherwise you have a bootloop.
Vbmet contains the crc check of boot.img, is a part of the safe boot.
Click to expand...
Click to collapse
i also try to disable or flash empty vbmeta
By these commands,
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Fastboot flash vbmeta vbmeta.Img.empty
After that device Again start Bootloop

Question Device wont boot up

* First of all, I flashed the latest ColorOs 12.1 firmware using the fastboot enhance tool 1.3 posted in this github
Releases · libxzr/FastbootEnhance
A user-friendly Fastboot ToolBox & Payload Dumper for Windows - libxzr/FastbootEnhance
github.com
-----> the flash was successful and the device booted normally
Next, I tried to root the device. I downloaded the patched boot.img file to be applied by magisk from this url:
[OP10Pro] Color OS A.15.zip​It was listed under the following thread : https://forum.xda-developers.com/t/root-oneplus-10-pro-color-os-oxygen-os.4401243/
I then put the device on Fastboot mode and used the command: fastboot flash boot boot.img where boot.img is the file I downloaded from the above link----> this resulted into a boot loop
* I extracted the stock boot.img from the payload.bin using the tool found in that thread:
How to Extract payload.bin and get stock boot image file
To extract the payload.bin file from Android stock firmware and get stock boot image file, you should refer to the instructions given in here.
www.droidwin.com
I tried to flash it using the same command: fastboot flash boot boot.img-----> the bootloop remained
* I tried to flash stock vbmeta, vendor_boot.img and boot from boot.img using the following commands:
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_b vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system_a vbmeta_system.img
fastboot --disable-verity --disable-verification flash vbmeta_system_b vbmeta_system.img
fastboot flash --disable-verity --disable-verification vbmeta_vendor_a vbmeta_vendor.img
fastboot flash --disable-verity --disable-verification vbmeta_vendor_b vbmeta_vendor.img
fastboot flash vendor_boot vendor_boot.img
fastboot boot boot.img
all the commands ran without a problem however, the bootloop still remained.
As a last resort, I tried to flash the stock firmware again using the fastboot enhance tool 1.3 that I used in the first step, the tool showed that operation was complete, like it did in the first step. Then I clicked reboot to system. The reboot was initiated and the oneplus logo appeared for few seconds then, it disappeared and since then, nothing appeared on the screen.
I tried all power clicking combos to get the phone to enter any mode (fastboot or recovery). All of them failed. The screen since then is turned off and the phone does not turn on or enter any mode regardless which buttons I click. I tried:
press and hold power button
keep pressing power button+ vol up
keep pressing power button + vol down
keep pressing power button+ vol up + vol down
All of them failed to turn the phone on, The screen remained completely black.
I thought the device went out of charge so I left it connected to the charger for like 15 minutes. Still this did not affect any thing
Any one knows how can I solve this problem?
Thanks in advance

lordvoldmort said:
* First of all, I flashed the latest ColorOs 12.1 firmware using the fastboot enhance tool 1.3 posted in this github
Releases · libxzr/FastbootEnhance
A user-friendly Fastboot ToolBox & Payload Dumper for Windows - libxzr/FastbootEnhance
github.com
-----> the flash was successful and the device booted normally
Next, I tried to root the device. I downloaded the patched boot.img file to be applied by magisk from this url:
[OP10Pro] Color OS A.15.zip​It was listed under the following thread : https://forum.xda-developers.com/t/root-oneplus-10-pro-color-os-oxygen-os.4401243/
I then put the device on Fastboot mode and used the command: fastboot flash boot boot.img where boot.img is the file I downloaded from the above link----> this resulted into a boot loop
* I extracted the stock boot.img from the payload.bin using the tool found in that thread:
How to Extract payload.bin and get stock boot image file
To extract the payload.bin file from Android stock firmware and get stock boot image file, you should refer to the instructions given in here.
www.droidwin.com
I tried to flash it using the same command: fastboot flash boot boot.img-----> the bootloop remained
* I tried to flash stock vbmeta, vendor_boot.img and boot from boot.img using the following commands:
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_b vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system_a vbmeta_system.img
fastboot --disable-verity --disable-verification flash vbmeta_system_b vbmeta_system.img
fastboot flash --disable-verity --disable-verification vbmeta_vendor_a vbmeta_vendor.img
fastboot flash --disable-verity --disable-verification vbmeta_vendor_b vbmeta_vendor.img
fastboot flash vendor_boot vendor_boot.img
fastboot boot boot.img
all the commands ran without a problem however, the bootloop still remained.
As a last resort, I tried to flash the stock firmware again using the fastboot enhance tool 1.3 that I used in the first step, the tool showed that operation was complete, like it did in the first step. Then I clicked reboot to system. The reboot was initiated and the oneplus logo appeared for few seconds then, it disappeared and since then, nothing appeared on the screen.
I tried all power clicking combos to get the phone to enter any mode (fastboot or recovery). All of them failed. The screen since then is turned off and the phone does not turn on or enter any mode regardless which buttons I click. I tried:
press and hold power button
keep pressing power button+ vol up
keep pressing power button + vol down
keep pressing power button+ vol up + vol down
All of them failed to turn the phone on, The screen remained completely black.
I thought the device went out of charge so I left it connected to the charger for like 15 minutes. Still this did not affect any thing
Any one knows how can I solve this problem?
Thanks in advance
Click to expand...
Click to collapse
Flash the stock boot image (color is) from the current firmware you are on. Extract it with payload dumper. Flash it the same way you just did. After that your phone should boot normally again. After this take that patched image and instead of doing fastboot flash boot boot.img do fastboot boot boot.img if it boots then open magisk and select install (if warning show up and say magusk need to reboot device ignore and cancel from messenger) then direct install and reboot. This will patch your image from your firmware and not use the one that you booted

lordvoldmort said:
I then put the device on Fastboot mode and used the command: fastboot flash boot boot.img where boot.img is the file I downloaded from the above link----> this resulted into a boot loop
Click to expand...
Click to collapse
this is where you screwed up.
have you tried using the stock recovery?

is there any solution?

My device is non rooted stock version updated latest stable IN andoid 12.1.
It was become dead in my pocket on Saturday. No key combination was working. No response on laptop connection.
I went to service center. It is alive today. Will take delivery today.
Thay told me if water damage then warranty will be void.

Question Install gsi rom on realme 8 pro

Ricedroid 8.6
Unlock the bootloader,
Go to fastboot mode,,
Type
Fastboot reboot bootloader
Fastboot reboot fastboot
Fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
(Vbmeta.img extract from your current stock rom).
Fastboot erase system
Fastboot reboot fastboot
Fastboot flash system system.img
(System.img is downloaded gsi rom and extract the zip and put it in system.img )
Fastboot -w
Fastboot reboot bootloader
Fastboot erase userdata
Fastboot reboot
(After mobile rebooting or go to the recovery mode and you need to format data wipe data in recovery mode).
Installation method of gsi rom
1st you install treble info apk
Then you will see supported or not..
My device is realme 8 pro
I installed currently ricedroid 8.6 arm64- slim bgN
Everything is working properly
Volte working,
(You need to some sitting in treble sitting).
(Go to sitting,
Phh treble sitting,.
Ims features,
Click
Requist ims network,
Presence of 4 g network
Then,
Click install ims apk for qualcomm vendor.
Then apk downloaded,
Then install it.
Facelook working,.
I don't know about fingerprint because before install gsi rom my fingerprint already gone.

I am definitely going to try this. But before I do I need a way to go back to stock rom.
I already have a 8 Pro(IN) bootloader unlocked .
I remember using the ofp flash tool for flashing realme ui 3.0 from 2.0... on my device.

Striker3214 said:
I am definitely going to try this. But before I do I need a way to go back to stock rom.
I already have a 8 Pro(IN) bootloader unlocked .
I remember using the ofp flash tool for flashing realme ui 3.0 from 2.0... on my device.
Click to expand...
Click to collapse
You can revert back to rui in realme 8 pro with this method.
1.) First of all you need
laptop,
Usb data cable,
Minimal adb & fastboot setup,
firmware.
MCT ofp extractor tool.
and Your device.
Download below files.
Firmware:
Download your device Firmware (ofp file).
MCT OFP extractor tool:
https://drive.google.com/file/d/1-MgGdT9fxi2LtJ1DIOxLVSM67thj9EpG/view?usp=drivesdk
Minimal adb & fastboot setup:
ADB & FASTBOOT.rar | by IamNH for Realme 2 Pro
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
2.) Extract the ofp file package by mct ofp extract tool.
3.) Request to unlock your device bootloader by indeapth test apk, once approved then you can start deep testing and unlock bootloader.
4.) connect your device with laptop.
5.) Open minimal adb & fastboot terminal.
and flash this images files by below cmd.
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash metadata metadata.img
fastboot flash opporeserve2 opporeserve2.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
Note: Flash this only 3 super images
fastboot flash super super.0.xxxxxx.img
fastboot flash super super.1.xxxxxx.img
Note: During super 2 flash check super_map.csv file for related country
fastboot flash super super.2.xxxxxx.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vbmeta vbmeta.img
fastboot flash userdata userdata.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot -w
fastboot reboot
Disclaimer: I am not responsible for bricked devices, dead SD cards, etc!
Don't Lock your device bootloader otherwise it will brick and you have to go service centre for fix.