Device - OnePlus 5 (64GB), TWRP 3.3.1-0-20190713-codeworkx
Yesterday, while trying to reset my phone I accidentally wiped the system partition. I am able to boot the device into fastboot mode and TWRP (doesn't ask for any password), however the phone is going undetected on my Mac.
I tried ADB side loading using terminal, following error comes -
Device (Null) not found.
Tried to connect thru OTG, even that is going unnoticed. I just want to copy the ROM file to phone, in order to restore it to stock condition.
Any help would be appreciated...
Was your device encrypted and you had a password? Otherwise it's normal that it doesn't ask for a password.
First off, I don't know how proficient you are.
I assume
- You're in TWRP
- Your phone is connected to your Mac and charges
- You're using a cable that can transfer data, eg. the Dash Charge cable
In TWRP, go to mount. You can either have MTP or adb enabled, not both at once AFAIK (MTP disabled = adb enabled). You probably have it disabled. You can either get the zip to the phone by MTP or via adb push. I think it happened once that I had to switch MTP off and on again.
If you try to use a USB stick, you have to mount it. You can do that under mount too. I'm currently not sure where it will be mounted though. (I don't know what formats are supported, but Fat32 should do the job).
I assume you tried sideload correctly, but just to make sure you did it right, you have to go to Advanced -> Sideload and enable it, THEN use the command 'adb sideload ....
If nothing of the above works, I only assume there's something wrong with the recovery. Try another version, official, codeworkx (he posted a thread), or blu_spark (latest version is on GitHub).
You can modify the system partition without needing to decrypt, doesn't matter.
Related
Alright here is my situation. I ran the latest OTA update on the stock rom and the phone started going into
a boot loop. My problem is that I havent performed a recent backup and need to access some files on the
phone. Developer mode is enabled, however I disabled USB debugging prior to running the update. When my
phone reboots, I remove the battery and restart the phone but every once in a while my phone successfully
loads and I am able to punch in my pin to unlock the phone. However, a few seconds later the phone reboots.
I tried to access the phone using ADB but because I dont have USB debugging enabled I dont see any devices
when I run the "adb devices" command. I also tried to acquire a smartphone image using encase forensic, but
yet again, because USB debuggin is not enabled, I am not able to pull data.
I am able to go into recovery mode and I tried to wipe my cache partition, but that did not help.
My questions are:
1. Is there a way for me to access my data files while the phone is stuck in a boot loop and USB debugging is
disabled?
2. Is it possible for me to download the latest update, copy it over to my sdcard and rerun the update from
my sdcard from recovery mode? Could this possibly solve my problem?
3. In a worst case scenario, if I do a factory wipe/reset, will this solve my problem and what is the
likelyhood of recovering my files from the data partition?
Any tips, tricks, advice is greatly appreciated.
tparnet said:
Alright here is my situation. I ran the latest OTA update on the stock rom and the phone started going into
a boot loop. My problem is that I havent performed a recent backup and need to access some files on the
phone. Developer mode is enabled, however I disabled USB debugging prior to running the update. When my
phone reboots, I remove the battery and restart the phone but every once in a while my phone successfully
loads and I am able to punch in my pin to unlock the phone. However, a few seconds later the phone reboots.
I tried to access the phone using ADB but because I dont have USB debugging enabled I dont see any devices
when I run the "adb devices" command. I also tried to acquire a smartphone image using encase forensic, but
yet again, because USB debuggin is not enabled, I am not able to pull data.
I am able to go into recovery mode and I tried to wipe my cache partition, but that did not help.
My questions are:
1. Is there a way for me to access my data files while the phone is stuck in a boot loop and USB debugging is
disabled?
2. Is it possible for me to download the latest update, copy it over to my sdcard and rerun the update from
my sdcard from recovery mode? Could this possibly solve my problem?
3. In a worst case scenario, if I do a factory wipe/reset, will this solve my problem and what is the
likelyhood of recovering my files from the data partition?
Any tips, tricks, advice is greatly appreciated.
Click to expand...
Click to collapse
Boot phone into recovery mode. You can access phone now and make backup or download need files to PC.
svs57 said:
Boot phone into recovery mode. You can access phone now and make backup or download need files to PC.
Click to expand...
Click to collapse
Thanks svs57 for the quick reply.
Would you mind elaborating a bit more? I am an IT guy but by no means a developer. When I boot into recovery is the phone supposed to show up in My Computer via MTP or PTP? The phone is not showing up as a device. Or am I supposed to use adb commands to pull the files down?
When I go into recovery and run the "adb devices" command now I get what appears to be a serial number followed by the word "unauthorized". I rebooted and went into recovery mode again this time tried "apply update from ADB". When I try using either the adb push or adb pull I get "error: closed"
Thanks again for the help.
You have to use latest version of adb. Then you can login to phone via adb and find file you want to backup. Then use "adb pull" to get file to PC.
If you have custom recovery you also can make backup you data using recovery.
Also you can flash the same ROM you have without wipe data.
Ok, I'm going to start by explaining everything I did up to this point to eliminate any troubleshooting sugggestions i may have already done.
I rooted and installed recovery the same way everyone else did. After a couple of days, I tried to install a ROM but im assuming i was encrypted because i was stuck in a loop that would only boot me into TWRP. Did my research and took the necessary steps to get around that and decrypt and boot into the new ROM.. FINALLY!!! Only one problem, this rom doesn't have Super SU installed, Alright... so i download the proper Super SU build and put it on my Micro SD card and try to boot into TWRP to flash....
This is where the problem begins. I never get the prompt to authorize my PC from my phone to allow anything, and i never did each time i reset. I'm almost certain the adb on this rom is messed up, i've wiped about 4-5 times to re-enable usb debugging from scratch in order to adb or fastboot into recovery via command prompt, however when i try adb, i get that unauthorized error an there's no option on the LG V20 to revoke under developer settings. Fastboot i just get the same "waiting for device" message. Also keep in mind that i set it to photo mode, every mode that was available and nothing. Tried different USB Cords and did this on both my laptop and my PC at work
I've tried uninstalling and reinstalling all of the drivers, re-installed the latest version of adb and fastboot to my PC, that didn't work either. Tried deleting the adbkeys file in the .android folder and still nothing.
When i try to boot in recovery manually, i just get the wipe data option and when i click yes to everything, it actually wipes my data. I'm unable to reflash TWRP because I can't access ADB or Fastboot due to the unauthorized error.
Someone, PLEASE HELP!!!!
any luck?
ahq1216 said:
Ok, I'm going to start by explaining everything I did up to this point to eliminate any troubleshooting sugggestions i may have already done.
I rooted and installed recovery the same way everyone else did. After a couple of days, I tried to install a ROM but im assuming i was encrypted because i was stuck in a loop that would only boot me into TWRP. Did my research and took the necessary steps to get around that and decrypt and boot into the new ROM.. FINALLY!!! Only one problem, this rom doesn't have Super SU installed, Alright... so i download the proper Super SU build and put it on my Micro SD card and try to boot into TWRP to flash....
This is where the problem begins. I never get the prompt to authorize my PC from my phone to allow anything, and i never did each time i reset. I'm almost certain the adb on this rom is messed up, i've wiped about 4-5 times to re-enable usb debugging from scratch in order to adb or fastboot into recovery via command prompt, however when i try adb, i get that unauthorized error an there's no option on the LG V20 to revoke under developer settings. Fastboot i just get the same "waiting for device" message. Also keep in mind that i set it to photo mode, every mode that was available and nothing. Tried different USB Cords and did this on both my laptop and my PC at work
I've tried uninstalling and reinstalling all of the drivers, re-installed the latest version of adb and fastboot to my PC, that didn't work either. Tried deleting the adbkeys file in the .android folder and still nothing.
When i try to boot in recovery manually, i just get the wipe data option and when i click yes to everything, it actually wipes my data. I'm unable to reflash TWRP because I can't access ADB or Fastboot due to the unauthorized error.
Someone, PLEASE HELP!!!!
Click to expand...
Click to collapse
different route but im in the same boat. any luck?
I fixed this shortly after. Wanted to avoid returning to stock as. The only option was you and I was on 10d. I had to go back to stock but luckily the recovery method still works.
Hello everyone,
I recently decided too install the LineageOS.
Everything went fine, but I forgot Gapps and didnt want too use my phone without them so I decided too install the ROM again but this time with the apps.
I followed the linageos guide but accidently wiped everything before I could
Code:
adb push filename.zip /sdcard/
(dunno if thats the problem)
Im using TWRP 3.1.1-1. I can get into Recovery Mode. While in fastboot modus my pc detects my phone as an OnePlus, in Recovery modus its just android.
Code:
fastboot devices
shows my serial number. OEM is unlocked.
while in recovery mode
Code:
adb push filename.zip /sdcard/
gets me
Code:
No such file or directory
Code:
adb push C:\User\...filename.zip /sdcard/
gets me
Code:
failed to copy.. remote couldnt create file
while in fastboot mode I get
Code:
no devices/emulator found
Copying by dragging the file into internal storage doesnt work neighter.
I dont know what I did different besides the wipe before the copying. Maybe the wipe deactivates USB Debugging?
Maybe someone sees where my problem is.
Thanks
r717
I guess you don't have an OTG Drive.
you could always go 100% stock again and then flash LineageOS
http://downloads.oneplus.net/oneplus-5/oneplus_5_oxygenos_4.5.13/
well first thanks for your reply. I flashed the original recovery and tried 2 sideload now. Seems to be driver problems. So I have to try every solution with Win10 and OP5 drivers I guess?
Make sure the Android drivers on your computer are up to date and also that you don't have any old drivers from a previous phone. I accidentally wiped everything on my OP5 once but when I connected it to my Windows 10 computer the OP5 was still recognized as a storage device--but I used TWRP not the stock recovery and also used the file explorer in TWRP. With the stock recovery you should still be able to side load flash the stock ROM from your computer. If you can't it's likely a driver issue.
I had once a similar issue, although not exactly this, just something with drivers.
A long process to fix was to install Linux as a virtual machine in Windows and that worked well. I could do all I needed, the phone was quickly recognized.
Virtualbox or VMware both are free/have a free version and I used Ubuntu.
Give it a try if all else fails.
Hello everyone,
I've wasted my Christmas days to - unsuccessfully - re-root a Shield (16GB; 2015) after upgrading to Software 7.2.1. I need to use more than one USB mass storage device and to be able to copy from one to another, so I want to re-enable Stickmount.
The device was rooted before (which means the bootloader was already unlocked, too), and enabling USB debug, finding the device on my PC via "adb devices" was no problem, either. Issuing "adb reboot bootloader" went fine, too, the device could now be seen via "fastboot devices".
So, I flashed the TWRP image (I actually tried three different versions, 3.0.2, 3.1.1, and the most recent 3.2.3). All seemed to load fine (it spewed out two time values followed by OKAY, took about one second), but the reboot that follows only shows the NVIDIA logo forever without anything else happening (the longest I waited was 20 minutes) - according to the docs I could find (and had used before), TWRP should appear after about 15 seconds.
So, I'm stuck. I cannot get TWRP to start which prevents me from sideloading SuperSU, which means I can't use Stickmount.
Is there anything I did wrong? Is there any other way to get Stickmount installed onto my Shield? Any help is appreciated.
Cheers, Pit.
You'll need to wait until TWRP gets updated to get around the new android security measures. So keep checking TWRP website periodically to see when a new version is released.
You could have found this out if you went to Nvidia Shields Android TV forum and read some posts.
I was reading here, as well as at the nvidiashieldzone, where the tutorials are up, plus I was googling for the errors I was getting to no avail. Sorry for not finding every post on every forum on the internet, and thanks for giving the right pointer.
That means there is currently no way whatsoever to get the Shield rooted on 7.2.1., right?
Not just now, there's a guide to root 7.2 - using a developer image, and there's a chance of bricking - best to wait until TWRP is updated - also you don't need to root to use stickmount.
You only need to do something like this:
adb reboot bootloader
fastboot boot twrp-3.2.3-0-foster.img
#in twrp - mount/system - select storage - internal storage
adb shell
pm install -i "com.android.vending" -r /sdcard/Download/stickmount.apk
adb reboot
That way you can use your apk without being rooted - and your device will still be secure, and you can use widevine etc for netflix and other apps that check to see if your device is rooted.
Or you can just push the driver files stickmount uses like this:
adb reboot bootloader
fastboot boot twrp-3.2.3-0-foster.img
#in twrp - mount/system - select storage - internal storage
adb push hosts /system/etc/hosts (example file)
adb shell "chmod -R 644 /system/etc/hosts"
adb reboot
Thanks for the info - if I understand this correctly, I can install apks with root-like permissions using TWRP without rooting the whole device, right?
I will try that out once TWRP is working again.
So I screwed up. When wiping my system for lineageos, I accidentally wiped everything, including the system, internal storage, and data. I am in TWRP right now. Trying to send files over at MTP just makes the progress bar not move. I cannot move it over with my phone mounted as a usb storage device. When using adb push to send over a ROM, the command completes, but it does not appear in the sdcard folder as I specified. Adb sideload just stops at 50%, with the phone displaying step 2/2 and not continuing after that- I have the option to reboot or wipe dalvik / cache. I have no OS. I know that rebooting into TWRP again will make MTP work, however as I have no OS installed I know that I will not be able to access fastboot. Any ideas on how to get a rom onto my phone's storage?
You might need to format your internal storage as it may still be encrypted which may be why files aren't copying across. This is just a guess though. If all else fails (I have been in a similar situation before), you should be able to boot into fastboot (bootloader) mode from TWRP and flash OOS back through that. You would need to find the fastboot version of the ROM. I believe there is a thread in this forum somewhere. A last resort would be using the MSMTool to get back to stock. I've never had to do this myself though. The phone will be in a like brand new state though, so you would need to unlock the bootloader again if you are going to flash a custom ROM or do any modding after.
You can use OTG storage, encryption has no effect on it and you can flash files too. I used it to bypass the encryption issue in TWRP. If that doesn't work then post #2 is your best option. Also you can still boot in fastboot even if your ROM is broken. You can find the fastboot ROMs in the guide section.