I'm using havoc os with latest cosmicdan recovery. After i flashing January firmware, mtp on cosmicdan recovery stopped working my pc didn't even recognized the device not shown device manager too no sound or anything. I tried two PC's its still not working though. When i tried mohancm recovery mtp just started working fine. Any fix in this for @CosmicDan recovery.
aravindhghosh said:
I'm using havoc os with latest cosmicdan recovery. After i flashing January firmware, mtp on cosmicdan recovery stopped working my pc didn't even recognized the device not shown device manager too no sound or anything. I tried two PC's its still not working though. When i tried mohancm recovery mtp just started working fine. Any fix in this for @CosmicDan recovery.
Click to expand...
Click to collapse
Go to Mount menu and enable MTP.
Sent from my Mi A1 using XDA Labs
mitux said:
Go to Mount menu and enable MTP.
Sent from my Mi A1 using XDA Labs
Click to expand...
Click to collapse
No use i tried it but it won't work.
It's a known issue with permanent TWRP and Pie.
The solution is to boot TWRP from fastboot every time you need to transfer something.
IIRC, CosmicDan said he's not going to continue working on a new TWRP, so we'll have to wait until someone picks the project up
Related
I've been using the built-in CM updater almost daily for weeks now with no issues. Today, I noticed the CM11 nightlies were out. I excitedly downloaded it and installed it. It rebooted into ClockworkMod Recovery (which I don't recall it ever doing with CM10 nightlies) and gave a "set_metadata_recursive some changes failed . . . (Status 7)" error.
After doing some research, I think the issue may be that I'm still using an outdated CMR v6.0.1.9.
Should I have USB access when in CMR? When I plug the cable in, Windows says the device has malfunctioned
Assuming CMR is my issue, how can I update it without USB access?
I tried a factory reset, but it's still stuck in a boot loop.
I don't recall if USB access to the internal storage card is enabled while in CWM recovery or not, but for sure you can adb sideload any zip if you have adb setup on your PC. I suggest you to update your recovery then manually flash latest cm11. Then you'll use again the built-in updater for upcoming nightlies
clem_ita said:
I don't recall if USB access to the internal storage card is enabled while in CWM recovery or not, but for sure you can adb sideload any zip if you have adb setup on your PC. I suggest you to update your recovery then manually flash latest cm11. Then you'll use again the built-in updater for upcoming nightlies
Click to expand...
Click to collapse
Sideloading is new to me. I'll give it a shot this afternoon and post back. Thanks!
It is your outdated CWM recovery. Get the latest cwm recovery and it will all be fine
Had the same issue with Nexus 4, Nexus 7 and Galaxy S3
Was always caused by older version of cwm
You don't have usb access? Just restore a backup then
If you fastboot flash the new cwm recovery and ROM, wipe cache you will be golden. Without loss of data
Sent from my Nexus 4 using Tapatalk
I used WUGFRESH to install 5.0, rooted, installed latest TWRP.. and get ADB just fine when the N7 is normally booted. However, when using TWRP, I'm unable to get an ADB connection, normal or sideload. I noticed MTP is turned on in TWRP, which may be the problem, but don't see any want to turn it off. Any thoughts appreciated! thanks, jf
EDIT: ADB works fine if I use CM Recovery, but can't format to F2FS with CM, which is why I want to use TWRP.
EDIT: I found out how to turn off MTP, its under MOUNT, but that did not fix the problem.
friedsonjm said:
EDIT: I found out how to turn off MTP, its under MOUNT, but that did not fix the problem.
Click to expand...
Click to collapse
That worked for me. MTP goes away, and boom! adb comes right up seconds later. (twrp v2.8.1.0 iirc)
I'm not sure if TWRP stores it's settings in the ".twrps" file or not, but it seems to remember you've toggled that button the next time you boot it. Probably that lasts until the next time /data is fully wiped.
Hey guys,
so I tried flashing Omni 8.0 rom and I was stuck at the boot screen. so I went back into twrp tried to reflash still nothing. I flashed a new version of twrp the one that can use multirom and it erased all my data. I flashed back the twrp I started with and now I can not sideload the full OTA zip to get back to stock. It says "cannot load one.zip" which is what I have it labeled as. I tried to download the recovery tool and I can't seem to figure out how to get the driver to work so it will see me on my comm port. Does anyone have any ideas on what to do or what happened? I'm stuck in twrp.
almost looks like it can't mount the system
IDK, maybe a broken download. I'd try to restore a backup if you have one, if not Wipe > Factory Reset. If it still doesn't boot after 20 minutes, refer to this thread: https://forums.oneplus.net/threads/i-have-to-go-back-to-oxygen-os.649947/#post-16907420. Basically, download the OOS ROM onto your computer and use an ADB/USB Sideload in TWRP recovery (you can flash Oxygen Recovery from TWRP if TWRP doesn't work) to install it. May take a while to boot.
I have no idea how it happened but I got my system mounted again that was my problem. I'm back.
thread can be closed
keeganjk said:
IDK, maybe a broken download. I'd try to restore a backup if you have one, if not Wipe > Factory Reset. If it still doesn't boot after 20 minutes, refer to this thread: https://forums.oneplus.net/threads/i-have-to-go-back-to-oxygen-os.649947/#post-16907420. Basically, download the OOS ROM onto your computer and use an ADB/USB Sideload in TWRP recovery (you can flash Oxygen Recovery from TWRP if TWRP doesn't work) to install it. May take a while to boot.
Click to expand...
Click to collapse
thanks for the reply mate
snipeez1987 said:
thanks for the reply mate
Click to expand...
Click to collapse
yw
snipeez1987 said:
Hey guys,
so I tried flashing Omni 8.0 rom and I was stuck at the boot screen. so I went back into twrp tried to reflash still nothing. I flashed a new version of twrp the one that can use multirom and it erased all my data. I flashed back the twrp I started with and now I can not sideload the full OTA zip to get back to stock. It says "cannot load one.zip" which is what I have it labeled as. I tried to download the recovery tool and I can't seem to figure out how to get the driver to work so it will see me on my comm port. Does anyone have any ideas on what to do or what happened? I'm stuck in twrp.
Click to expand...
Click to collapse
Easy fix for "Cannot load xxx.rom": you have to patch the adb.exe with a large address awareness program. Google it, I found one in another XDA thread.
Reason: the ROM filesize is too large. For small ROMs (like custom ROMs) adb would recognise it without any problems.
ipredatorv said:
Easy fix for "Cannot load xxx.rom": you have to patch the adb.exe with a large address awareness program. Google it, I found one in another XDA thread.
Reason: the ROM filesize is too large. For small ROMs (like custom ROMs) adb would recognise it without any problems.
Click to expand...
Click to collapse
Awesome. I'll keep that in mind. I'm sure I'll mess it up again lol. Hopefully not though.
I can't do anything in twrp and am trying to root it but can't find magisk or any other files because twrp won't show me them.
I tried going to wipe > repair or change file system and clicking on it says invalid partition selection. Can't backup either because storage won't mount.
Also if I try to reboot to system out of twrp, twrp just crashes before my phone restarts(It still reboots into the OS though). I never even get a chance to click the reboot button.
Lastly if I want to get back into twrp it seems I have to flash the twrp via the bootloader every time.
And I CAN transfer files while OOS is running, I just can't get them in TWRP.
I've read that formatting might work, but will formatting remove the OS? I wouldn't want to chance anything since it seems impossible to flash anything right now.
Flash codeworkx twrp 8.0 with TOOL ALL IN ONE or ADB.
Tiago A said:
Flash codeworkx twrp 8.0 with TOOL ALL IN ONE or ADB.
Click to expand...
Click to collapse
It's codeworkx the only TWRP that is working with Oreo?
Eric214 said:
It's codeworkx the only TWRP that is working with Oreo?
Click to expand...
Click to collapse
No bluespark is working too without problems for me on oos Oreo
Eric214 said:
It's codeworkx the only TWRP that is working with Oreo?
Click to expand...
Click to collapse
Bluspark too
Do you have to flash twrp for this to work, or can you just fastboot into the twrp image?
Hi, I have a essential phone running Oreo 8.1, just recently I have rooted the phone with magisk v16 an twrp 3.2.1, I successfully flashed it with twrp but after the flash whenever I want to get into twrp it just freezes up on the mount data screen and I have to force reboot it, does anyone know a solution to this problem
Make sure you're following the exact steps from this post. Every step is crucial (except #3, because you have to disable your screen lock before booting twrp.
You shouldn't have to manually mount anything in TWRP either. The magisk installer might give you an error about mounting system but it doesn't seem to make any difference.
[QRCODE][/QRCODE]
yellk20 said:
Hi, I have a essential phone running Oreo 8.1, just recently I have rooted the phone with magisk v16 an twrp 3.2.1, I successfully flashed it with twrp but after the flash whenever I want to get into twrp it just freezes up on the mount data screen and I have to force reboot it, does anyone know a solution to this problem
Click to expand...
Click to collapse
You cannot have TWRP installed with 8.x.
TWRP is not compatible.
You must flash the original boot image, then install magisk.
TWRP cannot remain.
You will boot loop.
Please read the instructions on rooting carefully.
Ok thank you
Why can't TWRP replace recovery instead of boot?
RawSlugs said:
Why can't TWRP replace recovery instead of boot?
Click to expand...
Click to collapse
No one has created a bit image with TWRP as the recovery.
Sent from my PH-1 using XDA Labs
RawSlugs said:
Why can't TWRP replace recovery instead of boot?
Click to expand...
Click to collapse
Because the partition layout of the Essential does not have a recovery partition.
Recovery is contained in the boot image.
So to have TWRP resident/permanent, the boot image must be patched.
It has been done for 7.x, but sense 8.x is still beta, there is no official TWRP for Oreo.
Once Oreo is final, I expect we will get a TWRP that works.
The current limitation, means you can't flash without a computer handy.