Develop Bugs

[Q] any idea on getting root

i know it just came out and all but my room mate got one and we were hoping someone will look for root i have an evo so i dont think i can help him much plus i dont know code so just wondering
thanks

I bought the Motorola Bravo which is similar to the Flipside and an app on the market called Z4ROOT was able to root the phone. It works on many phones not just the Bravo. Give that try and see if it works.

z4root does work for permanent root i have tried and can confirm

jediskywalker said:
i know it just came out and all but my room mate got one and we were hoping someone will look for root i have an evo so i dont think i can help him much plus i dont know code so just wondering
thanks
Click to expand...
Click to collapse
Rooting a Motorola Flipside
Download drivers for the phone:
http://www.motorola.com/staticfiles/Support/Experiences/Global_Drivers/USB_Drivers_bit_4.7.1.zip
With the phone unplugged from the USB, install the drivers
grab the ADB SDK files
http://dl.google.com/android/android-sdk_r08-windows.zip
Extract SDK files somewhere you will remember, and can easily type (for ease of use only)
Download z4root:
(you may need to sign up to download)
http://forum.xda-developers.com/attachment.php?attachmentid=446145&d=1290341328
Copy z4root.1.3.0.apk to your SDK folder
ON YOUR PHONE:
go to Apps Menu->Settings->Applications->Development and check "USB debugging"
Plug in your phone, and have it set to "Charge only"
go to the command prompt, and type
cd C:\"PATH TO SDK" <ENTER>
Now, type
adb install z4root.1.3.0.apk
Once that is complete, you can now go find Z4 in your programs list. I chose "permanently root". Your phone will
reboot, and then you are rooted.
Unknown sources is still disabled at this point, but you can now install apps that require super user
Tonight, I will try to enable "Unknown Sources" on my flipside.
UPDATE: To get "Unknown Sources" enabled, go to this thread:
http://forum.xda-developers.com/showthread.php?t=867637

Got my Flipside rooted and non market apps allowed
I followed the instructions given at modmymobile dot com forum. Look up "fully unlock 3rd party apps backflip" It allowed me to root my phone and install non market apps. I tried and tried to follow the instructions given here, but i guess they weren't idiot proof. It is for the backflip, but it worked perfectly for my Flipside. I couldn't post the link here.

Someone found some typos in my scripts. I have updated them so they are accurate. Should make things run better.

Hey I kinda need some help. I've gotten through all the way to entering "adb install z4root.1.3.0.apk" into the command prompt but all I get is a message saying "adb" is not recognized as an internal or external command, operable program or batch file. Anyone have any ideas on how this could be happening?

ishiiisbooyah said:
Hey I kinda need some help. I've gotten through all the way to entering "adb install z4root.1.3.0.apk" into the command prompt but all I get is a message saying "adb" is not recognized as an internal or external command, operable program or batch file. Anyone have any ideas on how this could be happening?
Click to expand...
Click to collapse
Lets say you installed your SDK in the default folder, you would need to type
Code:
cd c:\"Program Files"
cd Android
cd appinventor-extras
Now, I put mine in c:\SDK, so all I type is
Code:
cd c:\SDK
you either must add the SDK to your PATH, or find the directory that you installed it to, and then try running adb from there. If adb.exe isn't in the folder, you aren't in the right folder.

jonsjava said:
Rooting a Motorola Flipside
[/url]
Click to expand...
Click to collapse
hi
i m new in unlocking field
can i unlock this handset "flipside" by motorola came from usa at&T
if yes then plz explain
thanks in advance

RZ4root does not appear on the marketplace and when I click the link above it starts to download, then says the content is not supported on my phone.
Model num MB508 Motorola Flipside running Android 2.1 update 1.

You need to push it to the phone from a computer using adb to install z4root, now that it has been removed from the market.
Sent from my Liberty using Tapatalk

adb.exe not in the zip file
jonsjava said:
Rooting a Motorola Flipside
grab the ADB SDK files
android-sdk_r08-windows.zip
Extract SDK files somewhere you will remember, and can easily type (for ease of use only)
(...snipped...)
go to the command prompt, and type
cd C:\"PATH TO SDK" <ENTER>
Now, type
adb install z4root.1.3.0.apk
Click to expand...
Click to collapse
adb.exe is not present in the SDK that you linked. Are you sure that is the SDK we need to root the Flipside?

You have to install it manually. It comes with the platform-tools.

how do i install adb.exe from platform-tools
lol, i may ask stupid questions but this one wasnt me, i shouldnt leave my laptop lying around haha

jonsjava said:
Rooting a Motorola Flipside
Download drivers for the phone:
http://www.motorola.com/staticfiles/Support/Experiences/Global_Drivers/USB_Drivers_bit_4.7.1.zip
With the phone unplugged from the USB, install the drivers
grab the ADB SDK files
http://dl.google.com/android/android-sdk_r08-windows.zip
Extract SDK files somewhere you will remember, and can easily type (for ease of use only)
Download z4root:
(you may need to sign up to download)
http://forum.xda-developers.com/attachment.php?attachmentid=446145&d=1290341328
Copy z4root.1.3.0.apk to your SDK folder
ON YOUR PHONE:
go to Apps Menu->Settings->Applications->Development and check "USB debugging"
Plug in your phone, and have it set to "Charge only"
go to the command prompt, and type
cd C:\"PATH TO SDK" <ENTER>
Now, type
adb install z4root.1.3.0.apk
Once that is complete, you can now go find Z4 in your programs list. I chose "permanently root". Your phone will
reboot, and then you are rooted.
Unknown sources is still disabled at this point, but you can now install apps that require super user
Tonight, I will try to enable "Unknown Sources" on my flipside.
UPDATE: To get "Unknown Sources" enabled, go to this thread:
http://forum.xda-developers.com/showthread.php?t=867637
Click to expand...
Click to collapse
Notice:
For anyone having trouble rooting the Motorola Flipside with these instructions, after much trial and error I managed to get my girlfriend's rooted. I'll provide the method I took.
Note: The easiest way to do this is to have downloaded and extracted "android-sdk_r08-windows" directly to your (C: ) drive. Not under programs or another system folder.
Once you have it extracted to (C: ), copy and paste z4root.1.3.0.apk into the "android-sdk_r08-windows" folder. ADB.exe will most likely not be in here. What you have to do now is click on SDK Manager within the SDK folder. A Black Command window will pop-up, ignore it. A secondary window will pop-up prompting you to install the packages I went ahead and installed all of them (better if you don't know which to install).
Now that they've all been installed, a command line will state that ADB has to be restarted. Let it restart and it should say completed.
Now -- here's where everything was messing up. When you click open the SDK-R08 folder, you should have the z4root.apk file right there amongst a list of folders. Go to the "platform-tools" folder and in there you should see the ADB.exe file. Ignore that for now. While in platform-tools press Ctrl+A so that everything is highlighted. Right click and select Cut, back out to the main directory of the SDK R08 folder and select Paste so that the ADB.exe, .dll, and all the other files from within platform-tools is out and listed alongside the z4root.apk.
Next - Follow all of the instructions up to "Plug in your phone, and have it set to "Charge only" Like JonsJava said, open up command prompt (type in CMD in the "search programs and files bar"). If you extracted the "android-sdk-r08-windows" file directly to the (C: ) drive, all you have to type in is...
(Note: Before I go into that, it'll be easiest to rename the file "SDK" instead of the whole "android-sdk, etc, name... I'll complete the instructions assuming you renamed it to SDK. Continued below... all you have to type in is...
cd C:\SDK
(The next line below will look like this)
c:\SDK>
Here, type in... adb install z4root.1.3.0.apk
Total should look like... c:\SDK>adb install z4root.1.3.0.apk
Hit enter and it should go through a few instructions. From there look in the applist on your phone for z4root, click on it and select permanently root. Your phone will restart. From there you're rooted (test by downloading an app which requires root) and don't have to worry about the low memory issues every again. Glad I got the Captivate, lol. So much easier to root, rom, and overclock.
Last note:
Uploaded with ImageShack.us
This is what the main directory of the SDK folder should look like before you enter anything in the command line.

I don't seem to be able to get this...
I'm using x64 windows 7, I have a Flipside MB508 on 2.1, and I can't get this to work.
I followed all the instructions, updated all the platform-tools stuff, and now my problem lies with the driver, I believe.
I installed those Motorola drivers that were linked, with my phone unplugged, successfully..
copied the apk to C:\SDK...
found adb.exe in the platform-tools folder..
...and this happened..
C:\SDK\tools>cd C:\SDK
C:\SDK>cd platform-tools
C:\SDK\platform-tools>adb install C:\SDK\z4root.1.3.0.apk
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
C:\SDK\platform-tools>adb install C:\SDK\z4root.1.3.0.apk
error: device not found
C:\SDK\platform-tools>_
"error: device not found" every time i try this
USB debugging is on, phone is plugged in set to charge only..
Windows even sees it, the taskbar eject icon says 'Eject MB508"
please please help me get adb to see my phone.. I really want to be able to root this thing!!
EDIT: I noticed the Motorola drivers are 32bit.. I'm going to try 32 bit windows 7 instead of 64 bit and see if I get more successful results
EDIT 2: Bazinga!! Installed Win7 32 bit on my other HDD, booted up, followed the steps again, worked flawlessly! Thanks a lot for the easy instructions, got z4root installed, and my phone worked with permanent root

ErebusRaze said:
Notice:
Hit enter and it should go through a few instructions. From there look in the applist on your phone for z4root, click on it and select permanently root. Your phone will restart. From there you're rooted (test by downloading an app which requires root) and don't have to worry about the low memory issues every again. Glad I got the Captivate, lol. So much easier to root, rom, and overclock.
Click to expand...
Click to collapse
You wrote in here that once rooted, thebphone would no longer have low memory issues...i rooted my wife's phone, was able to sideload applications (but for some strange reason I am now unable to, as adb command prompt states 'device not found')- but she still gets low memory issues at least 2-3 times a week...

I should just hold up a sign...
LINK2SD
Its in the market
Sent from my MB508 using XDA App

Link2sd? What does this do? I briefly looked at the thread, but it is not entirely clear. The flip side is running 2.1. With this app, can we free up space by moving apps to the sd card? I thought that was only possible in 2.2?

thehotrod11 said:
Link2sd? What does this do? I briefly looked at the thread, but it is not entirely clear. The flip side is running 2.1. With this app, can we free up space by moving apps to the sd card? I thought that was only possible in 2.2?
Click to expand...
Click to collapse
Link2sd makes installing to sd card possible on 2.1...
Sent from my MB508 using XDA App

How to enable ADB on ALLWINNER A13 9" - 4.2.2 - Windows 7 - error:device not found

How to enable ADB on ALLWINNER A13 9" - 4.2.2 - Windows 7 - error:device not found
Hi folks, my target is to do a full backup of my android tablet device without rooting nor installing app's on the device. It can be done just by the ADB tool and the simple command
Code:
adb backup -apk -shared -all
.
Basic information
PC: Windows 7, pro. USB 2.0 port. ADB Driver "Drivers-AllwinnerA10-32bits\32Bit_Win_7_Vista_XP" from 2011. ADB Platform-Tool, Android Debug Bridge version 1.0.31. Logged in as normal User, not Admin. The development kit is not installed, I just downloaded the Platform-Tool, unzipped it and started "adb" - I just want to make a f***ing backup :crying:
Tablet:
ALLWINNER A13 9". Android Version 4.2.2. USB Debugging enabled. Detail Info's:
Model number: JL902
Kernel Version: 3.4.0+ [email protected] #1 Mon 25.11.2013
Build-Number: full_gs702c-userdebug 4.2.2 JDQ39 eng.root.20131207
NOT ROOTED.
Problem:
I do not get a connection from the PC to the tablet. Also no RSA Key question comes up at the tablet. The adb tool just throws an error :"device not found". I tried several things, log in as Admin, "adb wait-for-device", plugging and unplugging ... nothing helped. The adb tool works fine, I tested it with a Samsung Galaxy S2. I'm not quite sure about the adb USB driver on windows, but there is no exclamation mark nor other problems reported. So this should be fine.
Anyone any hint, tip or solution? Would be great - gathering for hours with this problem - searching forum 'n stuff....
Thanks in advance
Juha

Try with uberizer or MTKDroid tools. Just connect and select adb terminal.

kramkumar said:
Try with uberizer or MTKDroid tools. Just connect and select adb terminal.
Click to expand...
Click to collapse
Thx 4 the hint, tried uberizer:
Code:
ERROR No useable device has been found
I think since in Android 4.2.2 the RSA Key authentication was introduced, something is wrong with the connection. Because I would expect the RSA Key question on the tablet, but the tablet does not show this dialog.
By the way, I recognized that the USB driver for the ADB interface is titled "Drivers-AllwinnerA10" but the tablet has a A13 core. But I do not find another driver at the moment and the vendor ID -VID_10D6&PID_0C02&REV_0202&MI_01- fits (otherwise, windows wouldn't install it anyway). Does it make sense to search for another driver?

hi from messing with various drivers and android devices i have found that installing PDA net for windows (theirs and android version too but not needed) once pdanet installs let the drivers for your phone be installed, if by any chance you have drivers already installed what you can do is go to device manager, click on your device uninstall the drivers, unplug your phone and then open pdaNET a window will come up waiting for you to connect your phone and the driver installation process will begin.
The program downloads the correct driver for mostly any model phone you have and works flawlessly with ADB, if by any chance this helped just give me a thanks !

abstractVoid said:
The program downloads the correct driver for mostly any model phone you have and works flawlessly with ADB, if by any chance this helped just give me a thanks !
Click to expand...
Click to collapse
Thanks for the tip. It really installed an USB driver as you said (I've deinstalled the other driver before). But sadly the result is the same. I can't access the ADB interface - same error "Device not found".
At this point I want to say thanks to all viewers of this thread, it seems really to be not an easy task. I'm still open minded in any direction and would be happy for any suggestion what I might try.
Even a hint, how I could reduce the possibilities for the root of my problem. I'm still not quite sure, if the driver is the problem or even if the tablet itself has some kind of software defect on this kernel version - By the way, does anyone have the same kernel version (posted at the beginning - 3.4.0+ [email protected] --- repeated for your convenience) of Jelly Bean (4.2.2)? Do you have experience with the ADB interface then?
How may I isolate the real problem? Any idea wellcome :cyclops:

I have nearly an identical tablet except mine has the PnP code of Vendor 10D6/Device 0C01 and it shows as P706 on the USB description.
I installed PDAnet, that actually was able to upload the Android version of PDAnet to the tablet, so I think that's a definite for the driver working. But I'm also having trouble getting ADB to list the device and I'm using the latest ADB from the SDK. Since ADB tries to setup a network server, I'm wondering if the ADB driver on windows has to be tethered as a NIC somehow?, just a theory.
I'm using a fresh install of XP and can do a complete rollback, so I'm certain it's not the OS.
There's also another quirk about this tablet. I wanted to do a backup of the firmware from this device. Techknow's utilities use ADB to issue several shell commands to copy "partitions" to the SD card, I thought I might as well try to do that manually only to find what would've been copied as /dev/block/nanda, nandb, etc. is named /dev/block/acta, actb, etc. instead. But lack of "root" means I can't read any of those partitions or even copy su into /sbin.
Uberizer isn't any good since as far as I can see that also uses ADB. Any known issues with versions of ADB? or even any other tools which do similar to ADB?, or even a way to "root" these devices just by Terminal and SD?
Regards

Ah, okey, soz I got the USB thing a bit mixed up. My tablet does have the same code, I assume the 0C01 is when it's in recovery mode (power on with volume + pressed)
I also realised the driver that was working wasn't one from PDAnet.
I've updated the working 32-bit driver with the version of ADB I'm using and included it in the attachment. Maybe you can try that and see if you have any progress.
I'll keep posted on this thread.

SOLVED!
Copy .android from the attachment into your %USERPROFILE% directory (i.e. C:\Document and Settings\<user> on XP or C:\Users\<user> on Windows 7)
You can check what the user directory is by DIR %USERPROFILE% in the "DOS" command line (%USERPROFILE% is case sensitive).
ADB should list your device when you do adb devices in the "DOS" command line.
Basically, adb_usb.ini with a custom identifier was missing.
Regards,
qUE

Right, I've made up a pack to automate putting SU on the device and setting up permissions on SU and BUSYBOX.
!!! This is only for the VID_10D6&PID_0C02 device, your mileage may very with other devices. !!!
DRIVER directory should contain the USB driver you need, otherwise try installing PDAnet and tell it to replace the driver.
Install USB driver, run SUME.BAT
to hopefully backup all the needed stock firmware to SD;
adb shell
su
cat /dev/block/acta > /mnt/sd-ext/acta.img
cat /dev/block/actb > /mnt/sd-ext/misc.img
cat /dev/block/actc > /mnt/sd-ext/system.img
exit
exit
adb kill-server
qUE

Confirmed solved
qUE-ARM said:
SOLVED!
Copy .android from the attachment into your %USERPROFILE% directory (i.e. C:\Document and Settings\<user> on XP or C:\Users\<user> on Windows 7)
<SNIP>
Basically, adb_usb.ini with a custom identifier was missing.
Click to expand...
Click to collapse
CONFIRMED SOLVED
Yes, that was it! I copied the adb_usb.ini file into the .android user directory (which only contains these ascii chars "0x10D6" - no CR no LF or anything else) and it worked out !!!
Thank you (Thanks meter will follow ) Some interesting things I discovered now:
There was no RSA-Key question at all on the tablet!!!
as I did the full backup with "adb backup -apk -shared -all" I was asked on the tablet to confirm this
So obviously something strange is going on here. Since it is claimed everywhere the with Android 4.2.2 the ADB interface should be generally RSA-Key protected. Okay, might be that I misunderstood something here :silly:
At least this problem is solved and I appreciated every comment in this thread. One question would be final to answer:
Who should have brought the adb_usb.ini to my PC. The ADB driver ? The ADB Platform-Tool package? So, whom to blame here - NO - just kidding :laugh:

I did briefly try the platform-tools (since I didn't mind the OS being trashed), they didn't add any adb_usb.ini and there isn't any real indication the file was needed/didn't exist, they could've simply put a note on the ADB utility when it didn't find any devices.
I'm not sure what ADB backup does. As far as I know the mounted partition images are differently named to various backup tutorials, so I get the feeling ADB backup just simply copies the user data and not much else. I recommend doing the backup I mentioned as well, it'll at least capture a copy of the boot partition, which if the device doesn't have that you'll probably need to revert to using live suite or some other firmware utility to restore it. Getting the firmware for that is another story, read a fair amount of posts here and other places on the net that don't sound fun.
I personally still can't get superuser to behave for using su on the terminal/term.apk (I want to remove useless "system" apps and make sure the device isn't talking back to anyone, i.e. google), but I'll keep tinkering.
My main aim for getting one of these tablets was to boot other firmware from the SD slot, but it looks as if the u-boot process is locked to internal NAND. So might have to modify it by adding "fatload mmc" to the script.
qUE

Quick Update;
Right the permissions thing turned out to be an issue with Superuser, dunno why. So replace the su binary from SuperSU (http://forum.xda-developers.com/showthread.php?t=1538053) into my SUME pack and install the Superuser.apk by;
adb root
adb shell mount -o rw,remount /system
adb push Superuser.apk /system/app
as for stripping back the Applications, I've got it down to this as bare bones
adb pull /system/app backup\system\app
to backup system applications before you do anything
I found if you do delete any applications and then android gets stuck at the logo, just adb push them back and it'll boot without reboot when you've got the chain right.
minimum applications needed for boot are;
DefaultContainerService.apk
DefaultContainerService.odex
SystemUI.apk
SystemUI.odex
Launcher2.apk
Launcher2.odex
Settings.apk
Settings.odex
SettingsProvider.apk
SettingsProvider.odex
ActSensorCalib.apk
InputDevices.apk
InputDevices.odex
FusedLocation.apk
FusedLocation.odex
LatinIME.apk
LatinIME.odex
PackageInstaller.apk
PackageInstaller.odex
ApplicationsProvider.apk
ApplicationsProvider.odex
A few odds and sods missing will make settings close, but it's trivial stuff. Personally don't like the sound of Fused Location, but it won't boot without it and I haven't seen any dodgey traffic from it (yet).
I recommend installing Droidwall with adb push /system/app, before installing games.
And modifying /etc/hosts with 127.0.0.1 to certain you know whos and advertisers.
Some of my personal choice replacement applications (so far);
Total Commander over ES file explorer.
Opera Classic over the inbuilt browser (although I'm still trying to remove the default search engine).
qUE

More update;
Discovered some new things;
BACKUP FILES WITH "ADB PULL" BEFORE MODIFYING ANY FILES!!!
I think performancepolicy.apk needs to be added to the bare bones application list, afaics from looking inside the package it sets system performance stuff, so likely throttling to preserve battery power.
bin_cfg.xml in /misc which can be modified by
adb shell mount -o rw,remount /misc
then adb pull, edit and push the file back
the line in there for "backlight_brightness" 780;1020;780 can be changed to 240;1020;240 which dims the backlight substantially saving battery power. not sure if 240 is the absolute minimum, but 120 seems to be too low afaics. interestingly information on the settings is in the files named _userview.xml
build.prop in /system which can be modified by
adb shell mount -o rw,remount /system
then adb pull, edit and push the file back
and then chmod 644 /system/build.prop
the lines in there for ro.wifi.signal.level.# can all be set to 0, this theoretically cuts the wifi power usage to less than 1mW, again saving battery. if android doesn't boot fully on reboot it's because chmod hasn't been set, you should be able to adb back in and correct.
please be careful modifying either file as both seem to have safety limits imposed on certain device components (i.e. battery temprature), messing with those can make the tablet stop working.
qUE

Trying to Flash the Stock Rom Via ADB sideload

I am Trying to flash the stock rom via side load i flashed that few days back to at that time it was flashed success fully but now it always gives me error
Code:
"C:\android-sdk\platform-tools>adb sideload OnePlus3TOxygen_28_OTA_039_all_1701140132_de9036f11e2246a8.zip
loading: 'OnePlus3TOxygen_28_OTA_039_all_1701140132_de9036f11e2246a8.zip'
* cannot read 'OnePlus3TOxygen_28_OTA_039_all_1701140132_de9036f11e2246a8.zip' *
C:\android-sdk\platform-tools>adb sideload <OnePlus3TOxygen_28_OTA_039_all_1701140132_de9036f11e2246a8.zip>
The syntax of the command is incorrect.
C:\android-sdk\platform-tools>"

Mine would not sideload either. I downloaded the zip file to my PC, connected the phone to the PC, put the phone in USB mode, dragged the zip file from the PC to the phone root directory, disconnected from the PC, and flashed the ROM from the phone hard drive.

Faulty ADB drivers I guess. If you have TWRP you can try adb push name /sdcard/

Puddi_Puddin said:
Faulty ADB drivers I guess.
Click to expand...
Click to collapse
Isn't obvious this is not a driver problem?! Read the error message that is staring him in the face. He has not specified the correct file/path.

bulletmark said:
Isn't obvious this is not a driver problem?! Read the error message that is staring him in the face. He has not specified the correct file/path.
Click to expand...
Click to collapse
Second one is a invalid command because of those <> first command mainly happenda with wrong drivers, I and many other get the error it is quite unexplainable.

Any resolution to this? I'm getting the same problem, saying it cannot read the zip file when I try to sideload

trying to update my wifes phone now. getting the same issue. i typed in adb devices and it shows up, so i know its not driver related. wonder if its a faulty image? ill keep trying
---------- Post added at 03:59 AM ---------- Previous post was at 03:55 AM ----------
funny i think i just foud the issue. someone posted saying older adbs cant see larger than 1gb (i have a opo so never even heard of this). ill give it a try and report back...
this is the adb ill be using https://forum.xda-developers.com/showthread.php?t=2317790

Okay, now that may work for others but I could not get it... Sorry
I ended up just removing the encryption, flashing twrp, and flashing OOS that way. Make sure to make a backup... I made a backup of everything... Except contacts because I thought gmail handled that like on my phone. I left my wife a note saying sorry for when she wakes up ha.
At least the annoying updates available message will be gone that we've had since Aug or something

I was getting the exact same errors and was frustrated to no end..... till I figured out how to fix it =)
I had to use this program on my adb.exe to make it large address aware
https://www.techpowerup.com/forums/threads/large-address-aware.112556/
Grab the laa_2_0_4.zip from the website, open and run as administrator
Click on select executable and go to where your adb.exe is installed, for me it was in C:\adb\adb.exe
Then make sure the checkbox on step 2 is selected and then hit save
I rebooted my PC and upon using the adb on reboot I was finally able to flash the stock OOS roms via adb sideload on my phone
Yipeee!!

shoemocker said:
I was getting the exact same errors and was frustrated to no end..... till I figured out how to fix it =)
I had to use this program on my adb.exe to make it large address aware
https://www.techpowerup.com/forums/threads/large-address-aware.112556/
Grab the laa_2_0_4.zip from the website, open and run as administrator
Click on select executable and go to where your adb.exe is installed, for me it was in C:\adb\adb.exe
Then make sure the checkbox on step 2 is selected and then hit save
I rebooted my PC and upon using the adb on reboot I was finally able to flash the stock OOS roms via adb sideload on my phone
Yipeee!!
Click to expand...
Click to collapse
I used the same tool

RR Won't Flash

Hi everyone. I am experiencing problems trying to flash RR Nougat to my Oneplus 3, currently on CM13 6.0.1. It just won't flash at all. I've wiped cache etc but it doesn't want to execute. I've also tried Lineage OS but failed, I have even tried pushing the file via Unified Android Toolkit and even that didn't work. Phone has an unlocked boot-loader (I'm pretty sure) USB debugging, root access etc. Unsure what the issue is so any help would be appreciated. This is what happened whilst using UAT.
Working out the best location to set for Internal Storage..
Waiting for Adb Mode
Device mode detected [device adb]
Pushing RR-N-v5.8.3-20170716-oneplus3-Weekly.zip to: /sdcard/
adb: error: cannot stat 'root\RR-N-v5.8.3-20170716-oneplus3-Weekly.zip': No such file or directory
File push did not work for sdcard
Setting push location to mnt/sdcard and trying again
Pushing RR-N-v5.8.3-20170716-oneplus3-Weekly.zip to: /mnt/sdcard/
adb: error: cannot stat 'root\RR-N-v5.8.3-20170716-oneplus3-Weekly.zip': No such file or directory
File push did not work for mnt/sdcard
Setting push location to storage/emulated/0 and trying again
Pushing RR-N-v5.8.3-20170716-oneplus3-Weekly.zip to: /storage/emulated/0/
adb: error: cannot stat 'root\RR-N-v5.8.3-20170716-oneplus3-Weekly.zip': No such file or directory
An Error Occured
The file did not push to the set location for some reason
Please report this in your device thread with details for more help
Press any key to return to the Main Menu..
Thank You.

I don't really have an answer for you but recently I tried to go back to stock, after I locked my bootloader I was unable to sideload anything with adb, have you tried flashing it with TWRP? Just a suggestion, are you able to use recovery at all, if uat can't find the directory, it could be a PC issue? I'm just throwing out ideas to try to help.

Update your adb drivers, now command prompt can push files larger then several mb's, don't know precisely how much.
Same problem I had couple of weeks back, don't know why but mine adb driver changed, set it back to the Google adb driver from sdk and the file was sideloaded.

Make sure you are on the latest firmware that is required.

I would just transfer through mtp or download on your op3, then just flash trough TWRP. That's what I do.

sv2203 said:
Update your adb drivers, now command prompt can push files larger then several mb's, don't know precisely how much.
Same problem I had couple of weeks back, don't know why but mine adb driver changed, set it back to the Google adb driver from sdk and the file was sideloaded.
Click to expand...
Click to collapse
Yup follow his method. This issue is somekind of adb sideload bug for huge files, name too long or not run as admin. Restarting PC, reinstall driver OP3 driver is another option if problem still persists.

Question Solved: Can not access fastboot device driver not found and I can not locate any either

So I have the drivers
usb_driver_r13-windows: from google they do not work and as far as I can see they are the latest
They are from 7/23/2020 but they are the latest Google provides.
I have installed OP9P_Default_Drivers, do not help at all either
I also downloaded: https://oneplusdriver.com/download-oneplus-driver, again no help in fastboot
Now they are in C:\Program Files (x86)\OnePlus USB Drivers
however trying to point here to use this driver fails "The hash for the file is not porsent ..." and it refuses to use this driver.
tool_amd64, can not install thr driver either as it also fails to install, the lost is clean:
Code:
OnePlus USB Drivers install...
Get system info ...
CPU architecture: AMD64
Operater System: Windows 8
Install drivers command:
tool_amd64.exe /PATH . /LM /SW
mtp & rndis drivers not need install.
set adb environment...
find ANDROID HOME = C:\Android
ANDROID HOME already exist!
adb path already exist in path!
check system environment...
system32 is not in USER path
system32 path already exist in path!
install drivers success!
I also tried: L2 drivers which should not and do not work.
Simply put I'm unable to locate any driver that supports "USB\VID_18D1&PID_D00D"
I'm un sure how anyone is doing anything in fastboot, if there is not a driver that supports this ID, but based on multiple Google searching I'm not locating any others that I'd even trust to try, or that would make any sense to try.
So at this point I'm completely blocked, from unlocking the phone (step 0 for me), as there is no driver that is supported for fastboot and the One Plus 9 Pro and Windows 10 20H2 with the latest patches from 05/2021, as something seems very wrong with the one plus driver.
Very unhappy right now with One Plus!
ERIC

Win 10 right...I had fastboot issues and found a thread eventually that walked me through booting win 10 in a way that gave me the option to disable security checks on driver's, and then I was able to install the OP driver I needed and voila fastboot could see my device.

sbcdave said:
Win 10 right...I had fastboot issues and found a thread eventually that walked me through booting win 10 in a way that gave me the option to disable security checks on driver's, and then I was able to install the OP driver I needed and voila fastboot could see my device.
Click to expand...
Click to collapse
That is not a safe thing to do, it is on One Plus to provide a valid signed driver, right now I'm using a Linux VM as fastboot and linux = however oneplus needs a valid WIndows 10 driver that is signed

egandt said:
So I have the drivers
usb_driver_r13-windows: from google they do not work and as far as I can see they are the latest
They are from 7/23/2020 but they are the latest Google provides.
I have installed OP9P_Default_Drivers, do not help at all either
I also downloaded: https://oneplusdriver.com/download-oneplus-driver, again no help in fastboot
Now they are in C:\Program Files (x86)\OnePlus USB Drivers
however trying to point here to use this driver fails "The hash for the file is not porsent ..." and it refuses to use this driver.
tool_amd64, can not install thr driver either as it also fails to install, the lost is clean:
Code:
OnePlus USB Drivers install...
Get system info ...
CPU architecture: AMD64
Operater System: Windows 8
Install drivers command:
tool_amd64.exe /PATH . /LM /SW
mtp & rndis drivers not need install.
set adb environment...
find ANDROID HOME = C:\Android
ANDROID HOME already exist!
adb path already exist in path!
check system environment...
system32 is not in USER path
system32 path already exist in path!
install drivers success!
I also tried: L2 drivers which should not and do not work.
Simply put I'm unable to locate any driver that supports "USB\VID_18D1&PID_D00D"
I'm un sure how anyone is doing anything in fastboot, if there is not a driver that supports this ID, but based on multiple Google searching I'm not locating any others that I'd even trust to try, or that would make any sense to try.
So at this point I'm completely blocked, from unlocking the phone (step 0 for me), as there is no driver that is supported for fastboot and the One Plus 9 Pro and Windows 10 20H2 with the latest patches from 05/2021, as something seems very wrong with the one plus driver.
Very unhappy right now with One Plus!
ERIC
Click to expand...
Click to collapse
Check your windows updates section, I was having the same issue. Was available through there for me, no problems after that.

egandt said:
That is not a safe thing to do, it is on One Plus to provide a valid signed driver, right now I'm using a Linux VM as fastboot and linux = however oneplus needs a valid WIndows 10 driver that is signed
Click to expand...
Click to collapse
I'm not sure this is valid. Would Windows 10 accept the driver if it was signed with LetsEncrypt certs... I doubt it.

Go to Windows Update -> Optional Updates.
You'll find the fastboot and adb drivers there.

If you're using a USB dock, try putting the USB cable directly into your PC instead, I've seen that fix problems where the phone isn't being seen

Reli4nth said:
Go to Windows Update -> Optional Updates.
Click to expand...
Click to collapse
worked so much easier than messing with external questionable drivers.

We have to disable the signature checks on windows. Run CMD as Administrator and paste the below codes and Hit Enter. Reboot your PC after doing this.
bcdedit.exe -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit.exe -set TESTSIGNING ON
Now try to install the one plus drivers again, and it should be done in 5 mins. After this windows will identify your device in fastboot mode.

Reli4nth said:
Go to Windows Update -> Optional Updates.
You'll find the fastboot and adb drivers there.
Click to expand...
Click to collapse
hey, where did you find the fastboot and adb drivers? When i enter "optional updates" in the search bar i can only see a very limited number of updates.
thx
EDIT: found out my problem was the missing driver. The Driver CD showed no files so i installed a driver from here: https://www.technobuzz.net/oneplus-6-usb-drivers/
Deavtivated the signature with the help of this
bcdedit.exe -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit.exe -set TESTSIGNING ON
Now i can find my phone in fastboot.
My only hope is that the installed driver was legit. Couldnt find an official version.. :S

Yikes....forgot there was a time I didn't know this.
Direct from Google (no "questionable about 'em, they are Google's own tools/drivers) -
ADB and Fastboot:
SDK Tools release notes | Android Studio | Android Developers
Learn about the Android SDK Tools component for the Android SDK.
developer.android.com
(Set PATH in Envorinment Variables to whatever folder you extract these to in order to have access to adb/fastboot in any folder using command-prompt.)
USB-Drivers (ADB fastboot):
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
(extract, right-click on android_winusb.inf file and select "install", go to Device Manager, right click "Android" device and update driver - choose "pick from list", Android, Bootloader - for fastboot/bootloader, obviously)
Download the SDK tools and update the ADB/Fasboot folder with every release of Android to try and keep it up to date. The USB drivers have worked for every device I have had to use them on.