Related
Hi,
please help me! I hope it is not a brick.
I wanted to make full wipe. I made factory reset in recovery and then wiped sdcard.. Now I cannot boot ROM because there is no one and I have nothing on my SD. So I even cannot copy rom or backup back to phone.
Is there any way out? (
EDIT: I think I can push files (e.g. backup) through adb, right? I installed adb for dummies but when I want to execute SDKmanager.exe. it only opens black window and immediately closes it. I cannot continue
devcager said:
Hi,
please help me! I hope it is not a brick.
I wanted to make full wipe. I made factory reset in recovery and then wiped sdcard.. Now I cannot boot ROM because there is no one and I have nothing on my SD. So I even cannot copy rom or backup back to phone.
Is there any way out? (
EDIT: I think I can push files (e.g. backup) through adb, right? I installed adb for dummies but when I want to execute SDKmanager.exe. it only opens black window and immediately closes it. I cannot continue
Click to expand...
Click to collapse
Access your commands through a terminal window, like start > run > cmd to get into the prompt.
and from there work your way to your directory where you have placed it, and execute the command from that directory directly.
..
Thanks!
In the end I used adb to push backup in recovery...
All this I did because I wanted wipe my device - today I woke up and got a call and found out that my earphone stopped working I am afraid that it is due to condensation and next oxidation... I did not do anything wrong but when you come from cold winter weather into a warm flat it can happen Now I need to send it and hope the warranty will pass..
Anyway, I was looking for complete unroot process and found several advices. I am not clever from them. Is it enough to flash stock ROM? Recovery will be removed as well??
..
Election Day said:
Flash a stock ROM (this will also flash the stock recovery) and relock the bootloader with fastboot oem lock afterwards.
Click to expand...
Click to collapse
Ok. I have everything done but the relocking. Could you tell me how shall I do this? I tried to write "adb reboot bootloader" and then " fastboot oem lock" but both case the command line responded something like that it is not internal command etc. (I dont have it in English) Cannot lock it
devcager said:
Ok. I have everything done but the relocking. Could you tell me how shall I do this? I tried to write "adb reboot bootloader" and then " fastboot oem lock" but both case the command line responded something like that it is not internal command etc. (I dont have it in English) Cannot lock it
Click to expand...
Click to collapse
1.Switch off your phone
2.Connect your phone to your PC throught the USB cable
3.Switch on phone into fastboot
4.Provided that you have the driver for windows for the phone installed open Start/run/cmd (from your PC)
5.From the Android-SDK/platform-tools run the following "fastboot oem lock".
like :
C:\Android-sdk\platform-tools\fastboot oem lock
this will lock it immediately ...
mahanddeem said:
1.Switch off your phone
2.Connect your phone to your PC throught the USB cable
3.Switch on phone into fastboot
4.Provided that you have the driver for windows for the phone installed open Start/run/cmd (from your PC)
5.From the Android-SDK/platform-tools run the following "fastboot oem lock".
like :
C:\Android-sdk\platform-tools\fastboot oem lock
this will lock it immediately ...
Click to expand...
Click to collapse
it works only in "tools" and then it just says "waiting for device" and stucks When I tried "fastboot devices" it says nothing... I tried to reinstall drivers but maybe I have some old version? When I am in Windows copying files etc. it works well.
1. Make sure you open the command prompt IN in the folder with fastboot.exe.
2. Put the phone in fastboot mode.
3. In the command prompt type fastboot devices.
It will now show your serial number. If not its either you are such a noob that you managed to screw that up or the fastboot drivers are not installed. Or both.
albundy2010 said:
1. Make sure you open the command prompt IN in the folder with fastboot.exe.
2. Put the phone in fastboot mode.
3. In the command prompt type fastboot devices.
It will now show your serial number. If not its either you are such a noob that you managed to screw that up or the fastboot drivers are not installed. Or both.
Click to expand...
Click to collapse
OK. I really dont understand what could have been screwed up. Ok. It doesnt show anything. Just nothing. Cen you please send me the link for the drivers which should work? Maybe there is the problem. Fastboot drivers are something else than drivers for adb to be working? Because I dont know whats wrong. Thanks...
devcager said:
OK. I really dont understand what could have been screwed up. Ok. It doesnt show anything. Just nothing. Cen you please send me the link for the drivers which should work? Maybe there is the problem. Because I dont know whats wrong. Thanks...
Click to expand...
Click to collapse
If you have i9023 you need to add a line into the sdk for driver. You can search the tutorial threads for it.
Sent from my Nexus S using Tapatalk
try this
just check if you have fastboot and adb on the same folder, when I've rooted mine's got this issue, if cmd report "the command is an external one" simply means there is no such program in the folder you are in
copy both adb and fastboot in tools and platform-tools too, so you can run the command in both folder
cd>desktop > cd android>cd android-sdk> cd tools (then run adb or fastboot)
cd>desktop > cd android>cd android_sdk> cd platform-tools (thr run adb or fastboot)
1. Find out exactly what phone model you have if you don't know already.
2. Do the same for your computers os . Including 32 or 64 bit.
3. Combine that info and search the forum or just Google search. How to install fastboot drivers for phone model in step 1 with the os in step 2.
..
Thank you all. I decided to unroot it and relock it using Odin software which was great and quick. So I am done.... Adb has a lot of problems with drivers, commands, paths. This way was much easier
adb has no issues. User error.
albundy2010 said:
adb has no issues. User error.
Click to expand...
Click to collapse
+1
Sent from my GT-I9100 using XDA App
albundy2010 said:
adb has no issues. User error.
Click to expand...
Click to collapse
Maybe you are right. Maybe it was driver problem which I solved and then immediately used odin. Anyway, it is user friendly and I am finally done with what I wanted
albundy2010 said:
adb has no issues. User error.
Click to expand...
Click to collapse
Agreed, but not the user friendliest.
For the OP: Good luck having it repaired!
I wiped the system thinking it was part of the system factory reset in TWRP but i didnt know that it would result in it saying NO OS INSTALLED. i read other similar threads about this problem but dont exactly understand what to do and how to restore my phone. i have a nandroid backup but its on my pc and not the internal storage on the phone. im fairly new to this so those replying, please explain exactly what to do. Im so scared about what to do now :crying::crying::crying:
Don't be scared its common and very, very easy to fix
Now I don't use TWRP so I have no idea of the directory structure so I can't advise you exactly.
But what you will essentially do is use adb push to get the files on your phone.
Click the link in my signature to go to the sticky roll up thread. All the important threads are linked there. Y
In that thread you'll quickly find my adb info thread. This should be most of what you need to know
Sent from my Nexus 5 using Tapatalk
First relax, your phone is not ruined. I assume you have a custom recovery. You're going to have to either side load a rom zip using adb or adb push a rom zip onto your phone and flash it in recovery.
Edit, OP you'll want to push the rom to /sdcard/Download. That'll put it into the folder twrp defaults to look for it.
Sent from my Nexus 5 using XDA Free mobile app
Well, you have three pretty easy options.
TWRP supports ADB commands, but the stock Google driver won't work. If you install the Universal ADB Driver you should be able to push your backup to your device (adb push [file location on your computer] [where to push on your phone])
http://www.koushikdutta.com/post/universal-adb-driver
You could also flash a ROM through adb sideload. Download a ROM zip to your computer, then in TWRP choose Advanced -> ADB Sideload. Then run "adb sideload [zip file]" to sideload the ROM you downloaded.
Last, you can restore to the Nexus Factory Image.
https://developers.google.com/android/nexus/images
All of these options will require you to have the Android SDK setup on your computer. The link for the factory images has instructions on how to get that installed.
raptir said:
]
All of these options will require you to have the Android SDK setup on your computer. The link for the factory images has instructions on how to get that installed.
Click to expand...
Click to collapse
Luckily its easier install adb and fastboot than the ask method. Just go to the thread mentioned earlier and use the 15 second installer
OP, no matter what you'll need run that installer
Sent from my Nexus 5 using Tapatalk
All these guys have it spot on! I just wanted to mention that when you install a ROM system gets wiped automatically as this is a parameter in the zip's updater-script.
So in other words there is really no reason to wipe system manually. Just let the install process do it for you. If u wipe system manually and then you realize you do not have a ROM zip or a nandroid only ADB can save you. So this way you can save yourself a headache
raptir said:
Well, you have three pretty easy options.
TWRP supports ADB commands, but the stock Google driver won't work. If you install the Universal ADB Driver you should be able to push your backup to your device (adb push [file location on your computer] [where to push on your phone])
\
You could also flash a ROM through adb sideload. Download a ROM zip to your computer, then in TWRP choose Advanced -> ADB Sideload. Then run "adb sideload [zip file]" to sideload the ROM you downloaded.
Last, you can restore to the Nexus Factory Image.
All of these options will require you to have the Android SDK setup on your computer. The link for the factory images has instructions on how to get that installed.
Click to expand...
Click to collapse
I downloaded everything and ran the flash-all . bat file but its currently been on < waiting for device > for a while now. i think it didnt detect the phone although it is connected through the USB :/
thauri said:
I downloaded everything and ran the flash-all . bat file but its currently been on < waiting for device > for a while now. i think it didnt detect the phone although it is connected through the USB :/
Click to expand...
Click to collapse
Did you or did you not read my adb and fastboot thread?
And WHY are you going for the last resort first???
You really need to chill out and read things because I don't think you're thinking straight
Sent from my Nexus 5 using Tapatalk
raptir said:
Well, you have three pretty easy options.
TWRP supports ADB commands, but the stock Google driver won't work. If you install the Universal ADB Driver you should be able to push your backup to your device (adb push [file location on your computer] [where to push on your phone])
You could also flash a ROM through adb sideload. Download a ROM zip to your computer, then in TWRP choose Advanced -> ADB Sideload. Then run "adb sideload [zip file]" to sideload the ROM you downloaded.
Last, you can restore to the Nexus Factory Image.
All of these options will require you to have the Android SDK setup on your computer. The link for the factory images has instructions on how to get that installed.
Click to expand...
Click to collapse
rootSU said:
Luckily its easier install adb and fastboot than the ask method. Just go to the thread mentioned earlier and use the 15 second installer
OP, no matter what you'll need run that installer
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
yeah i did download the 15 second ADB installer but my computer isnt detecting the phone connected when i ran the flash-all . bat file.
1) you need to read the whole of my thread. There are drivers to install
2) Still dont understand why you're running flashall bat when you can just adb push your backup to your sdcard. You know you lose all your data when you do that?
Sent from my Nexus 5 using Tapatalk
rootSU said:
1) you need to read the whole of my thread. There are drivers to install
2) Still dont understand why you're running flashall bat when you can just adb push your backup to your sdcard. You know you lose all your data when you do that?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
ok yes im reading your thread and doing the ADB commands. i have a question though, the multi-line input for the code to ADB push goes in cmd right? how is that possible?
Yes
Type one line, press enter, type another line, press enter
Sent from my Nexus 5 using Tapatalk
rootSU said:
Yes
Type one line, press enter, type another line, press enter
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
when i press enter after adb shell and mount data, it says data failed : Device or Resource busy
thauri said:
when i press enter after adb shell and mount data, it says data failed : Device or Resource busy
Click to expand...
Click to collapse
If "mount data" shows device or resource busy, then that usually means it is already mounted.
rootSU said:
If "mount data" shows device or resource busy, then that usually means it is already mounted.
Click to expand...
Click to collapse
i did everything but in the last part, it doesnt transfer the recovery files to the phone
Edit: The files are transferring successfully but only one at a time.
EDIT 2: All the necessary files were transferred but the TWRP recovery mode isnt detecting it as a restore option
Messing up is scary but it's a great opportunity to learn. I think you'll get through this just fine.
thauri said:
i did everything but in the last part, it doesnt transfer the recovery files to the phone
Edit: The files are transferring successfully but only one at a time.
EDIT 2: All the necessary files were transferred but the TWRP recovery mode isnt detecting it as a restore option
Click to expand...
Click to collapse
It must be in the exact location twrp needs to see it.
Sent from my Nexus 5 using Tapatalk
rootSU said:
It must be in the exact location twrp needs to see it.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I did, I put it in the backup folder in TWRP where all the other backups usually were
thauri said:
I did, I put it in the backup folder in TWRP where all the other backups usually were
Click to expand...
Click to collapse
Take a new backup, then delete everything in the new backup folder and move everything from your old backop into the new backup folder,
So for example
Code:
adb shell
mount /data
cd /data/media/0/TWRP/backups
ls
^^ This should list the contents... You should see your old backup and your new backup (which will be mostly empty).
Lets pretend your new backup folder is 22222222 and your old backup folder is 11111111
Code:
rm -Rf 222222222/*
mv 111111111/* 222222222
The first command is a remove (recursive) of the contents of the new backup. second command mvs contents of old backup into new backup folder,
Try that.
I don't know TWRP so my assumptions of the path may be incorrect
Someone else posted twrp default path as /sdcard/downloads - try that.
I try to hard reset but I'm still stuck on loading screen. How do I add a zip file to my sd so I can flash it, since it doesn't even detect my oneplus on my computer? Please help me and lend me your knowledge and power =].
Can you boot in bootloader and connect it through adb and fastboo with your pc? in that case it would be easy to reflash everything
I can boot into fastboot and TWRP but I'm wondering how can I add file into my internal hard drive since it doesnt detect the phone on my computer?
Any help with some instructions would be really nice =] :good:
Do you see it using "adb devices" or "fastboot devices" ?
If not, you must update your adb drivers on your computer and reboot it
right now its on MTP USB Device as my device on my Device Manager, can you link me to the proper usb driver? Because I"m pretty sure I updated it and it was working while my phone is working. Also how can I check if its using adb devices?
bud77 said:
Do you see it using "adb devices" or "fastboot devices" ?
If not, you must update your adb drivers on your computer and reboot it
Click to expand...
Click to collapse
Also it said "Windows has determined the driver software for your device is up to date" but doesnt detect my phone?
Anyone still here so they can help me?
So as asked previously, when you connect via fastboot, and boot it into TWRP, do you see it via adb ("adb devices" command in the platform-tools folder)? Did you try adb push <filename> /sdcard/ ?
yes i see adb push , but there's no file there. How can i add file there?
Dzhedaj said:
So as asked previously, when you connect via fastboot, and boot it into TWRP, do you see it via adb ("adb devices" command in the platform-tools folder)? Did you try adb push <filename> /sdcard/ ?
Click to expand...
Click to collapse
Basically i'm in TWRP and i dont see any thing in recover or etc or in my sd, all blank so how can I put an image there to flash?
Anyone still here to have any answers to help?
which jeithis
http://i.imgur.com/378HzRp.png also get this image also
Use an adb push command to send a ROM zip to your phone.
Transmitted via Bacon
@M I N E, go read the sticky posts in the general section. It will explain how to do an adb push command.
@timmaaa and others have done a great job with some write ups for this device.
timmaaa said:
Use an adb push command to send a ROM zip to your phone.
Transmitted via Bacon
Click to expand...
Click to collapse
Or do a factory wipe then go into TWRP -> Advanced -> ADB Sideload -> Swipe
adb sideload <name-of.zip>.zip (ensure the .zip is in the same folder as your fastboot/adb) and then it'll send the zip over to the phone and flash.
I prefer the adb sideload method as it pretty much pushes the file over to the phone and then flashes it afterwards.
Either method is fine though.
If OP has problems with drivers, I recommend using http://forum.xda-developers.com/showthread.php?t=2386956 they work great.
what is the push load command? How can i push something if i dont have any file on my phone to flash? can you guys type out the command?
M I N E said:
what is the push load command? How can i push something if i dont have any file on my phone to flash? can you guys type out the command?
Click to expand...
Click to collapse
Read the post above you that I posted. Use that command as well as the instructions and you can flash a file using adb sideload.
well I try factory swipe nothing there, i check the TWRP , no files is there i mean nothing. And I cant do adb push because my when i type adb devices it doesnt recognized, because how can i turn on debugging if my phone doesnt have any rom?
M I N E said:
well I try factory swipe nothing there, i check the TWRP , no files is there i mean nothing. And I cant do adb push because my when i type adb devices it doesnt recognized, because how can i turn on debugging if my phone doesnt have any rom?
Click to expand...
Click to collapse
You're not reading my message properly. I'm telling you to do adb sideload. Please read what I said carefully word-by-word.
Or do a factory wipe then go into TWRP -> Advanced -> ADB Sideload -> Swipe
adb sideload <name-of.zip>.zip (ensure the .zip is in the same folder as your fastboot/adb) and then it'll send the zip over to the phone and flash.
I prefer the adb sideload method as it pretty much pushes the file over to the phone and then flashes it afterwards.
Click to expand...
Click to collapse
The whole point of adb sideload is that you're sideloading a flashable zip that is not on your phone but on your computer and you're pushing the file onto your phone which will followup with flashing the zip.
You need to be typing adb sideload on your computer with the proper environment for adb set up with the proper drivers installed if you haven't already.
I screwed up trying to restore and now it says the phone is not rooted and has no OS installed on it. I still have access to the custom recovery if that helps. I have tried using ADB and Fastboot but it does not seem to be working. I need to know asap because it is for my dad and he travels a lot. He needs a phone. Please any help is appreciated.
1.Flash twrp
2. Go to adb sideload
3. In the terminal type adb sideload filename.zip
The ROM will flash and that's it.
If you need it back to stock just google "nexus 5 factory image" then download the latest one and follow the instructions given by google.
Also are you running linux (which distro) or windows just so I know what to tell you if that doesn't work
First of al: It's best to not use Windows 8 since there have been some driver incompatibilities and I'm not sure if they have been completely fixed yet.
Install 'Universal Naked Driver' and 'Minimal ADB and fastboot'. Both can be found here on xda.
Download the latest factory image for hammerhead from Google website. Extract the downloaded file twice and copy over everything to your 'Minimal ADB and fastboot' install dir.
Double click the flash-all.bat while your phone is in bootloader mode.
This will COMPLETELY reset your phone (all personalbdata will be wiped). Only the bootloader will stay unlocked.
awsumatt said:
1.Flash twrp
2. Go to adb sideload
3. In the terminal type adb sideload filename.zip
The ROM will flash and that's it.
If you need it back to stock just google "nexus 5 factory image" then download the latest one and follow the instructions given by google.
Also are you running linux (which distro) or windows just so I know what to tell you if that doesn't work
Click to expand...
Click to collapse
When trying step 3, it says cannot read sideload.
The command is not "sideload filename.zip" but
"adb sideload filename.zip"
Did you enter it correctly?
What does the terminal say as an error? And are you running Linux, Mac, or windows?
experience7 said:
The command is not "sideload filename.zip" but
"adb sideload filename.zip"
Did you enter it correctly?
Click to expand...
Click to collapse
Yes that is exactly how i entered it but with the file name of course. Although I did try your method but i don't see any file called flash-all.bat.
So just gonna ask again, what message did you get in the terminal?
Did you extract it twice? There should be a tgz file at some point... this one can be extracted as well (using 7-zip for example)
experience7 said:
The command is not "sideload filename.zip" but
"adb sideload filename.zip"
Did you enter it correctly?
Click to expand...
Click to collapse
okay nevermind my last comment. Now it says fastboot is not recognizable internal or external command. Press any key to exit
After you copied all the files into the Minimal ADB and fastboot folder the flash-all.bat should be in the same directory as fastboot.exe. Is this the case?
Try adb kill-server then (I'm a little rusty with windows) su adb start-server
experience7 said:
Did you extract it twice? There should be a tgz file at some point... this one can be extracted as well (using 7-zip for example)
Click to expand...
Click to collapse
Okay after I run the flash-all.bat, it just hangs at waiting for device
Install the 'Universal Naked Driver', reboot your computer and try again.
Again: The phone has to be in bootloader mode (you have to see the green android)
experience7 said:
Install the 'Universal Naked Driver', reboot your computer and try again.
Again: The phone has to be in bootloader mode (you have to see the green android)
Click to expand...
Click to collapse
I've decided to take the loss on this one. I just do not have time for this. I'll just go get it replaced. Thank you so much for the help. I'll definitely use XDA for more of my android problems in the future. Thank you again and to everyone who replied to this thread.
sbecerra407 said:
I've decided to take the loss on this one. I just do not have time for this. I'll just go get it replaced. Thank you so much for the help. I'll definitely use XDA for more of my android problems in the future. Thank you again and to everyone who replied to this thread.
Click to expand...
Click to collapse
Install this(fastboot + adb): http://forum.xda-developers.com/showthread.php?t=2588979
Download the file for Nexus 5: https://developers.google.com/android/nexus/images
Extract the file
Connect phone to pc in bootloader mode
Double click in flash all script
Wait for it to finish
sbecerra407 said:
When trying step 3, it says cannot read sideload.
Click to expand...
Click to collapse
ofc... you need to ENABLE sideload on twrp itself..
Thread cleaned.
Let's keep it on topic guys,
Hi,
I did an advanced wipe wiping everything - Dalvik cache, system, data, internal storage and cache.
Now, when I try to reboot, it says no OS and keeps bringing me back to TWRP. I tried the install feature but looks like there's no file in it either. My PC does not detect my phone as a hardware I think as when I tried to copy the ZIP file to it using another post which I'm not allowed to post here, the cmd commands for adb and mkdir were not recognized.
Can someone please help me salvage my phone?
In case any more details are required about the phone, happy to provide.
dheerajc17 said:
Hi,
I did an advanced wipe wiping everything - Dalvik cache, system, data, internal storage and cache.
Now, when I try to reboot, it says no OS and keeps bringing me back to TWRP. I tried the install feature but looks like there's no file in it either. My PC does not detect my phone as a hardware I think as when I tried to copy the ZIP file to it using another post which I'm not allowed to post here, the cmd commands for adb and mkdir were not recognized.
Can someone please help me salvage my phone?
In case any more details are required about the phone, happy to provide.
Click to expand...
Click to collapse
Go to Device management, you'll find the android composite device there. Change the driver to MTP device.
you can also try using adb sideloas
I assume you use Windows? It's probably just a driver issue. I always install official Google Android SDK, which contains proper USB drivers. Once you install it, your phone should be recognized by PC, while in TWRP.
daedric said:
Go to Device management, you'll find the android composite device there. Change the driver to MTP device.
Click to expand...
Click to collapse
Sorry, but am new to this. Can you please provide instructions to get my phone back to normal.
Thanks in advance
aciupapa said:
you can also try using adb sideloas
Click to expand...
Click to collapse
Sorry, but as am new to this, can you please help with instructions on how can I get my phone back to normal?
Thanks,
focus-pocus said:
I assume you use Windows? It's probably just a driver issue. I always install official Google Android SDK, which contains proper USB drivers. Once you install it, your phone should be recognized by PC, while in TWRP.
Click to expand...
Click to collapse
It is now visible in Android monitor in the studio but still doesn't show up as a connected device on the PC.
Anyways, the cmd doesn't recognize the adb command. can you please help with how can I bring my phone back to normal?
dheerajc17 said:
It is now visible in Android monitor in the studio but still doesn't show up as a connected device on the PC.
Anyways, the cmd doesn't recognize the adb command. can you please help with how can I bring my phone back to normal?
Click to expand...
Click to collapse
You need to add path to adb.exe to Windows PATH variable, then reboot and cmd should recognize adb commands, or you can just navigate to folder with adb.exe in cmd. Then check if adb can see your device, if it does, then just do adb sideload of ROM, and flash your ROM in TWRP.
If it's all too complicated, just return to stock using instructions from Google factory image website.
Put a rom on a flash drive, and connect it to your phone. In TWRP, go into "Mount" options, mount the flash drive (cant remember the exact wording), and then...can't remember quite vividly how, but it's easy from there to navigate inside your flash drive and install the rom.
REMEMBER: the flash drive should be formatted in FAT32 for TWRP to recognize it.