Database Info

team eos rom not booting

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.

Please help , Stuck on Loading Screen.

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.

Moto G 2013 (xt1033) with no OS, can't adb push/sideload rom.

I have a Moto G xt1033 with no operating system.
I can recognize the device using fastboot devices and adb devices. (drivers are installed properly)
CWM recovery is installed properly.
There's no operating system and the sdcard is empty.
When I try to use the command adb push to get the rom.zip into the sd card (or data/media folder) it just won't work, it will give me a 'protocol failure' after a couple of seconds.
When I try to use the command adb sideload it will immediately crash (at 2%) and give me the error: failed to write data 'protocol fault <no status>'.
I've also tried to install a stock rom using flashing through fastboot, but it also failed.
Anyone has any idea of how I can save this phone?

It sounds like something is not right with your ADB / Fastboot setup. What operating system is on the PC / Laptop?
You might want to try reinstalling ADB:
http://forum.xda-developers.com/showthread.php?t=2317790​
Alternatively, a quick way to get access to Recovery Mode ADB is to use Linux, either as a LiveCD or full install. The command to install ADB / Fastboot on Ubuntu is:
sudo apt-get install android-tools-adb android-tools-fastboot​

Thanks for the tips, my computer's OS is Windows 7, but the problem was related to my computer's front USB ports, all 6 of them. As soon as I connected to one of my back USB port it worked.. Most likely because my front ports are 2.0 and the back ones 3.0. Never thought it would make a difference in this case, kinda feel stupid for having wasted so much time looking for a solution when it was so simple.
Thanks for the reply anyway @lost101.

XT1032
Am experiencing the same problem,
unable to sideload/push stock rom gets stuck on push at 31%
Recovery CMW, able to boot into recovery
getvar=all, i don't even have imei shown in that!
pls help me fix it...
Thanks a load in advance

As soon as I select 'ADB sideload' on TWRP, the phone is no longer recognized by the desktop computer nor ADB.exe...
But when I select cancel, the device is then recognized. This is version 3.3.1-0
Edit: It seems to only logical solution is to use 'adb push [image_name] /sdcard/.'

Question Deleted the internal storage in TWRP , Now no OS. Tried ADB sideload but at the top of it , says unable to Decrypt FBE device something like that

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.

Question Help! Sideloading OTA fails

I tried to sideload June OTA just as normal.
Code:
adb sideload F:\Pixel6a\bluejay-ota-tq3a.230605.010-a67dbf36.zip
serving: 'F:\Pixel6a\bluejay-ota-tq3a.230605.010-a67dbf36.zip' (~0%) adb: failed to read command: No error
that's the output of my terminal after trying to sideload it,.. on the phone nothing happens at all
it says verifying, but nothing about receiving anything and after leaving it for almost 10 minutes still nothing.
So I disconnect it and it says verification failed and it warns me
"Previous installation has failed, Your device may fail to boot if you reboot or power off now."
But it didn't even write anything did it? since it just failed at sending and verifying the ota in the first place.
Can I reboot my phone?
Edit: guess it's true that sideloading the OTA is really as safe as it gets, rebooting to System was no issue.
I just don't get what's wrong... using the same platform tools that I used for March, April and May update, 33.0.3-8952118
I re-downloaded the OTA from google to confirm it wasnt corrupt, same issue.
All my modules were disabled (not that that would stop adb from sending the file).

G5-User7080 said:
I tried to sideload June OTA just as normal.
Code:
adb sideload F:\Pixel6a\bluejay-ota-tq3a.230605.010-a67dbf36.zip
serving: 'F:\Pixel6a\bluejay-ota-tq3a.230605.010-a67dbf36.zip' (~0%) adb: failed to read command: No error
that's the output of my terminal after trying to sideload it,.. on the phone nothing happens at all
it says verifying, but nothing about receiving anything and after leaving it for almost 10 minutes still nothing.
So I disconnect it and it says verification failed and it warns me
"Previous installation has failed, Your device may fail to boot if you reboot or power off now."
But it didn't even write anything did it? since it just failed at sending and verifying the ota in the first place.
Can I reboot my phone?
Edit: guess it's true that sideloading the OTA is really as safe as it gets, rebooting to System was no issue.
I just don't get what's wrong... using the same platform tools that I used for March, April and May update, 33.0.3-8952118
I re-downloaded the OTA from google to confirm it wasnt corrupt, same issue.
All my modules were disabled (not that that would stop adb from sending the file).
Click to expand...
Click to collapse
Yeah, when sideloading an OTA (or updating via Settings) it puts the new version of the OS on the inactive slot. If something goes wrong with the update you'll still have your current slot to fallback on (like in your case).
Maybe try different cables/ports.

You can update through recovery if necessary; download the OTA to your device, reboot to recovery, and select Apply update from SD card.

V0latyle said:
You can update through recovery if necessary; download the OTA to your device, reboot to recovery, and select Apply update from SD card.
Click to expand...
Click to collapse
oh I remember seeing that option, does that mean I need to put the ota.zip in /sdcard/ ?
in essence that would circumvent adb sending issues / cable issues, I suppose?

G5-User7080 said:
oh I remember seeing that option, does that mean I need to put the ota.zip in /sdcard/ ?
in essence that would circumvent adb sending issues / cable issues, I suppose?
Click to expand...
Click to collapse
Yes. You don't need to use a PC at all. You can either download the OTA directly through your phone's browser, or if you want, you can use a USB cable to transfer the OTA file to your phone's storage. It doesn't matter where you put it; if you download it on your phone, it'll be in /sdcard/Downloads, if you use a USB cable you'll see the contents of /sdcard pop up as a USB drive in your computer.

V0latyle said:
Yes. You don't need to use a PC at all. You can either download the OTA directly through your phone's browser, or if you want, you can use a USB cable to transfer the OTA file to your phone's storage. It doesn't matter where you put it; if you download it on your phone, it'll be in /sdcard/Downloads, if you use a USB cable you'll see the contents of /sdcard pop up as a USB drive in your computer.
Click to expand...
Click to collapse
oki, I tried Pixelflasher first and interestingly it just worked.. same cable, same port, same adb, same everything
mhhhh.... using windows terminal wouldnt be the issue would it?
anyway, happy it works, but also frustrated I couldnt figure out why it refused to work typing the adb commands manually totally out of the blue

G5-User7080 said:
oki, I tried Pixelflasher first and interestingly it just worked.. same cable, same port, same adb, same everything
mhhhh.... using windows terminal wouldnt be the issue would it?
anyway, happy it works, but also frustrated I couldnt figure out why it refused to work typing the adb commands manually totally out of the blue
Click to expand...
Click to collapse
Were you using PowerShell or Command Prompt?
What were you doing on the phone?
There's two ways to get into sideload mode:
Manual way:
Manually enter recovery
Select Apply update from ADB
ADB way:
While in Android or recovery, issue the following command to your phone via ADB: adb reboot sideload
Either way, the device should read "Now send the package you want to apply to the device with "adb sideload <filename>"...

V0latyle said:
Were you using PowerShell or Command Prompt?
What were you doing on the phone?
There's two ways to get into sideload mode:
Manual way:
Manually enter recovery
Select Apply update from ADB
ADB way:
While in Android or recovery, issue the following command to your phone via ADB: adb reboot sideload
Either way, the device should read "Now send the package you want to apply to the device with "adb sideload <filename>"...
Click to expand...
Click to collapse
just windows 11 terminal, that should be powershell by default, dont think I've used anything else before tho
on the phone?
like nothing, I did it the way I asked you a few months back, the same I've done for the past 3 OTAs, disable modules, adb reboot sideload, followed by adb sideload <drag ota here>.
then the percentage didnt go up in terminal it said what I posted in OP
the phone only showed "verifying stuff", after like 8 mins I disconnected the phone and it showed like 100 lines of "failed to verify xxx" and then went back to fastbootd
i dont think the phone ever actually received the actual ota file.
it did read "now send the package..." then I did adb sideload ota-xyzyadayada.zip and thats what happened.

G5-User7080 said:
just windows 11 terminal, that should be powershell by default, dont think I've used anything else before tho
on the phone?
like nothing, I did it the way I asked you a few months back, the same I've done for the past 3 OTAs, disable modules, adb reboot sideload, followed by adb sideload <drag ota here>.
then the percentage didnt go up in terminal it said what I posted in OP
the phone only showed "verifying stuff", after like 8 mins I disconnected the phone and it showed like 100 lines of "failed to verify xxx" and then went back to fastbootd
i dont think the phone ever actually received the actual ota file.
it did read "now send the package..." then I did adb sideload ota-xyzyadayada.zip and thats what happened.
Click to expand...
Click to collapse
Odd, and Pixel Flasher worked - did you sideload or did you flash the factory image?

V0latyle said:
Odd, and Pixel Flasher worked - did you sideload or did you flash the factory image?
Click to expand...
Click to collapse
used PF's new "Full OTA" option, so sideload