I recently rolled back to the factory image to install the OTA 4.4 update (Sprint). I had an unlocked bootloader prior to the update and when I boot into recovery my device tells me I'm unlocked. I downloaded the TWRP image and used the following command from the boot loader:
Code:
mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
When I run that command (I also tried "fastboot" in addition to mfastboot), it looks like everything worked OK but when I choose the "recovery" option from the bootloader my device boots into Android instead of into the recovery rom. When I try:
Code:
adb reboot recovery
My device displays the "No Command" recovery screen, as if it were booted using the stock Android recovery image instead of TWRP.
Am I missing a step somewhere to get TWRP on my device?
danherbert said:
I recently rolled back to the factory image to install the OTA 4.4 update (Sprint). I had an unlocked bootloader prior to the update and when I boot into recovery my device tells me I'm unlocked. I downloaded the TWRP image and used the following command from the boot loader:
Code:
mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
When I run that command (I also tried "fastboot" in addition to mfastboot), it looks like everything worked OK but when I choose the "recovery" option from the bootloader my device boots into Android instead of into the recovery rom. When I try:
Code:
adb reboot recovery
My device displays the "No Command" recovery screen, as if it were booted using the stock Android recovery image instead of TWRP.
Am I missing a step somewhere to get TWRP on my device?
Click to expand...
Click to collapse
So after flashing recovery did you try to access twrp prior to rebooting to the system?
Sent on my Moto X
flashallthetime said:
So after flashing recovery did you try to access twrp prior to rebooting to the system?
Click to expand...
Click to collapse
Yes. I've tried accessing recovery directly from the fastboot menu immediately after flashing.
danherbert said:
Yes. I've tried accessing recovery directly from the fastboot menu immediately after flashing.
Click to expand...
Click to collapse
OK, you're going to hate this but you need to rsdlite your carriers kitkat sbf firmware, its happened to more than a few people including me, recovery just won't stick after taking an ota for some folks
Sent on my Moto X
flashallthetime said:
OK, you're going to hate this but you need to rsdlite your carriers kitkat sbf firmware, its happened to more than a few people including me, recovery just won't stick after taking an ota for some folks
Click to expand...
Click to collapse
Your suggestion worked. I didn't have easy access to a Windows machine so I couldn't use rsdlite. I had to manually reset to stock. For anyone who stumbles upon this thread, these are the steps I used which worked for me:
Make sure adb and fastboot from the Android SDK are already part of your PATH.
Download moto-fastboot for Mac OS X
Download the Kitkat 4.4 update for Sprint (Make sure to download the version that matches the build number from "Settings -> About Phone" in your device)
Download the Kitkat 4.4 version of TWRP
Extract the factory image .zip to a folder
Copy the moto-fastboot binary to the folder you extracted the factory image to and rename it to "mfastboot"
Copy the TWRP .img file to the folder with the factory image files
Create a file named "factoryreset.sh" and paste the following as its contents
Code:
#!/bin/sh
FASTBOOT=./mfastboot
$FASTBOOT getvar max-download-size
$FASTBOOT oem fb_mode_set
$FASTBOOT flash partition gpt.bin
$FASTBOOT flash motoboot motoboot.img
$FASTBOOT flash logo logo.bin
$FASTBOOT flash boot boot.img
$FASTBOOT flash recovery recovery.img
$FASTBOOT flash system system.img
$FASTBOOT flash modem NON-HLOS.bin
$FASTBOOT erase modemst1
$FASTBOOT erase modemst2
$FASTBOOT flash fsg fsg.mbn
$FASTBOOT erase cache
$FASTBOOT erase userdata
$FASTBOOT erase customize
$FASTBOOT erase clogo
$FASTBOOT oem config carrier sprint
$FASTBOOT oem fb_mode_clear
Open a terminal and navigate to the directory you created
On your device, navigate to "Settings -> About Phone" and tap on the build number 7 times to enable developer mode
Go back to the main "Settings" screen, open "Developer Options", and enable USB Debugging
Connect your device to your computer. Go back to your device, make sure you choose to trust your computer to use ADB in the dialog that pops up, then run the following command from your terminal
Code:
adb reboot-bootloader
Once your device is in fastboot mode, run the command
Code:
sh factoryreset.sh
From the device choose to boot normally and wait for it to finish booting completely.
Run the command
Code:
adb reboot-bootloader
Once the device is in fastboot mode again, run the command
Code:
fastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
From your device, power up normally then reboot into the recovery. If everything went smoothly you'll boot into TWRP recovery.
Code:
adb reboot recovery
Please gve the fastboot command for Oreo for flashing
Boot.img
Recovery.img
System.img
...........................,.......,..........
These comments are not working
Fastboot flash boot
Fastboot flash recovery
Please help me
Curious8 said:
Please gve the fastboot command for Oreo for flashing
Boot.img
Recovery.img
System.img
...........................,.......,..........
These comments are not working
Fastboot flash boot
Fastboot flash recovery
Please help me
Click to expand...
Click to collapse
The fastboot commands you are executing are lacking the image file and have the incorrect partition target.
Code:
fastboot flash ramdisk "boot-image-filename.img"
fastboot flash recovery_ramdisk "recovery-image-filename.img"
fastboot flash system "system-image-filename.img"
fastboot flash vendor "vendor-image-filename.img"
@Curious8
If you will flash anything - it' a good idea you have FULL-Update from your Build on your PC !
Find FULL-Update with HuaweiFirmwareFinder and download.
Extract with HuaweiExtractor from Update.app (inside Update.zip) 3 img : ramdisk.img, recovery_ramdis.img, system.img
The Extractor do automatic 3 *.img.header. This 6 files copy to your ADB-Folder.
NOW you can flash any developer-rom. If this not work reset your phone to stock-rom with
- fastboot flash ramdisk ramdisk.img
- fastboot flash recovery_ramdisk recovery_ramdis.img
- fastboot flash system system.img
this help for self-repair if
- bootloader unlocked
- FRP unlock
the commands you write is for Android older OREO ! With OREO we have new Partition-Names and new commands.
Hello I have this problem with my realme X2 Pro
I wanted to install TWRP on my phone using ADB and Fastboot after unlocking with success my bootloader The problem Is I first intalled with success TWRP BUT the touch was not working so I decieded to try a newer version but now this error apears
Sending 'recovery' (98304 KB) OKAY [ 2.354s]
Writing 'recovery' FAILED (remote: 'Error flashing partition : Volume Full')
fastboot: error: Command failed
I Tried to do adb push twrp-3.4.0-0-RMX1931-mauronofrio.img /dev/block/bootdevice/by-name/recovery but i did not work It got me this error
adb: error: failed to get feature set: no devices/emulators found
If anyone could help me it would very apreciated
I though it was (from Fastboot mode):
Code:
fastboot flash recovery <your recovery image here>
and then
Code:
fastboot flash vbmeta vbmeta.img
Uqbar said:
I though it was (from Fastboot mode):
Code:
fastboot flash recovery <your recovery image here>
and then
Code:
fastboot flash vbmeta vbmeta.img
Click to expand...
Click to collapse
Hello when I try to use fastboot flash recovery twrp.img that is creating the Volume full error
How can I solve it ?
Farchyk said:
Hello when I try to use fastboot flash recovery twrp.img that is creating the Volume full error
How can I solve it ?
Click to expand...
Click to collapse
Are you really really sure the twrp image is the right size?
Mauronofrio's one is exactly 81920 KB, not 98304 KB.
Also the official TWRP has the same size, AFAIK.
I would re-download it and maybe checksum it.
How to unlock the Realme 8 Pro bootloader?
1. you'd better write in english, to get a broader range of people who understand you question ;-).
2. Also waiting for that ... it's a shame.
Greetz
Kurt
How to unlock bootloader realme 8 5G
Answer from [email protected] from today :
Unlock Bootloader tutorial for Realme 8 Pro RMX3081 is not available as of now.Further, keep following our social media handles and official community portal for the latest updates,
Yeah, we can achieve the bootloader unlock of realme 8 pro. Mine is unlocked. The build number and security patch must be (RMX3081_11_A.44) (November 5,2021)
This is Export rom not the GDPR rom (EU)
Have flashed it and can unlock and flash files via fastboot.
OFP - Original Firmware Project :
Code:
Model Project Project ID Download link
RMX3081 20711 (Project ID-20711)_INDIA,MM,BD,PK RMX3081export_11_A.44 https://fileload.coloros.com/504197RMX3081export_11_A.44_2021110921030235.zip
RMX3081 20712 (Project ID-20712)_PH,VN,KH,-EG,IQ,MY RMX3081export_11_A.44 https://fileload.coloros.com/504198RMX3081export_11_A.44_2021110921100000.zip
RMX3081 20713 (Project ID-20713)_LUX,CH,ES,UK,FR,IT,DE,NL,BE,NO,PT,FIN,CY RMX3081GDPR_11_A.44 https://fileload.coloros.com/504200RMX3081GDPR_11_A.44_2021110921090000.zip
RMX3081 20713 (????) RMX3081export_11_A.44 https://fileload.coloros.com/504199RMX3081export_11_A.44_2021110921060000.zip
RMX3081 20714 (????) RMX3081export_11_A.44 https://fileload.coloros.com/504201RMX3081export_11_A.44_2021110921110000.zip
@Shibu Shaji share us the
getprop ro.build.display.full_id
Yeah, we can achieve the bootloader unlock of realme 8 pro. Mine is unlocked. The build number and security patch must be (RMX3081_11_A.44) (November 5,2021)
StratOS_HTC said:
This is Export rom not the GDPR rom (EU)
Have flashed it and can unlock and flash files via fastboot.
OFP - Original Firmware Project :
Code:
Model Project Project ID Download link
RMX3081 20711 (Project ID-20711)_INDIA,MM,BD,PK RMX3081export_11_A.44 https://fileload.coloros.com/504197RMX3081export_11_A.44_2021110921030235.zip
RMX3081 20712 (Project ID-20712)_PH,VN,KH,-EG,IQ,MY RMX3081export_11_A.44 https://fileload.coloros.com/504198RMX3081export_11_A.44_2021110921100000.zip
RMX3081 20713 (Project ID-20713)_LUX,CH,ES,UK,FR,IT,DE,NL,BE,NO,PT,FIN,CY RMX3081GDPR_11_A.44 https://fileload.coloros.com/504200RMX3081GDPR_11_A.44_2021110921090000.zip
RMX3081 20713 (????) RMX3081export_11_A.44 https://fileload.coloros.com/504199RMX3081export_11_A.44_2021110921060000.zip
RMX3081 20714 (????) RMX3081export_11_A.44 https://fileload.coloros.com/504201RMX3081export_11_A.44_2021110921110000.zip
@Shibu Shaji share us the
getprop ro.build.display.full_id
Click to expand...
Click to collapse
Here is my id : RMX3081export_11_A.44_2021110921030235
Yeah, see it's exported Project ID-20711 and don't have a bootloader locked.
Have flashed it previously and know that.
The GDPR versions of ROM you cannot do almost nothing 4 now.
Oh bro, this is not GDPR version.. After I unlocked my bootloader, i tried to root realme 8 pro with patched boot image from OFP Rom but it's doesn't work for me..
Any thing to say about this?
StratOS_HTC said:
Yeah, see it's exported Project ID-20711 and don't have a bootloader locked.
Have flashed it previously and know that.
The GDPR versions of ROM you cannot do almost nothing 4 now.
Click to expand...
Click to collapse
Well let me guide you throught it :
Get the firmware in zip
Extract the boot.img and vbmeta files from the opf file.
adb reboot bootloader
fastboot flashing unlock (Unlock bootloader)
*fastboot flashing unlock_critical
Use magisk to patch the boot.img use patched image as boot.img
fastboot –disable-verity –disable-verification flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot reboot
or use it with --force additional option
after finish it give feedback, please.
If successfull go back fo fastbootd mode and provide me with two files fetched from the system
fetch could be limited in fastboot
fastboot fetch vbmeta vbmeta.xxx
fastboot fetch vbmeta_system vbmeta_system.xxx
U can get it via adb (I guess)
adb pull /dev/block/sde18 vbmeta
adb pull /dev/block/sde16 vbmeta_system
Since jour project id is 20711
Guess your PCB shows 0020711*
dial : *#899#
press the PCB num
StratOS_HTC said:
Well let me guide you throught it :
adb reboot bootloader
fastboot flashing unlock (Unlock bootloader)
Get the firmware in zip
Extract the boot.img and vbmeta files from the opf file.
Use magisk to patch the boot.img use patched image as boot.img
fastboot –disable-verity –disable-verification flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
StratOS_HTC said:
Well let me guide you throught it :
Get the firmware in zip
Extract the boot.img and vbmeta files from the opf file.
adb reboot bootloader
fastboot flashing unlock (Unlock bootloader)
*fastboot flashing unlock_critical
Use magisk to patch the boot.img use patched image as boot.img
fastboot –disable-verity –disable-verification flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot reboot
or use it with --force additional option
after finish it give feedback, please.
If successfull go back fo fastbootd mode and provide me with two files fetched from the system
fetch could be limited in fastboot
fastboot fetch vbmeta vbmeta.xxx
fastboot fetch vbmeta_system vbmeta_system.xxx
U can get it via adb (I guess)
adb pull /dev/block/sde18 vbmeta
adb pull /dev/block/sde16 vbmeta_system
Click to expand...
Click to collapse
Yeah , tried but nothing seems to be work.
StratOS_HTC said:
Well let me guide you throught it :
Get the firmware in zip
Extract the boot.img and vbmeta files from the opf file.
adb reboot bootloader
fastboot flashing unlock (Unlock bootloader)
*fastboot flashing unlock_critical
Use magisk to patch the boot.img use patched image as boot.img
fastboot –disable-verity –disable-verification flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot reboot
or use it with --force additional option
after finish it give feedback, please.
If successfull go back fo fastbootd mode and provide me with two files fetched from the system
fetch could be limited in fastboot
fastboot fetch vbmeta vbmeta.xxx
fastboot fetch vbmeta_system vbmeta_system.xxx
U can get it via adb (I guess)
adb pull /dev/block/sde18 vbmeta
adb
Click to expand...
Click to collapse
StratOS_HTC said:
Well let me guide you throught it :
Get the firmware in zip
Extract the boot.img and vbmeta files from the opf file.
adb reboot bootloader
fastboot flashing unlock (Unlock bootloader)
*fastboot flashing unlock_critical
Use magisk to patch the boot.img use patched image as boot.img
fastboot –disable-verity –disable-verification flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot reboot
or use it with --force additional option
after finish it give feedback, please.
If successfull go back fo fastbootd mode and provide me with two files fetched from the system
fetch could be limited in fastboot
fastboot fetch vbmeta vbmeta.xxx
fastboot fetch vbmeta_system vbmeta_system.xxx
U can get it via adb (I guess)
adb pull /dev/block/sde18 vbmeta
adb pull /dev/block/sde16 vbmeta_sys
Click to expand...
Click to collapse
StratOS_HTC said:
Well let me guide you throught it :
Get the firmware in zip
Extract the boot.img and vbmeta files from the opf file.
adb reboot bootloader
fastboot flashing unlock (Unlock bootloader)
*fastboot flashing unlock_critical
Use magisk to patch the boot.img use patched image as boot.img
fastboot –disable-verity –disable-verification flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot reboot
or use it with --force additional option
after finish it give feedback, please.
If successfull go back fo fastbootd mode and provide me with two files fetched from the system
fetch could be limited in fastboot
fastboot fetch vbmeta vbmeta.xxx
fastboot fetch vbmeta_system vbmeta_system.xxx
U can get it via adb (I guess)
adb pull /dev/block/sde18 vbmeta
adb pull /dev/block/sde16 vbmeta_system
Click to expand...
Click to collapse
Yeah i tried the steps that u said above to ROOT realme 8 pro, but it doesn't work for me... here are the steps that i did.
Fastboot mode
*Fastboot flashing unlock
*Fastboot --disable-verity --disable-verification
flash vbmeta vbmeta.img
*Fastboot flash boot (magisk patched) boot.img
Result : Device went to bootloop. Retrieved from
bootloop by flashing stock boot image that previously extracted from OFP file and now the device is fine.
Also tried this step
Fastboot mode
*Fastboot flashing unlock
*Fastboot --disable-verity --disable-verification
flash vbmeta vbmeta.img
* Fastboot --disable-verity --disable-verification
flash vbmeta_system vbmeta_system.img
*Fastboot --disable-verity --disable-verification
flash vbmeta_vendor vbmeta_vendor.img
*Fastboot flash boot (magisk patched) boot.img
Result : Bootlooped. Retrieved by flashing stock boot image..
And also, i tried to BOOT patched boot image... and it shows
FAILED <remote: unknown command>
ABV is still active.
THX @Shibu Shaji
For showing us the 20711 EXPORT .44 ROM fastboot getvar all infos.
I have also the 20713 GDPR .44 ROM fastboot getvar all infos.
The bootloader in EXPORT is unlocked and is not userspaced.
From green to orange state ... some progress after all ...
It seems your bootloader unlocked? actually how? I think ur AVB is now disabled
StratOS_HTC said:
View attachment 5505451
From green to orange state ... some progress after all ...
Click to expand...
Click to collapse
Wow, how did you do it?
currently via isp ufs access and help of a reversing from a friend.
On bootloop also ...
Oh bro, So what to do next? Is there any other problems with ur partitions after this?
Since EDL is not configured correctly (No kernel driver supported: Operation not supported or unimplemented on this platform) after the firehose programmer sucessfully boot ...
Also QFIL and unimplemented <CONFIGURE> or <SIG> and signed and certed things the only thing to do is via ISP UFS control.
OR possible USB port communication debug via MSM flash.
For EXPORT version have prepared seen action on the screen for this ROM
Code:
Project 20711
RMX3081
Version Flash MSM download tool v.2.0.51 for eMMC/UFS
Rom ofp : RMX3081export_11_A.28_202104090210
Server : India
Use default NV=yes
Reboot on finish=yes
Download Firehose protocol file
Sahara communication succeeded
Boot via firehose
Trying to handshake
Get sign data
Verify data
Getting NV code from server
Failed to get NV code. Default NV code would be used
Firehose GetUfsInfo
Erasing the partition Primarly GPT
Erasing the partition BackupGPT
Erasing the partition userdata
Downloading cdt_engineering_release.img
Erasing partition keystore
Downloading cache.img
Downloading recovery.img
Downloading metadata.img
Downloading userdata.img
Downloading gpt_main0.bin
Downloading xbl.elf
Downloading gpt_main1.bin
Downloading gpt_main2.bin
Downloading aop.mbn
Downloading tz.mbn
Downloading NON-HLOS.bin
Erasing the partition mdtpsecapp
Erasing the partition mdtp
Downloading abl.elf
Downloading dspso.bin
Downloading boot.img
Downloading devcfg.mbn
Downloading vbmeta_vendor.img
Downloading dtbo.img
Downloading imagefv.elf
Downloading oppo_sec.mbn
Downloading dpAP.mbn
Erasing the partition spunvm
Downloading splash.img
Downloading logfs_ufs_8mb.bin
Erasing the partition cateloader
Erasing the partition rawdump
Erasing the partition logdump
Download multi_image.mbn
Erasing the partition catefv
Downloading gpt_main4.bin
Download static_nvbk.bin
Erasing the partition opporeserve1
Downloading emmc_fw.bin
Downloading DRIVER.ISO
Downloading gpt_main5.bin
Restarting
Downloading Firehose protocol file
Sahara communication succeeded
Trying to handshake via Firehose
Configure the settings of Firehose
Get sign data
Verify data
Downloading super partsuper.0
Downloading super partsuper.1
Downloading super partsuper.2
Get basic data
Write patch image to user partition
Restarting
Download succeeded
Get sign data
Verify data
Currently non-implemented/documented also by MSM7125 ?
Hello,
After unlock his bootloader, I try to install TWRP recovery on my smartphone with :
Bash:
fastboot flash recovery twrp.img
Bash:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
But he reboot always on the fastboot mode when I push simultaneously on power and volume + and when I don't push on any button.
I use these file :
twrp.img
vbmeta.img
Thanks for your help .
TWRP by brigudav- i flashed only twrp renamed to recovery.img and patched os via that stock recovery will not back.
Rename the file change nothing to me.
As information, when I try in try
Bash:
fastboot boot recovery.img
i get :
Bash:
FAILED (remote: unknown command)
in fastboot
and
Bash:
FAILED (remote: Unrecognized command boot)
in fastbootd
I've test lineage recovery and that's the same : impossible to boot on other recovery except the stock MI-Recovery 3.0 .
I get the exactly same errorwhile try booting twrp.img is there no custom recovery for lime that works?
GrandTouque said:
Hello,
After unlock his bootloader, I try to install TWRP recovery on my smartphone with :
Bash:
fastboot flash recovery twrp.img
Bash:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
But he reboot always on the fastboot mode when I push simultaneously on power and volume + and when I don't push on any button.
I use these file :
twrp.img
vbmeta.img
Thanks for your help .
Click to expand...
Click to collapse
The twrp image is just for another device, for davinci and not for lime. But i got the same problem with correct twrp image
ex-it said:
The twrp image is just for another device, for davinci and not for lime. But i got the same problem with correct twrp image
Click to expand...
Click to collapse
You are right, I try to flash a unofficial TWRP that I found at this thread and now I've just a black screen when I boot on it but I can now boot on the OS with this "recovery".
Finally, I've found this one on this thread who works .