Database Users

My pc doesnt recognizes my nexus 4

Hello yesterday i wiped everything on my phone by a mistake.Then i plugged it to my pc but it didnt recognized it,even when my phone is at recovery screen or bootloader screen.What to do? İ decided to flash roms by usng the pc.
NOte:İt gives a sound when i connect it but then nothing happens.

Is it recognized by adb while in recovery?

chromium96 said:
Is it recognized by adb while in recovery?
Click to expand...
Click to collapse
How to undertstand if it does?

korkuadam said:
How to undertstand if it does?
Click to expand...
Click to collapse
-setup adb
-boot phone into recovery and plug it into your computer
-open command prompt and type:
Code:
adb devices
-if your phones serial number shows up, its recognized. Then you can push a rom back onto your phone and flash it using:
Code:
adb push \path\to\rom.zip /sdcard

chromium96 said:
-setup adb
-boot phone into recovery and plug it into your computer
-open command prompt and type:
Code:
adb devices
-if your phones serial number shows up, its recognized. Then you can push a rom back onto your phone and flash it using:
Code:
adb push \path\to\rom.zip /sdcard
Click to expand...
Click to collapse
This is not working.Can i do something with toolkit?

korkuadam said:
This is not working.Can i do something with toolkit?
Click to expand...
Click to collapse
İ just fixed it somehow,thanks

Why cant I flash custom recovery on 4.3?

I downloaded the latest twrp recovery and put the file in my platform tools. (also renamed it to twrp.img) and I go into fastboot mode. Run cmd in my platform tools directory and type fastboot flash recovery twrp.img and I get this message twrp.img no error. Im following a youtube video and the guy does the same thing im doing and his works..

Does it do the same with CWM?

EddyOS said:
Does it do the same with CWM?
Click to expand...
Click to collapse
I prefer twrp so no I have not tried CWm

Cjshino said:
I prefer twrp so no I have not tried CWm
Click to expand...
Click to collapse
Fair enough, but try it and see what happens

EddyOS said:
Fair enough, but try it and see what happens
Click to expand...
Click to collapse
still doesnt work

Cjshino said:
still doesnt work
Click to expand...
Click to collapse
1. Is your bootloader unlocked?
Use "fastboot oem unlock" to unlock your phone's bootloader. Be warn that it will wipe everything if you do not use "fastboot format cache" afterwards.
2. Can you see your device after you run command "fastboot devices"?
Install the fastboot drivers, download google usb driver here: http://developer.android.com/sdk/win-usb.html

ksilver89 said:
1. Is your bootloader unlocked?
Use "fastboot oem unlock" to unlock your phone's bootloader. Be warn that it will wipe everything if you do not use "fastboot format cache" afterwards.
2. Can you see your device after you run command "fastboot devices"?
Install the fastboot drivers, download google usb driver here: http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
yes my bootloader is unlocked and when I run command 'fastboot devices' it works. Im really stumped..

is your kernel rooted? if yes use Recovery Tools (on play store).

Cjshino said:
yes my bootloader is unlocked and when I run command 'fastboot devices' it works. Im really stumped..
Click to expand...
Click to collapse
I just flashed it last night without any problems but I renamed the file recovery.img. You sure you have version 2.6 for the Nexus 4? TWRP has different recoveries for each device.
---------- Post added at 01:22 PM ---------- Previous post was at 01:16 PM ----------
Here's another thing to check. Make sure you didn't rename the file twrp.img.img as windows hides extensions by default. In my case when I renamed the file recovery I didn't have to add the extension .img as it was already there.

Cjshino said:
yes my bootloader is unlocked and when I run command 'fastboot devices' it works. Im really stumped..
Click to expand...
Click to collapse
If you're rooted, try this method:
1. Boot to Android system.
2. Enable USB Debugging
3. Connect your phone with USB.
4. Run the command below:
Code:
adb push twrp.img /sdcard/twrp.img
adb shell
5. Next, get root permission and flash the recovery.
Code:
su
dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
6. After confirming every steps, boot into recovery.
Code:
adb reboot recovery

Thanks guys i just used a toolkit and I have twrp for 4.3 now

[Q] How do i install TRWP onto D802?

Got a D802 on 80220B, rooted with ioroot25...cannot install successfully, any working method?

mockneygeeza said:
Got a D802 on 80220B, rooted with ioroot25...cannot install successfully, any working method?
Click to expand...
Click to collapse
Manual Root Method
Download and extract the latest IOroot.zip
Enable USB Debugging. VZW users must also enable ethernet mode.
Open terminal/command prompt. windows/linux users: cd into /ioroot folder. mac users cd into /ioroot/mac
(windows users can hold shift key, right click in ioroot folder. Select "open command window" option.
1. adb devices
2. adb reboot recovery
(when booted in recovery, select: 'apply update from adb' with power button)
3. adb sideload kk_root.zip
reboot when zip finishes flashing. done.

mockneygeeza said:
Got a D802 on 80220B, rooted with ioroot25...cannot install successfully, any working method?
Click to expand...
Click to collapse
Because loki is patched in 4.4.2 to use a custom recovery you would need to use the old bootloader and a patched kernel as well, flashing itself can be done with dd command in adb shell

what about recovery? Can we install via adb?
prabu33 said:
Manual Root Method
Download and extract the latest IOroot.zip
Enable USB Debugging. VZW users must also enable ethernet mode.
Open terminal/command prompt. windows/linux users: cd into /ioroot folder. mac users cd into /ioroot/mac
(windows users can hold shift key, right click in ioroot folder. Select "open command window" option.
1. adb devices
2. adb reboot recovery
(when booted in recovery, select: 'apply update from adb' with power button)
3. adb sideload kk_root.zip
reboot when zip finishes flashing. done.
Click to expand...
Click to collapse

SNaReX said:
what about recovery? Can we install via adb?
Click to expand...
Click to collapse
Yes, you could flash it the same way but it won't work because of the new bootloader, and instead only nuke stock recovery.

I've used FreeGee (from PlayStore) to install TWRP 2.6.3.3. Really easy

detzero said:
I've used FreeGee (from PlayStore) to install TWRP 2.6.3.3. Really easy
Click to expand...
Click to collapse
On Kitkat?

detzero said:
I've used FreeGee (from PlayStore) to install TWRP 2.6.3.3. Really easy
Click to expand...
Click to collapse
Fenix said:
On Kitkat?
Click to expand...
Click to collapse
Freegee on 4.4.2 is supposed to do just what I wrote, flash old bootloader, patched kernel and recovery, but there are a lot of people having all sorts of issues though

Fenix said:
On Kitkat?
Click to expand...
Click to collapse
I'm sorry, I've read 80210B
My fault...

download mode

I'm stuck right here as far as download mode goes.
I installed TWRP on a d800 rooted with stock 4.2.2. The TWRP install went ok but it never booted afterward.
I can get into twrp, but can't sideload anything because the computer does not connect to the device, I hear the connection noise the computer makes but nothing in the device manager.
any ideas?

May I suggest you use "adb push rom.zip /sdcard/rom.zip" instead of sideload (the sideload doesn't have to be enabled)

bender_007 said:
May I suggest you use "adb push rom.zip /sdcard/rom.zip" instead of sideload (the sideload doesn't have to be enabled)
Click to expand...
Click to collapse
Thanks, I get
error: closed
I was wrong about my computer not seeing my device, it's in the device manager under Android and the adb drivers are installed.
I also renamed the rom to "update" to make it simpler

What's up now ?
Sorted it out or still issues there ?

I also tried the adb shell method.
I also tried this method through TWRP terminal and nada.
If I did something wrong here let me know, hopefully I can get it up and going

bender_007 said:
May I suggest you use "adb push rom.zip /sdcard/rom.zip" instead of sideload (the sideload doesn't have to be enabled)
Click to expand...
Click to collapse
This is what I get when I do the above. The CMD prompt in located in the same directory as the adb files
ADB sees my device as this #

Gabriel51 said:
This is what I get when I do the above. The CMD prompt in located in the same directory as the adb files
ADB sees my device as this #
Click to expand...
Click to collapse
ok, let's do it like this
1. copy rom to c:\rom.zip
2. while in adb folder "adb push c:\rom.zip /sdcard/rom.zip"
that should work, you don't need sideload to be enabled.
Please test and report.

bender_007 said:
ok, let's do it like this
1. copy rom to c:\rom.zip
2. while in adb folder "adb push c:\rom.zip /sdcard/rom.zip"
that should work, you don't need sideload to be enabled.
Please test and report.
Click to expand...
Click to collapse
I moved the file to the root of my C drive changed the name to "rom.zip"
Copied the command you supplied and got this result
I know my phone is connected because I can reboot it by using the command " adb reboot"

I used this;
adb push C:\Android\sdk\platform-tools\rom.zip
And it is now ready to install through TWRP!
Hold your breath.......
Edit;
Failed but at least it's in the twrp list
"unable to open zip"

I think I got it, I was able to access the firmware update screen.
Sorry fir these incomplete responses, I don't want you to keep looking for a resolve while I do this.
If your still here?
I'll be back!
Success!
After nothing would work except for loading the rom through adb I decided to wipe the whole thing.
I reloaded the rom and when selected for install it opened instead of preparing for install so I thought I would reboot and when I did I was prompted by su that my device may have lost root and gave me the option to reinstall it, I chose yes and when rebooting it hung (normal) at the LG logo, however this time the charge light was flashing! I attempted to access "download" and was successful in loading the stock rom.
In the end it looks like TWRP was the culprit, it used to be my favorite but not for this device
All is well, thanks for your help...

root with no co.puter

I try to do the command thing,I just can't get it is it a way to root with doing that command thingy?My bootloader is unlocked

johhnyred23 said:
I try to do the command thing,I just can't get it is it a way to root with doing that command thingy?My bootloader is unlocked
Click to expand...
Click to collapse
There is no way to flash TWRP on a non-rooted device without a computer... Rooting itself requires TWRP and the SuperSU zip on the device.
What part is not working right?

acejavelin said:
There is no way to flash TWRP on a non-rooted device without a computer... Rooting itself requires TWRP and the SuperSU zip on the device.
What part is not working right?
Click to expand...
Click to collapse
When I try to open a command,it doesn't have Android on there

johhnyred23 said:
When I try to open a command,it doesn't have Android on there
Click to expand...
Click to collapse
I'm still not understanding... On your computer you open a command window? You need to navigate to the directory containing fastboot and the twrp image file a day execute the commands there.

acejavelin said:
I'm still not understanding... On your computer you open a command window? You need to navigate to the directory containing fastboot and the twrp image file a day execute the commands there.
Click to expand...
Click to collapse
I'll try thanks,I just now good on command,I was used to the one kicks,and I haven't root in a few years

I figure it out,I'm now officially rooted thanks guys