Hello Everyone,
I'm a bit of a noob on android(I've only had 2 Droids,X10 and HOX till now and only know the basics of flashing ROMs and such :victory.I wanted to know,when we're flashing JB ROMs,such as insertcooin,ARHD 17 etc, do we have to flash "firmware"/change the HBOOT if we've already OTA updated to stock jelly bean(I unrooted when stock jelly bean was about to come out).
Thanks in advance,
Robin
TL;DR version :angel: if I've updated to stock OTA JB,do I need to flash firmwares/change HBOOT before flashing ARHD 17,Insertcoin,maximus etc?
No, you're good to go.
Actually... Yes. Sometimes the devs make modifications. With the sense roms you can usually get away with it. But it's good habit to flash the boot.img that comes with the rom as well.
peedub said:
Actually... Yes. Sometimes the devs make modifications. With the sense roms you can usually get away with it. But it's good habit to flash the boot.img that comes with the rom as well.
Click to expand...
Click to collapse
He said hboot, not boot.img.
Oops, sorry about that! Disregard everything I said!
Related
So for the first time ever, I successfully rooted my Nexus, and flashed the latest build of the AOKP ROM (40) to my phone using the GNexus toolkit.
Now with Android 4.1 coming to us very soon, I went to the button just to make sure it would still work even after flashing (I tried to search the forums for this q but to no avail.), but sadly the button is gone.
I'm assuming I have to make a Nandroid (right?) and flash back to stock to update and then reflash back to AOKP? Please enlighten me. Thanks for reading this, and thanks to any helpful comments.
itsjaylin said:
So for the first time ever, I successfully rooted my Nexus, and flashed the latest build of the AOKP ROM (40) to my phone using the GNexus toolkit.
Now with Android 4.1 coming to us very soon, I went to the button just to make sure it would still work even after flashing (I tried to search the forums for this q but to no avail.), but sadly the button is gone.
I'm assuming I have to make a Nandroid (right?) and flash back to stock to update and then reflash back to AOKP? Please enlighten me. Thanks for reading this, and thanks to any helpful comments.
Click to expand...
Click to collapse
Woah, you are mixing up a lot of things.
1) You CANNOT update a non-stock ROM unless the dev puts out an update for it.
2) If you are talking about the "System update" "Check now" button, it is still there (at least on stock ROMs -- it won't work anyway on non-stock ROMs).
3) Flashing a stock build, updating it, and then flashing AOKP does absolutely nothing. Why would you update a stock build, just to overwrite it with AOKP?
efrant said:
Woah, you are mixing up a lot of things.
1) You CANNOT update a non-stock ROM unless the dev puts out an update for it.
2) If you are talking about the "System update" "Check now" button, it is still there (at least on stock ROMs -- it won't work anyway on non-stock ROMs).
3) Flashing a stock build, updating it, and then flashing AOKP does absolutely nothing. Why would you update a stock build, just to overwrite it with AOKP?
Click to expand...
Click to collapse
Ok thanks for clearing this up. I'm still thinking that a ROM is somewhat of an overlay over what you already had. But I understand now. If I flash back to stock, I'll have the button back and be able to update.
And I shouldn't update back to AOKP until THEY release another build with 4.1?
itsjaylin said:
If I flash back to stock, I'll have the button back and be able to update.
And I shouldn't update back to AOKP until THEY release another build with 4.1?
Click to expand...
Click to collapse
1) yes, you'll have the button back. I've also gone back to IMM76I, waiting for the OTA to drop. Been meaning to try one.
2) you should go back to aokp? No, you can go back to aokp or any other rom whenever you feel like it.
Just remember that to successfully update a stock rom OTA style, you cannot be using a custom recovery (like cwm), which you need to flash a custom rom.
edit: actually, i've gone back to cm9 hahaha
sent from my i9250
itsjaylin said:
So for the first time ever, I successfully rooted my Nexus, and flashed the latest build of the AOKP ROM (40) to my phone using the GNexus toolkit.
Now with Android 4.1 coming to us very soon, I went to the button just to make sure it would still work even after flashing (I tried to search the forums for this q but to no avail.), but sadly the button is gone.
I'm assuming I have to make a Nandroid (right?) and flash back to stock to update and then reflash back to AOKP? Please enlighten me. Thanks for reading this, and thanks to any helpful comments.
Click to expand...
Click to collapse
Well, seeming as you're not running a stock ROM, there are no OTA updates, for your device, anymore. But as soon as the devs get their hands on the source, they'll get it to you, trust me
itsjaylin said:
Ok thanks for clearing this up. I'm still thinking that a ROM is somewhat of an overlay over what you already had. But I understand now. If I flash back to stock, I'll have the button back and be able to update.
And I shouldn't update back to AOKP until THEY release another build with 4.1?
Click to expand...
Click to collapse
A ROM is not an overlay. When you flash a ROM you are basically replacing the firmware.
It's easy enough to flash the update the OTA gives you, so you're better off using whatever Android version and ROM you really like right now and then updating manually once the OTA comes out
I am a total noob when it comes to this. I have completely forgotten what I did when I updated to 4.0.4 + Yakju way back.
Here's what I have:
Running custom ROM AOKP on 4.0.4 IMM76D, Baseband I9250UGKL1
Yakju
Franco Kernel
It's rooted and unlocked I guess? I have clockwork rom manager thingy.
I have a backup to stock rom running 4.0.4
What I want:
To run the latest version of Jelly Beans for Galaxy Nexus on custom rom without wiping any data if possible.
If it wipes data what's the best way to revert back to what my phone setting was before?
Just flash the latest AOKP. I'm sure its advised that you wipe going to a 4.1.1 based ROM from a 4.0.4 based one, but you can probably get away with flashing over the top. Note that it's only going to work if you're staying with just an updated version of AOKP. You can't switch ROM makers.
Definitely make a nandroid backup of your current 4.0.4 setup before you go and flash it.
martonikaj said:
Just flash the latest AOKP. I'm sure its advised that you wipe going to a 4.1.1 based ROM from a 4.0.4 based one, but you can probably get away with flashing over the top. Note that it's only going to work if you're staying with just an updated version of AOKP. You can't switch ROM makers.
Definitely make a nandroid backup of your current 4.0.4 setup before you go and flash it.
Click to expand...
Click to collapse
Wow it's that simple?!
donatepresent said:
Wow it's that simple?!
Click to expand...
Click to collapse
Well, depends. Like I said if they advise that you wipe between flashes, then you'll have to do that.
martonikaj said:
Well, depends. Like I said if they advise that you wipe between flashes, then you'll have to do that.
Click to expand...
Click to collapse
You are the man! It worked like a charm!!! No wipe needed! Jelly Bean is awesomeee bro!!
donatepresent said:
You are the man! It worked like a charm!!! No wipe needed! Jelly Bean is awesomeee bro!!
Click to expand...
Click to collapse
Glad it worked.
Having come from flashing SGS have read up as much as I can regarding flashing the HOX.
Have held back having a crack at a custom ROM until Jellybean update arrives on stock, to see how it runs.
However, if I do upgrade to stock Jellybean (which would have a new HBOOT?) would it still be possible to load AOSP Rom after.
If i've read correctly, unless I have a Nandroid backup of a custom ROM (whether it be Jellybean or ICS), the new HBOOT will prevent an ICS based ROM but custom Jellybean should be ok?
Lazieye said:
Having come from flashing SGS have read up as much as I can regarding flashing the HOX.
Have held back having a crack at a custom ROM until Jellybean update arrives on stock, to see how it runs.
However, if I do upgrade to stock Jellybean (which would have a new HBOOT?) would it still be possible to load AOSP Rom after.
If i've read correctly, unless I have a Nandroid backup of a custom ROM (whether it be Jellybean or ICS), the new HBOOT will prevent an ICS based ROM but custom Jellybean should be ok?
Click to expand...
Click to collapse
It's a confusing, ill-explained situation a lot of people are confused about.
From what i understand, when upgrading to JellyBean (including the upgraded hboot), you can STILL flash ICS custom roms & nandroid back ups. However, what you will be unable to do is flash any sort of Ice cream sandwich RUU's. This is because, the upgraded hboot will cause errors in the installation (considering the hboot version in the RUU, will be of a totally different earlier version).
Hope this clears it up a little bit.
I rooted my phone & flashed Jelly Bean ROM - it wouldn't stop loading. So, tried to re-root, it did the same thing. I restored to stock. Stock isn't rooted so I re-rooted it from there.
So, with all that said, here is the question:
I want to install Jelly Bean. My understanding is that you must first upgrade to ICS, then to Jelly Bean. Is this the only way to go?
Thank you for your help!
:highfive:
No. What is your root method?
Eks Dee Aye said:
No. What is your root method?
Click to expand...
Click to collapse
odin/hercules......
I'm assuming it also flashed CWM to replace the stock recovery...or no?
no. i went from juggernaut5 (gb rom) to cm10 (jb rom). never visited ics. just flash like normal (twrp or cwm).
You may have just had a bad flash or bad download. Try again with a different dl (and maybe a different recovery).
Sent from my beastly Galaxy S 2.
I have a T-Mobile Galaxy S2. Rooted it withe hercules tar kernel on Android 2.3. When I upgraded to JB the kernel no longer worked (couldn't root). I tried flashing Cyangoen 10.0 and 9.0 but neither wokred (Waited 20 minutes and nothing). Is there a kernel I need to flash with ODIN?
Also, looking for a good place to learn abot kernels in genral.
Many thanks.
FezK
FezK said:
I have a T-Mobile Galaxy S2. Rooted it withe hercules tar kernel on Android 2.3. When I upgraded to JB the kernel no longer worked (couldn't root). I tried flashing Cyangoen 10.0 and 9.0 but neither wokred (Waited 20 minutes and nothing). Is there a kernel I need to flash with ODIN?
Also, looking for a good place to learn abot kernels in genral.
Many thanks.
FezK
Click to expand...
Click to collapse
Kernel is causing the problem. Flash only kernel which is made for specific rom/android version. follow this if you want to flash via Odin. I recommend you to install CWM because its easy,safe and time saving.
Installed CWM Recovery, tried to flash Cyanogen 9...now it keeps rebooting back into CWM...can't access the Recovery menu. I downloaded the updated kernel. How do I get it flashed?
I was able to connect via ODIN. Can't get recovery-clockwork-touch-6.0.3.1-hercules.tar to flash.
restart your computer log back in and use a different USB port and make sure you have all the DRIVERS for the phone plug it in flash the ODIN CWM file then you should flash an ICS ROM then flash JB to avoid any hiccups 2.3.4 is a big jump to JB might be giving you errors and you are rooted correct ?
Thank you. Yes I'm rooted an runnning smoothly with Juggernaut ROM for now. Want to change to Cyanogen 9.0. I'll flash the ODIN CWM file as you recommend. Where can I find a good ICS ROM and JB? Didn't know the jump from 2.3.4 to JB would be so big.
Many thanks.
what do you prefer the more stocky looking approach or you into AOKP/CM if you like stock then anything from PTMR and JAMISON904 are on point and very stable if you want some options and custom stuff look into the CM/AOKP around here in the development forums since you are rooted i would download a nice ICS you wont be on it long so doesnt matter lol and then finally jump ship to JB give it time for the battery to settle in becuase there was nothin like GB as far as the battery life goes this one guy who has amazing work and dedication http://goo.im/devs/Cl3Kener anything on there will do you justice when you get to the JB stage good luck and happy flashing!!
C13Kener DOES have some amazing stuff. Thanks. I see that he has a nice ICS stock ROM (Samsung-Stock-4.1.2-Tiberius-Kernel-1.1.zip). Can I just flash that from recovery or do I need to flash a new kernel via ODIN beforehand? Apprecaite your patience and help.
FezK said:
C13Kener DOES have some amazing stuff. Thanks. I see that he has a nice ICS stock ROM (Samsung-Stock-4.1.2-Tiberius-Kernel-1.1.zip). Can I just flash that from recovery or do I need to flash a new kernel via ODIN beforehand? Apprecaite your patience and help.
Click to expand...
Click to collapse
I think there is some confusion here. A ROM is not the same thing as a kernel.
I think thats where I'm having trouble. I have an older kernel (recovery-cwm-hercules.tar) and need to upgrade it before I can flash an ICS ROM. Don't know where to find kernels for the ROMS I want to flash. I thought some ROMs came with the kernel embedded in their zipfile, but finding thats not the case. ODIN is fairly easy to use, but I don't know where to find the right kernels for ROMs like Cyanogen.
FezK said:
I think thats where I'm having trouble. I have an older kernel (recovery-cwm-hercules.tar) and need to upgrade it before I can flash an ICS ROM. Don't know where to find kernels for the ROMS I want to flash. I thought some ROMs came with the kernel embedded in their zipfile, but finding thats not the case. ODIN is fairly easy to use, but I don't know where to find the right kernels for ROMs like Cyanogen.
Click to expand...
Click to collapse
Recovery is a tool used to flash ROMs and do backups.
TWRP and CWM are recoveries.
ROMs are the operating system of the phone. They come with a kernel. The kernel is what boots the phone into the OS. You can flash a different kernel if it matches the type of ROM you are on. I hope that clears up some of the confusion.