Related
I am fairly new to Android, but am comfortable with command line operation on other Unix systems, etc. I read every thread I can find on this, but did not find my problem described exactly (there are some similar problems), so here it is:
My phone is a GSM Galaxy Nexus, about a month old. I rooted and unlocked it right away using post 1 from this guide: [VZW/SPRINT/GSM][Guide] Ultimate Galaxy Nexus Guide (Unlock/Root/Flash Roms/FAQ) - thanks Jubakuba!
I did NOT use any of the toolkits or automated methods.
A couple of days ago, I decided to try loading another ROM. I read through post 2 of the above guide. I followed the instructions in that thread and flashed a Trinity ROM. The flash seemed to go fine, and completed normally, but when I rebooted the phone, it was stuck in the Google Lock screen bootloop. I was able to restore a nandroid to get it back to where it was before, and the phone operates normally, no resets, reboots, nada. I inquired in Jubakubas thread as well as in the Trinity ROM thread in the developers section, and got some suggestions, which I tried. None of them worked. I also tried flashing a few other ROMS, a CM9 ROM and the RASCREAM ROM, and they all do the same thing. I have tried flashing these without wiping data or cache or dalvik cache, wiping some of them and wiping all of them, and the results are always the same - boot loop, which I can restore using CWM recovery and my nandroid.
One of the posters in the developers forum suggested taking the phone back to unrooted stock condition, so I did that, using this thread: [HOW-TO] [GSM & CDMA] Convert to latest yakju/takju/mysid build / Return to stock - another excellent guide, which worked exactly as described.
After that, my phone was back to as new, and I had to go through the whole start-up and restore applications, etc. I made a new nandroid so that recovery would be relatively painless, etc. Not too tough. I then Rooted the phone (it was always unlocked) and tried flashing a ROM again, with exactly the same results. Again, I was able to restore my nandroid and get back to operational.
I guess my question at this point is what on earth could be causing this? Some of the threads on boot loops where peoples phones start to boot loop spontaneously suggest a hardware problem, but the fact that I have NEVER had a boot loop in a month of use while running 4.0.4 stock rooted and unlocked seems to point more toward software as the cause. I will say one thing - I am learning how to use CWM and the bootloader commands! But, I would really like to be able to use some custom ROMS, not that there is anything really wrong with stock - this is a great phone. But, please HELP!
Reflash bootloader and radio through fastboot and please describe exactly (!) how you are going about flashing a custom Rom after
Sent from my Galaxy Nexus using Tapatalk 2
d0msen said:
Reflash bootloader and radio through fastboot and please describe exactly (!) how you are going about flashing a custom Rom after
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Okay, I booted into fastboot mode, then flashed the bootloader (bootloader-maguro-primela03.img) and radio (radio-maguro-i9250xxla02.img). I rebooted the bootloader, then went into recovery mode. From recovery mode, I selected "Install zip from sd card", "Choose zip from sd card", then selected the zip file in the /Download folder "TNP1536-384-Alpha86b-4.7-lto.zip". It went through its' install and said "System successfully corrupted" at the end and "Install from sdcard complete." I went back to reboot system rom and rebooted. Now, it is not looping anymore, but just sitting at the Google lock screen for about 2 minutes now. I will wait a few more minutes to see if it boots the rest of the way or starts looping, etc.
Okay, it has been 5-6 minutes with no additional changes, so I am pulling the battery. Powering it on now results in the same boot loop as before, so I will need to boot into bootloader mode and restore my nandroid.
are you wiping data when you flash the rom?
if not, you need to do that first inside of cwm
I would let it sit longer before pulling the battery
Sent from my Galaxy Nexus using xda premium
Anytime you flash a different ROM, you need to wipe - not optional. If you don't, you will have problems.
CYoung234 said:
"System successfully corrupted"
Click to expand...
Click to collapse
The
BOOM!
System successfully corrupted
Please freak out now
is a joke. By your account the kernel flashed successfully. Try flashing another kernel, perhaps not an Alpha version, although I've run that particular Alpha successfully. Do you have an app that sets kernel settings on boot by chance?
Hmmm thats a Kernel i think try another kernel.. Franco is a option ... maybe ur phone can't handle the undervolt of Trinity? I don't know worth a try download franco and post ur results here
Good luck
Is the Rom in the nandroid you're always restoring to something else than 4.0.3 or. 4 based? That would cause trinity to boot loop as it doesn't work on anything lower.
Aside try wiping everything (factory reset + format system under mounts and storage), then flashing something that is considered fairly stable like an aokp milestone build and see if you can boot it without flashing any custom kernel before. Report back
Sent from my Galaxy Nexus using Tapatalk 2
d0msen said:
Is the Rom in the nandroid you're always restoring to something else than 4.0.3 or. 4 based? That would cause trinity to boot loop as it doesn't work on anything lower.
Aside try wiping everything (factory reset + format system under mounts and storage), then flashing something that is considered fairly stable like an aokp milestone build and see if you can boot it without flashing any custom kernel before. Report back
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
The nandroid I am restoring to is stock 4.0.4. I will wipe everything, then try flashing a known stable aokp build, then report back.
efrant said:
Anytime you flash a different ROM, you need to wipe - not optional. If you don't, you will have problems.
Click to expand...
Click to collapse
I have tried this both ways. Wiping prior to flashing does not seem to be as universally accepted as you indicate. For example, in the Trinity ROM dev forum, a number of the more senior posters have the opinion that you should never wipe prior to flashing, that is is an un-necessary step. I do not personally know one way or the other, so I will make sure I wipe prior to flashing from now on.
CYoung234 said:
I have tried this both ways. Wiping prior to flashing does not seem to be as universally accepted as you indicate. For example, in the Trinity ROM dev forum, a number of the more senior posters have the opinion that you should never wipe prior to flashing, that is is an un-necessary step. I do not personally know one way or the other, so I will make sure I wipe prior to flashing from now on.
Click to expand...
Click to collapse
Perhaps they meant if flashing an update of the same ROM (?), just guessing. Even then it can be a good idea sometimes; new Android version (i.e. 4.0.3 > 4.0.4), significant framework changes, etc... but I err on the "safe" side.
Updating to the next nightly of CM9 I wipe absolutely nothing.
CYoung234 said:
I have tried this both ways. Wiping prior to flashing does not seem to be as universally accepted as you indicate. For example, in the Trinity ROM dev forum, a number of the more senior posters have the opinion that you should never wipe prior to flashing, that is is an un-necessary step. I do not personally know one way or the other, so I will make sure I wipe prior to flashing from now on.
Click to expand...
Click to collapse
What Trinity ROM? Unless I'm mistaken, there is no such thing as a Trinity ROM. Trinity kernel, yes, but ROM, no.
Sent from my Galaxy Nexus using Tapatalk 2
CMNein said:
Perhaps they meant if flashing an update of the same ROM (?), just guessing. Even then it can be a good idea sometimes; new Android version (i.e. 4.0.3 > 4.0.4), significant framework changes, etc... but I err on the "safe" side.
Updating to the next nightly of CM9 I wipe absolutely nothing.
Click to expand...
Click to collapse
Yes, pretty much this. If you are updating CM9 to the next build, no need to wipe. If you are going from CM9 to AOKP, then you need to wipe.
Updating: no need to wipe.
New ROM: wipe.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
What Trinity ROM? Unless I'm mistaken, there is no such thing as a Trinity ROM. Trinity kernel, yes, but ROM, no.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Just had a thought. Trinity is the unofficial support thread for Rascream (by Rascarlo), and Morfic did make a build of Rascream with the Linaro 4.7 tool chain.
OP, which Galaxy Nexus do you have?
efrant said:
What Trinity ROM? Unless I'm mistaken, there is no such thing as a Trinity ROM. Trinity kernel, yes, but ROM, no.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
You are correct, it is a kernel, not a ROM. I have tried 3 different Trinity kernels and one Franco kernel, all with the same results. The specific kernel I flashed for post #3 was TNP-1536-384-ALPHA86b-4.7-LTO.zip. The other two I tried were both stable releases. Morfic asked me to try the alpha kernel.
CMNein said:
Just had a thought. Trinity is the unofficial support thread for Rascream (by Rascarlo), and Morfic did make a build of Rascream with the Linaro 4.7 tool chain.
OP, which Galaxy Nexus do you have?
Click to expand...
Click to collapse
Google Galaxy Nexus i9250.
CYoung234 said:
Google Galaxy Nexus i9250.
Click to expand...
Click to collapse
Okay, was asking in the event that you were also flashing Rascream, or Morfic's build of it.
Re: wiping, since we now know that we're just talking kernel here, wiping dalvik + wiping cache is indeed approaching useless, so they weren't leading you astray. I can't think of what would be causing you to boot loop however.
d0msen said:
Is the Rom in the nandroid you're always restoring to something else than 4.0.3 or. 4 based? That would cause trinity to boot loop as it doesn't work on anything lower.
Aside try wiping everything (factory reset + format system under mounts and storage), then flashing something that is considered fairly stable like an aokp milestone build and see if you can boot it without flashing any custom kernel before. Report back
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
SUCCESS! I followed your advice (mostly - I did not factory reset + format system) and d/led AOKP Milestone 5 + GAPPS, flashed bootloader and radio from the bootloader, wiped data / reset, wiped dalvik cache, and booted into recovery and installed both zip files. It booted fine, and I am grabbing my apps and configuring now. I will let you know how it performs and use it for a few days. I will likely head in the Rascream / Trinity direction after using this one for a bit. But thank you to all who have posted.
CYoung234 said:
SUCCESS! I followed your advice (mostly - I did not factory reset + format system) and d/led AOKP Milestone 5 + GAPPS, flashed bootloader and radio from the bootloader, wiped data / reset, wiped dalvik cache, and booted into recovery and installed both zip files. It booted fine, and I am grabbing my apps and configuring now. I will let you know how it performs and use it for a few days. I will likely head in the Rascream / Trinity direction after using this one for a bit. But thank you to all who have posted.
Click to expand...
Click to collapse
This got me thinking: is trinity even compatible with a stock ROM (regardless of it being 4.0.4)? Maybe that is why you were having issues.
So I wanted to flash the FNV AoSP ROM on my Galaxy Nexus GSM. First off al I flashed the 4.2 takyu version and rooted it with SuperSU. After that I flashed the recovery with Clockwork 6.0.1.5 after that I did the following things:
- Wipe data/factory reset
- Mounts and storage > Format /system
- Wipe cache
- Wipe dalvik
- Flashed ROM fnv_20121119_003_maguro.zip
- Flash 4.2 gapps
Am I doing something wrong?
When you say, won't work what do you mean?
Does the recovery not flash the file? If so, what error does it say?
Does it not boot after what seems to be a successful flash in recovery? Do you see the bootanimation?
cupfulloflol said:
When you say, won't work what do you mean?
Does the recovery not flash the file? If so, what error does it say?
Does it not boot after what seems to be a successful flash in recovery? Do you see the bootanimation?
Click to expand...
Click to collapse
It flashs the files and all but it gets into a bootloop. I see the costum bootanimation of the ROM, but it keeps playing and it won't start up. After some time the screen goes black, but it's not off, because if I hold down power it won't turn on so I have to pull battery.
CheesieOnion said:
It flashs the files and all but it gets into a bootloop. I see the costum bootanimation of the ROM, but it keeps playing and it won't start up. After some time the screen goes black, but it's not off, because if I hold down power it won't turn on so I have to pull battery.
Click to expand...
Click to collapse
Your ROM name seems to show that it is a recent build. A quick search around, the last official FNV ROM I see was uploaded in September. The Gerrit, Github, Twitter, and threads here and on another site seem to have been untouched for quite some time.
Of course I am a little out of the loop, so perhaps I am missing something. As devs often post things in IRC, or in other non-official channels. Did you get this ROM from a trusted spot?
That said, it could be a ROM issue perhaps.
CheesieOnion said:
So I wanted to flash the FNV AoSP ROM on my Galaxy Nexus GSM. First off al I flashed the 4.2 takyu version and rooted it with SuperSU. After that I flashed the recovery with Clockwork 6.0.1.5 after that I did the following things:
- Wipe data/factory reset
- Mounts and storage > Format /system
- Wipe cache
- Wipe dalvik
- Flashed ROM fnv_20121119_003_maguro.zip
- Flash 4.2 gapps
Am I doing something wrong?
Click to expand...
Click to collapse
it probably doesnt need the gapps. try reflashing, but without the gapps. don't wipe anything.
cupfulloflol said:
Your ROM name seems to show that it is a recent build. A quick search around, the last official FNV ROM I see was uploaded in September. The Gerrit, Github, Twitter, and threads here and on another site seem to have been untouched for quite some time.
Of course I am a little out of the loop, so perhaps I am missing something. As devs often post things in IRC, or in other non-official channels. Did you get this ROM from a trusted spot?
That said, it could be a ROM issue perhaps.
Click to expand...
Click to collapse
I got the rom from the topic here on XDA. It is the build from 19 november.
simms22 said:
it probably doesnt need the gapps. try reflashing, but without the gapps. don't wipe anything.
Click to expand...
Click to collapse
In the instuctions in the ROM-topic it says it needs them and I also need them to use.
CheesieOnion said:
I got the rom from the topic here on XDA. It is the build from 19 november.
In the instuctions in the ROM-topic it says it needs them and I also need them to use.
Click to expand...
Click to collapse
install the gapps from the play store. you can flash without them, besides the ones that you cant get from the play store are included. you can try it, or just stay in your bootloop, its your call.
CheesieOnion said:
I got the rom from the topic here on XDA. It is the build from 19 november.
Click to expand...
Click to collapse
Ah, my bad I didn't realize it was picked up by someone else, I see that now (which I thank you for the heads up that it is back in production). I was just making sure you weren't flashing something that wasn't ready for public use, and that it was a real ROM.
I was on paranoid android, i flashed ak kernel and my Phone started to have sod and reboot without passing for the Google logo.
I dirty flashed pa again to come back to stock kernel, same reboot.
So i made a full wipe and flashed slim bean + ak kernel but the problem remains. Another full wipe and flashed only slim bean w/o a kernel. And again reboot.
I don't know What to do. The only thing is to flash stock image and root again but it's a bit annoying.
Someone has a better idea?
Il_Tene said:
I was on paranoid android, i flashed ak kernel and my Phone started to have sod and reboot without passing for the Google logo.
I dirty flashed pa again to come back to stock kernel, same reboot.
So i made a full wipe and flashed slim bean + ak kernel but the problem remains. Another full wipe and flashed only slim bean w/o a kernel. And again reboot.
I don't know What to do. The only thing is to flash stock image and root again but it's a bit annoying.
Someone has a better idea?
Click to expand...
Click to collapse
Try using AK's kernel revert (back to stock kernel.)
It works for some people and for others, it doesn't though. I also had reboot problems with AK so I don't use it anymore, and also it sucks that I had to revert to stock when it happens. Hope it works for you, goodluck man.
4.2.2 - http://d-h.st/R7y
4.2.1 - http://d-h.st/2w6
From AK's thread
I didn't use that "script" because i thaught it is needed only if you want to go back to stock kernel without reflashing the rom. If I reflash the rom the kernel will be overwritten, isn't it?
However now i'm no more with ak kernel so i don't think ak's kernel revert could do something.
Il_Tene said:
I didn't use that "script" because i thaught it is needed only if you want to go back to stock kernel without reflashing the rom. If I reflash the rom the kernel will be overwritten, isn't it?
However now i'm no more with ak kernel so i don't think ak's kernel revert could do something.
Click to expand...
Click to collapse
Yes. The kernel id's overwritten whenever you flash a rom.
Sent from my Nexus 7 using Tapatalk HD
I just got my replacement HTC One V CDMA unlocked and rooted. I want to overclock and understand I need a custom ROM to do so. My first HTC One V I bricked trying to flash rhythmicrom. I unlocked, rooted, backed up using TWM. Each time I tried to flash the new ROM it would get stuck on the HTC screen with the red writing talking about developmental purposes, etc. Each time it would hang on that screen I would simply do a recovery to the back up file and everything would go back to normal. The last time I tried to flash it hung up, and when I tried to go back it would not go back. I am not sure why Rhythmicrom would not work. Is there another one I should try? Does it matter if my HTC one V is a newer version, etc? I just need a basic ROM with the ability to overclock. MMS is a necessity and the camera would be nice. Thanks for any help you can give me.
Did you make sure to flash the appropriate kernel via fastboot aftter flashing the ROM, because if not that could be the cause of your phone failing to boot. As for ROM's, well I guess that depends on whether you have a PrimoU or a PrimoC, I personally use SHPONGLE for the PrimoU, but I can't comment on the PrimoC as I do not own one
zzjoshzz said:
Did you make sure to flash the appropriate kernel via fastboot aftter flashing the ROM, because if not that could be the cause of your phone failing to boot. As for ROM's, well I guess that depends on whether you have a PrimoU or a PrimoC, I personally use SHPONGLE for the PrimoU, but I can't comment on the PrimoC as I do not own one
Click to expand...
Click to collapse
Thank you for the reply. Yes I used the kernel (boot.img) that was included with the rythmicrom rom. I have a PrimoC. I was reading and see that my problem might be caused due to maybe having a newer version of the phone and the hboot or radio might be different?
tackj said:
Thank you for the reply. Yes I used the kernel (boot.img) that was included with the rythmicrom rom. I have a PrimoC. I was reading and see that my problem might be caused due to maybe having a newer version of the phone and the hboot or radio might be different?
Click to expand...
Click to collapse
Hey, so some kernels support the newer radio and some do not. If you are on the newer radio: Baseband version 1.00.00.0928 (check in about phone in settings) then you have to use a kernel that supports the OTA, such as for sense use the FOTA kernel posted under the cdma development thread, for android 4.1 use the kernel I made that can be found in the slim bean rom thread by curtis, and for 4.2 rythmic rom's kernel should work just fine. If not, try the codefirex kernel from simon's rom (original dev. thread) but you'll lose functionality of the camera as it is an ion kernel.
I hope this helps, quote me in the reply if you have more questions, otherwise I may forget to check back here.
why u no flash kernel omg! just read the trouble shooting section
lilrob1213 said:
Hey, so some kernels support the newer radio and some do not. If you are on the newer radio: Baseband version 1.00.00.0928 (check in about phone in settings) then you have to use a kernel that supports the OTA, such as for sense use the FOTA kernel posted under the cdma development thread, for android 4.1 use the kernel I made that can be found in the slim bean rom thread by curtis, and for 4.2 rythmic rom's kernel should work just fine. If not, try the codefirex kernel from simon's rom (original dev. thread) but you'll lose functionality of the camera as it is an ion kernel.
I hope this helps, quote me in the reply if you have more questions, otherwise I may forget to check back here.
Click to expand...
Click to collapse
Thank you very much for you help. I checked my radio and it is 1.00.00.0928. Is this the reason why the rythmicrom kernel would not work? So you recommend using the FOTA kernel with which ROM? Sorry for the dumb questions. I tried my best to read everything I could before asking for help. I just don't want to brick my replacement phone. I am not sue they will be as understanding as they were the first time.
tackj said:
Thank you very much for you help. I checked my radio and it is 1.00.00.0928. Is this the reason why the rythmicrom kernel would not work? So you recommend using the FOTA kernel with which ROM? Sorry for the dumb questions. I tried my best to read everything I could before asking for help. I just don't want to brick my replacement phone. I am not sue they will be as understanding as they were the first time.
Click to expand...
Click to collapse
well it shouldn't have been the reason because if you type "fastboot flash boot boot.img" in command line for the kernel you want to flash then it should flash correctly and rythmic rom's kernel has supported new radio since the beginning pretty much. Unless you have a really old version or something. The FOTA kernel is for sense roms or cm9 (which is based on android 4.0 ics). I really like and very much recommend MyOneV rom that curiousnoob has ported under the cdma dev. thread. It's fast, smooth, and has the least amount of lag compared to any other sense rom that I've tried. It's my daily and go-to rom!
You shouldn't brick your phone as long as you fastboot flash the correct kernel (for primoc/cdma), even if you end up in a bootloop you can hold power button and get back to bootloader to flash a new rom or restore a backup
lilrob1213 said:
well it shouldn't have been the reason because if you type "fastboot flash boot boot.img" in command line for the kernel you want to flash then it should flash correctly and rythmic rom's kernel has supported new radio since the beginning pretty much. Unless you have a really old version or something. The FOTA kernel is for sense roms or cm9 (which is based on android 4.0 ics). I really like and very much recommend MyOneV rom that curiousnoob has ported under the cdma dev. thread. It's fast, smooth, and has the least amount of lag compared to any other sense rom that I've tried. It's my daily and go-to rom!
You shouldn't brick your phone as long as you fastboot flash the correct kernel (for primoc/cdma), even if you end up in a bootloop you can hold power button and get back to bootloader to flash a new rom or restore a backup
Click to expand...
Click to collapse
Thanks for the information. Is it necessary to wipe the sd card before installing the new ROM? This is how I bricked my last one. I read somewhere that I needed to do a full wipe including the sd card. The sd card is where my recovery was and when I wiped it I didn't have anything to recover to. I tried RUU and that did not work.
So I think I might do this kernel [KERNEL][VM/PRIMOC][ICS:Sense] FOTA-Compatible Sick Kernel
With this ROM: myOneV 9.5+CDMA
Does this look ok?
tackj said:
Thanks for the information. Is it necessary to wipe the sd card before installing the new ROM? This is how I bricked my last one. I read somewhere that I needed to do a full wipe including the sd card. The sd card is where my recovery was and when I wiped it I didn't have anything to recover to. I tried RUU and that did not work.
So I think I might do this kernel [KERNEL][VM/PRIMOC][ICS:Sense] FOTA-Compatible Sick Kernel
With this ROM: myOneV 9.5+CDMA
Does this look ok?
Click to expand...
Click to collapse
It isn't necessary to wipe sd card, although if you get any weird bugs that no one else has reported (read threads) then yeah, I'd wipe sd card. In fact, I do actually wipe everything (except sd-ext) from twrp 2.6.1. But before I wipe I mount usb to my computer and copy over the twrp folder with my backup and any pictures I wanna save. Then, wipe everything including sd card (although not necessary I like to do it) and then mount usb again and copy the files I need (rom.zip and twrp folder). But to do a full wipe technically it's just wiping data, cache, dalvik cache, and system.
RUU will not work if you are on the newer hboot version (forgot the number but it's around here which is new vs old).
that combination works for me (I'm on new hboot and radio) so should work fine! btw that's the rom and kernel I mentioned earlier idk if you caught that or not
lilrob1213 said:
It isn't necessary to wipe sd card, although if you get any weird bugs that no one else has reported (read threads) then yeah, I'd wipe sd card. In fact, I do actually wipe everything (except sd-ext) from twrp 2.6.1. But before I wipe I mount usb to my computer and copy over the twrp folder with my backup and any pictures I wanna save. Then, wipe everything including sd card (although not necessary I like to do it) and then mount usb again and copy the files I need (rom.zip and twrp folder). But to do a full wipe technically it's just wiping data, cache, dalvik cache, and system.
RUU will not work if you are on the newer hboot version (forgot the number but it's around here which is new vs old).
that combination works for me (I'm on new hboot and radio) so should work fine! btw that's the rom and kernel I mentioned earlier idk if you caught that or not
Click to expand...
Click to collapse
Cool thank you. Yes I did catch that I just wanted to confirm that was the one you are talking about. I went to download that rom and it said it was not available any longer.
tackj said:
Cool thank you. Yes I did catch that I just wanted to confirm that was the one you are talking about. I went to download that rom and it said it was not available any longer.
Click to expand...
Click to collapse
oh right... curiousnoob is revamping it to make it better, you can either be patient or I can upload you an older version give me a second
here: https://docs.google.com/file/d/0By_o-NyPojUXNTdna3p5bGdSNVU/edit?usp=sharing it's from 09/02/2013 but it's the best I think so far... next update should be awesome-er! haha
lilrob1213 said:
oh right... curiousnoob is revamping it to make it better, you can either be patient or I can upload you an older version give me a second
here: https://docs.google.com/file/d/0By_o-NyPojUXNTdna3p5bGdSNVU/edit?usp=sharing it's from 09/02/2013 but it's the best I think so far... next update should be awesome-er! haha
Click to expand...
Click to collapse
Thank you for all of your help! Will this ROM work with the stock kernel? Just wondering. I would like to overclock so i will be flashing the sick kernel, but I was just curious. Thank you again.
tackj said:
Thank you for all of your help! Will this ROM work with the stock kernel? Just wondering. I would like to overclock so i will be flashing the sick kernel, but I was just curious. Thank you again.
Click to expand...
Click to collapse
kinda... but with stock kernel wifi didn't work... however fota kernel works so great with overclock that there's no need for stock kernel and it's not a problem, I'm happy to help
lilrob1213 said:
kinda... but with stock kernel wifi didn't work... however fota kernel works so great with overclock that there's no need for stock kernel and it's not a problem, I'm happy to help
Click to expand...
Click to collapse
Thank you for the link! I downloaded and got the ROM working now with the stock kernel. Now I am going to try and flash the sick kernel. Just to confirm, this is the one I need:
http://forum.xda-developers.com/showthread.php?t=2261819
I am going to put it in my fastboot folder, rename it boot.img and then flash it using cmd.
Does this sound right?
Also, just an FYI...I received a PM from Curiousn00b stating that the newest version is now available.
tackj said:
Thank you for the link! I downloaded and got the ROM working now with the stock kernel. Now I am going to try and flash the sick kernel. Just to confirm, this is the one I need:
http://forum.xda-developers.com/showthread.php?t=2261819
I am going to put it in my fastboot folder, rename it boot.img and then flash it using cmd.
Does this sound right?
Also, just an FYI...I received a PM from Curiousn00b stating that the newest version is now available.
Click to expand...
Click to collapse
Yup sounds flawless to me! Enjoy it! and thanks for the headsup I will probably download that and test myself
lilrob1213 said:
Yup sounds flawless to me! Enjoy it! and thanks for the headsup I will probably download that and test myself
Click to expand...
Click to collapse
Hey, I got the kernel to work! Now my wifi is operational. Now that the new version is available, do I dare ask how to go about updating? Is it just the same process? Thanks!
tackj said:
Hey, I got the kernel to work! Now my wifi is operational. Now that the new version is available, do I dare ask how to go about updating? Is it just the same process? Thanks!
Click to expand...
Click to collapse
You flashed the fota sick kernel? Well, you can update by just wiping dalvik and cache and flashing the new rom, but it's a full wipe (same process as before) is always recommended over the previous "update"
lilrob1213 said:
You flashed the fota sick kernel? Well, you can update by just wiping dalvik and cache and flashing the new rom, but it's a full wipe (same process as before) is always recommended over the previous "update"
Click to expand...
Click to collapse
Yes, I was able to flash the FOTA sick kernel. I have it set at 1.709 GHz max and 245 mhz min. with the I/O scheduler on noop. I put the governor on "performance" and did a benchmark test with antutu. My score was 7069 which didn't look all that great compared to the others. Does this sound about right? I was also only getting 6.2 fps on the 3D testing.
tackj said:
Yes, I was able to flash the FOTA sick kernel. I have it set at 1.709 GHz max and 245 mhz min. with the I/O scheduler on noop. I put the governor on "performance" and did a benchmark test with antutu. My score was 7069 which didn't look all that great compared to the others. Does this sound about right? I was also only getting 6.2 fps on the 3D testing.
Click to expand...
Click to collapse
hmmm... I have no idea... I've never really messed with benchmarks before, don't think they matter much, I'm happy just having a lag-free phone btw for typical use, I'm sure you know, performance gov. will kill your battery fairly quickly, so I usually use [email protected]$$v2 gov. or lionheart, but usually the first
lilrob1213 said:
hmmm... I have no idea... I've never really messed with benchmarks before, don't think they matter much, I'm happy just having a lag-free phone btw for typical use, I'm sure you know, performance gov. will kill your battery fairly quickly, so I usually use [email protected]$$v2 gov. or lionheart, but usually the first
Click to expand...
Click to collapse
You are right, the phone is more snappy for sure. What GHz do you use for everyday? I was using [email protected]$$v2 gov but put it on performance just during the test. I also have buzzlauncher as my launcher so I am not sure if that is taking away from the performance, but it looks nice. I am just happy that it is working, so again thanks for your help.
I have a T989, not a T989D, running TWRP 2.7.1.0 and UVMC6 radio, coming from a JB 4.1.2 Slimrom.
Also I have taken out the board and inspected the power button, and everything seems okay there. I don't think it's being caused by a faulty button or some other hardware problem because I can flash my old Slimrom, and that boots up just fine.
I wanted to give Paranoid Android a whirl with the latest Wild kernel, and though I've tried 8 different PA builds, a PACman, a Slimkat, and an Alpine rom, ALL KitKat roms so far are bootlooping. [EDIT: Even PA 3.99 JB 4.3 is doing it. So it's more than just KitKat even.]
I'm doing the following:
Wipe system, data, cache, dalvik, and perhaps android secure and preload as well
Flash ROM & Gapps
Wipe cache & dalvik
Reboot
I reach the splash, and maybe it even finishes booting. But invariably, it takes about 60-90s from initialization before the screen dims, everything freezes for 2-5s, and it reboots.
I'm out of ideas.
Why won't my phone work with KitKat?
Thanks in advance
Have you ever used odin to flash the factory 4.1.2 UVMC6 rom? Some driver stuff was updated in that version and can only be installed with odin.
Edit: If your phone came with 4.1.2 jellybean, you already have the newest drivers.
meekrawb said:
Have you ever used odin to flash the factory 4.1.2 UVMC6 rom? Some driver stuff was updated in that version and can only be installed with odin.
Edit: If your phone came with 4.1.2 jellybean, you already have the newest drivers.
Click to expand...
Click to collapse
I read something to that effect. Haven't seen a .tar file for it, only .zip.
jaybird16 said:
I read something to that effect. Haven't seen a .tar file for it, only .zip.
Click to expand...
Click to collapse
If you sign up for an account on sammobile.com you can download from there. Just type "t989" in the search box.
meekrawb said:
If you sign up for an account on sammobile.com you can download from there. Just type "t989" in the search box.
Click to expand...
Click to collapse
Okay, I did that. Flashed the latest Paranoid Android 4.45. No dice. Same story.
jaybird16 said:
Okay, I did that. Flashed the latest Paranoid Android 4.5. No dice. Same story.
Click to expand...
Click to collapse
That was the only thing I could think of. Maybe someone else has some ideas.
I had the same problem. Turned out it had to do with the recovery. I redownloaded twrp, used flashify to install it. And that fixed the problem.
meekrawb said:
That was the only thing I could think of. Maybe someone else has some ideas.
Click to expand...
Click to collapse
Much appreciated. My phone shipped at the tail end of Gingerbread. So now I have whatever drivers from 4.1.2, and that's one more potential problem eliminated.
The stock rom ran just fine, btw, once I factory reset (the documentation was nil, but at 750mb, I knew it was more than just UVMC6 radio firmware...)
So 4.1.x seems to be okay, but not 4.3.x or 4.4.x. Next I'll have to try a flavor of 4.2.x and see how it feels about that.
Lokke9191 said:
I had the same problem. Turned out it had to do with the recovery. I redownloaded twrp, used flashify to install it. And that fixed the problem.
Click to expand...
Click to collapse
Interesting.
After I flashed the stock UVMC6 (and associated rom and lameass stock recovery) earlier today, I felt it was safest to use Odin to reflash TWRP while I had a functioning rom (even tho not rooted). So I downloaded the tar and that's the recovery I used to test PA 4.45. I will be doing more testing. I mean, it's not because there are leprechauns in my phone, right?
jaybird16 said:
Interesting.
After I flashed the stock UVMC6 (and associated rom and lameass stock recovery) earlier today, I felt it was safest to use Odin to reflash TWRP while I had a functioning rom (even tho not rooted). So I downloaded the tar and that's the recovery I used to test PA 4.5. I will be doing more testing. I mean, it's not because there are leprechauns in my phone, right?
Click to expand...
Click to collapse
Never. Ever. Rule out leprechauns!
Lokke9191 said:
Never. Ever. Rule out leprechauns!
Click to expand...
Click to collapse
LOL, good point.
w00t! TWRP 2.1.8 for the Hercules just dropped!
I was thinking maybe the MD5 wouldn't have checked out the first time you downloaded, but would have the second time. I don't usually bother unless I have a reason to think that's a problem. I can always look after the fact.
Downloaded 2.1.8 and MD5 checks out...now to flash it...
jaybird16 said:
LOL, good point.
w00t! TWRP 2.1.8 for the Hercules just dropped!
I was thinking maybe the MD5 wouldn't have checked out the first time you downloaded, but would have the second time. I don't usually bother unless I have a reason to think that's a problem. I can always look after the fact.
Downloaded 2.1.8 and MD5 checks out...now to flash it...
Click to expand...
Click to collapse
Nice. Lemme know how it works out. Oh. The new PA is awesome.
My bad. I saw the number "8" at the bottom of the page which had not been there earlier and assumed it was next after after "7". No, that's an ancient recovery from 2012.
TWRP 2.8.1 for the Hercules has NOT just dropped!
Okay, so, my first test with a newly downloaded, MD5 checked, and flashed TWRP 2.7.1 recovery, and an MD5 checked PA 4.45 has not produced any different result.
However, you've made me realize that I can't hope to troubleshoot this without being fastidious about MD5 from here on out, so, thx 4 that.
...same goes for a 2nd test with an MD5 checked PA 4.5 Alpha3...
...same goes for a 3rd test with an MD5 checked PA v3.69 (4.2)...
...But Slim-Star v4.12 (4.2) loads no problem...go figure...
Fix permissions?
I tried to install the PA 4.5 Beta, and same problem. It bootloops.
Could it have anything to do with permissions?
jaybird16 said:
Interesting.
After I flashed the stock UVMC6 (and associated rom and lameass stock recovery) earlier today, I felt it was safest to use Odin to reflash TWRP while I had a functioning rom (even tho not rooted). So I downloaded the tar and that's the recovery I used to test PA 4.45. I will be doing more testing. I mean, it's not because there are leprechauns in my phone, right?
Click to expand...
Click to collapse
when i had an issue like this i re-installed the factory original rom and started from the very beginning. if you've tried that and it doesn't work, well i'm pretty much unhelpful here. :crying:
Also note that WildKernel has a special version of v9 out for recent roms (roms released within the last two months).
Any other version of wildkernel will lead to bootloops in my experience.
If your rom is older than two months, then v8 or v9 should do fine
ayr0 said:
Also note that WildKernel has a special version of v9 out for recent roms (roms released within the last two months).
Any other version of wildkernel will lead to bootloops in my experience.
If your rom is older than two months, then v8 or v9 should do fine
Click to expand...
Click to collapse
There were problems reported of even the latest version of Wild! not working with Paranoid.
jrc2
Sent from my T-Mobile S2 using Tapatalk.
I'm having the same issues, but no one knows what's up. I've tried so many ROM's and only the older ones work.
http://forum.xda-developers.com/showpost.php?p=55050951&postcount=9
This is my post with the logs I got from the constant crash on cm11. I tried pa and had the same result.
Issue solved
After sharing some logs with Sultanxda, he pointed out this bootloop issue due to the CM kernel and helped me get it fixed.
My problem was that my phone would not boot on MOST JellyBean ROM's or ANY KitKat ROM. It would crash/kernel panic on or before the set up screen.
I do not know if the latest KitKat ROM's have the issue patched, but I asked if he could upload the patch for the kernel to source for other ROM's to use.
This thread should be solved I guess.