Phone is stuck on fastboot after following steps in flashing rom which was wipe dalvik and now is stuck on fastboot
Dernasurboi said:
Phone is stuck on fastboot after following steps in flashing rom which was wipe dalvik and now is stuck on fastboot
Click to expand...
Click to collapse
Need more information. What rom? What steps did you do?
1finger said:
Need more information. What rom? What steps did you do?
Click to expand...
Click to collapse
First I wiped dalvik and when that happened I couldn't find my rom on my internal storage. Then I tried to get out of twrp because when phone reboots it just went to it automatically. Then I tried to flash a stock miui thinking it would solve the problem but it still didn't work. And now its stuck on fastboot
Dernasurboi said:
First I wiped dalvik and when that happened I couldn't find my rom on my internal storage. Then I tried to get out of twrp because when phone reboots it just went to it automatically. Then I tried to flash a stock miui thinking it would solve the problem but it still didn't work. And now its stuck on fastboot
Click to expand...
Click to collapse
Are you able to use any fastboot commands when connected to your PC?
Veiranx said:
Are you able to use any fastboot commands when connected to your PC?
Click to expand...
Click to collapse
yes I am able to use commands via pc
Try command "fastboot continue"
ApexPrime said:
Try command "fastboot continue"
Click to expand...
Click to collapse
it just says "FAILED (remote: Failed to load image from partition: Load Error)"
Just clean flash using miflash and start over
ApexPrime said:
Just clean flash using miflash and start over
Click to expand...
Click to collapse
This is the way.
Dernasurboi said:
Phone is stuck on fastboot after following steps in flashing rom which was wipe dalvik and now is stuck on fastboot
Click to expand...
Click to collapse
If your phone is stuck in fastboot mode after following steps to flash a ROM and wiping the dalvik cache, here are some steps you can try:
Try restarting your phone by holding down the power button for a few seconds. If it doesn't respond, you can try holding down the power button and the volume up button together for a few seconds to see if that triggers a restart.
If restarting the phone doesn't work, try disconnecting it from any cables or power sources and then holding down the power button for at least 10-15 seconds to force a shutdown. Once the phone is off, you can try turning it on again to see if it boots up normally.
If the phone is still stuck in fastboot mode, you can try connecting it to a computer and using the fastboot commands to flash a new ROM or restore a backup. You can find instructions on how to do this online for your specific device.
If none of these steps work, you may need to seek assistance from a professional or contact the manufacturer for support. It's also possible that there is a hardware issue with the phone that needs to be addressed.
I suggest watching Munchy's videos on how to flash a ROM. He does good, easy to understand guides.
Related
Hi
I looked in fastboot if my bootloader is open, than i tried to flash TWRP it gave me an error. Now i try do reboot my phone with fastboot reboot and nothing happen!
I need help please:
taaeem said:
Hi
I looked in fastboot if my bootloader is open, than i tried to flash TWRP it gave me an error. Now i try do reboot my phone with fastboot reboot and nothing happen!
I need help please:
Click to expand...
Click to collapse
1) Did you install the drivers for Huawei p6?
2) Is your phone connected to the computer?
3) Are you in the fastboot folder?
If any of the 3 above aren't done, try installing driver, reconnnect to the computer, or get into the fastboot folder in cmd.
If you did all these, I would try forcing the phone to reboot by holding down the power button for 10 seconds. It should just reboot into the system. It is not my fault if doesn't works tho.
bokchoi2020 said:
1) Did you install the drivers for Huawei p6?
2) Is your phone connected to the computer?
3) Are you in the fastboot folder?
If any of the 3 above aren't done, try installing driver, reconnnect to the computer, or get into the fastboot folder in cmd.
If you did all these, I would try forcing the phone to reboot by holding down the power button for 10 seconds. It should just reboot into the system. It is not my fault if doesn't works tho.
Click to expand...
Click to collapse
I did it with force reboot and worked everything okay
taaeem said:
I did it with force reboot and worked everything okay
Click to expand...
Click to collapse
Hahah glad I can help ;D
I'm a dummy.
First off, I'm still S-On.
I was attempting to flash a GPe ROM using TWRP and figured I'd wipe my phone while I was waiting for ROM to download. I clicked 'Wipe' and after not very carefully choosing my option and typing 'yes' (bottom right button, the one that nukes everything) I found that I couldn't keep my Recovery partitions running because they couldn't mount to the internal storage. TWRP just flickers before finally rebooting into a loop and Philz runs for about 20 seconds while giving me errors that it can't open or mount to `cache/recovery/...` before rebooting into the loop.
I've tried formatting the directories in Philz in separate 20 second windows by hand and have managed to make my way through the list (/cache, /data, /system, etc) to no avail. The errors that Philz gives that it can't open or mount to `/cache/recovery/...` are gone, but there is still only 20 seconds that I'm able to use it before rebooting into a loop. I've tried booting into recoveries with `fastboot boot boot/recovery.img` but those only stay running as long as the flashed recoveries (BTW I've downloaded all the recoveries and ROMs I'm trying multiple times).
It seems like the only thing I have at my disposal right now is Fastboot; ADB works in the 20 second windows, but I haven't been able to find anything on how to fix this and can't do much by myself in 20 seconds; I've tried to use RebootRUU, but as far as I can tell that just brings me to a black screen with HTC and gives me access to Fastboot.
I have no idea what to attempt next, does anyone have any thoughts or pointers? Thank you.
JustLikeThat said:
I'm a dummy.
First off, I'm still S-On.
I was attempting to flash a GPe ROM using TWRP and figured I'd wipe my phone while I was waiting for ROM to download. I clicked 'Wipe' and after not very carefully choosing my option and typing 'yes' (bottom right button, the one that nukes everything) I found that I couldn't keep my Recovery partitions running because they couldn't mount to the internal storage. TWRP just flickers before finally rebooting into a loop and Philz runs for about 20 seconds while giving me errors that it can't open or mount to `cache/recovery/...` before rebooting into the loop.
I've tried formatting the directories in Philz in separate 20 second windows by hand and have managed to make my way through the list (/cache, /data, /system, etc) to no avail. The errors that Philz gives that it can't open or mount to `/cache/recovery/...` are gone, but there is still only 20 seconds that I'm able to use it before rebooting into a loop. I've tried booting into recoveries with `fastboot boot boot/recovery.img` but those only stay running as long as the flashed recoveries (BTW I've downloaded all the recoveries and ROMs I'm trying multiple times).
It seems like the only thing I have at my disposal right now is Fastboot; ADB works in the 20 second windows, but I haven't been able to find anything on how to fix this and can't do much by myself in 20 seconds; I've tried to use RebootRUU, but as far as I can tell that just brings me to a black screen with HTC and gives me access to Fastboot.
I have no idea what to attempt next, does anyone have any thoughts or pointers? Thank you.
Click to expand...
Click to collapse
Try flashing the stock recovery and then factory reset in bootloader then try custom recovery again.
Darknites said:
Try flashing the stock recovery and then factory reset in bootloader then try custom recovery again.
Click to expand...
Click to collapse
I've been trying the only AT&T one that I can find and I get a black screen for a couple of minutes, then a picture of the phone with a red triangle and exclamation point...
JustLikeThat said:
I've been trying the only AT&T one that I can find and I get a black screen for a couple of minutes, then a picture of the phone with a red triangle and exclamation point...
Click to expand...
Click to collapse
Hmm not sure then, only other thing I can think of is ruu but looks like you tried that.
Sent from my HTC One_M8 using Tapatalk
That's OK. Press volume up and down a few times and select factory reset eventually. It takes a few tries and it will show up
SaHiLzZ said:
That's OK. Press volume up and down a few times and select factory reset eventually. It takes a few tries and it will show up
Click to expand...
Click to collapse
I've always been able to select factory reset in bootloader, but it doesn't do anything
JustLikeThat said:
I've always been able to select factory reset in bootloader, but it doesn't do anything
Click to expand...
Click to collapse
Make sure you're in the bootloader go into fastboot and make sure the downloaded image is in the same folder as your fastboot.
fastboot flash recovery stockrecovery.img
fastboot erase cache
fastboot reboot-bootloader
Go into bootloader and then choose Factory Reset - let that finish running <<<Important!
Phone will go out and start bootlooping. Now power off and go back to bootloader mode:
Go into fastboot
fastboot flash recovery <custom recovery>.img
fastboot erase cache
fastboot reboot-bootloader
Now you can go into custom recovery and you should be good to go now.
JustLikeThat said:
I've been trying the only AT&T one that I can find and I get a black screen for a couple of minutes, then a picture of the phone with a red triangle and exclamation point...
Click to expand...
Click to collapse
That just means you have a stock recovery installed but no update to install, press volume up and the power button to enter the stock recovery when you see the red triangle.
ashyx said:
That just means you have a stock recovery installed but no update to install, press volume up and the power button to enter the stock recovery when you see the red triangle.
Click to expand...
Click to collapse
That just caused it to try to boot again :/
SaHiLzZ said:
Make sure you're in the bootloader go into fastboot and make sure the downloaded image is in the same folder as your fastboot.
fastboot flash recovery stockrecovery.img
fastboot erase cache
fastboot reboot-bootloader
Go into bootloader and then choose Factory Reset - let that finish running <<<Important!
Phone will go out and start bootlooping. Now power off and go back to bootloader mode:
Go into fastboot
fastboot flash recovery <custom recovery>.img
fastboot erase cache
fastboot reboot-bootloader
Now you can go into custom recovery and you should be good to go now.
Click to expand...
Click to collapse
Holy balls thank you so so much!!!!!! You are a scholar and a saint!
JustLikeThat said:
Holy balls thank you so so much!!!!!! You are a scholar and a saint!
Click to expand...
Click to collapse
Quick question, is it always best practice to always clear out your cache? is there any risk in clearing it?
My new Asus Zenfone 2 stacked in wiping cache screen in recovery...
unable to do recovery, normal boot
and i think i cant even charge it in this situation...:crying:
manager21 said:
My new Asus Zenfone 2 stacked in wiping cache screen in recovery...
unable to do recovery, normal boot
and i think i cant even charge it in this situation...:crying:
Click to expand...
Click to collapse
My ZenFone 2 also got stuck at wiping case for 10 min or more I thought I should interrupt the process but luckily I left for some more minutes and got unstuck, it takes a lot of time for this phone to wipe case.
try holding power plus volume up for 15 sec to do a hard shut down and open it again.
if it doesn't work try volume down.
It wasn't stuck. The wiping process is just extremely slow compared to your experience with TWRP or CWM. If yours is bricked Asus will likely replace it for you.
"I'd Totally Hug You, If That Was Something I Did"
Ace42 said:
It wasn't stuck. The wiping process is just extremely slow compared to your experience with TWRP or CWM. If yours is bricked Asus will likely replace it for you.
"I'd Totally Hug You, If That Was Something I Did"
Click to expand...
Click to collapse
no. it was stack because i wasnt patient and i stop it... but i fixed it with ADB Fastboot and the command "fastboot erase cache"
then i did a factory reset also very slow at wiping data, formatting data but i take my lesson and i was patient this time!
It's really slow, I bricked mine by updating while rooted accidentally and go stuck in fastboot with no ROM or recovery for a while however I managed to fix it. Patience is key in most cases
Pilz said:
It's really slow, I bricked mine by updating while rooted accidentally and go stuck in fastboot with no ROM or recovery for a while however I managed to fix it. Patience is key in most cases
Click to expand...
Click to collapse
I brick my phone like you. Now I can use fastboot but not ADB and don't have unlocked bootloader. How can I fix my zenfone?:crying:
Eruz said:
I brick my phone like you. Now I can use fastboot but not ADB and don't have unlocked bootloader. How can I fix my zenfone?:crying:
Click to expand...
Click to collapse
If you can enter fastboot, I think you can also enter recovery.
- If you don't care about your data enter recovery and do a wipe data (it may take very very long so please wait). When it reboots, if it's not working flash the original image from Asus site (the same version you have installed) via ADB Sideload in recovery.
- If you have to save your data run tethered TWRP, do a full backup on your microsd, use the TWRP file manager to copy all your internal memory on microsd. For recover apps data, use Titanium backup for recover apps from nandroid backup after you wiped everyting.
marcof93 said:
If you can enter fastboot, I think you can also enter recovery.
- If you don't care about your data enter recovery and do a wipe data (it may take very very long so please wait). When it reboots, if it's not working flash the original image from Asus site (the same version you have installed) via ADB Sideload in recovery.
- If you have to save your data run tethered TWRP, do a full backup on your microsd, use the TWRP file manager to copy all your internal memory on microsd. For recover apps data, use Titanium backup for recover apps from nandroid backup after you wiped everyting.
Click to expand...
Click to collapse
I don't care about data, I'll try first method. But before I bricked my phone, I have firmware version 2.18. Now I update boot and recovery images to version 2.19 by fastboot: I have to downgrade them before wipe data or it's not important?
Eruz said:
I don't care about data, I'll try first method. But before I bricked my phone, I have firmware version 2.18. Now I update boot and recovery images to version 2.19 by fastboot: I have to downgrade them before wipe data or it's not important?
Click to expand...
Click to collapse
Enter fastboot and connect your phone to pc. If you have adb installed and intel drivers, after connect your phone to pc while in fastboot, open cmd and type: Fastboot erase cache
It will go back to normal after
It stuck on the boot animation with animated ring by 40 minutes. I have to wait more? Is there another way to fix it (like flashing with Odin as a couple of years ago)?
I have already wipe cache, data and all wipeable things
Thanks guys
Eruz said:
It stuck on the boot animation with animated ring by 40 minutes. I have to wait more? Is there another way to fix it (like flashing with Odin as a couple of years ago)?
I have already wipe cache, data and all wipeable things
Thanks guys
Click to expand...
Click to collapse
Just press power button until phone turns off. After that enter fastboot and do what I told you
sirsomething said:
Just press power button until phone turns off. After that enter fastboot and do what I told you
Click to expand...
Click to collapse
I know that but what will I do? I already try to wipe that partitions and the phone is still bricked. Sorry for my bad english, dude.
Eruz said:
I know that but what will I do? I already try to wipe that partitions and the phone is still bricked. Sorry for my bad english, dude.
Click to expand...
Click to collapse
Did you get stuck on bootloader after wiping the cache?
sirsomething said:
Did you get stuck on bootloader after wiping the cache?
Click to expand...
Click to collapse
Yep, for 40 minutes. I wiped it again and restart but nothing changes.
Eruz said:
Yep, for 40 minutes. I wiped it again and restart but nothing changes.
Click to expand...
Click to collapse
Can you enter Recovery or only fastboot?
sirsomething said:
Can you enter Recovery or only fastboot?
Click to expand...
Click to collapse
I can enter stock recovery and fastboot, but not ADB
Eruz said:
I can enter stock recovery and fastboot, but not ADB
Click to expand...
Click to collapse
ADB is installed on your computer and you enter via command line. How can you not acess it? It is just opening the command line and write the code i told you
sirsomething said:
ADB is installed on your computer and you enter via command line. How can you not acess it? It is just opening the command line and write the code i told you
Click to expand...
Click to collapse
ADB doesn't recognize my device, fastboot does. I enabled USB debugging mode and ADB always worked before I updated Zenfone this morning, but now don't. Is it possible enable 'Update zip from SDCard' instead ADB? Maybe I can fix it in this way
PS before Zenfone I had a Galaxy Nexus and I have a bit of confident with ADB, fastboot, ROM and other stuff, so I know what they are and how work
Eruz said:
ADB doesn't recognize my device, fastboot does. I enabled USB debugging mode and ADB always worked before I updated Zenfone this morning, but now don't. Is it possible enable 'Update zip from SDCard' instead ADB? Maybe I can fix it in this way
PS before Zenfone I had a Galaxy Nexus and I have a bit of confident with ADB, fastboot, ROM and other stuff, so I know what they are and how work
Click to expand...
Click to collapse
Sorry for the misunderstanding then. I don't think i can help you in that case :x have you tried to reinstall intel drivers or something?
sirsomething said:
Sorry for the misunderstanding then. I don't think i can help you in that case :x have you tried to reinstall intel drivers or something?
Click to expand...
Click to collapse
Yep, unistalled all Intel, Asus or Google driver and then reinstalled Intel driver. I think if I can installed custom bootlader ADB will be enabled.
Btw thanks man :highfive::highfive:
So before I get linked to a bunch of solutions, here's what I've tried so far as I do have fastboot access:
I've tried flashing the latest factory image from Google. Both manually from fastboot and with NRT, all to no avail. It shows the Google logo then reboots repeatedly. I've tried entering recovery to factory reset there after flashing, but the device won't get into recovery.
I've also tried this method, but I can't get the device to enter download mode. It shows that it's entering it for a moment when I plug it into my computer while holding volume up, but then reboots into the bootloop again.
There's one weird thing that should be noted that makes me think this is some weird software issue, and not a hardware failure. I let the device bootloop all night last night until the battery died. When I powered it on this morning it went all the way to the Android setup page where you select wifi, etc and go from there. However, when I plugged it in and kept going through setup, it rebooted and has been looping since. I've contacted Google and they're supposed to conference call me with LG to see what we can do. Do I have any options other than that? Thanks for any help.
From bootloader
fastboot erase cache
fastboot format cache
fastboot erase user
fastboot format user
BTW what exactly is happening when you say it doesn't enter recovery?
addisontodd said:
So before I get linked to a bunch of solutions, here's what I've tried so far as I do have fastboot access:
I've tried flashing the latest factory image from Google. Both manually from fastboot and with NRT, all to no avail. It shows the Google logo then reboots repeatedly. I've tried entering recovery to factory reset there after flashing, but the device won't get into recovery.
I've also tried this method, but I can't get the device to enter download mode. It shows that it's entering it for a moment when I plug it into my computer while holding volume up, but then reboots into the bootloop again.
There's one weird thing that should be noted that makes me think this is some weird software issue, and not a hardware failure. I let the device bootloop all night last night until the battery died. When I powered it on this morning it went all the way to the Android setup page where you select wifi, etc and go from there. However, when I plugged it in and kept going through setup, it rebooted and has been looping since. I've contacted Google and they're supposed to conference call me with LG to see what we can do. Do I have any options other than that? Thanks for any help.
Click to expand...
Click to collapse
it's seems like me , it's been a month i can't boot it up .
sfhub said:
From bootloader
fastboot erase cache
fastboot format cache
fastboot erase user
fastboot format user
BTW what exactly is happening when you say it doesn't enter recovery?
Click to expand...
Click to collapse
I choose reboot recovery from the fastboot menu and it just boot loops. It won't enter recovery.
addisontodd said:
I choose reboot recovery from the fastboot menu and it just boot loops. It won't enter recovery.
Click to expand...
Click to collapse
what if you try
fastboot boot twrp.img
I've bootlooped so many times I don't know where to start.
So you flashed the factory IMG from your bootloader correct.
Fastboot -w will wipe without wiping system.
Then reflash your whole system. I would redownload from the Google site through Skipsoft...the easiest way. When it asks to keep or flash new recovery you want to flash the stock recovery.
http://forum.xda-developers.com/nex...olkit-skipsoft-android-toolkit-nexus-t3230444
You'll have to reroot afterwards which you can also do through skipsoft.
Profit... Thank me if I helped.
It's a Hardware issue. Installing system again will not fix it. Send it to LG for a repair. My phone had the same issue.
Hi guys,
Rooted Oneplus 3 is soft bricked. Please help me!!! :crying:
:crying:Quick desription: Fastboot formatted it. My PC detects it.
Tried to Fastboot flash latest TWRP ("twrp-3.0.2-0-oneplus3.img") via CMD Prompt.
After that I get a message saying that the processed was "finished" (within 0.802s!).
Now I reboot+volume down and bootloop continues. Phone starts, I see the normal warnings I used to get after rooting it. Then I see the Oneplus logo for a fraction of a second and then it boots again and the process repeats itself.
I think it may be worth mentioning that the reason all this happened is an encryption problem that occurred while I was flashing a rom update with TWRP: After the flashing finished, got an error saying "unable to mount storage". Wiped cache+dalvik and then restarted. Got a black screen that did not display any signs of life after several minutes. Then turned it off and on by long press on the power button. Then I got an error saying that the encyption process was disrupted and that I have to wipe my phone (strange given that I did not select any encryption button in TWRP). Anyhow, then I fastboot formatted the phone and that's it.
Thank so much for anyone who can help!!!
fastboot flash recovery recovery.img (I recommend blu_spark's TWRP) reboot to recovery, if it doesn't work, try:
fastboot boot recovery recovery.img
See if you boot to recovery and then try flashing a custom ROM.
Hi Fobos, thanks for responding quickly.
I tried using fastboot boot command (with twrp-3.0.2-0-oneplus3.img). No luck with that.
Also, didn't find a downloadable blu_spark *.img version for twrp recovery. would you be so kind to add a link?
Thank you.
Now I think it's hard bricked ( Help!!!
Phone just stopped responding. Mostly doesn't respond. Occasionaly turns on for a nano second, flashes the +1 logo and turns off. Most of the time it doesnt even do that any more when I press (long / short press) the power button!
Somebody help, please!!
ppppp44 said:
Phone just stopped responding. Mostly doesn't respond. Occasionaly turns on for a nano second, flashes the +1 logo and turns off. Most of the time it doesnt even do that any more when I press (long / short press) the power button!
Somebody help, please!!
Click to expand...
Click to collapse
Keep calm and breath in. I was in the same situation.
Take a breath.
So, you have 2 ways depending on what you want. You can either go back to full stock with a flashing tool or you can install a custom recovery and then installing a custom rom (or stock one). I suggest the flashing tool.
Just follow the steps here: https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306 and if you have any question come back here and ask them.
Good luck.
Recoveryhttps://forum.xda-developers.com/devdb/project/dl/?id=24575
First format recovery by using command
fastboot format recovery
then flash recovery using
fastboot flash recovery "recovery.img"
Kayembe said:
Keep calm and breath in. I was in the same situation.
Take a breath.
So, you have 2 ways depending on what you want. You can either go back to full stock with a flashing tool or you can install a custom recovery and then installing a custom rom (or stock one). I suggest the flashing tool.
Just follow the steps here: https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306 and if you have any question come back here and ask them.
Good luck.
Click to expand...
Click to collapse
Hey Keyembe, thanks for the reply...
Tried to follow the instructions you posted. Did everything to allow unsigned drivers to be installed. Disabled it on from the advanced boot settings, and - when that didn't work, also running on test mode. Neither options work:
In the device manager I right click the android device (currently in fastboot mode), which is installed with Google drivers. I try to update the driver software to the unsigned driver and I get an error saying it's not compatible with my system (Win10 Pro) and that I should make sure it is compatible with an x64 based system.
What now?
Tx
Hey! Thanks for the reply...
anup807 said:
Recoveryhttps://forum.xda-developers.com/devdb/project/dl/?id=24575
First format recovery by using command
fastboot format recovery
then flash recovery using
fastboot flash recovery "recovery.img"
Click to expand...
Click to collapse
Hi Anup!
Thanks for the link to the Blu_Spark version of TWRP.
On CMD Prompt, tried to format recovery, console stopped responding. "Fastboot format recovery"...Just stops responding
Also tried "Fastboot delete recovery". I get a message saying "deleting recovery..." then also stops responding. Nothing happens from there.
I tried to use the OPO3 Root Toolkit. It does detect the fastboot device, but when I try to flash or boot or do anything else other than detection, it is unable to find the device. Says operation failed.
What now? :crying:
You could look through this post if nothing else helps.
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
Machiel187 said:
You could look through this post if nothing else helps.
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
Click to expand...
Click to collapse
Check your cable (try another one), even reinstall your adb drivers on your machine (if Windows).
Let the device charge for 30 minutes at least then retry (charge with new cable too).
ppppp44 said:
Hey Keyembe, thanks for the reply...
Tried to follow the instructions you posted. Did everything to allow unsigned drivers to be installed. Disabled it on from the advanced boot settings, and - when that didn't work, also running on test mode. Neither options work:
In the device manager I right click the android device (currently in fastboot mode), which is installed with Google drivers. I try to update the driver software to the unsigned driver and I get an error saying it's not compatible with my system (Win10 Pro) and that I should make sure it is compatible with an x64 based system.
What now?
Tx
Hey! Thanks for the reply...
Click to expand...
Click to collapse
Firstly, plug your phone on your computer in recovery mode or fastboot mode.
When you go in cmd and you type "adb devices" do you get anything?
If that works and you still can access recovery, you can install stock rom available on the OnePlus site. Here's a link : http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_4.1.3/
Boot into recovery, then install from adb.
Machiel187 said:
You could look through this post if nothing else helps.
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
Click to expand...
Click to collapse
Thanks mate, followed the instructions on this post. I never get the device to be detected as Qualcomm. All I get is "Android Phone". I did install the Qualcomm drivers despite the warning I got for installing unsigned drivers. Installation went OK. When I go to the device manager again I still identifies the device as android phone. Also when I click "Have Disk" and select the qualcomm drivers I get an error saying they are incompatible with the device or with an x64 based system (regardless of them being signed or not).
Any ideas?
thanks again..
Kayembe said:
Firstly, plug your phone on your computer in recovery mode or fastboot mode.
When you go in cmd and you type "adb devices" do you get anything?
If that works and you still can access recovery, you can install stock rom available on the OnePlus site. Here's a link : http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_4.1.3/
Boot into recovery, then install from adb.
Click to expand...
Click to collapse
Hey Kayembe,
I only get to fastboot mode. No Adb device detected. No recovery mode available.
ppppp44 said:
Thanks mate, followed the instructions on this post. I never get the device to be detected as Qualcomm. All I get is "Android Phone". I did install the Qualcomm drivers despite the warning I got for installing unsigned drivers. Installation went OK. When I go to the device manager again I still identifies the device as android phone. Also when I click "Have Disk" and select the qualcomm drivers I get an error saying they are incompatible with the device or with an x64 based system (regardless of them being signed or not).
Any ideas?
thanks again..
Click to expand...
Click to collapse
Strange. Are you sure you turned off Driver Signature Enforcement?
When you hold the power button 10 seconds and plug the phone in, it should not be on. The screen should stay black. (looks like its off)
So make sure it's not trying to boot, because then it probably shows up as Android Phonee again.
Machiel187 said:
Strange. Are you sure you turned off Driver Signature Enforcement?
When you hold the power button 10 seconds and plug the phone in, it should not be on. The screen should stay black. (looks like its off)
So make sure it's not trying to boot, because then it probably shows up as Android Phonee again.
Click to expand...
Click to collapse
That's exactly what happens but when it's not in fastboot mode [ either after 10 seconds power button press or after i see the +1 logo (black screen)] - phone is not detected by my pc.
Yeah I'm sure about the driver signature enforcement. It's definitely off.
What am I doing wrong?
Thanks
ppppp44 said:
That's exactly what happens but when it's not in fastboot mode [ either after 10 seconds power button press or after i see the +1 logo (black screen)] - phone is not detected by my pc.
Yeah I'm sure about the driver signature enforcement. It's definitely off.
What am I doing wrong?
Thanks
Click to expand...
Click to collapse
I'm going to do a unbrick in a few hours.. Make sure Driver Enforcement is off. If you go to device manager and right click on it you can change the drivers somewhere so it shows up as described in the post..
Make sure you use method 2.
Puddi_Puddin said:
I'm going to do a unbrick in a few hours.. Make sure Driver Enforcement is off. If you go to device manager and right click on it you can change the drivers somewhere so it shows up as described in the post..
Make sure you use method 2.
Click to expand...
Click to collapse
ok I somehow managed to flash Blu_Spark Twrp and got it to work.
Within TWRP, flashed OnePlus3Oxygen_16_OTA_051_all_1704112009_2521.zip
and also SuperSU.zip, and no_verity.zip.
Getting some errors.
Device still doesn't boot.
Attaching the log TXT here.
I am desperate... please help.,..
Puddi_Puddin said:
I'm going to do a unbrick in a few hours.. Make sure Driver Enforcement is off. If you go to device manager and right click on it you can change the drivers somewhere so it shows up as described in the post..
Make sure you use method 2.
Click to expand...
Click to collapse
BTW, Now when I enter recovery mode on TWRP I am asked to put in a password to decrypt data. I don't have any such password any tried to go over the process of reformatting the device and flashing twrp again. that didn't make this decryption message go away...
((
ppppp44 said:
BTW, Now when I enter recovery mode on TWRP I am asked to put in a password to decrypt data. I don't have any such password any tried to go over the process of reformatting the device and flashing twrp again. that didn't make this decryption message go away...
((
Click to expand...
Click to collapse
try "default_password" for the password
ppppp44 said:
BTW, Now when I enter recovery mode on TWRP I am asked to put in a password to decrypt data. I don't have any such password any tried to go over the process of reformatting the device and flashing twrp again. that didn't make this decryption message go away...
((
Click to expand...
Click to collapse
Go to Fastboot type 'fastboot erase userdata' (you have to reflash OOS tho.. Make sure you are on the latest TWRP. I'm not a fan of Bluspark but his TWRP is currently more up 2 date.