Related
I accepted the latest over the air update and I need to know if that messed up my chances of obtaining root. I tried photon torpedo and could not get it to work. My device says it is unlocked but I can not boot into recovery. I have flashed several recoveries using sdk-tools but I cannot erase any recoveries. I receive an error. I have tried several things and am at a loss to as what is the most recent way if there is one. Looking for someone with more experience then I to guide me. I previously rooted my EVO 4g and EVO 3d and was away from internet for about 9 months so I mistook the old Motorola Photon for the Photon Q. Didn't realize till way later that I was trying some rooting techniques intended for the old photon on my photon q. Anyways I feel a bit lost. Any help would be greatly appreciated. I can provide any information requested. Will be monitoring this thread all day today and will provide quick responses. Cheers!
Uhm... You tried the rooting steps for the Photon?
I really hope you didn't brick your device - that is a SURE fire way to do it tho.
Anyhoo, why haven't you just tried the official unlock from Moto?
arrrghhh said:
Uhm... You tried the rooting steps for the Photon?
I really hope you didn't brick your device - that is a SURE fire way to do it tho.
Anyhoo, why haven't you just tried the official unlock from Moto?
Click to expand...
Click to collapse
I did try that first. And successfully as far as I know because my bootloader says unlocked. I then went to install supersu and It won't install su binary. Tried to force install su binary and that did not work either. Any ideas? I joined the military so I was busy for 9 months straight. Honestly I'm usually more up to date than that. I think it's an understandable mistake and I understand the risks behind rooting. I bricked my first phone 7 years ago and brought it back using putty.
sent17inel said:
I did try that first. And successfully as far as I know because my bootloader says unlocked. I then went to install supersu and It won't install su binary. Tried to force install su binary and that did not work either. Any ideas? I joined the military so I was busy for 9 months straight. Honestly I'm usually more up to date than that. I think it's an understandable mistake and I understand the risks behind rooting. I bricked my first phone 7 years ago and brought it back using putty.
Click to expand...
Click to collapse
You didn't truly brick the device if you were able to bring it back using putty...
Regardless, you should always be careful with anything you do. Why are you trying to install the SuperSU binary right after unlocking? You need to flash a custom recovery first.
Or do you already have a custom recovery? I'm kinda lost here, you seemed to indicate you were unable to get a custom recovery flashed, but you're trying to force SuperSU without a custom recovery...?
arrrghhh said:
You didn't truly brick the device if you were able to bring it back using putty...
Regardless, you should always be careful with anything you do. Why are you trying to install the SuperSU binary right after unlocking? You need to flash a custom recovery first.
Or do you already have a custom recovery? I'm kinda lost here, you seemed to indicate you were unable to get a custom recovery flashed, but you're trying to force SuperSU without a custom recovery...?
Click to expand...
Click to collapse
Soft bricked . . . I tried to flash a custom recovery. I Tried 2. CW and another one that I can't remember at the moment. They both said they flashed successfully but I was unable to boot into any of them. I got the android with an exclamation mark. I tried to erase them and it gave me an error. Some kind of permission error. I did this all a few days ago. Decided to take a break. Honestly "you should always be careful with anything you do" . . did that really need to be said?
sent17inel said:
Honestly "you should always be careful with anything you do" . . did that really need to be said?
Click to expand...
Click to collapse
Hey, I'm not trying to force SuperSU to apply without a custom recovery here... one step at a time is all I'm trying to say.
Let's get on with it...
sent17inel said:
Soft bricked . . . I tried to flash a custom recovery. I Tried 2. CW and another one that I can't remember at the moment. They both said they flashed successfully but I was unable to boot into any of them. I got the android with an exclamation mark. I tried to erase them and it gave me an error. Some kind of permission error. I did this all a few days ago. Decided to take a break.
Click to expand...
Click to collapse
So you haven't been able to flash a custom recovery. When you flash, it says successful? Perhaps try again. Follow the directions carefully.
arrrghhh said:
Hey, I'm not trying to force SuperSU to apply without a custom recovery here... one step at a time is all I'm trying to say.
Let's get on with it...
So you haven't been able to flash a custom recovery. When you flash, it says successful? Perhaps try again. Follow the directions carefully.
Click to expand...
Click to collapse
I did try again about 5 minutes ago. It says that it won't unlock because it's already unlocked.
I got into the stock recovery. adb reboot recovery and then it will display a green android laying down with a red exclamation point. From there I hit both volume keys and it brings up the stock recovery menu. I should be able to go from here. I think the Update I did changed some things that caused the CW recovery to not flash right or to be rewritten before I can boot into it. I should be good now. Thank you for your help.
sent17inel said:
I got into the stock recovery. adb reboot recovery and then it will display a green android laying down with a red exclamation point. From there I hit both volume keys and it brings up the stock recovery menu. I should be able to go from here. I think the Update I did changed some things that caused the CW recovery to not flash right or to be rewritten before I can boot into it. I should be good now. Thank you for your help.
Click to expand...
Click to collapse
So you managed to flash custom recovery? I didn't mean to say you should try to unlock again - I meant you should try flashing recovery again (CWM, TWRP).
arrrghhh said:
So you managed to flash custom recovery? I didn't mean to say you should try to unlock again - I meant you should try flashing recovery again (CWM, TWRP).
Click to expand...
Click to collapse
With the over the air update it installs a shell script that forces the install of the stock recovery. When you reboot into the stock recovery you are presented with an image that looks like it has failed (android laying down with stomach open and a red exclamation point over it.) it will not do anything from here and eventually time out and reboot itself. If when it is at this image you press both volume keys you will be presented with a Recovery menu. I can take it from here. Thank you.
sent17inel said:
With the over the air update it installs a shell script that forces the install of the stock recovery. When you reboot into the stock recovery you are presented with an image that looks like it has failed (android laying down with stomach open and a red exclamation point over it.) it will not do anything from here and eventually time out and reboot itself. If when it is at this image you press both volume keys you will be presented with a Recovery menu. I can take it from here. Thank you.
Click to expand...
Click to collapse
Ok... Good luck.
Thread moved. Please post in the correct forum sections in future. All questions belong here in Q&A.
Thanks
AvRS
unlocking nd rooting visuals
can someone who owns Photon Q 4G LTE do a visual on rooting nd unlocking the bootloader cause was thinking bout getting this phone & dont wanna brick the phone i have read the guide's nd done tons of reseaching but found no visual's on how to do it can someone help pls?
thanks in advance
1300 said:
can someone who owns Photon Q 4G LTE do a visual on rooting nd unlocking the bootloader cause was thinking bout getting this phone & dont wanna brick the phone i have read the guide's nd done tons of reseaching but found no visual's on how to do it can someone help pls?
thanks in advance
Click to expand...
Click to collapse
Well, I was going to ask you where you are stuck in the process, but it sounds like you haven't even purchased the device yet...
I wouldn't worry about unlocking and rooting until the device is in your hands. We can help out a lot easier when you actually have the thing, hahaha.
To answer your question, I don't think there's any visuals because it's not a very visual thing. fastboot is anything but visually-appealing, and the process is rather dry. Just follow the steps carefully and you'll be fine. It's very straightforward.
Plus you must decide if you prefer to keep the bootloader LOCKED or UNLOCKED and still have root access. Research the differences in the two.
The only thing simple is the belief in simplicity.
Similar problem
Hey, I have similar problem here
I tried to root my phone using howtos on internet, but when I flash cwm img (first try from howtos, second try from CWM page), it take only a second (in every howto is it should take few minutes). But it returns that cwm was flashed sucessfully. Still.... its weird.
Then - when I want to reboot to CWM, I can see only that dead poor green thing. I tried to upload the superuser zip from here, but it returns "signature verification failed".
I still belive, there IS CWM recovery, because img was flashed sucessfully (or am I wrong?) so i tried to reboot to CWM via adb.
And another problem has appeared. ADB doesn`t recognise my phone. I installed the newest drivers from moto pages (USB drivers bit 4.7.1 and DeviceManager 2.3.4) have USB debugging mod ON, restarted my computer (win7 64bit), tried stand on my head, kill black ****.... it still returns "device not found".
Any ideas how to get to the next step? Functional adb would be great...
How long took you to flash cwm image?
Thx
D.Eternity said:
Hey, I have similar problem here
I tried to root my phone using howtos on internet, but when I flash cwm img (first try from howtos, second try from CWM page), it take only a second (in every howto is it should take few minutes). But it returns that cwm was flashed sucessfully. Still.... its weird.
Then - when I want to reboot to CWM, I can see only that dead poor green thing. I tried to upload the superuser zip from here, but it returns "signature verification failed".
I still belive, there IS CWM recovery, because img was flashed sucessfully (or am I wrong?) so i tried to reboot to CWM via adb.
And another problem has appeared. ADB doesn`t recognise my phone. I installed the newest drivers from moto pages (USB drivers bit 4.7.1 and DeviceManager 2.3.4) have USB debugging mod ON, restarted my computer (win7 64bit), tried stand on my head, kill black ****.... it still returns "device not found".
Any ideas how to get to the next step? Functional adb would be great...
How long took you to flash cwm image?
Thx
Click to expand...
Click to collapse
Let's take a step back here.
If you DON'T have ADB, you're NOT going to be able to flash CWM.
Make sure you establish an ADB connection BEFORE trying to flash again.
Good luck.
arrrghhh said:
Let's take a step back here.
If you DON'T have ADB, you're NOT going to be able to flash CWM.
Make sure you establish an ADB connection BEFORE trying to flash again.
Good luck.
Click to expand...
Click to collapse
Ok, but when I ask for fastboot devices, it returns my device (and I can work with fastboot commands). When I type adb device, it returns empty list. How is it possible?
D.Eternity said:
Ok, but when I ask for fastboot devices, it returns my device (and I can work with fastboot commands). When I type adb device, it returns empty list. How is it possible?
Click to expand...
Click to collapse
fastboot and adb are kind of separate things...
You can't access adb when the phone is in fastboot mode, and you can't access fastboot when the phone is in recovery or booted into a ROM. However, in recovery or when booted adb should work. If it's still failing make sure you're using the factory USB cable. Also, try a different port or computer.
Good luck.
arrrghhh said:
fastboot and adb are kind of separate things...
You can't access adb when the phone is in fastboot mode, and you can't access fastboot when the phone is in recovery or booted into a ROM. However, in recovery or when booted adb should work. If it's still failing make sure you're using the factory USB cable. Also, try a different port or computer.
Good luck.
Click to expand...
Click to collapse
I know fastboot and adb are separate things, this is why I assumed cwm recovery image was flashed succesfully (despite it took only a few seconds). Now I`m trying to get into CWM, but when my phone is plugged (standard mode), adb reboot recovery returns Device not found. I haven`t the original cable here, but in the office (where I have motorola cable) it was the same. Truth is both my computers are Win7 64bit. Is it possible adb has problem with 64bit system?
Thank you for helping me
So basically I rooted my LG p500h and installed a ROM through ROM manager, the thing is that when I rebooted the device I got stuck at the analog to the Android logo that shows up after the LG logo. I flashed an stock ROM through KDZ update software but after the program did it's thing, I did hard reset the phone and got the same problem: won't boot up and forever stuck at the android logo. I can get to emergency mode tho and when usb connected will show the battery charging up. I have searched solutions and I haven't reached one yet so everyone told me to post here and ask for some help! I hope it's not the end of my device Any help is sincerly appreciated!
Secretagogo said:
So basically I rooted my LG p500h and installed a ROM through ROM manager, the thing is that when I rebooted the device I got stuck at the analog to the Android logo that shows up after the LG logo. I flashed an stock ROM through KDZ update software but after the program did it's thing, I did hard reset the phone and got the same problem: won't boot up and forever stuck at the android logo. I can get to emergency mode tho and when usb connected will show the battery charging up. I have searched solutions and I haven't reached one yet so everyone told me to post here and ask for some help! I hope it's not the end of my device Any help is sincerly appreciated!
Click to expand...
Click to collapse
Much as I hate to say it, ROM Manager is not friendly to our devices. Secondly, stay away from KDZ too. But don't panic. You do have options. You will need to use either ADB and dd commands, or fastboot and fastboot mode. Since you can't boot, most likely the ADB way won't work ATM. Both methods require either the ADB binaries or the Android SDK. An alternate method would be Android Flash Recovery. There is a link in my signature. There are complete instructions in the download. On thing, put the device in fastboot mode before connecting it to the PC.
Enter into emergency mode, BACK+VOL UP+POWER
then follow this guide to flash recovery: http://forum.xda-developers.com/showpost.php?p=15217609&postcount=3
After that enter into recovery, HOME+VOL DOWN+POWER
then wipe data/factory reset, wipe dalvik cache, wipe cache, format system then flash a rom of your choice like oxygen, cm9 present in development section.
Then reboot
shinobisoft said:
Much as I hate to say it, ROM Manager is not friendly to our devices. Secondly, stay away from KDZ too. But don't panic. You do have options. You will need to use either ADB and dd commands, or fastboot and fastboot mode. Since you can't boot, most likely the ADB way won't work ATM. Both methods require either the ADB binaries or the Android SDK. An alternate method would be Android Flash Recovery. There is a link in my signature. There are complete instructions in the download. On thing, put the device in fastboot mode before connecting it to the PC.
Click to expand...
Click to collapse
Odd enough, I plugged in the device to the computer after the USB drivers got installed (following all the instructions given by the files provided), I went to the bathroom and left the cell phone unattended, just to find it boot up! weird. Anyways your advice was very helpful and very clear! Now I will figure out how to get my old ROM for my country. Thanks again!
So, I got my new phone today, and immediately rooted it. This was the first time I'd ever done something like this to any phone, so I was really in the dark on the whole matter. I managed to root it successfully, and proceeded to install Cyanogen, which took ages to install, and I remembered that I'd forgotten to wipe the phone, so I restarted, went into recovery mode and ACCIDENTALLY WIPED ALL OF MY FILES with TWRP. Once I realised what I'd done, I panicked, restarting the phone, which landed me, stuck, on the 'WARNING, BOOTLOADER UNLOCKED' screen. I panicked again, and went to this thread:
http://forum.xda-developers.com/showthread.php?t=2542219
And tried to follow everything, but I didn't really understand what I was doing and was in a state of panic. I can go into details of what I did if needs be, but long story short, whenever I boot up my phone I get the bootloader unlocked screen and do not boot into the OS. I cannot also access the Recovery window, and it has the android mascot lying on its back with a red triangle.
All I want to do is fix my phone, if anyone could guide me through this, I'd be forever grateful.
tl;dr: F**ked up, possible bricked my phone and don't know what to do.
Many thanks for any response.
Phaydze said:
So, I got my new phone today, and immediately rooted it. This was the first time I'd ever done something like this to any phone, so I was really in the dark on the whole matter. I managed to root it successfully, and proceeded to install Cyanogen, which took ages to install, and I remembered that I'd forgotten to wipe the phone, so I restarted, went into recovery mode and ACCIDENTALLY WIPED ALL OF MY FILES with TWRP. Once I realised what I'd done, I panicked, restarting the phone, which landed me, stuck, on the 'WARNING, BOOTLOADER UNLOCKED' screen. I panicked again, and went to this thread:
http://forum.xda-developers.com/showthread.php?t=2542219
And tried to follow everything, but I didn't really understand what I was doing and was in a state of panic. I can go into details of what I did if needs be, but long story short, whenever I boot up my phone I get the bootloader unlocked screen and do not boot into the OS. I cannot also access the Recovery window, and it has the android mascot lying on its back with a red triangle.
All I want to do is fix my phone, if anyone could guide me through this, I'd be forever grateful.
tl;dr: F**ked up, possible bricked my phone and don't know what to do.
Many thanks for any response.
Click to expand...
Click to collapse
Recovery has been deleted by u accidentally
Go to bootlander (power + volume down) try to install TWRP recovery again through adb n install cm11 directly through adb sideload
Phaydze said:
So, I got my new phone today, and immediately rooted it. This was the first time I'd ever done something like this to any phone, so I was really in the dark on the whole matter. I managed to root it successfully, and proceeded to install Cyanogen, which took ages to install, and I remembered that I'd forgotten to wipe the phone, so I restarted, went into recovery mode and ACCIDENTALLY WIPED ALL OF MY FILES with TWRP. Once I realised what I'd done, I panicked, restarting the phone, which landed me, stuck, on the 'WARNING, BOOTLOADER UNLOCKED' screen. I panicked again, and went to this thread:
http://forum.xda-developers.com/showthread.php?t=2542219
And tried to follow everything, but I didn't really understand what I was doing and was in a state of panic. I can go into details of what I did if needs be, but long story short, whenever I boot up my phone I get the bootloader unlocked screen and do not boot into the OS. I cannot also access the Recovery window, and it has the android mascot lying on its back with a red triangle.
All I want to do is fix my phone, if anyone could guide me through this, I'd be forever grateful.
tl;dr: F**ked up, possible bricked my phone and don't know what to do.
Many thanks for any response.
Click to expand...
Click to collapse
Since you managed to root, im assuming you have ADB and Fastboot on your PC?
Download a recovery.img file from XDA. I recommend this one ----> http://forum.xda-developers.com/showthread.php?t=2639583
Place the recovery.img file in the same file folder/location as your fastboot and ADB files.
Open a command window from the same location as the adb/fastboot/recover.img files.
In the command window type "fastboot device" and make sure some type of serial number shows up in the window.
Once you know your device is connected via fastboot, type: "fastboot flash recovery __________.img"
Where the ______.img is, you would put the name of the recovery.img file.
For example, the file that gets downloaded if you download philz touch (the link i gave you), is called "recovery.img"
So in fastboot you would type "fastboot flash recovery recovery.img"
Once thats been flashed, you should be able to boot into recovery, sideload a rom, and flash it to your device.
Good Luck!
Phaydze said:
So, I got my new phone today, and immediately rooted it. This was the first time I'd ever done something like this to any phone, so I was really in the dark on the whole matter. I managed to root it successfully, and proceeded to install Cyanogen, which took ages to install, and I remembered that I'd forgotten to wipe the phone, so I restarted, went into recovery mode and ACCIDENTALLY WIPED ALL OF MY FILES with TWRP. Once I realised what I'd done, I panicked, restarting the phone, which landed me, stuck, on the 'WARNING, BOOTLOADER UNLOCKED' screen. I panicked again, and went to this thread:
http://forum.xda-developers.com/showthread.php?t=2542219
And tried to follow everything, but I didn't really understand what I was doing and was in a state of panic. I can go into details of what I did if needs be, but long story short, whenever I boot up my phone I get the bootloader unlocked screen and do not boot into the OS. I cannot also access the Recovery window, and it has the android mascot lying on its back with a red triangle.
All I want to do is fix my phone, if anyone could guide me through this, I'd be forever grateful.
tl;dr: F**ked up, possible bricked my phone and don't kn.
go to this link for any response.
http://forum.xda-developers.com/showthread.php?t=2744058
Click to expand...
Click to collapse
Hello all,
2 days ago when on vacation i decided to temper around with my OnePlus one that i recently bought (have bought the Chinese version but it was already rooted and had cyanoged mod on it)
All was fine until i decided to flash Paranoid Android and i posted a question here, about how to bypass the always apearing CyanogenMod Simple Recovery tool.
After trying what everyone suggested and not getting result i had 1 last thing that someone suggested:
http://forum.xda-developers.com/showthread.php?p=54717885
If you still have not fixed this issue, for some reason when I was flashing my recovery it would NOT work for the life of me until I changed the name of the custom recovery file to 'recovery.img'. Everytime I flash (for example) openrecovery-twrp-blah-bacon.img it would say success, but it kept rebooting into CM fastboot mode.
Click to expand...
Click to collapse
I misunderstood and i renamed the .zip file from paranoid sources into recovery.img and flash (Kernel) it via some app from play store, i thin it was TRWL
Now my phone is stuck into loading faze and the only thing i can do is enter Fastboot mode.
I tried to do a:
fastboot erase cache
But it did not work, its still stuck in loading and will not do anything.
Could you help me out ? I have a really bad feeling i just lost my phone due to hurrying and not having a pc around to read more.
You can try to fastboot flash recovery(original or proper one that works) but I don't know the exact commands.
In the first case where your recovery would not switch from CM to TWRP/CWR was because you had "Update CM Recovery" enabled in Developer Options. If you ticked that off, then it would have replaced CM Recovery. Its confusing yeah.
So wait... you renamed the .zip to a .img? Thats not good. But at least you can enter fastboot mode so thats at least something. Is your bootloader still unlocked? Are you able to boot into recovery mode? Try fastboot boot <name-of-recovery-for-twrp>.img and see if you can get into recovery.
If you can then perform a wipe and then enable adb sideload within TWRP and then type,
adb sideload <name-of-zip>.zip and then after its done sideloading, reboot
Thanks for the answer.
I managed last night out of 10 flash resets to get the Custom Recovery Tool to booth up.
I was about to give up when i saw it boot and i immediately flashed the CM .zip i had on the phone from last time.
I even managed to get Paranoid android to flash and im very happy.
Thanks for the help
vidockq said:
Thanks for the answer.
I managed last night out of 10 flash resets to get the Custom Recovery Tool to booth up.
I was about to give up when i saw it boot and i immediately flashed the CM .zip i had on the phone from last time.
I even managed to get Paranoid android to flash and im very happy.
Thanks for the help
Click to expand...
Click to collapse
I'd appreciate it if we helped give us a thanks.
Sent from my One using Tapatalk
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?