I've got a nexus one with a broken power button and a corrupt OS. It rarely successfully manages to boot. Since this is the case, I'm not able to turn on USB debugging to follow some of the tutorials here..
My next try was fastboot.. I downloaded these two files:
recovery-clockwork-5.0.2.0-passion.img
update-cm-7.1.0-N1-signed.zip
But it seems like I wont be able to flash a recovery file if I have "s-on" displayed on my hboot or fastboot screen..
How do I gain "s-off"? And is it possible to flash a stock rom via fastboot?
And yes, my phone's got stock gingerbread 2.3.4 rom.
HBOOT 0.35.0017
MICROP 0b15
Touch panel SYNT0103
Radio 5.08.00.04
Please help me with this matter as I have been trying to accomplish this task for over three months now..
Read Nexus One wiki, section "root", and section "recovery".
You don't need S-OFF to flash anything, if you unlock your bootloader. This is Nexus.
Boot into fastboot, plug into your PC, open command prompt wherever you have the fastboot command in Windows, most likely in android sdk under platform-tools, run "fastboot oem unlock" from command prompt, your bootloader is now unlocked. Attempt to flash your recovery now."
Sent from my Nexus One using XDA App
troby86 said:
Boot into fastboot, plug into your PC, open command prompt wherever you have the fastboot command in Windows, most likely in android sdk under platform-tools, run "fastboot oem unlock" from command prompt, your bootloader is now unlocked. Attempt to flash your recovery now."
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
My phone's power button is broken so I'm not able to select the recovery option
Jack_R1 said:
Read Nexus One wiki, section "root", and section "recovery".
You don't need S-OFF to flash anything, if you unlock your bootloader. This is Nexus.
Click to expand...
Click to collapse
It's already unlocked, as there is a small open lock displayed at the bottom of the boot screen.. and fastboot displayed it as already unlocked as well.. still.. i need a way to go to recovery without the power button
If you're in the bootloader - "fastboot reboot recovery".
If you're in the OS or while the OS is booting and ADB daemon is already running - "adb reboot recovery".
Jack_R1 said:
If you're in the bootloader - "fastboot reboot recovery".
If you're in the OS or while the OS is booting and ADB daemon is already running - "adb reboot recovery".
Click to expand...
Click to collapse
fastboot reboot recovery doesnt seem to boot the phone to recovery..
should the OS be completely booted up if I want to use the adb command? because it displays the error "error: device not found" when I try to "adb reboot recovery"
Might this be a problem with my computer? I checked and confirmed that the drivers for the phone are successfully installed...
knaphih said:
fastboot reboot recovery doesnt seem to boot the phone to recovery..
should the OS be completely booted up if I want to use the adb command? because it displays the error "error: device not found" when I try to "adb reboot recovery"
Might this be a problem with my computer? I checked and confirmed that the drivers for the phone are successfully installed...
Click to expand...
Click to collapse
Do you have the fastboot command on your computer?
troby86 said:
Do you have the fastboot command on your computer?
Click to expand...
Click to collapse
Yes, I can fastboot works ok because I can flash recovery image and reboot phone through fastboot. But since my power button is broken, I need to reboot to recovery through the computer...
knaphih said:
Yes, I can fastboot works ok because I can flash recovery image and reboot phone through fastboot. But since my power button is broken, I need to reboot to recovery through the computer...
Click to expand...
Click to collapse
First try: "adb reboot recovery" or "fastboot reboot-recovery"
If that doesn't work, give this a good read to see if it will help you:
http://wiki.cyanogenmod.com/index.php?title=Fastboot
If you are able to flash the recovery via fastboot, then I see no reason why you should not be able to reboot into recovery via fastboot or adb.
---------- Post added at 06:18 AM ---------- Previous post was at 06:11 AM ----------
knaphih said:
Yes, I can fastboot works ok because I can flash recovery image and reboot phone through fastboot. But since my power button is broken, I need to reboot to recovery through the computer...
Click to expand...
Click to collapse
And if none of that seems to work:
http://www.androidguys.com/2010/09/08/manage-nexus-broken-power-button/
OR
http://www.yamihoshi.nl/tech/tutorial-google-nexus-one-power-button-soft-fix
Both are the same, the second one is easier to follow.
OR
Put your recovery .img file into the same folder as your fastboot command, and run this: "fastboot boot recovery-clockwork-2.5.1.4-passion.img"
^^^^^USE YOUR RECOVERY NAME...NOT THE EXACT ONE ABOVE^^^^^
First try: "adb reboot recovery" or "fastboot reboot-recovery"
If that doesn't work, give this a good read to see if it will help you:
http://wiki.cyanogenmod.com/index.php?title=Fastboot
If you are able to flash the recovery via fastboot, then I see no reason why you should not be able to reboot into recovery via fastboot or adb.
Click to expand...
Click to collapse
I've attached an image showing proof that I've tried your method but still kept on failing to reboot to recovery..
When i try the command "fastboot boot recovery-clockwork-5.0.2.0-passion.img", the phone simply restarts and goes back to the 'X' boot screen and gets stuck there.
Could anyone please find me an genuine unedited gingerbread 2.3.4 ROM so I can PASSIMG it? ... I've downloaded several rooted ones.. but all seem to need the "android-info" file
fastboot reboot recovery
No "reboot-recovery".
And if you still get stuck on "X" when you reboot to recovery - it means that your recovery is corrupted/unusable too, and you need to PASSIMG everything.
Generally, booting the recovery through "fastboot boot" should have done enough - if your phone can't boot, it might probably be a HW problem preventing it from booting, and in that case - nothing will help.
fastboot reboot recovery
No "reboot-recovery".
And if you still get stuck on "X" when you reboot to recovery - it means that your recovery is corrupted/unusable too, and you need to PASSIMG everything.
Generally, booting the recovery through "fastboot boot" should have done enough - if your phone can't boot, it might probably be a HW problem preventing it from booting, and in that case - nothing will help.
Click to expand...
Click to collapse
I've attached an image trying out "fastboot reboot recovery" fastboot doesnt even seem to send that command to the phone..
Could anyone please provide me with a genuine stock gingerbread 2.3.4 or higher PASSIMG file? i've searched a lot but all i see are modded or rooted ones.
Yes, you're right. Fastboot can't reboot to recovery, only adb.
Oh well, in that case you're out of luck. You can't PASSIMG without power button, so if "fastboot boot some_boot_image" doesn't help - there's not much left to do.
You could always disassemble the phone and fix the power button...
knaphih said:
I've attached an image trying out "fastboot reboot recovery" fastboot doesnt even seem to send that command to the phone..
Could anyone please provide me with a genuine stock gingerbread 2.3.4 or higher PASSIMG file? i've searched a lot but all i see are modded or rooted ones.
Click to expand...
Click to collapse
Here's the 2.3.6 PASSIMG zip file link. Follow the directions. If you can get into BootLoader, your phone should automatically boot this if you have it named to PASSIMG.zip, and on the ROOT of your SD card:
http://forum.xda-developers.com/showthread.php?t=1312540
You guys are life savers troby86 and Jack_R1..
Yes, you're right. Fastboot can't reboot to recovery, only adb.
Oh well, in that case you're out of luck. You can't PASSIMG without power button, so if "fastboot boot some_boot_image" doesn't help - there's not much left to do.
You could always disassemble the phone and fix the power button...
Click to expand...
Click to collapse
I've seen an in depth video tutorial on youtube and attempted to repair the power button on my own.. however I failed since I cannot do such tiny soldering..
Here's the 2.3.6 PASSIMG zip file link. Follow the directions. If you can get into BootLoader, your phone should automatically boot this if you have it named to PASSIMG.zip, and on the ROOT of your SD card:
http://forum.xda-developers.com/show....php?t=1312540
Click to expand...
Click to collapse
Thankyou so much . This is what I've been searching for.. I'll let you guys know the outcome after I download and fix my phone (hopefully I will)
knaphih said:
You guys are life savers troby86 and Jack_R1..
I've seen an in depth video tutorial on youtube and attempted to repair the power button on my own.. however I failed since I cannot do such tiny soldering..
Thankyou so much . This is what I've been searching for.. I'll let you guys know the outcome after I download and fix my phone (hopefully I will)
Click to expand...
Click to collapse
Did the link I provided work? If not here is the actual file:
http://www.multiupload.com/KVY1MG1HGH
troby86 said:
Did the link I provided work? If not here is the actual file:
http://www.multiupload.com/KVY1MG1HGH
Click to expand...
Click to collapse
wow troby86
your still here
http://forum.xda-developers.com/showthread.php?t=1350288
atleast have the decency to refund my money you jackass
mally2 said:
wow troby86
your still here
http://forum.xda-developers.com/showthread.php?t=1350288
atleast have the decency to refund my money you jackass
Click to expand...
Click to collapse
I realize the situation you are in sucks, but please don't let your frustration carry over into these threads. We are here to help the original poster, not to try and get claims resolved and to sling mud. Try to keep this thread a helpful thread
Thanks
bassmadrigal said:
I realize the situation you are in sucks, but please don't let your frustration carry over into these threads. We are here to help the original poster, not to try and get claims resolved and to sling mud. Try to keep this thread a helpful thread
Thanks
Click to expand...
Click to collapse
well what do you know, he may just ask the OP to send him his nexus to get it fixed and you will never hear from him again.... just warning y'all thats all....
Related
I need some help here.
Power button broke on my n1 sometime ago. Recently I tried to flash a new kernel but forgot to wipe and it's basically stuck at the logo.
I'm able to get into the hboot screen via bqttry removal technique but cannot select any option because of bad power button.
Any ideas how to flash a new room? I tried connecting USB to pc but phone is not recognized while in hboot mode.
Any help would appreciated as it's my only phone
Thanks
Is your phone unlocked (ie do you have a lock symbol at the bottom of the 'X' screen)?
If so, I believe you can hold the trackball while booting up and that will take you into fastboot.
From there, I think you just issue the command
Code:
fastboot reboot recovery
If that doesn't work, you can just boot off a recovery file that is stored on your computer. Download either clockworkmod (I would recommend any v2.x as v3.x has some problems) or Amon_RA to a easy to type location on your computer. Then issue the command
Code:
fastboot boot recovery "c:\location to\recovery.img"
Ok, so I got it to boot in fastboot, but there's no option to
./fastboot-mac reboot recovery
Click to expand...
Click to collapse
also
./fastboot-mac boot recovery ../recovery-RA-passion-v2.2.1.img
Click to expand...
Click to collapse
I get:
cannot load 'recovery'
and I did this:
fastboot flash recovery /path/to/<recovery>.img
Click to expand...
Click to collapse
Is there a way reboot it into recovery?
Thanks!
Passimg back to stock, root, and try again...
jp2000 said:
I get:
cannot load 'recovery'
Click to expand...
Click to collapse
Is there any more into that error? Did you verify the md5sum to make sure the recovery isn't corrupted?
Also, if you have a recent nandroid backup saved on your sdcard, you can pull that off and flash the imgs directly
Code:
./fastboot-mac flash system /location/to/system.img
./fastboot-mac flash boot /location/to/boot.img
./fastboot-mac flash userdata /location/to/data.img
./fastboot-mac reboot
Where these files will be located depends on your recovery. I know with clockworkmod they are located in the backup folder under the clockworkmod folder on the sdcard. I don't know where they are stored for Amon_RA, but I would assume it would be similar.
Thanks to everyone for your suggestions.
Finally got my phone working!
Hi.
I have the same problem but whenever I try "fastboot flash" or "fastboot recovery" I end up with "FAILED (remote: signature verifiy fail)". I think this is due to that my bootloader is not unlocked, so I tried:
fastboot oem unlock
I got the option to unlock bootloader but I had to use my power button to select "unlock". My power button is broken so I don't know what to do.
Is there anything else I can do? Otherwise I think I have to open the phone and try to repair the button.
PASSIMG back to stock and root. Use "unroot/restore" section in Wiki.
If you're skilled enough with soldering tiny connectors - you can repair the button. There is a guide on this forum, showing the exact location to attach to.
Thanks. Now I can use the phone again!
Where is this repair guide...please let me know...
Sent from my Nexus One using xda premium
Hello,
ok so the problem is I tired to update to Jelly beam, i read about it here and i follow the steps. I make it to recovery and when i wanted to install files from zip it gave me error - Installation Aborted. I read somewhere that i have to update my Clockwork recovery so i tried and since then i can't do anything. When i press the power button i go to bootloader, from there if i chose Recovery the phone reboots and stucks on the colored X. When i type "adb devices" in cmd so i can try to apply some method list of devices is empty. I think it can be fixed if i make it to recovery but i can't. I looked a lot and maybe its because im mad or something but i can't find a solution, so if anyone can help me i will be very happy. I don't bother if im back to stock.
Use fastboot in bootloader, adb is only available in os and recovery
fastboot flash recovery recovery.img
Sent from my Nexus One using xda app-developers app
demkantor said:
Use fastboot in bootloader, adb is only available in os and recovery
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Tried that, stuck on : <waiting for device>
EDIT: I tried on my brother laptop and it worked but when i exucute the command, it says FAILED(remote: image update error)
EDIT2: Thanks i fixed it its working now. WOOHO!
when in bootloader have phone in fastboot mode, connect to pc via usb, make sure you have the proper drivers
HERE, THIS SHOULD HELP this is for a different phone so dont use the files but the concept is the same
After only four day of having this phone i managed to brick it. I would really like to know if its fixable or if i have a really nice paper weight. Im stuck on a boot loop, I was half way through flashing a rom when it suddenly shut off. Now it will not boot up. I can load into the bootlader but when i try to go into recovery it just sends me to fastboot. When i restart the phone i can see the old recovery (TWRP)for just an instant but then the screen goes completely black. If i plug in to my pc, nothing happens my computer detects it but it says y device is damaged nd it cant identify it. PLEASE HELP Am i out of luck?
Ive looked around but i couldnt seem to find anyone with the same problem as me (Sprint Variant)
Good news it's not bricked i would put this question on the rom thread someonethere sshould be able to help
There's a Sprint One forum as well, so hopefully you found a ROM on there!
http://forum.xda-developers.com/forumdisplay.php?f=2215
jaythenut said:
Good news it's not bricked i would put this question on the rom thread someonethere sshould be able to help
Click to expand...
Click to collapse
I really hope so because on a college budget i cant afford another phone D:
Seen this in a couple of other places. Seems certain recoveries are possibly becoming currupted during flashing a new ROM.
What you need to do it get back into fastbboot, and....
fastboot erase recovery
fastboot erase cache
the re-flash your recovery, boot into recovery, full wipe and reflash your ROM.
wnp_79 said:
Seen this in a couple of other places. Seems certain recoveries are possibly becoming currupted during flashing a new ROM.
What you need to do it get back into fastbboot, and....
fastboot erase recovery
fastboot erase cache
the re-flash your recovery, boot into recovery, full wipe and reflash your ROM.
Click to expand...
Click to collapse
When i go back into fastboot my only options are
-Bootloader
-Reboot
-Reboot bootleader
-Power down.
I appriciate the help!
i suggest you contact with HTC customservices to repair this problem.
Muquita said:
When i go back into fastboot my only options are
-Bootloader
-Reboot
-Reboot bootleader
-Power down.
I appriciate the help!
Click to expand...
Click to collapse
Can you flash recovery in fastboot ?
the safest thing to do is relock and use a matching RUU to get back to stock
Muquita said:
When i go back into fastboot my only options are
-Bootloader
-Reboot
-Reboot bootleader
-Power down.
I appriciate the help!
Click to expand...
Click to collapse
Your phone isn't bricked. There are two tools in this forum that can help you. One is made by hasoon2000(I think that's his user name), and the other is jwtool(I think). Use them to help to flash a recovery if you don't know how to use fastboot.
DynamicRam said:
Can you flash recovery in fastboot ?
the safest thing to do is relock and use a matching RUU to get back to stock
Click to expand...
Click to collapse
I cannot. My computer wont recognize it. I re-installed the driver and it Says my device malfunctioned.
Im giving up hope here.
Muquita said:
I cannot. My computer wont recognize it. I re-installed the driver and it Says my device malfunctioned.
Im giving up hope here.
Click to expand...
Click to collapse
dont give up
Sent from my HTC One
Muquita said:
I cannot. My computer wont recognize it. I re-installed the driver and it Says my device malfunctioned.
Im giving up hope here.
Click to expand...
Click to collapse
Edit: Just got done typing the stuff below and saw you can't connect to your device in fastboot? What do you mean by re-installed driver?
Don’t worry, as long as you can still get into hboot your phone is not completely bricked!
The fastboot commands I referred to need to be carried out on your laptop/pc when you phone is connected in fastboot.
Can I assume that as you have already unlocked bootloader and flashed a custom recovery you are already familiar with this and have your computer set up for fastboot commands?
(Apologies if you already know some of this, best not to skip parts out though!)
I’d start with downloading a fresh version of your chosen recovery, and place it in your fastboot directory ready. I’d also do the same with your ROM.
Like you have already done, boot into fastboot. Connect your phone to your pc, and the red text should change to ‘Fastboot USB’.
Then open up command prompt and get to your fastboot directory. (On Windows 7 you just find that folder in Explorer, hold shift and right-click, then choose ‘Open command window here’.)
To check your pc is talking to your phone, type ‘fastboot devices’. You should get a device serial number back if all is well.
Then type ‘fastboot erase cache’ and hit enter.
Then type ‘fastboot erase recovery’ and hit enter.
Then type ‘fastboot flash recovery [name of recovery].img’ and hit enter.
Then type ‘fastboot reboot recovery’ and hit enter.
Hope fully you should successfully boot into recovery now. Once in recovery, mount USB storage and copy over your fresh ROM. Choose to do a full wipe including cache and dalvik, then reflash your ROM.
Reboot.
Let me know how this goes.
cronus101 said:
Your phone isn't bricked. There are two tools in this forum that can help you. One is made by hasoon2000(I think that's his user name), and the other is jwtool(I think). Use them to help to flash a recovery if you don't know how to use fastboot.
Click to expand...
Click to collapse
I used the hasoon2000 to flash TWRP earlier, but my problems is that my pc wont recognize my phone. When i plug it in it and try to re-flash it it cant find it. When i check my devices it shows up as an android device but it says the drivers are damaged. if i could get it to read it i think i should be eable to reflash somethint.
I APPRICIATE ALL THIS HELP. i really am trying to be as specific as possible :fingers-crossed:
Hey so just a thought and experience I have had with all my HTC phones is when you see that quick glimpse of the TWRP recovery screen then it disappears to an empty black screen......you are sometimes still in a form of recovery but during your Rom flash something (i don't know for sure) changed and it doesn't show the screen only black. So with that long explanation out of the way....have you tried once the screen goes black the
"adb devices "
Mine whenever in this situation would return the output of serial number and recovery so then you can push or sideload the Rom and boot into the system at which point your fastboot drivers will finally be recogniZed.....
Hope this helps a little
Sent from my HTC EVARE_UL using xda app-developers app
Muquita said:
I used the hasoon2000 to flash TWRP earlier, but my problems is that my pc wont recognize my phone. When i plug it in it and try to re-flash it it cant find it. When i check my devices it shows up as an android device but it says the drivers are damaged. if i could get it to read it i think i should be eable to reflash somethint.
I APPRICIATE ALL THIS HELP. i really am trying to be as specific as possible :fingers-crossed:
Click to expand...
Click to collapse
I'd say the next step is to re-install your drivers in the SDK. Open up your Android SDK and reinstall them. In Windows Device Manager, find your connected device (probably now with an exclamation mark on it) and right click on it and select 'Update Driver'.
(Assuming you are using Windows 7 here?)
http://developer.android.com/tools/extras/oem-usb.html
Muquita said:
When i go back into fastboot my only options are
-Bootloader
-Reboot
-Reboot bootleader
-Power down.
I appriciate the help!
Click to expand...
Click to collapse
when you are in fastboot, connect your phone using the usb cable, and when you see "fastboot" written in red turned into "fastboot usb" or something like this, do the commands below using cmd window of course :
1) fastboot erase recovery
2) fastboot erase cache
3) fastboot flash recovery recoveryname.img
4) fastboot erase cache
Let us know when you fix it
Good Luck
wnp_79 said:
I'd say the next step is to re-install your drivers in the SDK. Open up your Android SDK and reinstall them. In Windows Device Manager, find your connected device (probably now with an exclamation mark on it) and right click on it and select 'Update Driver'.
(Assuming you are using Windows 7 here?)
http://developer.android.com/tools/extras/oem-usb.html
Click to expand...
Click to collapse
(Win8 but the procces is identical.) All my drivers are up to date. Still no love.
On the dev forum is a thread that includes all the latest drivers (including an app to remove older drivers.)
Find that thread, download the drivers and bmp and driver removal tool. Remove drivers with tool, install the new drivers, reboot, connect phone and see if 'adb devices' finds anything.
Also make sure you're using the latest adb.
Sent from my HTC One using xda app-developers app
thneed said:
Hey so just a thought and experience I have had with all my HTC phones is when you see that quick glimpse of the TWRP recovery screen then it disappears to an empty black screen......you are sometimes still in a form of recovery but during your Rom flash something (i don't know for sure) changed and it doesn't show the screen only black. So with that long explanation out of the way....have you tried once the screen goes black the
"adb devices "
Mine whenever in this situation would return the output of serial number and recovery so then you can push or sideload the Rom and boot into the system at which point your fastboot drivers will finally be recogniZed.....
Hope this helps a little
Sent from my HTC EVARE_UL using xda app-developers app
Click to expand...
Click to collapse
This actually sounds really similar to my situation.. Would you care to be a little more specific on the procedure? noob here.
Tabtoub said:
when you are in fastboot, connect your phone using the usb cable, and when you see "fastboot" written in red turned into "fastboot usb" or something like this, do the commands below using cmd window of course :
1) fastboot erase recovery
2) fastboot erase cache
3) fastboot flash recovery recoveryname.img
4) fastboot erase cache
Let us know when you fix it
Good Luck
Click to expand...
Click to collapse
My pc will not recognize my phone. The drivers are up to date but when i plug it in it says something malfunctioned ?
Hey guys, I need some major help!
I was trying to update my phone earlier today, when I flashed Android Revolution HD 40.3 something very bad happened!
For some reason the ROM did not install properly, and I can't get back into recovery. I was using TWRP and the loading screen comes up for it, but it never fully launches.
I can get into the bootloader, and I tried using the Toolkit under fastboot. It seems like my phone is detected, but when I try and flash anything it doesnt work. Ive flashed both TWRP and clockword. They seem to flash because it will show the loading screen of either one, but it never actually enters the recovery. What should I do?
My phone is S-ON, I am not sure if that is what caused the problem/is what is keeping this an issue.
Thanks for your help
SMGkrome said:
Hey guys, I need some major help!
I was trying to update my phone earlier today, when I flashed Android Revolution HD 40.3 something very bad happened!
For some reason the ROM did not install properly, and I can't get back into recovery. I was using TWRP and the loading screen comes up for it, but it never fully launches.
I can get into the bootloader, and I tried using the Toolkit under fastboot. It seems like my phone is detected, but when I try and flash anything it doesnt work. Ive flashed both TWRP and clockword. They seem to flash because it will show the loading screen of either one, but it never actually enters the recovery. What should I do?
My phone is S-ON, I am not sure if that is what caused the problem/is what is keeping this an issue.
Thanks for your help
Click to expand...
Click to collapse
Does the phone just reboot before it enters recovery? I would try manually flashing a custom recovery image. Here is a link to the exact image I used.
http://forum.xda-developers.com/showthread.php?t=2173863
It's very straightforward once you have fast boot setup. Don't worry I've been in your situation myself!
JasSingh93 said:
Does the phone just reboot before it enters recovery? I would try manually flashing a custom recovery image. Here is a link to the exact image I used.
http://forum.xda-developers.com/showthread.php?t=2173863
It's very straightforward once you have fast boot setup. Don't worry I've been in your situation myself!
Click to expand...
Click to collapse
Thanks for the response!
Was your phone S-ON?? It seems that there are fixes when it is S-OFF, but not S-ON
SMGkrome said:
Thanks for the response!
Was your phone S-ON?? It seems that there are fixes when it is S-OFF, but not S-ON
Click to expand...
Click to collapse
My phone was S-ON at the time, I recently gained S-OFF. You should still be able to flash a new recovery with S-ON. S-OFF is usually only needed for flashing new radios or firmwares.
JasSingh93 said:
My phone was S-ON at the time, I recently gained S-OFF. You should still be able to flash a new recovery with S-ON. S-OFF is usually only needed for flashing new radios or firmwares.
Click to expand...
Click to collapse
How did you flash the recovery? Like I've said, I tried flashing a new recovery via the Toolkit. They do seem to flash, but I cant access the recovery. I'm not sure if my bootloader was relocked or what, but it doesn't go past the intro screen for TWRP or Clockwork
SMGkrome said:
How did you flash the recovery? Like I've said, I tried flashing a new recovery via the Toolkit. They do seem to flash, but I cant access the recovery. I'm not sure if my bootloader was relocked or what, but it doesn't go past the intro screen for TWRP or Clockwork
Click to expand...
Click to collapse
It could be possible that the toolkit is installing an incorrect version maybe? Switch off your phone. Once off hold vol - and power the phone on. This should load up HBOOT and tell you the boot loader status.
This is how I flashed recovery. I entered fastboot and used the commands from that link to flash a new recovery image. Have you used fastboot commands before?
JasSingh93 said:
It could be possible that the toolkit is installing an incorrect version maybe? Switch off your phone. Once off hold vol - and power the phone on. This should load up HBOOT and tell you the boot loader status.
This is how I flashed recovery. I entered fastboot and used the commands from that link to flash a new recovery image. Have you used fastboot commands before?
Click to expand...
Click to collapse
To be honest, I'm pretty new to the fastboot commands. I usually follow guides to root, and flashing ROMs is pretty straightforward.
SMGkrome said:
To be honest, I'm pretty new to the fastboot commands. I usually follow guides to root, and flashing ROMs is pretty straightforward.
Click to expand...
Click to collapse
If you have fastboot setup and working, just boot the phone into fastboot mode and use the commands in that link I gave you.
From fastboot. Use command "fastboot erase cache"
From fastboot. Use command "fastboot flash recovery recovery.img"
Then simply highlight "recovery", tap the power button and the phone should load up clockwordmod recovery.
Easy
JasSingh93 said:
If you have fastboot setup and working, just boot the phone into fastboot mode and use the commands in that link I gave you.
From fastboot. Use command "fastboot erase cache"
From fastboot. Use command "fastboot flash recovery recovery.img"
Then simply highlight "recovery", tap the power button and the phone should load up clockwordmod recovery.
Easy
Click to expand...
Click to collapse
Is fastboot mode just when you hold power and volume down then select fastboot?
SMGkrome said:
Is fastboot mode just when you hold power and volume down then select fastboot?
Click to expand...
Click to collapse
It is
SMGkrome said:
Is fastboot mode just when you hold power and volume down then select fastboot?
Click to expand...
Click to collapse
This is going to make me sound incompetent, but to use fastboot commands I just need to install the ADT Bundle from google for developers?
SMGkrome said:
This is going to make me sound incompetent, but to use fastboot commands I just need to install the ADT Bundle from google for developers?
Click to expand...
Click to collapse
It doesn't make you sound incompetent at all! Yes its just the bundle, then the drivers should be installed with that too. If you're not 100% sure there are plenty of guides online on how to setup fastboot.
For example: http://techbeasts.com/2013/08/26/how-to-install-adb-fastboot-drivers-on-your-windows-pc-guide/
Or if you're lazy like me you can use this: http://forum.xda-developers.com/showthread.php?p=42407269
JasSingh93 said:
It doesn't make you sound incompetent at all! Yes its just the bundle, then the drivers should be installed with that too. If you're not 100% sure there are plenty of guides online on how to setup fastboot.
For example: http://techbeasts.com/2013/08/26/how-to-install-adb-fastboot-drivers-on-your-windows-pc-guide/
Or if you're lazy like me you can use this: http://forum.xda-developers.com/showthread.php?p=42407269
Click to expand...
Click to collapse
Ah, no dice. I followed all the steps, everything seemed to work (thanks for the guide). It flashed the recovery okay. When I restarted the phone, it goes into recovery, shows clockwork mod recovery, version XX and then proceeds to try and boot into my regular system
SMGkrome said:
Ah, no dice. I followed all the steps, everything seemed to work (thanks for the guide). It flashed the recovery okay. When I restarted the phone, it goes into recovery, shows clockwork mod recovery, version XX and then proceeds to try and boot into my regular system
Click to expand...
Click to collapse
Hm, that's really strange. So recovery tried to boot, but the phone restarts and tried to boot normally?
Did you try running the command "fastboot erase cache" in fastboot mode?
JasSingh93 said:
Hm, that's really strange. So recovery tried to boot, but the phone restarts and tried to boot normally?
Did you try running the command "fastboot erase cache" in fastboot mode?
Click to expand...
Click to collapse
Yeah, basically it goes back and forth between trying to get into recovery and try to boot normally but can't boot into either
SMGkrome said:
Yeah, basically it goes back and forth between trying to get into recovery and try to boot normally but can't boot into either
Click to expand...
Click to collapse
OK so new recovery flashed, I would try running "fastboot erase cache". This commonly fixed issues with recoveries failing to boot.
JasSingh93 said:
OK so new recovery flashed, I would try running "fastboot erase cache". This commonly fixed issues with recoveries failing to boot.
Click to expand...
Click to collapse
So I owe you a beer! I guess I must have forgotten that command. Worked perfectly, phone is all good now!
Thanks for all the help
SMGkrome said:
So I owe you a beer! I guess I must have forgotten that command. Worked perfectly, phone is all good now!
Thanks for all the help
Click to expand...
Click to collapse
No worries! Glad you got it working. Happy to help!
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