Related
Hi,
I am currently on the Darky v7.0 and I wanted to flash to 7.0.2
Do I just copy the rom in the sd folder and flash using rom manager just as i did before?
or do i have to switch back to stock 2.1 (rogers) and then flash 7.0.2?
This will be my second time flashing.
Please advice.
Thanks
Just install it over 7.0 if you got the non wipe version.
peachpuff said:
Just install it over 7.0 if you got the non wipe version.
Click to expand...
Click to collapse
This is the thread and the link to it. it does say "No wipe".
[ROM] Official Darky Port v7.0.2 No Wipe]
http://forum.xda-developers.com/showthread.php?t=880859&page=53
so does it mean its ok to install over 7.0?
does no wipe mean i dont have to wipe/remove the rom before flashing a new one?
Thanks
I too am curious why we are told to revert back to 100% stock before every time we change a rom. Why can't we just use Clockwork Recovery to wipe data/factory reset just like we do with every other Android phone?
Phateless said:
I too am curious why we are told to revert back to 100% stock before every time we change a rom. Why can't we just use Clockwork Recovery to wipe data/factory reset just like we do with every other Android phone?
Click to expand...
Click to collapse
samsung, in their infinite wisdom, decided rfs was the best filestructure to use for this phone. some roms change that to ext4 with voodoo, some roms rely on ULF to convert to ext4 and some dont convert anything.
ODIN is the user-friendly way to wipe everything back to stock...completely. if you remember to revert any lagfix (voodoo, ULF) then load your rom, it will work fine.
HOWEVER, there are so many people that dont remember to do that, its easier to flash back to stock rather than troubleshoot what could have possibly happened during their flash
personally, i have found that it takes just as long to revert the lagfix as it does to use ODIN....so rather than hoping that my new flash isnt corrupted in some way by my old flash, i flash back to stock. takes me 5 minutes total. as long as you keep a copy of the CWM update.zip on your sdcard, there is not even a reason to boot back into stock and root/setup/install rom manager, etc.
Pirateghost said:
samsung, in their infinite wisdom, decided rfs was the best filestructure to use for this phone. some roms change that to ext4 with voodoo, some roms rely on ULF to convert to ext4 and some dont convert anything.
ODIN is the user-friendly way to wipe everything back to stock...completely. if you remember to revert any lagfix (voodoo, ULF) then load your rom, it will work fine.
HOWEVER, there are so many people that dont remember to do that, its easier to flash back to stock rather than troubleshoot what could have possibly happened during their flash
personally, i have found that it takes just as long to revert the lagfix as it does to use ODIN....so rather than hoping that my new flash isnt corrupted in some way by my old flash, i flash back to stock. takes me 5 minutes total. as long as you keep a copy of the CWM update.zip on your sdcard, there is not even a reason to boot back into stock and root/setup/install rom manager, etc.
Click to expand...
Click to collapse
Thank you, that's the answer I was looking for. I already noticed that CWM can be flashed through an update.zip, so if I'm currently running the stock rom I don't have to ODIN and wipe data, do I? I can just flash CWM, nandroid, then go ahead and flash whatever I want?
Then NEXT TIME I flash something else I'll have to ODIN first.
Or does the user data already present in the stock rom make enough of a difference that I should ODIN anyway?
Phone is my gf's so I would really like to have a nandroid of her setup exactly as it is now so we can go back if she doesn't like Cognition, or whatever rom we decide to flash.
Phateless said:
Thank you, that's the answer I was looking for. I already noticed that CWM can be flashed through an update.zip, so if I'm currently running the stock rom I don't have to ODIN and wipe data, do I? I can just flash CWM, nandroid, then go ahead and flash whatever I want?
Then NEXT TIME I flash something else I'll have to ODIN first.
Or does the user data already present in the stock rom make enough of a difference that I should ODIN anyway?
Phone is my gf's so I would really like to have a nandroid of her setup exactly as it is now so we can go back if she doesn't like Cognition, or whatever rom we decide to flash.
Click to expand...
Click to collapse
you are correct in assuming that if you are running stock currently, you do not have to odin first
if you remember to revert any lagfix that may have been applied (depends on rom) you wont have to ODIN
make a nandroid of her current setup.
now this is where it gets tricky. i just played around with doing this last night actually:
if you go from 2.1 to 2.2 or higher, you cannot just flash back to 2.1 nandroid restore. the nandroid doesnt backup or restore your modem and kernel
going backwards to 2.1, you will want to flash a 2.1 kernel, and modem prior to restoring your nandroid backup and vice versa if you make a nandroid of 2.2 and want to go back to it from 2.1
if you keep clockwork flashable versions of such needed kernels and modems as well as a nandroid of the original setup and the cwm update.zip file on your sdcard, you will never need odin...unless there is a major malfunction. this can all be done in CWM, but as i said, the noob-friendly, and surefire way to get a fresh install is ODIN. i dont think any other company has something like this available to flash back to stock, so the methods used on the roms in the galaxy s phones are slightly different than the roms for htc or motorola devices. to me, i think this is a major win for us, in that most things are easily recoverable using a windows tool
Pirateghost said:
you are correct in assuming that if you are running stock currently, you do not have to odin first
if you remember to revert any lagfix that may have been applied (depends on rom) you wont have to ODIN
make a nandroid of her current setup.
now this is where it gets tricky. i just played around with doing this last night actually:
if you go from 2.1 to 2.2 or higher, you cannot just flash back to 2.1 nandroid restore. the nandroid doesnt backup or restore your modem and kernel
going backwards to 2.1, you will want to flash a 2.1 kernel, and modem prior to restoring your nandroid backup and vice versa if you make a nandroid of 2.2 and want to go back to it from 2.1
if you keep clockwork flashable versions of such needed kernels and modems as well as a nandroid of the original setup and the cwm update.zip file on your sdcard, you will never need odin...unless there is a major malfunction. this can all be done in CWM, but as i said, the noob-friendly, and surefire way to get a fresh install is ODIN. i dont think any other company has something like this available to flash back to stock, so the methods used on the roms in the galaxy s phones are slightly different than the roms for htc or motorola devices. to me, i think this is a major win for us, in that most things are easily recoverable using a windows tool
Click to expand...
Click to collapse
That makes sense, thanks! Over in HTC-land we call them radios instead of modems, and kernel/spl/radio all have to be compatible. Most are compatible with each other so there is seldom a need to flash around.
So what I gather from your post is that if she starts on stock 2.1 and I flash cwm, then flash Cognition (2.2 rom) I will most likely need to update the modem to match? Or is that only the case with stock roms?
Phateless said:
That makes sense, thanks! Over in HTC-land we call them radios instead of modems, and kernel/spl/radio all have to be compatible. Most are compatible with each other so there is seldom a need to flash around.
So what I gather from your post is that if she starts on stock 2.1 and I flash cwm, then flash Cognition (2.2 rom) I will most likely need to update the modem to match? Or is that only the case with stock roms?
Click to expand...
Click to collapse
most all the custom roms you will find will flash a kernel and modem that match and work properly with that rom
it really only applies to nandroid backups going from 2.1 to 2.2 and vice versa
Pirateghost said:
most all the custom roms you will find will flash a kernel and modem that match and work properly with that rom
it really only applies to nandroid backups going from 2.1 to 2.2 and vice versa
Click to expand...
Click to collapse
So you're saying when you flash the rom it will flash the correct kernel and modem as part of update/install script?
So basically I just need to install CWM, flash the rom, and not worry about the rest?
Phateless said:
So you're saying when you flash the rom it will flash the correct kernel and modem as part of update/install script?
So basically I just need to install CWM, flash the rom, and not worry about the rest?
Click to expand...
Click to collapse
yep
you dont need to worry about the rest until it comes time to flash to something else
there are a few options when that time comes:
use ODIN to restore to stock, then flash the next rom of your choosing
revert lagfix (if applied from the current rom you are running), then flash next rom of your choosing
if going back to a 2.1 NANDROID, not custom rom, then you will either need to odin, then flash.
or
flash 2.1 compatible kernel+modem and then restore your nandroid
Pirateghost said:
yep
you dont need to worry about the rest until it comes time to flash to something else
there are a few options when that time comes:
use ODIN to restore to stock, then flash the next rom of your choosing
revert lagfix (if applied from the current rom you are running), then flash next rom of your choosing
if going back to a 2.1 NANDROID, not custom rom, then you will either need to odin, then flash.
or
flash 2.1 compatible kernel+modem and then restore your nandroid
Click to expand...
Click to collapse
Got it. That all makes sense except for the kernel. Shouldn't that be included in the nandroid? I know the modem probably resides on a separate partition...
Phateless said:
Got it. That all makes sense except for the kernel. Shouldn't that be included in the nandroid? I know the modem probably resides on a separate partition...
Click to expand...
Click to collapse
the nandroid doesnt backup the kernel OR the modem as far as i know. either that or it doesnt flash them on the restore...
Pirateghost said:
the nandroid doesnt backup the kernel OR the modem as far as i know. either that or it doesnt flash them on the restore...
Click to expand...
Click to collapse
At least with HTC the kernel is part of the Rom and IS included in nandroids.
Hello, when i try to install custom kernel i face a boot loop. I only tried with v10, not tried with v20 though. Tried 3 different kernels and the same. Why is that? It just doesn't work.
And can you tell me some working custom kernel for v20l to try?
Thanks in advance.
What rom are you using?
For myself, usually its an issue of partition beinh ext3 or ext4 that will cause bootloop. I will usually try back2ext3 from paul or ext4 converter.. either one usually fix the bootloop depending on kernel requirements.
Cheers!
Not enough details. Which kernel?
On total stock ROM or on custom stock based ROM?
We are talking about kernel do don't use what is mentioned just above, it will wipe your all system.
I had a boot loop problem after installing a custom ROM based on stock ROM. I didn't wipe the phone before updating to custom ROM. After recovering the original ROM, I wiped the phone from CWM and then updated it and all works well now.
Well i have tried Neoblaze, HorsePower, Spica. I don't wipe after/before installing.
I om on stock rom. Then i must go back with back2ext3.
Striatum_bdr said:
Not enough details. Which kernel?
On total stock ROM or on custom stock based ROM?
We are talking about kernel do don't use what is mentioned just above, it will wipe your all system.
Click to expand...
Click to collapse
Sorry if I misunderstood the original question and thanks for clarifying!
martinesko36 said:
Well i have tried Neoblaze, HorsePower, Spica. I don't wipe after/before installing.
I om on stock rom. Then i must go back with back2ext3.
Click to expand...
Click to collapse
After installing the kernel try wiping cache and dalvik and see if that helps.
that's your problem, you have to wipe cache and dalvick cache after flashing. hope this can help
Thanks you, im very happy - working now. Flashed HorsePower.
Does Flashing a Custom Kernal Using Orange Fox Recovery Leads to Bootloop ?
1) If I do a full wipe, (cache, dalvik cache & system). Does this affect the kernel?
2) Currently I have the NOPE2.6 kernel. If I want to switch to a different rom that works with my kernel. Do I need to reflash the same kernel after installing the rom? Of can I just keep it?
3) Some roms can be used with either NOPE or Prometheus. But if I download the rom, I can see a 'boot.img' file in the zipfile. Is there a reason for this? I can't know which kernel it is, so I don't like flashing some unknown file.
Is this usually just a copy of NOPE/Prometheus, or something custom?
Thanks!
Wiping cache and dalvik will not affect the kernel. Btw, you never need to wipe system.
If the rom you are flashing is compatible with your current kernel, then you don't need to re flash.
It will be either prometheus or nope, if it is a cm rom.
spcd said:
1) If I do a full wipe, (cache, dalvik cache & system). Does this affect the kernel?
2) Currently I have the NOPE2.6 kernel. If I want to switch to a different rom that works with my kernel. Do I need to reflash the same kernel after installing the rom? Of can I just keep it?
3) Some roms can be used with either NOPE or Prometheus. But if I download the rom, I can see a 'boot.img' file in the zipfile. Is there a reason for this? I can't know which kernel it is, so I don't like flashing some unknown file.
Is this usually just a copy of NOPE/Prometheus, or something custom?
Thanks!
Click to expand...
Click to collapse
The boot imgs included in roms are either outdated versions of the existing kernels or the ones that were built from the compilation of the rom itself.
They are safe but most times unmodified, so they will not be overclocked.
I have been using Samsung for a long time and so this process seems weird. All we use to do there was just put the custom ROM and GAAPS and flash it via recovery and wipe phone. But when i was going through a lot of forums here..i see that the OP has asked people to flash the boot file using command prompt and then flash the ROM. Is this process really required even if we have the dual recovery installed?
If the updater script in the .zip does not have the correct commands to install the boot.img itself it has to be manually flashed.
Untill recently this was always the case, it was not possible to flash a kernel using recovery, it had to be done via fastboot.
I think this is probably a hangover from then, but now it can be done in recovery.
Also, if you have just unlocked, but do not have recovery installed the quickest way to get recovery is to flash the boot.img using fastboot, then flash the update.zip.
If you already have recovery, just flash the update.zip and the boot.img will be flashed.
This is only for roms int he original development section, as they require a custom kernel, roms in the development section will work on the stock kernel, so there is no need to flash a boot.img at all
Actually you need to flash different kernels for different roms... Like Stock-based(Sony) Roms can be either run on Stock Kernel(Sony) or Stock-Based Custom Kernel(like DooMKerneL). while AOSP Roms(like CM11) should be run on AOSP-based Custom Kernels(like Pimped Kernel).
You can flash custom Kernels only if you have unlocked your bootloader. if you have recovery on locked bootloader, then you can flash only Stock-based roms because they dont need a different kernel becoz they run on Sony Kernel itself. If you have a unlocked bootloader you can flash custom kernel, Then you can use both Stock-based Roms or AOSP-based Roms by flashing respective kernels.
If you already have Custom rom installed and changing to another Custom rom, Then if you are changing from (Stock-Based Rom to another Stock-Based Rom) or (AOSP-based Rom to another AOSP-based Rom) then you need not flash the kernel again, you can just wipe all partitions and install the new Custom rom over it. But if you are Cross flashing from (Stock-Based Rom to AOSP-Based Rom) or (AOSP-based Rom to Stock-based Rom), Then you should flash respective kernel, wipe partitions and install the rom over it.
if you dont know, whether the rom is Stock-based or AOSP-based, it will be mentioned in the OP of each Thread.Usually Roms that are available for a wide range of devices across OEMs are AOSP. Roms like CM, AOKP, PAC, Carbon, etc. are all AOSP roms.
Hope it helped.
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