Hello all,
A few months back I unlocked my Mi 9 SE and rooted it using TWRP+Magisk, so fine so good. I then wanted to go on and install a custom ROM, but every time I tried, I just got my phone stuck in a bootloop and had to reflash MIUI using the scripts provided by Xiaomi (MiFlash/ .flash_all). After that, I decided I would not try meddling with ROMs again until had a better understanding of the (basic) underlying workings of this stuff.
After doing some research on my own I got answers to some of my confusion, but a lot remain, which is why I'm now trying my luck here. Maybe there is a "beginner's guide" of sorts somewhere on this forum, but so far I haven't been lucky in finding any. So, if any more experienced "flasher" or maybe even developer could clarify some things for me, and perhaps others, that would be great!
Firmware/Vendor
Firstly, the thing that has confused me since the beginning is the concept of firmware/vendor. I understand that the firmware of Xiaomi phones can be found easily on the internet and that it contains some amount of proprietary software such as drivers. However, while in some flashing instructions it is clearly indicated to "flash fw" after wiping, in others this is not mentioned at all. Is this because some ROMS already contain those drivers and others don't?
Then comes the question of "vendor". Again, some guides mention this, some don't, and on the site http://xiaomifirmwareupdater.com/, where one can find the fw, there is also a section for "vendor" files. So my question here is: what is the difference between vendor and firmware, and is either of them necessary before installing ROMS?
General Questions
From all of this, the way I picture the contents of an android phone are, from low to high level:
Bootloader (like the BIOS on a computer) ==> Firmware (Basic proprietary drivers) ==> Kernel ==> Rest of the OS (Implicit question: how correct is this picture?)
The kernel, from what I gather, is included in the flashable images of most ROMS, and the devs in turn use either the stock kernel from Xiaomi of some custom one like Kowalski's.
Question: What is the distinction between the firmware and the kernel? Since both are, in the beginning, made by Xiaomi, why are they separate things if they serve a similar purpose (drivers and Hardware/Software communication)?
Also, "bonus question" (just out of curiosity): I've heard that the only way to actually hard-brick your phone (other than hardware damage) is to somehow mess up the bootloader (kind of like corrupting the BIOS on a computer). How could this happen?
ROM Build
Finally, a few questions if any ROM dev stumbles upon this post, since apart from the practical aspects I'm also curious about the way a ROM is actually ported to a specific device, say our beloved little grus. Again, I'll just say what I understood so far and you guys can then correct me. From what I read in the building instructions for LineageOS on other devices, the way to proceed is to get the source code of the ROM itself by cloning the repo and then adding device-specific code (Kernel, device tree and Vendor Blobs) before proceeding to actually build the Image. My questions are, apart from if this is correct:
- How intercompatible are these components? Is a device tree specific to a certain kernel? To a certain ROM? Could one use, say, the kowalski DT with the stock kernel from Xiaomi?
- Again, what is the difference between "vendor blobs" and the "vendor" files mentioned above?
I know this is a very long post and I'm asking a lot of unrelated questions, but I hope that if someone takes the time to read through it and answer at least some parts of it, this could be useful in the future not only for me but also any other beginner trying to get into custom ROMS on Xiaomi phones. Cheers!
Wouldn't agree with your firmware definition (although you probably consulted like Wikipedia - their definition is more like for embedded systems like remote controllers or so)
Download Xiaomi Fastboot firmware from:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Its tgz file, hence to unpack, you have to un-gzip and un-tar (you can use 7-zip on Windoze or MiXPlorer to do everything on your phone), open Images folder and look how many img files it contains.
Besides like System, Vendor, etc, it even contains image for Recovery (Recovery is not part of Android, you separately boot to Android, Recovery or Fastboot - the last is part of Bootloader).
Manufacturer can even push new Bootloader via the firmware OTA (I recall how Huawei pushed new bootloader.img in 2018 via its OTA updates, to invalidate the previous merhods for unlocking Bootloader, making it 'almost' impossible to unlock the new Bootloader)
Consider firmware as the opposite of hardware, it's all firm software on your phone: Bootloader, Recovery, Android - all except your user apps, settings and Data you will install to Data or Internal memory.
Firmware also does not overwrite some specifical info related to your particular phone like IMEI(s), Widewine L1 cert (hence if you dropped to L3 by installing custom ROMs, you cannot recover L1 by reflashing the full firmware)
And Kernel is just the Android kernel (as inherited from Linux kernel), similarly like Windows OS has its own kernel
Thanks for your reply, I think that there is a misunderstanding: What I'm talking about when I say Firmware is this thing: (taken from the site you referenced). This is a small (~70mb) zip archive that contains no images, only binaries. I'm NOT talking about the whole Xiaomi ROM, which is indeed a large tgz and contains all the images you mention.
{
"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"
}
To clarify, what confuses me in flashing guides is (example from evolution x rom) the line where it says "Flash FW & BB", or sometimes just "flash fw"
lachesis197 said:
Thanks for your reply, I think that there is a misunderstanding: What I'm talking about when I say Firmware is this thing: (taken from the site you referenced). This is a small (~70mb) zip archive that contains no images, only binaries. I'm NOT talking about the whole Xiaomi ROM, which is indeed a large tgz and contains all the images you mention.
View attachment 5181291
To clarify, what confuses me in flashing guides is (example from evolution x rom) the line where it says "Flash FW & BB", or sometimes just "flash fw"
View attachment 5181295
Click to expand...
Click to collapse
Don't really now what does it mean in the context of installation guide for the given custom ROM
Under Mi 9T/Redmi K 20 ROMs subforum, there are tons of threads, each one for a particular custom ROM.
For most of them there are also Telegram channels
IMO, you can better clarify by asking there, where the ROM users are subscribed and actively participating
Hello, I Have a Samsung galaxy s9 Exynos. I have rooted it with magick. Now i want to use evolution Rom but when I am trying to flash with TWRP it is showing--
Vendor Image on the device is NOT compatible
Expected Version: 29_ETFS
You can download it from mega.NZ/FM/F9VHHALY.
what to do. can Someone help?
Manglesh____ said:
Hello, I Have a Samsung galaxy s9 Exynos. I have rooted it with magick. Now i want to use evolution Rom but when I am trying to flash with TWRP it is showing--
Vendor Image on the device is NOT compatible
Expected Version: 29_ETFS
You can download it from mega.NZ/FM/F9VHHALY.
what to do. can Someone help?
Click to expand...
Click to collapse
You missed the Forum - this is for Xiaomi Mi 9 SE - do you really want a Xiaomi user to guide you about flashing your Samsung and to brick your phone
zgfg said:
You missed the Forum - this is for Xiaomi Mi 9 SE - do you really want a Xiaomi user to guide you about flashing your Samsung and to brick your phone
Click to expand...
Click to collapse
thank for telling man i really missed ,anyways the problem is solves now.
@lachesis197 I'm in the same spot you where 1,5 years ago.
It seems in the Android customization community most info to be found is of the sorts "to get this, do this". But very little of why something works the way it does. Very little explanations of what it all means.
hagekic548 said:
@lachesis197 I'm in the same spot you where 1,5 years ago.
It seems in the Android customization community most info to be found is of the sorts "to get this, do this". But very little of why something works the way it does. Very little explanations of what it all means.
Click to expand...
Click to collapse
Here I am about a year later after you! It seems so hard to find 'curated' info. All this info is all over the place.
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"
}
LineageOS is a free and open-source operating system for smartphones and tablet computers, based on the Android mobile platform.
This is an unofficial build of LineageOS for the Pixel 2 (walleye). I always liked Lineage (and its predecessor CyanogenMOD) as well as the Google line of phones. Unfortunately having a Google Pixel phone isn't certainty for a lot of custom ROMS anymore, so that's why I decided to compile my own version. It's been quite challeging, but I think I finally have a build that is good enough to share.
About
This ROM is is always built straight from the LineageOS sources found on https://github.com/lineageos. There are only 3 changes in order to get this build:
The binaries for this ROM come from AICP
GApps are compiled with the ROM from MindTheGapps including the Pixel specific bits for unlimited photo upload for instance
Disabled Android Verity Boot (AVB), so we don't get the security warning when booting
I am not a developer, I only build this ROM and it reflects the the current status. If there are any things missing or not working I suggest to contact the LineageOS team, they are the real geniuses here and deserve all the credits. I will try to keep this ROM updated on a regular basis.
First Installation
Installing the ROM can be a little hard, especially the first install. Upgrades will be relatively easy though. This first setup is only needed when coming from a different ROM then this. I can't support you if you did't follow this first installation. Be warned it will wipe your user data in the process
In order to get the initial setup and also to use the same vendor partition as the ROM you have to install the latest stock Pixel 2 image from Google found here. More info on unlocking your phone and installing the latest Pixel image can be found in the excellent post by @nathanchance found here. The bestway to flash a stock ROM in my opinion is @Deuces' script found here. The benefit of this is that it'll flash the image to both slots, so they are both on the latest build, including the bootloader and radio. All instructions for using the script are inside the forum. After flashing the image make sure you reboot at least once (no need to set it up now though).
Place the ROM and optionally the TWRP zip and root from (Magisk or from LineageOS (not tested) on the phone and reboot to recovery by using the command line (fastboot boot twrp.img)
Wipe 'data' and 'Dalvik / Art Cache' from TWRP - Wipe - Advanced Wipe. Optionally you should also delete the Android folder on your internal storage through the TWRP File Manager
Flash the ROM and optionally the TWRP zip and reboot the phone
Upgrades to new version
After the hard initial work to get the ROM installed it's going to be easy for upgrades to new versions.
Download the new ROM and reboot of flash to TWRP
Flash the new ROM and optionally TWRP. If you want to flash another kernel or a root solution you will have to reboot you phone, so it switches slots and let it boot normally. Then go back to recovery and flash in this order: TWRP - kernel - Magisk and reboot
After a monthly update from Google and only when LineageOS also adapted to the latest monthly sources (I will tell you this) you will have to do an extra step:
Download the latest Lineage OS ROM and place it on the internal storage
Download the latest image from the Google Factory Images site and run Deuces' script. No need to wipe your data!
After the script finishes it automatically boots into the bootloader. From here fastboot into TWRP and flash the previously downloaded new ROM, optionally followed by TWRP.
Optionally, after a reboot you can flash Magisk and/or another kernel.
Not working
Substratum
Use Powerbutton for flashlight when Ambient Display is set
Active Edge
Now playing
Downloads
I'm not maintaining this project anymore, download link has been removed.
Happy flashing
Miraculous... Will flash soon. Thank you for keeping Pixel 2 relevant.
Is link not posted yet?
I want to thank you for posting. But, I get the feeling this will just be closed as well really soon. Hope this sticks around, because XDA is not what it use to be, at all!
JCBiznatch said:
I want to thank you for posting. But, I get the feeling this will just be closed as well really soon. Hope this sticks around, because XDA is not what it use to be, at all!
Click to expand...
Click to collapse
Why would it be closed?
JCBiznatch said:
I want to thank you for posting. But, I get the feeling this will just be closed as well really soon. Hope this sticks around, because XDA is not what it use to be, at all!
Click to expand...
Click to collapse
I completely agree...
Any chance for an MD5
jascolli said:
Any chance for an MD5
Click to expand...
Click to collapse
Added in the same folder:
MD5: a28cd4f3cabe627fbe99cbe1485cba3f
TCUofficial said:
Why would it be closed?
Click to expand...
Click to collapse
I don't have a clue. It just seems that anyone who posts a ROM gets the thread closed. It's almost as if they don't want walleye to have any development.
Just check this forum out compared to the pixel XL 2 forum.
Thanks very much for sharing this. I've got it installed and it's running fantastic.
Everyone who has had a rom thread has closed the thread for different reasons, time, family, frustration or lack of support etc...
I see don't see why we should be negative and assumee the same is the case with this build. Every rom thread has produced better and more stable builds as time progressed.
@Joregen2009, I have seen your name around before, appreciate you building!!
razrlover said:
Everyone who has had a rom thread has closed the thread for different reasons, time, family, frustration or lack of support etc...
I see don't see why we should be negative and assumee the same is the case with this build. Every rom thread has produced better and more stable builds as time progressed.
@Joregen2009, I have seen your name around before, appreciate you building!!
Click to expand...
Click to collapse
It's my pleasure. I only wanted to share my build, because I know that many of you much be as frustrated as me for the lack of ROMs for our device.
We'll see how long this thread will hold. If it's up to me I'll try to provide at least a weekly build from the actual sources, or whenever there are some major changes in the sources that are important for our device until the Lineage Team declares our device official. Let's hope that happens soon and that this thread can contribute to that.
Awesome! Thanks for this ROM. Any known issues one should be aware of before flashing?
Does Lineage have Substratum support ?? Having trouble connecting......
Update. Found answer - : no substratum support
@jorgen2009
Hey thanks so much for the ROM. Its working great!
Is there any chance you could link me the kernel source for this specific build? (Pixel2)
I'm trying to figure out how to rebuild it with the drivers for my TP-LINK WN722N V1.
I really don't know what I'm doing but I'm trying to learn.
I'm trying to follow this guide to accomplish this.
https://forum.xda-developers.com/showthread.php?t=2338179
I do have Kali for Magisk up and running just fine.
Lsusb command shows my WiFi Adaptor but the kernel won't let me use it.
Thanks so much for reading, if what I'm trying to do is stupid feel free to let me know why haha. If I get it to work I'll share it with everyone.
redsmith said:
Awesome! Thanks for this ROM. Any known issues one should be aware of before flashing?
Click to expand...
Click to collapse
The only thing that I am aware of is the fact that the battery LED isn't working, but that will be solved in the next build
tkacer said:
Does Lineage have Substratum support ?? Having trouble connecting......
Update. Found answer - : no substratum support
Click to expand...
Click to collapse
Sorry, than I fear it's not supported by LineageOS in general yet, I don't use it myself
gahndii said:
@jorgen2009
Is there any chance you could link me the kernel source for this specific build? (Pixel2)
Click to expand...
Click to collapse
Sure, see LineageOS sources on github, I didn't touch the kernel in this build:
https://github.com/LineageOS/android_kernel_google_wahoo
I am still getting the security warning when booting. Am I the only one so I missed something?
Other question: is the Trusted Faces not working because the used GApps package has not been modified for the Pixel, or the ROM has got some incompatibility issue?
Great job. Just a little bug: Long press power button to turn on torch is not working when Ambient Display is set to always on.
banciii said:
I am still getting the security warning when booting. Am I the only one so I missed something?
Other question: is the Trusted Faces not working because the used GApps package has not been modified for the Pixel, or the ROM has got some incompatibility issue?
Click to expand...
Click to collapse
Are you sure you are on the April vendor? Your vendor version must be the same as the ROM needs (currently the April one).
Trusted Faces is GApps related yes, it's not in MindTheGApps. I'll try to make a build with OpenGApps in to see if that works. Both Face Detection for Media and Face Unlock are in the Nano package (https://github.com/opengapps/opengapps/wiki/Nano-Package)
redsmith said:
Great job. Just a little bug: Long press power button to turn on torch is not working when Ambient Display is set to always on.
Click to expand...
Click to collapse
I'll put it in the known issues list in the OP later this week for an overview
Another build is up. This time I used OpenGapps so you might need to clear the Store cache. I had no problems upgrading myself. The Text-to-speech improved a lot with these Gapps for me.
New in this build is the LED light when charging and some basic stuff for more compatibility with our device and some networks. Also all the normal changes since the last build for LineageOS are in of course. For the download link see the OP. I also adjusted the OP a bit to show the things that are known not to work. Let me know if I missed something so I can adjust the list
{
"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"
}
Download - h930, h932
Buy me a coffee or beer
smooth rom with microg will update after using. thank you for the rom
known bugs?
Nice Rom!
But there are some minor things I want to mention about this rom.
1. Show status bar clock with seconds not work.
2. Quicksettings show 3 Rows even with the media player. (See Picture)
3. Can't double tap to wake.
Thank you for your nice work for bring another android 11 custom rom to my dear LG V30+ and hope my bad English will not make you confuse.
I don't have data when I boot up.
I'm sorry but I'm having the toughest time upgrading to your rom. I came from rooted stock android9 h932 that I haven't touched in years. I spent the last 5hours flashing different firmwares and searching for what is wrong but no luck. What am I missing? Am I running the wrong firmware?
xprog said:
I don't have data when I boot up.
I'm sorry but I'm having the toughest time upgrading to your rom. I came from rooted stock android9 h932 that I haven't touched in years. I spent the last 5hours flashing different firmwares and searching for what is wrong but no luck. What am I missing? Am I running the wrong firmware?
Click to expand...
Click to collapse
That's an issue for all custom rom installation
I also saw that issue the first time when I try to flash a custom rom on it
What you need to do is format data in recovery
Remember to backup your data if that's important to you
Press Wipe>Format Data in TWRP
Than everything will be fine
Just reboot your phone (That doesn't wipe your system away)
Enjoy the new rom
This erased all of my local data after flash (Internal Storage)
I mostly keep my stuff in the cloud but some memes you just don't find the second time
Would be good to add some warning in case someone keep some more critical stuff than memes...
nice
First of all I just want to say thank you for bringing this to the 932!!!! But my wifi doesn't work. Anyone know how to fix this
NVM found a random wifi fix on Google from some telegram group lol
@ChazzMatt How is this possible for H932? LOS-17 based roms don't even support H932 but this one, a 11.0 rom does?
ROOT Your LG V30! and Custom ROMs FAQ
ROOT YOUR LG V3O! Bootloader unlock, install TWRP, root any V30/V30+/V30S on the planet! * WTF V30/V30+/V30S Bootloader Unlock, TWRP and Root INSTRUCTIONS The WTF bootloader unlock, TWRP installation, root method (link above) works on EVERY...
forum.xda-developers.com
"Whereas you do need to update to stock Pie first before trying to install "Android 10" LOS-17 custom ROMs. However, while those ROMS are improving they are still have a few more bugs than LOS-16. So if you try them, don't like them and instead want to run the older "Pie" LOS-16 based custom ROMs, then you've already ignored the warning above. Sorry, T-mobile H932 is not (yet) compatible with any of the "Android 10" AOSP/LOS-17 custom ROMs."
wa ,Android 11
noddledizzy said:
@ChazzMatt How is this possible for H932? LOS-17 based roms don't even support H932 but this one, a 11.0 rom does?
ROOT Your LG V30! and Custom ROMs FAQ
ROOT YOUR LG V3O! Bootloader unlock, install TWRP, root any V30/V30+/V30S on the planet! * WTF V30/V30+/V30S Bootloader Unlock, TWRP and Root INSTRUCTIONS The WTF bootloader unlock, TWRP installation, root method (link above) works on EVERY...
forum.xda-developers.com
"Whereas you do need to update to stock Pie first before trying to install "Android 10" LOS-17 custom ROMs. However, while those ROMS are improving they are still have a few more bugs than LOS-16. So if you try them, don't like them and instead want to run the older "Pie" LOS-16 based custom ROMs, then you've already ignored the warning above. Sorry, T-mobile H932 is not (yet) compatible with any of the "Android 10" AOSP/LOS-17 custom ROMs."
Click to expand...
Click to collapse
Dev @ShapeShifter499 finally solved merging the two separate LOS trees to create universal build for all V30/V30+/V30S. All LOS-based 10 & 11 ROMs since first week of October, 2020 now also support T-Mobile H932 -- as long as they have incorporated @ShapeShifter499's changes. By now, most have.
We posted about it in the LOS ROM threads. See HERE and read the next few posts after that:
Since temporarily moving to another country for family reasons right about that time, I haven't had enough spare time to (yet) edit my ROMs FAQ to mention that. I'm now back in the U.S., but the months since have been very busy!
======
This ROM here is actually posted in the wrong forum section. I'm going to request it be moved to the ROMs section...
ChazzMatt said:
Dev @ShapeShifter499 finally solved merging the two separate LOS trees to create universal build for all V30/V30+/V30S. All LOS-based 10 & 11 ROMs since first week of October, 2020 now also support T-Mobile H932 -- as long as they have incorporated @ShapeShifter499's changes. By now, most have.
We posted about it in the LOS ROM threads. See HERE and read the next few posts after that:
Since temporarily moving to another country for family reasons right about that time, I haven't had enough spare time to (yet) edit my ROMs FAQ to mention that. I'm now back in the U.S., but the months since have been very busy!
======
This ROM here is actually posted in the wrong forum section. I'm going to request it be moved to the ROMs section...
Click to expand...
Click to collapse
That's a good new indeed. But... what's the point at the same time. US carriers will not work with custom roms starting this year.
I'm a bit confused where to download lineageos for my phone.
I found two official links, why are there two?
Which link should i use to download lineageos and why?
LineageOS Downloads
download.lineageos.org
Sony Xperia XA2 (pioneer) - LineageOS ROMs
LineageOs ROM Sony Xperia XA2 (pioneer) Official roms Download last nightly build (2023-01-05) (mirror EU).LineageOS 19.1 – [ Android 12.1 (Snow Cone) ] [Recovery file (2023-01-05) (mirror EU)] Previous version (nightly) (2022-04-21) LineageOS 18.1 – [ Android 11.0 (Red Velvet Cake) ] [Recovery...
lineageosroms.com
The "top domain" which brought me to the download page was this:
LineageOS Downloads
download.lineageos.org
Home - LineageOS ROMs
Welcome to LineageOS ROMs, this site is listing the official changes and downloads for LineageOS and many other useful tools, such as CF-ROOT, G-APPS (Google Apps), Recoveries (TWRP Recovery, CWM Recovery) and much more. DISCLAIMER: LineageOS does not develop official ROMs for all brands and...
lineageosroms.com
Both these links provide a list of support phone manufactuers and models.
Why are there two different lists with sometimes different results?
lineageos.org is the real deal (or at least I'd love to believe so, the other one doesn't even list any maintainers)
Still, interesting and valid question - i don't know neither who is running the other one... but perhaps this helps:
https://forum.xda-developers.com/t/lineageosrom-com.3535772/#post-70692025
SigmundDroid said:
lineageos.org is the real deal (or at least I'd love to believe so, the other one doesn't even list any maintainers)
Still, interesting and valid question - i don't know neither who is running the other one... but perhaps this helps:
https://forum.xda-developers.com/t/lineageosrom-com.3535772/#post-70692025
Click to expand...
Click to collapse
Damn, i downloaded lineageos from lineageosroms.com and already installed it.
To be honest even if that doesn't mean anything it looks legit, there is no trace of google on my device and it works fine.
One thing i noticed, i can't even find a lineageosrom for my device on lineageos.org, it simply isn't listed.
In case you are woondering, i have a samsung galaxy s7.
This is where i downloaded the rom https://lineageosroms.com/herolte/
I can't find any rom for the S7 on the lineage org domain...
LineageOS Downloads
download.lineageos.org
Devices | LineageOS Wiki
wiki.lineageos.org
Wikipedia says lineageos.org
But what choice do i have.. none there is no rom on the org domain so ill have to trust the .com version..
Wired.
Edit: The rom i downloaded is a nightly build, there is no stable one, maybe that's the reason?
Librem5OS said:
samsung galaxy s7
Click to expand...
Click to collapse
Ah, I see, that'll be tricky then...
I just checked and seems most people are on LOS17:
https://stats.lineageos.org/model/herolte
Remembered something vaguely from webarchive and found this:
https://archive.org/search.php?query=lineageos 17 backup
Alas, couldn't see any herolte
Finally found this:
https://forum.xda-developers.com/t/stable-lineageos-17-1-for-galaxy-s7-build-38.3980101/
https://ivanmeler.github.io/devices/herolte.html
Should be a better choice than lineageosroms, eh?
SigmundDroid said:
Ah, I see, that'll be tricky then...
I just checked and seems most people are on LOS17:
https://stats.lineageos.org/model/herolte
Remembered something vaguely from webarchive and found this:
https://archive.org/search.php?query=lineageos 17 backup
Alas, couldn't see any herolte
Finally found this:
https://forum.xda-developers.com/t/stable-lineageos-17-1-for-galaxy-s7-build-38.3980101/
https://ivanmeler.github.io/devices/herolte.html
Should be a better choice than lineageosroms, eh?
Click to expand...
Click to collapse
Thank you so much!! Appreciated!
I would have never found that, already installed!
Also the statistics you sent very interesting https://stats.lineageos.org/model/herolte, second most users have set their region to unknown, mine is US but im not from the US, can i change the region by any chance? Can't see to find an option. I can't remember selecting US at all.
Wow, the new lineageos version is... it is...
There are some apps like storage manager or shell that have access to physicall motion detection and much much more permissions and the problem is, the option to disable that access IS GREYED OUT, what's going on with lineageos??
Librem5OS said:
what's going on with lineageos??
Click to expand...
Click to collapse
Blame google at this point, I suffer from similar problems (backup with syncthing). It's about time for better system like plasma mobile...
Librem5OS said:
can i change the region by any chance
Click to expand...
Click to collapse
Yes, can be tricky if you have weird combos (like english and non-english settings, eg ISO-date). It's called localization and you'll find in the settings. Apropos, spend an evening or so and check every single item of there - there is so much finetuning available
Don't get me wrong but welcome home in the ever changing world of LOS (both in sarcastic and an honest way)
SigmundDroid said:
Blame google at this point, I suffer from similar problems (backup with syncthing). It's about time for better system like plasma mobile...
Yes, can be tricky if you have weird combos (like english and non-english settings, eg ISO-date). It's called localization and you'll find in the settings. Apropos, spend an evening or so and check every single item of there - there is so much finetuning available
Don't get me wrong but welcome home in the ever changing world of LOS (both in sarcastic and an honest way)
Click to expand...
Click to collapse
Are you saying google has influence over lineageos? I mean as far as i know, google owns android.
However android is opensource (atleast most of it as far as i know, but not fully open source).
It's just.. i think lineageos is great but i am not sure if it can really be trusted anymore, these changes that i noticed are a bit suspicious in my opinion.
> Apps > Special Acces > Useage Data Access
By default all apps have useage access... This was not the case in previous versions
> Apps > Special Acces > Device Administrator
Is storage manager an active device administrator in lineage 19.1 yes or no?
The "show system" option is gone so there is no way to know if the app has access or not...
Under privacy settings what happened to the setting "start on boot"
In previous versions there was this option to deny individual app access, now it's gone...
This doesn't seem good at all...
PS: my region changed automtically (or it was after i changed language)
But why does the lanuage have impact on region?? Anyways this is not important, but what i would like to know is how so many devices have their region shows as "unknown" in the statistics you sent.
How do i set my location to unknown?
And the things i mentioned above, have you got any tip where i could share this in form of a question to the developers? I just want to know why this changes happened and if lineageos is going a bad path.
Librem5OS said:
google owns android.
However android is opensource
Click to expand...
Click to collapse
Well, it's "complicated". Making a recent android run on specific devices is no easy thing (companies)... not any easier on older devices (devs/maintainers).
Still, I think LOS is one best things (just consider the companies' bloatware)
Librem5OS said:
not the case in previous versions
Click to expand...
Click to collapse
Quite specific, eh? I wouldn't know, still on LOS18... but such things are part of "the ever changing world" Perhaps asking again in "your" device's forum?
PS: Consider a second device for testing other/new versions/ROMs/OSes... you don't wanna brick your main gadget.
SigmundDroid said:
Well, it's "complicated". Making a recent android run on specific devices is no easy thing (companies)... not any easier on older devices (devs/maintainers).
Still, I think LOS is one best things (just consider the companies' bloatware)
Quite specific, eh? I wouldn't know, still on LOS18... but such things are part of "the ever changing world" Perhaps asking again in "your" device's forum?
PS: Consider a second device for testing other/new versions/ROMs/OSes... you don't wanna brick your main gadget.
Click to expand...
Click to collapse
If i would have to find a new phone today most likely would go for google pixel (i hate google) but then flash grapheneOS on it, or maybe librem or fairphone, but i'm not familiar with them yet.
PS: i have no second device.
Also late me share an issue that i ran into today
I installed TWRP 3.6.2 and LineageOS 19.1 on my Samsung Galaxy S7, then i installed whatsapp (for testing purposes not to use it, because its facebook spyware) then after the testing was done i wanted to uninstall whatsapp but when i pressed uninstall the responsible service always stopped, but i was able to uninstall ANY other app expect whatsapp (facebook) decided to dig itself so deep in my phone i was unable to uninstall it, (besides even if i managed to uninstall it i am sure there will remain some "hidden" whatsapp activity on the device.
ANYWAYS, i decided to wipe my phone clean by using TWRP, after doing that i used TWRP to flash/install LineageOS 19.1 on my phone again, however i am now STUCK in the TWRP "loading screen" it simply won't go to recovery mode so i am unable to install LineageOS or do anything at all.
Next i will try to use adb to boot into recovery, if that doesn't work i will try to flash LineageOS 17 or 18 on the device.
The only thing working now is downloadmode.
EDIT:
I tryed useing universal adb drives, not to be confused with adb fastboot and platformtools.
Downloaded here https://adb.clockworkmod.com/
Don't know if this is legit https://developer.android.com/studio/releases/platform-tools
I just didn't download it after seeing the license agreement and google involvement. Can it be trusted?
Anyways... in cmd i typed adb devices
Output: daemon started succesfully
Output: list of devices attached
I tryed using: adb reboot recovery
Output: error no devices/emulators found
Then i tryed flashing the oldest twrp 3.0.0 with odin and it worked, but after odin said PASS the phone behaviour has not changes, it's the same as before stuck in twrp mode but not booting into recovery.
My phone is now useless it does not boot at all, not in twrp mode and not in recoverymode, however this is only the case when the phone is not connected to a charging/usb cable, if it is connected the phone vibrates once and the display goes on saying "samung galaxy s7 powered by android".
This display is forever, nothing happens it's stuck.
I am unable to boot into recovery (twrp) mode by presing home+power+volumeup, however the ONLY thing i can do now is boot into downloadmode by pressing home+power+volumedown.
I can use oding to flash a recovery or OS, i can use adb.
But i don't know what to do now.
(One person with same issue said they took out they battery, well f*ck modern phones...)
{
"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"
}
EDIT:
adb devices no longer working (reason unknown - atleast as far as i can tell...)
will try flashing stock rom...
EDIT SOLVED
fixed it... flashed twrp like 6 times... sometimes it got stuck, sometimes it worked, then stuck on twrp loadingscreen but now it booted into recovery... i used "nand erase" on the last attempt, maybe that did the job, who knows..
UPDATE
twrp 3.6.2 is now installed and booting to recovery.
but after installing lineageos 19.1 the phone is stuck in a boot loop.
twrp shows "running open recovery script" it displays some errors and reboots eternal.
UPDATE - DONE
Woah... finally after all this wired mess... formated data with twrp and wiped everything then lineageos installation worked, no stockrom needed.
Holy, missed most of your last posts but glad you made it! Looks like real work - as in blood, sweat and tears... and probably a lot of cursing
I've been looking around for roms for this model and tried out a few but I noticed some roms aren't just where you can fastboot install the zip. some roms have a big file named payload in the zip so the usual fastboot install doesn't work. so my question is how do you install a rom with the payload in it? I switched from galaxy devices to the pixel so this is new to me
bjf189 said:
I've been looking around for roms for this model and tried out a few but I noticed some roms aren't just where you can fastboot install the zip. some roms have a big file named payload in the zip so the usual fastboot install doesn't work. so my question is how do you install a rom with the payload in it? I switched from galaxy devices to the pixel so this is new to me
Click to expand...
Click to collapse
payload.bin is used in OTA updates (flashed using ADB).
Most ROMs have installation instructions so it's best to follow these. Most (if not all) custom Pixel ROMs require you to be on July Stock build and to wipe in recovery mode before flashing.
There are 2 ways to flash ROMs on Pixels: through fastboot or ADB side loading via recovery mode.
Check the instructions listed by the developer.
Alekos said:
payload.bin is used in OTA updates (flashed using ADB).
Most ROMs have installation instructions so it's best to follow these. Most (if not all) custom Pixel ROMs require you to be on July Stock build and to wipe in recovery mode before flashing.
There are 2 ways to flash ROMs on Pixels: through fastboot or ADB side loading via recovery mode.
Check the instructions listed by the developer.
Click to expand...
Click to collapse
I'm aware of the installation instructions the devs supply but only rom on xda I found was evolution and its been discontinued. the other roms I found were through telegram which Most do not supply instructions as far as I could see. I was looking into the hentai rom (strange name) or the sparkOS to try out but I'm stumped on the whole installation bit
bjf189 said:
I'm aware of the installation instructions the devs supply but only rom on xda I found was evolution and its been discontinued. the other roms I found were through telegram which Most do not supply instructions as far as I could see. I was looking into the hentai rom (strange name) or the sparkOS to try out but I'm stumped on the whole installation bit
Click to expand...
Click to collapse
You need to be very careful about installing full operating systems from unknown sources. You never know what is going to be hidden in there.
What you really should be doing is either compiling yourself from source, or using builds from well recognized suppliers with full source available, and with full REAL IDENTIFICATION available for those responsible for it. GrapheneOS, for example.
96carboard said:
You need to be very careful about installing full operating systems from unknown sources. You never know what is going to be hidden in there.
What you really should be doing is either compiling yourself from source, or using builds from well recognized suppliers with full source available, and with full REAL IDENTIFICATION available for those responsible for it. GrapheneOS, for example.
Click to expand...
Click to collapse
I came across the evolution rom here on xds to see it was discontinued but the thread lead me to find telegram that had numerous devs on it with the rom list for the pixel that included grapheneOS. I've noticed many devs here use telegram as well for roms and communications. I would think that in this case, it all seems legit
bjf189 said:
I'm aware of the installation instructions the devs supply but only rom on xda I found was evolution and its been discontinued. the other roms I found were through telegram which Most do not supply instructions as far as I could see. I was looking into the hentai rom (strange name) or the sparkOS to try out but I'm stumped on the whole installation bit
Click to expand...
Click to collapse
if you're looking for a custom ROM, I'd suggest you try Derpfest or Zephyrus. Both are listed in this forum and have great reviews. Installation instructions are provided for both (just flash via fastboot).
Every ROM available for Pixel 6 have installation instructions available. I've yet to see one without. There are more than 10 ROMs available. I suggest you join the telegram pixel 6 chat group and get some guidance there.
bjf189 said:
I'm aware of the installation instructions the devs supply but only rom on xda I found was evolution and its been discontinued. the other roms I found were through telegram which Most do not supply instructions as far as I could see. I was looking into the hentai rom (strange name) or the sparkOS to try out but I'm stumped on the whole installation bit
Click to expand...
Click to collapse
Hentai OS no instructions? In the channel or group, you can call for user guides then the bot will share a pdf. I'm using Hentai OS for few weeks now.
I'm now with bootloader locked since they also provide custom avb key to relock bootloader and still enjoying volte,vowifi in unsupported region). future update is yes through adb sideload while the phone in recovery mode
{
"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"
}
bjf189 said:
I came across the evolution rom here on xds to see it was discontinued but the thread lead me to find telegram that had numerous devs on it with the rom list for the pixel that included grapheneOS. I've noticed many devs here use telegram as well for roms and communications. I would think that in this case, it all seems legit
Click to expand...
Click to collapse
HERE doesn't make ANYTHING "legit". This is just a web forum, nothing is verified for safety.
Hello everyone, I just bought the OnePlus 9 Pro 5G LE2123 Dual SIM 12GB+256G. Due to my inexperience, I ask for considerations in reference to a possible procedure for obtaining Root + TWRP permissions. I also ask if obtaining root permissions invalidate the warranty with some alleged counter (for example samsung knox counter). In the previous smarphone ( samsung galaxy note 9 ) I corrupted the EFS IMEI file by mistake and I don't want to repeat the same mistake. Thanks to all the Admins of the topic for your attention, as I can't help but be happy to be part of your oneplus family
{
"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"
}
[GUIDE] [Magisk] [Unlock / ROOT / Keep Root] OOS 13.1.0.500
Different variants of Magisk that are available for use : Magisk Variant Stable / Beta / Canary Release Official Android / OOS OOS 11 and above Maintainer topjohnwu Project Link GitHub Zygisk No...
forum.xda-developers.com
Thank you so much my friend
Congratulations on your OnePlus 9 Pro! Enjoy!!
You are phenomenal, I am reading the best guide indicated above and it is perfect and very clear in its explanation. I have only three questions:
To possibly send it to assistance, would it be enough to just lock the bootloader and flash the original boot?
Is it essential to have twrp recovery?
What bekup operation should I do to avoid stumbling into some errors ( ex. EFS IMEI)?
Thank you for your time.
pronegate said:
You are phenomenal, I am reading the best guide indicated above and it is perfect and very clear in its explanation. I have only three questions:
To possibly send it to assistance, would it be enough to just lock the bootloader and flash the original boot?
Is it essential to have twrp recovery?
What bekup operation should I do to avoid stumbling into some errors ( ex. EFS IMEI)?
Thank you for your time.
Click to expand...
Click to collapse
Use the MSM tool to get back to stock.
I don't install TWRP, but boot it in temp mode for flashing etc.
SwiftBackup app for backing up apps and data, call logs and sms. Messed up data, MSM tool to factory and restore with SwiftBackup. Copy internal storage to PC for it's backup.....
Thanks friend
Other questions
In your experience, do you recommend staying on OOS 13 or immediately flashing some of the custom roms you recommend?
Before flashing the new custom rom, which partition should I wipe?
Once the new custom rom is installed, for ota updates is the same procedure with magisk to maintain root permissions?
Thank you for your time @TheGhost1951.
pronegate said:
Thanks friend
Other questions
In your experience, do you recommend staying on OOS 13 or immediately flashing some of the custom roms you recommend?
Before flashing the new custom rom, which partition should I wipe?
Once the new custom rom is installed, for ota updates is the same procedure with magisk to maintain root permissions?
Thank you for your time @TheGhost1951.
Click to expand...
Click to collapse
As for custom roms, it is just a matter of choice. I have seen people that are happy and seen some that have had problems. As for me I prefer stock because it is made specifically for your phone. Less chance of problems. If you install a custom ROM it is usually advisable to go into recovery and factory reset. That is the wiping that is talked about. Finally, go back and read the link I gave you on keeping root. Read it until you have a clear picture as to what you need to do...
TheGhost1951 said:
As for custom roms, it is just a matter of choice. I have seen people that are happy and seen some that have had problems. As for me I prefer stock because it is made specifically for your phone. Less chance of problems. If you install a custom ROM it is usually advisable to go into recovery and factory reset. That is the wiping that is talked about. Finally, go back and read the link I gave you on keeping root. Read it until you have a clear picture as to what you need to do...
Click to expand...
Click to collapse
Thank you for your time @TheGhost1951
pronegate said:
Thank you for your time @TheGhost1951
Click to expand...
Click to collapse
You are most welcome. Like I said, staying with stock roms are more trouble free. They are made for your phone. Custom roms are ok for the most part, but I have seen too many in the forums trying to run a custom ROM and having too many problems or it doesn't have everything the stock ROM has to begin with. On the OnePlus 9 Pro, there is one more little nugget I can offer the will give you full root that Magisk is short on. Once you are rooted with Magisk, send me a PM and I will clue you in on it....
Oh, by the way, you need to disable driver signing on windows PC from this link https://www.techpout.com/disable-driver-signature-enforcement/ and then search for and install latest OnePlus and Qualcomm USB drivers and install them. This way you can connect your phone to PC in ADB, Fastboot and EDL modes for maintenance tasks!
TheGhost1951 said:
You are most welcome. Like I said, staying with stock roms are more trouble free. They are made for your phone. Custom roms are ok for the most part, but I have seen too many in the forums trying to run a custom ROM and having too many problems or it doesn't have everything the stock ROM has to begin with. On the OnePlus 9 Pro, there is one more little nugget I can offer the will give you full root that Magisk is short on. Once you are rooted with Magisk, send me a PM and I will clue you in on it....
Click to expand...
Click to collapse
I INSTALLED THE DRIVERS AS GIVEN IN YOUR GUIDE
I WAIT VERY HURRY FOR THE ARRIVAL OF MY ONEPLUS 9 PRO. I WILL UPDATE YOU AS SOON AS I HAVE NEWS
I would recommend first testing Oxygen OS software, I thinks it is not necessary for most users to tinker with custom roms.
In some time you will discover if your needs are covered with official soft or not, I know Oxygen Os is not what it used to be, it is nor good nor bad, it just was so much better before merging with Oppo because it had its own dev team and they actually did care about users, now they pretend to but ignore important matters, just answer silly questions in their forums but always abstract and tasteless...
You can always root your phone and stay in Oxygen Os but with benefits of magisk, you can tinker with it staying in Oxygen OS, but beware, you need to dome some certain things in order to "trick" some sensitive apps to root, like banking, when it detects your phone is rooted some functions may not work for "safety reasons", read magisk tutorial and enable saferynet, magisk hide deny list and you will be good to go, pretty easy for certainly experienced user, if not feel free to ask, we all will be happy to help!
pronegate said:
You are phenomenal, I am reading the best guide indicated above and it is perfect and very clear in its explanation. I have only three questions:
To possibly send it to assistance, would it be enough to just lock the bootloader and flash the original boot?
Is it essential to have twrp recovery?
What bekup operation should I do to avoid stumbling into some errors ( ex. EFS IMEI)?
Thank you for your time.
Click to expand...
Click to collapse
When you have your phone in edl and recognized by the msm tool, you can press F8 and choose partitions to back up. Take a backup of modemst1/2, efs/persist and while you're in there, grab boot_a so you can inject magisk into that boot image for root.
After you select the partitions you want, press read back and they will be saved to C:\ - with the partitions backed up, even if you do manage to break something the msm tool can't fix, you'll have the originals to put back in place.
The password is oneplus, one word all lowercase.
I don't use twrp anymore but that's your choice. I also stay on oos11. Some stay on 11, some go to 13, some go custom rom. It just depends on what you want and need from your phone. For now, we have the last OnePlus phone with real custom rom support as the newer OnePlus phones don't have public msm tools for flashing or recovering from brick state