I got a simple question about flashing a rom, at this point its JellyTime.
I'm not really familiar with the order that you need to flash and if you need to flash the kernel separately?
My order is now:
- clean/wipe
- Flash ROM
- Flash gapps
- fastboot flash boot.img (is this step required, or does this already happen when flashing the ROM?)
Then the follow-up question is, does it affect the ROM when you boot the first time with an older kernel?
Spluh said:
I got a simple question about flashing a rom, at this point its JellyTime.
I'm not really familiar with the order that you need to flash and if you need to flash the kernel separately?
My order is now:
- clean/wipe
- Flash ROM
- Flash gapps
- fastboot flash boot.img (is this step required, or does this already happen when flashing the ROM?)
Then the follow-up question is, does it affect the ROM when you boot the first time with an older kernel?
Click to expand...
Click to collapse
You can flash the kernel basically anytime. I usually dirty flash kernels with no problem.
Also, no need to fastboot the boot.img. The rest of your order looks fine.
My order :
- format all partitions (except sdcard)
- wipe cache/dalvik
- Flash ROM
- Flash gapps
- fixing permissions
- Reboot
But i think your steps should be fine as well.
Sent from my Desire HD using xda premium
How do you fix permissions ?
When I flashed gapps I saw that in the end its fixing permissions. Do I need to something manually ?
Kobibo said:
How do you fix permissions ?
When I flashed gapps I saw that in the end its fixing permissions. Do I need to something manually ?
Click to expand...
Click to collapse
You can fix permissions using recoveries like 4ext and stuff...remember to wipe cache and davlik if you are flashing just kernel.
Like he said use recovery 4ext there's an option at "tools".
[ Sent from my HTC Desire HD using XDA-Premium App ]
RayRayX91 said:
My order :
- format all partitions (except sdcard)
- wipe cache/dalvik
- Flash ROM
- Flash gapps
- fixing permissions
- Reboot
But i think your steps should be fine as well.
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
Wiping cache+dalvik cache is redundant after formatting all partitions. A lot of people have this habit and recommend it, but its unnecessary. Dalvik-cache is located in the data partition. It's nothing special, its a folder there like any other, and contains classes.dex files for all apps on the device. When you format all partitions, data is formatted, so the dalvik-cache is wiped along with it. And the cache partition is formatted anyway. So wiping cache+dalvik again after formatting all partitions is of no use and unnecessary.
ai6908 said:
You can fix permissions using recoveries like 4ext and stuff...remember to wipe cache and davlik if you are flashing just kernel.
Click to expand...
Click to collapse
You don't need to wipe cache and dalvik after flashing a kernel. I used to do it too, but many times the devs themselves have said it isn't required. Lord Clockan said many times that wiping cache+dalvik is unnecessary after flashing a new kernel. When you think about it, it makes sense. Dalvik cache just contains classes.dex files for all the apps on the device and nothing else. When the dalvik-cache is rebuilt after a wipe, it pulls the classes.dex from each apk and puts it in the dalvik-cache folder (please correct me if I'm wrong). This isn't in any way related to the kernel and what it does. Regardless of the kernel flashed, the dalvik cache will remain the same. So it shouldn't make sense to wipe it for every kernel flash.
Sent from my Desire HD using xda premium
RayRayX91 said:
My order :
- format all partitions (except sdcard)
- wipe cache/dalvik
- Flash ROM
- Flash gapps
- fixing permissions
- Reboot
But i think your steps should be fine as well.
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
Hello, I did all of the steps in this order and ROM is booting OK. But after that I have random freezes while doing different tasks (taking picture, going to settings, after unlock). Do you have any suggestions what can I do/change to fix this. This is happening on all Jelly Time releases - i tried R3, R4, R5.1 and also AOKP V6. When I flash IcoColdSandwich everything is running without problem.
I will appreciate your help. Thank you!
My order :
- wipe data/factory reset
- wipe cache
- wipe dalvik
- Flash ROM
- Flash gapps
- fixing permissions
- Reboot
Thanks, that makes it clear.
So its possible that you flash the kernel when you are flashing the ROM!
Related
Hello there,
I was thinking to make a flashable CWM script that eliminates the necessary steps before changing a Rom. He script should have this content:
/format data
/format cache
/format system
/format Dalvik cache
Would it work? If yes has anyone such a similar script and share it please?
Thanks
First of all, wiping dalvik and system is redundant.
Wiping data wipes dalvik (/data/dalvik)
Also, when you flash a tom, it automatically wipes /system unless you're flashing an incremental update.
So why do you want this script when you have to push like 2 buttons anyway (factory reset/wipe data and cache)? The red be more trouble migrating to the flash able to wipe stuff than going to the wipe menu.
Sent from my Galaxy Nexus using Tapatalk 2
geoffcorey said:
Also, when you flash a tom, it automatically wipes /system unless you're flashing an incremental update.
Click to expand...
Click to collapse
no. the rom you're flashing has to have the script to wipe system (most do, but there are some that do not)
Zepius said:
no. the rom you're flashing has to have the script to wipe system (most do, but there are some that do not)
Click to expand...
Click to collapse
If it doesn't wipe system to install the rom, then I don't know what you think it would be installing....I would question that 'dev ' that does that.
Sent from my Nexus 7 using Tapatalk 2
Zepius said:
no. the rom you're flashing has to have the script to wipe system (most do, but there are some that do not)
Click to expand...
Click to collapse
If the ROM doesn't wipe /system, then most likely you're flashing an incremental upgrade, or the dev doesn't know what in the world he's doing and you should probably steer clear of said ROM.
Also, AFAIK, all the gnex ROMs here at xda, rootzwiki, and cyanogenmod wipe /system.
Sent from my Galaxy Nexus using Tapatalk 2
I understand the knowledge shared here but better be safe and follow all four steps then be not sure? Or not?
Can someone help by providing such script please?
Search for the Android Revolution ROM in the dev section. IIRC they have some kind of script in the OP
Anyone can pass Wipe Script Flashable ZIP me to flash (for Baked ROM)?
Thanks!!
There's no need to wipe until after you're done
Total newb question but on the CM10 thread they say:
Instructions:
First time flashing CyanogenMod 10 your device, or coming from another ROM?
Root the device and install ClockworkMod Recovery. Instructions are available here.
Perform a NANDroid backup of your current ROM.
Format the system, data & cache partitions of your device.
Perform a factory reset.
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Click to expand...
Click to collapse
.... they don't say how to flash if you are upgrading.
Some in the thread say that they just "dirty flash" it.
What exactly is a "dirty flash"?
oshax said:
Total newb question but on the CM10 thread they say:
Instructions:
First time flashing CyanogenMod 10 your device, or coming from another ROM?
Root the device and install ClockworkMod Recovery. Instructions are available here.
Perform a NANDroid backup of your current ROM.
Format the system, data & cache partitions of your device.
Perform a factory reset.
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
.... they don't say how to flash if you are upgrading.
Some in the thread say that they just "dirty flash" it.
What exactly is a "dirty flash"?
Click to expand...
Click to collapse
dirty flash means you didnt wipe data/cache.
most of the time, you can dirty flash newer versions of the same rom over the older version of the rom you have.
HOWEVER, if you have problems, you need to wipe data/cache and reflash the rom completely
Zepius said:
dirty flash means you didnt wipe data/cache.
most of the time, you can dirty flash newer versions of the same rom over the older version of the rom you have.
HOWEVER, if you have problems, you need to wipe data/cache and reflash the rom completely
Click to expand...
Click to collapse
Guess I might as well wipe the cache and dalvik even on a dirty flash?
Thanks
I upgraded from CM10 M1 to M2 with only a wipe of Dalvik cache. Works fine.
I finished installing M2 after wiping both the cache and dalvik cache (figured I would do the cache just in case).
Worked great!
Thanks all
oshax said:
Total newb question but on the CM10 thread they say:
Instructions:
.... they don't say how to flash if you are upgrading.
Some in the thread say that they just "dirty flash" it.
What exactly is a "dirty flash"?
Click to expand...
Click to collapse
***what Nexus version do you have?*** i've used the below instructions with GSM GNex***
If you're coming from an AOSP CM9 rom, Do the following :
Download Maguro (or your models ROM+Gappsl).
- boot into recovery.
- Preform NANDroid Backup.
- Wipe Dalvik cache.
- Wipe Factory reset.
- Wipe Cache.
- install zip from SDcard>choose zip from SDcard>ROM.zip (your ROM)
- Flash Gapps.zip
- Flash kernel.zip (if you have one)
- go to Advanced> Fix Permissions
- Reboot system now !
- Enjoy.
***I've used this method for a trillion flashes !***
No need to wipe anything when updating nightlies. Like it was said before, wipe data and reflash when you face problems.
Sent from my i9250
bk201doesntexist said:
No need to wipe anything when updating nightlies. Like it was said before, wipe data and reflash when you face problems.
Sent from my i9250
Click to expand...
Click to collapse
+1
Just like the title suggests, which KT747 kernal is compatible with CM10? Every time I flash the kernel my phone wont boot and I have to restore from a backup. I am currently on CM10-10/22 build 10827 and the KT747 kernel I am trying is the AOSP-JB-ATT-10-22-2012. I do have a ATT Galaxy S3 so I would assume that this should work?
Thanks for everyone's time!
Zehel
There is a version for pre 10-14 CM10 and one for after.
After you flash your ROM be sure to fully boot your device into android then go back into recovery again and then flash kt747 , then wipe cache+dalvik +fix permission . Reboot
Sent from my SGH-I747
Ah! Fix permissions could be a huge part of the problem. Let me try that and see if that fixes my problem. Also, maybe I am blind but I can't seem to find the one for CM. Is there a separate thread for the CM Kernel or is it in the thread by Ktoonsez?
Thanks again,
ZS
ZehelSitchel said:
Ah! Fix permissions could be a huge part of the problem. Let me try that and see if that fixes my problem. Also, maybe I am blind but I can't seem to find the one for CM. Is there a separate thread for the CM Kernel or is it in the thread by Ktoonsez?
Thanks again,
ZS
Click to expand...
Click to collapse
CM10 is an AOSP rom.
That makes crash822's post make sense. Thank you all for your help. I now have it working! Let the amazingness commence!
ZS
You checked "yes this is a question"
Guess where it belongs?
Moved to Q&A
FNM
ZehelSitchel said:
That makes crash822's post make sense. Thank you all for your help. I now have it working! Let the amazingness commence!
ZS
Click to expand...
Click to collapse
Hey man, do you mind sharing what you did to make the kernel work?
I have almost the same issue as you did before, and tried everything I know (including reflectingod's method), still doesn't work at all.
dingrn said:
Hey man, do you mind sharing what you did to make the kernel work?
I have almost the same issue as you did before, and tried everything I know (including reflectingod's method), still doesn't work at all.
Click to expand...
Click to collapse
Did you use the ktweaker app that installs automaticaly and turn on options from there.
Sent from my SGH-I747M using xda premium
ragzdincs said:
Did you use the ktweaker app that installs automaticaly and turn on options from there.
Sent from my SGH-I747M using xda premium
Click to expand...
Click to collapse
Well, to be more specific, KT747 kernel doesn't work at all on my GS3. I am using ATT variant i747, with task's AOKP ROM. I followed the full wipe -> ROM -> gapp -> kernel steps strictly, and was sure using the post-1014-JB kernel to pair with 1022 AOKP release, But still, my phone is suffering random hot reboot, black screen, system process are terminated randomly, and any opened apps will be closed within mins. Yes, I have cache/dalvik wiped after flashing the kernel, and permissions are fixed. I also tried to flash ROM first, then log on to system, then flash kernel, makes no difference. I really don't have a clue why KT747 kernel doesn't work on my phone, any suggestion is welcome.
I would suggest you to do a complete clean installation:
1. Wipe data
2. Wipe Cache
3. Wipe dalvik
4. Format /system
5. Format / data
6. Format / cache
7. Reboot recovery
8. Wipe data
9. Wipe Cache
10. Wipe dalvik
11. Mount /System
12. Install Rom
13. Install Gapp
14. Fix permission
15. Reboot & Setup your phone
16. Install Kernel
17. Wipe Cache
18. Wipe dalvik
19. Fix permission
It should be fine then.
noahattic said:
I would suggest you to do a complete clean installation:
1. Wipe data
2. Wipe Cache
3. Wipe dalvik
4. Format /system
5. Format / data
6. Format / cache
7. Reboot recovery
8. Wipe data
9. Wipe Cache
10. Wipe dalvik
11. Mount /System
12. Install Rom
13. Install Gapp
14. Fix permission
15. Reboot & Setup your phone
16. Install Kernel
17. Wipe Cache
18. Wipe dalvik
19. Fix permission
It should be fine then.
Click to expand...
Click to collapse
Thanks man, I will give this "full steps" a try. Hope it would work.
dingrn said:
Well, to be more specific, KT747 kernel doesn't work at all on my GS3. I am using ATT variant i747, with task's AOKP ROM. I followed the full wipe -> ROM -> gapp -> kernel steps strictly, and was sure using the post-1014-JB kernel to pair with 1022 AOKP release, But still, my phone is suffering random hot reboot, black screen, system process are terminated randomly, and any opened apps will be closed within mins. Yes, I have cache/dalvik wiped after flashing the kernel, and permissions are fixed. I also tried to flash ROM first, then log on to system, then flash kernel, makes no difference. I really don't have a clue why KT747 kernel doesn't work on my phone, any suggestion is welcome.
Click to expand...
Click to collapse
Rom is supposed to be flashed first. If you don't it overwrites the kernel with the one pre-loaded on with the Rom.Otherwise follow everyone else's instructions >Cache/Dalvik/FixPerms after flash. Go into settings and see that the kernel is there. Good luck
What is this?
Recovery flashable cache, Dalvik, and data wiping tools.
Why?
The script that wipes data should help prevent the problems experienced when different recoveries wipe data differently and with different options to choose from.
(Those that have typed in "YES" when wiping data know what I mean)
Why are there two?
One wipes cache & Dalvik.
One wipes cache, Dalvik, and data.
What data is wiped?
The data that is wiped should be all that is required for flashing ROMs (see below).
Media (your pics, music, etc) will not be deleted.
Feedback
Feedback from users that flash a lot of different ROMs (especially both TW and source built) will be useful in case there are any additional files and folders that need to be wiped.
Usage:
As always, flash at your own risk!
Flash in recovery
(these are most useful when using a recovery like TWRP where multiple zips can be queued for flashing)
A typical queue might be something like this:
1) Cache, Dalvik, and Data wiping tool
2) ROM
3) loki-doki
In case any devs want to add this to their ROM updater-script (most likely for an Aroma package), this is the code for the data wipe:
Code:
delete_recursive("/data/app");
delete_recursive("/data/app-asec");
delete_recursive("/data/app-lib");
delete_recursive("/data/app-private");
delete_recursive("/data/backup");
delete_recursive("/data/clipboard");
delete_recursive("/data/data");
delete_recursive("/data/drm");
delete_recursive("/data/log");
delete_recursive("/data/misc");
delete_recursive("/data/property");
delete_recursive("/data/system");
delete_recursive("/data/time");
delete_recursive("/data/user");
Download
Wipe_Cache_Dalvik_SGS4_v1.0
Wipe_Cache_Dalvik_Data_SGS4_v1.0
Wipe_Cache_Dalvik_Data_System_SGS4_v1.0
Thank you for this :good: what about formatting system though? Formatting system before a rom flash has solved many problems for me.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Planktron said:
Thank you for this :good: what about formatting system though? Formatting system before a rom flash has solved many problems for me.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
It would be redundant since all devs should format system in their install script.
Finally. :thumbup:
Sent from my SAMSUNG-SGH-I337 using xda premium
I have been meaning to thank you for this - I have used it a number of times already and found it to be very helpful. I am on OUDHS recovery - and while it would be better in some ways if I had TWRP because you can setup multiple files for flashing - it is still a big time saving tool when flashing any rom, update, kernel or theme on OUDHS/CWM. ANd it works beautifully.
I assume that I still need to wipe system when I want to do a totally CLEAN Flash - is that correct? If so - any thought of creating a third file that Wipes Data/Wipes System/Clears Cache and Clears Delvic Cache?
Or do you feel that is not needed?
Lol probably will implement this into my ROM once I put Aroma into it, if that's okay?
lol I love that part about "YES" i've seen too many users wipe their whole partiton and TWRP not be able to create one again (idk why) and then bootloops galore.
mocsab said:
I have been meaning to thank you for this - I have used it a number of times already and found it to be very helpful. I am on OUDHS recovery - and while it would be better in some ways if I had TWRP because you can setup multiple files for flashing - it is still a big time saving tool when flashing any rom, update, kernel or theme on OUDHS/CWM. ANd it works beautifully.
I assume that I still need to wipe system when I want to do a totally CLEAN Flash - is that correct? If so - any thought of creating a third file that Wipes Data/Wipes System/Clears Cache and Clears Delvic Cache?
Or do you feel that is not needed?
Click to expand...
Click to collapse
If devs are coding their install scripts properly, there is no need to wipe system (as I mentioned earlier with formatting system).
But...maybe I should make one just in case.
jetlitheone said:
Lol probably will implement this into my ROM once I put Aroma into it, if that's okay?
lol I love that part about "YES" i've seen too many users wipe their whole partiton and TWRP not be able to create one again (idk why) and then bootloops galore.
Click to expand...
Click to collapse
Absolutely you may use it. That's why I included the code.
Added zip to OP that will also format /system.
I wanted to thank you again for this tool - it has really been very useful and has saved me a ton of time and steps when flashing new roms and updates. Thanks - BIG TIME!
Hi,
When i tried flashing a custom rom and a custom kernel it just gives me black screen after starting up again maybe you guys have got the same problem before and what did you do to solve this issue? I tried these custom rom/custom kernel combinations :
FreedomOS-op3-nevax-1.7-CE-signed / blu_spark_r114-OOS-6.0.1 thulium
FreedomOS-op3-nevax-1.7-CE-signed / ElementalX-OP3-0.23
ResurrectionRemix-M-v5.7.2-20160804-oneplus3 / blu_spark_r114-OOS-6.0.1_thulium_e476ded
ResurrectionRemix-M-v5.7.2-20160804-oneplus3 / ElementalX-OP3-0.23
My TWRP version is 3.2.1 official
These are one of the many methods i tried:
Method 1
1. Wipe Cache, Data, Internal storage, Dalvik/art cache and system.
2. Flash Custom Rom.
3. Wipe cache, Dalvik/art cache.
4. Flash Custom Kernel.
5. Reboot.
Method 2
1. Wipe Cache, Data, Internal storage, Dalvik/art cache and system.
2. Flash Custom Rom.
3. Flash Custom Kernel.
4. Wipe cache, Dalvik/art cache.
Method 3
1. Wipe Cache, Data, Internal storage, Dalvik/art cache and system.
2. Flash Custom Rom.
3. Flash Custom Kernel.
These are some of the combinations i tried and even some of the methods i tried are nonsens but i am just trying to get it to work. If you need any more information just tell me . Help is very much appreciated .
3.5.2 base dont work with custom kernel yet. The twrp Version is a non known at my End. I think you better read this forum. From A to Z. Since all your awnsers can be found easy.
Saqrez said:
Hi,
When i tried flashing a custom rom and a custom kernel it just gives me black screen after starting up again maybe you guys have got the same problem before and what did you do to solve this issue? I tried these custom rom/custom kernel combinations :
FreedomOS-op3-nevax-1.7-CE-signed / blu_spark_r114-OOS-6.0.1 thulium
FreedomOS-op3-nevax-1.7-CE-signed / ElementalX-OP3-0.23
ResurrectionRemix-M-v5.7.2-20160804-oneplus3 / blu_spark_r114-OOS-6.0.1_thulium_e476ded
ResurrectionRemix-M-v5.7.2-20160804-oneplus3 / ElementalX-OP3-0.23
My TWRP version is 3.2.1 official
These are one of the many methods i tried:
Method 1
1. Wipe Cache, Data, Internal storage, Dalvik/art cache and system.
2. Flash Custom Rom.
3. Wipe cache, Dalvik/art cache.
4. Flash Custom Kernel.
5. Reboot.
Method 2
1. Wipe Cache, Data, Internal storage, Dalvik/art cache and system.
2. Flash Custom Rom.
3. Flash Custom Kernel.
4. Wipe cache, Dalvik/art cache.
Method 3
1. Wipe Cache, Data, Internal storage, Dalvik/art cache and system.
2. Flash Custom Rom.
3. Flash Custom Kernel.
These are some of the combinations i tried and even some of the methods i tried are nonsens but i am just trying to get it to work. If you need any more information just tell me . Help is very much appreciated .
Click to expand...
Click to collapse
try to flash supersu after the rom, reboot to system. Reboot back to recovery and flash kernel
otonieru said:
try to flash supersu after the rom, reboot to system. Reboot back to recovery and flash kernel
Click to expand...
Click to collapse
I didn't flash SuperSU as it is pre installed..
Darkje said:
3.5.2 base dont work with custom kernel yet. The twrp Version is a non known at my End. I think you better read this forum. From A to Z. Since all your awnsers can be found easy.
Click to expand...
Click to collapse
3.5.2 base? Can you please explain it a little bit more detailed thank you and i already read alot and can't find it thats why i made a thread.
Please read the freedom os topic. It address well why you cannot Flash a custom kernel. It is simply that kernel sources for Version 1.7 (aka 3.5.2 base) are not releases.
Darkje said:
Please read the freedom os topic. It address well why you cannot Flash a custom kernel. It is simply that kernel sources for Version 1.7 (aka 3.5.2 base) are not releases.
Click to expand...
Click to collapse
Oh i see any other idea for doing this with a different freedom os or something
Saqrez said:
Oh i see any other idea for doing this with a different freedom os or something
Click to expand...
Click to collapse
As suggested earlier try reading some ROM threads, going around flashing ROMs and kernels with no purpose is going to get you a soft brick very quickly.
My suggestion decide what you need out of a ROM, that is missing from stock, read a few rom threads to identify one that fills your needs. Then when you've got a ROM in mind go back and read the thread THOROUGHLY before flashing, had you done this with FreedomOS you wouldn't be here now.