Hi,
I was trying to install a custom ROM and did the usual procedure of wiping system and cache before flashing through twrp.
However, when I tried to flash the zip file on twrp, I kept getting an error that said the system partion was missing.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried to flash the system.img directly through fastboot but same error.
I went through the adb shell and found out that there is no partion called system in the device blocks. (odm, product and vendor is missing as well).
I'm really not sure how these partitions got wiped out completely and not just formatted. But anyone know what can be done to remake the partitons or any solutions to get a ROM up and running? I of course don't mind wiping and formatting all data as I have made a backup before.
Been trying for different solutions for a week now. Any help would be much appreciated.
system, odm, product and vendor
They are NOT missing but combined into a single partition called 'super'.
/dev/block/by-name/super
NextGenMagisk said:
system, odm, product and vendor
They are NOT missing but combined into a single partition called 'super'.
/dev/block/by-name/super
Click to expand...
Click to collapse
I see, so how does it not recognize those partitions when I try to install a ROM? Any ideas?
From what i can guess from your screenshots is that your device has a GPT with 'super' partition. So, you have to first make sure that the custom ROM you are trying to install is 100% compatible with your device model or not. If no, then find correct ROM with pre-built super partition.
If yes, then get android tools from here: You need root access for this method.
[Closed] Universal SystemRW / SuperRW feat. MakeRW / ro2rw (read-only-2-read/write super partition converter)
Welcome to the one and only, the original, universal, System-RW / Super-RW feat. Make-RW / ro2rw (read-only-2-read/write super partition converter) by lebigmac Also known as: THE-REAL-RW, FULL-RW, EXT4-RW, EROFS-RW, EROFS-2-RW, F2FS-RW...
forum.xda-developers.com
# ./lpdump /dev/block/by-name/super > lpdump.txt
You will get necessary metadata from 'lpdump.txt'. Use that to build your own super partition (all sizes need to be in 'bytes'). For exact steps you can surely find a post on XDA.
Rebuild your own super using the system, vender, etc from the custom ROM. Make sure not to exceed the maximum size allocated for 'super' partition.
Flash it from fastboot and hopefully the device will accept and boot it.
NextGenMagisk said:
From what i can guess from your screenshots is that your device has a GPT with 'super' partition. So, you have to first make sure that the custom ROM you are trying to install is 100% compatible with your device model or not. If no, then find correct ROM with pre-built super partition.
If yes, then get android tools from here: You need root access for this method.
[Closed] Universal SystemRW / SuperRW feat. MakeRW / ro2rw (read-only-2-read/write super partition converter)
Welcome to the one and only, the original, universal, System-RW / Super-RW feat. Make-RW / ro2rw (read-only-2-read/write super partition converter) by lebigmac Also known as: THE-REAL-RW, FULL-RW, EXT4-RW, EROFS-RW, EROFS-2-RW, F2FS-RW...
forum.xda-developers.com
# ./lpdump /dev/block/by-name/super > lpdump.txt
You will get necessary metadata from 'lpdump.txt'. Use that to build your own super partition (all sizes need to be in 'bytes'). For exact steps you can surely find a post on XDA.
Rebuild your own super using the system, vender, etc from the custom ROM. Make sure not to exceed the maximum size allocated for 'super' partition.
Flash it from fastboot and hopefully the device will accept and boot it.
Click to expand...
Click to collapse
Thanks for your message.
I understood what the 'super' partition means now, I will try to build the super partition. It's so weird that even the stock ROM does not have a super partition. (I unpacked it using the payload dump script form xda)
Unfortunately, my phone is now on a bootloader only loop. Cant even load recovery. Sigh.
Will update, thanks for your reply though.
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ONLY FOR NOUGAT FIRMWARE
Working:
ADB
If can possible make a mount / backup or restore any partition, included DATA, restore, backup, flashing...
The settings are saved on CUSTOM partition, and BACKUP's on external storage
MTP
Dont working:
Tell me
Changelog:
RC2 16-03-2017:
Updated UI
New logo and splash screen
Fixed errors on Backup/Restore
Optimized the code
RC1 11-03-2017:
Updated to TWRP base 3.0.3
Data in whole recovery, mount, unmount, backup, restore, flashing .zip files... NO MORE NEEDED DOWNGRADE TO MM
ADB Now can send command and receive
Optimizations...
b9 15-12-2016:
MTP and ADB works at init thanks to: @LastStandingDroid
ADB Keys working thanks to: @LastStandingDroid
Deleted unneded stuff
b8 14-12-2016:
Reworked MTP
Reworked with kernel B336
Updated banner with correct version of recovery
b7 13-12-2016:
Reworked MTP
Removed unnecesary files
Removed DM-Verity v2
b6 08-12-2016:
New Init logo and banner
Deleted parameters for MOUNTING DATA
Deleted splash2
Reworked init.rc and fstab
b2 03-12-2016:
ADB works but no "auth"
MTP works
Backup & Restore of all patitions working (no DATA backup)
Settings of TWRP saved on CUSTOM partition
b1 02-12-2016:
First version working on Nougat
Images
Attached in bottom of the post.
Download:
For install in Android MM (if dont are now in Android N) or for install in Recovery Nougat b*: https://mega.nz/#!tE1XXIaK!ICq1NO1DpLedfdgB0j5DzH4xtEN6jcz2Di8UXfcqSBE
recovery.img for install with Fastboot: https://mega.nz/#!gU91XJjI!V3RcPQ0tDeFNBJAu04cI1gxMqDypEdxs6TQHGF3h0_o
Regards
BadWolfYe said:
Working:
All dont listed in "Dont Working"
Dont working:
ADB
USB MTP
Mount and manage DATA
Download:
For install in FASTBOOT: https://mega.nz/#!JcNCADDA!f4EvXvIJYEPkALmUrG5WDhB-u7pRpcDZ5DvQpQpxlD8
For install in Android MM (if dont are now in Android N):
Im working in fix the error listed up, when i fix all, i work in Revolution Recovery for NOUGAT
Regards
Click to expand...
Click to collapse
Is for VNS-L21 ? Or not?
Why is this called Android Nougat?
The named its called for only work on Android Nougat Firmware....
Adb/mtp fixed...
Working on data partición fix
Oh god i hope you get it sorted, your my last hope with my brick ..... **** me
WTF?
This is no a job, dont need a review for employer's HAHAHAHAHAHA
News:
Data partition still no working...
In this moment recovery save the settings in CUST partition
Backup of all listed partitions CORRECT (tested)
Only can backup to external sd
ADB no work "unathorized" but MTP yes, for activate, go to mount and disable mtp, after, reenable mtp... an boila!
Installation fails at 7 status error (in this moment caused by data partition)
im deleting all unusued stuff on recovery, and upload in the next hours... BETA 2 xd
OP updated
I do not mean to be rude and I appreciate your work, but how is this different from the regular TWRP and from TWRP by Meticulus? I mean there are two rock-solid versions of TWRP, what is the added value of flashing this one?
Anyone READ the TITLE?
This is FOR NOUGAT boot only on NOUGAT firmware and another olds TWRP NO... this is the only recovery boot on NOUGAT...
BadWolfYe said:
Anyone READ the TITLE?
This is FOR NOUGAT boot only on NOUGAT firmware and another olds TWRP NO... this is the only recovery boot on NOUGAT...
Click to expand...
Click to collapse
My apologies, I feel super stupid now. Thanks for your contribution!
Thanks for your work
Thread cleaned of stupidity. Next time we'll talk privately. :good:
Cheers,
Darth
Senior Moderator
TWRP not picking up internal storage, please help.
Recovery updated and reworked...
Hello
I do not understand, I can not manage to make it work.
He shows me cust 177mb
Internal storage 0mb
Micro sdcard 0mb
And I get to nothing. thank you
I understood
BadWolfYe said:
Recovery updated and reworked...
Click to expand...
Click to collapse
Now can i flash directly on the reworked twrp? Like if im going to reflash the b329 + data files? And also the camera fix?
Is there somewhere already a supersu file for root
Then you could root it and then downgrade with toolkit because the twrp he has fixed and thus you could zip the zip yes
Thank you for your great work
Hello, I'm trying to install this Recovery for my P9 Lite in Nougatt, if i in ADB send a command:
"fastboot flash RevRecNP9Lite.img"
I have a error:
"unknown partition 'RevRecNP9Lite.img'
error: cannot determine image filename for 'RevRecNP9Lite.img"
Where is the problem? In ADB?
ExodosPL said:
Hello, I'm trying to install this Recovery for my P9 Lite in Nougatt, if i in ADB send a command:
"fastboot flash RevRecNP9Lite.img"
I have a error:
"unknown partition 'RevRecNP9Lite.img'
error: cannot determine image filename for 'RevRecNP9Lite.img"
Where is the problem? In ADB?
Click to expand...
Click to collapse
It must be "fastboot flash recovery RevRecNP9Lite.img"
Thank You, it works
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/**
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
**/
Working:
Boot
Decryption data
Vibration
flash zip
Android 11 support
Ota update
ADB Sideload
Supported devices:
Mi 10T (apollo)
Mi 10T PRO (apollopro)
Redmi K30S Ultra (apollo)
We couldn't modify /system /vendor /product and /odm, caused by new type of partition, so if you want modify them, use magisk module instead.
NOTE: Use BOOT COMMAND to Encrypt on MIUI. On AOSP you can directly flash.
Install guide:
To boot (Recommended if using MIUI Rom):
Code:
Code:
fastboot boot <twrp.img>
To recovery (Recommended if using AOSP Rom):
Code:
Code:
fastboot flash recovery <twrp.img>
Download: Here
Device Source: https://github.com/mhmdeve/twrp_device_xiaomi_apollo
TWRP Source: https://github.com/minimal-manifest-twrp
Donate: Here
Credits:
@Whyle for base tree
@akshat2012 for fixing Padding
@usmanov_ms for testing
@sewa2k for testing
@apollocustom for testing
After my device enters the menu interface, there is no response to touch.
That's why?
Redmi k30s ?
mhmdeveloper said:
Redmi k30s ?
Click to expand...
Click to collapse
Yes.
Oh!!
I have to look.
Firmware?
fw_apollo_miui_APOLLO_V12.5.3.0.RJDCNXM
Okay I'll lookout
On Mi10T Pro everything works fine so far.
Hi, i have a question, what is the name of that Magisk Module? the ODM partition failed when flash Xiaomi EU makes me crazy
it is showing internal storage zero, I cant copy any file. Tried format multiple times, repair also.
Hi mhmdeveloper, will you support to modify system by file manager(TWRP) in the future?
Thanks.
Hi, thanks, installed today and looks working good and without 'red bootloop error lines'.
Hi, just want to say that this twrp build is much better than the one built by Whyle. ADB sideload is a lifesaver! Thanks op!
is it possible restore data backup with this recovery and keep current rom?
because with whyle it failed (either don't work of rom doesn't understand it had data and treat it like unknown encryption = data reset)
and I lost everything
the data format on a11 does not work and does not see the phone memory, and twrp from while works as it should despite a few red lines of text
I got excited seeing an update to TWRP, but it seems even this doesn't support flashing it to the MIUI ROM and cannot be used to decrypt the data. Why is this?
Touchscreen not working in this TWRP with K30S.
Wanted to flash 12.5.3 update with my old TWRP version (one advised in root guide) and stuck in TWRP recovery boot page.
Does flashing this recovery mean I've to erase all data?
Just have to flash from fastboot and that's all?
I need help. by means of this version 3.5.2. I used the advanced formatting option with "yes" and cleared the cache and internal memory data. now the device entered a bootloop always starting the twrp when I start the phone and the most serious error I have is that no pc detects my computer. neither my flash nor adb nor through the sideload help help
comglorerate said:
I need help. by means of this version 3.5.2. I used the advanced formatting option with "yes" and cleared the cache and internal memory data. now the device entered a bootloop always starting the twrp when I start the phone and the most serious error I have is that no pc detects my computer. neither my flash nor adb nor through the sideload help help
Click to expand...
Click to collapse
I also had this.
Workaround is to get to fastboot or recovery one of these.
Press
Power + Volume Down = fastboot / bootloader
fastboot devices to check if device is showing
Power + Volume Up = Recovery
adb devices for same.
Let me know if it works.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Disclaimer
I am NOT responsible for bricked devices, dead SD cards or any
damage to you device. You are doing this at YOUR OWN RISKS. It's
reccomended to do a full SYSTEM BACKUP in case something went wrong.
Features
Tweaked with Build.prop for better experience
Deodexed for easy system apps modifications
DeKnoxed to remove annoying settings
Decrypted for keeping data when performing system changes trough TWRP of CWM recovery
Pre Rooted with Magisk to get superuser access and for some interesting advantages
Minecraft PE 1.19 & Geometry Dash 2.111 preinstalled (removable with root) so no need to pay for them
Many others features coming from stock Oreo ROM
How to install
First of all, make sure you have downloaded the ROM flashable zip (Download link in bottom of this post)
Put the zip file in your phone storage or SD card if not already in
Reboot in custom recovery such as TWRP or CWM with hardware buttons (if not installed, this is a Tutorial)
Go to WIPE section and select advanced wipe
wipe Data, System, Preload, Cache-Dalvik, Cache and Internal Storage (I highly recommend to do a full backup of your ROM BEFORE WIPING)
Now, go back to home and to INSTALL section
Select storage where the ROM zip is stored and choose it
Start the operation with -zip signature check- unchecked or it will fail
If everything goes well, reboot to system and after booted, complete the setup wizard
That's it
Devices supported
Samsung Galaxy A5 2017 (SM-A520W)
Maybe F, K, L and S variants
Not for DS (dual sim) versions and Snapdragon
Requirements
A computer (for custom recovery flash)
Latest Oreo bootloader unlocked (developpers options from settings)
SD card (at least 4Gb)
Internet connection
A minimum of knowledge in Samsung phones
TWRP/CWM/OrangeFox recovery installed
Downloads
flashable rom zip file---------- - Mod Edit : Link Removed -
Thanks to
AndroDef------ For his helpfull Classy Kitchen
Topjohnwu------ For his irreplacable Magisk Root
sfirmware.com------ For the stock TAR.MD5 file
If you see some bugs, please inform me[/CODE]
I would appreciate if someone gives me comments and reports errors and bugs
Duplicate thread, see this one :
(ROM)(A5)(Stock)(8.0) N'CreamOSv2 (Tweaked, Deodexed, Busybox, DeKnoxed, Decrypted and Rooted)
Disclaimer I am NOT responsible for bricked devices, dead SD cards or any damage to you device. You are doing this at YOUR OWN RISKS. It's reccomended to do a full SYSTEM BACKUP in case something went wrong. Features Tweaked with Build.prop...
forum.xda-developers.com
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Disclaimer
I am NOT responsible for bricked devices, dead SD cards or any
damage to you device. You are doing this at YOUR OWN RISKS. It's
reccomended to do a full SYSTEM BACKUP in case something went wrong.
Features
Tweaked with Build.prop for better experience
Deodexed for easy system apps modifications
DeKnoxed to remove annoying settings
Decrypted for keeping data when performing system changes trough TWRP of CWM recovery
Pre Rooted with Magisk to get superuser access and for some interesting advantages
Many others features coming from stock Oreo ROM
Busybox added to xbin
How to install
First of all, make sure you have downloaded the ROM flashable zip (Download link in bottom of this post)
Put the zip file in your phone storage or SD card if not already in
Reboot in custom recovery such as TWRP or CWM with hardware buttons (if not installed, this is a Tutorial)
Go to WIPE section and select advanced wipe
wipe Data, System, Preload, Cache-Dalvik, Cache and Internal Storage (I highly recommend to do a full backup of your ROM BEFORE WIPING)
Now, go back to home and to INSTALL section
Select storage where the ROM zip is stored and choose it
Start the operation with -zip signature check- unchecked or it will fail
If everything goes well, reboot to system and after booted, complete the setup wizard
That's it
Devices supported
Samsung Galaxy A5 2017 (SM-A520W) the one which i have tested (works fine)
Maybe F, K, L and S variants (Tell me if it works please)
Not for DS (dual sim) versions and Snapdragon
Requirements
A computer (for custom recovery flash)
Latest Oreo bootloader unlocked (developpers options from settings)
SD card (at least 4Gb)
Internet connection
A minimum of knowledge in Samsung phones
TWRP/CWM/OrangeFox recovery installed
Downloads
flashable rom zip file---------- N'CreamOS_8.0_v2_a5y17lte
Thanks to
AndroDef------ For his helpfull Classy Kitchen XDA Link
Topjohnwu------ For his irreplacable Magisk Root Magisk Github
sfirmware.com------ For the stock TAR.MD5 file SM-A520W(XAC)
If you see some bugs, please inform me
its just like samsung experience, i relly like it )
It is working fine on my Galaxy A520F Exynos Model, so you can check that out from the compat. checklist. For some reason the os thinks this is a A520W, but this is a F Model. I had a problem where TWRP said that flashing failed with error 7, but then I restarted it and I flashed it and it worked. Also you actually don't need a SD Card for the flasheble zip, you can actually just turn MTP on and Mount the DATA partition and copy the zip from your computer to your phone. This ROM is pretty good!
Oops, wrong post.
First I would just like to say this module mysteriously appeared on fox magisk module manager a few weeks ago and I am not the coder.
Links to backup & restore module on github:
GitHub - ziandzivan/data_backup: User Data backup creator from system for Google Pixels and other devices. (subsequent restoring by data_restore.zip script)
User Data backup creator from system for Google Pixels and other devices. (subsequent restoring by data_restore.zip script) - GitHub - ziandzivan/data_backup: User Data backup creator from system f...
github.com
GitHub - ziandzivan/data_restore_Courier: Courier-module for delivering to user and updating a Script data_restore.
Courier-module for delivering to user and updating a Script data_restore. - GitHub - ziandzivan/data_restore_Courier: Courier-module for delivering to user and updating a Script data_restore.
github.com
I tried both of them and they work pretty good / fast with a few bugs, such as: Using OTG storage causes the backup to work slow and fail,maybe it's the OTG I was using. I did this backup and restore operation on OnePlus 9 pro. It works fast if u backup to internal storage.
I know people are always looking for internal storage backup, I believe this module does the job.
You can backup without being in TWRP, but I believe this module requires people to be in TWRP recovery to restore internal storage backup.
/BUMP I noticed another few bugs with this script SOMETIMES. It does restore data and internal storage perfectly, but sometimes it may cause systemui to repeatedly bootloop. If that happens, you need to format everything and reinstall from scratch the firmware and then restore again the data backup
immortalwon said:
bugs, such as: Using OTG storage causes the backup to work slow and fail,maybe it's the OTG I was using
Click to expand...
Click to collapse
You have a trouble with your USB OTG. Use better SSD storage device or use intSD.
It works good. Here is mine (for example):
Spoiler: Pictures
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Restoring speed from SSD USB-OTG in TWRP:
from internal storage in running System :
So, you can see the restoring from my USB-OTG is faster.
Just out of curiosity has anyone tried side loading the restore zip to their phone with a temporary recovery such as lineage or some other similar aosp recovery? I read it supposedly works by flashing it through twrp although it's already on the phones internal storage. I wonder if someone could potentially edit the restore zip to tell the phone it's an update or a rom being flashed and make this work if it won't work as is. I may try this sometime just to see what happens. I imagine it won't be that simple or someone would have already done it but how awesome would it be if it did work!? IMO it would be the next best thing to having twrp on my pixel 7 If anyone has any thoughts or suggestions on how/if this could be possible please let me know!
Thanks,
DroidRommer