Related
All right guys, I know I should search the forum, but I have no time now, this is what's going on: I tried to install CF3D's plugin on my Transformer, but it went darn bad, I can't get past Asus' "powered by tegra" screen, and I need this by tomorrow, for my class, how do I fiz this?! I unlocked it, running TWRP v 0.2.2.3., can't remeber my rom's name but it's a mod of the CleanRom, v3.1 that's all I know. I think I can fix this by re-flashing my rom, but I don't know if I can put files into my SD only with TWRP in my hands, if not is it a real brick?? Please, help me!!!
TheBloodEagle27 said:
All right guys, I know I should search the forum, but I have no time now, this is what's going on: I tried to install CF3D's plugin on my Transformer, but it went darn bad, I can't get past Asus' "powered by tegra" screen, and I need this by tomorrow, for my class, how do I fiz this?! I unlocked it, running TWRP v 0.2.2.3., can't remeber my rom's name but it's a mod of the CleanRom, v3.1 that's all I know. I think I can fix this by re-flashing my rom, but I don't know if I can put files into my SD only with TWRP in my hands, if not is it a real brick?? Please, help me!!!
Click to expand...
Click to collapse
I don't understand "if I can put files into my SD only with TWRP in my hands", you don't have a pc where you can copy the rom to your sdcard? BTW you should be using twrp 2.3.1.0.
I actually have my PC here with me,
but like I said im not sure I can connect it to the pc since it will be on recovery, you know, like an MTP or mass storage, can TWRP do that?
Sent from my R800i using xda app-developers app
TheBloodEagle27 said:
I actually have my PC here with me,
but like I said im not sure I can connect it to the pc since it will be on recovery, you know, like an MTP or mass storage, can TWRP do that?
Sent from my R800i using xda app-developers app
Click to expand...
Click to collapse
You can't take the sdcard out and put it to your pc, copy the rom from pc to sdcard then put it back to your device? or you could use adb to push the file and hope adb is working on your pc.
ADB is working on my PC, but I don't see the TF700T icon under my computer
Sent from my R800i using xda app-developers app
TheBloodEagle27 said:
ADB is working on my PC, but I don't see the TF700T icon under my computer
Sent from my R800i using xda app-developers app
Click to expand...
Click to collapse
Try this,
Copy the rom.zip to the directory where your adb.exe is, then boot your device to twrp (home screen).
On your pc type
adb push rom.zip /Removable/MicroSD then hit enter (this copy the rom.zip from your pc to the root of your microsdcard.
If you see bunch of number and bytes and time then it's working.
buhohitr said:
Try this,
Copy the rom.zip to the directory where your adb.exe is, then boot your device to twrp (home screen).
On your pc type
adb push rom.zip /Removable/MicroSD then hit enter (this copy the rom.zip from your pc to the root of your microsdcard.
If you see bunch of number and bytes and time then it's working.
Click to expand...
Click to collapse
Alright, I'ts getting late, so I'll try it after school after all, I was thinking of using flashtool to flash the room through fastboot, that's how I used to do on my Xperia Play, but I don't know if the program works with asus' tablets... Anyway, thanks a lot man, for trying to help me and all, If it works I'll have a lot to owe u.
TheBloodEagle27 said:
Alright, I'ts getting late, so I'll try it after school after all, I was thinking of using flashtool to flash the room through fastboot, that's how I used to do on my Xperia Play, but I don't know if the program works with asus' tablets... Anyway, thanks a lot man, for trying to help me and all, If it works I'll have a lot to owe u.
Click to expand...
Click to collapse
EDIT: I must be doing something wrong. Where is the adb.exe location? I found one in the Asus Sync folder, is it that one? Second, where do I put this command? I know, in the command prompt, but which folder is it supposed to open?
TheBloodEagle27 said:
EDIT: I must be doing something wrong. Where is the adb.exe location? I found one in the Asus Sync folder, is it that one? Second, where do I put this command? I know, in the command prompt, but which folder is it supposed to open?
Click to expand...
Click to collapse
You don't move the adb.exe, where ever the adb command located, you need to open command prompt and navigate to the adb.exe folder. Asus Sync is located in C:\Program Files\ASUS\ASUS Sync and so is the adb.exe. so open command prompt and type:
cd\ hit enter, this bring you to root Ccomputer displayed C:\>
type:
cd Program Files\ASUS\ASUS Sync hit enter, you're now in the Asus sync folder (this is where your rom.zip should be in also)
computer should displayed:
C:\Program Files\ASUS\ASUS Sync>
now type
adb push rom.zip /Removable/MicroSD then hit enter (this copy the rom.zip from your pc to the root of your microsdcard.
buhohitr said:
You don't move the adb.exe, where ever the adb command located, you need to open command prompt and navigate to the adb.exe folder. Asus Sync is located in C:\Program Files\ASUS\ASUS Sync and so is the adb.exe. so open command prompt and type:
cd\ hit enter, this bring you to root Ccomputer displayed C:\>
type:
cd Program Files\ASUS\ASUS Sync hit enter, you're now in the Asus sync folder (this is where your rom.zip should be in also)
computer should displayed:
C:\Program Files\ASUS\ASUS Sync>
now type
adb push rom.zip /Removable/MicroSD then hit enter (this copy the rom.zip from your pc to the root of your microsdcard.
Click to expand...
Click to collapse
"system could not find specified directory" Heads up ¬¬...
Do you actually have a microSD card inserted into the tablet?
MartyHulskemper said:
Do you actually have a microSD card inserted into the tablet?
Click to expand...
Click to collapse
haha!! sorry for lol! if you don't have the sdcard, you could push it to internal sd.
buhohitr said:
haha!! sorry for lol! if you don't have the sdcard, you could push it to internal sd.
Click to expand...
Click to collapse
Ok then, how do I push ut to the internal SD?
TheBloodEagle27 said:
Ok then, how do I push ut to the internal SD?
Click to expand...
Click to collapse
adb push rom.zip /sdcard/
or
adb push rom.zip /storage/sdcard0/
Edit: Is it working for you yet??
buhohitr said:
adb push rom.zip /sdcard/
or
adb push rom.zip /storage/sdcard0/
Edit: Is it working for you yet??
Click to expand...
Click to collapse
I'm not sure, i'll try it out right now. I guess if it doesn't work it could be a problem with adb, is there any tutorial on how to set it up?
buhohitr said:
Try this,
Copy the rom.zip to the directory where your adb.exe is, then boot your device to twrp (home screen).
On your pc type
adb push rom.zip /Removable/MicroSD then hit enter (this copy the rom.zip from your pc to the root of your microsdcard.
If you see bunch of number and bytes and time then it's working.
Click to expand...
Click to collapse
I tried this, but got this message:
adb server is out of date. Killing...
ADB server didn't ACK
*failed to start daemon*
error:
what does that mean?
TheBloodEagle27 said:
I tried this, but got this message:
adb server is out of date. Killing...
ADB server didn't ACK
*failed to start daemon*
error:
what does that mean?
Click to expand...
Click to collapse
I thought that you already have adb working on your PC, but seems like you don't. You need to download Android SDK and once installed, you can use adb command from this SKD. Here is the link to how install Android SDK. It shouldn't take no more than 10 min. Just download and run the install, only select packages with the word "Android name" should be only 2. Once you done this, adb and fastboot should work fine. You also need Java, but like 99% ppl with a PC should already had Java installed.
http://forum.xda-developers.com/showthread.php?t=1616059
This tool is very important in rooting, recovery, flash stuff to your device. So I recommend you install this and get it working, it will save you a lot of time and headache in the future.
EDIT; If you think you have all the components already installed, you could download the adb/fastboot package here http://forum.xda-developers.com/attachment.php?attachmentid=1403567&d=1350299936 , unzip it to your C drive, you will have a folder called "Install recovery", in this folder there's adb and fastboot command, and then open cmd navigate to this folder and execute adb command line I provide previously see if that works.
buhohitr said:
I thought that you already have adb working on your PC, but seems like you don't. You need to download Android SDK and once installed, you can use adb command from this SKD. Here is the link to how install Android SDK. It shouldn't take no more than 10 min. Just download and run the install, only select packages with the word "Android name" should be only 2. Once you done this, adb and fastboot should work fine. You also need Java, but like 99% ppl with a PC should already had Java installed.
http://forum.xda-developers.com/showthread.php?t=1616059
This tool is very important in rooting, recovery, flash stuff to your device. So I recommend you install this and get it working, it will save you a lot of time and headache in the future.
EDIT; If you think you have all the components already installed, you could download the adb/fastboot package here http://forum.xda-developers.com/attachment.php?attachmentid=1403567&d=1350299936 , unzip it to your C drive, you will have a folder called "Install recovery", in this folder there's adb and fastboot command, and then open cmd navigate to this folder and execute adb command line I provide previously see if that works.
Click to expand...
Click to collapse
All there is in here is a .cmd file, no adb or nothing, I tried to use the command line you provided me, but all I get is:
adb server is out of date. Killing...
*daemon started succesfully*
Protocol Failure
Edit: I also downloaded the Android SDK Manager and downloaded the two tools
TheBloodEagle27 said:
All there is in here is a .cmd file, no adb or nothing, I tried to use the command line you provided me, but all I get is:
adb server is out of date. Killing...
*daemon started succesfully*
Protocol Failure
Edit: I also downloaded the Android SDK Manager and downloaded the two tools
Click to expand...
Click to collapse
If you go here http://forum.xda-developers.com/atta...7&d=1350299936 download the zip file then unzip to your drive. In this new folder you should see adb.exe and fastboot.exe and a few dll files. Do you see them??? Make sure your anti-virus doesn't strip the files.
buhohitr said:
If you go here http://forum.xda-developers.com/atta...7&d=1350299936 download the zip file then unzip to your drive. In this new folder you should see adb.exe and fastboot.exe and a few dll files. Do you see them??? Make sure your anti-virus doesn't strip the files.
Click to expand...
Click to collapse
Oh man, this sucks, it says 404 page not found, didn't you cpy the wrong link?
Hi guys,
My tf -101 B90 model is stuck on the logo EEE pad.
I can go to the recovery but there is no zip files.(because i was so stupid and remove files )
So ,what i to do?
Any ideas?
Tnx a lot
..i mean, how to copy rom file from my pc to tf 101.?
Tnx
Sent from my GT-N7100 using Tapatalk 2
dzontra11 said:
..i mean, how to copy rom file from my pc to tf 101.?
Tnx
Click to expand...
Click to collapse
Boot to recovery, then on your PC, download and unzip the Naked Drivers.
Plug your tablet into the PC. It should find new hardware. Go to the Device Manager (through Control Panel - System) and look for your device. It may show up as an Android or Asus ADB device, or unknown hardware. Right click on it and update driver. Pick the driver (browse to it, do not let it scan) where you put the naked drivers. This should install a good working ADB driver.
Once that is complete, you will need to get a copy of ADB. It is in the Android SDK, but if you only need ADB, you can get it from this thread: http://forum.xda-developers.com/showthread.php?t=1955627 It also has some help on getting ADB working.
Once you get ADB downloaded, put the exe in a folder named c:\adb\.
Next, open a command prompt and type cd c:\adb followed by adb devices
At this point, it should restart adb (it may error out and say the daemon failed to start, just execute the adb devices command again) and show a recovery device connected.
Now, you need the ROM you want to flash. Download this and put it in the c:\adb folder. I am going to call it ROM.zip.
From the command prompt type adb push ROM.zip /sdcard/
It will then push the file ROM.zip to your tablet.
From this point, you should be able to go to your recovery on your tablet and Install ZIP from SDCard and then it should show the file you just pushed to your /sdcard/.
Tnx dude.
I try.
Sent from my GT-N7100 using Tapatalk 2
i have a slight problem. i grabbed the ubuntu touch alpha and went in to recovery, loaded it (according to thread instructions) but ended up with a bootloop.
in the end i thought "lets just put another rom back on for now" and then realised i had deleted the other rom from the sdcard! so i'm stuck with it not booting in to ubuntu, and not able to get another rom on as it doesn't boot in.
can i connect to the internal sdcard area myself by plugging the usb in to the pc or something?
i have twrp loaded as recovery
thanks
ah, TWRP adb sideload to the rescue!
problem
my problem is stuck in boot screen after i did super wipe full what should i do? i have cwm 5.5.0.4. i try flash from sd put it says no files found
partti86 said:
my problem is stuck in boot screen after i did super wipe full what should i do? i have cwm 5.5.0.4. i try flash from sd put it says no files found
Click to expand...
Click to collapse
The issue, Superwipe wipes the internal /sdcard/ and also this is where it flashes from.
You need to boot to recovery and then use ADB to push files to the sdcard.
If you have never used ADB, it can be a bit daunting.
First, you need adb from the Android SDK. It is a big file for the few you need. I have a copy of the relevant ADB files here: https://db.tt/b9dQ6xzp
Unzip this to c:\adb folder on windows. If you are using Linux, it should already have adb in the /usr/bin/ folder.
Next, you need the Universal Naked Drivers: http://forum.xda-developers.com/attachment.php?attachmentid=1934814&d=1367674531
Unzip these to c:\universal_naked_drivers
Boot to CWM and then plug in your USB cable. It should show a new device found. It may find 2, an MTP and then there should be another either Unknown device or an Android ADB device. Right click and update the driver. Be sure to search for driver, then tell it you want to pick from a list. Hit the Have Disk button and then hit the browse button and browse to c:\universal_naked_drivers and hit OK. It should show you a driver to select and hit OK. If you are using Win 8, there is an additional step that is required to used non-signed drivers.
Once the driver is updated, download the zip file you want to flash on your PC. I assume it is a ROM.zip file for this example. Place this file in the c:\adb folder and call it ROM.zip (can be named something else, but this is what we will use for this example).
Now, open a command prompt and execute the following:
Code:
> [B]c:[/B]
c:\> [B]cd c:\adb[/B]
c:\adb> [B]adb devices[/B]
It will probably say some messages about the daemon is not running, restarting adb.
Then it should show a list. There should be some numbers followed by "recovery"
If no devices are shown, check that your ADB device is showing in the Device Manager.
Once you see it in the adb devices list, continue:
Code:
c:\adb> [B]adb push ROM.zip /sdcard/[/B]
successfully pushed xxx bytes
c:\adb>
At this point you should now see the ROM.zip file on the internal storage in CWM to allow you to install it.
Choose to install the file then reboot (not to recovery). You have to let it flash the file (progress bar will show). Once the screen goes black and the progress bar disappears, it should now boot to your ROM..
If your ROM requires a custom kernel and/or GAPPS to be flashed, use the same procedure to push your kernel.zip and GAPPS.zip to the /sdcard/ directory.
mk2media said:
ah, TWRP adb sideload to the rescue!
Click to expand...
Click to collapse
Can you explain what you did please? what is adb sideload?
Hi
I have a Nexus 5 currently on KitKat 4.4, and am trying to manually update to 4.4.1 but with no success
Have read and followed all stages in posts relating to updating the firmware, have downloaded the 4.4.1 file and Android SDK.
All steps work as they should, have got as far as my PC recognising my device serial number, until I get to the step where I enter, in the command prompt opened from the platform tools folder
adb sideload KitKat.zip (KitKat.zip being the name I have given the file)
I then keep getting the error message "unable to read file KitKat.zip"
I have tried with and without .zip in the command but still no luck
Help please?? I have run out of ideas to try
The command adb sideload (filename).zip has no space between side and load.
Sent from my Nexus 7 using XDA Premium HD app
---------- Post added at 02:44 PM ---------- Previous post was at 02:40 PM ----------
Also is your 4.4.1 update file in the platform tools folder? Are you opening the command prompt in the platform tools folder?
Sent from my Nexus 7 using XDA Premium HD app
Please ask questions in q&a. General is not for questions
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
When you type in the command prompt: adb sideload update, do not type in the .zip part in the command line
Sent from my Nexus 5 using Tapatalk
nohcho said:
When you type in the command prompt: adb sideload update, do not type in the .zip part in the command line
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Wrong. First, rename the file to "update.zip" without the quotes. Make sure it's not "update.zip.zip." . Make sure the file is in the platform-tools folder. The command is "adb sideload update.zip" no quotes
marleyfan61 said:
Wrong. First, rename the file to "update.zip" without the quotes. Make sure it's not "update.zip.zip." . Make sure the file is in the platform-tools folder. The command is "adb sideload update.zip" no quotes
Click to expand...
Click to collapse
Have tried renaming the file to update.zip as well as trying several other file names, doesn't make any difference the same error message appears
I was having the same issue. I just kept the ota name as it was when I downloaded it and added .zip to the end. It worked fine after that. Just copy and paste it in cmd
red83 said:
Have tried renaming the file to update.zip as well as trying several other file names, doesn't make any difference the same error message appears
Click to expand...
Click to collapse
Maybe a corrupt download. Try downloading again. Make sure you make file extensions visible so you don't accidentally name it .zip.zip. Then try my instructions again.
Are you booting to recovery then doing the power/volume up thing then select apply update from adb?
forgive me if you did this already, does your operating system display the three letter file extension like 'update.zip, adb.exe' etc.
marleyfan61 said:
Maybe a corrupt download. Try downloading again. Make sure you make file extensions visible so you don't accidentally name it .zip.zip. Then try my instructions again.
Are you booting to recovery then doing the power/volume up thing then select apply update from adb?
Click to expand...
Click to collapse
yes I put the phone into recovery mode as described in the online tutorials by holding the power button and the down arrow volume button simultaneously and from there I can select recovery mode and then into the sub menu that you popular by hold power and tapping the up volume button and it appears at the top of the screen, I then select ''update via ADB''....... by the way by default the windows drivers package doesn't have a specific ADB driver, and as a result you get an on screen prompt to verify this is the case.
When you activate usb debugging from developer options on the android desktop is when this becomes apparent, to get round this I have loaded up a couple of generic ADB drivers and tried them, they work as when you open the command prompt and specify the location of the adb.exe file it recognises the adb device when you put in ''adb devices''...its serial number/ imei can be seen from there.
Now here is the random part...when you populate the string under command prompt and then add '' adb sideload update.zip (exactly as that) you get an on screen prompt appear stating the ' cannot read update.zip '
I was thinking this file may be corrupt but I have located several now and none work at all.......basically I can run the adb.exe file from the ''platform-tools'' folder where the ''update.zip'' file has been located....regardless of what I name it or whether it is called kitkat.zip or without the .zip extension it still says it cannot read the file....what am I doing wrong??
red83 said:
yes I put the phone into recovery mode as described in the online tutorials by holding the power button and the down arrow volume button simultaneously and from there I can select recovery mode and then into the sub menu that you popular by hold power and tapping the up volume button and it appears at the top of the screen, I then select ''update via ADB''....... by the way by default the windows drivers package doesn't have a specific ADB driver, and as a result you get an on screen prompt to verify this is the case.
When you activate usb debugging from developer options on the android desktop is when this becomes apparent, to get round this I have loaded up a couple of generic ADB drivers and tried them, they work as when you open the command prompt and specify the location of the adb.exe file it recognises the adb device when you put in ''adb devices''...its serial number/ imei can be seen from there.
Now here is the random part...when you populate the string under command prompt and then add '' adb sideload update.zip (exactly as that) you get an on screen prompt appear stating the ' cannot read update.zip '
I was thinking this file may be corrupt but I have located several now and none work at all.......basically I can run the adb.exe file from the ''platform-tools'' folder where the ''update.zip'' file has been located....regardless of what I name it or whether it is called kitkat.zip or without the .zip extension it still says it cannot read the file....what am I doing wrong??
Click to expand...
Click to collapse
Try my suggestion above, worked for me. I was having the same problem.
red83 said:
yes I put the phone into recovery mode as described in the online tutorials by holding the power button and the down arrow volume button simultaneously and from there I can select recovery mode and then into the sub menu that you popular by hold power and tapping the up volume button and it appears at the top of the screen, I then select ''update via ADB''....... by the way by default the windows drivers package doesn't have a specific ADB driver, and as a result you get an on screen prompt to verify this is the case.
When you activate usb debugging from developer options on the android desktop is when this becomes apparent, to get round this I have loaded up a couple of generic ADB drivers and tried them, they work as when you open the command prompt and specify the location of the adb.exe file it recognises the adb device when you put in ''adb devices''...its serial number/ imei can be seen from there.
Now here is the random part...when you populate the string under command prompt and then add '' adb sideload update.zip (exactly as that) you get an on screen prompt appear stating the ' cannot read update.zip '
I was thinking this file may be corrupt but I have located several now and none work at all.......basically I can run the adb.exe file from the ''platform-tools'' folder where the ''update.zip'' file has been located....regardless of what I name it or whether it is called kitkat.zip or without the .zip extension it still says it cannot read the file....what am I doing wrong??
Click to expand...
Click to collapse
I'm not following some of what you are saying. I think it may be an adb driver issue. Have a look at this thread :http://forum.xda-developers.com/showthread.php?t=2514396
Also, I don't use adb.exe. I open a command prompt and navigate to the platform-tools folder and execute the commands in the cmd window. You say you are getting into recovery by doing the button presses. You should be able to connect your phone when not in recovery and within the cmd window execute "adb reboot recovery" to get into recovery. If that's not working it's a driver problem.
Beyond that I'm not going to be much more help - not that I've been any help since you are still having the problem.
marleyfan61 said:
I'm not following some of what you are saying. I think it may be an adb driver issue. Have a look at this thread :http://forum.xda-developers.com/showthread.php?t=2514396
Also, I don't use adb.exe. I open a command prompt and navigate to the platform-tools folder and execute the commands in the cmd window. You say you are getting into recovery by doing the button presses. You should be able to connect your phone when not in recovery and within the cmd window execute "adb reboot recovery" to get into recovery. If that's not working it's a driver problem.
Beyond that I'm not going to be much more help - not that I've been any help since you are still having the problem.
Click to expand...
Click to collapse
Yes what you said works, straight into recovery no probs by putting 'adb reboot recovery in a cmd prompt window to the specific directory that the abd file is located......(in platform tools) then if I put adb devices the serial number comes up straight away with 'sideload next to it.
So then I put adb sideload update.zip, and guess what!
cannot read update.zip....
Have you tried my suggestion?
richport29 said:
Have you tried my suggestion?
Click to expand...
Click to collapse
Yes have just tried what you suggested and only added .zip to the original name of the file and still the same error message appears
marleyfan61 said:
I'm not following some of what you are saying. I think it may be an adb driver issue. Have a look at this thread :http://forum.xda-developers.com/showthread.php?t=2514396
Also, I don't use adb.exe. I open a command prompt and navigate to the platform-tools folder and execute the commands in the cmd window. You say you are getting into recovery by doing the button presses. You should be able to connect your phone when not in recovery and within the cmd window execute "adb reboot recovery" to get into recovery. If that's not working it's a driver problem.
Beyond that I'm not going to be much more help - not that I've been any help since you are still having the problem.
Click to expand...
Click to collapse
Should I be "de-activating/activating" anything else other than activating the developer options and selecting USB debugging....should I remove my SIM card??
Anything else I may have overlooked please?
red83 said:
Yes have just tried what you suggested and only added .zip to the original name of the file and still the same error message appears
Click to expand...
Click to collapse
Try re-downloading the ota. Place it in the platform-tools folder, and try again.
7ed504f678cea49ecf0974e8cd956e2974e3f943.signed-hammerhead-KOT49E-from-KRT16M.7ed504f6.zip
richport29 said:
Try re-downloading the ota. Place it in the platform-tools folder, and try again.
7ed504f678cea49ecf0974e8cd956e2974e3f943.signed-hammerhead-KOT49E-from-KRT16M.7ed504f6.zip
Click to expand...
Click to collapse
Have tried re-downloading the file from several locations, placing it directly into the platform-tools folder and only adding .zip to the file directory name.....still no joy
When you type adb devices, what comes up?
Unless you absolutely have to have the camera fix in this update right now, then I suggest you just wait til the OTA becomes available on your phone. The camera fix is the only significant thing in the update. I don't know what the issue is with what you are trying but I suspect there is something not being done right. Sounds like it's not worth the frustration tho.
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.