I'm about to flash the Purekat v3.0 Rom. I'm now using new experience ROM with Percy cm#2 kernel(on SGY). I want to change to purekat with blackreactor cm version.
These is the step I will perform:
1.boot recovery (cwm)
2.flash kernel
3.reboot recovery
4.Under mounts and storage.
- Format data,system and cache
- Now mount system,data,cache.
5.Wipe data / factory reset
6.Wipe cache partition
7.Flash Rom zip. ( PureKAT 3.0)
8.Reboot system now
Are all of these steps correct?
I want to make sure these steps are correct to prevent any brick. Thanks.:laugh:
Related
I was on with Kingdroid V2.0 with S3 addon. Kernel Speedmod#3.3.
I flashed Criskelo V7 as follows- None of the steps belongs to me-All gathered from this forum, thanks to concerned member/s.
1- download AbyssNote kernel 4.2 (for CWM), Criskelo V7.ROM in SdCard
2- reboot to recovery mode and install AbyssNote V4.2 original touch
3- don't leave recovery , Go back to advanced then reboot recovery
NOW THIS IS TOUCH SCREEN ONLY (buttons will not work)
4- wipe data/factory reset…yes--delete all user data
5- wipe cache partition…yes--wipe cache
6- go to advanced and wipe dalvik Cache…yes--wipe dalvik cache
7- Go back
8- go mount and storage
9- format /cache…yes--format
10- format /system…yes--format
11- format /data…yes--format
12- Go back
Now Flash Criskelo V7 Rom
After installation completed, the phone automatically rebooted into CriskeloRom. Working Nice. About the Phone-Build Number IML74K.XXLQ3 Kernel [email protected]#3.Rom Version CriskeloRom Note ICSv07.
Now I would like to know whether shall I keep this kernel or flash kernel speedmod #3.3 over this kenel. suggestions are appriciated.
Ask the dev which kernel it is.
I think it probably is CF Root kernel.
I rooted the galaxy y, installed CWM, wiped cache and data..etc., installed a custom rom but the phone can't boot..stuck in bootscreen. I tried to change the kernel to CM kernel, and install a stable cm7, everything worked, but still no boot... what can I do?
what rom?
HnnnnnnnnmnHmmmmmmmmGpuuuuuuuuuuuuu
DeniablySam said:
what rom?
HnnnnnnnnmnHmmmmmmmmGpuuuuuuuuuuuuu
Click to expand...
Click to collapse
I've tried NukaRom V1.1.0 and CM7..happened the same..even with CM Kernel
Did you reboot to recovery after flashing kernel & mount system before flashing rom
Instructions to flash cm7
go to cwm
mount system
flash percy's cm #2 kernel
reboot to recovery
format system data cache
mount system data cache
flash cm7 zip
flash gapps (optional)
format data
restart
If you get bootloop remove sim card - if it boots change your stock rom firmware via odin
For stock based roms do as above but use a stock based kernel
marcussmith2626 said:
Did you reboot to recovery after flashing kernel & mount system before flashing rom
Instructions to flash cm7
go to cwm
mount system
flash percy's cm #2 kernel
reboot to recovery
format system data cache
mount system data cache
flash cm7 zip
flash gapps (optional)
format data
restart
If you get bootloop remove sim card - if it boots change your stock rom firmware via odin
For stock based roms do as above but use a stock based kernel
Click to expand...
Click to collapse
Thanks man! It works
I am a noob and just an android enthusiast. All the Galaxy Y roms I had used earlier were stock based. I decided to give Hyperion X a try and I followed the following steps for flashing-
1) Flashed stock ROM
2) Rooted the phone
3) Went into Samsung recovery. Flashed CWM 5.0.2.8
4) Mounted data sytem cache
5) Flashed ext4formatter
6) Without going back to cwm again directly flashed sir nvsetup's kernel
7)Then went back to cwm>advanced>reboot recovery
8) Then formatted data system cache
9) Wiped battery stats and dalvik cache
10) Mounted system data cache sdcard
11) Flashed Hyperion X
12) Flashed gapps
Every time I ended up on a bootloop ( I have tried flashing 4 times :crying: ) Please tell me where I went wrong.
For those who can't install the rom properly you can follow this guide:
-Flash Stock Rom via odin (If you're on stockrom skip this step)
-Flash CWM recovery using stock recovery (v.6.0.1.2 or 5.0.2.8)
-After flashing cwm recovery mount System,Data,Cache
-Flash Cm Specific Kernel
-After flashing cm kernel go back and mount System,Data,Cache
-Flash EXT4 formatter
-After flashing go to advance and recovery and REBOOT RECOVERY
-Now you're on the recovery again now mount System, Data,Cache
-Wipe S,D,C
-Mount S,D,C
-Flash the rom file or zip
-Go back Mount S,D,C
-Flash G-apps
-Reboot Now (Wait for it it takes time to boot the rom )
-Sorry for a long guide it's only for those who cannot understand the instructions given to flash the rom
Sent from my GT-S5360 using Tapatalk 2
I cant flash any custom ROM TWRP error: error executing updater binary in zip.
I try this TWRP:
TWRP 2.8.6.0
TWRP 2.8.7.0
I try this ROM:
Big ROM
Shell ROM
Gecko ROM
RECREATED REMIX STOCK
RECREATED REMIX STOCK BLUE
RECREATED REMIX METAMORFOSE
RECREATED REMIX [BLACK] LEOPARD
How fix this problem?
Solved! Use TWRP 2.8.7.0
How to:
1. reboot to recovery
2. wipe cache, dalvik cache, data, system
3. try flash custom ROM - NOT WORKING
4. restart recovery
5. wipe cache, dalvik cache, data, system
6. restart recovery (recovery say: no install supersu, swipe to install supersu)
7. flash custom ROM - WORKING
If I'd like to flash a new custom rom, what's the procedure?
Flash stock vendor, wipe system, data, cache + dalvik, flash rom + gapps?
uberstar100 said:
If I'd like to flash a new custom rom, what's the procedure?
Flash stock vendor, wipe system, data, cache + dalvik, flash rom + gapps?
Click to expand...
Click to collapse
A) when you are updating to a new build of same custom ROM, u can continue with 'dirty flash' : clear cache/Dalvik (Don’t WIPE data) » flash the ROM update files/ Add on zips » Clear Cache/Dalvik » Reboot system.
B) A 'clean flash' should be performed when you are changing to a NEW Custom ROM. The sequence: go to TWRP » Wipe / Factory reset » flash custom firmware and kernels(if any) » Flash the new Custom ROM zip files(GAPPs) » Clear Cache/Dalvik » Reboot system.
Good Luck!
bozka1 said:
A) when you are updating to a new build of same custom ROM, u can continue with 'dirty flash' : clear cache/Dalvik (Don’t WIPE data) » flash the ROM update files/ Add on zips » Clear Cache/Dalvik » Reboot system.
B) A 'clean flash' should be performed when you are changing to a NEW Custom ROM. The sequence: go to TWRP » Wipe / Factory reset » flash custom firmware and kernels(if any) » Flash the new Custom ROM zip files(GAPPs) » Clear Cache/Dalvik » Reboot system.
Good Luck!
Click to expand...
Click to collapse
Alright but don't ROMs usually modify the vendor partition? Also, my problem has already been done.