Develop Bugs

How do I un-root without a computer?

How would I go about pulling the files from http://rapidshare.com/files/3899834....651.1_Radio_1.39.00.04.26_release_171253.exe and flash back to stock using just the phone, not using the computer at all?

Why do you not want to use a computer? and why go back to stock?

deekoi said:
Why do you not want to use a computer? and why go back to stock?
Click to expand...
Click to collapse
Doesn't matter he wants to do it.

Download the RUU zip from there and move it to the root of your sdcard (where u have all your other flashable zips) with a file manager and flash

bronxknight28 said:
Download the RUU zip from there and move it to the root of your sdcard (where u have all your other flashable zips) with a file manager and flash
Click to expand...
Click to collapse
grab the rom.zip file people have extracted from the RUU, put it on the root of your sdcard. rename it from rom.zip to PC36IMG.zip, reboot into the bootloader and it will analyze the PC36IMG.zip file and ask if you want to flash.
confirm yes and you'll be back to stock in no time!

joeykrim said:
grab the rom.zip file people have extracted from the RUU, put it on the root of your sdcard. rename it from rom.zip to PC36IMG.zip, reboot into the bootloader and it will analyze the PC36IMG.zip file and ask if you want to flash.
confirm yes and you'll be back to stock in no time!
Click to expand...
Click to collapse
exactly what this guy said, but to be more specific on how to do it, run the RUU executeable at the first screen minimize the application
do a "start>run" or a "<windows key> + r" and type in %temp% and hit ok, then search this folder for rom.zip and then rename it to PC36IMG.zip *care on if the .zip extension showing or not depending on your windows view settings* and copy it to the root directory of the sd card
restart the phone by power+vol down then it will search then ask you to flash, this whole part is extremely similar to steps in the flipz root method
like I said exactly what he said, just broken down like barney

johnsongrantr said:
exactly what this guy said, but to be more specific on how to do it, run the RUU executeable at the first screen minimize the application
do a "start>run" or a "<windows key> + r" and type in %temp% and hit ok, then search this folder for rom.zip and then rename it to PC36IMG.zip *care on if the .zip extension showing or not depending on your windows view settings* and copy it to the root directory of the sd card
restart the phone by power+vol down then it will search then ask you to flash, this whole part is extremely similar to steps in the flipz root method
like I said exactly what he said, just broken down like barney
Click to expand...
Click to collapse
i'll one up ya! forget extracting the rom.zip file yourself, techworkz did it for ya and ive mirrored it!
http://www.joeyconway.me/evo/stock/...Radio_1.39.00.05.31_release_171253_signed.zip
put it on the /sdcard and rename to PC36IMG.zip. reboot to bootloader and flash!

I believe there is a stock ruu you run from your desktop its an .exe file I habent used it but I downloaded it from one of these post

joeykrim said:
i'll one up ya! forget extracting the rom.zip file yourself, techworkz did it for ya and ive mirrored it!
http://www.joeyconway.me/evo/stock/...Radio_1.39.00.05.31_release_171253_signed.zip
put it on the /sdcard and rename to PC36IMG.zip. reboot to bootloader and flash!
Click to expand...
Click to collapse
guess I've been "one upped" I was taking more of a teach a man to fish aproach rather than the give a man a fish aproach... but whatever works

joeykrim said:
i'll one up ya! forget extracting the rom.zip file yourself, techworkz did it for ya and ive mirrored it!
http://www.joeyconway.me/evo/stock/...Radio_1.39.00.05.31_release_171253_signed.zip
put it on the /sdcard and rename to PC36IMG.zip. reboot to bootloader and flash!
Click to expand...
Click to collapse
If i neet to go back from SD using the ZIP extracted from the RUU can i root again?

mikevillarroel said:
If i neet to go back from SD using the ZIP extracted from the RUU can i root again?
Click to expand...
Click to collapse
Yeah, you should be able to re-root after un-rooting.

Sirchuk said:
Yeah, you should be able to re-root after un-rooting.
Click to expand...
Click to collapse
I ask because on the first post of How to root by toast it says at the end:
HOW TO RETURN BACK TO STOCK BUILD:
-Easy peasy- run the RUU in the first post of this thread. this is the only RUU that after flashing, you will still be able to root using this method. link below:
Click to expand...
Click to collapse
and there are different rom versions, I think this one has other Radio.
Any ways, i see this as a must have since you can go back to stock ROM on the go if you need it, for warranty/replace/exchange.

Here comes a stupid question. Where is the root on your sd card? Is it anywhere on the sd card or is it a certain directory?

johnsongrantr said:
exactly what this guy said, but to be more specific on how to do it, run the RUU executeable at the first screen minimize the application
do a "start>run" or a "<windows key> + r" and type in %temp% and hit ok, then search this folder for rom.zip and then rename it to PC36IMG.zip *care on if the .zip extension showing or not depending on your windows view settings* and copy it to the root directory of the sd card
restart the phone by power+vol down then it will search then ask you to flash, this whole part is extremely similar to steps in the flipz root method
like I said exactly what he said, just broken down like barney
Click to expand...
Click to collapse
deviouskater said:
I believe there is a stock ruu you run from your desktop its an .exe file I habent used it but I downloaded it from one of these post
Click to expand...
Click to collapse
These both require a computer which is not what was originally asked but good information non the less.

Ranger093 said:
Doesn't matter he wants to do it.
Click to expand...
Click to collapse
He is probably sitting in the Sprint parking lot wanting to exchange his phone and doesn't want to go back home to unroot.

joeykrim said:
i'll one up ya! forget extracting the rom.zip file yourself, techworkz did it for ya and ive mirrored it!
http://www.joeyconway.me/evo/stock/...Radio_1.39.00.05.31_release_171253_signed.zip
put it on the /sdcard and rename to PC36IMG.zip. reboot to bootloader and flash!
Click to expand...
Click to collapse
Did what you said rebooted into bootloader but it wouldn't let me flash. What gives I have to unroot to get a new one. Thanks

Use the latest ZIP here:
http://goo-inside.me/evo/stock/RUU/
Move the ZIP from /sdcard/download to /sdcard and rename it to PC36IMG.zip. Check the MD5, then reboot into hboot.

I extracted the root then it top me its a older version can't do it

Sorry but what is MD5, and once downloaded do I have to extract it then flash?

Do not extract.
Do not flash.
Just do what I said to do.
Also, learn to search. https://secure.wikimedia.org/wikipedia/en/wiki/MD5

[REF][GUIDE]CWM md5 mismatch problem solved

So, many of you probably faced the issue, when you tried to restore your CWM backup, that the recovery says MD5 mistmach, and will do nothing. The problem is now solved, and was solved, so I'm not the one, who made thing possible, I'm just porting this to the V.
So, the problem (in my iterations at least) are based on the /cache/ cannot be mounted error, which is common in the V. For why is that, I simply don't have a clue, but it is present. Because of this, the backup won't be full, and thus, the md5 image won't be made for the recovery, so cannot be recovered as is.
But happily you can make an md5 image from the backup yourself, and thus recover your backup.
WARNING!​
I'm no dev, just someone, that knows linux.
If you follow this path, you do it on your own. I'm not responsible for bricked devices, lost data or whatsoever, including the future the past and the present.​
Click to expand...
Click to collapse
There are three ways for you, to make an md5 sum of the img files, the good and the bad one and also the quoted one:
One (the good)
For this, you will need adb, root, and a working android. Yo don't have it? Here you go.
Go to the directory, were you have adb (or have extracted adb.exe, suggested c:\htc\), then plug in your phone (just for charge, no data connection), open terminal (syntax: cmd) then type in:
adb shell
this will get you to the phone's terminal
if you have # at the end of the line, you are good to go, if not, then type su
The syntaxes needed:
cd /sdcard/clockworkmod/backup/{recovery_timestamped_directory} <- this is from your backup, so you need to fill in appropirate data
md5sum *img > nandroid.md5
Click to expand...
Click to collapse
This will make an md5 image with the name that cwm acknowledges.
Two (the bad one)
So, you'we fired your ROM, cannot even boot, but cwm comes in. Than this is for you. There are programs (e.g. total commander) which can make md5 images. So if you have your backup folder, just go into it (sd card reader is preferred). You will see something like this in it:
.android_secure.vfat.tar
boot.img
data.ext4.tar
{nandroid.md5}
recovery.img
system.ext4.tar
Click to expand...
Click to collapse
sidenote:
If you have the nandroid.md5 and you cannot recover, don't try to recover from it!!!
The image itself is corrup, you have no luck, try RUU. (you can recover if you delete the md5 and create a new, but it is not really recommended)
1.
So, there are 2 .img files, highlight them in totalcommander. go to file->create checksum files
2.
tick in md5, then ok
3.
No, you're not done
open the md5 file in text editor, and remove the * 's from before the file names.
4.
Rename the file to nandroid.md5
5.
Now you're done, go to cwm, then recover.
Three (the quoted one)
Also on the 2nd page you will find an alternative solution for the problem which can help you if you have got busybox installed on your device.
The solution resembles the One type of fix, so with quotes here's the one (thanx for Meeshka for it).
Meeshka said:
For those who keep getting "md5sum not found" both in adb and in android terminql on device:
try instead
# busybox md5sum *img > nandroid.md5
worked for me
Click to expand...
Click to collapse
If I helped, don't hesitate to push the Thanks button.

Thanks... a very useful guide. Bookmarked

WORKED!!! Tho I'm from a different device the first (adb) method saved my AOKP backup!!! Daysaver I'd say!!

I keep getting "md5sum: not found"

Put this in the general android section as it works across most devices. ..
Sent from my One V

Nevell said:
I keep getting "md5sum: not found"
Click to expand...
Click to collapse
if you send me the 2 img files i can create an appropirate md5 image of them, but send the one you did, so I can guess what the problem is.
send them to the email of my usr here, or in pm. and mainly, the md5 image has the name "nandroid.md5" like small caption all the way, even the md5? If it is there where it must, it must work, ad absurd it will be "wrong checksum error", but that is another version.
General android section has this, I have learned this from there, but it had only 1st option, and was "discovered" when cwm had generated wrong md5s, the V, in the V the problem is a tad bit different, but the solution is the same.

I fixed it in adb
Sent from my SPH-L710 using xda premium

Nevell said:
I fixed it in adb
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Can you explain what did you do to fix md5sum: not found error??
please i need it!

thatsgamer said:
Can you explain what did you do to fix md5sum: not found error??
please i need it!
Click to expand...
Click to collapse
Just created an md5sum manualy from the img files with the name of nandroid.md5, because on the V the recovery doesn't creates them because of cache mount problem.
The recovery process will end in an error message, because cache cannot be recovered, but the main thing will be recovered this way.

i have one x and i can't put sdcard in to card reader because one x dose not have sd card... and i cant fix it whit first solution because i cant acces my phone

haky1988 said:
i have one x and i can't put sdcard in to card reader because one x dose not have sd card... and i cant fix it whit first solution because i cant acces my phone
Click to expand...
Click to collapse
See : http://forum.xda-developers.com/showpost.php?p=32248108&postcount=7

unfortunately none of the methods described in the first post have worked for me, at the first one i got an "unable to write, source is read-only" error, and the second one failed from the first try
after almost giving up and beginning to deal with the idea of loosing my backups, i found this topic and in 10 secs it got the job done, now i'm back on my latest cwm backup

CWM showing different versions
-Delete-

maranello69 said:
unfortunately none of the methods described in the first post have worked for me, at the first one i got an "unable to write, source is read-only" error, and the second one failed from the first try
after almost giving up and beginning to deal with the idea of loosing my backups, i found this topic and in 10 secs it got the job done, now i'm back on my latest cwm backup
Click to expand...
Click to collapse
You do know that the first method is exactly like the one you linked right?
Aside that, I'm happy that the community could help you out

Loir can u help me. I can't locate the boot.img inside the downloads for cyanogen mod u provided. Forgive me but can you post a directory to this kernel file? Tks
Sent from my HTC Desire X using xda app-developers app

Thank you so much. You saved my phone.

For those who keep getting "md5sum not found" both in adb and in android terminql on device:
try instead
# busybox md5sum *img > nandroid.md5
worked for me

no * 's
Ken-Shi_Kun said:
So, many of you probably faced the issue, when you tried to restore your CWM backup, that the recovery says MD5 mistmach, and will do nothing. The problem is now solved, and was solved, so I'm not the one, who made thing possible, I'm just porting this to the V.
So, the problem (in my iterations at least) are based on the /cache/ cannot be mounted error, which is common in the V. For why is that, I simply don't have a clue, but it is present. Because of this, the backup won't be full, and thus, the md5 image won't be made for the recovery, so cannot be recovered as is.
But happily you can make an md5 image from the backup yourself, and thus recover your backup.
​
There are two ways for you, to make an md5 sum of the img files, the good and the bad one:
One (the good)
For this, you will need adb, root, and a working android. Yo don't have it? Here you go.
Go to the directory, were you have adb (or have extracted adb.exe, suggested c:\htc\), then plug in your phone (just for charge, no data connection), open terminal (syntax: cmd) then type in:
adb shell
this will get you to the phone's terminal
if you have # at the end of the line, you are good to go, if not, then type su
The syntaxes needed:
This will make an md5 image with the name that cwm acknowledges.
Two (the bad one)
So, you'we fired your ROM, cannot even boot, but cwm comes in. Than this is for you. There are programs (e.g. total commander) which can make md5 images. So if you have your backup folder, just go into it (sd card reader is preferred). You will see something like this in it:
sidenote:
If you have the nandroid.md5 and you cannot recover, don't try to recover from it!!!
The image itself is corrup, you have no luck, try RUU. (you can recover if you delete the md5 and create a new, but it is not really recommended)
1.
So, there are 2 .img files, highlight them in totalcommander. go to file->create checksum files
2.
tick in md5, then ok
3.
No, you're not done
open the md5 file in text editor, and remove the * 's from before the file names.
4.
Rename the file to nandroid.md5
5.
Now you're done, go to cwm, then recover.
If I helped, don't hesitate to push the Thanks button.
Click to expand...
Click to collapse
in 3. it says to remove the * *'s, but i don't see any, so i was wondering should i leave that be or if im doing something wrong.

Beastben13 said:
in 3. it says to remove the * *'s, but i don't see any, so i was wondering should i leave that be or if im doing something wrong.
Click to expand...
Click to collapse
I have done the thing with a legacy tcmd, so there is a probability, that they have modified the md5sum algorithm, so if you don't se the stars don't panic. (also it should do the trick even with stars in the file, but wanted to be sure at the time I wrote the post)

plz provide touch recovery for karbon a9+ plz and ther is bugs in cwm recovery 5.0.2.8 plz

[TUTORIAL] Install ROM via sideload

I know most of you already know this, but it may help others because this is very usefull for installing kitkat.
It's a pain to copy an 1,2 GB ROM to internal storage, so sideloading (installing from PC) it's lot easier and faster.
So here's the trick.
Copy the zip you want to install in "adb" folder (archiev attached)
Reboot phone in recovery mode
Optional - do your wipes
If you have CMW
Go to install zip -> install zip from sideload
If you have TWRP
Go to advanced -> ADB sideload
connect the USB cable and run START.cmd
type "adb devices" to check if your phone is recognized and connected (skip if you know everything it's ok)
type "adb sideload kitkat.zip" (replace kitkat with zip's name)
Notes:
Ofc you need USB drivers

Ive tried that a couple times but always i get a "cannot read kitkat.zip" thing, any idea why?
Sent from my LG-E975 using XDA Premium 4 mobile app

mastor10 said:
Ive tried that a couple times but always i get a "cannot read kitkat.zip" thing, any idea why?
Click to expand...
Click to collapse
Umm... Did you replace "kitkat.zip" with the actual name of your zip file (or rename your zip to "kitkat.zip")? I know it might be a very stupid question, but I can only read your post, not your mind...

kt-Froggy said:
Umm... Did you replace "kitkat.zip" with the actual name of your zip file (or rename your zip to "kitkat.zip")? I know it might be a very stupid question, but I can only read your post, not your mind...
Click to expand...
Click to collapse
Of course man, all of the roms ive flashed was through sideload

mastor10 said:
Of course man, all of the roms ive flashed was through sideload
Click to expand...
Click to collapse
Make a screenshot of what you're doing and error you get, this way will be easier for both.

roscatel said:
Make a screenshot of what you're doing and error you get, this way will be easier for both.
Click to expand...
Click to collapse
there you go
i changed the name to zip but norhing happens

mastor10 said:
there you go
i changed the name to zip but norhing happens
Click to expand...
Click to collapse
First, there is no way for a rom to use ".rar" extension. After, error means that the file couldn't be read (missing or corrupted). Also you may try my method which doesn't need android SDK, so there is no complications with wrong paths or such.

roscatel said:
First, there is no way for a rom to use ".rar" extension. After, error means that the file couldn't be read (missing or corrupted). Also you may try my method which doesn't need android SDK, so there is no complications with wrong paths or such.
Click to expand...
Click to collapse
yes i know, but in there the rom is in rar http://forum.xda-developers.com/showthread.php?t=2762171
so i changed the rar to zip, also i downloaded the file 3 times and the same happens, ill try with your adb and see
also the others zips i flash through sideload from sdk works just fine, only in this rom i get the error
edit, nope the same happens

mastor10 said:
yes i know, but in there the rom is in rar http://forum.xda-developers.com/showthread.php?t=2762171
so i changed the rar to zip, also i downloaded the file 3 times and the same happens, ill try with your adb and see
also the others zips i flash through sideload from sdk works just fine, only in this rom i get the error
edit, nope the same happens
Click to expand...
Click to collapse
Look at the screen I've attached. Are you sure your zip it's not the same have you checked it? I've highlighted the rom itself.

roscatel said:
Look at the screen I've attached. Are you sure your zip it's not the same have you checked it? I've highlighted the rom itself.
Click to expand...
Click to collapse
this is what i download
https://drive.google.com/uc?id=0BxtwB2oE42pDNFJsaGJ3ODNkWGM&export=download
from the topic i mention above, its the same, i rename it to a smaller name though

mastor10 said:
this is what i download
https://drive.google.com/uc?id=0BxtwB2oE42pDNFJsaGJ3ODNkWGM&export=download
from the topic i mention above, its the same, i rename it to a smaller name though
Click to expand...
Click to collapse
Ok then simply extract "VDT-V20..." from that archieve. That's the zip you have to install via sideload!

roscatel said:
Ok then simply extract "VDT-V20..." from that archieve. That's the zip you have to install via sideload!
Click to expand...
Click to collapse
this is whats inside the zip i download

mastor10 said:
this is whats inside the zip i download
Click to expand...
Click to collapse
It looks to me that your screenshot is showing contents of a ZIP inside a RAR. What @roscatel means, you should extract the ZIP from the RAR that you downloaded -- it's actually an archive packed inside another archive. After that, flash the ZIP you just extracted using any method (sideload, or from recovery as usual). Do NOT rename RAR to ZIP -- it doesn't make sense, and will most definitely NOT work.

kt-Froggy said:
It looks to me that your screenshot is showing contents of a ZIP inside a RAR. What @roscatel means, you should extract the ZIP from the RAR that you downloaded -- it's actually an archive packed inside another archive. After that, flash the ZIP you just extracted using any method (sideload, or from recovery as usual). Do NOT rename RAR to ZIP -- it doesn't make sense, and will most definitely NOT work.
Click to expand...
Click to collapse
hi my pc known my device but when i write adb sideload ...zip foul (stand) 0% and i watting 15 minuts for process but nothing happening . plz help me . my device is xperia tx.. plzzzzzzzzzzzzz

install the last TWRP (flash it via bootloader), same process by opening commande window in the folder (shift+right click: then open command) and tiping command: fastboot flash recovery (name of the file).img (like that: exemple: fastboot flash recovery lastTWRP.img)
it autorize MTP transfer, so you cas access your internal storage and copy the zip file
or retrieve backups from your phone

I'm using and side load on my lge
LM-x210MA an I keep getting these different errors do I need to flash more than a twrp.imf what about sys.img root.img root-boot.img this is all a lot to take in as a first timer go easy I'm not trolling just trying to learn

--[FIX]--SkyDragon G3 USB Fix

Like many of you new flashers, I have flashed the SkyDragon ROM and have noticed that there is no connectivity to the computer whatsoever, so I did a little digging. I went back and forth between 2 Nandroid backups and kept flashing parts of them until I could narrow down where this problem was coming from. I found out that it comes from the specific folder - data/property
There is a missing file called persist.sys.usb.config ,13B in size, and I have no idea what it does (maybe some of you could enlighten me) but throwing the old file into that folder, changing the permissions to rw-------- and rebooting worked like a charm.
I apologize for not sticking this into the development thread, however I'm a lurker with no input! :victory:
Without further ado,
I TAKE NO RESPONSIBILITY FOR ANY BORKEN DEVICES. IF YOU DON'T KNOW WHAT YOU'RE DOING, DON'T DO IT!
1. Download Root Browser and RB Text Editor
2. Navigate to /data/property
3. On the bottom bar, tap the "New" button
4. Click on "New file"
5. Enter the file name as follows:
persist.sys.usb.config
6. Click the file you just made and hit "Open as..."
7. Hit "Text file"
8. Click RB Text editor
9. Delete whatever is there and enter as follows:
auto_conf,adb
No spaces or caps!
10. Save the file by clicking the save button on the top right corner.
11. Reboot your phone
12.Profit
----------------------------------------------------------------------------------------------------------------------------------------
Steal this information, spread it around, someone post it to the development thread and make this ROM better!
If you're having any problems, don't hesitate to ask

i could just drop this in the proper location before flashing the rom yes ??

CheesyNutz said:
i could just drop this in the proper location before flashing the rom yes ??
Click to expand...
Click to collapse
Only if you're going to dirty flash it, but at that point, I'd just dirty flash it anyways. The file should already be there if you're on a ROM that can recognize your phone. I also do recommend a clean flash. I'm sorry if I made this difficult. When flashing the rom, it'll format /data which is where the file is held so if you had the file there already, it would just wipe it.

88keys6strings said:
Only if you're going to dirty flash it, but at that point, I'd just dirty flash it anyways. The file should already be there if you're on a ROM that can recognize your phone. I also do recommend a clean flash. I'm sorry if I made this difficult. When flashing the rom, it'll format /data which is where the file is held so if you had the file there already, it would just wipe it.
Click to expand...
Click to collapse
i was talking from a clean install
drop file in the proper location then wipe phone flash rom with new file and them proceed to set up the phone

CheesyNutz said:
i was talking from a clean install
drop file in the proper location then wipe phone flash rom with new file and them proceed to set up the phone
Click to expand...
Click to collapse
As long as it's after the wipe then yes. If you opened up the zip that contains the ROM, you could head into /data then create a new folder called property and throw the file in there then zip it back up and flash it. But you MUST put the file in /data/property AFTER you flash the ROM. You could drop the file into a downloads or media folder because those don't get touched then flash the rom then move it and change permissions then reboot as well.
So no, you cannot drop the file in it's PROPER location before you wipe, otherwise it'll get deleted. However, you can copy/paste it into say, mnt/sdcard/Download, via your root browser, beforehand then follow my instructions

I'll try when I get home in about six hours.

partylikeaninjastar said:
I'll try when I get home in about six hours.
Click to expand...
Click to collapse
For sure! Will await results

I hope the developers get to see this for the next update

I tried creating my own file as per the instructions (came to 13b size for the file too), but my phone isn't being recognized in android file transfer.
Then again, it wasn't recognized either when I was on stock rom (prior to flashing anything).

On my phone, the file already existed. Its contents read....
Code:
boot,adb,mtp
I changed it accordingly based on your instructions, reboot and nothing.
I found that if you turn USB debugging off, then on again, the file will get overwritten with the original code...boot,adb,mtp.
Could it be that this command simply enables USB debugging? That's what my testing showed. I turned off debugging, made the file change, reboot and debugging was enabled. Disable debugging and the file gets overwritten. Rinse, repeat. If I delete the file, it is recreated when enabling USB debugging....boot,adb,mtp.
Just a preliminary finding. I'm not well versed enough to explain or troubleshoot it any further. It did nothing to cure my USB problem.

Cablespider said:
On my phone, the file already existed. Its contents read....
Code:
boot,adb,mtp
I changed it accordingly based on your instructions, reboot and nothing.
I found that if you turn USB debugging off, then on again, the file will get overwritten with the original code...boot,adb,mtp.
Could it be that this command simply enables USB debugging? That's what my testing showed. I turned off debugging, made the file change, reboot and debugging was enabled. Disable debugging and the file gets overwritten. Rinse, repeat.
Just a preliminary finding. I'm not well versed enough to explain it further. It did nothing to cure my USB problem.
Click to expand...
Click to collapse
I may have overlooked something. I deleted some usb portion of the build.prop. Didn't change anything so i didnt think about it. If you make a backup then edit it deleting the usb part, then reboot that might get it to work.If you need specifics, I'll be next to a computer in about an hour and a half

Can someone just post the file here?
Sent from my LG-D851
---------- Post added at 10:44 PM ---------- Previous post was at 10:36 PM ----------
I copied one of the persist.sys files from that folder to my sdcard and edited it with Rom Toolbox Pro. I opened it as a text file and deleted what was there, then added the stuff in the OP and saved. I then renamed the file to persist.sys.usb.config and added it to that folder and changed permissions and rebooted. Worked fine.
Sent from my LG-D851

Skizzy034 said:
Can someone just post the file here?
Sent from my LG-D851
---------- Post added at 10:44 PM ---------- Previous post was at 10:36 PM ----------
I copied one of the persist.sys files from that folder to my sdcard and edited it with Rom Toolbox Pro. I opened it as a text file and deleted what was there, then added the stuff in the OP and saved. I then renamed the file to persist.sys.usb.config and added it to that folder and changed permissions and rebooted. Worked fine.
Sent from my LG-D851
Click to expand...
Click to collapse
Awesome! Glad it worked for you

This is from my stock rom with the modified skydragon kernel. place in root\data\property. let me know if this works. just rename it and drop the .zip part.

Cablespider said:
On my phone, the file already existed. Its contents read....
Code:
boot,adb,mtp
I changed it accordingly based on your instructions, reboot and nothing.
I found that if you turn USB debugging off, then on again, the file will get overwritten with the original code...boot,adb,mtp.
Could it be that this command simply enables USB debugging? That's what my testing showed. I turned off debugging, made the file change, reboot and debugging was enabled. Disable debugging and the file gets overwritten. Rinse, repeat. If I delete the file, it is recreated when enabling USB debugging....boot,adb,mtp.
Just a preliminary finding. I'm not well versed enough to explain or troubleshoot it any further. It did nothing to cure my USB problem.
Click to expand...
Click to collapse
Jephre said:
I tried creating my own file as per the instructions (came to 13b size for the file too), but my phone isn't being recognized in android file transfer.
Then again, it wasn't recognized either when I was on stock rom (prior to flashing anything).
Click to expand...
Click to collapse
partylikeaninjastar said:
I'll try when I get home in about six hours.
Click to expand...
Click to collapse
CheesyNutz said:
i was talking from a clean install
drop file in the proper location then wipe phone flash rom with new file and them proceed to set up the phone
Click to expand...
Click to collapse
UPDATED
Much easier now. Just tested it with a Nand that didn't work at all and followed the instructions and it worked flawlessly. Let me know if you have any more issues

aclegg2011 said:
This is from my stock rom with the modified skydragon kernel. place in root\data\property. let me know if this works. just rename it and drop the .zip part.
Click to expand...
Click to collapse
It should work just fine as long as you didn't actually compress it lol. Thank you for the upload!
ALSO
THIS IS MY 10TH POST!!! DEV SECTION HERE I COME!! :victory:

88keys6strings said:
1. Download Root Browser and RB Text Editor
2. Navigate to /data/property
3. On the bottom bar, tap the "New" button
4. Click on "New file"
5. Enter the file name as follows:
persist.sys.usb.config
6. Click the file you just made and hit "Open as..."
7. Hit "Text file"
8. Click RB Text editor
9. Delete whatever is there and enter as follows:
auto_conf,adb
No spaces or caps!
10. Save the file by clicking the save button on the top right corner.
11. Reboot your phone
12.Profit
Click to expand...
Click to collapse
I can now confirm that this does work. I now have working MTP again.

You guys could try adding "persist.sys.usb.config=mtp,adb" to the build.prop and see if that works.

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