I tried to unpack the system.img in the millet 6-line brush package with the super kitchen superr and added some apps to the priv app. But when I packaged it back and flashed successfully, the phone card was in the mi sign. The card is on the first screen of the boot. And after trying the system.new.dat in the rom zip, it is also stuck in the first screen. Can anyone help me thank you.
The system version of Xiaomi 6 is 8.0.0
Related
hi, im having hard time to install custom rom like Lineage and AIM Rom,
i know how to flash TWRP and Stock Recovery,
and once i tried to install Aim rom using TWRP, Im getting an error such as
this rom is for asus_z010D, Z010D, Z010DD, your device is Z010,
can you please help me with this problem, i really wanted to try Oreo version of Android,
I have asus zenfone max (ZC550KL)
firmware: WW_13.8.26.92
Android: 6.0.1
thanks a lot.
just simply use notepad++ to delete assert lines in updater-script file placed at META-INF\com\google\android (open the zip file and you'll see) and you are able to flash it via TWRP.
Z010
It's work. Thank you broo
I recently upgraded my phone to Android Oreo 8.1 and I have noticed that there is a lot of BLOAT I wanted to get rid of. I searched online and found a couple of guides on how to remove this so I followed one which used Assayyed Kitchen. I had got the Samsung Oreo stock firmware and converted the images from the new .lz4 format to .img using the LZ4 compress / decompress program so that I could use it in Assayyed Kitchen. Then, I extracted it from the program and recompiled it once I was done debloating the system.img. I unlocked my bootloader from the 'Developer Options' and booted into it so I could flash the .tar file created from Assayyed Kitchen, containing the debloated system.img. Once I flash the firmware, the device fails to reboot and instead, reboots into recovery mode and gives me an error something along the lines of 'the data partition is less than 50MB'. When I try to reboot it from recovery mode, it shows the Samsung logo and goes into a blank screen, failing to load the OS.
I have tried:
- Wiping the data/cache partition before flashing
- Compressing the .img to .img.lz4 before flashing
- Deknoxing the system.img before flashing
None of the following have worked. I am not sure whether Samsung has detected that the system.img is a custom ROM and is blocking it from being run but I unlocked the bootloader so I do not think that it should block it in the first place. I would be grateful for any assistance, thank you.
Assayyed Kitchen Guide: https://forum.xda-developers.com/android/software/guide-how-to-develop-modify-roms-t3616040
I have found an alternate way of debloating my phone using a debloat script. I did this by flashing a custom recovery (TWRP), formatting the data partition and then flashing Magisk v18.0 so that it goes undetected by the phone. Once I had done this, I booted into TWRP once again to flash the debloater ZIP file. Once I had flashed the ZIP, the device could not boot into the OS, yet again. I tried formatting the data partition and flashing Magisk again but to no avail. After re-installing the stock ROM, I repeated the steps and tried a different method. This involved using FlashFire to flash the ZIP file. I got FlashFire and gave it root access. I tried flashing the ZIP but a black screen appeared and the system rebooted. Then, I tested some of the settings, enabling 'Global' namespace in Magisk as well as 'auto-mount' and 'mount /system' in FlashFire, still to no avail.
I have almost given up on debloating my Galaxy J5 as it seems nearly impossible. Please help!
No-one?
hi
Hello.
I have the Huawei Mate 10 Lite phone in my hands. I wanted to change the system to some custom OS and something went wrong.
I unlocked the bootloader, uploaded TWRP and everything was OK. Problems started during Lineage install (the same with AICP). The system did not boot after installing.
At the moment only eRcovery is running but also can't install anything. I suspect this is due to the lack of original recovery. I extracted the RECOVERY.IMG and RECOVERY2.IMG files from the UPDATE.APP file.
However, I can't install them because I get this error:
-=edit=-
After many attempts to repair using information from the internet, I was able to repair the phone with this post - https://forum.xda-developers.com/showpost.php?p=76640204&postcount=79
Many thanks to @Chisetdel31260 for his great work and this post
Has anyone gotten a gsi working with the galaxy A105M/DS? I have tried aosp pie and lineage 16.0 pie arm32_binder64 A/B but both were stuck at the logo screen.
Samsung phones have a weird habbit of staying stuck on bootanimation on some Pie GSI.
Try this:
Delete the following file with TWRP file manager: system/bin/rw_system.sh
Then reboot
Hopefully it works!
ShaDisNX255 said:
Samsung phones have a weird habbit of staying stuck on bootanimation on some Pie GSI.
Try this:
Delete the following file with TWRP file manager: system/bin/rw_system.sh
Then reboot
Hopefully it works!
Click to expand...
Click to collapse
Thank you so much <3 it worked!
I was finally able to successfully boot up lineage os and it works like a charm
parthibratan said:
Has anyone gotten a gsi working with the galaxy A105M/DS? I have tried aosp pie and lineage 16.0 pie arm32_binder64 A/B but both were stuck at the logo screen.
Click to expand...
Click to collapse
Hi parthibratan can you tell me how you successfully flashed twrp on your device?!!
@ShaDisNX255 According to what i have studied in Samsung phones. Their bootanimation format is .qmg unlike .png in other mobiles. This maybe a reason to bootloop too as gsi's are made for all supported devices and changes in the stock bootanimation may cause a bootloop too! I actually need a help. I have the Samsung Galaxy A10 (A105F/DS) which is rooted using magisk and flashed twrp v.3.3.1 and i wanna gsi roms such as lineage os 16 and 17 , aosp , viper os etc., But , am afraid that my phone will get stuck in bootloop as this is my only device in my hand right now. Can i use this : Delete the following file with TWRP file manager: system/bin/rw_system.sh
Then reboot
Can you please guide me ?
Waiting for your reply ?
Infant9099 said:
@ShaDisNX255 According to what i have studied in Samsung phones. Their bootanimation format is .qmg unlike .png in other mobiles. This maybe a reason to bootloop too as gsi's are made for all supported devices and changes in the stock bootanimation may cause a bootloop too! I actually need a help. I have the Samsung Galaxy A10 (A105F/DS) which is rooted using magisk and flashed twrp v.3.3.1 and i wanna gsi roms such as lineage os 16 and 17 , aosp , viper os etc., But , am afraid that my phone will get stuck in bootloop as this is my only device in my hand right now. Can i use this : Delete the following file with TWRP file manager: system/bin/rw_system.sh
Then reboot
Can you please guide me ?
Waiting for your reply ?
Click to expand...
Click to collapse
If you are afraid of a bootloop, why not just do a full backup of your current stock ROM and if it fails, just restore
It's that easy, it doesn't matter if it doesn't boot, you can safely just return to stock
Albert pallam said:
Hi parthibratan can you tell me how you successfully flashed twrp on your device?!!
Click to expand...
Click to collapse
Yes of course
Download the twrp from here https://androidfilehost.com/?w=files&flid=306584
The U1 version of twrp didn't work for me so I used the U2 version
What I did was
1.Firstly download the firmware for my device
2.Extracted it and also extracted the boot.img.lz4 from the AP****.tar using 7zip and copied both AP*****.tar and boot.img.lz4 to my phone
3.Patched AP*****.tar using magisk manager and then patched boot.img.lz4
4.Copied both magisk_patched.tar and magisk_patched.img to my pc from my phones Download folder
5.Extracted only the vbmeta.img from the magisk_patched.tar and renamed the magisk_patched.img to recovery.img
6.Made a tar file of vbmeta.img and recovery.img using 7zip, named it patch then flashed it using odin's ap tab
7.Restarted the phone into stock recovery and factory data resetted and restarted the phone again fully booted up the phone once
8.Then renamed the downloaded twrp-a10-3.3.1-0_afaneh92_U2.img to recovery.img and created a tar of it using 7zip and named it twrp
9.Flashed the twrp.tar using odin's AP tab and voila I got twrp running on my a10
Hope this helps
ShaDisNX255 said:
If you are afraid of a bootloop, why not just do a full backup of your current stock ROM and if it fails, just restore
It's that easy, it doesn't matter if it doesn't boot, you can safely just return to stock
Click to expand...
Click to collapse
Hey it seems like I have a new problem
Turns out flashing the latest multidisabler.zip makes the phone stuck at bootanimation again
But if I don't flash multidisabler I can't copy anything into the phones Android folder it always fails
parthibratan said:
Yes of course
Download the twrp from here https://androidfilehost.com/?w=files&flid=306584
The U1 version of twrp didn't work for me so I used the U2 version
What I did was
1.Firstly download the firmware for my device
2.Extracted it and also extracted the boot.img.lz4 from the AP****.tar using 7zip and copied both AP*****.tar and boot.img.lz4 to my phone
3.Patched AP*****.tar using magisk manager and then patched boot.img.lz4
4.Copied both magisk_patched.tar and magisk_patched.img to my pc from my phones Download folder
5.Extracted only the vbmeta.img from the magisk_patched.tar and renamed the magisk_patched.img to recovery.img
6.Made a tar file of vbmeta.img and recovery.img using 7zip, named it patch then flashed it using odin's ap tab
7.Restarted the phone into stock recovery and factory data resetted and restarted the phone again fully booted up the phone once
8.Then renamed the downloaded twrp-a10-3.3.1-0_afaneh92_U2.img to recovery.img and created a tar of it using 7zip and named it twrp
9.Flashed the twrp.tar using odin's AP tab and voila I got twrp running on my a10
Hope this helps
Click to expand...
Click to collapse
Thank you for your help!!
I have flashed lineage os 17 (android 10).
It is smooth, but no volte is working for me. As a result I can't call or install whatsapp. So I decided to go back to stock ROM!.
Albert pallam said:
Thank you for your help!!
I have flashed lineage os 17 (android 10).
It is smooth, but no volte is working for me. As a result I can't call or install whatsapp. So I decided to go back to stock ROM!.
Click to expand...
Click to collapse
VoLTE will not work on any GSI, it's a Samsung only thing for now
---------- Post added at 07:16 AM ---------- Previous post was at 07:15 AM ----------
parthibratan said:
Hey it seems like I have a new problem
Turns out flashing the latest multidisabler.zip makes the phone stuck at bootanimation again
But if I don't flash multidisabler I can't copy anything into the phones Android folder it always fails
Click to expand...
Click to collapse
I don't know what multidisabler is or what it does
How do we flash gsi on the A10? I tried to flash the linage img in twrp and it says no os installed, I assume twrp for A10 does not support flashing gsi Roms?
Cupcake 1.5 said:
How do we flash gsi on the A10? I tried to flash the linage img in twrp and it says no os installed, I assume twrp for A10 does not support flashing gsi Roms?
Click to expand...
Click to collapse
-> Flash the gsi img as system img
-> Reboot directly to TWRP
-> Then reboot to system
Hello,
I wanted to flash Lineage OS 15.1 on my Huawei Mate 10 Lite (RNE-L21). I have an unlocked bootloader and TWRP 3.1.1-0 (OpenKirin Edition, from here: Link).
Unfortunately, when only wanting to do a factory reset prior to the Lineage OS install, I accidentally wiped my system partition. Now Lineage OS won't install, as it is lacking the stock system (checks the system prior to the install, see XDA-LineageOS15.1-Link).
Now I want to install the stock firmware, in order to install Lineage OS. For this reason I checked my phones region and fastboot getvar vendorcountry returned vendorcountry: hw/eu. So I guess I am on C432? Please correct me if I am wrong. So I downloaded the RNE-L21C432B304 firmware from here. The downloaded update.zip folder with a fairly huge UPDATE.APP file (>4GB) I unzipped and put on the external-sd card in a folder named "dload". Inside the dload folder there is the UPDATE.APP file among some other files (folder META-INF, new_filecontext_system, ...). However, when I now enter the software upgrade mode (power + both volume keys) the install breaks at 5%. It seems that it either can't detect the UPDATE.APP file, or it is the wrong one. I also tried to put the dload folder into /sdcard/, but the outcome is the same. Also if I don't add any files (so no dload folder), the outcome is the same, it breaks at 5%, so I am not sure if it is even checking the UPDATE.APP file.
I hope somebody has a hint for me.
Best, Felix
P.s.: I also tried to flash the OpenKirin EMUI 8-based Build LineageOS 16.0 Build 2 using their guide (OpenKirin Installation Guide), which wasn't working. But as they state you need to have EMUI 8.0 installed, I guess the problem is that I don't have any system installed at the moment.
I finally figured it out. I was on Android 7 before deleting the system partiton. I didn't know there is such a big difference partitionwise between Android 7 and 8 and I always tried to flash an Android 8 image. Flashing an Android 7 image worked. Then I could update to Andorid 8 via stock Huawei tools and afterwards flash a custom rom.
Mecroob said:
I finally figured it out. I was on Android 7 before deleting the system partiton. I didn't know there is such a big difference partitionwise between Android 7 and 8 and I always tried to flash an Android 8 image. Flashing an Android 7 image worked. Then I could update to Andorid 8 via stock Huawei tools and afterwards flash a custom rom.
Click to expand...
Click to collapse
Were did you find the android 7 rom? I want to downgrade my RNE-L21 (C185) from android 8 to 7.
brokenpotato said:
Were did you find the android 7 rom? I want to downgrade my RNE-L21 (C185) from android 8 to 7.
Click to expand...
Click to collapse
I mostly used this site: Link
Additionally, there is some tool, which includes a lot of Huawei stock ROMs. Unfortunately, I can't find it anymore. But maybe you have some luck googling.
Because I just came by the tool I used: It is called Huawei Multi-Tool:
[TOOL] Huawei Multi-Tool v8 by Team MT
Huawei Multi-Tool by Team MT Download Link: Project downloads Description: The application is based on working with fastboot and adb modes of Huawei and Honor smartphones. Allows you to perform many actions with any device on the...
forum.xda-developers.com