Develop Bugs

My OnePlus 3 is a brick

Dear XDA Community,
in past 2 months i've been using CM13, constantly having some trouble with apps involving the camera, such as the camera app(surprise) and e.g. snapchat.
So yesterday I decided to update my CM Build, not knowing it would be to CM14 and with this Android 7.
So resulting from this I experienced a lot of issues with different apps, especially the google ones and for example Instagram. I DID NOT Upgrade my twrp, which was pretty stupid as I found out.
So this morning I checked again for CM Updates and Updated to Version Nightly...25 I think... but because I did not update my TWRP it did absolutely nothing except bricking my phone.
I already followed through the Guide for Hard Bricked OP3s (both steps) "http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700"
Though it sadly did not work for me. The Recovery tool and all works but when I want to boot my Phone the md5checksum pops up after the OP3 Logo and it tells me that everythings fine except "boot: failed".
I tried the procedure of the Hard Brick fix over and over again but nothing seems to work. I am fairly new to this whole Custom Rom stuff so I have absolutely no clue what do to.
Does anyone have any idea that could help?
Best Regards
Aliasalex

Try fastboot flashing the whole rom.

how? i dont have a factory img.
i tried flashing CM14 again and OxygenOs OTA. Currently i am getting Cache, Boot and System Failed.
In the meanwhile I managed to get twrp installed, but trying to install OS or CM via twrp didnt work either
//edit: ran the msm download tool again. Now only Boot is failing. tried flashing a boot.img via fastboot but didnt work
//edit2: when flashing the boot.img via fastboot my phone boots and works. When restarting without PC it still has cache and boot failure in md5checksum

try the 1st method you mentioned in the OP but flash https://www.androidfilehost.com/?fid=24591020540821926 . from what I understand, you need to full write all your partitions since they seems corrupted.

aliasalex said:
how? i dont have a factory img.
i tried flashing CM14 again and OxygenOs OTA. Currently i am getting Cache, Boot and System Failed.
In the meanwhile I managed to get twrp installed, but trying to install OS or CM via twrp didnt work either
//edit: ran the msm download tool again. Now only Boot is failing. tried flashing a boot.img via fastboot but didnt work
//edit2: when flashing the boot.img via fastboot my phone boots and works. When restarting without PC it still has cache and boot failure in md5checksum
Click to expand...
Click to collapse
I'll help you when I'm home
Connect your phone to Fastboot. Go to device manager on Windows. Do you see something with OnePlus or kedacomm. I had this issue as well managed to solve it after 2 days.

Demian3112 said:
I'll help you when I'm home
Connect your phone to Fastboot. Go to device manager on Windows. Do you see something with OnePlus or kedacomm. I had this issue as well managed to solve it after 2 days.
Click to expand...
Click to collapse
Yes a Kedacom USB Device "Android ADB Interface" is listed.

aliasalex said:
Yes a Kedacom USB Device "Android ADB Interface" is listed.
Click to expand...
Click to collapse
I'm not home atm. But can you change it by any chance to Oneplus? Your almost there! Maybe the video can explain something, I don't have a pc close.
https://youtu.be/maLWScgXflk

Demian3112 said:
I'm not home atm. But can you change it by any chance to Oneplus? Your almost there! Maybe the video can explain something, I don't have a pc close.
https://youtu.be/maLWScgXflk
Click to expand...
Click to collapse
I installed the adb setup, still shows my OP3 as Kedacom -> android adb device..
my phone has been working for the past few days flawlessly, but it still doesnt boot on its own

aliasalex said:
I installed the adb setup, still shows my OP3 as Kedacom -> android adb device..
my phone has been working for the past few days flawlessly, but it still doesnt boot on its own
Click to expand...
Click to collapse
You can't access Fastboot because of that Kedacom driver, if you right click it you should be able to change the driver.
https://support.hidemyass.com/hc/en...ow-to-disable-Driver-Signing-check-on-Windows try to boot into this. Also try to install Oneplus drivers. It's in the unbrick post.

Demian3112 said:
You can't access Fastboot because of that Kedacom driver, if you right click it you should be able to change the driver.
https://support.hidemyass.com/hc/en...ow-to-disable-Driver-Signing-check-on-Windows try to boot into this. Also try to install Oneplus drivers. It's in the unbrick post.
Click to expand...
Click to collapse
But I can access fastboot!?
Also I disabled Driver Signing Check when first trying to unbrick my phone.
I installed the drivers given in the Unbrick Test, it showed something like Qualcomm [something] 9003. There was something in between.

aliasalex said:
But I can access fastboot!?
Also I disabled Driver Signing Check when first trying to unbrick my phone.
I installed the drivers given in the Unbrick Test, it showed something like Qualcomm [something] 9003. There was something in between.
Click to expand...
Click to collapse
Nice, whdn you boot you still get those errors in red letter something with "failed boot". Then manually flash the boot. Img provided in the folder where you ran the Unbrick tool from. Command for Fastboot "fastboot devices", then "fastboot flash boot boot.img". Make sure that Kedacom is not in device manager when you are accessing Fastboot.

Android fails into TWRP, TWRP Won't Load Anymore, and Phone Not Recognized in Win10

Hello, I tried to install the rom Google PixelROM v7.3 for LG Nexus 5X[7.1.2] by argraurand, and now my phone will no longer boot into TWRP or the OS. I am running TWR 3.0.2-0, I didn't see anything about having to have that updated to the most recent for using this rom. I was able to install the rom fine from this TWRP, but now my phone seems to be bricked like. Sitting with the phone in the bootloader, I can't get windows/fastboot/adb to recognize my device connected to my computer, the google drivers are definitely installed as earlier it was being recognized fine by windows/fastboot/adb. My bootloader changed with this ROM being installed, but now the TWRP won't load either, and neither will the Android OS (it looks like it's about to load then just defaults into the TWRP loading screen, which just sits forever). I can get also into the download mode "firmware update" tool of the phone by pressing the volume up when booting, but even in this mode the phone isn't being recognized in windows anymore. Do I have any chance of restoring my phone, or should I start shopping? I've fixed other phones many times, but without being able to load/restore via fastboot I feel totally lost.

myselfalex said:
Hello, I tried to install the rom Google PixelROM v7.3 for LG Nexus 5X[7.1.2] by argraurand, and now my phone will no longer boot into TWRP or the OS. I am running TWR 3.0.2-0, I didn't see anything about having to have that updated to the most recent for using this rom. I was able to install the rom fine from this TWRP, but now my phone seems to be bricked like. Sitting with the phone in the bootloader, I can't get windows/fastboot/adb to recognize my device connected to my computer, the google drivers are definitely installed as earlier it was being recognized fine by windows/fastboot/adb. My bootloader changed with this ROM being installed, but now the TWRP won't load either, and neither will the Android OS (it looks like it's about to load then just defaults into the TWRP loading screen, which just sits forever). I can get also into the download mode "firmware update" tool of the phone by pressing the volume up when booting, but even in this mode the phone isn't being recognized in windows anymore. Do I have any chance of restoring my phone, or should I start shopping? I've fixed other phones many times, but without being able to load/restore via fastboot I feel totally lost.
Click to expand...
Click to collapse
Try a different USB port. Maybe even a different pc. Fastboot tools was just updated. Make sure you have the latest one.

Maybe you can get a fastboot connection in Linux. Try this:
https://forum.xda-developers.com/showthread.php?t=3526755
Sent from my Nexus 5X using Tapatalk

Thank you both, I tried both another computer, and running this linux version with the fastboot built in, nada! Guess I'm shopping for a new phone. Pixel here I come. Thanks for the help agian.

LG G4 H815 No TWRP Access

Hello members of XDA,
The issue I'm having is pretty rare and found few or non threads about it, so I will try to be the most precise possible.
Yesterday I decided to change the ROM of my LG G4 H815, I was previously on LineageOS, since LineageOS on H815 wasn't developped anymore. So I asked myself why not trying Android Oreo with CypherOS. Before any changes I was with the latest version of LineageOS for H815 and I had TWRP with the version 3.0.2.1. Bootloader was obviously unlocked.
So I starded to download all the required material to switch to CypherOS 5.3.1, while the download I've made a backup of my actual lineageOS installation on my internal storage. Once every thing was downloaded I tried to install CypherOS I had an error 7 in TWRP install box, so I was pretty worried, scouted XDA threads about the error but i was redirected to the solution where you modify the update binary with txt but still didnt worked. I've found a thread talking about updating firmware of the H815 ( https://forum.xda-developers.com/g4/development/v5-8-5-n7-1-2-resurrection-remix-t3704450) While panicking I've done a wipe of everything (dalvik, data,cache and system) .I applied thge firmware update but I also re-read the thread of CypherOS and figured that I needed a newer version of TWRP, installed it so. THen magically CypherOS installed without any issue.
After installing the Gapps (Arm64 8.1 Nano) I rebooted and the first weird thing appears, after seeing the LG screen while the boot I have another screen telling me that the bootloader has been locked and that i should visit g.co/ABH for more information, then CypherOS initialise, CypherOS worked like a charm. So I wanted to go to my TWRP and make a backup in case. I launched ADB and use the command adb reboot recovery, the phone restarted and had the following events : LG logo, warning message about the bootloader, LG logo again and then a black screen. However I was in recovery mode since adb found me with the command fastboot devices. I had no TWRP logo or anything linked to it. Few minutes later, I had the basic recovery mode where you move yourself with the volume buttons and select with power where the functions are pretty limited.
Then I rebooted the phone with adb (fastboot reboot), CypherOS still working perfectly. Thaught that it was the bootloader which back to scratch when he was blocked, I figured out that he was still unlocked, I used the command "fastboot getvar unlocked" through ADB. THen I thaught i had to install back TWRP, tried through the fastboot mode but I had an error
Code:
FAILED (remote: unkown command)
since i tried everything i could even in the basic recovery mode, the only working command in the recovery is "fastboot flash recovery twrp.img" but still does nothing.
I mean it's not that terrible since I can use my phone and i'm about to change phone in 2 months for a Oneplus but i would really like to be able to install magisk on the phone to grant root access and be able to use TWRP on it like I used to. By the way the backup of lineageOS has been deleted while performing unecessary wipes.

Bennou said:
Hello members of XDA,
The issue I'm having is pretty rare and found few or non threads about it, so I will try to be the most precise possible.
Yesterday I decided to change the ROM of my LG G4 H815, I was previously on LineageOS, since LineageOS on H815 wasn't developped anymore. So I asked myself why not trying Android Oreo with CypherOS. Before any changes I was with the latest version of LineageOS for H815 and I had TWRP with the version 3.0.2.1. Bootloader was obviously unlocked.
So I starded to download all the required material to switch to CypherOS 5.3.1, while the download I've made a backup of my actual lineageOS installation on my internal storage. Once every thing was downloaded I tried to install CypherOS I had an error 7 in TWRP install box, so I was pretty worried, scouted XDA threads about the error but i was redirected to the solution where you modify the update binary with txt but still didnt worked. I've found a thread talking about updating firmware of the H815 ( https://forum.xda-developers.com/g4/development/v5-8-5-n7-1-2-resurrection-remix-t3704450) While panicking I've done a wipe of everything (dalvik, data,cache and system) .I applied thge firmware update but I also re-read the thread of CypherOS and figured that I needed a newer version of TWRP, installed it so. THen magically CypherOS installed without any issue.
After installing the Gapps (Arm64 8.1 Nano) I rebooted and the first weird thing appears, after seeing the LG screen while the boot I have another screen telling me that the bootloader has been locked and that i should visit g.co/ABH for more information, then CypherOS initialise, CypherOS worked like a charm. So I wanted to go to my TWRP and make a backup in case. I launched ADB and use the command adb reboot recovery, the phone restarted and had the following events : LG logo, warning message about the bootloader, LG logo again and then a black screen. However I was in recovery mode since adb found me with the command fastboot devices. I had no TWRP logo or anything linked to it. Few minutes later, I had the basic recovery mode where you move yourself with the volume buttons and select with power where the functions are pretty limited.
Then I rebooted the phone with adb (fastboot reboot), CypherOS still working perfectly. Thaught that it was the bootloader which back to scratch when he was blocked, I figured out that he was still unlocked, I used the command "fastboot getvar unlocked" through ADB. THen I thaught i had to install back TWRP, tried through the fastboot mode but I had an error since i tried everything i could even in the basic recovery mode, the only working command in the recovery is "fastboot flash recovery twrp.img" but still does nothing.
I mean it's not that terrible since I can use my phone and i'm about to change phone in 2 months for a Oneplus but i would really like to be able to install magisk on the phone to grant root access and be able to use TWRP on it like I used to. By the way the backup of lineageOS has been deleted while performing unecessary wipes.
Click to expand...
Click to collapse
It's clearly written on the official website and in the official TWRP support thread for the g4 what you have to do when on Nougat bootloader and want to flash TWRP... and keeping it.
Sent from my LG-H815 using XDA Labs

Yet, this still doesnt help me to solve my issue. Do you think there is a way to fix it or no ? If not, I'll just deal with it for the few months lasting.

Bennou said:
Yet, this still doesnt help me to solve my issue. Do you think there is a way to fix it or no ? If not, I'll just deal with it for the few months lasting.
Click to expand...
Click to collapse
Okay if it doesn't work for you you must do something wrong. It works 100%. If you really want help you should explain in detail exactly which steps you took as otherwise it's all just guessing what you're doing.
Sent from my LG-H815 using XDA Labs

Indeed, I didn't followed the procedure exactly, didn't do the step after flashing TWRP (removing battery and boot manually to recovery). Well thank you, was my bad on that.
Should I do a clean new install of cypheros or should I keep it like that, what would be your advice ? Knowing that at the moment CypherOS works like a charm. I also plan to install Magisk on it to root it.
To help others newbie like me, solution can be found here : https://forum.xda-developers.com/g4/development/recovery-twrp-3-touch-recovery-t3442424

Troubles with booting TWRP via adb

Just as the title says, I'm having trouble trying to boot TWRP via adb.
As a quick overview, this phone arrived with an unlocked bootloader from the seller I bought it from at AliExpress. Because of that, I decided to flash Pixel Experience 8.0. I remember back then that it gave me a few issues as well when it came to trying to boot TWRP via adb but somehow managed to do so.
Ultimately, I was able to run the rom without a problem and it was smooth sailing from there. Fast forward to now, I thought it was time that I updated to PE 9. Again, I'm having issues trying to do the same thing. If you're wondering why I don't have TWRP installed, it's because I didn't want to root my phone
due to issues that's connected to Fate Grand Order. I remained unrooted, which meant that I had stock recovery.
My biggest problem is the (Command Write Failed [Invalid Argument]) text when trying to boot TWRP. If it's not that, then it's stuck at "Waiting for device." Both situations lead to "Press any key to shutdown" at the top left corner of the fastboot screen.
Any thoughts?

1. try different port/cable , as some times windows can't talk to device
2. try OrangeFox 8.3-2
3. also flash recovery (native) orange fox 8.3-2

YasuHamed said:
1. try different port/cable , as some times windows can't talk to device
2. try OrangeFox 8.3-2
3. also flash recovery (native) orange fox 8.3-2
Click to expand...
Click to collapse
Thanks for the suggestion. I'll give it a try after work.

Android pie has messed up my twrp and gcam...

Hey everyone, so I saw that there was a new update for MIUI Developer ROM (9.3.28) and I decided to download it. After I downloaded it, i opened twrp and flashed it with lazyflasher as I always do. After the phone boots normally, i realised that the phone had been upgraded to android pie, so I went to check google camera to see if it was working still, but it didnt. So I went back to TWRP to try to enable HAL3 via adb shell, but when i opened TWRP i saw a strange message. It asked for a password in order to decrypt my data. this was the first time i saw it and after searching a bit I tried to use my phones password, but it didnt work. I decided to ignore the message and just open adb shell and enable HAL3. The thing is that when I tried to open it said device not found, which is really strange ( im using the same computer as i was before, adb is installed of course ). I had no choice but to downgrade to stable, so I tried to downgrade to stable rom. Downloaded the rom, but when i chose "choose package" it wouldnt let me install the stable one because it was an older version of android....
So long story short, Android Pie has left me with a non-working Google Camera, TWRP and no ability to downgrade or flash and ROMs.
Any help would be appreciated

https://www.youtube.com/watch?v=bsbZ3kG88Dw

Same problem with me. I tried everything but no luck and now I am unable to use camera2api. So i thought to root my phone and edit build prop manually but when I flashed magisk my phone stuck at boot logo. I lost all my data and I had to flash with mi flash tool. Luckily my bootloader was unlocked.

After flashing Pie, you have to flash a TWRP recover for MIUI Pie. This will allow to decrypt your device (data will be erased).
If you want to rollback to stable (as I did), download fastboot ROM via MIUI official site, boot to bootloader and flash it via flash_all.bat file included in the ROM (assuming you have fastboot on your PC).