Develop Bugs

Soft Bricked: No recovery, only fastboot

I did a CM nightly Update, which relocked my phone. I tried to unlock it but something went wrong. I can flash partitions but somehow can't boot into anything besides fastboot. When I try to boot into any recovery (even Stock) the phone just restarts after showing the Oppo logo for a moment. (Just as if I was trying to boot a custom rom from a locked device)
OEM-Info:
Code:
fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.005s]
finished. total time: 0.005s
Booting a recovery.img (Same reaction for every recovery):
Code:
fastboot boot twrp-2.8.7.2-find7.img
downloading 'boot.img'...
OKAY [ 0.355s]
booting...
OKAY [ 0.013s]
finished. total time: 0.368s
Phone Just reboots into a boot loop.
Flashing anything works fine but I'm getting boot loops again.
A strange thing that happens is that if i try
Code:
fastboot oem lock
the process just get's stuck showing three dots. (Same on Windows and Linux) That probably means that the bootloader is in some buggy way half way locked. (That sadly doesn't explains why the stock recovery won't work)
No idea how to fix it. Thank you in advance!
Jakob

Amazing tool here: forum.xda-developers.com/find-7/development/recovery-recovery-installer-7-t2819794

Hey !! I solved the pblm!!! what I did was just hit and trial but it worked. Now I will give the method:
Follow these steps and see if u are lucky enough!
step1: go to fastboot mod in your oppo f1
step2: flash stock recovery using adb. Type in "fastboot flash recovery stock.img"
step3: do not reboot your device and type in "fastboot flashing lock_critical".
step4: type in "fastboot reboot"
After these 4 steps I was able to boot back in Project spectrum. I haven't checked until that if I m able to go to recovery mode but I will update once I check. Check if you can boot.
Note: keep the stock.img file in the same folder in which you have your adb installed.
And I am not sure if this will work for you also.. but it is safe so go give a try!!!
THIS WORKED FOR OPPO F1f YOU CAN TRY YOUR LUCK BY USING THIS METHOD
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Help with HTC D728H

Hi guys,
My friend's HTC Desire D728H is stuck in a boot loop. I tried the following without success:
- Downloaded the Stock Flash for it (2PQ8IMG_A50CMG_DWG_L51_DESIRE_SENSE70_HTC_Europe_1.09.401.2_Radio_NA_release_482339_signed_2_4.zip) and tried to update from SD card from Download menu, didn't work. Tried flashing it with RB Soft, it gets to just before the end of the progress bar and then the phone reboots into the same boot loop.
There is no fastboot mode in the recovery menu. So I started the phone in download mode. From the command prompt on my Windows PC, typed Fastboot Devices and the PC detects it as LC5C3Z703897.
I cannot enable OEM Unlocking cos the phone won't boot.
I have HTC drivers installed.
adb in command prompt does not detect the phone.
I can boot it in RUU mode.
if I try to get the Token to unlock bootloader, it returns the following error:
(bootloader) [KillSwitch] : /dev/block/platform/mtk-msdc.0/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.006s]
finished. total time: 0.007s
As far as I know the phone has a stock rom, bootloader locked with S-ON.
How can I flash this phone and get it working again? I don't have lots of experience with HTC phones, so please provide me with details.
Thank you All in advance.

No one?

kfhd 8.9 2nd gen rebooting

hi i hope someone can help me the problem is the kindle keeps rebooting and i cant get to access twrp it only goes to blue screen teamwin and just stays there i can get fastboot to work but thats about all
i think it has twrp-2.6.0.0 and cyanogenmod but thats all i know as im trying to fix it for a friend any suggestions or help would be much appreciated thank you
updae
update
ok this is what I've tried KFHD System.img Recovery Tool which is not doing any good
I've selected option 2 restore-su/supersu.apk this says writing 'system'...
FAILED (remote: : Write partition)
tried various different versions with no luck all saying failed
i have erase cache and user data
ive tried fastboot -i 0x1949 getvar product
fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
fastboot -i 0x1949 flash boot boot.img
Fastboot -i 0x1949 flash recovery recovery.img
fastboot -i 0x1949 flash system system.img
target reported max download size of 1006632960 bytes
sending 'system' (907264 KB)...
OKAY [ 48.735s]
writing 'system'...
FAILED (remote: : Write partition)
finished. total time: 50.907s
I've just been trying and trying
when i try adb devices while stuck on twrp teamwin screen
i get List of devices attached
B0C910013086074C unauthorized
so i cant use any adb commands
could this be that development options has been turned off in the settings sometimes it does load up but i cant do anything as i get loads of pop ups on the screen something to do with google has stopped report or ok avg has stopped and ect so i press ok and this constantly happens it then switches off and goes back on the blue android and stays there is there any way to recover from fastboot or delete the apps what's on there using fastboot any help would be appreciated thank you for your time

Can't boot TWRP via "fastboot boot" after upgrade (OOS boots fine)

Hi,
TL;DR: Bootloader unlocked. "fastboot boot twrp.img" worked fine until I upgraded to OxygenOS 5.1.4 (from 5.0.4). Now "fastboot boot twrp.img" just does nothing.
I had a OxygenOS system (Android 8.0, I believe it was OOS 5.0.4), rooted with Magisk. Everything was fine. Stock recovery, I wanted to change it as little as possible. I could use twrp-3.2.1-x_blu_spark_v8.70-op5_op5t.img perfectly, via "flashboot boot /path/to/img".
Today I decided to upgrade. I had an OTA notification for months, for OOS 5.1.4 (Android 8.1). I made a full backup with TWRP. Read about latest ROMs, seems 5.1.6 has some Bluetooth issues.
I opened the 5.1.4 OTA notification, curious to read the Changelog. A message said I had a rooted phone, and the update would install a full version instead of the OTA. Also, I'd lose root. Nothing I didn't expect, but I still wanted to flash with TWRP. Unfortunately, the updater had already downloaded the ROM and suddenly restarted. I did not want to interrupt the update, so let it go through.
Phone booted on OOS 5.1.4 without problems. Unrooted, of course. I went into fastboot mode, and tried loading TWRP with "flashboot boot /path/to/twrp-3.2.1-x_blu_spark_v8.70-op5_op5t.img". The image gets downloaded, and boot takes about 10s (most of which is a warning message that my bootloader is unlocked). After that, I just drop back to the 1+ bootloader screen. If I then try repeating the same "flashboot boot ..." command, I get the error "FAILED (remote: 'Failed to load/authenticate boot image: 00000050')".
I tried:
Several TWRP versions, from Blu_Spark, Codeworkx and siankatabg. Don't remember all of them, but at least the latest ones, i.e. twrp-3.2.3-x_blu_spark_v9.85_treble-op5_op5t.img, twrp-3.2.3-0-20180822-codeworkx-dumpling.img and TWRP_3.2.3-Pie_siankatabg_OP5.img.
Removing the screen pattern, lock screen None.
Upgrading to OOS 5.1.6 via stock recovery.
Different USB cable.
I can boot the phone to the OS just fine. But without TWRP I cannot flash Magisk, to root the phone. I have not tried flashing TWRP to recovery, because at least I know stock recovery works and don't want to lose that.
This is what I have from device-info (did not change from before the upgrade, when TWRP was working):
Code:
$ ./fastboot oem device-info
(bootloader) Verity mode: enforcing
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) enable_dm_verity: true
(bootloader) have_console: false
(bootloader) selinux_type: SELINUX_TYPE_INVALID
(bootloader) boot_mode: NORMAL_MODE
(bootloader) kmemleak_detect: false
(bootloader) force_training: 0
(bootloader) mount_tempfs: 0
OKAY [ 0.001s]
Finished. Total time: 0.001s
This is how I'm trying to boot TWRP. From the OS, I hold the power button, press Reboot, then choose Bootloader (I have advanced reboot enabled). That takes me to a pretty screen with a menu and options to start the OS, boot to recovery, or restart bootloader. I can select using the volume up and volume down keys, but I just ignore the options and type the fastboot commands:
Code:
$ ./fastboot devices
<redacted> fastboot
$ ./fastboot boot ~/Android/OnePlus5t/TWRP/twrp-3.2.3-x_blu_spark_v9.85_treble-op5_op5t.img
Downloading 'boot.img' OKAY [ 0.819s]
booting OKAY [ 10.106s]
Finished. Total time: 10.936s
The 10s is basically the Android warning message saying the boot loader is unlocked and the data cannot be trusted. I get that when booting to normal OS as well. After that warning goes away, instead of getting TWRP, I just get a black screen with "1+ Bootloader".
In that screen, I can still type fastboot commands, but now I have a different error:
Code:
$ ./fastboot boot ~/Android/OnePlus5t/TWRP/twrp-3.2.3-x_blu_spark_v9.85_treble-op5_op5t.img
Downloading 'boot.img' OKAY [ 0.822s]
booting FAILED (remote: 'Failed to load/authenticate boot image: 00000050')
Finished. Total time: 0.835s
I'm at a loss here. Can someone help? I've considered trying out the RedWolf alternative thing, but am worried it might mess with encryption or something. I could flash TWRP, but really worry that 1) if it doesn't work, I won't have any recovery at all, and 2) I'd like to keep the stock recovery as a fallback.

This could perhaps be more of a question for the developers? I posted here because I was not allowed to post in the "OnePlus 5T ROMs, Kernels, Recoveries, & Other Development" section.

[Redmi Note 8] Unable to boot to recovery or fastboot (System has been destroyed)

Redmi note 8 (unlocked bootloader) stuck on "Your system has been destroyed" (I was trying to install PixelExperience 12, but was not able to boot into the PitchBlack recovery itself). Unable to boot to recovery or fastboot (no button combination is working).
If connected via USB (while just charging too), it just keeps rebooting & shows "Your system has been destroyed".
When disconnected from external power supply, it shuts down automatically after a few seconds, but when I try to boot into the bootloader (or try to turn it on), it again goes to the system destroyed screen.
Here are the set of commands I ran just after unlocking the bootloader:
PS D:\Android\ADB> ./fastboot flash recovery ginkgo_recovery.img
Sending 'recovery' (65536 KB) OKAY [ 1.404s]
Writing 'recovery' OKAY [ 0.385s]
Finished. Total time: 1.824s
PS D:\Android\ADB> ./fastboot boot ginkgo_recovery.img
Sending 'boot.img' (65536 KB) OKAY [ 1.391s]
Booting OKAY [ 0.148s]
Finished. Total time: 1.591s
PS D:\Android\ADB> ./fastboot devices
97900a40 fastboot
PS D:\Android\ADB> ./fastboot flash recovery ginkgo_recovery.img
Sending 'recovery' (65536 KB) OKAY [ 1.414s]
Writing 'recovery' OKAY [ 0.381s]
Finished. Total time: 1.808s
PS D:\Android\ADB> ./fastboot reboot recovery
Rebooting into recovery OKAY [ 0.001s]
Finished. Total time: 0.003s
PS D:\Android\ADB> ./adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
PS D:\Android\ADB> ./fastboot devices
PS D:\Android\ADB> ./fastboot devices
What I believe is that I forgot to disable vbeta verification before flashing the new recovery (when I tried flashing a new recovery in my POCO, I got an error regarding this, but this time none of that happened). Is there any way to do it now? without having to go into EDL mode & stuff?

Rocker_2102 said:
Is there any way to do it now? without having to go into EDL mode & stuff?
Click to expand...
Click to collapse
to avoid problems on ginkgo you have to flash VBMETA then TWRP then the recovery you want
now try to flash the attached VBMETA using :
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
it will fix "System destroyed", if not you have to use EDL

loopypalm said:
to avoid problems on ginkgo you have to flash VBMETA then TWRP then the recovery you want
now try to flash the attached VBMETA using :
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
it will fix "System destroyed", if not you have to use EDL
Click to expand...
Click to collapse
Umm.. that's where the problem is for me, I am unable to boot into fastboot mode. It juts goes back to the system destroyed screen no matter what button combination I try .

Rocker_2102 said:
Umm.. that's where the problem is for me, I am unable to boot into fastboot mode. It juts goes back to the system destroyed screen no matter what button combination I try .
Click to expand...
Click to collapse
did you try the comand while "system destroyed" is displayed ?

No.. but I tried connecting using adb and it did not work. I think I event tried "fastboot devices" which too didn't show anything .
But I'll try again now to confirm this.

Hi,
Thank you @loopypalm , I was able to boot into fastboot somehow. Now the device is working fine on MIUI 12.

Rocker_2102 said:
Hi,
Thank you @loopypalm , I was able to boot into fastboot somehow. Now the device is working fine on MIUI 12.
Click to expand...
Click to collapse
I think you should try some custom roms
miui is not the optimal choice unfortunately ...

loopypalm said:
I think you should try some custom roms
miui is not the optimal choice unfortunately ...
Click to expand...
Click to collapse
It wasn't my phone so just bringing it back to working condition is pretty awesome for me . On my phone I keep trying new ROMS (just tried Projet Elixir)

bro how did you booted into fastboot i also in same situation

how did you fixed i also in same situation

Techue said:
how did you fixed i also in same situation
Click to expand...
Click to collapse
Just keep trying pressing the fastboot button combination.. It took me around 2 days

Techue said:
how did you fixed i also in same situation
Click to expand...
Click to collapse
same here, it's not booting to fastboot even tho I tried the combination when "Your system has been destroyed" was displayed ;-;

Rocker_2102 said:
Just keep trying pressing the fastboot button combination.. It took me around 2 days
Click to expand...
Click to collapse
I got it to working condition this way only, unfortunately.