File Transfer with no os - OnePlus 5 Questions & Answers

Hello guys here's the story: I wanted to flash an old nandroid backup with twrp and it keep failing to flash the /system cause "needed a clean install". So i thought to wype the system and retry, still the same error, then i was sick to try and wanted to go back my newest backup, still the same error. Then i wanted to reinstall the 5.1.1 from scratch and make a format data. So now i'm on twrp with no os and nothing at all in the phone. When i plugged the phone to pc now i can't see it in "my computer", still adb recognize the device so i tryed a sideload to transfer the 5.1.1 but it fail the transfer with an error 7. I made a mess and finished the option...what can i do?

Try side loading any other version through Adb. It will work for sure.

You say when you plug phone into computer, it does not show up in my computer?
In TWRP, look under "mount" and make sure "enable mtp" is checked.

foomanjackel said:
You say when you plug phone into computer, it does not show up in my computer?
In TWRP, look under "mount" and make sure "enable mtp" is checked.
Click to expand...
Click to collapse
thank you for the advise, you was right, it was unchecked, not when enable it does appear in mycomputer, i can open it but i can drag or past anytthing, not even create a new folder...i'm still stuck

You can copy files to your phone using "adb push" command.

Related

Not recognized in recovery

Hello.
I was attempting to install a new KitKat ROM. The installation failed, and now the phone only sits at the Samsung boot logo. Since I downloaded the ROM using my phone, I figured the download was corrupt.
I put my phone into recovery to sideload a new ROM .zip downloaded from my pc.
Computer gives me a USB error sound
In device manager on windows, the phone displays as "SAMSUNG_Android" with an exclamation point.
I have correct drivers installed, computer recognizes when its not in recovery mode.
So if anyone could explain why it isn't being recognized it would be of great help!
Also, if I tried to mount the device as USB from recovery I get this
"E: Unable to mount '/usb-otg' "
I assumed that had something to do with it not being recognized.
I Googled this for about an hour and a half now... few people are having this with even fewer people responding to help. I may just be awful at searching though...
I assume you have a custom recovery? If so, boot into recovery and restore a nandroid
jd1639 said:
I assume you have a custom recovery? If so, boot into recovery and restore a nandroid
Click to expand...
Click to collapse
Yeah I forgot to make one... And formatted previous ones a while back...
INSM Sin said:
Yeah I forgot to make one... And formatted previous ones a while back...
Click to expand...
Click to collapse
Well, lesson learned, always have a nandroid. If you have kies, uninstall it then reinstall your usb drivers. You know you have to push a rom onto the device, now you need to figure out how to get the device recognized on your pc.
jd1639 said:
Well, lesson learned, always have a nandroid. If you have kies, uninstall it then reinstall your usb drivers. You know you have to push a rom onto the device, now you need to figure out how to get the device recognized on your pc.
Click to expand...
Click to collapse
Deleting Kies as we speak. I did manage to get windows to recognize it while its in recovery. Now, after attempting adb sideload "filename" I get
"failed to write data 'protocol fault <no status>'" in command prompt.
And yes... lesson learned.

Stuck on TWRP without a system to boot to.

Hi, I wanted to return my g2 to stock rom because I didn't like my custom rom, so I followed the lg flash tool guide(tot):http://forum.xda-developers.com/showthread.php?t=2432476
It worked, but it was jelly bean 4.2 instead of Kit kat 4.4, so I tried to install TWRP so that I can install again a custom rom, but when I tried to backup before flashing TWRP, it wrote "backup Failed", I tried again and it wrote it again, but then the phone just stayed on the boot animation for a few seconds and didnt turn on again. After that, again I tried to do the flash tool method just to return to stock rom but now, it just doesn't work, whenever I insert the DLL and TOT file and start the installation, it goes up to 80% extremely quick and just boots up to TWRP without actually installing the stock rom. So now I'm stuck here with TWRP but without a system to boot to and no rom on my sd card to flash.
I really need help here because I have no idea how to continue.
Thanks for any help!
PriStol said:
Hi, I wanted to return my g2 to stock rom because I didn't like my custom rom, so I followed the lg flash tool guide(tot):http://forum.xda-developers.com/showthread.php?t=2432476
It worked, but it was jelly bean 4.2 instead of Kit kat 4.4, so I tried to install TWRP so that I can install again a custom rom, but when I tried to backup before flashing TWRP, it wrote "backup Failed", I tried again and it wrote it again, but then the phone just stayed on the boot animation for a few seconds and didnt turn on again. After that, again I tried to do the flash tool method just to return to stock rom but now, it just doesn't work, whenever I insert the DLL and TOT file and start the installation, it goes up to 80% extremely quick and just boots up to TWRP without actually installing the stock rom. So now I'm stuck here with TWRP but without a system to boot to and no rom on my sd card to flash.
I really need help here because I have no idea how to continue.
Thanks for any help!
Click to expand...
Click to collapse
You could load the zip you want to flash to a USB drive, then connect it to your phone with an OTG cable. TWRP can read from OTG.
Can you get into download mode? (phone off, hold up volume, insert USB cable connected to computer)
thecadman99 said:
You could load the zip you want to flash to a USB drive, then connect it to your phone with an OTG cable. TWRP can read from OTG.
Can you get into download mode? (phone off, hold up volume, insert USB cable connected to computer)
Click to expand...
Click to collapse
I just tried to do it through an OTG cable, it said that it flashed successfuly, but when I restarted it just went back to TWRP without booting up the system. Also, when I tried to wipe dalvik and cache, it said "wipe failed.". When I rebooted it said "It seems that the device is not rooted"... I really don't know what to do now And I can get to download mode.
PriStol said:
I just tried to do it through an OTG cable, it said that it flashed successfuly, but when I restarted it just went back to TWRP without booting up the system. Also, when I tried to wipe dalvik and cache, it said "wipe failed.". When I rebooted it said "It seems that the device is not rooted"... I really don't know what to do now And I can get to download mode.
Click to expand...
Click to collapse
Can you get ADB connectivity from within TWRP if you connect your device to the PC?
If so you could do the following command from your computer.
Code:
adb push ROM.zip /sdcard/Download/
Then navigate to your /sdcard/Download folder and flash the ROM.
d00lz said:
Can you get ADB connectivity from within TWRP if you connect your device to the PC?
If so you could do the following command from your computer.
Code:
adb push ROM.zip /sdcard/Download/
Then navigate to your /sdcard/Download folder and flash the ROM.
Click to expand...
Click to collapse
When I try to do ADB sideload on TWRP, it just loads forever and doesn't do anything... So I cant get ADB connectivity.
PriStol said:
When I try to do ADB sideload on TWRP, it just loads forever and doesn't do anything... So I cant get ADB connectivity.
Click to expand...
Click to collapse
TWRP should detect your phone without the need for ADB sideload.
If I boot into TWRP, I can instantly run "adb devices" from the terminal my phone is picked up as a "device".
If I choose ADB Sideload, my TWRP hangs just like yours does, but if I run another "adb devices" command my device shows up in sideload mode, regardless of it hanging.
Conclusion, try running the adb commands without running sideload in the first place.
Edit: Upon reflection, this is most likely because I have created an RSA key between the PC and my phone.
d00lz said:
TWRP should detect your phone without the need for ADB sideload.
If I boot into TWRP, I can instantly run "adb devices" from the terminal my phone is picked up as a "device".
If I choose ADB Sideload, my TWRP hangs just like yours does, but if I run another "adb devices" command my device shows up in sideload mode, regardless of it hanging.
Conclusion, try running the adb commands without running sideload in the first place.
Click to expand...
Click to collapse
It just says error: device not found whenever I do a command.
Please help, I really dont know what to do.
PriStol said:
I just tried to do it through an OTG cable, it said that it flashed successfuly, but when I restarted it just went back to TWRP without booting up the system. Also, when I tried to wipe dalvik and cache, it said "wipe failed.". When I rebooted it said "It seems that the device is not rooted"... I really don't know what to do now And I can get to download mode.
Click to expand...
Click to collapse
Did you wiped absolutely everything before flashing? Do you have previous Nandroid backup you can just flash. Anyway if you connect your phone to PC while in TWRP what does your PC show. Anything?
yanis15 said:
Did you wiped absolutely everything before flashing? Do you have previous Nandroid backup you can just flash. Anyway if you connect your phone to PC while in TWRP what does your PC show. Anything?
Click to expand...
Click to collapse
I tried to wipe but it just wrote "wipe failed". I do have a back up on my computer but for some reason when I try to connect my phone to my computer through an OTG cable, it doesn't find the backup. And my pc doesn't show anything when I connect my phone.

system deleted, TWRP ready

Hello,
i delete the System and Data on my LeEco Le Pro3.
TWRP is installed.
Can i flash a rom with an usb flash drive in TWRP or fastboot?
greeting gizez
Boot into TWRP and use MTP to transfer ROM file from your PC to Phone. Then flash the ROM.
I have this problem, but I can't see the phone when connected to a PC. adb sideload doesn't work (adb devices doesn't find anything). Do I need to install driver for the phone? I originally used fastboot to unlock the bootloader and flashed TWRP, then installed LineageOS and gapps just fine. I then proceeded to wipe system in TWRP (I was trying to get back to new phone setup so I can transfer stuff from old phone, which I skipped the first time).
Any idea how to get around this? I tried plugging in pen drive through an micro USB OTG and a usb-c to micro usb adapter, but it's not recognized in TWRP, either. Would very much appreciate any help!
You can get your data. First try to connect phone while is in TWRP. Your phone can be detected as file manager. Try this.
If not, check my theme;
https://forum.xda-developers.com/le-pro3/help/brick-t3609704
marik1 said:
[...]
Go Advanced -> ADB Sideload, type "adb sideload aicp_zl1_n-12.1-NIGHTLY-20170516.zip" (zip of OS should be downloaded and put into "Minimal ADB and Fastboot" installation folder with name as same as the text of command). It should let you turn on system.
[...]
Click to expand...
Click to collapse
Also "adb push" command can be helpful. Sometimes phone is not current on adb devices list, but you can also try. As i remember, target should be /sdcard/0
marik1 said:
You can get your data. First try to connect phone while is in TWRP. Your phone can be detected as file manager. Try this.
If not, check my theme;
https://forum.xda-developers.com/le-pro3/help/brick-t3609704
Also "adb push" command can be helpful. Sometimes phone is not current on adb devices list, but you can also try. As i remember, target should be /sdcard/0
Click to expand...
Click to collapse
Thanks, but unfortunately no luck. Both adb sideload and adb push said error - device '(null)' not found. It seems like the PC is not recognizing the phone. I checked device manager on the PC, it showed LEX727. I right-click and had it install the driver. It says driver successfully installed. Then device manager showed MTP device with a !. I again tried having driver installed, but this time it doesn't find any driver.
I'm at my wit's end... Any more suggestion?
TWRP and/or Minimal ADB isn't trouble here? Tried you both on main menu of TWRP and in ADB Sideload mode? You can also try do it trough bootloader, for this check my link and read all.
marik1 said:
TWRP and/or Minimal ADB isn't trouble here? Tried you both on main menu of TWRP and in ADB Sideload mode? You can also try do it trough bootloader, for this check my link and read all.
Click to expand...
Click to collapse
Actually, the problem is solved, by using another PC. This one showed LEX727 in windows explorer as soon as i plug in the phonr (in twrp). I was able to drag and drop the zip files to the phone and go on my merry way. Now back in business!

TWRP, No OS, ADB sideload not working: what to do?

Hey all,
I have a OnePlus 2, which had Resurrection Rom (and TWRP 3.0.2-2). However, I wanted to factory reset that ROM. Problem is: I wiped too much data.
I now have no more OS (TWRP -> Reboot -> Reboot System gives a message "No OS installed!").
I do have TWRP 3.0.2-2 and can boot to it.
I have no img of an OS on the device (as far as I know, since I wiped basically everything).
If I go to TWRP -> Advanced -> ADB Sideload, it will go "Starting ADB sideload feature...", hang there for a few minutes and then give a red FAILED on the top of the screen.
I have the phone connected with USB to my pc (Ubuntu 16.10), but I can't find it with lsusb and I can't seem to transfer files that way either.
So my question is: how do I get any ROM back on there? Stock OxygenOS without a custom recovery or whatever would be fine, as long as I can boot to an OS again.
Any help is greatly appreciated, thanks in advance!
Greetings,
Rien
rienheuver said:
Hey all,
I have a OnePlus 2, which had Resurrection Rom (and TWRP 3.0.2-2). However, I wanted to factory reset that ROM. Problem is: I wiped too much data.
I now have no more OS (TWRP -> Reboot -> Reboot System gives a message "No OS installed!").
I do have TWRP 3.0.2-2 and can boot to it.
I have no img of an OS on the device (as far as I know, since I wiped basically everything).
If I go to TWRP -> Advanced -> ADB Sideload, it will go "Starting ADB sideload feature...", hang there for a few minutes and then give a red FAILED on the top of the screen.
I have the phone connected with USB to my pc (Ubuntu 16.10), but I can't find it with lsusb and I can't seem to transfer files that way either.
So my question is: how do I get any ROM back on there? Stock OxygenOS without a custom recovery or whatever would be fine, as long as I can boot to an OS again.
Any help is greatly appreciated, thanks in advance!
Greetings,
Rien
Click to expand...
Click to collapse
Try connecting it to windows pc and mount storage internal storage will pop up if drivers are installed properly just copy and install rom.
Jitesh.saitawadekar said:
Try connecting it to windows pc and mount storage internal storage will pop up if drivers are installed properly just copy and install rom.
Click to expand...
Click to collapse
I tried installing the drivers I found through Google ("oneplus 2 usb drivers -> result on technobuzz).
After that I connected it to a windows pc and I got the message following message:
"USB device not recognized"
The last USB device you connected to this computer malfunctioned, and Windows does not recognize it.
So I still can't access the storage.
rienheuver said:
I tried installing the drivers I found through Google ("oneplus 2 usb drivers -> result on technobuzz).
After that I connected it to a windows pc and I got the message following message:
"USB device not recognized"
The last USB device you connected to this computer malfunctioned, and Windows does not recognize it.
So I still can't access the storage.
Click to expand...
Click to collapse
Might be usb issue try with some other usb .
Jitesh.saitawadekar said:
Might be usb issue try with some other usb .
Click to expand...
Click to collapse
Wow, never thought of that one... but it was the cable indeed.
Thanks for the help!

Erased my phone, need help.

I screwed up. I rooted my phone (oneplus 5) and was in the process of trying some new roms.
Went to install another rom and accidentally hit erase pretty much everything.
I figure no sweat, I'll just copy a rom from my PC onto the phone. No so easy.
Went in recovery (TWRP) The PC see the phone and "internal Storage" but won't allow me to copy anything to the phone, so I can't copy the rom to get back up and running.
Is there a way to flash the rom (zip) in fastboot onto the phone or a way to copy the zip to the phone so I can install it using TRWP?
Thanks.
I've had a mounting issue before, try rebooting to recovery, if that fails again I flashed the stock recovery to format all partitions then re flashed twrp.
blackcell1 said:
I've had a mounting issue before, try rebooting to recovery, if that fails again I flashed the stock recovery to format all partitions then re flashed twrp.
Click to expand...
Click to collapse
I can get into TWRP, but I have no files there (on the phone) to flash. How do I flash from the PC? I have the ROM zip files on the PC.
Click reboot, recovery on twrp and reconnect your phone to your PC and it should mount so you can drag files over
blackcell1 said:
Click reboot, recovery on twrp and reconnect your phone to your PC and it should mount so you can drag files over
Click to expand...
Click to collapse
That is not working and the device is no longer appearing in windows. Add to that, this time when I tried to communicating with it in fastboot, it the PC was reading "waiting for device" and doesn't seem to be communicating with the phone. Ugh.
Format user data in TWRP, reboot back into recovery and then try again.
Or you can run these commands in fastboot:
fastboot erase userdata
fastboot format userdata
Reboot into recovery and see if it works
rickysidhu_ said:
Format user data in TWRP, reboot back into recovery and then try again.
Or you can run these commands in fastboot:
fastboot erase userdata
fastboot format userdata
Reboot into recovery and see if it works
Click to expand...
Click to collapse
It is not.
I erased data in TWRP still will not appear in windows.
I can not connect with fastboot any longer, When in fastboot and trying to connect via the PC (fastboot device) I am getting "waiting for any device" I hope I'm not dead in the water.
noncomjd said:
It is not.
I erased data in TWRP still will not appear in windows.
I can not connect with fastboot any longer, When in fastboot and trying to connect via the PC (fastboot device) I am getting "waiting for any device" I hope I'm not dead in the water.
Click to expand...
Click to collapse
Erasing data is different from formatting
As for the fastboot error, try using a different USB port and also try restarting your computer.
Also make sure your fastboot/adb platform tools are up to date
noncomjd said:
I screwed up. I rooted my phone (oneplus 5) and was in the process of trying some new roms.
Went to install another rom and accidentally hit erase pretty much everything.
I figure no sweat, I'll just copy a rom from my PC onto the phone. No so easy.
Went in recovery (TWRP) The PC see the phone and "internal Storage" but won't allow me to copy anything to the phone, so I can't copy the rom to get back up and running.
Is there a way to flash the rom (zip) in fastboot onto the phone or a way to copy the zip to the phone so I can install it using TRWP?
Thanks.
Click to expand...
Click to collapse
If you have the rom on PC but you're enable to copy into device..... maybe ADB sideload? Through TWRP you can also sideload a rom, connecting the phone to pc but only if ADB driver is recognized....
EDIT: if i dont remember wrong you need only to open TWRP>Advanced>ADB Sideload>Swipe to start then connect the phone to pc and the command is adb sideload zipname.zip
Hope i've not forgot something :good:
rickysidhu_ said:
Erasing data is different from formatting
As for the fastboot error, try using a different USB port and also try restarting your computer.
Also make sure your fastboot/adb platform tools are up to date
Click to expand...
Click to collapse
Erasing data is different from formatting
Right you are.
As for the fastboot error, try using a different USB port and also try restarting your computer.
Been around computers now for a while now, you would think I'd check the basics. Was so damn pissed that I was so stupid to hit erase, I never checked the cable, it was half out...Doh!. Plugged it in and I was able to connect via fastboot, ran the two commands you wrote and was able to see my op5 on windows and was able to copy my files over.
Up and running, thank you all so very much.
rickysidhu_ said:
Erasing data is different from formatting
As for the fastboot error, try using a different USB port and also try restarting your computer.
Also make sure your fastboot/adb platform tools are up to date
Click to expand...
Click to collapse
Erasing data is different from formatting
Right you are.
As for the fastboot error, try using a different USB port and also try restarting your computer.
Been around computers now for a while now, you would think I'd check the basics. Was so damn pissed that I was so stupid to hit erase, I never checked the cable, it was half out...Doh!. Plugged it in and I was able to connect via fastboot, ran the two commands you wrote and was able to see my op5 on windows and was able to copy my files over.
Up and running, thank you all so very much.
noncomjd said:
Erasing data is different from formatting
Right you are.
As for the fastboot error, try using a different USB port and also try restarting your computer.
Been around computers now for a while now, you would think I'd check the basics. Was so damn pissed that I was so stupid to hit erase, I never checked the cable, it was half out...Doh!. Plugged it in and I was able to connect via fastboot, ran the two commands you wrote and was able to see my op5 on windows and was able to copy my files over.
Up and running, thank you all so very much.
Click to expand...
Click to collapse
No problem! We all have 'derp' errors every now and then lol. Glad you got it working!

Categories

Resources