Hello to all! I want to know if someone makes to work dualboot f2fs with
devil recovery 6.0.4.5 and with
kernel Devil3.4_0.1.0-i9300-DUAL-20140209
when i format f2fs data and secondrom - restart
when i want to duplicate my first rom - restart
can't mount system on second boot menu
the recovery works with single rom f2fs partition but not dual
i use Smartdroid v4 and Smartdroid AOSP
Thanks for anser!
re
i got anser:
1. Install Devils recovery.
2. Install a rom to the first filesysten, preferrably the Sammy-based rom. Install a Devil2/3-kernel to it.
3. Make a nandroid backup of the Sammy rom to your external scdard.
4. Create a second filesystem in Devils recovery.
5. Restore your earlier made Sammy backup to the newly created second filesystem.
6. You now have two identical rom to choose from!
7. Clear the second filesystem to install a new rom.
8. Install the AOSP rom to the second filesystem. Install Devil 2/3-kernel.
9. Finished, choose from your two favorite roms!
BUT, there is a problem, Sammy-based roms doesn't seem to install in Devils latest recovery(error 7) so the above procedure should be made with the older Devils recovery on DerTeufel1980s OP. When everything is setup, ie you have made a nandroid of a working Sammy rom, you can upgrade to the latest recovery and choose which partitions should be formated to f2fs and restore selected backups with included Devil kernels to respective filesystem. If you run two AOSP roms this is not a problem, only if one is Sammy based!
Click to expand...
Click to collapse
i installed with succes dualboot f2fs with AOSP and something sammy based on devil recovery 6.0.4.5
-first i installed samy based rom with ext4 with kernel Devil3.4_0.1.0-i9300-DUAL-20140209 before restart.After than i made 1 system boot.
-custom backup
-format f2fs (i can't create the second image from dualboot menu if i restore sammy based on the first rom)
- after format i instaled ASOP 4.4.2 with preserve sistem f2fs, with no wipe at data and cache... instal Devil3.4_0.1.0-i9300-DUAL-20140209 kernel and restart. maked 1 sistem boot than RECOVERY inject gapps and then restart , maked another sistem boot (thats for open and works dualboot menu from recovery)
-RECOVERY -> dualboot -> create second image -> format sis , cache , data -> and than restored sammy based rom to secondrom on f2fs partition + Devil3.4_0.1.0-i9300-DUAL-20140209 kernel to be sure thats all ... that's a solution to have on dev 6.0.4.5 dualboot f2fs
AOSP + SAMMY BASED
formatting system to f2fs
hi ,
i am using agni kernel with carbon Rom i have formatted data .preload,cache to f2fs,but cannot get system formatted,can someone
point me to a tutorial to get it done ,please or explain it to me
Related
hi, i wanna ask...if i wanna flash to another devoid.Franco ROM (previously using void.echo) do i still need to dl the Terminal Emulator & Custom Recovery Tool Image and its Flash Image then run the Terminal Emulator & key in the codes then only start flashing another ROM?
i've did tat at the first time i flashed to a void.echo ROM now i wanted to flash to devoid.franco, do i still need to repeat all that step again? or i just enter the "power button, volume down button and home button" mode then wipe then flash will be good?..need advice thanks..
Just wipe and flash..
thanks for quick reply!
another question...how do i know that i already have the ext partition?...after i wipe everything included wipe ext..do i still need to create again?
Wiping doesn't remove partition..
On Mike mod
can we install franco kernel on mike mod 6.5.2
If your from void#echo previously, do these:
1. Backup all your user apps+contacts via Titanium Backup and all SMS via SMS backup
(they're all available free in the market)
2. Turn off phone. Reboot to recovery (hold power button+home+vol down)
3. Wipe user data, .android secure, cache, dalvik-cache, battery stats, and wipe ext.
4. Since your on void#echo already, you don't need to partition your sdcard.
5. Download devoid.franco, use usb-toggle on the recovery menu and copy it from pc to your phone while on the recovery and flash it.
6. Reboot (first boot might take a while)
7. Configure settings, Install titanium backup and sms restore app, Then restore all apps+settings+SMS. Enjoy~
8. Well if you know already what your doing and want some further improvements (completely optional, just do a nandroid backup incase) :
8.1 Reboot to recovery
8.2 Flash the latest kernel version from franco's thread
8.3 Reboot
8.4 Flash the ZRAM module
8.5 Reboot and Enjoy your phone
Thanks Kira.Lawliet!
hmm...i actually partition my sdcard again...yea..i flash before saw your reply ._.
will it harm? i partition my sdcard again....n flash to devoid.franco
You have to partition only if you want apps2sd. Else let it be. You can easily remove the ext partition by partitioning with 0mb ext partition in recovery.
sanmore said:
can we install franco kernel on mike mod 6.5.2
Click to expand...
Click to collapse
definitely you can. just flash your device with mik_os mod first. then flash the franco kernel (v15 now) and lastly flash the ZRAM initializer.
just make sure you wipe the cache and dalvik cache first before you're flashing.
flashing
Ok guys just remember that rom flashing requires you to follow rom partition conditions while kernel flashing may not need to recreate partitions. In my case, I'm using Nessy Hypnos2 and been running with much fluidity after flashing FrancoKernel 14.2. But I did wipe all just to make sure there wont be any conflicts. HYPNOS2 + FRANCOKERNEL 14.2 is like coffee and cream, a perfect match like newlyweds.
Hello fellas
This guide is just a quick how-to on dual booting. Many people have doubts on how to dual boot on Siyah, because it's something new and perhaps "scary" because they may think it can brick their phone.
___________________________________________
Requirements
A Galaxy S II I9100
3.x Siyah Kernel (3.2.x preferred). For latest version, visit the Siyah Kernel thread
90% charged battery
2.5GB of free space in your internal SD card
Patience
Time
So, do you complete all those requirements? Time to go to action. BUT BEFORE, a brief FAQ in a simplified way, based from this post made by the amazing droidphile
___________________________________________
FAQ
Can I dual boot Ice Cream Sandwich and Jelly Bean?
Yes you can, using Siyah v3.5.2.
1) What is dual booting?
Dual booting is the ability to boot into two different Ice Cream Sandwich-based ROMs (like CM9 and AOKP).
2) How is this done?
This is achieved by sharing the kernel and using a hidden partition in dev/block to store the 2nd ROM's /system and the /sdcard (Internal storage) to store /data and /cache inside a hidden folder (/sdcard/.secondrom)
3) How much does it take to clone a ROM?
It should take around 7 minutes
4) I want to dual boot fasturr. wat do?
When you get the splash screen to choose between ROMs, touch the screen or press volume UP to enter the PRIMARY ROM, and press the Home button or volume down for the SECONDARY ROM.
5) How can I remove the Dual boot and its partitions?
Just use the "Remove 2nd ROM" option in the Dual Boot options menu.
6) If I format my /sdcard, will my second ROM go kaput?
Yep, because you're wiping the folder that contains /data and /cache.
7) Can I dual boot a gingerbread ROM in a ICS ROM?
Niet. No.
___________________________________________
Now, the PROCEDURE
You must flash the Siyah kernel, either with CWM or ODIN
After you have flashed the kernel, reboot and let Android upgrade itself.
All done? Alright, move up to next step!
Download the desired ROM that you want to make it secondary, and place it in a safe place in your internal SD card
After that, reboot to CWM Recovery, and navigate to "Dual Boot options"
You'll see a list of options, namely :
View current status
Clone 1st ROM to 2nd ROM
Clone 2nd ROM to 1st ROM
Swap 1st ROM with 2nd ROM
Swap 2nd ROM with 1st ROM
Remove 2nd ROM
Install 2nd ROM from Internal SD card
Install 2nd ROM from External SD card
Wipe 2nd ROM data/cache
Wipe 2nd ROM dalvik-cache
Fix 2nd ROM permissions
What does each one mean, you ask?
View current status - This option will show you the stats of the dual booted ROM.
Clone 1st ROM to 2nd ROM - This option will copy (clone) the current ROM that you use (for example, CM9) and paste it to the 2nd ROM directory. Takes around 7-20 mins.
Clone 2nd ROM to 1st ROM - This options copies the 2nd ROM (after installed of course) and pastes it to the place where the 1st ROM was, replacing it.
Swap 1st ROM with 2nd ROM - This will swap the 1st ROM with the 2nd ROM, making the Primary ROM -> Secondary ROM and the Secondary ROM -> Primary
Swap 2nd ROM with 1st ROM - This will do the exact opposite of the above option
Remove 2nd ROM - This will completely wipe and remove any 2nd ROM files and folders
Install 2nd ROM from Internal SD card - This option is to flash the ROM to the 2nd ROM directory from the Internal SD card
Install 2nd ROM from External SD card - This option is to flash the ROM to the 2nd ROm directory from the External SD card
Wipe 2nd ROM data/cache - This will wipe the 2nd ROM data and cache. When it's done for the first time, it'll create data.img and cache.img and create the folders inside /sdcard/.secondrom, preparing your phone for the 2nd ROM.
Wipe 2nd ROM dalvik-cache - This will wipe the dalvik cache of the 2nd ROM
Fix 2nd ROM permissions - This will fix the permissions of the 2nd ROM
Select the option Wipe 2nd ROM data/cache. This will prepare your phone to flash the 2nd ROM. It takes around 5-7 minutes.
After having that done, select the option to wipe the dalvik cache.
After all that is done, select either "Install 2nd ROM from Internal SD card" or "Install 2nd ROM from External SD card" depending on the location of your ROM
Wait a few minutes for the flash
Reboot
Press the Home button or volume down to enter the Secondary ROM
___________________________________________
After you have done all that, you're set and you're in the Dual Booting world! I hope that this guide helped you, and if it did, press the thanks button!
___________________________________________
Credits
GokhanMoral - For his amazing kernel
Droidphile - For his great FAQ
Nice. Great for people who are not sure how they going to set up their dual boot option.
Edit: What about mounts and options, where you need to format the /secondrom_cache, /secondrom_system and /secondrom_data when you try to setup the very first time? If this step is not taken, you won't be able to have the option to choose either 1st or 2nd rom. Only subsequent reflashing of 2nd rom, then you just need to wipe 2ndrom cache and data.
Unless Gokhanmoral had changed his kernel, I think this is the most important part.
Please correct me if I am wrong.
Nice tutorial, very clear...
One question: I want to dual boot to a stock ICS rom for use a MHL adapter (resurrection remix dont support it as most of the AOSP/AOKP roms)... appart of that, what uses can you give to dual boot?? I cant imagine more!
whats wrong with this guide which is in the first post of siyah thread if people fail to read the faq prior to doing this instructions are pretty easy anyways even tho your guide is more clearer and pretty lol and you have taken the time to do this you will still get the some old questions beening asked lol.
anyways best wishes to you
Maybe it is time GM gets a section in XDA specifically for Siyah ...
g00ndu said:
Nice. Great for people who are not sure how they going to set up their dual boot option.
Edit: What about mounts and options, where you need to format the /secondrom_cache, /secondrom_system and /secondrom_data when you try to setup the very first time? If this step is not taken, you won't be able to have the option to choose either 1st or 2nd rom. Only subsequent reflashing of 2nd rom, then you just need to wipe 2ndrom cache and data.
Unless Gokhanmoral had changed his kernel, I think this is the most important part.
Please correct me if I am wrong.
Click to expand...
Click to collapse
It seems that kernel was changed recently. What I did for my current dual-booting (used Siyah 3.2.3 that time): Wiped data/cache and dalvik of 2nd rom and just flashed new rom from recovery. I didn't format any partitions and had no problems at all with possibility to choose a rom at boot. Regards
Perhaps you can put in the GUIDE FAQ that step 9 doesn't flash the kernel image if present in the zip. (Assuming that it doesn't flash anything other than the /system and /data partitions correct me if I'm wrong)
The first time I used it I feared that I would mess up because I knew that the zip had the kernel img inside.
Good tutorial, thanks!
Many40 said:
It seems that kernel was changed recently. What I did for my current dual-booting (used Siyah 3.2.3 that time): Wiped data/cache and dalvik of 2nd rom and just flashed new rom from recovery. I didn't format any partitions and had no problems at all with possibility to choose a rom at boot. Regards
Click to expand...
Click to collapse
What about the 1st time when you set up your dual rom? I remember that there were a few people who had written in saying they do not have the option of booting into the 2nd rom after following the method describe by the OP.
g00ndu said:
What about the 1st time when you set up your dual rom? I remember that there were a few people who had written in saying they do not have the option of booting into the 2nd rom after following the method describe by the OP.
Click to expand...
Click to collapse
Belive me I did only what I wrote to you. I did not format any partitions and had no problems at boot at all. (Boot option to choose 2nd rom has been available). To be sure I have asked this afternoon also droidphile (author of very helpful guide and experienced on this topic). This is his answer: http://forum.xda-developers.com/showthread.php?p=26742671 Regards. Happy if helped.
Sent from my GT-I9100 using xda premium
DJBoxer said:
whats wrong with this guide which is in the first post of siyah thread if people fail to read the faq prior to doing this instructions are pretty easy anyways even tho your guide is more clearer and pretty lol and you have taken the time to do this you will still get the some old questions beening asked lol.
anyways best wishes to you
Click to expand...
Click to collapse
My intent was to make it even easier and more accessible/straightforward. My guide is meant for first timers, while that guide is more for people who have basic knowledge, which isn't always the case.
g00ndu said:
Nice. Great for people who are not sure how they going to set up their dual boot option.
Edit: What about mounts and options, where you need to format the /secondrom_cache, /secondrom_system and /secondrom_data when you try to setup the very first time? If this step is not taken, you won't be able to have the option to choose either 1st or 2nd rom. Only subsequent reflashing of 2nd rom, then you just need to wipe 2ndrom cache and data.
Unless Gokhanmoral had changed his kernel, I think this is the most important part.
Please correct me if I am wrong.
Click to expand...
Click to collapse
g00ndu said:
What about the 1st time when you set up your dual rom? I remember that there were a few people who had written in saying they do not have the option of booting into the 2nd rom after following the method describe by the OP.
Click to expand...
Click to collapse
Replying to both of those quotes, wiping data/cache creates data.img and cache.img. GM did a great job on dual booting, now it requires fewer steps.
Not booting second rom!
Hey there its a good tutorial but the problem is that its not booting the second rom! My primary rom is Resurrection Remix v2.0 and I want to dual boot Cyanogenmod 7.2.0 RC3 but I do everything and when I go to boot it and press the home button to boot into the second rom it just displays a blank screen with no boot animation. Any help would be appreciated!
Thank you!
Catley!
Sweet...Siyah
Cool Tutorial...Been using dual ROMS on my GS2 for about a week now...works like a charm...gives a chance to try out all those cool customs ROMS...
Catley said:
Hey there its a good tutorial but the problem is that its not booting the second rom! My primary rom is Resurrection Remix v2.0 and I want to dual boot Cyanogenmod 7.2.0 RC3 but I do everything and when I go to boot it and press the home button to boot into the second rom it just displays a blank screen with no boot animation. Any help would be appreciated!
Thank you!
Catley!
Click to expand...
Click to collapse
Phistachio said:
7) Can I dual boot a gingerbread ROM in a ICS ROM?
Niet. No.
Click to expand...
Click to collapse
It's all in the FAQ/OP...
I currently have VK 4.8 and I was wondering if it's possible to install a stock rom as secondary, XXLPW for istance.
Thanks
pippofiori said:
I currently have VK 4.8 and I was wondering if it's possible to install a stock rom as secondary, XXLPW for istance.
Thanks
Click to expand...
Click to collapse
Currently ICS Sammy and AOSP roms can be dual-booted so it's possible.
If you have .zip CWM flashable rom file:
1. Flash Siyah kernel
2. Flash your rom as 2nd from dual boot CWM menu
If you have .tar Sammy rom file:
1. Flash Siyah kernel
2. Clone 1st rom to 2nd
3. Flash Sammy rom as 1st rom from for example mobile odin - remember not to loose root so when you open rom .tar file then when all partitions are recognized change in odin stock kernel to Siyah.
4. Swap 1st and 2nd roms.
Sent from my GT-I9100 using xda premium
hello,
I want cm9 and the stock rom.. is it the same way to do it? just flash the stock rom as secondary??
yakie996 said:
hello,
I want cm9 and the stock rom.. is it the same way to do it? just flash the stock rom as secondary??
Click to expand...
Click to collapse
Yes, but a way to do that depends whether you have .tar or .zip rom file
Sent from my GT-I9100 using xda premium
Great info and easy to follow, will give it a try and see the results
Hi,
I have Resurrection Remix 2.0 as my 1st ROM with Siyah 3.2.7.2. I'd like to add Slim ROM as a 2nd, but Slim comes with the Fluxi kernal as part of the zip. Will that screw things up?
Things required:
A GOOD recovery that allows u to choose that to backup
I used TWRP.
AmonRA has bugs restoring boot.img for ICS. , so do not use it fot this purpose.
Amon ra will make the os generate dalvik-cache from the very beginning and u'll be stuck at "Android is upgrading" for some time.
CWM doesnt let u choose what to backup.
Tassadar's MultiROM
http://forum.xda-developers.com/showthread.php?t=1304656
A modded recovery for multirom
Some sympathy for ur good'ol phone
what are we doing:
contrary to what many people have posted in the multirom thread, ICS kernels ARE compatible with gb (cm7 to be specific). yes, USB wont work in gb. KGSL drivers wont work in Stock ROMs. But is good enough to make it boot.
What prevents gb from booting if u have ics in ur internal memory, is the bootloader. So, basically we need to swap with a gb bootloader before booting gb.
/boot contains ur bootloader, kernel, ramdisk and some other stuff. So, we will be backing up and swapping the kernel as well in the process.
HOWTO:
This is a one time procedure, unless u decide to change ur rom in sdcard later
Lets assume u have ics in internal memory, with ur favourite kernel.
For the lines marked with [TWRP], u'll have to use TWRP, and for other lines, u have to use a modded recovery by Tassadar.
so u'll have to flash different recoveries bewteen some steps.
[TWRP] flash multirom if u havent.
[TWRP] backup only /boot. note the name of the backup (or maybe rename it by mounting as USB storage). this is the one u would need to restore if ur moving from another OS to ics.
[TWRP] do a full backup.
flash gingerbread/froyo rom. Flash multirom. Flash ur fav. kernel(if u need to)
the rom has to be compatble with ur baseband. if not, flash some baseband fix.
multirom > "create from internal memory"
multirom > "move to backup" (only if ur installing more than 1 ROM in sdcard)
[TWRP] backup only /boot. remember the name of the backup.
repeat steps 4-8 for more roms u want to keep.
[TWRP] restore the full backup u created at the beginning, so that u have ics in int. mem.
Now u need to restore a /boot backup only if ur switching between android versions. for example, if u want to switch from ics to gb, just restore the backup which contains /boot from the gb ROM. Then u can just boot normally with Multirom's boot manager.
Q&A for [ROM][STABLE] Slim CM7 #4 [19/12/2013][LINKS ADDED]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][STABLE] Slim CM7 #4 [19/12/2013][LINKS ADDED]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
My S5830i won´t boot up
Hi Guys,
its great to see, that there are still some users of this device and this rom. I try to flash a rom for the Ace for at least 7 Days now. I bricked it already, restored it with a full Stock firmware. I tried a lot of cm7 roms but none of them would boot up. I installed them like described. Recovery, wipe, install kernel reboot recovery install rom and gaps. After rebooting it stucks at the "Samsung Galaxy Ace" start screen. I already wiped Data and Cache after this, but it wont fix this problem. I would absolutely happy if someone could give me a hint what could be wrong.
Thanks for your help, cheers!
@NootYest, I am really concerned about the correct way you have been restoring your device back into stock firmware [ RFS partitions ] though. please follow my instruction @ post#6 for wipe flash-able zip packages , if you are doing other methods.
As for your problems , I am going to devise an experiment to force your partitions being transformed into EXT4, before flashing our CM Specific Basic Kernel. ( Method would apply only to CM7/7.2 based on kernel CM7 v4.0 (cooperVe). Do not use it on newer CM's please. )
Requirements :
SLIM_CM7.2_Cooperve #4
Temporary CWM for s5830i/c/M/s5839i devices , known as cooperVe.
CM Specific Basic Kernel - BroadcomCM[COOPERVE][v4.0 ]
EXT4 Formatter Tool
SLIMGapps by mathm2013 (Optional) >> This is an extreme bare bone Rom , check Dev section; his topic; for more instruction on how to flash this package.
1.. Copy them in the root of your SD card. ( Full back ; EFS partition back up; CWM back up is advised)
2.Boot into stock e3 recovery >> wipe data and flash your Temp CWM
3.cwm > wipe data > wipe cache > wipe dalvik cache
4.flash the EXT4 Formatter tool, so whole system will be converted to EXT4. (Stock filesystem is RFS).
5.Install kernel_CM7_v4.0_cooperVe .
6.When the Kernel is installed, go to the advanced menu --> "reboot recovery" (this will reboot the device, thus you will be directed into your new CWM built-in, which is implanted inside Kernel ).
7.Wipe data, cache and dalvik
8.Go to "mounts and storage", and make sure /system partition is mounted (will show unmounted)
9. Main menu > "Install zip from SD Card" > choose "zip from SD card" and install the ROM.
10.Reboot
I am going to check on your progress later ,,,,,
ehsanotaku said:
@NootYest, I am really concerned about the correct way you have been restoring your device back into stock firmware [ RFS partitions ] though. please follow my instruction @ post#6 for wipe flash-able zip packages , if you are doing other methods.
As for your problems , I am going to devise an experiment to force your partitions being transformed into EXT4, before flashing our CM Specific Basic Kernel. ( Method would apply only to CM7/7.2 based on kernel CM7 v4.0 (cooperVe). Do not use it on newer CM's please. )
Requirements :
SLIM_CM7.2_Cooperve #4
Temporary CWM for s5830i/c/M/s5839i devices , known as cooperVe.
CM Specific Basic Kernel - BroadcomCM[COOPERVE][v4.0 ]
EXT4 Formatter Tool
SLIMGapps by mathm2013 (Optional) >> This is an extreme bare bone Rom , check Dev section; his topic; for more instruction on how to flash this package.
1.. Copy them in the root of your SD card. ( Full back ; EFS partition back up; CWM back up is advised)
2.Boot into stock e3 recovery >> wipe data and flash your Temp CWM
3.cwm > wipe data > wipe cache > wipe dalvik cache
4.flash the EXT4 Formatter tool, so whole system will be converted to EXT4. (Stock filesystem is RFS).
5.Install kernel_CM7_v4.0_cooperVe .
6.When the Kernel is installed, go to the advanced menu --> "reboot recovery" (this will reboot the device, thus you will be directed into your new CWM built-in, which is implanted inside Kernel ).
7.Wipe data, cache and dalvik
8.Go to "mounts and storage", and make sure /system partition is mounted (will show unmounted)
9. Main menu > "Install zip from SD Card" > choose "zip from SD card" and install the ROM.
10.Reboot
I am going to check on your progress later ,,,,,
Click to expand...
Click to collapse
Hi ehsanotaku,
thank you for your reply!!!!! I did the trick! I tried different processes of installing cm7 and i think i know where the problem were.
First let me explain how i installed the rom. The Situation is a s5830i with Stock GB and an empty SDCard:
1. I copied the temporary cwm, the kernel, the cm7 and the gapps on the root of the SD
2. Reboot into stock recovery and start tmp recovery
3. Wipe data cache and dalvik
4. Install cm7 kerne and reboot recovery
5. Now I am in the new kernel recovery. There I go to mounts and storage, unmount system and format system
6. After formating system I installed the cm7, went back to mounts and storage and check if system is mounted
7. If system is mounted UNmount System
8. Install gapps, wipe cache and dalvik and reboot
The things i did in another way were formating system and unmount system before installation. So the update package had to mount the partition on its own. This process worked for me two times on two different devices. Perhaps you can add this to the main thread for future users.
Thank you!
@NootYest, I was going to recommend you to format your /System partition where your previous Android OS was resided, after your initial test. However this process is not necessary by default , when you are coming from stock GB -based OS ( unless you didn't revert back completely to your OLD RFS partitions as I did instruct ) . And for any modification/suggestion in regards of installation alternative methods please pm OP of ROM . I am just a regular novice helper @ XDA.
Have fun tinkering
I can confirm this works on a s5839i. Installed today on s5839i.
Any themes available for this rom as the packaged theme leaves a little to be desired, on all levels.
Oh dear this post seems to have been redirected to a different thread, so the question by the previous users in the other thread goes unanswered.
can you make a video on it pls pls ..............
kkaarann said:
can you make a video on it pls pls ..............
Click to expand...
Click to collapse
??
Thanks for this ROM
my 5830i was actually unusable on stock rom due to too many built in apps....This Slimcm7 rom actually solved my cell problem...too stable too light fluid performance.
Just on negligible issue is that sygic maps are not working on it but as i said its negligible.
Thanks developer for this wonderful rom
hii,
My device is currently running on miui 8.5.4.0 global stable,i want to flash los 14.1,and planned some steps in order to revert back to miui safely.please correct me if i am wrong.
1.boot into twrp recovery.
2.Take full backup of current working rom including system.
3.clear data/system/cache/dalvik.
4.flash firmware-los rom-gapps-reboot.
Steps to revert back:-
1.boot into twrp recovery.
2.clear data/system/cache/dalvik.
3.restore full miui backup including system.
4.flash lazy flasher zip to disable dm-verity and forced encryption.
5.reboot.
i have just learnt basics completely but i had some doubts so i posted the entire procedure i thought to do.
thanks.
After taking backup first go to Wipe menu and "Format Data" , type yes and reboot recovery, it will remove encryption - then you can wipe data/system/cache etc..
/system wipe is never necessary .. You can skip that
Hollow6 said:
/system wipe is never necessary .. You can skip that
Click to expand...
Click to collapse
doesn't it mess up with firmware flash of custom rom?does a custom rom contains a system partition of its own to be flashed?or it just replaces or moves required system files to system partition of stock rom? help me to clear my concept!
k3lcior said:
After taking backup first go to Wipe menu and "Format Data" , type yes and reboot recovery, it will remove encryption - then you can wipe data/system/cache etc..
Click to expand...
Click to collapse
what is the difference between format data and wipe data? isn't it same?i am asking so because i havnt seen such option in recovery before.
sorabhsolanki said:
doesn't it mess up with firmware flash of custom rom?does a custom rom contains a system partition of its own to be flashed?or it just replaces or moves required system files to system partition of stock rom? help me to clear my concept!
Click to expand...
Click to collapse
Every ROM does contains its own system ..
When you flash any ROM (a full fledged ROM not OTAs) , the previous system is replaced by the later one ..
---------- Post added at 05:54 AM ---------- Previous post was at 05:50 AM ----------
sorabhsolanki said:
what is the difference between format data and wipe data? isn't it same?i am asking so because i havnt seen such option in recovery before.
Click to expand...
Click to collapse
You'll have to understand what Format Exactly we are here talking about .. When you go to TWRP/wipe , you are provided with 2 options , Format and Advanced wipe .
The format option is set to "wipe" the partitions, /data /cache /dalvik , that is generally what we require in order to flash ROMs , the wipe Option is hence the same as format , but I think the guy above is talking about Full fledged Wipe that includes the "internal storage" as well which can be selected by twrp/wipe/advanced wipe
Hollow6 said:
Every ROM does contains its own system ..
When you flash any ROM (a full fledged ROM not OTAs) , the previous system is replaced by the later one ..
Click to expand...
Click to collapse
thanks.one more question.
why dont i need to disable dm-verity and forced encryption after flashing custom rom?why kernel doesn't trigger it,because in that case there is a modification in system partition and dm-verity feature of kernel should prevent the rom from booting.
The "kernel" itself also gets replaced by a modified kernel .. But then again , I'm not sure as to why DM verity doesn't kick in , better ask the Developers (Y)
sorabhsolanki said:
hii,
My device is currently running on miui 8.5.4.0 global stable,i want to flash los 14.1,and planned some steps in order to revert back to miui safely.please correct me if i am wrong.
1.boot into twrp recovery.
2.Take full backup of current working rom including system.
3.clear data/system/cache/dalvik.
4.flash firmware-los rom-gapps-reboot.
Steps to revert back:-
1.boot into twrp recovery.
2.clear data/system/cache/dalvik.
3.restore full miui backup including system.
4.flash lazy flasher zip to disable dm-verity and forced encryption.
5.reboot.
i have just learnt basics completely but i had some doubts so i posted the entire procedure i thought to do.
thanks.
Click to expand...
Click to collapse
when you want to revert back you dont need to wipe anything or flash disable dm verify, just restore your previous nandroid backup and thats all