Not needed..............
@jmz will this work on OS 4.5.2
krazyace35 said:
@jmz will this work on OS 4.5.2
Click to expand...
Click to collapse
I don't see why it wouldn't as I am on 4.5.3 and it worked.
jmz said:
I don't see why it wouldn't as I am on 4.5.3 and it worked.
Click to expand...
Click to collapse
Cool thanks I'll give it a try and thanks for this unlock tutorial
jmz said:
You will need a linux box or python installed on windows. Find instructions on the web for that.
Step 1: Download attachment
Step 2: Run command and make note of code return
Code:
adb shell cat /sys/block/mmcblk0/device/manfid
Step 3: Run command and make note of code return
Code:
adb shell cat /sys/block/mmcblk0/device/serial
Now you should have 2 sets of numbers. first should be in the format of 0x0000XX where XX is numbers. And the other is 0xSSSSSSSS.
So now use the downloaded file and execute (obivously replacing the entries with what was returned above.
Code:
./cublock.py XX SSSSSSSS
This will tell you you have unlock.signed now. So move that to your fastboot/adb directory and then reboot to bootloader and issue this command
Code:
adb reboot-bootloader
fastboot -i 0x1949 flash unlock unlock.signed
Once done, get back to android and do the following:
Code:
adb shell
su
idme print
You should now see unlock_code: AAAAAAAA and on and on.
Now go flash my TWRP build in OG dev
Original credit goes to @dpeddi & @vortox for the exploit. I did nothing to this code and it is all their work. So give them thanks
Click to expand...
Click to collapse
Sorry for the noob-ish question. How do you get adb to recognize the fire? When I type "adb devices" there are no devices present.
ryanyz10 said:
Sorry for the noob-ish question. How do you get adb to recognize the fire? When I type "adb devices" there are no devices present.
Click to expand...
Click to collapse
do steps 1 through 6 in this thread
http://forum.xda-developers.com/fire-hd/general/root-supersu-stable-appstore-custom-t3113311
Question
Sorry for another question. When I type ./cublock.py, I get ". is not recognized as an internal or external command".
Sorry again for being annoying lol
ryanyz10 said:
Sorry for another question. When I type ./cublock.py, I get ". is not recognized as an internal or external command".
Sorry again for being annoying lol
Click to expand...
Click to collapse
if on windows you need to get python installed
jmz said:
if on windows you need to get python installed
Click to expand...
Click to collapse
I've got python 3.4.2 installed. Which version would you recommend?
After some researching, people have said that python doesn't work very well on Windows 10, which is what I'm on right now.
jmz said:
You will need a linux box or python installed on windows. Find instructions on the web for that.
Step 1: Download attachment
Step 2: Run command and make note of code return
Code:
adb shell cat /sys/block/mmcblk0/device/manfid
Step 3: Run command and make note of code return
Code:
adb shell cat /sys/block/mmcblk0/device/serial
Now you should have 2 sets of numbers. first should be in the format of 0x0000XX where XX is numbers. And the other is 0xSSSSSSSS.
So now use the downloaded file and execute (obivously replacing the entries with what was returned above.
Code:
./cublock.py XX SSSSSSSS
This will tell you you have unlock.signed now. So move that to your fastboot/adb directory and then reboot to bootloader and issue this command
Code:
adb reboot-bootloader
fastboot -i 0x1949 flash unlock unlock.signed
Once done, get back to android and do the following:
Code:
adb shell
su
idme print
You should now see unlock_code: AAAAAAAA and on and on.
Now go flash my TWRP build in OG dev
Original credit goes to @dpeddi & @vortox for the exploit. I did nothing to this code and it is all their work. So give them thanks
Click to expand...
Click to collapse
Hi jmz,
I have a question here- all that was in your ZIP file was the cublock.py file.
Are we supposed to use this with the rest of draxie's tools in the HDX thread? If so, I was able to get an 'unlock.img' file, but nothing called 'unlock.signed'
maybe you didn't upload all the attachments we needed?
either way, thanks soooo much for your work !
edouble312 said:
Hi jmz,
I have a question here- all that was in your ZIP file was the cublock.py file.
Are we supposed to use this with the rest of draxie's tools in the HDX thread? If so, I was able to get an 'unlock.img' file, but nothing called 'unlock.signed'
maybe you didn't upload all the attachments we needed?
either way, thanks soooo much for your work !
Click to expand...
Click to collapse
sorry, with that tool you only get the unlock.img . I need to correct the post
In my linux box 'cuber' module, required by cublock.py, is not installed; is this the correct source? https://github.com/benesch/cuber
One more question: I forgot to block OTA update so my HD6 updated to 4.5.4, loosing root permissions. What I should do? Need to wait KingRoot supports the new software version or can I proceed to unlock bootloader and install twrp? Or could install, if available, a 4.5.3 recovery through dd? Very thanks.
I sense many roms being ported very soon...
Sure hope so!
I used the tools (cuber) in this post:
http://forum.xda-developers.com/kin...tools-create-unlock-img-fix-boot-img-t3050689
So i generated unlock.img, but i am still unable to enter fastboot mode,
i tried changing boot to 4002, i rooted and tried to execute fastboot file, nothing works tbh, how do you suppose i fix this?
thanks in advance
robert896 said:
So i generated unlock.img, but i am still unable to enter fastboot mode,
Click to expand...
Click to collapse
Need more info: Your computer OS, tablet device model (Settings>Device Options), Fire OS version (Device Options>System Updates). Tell exactly what happens when you run: adb reboot-bootloader.
DoLooper said:
Need more info: Your computer OS, tablet device model (Settings>Device Options), Fire OS version (Device Options>System Updates). Tell exactly what happens when you run: adb reboot-bootloader.
Click to expand...
Click to collapse
ok im on ubuntu 15.04 got full adb and fastboot (they work on other devices) --- fire os 4.4.3---device model, kfhd 3rd gen
i also have windows 7 x64 dual booted with full adb and fastboot set up also
when i do adb reboot-bootloader, it restarts but doesnt enter fastboot ,, it boots into normal mode
robert896 said:
device model, kfhd 3rd gen
Click to expand...
Click to collapse
These unlock instructions are for Fire HDs (4th gen). You need a fastboot cable for KFSOWI. Try G+ KFSOWI modding.
I am new to the tablet scene. This is my very first tablet. I would like to root the device and install custom recovery and hopefully custom Rom. Is this the first thing I do or should I start somewhere else?
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 ditched windows ages ago and i will never look back i am sick and tierd of waiting on moto uk to push ics. i use to have the dell streak and i rooted that but i was on windows then how do i root my xoom with linux mint is it possible and can any point me in the right direction please
Stand by, I will give you all the tools and options you need to do so, I could draft something tomorrow morning.
Sent from my PG86100 using Tapatalk
Thank you megabiteg Still learning linux but i Love it
megabiteg said:
Stand by, I will give you all the tools and options you need to do so, I could draft something tomorrow morning.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
well, it isn't that hard since everything you really need on your computer ist fastboot and a way to push a file to an sdcard (fat formatted)...
Just go here, download and install the android sdk from there. Make sure the commands adb and fastboot are in your path. (test by issuing adb devices, shold return a list of attached android devices with usb debugging turned on)
After that, just follow these instructions. I am not sure if you need to run fastboot as root, but you'll see
Cheers for the info just by any chance do you know the commands still learning Linux
llama-power said:
well, it isn't that hard since everything you really need on your computer ist fastboot and a way to push a file to an sdcard (fat formatted)...
Just go here, download and install the android sdk from there. Make sure the commands adb and fastboot are in your path. (test by issuing adb devices, shold return a list of attached android devices with usb debugging turned on)
After that, just follow these instructions. I am not sure if you need to run fastboot as root, but you'll see
Click to expand...
Click to collapse
elsworth1983 said:
Cheers for the info just by any chance do you know the commands still learning Linux
Click to expand...
Click to collapse
thought you ditched windows ages ago?
anyhow... don't have linux set up atm, so this will from memory and might contain some errors... Also, never tried mint, I always stuck to debian or debian-derivates...
anyhow, lets try this:
first, use your package management-system to install a jre (java runtime environment.
If that is set up, install the android sdk:
Code:
$ cd ~
$ wget http://dl.google.com/android/android-sdk_r17-linux.tgz
$ sudo su
[enter your su-password]
# cd /usr/local
# tar xfzv ~[yourusername]/android-sdk_r17-linux.tgz
# ./android-sdk-linux/tools/android
a window should open up and list some files available for download. Just select "Android SDK Platform-tools" and hit "Install 1 package...".
once that's finished (might take a while), close the Android SDK Manager and you should get back to your shell.
Code:
# ln -s /usr/local/android-sdk-linux/platform-tools/adb /usr/local/bin/adb
# ln -s /usr/local/android-sdk-linux/platform-tools/fastboot /usr/local/bin/fastboot
# exit
$ rm android-sdk_r17-linux.tgz
now, connect your xoom to your computer and enable usb debugging in the settings of your xoom. If you issue adb devices, you should get something like
Code:
List of devices attached
043c12343456476547 device
if you receive something like bash: adb: command not found, something went wrong somewhere. Try the same using sudo: sudo adb devices if that doesn't fix it please write another post.
Also, if you encounter an error after entering any of the comments above, please do not continue until you resolved that error. (For example ask for a solution here)
And, since you are still learning to use linux: whenever instructions contain a $ or # at the beginning of a line, DO NOT ENTER THESE. They are just there to tell you to issue that command as normal user ($) or superuser (#)
/EDIT: btw: there may be an easier way to do this if you just want to use adb/fastboot this once: you could try to simply download the adb and fastboot- binaries and put these into the folder with your recovery.img-file. Might work, not sure about that, though. Also, since I don't have linux installed on my machine atm, I can't provide you with a link to these binaries.
cheers for all your help will give this a go "Dont want to back to windows
Android SDK manger log
Error Stopping ADB server failed (code-1)
Connected the xoom and did adb devices and it listed the xoom with no errors in the terminal Thank you again ? Were do i go from here now
glad to read it's working
just follow the instructions in this thread That will help you to install a custom recovery and root your xoom. It will not, however, install a custom rom. To do that, you'd also need to download a custom rom (usually comes in a flashable .zip-file), place that on an acutal sd-card which you're gonna put into your xoom, and install that file from within the custom recovery. Just make sure you grab a rom that works with your xoom (for example, you shouldn't put a us-4g-rom onto a wifi-only-xoom and vice versa)
have i done something wrong
god-WE174AA-ABU-s5306uk god # adb reboot bootloader
god-WE174AA-ABU-s5306uk god # fastboot oem unlock
fastboot: command not found
The problem i seem to be having is when the xoom is on i type <adb reboot bootloader> The xoom reboots to the fastboot screen after that no commands work and when i do ADB devices in the terminal the device list is empty ?
elsworth1983 said:
have i done something wrong
god-WE174AA-ABU-s5306uk god # adb reboot bootloader
god-WE174AA-ABU-s5306uk god # fastboot oem unlock
fastboot: command not found
Click to expand...
Click to collapse
have you done the # ln -s /usr/local/android-sdk-linux/platform-tools/fastboot /usr/local/bin/fastboot? The error you're getting seems to suggest that it can't find the fastboot application? What happens if you type /usr/local/android-sdk-linux/platform-tools/fastboot oem unlock?
elsworth1983 said:
The problem i seem to be having is when the xoom is on i type <adb reboot bootloader> The xoom reboots to the fastboot screen after that no commands work and when i do ADB devices in the terminal the device list is empty ?
Click to expand...
Click to collapse
that is expected. adb is only available while android is booted up, fastboot is the protocol to use while in bootloader mode. As indicated before, I suspect that your computer can't find the fastboot application (on the computer).
Cheers for all the info i went back and started all from the top again only thing i am struggling with is Flashing the recovery now lol i get
god-WE174AA-ABU-s5306uk god # adb reboot bootloader
god-WE174AA-ABU-s5306uk god # fastboot flash recovery recovery-solarnz-100611-1150.img
error: cannot load 'recovery-solarnz-100611-1150.img'
I have it on a memory card which i checked which was working
elsworth1983 said:
Cheers for all the info i went back and started all from the top again only thing i am struggling with is Flashing the recovery now lol i get
god-WE174AA-ABU-s5306uk god # adb reboot bootloader
god-WE174AA-ABU-s5306uk god # fastboot flash recovery recovery-solarnz-100611-1150.img
error: cannot load 'recovery-solarnz-100611-1150.img'
I have it on a memory card which i checked which was working
Click to expand...
Click to collapse
The recovery image needs to be on your pc. It doesn't matter where on your pc as long as you can access it and know where it is.
Fastboot works by sending the image over the usb cable. Once you start flashing roms, those will need to be on your sd card within the xoom.
all i can say is thank you for all the information every 1 is giving me my head is mashed lol so if i put recovery-Tiamat-R4c-100611-1150-cwm.img on the desktop what would the terminal code be
kofrad said:
The recovery image needs to be on your pc. It doesn't matter where on your pc as long as you can access it and know where it is.
Fastboot works by sending the image over the usb cable. Once you start flashing roms, those will need to be on your sd card within the xoom.
Click to expand...
Click to collapse
depends on where your desktop is If it is in ~/Desktop/, then the correct command should be
Code:
fastboot flash recovery ~/Desktop/recovery-Tiamat-R4c-100611-1150-cwm.img
error: cannot load '/root/Desktop/recovery-Tiamat-R4c-100611-1150-cwm.img'
ARRRR i am really loosing the will to live ;-)
What am doing so wrong its lucky am not bold yet been trying this all day
elsworth1983 said:
error: cannot load '/root/Desktop/recovery-Tiamat-R4c-100611-1150-cwm.img'
ARRRR i am really loosing the will to live ;-)
Click to expand...
Click to collapse
if the graphical interface, where do you see the file located?
elsworth1983 said:
error: cannot load '/root/Desktop/recovery-Tiamat-R4c-100611-1150-cwm.img'
ARRRR i am really loosing the will to live ;-)
Click to expand...
Click to collapse
Sounds to me like you are running the commands as root. You likely have also downloaded the recovery image as a normal user. This means the '~' shortcut for the home directory is pointing you to someplace where the file is not.
Try using "fastboot flash /home/Your username/Desktop/recovery-Tiamat-R4c-100611-1150-cwm.img"
I have put the file on the desktop ? is that what u mean
Well I am trying to Flash the latest fagyi NAND for Blackstone - http://forum.xda-developers.com/showthread.php?t=1914723
So I did everything, but when I reached the fastboot thingy, I did this:
After ROM flashed, took batter out and restarted device.
Blue screen showed up, forced fastboot, ready USB state, so I connected to PC
Then I opened a command prompt, so now what should I enter in the command prompt! I am using fagyi's fastboot!
Thanks, in advance!
Sorry for double posting, but please someone answer me, or atleast give me a tip/advice!
Do you mean this part?
13. Now connect the Blackstone to your Windows OS and open a CLi/Command prompt
14. Within CLi go to the directory where you place the 'adb files & fastboot.exe' files (from step 2)
15. Type: fastboot flash recovery recovery.img (this will flash install the custom CWR)
16. Then type: fastboot boot recovery.img (this will reboot your Blackstone into CWR)
Click to expand...
Click to collapse
post-mortem said:
Do you mean this part?
Click to expand...
Click to collapse
Yeah that exactly!
Step 2 says
2. Extract the 'adb files & fastboot.exe' files to a folder
Click to expand...
Click to collapse
so the 1st question is, do you know what folder you put those files in? Note that we're talking about your computer, not your phone. On your computer, open a command prompt by doing Start -> Run... -> cmd (This is Step 13). Navigate to the folder from Step 2 This is Step 14). Then, type the appropriate commands from Steps 15 & 16.
Still don't get it? Ask away!
Um the files are placed in C:
And when I enter the commands, it says 'File too big to fit in memory"? What do I do now?
So your step 14 should be to type cd c:\, then 15 fastboot flash recovery recovery.img
Is that when you get the error?
Yes, exactly then!
Ok, try redownloading the fastboot program, or install the Android SDK to get the newest version directly from Google.
I've redowloaded it alot of times! And I already have the Android SDK and am using the latest one!
Are you sure that you're using the correct version of all relevant programs? By that, I mean 32 vs 64-bit.
I am not sure about that, how should I know?
Do you get the same error if you type fastboot devices ?
I havent typed that yet!
EDIT: No I get this - "RH104393397 fastboot"
Please Admin/Moderator, lock this thread, my problem is now fixed!
Angat said:
Please Admin/Moderator, lock this thread, my problem is now fixed!
Click to expand...
Click to collapse
Can you tell me how do you fix the problem ? I have the same problem
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,
So I finally undated my PC from Ubuntu 12.04 to 16.04. The good new is I have full MTP access to my G3 now. However, ADB is no longer recognized. ADB and Fastboot are located on a separate drive from the OS, so I am trying to run the same file from the same HD. Any suggestions?
You need to run adb in root. Are you doing that?
Sent from my SM-T530NU using XDA-Developers mobile app
How are you trying to use ADB? It doesn't work when your phone is on fastboot mode
Tel864 said:
You need to run adb in root. Are you doing that?
Sent from my SM-T530NU using XDA-Developers mobile app
Click to expand...
Click to collapse
I did try that without success even though I successfully ran ADB without root with 12.04. Only Fastboot needed root.
For some reason the file is not recognized as an executable file. Below is a screen copy:
Code:
$ ls
adb fastboot twrp-osprey-3.0.0-r2.img
commands.txt twrp-osprey-2.8.7-r5.img twrp-osprey-3.0.2-r1.img
$ adb
The program 'adb' can be found in the following packages:
* adb
* android-tools-adb
Try: sudo apt install <selected package>
$
Henriquefeira said:
How are you trying to use ADB? It doesn't work when your phone is on fastboot mode
Click to expand...
Click to collapse
I have not even got that far. See post above, "adb" is not recognized. I would rather not install the adb development package if I can avoid it.
Its fastboot flash recovery not adb flash
Henriquefeira said:
Its fastboot flash recovery not adb flash
Click to expand...
Click to collapse
The commands is not my issue. I have a list of commands I have run successfully many times. My issue is with the new OS (in the same PC) not recognizing adb. When I boot to the old OS, no issue, back to the new OS, command is not recognized..
My list of commands is as follows:
Code:
adb devices
adb reboot bootloader
sudo fastboot devices
sudo fastboot boot twrp-osprey-3.0.2-r1.img
Henriquefeira said:
Its fastboot flash recovery not adb flash
Click to expand...
Click to collapse
Re-reading your reply, I think you mis-read my code box. Next to the dollar sign my command "ls". Below is the OS response. Next $, command is "adb", and below the OS response.
I figured it out. So in Ubuntu 16.04 my command needs to be:
"./adb"
where in 12.04 "adb" worked.
MrTooPhone said:
I figured it out. So in Ubuntu 16.04 my command needs to be:
"./adb"
where in 12.04 "adb" worked.
Click to expand...
Click to collapse
This implies execution from the current directory... Are you sure you don't have multiple 'adb' executables installed? Check the command 'which adb' to see.
Sent from my MotoG3 using Tapatalk
acejavelin said:
This implies execution from the current directory... Are you sure you don't have multiple 'adb' executables installed? Check the command 'which adb' to see.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Pretty sure I had multiple 'adb' executables in 12.04.
i really could use some help friends im having problems with adb on windows when my device is on adb can see it of course
C:\adb>adb devices
List of devices attached
ZY22236P94 device
the problem is when its in bootloader mode adb cant seem to see it i have all drivers installed and i cant understand why im getting this error i want to install a recovery and i cant i currently have know recovery installed and i really need to rest my phone cause of a lot of software issus this is the message that get when bootloader mode
C:\adb>adb devices
List of devices attached
it shows nothing attached on windows devices manager it shows motorola adb interface connectad and running fine so i cant understand what im doing wrong please i really need some help here mates
steffano said:
i really could use some help friends im having problems with adb on windows when my device is on adb can see it of course
C:\adb>adb devices
List of devices attached
ZY22236P94 device
the problem is when its in bootloader mode adb cant seem to see it i have all drivers installed and i cant understand why im getting this error i want to install a recovery and i cant i currently have know recovery installed and i really need to rest my phone cause of a lot of software issus this is the message that get when bootloader mode
C:\adb>adb devices
List of devices attached
it shows nothing attached on windows devices manager it shows motorola adb interface connectad and running fine so i cant understand what im doing wrong please i really need some help here mates
Click to expand...
Click to collapse
adb doesn't work in bootloader mode, that is when you use fastboot... I think you should review the process involved in installing recovery.
Sent from my MotoG3 using Tapatalk