So I was screwing around with a NP I bought off of ebay trying to get it to update. I was trying to get stock 6.0 on before I installed Pure Android. I don't recall exactly where I screwed the pooch, but all I can do now is boot into recovery and the only ADB option is to sideload an update from a .zip. I'm running ubuntu with up to date ADB tools. When i run 'adb devices' nothing shows up until I select 'apply update from ADB' at which point the device shows up, but only ever in sideload mode. I've been searching for a couple of hours but I haven't been able to find a thread that offers me any help. I'm not even sure what file I should be updating with. Any help would be greatly appreciated. Thanks.
Just to let you know, adb won't run unless you choose "apply update from adb". This is normal. Did you try pushing a zip from the forums?
prophetjinn said:
Just to let you know, adb won't run unless you choose "apply update from adb". This is normal. Did you try pushing a zip from the forums?
Click to expand...
Click to collapse
I'm not sure what zip to push.
Related
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!
Hey guys,
i'm really sorry to bother you, i'm normally not the type of guy who jumps to "help me" real quick. However, since there doesnt seem to be anyone else with my Problem, and i couldt fix it by reading stuff myself, here i go.
Basically, i started off with a brand new internat. G2, D802. I didnt accept any OTAS.
I rooted it with ioroot, no problem. Afterwards, i installed CWM 6.0.4.4. Semi-touch as described in this thread: http://forum.xda-developers.com/showthread.php?t=2468858. Still no problem. Everything booted fine, no bootsloops, no nothing. Perfect so far.
Made a Nanondroid, saved my EFS. Backed it up. So far so good.
Then, i dl´ed the newest CM 11 Nightly, 12.12.2013. I went into Recovery, and did FactReset -> Format Sys -> Wipe Cache -> Wipe Dalvik
When i tried to install CM, a "status 7 error" was returned, i can give the complete message any time. Maybe i hit a corrupt download, idk.
Well, under "mount storage", connect an usb storage didnt work, so i guess i´m stuck with sideload.
I read some tutorials, and when showing the devices with my phone being in recovery, it shows "XXXXXX (some number, guess my mac-adress), recovery". SO i guess thats fine.
I then enabled "install zip via sideload" in cwm, and did "adb sideload /PATH/NEWLYDOWNLOADEDROM.ZIP". Wont work, all it returns is the list of commands.
Doing "adb push /PATH/ROM.ZIP /sdcard/XXX" does seem to copy something, however, when accessing that folder, it says theres no zip there.
i'm kind of at a loss now. Entering CWM works without fail, but how to proceed? I still have the Nandroid on my phone to resort to, but well, id rather get stuff working.
Thanks for help guys. All your hard work is appreciated.
Well, i managed to push stuff to my phone successfully now, still that error: set_metadata_recursive: some changes failed.
Googling stuff returns that it seems to be an error with CWM. However, i am still using the latest version. Even so, how do i up/downgrade (maybe offical version) in cwm itself? Or do i have to use a 3rd party programm.
how were you able to push to the phone? I cant get ADB to read my phone through twrp
Owell, ended up fixing stuff myself.
What i did was:
Download an the official CWM from http://forum.xda-developers.com/showthread.php?t=2468858.
Then go to where your adb stuff on your pc is, shift+right click -> open command prompt here. Connect your phone to the pc via usb cable, while beeing i recovery (i guess cwm or twrp shouldnt matter).
In Cmd, do:
adb kill-server
adb start-sever
adb devices
that should bring up something like [Some Number, your phones mac-address] recovery
all the while, do not start "install zip via sideload" in your recovery. I did not need that at all.
in your command prompt, type:
adb push PATH_TO_YOUR_DOWNLOADED_RECOVERY/WHATEVER_ITS_NAME_IS.zip /sdcard/WHATEVER_ITS_NAME_IS.zip
it will copy the recovery to your /sdcard-folder.
Type "adb kill-server" and unplug phone (did it just to be sure, idk if its necessary)
In your recovery, just install the downloaded .zip-recovery, and under "advanced" do reboot recovery.
It left me with a touch version of cwm 6.0.4.4, the same version number as before. However, this time installing the latest cm-11 nightly worked just fine.
Idk if the unofficial one is bugged, but best someone post that in the cwm-recovery thread. I cant, since my post are not over 9000.
Hope it helps.
im having this issue on my VZW LG G2. Im stuck in CWM getting Status 7 abortions when trying to flash cm 10.2. Rooted with io. I was on OTA 12B and looking for a fix.
Fixed it myself, thanks.
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...
Hi guys,
Unable to boot after c*cking up a manual upgrade from B10 to B11 on my A2017G and would love your input. I feel like if I can just install TWRP again it should be an easy fix. Here's some specifics:
1. my phone is unlocked, rooted and running stock firmware.
2. I was trying to install stock recovery to install the B11 update. I did so but also tried to install another zip (B10 bootloader?) which I seem to have flashed wrong. Now just get the screen as shown on attachment and cannot boot.
3. Stock recovery seems to have been flashed and I can boot to this. From here I can boot to bootloader but can't seem to do anything from there.
4. I try update via ADB with the sideload command, but get the message "E:footer is wrong. E: Signature verification failed. Installation aborted".
5. I try to Update from SD as have the firmware zip file and TWRP on the root of my external SD card, but get the message "Couldn't Mound /sdcard, aborted."
6. The only time my phone shows as a connected device in ADB is when I try to sideload files. No other ADB code seems to work, only get the message "error: closed" on the terminal.
Assuming I've got all the firmware files (and full backups on my external SD) I feel like if I can just install TWRP again it should be an easy fix. So, any ideas on how I install TWRP given situation above?
Best,
Neil
nstirton said:
Hi guys,
Unable to boot after c*cking up a manual upgrade from B10 to B11 on my A2017G and would love your input. I feel like if I can just install TWRP again it should be an easy fix. Here's some specifics:
1. my phone is unlocked, rooted and running stock firmware.
2. I was trying to install stock recovery to install the B11 update. I did so but also tried to install another zip (B10 bootloader?) which I seem to have flashed wrong. Now just get the screen as shown on attachment and cannot boot.
3. Stock recovery seems to have been flashed and I can boot to this. From here I can boot to bootloader but can't seem to do anything from there.
4. I try update via ADB with the sideload command, but get the message "E:footer is wrong. E: Signature verification failed. Installation aborted".
5. I try to Update from SD as have the firmware zip file and TWRP on the root of my external SD card, but get the message "Couldn't Mound /sdcard, aborted."
6. The only time my phone shows as a connected device in ADB is when I try to sideload files. No other ADB code seems to work, only get the message "error: closed" on the terminal.
Assuming I've got all the firmware files (and full backups on my external SD) I feel like if I can just install TWRP again it should be an easy fix. So, any ideas on how I install TWRP given situation above?
Best,
Neil
Click to expand...
Click to collapse
Are you able to boot into EDL mode by typing ADB reboot edl ?
If so you can flash desired recovery with axon7tool
marcus.linkenbach said:
Are you able to boot into EDL mode by typing ADB reboot edl ?
If so you can flash desired recovery with axon7tool
Click to expand...
Click to collapse
Hi, thanks for your reply. Unfortunately not, just get the message "error: closed" in the terminal. Is there a button combination I could press in order to get into EDL?
nstirton said:
Hi, thanks for your reply. Unfortunately not, just get the message "error: closed" in the terminal. Is there a button combination I could press in order to get into EDL?
Click to expand...
Click to collapse
Try vol+ + vol- + power
it seems that the only time my device will show as connected in ADB is when I navigate through Recovery and select the "Apply Update from ADB" option. But even then, whilst it shows as connected, it only seems to allow the "sideload" command. Please see screenshot of Terminal. So at no other time will it show as a connected device.
Similarly, to have it show up in Device Manager, it'll only show when I switch the phone off, hold down Vol+ & Vol- and attached the power cable.
You are still on MM. So you are able to boot into bootloader.
adb reboot bootloader
fastboot devices
Now it should show your device as fastboot
If so you can now flash recovery with “fastboot flash recovery recovery.img“
marcus.linkenbach said:
You are still on MM. So you are able to boot into bootloader.
adb reboot bootloader
fastboot devices
Now it should show your device as fastboot
If so you can now flash recovery with “fastboot flash recovery recovery.img“
Click to expand...
Click to collapse
Thanks for your reply. Unfortunately as mentioned the only time my device shows as connected in Terminal is when I select "Update via ADB" whilst in recovery. Otherwise the device never shows as connected in adb.
So unfortunately fastboot doesn't seem to be an option for me.
Perhaps my drivers are out of whack but assuming what I've done to my phone hasn't changed that, it must be something PC - side.
nstirton said:
Thanks for your reply. Unfortunately as mentioned the only time my device shows as connected in Terminal is when I select "Update via ADB" whilst in recovery. Otherwise the device never shows as connected in adb.
So unfortunately fastboot doesn't seem to be an option for me.
Perhaps my drivers are out of whack but assuming what I've done to my phone hasn't changed that, it must be something PC - side.
Click to expand...
Click to collapse
But what if it shows your device as sideload? Can't you there reboot into fastboot?
No, it doesn't accept the command. Only one accepts is sideload. You can see from my screenshot a few posts back that the device is connected but shows different to how it normally would.
Breakthrough!
I seemed to follow the steps I've tried 100 times today and I now have TWRP installed again!
Thanks again to those who helped