For some reason when I try to backup my ROM with nandroid it says it can't mount /data or /system. I have /data encrypted and its not asking me for a password. I reflashed TWRP and CWM and I got the same error in CWM. I checked and write protection isn't on. Its a Dev Edition GSM. Anyone know how to fix it?
*Bump* help please
which version of TWRP are you using? which version of android?
beelzebu said:
which version of TWRP are you using? which version of android?
Click to expand...
Click to collapse
2.6.3.1. I'm on KitKat. I think TWRP can't mount encrypted /data
spyz88 said:
2.6.3.1. I'm on KitKat. I think TWRP can't mount encrypted /data
Click to expand...
Click to collapse
I'm having the same issue. I really hope we can find a way to make this work on the Moto X.
Is 2.6.3.1 officially from TWRP or is it something someone forked? Their site shows changes up to 2.6.3.0 only.
that is the correct recovery for 4.4 on any unlocked bootloader device.
only thing i can think of to try removing the encryption and try backing it up
i just ran a nandroid backup 2 days ago on 4.4 so i know it works
dray_jr said:
that is the correct recovery for 4.4 on any unlocked bootloader device.
only thing i can think of to try removing the encryption and try backing it up
i just ran a nandroid backup 2 days ago on 4.4 so i know it works
Click to expand...
Click to collapse
Yeah it works without encryption (removing it requires factory reset btw) but I want to be able to backup while encrypted. I know TWRP was able to mount encrypted partitions on the Nexus 4, I was hoping someone could help get that working on the Moto X.
fbiryujin said:
Yeah it works without encryption (removing it requires factory reset btw) but I want to be able to backup while encrypted. I know TWRP was able to mount encrypted partitions on the Nexus 4, I was hoping someone could help get that working on the Moto X.
Click to expand...
Click to collapse
that is something i didnt know i have never encrypted my data. i agree hopefully someone will but with little Dev support it could take awhile.
Related
I have a Moto X developer edition and I've been trying to OTA update to 139.15.1 but my phone fails with the error code 410. I found the Flashable zip and so I'm going to install it with that but for future installs how do I do it with the OTA. The phone failed both while rooted and while running a stock nandroid I made before rooting. With the stock nandroid the only thing modified was the unlocked bootloader. Yes I am using the stock recovery. Any help would be greatly appreciated.
Scoopta said:
I have a Moto X developer edition and I've been trying to OTA update to 139.15.1 but my phone fails with the error code 410. I found the Flashable zip and so I'm going to install it with that but for future installs how do I do it with the OTA. The phone failed both while rooted and while running a stock nandroid I made before rooting. With the stock nandroid the only thing modified was the unlocked bootloader. Yes I am using the stock recovery. Any help would be greatly appreciated.
Click to expand...
Click to collapse
there are threads out there already describing how to take the ota on a dev phone. But pure curiosity here, how in the hell are you making nandroid backups with stock recovery? I had noidea stock recovery allowed you to make those backups. I thought that was the point of other recoveries.
jayboyyyy said:
there are threads out there already describing how to take the ota on a dev phone. But pure curiosity here, how in the hell are you making nandroid backups with stock recovery? I had noidea stock recovery allowed you to make those backups. I thought that was the point of other recoveries.
Click to expand...
Click to collapse
It isn't possible to make a nandroid backup with a stock recovery. I meant I reflashed the stock recovery after making the backup. Anyway it is possible to make a backup that includes your stock recovery by using the fastboot boot command to boot to a recovery over usb rather than flashing it to your recovery partition.
Scoopta said:
It isn't possible to make a nandroid backup with a stock recovery. I meant I reflashed the stock recovery after making the backup. Anyway it is possible to make a backup that includes your stock recovery by using the fastboot boot command to boot to a recovery over usb rather than flashing it to your recovery partition.
Click to expand...
Click to collapse
interesting. Still wouldn't expect the OTA to work if you booted that way though. The OTA would be checking the files on the phone not the files from the usb that are running the phone. I wouldn't think. But I could be really confused on what you just said. Either way, there are several threads on the matter that should adequately answer all your needs.
jayboyyyy said:
interesting. Still wouldn't expect the OTA to work if you booted that way though. The OTA would be checking the files on the phone not the files from the usb that are running the phone. I wouldn't think. But I could be really confused on what you just said. Either way, there are several threads on the matter that should adequately answer all your needs.
Click to expand...
Click to collapse
Yes it would appear you are confused on what I just said. Anyway I guess I'll browse around to find instructions on how to take an OTA for the next time there's an OTA released.
Scoopta said:
Yes it would appear you are confused on what I just said. Anyway I guess I'll browse around to find instructions on how to take an OTA for the next time there's an OTA released.
Click to expand...
Click to collapse
i get what you were saying now. I thought you were saying that you were booting your phone from a usb drive that had the stock recovery on it so you could see if the OTA would take on your phone. Anyway, I dont' remember all of the steps that people were taking but it was pretty simplistic.
jayboyyyy said:
i get what you were saying now. I thought you were saying that you were booting your phone from a usb drive that had the stock recovery on it so you could see if the OTA would take on your phone. Anyway, I dont' remember all of the steps that people were taking but it was pretty simplistic.
Click to expand...
Click to collapse
ok...thanks for the info. I'll see if I can find a thread on it.
I accidentally deleted my /system partition in TWRP, so I would appreciate if someone who have Brazilain Retail XT1058 with 4.4.3 and had NOT MODIFIED /system previously could make a TWRP backup of JUST the /system partition for me. Once the SBF has not leaked yet, this is the only way I can put my Moto X running flawlessly again.
Thanks in advance!
Guilhermewpds said:
I accidentally deleted my /system partition in TWRP, so I would appreciate if someone who have Brazilain Retail XT1058 with 4.4.3 and had NOT MODIFIED /system previously could make a TWRP backup of JUST the /system partition for me. Once the SBF has not leaked yet, this is the only way I can put my Moto X running flawlessly again.
Thanks in advance!
Click to expand...
Click to collapse
BUMP! Do we have any users with the Brazil Retail XT1058 (on 4.4.3) that would help @Guilhermewpds out?
He is "stuck" so-to-speak until someone uploads a TWRP backup of the /system partition. It isn't hard to do, and since you are JUST making a backup of /system, you won't be sharing any personal data.
Just boot to TWRP recovery, click BACKUP, Uncheck everything except "System". Then upload it somewhere and he can get his phone fully working again I'm SURE he will give you some "Thanks" for it, and be forever grateful... :good:
I have the Brazilian 4.4.3 but have xposed installed, so I guess I can't help you there. Anybody else?
I finally got it in a brazilian forum. Thank you for those who tried to help! I think the moderators can close this thread since the problem was solved.
Guilhermewpds said:
I finally got it in a brazilian forum. Thank you for those who tried to help! I think the moderators can close this thread since the problem was solved.
Click to expand...
Click to collapse
Good night, Guilherme.
Can you show me this brazilian forum? The wi-fi on my moto x won't turn on. I need this files to fix this!
Will we need to backup are EFS partition like the N5?
dirtbikerr450 said:
Will we need to backup are EFS partition like the N5?
Click to expand...
Click to collapse
I'd say yes, but it's personal preference really. If you'd happen to lose your EFS, then you're screwed because it contains your IMEI, MAC Address, Wifi MAC Address, etc...
If you flash a lot of ROMs I would say yes, but if you flash zero ROMs or very few, then I would say it's not totally necessary. It only takes one bad flash to ruin your EFS.
No one replied so I figured, why not?
StrifeSoldierVII said:
I'd say yes, but it's personal preference really. If you'd happen to lose your EFS, then you're screwed because it contains your IMEI, MAC Address, Wifi MAC Address, etc...
If you flash a lot of ROMs I would say yes, but if you flash zero ROMs or very few, then I would say it's not totally necessary. It only takes one bad flash to ruin your EFS.
No one replied so I figured, why not?
Click to expand...
Click to collapse
How does one go about backing up that partition?
elevatorguy said:
How does one go about backing up that partition?
Click to expand...
Click to collapse
A custom recovery like TWRP.
mwalt2 said:
A custom recovery like TWRP.
Click to expand...
Click to collapse
OK thanks. Would assume it's somewhere in an advanced setting somewhere? Don't remember seeing it in the regular backup part
elevatorguy said:
OK thanks. Would assume it's somewhere in an advanced setting somewhere? Don't remember seeing it in the regular backup part
Click to expand...
Click to collapse
Just do a regular Nandroid backup in recovery via TWRP and there is a check box for the EFS partition. Check it along with anything else you might want to back up at the time. Make sure you are on the latest TWRP version, otherwise you may not have this option.
StrifeSoldierVII said:
Just do a regular Nandroid backup in recovery via TWRP and there is a check box for the EFS partition. Check it along with anything else you might want to back up at the time. Make sure you are on the latest TWRP version, otherwise you may not have this option.
Click to expand...
Click to collapse
Thanks for the education. Will back it up now ?
elevatorguy said:
Thanks for the education. Will back it up now ?
Click to expand...
Click to collapse
Not a problem. Sucks that you didn't get an answer until now though.
StrifeSoldierVII said:
Not a problem. Sucks that you didn't get an answer until now though.
Click to expand...
Click to collapse
I wasn't the one who originally asked the question I just saw something about needing to backup something. I'm kinda paranoid about backing things up. Few more things to ask. Do you back EFS up with every nandroid and just restore it with everything else, or do you keep a copy of just the EFS itself and restore it separately if something messes up?
elevatorguy said:
I wasn't the one who originally asked the question I just saw something about needing to backup something. I'm kinda paranoid about backing things up. Few more things to ask. Do you back EFS up with every nandroid and just restore it with everything else, or do you keep a copy of just the EFS itself and restore it separately if something messes up?
Click to expand...
Click to collapse
I do a one time back of of just the EFS for each major android update, then erase the older version.
Like right now I have the efs backup for 5.0.2. When 5.1 comes to play I will back that up and then delete the 5.0.2. Just my preference
the_rooter said:
I do a one time back of of just the EFS for each major android update, then erase the older version.
Like right now I have the efs backup for 5.0.2. When 5.1 comes to play I will back that up and then delete the 5.0.2. Just my preference
Click to expand...
Click to collapse
One more question. Can you make a backup of just the EFS partition and restore just that partition or do you have to restore a complete nandroid of the whole system? Thanks I'm sure this is all basic stuff to you but I seem to learn something new every day.
elevatorguy said:
One more question. Can you make a backup of just the EFS partition and restore just that partition or do you have to restore a complete nandroid of the whole system? Thanks I'm sure this is all basic stuff to you but I seem to learn something new every day.
Click to expand...
Click to collapse
I do just do the efs partition
the_rooter said:
I do just do the efs partition
Click to expand...
Click to collapse
OK thanks. I'll make a copy of just that. Guess that means you can just restore that alone.
Hi everyone! I am a newby here. I just want the Efs backup from TWRP of 6.0 Marshmallow
Please anyone upload it. Thanks.
I'm sorry, but you can't use someone else's.
Sent from my Nexus 6 running cyosp using Tapatalk
I'm having some problems with wifi/bluetooth mac address and want to try to format efs partition and then restore it
already have an efs backup made with TWRP but couldn't find the option to format that partition in order to fix any possible FS error.
Did you know how?
I can no longer write any custom roms to my N6. Started with PURE 3.5 but now effects any rom i try to flash. I have brought my N6 back to factory state multiple times even relocking it. Only thing I can do is Fastboot flash N6 image from google manually piece by piece. I do have working 5.01 and phone works. Roms either hang or have errors. or just write the boot.img file. TWRP works other wise i can backup and restore, I am using 2.8.3.1. I have searched all over for a fix....
There used to be some weird mounting stuff that would make roms not boot. Thought that was worked out in pure shamu 3.1 ish.
Where do the roms hang? Did you ever fix permissions using twrp? Any kind of log you can pull?
dipstik said:
There used to be some weird mounting stuff that would make roms not boot. Thought that was worked out in pure shamu 3.1 ish.
Where do the roms hang? Did you ever fix permissions using twrp? Any kind of log you can pull?
Click to expand...
Click to collapse
I had no problem updating Pure for over a month from like 2.0 to 3.4.
they all hang when writing to system as far as i can tell. happens regardless of Pure....from a fresh clean image of 5.0 or 5.01 i can not flash any roms. driving me nutzo....i can no longer flash pure 3.4 either but i can restore the phone from a nandroid backup i had on my pc and run Pure 3.4 just fine.
Did you wipe everything except internal storage first? I had this issue earlier until I realized that I forgot to do that when coming from the stock ROM.
Pilz said:
Did you wipe everything except internal storage first? I had this issue earlier until I realized that I forgot to do that when coming from the stock ROM.
Click to expand...
Click to collapse
yes and both cache.....
also made sure system not mounted.
very frustrating.
Bignoze73 said:
yes and both cache.....
also made sure system not mounted.
very frustrating.
Click to expand...
Click to collapse
That is very odd, did you try reflashing TWRP or using a different version.
Pilz said:
That is very odd, did you try reflashing TWRP or using a different version.
Click to expand...
Click to collapse
mutiple times......tried all versions of TWRP too.
I can write a custom kernal like elementalx no problem.....just not roms.
Bignoze73 said:
mutiple times......tried all versions of TWRP too.
Click to expand...
Click to collapse
It doesn't make sense considering you also flashed back to stock. Have you also tried to flash a ROM from your PC rather than from your phone? There has to be some reasonable explanation for why it's not working.
Pilz said:
It doesn't make sense considering you also flashed back to stock. Have you also tried to flash a ROM from your PC rather than from your phone? There has to be some reasonable explanation for why it's not working.
Click to expand...
Click to collapse
how do you do that? the custom roms dont have system.img file like N6 image. The Pure 3.92 is in .dat format, another rom is folders. I also get checksum errors when extracting.
I also noticed in the last 24 hours there are 2 other threads with people have almost the same issues flashing roms. I think it has something to do with TWRP but no matter becuase no version works for me.
Bignoze73 said:
how do you do that? the custom roms dont have system.img file like N6 image. The Pure 3.92 is in .dat format, another rom is folders. I also get checksum errors when extracting.
I also noticed in the last 24 hours there are 2 other threads with people have almost the same issues flashing roms. I think it has something to do with TWRP but no matter becuase no version works for me.
Click to expand...
Click to collapse
If you restore your stock recovery on your phone you could try this.
Make sure TWRP is not installed on your phone and that the stock recovery is installed and working:
Have TWRP in your platform tools folder named however you want
Then use "fastboot boot recovery 'whatever you named TWRP' "
This will boot TWRP without installed it. Then try to flash the ROM using TWRP. You can also use the"adb push" to sideload the ROM onto your phone so you can find it via TWRP.
nope did not work.....roms just hang or flash new boot.img only.
i even tried erasing recovery partion and reflashing stock than twrp 2.8.3.1......that did not work either....something is stopping TWRP from writing to system.
thanks for your help
Bignoze73 said:
nope did not work.....roms just hang or flash new boot.img only.
i even tried erasing recovery partion and reflashing stock than twrp 2.8.3.1......that did not work either....something is stopping TWRP from writing to system.
thanks for your help
Click to expand...
Click to collapse
You're welcome, have you tried to contact some of the devs here to see if maybe they could help? I think the worst case scenario would be to RMA the phone.
Pilz said:
You're welcome, have you tried to contact some of the devs here to see if maybe they could help? I think the worst case scenario would be to RMA the phone.
Click to expand...
Click to collapse
RMA the phone??? ?What are you gonna tell them?? ? That you can't flash any custom Roms through TWRP?? ?
laureanop said:
RMA the phone??? ?What are you gonna tell them?? ? That you can't flash any custom Roms through TWRP?? ?
Click to expand...
Click to collapse
No obviously not look, but if you have other issues (in assuming you might if you can't flash a ROM) then that's the worst case scenario option.
Pilz said:
No obviously not look, but if you have other issues (in assuming you might if you can't flash a ROM) then that's the worst case scenario option.
Click to expand...
Click to collapse
This is a tough one cause if his factory image works without issues they're gonna have no reason to send him a replacement
laureanop said:
This is a tough one cause if his factory image works without issues they're gonna have no reason to send him a replacement
Click to expand...
Click to collapse
That's true, but there must be something wrong if he can't flash anything else so I'm sure he could find some issues.
Pilz said:
That's true, but there must be something wrong if he can't flash anything else so I'm sure he could find some issues.
Click to expand...
Click to collapse
Is there a tool or command to do a full memcheck of both ram and storage
rgraville said:
Is there a tool or command to do a full memcheck of both ram and storage
Click to expand...
Click to collapse
I'm not sure I've never had the need to do one from adb or fastboot
Pilz said:
I'm not sure I've never had the need to do one from adb or fastboot
Click to expand...
Click to collapse
yeah its pretty nuts....how can I return a phone that works fine other than the fact it wont flash a custom rom?
Must be another way to write a rom but TWRP......
thanks!
Bignoze73 said:
yeah its pretty nuts....how can I return a phone that works fine other than the fact it wont flash a custom rom?
Must be another way to write a rom but TWRP......
thanks!
Click to expand...
Click to collapse
I assume you are also out of the return window. Well if you are unlucky or lucky (depending on how you view it) you could have an issue eventually. They will RMA for burn in, camera issues etc... The camera issue was common in the earlier production models that I had. There should be another method, I would look into it if you have time.
Is anybody else facing extremely long wait times before TWRP boots up completely? Even my Galaxy S3 can load TWRP faster than my 3T can. Somebody please help me out here. :crying:
Saamyo said:
Is anybody else facing extremely long wait times before TWRP boots up completely? Even my Galaxy S3 can load TWRP faster than my 3T can. Somebody please help me out here. :crying:
Click to expand...
Click to collapse
Yes ,very long
f2fs or ext4? Did you read TWRP official thread about this issue?
Saamyo said:
Is anybody else facing extremely long wait times before TWRP boots up completely? Even my Galaxy S3 can load TWRP faster than my 3T can. Somebody please help me out here. :crying:
Click to expand...
Click to collapse
If u want a faster TWRP boot, format data to ext4..I had the same issue..after changing the data partition TWRP loads faster...and there is no significant change in performance..
tvakshaykumar said:
If u want a faster TWRP boot, format data to ext4..I had the same issue..after changing the data partition TWRP loads faster...and there is no significant change in performance..
Click to expand...
Click to collapse
Will I lose my data if I change the format of /data/?
Saamyo said:
Will I lose my data if I change the format of /data/?
Click to expand...
Click to collapse
Yes, take a titanium backup of apps and data first
tvakshaykumar said:
Yes, take a titanium backup of apps and data first
Click to expand...
Click to collapse
Oh ok. Thank you
Another question: will changing the format cause ROM incompatibilities or such?
Saamyo said:
Oh ok. Thank you
Another question: will changing the format cause ROM incompatibilities or such?
Click to expand...
Click to collapse
Ext4 is compatible with most of the roms and kernels
Saamyo said:
Oh ok. Thank you
Another question: will changing the format cause ROM incompatibilities or such?
Click to expand...
Click to collapse
No, quite the opposite since ext4 is the default filesystem on pretty much all Android devices, while Samsungs f2fs is not supported by every kernel/ROM as it has its disadvantages.
Isn't TWRP's slow loading due to decryption?
the-blind-bandit said:
Isn't TWRP's slow loading due to decryption?
Click to expand...
Click to collapse
No, it's because of a bug/side-effect of f2fs that's making it excruciatingly slow to boot twrp. However encryption does make it a little slower to boot twrp even with ext4 filesystem, just not as much.
tvakshaykumar said:
Yes, take a titanium backup of apps and data first
Click to expand...
Click to collapse
Titanium backup wont help i think because changing file system will wipe titanium backup files too..
Unless he back ups them to pc which is worth mentioning
Correct me if im wrong
This is a standard procedure.
Always to keep a copy of tibu backup files on the cloud or at an external disk.
Unleashed by ONEPLUS 3T rooted
agosto 2019.
I found slow twrp also in version 3.3
modified for the latest build of my XZ3.
Now I look for some guide to pass recovery to Ext4, correctly.