Hello, I need help getting TWRP to 2.2.2.1 so that I can flash old ROMs in this case AltRoms although I tried COTR and everything flashes correctly but when I try to boot in it doesn't. Currently I have TWRP 2.5 which doesn't work with most old ROMs. Another thing is that I struggle a LOT with Fast boot so I don't know how to get it to write the image, and I also tried smirk it but only installs latest which isn't useful. Any help please?
Sent from my Amazon Kindle Fire using xda app-developers app
Ichigo said:
First, get fastboot.exe from somewhere. Then, cd to it using cmd.
Now, type:
Code:
fastboot getvar store
and press enter
Next, hold your power button until it's(the kindle) completely shut down.
After that, plug your kindle in via usb. Give it a few seconds, and it should put you into fastboot(cmd will tell you how long it took or something like that).
Now, type:
Code:
fastboot flash recovery c:/*directory*/*recovery name*.img
, and obviously you'll replace the directory and recovery name with the correct info.
Once that's successful, just type:
Code:
fastboot reboot
and you should be good to go.
Click to expand...
Click to collapse
Forgive me for my stupidity, but what is Fastboot.exe (I know it some sort Process or Executable File) and how do I get into cd or cmd?
Sent from my Amazon Kindle Fire using xda app-developers app
Also to make make things a little easier. Go into kfu and /tools/ and take all the fastboot and adb files out of there, and move them to root of /C:
Also you can move the recovery.img and move that to C: also
Just saves some time and typing.
Ichigo said:
First, get fastboot.exe from somewhere. Then, cd to it using cmd.
Now, type:
Code:
fastboot getvar store
and press enter
Next, hold your power button until it's(the kindle) completely shut down.
After that, plug your kindle in via usb. Give it a few seconds, and it should put you into fastboot(cmd will tell you how long it took or something like that).
Now, type:
Code:
fastboot flash recovery c:/*directory*/*recovery name*.img
, and obviously you'll replace the directory and recovery name with the correct info.
Once that's successful, just type:
Code:
fastboot reboot
and you should be good to go.
Click to expand...
Click to collapse
i am getting an error stating partition does not exist
Ichigo said:
Is this on the original KF?
Click to expand...
Click to collapse
yes.
---------- Post added 5th March 2015 at 12:00 AM ---------- Previous post was 4th March 2015 at 11:49 PM ----------
locotumbler said:
yes.
Click to expand...
Click to collapse
Ok, got it to load due to my mistyping and leaving the y off recoverY. but now when i attempt to enter recovery mode via bootloader 2.05 it just powers down the unit
locotumbler said:
yes.
---------- Post added 5th March 2015 at 12:00 AM ---------- Previous post was 4th March 2015 at 11:49 PM ----------
Ok, got it to load due to my mistyping and leaving the y off recoverY. but now when i attempt to enter recovery mode via bootloader 2.05 it just powers down the unit
Click to expand...
Click to collapse
Try powering off, connect to wall charger, let it charge for a while, then Retry recovery
Sent from my XT912 using Tapatalk
sd_shadow said:
Try powering off, connect to wall charger, let it charge for a while, then Retry recovery
Sent from my XT912 using Tapatalk
Click to expand...
Click to collapse
figured out the problem. with bootloader 2.05 if i flash 2.2.2.1 it has the power down issue. if i flash 2.7.0.1 (i didn't have any other twrp's to try) i do not have this issue. so it appears 2.2.2.1 is not compatible with bootloader 2.05.
The battery was at 96% when this issue was happening.
locotumbler said:
figured out the problem. with bootloader 2.05 if i flash 2.2.2.1 it has the power down issue. if i flash 2.7.0.1 (i didn't have any other twrp's to try) i do not have this issue. so it appears 2.2.2.1 is not compatible with bootloader 2.05.
The batter was at 96% when this issue was happening.
Click to expand...
Click to collapse
Yes you should be using OtterX twrp with 2.05
If you are trying to install non-otterx roms you should be using fff bootloader 1.4a
Sent from my XT912 using Tapatalk
sd_shadow said:
Yes you should be using OtterX twrp with 2.05
If you are trying to install non-otterx roms you should be using fff bootloader 1.4a
Sent from my XT912 using Tapatalk
Click to expand...
Click to collapse
I tried loading that through fastboot and it kept loading bootlaoder 2.05. Am I missing how to revert from bootloader 2.05 to 1.4a?
locotumbler said:
I tried loading that through fastboot and it kept loading bootlaoder 2.05. Am I missing how to revert from bootloader 2.05 to 1.4a?
Click to expand...
Click to collapse
Easiest way to change twrp and bootloader is to use the installable zips
Kindle Fire Flashable Recoveries TWRP/COTR/CWM[2014]
Sent from my XT912 using Tapatalk
sd_shadow said:
Easiest way to change twrp and bootloader is to use the installable zips
Kindle Fire Flashable Recoveries TWRP/COTR/CWM[2014]
Sent from my XT912 using Tapatalk
Click to expand...
Click to collapse
i will try this when i get home tonight.
thank you for your patience.
If it's a zip, it's for installing in twrp, for Flashing in bootloader files must be .img or .bin
Sent from my XT912 using Tapatalk
sd_shadow said:
If it's a zip, it's for installing in twrp, for Flashing in bootloader files must be .img or .bin
Sent from my XT912 using Tapatalk
Click to expand...
Click to collapse
it was a bin that i attempted to flash in fastboot. i will say this about 2.05 boot loader. if you don't just hit the power button quickly the menu disappears and you have to reboot. if you do a long push like in 1.4 the menu disappears.
locotumbler said:
it was a bin that i attempted to flash in fastboot. i will say this about 2.05 boot loader. if you don't just hit the power button quickly the menu disappears and you have to reboot. if you do a long push like in 1.4 the menu disappears.
Click to expand...
Click to collapse
yes if I'm flashing in bootloader, I usually have kindle powered, send commands, then power on kindle like in my Flashing TWRP in OtterX bootloader
Related
So in the rush to get CyanogenMod installed on my newly-S-Offed phone, I downloaded CWM from the appstore and started looking through the various devices to flash ClockWorkMod Recovery to. I selected the vanilla HTC One, not the verizon-specific model. I have not yet rebooted my phone yet, but I am worried that doing so will brick the phone since I technically don't have the right bootloader. Looking through CWM's list on my phone, there is not a verizon-specific model bootloader. There is one on Cyanogen's site (can't post the link due to XDA restrictions), but it appears to involve rebooting the phone. How should I go about safely flashing a good bootloader onto my phone?
ab2 said:
So in the rush to get CyanogenMod installed on my newly-S-Offed phone, I downloaded CWM from the appstore and started looking through the various devices to flash ClockWorkMod Recovery to. I selected the vanilla HTC One, not the verizon-specific model. I have not yet rebooted my phone yet, but I am worried that doing so will brick the phone since I technically don't have the right bootloader. Looking through CWM's list on my phone, there is not a verizon-specific model bootloader. There is one on Cyanogen's site (can't post the link due to XDA restrictions), but it appears to involve rebooting the phone. How should I go about safely flashing a good bootloader onto my phone?
Click to expand...
Click to collapse
CWM is a custom recovery, not bootloader. Download your choice of CWM or TWRP, reboot into the bootloader and use Fastboot to flash it.
NotATreoFan said:
CWM is a custom recovery, not bootloader. Download your choice of CWM or TWRP, reboot into the bootloader and use Fastboot to flash it.
Click to expand...
Click to collapse
I am referring to ROM Manager from the android app store. When you bring it up it asks you to flash your bootloader. The bootloader I selected was the one for the Vanilla HTC One.
I don't use ROM Manager, but I just installed it on my phone. The prompts all refer to recovery, and make no mention of bootloader. See below.
Sent from my HTC6500LVW using Tapatalk
ab2 said:
I am referring to ROM Manager from the android app store. When you bring it up it asks you to flash your bootloader. The bootloader I selected was the one for the Vanilla HTC One.
Click to expand...
Click to collapse
Its most likely referring to the recovery, not the bootloader; Assuming you're root, Rom Manager is there to flash custom ROMS and custom recoveries. I don't think you'll have bricked your phone if you installed a bad recovery, but I think your best bet would be install a compatible one manually.
SO pick a thread and follow the directions under installation:
http://forum.xda-developers.com/showthread.php?t=2416273 CWM
http://forum.xda-developers.com/showthread.php?t=2416431 TWRP
i'd pick twrp
Well my phone will reboot safely, which is good.
However, rebooting into fastboot or recovery just reboots into normal mode. Recovery will say the first time that it's going into recovery, but will reboot again and go into normal.
Thoughts?
Success! I just had to keep scrolling. there was a version in Rom Manager, all the way down at the bottom under "m7vzw." Flashing that did the trick.
Thanks for the help.
Cheers.
ab2 said:
Well my phone will reboot safely, which is good.
However, rebooting into fastboot or recovery just reboots into normal mode. Recovery will say the first time that it's going into recovery, but will reboot again and go into normal.
Thoughts?
Click to expand...
Click to collapse
The S-Off exploit removes stock recovery, so it will go nowhere until you flash CWM or TWRP. Fastboot will work regardless.
Sent from my HTC6500LVW using Tapatalk
ab2 said:
Success! I just had to keep scrolling. there was a version in Rom Manager, all the way down at the bottom under "m7vzw." Flashing that did the trick.
Thanks for the help.
Cheers.
Click to expand...
Click to collapse
All that said, I can now boot into recovery no problem, but typing "adb reboot fastboot" just reboots the phone normally. Any idea why that might be?
I've never used that command personally. I have Quick Boot (Reboot) from the market and use it for getting into recovery and fastboot from Android.
Sent from my HTC6500LVW using Tapatalk
ab2 said:
All that said, I can now boot into recovery no problem, but typing "adb reboot fastboot" just reboots the phone normally. Any idea why that might be?
Click to expand...
Click to collapse
Do you have fastboot unchecked under power settings? Phone doesn't totally reboot with that checked.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
ab2 said:
All that said, I can now boot into recovery no problem, but typing "adb reboot fastboot" just reboots the phone normally. Any idea why that might be?
Click to expand...
Click to collapse
adb reboot recovery = takes you to recovery
adb reboot bootloader = takes you to fastboot/booloader
I don't believe adb reboot fastboot is a command, so it just does adb reboot
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
Ok so I've had the fone a while now and finally unlocked the bootloader but as I'm knew to all this on lg can someone point me to a simple root method for marshmallow 20a I think if one exists or some other method of flashing TWRP onto my phone.
Thanks in advance
Sent from my GT-N8013 using Tapatalk
Found this is there any reason I can't use this method to install TWRP so I can then flash a cm13 based rom
http://www.droidviews.com/root-lg-g4-and-install-twrp-recovery/
Sent from my GT-N8013 using Tapatalk
I've unlock my bootloader, and successfully flashed TWRP like this video https://www.youtube.com/watch?v=O64GfQORCaE
But I can't get in recovery mode.
I'm trying to root like so http://forum.xda-developers.com/g4/development/kernel-t3232651 because I've already have 6.0 and I'm stuck....
Anyone can help please??
Edit: You don't actually need to use fastboot commands... it's just annoyingly counter intuitive.
Here's what works to boot into recovery after it's been flashed:
Turn phone off
Hold power and volume down
Release power for a half second when the LG logo appears then press and hold again
Unit will boot to white LG recovery asking if you want to wipe all data
Confirm yes twice
Unit will boot to TWRP recovery
-----------------
I had this problem earlier. You have to use fastboot commands to boot into it.
Change twrp-2.8.7.0-h815 to match your twrp file name
Code:
adb reboot bootloader
fastboot flash recovery twrp-2.8.7.0-h815.img
Fastboot boot twrp-2.8.7.0-h815.img
ajscott said:
I had this problem earlier. You have to use fastboot commands to boot into it.
Change twrp-2.8.7.0-h815 to match your twrp file name
Code:
adb reboot bootloader
fastboot flash recovery twrp-2.8.7.0-h815.img
Fastboot boot twrp-2.8.7.0-h815.img
Click to expand...
Click to collapse
Excellent!!!
So after that I flash the .zip or .img that's in the folder? (total new with rooting)
---------- Post added 25th January 2016 at 12:27 AM ---------- Previous post was 24th January 2016 at 11:56 PM ----------
rooted!
but it doesn't read my sdcard and bluetooth...
When I was installing twrp and CM13 on my G4, I tought that I can't access twrp either. When pressing vol down+power I got to the default screen with only option to factory reset. So I used the above command to access it. But I noticed, that if I go through that factory reset thingy, it will go to twrp without factory reset. So after you get to factory reset recovery, answer yes to the first question and then yes to the second one and you'll get to twrp.
So to get this straight
1 adb reboot bootloader
2 fastboot flash recovery.....
3 fastboot boot TWRP......
Then I can backup my current setup and then flash any Rom from there just like with my Samsung using TWRP after that then I can enter recovery via the power and volume down buttons?
Sent from my GT-N8013 using Tapatalk
Would I be better to flash a stock based rom with modem and bootloader first
Sent from my GT-N8013 using Tapatalk
eddyctweets said:
So to get this straight
1 adb reboot bootloader
2 fastboot flash recovery.....
3 fastboot boot TWRP......
Then I can backup my current setup and then flash any Rom from there just like with my Samsung using TWRP after that then I can enter recovery via the power and volume down buttons?
Sent from my GT-N8013 using Tapatalk
Click to expand...
Click to collapse
Even after installing CM13 I still got default recovery with vol down+power, but was able to enter twrp when rebooting from CM13 using something like twrp manager.
But as I said above, you get to twrp by going through "factory reset" from default recovery. It will not do factory reset.
I personally went with Genisys 3.6 ROM after trying CM13 for a few days. Picture quality suffered too much for my liking, and miracast support was also lost with CM13. With Genisys ROM everything works well.
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
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.