Database Users

[Q] DEAD N4? Not Really but failed to root and install recovery

I tried to root my phone today by using the Nexus 4 toolkit. In the process of rooting the phone, the use connection is physically disconnect by myself well it was an accident. After that, I only got unlocked bootloader, but I am not be able to get the recovery and the SU in the phone. When I try to repeat the steps, it is stucking at " cannot connect device" or sometimes "failed ... unknown error" or even "protocol error"(if I remember correctly. It seems that the connection is gone between the phone and the desktop under the fastboot mode. But under the normal Android OS, I am able to connect my phone to desktop to do the data transfer things.
I am seeking for help here. I hope I explain my problem properly that you guys can understand. Here is error I got sometime when I connect my phone to PC.
The button is OK in the pic.

hilts425 said:
I tried to root my phone today by using the Nexus 4 toolkit. In the process of rooting the phone, the use connection is physically disconnect by myself well it was an accident. After that, I only got unlocked bootloader, but I am not be able to get the recovery and the SU in the phone. When I try to repeat the steps, it is stucking at " cannot connect device" or sometimes "failed ... unknown error" or even "protocol error"(if I remember correctly. It seems that the connection is gone between the phone and the desktop under the fastboot mode. But under the normal Android OS, I am able to connect my phone to desktop to do the data transfer things.
I am seeking for help here. I hope I explain my problem properly that you guys can understand. Here is error I got sometime when I connect my phone to PC.
The button is OK in the pic.
Click to expand...
Click to collapse
Accidently hit the thanks button
The phone`s bootloader is allready unlocked.
- Is the phone recognized in adb and fastboot mode? If not install the 0.72 usb naked drivers.
- Flash CWM recovery in fastboot mode from here http://clockworkmod.com/rommanager, choose touche or non touch.
- flash superSU 1.20 from here http://forum.xda-developers.com/showthread.php?t=1538053 in CWM recovery.
- Install BusyBox from Google Play.
- Done.

gee2012 said:
Accidently hit the thanks button
The phone`s bootloader is allready unlocked.
- Is the phone recognized in adb and fastboot mode? If not install the 0.72 usb naked drivers.
- Flash CWM recovery in fastboot mode from here http://clockworkmod.com/rommanager, choose touche or non touch.
- flash superSU 1.20 from here http://forum.xda-developers.com/showthread.php?t=1538053 in CWM recovery.
- Install BusyBox from Google Play.
- Done.
Click to expand...
Click to collapse
how do I flash cwm in fastboot?

hilts425 said:
how do I flash cwm in fastboot?
Click to expand...
Click to collapse
Install the android sdk platform-tools and once installed:
- open cmd terminal and type: adb reboot bootloader
- type: fastboot devices and you should see a serial number if the usb drivers are nstalled correctly
- then type: fastboot flash recovery recovery-(name of the recovery).img
Read some threads to get familiar with your phone and to learn how to flash, root, use adb and it`s commands etc etc.

gee2012 said:
Accidently hit the thanks button
The phone`s bootloader is allready unlocked.
- Is the phone recognized in adb and fastboot mode? If not install the 0.72 usb naked drivers.
- Flash CWM recovery in fastboot mode from here http://clockworkmod.com/rommanager, choose touche or non touch.
- flash superSU 1.20 from here http://forum.xda-developers.com/showthread.php?t=1538053 in CWM recovery.
- Install BusyBox from Google Play.
- Done.
Click to expand...
Click to collapse
the official recovery does not work now! Any ideas?

hilts425 said:
the official recovery does not work now! Any ideas?
Click to expand...
Click to collapse
Yes it works, but it will not flash the SU zip. You need a custom recovery for that.

gee2012 said:
Yes it works, but it will not flash the SU zip. You need a custom recovery for that.
Click to expand...
Click to collapse
OK when I choose the recovery I only appears the android robot with a "!" and I can not do nothing there. Is this a bad sign?

hilts425 said:
OK when I choose the recovery I only appears the android robot with a "!" and I can not do nothing there. Is this a bad sign?
Click to expand...
Click to collapse
ok when i flash the recovery in the cmd
it says
failed (command write failed unknown error.)

[Q] Failed Root? Stock Sideload Help!

Hello all,
I initally used the Wugz root toolkit to unlock, install drivers and root my device. I flashed CWM and a ROM. Once I flashed the ROM, it wouldn't boot, but would flash the google logo, go black, then go to the google logo and open up CWM again.
I searched for backups, they were gone. So I tried a few things and now I can't even get to CWM.
All I can get to is the Recovery menu and Stock Recovery. My computer won't recognize the device in adb fastboot but will recognize it when I put it into sideload from the stock recovery.
I've tried to flash the 4.1.2 and 4.2.2 images from the Google developer website but when it verifies the installation package it says installation aborted.
Is there any way I can fix this just from the Stock Recovery sideload? Is this hopelesss?

Take a look at this THREAD

Nico_60 said:
Take a look at this THREAD
Click to expand...
Click to collapse
Thanks. I did try this first, I must have messed it up somewhere. I'll try it again. Not sure if it'll work without the device being recognized under fastboot.

To know if it's recognized type "fastboot devices" but if the driver were already installed it must be ok

Whew got it to work. Thanks.

[HELP] Nexus 4 Softbrick, Can't Mount SDCard On Recovery Mode

I recently just installed ParanoidAndroid 3.99 RC2. after unlocking my bootloader, I do not go in the OS. then I want to reinstall from the recovery mode, CWM says "Cant Mount SDCard. so I want to go back to the Stock Rom., but the problem is, my computer does not recognize" fastboot Device ". though I had to install the driver. I've download" Factory Image "(4.3 JWR66Y.) so what can I do to get back to the original OS ?
Pliss Help Me !!!

ayyub46 said:
I recently just installed ParanoidAndroid 3.99 RC2. after unlocking my bootloader, I do not go in the OS. then I want to reinstall from the recovery mode, CWM says "Cant Mount SDCard. so I want to go back to the Stock Rom., but the problem is, my computer does not recognize" fastboot Device ". though I had to install the driver. I've download" Factory Image "(4.3 JWR66Y.) so what can I do to get back to the original OS ?
Pliss Help Me !!!
Click to expand...
Click to collapse
You have unlocked your bootloader with your Computer right?? so the drivers is working fine..
If you can get into bootloader you just need to extract the ROM, and run flash-all.xx

are you trying to run fastboot while in your phones recovery or bootloader?

You don't flash stock google firmware using recovery, you flash it using fastboot while the device is on bootloader mode.
http://forum.xda-developers.com/showthread.php?t=2010312

rcoliveirajr said:
You have unlocked your bootloader with your Computer right?? so the drivers is working fine..
If you can get into bootloader you just need to extract the ROM, and run flash-all.xx
Click to expand...
Click to collapse
simms22 said:
are you trying to run fastboot while in your phones recovery or bootloader?
Click to expand...
Click to collapse
eksasol said:
You don't flash stock google firmware using recovery, you flash it using fastboot while the device is on bootloader mode.
http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
I've installed the driver and want to flash it using fastboot. but cmd says "is not recognize".
omg what the day !!

then it seems that the driver isnt installed properly(or in the right location), fastboot wouldnt see your device then.

ayyub46 said:
I've installed the driver and want to flash it using fastboot. but cmd says "is not recognize".
omg what the day !!
Click to expand...
Click to collapse
Try to delete all drivers that you installed, or Windows installed, and download and install this driver. Probably it'll work..

[SOLVED] im using android sdk and flash using fastboot mode. thanks for ur all suggest guys
Sent from my Nexus 4 using xda app-developers app

[Help] I bricked my Axon. Need help.

So i've gone through every thread here without success. I have a unlocked bootloader but no OS nor custom recovery and i cant get into fastboot mode to install twrp. When i use ADB it wont find my device unless i go into Stock recovery -> update through ADB and even then it only recognized my device as sideload. What can i do? When i tried to use the MiFlash tool i cant seem to get the correct qualcomm drivers installed. what can i do?
Edit: I solved my issue by downloader the stock B08 system on my S5 and then i placed it in the external sd. Then i put the SD back into the Axon and installed the system. After i had installed the system and booted into the OS i could enter adb with my device being recognized and after that i flashed twrp by using ADB.
I have a new problem though and that is that i can't install the 3.1.0.0. twrp. it only boots into black screen when i enter recovery. I can use the 3.0.4.0. version though.

You can't enter fastboot mode on your phone. Correct?
I also assume that you installed a ROM from recovery and that's what caused the brick, right?
What happens when you try to enter recovery?

senny22 said:
So i've gone through every thread here without success. I have a unlocked bootloader but no OS nor custom recovery and i cant get into fastboot mode to install twrp. When i use ADB it wont find my device unless i go into Stock recovery -> update through ADB and even then it only recognized my device as sideload. What can i do? When i tried to use the MiFlash tool i cant seem to get the correct qualcomm drivers installed. what can i do?
Click to expand...
Click to collapse
Go into My Computer, manage, devices and try to uninstall all drivers that are possibly related to your device.
Unplug your phone and let the drivers reinstall by itself.
Go into ADB and see if ADB Devices works.
If possible go into ADB reboot edl and try to reflash custom recovery : "axon7tool -w recovery"
When recounting unplug your phone and see if you can reboot, shutdown and enter into TWRP.
ps : i hope you have a backup ?

nonamesl said:
You can't enter fastboot mode on your phone. Correct?
I also assume that you installed a ROM from recovery and that's what caused the brick, right?
What happens when you try to enter recovery?
Click to expand...
Click to collapse
Correct. It simply reboots.
Yup, i tried installing the B29 stock system on my G model and so i suppose i had the wrong bootstack becasue this is where my problems started.
I get to the stock android recovery.

raystef66 said:
Go into My Computer, manage, devices and try to uninstall all drivers that are possibly related to your device.
Unplug your phone and let the drivers reinstall by itself.
Go into ADB and see if ADB Devices works.
If possible go into ADB reboot edl and try to reflash custom recovery : "axon7tool -w recovery"
When recounting unplug your phone and see if you can reboot, shutdown and enter into TWRP.
ps : i hope you have a backup ?
Click to expand...
Click to collapse
It still wont recognize my device. Which driver am i supposed to have in the Device manager? Do you think i can use my old S5 to transfer a Stock system to the sd card and then update my phone manually through the stock recovery and then when i have an OS installed maybe i can connect to ADB. I read somewhere that ADB commands only works in recovery and in the OS.
I have a twrp backup of my system on my SD card so no worries there.

senny22 said:
It still wont recognize my device. Which driver am i supposed to have in the Device manager? Do you think i can use my old S5 to transfer a Stock system to the sd card and then update my phone manually through the stock recovery and then when i have an OS installed maybe i can connect to ADB. I read somewhere that ADB commands only works in recovery and in the OS.
I have a twrp backup of my system on my SD card so no worries there.
Click to expand...
Click to collapse
You should see your phone as QUSB_BULK. Installed the ZADIG drivers ? That may cure the problem.
After that, imo, it is important you can reboot edl and flash TWRP recovery again AND when it recounts, you pull usb.
Normally you will have replaced recovery , reboot ok and you can enter TWRP and fastboot also.
ps : sometimes it is also advisable to go to ADB RECOVERY directly and do the processes.
ps2 : when TWRP backup, you can always put it on SD via other phone and in TWRP restore. Normaly you're good to go then...

Try the Marshall London Bootloader Interface driver maybe?

nonamesl said:
Try the Marshall London Bootloader Interface driver maybe?
Click to expand...
Click to collapse
Ok, should i be able to find my device with "adb devices" if i uninstall all the other drivers and install this driver?

senny22 said:
Ok, should i be able to find my device with "adb devices" if i uninstall all the other drivers and install this driver?
Click to expand...
Click to collapse
Installing the driver and using it for the phone (device manager -> change driver manually (or something of the sort)) worked for me, but it could differ. Let me know. You don't have to uninstall other drivers just use that specific one for your phone by switching the driver manually via device manager.

moto x style xt1572 stuck on bootloader is unlocked screen after failed rom flashing

for the first time last night I tried to root my moto x style/pure. All was going well as I rooted and unlocked the bootoader successfully but after trying to flash a .img file (as I was told by the app I was using) from a custom rom my phone turned off and is now stuck on 'bootloader is unlocked' warning when trying to boot it up. I can access android recovery, but i dont know what else to do from there...

tdm123 said:
for the first time last night I tried to root my moto x style/pure. All was going well as I rooted and unlocked the bootoader successfully but after trying to flash a .img file (as I was told by the app I was using) from a custom rom my phone turned off and is now stuck on 'bootloader is unlocked' warning when trying to boot it up. I can access android recovery, but i dont know what else to do from there...
Click to expand...
Click to collapse
What EXACTLY did you flash and how? What img file from what ROM?

What app, what .img file? Twrp app?
What recovery you can run? Stock 3e or twrp? You have style or pure moto xs? @tdm123

acejavelin said:
What EXACTLY did you flash and how? What img file from what ROM?
Click to expand...
Click to collapse
i used an app i got from the xda forums (it was a tool) and the .img file was from the latest official lineage os build for my device. unfortunately i deleted the tool and the rom in a fit of rage so i cant be more specific

dzidexx said:
What app, what .img file? Twrp app?
What recovery you can run? Stock 3e or twrp? You have style or pure moto xs? @tdm123
Click to expand...
Click to collapse
i used a tool from an xda forum, i think i tried to flash the boot image file and i used the official twrp app from the playstore. if its any help, i can access android recovery

tdm123 said:
i used an app i got from the xda forums (it was a tool) and the .img file was from the latest official lineage os build for my device. unfortunately i deleted the tool and the rom in a fit of rage so i cant be more specific
Click to expand...
Click to collapse
If yu was at stock rom you coldn't flash any .img file from LineageOs.
I think you have to restore(your own twrp backup) or flash the newest stock rom.

dzidexx said:
If yu was at stock rom you coldn't flash any .img file from LineageOs.
I think you have to restore(your own twrp backup) or flash the newest stock rom.
Click to expand...
Click to collapse
for some reason, my phone needs usb debugging enabled everytime it turns on so im unable to connect it to my laptop. if i was to take out my sd card, put the files into my sd card, go to android recovery and apply update from sd card would it work?

What recovery? 3e - stock or twrp - custom can you run? @tdm123

dzidexx said:
What recovery? 3e - stock or twrp - custom can you run? @tdm123
Click to expand...
Click to collapse
its stock recovery

So you have to flash stock rom using fastboot. After update to the newest.
Remember!!! Don't lock bootloader and:
Without: "oem begin, flash bootloader, gpt, oem lock"
Check how many system sparsechunks are in downloaded StockRom.zip, you have to flash all from 0 to end.
Here is how to:
https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110
Connect to pc in bootloader mode.

dzidexx said:
So you have to flash stock rom using fastboot. After update to the newest.
Remember!!! Don't lock bootloader and:
Without: "oem begin, flash bootloader, gpt, oem lock"
Check how many system sparsechunks are in downloaded StockRom.zip, you have to flash all from 0 to end.
Here is how to:
https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110
Connect to pc in bootloader mode.
Click to expand...
Click to collapse
before i try this, my computer cant detect my phone, so how can i do this?

Install motorola device manager.
Try another port, cable, pc. Linux can be the best.

dzidexx said:
Install motorola device manager.
Try another port, cable, pc. Linux can be the best.
Click to expand...
Click to collapse
ive just tried all three usb ports on my laptop. wondershare mobilego detects it but cant do anything, file explorer shows nothing, and im using a windows 10 laptop and never used linux

You have bootloop. You can connect only in bootloader/fastboot mode.
Only fastboot can detect the device.
Windows device manager should show "adb device".
How did you unlock bootloader?

dzidexx said:
You have bootloop. You can connect only in bootloader/fastboot mode.
Only fastboot can detect the device.
Windows device manager should show "adb device".
How did you unlock bootloader?
Click to expand...
Click to collapse
i unlocked thebootloader through a tool on a xda forum called windroid toolkit. it worked perfectly unlocking the bootloader. windows device manager shows android device instead of adb device. can i repair bootloop?

I posted kink here - post #10. There you will find everything. @tdm123