Hi, I'm going to install the new CM 12.1 rom and I've never installed any custom rom, just the ota's and stable versions of miui.
First of, the recovery. If I'm not wrong the recommended is TWRP, so I go to their website and flash the last version (actually 2.8.7.0).
Now, about partitions. I've been reading in the website that the resize2fs feature will make a 32GB partition instead of the real space (I have the 64GB version). But I'm not sure if I have to use this feature to flash the cm rom. I suppose I have just to perform the factory reset wipe, cache and dalvik and then flash the zip. Will the user partition have the full capacity? (55,3GB i think)
Until now everything seems easy enough and reasonably understandable... The big deal is about the system partitions, I'm kind of lost about this, what's the difference between them, which one should I use for the rom, and the other one is if i want/need dual boot? (two different roms installed at once?). I think I read that they can be unified (merge the partitions and have more space in the system partition, what is this for?). I really don't know what to do but I know I don't need dual boot or tdb (once merged can be restored, right?).
And 1 last thing, about the kernel... Since it's open source I don't know if a custom one will be included in the rom or the stock will be used for cm12.1.
Thanks!
Hi, You are confusing so many things in your query.
1- If you are talking about the Offical CM12.1 nightlies then you need not to worry about partitions as it will work on stock partition layout, that's what written in device wiki page of CM website. You just need to flash it via TWRP/CWM.
2- If you are talking about other CM 12.1, then you might need to repartition system of your Mi3/Mi4, in that case you will loss the ability of dual boot, which I think is useless.
3- About repartition, As you know that Mi3/Mi4 has two system partitions of 650MB~ each but due to ROMs new partition table, it's quite difficult to merge install those ROM, so repartitioning is simply merging both systems to get more space to install such ROMS. You just need to flash a zip file via CWM recovery to repartition your device system partition & an other zip to get back to stock partition layout.
4- If I am not wrong you can use custom kernels on CM12.1.
I hope this help you to understand things you are asking, you can type back, if you need more help.
Good day.
Thanks for the answer!
Yes, I was talking about the official CM12.1 for my MI 3W. I won't bother with partitions, I'll just flash the zip.
And about the kernels, I saw there are many. But I'll focus on stock and the CM kernel, as they're probably the best and most stable. The CM kernel for cancro is the one in the github repo? How can I install it? I suppose I have to compile it, zip it and flash it. This is the stock kernel, right?
You know if there's some improvement or difference between stock and CM kernel?
Related
Hey all,
I just wanted to clarify this to ensure that my understanding of the Samsung recovery partition is accurate (which it very well may not be). Am I wrong in assuming that the kernel and the recovery are all located on the recovery partition for Samsung devices? I flashed the official ICS build via ODIN, and I'm wondering if it'd be a bad idea to flash an existing version of a CWM recovery.img while running the official ICS build. I don't want to flash an older kernel, but would obviously like to obtain root.
If that ends up being the case, I assume that I'd have to build a new CWM using the stock ICS recovery as a base? Sorry for the noob questions, I'm just trying to get a better understanding of how things are working under the hood for this thing.
Thanks!
AFAICT the recovery.img and the boot.img are in distinct partitions on the device. The default is to boot the stuff in boot.img (which consists of a descriptive header, a kernel image and a ramdisk image). I'm not sure (yet) of the format of the recovery.img but I wouldn't be surprised if it's formatted similarly (but don't quote me ). The recovery.img is only used if you use the 'download/recovery menu'.
The main point is that they _are_ distinct. So using a CMW recovery is fine with a Stock ROM.
Replacing the kernel, however, is a different matter. It requires basically reconstructing the boot.img 'on the fly'. If you want to see an example check out the updater-script for Motley's kernel.
As for root & CWM packages, see nirogu's excellent thread about it: http://forum.xda-developers.com/showthread.php?t=1406137
I am planning to flash a custom rom on my phone (for the first time).
Model : Xperia SP(C5302)
Build : 12.1.A.1.205 (Stock) running JB 4.3 with LB
I have rooted my phone using the towelroot method and installed supersu. I have also installed custom recovery from here http://forum.xda-developers.com/showthread.php?t=2649923
I am planning to flash this custom rom http://forum.xda-developers.com/xperia-sp/development/cyanogenmod-11-locked-bootloader-users-t2868398
So I have a few questions that I am not clear about(even after searching the forums). And sorry if they are dumb. I really want to understand as much as possible before flashing roms.:fingers-crossed:
1. After reading the thread of my recovery, from what I understand, the recoveries are installed in /system. But on OP of the custom rom, I am about to install, there is an instruction to format /system before flashing the rom. So my question is if I format the /system partition, won’t my recoveries be removed (by the recoveries itself) before I even flash the rom?
2. Also will the recovery still be available to me if say I enter bootloop for some reason during flashing the rom?(asking for the same reason as above that is wiping my /system should also remove my recoveries)
3. Does CM 11 come with any inbuilt custom recovery? If not can I install the one I am already using (assuming installing a custom rom will remove my installed recoveries)?
4. Say I screw up during the flashing procedure. So if I want to rectify this I should first flash the stock .205 ftf, root, install a recovery again and then restore using the nandroid backup. Am I correct?
5. Is it necessary to wipe cache and dalvik cache before flashing rom? I see this instruction in some roms but not in others. And dalvik should be wiped after flashing rom and gapps, right?
6. Should I install supersu again after I flash the rom. I read in an article that it causes problems with CM. As far as I know CM11 comes pre-installed with superuser. But it also supposedly causes some problems.
7. Is it safe to restore user app+data, messages and contacts backed up using Titanium backup on a newly flashed rom? I have seen conflicted views on this.
Click to expand...
Click to collapse
And that’s it for my questions (for now at least... ).
A Big Thanks in advance for all your helpful answers
Prat92 said:
I am planning to flash a custom rom on my phone (for the first time).
Model : Xperia SP(C5302)
Build : 12.1.A.1.205 (Stock) running JB 4.3 with LB
I have rooted my phone using the towelroot method and installed supersu. I have also installed custom recovery from here http://forum.xda-developers.com/showthread.php?t=2649923
I am planning to flash this custom rom http://forum.xda-developers.com/xperia-sp/development/cyanogenmod-11-locked-bootloader-users-t2868398
So I have a few questions that I am not clear about(even after searching the forums). And sorry if they are dumb. I really want to understand as much as possible before flashing roms.:fingers-crossed:
And that’s it for my questions (for now at least... ).
A Big Thanks in advance for all your helpful answers
Click to expand...
Click to collapse
First of all, I am only explaining the one I know about
1. Well, wiping the system will remove the recovery. That's why you'll have to flash the ROM after wiping the system. Do not ever reboot the phone after wiping the system but haven't yet flashed the ROM zip, else you'll have to do more work to flash the Stock ROM. This is due to the fact your phone does not have an OS to boot into! When flashing the ROM zip, the recovery will be automatically installed.
2. This is based on luck, most of time you'll end up unable to boot into anything. A fix is to flash the Stock ROM again.
3. Every ROM has recovery built with it (unless stated otherwise in the thread)! Upon flashing, it will be automatically installed too.
4. The methods you mentioned is correct. However, only restore the nandroid backup if you want to stay on stock. You could always retry to flash the ROM again. Nandroid backup is an image backup of your android. If you restore your nandroid backup, you'll end up with your previous version of android (like the way before you started flashing the ROM)
5. Wiping /cache and dalvik-cache is a really good practise! It doesn't really matter when you will need to wipe them, but personally I wipe them all before flashing the ROM. Wiping /data and performing a factory reset through recovery is recommended if you're coming from a different ROM. That's why backing up user apps through TiB (Titanium Backup) is recommended for you to easily get your installed apps back. Remember, nandroid backup and apps backup from TiB is different to each other.
6. No, this might cause extreme conflicts. No, I am using SuperUser as long as I have used CM. It never fails to give root permission at all despite the hatred I sense in some apps that overly-recommends SuperSU.
7. Of course it is very safe to restore them backups with TiB. However, based on my experience, messages and contacts were unable to be restored due to the difference in ROM version. I don't know if anyone else faces the same problem as mine. As of this, I really recommend your contacts to be synced with Google.
Heads up!
Based on this post, the dev of the ROM you wanted to flash, MrSteve555, recommends PhilZ when flashing the ROM.
TechnoSparks said:
First of all, I am only explaining the one I know about
1. Well, wiping the system will remove the recovery. That's why you'll have to flash the ROM after wiping the system. Do not ever reboot the phone after wiping the system but haven't yet flashed the ROM zip, else you'll have to do more work to flash the Stock ROM. This is due to the fact your phone does not have an OS to boot into! When flashing the ROM zip, the recovery will be automatically installed.
2. This is based on luck, most of time you'll end up unable to boot into anything. A fix is to flash the Stock ROM again.
3. Every ROM has recovery built with it (unless stated otherwise in the thread)! Upon flashing, it will be automatically installed too.
4. The methods you mentioned is correct. However, only restore the nandroid backup if you want to stay on stock. You could always retry to flash the ROM again. Nandroid backup is an image backup of your android. If you restore your nandroid backup, you'll end up with your previous version of android (like the way before you started flashing the ROM)
5. Wiping /cache and dalvik-cache is a really good practise! It doesn't really matter when you will need to wipe them, but personally I wipe them all before flashing the ROM. Wiping /data and performing a factory reset through recovery is recommended if you're coming from a different ROM. That's why backing up user apps through TiB (Titanium Backup) is recommended for you to easily get your installed apps back. Remember, nandroid backup and apps backup from TiB is different to each other.
6. No, this might cause extreme conflicts. No, I am using SuperUser as long as I have used CM. It never fails to give root permission at all despite the hatred I sense in some apps that overly-recommends SuperSU.
7. Of course it is very safe to restore them backups with TiB. However, based on my experience, messages and contacts were unable to be restored due to the difference in ROM version. I don't know if anyone else faces the same problem as mine. As of this, I really recommend your contacts to be synced with Google.
Heads up!
Based on this post, the dev of the ROM you wanted to flash, MrSteve555, recommends PhilZ when flashing the ROM.
Click to expand...
Click to collapse
Thanks for such detailed answers. That cleared most of my doubts
Just some last few questions(promise!)
1. If wiping /system does remove the recovery before I install the rom, how is it possible to access it even to flash the rom? Shouldn't it like just close right when I wipe /system. Or does it not work like that?
2. Just to be sure the nandroid backup I made on my stock rom won't work if I later try to flash it through recovery while using CM,right?
Prat92 said:
Thanks for such detailed answers. That cleared most of my doubts
Just some last few questions(promise!)
1. If wiping /system does remove the recovery before I install the rom, how is it possible to access it even to flash the rom? Shouldn't it like just close right when I wipe /system. Or does it not work like that?
2. Just to be sure the nandroid backup I made on my stock rom won't work if I later try to flash it through recovery while using CM,right?
Click to expand...
Click to collapse
1. Wiping system wont close the recovery at all. It still runs and you can still navigate within it. But remember do not reboot unless you've flashed the ROM! The mechanism of how the magic works is yet to be acknowledged. So I can't tell why it doesn't closes upon wipe. My best guess here is that the recovery might be running on a temporary partition perhaps. I hope a developer see this post and explains the magic.
2. Nandroid backup works all the time (if they are no errors when you are creating them). Nandroid backup is simply a backup of your whole device. If you're on CM, restoring nandroid backup will get your phone back to the way when you attempted the nandroid backup (stock ROM, rooted, and triple recoveries installed). Nandroid backup is useful when you're about to try something that may damage your ROM, without doing so much work to restore your device.
Say, you created a nandroid backup in cwm in which Cyanogenmod was installed. And then you flashed something afterwards. If that "something" damages the ROM and gives you bootloop, you can simply flash Stock ROM, root it again, install recoveries again, and restore the nandroid backup. Then, voilà, cyanogenmod is back. This will simplify your work rather than flash CM again, then gapps, then restore your apps and all those other things that will consume so much time
So a new nandroid backup will backup the whole device, in a form of an image.
Hi
I'm searching for a custom ROM for my mom's gamaxy s5 mini. Touchwize is very buggy on her devices, so i'm looking for a stable ROM.
I'm not specific looking for a ROM that has a lot of features but they are always welcome.
What ROM do you guys suggest?
Thanks
stock rom with custom kernel
Dev!n said:
stock rom with custom kernel
Click to expand...
Click to collapse
+1
Custom roms for the S5 Mini are still on BETA stage. They have some bugs, an higher battery drain and some features are unsopported. Stock rom with a custom kernel and ROOT os the best way. Also, don't forget to format the Data and Cache partitions into the F2FS filesystem.
Andrea224 said:
+1
Custom roms for the S5 Mini are still on BETA stage. They have some bugs, an higher battery drain and some features are unsopported. Stock rom with a custom kernel and ROOT os the best way. Also, don't forget to format the Data and Cache partitions into the F2FS filesystem.
Click to expand...
Click to collapse
What kernel do you suggest?
And how do I format data and cache partition into F2FS filesystem? And before I do that, in what filesystem are they formated originally?
titan1655 said:
What kernel do you suggest?
And how do I format data and cache partition into F2FS filesystem? And before I do that, in what filesystem are they formated originally?
Click to expand...
Click to collapse
I suggest this kernel: http://forum.xda-developers.com/galaxy-s5-mini/orig-development/kernel-custom-kernel-t3130662
You can format the two partitions into the TWRP 3.0.0 recovery. Normally, on every phone, they are formatted into the ext4 filesystem (you can also read it before formatting)
Andrea224 said:
I suggest this kernel: http://forum.xda-developers.com/galaxy-s5-mini/orig-development/kernel-custom-kernel-t3130662
You can format the two partitions into the TWRP 3.0.0 recovery. Normally, on every phone, they are formatted into the ext4 filesystem (you can also read it before formatting)
Click to expand...
Click to collapse
Last question.
Why only format the Data and Cache partitions into the F2FS filesystem? And not the other partitions?
titan1655 said:
Last question.
Why only format the Data and Cache partitions into the F2FS filesystem? And not the other partitions?
Click to expand...
Click to collapse
Because only these two partitions have this possibility.
What custom kernel would you recommend for G800H? And what is the advantage of formatting the partitions into F2FS?
morcio said:
And what is the advantage of formatting the partitions into F2FS?
Click to expand...
Click to collapse
https://en.wikipedia.org/wiki/F2FS should tell you why you want this (It's a FS designed especially for mobile devices that use flash memory for storage).
Sm-g800h or sm-g800f???
Info: model SM-G800F, baseband G800FXXU1BPC4
I had the same question as TS and listened to the advice of @Andrea224 by flashing the custom kernel mentioned in this thread.
I started with the stock 5.1.1 ROM.
- First I flashed the kernel using Odin3.
- Then I flashed TWRP 3.0.0 recovery using Odin3.
- Then I re-formatted \data and \cache F2FS booting in TWRP.
All went well.
When I boot in Recovery I got the question to mount read/write and the warning about not able to receive OTA updates.
When I exit Recovery I get the question to install SuperSU.
Coming from a long line of HTC devices the above questions are new to me.
What do they mean? I once did choose to install SuperSU. Is my phone rooted now? Or should I still flash the CF-Auto-Root-kminilte-kminiltexx-smg800f.tar.md5 file?
Also in TW I get the questions about not having an original software installed. Is this about Knox? How can I disable this?
Concluded: Have I done all the correct steps to have a stable system?
bakmanhans said:
Info: model SM-G800F, baseband G800FXXU1BPC4
I had the same question as TS and listened to the advice of @Andrea224 by flashing the custom kernel mentioned in this thread.
I started with the stock 5.1.1 ROM.
- First I flashed the kernel using Odin3.
- Then I flashed TWRP 3.0.0 recovery using Odin3.
- Then I re-formatted \data and \cache F2FS booting in TWRP.
All went well.
When I boot in Recovery I got the question to mount read/write and the warning about not able to receive OTA updates.
When I exit Recovery I get the question to install SuperSU.
Coming from a long line of HTC devices the above questions are new to me.
What do they mean? I once did choose to install SuperSU. Is my phone rooted now? Or should I still flash the CF-Auto-Root-kminilte-kminiltexx-smg800f.tar.md5 file?
Also in TW I get the questions about not having an original software installed. Is this about Knox? How can I disable this?
Concluded: Have I done all the correct steps to have a stable system?
Click to expand...
Click to collapse
Now, I will explain to you how to get it work properly:
- Boot your phone in download mode and flash the latest update of the TouchWiz for your country with Odin. (If you are on CM13, into TWRP: 1- Do a backup of your data; 2- In Wipe -> Advanced Wipe select Dalvik, Cache, System, Data and wipe these partitions; then select Cache and Data and format both to ext4; 3- After all, flash TWwith Odin)
- Boot your phone in download mode and flash SuperSU with CF-Auto-root.
- Boot your phone in download mode and flash the TWRP 3.0.0 with Odin.
- When you are into recovery: 1- Tick the option for never show this message on every reboot into recovery and then swipe to allow modification; 2- Do a backup of your Data; 3- Flash the custom kernel; 4- Format Data and Cache to F2FS; 5- Restore the backup of your Data; 6- Reboot the phone and DO NOT allow to install SuperSU if it ask to you. (If after the reboot, the phone says that your device isn't rooted, flash another time CF-Auto-root)
- With the kernel and root installed, now is time to delete some apps: 1- Download and install RootExplorer; 2- Go into "system" -> search SecurityLogAgent.apk into the folder called "app" or "priv-app" (I don't remember in which folder is it) and delete it. Naturally, you have to grant root access to the app.
Now you have a good and stable rom. Also, if you want to debloat the stock rom, you can use this ZIP -> http://forum.xda-developers.com/galaxy-s5/development/mod-urwsoft-barebone-cleaner-t3043479 (this is for the S5, but it's compatible with the S5 Mini) or you can delete manually some apps through RootExplorer. If you have some problems, contacts me.
With Root Explorer you mean the payed version?
Verstuurd vanaf mijn SM-G800F met Tapatalk
bakmanhans said:
With Root Explorer you mean the payed version?
Verstuurd vanaf mijn SM-G800F met Tapatalk
Click to expand...
Click to collapse
Yes, just search on Google the apk.
Did all the steps above except for the URWsoft BareBone Cleaner. I had to reflash both Autoroot and TWRP through Odin twice. Weird. By removing SecurityLogAgent.apk I was finally able to enjoy my device without being warned all the time. Nice!
I have noticed that after every reboot my Wifi connection settings are lost. Anybody else experienced this?
bakmanhans said:
Did all the steps above except for the URWsoft BareBone Cleaner. I had to reflash both Autoroot and TWRP through Odin twice. Weird. By removing SecurityLogAgent.apk I was finally able to enjoy my device without being warned all the time. Nice!
I have noticed that after every reboot my Wifi connection settings are lost. Anybody else experienced this?
Click to expand...
Click to collapse
It's a bug, it appears when you flash a custom kernel. To fix it, go here -> http://forum.xda-developers.com/showpost.php?p=65568464&postcount=10
I'm sorry for restoring such an old thread but my question is the same.
Which is the best rom for G800F?
Custom roms I see that have still many known bugs
Stock rom ok, but how about debloating it? I haven't found a debloated version, nor a guide/script to debloat it automatically.
And what about the kernel? Which is the best kernel for stock rom? And for custom roms?
Thank you
Alefello said:
Stock rom ok, but how about debloating it? I haven't found a debloated version, nor a guide/script to debloat it automatically.
Click to expand...
Click to collapse
I use Root Package Disabler from play store, it has in-built bloatware list that you can disable/freeze.
Very convenient and effective.
How about Resurrection Remix MM? It's marked as stable and it seems that everything is working in the changelog and comments.
Or LOS 13 too seems everything is working (but I can't find confirmation in comments)
I'm using this one
https://forum.xda-developers.com/galaxy-s5-mini/development/rom-resurrection-remix-n-5-8-2-t3562523
It's 7.1.2 RR. It's perfection. I'm not even kidding I've used it for 3 months and it's stable as hell. On top of that it has million features that come with RR roms. Battery life is really good too.
partitions are a little different here.
im creating something here before i flash AOSCP to my p20 pro and start working on it before i share it.
I'm creating a flashable TWRP .zip for european latest stock rom so that we can all recover easy when something goes wrong or when we want to go back to stock easy and fast.
So, i have :
kernel partition and system partition and vendor partition.
I assume kernel partition is the boot partition just renamed to kernel in the huaweis ?
And what else do we need to go back to stock ? I think those 3 are enough right ?
Hey there,
today I started flashing my mi9tpro.
First I tried xiaomi.eu, but still wasn't happy about the security/junkcleaner integration ...
So I moved on to paranoid quartz 4 for the start. Runs nice and smooth, could settle here.
But I wanted to give ressurection, crdroid, havoc a try too.
Now there is a conflict between the statement of xiaomi.eu:
FORMAT /data partition (NEVER wipe System or Persist!)
Click to expand...
Click to collapse
And e.g. crdroid:
Wipe Data/Cache/System when coming from non-AOSP ROMs
Click to expand...
Click to collapse
Sure, I am coming from a non-AOSP rom, so this is a step I need to do for trying the other roms based on AOSP.
BUT:
If I want to return to Miui, Xiaomi.eu or Paranoid ... will there be troubles about flashing?
Do I need to flash anything, so /system is returned to stock?
I made a full backup booting twrp before flashing anything (even twrp), so if I need a original /system, I should be able to restore this image.
Greetings
houston_ said:
Now there is a conflict between the statement of xiaomi.eu:
And e.g. crdroid:
Sure, I am coming from a non-AOSP rom, so this is a step I need to do for trying the other roms based on AOSP.
BUT:
If I want to return to Miui, Xiaomi.eu or Paranoid ... will there be troubles about flashing?
Do I need to flash anything, so /system is returned to stock?
Click to expand...
Click to collapse
No need to format /System, as it afaik can result in an instant-bootloop to Fastboot, which may then cause you to reflash the whole MIUI Fastboot ROM.
When coming from MIUI to AOSP ROMs, formatting /Data (aka the "Format Data" Option where you have to type "yes") should be enough.
Same process goes when going back to MIUI from AOSP.
Hope it helped!
houston_ said:
Hey there,
today I started flashing my mi9tpro.
First I tried xiaomi.eu, but still wasn't happy about the security/junkcleaner integration ...
So I moved on to paranoid quartz 4 for the start. Runs nice and smooth, could settle here.
......
If I want to return to Miui, Xiaomi.eu or Paranoid ... will there be troubles about flashing?
Do I need to flash anything, so /system is returned to stock?
I made a full backup booting twrp before flashing anything (even twrp), so if I need a original /system, I should be able to restore this image.
Greetings
Click to expand...
Click to collapse
The system partition is home to the OS. Every time you flash a ROM, you replace the system partition. If you want to return to stock, flashing MIUI will restore the stock system partition.
In reality there is no need to wipe the system partition, because flashing a ROM will wipe it automatically anyway, before installing the new ROM.
When flashing new ROMs, doing a factory reset is all that's needed. You should rarely need to enter advanced wipe menu in TWRP.
The only extra step required is when flashing over MIUI (official or custom version). In this case you will also need to format data too.
Follow my guide for flashing
https://forum.xda-developers.com/k20-pro/how-to/simple-guide-flipkart-owners-t4151007/post83329343
Thanks for both of of your answers! So nothing really changed since my HTC10. On my Cubot I used gsi images... Unsuccessfully, but quite easy.
Just wanted to ask before loosing something important