Database Users

Fixing the device after a full wipe when ADB push/sideload wont work.

Problem was because the user with the problem had the wrong SDK files, it's fixed now. For the story and steps to fix the device press [SHOW]
Hey guys, this is a cross-post from the OPPO forums.
One of the guys needs some help, here's the story:
Okay, here is BUMBUMBUM's story:
"ok well first started yesterday by rooting my device then downloading goomanager from the playstore and using that to install TWRP recovery once I had that installed I downloaded a cm nightly and flashed it using TWRP it worked realized that stock firmware provided better battery life so I started searching for ways to unroot and return to stock saw a couple post about just flashing the stock rom so I went ahead and did it after I restarted my device noticed I still had TWRP so I went into recocvery and started wiping the dalvik/cache hoping it would return to stock didnt work so after couuntless wipes I think it was when I wiped the system that it started saying I had no OS"
"after I tried to connect my device to my computer to see if i could transfer the rom.zip that way but my computer wasnt recognizing the device so I went on the forums and xda and searched, I came across this post and followed the steps. But when I try to sideload it gives me the error *cannot read 'sideload* and if I try to push it to my device using adb push I get an error that I can not stat the file.."
I've tried to help him but I didn't succeed. As far as I know he did everything right..
He has all the drivers/the ROM and the correct settings but we still couldn't get it working.
Do any of you have any ideas?
Steps we went through:
1. Connect your phone make sure it's actually connected and you have the drivers.
If you don't have the drivers check this out: http://forum.xda-developers.com/showthread.php?t=1983470
2. Rename the ROM you want to flash to something basic, I used Find5.zip
3. Open CMD (command prompt), navigate it to the folder you placed the ROM
(e.g. code: cd C:\Users\Jelle\Downloads\ will navigate to my Downloads folder)
4. Boot to recovery on your phone and enable the ADB sideload function.
5. in CMD type adb sideload Find5.zip
6. Let TWRP or CWM flash the zip and prompt for reboot.
7. Reboot and be happy, your phone is fixed!

Found a way to get ADB Push working!
Hey Guys,
after I accidentially made quite the same mistake as posted above with my Find 5 I tried everything to get a Firmware on my Device.
Finally I got it working!
So here is how I did it:
1. Get all Drivers - google for ADB Driver for all Devices
2. Get the ADB Driver for the Find 5 ([oppo.com/index.php?q=software/view&sw_id=631) and unzip them!
3. Connect your Find 5 (While in TWRP) to your Computer important is not to select "adb sideload" just leave it like you got into recovery!!! then --> go to "Device Manager" and look for Android. The must be a warning. So rightclick on your device and click on install/update driver. Then after your computer can't find the driver go to the directory where you downloaded the Oppo Find 5 ADB drivers. Then select "manually search for local files" and choose the unzipped folder of the drivers. Then click next. After your PC installed the drivers download the Android SDK and try to get the ADB Shell working.
4. Download the latest Stock Rom and rename it to e.g. "stock".
5. Goto your cmd with running ADB and do "adb push /[path to your file]/stock.zip /sdcard
6. Hit Enter and wait for about 3 Minutes! (Don't Panic the file is large :silly
7. After the file was transfered succesfully, click on "Install" on your Phone and select the "stock.zip"
8. After installing reboot and enjoy your Find 5! :good:
Cheers,
Bent
I hope I could have helped some people, sorry if my explanation is not the best for you, I am German so my Windows does PM me for help!

Lg g2 Boot loops

I am not sure if I can post this solution in this thread as I am not a developer and merely sharing my experience, It seems several people are having issues with bootloops after installing att update or for some other reason, my post deals with helping only a certain issue. You should be able to boot into recovery by any means in order to use my solution.
The problem I had was I was trying to flash a new Rom and copied Rom and gapps into my phone( of course I was rooted and had recovery flashed) and then out of curiosity I wiped everything in advanced wipe in twrp so now I have no Rom to boot into or no file to flash and either download mode would not work, I was p******g in my shorts as I my phone was only a week old and its dead that's what I at least thought. And after spending the whole night no solution was found in xda website and neither did Google help any, now the solution. now u should compare this to ur problem and find where u stand. I installed pdanet on my pc as stock lg drivers don't seem to help pc recognize my phone in recovery mode, then I plugged my phone to pc while phone is still in recovery mode and then opened pdanet in pc and installed lg drivers through it and then adb was able to see my device(until now I was trying adb sideload and it wasn't working) so when adb was able to see my device, I used sideload in twrp and pushed Rom from pc to phone using sideload commands and my phone was back and I am the happiest man in the world. So in short
1. This method works only for people who can boot into twrp recovery but not into phone.
2. Have ur desired roms and gapps ready 3. Make sure u have a working adb in ur pc and if not install minimal adb and fastboot application only onto ur desktop for easy access, and copy ur desired Rom and gapps into that folder and rename them to 1.zip and 2.zip for easy reference and easy adb commands.
4. Download and install pdanet on your pc. Power on ur device into recovery and plug it into your pc. Start adb from the folder u installed on your desktop(hold shift and right click within the folder(minimal adb and fastboot) and click on start command here option, command opens up and it will show in which folder ur in and then type adb devices and if everything is right your phone in sideload mode should show up as adb sideload and if not (this is where the problem is) run pdanet and install lg drivers through it and then unplug exit sideload and restart sideload in ur phone and plug it back to pc and ur pdanet will notify u have connected ur lg phone. Then run adb again and type adb devices and it will show up as adb sideload and now (you should search how to use sideload as I don't remember those commands) and push Rom into (the ones u renamed for easy access and reboot and all should be all. Sorry for the lengthy post but I typed this solution into several posts individually and so decided to put it up as sticky and if anyone feels to remove part of or all the post I have no problem, just wanted to do my help to others with similar problem.
Sent from my LG-D800 using xda app-developers app

lingarajug said:
I am not sure if I can post this solution in this thread as I am not a developer and merely sharing my experience, It seems several people are having issues with bootloops after installing att update or for some other reason, my post deals with helping only a certain issue. You should be able to boot into recovery by any means in order to use my solution.
The problem I had was I was trying to flash a new Rom and copied Rom and gapps into my phone( of course I was rooted and had recovery flashed) and then out of curiosity I wiped everything in advanced wipe in twrp so now I have no Rom to boot into or no file to flash and either download mode would not work, I was p******g in my shorts as I my phone was only a week old and its dead that's what I at least thought. And after spending the whole night no solution was found in xda website and neither did Google help any, now the solution. now u should compare this to ur problem and find where u stand. I installed pdanet on my pc as stock lg drivers don't seem to help pc recognize my phone in recovery mode, then I plugged my phone to pc while phone is still in recovery mode and then opened pdanet in pc and installed lg drivers through it and then adb was able to see my device(until now I was trying adb sideload and it wasn't working) so when adb was able to see my device, I used sideload in twrp and pushed Rom from pc to phone using sideload commands and my phone was back and I am the happiest man in the world. So in short
1. This method works only for people who can boot into twrp recovery but not into phone.
2. Have ur desired roms and gapps ready 3. Make sure u have a working adb in ur pc and if not install minimal adb and fastboot application only onto ur desktop for easy access, and copy ur desired Rom and gapps into that folder and rename them to 1.zip and 2.zip for easy reference and easy adb commands.
4. Download and install pdanet on your pc. Power on ur device into recovery and plug it into your pc. Start adb from the folder u installed on your desktop(hold shift and right click within the folder(minimal adb and fastboot) and click on start command here option, command opens up and it will show in which folder ur in and then type adb devices and if everything is right your phone in sideload mode should show up as adb sideload and if not (this is where the problem is) run pdanet and install lg drivers through it and then unplug exit sideload and restart sideload in ur phone and plug it back to pc and ur pdanet will notify u have connected ur lg phone. Then run adb again and type adb devices and it will show up as adb sideload and now (you should search how to use sideload as I don't remember those commands) and push Rom into (the ones u renamed for easy access and reboot and all should be all. Sorry for the lengthy post but I typed this solution into several posts individually and so decided to put it up as sticky and if anyone feels to remove part of or all the post I have no problem, just wanted to do my help to others with similar problem.
Sent from my LG-D800 using xda app-developers app
Click to expand...
Click to collapse
I have more or less the same issue. Was with StockMod for D802 and received an official OTA and accepted and installed it. Now I'm stuck in bootloop. Unlike you, I can go into recovery (CWM not TWRP) BUT I can't seem to go into fastboot mode. When I hold the Volume Up and connect the phone through cable to my laptop, the phone boots but goes automatically into recovery mode. Did system wipe as well (which I shouldn't have) and at that point my phone has no OS to boot into so I used ADB to transfer CM 10.2 and GAPPS to my phone hoping that if I do it like I'm flashing a custom rom will help but unfortunately it didn't. I'm still stuck in bootloop and can't go into fastboot. help please...:crying:

Try a stock Rom and see if it helps.
Sent from my LG-D800 using xda app-developers app

[Q] Big issue with my Sprint LG G2 after I cleared the system

So I deleted everything in my phone, including the Rom I wanted to flash (smart, right?) and all I have is TWRP Recovery mode and Download Mode. When I put my phone into any mode, my PC does not recognize it and I therefor cannot fix it... I've tried it on three computers with downloading and updating the drivers. The first time it works after installing and updating the drivers, but when I put it in the second time it does not work. I need to unplug my phone in download mode while doing the LG program, and the computer won't recognize or find my phone. All help is greatly appreciated and thanks to repliers in advance
Day 2 of not having a phone: I can't do this xD I need to fix it somehow, if anyone can help me please do

Boot to recovery and start adb sideload mode. Then from your computer just adb sideload rom.zip
If your phone doesnt install the drivers once in sideload mode then manually search for the adb bridge driver from the android sdk and install it.

x714x said:
Boot to recovery and start adb sideload mode. Then from your computer just adb sideload rom.zip
If your phone doesnt install the drivers once in sideload mode then manually search for the adb bridge driver from the android sdk and install it.
Click to expand...
Click to collapse
Tried that and it would say "device not found." and other error codes. One time I was able to load my device onto the computer and after it completed the CM 11 transfer it stopped. I may have to order an OTG cable or something...

Stuck in CWM - device not recognised

Hi
I flashed CloudG3 rom under CWM, and after install it won't boot the system - it sends me to CWM recovery instead.
Figured I would install another ROM but my device is not recognised by windows (won't show up under my computer). Can you please guide me on what I could do to sort this?
Thanks

Install the lg g2 drivers to get recognised by the os, after you download driver for adb sideload and restart, run sideload in the recovery with the usb pulgged in ur pc.
Open Android folder, and then do to platform-tools, drag a ROM there to be installed. Open a command in this folder. Write what is in the cellphone, adb sideload romfilename.zip if i'm right, then it will start installing and then you get out of the recovery stuck.
Using TWRP.

Hi
I installed lg drivers but it didn't help - looked like it was CWM that was causing an issue to get the device detected by computer.
Before you posted, I followed the instructions here http://forum.xda-developers.com/showthread.php?t=2739739 - this helped to get TWRP on top of CWM. Under TWRP, the device is detected by windows
Now should I install a rom using your guidance above or can I do it under TWRP? Or is it the same?

Oneplus One with fastboot and TWRP functioning, but can't get a ROM working

I really need help, I have tried the following, having TWRP V2.8.5.1 functioning and Fastboot also.
- Through TWRP, tried connecting the PC so I can Flash a ROM from there, but I can't seem to be able to connect the One to my PC so it will let me transfer files through cmd with adb push. My computer is a windows 10 OS with Samsung drivers and Android SDK full installed, still can't get it to work.
- Through Fastboot tried flashing cm-11-20141008-SNAPSHOT-M11-bacon.zip downloaded from Cyanogenmod page and using Oneplus One Toolkit 2.0, even though the Toolkit says the files are there, still phone continues to show 1+ logo and then rebooting.
Please I need some help.
Cheers. and thank you.

Why adb push when you can just copy the file over using a file manager (or a command prompt if you insist) and then flash from the internal storage?

I'm having the same issue but in my case I can boot into recovery or other stuff IF I HAVE THE USB PLUGGED IN
Maybe you can check and and let me know, if I found a solution I'll tell you, hoping the same from you please.

http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541 this could help.