Develop Bugs

TWRP v3.0.3-0_UNOFFICIAL on Android 7.0 (Nougat) (4.14.401.7)

Hi,
I'm currently on Android 7.0 (Nougat) (4.14.401.7) Stock on my HTC One M9. I tried to install TWRP v3.0.3-0_UNOFFICIAL, but got the following error when trying to reboot to Bootloader mode:
>> adb reboot bootloader
adb server version (31) doesn't match this client (36); killing...
* daemon started successfully *
Then my phone actually entered Bootloader mode anyway, but when I tried to flash TWRP, got this error:
unknown partition 'recovery.img'
error: cannot determine image filename for 'recovery.img'
But I know that the "recovery.img" file was in the same folder. Any ideas on what I'm I doing wrong?
I'm also curious, why is TWRP v3.0.3-0_UNOFFICIAL's size 19,5 MB and the Stock Recovery's size for this Android version is 64,0 MB? Is this kind of size difference normal?

phen0m2016 said:
Hi,
I'm currently on Android 7.0 (Nougat) (4.14.401.7) Stock on my HTC One M9. I tried to install TWRP v3.0.3-0_UNOFFICIAL, but got the following error when trying to reboot to Bootloader mode:
>> adb reboot bootloader
adb server version (31) doesn't match this client (36); killing...
* daemon started successfully *
Then my phone actually entered Bootloader mode anyway, but when I tried to flash TWRP, got this error:
unknown partition 'recovery.img'
error: cannot determine image filename for 'recovery.img'
But I know that the "recovery.img" file was in the same folder. Any ideas on what I'm I doing wrong?
I'm also curious, why is TWRP v3.0.3-0_UNOFFICIAL's size 19,5 MB and the Stock Recovery's size for this Android version is 64,0 MB? Is this kind of size difference normal?
Click to expand...
Click to collapse
Did u input this command:
fastboot flash recovery recovery.img
I think u missed a "recovery" in there.

Can't install Lineage recovery

I did everything on https://wiki.lineageos.org/devices/ginkgo/install , I flashed the recovery, on the Prompt I get "okay" to both Sending and Writing, and on "Now reboot into recovery to verify the installation" my phone is still on fastboot, so I press for a long time the power button to (force?) shut down it, use volume_up+power and what I see is the "Redmi-Recovery 3.0" (stock recovery).
Is it possible to have 2 recovery and I simply don't know how to access the LOS one? Maybe I could have more luck installing TWRP and overwriting it with LOS recovery (how to?)?
From fastboot if I write "fastboot reboot recovery" right after "fastboot flash recovery ..." prompt says "Rebooting into recovery...okay" but then the normal OS is loaded.
If I use
Code:
adb reboot bootloader
I access to the stock fastboot, and from there
Code:
fastboot boot recoveryimagename.img
says
Code:
fastboot: error: cannot load 'lineage-17.1-20201228-recovery-ginkgo.img': No such file or directory
. If I use it from MIUI-OS:
Code:
< waiting for any device >
and Prompt is waiting there.
I have fastboot and recovery image in the same folder but with
Code:
fastboot flash recovery *recovery*
I get
Code:
fastboot: error: cannot load 'lineage-17.1-20201228-recovery-ginkgo.img': No such file or directory
, infact I used full path (full of the img file, not the adb/fastboot which I properly installed) instead of relative, giving the "okay", and after that with
Code:
fastboot boot lineage-17.1-20201228-recovery-ginkgo.img
I get
Code:
fastboot: error: cannot load 'lineage-17.1-20201228-recovery-ginkgo.img': No such file or directory
!
Only now I've seen I was writing from root Prompt and therefore from "C:\WINDOWS\system32>", I used "cd platform-tools_path" and (after
Code:
fastboot flash recovery lineage-17.1-20201228-recovery-ginkgo.img
)
Code:
fastboot boot lineage-17.1-20201228-recovery-ginkgo.img
worked, but now the phone is stuck here!! From prompt everything seems ok. The phone is stuck on the normal loading boot after that "fastboot boot..."! Before I even tried installing TWRP...maybe that was too much? Now?
I used again "fastboot boot lineage-17.1-20201228-recovery-ginkgo.img" and it seems to working...maybe in a couple of minutes(hours probably) I'll mark this as solved!

Ok, I think everything is good now, but I have a question: is it possible to have more than one recovery installed?

BEDBOI2 said:
is it possible to have more than one recovery installed?
Click to expand...
Click to collapse
it is possible on other devices, but until now not possible on ginkgo

Root Failed. Device is Corrupt.

I was trying to root my moto g8 play, as there is no TWRP for my device (at least I didn't find one), I tried a diffrent method:
I got the exact same firmware and extracted the boot.img, patched it using magisk, then installed it on fastboot mode with the commands:
fastboot flash boot_a patched.img
fastboot flash boot_b patched.img
fastboot reboot
After this my device went into a bootloop, I tried fixing it with the commands in the flashfile.xml, but now it just says "Your device is corrupt. It can't be trusted and may not work properly" and doesn't turn on.
Note: Bootloader is unlocked

Is there anything I can do?

Question Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40 brick

So for context I messed up and flashed to boot twrp and now I'm trying to my phone gets out of fastboot but i cant...
So what i did was: "fastboot flash boot_a twrp.img" and "fastboot flash boot_b twrp.img" and now it is stuck on fastboot... so I tried to flash_all.bat from V13.0.8.0.SKHEUXM and V13.0.9.0.SKHEUXM and both gave me this error when this line was executed:
fastboot flash super images\super.img error: cannot load 'images\super.img'
By the way I can still flash twrp into boot and it works but gives many error on mount metadata and root...
So I could use some help to unbrick this phone thank you...

Try the command fastboot continue

Try flashing your ROMs' boot.img in Fastboot.
This tool can dump the individual IMG-files from ROM ZIPs:
[Windows] Payload Dumper GUI - dump boot.img and other img files from payload.bin.
Hello there. Was bored and decided to make a gui that dumps Payload.bin file for easy flashing. Tested on Lineage OS 18 Payload.bin Result: Credits: Based on vm03 payload_dumper script. Github: Payload_dumper.py...
forum.xda-developers.com
Your problem with not being able to run flash_all.bat might be a something with your PC, the SDK Platform Binaries (outdated version?), your USB-cable, your USB-port, or maybe you just need to disconnect/reconnect.
I recommend OrangeFox Recovery: https://orangefox.download/device/alioth
The recovery.img from the ZIP can be booted with fastboot boot recovery.img

Thank for the help guys but I din't try miflash tool tried it and it worked

How do I install Net-Hunter on a OnePlus 8 Pro using OxygenOS/Andriod 13?

How do I install Net-Hunter on a OnePlus 8 Pro using OxygenOS/Andriod 13? The install documentation Net-Hunter images state it uses Android version twelve. Does that mean I must roll back my devices before attempting to flash them? I am very new to rooting devices, so any help is appreciated. I'm using Linux instead of Windows as a daily driver, so the documentation hasnt been so helpful, but here is where I am so far; correct me if I've made a mistake. (I've assumed I had to rollback the Android version but If I do not plz, let me know)
I've unlocked the boot-loader
I've downloaded the OnePlus 8 Pro android 11 firmware onto my laptop(I am not sure if links are allowed here, but ill post in the comments if someone wants to verify its the right one)
I've dumped the payload.bin from the firmware, extracting it into .img files
I then connected my OnePlus 8 Pro to my Linux system and I ran the following commands:
fastboot reboot fastboot fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash qupfw qupfw.img
fastboot flash storsec storsec.img
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vendor vendor.img
The last command gave me the following error: Fix FAILED (remote: 'Not enough space to resize partition')
Like an idiot, I restarted the phone and bricked it, so now it looks like ill have to open a Windows VM with MSMDownloadTool (if anyone knows a Linux alternative, that would be swell)
TLDR:
Do I need to roll back to Android 12 to install Net-Hunter?=
If not, does anyone know of a Linux-friendly method?
If so, what mistake did I make to get that error?
Is there a Linux equivalent to MSMDownloadTool?
SPECS:Laptop: EndeavorOSPhone: OnePlus 8 Pro, NA model, OxygenOS/Andriod 13

Going to document my journey in these comments so I can make a full guide if I figure it out

When I run lsusb the phone shows up as: Bus 001 Device 006: ID 05c6:900e Qualcomm, Inc. QUSB_BULK_SN:B8FAE271.
Research indicates this means the phone is recognized as a Qualcomm device in EDL (Emergency Download) mode. Aparently this mode is used for low-level flashing and unbricking the device using tools like the MSMDownloadTool. But im on Linux....

Reasearch indicates on Linux I can use a tool called qdl to flash Qualcomm devices in EDL (Emergency Download) mode. qdl is a command-line tool that works with Qualcomm Firehose programmers.
However I need the appropriate firmware files for my OnePlus 8 Pro device, which MUST include a programmer (.mbn) file, a rawprogram.xml file, and a set of partition images.

Any luck? . I get monitor mode without injections on internal, it is not recognizing external nics like the tl-wn721n , not getting Bluetooth recognized either. i am on android 12 stock, rooted and flahsed nethunter.zip with magisk . The OP 8 Seems to be very hard to get NHup and running, too bad NetHunter would pair nicely with IR cam