Database Info

Recovery FAIL

Tried to flash CWM recovery, but can't boot to it. I get the dead android with !.
Fastboot claims it's writing recovery fine, but apparently it's not. There are no instructions anywhere.
# fastboot flash recovery recovery-clockwork-touch-6.0.2.3-wingray.img
sending 'recovery' (5104 KB)...
OKAY [ 0.551s]
writing 'recovery'...
OKAY [ 1.958s]
finished. total time: 2.509s
This is a 600.

Well I am at a loss. The download to root the phone is missing from here, so that eliminates my last option.
No wonder hardly anyone's succeeded in getting a ROM onto these.

As I remember you said on another post that you're on Linux... So try using ARP (link on 7Heavens Projekt on my signature) it roots the Xoom, I remember when I turned to Stock my Xoom and tried that, worked fine.
"The past is dead, it was all just a dream" - Magus (Chrono Trigger)

AW: Recovery FAIL
Xoom rooted?
Sent from my MZ601 using xda app-developers app

Need help with bricked Honor 8

EDIT: Guys it worked. Some weird **** happened first, keyboard wasn't working on stock rom and everything was buggy but after an update with HiSuite and a factory reset everything works fine. Thank you for all your support.
I bricked my Honor 8 (FRD-L09) while trying to go back to stock rom. I can only acces eRecovery and Fastboot, when I try to access normal recovery, the screen just freezes at "Your device is booting now". After reading multiple guides, I tried unbricking with the Huawei Multitool but I always get these errors:
sending 'boot' (15464 KB)...
OKAY [ 0.334s]
writing 'boot'...
OKAY [ 0.371s]
finished. total time: 0.710s
target reported max download size of 471859200 bytes
sending 'cust' (433554 KB)...
OKAY [ 9.343s]
writing 'cust'...
FAILED (remote: partition error)
finished. total time: 9.358s
target reported max download size of 471859200 bytes
sending 'recovery' (36996 KB)...
OKAY [ 0.794s]
writing 'recovery'...
OKAY [ 0.883s]
finished. total time: 1.682s
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (435393 KB)...
OKAY [ 10.280s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 10.327s
I'm desperate and I don't know what to do.
EDIT: I HAVE MANAGED TO INSTALL RR BUT STILL CAN'T GO BACK TO STOCK.

Rommco05 said:
Hi, what about twrp u loos access?
Click to expand...
Click to collapse
I have regained access to twrp. I have installed a custom rom, but still can't install stock rom.

Rommco05 said:
Your hole model number is? U try yo flash stock rom via twrp?
Click to expand...
Click to collapse
FRD-L09. I haven't flashed stock rom via TWRP. I tried the huawei extractor method right now, I'm probably doing something wrong, I'll look more into it . I'm calm now that I managed to install a custom rom.

Rommco05 said:
Ok, so if still without luck try to download full stock fw B360 or B381 (2 zips)
Click to expand...
Click to collapse
Ok.. I will try that. My phone is stuck at "your device is booting up" screen after flashing stock recovery.

Note that there is also recovery2 in first update.zip when you extract it via Huawei Multitool. Thats probably why recovery never boots up, it's not all. Try to send the first basic ones - boot, recovery, recovery2, erecovery, and so on (don't exactly remember which). Then you should be fine to dload or flash the rest through fastboot (if possible). And remember to always use full-ota-mf-pv version of software (like FRD-L09C432B381) with about 2.37 GB total (2 zip files).

Rommco05 said:
You can flash back twrp?
Click to expand...
Click to collapse
Yes, I can.

So, did it work?!

PalakMi said:
So, did it work?!
Click to expand...
Click to collapse
I'm at work now. I'll try after a few hours.

Radu Florin said:
I'm at work now. I'll try after a few hours.
Click to expand...
Click to collapse
Good luck, I hope it works after all

Guys it worked. Some weird **** happened first, keyboard wasn't working on stock rom and everything was buggy but after an update with HiSuite and a factory reset everything works fine. Thank you for all your support.

Radu Florin said:
Guys it worked. Some weird **** happened first, keyboard wasn't working on stock rom and everything was buggy but after an update with HiSuite and a factory reset everything works fine. Thank you for all your support.
Click to expand...
Click to collapse
Great , your device is back :highfive:

NXT-L29 TWRP installed without error but isn't accessible

Hi. I unlocked bootloader and flashed twrp via fastboot, but when I try to boot into it, the phone gets stuck at "your phone is booting now". The stock recovery no longer works. The phone's never been updated, still on Android 6.0 and EMUI 4.0. I tried several twrp versions with the same effect. What am I doing wrong? Can dm-verity be somehow interfering with twrp? Any ideas? Thanks in advance.
Code:
fastboot flash recovery twrp-3.0.2-0-next.img
target reported max download size of 471859200 bytes
sending 'recovery' (22020 KB)...
OKAY [ 0.701s]
writing 'recovery'...
OKAY [ 0.129s]
finished. total time: 0.830s

Months later I tried the same, also NXT-L29
Endless:
"Your device has been unlocked and can't be trusted....."
Your device is booting now...
Any solution please?

Lineage os 17.x, 18.x GSI

Hello, someone have bootloader unlocked and Is willing to try Lineage OS?
Here is the roms: Lineage OS 16.x, 17.x, 18.x
Download the a/b versión (treble_arm64_bv)
no root needed or twrp, just bootloader unlocked and a pc.
If someone tried, please let me know!

Did you try to install any GSI rom ???

works with all gsi? so I test

Niick.Ok said:
works with all gsi? so I test
Click to expand...
Click to collapse
Yes, should work with any GSI roms, please Let me know if you tried!

Someone tried this? I dont know how to install the rom, but i've already installed twrp

CæsarAM said:
Someone tried this? I dont know how to install the rom, but i've already installed twrp
Click to expand...
Click to collapse
For install roms, you need the stock recovery.
Here is a mini tutorial If anyone want yo try it!
start the phone in fastboot mode, then connect to the computer via USB.
enter at the PC: fastboot reboot fastboot
when the phone is restarted, fastbootd (look for the “d” at the end of fastboot) should appear.
now type: fastboot flash system image-name.img (e.g. lineage-17.1-20210615-UNOFFICIAL-treble_arm64_bvS.img)
when all this is finished, type: fastboot reboot recovery
in the original recovery, go to delete all data, then restart the phone.
The first start take while, please be patient! Enjoy!

SaocMc said:
For install roms, you need the stock recovery.
Here is a mini tutorial If anyone want yo try it!
start the phone in fastboot mode, then connect to the computer via USB.
enter at the PC: fastboot reboot fastboot
when the phone is restarted, fastbootd (look for the “d” at the end of fastboot) should appear.
now type: fastboot flash system image-name.img (e.g. lineage-17.1-20210615-UNOFFICIAL-treble_arm64_bvS.img)
when all this is finished, type: fastboot reboot recovery
in the original recovery, go to delete all data, then restart the phone.
The first start take while, please be patient! Enjoy!
Click to expand...
Click to collapse
Don't works for this phone, when I flash the system image it says "FAILED (remote: 'Not enough space to resize partition')". I think it's because this device has dynamic partitions

CæsarAM said:
Don't works for this phone, when I flash the system image it says "FAILED (remote: 'Not enough space to resize partition')". I think it's because this device has dynamic partitions
Click to expand...
Click to collapse
yes, because of it, you need to flash via fastbootd
After some research, this could be a posible solution:
flash the stock vbmeta with fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
deleted product partition with fastboot delete-logical-partition product
flash the rom with fastboot flash --u system lineage-17.1-20210615-UNOFFICIAL-treble_arm64_bvS.img
Factory reset from recovery
you can extract the vbmeta file from stock rom, https://mirrors.lolinet.com/firmware/moto/astro/official/

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
same error

I tried to install the gsi roms with the new recovery that they released for this phone and it didn't let me erase the system partition, I couldn't install the gsi image either, none of the three recovery variants that they released worked for me

Niick.Ok said:
I tried to install the gsi roms with the new recovery that they released for this phone and it didn't let me erase the system partition, I couldn't install the gsi image either, none of the three recovery variants that they released worked for me
Click to expand...
Click to collapse
because this device has dynamic partitions, can't install rom via recovery, only via fastbootd, but seems the lineage OS is larger than the system partition of our device, so we need to find a lighter rom or keep searching a solution

What size would the rom need? And another query, how is fastboot mode different from fastbootd mode? I see that the D is attached to the end many

Niick.Ok said:
What size would the rom need? And another query, how is fastboot mode different from fastbootd mode? I see that the D is attached to the end many
Click to expand...
Click to collapse
Basically, Fastbootd is a newer version of fastboot.
fastboot -w (warning : this will wipe all your data)
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
fastboot reboot
This steps are how fusion+ flash GSI roms(Copied from here: https://forum.xda-developers.com/t/rom-11-official-omnirom-liber.4232413/), the boot, dtbo and vmeta files are from stock rom, If anyone wants to try this, please let me know! Remember you need stock recovery and a factory reset after flashing the rom

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system Havoc-OS-v4.1-20210208-arm64-ab-Official.img
target reported max download size of 536870912 bytes
sending sparse 'system_a' 1/6 (458752 KB)...
OKAY [ 14.145s]
writing 'system_a' 1/6...
OKAY [ 2.422s]
sending sparse 'system_a' 2/6 (458752 KB)...
OKAY [ 14.199s]
writing 'system_a' 2/6...
OKAY [ 2.429s]
sending sparse 'system_a' 3/6 (458752 KB)...
OKAY [ 14.093s]
writing 'system_a' 3/6...
FAILED (remote: Operation not permitted)
finished. total time: 47.854s

Niick.Ok said:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system Havoc-OS-v4.1-20210208-arm64-ab-Official.img
target reported max download size of 536870912 bytes
sending sparse 'system_a' 1/6 (458752 KB)...
OKAY [ 14.145s]
writing 'system_a' 1/6...
OKAY [ 2.422s]
sending sparse 'system_a' 2/6 (458752 KB)...
OKAY [ 14.199s]
writing 'system_a' 2/6...
OKAY [ 2.429s]
sending sparse 'system_a' 3/6 (458752 KB)...
OKAY [ 14.093s]
writing 'system_a' 3/6...
FAILED (remote: Operation not permitted)
finished. total time: 47.854s
Click to expand...
Click to collapse
Can you double check that your bootloader is unlocked and you are flashing vía fastbootd?
Some users report that error is caused by the bootloader locked, maybe, somehow your bootloader got locked again.

That's what I thought, when I got that error yesterday I tried to unlock the bootloader again, I tried via fastbootd and it didn't let me, I had to do it from the bootloader menu and there it left me, from fastbootd it told me that it did not know the commands, (summarizing I tried to unlock the bootloader again from the fastbootd menu and it wouldn't let me, so I tried from bootloader and it left me, but it told me that it was already unlocked, any other solution?

I think I already found the problem yesterday when trying to install gsi, yesterday wn fastbootd it appeared (secure boot = yes) I flashed the vbmeta of the official rom and I did not deactivate it, I would need you to pass me a modified vbmeta to flash it and deactivate the secure boot, from there I try to flash again, 2- another possible solution I think would be flashing magisk, see if it manages to pass that verification (secure boot = yes) by modifying the boot. In any case, I would need your help to achieve the modified vbmeta

Niick.Ok said:
I think I already found the problem yesterday when trying to install gsi, yesterday wn fastbootd it appeared (secure boot = yes) I flashed the vbmeta of the official rom and I did not deactivate it, I would need you to pass me a modified vbmeta to flash it and deactivate the secure boot, from there I try to flash again, 2- another possible solution I think would be flashing magisk, see if it manages to pass that verification (secure boot = yes) by modifying the boot. In any case, I would need your help to achieve the modified vbmeta
Click to expand...
Click to collapse
I found this tutorial: https://forum.hovatek.com/thread-32719.html
Method 3 is for flash a empty vmeta and disable verification.
You can try with both, the stock vmeta or the empty one.

I tried everything and I could not, I will wait for a developer to find a way, or for a rom to come out for this cell phone, I already tried the three methods that you sent me and more

SaocMc said:
Can you double check that your bootloader is unlocked and you are flashing vía fastbootd?
Some users report that error is caused by the bootloader locked, maybe, somehow your bootloader got locked again.
Click to expand...
Click to collapse
I get the exact same error no matter the GSI I try, bootloader is unlocked, flashing using fastbootd, I already hate this device...

Fastboot boot TWRP doesn't do anything

I'm trying to flash a custom ROM to my Xiaomi Redmi Note 7 Pro (Unlocked Bootloader)
Here's what i've done so far:
1) Entered Fastboot successfully
2) Typed: C...\platform-tools>fastboot flash recovery twrp-3.5.2_9-0-violet.img
And gotten the respone:
Sending 'recovery' (65536 KB) OKAY [ 1.878s]
Writing 'recovery' OKAY [ 0.462s]
Finished. Total time: 2.357s
3) Typed: C...\platform-tools>fastboot boot twrp-3.5.2_9-0-violet.img
And gotten the response:
Sending 'boot.img' (65536 KB) OKAY [ 1.968s]
Booting OKAY [ 0.143s]
Finished. Total time: 2.172s
This is the part where the phone is supposed to be booted into TWRP Custom Recovery, but instead, nothing happens. The phone is still in fastboot. If I try to reboot it and then reboot into recovery, it boots in the default xiaomi recovery. I've tried older versions of twrp.img files, and nothing works. What am I doing wrong?
Thanks in Advance

After flashing the recovery, try typing fastboot reboot recovery instead. That works without fail for me.

camperbh said:
After flashing the recovery, try typing fastboot reboot recovery instead. That works without fail for me.
Click to expand...
Click to collapse
didn't work, it just rebooted my phone

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Well this is what happens when I type it. You could also try booting to system after flashing and type "adb reboot recovery" instead. Or you could just turn off the phone and go into recovery with power+vol up.

camperbh said:
View attachment 5313135
Well this is what happens when I type it. You could also try booting to system after flashing and type "adb reboot recovery" instead. Or you could just turn off the phone and go into recovery with power+vol up.
Click to expand...
Click to collapse
the same message gets displayed to me, but it doesnt work. Even when I do power+vol up, it just reboots and doesnt go to recovery at all

What about the adb method? Does that work?

camperbh said:
What about the adb method? Does that work?
Click to expand...
Click to collapse
nope

That's all the methods I know of. As a last resort, maybe try flashing your stock rom using miflash and repeat the process to see if it works I guess. This is all the help I can offer, sorry.

camperbh said:
That's all the methods I know of. As a last resort, maybe try flashing your stock rom using miflash and repeat the process to see if it works I guess. This is all the help I can offer, sorry.
Click to expand...
Click to collapse
considering that it doesnt go to twrp neither when typing fastboot boot twrp.img nor when i type fastboot reboot recovery nor when rebooting and typing adb reboot recovery, i feel like the issue is that for some reason it cannot flash the twrp.img file. What's weird though is that it says it successfully flashes it. Anyway, thank you for your time, have a good one

Thinking about it, it could also be a driver issue. Try reainstalling your drivers and see if it works.

camperbh said:
Thinking about it, it could also be a driver issue. Try reainstalling your drivers and see if it works.
Click to expand...
Click to collapse
if you're referring to adb drivers, i tried that. It's updated to the latest version

maxccbvoe said:
I'm trying to flash a custom ROM to my Xiaomi Redmi Note 7 Pro (Unlocked Bootloader)
Here's what i've done so far:
1) Entered Fastboot successfully
2) Typed: C...\platform-tools>fastboot flash recovery twrp-3.5.2_9-0-violet.img
And gotten the respone:
Sending 'recovery' (65536 KB) OKAY [ 1.878s]
Writing 'recovery' OKAY [ 0.462s]
Finished. Total time: 2.357s
3) Typed: C...\platform-tools>fastboot boot twrp-3.5.2_9-0-violet.img
And gotten the response:
Sending 'boot.img' (65536 KB) OKAY [ 1.968s]
Booting OKAY [ 0.143s]
Finished. Total time: 2.172s
This is the part where the phone is supposed to be booted into TWRP Custom Recovery, but instead, nothing happens. The phone is still in fastboot. If I try to reboot it and then reboot into recovery, it boots in the default xiaomi recovery. I've tried older versions of twrp.img files, and nothing works. What am I doing wrong?
Thanks in A
Click to expand...
Click to collapse
maxccbvoe said:
I'm trying to flash a custom ROM to my Xiaomi Redmi Note 7 Pro (Unlocked Bootloader)
Here's what i've done so far:
1) Entered Fastboot successfully
2) Typed: C...\platform-tools>fastboot flash recovery twrp-3.5.2_9-0-violet.img
And gotten the respone:
Sending 'recovery' (65536 KB) OKAY [ 1.878s]
Writing 'recovery' OKAY [ 0.462s]
Finished. Total time: 2.357s
3) Typed: C...\platform-tools>fastboot boot twrp-3.5.2_9-0-violet.img
And gotten the response:
Sending 'boot.img' (65536 KB) OKAY [ 1.968s]
Booting OKAY [ 0.143s]
Finished. Total time: 2.172s
This is the part where the phone is supposed to be booted into TWRP Custom Recovery, but instead, nothing happens. The phone is still in fastboot. If I try to reboot it and then reboot into recovery, it boots in the default xiaomi recovery. I've tried older versions of twrp.img files, and nothing works. What am I doing wrong?
Thanks in Advance
Click to expand...
Click to collapse
The first method. I also had a problem after flashing "fastboot flash recovery twrp.img it says successfully but when I try to go to recovery by holding button + volume it cannot proceed it shows black screen but the phone did not get bootloop.
2nd method : I've also tried by using a command " fastboot boot recovery twrp.img " it shows the the command I use is invalid argument . For those who already root their phone Redmi 9t plsss reply about this issue plsss plssss