Related
hi, this is how i managed to get root working on my tab, everything went fine for me till it came to booting into recovery then nothing use to happen so i combined two separate guides to get it working. thanks (bcmobile and 411tecknology)
the command in "(getting root 5) )" worked for me as i was getting stuck with "fastboot flash recovery skitzandroid-recovery.img"
i unlocked the bootloader by firmware upgrade the the following
for all those people like me with no experience in dos commands or linux, hope this works for you
PREPARE:
1) With your Tab in fastboot mode (step 1 of “GETTING ROOT” below), make sure you have a working fastboot implementation:
working dir\\fastboot devices
If all is well, you should see your device serial number. If there is a problem, you won’t get any response.
2) Downlad the two files attached to this thread
3) create a folder in drive c naming it "root"
This will be referred to as the working directory throughout the rest of this guide
4) Copy skitzandroid-10-1v-root.zip to your working directory (DO NOT UNZIP!) c: root
5) Extract the skitzandroid-recovery.img file from skitzandroid-stock-recovery.zip to your working folder. Your working folder( c: root) should now have 1 IMG file and one ZIP file.
6) copy fastboot files to the the folder that you are going to use as working dir ( c:root)
7) Copy the skitzandroid-10-1v-root.zip file to the root of your sdcard. You can eithe drag/drop, or run:
working dir or c:\root>adb push skitzandroid-10-1v-root.zip /sdcard
GETTING ROOT:
1) Power off your Tab and power it back on, while holding the VOLUME DOWN button.
2) When the DOWNLOAD / FASTBOOT icons appear, press VOLUME DOWN again to select FASTBOOT icon (the one with the USB logo) and press VOLUME UP to confirm selection.
3) Confirm you are now in fastboot mode and do a:
fastboot devices
If all is well, you should see your device serial number.
4) Open a terminal / CMD prompt and CD to your working folder
keep doing cd.. until you get to "c:>" then
cd/root
5) Run the following command:
c:\root> fastboot boot skitzandroid-recovery.img
..and wait. It might not look like anything is happening but it is.
6) You should now have a recovery menu. Use the volume rocker (up/down navigates menu options)
to select “Install zip from SDCARD” (or something like that)
7) Navigate to the root of your internal storage (/sdcard), select the skitzandroid-10-1v-root.zip file and press (tap!) the POWER button to confirm selection.
Once complete, use the Volume rocker to select “REBOOT” from the menu and press (tap!!!) the POWER button to confirm selection.
9) YOUR’RE DONE. Press the thanks button on this thread to continue
TESTING:
Check your apps menu to confirm the existence of SuperUser app.
whats wrong with this?
http://forum.xda-developers.com/showthread.php?t=1079781
Nothing!
I used it on UNLOCKED 10.1v (not from Vodafone) and had no data loss!
Great, Thanks
Frank
I do not understand: 3) Confirm you are now in fastboot mode and do a:
fastboot devices
If all is well, you should see your device serial number.
Where do I enter this data?
I mean - fastboot deviсes
TNTCOSMOS said:
I do not understand: 3) Confirm you are now in fastboot mode and do a:
fastboot devices
If all is well, you should see your device serial number.
Where do I enter this data?
I mean - fastboot deviсes
Click to expand...
Click to collapse
once you start your device in fastboot mode and connect it with the computer to make sure your device is recognized by the computer you open command prompt take it to your working dir.. (ie. c:>root) in our case type fastboot devices and hit enter, if your computer recognized your device you will the serial number under it.
im sorry> can you help me?
When i write in the command line "fastboot.exe devices" nothing happens....
TNTCOSMOS said:
im sorry> can you help me?
When i write in the command line "fastboot.exe devices" nothing happens....
Click to expand...
Click to collapse
assuming you have installed sdk if not please do so, then staying in sdk go to
(C:\android\android-sdk-windows\platform-tools ) by clicking your mouse in desktop
(not cmd prompt). above eg.. is how i installed sdk on my desktop yours may be different, now in platform-tools you will see two files called fastboot copy them both to to your folder called ..root.. and you are set to go.
bottom line is if you want to start fastboot from any folder in cmd you have to have these two files in the folder.
also if you know that your device is detected by your computer dont worry about step 3. all it does is tell you that your device is connected.
I have all turned out, the problem was the drivers. I copied the driver from pdanet and it worked!
TNTCOSMOS said:
I have all turned out, the problem was the drivers. I copied the driver from pdanet and it worked!
Click to expand...
Click to collapse
Glad to hear that you finally got the root.
same problem
TNTCOSMOS said:
im sorry> can you help me?
When i write in the command line "fastboot.exe devices" nothing happens....
Click to expand...
Click to collapse
i've tried with pdanet too but it's not working....like the computer can't see the device...any ideea ???
and when i write "fastboot boot ......etc......" it says <waiting for the device>
please help
You need the drivers installed for fastboot, have you installed them? Please have a look at the [Guide] Unlock your bootloader thread. it contains all the details to get fastboot working.
thank you...finally did it
another noob question...how do i enter in cwm for installing another ROM ???
zbuggy said:
thank you...finally did it
another noob question...how do i enter in cwm for installing another ROM ???
Click to expand...
Click to collapse
The easiest way if you are rooted is to install rom manager from the market. It has an option to reboot to recovery if you have CWM installed. It also allows you to update to the latest CWM recovery if there is one.
i've tried putting the TB Galaxy 1.0.9: Honeycomb 3.1 + TouchWiz UX and i made a mistake... in cwm i've uploaded the zip file only with the update and not the rom itself.since then the tab won't start...it stop's in the beggining at the "samsung galaxy tab 10.1v"...any ideea...what can i do ?
Download latest rom and instructions from samfirmware.com using odin Get ur tab into fastboot mode with 3 button recovery and start from scratch.
It should work out
Sent from my GT-P7500 using Tapatalk
zbuggy said:
i've tried putting the TB Galaxy 1.0.9: Honeycomb 3.1 + TouchWiz UX and i made a mistake... in cwm i've uploaded the zip file only with the update and not the rom itself.since then the tab won't start...it stop's in the beggining at the "samsung galaxy tab 10.1v"...any ideea...what can i do ?
Click to expand...
Click to collapse
Do the following. If you have not yet odin.
Download the full rom.
Follow instructions in how to get into fasboot in sticky thread.
Once in fastboot you can load recovery via it, to do that download the recovery from droidbasement.com/blog, search on pershoot's website for recovery 4.0.4 if i remember correctly then type
fastboot boot recovery.img
where recovery.img is the name of the file you downloaded from droidbasement.com
Recovery will then load give it a minute or so.
Once loaded you can push the downloaded full rom via adb. That is part of the android sdk.
Like this: adb push romfile.zip /data/media/ (this will take a few minutes)
Then in cwm instal rom.
I hope it helps. Btw, remember you need to flash the wipe script of the rom before you install the rom if you are comming from stock.
Send from my GT-P7100
10x everybody it worked!!!!!!!!
Still me, posting in yet another thread. Still can't get the proper drivers. Pda method is not working. Which version of PDanet should I use ? The latest ? This is ****ing irritating...
I'm used to have to struggle to get things work at the beginning, but with my Magic and Hd2 it was a matter of hours...not weeks ! I'm sure it's something stupid but everybody deserted these guides topics...
I'm actually considering posting in the Dev section just to get attention...
Also, pershoot blog's advices are a joke : with no tags, a not working search field, no categories, try to find an info ! Knowing that the word "Recovery" will pop about 3 times per subject, I'm good to spend the week-end searching...
DannyBiker said:
Still me, posting in yet another thread. Still can't get the proper drivers. Pda method is not working. Which version of PDanet should I use ? The latest ? This is ****ing irritating...
I'm used to have to struggle to get things work at the beginning, but with my Magic and Hd2 it was a matter of hours...not weeks ! I'm sure it's something stupid but everybody deserted these guides topics...
I'm actually considering posting in the Dev section just to get attention...
Also, pershoot blog's advices are a joke : with no tags, a not working search field, no categories, try to find an info ! Knowing that the word "Recovery" will pop about 3 times per subject, I'm good to spend the week-end searching...
Click to expand...
Click to collapse
Hello,
I have been successful with rooting on win7. With win xp - after a few day struggling - fastboot did not give a go. Hope this helps
I just can't get the "Adb Original" signature from Pdanet. I always get standard Adb. I add the galaxy tab lines in the .inf file but still...
Do you guys edit the inf file with Wordpad or another tool ?
So my kindle fire is stuck on twrp mode everytime i boot it. it first go to kindle with the "orange logo" then the "blue logo" i can hold the volume down to go to twrp recovery options and i can go to fastboot by going to "reboot" and "bootloader". How did this happen your wondering? Well i accidentally deleted my backup and the rom after i was done installing a rom, when i mount it i dont see it on my desktop, I click on the script while its mounting and it says "E:Unable to locate volume information for usb storage mode". it wont show the device on my windows 7 on "my computer" i downloaded the adb driver it detects the kindle and w/e but it wont show on my desktop so that i can transfer a rom into it and install it. If your curious of knowing what usb im using , its a galaxy s3 usb charger. It fits on the rear side of the kindle fire 7 hd and chargers...could it be that thats stoping my kindle fire hd from mounting? if it is then what other usb am i suppose to use to mount it or where can i find or buy one online or store? :crying:
Marckiscool said:
So my kindle fire is stuck on twrp mode everytime i boot it. it first go to kindle with the orange logo then the blue logo (twrp) i can hold the volume down to go to twrp recovery options but i accidentally deleted my backup and the rom when i mount it i dont see it, i click on the script while its mounting and i see "E:Unable to locate volume information for usb storage mode". it wont show the device on my windows 7 on "my computer" i downloaded the adb driver it detects the kindle and w/e but it wont show on my desktop so i can transfer a rom in it and install it. Of your curious of knowing what usb im using its a galaxy s3 it fits on the rear side of the kindle fire 7 hd and chargers could it be that? if it is then what other usb am i suppose to use to mount it or where can i find or buy one online or store? :crying:
Click to expand...
Click to collapse
Here is the tutorial to push onto TWRP. http://forum.xda-developers.com/showthread.php?t=2459498 Follow it and you will be back up in a short time.
Hey Thanks for the reply tho but The cmd doesnt seem to find the rom and its not working i tried to download his adb but my kindle wont install it
Marckiscool said:
Hey Thanks for the reply tho but The cmd doesnt seem to find the rom and its not working i tried to download his adb but my kindle wont install it
Click to expand...
Click to collapse
To CD into the directory you go into the folder where you put your extracted adb zip folder and ROM hold shift and right click on the mouse. Now left click on "open a command window here." Or you can CD from the directory directly. Use adb sideload rather than adb push. You want to copy the ROM into the same folder as the extracted adb folder because adb.exe is already in there and that's what you need for this procedure to work.
Here is a video that I think will help you a bit too. Short but very well done and very informative https://www.youtube.com/watch?v=CivvxcM1PCY He refers to the SDK tool folder. When he refers to that, you will refer to the extracted ABD folder. It takes a few seconds but soon you will see the flashing process in the form of a percentage.
Edit: When he refers to the USB drivers, thats what you use to get your device recognized. In command type adb devices. If you get waiting for device, you need to square that around first.
same thing wid nexus s
same thing happened to my nexus s. but when i type sideload or push it, it shows device not found. And when i type adb devices command it shows no devices please help, no os is there. i think there is any virus or any thing there which is stops it to connect. Kindly tel me if there is any file tht i can delete frm system and i can connect. Please guyx help me
Preparing Tools:
Intel USB Driver for Android
ADB Fastboot Tool 1.0.32
Asus MemoPad 7 Firmware (Download From the Asus website, and Put it in the same folder with fastboot adb tools)
1. Turn off your tablet
2. Go to FastBoot mode by pressing power + volume down, then the android logo should appear (Move in the menu with Volume Up and Volume Down, then press On Button to enter), then apply update from ADB option (Or enter in Recovery and then apply update from ADB option)
3 .Connect your tablet with USB Cable to your PC/laptop
4. Open command prompt in Windows (Shift + Right Click) (in the same folder where ADB is located)
5. Check connection by type <adb devices> (Without <>) if connection successful will be a list of devices
6. Type <adb sideload file.zip> (Without <>) (file.zip=adjust the filename, Asus firmware that you download earlier)
7. Wait until the process is complete
8. The tablet will flash to clean thoroughly
This method can be used to downgrade , or that an error during install root ( root will disappear completely )
I use the last firmware "UL-K017-WW-12.8.1.33-user" Lollipop 5.0 This is the only one that worked for me.
After flashing , the device may take about 10 minutes to start.
If you see sleep Android Robot Error in the Recovery Mode , Press Power button and hold it, then press Volume up, after one second you will see yellows words, just wait until the recovery menú appears.
My mother tongue is Spanish, sorry if I have some errors. Have a nice day.
Hello
I live in Colombia and i have the Asus Memo Pad 7 ME170C, i proved very much metods to restar my tab, but not works, i can enter in droidboot, i download this: UL-K017-WW-11.2.3.18.2-user, UL-K017-WW-11.2.3.28-user, UL-K017-WW-12.8.1.33-user. Anything works. always say error, the android is lying and red triangle, i proved the metod to restart for fastboot, flash the boot, flashboot and splashscreen, and upload for sd card and not works.
please help me. i'm soy for my english i talk spanish
NESSY24 said:
Hello
I live in Colombia and i have the Asus Memo Pad 7 ME170C, i proved very much metods to restar my tab, but not works, i can enter in droidboot, i download this: UL-K017-WW-11.2.3.18.2-user, UL-K017-WW-11.2.3.28-user, UL-K017-WW-12.8.1.33-user. Anything works. always say error, the android is lying and red triangle, i proved the metod to restart for fastboot, flash the boot, flashboot and splashscreen, and upload for sd card and not works.
please help me. i'm soy for my english i talk spanish
Click to expand...
Click to collapse
Send me an Email to Luis.ZK.97 @ gmail . com.
I´m gonna try help you in spanish, is more easy for you and me.
I am trying to flash a customer recovery to my device, but when the phone gets put in download mode i am getting " "lge android mtp device cannot start code 10". " I can not perform any of the essential fastboot commands because the device can't start. I have tried, updating drivers, and trying different mtp drivers available to me, none of which worked. I've tried to do this on 3 pcs running windows 7, 8 , and 10 and they all fail.
Is there a solution to this issue? surely i'm not the only one having this problem. Searching the forum yielded only Samsung results with the same error message. Following the lines of going to the registry and deleting a specific entry, it still didn't work, so please, any help?
PS. reinstalling the drivers for my device does nothing, and windows is already updated.
bump
Did you solved it? I have the same problem
Sunaj1 said:
I am trying to flash a customer recovery to my device, but when the phone gets put in download mode i am getting " "lge android mtp device cannot start code 10". " I can not perform any of the essential fastboot commands because the device can't start. I have tried, updating drivers, and trying different mtp drivers available to me, none of which worked. I've tried to do this on 3 pcs running windows 7, 8 , and 10 and they all fail.
Is there a solution to this issue? surely i'm not the only one having this problem. Searching the forum yielded only Samsung results with the same error message. Following the lines of going to the registry and deleting a specific entry, it still didn't work, so please, any help?
PS. reinstalling the drivers for my device does nothing, and windows is already updated.
Click to expand...
Click to collapse
because flashing twrp.... phone doesnt have to be in download mode..
you turn on phone plug usb. then install minmal adb
copy twrp file into adb folder/ keep pressed SHIFT KEY on empty space in minimal adb.. then right click mouse
then select start command prompt here.
then send command you should see a message on phone .. turn on screen. select ok. then again send command
the twrp files both one in sd card and in minimal adb and the command should be named the same for twrp. example twrp.v.1.1.3 the command has to be the same .. just edit command or both or rename twrp the twrp file.
Okay I know I need to wipe the device and/or reinstall the update
But I have no clue how to use android SDK or adb.
I have them both downloaded, not sure if they are installed for google glass access.
I'm using the command prompt and I search for adb or fastboot but no devices come up?
I downloaded the XE22 (latest firmware) but when I open that it asks me to burn a cd?
I'm lost and glass support won't help. Anybody?
phild22 said:
Okay I know I need to wipe the device and/or reinstall the update
But I have no clue how to use android SDK or adb.
I have them both downloaded, not sure if they are installed for google glass access.
I'm using the command prompt and I search for adb or fastboot but no devices come up?
I downloaded the XE22 (latest firmware) but when I open that it asks me to burn a cd?
I'm lost and glass support won't help. Anybody?
Click to expand...
Click to collapse
I just went through this to get to XE23. Did you ever get to the answer? Very similar process to flashing any other android device; identical really. LMK if you're still charging and using or want to.
GH
greddy91 said:
I just went through this to get to XE23. Did you ever get to the answer? Very similar process to flashing any other android device; identical really. LMK if you're still charging and using or want to.
GH
Click to expand...
Click to collapse
Ok... As I am new to the Glass game.... Last night, when I got the unit fully charged (Sitting at SW version XE12), I connected it to the network to update.... This morning, I have a bootloop issue.
I want to flash XE 12 back to the device and try to let it update again.... I have yet to find a clear breakdown on how to falsh this... SDK is installed.... But it appears that I don't have a the proper USB drivetr and have know idea how to install it...
Really could use some help with the entire process...
So, sharing files used on Google drive:
https://drive.google.com/drive/folders/0B3-nca6GSfX1R2h1eDNDUjZwRVk?usp=sharing
Installed Minimal ADB and hit yes all the way through - in the google drive above.
This gives ADB commands functionality anywhere in CMD
I plugged in the glass and it came up as a USB drive - AWESOME.
Enter Command Prompt
Navigate to the directory where I had the Glass EX23 unzipped
Entered "adb devices" to make sure ADB was seeing the Glass (make sure no other android goodies are plugged in)
It was there so...
Enter "adb reboot bootloader"
My glass went blank.
Entered "fastboot devices" ... and nothing.
So opened "Device Manager"
There was a flagged driver standing out for when I flashed an old Note 2. There's the problem...
Right click and chose "Update driver" and pointed it to the "usb driver" directory extracted from the zip file in the google drive above.
Chose Android Composite ADB Interface - Skipped past the unsigned driver warning
Voila - the device is now seen in device manager
I then entered the command in cmd "fastboot devices" - and still blank
Unplugged glass and rebooted.
After it came up, plugged it back in - seen as USB drive again. Still good!
Entered "adb devices" to make sure ADB was seeing the Glass
It was there again so...
Enter "adb reboot bootloader"
My glass went blank again.
Entered "fastboot devices" ... and there it is!!! The Gates of Valhalla are in sight!!!
Assure you're in the directory where the google image has been unzipped...
Now begin by entering:
"fastboot flash boot boot.img"
let it complete
Now "fastboot flash system system.img"
let it complete (this is the longest one... be patient)
Now "fastboot flash recovery recovery.img"
Now "fastboot flash userdata userdata.img"
Now "fastboot erase cache" - takes a bit of time for cleanup
Now "fastboot reboot"
The moment of glory has arrived... watch your glass go through boot - yes the Glass screen turns on and off a few times and flashes some odd colors... again, be patient... took like 5 minutes and ate up 40% of my full battery, but there it was XE23 and full stability.
Note - NONE of these utilities are mine, they were borrowed after researching in hundreds of other threads on how to get this done.
Of note... I came from XE10 straight to XE23 with no issues.
Legobricke said:
Ok... As I am new to the Glass game.... Last night, when I got the unit fully charged (Sitting at SW version XE12), I connected it to the network to update.... This morning, I have a bootloop issue.
I want to flash XE 12 back to the device and try to let it update again.... I have yet to find a clear breakdown on how to falsh this... SDK is installed.... But it appears that I don't have a the proper USB drivetr and have know idea how to install it...
Really could use some help with the entire process...
Click to expand...
Click to collapse
What version of Glass is it? And there is a thread under development about modifying your android_winusb.ini file so you can manually select the driver.
Muskeman16 said:
What version of Glass is it? And there is a thread under development about modifying your android_winusb.ini file so you can manually select the driver.
Click to expand...
Click to collapse
It is model XE-C running version XE-12...
Legobricke said:
It is model XE-C running version XE-12...
Click to expand...
Click to collapse
Have you attempted to re-flash it at all?
Muskeman16 said:
Have you attempted to re-flash it at all?
Click to expand...
Click to collapse
That is was I'm attempting to do.... But I'm not having much luck....
I am sure that USB debugging was not turned on.... When I put the Glass in to fastboot mode (holding down camera button and turning on which gives me short fast bursts from the power light) it doesn't seem to recognize it on the desktop. I get 3 low tones when I plug it in and ADB doesn't see it...
I guess I need a direct breakdown of the process... I have searched the net and forum, but the ones I find seem to drop a process or imply something that I'm not understanding.
I have flashed devices before and I'm familiar with the process, but I'm missing something when it comes to the Glass....
When I power up (normal power up) and the plug it, device manager lists it as Android Device. When I open that, just shows ADB Device Interface... I have tried to update the entry with the USB driver, it is claims the drivers are up to date.
I am using Windows 7.... But it is clear that ADB is not seeing the device... So, I'm stuck until I can findout how to get the device to be recongized.... What is strange is that when I plug the Glass in, it does see it in the tray below... It even allows me the "eject Glass_1... but for the life me, I can't get ADB to see it...
Any help is appreciated!
Ok.... I can finally see the Glass in ADB.... But only if I put the Glass in Fastboot mode prior to plugging in to USB.... I adb "fastboot device" and get a serial number.... Then I adb "fastboot flash boot boot.img and get FAILED (remote failure)...
What am I doing wrong?
I have even tried to unlock the device, but it hangs at erasing userdata.
The very interesting thing is on a few occasions, I have gotten GLASS to work....
I re-set it up.... and then it works fine until I have to charge it again and then it goes back to the freezing on the GLASS screen.
Every time I try to flash Boot/system/ etc image... it fails.... Not sure why....
Ok....
Finally nailed it.... No more GLASS looping....
I took this unit that was experiencing GLASS loop at firmware X12 to X23... What a journey....
To start.... I downloaded the "minimal adb fastboot" and installed....
Then I downloaded the new firmware from google
I dragged the zip folder to my desktop and extracted it....
At this point, I put GLASS in fastboot mode (Hold camera button down then press the power button. Once power light come on, let go of the power button but keep camera pressed. One the light starts to flash (slowly, not fading), you are in fastboot mode).
I then attached the glass via usb cable to computer (I was operating Windows 10).
Open device manager and look for "android devices" and open it. You should see "Android ADB Interface" - Right click on it and select Update Driver Software". Then select Browse my computer for driver software. The select "Let me pick from a list of device drivers on my computer". Look for "Android ADB Interface". Select it and then update it.
Once this is done, got to your icon tray (should be down in the bottom right of your scree) and right click on "Safetly Remove Hardware or Eject Media". It should open a window up. Confirm that glass is there.
Then go to the desktop where you extracted the firmware and open the folder. Once open, Hold shift and right click. This should give you a menu. You are looking for "Open command window here". select it and it should open a command window.
Then follow the instructions listed on the google firmware page.
I didn't follow all the instructions.... The ones I did were enough to fix my boot looping GLASS -
1.) fastboot devices (This should comeback with a serial number. If it doesn't, be sure you have the glass in fastboot mode)
2.) fastboot oem unlock ( I had to do this because the device would fail when I tried flashing to the device. This was the only way I could get it to take the flashing). It will make you type this twice to confirm you wish to unlock.... This will erase all the data (cache and user data) on the device and you have to be patient.... It does take some time... If you think it has hung up (which I did), I just hit a key on my keyboard and then pressed enter.... It then confirmed that the unit had been unlocked.
3.) After I unlocked the unit, I then typed fastboot devices again just to be sure that it was still reading the GLASS.
4.) fastboot flash boot boot.img - This will fail if you don't have the unit unlocked.... The first time I did this, the glass unit went down and I had to start the process again. The second time I did the process, it worked.
5.) fastboot flash system system.img - This did take a few minutes
6.) fastboot flash recovery recovery.img
Once done, I closed the command window and ejected the glass unit from the computer..... I pressed the power button and BOOM! I was back to a working glass...
One key element I must point out.... allot of this process requires allot of patience....
The pages that are linked above will help you through the process.... I took a week of researching.... But it was worth it...
There are risks involved - bricking/etc.... But this is the process that worked for me...
Good luck!
Legobricke said:
Ok.... I can finally see the Glass in ADB.... But only if I put the Glass in Fastboot mode prior to plugging in to USB.... I adb "fastboot device" and get a serial number.... Then I adb "fastboot flash boot boot.img and get FAILED (remote failure)...
What am I doing wrong?
Click to expand...
Click to collapse
Just for clarity - I associate adb and fastboot as two seperate commands.
"adb devices" gives you your android attached devices inventory
"fastboot devices" gives you your attached devices in fastboot
The "adb reboot bootloader" changes the device seen in adb to a device that can be seen in fastboot.
Not sure if that was clear before, but it may help here.
greddy91 said:
Just for clarity - I associate adb and fastboot as two seperate commands.
"adb devices" gives you your android attached devices inventory
"fastboot devices" gives you your attached devices in fastboot
The "adb reboot bootloader" changes the device seen in adb to a device that can be seen in fastboot.
Not sure if that was clear before, but it may help here.
Click to expand...
Click to collapse
Thanks for the clarify....
I attempted to go the adb route, but could never get the system to see the GLASS in adb... and because the GLASS was looping on the GLASS screen, I couldn't activate USB Debugging..
So, I found out in researching that I could manually put the GLASS in fast boot mode....
Once it was unlocked, everything took...
not a tech guy -_-
Hi thanks for clearifying But could you explain step by step and like i know nothing about commad prompt. Im just tring to work my glass but at turkey i cant find any coder who understands this. (sorry for bad english)