Hi guys,
I know custom ROMs are made of AOSP. However, it's not very clear to me why do they also have lower quality signal compared to stock ROMs. In the same area where I usually got 4G (not great signal, but still 4G), now I only get 3G.
Is there a reason for this? Aside from "it's not made by the manufacturer". Yeah, I know that, but why exactly isn't the same quality...? What makes it slightly worse?
Also, is there anything can do to improve reception?
arsradu said:
Hi guys,
I know custom ROMs are made of AOSP. However, it's not very clear to me why do they also have lower quality signal compared to stock ROMs. In the same area where I usually got 4G (not great signal, but still 4G), now I only get 3G.
Is there a reason for this? Aside from "it's not made by the manufacturer". Yeah, I know that, but why exactly isn't the same quality...? What makes it slightly worse?
Also, is there anything can do to improve reception?
Click to expand...
Click to collapse
Exactly what you said: "It's not made by the manufacturer". Proprietary blobs are extracted from the device, creating vendor image while building AOSP and modifying vendor partition it when installing a zip.
I don't think there's anything to improve, until someone makes a kernel or a vendor image.
(flashing original vendor lead to bootloop on my phone, probably because encryption?)
However, you can try downloading stock ROM and flash stock vendor, but make sure to not have your device encrypted (I did not try on a non-encrypted device).
georg3_ said:
Exactly what you said: "It's not made by the manufacturer". Proprietary blobs are extracted from the device, creating vendor image while building AOSP and modifying vendor partition it when installing a zip.
I don't think there's anything to improve, until someone makes a kernel or a vendor image.
(flashing original vendor lead to bootloop on my phone, probably because encryption?)
However, you can try downloading stock ROM and flash stock vendor, but make sure to not have your device encrypted (I did not try on a non-encrypted device).
Click to expand...
Click to collapse
I've noticed this with stock ROMs as well, when they weren't dedicated for that specific region... So...I'm guessing it's probably the same here. AOSP includes some files to make the ROM work...but not dedicated files for each region.
By the way, can you please, guide me how should I do this? It's been a really long time since I've done stuff like this. Android has changed a lot.
I already have the ROM at hand, downloaded via RSA. But it's Android 11, since that's the last ROM that Motorola released for this phone.
So that part is done. What next? )
Also, any idea if this method should also bring back VoLTE and VoWIFI? Or it's not that simple?
arsradu said:
I've noticed this with stock ROMs as well, when they weren't dedicated for that specific region... So...I'm guessing it's probably the same here. AOSP includes some files to make the ROM work...but not dedicated files for each region.
By the way, can you please, guide me how should I do this? It's been a really long time since I've done stuff like this. Android has changed a lot.
I already have the ROM at hand, downloaded via RSA. But it's Android 11, since that's the last ROM that Motorola released for this phone.
So that part is done. What next? )
Also, any idea if this method should also bring back VoLTE and VoWIFI? Or it's not that simple?
Click to expand...
Click to collapse
EDIT: Newer OS than vendor shouldn't make a problem.
Newer vendor than OS does.
Extract the ROM, there should be vendor.img in there, and there are 2 methods for this:
1. TWRP method
Install, Install Image, select your vendor image set it to flash as vendor image, and swipe to flash.
2.Fastboot method
Open a terminal/command prompt in the extracted ROM folder, and type
Code:
fastboot flash vendor vendor.img
That should do it.
georg3_ said:
Older OS than vendor shouldn't make a problem.
Older vendor than OS does.
Extract the ROM, there should be vendor.img in there, and there are 2 methods for this:
1. TWRP method
Install, Install Image, select your vendor image set it to flash as vendor image, and swipe to flash.
2.Fastboot method
Open a terminal/command prompt in the extracted ROM folder, and type
Code:
fastboot flash vendor vendor.img
That should do it.
Click to expand...
Click to collapse
Alright. So....I can't use Android 11 vendor, extracted from stock ROM, if I'm currently on PixelExperience based on Android 12, right?
arsradu said:
Alright. So....I can't use Android 11 vendor, extracted from stock ROM, if I'm currently on PixelExperience based on Android 12, right?
Click to expand...
Click to collapse
Stau bine pe engleza daca e )
I translated it wrong, i meant it would be fine to flash it
Buun. Thank you, kind sir. Will try it then and let you know.
georg3_ said:
Stau bine pe engleza daca e )
I translated it wrong, i meant it would be fine to flash it
Click to expand...
Click to collapse
I'm getting bootloop, too...
I tried to flash the rom, flash Disable_Dm-Verity_ForceEncrypt.zip (should disable encryption...unless I'm missing something). But after flashing vendor.img from stock Android 11, I can't boot anymore. I also tried wiping data after that, but no luck.
arsradu said:
I'm getting bootloop, too...
I tried to flash the rom, flash Disable_Dm-Verity_ForceEncrypt.zip (should disable encryption...unless I'm missing something). But after flashing vendor.img from stock Android 11, I can't boot anymore. I also tried wiping data after that, but no luck.
Click to expand...
Click to collapse
Probably not an encryption related issue, guess we can't fix anything.
Related
I built a custom rom based on ASOP and flashed it into my Nexus 5X with TWRP recovery. Now my phone does not have IMEI anymore and the baseband is unknown.
I found that someone said I should backup efs folder and restore them after I flashed the new rom. I tried it and nothing changed. Also I found that the size of system.img in the factory image is 2GB. However size of the one I built is only 586M. I flashed only this system.img file into my device, is there anything wrong?
Thanks very much for any help!
ZhenyuNing said:
I built a custom rom based on ASOP and flashed it into my Nexus 5X with TWRP recovery. Now my phone does not have IMEI anymore and the baseband is unknown.
I found that someone said I should backup efs folder and restore them after I flashed the new rom. I tried it and nothing changed. Also I found that the size of system.img in the factory image is 2GB. However size of the one I built is only 586M. I flashed only this system.img file into my device, is there anything wrong?
Thanks very much for any help!
Click to expand...
Click to collapse
I would say there is something wrong with the one you built.
Reflash the complete stock image and see if works ok.
Also is the efs backup from when it was working ok? Copy it to your computer so you don't accidentally delete it.
Darke5tShad0w said:
I would say there is something wrong with the one you built.
Reflash the complete stock image and see if works ok.
Also is the efs backup from when it was working ok? Copy it to your computer so you don't accidentally delete it.
Click to expand...
Click to collapse
Thanks for your reply.
I just modified some code in "art" fold, I guess this should not affect the radio. I build the image following the instructions in Google's website. Like,
source build/envsetup.sh
lunch aosp_bullhead-userdebug
make -j16
I have successfully finished the build and got system.img. After that, I flashed the file into device.
Also after reflashing factory image, everything goes well again. I backup efs after reflashing factory image, so i think it should be ok. However, once I flash my system.img again, the same thing happen. I really want to flash my own system.img into the device, did I miss anything?
The AOSP system image is going to be quite a bit smaller than the factory one. There are a lot more apps and google background stuff in the factory image. So that's not necessarily going to mean that something is wrong.
Did you try building from unmodified source? Haven't done much 5x building and no aosp builds, but that's where I'd start to make sure everything is working properly.
@ ZhenyuNing have you solved you problem? I have same issue with nexus6 when flash my compile img! If you have qq, pls contact me 493441095 深入交流
Hi
long time user of Huawei and Sammy
after waiting long for some sort of development for Huawei phones i have given up and im taking the plunge into the oneplus territory, after researching it seems like oneplus dont put obstacles in the way of development.
i have a few questions before i receive my oneplus and starting tinkering with it.
(disclaimer i know there is a tool for fact image twrp etc etc)
Firstly regarding stock image, is there only one firmware for the oneplus5T? i dont see anyone mentioning anything about branding or region stock ROMS.
also is there a download portal we can download the stock ROM / and extract .img files? (Huawei had a tool that lets you extract the .zip and within the zip the boot.img file could be extracted using another tool also to repack)
if not is there something similar (does TWRP let you backup boot.img and other important files? are they able to be modified and re-flashed?)
also what is the proper procedure in flashing ROM, Kernel, SuperSU and boot.img (which order)?
--i say boot image because i have some customisations id like to flash, if the kernel or SuperSU contains the boot.img i may be able to edit the changes and flash
on the huawei it was ROM>boot.img>kernel> supersu (Assuming supersu and kernel, bluspark in particular, doesnt flash stock boot.img just uses the one installed to modify - specifically id like to modify fstab in the boot img and keep my modifications)
when installing TWRP and wiping /data before first boot do any system applications get wiped? (on huawei some applications disappeared, themes, camera etc) or does all the good stuff reside somewhere else? (i.e i dont have to flash anything after wiping data as i did on the huawei to get some stuff back)
and finally, does root affect logging into snapchat?
on my mate 9 i had no problems but using the root method for the 10 caused problem
thank you!
To My knowledge the is one Global Rom.
For all your other questions, go here: https://forum.xda-developers.com/oneplus-5t/development
virtyx said:
Hi
long time user of Huawei and Sammy
after waiting long for some sort of development for Huawei phones i have given up and im taking the plunge into the oneplus territory, after researching it seems like oneplus dont put obstacles in the way of development.
i have a few questions before i receive my oneplus and starting tinkering with it.
(disclaimer i know there is a tool for fact image twrp etc etc)
Firstly regarding stock image, is there only one firmware for the oneplus5T? i dont see anyone mentioning anything about branding or region stock ROMS.
also is there a download portal we can download the stock ROM / and extract .img files? (Huawei had a tool that lets you extract the .zip and within the zip the boot.img file could be extracted using another tool also to repack)
if not is there something similar (does TWRP let you backup boot.img and other important files? are they able to be modified and re-flashed?)
also what is the proper procedure in flashing ROM, Kernel, SuperSU and boot.img (which order)?
--i say boot image because i have some customisations id like to flash, if the kernel or SuperSU contains the boot.img i may be able to edit the changes and flash
on the huawei it was ROM>boot.img>kernel> supersu (Assuming supersu and kernel, bluspark in particular, doesnt flash stock boot.img just uses the one installed to modify - specifically id like to modify fstab in the boot img and keep my modifications)
when installing TWRP and wiping /data before first boot do any system applications get wiped? (on huawei some applications disappeared, themes, camera etc) or does all the good stuff reside somewhere else? (i.e i dont have to flash anything after wiping data as i did on the huawei to get some stuff back)
and finally, does root affect logging into snapchat?
on my mate 9 i had no problems but using the root method for the 10 caused problem
thank you!
Click to expand...
Click to collapse
Lu-USVI said:
To My knowledge the is one Global Rom.
For all your other questions, go here: https://forum.xda-developers.com/oneplus-5t/development
Click to expand...
Click to collapse
thanks
I've read most of the threads and I don't see much in terms of my questions.
I just wanted to point out that I have been able to boot some treble GSI on my device from different roms like AOSP, RR, ArrowOS in the treble section of XDA and some of them boot fine, but I have found some issues:
PHH PIE GSI doesn't like magisk it breaks wifi and mobile data once magisk is flashed
PHH Oreo AOSP GSI I do not remember any issues besides being too stock for my liking
RR GSI It has so many options almost comparable to what a Venom Rom would be for HTC devices
TWRP it is not able to read encryption on any of this GSIs
AOSP Oreo I don't remember if the other variants GSIs does not read exFAT formatted MicroSD (works on PIE GSI)
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
I would like more users to share their experience here with GSIs
the steps I took to flash this
1. make sure you download an arm64 AB GSI image from your favorite ROM
2. go to TWRP wipe section wipe system, Dalvik cache data & internal
3. go to TWRP wipe section format data, type yes
5. restore stock Vendor.img and stock Boot.img
6. flash GSI
7. reboot & enjoy
first boot might take awhile it encrypts the device, thi is the part that makes TWRP not being able to decrypt data since TWRP decrypts Qualcomm Encryption on our device but no stock android encryption this part it is possible to fix by TWRP team and it will probably come in later
Thanks for sharing. I was planning on trying out a GSI this weekend and see how it goes. Glad it works!
I forgot to save the stock vendor and stock boot file I need these two files Can you help
emrince said:
I forgot to save the stock vendor and stock boot file I need these two files Can you help
Click to expand...
Click to collapse
https://forum.xda-developers.com/u12-plus/how-to/collection-htcu-u12-ruu-firmware-t3794664/page24
Read the OP there
I tried to boot the RR img, no dice.
Backed up modified rom on slot b
Switched to slot a in TWRP, supposedly empty
Wiped system, data, cache, dalvik
Flashed prior stock vendor img and boot img
Flashed RR ab arm64 su gapps Img
Rebooted slot a
Bootloop
Interestingly, after looking 3 times, my phone booted back to slot b by itself back to stock, back up restored just fine
I realize I didn't wipe factory reset with yes
Finally got RR to to boot! It's a very finicky process. I think my problem was I kept trying to "dual" boot, Viper in one slot and the GSI in the other. Turns out it just has to be in the active slot, regardless of which slot you switch to in TWRP. Maybe that's obvious for some. This a/b partition business sure has a learning curve.
Anyway, things I noticed on RR: Lots of customization as usual for RR, very fast and smooth, screen brightness is on max all the time regardless of slider or auto brightness, and I couldn't make phone calls but texting worked. Everything else seemed to work fairly well. I love the fling navbar....on to the next one.
I'm not sure if anyone else is trying the GSI's, this doesn't seem to be a very active thread. So far I have only been able to boot RR 8.1 GSI. I have tried multiple other images without any success. I think the reason I didn't get data and calls didn't work on RR is that I am on Verizon and the HTC u12 does not have CDMA radios. Volte calling was not available on the rom. Oh well. I'm excited for the upcoming developments in the Viper forum. If anyone knows a fix for data on verizon with the GSI's, I'm all ears. Thanks
Anybody successful in making one of this ROMs a daily driver?
Sent from my HTC U12+ using XDA Labs
Resurrection Remix 8.1 is pretty stable if you are on a gsm network. I popped in a Tmobile sim card and it was pretty solid. There are some minor annoyances like the inability to adjust the brightness (always on full), though decreasing screen pixels makes it more dim, vendor mismatch message on boot, and no volte or wifi calling. There may be some other small things like with the camera and bluetooth but I didn't keep it for long as I am on Verizon and don't get data. I could see using it as a DD though. There are probably ways to fix the annoyances I mentioned.
Have any of you tested this version of RR on U12+?
https://forum.xda-developers.com/pr...0-resurrection-remix-v7-0-arm64-32-b-t3891636
For example, face recognition, 4k camera mode, slow motion recording, 3D sound, AudioFocus, bokeh mode etc.?
regards
q
@JEANRIVERA Is i't there any working Android P GSI rom?
Just can't wait anymore HTC for P update =)
nomaj said:
@JEANRIVERA Is i't there any working Android P GSI rom?
Just can't wait anymore HTC for P update =)
Click to expand...
Click to collapse
Original PHH, ArrowOS & DescendantOS all work fine, the only problem is no Magisk support yet
JEANRIVERA said:
Original PHH, ArrowOS & DescendantOS all work fine, the only problem is no Magisk support yet
Click to expand...
Click to collapse
So.. i will missing root? and fixes for google sotre etc ?
JEANRIVERA said:
Original PHH, ArrowOS & DescendantOS all work fine, the only problem is no Magisk support yet
Click to expand...
Click to collapse
I have problem with install ArrowsOS, i have still bootlops.. It's probably related to a / b boot, how to fix this? Twrp say "No OS installed", i set wipe system,data,cache next i flash vendor, boot and system file, i made a mistake?
JEANRIVERA said:
Original PHH, ArrowOS & DescendantOS all work fine, the only problem is no Magisk support yet
Click to expand...
Click to collapse
@JEANRIVERA
Is't this update helpping us?
2019.3.28 Magisk v19.0
https://forum.xda-developers.com/showpost.php?p=79216305&postcount=50https://forum.xda-developers.com/showpost.php?p=79216305&postcount=50
mientus25 said:
I have problem with install ArrowsOS, i have still bootlops.. It's probably related to a / b boot, how to fix this? Twrp say "No OS installed", i set wipe system,data,cache next i flash vendor, boot and system file, i made a mistake?
Click to expand...
Click to collapse
Hey, I'm having the same problem. Did you work out a solution to get any GSI to boot on your U12?
SilentAchiever said:
Hey, I'm having the same problem. Did you work out a solution to get any GSI to boot on your U12?
Click to expand...
Click to collapse
I tried to find a solution for 12 hours and nothing came of it
I's dual sim working on GSI roms?
---------- Post added at 10:38 AM ---------- Previous post was at 10:36 AM ----------
mientus25 said:
I tried to find a solution for 12 hours and nothing came of it
Click to expand...
Click to collapse
1. make sure you download an arm64 AB GSI image from your favorite ROM
2. go to TWRP wipe section wipe system, Dalvik cache data & internal
3. go to TWRP wipe section format data, type yes
5. restore stock Vendor.img and stock Boot.img
6. flash GSI
Did you flashed GSI rom from point 6?
Yes, i follow this instruction and twrp say "OS no installed".
mientus25 said:
Yes, i follow this instruction and twrp say "OS no installed".
Click to expand...
Click to collapse
Check this... wiping
"for GSI it is better to wipe from stock recovery "
Hi. I have a MTK6739 which came with the "GO" version of Android (1GB ram). It came with Oreo, and it is GSI compatible (Arm with A only).
I recently wanted to give some GSI images a try and tried to flash AOSP. I tried to flash the system image using fastboot and also SP Flash Tool (of MTK). Both gave me the same error:
FAILED (remote: sparse image size span overflow.)
After getting this error, i reset my phone and my default system is still there, so nothing is being written to the system partition. I thought maybe treble AOSP images are larger than my phone's system partition but when i checked, the default system img of my phone is actually larger than the GSI images (I have also tried a "go" version of a gsi image with the same outcome).
What is my problem here please?
PS: My bootloader is unlocked.
What version of Android did your phone come with? If it's 8.X, then you have what is called Treble Legacy, which from what I am experiencing is sorta buggy. Do you have TWRP installed? It will help to have it, for a number of reasons. When a flash fails on mine, it typically wont boot the OS but rather just boot into TWRP, which makes it easy to simply kick it back in fastboot or do a wipe of a partition.
My BV5500 is GSI Enabled (Legacy) and even though it supports Treble, images won't load with TWRP even though it has Treble support. What images that do run have to be flashed with fastboot. I did use MTK tools to flash a few partitions again, but for the most part I use TWRP/Fastboot.
Mine also has the same behavoir as yours, you flash a ROM and /system is empty! (Or unchanged) So def a bug somewhere.
Chaos Storm said:
What version of Android did your phone come with? If it's 8.X, then you have what is called Treble Legacy, which from what I am experiencing is sorta buggy. Do you have TWRP installed? It will help to have it, for a number of reasons. When a flash fails on mine, it typically wont boot the OS but rather just boot into TWRP, which makes it easy to simply kick it back in fastboot or do a wipe of a partition.
My BV5500 is GSI Enabled (Legacy) and even though it supports Treble, images won't load with TWRP even though it has Treble support. What images that do run have to be flashed with fastboot. I did use MTK tools to flash a few partitions again, but for the most part I use TWRP/Fastboot.
Mine also has the same behavoir as yours, you flash a ROM and /system is empty! (Or unchanged) So def a bug somewhere.
Click to expand...
Click to collapse
Mine came with Android 8.1. Unfortunately my device doesn't have TWRP. In my situation, the flash fails but the phone still boots to its original OS. So nothing is overwritten. What i didn't do however is that i didn't "wipe" the partition before flashing the gsi image. And why should i anyway? The default flashing software of MTK (SP Flash Tool) doesn't even have a wipe option. It just overwrites to the partition. I never had to wipe the old rom to flash the stock rom before, it happened automatically.
Did you have any success with any of the gsi images that you have tried?
twilightened said:
Mine came with Android 8.1. Unfortunately my device doesn't have TWRP. In my situation, the flash fails but the phone still boots to its original OS. So nothing is overwritten. What i didn't do however is that i didn't "wipe" the partition before flashing the gsi image. And why should i anyway? The default flashing software of MTK (SP Flash Tool) doesn't even have a wipe option. It just overwrites to the partition. I never had to wipe the old rom to flash the stock rom before, it happened automatically.
Did you have any success with any of the gsi images that you have tried?
Click to expand...
Click to collapse
Yes, XenonHD and AOSP GSI 8.1 Oreo "Go" work. Also, Lineage and RessurectionRemix work but are very slow. This is in part to Gapps.
In the end, I used AOSP GSI 8.1 Oreo "Go", which was designed for 1GB RAM devices, and since it's been tweaked to run on slow hardware, it runs plenty fast.
On my BV5500 I would often have trouble getting a flash to function. Sometimes I would have to use SP Flash to restore stock boot and stock recovery, and then it would boot, complain of corruption, ask me to wipe, then kick me back into fastboot, where I would flash the rom and twrp.
Sometimes when I tried to flash a ROM that had worked previously it would say it finished but the partition would be empty.
As regards to wiping, perhaps its a bug but I found that my chances of flashing were better if the system partition was wiped prior to flashing.
Oh, one more thing: when I flash these ROMS, they all are sparse images and send data in small chunks. At least when done via fastboot. Perhaps try a different ROM or re-download the ROM, it's possible it's corrupt. Worth a shot.
Chaos Storm said:
Yes, XenonHD and AOSP GSI 8.1 Oreo "Go" work. Also, Lineage and RessurectionRemix work but are very slow. This is in part to Gapps.
In the end, I used AOSP GSI 8.1 Oreo "Go", which was designed for 1GB RAM devices, and since it's been tweaked to run on slow hardware, it runs plenty fast.
On my BV5500 I would often have trouble getting a flash to function. Sometimes I would have to use SP Flash to restore stock boot and stock recovery, and then it would boot, complain of corruption, ask me to wipe, then kick me back into fastboot, where I would flash the rom and twrp.
Sometimes when I tried to flash a ROM that had worked previously it would say it finished but the partition would be empty.
As regards to wiping, perhaps its a bug but I found that my chances of flashing were better if the system partition was wiped prior to flashing.
Oh, one more thing: when I flash these ROMS, they all are sparse images and send data in small chunks. At least when done via fastboot. Perhaps try a different ROM or re-download the ROM, it's possible it's corrupt. Worth a shot.
Click to expand...
Click to collapse
Thanks for the reply. I will try wiping first and flashing after that. Let's see if it is gonna work.
PS: By the way, these images come as img.xz format. I first unpack them and get the img. Am i doing it wrong? Should i just flash the img.xz images?
twilightened said:
Thanks for the reply. I will try wiping first and flashing after that. Let's see if it is gonna work.
PS: By the way, these images come as img.xz format. I first unpack them and get the img. Am i doing it wrong? Should i just flash the img.xz images?
Click to expand...
Click to collapse
No, you are doing it correctly. I think they compress them to save bandwidth.
just need to resize that partition
twilightened said:
Hi. I have a MTK6739 which came with the "GO" version of Android (1GB ram). It came with Oreo, and it is GSI compatible (Arm with A only).
Click to expand...
Click to collapse
Which device? Please tell.
I have also Blackview A20 (go).
Flash stock with spflash. Only for stock
Let it reboot. reset. Allow it to reboot once again. Check everything GPS/wifi/bt. Enable ON
Do not connect to Google accounts. not needed.
Enable adb
Charge at least 90% - some devices will NOT flash and silently ignore.
fastboot erase system
fastboot flash system gsi.img
fastboot reboot
If it asks you a password, just type anything. Then it will ask you reset phone. Say OK.
all done
Note always check the sha1sum or md5sum of GSI. Despite having
kusti420 said:
just need to resize that partition
Click to expand...
Click to collapse
Excuse me, I'm new to this, would you have a tutorial? I have several phones that would help
kusti420 said:
just need to resize that partition
Click to expand...
Click to collapse
how can i resize the partition pls?
Hey guys and gals!
So I don't wanna keep posting on other ROM threads to be annoying, so I will create a thread of my own. How do one flash the system_ext.img coming from Stock (root) ? I absolutely cannot get any TWRP versions (Chinese or English) to function. I take my passcode off and it's always 0mb. Doesn't matter if I am on a custom ROM or not. It's just something I cannot get to work. ONE time, it seen my storage but it would not flash a ROM. SO how can I flash this image via fastboot?
Global version of OOS. Although, I am currently on EXTENDED. I said Stock because I'll always have a Crash Dump, and need to start over. It's also tiresome to flash YAAP (12-18-20) then use the updater to create the image. Again, some things with this device, I'm getting used to. I'm all for learning and testing everything. I just cannot find a way to flash this image or get TWRP to function.
Have a great day!
So I would suggest you update your fastboot tools, because once you have the partition created assuming you are coming from a rom that has the system ext img it shouldn't be a problem. For example this is what I did, I was on RR remix so twrp chinese was working ( by the way I don't know why it wouldn't work for you if it works for everyone else) from there its just a matter of flashing the zip that contains the img. You can try derp,evox, yaap etc. After that again just flash what ever rom you desire it shouldn't be any issues. Also to keep in mind that a11 with twrp does not work with a pin only with a pattern, even tho I have read you said you have no pin lock. Wouldn't really know why your device would be the case but you can try that out .
lil_kujo said:
So I would suggest you update your fastboot tools, because once you have the partition created assuming you are coming from a rom that has the system ext img it shouldn't be a problem. For example this is what I did, I was on RR remix so twrp chinese was working ( by the way I don't know why it wouldn't work for you if it works for everyone else) from there its just a matter of flashing the zip that contains the img. You can try derp,evox, yaap etc. After that again just flash what ever rom you desire it shouldn't be any issues. Also to keep in mind that a11 with twrp does not work with a pin only with a pattern, even tho I have read you said you have no pin lock. Wouldn't really know why your device would be the case but you can try that out .
Click to expand...
Click to collapse
Sorry for the delay. Wish XDA would alert me, better. So Chinese TWRP is working now, on XTEND. I dunno, sometimes it works and sometimes I get 0mb. I think that point, to go onto a ROM WITH that image, should be fine. Since I always had troubles, I'd only fastboot flash to different ROMs. Trust me, for all my time on Android, this device is making me needy and a big newb. I just waiting for that "then don't bother to flash anything and shut up" LOL! BUT then again, I'm not on r/jailbreak. So once the partition is created, I can go to a ROM without that image? Do you know how I can check? Because I would like to just flash Hydrogen but don't wanna jump to stock. I think I can just flash a ROM with it and reboot back to the bootloader without setting up, right?
draymond1987 said:
Sorry for the delay. Wish XDA would alert me, better. So Chinese TWRP is working now, on XTEND. I dunno, sometimes it works and sometimes I get 0mb. I think that point, to go onto a ROM WITH that image, should be fine. Since I always had troubles, I'd only fastboot flash to different ROMs. Trust me, for all my time on Android, this device is making me needy and a big newb. I just waiting for that "then don't bother to flash anything and shut up" LOL! BUT then again, I'm not on r/jailbreak. So once the partition is created, I can go to a ROM without that image? Do you know how I can check? Because I would like to just flash Hydrogen but don't wanna jump to stock. I think I can just flash a ROM with it and reboot back to the bootloader without setting up, right?
Click to expand...
Click to collapse
That img will always exist is part of android 11 so it will be the norm. Every rom in the future will have it as seen on some custom roms right now, I flashed the h2os from twrp since I was coming from derp. So I didnt go back to stock. When you flash that img a partition will be created so the space will be available for when you flash another rom. So in the case that for example you were on derp and decided to fastboot flash h2os 11 you will not have issues flashing with fastboot commands the system_ext to both slots. ( By the way you need to specify which slot so I recommend you have a custom rom prior on both slots better if it's a11 rom.) The command fastboot flash system_ext_a system_ext.img and system_ext_b system_ext.img is to be used when doing it with fastboot command from fastbootd. If you decide to go with twrp from any custom rom a11 like the ones mentioned before just flash and right after you flash format data. You will lose twrp since the zip has the new recovery from oneplus. Reboot to recovery and again format data reboot enjoy. If you want to use just regular fastboot method you have to flash every img in the zip like 23 or so don't rememeber in order for it to work. So to make it simple for you. Flash a custom a11 rom with twrp if you are on a custom rom already. To both slots. After reboot and have the rom settle by letting it start to home screen. Save the zip of h2os to the phone reboot to recovery flash h2os zip not don't reboot but in twrp go to wipe format data. Then reboot to recovery again it will reboot to stock recovery format data again reboot and enjoy.
You will still have a custom rom in the other slot and if you want to have the stock on both slots just use the ota system update form stock rom local upgrade
There you go it should be simple and quick it took me like ten minutes to set it up and flash yesterday. By the way despite being a beta I really enjoy h2os 11. Do expect some minor bugs since it's a beta build.
I'll leave a link so you can read about system_ext and android new partition going forward. https://source.android.com/devices/bootloader/partitions
lil_kujo said:
I'll leave a link so you can read about system_ext and android new partition going forward. https://source.android.com/devices/bootloader/partitions
Click to expand...
Click to collapse
You're a wealth of information! Thanks for helping me to understand!
Edit: I tried the installing of two ROMs but I couldn't get it. I tried XTEND and Derp. But I had trouble with Xtend not being able to boot after setting up Derp. I had to wipe data for it to boot. Then lost everything. Bleh.
Can I ask you for your recommendation for an A11 ROM to have on a slot?
draymond1987 said:
You're a wealth of information! Thanks for helping me to understand!
Edit: I tried the installing of two ROMs but I couldn't get it. I tried XTEND and Derp. But I had trouble with Xtend not being able to boot after setting up Derp. I had to wipe data for it to boot. Then lost everything. Bleh.
Click to expand...
Click to collapse
So just to give you some more context, when you have to different rom on each slot is normal you have to format data, one : because they might have different data format , example oneplus only supports ext4 while derp is f2fs. So when flashing derp and the other slot is xtended is expected you will have to format in some occasions it might boot but you will have a buggy experience. So now that you have two custom roms and twrp try flashing h2os and again always format data and format data again in stock recovery since that will change the data format to ext4.
draymond1987 said:
Can I ask you for your recommendation for an A11 ROM to have on a slot?
Click to expand...
Click to collapse
Derp works perfect, that is the one I was coming from.
lil_kujo said:
So just to give you some more context, when you have to different rom on each slot is normal you have to format data, one : because they might have different data format , example oneplus only supports ext4 while derp is f2fs. So when flashing derp and the other slot is xtended is expected you will have to format in some occasions it might boot but you will have a buggy experience. So now that you have to custom roms and twrp try flashing h2os and again always format data and format data again in stock recovery since that will change the data format to ext4.
Click to expand...
Click to collapse
So I can have derp AND Hydro running? But like, when I format data, it was a full data wipe. I guess what you're talking about, right? Like I said, both ROMs kinda worked but it force a "fastboot -w". Maybe since I can get TWRP to work, I can wipe data there, and not touch user data?
draymond1987 said:
So I can have derp AND Hydro running? But like, when I format data, it was a full data wipe. I guess what you're talking about, right? Like I said, both ROMs kinda worked but it force a "fastboot -w". Maybe since I can get TWRP to work, I can wipe data there, and not touch user data?
Click to expand...
Click to collapse
On 7t there is no such thing as dual boot you can have of course one rom in one slot and another different slot on the other slot and it would work, also when you fastboot -w you are not erasing the imgs, you are erasing user data. The imgs from the rom will always be there until you change them. There is no way of saving data because of what i mentioned before of the different dat file ext4 and f2fs, when you are on stock it will "make data work for it but not for other roms" because of the decryption issue for one and second because of the format ext4. The only two roms i have tried so far that you can have dual boot are EVO x and Derp because there code is so similar coming from the same dev. SO to answer your question, Yes you can have two different ROMS but the rom that you use for setup that will be the one that will take over, in this case stock will take over data, which means you wont be able to use the other slot till you format data again and get rid of the encryption so that the other rom can use data partition. I know it sounds complicated but it really is very simple.
It is rather simple. I did notice a few people using those ROMs in slots. I mean, it's not a big deal if I can have two ROMs. I do miss the days of dual booting though.
May I ask, and this isn't to make a ROM work with Stock on a slot. Can you convert the file system to F2FS? I stumbled across a ROM that said it was better on this device but I can't find that post.
draymond1987 said:
It is rather simple. I did notice a few people using those ROMs in slots. I mean, it's not a big deal if I can have two ROMs. I do miss the days of dual booting though.
May I ask, and this isn't to make a ROM work with Stock on a slot. Can you convert the file system to F2FS? I stumbled across a ROM that said it was better on this device but I can't find that post.
Click to expand...
Click to collapse
yes you can, it depends, if the rom supports it. the fastboot way is way to complicated so twrp is the best option, when you choose wipe you will see a setting that says advanced, from there you choose data and click the option change format or repair then you will see some options. do note that when you change the type it will erase your data. do note that only data will change your system data will still be ext4.
lil_kujo said:
yes you can, it depends, if the rom supports it. the fastboot way is way to complicated so twrp is the best option, when you choose wipe you will see a setting that says advanced, from there you choose data and click the option change format or repair then you will see some options. do note that when you change the type it will erase your data. do note that only data will change your system data will still be ext4.
Click to expand...
Click to collapse
Ahh okay, I think I understand a little better now. Thanks for everything so far!