Related
I have a kernel that i found that i want to flash. When you flash a kernel, does it replace a flashed ROM or do they combine?
Also, when you flash anything (ROM or kernel) does it replace the stock ROM or does it take a spot next to it? Can you make several spots so there can be more than one ROM? What is wiping out a ROM? If you leave a ROM, can you save your setting so when you go back you don't have to start over again? Can you back up contacts,messages, and apps from stock ROM and extract the data to the new ROM?
I AM CONFUSED
pranker98 said:
I have a kernel that i found that i want to flash. When you flash a kernel, does it replace a flashed ROM or do they combine?
Also, when you flash anything (ROM or kernel) does it replace the stock ROM or does it take a spot next to it? Can you make several spots so there can be more than one ROM? What is wiping out a ROM? If you leave a ROM, can you save your setting so when you go back you don't have to start over again? Can you back up contacts,messages, and apps from stock ROM and extract the data to the new ROM?
I AM CONFUSED
Click to expand...
Click to collapse
1. No, they "combine"
2. It replaces it when you flash
3. Yes, but its more complicated than just flashing multiple roms. There is an app but it doesn't support Sensation.
4. Wiping a ROM is just that, wiping your phone of the ROM along with all your app,data and anything else on the phone(SD card not effected).
5. Umm. I don't understand your question completely but yes flashing a new ROM over an old ROM will preserve your data but you can flash a different rom and expect it to work. For example ARHD-->ARHD(updated) is OK but ARHD --> Insertcoin wont work.
6. Yes, its called titanium backup. Look it up.
thanks. after reading this, I stumbled on radios. what are radios?
pranker98 said:
thanks. after reading this, I stumbled on radios. what are radios?
Click to expand...
Click to collapse
Radio is what gives your phone signal. which version works best for you will depend on your location and carrier so you will just have to experiment. its generally advised that you flash the latest recommended version stated on the rom your using
pranker98 said:
I have a kernel that i found that i want to flash. When you flash a kernel, does it replace a flashed ROM or do they combine?
Also, when you flash anything (ROM or kernel) does it replace the stock ROM or does it take a spot next to it? Can you make several spots so there can be more than one ROM? What is wiping out a ROM? If you leave a ROM, can you save your setting so when you go back you don't have to start over again? Can you back up contacts,messages, and apps from stock ROM and extract the data to the new ROM?
I AM CONFUSED
Click to expand...
Click to collapse
kevinliu2336 said:
1. No, they "combine"
2. It replaces it when you flash
3. Yes, but its more complicated than just flashing multiple roms. There is an app but it doesn't support Sensation.
4. Wiping a ROM is just that, wiping your phone of the ROM along with all your app,data and anything else on the phone(SD card not effected).
5. Umm. I don't understand your question completely but yes flashing a new ROM over an old ROM will preserve your data but you can flash a different rom and expect it to work. For example ARHD-->ARHD(updated) is OK but ARHD --> Insertcoin wont work.
6. Yes, its called titanium backup. Look it up.
Click to expand...
Click to collapse
The only thing I'd add is that for:
o If you leave a ROM, can you save your setting so when you go back you don't have to start over again?
You can do a Nandroid backup from CWM recovery, it takes a snapshot of the ROM, Kernel, Data,.. You can then play with other ROMs. Then at a later date restore the Nandroid backup from CWM and you're back at the earlier ROM.
It's extremely important that when you play with ROMs you backup a working version. It saves a lot of swearing when you lose a nice working system unintentionally. It's happened a couple of times to me and it's a bugger.
Hello,
I recently installed custom Jellywiz rom on my Verizon S3.
My question is if I have new custom rom versions or if I want to switch to a different rom, do I always have to go back to stock firmware and then install the custom rom or can I directly flash over my existing custom rom ?
tomalrocks said:
Hello,
I recently installed custom Jellywiz rom on my Verizon S3.
My question is if I have new custom rom versions or if I want to switch to a different rom, do I always have to go back to stock firmware and then install the custom rom or can I directly flash over my existing custom rom ?
Click to expand...
Click to collapse
New custom rom versions: Unless otherwise stated by the developer you can go ahead and just dirty flash right on top of the current one, but if you experience issues then i'd wipe data and cache and do a clean install.
Switching to a different rom: ALWAYS do a clean install (wipe data, and cache), i can't urge how important that is, while you may not have any issues whatsoever, you definitely could encounter issues because each developer may have different changes, and you don't want stuff to mix and match.
Neverendingxsin said:
New custom rom versions: Unless otherwise stated by the developer you can go ahead and just dirty flash right on top of the current one, but if you experience issues then i'd wipe data and cache and do a clean install.
Switching to a different rom: ALWAYS do a clean install (wipe data, and cache), i can't urge how important that is, while you may not have any issues whatsoever, you definitely could encounter issues because each developer may have different changes, and you don't want stuff to mix and match.
Click to expand...
Click to collapse
Thanks. So just flashing over existing rom after wiping data and cache will work. Will do that. I do not want to go back to stock rom always as that is time consuming.
tomalrocks said:
Thanks. So just flashing over existing rom after wiping data and cache will work. Will do that. I do not want to go back to stock rom always as that is time consuming.
Click to expand...
Click to collapse
Yeah this is fine. The way I've always done it. Also in clockwork, go to advanced >wipe dalvic
Neverendingxsin said:
New custom rom versions: Unless otherwise stated by the developer you can go ahead and just dirty flash right on top of the current one, but if you experience issues then i'd wipe data and cache and do a clean install.
Switching to a different rom: ALWAYS do a clean install (wipe data, and cache), i can't urge how important that is, while you may not have any issues whatsoever, you definitely could encounter issues because each developer may have different changes, and you don't want stuff to mix and match.
Click to expand...
Click to collapse
aypeeootrek said:
Yeah this is fine. The way I've always done it. Also in clockwork, go to advanced >wipe dalvic
Click to expand...
Click to collapse
Thanks :good:
Do you know whether I am use CWMod recovery to flash stock roms or do i need to use ODIN for that?
tomalrocks said:
Thanks :good:
Do you know whether I am use CWMod recovery to flash stock roms or do i need to use ODIN for that?
Click to expand...
Click to collapse
You can flash stock roms in CWM, but be careful if they don't include a kernel. If you go from AOSP to Stock, you might get a boot loop unless you also flash a stock compatible kernel, and vice versa. Boot loop is easily recoverable of course, but it will scare new users
thnx123
yhnk you for
Zalithian said:
You can flash stock roms in CWM, but be careful if they don't include a kernel. If you go from AOSP to Stock, you might get a boot loop unless you also flash a stock compatible kernel, and vice versa. Boot loop is easily recoverable of course, but it will scare new users
Click to expand...
Click to collapse
hehehe I already got that scare after flashing new rom and it was taking a long time to boot during first boot.
Thanks anyways
iv'e been dirty flashing new updates to the rom iam using (euphoria) ever since i first got it, and was wondering if i should do a clean install once every few versions.
1. if i dont have any bugs, any point in doing a clean install?
2. does the device get slower after a few dirty flash upgrades?
thanks =P
DjDafiDak said:
iv'e been dirty flashing new updates to the rom iam using (euphoria) ever since i first got it, and was wondering if i should do a clean install once every few versions.
1. if i dont have any bugs, any point in doing a clean install?
2. does the device get slower after a few dirty flash upgrades?
thanks =P
Click to expand...
Click to collapse
No to both questions. I dirty flash every cm12 build and I can't attribute slowness or bugs specifically to a dirty flash.
Euphoria isn't cm but its still android and the same basic logic would apply. I would clean flash when switching Roms, not necessarily when updating to a later version of a ROM.
Hello,
I am running PixysOS rom on my Honor 6X (BLN-AL20) since some months and I am actually satisfied of the stability and usability of the Rom.
Actually I can't convince the device to use the installed as card to store pictures, videos etc.
The SD card is recognised and listed under memory but the system is not using it.
Is there any workaround to fix this problem?
Thanks,
Andrea.
Sent from my BLN-AL20 using Tapatalk
Anybody out there?
Sent from my BLN-AL20 using Tapatalk
Sephiroth79 said:
Anybody out there?
Sent from my BLN-AL20 using Tapatalk
Click to expand...
Click to collapse
for me my internal storage is not detected. only sd card is main storage. seems like its a bug and never gonna fixed. there is no perfect android 9 os out there. so better go to emui 8 and use cyclox kernel.
Sephiroth79 said:
Hello,
I am running PixysOS rom on my Honor 6X (BLN-AL20) since some months and I am actually satisfied of the stability and usability of the Rom.
Actually I can't convince the device to use the installed as card to store pictures, videos etc.
The SD card is recognised and listed under memory but the system is not using it.
Is there any workaround to fix this problem?
Thanks,
Andrea.
Click to expand...
Click to collapse
By what I read in the thread of DotOS, that's a bug that should had be fixed in latest builds... Are you using latest version or not?
Anyway every Pie ROM/GSI I tried seems to read microSD, eject it and re-read once again immediately after booting to OS, on every single boot. Then, there are systems that keep reading the microSD (as AEX, Descendant...) and allows modifications, reading files, basically everything you should be able to do with a microSD, and systems that just keep it ejected (like DotOS did on old builds). Saw other users reporting that on the thread. Look for "microSD" in DotOS thread to read latest comments about, there you could find a solution. By how things sound at the moment, my only advice is to move on another system.
Thanks for your reply. Could you suggest me a proper and stable rom?
Sephiroth79 said:
Thanks for your reply. Could you suggest me a proper and stable rom?
Click to expand...
Click to collapse
Nothing hard to do man. We use to thank others with the appropriate button, for next times.
Anyway since that we're not talking 'bout different devices but we share the same phone, i feel to strongly recommend ya the Descendant GSI project by Dil3mm4.. It's a fork of Phh AOSP project but with sone very good extras. I never used a system smooth like this one, really impressive. It has a decent amount of customizations options (not at levels like RROS in example, but too much is too much IMHO), great battery management, fluid transitions and great compatibility with Huawei devices (it's a GSI, but the dev has a P8 Lite at the moment, so he knows how to make things working on Huawei).
Give it a shot, you can always go back to stock with HuRUpdater in just 5 minutes. And in case you'd like to try more, remember to take a look into Treble section here on XDA. Every arm64 a-only GSI is good to be flashed on our device, but before flashing just look if other users owning a Huawei device have already tried it or not. I say this simply because many GSIs are actually not working thanks to our vendor compatibility, so make things without hurry and nothing can go wrong
Used appropriate "thanks button" this time...eheh
Any tutorial on how to install the Descendant GSI rom starting from PixysOs with Askuccio's TWRP?
Sephiroth79 said:
Used appropriate "thanks button" this time...eheh
Any tutorial on how to install the Descendant GSI rom starting from PixysOs with Askuccio's TWRP?
Click to expand...
Click to collapse
Well there isn't a dedicated tutorial for every ROM/GSI you're starting from, overall because a clean flash is strongly recommended (especially when you switch from a ROM to a GSI) - you can dirty flash Descendant updates or other GSIs based on phhusson trees without problems, but in this case you've already modified your device kernel and other stuff with a custom ROM, so it's better to start from scratch in way to avoid useless wastes of time running to repairs with hurry.
The faster and safest way to do this is:
1) restore stock OS with HuRUpdater and let it boot (i saw that you already own Askuccio's TWRP, i always had to use Elemental TWRP from KingOfMezi in way to use HuRU without errors, but apart this Askuccio's TWRP works for flashing everything you'd need);
2) following steps listed in Descendant OP, flash the system image through fastboot or through TWRP, then reboot to TWRP once again and wipe ONLY /cache and /dalvikART partitions;
3) factory reset through stock recovery and let the system boot (yeah, you'll have to reflash stock recovery once again before reflashing TWRP - again.
4) flash all the rest you'd like to flash (GApps, Magisk, ecc.)
By default, /data partition remains encrypted after performing factory reset with stock recovery, and so with TWRP you won't be able to perform full backups, but you can also choose to run with /data decrypted. The method isn't supported by the developer, but works like a charm (personally tested about 3 versions of the GSI ago, worked). You just have to flash "disable dm verity" script during the process, but you can know more by reading about it here.
Happy flashing
RedSkull23 said:
Well there isn't a dedicated tutorial for every ROM/GSI you're starting from, overall because a clean flash is strongly recommended (especially when you switch from a ROM to a GSI) - you can dirty flash Descendant updates or other GSIs based on phhusson trees without problems, but in this case you've already modified your device kernel and other stuff with a custom ROM, so it's better to start from scratch in way to avoid useless wastes of time running to repairs with hurry.
The faster and safest way to do this is:
1) restore stock OS with HuRUpdater and let it boot (i saw that you already own Askuccio's TWRP, i always had to use Elemental TWRP from KingOfMezi in way to use HuRU without errors, but apart this Askuccio's TWRP works for flashing everything you'd need);
2) following steps listed in Descendant OP, flash the system image through fastboot or through TWRP, then reboot to TWRP once again and wipe ONLY /cache and /dalvikART partitions;
3) factory reset through stock recovery and let the system boot (yeah, you'll have to reflash stock recovery once again before reflashing TWRP - again.
4) flash all the rest you'd like to flash (GApps, Magisk, ecc.)
By default, /data partition remains encrypted after performing factory reset with stock recovery, and so with TWRP you won't be able to perform full backups, but you can also choose to run with /data decrypted. The method isn't supported by the developer, but works like a charm (personally tested about 3 versions of the GSI ago, worked). You just have to flash "disable dm verity" script during the process, but you can know more by reading about it here.
Happy flashing
Click to expand...
Click to collapse
Point 1: I have to download stock fw using Huawei firmware finder and I have to use Askuccio's TWRP to flash HuRupdater on the device. Do I have to choose a custom recovery or I have to let HuRupdater flash stock recovery too?
Point 2: you are saying I have to wipe cache/dalviw partitions using TWRP so I have to flash TWRP after flashing and booting stock fw?
Sephiroth79 said:
Point 1: I have to download stock fw using Huawei firmware finder and I have to use Askuccio's TWRP to flash HuRupdater on the device. Do I have to choose a custom recovery or I have to let HuRupdater flash stock recovery too?
Point 2: you are saying I have to wipe cache/dalviw partitions using TWRP so I have to flash TWRP after flashing and booting stock fw?
Click to expand...
Click to collapse
To me flashing HuRU with Askuccio TWRP never worked, as said above, so i'd suggest you to look for ElementalTWRP in way to have a custom recovery that can flash HuRU with no problems. Secondarily, in way to avoid confusion, just start from stock and do a fastboot flash of Descendant, reboot to OS and let it boot. Once set, flash TWRP and flash GApps, then wipe just /cache and /dalvik and reboot one last time. Then you can do anything you want.
RedSkull23 said:
To me flashing HuRU with Askuccio TWRP never worked, as said above, so i'd suggest you to look for ElementalTWRP in way to have a custom recovery that can flash HuRU with no problems. Secondarily, in way to avoid confusion, just start from stock and do a fastboot flash of Descendant, reboot to OS and let it boot. Once set, flash TWRP and flash GApps, then wipe just /cache and /dalvik and reboot one last time. Then you can do anything you want.
Click to expand...
Click to collapse
Ok, I'll put elemental TWRP recovery in the same directory in order to let HuRU flash it together with the stock firmware.
Edit: can't find elemental twrp download link
Sephiroth79 said:
Ok, I'll put elemental TWRP recovery in the same directory in order to let HuRU flash it together with the stock firmware.
Edit: can't find elemental twrp download link
Click to expand...
Click to collapse
Good, i usually do that later just in case the system prompts to factory reset before booting, but it's up to you. Here's the link anyway https://mega.nz/#!a81EDZAR!2-9yPFh3reghkGcfSl3nRIJhHGkP8fqDsgUG66ewjkk
Using fw finder I downloaded the fw named: BLN-AL30C00B541 (8.0.0.541) FULLOTA-MF 2018.12.27
Clicking on download give me some choices:
- update.zip (1.74 GB)
- BLN-Al20_all_cn/update_full_BLN-AL20_all_cn.zip (643 MB)
Already downloaded both of them and can't find any of the files required from HurUpdater to run. Do I have to use an extractor?
EditOne: used Huawei Update Extractor gives an error on the update.app extracted from the update.zip archive and works on the same file extracted from BLN-Al20_all_cn/update_full_BLN-AL20_all_cn.zip
Edit2: just realized I don't need to extract anything but still can't find update_data_public and update_all_hw files
That is because it's Chinese build and as you just noticed some update packages are assembled in a slightly different manner, so some package misses one if not two useful zips. Would you mind to switch to India variant? Nothing changes in performance nor in features, plus if you'd only use the firmware as a base to get to other ROMs/GSIs, it really doesn't matter (but i can offer better assistance since that i'm more experienced with India variant other than China). FYI in this thread https://forum.xda-developers.com/honor-6x/how-to/french-language-t3938592/ i've already guided an user to obtain India variant, but it's really simple:
in TEAM MT site (google for "team mt online firmware database", the first result you get is what you need), look for build "BLN-L22HNC675CUSTC675D1B510" - you'll obtain 4 results. Download the package dated 2018.07.19, it is the better one. From here you just have to follow instructions in HwOTA thread, renaming the three packages as suggested in OP and choosing to debrand during the process to BLN-L22 region/variant (don't remember if it happens anyway since that the firmware is India variant but it's a thing that doesn't give hassles).
I have successfully installed LineageOS what feels like a hundred times now. I followed every single piece of advice and best practice. In total frustration I gave up LineageOS and followed every single step for an OctaviOS installation. I even flashed the newest Global stock firmware successfully, just to follow every recommended step.
I boot into OctaviOS, after successful installation and...
Wi-Fi still won't turn on.
I am completely out of ideas and I have no idea what to do about it. Going back to stock and using this in production is not an option.
I have installed TWRP 3.4.0-0 By mahajant99 and every ROM flash and partition wipe, worked as expected and I never encountered a serious error. All flashes went fine and everything was done exactly step by step, as the guides recommended. Still, no Wi-Fi.
What can I do to fix this?
P.S.: Wi-Fi works through stock ROM. So no hardware issue.
Please, before flashing a custom ROM, make sure you installed the MIUI 12.0.4.0 Firmware Only because it is an essential to make WIFI and Calling Works...
Please be guided here on the tutorial created by @ManoloRey... It works smooth, no problems...
Better use OrangeFox as a recovery image...
How to install Poco x3 ROM
Clean Flash 1. Flash recovery (latest Ofox 11.0 Beta - "Download" ). This is very important. 2. Reboot to recovery. 3. Dont wipe or format anything.. 4. Flash any custom roms you want. e.g. PE+. etc. Wait until complete. 5. Format data -> Yes. 6. Reboot to System. 7. Complete initial setup. 8...
telegra.ph
Please, before flashing a custom ROM, make sure you installed the MIUI 12.0.4.0 Firmware Only because it is an essential to make WIFI and Calling Works...
Please be guided here on the tutorial created by @ManoloRey... It works smooth, no problems...
Better use OrangeFox as a recovery image...
https://telegra.ph/How-to-http://http://
Disregard this...
yan2xme said:
Please, before flashing a custom ROM, make sure you installed the MIUI 12.0.4.0 Firmware Only because it is an essential to make WIFI and Calling Works...
Please be guided here on the tutorial created by @ManoloRey... It works smooth, no problems...
Better use OrangeFox as a recovery image...
How to install Poco x3 ROM
Clean Flash 1. Flash recovery (latest Ofox 11.0 Beta - "Download" ). This is very important. 2. Reboot to recovery. 3. Dont wipe or format anything.. 4. Flash any custom roms you want. e.g. PE+. etc. Wait until complete. 5. Format data -> Yes. 6. Reboot to System. 7. Complete initial setup. 8...
telegra.ph
Click to expand...
Click to collapse
To test, I followed the guide and installed this precise FW+Vendor image. Doing this, I cannot boot into a custom ROM (e.g. OctaviOS), at all. I repeated this test several times, to exclude possible installation errors. I did CLEAN flashes and installations. Still, it makes things worse. As already said, I can't even boot into the ROM.
Aki-to said:
To test, I followed the guide and installed this precise FW+Vendor image. Doing this, I cannot boot into a custom ROM (e.g. OctaviOS), at all. I repeated this test several times, to exclude possible installation errors. I did CLEAN flashes and installations. Still, it makes things worse. As already said, I can't even boot into the ROM.
Click to expand...
Click to collapse
Better just try another rom... They are all still AOSP and uses same kernel as NitrogenOS does. Better use EvoX or RR or Pixel Experience ROM... They're more polished and expect to also have great updates... Just wait for more stable Android 11 Custom Roms or just contact the OP of the OctaviOS for surya...
@id.agung17
yan2xme said:
Better just try another rom... They are all still AOSP and uses same kernel as NitrogenOS does.
Click to expand...
Click to collapse
Even IF another ROM would work -- why doesn't this ROM work on my phone? What's so special about my phone? I have a plain brandnew POCO X3 NFC, like most others here. So why wouldn't it work? Does the firmware version have anything to do with it?
Every guide I read, explicitly recommends version "12.0.3". However, the newest version is already at version "12.0.4". Maybe this is causing the issue?
Aki-to said:
Even IF another ROM would work -- why doesn't this ROM work on my phone? What's so special about my phone? I have a plain brandnew POCO X3 NFC, like most others here. So why wouldn't it work? Does the firmware version have anything to do with it?
Every guide I read, explicitly recommends version "12.0.3". However, the newest version is already at version "12.0.4". Maybe this is causing the issue?
Click to expand...
Click to collapse
Maybe, have you also even tried installing fw 12.0.3? Because at the meantime, no developer has compiled the public kernel of poco x3 to their respective roms... They still use the kernel from the first miui rom... Idk whats really the difference on stock kernel vs the released kernel for surya because in my situation, everything works fine on installing roms. My device is surya, 6/64gb... Plain just like you... Idk why devs couldnt even fix this thing...
Sorry bro I can't help you with this, I'm just an ordinary kid being new to this stuff and have a little experience with this (still I'm a fast learner) because I only experienced much more customization on the Poco X3 than even other phones I have owned previously. I did not also learned coding (i was a rookie HTML coder past years but i forgotten it) like Java or scripts on Linux to compile and make compatible custom roms for phones... Peace
I did the following steps:
Flash "surya_global_images_V12.0.3.0.QJGMIXM_20200925.0000.00_10.0_global" with "MiFlash 2020.3.14.0".
Wipe Cache, Dalvik.
Flash "OctaviOS-v1.2-surya-20201109-2033-VANILLA-Official".
Flash "Magisk-v21.1".
Format Data.
Reboot into System.
Wi-Fi is working!!
Now only NikGapps is missing, but that is just booting into Recovery, flashing and booting back into System, so no problem here, anymore.
Thank you, @yan2xme! You say you are noob, but you had the right guess, too! Anyway, thanks for your help, I appreciate it!
P.S.: Boot-up is additionally much faster, smoother and without SystemUI crash on startup. This 12.0.4 firmware really sucks!
Aki-to said:
I did the following steps:
Flash "surya_global_images_V12.0.3.0.QJGMIXM_20200925.0000.00_10.0_global" with "MiFlash 2020.3.14.0".
Wipe Cache, Dalvik.
Flash "OctaviOS-v1.2-surya-20201109-2033-VANILLA-Official".
Flash "Magisk-v21.1".
Format Data.
Reboot into System.
Wi-Fi is working!!
Now only NikGapps is missing, but that is just booting into Recovery, flashing and booting back into System, so no problem here, anymore.
Thank you, @yan2xme! You say you are noob, but you had the right guess, too! Anyway, thanks for your help, I appreciate it!
P.S.: Boot-up is additionally much faster, smoother and without SystemUI crash on startup. This 12.0.4 firmware really sucks!
Click to expand...
Click to collapse
Ohhh... ok thanks for the appreciation too... Hehe
Resurrection Remix Rom Developer also pointed out that you should flash 12.0.3 even theres the newer version... So maybe.... Haha