persist.img? - Lenovo Z5 Pro GT Questions & Answers

Does anyone care to share the persist.img from a stock z5 pro GT, and if possible include version number.
did accidentally erase my phone and need this to continue recovery.
Kinf regards

My bad.
The persist.img was in the standard lenovo rom, it just was not flashed when using the QFIL program.
But flashing but fastboot solved the problem.
Code:
adb reboot bootloader
fastboot flash persist persist.img
fastboot flash vbmeta vbmeta.img
fastboot reboot system

it just doesn't work
thorvall said:
My bad.
The persist.img was in the standard lenovo rom, it just was not flashed when using the QFIL program.
But flashing but fastboot solved the problem.
Code:
adb reboot bootloader
fastboot flash persist persist.img
fastboot flash vbmeta vbmeta.img
fastboot reboot system
Click to expand...
Click to collapse
I updated the whole android from 9 to 10 several times but yet it just doesn't work

Related

confused, cannot flash TWRP

Strange, maybe I am missing something but not aware of what...
I've been on Revolution OS and as being curious I gave Android Q a try....means, I flashed "Q" successfully yesterday -through Mi flashing tool- but wasn't happy at all, therefore I went back to Global Dev (again via Mi Flashing tool) to reinstall Revoultion.....Regardless of which TWRP version I' am trying to flash, even after Fastboot is indicating a successful TWRP flash I am not able to access the Recovery. Trying to use adb reboot recovery ends-up in the stock recovery....also fastboot boot recovery.img dosn't help....
even trying to flash the TWRP version I used to install Revolution recerntly does not work.
flyingjack said:
Strange, maybe I am missing something but not aware of what...
I've been on Revolution OS and as being curious I gave Android Q a try....means, I flashed "Q" successfully yesterday -through Mi flashing tool- but wasn't happy at all, therefore I went back to Global Dev (again via Mi Flashing tool) to reinstall Revoultion.....Regardless of which TWRP version I' am trying to flash, even after Fastboot is indicating a successful TWRP flash I am not able to access the Recovery. Trying to use adb reboot recovery ends-up in the stock recovery....also fastboot boot recovery.img dosn't help....
even trying to flash the TWRP version I used to install Revolution recerntly does not work.
Click to expand...
Click to collapse
What I've found is normal commands to boot into recovery do not work for this phone. Boot into fastboot, flash recovery then use volume up and power combination to boot into recovery. Hopefully that will get you back in.
flyingjack said:
Strange, maybe I am missing something but not aware of what...
I've been on Revolution OS and as being curious I gave Android Q a try....means, I flashed "Q" successfully yesterday -through Mi flashing tool- but wasn't happy at all, therefore I went back to Global Dev (again via Mi Flashing tool) to reinstall Revoultion.....Regardless of which TWRP version I' am trying to flash, even after Fastboot is indicating a successful TWRP flash I am not able to access the Recovery. Trying to use adb reboot recovery ends-up in the stock recovery....also fastboot boot recovery.img dosn't help....
even trying to flash the TWRP version I used to install Revolution recerntly does not work.
Click to expand...
Click to collapse
I escaped from the FASTBOOT loop by flashing the FASTBOOT ROM using command.
ROM I used
cepheus_global_images_V10.2.6.0.PFAMIX_20190327.0000.00_9.0_global_9cc39b4570.tgz
The command I used
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash cust cust.img
fastboot flash dtbo dtbo.img
fastboot flash dummy dummy.img
fastboot flash logo logo.img
fastboot flash metadata metadata.img
fastboot flash misc misc.img
fastboot flash persist persist.img
fastboot flash vbmeta vbmeta.img
fastboot flash vendor vendor.img
fastboot erase userdata
fastboot flash userdata userdata.img
fastboot reboot
Finally I found a TWRP version that is working (3.3.0-0423 by wzsx150 -thx mate!) and got back to Revolution OS!!
Thx also for your support!

Fix for "The system has been destroyed" Redmi note 8/8T

Fix for "The system has been destroyed" Redmi note 8/8T
This will only work for unlocked bootloader...this guide will help you recover from the System has been destroyed when trying to install custom rom or recovery or maybe some other actions!
Method 1:
1. Install the .exe from here (PC installation).
2. Download Vbmeta and copy to the installed folder.
3. Connect the phone with PC in Fastboot mode.
4. Run "cmd-here.exe" from the installed folder.
5. Run this command fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
6. Download and Flash recovery using this command fastboot flash recovery recovery.img and Boot to recovery (Vol+ and Power).
7. Flash recovery.zip again in Booted recovery.
If this doesnt work try with the next method
Method 2
If you can enter fastboot screen download stock miui fastboot rom its like 3gb+. and miflash tools and flash remember in miflash tool at the bottom check the
1. clean all: this will still keep bootloader unlocked but wipe everything
2. save user data: will save your data if any and bootloader unlock
3. clean all and lock: wipe everything and will lock bootloader again
NEEDS:
1. A PC and A USB cord for your device
2. MIUI fastboot rom
3. Miflash tools
4. Xiaomi driver and ADB
5. Internet to download files
enweazudaniel said:
For unlocked bootloader only...this guide will help you recover from the System has been destroyed when trying to install custom rom or recovery or maybe some other actions!
SIMPLE SOLUTION:
If you can enter fastboot screen download stock miui fastboot rom its like 3gb+. and miflash tools and flash remember in miflash tool at the bottom check the
1. clean all: this will still keep bootloader unlocked
2. save user data: will save your data if any
3. clean all and lock: will lock bootloader again
NEEDS:
1. A PC and A USB cord for your device
2. MIUI fastboot rom
3. Miflash tools
4. Xiaomi driver and ADB
Click to expand...
Click to collapse
To be fair you dont even need the flash tool having the fastboot rom. Which is really nice if you are not running Windows. Just extract the fastboot package and run the script you need from the folder ( *.sh for mac and linux, bat for windows).
Worked like a charm and fixed my destryoed system.
Or you can flash vbmeta.img (which is just 4 KB) using fastboot mode. Without downloading the entire MIUI fastboot rom (1GB+)
Sent from my Redmi Note 8 using Tapatalk
DailyRoutine said:
Or you can flash vbmeta.img (which is just 4 KB) using fastboot mode. Without downloading the entire MIUI fastboot rom (1GB+)
Click to expand...
Click to collapse
This didn't work for me
Itemt said:
This didn't work for me
Click to expand...
Click to collapse
Maybe you put the wrong command?
It did work for me. Destroyed after flashing custom rom, flash vbmeta, back to normal.
Sent from my Redmi Note 8 using Tapatalk
Itemt said:
This didn't work for me
Click to expand...
Click to collapse
enweazudaniel said:
If you can enter fastboot screen download stock miui fastboot rom its like 3gb+. and miflash tools and flash remember in miflash tool at the bottom check the
1. clean all: this will still keep bootloader unlocked
2. save user data: will save your data if any
3. clean all and lock: will lock bootloader again
Click to expand...
Click to collapse
honestly flashing full fastboot rom isn't required...
Download latest adb and fastboot package
now copy the vbmeta.img file from the fastboot rom into the platform tools folder...open command prompt in this path...connect your device in fastboot mode and flash vbmeta using following command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
after that flash recovery.img.
thanks @the_weird_aquarian, will try it next time if i face this again!
have a good day
Worked
the_weird_aquarian said:
honestly flashing full fastboot rom isn't required...
now copy the vbmeta.img file from the fastboot rom into the platform tools folder...open command prompt in this path...connect your device in fastboot mode and flash vbmeta using following command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
after that flash recovery.img.
Click to expand...
Click to collapse
Wow Thanks a lot. Xiaomi ADBFastbootTool was not working on my systems had tried everything. But thanks to you I was able to boot into recovery within minutes :good:
geekyhellboy said:
Wow Thanks a lot. Xiaomi ADBFastbootTool was not working on my systems had tried everything. But thanks to you I was able to boot into recovery within minutes :good:
Click to expand...
Click to collapse
Happy to help
I wanted to thank you very much because your advice saved my phone
:highfive: :good:
enweazudaniel said:
For unlocked bootloader only...this guide will help you recover from the System has been destroyed when trying to install custom rom or recovery or maybe some other actions!
SIMPLE SOLUTION:
If you can enter fastboot screen download stock miui fastboot rom its like 3gb+. and miflash tools and flash remember in miflash tool at the bottom check the
1. clean all: this will still keep bootloader unlocked
2. save user data: will save your data if any
3. clean all and lock: will lock bootloader again
NEEDS:
1. A PC and A USB cord for your device
2. MIUI fastboot rom
3. Miflash tools
4. Xiaomi driver and ADB
Click to expand...
Click to collapse
Phone not detecting in mi flash tool what should I do now
---------- Post added at 07:49 AM ---------- Previous post was at 07:48 AM ----------
DailyRoutine said:
Or you can flash vbmeta.img (which is just 4 KB) using fastboot mode. Without downloading the entire MIUI fastboot rom (1GB+)
Sent from my Redmi Note 8 using Tapatalk
Click to expand...
Click to collapse
Give vbmeta link or attached file
---------- Post added at 07:50 AM ---------- Previous post was at 07:49 AM ----------
Itemt said:
This didn't work for me
Click to expand...
Click to collapse
Update drivers and try again
Even with the drivers, my phone is no longer recognized on the pc with fastboot, when sending the command, Wait devices...
mudinhu said:
Even with the drivers, my phone is no longer recognized on the pc with fastboot, when sending the command, Wait devices...
Click to expand...
Click to collapse
try this, in mi flashing tool, first send command then connect device
Very Simple to Fix, Just watch my Video on YouTube "Tech Karan"[YT Channel] or Search System has been Destroyed for Redmi Note 8, You'll get Video there.
Hope it helps.
the_weird_aquarian said:
honestly flashing full fastboot rom isn't required...
Download latest adb and fastboot package
now copy the vbmeta.img file from the fastboot rom into the platform tools folder...open command prompt in this path...connect your device in fastboot mode and flash vbmeta using following command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
after that flash recovery.img.
Click to expand...
Click to collapse
Can you give more details about the last step i am trying to go into recovery and cant
the_weird_aquarian said:
honestly flashing full fastboot rom isn't required...
Download latest adb and fastboot package
now copy the vbmeta.img file from the fastboot rom into the platform tools folder...open command prompt in this path...connect your device in fastboot mode and flash vbmeta using following command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
after that flash recovery.img.
Click to expand...
Click to collapse
Yup, this method saved me from a bootloop!!!
RoxtarKaran.RK said:
Very Simple to Fix, Just watch my Video on YouTube "Tech Karan"[YT Channel] or Search System has been Destroyed for Redmi Note 8, You'll get Video there.
Hope it helps.
Click to expand...
Click to collapse
I saw your video, followed link to your zip file. Nothing to download but wave browser and other junk. Lots of thank u comments but no file.
RoxtarKaran.RK said:
Very Simple to Fix, Just watch my Video on YouTube "Tech Karan"[YT Channel] or Search System has been Destroyed for Redmi Note 8, You'll get Video there.
Hope it helps.
Click to expand...
Click to collapse
I found your video and the links are to malware and there are 100 nearly identical videos with the same people thanking different presenters. That is very suspicious sir.
I havew a redmi note 8 global
System has been destroyed after trying to update magisk on Lineage OS
I am unable to boot into "FASTBOOT"
Is there a solution "fix" for that?
I had this happen once before and was able to boot into "fastboot" and fix the problem but this time the only thing I get is "System Has Been Destroyed"
the_weird_aquarian said:
honestly flashing full fastboot rom isn't required...
Download latest adb and fastboot package
now copy the vbmeta.img file from the fastboot rom into the platform tools folder...open command prompt in this path...connect your device in fastboot mode and flash vbmeta using following command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
after that flash recovery.img.
Click to expand...
Click to collapse
unknown option --disable-verity. Can u help me?

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

Realme X2 Pro fastboot/bootloader bootloop

Hi,
I have a Realme X2 Pro RMX1931 EU version with unlocked Bootloader.
Yesterday I was trying to Root it and install TWRP. I Rooted it successfully, but when I tried to install TWRP using Fastboot adb, my phone bricked.
Now I can't go out the fastboot/bootloader mode. OS and Recovery unaccessible.
I've tried to run this commands without any change:
- fastboot -w && fastboot erase system
- fastboot flash boot boot.img
- fastboot flash system system.img
- fastboot flash recovery recovery.img
- fastboot flash vendor vendor.img
- fastboot flash vbmeta vbmeta.img
Any idea or suggestion to solve this problem? Thanks!

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.

Categories

Resources