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.
Related
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
Hi friends , I am stuck at boot loop.
I have flashed the eUI 5.8.19S ROM properly and it was working fine. After that , I might have done mistake with TWRP .
Now , I am in bootloop .
My phone is recognized in fastboot mode.
I am able to flash recovery image also ,
But , after that when I am trying to reboot fastboot is giving me error message in phone :
Fastboot oem devices in unlock
Lock failed... return to fastboot in 3s
After getting the above error for couple of times , I have flashed the boot image by
fastboot flash boot boot.img
Also, on trying to boot into recovery , fastboot is showing this error message :
C:\Users\Shounak\AppData\Local\Android\sdk1\platform-tools>fastboot boot twrp-3.1.1-0-x3.img
downloading 'boot.img'...
OKAY [ 0.819s]
booting...
(bootloader) Fastboot oem devices is unlock
(bootloader) Fastboot oem devices is unlock
(bootloader) Start lock flow
FAILED (remote:
Lock failed - Err:0xfffffffe
)
finished. total time: 4.801s
I am unable to understand why is fastboot going into lock flow.
Can you please help me ? I am really stuck here.
coolcoder001 said:
Hi friends , I am stuck at boot loop.
I have flashed the eUI 5.8.19S ROM properly and it was working fine. After that , I might have done mistake with TWRP .
Now , I am in bootloop .
My phone is recognized in fastboot mode.
I am able to flash recovery image also ,
But , after that when I am trying to reboot fastboot is giving me error message in phone :
Fastboot oem devices in unlock
Lock failed... return to fastboot in 3s
After getting the above error for couple of times , I have flashed the boot image by
fastboot flash boot boot.img
Also, on trying to boot into recovery , fastboot is showing this error message :
C:\Users\Shounak\AppData\Local\Android\sdk1\platform-tools>fastboot boot twrp-3.1.1-0-x3.img
downloading 'boot.img'...
OKAY [ 0.819s]
booting...
(bootloader) Fastboot oem devices is unlock
(bootloader) Fastboot oem devices is unlock
(bootloader) Start lock flow
FAILED (remote:
Lock failed - Err:0xfffffffe
)
finished. total time: 4.801s
I am unable to understand why is fastboot going into lock flow.
Can you please help me ? I am really stuck here.
Click to expand...
Click to collapse
R u able to use twrp???
Error: fastboot oem unlock on SHIELD TV 2017 (16GB) with Nvidia OS 7.2.1 (Dev & Rec)
I have a SHIELD TV 2017 (16GB, remote only) device that currently has Nvidia's Developer OS 7.2.1 installed. The same error occurs with the Factory (OS installed on device originally) and Recovery OS installation.
After gaining access to the device through ADB, when I enter the command fastoob oem unlock I receive the following error. It's unclear why this error occurs since there isn't any other information made available.
fastboot oem unlock
(bootloader) erasing userdata...
(bootloader) erasing userdata done
FAILED ()
Finished. Total time: 113.891s
Has anyone else experienced this as well? Is it something to be concerned about? Does anyone know why this failure is occurring?
Edit: The ADB software package I found and installed is "15 seconds ADB Installer 2.0" which I installed on Windows 10 Pro. I don't know if this may have something to do with it.
nadia p. said:
I have a SHIELD TV 2017 (16GB, remote only) device that currently has Nvidia's Developer OS 7.2.1 installed. The same error occurs with the Factory (OS installed on device originally) and Recovery OS installation.
After gaining access to the device through ADB, when I enter the command fastoob oem unlock I receive the following error. It's unclear why this error occurs since there isn't any other information made available.
fastboot oem unlock
(bootloader) erasing userdata...
(bootloader) erasing userdata done
FAILED ()
Finished. Total time: 113.891s
Has anyone else experienced this as well? Is it something to be concerned about? Does anyone know why this failure is occurring?
Edit: The ADB software package I found and installed is "15 seconds ADB Installer 2.0" which I installed on Windows 10 Pro. I don't know if this may have something to do with it.
Click to expand...
Click to collapse
I am in the process of trying to root my 2017 Nvidia shield myself and having difficulty flashing the modified boot image while in fastboot (after unlocking) so if you can shed some light on that issue I'd appreciate it.
For yours my suggestion is to ADB reboot bootloader and plug a keyboard in then navigate to unlock bootloader from the menu.
This is how I did mine.
[SOLVED] Use Minimal ADB & Fastboot 1.4.1 tools or later.
I have resolve this issue, another member here was kind enough to point me to another ADB software named Minimal ADB & Fastboot 1.4.1.
Using Minimal ADB & Fastboot 1.4.1 instead of 15 seconds ADB Installer 2.0 resolved the failure issue.
fastboot oem unlock
...
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) Unlocking bootloader...
(bootloader) Bootloader is unlocked now.
OKAY [ 48.891s]
finished. total time: 48.891s
fastboot oem lock
...
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) Locking bootloader...
(bootloader) Bootloader is locked now.
OKAY [ 53.344s]
finished. total time: 53.344s
Having the proper tool(s) for the job is always key.
sconnyuk said:
I am in the process of trying to root my 2017 Nvidia shield myself and having difficulty flashing the modified boot image while in fastboot (after unlocking) so if you can shed some light on that issue I'd appreciate it.
For yours my suggestion is to ADB reboot bootloader and plug a keyboard in then navigate to unlock bootloader from the menu.
This is how I did mine.
Click to expand...
Click to collapse
Hello sconnyuk, I attempted to use the OS menu option "Unlock Bootloader" that appears on the screen of the Shield TV after executing adb reboot bootloader from the Command Prompt (Administrator) window. It's unclear to me that this method works. From what I have attempted and experienced so far is it does not (lock or unlock) the bootloader.
I believe it doesn't execute the same "oem" command which is why, although this is only my speculation.
I feel the the reason so many senior members here advise us to use the ADB & Fastboot tools is because it works.
nadia p. said:
Hello sconnyuk, I attempted to use the OS menu option "Unlock Bootloader" that appears on the screen of the Shield TV after executing adb reboot bootloader from the Command Prompt (Administrator) window. It's unclear to me that this method works. From what I have attempted and experienced so far is it does not (lock or unlock) the bootloader.
I believe it doesn't execute the same "oem" command which is why, although this is only my speculation.
I feel the the reason so many senior members here advise us to use the ADB & Fastboot tools is because it works.
Click to expand...
Click to collapse
Yes I can confirm now the menu lock and unlock do work, I've just finished flashing my modified boot.img after unlocking the bootloader this way.
?
I have Chinese 6gb 128gb Mi Max 3 with latest China stable ROM. Finally i decided to get root but i can't flash TWRP over fastboot as in all instructions. My bootloader is unlocked. I get following warning
J:\Xiaomi Mi Max 3 - root>fastboot flash recovery twrpteamwin.img
target reported max download size of 536870912 bytes
sending 'recovery' (61164 KB)...
OKAY [ 1.333s]
writing 'recovery'...
(bootloader) Security Warning: rollback version downgrading,
(bootloader) which may make your device enter to EDL state!!!
(bootloader) Warning: If you want force flashing, try do
(bootloader) 'fastboot oem ignore_anti' before!
FAILED (remote: Please check your package anti version!!!)
finished. total time: 1.353s
I tried 3 versions of TWRP. I also installed latest global stable ROM. Same error. What should i do? Please help...
Same for me. Tried
Code:
C:\platform-tools>fastboot flash recovery twrp-3.3.0-0-nitrogen.img
Sending 'recovery' (61164 KB) OKAY [ 1.325s]
Writing 'recovery' (bootloader) Security Warning: rollback version downgrading,
(bootloader) which may make your device enter to EDL state!!!
(bootloader) Warning: If you want force flashing, try do
(bootloader) 'fastboot oem ignore_anti' before!
FAILED (remote: 'Please check your package anti version!!!')
fastboot: error: Command failed
Is it safe to do the oem ignore_anti thing and force it or would it brik my device?
Device should be official global 64gb 4 gb RAM bootloader unlocked official with 720h waiting periode. Currently MIUI Global 10.2.1.0 installed.
That's what I'm trying to figure out, if it's safe to override it. I don't want to brick my phone. Right now i had installed China beta ROM which has a root built in. But Android Auto refuses to work with this ROM. So i have to either go back to China stable without root, or flash TWRP somehow
So i tried it with
Code:
fastboot oem ignore_anti
At least twrp has started. If do not flash any old miui it should work. I think i go with the EU developer one. or may be RR GSI.
bigScreenUser said:
So i tried it with
Code:
fastboot oem ignore_anti
At least twrp has started. If do not flash any old miui it should work. I think i go with the EU developer one. or may be RR GSI.
Click to expand...
Click to collapse
PLease let me know if you were able to flash ROM after that! I'm waiting for your reply and biting my nails
Try
fastboot boot twrp.img
And then flash twrp.img through booted recovery.
bigScreenUser said:
So i tried it with
Code:
fastboot oem ignore_anti
At least twrp has started. If do not flash any old miui it should work. I think i go with the EU developer one. or may be RR GSI.
Click to expand...
Click to collapse
So, did it work? Were you able to flash ROM after overriging ARB warning during TWRP install?
If anyone is interested in overcoming this error: I have done the following, here are my steps:
My phone: China Stable ROM, 6Gb/128Gb Mi Max 3
- Make sure oyu have unlocked bootloader
- I flashed Global Stable ROM first, with the chinese software tool: essentially just automated flashing via fastboot, but any method works. Custom ROMs would be flashed after TWRP.
- Copy TWRP image on a flash drive, make sure it's accessible from the phone
- Phone in fastboot mode, conenct to PC "fastboot boot twrp-tw3300.img" (renamed latest teamwin TWRP image for Mi Max 3)
- Phone boots in TWRP
- Select flash - image - and flash TWRP from inside TWRP (no wiping, nothing else, flash image to recovery partition)
- If root is desired, flash Magisk.
- Reboot to recovery, to see that it sticks
- Reboot to system
- Install Magisk apk, check root.
Sorry for late reply, was bussy getting RR GSI up and running. But sadly it was stuck in bootloop. So i flashed a room from mi-glob roombuilder. This worked so far succesfully, but the chines dialoges do not go well with me.
From my understanding, the warning from the Booloader ist just a warning. In this case may be triggered by ARB, wich means that fastboot or the BL can not guarantee that the room or recovery will work on that phone or may even brick it or is at least not from the vendor.
After you type in :
Code:
fastboot oem ignore_anti
basically this compatibillity check is disabled. After that you can flash any room or recovery you like. If you do flash an older firmware on an ARB activated device you will produce a nice paperwight. But that is another topic.
I do not know, which part (bootloader or fastboot) is responsible for the warning, as i am a total noob regarding flashing android devices.
Hello kind saviour,
I accidentally deleted my build.prop file and now my phone is stuck on "the boot loader is unlocked and software integrity cannot be guaranteed..." screen at boot.
I use the AOSIP rom for OnePlus 7t,if that helps.
I do NOT want to lose any data and preferably not lose any system settings either.
Updating the ROM is OK for me. Please let me know if that is a good idea however.
The good part:
fastboot boot TWRP.img works, sdcard data de-cryption works, i can access files with MTP. Already made a backup of most important data.
I do not know which AOSIP version I have, but it's not the latest.
Doesn't work: fastboot boot magisk-patched.img (image might be too old?)
Doesn't work: fastboot reboot fastboot + fastboot boot boot.img -> Error:
*FAILED (remote: 'Download is not allowed on locked devices')
Booting from A instead of B goes into infinite booting animation.
adb commands during twrp don't work
No adb access anywhere else
I have no backup of build.prop
I have a builT.prop file and i suspect i saved it with wrong name (but I still can't access /system partition)
I had access to /system partition during first twrp boot, but accidentally mounted it as read only the first time.
After following reboots to twrp, system is always unmountable (both from slot a as well as slot b).
Even after deleting twrp folder from pc, the system partition remains unmountable:
*Failed to mount '/system_root' (Permission denied)
*Failed to mount '/vendor' (Permission denied)
bootloader is unlocked & phone is rooted with magisk.
If you could help me with a solution where i can keep my data you would make me soo happy. Having a rough time with life lately and you could be my second coming of Jesus
Thanks in advance.
Dirty flash latest aosip with TWRP or with fastboot
HueyT said:
Dirty flash latest aosip with TWRP or with fastboot
Click to expand...
Click to collapse
Thank you! I will try that later today and report back.
I tried dirty flashing the latest AOSIP update, and it made everything worse. (Maybe I was on the wrong slot??)
Now there is no fastbootD, no recovery, and neither possible to fastboot boot twrp.img!
Only thing that worked was the bootloader (fastboot).
I didn't even get the usual "the boot loader is unlocked and software integrity cannot be guaranteed..." screen.
However, i changed slot with fastboot and now I have recovery and fastbootD and can boot twrp again.
Now I'm really worried about messing up my next steps, so would be super grateful for any help you can give me. I believe we are near a solution here.
Big Questions:
Should I dirty update the rom from fastbootD or from TWRP?
Which *SLOT* do I update from?
History of how everything went wrong:
Spoiler: command line messages and responses
fastboot update OSiP-10-Gapps-hotdogb-20210621-img.zip
Code:
--------------------------------------------
Bootloader Version...: unknown
Baseband Version.....:
Serial Number........: 9de0f5c0
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
android-info.txt syntax error:
Setting current slot to 'b'
FAILED (remote: 'set_active command is not allowed on locked devices')
fastboot: error: Command failed
fastboot oem device-info
Code:
FAILED (remote: 'Unable to open fastboot HAL')
fastboot: error: Command failed
//I manually rebooted to bootloader (fastboot) here//
fastboot oem device-info
Code:
(bootloader) Verity mode: true
(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
(bootloader) op_abl_version: 0x31
(bootloader) cal_rebootcount: 0x31
OKAY [ 0.050s]
Finished. Total time: 0.053s
fastboot reboot fastboot
Code:
Rebooting into fastboot
OKAY [ 0.004s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Update: i found a solution by updating adb/fastboot .exe files,
flashing twrp-3-5-1_10-hotdog-sdcardfs.img
and dirty flashing the latest aosip image in twrp's fastboot mode
I got a "QUALCOMM CrashDump Mode" message once but it boots to aosip now. We will see if the crashdump messages appear again or not.