not at all, this is to expand system partition to install larger GSIs, fo rtht a i needed system and userdata rm first to resize system
Recommended and tested TWRP Recovery
- Thread starter -Alf-
- Start date
I would say ANE has a pretty big system partition, but it's your choice.
System resizing makes sense on Honor 9 lite which is 2312M on EMUI 9.1.
no ideas on how to create this parttition labes?
seems like the only thing stopping the progress, even reverting to original start and ends it still doesnt create labels for rm partitions
seems like the only thing stopping the progress, even reverting to original start and ends it still doesnt create labels for rm partitions
Are you a developer, making roms or staff like that?
Thank you again, the tool you shared here truly helped restore my partitions and back to rooted Android 9.1.
The tutorial I followed somewhere around XDA had a partially functional parted(~472kb) file, but the parted(1.02mb) file in the tool you shared did the trick and i was able to set labels to my removed partitions.
Though I was unable to boot any GSIs probably due to kernel/vendor, am happy the device was never bricked modifying partitions the way I did initially.
All Nippon GSI reboot to bootloader, Nazim/phh GSI hang on the unlocked bootloader warning screen, I tested from Android 9 to 13 GSI, lineage, spark, crDroid, pixel GSI, OEM(Nokia, Samy, Huawei)
Installation by : fastboot install system xxxxx.img
No dynamic partitions
No symless updates support
arm64-ab
Last edited:
because they are not phhusson based gsi.
Have you tried anything from the P20 lite section? For example Pixel Experience Plus [11] .
And I hope you do a factory reset in stock recovery after installing system.img
(before booting up the ROM!)and it may also be necessary to flash vbmeta, taken from the stock set or from Google, vbmeta link
Command:
fastboot flash vbmeta vbmeta.img
Download vndk-lite version, because of system r/w mode.
P.S.: One more piece of advice if I may - try installing AOSP [11] from Phhusson first, e.g.
this one
If the installation fails, other Treble ROMs might not work on your phone either.
Last edited:
Hi,
I'm picking up my work on the P20 Lite, but I need to seek advice, because my notes are not as complete as I could wish. My device currently has the GAGUGA 3.2.1-0 installed over erecovery, which was where I left off. I don't exactly recall what this permits me to do or not?
Also, I noticed that the official TWRP recovery is newer, so I wonder if I should go with that instead?
(I am building Ubuntu Touch based on Android 9.)
Finally: this page seems has been updated since last I worked on this. It details procedures that are very slightly different from what I was doing last year. Is this the guide to follow now?
I'm picking up my work on the P20 Lite, but I need to seek advice, because my notes are not as complete as I could wish. My device currently has the GAGUGA 3.2.1-0 installed over erecovery, which was where I left off. I don't exactly recall what this permits me to do or not?
Also, I noticed that the official TWRP recovery is newer, so I wonder if I should go with that instead?
(I am building Ubuntu Touch based on Android 9.)
Finally: this page seems has been updated since last I worked on this. It details procedures that are very slightly different from what I was doing last year. Is this the guide to follow now?
This TWRP is missing here:
https://forum.xda-developers.com/t/how-to-change-bl-unlock-code.4226815/post-84401663
Latest TWRP may not be fully compatible with hi6250 if not modified.
Thanks for the two replies above.
I have succeeded in building an Ubuntu Touch version based on Android 9 (Halium 9) and got the device to boot. While I was tweaking the kernel so as to achieve the graphic UI, however, the device suddenly switched to booting directly to the GAGUGA version TWRP which is installed over erecovery.
Now, despite undoing my kernel changes and rebuilding the version that booted successfully, this behavior continues.
I also noticed that when I perform a wipe/factory reset, I get a message about it not being able to format cache. I'm not sure whether this was there previously.
Do you have any ideas why this might have happened or what could be causing the above?
I have succeeded in building an Ubuntu Touch version based on Android 9 (Halium 9) and got the device to boot. While I was tweaking the kernel so as to achieve the graphic UI, however, the device suddenly switched to booting directly to the GAGUGA version TWRP which is installed over erecovery.
Now, despite undoing my kernel changes and rebuilding the version that booted successfully, this behavior continues.
I also noticed that when I perform a wipe/factory reset, I get a message about it not being able to format cache. I'm not sure whether this was there previously.
Do you have any ideas why this might have happened or what could be causing the above?
This happens if the software does not work properly, the phone is automatically restarted in recovery mode (eRecovery).
I can't help you, all about Ubuntu Touch is Greek to me
I hope you don't do a factory reset in TWRP. This is strongly not recommended on Huawei devices!
Last edited:
Aaah! Well, that's probably where I went wrong. I did a factory reset a couple of times at least. This may very well be the reason. How can I fix this, given that this is the source of the problem?This happens if the software does not work properly, the phone is automatically restarted in recovery mode (eRecovery).
I can't help you, all about Ubuntu Touch is Greek to me
I hope you don't do a factory reset in TWRP. This is strongly not recommended on Huawei devices!
It's just one of the possible causes. As I said before, I don't know what the problem is.
As for factory reset in TWRP, more info
here
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
5EMUI 8 Stock ROMs:
3.2.1-0 by pretoriano80 (with data decryption on Android 8 )
https://mega.nz/#!Fgd0xa4R!1o5ejzDnkLJLG2tAZG-STtlJ4nnNCHfwwZdOlmOkrVw
EMUI 8 Custom ROMs:
3.2.1.0 by Catuva21:
https://mega.nz/#!JlkRVY7b!Hz0QTmbgmMNeCaU-PmVRBGKsdd9pslmWNkOZpE6I8ZA
3.2.3-0 by Askuccio
https://mega.nz/#!h9903SqS!aRXc9x6Kuz_GclVy_3ZExCLDSdnp7Ee8VIgfqOG9x8k
Chinese ROMs (inc. KangVip):
3.2.1-0
https://mega.nz/#!sp0UyCDR!bq10MAyh0sddUCPi0zecQzrmLfCESFvNlCiQ3vkPMqI
EMUI 9.1 Stock ROM & Custom ROMs:
3.2.1-0 GAGUGA Edition
https://mega.nz/#!tkcTlATI!A8UJGPBGtxJbLcUOJoxCGJj5PFZXzCnjbb3OkwqKTP8
EMUI 9.1 Custom ROMs:
3.4.0-0-emui9_eR by @S_mak
https://mega.nz/#!B8kWgJDC!_hj7xkTzF9Uj66wKjtrWPHEV5Dbkk7Q256tuiKg7FQU
On [A12], [A12.1] GSIs use 3.4.0-0-emui9_eR .1
Yes, you can revert to stock flashing this Service ROM , if yot are running EMUI 8. For EMUI 9.1 use Service ROM 9.1.0. This process will erase all your data and lock the BL again!
Or, simply flash SYSTEM.img extracted from Service ROM using Huawei
update extractor. This procedure will not erase your data ,bootloader remains unlocked etc.1
It is a feature turned into a bug with emui 9. I can only speculate but it is probably related to us having boot bundled with recovery in stock partitioning scheme. There's a twrp that actually utilizes this bug/feature. It's for honor 9 lite but it's based on official p20 lite twrp so it works on p20 lite too. Check here if you want to test it yourself. Boot it and go to reboot menu, there'll be a boot override selection. I haven't seen any twrp that offers this other than tishserg's.
edit : I've had the same thing happened to me multiple times and fixed it with the twrp in question. Irc another way to trigger this is to factory reset from gsi while twrp is installed. You'll keep booting to twrp until you fix it the way you did or with the twrp I linked.1
I'd argue with you but I see no point in doing so. Instead I am going to elaborate my point for future replies. Boot image is a combination of partitions. Normally a boot image includes kernel, ramdisk and few headers along with AVB. But this device is not normal. Huawei with their ultimate wisdom decided to approach this partitioning with a radical view and split these partitions into their own image. Then they merged them with different images in emui 9. Magisk is a perfect example for this because it uses ramdisk. It patches boot image because ramdisk is inside the boot image for most devices. But you patch dedicated ramdisk.img in emui 8 and recovery_ramdisk.img in emui 9 because that's where ramdisk resides for us. You could learn this much just by looking at magisk log while patching image from manager. So yeah, "boot" is bundled with recovery in our devices. As for the speculation part, it is what it is. I am no genius but I certainly am not a idiot either. I can't pinpoint why a bug happens with just the explanation of it.You again?
Last time i saw the boot partition on android 7...
Exactly! YOU can only speculate bro.
normal devices : boot.img = AVB + kernel + ramdisk
emui 8 devices : ramdisk.img = ramdisk
emui 9 devices : recovery_ramdisk.img = recovery + ramdisk1
Well I haven't done much so I think I know what I'm doing...This TWRP doesn't have the bug at all. (If you know what you're doing. )
I've even reflashed the stock recovery, re-downloaded the TWRP, flashed it in recovery_ramdisk as usual and the bug is still there. Also looking in the thread on 4pda, it seems like I'm not the only one who has encountered this problem 1
