Related
I recently managed to successfully root my TF101.
I installed CWM (Via ROM Manager) and downloaded CM9
I boot into CWM and attempt to do a nandroid...can't find path.
I attempt to just install from SDCard...can't find path
Realization (and research) hits that CWM can't see the external sd, and the system doesn't see it as SDCARD but EXT-.
CWM can't see the internal SDCard because apparently on the Tablet the ICS encryption locks that down (but doesn't on my EVO since the SC Card isn't part of the internal storage)
I attempt to perform a factory data wipe to clear out the encrtyption , but upon reboot CWM loads. I try to perform the boot-launcher data wipe, but then CWM loads.
I try to use CWM to factory reset but since it can see the damned SDCard because of the encryption, no dice.
My machine is not bricked, as I can still boot into the previous install but I can't seem unable to format the thing to install CM9.
What to do, and thanks.
It has been said multiple times before DO NOT USE ROM MANAGER.
Either use Thing O Doom's peri to install a different CWM or Gnufabio's Recovery installer or NVFlash a rom to completely wipe. And don't use encryption there is no point 99% of the time
I didn't check here first, which is obviously what was my first mistake.
Will any of those recoveries be able to access and format the SD Card area?
Also, I use encryption as I do have sensitive things on my machine that I don't want exposed in case the machine is stolen. First time I've ever had it give me a problem, as the phone encrypts differently.
Team roug's recovery has internal and external sd support and i think the encryption is an ics/tegra 2 bug more than anything
Ok, so I managed to get the new recovery on via Thing O Doom's peri. And I was able to install Revolver via the ext card...but upon boot I was prompted for my encryption pin and got the message that android was updating...My Build number is now Revolver but everything is the same as it was. I still can't factory wipe this damned thing.
Upon request to wipe, it boots back to recovery and says formatting data and cache, data wipe failed.
Tis site states http ://0xfeedface.org/blog/lattera/2012-06-04/installing-cm9-encrypted- android-tablet
The dilemma
When you encrypt your Android device, the /data partition is what gets encrypted. The partition in full is encrypted and cannot be mounted within CWM. CWM also cannot perform a wipe, since it cannot mount the /data partition. And CWM cannot mount the external SD card. This is our dilemma. No access to the internal SD. No access to the external SD. No way to perform a wipe and format the internal SD from CWM.
The Solution
What we need to do, then, is use adb while the tablet is in recovery mode to reformat the internal SD card, thereby removing the encryption. On the US Transformer Prime, the internal SD card is at /dev/block/mmcblk0p8. The partition for our spare SD card will be at /dev/block/mmcblk1p1. You will need to replace those device entries for any other device you might attempt this on. After formatting the internal SD card, we will mount it and then mount the external SD card at /data/media:
In CWM, wipe cache
adb shell
mke2fs -t ext4 /dev/block/mmcblk0p8 # Warning: This can take a while. Be patient.
mount /data
mount /dev/block/mmcblk1p1 /data/media
Now go back to CWM on your device, then go ahead and flash your CM9 and gapps zips like normal. You now have CM9 installed! The /data partition is not encrypted. If you do not need to flash any other ROMs (unlikely if you're reading this article), feel free to re-encrypt your device.
Click to expand...
Click to collapse
I don't know the block numbers for the TF01
you need to undo the encryption before you can wipe anything
You can't. Hence my problem. I cannot mount,delete, or format the SDCard. It sounds like the process in the above post is the solution, but I don't know how to find out what block numbers the tf101 uses.
If you don't mine losing your data NVflashing a rom will resolve all the problems
Yep nvflash will do the trick otherwise as the solution you found yourself explains
Use adb in recovery ( in other words hook it up on a pc ) for this you will need android sdk runnin on your pc
More info about adb u can find here
http://forum.xda-developers.com/showthread.php?t=1751439&highlight=adb+help
Good luck
Thanks to all, I have resolved my issue!
I had to download the stock rom, extract the blob, and use Wheelie for PC to NVFlash everthing abck to stock. I was then able to update over OTA, and use the excellent Thing O Doom's peri to re-root and flash the working recovery.
There should be several items in the Root FAQ up top, such as:
If you are encrypted and going to root, factory reset to get rid of the encryption FIRST since the encryption locks down the SDCARD partition (Unlike on the phone)and none of the recoveries can access it to mount. DON"T use ROM manage on the TF101 and always, always check XDA first.
:good:
darthrater said:
Thanks to all, I have resolved my issue!
I had to download the stock rom, extract the blob, and use Wheelie for PC to NVFlash everthing abck to stock. I was then able to update over OTA, and use the excellent Thing O Doom's peri to re-root and flash the working recovery.
There should be several items in the Root FAQ up top, such as:
If you are encrypted and going to root, factory reset to get rid of the encryption FIRST since the encryption locks down the SDCARD partition (Unlike on the phone)and none of the recoveries can access it to mount. DON"T use ROM manage on the TF101 and always, always check XDA first.
:good:
Click to expand...
Click to collapse
That FAQ is sadly pretty outdated, I wish I could liberate the OP
Glad all is working now though.
Im having a trouble reflashing a ROM. During my efforts to fix my horrible battery life problem by doing Odin back to stock and reflashing DK ROM something else has gone wrong.
I go to to Recovery and I tried to wipe data and Reset to Factory
it says
Formatting / data......
Formatting / Cache....
Formatting / sd-ext....
E:format_Volume: make_extf4fs failed on on dev/block/mmcblk1p2
Formatting/sdcard/.android_secure....
Data wipe Complete.
It also says, sd-ext.img not found when I restored my Nandroid backup. Not sure whats going on here...
When it restarts, its still the same old rom with everything still there, just with user data wiped like my google login. How do I fix this? I have already Odin back to stock, rerooted and CWM and am still getting this issue. Could this be contributing to my terrible battery drain?
Nothing wrong, that's normal.
ROMs on phones that didn't have enough local space to install any real number of apps, etc (think Nexus One, or HTC Evo 4G) used to create a second partition on the SD card. This partition was formatted to ext4 and mounted in place of stuff like /system/apps or /data, etc..
Nandroid simply tries to format the partition if it's there, and obviously it isn't. I doubt anyone here has that partition. The sd-ext.img would be the image file nandroid would create if you did have the partition and you backed it up.
But the problem is I cant flash another ROM without doing the factory reset, and when I do factory reset I get that error and the new ROM isnt flashed.... I have never had this error before when I flashed DK originally, or on my last Blaze phone. I need to fix this issue so I can flash a different ROM, or next newest update to this ROM.
You've got some other problems then, because I get that error all the time and have for some time on all sorts of phones.
Once the /data partition is formatted, your wipe is complete. The /cache is good stuff too... once you see those two lines, you are all resetted.
If you nandroid restore, you're going back to what you had.
So why wont it factory reset then? Everytime I do factory reset in recovery, it shows all my files and stuff still on the phone. It never completely wipes my phone. I dont know what to do or what the problem is...
Is there a certain way everything is supposed to look in mounts and storage? Whats supposed to be mounted or unmounted? And what should be formatted?
Factory reset doesn't wipe your sd card. For that you have to format it from the settings menu.
dr4stic said:
Factory reset doesn't wipe your sd card. For that you have to format it from the settings menu.
Click to expand...
Click to collapse
Can you explain how to do that?
I beilive he means in CWM, under mounts and storage, format /sdcard
Sent from my SGH-T769
No, I meant in android. I'm sure a quick Google search would turn it up, but here goes: Settings -> Storage... you'll want to unmount first, then format.
SD card = removable card
USB Storage = internal storage
Just remember, this will destroy ALL your data on whichever you choose to format. Everything, your pictures, music, etc...
*removed*
It's awesome. Usually, wiping system, cache and data lasted like 5 or 10 minutes, I tested this recovery and it wiped everything so quickly. Thank you so much for this .
Edit: Installing works.
Q9Nap said:
Here is TWRP for Moto E LTE with "Use rm -rf instead of formatting" enabled by default.
Moto E LTE uses f2fs format for the userdata partition and TWRP doesn't format it correctly by default, causing issues with mounting.
# README
Warning: backup any important data on your internal storage first!
Boot into TWRP and perform the following:
Wipe > Format Data > type "yes" then enter
This will format your userdata partition using mkfs.f2fs, in case it isn't already
Now, whenever you wipe data, TWRP will use rm -rf instead of attempting to format using make_ext4fs
# DOWNLOAD
http://batakang.com/ftp/devs/mhous33/surnia/twrp-2.8.6.0-surnia-rmrf.img
# CREDITS
@cybojenix for his initial TWRP work!
@squid2 for his improved TWRP work and very useful information!
@dhacker29 for his very useful information!
Click to expand...
Click to collapse
When I try to format data it fails, it's unable to mount anything. My phone is a surnia XT1527. Now when I try to flash it says unable to mount /data.
wiped system, devlik cache, data, internal storage, chache. dont know how to restore
I had a problem with someone using remote spy software and hiding spy apps on my phone. I have a MOTO E 2015, XT1527. I had this phone rooted with a custom rom installed. my OS was lollipop.
I went into TWRP recovery and wiped:
devlik cache
system
data
internal storage
chache
USB-OTG
I did not have an SD card inserted at the time
I am not very knowledgable on all of this (not so tech-savy but can follow instructions), but I need to fix this phone asap.
My phone keeps re-starting and will not go any further than the boot animation screen (if that's correctly stated). I can get into recovery mode but that's it. I have no backups. recovery tells me that I have uninstalled the OS, which I'm guessing means I have uninstalled everything else too!
I don't know what to do from here, what to do first or how to do it, I do have access to a computer, and need help PLEASE!!! I have been looking up ways to fix this but cant find clear answeres directed to this phone and problem specifically.
jacquelinexrose said:
I went into TWRP recovery and wiped:
devlik cache
system
data
internal storage
chache
USB-OTG
I did not have an SD card inserted at the time
Click to expand...
Click to collapse
Definitely wiped everything. You need to download a ROM, boot into recovery and install it.
So glad I found this thread! I'm using the latest 3.0.2.0 but this setting saved me from going crazy!
I was seeing too much red Big thanks!
link dead
Hello, I would really appreciate your kind help solving a bit of a problem I have with my Moto G 4G
I had a problem with my google account where it wouldn't sync anymore and play store sopped working (says no connection even though is there).
Since I already encountered this problem before and solved it once by formatting cache, and data I tried to go into Recovery.
Here the oddities begin: TWRP doesn't load and gets stuck on splashscreen;
I searched for it and read that formatting cache and userdata would solve also this problem, so I guessed that formatting them from bootloader would have done the trick.
Unfortunately when I enter the command fastboot format cache or fastboot format userdata I get this:
formatting is not supported for filesystem with type 'raw'
Are some of my partitions corrupted?!
How can I solve this??
BTW I can boot into system and all is fine except the problem with the google account that led me to these findings.
albmanzi said:
Hello, I would really appreciate your kind help solving a bit of a problem I have with my Moto G 4G
I had a problem with my google account where it wouldn't sync anymore and play store sopped working (says no connection even though is there).
Since I already encountered this problem before and solved it once by formatting cache, and data I tried to go into Recovery.
Here the oddities begin: TWRP doesn't load and gets stuck on splashscreen;
I searched for it and read that formatting cache and userdata would solve also this problem, so I guessed that formatting them from bootloader would have done the trick.
Unfortunately when I enter the command fastboot format cache or fastboot format userdata I get this:
formatting is not supported for filesystem with type 'raw'
Are some of my partitions corrupted?!
How can I solve this??
BTW I can boot into system and all is fine except the problem with the google account that led me to these findings.
Click to expand...
Click to collapse
Have you tried reflashing TWRP through fastboot, like this
Code:
fastboot flash recovery recoveryimage.img
You could then wipe, or format these partitions in TWRP.
Professor Gibbins said:
Have you tried reflashing TWRP through fastboot, like this
Code:
fastboot flash recovery recoveryimage.img
You could then wipe, or format these partitions in TWRP.
Click to expand...
Click to collapse
I tried that already, albeit just reflashig TWRP 3.0 and not other recoveries... it didn't work, still keeps getting stuck at splash screen :crying:
Did you use
Code:
fastboot format cache
or
Code:
fastboot erase cache
Because the format seems to give that error and erase should not.
UPDATE: After reading your post it says you did indeed use format, not erase, so use
Code:
fastboot erase cache
fastboot erase userdata
Thanks, unfortunately it worked to solve just the recovery getting stuck, and I f*ed up other things in the process.
I still can't access to Google accounts, or create another, says connection error with google servers.
Since I had the SD card as internal storage before, erasing userdata caused the SD card to not be recognised anymore... I could format it to solve the problem, but I didn't have a recent backup so now I also need to try recovering that data. I know. I'm an idiot.
The strange thing is I even wiped Cache, Dalvik, Data and System and proceeded to flash a new ROM, and google account still doesn't work
There are so many variables that could be causing the Google account issue. Although, did you flash the stock rom or a custom rom?
I flashed 6.0.1 custom rom, Resurrection Remix
Google account issue got solved by simply doing another wipe and ROM flashing.
Now I have to deal with the corrupted microsd card issue I caused when i erased userdata...
I don't want to format the card before I can restore the data that was in there, there's still important stuff there, and last backup is too old.
When I'm in recovery with the phone connected to PC I can see the drive and windows says it has only 590MB of free space from a 7.42GB total; problem is when I open the drive it says it's empty.
When I put the microsd in a card reader instead, it does get a drive letter assigned but when I try to open it windows asks me to insert a disk.
Data is still there, it didn't got wiped with userdata... did it?!
I tried the method described in this guide http://forum.xda-developers.com/galaxy-s4/general/guide-internal-memory-data-recovery-t3093292 to recover mmcblk1p1 and mmcblk1p1p2 but the recuva scan I did to the generated virtual hard disk reported no deleted files and just the file indexervolumegrid in system volume information folder.
Now I'm going to try to use testdisk to see if i can repair the partition, but i'm no expert so I'm not sure how to do that.
albmanzi said:
Google account issue got solved by simply doing another wipe and ROM flashing.
Now I have to deal with the corrupted microsd card issue I caused when i erased userdata...
I don't want to format the card before I can restore the data that was in there, there's still important stuff there, and last backup is too old.
When I'm in recovery with the phone connected to PC I can see the drive and windows says it has only 590MB of free space from a 7.42GB total; problem is when I open the drive it says it's empty.
When I put the microsd in a card reader instead, it does get a drive letter assigned but when I try to open it windows asks me to insert a disk.
Data is still there, it didn't got wiped with userdata... did it?!
I tried the method described in this guide http://forum.xda-developers.com/galaxy-s4/general/guide-internal-memory-data-recovery-t3093292 to recover mmcblk1p1 and mmcblk1p1p2 but the recuva scan I did to the generated virtual hard disk reported no deleted files and just the file indexervolumegrid in system volume information folder.
Now I'm going to try to use testdisk to see if i can repair the partition, but i'm no expert so I'm not sure how to do that.
Click to expand...
Click to collapse
Unfortunaly the erase userdata command will also erase the internal SD card. This is because the shared internal 'SD card' is actually stored under the userdata partition, in /data/media.
Im not a data recovery expert, but i believe that recovering data deleted on solid state media is much more difficult than a magnetic disk. Also, that tutorial appears to be for a Samsung phone, so those are not the correct partitions.
As for repairing the partition, the userdata partition, and the /data/media directory inside it, is recreated when booting into a ROM.
Professor Gibbins said:
Unfortunaly the erase userdata command will also erase the internal SD card. This is because the shared internal 'SD card' is actually stored under the userdata partition, in /data/media.
Im not a data recovery expert, but i believe that recovering data deleted on solid state media is much more difficult than a magnetic disk. Also, that tutorial appears to be for a Samsung phone, so those are not the correct partitions.
As for repairing the partition, the userdata partition, and the /data/media directory inside it, is recreated when booting into a ROM.
Click to expand...
Click to collapse
Yeah, I can't find anything even with testdisk.... I am at a loss, fortunatyely the lost data isn't mission critical, nevertheless it forces me to repeat many hours of work.
Going to format the card.
Sorry to hear that. Although I suppose it's a good reminder of the importance of regular backups.
I searched for an answer and noticed it's a common issue. I am trying to flash a kernel on to my already flashed rom. I was wondering if there is a more current fix. More importantly, how can this be avoided in the future. Thank you guys!
Its caused by a bug/error with either the filesystem or encryption.
Did you wipe data after flashing the new ROM? Data from stock usually doesn't work with custom ROMs.
Do you have a PIN/password on Android?
Are you using the latest build of TWRP?
Press the menu button at the bottom of the screen in TWRP and post what the error message is in the red text.
It's caused by no root access
djhulk2 said:
It's caused by no root access
Click to expand...
Click to collapse
Something is probably wrong with the data partition. TWRP should always have root access.
Try in TWRP:
Wipe > Format Data > Slide to format
This will erase the data partition, so backup everything to a PC in Android first if needed. It should allow TWRP to mount /data again.
KemikalElite said:
Something is probably wrong with the data partition. TWRP should always have root access.
Try in TWRP:
Wipe > Format Data > Slide to format
This will erase the data partition, so backup everything to a PC in Android first if needed. It should allow TWRP to mount /data again.
Click to expand...
Click to collapse
I've debated on doing this. I'm not worried about losing pictures texts etc as they're backed up.
I read that it essentially leaves the device with no OS. If that's wrong please let me know!
I have found that if I choose Slot A and reboot system it reboots me in to TWRP. If I choose Slot B it runs the OS like normal (except I still have issues using Facebook and it's services).
The ROM works and I can perform all the custom mods on it. I just want to flash a kernel and the problem persists. 0 mb in storage.
It's trial and error at this point. Fail fast fail forward. I have another phone I can use but I love the OnePlus. Any help will be appreciated!
https://andi34.github.io/faq/faq_twrp.html
I'm not willing to risk it until I know how to get the custom ROM on to the storage to flash it.
Yes formating by typing in yes will wipe it all,everything including pictures, with no rom on it at all. If u choose to do that, don't close twrp. Instead you should be able mount after wards, once mounted transfer the magisk zip, twrp, and your custom rom(has to be 1.5gb not 200mb through magisk). Flash magesik, install ram disk twrp, install rom. That was a method I've done before but if u want to keep everything there is other way
fastboot boot twrp.img, that command boots twrp if u have it or don't, installing to ram disk makes it permant...this boot command is just a one time thing each time. It's what I do when new firmware update, I loose root but I regain it each time
Never heard of formating data removing the OS, that would be if you wipe the system and normal wipe is like a factory data reset and therefore will not wipe your phone of the OS
djhulk2 said:
Yes formating by typing in yes will wipe it all,everything including pictures, with no rom on it at all. If u choose to do that, don't close twrp. Instead you should be able mount after wards, once mounted transfer the magisk zip, twrp, and your custom rom(has to be 1.5gb not 200mb through magisk). Flash magesik, install ram disk twrp, install rom. That was a method I've done before but if u want to keep everything there is other way
fastboot boot twrp.img, that command boots twrp if u have it or don't, installing to ram disk makes it permant...this boot command is just a one time thing each time. It's what I do when new firmware update, I loose root but I regain it each time
Click to expand...
Click to collapse
I attempted to format. It said
"failed to mount /data (device or resource busy)
"unable to mount storage"
Try this in recovery, sometimes its known to work.
Wipe > Advanced Wipe > Check Data and press Repair or Change File System > Change File System > Change it to EXT2.
Repeat the same process selecting Ext4
Wipe > Advanced Wipe > Check Data and press Repair or Change File System > Change File System > Change it to back to EXT4.
Try formatting data after this.
drey4211 said:
I attempted to format. It said
"failed to mount /data (device or resource busy)
"unable to mount storage"
Click to expand...
Click to collapse
Since you dont care about the data on the phone I would just do 1 of 2 things. 1st I would reflash twrp on to you phone if that doesn't work then I would just grab the fastboot ROM and just flash your phone back to full stock reroot and install twrp from scratch. I would not try to start repairing partitions. I wouldn't want to worry about screwing up the EFS partition
Well in an update, I formatted the
Storage and now I'm stuck in bootloader screen. It's unlocked but I'm having a hard time flashing a ROM through adb.
I use the twrp version 3.3.1-2
Best would be to just use fast command to boot it
But it should be under wipe/format data/then type in yes
That was what I was trying to have you avoid. If your can boot to fastboot download the fastboot ROM I told you to and run the flash-all.bat file. If your on 9.5.8 make sure you use the fastboot ROM of the same version. Do not flash azip of a different version firmware like 9.5.7.
It happens to me any time I'm in twrp and flash a rom then reflash twrp. It doesn't matter if I flash Magisk or not the issue always happens. What I do is use a USB C flash drive and plug it in when I want to flash/backup a rom. This way I can always access it. After flashing any rom then booting I'm always able to access my internal storage again. It seems like a bug in twrp.
The strange part is when this bug happens your files are encrypted in a 0 folder but you can still copy from your PC to your internal storage while in twrp.
I essentially soft bricked my device. Called OnePlus and they got me up and running. That's awesome that they have that service!
Are you removing all security? Pattern, pin and fingerprints? Are you decrypted? Never had an issue with flashing a ROM causing these issues which is why I'm asking. Something you've done at some point is causing this
I'm not sure what that was. Ironically enough I am now stuck in TWRP boot loop. Hopefully I can figure this out otherwise I have to call oneplus again.
I will admit I may not know everything but it's trial and error. I don't have anyone to really teach me this so I try to read the forums and learn. You guys have been great!
ajsmsg78 said:
It happens to me any time I'm in twrp and flash a rom then reflash twrp. It doesn't matter if I flash Magisk or not the issue always happens. What I do is use a USB C flash drive and plug it in when I want to flash/backup a rom. This way I can always access it. After flashing any rom then booting I'm always able to access my internal storage again. It seems like a bug in twrp.
The strange part is when this bug happens your files are encrypted in a 0 folder but you can still copy from your PC to your internal storage while in twrp.
Click to expand...
Click to collapse
I've the same issue.. did you find a fix? So annoying