Hi all,
I installed CM14 on my OP3 but now after 5days somthing has happen.
The phone doesn't start I can see the logo and after that I see some check that it does.
cache : failed
boot: failed
boot-aging: failed
system: failed
Tried to do "technobuzz net / unbrick-oneplus-3"
But it doesn't work.
In fastboot under
Fastboot mode
PRODUCT_NAME - msm8996
VARIANT - MTP UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - ********
SECURE BOOT - enabled
Device state - locked
So I can't flash any thing and the recovery menu is not there.
I can only start the phone in Fastboot menu but no more.
Can anyone help my?
Can I boot some bootimage and login to CM14?
thefuse said:
Hi all,
I installed CM14 on my OP3 but now after 5days somthing has happen.
The phone doesn't start I can see the logo and after that I see some check that it does.
cache : failed
boot: failed
boot-aging: failed
system: failed
Tried to do "technobuzz net / unbrick-oneplus-3"
But it doesn't work.
In fastboot under
Fastboot mode
PRODUCT_NAME - msm8996
VARIANT - MTP UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - ********
SECURE BOOT - enabled
Device state - locked
So I can't flash any thing and the recovery menu is not there.
I can only start the phone in Fastboot menu but no more.
Can anyone help my?
Click to expand...
Click to collapse
same here
Is there any way to get the device state -locked to unlocked without having the OS?
C:\adb>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) Have console: false
(bootloader) Selinux type: <none>
(bootloader) Boot_mode: normal
(bootloader) Kmemleak_detect: false
OKAY [ 0.094s]
finished. total time: 0.095s
C:\adb>
I got it back from the repair yesterday, and they replaced my motherboard because of faulty motherboard.
install mod-twrp via fastboot
http://forum.xda-developers.com/devdb/project/dl/?id=21835 and install OxygenOS 3.2.6/3.2.8
You simply plug it into a pc and type fastboot oem unlock to unlock the device, then flash TWRP and reflash the OS
cache : failed
modem : failed
boot: failed
boot-aging: failed
system: failed
md5checksum: failed
I have same problem, i was on OOS b9
I flashed TWRP but can not restart to recovery, and also I flashed stock recovery but same problem ,
Any suggestion
Regards
almuhajir said:
cache : failed
modem : failed
boot: failed
boot-aging: failed
system: failed
md5checksum: failed
I have same problem, i was on OOS b9
I flashed TWRP but can not restart to recovery, and also I flashed stock recovery but same problem ,
Any suggestion
Regards
Click to expand...
Click to collapse
Unbrick guide, you will have to flaah these files manually.
Puddi_Puddin said:
Unbrick guide, you will have to flaah these files manually.
Click to expand...
Click to collapse
I got this problem after using (guide mega unbrick guide hard bricked)
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Yes. Boot into fastboot and see of windows device manager shows Kedacom. If it does boot into https://www.google.nl/amp/www.howto...signed-drivers/amp/?client=ms-android-oneplus then install http://www.technobuzz.net/download-oneplus-3-usb-drivers/ now go to device manager it still shows kedacom. (Im not fully sure) but there should be a option if you right click it to change it to Oneplus drivers. Try to play yourself with thid method. I had it aswell and fixed it. I cant give you a fully guide since im not homeless yet..
Puddi_Puddin said:
Yes. Boot into fastboot and see of windows device manager shows Kedacom. If it does boot into https://www.google.nl/amp/www.howto...signed-drivers/amp/?client=ms-android-oneplus then install http://www.technobuzz.net/download-oneplus-3-usb-drivers/ now go to device manager it still shows kedacom. (Im not fully sure) but there should be a option if you right click it to change it to Oneplus drivers. Try to play yourself with thid method. I had it aswell and fixed it. I cant give you a fully guide since im not homeless yet..
Click to expand...
Click to collapse
Dear,
its not show Kedacom with me
What does it show then? Otherwise try to manually flash these files.
Puddi_Puddin said:
What does it show then? Otherwise try to manually flash these files.
Click to expand...
Click to collapse
I'll try to flashed manually, i'll give you feedback
almuhajir said:
I'll try to flashed manually, i'll give you feedback
Click to expand...
Click to collapse
Otherwise well go back to the basics
1. Boot into fastboot type "Fastboot devices" does it show up? No? > Device Manager try to see if it shows something with Kedacomm.
2. Fastboot devices shows up? > Go to the unbrick program it has a file with all partitions. Flash the missing ones that you get on your screen manually, i assume that you know how fastboot works.
3. System boots yay! But no wifi Reflash OOS but dont boot! Go to Fastboot and type this
"fastboot erase modemst1"
"fastboot erase modemst2"
If you still didn't manage to fix it try to explain as clearly ss you can with what you are doing and what you have tried.
Puddi_Puddin said:
Otherwise well go back to the basics
1. Boot into fastboot type "Fastboot devices" does it show up? No? > Device Manager try to see if it shows something with Kedacomm.
2. Fastboot devices shows up? > Go to the unbrick program it has a file with all partitions. Flash the missing ones that you get on your screen manually, i assume that you know how fastboot works.
3. System boots yay! But no wifi Reflash OOS but dont boot! Go to Fastboot and type this
"fastboot erase modemst1"
"fastboot erase modemst2"
If you still didn't manage to fix it try to explain as clearly ss you can with what you are doing and what you have tried.
Click to expand...
Click to collapse
Thanx dear,
the problem now still in
cache : failed (dont have it)
modem : ok flash it via fastboot
boot: failed try but not show ok
boot-aging: failed (dont have it)
system: failed (dont have it)
md5checksum: failed (dont have it)
almuhajir said:
Thanx dear,
the problem now still in
cache : failed (dont have it)
modem : ok flash it via fastboot
boot: failed try but not show ok
boot-aging: failed (dont have it)
system: failed (dont have it)
md5checksum: failed (dont have it)
Click to expand...
Click to collapse
Either Method 1 or Method 2 has these files. Try to navigate the folders. Then manually flash them. If you really cant find them ill send you them later this day or tomorrow since im not home. To be exact your device does showup under fastboot devices.
Puddi_Puddin said:
Either Method 1 or Method 2 has these files. Try to navigate the folders. Then manually flash them. If you really cant find them ill send you them later this day or tomorrow since im not home. To be exact your device does showup under fastboot devices.
Click to expand...
Click to collapse
Many thanx dear,
now i download Method 2, i hope to get repair,
Thanx
almuhajir said:
Many thanx dear,
now i download Method 2, i hope to get repair,
Thanx
Click to expand...
Click to collapse
It will, it is software based.. If your device shows up under Fastboot then there is no problem If you have no wifi on boot make sure to post what i said before, keep in mind your device will be at 3.2.1 OOS.
Left with a bricked Wileyfox Swift that was originally running CM13. Tried to update to the nightly build from 20161118 and now have a bricked device which I can only access in fastboot (no recovery, no adb, no boot)
According to fastboot oem device-info I get this:
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
I attempted to flash files one by one via fastboot using this guide:
http://forum.xda-developers.com/wileyfox-swift/help/stupid-bricked-phone-access-fastboot-t3414437/post67663025#post67663025
Got stuck on the last 4 files which are not in the cyanogen installer zip.
Can anyone tell me where I would find the last 4 files in that guide?
Cheers
LG-dudey said:
Left with a bricked Wileyfox Swift that was originally running CM13. Tried to update to the nightly build from 20161118 and now have a bricked device which I can only access in fastboot (no recovery, no adb, no boot)
According to fastboot oem device-info I get this:
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
I attempted to flash files one by one via fastboot using this guide:
http://forum.xda-developers.com/wileyfox-swift/help/stupid-bricked-phone-access-fastboot-t3414437/post67663025#post67663025
Got stuck on the last 4 files which are not in the cyanogen installer zip.
Can anyone tell me where I would find the last 4 files in that guide?
Cheers
Click to expand...
Click to collapse
There are two Zips on the site one is for install by recovery the other by fastboot the two zips are not the same you need the fastboot one
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.
Hello,
I have a Nokia 6.1 that bricked itself over a system update last year.
Symptoms
Turns on and goes into "Download Mode" screen. Does not turn off. Keeps rebooting.
Had to run
Code:
fastboot oem HALT
to put it to sleep.
Phone details
Android 8.1
Bootloader Locked
Output of
Code:
fastboot oem device-info
`
Code:
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.016s]
finished. total time: 0.016s
Goal
Somehow recover critical data stored on the phone. Data wiping is not an option.
What I've tried
1. Key combos
Multiple key combinations fails to take it to a recovery screen.
2. ADB & Fastboot
On windows 10 I've installed the minimal ADB&Fastboot drivers.
Code:
adb devices
shows nothing.
Code:
fastboot devices
shows the device.
The following set of commands takes it to a recovery (?) mode
Code:
fastboot devices
fastboot reboot
fastboot getvar current-slot
fastboot --set-active=b
fastboot --set-active=a
fastboot reboot
This screen only shows 2 options "Try again" and "Factory Reset"
Also says "Can't load android system. Data my be corrupt." (sth similar)
I've tried installing TWRP with
Code:
fastboot boot twrp.img
but since the bootloader is locked I'm unable to do so.
I have not tried unlocking the bootloader as it supposedly wipes the data, even though it supposedly doesn't have to.
After some time I'd discovered something called an EDL mode and tried to jerry rig a USB-C cable with shorted green and black wires to get the phone to boot into that mode. I'm not sure what the proper sequence of actions here should be as the phone turns on and goes into "Download Modes" the second I plug the USB cable in and nothing shows up on Device Manager.
Would it be possible in any way to recover the data or at least take a dump of the userdata partition in the storage. Thanks a lot in advance.
Hi.
So I managed to put /e/ OS (by doing the HOWTO on docDOTeDOTfoundation/devices/FP3/install ) and TWRP 3.4 (by doing the HOWTO on twrpDOTme/fairphone/fairphone3.htm ) plus doing a 'fastboot oem lock' and a 'fastboot oem unlock') on my FP3.
As long as I keep bootloader unlocked it starts /e/ OS on power-on or TWRP when I power on with holding PWR and volume-up.
However, when I lock the phone all I get is a:
<!>
Your device is corrupt. It can't be trusted and will not boot.
Visit this link on another device:
g.co/ABH
As far as I understood some checksum is calculated and if it does not match … well - whoever took the decision to make it work that way didn't care about users of custom ROMs - probably knowing that this will make it hard for such users… This reminds me on others OS which restrict what a user can do with his phone / PC …
Anyhow, I didn't find how to override that check. Maybe the checksum can be "corrected" or maybe I just have to set a variable and I'm good.
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: trueSo i'ts probably not the device tampered status…
Just in case: "Fix Recovery Bootloop" from the TWRP howto from above failed and fails again and again (even after reboot into the bootloader) with
cd /tmp/repackorig/ && /sbin/magiskboot hexpatch kernel <a_long_hex_number> <another_long_hex_number> process ended with
Error: 1
Error patching kernel.
What can I do?
Thanks in advance!
I think that you cannot lock the bootloader since you install TWRP. If you do that, FP3 won't boot.
It's a matter of security.
bootloader must be unlocked
Locking an AVB device is possible but requires the system image be properly signed, no other modifications to system made, and flashing the AVB key to the avb_custom_key partition.