Greetings my friends,
my name is Braadliiah, as it goes here, and I have a few questions today, pertaining to Firmware and Software. I am pretty new to the Android Flashing process, and there are many questions swirling my head, with so much unfamiliar to me. So from the top, I recently found out that all Software, that is Roms, contain a Kernel version, and that it would be redundant to install a Kernel before software, as the software will overwrite or replace the Kernel, but that afterward may be practical to achieve performance. I also understand that both Software and Firmware are OS's, or operating systems. I have become aware, that Firmware is the OS which connects the Rom to the Hardware. And yet, what I do not understand in the fast booting world, are there distinguished niches of Custom Firmware and ROM's to seperately investigate and flash? Does one typically flash both simaltaneously with a custom ROM? As, I have a Tab 3, which I would like to modernize as much as possible, though I am not at all familiar with just how far one can customize their device, in terms of Flashing. Please get back to me, and answer my questions, and I will be so thankful that you helped this NOOB. ps. The thread is a general question, and not necessarily themed around my tablet, but I would be happy to go ask over in that section of the Forums as well! :good:
Braadleyah said:
Greetings my friends,
my name is Braadliiah, as it goes here, and I have a few questions today, pertaining to Firmware and Software. I am pretty new to the Android Flashing process, and there are many questions swirling my head, with so much unfamiliar to me. So from the top, I recently found out that all Software, that is Roms, contain a Kernel version, and that it would be redundant to install a Kernel before software, as the software will overwrite or replace the Kernel, but that afterward may be practical to achieve performance. I also understand that both Software and Firmware are OS's, or operating systems. I have become aware, that Firmware is the OS which connects the Rom to the Hardware. And yet, what I do not understand in the fast booting world, are there distinguished niches of Custom Firmware and ROM's to seperately investigate and flash? Does one typically flash both simaltaneously with a custom ROM? As, I have a Tab 3, which I would like to modernize as much as possible, though I am not at all familiar with just how far one can customize their device, in terms of Flashing. Please get back to me, and answer my questions, and I will be so thankful that you helped this NOOB. ps. The thread is a general question, and not necessarily themed around my tablet, but I would be happy to go ask over in that section of the Forums as well! :good:
Click to expand...
Click to collapse
If you have a Samsung tab 3
Start here
https://forum.xda-developers.com/galaxy-tab-3
All ROMs/kernels/firmware need to be made compatible for the device you want to install them on.
Sent from my Moto E (4) using Tapatalk
Braadleyah said:
Greetings my friends,
my name is Braadliiah, as it goes here, and I have a few questions today, pertaining to Firmware and Software. I am pretty new to the Android Flashing process, and there are many questions swirling my head, with so much unfamiliar to me. So from the top, I recently found out that all Software, that is Roms, contain a Kernel version, and that it would be redundant to install a Kernel before software, as the software will overwrite or replace the Kernel, but that afterward may be practical to achieve performance. I also understand that both Software and Firmware are OS's, or operating systems. I have become aware, that Firmware is the OS which connects the Rom to the Hardware. And yet, what I do not understand in the fast booting world, are there distinguished niches of Custom Firmware and ROM's to seperately investigate and flash? Does one typically flash both simaltaneously with a custom ROM? As, I have a Tab 3, which I would like to modernize as much as possible, though I am not at all familiar with just how far one can customize their device, in terms of Flashing. Please get back to me, and answer my questions, and I will be so thankful that you helped this NOOB. ps. The thread is a general question, and not necessarily themed around my tablet, but I would be happy to go ask over in that section of the Forums as well! :good:
Click to expand...
Click to collapse
No, you didn't quite get it right. I will explain as well as I can.
The term "firmware" is the entire software package that is installed on your device. The firmware contains multiple .img files, these .img files are flashed to different partitions on the device i.e. bootloader, modem, system, recovery, etc...
The term "ROM" refers to only the system.img, this is the OS. When you flash a ROM, the only partition being flashed is the system partition, nothing else about the "firmware" is being changed, everything else from the firmware is still there "under" the ROM or system.img.
The term "kernel" refers to a specific piece of software that connects your hardware with the OS and the rest of the software on your device. When you flash a custom ROM, typically, the kernel is packaged inside the ROM because the kernel resides in the system partition. There is no need to flash a kernel when flashing a ROM unless you just want to use a custom kernel other than the one that is packaged in your ROM, but, you would flash the "additional" kernel after you flash your ROM. There are some special cases where certain devices have to flash a custom kernel in order to root their device and then flash TWRP custom recovery and/or custom ROMs.
Typically, this is the process used to flash custom ROMs.
1) Flash TWRP custom recovery for your specific model number. (this will require an unlocked bootloader/OEM unlock before you flash TWRP)
2) Find and download a ROM for your specific model number and its appropriate Gapps package as instructed in the thread where you get the ROM, place them both on your external sdcard.
3) Boot into TWRP then flash the ROM and the Gapps. Factory reset, wipe cache and wipe dalvik cache after flashing the ROM and Gapps, then reboot into system. Let it boot, it can take up to 30 mins to boot into new system.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
No, you didn't quite get it right. I will explain as well as I can.
The term "firmware" is the entire software package that is installed on your device. The firmware contains multiple .img files, these .img files are flashed to different partitions on the device i.e. bootloader, modem, system, recovery, etc...
The term "ROM" refers to only the system.img, this is the OS. When you flash a ROM, the only partition being flashed is the system partition, nothing else about the "firmware" is being changed, everything else from the firmware is still there "under" the ROM or system.img.
The term "kernel" refers to a specific piece of software that connects your hardware with the OS and the rest of the software on your device. When you flash a custom ROM, typically, the kernel is packaged inside the ROM because the kernel resides in the system partition. There is no need to flash a kernel when flashing a ROM unless you just want to use a custom kernel other than the one that is packaged in your ROM, but, you would flash the "additional" kernel after you flash your ROM. There are some special cases where certain devices have to flash a custom kernel in order to root their device and then flash TWRP custom recovery and/or custom ROMs.
Typically, this is the process used to flash custom ROMs.
1) Flash TWRP custom recovery for your specific model number. (this will require an unlocked bootloader/OEM unlock before you flash TWRP)
2) Find and download a ROM for your specific model number and its appropriate Gapps package as instructed in the thread where you get the ROM, place them both on your external sdcard.
3) Boot into TWRP then flash the ROM and the Gapps. Factory reset, wipe cache and wipe dalvik cache after flashing the ROM and Gapps, then reboot into system. Let it boot, it can take up to 30 mins to boot into new system.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Seriously great help!:victory: I had not found anything that had spelled it out in a row, until now. The most comprehensive information that I have found on the matter, anywhere on the internet.
Related
A few questions as this is all new to me.
Do all ROMS require you to flash a new kernal?
Do you flash a kernal the same way as you flash a radio? (PD98IMG File and Hboot?)
I appreciate the input...
ROMS should and typically will come with the recommended kernel, however, some kernels do work that aren't the packaged one. Always be careful when flashing a new one (backup, backup, backup!) because sometime they don't always get along with the ROM you have running.
Also, most of them should be flashable .zips that can be ran through CWM.
At least in my experience with various kernels
Hope this helped!
Kernels are included with every rom I have ever tried, and if you want to use a different kernel than the one in the rom, you have to make sure that is compatible. A good rule of thumb is if it a sense based rom (custom user interface that comes stock on the inspire) you have to use a sense based kernel. If it is a ASOP rom (Android Open Source Project, like Cyanogenmod 7, or MUIU) you must use a ASOP kernel. They will specify in the OP. And I have never heard of flashing them through HBOOT, or FASTBOOT. In my experience it is always through CWM recovery, and you flash them just as you would a rom, theme, or anything else. Move the .zip file to the root of your SD, choose install zip from sd card, scroll down to choose zip from sdcard, then choose the file. When it is done hit back and then reboot. Easy Peezy.
Tmullins23 said:
A few questions as this is all new to me.
Do all ROMS require you to flash a new kernal?
Do you flash a kernal the same way as you flash a radio? (PD98IMG File and Hboot?)
I appreciate the input...
Click to expand...
Click to collapse
Read.
Reread.
Search.
Research.
Try.
Retry.
Then ask.
kernal == kernel
Most users will flash kernels through clockwork like a rom. I flash them through fastboot, you can fastboot flash zimage(or boot), or fastboot boot zimage , which lets you boot the kernel before actually writing it, fastboot flashing requires eng s-off, which you probably don't have or need
so i need some help in rooting my tab 7+ p6200
so basically i dont know anything about rooting and all the other stuff about android..
so can someone explain to me some guidelines about rooting
is it safe? if ever i brick my device, will there be a way to unbrick? just some questions about rooting
and please kindly explain these terms that i dont understand
1. flashing
2. CWM
3. Firmware recovery
4. kernel
5. and so many more stuff
so if someone out there who can help me.. it will be a big help..
THANKS!
theejay0625 said:
so i need some help in rooting my tab 7+ p6200
so basically i dont know anything about rooting and all the other stuff about android..
so can someone explain to me some guidelines about rooting
is it safe? if ever i brick my device, will there be a way to unbrick? just some questions about rooting
and please kindly explain these terms that i dont understand
1. flashing
2. CWM
3. Firmware recovery
4. kernel
5. and so many more stuff
so if someone out there who can help me.. it will be a big help..
THANKS!
Click to expand...
Click to collapse
I don;t have a 6200 so i don't know how to root it, it could be the same as the 6210 but I'm not sure. Look in the development section.
I can answer a couple of these other things but you could really get the answers quickly by googling them.
CWM
Clockwork Mod Recovery, a custom recovery as opposed to the stock recovery. You have to have a custom recovery installed in order to flash custom ROMs.
ROM
The operating system (OS)
Kernel
Facilitates communication between the OS and the hardware.
Flashing
A general term for installing a custom ROM, the stock firmware, a mod or an update. There are many ways of flashing and not all devices do it the same way. Samsung uses Odin and also certain files can be flashed in the stock recovery if it is unlocked. With HTC you can flash certain files directly in hboot if the device is unlocked otherwise you need a custom recovery.
Recovery
This is a software layer that you can flash to your phone that allows you to boot the phone into a utility state where you can install roms, flash things like patches or modifications, backup your rom/kernel, etc. When people refer to a nandroid backup, they are referring to a backup made here. It's a snapshot of your phone that lets you mess with things and restore back to that point in time should you screw something up. You pretty much can't brick your phone at this level - it's all just files and filesystems. You can also mount your SD card to reader mode for connection to a computer, do a factory reset of data, and a few other fun things like root your rom here. You should only root your rom if it is a stock rom that has not been rooted yet. Rooting a rooted rom will usually unroot your root so you don't have root. (copied from tspderek in the Rezound forum)
kzoodroid said:
I don;t have a 6200 so i don't know how to root it, it could be the same as the 6210 but I'm not sure. Look in the development section.
I can answer a couple of these other things but you could really get the answers quickly by googling them.
CWM
Clockwork Mod Recovery, a custom recovery as opposed to the stock recovery. You have to have a custom recovery installed in order to flash custom ROMs.
ROM
The operating system (OS)
Kernel
Facilitates communication between the OS and the hardware.
Flashing
A general term for installing a custom ROM, the stock firmware, a mod or an update. There are many ways of flashing and not all devices do it the same way. Samsung uses Odin and also certain files can be flashed in the stock recovery if it is unlocked. With HTC you can flash certain files directly in hboot if the device is unlocked otherwise you need a custom recovery.
Recovery
This is a software layer that you can flash to your phone that allows you to boot the phone into a utility state where you can install roms, flash things like patches or modifications, backup your rom/kernel, etc. When people refer to a nandroid backup, they are referring to a backup made here. It's a snapshot of your phone that lets you mess with things and restore back to that point in time should you screw something up. You pretty much can't brick your phone at this level - it's all just files and filesystems. You can also mount your SD card to reader mode for connection to a computer, do a factory reset of data, and a few other fun things like root your rom here. You should only root your rom if it is a stock rom that has not been rooted yet. Rooting a rooted rom will usually unroot your root so you don't have root. (copied from tspderek in the Rezound forum)
Click to expand...
Click to collapse
Thank you sir for your answers! really cleared a lot..
theejay0625 said:
Thank you sir for your answers! really cleared a lot..
Click to expand...
Click to collapse
I should also add that Rooting (root) is just adding the superuser binaries to the system/bin folder and nothing else. Its pretty much the same thing as an administrator in windows, it allows you access to system folders. Rooting and installing a custom recovery are not the same thing, two different animals, though some devs will included both in their method for rooting a device. I prefer to do mine separately as I don't always want to install a custom recovery.
So I Unlocked my bootloader with htcdev.com, used hasoons toolkit to get Team Win Recovery Project, Once again used hasoons tool to get superSU rooted, installed etc. I then made a backup with TWRP, wiped the phone and flashed the Xylon Rom which i downloaded from the OneXRoot website along with the google apps .zip file. I then booted into fastboot and used cmd to flash the boot.img file onto the phone. Now the phone boots into the grey xylon screen but does not get any further, just that flashing white streak that indicates "Loading". I have tried wiping and restoring to the backup i made in TWRP but then it just loades the HTC One screen over and over not booting any OS, I have also tried wiping and re installing the rom with the previous steps to no avail. How should i recover my phone to a usable state? I dont care what Rom/OS is on there i would just like to get it working again.
Any advice would be appreciated greatly.
Kind Regards, Raf.
Did you erase dalvik and cache?
Or you can do an RUU. And next time, use xda as a despot of knowledge. ROMs downloads inclusive
And next time, also post in the q&a section
Sent from my HTC One XL using XDA Premium 4 mobile app
Are you Soff?
I believe Xylon uses the 3.4 kernel which required S off and running the 3.18 RUU beforehand.
Sent from my One X using XDA Premium 4 mobile app
Raff1234 said:
So I Unlocked my bootloader with htcdev.com, used hasoons toolkit to get Team Win Recovery Project, Once again used hasoons tool to get superSU rooted, installed etc. I then made a backup with TWRP, wiped the phone and flashed the Xylon Rom which i downloaded from the OneXRoot website along with the google apps .zip file. I then booted into fastboot and used cmd to flash the boot.img file onto the phone. Now the phone boots into the grey xylon screen but does not get any further, just that flashing white streak that indicates "Loading". I have tried wiping and restoring to the backup i made in TWRP but then it just loades the HTC One screen over and over not booting any OS, I have also tried wiping and re installing the rom with the previous steps to no avail. How should i recover my phone to a usable state? I dont care what Rom/OS is on there i would just like to get it working again.
Any advice would be appreciated greatly.
Kind Regards, Raf.
Click to expand...
Click to collapse
Ok firstly I wouldn't suggest getting ROMs from anywhere except XDA. Other sites (especially OneXRoot) don't properly distinguish between phone models, put simply this leads to bricks. Secondly can you please post your bootloader details, it's pretty standard to do this when asking for help as it gives us the information we need to help you properly.
There could be a few reasons the ROM didn't boot but lets not get into that now. When you created the backup of your stock ROM which boxes did you check? You're s-on so most likely even if you checked the right boxes (system/data/boot) and then restored those partitions later your phone can't flash the boot partition in recovery which means it won't boot. I'd strongly suggest getting s-off, it has many advantages which we can get into once your phone is recovered, and at this stage there's really no reason not to have it.
The best way to recover and get your phone booting right now is just to flash a different ROM. You can download a ROM to your PC and use the mount menu in TWRP recovery to mount your sd card so you can copy it to your phone. If it's aosp just make sure you have the correct version of gapps to correspond with the Android version of the ROM (4.0/4.1/4.2/4.3/4.4). And obviously make sure you flash the boot.img via fastboot after flashing the ROM. Also make sure you perform a full wipe (cache/dalvik/system/factory reset) before flashing any ROM. Before you attempt to flash anything though I need to see your bootloader details as mentioned above, certain ROMs require certain firmware to be installed in order to work.
I mentioned before not to get ROMs from other sites, you actually don't need anything from anywhere except XDA, it literally has everything you'll ever need. The other sites generally just copy/paste from here anyway. Here is our device forum main page:
http://forum.xda-developers.com/forumdisplay.php?f=1538
Here are our two development sections:
http://forum.xda-developers.com/forumdisplay.php?f=1541 (mainly Sense ROMs)
http://forum.xda-developers.com/forumdisplay.php?f=1726 (aosp ROMs)
Here's the q&a section:
http://forum.xda-developers.com/forumdisplay.php?f=1572 (this is where your post should have been created)
Also if you click the Everything Evita link in my signature you'll find that thread extremely valuable. It contains links to basically anything and everything that's of any use.
PS. I'm reporting this thread so the mods can move it to the right section (q&a), please make sure you post in the correct section next time. Thanks!
PPS. Welcome to our forum
Sent from my Evita
timmaaa said:
Ok firstly I wouldn't suggest getting ROMs from anywhere except XDA. Other sites (especially OneXRoot) don't properly distinguish between phone models, put simply this leads to bricks. Secondly can you please post your bootloader details, it's pretty standard to do this when asking for help as it gives us the information we need to help you properly.
There could be a few reasons the ROM didn't boot but lets not get into that now. When you created the backup of your stock ROM which boxes did you check? You're s-on so most likely even if you checked the right boxes (system/data/boot) and then restored those partitions later your phone can't flash the boot partition in recovery which means it won't boot. I'd strongly suggest getting s-off, it has many advantages which we can get into once your phone is recovered, and at this stage there's really no reason not to have it.
The best way to recover and get your phone booting right now is just to flash a different ROM. You can download a ROM to your PC and use the mount menu in TWRP recovery to mount your sd card so you can copy it to your phone. If it's aosp just make sure you have the correct version of gapps to correspond with the Android version of the ROM (4.0/4.1/4.2/4.3/4.4). And obviously make sure you flash the boot.img via fastboot after flashing the ROM. Also make sure you perform a full wipe (cache/dalvik/system/factory reset) before flashing any ROM. Before you attempt to flash anything though I need to see your bootloader details as mentioned above, certain ROMs require certain firmware to be installed in order to work.
I mentioned before not to get ROMs from other sites, you actually don't need anything from anywhere except XDA, it literally has everything you'll ever need. The other sites generally just copy/paste from here anyway. Here is our device forum main page:
http://forum.xda-developers.com/forumdisplay.php?f=1538
Here are our two development sections:
http://forum.xda-developers.com/forumdisplay.php?f=1541 (mainly Sense ROMs)
http://forum.xda-developers.com/forumdisplay.php?f=1726 (aosp ROMs)
Here's the q&a section:
http://forum.xda-developers.com/forumdisplay.php?f=1572 (this is where your post should have been created)
Also if you click the Everything Evita link in my signature you'll find that thread extremely valuable. It contains links to basically anything and everything that's of any use.
PS. I'm reporting this thread so the mods can move it to the right section (q&a), please make sure you post in the correct section next time. Thanks!
PPS. Welcome to our forum
Sent from my Evita
Click to expand...
Click to collapse
Hi, thanks for the tips about Son/Off I plan on doing that later,I figured out i could put a new rom on using the mount function in TWRP, I successfully loaded cyanogen nightly onto my phone and it is working great, however i flashed the gapps aswell but when I booted my phone i had to manually install the play store, maps, and other google services. When i made a backup I believe i ticked all the correct boxes, and i always cleared the cache, etc.
Thanks for all the help so far.
Raff.
You had to install Play Store? Or you had to install apps from the Play Store? Which ROM and which gapps package did you flash?
Sent from my Evita
timmaaa said:
You had to install Play Store? Or you had to install apps from the Play Store? Which ROM and which gapps package did you flash?
Sent from my Evita
Click to expand...
Click to collapse
I installed CM10.2 Nightly (The .zip is called cm-10.2-20130821-NIGHTLY-evita) and gapps 4.3, I got these from the OneXRoot site unfortunately. I did this before I checked on the thread again and saw that these other sites were not the best/reliable things to use. I had to install the play store from my browser, I just googled play store download and installed it, then proceeded to install all my other apps.
Ahh ok, I see. As far as I know the best place to get gapps from is the goo.im gapps page. I'm not sure if they have 4.4 gapps up yet but they're fairly easy to find with Google.
Sent from my Evita
So I am new to htc and new to what to do, been on Samsung for years and htc is way different.
First, once I update firmware will it be safe to flash the roms in the android development section even if they are from July or August ?
Do the Roms include kernels or do I need to find one and flash it after I flash the rom along with gapps ? If so what kernels do you recommend and /or do you have a list of some of them ?
What is fastboot and how do I use it? I am updating the firmware through sd card method but also want to update the twrp and I heard that is done through fast boot. Does that require a computer or?
Thank you for taking the time to read my questions
thrgk said:
So I am new to htc and new to what to do, been on Samsung for years and htc is way different.
First, once I update firmware will it be safe to flash the roms in the android development section even if they are from July or August ?
Do the Roms include kernels or do I need to find one and flash it after I flash the rom along with gapps ? If so what kernels do you recommend and /or do you have a list of some of them ?
What is fastboot and how do I use it? I am updating the firmware through sd card method but also want to update the twrp and I heard that is done through fast boot. Does that require a computer or?
Thank you for taking the time to read my questions
Click to expand...
Click to collapse
First off I assume you are s-off and unlocked via firewater or sunshine.
1) this is only anectodal but I ran ViperROM 1.8 (4.4.2 based) with the 4.4.3 firmware for a few weeks without issue.
2) all Roms come with a kernel. Some are stock, some are custom but they all come with one. ASSUMING you are s-off then the packaged kernel will be flashed along with the rom. If you're looking for a custom kernel make sure you find a Sense/GPE/AOSP kernel which matches your rom type (SENSE/GPE/AOSP) and flash it AFTER flashing the rom. Flashing a rom will overwrite whatever kernel you previosly had installed with the new rom's kernel. I am currently runing ViperROM 2.5 which is a Sense ROM with the EliteLunar kernel (sense version) with no issues.
3) fastboot is an interface between a computer and your phone. I always find it alarming when people ask this question. Learn and become familiar with fastboot BEFORE YOU FLASH ANY ROMs OR ZIP FILES IN RECOVERY. I'm not being rude, I assure you this is sound advice. Many fastboot tasks can be performed with apps like flashify or by a flashable zip file which many devs are kind enough to create. However, having fastboot set up and functional (that includes knowledge of how to use it) is irreplaceable if/when things go downhill.
cntryby429 said:
First off I assume you are s-off and unlocked via firewater or sunshine.
1) this is only anectodal but I ran ViperROM 1.8 (4.4.2 based) with the 4.4.3 firmware for a few weeks without issue.
2) all Roms come with a kernel. Some are stock, some are custom but they all come with one. ASSUMING you are s-off then the packaged kernel will be flashed along with the rom. If you're looking for a custom kernel make sure you find a Sense/GPE/AOSP kernel which matches your rom type (SENSE/GPE/AOSP) and flash it AFTER flashing the rom. Flashing a rom will overwrite whatever kernel you previosly had installed with the new rom's kernel. I am currently runing ViperROM 2.5 which is a Sense ROM with the EliteLunar kernel (sense version) with no issues.
3) fastboot is an interface between a computer and your phone. I always find it alarming when people ask this question. Learn and become familiar with fastboot BEFORE YOU FLASH ANY ROMs OR ZIP FILES IN RECOVERY. I'm not being rude, I assure you this is sound advice. Many fastboot tasks can be performed with apps like flashify or by a flashable zip file which many devs are kind enough to create. However, having fastboot set up and functional (that includes knowledge of how to use it) is irreplaceable if/when things go downhill.
Click to expand...
Click to collapse
Thanks for all the info. So if I am on 4.4.3 and want to flash a 4.4.2 rom just flash the 4.4.2 firmware just to be safe before flashing the 4.4.2 rom?
Also where are the kernels located ? Are they carrier dependent as I didn't see any yet browsing but didn't look hard either.
So I can do flash boot through flashify and be ok? Now all roms and kernels are flashed through twrp tho right ?
EDIT: actually fastboot can flash rom and kernels so no real need for custom recovery other then for convenience?
Btw do you have a kernel recommendation for aosp, sense, ? I already saw your recommendation for sense above.
Thanks !!
Sent from my SM-N900V using XDA Free mobile app
I have a feeling that it's simply not necessary to downgrade your firmware in order to run a 4.4.2 rom but you should find a more reputable source than myself. I'm just trying to answer these easy questions to save time for the guys who really know what they're doing. Once you do start flashing things, always make sure 1) they are for your device (and carrier, unless unified for all carriers) and 2) the md5 of the downloaded file matches that provided by the hosting website or the OP.
I'm not a fan of flashing utilities simply because I've heard of instances where they don't work correctly. For example, I keep hearing how the TWRP manager app flashes TWRP to the system partition on Verizon devices and sends the phone into a sort of recovery loop. I would suggest gaining knowledge about the fastboot flash command "fastboot flash <partition name> <filename.extension>" and how to enter and flash within RUU mode.
My experience is that ROMS and kernels are easiest flashed through a custom recovery especially when the developer packages it with an Aroma installer script.
A few Sense/GPE custom kernels exist for verizon. There's MassStashed and Checkm8 (no longer maintained?) for 4.4.2 roms. Also, for 4.4.3 roms I only know of the EliteLunar kernel which isn't on XDA although you can find a few links to it in the forums if you search. Last I knew, there weren't any AOSP kernels which work with verizon but that might not be true anymore. The general HTC One m8 forum may have some kernels which aren't represented in the verizon-specific forum. Just make sure and find out if they're compatible with verizon devices. I'm pretty happy with sense so I haven't wondered off to AOSP like I usually do.
so do you recommend to use flashify or no?
thrgk said:
so do you recommend to use flashify or no?
Click to expand...
Click to collapse
Its the easiest way
thrgk said:
so do you recommend to use flashify or no?
Click to expand...
Click to collapse
I'm not saying you shouldn't use flashify, it's awfully convenient. Just make sure you're using it for the convenience and not because you don't know how to accomplish the same tasks in recovery/fastboot.
Usually after unlocking this is my first step but having a read through the TWRP thread and G+ its left me a little confused.
If i flash TWRP it seems like i have to make sure the boot image, the system and the vendor image all match up for the phone to boot. And monthly updates may cause TWRP issues.
Since theres a distinct lack of ROMs it looks like i will have to stay stock. Now if i update monthly do i have to reconnect to a PC and update the new monthly update with TWRP? Once ROMs do start appearing will i have to flash vendor images separately like i did on the Nexus 6P? And a final question, if want to put a custom kernel on the phone will that have to match the boot, system and vendor images for it work?
Im currently pretty happy with stock but im getting an itchy trigger finger and wanna start trying some Magisk Modules but have no means to do a backup just in case other than TiBu but even then wouldnt be able to pull the files from a bootlooping device.
TIA
yatezy said:
Usually after unlocking this is my first step but having a read through the TWRP thread and G+ its left me a little confused.
If i flash TWRP it seems like i have to make sure the boot image, the system and the vendor image all match up for the phone to boot. And monthly updates may cause TWRP issues.
Since theres a distinct lack of ROMs it looks like i will have to stay stock. Now if i update monthly do i have to reconnect to a PC and update the new monthly update with TWRP? Once ROMs do start appearing will i have to flash vendor images separately like i did on the Nexus 6P? And a final question, if want to put a custom kernel on the phone will that have to match the boot, system and vendor images for it work?
Im currently pretty happy with stock but im getting an itchy trigger finger and wanna start trying some Magisk Modules but have no means to do a backup just in case other than TiBu but even then wouldnt be able to pull the files from a bootlooping device.
TIA
Click to expand...
Click to collapse
Any time you make an update to the rom, or flash a new rom, wipe data/cache, you'll have to flash TWRP, Kernel, and Magsik at the end.
If you are staying stock, as Google pushes factory images with security updates, the easiest way and the least room for error, is to update via ADK and platform-tools using a PC and remove the -w from the flash-all script to maintain all your data, ADK will update on top of the ROM (there are plenty of guides in the guide section on how to do this). However, doing so will remove TWRP, so using ADK, you'll have to temporarily fastboot to TWRP, and install the TWRP zip, Kernel zip(optional), and Magisk zip (again, plenty of guides on how to do this). To answer your questions, NO, you don't have to flash the images separately, ADK and the flash-all script do this for you. Also, NO, you don't have to ensure the kernel matches the images. See this guide:
https://forum.xda-developers.com/pixel-2/how-to/guide-how-to-install-google-software-t3760033
When you make a backup in TWRP, it stores the files in a location in phone storage, so if you lose TWRP, you can fastboot the TWRP img with ADK, and restore via that. As long as you don't accidently wipe storage.
Right now, you're right, there are not a lot of ROMs for our phone. Personally I daily the Aquarius OS and absolutely love it. So I'd say give that a whirl. The dev just announced that he is going to maintain support for the phone.
https://forum.xda-developers.com/pixel-2/development/rom-aquarios-8-1-0-walleye-volte-wfc-t3775295
djer34 said:
Any time you make an update to the rom, or flash a new rom, wipe data/cache, you'll have to flash TWRP, Kernel, and Magsik at the end.
If you are staying stock, as Google pushes factory images with security updates, the easiest way and the least room for error, is to update via ADK and platform-tools using a PC and remove the -w from the flash-all script to maintain all your data, ADK will update on top of the ROM (there are plenty of guides in the guide section on how to do this). However, doing so will remove TWRP, so using ADK, you'll have to temporarily fastboot to TWRP, and install the TWRP zip, Kernel zip(optional), and Magisk zip (again, plenty of guides on how to do this). To answer your questions, NO, you don't have to flash the images separately, ADK and the flash-all script do this for you. Also, NO, you don't have to ensure the kernel matches the images. See this guide:
https://forum.xda-developers.com/pixel-2/how-to/guide-how-to-install-google-software-t3760033
When you make a backup in TWRP, it stores the files in a location in phone storage, so if you lose TWRP, you can fastboot the TWRP img with ADK, and restore via that. As long as you don't accidently wipe storage.
Right now, you're right, there are not a lot of ROMs for our phone. Personally I daily the Aquarius OS and absolutely love it. So I'd say give that a whirl. The dev just announced that he is going to maintain support for the phone.
https://forum.xda-developers.com/pixel-2/development/rom-aquarios-8-1-0-walleye-volte-wfc-t3775295
Click to expand...
Click to collapse
Any particular reason? Can the XL roms be used on the Pixel?
ZeroSkylineX said:
Any particular reason? Can the XL roms be used on the Pixel?
Click to expand...
Click to collapse
I believe it is due to the ROMs use of the kernel and how it translates to the different hardware. I know you may think that the only hardware difference of the pixel 2 xl is a bigger screen, but there are several hardware differences that make the pixel 2 xl different from the pixel 2. See this thread:
https://forum.xda-developers.com/pixel-2/help/flash-google-pixel-2-xl-rom-regular-t3758985