[Q] Issue upgrading from CM9-stable to CM10-nightly + encrypted /data - Asus Eee Pad Transformer Prime

Hi,
Well, I guess I did a nice one...
My TF201 is unlocked, with TWRP v 5.8.3.4 as recovery. I was running so far CM9-stable RC. Please note my /data folder is encrypted using Asus inbuilt tool and I already experienced issue with it previously.
Unfortunately I faced a lot of crashes using CM9 (even following cache cleaning, removing Apps, and so on). Therefore I decided to give CM10-nightly build (v. 20130310) a try.
I first made a nanodroid backup of the whole system using TWRP ; on my internal SDCard. And I did not get this specific backup on any other support.
Downloaded all the stuff (CM10-nightly + GoogleApps) on my internal SDCard and... let's go :
1 – Using TWRP : first decrypt /data at startup → OK
2 – Using TWRP : factory reset + wipe dalvik cache → OK
3 – Using TWRP : install CM10.zip + GoogleApps.zip from the (decrypted) SDCard → OK
4 – Reboot : get stuck on CM10 splash screen (I tried to reboot several time without any success)
5 – Reboot, and great idea, reboot to bootloaded mode (vol. Down key pressed) and... “wipe data” →... OK (Step 5 was done without giving my password to decrypt /data just 'cause it has just never been asked !! And I guess I was tired...)
6 – Finally, CM 10... well... “running”
From now on, I am able to access CM10, but :
- CM10 does not ask me for my PIN during startup in order to decrypt /data (CM9 used to do it)
- (of course) CM10 can not access /data or internal SDCard
- At least but not last... I can not anymore access my SDCard from TWRP (my pass is not recognized anymore). Meaning I can not access my Nandroid backup
My guess is
I- I formated /data in step 5
II- ...but I therefore destroyed all data
III- ...including the passkey...
Any help would be (more) than welcome! I still have an ADB access to the Prime, but I do not want to make anymore (stupid) mistake
(And I confessed, I am more used to Linux system than Android.)
Regards

Stupid thing, stupid solution...
Used TWRP to format /data (this app deals pretty well with encryption by the way!) > OK
Reboot to CM 10 just to be sure > much better!
Put Gapps on the SD card, now readable > reboot to recovery
Using TWRP, format cache and Install Gapps from the internal SD (couldn't be install at the first attempt as /data was encrypted andtherfore unmounted)
Reboot, and now CM10 rolls!
What I have learned:
Always backup data before to start (my TF201 is sync on Google servers)
Backup your ROM before to start (Ok, I did it... but)
Better, back it up on AN EXTERNAL media (or backup the backup...)
Read, read, and read AND backup, backup, backup...

Related

Apps/Games Problem

recently i have been having issues with my games and apps that are installed in my phone.........all of them say ether "application not installed" or the force close messege while the day before all was ok... so what can cause this issue
Have you made any changes to you phone recently, tweaked, anything...? Or did it just happen suddenly?
ivanrcks95 said:
recently i have been having issues with my games and apps that are installed in my phone.........all of them say ether "application not installed" or the force close messege while the day before all was ok... so what can cause this issue
Click to expand...
Click to collapse
Hi @ivanrcks95...
After reading your post I sat & scratched my head for a while...
1. do you have any apps etc moved-out to sd...? If so, are there many & what app did you use to move them...?
2. Are you running any ram tweaks or partition managment tweaks...?
The reason I ask these questions is because I have seen this behaviour often when an "Ace" is switching back from USB data transfer mode to Internal & SD memory...
The status of your ram at this point can cause a severe lag with the mounting of the necessary partitions often returning the error messages that you describe... on occasion you will also get "Problem loading widgets" etc. If a particularly bad lag occurs then the data & partitions can become corrupted...
An easy cure to get things running again would be a complete wipe & restore from Nandroid backup (assuming that you have done one...?)... A selective nandroid restore would let you just repair the system partition, which I feel would be adequate.
Have you tried re-installing 1 or 2 apps...? if they install successfully then that tells us that the partition is now functioning but some of the data contained has become corrupt. If the apps fail to install then I think we can safely assume that the partition is corrupt...
Again the simple solution would be a nandroid restore... If you do not have this option then I would suggest the following... :
1. backup all data from your sd card where possible & reformat & partition using CWM 4 or 5 (if ya runnin CM7.2 then you "MUST" use CWM5)...(sd card partitions may be cause of issue)
2. complete a full wipe (system, cache, Dalvik), Wipe battery stats (Always do when installing a new rom so battery can correctly callibrate to new power requirments)...
3. Re-flash rom, modded kernel etc. (always check if system, data partitions need to be mounted before flash from CWM to prevent boot errors & wrong permission assignment)...
4. Re-boot phone after flash to check all is well... Then copy back to sd the backup that you made at the beginning...
You should now have a fully working phone again... Downside is that you may have to re-install ya apps etc...
Nandroid backup recovery...
======================
1. Follow step 1 of my guide above...
2. If doing a "selective" nandroid restore then wipe just the Dalvik cache then just select the needed files and restore them... If doing a "Complete" nandroid restore then do a complete wipe before restore...
3. Re-boot phone after restore to check all is well... Then copy back to sd the backup that you made at the beginning...
You should now have a fully working phone again...
!!! IMPORTANT !!!
==============
If after formatting & partitioning the sd card, CWM has trouble locating the Nandroid backup after you place it in root of sd card then do the following :
1. Open into "Root" of sd card
2. Create a folder called "clockworkmod" all lowercase letters...
3.Create within the above folder another folder called "backup" again all lowercase...
4. now place within this folder your nandroid backup...
5. unmount usb (assuming your phone is connected to pc for folder creation)...
6. now complete the nandroid recovery...(should go without a hitch unless the backup has been altered in any way (MD5 hash file check will fail if file is altered after creation)...
Hope this info is of help to you given that you did;nt really provide many details of your problem...
Stay Breezy n Be Lucky...
Pe"ACE"...
ok i am running my own ROM that i havent published but its a mix with cyanogen and ice cream sunday put into one( so some bits from each rom to make my own) well when i re-install apps they work but ive noticed as soon as i reboot my phone they force close again i can try to reinstall my rom and do a full wipe to solve this but all my apps are in my sd card so it could be that my sd card is a bit mest up or maybe ive mest something up with my rom

[Q] Dummy needs help! In TWRP recovery with all partitions formatted...

I'm sure I qualify for some sort of noob trophy. Having said that, here's my situation: My DNA is rooted w/S-Off, TWRP v2.6.1.0. I have run most of the sense 4 and 5 roms and briefly Newt's GPE v1.0.4. I wanted to flash the official cyanogenmod 10.2. I downloaded the rom and gapps zips and then booted into recovery. From the wipe menu, I did factory reset and advanced wipe of cache, dalvik, and system. Prior to flashing the new rom, I had to step away from the process to help with the kids. When I returned to my DNA, I remembered that I wanted to eliminate the duplicate storage between /data/media and /sdcard that was eating up all my internal storage. As you can likely now guess, my [email protected]$$ formatted the data partition to wipe the sdcard without having ever flashed the rom! I'm now left sitting in recovery with an empty phone. I have my TWRP backups saved on my Windows 7 cpu. What's the SIMPLIEST method to either get one of my backups or a rom.zip onto my sdcard? I thank you in advance for anyone willing to help me out!
raknarc said:
I'm sure I qualify for some sort of noob trophy. Having said that, here's my situation: My DNA is rooted w/S-Off, TWRP v2.6.1.0. I have run most of the sense 4 and 5 roms and briefly Newt's GPE v1.0.4. I wanted to flash the official cyanogenmod 10.2. I downloaded the rom and gapps zips and then booted into recovery. From the wipe menu, I did factory reset and advanced wipe of cache, dalvik, and system. Prior to flashing the new rom, I had to step away from the process to help with the kids. When I returned to my DNA, I remembered that I wanted to eliminate the duplicate storage between /data/media and /sdcard that was eating up all my internal storage. As you can likely now guess, my [email protected]$$ formatted the data partition to wipe the sdcard without having ever flashed the rom! I'm now left sitting in recovery with an empty phone. I have my TWRP backups saved on my Windows 7 cpu. What's the SIMPLIEST method to either get one of my backups or a rom.zip onto my sdcard? I thank you in advance for anyone willing to help me out!
Click to expand...
Click to collapse
Step 0: boot to recovery
Step 1: adb devices //if it isn't detected: Advanced > adb sideload > adb devices again > cancel sideload
Step 2.1 TWRP backup option: adb push <directory of TWRP backup, without "<>"> /sdcard/TWRP/BACKUPS/
Step 2.2: New ROM option: adb push <rom directory> /sdcard/ // you may also need do do this for gapps
Step 3: Restore backup or flash ROM
Thanks, Walther! I wasn't able to get the backup to push, but I had the Tranquil Rom zip on cpu as well and I did successfully push it over to my DNA. It's booted and setting up as I type this. I'll hook up to cpu, when done, and transfer the backup to sdcard. Then, maybe, I'll be able to restore back to where I was before I borked everything up.
Thanks again!
Hi!
Fine, for me am from Kampala but my home district is Busujju, Uganda.
Serwaniko Kenneth

[Q] Boot loop to ClockworkMod Recovery. Possible brick?

I think I did something stupid.
I wanted to install a new ROM (OmniROM) and wanted a fresh device.
So I went into ClockworkMod Recovery v6.0.2.2 and went to the "Mounts and Storage" menu.
Here I did a format of all the storage available (except /external_sd)
To sum it up:
- format /cache
- format /system
- format /data
- format /preload
- format /sdcard
- format /data and /data/media
After this I went on and tried to install OmniRom. But I receive an "Installation aborted" error.
When I try to reboot the device it tells me:
Root access possibly lost. Fix? THIS CAN NOT BE ONDONE.
- No
- Yes - Fix root (/system/xbin/su)
- +++++Go Back+++++
I tried installing an other ROM (ArchiDroid 2.3) This installation process starts and I get through the wizard.
But the device keeps booting to ClockworkMod Recovery..
I'm having the feeling I ****ed up and deleted some necessary system files.
Is there a way to fix this brick?
I appreciate any help!
Managed to fix it.
I still had a full CWM backup from when I first rooted the phone. (1,5 year ago)
It was like a trip back in time

[FIX] How to solve "unable to mount data" error

Hey,
recently many are facing the problem to suddenly receive the above error and aren't able to solve it by formatting data (well, it cannot be mounted).
Here are the steps that I suggest in case you find yourself in that situation (obviously all data including internal storage content will be gone afterwards, so make external backups of important stuff if you can before continuing)
- (re-)flash lastest twrp (currently 3.2.1.1) via fastboot
- boot to recovery
- wipe dalvik, cache, vendor, system, data
- format data (the one where you need to type "yes")
- reboot to recovery before flashing anything
- now flash your stuff
This helped a few people already, but please comment if it also does (or doesn't) for you!
Cheers and greetings,
Phil the Thrill
I had this problem, but not always just formatting helps. First time when I install LOS 15.1 I didn't format internal storage then LOS crypt my storage and TWRP couldn't mount it and I can't just format it, I have error when I try to format it in ext4 by default. Then I try to format it to another file system and select ext2. TWRP succesful format data and then I select again to format it to ext4 and install other rom. I don't know why first time TWRP couldn't format data.
I use google translate. Sorry if I have misspellings
aleksandar9999a said:
I had this problem, but not always just formatting helps. First time when I install LOS 15.1 I didn't format internal storage then LOS crypt my storage and TWRP couldn't mount it and I can't just format it, I have error when I try to format it in ext4 by default. Then I try to format it to another file system and select ext2. TWRP succesful format data and then I select again to format it to ext4 and install other rom. I don't know why first time TWRP couldn't format data.
I use google translate. Sorry if I have misspellings
Click to expand...
Click to collapse
I didn't just suggest to format anything...
The important thing is to reflash twrp via fastboot.
The point is that after doing this you might even be able at all again to format data...
If you follow the further steps I think you're good to go and don't need to change any file system.
Phil_Smith said:
Hey,
recently many are facing the problem to suddenly receive the above error and aren't able to solve it by formatting data (well, it cannot be mounted).
Here are the steps that I suggest in case you find yourself in that situation (obviously all data including internal storage content will be gone afterwards, so make external backups of important stuff if you can before continuing)
- (re-)flash lastest twrp (currently 3.2.1.1) via fastboot
- boot to recovery
- wipe dalvik, cache, vendor, system, data
- format data (the one where you need to type "yes")
- reboot to recovery before flashing anything
- now flash your stuff
This helped a few people already, but please comment if it also does (or doesn't) for you!
Cheers and greetings,
Phil the Thrill
Click to expand...
Click to collapse
Thats because maybe on a backup you select another storage that nota the internal storage....maybe you select otg storage ir something....put the selection on Internal storage....and it resolves
I've same problem in my redmi note 4 (mido). I tried the same but it not works.
After update of resurrection remix oreo (30-05-2018), I unable to install any zip through twrp.It shows "unable to mount /vendor". I also search for vendor partition in mount menu but I cant found any options for it.
If you found any solution plz tell me......... thanks
Stonner_99 said:
I've same problem in my redmi note 4 (mido). I tried the same but it not works.
After update of resurrection remix oreo (30-05-2018), I unable to install any zip through twrp.It shows "unable to mount /vendor". I also search for vendor partition in mount menu but I cant found any options for it.
If you found any solution plz tell me......... thanks
Click to expand...
Click to collapse
me either, my problem. RRD. pls anyhelp?
Hutabarat said:
me either, my problem. RRD. pls anyhelp?
Click to expand...
Click to collapse
Hi, I had the same problem. (Redmi Note 4, Mido)
But after installing RedWolf (Build 27)
with adb/fastboot and everything works fine - without formating everything.
This maybe can help,
first i enter wipe menu on twrp and advanced wipe, mark data partition then repair or change file system, after that change file system, change to what ever except ext4 (i use ext2 one) then change again to ext 4. Done you get data partition back
*this method will wipe your data on that partition
solution about unable to mount data on s7 edge
Hi,
Make sure to do a backup of your data, all data will be erased
after many attempts to find the solution
i tried to go to recovery latest twrp:
go to wipe
select data
for me i choosed ext3 and make repair
than i select Fat and again ext3
you can choose another file system
Thank you
Thanks this worked for me
This is the best answer to solve the problem:
CHoozen said:
This maybe can help,
first i enter wipe menu on twrp and advanced wipe, mark data partition then repair or change file system, after that change file system, change to what ever except ext4 (i use ext2 one) then change again to ext 4. Done you get data partition back
*this method will wipe your data on that partition
Click to expand...
Click to collapse
This worked for me.
- (re-)flash lastest twrp (currently 3.2.1.1) via fastboot
- boot to recovery
- wipe dalvik, cache, vendor, system, data
- format data (the one where you need to type "yes")
- reboot to recovery before flashing anything
- now flash your stuff
I was in Xiaomi.EU 9.3.28 in a "encrypted storage" situation
After messing it up I endend in a situation where I can not mount the data partition.
Follow your steps and now I'm setting up xiaomi.eu 9.5.9 without a problem.
Thank you very much.
Wachuwey said:
This worked for me.
- (re-)flash lastest twrp (currently 3.2.1.1) via fastboot
- boot to recovery
- wipe dalvik, cache, vendor, system, data
- format data (the one where you need to type "yes")
- reboot to recovery before flashing anything
- now flash your stuff
I was in Xiaomi.EU 9.3.28 in a "encrypted storage" situation
After messing it up I endend in a situation where I can not mount the data partition.
Follow your steps and now I'm setting up xiaomi.eu 9.5.9 without a problem.
Thank you very much.
Click to expand...
Click to collapse
Thanks to you I was able to recover my wife's Redmi 5. Cheers :good:
could not mount data and unable to find crypto error
Good morning guys im using Xiaomi Redmi note 4x(mido) i installed LineageOS 15.1 then the gapps, but the google photos and other google apps keep crashing and recommended me to uninstall and install again. so i wen to twrp and installed the gapps again, then it keeps crashing again. so what i did is to wipe in twrp then installed linneage and the gapps but when rebooting it asked my password then after than i can't no longer boot it keep sayingf could not mount/data and unable to find crypto. i tried all the steps and fix i found here and in other sites but it does not work when i try changing it to other file system it says mke2fs -t ext3 -b 4096 /dev/block/mmcblk0p49, and error 64. Please help thank you
Still not able to mount storage.
Phil_Smith said:
Hey,
recently many are facing the problem to suddenly receive the above error and aren't able to solve it by formatting data (well, it cannot be mounted).
Here are the steps that I suggest in case you find yourself in that situation (obviously all data including internal storage content will be gone afterwards, so make external backups of important stuff if you can before continuing)
- (re-)flash lastest twrp (currently 3.2.1.1) via fastboot
- boot to recovery
- wipe dalvik, cache, vendor, system, data
- format data (the one where you need to type "yes")
- reboot to recovery before flashing anything
- now flash your stuff
This helped a few people already, but please comment if it also does (or doesn't) for you!
Cheers and greetings,
Phil the Thrill
Click to expand...
Click to collapse
I tried everything that is:
-changing file system also gives "unable to mount storage " in every format like fat, ext2, ext3, ext4.
-factory reset also gives same error "unable to mount storage"
-I also tried different recovery.
Please someone help me!!!
Wachuwey said:
This worked for me.
- (re-)flash lastest twrp (currently 3.2.1.1) via fastboot
- boot to recovery
- wipe dalvik, cache, vendor, system, data
- format data (the one where you need to type "yes")
- reboot to recovery before flashing anything
- now flash your stuff
I was in Xiaomi.EU 9.3.28 in a "encrypted storage" situation
After messing it up I endend in a situation where I can not mount the data partition.
Follow your steps and now I'm setting up xiaomi.eu 9.5.9 without a problem.
Thank you very much.
Click to expand...
Click to collapse
Format data solved everything. But before format data, you better backup all your files. Because all of it will be erased like new.
Thank you.
CHoozen said:
This maybe can help,
first i enter wipe menu on twrp and advanced wipe, mark data partition then repair or change file system, after that change file system, change to what ever except ext4 (i use ext2 one) then change again to ext 4. Done you get data partition back
*this method will wipe your data on that partition
Click to expand...
Click to collapse
I LOVE YOU!!! U saved me when nothing worked. Ty so much !!
Hey King,
I do not use a Redmi Note 8, yet I had the same problem with my Moto G5 Plus.
Until I read your post and now my phone works.
Thank you!
Hi, i have TWRP 3.6.0 installed on my mi 11 lite (courbet), and then it shows "unable to mount /data". I know, formatting helps, but what to do if i don't want to format it, only i want to update the rom?

TWRP unable to mount memory even after wipe

Hi,
I have a Xiaomi Redmi Note 5A, and I installed TWRP and Magisk on it 6 months ago, and all was working fine until the last update of MIUI that was installed just yesterday. After that, Magisk had no more root access and TWRP was no more here. At this point I flashed again TWRP with ADB, and after rebooting on recovery, TWRP launched but it was unable to mount any memory, so I could not flash any file. After several tries and researchs on forum I ended up to wipe memory (also changing format file from EXT4 to EXT2 then back to EXT4). After that TWRP sees effectively the memory but I can't still flash any file as I just wiped memory. So I have to reboot on system to put files on the memory: doing that I have first all the different screens steps to setup MIUI from scratch. When all the phone is configured, I reboot in fastboot to flash again TWRP, then I reboot on recovery, and again TWRP is unable to mount memory. I tried this several times and tried many other things (removing the patern lock, setting just a PIN...) but nothing worked so far after several hours searching...
If anyone could help, I would really appreciate it. Thanks in advance!
Ok, I finally solved it. Here is what I have done:
First I strictly followed instructions from this tutorial:
Fix Unable To Mount Storage TWRP: If you are trying to factory reset your device using twrp recovery and it’s displaying unable to must data then follow the below instructions.
First off all remove pattern lock from device and add PIN lock/password as a security lock as shown in above method.
Still getting “unable to mount storage twrp error” then go to main menu of twrp recovery.
Click on “WIPE” option >> “Advance Wipe” >> select “Cache” >>click on “Repair or Change File System” >> “Change File System” >> click “F2Fs” and “swipe to Change”
Again Go back and select >> “EXT4” option >> “Swipe To Change”
Now repeat the same process with “System” option and “Data” option one by one.
After doing that you are free to wipe or factory reset your device without any TWRP error. This time it will not show the unable to mount storage in TWRP recovery.
Click to expand...
Click to collapse
Note that it wiped everything even OS.
So I downloaded the latest official ROM from MIUI website, and I copied the file to the phone with USB mass storage mode (still being in TWRP). I also put the LazyFlasher zip and Magisk zip. Then I installed the 3 zips at the same time, ROM first, LazyFlasher second, Magisk third.
After rebooting, and reconfiguring the phone, all works fine.

Categories

Resources