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!
Related
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
OK. I have spent the last 8 hours reading and trying my darnedest to get my phone up and running.
I wiped everything, and formatted data accidentally.
Now the phone wont mount the USB so I can put a ROM on it. I cannot get drivers to make either the skipsoft toolkit or the WugFresh tool kit to work.
I have read on ADB side loading, but cannot figure out how to get the phone to get recognized in order to connect with it. As it sets right now, I am stuck at the bootloader image, or TWRP recovery. No image on the phone, and I cant seem to get the drivers to allow my PC to see the phone. (Ive used WugFresh drivers, naked drivers)
Any help you guys can give me would be awesome.
Thank you
Mark
Hey there,
Our phones are MTP devices and because of that (I think) we can't mount them as a usb drive. But yea you can use adb sideload to get yourself up and running again.
For the drivers try this: http://forum.xda-developers.com/nexus-4/orig-development/toolkit-skipsoft-android-toolkit-nexus-t1995688
On your Phone:
1. Boot into TWRP,
2. Tap advanced,
3. Tap adb sideload,
4. Swipe to start sideload.
Once it says its waiting or something like that, it's ready to sideload from the PC.
On your PC:
Put the rom you wanna flash in the same folder as adb. So if adb is in C:\adb\ then put the file there.
In CMD type in adb sideload filename.zip (filename.zip is the name of your file you want to flash)
So an example would be:
Code:
c:\adb>adb sideload CARBON-JB-NIGHTLY-20131117-1149-mako.zip
It'll take a bit to transfer the file, but once it finishes you should be able to boot into the rom and use it normally again.
Hope it works for you, regards...
You can use Wugfresh to restore to stock and start over.
Dear people of xda,
Recenlty ive receive a FOTA update to my device which runs 4.2.2. Being stupid, i did the update although i had cwm recovery installed on my devices. Now my device keeps bootlooping into cwm without being able to do anything.
Ive read tons of threads talking about this issue but i still cant get my to boot normally.
Yingy in this thread http://forum.xda-developers.com/showthread.php?t=2563527 had the same problem but the only diffrence is my pc cant recognize my device in order to do the adb fix by thecubed.
Im plugging my G2 for the first time in this computer and that is why i think my pc is failing to install drivers. I downloaded and instellad latest driver although windows device manger shows error devices not detected and the end of the process.
In order to fix my phone i just need to make me pc recognize my phone in adb although phone was never plugged before to this pc so i think my G2 wont let it access. I tried installing universal driver such as Pdanet as offered in threat but still when i write adb devices in cmd i get device offline!
Download latest adb drviers, lates lg g2 driver, lg user support tool does not recognize plugged device as well. All me sdk manger tools are patched to latest version.
PLEASE ive tried anything possible. spend like 9 hours and still nothing. i would really appriciate your help.
Thanks.
Edit: here my problem with pdanet drivers, it asks me to allow pc usb debbuging as shown in screenshot below but icant do it since im stuck at cwm recovery!
Solved!
BOOM!! after 12 hours i FINALLY manged to solved this problem. Really simple actually lol.
If anyone come across the issue please do the following:
1. Go to clockwork recovery as always, go to install zip from sdcard, choose install zip from sideload.
2. Plug your phone to pc.
3. Run adb with lastest drivers and sdk tools.
4. At the adb folder press shift+right click and start cmd.
5. write adb devices it should show your device id like this (xxxxxxxxx sideload).
6.Download latest twrp recovery from here http://teamw.in/project/twrp2/197 and if you have open europe version G2 like me download latest version from here: http://techerrata.com/browse/twrp2/g2d802
7.put the zip file in the adb folder, do not unzip it.
8. write in cmd console adb sideload xxxx.zip (xxxx is the name of twrp file).
9. cwm will flash twrp recovery over cwm.
10. reboot in recovery in advanced options.
11. now you have twrp recovery.
12. follow this guide : http://forum.xda-developers.com/showthread.php?t=2451696&nocache=1
13. THATS IT!!!
finally after going through this mess, im never using cwm recovery again. twrp is the best
good luck everyone!
Only Have in the Phone the CWM R 5.5.0.4 nothing more, i try to install the drivers in win 7 64 and allways fail :/ how i can solve this, i'm so nervous OMG
Relax, we got you.
Driver installation for Windows is not straight forward. Plug in your phone, then open device manager. You will see an unrecognized device there. Right click it, select settings. Click 'Update driver', then choose the 'From this computer' option. Select the driver folder you downloaded. This should work. If it doesnt, click on the option 'Chose from list of producers', select 'Android' or simply all devices, search for OPPO and select the appropiate driver (Android ADB interface).
This should install the driver correctly. After that, get ADB and fastboot up and running: http://forum.xda-developers.com/showthread.php?t=2588979
Install a current recovery via fastboot. Search the forum for how to do this in detail. The quick version is put your phone into fastboot mode, plug into PC, start fastboot and type 'fastboot flash recovery recovery.img'.
Then push a current ROM to your phone via ADB. Again, search the forum on how to do this. Do a full wipe in the recovery and install a new ROM.
Please report back if this worked so others with the same problem can use this in the future.
theevilworm said:
Relax, we got you.
Driver installation for Windows is not straight forward. Plug in your phone, then open device manager. You will see an unrecognized device there. Right click it, select settings. Click 'Update driver', then choose the 'From this computer' option. Select the driver folder you downloaded. This should work. If it doesnt, click on the option 'Chose from list of producers', select 'Android' or simply all devices, search for OPPO and select the appropiate driver (Android ADB interface).
This should install the driver correctly. After that, get ADB and fastboot up and running: http://forum.xda-developers.com/showthread.php?t=2588979
Install a current recovery via fastboot. Search the forum for how to do this in detail. The quick version is put your phone into fastboot mode, plug into PC, start fastboot and type 'fastboot flash recovery recovery.img'.
Then push a current ROM to your phone via ADB. Again, search the forum on how to do this. Do a full wipe in the recovery and install a new ROM.
Please report back if this worked so others with the same problem can use this in the future.
Click to expand...
Click to collapse
Its working, but now when i install the twrp 2.7.0.0 the touch don't work :/
samarain said:
Its working, but now when i install the twrp 2.7.0.0 the touch don't work :/
Click to expand...
Click to collapse
Flash this TWRP edition: http://forum.xda-developers.com/showthread.php?t=2435177
Working now.. Thanks alot for the big help
Sent from my amazing HTC One..
Good to hear! Can you post what you did exactly so others reading this thread can be helped too?
How did you push a ROM to your phone?
theevilworm said:
Good to hear! Can you post what you did exactly so others reading this thread can be helped too?
How did you push a ROM to your phone?
Click to expand...
Click to collapse
The only thing i need to know was what step i need make to detect the Oppo drivers, you say " click on the option 'Chose from list of producers', select 'Android' or simply all devices, search for OPPO and select the appropiate driver (Android ADB interface)." after that problem solved because i do this kind of things many times before in other phones and its easy.
When drivers are installed successfully just need to go to recovery "power + Vol. Down" and after write in the command window ( adb push "name of the rom.zip" /sdcard/ ) and he start copying the rom to the SD card, after that just install in the recovery choosing the rom in the root of the sdcard, and thats it! Easy :good:
I'm stuck right here as far as download mode goes.
I installed TWRP on a d800 rooted with stock 4.2.2. The TWRP install went ok but it never booted afterward.
I can get into twrp, but can't sideload anything because the computer does not connect to the device, I hear the connection noise the computer makes but nothing in the device manager.
any ideas?
May I suggest you use "adb push rom.zip /sdcard/rom.zip" instead of sideload (the sideload doesn't have to be enabled)
bender_007 said:
May I suggest you use "adb push rom.zip /sdcard/rom.zip" instead of sideload (the sideload doesn't have to be enabled)
Click to expand...
Click to collapse
Thanks, I get
error: closed
I was wrong about my computer not seeing my device, it's in the device manager under Android and the adb drivers are installed.
I also renamed the rom to "update" to make it simpler
What's up now ?
Sorted it out or still issues there ?
I also tried the adb shell method.
I also tried this method through TWRP terminal and nada.
If I did something wrong here let me know, hopefully I can get it up and going
bender_007 said:
May I suggest you use "adb push rom.zip /sdcard/rom.zip" instead of sideload (the sideload doesn't have to be enabled)
Click to expand...
Click to collapse
This is what I get when I do the above. The CMD prompt in located in the same directory as the adb files
ADB sees my device as this #
Gabriel51 said:
This is what I get when I do the above. The CMD prompt in located in the same directory as the adb files
ADB sees my device as this #
Click to expand...
Click to collapse
ok, let's do it like this
1. copy rom to c:\rom.zip
2. while in adb folder "adb push c:\rom.zip /sdcard/rom.zip"
that should work, you don't need sideload to be enabled.
Please test and report.
bender_007 said:
ok, let's do it like this
1. copy rom to c:\rom.zip
2. while in adb folder "adb push c:\rom.zip /sdcard/rom.zip"
that should work, you don't need sideload to be enabled.
Please test and report.
Click to expand...
Click to collapse
I moved the file to the root of my C drive changed the name to "rom.zip"
Copied the command you supplied and got this result
I know my phone is connected because I can reboot it by using the command " adb reboot"
I used this;
adb push C:\Android\sdk\platform-tools\rom.zip
And it is now ready to install through TWRP!
Hold your breath.......
Edit;
Failed but at least it's in the twrp list
"unable to open zip"
I think I got it, I was able to access the firmware update screen.
Sorry fir these incomplete responses, I don't want you to keep looking for a resolve while I do this.
If your still here?
I'll be back!
Success!
After nothing would work except for loading the rom through adb I decided to wipe the whole thing.
I reloaded the rom and when selected for install it opened instead of preparing for install so I thought I would reboot and when I did I was prompted by su that my device may have lost root and gave me the option to reinstall it, I chose yes and when rebooting it hung (normal) at the LG logo, however this time the charge light was flashing! I attempted to access "download" and was successful in loading the stock rom.
In the end it looks like TWRP was the culprit, it used to be my favorite but not for this device
All is well, thanks for your help...