Hey all,
Hopefully you can help me here.
I've been out of the rooting game for a while and decided to get my pixel 2xl back out,whilst I've rooted and installed twrp no problems,what I'm struggling to figure out is this, when I go to back up my stock but rooted A10 QQ2A ROM it always fails out, and complains of being unable to mount system and vendor.
I've done a Critical_Unlock when I unlocked the bootloader,so I thought I'd have FULL control over such things. What am I inevitably doing wrong? And what partitions should I select in order to have a functioning backup.
I've had the same messages for months but the backup always completed. Yesterday however, I got the same last message as you and my backup failed as well. Hopefully the developer or somebody with more experience will chime in with a fix.
I am perplexed,I seem to remember running Android 9 with twrp with no such issues,but I cannot backup my stock rom.
I used to always back every partition up and restore with no problems,with my old one plus 6,and even this very pixel 2 XL last summer,something in Android and twrp must have changed.
TWRP can't mount system, so no backup.
Google for "twrp" & "android 10"
Sui77 said:
TWRP can't mount system, so no backup.
Google for "twrp" & "android 10"
Click to expand...
Click to collapse
Well that's a tough pill to swallow,looks like unless i can roll back to a A9 ROM,I'm unrooting and staying stock.
Sent from my Pixel 2 XL using Tapatalk
Davies_90 said:
Hey all,
Hopefully you can help me here.
I've been out of the rooting game for a while and decided to get my pixel 2xl back out,whilst I've rooted and installed twrp no problems,what I'm struggling to figure out is this, when I go to back up my stock but rooted A10 QQ2A ROM it always fails out, and complains of being unable to mount system and vendor.
I've done a Critical_Unlock when I unlocked the bootloader,so I thought I'd have FULL control over such things. What am I inevitably doing wrong? And what partitions should I select in order to have a functioning backup.
Click to expand...
Click to collapse
Twrp will not work on android 10 stock it cant mount or decrypt. It is able to mount on some roms like Lineage & AOSIP
---------- Post added at 12:49 PM ---------- Previous post was at 12:41 PM ----------
Davies_90 said:
Well that's a tough pill to swallow,looks like unless i can roll back to a A9 ROM,I'm unrooting and staying stock.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Also you can still flash roms using twrp its saying cant mount wont pose an issue with flashing roms
Related
Has anyone heard anything about when we're supposed to get a custom recovery for these Pixels? I still haven't really set my phone back up the way I like it since rooting because it takes forever and I just know that as soon as I get it set up TWRP will drop and I'll have to wipe it again. Also, is clockworkmod recovery still a thing? I've been out of the rooting scene for a bit.
Last update by Ethan Yonker (the head guy for TWRP) was able to get TWRP to load but because of the new FBE and dual partitions for seamless updates is going to take him awhile before there's an actual fully functional working version of TWRP. As for CWM, no clue, haven't used them since I've switched from the Thunderbolt to the S3.
Koush
scsa20 said:
Last update by Ethan Yonker (the head guy for TWRP) was able to get TWRP to load but because of the new FBE and dual partitions for seamless updates is going to take him awhile before there's an actual fully functional working version of TWRP. As for CWM, no clue, haven't used them since I've switched from the Thunderbolt to the S3.
Click to expand...
Click to collapse
I contacted Koush(CWM) a few days ago and asked about cwm for our devices no response as of yet,he may be out of the scene.
Or i think he was working with Cyanogen on something not sure.
lol the clockworkmod app hasnt even been updated in like 4 yrs, those guys are long gone
cwalker0906 said:
lol the clockworkmod app hasnt even been updated in like 4 yrs, those guys are long gone
Click to expand...
Click to collapse
Wow yeah I just looked at their rom manager app in the play store. Last update was Jan of 2014. It's kinda trippy how they just went to the wayside. I remember when I first got into Android (2012) cwm was like a major player in the custom recovery space. Looks like TWRP eeked them out.
There's no real reason for multiple recoveries. TWRP was far superior and made sense. Touch recovery for touch phones.
humdrum2009 said:
I contacted Koush(CWM) a few days ago and asked about cwm for our devices no response as of yet,he may be out of the scene.
Or i think he was working with Cyanogen on something not sure.
Click to expand...
Click to collapse
You should probably ask the maintainers for the device under CM. If there are any yet. He has probably already had that question a million times.
---------- Post added at 03:26 PM ---------- Previous post was at 03:25 PM ----------
norcal61 said:
Has anyone heard anything about when we're supposed to get a custom recovery for these Pixels? I still haven't really set my phone back up the way I like it since rooting because it takes forever and I just know that as soon as I get it set up TWRP will drop and I'll have to wipe it again. Also, is clockworkmod recovery still a thing? I've been out of the rooting scene for a bit.
Click to expand...
Click to collapse
If you have already unlocked your bootloader? Why would you need to wipe your device again?
pcriz said:
If you have already unlocked your bootloader? Why would you need to wipe your device again?
Click to expand...
Click to collapse
Mostly because I have OCD about whenever I flash something new I do a full wipe. And I'm sure that when TWRP happens that the custom roms will come rolling in and I'll definitely be doing a full wipe before flashing a custom ROM.
Why a new thread for TWRP when there was already one posted.
Nobody knows how to search the forums anymore?
pcriz said:
You should probably ask the maintainers for the device under CM. If there are any yet. He has probably already had that question a million times.
---------- Post added at 03:26 PM ---------- Previous post was at 03:25 PM ----------
If you have already unlocked your bootloader? Why would you need to wipe your device again?
Click to expand...
Click to collapse
Usually any more you need to format your phone to have it decrypted. Twrp required this on my unlocked Htc 10.
scsa20 said:
Last update by Ethan Yonker (the head guy for TWRP) was able to get TWRP to load but because of the new FBE and dual partitions for seamless updates is going to take him awhile before there's an actual fully functional working version of TWRP. As for CWM, no clue, haven't used them since I've switched from the Thunderbolt to the S3.
Click to expand...
Click to collapse
CWM is dead dude lol.
I recently flashed Resurrection Remix standard Nougat Edition with the latest version of open gapps, nothing else. I then proceeded to make a backup with TWRP as IMO its always good to have a backup at this fresh working condition. This is the issue going into TWRP and choosing backup and swiping to start the backup i get the error "unable to mount storage" and the backup fails.
I am able to access files via MTP with windows but for some reason TWRP isn't working.
I am afraid to do anything at the moment as without a means to backup or restore via backup i'm afraid of bricking my device. Since i've owned my 1+3 I've always just stayed stock with magisk but i thought hey why not have fun right so I decided to check out Resurrection Remix and I it but I don't like not being able to create backups or really even use TWRP. My first thought would to Re-Flash TWRP but as i said without some more knowledge I don't want to try anything.
Thank you in advance for reading my post and thank you a thousand times if you can help me out. If you need information or any sort of logs please ask.
lebeatnik said:
I recently flashed Resurrection Remix standard Nougat Edition with the latest version of open gapps, nothing else. I then proceeded to make a backup with TWRP as IMO its always good to have a backup at this fresh working condition. This is the issue going into TWRP and choosing backup and swiping to start the backup i get the error "unable to mount storage" and the backup fails.
I am able to access files via MTP with windows but for some reason TWRP isn't working.
I am afraid to do anything at the moment as without a means to backup or restore via backup i'm afraid of bricking my device. Since i've owned my 1+3 I've always just stayed stock with magisk but i thought hey why not have fun right so I decided to check out Resurrection Remix and I it but I don't like not being able to create backups or really even use TWRP. My first thought would to Re-Flash TWRP but as i said without some more knowledge I don't want to try anything.
Thank you in advance for reading my post and thank you a thousand times if you can help me out. If you need information or any sort of logs please ask.
Click to expand...
Click to collapse
I am tired of repeating this.
I think that you are on the official version of TWRP which is good if your ROM is OOS. But when shifting to custom ROMs, it is a good idea to flash eng.stk's TWRP.
The official TWRP will not work with custom ROMs.
The official TWRP will not work with custom ROMs.
???!!!
I'm with official twrp 3.1.1.2 , flashing custom ROMs and using them , till today, no problem. I think his data encrypted so twrp not showing storage.
I am on the official version of TWRP I have not read anywhere about that issue, so if I flash eng.stk's TWRP it should work? Sorry your tired of repeating it but it's not on the ROMs thread so idk where I would have gotten that info, but thanks
drmuruga said:
The official TWRP will not work with custom ROMs.
???!!!
I'm with official twrp 3.1.1.2 , flashing custom ROMs and using them , till today, no problem. I think his data encrypted so twrp not showing storage.
Click to expand...
Click to collapse
May be I shouldn't have been that categorical, but for many, the issue is there. Glad that it works for you.
---------- Post added at 05:27 PM ---------- Previous post was at 05:25 PM ----------
lebeatnik said:
I am on the official version of TWRP I have not read anywhere about that issue, so if I flash eng.stk's TWRP it should work? Sorry your tired of repeating it but it's not on the ROMs thread so idk where I would have gotten that info, but thanks
Click to expand...
Click to collapse
Why don't you try? You are not going to lose anything.
Also take into account the post above yours regarding encryption.
It worked, for some reason official TWRP would not unlock after I entered the encryption code, blue spark TWRP works, thanks, this is probably what I would have tried but it's nice to have gotten some info on the issue before I went flashing things Willie nillie
After you flash your files in TWRP, then select reboot, and reboot back into TWRP
Hello my fellow 5t owners.
Now I'm no noob when it comes to Android, but I have a small question to ask everyone, to guage what people do, and how they do it.
I'm assuming we are all rooted so can not take OTA updates.
The question is this:
When a new update comes out, do u dirty flash on top of ur original firmware, or do u do a full wipe and a clean flash?
If ur dirty, like me, then we all know how to do that.
If u clean flash every update, what steps do u take to back up everything on ur device before u wipe? Do u just use TiBu for apps and data or do u take any other additional steps?
I like forward to reading it replies
its usually ok to dirty flash an update providing its based on the same rom source (oos or aosp), i would wipe cache after tho.
I only ever dirty flash from the same OS, I tend to stick to OOS so it's kinda easy and everything stays the same, I just have to go into TiBu, back up newer versions and then debloat everything I usually get rid of, lol.
Sent from my OnePlus5T using XDA Labs
I usually flash AOSP ROMs and clean flash whenever the developer recommends it. I'll also clean flash even if it's safe to dirty flash, but only when I have free time. The way I backup and restore is:
Apps, call logs and sms with TiBackup
Bluetooth and WiFi with Pairs
Create a backup within Nova for my homescreen setup
I go through my ROM settings again manually though
rickysidhu_ said:
I usually flash AOSP ROMs and clean flash whenever the developer recommends it. I'll also clean flash even if it's safe to dirty flash, but only when I have free time. The way I backup and restore is:
Apps, call logs and sms with TiBackup
Bluetooth and WiFi with Pairs
Create a backup within Nova for my homescreen setup
I go through my ROM settings again manually though
Click to expand...
Click to collapse
That's great info thanx.
I used to be a flashaholic when I was running a custom ROM, mainly used OmniROM on my Galaxy S3, but now OOS is actually a really good close to stock ROM so I am happy with it. I like the closest to stock Android I can get, just using Evie Launcher instead of OnePlus Launcher.
Sent from my OnePlus5T using XDA Labs
Adam3Sixty said:
Hello my fellow 5t owners.
Now I'm no noob when it comes to Android, but I have a small question to ask everyone, to guage what people do, and how they do it.
I'm assuming we are all rooted so can not take OTA updates.
The question is this:
When a new update comes out, do u dirty flash on top of ur original firmware, or do u do a full wipe and a clean flash?
If ur dirty, like me, then we all know how to do that.
If u clean flash every update, what steps do u take to back up everything on ur device before u wipe? Do u just use TiBu for apps and data or do u take any other additional steps?
I like forward to reading it replies
Click to expand...
Click to collapse
TiBu is more than enough i think.
Also, im having trouble dirty flashing the new oreo update on my 5t. Idk where im going wrong.
what i did :
flash the full sized update on top of OOS 4.7.6
flash magisk
reboot to recovery
reboot to system
after i do this the device doesnt boot and i can see a static led light on and thats it.
---------- Post added at 12:05 PM ---------- Previous post was at 12:03 PM ----------
Adam3Sixty said:
That's great info thanx.
I used to be a flashaholic when I was running a custom ROM, mainly used OmniROM on my Galaxy S3, but now OOS is actually a really good close to stock ROM so I am happy with it. I like the closest to stock Android I can get, just using Evie Launcher instead of OnePlus Launcher.
Sent from my OnePlus5T using XDA Labs
Click to expand...
Click to collapse
i totally agree. OOS is really good
Try to reflash the rom, do not flash magisk but reboot system. Then you can reinstall TWRP and flash magisk.
pargas said:
Try to reflash the rom, do not flash magisk but reboot system. Then you can reinstall TWRP and flash magisk.
Click to expand...
Click to collapse
Okay I'll try that. Thanks!
worked. thanks!
darkishrex said:
TiBu is more than enough i think.
Also, im having trouble dirty flashing the new oreo update on my 5t. Idk where im going wrong.
what i did :
flash the full sized update on top of OOS 4.7.6
flash magisk
reboot to recovery
reboot to system
Click to expand...
Click to collapse
pargas said:
Try to reflash the rom, do not flash magisk but reboot system. Then you can reinstall TWRP and flash magisk.
Click to expand...
Click to collapse
darkishrex said:
worked. thanks!
Click to expand...
Click to collapse
and now I know exactly what I'll be doing on Sunday morning
Should have a Boeffla Kernel beta to try as well!!
Sent from my OnePlus5T using XDA Labs
So after almost a whole day of blood, sweat and tears, I am FINALLY on OOS 5.0.2!! And what a nightmare it was
I ended up having to totally wipe everything, after trying to restore my back up and getting the "ENCRYPTION FAILED" ur device is now borked message.
STILL haven't got everything sorted, and kicking myself that I didn't flash 5.0.3 seeing as it's out in the wild, but never mind, I am now on Oreo and it's working almost perfectly, with Magisk and Systemless Xposed.
Sent from my OnePlus 5T using XDA Labs
I recently flashed OOS 8.0 Beta 1 and now I am no longer able to mount my data partition. I have flashed the official TWRP and Blu_Spark TWRP, but neither is able to mount data. It does not provide any error messages, but when I attempt to mount the data partition it simply will not mount it.
Any suggestions? I am willing to wipe everything if needed, as I performed a back up prior to flashing OOS 8.0.
Thanks in advance!
You are probably encrypted, I think TWRP is not able to decrypt data yet.
Sent from my OnePlus5T using XDA Labs
Unn113 said:
You are probably encrypted, I think TWRP is not able to decrypt data yet.
Sent from my OnePlus5T using XDA Labs
Click to expand...
Click to collapse
Thanks for the response Unn113. Do I simply need to format and start from scratch?
trippmcnealy said:
I recently flashed OOS 8.0 Beta 1 and now I am no longer able to mount my data partition. I have flashed the official TWRP and Blu_Spark TWRP, but neither is able to mount data. It does not provide any error messages, but when I attempt to mount the data partition it simply will not mount it.
Any suggestions? I am willing to wipe everything if needed, as I performed a back up prior to flashing OOS 8.0.
Thanks in advance!
Click to expand...
Click to collapse
Same thing happened to me. I fastboot flashed the recovery.img to get it working again. I flashed the Blue_Spark from this thread
[OFFICIAL] OxygenOS Open Beta 1 (Android O) for the OnePlus 5T
Post#2
Jackson.Armstrong.Blow said:
Same thing happened to me. I fastboot flashed the recovery.img to get it working again. I flashed the Blue_Spark from this thread
[OFFICIAL] OxygenOS Open Beta 1 (Android O) for the OnePlus 5T
Post#2
Click to expand...
Click to collapse
Thanks!
trippmcnealy said:
I recently flashed OOS 8.0 Beta 1 and now I am no longer able to mount my data partition. I have flashed the official TWRP and Blu_Spark TWRP, but neither is able to mount data. It does not provide any error messages, but when I attempt to mount the data partition it simply will not mount it.
Any suggestions? I am willing to wipe everything if needed, as I performed a back up prior to flashing OOS 8.0.
Thanks in advance!
Click to expand...
Click to collapse
Use this Blu_Spark and it should work.
BTW, questions & troubleshooting issues belong in the Help section. A mod will move this thread there shortly.
Unn113 said:
You are probably encrypted, I think TWRP is not able to decrypt data yet.
Click to expand...
Click to collapse
The Blu_Spark above works with encryption for me. Just make sure lockscreen security is set to none or swipe before booting into recovery.
the Doctor said:
Use this Blu_Spark and it should work.
BTW, questions & troubleshooting issues belong in the Help section. A mod will move this thread there shortly.
The Blu_Spark above works with encryption for me. Just make sure lockscreen security is set to none or swipe before booting into recovery.
Click to expand...
Click to collapse
Yes, so it don't work fully, and it's better to either don't use security, (but what's the point of encryption if phone is not secure), or don't mess with risky stuff for now, till twrp bug gonna be fixed.
Sent from my OnePlus5T using XDA Labs
Either blu_spark or ibe recovery work. They also work with lockscreen security setup, no problems over here.
Unn113 said:
Yes, so it don't work fully, and it's better to either don't use security, (but what's the point of encryption if phone is not secure), or don't mess with risky stuff for now, till twrp bug gonna be fixed.
Click to expand...
Click to collapse
How do you figure? I've successfully backed up my previous ROM and flashed another one using that TWRP, my device is encrypted properly, I've reset lockscreen security, and my device passes SafetyNet.
Had the same issue. Flashing Blu_Spark worked perfectly. Thanks @the Doctor
help for twrp
TWrp message
message came to me
say
E: primary block device /dev/block/mmcb1kop8
for mount point /data is not present
failed to mount data
unable to create /data/media folder,
icant install rom and wipe data and now dont have any rom to open my device
please help me
I had this problem after installing TWRP 3.2.1-1. A new version was released last night (3.2.1-2) which I flashed this morning and seems to solve the problem. You can find the new version here.
I've downloaded the latest Android Pie stock image, however it seems that once I manual boot to TWRP 3.2.3, it causes the Android system UI to keep crashing. Any guesses on what's going on or what I'm doing wrong? I am flashing with the W removed.
Sent from my Pixel 2 XL using Tapatalk
brackett5 said:
I've downloaded the latest Android Pie stock image, however it seems that once I manual boot to TWRP 3.2.3, it causes the Android system UI to keep crashing. Any guesses on what's going on or what I'm doing wrong? I am flashing with the W removed.
Click to expand...
Click to collapse
So after you fastboot the factory image, and then fastboot into twrp you get a crash???
Reflash factory image but don't install TWRP. Do you still get crashes?
sublimaze said:
Reflash factory image but don't install TWRP. Do you still get crashes?
Click to expand...
Click to collapse
I fastboot into TWRP, backup my phone, rebooted back into system ( on accident) and all the sudden my system UI was broke.
Sent from my Pixel 2 XL using Tapatalk
brackett5 said:
I fastboot into TWRP, backup my phone, rebooted back into system ( on accident) and all the sudden my system UI was broke.
Click to expand...
Click to collapse
Go back to bone stock and don't install/fastboot TWRP, and see if you still get FCs.
sublimaze said:
Go back to bone stock and don't install/fastboot TWRP, and see if you still get FCs.
Click to expand...
Click to collapse
I already have and it works fine. Sorry, I should have mentioned that. I was wondering if it was the backing up process. It's happened twice now since backing up.
Sent from my Pixel 2 XL using Tapatalk
brackett5 said:
I already have and it works fine. Sorry, I should have mentioned that. I was wondering if it was the backing up process. It's happened twice now since backing up.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
You're backing up a fresh stock install? Is that correct?
Try flashing JUST the factory image, let it boot, boot into bootloader, fastboot into TWRP 3.2.2-0.IMG (previous version of TWRP), and see if you're still crashing.
Az Biker said:
You're backing up a fresh stock install? Is that correct?
Try flashing JUST the factory image, let it boot, boot into bootloader, fastboot into TWRP 3.2.2-0.IMG (previous version of TWRP), and see if you're still crashing.
Click to expand...
Click to collapse
That's what I mean by stock, I'm sorry. I've been installing the factory image (flash-all). I'll try the 3.2.2 when I get home
Sent from my Pixel 2 XL using Tapatalk
brackett5 said:
I already have and it works fine. Sorry, I should have mentioned that. I was wondering if it was the backing up process. It's happened twice now since backing up.
Click to expand...
Click to collapse
Are you using Titanium Backup or a similar 3rd party app to restore data? If you are restoring system data, especially across different versions of Android, that is likely the culprit.
TWRP does not modify any system data except the recovery files, so it should not affect system UI. I updated from Oreo to Pie by flashing the Pie factory image, then installed TWRP & Magisk in the same recovery session, and I have yet to experience any system UI errors. I know that doesn't really help your situation, but your it appears to be limited to your phone/setup.
sublimaze said:
Are you using Titanium Backup or a similar 3rd party app to restore data? If you are restoring system data, especially across different versions of Android, that is likely the culprit.
TWRP does not modify any system data except the recovery files, so it should not affect system UI. I updated from Oreo to Pie by flashing the Pie factory image, then installed TWRP & Magisk in the same recovery session, and I have yet to experience any system UI errors. I know that doesn't really help your situation, but your it appears to be limited to your phone/setup.
Click to expand...
Click to collapse
I honestly have not idea what was going on, but I installed twrp 3.2.2, Flash Kernel3.0.3, and the Magisk posted in your post all in the same session and it worked. Im lost, but im good now.
Thank you all.