Related
1. I've searched similar threads on the forum already.
2. I've used usbdeview to uninstall old drivers so as to eliminate any conflicts when installing the new ones.
3. I've tried this on both Win7 x64 as well as Vista x64 with the same results.
4. I don't care about clockwork recovery - the stock recovery is fine as as far as I can tell it makes no difference to the issue i'm having.
After checking the dozen or so guides on how to do this I first tried installing the usb drivers for the phone whilst in fastboot mode. This was impossible for me as no matter what combination I used to point the windows device driver installer to the google usb drivers, they simply would-not-install. What I did notice (though trial and error) was that those same drivers are not, in fact, used for fastboot mode, but for normal boot whilst the phone is in usb debugging mode. I.e. windows device driver installer was able to install the drivers in the folder. I then decided to go ahead anyway.
I launched the cmd (in admin mode) and navigated to the program files (x86) (so much for the 64bit sdk, GG Google lol)->android->android-sdk->platform-tools (the original tools folder is no longer the correct folder as Google moved the .dll's). I then tried to launch the various 'fastboot' commands necessary and hit another roadblock as the cmd prompt reports that 'fastboot' is not a valid command.
So there you have it, I can't install the drivers and can't execute and 'fastboot' commands. Anyone know how to root this phone using neither of those 2 components? *sigh*
Any help would be greatly appreciated.
P.S. For an added bit of irony, rooting a friends HTC HD was easier...
Fastboot is in the "tools" folder, not "platform-tools" and make sure you have copied over the .dll files into the "tools" folder or else it wont work.
The clockwork method is easy, and can be used without flashing the clockwork recovery image to the phone so you can root it and pretty much keep everything stock. The 'fastboot boot recovery.img' command boots the phone with the image, but it doesnt flash it.
The whole rooting process is really easy, it should only take a minute or two.
This guide h ttp://forum.xda-developers.com/showthread.php?t=935819 worked flawlessly for me a few times.
Thanks for the reply.
After installing the pdanet it asked me if i wanted to reinstall the usb drivers. I chose to do so because at this point, I had nothing to lose. After doing so and rebooting the phone into recovery mode, windows device manager no longer had a missing driver reported! Go figure.
I have thus been able to unlock my bootloader. However I have not been able to root my phone (to be honest i originally thought they were the same thing). The guide askes to flash the clockworkrecovery to the phone which would replace the stock recovery would it not? Is there any way to root the phone now that it's bootloader is unlocked without flashing the clockwork image?
There are usb drivers with the sdk but theyre in the 3rd party section for some reason.
The unlocked bootloader isnt necessary if you want to get root, but if you use the fastboot command i pasted above, nothing gets flashed, but the phone boots only once using the specified recovery.img. Nothing will get overwritten unless you use the 'flash' parameter as quite a few of the guides do. Make sure you have your su*.zip already copied onto your sdcard partition as this makes it easier.
mrbeardy said:
There are usb drivers with the sdk but theyre in the 3rd party section for some reason.
The unlocked bootloader isnt necessary if you want to get root, but if you use the fastboot command i pasted above, nothing gets flashed, but the phone boots only once using the specified recovery.img. Nothing will get overwritten unless you use the 'flash' parameter as quite a few of the guides do. Make sure you have your su*.zip already copied onto your sdcard partition as this makes it easier.
Click to expand...
Click to collapse
I think it doesn't matter if you do fastboot "flash" or "boot" because Nexus S was built with a safety system that replaces the custom recovery for the stock everytime you reboot. Correct me if i'm wrong
Rafael Cadina said:
I think it doesn't matter if you do fastboot "flash" or "boot" because Nexus S was built with a safety system that replaces the custom recovery for the stock everytime you reboot. Correct me if i'm wrong
Click to expand...
Click to collapse
fastboot boot only boots the recovery one time, fastboot flash flashes the recovery permanently to your phone(until you flash another). so yea, it makes a BIG difference.
I also had a difficult time rooting it because of the drivers. Once I found this thread right here http://forum.xda-developers.com/showthread.php?t=878786 the drivers worked instantly! Actually everything worked!
Hang on, so I don't need to unlock the bootloader to get perm root? (if so, how do I re-lock the bootloader?) Why do so many of the guides include this part then? What's the advantage of an unlocked botloader?
/confused.
EDIT: note that i'm running 2.3.3 if that makes any diff.
Ok, i'm I used this method (http://www.dkszone.net/root-nexus-s-android-2.3.3-gingerbread-google-samsung) to root the phone. I have confirmed this by downloading apps like adfree but when i use titanium backup is says it can't get root privileges even though the super user app is allowing it.
EDIT: I worked it out, turns out Titanium Back up needs something called 'busybox' (which wasn't the case on my previous installs on other phones). After installing it, it now works perfectly. No need for clockwork after all (not sure why i'd ever use it to be honest as I don't install custom roms but I still need root for other apps that i use).
Since upgrading to Windows 8 the toolkit for android and pretty much the drivers are impossible to get working.
It seems that the device has nothing on it, zip, zero. No matter how I try to recover it what ROM it tried to install it didn't work and when I try to access anything via command prompt it can not find the device.
I look at the devices on system manager and there is one listed as unknown device but I do have android phone listed as a device.
It plugs in, makes a sound knowing there is something but its unknown. Tried using the Samsung drivers, no luck there.
I need to do a complete reboot, get the original folders back on but don't know how to get it to recognise and get things going again.
jozkam said:
Since upgrading to Windows 8 the toolkit for android and pretty much the drivers are impossible to get working.
It seems that the device has nothing on it, zip, zero. No matter how I try to recover it what ROM it tried to install it didn't work and when I try to access anything via command prompt it can not find the device.
I look at the devices on system manager and there is one listed as unknown device but I do have android phone listed as a device.
It plugs in, makes a sound knowing there is something but its unknown. Tried using the Samsung drivers, no luck there.
I need to do a complete reboot, get the original folders back on but don't know how to get it to recognise and get things going again.
Click to expand...
Click to collapse
You need to disable driver signing in windows 8 to be able to install drivers for the Nexus.
Done this already, for some strange reason the device listed in Device manager now knows its a adb interface but still listed as a unknown device.
Try getting to look at the Samsung drivers but still no luck.
When you go into the device properties it states the following;-
Windows has stopped this device because it has reported problems. (Code 43)
Windows 8 doesn't seem to work very well with adb/fastboot etc...
Do you have access to another computer that has Windows 7 (or XP, Linux?)?
Thanks for you help guys so far.
I do have a Vista 32bit laptop that I can use. Going to install the Toolkit, drivers etc on there and see how far it goes.
jozkam said:
Thanks for you help guys so far.
I do have a Vista 32bit laptop that I can use. Going to install the Toolkit, drivers etc on there and see how far it goes.
Click to expand...
Click to collapse
I've read where people who are using Win8 and fastboot flashing .img files to get back to stock, it stops/locks up in varying spots...after three hours of messing with it they try another OS (Win7, Linux) and it works within minutes.
Hopefully, Vista works...and I'm sorry you have to resort to Vista!
Well I seen to be getting somewhere but still with strange issues in Device Manager.
It shows Android device with the following devices below.
- Android Composite ADB Interface (yellow exclamation mark)
- Google Nexus 7 ADB Interface (yellow exclamation mark)
- Google Nexus 7 ADB Interface (yellow exclamation mark)
- Google Nexus 7 ADB Interface (yellow exclamation mark)
- Google Nexus 7 ADB Interface (yellow exclamation mark)
- Google Nexus 7 ADB Interface (working properly)
- Google Nexus 7 BootLoader Interface (yellow exclamation mark)
Further down I have Portable Devices with MTP Device listed (yellow exclamation mark).
I have Google Nexus Toolkit installed.
jozkam said:
Well I seen to be getting somewhere but still with strange issues in Device Manager.
It shows Android device with the following devices below.
- Android Composite ADB Interface (yellow exclamation mark)
- Google Nexus 7 ADB Interface (yellow exclamation mark)
- Google Nexus 7 ADB Interface (yellow exclamation mark)
- Google Nexus 7 ADB Interface (yellow exclamation mark)
- Google Nexus 7 ADB Interface (yellow exclamation mark)
- Google Nexus 7 ADB Interface (working properly)
- Google Nexus 7 BootLoader Interface (yellow exclamation mark)
Further down I have Portable Devices with MTP Device listed (yellow exclamation mark).
I have Google Nexus Toolkit installed.
Click to expand...
Click to collapse
Is this from your Vista machine or Win8 machine now?
RMarkwald said:
Is this from your Vista machine or Win8 machine now?
Click to expand...
Click to collapse
Vista machine.
jozkam said:
Vista machine.
Click to expand...
Click to collapse
Strange. Did you install the USB drivers? Maybe download them from Asus, extract them to your Desktop, right click on your N7 in Device Manager and unistall the drivers for your device, then connect your N7 and browse to the location of the downloaded USB drivers....?
Okay following God knows how many windows updates, following restart I can see that the MTP device is now showing as working properly.
When running the toolkit (version 3.2) it shows the device number at the top under ADB mode but not under Fastboot mode.
RMarkwald said:
Strange. Did you install the USB drivers? Maybe download them from Asus, extract them to your Desktop, right click on your N7 in Device Manager and unistall the drivers for your device, then connect your N7 and browse to the location of the downloaded USB drivers....?
Click to expand...
Click to collapse
Remind me which USB drivers?
Okay, puzzling but it appears to be getting somewhere.
In device manager there is one instance of Google Nexus 7 ADB Interface under Android Device and MTP Device under Portable Devices even though it seems to reinstall the same instance of MTP device every 1 minute or so.
I am installing the Samsung drivers however, the same as before when it comes to the Toolkit. The ADB mode list of devices shows correctly, nothing underneath fastboot mode.
What would be the next stage?
I would boot into fastboot, change directory to your Android SDK - Platform Tools directory, and if you type: fastboot devices
does anything show up?
Well, I would reflash stock images completely. Hopefully you have a backup of whatever is/was on your internal sd card because doing this will erase it.
You can get the image from here (note, I am assuming you have the N7 Wifi Only): https://developers.google.com/android/nexus/images#nakasi
Then, you can revert to stock by following this post: http://rootzwiki.com/topic/28544-guide-nexus-7-bootloadersrecoveriesrootback-to-stock/#entry764332
NOTE: Step 10 the file name will be different than shown.
Ok so I have managed to get into the ClockworkMod recovery v6.0.1.9, going with the 'install zip from sideload', used the command adb sideload nakasi-jop40c-factory-6aabb391.tar.
The screen on nexus says:
Restarting adbd...
Finding update package...
E: Cant open /tmp/update.zip
(bad)
Installation aborted.
Sorry about this I am a complete amateur when it comes to this stuff, thanks for the help so far.
UPDATE: - I used the CLEANROM 2.5 zip file and it has now gone back to its original state, YES, thank you so much.
This may have happened when I started to use Paranoid Android, they brought out a beta 5 version, which originally worked but I can't see to get it updated via the 'update recovery' step.
http://forum.xda-developers.com/showthread.php?t=1800268
Thanks once again.
RMarkwald said:
I would boot into fastboot, change directory to your Android SDK - Platform Tools directory, and if you type: fastboot devices
does anything show up?
Well, I would reflash stock images completely. Hopefully you have a backup of whatever is/was on your internal sd card because doing this will erase it.
You can get the image from here (note, I am assuming you have the N7 Wifi Only): https://developers.google.com/android/nexus/images#nakasi
Then, you can revert to stock by following this post: http://rootzwiki.com/topic/28544-guide-nexus-7-bootloadersrecoveriesrootback-to-stock/#entry764332
NOTE: Step 10 the file name will be different than shown.
Click to expand...
Click to collapse
Steps done, back to stock which is great, thanks a lot.
Oh man just when I thought my problems were finished.
One thing I forgot to do was run the superuser zip file to give permissions on the clockworkmod recovery. Even trying to do something with Rom Manager within jellybean itself but it says I need permissions.
How can I reverse back and get the superuser.zip from working? At the moment I can not access recovery, tried using command prompts and Rom Manager but to no avail.
jozkam said:
Oh man just when I thought my problems were finished.
One thing I forgot to do was run the superuser zip file to give permissions on the clockworkmod recovery. Even trying to do something with Rom Manager within jellybean itself but it says I need permissions.
How can I reverse back and get the superuser.zip from working? At the moment I can not access recovery, tried using command prompts and Rom Manager but to no avail.
Click to expand...
Click to collapse
You can boot back into fastboot, and download the latest TWRP Recovery from here: http://teamw.in/project/twrp2/103
They even give you instructions on the command to run type in: fastboot flash recovery <name of recovery file>
Put the .img file in your Android SDK - Platform Tools folder as well.
Type in the flash recovery command, then reboot to recovery.
From there, you can flash the Superuser.zip (I assume you have it?). If not, here it is: http://download.chainfire.eu/282/SuperSU/CWM-SuperSU-v0.98.zip
You'll also want to make sure that the following files are deleted/removed:
/system/etc/install-recovery.sh
/system/recovery-from-boot.p
The reason being is that if they are there, it will reload the stock Android recovery at reboot, which will remove TWRP or CWM if you have flashed those. I would just rename them by putting a .bak on the end of the file names. But to do this, you'll need root first. You may have to: fastboot flash recovery, flash SuperSU zip, reboot, browse to those two locations to verify if those files exist/rename them, fastboot flash recovery again...reboot, and recovery may stick. When I went back to stock and fastboot flashed TWRP, I checked for those files and they weren't there, and recovery stuck just fine.
You're learning the manual way, congratulations! Not too bad is it?!
RMarkwald said:
You can boot back into fastboot, and download the latest TWRP Recovery from here: http://teamw.in/project/twrp2/103
They even give you instructions on the command to run type in: fastboot flash recovery <name of recovery file>
Put the .img file in your Android SDK - Platform Tools folder as well.
Type in the flash recovery command, then reboot to recovery.
From there, you can flash the Superuser.zip (I assume you have it?). If not, here it is: http://download.chainfire.eu/282/SuperSU/CWM-SuperSU-v0.98.zip
You'll also want to make sure that the following files are deleted/removed:
/system/etc/install-recovery.sh
/system/recovery-from-boot.p
The reason being is that if they are there, it will reload the stock Android recovery at reboot, which will remove TWRP or CWM if you have flashed those. I would just rename them by putting a .bak on the end of the file names. But to do this, you'll need root first. You may have to: fastboot flash recovery, flash SuperSU zip, reboot, browse to those two locations to verify if those files exist/rename them, fastboot flash recovery again...reboot, and recovery may stick. When I went back to stock and fastboot flashed TWRP, I checked for those files and they weren't there, and recovery stuck just fine.
You're learning the manual way, congratulations! Not too bad is it?!
Click to expand...
Click to collapse
Wouldn't have got this far without you, really appreciate your help, now its stable with 2.54 Paranoid Android.
:good:
After about 10 tries I still cant get this damn tablet to work with the toolkit. I screwed up while updating and lost root, now I cant get the root toolkit to recognize my device after installing the drivers on any pc (tried win two with 8 and two with 7). I have no clue what to do as I was able to unlock and root it initially but now I cant redo it to get my device back and in working order. This is driving me insane!!!!!!!!! I am using the most recent toolkit, and my tablet is on 4.2.2 unlocked but no longer rooted.
Another satisfied toolkit customer. Did you pay for the privilege? If yes, I suppose you should call their support department during normal business hours.
It's a little surprising. I can see that the behavior of ADB might have changed - when the regular OS is booted. (This is a new security feature of 4.2.2 adb - you need the latest SDK version of the "adb" program)
And if you used the OTA, then the custom recovery was replaced by the 4.2.2 stock recovery, so ADB won't even show up there (stock recoveries don't run the "adbd" daemon).
But I would think that you should be able to use fastboot, even if the bootloader was also upgraded.
So, a couple of questions.
A) Can you get the tab into bootloader mode?
B) Does it show version 4.18 on that screen?
C) Does the recovery appear to have been replaced by a stock recovery?
D) Does your PC (pick one and stick with it) show an Unknown Device, or something else when you plug the tab in whilst it is in bootloader/fastboot mode?
E) From the command line, what happens when you run "fastboot devices" either from the command line or from the toolkit when the device is plugged to the PC and in bootloader/fastboot mode?
Thanks for the fast reply. First of I thought the toolkit was free, since it is posted in many forums and you can download it right from the developers site. Next, I did use the OTA like a moron because I forgot that this was my unlocked and rooted nexus. Now to your questions:
A: I can get it into bootloader
B: The version is 4.18
C: The recovery only shows up with the droid dude and a red !
D: On my Win8 Desktop it shows up under Andriod Phone as 'Android ADB Interface' in device manager
E: in the comand line I get the serial of my tablet
lamboboy732 said:
Thanks for the fast reply. First of I thought the toolkit was free, since it is posted in many forums and you can download it right from the developers site. Next, I did use the OTA like a moron because I forgot that this was my unlocked and rooted nexus. Now to your questions:
A: I can get it into bootloader
B: The version is 4.18
C: The recovery only shows up with the droid dude and a red !
D: On my Win8 Desktop it shows up under Andriod Phone as 'Android ADB Interface' in device manager
E: in the comand line I get the serial of my tablet
Click to expand...
Click to collapse
This
>> E: in the comand line I get the serial of my tablet
is good.
the droid dude is the stock recovery. It actually sounds to me like the OTA succeeded for you - as you are showing both stock recovery and the 4.18 bootloader.
With the tablet in fastboot mode, just flash a custom recovery and you are good to go. You can either use "fastboot flash recovery name-of-recovery-image-file.img", or the equivalent operation in the toolkit.
Then, boot into recovery, and see if
A) the custom recovery appears correctly, and
B) if ADB now shows up either via command line or the toolkit (with the device in custom recovery).
If you got your adb & fastboot tools via installation of the Android SDK, make sure it is updated to the latest version
adb version
should report something like 1.0.31 (iirc)
good luck
Hello,
I just got the OTA message for 4.4 and tried to install it but I got a bootloop. After clearing the cache and performing a factory reset in TWRP (which got installed through Nexus Toolkit) it still didn't work. Someone told me to perform a complete format through TWRP which I did (hindsight, I know) and now TWRP says I have no OS installed, adb won't see my device (I have the drivers installed) and when I go into the bootloader (which says FASTBOOT MODE) fastboot still won't recognize the device (nothing shows up on my PC either but that can be normal).
I'm at my wit's end here, is there anyone who can help me?
You need to realize that if you want to install OTA, you need to use stock recovery. Even though it is possible to flash through TWRP, it can still run into problems. Especially when you made root modifications to your device.
You don't have to do a full wipe for everything. There is a method to flash factory firmware without wiping data (link in my signature). After that if it still don't boot due to existing data, boot into a custom recovery and do a factory reset without wiping the internal storage.
But since you have custom recovery already, just go into the Development section, find a stock KitKat rom, download it and sideload it using TWRP (which is enabled it in the Advance menu).
eksasol said:
You need to realize that if you want to install OTA, you need to use stock recovery. Even though it is possible to flash through TWRP, it can still run into problems. Especially when you made root modifications to your device.
You don't have to do a full wipe for everything. There is a method to flash factory firmware without wiping data (link in my signature).
But since you have custom recovery already, just go into the Development section, find a stock KitKat rom, download it and sideload it using TWRP (which is enabled it in the Advance menu).
Click to expand...
Click to collapse
Yes I've tried that but I don't know how to sideload it. adb doesn't see my device, fastboot doesn't either and windows doesn't recognize the device (although I have the adb naked drivers installed).
fverswijver said:
Yes I've tried that but I don't know how to sideload it. adb doesn't see my device, fastboot doesn't either and windows doesn't recognize the device (although I have the adb naked drivers installed).
Click to expand...
Click to collapse
If it is connected adb should see your device while in TWRP. Fastboot only work in fastboot mode (bootloader screen), not in recoveries. If you have the UND installed then they both should work, if not it wasn't installed correctly. If you are using Windows 8 you need to disable driver signature before you can install UND (search google for that).
You could also make a bootable Ubuntu flashdrive, and use the ADB/Fastboot for Ubuntu link in my signature to install them.
eksasol said:
If it is connected adb should see your device while in TWRP. Fastboot only work in fastboot mode (bootloader screen)
Click to expand...
Click to collapse
I tried both. ADB devices gives me an empty line and fastboot devices (when in bootloader screen) gives me nothing at all. I've tested 2 different computers (both windows 7 x64) and it still won't detect it. When in TWRP windows tries to detect my device but it says "Unknown Device" and gives the yellow triangle.
fverswijver said:
Yes I've tried that but I don't know how to sideload it. adb doesn't see my device, fastboot doesn't either and windows doesn't recognize the device (although I have the adb naked drivers installed).
Click to expand...
Click to collapse
You might have to point the drivers to your phone. If you go into device manager, see if your Nexus 4 has an error. If it does, right click it, and then update the driver. Do a manual install, and point it to the .ini file for the driver
fverswijver said:
I tried both. ADB devices gives me an empty line and fastboot devices (when in bootloader screen) gives me nothing at all. I've tested 2 different computers (both windows 7 x64) and it still won't detect it. When in TWRP windows tries to detect my device but it says "Unknown Device" and gives the yellow triangle.
Click to expand...
Click to collapse
Fix your drivers, uninstall them and select the checkbox to delete the driver files, search Google on how to disable driver signature and try reinstalling the driver again.
or
Make a bootable Ubuntu flashdrive, and use the ADB/Fastboot for Ubuntu link in my signature to install them.
eksasol said:
Make a bootable Ubuntu flashdrive, and use the ADB/Fastboot for Ubuntu link in my signature to install them.
Click to expand...
Click to collapse
I did this and still the same, adb gives an empty list and fastboot gives nothing.
fverswijver said:
I did this and still the same, adb gives an empty list and fastboot gives nothing.
Click to expand...
Click to collapse
Try using a different cable and on different computers.
eksasol said:
Try using a different cable and on different computers.
Click to expand...
Click to collapse
I've tried 3 different computers, 2 different OSes and 3 different cables. Nothing seems to work. I'm really starting to panic now.
fverswijver said:
I've tried 3 different computers, 2 different OSes and 3 different cables. Nothing seems to work. I'm really starting to panic now.
Click to expand...
Click to collapse
Just to clarify, see attachment for the correct name of the device if UND is installed correctly.
If you tried it with Ubuntu, make sure you do the 1st step from here also:
http://bernaerts.dyndns.org/linux/74-ubuntu/245-ubuntu-precise-install-android-sdk
Same here
i installed the ota update normally with twrp installed everything went fine but im kind of disappointed in this update:/
eksasol said:
Just to clarify, see attachment for the correct name of the device if UND is installed correctly.
Click to expand...
Click to collapse
These are my findings:
Ubuntu:
- Bootloader (fastboot)
-- running lsusb in Ubuntu shows no device
- TWRP (adb)
-- running lsusb shows no device
Windows 7 (3 different computers)
- Bootloader (fastboot)
-- Windows gives the following popup, no device listed in Device Manager
- TWRP (adb)
-- Windows gives the same popup as on fastboot and this appears in the Device Manager:
fverswijver said:
These are my findings:
Ubuntu:
- Bootloader (fastboot)
-- running lsusb in Ubuntu shows no device
- TWRP (adb)
-- running lsusb shows no device
Windows 7 (3 different computers)
- Bootloader (fastboot)
-- Windows gives the following popup, no device listed in Device Manager
- TWRP (adb)
-- Windows gives the same popup as on fastboot and this appears in the Device Manager:
Click to expand...
Click to collapse
Is file transfering working atleast? If it is, then it's a software problem. If it isn't, then it could be a hardware problem, you can try replacing the USB charging board for the phone. Also some roms with corrupt files can cause this issues, so try a different roms if you haven't.
File transfer used to work but atm I'm unable to even connect it to a computer so I can't actually transfer any files. If I could I would flash a rom but no files = no flashing.
fverswijver said:
File transfer used to work but atm I'm unable to even connect it to a computer so I can't actually transfer any files. If I could I would flash a rom but no files = no flashing.
Click to expand...
Click to collapse
Get one of these: http://www.ebay.com/sch/i.html?_nkw=nexus+4+usb+charging+port+replacement&_sacat=0
If it don't work, then use the phone as a door stopper.
hey guys, I'm having the same problem here but with a Nexus 5 now.
Its been over a month and I've kind of gave up over the situation.
I couldn't resist to write a comment on the thread, since it appears to be the same problem as mine.
long story short, I decided to order an USB charging port to replace the one on the phone (as my last attempt).
Otherwise I will consider using the device as a door stopper.
Do not despair! Check this out: http://highonandroid.com/android-ro...r-android-in-a-bootloop-with-no-os-using-adb/
http://highonandroid.com/android-roms/how-to-copy-files-over-to-your-android-in-a-bootloop-with-no-os-using-adb/
i installed nokia xl rom into my device un fortunately i wipe the os and later i copy a rom file into my sd card and tried to flash tjat but it showing unable to open the zip. iam stuck with my company logo on the screen. twrp cannot open the zip and flash the rom. please help me in this issue.
thanks in advance
Don't ask me how this came about but I currently do not have a recovery on my phone.
The phone was running a rooted version of android 4.4.4 (paranoid android I think I had) and when android 5.0 came out I decided to flash it to my phone manually, to do this I used the tools available in android root tool kit. I think I messed it up a bit however as I have no recovery image on the phone.
I am now bored of running stock and want to flash a cyanogenmod ROM onto the phone - hence why I now need a recovery.
I can get my pc to recognise that a fastboot device is connected, but when I try the fastboot flash recovery <recovery.img> command it returns "could not load file". Even though the file is there in the path specified - I'd downloaded CWM recovery.
So I am not sure what I should do, can anyone help me?
I do not have my OEM cable and cannot get the PC to recognise an ADB device is connected, so a solution that gets round this problem would be useful. I'd rather not have to spend money on a new USB cable just for this purpose.
Thanks.
fredcorp6 said:
Don't ask me how this came about but I currently do not have a recovery on my phone.
The phone was running a rooted version of android 4.4.4 (paranoid android I think I had) and when android 5.0 came out I decided to flash it to my phone manually, to do this I used the tools available in android root tool kit. I think I messed it up a bit however as I have no recovery image on the phone.
I am now bored of running stock and want to flash a cyanogenmod ROM onto the phone - hence why I now need a recovery.
I can get my pc to recognise that a fastboot device is connected, but when I try the fastboot flash recovery <recovery.img> command it returns "could not load file". Even though the file is there in the path specified - I'd downloaded CWM recovery.
So I am not sure what I should do, can anyone help me?
I do not have my OEM cable and cannot get the PC to recognise an ADB device is connected, so a solution that gets round this problem would be useful. I'd rather not have to spend money on a new USB cable just for this purpose.
Thanks.
Click to expand...
Click to collapse
I would highly recommend Wug's Nexus Root Toolkit. It can automate any process you need. From what it sounds like it your post, you need to re-install TWRP. With the Nexus Root Toolkit, you can find that option under the "Root" section. Just check the box "Custom Recovery" and press the big "Root" button. Everything is very easy with this program. One thing I would recommend is that you get a very good USB to Micro USB to do this with. That is always the first point of failure in my experience. Good luck!