Related
I just saw an interesting thread in the development section that explains an alternative to the Death SPL. The method there lets you flash ANY rom on any SPL, but I dont really understand how it works.
The thread can be found here: http://forum.xda-developers.com/showthread.php?t=704560
So basically, you shrink the cache partition to allow for more room for the actual ROM(which partition does that go in?)?
To do this do we edit the boot.img in the ROM update.zip? What else do we do?
Could someone explain this in a way a 9th grader could understand?
kingkurry said:
Could someone explain this in a way a 9th grader could understand?
Click to expand...
Click to collapse
Take file by firerat, flash file. omgroflpartitons.
If you don't understand the instructions as they are, wait for it to be perfected before you try anything. This will probably end up being integrated into releases that need it, so you don't need to worry about the specifics at the moment.
Will that patch file work for all ROMs. He said its only been tested with CyanogenMod 5. And I want to understand what im doing, not just do it without thinking about it...
Also, does the recovery patcher decrease the size of the partition that holds the recovery image?
Does it permanently change the size of the recovery partition?
When you flash a ROM, what partition is it being flashed too? Is this the one being increased in size?
What does the boot.img in an update.zip package hold, and is that copied to the boot partition?
Sorry but my curiosity is killing me
OK well to break it down we have 6 partitions on the internal memory:
Misc - Here be dragons
Recovery - Contains recovery system (+seperate recovery kernel) - recovery.img lives here
Boot - Contains kernel & important initialization stuff - boot.img lives here
-------------
System - Contains the whole android system (the "ROM", if you like).. everything else from an update.zip apart from the boot.img
Cache - Used by system and recovery for temporary storage
Userdata - Contains all personal data, downloaded apps, settings etc.
The first three partitions must be left at the default size so don't worry about them.
What this patch does is pass a command to the kernel which remaps the 3 large partitions at boot time. Since we're flashing system images from recovery, we also need to pass the same command to the recovery kernel before attempting to flash the main system, or we'd be writing to one place then telling the kernel to look for it in another.. bad idea.
This method allows any partition setup you like, but the most useful at the moment (and this is the way firerat has set up his scripts to suit cm5) is to make the /system partition just the right size for the "ROM" with a bit of breathing space, make the /cache partition a minimal size for the recovery system to use, then have /userdata fill the remaining space so we can load it up with apps. Since we've reduced cache to a minimal size, it's redirected at boot time to a place on the sdcard instead.. this give us maximum space to divide between /system and /data with no wastage.
Does that help at all..?
Thanks dude. That does help a lot.
Just wondering though, how much breathing space do u need in the system partition?
What does the recovery system use the cache partition for and how do we know what "a minimal size for the recovery system to use" is?
Is it possible to reduce the userdata partition to the minimum possible size a partition can be(if i recall correctly it was 128kb) and use an ext partition on your SD card instead?
If we shrink the Cache partition a lot, does this mean we have to use linux swap to compensate for the lowered amount of cache?
Also do we have to remap the partitions every time we flash a new ROM?
And what are the "dragons"?
kingkurry said:
And what are the "dragons"?
Click to expand...
Click to collapse
He's saying that it's just there. There could be anything from nothing there to a text document containing the ingredients to the cure of AIDs.
Well what about every thing else? Can you guys help me with that? Also what is the total size of all 3 of the big partitions combined?
So, I figured I'd set up the scenario first in hopes to help make this understood:
1. Got the device
2. Booted/Updated to 5.0
3. Rooted using CF Autoroot
4. Remained on Stock 5.0 + Root (Stock bootloader/recovery)
- 1st "OFFICIAL" ROM came out so like the gentle flash'aholic I am, I rushed and downloaded [ROM][Unofficial][5.0.2][alpha/wip] Resurrection Remix v5.2.6[victara]
1. I installed TWRP via the Google Play App, (I think i was on 2.8.3.0)
2. Rebooted into TWRP, and did a FULL BACKUP (saved locally)
3. Formatted Davlik, System, Data, Internal Storage, Cache
4. Rebooted into TWRP, pushed the ROM files ([ROM][Unofficial][5.0.2][alpha/wip] Resurrection Remix v5.2.6[victara])
5. Flashed the ROM, GAPPS, SuperSU, Rebooted.
After about a minute of booting into the new ROM (new red loading animation) I started to get "encryption unsuccessful", and the only option was to factory reset phone, after which nothing happened, my guess was because of the custom recovery.
What was my error, and how do I prevent this from happening again?
My thinking is that wiping the Cache/System/Data/Internal/Davlik partitions somehow messed up some function someplace?
To fix it I took steps in this thread (http://forum.xda-developers.com/moto-x-2014/help/lollipop-update-failing-how-troubleshoot-t2961633) - thanks @randyklein
-Download "Official 4.4.4 Full Restore Images" from http://www.graffixnyc.com/motox.php# and extract. Move recovery.img, boot.img, and system.img into adb folder
-Boot into fastboot, plug in USB
-Using mfastboot v2, run the following commands:
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
How do I avoid this in the future if I decide to try a custom ROM/Recovery again?
Same problem...
Format data in twrp to fix encryption error
CWick4141 said:
Format data in twrp to fix encryption error
Click to expand...
Click to collapse
will i lose my twrp backup ?
marquesini said:
will i lose my twrp backup ?
Click to expand...
Click to collapse
Data partition just stores your apps (if not pre-loaded into system partition via ROM), and any data associated with them, so it leaves the Internal SD Card partition alone.
What concerns me is that I already wiped data, and I think I formatted the data partition as well, and still had the issue.
I'll have to try again soon.
I did a full wipe and then formated the data, then installed the ROM,gaaps,and supersu beta.
Got it working with root.
Shemploo said:
Data partition just stores your apps (if not pre-loaded into system partition via ROM), and any data associated with them, so it leaves the Internal SD Card partition alone.
What concerns me is that I already wiped data, and I think I formatted the data partition as well, and still had the issue.
I'll have to try again soon.
Click to expand...
Click to collapse
Formatting data in twrp is not the same as wiping data
CWick4141 said:
Formatting data in twrp is not the same as wiping data
Click to expand...
Click to collapse
True, that is why I said in above post that I think I formatted it as well, but being as I'm not certain I'll have to do it again to be sure.
Shemploo said:
True, that is why I said in above post that I think I formatted it as well, but being as I'm not certain I'll have to do it again to be sure.
Click to expand...
Click to collapse
You would know if you formatted data since it erases everything including internal storage
CWick4141 said:
You would know if you formatted data since it erases everything including internal storage
Click to expand...
Click to collapse
Alright, I booted TWRP, and clicked "Data" then "Repair/Change File System" it's currently showing f2fs, my format options are EXT2, EXT3, EXT4, FAT.
I think I want EXT4 right?
UPDATE: I tried EXT4 as every partition seems to use it, and from past experience, and It's working!.
Thank you for nudging me in the right direction.
edit: wrong thread
now I'm not new to android but I just for this nexus 6 with 64 gigs of storage... for some reason the system is 35 gigs anyone know how I can slim that down
Did you manually flash a stock ROM, and did you flash the userdata.img? If so, back up everything as I believe you'll need to do a factory reset to fix the problem. The userdata.img by default is for a 32GB system.
Strephon Alkhalikoi said:
Did you manually flash a stock ROM, and did you flash the userdata.img? If so, back up everything as I believe you'll need to do a factory reset to fix the problem. The userdata.img by default is for a 32GB system.
Click to expand...
Click to collapse
I flashed the img file from scratch... that I pulled off of X d a
For curiosity sake, link please?
In any case, never flash userdata.img on a 64GB device; this means you cannot use the batch file Google includes with their ROM packages. The image partitions internal storage as 32GB and leaves the remainder unallocated. Android lumps the unallocated space with system.
Good Morning, I want to upgrade brother device to new version of android (because he can`t install security updates for unknow reasons), but I affraid that he loose all apps and settings (he is a firefighter and have app from firefighter station which signals dangerous traffic etc.) So my question is can I update downloaded stock ROM via TWRP (adb sideload) without fears that he loose everything?
iHusky said:
Good Morning, I want to upgrade brother device to new version of android (because he can`t install security updates for unknow reasons), but I affraid that he loose all apps and settings (he is a firefighter and have app from firefighter station which signals dangerous traffic etc.) So my question is can I update downloaded stock ROM via TWRP (adb sideload) without fears that he loose everything?
Click to expand...
Click to collapse
The only thing that will take your fear, is a backup of all important partitions (boot, system, data, vendor, efs, persist), stored externally, plus a copy of the internal storage content, also stored externally.
With that you should be able to restore everything to the exact point it is at right now, so you'll really need to mess up hard to not come out of basically any situation with those partitions saved.
As for your inital question:
Why don't you just update via ota if you wanna stay on stock?
Phil_Smith said:
The only thing that will take your fear, is a backup of all important partitions (boot, system, data, vendor, efs, persist), stored externally, plus a copy of the internal storage content, also stored externally.
With that you should be able to restore everything to the exact point it is at right now, so you'll really need to mess up hard to not come out of basically any situation with those partitions saved.
As for your inital question:
Why don't you just update via ota if you wanna stay on stock?
Click to expand...
Click to collapse
Because, brother have error, while try install security updates, but he have from March this year
And this is not possible to make update, because after click backup (Data partition) I get error "cannot create data/media/0/TWRP
iHusky said:
Because, brother have error, while try install security updates, but he have from March this year
And this is not possible to make update, because after click backup (Data partition) I get error "cannot create data/media/0/TWRP
Click to expand...
Click to collapse
Okay, so maybe first copying internal storage content to your PC and backup important apps would be sufficient then.
For apps you can use Titanium Backup (good, but makes troubles on android 10 at the moment), Swift Backup (recommend by many others) and more.
These backup solutions save apps and app data on your phone, so copy that to an external place, or you might lose them if you need to format data (which I'll suggest).
After your "backups" are made, I would wipe every partition in each slot, which you can also achieve with a "fastboot -w", and then also format data - the one where you need to type "yes" (which will also erase all internal storage content, but most probably will also solve your troubles).
From here there are tools like miflash or fastboot images to reflash stock (inform yourself about them, before you start all that!).
Be sure to flash the latest one right away, so you won't be in the need of "dirty" updates immediately again.
Afterwards, you can copy back the internal storage content and the folder of the backup app, and restore the previously saved apps.
Phil_Smith said:
Okay, so maybe first copying internal storage content to your PC and backup important apps would be sufficient then.
For apps you can use Titanium Backup (good, but makes troubles on android 10 at the moment), Swift Backup (recommend by many others) and more.
These backup solutions save apps and app data on your phone, so copy that to an external place, or you might lose them if you need to format data (which I'll suggest).
After your "backups" are made, I would wipe every partition in each slot, which you can also achieve with a "fastboot -w", and then also format data - the one where you need to type "yes" (which will also erase all internal storage content, but most probably will also solve your troubles).
From here there are tools like miflash or fastboot images to reflash stock (inform yourself about them, before you start all that!).
Be sure to flash the latest one right away, so you won't be in the need of "dirty" updates immediately again.
Afterwards, you can copy back the internal storage content and the folder of the backup app, and restore the previously saved apps.
Click to expand...
Click to collapse
I tried MiFlash, but without wipe anything, and it don`t upgrade version of system
But if I must, flash 2 slots A/B using MiFlash or one slot (A) is for system?
You can just download the zip file with version u want from the site below and flash it via TWRP making cache and dalvik cache wipes and changing slots at the end.
https://mifirm.net/model/jasmine.ttt#zip-mif
pfss said:
You can just download the zip file with version u want from the site below and flash it via TWRP making cache and dalvik cache wipes and changing slots at the end.
https://mifirm.net/model/jasmine.ttt#zip-mif
Click to expand...
Click to collapse
So, I don't need
to flash second slot?
iHusky said:
So, I don't need
to flash second slot?
Click to expand...
Click to collapse
Just if u want. It's not necessary.
In october I updated mine this way but forgot to change the slot before rebooting to the system and realized that was in the old Android version. I just went to TWRP again and changed slot. After rebooting, the phone was in the updated Android One.
pfss said:
Just if u want. It's not necessary.
In october I updated mine this way but forgot to change the slot before rebooting to the system and realized that was in the old Android version. I just went to TWRP again and changed slot. After rebooting, the phone was in the updated Android One.
Click to expand...
Click to collapse
I tried using fastboot and MiFlash but after all it stuck on bootloader
iHusky said:
I tried using fastboot and MiFlash but after all it stuck on bootloader
Click to expand...
Click to collapse
I just updated mine to November patch downloaded from here: https://mifirm.net/downloadzip/4197
I entered fastboot mode, executed
Code:
fastboot boot my_twrp_image_file.img
In TWRP made de wipes, flashed the ROM, changed slot and rebooted phone. It looks like it's normal.
Hi there everyone!
A few days ago, I was wondering about taking a full backup of my phone. I thought about titanium backup, but I also red something about extracting a partition as an image from the device. And then, I came up with an idea:
Is it possible to extract the userdata and the data partition as an image on this device? (I know that boot image can be extracted)
And if it's possible, after a full wipe and reflash of the phone, can I also flash these two images to get back my user data and the data of my apps? Or will it be enough?
As far as I know, these two partitions store most of the data, maybe system stores data too, like system apps.
Can you also provide me some commands for the process?
Thank you!
gurtnyi said:
Hi there everyone!
A few days ago, I was wondering about taking a full backup of my phone. I thought about titanium backup, but I also red something about extracting a partition as an image from the device. And then, I came up with an idea:
Is it possible to extract the userdata and the data partition as an image on this device? (I know that boot image can be extracted)
And if it's possible, after a full wipe and reflash of the phone, can I also flash these two images to get back my user data and the data of my apps? Or will it be enough?
As far as I know, these two partitions store most of the data, maybe system stores data too, like system apps.
Can you also provide me some commands for the process?
Thank you!
Click to expand...
Click to collapse
use twrp for that
tutibreaker said:
use twrp for that
Click to expand...
Click to collapse
Does it also backup the full data partition including /data/media ?