[Q] Basic Doubts - Android Q&A, Help & Troubleshooting

Hello
Here are some basic queries that I have before I start my adventure in Android ROM flashing:
What's the difference between Baseband and Kernal?
I have a Nexus 4 & Google provides only stock ROM (and not kernel) on their official website. If I flash a 3rd party kernel how will I able to restore stock kernel? and
What are binaries?
Thanks!

ngr.hd said:
Hello
Here are some basic queries that I have before I start my adventure in Android ROM flashing:
What's the difference between Baseband and Kernal?
I have a Nexus 4 & Google provides only stock ROM (and not kernel) on their official website. If I flash a 3rd party kernel how will I able to restore stock kernel? and
What are binaries?
Thanks!
Click to expand...
Click to collapse
To answer your questions:
1. Baseband is a subset of the phones system that controls radio communications and related aspects of cellular tower communications. The Kernel is the low level layer of code that interfaces directly with the phones hardware such as sensors, processor, etc
2. Included in the stock ROM or Google Factory Image for the Nexus 4 is a kernel, the kernel is contained withing the boot.img file in the ramdisk usually in the form of a zimage file. If you flash a 3rd party kernel and you want to restore the stock kernel you will have to flash the Google Nexus 4 Factory Image to restore the stock kernel. The other method is before you flash a 3rd party kernel is to make a NANDROID backup of your phones stock ROM using either Clockworkmod Recovery or Team Win Recovery Project. Then after you flash the 3rd party kernel if you want to restore the stock kernel you can just restore your NANDROID backup of the stock ROM which will contain the stock kernel.
3. Binaries are the proprietary files that allow the phones hardware and sensors such as the touchscreen or GPS for example to function. You will only need to download these if you are building Android from source and/or making your own custom ROM. If you need to download the proprietary binaries for the Nexus 4 you can download them from here.
Let me know if you still have any questions .

shimp208 said:
To answer your questions:
1. Baseband is a subset of the phones system that controls radio communications and related aspects of cellular tower communications. The Kernel is the low level layer of code that interfaces directly with the phones hardware such as sensors, processor, etc
2. Included in the stock ROM or Google Factory Image for the Nexus 4 is a kernel, the kernel is contained withing the boot.img file in the ramdisk usually in the form of a zimage file. If you flash a 3rd party kernel and you want to restore the stock kernel you will have to flash the Google Nexus 4 Factory Image to restore the stock kernel. The other method is before you flash a 3rd party kernel is to make a NANDROID backup of your phones stock ROM using either Clockworkmod Recovery or Team Win Recovery Project. Then after you flash the 3rd party kernel if you want to restore the stock kernel you can just restore your NANDROID backup of the stock ROM which will contain the stock kernel.
3. Binaries are the proprietary files that allow the phones hardware and sensors such as the touchscreen or GPS for example to function. You will only need to download these if you are building Android from source and/or making your own custom ROM. If you need to download the proprietary binaries for the Nexus 4 you can download them from here.
Let me know if you still have any questions .
Click to expand...
Click to collapse
Thanks a million for the follow up.
A few more specific questions:
1. By saying Baseband (used in Android terminology) and Radio (used in WinMo terminology) mean the same thing, right? So, can we say, flashing 3rd party basebands can improve cellular connectivity?
2. [In relation to your 2nd answer]
A. So, we can also extract zimage and flash it solely without the need of flashing the whole stock ROM, just like we flash a 3rd party kernel?
B. Is NANDROID really that reliable, as in, it's just like making an .iso of a DVD, and any malwares already present in your DVD would also get backed up?
3. I have seen many kernel threads in which OP mentions CWM and non-CWM variants. Saying so, does he means to say that the kernel comes with CWM built in, right? If this is true, no dev has not integrated TWRP right into their kernel. So, devs prefer CWM over TWRP? And
4. CWM has an app in the Play Store and I'm sure it's not that recovery mod. So what's that? How is it different from the flashable mod and the Touch version?
Lastly, a humble request, there can be more queries as I dive more deep into Android Dev., please do answer them.
Thanks

ngr.hd said:
Thanks a million for the follow up.
A few more specific questions:
1. By saying Baseband (used in Android terminology) and Radio (used in WinMo terminology) mean the same thing, right? So, can we say, flashing 3rd party basebands can improve cellular connectivity?
2. [In relation to your 2nd answer]
A. So, we can also extract zimage and flash it solely without the need of flashing the whole stock ROM, just like we flash a 3rd party kernel?
B. Is NANDROID really that reliable, as in, it's just like making an .iso of a DVD, and any malwares already present in your DVD would also get backed up?
3. I have seen many kernel threads in which OP mentions CWM and non-CWM variants. Saying so, does he means to say that the kernel comes with CWM built in, right? If this is true, no dev has not integrated TWRP right into their kernel. So, devs prefer CWM over TWRP? And
4. CWM has an app in the Play Store and I'm sure it's not that recovery mod. So what's that? How is it different from the flashable mod and the Touch version?
Thanks
Click to expand...
Click to collapse
To answer a few more of your questions :
1. Yes you can flash different basebands (Used pretty much interchangeably with radio) often referred to as modems to improve cellular connectivity.
2. A. You can in theory extract the zimage and bundle it with a ramdisk and boot the system from that or flash that using the command syntax in fastboot:
Code:
boot <kernel> [ <ramdisk> ]
flash:raw boot <kernel> [ <ramdisk> ]
I have never done it this way, the safer easier way is to flash the stock boot.img file that contains the stock kernel. For example:
Code:
fastboot flash boot boot.img
2. B. NANDROID is very reliable, it is the go to standard for completely backing up an Android using a custom recovery. In a sense it is like making an ISO disk on windows, as you mentioned since it backs up the whole system anything good or bad will be included in the backup. NANDROID also has advanced options to only restore part of your backup I.E only restore the boot.img or system.img file. So say you wanted to restore the stock kernel you could go into recovery mode and restore only the stock boot.img (Containing the stock kernel) file without having to restore your entire backup.
3. Kernels do not come with CWMR built in (Except on some older Sony devices and other exceptions to this rule) the recovery partition that contains CWMR or TWRP is separate from the boot.img partition where the kernel is stored. Developers don't necessarily prefer CWMR over TWRP for the most part they are completely compatible with each other it's more of a personnel preference on the user's part.
4. I believe you are talking about ROM Manager (Correct me if you are talking about a different app), ROM Manger is outdated and should not be used to flash CWMR on most modern devices as it can brick the device rather then installing the custom recovery image. I would recommend not using ROM Manager to try and flash anything to your device.

Related

[To Kernel Devs]Custom kernel|Zimage/boot.img issues at stock ROMs with stock kernel

I noticed for myself with custom ROMs there is no problem to flash a kernel zip
with Zimage or boot.img inside via recovery.Tried all available kernels and all works.
But if I do a restore to my rooted and S-Off stock ROM with stock kernel,
nothing works.First I flashed kernel zip with Zimage,then I got
Code:
Flashing New boot.img ...
assert failed: write_raw_image ("/tmp/newboot.img". "boot")
(Status 7)
Installation aborted
After this,I tried to flash a kernel zip with boot.img inside.This works,but
phone stuck at HTC splash image.
Also,after flashed the kernel zip with boot.img inside,the kernel zips with
Zimage inside works too,but also stucks at HTC splash image.
Phone details:
EVO 3D GSM, rooted by:
HBOOT 1.49.1107
revolutionary s-off
CWM 5.0.2.0
Any answers/solutions for this from the devs,why custom kernels don`t
work with rooted/S-Off stock ROM and stock kernel?
This should go to Q&A Section...
Stock ROM's have secured Boot Images, custom ROM Dev's unsecure the Boot Image to allow Root ADB commands.
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums
Moving to Q&A
harpss1ngh said:
This should go to Q&A Section...
Stock ROM's have secured Boot Images, custom ROM Dev's unsecure the Boot Image to allow Root ADB commands.
Click to expand...
Click to collapse
So no solution to get a custom kernel working on rooted/S-Off stock ROM
with stock kernel?
harpss1ngh said:
This should go to Q&A Section...
Stock ROM's have secured Boot Images, custom ROM Dev's unsecure the Boot Image to allow Root ADB commands.
Click to expand...
Click to collapse
I could be wrong, but as far as I know this is partly true, although I might have misread.
I agree, completely 100% stock kernels from the manufacturer have secured kernels (boot images).
Ganii said:
So no solution to get a custom kernel working on rooted/S-Off stock ROM
with stock kernel?
Click to expand...
Click to collapse
The first 256 bytes of the kernel/boot.img are the signature/encryption on 100% stock kernels for this device. Since the first 256 bytes are encrypted, the standard Anykernel (zImage in .zip file with dd, etc.) method does not work. It will successfully dump the kernel from the boot partition but it will fail when parsing out the pieces due to the 256 bytes at the beginning, at least in previous/current state.
The only way I've seen to bypass this is by flashing an unsigned kernel. I've had success removing the first 256 bytes of the dumped/RUU kernel file and flashing. Once the user has an unsigned/unsecured kernel loaded in the boot partition, the Anykernel style (zImage, dd, mkbootimg.sh, etc) type kernel usually works.
These unsigned kernel files can be found in ROMs or separately in kernel .zip files, but they have to always be in the boot.img form the first time.
Some of this is my personal theory but it is based on my experiences. Welcome anybody else with experience to chime in, especially other kernel developers.
Hope my ideas make sense!
I also tried to flash boot.img,but doesn`t work.
http://forum.xda-developers.com/showpost.php?p=18686747&postcount=166
I think you might be typing the commands wrong. Have you tried
fastboot flash zimage??? Also did you unpack/unzip the .img to the correct directory??? Also did you do fastboot reboot boot loader???
Locked & Loaded
""Shooter on Deck""
Ganii said:
I also tried to flash boot.img,but doesn`t work.
http://forum.xda-developers.com/showpost.php?p=18686747&postcount=166
Click to expand...
Click to collapse
If the kernel is compiled and verifed working properly, flashing the boot.img should work as it completely overwrites the stock kernel image.
In comparison to the Anykernel method, where they dump the stock signed kernel and attempt to split out the ramdisk, cmdline and base, which will fail due to the 256 byte signature at the front of the kernel.
As a side note, I'm fairly certain it would be simple to modify the current tools, somebody might have already, to ignore the first 256 bytes of the kernel partition, and then use the rest of the image to split out the correct information. On a mass scale, the only hard part would be determining which kernels had 256 bytes of encryption/signed or which don't. The easiest solution would be to provide a flag to pass to the binary which splits out the imagine ... probably getting off topic.
Hope the extra details help clarify the process as far as I understand it!
Whats the fastest kernel out for the EXT3? And how about EXT4?

[Q] Kernel Update Possible Questions

I been searching around all over the place and I am just hitting my head against the wall. Any help would be appreciated.
This is my setup: hboot 1.5 S-ON, I have unlocked using the HTC method. I have Revolutionary CWM recovery installed.
I am looking to update the Kernel and Radio/PRI of the phone to the latest versions. (I haven't done it in a very long time.)
By what I read, since I have hboot 1.5 updating the kernel seems close to impossible. I did read that I may have to go to a Stock Rom and update via sprint OTA to get the latest updates then unlock again? That doesnt sound right to me.
I am all types of confused. Part of this was started because I wanted to try the MeanROM (link:http://forum.xda-developers.com/showthread.php?t=1466362) and also update my phone. Everything I try to do fails or I cant do because of the 1.5 or the S-ON.
Hopefully i am making some sense. I dont know what I have to do to get the latest kernel or if it even is possible.
If you are rooted already the only thing you need to do is install flash GUI app (you can get it in the market) and flash the kernel (boot.img) file before you flash the ROM and you should be OK
There is a myth that if your on 1.5 s-on your doomed, that's not true. It does mean that you'll need an extra step to do things but you'll be able to get things done without issues.
Sent from my Xoom using Tapatalk
megabiteg said:
If you are rooted already the only thing you need to do is install flash GUI app (you can get it in the market) and flash the kernel (boot.img) file before you flash the ROM and you should be OK
There is a myth that if your on 1.5 s-on your doomed, that's not true. It does mean that you'll need an extra step to do things but you'll be able to get things done without issues.
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Thank you for the reply, so I understand I can load that application, unzip the rom I want which will have the boot.img. Then flash that boot.img and then install that rom, is that correct? Lastly, does this also update the radio and pri?
spiderz13 said:
Thank you for the reply, so I understand I can load that application, unzip the rom I want which will have the boot.img. Then flash that boot.img and then install that rom, is that correct? Lastly, does this also update the radio and pri?
Click to expand...
Click to collapse
If your firmware is compatible with the Rom and kernel yes. If not, you will brick your phone or features will not work as they have to do. After you install flash GUI go to browse button and you will be advertised that file is too large for a kernel or recovery image, then asks if it is a valid Rom zip file. Tap yes and it will search the kernel inside the Rom. After it finishes tap flash and after reboot in recovery(you have to have recovery.img in root of your SD card), next wipe dalvik and cache, install zip and wait until the phone finishes. It is also recommended to you to make a nandroid backup before install anything.
spiderz13 said:
Thank you for the reply, so I understand I can load that application, unzip the rom I want which will have the boot.img. Then flash that boot.img and then install that rom, is that correct? Lastly, does this also update the radio and pri?
Click to expand...
Click to collapse
For the EVO 3D, much like the EVO 4G, the custom ROMs generally do not contain the radio or pri images.
There are some different reasons for this, but one of the common reasons being some users claim to experience different radio performance based on their geographic loation in relation to different versions of the radio and pri images.
luis4ever said:
If your firmware is compatible with the Rom and kernel yes. If not, you will brick your phone or features will not work as they have to do. After you install flash GUI go to browse button and you will be advertised that file is too large for a kernel or recovery image, then asks if it is a valid Rom zip file. Tap yes and it will search the kernel inside the Rom. After it finishes tap flash and after reboot in recovery(you have to have recovery.img in root of your SD card), next wipe dalvik and cache, install zip and wait until the phone finishes. It is also recommended to you to make a nandroid backup before install anything.
Click to expand...
Click to collapse
The only clarification to this post would be having recovery.img in the root of your SD card is not required for rebooting into recovery mode. In order for a custom recovery to load, when rebooting into recovery mode, the recovery.img has to have been flashed previously. Flash Image GUI can also flash the recovery.img to the recovery partition so when you reboot into recovery, the proper custom recovery loads. Most users flash custom recoveries infrequently when compared to how often they flash ROMs so the process for flashing the recovery process isn't covered as often.
In general, regarding the OP's original question of flashing the "MeanROM", the Flash Image GUI thread provides a great beginner step by step guide I wrote to help walk thru the general overview and process. I've quoted it below for easy reference.
Appreciate all the support of Flash Image GUI! I'll echo the optimism for hboot 1.5 s-on unlocked users, most everything is still possible. HTC just requires an extra few steps which can be frustrating, but once they are learned, the process is fairly smooth.
Hope the clarification helps iron out any confusion on the details!
HTC Unlock - Hboot 1.5 Users Guide for ROMs with a Kernel (boot.img file):
1) Unlock using HTC method for Hboot 1.5 users
2) Load this application, Flash Image GUI, onto the device, either through the Market or the link provided in this OP.
3) Download ROM .zip file to the sdcard on the device.
4) Open up Flash Image GUI, select Browse and select the ROM .zip file, downloaded to /sdcard in the previous step.
5) Flash Image GUI will provide a warning, reminding that the ROM .zip file will *need* to be flashed in the custom recovery afterward.
6) Flash Image GUI will index the full ROM .zip file searching for the kernel and kernel modules. Once located, the Flash Image button should be enabled.
7) Select the Flash Image button and Flash Image GUI will load the kernel modules and kernel from inside the ROM zip file.
8) Select reboot recovery.
9) Inside the custom recovery, load/flash the ROM zip file.
10) Reboot to normal Android mode and all should work including Wifi!
Click to expand...
Click to collapse

how to install custom recovery so I can install cm10.2?

as title.
prefer twrp if possible.
thank you very much
I haven't actually done this, but here are the steps as I understand them:
1) perform an adb backup -all ( in case you want to go back to stock. Easier than flashing and re-installing all your apps)
2) back up your TA partition
3) Unlock your bootloader
4) Install a kernel that contains your chosen recovery mode, twrp in this case
5) Reboot into recovery mode and install your CM ROM
There are lots of tutorials and guides here on xda. Search for your device model with twrp and kernel/cm10.2.
You can also search the CyanogenMod site, they also have guides for some devices.
Good luck.
http://wiki.cyanogenmod.org/w/Install_CM_for_pollux
I've found that link but it doesn't talk about installing recovery. After installing the kernel (in my experience with HTC One X, boot.img = kernel only), the device somehow has magically received CWM as well?
mrjayviper said:
http://wiki.cyanogenmod.org/w/Install_CM_for_pollux
I've found that link but it doesn't talk about installing recovery. After installing the kernel (in my experience with HTC One X, boot.img = kernel only), the device somehow has magically received CWM as well?
Click to expand...
Click to collapse
You have a lot of reading to do before you're ready to potentially wreck your new tablet. One mistake or flashing the wrong ROM version and you could brick it but good. You will also lose some functionality in the proprietary apps and the OS.
On Xperia devices I believe there is no recovery partition so the recovery mod is integrated into the kernel that you need to install. Pollux_windy is the Cyanogen ROM for the wifi only version of Tab Z and the other pollux_[whatever] is for the Tab z with cell service. The kernel is a separate install that you need to do before flashing the new ROM so that you have a recovery mode to flash from.
I'm quite happy with the stock firmware so I don't plan on installing a ROM just yet. I did toy with the idea of flashing a kernel with a recovery mod but then learned that the Bravia engine and a few other features get disabled when your crypto keys get erased by unlocking the bootloader. Having a recovery mod without the need to install a ROM lost its appeal to me at that point.
This is not exactly what you are looking for but it's a place to start: http://wiki.cyanogenmod.org/w/Install_for_pollux_windy
Be careful and don't rush into this until you are 100% sure you know exactly what you are doing and what you need to accomplish your goal. Eg. If you don't back up your DRM keys before unlocking the bootloader, they are gone for good and you can never get them back. It goes without saying, if you flash a ROM and your Tab develops a problem and you can't get it back to a factory state, you'll lose warranty service.
Does the cyanogenMod kernel work with the stock rom (pollux/LTE)
(Root/Unlcked)
THX
mrjayviper said:
http://wiki.cyanogenmod.org/w/Install_CM_for_pollux
I've found that link but it doesn't talk about installing recovery. After installing the kernel (in my experience with HTC One X, boot.img = kernel only), the device somehow has magically received CWM as well?
Click to expand...
Click to collapse
I've been flashing Samsung (android) & Nexus phones over the last 3 years - but flashing the Tablet Z is quite different.
The replies here from dph3055 give very good advice - I wish I'd read something like it before I began messing with the SXTZ. I messed up straight away by unlocking my bootloader before backing up my TA partition - lost all the DRM keys :crying:

How to flash a stock image using TWRP only, not a PC

I have a Nexus 6P that has some weird issue where it is not being recognized by any PC or any USB port as a USB device. So I can't get it to work with fastboot as an adb device. It has stock android 6.0.1 on it and TWRP. This is how I got it. I think there is something wrong with the software not allowing the USB mode to work properly so I wanted to flash to another stock image. I've already downloaded the stock anglr image and uses Google Drive to transfer the files over, both the complete image and also the independent IMG files. Is it possible to use TWRP to flash the phone back to stock?
Two questions before I venture an answer -
a. When you mean flash back to stock, I am assuming you mean your TWRP stays and all you want is to flash stock android. Right?
b. Your custom recovery is TWRP right?
tropicanapure said:
Two questions before I venture an answer -
a. When you mean flash back to stock, I am assuming you mean your TWRP stays and all you want is to flash stock android. Right?
b. Your custom recovery is TWRP right?
Click to expand...
Click to collapse
a: Yes, unrooted and a different stock image to see if maybe this version on the phone is buggy with the USB connection not working.
b: Yes, TWRP 2.8.7.2
Great. Then the simple answer is yes. Subject to the fact that whatever you trying to flash is "flashable" (i.e. usable by TWRP). To be honest I have been flashing using TWRP for last 3 years and never once have I used a PC.
Slightly longer answer. To do this
a. (ALWAYS) Backup original Android install using TWRP
b. Factory reset (NOT wipe - unless you know what you are doing!)
c. Look for the Flashable ZIP containing your stock image - and flash.
and voila! You are back to stock!
Good luck!
tmar89 said:
a: Yes, unrooted and a different stock image to see if maybe this version on the phone is buggy with the USB connection not working.
b: Yes, TWRP 2.8.7.2
Click to expand...
Click to collapse
tropicanapure said:
Two questions before I venture an answer -
a. When you mean flash back to stock, I am assuming you mean your TWRP stays and all you want is to flash stock android. Right?
b. Your custom recovery is TWRP right?
Click to expand...
Click to collapse
tropicanapure said:
Great. Then the simple answer is yes. Subject to the fact that whatever you trying to flash is "flashable" (i.e. usable by TWRP). To be honest I have been flashing using TWRP for last 3 years and never once have I used a PC.
Slightly longer answer. To do this
a. (ALWAYS) Backup original Android install using TWRP
b. Factory reset (NOT wipe - unless you know what you are doing!)
c. Look for the Flashable ZIP containing your stock image - and flash.
and voila! You are back to stock!
Good luck!
Click to expand...
Click to collapse
Thanks. So if I download the stock android image from google developers page, I can copy that over to the device and use TWRP to flash it?
Actually, I've been reading that I cannot flash a factory image with recovery, only fastboot. But fastboot doesn't work for me because device won't recognize when connected with USB (trust me, I tried everything with drivers and cables, computers, etc). I think I need to find a flashable stock image for my device.
tmar89 said:
Thanks. So if I download the stock android image from google developers page, I can copy that over to the device and use TWRP to flash it?
Click to expand...
Click to collapse
No. Which is why I said - "flashable". I dont have a Nexus 6p so I dont know where you can find a TWRP flashable stock image for that device. But a quick search of your device specific sub-forum on XDA yielded this link.
The link in the first para should help you find a "flashable factory/ stock image". I would suggest you follow instructions on that post and ask further questions there as the folks in there will have the same device as you and provide better help.
Again, good luck!
Thanks, I appreciate this advice as it helps.
tmar89 said:
Thanks, I appreciate this advice as it helps.
Click to expand...
Click to collapse
No worries. Pass it on
PS: Here's another XDA thread that has a flashable version of the STOCK rom.
PPS: Found via Google search terms nexus 6p stock rom flashable

Can I flash stock miui rom with twrp?

First question is the title basically, wanna flash miui if i happen to not like PE. Can i flash it with twrp?
Second question, If I flash PE without any custom kernels. And flash miui after that. Will i have my original kernel? Or does flashing custom roms change to a custom kernel?
Sorry a bit new to this. Thanks for your time.
1 - Yes, you can flash miui with twrp, just use rom recovery package.
2 - Any rom zip package comes bundled with the kernel. flashing will install the kernel contained in the package.
csleo17 said:
1 - Yes, you can flash miui with twrp, just use rom recovery package.
2 - Any rom zip package comes bundled with the kernel. flashing will install the kernel contained in the package.
Click to expand...
Click to collapse
What is rom recovery package?
thanks for your time man
ParsaMrrelax said:
What is rom recovery package?
thanks for your time man
Click to expand...
Click to collapse
Android devices predominantly followed by following partitions!
/system
/boot
/recovery
/vendor
/storage
/persist
/ta (in xperia)
/overlay (optional)
now RECOVERY (beside parition name) refers to a operating system DESIGNED ONLY to change size of these partitions (ADVANCE) and basic need to spread out(FLASH) operating system according to command by package in certain partitions. -- TWRP is one OUTSTANDING Recovery project over the years. back in old days Philztouch recovery was also popular for Xperia models-
the term "rom recovery package" means, READ ONLY MEMORY ( a android operating system File ) Designed for RECOVERY TO READ and spead the data in /system + / boot & /data partitions for your Poco (or any android based) for boot in to android operating system.
MIUI mainly releases TWO filetypes of SAME ROMS , for example miui10.3.6 has
1. RECOVERY ROM (1.6gb) (to be flashed by TWRP
2. FASTBOOT ROM (2.8gb) which can be flashed by FLASHER running on WINDOWS based System (some times iMac too)
3. Android devices uses many types of processor, SNAPDRAGON processors are famouss (poco uses Snapdragon or SD845) hence Two type of Flashers can be USED to FLASH POCO, 1 MI FLASH (RECOMENDED) (supports Two Mods, on fastboot rom, fastboot & EDL) or QUALCOMS QLOADER flasher (ADVANCE and NOT RECOMENDED)
coming back to twrp,
all custom roms are designed keeping in mind that RECOVERY (such as TWRP) will be FLASHING it on ANDROID DEVICE. so the sequence of flashing such roms are like
1. flashing vendor firmware , from a. vendor firmware , download from https://mirror.akhilnarang.me/MIUI/b...r-firmware.zip
b. flashing pixel experience ROM ( you should also try Crdroid and Havoc)
c. flashing google apps from openapps.org (take arm64>android9.0>MICRO package and hit download) 250+mb filesize
d. (optional) optimus drunk kernel (check development forum for post)
e. flashing magisk18.3.zip (if you want your Device to WAKEUP ROOTED)
now answering you question
1. YES YOU CAN TOGGLE BETWEEN MIUI AND CUSTOM ROMS, but don't make it habit! there is always chance for you to BRICK your device. also you will loose all your data if MIUI uses Encryption method which TWRP cannot READ to operate /data partition. then you must RE FORMATE /data partition via twrp in order to make it accesable for custom rom(s)
2.ANY TIME WHEN TWRP FLASH ANY ROM, MIUI OR ANY CUSTOM ROM, THE OLD KERNEL IS OBSOLETE AND NEW ONE IS PLACED thats why you need to flash magisk everytime you clean flash any rom in order to get root access
please do ask if you need any clarification
might be a old thread.
but i installed a custom rom on my moms phone but i thinking going back to stock. the custom rom is old and has scroll problems...
but i see stable miui has no updates. but can i flash official miui rom from twrp over the custom lingeos rom?
or is it better to update her phone to a more recent custom rom.
either way she will lose her data. plus camera has bugs but i never had the time with work and she working to put it back in a mint working state. cause the scrolling being broking is fuking stupid
tought about miui stable. just to flash it true trwp.
or update it to a more recent custom rom.

Categories

Resources