So starting yesterday my droid dna has been stuck in a boot loop. I just bought it about 5 days ago.
It was rooted and running supercharged HTC sense rom and stock kernal.
I tried everything I could find online.
I relocked bootloader and restored rom using the RUU exe that everyone links, I re-unlocked installed the rom again to see if that would work and it allowed maybe 2 full boots out of 100+ tries occasionally it booted up and had several crashes on the supercharged that included the custom AC!D sound mod adn the UI would lock up if I tried to make or answer a call. I tried re-restoring with the RUU. all fastboot commands worked fine with no error on restoring the bootloader and recovery etc.
NOTHING is working. Please help for the love of my brand new droid dna which has already boot looped...
Have you tried just restoring from your backup? The one you made before flashing the rom
And just curious. Did you dirty flash it? What recovery are you using?
Sent from my SuperCharged DNA
You're supposed to use the kernel that's supplied with the rom, not the stock kernel.
croppz said:
Have you tried just restoring from your backup? The one you made before flashing the rom
And just curious. Did you dirty flash it? What recovery are you using?
Sent from my SuperCharged DNA
Click to expand...
Click to collapse
I tried that and it didn't work, I don't think I dirty flashed as I wiped data.
orangechoochoo said:
You're supposed to use the kernel that's supplied with the rom, not the stock kernel.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=36676709
I didn't and don't see any kernal mention on this rom's post.
Egodeath said:
I tried that and it didn't work, I don't think I dirty flashed as I wiped data.
http://forum.xda-developers.com/showthread.php?p=36676709
I didn't and don't see any kernal mention on this rom's post.
Click to expand...
Click to collapse
There's a discussion in that thread about the developer including the kernel in the rom, doing that won't flash the kernel. It doesn't look like the instructions were updated to reflect that. Try Supercharged Hatka, made by the same developer along with Mustafa.
I managed to get it to boot up as stock with a 2nd relocking using fastboot oem lock and the RUU.exe. Haven't had any issues yet. I will see if anything goes wrong. Made a few calls and restored off gmail account.
Now that you got it running don't use that Rom this time, try Supercharged Hatka or Viper.
orangechoochoo said:
There's a discussion in that thread about the developer including the kernel in the rom, doing that won't flash the kernel. It doesn't look like the instructions were updated to reflect that. Try Supercharged Hatka, made by the same developer along with Mustafa.
Click to expand...
Click to collapse
I even asked the guy in the thread if the rom is stable on stock kernal and he stated that it was. I didnt read the whole thread but I didnt see anything about a kernal included. I know some are running cubed with it. Regardless, it worked fine on my device, I went back to stock just because Im looking to try out viper or hatka
Sent from my SuperCharged DNA
Maybe. There are so many boot.img files floating around things get mixed up and sometimes you forget what kernel you're running until you look at the About phone menu. It would be nice if they could be named appropriately.
orangechoochoo said:
Maybe. There are so many boot.img files floating around things get mixed up and sometimes you forget what kernel you're running until you look at the About phone menu. It would be nice if they could be named appropriately.
Click to expand...
Click to collapse
Now that I look, kernal definitely doesnt look stock but im just going off the name. Never looked before so I dunno what the name would have been.
Sent from my SuperCharged DNA
Yours looks stock. Covxx said he put DSBs kernel in the rom but it has to be flashed separately to apply it, therefore DSBs kernel is not flashed and you remain on the stock kernel. Dsb has his name in the kernel version when you look at About Phone.
orangechoochoo said:
Yours looks stock. Covxx said he put DSBs kernel in the rom but it has to be flashed separately to apply it, therefore DSBs kernel is not flashed and you remain on the stock kernel. Dsb has his name in the kernel version when you look at About Phone.
Click to expand...
Click to collapse
Gotcha. Thanks man.
Sent from my SuperCharged DNA
Related
Here's the stock kernel from software ver 1.13.651.7, flashable through recovery, of course.
Thank you.
Sent from my PG86100 using XDA Premium App
Thanx for this.
Sent from my PG86100 using XDA Premium App
Finally! Thanks man!
Wow thanks.
thanks.........
Thanks dude. Not sure what I did but my battery started discharging crazy fast this morning, I had to switch back to stock.
[Kernel] Modified Stock 2.08.651.2 (2.6.35.13-g84f8edd)
Adding new kernel to new post.
Good looking man. Thanks.
Locked & Loaded
" Shooter on Deck"
Has anyone flashed this kernel?
I downloaded this from the link at the top, and flashed via TWRP recovery (yes I did wipe the caches).
After I rebooted, I checked the Kernel version, and either it didn't work, or the version of this kernel is the same as the original one I had, 1.11.651.3. In fact, I tried this twice, but the results are still the same.
Am I missing something?
Dudemeister said:
Has anyone flashed this kernel?
I downloaded this from the link at the top, and flashed via TWRP recovery (yes I did wipe the caches).
After I rebooted, I checked the Kernel version, and either it didn't work, or the version of this kernel is the same as the original one I had, 1.11.651.3. In fact, I tried this twice, but the results are still the same.
Am I missing something?
Click to expand...
Click to collapse
Do you have hboot 1.5? Just asking because there are ~2 more steps to take before flashing a kernel... Or I heard you can use Flash Image GUI.
Sent from my Infected EVO3D! Virus, you rock!
I flashed a AOSP kernel, and my rom didn't load. so I restored a backup and my wifi didn't work and also. So i flashed this kernel and now my backup doesn't work or even any rom that I have downloaded.
using viperrom before.
now nothing is working
questions is:
1. is there a way to flash a kernel, using recovery?
2. what roms work with this kernal?
im getting really sick of this evo3d.
TheFlatulentFox said:
questions is:
1. is there a way to flash a kernel, using recovery?
2. what roms work with this kernal?
Click to expand...
Click to collapse
1. Yes, so long as you are NOT HBOOT 1.5
2. This is a stock HTC Sense kernel as clearly outlined in the OP. It is not AOSP.
SteelH said:
1. Yes, so long as you are NOT HBOOT 1.5
2. This is a stock HTC Sense kernel as clearly outlined in the OP. It is not AOSP.
Click to expand...
Click to collapse
yeah I have Hboot 1.5
and I know I installed a kernel for AOSP and downloaded an AOSP rom. I should have said that before. but The AOSP rom didnt load, it just hanged on the HTC screen. So i recovered my backup using still on the AOSP kernel, it worked excluding WIFI and some other stuff. so I installed this kernel using GUI app, and restored my back up again. and now it just hangs.
now I can't find a rom for this kernel I downloaded three different roms, all sense. none of them are working.
TheFlatulentFox said:
yeah I have Hboot 1.5
and I know I installed a kernel for AOSP and downloaded an AOSP rom. I should have said that before. but The AOSP rom didnt load, it just hanged on the HTC screen. So i recovered my backup using still on the AOSP kernel, it worked excluding WIFI and some other stuff. so I installed this kernel using GUI app, and restored my back up again. and now it just hangs.
now I can't find a rom for this kernel I downloaded three different roms, all sense. none of them are working.
Click to expand...
Click to collapse
Someone correct me if I'm wrong, but I'm almost positive this kernel is WAY outdated (note the date of the OP)
I am rooted (SuperCID 11111111 method), and s-off. I did not install any OTA's and i'm on stock kernal and ROM.
For my first custom ROM I want to install the ViperDNA ROM. Now that we have S-OFF, do we still need to install the "Stock DSB System Write Boot.img" Kernal? I could be wrong, but I believe that kernal is the same as stock but with system write capabilities which we can now do with S-OFF. Are there any other benefits to the DSB kernal that we may need for the ViperDNA?
Another small minor question while i'm at it: I haven't experienced any wifi issues, dose anyone recommend installing the new radios or anything else from the latest ota? Also should I wait for ViperDNA 1.2 or is it ok to start with 1.1?
Thank you in advance for your help. This is the first time I had to ask a question, I usually find what i'm looking for by reading the threads. I would have asked in the ViperDNA thread but this is my first post.
Thanks
I would do it just to be safe and I flashed the new radios and got faster 4g but only slightly faster
Sent from my ViperDNA infected with ViperBlue DNA
devilsaces said:
I am rooted (SuperCID 11111111 method), and s-off. I did not install any OTA's and i'm on stock kernal and ROM.
For my first custom ROM I want to install the ViperDNA ROM. Now that we have S-OFF, do we still need to install the "Stock DSB System Write Boot.img" Kernal? I could be wrong, but I believe that kernal is the same as stock but with system write capabilities which we can now do with S-OFF. Are there any other benefits to the DSB kernal that we may need for the ViperDNA?
Another small minor question while i'm at it: I haven't experienced any wifi issues, dose anyone recommend installing the new radios or anything else from the latest ota? Also should I wait for ViperDNA 1.2 or is it ok to start with 1.1?
Thank you in advance for your help. This is the first time I had to ask a question, I usually find what i'm looking for by reading the threads. I would have asked in the ViperDNA thread but this is my first post.
Thanks
Click to expand...
Click to collapse
DSB's Stock kernel is a part of the Viper ROM so no need to install separately. Installing new radio or the whole firmware is pretty much up to you. I have not received any faster data speeds with new one but some have. Also waiting for Viper 1.2 is also up to you, nits hinted that we may have it this weekend. It is an awesome ROM. The only thing with not waiting is that 1.2 will require a full wipe but if you are not opposed to taht like most of us flashaholics then go for it. You need to install 1.1.0 then there will be three small ota's that you will have to do one at a time to get to current 1.1.3.
Thanks for the quick responses. I might not have time to flash until this weekend anyway so maybe i'll wait for 1.2 just so I only have to wipe once. ViperDNA looks great, can't wait to mess around with it. I was a flashaholic with my Thunderbolt but I need to relax a little more with the DNA...Maybe.
devilsaces said:
Thanks for the quick responses. I might not have time to flash until this weekend anyway so maybe i'll wait for 1.2 just so I only have to wipe once. ViperDNA looks great, can't wait to mess around with it. I was a flashaholic with my Thunderbolt but I need to relax a little more with the DNA...Maybe.
Click to expand...
Click to collapse
lol, yeah. I think I flashed every rom there was for the Inc. and was doing same on DNA until Viper came out - it has everything. Can do as much or as little as you want with tweaks. Now I only flash when Viper has an update requiring one!
TJMac44 said:
lol, yeah. I think I flashed every rom there was for the Inc. and was doing same on DNA until Viper came out - it has everything. Can do as much or as little as you want with tweaks. Now I only flash when Viper has an update requiring one!
Click to expand...
Click to collapse
Yeah, I can't remember a ROM for the thunderbolt that had the same level of customization as Viper. TBolt ROMS went more in the direction of trying to get the latest sense roms, most felt unstable, or to get ASOP. I have my ASOP fix with my Nexus 7 now so I don't mind sticking with just sense based roms.
TJMac44 said:
DSB's Stock kernel is a part of the Viper ROM so no need to install separately. Installing new radio or the whole firmware is pretty much up to you. I have not received any faster data speeds with new one but some have. Also waiting for Viper 1.2 is also up to you, nits hinted that we may have it this weekend. It is an awesome ROM. The only thing with not waiting is that 1.2 will require a full wipe but if you are not opposed to taht like most of us flashaholics then go for it. You need to install 1.1.0 then there will be three small ota's that you will have to do one at a time to get to current 1.1.3.
Click to expand...
Click to collapse
I just flashed the new radio, planning on flashing ViperDNA this weekend.
After doing a little more research I came across this post:
http://forum.xda-developers.com/showpost.php?p=37535001&postcount=1
It turns out that there are 2 parts to a kernal, the kernal modules and the boot.img. I guess I DO need to flash the boot.img separately. The modules are already packaged with the ViperDNA Rom. Does this sound correct? When I was flashing ROMs with my TBolt I usually flashed different kernals separately so they were already together.
uppon2 said:
Keep in mind bootloader unlock will not work if you have done the latest OTA update without previously using supercid. See bootloader unlock guide below for more details.
3. You now need all required kernel files you are planning to use with the ROM you have selected. Now for the Droid DNA at the moment the kernel is broken down in to 2 parts. The first file is kernel modules and the second file is the the boot.img. Now whatever ROM you choose to download and install, it should already be using a specific kernel. When you flash a ROM the kernel modules will already be installed for the specific kernel the ROM is using.
For example If you listened to my advice and are going to use ViperDNA, this ROM already comes with the kernel modules required for the kernel it is using. The only thing that is left for you to do is download the second part of the kernel which is the boot.img file. Every kernel needs both the kernel modules and boot.img files to work 100% without fault, and every kernel has different modules and a boot.img that will only work for that specific kernel.
Each ROM should give you a download link for the required boot.img so just make sure to read the first few posts - If you are planning to use ViperDNA then it can be found on the first page post number 2 of the ViperDNA thread and it is named Stock DSB System Write Boot.img -
* If that wasn't already clear enough I would like to say that if you are download a complete kernel zip separately (which you can do) then you will get both files required. The first is the "already included in the ROM" kernel modules and the second file will be the boot.img - You can find all of the different kernels here - as you can see in this list the kernel included in ViperDNA is the one named "[KERNEL]Droid DNA Cubed Kernel Stock" - Once you have finished installing a ROM then I would recommend having a look at some different kernels if you want. Down the very bottom of this post I have included instructions on how to flash a kernel so please check it out.*
Click to expand...
Click to collapse
I have flashed paranoidandroid 3.15 on my galaxy s3 a couple weeks ago, aside the occasional screen that win't turn on I haven't had any problem, but I set my mind on flashing a new kernel in order to be able to change thez governor. I tried to flash air kernel on, I did exactly what I was told: Boot into recovery, clear cache/delvik, installed kernel from sd card, and rebooted. But after the phone being rebooted, I still had the stock kernel.
My question is, why did this happen, and how do I fix it?
All help is appreciated
what recovery? link to the kernel?
Glebun said:
what recovery? link to the kernel?
Click to expand...
Click to collapse
I'm running TWRP ( Team Win Recovery Project)
http://forum.xda-developers.com/showthread.php?t=1469842 link to the kernel, although if you know any kernels that work better/ more appropriate for ParanoidAndroid, I am more than open to suggestions
vonniel said:
I'm running TWRP ( Team Win Recovery Project)
http://forum.xda-developers.com/showthread.php?t=1469842 link to the kernel, although if you know any kernels that work better/ more appropriate for ParanoidAndroid, I am more than open to suggestions
Click to expand...
Click to collapse
Kernel is for nexus s not galaxy s3
Sent from my GT-I9300 using xda premium
wow, you're lucky the updater-script saved your phone. Flashing wrong firmware will kill it
Glenbun. Only mismatched, corrupted, or missing boot loaders can kill a phone.
yeah-yeah, but we should scare the noobs away from flashing the wrong firmware that potentially includes a bootloader
Glebun said:
yeah-yeah, but we should scare the noobs away from flashing the wrong firmware that potentially includes a bootloader
Click to expand...
Click to collapse
Glebun u have a point, even other incompatible components of recovery zip packages can brick the phone.
Sent from my Supercharged V12 Samsung Galaxy S3 using Tapatalk
Glebun said:
wow, you're lucky the updater-script saved your phone. Flashing wrong firmware will kill it
Click to expand...
Click to collapse
Wow, I feel so dumb ^^' I'll be more careful next time around.
What kernel would you recommend for me?
I recommed stock mb5 or speedmod k2-12 kernels for you
Bahadirafro said:
I recommed stock mb5 or speedmod k2-12 kernels for you
Click to expand...
Click to collapse
Well, I don't really know either of them, I don't mind stock, but I want to change things, sometimes it just isn't up for the task, or uses up battery when I would rather it didn't, without even knowing what they do, and looking around, I found the perseus kernel, I would like some opinions on the kernel, I would be very grateful if you told me if it fits me, if it's compatible with ParanoidAndroid, and finally if you have a better suggestion for a kernel.
http://forum.xda-developers.com/showthread.php?t=1691401
read the first post of the thread to find out if it's compatible with your ROM.
and try it to see if it suits you
If I'm running TWRP can I still download kernels that say they are meant for CWM?
yes
I recently picked up a GP 4.2. I immediately got it rooted so now I'm running a 2.3.6 stock rom with root. What's the next step in terms of getting a recovery installed and maybe moving up to an ICS or JB rom? I've kind of poked around a bit but it's some what confusing with all the other types of GPs in the same area. Does anybody have a recovery and rom they'd recommend? Is using rom manager to push CWM feasible?
I would recommend the ChaOS ROM/Kernel which includes CWM. It is one of the few available ROMs for this device right now but offers a lot of great features. You can also install an S3 or Jelly Bean theme with the ChaOS ROM. Here's the link to the ROM: http://forum.xda-developers.com/showthread.php?t=2279806. I do not believe using ROM manager to push CWM is feasible on this device. Also, CM7 will most likely make it on to this device very soon. I would recommend watching for that in the near future. I know it can be a hassle trying to weed through the Galaxy Player forums to find 4.2 information but it's all we've got. Hope this helps and welcome to the SGP 4.2 community!
MetaMav said:
I would recommend the ChaOS ROM/Kernel which includes CWM. It is one of the few available ROMs for this device right now but offers a lot of great features. You can also install an S3 or Jelly Bean theme with the ChaOS ROM. Here's the link to the ROM: http://forum.xda-developers.com/showthread.php?t=2279806. I do not believe using ROM manager to push CWM is feasible on this device. Also, CM7 will most likely make it on to this device very soon. I would recommend watching for that in the near future. I know it can be a hassle trying to weed through the Galaxy Player forums to find 4.2 information but it's all we've got. Hope this helps and welcome to the SGP 4.2 community!
Click to expand...
Click to collapse
Thank you for the info Meta. I'm somewhere around the mid-high mid level with flashing and rooting but slogging through trying to find the right info for a GP 4.2 was getting a bit hectic. I think part of it was the way some people abbreviate the model compared to others. I just wanted to make sure I didn't brick the device.
I got it mainly for a perm, in-car music and GPS/navigation provider instead of always looking to my phone to do it. One thing I noticed about the rom, it mentions installing it via CWM. If I don't have CWM yet, can this rom get pushed by odin or do I have to get CWM first and then flash the rom?
NapalmDawn said:
Thank you for the info Meta. I'm somewhere around the mid-high mid level with flashing and rooting but slogging through trying to find the right info for a GP 4.2 was getting a bit hectic. I think part of it was the way some people abbreviate the model compared to others. I just wanted to make sure I didn't brick the device.
I got it mainly for a perm, in-car music and GPS/navigation provider instead of always looking to my phone to do it. One thing I noticed about the rom, it mentions installing it via CWM. If I don't have CWM yet, can this rom get pushed by odin or do I have to get CWM first and then flash the rom?
Click to expand...
Click to collapse
you should flash CWM via odin first and then flash the ROM via CWM
Would the instructions here be the right thing to do?
http://www.youtube.com/watch?v=-MbHDbjph8A
MetaMav said:
I would recommend the ChaOS ROM/Kernel which includes CWM. It is one of the few available ROMs for this device right now but offers a lot of great features. You can also install an S3 or Jelly Bean theme with the ChaOS ROM. Here's the link to the ROM: http://forum.xda-developers.com/showthread.php?t=2279806. I do not believe using ROM manager to push CWM is feasible on this device. Also, CM7 will most likely make it on to this device very soon. I would recommend watching for that in the near future. I know it can be a hassle trying to weed through the Galaxy Player forums to find 4.2 information but it's all we've got. Hope this helps and welcome to the SGP 4.2 community!
Click to expand...
Click to collapse
Do you know if CM will come to the 3.6 as well? And from what I understand, to get CWM on the 3.6 you have to flash a custom kernel?
NapalmDawn said:
Would the instructions here be the right thing to do?
http://www.youtube.com/watch?v=-MbHDbjph8A
Click to expand...
Click to collapse
Yes. Those instructions are correct. However, you do not need to run the adb dev tool like the person does in the beginning of video in order to boot into download mode. You can just hold the power, home, and down-volume button to boot the phone into download mode before using Odin. Zaclimon's CWM kernel can be found here (along with the wifi fix): http://forum.xda-developers.com/showthread.php?t=2198444 and installed with the instructions in the youtube video.
Xenphor said:
Do you know if CM will come to the 3.6 as well? And from what I understand, to get CWM on the 3.6 you have to flash a custom kernel?
Click to expand...
Click to collapse
From what I have read I know that SerkTheTurk is currently compiling CM for the 4.2. I would imagine either him or some other 3.6 dev will take up the task of CM for your device. And, the answer to your second question is yes, you do have to flash a custom kernel similar to how the 4.2 requires a custom kernel.
Hope that helps.
MetaMav said:
Yes. Those instructions are correct. However, you do not need to run the adb dev tool like the person does in the beginning of video in order to boot into download mode. You can just hold the power, home, and down-volume button to boot the phone into download mode before using Odin. Zaclimon's CWM kernel can be found here (along with the wifi fix): http://forum.xda-developers.com/showthread.php?t=2198444 and installed with the instructions in the youtube video.
From what I have read I know that SerkTheTurk is currently compiling CM for the 4.2. I would imagine either him or some other 3.6 dev will take up the task of CM for your device. And, the answer to your second question is yes, you do have to flash a custom kernel similar to how the 4.2 requires a custom kernel.
Hope that helps.
Click to expand...
Click to collapse
Ok thanks. I also have a question regarding flashing kernels. In the linux world (and other os world), randomly changing your kernel is a big no no that would lead to major compatibility issues. I don't understand how people can mix and match kernels, roms, firmware, bootloaders, recoveries and everything else? There won't be conflicts?
Regarding the kernel available for the 3.6: what do I do if I encounter stability issues with it and, say, the upcoming CM7? I wouldn't be able to go back to my original kernel because I didn't have CWM to back it up in the first place. Won't I be stuck with a potentially faulty kernel?
Xenphor said:
Ok thanks. I also have a question regarding flashing kernels. In the linux world (and other os world), randomly changing your kernel is a big no no that would lead to major compatibility issues. I don't understand how people can mix and match kernels, roms, firmware, bootloaders, recoveries and everything else? There won't be conflicts?
Regarding the kernel available for the 3.6: what do I do if I encounter stability issues with it and, say, the upcoming CM7? I wouldn't be able to go back to my original kernel because I didn't have CWM to back it up in the first place. Won't I be stuck with a potentially faulty kernel?
Click to expand...
Click to collapse
In changing kernels in the android world, you have mixed results. There are times a kernel can cause some issues but for the most part (we're talking like 98%), if an XDA dev posts a kernel and lets you know you can use it, you can trust it. These devs no matter the device spend painstaking hours ironing things out. Also, many of them have a select group of people testing the kernel for faults and issues. In a very active community, if a well known dev posts a kernel, you can trust it. HOWEVER...no matter what we think or believe or what we're told, every device is a unique and beautiful snowflake. Back up back up back up BACK UP BACK UP BACK UP your stuff. If you want to be super ULTRA safe, take the back up and download it to your PC or somewhere safe.
NapalmDawn said:
In changing kernels in the android world, you have mixed results. There are times a kernel can cause some issues but for the most part (we're talking like 98%), if an XDA dev posts a kernel and lets you know you can use it, you can trust it. These devs no matter the device spend painstaking hours ironing things out. Also, many of them have a select group of people testing the kernel for faults and issues. In a very active community, if a well known dev posts a kernel, you can trust it. HOWEVER...no matter what we think or believe or what we're told, every device is a unique and beautiful snowflake. Back up back up back up BACK UP BACK UP BACK UP your stuff. If you want to be super ULTRA safe, take the back up and download it to your PC or somewhere safe.
Click to expand...
Click to collapse
Well that's my dilemma because in order to backup my kernel I first need to flash the custom kernel to get CWM. What do I do?
Xenphor said:
Well that's my dilemma because in order to backup my kernel I first need to flash the custom kernel to get CWM. What do I do?
Click to expand...
Click to collapse
Just flash the cwm kernel because its basically the stock kernel but with cwm, and it shouldnt brick but if it does you can flash the stock kernel back again
Sent from my YP-GI1 using Tapatalk 2
SerkTheTurk said:
Just flash the cwm kernel because its basically the stock kernel but with cwm, and it shouldnt brick but if it does you can flash the stock kernel back again
Sent from my YP-GI1 using Tapatalk 2
Click to expand...
Click to collapse
Where could I find a stock kernel?
Xenphor said:
Where could I find a stock kernel?
Click to expand...
Click to collapse
US version: http://forum.xda-developers.com/showthread.php?t=1885374
International: http://forum.xda-developers.com/showthread.php?t=1884071
Sent from my YP-GI1 using Tapatalk 2
SerkTheTurk said:
US version: http://forum.xda-developers.com/showthread.php?t=1885374
International: http://forum.xda-developers.com/showthread.php?t=1884071
Sent from my YP-GI1 using Tapatalk 2
Click to expand...
Click to collapse
Ok thank you. However, will this work with YP-GS1?
But about kernels, on the webpage where I downloaded the stock rooted rom http://tau.shadowchild.nl/attn1/?p=166 it says specifically that the Wifi module in system and kernel must MATCH. This is what I'm talking about in regards to kernel compatibility with roms. How do I know if a kernel I'm downloading will have changes applied to it that will work with another rom like with this stock rom/kernel?
Well in order-I used odin to flash CWM. Once it rebooted, I saw the Galaxy SII boot anim. Used Rom Manager to have it boot to CWM. From there I flashed wifi fix, the rom and then the mod pack. My build number is gingerbread-ueld3. From what I can tell, I think I'm all done. At first I was like hrmmmmm. Doesn't look much different. When I hit the toggle bar though, I could tell it had changed. The process was all very simple after I got headed in the right direction with CWM. That was my only confusing start point for this.
Edit-my bad. The rom didn't take on the first flash. I could tell by the build number. Reflashing the rom and the s3 addons. Hrmmm. Might be boot looping. It's going through the comet and coming up to the white samsung, vibrates a few times after a bit and goes back to the comet with no sound.
NapalmDawn said:
Well in order-I used odin to flash CWM. Once it rebooted, I saw the Galaxy SII boot anim. Used Rom Manager to have it boot to CWM. From there I flashed wifi fix, the rom and then the mod pack. My build number is gingerbread-ueld3. From what I can tell, I think I'm all done. At first I was like hrmmmmm. Doesn't look much different. When I hit the toggle bar though, I could tell it had changed. The process was all very simple after I got headed in the right direction with CWM. That was my only confusing start point for this.
Edit-my bad. The rom didn't take on the first flash. I could tell by the build number. Reflashing the rom and the s3 addons. Hrmmm. Might be boot looping. It's going through the comet and coming up to the white samsung, vibrates a few times after a bit and goes back to the comet with no sound.
Click to expand...
Click to collapse
Well I had to flash this kernel http://forum.xda-developers.com/showthread.php?t=2198234 to get CWM on mine. I haven't actually flashed anything with CWM because there doesn't seem to be any good roms for the 3.6 unless CM7 comes out sometime. I used Odin to flash a stock rom from here http://tau.shadowchild.nl/attn1/?p=166
NapalmDawn said:
Well in order-I used odin to flash CWM. Once it rebooted, I saw the Galaxy SII boot anim. Used Rom Manager to have it boot to CWM. From there I flashed wifi fix, the rom and then the mod pack. My build number is gingerbread-ueld3. From what I can tell, I think I'm all done. At first I was like hrmmmmm. Doesn't look much different. When I hit the toggle bar though, I could tell it had changed. The process was all very simple after I got headed in the right direction with CWM. That was my only confusing start point for this.
Edit-my bad. The rom didn't take on the first flash. I could tell by the build number. Reflashing the rom and the s3 addons. Hrmmm. Might be boot looping. It's going through the comet and coming up to the white samsung, vibrates a few times after a bit and goes back to the comet with no sound.
Click to expand...
Click to collapse
Poop. I think I bootloped the sucker. I can use Odin to reflash the stock, rooted rom just like I did when I got it first rooted right? Do we have another rom for the 4.2 I could try flashing? Not sure why it has bootlooped. I even went back into CWM, did a factory reset, flashed only the rom (no addons) and same thing. Possible bad download? It is flashing from the internal SD as my CWM is not seeing my external SD.
NapalmDawn said:
Poop. I think I bootloped the sucker. I can use Odin to reflash the stock, rooted rom just like I did when I got it first rooted right? Do we have another rom for the 4.2 I could try flashing? Not sure why it has bootlooped. I even went back into CWM, did a factory reset, flashed only the rom (no addons) and same thing. Possible bad download? It is flashing from the internal SD as my CWM is not seeing my external SD.
Click to expand...
Click to collapse
I have been meaning to post this on the dev thread for awhile. I thought this problem might only be for certain people but I think it applies to US and maybe non-EU devices. I believe that the ChaOS ROM will bootloop on US (YP-GI1/XAA) devices if you do not install ChaOS's Enhanced Stock ROM (http://forum.xda-developers.com/showthread.php?t=2279450) for whatever reason. I spent days trying to install his ROM and bootlooping.
The way I successfully installed (if I remember correctly):
-Do a factory reset of rooted stock ROM
-Boot to CWM (meaning you have already flashed the custom kernel) and install ChaOS's Enhanced Stock (put all install files on internal SD)
-Boot to CWM, wipe davlick cache under "advanced", wipe cache partition, and install the ChaOS ROM
-Wait a little while and your device should boot up properly
I hope this works for you. If it doesn't let me know and I can help you further. If this does work for you too then I will post this on the ROM's thread for other users.
Xenphor said:
Well that's my dilemma because in order to backup my kernel I first need to flash the custom kernel to get CWM. What do I do?
Click to expand...
Click to collapse
SerkTheTurk said it very well, you do not need to worry, but if you also want to do a backup before you install the custom kernel you could use the adb tools on the computer to backup the device. I'm sure you could learn how to do that with a quick Google search.
MetaMav said:
I have been meaning to post this on the dev thread for awhile. I thought this problem might only be for certain people but I think it applies to US and maybe non-EU devices. I believe that the ChaOS ROM will bootloop on US (YP-GI1/XAA) devices if you do not install ChaOS's Enhanced Stock ROM (http://forum.xda-developers.com/showthread.php?t=2279450) for whatever reason. I spent days trying to install his ROM and bootlooping.
The way I successfully installed (if I remember correctly):
-Do a factory reset of rooted stock ROM
-Boot to CWM (meaning you have already flashed the custom kernel) and install ChaOS's Enhanced Stock (put all install files on internal SD)
-Boot to CWM, wipe davlick cache under "advanced", wipe cache partition, and install the ChaOS ROM
-Wait a little while and your device should boot up properly
I hope this works for you. If it doesn't let me know and I can help you further. If this does work for you too then I will post this on the ROM's thread for other users.
SerkTheTurk said it very well, you do not need to worry, but if you also want to do a backup before you install the custom kernel you could use the adb tools on the computer to backup the device. I'm sure you could learn how to do that with a quick Google search.
Click to expand...
Click to collapse
ell there's not really much point in backing up the kernel when I've already downloaded it on my computer.
I've since flashed KingOS rom and don't really notice any differences at besides a few color changes... what's all the hype about?
Xenphor said:
ell there's not really much point in backing up the kernel when I've already downloaded it on my computer.
I've since flashed KingOS rom and don't really notice any differences at besides a few color changes... what's all the hype about?
Click to expand...
Click to collapse
Xen-it seems GPlayer development is still fairly newish. the work you see from devs now are all ground work. For the 4.2 and 3.6, they seem a little less dev populated than the 4 and 5. People will build upon the work of early devs and eventually get kernels that can OC and maybe ICS and JB roms. At this stage, we likely won't see anything like ZOMG earth shattering until people spend time with the devices. Seems Serk is on his way to doing the best he can for 4.2 but I am not sure who is tackling 3.6
It's weird how roms for devices go. I learned this when I had a tbolt and shockingly saw a FUNCTIONAL JB rom for my old Eris while the tbolt was still hanging back in ginger land with not even a really good ICS rom let alone JB. I asked the Tbolt community-why? How is it the dinosaur Eris has JB and not us? It all depends on what the devs can do with the sources provided. Sometimes certain hardware points are sticky. you can have beautiful JB rom for a device that can't talk to the camera if the hardware source isn't made available (reference the HP TP for many years)
For now, flash what you're comfortable with and and learn what you do and don't like. Also learn if you want to play things safe and not experiment or take on potentially beta builds. For the tbolt, tackling an ICS rom was too dicey so I never did. On my new Rezound, I eat up JB roms as they are in much better shape
Hi, just bought an og ,coming from HTC phone. There r some new things it looks like. What is a EFS ? Back up EFS partition ? I'm gonna used the my att og on straight talk , any things I should watch out for ? Should stay 100 % stock until service is activated? I'm looking for a near stock stable optimized rom, any to recommend ? Which kernel is good for it ? Htcs have hboot , it looks like lgs use different things , how do I go around flashing radios ? Excuse me for throwing out tons of noob questions , gonna start somewhere
0 help lol
Welcome. There is a zip file that you put on your external SD card somewhere in the optimus g forums that will backup your efs partition.
Edit: I found it for you if you haven't had any luck finding it. Also.. The efs supposedly holds your imei number and stuff.
http://forum.xda-developers.com/showthread.php?t=2164749
Sent from my Optimus G using xda app-developers app
Ic, so how would EFS be deleted ? always just had CDMA phones, never heard of ESNs deleted by mistake. Are radios to be flashed in recovery too ? My HTC flashes radios in fastboot.
Optimus 3D
optimusv45 said:
Ic, so how would EFS be deleted ? always just had CDMA phones, never heard of ESNs deleted by mistake. Are radios to be flashed in recovery too ? My HTC flashes radios in fastboot.
Click to expand...
Click to collapse
It is real, there are a lot of hard bricks because of it, look in the Optimus 3D P920 forum, a lot people lost their IMEI and couldn't get it going. And yes, you can flash different radios
whats a very stable and optimized near stock rom for this phone ? what kernel can go with it ?
optimusv45 said:
whats a very stable and optimized near stock rom for this phone ? what kernel can go with it ?
Click to expand...
Click to collapse
MysteryEmotion's eg8 ROM is the newest and may have the best chance of being actively maintained in the future. He also builds his own kernel with tweaks.
Ic, what version android is MysteryEmotion's eg8 ROM ? Has anyone tried houstonn's Stock 4.1.2 Jelly Bean LG-E970 At&t ? I don't need the latest version android or anything , mostly seeking for stability and everything work.
optimusv45 said:
Ic, what version android is MysteryEmotion's eg8 ROM ? Has anyone tried houstonn's Stock 4.1.2 Jelly Bean LG-E970 At&t ? I don't need the latest version android or anything , mostly seeking for stability and everything work.
Click to expand...
Click to collapse
Mystery's eg8 is based on 20j 4.1.2 stock with addons and enhancements. I think Houstonn's is a port from another OG that was released with jellybean before AT&T got the update.
Can you please clarify a bit? Do you mean stock LG or stock Google/Android.
Stock LG: Either go with MysteryEmotion's eg8 Or SnowJBLeaopard's SnowJB -almost forgot SlickRom, that is super debloated, but not really to my liking. (forgot who posted it)
Stock Google/Android: Either Shelnutt's Unofficial 10.1 Or houstonn's Vanilla Rootbox. The latter has a lot of "bells and whistles" while the former is basically stock. Also should mention TuxAttack's Beanstalk. Also a lot of bells and whistles though.
optimusv45 said:
whats a very stable and optimized near stock rom for this phone ? what kernel can go with it ?
Click to expand...
Click to collapse
Personally I would go with dvhexers CM 10.1.2, and his included kernel is quite good. This is stock android/CM though, with a bit of searching and patience you can run LG Home on top of this, with the original weather/clock and calendar.
i.e.
http://forum.xda-developers.com/showthread.php?t=2198225
So then you have the best of both. Too many options for you not to get out there any try a few. But @dvhexers CM10.1 I think was perfectly stable.
I am using the JellyBean ROM. I have been on it for about a month now and haven't had any issues that wasn't caused by me
Though, other than that I suggest mysteryemotionz
okay, I'll probably go with ME eg8 and his V6.1 kernel for 4.1.2. just being on the safe side , should i flash a JB radio for this rom ? if yes, do i flash in RECOVERY ? i have found a radio called CWM-ATTJB-Radio, is this the right one ? I am being carefully about this because my HTC flash radios in Hboot with PG86IMG files... as far as flashing kernel, do u guys recommend flashing with Flash Image GUI for this phone ? and is wiping Dalvik always needed for flashing kernels for this phone ? i thanked everyone that helped.
theregkid said:
I am using the JellyBean ROM. I have been on it for about a month now and haven't had any issues that wasn't caused by me
Though, other than that I suggest mysteryemotionz
Click to expand...
Click to collapse
Hi theregkid, a month of stability is very good. can you tell me which JellyBean ROM you are referring to ? ME's eg8 ?
optimusv45 said:
Hi theregkid, a month of stability is very good. can you tell me which JellyBean ROM you are referring to ? ME's eg8 ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2359068
Sorry, for some reason I called the ROM 'Beanstalk' Jellybean.
It was ported from the infuse 4G. I have tried just about every ROM and this one is my favorite.
Maybe it is just me, but again I haven't had any real issue with it. I did have a kernel crash from MysteryEmotionz kernel though. I then flashed Smoochas and all is good.
The crash occurred whenever I tried to run a QR code app. (any QR code app)
optimusv45 said:
okay, I'll probably go with ME eg8 and his V6.1 kernel for 4.1.2. just being on the safe side , should i flash a JB radio for this rom ? if yes, do i flash in RECOVERY ? i have found a radio called CWM-ATTJB-Radio, is this the right one ? I am being carefully about this because my HTC flash radios in Hboot with PG86IMG files... as far as flashing kernel, do u guys recommend flashing with Flash Image GUI for this phone ? and is wiping Dalvik always needed for flashing kernels for this phone ? i thanked everyone that helped.
Click to expand...
Click to collapse
ME's eg8 is modified stock, it should come with his kernel already. Yes the radio's flash in CWM as zips, you can manually push with ADB/Fastboot commands, but why bother.
What are you referring to by "Flash image GUI" ? If you mean "clockwork mod recovery" or "TWRP" then yes. Once you download the freegee app from the market, it will give you the option for either, choose which ever you like more, personally I prefer CWM. Yes always wipe dalvik cache after you flash a kernel, so it can recreate the DEX files for that particular kernels methods of execution.
[r.]GimP said:
ME's eg8 is modified stock, it should come with his kernel already. Yes the radio's flash in CWM as zips, you can manually push with ADB/Fastboot commands, but why bother.
What are you referring to by "Flash image GUI" ? If you mean "clockwork mod recovery" or "TWRP" then yes. Once you download the freegee app from the market, it will give you the option for either, choose which ever you like more, personally I prefer CWM. Yes always wipe dalvik cache after you flash a kernel, so it can recreate the DEX files for that particular kernels methods of execution.
Click to expand...
Click to collapse
Flash image GUI is an image flashing app from the market. MiRaGe, known for his rom and kernel works for Optimus V and HTC Evo V 4G, recommends flashing his kernels with this app. I have been using it to flash kernels. So i was just wondering if this would work with kernels for this phone , i guess every phone is different.
optimusv45 said:
Flash image GUI is an image flashing app from the market. MiRaGe, known for his rom and kernel works for Optimus V and HTC Evo V 4G, recommends flashing his kernels with this app. I have been using it to flash kernels. So i was just wondering if this would work with kernels for this phone , i guess every phone is different.
Click to expand...
Click to collapse
I'm not familiar with those apps, and don't recall seeing them mentioned here at all. FWIW, I personally avoid any apps that flash things. They may make things convenient, but I've seen too many issues caused on too many devices by apps that flash stuff.
Just read the relevant threads to learn about what you are doing, and flash manually from recovery. That way, you're in control of what you're doing. Less chance of snafus caused by incompatibilities...
i am in complete stock . rg8 is 700 mb ?.... most roms i use for my HTC are around 150..
Thanks everyone for all the help. Now I'm running eg8 , everything seems fine execept the first time I took a picture had a very strange crash. The screen went blank and codes started rolling up the screen , it went on for about 3 minutes then phone restarted itself ...