Related
I went to GooManager and downloaded the new version of TWRP. When I reboot to recovery my phone gets stuck on "swipe to unlock" and doesn't let me do anything but to restart my phone on fastboot. I can't flash any ROMs
Can someone please help me? Thanks in advanced. :crying:
chamo311 said:
I went to GooManager and downloaded the new version of TWRP. When I reboot to recovery my phone gets stuck on "swipe to unlock" and doesn't let me do anything but to restart my phone on fastboot. I can't flash any ROMs
Can someone please help me? Thanks in advanced. :crying:
Click to expand...
Click to collapse
did you install the correct version for the htc one sprint(wls)(spr)
Aldo101t said:
did you install the correct version for the htc one sprint(wls)(spr)
Click to expand...
Click to collapse
I was using the previous version (2.5) just fine and just went to GooManager and I assume that GooManager will download the right for me.
I opened GooManager and click on Menu then Install OpenRecoveryScript and then I manually rebooted to recovery once the download finished. And that's when I get stuck on "swipe to unlock"
Filename was "openrecovery-twrp-2.6.0.0-m7wls.img"
chamo311 said:
I was using the previous version (2.5) just fine and just went to GooManager and I assume that GooManager will download the right for me.
I opened GooManager and click on Menu then Install OpenRecoveryScript and then I manually rebooted to recovery once the download finished. And that's when I get stuck on "swipe to unlock"
Filename was "openrecovery-twrp-2.6.0.0-m7wls.img"
Click to expand...
Click to collapse
well, thats the right one, i would suggest that you manually download the file and install using adb fastboot.
I direct downloaded the file from their site and fast boot flashed after verifying MD5. There is definitely a problem with he recovery
Aldo101t said:
well, thats the right one, i would suggest that you manually download the file and install using adb fastboot.
Click to expand...
Click to collapse
Thank you sir! I am new to this so I am learning as I go. I read that these are the steps to follow to do an ADB Fastboot. Please correct me if I am wrong. Thanks again for your help.
1) Download the above file. Save it to the root of your /sdcard directly (internal memory only) and rename it to "twrp.img"
2) Turn off your device. Turn on the device and keep holding volume down until a menu shows up. Select fastboot from the menu list.
3) Plug the device into your computer. Run the following command via the command line:
fastboot flash recovery "twrp.img"
Bless.
Kraizk said:
I direct downloaded the file from their site and fast boot flashed after verifying MD5. There is definitely a problem with he recovery
Click to expand...
Click to collapse
That sucks! So should I do try adb fastboot or go back to the previous version (2.5)?
What sucks is that without 2.6 working properly, I won't be able to flash any ROM with the new android version (4.2)
Aldo101t said:
well, thats the right one, i would suggest that you manually download the file and install using adb fastboot.
Click to expand...
Click to collapse
Did the ADB and still the same problem. Should I go back to previous version of TWRP?
chamo311 said:
Thank you sir! I am new to this so I am learning as I go. I read that these are the steps to follow to do an ADB Fastboot. Please correct me if I am wrong. Thanks again for your help.
1) Download the above file. Save it to the root of your /sdcard directly (internal memory only) and rename it to "twrp.img"
2) Turn off your device. Turn on the device and keep holding volume down until a menu shows up. Select fastboot from the menu list.
3) Plug the device into your computer. Run the following command via the command line:
fastboot flash recovery "twrp.img"
Bless.
Click to expand...
Click to collapse
no, thats not right, don't put on your sdcard, download the file, put it in your directory where yoy have fastboot(on your computer. cd to that directory, open command prompt, (administrative) type adb reboot bootloader, when in bootloader (fastboot usb) type fastboot flash recovery(name of file).img
Aldo101t said:
no, thats not right, don't put on your sdcard, download the file, put it in your directory where yoy have fastboot(on your computer. cd to that directory, open command prompt, (administrative) type adb reboot bootloader, when in bootloader (fastboot usb) type fastboot flash recovery(name of file).img
Click to expand...
Click to collapse
It is broken, several users are reporting it in the original TWRP post as well
Kraizk said:
It is broken, several users are reporting it in the original TWRP post as well
Click to expand...
Click to collapse
Now that's some "good news" LOL! because I thought I screwed my phone and I wasn't going to be happy about it. I went back to v2.5 and everything works great!!
Thank you so much for all your help, guys!
Bless!!:good:
Kraizk said:
It is broken, several users are reporting it in the original TWRP post as well
Click to expand...
Click to collapse
that could be, thanks for the heads up
STUCK in TWRP Recovery
Aldo101t said:
that could be, thanks for the heads up
Click to expand...
Click to collapse
Completely stuck in Recovery. Can swipe to unlock screen but can not reboot even with Volume Down and Power button on Sprint HTC One. Just stuck. Phone is useless. Cant throw adb commands, nothing. WTF? What to do any ideas? Just watching the battery go down on the recovery screen...
Jason0071 said:
Completely stuck in Recovery. Can swipe to unlock screen but can not reboot even with Volume Down and Power button on Sprint HTC One. Just stuck. Phone is useless. Cant throw adb commands, nothing. WTF? What to do any ideas? Just watching the battery go down on the recovery screen...
Click to expand...
Click to collapse
just revert back to 2.5.0.0 and you are good to go
Jason0071 said:
Completely stuck in Recovery. Can swipe to unlock screen but can not reboot even with Volume Down and Power button on Sprint HTC One. Just stuck. Phone is useless. Cant throw adb commands, nothing. WTF? What to do any ideas? Just watching the battery go down on the recovery screen...
Click to expand...
Click to collapse
Did you just recently update your firmware to the new base? The reason I ask is because after I did I used the the firmware with the bootloader and recovery included. I had reflashed TWRP 2.5. Well I noticed that the method of holding down volume key and and power button would not work for me at all whether I was in the os, bootloader or recovery. So I flashed the Rom I was on again and it fixed it. So I am wondering this is what is happening to you. Maybe just let the phone lose charge then plug it in reboot to the os then into bootloader and flash the 2.5 TWRP recovery. Only thing I can think of your not bricked
Jason0071 said:
Completely stuck in Recovery. Can swipe to unlock screen but can not reboot even with Volume Down and Power button on Sprint HTC One. Just stuck. Phone is useless. Cant throw adb commands, nothing. WTF? What to do any ideas? Just watching the battery go down on the recovery screen...
Click to expand...
Click to collapse
Did you try holding the phone under a bright light then holding power and vol down to reboot. This works sometimes
Sent from my jacked HTC One!!
Aldo101t said:
just revert back to 2.5.0.0 and you are good to go
Click to expand...
Click to collapse
Given all the issues with 2.6 listed here, should I update from 2.5 to 2.6? Also, if TWRP says 2..5.0.0 at the top of the screen, how do I know this is the wls version?
mzel said:
Given all the issues with 2.6 listed here, should I update from 2.5 to 2.6? Also, if TWRP says 2..5.0.0 at the top of the screen, how do I know this is the wls version?
Click to expand...
Click to collapse
look at the zip file you download (openrecovery twrp-2.5.0.0-m7wls.img) m7wls tells you its for sprint.or m7spr whatever
there is a new version 2.6.0.1 but i don't know if it still has bugs or not, i'd stay at 2.5.0.0
Aldo101t said:
look at the zip file you download (openrecovery twrp-2.5.0.0-m7wls.img) m7wls tells you its for sprint.or m7spr whatever
there is a new version 2.6.0.1 but i don't know if it still has bugs or not, i'd stay at 2.5.0.0
Click to expand...
Click to collapse
I do not have a separate file. I think my TWRP came as part of some bigger ( root, recovery, permissions) package. I would think it was the Sprint version, but I keep having slight problems - those system apps try reboot after install, but in my case they do not. I have to boot manually, and after each recovery reboot I get a "reboot error notification". Can this be related?
mzel said:
I do not have a separate file. I think my TWRP came as part of some bigger ( root, recovery, permissions) package. I would think it was the Sprint version, but I keep having slight problems - those system apps try reboot after install, but in my case they do not. I have to boot manually, and after each recovery reboot I get a "reboot error notification". Can this be related?
Click to expand...
Click to collapse
that error is nothing don't worry about it, if you install a custom rom(make sure it's for sprint)that will go
Hey xda devs,
I just f ed up very bad. I was trying to flash a new recovery onto my Moto X and I was careless typing commands into the terminal I guess that serves me right.... So I was just rebooting my phone into the bootloader by typing adb reboot bootloader, so I had the "bootloader" sticking in my head there and because I did it a thousand times already I just proceed to flashing the new recovery but I type "fastboot flash bootloader xxxx.img"
So now, I have basically flashed a recovery.img into my bootloader partition
I still have adb and root access though.. is there any way I could save my bootloader partition? like adb dd it maybe ? I dont know
Did you try to manually reflash the correct image file? Or sbf back to stock?
Travisdroidx2 said:
Did you try to manually reflash the correct image file? Or sbf back to stock?
Click to expand...
Click to collapse
I'm not in fastboot anymore, I guess that's what I should have done when I realized my mistake. Because I was well aware of what I had just done.. but I rebooted the phone and now I guess there is no way to enter fastboot anymore.
Without fastboot how can I flash the correct img. file into the bootloader partition?
And what do you mean with sbf back to stock?
yabbandroid said:
I'm not in fastboot anymore, I guess that's what I should have done when I realized my mistake. Because I was well aware of what I had just done.. but I rebooted the phone and now I guess there is no way to enter fastboot anymore.
Without fastboot how can I flash the correct img. file into the bootloader partition?
And what do you mean with sbf back to stock?
Click to expand...
Click to collapse
Ever use RSD to flash a SBF? RSD will need to recognize your device though. There is stickies I am sure. I will find one to link you to.
Hold the power button until the phone is off. Now press and hold both the power button and volume down button for 10 seconds. Then release the power button, but keep the volume down button held. You should then be in fastboot mode.
AGISCI said:
Hold the power button until the phone is off. Now press and hold both the power button and volume down button for 10 seconds. Then release the power button, but keep the volume down button held. You should then be in fastboot mode.
Click to expand...
Click to collapse
The problem is that his bootloader (The mode that you have to get into to use fastboot) is no more. If you could find the block number you could do a dd command.
Vekhez said:
The problem is that his bootloader (The mode that you have to get into to use fastboot) is no more. If you could find the block number you could do a dd command.
Click to expand...
Click to collapse
Yep, good suggestion. It will only work if he has busybox installed (the 'stericson' variant, from the play store).
This command should work (from and ADB SHELL) assuming busybox is installed. First motoboot.img would need to be copied to the working directory on the sdcard where you are running the command from. Might need to be superuser as well.
dd if=motoboot.img of=/dev/block/platform/msm_sdcc.1/by-name/bootloader
Let me know if you have success. After running the command, if it shows success, you should be able to power off and successfully boot into bootloader (AP fastboot mode).
samwathegreat said:
Yep, good suggestion. It will only work if he has busybox installed (the 'stericson' variant, from the play store).
This command should work (from and ADB SHELL) assuming busybox is installed. First motoboot.img would need to be copied to the working directory on the sdcard where you are running the command from. Might need to be superuser as well.
dd if=motoboot.img of=/dev/block/platform/msm_sdcc.1/by-name/bootloader
Let me know if you have success. After running the command, if it shows success, you should be able to power off and successfully boot into bootloader (AP fastboot mode).
Click to expand...
Click to collapse
You're my hero, Sam. I'm gonna try that. I thought about dd but I don't understand this command so well ^^. Thank you for writing it down. I have root access so I can install busybox. I will try :good::good:
edit: did it as root! I think you just saved my phone! A thousand thanks to you, because I love my moto x !!
.img of=/dev/block/platform/msm_sdcc.1/by <
by-name/ by-num/
/block/platform/msm_sdcc.1/by-name/bootloader <
3209+0 records in
3209+0 records out
1643008 bytes transferred in 0.086 secs (19104744 bytes/sec)
Click to expand...
Click to collapse
succcess, success, after that I could succesfully reboot into fastboot. Only my recovery seems to be lost, but I will try to reflash this one now using fastboot which is back and working !!! (will be more careful in the future)
SO HAPPY. THank you !
yabbandroid said:
SO HAPPY. THank you !
Click to expand...
Click to collapse
Fantastic, bud!!! Yep, dd can come in very handy sometimes, and it's good to know some native linux commands (they save our butts every now and then...)
Very glad to hear my method worked for you. :good:
So im stuck with my nexus with no OS... after flashing pure shamu it booted to just a password box... I input my password and it said i had corrupt data. I hit reset... wiped phone... all files GONE... Now what do i do. I cant mount to put recovery on.... I cant do anyting with this phoen right now... anyone had this happen... If so what steps to remedy?
Sounds like you need to try and fastboot the original google files, nuke and repave....
flash the stock img then start again
Flashing stock as we speak... was hoping another optino.... but after years of doing this I kinda know better... live and learn
hell
Hi there, i'm new with Android and my problem is the same as yours on my Nexus 6.
after a failed root, i accidentally deleted all data. Now i'm without OS, boot locked, and the TWRP recovery has been deleted too (when i select recovery mode, it come back to the fastboot menu). i cannot use "fastboot oem unlock"
I don't know what i have to do . I really need help, i just want to restart from the beggining like official rom ...
sry for bad english.
asphalte7 said:
Hi there, i'm new with Android and my problem is the same as yours on my Nexus 6.
after a failed root, i accidentally deleted all data. Now i'm without OS, boot locked, and the TWRP recovery has been deleted too (when i select recovery mode, it come back to the fastboot menu). i cannot use "fastboot oem unlock"
I don't know what i have to do . I really need help, i just want to restart from the beggining like official rom ...
sry for bad english.
Click to expand...
Click to collapse
Try using these fastboot commands:
fastboot format userdata
fastboot format cache
Evolution_Freak said:
Try using these fastboot commands:
fastboot format userdata
fastboot format cache
Click to expand...
Click to collapse
done, what can i do after this ?
it says : created filestystem.... OKAY (with a lot of parameters)
asphalte7 said:
done, what can i do after this ?
it says : created filestystem.... OKAY (with a lot of parameters)
Click to expand...
Click to collapse
Should be able to boot twrp now.
but i have to unlock first ... my device is locked
asphalte7 said:
but i have to unlock first ... my device is locked
Click to expand...
Click to collapse
you cant unlock it without booting up and enabling allow oem unlocking in the developer options
asphalte7 said:
but i have to unlock first ... my device is locked
Click to expand...
Click to collapse
If you can boot to TWRP recovery, then you can ADB push a ROM to recovery and boot it.
Edit: Sorry, I missed the fact that TWRP had been deleted too.
asphalte7 said:
but i have to unlock first ... my device is locked
Click to expand...
Click to collapse
No, if you can boot to TWRP, as @rootSU said, you can move a ROM to internal and get up and running. Then you can go about unlocking.
Evolution_Freak said:
No, if you can boot to TWRP, as @rootSU said, you can move a ROM to internal and get up and running. Then you can go about unlocking.
Click to expand...
Click to collapse
and how can i boot twrp ? i'm like john snow, i know nothing
i only have a console, and a nexus - which cannot exit the "bios"
asphalte7 said:
and how can i boot twrp ? i'm like john snow, i know nothing
i only have a console, and a nexus - which cannot exit the "bios"
Click to expand...
Click to collapse
Power off the device. Once completely shut down, hold power and volume down until bootloader screen appears. Then use the volume keys to select recovery. Then push power to select.
from your original post, it says your not running twrp anymore. have you tried just letting the phone try to boot up? have you tried reflashing twrp to your phone via fastboot. id try, and if its successful, id push a rom to my phone then. if not, try flashing a factory img.
asphalte7 said:
and how can i boot twrp ? i'm like john snow, i know nothing
i only have a console, and a nexus - which cannot exit the "bios"
Click to expand...
Click to collapse
Evolution_Freak said:
Power off the device. Once completely shut down, hold power and volume down until bootloader screen appears. Then use the volume keys to select recovery. Then push power to select.
Click to expand...
Click to collapse
Or, if you are still in fastboot, issue this command > fastboot reboot recovery
Evolution_Freak said:
Power off the device. Once completely shut down, hold power and volume down until bootloader screen appears. Then use the volume keys to select recovery. Then push power to select.
Click to expand...
Click to collapse
as i said before, when twrp has been deleted, the Recovery mode is useless : when i hit it, it instantly return to bootloader screen
asphalte7 said:
as i said before, when twrp has been deleted, the Recovery mode is useless : when i hit it, it instantly return to bootloader screen
Click to expand...
Click to collapse
Then I'm afraid you may be stuck. A RMA may be in your future if no one else can offer a solution.
simms22 said:
from your original post, it says your not running twrp anymore. have you tried just letting the phone try to boot up? have you tried reflashing twrp to your phone via fastboot. id try, and if its successful, id push a rom to my phone then. if not, try flashing a factory img.
Click to expand...
Click to collapse
i left my phone during half an hour on the "Google" screen ....
i cannot flash twrp with fastboot because its locked..
or which command i have to type to install it ?
how can u flash a factory img ? i dowloaded the official 5.1 rom for nexus 6
asphalte7 said:
i left my phone during half an hour on the "Google" screen ....
i cannot flash twrp with fastboot because its locked..
or which command i have to type to install it ?
how can u flash a factory img ? i dowloaded the official 5.1 rom for nexus 6
Click to expand...
Click to collapse
flashing twrp..
fastboot flash recovery recoveryname.img
and flashing a factory img is done while the phone is in its bootloader. there are instruction how here on xda. but to be honest, i dont know if that will work. where did you buy your n6 from btw?
Hello All,
I have following issue and hope that - if possible - someone can help me. I also would like to mention that I am not an
Android expert but did read a lot of articles here in the forum to find out - or better - to get an idea how things are working.
My Z3C had a water damage. Now I only get fastboot mode. Display is broken and does not show anything. I installed Android-SDK
to get ADB and Fastboot. I installed also drivers.
When I connect the device while pushing the "volume down" button the device manager show me a somc flash device with the "volume up" button I see an Android ADB Interface device. However ADB is not working (no device found) only Fastboot does.
I flashed the "Z3c_DooMLoRD_AdvStkKernel_v01_FW-105.img" with Flashtool via fastboot in the hope that I can somehow access
to "sdcard" by blindly navigating to "mount storage" but nothing seem to work.
On my linux device I see that the usb device is recognized but that it is not an mtp device.
Before I continue to spent hours without really knowing what I am doing I thought that if there is a solution I would find it here.
So if there is any way to get access to my files / pics on the device I would be really glad if someone can let me know how or
at least bring me to the right direction.
Thanks a lot in advance!
Is your bootloader unlocked?
clouds5 said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
Thanks for your reply clouds5.
I followed the process to unlock the bootloader (got code from sony side and unlocked via fastboot with
"fastboot.exe -i 0x0fce oem unlock 0xKEY").
In Flashtool, when I click on the "BLU" Icon I get a window with with my IMEI and my Unlock Code and a
Relock Button. So I assume that the bootloader is unlocked.
If there is another way to verify please let me know and I will do.
no you cannot access files via fastboot only. but isn't it possible to flash custom recovery img file and boot into recovery and access files?
evildog1 said:
no you cannot access files via fastboot only. but isn't it possible to flash custom recovery img file and boot into recovery and access files?
Click to expand...
Click to collapse
I flashed "Z3c_DooMLoRD_AdvStkKernel_v01_FW-105.img" from doomlord.xperia-files.com/download.php?dlid=WjNjX0Rvb01Mb1JEX0FkdlN0a0tlcm5lbF92MDFfRlctMTA1 with
fastboot flash boot Z3c_DooMLoRD_AdvStkKernel_v01_FW-105.img
in the hope that it is possible but after rebooting it immediately goes into fastboot again. As I do not have
a screen I can not see anything - so I can not really confirm if it works or not - and in windows I do not see
anything either..
Galbasib said:
I flashed "Z3c_DooMLoRD_AdvStkKernel_v01_FW-105.img" from doomlord.xperia-files.com/download.php?dlid=WjNjX0Rvb01Mb1JEX0FkdlN0a0tlcm5lbF92MDFfRlctMTA1 with
fastboot flash boot Z3c_DooMLoRD_AdvStkKernel_v01_FW-105.img
in the hope that it is possible but after rebooting it immediately goes into fastboot again. As I do not have
a screen I can not see anything - so I can not really confirm if it works or not - and in windows I do not see
anything either..
Click to expand...
Click to collapse
hmm you better send it to repair.
evildog1 said:
hmm you better send it to repair.
Click to expand...
Click to collapse
That's unfortunately not an option as I had to disassemble the device
evildog1 said:
no you cannot access files via fastboot only. but isn't it possible to flash custom recovery img file and boot into recovery and access files?
Click to expand...
Click to collapse
Should sdcard appear automatically when booting into recovery or are there any specific steps I would need to complete?
I tried to install twrp on my OP3T but everytime i write "fastboot flash recovery trwp.img" it says "error: cannot load 'twrp.img'"
When I type "adb devices" my phone doesn't show up
I unlocked the bootloader
I activated USB debugging
I checked the OEM thing
I have put the twrp.img in the same Minimal ADB and Fastboot folder
What could it be?
Install correct driveres or use another usb port. Device have to be adressed via "fastboot devices" or "adb devices".
It's probably a typing error ..Rename the twrp in whatever you want and then type " fastboot flash recovery " whatever you want".img
Rename file
Did you rename the file? You need to rename it before flashing.
IT WORKED
Everytime I was putting the phone into bootloader mode, the phone was already plugged in. Then I tried to put the phone to bootloader mode and THEN plugging it in my pc... and it worked ^^
Strange, right?
cerfeda.albert said:
Everytime I was putting the phone into bootloader mode, the phone was already plugged in. Then I tried to put the phone to bootloader mode and THEN plugging it in my pc... and it worked ^^
Strange, right?
Click to expand...
Click to collapse
I also experienced this thing this morning.
A simple unplug, re-plug solved for me
Whenever i flash twrp through fastboot it just gets stuck on the twrp logo and doesn't go beyond it.
I've tried with 3.0.3.1, 3.0.3.0, 3.0.2.0 but still the same
can anyone help me with this?
Guiliang said:
Did you rename the file? You need to rename it before flashing.
Click to expand...
Click to collapse
no you don't.
Just type the first few letters and hit [tab]. Works on windows, linux, mac os and every other shell made within the last 40 years.
cerfeda.albert said:
I tried to install twrp on my OP3T but everytime i write "fastboot flash recovery trwp.img" it says "error: cannot load 'twrp.img'"
When I type "adb devices" my phone doesn't show up
I unlocked the bootloader
I activated USB debugging
I checked the OEM thing
I have put the twrp.img in the same Minimal ADB and Fastboot folder
What could it be?
Click to expand...
Click to collapse
The last parameter has to be the EXACT filename, that you are flashing, which is the TWRP image. It has to be in the same folder as your command prompt is or you need to include the path to the twrp file.
Try the last TWRP release, should work!
Would like to express that I am also having the exact same issue. Any version of TWRP simply fails to load and stays on the TWRP logo.
I am on OxygenOS 3.5.3.
Anybody know a solution? I am currently running with no recovery now and I am quite worried.
milanexplorer said:
Whenever i flash twrp through fastboot it just gets stuck on the twrp logo and doesn't go beyond it.
I've tried with 3.0.3.1, 3.0.3.0, 3.0.2.0 but still the same
can anyone help me with this?
Click to expand...
Click to collapse
originalnabisco said:
Would like to express that I am also having the exact same issue. Any version of TWRP simply fails to load and stays on the TWRP logo.
I am on OxygenOS 3.5.3.
Anybody know a solution? I am currently running with no recovery now and I am quite worried.
Click to expand...
Click to collapse
After installing the twrp and then you type ... Fastboot boot twrp.img. Probably you are stuck on twrp splash screen...
Try to boot manually.to twrp by pressing power button and volume down button...Then you should be able to boot on twrp....
originalnabisco said:
Would like to express that I am also having the exact same issue. Any version of TWRP simply fails to load and stays on the TWRP logo.
I am on OxygenOS 3.5.3.
Anybody know a solution? I am currently running with no recovery now and I am quite worried.
Click to expand...
Click to collapse
See this thread.
originalnabisco said:
Would like to express that I am also having the exact same issue. Any version of TWRP simply fails to load and stays on the TWRP logo.
I am on OxygenOS 3.5.3.
Anybody know a solution? I am currently running with no recovery now and I am quite worried.
Click to expand...
Click to collapse
Did you try to fastboot TWRP after flashing it?
What I mean is, after you enter the command "fastboot flash recovery twrp.img", proceed with "fastboot boot twrp.img" and it will boot. Doing this you prevent Oxygen OS from overwriting TWRP. You should be able to boot normally after doing that.
Don't be worried and try to boot into recovery as described, that should work, if it doesn't I wonder if you flashed the right version of TWRP.
Try and let us know.
jmazzamj said:
Did you try to fastboot TWRP after flashing it?
What I mean is, after you enter the command "fastboot flash recovery twrp.img", proceed with "fastboot boot twrp.img" and it will boot. Doing this you prevent Oxygen OS from overwriting TWRP. You should be able to boot normally after doing that.
Don't be worried and try to boot into recovery as described, that should work, if it doesn't I wonder if you flashed the right version of TWRP.
Try and let us know.
Click to expand...
Click to collapse
how long does it usually take? i've waited more than 10 minutes now.
Razoth said:
how long does it usually take? i've waited more than 10 minutes now.
Click to expand...
Click to collapse
Boot manually on it...
cultofluna said:
Boot manually on it...
Click to expand...
Click to collapse
apperantly i'm a retard, after i rebooted to recovery with hardware keys it shows the oneplus logo and i was like "this isnt twrp startup" and hardreset it... waiting boots into twrp just fine...
adb cannot locate file
cerfeda.albert said:
Everytime I was putting the phone into bootloader mode, the phone was already plugged in. Then I tried to put the phone to bootloader mode and THEN plugging it in my pc... and it worked ^^
Strange, right?
Click to expand...
Click to collapse
I'm having some difficulty getting past this step.
I've unlocked bootloader, enabled oem unlock and enabled usb debugging. I've added the PATH where my twrp.img file is located.
Whenever I input fastboot flash recovery twrp.img, it says error: cannot load twrp.img: no such file or directory.
I see the file in the correct location so i'm not sure what i'm doing wrong here.
Any ideas?
chizzwhizz said:
I'm having some difficulty getting past this step.
I've unlocked bootloader, enabled oem unlock and enabled usb debugging. I've added the PATH where my twrp.img file is located.
Whenever I input fastboot flash recovery twrp.img, it says error: cannot load twrp.img: no such file or directory.
I see the file in the correct location so i'm not sure what i'm doing wrong here.
Any ideas?
Click to expand...
Click to collapse
Reinstall your adb + fastboot drivers