[Q] CM7 Clockwork Recovery - G2 and Desire Z Q&A, Help & Troubleshooting

I have been reading into it, and my only hesitation with going to CM7 while it's in Nightlies stage is that I am hoping there will be a recovery that does the EXT4, as well as the current stuff so that if I don't like the CM7 for stability issues or whatever, I can flash back to 6.1.1, revert my nand.
I have read that I can rename the new recovery the old file name, and trick it to installing that, once in CM7 can I just reflash the older version of recovery so that I can go back to 6.1.1 if necessary?

theratdude64 said:
I have been reading into it, and my only hesitation with going to CM7 while it's in Nightlies stage is that I am hoping there will be a recovery that does the EXT4, as well as the current stuff so that if I don't like the CM7 for stability issues or whatever, I can flash back to 6.1.1, revert my nand.
I have read that I can rename the new recovery the old file name, and trick it to installing that, once in CM7 can I just reflash the older version of recovery so that I can go back to 6.1.1 if necessary?
Click to expand...
Click to collapse
If you don't like CM7, download the v2 recovery from ROM manager, flash it, boot into recovery and restore your old backup.
As soon as the nightlies came out I flashed them just to play around, flashing back wasn't an issue at all.
Sent from my T-Mobile G2 using XDA App

Awesome, I shall do that. Thanks I will likely like it... but I always have issues with my GPS and different Kernels, and I don't wanna shoot myself in the foot if I don't have reliable GPS in CM7. My job drives all over the place and I require the GPS sometimes

theratdude64 said:
Awesome, I shall do that. Thanks I will likely like it... but I always have issues with my GPS and different Kernels, and I don't wanna shoot myself in the foot if I don't have reliable GPS in CM7. My job drives all over the place and I require the GPS sometimes
Click to expand...
Click to collapse
From what I've read, the GPS issues have been sorted (reboot a few times if they're funky); and the only kernel issue I know of was with the camcorder with pershoot but he fixed it.
Sent from my T-Mobile G2 using XDA App

Ahh very nice. Yeah I was also seeing that the camcorder was garbage but didn't see that was taken care of. I just may do it tonight

Related

[Q] FPS Fix for Stock 2.2?

I rooted my evo yesterday, so I am still completely new to how things work. (Though I have read the forums for a while)
I know I can flash a custom rom to fix the 28FPS limit I am getting, but I don't have time to completely wipe my phone and rebuild everything again.
It's kind of looking like I just flash a kernel? but I am not sure and I don't want to brick my phone.
Is there a way to just fix the performance limitations (i.e. FPS limit) and keep my stock 2.2 and all my settings/preferences?
Thank you.
I searched but didn't find anything that made sense.
Phone:
Evo w/ stock 2.2 (UnrEVOked3 root)
You should be able to just flash a custom kernel, but I don't know how those work on plain stock. Make sure you nand first.
Sent from my blah blah blah blah
I have rooted stock 2.2 with Kings kernel #9. Works flawlessly. It's hard for me to go back to regular once the FPS is unlock.
http://forum.xda-developers.com/showthread.php?t=754128
Just flash the zip file from recovery. Make sure you do a nand backup before you start flashing the kernel.
Thanks for the info.
I will give it a try later.
Can I flash any kernel? Or how does that work?
I was looking at snap 8.2. Is it compatible with stock & sense?
(http://forum.xda-developers.com/showthread.php?t=733099)
Also, once a kernel is flashed can you update it without problems or doing a full nandroid restore?
Thanks again,
Sent from my Evo using XDA App.
xNotta said:
Thanks for the info.
I will give it a try later.
Can I flash any kernel? Or how does that work?
I was looking at snap 8.2. Is it compatible with stock & sense?
(http://forum.xda-developers.com/showthread.php?t=733099)
Also, once a kernel is flashed can you update it without problems or doing a full nandroid restore?
Thanks again,
Sent from my Evo using XDA App.
Click to expand...
Click to collapse
No. Go for Netarchy's or Kingklick's kernels for 2.2 Sense roms. Snap is only for cm6/AOSP style roms.
daneurysm said:
No. Go for Netarchy's or Kingklick's kernels for 2.2 Sense roms. Snap is only for cm6/AOSP style roms.
Click to expand...
Click to collapse
Netarchy, Kingklick, or Hero_over's kernel
jerryparid said:
Netarchy, Kingklick, or Hero_over's kernel
Click to expand...
Click to collapse
+1.
I'm using hero 4 on stock odex with no issues and great battery life.
Thank you.
I will read into each kernel.
Any suggestions on which is best/worst?
EDIT: Thought I would post some links to each kernel you listed:
KiNgxKernel
netarchy-toastmod
I couldn't find the link for Hero_over's kernel. The forums search function is down for some reason.
Please correct me if those aren't the correct or official links to the kernels.
with netarchy it says:
An important note for Clockwork mod Recovery users:
Clockwork Mod is reportedly not wiping correctly (ie; if you try to wipe cache/dalvik-cache/data/etc it's not actually doing it, or not doing it right)
You may want to consider using Amon Ra Recovery instead.
Click to expand...
Click to collapse
I am using clockwork, so I think that eliminates netarchy from my choices.
Sent from my Evo using XDA App.
xNotta said:
Thank you.
I will read into each kernel.
Any suggestions on which is best/worst?
EDIT: Thought I would post some links to each kernel you listed:
KiNgxKernel
netarchy-toastmod
I couldn't find the link for Hero_over's kernel. The forums search function is down for some reason.
Please correct me if those aren't the correct or official links to the kernels.
with netarchy it says:
I am using clockwork, so I think that eliminates netarchy from my choices.
Sent from my Evo using XDA App.
Click to expand...
Click to collapse
not wiping correctly may cause your phone to bootloop no matter the kernel(Fresh's seems to be particularly sensitive to it), you should be ok though. If it happens just keep redoing it till it works.
I'm using netarchy's 4.1.9 cfs ATM and it's working great. Smooth as butter.
king kernel is really good, thats what im on right now. medium use: 500+ texts, wifi on, data on, hour of browsing, 30 mins of music playing, live wallpaper. with all that im hitting ~13 hours and im at 8% right now. king kernel is pretty good, nice and smooth too
ms79723 said:
king kernel is really good, thats what im on right now. medium use: 500+ texts, wifi on, data on, hour of browsing, 30 mins of music playing, live wallpaper. with all that im hitting ~13 hours and im at 8% right now. king kernel is pretty good, nice and smooth too
Click to expand...
Click to collapse
Wow! that is double my current battery time with stock and everything turned off to conserve power.
Should I use BFS or CFS?
Can I back it up my kernel so I can reflash it if I ever need to?
(there is a link to stock kernel on netarchy's xda post)
I added a poll. Please vote for your favorite.
xNotta said:
Wow! that is double my current battery time with stock and everything turned off to conserve power.
Should I use BFS or CFS?
Can I back it up my kernel so I can reflash it if I ever need to?
(there is a link to stock kernel on netarchy's xda post)
I added a poll. Please vote for your favorite.
Click to expand...
Click to collapse
im on the latest king kernel which is BFS (the king kernel #9)
as for backing up your kernel...i dont know...(didnt know that was possible). once you unlock fps, you'll never want to go back.
edit: also forgot to add that my screen off is underclocked to max:245 and min:245. so that made a HUGE difference in battery life
xNotta said:
Wow! that is double my current battery time with stock and everything turned off to conserve power.
Should I use BFS or CFS?
Can I back it up my kernel so I can reflash it if I ever need to?
(there is a link to stock kernel on netarchy's xda post)
I added a poll. Please vote for your favorite.
Click to expand...
Click to collapse
There really is no generalization for which is better, BFS or CFS. Every phone is slightly different in build due to margin of error in production. Some people have great results with BFS where others do not. I tried both extensively on Netarchy and much prefer CFS (better performance and battery). Why? I don't know. It just works for me. You will probably have to do some experimenting of your own.
Edit: Also concerning recoveries, I would go ahead and flash Amon_RA's recovery over ClockworkMod just to avoid conflicts. Amon works with everything is very straightforward to use.
Sent from my PC36100 using XDA App
sombdy said:
Edit: Also concerning recoveries, I would go ahead and flash Amon_RA's recovery over ClockworkMod just to avoid conflicts. Amon works with everything is very straightforward to use.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Rom Manager won't work with Amon_RA, will it?
I still know very little about root abilities so I would like so stay with something easy like rom manager.
And are Nandroid back ups interchangeable between recovery images?
Sent from my Evo using XDA App.
xNotta said:
Rom Manager won't work with Amon_RA, will it?
I still know very little about root abilities so I would like so stay with something easy like rom manager.
And are Nandroid back ups interchangeable between recovery images?
Sent from my Evo using XDA App.
Click to expand...
Click to collapse
you can use rom manager to install ra, but then all you'll be able to use rom manager for is to download roms. Which is still ok - some folks prefer it this way, because some things shouldnt be too easy, if you know what I mean. If you let a tool do all the work, what do you do when that tool breaks or is unavailable, and you have to do it manually?
ra can only be used outside of rom manager. Nands cannot be used between ra and clockwork - if you backup with ra, you need to restore with ra, and if you backup with clockwork, you need to restore with clockwork.
fachadick said:
you can use rom manager to install ra, but then all you'll be able to use rom manager for is to download roms. Which is still ok - some folks prefer it this way, because some things shouldnt be too easy, if you know what I mean. If you let a tool do all the work, what do you do when that tool breaks or is unavailable, and you have to do it manually?
Click to expand...
Click to collapse
I know exactly where you are coming from.
This is only my first few days with root, so I want to make sure my first few backups are done correctly.
So, RA is a beter recovery?
Sent from my Evo using XDA App.
xNotta said:
I know exactly where you are coming from.
This is only my first few days with root, so I want to make sure my first few backups are done correctly.
So, RA is a beter recovery?
Sent from my Evo using XDA App.
Click to expand...
Click to collapse
I don't mean to be ambiguous, but it really depends who you talk to. Some people swear by RA, and insist that clockwork doesn't wipe properly. Other people can conclusively prove that clockwork does indeed wipe properly, and use that with no issues. Personally, I use clockwork, but do all my flashing and wiping manually and not through rom manager. The only time I ever had any issues was a while ago, with an older version of clockwork.
I also think that clockwork has the benifit of not requiring signed zips, but don't quote me on that.
edit - just wanted to add that some devs will specify one or the other to be specifically used for whatever it is that you'll be flashing. So if they say to use X to flash, you better try using X to flash before asking why you're having issues
idk im new to trying kernals, but im running fresh 2.2 and im only getting 31-33 fps.
using kinklicks bfs 9 kernal
any help?
I have tried most of the kernels listed. For me, the best has been Netarchy's 4.1.9.1 cfs. It is smooth and has not had a single glitch, which I can't say for the others I have tried. The second best I tried was the Baked snack battery kernel #5.
cfs or bfs? What I found was that bfs gave slightly better benchmark scores than cfs, but I had a lot of odd problems or glitches when running bfs kernels (mainly scrolling lag in some apps, and some apps fcing randomly). haven't had any problems with the cfs kernels. Frankly, I haven't found any advantage to bfs because, while it seems to give better benchmark scores, in actual use it seems much slower and more laggy to me than cfs.
Clockwork or AmonRa recovery? I have used both, only had a problem once (boot loop), and that was with clockwork. Since then, I have always used Amonra's recovery to flash with. When flashing just a kernel just wipe cache and Dalvik cache, then flash the kernel. As long as you do not wipe data (reset) you should not lose anything when you flash the kernel.
Oh, and when you do a nand backup, it backs up the kernel you are currently using with it. So you can easily switch back and forth to test by restoring your backups.
fachadick said:
I also think that clockwork has the benifit of not requiring signed zips, but don't quote me on that.
Click to expand...
Click to collapse
As of version 1.8.0.0, Amon_RA's recovery no longer requires signed .zip's.
Sent from my PC36100 using XDA App

[Q] Not bricked but i cant boot my roms!

So my roms i download will install and boot up but once i get to that specific roms boot screen it just does an infinite loop. i then take the battery out, boot it into recovery and go back to my back up. I am not sure why it is doing this and would just love to be able to use cm7 (which did the infinite boot as well). its rooted using unrevoked and i have used a few other roms on it as well this has just been what has been happening lately. any help would be much appreciated!!
Had the same prob with cm7 #22, but 23 is working just fine, try that one. Remember the Dec said some may be broken, just fish around, but be very careful.
Sent from my ADR6300 using XDA App
Sorry, meant to say the "dev" said some cm7 nightlys are experimental and may be broken. Flash to the last rom that functioned for you, then use rom manager to download the latest cm7 nightly. Which is what I'm using now and am very satisfied with.
Sent from my ADR6300 using XDA App
30 is running great for me
6stringandy said:
Sorry, meant to say the "dev" said some cm7 nightlys are experimental and may be broken. Flash to the last rom that functioned for you, then use rom manager to download the latest cm7 nightly. Which is what I'm using now and am very satisfied with.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
see i tried the latest one and a few others. im not sure what it could be, that makes them go to the infinite boot screen. Should i try factory reset, root it again, restore my old version, then try to boot more roms?
crazyturtle777 said:
see i tried the latest one and a few others. im not sure what it could be, that makes them go to the infinite boot screen. Should i try factory reset, root it again, restore my old version, then try to boot more roms?
Click to expand...
Click to collapse
Flash CM7 in recovery. Then BEFORE you reboot, install a different kernel
This is your best choice for CM7 - http://forum.xda-developers.com/showthread.php?t=905873
Then reboot your Inc and see if it boots up, I have heard of a couple people who couldn't get their Inc to boot up with the stock CM& kernel, no clue why though.
hahaha so i got it to work. it was rom manager not letting me go through with it all. just did it manually through recovery. but i got sm7 to install and no notification bar. hence why im laughing. just gonn install miui and give her a shot.

Kernel Troubles

Not sure if its the fact i am running CM 7 or what but whenever i try a different kernel then there stock everything boots just fine but the touch screen doesn't work. I am lost and have no clue what to try.
What kernel are you trying to flash?
Sent from my ADR6300 using XDA Premium App
If running cm7, ya gotta flash a gingerbread AOSP kernel - try that.
Sent from my ADR6300 using XDA Premium App
I believe it was the AOSP kernel part that i was missing. I finally got a Invisiblek to install. Thanks for the help.
bjohnson8949 said:
I believe it was the AOSP kernel part that i was missing. I finally got a Invisiblek to install. Thanks for the help.
Click to expand...
Click to collapse
Invisiblek is the way to goon Gingerbread roms. I've flashed his newest with OMFGB 1.1.1, and it is awesome. No problems snappy, excellent battery too!
Sometimes people (including me) mix up AOSP and Sense, sadly they don't like to play with others if you install them with the wrong rom. Racists, pft.
I have only had the phone about a week now so I have had a lot to learn. So far everything seems good now and I am happy. Now if i could just get better battery life lol.
I was trying to install the following http://forum.xda-developers.com/showthread.php?t=972746 I am getting same issue installs fine boots. Then when I try to unlock screen I get nothing. I have HtC incredible running cm 7 rc 3
clockworkmod 3.0.0.8
radio 2.15.00.11.19
If you need anymore information let me know.
I am doing the following for install.
reboot to recovery
clear cache
clear dalvik cache
install zip from sd card
Thanks for all the help already
bjohnson8949 said:
I was trying to install the following http://forum.xda-developers.com/showthread.php?t=972746 I am getting same issue installs fine boots. Then when I try to unlock screen I get nothing. I have HtC incredible running cm 7 rc 3
clockworkmod 3.0.0.8
radio 2.15.00.11.19
If you need anymore information let me know.
I am doing the following for install.
reboot to recovery
clear cache
clear dalvik cache
install zip from sd card
Thanks for all the help already
Click to expand...
Click to collapse
It worked fine for me...and still working
Maybe download it again and then try it. Just as a question are you by chance trying to flash a froyo kernel and not realizing it? Its gotta say gb or gingerbread
Sent from my ADR6300 using XDA App
I was trying to flash Tiamat Version 3.3.3-sbc -- Current Gingerbread with SBC from the link I posted.
bjohnson8949 said:
I was trying to install the following http://forum.xda-developers.com/showthread.php?t=972746
Click to expand...
Click to collapse
bjohnson8949 said:
I was trying to flash Tiamat Version 3.3.3-sbc -- Current Gingerbread with SBC from the link I posted.
Click to expand...
Click to collapse
The link you provided is the EVO kernel. Have you tried the Inc kernel?
Evo: http://www.thebcblends.com/cayniarb/Kernels/evo/Tiamat_Evo-v3.3.3-sbc.zip
Inc: http://www.thebcblends.com/cayniarb/Kernels/inc/Tiamat_Inc-v3.3.3-sbc.zip
The zip files have different contents.
EDIT - I just realized the thread you linked has both the Inc and the Evo versions. I saw that it was in the Evo subforum and jumped to the wrong conclusion. In any regard, make sure you are flashing the right one.
I just flashed
Inc: http://www.thebcblends.com/cayniarb/Kernels/inc/Tiamat_Inc-v3.3.3-sbc.zip
and i am still having same problem. Any ideas ?
Edit: Messing around with rooted phones is something I have just started so it maybe something simple I am missing.
Not sure why my cell doesn't seem to like other kernels but
http://forum.xda-developers.com/showthread.php?t=905873
seems to be doing just fine so i will leave it alone.
Thanks for all the help.
Have you tried Incredikernel? Kernels are really a matter of personal preference, but Incredikernel seems to be one of the best. (And also my favorite.)
I gave it a shot a while back and had trouble. My issue is that he touch screen doesn't respond. Incredikernel is recommended in several places but i had zero luck with it supporting the screen. I have started to wonder if its support for slcd.
I will try it again and see what happens.

A boot loop in every custom ROM installed?

Hi, my Evo is a launch one (HW002). Ive been running Magnus ROM for the last month, but today I decided to give Virus's ROM a try, and after download and 3 wipes of the usual suspects (cache, dalvik, data) plus the Format All zip, I flashed my ROM but when I came back I was stuck on a boot loop. So I nand back to Magnus again, and then decide to flash Kings 2.3 Sense ROM, and also had a boot loop! This has never happened before, and I was able to nand back to Magnus..... is there something wrong with my phone, that is not letting me flash ANY new ROM at all???
Well I don't own eco but I think u should format data and stuff before flashing and go back to stock and start all over and also I would never try a rom with the name virus smh
Sent from my SGH-T959 using XDA Premium App
Droga said:
Hi, my Evo is a launch one (HW002). Ive been running Magnus ROM for the last month, but today I decided to give Virus's ROM a try, and after download and 3 wipes of the usual suspects (cache, dalvik, data) plus the Format All zip, I flashed my ROM but when I came back I was stuck on a boot loop. So I nand back to Magnus again, and then decide to flash Kings 2.3 Sense ROM, and also had a boot loop! This has never happened before, and I was able to nand back to Magnus..... is there something wrong with my phone, that is not letting me flash ANY new ROM at all???
Click to expand...
Click to collapse
What recovery are you using to flash the rom? Clockwork or Amon ra? What radios are you on? Which Virus rom were you trying to flash? I've never had trouble.trying.to boot any of his.roms, they are usually solid.
Sent from my PC36100 using XDA App
k2buckley said:
What recovery are you using to flash the rom? Clockwork or Amon ra? What radios are you on? Which Virus rom were you trying to flash? I've never had trouble.trying.to boot any of his.roms, they are usually solid.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Amons recovery, latest radio and newest Virus 2.3 ROM. Ive never had trouble flashing ANY ROM before, and all of a sudden my phone is acting up. At least it is letting nand back to my previous ROM.
Droga said:
Amons recovery, latest radio and newest Virus 2.3 ROM. Ive never had trouble flashing ANY ROM before, and all of a sudden my phone is acting up. At least it is letting nand back to my previous ROM.
Click to expand...
Click to collapse
Hmm, that's odd. Are you sure the files you're trying to flash aren't corrupted? You said you did a full wipe, including a format all, so an improper wipe is ruled out. I unfortunately don't have a lot to suggest. I think if that was happening to me, I would first try reflashing my recovery, and then try wiping and flashing again.
Sent from my PC36100 using XDA App
k2buckley said:
Hmm, that's odd. Are you sure the files you're trying to flash aren't corrupted? You said you did a full wipe, including a format all, so an improper wipe is ruled out. I unfortunately don't have a lot to suggest. I think if that was happening to me, I would first try reflashing my recovery, and then try wiping and flashing again.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Already tried that, no go.
I guess Im stuck with my ROM for the time being....
Droga said:
Already tried that, no go.
I guess Im stuck with my ROM for the time being....
Click to expand...
Click to collapse
I wish I had more to try suggesting for you. Its odd that both of the roms you tried flashing were sense based 2.3 roms. I wonder if you're phone doesn't like the kernel that comes cooked into those roms. I think virus's 2.3 rom uses the same kernel as the 2.3 king's rom. Perhaps after you flash the rom, you could power off the phone, take out the sd card, and try booting it without the sd card in it. I've heard of weird booting issues being caused by an issue with the sd card. It certainly couldn't hurt anything to try it, but I would think that if that was the issue, you'd have trouble booting any rom. I'd still try it though.
k2buckley said:
I wish I had more to try suggesting for you. Its odd that both of the roms you tried flashing were sense based 2.3 roms. I wonder if you're phone doesn't like the kernel that comes cooked into those roms. I think virus's 2.3 rom uses the same kernel as the 2.3 king's rom. Perhaps after you flash the rom, you could power off the phone, take out the sd card, and try booting it without the sd card in it. I've heard of weird booting issues being caused by an issue with the sd card. It certainly couldn't hurt anything to try it, but I would think that if that was the issue, you'd have trouble booting any rom. I'd still try it though.
Click to expand...
Click to collapse
If his phone doesn't like the stock kernel, I'd recommend flashing a custom kernel in the same session, after wiping the cache and dalvik after he flashes the rom.
teh roxxorz said:
If his phone doesn't like the stock kernel, I'd recommend flashing a custom kernel in the same session, after wiping the cache and dalvik after he flashes the rom.
Click to expand...
Click to collapse
Right, which is definitely what I'd normally suggest. However, since he's trying to use the new Sense 2.3 roms, there arent really any custom kernels for those roms yet. Some people have reported success with Netarchy's, but it breaks the camera app. Other people reported loops with netarchy. Basically, there arent any custom kernels for any 2.3 GB + sense roms yet, so his kernel switching is limited. He could try another one, and may have it work, as some other people had reported. But his camera won't work!
k2buckley said:
Righ, which is definitely what I'd normally suggest. However, since he's trying to use the new Sense 2.3 roms, there arent really any custom kernels for those roms yet. Some people have reported success with Netarchy's, but it breaks the camera app. Other people reported loops with netarchy. Basically, there arent any custom kernels for any 2.3 GB + sense roms yet, so his kernel switching is limited. He could try another one, and may have it work, as some other people had reported. But his camera won't work!
Click to expand...
Click to collapse
I had already tried another ROM ( Myn's Warm Z) just to see if it is the kernels and the Sense 2.3 combination, but that didnt give me any problems at all. So Im guessing it is the kernel included in those ROMS. I will try your suggestions, though, just to see if they actually make a difference. Thanks for the kind help.
k2buckley said:
Right, which is definitely what I'd normally suggest. However, since he's trying to use the new Sense 2.3 roms, there arent really any custom kernels for those roms yet. Some people have reported success with Netarchy's, but it breaks the camera app. Other people reported loops with netarchy. Basically, there arent any custom kernels for any 2.3 GB + sense roms yet, so his kernel switching is limited. He could try another one, and may have it work, as some other people had reported. But his camera won't work!
Click to expand...
Click to collapse
True...but from what I've heard [haven't flashed it] but some have reported success with stock kernel 15, and it not breaking anything, so he could try that...
teh roxxorz said:
True...but from what I've heard [haven't flashed it] but some have reported success with stock kernel 15, and it not breaking anything, so he could try that...
Click to expand...
Click to collapse
This is true.
Hey OP, you catching this? Lol. Try flashing the stock HTC 15 kernel right after you flash the rom, but before you boot. See if that makes any difference.
This is why teamwork wins.
teh roxxorz said:
True...but from what I've heard [haven't flashed it] but some have reported success with stock kernel 15, and it not breaking anything, so he could try that...
Click to expand...
Click to collapse
k2buckley said:
This is true.
Hey OP, you catching this? Lol. Try flashing the stock HTC 15 kernel right after you flash the rom, but before you boot. See if that makes any difference.
Click to expand...
Click to collapse
I will do this and come back with results in a while.
Muy Bien amigo.
I'll be floating around.
teh roxxorz said:
This is why teamwork wins.
Click to expand...
Click to collapse
Always true!
Hopefully the different kernel helps him out!
Tried stock kernel #15: no go.
Thanks for the help, though!
Droga said:
Tried stock kernel #15: no go.
Thanks for the help, though!
Click to expand...
Click to collapse
Damn. That sucks. I'm not sure what would be causing that. You wiped, you tried a different kernel, your radios and PRI are updated, you tried booting without the SD card in place. I'm not sure what'd send you to bootloops. Did you happen to try updating to the most recently leaked radio? The one that was in the dump from the leaked gingerbread rom? Although I doubt that'd make any difference, but you never know. I flashed it the other day, and it works just as good as all the other ones. I never really notice a major difference from changing radios. But the leaked one does work.
Droga said:
Tried stock kernel #15: no go.
Thanks for the help, though!
Click to expand...
Click to collapse
Sorry man.
teh roxxorz said:
Sorry man.
Click to expand...
Click to collapse
No worries. I was able to install a new custom ROM just now (Kings R3) and it installed just fine. I will try again to install the other ROMS just to see if it will work today.

Quick maybe stupid question.

I have been reading where people are getting the nightly CM7 builds. I was wondering first off how do I go about setting this up. Secondly does this wipe your setting every time? It would be a pain to have to setup the phone every day. Also I have ripped out the ADW launcher as I find the Go Launcher to be superior is this something that would be overwritten? Thanks in advance for the knowledge, still new to the forum and handicapped as far as knowledge base when it comes to this.
carsenj said:
I have been reading where people are getting the nightly CM7 builds. I was wondering first off how do I go about setting this up. Secondly does this wipe your setting every time? It would be a pain to have to setup the phone every day. Also I have ripped out the ADW launcher as I find the Go Launcher to be superior is this something that would be overwritten? Thanks in advance for the knowledge, still new to the forum and handicapped as far as knowledge base when it comes to this.
Click to expand...
Click to collapse
Nightly builds can be downloaded via ROM manager, you need to have a premium licence though or you can get them from here.
I theory all of your setting would remain the same, but sometimes nightly builds can be unstable and broken, but for the majority of the time you would not experience any issues.
Have you installed go launcher to system/app? If so you would lose this every time you flash because flashing a rom rewrites the system partition. But if you have just installed it like a normal app it still be there after you flash.
Hope this helps
cjward23 said:
Nightly builds can be downloaded via ROM manager, you need to have a premium licence though or you can get them from here.
I theory all of your setting would remain the same, but sometimes nightly builds can be unstable and broken, but for the majority of the time you would not experience any issues.
Have you installed go launcher to system/app? If so you would lose this every time you flash because flashing a rom rewrites the system partition. But if you have just installed it like a normal app it still be there after you flash.
Hope this helps
Click to expand...
Click to collapse
That helps immensely. I have attempted to purchase the full Rom Manager to no avail. It just sits in the verifying state. So I just returned it. If I dl it from the mirror I'll have to install from recovery not the rom manager because to install from a zip is also only in the premium license version.
As for the settings. I just installed the Go Launcher like any other app no special settings. So I should be good?
carsenj said:
That helps immensely. I have attempted to purchase the full Rom Manager to no avail. It just sits in the verifying state. So I just returned it. If I dl it from the mirror I'll have to install from recovery not the rom manager because to install from a zip is also only in the premium license version.
As for the settings. I just installed the Go Launcher like any other app no special settings. So I should be good?
Click to expand...
Click to collapse
To be honest your better not using rom manager and just doing everything manually in recovery, rom manager is known to on occasion cause issues. And yes if you flash a new nightly go launcher would still be there. Just do a nandroid first to be safe
What version of CM are you using at the moment?
[sig]stock gingerbread rocks[sig]
cjward23 said:
To be honest your better not using rom manager and just doing everything manually in recovery, rom manager is known to on occasion cause issues. And yes if you flash a new nightly go launcher would still be there. Just do a nandroid first to be safe
What version of CM are you using at the moment?
[sig]stock gingerbread rocks[sig]
Click to expand...
Click to collapse
At the moment I am just running the CM 7 release 7.0.2. It is running great. I'm running it in conjuntion with Pershoots kernel and couldn't be happier. Just thought it'd be nice to check out new builds every so often just didn't want to spend 2 hours reconfiguring my phone again.
As for using recovery, I may actually do that. I have been wanting to get more into the process and what not. Having to root the phone through ADB got me interested more in the inter workings of these little devices that run our lives.
carsenj said:
At the moment I am just running the CM 7 release 7.0.2. It is running great. I'm running it in conjuntion with Pershoots kernel and couldn't be happier. Just thought it'd be nice to check out new builds every so often just didn't want to spend 2 hours reconfiguring my phone again.
As for using recovery, I may actually do that. I have been wanting to get more into the process and what not. Having to root the phone through ADB got me interested more in the inter workings of these little devices that run our lives.
Click to expand...
Click to collapse
The reason I asked what verson you were on is because if you do start using the nightlys you can't then downgrade to a stable release with out doing full wipes. Due to nightys being 2.3.4 and stables being 2.3.3
CWM is fairly easy to use
Sent from an ice cream sandwhich
Actually just read the last couple pages of the nightly thread. They have a stable release of 7.0.3. Dling right now to check it out. Thanks for the knowledge.
cjward23 said:
The reason I asked what verson you were on is because if you do start using the nightlys you can't then downgrade to a stable release with out doing full wipes. Due to nightys being 2.3.4 and stables being 2.3.3
CWM is fairly easy to use
Sent from an ice cream sandwhich
Click to expand...
Click to collapse
Nevermind got it all figured out. Everything seems to be working and this build seems pretty stable.

Categories

Resources