[Q] Another way to push root? - Droid RAZR M Q&A, Help & Troubleshooting

I have taken the OTA to KK. I have read how to fastboot the CWM recovery file to get the custom recovery to then flash the SuperSU file. I still can't get my Windows 7 Home Premium 64-bit to recognize my phone to ADB. Here is what I have done so far: (this is not an order what I have done, just steps I did in general)
1. Downloaded an ADB package file I found in another topic/thread on XDA that had everything built in to get adb to work including the 64 bit driver from google. This didn't work.
2. Downloaded the newest Motorola drivers from their website.
3. Downloaded the Universal ADB USB driver files from Koush's website. Still didn't work.
4. Found a thread on XDA that says to download the older Motorola drivers as the new ones from Motorola suck. I did that, still nothing.
I boot my phone into AP Fastboot, and connect the USB cable. It says on the phone that I'm connected. I have made sure USB debugging was checked. In Device Manager, it says MOT ADB interface when I have the phone connected. When I try "adb devices", nothing pops up. I try "adb reboot bootloader", says error: device not found. I made sure to install the ADB installers as an Administrator. Any other way to push the recovery file to the phone?
Thanks for any help!

I also searched and tried to install PDAnet for the adb drivers and that didn't work either
Sent from my XT907 using XDA Free mobile app

Anyone?
Sent from my XT907 using XDA Free mobile app

I had the same problem with the drivers after updating to 4.4.2. This is what I did to solve the problem.
1. Uninstall all Motorola drivers and Device Manager
2. Reboot PC
3. Install Motorola Device Manger (Latest Version)
4. Connect Phone and let Device Manager re-install the drivers

turns out i didn't need to use the command "adb reboot bootloader". i just did the fastboot command and it flashed instantly. Never knew why I didn't try that in the first place.../thread closed

Related

It is impossible to root my Nexus 4!!!

HI everyone, I really do need your help here to root my Nexus 4 !!!
Following instruction in this Ultimate Nexus 4 Root Guid, I am able to install ADB to my sytem, after checking that it recognizes my devices, I proceed to boot to Nexus 4 screen boot by command "adb reboot bootloader", but when trying to proceed with "fastboot oem unlock", it keep saying "device is waiting" or "failed" . The instruction says :
If your Command Prompt displays the message "waiting for device" your driver wasn't successfully installed.
Close the Command Prompt window and open Device manager while your phone is still plugged in. (Search for it using the search option).
Right Click the "Android" option and select Update Driver. Choose to "Browse My Computer" and "Let Me Pick From A List." Pick the Driver with the newest date and install it. Now retry the code above.
I just dont get what is newest date driver ?? please tell me what to do next ....
I also try with "naked driver" bt it does not work out ...
Did you reboot your computer twice? Basically you have to install a driver for ADB debugging while the phone is on, and a driver for the thing while the phone is off. Each time you have time reboot the computer.
Reboot to bootloader, plug phone to computer, check Device Manager if ADB Debugging Interface (or something similar) is there.
If there is, check driver using this command
adb devices
Click to expand...
Click to collapse
If no device show up, update your drive, reboot computer than try again. If it still doesn't work, try another driver.
Go into the folder with ADB in it. My bet is you don't have the fastboot files installed. You can Google for them and just move it to your folder with ADB after you download it.
Sent from my Nexus 4 using Tapatalk 2
The toolkit worked for me. Option 8.
http://forum.xda-developers.com/showthread.php?t=1995688
Try using one of the toolkits to install the correct drivers

[Q] Nexus 4 factory rom deleted

Good day guys,
I need a help with my nexus 4, I had a rooted rom in my nexus 4 with clockwork mode recovery, I tried to wipe my data through clockwork mode but by mistake I did system wipe. Now there is no rom in the device, I can only access to fastboot mode and clockwork recovery mode, also I tried to install rom through toolkit but my PC & Mac doesn't read any device connected and no device shown in device manger in my windows 7 with using different usb cables and ports. I installed samsung drivers and adb drivers but still I cannot see the device in device manager.
Please if any body can help me to install rom back to my device.:crying:
alhawi6 said:
Good day guys,
I need a help with my nexus 4, I had a rooted rom in my nexus 4 with clockwork mode recovery, I tried to wipe my data through clockwork mode but by mistake I did system wipe. Now there is no rom in the device, I can only access to fastboot mode and clockwork recovery mode, also I tried to install rom through toolkit but my PC & Mac doesn't read any device connected and no device shown in device manger in my windows 7 with using different usb cables and ports. I installed samsung drivers and adb drivers but still I cannot see the device in device manager.
Please if any body can help me to install rom back to my device.:crying:
Click to expand...
Click to collapse
In cwm there should be an option to mount the device as usb storage. Try that. It should let you plug the phone into the pc and simply copy the zip onto the phones internal sd.
If thats not working try this to set up the drivers. Then plug the phone in and boot into the bootloader/fastboot mode. The open command prompt and cd to the android-sdk/platform-tools directory. Then run the following command:
Code:
adb push /path/to/rom/on/pc/ /mnt/sdcard/
still not working
Still not connected to windows, I cannot do any thing with my device
Download any ROM and do the following:
1. Connect phone to PC when in fastboot
2. Install drivers (if required)
3. Flash latest version of CWM using fastboot flash recovery name_of_recovery.img
4. Reboot phone into fastboot using fastboot reboot-bootloader
5. Boot into CWM
6. Install drivers (if required)
7. Select 'Install via sideload'
8. Flash ROM using adb sideload name_of_rom.zip
9. Follow instructions in CWM
If that still doesn't work, go back to stock using this guide (and read ALL of it):
http://forum.xda-developers.com/showthread.php?t=2010312
EddyOS said:
Download any ROM and do the following:
1. Connect phone to PC when in fastboot
2. Install drivers (if required)
3. Flash latest version of CWM using fastboot flash recovery name_of_recovery.img
4. Reboot phone into fastboot using fastboot reboot-bootloader
5. Boot into CWM
6. Install drivers (if required)
7. Select 'Install via sideload'
8. Flash ROM using adb sideload name_of_rom.zip
9. Follow instructions in CWM
If that still doesn't work, go back to stock using this guide (and read ALL of it):
http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
Thank you for your quick replay
My problem now that I cannot connect my device to PC, I installed drivers every thing and when I open fast boot or recovery mode and plug the cable, nothing indicates on my PC that there is a device connected even device manager not showing any device connected... I am stuck now, I cannot install any rom to get phone life back.
don't worry! the biggest problem would be that you had no drivers installed!
nexus are super easy to recover and you can play with them safely (except if you flash wrongs kernels from other devices haha)
do what my mate gets up in the post! and it will fixed it.
alhawi6 said:
Thank you for your quick replay
My problem now that I cannot connect my device to PC, I installed drivers every thing and when I open fast boot or recovery mode and plug the cable, nothing indicates on my PC that there is a device connected even device manager not showing any device connected... I am stuck now, I cannot install any rom to get phone life back.
Click to expand...
Click to collapse
It's not that it's not showing, it might already be installed correctly. When you have the Nexus 4 connect in fastboot it will show in Device Manager as 'Android Bootloader Interface' under the heading of 'Android Phone (see attached)
alhawi6 said:
Thank you for your quick replay
My problem now that I cannot connect my device to PC, I installed drivers every thing and when I open fast boot or recovery mode and plug the cable, nothing indicates on my PC that there is a device connected even device manager not showing any device connected... I am stuck now, I cannot install any rom to get phone life back.
Click to expand...
Click to collapse
Try with a different USB cable also could be your USB port on your computer
Sent from my Nexus 4
spaceman860 said:
Try with a different USB cable also could be your USB port on your computer
Sent from my Nexus 4
Click to expand...
Click to collapse
It seems that it will never works. I tried all the recommendations given but still device not detected by PC.
same problem for me.. help me
alhawi6 said:
Good day guys,
I need a help with my nexus 4, I had a rooted rom in my nexus 4 with clockwork mode recovery, I tried to wipe my data through clockwork mode but by mistake I did system wipe. Now there is no rom in the device, I can only access to fastboot mode and clockwork recovery mode, also I tried to install rom through toolkit but my PC & Mac doesn't read any device connected and no device shown in device manger in my windows 7 with using different usb cables and ports. I installed samsung drivers and adb drivers but still I cannot see the device in device manager.
Please if any body can help me to install rom back to my device.:crying:
Click to expand...
Click to collapse
i've the same problem in my nexus 4.. Could u recover from that?

Lg g2 Boot loops

I am not sure if I can post this solution in this thread as I am not a developer and merely sharing my experience, It seems several people are having issues with bootloops after installing att update or for some other reason, my post deals with helping only a certain issue. You should be able to boot into recovery by any means in order to use my solution.
The problem I had was I was trying to flash a new Rom and copied Rom and gapps into my phone( of course I was rooted and had recovery flashed) and then out of curiosity I wiped everything in advanced wipe in twrp so now I have no Rom to boot into or no file to flash and either download mode would not work, I was p******g in my shorts as I my phone was only a week old and its dead that's what I at least thought. And after spending the whole night no solution was found in xda website and neither did Google help any, now the solution. now u should compare this to ur problem and find where u stand. I installed pdanet on my pc as stock lg drivers don't seem to help pc recognize my phone in recovery mode, then I plugged my phone to pc while phone is still in recovery mode and then opened pdanet in pc and installed lg drivers through it and then adb was able to see my device(until now I was trying adb sideload and it wasn't working) so when adb was able to see my device, I used sideload in twrp and pushed Rom from pc to phone using sideload commands and my phone was back and I am the happiest man in the world. So in short
1. This method works only for people who can boot into twrp recovery but not into phone.
2. Have ur desired roms and gapps ready 3. Make sure u have a working adb in ur pc and if not install minimal adb and fastboot application only onto ur desktop for easy access, and copy ur desired Rom and gapps into that folder and rename them to 1.zip and 2.zip for easy reference and easy adb commands.
4. Download and install pdanet on your pc. Power on ur device into recovery and plug it into your pc. Start adb from the folder u installed on your desktop(hold shift and right click within the folder(minimal adb and fastboot) and click on start command here option, command opens up and it will show in which folder ur in and then type adb devices and if everything is right your phone in sideload mode should show up as adb sideload and if not (this is where the problem is) run pdanet and install lg drivers through it and then unplug exit sideload and restart sideload in ur phone and plug it back to pc and ur pdanet will notify u have connected ur lg phone. Then run adb again and type adb devices and it will show up as adb sideload and now (you should search how to use sideload as I don't remember those commands) and push Rom into (the ones u renamed for easy access and reboot and all should be all. Sorry for the lengthy post but I typed this solution into several posts individually and so decided to put it up as sticky and if anyone feels to remove part of or all the post I have no problem, just wanted to do my help to others with similar problem.
Sent from my LG-D800 using xda app-developers app
lingarajug said:
I am not sure if I can post this solution in this thread as I am not a developer and merely sharing my experience, It seems several people are having issues with bootloops after installing att update or for some other reason, my post deals with helping only a certain issue. You should be able to boot into recovery by any means in order to use my solution.
The problem I had was I was trying to flash a new Rom and copied Rom and gapps into my phone( of course I was rooted and had recovery flashed) and then out of curiosity I wiped everything in advanced wipe in twrp so now I have no Rom to boot into or no file to flash and either download mode would not work, I was p******g in my shorts as I my phone was only a week old and its dead that's what I at least thought. And after spending the whole night no solution was found in xda website and neither did Google help any, now the solution. now u should compare this to ur problem and find where u stand. I installed pdanet on my pc as stock lg drivers don't seem to help pc recognize my phone in recovery mode, then I plugged my phone to pc while phone is still in recovery mode and then opened pdanet in pc and installed lg drivers through it and then adb was able to see my device(until now I was trying adb sideload and it wasn't working) so when adb was able to see my device, I used sideload in twrp and pushed Rom from pc to phone using sideload commands and my phone was back and I am the happiest man in the world. So in short
1. This method works only for people who can boot into twrp recovery but not into phone.
2. Have ur desired roms and gapps ready 3. Make sure u have a working adb in ur pc and if not install minimal adb and fastboot application only onto ur desktop for easy access, and copy ur desired Rom and gapps into that folder and rename them to 1.zip and 2.zip for easy reference and easy adb commands.
4. Download and install pdanet on your pc. Power on ur device into recovery and plug it into your pc. Start adb from the folder u installed on your desktop(hold shift and right click within the folder(minimal adb and fastboot) and click on start command here option, command opens up and it will show in which folder ur in and then type adb devices and if everything is right your phone in sideload mode should show up as adb sideload and if not (this is where the problem is) run pdanet and install lg drivers through it and then unplug exit sideload and restart sideload in ur phone and plug it back to pc and ur pdanet will notify u have connected ur lg phone. Then run adb again and type adb devices and it will show up as adb sideload and now (you should search how to use sideload as I don't remember those commands) and push Rom into (the ones u renamed for easy access and reboot and all should be all. Sorry for the lengthy post but I typed this solution into several posts individually and so decided to put it up as sticky and if anyone feels to remove part of or all the post I have no problem, just wanted to do my help to others with similar problem.
Sent from my LG-D800 using xda app-developers app
Click to expand...
Click to collapse
I have more or less the same issue. Was with StockMod for D802 and received an official OTA and accepted and installed it. Now I'm stuck in bootloop. Unlike you, I can go into recovery (CWM not TWRP) BUT I can't seem to go into fastboot mode. When I hold the Volume Up and connect the phone through cable to my laptop, the phone boots but goes automatically into recovery mode. Did system wipe as well (which I shouldn't have) and at that point my phone has no OS to boot into so I used ADB to transfer CM 10.2 and GAPPS to my phone hoping that if I do it like I'm flashing a custom rom will help but unfortunately it didn't. I'm still stuck in bootloop and can't go into fastboot. help please...:crying:
Try a stock Rom and see if it helps.
Sent from my LG-D800 using xda app-developers app

Windows 10 laptop can't detect softbricked Nexus 4, TWRP, no OS

I've checked other threads but other similar threads were able to get the phone detected in Device Manager so...
I went to factory reset my old Nexus 4 after using it whilst my LG G4 was being repaired. Instead of wiping the data, I accidentally wiped the entire phone, OS included. I wasn't paying attention to what i was doing due to working at the same time and as a result the phone now only boots into TWRP and fastboot mode, but nothing else.
I tried to connect it to my windows 10 laptop so I could flash a new ROM but my laptop can't find the nexus 4 at all. Not when in recovery or when in fastboot.
Opening device manager shows that it is not there at all. There is no ACER usb device driver, nothing that resembles the nexus 4 at all. I've attached an image showing what device manager shows when the nexus 4 is connected and in recovery mode.
As you can see, there are no drivers I can uninstall. I have installed the google USB drivers from Android SDK manager. Still doesn't show. ADB doesn't work either.
I have tried multiple USB cables and every USB port. The phone charges when using an AC adaptor and charges when connected to the laptop. I can't try a different computer because I do not have access to one. Frankly I'm at a loss as to what to do.
When my nexus 4 was previously unable to connect I was able to see the device and just had to uninstall/reinstall/update drivers to get it working. This time, I can't seem to do anything. My LG G4 connects fine and without issue.
Anyone able to help?
The only way to really tell if it is a software or hardware issue would be to try another computer with Win7.
You may be able to flash a custom ROM with a OTG drive as well.
I had the same problem. When using adb and fastboot I get errors about like "error: device '(null)' not found".
Youtube video with id t0pV2pSw2N0 (sorry I am not yet allowed to post external urls) was helpfull and now I can see Android Composite ADB Interface again in the device manager. I still can not use commands adb and fastboot with exception of adb sideload. Unfortunately I have not yet succeeded to flash an image succesfully with sideload.
first try 2 remove any current drivers that are installed.
then u should experiment with different drivers.
the SkipSoft ToolKit have a huge selection, try each one of them (one of them should work).
begin with the ULTIMATE drivers and Adb/Fastboot Installer and if it don't work use the toolkit drivers.
https://skipsoft.net/download-page/
For me it turned out that MTP was enabled by default. After each restart MTP was enabled again. Now I have disabled MTP and my device is found by normal adb command.
Steps:
1) Start your device in twrp recovery mode
2) In main menu go to mount and tap "Disable MTP"
3) In main menu go to advanced -> adb sideload. Wipe caches and slide to start sideload
4) On your pc go to the command shell
5) Start "adb sideload <image_name.zip>" (replace image_name.zip with a valid image). It does not matter whether this fails or succeeds. Only thing important is that adb connects to your device.
6) Start "adb shell getprop persist.sys.usb.config". As result you will see the actual setting of the USB configuration your device when starting up. In my case it responded with "mtp,adb".
7) Start "adb shell setprop persist.sys.usb.config adb" to enable only "adb" configuration
8) Repeat step 6 to check result
9) Restart your device in recovery mode
10) Start "adb devices" to check if your device is now listed.
i_need_some_help said:
For me it turned out that MTP was enabled by default. After each restart MTP was enabled again. Now I have disabled MTP and my device is found by normal adb command.
Steps:
1) Start your device in twrp recovery mode
2) In main menu go to mount and tap "Disable MTP"
3) In main menu go to advanced -> adb sideload. Wipe caches and slide to start sideload
4) On your pc go to the command shell
5) Start "adb sideload <image_name.zip>" (replace image_name.zip with a valid image). It does not matter whether this fails or succeeds. Only thing important is that adb connects to your device.
6) Start "adb shell getprop persist.sys.usb.config". As result you will see the actual setting of the USB configuration your device when starting up. In my case it responded with "mtp,adb".
7) Start "adb shell setprop persist.sys.usb.config adb" to enable only "adb" configuration
8) Repeat step 6 to check result
9) Restart your device in recovery mode
10) Start "adb devices" to check if your device is now listed.
Click to expand...
Click to collapse
Thanks, I will give this a try!
elad.g said:
first try 2 remove any current drivers that are installed.
then u should experiment with different drivers.
the SkipSoft ToolKit have a huge selection, try each one of them (one of them should work).
begin with the ULTIMATE drivers and Adb/Fastboot Installer and if it don't work use the toolkit drivers.
https://skipsoft.net/download-page/
Click to expand...
Click to collapse
I tried removing all USB drivers and then using the toolkit and tried installing each driver. None of them allowed my PC to detect the nexus 4. As you can see in the attachment, nothing in device manager remotely resembling my nexus 4. This is after uninstalling and reinstalling and also updateing the LG G4 drivers (it makes no difference).
i_need_some_help said:
I had the same problem. When using adb and fastboot I get errors about like "error: device '(null)' not found".
Youtube video with id t0pV2pSw2N0 (sorry I am not yet allowed to post external urls) was helpfull and now I can see Android Composite ADB Interface again in the device manager. I still can not use commands adb and fastboot with exception of adb sideload. Unfortunately I have not yet succeeded to flash an image succesfully with sideload.
Click to expand...
Click to collapse
Alas, this did not work.
audit13 said:
The only way to really tell if it is a software or hardware issue would be to try another computer with Win7.
You may be able to flash a custom ROM with a OTG drive as well.
Click to expand...
Click to collapse
Unfortunately I don't have access to any other PC for this purpose. I can't connect download software or connect USB devices to the PCs at work due to security. I tried an OTG drive but TWRP wouldn't let me mount it, apparently OTG is not enabled by default for the nexus 4.
I've tried all 3 USB ports, several different cables but no luck. I guess that's it for this nexus 4 then?
If the phone is not booted into its ROM, ADB commands won't work. You need to use "fastboot devices" with the phone in bootloader mode.
You android device will reboot in several different boot modes (fastboot, recovery, normal). For each of these boot modes a separate device drive might be installed on your Windows. So check the device drive after each change of boot mode. If needed uninstall and reinstall the correct device driver.

system deleted, TWRP ready

Hello,
i delete the System and Data on my LeEco Le Pro3.
TWRP is installed.
Can i flash a rom with an usb flash drive in TWRP or fastboot?
greeting gizez
Boot into TWRP and use MTP to transfer ROM file from your PC to Phone. Then flash the ROM.
I have this problem, but I can't see the phone when connected to a PC. adb sideload doesn't work (adb devices doesn't find anything). Do I need to install driver for the phone? I originally used fastboot to unlock the bootloader and flashed TWRP, then installed LineageOS and gapps just fine. I then proceeded to wipe system in TWRP (I was trying to get back to new phone setup so I can transfer stuff from old phone, which I skipped the first time).
Any idea how to get around this? I tried plugging in pen drive through an micro USB OTG and a usb-c to micro usb adapter, but it's not recognized in TWRP, either. Would very much appreciate any help!
You can get your data. First try to connect phone while is in TWRP. Your phone can be detected as file manager. Try this.
If not, check my theme;
https://forum.xda-developers.com/le-pro3/help/brick-t3609704
marik1 said:
[...]
Go Advanced -> ADB Sideload, type "adb sideload aicp_zl1_n-12.1-NIGHTLY-20170516.zip" (zip of OS should be downloaded and put into "Minimal ADB and Fastboot" installation folder with name as same as the text of command). It should let you turn on system.
[...]
Click to expand...
Click to collapse
Also "adb push" command can be helpful. Sometimes phone is not current on adb devices list, but you can also try. As i remember, target should be /sdcard/0
marik1 said:
You can get your data. First try to connect phone while is in TWRP. Your phone can be detected as file manager. Try this.
If not, check my theme;
https://forum.xda-developers.com/le-pro3/help/brick-t3609704
Also "adb push" command can be helpful. Sometimes phone is not current on adb devices list, but you can also try. As i remember, target should be /sdcard/0
Click to expand...
Click to collapse
Thanks, but unfortunately no luck. Both adb sideload and adb push said error - device '(null)' not found. It seems like the PC is not recognizing the phone. I checked device manager on the PC, it showed LEX727. I right-click and had it install the driver. It says driver successfully installed. Then device manager showed MTP device with a !. I again tried having driver installed, but this time it doesn't find any driver.
I'm at my wit's end... Any more suggestion?
TWRP and/or Minimal ADB isn't trouble here? Tried you both on main menu of TWRP and in ADB Sideload mode? You can also try do it trough bootloader, for this check my link and read all.
marik1 said:
TWRP and/or Minimal ADB isn't trouble here? Tried you both on main menu of TWRP and in ADB Sideload mode? You can also try do it trough bootloader, for this check my link and read all.
Click to expand...
Click to collapse
Actually, the problem is solved, by using another PC. This one showed LEX727 in windows explorer as soon as i plug in the phonr (in twrp). I was able to drag and drop the zip files to the phone and go on my merry way. Now back in business!

Categories

Resources