So after moving to this phone form a rather humble galaxy nexus the partition layout is much more complex I know what a lot of the partitions do but a few I have no clue.
So in the interest of explorations let's see if you guys can help fill me in:
Boot (Self explanitory the boot partition for the kernel bootstrap)
Cache (Self explanitory the standard android cache partition)
Recovery (Recovery partition where TWRP goes or stock recovery)
System (System partition that is in use aka the OS)
System Image (??? What is this an image of system as shipped form factory?)
Data (User data partition)
Modem (??? The factory modem drivers?)
EFS (I hear this is the IMEI MAC and other modem setting the phone needs for connectivity)
Question mainly revolves around the system image partition I take it this is put in place to recover from a very bad flash from factory. Out of curiosity does this every get overwritten say during official updates? I'm curious if anyone knows if it's possible to get the system image partition back after a wipe it's a possible mod say after warranty period although right now I wouldn't touch that 3GB partition.
It's supposedly a "feature" of TWRP used to create a stock ROM image in case you ever want to restore to the original ROM or when you want to get OTA updates.
Don't know how accurate that info is, as I've just found it by googling a bit. It's present on other, older, phones too. So it's definitely not unique to OnePlus.
Related
Hi all,
I have a nexus 7 running Android 4.1.2 stock w/ root. Some months ago, I disabled the OTA update notification - but I can't seem to remember how!
I want to now re-enable OTA updates so that I can update to the latest android version, and not lose my installed apps.
I've searched the device for FOTAKill.apk inside /system/app, and its not found
I've also searched for frozen / hidden apps using Titanium Backup Pro... nothing
When I enter Settings -> About Tablet -> System Updates... it says I'm up to date... but I'm not, considering I'm running 4.1.2.
Any help or pointers in re-enabling OTA is appreciated!!
- make a full nandroid backup.
- using fastboot, flash the system.img file from the 4.2.2 factory image to the system partition.
- using your custom recovery, reflash a SuperSU root kit bundle.
- using the custom recovery, wipe cache and dalvik-cache.
If you don't like the result, restore the nandroid backup and proceed in a different fashion. It will probably break things like stickmount and any other changes that you caused in /system.
Note the above method is for use by lazy and sloppy users. A better approach is to make TiBu backups of only your market apps, bite the bullet, and start from scratch with a flash & (new) configuration of a pure stock ROM. In any case, every conceivable procedure should start with making a full nandroid backup and getting it copied to a safe place off the tablet.
I will also say that unless odd problems crop up, the portions of the factory install procedure (using fastboot) that deal with erasure or flashing of the userdata partition should be skipped, as these steps completely wipe your /data storage - including your /sdcard area in /data/media/0 and any CWM/TWRP nandroid backups!
It's not really clear why these steps would be needed unless the /data ext4 filesystem in the userdata partition got corrupted somehow. A more sly approach would be to use the custom recovery's "factory reset" procedure to clean up /data - either before or after flashing the factory ROM - and completely skip anything that touches the userdata partition in the factory install instructions.
good luck
can i install Stock Firmware after reparation internal memory by twrp?
if i can flash so my partitions will change or not and what other problems can occur?
faizynadim said:
can i install Stock Firmware after reparation internal memory by twrp?
if i can flash so my partitions will change or not and what other problems can occur?
Click to expand...
Click to collapse
https://firmware.center/firmware/Motorola/Moto G4 (Plus)/
After u install twrp recovery you don't modify your stock rom though no ota updates.but u can replace it with stoct recovery again.. if u mess up with stock rom yeah u can get it from the above link ..
i am asking about re partition...i am not asking about briking device or flashing stock rom...
Did modify the system partition or only the internal storage?
i have not changed yet.....i am asking if i change the partition of system and data partition...then i will be able to flash stock rom or problems will occur...
Ok, now changing the size of the system partition may create problems if you try to flash the stock img files, I think
ok..i will try that... ?
Whatever you do, don't reduce the size of the system partition, if you want to flash stock ROM later...zips should work fine though. I have seen people repartition xiaomi mi 3 phones and install custom roms.
faizynadim said:
i have not changed yet.....i am asking if i change the partition of system and data partition...then i will be able to flash stock rom or problems will occur...
Click to expand...
Click to collapse
What are you hoping to achieve with changing the partitions (e.g. are you changing the format of the partitions to ext4 or f2fs? Or are you changing the sizes of the partitions)?
If you're changing the partition sizes, I personally would leave the sizes alone, unless you're confident in the size of the partition that the stock ROM would need (and need in the future). From what I see on my device running Nougat NPJS25.93-14.4, cache (ext4) is 256 MB, system (ext4) is 2.5 GB and data (f2fs) takes up the rest of my internal storage.
As for changing formats, I don't know if the stock ROM will work with a system partition not formatted as ext4. Cache may or may not work with f2fs. Again, what are you hoping to achieve?
I want that nobody can flash stock rom on my phone normally....i have cerberus installed as root and if any theif can install firmware so that is useless and theif can enjoy using my phone...so i want to change partition sizes to make it difficult for anyone to flash factory images.
faizynadim said:
I want that nobody can flash stock rom on my phone normally....i have cerberus installed as root and if any theif can install firmware so that is useless and theif can enjoy using my phone...so i want to change partition sizes to make it difficult for anyone to flash factory images.
Click to expand...
Click to collapse
Speaking from my humble (and maybe ignorant) opinion,
I had a few experiences modifying partitions from other devices in the past (i did it no more than 3-4 times), i can say that when you flash a full stock factory image, normally, all the partitions recover his original sizes and formats.
All the devices that i modified included the General Partition Table (gpt.bin) file and the FSTAB config instructions into his full factory images, and from what i saw on the G4 plus, it includes these files too.
Here you have the complete partition table list taken from my G4 plus running 7.0 (NPJS25.93-14-4).
ohhh thanks ?
Delete
unless rooting you can technically flash all to either one as far as I'm aware, as long as they are all flashed to the same partition. The reason for two of them is so that have another fully functional image on the other partition in case things go awry.
First I have a One Plus 6 (so Treble A/B) configuration, been using it since 5.1.5 (as I bought it the first day)
TWRP 2.3.3.0 currently being used.
Note as stated the partitions are decrypted, AKA no need to decrypt when entering TWRP.
1. The foremost issue I have is that flashing a new pair of system's system_a, system_b should not result in being unable to boot every time (now I have decrypted internal storage so that is not what is the cause of the failures), there is simply no chance of upgrading when encrypted which I can understand.
2. Re-flashing the previous working System_a and System_b should boot even if the newer flash failed (assuming you clear cache), it will not do so.
3. Restoring TWRP (system and data) should also work, to restore a working state (heck as nothing here has touched data, but restoring it anyways to be safe) we should be able to simply restore system (again it will not boot after restore). Simply put restoring system via TWRP seems nearly impossible.
4. I've never seen this device boot after installing TWRP to the system partition using custom ROM, (I got it to work once and only once with Oxygen), so the only way to safely boot twrp is via fastboot.
Basically on my OnePlus 6 the only way I can update from v1 to v2 say for a monthly security update is to wipe restore the phone to the default OS (Oxygen in this case), this destroys all Data, then flash my way back to the custom ROM. In my case normally this means re-flashing system_a and system_b, formatting data (again), flashing no encrypt, then magisk and finally restoring backups made in Titanium Backup (zip's), this takes me hours and is not something one can just do.
While at it all Treble instructions say flash system_a and system_b , but upgrading from v1 to v2 should only require updating the system currently in not use (say system_b if booting from system_a) and clearing data then switching to system_b as the boot from TWRP. If the boot fails on upgrade I should then simple be able to switch back to booting from system_a, clear cache and boot as if nothing changed, why is this nor supported or even commented on? Is this not the reasoning behind treble?
Basically I think Treble has much promise, but at least my experience with the Oneplus 6 is that is it is not safe for use, far too often I simply find I have no way to upgrade to even restore the phone on failure (a computer which is what a phone is) without a restore-able backup is untrustworthy, and not even being able to flash TWRP makes it worse (or would if TWRP backups actually worked).
This post is the result of 3 months of fighting with the phone and Treble and trying many different ways to ensure clean upgrades and backups all without any success. Simply put I'm tried and unable to come up with a valid method which works with this phone and Treble to allow for upgrades (for security fixes, something I've done for years prior to Treble without issue) or even backups I can safely restore using TWRP.
Thanks,
ERIC
I have the same issues. I also did another mistake and updated to pie beta 3. Now everytime I do something wrong, it goes directly to qualcomm crash dump mode and to be able to revert it back, I need to flash all partitions from fastboot once again to make it work... I don't like A/B partitions... It seems to cause more issues than what it offers.
twrp restore
I am having the same issues you described also when simply restoring from TWRP, even if I have been thinkering with my phones for a while.
Do you have any suggestion about restoring?
Thank you
Fabio
Hello guys,
I had Lineage OS installed on my Galaxy S10+ and it got into boot loop after my phone lost power a few times because of low battery. The system halts at the Lineage Logo animating forever.
The problem is I canont access encrypted files on /data partition as it seems default Samsung encryption is used (and I have not disabled encryption when I was installing Linaage - I know - my mistake...) What I'm thinking to do is to do a dirty flash of the same system or an upgrade.
But before I will do it, I would like to do full backup of /data partition - sector by sector, so if my dirty flash won't work I can restore /data partition again and try to fix it again without loosing my data.
So my question is: How can I backup whole /data partition as an image? And how can I restore it?
My system is going into boot-loop, but I can get into recovery.
Thank you very much!!!
Encryption keys not withstanding it's the user partition that's likely been corrupted. You see where I'm going with this?
You try safe mode?