OnePlus 6
current OS unknown (probably 5.1.5)
stock recovery
Hi all,
since I obviously hard-bricked my OP6 recently, the only thing that the phone does is booting directly into the bootloader.
Current status:
Code:
PS C:\Android> fastboot oem device-info
...
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(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
I'm not allowed to execute ANY commands, which are always denied by "FAILED: (remote xyz is not allowed)"
oem unlocking does not work.
Trying to boot from a boot.img via fastboot (fastboot boot yxz.img) sends the phone into a freezing boot logo screen
I'm out of ideas and beginning to get really desperate about this.
Any help?
EDIT: The MsmDownloadToolV4.0InternationalVersionOxygenOS5.1.5 fixed it, finally. After more than 5 failed attempts. (which made me lose hope).
I'm STILL curious about that remote error. What causes it and is there another way to fix it?
Related
Hi,
I have a Motorola XT925 that appears to be unrecoverable and I was wondering if anyone here has been able to solve. I have looked through this group and there seems to be similar issues but non resolved for my particular issue.
When the phone attempts to boot I get the "Encryption unsuccessful" message with a "Reset phone" button that does nothing. According to other posts I have read on this error, if I could unlock the bootloader (and wipe the device) all would be well, however, when I get the phone into fastboot mode and attempt the unlock (as detailed on the Motorola website), it states the phone does not qualify for bootloader unlocking.
I see there is an exploit that can unlock the bootloader if the phone has root installed, however this phone does not and will not boot...
Is there anything that can be done?
Do you have the unlock key?
If its an xt925 ,it should qualify for unlock.
Make sure you update your drivers, try using another port (2.0 preferably), and that you copy the string correctly.
Tapatalk with RAZR HD
neo.ank said:
Do you have the unlock key?
If its an xt925 ,it should qualify for unlock.
Make sure you update your drivers, try using another port (2.0 preferably), and that you copy the string correctly.
Tapatalk with RAZR HD
Click to expand...
Click to collapse
Thanks for replying, you are indeed correct. I must have cut and paste the unlock key incorrectly. However, I still do not think thing the phone is functioning correctly as I am not able to do anything with the fastboot command. I can not erase/format partitions (userdata or cache), I can not flash either the recovery (to CWM) or boot partitions and can't even boot the phone directly to the recovery image.
Here are some outputs from the fastboot:
C:\Users\EIT-Z820\Downloads>fastboot getvar all
(bootloader) version-bootloader: 109B(*)
(bootloader) product: vanquish_u
(bootloader) secure: yes
(bootloader) mid: 0056
(bootloader) version: 0.5
(bootloader) serialno: TA24000RHS
(bootloader) qe: qe 0/0
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 31457280
(bootloader) emmc-size: 16GB
(bootloader) reason: Reboot to bootloader
(bootloader) revision-hardware: 0x8300
(bootloader) cpu: MSM8960 CS
(bootloader) uid: 1789E20102000100000000000000
(bootloader) cid: 0x0e
all:
C:\Users\EIT-Z820\Downloads>fastboot erase cache
(bootloader) Variable not supported!
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.049s
C:\Users\EIT-Z820\Downloads>fastboot flash recovery recovery.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (7892 KB)...
OKAY [ 0.612s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
Not sure what the Variable not supported message is, however even when I unlocked the device, there was a message saying that it was unable to erase partition.
Any ideas?
Drivers, could be the reason. Try re-installing.
Also, use 'mfastboot' and see if the issue persist.
Tapatalk with RAZR HD
Hello,
i have successfully unlocked bootloader with the official way. I can flash everything twrp, cm rom, supersu...no problems.. but as i saw in 2 apps of playstore for device's info. These two said that bootloader is unknown... So i tried via cmd in order to see whats really happening and i took these results with this command "fastboot oem device-info" :
C:\adb>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.007s]
finished. total time: 0.007s
Anyone knows why this confusion happends?
UPDATE: By pressing volume up + power button i can't boot on bootloader anymore, either from advanced reboot of cm. It's a think that does not matter to me, but i would like to know the reason.
Hi there!
It's been a couple of hours I pass trying to install a new Rom on my Oneplus X.
First thing I do was to return it Stock and install OOS at last update to have the last firmware.
I've unlock the bootloader, do the OEM unlock thing, I flash the recovery to TWRP 3.2.1.0 (it was a pain in the ass to do.... don't know exactly why)
As I had difficulties installing the TWRP, I install the OPXBLUpdateOOS3.1.zip which help me installing the recovery
I ran this command to be sure it is unlock
PS C:\adb> fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.010s]
finished. total time: 0.011s
And than, I try to install roms with TWRP... I select my Rom (I want to install Oreo from AOSPA, but I also try Lineage 14 and Cyanogen 13 which was the one I had before)
I always got this error :
Checking for Digest files
Skipping Digest check: no digest file found
And than, the recovery reboot...
What have I done wrong? What can I do now to install at least android N ?
What twrp are you using? Flash the latest official or the one by CheckYourScreen. It's under original android development forum. It looks more like an issue with twrp than from the zip files.
i am having the same problem with latest twrp
Try using the 3.2.3-0 TWRP recovery bcoz everything you mentioned which you did seems to be correct. So try the TWRP 3.2.3-0 and report back.
I have the same issue with the latest twrp: 3.2.3-0 on samsung galaxy a5 2016. Can't install an official ROM from sammobile.
I have the same message on Note 4 but it doesn't affect installation. I just ignore it.
I have the same fcking issue with missing digest fcking ****. I can't flash the Magisk more SuperSU. **** off!
I had problem in flashing ROM file in Samsung galaxy grand 2 .the error says "No digest file found "and "zip is corrupt" .pls help me to resolve the issue
I am facing the same problem. No digest file found!
C:\Users\Nabil\Downloads\adb>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.006s]
Finished. Total time: 0.007s
omkolte17 said:
Try using the 3.2.3-0 TWRP recovery bcoz everything you mentioned which you did seems to be correct. So try the TWRP 3.2.3-0 and report back.
Click to expand...
Click to collapse
I just had this with my S5 Plus on 323 , I downgraded twrp and voila ..fixed roms that ended with (no rom installed are you sure you want to reboot?) are working perfectly !!!
My One Plus X is stuck in Oneplus logo I haven't rooted my phone, now i can only enter in fastboot mode. unable to enter in recovery mode and system.
when i try to fastboot oem unlock failed it says unable to unlock, device is locked.
how to unlock oem device through fastboot mode. or any way to solve this issue ?
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.008s]
finished. total time: 0.009s
Edit : Sorry, I forgot to answer the question : No...
**********************
Was TWRP installed before ?
Explain what you did just before that !
But seeing what you have, I bet flashing the official recovery won't work.
Flashing stock recovery
1) Download stock Recovery OnePlus (there are one for MM version and one for previous version. Depends on question one I asked !)
2) Copy the recovery in the adb folder
3) Start a new prompt command from the folder adb
4) Put the smartphone in fastboot mode (power off the smartphone , and click volume up + power)
5) Put the command "fastboot device" for be sure computer can see the smartphone
6) Put the command fastboot "flash recovery name-recovery.img"
But you bet shot will be to run the Mega unbrick guide I guess...
aiwin007 said:
My One Plus X is stuck in Oneplus logo I haven't rooted my phone, now i can only enter in fastboot mode. unable to enter in recovery mode and system.
when i try to fastboot oem unlock failed it says unable to unlock, device is locked.
how to unlock oem device through fastboot mode. or any way to solve this issue ?
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.008s]
finished. total time: 0.009s
Click to expand...
Click to collapse
It's softbricked. Happened to me awhile ago, i've resolved it with the unbrick tools.
*Your bootloader is locked and can't do oem unlock, can't boot to twrp/system→ So there's no way to flash anything.
You need to run the unbrick tools. Head to the mega unbrick guide for more details.
Mega Unbrick's Thread
Notes:
Link for the recovery tool in OP is dead, so use this one instead
Recovery Tool
And download "Qualcomm driver" from OP.
hi
I hope you have a great day.
I have a problem with my HTC d728w phone, after months I turned on the phone and the phone just boot into fastboot mode.
I select the "boot to bootloader" or "reboot" option but the phone comes back to fastboot mode.
I tried many ways, like: download the Flashman program to flash the ROM of the device and get the Fail message.
I tried the RUU and ADB and I get Unknows command for every command. just I can see the limited information of the device with "fastboot Getvar all".
so what I should do ? just I saw whole google links and I m so confused with this problem.
"Sorry for bad English"
(bootloader) battery-status: good
(bootloader) max-download-size: 0x8000000
(bootloader) warranty: yes
(bootloader) unlocked: no
(bootloader) secure: yes
(bootloader) version: 0.5
all: Done!!
finished. total time: 0.005s