Database Info

Flashing question

I am new to the Charge but not rooting and Android. I came from the DX so the way things are done in this thing are different. Here's my question:
I am currently rooted and running a rom with a custom kernel. If I use Odin to flash the official software, will I also need to replace the kernel separately or will flashing the official software also restore the original kernel?

You will not need to replace anything, the Odin package is all in one. It will put you back to bare stock which means ROM, kernel, recovery, modem, you name it.
If you wouldn't mind helping could you link me to a rooting guide on a DX? Some general tips on rooting it would be very appreciated. My dad has one and I'd like to root/ROM it for him but i don't feel like studying up >_< Thanks!

Wrightperspective said:
I am new to the Charge but not rooting and Android. I came from the DX so the way things are done in this thing are different. Here's my question:
I am currently rooted and running a rom with a custom kernel. If I use Odin to flash the official software, will I also need to replace the kernel separately or will flashing the official software also restore the original kernel?
Click to expand...
Click to collapse
Odin will replace everything, including your kernel.

Thanks for the response. I got confused because I saw posts saying that some kernels were interchangeable but I didn't know if they meant that you would have to flash the kernel after you flash the rom or if you just flash a new rom and the kernel remains. Appreciate the response.

You have to flash kernal only on cmw versions and not all of them read the pre requisites it will tell you if the cwm version either do not or do.have a kernal included for example humble 5 cwm version I.believe u.have to flash a kernal prior to rebooting or stock recovery will over write cwm happened to me and learned my.lesson the hard way !!!
Sent from my Gummy Charged GBE 2.0 using xda premium

Okay...so flashing the stock file will also get rid of CWM, right?

Back to Honeycomb with Nandroid

I have a nandroid of my rooted honeycomb 3.2.1 install. If I want to flash the leaked stock ICS, is it possible to go back to the nandroid and then go back to stock recovery to install the leak?
I understand I can use the unrooting method but I'm just trying to understand this better and understand my options. I don't wish to go back to the stock images and lock the boot loader again just to flash the update and unlock and root again if I don't have to unless that is just the best way to do it.

crankerchick said:
I have a nandroid of my rooted honeycomb 3.2.1 install. If I want to flash the leaked stock ICS, is it possible to go back to the nandroid and then go back to stock recovery to install the leak?
I understand I can use the unrooting method but I'm just trying to understand this better and understand my options. I don't wish to go back to the stock images and lock the boot loader again just to flash the update and unlock and root again if I don't have to unless that is just the best way to do it.
Click to expand...
Click to collapse
I would really advise that you flash the most recent EOS wingray. Rom #36 and the GApps (Google System apps) package version 10. It seems to be more complete than the ota update, it's easier to flash and you preserve your root and recovery.

Thanks, nice to see someone offer a comparison of the two packages. I'm currently running EOS build 34 from the other night. I guess i was just curious about the stock update. I know there are still some things non-functional with eos and figured the stock rom would be completely functional minus whatever bugs. It does seem like a bit of work to flash it though, since the only thing i can seem to find on what to do is saying to unroot and relock using the moto stock files.
Seems like if im interested in trying a stock rom i shojld just wait for the ota and a rom made from it with root already.
I will miss the notification tray settings in eos if i go stock!

crankerchick said:
Thanks, nice to see someone offer a comparison of the two packages. I'm currently running EOS build 34 from the other night. I guess i was just curious about the stock update. I know there are still some things non-functional with eos and figured the stock rom would be completely functional minus whatever bugs. It does seem like a bit of work to flash it though, since the only thing i can seem to find on what to do is saying to unroot and relock using the moto stock files.
Seems like if im interested in trying a stock rom i shojld just wait for the ota and a rom made from it with root already.
I will miss the notification tray settings in eos if i go stock!
Click to expand...
Click to collapse
True, that.
EOS wingray version 36 with the version 10.1 GApps really fixed most of the remaining issues. There should be a new nightly and there is a new GApps 10.2 to flash today.

[Q] get back to stock kernel?

I need to get back to stock kernel for tf101.
Currently i'm running 8.5.6.13-root-cwm and clemsyn kernel version 22
and i'm looking to move to a stock .19(root+cwm) then move on to ICS using:
http://forum.xda-developers.com/showthread.php?t=1438433
where can i find the stock kernel i need and what is necessary to install it?

have a look here:
http://www.xdafileserver.nl/index.php?dir=ASUS/Asus+Transformer+(TF101)/ROMS/
especially in folder "stock rom by gee one"

Thank you, This will be very helpful!

This is still very helpful but i can only see that it has the ICS roms. looking for the HC rom that includes stock kernel, or stock kernel stand alone if either exists

Finky said:
I need to get back to stock kernel for tf101.
Currently i'm running 8.5.6.13-root-cwm and clemsyn kernel version 22
and i'm looking to move to a stock .19(root+cwm) then move on to ICS using:
http://forum.xda-developers.com/showthread.php?t=1438433
where can i find the stock kernel i need and what is necessary to install it?
Click to expand...
Click to collapse
Hi Finky,
because you have CWM already installed, I think you can just flash an ICS stock rom or custom rom.
for US read this:
http://forum.xda-developers.com/showthread.php?t=1622333
for ww read this:
http://forum.xda-developers.com/showthread.php?t=1627301
Make sure you read the threats because .21 has root problems, but make sure you install OTA root keeper.....in the developers forum are also CWM version of .17 that is rootable....read well before starting.
goodluck....

nlheiz said:
Hi Finky,
because you have CWM already installed, I think you can just flash an ICS stock rom or custom rom.
for US read this:
http://forum.xda-developers.com/showthread.php?t=1622333
for ww read this:
http://forum.xda-developers.com/showthread.php?t=1627301
Make sure you read the threats because .21 has root problems, but make sure you install OTA root keeper.....in the developers forum are also CWM version of .17 that is rootable....read well before starting.
goodluck....
Click to expand...
Click to collapse
So if i were to flash an ICS rom or HC rom, it will overwrite kernel and set it back to stock kernel?
Also i have made some system apk changes awhile back, would those be an issue?

Finky,
I just read the two threads, and it seems that every one with a custom kernel has problems. So, seems you just have to follow the thread that you put in your 1st post to make sure you get ride of your custom kernel.
Or, you can cwm flash the revolver rom (has the standard kernel of ICS inside) or one of the other custom roms (I use Revolver). that way you have ICS although it is custom. maybe that is some thing for you to do....or you want asus rom?

VRBLJ1 and VRALEC Bootchains - why exactly are they necessary?

ok so I was an original GS III owner (I preordered, used the original root66, waited for the unlocked bootloader, etc.)
I just rx'ed a 2nd replacement because the power button fell off my first replacement (my 1st gsIII had a faulty modem).
This one came preloaded with the 2nd OTA (VRALHE)
I was wondering the correct method to go about setting it up...
1.) odin the original root66 VRALF and continue in the same way I did with my original one (dd a TWRP and the insecure bootloader)?
2.) I could follow the directions in section 1 here: http://forum.xda-developers.com/showthread.php?t=1762709
and odin a pre-rooted VRBLJ1. It then says I can just go ahead and add a custom recovery (it mentions the EZ app but I'd rather just dd. then do the insecure aboot the same way)
3.) I could follow the directions here: http://forum.xda-developers.com/showthread.php?t=1974114
it mentions ODINing the VRBLJ1 leak and then ODINing a custom recovery but the recoveries INCLUDE "VRBLJ1 Bootchain." Why?
according to Invisiblek (http://rootzwiki.com/topic/29256-ro...-unlock-sch-i535-d2vzwverizon-galaxy-s-iii/):
What the locked bootloader prevents us from doing is flashing, via odin, a custom recovery or kernel. What we can do however, is revert to an older (semi-insecure) bootchain which we have acquired, flash our custom recovery, and then continue on from our freshly flashed custom recovery by flashing an unlocked bootloader and anything else we want.
Kernels from the newer OTA's prevent us from doing this process. We'll need to flash a kernel too...
Click to expand...
Click to collapse
he mentions flashing the VRALEC and then later (after flashing the VRALF2 kernel and a custom recovery) the VRALF2 bootchain. His explanation makes sense, but the other threads say to use the VRBLJ1 bootchain. why all the conflicting info?
Also, as I wrote this I used the rootDebugFS thing on my freshly rx'ed VRALHE. i then dd'ed a recovery and the insecure aboot. Everything is working fine. So what's all the fuss about? and will I encounter problems if I try to odin anything, like invisiblek said?
Thanks

preusstang said:
ok so I was an original GS III owner (I preordered, used the original root66, waited for the unlocked bootloader, etc.)
I just rx'ed a 2nd replacement because the power button fell off my first replacement (my 1st gsIII had a faulty modem).
This one came preloaded with the 2nd OTA (VRALHE)
I was wondering the correct method to go about setting it up...
1.) odin the original root66 VRALF and continue in the same way I did with my original one (dd a TWRP and the insecure bootloader)?
2.) I could follow the directions in section 1 here: http://forum.xda-developers.com/showthread.php?t=1762709
and odin a pre-rooted VRBLJ1. It then says I can just go ahead and add a custom recovery (it mentions the EZ app but I'd rather just dd. then do the insecure aboot the same way)
3.) I could follow the directions here: http://forum.xda-developers.com/showthread.php?t=1974114
it mentions ODINing the VRBLJ1 leak and then ODINing a custom recovery but the recoveries INCLUDE "VRBLJ1 Bootchain." Why?
according to Invisiblek (http://rootzwiki.com/topic/29256-ro...-unlock-sch-i535-d2vzwverizon-galaxy-s-iii/):
he mentions flashing the VRALEC and then later (after flashing the VRALF2 kernel and a custom recovery) the VRALF2 bootchain. His explanation makes sense, but the other threads say to use the VRBLJ1 bootchain. why all the conflicting info?
Also, as I wrote this I used the rootDebugFS thing on my freshly rx'ed VRALHE. i then dd'ed a recovery and the insecure aboot. Everything is working fine. So what's all the fuss about? and will I encounter problems if I try to odin anything, like invisiblek said?
Thanks
Click to expand...
Click to collapse
I'm assuming since VRBLJ1 is the newest JB leak then it uses the newer boot chain. The only reason you would need that boot chain to unlock the bootloader is if you used Odin to flash the newest VZW JB leak onto your phone. Then you would need it to unlock the VRBLJ1 JB leak. If you are are any of the ICS stock ROMs and want to unlock you can use the old way of doing it. The post you are reading from invisiblek is old, it was when we were on the VRALFW stock ROM.
Now I have no clue why you would want to use Odin to flash the newest JB leak when you can do it by downloading the version of the ROM made to be flashed with TWRP or CWM. I would love to have a dev or someone knowledgeable about these things to chime in and tell us if there is any benefit to using Odin to update to the newest JB leak or if there is no difference between having the JB leak or one of the OTA's on your phone before you flash a ROM.
Sent from one of the many Anthropomorphic Personalities on the Disc

shangrila500 said:
I'm assuming since VRBLJ1 is the newest JB leak then it uses the newer boot chain. The only reason you would need that boot chain to unlock the bootloader is if you used Odin to flash the newest VZW JB leak onto your phone. Then you would need it to unlock the VRBLJ1 JB leak. If you are are any of the ICS stock ROMs and want to unlock you can use the old way of doing it. The post you are reading from invisiblek is old, it was when we were on the VRALFW stock ROM.
Now I have no clue why you would want to use Odin to flash the newest JB leak when you can do it by downloading the version of the ROM made to be flashed with TWRP or CWM. I would love to have a dev or someone knowledgeable about these things to chime in and tell us if there is any benefit to using Odin to update to the newest JB leak or if there is no difference between having the JB leak or one of the OTA's on your phone before you flash a ROM.
Sent from one of the many Anthropomorphic Personalities on the Disc
Click to expand...
Click to collapse
Its just another way of basically doing the same thing. If your already rooted and have cwm recovery, then flashing a J1 rom via cwm or twrp recovery is by far the easiest method. Now if your stock and unrooted, it would be easier to odin root66 J1 , then unlock and get cwm recovery via the ez unlock/recovery apps. This is why I have 2 different methods in my guide...I also chose to not flash bootchains unless its a last resort because they can perma brick a device if something goes wrong. Also I like to use methods that dont trip the flash counter, makes for one less thing to do if the device ever needs to be returned.

droidstyle said:
Its just another way of basically doing the same thing. If your already rooted and have cwm recovery, then flashing a J1 rom via cwm or twrp recovery is by far the easiest method. Now if your stock and unrooted, it would be easier to odin root66 J1 , then unlock and get cwm recovery via the ez unlock/recovery apps. This is why I have 2 different methods in my guide...I also chose to not flash bootchains unless its a last resort because they can perma brick a device if something goes wrong. Also I like to use methods that dont trip the flash counter, makes for one less thing to do if the device ever needs to be returned.
Click to expand...
Click to collapse
Gotcha, that's been bothering me for a few days. I remember when I was flashing on my RAZR that the stock OTA was the base for everything and if you didn't have the latest OTA some of the ROMs wouldn't run on your phone until you updated and some of the older ROMs wouldn't work until they had been updated to work on the newest OTA or leak. The ROMs were just overlays and usually only added a little bit of added performance or functionality.
Would updating to the latest OTA via Odin add any benefits like it did on the RAZR ? I know the RAZR wasn't unlocked and we weren't flashing ROMs like we do on the GS3 but.....
Sent from one of the many Anthropomorphic Personalities on the Disc

no not on samsung devices...you can go from f2 to the latest with no issues.

droidstyle said:
no not on samsung devices...you can go from f2 to the latest with no issues.
Click to expand...
Click to collapse
No I get that, I was meaning are there any positive side effects from using the newest JB leak as your base ROM before flashing a new one. Like flashing the new JB leak via Odin, then unlocking and flashing a new ROM on top of it. Will there be any benefits like there were on the RAZR or when we flash in custom recoveries does it completely do away with the stock ROM that was on the system partition and replace it with whatever we flash? I know on the RAZR you would use the ROM you were on as a base you flash whatever else you wanted and there were benefits to having a certain OTA as your base before you flashed. I don't think I'm doing a very good job of phrasing my question, I apologize for that. Its just a hard question to put into words.
Sent from one of the many Anthropomorphic Personalities on the Disc

shangrila500 said:
No I get that, I was meaning are there any positive side effects from using the newest JB leak as your base ROM before flashing a new one. Like flashing the new JB leak via Odin, then unlocking and flashing a new ROM on top of it. Will there be any benefits like there were on the RAZR or when we flash in custom recoveries does it completely do away with the stock ROM that was on the system partition and replace it with whatever we flash? I know on the RAZR you would use the ROM you were on as a base you flash whatever else you wanted and there were benefits to having a certain OTA as your base before you flashed. I don't think I'm doing a very good job of phrasing my question, I apologize for that. Its just a hard question to put into words.
Sent from one of the many Anthropomorphic Personalities on the Disc
Click to expand...
Click to collapse
no not on samsung devices...the reason you needed to do that on the moto device is because of the locked bootloader. meaning you couldnt replace the kernel, so you had to ota to the latest, then root , recovery, and flash rom. since our device is fully unlocked, we dont have to worry about this. most if not all roms for d2vzw are packaged with a kernel. so it does not matter what current base your on, flashing a rom will overwrite it.

droidstyle said:
no not on samsung devices...the reason you needed to do that on the moto device is because of the locked bootloader. meaning you couldnt replace the kernel, so you had to ota to the latest, then root , recovery, and flash rom. since our device is fully unlocked, we dont have to worry about this. most if not all roms for d2vzw are packaged with a kernel. so it does not matter what current base your on, flashing a rom will overwrite it.
Click to expand...
Click to collapse
That's what I thought. I was just wanting a little clarification on that. Thanks man!!!
Sent from one of the many Anthropomorphic Personalities of the Disc

solved

Ok so im planning on flashing in cyanogenmod v9.1 and then up to ultragen v1.1 with the jb and tw5 taste, now if i do this do i still need to flash in a version of gapps or is there one in the ultragen rom, and in order to do the flashing can i use the cmw-based voodoo lagfix recover 5.0.2.7 to flash in the cm9.1 or do i need to use odin or something, im kinda new to all this, all ive done to the phone so far is recover from soft brick by using odin to flash back to stock and then using some off site instructions to root the phone which also apparently came along with the voodoo recovery, so im basically a noob at this

jimmy2989 said:
Ok so im planning on flashing in cyanogenmod v9.1 and then up to ultragen v1.1 with the jb and tw5 taste, now if i do this do i still need to flash in a version of gapps or is there one in the ultragen rom, and in order to do the flashing can i use the cmw-based voodoo lagfix recover 5.0.2.7 to flash in the cm9.1 or do i need to use odin or something, im kinda new to all this, all ive done to the phone so far is recover from soft brick by using odin to flash back to stock and then using some off site instructions to root the phone which also apparently came along with the voodoo recovery, so im basically a noob at this
Click to expand...
Click to collapse
No need to flash the gapps with Utragen ROM its included.
Use CM recovery to flash no need for Odin ... cm 5.0.2.x is fine.
I always go to cm 9 then work up never had a problem.
Ultragen is a very stable ICS based rom .. I used it for awhile.
Be sure you follow the OP`s flashing instructions.
If you want JB try slim 4.1.2 its very stable...if you can live
without GPS.
Sent from my Nexus 7 using xda premium

Thanks, everythings installed and its running beautifullyi thanked your post ill mark this thread as solved