Hi. this is in regards to the rom here:
Dual/Single] HaoZeke's LineageOS [8-4-17]
And my device is a Sony Xperia Z5 model 6653 currently running a modified 32.3 A.0.376 with a patched Kernel running 7.0 and I am rooted
.I'm kinda new to the modifying of droids. I've had one since ever having a phone, but just got into tweaking them.
I just want to be sure I'm doing this right because sometimes the boot image is attached to the zip file or include in the package but I'm assuming we download
it separately here, right? I'm only guessing since I see it located by itself in the dl list. Also, this IS the kernel too right? Or do I have to download that as well somewhere?
I had an image but it's not taking them I guess. Basically the download screen, all the builds and the boot image. I would take the top build as it's newest and the boot image?
Also, flash twrp from that source after flashing the gapps?
In fact what is the order? Rom, then Gapps, then Boot (if we use that boot file) and then finally TWRP?
And Magisk doesn't have to be flashed I think but just gotten in the play store provided this Rom is already rooted?
Also, wanted to be sure this is correct. ARM... 64 for the GAPPS?
Thanks for your help in advance. I appreciate it. I've had a ton of issues with other lineage 7.1 builds and issues with error 7 . I've rewritten updater scripts to no avail, deleting the asserts and nothing . This is the last one I'm trying as it sounds the coolest anyway. Thanks again.
Hello,
ARM64 for gapps, and proper order of flashing is : rom, gapps, boot optionally and then supersu or whatever you want.
And for me deleting asserts line always work, i will send you link with already modified that updater script.
Related
Your warranty is now void, don't blame me if your phone blows up blahblahblah.
Only system and kernel are being flashed, no Modem, BL, etc. You should already have updated to 20B before using.
Have not tested this myself, due to not owning the H850. edit: flashed it on T-Mobile 830 for fun with 20A 830 boot, no surprise, didn't work.
Decided to post anyway. If your going to use it, BACKUP, BACKUP, BACKUP
Based off of H85020b_00_TIM_IT_OP_1123.kdz
Only things touched are bootanimation (pixel black) and renamed recovery-from-boot.bak. It's also been zip-aligned.
Flash in recovery, profit??
SuperSu and Busybox included. Only /system is wiped, data left alone.
Should be able to dirty flash over current 20B if you like.
Any errors, etc, would most likely be related to deodexing as all files are stock.-Again, haven't tested this one myself
Link: H850_20B_DeOdexed
MD5: 99c9667294d1227de91605b8958233e0
If anyone would like to use this as a base, Great! Would appreciate some credit. [emoji13]
Enjoy.
Optional: Adjust Screen Color
Credits: @Chainfire for supersu. @SuperR. for the kitchen. @PlayerZ_ZawZaw for bootanimation. @jcadduono for TWRP. @bullghost for Firmware Extractor
It's people like them that make Android great!
Finally, thanks to Google/LG & XDA.
...whew.
Reserved
Great work Bro, nice. :good:
A couple questions 1. Isn't 20B just a security patch update? 2. Does this ROM zip upgrade firmware (bootloader , radio, recovery) or just update software. 3. Since it's based off of the Italian H850 variant this won't cause troubles for EU variant?
xlxcrossing said:
A couple questions 1. Isn't 20B just a security patch update? 2. Does this ROM zip upgrade firmware (bootloader , radio, recovery) or just update software. 3. Since it's based off of the Italian H850 variant this won't cause troubles for EU variant?
Click to expand...
Click to collapse
1. Not 100% sure. 2. Just system and kernel are flashed. No M/BL, etc. 3. No idea really.
Received error while flashing, code 7, seems it couldn't locate a certain filesystem and aborts installation - same here with the 20B version
Mr. Schnabel said:
Received error while flashing, code 7, seems it couldn't locate a certain filesystem and aborts installation - same here with the 20B version
Click to expand...
Click to collapse
Hmmm flashed ok on my h830(swapped kernel), wouldnt boot (of course, this is for 850), but still flashed. Not sure why your getting that error, already removed the assert.
lordodin912 said:
Hmmm flashed ok on my h830(swapped kernel), wouldnt boot (of course, this is for 850), but still flashed. Not sure why your getting that error, already removed the assert.
Click to expand...
Click to collapse
Same error... Keep at it tho, something like this could be really useful
If anyone wants to try this themselves here's a quick guide.
You can take the system.img and boot.img from either the kdz with LG Firmware Extractor or from autoprime complete zip.
Then Google "superR kitchen xda", if your using windows there is a VM iso in the thread you can use with VirtualBox etc.
Once you have the kitchen working just remember, set_metadata for perm, use smali/baksmali for deodexing and don't sign the zip or let it remove the meta-inf folders from apps.
In my h850 doesn't finish to install, it remains on initial boot animation.
failax said:
In my h850 doesn't finish to install, it remains on initial boot animation.
Click to expand...
Click to collapse
Flashed ok but stuck on LG logo? May need to flash no verify or "format data" in TWRP. BACKUP everything if formatting.
Ok so I just clean flashed my 20a for h830 and got that error code 7, doesn't happen on dirty. Just restarted TWRP after wiping and then it flashed ok. Might be the same problem over here.
Does anyone know how to create a flashable TWRP rom (.ZIP) from the stock Nougat ROM?
I have already installed TWRP and I really would like to have a ROM ready to be flashed in case of problems...
The other system is really slow and not intuitive in my opinion.
Thanks.
Anyone?
It's a good question. What "other system" are you referring to?
I'd love for the OpenKirin or TWRP guys to chime in. I've TRIED cross-compiling both the factory Berlin source and the OpenKirin Berlin source with gcc 4.9, and I keep running into errors. I'm trying to work through it myself as to not bother them, but if they have any recommendations and tips on how they are compiling from source, I'd love to hear more.
Here are some links that should help:
OpenKirin source
github.com/OpenKirin/android_device_honor_berlin
Huawei Berlin Source (You'll want to change the country code for the country that you are in. This one is for the US.)
hihonor.com/us/support/software-list/index.html
Info for AOSP Source:
source.android.com/source/downloading
sethdc said:
It's a good question. What "other system" are you referring to?
Click to expand...
Click to collapse
Hi.
Referring to firmware finder method... and I see that I cannot do the same procedure now that I am already on Nougat. My OS for sure has some corrupted files, but if I do again the firmware finder process (with MF file not the MF-PV), the operation stops.
That's why I need a TWRP ROM ready to flash...
Frankly speaking the samsung forums are much more "crowded" than here and solutions come out very quickly.
I was used to flash ROMs every week just to test or play with... Here is kinda desert....
Diamantes said:
Hi.
Referring to firmware finder method... and I see that I cannot do the same procedure now that I am already on Nougat. My OS for sure has some corrupted files, but if I do again the firmware finder process (with MF file not the MF-PV), the operation stops.
That's why I need a TWRP ROM ready to flash...
Frankly speaking the samsung forums are much more "crowded" than here and solutions come out very quickly.
I was used to flash ROMs every week just to test or play with... Here is kinda desert....
Click to expand...
Click to collapse
Go to this link
http://hwmt.ru/oth/HWFF/info/view.php?find_model=
find the firmware version which worked on your device previously Download the zip package which has full as status .
Boot into twrp and make a clean flash of the zip.
Stock ROM Zip default has updater script so it can be flashed through TWRP.
Diamantes said:
Does anyone know how to create a flashable TWRP rom (.ZIP) from the stock Nougat ROM?
I have already installed TWRP and I really would like to have a ROM ready to be flashed in case of problems...
The other system is really slow and not intuitive in my opinion.
Thanks.
Click to expand...
Click to collapse
You don't need to create. Full firmware packages are TWRP flashable, at least for Honor 8 which I personally tried and tested.
Sent from my Honor 8 using XDA Labs
Well, I will try again as you said.
But I read that MF-PV files are used to change from a previous OS version to the new one. (For example in this case from marshmallow to nougat).
Files with MF only should be used to update within the same OS number.
If I use that zip file, it doesn't work with TWRP on my phone.
I'm not trying the MF-PV because in theory it deletes data and everything....
Anyway, we'll see.
Thx.
Hello XDA Developers
I have been trying to flash a custom rom on my Google Pixel which is running Android Oreo and I have gotten as far as unlocking the bootloader and installing TWRP. How ever when I attempt to flash any zip file it just says error installing zip and I have no idea what's going on. TWRP sometimes even has trouble mounting the proper partitions so it's a bit of a hit and miss. Id really like to install a custom ROM. I thought maybe it was a bad zip file but I have tried several different ROMs and they all throw up the same error.
Update: Okay I have figured out that installing newer versions of TWRP doesn't work with some of the ROMs and it's better to use the older versions but you have to figure out which one that is if they don't tell you. I was able to successfully install a custom ROM.
Dunno if this advice is any good but don't set a pin code or password on the phone leave it unlocked it's easier for TWRP to read the partitions that way.
Good afternoon XDA.
I'm trying to get Magisk installed on my phone, but I'm really struggling.
Any hints/tips? I've followed instructions to every forum post and every Youtube video I've tried.
AFAIK, I have managed to install TWRP without issue, although after I've rebooted my phone into recovery, it encrypts the data folder, meaning if I patch any zips in TWRP, I have to first format the data to EXT2 and back to EXT4 for me to be able to mount the folder, which I think is where my problems lie.
After this, TWRP seems to look like it's installed the Magisk.zip without any issues, but when I install the magisk apk once I've booted back into Android, it says it is not installed, and is asking me to either download the zip again, or find a boot image to patch.
The ROM I have installed is also custom as far as I'm aware, as the kernel says "[email protected] #2'
Android version: 8.0.0 (I don't mind using an older ROM, like 7 if it means I can get Magisk working.
Build: 41.3.A.2.157
Thanks
Try this, download flash tool, use Xperiafirm to ? get the latest firmware for your region which is currently 171, check all the wipes, flash, then look down a few post to YasaHamed thread, follow his instructions and make use you use the correct kernel..
madladfromhalifax said:
I'm trying to get Magisk installed on my phone, ...
Click to expand...
Click to collapse
I had no problems with a patched stock kernel as described in my [Guide].
Updates of kernels and Magisk, whatever ...
I used latest TWRP, several versions
The encryption only forces you to wipe data if you set up a patched kernel the first time.
I will see how this works with a XZ1 (no TA-backup) since my XZ got stolen last week.
use AdrianDC's twrp, not the twrp official one
madladfromhalifax said:
Good afternoon XDA.
I'm trying to get Magisk installed on my phone, but I'm really struggling.
Any hints/tips? I've followed instructions to every forum post and every Youtube video I've tried.
AFAIK, I have managed to install TWRP without issue, although after I've rebooted my phone into recovery, it encrypts the data folder, meaning if I patch any zips in TWRP, I have to first format the data to EXT2 and back to EXT4 for me to be able to mount the folder, which I think is where my problems lie.
After this, TWRP seems to look like it's installed the Magisk.zip without any issues, but when I install the magisk apk once I've booted back into Android, it says it is not installed, and is asking me to either download the zip again, or find a boot image to patch.
The ROM I have installed is also custom as far as I'm aware, as the kernel says "[email protected] #2'
Android version: 8.0.0 (I don't mind using an older ROM, like 7 if it means I can get Magisk working.
Build: 41.3.A.2.157
Thanks
Click to expand...
Click to collapse
simplyfied!!!! https://forum.xda-developers.com/xperia-xz/how-to/rooted-kernels-f8332-41-3-2-588-0-t3748987
I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE!!!
YOU HAVE BEEN WARNED!!!
Watch dogs is a ROM I created and it started with the OnePlus 9 Pro back in December. I have decided to bring it to the OnePlus 9, it's based on LineageOS & crDroid source & dependencies and I thank them for its use. SafetyNet and CTS passes whether your rooted or not. Modules not required. Most features are the same as crDroid but I have made some adjustments to bluetooth quality and some fonts that are not available there, plus Gapps are included.
Before you begin, if you don't have the latest platform tools installed on your windows machine. Download it here:
DO NOT FLASH GAPPS!!!! THEY ARE INCLUDED IN BUILD!!!!!
Flashing Instructions
First time installation (clean flash):
This update requires OOS 13.1 - 13.1.0.500(EX01) firmware
Backup your data
Download the ROM, and firmware flasher listed further down on this post and place all in your platform tools folder,
Extract all the contents in platform tools, Firmware flasher in folder.
You must flash firmware in bootloader.
Boot to recovery and factory reset then adb sideload
adb sideload WatchDogs-13.0-20230625-lemonade.zip
Reboot to system
reboot to recovery if you want root
adb sideload magisk.apk or adb sideload magisk.zip
Reboot to system
Update installation:
Updates can be sideloaded with custom recovery. Updates do not appear in system updater.
Sources:
ROM
Kernel
Downloads:
ROM
FIRMWARE FLASHER
Bugs?
Let me know.
Initial builds
WatchDogs-WITHGAPPS-13.0-20230312-lemonade.zip
WatchDogs-NOGAPPS-13.0-20230312-lemonade.zip
If you require Google apps, flash the first one only!
If you do not want Google apps, flash the second one only!
You can't cross dirty flash a update which should be common sense. Example, you can't dirty flash the with gapps build then next update, dirty flash the no gapps one.
I tried CRdroid recovery and the one I was on and both said name mismatch. Got any suggestions for me to try? Thank you for the new development too!
Telegram group please
lorilucille9 said:
I tried CRdroid recovery and the one I was on and both said name mismatch. Got any suggestions for me to try? Thank you for the new development too!
Click to expand...
Click to collapse
That's weird. Did you try sideloading the firmware flasher first before the ROM? If you still have difficulties, I will post the dtbo, boot and vendor_boot files for you to flash to make it compatible. I don't have this phone. I have the OnePlus9 Pro so I can't test it. I'm sure it works or there would be other users saying the same thing.
I flashed the firmware successfully and tried it again but still got the same error. It wouldn't hurt to post the kit files and recovery for others too. If you do then I'll try again before I have to head into work in a couple hours.
UPDATE:
I used the CrDroid boot-20230106 file and then sideloaded fw_Oneplus9_IN_OOS13_F20 on both slots and was able to flash the rom on both slots successfully. Will let you know what I find in time and thanks again for another version rom to pplay with
lorilucille9 said:
I flashed the firmware successfully and tried it again but still got the same error. It wouldn't hurt to post the kit files and recovery for others too. If you do then I'll try again before I have to head into work in a couple hours.
UPDATE:
I used the CrDroid boot-20230106 file and then sideloaded fw_Oneplus9_IN_OOS13_F20 on both slots and was able to flash the rom on both slots successfully. Will let you know what I find in time and thanks again for another version rom to pplay with
Click to expand...
Click to collapse
Good deal, and no problem. Since I use crDroid sources, I figured that should work. I will still post the files necessary to flash recovery when I get a chance. Let me know if there are any bugs or issues with the ROM itself so I can work on it. Thank you!
I installed it on my first try without any problems. but I couldn't understand how it differs from crdroid.
incesu571 said:
I installed it on my first try without any problems. but I couldn't understand how it differs from crdroid.
Click to expand...
Click to collapse
Bootanimation, fonts, bluetooth, sound audio and other tweaks.
TheSayaMan said:
Bootanimation, fonts, bluetooth, sound audio and other tweaks.
Click to expand...
Click to collapse
thx bro
TheSayaMan said:
Bootanimation, fonts, bluetooth, sound audio and other tweaks.
Click to expand...
Click to collapse
Not to mention Gapps included if you choose it so OTAs with no issues... otherwise you'd have to sideload Gapps again after at least for me that's what was happening.
lorilucille9 said:
Not to mention Gapps included if you choose it so OTAs with no issues... otherwise you'd have to sideload Gapps again after at least for me that's what was happening.
Click to expand...
Click to collapse
correct, sorry, forgot to mention that as well. Thank you!! crDroid doesn't offer a with gapps build. You can use the no gapps build to flash your own gapps but I won't support force close issues with the ROM. Example, pixel setup wizard can't be used because it interfers with the default launcher. And yes, on updates, just sideload the with gapps build and your done, unless you want root, then you will have to reboot and sideload magisk because root will be gone on a update.
incesu571 said:
Telegram group please
Click to expand...
Click to collapse
There is one in my 9 pro thread. I will update when I can.
I have op 9 t-mobile version le 2117, can you please guide me which firmware should i use IN, EU or NA?
Sady94 said:
I have op 9 t-mobile version le 2117, can you please guide me which firmware should i use IN, EU or NA?
Click to expand...
Click to collapse
Convert your T-Mobile to EU as listed on another thread, then you can use the EU firmware. I will be posting a update soon with the boot, vendor_boot and dtbo. If you don't want to do that, I will post them later to flash recovery on your phone. Keep in mind that different variants act different, so you may have bugs on T-Mobile, it wasn't tested.
screenshots?
pubmastervnt said:
screenshots?
Click to expand...
Click to collapse
Not by me, maybe someone else who is running it
MARCH UPDATES: 03/24:
WatchDogs-WITHGAPPS-13.0-20230324-lemonade.zip
WatchDogs-NOGAPPS-13.0-20230324-lemonade.zip
Sady94 said:
I have op 9 t-mobile version le 2117, can you please guide me which firmware should i use IN, EU or NA?
Click to expand...
Click to collapse
You can use my custom recovery, files added in OP. You still need latest stock A13.
fastboot flash --slot all boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vendor_boot vendor_boot.img
You cant install this (or any rom but base 11) on tmobile 2117 without BL unlock key. Pretty sure its not possible.
You can only convert to base global 11\OOS11 on 2117 for root, then in ui updater doesnt work OTA or manually. You can get to 13 stock only, because you need to be stock to ota, where you need a key to unlock bootloader again (conversion would bring you back to 11).
*The rooting situation with this phone sucks. I think Jaguar is the only one that will work because it is base 11.