Related
Hi! Sorry about this rude way but I am in an emergency situation.
I have a ZTE RACER with Android 2.2.2 (official ZTE Frimware) which it keeps rebooting at the splash screen.
Before that, I did a root using SuperOneClick 2.3.3 by Shortfuse. After following the instructions (USB debug, plug-in, root) I've rebooted the phone normally (NOT with adb), and when it got after the ZTE Logo (the first one, not the splash screen and not the Android logo). The animation goes a little and freezes for a few seconds, then restarts automaticly (but not entirely, just repeats the splash screen) and reboot. Rance and repeat! I tried to unroot, but the app hangs, restarting with adb and nothing happens. adb restart command doesn't help that much. What should I do to fix it?
Additional info:
Phone recives adb commands normally.
Possibly Superuser app was leftover before unrooting and rooting again (yes I already did root, but superuser stoped working properly afer app and su files update)
Can't go to FTM Mode, ROM Manager gave me a broken CWM.
Unsure If I can install CWM manually since SD doesn't seem to get mounted.
Phone Info:
ZTE-RACER
Android 2.2.2 (FROYO_P2XXGV_V1.0.0_B2)
CWM 5.0.x (Installed with ROM Manager. Broken.)
Carrier: GR COSMOTE (that's unknown carrier for you.)
Thanks for any help.
P.S.: Does anyone here is greek and has a ZTE RACER with the official 2.2 upgrade? I need the FTM Mode.
From what you have said, it seems like you are in a soft brick not a hard one. This means that there is chance of recovery but you have to be very careful.
You weren't rude so don't worry bout that.
You may want to try a hard reset.
Now that we have identified the problem, you have the ability to try and find it yourself at least.
It is possible to manually flash the generic default 2.2 and this will restore your device.
or
turn off your phone and then press power button and volume up button.Programing will open and there is a option of reset and restore.By using volume button go to reset and restore option and then press power button and home key programing will start and your phone will reset.
Hit thanks if you found this useful.
Deftone said:
It is possible to manually flash the generic default 2.2 and this will restore your device.
or
turn off your phone and then press power button and volume up button.Programing will open and there is a option of reset and restore.By using volume button go to reset and restore option and then press power button and home key programing will start and your phone will reset.
Hit thanks if you found this useful.
Click to expand...
Click to collapse
For the first one, I don't know how since the only way I had was to reflash it with the 1-Click Update (I did that on my ZTE MF636 3G Modem).
About the second, you mean that I must use the adb command, or I just hold it down without connecting it (I am newbie to the Android), but thanks for the help. I'll keep you posted for the results.
(NOTE: 1-click update is the offline frimware updater made by ZTE.)
if the logo appears look for a solution, if nothing happens buy a new one because is a full brick
rivas1981 said:
if the logo appears look for a solution, if nothing happens buy a new one because is a full brick
Click to expand...
Click to collapse
Logo appears but... I still don't get it.
Was that for CWM? Or for the phone?
CWM is broken by the ROM Manager. After installing, I tried to get in, but it got frozen to the Android logo + the red led is on. (Temporal brick).
Should I flash a working CWM to the phone?
Anyone?
If there is a working CWM recovery .img file for your device, flash that using fastboot.
-- Sent from my TouchPad using Communities
post-mortem said:
If there is a working CWM recovery .img file for your device, flash that using fastboot.
-- Sent from my TouchPad using Communities
Click to expand...
Click to collapse
a) I am not sure if it works but for sure it doesn't come from ROM Manager.
b)Where do I find fastboot and what's the command?
Anyone, please?
I think you get it when you install the SDK, along with ADB. You put your phone into fastboot mode, plug the USB into your computer, and use fastboot flash_image to flash the .img file to your device's recovery partition.
If you can boot your device into fastboot mode, search for "Android Flash Recovery" by Bill.Weckel (Windows only). That'll be the easiest way.
-- Sent from my TouchPad using Communities
post-mortem said:
I think you get it when you install the SDK, along with ADB. You put your phone into fastboot mode, plug the USB into your computer, and use fastboot flash_image to flash the .img file to your device's recovery partition.
If you can boot your device into fastboot mode, search for "Android Flash Recovery" by Bill.Weckel (Windows only). That'll be the easiest way.
-- Sent from my TouchPad using Communities
Click to expand...
Click to collapse
This command doesn't work. Is it fastboot flash recovery [image_file]?
Will somebody please help me out!
Here is the thread for Android Flash Recovery:
http://forum.xda-developers.com/showthread.php?t=1827723
Doesn't work! It does detect it, but it can't flash it (on normal boot only. On recovery/bootloader it just getting bricked). Any other options? Or I have to send it for reflashing?
and nothing I do get's it to go away. I have spent the better part of 8 hours screwing around with it and can't figure it out. Here is what I know:
If you just try and turn on the phone sans power cord, it won't turn on. If you plug it it, it displays the LG screen and stops. If you hold down the power, down, home keys, then power cable, it will boot into fastboot and take fastboot commands. I have followed the procedure to flash a recovery image listed here in the forums to no avail. It will erase the recovery, flash it, but will not reboot on the reboot command. When I disconnect the data cable and reconnect, it will go right back to the LG screen. I have tried KDZ and downloaded the original rom via the Original LG Firmware tool. It will communicate with the phone if I put the phone in emergency mode via the simultaneous back and volume down button while connecting the power cable. KDZ will start to install the rom but after some time, the phone spontaneously reboots and then hangs at the LG screen. Upon reboot back into emergency, the KDZ routine finishes and says it's finished but when I reboot it goes right back to the LG screen. I have tried the kdz tool in diag and emergency modes while shaking the phone. I have tried the software update tool but it says it cant communicate properly with the phone. I don't know what else to try.
Any suggestions?
Thanks a bunch!
After you succesfully flashed the recovery using fastboot, do you try to boot into recovery manually?
If that doesn't works you could try this http://forum.xda-developers.com/showthread.php?t=1827723
gabo_lope said:
After you succesfully flashed the recovery using fastboot, do you try to boot into recovery manually?
If that doesn't works you could try this http://forum.xda-developers.com/showthread.php?t=1827723
Click to expand...
Click to collapse
By recovery do you mean clockworkmod? If so, the phone is stock, unrooted so no, if not, what do you mean and how do I do that?
Thanks a bunch!
PS, If I follow the method I found for entering recovery it goes right back to fastboot.
PS Part two, the app you link did the same thing as I did manually and did not help.... thanks anyway...
J
Check if this thread helps...
forum.xda-developers.com/showthread.php?t=1827723
ROM - Paranoid Android By ByteCode.
Sent via XDA App.
"Hit ThanX if i helped u by anyway !"
jackler1 said:
By recovery do you mean clockworkmod? If so, the phone is stock, unrooted so .......
Click to expand...
Click to collapse
Hey jackler1, it will not allow you to install any custom recovery if your phone is still not rooted as you mentioned.
Hence using the Home+Vol-+power combo takes you to the fast boot screen.
1st thing you need to do is to root the phone, for it to allow installation of a custom recovery.
Many root tools are available for the P500 - eg Gingerbreak, Super one click.
try this for rooting - http://forum.xda-developers.com/showthread.php?t=1832485
pmvyas said:
Hey jackler1, it will not allow you to install any custom recovery if your phone is still not rooted as you mentioned.
Hence using the Home+Vol-+power combo takes you to the fast boot screen.
1st thing you need to do is to root the phone, for it to allow installation of a custom recovery.
Many root tools are available for the P500 - eg Gingerbreak, Super one click.
try this for rooting - http://forum.xda-developers.com/showthread.php?t=1832485
Click to expand...
Click to collapse
Hey,
I am unable to get into any other mode but fastboot or emercency mode so I have no idea how to root the thing. The thread you mention is of no help, thanks anyway and will take suggestions if you have them
DpAk007 said:
Check if this thread helps...
forum.xda-developers.com/showthread.php?t=1827723
ROM - Paranoid Android By ByteCode.
Sent via XDA App.
"Hit ThanX if i helped u by anyway !"
Click to expand...
Click to collapse
I had already attempted this method as well to no avail, thanks anyway!
Hi,
I have put more than 12 hours of my time, before creating this thread. I have tried things, but still struck, so thought to post it in a new thread. Thanks for all your time.
Currently struck in,
fastboot mode started udc_start()
I tried, fastboot erase recovery -> fastboot flash recovery recovery.img -> fastboot reboot (successfully). But it still struck at same place after reboot.
I tried with different recovery images, but still the same observation. I tried to boot by key combination (volume down+home+power), still same observation.
Earlier, I installed ROM manager through google play and installed CWM recovery, version 5.xxx (which I feel now is a mistake), as I tried to install CM11 from MukilSoni, which needs CWM version 6.xx +. I am able to go into recovery and select CM11 image through CWM and proceed with install steps. But, after initial selection in CWM (like app install, etc) it rebooted and went into fastboot mode.I checked the log, it ended with some return error 7.
Then, I tried to Google and check how to recover from fastboot mode, but all failed. I didnt tried KDZ method, but thought to hear from you guys before making it more messy.
Glad, if I get any help and appreciate it.
Thanks for reading it and your time.
Regards,
Ganesh
Hi,
I have put more than 12 hours of my time, before creating this thread. I have tried things, but still struck, so thought to post it in a new thread. Thanks for all your time.
Currently struck in,
fastboot mode started udc_start()
I tried, fastboot erase recovery -> fastboot flash recovery recovery.img -> fastboot reboot (successfully). But it still struck at same place after reboot.
I tried with different recovery images, but still the same observation. I tried to boot by key combination (volume down+home+power), still same observation.
Earlier, I installed ROM manager through google play and installed CWM recovery, version 5.xxx (which I feel now is a mistake), as I tried to install CM11 from MukilSoni, which needs CWM version 6.xx +. I am able to go into recovery and select CM11 image through CWM and proceed with install steps. But, after initial selection in CWM (like app install, etc) it rebooted and went into fastboot mode.I checked the log, it ended with some return error 7.
Then, I tried to Google and check how to recover from fastboot mode, but all failed. I didnt tried KDZ method, but thought to hear from you guys before making it more messy.
Glad, if I get any help and appreciate it.
Thanks for reading it and your time.
Regards,
Ganesh
Click to expand...
Click to collapse
Did you ever try pull out the battery, reinsert, reboot system with 3 buttons combination? I got several fastboot mode as you're facing, and the system works just fine using above method.
I think you got just soft brick. Please, keep the device stay untouched until someone with such expertise to solve the problem will guide you. I think @akiratoriyama can share his bad experience bricking his lovely p500.
Wish you luck.
PS.
You must to press three buttons a bit longer, do not release it, until recovery mode appearing. Otherwise fastboot mode or blank screen showing instead.
Sent from my Optimus One using xda app-developers app
agk.ganesh said:
Hi,
I have put more than 12 hours of my time, before creating this thread. I have tried things, but still struck, so thought to post it in a new thread. Thanks for all your time.
Currently struck in,
fastboot mode started udc_start()
I tried, fastboot erase recovery -> fastboot flash recovery recovery.img -> fastboot reboot (successfully). But it still struck at same place after reboot.
I tried with different recovery images, but still the same observation. I tried to boot by key combination (volume down+home+power), still same observation.
Earlier, I installed ROM manager through google play and installed CWM recovery, version 5.xxx (which I feel now is a mistake), as I tried to install CM11 from MukilSoni, which needs CWM version 6.xx +. I am able to go into recovery and select CM11 image through CWM and proceed with install steps. But, after initial selection in CWM (like app install, etc) it rebooted and went into fastboot mode.I checked the log, it ended with some return error 7.
Then, I tried to Google and check how to recover from fastboot mode, but all failed. I didnt tried KDZ method, but thought to hear from you guys before making it more messy.
Glad, if I get any help and appreciate it.
Thanks for reading it and your time.
Regards,
Ganesh
Click to expand...
Click to collapse
Two years ago I bricked my phone also after using ROM manger. Though I will never ever use this or similar tools again. But at least, if I remember correctly, I could revive my phone with the "fastboot erase recovery" method http://forum.xda-developers.com/showthread.php?t=1088046. But since you failed is seems to be another problem. I am not a fastboot expert , but since you bricked your phone with ROM manager too, I wanted to share my success story with above mentioned method and installing AmonRa recovery. So maybe you will give it a second try? All I can remember is, that it is extremely important to follow the instructions exactly.
xu3sno said:
Did you ever try pull out the battery, reinsert, reboot system with 3 buttons combination? I got several fastboot mode as you're facing, and the system works just fine using above method.
I think you got just soft brick. Please, keep the device stay untouched until someone with such expertise to solve the problem will guide you. I think @akiratoriyama can share his bad experience bricking his lovely p500.
Wish you luck.
PS.
You must to press three buttons a bit longer, do not release it, until recovery mode appearing. Otherwise fastboot mode or blank screen showing instead.
Sent from my Optimus One using xda app-developers app
Click to expand...
Click to collapse
androidck said:
Two years ago I bricked my phone also after using ROM manger. Though I will never ever use this or similar tools again. But at least, if I remember correctly, I could revive my phone with the "fastboot erase recovery" method http://forum.xda-developers.com/showthread.php?t=1088046. But since you failed is seems to be another problem. I am not a fastboot expert , but since you bricked your phone with ROM manager too, I wanted to share my success story with above mentioned method and installing AmonRa recovery. So maybe you will give it a second try? All I can remember is, that it is extremely important to follow the instructions exactly.
Click to expand...
Click to collapse
Thanks @xu3sno & @androidck
I am also getting help from mukulsoni & others in Official CM11 version 10 thread.
I am able to go into the flash tool (pointed by mukulsoni, http://forum.xda-developers.com/showpost.php?p=49567169&postcount=45)
and able to go 'Select kernel to hotboot' with recovery.img (CWMod-6.4.0.6-Jan16)
But rebooting by HOME+Volume DOWN+POWER --> goes into CWM recovery of v5.0.2.0 (which i installed initially)
I am thinking, what to do next.
I will keep my progress posted here.
Thanks for listening..
agk.ganesh said:
Thanks @xu3sno & @androidck
I am also getting help from mukulsoni & others in Official CM11 version 10 thread.
I am able to go into the flash tool (pointed by mukulsoni, http://forum.xda-developers.com/showpost.php?p=49567169&postcount=45)
and able to go 'Select kernel to hotboot' with recovery.img (CWMod-6.4.0.6-Jan16)
But rebooting by HOME+Volume DOWN+POWER --> goes into CWM recovery of v5.0.2.0 (which i installed initially)
I am thinking, what to do next.
I will keep my progress posted here.
Thanks for listening..
Click to expand...
Click to collapse
Are you sure that you are booting into cwm v5.0.2.0? Version is listed at the top. If that is true, then either the flash tool failed to flash cwm v6.4.0.6, or you have chosen the wrong recovery.img. This can easily happen since they all have the same name. Try to flash it again, but make sure that you use the correct image.
Also, I believe that you may not have any rom installed, or existing rom might be corrupted. So you may want to flash a cm-9 or cm-10.x rom first, just to stabilize and to be sure that you are healthy. Those can be flashed using cwm 5.0.2.0. I can post a link or two, if you'd like.
Edit: Here is a link to cm-10.1.6:
http://jenkins.androidarmv6.org/view/All/job/android/597/
Gapps already included.
Sent from my LG-P509 using Tapatalk 2
ibub said:
Are you sure that you are booting into cwm v5.0.2.0?
Also, I believe that you may not have any rom installed, or existing rom might be corrupted. So you may want to flash a cm-9 or cm-10.x rom first, just to stabilize and to be sure that you are healthy. Those can be flashed using cwm 5.0.2.0. I can post a link or two, if you'd like.
Click to expand...
Click to collapse
+1
CM10.1.6 worked
ibub said:
Are you sure that you are booting into cwm v5.0.2.0? Version is listed at the top. If that is true, then either the flash tool failed to flash cwm v6.4.0.6, or you have chosen the wrong recovery.img. This can easily happen since they all have the same name. Try to flash it again, but make sure that you use the correct image.
Also, I believe that you may not have any rom installed, or existing rom might be corrupted. So you may want to flash a cm-9 or cm-10.x rom first, just to stabilize and to be sure that you are healthy. Those can be flashed using cwm 5.0.2.0. I can post a link or two, if you'd like.
Edit: Here is a link to cm-10.1.6:
http://jenkins.androidarmv6.org/view/All/job/android/597/
Gapps already included.
Sent from my LG-P509 using Tapatalk 2
Click to expand...
Click to collapse
Thanks @ibub for your helping hand.
I will check why recovery image not upgrading as expected. (I didn't manually download CWM5.xx version to my PC. I got it via ROM manager app, so i hope I haven't chosen wrong image)
Yes, I got CM10.1.6 from your link and installation went successfully and able to boot up..
But, it is very slow. (May be it will take some time?!) I will check it.
Between, @mukulsoni advised to install CWM6.xxx via CWM5.0.2.0. I will check how it goes.
mns123 said:
+1
Click to expand...
Click to collapse
Thanks.
agk.ganesh said:
Thanks @ibub for your helping hand.
I will check why recovery image not upgrading as expected. (I didn't manually download CWM5.xx version to my PC. I got it via ROM manager app, so i hope I haven't chosen wrong image)
Yes, I got CM10.1.6 from your link and installation went successfully and able to boot up..
But, it is very slow. (May be it will take some time?!) I will check it.
Between, @mukulsoni advised to install CWM6.xxx via CWM5.0.2.0. I will check how it goes.
Thanks.
Click to expand...
Click to collapse
Yeah, I chose to post that link only to make sure that your phone is healthy. Now you can install any recovery/rom that you want. If your volume keys are broken, I suggest that you flash to twrp recovery. It's touch driven.
Sent from my LG-P509 using Tapatalk 2
Thanks
ibub said:
Yeah, I chose to post that link only to make sure that your phone is healthy. Now you can install any recovery/rom that you want. If your volume keys are broken, I suggest that you flash to twrp recovery. It's touch driven.
Sent from my LG-P509 using Tapatalk 2
Click to expand...
Click to collapse
Yes, I will try installing now new recovery and then new ROM.
Very glad to see the support from you guys... Thanks ibub and all..
[rant] NEVER EVER USE KDZ. PERIOD. :crying: [/rant]
Best of luck on your ROM journey :good:
Thanks
akiratoriyama said:
[rant] NEVER EVER USE KDZ. PERIOD. :crying: [/rant]
Best of luck on your ROM journey :good:
Click to expand...
Click to collapse
Thanks @akiratoriyama.
I have upgraded CWM recovery 6.xx through CWM 5.0.2.0 and successfully installed MukulSoni's Kitkat ROM.
And enjoying eating kitkat..
Thanks all..
Really hope someone can help me on this. I clicked on update and now it shows 12.0-YNG1TAS17L
And when I boot the phone into recovery, it goes to a new screen of Cyanogen Recovery, it is totally different than TWRP that I have in on my phone.
I already make sure the phone "update Cyanogen Recovery" is unchecked. But no matter now many times I reboot, reset the phone. It goes to that new recovery screen.
Now I can't root my phone at all. I tried android-sdk-windows.....etc. It will not work.
Tried install it from recovery, it saids install failed.
IS there a way I can use TWRP instead?
Thanks
benzso63 said:
I already make sure the phone "update Cyanogen Recovery" is unchecked.
Click to expand...
Click to collapse
Well, you should have checked that BEFORE the update, not after.
benzso63 said:
IS there a way I can use TWRP instead?
Click to expand...
Click to collapse
Yes, there are many ways. Check custom recovery installation.
benzso63 said:
Really hope someone can help me on this. I clicked on update and now it shows 12.0-YNG1TAS17L
And when I boot the phone into recovery, it goes to a new screen of Cyanogen Recovery, it is totally different than TWRP that I have in on my phone.
I already make sure the phone "update Cyanogen Recovery" is unchecked. But no matter now many times I reboot, reset the phone. It goes to that new recovery screen.
Now I can't root my phone at all. I tried android-sdk-windows.....etc. It will not work.
Tried install it from recovery, it saids install failed.
IS there a way I can use TWRP instead?
Thanks
Click to expand...
Click to collapse
Use fastboot or a toolkit to reinstall TWRP, after it installs reboot back into TWRP, dont reboot the whole system and TWRP will stick. Otherwise TWRP will be overwritten with the stock recovery.
benzso63 said:
Really hope someone can help me on this. I clicked on update and now it shows 12.0-YNG1TAS17L
And when I boot the phone into recovery, it goes to a new screen of Cyanogen Recovery, it is totally different than TWRP that I have in on my phone.
I already make sure the phone "update Cyanogen Recovery" is unchecked. But no matter now many times I reboot, reset the phone. It goes to that new recovery screen.
Now I can't root my phone at all. I tried android-sdk-windows.....etc. It will not work.
Tried install it from recovery, it saids install failed.
IS there a way I can use TWRP instead?
Thanks
Click to expand...
Click to collapse
Read the FAQ:
http://forum.xda-developers.com/oneplus-one/help/faq-oneplus-one-frequently-questions-t2895136
XDA Moderator
Transmitted via Bacon
Bro, I followed this instructions. Did everything I could but still boot up with stock recovery. It is stuck. I don't know what to do .
As you can see the screen shot when I tried push the superSu to it, it saids error: device not found.
All previous steps I followed without error.
But end up still showing stock recovery.
Heisenberg said:
Read the FAQ:
http://forum.xda-developers.com/oneplus-one/help/faq-oneplus-one-frequently-questions-t2895136
XDA Moderator
Transmitted via Bacon
Click to expand...
Click to collapse
I did but it saids device not found.
gsmyth said:
Use fastboot or a toolkit to reinstall TWRP, after it installs reboot back into TWRP, dont reboot the whole system and TWRP will stick. Otherwise TWRP will be overwritten with the stock recovery.
Click to expand...
Click to collapse
benzso63 said:
Bro, I followed this instructions. Did everything I could but still boot up with stock recovery. It is stuck. I don't know what to do .
As you can see the screen shot when I tried push the superSu to it, it saids error: device not found.
All previous steps I followed without error.
But end up still showing stock recovery.
Click to expand...
Click to collapse
You haven't followed the instructions there, from what I can see you've issued the "fastboot reboot" command after flashing the recovery, which you're not meant to do, you're meant to force a reboot directly into recovery with the power + volume down combo.
Hi Heisenberg, I got the problem solved by using the toolkit. Now I got my TWRP back and rooted. Thanks for the info.
Heisenberg said:
You haven't followed the instructions there, from what I can see you've issued the "fastboot reboot" command after flashing the recovery, which you're not meant to do, you're meant to force a reboot directly into recovery with the power + volume down combo.
Click to expand...
Click to collapse
I have a nexus 5 16 GB and i downloaded the recent software update android 6.0.1 and then I decided to root and I used 'Nexus root toolkit v2.06' and first unlocked the bootloader and then rooted. Everything worked fine but after the process was complete it was rebooting and the booting animation went on and on for many hours and the device did not root. I really don't know what's going on. My purpose is to install a custom rom: cyanogenmod 12. Now what should I do ???? PLEASE HELP. When i try to enter recovery mode it shows a picture of the android mascot with opened back and exclamation and cannot enter command as well. and after some time the booting animation begins and goes on and on...
please help...
nexus_5_ said:
I have a nexus 5 16 GB and i downloaded the recent software update android 6.0.1 and then I decided to root and I used 'Nexus root toolkit v2.06' and first unlocked the bootloader and then rooted. Everything worked fine but after the process was complete it was rebooting and the booting animation went on and on for many hours and the device did not root. I really don't know what's going on. My purpose is to install a custom rom: cyanogenmod 12. Now what should I do ???? PLEASE HELP. When i try to enter recovery mode it shows a picture of the android mascot with opened back and exclamation and cannot enter command as well. and after some time the booting animation begins and goes on and on...
please help...
Click to expand...
Click to collapse
Unless something has changed, version 6. requires that you flash a special kernel before you can root your phone otherwise you are as you are now, stuck in a boot loop. You should probably download the factory image from Google, and then flash the system image to get rid of what you have done.. Perhaps then your phone will start normally
funnel71 said:
Unless something has changed, version 6. requires that you flash a special kernel before you can root your phone otherwise you are as you are now, stuck in a boot loop. You should probably download the factory image from Google, and then flash the system image to get rid of what you have done.. Perhaps then your phone will start normally
Click to expand...
Click to collapse
Thank you very much for the reply, I really do have no idea as to how to flash the factory image because i am very new in this area. Could you please recommend software and which factory image i should download, please ?? thanks very much.
:good:
funnel71 said:
Unless something has changed, version 6. requires that you flash a special kernel before you can root your phone otherwise you are as you are now, stuck in a boot loop. You should probably download the factory image from Google, and then flash the system image to get rid of what you have done.. Perhaps then your phone will start normally
Click to expand...
Click to collapse
Also, you mentioned a 'special kernel' what does that mean. All i want to do to my device is install cyanogenmod 12 and for that i believe it needs to be rooted, so i am really confused. What should I do know
I'm having this same problem, and unfortunately, when I start the phone on fastboot, I can not access the recovery mode in order to upload a factory image of nexus 5.
I used the new tool available her for quick flash, and now, I don't have a phone.
First, don't panic. Your phone is still very easy to recover. Unfortunately I can't get you a complete walkthrough here (for now at least), so I'll give you the main idea and you'll have to do your homework (as maybe you should have done before).
1. You need to get fastboot working on your computer. It's included in the Android sdk package, but there might be some easier way to get it. Google it. You might need drivers for your pc too. Google it as well.
2. Then you need to get into fastboot mode on your phone. To do it, hold down power button AND volume down button until it gets into fastboot mode. You will see an android on his back with the cover open. At this point, connect your phone to your pc, open a terminal on your pc and type "fastboot devices" without the quotes "". It should find your phone if fastboot is working. If it doesn't work go back to step 1.
3. Download TWRP recovery on your pc and place the img file in the same folder as your fastboot executable (not mandatory but easier). It can be found here https://dl.twrp.me/hammerhead/
4. Always in fastboot mode, type "fastboot flash recovery twrp-2.8.7.1-hammerhead.img" assuming you downloaded that file, which you should have by the way. It should install fine. If you haven't placed the file in the same directory as your fastboot executable, you will need to provide the path to your img file as well.
5. Then use the volume rocker to switch between modes and choose reboot recovery.
6. You should now be in TWRP recovery. At this point, download a custom kernel (anyone found on xda for hammerhead should do) and push it to your phone. It should be fairly simple with TWRP. Then flash your new kernel using install. It should help you get your phone booting normally. Alternatively, you can download a custom ROM like cm12.1 and flash it altogether. It will install everything needed for your phone to boot up too. Beware if flashing a ROM though, I strongly advice you to do a factory reset before flashing it. You will find that option in the wipe menu.
Hope it helps, let me know if you need further assistance.
Yesterday, I have tried everything to have my computer to recognize the "fastboot" command, and I installed like 2 or 3 different programs for that. With my old Windows 7, I have been able to push a flashed image to fix this issue, using the fastboot command, but with Windows 10, it's always telling me it's not a valid command. I'll keep trying it, otherwise, i'll have to "resurrect" my old Windows XP computer.
Also, I noticed now that, while trying to install the fastboot, as per some files that I could download, but no file has been copied into my computer, not even if I run it as admin.
fixed. but no RECOVERY mode options....
Hi Guys,
Thank you very much for the help, I have finally recovered the phone and running android 6.0 MRA58N but it is not rooted. Now if you don't mind could you teach me how to root because i have checked lots of videos and tuts but none worked for me...
IMPORTANT:
when i am in recovery mode why cannot I access options even when i press volume up + power button and release them at the same time...????
Thanks in advance.
Just flash a custom recovery via fastboot. Just make sure your bootloader is unlocked. Can't link though.
hi guys i have used nexus 5 mobile with cyanogenmod 14.1 .It worked properly in 1 year. after that suddenly switched off and it not properly boot up .i try to switch on my mobile , first it show google with unlock logo properly and when it show cyanogenmod logo it stuck and again show google with unlock logo....i try recovery mode to wipe and flash the same rom ....the process is interrupt at middle stage and again show the google..i try lots of time . after few try that process finished completely without interrupt. then use my mobile 1 day same as i used first time root. after that same problem occur on my mobile ..so help me guys
@[email protected], possible power button problem?