Related
It's on the teamdouche nightlies and I was wondering what it was, is it like CM6 final? and they're only going to work on CM7 now? Or like what?
Looking @ the size of the file, it must be cyanogen 7
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
agentg1001 said:
Looking @ the size of the file, it must be cyanogen 7
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
Click to expand...
Click to collapse
That was also my guess but I'd much rather have somebody who knows for sure, I'm about to do a backup and flash it though so I'm not even too worried about it now. I'll post back here when I've done it
if its the nightly thn yeah its CM7
currently running it
It IS the first nightly of CyanogenMod 7 (Gingerbread, 2.3.1). This can be used as a daily ROM. I'm running it now and I have been running it since last night. Some apps have to be updated to work on Gingerbread though.
So lately I've been getting the 5 vibration code and I've been searching around here and on other forums and no one seems to know what causes it. Has anyone else that's been experiencing this noticed that it seems to go away after a battery pull and then letting the phone cool down? I'm rooted with unrevoked running cm7 rc2 with Chad's newest kernel right now and tried running cm7 with the included kernel and experienced the same issue.
My main concern is whether to ruu and whether thats going to fix it or if it's simply a hardware issue
Sent from my ADR6300 using XDA Premium App
I have it too. Can you boot your phone up like normal after a little while? Everyone else on this forum who gets this can't do jack with their phone. I can boot up fine afterwards, it's just extremely annoying.
It's a code for some kind of hardware failure and they all had to get a new phone. I've been told a RUU may fix everything, but that's a semi-long process for someone as ADD as me to go through. You could try it though. And if you do, shoot me a PM with the results.
Yeah that's exactly what mine does, It'll boot right away and I usually only run into the issue when I'm playing a game for more than five minutes or using my phone in a warm environment. It seems to hit 100° F and then stops itself from overheating.
I was really hoping to not have to Ruu, because its such a process and I don't want to lose the gingerbread keyboard. Maybe someone else will chime in with another idea.
Sent from my ADR6300 using XDA Premium App
So far you and I are the only 2 I know about in the internet who can still boot up like normal afterwards.
I wiped dalvik last night and I haven't had the issue today, you might give that a try. It can't hurt.
-CM7 ADR6300
Ill try that today. I initially thought it was the battery overheating but it did it with the stock 1300 and its doing it with the evo battery I'm using now. Ill finish setting up adb and try the ruu next week when I get time.
Sent from my ADR6300 using XDA Premium App
This just in, rebooted while playing star wars podracing on n64oid.
I think it is a heat issue, cuz my phone is always pretty warm when it happens.
-CM7 ADR6300
I've read about this in a lot of forums lately. But it seems like it only comes up with cm7. You guys sure its not rom related?
Sent from my ADR6300 using XDA App
Also had it on OMFGB, though not as frequently.
Also, today I've noticed my haptic feedback has been... varied in vibration intensity.
-CM7 ADR6300
thisisshep said:
Ill try that today. I initially thought it was the battery overheating but it did it with the stock 1300 and its doing it with the evo battery I'm using now. Ill finish setting up adb and try the ruu next week when I get time.
Sent from my ADR6300 using XDA Premium App
Click to expand...
Click to collapse
I have an Ruu that you just place on the root of your SD and flash through hboot no adb needed if you want it pm me..... and ill give you the file and instructions
Sent from my Incredible using XDA App
Well I broke down tried the RUU and that went through fine but I cant seem to replicate the error with stock. I tried gaming for about 20 minutes and it didnt do it yet, normally it does it after like 5
Good to know.
Have you gone back to CM7 and seen if it helps out there?
-CM7 ADR6300
No I havent tried rerooting yet and reinstalling cm7 It keeps doing it only now it gets stuck in a boot loop instead of doing the five vibration thing then it boot loops about 3-5 times till it cools itself down then restarts normally like nothing ever happened
I already talked to verizon and the new ones in the mail so theres really no sense messing with it anymore now i just need to decide if i want to root the next phone or not
That's what's happening to mine now, too... I also couldn't root it? Unrevoked kept failing. Oh well. I'm selling it and migrating to a Thunderbolt.
Sent from my ADR6300 using XDA App
thisisshep said:
So lately I've been getting the 5 vibration code and I've been searching around here and on other forums and no one seems to know what causes it. Has anyone else that's been experiencing this noticed that it seems to go away after a battery pull and then letting the phone cool down? I'm rooted with unrevoked running cm7 rc2 with Chad's newest kernel right now and tried running cm7 with the included kernel and experienced the same issue.
My main concern is whether to ruu and whether thats going to fix it or if it's simply a hardware issue
Sent from my ADR6300 using XDA Premium App
Click to expand...
Click to collapse
What version of ClockWorkMod are you running? I read some problems with flashing CM7 caused by CWM 3.0.0.8 that was fixed by going to 3.0.0.7
dpwhitty11 said:
That's what's happening to mine now, too... I also couldn't root it? Unrevoked kept failing. Oh well. I'm selling it and migrating to a Thunderbolt.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Nice, I hope the person who buys it informed.....id be f ing pissed
Sent from my ADR6300 using XDA App
pete_kowalski83 said:
Nice, I hope the person who buys it informed.....id be f ing pissed
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Yeah, you've got that right !!!!
When it happened to me I couldn't do a damn thing except get into clockwork Mod, which didn't help because I couldn't access the sdcard. I called up verizon and got a new one. For the two of you that actually have a working phone after this is your phone S-ON or S-OFF?
thisisshep said:
It seems to hit 100° F and then stops itself from overheating.
Click to expand...
Click to collapse
100F is nothing for these processors. Think about it, your body is 98F and a processor is meant to handle a lot more heat than your body. I know the TI OMAP in the original droid had a failure point of 220F.
silverxbv2 said:
I've read about this in a lot of forums lately. But it seems like it only comes up with cm7. You guys sure its not rom related?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Nope, not rom related since it happened to me when I was using Incredibly Re-Engineered v2.3 and flashing a custom kernel when it happened.
Mine remained rooted ans s-off throughout the issue.
I unrooted and applied s-on and reverted to the November RUU and it fixed everything.
Rerooted and reapplied s-off a few hours ago and flashed Virtuous. No more CM7 for me. That's when I started having issues.
Mine does the same thing. Vibrates once, turns off, vibrates 5 times and the LED blinks green. I think mine is related to an overheating issue. Mine reboots almost always when im plugged into the car charger, talking on the phone over bluetooth on my way to work. About a 35-45 minute commute. Even when plugged in at home, and while messing with the settings as well. The only thing that is almost always the same is the screen brightness. Thats when it gets super warm and then turns off. I'll try it out with the screen brightness settings to lower then usual. But when I let it cool off, like I do in the car in front of the A/C vent for about 30 seconds,, with the battery out of the device, it comes right back on no problems.
Mine was rooted and s off. I believe I installed cm7 using clockwork 3.0.0.7 then upgraded to 8 and still had the issue. I know 100°f is nothing for a processor but it seemed to have issues as soon as it got around 110 then if you let it sit it works again so that's what led me to thinking it was a heat issue even though it doesn't make much sense
Sent from my ADR6300 using XDA Premium App
I woke up and my phone (running bonestock) had a android guy and a weird symbol. Anyway I pulled the battery and reboooted and when it was done it said shutting off...... It rebooted and a loading bar got 1/3 full befor the android thing showed again?
Did my phone try to update but the update failed becuase I was rooted? If so, was it the latest gingerbread, or mabey even ICS.
Sent from my Incredible 2 3D using xda app-developers app
i just checked my gfs phone she was previously rooted but returned to stock. the updater didnt find any new otas
More than likely the latest gb.
Sent from Kangdemnation
My girlfriend's phone tried to update last night too. She is running the newest andybonestock rom. I cancelled the download. Just sharing the info.
Sent from my ICS Dinc2
cstone1991 said:
My girlfriend's phone tried to update last night too. She is running the newest andybonestock rom. I cancelled the download. Just sharing the info.
Sent from my ICS Dinc2
Click to expand...
Click to collapse
It just froze on me
Sent from my Incredible 2 using xda app-developers app
When ICS finally drops do you really think its gonna be a surprise? Every phone that has received an update recently has had the news leaked at least a week before it dropped. All this hoping is a waste of time. It will get here when it gets here.
Sent from my Incredible 2 using xda app-developers app
okay i finally found a link and was able to flash if anyone is interested...
from numerous attempts before; this is how i was able to flash
1 - Mobile odin el26cwm
2 - Factory Data/Reset
3 - Wipe Cache
4 - Wipe Davlik-cache (under advance)
5 - Format system (under mounts and storage)
6 - Install update-cm-7.2.0-RC6-epic4gtouch-KANG-signed.zip
7 - Install gapps-gb-20110828-signed.zip
8 - Reboot
Setup files needed:
ROM - http://minus.com/lidQKBHor76kG
GAPPS - http://cmw.22aaf3.com/gapps/gapps-gb-20110828-signed.zip
Original Thread and dedication - http://rootzwiki.com/topic/12440-ro...ha-6-1-15-2012-i-cant-believe-its-not-butter/
Sorry we don't have a fully stable cm7. Nor a current non stable build of cm7.
we dont have a fully stable anything really ? but without being a smartass cuss i didnt mean it haha, can u hand me a link or is it dead and gone ? i thought i found one but it didnt boot stuck at splashscreen
http://rootzwiki.com/topic/12440-ro...2-i-cant-believe-its-not-butter/page__st__710
That is the closest thing to CM7 that has been released publicly for this phone. I'm not sure about all the issues but I kno for a fact that 4G doesn't work with it. I think a this point you would probably be better off with CM9 or maybe even CM10.
I tried building CM7 for this phone and there was some issues that I didn't feel like it should be released. The ROM itself was smooth, but it was far from a daily driver.
As far as I know times_infinity has also built CM7 with the same issues I was experiencing. Using the kernel bubby hacked together was a nightmare. If it happens, we need a new kernel.
I will eventually get back around to working on it again.
Sent from my SPH-D710 using xda premium
Mattix724 said:
I tried building CM7 for this phone and there was some issues that I didn't feel like it should be released. The ROM itself was smooth, but it was far from a daily driver.
As far as I know times_infinity has also built CM7 with the same issues I was experiencing. Using the kernel bubby hacked together was a nightmare. If it happens, we need a new kernel.
I will eventually get back around to working on it again.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
yeah that rom wouldnt boot 8^(
Along the same lines, what happened to cm9? Why is the thread closed if nightlies are still happening according to the website?
Sent from my SPH-D710 using xda app-developers app
Lonbobby said:
Along the same lines, what happened to cm9? Why is the thread closed if nightlies are still happening according to the website?
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Darchstars CM9 thread was closed because he is no longer working on our device. Check again in original development.
Sent from my Nexus 7 using Tapatalk 2
Chris and team epic have a beta 1 in original development. Nightlies are at goo.im/devs/shabbypenguin
Experimental builds done multiple times in a day sometimes are at goo.im/devs/chris41g/cm
sent from my BAD A$$ Epic touch
bump for updated op
for alot of people getting blue screen during first boot and have to battery pull and roll back to 22nd, just warning
my phone still getting blue screen on 26th nightly too
KronicSkillz said:
my phone still getting blue screen on 26th nightly too
Click to expand...
Click to collapse
Are you trying to flash this on Windows or something? Android doesn't have blue screens. Lol.
In all seriousness though, try different kernels. Not all phones are created equal.
rani9990 said:
Are you trying to flash this on Windows or something? Android doesn't have blue screens. Lol.
In all seriousness though, try different kernels. Not all phones are created equal.
Click to expand...
Click to collapse
You didn't try it yourself did you? Well it doesn't even work with the built-in CM Kernel. Even tried a full wipe - to no avail. We'll have to wait for more stable ones. :fingers-crossed:
rani9990 said:
Are you trying to flash this on Windows or something? Android doesn't have blue screens. Lol.
In all seriousness though, try different kernels. Not all phones are created equal.
Click to expand...
Click to collapse
what is with the assumptions, all i did was update run the updater with 26th update and it blue screened after lg logo, so YES IT DOES HAVE BLUE SCREENS... take the idiotic attitude somewhere else when ur the one whos wrong
this is a widespread problem if u knew everything like you act like you do you would have already known that
Geezus, I was kidding. I forgot how unfriendly you guys were....
Sent from my Nexus 7 using Tapatalk 2
rani9990 said:
Geezus, I was kidding. I forgot how unfriendly you guys were....
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
You people..? What do you mean, You people..?
Sent from my LG-P930 using Tapatalk 2
has anyone tried the daily from today yet?
edit -
since no one else is talking i tried flashing 27th nightly and still BSOD upon first boot, confirmed the CM mods are finally aware of the issue, itll probably be fixed for tomorow.
Same problem for 27/05
Sent from my LG-P930 using xda app-developers app
ultimate_neet said:
Same problem for 27/05
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
yes I Still get the same problem
the 28th nightly is currently downloading it should be fixed today but ill post after i have it installed to verify.
the nightlies from today have fixed the BSOD on firstboot. confirmed.
YUP, it's fixed. But i have some problem installing the WIND Kernel, does someone knows something about it?
same here i reflashed to nightly from today to go back to stock kernel until its fixed