I have TNT 3.1.3 installed. Fortunately today I did a backup. I ran into the boot loop tonight. I have tried repartitioning the sdcard to 2048,0 as recommended, but of course when I do that I lose all the data.
I used adb to push the clockworkmod directory (with my backup) under sdcard and I was able to do a restore. That seemed to work. Had to power off once when it seemed hung on the first boot. But when I go into the terminal emulator and use the df command it looks like the sdcard has a partion size of 8192 even though I used clockworkmod to partition it to 2048.
How are you supposed to partition the sdcard to 2048,0 since it wipes what is on your sdcard? Do you have to start completely from scratch when you re-partition your sdcard?
Thanks.
OK, I was able to recover and I am now on vegan beta 5.1. I still would like to verify that the sdcard partition is correct. Otherwise, I am afraid I might hit the boot loop again. Is there anyway to check it and verify it? When I partition with 2048 and zero, what is that doing?
Thanks.
its setting your data to 2048 and your swap to 0. It seems to be the only way to stop several problems...boot loops..massive force closes...processes stopping. If you already partitioned it that way with clockwork then your okay. I keep an extra copy of my backups on a micro sdcard for clockwork backups and titanium app backup
Related
I am unable to create a nandroid backup.
ROM: DarchDroid 2.5.1.2
Recovery: GodSpeed Recovery Toastcfh
I'm trying to do a NAND + ext backup (A2SD ext4)
I get the following error after about 45 seconds:
Code:
Error : Run 'nandroid-mobile.sh' via adb!
I'm guessing this has something to do with the newish A2SD that's being used on DarchDroid? Like... I'm used to the A2SD apps being stored in /system/sd/app but I don't see that folder structure in root explorer. I still have yet to find where the ext partition is.
I know A2SD is working, under Settings > SD card & Phone Storage: I see the ext partition has about 80MB used and internal phone storage remains at 128MB (I have a few apps on internal storage)
I have it setup with a 32MB swap with 512MB of ext4
Any ideas?
so... what's the error?
Whoops...
I edited the original post, its just a generic nandroid error.
I just flashed not too long ago, so I'm not too far into modifying it. I just did a full wipe of /data and /ext and re flashed. Same error.
it could be because you dont have enough memory on your SD card to make the backup
mrchu001 said:
it could be because you dont have enough memory on your SD card to make the backup
Click to expand...
Click to collapse
7GB free...
I'm moving away from DarchDroid anyways... GPS is broken still, going back to FreshToast.
As I was getting low on my LG-P500 phone, I tried looking for some app2sd solution, doing the following steps:
- Backup all SD card content to PC
- Boot into recovery (CWM5.0.2.7)
- From recovery, create sd-ext partition
- From recovery, format the new partition
- From recovery, mount usb device, restore all SD card content from PC.
- Reboot device, installed link2sd and managed to link applications to sd.
Now link2sd seems to work fine- I tried linking quite a few applications and all of them work fine, no complaints. It only gave me an error with some apps which I have previously *moved* to SD using Titanium backup, but upon moving them to internal storage link2sd picked them okay.
However, I noticed that using file explorer, root explorer etc- they all show the sd-ext partition as empty, with size of 0 bytes??
Then, I booted into recovery and tried to mount the sd-ext partition, but I get an error message... (all other partitions I can mount/unmount just fine).
To be sure, after each reboot it looks like all the applications linked2sd work appropiately, so everything looks fine.
However, now I am concerned whether I can create (and restore, of course) nandroid backups- what will happen with all these apps linked to sd? Am I right that CWM may not be able to backup (and therefore restore) anything that is on this partition?
Am I going to lose all these apps and data? Does TiB backup these apps+data and be able to restore them fine to sd-ext? I'm asking about TiB as a mediocre workaround of restoring applications that were in sd-ext (and thus omitted by CWM backup). That is, after restoring nand backup- doing an additional restore from TiB??
Any help/insight is welcome
Ah, yes, some more info:
Phone: LG optimus P500
ROM: Lupohirps CM9 4.0.3 from this thread http://forum.xda-developers.com/showthread.php?t=1558213
Recovery: CWM 5.0.2.7 (By the way, whenever I try to flash 5.0.2.0 I get an error...)
that's weird since the app working. what ekstension do you have on sd card fat? fat32?
Can you open Android Terminal (https://play.google.com/store/apps/details?id=jackpal.androidterm) and issue these commands:
su
busybox ls -la /sd-ext/
busybox mount
If /sd-ext doesn't show up in mount, then it is not mounted.
Actually CM9 for P500 lacks file /system/etc/init.d/05mountsd (this file is responsible for mounting /sd-ext). IMHO You should ask ROM developer about sd-ext support.
If you want to test (and potentially restore your Nandoid backup or reflash CM9 afterwards) I can give you this script from CM7 (actually modified version that allows any ext version).
Your sd-ext files are actually in data/sdext2, not in /sd-ext.
Also Try using Amonra 3.0.6, overall it has better sd-ext support, I find it mounts and wipes things like dalvick cache inside the sd-ext partition as well , which is handy, unlike CWM.
Thanks for all your replies!
Sdcard file system is fat32. For the partition I have no idea as cwm didn't ask for any specific (e.g. ext2/3/4) and I haven't seen any way to get this Info...
Anyway, following this thread, I did find that all the app/data is in /data/sdext2- not sure what it means in terms of nandroid backup& recovery but it looks more reassuring..
As to RA recovery, I'm not in particular in love with cwm- it is just what I'm used to from other android devices I've been using. Actually on my htc mt4g I was using ext4 touch recovery and that one I really liked, but it is not supported in lots of devices. That phone was stolen, unfortunately. I'll give it a try, though.
Sent from my GT-P7510 using Xparent Cyan Tapatalk 2
DavisNT said:
Can you open Android Terminal (https://play.google.com/store/apps/details?id=jackpal.androidterm) and issue these commands:
su
busybox ls -la /sd-ext/
busybox mount
If /sd-ext doesn't show up in mount, then it is not mounted.
Actually CM9 for P500 lacks file /system/etc/init.d/05mountsd (this file is responsible for mounting /sd-ext). IMHO You should ask ROM developer about sd-ext support.
If you want to test (and potentially restore your Nandoid backup or reflash CM9 afterwards) I can give you this script from CM7 (actually modified version that allows any ext version).
Click to expand...
Click to collapse
Thanks! Looks likeb system/ cache/ data are all yaffs2, /mnt/Sdcard is vfat and /data/sdext2 is ext4. Not sure what all the output means (relatime, barrier=1, data= ordered etc. etc.)
So, can I figure out where the /data/sdext2 is physically stored? Is it actually the sd-ext/ext4 partition? Looks like must have, as its contents are way bigger than phone's 200MB internal storage...
Thank you all again
Sent from my GT-P7510 using Xparent Cyan Tapatalk 2
jaibar said:
Thanks! Looks likeb system/ cache/ data are all yaffs2, /mnt/Sdcard is vfat and /data/sdext2 is ext4. Not sure what all the output means (relatime, barrier=1, data= ordered etc. etc.)
So, can I figure out where the /data/sdext2 is physically stored? Is it actually the sd-ext/ext4 partition? Looks like must have, as its contents are way bigger than phone's 200MB internal storage...
Thank you all again
Sent from my GT-P7510 using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
/data/sdext2 is the mountpoint for the ext4 partition thats on your sd card, physically its obviously on your sd card, but If you use linux, data/ is where the all partitions other then home partition get "attached"/mounted to, the 11link2sd script made by link2sd in yout init.d folder actually mounts it sdext2, the name means nothing, just something link2sd names it as.
---------- Post added at 08:40 PM ---------- Previous post was at 08:30 PM ----------
So Basically nandroid will not back it up under /data/sdext2 as the script runs after recovery, the best way to backup apps that are on the ext partion is back them up using Titanium Backup, as that saves the real apks, and when you restore all your apps, select link2sd to automatically move them to sd-ext partition.
Hi at all,
at first sorry for my bad english.
I had a similar case. If I made a backup with cwm 5.0.2.7, cwm cant mount/read the sd-ext.
In a other thread a user wrote, that cwm 5.0.2.8 had problems with the sd-ext.
And he does downgrade to cwm 5.0.2.0, and than cwm will work.
So, I did this:
I open the rommanager and choose the option "install Clockworkmod", now I choose the "LG Optimus One (old BB)".
But i have the new baseband on my O1.
The basis of this is, if you choose the new baseband in the rommanager, he will install cwm 5.0.2.7. For the old is it the 5.0.2.0 version.
Now, Rommanger made the installation with cwm 5.0.2.0. to my phone.
After this i go in to the recovery and made my nand-backup. It works perfekt!
No problems with the sd-ext, after I did this.
May be this will help.
Fietz said:
Hi at all,
I open the rommanager and choose the option "install Clockworkmod", now I choose the "LG Optimus One (old BB)".
But i have the new baseband on my O1.
The basis of this is, if you choose the new baseband in the rommanager, he will install cwm 5.0.2.7. For the old is it the 5.0.2.0 version.
Click to expand...
Click to collapse
Thanks for the tip..
I have tried in the past to flash cwm 5.0.2.0 via Rom Manager, but I kept getting an error message, so I gave up.
Now I thought to give it a second chance, but as it fails to flash with Rom Manager (in the menu when I choose LG optimus one I don't get any choice between old BB or new or anything- it just reflashes 5.0.2.7) and from the "all recoveries menu I can only choose 5.0.2.0 but it gives an error message), so I downloaded the zip files from this thread http://forum.xda-developers.com/showthread.php?t=1523050 (including also Amon Ra 3.06) and tried to manually flash from recovery.
It flashed and showed recovery as "5.0.2.0" but nothing worked- every submenu that I tried to enter was black screen (with the CWM logo on background) and it gave me the creeps- I don't like being stuck without a functional recovery so I rebooted and flashed 5.0.2.7 again from Rom Manager.
I'll try to flash Amon Ra and see how it works.
[EDIT] flashed AmonRa 3.06 and it seems to work fine- able to mount/unmount all partitions including sd-ext, and it also has an option to check each of them in separate during nandroid backups.
A noobish question: it has also an option to include the ".android_secure" . Isn't this one a redundancy with sd-ext (e.g. contains all the apps/data that has been moved/linked2sd)?
jaibar said:
As I was getting low on my LG-P500 phone, I tried looking for some app2sd solution, doing the following steps:
- Backup all SD card content to PC
- Boot into recovery (CWM5.0.2.7)
- From recovery, create sd-ext partition
- From recovery, format the new partition
- From recovery, mount usb device, restore all SD card content from PC.
- Reboot device, installed link2sd and managed to link applications to sd.
Now link2sd seems to work fine- I tried linking quite a few applications and all of them work fine, no complaints. It only gave me an error with some apps which I have previously *moved* to SD using Titanium backup, but upon moving them to internal storage link2sd picked them okay.
However, I noticed that using file explorer, root explorer etc- they all show the sd-ext partition as empty, with size of 0 bytes??
Then, I booted into recovery and tried to mount the sd-ext partition, but I get an error message... (all other partitions I can mount/unmount just fine).
To be sure, after each reboot it looks like all the applications linked2sd work appropiately, so everything looks fine.
However, now I am concerned whether I can create (and restore, of course) nandroid backups- what will happen with all these apps linked to sd? Am I right that CWM may not be able to backup (and therefore restore) anything that is on this partition?
Am I going to lose all these apps and data? Does TiB backup these apps+data and be able to restore them fine to sd-ext? I'm asking about TiB as a mediocre workaround of restoring applications that were in sd-ext (and thus omitted by CWM backup). That is, after restoring nand backup- doing an additional restore from TiB??
Any help/insight is welcome
Ah, yes, some more info:
Phone: LG optimus P500
ROM: Lupohirps CM9 4.0.3 from this thread http://forum.xda-developers.com/showthread.php?t=1558213
Recovery: CWM 5.0.2.7 (By the way, whenever I try to flash 5.0.2.0 I get an error...)
Click to expand...
Click to collapse
Hi, Jaibar
I have LG Optimus One with JB 4.2.2, CM 10.1.
Here what I have done in order to gain extra space on my internal memory. All the steps that you have followed are the same as I did. BUT! There are two important things that I have followed that had greatly helped to succeed:
1) For every 100Mb internal memory - NO MORE than 512Mb of SD card memory(for my LG I have separated 965Mb on the SD card)
2) INT2EXT+ works with EXT2/3/4 partitions BUT INT2EXT4+ works with ONLY EXT4 partition. After I have watched this short video, and this blog post I have been able to restart my phone with extended internal memory.
Believe me, for three days I have been flashing my phone, trying to find the correct way. At the end I have noticed that the problem was that I couldn't mount /sd-ext I thought that maybe following this two rules will help - and it did!
I hope that it will help! Good luck
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.
ill keep this simple. tried to advanced wipe data and cache with TWRP which returned an E:/ unable to mount for both data and cache. internal storage is now saying its 0MB after i "fastboot erase" on as many of the partitions it would return success with (ie, what was mounted) flashall is asking me for a specific device.
How do i reset the internal partitions so they become mountable again? i believe in erasing the ones i had, it has deleted them altogether and i need to flash original firmware to get it to auto restructure (im guessing)
EDIT: so i downloaded this (link not allowed) i just dont know how to implement it through adb or fastboot
somewhere i read that the latest moto PQ versions for CWM and TWRP both have some selinux problem when wiping data, causing a force unmount (parroting. i DONT know what im talking about)
the first time i installed with CM11 with twrp (after CMW only allowing me to install 10.2) it worked great, except google play and whisperpush(whatever that is) crashing consistently. i should have used 'fix permissions' instead of going for a wipe+re-install
please help, what commands do i need to use through fastboot to restore the partitions, or where can i get the fxz file to use with RSD?
this is a brand new out of the box Sim-modded and pre-rooted PQ
SOLVED (i think)
god im so ****ing stupid.
due to corrupting the file structure and not being able to mount the cache or data partitions, when i installed CM11 snapshot it picked my external SD as the data storage /android/data/
FIX: unmounting and removing the external SD i rebooted to system, booted back to recovery. -> factory reset.... auto reboot, cant mount messages, then a second time it said SELinux supported message. ->factory reset again and finally no red messages, wipe to system (got an error, but probably cause system = external SD). i then inserted the external SD, installed the ROM and everything looks normal and working right
TWRP will restore file structure with 'factory reset' BUT ONLY IF you remove your external sd
i hope this thread saves time and headaches for someone.
just fyi. cm13 has no option to decrypt once you've encrypted it, twrp cannot mount encrypted drives (atleast most of the time i've heard a few say it can that's why i tried it but 2.8.7.0 doesn't even ask for a password or try to decrypt in my case)
so pretty much once you encrypt your stuck with the rom you have unless you have this magical twrp that asks for decrypt password.
also to make things worse, twrp can't format and cm13 changes the sdcard path so although it sees the external sd it can't flash files from it (atleast on g3)
so the only way to fix is to boot into android, backup your internal storage to sdcard or computer
reboot into twrp run a manual format on /data/ from terminal command, then reboot, copy your twrp backup to internal sd, go back to recovery and flash backup, then copy internal sdcard files back to internal drive (from sd or computer backup)
the command to format is the following
mke2fs -T ext4 /dev/block/mmcblkXpXX (NOTE: REPLACE THE XpXX with the proper values for your device) you can find these values by asking in your device forums, or downloading a partition info app that will tell you and i'm sorry i can't remember the one i used, but this is the best way to be sure because even diff device variants sometimes have diff partition tables based on phone provider.
*edit* just for personal peace of mind i remind everyone that every device is diff and i cannot guarantee positive results but this 100% worked for me everything is back to normal.
I did this a few months back and ended up flashing factory images via adb and starting all over again which sucked
Very useful information. :good:
TWRP v3.0.0 can use the adopted storage device (encrypted SD card) now.
Seems it's been fixed because I am successfully using cm13 with twrp 3.0, albeit with visible performance loss.
I just want to say thanks a lot for this. I can once again mount my /data partition.