SOLVED! See my last post on How-To
So, I can't access fastboot. At all. I've tried the following:
Power+Up - Nothing
Boot to fastboot from stock Recovery - Nothing
Boot to fastboot from OS (Advanced power menu) - Nothing
Boot to fastboot from All in One Tool - Nothing
Tried from 3.2.8, and 3.2.7, same result. I have an unlocked bootloader, but that shouldn't matter. And I can't lock it either, since I have no fastboot access.
I can access stock recovery, but have no way to install TWRP.
Please help!
Are u rooted?
Dupleshwar said:
Are u rooted?
Click to expand...
Click to collapse
Was, but with a stock restore I'm fairly sure the root is gone.
deecept said:
Was, but with a stock restore I'm fairly sure the root is gone.
Click to expand...
Click to collapse
You can sideload zips with stock recovery
---------- Post added at 12:44 PM ---------- Previous post was at 12:43 PM ----------
U can try flashing stock again after a backup
Dupleshwar said:
You can sideload zips with stock recovery
U can try flashing stock again after a backup
Click to expand...
Click to collapse
I don't care about data here, so I have tried reflashing stock several times. Both 3.2.7 and 3.2.8, but still refuses to boot into bootloader so I can use fastboot.
Sideload is used to flash stock zip. It still refuses to boot into bootloader mode.
Sorry this as far as I know and can help hope u find a solution soon
Sideload oxygen 3.2.4. The newer ones have updated firmware. once ur in 3.2.4 then try to boot into fastboot.. you should be able to
ihuman007 said:
Sideload oxygen 3.2.4. The newer ones have updated firmware. once ur in 3.2.4 then try to boot into fastboot.. you should be able to
Click to expand...
Click to collapse
Thanks man .. but no go. Still won't boot into fastboot from any of the ways possible.
I'm running out of things to try here! Trying to OTA update from 3.2.4 to 3.2.7 now, see if that helps.
Try adb reboot bootloader?
Sent from my ONEPLUS A3000 using Tapatalk
I did notice something weird. Whenever I'm in stock recovery, and ask to boot to Fastboot, the phone vibrates twice. It seems it's trying to boot into fastboot/bootloader, but fails, and then reboots (second vibration) into the "this phone can't be trusted" image.
Unsure what that means, other than something for sure is corrupt. Any and all help is greatly appreciated!
AFschizoid said:
Try adb reboot bootloader?
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
Tried, does nothing Same as any other option to boot into bootloader. Thanks tho
Ok turn it off, hold volume up, and plug it in to the computer and tell me if it shows anything in device manager
Sent from my ONEPLUS A3000 using Tapatalk
AFschizoid said:
Try adb reboot bootloader?
Click to expand...
Click to collapse
Second this suggestion.
OP, do you have adb set up? - http://forum.xda-developers.com/showthread.php?t=2588979&page=93
Sent from my OnePlus 3 using XDA Labs
Just saw the post about it vibrating twice. Could be a corrupt fastboot. If you don't want to delete data use method one from this thread. If you don't care use method 2 https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
Sent from my ONEPLUS A3000 using Tapatalk
AFschizoid said:
Ok turn it off, hold volume up, and plug it in to the computer and tell me if it shows anything in device manager
On a Mac, but in System Information QUSB_BULK shows up, with some info indication qualcomm. So at least SOMETHINGS happening here.
Click to expand...
Click to collapse
Ok so it shows qusb bulk but didn't boot bootloader? Give me a min, gotta do some hunting. Or if you get an xp virtual machine set up can use that thread
Sent from my ONEPLUS A3000 using Tapatalk
SOLVED:
I used the MSM Download Tool. I can find the device, and it has FINISHED! It now actually works!
Thanks SO much for suggestions!
Prerequsites:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
Windows OS
How to:
1. Power off device completely
2. Hold volume up while plugging in, keep holding until Windows; Device manager shows device or Mac: System Information -> USB shows device
3. Install drivers (follow guide in above link)
4. Start MSM Download Tool and press start
5. It should download, and let you know when it's complete. Then reboot into bootloader/Fastboot.
FIXED! Thanks so so much
Good luck
Pretty useless with anything apple as I don't use it lol. Most I've ever done was out a new hard drive and ram in and install snow leopard lol
Sent from my ONEPLUS A3000 using Tapatalk
deecept said:
SOLVED:
I used the MSM Download Tool. I can find the device, and it has FINISHED! It now actually works!
Thanks SO much for suggestions!
Prerequsites:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
Windows OS
How to:
1. Power off device completely
2. Hold volume up while plugging in, keep holding until Windows; Device manager shows device or Mac: System Information -> USB shows device
3. Install drivers (follow guide in above link)
4. Start MSM Download Tool and press start
5. It should download, and let you know when it's complete. Then reboot into bootloader/Fastboot.
FIXED! Thanks so so much
Click to expand...
Click to collapse
Happy it worked for ya! 😄
Sent from my ONEPLUS A3000 using Tapatalk
Related
I was attempting to unlock/root and long story short, now I have TWRP installed, and I can get to FASTBOOT but if i try to boot normally I get the Nexus logo, and no further. When I unlocked, I installed TWRP then loaded it. After leaving TWRP it said 'Seems you are not rooted, want to root"? or something to that effect. I clicked YES and now I'm stuck. Since I had just unlocked it, it *should* have reset my entire device(which was all stock anyway) so I am not sure what went wrong. I have been trying everything I know but I'm now out of ideas. Would appreciate any help. I see now that the version of SuperSu that it would have pushed would have been wrong, would that be preventing the tablet from booting?
If you can mount in fastboot you're not bricked. You tried to check md5 and push the recovery image again? And also try to throw new ROM on it.
Sent from my HTC One using xda app-developers app
ronni.rasmussen said:
If you can mount in fastboot you're not bricked. You tried to check md5 and push the recovery image again? And also try to throw new ROM on it.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
It wont boot so I don't know how to put anything on it, it's empty and doesn't show up in windows. Also I don't know what you meant exactly by push the recovery image again. Twrp is working fine. Sorry I am hardly a pro at this stuff.
Landara said:
It wont boot so I don't know how to put anything on it, it's empty and doesn't show up in windows. Also I don't know what you meant exactly by push the recovery image again. Twrp is working fine. Sorry I am hardly a pro at this stuff.
Click to expand...
Click to collapse
Try to get to fastboot and connect PC and check if it connects. You will need the USB drivers installed
Sent from my HTC One using xda app-developers app
ronni.rasmussen said:
Try to get to fastboot and connect PC and check if it connects. You will need the USB drivers installed
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Oh I can do that no problem, been using ADB. But now it just won't boot normally. But I can use the terminal and everything.
Landara said:
Oh I can do that no problem, been using ADB. But now it just won't boot normally. But I can use the terminal and everything.
Click to expand...
Click to collapse
Then it should be possible to flash and push recovery and ROM to device even get a stock image back.
Which recovery image did you install?
And did you flash any ROM or kernel?
Sent from my HTC One using xda app-developers app
Landara said:
Oh I can do that no problem, been using ADB. But now it just won't boot normally. But I can use the terminal and everything.
Click to expand...
Click to collapse
I would suggest you just restore your N7 back to stock. No need for root yet, seriously! But this should help get you going in the right direction.
Power it off completely. Hold Power + Volume down until it boots into the bootloader. Run the following commands:
fastboot devices (to confirm you are connected)
fastboot flash recovery recovery.img
If you haven't unlocked your N7 yet, run fastboot oem unlock first.
ronni.rasmussen said:
Then it should be possible to flash and push recovery and ROM to device even get a stock image back.
Which recovery image did you install?
And did you flash any ROM or kernel?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I put TWRP on there, immediately after unlocking. So it should have been completely stock since as far as I know it wipes it when you unlock. After putting TWRP on there, i told it to reboot normally(from within TWRP) and it detected that I was not rooted and asked me if I wanted to install SuperSu. I said yes and now it will not boot to the operating system. It boots fine to Bootloader and Recovery. And I am certain it's connected to my PC because I can even tell it ADB REBOOT BOOTLOADER/RECOVERY and that works. But I don't see how I can load a ROM onto it if I can't access it via windows. I don't know how to get a ROM onto the SD card. Surely there could be a way but I don't know it.
Landara said:
I put TWRP on there, immediately after unlocking. So it should have been completely stock since as far as I know it wipes it when you unlock. After putting TWRP on there, i told it to reboot normally(from within TWRP) and it detected that I was not rooted and asked me if I wanted to install SuperSu. I said yes and now it will not boot to the operating system. It boots fine to Bootloader and Recovery. And I am certain it's connected to my PC because I can even tell it ADB REBOOT BOOTLOADER/RECOVERY and that works. But I don't see how I can load a ROM onto it if I can't access it via windows. I don't know how to get a ROM onto the SD card. Surely there could be a way but I don't know it.
Click to expand...
Click to collapse
Start over by downloading recovery, Superuser and a clean stock rom image.
But before that you could try to reset all data in recovery (factory reset) and cache if you haven't tried.
http://forum.xda-developers.com/showthread.php?t=2380913
Thanks to this thread I have booted! Still have to root it but now that I know that you have to flash the NEW SuperSu not the one TWRP flashed for me, I shouldn't have a problem Thanks so much for your help everyone!
Landara said:
http://forum.xda-developers.com/showthread.php?t=2380913
Thanks to this thread I have booted! Still have to root it but now that I know that you have to flash the NEW SuperSu not the one TWRP flashed for me, I shouldn't have a problem Thanks so much for your help everyone!
Click to expand...
Click to collapse
Super
Hi,
I've really big problem and i hope that here i get sugestion...
1, I try flash new ROM to my phone. I copy ROM to "SD card" but in wrong version.
After this I into Flashtool get new Kernel and new ver. of TWRecovery. Then I go to recovery and start flashing as every time before...
2, But now I'm in bad sittuation. I can only get into recovery... When i want to go to bootloger, i can't. Every time when I go to bootloger from recovery, i'm back in recovery. Every time is phone reaction the same as I hold power up button+vol. up. And I'm only in recovery.
When I want transfer some ROM to phone, I can't. Cose when I Mount USB massstorage I see phone as "Elementary sys device". I have install ABD device drivers...
Changelog I can't get you, cose it's in "SD card"...
3, Please, Show me "the way" out of this sh*t... I use HTC HD2 few years, all time flashing. Now I use Xperia S for 3 yr. All time flashing. But now I'm in a wrong way ind can't get my phone to standby
Thank you for answers!
magntwo said:
Hi,
I've really big problem and i hope that here i get sugestion...
1, I try flash new ROM to my phone. I copy ROM to "SD card" but in wrong version.
After this I into Flashtool get new Kernel and new ver. of TWRecovery. Then I go to recovery and start flashing as every time before...
2, But now I'm in bad sittuation. I can only get into recovery... When i want to go to bootloger, i can't. Every time when I go to bootloger from recovery, i'm back in recovery. Every time is phone reaction the same as I hold power up button+vol. up. And I'm only in recovery.
When I want transfer some ROM to phone, I can't. Cose when I Mount USB massstorage I see phone as "Elementary sys device". I have install ABD device drivers...
Changelog I can't get you, cose it's in "SD card"...
3, Please, Show me "the way" out of this sh*t... I use HTC HD2 few years, all time flashing. Now I use Xperia S for 3 yr. All time flashing. But now I'm in a wrong way ind can't get my phone to standby
Thank you for answers!
Click to expand...
Click to collapse
Boot phone into recovery, then run following command to copy the ROM to phone memory.
Code:
adb push /path/to/ROM.zip /sdcard/
Then flash the ROM via recovery!
Mirhawk said:
Boot phone into recovery, then run following command to copy the ROM to phone memory.
Code:
adb push /path/to/ROM.zip /sdcard/
Then flash the ROM via recovery!
Click to expand...
Click to collapse
You mean into terminal command? I need to get phone into fasboot. then I can do what I want.. Now it's dead phone... It was happend when I want to flash yours ROM. But i miss one step, flash boot.img
magntwo said:
You mean into terminal command? I need to get phone into fasboot. then I can do what I want.. Now it's dead phone... It was happend when I want to flash yours ROM. But i miss one step, flash boot.img
Click to expand...
Click to collapse
Recovery is TWRP. The one with menu of install, wipe and all. You need to boot into that and use the adb on PC.
Mirhawk said:
Recovery is TWRP. The one with menu of install, wipe and all. You need to boot into that and use the adb on PC.
Click to expand...
Click to collapse
Yes, I'm in TWRP, exactly v.2.8.0.1, from topic of your ROM. Bud now I can't connect phone via ABD drivers. I try it via apps and two ways via Commans window.
I'm only in TWRP. I can't get to fastboot, I can't install ROM now, phone reaction is the same as I hold power up+vol up button.
I need one of two ways... 1,get phone connected with PC via fastboot to flash new kernel, boot.img and at least your ROM
2,get phone connected with PC via mass storage, to get some old ROM, flash it and get to fastboot...
For example:
magntwo said:
Yes, I'm in TWRP, exactly v.2.8.0.1, from topic of your ROM. Bud now I can't connect phone via ABD drivers. I try it via apps and two ways via Commans window.
I'm only in TWRP. I can't get to fastboot, I can't install ROM now, phone reaction is the same as I hold power up+vol up button.
I need one of two ways... 1,get phone connected with PC via fastboot to flash new kernel, boot.img and at least your ROM
2,get phone connected with PC via mass storage, to get some old ROM, flash it and get to fastboot...
For example:
Click to expand...
Click to collapse
You cannot use fastboot command in recovery, You can use the adb commands only. Did Yo try pushing the ROM to phone?
Mirhawk said:
You cannot use fastboot command in recovery, You can use the adb commands only. Did Yo try pushing the ROM to phone?
Click to expand...
Click to collapse
Yes, I was... I have in "sd card" save my last ROM+gapps. As I wrote, two ways when I try it. One is Fail of flash by TWRP, second fall of TWRP during flash.
Ty for "want to help"!
magntwo said:
Yes, I was... I have in "sd card" save my last ROM+gapps. As I wrote, two ways when I try it. One is Fail of flash by TWRP, second fall of TWRP during flash.
Ty for "want to help"!
Click to expand...
Click to collapse
Ah apologies, got lost while replying.
Anyways, lets start from basic. Can You try un-installing and installing the fastboot drivers? Because I suspect that's why You are not able to enter into fastboot mode.
Mirhawk said:
Ah apologies, got lost while replying.
Anyways, lets start from basic. Can You try un-installing and installing the fastboot drivers? Because I suspect that's why You are not able to enter into fastboot mode.
Click to expand...
Click to collapse
I try it, but no way.. The same.
magntwo said:
I try it, but no way.. The same.
Click to expand...
Click to collapse
Can You try using a different PC/Laptop?
Mirhawk said:
Can You try using a different PC/Laptop?
Click to expand...
Click to collapse
I tryed my Vaio laptom and Dell laptom from my work. Both wrong... I'm completlly helplessly in this moment.
magntwo said:
I tryed my Vaio laptom and Dell laptom from my work. Both wrong... I'm completlly helplessly in this moment.
Click to expand...
Click to collapse
Just a sec, what combination do You use to go into bootloader? Power up+volume up? That is not what Yo do, You disconnect the phone from cable, and then turn off the phone. Then just press volume up, and connect the phone. No other button is needed to be pressed.
Mirhawk said:
Just a sec, what combination do You use to go into bootloader? Power up+volume up? That is not what Yo do, You disconnect the phone from cable, and then turn off the phone. Then just press volume up, and connect the phone. No other button is needed to be pressed.
Click to expand...
Click to collapse
Thank you. This is the way.. Now I'm in fastboot.... I gona flash kernel 2.8.0.1, then boot.img from your ROM and finally the ROM
magntwo said:
Thank you. This is the way.. Now I'm in fastboot.... I gona flash kernel 2.8.0.1, then boot.img from your ROM and finally the ROM
Click to expand...
Click to collapse
Finally! Follow the procedure here to flash a Kitkat/Lollipop ROM.
Mirhawk said:
Finally! Follow the procedure here to flash a Kitkat/Lollipop ROM.
Click to expand...
Click to collapse
Re: one more...
Quote:
Originally Posted by magntwo
Sorry, again...
As I wrote, I have in this moment folder with everything, nAOSP 5.0 b12, gapps-lp-20141109-signed, boot-carbon_3-11-14, beta SU v2.44, kernel v2.
As you know, two things, get this folder to phone and get fastboot, in this moment i'll be there, where I want to be
Ty!
Hi, can You please post it in a thread and tag Me? The messages kinda confuse Me!
.
Click to expand...
Click to collapse
Here we're... Thank you.
magntwo said:
Here we're... Thank you.
Click to expand...
Click to collapse
Apologies, might have missed out Your quote earlier. So You now have ROM and other stuff in the phone. What problem are You facing Now? Also I would recommend the new released version b14c with kernel from b14d of nAOSP.
Mirhawk said:
Apologies, might have missed out Your quote earlier. So You now have ROM and other stuff in the phone. What problem are You facing Now? Also I would recommend the new released version b14c with kernel from b14d of nAOSP.
Click to expand...
Click to collapse
simply... I get to bootloader as we wrote last. Then I flash kernel, and phone died. Now I can only charge or see a Sony logo. I can ONLY this now. no buttons helps, no different cable/slot/PC helps... I'M only in charging mod, after turn on only logo see. no TWRP, no bootloger.
magntwo said:
simply... I get to bootloader as we wrote last. Then I flash kernel, and phone died. Now I can only charge or see a Sony logo. I can ONLY this now. no buttons helps, no different cable/slot/PC helps... I'M only in charging mod, after turn on only logo see. no TWRP, no bootloger.
Click to expand...
Click to collapse
So You can't even go into bootloader now? That's weird and also makes this a bit complicated! Because You need to be able to go into bootloader mode to flash a new kernel which has recovery. Hope You are pressing only volume while connecting phone to PC. Drivers are fine as You were able to flash a kernel earlier. Which Kernel did You flash first? If You are able to go into bootloader, then flash this kernel via fastboot mode.
Mirhawk said:
So You can't even go into bootloader now? That's weird and also makes this a bit complicated! Because You need to be able to go into bootloader mode to flash a new kernel which has recovery. Hope You are pressing only volume while connecting phone to PC. Drivers are fine as You were able to flash a kernel earlier. Which Kernel did You flash first? If You are able to go into bootloader, then flash this kernel via fastboot mode.
Click to expand...
Click to collapse
Ok, I flash it. But I really can't into bootloader. If I hold vol button, conn cable only red, charging light... Now I really don't know what else.
magntwo said:
Ok, I flash it. But I really can't into bootloader. If I hold vol button, conn cable only red, charging light... Now I really don't know what else.
Click to expand...
Click to collapse
So You were able to flash the kernel I gave? Then You should be able to boot into CWM recovery. The Kernel logo will be of a Android bot.
I cant format,update,or enter revovery mode.Ive tried to turn off the phone and do that power button and volume up.Then i go press recovery,then the phone restarts and go to the same screen.Theres no error thingy showing.
Hi,
Reflash your recovery via fastboot command:
Code:
fastboot flash recovery [color="red"]recovery.img[/color]
Replace recovery.img with your prefered recovery's filename.
Sent from my GT-I9500
krasCGQ said:
Hi,
Reflash your recovery via fastboot command:
Code:
fastboot flash recovery [color="red"]recovery.img[/color]
Replace recovery.img with your prefered recovery's filename.
Sent from my GT-I9500
Click to expand...
Click to collapse
Fastboot undetected
haridzk said:
Fastboot undetected
Click to expand...
Click to collapse
Have you installed the USB driver?
Sent from my GT-I9500
krasCGQ said:
Have you installed the USB driver?
Sent from my GT-I9500
Click to expand...
Click to collapse
You mean using conputer?
New Z00A ZE551ML 3.15 firmware can't upgrade OTA manually
I have the same problem, although it is not likely the drivers.
When attempting to sideload the full firmware image, it errors out after a few seconds, stating that it cannot detect the device. I reboot the phone manually, then reboot bootloader from command prompt. try again and the same thing happens. First, I tried placing the file on an sd card, renaming it to MOFD_SDUPDATE but it failed after 25% and left me with the screen showing the "unplugged" icon. Now I cannot enter recovery at all. Attempted root, tethered, untethered, and no luck with any. I used an app before trying any of this to make sure it was not rooted or unlocked already. I'm running out of ideas. When I get home, I will try flashing just the droidboot.img as suggested in this thread: http://forum.xda-developers.com/zenfone2/help/unlock-bootloader-read-fix-t3138837.
Any other advice would be greatly appreciated. As I said my phone has
VERSION: WW-ASUS_Z00A-2.15.40.13 and failed to manually upgrade to 2.19.40
haridzk said:
You mean using conputer?
Click to expand...
Click to collapse
No, I mean USB Driver, for real. You can't do anything related to debugging without having the related drivers installed.
Sent from my GT-I9500
Quadro1972 said:
I have the same problem, although it is not likely the drivers.
When attempting to sideload the full firmware image, it errors out after a few seconds, stating that it cannot detect the device. I reboot the phone manually, then reboot bootloader from command prompt. try again and the same thing happens. First, I tried placing the file on an sd card, renaming it to MOFD_SDUPDATE but it failed after 25% and left me with the screen showing the "unplugged" icon. Now I cannot enter recovery at all. Attempted root, tethered, untethered, and no luck with any. I used an app before trying any of this to make sure it was not rooted or unlocked already. I'm running out of ideas. When I get home, I will try flashing just the droidboot.img as suggested in this thread: http://forum.xda-developers.com/zenfone2/help/unlock-bootloader-read-fix-t3138837.
Any other advice would be greatly appreciated. As I said my phone has
VERSION: WW-ASUS_Z00A-2.15.40.13 and failed to manually upgrade to 2.19.40
Click to expand...
Click to collapse
If you are getting the USB logo on your screen you're sh!t out of luck as it is a hard brick... You'll need to send back to ASUS to get rom put back on phone...
ultramag69 said:
If you are getting the USB logo on your screen you're sh!t out of luck as it is a hard brick... You'll need to send back to ASUS to get rom put back on phone...
Click to expand...
Click to collapse
I was very fortunate that it would still boot into the bootloader. As a result I was able to fix using these instructions and pre-rooted images, including an Asus recovery image:
http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
---------- Post added at 04:37 AM ---------- Previous post was at 04:33 AM ----------
Quadro1972 said:
I was very fortunate that it would still boot into the bootloader. As a result I was able to fix using these instructions and pre-rooted images, including an Asus recovery image:
http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
Click to expand...
Click to collapse
Also, if anyone else attempts this fix, download the images using Google Chrome or it will error out, fail checksum
Hey there, before anyone says it I know I'm a noob.
So I had oxygenos 4.0 with TWRP & root. I was stupid so I did an OTA update to 4.0.2, and my device just booted to TWRP and nothing happened. I tried to reboot to system but it kept going to TWRP. I searched the internet for an hour trying to find a resolution but couldn't find anything that worked. So I saw somewhere that I needed to install the original ROM (like 1.4GB), and that didn't work. Then I found somewhere that you need to put the original recovery on, so I did that using fastboot. Now when my phone boots up I just see the 1+ logo for like 15 sec and then it goes dark. I can't access recovery mode, but I still can access fastboot though. So I tried to reinstall TWRP, and still don't get anything (the black screen). So now I can't really do anything with my phone other than fastboot. I did create a backup in TWRP though, so it's probably still on my phone. What can I do to make it work again, without losing data (or at least not losing the backup)
Do you at least have fastboot? If so it'll be pretty easy, just download one of the modified TWRP recoveries, fastboot flash recovery yada yada, install or restore if it's the same problem I had. If no fastboot then you'll need to refer to the mega unbrick guide on the oneplus forums. Let me know if you can't find it or whatevs
Sent from my ONEPLUS A3000 using Tapatalk
AFschizoid said:
Do you at least have fastboot? If so it'll be pretty easy, just download one of the modified TWRP recoveries, fastboot flash recovery yada yada, install or restore if it's the same problem I had. If no fastboot then you'll need to refer to the mega unbrick guide on the oneplus forums. Let me know if you can't find it or whatevs
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
I do have fastboot, could you maybe give me some instructions? I don't really understand it
Download and rename to something easier to type in. https://forum.xda-developers.com/showthread.php?t=3402999
Move to same folder as fastboot and adb on computer.
Go into fastboot mode on phone (vol up while plugging phone into computer) and flash it by executing command
Fastboot flash recovery "recoveryname.img" no quotes and whatever you named your recovery to.
Then fastboot reboot and hold vol down. If you get into TWRP then you're golden to flash or restore. If not let me know
Sent from my ONEPLUS A3000 using Tapatalk
---------- Post added at 10:24 AM ---------- Previous post was at 10:19 AM ----------
Sounds like the same thing happened to me when I accidentally ota from cm13 to cm14., not paying attention to version numbers
Sent from my ONEPLUS A3000 using Tapatalk
AFschizoid said:
Download and rename to something easier to type in. https://forum.xda-developers.com/showthread.php?t=3402999
Move to same folder as fastboot and adb on computer.
Go into fastboot mode on phone (vol up while plugging phone into computer) and flash it by executing command
Fastboot flash recovery "recoveryname.img" no quotes and whatever you named your recovery to.
Then fastboot reboot and hold vol down. If you get into TWRP then you're golden to flash or restore. If not let me know
Sent from my ONEPLUS A3000 using Tapatalk
---------- Post added at 10:24 AM ---------- Previous post was at 10:19 AM ----------
Sounds like the same thing happened to me when I accidentally ota from cm13 to cm14., not paying attention to version numbers
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
Thank you so much!! My phone now fully works again, didn't even have to install anything from TWRP. Also my phone got updated
AFAIK; the oneplus3 is pretty unbrickable.
If you have fastboot, then the solution is usually pretty simple; you can get packages that flash via fastboot, or just flash TWRP recovery and work from there.
The most broken I got was flashing the modem / firmware package for OOS4 over a lineage os install, and it didn't even show a power indicator when charging and was entirely black screened. Even then there's a way to flash it in that state using the USB; this phone is pretty resilient.
Love this phone, wish it had better radio bands for US TMobile.
While flashing a stock rom on odin and it got interrupted, the error showed after rebooting. I have tried with kies but it only keeps on disconnecting when plugged in. It no longer allows me to enter into download mode.
I know that there are threads here regarding this issue, but there is no solution that worked for me.
Please help me I have tried every solution that I have found based on different samsung devices. Nothing works for me.
SM-T210
What device is it? On older devices like my TAB3 the error screen that you get that tells you to use kies to fix is download mode and Odin should recognize it. I've tried a few things that have left me in this situation.
RealWelder said:
What device is it? On older devices like my TAB3 the error screen that you get that tells you to use kies to fix is download mode and Odin should recognize it. I've tried a few things that have left me in this situation.
Click to expand...
Click to collapse
Thank you for replying. The model device name is SM-T210. Yes, Odin can still recognize it but no luck on kies. Did you fix yours?
Yes, i have a 210R. I've done this many times. What I always do use odin to flash @gr8nole's TWRP recovery. Then in TWRP either restore a backup or download my custom ROM and install it in TWRP. (I did my ROM off of 210 firmware so it would be compatible with both the 210 and the 210R)
---------- Post added at 01:23 PM ---------- Previous post was at 01:18 PM ----------
Here is my ROMs thread.
https://forum.xda-developers.com/showthread.php?t=3510449
The zip will flash a raw system image and boot image and should get you going. If not I can upload a twrp backup for you.
RealWelder said:
Yes, i have a 210R. I've done this many times. What I always do use odin to flash @gr8nole's TWRP recovery. Then in TWRP either restore a backup or download my custom ROM and install it in TWRP. (I did my ROM off of 210 firmware so it would be compatible with both the 210 and the 210R)
Click to expand...
Click to collapse
That's good to hear. Is this the one that you used? https://forum.xda-developers.com/showthread.php?t=2437219
So in flashing TWRP on Odin, do I need to uncheck the auto reboot and directly boot it to TWRP after flashing is done?
gamzybaby said:
That's good to hear. Is this the one that you used? https://forum.xda-developers.com/showthread.php?t=2437219
So in flashing TWRP on Odin, do I need to uncheck the auto reboot and directly boot it to TWRP after flashing is done?
Click to expand...
Click to collapse
Yep that's the one. Honestly, it should work either way...since no OS is installed if you try to boot it should automatically reboot to TWRP.
RealWelder said:
Yep that's the one. Honestly, it should work either way...since no OS is installed if you try to boot it should automatically reboot to TWRP.
Click to expand...
Click to collapse
Thank you so much for your help. I am currently downloading your ROM and will update you later. 300kbps download speed
gamzybaby said:
Thank you so much for your help. I am currently downloading your ROM and will update you later. 300kbps download speed
Click to expand...
Click to collapse
No problem. I'll be off and on throughout the day, if you need anything.
RealWelder said:
No problem. I'll be off and on throughout the day, if you need anything.
Click to expand...
Click to collapse
There's no problem flashing the TWRP but it still goes back to the problem. I'll show you a picture of the error.
gamzybaby said:
There's no problem flashing the TWRP but it still goes back to the problem. I'll show you a picture of the error.
Click to expand...
Click to collapse
Try holding vol+, home, and power until the tab3 splash comes up, then release power but keep the other 2 held in. It should boot to TWRP recovery.
RealWelder said:
Try holding vol+, home, and power until the tab3 splash comes up, then release power but keep the other 2 held in. It should boot to TWRP recovery.
Click to expand...
Click to collapse
I tried that but the tab3 splash doesn't come up. The one that I showed you will show.
gamzybaby said:
I tried that but the tab3 splash doesn't come up. The one that I showed you will show.
Click to expand...
Click to collapse
Do you have adb? If so, does the adb recognize the tab?
RealWelder said:
Do you have adb? If so, does the adb recognize the tab?
Click to expand...
Click to collapse
Sorry. I have no knowledge about Adb. But I'm willing to learn.
First let's go ahead and retry your stock firmware with Odin. If it is successful, you can reflash TWRP and then try my ROM or just run stock. If that doesn't work, then we'll try adb. After your odin flash, even if it fails, if the splash screen comes back, you can flash TWRP and then enter recovery.
RealWelder said:
First let's go ahead and retry your stock firmware with Odin. If it is successful, you can reflash TWRP and then try my ROM or just run stock. If that doesn't work, then we'll try adb. After your odin flash, even if it fails, if the splash screen comes back, you can flash TWRP and then enter recovery.
Click to expand...
Click to collapse
Just know that I can't go into download mode. Though Odin can still detect and flash. But I will try what you said and reflash the stock firmware i downloaded from sammobile.
RealWelder said:
First let's go ahead and retry your stock firmware with Odin. If it is successful, you can reflash TWRP and then try my ROM or just run stock. If that doesn't work, then we'll try adb. After your odin flash, even if it fails, if the splash screen comes back, you can flash TWRP and then enter recovery.
Click to expand...
Click to collapse
Theres no problem in flashing. Everything is fine but it still returns to the error.
Hmm. Is it the correct firmware? I'm gonna go ahead and prepare you a file that will have adb, fastboot, and a cmd window. I'll upload it shortly, just extract it into a folder on your desktop or somewhere where it is easy to get to.
---------- Post added at 03:14 PM ---------- Previous post was at 03:12 PM ----------
https://drive.google.com/file/d/0B3XczzpnAnvwcmdRb1YxRDlyR00/view?usp=drivesdk
Here is adb. After you extract it, open the cmd window and type adb devices with the tab plugged in. Hopefully it will show it.
RealWelder said:
Hmm. Is it the correct firmware? I'm gonna go ahead and prepare you a file that will have adb, fastboot, and a cmd window. I'll upload it shortly, just extract it into a folder on your desktop or somewhere where it is easy to get to.
Click to expand...
Click to collapse
Now that I don't know. But I searched for Sm-t210. Okay. Thank you so much for your time and effort.
gamzybaby said:
Now that I don't know. But I searched for Sm-t210. Okay. Thank you so much for your time and effort.
Click to expand...
Click to collapse
https://www.sammobile.com/firmwares/database/SM-T210/
If I remember right we want the UK version.
RealWelder said:
https://www.sammobile.com/firmwares/database/SM-T210/
If I remember right we want the UK version.
Click to expand...
Click to collapse
The adb that you gave me didnt work. It says it lacks .dll. So I downloaded this https://forum.xda-developers.com/showthread.php?t=2317790
I dont know if that works. and I tried adb devices.
https://drive.google.com/file/d/0B2KHvn5cNuHcOWFYXzM0c1RhWmc/view?usp=sharing