Develop Bugs

[Find7a] [X900x] CWM Base Recovery 6.0.3.7 + TWRP + Easy ROOT Method

Install ClockworkMod Recovery 6.0.3.7 (CWM) or Team Win Recovery Project (TWRP) on Oppo Find 7a FHD (X900x) + Easy ROOT Method
Warning: Note: No one but yourself is responsible for what you do to your device.
X9007 = Chinese TD-LTE support // X9006 = EU FDD-LTE or US FDD-LTE support
Requirements:
Download / unzip the file --> AndroidSDKSlim.zip
Download one of the following two files --> X9007_CWM_recovery.im OR X9007_TWRP_recovery.img
Make sure you have a charged battery (50 % minimum)
How to install: ​
Connect your phone to your PC. You should see a window with the drivers in an application called 'setup.exe '.
Start the installation process and wait until it ends. then disconnect the phone from the PC.
Extract the contents of the file ' AndroidSDKSlim.zip ' on your desktop. You should have a folder named ' android-sdk-windows ' where there is another folder: 'platform-tools.'
In this folder, move the two .img files you downloaded ( X9007_TWRP_recovery.img X9007_CWM_recovery.img )
​
Turn off your mobile.
Restart your mobile in fastboot mode by pressing the High Volume + Power buttons until the appearance of the word ' Fastboot ' .
Connect your phone to your PC via the USB cable.
In platform-tools folder 'with your mouse, do' right click 'while holding down the 'Shift ' button, then select ' Open a command window here . '
​
In this window, type the following code to verify that your device is recognized.
Code:
fastboot devices
​
Then type the following command to install the TWRP or CWM :
For the TWRP
Code:
fastboot flash recovery X9007_TWRP_recovery.img
For the CWM
Code:
fastboot flash recovery X9007_CWM_recovery.img
​
Once the process is finished, disconnect your phone from your computer, then simultaneously press the buttons ' power ' and 'volume down ' until you feel a vibration.
Your phone will reboot into your new custom recovery.
Select ' reboot system now ' to reboot your phone !
How to root : ​
Just download the attached file --> UPDATE-SuperSU-v1.94.zip
Copy/paste it on your memory phone
Reboot into recovery mode
Flash the file & next reboot your phone
Enjoy ! You're root !
Video : Root method & Flashing Custom recovery by C4ETech
Note
If you don't want to root your phone by this way,(With CUSTOM Recovery) you can see this Thread -->> ROOT method with OPPO Recovery Stock
Credits & Thanks
Dees_Troy
jmz
mazwoz
sammycakes
Chainfire
C4ETech
TonyStark​
Your feedback is welcome​ ​

Stock OPPO recovery
Flashable ZIP file --> oppo_recovery_v1.0.20140421-find7a.zip
Flash the ZIP file using TWRP or CWM recovery
Fastboot method IMG file --> oppo_recovery_v1.0.20140421-find7a.img
Flash the IMG file with this fastboot command :
Code:
fastboot flash recovery oppo_recovery_v1.0.20140421-find7a.img

Does this work for the X9006 international model?
Gesendet von meinem MI 2 mit Tapatalk

MrColdbird said:
Does this work for the X9006 international model?
Gesendet von meinem MI 2 mit Tapatalk
Click to expand...
Click to collapse
Hi,
Yes I think there is not difference betwen the X9007 & X9006. Need confirmation to be sure. Wait for first feedbacks. There is Only frequency bands difference I think...
X9007 = Chinese TD-LTE support
X9006 = EU FDD-LTE or US FDD-LTE support

should do a linux version. I rooted mine once i got it lol

Nice one! Now all I need is for the phone to arrive Was worried about whether there would be any development going on but it seems I was concerned about nothing.
Cheers.

Can anyone post a nandroid backup of the international model
i want to try it on my chineese model in order to get frznch language fully working
Actually i use morelocale 2 but some stuff are still in english
Thanks
Sent from my X9007 using xda app-developers app

houz said:
Can anyone post a nandroid backup of the international model
i want to try it on my chineese model in order to get frznch language fully working
Actually i use morelocale 2 but some stuff are still in english
Thanks
Sent from my X9007 using xda app-developers app
Click to expand...
Click to collapse
How about trying to install the ColorOS 2.0 International Beta? Includes French (as well as Google Play Services and is rooted)

Thank you!
im from Viet Nam.
Can i copy your post to devteam sir?

mrkimi84 said:
Thank you!
im from Viet Nam.
Can i copy your post to devteam sir?
Click to expand...
Click to collapse
Hello
If you give credits yes

Wipe
Is it Wipe ?
Are Oppo's update still available ?
Thanks

Any update on this being safe for the X9006 yet?
Got my phone today!!!

Just wanted to confirm the TRWP push worked great on my X9006 last night. Used included SuperSU to root and I'm all set! Well at least until the custom ROMs start flowing

No change in performance or anything?
Sent from my X9006 using XDA Free mobile app

jgunna405 said:
No change in performance or anything?
Click to expand...
Click to collapse
No change.
If anything a bit faster since I used TiBu to uninstall some stock system junk.
I will warn you though, with TWRP you can't run the stock OS updates (and one was released just this morning).
I'm hoping somebody will be able to find a way around that shortly with a custom zip for TWRP containing the updates though.

Dang, just opened up my phone, came to XDA to root so I can restore my saved apps and delete some system apps but now I can't get the OTA lol. Oh well, only a matter of time until the newest OTA is available via a flashable zip or at the least we can flash the stock recovery so we can OTA.

Yeah, no insult to this work which is great to have but for the moment I figured we were more likely to see a factory bug fix or two like the one that just got pushed before omni hits primetime so I decided to use the kedros method for now.

Hi eveybody
I Added the link towards second ROOT method on first post
Hope You'll like it

I believe with the OTA that went out since then, this custom recovery method may be invalid. I cannot flash CWM or TWRP using your method described above
(tried to share the image on dropbox, but not letting me for some reason. Here is a copy and paste of what I am getting) -
Directory of C:\TEMP\AndroidSDKSlim\android-sdk-windows\platform-tools
05/07/2014 10:07 AM <DIR> .
05/07/2014 10:07 AM <DIR> ..
05/07/2014 10:03 AM 819,200 adb.exe
05/07/2014 10:03 AM 96,256 AdbWinApi.dll
05/07/2014 10:03 AM 60,928 AdbWinUsbApi.dll
05/07/2014 10:03 AM <DIR> api
05/07/2014 10:03 AM 160,256 fastboot.exe
05/07/2014 10:03 AM 727,881 NOTICE.txt
05/07/2014 10:03 AM 16,654 source.properties
05/07/2014 10:03 AM <DIR> systrace
05/07/2014 10:05 AM 13,877,248 X9007_CWM_recovery.img
05/07/2014 10:07 AM 15,233,024 X9007_TWRP_recovery.img
8 File(s) 30,991,447 bytes
4 Dir(s) 181,535,727,616 bytes free
C:\TEMP\AndroidSDKSlim\android-sdk-windows\platform-tools>fastboot devices
8e72e3fc fastboot
C:\TEMP\AndroidSDKSlim\android-sdk-windows\platform-tools>fastboot flash recover
y x9007_CWM_recovery
error: cannot open 'x9007_CWM_recovery'
C:\TEMP\AndroidSDKSlim\android-sdk-windows\platform-tools>fastboot flash recover
y X9007_CWM_recovery
error: cannot open 'X9007_CWM_recovery'
C:\TEMP\AndroidSDKSlim\android-sdk-windows\platform-tools>fastboot flash recover
y X9007_TWRP_recovery
error: cannot open 'X9007_TWRP_recovery'

Hi
I dont know try with another computer. @seanpr123 has confirmed that the TWRP works
Envoyé de mon GT-I9305 en utilisant Tapatalk

Help with reset...

So I decided to try to run ubuntu touch on my Samsung Galaxy Nexus(verizon). All went well, but now it seems I cant start the phone, can only get into fastboot mode. Can anyone please walk me through the steps of putting stock android back on my phone? I have adb and fastboot installed on my computer. There's a guide here that walks you through the process of returning the phone to stock software/firmware, but it requires USB debugging to be on, which I can't turn on because the phone won't boot up. I greatly appreciate any help!!!
Phone Info(what's written in fastboot):
PRODUCT NAME-Tuna
VARIANT- toro 32GB
HW VERSION- 9
BOOTLOADER VERSION: PRIMELC03
BASEBAND VERSION- I515.FK02 CDMA-I515.FK01
CARRIER INFO- NONE
SIGNING- production
LOCK STATE- UNLOCKED

You dont need USB debug on in order to use fastboot
---------- Post added at 05:39 PM ---------- Previous post was at 05:38 PM ----------
Debugging is only needed if using adb.
But if u already in fastboot bootloader mode then u don't need to do "adb reboot bootloader" command

ashclepdia said:
You dont need USB debug on in order to use fastboot
---------- Post added at 05:39 PM ---------- Previous post was at 05:38 PM ----------
Debugging is only needed if using adb.
But if u already in fastboot bootloader mode then u don't need to do "adb reboot bootloader" command
Click to expand...
Click to collapse
Thanks for the pretty fast response! I'm still lost as to how I can make everything go back to the way it is (i.e, get rid of ubuntu and get android back on ) . Definitely my last time trying to muck around with roms and such D;

vsp3317 said:
Thanks for the pretty fast response! I'm still lost as to how I can make everything go back to the way it is (i.e, get rid of ubuntu and get android back on ) . Definitely my last time trying to muck around with roms and such D;
Click to expand...
Click to collapse
Don't give up!
Once you've done it once or twice it becomes easier, everything starts to make sense
Did you download one of the Google factory img for toro to your computer? Get it from here
https://developers.google.com/android/nexus/images
(It will be under the Mysid/toro name) any of the available ones will work that are for toro.
---------- Post added at 06:19 PM ---------- Previous post was at 06:17 PM ----------
Then you just uncompress the file, open command prompt(aka terminal) in that folder/directory , put device into fastboot mode(bootloader), and then execute the flash all script that comes with the factory IMG download.
---------- Post added at 06:26 PM ---------- Previous post was at 06:19 PM ----------
Oh, and to easily open a command prompt in that directory, uncompress the factory img download file from that site linked above, then open the folder to view it's contents. Hold shift and right click within the folder and choose "open command prompt"
Then all you should need to do is put "flash-all.exe" and hit enter in the command prompt that pops up once device is connected and in fastboot(bootloader)mode. (No quotes...just enter the text) and then be patient. The flashing of the radio files might seem to take a long time especially the CDMA radio. Do NOT unplug or anything before it is completed fully)
If need anymore info ask away

ashclepdia said:
Don't give up!
Once you've done it once or twice it becomes easier, everything starts to make sense
Did you download one of the Google factory img for toro to your computer? Get it from here
(It will be under the Mysid/toro name) any of the available ones will work that are for toro.
---------- Post added at 06:19 PM ---------- Previous post was at 06:17 PM ----------
Then you just uncompress the file, open command prompt(aka terminal) in that folder/directory , put device into fastboot mode(bootloader), and then execute the flash all script that comes with the factory IMG download.
---------- Post added at 06:26 PM ---------- Previous post was at 06:19 PM ----------
Oh, and to easily open a command prompt in that directory, uncompress the factory img download file from that site linked above, then open the folder to view it's contents. Hold shift and right click within the folder and choose "open command prompt"
Then all you should need to do is put "flash-all.exe" and hit enter in the command prompt that pops up once device is connected and in fastboot(bootloader)mode. (No quotes...just enter the text) and then be patient. The flashing of the radio files might seem to take a long time especially the CDMA radio. Do NOT unplug or anything before it is completed fully)
If need anymore info ask away
Click to expand...
Click to collapse
Wow, I can't thank you enough man!!! :highfive: That worked like a charm , no problems at all . And oh it's "flash-all.bat" not .exe, for the people that might come across this thread later. Thanks again though, I really don't know what I would've done. Definitely going to do a **** ton more research next time I decide to go and flash a rom haha.

vsp3317 said:
Wow, I can't thank you enough man!!! :highfive: That worked like a charm , no problems at all . And oh it's "flash-all.bat" not .exe, for the people that might come across this thread later. Thanks again though, I really don't know what I would've done. Definitely going to do a **** ton more research next time I decide to go and flash a rom haha.
Click to expand...
Click to collapse
No problem buddy
That's what these forums are for, learning, helping, development, all that good stuff! Just happy it went smoothly for ya.
I think it used to be named .exe, at least it shows as exe on my laptop but I use Linux so it could just be seeing it differently(since I have wine installed)
There is usually a windows executable and a Linux .sh script that can be executed from the terminal to start the process.
See, it's not all THAT bad now is it? Especially since now you know how to do it, messing up the device isn't such a daunting thing anymore lol.
As for keeping status 7 from happening again I highly recommend bookmarking the TWRP or CWM official sites so that before flashing things in the future, you can make sure you have the most up to date custom recovery installed by comparing what is available vs what you have installed(booting into recovery mode will usually have the version info somewhere on the main screen) and of course having a recent nandroid backup made within your current custom recovery. I prefer TWRP but it's a personal choice to each user which they use
Just don't be afraid to play around
Congrats again on your first soft brick&restore! Lol
It's such a relieving feeling once you bring device back from the dead ain't it?

[ROOT][D5322][Lollipop][Update]Stable root guide, r/w fix, no FTF requirements

Hello guys,
Today I am presenting stable rooting method for D5322_19.3.A.0.470_Lollipop 5.0 without any old FTF requirement or fear of data loss etc.
Requirements
D5322 with Unlocked bootloader
Current firmware version should be 19.3.A.0.470
Flashtool with updated fastboot and flashmode drivers
50% Battery and a Safe backup (In case of error)
Happy mind
Downloads
1. Recovery kernel (Please download DUAL_RECOVERY_D5322-LP.img for best result) ====>> Here (16 MB)
(Recovery kernel credits goes to our respectable XDA Recognized Contributor @abcdjdj)
2. SuperSU.zip ===> Here (Tested)
3. Download BusyBox ===> Here Tested v1.23.1-Stericson.zip
Rooting procedure
Move SuperSu.zip, BusyBox.zip to your devices and turn off it.
Put downloaded D5322_19.3.A.0.470_Lollipop 5.0.ftf in flashtools firmware folder
Open Flashtool and connect your device in FASTBOOT mode by holding volume UP key.(Blue LED)
Flash recovery kernel in fastboot mode and disconnect the device.
Turn on device,press volume down button continusly when you see pink LED.
Flash SuperSU and BusyBox
Wipe cache and delvik
Turn on device -- Rooted + No read write issue + No SD card problem
Rare issue
=> Some users may face system app removal problem ==> Fix Here
=> Flashtool Cannot unbundle files (Very rare) ==> Fix Here
Feel free to ask questions ......

Not able to perform step 10.
error as :
Click to enlarge image
10/010/2015 18:10:29 - INFO - Selected Bundle for Sony Xperia T2 Ultra (D5322). FW release : 19.3.A.0.470. Customization : Lollipop 5.0
10/010/2015 18:10:29 - INFO - Preparing files for flashing
10/010/2015 18:10:29 - ERROR - Cannot delete C:\Users\'@#&\.flashTool\firmwares\prepared\boot
10/010/2015 18:10:29 - INFO - Cannot open bundle. Flash operation canceled
---------- Post added at 06:45 PM ---------- Previous post was at 06:12 PM ----------
any help?
---------- Post added at 07:18 PM ---------- Previous post was at 06:45 PM ----------
stuck at step 10, help me buddy.. I am waiting

Buddy, It seems your end problem == user account permission // corrupt download // file is using by another process

what to do?
no process is running or using any file..
---------- Post added at 07:30 PM ---------- Previous post was at 07:28 PM ----------
all I think is problem is with this file only
4. D5322_19.3.A.0.470_Lollipop 5.0 kernel (9MB)
can you reupload or send me this file? 5.0 or 5.0.2 kernel so I can start my device
---------- Post added at 07:58 PM ---------- Previous post was at 07:30 PM ----------
step 10 problem SOLVED
Figured it out! thnx to @ kentexcitebot
I went through C:\Users\name\.flashTool\firmwares and deleted the "prepared" folder under the folder "firmwares".
That fixed the problem, apparently.
Now device is about to boot.. waiting for boot complete

I went through C:\Users\name\.flashTool\firmwares and deleted the "prepared" folder under the folder "firmwares".
That fixed the problem, apparently.
Now device is about to boot.. waiting for boot complete
Click to expand...
Click to collapse
Similar to "FILE IS USING BY ANOTHER PROCESS" Delete means you forced to terminate the process..

rrajesh said:
Similar to "FILE IS USING BY ANOTHER PROCESS" Delete means you forced to terminate the process..
Click to expand...
Click to collapse
yes... my bad.. you need to update steps.. as someone else might get same problem.
root access worked properly. :good:
now my problem is xposed installer.. how to install?
tried flashing zip, but device won't boot.

Xposed is not not available for our device yet...Wait until it fixed for our device. .. You can delete all xposed files to get rid on bootloop.
Solution
1. Flash recovery kernel from #1 post
2. Get rid on Xposed bootloop HERE manually : no flash required

I am not being harsh
I am just letting know what is happening, sorry if I sound harsh
already uninstalled xposed.
ok, so finally I manage to get it working,
1st performed clean installation of 5.0.2 ftf
then followed steps 1 to 9
then deleted the "prepared" folder under the folder "firmwares", (If existed).
then followed step 10 & 11.
started device & updated everything.
I got proper root access & everything is working fine :good:
Thank you :good:
Only problem is, cant boot in Recovery now, after everything is done successfully.

Hw u managed to work xposed on our phne its nt possible as it is not working anymore @rrd84

Thanks bro, root successful but cannot remove/uninstall system apps please help

Check Dis thread @joseph LR http://forum.xda-developers.com/showthread.php?t=3096863

pvnsai73 said:
Hw u managed to work xposed on our phne its nt possible as it is not working anymore @rrd84
Click to expand...
Click to collapse
NO, xposed is not working, bootloops, I said I managed to fix my problem of step 10.
you misunderstood me
---------- Post added at 08:03 PM ---------- Previous post was at 07:56 PM ----------
joseph LR said:
Thanks bro, root successful but cannot remove/uninstall system apps please help
Click to expand...
Click to collapse
yes.. preinstalled apps are not uninstalling by this root method, everything else is good.
but kingo root method can uninstall them, kingo root is chinese root tool,
but I am not able to replace kingo root SuperUser with supersu,
thats y I am sticking with this thread root method.
---------- Post added at 08:11 PM ---------- Previous post was at 08:03 PM ----------
pvnsai73 said:
Check Dis thread @joseph LR http://forum.xda-developers.com/showthread.php?t=3096863
Click to expand...
Click to collapse
I am having this problem, any help?
whichever option I select, mobile either reboot or poweroff
click image to enlarge

joseph LR said:
Thanks bro, root successful but cannot remove/uninstall system apps please help
Click to expand...
Click to collapse
Dear joseph LR,
You can download following apps from PlayStore
Download R/W Checker from HERE
[Open and tap to R/W, if successful your root is with r/w is ok]
System App remover (Using since 2012) Download
Enjoy!!

Dear @rrd84,
I worked on recovery and Xposed with different methods whole Sunday,,,but not working.. RC LED blinks but phone boot normally always
I think we should wait until @Nut (XZ Developer) fix it..
.

@ rrajesh
Thanks for R/W Checker
working perfectly now
yes.. we should wait until @Nut (XZ Developer) fix it..

No Recovery Mode D5322 since rooted Kitkat 4.4.3
I am not able to do Step 6 as my device doesn't boot into recovery mode. Is there any other way of flashing SuperSU and BusyBox? Please help me. Can I flash them using flashtool?
Thank you

badboy_0077 said:
I am not able to do Step 6 as my device doesn't boot into recovery mode. Is there any other way of flashing SuperSU and BusyBox? Please help me. Can I flash them using flashtool?
Thank you
Click to expand...
Click to collapse
No, you can't flash them using Flashtool
Read 1st post carefully for recovery mode...

????
about step no. 4 Flash recovery kernel in fastboot mode and disconnect the device can any one tell me what to do exactly in pic if possible

rustynail1985 said:
about step no. 4 Flash recovery kernel in fastboot mode and disconnect the device can any one tell me what to do exactly in pic if possible
Click to expand...
Click to collapse
#Download recovery kernel an put it on C:\Users\[ UR NAME] \.flashTool [latest flashtool]
#Connect your device in fastboot mode ( Hold volume up and now inset usb...Wait 15Sec)
#Open flash tool ,, click on Flash Device (First icon)
#Select fastboot
#Select flash kernel (Browse downloaded file. change file type sin to img in explorer)
#OK

rrajesh said:
No, you can't flash them using Flashtool
Read 1st post carefully for recovery mode...
Click to expand...
Click to collapse
I did all the steps successfully . But im not able to use flodermount. It gives error unable to write to sd. Root explorer also not mounting to r/w. NextappSd also showing error. Phone is successfully rooted. Please help

Unable to sideload community build

I am trying to install the latest community build , I download a latest version of 3.5.3 from OnePlus's download section.
Currently I am on 3.2.7 , not rooted and boot loader is locked. All factory setting
these are the steps
check and make sure USB debugging is on
connect the device to PC
adb reboot recovery
device goes to recovery , select language and select install from adb on my phone
checking to make sure device is recognized and authorized
adb devices
50f4f77f sideload
************************************
adb sideload Update.zip
loading: 'Update.zip'
* cannot read 'Update.zip' *
I know I am in a correct folder as I already a did a <dir> and verified update.zip is in the current folder but lets try this
adb sideload C:\adb\Update.zip
loading: 'Update.zip'
* cannot read 'Update.zip' *
:crying:
at this point I am sure there is something wrong with the zip file. so I delete it and download the 3.2.6 just to test it out and I was able to downgrade to 3.2.6 with adb sildeload. once installation was complete I tried again to download 3.5.3 and sideload it but still getting a cannot read <filename> error.
any idea what I am missing here ?
By the way , I have tried several options such as :
1- changing the location of the file from adb folder to other location
2- renaming the file
3- launching cmd prompt as an administrator and navigating to the file location

Hello,
I have a strong feeling that you are trying to flash a wrong zip file. Can you mention the size of file that you mentioned as "update.zip"?

catrawalkar said:
Hello,
I have a strong feeling that you are trying to flash a wrong zip file. Can you mention the size of file that you mentioned as "update.zip"?
Click to expand...
Click to collapse
"OnePlus3Oxygen_16_OTA_003_all_1609142002_2a17363c90cd462e.zip" is the name of the file

nima352000 said:
"OnePlus3Oxygen_16_OTA_003_all_1609142002_2a17363c90cd462e.zip" is the name of the file
Click to expand...
Click to collapse
Then why are you giving command of update.zip? You should write the name of file in the command.
Replace "update.zip" in your command to the name of file as it is.

catrawalkar said:
Then why are you giving command of update.zip? You should write the name of file in the command.
Replace "update.zip" in your command to the name of file as it is.
Click to expand...
Click to collapse
As I mentioned in my post I have already tried that this was my last attempt as many folks out here saying that "renaming" the file helped them

nima352000 said:
As I mentioned in my post I have already tried that this was my last attempt as many folks out here saying that "renaming" the file helped them
Click to expand...
Click to collapse
Can you post a screenshot of your command prompt and folder that contains zip file?

catrawalkar said:
Can you post a screenshot of your command prompt and folder that contains zip file?
Click to expand...
Click to collapse
sure , here it is

I had this issue when I tried to download the first time. The zip is corrupted. I downloaded the file again and update your adb and fastboot version. I am sure it should work fine.
---------- Post added at 08:35 AM ---------- Previous post was at 08:29 AM ----------
I also suspect the issue could be due to renaming the filename manually into update.zip and when the extension is hidden, it becomes update.zip.zip. please crosscheck to be double sure.

Reboot your computer after you download the file.
I know it sounds weird but I have to do it every time I download the community builds and I've no idea why...otherwise they give the same error. Don't rename the file either there's no need.

nima352000 said:
sure , here it is
Click to expand...
Click to collapse
There could be renaming issue. Try re-downloading file and let me know if you have resolved the issue..

Renaming the file is only for the sake of convenience. Or else you may end up giving a wrong file name by typing error when giving the sideload command as the file names are usually too long.
In this case the file should have been corrupt (not fully downloaded).

Try opening the .zip file.
If it is corrupted, the CRC will fail and it won't open.
In which case you know you have a bad download.

debasish.patra said:
I had this issue when I tried to download the first time. The zip is corrupted. I downloaded the file again and update your adb and fastboot version. I am sure it should work fine.
---------- Post added at 08:35 AM ---------- Previous post was at 08:29 AM ----------
I also suspect the issue could be due to renaming the filename manually into update.zip and when the extension is hidden, it becomes update.zip.zip. please crosscheck to be double sure.
Click to expand...
Click to collapse
Hi , I did try to reinstall the adb drivers , but I will give it a shot again. Also as far as renaming the file the file in the above screen shot is originally downloaded from OnePlus's website without renaming. >dir command shows the file extension to be correct ending with .zip not zip.zip ..
anyways I will reinstall the adb drivers again today

Roxas598 said:
Reboot your computer after you download the file.
I know it sounds weird but I have to do it every time I download the community builds and I've no idea why...otherwise they give the same error. Don't rename the file either there's no need.
Click to expand...
Click to collapse
will give this a try . download a fresh copy with original name , reboot the PC and retry ? is that the sequence you are suggesting ?

kgs1992 said:
Try opening the .zip file.
If it is corrupted, the CRC will fail and it won't open.
In which case you know you have a bad download.
Click to expand...
Click to collapse
doesn't look like that was the case . was able to open the .zip file just fine

nima352000 said:
will give this a try . download a fresh copy with original name , reboot the PC and retry ? is that the sequence you are suggesting ?
Click to expand...
Click to collapse
Yep that's it mate

debasish.patra said:
I had this issue when I tried to download the first time. The zip is corrupted. I downloaded the file again and update your adb and fastboot version. I am sure it should work fine.
---------- Post added at 08:35 AM ---------- Previous post was at 08:29 AM ----------
I also suspect the issue could be due to renaming the filename manually into update.zip and when the extension is hidden, it becomes update.zip.zip. please crosscheck to be double sure.
Click to expand...
Click to collapse
by the way may I get the link to "adb and fastboot version" which you are referring to ? just wanted to make sure I am on the right track

What version of adb are you using?
Your screen print shows 944,128 bytes whereas mine shows 1,479,680 bytes for adb.exe
eg output from the command "adb version"
Android Debug Bridge version 1.0.36
Revision 8f855a3d9b35-android
Looks like you are on:
>adb version
Android Debug Bridge version 1.0.32
Revision eac51f2bb6a8-android

Roxas598 said:
Yep that's it mate
Click to expand...
Click to collapse
it actually worked ! thanks a bunch mate !

for anybody who is having the same issue and interested what was the solution , I download a new copy of .zip file from OnePlus websire . restarted my PC and tried again and it worked . Can't make any sense of it but that was the solution

Unlocking Bootloader/ Magisk Attempt

MAGISK FULL GUIDE (APK for install and other mods coming soon!)
The bootloader unlock is pretty similar to any other phone.
Go to settings>about> click on build number until developer options are enabled. Go back and select system>Developer Options. Make sure to enable OEM unlocking.
(On PC) "adb reboot bootloader", "fastboot flashing unlock_critical", use volume to select unlock. THIS WILL ERASE ALL CONTENT ON YOUR DEVICE.
IF YOU DONT WANT TO DO THIS FROM SCRATCH, SKIP TO PART 2
Go to https://support.microsoft.com/en-us/surfacerecoveryimage
Select Surface Duo from the drop down
Enter your serial number and download the file
Extract the firmware .zip
Extract the Payload file
Moved bootloader to root
Installed Magisk Manager apk and patched bootloader image
Attempted to flash which resulted in "cannot write to partition_b"
PART 2:
download the patched magisk_boot.img from here https://drive.google.com/file/d/1-7NWj8_jFH8AtpTTpXITOv1eh-wo7xlz/view?usp=sharing
adb reboot bootloader
fastboot boot magisk_patched.img
PART 3 - All right, lets make it permanent!
Place magisk_patched.img on your sd root
adb shell
su
cd /dev/block/by-name/
chmod 777 boot_a
chmod 777 boot_b
DEV=$(ls /dev/block/by-name/boot_b); echo $DEV
dd of=$DEV if=/sdcard/magisk_patched.img
DEV=$(ls /dev/block/by-name/boot_a); echo $DEV
dd of=$DEV if=/sdcard/magisk_patched.img
Reboot and we are good!
I am working on an app to streamline the process as well as provide additional mods and addons to the device. I hope to have something for you guys by the end of the week.
I do plan on streaming some of this stuff (twitch.tv/goingh0st), and am working on a section of my discord for the same thing (World of Gh0st)
https://www.patreon.com/GoinGh0st
Thank you for your support and I cant wait to get more stuff to you guys!

Would you mind sharing the patched Boot?
Everything you posted is spot on, try switching partitions.

Perseu5 said:
The bootloader unlock is pretty similar to any other phone. Go to settings>about> click on build number until developer options are enabled. Select oem bootloader unlocking. Adb reboot bootloader, fastboot flashing unlock, use volume to select unlock. This will erase all content on your device.
Go to https://support.microsoft.com/en-us/surfacerecoveryimage
Select Surface Duo from the drop down
Enter your serial number and download the file
Extract the firmware .zip
Extract the Payload file
Moved bootloader to root
Installed Magisk and patched bootloader image
Attempted to flash which resulted in "cannot write to partition_b"
Attempted to boot the patched boot image which resulted in a bootloop.
Out of town for the time being but will be attempting something different when I get back in a day or so.
Click to expand...
Click to collapse
I tried the same and I had the same issue. Seems the the boot partitions, both a and b, are not writable or erasable even with the bootloader unlocked.
I even went as far as unlocking critical and still the same issue.
Sent from my Surface Duo using Tapatalk

really????
try different USB CABLE! DO NOT USE type C to C.
Use USB-A to C

So anyone tried my method? Should work

avetny said:
really????
try different USB CABLE! DO NOT USE type C to C.
Use USB-A to C
Click to expand...
Click to collapse
Haven't had time to try, but I was using c to a cable
Sent from my Surface Duo using Tapatalk

bxmoney181 said:
Haven't had time to try, but I was using c to a cable
Sent from my Surface Duo using Tapatalk
Click to expand...
Click to collapse
u mean usb type A to C?

avetny said:
u mean usb type A to C?
Click to expand...
Click to collapse
Yup
Sent from my Surface Duo using Tapatalk
---------- Post added at 07:29 PM ---------- Previous post was at 07:27 PM ----------
avetny said:
So anyone tried my method? Should work
Click to expand...
Click to collapse
Have you confirmed successful flash of partitions??
Sent from my Surface Duo using Tapatalk

bxmoney181 said:
Yup
Sent from my Surface Duo using Tapatalk
---------- Post added at 07:29 PM ---------- Previous post was at 07:27 PM ----------
Have you confirmed successful flash of partitions??
Sent from my Surface Duo using Tapatalk
Click to expand...
Click to collapse
ok I'll try it tomorrow after work my self

I'll be back in town tonight, I was in fact using a c to c cable so hopefully a a to c cable will work. Should be back by 8 and will attempt it then!

Perseu5 said:
I'll be back in town tonight, I was in fact using a c to c cable so hopefully a a to c cable will work. Should be back by 8 and will attempt it then!
Click to expand...
Click to collapse
im still at work....
Please try it out....I remember in my pass that was a issue with many phones

Perseu5 said:
I'll be back in town tonight, I was in fact using a c to c cable so hopefully a a to c cable will work. Should be back by 8 and will attempt it then!
Click to expand...
Click to collapse
How did it go?

Just tried with a to c cable with same result unfortunately. Sending successfully, writing boot_b gives flashing not allowed to this partition. Also did a critical unlock and verified with fastboot oem device-info

wtf!!!!!!!!
---------- Post added at 09:21 PM ---------- Previous post was at 09:11 PM ----------
...... I will return this phone man.

I'm not sure with anything about unlocking and rooting (noob atm) but i noticed in developer settings that the default USB configuration is set to "No data transfer"
Is that by any chance causing the write issues?

panzercool said:
I'm not sure with anything about unlocking and rooting (noob atm) but i noticed in developer settings that the default USB configuration is set to "No data transfer"
Is that by any chance causing the write issues?
Click to expand...
Click to collapse
Nah that's not it. I was once that's there too lol. Keep reading and keep learning.
Sent from my Surface Duo using Tapatalk

bxmoney181 said:
Nah that's not it. I was once that's there too lol. Keep reading and keep learning.
Sent from my Surface Duo using Tapatalk
Click to expand...
Click to collapse
Would you post the patched boot image?
I want to try this myself without going through the prerequisite hoops.

Updating the main post now. I figured it out guys!

Perseu5 said:
Updating the main post now. I figured it out guys!
Click to expand...
Click to collapse
oh broo tell us whats happening

Perseu5 said:
Updating the main post now. I figured it out guys!
Click to expand...
Click to collapse
Tell us!!!