Related
Can someone help me please? I made a rookie mistake (although I'm not rookie) and I removed my framework-res.apk, I have a backup of it but I can't figure out how to push it using fastboot commands. I don't have access to adb. If anyone can help me get adb access that would help as well. Thx in advance guys.
No you can not push it through fastboot. If you have CWM installed, boot to recovery, mount /system and you can push with adb there.
Hi. I've done the same thing, but when I'm in CWM Recovery, my PC can't find the device in ADB?
abbaskip said:
Hi. I've done the same thing, but when I'm in CWM Recovery, my PC can't find the device in ADB?
Click to expand...
Click to collapse
Download androidcommander and download the sdk tools. Or go to uot kitchen and make up a fake framewok for flashing your tablet then replace the framework file with yours and flash it in clockwork
No you can't push via fastboot.
However if you're looping you'll find that adb has actually started and then you can just adb remount and adb push.
abbaskip said:
Hi. I've done the same thing, but when I'm in CWM Recovery, my PC can't find the device in ADB?
Click to expand...
Click to collapse
Try loading up these drivers and going back into adb... This worked for me on my Win7 machine
View attachment Motorola_End_User_Driver_Installation_5.2.0_32bit.rar
I flashed eos-tf101-20130704-121, and it does not boot. I've tried several times, and I made sure to wipe the system, cache, etc. why is it not working?
also, how do I get into download mode?
That's an ancient build of a dead ROM project
KatKiss is the new EOS
http://forum.xda-developers.com/showthread.php?t=2362764
Unfortunately, I don't have a spare sd card, and I can't seem to get download mode to work, so I was hoping I could install the ROM update, and install KatKiss. I am working on getting KatKiss though!
If yo boot to recovery you can use ADB to push files to your tablets internal memory to flash.
frederuco said:
If yo boot to recovery you can use ADB to push files to your tablets internal memory to flash.
Click to expand...
Click to collapse
sorry - how do I do this? never used adb before.
sniper8752 said:
I flashed eos-tf101-20130704-121, and it does not boot. I've tried several times, and I made sure to wipe the system, cache, etc. why is it not working?
also, how do I get into download mode?
Click to expand...
Click to collapse
you have to wipe cache and dalvik after flashing the rom
KronicSkillz said:
you have to wipe cache and dalvik after flashing the rom
Click to expand...
Click to collapse
no luck.
Im going to guess that you have CWM Recovery installed ?
If yes, that is likely the reason for it not booting
You'll need to put the TF into APX Mode (Volume up & Power while connected to the PC > USB)
Nothing will appear on the TF screen, but the PC should recognise it
Follow the instructions here to get TWRP Recovery installed instead
http://forum.xda-developers.com/showthread.php?t=1688012
sniper8752 said:
sorry - how do I do this? never used adb before.
Click to expand...
Click to collapse
You need adb from the Android SDK. I have a zip of the files you need here: http://db.tt/b9dQ6xzp
Unzip these to c:\adb\
Plug your tablet in using the USB cable. Your computer should detect a new device. Update the driver with the Naked Drivers 0.72 ADB driver found in the Dev forum (I think it is on page 2 of threads). If you are running Win 8, there are some extra steps to allow you to use this driver.
Once your devices shows in the device manager as an ADB device, open a command prompt and type the following:
Code:
c:
cd c:\adb
adb devices
At this point, it will probably restart the daemon and then it should show a recovery device. If it does, you can proceed. If not, check that your cable is good, and that an ADB device is showing in the device manager.
Grab the ROM of choice and any GAPPS and kernel that you want to move over to your device. Put them in the c:\adb folder. They will be referred to a ROM.zip, GAPPS.zip and kernel.zip going forward.
Execute the following:
Code:
adb push ROM.zip /sdcard/
adb push GAPPS.zip /sdcard/
adb push kernel.zip /sdcard/
Note there is a space between the zip and the /sdcard/. If you omit this space it will not work.
After each time the "adb push" is executed, it may take up to 10 minutes to push the file depending on how big it is. Just be patient until it says it was pushed successfully.
Once this is done, you should see these files in the internal memory of your device when in recovery.
thanks! got it to work.
I had a problem now and i am not found the solution. I bricked my phone after Full wipe
sorry for my bad english.
Phone is: HTC ONE S (s4)
super cid, unlocked, rooted, hboot 2.16, radio 1.35a
recovery: TWRP 2.7.x
last rom before i full wipe; viperOneS 3 (4.2.2) and before i installed the kernel maximus hd 's kernel
Pls not send me the link; because i try to everything to i found the forum links/posts. i search to forums for 4-5 hours no result for my kind of problem
Now: i can't flash rom and i phone not open
what i did ?
1. adb reboot-bootloader and open the Recovery (TWRP 2.7.x)
2. I do Full Wipe; Factory Reset, Wipe Cache, data, system, dalvik & format Data menus
3. my rom zip is gone on the SD CArd. ok it's normal. i need to recopy rom.zip to sd card
i think ; flash the rom via sideload / adb push methods. WTF ! 2 options are not work for some errors.
Problems;
ADB Sideload feature ; error device not found. i investigate the problem and i see the Phone driver not installed on the Windows. (win 8.1.1)
Device Manager look; One S (unknown device)
EDIT: i try on the Windows 7 laptop but result is same. windows doesn't recognize the phone when the Recovery Mode. and i can't sideload feature
Ok , i try to push .
Phone is start screen but no start because no have OS ! but when the mode device manager phone is OK
try this things;
adb push rom.zip /sdcard ERROR : No such file or directory
adb push rom.zip sdcard ERROR : No such file or directory
adb push rom.zip /sdcard/ ERROR: no such file or directory
adb push rom.zip /sdcard/rom.zip ERROR: Is a Directory
adb push rom.zip /data/media/0/ ERROR: Is a directory
bla bla bla i try to every possibilities
i m tired and i think to destroy my phone PLS HELP ME
I arrived at the point; i need to flash rom but how to copy zip to SD card ?
Sorry for my english too xD
I had the same problem last week.
Try to go in bootloader, then in fastboot and connect the device to the PC, from the PC with the Promt go in your adb folder
Code:
cd c:/[I]position of your folder[/I]
then test if adb sees your device with the command
Code:
adb devices
If it's ok then try again to push again the ROM with the command
Code:
adb push [I]name_of_the_file.zip[/I] /sdcard/zip.rom
casu91 said:
Sorry for my english too xD
I had the same problem last week.
Try to go in bootloader, then in fastboot and connect the device to the PC, from the PC with the Promt go in your adb folder
Code:
cd c:/[I]position of your folder[/I]
then test if adb sees your device with the command
Code:
adb devices
If it's ok then try again to push again the ROM with the command
Code:
adb push [I]name_of_the_file.zip[/I] /sdcard/zip.rom
Click to expand...
Click to collapse
thnx man, but when i go to fastboot, ADB devices are empty ? no adb push command work.
fastboot devices command works but did not help me the problem
thanks in other adviseee
natmacax said:
thnx man, but when i go to fastboot, ADB devices are empty ? no adb push command work.
fastboot devices command works but did not help me the problem
thanks in other adviseee
Click to expand...
Click to collapse
Then you should fix the driver problem first, have you tried it with both Win 8.1 and 7?
doesn't work ADB on fastboot mode. both of win 7 and win 8.
BUT in the fastboot mode no driver problem ! i dont understand, you say ; when phone in the fastboot mode, adb push command should work ?
BTW, just now in the fastboot mode, its finally fastboot flash zip rom.zip command works, but *UCKN the new problem occurs
when the write flash command, error : data length is too large!
i investigate this problem now, do you know the problem root cause ?
natmacax said:
I had a problem now and i am not found the solution. I bricked my phone after Full wipe
[..]
i m tired and i think to destroy my phone PLS HELP ME
I arrived at the point; i need to flash rom but how to copy zip to SD card ?
Click to expand...
Click to collapse
In a last try you can simply downgrade your hboot and run last ruu. Then re-uprade your hboot and so
Edit : ADB doesn't work in fastboot mode
benJX said:
In a last try you can simply downgrade your hboot and run last ruu. Then re-uprade your hboot and so
Edit : ADB doesn't work in fastboot mode
Click to expand...
Click to collapse
just now in the fastboot mode, its finally fastboot flash zip rom.zip command works, but i have a new problem
when the write flash command, error : data length is too large!
does have a any solution for this ?
also, you sayed upgrade downgrade hboot.... this is solution of the adb push problem ?
thnx
natmacax said:
doesn't work ADB on fastboot mode. both of win 7 and win 8.
BUT in the fastboot mode no driver problem ! i dont understand, you say ; when phone in the fastboot mode, adb push command should work ?
BTW, just now in the fastboot mode, its finally fastboot flash zip rom.zip command works, but *UCKN the new problem occurs
when the write flash command, error : data length is too large!
i investigate this problem now, do you know the problem root cause ?
Click to expand...
Click to collapse
Sorry if I wasn't clear, what i was saying is that adb push command should work if your adb drivers are working!
benJX said:
In a last try you can simply downgrade your hboot and run last ruu. Then re-uprade your hboot and so
Edit : ADB doesn't work in fastboot mode
Click to expand...
Click to collapse
I think that's a good solution if you can't push the zip with adb commands, I didn't think of that because when I had the problem I did it with the adb command
casu91 said:
I think that's a good solution if you can't push the zip with adb commands, I didn't think of that because when I had the problem I did it with the adb command
Click to expand...
Click to collapse
natmacax said:
also, you sayed upgrade downgrade hboot.... this is solution of the adb push problem ?
Click to expand...
Click to collapse
I'm not sure about what I'm saying but adb sideload doesn't work on recoveries made for hboot 2.16, aswell as mounting sdcard.
When you try to adb sideload from modded recovery for 2.16, it recognizes only 48mb of memory that's why you can't use it. But I repeat I'm not sure about it I never had to use adb sideload.
Edit : And you cannot flash a rom with fastboot. Flashing zip from it has to be done only when you want ot uprgade/downgrade firmware files in ruu mode
benJX said:
I'm not sure about what I'm saying but adb sideload doesn't work on recoveries made for hboot 2.16, aswell as mounting sdcard.
When you try to adb sideload from modded recovery for 2.16, it recognizes only 48mb of memory that's why you can't use it. But I repeat I'm not sure about it I never had to use adb sideload.
Edit : And you cannot flash a rom with fastboot. Flashing zip from it has to be done only when you want ot uprgade/downgrade firmware files in ruu mode
Click to expand...
Click to collapse
IT'S FINALLY OVER
THANKS FOR ALL
i think the problem as you sad, hboot & TWRP version !
i downgrade hboot 2.16 > modded 2.15 (then i try flash rom sideload or pus, via twrp 2.7 didn't work)
then i reflash recovery downgrade TWRP 2.6.3 and all it works
i flash the rom via adb sideload, all it works.
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.
was bout to flash pixel experience plus android 12. But i accidentally deleted the internal storage . Now i don't have a OS. I don't have a SD card as well. I tried ADB sideload from TWRP. I still have the TWRP but only TWRP. I installed all the drivers for ADB, Also the qualcomm driver as well. But when i use the adb devices command in cmd without running adb from mobile it shows the device is there but when i start ADB from TWRP it doesn't detect the device in PC> PLEASE HELP
eusz said:
was bout to flash pixel experience plus android 12. But i accidentally deleted the internal storage . Now i don't have a OS. I don't have a SD card as well. I tried ADB sideload from TWRP. I still have the TWRP but only TWRP. I installed all the drivers for ADB, Also the qualcomm driver as well. But when i use the adb devices command in cmd without running adb from mobile it shows the device is there but when i start ADB from TWRP it doesn't detect the device in PC> PLEASE HELP
Click to expand...
Click to collapse
What do you mean with this "without running ADB from mobile"?
ADB must run only in the CMD.
When you do adb devices, device doesn't appear?, try with disabling/enabling MTP.
When the twrp is open and i don't click ADB mode in twrp , it detects the phone . But after i click ADB in the twrp it get's disconnected in the PC and i can't flash the rom.
eusz said:
When the twrp is open and i don't click ADB mode in twrp , it detects the phone . But after i click ADB in the twrp it get's disconnected in the PC and i can't flash the rom.
Click to expand...
Click to collapse
Not sure what you mean with "click" ADB, adb is a command to type through.
Try transferring the file to the internal storage, use, adb push, then flash through TWRP, strange enough so TWRP enables ADB by default, although the ADB sideload can fail.
Try reflashing Newest TWRP , may be a bug or an error, even try to install "Minimal adb and fastboot tool" its more easy to use ...
Enriquecalong said:
Try reflashing Newest TWRP , may be a bug or an error, even try to install "Minimal adb and fastboot tool" its more easy to use ...
Click to expand...
Click to collapse
try ofox recovery, in that recovery always appears ADB SIDELOAD in pc , without error , almost for me...
TWRP RECOVERY(VAYU VERSION)
OFOX RECOVERY (VAYU)
For android 12 roms use ofox... less bugs
If your internal storage doesnt appears only FORMAT DATA and you can copy the rom in your internal storage without using ADB.
SubwayChamp said:
Not sure what you mean with "click" ADB, adb is a command to type through.
Try transferring the file to the internal storage, use, adb push, then flash through TWRP, strange enough so TWRP enables ADB by default, although the ADB sideload can fail.
Click to expand...
Click to collapse
ADB sideload didn't work here.
Enriquecalong said:
try ofox recovery, in that recovery always appears ADB SIDELOAD in pc , without error , almost for me...
TWRP RECOVERY(VAYU VERSION)
OFOX RECOVERY (VAYU)
For android 12 roms use ofox... less bugs
If your internal storage doesnt appears only FORMAT DATA and you can copy the rom in your internal storage without using ADB.
Click to expand...
Click to collapse
This worked thanks man.