Database Users

Accidentally wiped everything. No adb during recovery or bootloader.

I'm on TWRP 2.3.3.0., and my computer is W8 Pro. I've searched but most people seem to be able to get adb working during the bootloader at least, but not for me. I've tried sideloading a zip through the command prompt (and picking the adb sideload option in TWRP) but it tells me that adb is not recognized. I've tried using the Nexus Root Toolkit to restore a backup I have on my computer, but, yeah, no adb. I was wondering if disabling driver signature enforcement was temporary, so I went through the menus and disabled it again on my computer. I've used the cable/port that I rooted it with but I've also used different cables and ports as well. Why isn't this working? Am I bricked?

Have you tried jromflasher for nexus 7? With that tool you can wipe your system, upload ROM, temporary load custom recovery, and flash the ROM.
Sent from my Nexus 7 using Tapatalk HD

xbox1513 said:
Have you tried jromflasher for nexus 7? With that tool you can wipe your system, upload ROM, temporary load custom recovery, and flash the ROM.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Error 103. I think my device needs to be booted into an actual ROM.
I thought that maybe the drivers from plugging my phone in were interfering, so I used the Nexus Root Toolkit again, and went through the driver installation for a second time, deleting all the old ADB drivers and such. Well, when I tried to install the RAW drivers, I get "Windows was unable to install your unknown device," and basically it could not find the driver software and to check the company website and so on. Did I just dig myself into a deeper hole? Gah! I wish I could remember which wipe option deleted sdcard so I know to never do it again.

OP is using Win8 - might want to try to do it with a PC or laptop running Win7 or Vista OS and start fresh by loading the drivers and/or use Jromflasher - borrow a friend/neighbor's PC to see if it can be jump started, assumed that s/he cannot get it to boot into Fastboot and/or Recovery as the file systems are likely corrupted. (I have an old/aging laptop running Windows XP SP3 that's set aside for fixing often the impossible)
Otherwise, it might be time for an RMA to get it repaired by Google/Asus and/or exchange - it could cost $$ if they determined that the warranty has been "compromised" ...

You know you won't get adb while in bootloader? You need fastboot.
Sent from my SGH-I777 using xda premium

korockinout13 said:
You know you won't get adb while in bootloader? You need fastboot.
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
It says "fastboot mode" on the bootloader.

Letitride said:
OP is using Win8 - might want to try to do it with a PC or laptop running Win7 or Vista OS and start fresh by loading the drivers and/or use Jromflasher - borrow a friend/neighbor's PC to see if it can be jump started, assumed that s/he cannot get it to boot into Fastboot and/or Recovery as the file systems are likely corrupted. (I have an old/aging laptop running Windows XP SP3 that's set aside for fixing often the impossible)
Otherwise, it might be time for an RMA to get it repaired by Google/Asus and/or exchange - it could cost $$ if they determined that the warranty has been "compromised" ...
Click to expand...
Click to collapse
Thanks. I'll try this later tonight. Would they RMA in this scenario, even though it is my fault? Assuming I can't get it working.

I don't understanding why you would RMA? You can get into twrp right? So you can still flash ROMs and whatnot. Just need to get adb installed on cpu

You can also try "disable driver signature check" on advanced reboot on windows 8.
Sent from my Nexus 7 using Tapatalk HD

Bullonie said:
It says "fastboot mode" on the bootloader.
Click to expand...
Click to collapse
Well....use fastboot then.
You should have done some reading before you started flashing ROM's. You dont seem to even know what fastboot is.

Have you tried downloading the android sdk from Google and installing their usb driver?
Sent from my Nexus 7 using XDA Premium HD app

Adb works in recovery and in Android OS, only fastboot works in the bootloader. Installing Windows 8 messed it up for me, but I simply grabbed the Nexus 7 driver from ASUS'S website. I suggest you read and learn how to use fastboot.
Sent from my Nexus 7 using Tapatalk HD

Stuck at "android is upgrading"/"starting apps"

Basically I tried to install acid audio mod 8 on my phone but did not realize that it was xperia only, so now it is stuck on "android is upgrading"/"starting apps" everytime i reboot. I tried flashing back to acid audiomod 7 and that didnt help. I am running Slimrom with franco kernel btw. I also tried wiping dalvik cache, just cache, and formating the phone from recovery, none of that helped. I dont have any roms saved on my phone or any backups so I am stuck like this and I cant connect my phone to my pc, my pc would recognize it but it wont show up in my computer so I cant access it to to save another rom to it. I tried connecting via recovery (where it goes "download mode do not unplug the device until the process is complete") But that doesnt work, the it would try and install drivers for two "Full JellyBean on Mako" (so it seems like slimrom is based off of a older cm 10 build), but it would come back with no drivers found. When I am in recovery via clockwork my pc recognizes my phone as "Android" but again I still cant do anything with it. Someone please help! I need to fix it by tonight because I am going camping tommorow with family for a few days so having my phone working is a must .
Thanks for those that try to help!
PS I tried using nexus 4 toolkit to reinstall drivers that didnt help.

Deleted
Sent from my Nexus 4 using xda app-developers app

help!
please help! Im searching for what I can do but i cant find anything at all.

What exactly do you mean it recognizes as android? Do you mean from device manager? Does it recognize it via adb? If so you can use adv to push or side load a rom
Sent from my Nexus 4 using xda app-developers app

marsdta said:
What exactly do you mean it recognizes as android? Do you mean from device manager? Does it recognize it via adb? If so you can use adv to push or side load a rom
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Im not sure how to do that, lol, im still pretty noob, but yeah I mean from devicemanager.

I would install the SDK . you could also use the adb files of the toolkit if you want
When you locate the adb files. Open a command prompt (shift right click ) and type adb devices. To check if its being recognized. If it is we can push a ROM.
Download ROM of choice and place it in the same folder as adb
Then type the command
Adb push nameofrom.zip /sdcard/nameofrom.zip
Or if you near a PC I can help out via teamviewer
Sent from my Nexus 4 using xda app-developers app

marsdta said:
I would install the SDK . you could also use the adb files of the toolkit if you want
When you locate the adb files. Open a command prompt (shift right click ) and type adb devices. To check if its being recognized. If it is we can push a ROM.
Download ROM of choice and place it in the same folder as adb
Then type the command
Adb push nameofrom.zip /sdcard/nameofrom.zip
Or if you near a PC I can help out via teamviewer
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Could you please help out through team viewer lol? I know I have adb sdk installed, just dont know how to use it.

lemon07r said:
Could you please help out through team viewer lol? I know I have adb sdk installed, just dont know how to use it.
Click to expand...
Click to collapse
LEARN.

exbo, no comment, not even worth say anything lol maybe try learning manners.
Anyways thank you marsdta for helping me through team viewer .

Download the factory image, learn to use adb or try the toolkit to flash it back to stock, and never touch your phone again. As far as drivers, try this. http://junefabrics.com/android/downloadold.php

marsdta said:
What exactly do you mean it recognizes as android? Do you mean from device manager? Does it recognize it via adb? If so you can use adv to push or side load a rom
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Hello sir I to have the same problem I tried to install beats audio on my gionee elife e3 mobile it was also having same problem but I am using windows 8.1 it was detecting as android phone but not android device so please help me over team viewer I have all drivers installed for it though when I select update driver of unknown device as android device it dosent show android adb interface but when I select as android phone it shows android adb interface and in sdk when I use adb devices it dosent show any name so where can I side load to so help me please....

lemon07r said:
Basically I tried to install acid audio mod 8 on my phone but did not realize that it was xperia only, so now it is stuck on "android is upgrading"/"starting apps" everytime i reboot. I tried flashing back to acid audiomod 7 and that didnt help. I am running Slimrom with franco kernel btw. I also tried wiping dalvik cache, just cache, and formating the phone from recovery, none of that helped. I dont have any roms saved on my phone or any backups so I am stuck like this and I cant connect my phone to my pc, my pc would recognize it but it wont show up in my computer so I cant access it to to save another rom to it. I tried connecting via recovery (where it goes "download mode do not unplug the device until the process is complete") But that doesnt work, the it would try and install drivers for two "Full JellyBean on Mako" (so it seems like slimrom is based off of a older cm 10 build), but it would come back with no drivers found. When I am in recovery via clockwork my pc recognizes my phone as "Android" but again I still cant do anything with it. Someone please help! I need to fix it by tonight because I am going camping tommorow with family for a few days so having my phone working is a must .
Thanks for those that try to help!
PS I tried using nexus 4 toolkit to reinstall drivers that didnt help.
Click to expand...
Click to collapse
i had the exact same problem, it was stuck at starting apps, then suddenly i heard my phones msg toe go up, so i thought id randomly give a call to the hone, and it rang and showed up the diler, i rejected, jumped in settings, and as it turns our, i had an old version of nova launcher which wasnt compatable with art. and since it was my default launcher ,even though it fc'd android kept trying to launch it i set lg home as default and now its fine phone is lg g2

you can do what is stated above or you can wipe data using stock recovery, not needing any pc, but you will loose all your data

shriom_manerker said:
i had the exact same problem, it was stuck at starting apps, then suddenly i heard my phones msg toe go up, so i thought id randomly give a call to the hone, and it rang and showed up the diler, i rejected, jumped in settings, and as it turns our, i had an old version of nova launcher which wasnt compatable with art. and since it was my default launcher ,even though it fc'd android kept trying to launch it i set lg home as default and now its fine phone is lg g2
Click to expand...
Click to collapse
Download stock images etc
Go into fastboot, use the fastboot toolkit to flash them. That's what I did cause recovery was being weird. This was a while ago though. I dont have a nexus 4 anymore so I can explain how to do it in detail, i broke it and now im stuck with my dumb iphone 4s.

Soft brick but with no adb connection on bootloader

Ok, tired of waiting for the OTA KitKat update for my Nexus 7 2012 tablet, I downloaded the OTA update and sideloaded it with adb. Got a status 7 error and now it's stuck on a bootloop. Thing is, my Windows 8 laptop won't recognize the device anymore (code 43 error on device manager) when on recovery or bootloader. There's even no way to instal google's usb drivers or anything because it says the device malfunctioned. I downloaded the factory image but, obviously, can't sideload it or do anything with it.
Please give me a hand with this, I'm really desperate.

More detail would be nice. What did the bootloop go between? Had you installed any custom recovery like CWM?
Are you still able to access fastboot mode?
Sent from my GT-S5570 using xda app-developers app

nobody_nowhere said:
More detail would be nice. What did the bootloop go between? Had you installed any custom recovery like CWM?
Are you still able to access fastboot mode?
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
Sorry, wasn't sure what you needed. The bootloop esentially goes from recovery to off and then to recovery again. I am able to go to fastboot normally (power and volume down when off).
Wanting to root the device a while ago, I unlocked it and rooted it whitout issues. Since the 4.3 update though, it was a little more difficult to root so having no time to research I just left it at that. That's all that was done to the Nexus 7. No Custom Recovery, no ROM, no nothing. Now, waiting for 3 weeks for KitKat, decided to sideload the OTA update (I did check the version was my device's version) the status 7 error appeared and all hell broke loose with the computer not recognizing the device.

Well, since you still have access to your fastboot menu, there isn't anything to worry about. Once you resolve the driver issue, you must be able to re flash the image.
Sent from my GT-S5570 using xda app-developers app

Duplicate post. Please erase.

nobody_nowhere said:
Well, since you still have access to your fastboot menu, there isn't anything to worry about. Once you resolve the driver issue, you must be able to re flash the image.
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
Yeah, that's what relaxes me a bit, but I can't seem to fix it for 20 hours straight. I use this for studying.

Well, I suggest using another computer (a friend's or relatives') or installing a Linux distro like ubuntu. Oses other than Windows usually don't have such problems. I suggest you download something called adb gui which as I recall did a pretty fine job of 're installing the drivers for me.
But then, please do correct me if I'm wrong... I think that you must first use the device on adb and get the drivers installed and then only can you use it by the fastboot interface.
Sent from my GT-S5570 using xda app-developers app

I used Wug nexus root toolkit to install drivers (windows 8.1) there are clear instructions (if you click manual or something similar) how to get drivers to work.

Yeah, actually I did use the toolkit when I was trying to update to KitKat. Thing is, it doesn't work since the bricking occurred.
Yeah, I'll try on another pc, and I'll keep you posted.
Thanks
Sent from my Nexus 4 using xda app-developers app

I'm having a very similar issue. Mine will try and bootup but just stays on the boot animation for as long as I could wait, 10 minutes or more. bootloader is working just fine and I should be able to use fastboot commands to resolve the issue. I'm not able to get to recovery for one reason or another, but it is updated to the latest CWM.
The trouble I am having is the same though. I cannot for the life of me get the drivers to work. I have tried it on one win8 pc, and one win7 pc. I haven't tried any of the toolkits to help with driver installation on the win8 pc yet. I also have another pc that I am going to try also has win8 on it as well. If you can get the drivers installed, please post a reply as to what you did here, and I will do the same, from what I have been able to find you and I aren't the only ones that are having this issue.
If the windows route doesn't work, I have a copy of Ubuntu that will be going on the computer to see if that resolves my issues. Also, may want to try another cord, I have a couple that are charge cords only. Once getting the drivers working it should be a very simple job.

Johnson90512 said:
I'm having a very similar issue. Mine will try and bootup but just stays on the boot animation for as long as I could wait, 10 minutes or more. bootloader is working just fine and I should be able to use fastboot commands to resolve the issue. I'm not able to get to recovery for one reason or another, but it is updated to the latest CWM.
The trouble I am having is the same though. I cannot for the life of me get the drivers to work. I have tried it on one win8 pc, and one win7 pc. I haven't tried any of the toolkits to help with driver installation on the win8 pc yet. I also have another pc that I am going to try also has win8 on it as well. If you can get the drivers installed, please post a reply as to what you did here, and I will do the same, from what I have been able to find you and I aren't the only ones that are having this issue.
If the windows route doesn't work, I have a copy of Ubuntu that will be going on the computer to see if that resolves my issues. Also, may want to try another cord, I have a couple that are charge cords only. Once getting the drivers working it should be a very simple job.
Click to expand...
Click to collapse
Since you say that you do have ubuntu I suggest using that to fix your issue.... just download and execute the command fastboot from the terminal
Sent from my GT-S5570 using xda app-developers app

nobody_nowhere said:
Since you say that you do have ubuntu I suggest using that to fix your issue.... just download and execute the command fastboot from the terminal
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
Do you think that will be easier? I've not done a whole lot of work with android using linux. I have experience with both separately, but not together. any insight would be fantastic. Have you tried running a linux distro yourself to solve your issue?

Johnson90512 said:
Do you think that will be easier? I've not done a whole lot of work with android using linux. I have experience with both separately, but not together. any insight would be fantastic. Have you tried running a linux distro yourself to solve your issue?
Click to expand...
Click to collapse
It pretty much cancels out any problems with drivers.
It is easy to do.
It takes 5 minutes to boot up and test? Try it for yourself
Sent from my Nexus 5

Johnson90512 said:
Do you think that will be easier? I've not done a whole lot of work with android using linux. I have experience with both separately, but not together. any insight would be fantastic. Have you tried running a linux distro yourself to solve your issue?
Click to expand...
Click to collapse
If I did have any driver issues, the first thing I'd do is reinstall drivers, and if necessary, Windows itself, because I like everything to be working perfectly.
But supposing that that was not an option and I needed my phone or tab real bad, ubuntu would be my first choice. Especially because the concept of installing 'drivers' doesn't exist in ubuntu.
No, that should be fine. As long as you have used terminal before and you know the basics.
Sent from my GT-S5570 using xda app-developers app

nobody_nowhere said:
If I did have any driver issues, the first thing I'd do is reinstall drivers, and if necessary, Windows itself, because I like everything to be working perfectly.
But supposing that that was not an option and I needed my phone or tab real bad, ubuntu would be my first choice. Especially because the concept of installing 'drivers' doesn't exist in ubuntu.
No, that should be fine. As long as you have used terminal before and you know the basics.
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
I appreciate the advice, I will give it a shot this evening, and let you know if this works. I'm sure that it will.

Alright, so I got SDK up and running on Linux! It was a little bit of a pain, but it installed just fine. Once I got it all installed I was able to see the nexus 7 through fastboot! From there I was able to reinstall the bootloader. Then was able to get to recovery to do an adb push to get a rom of 4.4 on to it. 4.4 installed just fine. All problems are fixed Good suggestions guys!

Need help bad

I rooted my nexus 4 with towel root and delete some Google system apps being Google drive and chrome. I was using a few closed modules as well as xposed installer. I was having issues connecting to WiFi so I uninstalled everything but didn't unroot and factory reset my phone the issue now is when I boot up my phone I have no file manager to install apps (Google drive) and no web browser (Google chrome) to connect to the internet. And when I try to log into my Gmail or play store I get an error message saying this service is unavailable at the moment or my device is not provisioned for internet if problem persist contact customer service. I tried to install to unlock the boot loader ad install CWM with the nexus 4 root toolkit some thing went wrong and now there's no stock recovery period. It will still go into bootloader mode but now the phone doesn't even show up as being detectable to the computer. Phone still boots fine I can call and receive incoming calls text work fine as well. If there was some way I can install towel root again and the nexus 4 boot loader unlock app I think I could use flashify to flash clockworkmod so I could put the stock factory Rom on my internal storage wipe the device of the cheap I did and then flash stock 4.4.4 with a Gapps package I'd be okay but since I can't get the computer to recognize my nexus 4 I'm stuck. Please any help is greatly appreciated.

When you boot into the boot loader does the device show up in device manager at all? It'll probably show up but with an exclamation mark on a USB. If it does, right click on it and update driver software, then browes your computer and choose let me pick from a list...... Then choose android adb interface. It'll ask you if you're sure. Just say yes.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
When you boot into the boot loader does the device show up in device manager at all? It'll probably show up but with an exclamation mark on a USB. If it does, right click on it and update driver software, then browes your computer and choose let me pick from a list...... Then choose android adb interface. It'll ask you if you're sure. Just say yes.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Yes it does but when I tried to update the drivers it will not update them. I tried this on Windows xp 32 bit and on a windows 7 64 bit based computer. I tried to manually install the drivers but the computer can't find the drivers on my computer even if I put then into an accessible folder.

x.0ni.x said:
Yes it does but when I tried to update the drivers it will not update them. I tried this on Windows xp 32 bit and on a windows 7 64 bit based computer. I tried to manually install the drivers but the computer can't find the drivers on my computer even if I put then into an accessible folder.
Click to expand...
Click to collapse
Use the "let me pick from a list of devices..." it's right below the option where you would search for software on your computer.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Use the "let me pick from a list of devices..." it's right below the option where you would search for software on your computer.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I tried that too. Still wouldn't locate them.

[Q] broken N4

phone got wiped, os and all. can only get into team win recovery (no android with !). in recovery file manager there is NOTHING on the phone. can not get phone to be recognized by computer. used sdk to install drivers still nothing. can not activate usb debugging as there is no os. reboot in recovery gives warning no os on phone. there is nothing to restore, all folders in install tab are completely empty. is there anyway to save my phone? there is nothing on it...just enough for safe mode and recovery.

You need to get the computer to recognize your device. When booted into recovery and the device connected to your pc go to device manager and see what the issue is.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
You need to get the computer to recognize your device. When booted into recovery and the device connected to your pc go to device manager and see what the issue is.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
got drivers installed sees the device as "android bootloader interface...a link to what to do from this point would work or step by step instruction on how to get os on phone would be great.

Paltirian said:
got drivers installed sees the device as "android bootloader interface...a link to what to do from this point would work or step by step instruction on how to get os on phone would be great.
Click to expand...
Click to collapse
You've got two options
1. Flash the factory image.with fastboot. You'll then have to re-install twrp amrd root
2. Push a rom onto your device using adb in recovery. Then flash that in twrp
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
You've got two options
1. Flash the factory image.with fastboot. You'll then have to re-install twrp amrd root
2. Push a rom onto your device using adb in recovery. Then flash that in twrp
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
ok...it is recognized in fast boot but not in recovery. as far as i knew i only need the usb drivers that come from sdk as it is a google device. is there another driver set i need from recovery. where could i find super simple instructions of how to flash image? and if i didnt care about re rooting could i just use fast boot to flash iamge and run with that?

Paltirian said:
ok...it is recognized in fast boot but not in recovery. as far as i knew i only need the usb drivers that come from sdk as it is a google device. is there another driver set i need from recovery. where could i find super simple instructions of how to flash image? and if i didnt care about re rooting could i just use fast boot to flash iamge and run with that?
Click to expand...
Click to collapse
Simplest way is to download the factory image. Google nexus factory image. It's a .tgz file. Extract it using 7-zip. There's a flash-all.bat file in there. Boot into the bootloader and with your device connected to the pc just double click the flash-all.bat. It will wipe your device so if you can, backup first.
Sent from my Nexus 5 using XDA Free mobile app

You are my freaking hero. I'd give you a hug if i could. Will root tomorrow or so... Have you tried lollipop and would you recommend it over KitKat? Again ty so much

Paltirian said:
You are my freaking hero. I'd give you a hug if i could. Will root tomorrow or so... Have you tried lollipop and would you recommend it over KitKat? Again ty so much
Click to expand...
Click to collapse
No problem, glad you got it working. I like lollipop. It looks different but once you get over the difference you like it. I'm running 5.0.1
Sent from my Nexus 9 using XDA Free mobile app