I lurked around the GlitchV13 forum for a good long time and didn't find an answer to this.. and because I've only been lurking for about a year I wasn't able to post anything, so it's about time I guess.
I'm having problems with the GlitchV13 kernel. Maybe I'm just being dumb and don't see something here. some help would be greatly appreciated.
I flashed GlitchV13 on my CM7.1 using CWM 5.0.2.7. No problems at all. Running great for two days. Suddenly, my phone won't connect to wifi. Cycled airplane mode and nothing popped up, so I did a reboot.. annnd got stuck in a bootloop between the CM splash and my lockscreen (wtf). Rebooted again, and now I'm stuck on the CM7 screen. Tried to Odin CWM4, still no bueno, and I get a "E:Can't mount recovery/log/"blahblahblah.
Admittedly, this happened one time before- I did a clean install from stock. Then I got gutsy and flashed GV13 again. Any idea why this is happening? After I flashed Glitch I didn't touch any other recoveries, nor did I try to push anything with Odin or Heimdall.
I really just don't wanna flash back to stock again, and a new solution to why this is happening would be super!
Thanks in advance.
EDIT: Got it. Glitch comes packaged with 4.x CWM, while CM7 comes packaged with 5.0.2.7. Any way to reconcile the two? Worth it to push 4.x over 5.x, flash Glitch then backup so I don't have to do a full restore to CM7?
I had the wifi problem on the stock kernel once, so I dont think that problem is with Glitch.
I also just flashed the latest kernel version and they have updated CWM to 5.0.2.7.
That being said are you sure the recovery is making this much trouble on the phone? Usually it doesn't make a difference (besides backups and whatnot).
The glitch recovery has a few extra features that the CM7 recovery does not.
one being able to wipe dalvik and cache at the same time. (very minor but its more convenient)
I personally think its worth it.
Related
So I've got a problem for you gurus out there. A little history...
It all started last week when I tried flashing to KaosFroyo v38 and it was eating my battery alive. People suggested flashing CFS kernel v6 (at the time) but every time I flashed I would never get past the skating androids. I factory wiped, davlik wiped, still no go. After messing with it for a couple days I just re-flashed back to KF v37 and figured I would wait for a new rev.
So this week CFS v8 is out and the new governor feature which I am really wanting to try so I figured I would give it a go again. Factory and dav wipe, flashed KFv38, flashed CFSv8 on top, same issue with the skating androids. Someone suggested to try a different rom. So, I tried CELBv3.6 since it had the same kernel and still no go. This morning I tried FloyoTazz v17 and the same issue.
It appears that it might be kernel related but I am really not sure. I PM'd conap and he suggested I get a logcat at boot to diagnose, but my device doesn't seem to boot enough to detect the device on my PC. When I enter adb logcat it just says "- waiting for device -" and if I enter adb devices nothing is listed. It's like all my phone does is turn on and thats it.
KaosFroyo is the only rom I've tried that I can get to flash and boot and v37 is the only one that doesn't drain my battery so thats where I am at.
Any help would be much appreciated.
Bump. Still looking for answers.
P.S. - Helped my friend root his eris this morning. Installed TazzFroyo v17 first time no problems. I'm really curious what in the world is causing my phone to not boot up...so weird.
Man I guess I really stumped you guys.
Just an update on some things I tried yesterday.
1. Reformated my SDCard to a single partition. No change.
2. Tried booting without SDCard. No change.
3. Unrooted back to factory 2.1. Re-rooted and flashed. No change.
I'm running out of google searches and ideas. Since I can't boot long enough for my PC to recognize my phone, is there a way I can run a boot log locally on my phone without adb? Unfortunately until I get a boot log of some sort, I'm stuck with the trial and error approach.
It is possible that your phone can't handle the CPU speed of 710 that the ROM and Kernal are clocked at. That would put you into a boot loop. I have seen that before. Not common, but it has happened. You might be able to PM Conap for suggestions on how to lower the clock speed before you boot up. I believe it can be done through the computer link in recovery.
koamalu said:
It is possible that your phone can't handle the CPU speed of 710 that the ROM and Kernal are clocked at. That would put you into a boot loop. I have seen that before. Not common, but it has happened. You might be able to PM Conap for suggestions on how to lower the clock speed before you boot up. I believe it can be done through the computer link in recovery.
Click to expand...
Click to collapse
I've run setcpu at 710 without issues, but definitely something to try. Thanks for the tip.
Just to follow up on this issue which is now resolved.
I have been working with Conap who writes the kernel for many of the new roms out there for the past week and we finally resolved the issue. Apparently with CFSv6+ he added CIFS support to the kernel which was causing the boot problem for me. After removing that from the kernel, everything flashes fine.
Hi, all. Relative noob here. Fascinate, Stock ED04 OTA, Rooted, modified stock kernel to "stick" CWM, Bloat frozen using TB.
I want to take the next step of flashing a ROM, and am doing (I feel) due dilligence by reading everything possible in this forum. However, I think I'm starting to suffer from information overload, and confusion has set in.
I used Odin to flash CWM 3.0.2.8x.ti. Immediately after selecting backup and restore/backup, I get "Error while backing up boot image". I see a few posts with the same statement, but no resolution. Flashed back to CWM 2.5; and backup appears to complete successfully. However, the date of the backup is 2000-01-01; and this is consistent on repeated attempts. The time and date on my phone (when booted) is correct.
Am I missing something? Any help would be greatly appreciated.
dhartman977 said:
Hi, all. Relative noob here. Fascinate, Stock ED04 OTA, Rooted, modified stock kernel to "stick" CWM, Bloat frozen using TB.
I want to take the next step of flashing a ROM, and am doing (I feel) due dilligence by reading everything possible in this forum. However, I think I'm starting to suffer from information overload, and confusion has set in.
I used Odin to flash CWM 3.0.2.8x.ti. Immediately after selecting backup and restore/backup, I get "Error while backing up boot image". I see a few posts with the same statement, but no resolution. Flashed back to CWM 2.5; and backup appears to complete successfully. However, the date of the backup is 2000-01-01; and this is consistent on repeated attempts. The time and date on my phone (when booted) is correct.
Am I missing something? Any help would be greatly appreciated.
Click to expand...
Click to collapse
i have had the same thing happen every time i try and backup. I'm wondering if it has anything to do with the newer recovery b.c when i had 2.5 i had no issues with it. Anybody have an answer for this?
I was in the same boat as you: rooted and bloat frozen via TB since the first week, and just added the modified kernel with CWM 3 earlier this past week. Haven't had any problems with it. I used Heimdall to flash CWM and the kernel. Now I'm running Evil Fascination with the LG Alternate Launcher. Tried ComRom but didn't care for it, though the default wallpaper was very pretty.
Back to the point, after I flashed the kernel and CWM I restarted the phone, let it boot, then rebooted into recovery to backup, instead of unplugging it and immediately booting Recovery.
Honestly, you've made it this far, you want to get a new ROM, I say download one and follow the directions (read them three times top-to-bottom) before flashing, and you should be good.
Yeah - I think Evil is where I want to end up until CM7 is fully functional (just spent all morning reading the CM7 waiting room thread).
Unfortunately, I'm apprehensive about flashing a new ROM until I can get a good backup image. I'm not sure why I'm getting the erroneous date on the backups. I could certainly be doing something wrong; just not sure what (if anything).
Maybe I need to use a different CWM? 2.5.1 and 3.0.2.8. don't seem to have worked for me. Also, If I understand what eulipion2 said, I have already fully booted, then powered down and rebooted into CWM to do a backup. 3.0.2.8 fails and 2.5.1 gives be incorrect dates.
Going to do a few hours of reading on CWM, I guess!
I'm using the first kernel listed in this thread from times_infinity. I initially flashed ComRom, didn't like it, kept this recovery, and flashed EF. Works great so far.
Give the Nandroid a go with this Recovery and see if it works for you.
hey i figured out how to get the back up to work. you have to enable voodoo and then it will work
Hey guys. Thanks for the suggestions. Tried the CWM 3 link from above, still no dice. I suspect I may need to have a voodoo kernel installed to actually enable the voodoo and try the backup again. Makes sense I guess.
Getting frustrated.
Success! Flashed a voodoo kernel, and was able to get (what appears to be) a successful nandroid backup with 3.0.2.8 (red). Never did get 2.5.1 (yellow) working. Strange, but irrelevant. CM7 build 7 is looking like it's ready for a test drive.
I had rooted my TB using TB auto root, and flashed Gingeritis 3d when I first got my TB last month.
I wanted to try out an aosp rom like CM7.
So I dled the rom, dled zoom kernel, and got the MR2.5 radio to be sure.
I flashed the radio first, booted into Gingeritis just fine with signal.
So I then rebooted into recovery, did a factory wipe, dalvik, and cache.
I then hit instal zip from sd, found the zoom kernal zip, installed it, and then did the same for the CM7 rom. But when I reboot, It just sits on the white HTC splash screen.
I had tried it through ROM Manager last week, and it had done the same thing. I thought it was the kernal, but as I flashed the kernel this time.. and it's still doing it. I don't know whats wrong.
Can someone tell me what I'm doing wrong?
I'd really like to get CM7 running on this thing.
Thanks guys
Deviant6 said:
I had rooted my TB using TB auto root, and flashed Gingeritis 3d when I first got my TB last month.
I wanted to try out an aosp rom like CM7.
So I dled the rom, dled zoom kernel, and got the MR2.5 radio to be sure.
I flashed the radio first, booted into Gingeritis just fine with signal.
So I then rebooted into recovery, did a factory wipe, dalvik, and cache.
I then hit instal zip from sd, found the zoom kernal zip, installed it, and then did the same for the CM7 rom. But when I reboot, It just sits on the white HTC splash screen.
I had tried it through ROM Manager last week, and it had done the same thing. I thought it was the kernal, but as I flashed the kernel this time.. and it's still doing it. I don't know whats wrong.
Can someone tell me what I'm doing wrong?
I'd really like to get CM7 running on this thing.
Thanks guys
Click to expand...
Click to collapse
I'm not familiar with cm7 on this phone. I enjoy sense roms so I haven't played with cyanogen.
Are you positive the kernel is compatible with asop roms? If yes, download the ROM again and verify the md5 after you place it on the phone.
Also make sure you delete the radio pg05img.zip or whatever the correct spelling is from the phone as well. Sounds like you already did that but just making sure.
Flash from recovery not ROM manager.
Sent from my Synergy driven Thunderbolt...
I'm restoring it now.
I had tried flashing through RM 3 times last week and got the same issue.
And I'm pretty sure the kernels I flashed are aosp kernels.
I searched for CM7 kernels, and I know for sure the zoom one is an aosp kernel.
I've found lots of people with the same issue online, but found no fixes.
I don't know what to do.
I really need some help here guys. someone experienced flashing cm7 or aosp roms.
Does it have something to do with me trying to go from a sense rom to a aosp rom?
I thought all I had to do was change the kernel...?
If someone can give me a link to a cm7/kernel/radio combo they KNOW works, I would really really appreciate it.
Has anyone gotten through this issue before?? If so, what did you do to get past it!?!?!?
Are you positive you downloaded cm 7 for the thunderbolt and not some other device? I would try wiping everything from recovery (system, data, etc.) then install just the rom and see if it boots. And, as stated above, check the MD5. Could just be a corrupt file.
Sent from my ADR6400L using Tapatalk
bpyazel said:
Are you positive you downloaded cm 7 for the thunderbolt and not some other device? I would try wiping everything from recovery (system, data, etc.) then install just the rom and see if it boots. Are you letting it sit long enough? First boot of a fresh rom can take a while (5 - 10 minutes).
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
Well, I've searched around and found: update-cm-7.1.1-Thunderbolt-signed.zip
which I assume is the correct one.
And I know the first boot takes a good while, but it doesn't sit at the splash screen, they take a long time during the boot animation. Which mine doesn't even get to.
And I've let it sit 15+mins. so it's not that.
I'm trying it through RM this time (again) and even though I had the most up to date version of it, I reflashed RM (hoping that was the issue) and i downloaded and im installing CM7 from RM now.
EDIT:
I found the issue. Well, the only thing I did differently this time was to reflash Clockwork Mod Recovery from Rom Manager.
I had the most current one already, but I did it anyways, and redid all the steps, and now I'm in.
So I don't know if it was corrupted, or w/e, but that seemed to do it.
So for everyone else getting stuck at the white splash screen after flashing: Restore your phone to the previous rom, open Rom Manager, and hit the very top button: Flash Clockwork Mod Recovery (even if its allready updated)
After that, do your flash like normal.
It solved my issue and everything went fine.
getting to be far too familiar a scenario lately....
lately EVERY time i reboot my phone (running ics build 2, 3 and 4, stock kernel) it gets stuck on samsung logo.. somehow my phone will only boot into the frigging cm7 recovery which as im sure youre all aware is rather useless to fix any problems im having in ics and leaves me unable to flash, backup, or restore anything. it's quite frustrating and i have no idea how to fix it but by going back to bml, re-partitioning, then odin ei20 modem, cm7 fixed recovery, then flash back to ics but doin this every reboot it getting very tedious..
ive read about recovery loops, but the fix doesnt work for me as i cant mount the ICS /system partition in cm7 recovery...and ive been all over trying a zillion things to get it to work and havent pulled dmesg or logcat but if someone thinks it would be useful ..i wish i knew why EVERYTHING is great, then BANG, reboot and it's FML city.
i should add this phone is a replacement via insurance and that the entire time ive had it, i've been having this problem to varying degrees of intensity,.sometimes if i rebooted enough the ics boot animation would finally come up and freeze part way through, and in the first week with this phone is seemed fine. the first few times i rebooted and battery pulled until it started but this is the fourth time in two weeks ive found myself going back to repartition from odin and then back to ics.. the phone is only mine for a month,.
if nobody has any ideas ill be getting it replaced tomorrow in store. i have the no fee insurance replacement plan, but i would prefer not to have to use another as it's not under warranty and this would be my second replacement and this mes has to last me until the gnex hits uscc in hopefully april if it ever does because i'd rather switch to vzw than take any of usccs other offerings currently.. if they dont get the gnex it'll be time for me to move on...
anyway please advise.. thanks
http://exzacklyright.blogspot.com/2012/01/how-to-flash-ics-on-verizon-samsung.html
exzacklyright said:
http://exzacklyright.blogspot.com/2012/01/how-to-flash-ics-on-verizon-samsung.html
Click to expand...
Click to collapse
Thanks for the response. Sounds like a good guide for newbs but in my case information is redundant. I have no problems with the install, unless recovery switches to cm7 recovery during reboot and cannot manage to boot/flash/nandroid until I Odin stock ei20 with repartition and wipe out every bit of data I had. The posts about howto fix CWM bootloop for cm9 do not seem to work for me, as the post says.. Please reread the OP, ya got me excited thinking there was a solution ;-/ thanks anyway, maybe it will help another user.
wizayne said:
Thanks for the response. Sounds like a good guide for newbs but in my case information is redundant. I have no problems with the install, unless recovery switches to cm7 recovery during reboot and cannot manage to boot/flash/nandroid until I Odin stock ei20 with repartitions and wipe out every bit of data in had. The posts about howto fix cwm bootloop for cm9 do not seem to work for me, as the post says.. Please reread the OPEN, ya got me excited thinking there was a solution ;-/ thanks anyway, maybe it will help another user.
Click to expand...
Click to collapse
have you tried flashing glitch kernel to the phone. imo it sounds like a kernel issue and not so much a phone issue.
mkuehl06 said:
have you tried flashing glitch kernel to the phone. imo it sounds like a kernel issue and not so much a phone issue.
Click to expand...
Click to collapse
The problem started after using ics from alphalulz v1 on around build 3 team hacksung IMMEDIATELY AFTER flashing glitch kernel v14 build 4...I have since kept away from glitch on ics, and the problem remains.
Lately it hasn't been as bad though and it seems by hitting random buttons during boot that it will eventually start but reading tells me glitch v14 build 5 is still recovery bootloop ridden and I haven't seen a word about it in the OP for ANY ics components be it team hacksung roms or glitch kernel, and an issue like this which from reading is seemingly widespread *should* be mentioned.
Any suggestions?
In your op you said e120, what phone are you using. E120 isn't a fascinate build.
Sent from my SCH-I500 using XDA App
Ei20 is the latest and greatest version of gb/radio from uscc for the mesmerize, not that it'll change the outcome afaik to go to anything else... unfortunately ;-/
But it is a full flash package if ya open the tar up complete with movinand, sbl, radio, rfs, etc.. I think it is a 10 or 11 file package and I've used it a hundred times with making the switch from mtd to bml
wizayne said:
Ei20 is the latest and greatest version of gb/radio from uscc for the mesmerize, not that it'll change the outcome afaik to go to anything else... unfortunately ;-/
But it is a full flash package if ya open the tar up complete with movinand, sbl, radio, rfs, etc.. I think it is a 10 or 11 file package and I've used it a hundred times with making the switch from mtd to bml
Click to expand...
Click to collapse
That makes more sense to me now I know what phone your on. Try rootzwiki they have a mesmorize section, they can help ya out more than I can. I have fassy so idk much about mes
Sent from my SCH-I500 using XDA App
this is what i get for oding late at night but i managed to do something very very stupid I odined my phone with a one click package for my captivate
I've been able to get the phone back in mostly working order now though.. but i feel in my gut something still may not be right.
here is where i got the package
http://forum.xda-developers.com/showthread.php?t=1300843
This below is what version i accidently installed.
I897UCKI2 Android 2.3.5 Gingerbread
With Bootloaders - Link to thread - Second Post [With CWM Injected Kernel from Boog]
so after i made this mistake.. (noticed my phone had a at&t bootscreen an wouldn't load) I went forth an flashed stock firmware avail for aiotools for the vibrant an then installed the stock froyo bootloader
I'm hoping everything is right in its place well except once i get cm9 flashed it boots up an shows a EU error so i freak yank the battery an odin this phone back into the stoneage an well... surprisingly.... my internal memory is 100% there O.O
anyways current issue is not being able to get cm7 to install though i'm probably missing something due to being tired anyways..
help sugestions banter calling me a noob I just want to make sure i did possibly everything to fix this mistake.
pintek said:
I'm hoping everything is right in its place well except once i get cm9 flashed it boots up an shows a EU error so i freak yank the battery an odin this phone back into the stoneage an well... surprisingly.... my internal memory is 100% there O.O
Click to expand...
Click to collapse
You,my friend, dodged a bullet here.
pintek said:
anyways current issue is not being able to get cm7 to install though i'm probably missing something due to being tired anyways..
Click to expand...
Click to collapse
Well, when you say you are not able to get CM7 to install, what exactly is it doing?
Are you getting thrown into a bootloop (caused by CWR mismatch and pretty common)? If so, pull battery and boot into recovery and re-flash CM7 over itself again. No wipe. Then reboot.
You may have to flash a different kernel, like glitch or something like that. But try the above first. Should work for you. Does it still say ATT when you boot up?
Lucky for you, everything is good, but if you want to flash a GB or higher ROM, i would suggest you flash the bootloaders in this thread: http://forum.xda-developers.com/showthread.php?t=1117990
After that just flash CM9, and you *should* be good, if not, try flashing it again with wiping data, cache, and dalvik cache. I guarantee that will work.
I ended up having to format both SD cards an retrying install custom rom via aio tool an with luck was able to get cm7 installed then cm10 an i dno't have the ime error everyone else seams to have . I did before this flash the gb bootloader over this cause it was the only thing that managed to remove the at&t splash screen before the kernal.
Lesson I learned....
remember that the vibrant you use aio tool not a premade pack >.<
an ya i do own both phones so this does complicate things now an then <,<
I also have both devices. Set up two different folders on your pc, one marked i897 and the other t959. I also add i897 or t959 to any files that could possibly get mixed up in Odin.
Its peanut butter jelly(bean) time...