Database Info

Internal Memory full?

Hi all, I just flashed CM7 using the newest clockwork mod recovery. Now it says my internal memory is full. I havnt deleted anything internally since I got the phone. What is the best way to format that memory and reinstall a fresh copy of CM7?

Kaczman said:
Hi all, I just flashed CM7 using the newest clockwork mod recovery. Now it says my internal memory is full. I havnt deleted anything internally since I got the phone. What is the best way to format that memory and reinstall a fresh copy of CM7?
Click to expand...
Click to collapse
Go to recovery......in recovery go wipe cache, factory reset/data, go to mounts/storage and format system, data, cache....go to advance and delete dalvik cache..... then just install zip from sd, choose zip, flash taht **** and reboot your phone

Awesome!! thanks bud!

I don't mess with CWM wiping partitions anymore, I wrote a flashable script for that - a long time ago there was an issue with that on CWM 4.0.0.8
A member has confirmed that A01 wipe will be okay if you turn off and have no ROM installed, you will still be able to get to CWM and flash whatever you want.
A01 wipe will format /cache, /data and /system
B01 wipe will format /cache and /data
Use as needed.
I keep a backup memory card with my phone at all times that has A01 wipe, B01 wipe, and my original CWM backup of my stock system on it, in case I ever need to go back to stock if something goes wrong.
Attached are the scripts, just throw these on your sdcard and flash like normal in CWM if you need to, before installing a ROM or patch if needed.

Blue6IX said:
I don't mess with CWM wiping partitions anymore, I wrote a flashable script for that - a long time ago there was an issue with that on CWM 4.0.0.8
A member has confirmed that A01 wipe will be okay if you turn off and have no ROM installed, you will still be able to get to CWM and flash whatever you want.
A01 wipe will format /cache, /data and /system
B01 wipe will format /cache and /data
Use as needed.
I keep a backup memory card with my phone at all times that has A01 wipe, B01 wipe, and my original CWM backup of my stock system on it, in case I ever need to go back to stock if something goes wrong.
Attached are the scripts, just throw these on your sdcard and flash like normal in CWM if you need to, before installing a ROM or patch if needed.
Click to expand...
Click to collapse
hey Blue just outta curiosity has anyone confirmed having issues with wiping through CWM with the new recovery or has the issue carried over from the 4.0.0.8/9?

I'm pretty sure I don't remember anyone having issues directly with cwm 4.0.0.9, and it was only a problem with 4.0.0.8 - even then not everyone experienced it.
I haven't tried the new recovery available yet, I meant to get to it this weekend, but it doesn't look like i'll get a chance to fit it in my schedule. I haven't seen my lady in just over a week, so spending the weekend with her.
Hopefully over the next week i'll get a chance to bring myself up to speed with it, I don't expect to go back to 4.0.0.9 once I move up to the new CWM recovery.

[Q] TF101 Installing Custom ROM on Encrypted device

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.

(SOLVED) [Q] [HELP] Motorola NOOB! Mount point information for XT925?

Hi there, I seem to have messed up my mounting partitions while trying to deodex Stock JB Central Europe. I basically used xultimate to pull the files and deodex then tried using adb shell to mount the system partition and copy them over. After I rebooted the phone, it would get stuck on unlocked bootloader warning or on the motorola logo. I hard reset into recovery and restored a nandroid backup and once booted into android found so many folders under the Storage folder such as "asec", "obb", rfs0" and so on. Now, when I try to wipe dalvik-cache in recovery, i get the following error: "E: unknown volume for path [/sd-ext]". Also, when i try flashing custom rom's and reboot, it gets stuck on the unlocked bootloader warning and wont load - while in recovery after flashing, i also get another error something like this: "E: cant load /cache/recovery.log" or similar. I also sometimes have issues mounting system, cache partitions, data and internal storage, all depending on which custom recovery i am using. I read on another site that downgrading to ics might solve mounting problems so I forced a downgrade to ics but that didnt work either and am still on ics.
Is there a way to restore the partitions correctly or are they stuck this way? Would mounting and remounting solve this problem? Any help would be much appreciated and would very much appreciate it if someone could upload their mount point info so i could use to try and fix it.
Many thanks in advance.
EDIT: Managed to flash Slim Bean 4.3 Official using OUDHS recovery without wiping cache and dalvik-cache at first. After reboot, it would bootloop so went to recovery and wiped cache and dalvik-cache then it worked. Still no sd-ext and some apps can't write or backup to external memory such as Go Backup & Restore Pro so what remains is to mount/unmount the partitions correctly.

Phone soft-bricked after bad manipulations (need help from advanced users)

Hello
First of all, I'd like to excuse myself because of my lack of knowledge in all that android stuff and also in english. I got my phone rooted just by following tutorials on internet.
I have a Huawei Ascend Mate 7 MT7-L09. Probalby half a year ago, I have unlocked bootloader and installed CWM-based Recovery v6.0.5.1 and got it rooted.
Not long ago, Huawei released a new version of the EMUI, wich I guess is the Android 6.0 marshmallow thing (logically, I was using the previous version). After downloading, I tried to install it but it would reboot to the CWM everytime I was trying. And then, after booting, the phone would tell me the update failed. It's normal, I know. I needed to install it manualy and etc
BUT instead, by pure ''I don't give a crap what may happend'', I did some big crap.
First of all, in the phone's settings, I did a factory reset. I made a backup of all my files and data before (not in the CWM, but in the phone's tools). After the reset, the phone booted in an old-fashioned android version.There wasn't any keys to go home/back on the bottom of the screen. Because of this, the phone was almost unusable because I had to reboot the phone to leave an app and select another.
I raged and booted to the CWM by pressing the + button and the lock phone button.
I went to Mounts and Storage Menu and did all of this
format /boot
format /system
format /cache
format /data
format /storage/sdcard1
format /data and/data/media (/sdcard)
I did the wipe data/factory reset
I also went to Backup and Restore
I made the
delete from /sdcard
delete from /storage/sdcard1
free unused backup data
choose default backup format
I went in Advenced Menu aswell
I chose
wipe dalvik cache
I think that's it. No wonder why it doesn't work well now LOL...
Later on, I thought I may try to fix it. After reading some stuff, I downloaded a package from the official Huawei website, I think it was with the 5.5.3 EMUI or some sort of. After mounting USB storage to my pc, I put the zip file, wich was not really a zip file because it had a .tar format, it would show me by going to the install zip: Impossible to read format lol. Then I found a package of a rom wich was zip. After putting on the phones storage this zip it would start to install and show installing update and then show me: Installation aborted. Then i gave up and decided to ask some help from pros.
So..... What should I do?
I know my explications are weird, but this is the only way I can describe my problem.
Thank you for reading this long story, and even a bigger one if you help me.

hi,
i don't know cwm recovery.
I suggest you install TWRP recovery , then flash the rom image found here.
(i have installed B571 by this way)
http://forum.xda-developers.com/mat...overy-twrp-2-8-7-0-mate7-android-5-1-t3156779
http://forum.xda-developers.com/mate-7/general/huawei-mt7-l09-l10-stock-firmware-ota-t3275784
regards

tar is another compression format like rar and zip.
If you have the software installed to use terminal commands (ADB) to connect to your phone when it is in so called 'recovery'or 'fastboot' mode you should flash the TWRP recovery image for Mate 7 posted somewhere on the forum for better compatibility. It is basically similar as CWM (clockworkmod) but newer.
In another post here there is a summary of firmwares and in that list is also the 'Twrp Backup' of a fresh installation. That should be downloaded, unpacked and placed in the folder where other/previous backups are stored. To find out where that it is you can create a backup yourself in recovery but only select the 'boot' so the backup is done immediately (and useless) and you can browse your phone to see where to put the downloaded recovery backup.
Next is restoring that backup within recovery.
Personally I would also do a factory reset after that but you should be ready to go after that.

0 mb in TWRP internal storage

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