Related
If you have updated your Pantech Crossover with latest update of gingerbread 2.3.6 and regretting it, don't feel bad because you can now root it with few simple steps which are mentioned hereunder...
NOTE: this procedure is very much safe, but if you mess something up just because of your less technical knowledge/experience then don't blame because I don't take any responsibility of your mistakes.
- connect your CrossOver with your computer and make sure that latest drivers are installed.
- download and extract attached file and open command prompt placed in it.
- type "adb reboot bootloader" and wait for phone to boot into bootloader mode (your phone will remain on 10% loading bar which is actually bootloader mode, so don't panic) [people with bootloader drivers issue should download modified drivers from the link below]
- type "fastboot boot recovery.img" and your phone will boot into CWM recovery.
- copy update.zip to your memory card and select "install update.zip from memory card" from the recovery menu.
- restart your phone and you are rooted.
------------------------------------------------
Modified Drivers
Google_USB_Driver_rev4_p8000mod_by_pawaa.zip
Download: http://www.mediafire.com/?3sr2pi8fds1zab8
Thank you sir I have been looking for this
Sent from my R800x using xda premium
i have a problem when i tell the phone to boot into bootloader it restarts and freezes on the loading bar
crazymonkey05 said:
i have a problem when i tell the phone to boot into bootloader it restarts and freezes on the loading bar
Click to expand...
Click to collapse
that is the bootloader mode, you can proceed to next step...
Thank you.
Thank you.
thank you i have succesfuly rooted it and now im having fun, thanks again
crazymonkey05 said:
thank you i have succesfuly rooted it and now im having fun, thanks again
Click to expand...
Click to collapse
having fun is good...
Linux
Awesome! Been hoping someone would crack this for a while.
Do you have a source for the .exe files by any chance? I'm on a linux box now, I'll be able to try it on Windows by tomorrow I think.
edit: nvm, had fastboot all along. thanks!
For those rooting, don't forget to enable Superuser through an app like Terminal Emulator.
If you open Terminal Emulator and the command prompt starts with a $, you are still rooted. Type "su" (without the quotes). If the next line in the command prompt starts with a #, congrats!
You're awesome
Sent from my Galaxy Nexus using Tapatalk 2
ok how do you get the device to boot into clockwork recovery because i only see the ASRU
crazymonkey05 said:
ok how do you get the device to boot into clockwork recovery because i only see the ASRU
Click to expand...
Click to collapse
You only have to follow the steps I mentioned, CMW recovery is include in the attached package...
Sent from my PantechP8000
Hi,
Firstly, thanks for posting this guide and the resources and files. I'm having a problem. After typing "fastboot boot recovery.img" in the cmd prompt, it says <waiting for device> and then doesn't do anything. On the device, the screen is still stuck at the loading screen with the bar at 10%. The only thing I can do is pull the battery to get it to boot up normally.
Am I missing a step or doing something wrong? Sorry this is my first experience with rooting. Is there anything that needs to be done before attempting to root using this method? My phone is pretty stock except for a few apps and launcher pro. Thanks for all the help.
HungryBear22 said:
Hi,
Firstly, thanks for posting this guide and the resources and files. I'm having a problem. After typing "fastboot boot recovery.img" in the cmd prompt, it says <waiting for device> and then doesn't do anything. On the device, the screen is still stuck at the loading screen with the bar at 10%. The only thing I can do is pull the battery to get it to boot up normally.
Am I missing a step or doing something wrong? Sorry this is my first experience with rooting. Is there anything that needs to be done before attempting to root using this method? My phone is pretty stock except for a few apps and launcher pro. Thanks for all the help.
Click to expand...
Click to collapse
android development drivers are missing in your computer, while your phone is in bootloader mode, check your device manager for that...
Here is the link to download these drivers:
http://goo.gl/WUyXn
After I got the right drivers installed, worked like a charm thanks.
pawaa said:
android development drivers are missing in your computer, while your phone is in bootloader mode, check your device manager for that...
Here is the link to download these drivers:
Thanks for the help. Ok, so when I have the device at the 10% loading bar, in the device manager it shows "Other devices" with an "Android" subcategory with the yellow exclamation (!) mark. I right click that, click update driver, and point it to the directory with the download and unzipped drivers that you asked me to download. However, it says it can't find any drivers to install.
Note that when I'm normally running the phone connected to the computer, it shows up in the device manager as a Pantech android device, and I can transfer files seamlessly using the Pantech Connectivity Suite. Sorry for asking so many questions. I really appreciate the help. If there's any other information you need that I forgot to add, let me know. Thanks again for the help.
Click to expand...
Click to collapse
HungryBear22 said:
.............. I really appreciate the help. If there's any other information you need that I forgot to add, let me know. Thanks again for the help.
Click to expand...
Click to collapse
You have to manually select the drivers from the last option
Sent from my PantechP8000
pawaa said:
You have to manually select the drivers from the last option
Sent from my PantechP8000
Click to expand...
Click to collapse
Thanks for the help, I got everything to work and now have root access. Thank you so much!
Another Thank YOU
Hello pawaa, and thanks for posting on the Android Forums too. The "root" worked exactly as you instructed, which really helps an amateur like me.
fred
You guys are most welcome, enjoy your newly rooted devices.
Sent from my PantechP8000
Hello,
I followed Hasoon's all-in-one root toolkit and flashed the included TWRP 2.5.0.0 onto my AT&T HTC One X. Now I cannot do anything, whatever I do, it tells me "Unable to mount /cache". Could you please help me? I can't mount the sdcard to the computer either, so I am sort of stuck.
Thanks!
Simone
simsale said:
Hello,
I followed Hasoon's all-in-one root toolkit and flashed the included TWRP 2.5.0.0 onto my AT&T HTC One X. Now I cannot do anything, whatever I do, it tells me "Unable to mount /cache". Could you please help me? I can't mount the sdcard to the computer either, so I am sort of stuck.
Thanks!
Simone
Click to expand...
Click to collapse
Can you format the SD card in TWRP?
exad said:
Can you format the SD card in TWRP?
Click to expand...
Click to collapse
I was able to wipe it. However, it still gave all these same unable to mount /cache error messages. The data is gone though.
When I connect the mounted device to the computer it still doesn't recognize it.
Thanks!
Simone
simsale said:
I was able to wipe it. However, it still gave all these same unable to mount /cache error messages. The data is gone though.
When I connect the mounted device to the computer it still doesn't recognize it.
Thanks!
Simone
Click to expand...
Click to collapse
Does the PC not recognize that anything is connected or does it detect that its plugged in but can't find the driver?
What rom is currently installed on the phone?
exad said:
Does the PC not recognize that anything is connected or does it detect that its plugged in but can't find the driver?
What rom is currently installed on the phone?
Click to expand...
Click to collapse
Currently I think it recognizes the phone as a media device (or similar, I forgot the name), not as a disk drive. I am on a Mac, and I have Android File Transfer installed, which then tells me that the device cannot be opened. On Windows it couldn't be opened either although it talked about a driver issue. I currently only have a Mac, but from Monday I could work on a Windows machine again.
The ROM currently being installed is the original AT&T provided ROM.
Thanks so much!
Simone
simsale said:
Currently I think it recognizes the phone as a media device (or similar, I forgot the name), not as a disk drive. I am on a Mac, and I have Android File Transfer installed, which then tells me that the device cannot be opened. On Windows it couldn't be opened either although it talked about a driver issue. I currently only have a Mac, but from Monday I could work on a Windows machine again.
The ROM currently being installed is the original AT&T provided ROM.
Thanks so much!
Simone
Click to expand...
Click to collapse
What version? IS it already installed on your phone? I'm trying to find out if you require MTP drivers or not. Latest version of sense/stock Roms require MTP driver to access the SD card.
In any case I wouldn't suggest using any version of TWRP above 2.3.3.1
So, I would download twrp 2.3.3.1 and check the md5
then fastboot flash recovery recoveryfilename.img
fastboot erase cache
fastboot reboot-bootloader
select recovery from bootloader then try to mount sdcard with twrp.
exad said:
What version? IS it already installed on your phone? I'm trying to find out if you require MTP drivers or not. Latest version of sense/stock Roms require MTP driver to access the SD card.
In any case I wouldn't suggest using any version of TWRP above 2.3.3.1
So, I would download twrp 2.3.3.1 and check the md5
then fastboot flash recovery recoveryfilename.img
fastboot erase cache
fastboot reboot-bootloader
select recovery from bootloader then try to mount sdcard with twrp.
Click to expand...
Click to collapse
I see, this all sounds like I need to wait for a windows machine.
I am not sure what ROM version, unfortunately. I bought the phone in December from AT&T, and it all looks like it asks for MTP drivers. I will try this with a Windows machine and then get back to this post - thank you so very much for your help.
Simone
simsale said:
I see, this all sounds like I need to wait for a windows machine.
I am not sure what ROM version, unfortunately. I bought the phone in December from AT&T, and it all looks like it asks for MTP drivers. I will try this with a Windows machine and then get back to this post - thank you so very much for your help.
Simone
Click to expand...
Click to collapse
Yes, you would need mtp drivers for the latest software version. They are included with the latest HTC sync.
exad said:
Yes, you would need mtp drivers for the latest software version. They are included with the latest HTC sync.
Click to expand...
Click to collapse
Alright, I have tried this with the latest HTC Sync manager: the MTP Drivers however won't install. I have tried with the One X+ of my Dad (which is also brand new, so probably requires the newest version also), and it installs fine and appears as a media device in the explorer. Mine however does not do anything, and driver installation says it fails to install the driver. I have tried manually installing the drivers, however, it seems to have to do with the phone because when I disconnect it suddenly Windows 7 is able to install those drivers, and as mentioned before it also works with a functional phone.
Next week I will be back at work and I have a Windows 8 machine there. I don't have high hopes that it works there, but since there seems to be an MTP driver issue with Win7, maybe there's a chance.
Is there anything else I could do?
Thanks!
PS: don't use your vacation time to root your phone...haha.
simsale said:
Alright, I have tried this with the latest HTC Sync manager: the MTP Drivers however won't install. I have tried with the One X+ of my Dad (which is also brand new, so probably requires the newest version also), and it installs fine and appears as a media device in the explorer. Mine however does not do anything, and driver installation says it fails to install the driver. I have tried manually installing the drivers, however, it seems to have to do with the phone because when I disconnect it suddenly Windows 7 is able to install those drivers, and as mentioned before it also works with a functional phone.
Next week I will be back at work and I have a Windows 8 machine there. I don't have high hopes that it works there, but since there seems to be an MTP driver issue with Win7, maybe there's a chance.
Is there anything else I could do?
Thanks!
PS: don't use your vacation time to root your phone...haha.
Click to expand...
Click to collapse
OK, so on Windows 8 I am able to install the driver, and it does not fail like in Win7, but I still can't access the mounted storage. The message of the device is:
This device cannot start. (Code 10)
The process hosting the driver for this device has terminated.
Is there anything else I can do, or should I rather get a new phone?
simsale said:
Is there anything else I can do, or should I rather get a new phone?
Click to expand...
Click to collapse
Did you do all of what exad said in his earlier post (quoted below) already?
exad said:
So, I would download twrp 2.3.3.1 and check the md5
then fastboot flash recovery recoveryfilename.img
fastboot erase cache
fastboot reboot-bootloader
select recovery from bootloader then try to mount sdcard with twrp.
Click to expand...
Click to collapse
lauterm said:
Did you do all of what exad said in his earlier post (quoted below) already?
Click to expand...
Click to collapse
Yes, in fact, I cannot connect to the phone with this strange driver issue, which means none of the commands actually do anything.
simsale said:
Yes, in fact, I cannot connect to the phone with this strange driver issue, which means none of the commands actually do anything.
Click to expand...
Click to collapse
Are you rebooting to bootloader to do the fastboot commands? In bootloader it should say Fastboot in red. Then after a couple seconds that should change to Fastboot USB. I don't think fastboot needs the specific drivers to be on the PC like mounting the SD card requires.
lauterm said:
Are you rebooting to bootloader to do the fastboot commands? In bootloader it should say Fastboot in red. Then after a couple seconds that should change to Fastboot USB. I don't think fastboot needs the specific drivers to be on the PC like mounting the SD card requires.
Click to expand...
Click to collapse
Well, when I turn on the phone, all I get is the TWRP interface. Mounting from there doesn't do anything. I am not in fact in bootloader. Maybe I am doing something wrong here!!
simsale said:
Well, when I turn on the phone, all I get is the TWRP interface. Mounting from there doesn't do anything. I am not in fact in bootloader. Maybe I am doing something wrong here!!
Click to expand...
Click to collapse
You are definitely doing something wrong. fastboot commands only work within bootloader/fastboot and adb commands only work while the rom is loaded up or in sideload mode in TWRP. It's assumed you know this prior to rooting.
simsale said:
Well, when I turn on the phone, all I get is the TWRP interface. Mounting from there doesn't do anything. I am not in fact in bootloader. Maybe I am doing something wrong here!!
Click to expand...
Click to collapse
Turn off the phone. Then hold volume down and briefly press the power button. Don't let go of volume down until it gets to the boot loader screen. Wait for fast bot USB to display. Then you can try exad's fast boot commands.
Sent from my One X using xda app-developers app
lauterm said:
Turn off the phone. Then hold volume down and briefly press the power button. Don't let go of volume down until it gets to the boot loader screen. Wait for fast bot USB to display. Then you can try exad's fast boot commands.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Oh, thanks so much. I actually did know this from rooting my old phone - I guess I forgot.
It doesn't go into Fastboot USB though, stays at Fastboot. Is there another trick? Thanks so much!
use cwm
simsale said:
Oh, thanks so much. I actually did know this from rooting my old phone - I guess I forgot.
It doesn't go into Fastboot USB though, stays at Fastboot. Is there another trick? Thanks so much!
Click to expand...
Click to collapse
It should change to FASTBOOT USB if you are plugged into a computer. If you connected to the computer after you got to bootloader mode, you might have to press volume up or down to get it to switch to FASTBOOT USB Maybe this is the root of your problem. Have you tried multiple USB cables? Is there any crud in the micro-USB port on your phone? It's a little odd that the micro-USB port would break in a manner that charging would still work but not data connections, but I'm starting to wonder if that isn't the case.
lauterm said:
It should change to FASTBOOT USB if you are plugged into a computer. If you connected to the computer after you got to bootloader mode, you might have to press volume up or down to get it to switch to FASTBOOT USB Maybe this is the root of your problem. Have you tried multiple USB cables? Is there any crud in the micro-USB port on your phone? It's a little odd that the micro-USB port would break in a manner that charging would still work but not data connections, but I'm starting to wonder if that isn't the case.
Click to expand...
Click to collapse
OK, I managed to get into Fastboot USB and now have the SDcard mounted. I'll try flashing a new ROM now. Is this one you'd recommend?
http://forum.xda-developers.com/showthread.php?t=1868236&highlight=+rom+
Thanks so much!!
Simone
I installed latest CM rom and unfortunately xposed framework on top.
after that my device does not start and seems to stack in CM logo for ever.
I can get to recovery but does not find any backup files! Seems like scdard is empty or not recognizable.
I tried to push a new rom for with adb from fastboot but my pc does not seems to find the phone. Like adb debugging is not enabled on the phone.
I also fails when I try to erase the device from recovery.
Any help is welcome.
Boot in fastboot and flash a factory image. Best way to fix pretty much anything.
mortenmhp said:
Boot in fastboot and flash a factory image. Best way to fix pretty much anything.
Click to expand...
Click to collapse
does for find the device any more, so i cannot flash anything
Try to reinstall the universal drivers, and try different usb ports on your computer.
sprkrt said:
does for find the device any more, so i cannot flash anything
Click to expand...
Click to collapse
You need to make sure you're in the bootloader.
sprkrt said:
does for find the device any more, so i cannot flash anything
Click to expand...
Click to collapse
Hi, your phone is ok, just empty. the problem is on the computer. You need to fix the driver for nexus 5. You probably have them installed since you unlocked the phone. just keep your phone connected and on recovery mode.
go to device manager, look for nexus 5. Choose "update driver"
"Browse my computer for driver...,
"let me pick from a list of device drivers"
choose any ADB driver, and install it.
Many more ways to do it
sprkrt said:
does for find the device any more, so i cannot flash anything
Click to expand...
Click to collapse
If it can boot to the bootloader, and it still cant find the device, the problem is either with your computer(driver) or with the usb hardware on the phone(highly unlikely since it happened after you messed with software)
mortenmhp said:
If it can boot to the bootloader, and it still cant find the device, the problem is either with your computer(driver) or with the usb hardware on the phone(highly unlikely since it happened after you messed with software)
Click to expand...
Click to collapse
problem solved.
i tried the exact same process on my imac and worked perfectly!
( i had already reinstalled the drivers on my pc with no luck...)
sprkrt said:
problem solved.
i tried the exact same process on my imac and worked perfectly!
( i had already reinstalled the drivers on my pc with no luck...)
Click to expand...
Click to collapse
He he this deserves a headline
Apple recovered my nexus from death lmao
Glad that you worked it out.
Sent from my Nexus 5 using Tapatalk
Hey guys, semi-noob here. Here is the situation:
1) encrypted device yesterday (Nexus 5 w/ stock android 4.4.2 and CWM Recovery)
2) 4.4.3 came out, downloaded and installed (yee! new dialer)
3) restarted after install (so excited! :fingers-crossed
4) enter the bootloop
5) try to do fastboot -> recovery mode
6) nope. recovery mode = bootloop
What do, XDA? I searched the forums, and nothing seems to address this. The N5 isn't even showing up on the devices list for my comp (W7 w/ ADB installed and ran before). I can't talk to it through my computer.
haloux said:
Hey guys, semi-noob here. Here is the situation:
1) encrypted device yesterday (Nexus 5 w/ stock android 4.4.2 and CWM Recovery)
2) 4.4.3 came out, downloaded and installed (yee! new dialer)
3) restarted after install (so excited! :fingers-crossed
4) enter the bootloop
5) try to do fastboot -> recovery mode
6) nope. recovery mode = bootloop
What do, XDA? I searched the forums, and nothing seems to address this. The N5 isn't even showing up on the devices list for my comp (W7 w/ ADB installed and ran before). I can't talk to it through my computer.
Click to expand...
Click to collapse
Hi.
Boot into bootloader
open cmd
Type fastboot devices
See if your device gets detected or not.
If yes..you can flash stock factory IMG.
If not make sure u have installed the drivers and adb set up is there.
Sent from my Nexus 5 using XDA Free mobile app
Vivek_Neel said:
Hi.
Boot into bootloader
open cmd
Type fastboot devices
See if your device gets detected or not.
If yes..you can flash stock factory IMG.
If not make sure u have installed the drivers and adb set up is there.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Hi,
Thanks for the quick response.
Win7 doesn't even detect the N5. Device manager doesn't even show that it exists (as android device or anything else). I've unplugged and replugged, no sound, multiple different ports.
Whatever you do don't use a toolkit try and fix it.If something else happens trying to diagnosis it would be very hard.Manual installation and fixing is the Best. Plus you learn how to get out of jams.
habitformer said:
Whatever you do don't use a toolkit try and fix it.If something else happens trying to diagnosis it would be very hard.Manual installation and fixing is the Best. Plus you learn how to get out of jams.
Click to expand...
Click to collapse
Will do (or won't do?). Thank you for the advice. Any tips on how to get my system to recognize the device?
So here are a list of things I've tried so far.
Verified that ADB works and is capable of recognizing an android device
Booted into fastboot and attached to 2 different computers (with no response or indication of the device on both)
Verified that ADB and all SDK software was up to date
Restarted computer to verify USB controller status
Refreshed device manager list before and after plugging in N5.
I'm at a loss. ADB was used in the past, the drivers are up to date. It's as though the N5 isn't even sending a signal to my computer that it's alive. I'm losing hope here guys. Please, someone help.
haloux said:
So here are a list of things I've tried so far.
Verified that ADB works and is capable of recognizing an android device
Booted into fastboot and attached to 2 different computers (with no response or indication of the device on both)
Verified that ADB and all SDK software was up to date
Restarted computer to verify USB controller status
Refreshed device manager list before and after plugging in N5.
I'm at a loss. ADB was used in the past, the drivers are up to date. It's as though the N5 isn't even sending a signal to my computer that it's alive. I'm losing hope here guys. Please, someone help.
Click to expand...
Click to collapse
I swear I went through this 2 days ago @scarmon25 will tell,we had a late night hangouts session.
I used a one of my many nexus cables and it finally linked up.Not to sound like a jerk but you've got USB debugging on right?
I reread your OP.If.you can get into recovery just restore a back up!!! Than all should be good.
haloux said:
So here are a list of things I've tried so far.
Verified that ADB works and is capable of recognizing an android device
Booted into fastboot and attached to 2 different computers (with no response or indication of the device on both)
I'm at a loss. ADB was used in the past, the drivers are up to date. It's as though the N5 isn't even sending a signal to my computer that it's alive. I'm losing hope here guys. Please, someone help.
Click to expand...
Click to collapse
One thing you haven't stated. Do you have the fastboot drivers installed? They're different from adb. Since you're not seeing the device after "fastboot devices", I would check and make sure.
habitformer said:
I swear I went through this 2 days ago @scarmon25 will tell,we had a late night hangouts session.
I used a one of my many nexus cables and it finally linked up.Not to sound like a jerk but you've got USB debugging on right?
I reread your OP.If.you can get into recovery just restore a back up!!! Than all should be good.
Click to expand...
Click to collapse
Yea, USB debugging was on. The recovery mode just yields the dead android.
adrman said:
One thing you haven't stated. Do you have the fastboot drivers installed? They're different from adb. Since you're not seeing the device after "fastboot devices", I would check and make sure.
Click to expand...
Click to collapse
How would I verify that? I assumed that fastboot drivers were installed bc I used them in the past.
Code:
fastboot devices
(yields)
No devices found.
I would do a search here for "windows fastboot drivers". I can't be of much help to you as I haven't used windows for several years now. Also, if you have a working Android device, see if it shows up when connected in bootloader mode as a test.
Sent from my Nexus 5 using Tapatalk
Small breakthrough:
Used a diff cable like someone suggested and my device appeared. Updated device driver and fastboot driver. ADB devices still yields no device attached though.
haloux said:
Small breakthrough:
Used a diff cable like someone suggested and my device appeared. Updated device driver and fastboot driver. ADB devices still yields no device attached though.
Click to expand...
Click to collapse
if you are in fastboot mode (or bootloader) you should use the fastboot command and not the adb.
type: fastboot devices
any signs of life?
Tapatalk-kal küldve az én Nexus 5-el
bitdomo said:
if you are in fastboot mode (or bootloader) you should use the fastboot command and not the adb.
type: fastboot devices
any signs of life?
Tapatalk-kal küldve az én Nexus 5-el
Click to expand...
Click to collapse
Wow. It worked! The device showed up! Thank you guys.
haloux said:
Wow. It worked! The device showed up! Thank you guys.
Click to expand...
Click to collapse
Not sound like a turd but I mentioned using a nexus USB cable in post #7 after mentioning my issue.
Hello everyone,
I have done something utterly stupid with my Nexus 5, I wiped the internal storage and lost my roms, I really wasnt thinking.
I have tried looking at options like adb sideload but cant find a decent tutorial
Could I just get a micro usb to usb adapter and install a rom off that?
Would anyone be able to point me in the right direction with adb sideload?
Other problems are I can't get on the android SDK because the CMD box only flashes up.
Does the adb sideload option in TWRP actually do anything if you wait for it? Its been waiting for about 1 hour now and nothings happening.
Please guys any help is appreciated
osamarchie2000 said:
Hello everyone,
I have done something utterly stupid with my Nexus 5, I wiped the internal storage and lost my roms, I really wasnt thinking.
I have tried looking at options like adb sideload but cant find a decent tutorial
Could I just get a micro usb to usb adapter and install a rom off that?
Would anyone be able to point me in the right direction with adb sideload?
Other problems are I can't get on the android SDK because the CMD box only flashes up.
Does the adb sideload option in TWRP actually do anything if you wait for it? Its been waiting for about 1 hour now and nothings happening.
Please guys any help is appreciated
Click to expand...
Click to collapse
Why don't you flash the factory image using fastboot?
The Cmd box you are referring to happens because you need to navigate to that directory using Cmd and run it from there. You cannot just click it.
Thanks but I cant get the SDK to work at all. Im still looking into it but at the moment it wont work
Please somebody help me with the SDK, I dont know what else to do.
I cant open the SDK manager and I cant open it through eclipse either.
Someone else must have had this problem before
Click the link in my signature and then "adb and fastboot. What is it?"
This will help you configure adb properly. It also helps you learn commands. Like adb push.
adb sideload is the same as push but you type sideload instead.
FYI as much as people round here say it, there is no such thing as a soft brick. Its brick or not brick.
Sent from my Nexus 5 using Tapatalk < Yes, I want you to know that I'm using a mobile client
Switched off my phone and now I cant get it into recovery mode. Only the google logo which just stays there for ages
What do I do now?
osamarchie2000 said:
Switched off my phone and now I cant get it into recovery mode. Only the google logo which just stays there for ages
What do I do now?
Click to expand...
Click to collapse
Show down and don't panic. Your device is easily fixed. Hold the power button for 20 seconds. This will shut down the phone. Then press and hold the vol down then press the power button. That'll bring your into the bootloader.
Sent from my Nexus 5 using XDA Free mobile app
osamarchie2000 said:
Switched off my phone and now I cant get it into recovery mode. Only the google logo which just stays there for ages
What do I do now?
Click to expand...
Click to collapse
Power + volume down button brings you in the bootloader, from there go into recovery (navigate with volume buttons and select with power button)
In recovery follow this guide: http://forum.xda-developers.com/showthread.php?t=2559200.
Or flash the factory image in the bootloader. (that should work because you need to unlock your bootloader in fastboot)
Thanks guys,
It wasnt working because water damage had interfered with the volume buttons previously.
I have a micro usb to usb adapter now.
Can i put a rom on a USB drive and install that way?
Thanks guys
osamarchie2000 said:
Thanks guys,
It wasnt working because water damage had interfered with the volume buttons previously.
I have a micro usb to usb adapter now.
Can i put a rom on a USB drive and install that way?
Thanks guys
Click to expand...
Click to collapse
Yeah that will work too. Water damage is never good for a phone even if it stil works after that. But that's another story
osamarchie2000 said:
Thanks guys,
It wasnt working because water damage had interfered with the volume buttons previously.
I have a micro usb to usb adapter now.
Can i put a rom on a USB drive and install that way?
Thanks guys
Click to expand...
Click to collapse
Yes you can. You'll have to "tell" twrp where to find the rom zip.
Sent from my Nexus 5 using XDA Free mobile app
Only problem now is I cant get the SDK to work for my life. Ive spent 5 hours trying to fix my phone already today, I have the JDK installed. I open the eclipse thingy and when i try to open the SDK with eclipse it wont work either. Please somebody help with this
osamarchie2000 said:
Only problem now is I cant get the SDK to work for my life. Ive spent 5 hours trying to fix my phone already today, I have the JDK installed. I open the eclipse thingy and when i try to open the SDK with eclipse it wont work either. Please somebody help with this
Click to expand...
Click to collapse
You don't need the SDK. You're not developing here
Sent from my Nexus 5 using Tapatalk < Yes, I want you to know that I'm using a mobile client
TWRP cant find any of the files on my USB-OTG
with the CMD, it gives me my device and its serial number and says recovery for
C:\adb devices
but for C:\fastboot devices
I get nothing.
Any ideas please?
osamarchie2000 said:
with the CMD, it gives me my device and its serial number and says recovery for
C:\adb devices
but for C:\fastboot devices
I get nothing.
Any ideas please?
Click to expand...
Click to collapse
Did you read my thread that I told you to read?
Sent from my Nexus 5 using Tapatalk < Yes, I want you to know that I'm using a mobile client
osamarchie2000 said:
with the CMD, it gives me my device and its serial number and says recovery for
C:\adb devices
but for C:\fastboot devices
I get nothing.
Any ideas please?
Click to expand...
Click to collapse
Here's a hint, read rootSU's sticky rollup and look for the 15 second fastboot adb installer.
Sent from my Nexus 5 using XDA Free mobile app
Very sorry, Ive just re-read what Im looking for
Appologies
thankyou all, phone is well and good and im on CM11.
Thanks guys, anyone who helped is the best