Related
I tried updating my nexus 7 to 4.2.1 and i thought everything went okay but now adb doesn't recognize my device in fastboot and i can't boot up my nexus 7 because everything got wiped on my sd card. I can boot into recovery but i can't mount my sd card either. It tells me there is an error. Apparently there is no OS installed. Any help is welcomed.
YoungCorruptionV2.0 said:
I tried updating my nexus 7 to 4.2.1 and i thought everything went okay but now adb doesn't recognize my device in fastboot and i can't boot up my nexus 7 because everything got wiped on my sd card. I can boot into recovery but i can't mount my sd card either. It tells me there is an error. Apparently there is no OS installed. Any help is welcomed.
Click to expand...
Click to collapse
You can boot into the bootloader, and use fastboot commands to reflash the stock Android 4.2.1 OS.
RMarkwald said:
You can boot into the bootloader, and use fastboot commands to reflash the stock Android 4.2.1 OS.
Click to expand...
Click to collapse
Fast boot commands don't work because adb can't recognized my device while in fastboot. I tried "adb devices" and no devices were listed
Sent from my EVO using Tapatalk 2
YoungCorruptionV2.0 said:
Fast boot commands don't work because adb can't recognized my device while in fastboot. I tried "adb devices" and no devices were listed
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
You can't use adb in fast boot . Reboot to the boot loader. If you type 'fastboot devices' in fast boot your phone will show
Sent from my One X using xda app-developers app
I had the same problem.
What version of adb.exe Ade you using?
The latest is dated sometime in November this year. If it's earlier than that, download the SDK from android development site and use newer version of adb.exe
That should fix the issue...
Sent from my Nexus 7 using xda premium
From bootloader use fastboot commands, from recovery use adb commands.
You can't do adb commands in fastboot mode. To do adb commands you either need to be in Android or in a recovery.
Sent from my Nexus 7
Stop... MUFFIN TIME!!!
If you have twrp recovery installed you can boot to recovery and use adb sideload.
So just download a rom on your computer boot to recovery and sideload the rom to your device and then install it.
Not sure if this can be done with cwm though
Sent from my Nexus 7 using Tapatalk 2
I unlocked my N7 3G with WugFresh tool and then I rooted and installed a custom recovery.
Everytime I power on my device by pressing Vol DOWN + POWER ON my device is in fastboot mode. But If I try to run adb devices, no devices are found. While if I launch recovery and run the same command, my device is listed.
So I don't understand why I can't communicate with my device if I power on it in fastboot mode, but only if launch it in recovery mode or I power on it with USB debug on.
So I couldn't flash my custom recovery with this command:
Code:
fastboot flash recovery recovery-CWM-tilapia-regular.img
but I had to use WugFresh's tool to flash a custom recovery, in fact when this program launch command to power on device in fastboot mode, it works! I don't understand why I can't do it manually but only throught this software
Try using the command : fastboot devices
Sent from my Nexus 7 using xda premium
KidCarter93 said:
Try using the command : fastboot devices
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thanks. Now it works. I'm too stupid! :silly:
Adb has no access in bootloader for future reference, only in os and recovery
Sent from my HTC Vision using Tapatalk 2
Please help, I downloaded ChameleonOS Rom for Mako and I was on PA. I did a backup in TWRP and after I wiped data and cache I tried tp flash CHAOS ROm. It said success but it won't boot passed Google and If I try to restore PA it says failed and now I have no rom to flash to boot up and also I can't turn on debug to use ADB.
Zehlek said:
Please help, I downloaded ChameleonOS Rom for Mako and I was on PA. I did a backup in TWRP and after I wiped data and cache I tried tp flash CHAOS ROm. It said success but it won't boot passed Google and If I try to restore PA it says failed and now I have no rom to flash to boot up and also I can't turn on debug to use ADB.
Click to expand...
Click to collapse
i'm not on twrp at the moment but you may be able to try this
you may also try the nexus toolkit
Nexus 4 toolkit says device not found when trying to push file to device. It shows serial under fastboot mode but not ADB Mode. Is that because I can't turn on debug?
Zehlek said:
Nexus 4 toolkit says device not found when trying to push file to device. It shows serial under fastboot mode but not ADB Mode. Is that because I can't turn on debug?
Click to expand...
Click to collapse
hmm... can you try setting the current status to "Soft-Bricked/Bootloop" and do the Flash Stock + Unroot? might be able to get you back to square one.
if you can get into twrp you might be able to run adb commands from the recovery even if you didnt have it enabled before using the toolkit.
efan3719 said:
hmm... can you try setting the current status to "Soft-Bricked/Bootloop" and do the Flash Stock + Unroot? might be able to get you back to square one.
if you can get into twrp you might be able to run adb commands from the recovery even if you didnt have it enabled before using the toolkit.
Click to expand...
Click to collapse
That might work, how do I set the current status to "Soft-Bricked/Bootloop" and do the Flash Stock + Unroot?
Zehlek said:
That might work, how do I set the current status to "Soft-Bricked/Bootloop" and do the Flash Stock + Unroot?
Click to expand...
Click to collapse
On the main screen of the nexus tool kit there is a radio button option you can click for it.
Sent from my Nexus 4 using xda premium
not sure what you're trying to do, but if you just want to get the device up and running again..
- Download recovery with sideload
- Go into fastboot
- Use CMD to navigate to your Nexus Toolkit folder,
- Execute " fastboot flash recovery recovery.img ", assuming the image you downloaded was renamed to recovery
- Go into recovery, choose flash with sideload
- Back to CMD, type "adb-toolkit sideload *zipnamehere.zip*" , assuming your adb is named adb-toolkit
reboot, profit.
exb0 said:
not sure what you're trying to do, but if you just want to get the device up and running again..
- Download recovery with sideload
- Go into fastboot
- Use CMD to navigate to your Nexus Toolkit folder,
- Execute " fastboot flash recovery recovery.img ", assuming the image you downloaded was renamed to recovery
- Go into recovery, choose flash with sideload
- Back to CMD, type "adb-toolkit sideload *zipnamehere.zip*" , assuming your adb is named adb-toolkit
reboot, profit.
Click to expand...
Click to collapse
This guy sounds like he knows what he's doing.
Sent from my Nexus 4 using xda premium
exb0 said:
not sure what you're trying to do, but if you just want to get the device up and running again..
- Download recovery with sideload
- Go into fastboot
- Use CMD to navigate to your Nexus Toolkit folder,
- Execute " fastboot flash recovery recovery.img ", assuming the image you downloaded was renamed to recovery
- Go into recovery, choose flash with sideload
- Back to CMD, type "adb-toolkit sideload *zipnamehere.zip*" , assuming your adb is named adb-toolkit
reboot, profit.
Click to expand...
Click to collapse
It says fastboot is not recognized as an internal command
In twrp, it keeps saying starting adb sideload feature
i posted this in another thread. try this...
1. First make sure that you have fastboot driver installed.
2. Power down your Nexus 4 (hold the power button until it shuts off) before rebooting into fastboot mode. You can do this by holding down the the Volume Down and Power buttons simultaneously.
3. Connect your device to your computer. Open up a terminal or command prompt, and navigate to the folder containing the fastboot program.
4. Type fastboot devices into the command line, and you should then see your device’s ID, which means fastboot is setup correctly. if not, check to make sure Google Nexus 4 drivers are installed correctly.
5. now open Nexus 4 toolkit and Flash Google Factory stock Rom. Once you are back to stock continue on from there...
Good Luck!
Zehlek said:
It says fastboot is not recognized as an internal command
Click to expand...
Click to collapse
my bad, it's fastboot-toolkit. But since you have a recovery with sideload already, just download a rom that's working, put it in your nexus 4 toolkit folder, rename it to flash.zip, and type in CMD
"adb-toolkit sideload flash.zip"
Thank you all for your help. What I had to end up doing was extracting the factory image and flash boot, system, and use data IMG files manually with nexus 4 toolkit. My Nexus 4 is alive. Again thank you all very much
Sent from my Nexus 4 using Tapatalk 2
Zehlek said:
Thank you all for your help. What I had to end up doing was extracting the factory image and flash boot, system, and use data IMG files manually with nexus 4 toolkit. My Nexus 4 is alive. Again thank you all very much
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Glad to here it. My heart sank when I read your issue. Happy to see it resolved.
Sent from my Nexus 4 using xda premium
efan3719 said:
Glad to here it. My heart sank when I read your issue. Happy to see it resolved.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Thank you. I was beginning to panic when I saw there nothing working that would transfer a rom to my sdcard. Again thank you for all your help
Sent from my Nexus 4 using Tapatalk 2
Hi, when android 4.3 launched, i went back to 4.2 complete stock with no custom recovery and locked the bootloader to receive the update OTA.
Now I have 4.3 with Z20i bootloader and when i flash cwm, phone gets stuck on the GOOGLE splashscreen and after 1/2 hour moves to the X screen and gets stuck there. Recovery does not works. I had to flash stock recovery and wipe all data to make it work. when trying
Code:
fastboot boot recovery.img (recovery-clockworkmod-6.0.3.6-mako.img)
, it shows a black screen after google and then reboots in safemode whenever any button is pushed.
RohMish said:
Hi, when android 4.3 launched, i went back to 4.2 complete stock with no custom recovery and locked the bootloader to receive the update OTA.
Now I have 4.3 with Z20i bootloader and when i flash cwm, phone gets stuck on the GOOGLE splashscreen and after 1/2 hour moves to the X screen and gets stuck there. Recovery does not works. I had to flash stock recovery and wipe all data to make it work. when trying
Code:
fastboot boot recovery.img (recovery-clockworkmod-6.0.3.6-mako.img)
, it shows a black screen after google and then reboots in safemode whenever any button is pushed.
Click to expand...
Click to collapse
Normally you have to execute
Code:
fastboot flash recovery recovery.img
Try it with the latest cwm image
Sent from my Nexus 4 running Android 4.2.2
mihahn said:
Normally you have to execute
Code:
fastboot flash recovery recovery.img
Try it with the latest cwm image
Sent from my Nexus 4 running Android 4.2.2
Click to expand...
Click to collapse
flash installs the recovery but nothing works. i have to do a wipe and install the stock recovery to boot it. i wrote it on top
Put your device on the bootloader menu and use this: https://developers.google.com/android/nexus/images#occamjwr66v
Always use the stock bootloader like pretty much everyone who owns the Nexus 4.
Sent from my Nexus 4 using Tapatalk 4
andyabc said:
Put your device on the bootloader menu and use this: https://developers.google.com/android/nexus/images#occamjwr66v
Always use the stock bootloader like pretty much everyone who owns the Nexus 4.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
It is on the stock bootloader that comes with the nexus 4. The problem is after 4.3 update, i am not able to install cwm on my phone. using fastboot boot command gives black screen while fastboot flash boots a recovery whose none of functions work as it is unable to mount any partition, etc. and i have to install factory image of recovery and do a factory reset to boot the device again to android.
RohMish said:
It is on the stock bootloader that comes with the nexus 4. The problem is after 4.3 update, i am not able to install cwm on my phone. using fastboot boot command gives black screen while fastboot flash boots a recovery whose none of functions work as it is unable to mount any partition, etc. and i have to install factory image of recovery and do a factory reset to boot the device again to android.
Click to expand...
Click to collapse
Oh, I thought that was some custom bootloader, apologies.
Em yeah you will have to install the factory image.
Sent from my Nexus 4 using Tapatalk 4
andyabc said:
Oh, I thought that was some custom bootloader, apologies.
Em yeah you will have to install the factory image.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Did that. it has made me more mad as it took 3 hours to download and when your phone is not working, even ever minute is like an day.
RohMish said:
Did that. it has made me more mad as it took 3 hours to download and when your phone is not working, even ever minute is like an day.
Click to expand...
Click to collapse
Did you try installing an other recovery like either the latest version of CWM or TWRP?
Sent from my Nexus 4 using Tapatalk 4
andyabc said:
Did you try installing an other recovery like either the latest version of CWM or TWRP?
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
tried an older version of cwm, touch, everything. but all are having same issues
RohMish said:
tried an older version of cwm, touch, everything. but all are having same issues
Click to expand...
Click to collapse
Older is worse!
Try TWRP 2.6.0.0.
Sent from my Nexus 4 using Tapatalk 4
andyabc said:
Older is worse!
Try TWRP 2.6.0.0.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
trying it now.
any ways i can switch to cwm after that as i prefer cwm any day of week. will fastboot boot command word as i dont want to sit flashing the factory image and let the apps and all download again
UPDATE: Tried twrp via fastboot boot command. nothing. just a blank screen after the reboot from bootloader (and after google boot screen) for a few seconds, andd then shuts down.
RohMish said:
trying it now.
any ways i can switch to cwm after that as i prefer cwm any day of week. will fastboot boot command word as i dont want to sit flashing the factory image and let the apps and all download again
Click to expand...
Click to collapse
The issue is that fastboot boot recovery doesn't work on 4.3. The new command if fastboot - c lge.kcal=0|0|0|x boot recovery.img
BLACKED OUT LTE N4
spaceman860 said:
The issue is that fastboot boot recovery doesn't work on 4.3. The new command if fastboot - c lge.kcal=0|0|0|x boot recovery.img
BLACKED OUT LTE N4
Click to expand...
Click to collapse
not working. says 0 is a not a command. this is as | works as a batch separator in windows
Update: as i remembered modifier <"> will prevent | from kicking into next line, i tried that, and it works!
fastboot -c "lge.kcal=0|0|0|x" boot recoverycwm.img. but still no action. tried a backup, it starts to backup but files are corrupted. and nothing else work.
This is from efrant guide
Open a command prompt in the directory mentioned above and type: fastboot boot customrecovery.img Note: If you are running the latest bootloader (z20i), the command would be: fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img Thanks hwti & el_charlie
BLACKED OUT LTE N4
spaceman860 said:
This is from efrant guide
Open a command prompt in the directory mentioned above and type: fastboot boot customrecovery.img Note: If you are running the latest bootloader (z20i), the command would be: fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img Thanks hwti & el_charlie
BLACKED OUT LTE N4
Click to expand...
Click to collapse
i loads up but is kind of broken.
any way i can copy the files to my pc to do some analysis. currently the folder which used to save the files has nothing. adb pull /mnt/shell/emulated/clockworkmod/backup/ /android/adbbackupfiles/nexus4 is yielding nothing.
OK. so now i tried using the touch version, and this time there are some files(Still copying). but those are very different than what it was on my older phones and my initial backup. Sorry, I had got away with this due to studies. now the files are .a and.b and the orignal file which is 0KB
Nexus 4 running 4.4.2 bootloader version MAKOZ30d
I used Wug's root toolkit to unlock my bootloader but after reboot into fastboot, neither my windows 7 machine nor my linux mint machine will mount the phone without MTP turned on. I can run adb commands while MTP is on but drivers fail to load if mtp is off.. So now I have an unlocked bootloader and am unable to complete the rooting proces..
Any help is much appreciated.
Cheers!
go to settings/storage open 3dots menu /usb computer connection. if nothing is selected that is why your phone doesn't connect. select mtp an problem solved.
if it's not that i cannot help you except suggesting to reinstall android from scratch using wug toolkit.
wasabitobiko said:
Nexus 4 running 4.4.2 bootloader version MAKOZ30d
I used Wug's root toolkit to unlock my bootloader but after reboot into fastboot, neither my windows 7 machine nor my linux mint machine will mount the phone without MTP turned on. I can run adb commands while MTP is on but drivers fail to load if mtp is off.. So now I have an unlocked bootloader and am unable to complete the rooting proces..
Any help is much appreciated.
Cheers!
Click to expand...
Click to collapse
You can't "mount storage" in Fastboot mode.... what exactly are you trying to do?
acejavelin said:
You can't "mount storage" in Fastboot mode.... what exactly are you trying to do?
Click to expand...
Click to collapse
Trying to finish the rooting process by using adb.. by "mount" I mean get access in fastboot from either of my computers. Didn't have this problem with my other N4.. when I plug the phone into my computer while in fastboot and try any adb commands.. I get <waiting for device> nothing... It seems like the adb drivers aren't loading while in fastboot. I'll try to back things out using the toolkit again..
wasabitobiko said:
Trying to finish the rooting process by using adb.. by "mount" I mean get access in fastboot from either of my computers. Didn't have this problem with my other N4.. when I plug the phone into my computer while in fastboot and try any adb commands.. I get <waiting for device> nothing... It seems like the adb drivers aren't loading while in fastboot. I'll try to back things out using the toolkit again..
Click to expand...
Click to collapse
OK, so your fastboot commands are not working, that would likely be a driver issue? If you do
Code:
fastboot devices
and get a result, then keep going, if you don't, use one of the driver options in Wugfresh's toolkit, follow the instructions TO THE LETTER...
If you are just trying to get root and are unlocked, download the latest SuperSU.zip (to your phone preferably) from http://download.chainfire.eu/supersu and openrecovery-twrp-2.7.0.0-mako.img then start phone in Fastboot mode and enter:
Code:
fastboot boot openrecovery-twrp-2.7.0.0-mako.img
this will start TWRP on your device WITHOUT flashing it.
If the SuperSU zip file is on your phone, just use TWRP's Install button and navigate the file and flash it, then reboot and enjoy.
If the SuperSU zip is on your PC, then in TWRP go to Advanced, and start ADB Sideload, give it a few seconds for it to be recognized by your PC, you should be able to enter
Code:
adb devices
and get a result of SIDELOAD back, then enter:
Code:
adb sideload UPDATE-SuperSU-v1.94.zip
Or whatever the current SuperSU zip file is named. Then reboot and enjoy, your rooted!
Remember that adb commands only work in android and custom recovery NOT in fastboot mode.
Sent from my Nexus 4 using XDA Free mobile app
Ok.. If I can't run adb commands from fastboot, how do I enter that command in fastboot?
Sent from my Nexus 4 using XDA Free mobile app
wasabitobiko said:
Ok.. If I can't run adb commands from fastboot, how do I enter that command in fastboot?
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
ADB sideload is a special mode that recovery can be placed into, it only allows the "sideload" command to be used. Fastboot is different, it uses the fastboot.exe program and fastboot mode on the android device to allow a limited list of features to be used.
I don't know what you are using for a rooting guide, but basically the end result is to flash SuperSU via recovery, that is all that is really needed.
Sent from my Nexus 4 using Tapatalk
Well, basically if your boot loader is unlocked and you have a custom recovery installed just download the latest superSU zip to your SD card. Reboot into recovery, install SuperSU, reboot. Alas, you're rooted.
Sent from my Nexus 4 using XDA Free mobile app
That's the problem.. No custom recovery installed.. Still working on the driver issue.
Sent from my Nexus 4 using XDA Free mobile app
wasabitobiko said:
That's the problem.. No custom recovery installed.. Still working on the driver issue.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
If you unlocked your bootloader your drivers should be working fine. If you rebooted your phone now you'd see it works fine. Next step in rooting is to flash custom recovery. Download a custom recovery, I recommend latest version of TWRP, then flash the recovery image. 'fastboot flash recovery recovery.img' (replace recovery.img with whatever .img file you are flashing.
Once custom recovery is installed you can boot into it to flash supersu. If using TWRP it will prompt you to root when you reboot it.
Thanks.. And please don't take offense to this but re-read the thread. Ever since I used wug's rootkit to unlock the bootloader, neither my pc nor linux machine will recognize the Nexus 4. When I plug it in I get a usb error "device failed to load".. When I look at the device mgr it's listed as unknown device. Btw.. I've restarted both my phone and machine multiple times to no avail.
Sent from my Nexus 4 using XDA Free mobile app
Unknown device? Youve probably installed no or wrong fastboot drivers.
Sent from my Nexus 4 using XDA Free mobile app
wasabitobiko said:
That's the problem.. No custom recovery installed.. Still working on the driver issue.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
Google tool 15 second adb xda
Sent from my Nexus 5 using XDA Free mobile app
UPDATE: It looks like the micro usb port on the phone is fried... had been charging fine until today. I'll keep you posted. Thanks for all the help. Does anyone know if this is a relatively easy fix?
Update: Fixed..
Replacing the usb port on the Nexus 4 is super easy. Thanks for the help guys. Everything's working and root has been achieved.