Related
After flashing a kernel, they say to do a full wipe (and then reinstall the ROM?).
My question is whether after the wipe, can I restore a nandroid backup? Setting it up from scratch and just the way I like it is quite tedious if I were to do this each time, plus download the apps from the market etc. My arc is my main phone so I don't have the luxury of flashing ROMs and kernels all the time.
Do let me know if that's possible. If not, can you tell me how you guys do it?
My arc is running Stock ICS 4.0.4 with an unlocked bootloader.
I believe you got it all wrong.... you need to do a full wipe before installing a new ROM (to make sure it works properly and nothing is left from the old one).... not a kernel... You can flash kernels as often you want without any wipes. Just dont forget the WIFI-modules (only of needed by ther kernel).
xtacy! said:
My question is whether after the wipe, can I restore a nandroid backup?
Click to expand...
Click to collapse
Just think about it, it would be pointles to delete evrething and then restore it back..
P.S.: sh*t I pushed the wrong button and thanked you instead of quote....
yea..there is no point restoring the nand after flashing a kernel...full wipe and fresh installing rom is highly recommended..
Best way is to tryout a kernel..if everything is well and good then better stick to it.
afterall wat do u look in a kernel? OC,UV, good battery life and smooth UI..once you attain all these then stick to it..
btw i have tried many kernels this month without doing a full wipe..i never faced any problem as such..i just uninstall all OC, UV apps just to be safe
Thanks for the replies guys. And an extra thanks to Antochrist for his mistake. LOL!
Another reason for my question was because one of the kernel developers said to do a clean install.
Let's say I flash a kernel with additional wifi modules. Suppose I want to get back to stock kernel and its wifi modules, do I just flash the stock kernel or do I need to do anything extra to fix the wifi?
xtacy! said:
Let's say I flash a kernel with additional wifi modules. Suppose I want to get back to stock kernel and its wifi modules, do I just flash the stock kernel or do I need to do anything extra to fix the wifi?
Click to expand...
Click to collapse
yea u just need to flash the stock kernel as wifi modules are included in the stock kernel itself
xtacy! said:
Thanks for the replies guys. And an extra thanks to Antochrist for his mistake. LOL!
Another reason for my question was because one of the kernel developers said to do a clean install.
Let's say I flash a kernel with additional wifi modules. Suppose I want to get back to stock kernel and its wifi modules, do I just flash the stock kernel or do I need to do anything extra to fix the wifi?
Click to expand...
Click to collapse
I think clean install only needed for new rom, not new kernel
cmiiw
Sent from mobile
Similar issues
Happy new years everyone!
I am pretty new to using custom ROMS and kernels and have made a standard noob mistake
which was forgetting to back up all the original software (ROM, kernel, etc). I realized this quite later
and though I have found the original ROM for my GT-P5110 I seem to have trouble finding the stock Kernel
(the one it had when it left the factory; 4.0.4) I did a search and have found my search-fu to be weak.
Can anyone help me find the stock rom for the GT-P5110 (Galaxy note 2 10.1)?
And one more thing, should I get the Galaxy S3 LTE vs. LG Optimus G vs.your opinion?
(I am in South Korea btw) Is Korean version is any different or any harder to root or to
flash a custom ROM, anyone have any experience?
Many thanks
But I did not get the Right Answer...
arpith.fbi said:
yea u just need to flash the stock kernel as wifi modules are included in the stock kernel itself
Click to expand...
Click to collapse
Thanks for the info that WIFI modules are included in the kernel and no extra additions need to be made.. I Don't know abt it ..
NOW assuming u now a lot abt Linux/Android could you please answer this for me..
- Does Restoring NANDROID
- Restore 'Stock Kernel' along with 'RIL file', RAMDISK - INIT### n stuff
Which Hyperion users need to fiddle with..
But kernel and ram disk are stored in the boot partition so does NANDROID back that up too ?
and Can you help me with RIL file related info..
Thanks
NANDroid only backs up ROM. It doesn't back up kernel. Kernel is always flashed externally, it's the same with all Android devices.
僕のLT18iから送られてきた
I am an OG Evo owners and just getting back into flashing and trying out different roms. Back when I would flash custom roms, the tool of choice for backing up data+apps was Titanium backup. Has this changed?
I am on Blazer 1.7 right now and would like to update to 1.9 but I don't want to lose all of my data and apps. He says something in his OP about there being an update.zip, but I don't see it anywhere. Is this pretty common for devs to include a update.zip that lets you seamlessly upgrade from version to version of the same custom rom?
With the OG Evo, you couldn't back up data from a ASOP rom and then flash over to a sense ROM and restore your data or else it would crap out on you. Is there anything that I need to watch out for in that respect?
So I have two questions
1. How do I retain my apps and information going from the same custom rom to a updated version of that custom rom?
2. How do I retain my apps and information going form one custom rom to another custom rom?
Thanks!
Hi and welcome to this awesome phone! XD
I too came from an OG EVO, was sporting Warm twopointthree back then...
jhoffy22 said:
Back when I would flash custom roms, the tool of choice for backing up data+apps was Titanium backup. Has this changed?
Click to expand...
Click to collapse
Nope, it is still the tool of choice and everything from the OG EVO applies. It's a universal tool and works the same across devices. Do a user app+data only back up from OG EVO and restore it on the SG3. Do not restore system apps from OG EVO to SG3, these are the apps that are red or yellow font in TB.
jhoffy22 said:
I am on Blazer 1.7 right now and would like to update to 1.9 but I don't want to lose all of my data and apps. He says something in his OP about there being an update.zip, but I don't see it anywhere. Is this pretty common for devs to include a update.zip that lets you seamlessly upgrade from version to version of the same custom rom?
Click to expand...
Click to collapse
I'm not on Blazer and haven't used it, maybe some one will come in and comment on this. You could try another ROM, like FreeGS3. It has a lot of positive reviews and is up-to-date with the latest OTA. The link is in my sig... You should have TWRP recovery for this ROM to install properly, the link is also in my sig.
jhoffy22 said:
With the OG Evo, you couldn't back up data from a ASOP rom and then flash over to a sense ROM and restore your data or else it would crap out on you. Is there anything that I need to watch out for in that respect?
Click to expand...
Click to collapse
The same applies with the SG3, this is because the system apps on the stock or TW SG3 are well Touch Wiz System.UI and framework and applying these to a AOSP ROM that has completly different System.UI and framwork will bring a lot of force closes and ultimatly an unresponsive device. You can restore user apps without issues.
jhoffy22 said:
1. How do I retain my apps and information going from the same custom rom to a updated version of that custom rom?
Click to expand...
Click to collapse
There are a few options for this, you can "dirty flash" the ROM and you'll have the same setup and data as before the flash. This is just flash the ROM and only wipe cache and dalvik, but you should only do this when it's an incremental update from the same ROM. Although some say it is best to do a complete wipe and then flash the ROM even if it's incremental update of the same... One thing reported from some doing a dirty flash is poor battery performance or randon force closes, only way to fix this is a clean flash. Also, the dev (usually) let's the user base know if there was a change to the System.UI or framework and needing a clean install of the incremental update. This was also the case back in the OG EVO. Try the different options and see what's best for you.
jhoffy22 said:
2. How do I retain my apps and information going form one custom rom to another custom rom?
Click to expand...
Click to collapse
Answered above, same applies.
Also, for clean install do the following, Wipe Factory Reset>Wipe System>Wipe Cache>Wipe Dalvik and then flash the new ROM.
dragon_rckr said:
Hi and welcome to this awesome phone! XD
I too came from an OG EVO, was sporting Warm twopointthree back then...
Nope, it is still the tool of choice and everything from the OG EVO applies. It's a universal tool and works the same across devices. Do a user app+data only back up from OG EVO and restore it on the SG3. Do not restore system apps from OG EVO to SG3, these are the apps that are red or yellow font in TB.
I'm not on Blazer and haven't used it, maybe some one will come in and comment on this. You could try another ROM, like FreeGS3. It has a lot of positive reviews and is up-to-date with the latest OTA. The link is in my sig... You should have TWRP recovery for this ROM to install properly, the link is also in my sig.
The same applies with the SG3, this is because the system apps on the stock or TW SG3 are well Touch Wiz System.UI and framework and applying these to a AOSP ROM that has completly different System.UI and framwork will bring a lot of force closes and ultimatly an unresponsive device. You can restore user apps without issues.
There are a few options for this, you can "dirty flash" the ROM and you'll have the same setup and data as before the flash. This is just flash the ROM and only wipe cache and dalvik, but you should only do this when it's an incremental update from the same ROM. Although some say it is best to do a complete wipe and then flash the ROM even if it's incremental update of the same... One thing reported from some doing a dirty flash is poor battery performance or randon force closes, only way to fix this is a clean flash. Also, the dev (usually) let's the user base know if there was a change to the System.UI or framework and needing a clean install of the incremental update. This was also the case back in the OG EVO. Try the different options and see what's best for you.
Answered above, same applies.
Also, for clean install do the following, Wipe Factory Reset>Wipe System>Wipe Cache>Wipe Dalvik and then flash the new ROM.
Click to expand...
Click to collapse
Thank you for the awesome reply! Blazer 1.7 is awesome, smooth as butter and no problems with battery life whatsoever. I'm really enjoying it. The only reason I want to update is because of the pop up that I am getting about the new software update being available. I don't want to accidentally install the update and then brick my phone.
jhoffy22 said:
Thank you for the awesome reply! Blazer 1.7 is awesome, smooth as butter and no problems with battery life whatsoever. I'm really enjoying it. The only reason I want to update is because of the pop up that I am getting about the new software update being available. I don't want to accidentally install the update and then brick my phone.
Click to expand...
Click to collapse
Gotcha! No worries here, just hit apply update and it'll reboot and "try" to install but it will fail since you have a custom bootloader. It won't brick the phone at all, unlike ye ol EVO :/
The thing that has bricked many SG3 has been flashing a ROM the international version... stay away from those.
BTW if you think Blazer is smooth, try FreeGS3, you'll be blown away haha
There's also a JB leak from Sprint in the dev section, I'm trying that tonight.
dragon_rckr said:
Gotcha! No worries here, just hit apply update and it'll reboot and "try" to install but it will fail since you have a custom bootloader. It won't brick the phone at all, unlike ye ol EVO :/
The thing that has bricked many SG3 has been flashing a ROM the international version... stay away from those.
BTW if you think Blazer is smooth, try FreeGS3, you'll be blown away haha
There's also a JB leak from Sprint in the dev section, I'm trying that tonight.
Click to expand...
Click to collapse
Haha I will be careful to avoid that then.
I have one more question. When doing a restore with Titanium backup coming from one rom to another (just switched from Blazer to FGS3), what restore option do I choose? I chose to "restore missing apps with data"
jhoffy22 said:
Haha I will be careful to avoid that then.
I have one more question. When doing a restore with Titanium backup coming from one rom to another (just switched from Blazer to FGS3), what restore option do I choose? I chose to "restore missing apps with data"
Click to expand...
Click to collapse
Yup, just that and select which user apps you want to restore and let go through the process.
dragon_rckr said:
Yup, just that and select which user apps you want to restore and let go through the process.
Click to expand...
Click to collapse
Sweet, thanks a lot!
jhoffy22 said:
Sweet, thanks a lot!
Click to expand...
Click to collapse
No prob
You can also restore some system apps, but be careful with which ones. I usually restore dialer storage, msg storage, wifi settings and account sync settings.
I just got my replacement HTC One V CDMA unlocked and rooted. I want to overclock and understand I need a custom ROM to do so. My first HTC One V I bricked trying to flash rhythmicrom. I unlocked, rooted, backed up using TWM. Each time I tried to flash the new ROM it would get stuck on the HTC screen with the red writing talking about developmental purposes, etc. Each time it would hang on that screen I would simply do a recovery to the back up file and everything would go back to normal. The last time I tried to flash it hung up, and when I tried to go back it would not go back. I am not sure why Rhythmicrom would not work. Is there another one I should try? Does it matter if my HTC one V is a newer version, etc? I just need a basic ROM with the ability to overclock. MMS is a necessity and the camera would be nice. Thanks for any help you can give me.
Did you make sure to flash the appropriate kernel via fastboot aftter flashing the ROM, because if not that could be the cause of your phone failing to boot. As for ROM's, well I guess that depends on whether you have a PrimoU or a PrimoC, I personally use SHPONGLE for the PrimoU, but I can't comment on the PrimoC as I do not own one
zzjoshzz said:
Did you make sure to flash the appropriate kernel via fastboot aftter flashing the ROM, because if not that could be the cause of your phone failing to boot. As for ROM's, well I guess that depends on whether you have a PrimoU or a PrimoC, I personally use SHPONGLE for the PrimoU, but I can't comment on the PrimoC as I do not own one
Click to expand...
Click to collapse
Thank you for the reply. Yes I used the kernel (boot.img) that was included with the rythmicrom rom. I have a PrimoC. I was reading and see that my problem might be caused due to maybe having a newer version of the phone and the hboot or radio might be different?
tackj said:
Thank you for the reply. Yes I used the kernel (boot.img) that was included with the rythmicrom rom. I have a PrimoC. I was reading and see that my problem might be caused due to maybe having a newer version of the phone and the hboot or radio might be different?
Click to expand...
Click to collapse
Hey, so some kernels support the newer radio and some do not. If you are on the newer radio: Baseband version 1.00.00.0928 (check in about phone in settings) then you have to use a kernel that supports the OTA, such as for sense use the FOTA kernel posted under the cdma development thread, for android 4.1 use the kernel I made that can be found in the slim bean rom thread by curtis, and for 4.2 rythmic rom's kernel should work just fine. If not, try the codefirex kernel from simon's rom (original dev. thread) but you'll lose functionality of the camera as it is an ion kernel.
I hope this helps, quote me in the reply if you have more questions, otherwise I may forget to check back here.
why u no flash kernel omg! just read the trouble shooting section
lilrob1213 said:
Hey, so some kernels support the newer radio and some do not. If you are on the newer radio: Baseband version 1.00.00.0928 (check in about phone in settings) then you have to use a kernel that supports the OTA, such as for sense use the FOTA kernel posted under the cdma development thread, for android 4.1 use the kernel I made that can be found in the slim bean rom thread by curtis, and for 4.2 rythmic rom's kernel should work just fine. If not, try the codefirex kernel from simon's rom (original dev. thread) but you'll lose functionality of the camera as it is an ion kernel.
I hope this helps, quote me in the reply if you have more questions, otherwise I may forget to check back here.
Click to expand...
Click to collapse
Thank you very much for you help. I checked my radio and it is 1.00.00.0928. Is this the reason why the rythmicrom kernel would not work? So you recommend using the FOTA kernel with which ROM? Sorry for the dumb questions. I tried my best to read everything I could before asking for help. I just don't want to brick my replacement phone. I am not sue they will be as understanding as they were the first time.
tackj said:
Thank you very much for you help. I checked my radio and it is 1.00.00.0928. Is this the reason why the rythmicrom kernel would not work? So you recommend using the FOTA kernel with which ROM? Sorry for the dumb questions. I tried my best to read everything I could before asking for help. I just don't want to brick my replacement phone. I am not sue they will be as understanding as they were the first time.
Click to expand...
Click to collapse
well it shouldn't have been the reason because if you type "fastboot flash boot boot.img" in command line for the kernel you want to flash then it should flash correctly and rythmic rom's kernel has supported new radio since the beginning pretty much. Unless you have a really old version or something. The FOTA kernel is for sense roms or cm9 (which is based on android 4.0 ics). I really like and very much recommend MyOneV rom that curiousnoob has ported under the cdma dev. thread. It's fast, smooth, and has the least amount of lag compared to any other sense rom that I've tried. It's my daily and go-to rom!
You shouldn't brick your phone as long as you fastboot flash the correct kernel (for primoc/cdma), even if you end up in a bootloop you can hold power button and get back to bootloader to flash a new rom or restore a backup
lilrob1213 said:
well it shouldn't have been the reason because if you type "fastboot flash boot boot.img" in command line for the kernel you want to flash then it should flash correctly and rythmic rom's kernel has supported new radio since the beginning pretty much. Unless you have a really old version or something. The FOTA kernel is for sense roms or cm9 (which is based on android 4.0 ics). I really like and very much recommend MyOneV rom that curiousnoob has ported under the cdma dev. thread. It's fast, smooth, and has the least amount of lag compared to any other sense rom that I've tried. It's my daily and go-to rom!
You shouldn't brick your phone as long as you fastboot flash the correct kernel (for primoc/cdma), even if you end up in a bootloop you can hold power button and get back to bootloader to flash a new rom or restore a backup
Click to expand...
Click to collapse
Thanks for the information. Is it necessary to wipe the sd card before installing the new ROM? This is how I bricked my last one. I read somewhere that I needed to do a full wipe including the sd card. The sd card is where my recovery was and when I wiped it I didn't have anything to recover to. I tried RUU and that did not work.
So I think I might do this kernel [KERNEL][VM/PRIMOC][ICS:Sense] FOTA-Compatible Sick Kernel
With this ROM: myOneV 9.5+CDMA
Does this look ok?
tackj said:
Thanks for the information. Is it necessary to wipe the sd card before installing the new ROM? This is how I bricked my last one. I read somewhere that I needed to do a full wipe including the sd card. The sd card is where my recovery was and when I wiped it I didn't have anything to recover to. I tried RUU and that did not work.
So I think I might do this kernel [KERNEL][VM/PRIMOC][ICS:Sense] FOTA-Compatible Sick Kernel
With this ROM: myOneV 9.5+CDMA
Does this look ok?
Click to expand...
Click to collapse
It isn't necessary to wipe sd card, although if you get any weird bugs that no one else has reported (read threads) then yeah, I'd wipe sd card. In fact, I do actually wipe everything (except sd-ext) from twrp 2.6.1. But before I wipe I mount usb to my computer and copy over the twrp folder with my backup and any pictures I wanna save. Then, wipe everything including sd card (although not necessary I like to do it) and then mount usb again and copy the files I need (rom.zip and twrp folder). But to do a full wipe technically it's just wiping data, cache, dalvik cache, and system.
RUU will not work if you are on the newer hboot version (forgot the number but it's around here which is new vs old).
that combination works for me (I'm on new hboot and radio) so should work fine! btw that's the rom and kernel I mentioned earlier idk if you caught that or not
lilrob1213 said:
It isn't necessary to wipe sd card, although if you get any weird bugs that no one else has reported (read threads) then yeah, I'd wipe sd card. In fact, I do actually wipe everything (except sd-ext) from twrp 2.6.1. But before I wipe I mount usb to my computer and copy over the twrp folder with my backup and any pictures I wanna save. Then, wipe everything including sd card (although not necessary I like to do it) and then mount usb again and copy the files I need (rom.zip and twrp folder). But to do a full wipe technically it's just wiping data, cache, dalvik cache, and system.
RUU will not work if you are on the newer hboot version (forgot the number but it's around here which is new vs old).
that combination works for me (I'm on new hboot and radio) so should work fine! btw that's the rom and kernel I mentioned earlier idk if you caught that or not
Click to expand...
Click to collapse
Cool thank you. Yes I did catch that I just wanted to confirm that was the one you are talking about. I went to download that rom and it said it was not available any longer.
tackj said:
Cool thank you. Yes I did catch that I just wanted to confirm that was the one you are talking about. I went to download that rom and it said it was not available any longer.
Click to expand...
Click to collapse
oh right... curiousnoob is revamping it to make it better, you can either be patient or I can upload you an older version give me a second
here: https://docs.google.com/file/d/0By_o-NyPojUXNTdna3p5bGdSNVU/edit?usp=sharing it's from 09/02/2013 but it's the best I think so far... next update should be awesome-er! haha
lilrob1213 said:
oh right... curiousnoob is revamping it to make it better, you can either be patient or I can upload you an older version give me a second
here: https://docs.google.com/file/d/0By_o-NyPojUXNTdna3p5bGdSNVU/edit?usp=sharing it's from 09/02/2013 but it's the best I think so far... next update should be awesome-er! haha
Click to expand...
Click to collapse
Thank you for all of your help! Will this ROM work with the stock kernel? Just wondering. I would like to overclock so i will be flashing the sick kernel, but I was just curious. Thank you again.
tackj said:
Thank you for all of your help! Will this ROM work with the stock kernel? Just wondering. I would like to overclock so i will be flashing the sick kernel, but I was just curious. Thank you again.
Click to expand...
Click to collapse
kinda... but with stock kernel wifi didn't work... however fota kernel works so great with overclock that there's no need for stock kernel and it's not a problem, I'm happy to help
lilrob1213 said:
kinda... but with stock kernel wifi didn't work... however fota kernel works so great with overclock that there's no need for stock kernel and it's not a problem, I'm happy to help
Click to expand...
Click to collapse
Thank you for the link! I downloaded and got the ROM working now with the stock kernel. Now I am going to try and flash the sick kernel. Just to confirm, this is the one I need:
http://forum.xda-developers.com/showthread.php?t=2261819
I am going to put it in my fastboot folder, rename it boot.img and then flash it using cmd.
Does this sound right?
Also, just an FYI...I received a PM from Curiousn00b stating that the newest version is now available.
tackj said:
Thank you for the link! I downloaded and got the ROM working now with the stock kernel. Now I am going to try and flash the sick kernel. Just to confirm, this is the one I need:
http://forum.xda-developers.com/showthread.php?t=2261819
I am going to put it in my fastboot folder, rename it boot.img and then flash it using cmd.
Does this sound right?
Also, just an FYI...I received a PM from Curiousn00b stating that the newest version is now available.
Click to expand...
Click to collapse
Yup sounds flawless to me! Enjoy it! and thanks for the headsup I will probably download that and test myself
lilrob1213 said:
Yup sounds flawless to me! Enjoy it! and thanks for the headsup I will probably download that and test myself
Click to expand...
Click to collapse
Hey, I got the kernel to work! Now my wifi is operational. Now that the new version is available, do I dare ask how to go about updating? Is it just the same process? Thanks!
tackj said:
Hey, I got the kernel to work! Now my wifi is operational. Now that the new version is available, do I dare ask how to go about updating? Is it just the same process? Thanks!
Click to expand...
Click to collapse
You flashed the fota sick kernel? Well, you can update by just wiping dalvik and cache and flashing the new rom, but it's a full wipe (same process as before) is always recommended over the previous "update"
lilrob1213 said:
You flashed the fota sick kernel? Well, you can update by just wiping dalvik and cache and flashing the new rom, but it's a full wipe (same process as before) is always recommended over the previous "update"
Click to expand...
Click to collapse
Yes, I was able to flash the FOTA sick kernel. I have it set at 1.709 GHz max and 245 mhz min. with the I/O scheduler on noop. I put the governor on "performance" and did a benchmark test with antutu. My score was 7069 which didn't look all that great compared to the others. Does this sound about right? I was also only getting 6.2 fps on the 3D testing.
tackj said:
Yes, I was able to flash the FOTA sick kernel. I have it set at 1.709 GHz max and 245 mhz min. with the I/O scheduler on noop. I put the governor on "performance" and did a benchmark test with antutu. My score was 7069 which didn't look all that great compared to the others. Does this sound about right? I was also only getting 6.2 fps on the 3D testing.
Click to expand...
Click to collapse
hmmm... I have no idea... I've never really messed with benchmarks before, don't think they matter much, I'm happy just having a lag-free phone btw for typical use, I'm sure you know, performance gov. will kill your battery fairly quickly, so I usually use [email protected]$$v2 gov. or lionheart, but usually the first
lilrob1213 said:
hmmm... I have no idea... I've never really messed with benchmarks before, don't think they matter much, I'm happy just having a lag-free phone btw for typical use, I'm sure you know, performance gov. will kill your battery fairly quickly, so I usually use [email protected]$$v2 gov. or lionheart, but usually the first
Click to expand...
Click to collapse
You are right, the phone is more snappy for sure. What GHz do you use for everyday? I was using [email protected]$$v2 gov but put it on performance just during the test. I also have buzzlauncher as my launcher so I am not sure if that is taking away from the performance, but it looks nice. I am just happy that it is working, so again thanks for your help.
Hey, folks.
I have a two day old Pixel 2 XL. I have unlocked it and an running the stock ROM (latest factory), but I have rooted it by installing Magisk (flashed a zip file).
I still have the stock recovery, I flashed by booting to twrp via fastboot command.
I keep getting an error that Magisk Manager Keeps closing.
Is there a known issue that I just have not read about yet?
I only rooted so I could use AdAway, but when I tried to check a few settings in Magisk today, this kept coming up.
I'll reboot and see if I can get into it again, but if there is a known "proper" fix, I'd appreciate some gentle assistance.
Thanks
Seems to open up fine after a reboot and passes safety net check.
No clue what causes the issue, but I can live with an occasional reboot.
myk.robinson said:
Seems to open up fine after a reboot and passes safety net check.
No clue what causes the issue, but I can live with an occasional reboot.
Click to expand...
Click to collapse
Are you on stock or custom kernel?
Badger50 said:
Are you on stock or custom kernel?
Click to expand...
Click to collapse
Stock. You and Az Biker helped me with unlocking, and I not flashed the Magisk zip. Still stock kernel and stock bootloader, and I flashed the latest factory image.
myk.robinson said:
Stock. You and Az Biker helped me with unlocking, and I not flashed the Magisk zip. Still stock kernel and stock bootloader, and I flashed the latest factory image.
Click to expand...
Click to collapse
Maybe flash a custom kernel, followed immediately by flashing magisk ???
Badger50 said:
Maybe flash a custom kernel, followed immediately by flashing magisk
Click to expand...
Click to collapse
I mistyped my response, i ONLY flashed the Magisk zip file.
Same prescription, though? Try a different kernel with Magisk again, after taking a backup, of course?
myk.robinson said:
I mistyped my response, i ONLY flashed the Magisk zip file.
Same prescription, though? Try a different kernel with Magisk again, after taking a backup, of course?
Click to expand...
Click to collapse
While backups are always good practice, you'd be fine without one for flashing a kernel+magisk. Unless of course you want to, which is never a bad thing
Badger50 said:
While backups are always good practice, you'd be fine without one for flashing a kernel+magisk. Unless of course you want to, which is never a bad thing
Click to expand...
Click to collapse
You probably already know what my next question will be
I'll read some kernel threads and check out the pros and cons. My main concern is that I retain the features and stability of the stock kernel. Just have bad memories of certain kernels on my Moto G4 Plus breaking the fingerprint reader and messing up the screen saturation
Thanks
myk.robinson said:
You probably already know what my next question will be
I'll read some kernel threads and check out the pros and cons. My main concern is that I retain the features and stability of the stock kernel. Just have bad memories of certain kernels on my Moto G4 Plus breaking the fingerprint reader and messing up the screen saturation
Thanks
Click to expand...
Click to collapse
The past is the past my friend. I will unequivocally just say that whatever custom kernel you choose, they are all extremely good and reliable. I haven't run the stock kernel since the custom ones came out. My battery life is excellent, and functionality is just perfect. Not to mention, that if you use the EXKM app, there's a few extra perks that you may like. If you want the latest Linux changes and updates go with Flash kernel. If you want to stay closer to stock Linux/Google code, then go with Snoke or Ex kernel. I'm not going to try and convince you on what to do, I'm just relaying personal experience my friend ??
Hi,
I have a Pixel 3xl rooted and running with Havoc Rom.
if I want to switch from a custom rom to another custom rom, how can I do that?
Do I have to install stock rom and erase data before the new custom rom or can I just install the new custom rom above to previous one?
Thank you.
oceliome said:
Hi,
I have a Pixel 3xl rooted and running with Havoc Rom.
if I want to switch from a custom rom to another custom rom, how can I do that?
Do I have to install stock rom and erase data before the new custom rom or can I just install the new custom rom above to previous one?
Thank you.
Click to expand...
Click to collapse
Install stock factory image to both slots with -w intact in the flash-all batch, and then start with the instructions of the ROM you want to install.
sliding_billy said:
Install stock factory image to both slots with -w intact in the flash-all batch, and then start with the instructions of the ROM you want to install.
Click to expand...
Click to collapse
I would personally back up anything I wanted then flash the new rom boot.img and try to dirty flash it. If it got messed up then I would do as above. I am still crazy though and 9/10 you need a wipe when switching.
wangdaning said:
I would personally back up anything I wanted then flash the new rom boot.img and try to dirty flash it. If it got messed up then I would do as above. I am still crazy though and 9/10 you need a wipe when switching.
Click to expand...
Click to collapse
I get it. I hate clean flashing more than anything, but pretty much no custom ROMs allow for dirty installs except for over the same ROM these days. Even over the same doesn't always work well especially if the build was dirty. Not worth the extra effort trying to figure out and fix what broke on a cross-rom dirty flash, IMO.
sliding_billy said:
I get it. I hate clean flashing more than anything, but pretty much no custom ROMs allow for dirty installs except for over the same ROM these days. Even over the same doesn't always work well especially if the build was dirty. Not worth the extra effort trying to figure out and fix what broke on a cross-rom dirty flash, IMO.
Click to expand...
Click to collapse
True, but lots of people have extra time nowadays. I would say just always make sure you back up somehow before any switch. Be ready to wipe your device clean.
Thank you for your replys.
I'm not an english speaking personn, so if i understand:
The normal way to switch two customs roms is to "transit" by the stock rom and clear all data and then install rhe new custom rom.
The other way, would be dirty flash the new custom rom above the previous custom rom (with loss data possible so a bachup is needed).