So, today i wanted to root and install twrp with the Nexus Root Toolkit v2.1.9.
I followed the instructions and unlocked bootloader successfully.
So the next thing was, that i clicked on root with custom recovery. My Nexus 5x boots in fastboot mode but i get the message, that no fastboot device was found.
i tried several things, other USB Port, other pc, installed dirvers, uninstall drivers, reinstall adb. But nothing works.
I'm kind of confused, don't you need fastboot to unlock the bootloader? I unlocked the bootloader successfully, so whats the problem?
Perou said:
So, today i wanted to root and install twrp with the Nexus Root Toolkit v2.1.9.
I followed the instructions and unlocked bootloader successfully.
So the next thing was, that i clicked on root with custom recovery. My Nexus 5x boots in fastboot mode but i get the message, that no fastboot device was found.
i tried several things, other USB Port, other pc, installed dirvers, uninstall drivers, reinstall adb. But nothing works.
I'm kind of confused, don't you need fastboot to unlock the bootloader? I unlocked the bootloader successfully, so whats the problem?
Click to expand...
Click to collapse
best is to not use a tool kit, just follow the steps of this brilliant guide: http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
in case of questions/problems simply post into the thread mentioned above.
Perou said:
So, today i wanted to root and install twrp with the Nexus Root Toolkit v2.1.9.
I followed the instructions and unlocked bootloader successfully.
So the next thing was, that i clicked on root with custom recovery. My Nexus 5x boots in fastboot mode but i get the message, that no fastboot device was found.
i tried several things, other USB Port, other pc, installed dirvers, uninstall drivers, reinstall adb. But nothing works.
I'm kind of confused, don't you need fastboot to unlock the bootloader? I unlocked the bootloader successfully, so whats the problem?
Click to expand...
Click to collapse
Got the same problem after installing the Developer Preview (7.1.1). No method of installing drivers seems to help on Windows 10. Tried on two different PC's with different cables but no joy.
I found a solution!!!
I had the same problem too ! while on android 7.0 and android 7.1.
In the past I used fastboot with the nexus 5x and it didn't have any issues.
I'm not responsible for anything you will do !!
I didnt tell you to do this , I was just showing my way to fix it.
Do it at your own risk!
So my solution is :
1. connect your device while in fastboot mode.
2. open the device manager (ctrl + X on windows 10)
3. find your device "XXX ADB Device"(Mine was "Alcatel ADB Device" but it can be anything)
4. click on the arrow
5. right click on the Android Bootloader Interface
6. Click on "Properties"
7. Go to "Driver" Tab
8. Click "Uninstall"
9. Mark the "Delete the driver software for this device
10. Click OK
11. Disconnect and Reconnect your device from the cable
12. You are all set !!
(Explanation : Windows will ReSearch for new driver that will work with the nexus 5x)
I'm not responsible for anything you will do !!
I didnt tell you to do this , I was just showing my way to fix it.
Do it at your own risk!
Tell me if this helped you
Tried this just for the hell of it but no success.
have you downloaded the latest sdk tools, platform tools and usb driver from sdk manager?
Giorgos Chatziioannou said:
have you downloaded the latest sdk tools, platform tools and usb driver from sdk manager?
Click to expand...
Click to collapse
Yes. Seriously tried everything. (Apart from something that works of course )
divvykev said:
Yes. Seriously tried everything. (Apart from something that works of course )
Click to expand...
Click to collapse
i had the same trouble awhile ago and i am not sure whay fixed it... but try to go into twrp recovery and check if it works then. if i recall right it worked at the first screen where it asks password for decryption, not after you close it
divvykev said:
Yes. Seriously tried everything. (Apart from something that works of course )
Click to expand...
Click to collapse
Wow! i feel so much better, just knowing i am not the only one with this problem!
I was on Marshmallow, flashed stock Nougat with fastboot, then flashed Kali Nethunter, with TWRP, and now, i want to fastboot flash again, but fastboot is not working.
What i tried so far:
I Have latest Android SDK.
I Flashed 2 different Nougat ROM's from TWRP
I Flashed Vendor Image from TWRP (Atleast that solved the "something wrong with your device" message)
Followed google steps for updating Android Usb Driver
Tried the Uninstall driver steps, from above,
Adb is working fine, its just Fastboot that doesnt want to work
My thinking currently is, the Bootloader.img that is currently flashed is preventing me from Fastboot, but you can flash all images from TWRP except Bootloader and radio, so now i dont know what to do...
---------- Post added at 03:34 PM ---------- Previous post was at 03:30 PM ----------
Giorgos Chatziioannou said:
i had the same trouble awhile ago and i am not sure whay fixed it... but try to go into twrp recovery and check if it works then. if i recall right it worked at the first screen where it asks password for decryption, not after you close it
Click to expand...
Click to collapse
My TWRP is not asking for password for decryption, yet in my bootlaoder, the green "SECURE BOOT - enabled" is still there, and when i boot android, the lock below the google logo, seems locked.
is this normal ?
---------- Post added at 03:45 PM ---------- Previous post was at 03:34 PM ----------
Finaly got it to work, with help from this answer:
http://forum.xda-developers.com/showpost.php?p=64236079&postcount=12
After trying all that i mentioned in previous post, i killed ADB from task manager, switched off phone, booted to bootloader, with hardware buttons, plugged in cable, only after i was already in bootloader, and the voodoo started working for me! i can now see my device in fastboot!
ReeVestrife said:
Wow! i feel so much better, just knowing i am not the only one with this problem!
I was on Marshmallow, flashed stock Nougat with fastboot, then flashed Kali Nethunter, with TWRP, and now, i want to fastboot flash again, but fastboot is not working.
What i tried so far:
I Have latest Android SDK.
I Flashed 2 different Nougat ROM's from TWRP
I Flashed Vendor Image from TWRP (Atleast that solved the "something wrong with your device" message)
Followed google steps for updating Android Usb Driver
Tried the Uninstall driver steps, from above,
Adb is working fine, its just Fastboot that doesnt want to work
My thinking currently is, the Bootloader.img that is currently flashed is preventing me from Fastboot, but you can flash all images from TWRP except Bootloader and radio, so now i dont know what to do...
---------- Post added at 03:34 PM ---------- Previous post was at 03:30 PM ----------
My TWRP is not asking for password for decryption, yet in my bootlaoder, the green "SECURE BOOT - enabled" is still there, and when i boot android, the lock below the google logo, seems locked.
is this normal ?
---------- Post added at 03:45 PM ---------- Previous post was at 03:34 PM ----------
Finaly got it to work, with help from this answer:
http://forum.xda-developers.com/showpost.php?p=64236079&postcount=12
After trying all that i mentioned in previous post, i killed ADB from task manager, switched off phone, booted to bootloader, with hardware buttons, plugged in cable, only after i was already in bootloader, and the voodoo started working for me! i can now see my device in fastboot!
Click to expand...
Click to collapse
nice i ll keep it in mind if happens again
http://forum.xda-developers.com/showpost.php?p=69273414&postcount=33
This is the solution which finally worked for me Very close to the solution posted here.
Many thanks to @TheeWolf
Thank you so much man!!
Related
I flashed a rom from this thread http://forum.xda-developers.com/showthread.php?t=2196742 and now I cant go anywhere past the Google logo.I am able to go in to Download and recovery mode but my phone is not recognized at all even after installing the drivers many times.
I even went to Recovery and used sideload to install a few roms but the phone wont but.Google logo comes and goes and screen stays black.
Is there any way this phone can be saved or is it toast.
Thank You in advance,
And for the love of the god you are calling, how can we help you if we don't know what phone are you using?maybe you should go to a psychic instead of asking help here. we don't read minds,you know that, don't you?
If it's a KDZ then try factory reset.
INSTALL LATEST DRIVER FOR YOUR PHONE MODEL
GO TO RECOVERY AND FULL WIPE AND OPEN INSTALL FROM SIDELOAD
BE SURE YOUR IN SIDELOAD MODE
USE ADB UNIVERSAL DRIVER http://adbdriver.com/
USE LATEST ADB WITHOUT SDK AS OLDER VERSION DONT SUPPORT ADB SIDELOAD
IF NOT DETECTED:
TRY ALL USB PORTS IF NOT TRY INSTALL DRIVER TO ANOTHER PC AND TRY IF UR DEVICE CAN BE DETECTED IN SIDELOAD MODE
---------- Post added at 01:58 PM ---------- Previous post was at 01:50 PM ----------
solentdan said:
i flashed a rom from this thread http://forum.xda-developers.com/showthread.php?t=2196742 and now i cant go anywhere past the google logo.i am able to go in to download and recovery mode but my phone is not recognized at all even after installing the drivers many times.
I even went to recovery and used sideload to install a few roms but the phone wont but.google logo comes and goes and screen stays black.
Is there any way this phone can be saved or is it toast.
Thank you in advance,
Click to expand...
Click to collapse
but phone can be recognized on sideload mode? Did u full wipe before flashing new rom in sideload??
What model # phone do you have? You might be using the wrong ROM section
Am unlocked, S-off, rooted, otherwise stock 4.4.3. Was trying to update to the latest 4.4.4 so replaced TWRP with stock recovery. First attempt failed, red triangle. I figured this was due to Viper4android and the buildprop tweaks that required so I uninstalled the driver and replaced the buildprop with stock version. At this point, I had turned fastboot on and USB debugging off.
After this the phone will not reboot to OS. I can get the HTC screen to flash for a few seconds by pressing Power+VolUp, which then goes black and nothing happens. I can also sometimes get to bootloader, but cannot get my PC to recognize the phone in ADB so not much luck there.
I assume something went wrong with Viper4Android uninstallation or I screwed up the buildprop replacement. Am out of ideas, should I do a factory reset in the bootloader? I do have a TWRP backup, but I can't replace the recovery or anything else through ADB for that matter.
Edit: I did notice in bootloader that OS gets no version info, so something obviously gone wrong there. I just have no idea what to do without ADB. I guess I'm screwed.
Thanks for any help!
MrDelicious said:
Am unlocked, S-off, rooted, otherwise stock 4.4.3. Was trying to update to the latest 4.4.4 so replaced TWRP with stock recovery. First attempt failed, red triangle. I figured this was due to Viper4android and the buildprop tweaks that required so I uninstalled the driver and replaced the buildprop with stock version. At this point, I had turned fastboot on and USB debugging off.
After this the phone will not reboot to OS. I can get the HTC screen to flash for a few seconds by pressing Power+VolUp, which then goes black and nothing happens. I can also sometimes get to bootloader, but cannot get my PC to recognize the phone in ADB so not much luck there.
I assume something went wrong with Viper4Android uninstallation or I screwed up the buildprop replacement. Am out of ideas, should I do a factory reset in the bootloader? I do have a TWRP backup, but I can't replace the recovery or anything else through ADB for that matter.
Edit: I did notice in bootloader that OS gets no version info, so something obviously gone wrong there. I just have no idea what to do without ADB. I guess I'm screwed.
Thanks for any help!
Click to expand...
Click to collapse
Go to captain throbacks site for our m8 he has twrp fishable zips that you flash in your bootlloader. After that you can do a restore or reflash whatever. It might not show the proper os in bootlloader but don't worry bout it you can fix after. You'll be able to see what one your on after you get up and running again. Hopefully that should work. Just make sure you follow the directions correctly on his site. Just Google captain throwback.
---------- Post added at 02:02 AM ---------- Previous post was at 01:57 AM ----------
str8str said:
Go to captain throbacks site for our m8 he has twrp fishable zips that you flash in your bootlloader. After that you can do a restore or reflash whatever. It might not show the proper os in bootlloader but don't worry bout it you can fix after. You'll be able to see what one your on after you get up and running again. Hopefully that should work. Just make sure you follow the directions correctly on his site. Just Google captain throwback.
Click to expand...
Click to collapse
Also best way to update your firmware is thru a bootlloader flushable zip as well you don't have to worry about restoring stock recovery and doesn't matter what rom your on etc. There are threads on how to do it very easy.
str8str said:
Go to captain throbacks site for our m8 he has twrp fishable zips that you flash in your bootlloader. After that you can do a restore or reflash whatever. It might not show the proper os in bootlloader but don't worry bout it you can fix after. You'll be able to see what one your on after you get up and running again. Hopefully that should work. Just make sure you follow the directions correctly on his site. Just Google captain throwback.
---------- Post added at 02:02 AM ---------- Previous post was at 01:57 AM ----------
Also best way to update your firmware is thru a bootlloader flushable zip as well you don't have to worry about restoring stock recovery and doesn't matter what rom your on etc. There are threads on how to do it very easy.
Click to expand...
Click to collapse
Thanks! I shall look into this.
Okay so I'm new to all this rooting and stuff and I was messing around with TWRP and now my when I turn on my OP3, it shows "md5 checksum failed" with "cache:failed", "system: failed", "system_aging:failed" and goes into a bootloop. And I cant even boot it to recovery mode. It's driving me crazy!
Can you still boot into fastboot? Turn on with volume up, if so reflash TWRP, and then restore your backup, or flash a stock rom.
ghostofcain said:
Can you still boot into fastboot? Turn on with volume up, if so reflash TWRP, and then restore your backup, or flash a stock rom.
Click to expand...
Click to collapse
I can boot it into fasboot and I tried flashing TWRP, OxygenOs and even Cyanogenmod. Still didnt work.
Didn't work how, are you getting errors in console?. Can you flash TWRP and boot into it?
You have successfully bricked your device.
Don't worry use a Oneplus download tool to download stock firmware to your device in download mode.
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
The method 2 worked fine for me.
Go ahead..!!
Hope it helps
A bricked device is broken unable to be fixed, this is a soft brick as you can still get it to respond.
For future users if you broke something and want help please supply at least the following.
1. What you did, yes it's embarrassing but maybe someone can undo it.
2. What you are still able to do, can you access recovery, fastboot or adb.
3. What you've tried, if you try and flash something and get an error message let us know.
The more information you supply the better the chances someone can help. A simple my device is bricked help can't achieve much.
So I'm telling now how I got to this situation:
I'd installed a rooted OxygenOS with TWRP. I don't know how I thought it was a good idea to lock the bootloader after I installed TWRP, still did it. After that I was able to load in to fastboot, nothing else. Followed Method 1 on the link from Joyo-rocker and came to the posters message. Now I'm trying Method 2. Will update this post.
Edit: If your phone shows the boot messages "md5 checksum failed" with "cache:failed", "system: failed", "system_aging:failed" you need to fully reload your ROM over the unbrick tool. Look for Method 2 in Joyo-rockers link in this post (cant post links yet)
flobiwahn said:
So I'm telling now how I got to this situation:
I'd installed a rooted OxygenOS with TWRP. I don't know how I thought it was a good idea to lock the bootloader after I installed TWRP, still did it. After that I was able to load in to fastboot, nothing else. Followed Method 1 on the link from Joyo-rocker and came to the posters message. Now I'm trying Method 2. Will update this post.
Click to expand...
Click to collapse
Had the same issue, method 2 works fine.
Hi
I have same issue!!!
I tried the secund method! But the same.....after the 1+ logo :
cache: failed
boot: failed
boot_aging: failed
system: failed
md5 checksum failed
I opened the Msmdownloadertool v3.0.2 using Admin privileges!
Volume up 10s connected phone usb cable....
press 'start" ....after I get green indicator in the tool...My phone rebooted....and I got these messege ! .....and my phone turn off.....
Please help
Please...
kovacsabesz said:
Hi
I have same issue!!!
I tried the secund method! But the same.....after the 1+ logo :
cache: failed
boot: failed
boot_aging: failed
system: failed
md5 checksum failed
I opened the Msmdownloadertool v3.0.2 using Admin privileges!
Volume up 10s connected phone usb cable....
press 'start" ....after I get green indicator in the tool...My phone rebooted....and I got these messege ! .....and my phone turn off.....
Please help
Please...
Click to expand...
Click to collapse
You didnt download the right tool, method 2 includes every needed partition and should revert you to full stock 3.1.2
Oh,
Done.....
I fixed it! Thanks guys!
Deleted
---------- Post added at 09:07 AM ---------- Previous post was at 09:00 AM ----------
sashamalla said:
Okay so I'm new to all this rooting and stuff and I was messing around with TWRP and now my when I turn on my OP3, it shows "md5 checksum failed" with "cache:failed", "system: failed", "system_aging:failed" and goes into a bootloop. And I cant even boot it to recovery mode. It's driving me crazy!
Click to expand...
Click to collapse
Go to the folder where the recovery tool.exe is. Boot your phone into Fastboot.
Search for cache.img, system.img, system_aging.img and put them in your ADB file folder
Type this:
Fastboot devices > doesn't show up? No worries I'll help you later this day just let me now.
Fastboot flash system system.img
Fastboot flash system_aging.img
Fastboot flash cache cache.img
If it boots and you don't have Sim and WiFi. Then reflash Oxygen OS and don't boot it! Boot it into Fastboot and type:
fastboot erase modemst1
fastboot erase modemst2
Now boot it and u can do whatever you want!
Same happened to me, reinstall windows and start again with method two, was a driver issue
TheLoverMan said:
Same happened to me, reinstall windows and start again with method two, was a driver issue
Click to expand...
Click to collapse
Why would you install windows instead fix the driver thing.
Was having problems with uninstalling the drivers. They would always come back so only way I could do it was by a reinstall of windows.
This was already mentioned, as i remember. Just let me search for a minute cause i had this same issue.
http://forum.xda-developers.com/attachment.php?attachmentid=3875375&d=1473889816
Flash this TWRP, it is 3.0.2-19 for temporary but i use it as daily.
kovacsabesz said:
Oh,
Done.....
I fixed it! Thanks guys!
Click to expand...
Click to collapse
Hey! Im having the same problem. Please help me with the way you did, Im Stuck . please help
TheLoverMan said:
Was having problems with uninstalling the drivers. They would always come back so only way I could do it was by a reinstall of windows.
Click to expand...
Click to collapse
Ye well there is a driver enforce mode link even in the hardbrick guide... No need to reinstall Windows lol
I Unbricked Successfully
I unbricked the phone successfullly but now during startup its asking me password. The one I had isn't working and I dont know what to do. can anyone help me here? Can I find a Password in the recovery tool?
Pratik121 said:
I unbricked the phone successfullly but now during startup its asking me password. The one I had isn't working and I dont know what to do. can anyone help me here? Can I find a Password in the recovery tool?
Click to expand...
Click to collapse
You see.. OOS had force encryption. Go to Fastboot and type "fastboot erase userdata" then go to recovery and flash OOS or any other rom.. Password should be gone now.
Okay. I'm desperate... I bricked my OP3 and have no money for a new one!
Here's what happened:
I was running the latest stable version of FreedomOS and everything worked perfectly. I got bored and decided it'd be a good idea to install CM 13. I booted into TWRP and flashed the rom then realized "oh wait i could install CM14" . I went to the XDA thread which said i first had to install a version of Oxygen OS.
Instead of just flashing the O2OS zip through TWRP like a normal person I decided to revert fully to factory settings. I found some instructions on how to do so. They said:
1 - flash stock Recovery
2 - run "fastboot oem lock"
I got this far and reaized that i F***ed up. My OP3 won't boot into recovery or system and i can't run "fastboot oem unlock" (it says remote unlock isn't allowed).
I tried the "Mega Unbrick Guide" but the msn download always fails and says "sahara connection failed"
Is there any way to restore my OP3?
Please say there is... I'm broke and can't afford a new phone... ?
Well, keep trying with that unbrick guide ... It's your best bet.
Btw, re-locking bootloader is not necessary, even if you're reverting to fully stock. It's pointless and can only cause problems, no benefits whatsoever. But now you know that already ...
Sent from my OnePlus 3 using Tapatalk
dmdylan said:
Okay. I'm desperate... I bricked my OP3 and have no money for a new one!
Here's what happened:
I was running the latest stable version of FreedomOS and everything worked perfectly. I got bored and decided it'd be a good idea to install CM 13. I booted into TWRP and flashed the rom then realized "oh wait i could install CM14" . I went to the XDA thread which said i first had to install a version of Oxygen OS.
Instead of just flashing the O2OS zip through TWRP like a normal person I decided to revert fully to factory settings. I found some instructions on how to do so. They said:
1 - flash stock Recovery
2 - run "fastboot oem lock"
I got this far and reaized that i F***ed up. My OP3 won't boot into recovery or system and i can't run "fastboot oem unlock" (it says remote unlock isn't allowed).
I tried the "Mega Unbrick Guide" but the msn download always fails and says "sahara connection failed"
Is there any way to restore my OP3?
Please say there is... I'm broke and can't afford a new phone...
Click to expand...
Click to collapse
Well first off, factory settings is just a wipe from TWRP I have no idea why you would install Stock Recovery and relock the device. That's like...LITERAL restore back to stock like before you even got the device.
Next is that your phone needs to be in fastboot mode in order to run OEM unlock.
Plug the phone into a different USB port and try it if not do a little more digging in the OP forums
No need to panic for as long as you have fastboot, you're all good..
Go here; http://forum.xda-developers.com/oneplus-3/how-to/untouched-oxygen-os-3-2-5-img-boot-img-t3460975
Download the boot and system images and flash through fastboot.. I've done this myself and once your phone boots, install twrp etc..
hagar006 said:
No need to panic for as long as you have fastboot, you're all good..
Go here; http://forum.xda-developers.com/oneplus-3/how-to/untouched-oxygen-os-3-2-5-img-boot-img-t3460975
Download the boot and system images and flash through fastboot.. I've done this myself and once your phone boots, install twrp etc..
Click to expand...
Click to collapse
Thanks for your help but it didn't work because my bootloader is locked
dmdylan said:
Thanks for your help but it didn't work because my bootloader is locked
Click to expand...
Click to collapse
resolveste have the problem ????
Excuse my English, I am Portuguese
---------- Post added at 11:02 AM ---------- Previous post was at 10:57 AM ----------
Excuse my English, I am Portuguese[
---------- Post added at 11:05 AM ---------- Previous post was at 11:02 AM ----------
there is a way to solve this, you have windows 10 ????
When you cannot afford another phone ..why the f you touch your current phone. Leave it as it is... The stock is the most stable. The most battery friendly most performance.
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
unbrick tool
hello,
you need the OnePlus3_Unbrick_Tool_Full.rar to unbrick your phone, i was also in your situation,
you need also the Qualcomm_Diag_QD_Loader_2016_driver.exe with this two tools you can flash to restore the OP3
me helped al lot this thread http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
a had a success with this part How to Make the device show as Qualcomm 9008
it is important that you have the correct driver installed on your pc that the phone will be recognized as Qualcomm 9008
if you need help you can pn me if you want
try this also http://www.androidbrick.com/unbrick-oneplus-one-two-3-qualcomm-hs-usb-qdloader-9008/
1. download one plus rom from the official oneplus website -> s3.amazonaws.com/oxygenos.oneplus.net/OnePlus3Oxygen_16_OTA_015_all_1609141252_c38077177cfc4e74.zip
2. boot in recovery and select install rom from adb -> downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_3.2.6 (follow the Flash Instructions)
3. be happy
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.