NOTE: BEWARE OF GREMLINS! Just because this worked for me, does not mean it will for you. Proceed at own risk! I am not responsible for anything that happens to your phone if you use this guide!
What you will need (to boot TW ROMS):
A rooted galaxy s2 sgh-i777 running stock Android 4.1.2
ClockworkMod Recovery
Cook's safe pre-load ROM wipe
Jeeboo kernel
A TW galaxy s2 sgh-i9100 ROM
What you will need (to boot AOSP ROMS):
WARNING! I HAVE NOT TESTED THIS! TEST AT OWN RISK!
A rooted galaxy s2 sgh-i777 running stock Android 4.1.2
ClockworkMod Recovery
Cook's pre-load ROM wipe
Shift Kernel (use the one for whichever Android version you're going to)
An AOSP sgh-i9100 galaxy s2 ROM
The Procedure (for booting TW ROMS):
Boot into clockworkmod recovery
Make a Nandroid backup
Flash Cook's safe pre-load ROM wipe .zip file
Flash ROM (I used WizzedKat ROM v3)
Flash jeeboo kernel
Reboot
Done! Enjoy Android 4.4.2 kit kat (if you flashed WizzedKat)
The Procedure (for booting AOSP ROMS):
Again, I HAVE NOT TESTED THIS!
Boot to clockworkmod recovery
Make a Nandroid backup
Flash Cook's pre-load ROM wipe .zip file
Flash ROM
Flash shift kernel
Reboot and pray your phone boots up because...surprise! I haven't tested this so I am not sure if it works or not.
How to Get Back to Stock:
So you've booted a ROM, played with it, and now you want to go back to stock ROM...no problem! Here's how:
Boot into clockworkmod recovery
Flash Cook's safe pre-load ROM wipe if coming from TW. Flash Cook's pre-load ROM wipe if coming from AOSP
Restore your Nandroid backup (if you made one)
*OPTIONAL* Flash jeeboo kernel or AJ kernel (both work with the stock ROM on the i777)
Reboot
Known Bugs
After rebooting back to stock, your baseband version might still say whatever it was while you were on the ROM you just were on and your phone may act funny when trying to make a call.
To fix this you will need to flash the stock MD8 Odin .tar file in mobile odin OVER your Nandroid backup you just restored. You can probably use Odin for the PC as well. This should NOT affect anything as far as apps and personal data goes, however you will have to reroot using the framaroot app and reflash clockworkmod recovery as well.
Happy flashing!
StoneyJSG said:
NOTE: BEWARE OF GREMLINS! Just because this worked for me, does not mean it will for you. Proceed at own risk! I am not responsible for anything that happens to your phone if you use this guide!
What you will need (to boot TW ROMS):
A rooted galaxy s2 sgh-i777 running stock Android 4.1.2
ClockworkMod Recovery
Cook's safe pre-load ROM wipe
Jeeboo kernel
A TW galaxy s2 sgh-i9100 ROM
What you will need (to boot AOSP ROMS):
WARNING! I HAVE NOT TESTED THIS! TEST AT OWN RISK!
A rooted galaxy s2 sgh-i777 running stock Android 4.1.2
ClockworkMod Recovery
Cook's pre-load ROM wipe
Shift Kernel (use the one for whichever Android version you're going to)
An AOSP sgh-i9100 galaxy s2 ROM
The Procedure (for booting TW ROMS):
Boot into clockworkmod recovery
Make a Nandroid backup
Flash Cook's safe pre-load ROM wipe .zip file
Flash ROM (I used WizzedKat ROM v3)
Flash jeeboo kernel
Reboot
Done! Enjoy Android 4.4.2 kit kat (if you flashed WizzedKat)
The Procedure (for booting AOSP ROMS):
Again, I HAVE NOT TESTED THIS!
Boot to clockworkmod recovery
Make a Nandroid backup
Flash Cook's pre-load ROM wipe .zip file
Flash ROM
Flash shift kernel
Reboot and pray your phone boots up because...surprise! I haven't tested this so I am not sure if it works or not.
How to Get Back to Stock:
So you've booted a ROM, played with it, and now you want to go back to stock ROM...no problem! Here's how:
Boot into clockworkmod recovery
Flash Cook's safe pre-load ROM wipe if coming from TW. Flash Cook's pre-load ROM wipe if coming from AOSP
Restore your Nandroid backup (if you made one)
*OPTIONAL* Flash jeeboo kernel or AJ kernel (both work with the stock ROM on the i777)
Reboot
Known Bugs
After rebooting back to stock, your baseband version might still say whatever it was while you were on the ROM you just were on and your phone may act funny when trying to make a call.
To fix this you will need to flash the stock MD8 Odin .tar file in mobile odin OVER your Nandroid backup you just restored. You can probably use Odin for the PC as well. This should NOT affect anything as far as apps and personal data goes, however you will have to reroot using the framaroot app and reflash clockworkmod recovery as well.
Happy flashing!
Click to expand...
Click to collapse
I'm lost. Are there any i900 roms able to flash to a sigh 777?
Tmobilefan906 said:
I'm lost. Are there any i900 roms able to flash to a sigh 777?
Click to expand...
Click to collapse
Yes, any i9100 touch wiz based ROM will work using the method above. I booted wizzedKat rom just fine. As for AOSP based roms, they should work but I haven't tried it so boot them at your own risk.
StoneyJSG said:
Yes, any i9100 touch wiz based ROM will work using the method above. I booted wizzedKat rom just fine. As for AOSP based roms, they should work but I haven't tried it so boot them at your own risk.
Click to expand...
Click to collapse
I have an issue. Idk of its battery or something else. I get a quick glance of charge icon and it goes out. I tried plugging in device without a battery, and the soft keys and screen flickers. Any thoughts?
StoneyJSG said:
Yes, any i9100 touch wiz based ROM will work using the method above. I booted wizzedKat rom just fine. As for AOSP based roms, they should work but I haven't tried it so boot them at your own risk.
Click to expand...
Click to collapse
I got Wizzedkat to work.
---------- Post added at 04:27 PM ---------- Previous post was at 04:26 PM ----------
Tmobilefan906 said:
I have an issue. Idk of its battery or something else. I get a quick glance of charge icon and it goes out. I tried plugging in device without a battery, and the soft keys and screen flickers. Any thoughts?
Click to expand...
Click to collapse
But I came from gingerbread and not 4.1.2
Tmobilefan906 said:
I got Wizzedkat to work.
---------- Post added at 04:27 PM ---------- Previous post was at 04:26 PM ----------
But I came from gingerbread and not 4.1.2
Click to expand...
Click to collapse
That is odd, the battery thing didn't happen to me, of course I came from Android 4.1.2 and that might be it. Restore your nandroid back up and then take the OTA to 4.1.2 jelly bean on the MD8 bootloader. You might also have to flash the 4.1.2 ODIN tar file if your phone acts funny after taking the OTA or restoring the nandroid, which may or may not wipe all your data, it didn't wipe mine and I used the mobile odin app. Do not take the OTA to 4.1.2 on the MD9 bootloader, if you do then i9100 roms may not work as I haven't tested it on that bootloader. Once you are on 4.1.2 , follow my guide above again to boot wizzed kat or any other i9100 touch whiz rom. It should fully work then, if it doesn't then I'm at a stalemate.
StoneyJSG said:
That is odd, the battery thing didn't happen to me, of course I came from Android 4.1.2 and that might be it. Restore your nandroid back up and then take the OTA to 4.1.2 jelly bean on the MD8 bootloader. You might also have to flash the 4.1.2 ODIN tar file if your phone acts funny after taking the OTA or restoring the nandroid, which may or may not wipe all your data, it didn't wipe mine and I used the mobile odin app. Do not take the OTA to 4.1.2 on the MD9 bootloader, if you do then i9100 roms may not work as I haven't tested it on that bootloader. Once you are on 4.1.2 , follow my guide above again to boot wizzed kat or any other i9100 touch whiz rom. It should fully work then, if it doesn't then I'm at a stalemate.
Click to expand...
Click to collapse
I put the metal ends of battery on my enclosed note 3 charger for a couple secs. Gave it a lil boost. I flashed GB firmware to it, then rooted it via max Lee's method. Now running wickedkatt rom!
StoneyJSG said:
That is odd, the battery thing didn't happen to me, of course I came from Android 4.1.2 and that might be it. Restore your nandroid back up and then take the OTA to 4.1.2 jelly bean on the MD8 bootloader. You might also have to flash the 4.1.2 ODIN tar file if your phone acts funny after taking the OTA or restoring the nandroid, which may or may not wipe all your data, it didn't wipe mine and I used the mobile odin app. Do not take the OTA to 4.1.2 on the MD9 bootloader, if you do then i9100 roms may not work as I haven't tested it on that bootloader. Once you are on 4.1.2 , follow my guide above again to boot wizzed kat or any other i9100 touch whiz rom. It should fully work then, if it doesn't then I'm at a stalemate.
Click to expand...
Click to collapse
The battery was "dead" lol. It's gonna need a new one eventually.
StoneyJSG said:
That is odd, the battery thing didn't happen to me, of course I came from Android 4.1.2 and that might be it. Restore your nandroid back up and then take the OTA to 4.1.2 jelly bean on the MD8 bootloader. You might also have to flash the 4.1.2 ODIN tar file if your phone acts funny after taking the OTA or restoring the nandroid, which may or may not wipe all your data, it didn't wipe mine and I used the mobile odin app. Do not take the OTA to 4.1.2 on the MD9 bootloader, if you do then i9100 roms may not work as I haven't tested it on that bootloader. Once you are on 4.1.2 , follow my guide above again to boot wizzed kat or any other i9100 touch whiz rom. It should fully work then, if it doesn't then I'm at a stalemate.
Click to expand...
Click to collapse
When I go to make back up, just the icon of top hat stays on. If I tap power button, it goes back to main menu. Any ideas? It's cwm 5.0.4
StoneyJSG said:
That is odd, the battery thing didn't happen to me, of course I came from Android 4.1.2 and that might be it. Restore your nandroid back up and then take the OTA to 4.1.2 jelly bean on the MD8 bootloader. You might also have to flash the 4.1.2 ODIN tar file if your phone acts funny after taking the OTA or restoring the nandroid, which may or may not wipe all your data, it didn't wipe mine and I used the mobile odin app. Do not take the OTA to 4.1.2 on the MD9 bootloader, if you do then i9100 roms may not work as I haven't tested it on that bootloader. Once you are on 4.1.2 , follow my guide above again to boot wizzed kat or any other i9100 touch whiz rom. It should fully work then, if it doesn't then I'm at a stalemate.
Click to expand...
Click to collapse
How can I update my recovery? I know that with this device, kernels come with recovery. Which do u recommend? I love twrp, but will use cwm if that is all that is available.
---------- Post added at 11:18 PM ---------- Previous post was at 10:52 PM ----------
StoneyJSG said:
That is odd, the battery thing didn't happen to me, of course I came from Android 4.1.2 and that might be it. Restore your nandroid back up and then take the OTA to 4.1.2 jelly bean on the MD8 bootloader. You might also have to flash the 4.1.2 ODIN tar file if your phone acts funny after taking the OTA or restoring the nandroid, which may or may not wipe all your data, it didn't wipe mine and I used the mobile odin app. Do not take the OTA to 4.1.2 on the MD9 bootloader, if you do then i9100 roms may not work as I haven't tested it on that bootloader. Once you are on 4.1.2 , follow my guide above again to boot wizzed kat or any other i9100 touch whiz rom. It should fully work then, if it doesn't then I'm at a stalemate.
Click to expand...
Click to collapse
Also, when I open Stweaks it says no kernel support. Odd...it should...jeebo kernel was flashed.
Are u gonna maintain this thread or not?
Tmobilefan906 said:
How can I update my recovery? I know that with this device, kernels come with recovery. Which do u recommend? I love twrp, but will use cwm if that is all that is available.
---------- Post added at 11:18 PM ---------- Previous post was at 10:52 PM ----------
Also, when I open Stweaks it says no kernel support. Odd...it should...jeebo kernel was flashed.
Click to expand...
Click to collapse
I flash jeebo kernel and AJ kernel back and forth with my s2 on Android 4.1.2 which both have CWM recovery. Stweaks may not work with jeebo kernel, it might work wth shift kernel, but I am not sure shift kernel works with wizzed kat rom. I do know stweaks works with AJ kernel on 4.1.2 and siyah kernel if you're on Android 4.0.x
Tmobilefan906 said:
When I go to make back up, just the icon of top hat stays on. If I tap power button, it goes back to main menu. Any ideas? It's cwm 5.0.4
Click to expand...
Click to collapse
I'm not sure what's causing this. Try going to google play and getting the flashify and nandroid manager apps. These will let you back up and manage your backups from Android without having to boot to recovery.
StoneyJSG said:
I flash jeebo kernel and AJ kernel back and forth with my s2 on Android 4.1.2 which both have CWM recovery. Stweaks may not work with jeebo kernel, it might work wth shift kernel, but I am not sure shift kernel works with wizzed kat rom. I do know stweaks works with AJ kernel on 4.1.2 and siyah kernel if you're on Android 4.0.x
Click to expand...
Click to collapse
Now, when u say on a certain android version, do u mean the phones bootloader or the actual roms android version?
---------- Post added at 11:32 PM ---------- Previous post was at 11:31 PM ----------
StoneyJSG said:
I'm not sure what's causing this. Try going to google play and getting the flashify and nandroid manager apps. These will let you back up and manage your backups from Android without having to boot to recovery.
Click to expand...
Click to collapse
I went ahead and installed an SD card. Now it will back up.
StoneyJSG said:
I'm not sure what's causing this. Try going to google play and getting the flashify and nandroid manager apps. These will let you back up and manage your backups from Android without having to boot to recovery.
Click to expand...
Click to collapse
?android version of rom, or device's bootloader version?
Tmobilefan906 said:
Now, when u say on a certain android version, do u mean the phones bootloader or the actual roms android version?
---------- Post added at 11:32 PM ---------- Previous post was at 11:31 PM ----------
I went ahead and installed an SD card. Now it will back up.
Click to expand...
Click to collapse
Actual ROM version. Ah yes putting in an SD card would be the fix. Thought you had one already. Looks like you're good to go now.
StoneyJSG said:
Actual ROM version. Ah yes putting in an SD card would be the fix. Thought you had one already. Looks like you're good to go now.
Click to expand...
Click to collapse
U familiar with partitioning? I have a i777 with a gt9100 rom.
Tmobilefan906 said:
U familiar with partitioning? I have a i777 with a gt9100 rom.
Click to expand...
Click to collapse
No I have never ventured down that avenue before, been meaning to. There's a thread on it though here somewhere in the i777 forum.
StoneyJSG said:
No I have never ventured down that avenue before, been meaning to. There's a thread on it though here somewhere in the i777 forum.
Click to expand...
Click to collapse
I tried it with Wizzedkat rom, stock rom and it doesn't work. I know that when u flash a recovery a kernel comes with it. I flash twrp or cwm, and my device doesn't boot back up. I'm so frustrated!ugh.
Tmobilefan906 said:
I tried it with Wizzedkat rom, stock rom and it doesn't work. I know that when u flash a recovery a kernel comes with it. I flash twrp or cwm, and my device doesn't boot back up. I'm so frustrated!ugh.
Click to expand...
Click to collapse
Hmm odd. Can you get into download mode? You might can use ODIN to flash the Android 4.1.2 stock MD8 firmware tar file which will flash over anything you currently have.
Related
hi guys, first post
ive had my rooted galaxy s2 with the latest siyah kernel 3.3.2, i had cwm recover 5 and rom manager
i tried to flash cyanogen mod through rom manager, following the steps it gave me, i downloaded the files through rom manager and went through all the prompts till i clicked agee to go into recovery mode.
once it did that the phone shut off but would not turn on again so i went to turn on manually, it loads the samsung galaxy screen with the yellow triangle but goes straight into a white flashing screen.
Ive tried taking the battery out, leaving it and putting it back in again, still a flashing screen,
check what i9100 you have and download correct cm9.
using cwm format data system cacha sdcard dalvik
flash cm9 using cwm
rommanager doesnt work on GS2
atifsh said:
check what i9100 you have and download correct cm9.
using cwm format data system cacha sdcard dalvik
flash cm9 using cwm
rommanager doesnt work on GS2
Click to expand...
Click to collapse
i have the international 19100T
ahh rats i should have known rom manager does not work, , im just stuck in a white flash screen on boot up, cant get to cwm, although i can get into odin
would reflashing my kernel on odin get me through? everything is back up onto my sd card.
Try flashing a kernel first, and if that doesn't work, flash a rom in Odin, re-root your phone & restore your backup. But yeah, don't use Rom Manager with a kernel that has CWRecovery. One or the other. Rom Manager has a habit of doing stuff like what's happened to you on SGS2's which also have CWRecovery installed.
MistahBungle said:
Try flashing a kernel first, and if that doesn't work, flash a rom in Odin, re-root your phone & restore your backup. But yeah, don't use Rom Manager with a kernel that has CWRecovery. One or the other. Rom Manager has a habit of doing stuff like what's happened to you on SGS2's which also have CWRecovery installed.
Click to expand...
Click to collapse
awesome, I tried flashing the latest siyah kernel, the one that i already had on my phone before the problems, that didn't do anything to get me through, any suggestions on which kernel/rom to flash?
because you are on siyah and im not comfortable with that, please flash a stock kernel or cfroot kernel and format system data partitions after that.
now flash any official stock ICS or GB rom using Odin.
atifsh said:
because you are on siyah and im not comfortable with that, please flash a stock kernel or cfroot kernel and format system data partitions after that.
now flash any official stock ICS or GB rom using Odin.
Click to expand...
Click to collapse
ohh sweet baby jesus im i flashed a cf kernel and now im into cwm on 4.0.1.5, can i just normal reboot my phone now?
No need to format anything. Given you want to use CM9, I'd recommend you flash CM9 Resurrection Edition in Odin, put the latest CM9 nightly & Gapps on your internal/external SD card then flash that nightly & Gapps in CWM (read the first page of the CM9 discussion thread thoroughly & follow the instructions to the letter. From there you can stick with the CM9 stock kernel or flash whatever other kernel you want to use (provided it's CM9 compatible).
From then on, if you want to flash CM9 nightlies, do it via CWM/CWRecovery, just don't use Rom Manager this time I use CM9 as well & I have it frozen because I use Siyah (which has CWM).
MistahBungle said:
No need to format anything. Given you want to use CM9, I'd recommend you flash CM9 Resurrection Edition in Odin, put the latest CM9 nightly & Gapps on your internal/external SD card then flash that nightly & Gapps in CWM (read the first page of the CM9 discussion thread thoroughly & follow the instructions to the letter. From there you can stick with the CM9 stock kernel or flash whatever other kernel you want to use (provided it's CM9 compatible).
Click to expand...
Click to collapse
alrighty! thanks for the info, is cf kernel compatible with cm9? i want to just have one kernel that'll handle most roms, any suggestions?
ive reloaded my old stable phone version, the version i saved before trying to flash cyanogen mod with rom manager, this version has siyah and stock rom, back to square one *phew*
i still say wipe first, cm9 will come with its own latest cwm that can be used to flash any custom roms after.
flashing via odin version is easy and fool proof as it has everything bundled for correct working of cm9.
If you flash CM9 the CM9 kernel will overwrite/replace your CFRoot kernel, which is fine. As I said in my previous post you can stick with that if you're happy with it, or you can flash any other kernel that's CM9 compatible.
No suggestions/recommendations. Because your experience will not be the same as someone else's using a given rom or kernel. If you want to go down that path, try some kernels to find one you like. To see if a kernel is compatible with CM9, read the the dev thread devoted to the kernel in question.
OK. Given you're back @ square one, Atifsh is right when he says flashing the Resurrection version (Odin version) then flashing Gapps/nightly from there is probably a good way to go for you. Once you've done that, you'll be able to flash CM9 nightlies via CWRecovery. As said previously, read that first page of the CM9 discussion thread/instructions thoroughly before you do anything.
keegan25 said:
alrighty! thanks for the info, is cf kernel compatible with cm9? i want to just have one kernel that'll handle most roms, any suggestions?
ive reloaded my old stable phone version, the version i saved before trying to flash cyanogen mod with rom manager, this version has siyah and stock rom, back to square one *phew*
Click to expand...
Click to collapse
Something similar happened to me too. I flashed stock XWLPG, then siyah 3.3.2 and did a factory reset. After that, got stuck in a flashing white screen after the yellow triangle.
What I did: boot on download mode, flash XWLPG over PC Odin once more, did a full wipe BEFORE flashing siyah and then siyah. Everything went ok this time, but eventually I found out that every time I do a factory reset after siyah that problem would occur.
Regards,
Sent from my GT-I9100 using XDA
keegan25 said:
i have the international 19100T
ahh rats i should have known rom manager does not work, , im just stuck in a white flash screen on boot up, cant get to cwm, although i can get into odin
would reflashing my kernel on odin get me through? everything is back up onto my sd card.
Click to expand...
Click to collapse
exact same problem, except i can't put it into download mode?
i know it's powerbutton vol down but it's not working? any ideas?
acbutcher91 said:
exact same problem, except i can't put it into download mode?
i know it's powerbutton vol down but it's not working? any ideas?
Click to expand...
Click to collapse
Power + vol down + home key?
I have a stock SGS3(4.1.1) pure stock. And now i want to flash CyanogenMod 10 and SiyahKernel.
But i don't know were to start!
What do i need to do before i install Odin(or mobile odin if you guys recommend that)
Please guys can you make me a step by step guide, how to flash CyanogenMod 10 and SiyahKernel?
This is my guess on how to do it:
1.Root
2.Flash a custom recovery
3.Flash CyanogenMod 10
4.Flash SiyahKernal
Probably i am all wrong. And that's why i need your help.
Thank's in advanced
Root with cf root which one have cwm and others steps like u said.
Better see instruction which every rom have on their threads.
Sent from my GT-I9300 using xda premium
xhaniGS2 said:
Root with cf root which one have cwm and others steps like u said.
Better see instruction which every rom have on their threads.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Thank's mate
So CF-Root have CWM(i i guess that is Custom recovery?)
I guess i have to flash CM10 before i flash the kernal?
Yes cwm is custom recovery.
First install rom than kernel. Wipe your phone from cwm before you install a new rom.
Sent from my GT-I9300 using xda premium
Do you know WHY you want a custom recovery?
Are yo udoing it because other people told you to or because you know what are the pros and cons of doing so?
If you just want root, you can just install Siyah kernel using Odin. That will give you a custom kernel + root. You can only use MobileOdin (which is great!) if you are already rooted.
There is no need to flash CWM or anything else, unless you know exactly what you'll be gaining or losing from it.
I suggest you take a look at the posts from the past 2 weeks and you'll notice that a lot of people are having problems with CWM. The most common is the lack of USB connectivity to the computer.
Simonetti2011 said:
Do you know WHY you want a custom recovery?
Are yo udoing it because other people told you to or because you know what are the pros and cons of doing so?
If you just want root, you can just install Siyah kernel using Odin. That will give you a custom kernel + root. You can only use MobileOdin (which is great!) if you are already rooted.
There is no need to flash CWM or anything else, unless you know exactly what you'll be gaining or losing from it.
I suggest you take a look at the posts from the past 2 weeks and you'll notice that a lot of people are having problems with CWM. The most common is the lack of USB connectivity to the computer.
Click to expand...
Click to collapse
When i flashed my SGS1. I used ClockWorkMod. So i was thinking i will be needing that for flashing CM10 and Siyah Kernel.
And no. I don't know the pro's and con's with CWM(?).
Do i need cwm when, flashing a ROM and a Kernal?
You need a custom recovery to flash, yes. Root your device, install a recovery, and flash you Rom. There are guides here where all is already written.
As we can't do things for you, it's good to read a bit...
Striatum_bdr said:
You need a custom recovery to flash, yes. Root your device, install a recovery, and flash you Rom. There are guides here where all is already written.
As we can't do things for you, it's good to read a bit...
Click to expand...
Click to collapse
No, you don't.
Just flash SiyahKernel using Odin3 through a USB connection. That's it.
I've done it on SIII of several friends, and in no moment I used CWM.
CWM is so full of bugs it is more trouble than a solution.
---------- Post added at 01:52 PM ---------- Previous post was at 01:32 PM ----------
mull54 said:
So i was thinking i will be needing that for flashing CM10 and Siyah Kernel.
And no. I don't know the pro's and con's with CWM(?).
Do i need cwm when, flashing a ROM and a Kernal?
Click to expand...
Click to collapse
Until you fully understand the pro's and con's of a custom recovery, I advise you to keep the stock one.
Read more of the post in these forums, specially the stickiers, read reports of users with problems, and so on. You'll come to the conclusion that a custom recovery, such as CWM, is uncessary for most users.
For what you want, however (which seems to be flashing a custom kernel + rooting), they aren't necessary.
Like I've written, you can flash Siyah using Odin. This will also root your device automatically. From then on, you can simply use MobileOdin to flash kernels and ROMs, while keeping your phone rooted.
Simonetti2011 said:
No, you don't.
Just flash SiyahKernel using Odin3 through a USB connection. That's it.
I've done it on SIII of several friends, and in no moment I used CWM.
CWM is so full of bugs it is more trouble than a solution.
---------- Post added at 01:52 PM ---------- Previous post was at 01:32 PM ----------
Until you fully understand the pro's and con's of a custom recovery, I advise you to keep the stock one.
Read more of the post in these forums, specially the stickiers, read reports of users with problems, and so on. You'll come to the conclusion that a custom recovery, such as CWM, is uncessary for most users.
For what you want, however (which seems to be flashing a custom kernel + rooting), they aren't necessary.
Like I've written, you can flash Siyah using Odin. This will also root your device automatically. From then on, you can simply use MobileOdin to flash kernels and ROMs, while keeping your phone rooted.
Click to expand...
Click to collapse
But i want to flash CM10 first, and then flash Siyah kernal. And from what i heard. I need Cwm for flashing a Custom rom?!
mull54 said:
But i want to flash CM10 first, and then flash Siyah kernal. And from what i heard. I need Cwm for flashing a Custom rom?!
Click to expand...
Click to collapse
From:
http://en.wikipedia.org/wiki/CyanogenMod
The CyanogenMod source code repository also contains the ClockworkMod Recovery (a "recovery image", maintained by Koushik "Koush" Dutta), which is used to install CyanogenMod and other custom upgrades. A recovery image is a special boot mode, which is used to backup or restore the device's storage and repair or upgrade system software. ClockworkMod Recovery can be automatically installed onto many rooted devices supported by CyanogenMod with Dutta's companion app, "ROM Manager", which is available on the Play Store. CyanogenMod does not need to be installed with a ClockworkMod Recovery, others such as TWRP (TeamWin Recovery Project) work just as well. Some users have experienced hard bricks from "ROM Manager".
Just to clear thing's up here!
This is what í will do?(i have choosen to use CWM)
PS. I Don't want to use ODIN(Desktop)
1. I root my phone with CF-Root and install CWM automatic i guess(?)
2. Than i use CWM Manager to flash CM10(?)
3. Than i use ODIN Mobile to flash SiyahKernal(?)
Or could i flash SiyhaKernal first. And than flash CM10 with CWM Manager for example?
Or could i just flash the kernal via odin without rooting my phone before i flash it?
1. Root your phone
2. Install Cutom ROM (CM10)
3. Use CWM (if installed) to flash SiyahKernal
I used Odin to root my phone and I have a CM10.1 nightly installed right now. I am about to flash the Siyah Kernel but I wonder - since I like being up to date with CM nightlies, will installing a new nightly override the Siyah kernel? Will I have to reinstall it every time?
The way I get it is a kernel sits between firmware and hardware - so by installing new FIRMWARE the kernel is untouched. Is that correct? I am glad for any information on this.
Thank you a lot in advance!
Behemoth1702 said:
I used Odin to root my phone and I have a CM10.1 nightly installed right now. I am about to flash the Siyah Kernel but I wonder - since I like being up to date with CM nightlies, will installing a new nightly override the Siyah kernel? Will I have to reinstall it every time?
The way I get it is a kernel sits between firmware and hardware - so by installing new FIRMWARE the kernel is untouched. Is that correct? I am glad for any information on this.
Thank you a lot in advance!
Click to expand...
Click to collapse
The CM nightly roms as with all other s3 roms have boot.img in the zip (i.e the kernel) so yes, flashing a new rom overwrites the kernel.
rootSU said:
The CM nightly roms as with all other s3 roms have boot.img in the zip (i.e the kernel) so yes, flashing a new rom overwrites the kernel.
Click to expand...
Click to collapse
Thank you very much for the info!
My friend wants me to flash custom rom to his s2.I have xperia x10 and galaxy nexus with me.Both i have flashed.So i have some experince with flashing but i dont see bottloader unlocking here or one click root ad all so i wanna confirm the steps here beore i do anything stupid
so are these the steps:
1.Root your stock phone with CF-Root 5.6 from http://forum.xda-developers.com/showthread.php?t=1103399
2.Then copy GT-I9100 Resurrection Remix JB v3.1.3 from http://forum.xda-developers.com/showthread.php?t=1436854 to the sd card
3.Get into cwm recovery and flash this rom after a clean wipe
4.Flash Dorimanx 7.44 after a reboot
Is this it?
aswinrulez said:
My friend wants me to flash custom rom to his s2.I have xperia x10 and galaxy nexus with me.Both i have flashed.So i have some experince with flashing but i dont see bottloader unlocking here or one click root ad all so i wanna confirm the steps here beore i do anything stupid
so are these the steps:
1.Root your stock phone with CF-Root 5.6 from http://forum.xda-developers.com/showthread.php?t=1103399
2.Then copy GT-I9100 Resurrection Remix JB v3.1.3 from http://forum.xda-developers.com/showthread.php?t=1436854 to the sd card
3.Get into cwm recovery and flash this rom after a clean wipe
4.Flash Dorimanx 7.44 after a reboot
Is this it?
Click to expand...
Click to collapse
Yeah, all good but, have you read this?
Is your device a GT I9100? Are you on 4.0.4? Got the brick bug? You know siyah is a safe kernel?
gastonw said:
Yeah, all good but, have you read this?
Is your device a GT I9100? Are you on 4.0.4? Got the brick bug? You know siyah is a safe kernel?
Click to expand...
Click to collapse
what if im flashing to 4.2.1 rom?this issue is with ics only right?
aswinrulez said:
what if im flashing to 4.2.1 rom?this issue is with ics only right?
Click to expand...
Click to collapse
The thing is where you're flashing from.
And yes, only 4.0.4's kernel's dangerous.
gastonw said:
The thing is where you're flashing from.
And yes, only 4.0.4's kernel's dangerous.
Click to expand...
Click to collapse
ok i dont have the phone yet..so will confirm its once i get it.
This issue only happens when i flash to ics rom right?not when i flash from stock ICS to JB ?
aswinrulez said:
ok i dont have the phone yet..so will confirm its once i get it.
This issue only happens when i flash to ics rom right?not when i flash from stock ICS to JB ?
Click to expand...
Click to collapse
If you want to go from stock ICS to stock JB you have no need to root.
All you do is simply reboot into download mode (Power on using Volume Up + Home + Power) then flash the JB md5 file via ODIN.
Once you have flashed the file you may find system wont boot into rom (this is normal). Just reboot into download mode and flash latest version of Siyah kernel (.tar file) which will be Siyah v6 beta4 (or above). This will give you cwm recovery, better battery life, root access, SU etc.
Go and have a look at some topics/search etc, All the info you need is already on here and if you try and take some shortcuts you may run into problems or even possibly brick your device so take some time and learn.
PS. Yes the eMMc brick bug is part of stock 4.0.4 kernel so just dont go into stock recovery. You can also brick device by your flash process getting interrupted so make sure you have drivers installed correctly (install kies) and taht you're not running any other programs while flashing and also that you have at least 55% battery.
It's a very good thing you are reading before getting the bad boy you intend to flash.
See the thing about this bug is when you make a back up, wipe things up from the recovery, and flash via oding. Once you do the wipes, you are kinda screwed.
Now, you got a couple of choices here:
1) Your device arrives with 4.0.4 ICS, flash siyah kernel (I'll get you off the hook).
2) Arrives with 4.0.3, you are good to go, no danger.
3) You can try mobile odin, it flashes with its own kernel and, apart from being fast, it's easy.
4) If you get a gingerbread version, you good as well.
That being said, I'd advice you to play with it for a couple of days instead of flashing right away.
Check out some videos, read something about ExynosAbuse (It'll get you rooted with one click) and revolv around the q&a section looking for "not to do list".
good luck and remember, keep on reading.
Sent from the little guy
TheATHEiST said:
If you want to go from stock ICS to stock JB you have no need to root.
All you do is simply reboot into download mode (Power on using Volume Up + Home + Power) then flash the JB md5 file via ODIN.
Once you have flashed the file you may find system wont boot into rom (this is normal). Just reboot into download mode and flash latest version of Siyah kernel (.tar file) which will be Siyah v6 beta4 (or above). This will give you cwm recovery, better battery life, root access, SU etc.
Click to expand...
Click to collapse
Thanks a lot for all your help
the ressurection remix rom i downloaded came as zip file.I can flash it from cwm itself right?
and regarding the kernel im a bit confused between siyah and dorimanx .I know it depends on phone but what would u suggest?ur personal choice
and i need one more help.I need a vanilla jb rom.Not too much bloatware and with less bugs as possible and tweaked for performance and battery.The problem is net speed is very very low...trust me..i cannot try most of them unless i wait for weeks.So if anyone can suggest i can download that alone and do
yeah, via recovery. Read sonething about cmw.
About custom ROM, can't tell you what to flash, do sone diggin in the android development sectio, whatch some vids, It's all here at xda.
Sent from the little guy
gastonw said:
yeah, via recovery. Read sonething about cmw.
About custom ROM, can't tell you what to flash, do sone diggin in the android development sectio, whatch some vids, It's all here at xda.
Sent from the little guy
Click to expand...
Click to collapse
Thank you
don't mention it.
keep reading & happy flashing.
Sent from the little guy
The LG G Pad 8.3 has a locked bootloader, and to bypass it we have two different tools: Open bump and Loki. Most custom roms now use Open bump (recommended), but some still use Loki. Jellybean and Kitkat bootloaders have different backlight settings, and kernels need to be adapted to match those backlight settings. So here I provide some flashable zips, so you can choose the bootloader that best suits your custom rom.
IMPORTANT: to install these files, reboot into recovery and flash the zip of your choice. After that, reboot into recovery again so the changes take effect. If you are stuck on Lollipop bootloader and have no access to recovery, check this post.
V50020F Bootloader is needed if the kernel in your custom rom/recovery is adapted to Kitkat bootloader backlight, like CyanogenMod 12.1 and TWRP official builds.
V50020F Bootloader: https://www.androidfilehost.com/?fid=24352994023707804
*** DEPRECATED (below) ***
V50010B Bootloader is needed if the kernel in your custom rom is adapted to Jellybean bootloader backlight, like those based on CyanogenMod old code.
V50010B Bootloader: https://www.androidfilehost.com/?fid=23991606952613674
V50020D Bootloader Loki is needed if the kernel in your custom rom is adapted to Kitkat bootloader backlight, but it's packed with Loki. All the files are from V50020D, except aboot.img from V50010B. This should not be used anymore, every custom rom should use Open bump instead of Loki. If you are a developer and want to use Open bump instead of Loki, check this commit.
V50020D Bootloader Loki: https://www.androidfilehost.com/?fid=23991606952613676
* If you are a developer and want to use Kitkat bootloader backlight settings (instead of Jellybean), check this commit.
Wow I may not have my Gpad yet but I think its getting easier now because of this base flashable zip. Thanks
This will automatically replace old version of TWRP if flash for the first time like this one?
http://forum.xda-developers.com/showthread.php?t=2641409
@jsevi83 Great Idea! :good:
How can we exactly use this?
Just want to make sure nothings bad gonna happen
Im currently on LRS Kitkat and old TWRP. If I want to replace it with CM 4.4.2 ROM. I have to wipe the system then use 4.2.2 base then the full CM ROM?
Just found out that even the new TWRP 2.7.0.1 is still not compatible LRS ROM
Its possible to replace recovery.img with old TWRP or perhaps Philz CWM?
Yeah, I'm a little lost too on how to proceed. If you can post some detailed instructions, it'd be much appreciated
yawako said:
How can we exactly use this?
Just want to make sure nothings bad gonna happen
Im currently on LRS Kitkat and old TWRP. If I want to replace it with CM 4.4.2 ROM. I have to wipe the system then use 4.2.2 base then the full CM ROM?
Just found out that even the new TWRP 2.7.0.1 is still not compatible LRS ROM
Its possible to replace recovery.img with old TWRP or perhaps Philz CWM?
Click to expand...
Click to collapse
ptargino said:
Yeah, I'm a little lost too on how to proceed. If you can post some detailed instructions, it'd be much appreciated
Click to expand...
Click to collapse
It's pretty simple, If your on a 4.4 stock (not aosp) and want to flash an aosp 4.4 rom (which uses 4.2 bootstack) flash the 4.2 zip then reboot into recovery from recovery (important) and then flash your rom normally. If your on 4.2 stock or aosp and want to flash a 4.4 stock rom, flash the 4.4 zip then do the same by rebooting into recovery from recovery and flash away. Its important to reboot into recovery from recovery after flashing these because if you boot your current rom, the kernel and other boot partitions won't match - bad things will happen.
annoyingduck said:
It's pretty simple, If your on a 4.4 stock (not aosp) and want to flash an aosp 4.4 rom (which uses 4.2 bootstack) flash the 4.2 zip then reboot into recovery from recovery (important) and then flash your rom normally. If your on 4.2 stock or aosp and want to flash a 4.4 stock rom, flash the 4.4 zip then do the same by rebooting into recovery from recovery and flash away. Its important to reboot into recovery from recovery after flashing these because if you boot your current rom, the kernel and other boot partitions won't match - bad things will happen.
Click to expand...
Click to collapse
Thanks, I added the instructions to the first post and mentioned you in the credits.
What do you meant boot into recovery from recovery?why boot into it twice? Im on stock 4.2 and want to flash 4.4
jsevi83 said:
Thanks, I added the instructions to the first post and mentioned you in the credits.
Click to expand...
Click to collapse
ok, so i did the thing where bad things happen, i tried flashing the 4.4.2 one thinking i had 4.2.2 and now its bootloop hell. Goes to teamwin screen then it auto runs "Running Open recovery script" then bootloops again. Hard reset does not work, just goes back into loop.
How can i undo the stupidity? thanks
RyanEJ25 said:
What do you meant boot into recovery from recovery?why boot into it twice? Im on stock 4.2 and want to flash 4.4
Click to expand...
Click to collapse
Boot into recovery, flash the chosen base zip, then press the reboot button and then recovery, this way it reboots into recovery again and the changes are applied. Then you flash the rom you want.
erwaso said:
ok, so i did the thing where bad things happen, i tried flashing the 4.4.2 one thinking i had 4.2.2 and now its bootloop hell. Goes to teamwin screen then it auto runs "Running Open recovery script" then bootloops again. Hard reset does not work, just goes back into loop.
How can i undo the stupidity? thanks
Click to expand...
Click to collapse
It depends on what rom you want to have. If you want stock 4.4.2, flash any of the zips found in the forum (like the flashable V50020B), it will also change the base. If you want CM11 or any other AOSP based rom, flash the 4.2.2-base.zip, reboot into recovery again and then flash the zip of the rom.
jsevi83 said:
Boot into recovery, flash the chosen base zip, then press the reboot button and then recovery, this way it reboots into recovery again and the changes are applied. Then you flash the rom you want.
It depends on what rom you want to have. If you want stock 4.4.2, flash any of the zips found in the forum (like the flashable V50020B), it will also change the base. If you want CM11 or any other AOSP based rom, flash the 4.2.2-base.zip, reboot into recovery again and then flash the zip of the rom.
Click to expand...
Click to collapse
I understand that part. Problem is I don't have the chance to do anything. It goes from LG screen to teamwin logo to the flashing screen then back to the LG screen.
How can I stop the boot looping?
erwaso said:
I understand that part. Problem is I don't have the chance to do anything. It goes from LG screen to teamwin logo to the flashing screen then back to the LG screen.
How can I stop the boot looping?
Click to expand...
Click to collapse
I don't understand how you got into that situation, I tested the zips a lot before publishing them. Anyway, if I were you I would install the KDZ file to get back to stock. There are some threads in the forum explaining how to do that.
erwaso said:
I understand that part. Problem is I don't have the chance to do anything. It goes from LG screen to teamwin logo to the flashing screen then back to the LG screen.
How can I stop the boot looping?
Click to expand...
Click to collapse
Free thanks...
Anyways, can you get into download mode?
Sent from my LG-V500 using Tapatalk
annoyingduck said:
Free thanks...
Anyways, can you get into download mode?
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
Yes sir. But while I use the mobile tool in Windows Vista, it keeps stopping at 30% during extraction. I saw that YouTube video for unbricking going from 5 to 80 in a second during extraction.
So annoyed lol. Never happened to me before.
---------- Post added at 06:41 PM ---------- Previous post was at 06:38 PM ----------
jsevi83 said:
I don't understand how you got into that situation, I tested the zips a lot before publishing them. Anyway, if I were you I would install the KDZ file to get back to stock. There are some threads in the forum explaining how to do that.
Click to expand...
Click to collapse
I was already in trouble before, I was rooted on 4.2.2 and did a factory reset before updating to Stock 4.4.2. I got stuck in twrp home screen and no matter what I tried to wipe or flash it went back to twrp home. So I tried to flash your 4.4.2 zip and now it's all boot loop happy lol
I saw that kdz thread. I'll try it when the kids aren't running around me in circles
erwaso said:
Yes sir. But while I use the mobile tool in Windows Vista, it keeps stopping at 30% during extraction. I saw that YouTube video for unbricking going from 5 to 80 in a second during extraction.
So annoyed lol. Never happened to me before.
---------- Post added at 06:41 PM ---------- Previous post was at 06:38 PM ----------
I was already in trouble before, I was rooted on 4.2.2 and did a factory reset before updating to Stock 4.4.2. I got stuck in twrp home screen and no matter what I tried to wipe or flash it went back to twrp home. So I tried to flash your 4.4.2 zip and now it's all boot loop happy lol
I saw that kdz thread. I'll try it when the kids aren't running around me in circles
Click to expand...
Click to collapse
Use mobile tool and do it again. Be sure your using the regular mobile tool, not the modified one for the kdz method. Get in dl mode, choose upgrade recovery option + manually enter your model # and serial #. Give it a good 5+ min to determine if it's actually hanging. If it does, unplug it and plug it back in and it'll continue. I did that once and it worked fine.
-VZW LG G2 VS980
annoyingduck said:
Use mobile tool and do it again. Be sure your using the regular mobile tool, not the modified one for the kdz method. Get in dl mode, choose upgrade recovery option + manually enter your model # and serial #. Give it a good 5+ min to determine if it's actually hanging. If it does, unplug it and plug it back in and it'll continue. I did that once and it worked fine.
-VZW LG G2 VS980
Click to expand...
Click to collapse
Thanks! I'll try it and report back. Appreciate the assist!
Ended up deleting all LG related anything on my comp, then reinstalling them as suggested in another thread. This worked lol. Now to root ioroot and see if I can't screw up again.
Thanks.
jsevi83 said:
It depends on what rom you want to have. If you want stock 4.4.2, flash any of the zips found in the forum (like the flashable V50020B), it will also change the base. If you want CM11 or any other AOSP based rom, flash the 4.2.2-base.zip, reboot into recovery again and then flash the zip of the rom.
Click to expand...
Click to collapse
I still don't get it. If I am on Pacman that says 4.4.2, what do I flash? How do I know if a certain rom is AOSP based, and what bootstack when it says 4.4.2? And if I'm already on PacMan 442, and want to get rid of the dim light issue, do I flash the appropriate zip, then reflash the rom? Or do I need to downgrade to stock 4.2.2 then flash 422 zip, then flash the custom rom again???
graphdarnell said:
I still don't get it. If I am on Pacman that says 4.4.2, what do I flash? How do I know if a certain rom is AOSP based, and what bootstack when it says 4.4.2? And if I'm already on PacMan 442, and want to get rid of the dim light issue, do I flash the appropriate zip, then reflash the rom? Or do I need to downgrade to stock 4.2.2 then flash 422 zip, then flash the custom rom again???
Click to expand...
Click to collapse
If you have the dim light issue at boot, flash the 4.2.2 base zip. If you want to install a custom rom based on stock 4.4.2, install the 4.4.2 base zip.
jsevi83 said:
If you have the dim light issue at boot, flash the 4.2.2 base zip. If you want to install a custom rom based on stock 4.4.2, install the 4.4.2 base zip.
Click to expand...
Click to collapse
Thank you for the prompt reply and help. Lest I belabor the point, I understand what you're saying from the beginning, but what confused me was the mention by another member that the 4.4.2 customs roms used 4.2 "bootstack" (whatever that means). So the question again is: if a custom rom says 4.4.2, is it really 4.4.2 or 4.2 boot stack (whatever that is)? And in which case, which zip do I use?? I can do it by trial and error, but need to be assured that shooting from the hip won't mess my tab unnecessarily. Again thanks for the help.
I have a rooted sprint note 3 that I really want to flash a custom rom on. I cannot seem to find any good places to give me step by step instructions. I have flashed custom roms way back on my droid razr, but I really need some help. Can anyone point me in the right direction with a link or anything that will walk me through this?
I'm also having the same problem, I'm rooted but don't know how to install a custom recovery. I used toweltoot. Any suggestions??!
Sent from my SM-N900P using XDA Free mobile app
tboy72 said:
I have a rooted sprint note 3 that I really want to flash a custom rom on. I cannot seem to find any good places to give me step by step instructions. I have flashed custom roms way back on my droid razr, but I really need some help. Can anyone point me in the right direction with a link or anything that will walk me through this?
Click to expand...
Click to collapse
OK, first what version of KIKAT are you on ? If you are on 4.4.4 NH7 the latest upgrade then you can root with Chainfires CF-autoroot or his SuperSu v 1.94 or v2.02 this will trip KNOX warranty. Towel Root will not work yet for NH7. If you are still on 4.4.2 NC5 then you can use Towel Root to root your device, this will NOT trip KNOX warranty. If you root with Chainfires CF-autoroot or his SuperSu v 1.94 or v2.02 this will trip KNOX warranty on NC5.
Recoveries, the two popular ones are TWRP and Philz CWM. INSTALLING A RECOVERY WILL TRIP KNOX WARRANTY!!! You need a recovery to flash roms so you need to make choice at this point ? Here is the link to Philz CWM latest version 6.48.4.tar https://goo.im/devs/philz_touch/CWM_Advanced_Edition/hlte/ download to desktop or downloads.
I run a stock rooted 4.4.2 NC5 with Philz custom recovery version 6.12.9 hltespr https://goo.im/devs/philz_touch/CWM_Advanced_Edition/hltespr/ . The device was rooted and warranty tripped the second day I owned it. I was in a Sprint corporate Store a couple of wks ago. Showed the tech my rooted note 3. He said I can't touch that, I said what if I unrooted the phone. He said no problem, now I can warranty the phone. He didn't care that the KNOX flag was tripped at all 0x1. Just can't be rooted when you bring it in for service. Sprint doesn't care about KNOX only Samsung cares about KNOX. When Samsung paid millions to the NSA to design a security system to track and spy on others than they care !!!
Ok lets install a recovery !!!
1. you need Odin on the desktop of your PC here is the link http://www.downloadodin.info/download-odin-1-85
2. you need to install Samsung drivers on your PC you can get them from the link in #1
3. completely power down your device, and boot into download mode (press and hold the power button, volume down button, and the home button at the same time) a new screen will popup then push the volume up button to get into download mode.
4. click on the Odin zip file and extract to desktop, right click and run as administrator
5. with your device in download mode connect it to your pc via usb cable, COM: will light up in the upper left hand corner of Odin doesn't matter what color or number just shows a connection has been made.
6. click PDA box in odin, a box will popup click where ever you have recovery file downloaded, once open it will show up in box next to PDA
7. click start wait till you see pass and success 1, then your custom recovery is installed.
After the recovery is installed, download a copy of SuperSu to your desktop here is the link http://download.chainfire.eu/396/SuperSU/ to version v1.94. Then copy and paste to sd card via USB cable. Now the next thing you are going to do is completely power down the device and boot into recovery. (press and hold the power button, volume up button, and home button at he same time) a menu will come up, click on Install Zip, then sd card to install zip and root device. Boot device and verify it is rooted, then power down, and boot into recovery. Click on backup, MAKE A BACKUP OF YOUR ROOTED ROM !!! Then make a backup of EFS file by its self it will show up in your backup file on the sd card or ext sd card depending on where you choose to put it. Copy and paste the efs file someplace safe.
With the Google Play Store download some type of root file manager like Root Explorer (what I use)
OK lets flash a rom !!!
First, you CANNOT flash a rom that is based on an older version of rom you are currently running. EX: If you are on KK 4.4.2 NC5 you can flash a rom based on NAB or NC5 but you CANNOT use a rom based on mj4 or older read the OP thread carefully . You can run AOSP roms as long as they are based on 4.4+.
1. install the new rom zip you want to flash on your sd card via usb cable from PC or download directly to device
2. power down phone completely and boot into recovery
3. from the menu find and wipe cache, delvik cache, and wipe system to install new rom, NOT FACTORY RESET !!!
4. go back to menu and click on install zip then click on where you have the zip ( i.e. sd card ) and install this will take a minute or two
5. back to main menu and reboot device this will take several minutes on the first boot of a new rom
6. enjoy your new rom !!!
Lets do a restore from backup recovery file !!!
1. completely power down device and boot into recovery
2. go to main menu and click on wipe system to install new rom ( no need to mess with the caches on a restore )
3. back to the menu click on back up and restore, then click on the backup file location ( i.e. sd card )
4. now click on restore
5. when its completed reboot device this will install your original rooted stock rom you made a backup for
Eventually you will figure out that you can make several backups and they have really weird numbered time stamps to identify them.
bman55 said:
I'm also having the same problem, I'm rooted but don't know how to install a custom recovery. I used toweltoot. Any suggestions??!
Sent from my SM-N900P using XDA Free mobile app
Click to expand...
Click to collapse
Look UP !!!
jimzweb1 said:
OK, first what version of KIKAT are you on ? If you are on 4.4.4 NH7 the latest upgrade then you can root with Chainfires CF-autoroot or his SuperSu v 1.94 or v2.02 this will trip KNOX warranty. Towel Root will not work yet for NH7. If you are still on 4.4.2 NC5 then you can use Towel Root to root your device, this will NOT trip KNOX warranty. If you use Chainfires CF-autoroot or his SuperSu v 1.94 or v2.02 this will trip KNOX warranty on NC5.
Recoveries, the two popular ones are TWRP and Philz CWM. INSTALLING A RECOVERY WILL TRIP KNOX WARRANTY!!! You need a recovery to flash roms so you need to make choice at this point ? Here is the link to Philz CWM latest version 6.48.4.tar https://goo.im/devs/philz_touch/CWM_Advanced_Edition/hlte/ download to desktop or downloads.
I run a stock rooted 4.4.2 NC5 with Philz custom recovery version 6.12.9 hltespr. The device was rooted and warranty tripped the second day I owned it. I was in a Sprint corporate Store a couple of wks ago. Showed the tech my rooted note 3. He said I can't touch that, I said what if I unrooted the phone. He said no problem, now I can warranty the phone. He didn't care that the KNOX flag was tripped at all 0x1. Just can't be rooted when you bring it in for service. Sprint doesn't care about KNOX only Samsung cares about KNOX. When Samsung paid millions to the NSA to design a security system to track and spy on others than they care !!!
Ok lets install a recovery !!!
1. you need Odin on the desktop of your PC here is the link http://www.downloadodin.info/download-odin-1-85
2. you need to install Samsung drivers on your PC you can get them from the link in #1
3. completely power down your device, and boot into download mode (press and hold the power button, volume down button, and the home button at the same time) a new screen will popup then push the volume up button to get into download mode.
4. click on the Odin zip file and extract to desktop, right click and run as administrator
5. with your device in download mode connect it to your pc via usb cable, COM: will light up in the upper right hand corner of Odin doesn't matter what color or number just shows a connection has been made.
6. click on the PDA box, a new box will popup click on where ever you have the recovery file then click open
7. click start wait till you see pass and success 1, then your custom recovery is installed.
Now the next thing you are going to do is completely power down the device and boot into recovery. (press and hold the power button, volume up button, and home button at he same time) a menu will come up MAKE A BACKUP OF YOU ROM !!! Then make a backup of EFS by its self it will show up in your backup file on the sd card. Copy and paste the efs file someplace safe.
With the Google Play Store download some type of root file manager like Root Explorer (what I use)
OK lets flash a rom !!!
First, you CANNOT flash a rom that is based on an older version of rom you are currently running. EX: If you are on KK 4.4.2 NC5 you can flash a rom based on NAB or NC5 but you CANNOT use a rom based on mj4 or older read the OP thread carefully . You can run AOSP roms as long as they are based on 4.4+.
1. install the new rom zip you want to flash on your sd card via usb cable from PC or download directly to device
2. power down phone completely and boot into recovery
3. from the menu find and wipe cache, delvik cache, and wipe system to install new rom, NOT FACTORY RESET !!!
4. go back to menu and click on install zip then click on where you have the zip and install this will take a minute or two
5. back to main menu and reboot device this will take several minutes on the first boot of a new rom
6. enjoy you new rom !!!
Lets do a backup recovery !!!
1. completely power down device and boot into recovery
2. go to main menu and click on wipe system to install new rom ( no need to mess with the caches on a restore )
3. back to the menu click on back up and restore then click on the backup file you made
4. now click on restore
5. when its completed reboot device this will install your original rooted stock rom you made a backup for
Eventually you will figure out that you can make several backups and they have really weird numbered time stamps to identify them.
Click to expand...
Click to collapse
Thanks so much for your help! Unfortunately I am not even able to install Odin on my windows 7 pc. Chrome says its malicious and blocks it, Firefox does the same. First my Norton firewall wouldn't allow it, so I disabled that long enough to try to download Odin.
I can't do anything unless I can get Odin to download to my pc.
jimzweb1 said:
Look UP !!!
Click to expand...
Click to collapse
If I'm on CM11, can I flash a TouchWiz ROM that's on 4.4.2?
Because I've been trying to flash the Vision-X ROM but I get stuck in a bootloop after I flash the kernel and ROM.
itzkpanda said:
If I'm on CM11, can I flash a TouchWiz ROM that's on 4.4.2?
Because I've been trying to flash the Vision-X ROM but I get stuck in a bootloop after I flash the kernel and ROM.
Click to expand...
Click to collapse
YES, first, make sure you are wiping everything in recovery, then I would just flash the rom. This will make sure you don't have a bad down load of the rom. If it boots up, then go back into recovery and flash the kernel. You should try the LeanKernel its OC to 2.7ghz here is the link http://forum.xda-developers.com/showthread.php?t=2488082 Vision-X is TW based rom so click leankernel other n900x devices choose the " hltespr kk v3.8 " kernel. Enjoy !!!
Make sure you install Trickster or SetCPU from the play store so you can set what type of governor you want to use on the kernel. ( like interactive ) Then you need to set the min and max cpu frequencies so the kernel will give you the maximum battery life.
jimzweb1 said:
YES, first, make sure you are wiping everything in recovery, then I would just flash the rom. This will make sure you don't have a bad down load of the rom. If it boots up, then go back into recovery and flash the kernel. You should try the LeanKernel its OC to 2.7ghz here is the link http://forum.xda-developers.com/showthread.php?t=2488082 Vision-X is TW based rom so click leankernel other n900x devices choose the " hltespr kk v3.8 " kernel. Enjoy !!!
Make sure you install Trickster or SetCPU from the play store so you can set what type of governor you want to use on the kernel. ( like interactive ) Then you need to set the min and max cpu frequencies so the kernel will give you the maximum battery life.
Click to expand...
Click to collapse
Thanks. When i flash just the ROM I still get stuck in a bootloop
tboy72 said:
Thanks so much for your help! Unfortunately I am not even able to install Odin on my windows 7 pc. Chrome says its malicious and blocks it, Firefox does the same. First my Norton firewall wouldn't allow it, so I disabled that long enough to try to download Odin.
I can't do anything unless I can get Odin to download to my pc.
Click to expand...
Click to collapse
I run windows 7 Ultimate, my browser is IE 11 with Microsoft Security Essentials never had a problem.
---------- Post added at 01:12 PM ---------- Previous post was at 12:58 PM ----------
itzkpanda said:
Thanks. When i flash just the ROM I still get stuck in a bootloop
Click to expand...
Click to collapse
When you say stuck in a bootloop, does that mean its stuck at say the sprint logo ? It takes a full 5 to 6 minutes on the first boot up !!! Make sure you use the stock kernel, then flash a custom one later.
If that doesn't work, you should have made a backup of your original stock rooted 4.4.2 NC5. Go to your recovery WIPE cache, delvike cache, and wipe system to install a new rom. Then restore the original stock rooted backup and boot the device. If it boots then go back into recovery wipe everything again and install the Vision-X zip again and boot it.
Sometimes after an AOSP rom like CM11, you have to go back to stock rooted and start again.
jimzweb1 said:
I run windows 7 Ultimate, my browser is IE 11 with Microsoft Security Essentials never had a problem.
---------- Post added at 01:12 PM ---------- Previous post was at 12:58 PM ----------
When you say stuck in a bootloop, does that mean its stuck at say the sprint logo ? It takes a full 5 to 6 minutes on the first boot up !!! Make sure you use the stock kernel, then flash a custom one later.
Click to expand...
Click to collapse
The Samsung Galaxy Note 3 logo comes up, then it reboots and shows the Note 3 logo, then reboots and repeats. It never makes it to the Sprint logo
itzkpanda said:
The Samsung Galaxy Note 3 logo comes up, then it reboots and shows the Note 3 logo, then reboots and repeats. It never makes it to the Sprint logo
Click to expand...
Click to collapse
Cool, I run a CSC of XAS which eliminates the Sprint logo. All I ever get is the Samsung logo, I don't miss Sprint logo.
jimzweb1 said:
Cool, I run a CSC of XAS which eliminates the Sprint logo. All I ever get is the Samsung logo, I don't miss Sprint logo.
Click to expand...
Click to collapse
I dont have that.
Normally it would go to the Samsung Galaxy Note 3 logo to the Sprint logo and then turn on, but it just bootloops on the Samsung Galaxy Note 3 logo.
Do you know how I would be able to get the Vision-X rom to work?
itzkpanda said:
I dont have that.
Normally it would go to the Samsung Galaxy Note 3 logo to the Sprint logo and then turn on, but it just bootloops on the Samsung Galaxy Note 3 logo.
Do you know how I would be able to get the Vision-X rom to work?
Click to expand...
Click to collapse
Did you try my suggestion in post #9 ?
jimzweb1 said:
Did you try my suggestion in post #9 ?
Click to expand...
Click to collapse
Ah, i didnt see the 2nd edit
Do you have a link for a stock rooted 4.4.2 rom?
itzkpanda said:
Ah, i didnt see the 2nd edit
Do you have a link for a stock rooted 4.4.2 rom?
Click to expand...
Click to collapse
Yes here you go http://forum.xda-developers.com/showthread.php?t=2472664 scroll down to old 4.4.2 NC5(D) click on show content. Download the Full Rom ODEX NC5 version. This is flashed through a recovery like twrp or cwm.
If you don't have a backup of the original rom that came with the phone I would go this way. First, here is a link for a complete stock 4.4.2 NC5 rom http://forum.xda-developers.com/showthread.php?t=2712205 just click on NC5 and follow the instructions on the top of the thread. Then install the recovery look in post #3. Then root the device here is the link http://download.chainfire.eu/396/SuperSU/ this is Chainfires supersu v1.94.
Once you are back to stock rooted nc5, go to recovery make a backup to a ext sd card or use the internal sd card, then copy and paste the backup file somewhere on your PC. Now have base to work from, so if something goes south you can always get back to square one. With all the flashing I do, I end up recovering a backup at least a couple of times a wk or day if I'm trying something out. It's like system restore on a PC.
jimzweb1 said:
Yes here you go http://forum.xda-developers.com/showthread.php?t=2472664 scroll down to old 4.4.2 NC5(D) click on show content. Download the Full Rom ODEX NC5 version. This is flashed through a recovery like twrp or cwm.
If you don't have a backup of the original rom that came with the phone I would go this way. First, here is a link for a complete stock 4.4.2 NC5 rom http://forum.xda-developers.com/showthread.php?t=2712205 just click on NC5 and follow the instructions on the top of the thread. Then install the recovery look in post #3. Then root the device here is the link http://download.chainfire.eu/396/SuperSU/ this is Chainfires supersu v1.94.
Once you are back to stock rooted nc5, go to recovery make a backup to a ext sd card or use the internal sd card, then copy and paste the backup file somewhere on your PC. Now have base to work from, so if something goes south you can always get back to square one. With all the flashing I do, I end up recovering a backup at least a couple of times a wk or day if I'm trying something out. It's like system restore on a PC.
Click to expand...
Click to collapse
Thanks for the info! I'll try it and let you know how it goes.
jimzweb1 said:
Yes here you go http://forum.xda-developers.com/showthread.php?t=2472664 scroll down to old 4.4.2 NC5(D) click on show content. Download the Full Rom ODEX NC5 version. This is flashed through a recovery like twrp or cwm.
If you don't have a backup of the original rom that came with the phone I would go this way. First, here is a link for a complete stock 4.4.2 NC5 rom http://forum.xda-developers.com/showthread.php?t=2712205 just click on NC5 and follow the instructions on the top of the thread. Then install the recovery look in post #3. Then root the device here is the link http://download.chainfire.eu/396/SuperSU/ this is Chainfires supersu v1.94.
Once you are back to stock rooted nc5, go to recovery make a backup to a ext sd card or use the internal sd card, then copy and paste the backup file somewhere on your PC. Now have base to work from, so if something goes south you can always get back to square one. With all the flashing I do, I end up recovering a backup at least a couple of times a wk or day if I'm trying something out. It's like system restore on a PC.
Click to expand...
Click to collapse
After following your steps i Have Vision-X working now, thanks!
itzkpanda said:
After following your steps i Have Vision-X working now, thanks!
Click to expand...
Click to collapse
Awesome !!! Believe it or not, even with a perfect backup to restore from. Every once in awhile I will start from scratch and get a fresh stock copy of NC5, use Odin to install and get back to original official status. Then root, get rid of the bloatware, and make a backup just to keep things fresh. I have not upgraded to 4.4.4 NH7 and don't recommend it at this time. There are a lot of complaints of stuff missing or not working.
Besides, I'm rooted and flashing other roms. 4.4.4 only adds Kid Mode and some security updates, which are useless if you have a custom rom in the device.
Same issue
I am having the same issue with the bootloop sticking on the galaxy screen. I used CF autoroot to root my 4.4.2 stock. Installed Josh's KKKiller 4.4.2. Liked it but had some issues so went back to stock 4.4.2. Re rooted with CF. Installed AOSP rom but my phone needs stock voicemail to dl vociemail to phone. Went back to stock NC5 Odin. Went to reinstall TWRP and cannot install any but the latest 4.4.4 TWRP and cannot install any rom but a 4.4.4. I have re-stocked and re-rooted. I cannot even flash the stock? 4.4.4 NH7. Get the same error message from TWRP on all but Pacman, Liquidsmooth. Havent tried all the aosp but assume results will be the same. I would like to flash some 4.4.2 roms. Am I stuck?
Screw U 4 making me said:
I am having the same issue with the bootloop sticking on the galaxy screen. I used CF autoroot to root my 4.4.2 stock. Installed Josh's KKKiller 4.4.2. Liked it but had some issues so went back to stock 4.4.2. Re rooted with CF. Installed AOSP rom but my phone needs stock voicemail to dl vociemail to phone. Went back to stock NC5 Odin. Went to reinstall TWRP and cannot install any but the latest 4.4.4 TWRP and cannot install any rom but a 4.4.4. I have re-stocked and re-rooted. I cannot even flash the stock? 4.4.4 NH7. Get the same error message from TWRP on all but Pacman, Liquidsmooth. Havent tried all the aosp but assume results will be the same. I would like to flash some 4.4.2 roms. Am I stuck?
Click to expand...
Click to collapse
No, just install the 4.4.4 twrp recovery that works. Boot into that recovery and wipe everything i.e. cache, delvik cache, and completely wipe system to install a new rom. Now from recovery boot into download mode. Then from your PC bring up odin and flash a fresh copy of NC5, I use micmars NC5 here is the link http://forum.xda-developers.com/showthread.php?t=2712205 now this should take you back to NC5 stock. Then try flashing Philz CWM 6.12.9 hltespr here is the link https://goo.im/devs/philz_touch/CWM_Advanced_Edition/hltespr/ it just seems to work better when you are flashing back and forth from AOSP . Just me I have beat that recovery to death and it has never failed. Make sure the first thing you do is make a backup after you are rooted, so you can always get back to square one. You should also have a backup of your efs file on your PC for safe keeping. Let me know how it goes.