Related
Just flashed imoseyon's kernel on my rooted thunderbolt and now I'm stuck in a bootloop...any advice? I've running stock rom.
It's the lean version of his kernel and thats the only thing I flashed. I cleared cache + davik cache before flashing.
I was able to do a restore, but I want to use this kernel
It sounds stupid, but try again. Clear cache and dalvik
I've tried 5 times Even tried uninstalling setcpu and unfreezing all the bloatapps that I had frozen. Still get stuck on boot
I've also tried re-downloading the kernal file in case it was corrupt...no luck still.
Which Imoseyon kernel are you running?
Could it be that your particular Tbolt won't handle the lower voltage? Also you might want to check the md5sum again.
Good luck.
brenick said:
Which Imoseyon kernel are you running?
Could it be that your particular Tbolt won't handle the lower voltage? Also you might want to check the md5sum again.
Good luck.
Click to expand...
Click to collapse
I said its the lean version, and he doesnt post md5sum so I have nothing to compare to. But thanks for using my thread to +1 your post count....
wifi is broke and my data is stuck on 1X only now after doing advanced restore-->reboot only.
Did you flash the GB Sense kernel instead of the Froyo kernel?
I used this 1... http://forum.xda-developers.com/showthread.php?t=1021404 It says Froyo... where can I find the stock kernel that you get after rooting? I need to get wifi/data working again now.
I mount the phone as disk drive on my computer, and I can only view the SD Card...ugh whats going on, so many issues after flashing this kernel
I did a factory reset now and I still cant connect to wifi/3g/4g...I think I need to flash the stock kernel to fix it. Can someone point me in the right direction please?
Flash another rom such as BAMF, whenever you flash a rom it flashes the kernel that is included in the rom as well.
I'm using his kernel just fine. Can you check your radio version?
Sent from my ADR6400L using XDA App
radio 1.16.00.0402, and Im on the stock ROM, dont want to use a special ROM...
Flash a rom or the stock rom that should get you on another kernel. Also, my TB couldn't handle some of the kernels. I was never able to get it at 1.92ghz. I can only use the normal version. Try one of the other versions. Best of luck!
Sent from my DROID PRO using Tapatalk
make sure the kernel is not oc'd to 1.92.................most phones can not handle that.
Hi,
I need some help. I am an XDA lurker and have learned a ton. I am mostly aware of the usual fixes for these things, but I can not return to any other ROM than a CM10. CM10 data and camera are not working great, even though I LOVE this ROM and LOVE these developers, I can't use it yet.
Firtst, my backups are gone, I know, I know. But they are gone. I tried flashing NoSympothy and invisibleK,s stock ROMs but I get frozen at the Galaxy SIII screen everytime.I have tried all the usual system wiping drills, cache, data, etc... Formatted everything. I have downloaded from multiple sources. It seems like it doesn't like ICS now?
I am rooted and UNLOCKED! Woohoo, thanks Adam!!!!!
Any suggestions?
Recoverys to CM10 work. New flashes to CM10 work. But no stock image or stock rom?
rude53 said:
Hi,
I need some help. I am an XDA lurker and have learned a ton. I am mostly aware of the usual fixes for these things, but I can not return to any other ROM than a CM10. CM10 data and camera are not working great, even though I LOVE this ROM and LOVE these developers, I can't use it yet.
Firtst, my backups are gone, I know, I know. But they are gone. I tried flashing NoSympothy and invisibleK,s stock ROMs but I get frozen at the Galaxy SIII screen everytime.I have tried all the usual system wiping drills, cache, data, etc... Formatted everything. I have downloaded from multiple sources. It seems like it doesn't like ICS now?
I am rooted and UNLOCKED! Woohoo, thanks Adam!!!!!
Any suggestions?
Recoverys to CM10 work. New flashes to CM10 work. But no stock image or stock rom?
Click to expand...
Click to collapse
You have to flash the stock kernel as well as the ROM. Try flashing the Synergy latest nightly build it includes a custom kernel as long as your bootloader is unlocked.
Thanks,
I had a feeling it was something with the kernel. I wasn't sure what was included though. I think I tried to get synergy from here on my phone and it just kept opening new windows instead of downloading. I will grab the just the kernel from somewhere and let you know. I'll update in an hour or so. Thanks for the next few steps to try. Much appreciated!
That was it THANKS!!!
adclem said:
You have to flash the stock kernel as well as the ROM. Try flashing the Synergy latest nightly build it includes a custom kernel as long as your bootloader is unlocked.
Click to expand...
Click to collapse
Stock ROMs include the stock kernel. They will work as a one flash wonder. Your issue more sounds recovery based. Which recovery from which app were you using? It more sounds lime maybe you're still on a kexec recovery which is why you couldn't flash stock but synergy latest worked (or something of the sort, maybe other way around)
Sent from my Galaxy S3 using Tapatalk 2
I know this isn't the first thread of this kind to be made but everything seems out of date, a month marks a lot of updates fixing old bugs and making new ones. Anyway, I'm looking for a custom ROM and possibly a separate kernel that is "stable" (as stable as a custom ROM could be) and battery friendly. I was going to do AOKP or paranoid android but I hear in later updates they got buggy from using newer radios and some people are getting the sleep of death. I'm also interested in the Siyah kernel for the lulzactiveq governor but I question its stability and compatibility with other ROMs. I'm a noob and this is going to be my first flashing of a ROM aside from the massively fail attempts on my old Droid Pro. I'm already rooted and unlocked and made a NANDroid with clockwork recovery but advice on flashing and software is cool. I hear with Odin the yellow triangle pops up when you download boot but with cwr it doesn't which is why I plan on using it. Also, exactly how does one clean flash? I know dirty is just clearing caches so which should I do?
Using the latest OTA with the G7 baseband, still ICS.
TL;DR Stable bettery-friendly ROM, advice on flashing, possibly a kernel for ROM for better battery life?
Thanks a lot, sorry again for making the millionth thread on this matter!
Big fan of CleanRom here. I've tried different JB-based roms but keep coming back. I'm on CR 2.5 now with the HD radio, but have been on 2.1 with CleanKernel previously, along with the stock and G7 radios.
A "clean" flash will have you wipe data/factory reset as well. You should do this when switching Rom bases. I dirty flashed from CR 2.1 up to 2.5 and haven't had issues though.
Edit: FWIW, I can routinely see over 24hrs on a charge under normal/low usage.
Edit 2: If you care about your apps' data, you might want to go ahead and run a backup with something like Titanium Backup before doing a clean flash.
I'm no expert but I will answer a few of your questions. I rooted a month ago and have flashed every rom I can find, every rom I used has its own quirks and nothing is absolutely perfect.
It wouldnt hurt to just flash a few roms and see what you like best. As long as you have your backup and you can boot into recovery I dont see how it could hurt right?
At this moment I am using LiquidSmooth-JellyBean v2.0 RC3. Its quick and really clean but I have to manually cycle WiFi to get it working after I leave a routers range (i'm sure theres a fix but I havent looked yet)
A Clean Flash- Wipe your dalvik cache from recovery>advanced and data wipe/factory reset . This is wiping all your phone settings/data. Backup before this point since theres no going back unless you have a backup.
A Dirty Flash- you are installing on top of an old ROM without clearing all of your cache- you can retain settings but will have a high possibility of problems.
GoodLuck!
Thanks, I'm looking at cleanROM now. Is it ICS or JB? Usually it's either mentioned or there's a [JB]/[Jelly Bean] thing in the title but it's got nothing.
Also, does anything not work like wifi-direct or NFC? I know sometimes it's a per-person thing and other times there's a bunch of stuff you have to do to get things working properly.
If it doesn't have wifi or NFC and is ICS based I may as well play with other ROMs then. I don't want my phone OOC for too long though b/c I'm looking for work and lack a house phone.
Touchwiz ICS is the most stable at this time! It does not matter if its Beans, Synergy, or Clean Rom...they all are based off of VRALG1 Touchwiz... anything different between those are just additional mods baked into a stock rom. AOSP still has RIL issues, meaning the data handoff between 4g/3g is bad. Alot of times when Im on the outskirts of a solid 4g area the device's data connection flakes out.
CleanRom is using VRALG7 base and that is ICS. From what I remember CleanRom was pretty stable.
Quick definition:
Anytime you do not format your system, your not doing a true clean install.
Factory reset/data, cache, dalvik is a considered a clean install only when running the same base version (4.0 or 4.1 for example).
When changing base versions you should be doing all that + formatting your system (cwm under mounts and storage) or your just flashing a jb rom on top of an ICS rom. Issues arise because of this. Most devs are calling for this too.
Sent from my VZW GS3 running Synergy/Trinity/Dark Horse Rises
Synergy R73 seems to be the best so far. No reboots. Fast stable. Had Clean Rom Prior to it which was also great. Tried Jellywiz but kept having issues.
So only ICS roms are stable? I kinda want jelly though, which ROM seems the most stable? I hear older versions of AOKP and Paranoid work better then the newer ones. Siyah + AOKP might be neat, alternatively Euroskanks CM Kang project with the same Siyah kernel. I've read some great things about lulzpowerq which is why I want that kernel so much, probably with SIO or NOOP for i/o since I hear they're wonderful for battery life. The main battery problem is from using the HD radio though, right? So just flash to G1 and it should be good?
MasterPoppy said:
So only ICS roms are stable? I kinda want jelly though, which ROM seems the most stable? I hear older versions of AOKP and Paranoid work better then the newer ones. Siyah + AOKP might be neat, alternatively Euroskanks CM Kang project with the same Siyah kernel. I've read some great things about lulzpowerq which is why I want that kernel so much, probably with SIO or NOOP for i/o since I hear they're wonderful for battery life. The main battery problem is from using the HD radio though, right? So just flash to G1 and it should be good?
Click to expand...
Click to collapse
Just experiment its the only way you'll find out what works best for you.
Sent from my Galaxy SIII
Alrighty, thanks for the help! When I watched the noob video I was a bit afraid people would be mean. You guys are really helpful and awesome though. :highfive:
Synergy .r73 and KT747 ...
Most of the issues you hear about are caused by overclocking (anything above 1728 MHz is just for bragging rights or quadrant scores), underclocking (anything under 384 MHz is asking for trouble) undervolting (don't get ridiculous here ... your CPU needs power), using a task killer and/or applying unnecessary tweaks (e.g., V6 Supercharger ... totally unnecessary).
My phone, wifi and GPS work flawlessly, and my 4g speeds are off the charts.
The theme support is pretty good, too.
Sent from my SCH-I535 using xda premium
Jb rom's will not come close to the stability of ics until the official release from samsung/vzw. Data issues being reported as well. I suggest reading for a day before doing anything. AND BACK UP YOUR IMEI BEFORE FLASHING ANYTHING!
Sent from my VZW GS3 running Synergy/Trinity/Dark Horse Rises
annoyingduck said:
Jb rom's will not come close to the stability of ics until the official release from samsung/vzw. Data issues being reported as well. I suggest reading for a day before doing anything. AND BACK UP YOUR IMEI BEFORE FLASHING ANYTHING!
Sent from my VZW GS3 running Synergy/Trinity/Dark Horse Rises
Click to expand...
Click to collapse
I've been reading, seems the main problem is the modem being used in some of the ROMs. Apparently they updated to HD and everything works fine after G7. I also heard about IMEI issues, how do I back-up? A lot of the instructions are confusing...
Go here:
http://forum.xda-developers.com/showthread.php?t=1852255
Read the entire first page min. Do the terminal method A, and the synergy method B if you plan on running a rom other than synergy. (if you flash synergy it does it for you.)
Sent from my VZW GS3 running Synergy/Trinity/Dark Horse Rises
pdinphx said:
Synergy .r73 and KT747 ...
Most of the issues you hear about are caused by overclocking (anything above 1728 MHz is just for bragging rights or quadrant scores), underclocking (anything under 384 MHz is asking for trouble) undervolting (don't get ridiculous here ... your CPU needs power), using a task killer and/or applying unnecessary tweaks (e.g., V6 Supercharger ... totally unnecessary).
My phone, wifi and GPS work flawlessly, and my 4g speeds are off the charts.
The theme support is pretty good, too.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I agree with this.
I've used Synergy r73 with Imo's kernel and KT747 kernel. I'm currently using Ziggy's kernel, which is the default on Synergy r73. So far so good and smooth!!
annoyingduck said:
Go here:
http://forum.xda-developers.com/showthread.php?t=1852255
Read the entire first page min. Do the terminal method A, and the synergy method B if you plan on running a rom other than synergy. (if you flash synergy it does it for you.)
Sent from my VZW GS3 running Synergy/Trinity/Dark Horse Rises
Click to expand...
Click to collapse
I tried reboot nvbackup but it just rebooted normally and didn't go to the bootloader thingy. Does that mean it didn't work? I had superuser access and everything, am I supposed to do the vol down + pwr + home thing you usually do to get into the bootloader or something?
MasterPoppy said:
I tried reboot nvbackup but it just rebooted normally and didn't go to the bootloader thingy. Does that mean it didn't work? I had superuser access and everything, am I supposed to do the vol down + pwr + home thing you usually do to get into the bootloader or something?
Click to expand...
Click to collapse
Did you see tiny blue text at the top left when it was rebooting?
yeah, a quick flash before it booted. is that it? and do I have to do the other backup thing with the program after it or should nvbackup do the trick?
MasterPoppy said:
yeah, a quick flash before it booted. is that it? and do I have to do the other backup thing with the program after it or should nvbackup do the trick?
Click to expand...
Click to collapse
Well according to that thread "You may see tiny blue text on the bootloader screen indicating that it is copying." So I would assume that's it.
To be honest, when researching this whole lost IMEI issue, I was so paranoid that I did EVERY type of backup that was discussed in these forums. I saved every backup file to my dropbox account, my phone, and my computer just in case. I'll admit, I'm a bit more care free when flashing now, but I have yet to experience a lost IMEI issue.
If you're paranoid like me then it never hurts to do the other backup methods.
Hello, all.
I have a T-Mobile Blaze 4G with rooted stock ROM (Gingerbread), flashed radio version T989UVMC6, manually debloated and dewizzed. I'm running Halo launcher and Busybox Free version 9.6.
Since almost the first day I've had this phone, it would occasionally force close the phone process, usually when hanging up the phone with the Bluetooth radio on and paired with an earpiece. It happened bone stock, rooted, after I changed the modem, whenever. It seemed to happen less often after I changed the modem. The process always starts back up, but the Bluetooth device connection and system sound controls are wonky (unusable) until the phone is rebooted.
The only thing that seems to stop it is running Zepplinrox's V6 Supercharger script. That, however, occasionally freezes the entire system when trying to open certain apps, requiring a reboot. I've run earch after search on this subject, and nobody else seems to have this problem. The only thing I haven't tried is wiping the whole thing and flashing a custom ICS or JB ROM. I tried Dark Knight ver. 8 and hated it pretty much instantly.
I have two questions. Number one; Will flashing a custom ROM fix this situation? I figure that this must be a problem with the crappy stock Samsung ROM. Number two; Which ROM is fully functional and stable? I'd really like to keep this phone dependable. I don't care about the latest and greatest funky cool features that are hit-or-miss at best. I just need dependable, fast and functional.
Since you have been having issues for a while, I would suggest starting fresh. With a few runs of black hole wipe from cwm. Add a run of the gremlin remover for extra cleanliness. Then a flash of the latest ICS rooted stock rom and kernel, for reliability.
Black hole wipe. http://forum.xda-developers.com/showthread.php?t=1721057
Gremlin remover, FSC http://forum.xda-developers.com/showthread.php?t=2218713
Uvmb1 ics ROM http://forum.xda-developers.com/showthread.php?t=2329081
Romman0 said:
Since you have been having issues for a while, I would suggest starting fresh. With a few runs of black hole wipe from cwm. Add a run of the gremlin remover for extra cleanliness. Then a flash of the latest ICS rooted stock rom and kernel, for reliability.
Black hole wipe. http://forum.xda-developers.com/showthread.php?t=1721057
Gremlin remover, FSC http://forum.xda-developers.com/showthread.php?t=2218713
Uvmb1 ics ROM http://forum.xda-developers.com/showthread.php?t=2329081
Click to expand...
Click to collapse
I'll definitely go for the rooted version! Does it matter what order in which the ROM and the kernel are flashed? Also, I take it from the name of the download link that I'll have to go through the process of de-bloating this thing again. S'okay, I actually enjoy that part, but I don't want to screw it up since I've not messed with anything newer than GB. Is there a good guide somewhere on the forum for apps that can be dumped safely? I know there was one for GB stock root.
Thanks for the response.
ionizd said:
I'll definitely go for the rooted version! Does it matter what order in which the ROM and the kernel are flashed? Also, I take it from the name of the download link that I'll have to go through the process of de-bloating this thing again. S'okay, I actually enjoy that part, but I don't want to screw it up since I've not messed with anything newer than GB. Is there a good guide somewhere on the forum for apps that can be dumped safely? I know there was one for GB stock root.
Thanks for the response.
Click to expand...
Click to collapse
Flash the ROM then the kernel, rewipe cache and davlik, then profit.
The most recent ICS debloating thread. http://forum.xda-developers.com/showthread.php?t=2183726&highlight=debloat
Romman0 said:
Flash the ROM then the kernel, rewipe cache and davlik, then profit.
The most recent ICS debloating thread. http://forum.xda-developers.com/showthread.php?t=2183726&highlight=debloat
Click to expand...
Click to collapse
A few more silly questions; Do I need GAPPS or is that just for CM? Aren't the CM 10 ICS nightlies fairly stable and relatively bug-free? I use CM7 on my Nook color and it's...okay... Just a few little annoying things pop up with that. To be honest, I like the idea of starting with a clean slate and adding stuff I like rather than pulling stuff out of the Samsung stock ROM, but the issues I've had with the Nook and CM7 have sort of scared me off. Your opinions?
ionizd said:
A few more silly questions; Do I need GAPPS or is that just for CM? Aren't the CM 10 ICS nightlies fairly stable and relatively bug-free? I use CM7 on my Nook color and it's...okay... Just a few little annoying things pop up with that. To be honest, I like the idea of starting with a clean slate and adding stuff I like rather than pulling stuff out of the Samsung stock ROM, but the issues I've had with the Nook and CM7 have sort of scared me off. Your opinions?
Click to expand...
Click to collapse
All the AOSP ROMs for the Blaze needs GAPPs. And yes. The latest CM10 nightly is stable. And you said CM10 ICS? CM9 is ICS and CM10 is Jellybean.
ionizd said:
A few more silly questions; Do I need GAPPS or is that just for CM? Aren't the CM 10 ICS nightlies fairly stable and relatively bug-free? I use CM7 on my Nook color and it's...okay... Just a few little annoying things pop up with that. To be honest, I like the idea of starting with a clean slate and adding stuff I like rather than pulling stuff out of the Samsung stock ROM, but the issues I've had with the Nook and CM7 have sort of scared me off. Your opinions?
Click to expand...
Click to collapse
The stock roms don't require gapps, but like Wolf said the cm10 jb variants do.
If your willing to use cm10 it is very stable. Just use the latest CM10 nightly and not the old stable version.
Here http://forum.xda-developers.com/showthread.php?t=1922935
The jb gapps 20121011 http://goo.im/gapps/gapps-jb-20121011-signed.zip
xWolf13 said:
All the AOSP ROMs for the Blaze needs GAPPs. And yes. The latest CM10 nightly is stable. And you said CM10 ICS? CM9 is ICS and CM10 is Jellybean.
Click to expand...
Click to collapse
Of course. I get a bit confused ever since people started talking about 10.1.
Okay, I went ahead and installed the stock rooted ROM with the stock kernel. Went through the debloating process (mostly, there are some apps that I'm not sure I can do without so they stay for now), and did some customizing. I'm seeing a bit more battery drain. Is this an issue with ICS or do I need to try another kernel or supercharge the phone? I also have this crazy issue with ROM Manager ver. 5.5.3.0. It tells me that there is an updated version of Clockworkmod Recovery, but it freezes when I try to flash from ROM Manager. Also, ROM Manager freezes when I try to reboot into Clockworkmod Recovery. Maybe I need to test a bit more before I mess with it any more.
**EDIT** Well, it looks as if my CWM recovery installation is corrupted. Can I reflash it without messing up my current ROM?
ionizd said:
Okay, I went ahead and installed the stock rooted ROM with the stock kernel. Went through the debloating process (mostly, there are some apps that I'm not sure I can do without so they stay for now), and did some customizing. I'm seeing a bit more battery drain. Is this an issue with ICS or do I need to try another kernel or supercharge the phone? I also have this crazy issue with ROM Manager ver. 5.5.3.0. It tells me that there is an updated version of Clockworkmod Recovery, but it freezes when I try to flash from ROM Manager. Also, ROM Manager freezes when I try to reboot into Clockworkmod Recovery. Maybe I need to test a bit more before I mess with it any more.
**EDIT** Well, it looks as if my CWM recovery installation is corrupted. Can I reflash it without messing up my current ROM?
Click to expand...
Click to collapse
Yes, with Odin, in the Dev forum
BTW, stay away from ROM Manager with our device. I've softbricked so many times because of it, it's ridiculous
jparnell8839 said:
Yes, with Odin, in the Dev forum
BTW, stay away from ROM Manager with our device. I've softbricked so many times because of it, it's ridiculous
Click to expand...
Click to collapse
Used this method http://forum.xda-developers.com/showthread.php?t=2011585, it worked well. Still have the battery drain issue, though. : /
ionizd said:
Used this method http://forum.xda-developers.com/showthread.php?t=2011585, it worked well. Still have the battery drain issue, though. : /
Click to expand...
Click to collapse
Since you have it setup, except for battery life. I would make a backup, then try a mod one at a time and see if any help. Also check the battery stats to see if anything of is seen. ICS will use more juice than GB, generally.
I would suggest Nos/direct injection, supercharger, or cross breeder. I would use one and see, then restore and try another.
http://forum.xda-developers.com/forumdisplay.php?f=565
Some time later...
I've been using the stock rooted ICS ROM since my last post, debloated and dewizzed of course, with Holo Launcher and T989UVMC6 baseband version flashed. Just over a month has passed, and I have good news!
I FREAKING LOVE THIS PHONE!!!
All of the force close and freezing issues have vanished, the phone's battery lasts almost as long as it did on GB, it's WAY more user friendly, and the phone is as fast as it ever was.
The bad news is that my wife got a GS4 and I lust after it now. : /
Thanks to everyone for their help!
Hi guys,
I'm experiencing reboots when I push my phone hard. I typically have reboots when I'm using Chrome to view webpages in desktop mode or when using GPS (Google Maps, Waze). I've used two different roms and a few different kernels, but seem to be experiencing the same reboots across all platforms (and various rom/kernel combinations). Any help would be greatly appreciated!
Device: T-Mobile Samsung Note 5 64GB
Recovery: Philz Touch
ROMs used (COJ5):
Hyperdrive RLS2
Hyperdrive RLS3
fOrEvErLoCo's BrEaKdOwN R3.0.1
Kernels used:
Stock Hyperdrive RLS2 Kernel
Stock Hyperdrive RLS3 Kernel
Stock fOrEvErLoCo's BrEaKdOwN R3.0.1 Kernel
arter97 N920TW8 9.4 Kernel
arter97 N920TW8 X Kernel
SkyHigh N920T TW LL Kernel
Could this have anything to do with SuperSU?
still random rebooting.
and apparently we currently can't downgrade from COJ5? Double
Any help would be very, very appreciated. Thanks in advance!
Have you odin'd to stock + factory reset?
10-K said:
Have you odin'd to stock + factory reset?
Click to expand...
Click to collapse
As of right now I'm on jovy23's COJ5 Deodexed Stock Rooted Rom, installed after a fresh wipe of cache, dalvik, data, system, etc.
I seem to have found what was causing the reboots. I think it's giving Lastpass accessibility rights.
All throughout the initial installing of apps, the phone never randomly rebooted. Shortly after I got all my apps up and running, the reboots would begin to happen (sometimes twice in 15 minutes.)
Even on this fresh install of the deodexed stock rom, I had one random reboot. Since turning off Lastpass in Settings > Accessibility, I have experienced zero random reboots.
Did anyone else experience this? I'm wondering if it's specifically Lastpass that's giving the phone issues or Accessibility as a whole.
Will try to see if turning off Lastpass on the other kernels and ROMs helps next week and will post an update.
Thanks everyone!