question about partitions and custom ROM - Motorola Droid RAZR

I haven't tried any custom roms yet because frankly default jb is great.
I was wondering though, when you flash a custom ROM, will it use the application storage partition for your apps? Or will it want you to install apps on the roms partition?

The apps install on the individual rom's partition, because each romslot used creates a new partition that the rom recognizes as the only available storage space. This is the biggest reason some people opt out of using safestrap or bmm- the rom space is limited. They end up flashing over stock so they have all 8 gb, just as they would normally. Every app installed on each rom takes up space on the internal storage (a lot of redundancy).

timmytucker718 said:
I haven't tried any custom roms yet because frankly default jb is great.
I was wondering though, when you flash a custom ROM, will it use the application storage partition for your apps? Or will it want you to install apps on the roms partition?
Click to expand...
Click to collapse
Safestrap (/BMM), creates rom-slots on your internal sdcard. A rom-slot has its own /system, /data partitions and is independent of any other rom-slot or stock slot.

Thanks fellas. I didn't think you could use a custom rom on the razr without ss or bmm because of the locked boot loader. Can you?
And it's lame how theres a different partition for apps. Internal storage and apps should share a partition like on other android phones I've used.

timmytucker718 said:
Thanks fellas. I didn't think you could use a custom rom on the razr without ss or bmm because of the locked boot loader. Can you?
And it's lame how theres a different partition for apps. Internal storage and apps should share a partition like on other android phones I've used.
Click to expand...
Click to collapse
Locked bootloader means no flashable recovery.
And you cannot flash a ROM without custom recovery.
So the only way is Safstrap or BMM.
Its nothing different. Every android phone has these partitions.
/boot stores the kernel
/system stores the ROM
/data stores app and user data.
What SS does is create a copy of these partitions (like a virtual system) on the internal sdcard and set is to boot. Its the only way since the BL is locked.
DROID RAZR with Tapatalk 4

Related

Link2SD question for 2.3

Am I the only one who notices this or did I not configure my link2sd properly.
After setting up Link2SD to work, if I reflash my ROM, suddenly the new ROM will only recognize my Link2SD partition instead of my 1st partition.
Is there an easy way to point to the ROM to the correct partition rather than having to remove the Link2SD partition?
Thx.
sasukewa said:
Am I the only one who notices this or did I not configure my link2sd properly.
After setting up Link2SD to work, if I reflash my ROM, suddenly the new ROM will only recognize my Link2SD partition instead of my 1st partition.
Is there an easy way to point to the ROM to the correct partition rather than having to remove the Link2SD partition?
Thx.
Click to expand...
Click to collapse
The ROM can only recognize one partition at a time, if you have swap set up then you can switch between partitions, other wise, only link2sd can recognize the second partition and only on ROMS/Kernels that have the option enabled, otherwise your SD card will show up as corrupted or only one partition.
Basically the new rom wipes your swap enabled and your custom installrecovery.sh files which run your link2sd.
You need to create the required files in system/etc for your phone to be able to read the partitions correctly. And I think some roms need a custom kernel to activate swapiness too.
I have my link2sd all set up with wolfs rom and thjaps kernel, and take a backup before I flash anything now in case it screws it up.
Sent from my X10i using XDA App
Foloow the link in my signature and read up on how to update with link2sd...
If you still need help then PM me

[Q] Flash Kernel Using CWM

I am posting here as there is not sub-forum for Xperia Pro.
I want to flash kernel using CWM already installed on my phone. Is it possible? If so, how do I go about it?
PS: I found a thread which is for Samsung phones here.
I don't think so
There is no way to flash a Kernel for SE phones faik
Were is our moderator!
Sent from my MT15i using Tapatalk
Can anyone tell me why kernel cannot be flashed via flash_image and the like. Is it because /boot partition is locked in Xperia phones? Or because the there is no proper flash_image made for Xperia phones?
That's something like ; doing a bypass surgery while you're awake
Something like that ^
Qwerty123 \m/ said:
That's something like ; doing a bypass surgery while you're awake
Something like that ^
Click to expand...
Click to collapse
I am not a complete nooby. flash_image can be used on (at least) Samsung phones, to flash kernels.
I have a nokia n900(linux kernel)...and i can flash kernels from the phone itself...dual boot maemo OS and android...restore the whole system image on the phone itself...but on neoV...it is not possible.
dont know about other android phones because neoV is my first android.
On PC you can update BIOS, on some motherboards you can do it from Windows, on others you can use some utility in BIOS setup program, on another motherboards you need true DOS and use BIOS flash program, same is with PC video cards, with PDAs...
ameer1234567890 said:
Can anyone tell me why kernel cannot be flashed via flash_image and the like. Is it because /boot partition is locked in Xperia phones? Or because the there is no proper flash_image made for Xperia phones?
Click to expand...
Click to collapse
Because SE xperia phones DONT HAVE recovery partitsion!
taaviu said:
Because SE xperia phones DONT HAVE recovery partitsion!
Click to expand...
Click to collapse
Exactly what does flashing a kernel with flash_image have to do with recovery partition?
ameer1234567890 said:
Exactly what does flashing a kernel with flash_image have to do with recovery partition?
Click to expand...
Click to collapse
The phone's internal memory (not the SD card) is solid-state (flash) memory, AKA NAND. It can be partitioned much like a normal hard drive can be partitioned. The bootloader exists in its own partition. Recovery is another partition; radio, system, cache, etc are all partitions.
Here are the standard partitions on an Android phone:
/misc - not sure what this is for.
/boot - bootloader, kernel
/recovery - holds the recovery program (either clockworkmod or RA recovery for a rooted Evo)
/system - operating system goes here: Android, Sense, boot animation, Sprint crapware, busybox, etc
/cache - cached data from OS usage
/data - user applications, data, settings, etc.
The below partitions are not android-specific. They are tied to the hardware of the phone, but the kernel may have code allowing Android to interact with said hardware.
/radio - the phone's radio firmware, controls cellular, data, GPS, bluetooth.
/wimax - firmware for Sprint's flavor of 4G, WiMax.
During the rooting process, a critical piece of the process is disabling a security system built into the bootloader that protects these partitions from accidental (or intentional) modification. This is what's referred to as "unlocking NAND." The security system can be set to active or inactive. S-ON means the security is in place (NAND locked). S-OFF means the security is off (NAND unlocked). When S-OFF, you have the ability to modify all partitions. With S-ON, you only have write access to /cache and /data. Everything else is read-only.
When you flash a custom ROM, that ROM typically includes a kernel and an OS. That means the /boot and /system partitions will be modified at a minimum. Some ROMs require a clean install, so a format of the /data and /cache partitions is sometimes built into the .zip that you flash. This is essentially doing a factory reset. See next paragraph.
When you do a factory reset (AKA: wipe, hard reset, factory wipe, etc.), you are erasing the /data and /cache partitions. Note that a factory reset does NOT put your phone back to its factory state from an OS standpoint. If you've upgraded to froyo, you will stay on froyo, because the OS lives in /system, and that is not touched during a factory reset. So "factory data reset," as it says under Settings > SD & phone storage, causes confusion. It's not a factory reset. It's a factory DATA reset. Now you know the distinction.
The SD card can also be partitioned to include a section dedicated to storing user apps. To create the partition, your SD card needs to be formatted. Typically a user will copy all the contents in the SD card to a PC hard drive, wipe the card and partition it, and then copy everything back.
Original http://www.addictivetips.com/mobile...plained-boot-system-recovery-data-cache-misc/
taaviu said:
The phone's internal memory (not the SD card) is solid-state (flash) memory, AKA NAND. It can be partitioned much like a normal hard drive can be partitioned. The bootloader exists in its own partition. Recovery is another partition; radio, system, cache, etc are all partitions.
Here are the standard partitions on an Android phone:
/misc - not sure what this is for.
/boot - bootloader, kernel
/recovery - holds the recovery program (either clockworkmod or RA recovery for a rooted Evo)
/system - operating system goes here: Android, Sense, boot animation, Sprint crapware, busybox, etc
/cache - cached data from OS usage
/data - user applications, data, settings, etc.
The below partitions are not android-specific. They are tied to the hardware of the phone, but the kernel may have code allowing Android to interact with said hardware.
/radio - the phone's radio firmware, controls cellular, data, GPS, bluetooth.
/wimax - firmware for Sprint's flavor of 4G, WiMax.
During the rooting process, a critical piece of the process is disabling a security system built into the bootloader that protects these partitions from accidental (or intentional) modification. This is what's referred to as "unlocking NAND." The security system can be set to active or inactive. S-ON means the security is in place (NAND locked). S-OFF means the security is off (NAND unlocked). When S-OFF, you have the ability to modify all partitions. With S-ON, you only have write access to /cache and /data. Everything else is read-only.
When you flash a custom ROM, that ROM typically includes a kernel and an OS. That means the /boot and /system partitions will be modified at a minimum. Some ROMs require a clean install, so a format of the /data and /cache partitions is sometimes built into the .zip that you flash. This is essentially doing a factory reset. See next paragraph.
When you do a factory reset (AKA: wipe, hard reset, factory wipe, etc.), you are erasing the /data and /cache partitions. Note that a factory reset does NOT put your phone back to its factory state from an OS standpoint. If you've upgraded to froyo, you will stay on froyo, because the OS lives in /system, and that is not touched during a factory reset. So "factory data reset," as it says under Settings > SD & phone storage, causes confusion. It's not a factory reset. It's a factory DATA reset. Now you know the distinction.
The SD card can also be partitioned to include a section dedicated to storing user apps. To create the partition, your SD card needs to be formatted. Typically a user will copy all the contents in the SD card to a PC hard drive, wipe the card and partition it, and then copy everything back.
Original http://www.addictivetips.com/mobile...plained-boot-system-recovery-data-cache-misc/
Click to expand...
Click to collapse
As I had mentioned before, I am not a nooby.
ameer1234567890 said:
As I had mentioned before, I am not a nooby.
Click to expand...
Click to collapse
Then show us HOW to install kernel via recovery?
Dont talk about Samsung and HTC option to install kernel via recovery. I have HTC Desire my second phone and yes i know there is option install kernel via recover(also im tested ALL desire roms and kernel already).
SE xperia have just different partitions layout and we simply cant flash kernel via recovery.....BUT i dont want tell you its IMPOSSIBLE.
Be nice and show us how to do that
PS:im tottaly noob.
Boot holds kernel and initrd not the actual bootloader, that is what should be writable. Provided the actual bootloader is not damaged it should be possible, however because there is no recovery partition it is riskier, but s1tool can restore bootloader......
Hmm
Sent from my MT11i using Tapatalk
I have S2(of course i have and xperia neo) and i dont flash with CWM i flash with odin or heimdall; CWM method is not sure.
In my opinion,and i'm NOT an expert, it easy to flash a kernel for xperia with flashtool or using fastboot from adb.
OK guys, you might have misread it. I am looking for a way to flash kernel not just using CWM (eventhough the title says so), but using any method without having to connect to a PC. One such possible method is to use flash_image in terminal, which does not work in my phone.
PS: The fact that I am not a noob doesn't make me a pro.

Moving from link2SD to another apps2SD script

Currently I have an HTC Explorer on the stock ROM with stock kernel, and it is rooted and I use link2SD to move all my apps to my SD card. However, this method does not move the application data. I would like to install a new apps2SD script that will move app data as well as apps, as I am running out of space due to the data.
The problem I am facing is that with link2SD, I am using a FAT32 partition (my current stock kernel does not support ext partitions). Almost all my apps are on this FAT32 partition. I believe if I switch to a different script, I must use an ext partition. I think I will need to install a custom kernel that supports ext partitions (and init.d scripts?) and create a new ext partition.
My questions are these:
1. Will installing a new kernel be enough without installing a new ROM? (If so, can anyone suggest one for the Explorer that adds ext & init.d support? Preferably as few other features as possible, I'd like to stick reasonably close to stock)
2. How can I move all my existing apps from the FAT32 partition to the ext partition, and also move all the data currently on internal storage to the ext partition, without losing anything? (If I back everything up with Titanium Backup, make the switch, and then restore the backup once the script is installed, will that work? If so, do I need to do a wipe at any point?)
3. Which apps2SD script should I use? I have read about several, and have no idea which is best.
4. How do I actually make the switch? Do I uninstall link2SD, remove the FAT32 partition and replace it with an ext2 partition, install the new script in recovery, then boot up? Or would that cause problems with the remnant symlinks made by link2SD? Do I need to do a wipe at some point?
I realise I am asking a lot of questions here, at this point I am beginning to regret not going with a custom kernel and a full a2sd script in the first place. Any help would be much appreciated.
Would like to know also..

[Q] Not enough space for ROM slot 1. Safe Strap.

Trying to install a ROM for the first time and I'm using Safe Strap. I try to install a ROM on slot 1 or any other ROM slot for that matter and it says I don't have enough space for my Data partition. How can I make more space? I tried wiping the internal storage using Safe Strap but it gives me an error. Any suggestions?
gdorman said:
Trying to install a ROM for the first time and I'm using Safe Strap. I try to install a ROM on slot 1 or any other ROM slot for that matter and it says I don't have enough space for my Data partition. How can I make more space? I tried wiping the internal storage using Safe Strap but it gives me an error. Any suggestions?
Click to expand...
Click to collapse
Try to use clean master to clean app and system cache,and put some big data app in the ext-sd,it's an intuitive app https://play.google.com/store/apps/details?id=com.cleanmaster.mguard
for a rom you need at least 2 gb
Some rom will boot only in rom slot 1 with safe strap,(all cyanogen mod "CM 10..1" for exemple) read the developer info
Vallerino WR said:
Try to use clean master to clean app and system cache,and put some big data app in the ext-sd,it's an intuitive app https://play.google.com/store/apps/details?id=com.cleanmaster.mguard
for a rom you need at least 2 gb
Some rom will boot only in rom slot 1 with safe strap,(all cyanogen mod "CM 10..1" for exemple) read the developer info
Click to expand...
Click to collapse
I am having this same issue. I deleted a ton of apps and ran the cleaner and it is still showing that I am short on space. What else can I do? Getting very aggravated.
massappeal16 said:
I am having this same issue. I deleted a ton of apps and ran the cleaner and it is still showing that I am short on space. What else can I do? Getting very aggravated.
Click to expand...
Click to collapse
before flashing a rom, i made factory reset.
Did u try factory reset/wipe?
Yes, if you have a ton if pics, music, downloads, etc on your internal memory transfer it to micro sd. Stated above "For a rom you need at least 2 gigabytes" is mis leading,(if not referring to total partition size) as you are givn a choice of 1, 2 or 3 gig space. I have never used anything over 1gig, and never ran out if space/memory. Factory reset does not clean your phones storage.. I suggest manually deleting/ formatting for best results to get your space/memory back.
XT912 RaZR SpYdEr CDMA
hit ThAnKs if I was helpful!!!
so I just tried Safestrap on my S4, says I have 12MB of space left. I just wiped my entire phone, and it's still at 12MB of space, before and after the wipe, am I missing something?
EDIT: I installed the ATT version of it by mistake, genius me
Same Problem here
I am having the same problem. I have deleted most apps. Deleted all pics & music, still not enough space to flash ROM. I am on XT912 RAZR Rooted.
have a look at this link
I had a similar problem until I found this link, I think I just used the top/first method as I had luckypatcher installed already.
http://jbnote.com/mobile/how-to-fix-insufficient-storage-available-error-in-android-phone/
hope it is a help to you
SafeStrap uses the space on your internal sdcard for creating slots.
Apart from the data, it creates two more partitions viz system and boot so the amount of free space required is (sizeOf) data + 900 MB.
So if you chose say 1GB for data, then you must have about 1.9 GB of free space on your internal sdcard.
Confirm before you try to create a slot.
DROID RAZR with Tapatalk 4
12MB of space left for ROM SLOT 1
hondasarecool said:
so I just tried Safestrap on my S4, says I have 12MB of space left. I just wiped my entire phone, and it's still at 12MB of space, before and after the wipe, am I missing something?
EDIT: I installed the ATT version of it by mistake, genius me
Click to expand...
Click to collapse
So, did any of the suggestions here resolve your issue???
hey, is there is any way to resize the internal system partition. because I am trying to flash a new ROM. but my system partition size is only 450mb and I need around 1gb to flash the ROM. there are different partion like data partition, system partition, cache partition etc, can I resize them a make system partition of around 1gb. my phone karbonn titanium S1.
thank you
akshatrathi said:
hey, is there is any way to resize the internal system partition. because I am trying to flash a new ROM. but my system partition size is only 450mb and I need around 1gb to flash the ROM. there are different partion like data partition, system partition, cache partition etc, can I resize them a make system partition of around 1gb. my phone karbonn titanium S1.
thank you
Click to expand...
Click to collapse
No you can't change the stock system partitions.
This thread is for creating partitions on sdcard using a specific recovery. This is not universal.

Safestrap eating my memory.

Why is this safestrap instaling on the user storage and not on the system partition?
Nimerod said:
Why is this safestrap instaling on the user storage and not on the system partition?
Click to expand...
Click to collapse
Because you have a locked bootloader and safestrap uses the user storage to store the "slot" images you create to hold your different bootable ROMs.
Not much else you can do without having an unlocked bootloader. However, at least with kexec built into Safestrap, you have the ability to boot different kernels, so that's definitely worth it.

Categories

Resources