Related
Not sure what they did on this thing. I thought 2.1 was supposed to IMPROVE performance...and add some BT functionality.
I got no BT improvement. Instead, I got:
1. Random reboots
2. Slow/crashing Navigation
3. Useless voice recognition on Navigation
4. Random phone calls placed when fiddling with BT
5. Slow opening notifications
6. WIFI won't turn on
I could go on and on...
Sprint says I can't go back to 1.5, but I'm sure there's a way to do it.
HELP PLEASE! I'm rooted, if that helps.
Greg
theres noway. your H-Boot has been updated. thats the end of it. 1.5 just wont work anymore.
Sent from my Hero CDMA using the XDA mobile application powered by Tapatalk
troublestylist said:
HELP PLEASE! I'm rooted, if that helps.
Click to expand...
Click to collapse
Yes it does. Just find a 1.5 ROM for CDMA hero. However, before most of our devs moved on to the EVO almost all of them stop developing 1.5 and moved to 2.1
I would suggest trying out some 2.1 ROMs and see what you like.
If you are rooted you should have put a recovery on your phone that you can get to by pressing home and turning on your phone. The first thing you will want to do is make a nandroid backup in case you don't like things. Then stick a ROM on your sdcard. Select all the wipe options except for battery and rotate and then flash a new ROM.
Id try wiping and reloading a 2.1 rom. I never had any of those problems when I went to 2.1.
I'm running the latest DamageControl and can honestly say I am not having any of those issues. I say you should try using a different ROM.
centran said:
Yes it does. Just find a 1.5 ROM for CDMA hero. However, before most of our devs moved on to the EVO almost all of them stop developing 1.5 and moved to 2.1
I would suggest trying out some 2.1 ROMs and see what you like.
If you are rooted you should have put a recovery on your phone that you can get to by pressing home and turning on your phone. The first thing you will want to do is make a nandroid backup in case you don't like things. Then stick a ROM on your sdcard. Select all the wipe options except for battery and rotate and then flash a new ROM.
Click to expand...
Click to collapse
I didn't root until I got 2.1, so I surmise the 1.5 is gone, right?
derekwilkinson said:
I'm running the latest DamageControl and can honestly say I am not having any of those issues. I say you should try using a different ROM.
Click to expand...
Click to collapse
RegawMOD was also recommended. Any reason why to pick one or the other?
Thanks for all the help. Sad that unpaid and unsupported independent developers can do this job better than HTC.
In a best case world, I'd be able to get ad hoc networking to work. I followed the directions but didn't have any success. My ultimate goal was to enable my Hero to display photos wirelessly from my computer. Many programs do it the other way around.
Originally I thought BT would be the easiest wireless protocol, but it seems pretty weak for that sort of data transfer. So 802.11 seemed a better solution...but for some reason Android folks decided to cripple the OS from recognizing ad hoc networks. Odd.
troublestylist said:
I didn't root until I got 2.1, so I surmise the 1.5 is gone, right?
Click to expand...
Click to collapse
You can still flash 1.5 ROMs. You just can't flash the 1.5 RUU.
Great...
Tried Damagecontrol 2.09, did a clean wiped install, and everything seemed fine. Didn't seem much faster, but whatever.
Too bad I waited until I was at work to reboot. Now it's in a bootloop, and I'm stuck at work with no phone.
Sprint sent me a new phone. Once I confirm it's got 1.5, they can have this 2.1-infected POS back.
troublestylist said:
Tried Damagecontrol 2.09, did a clean wiped install, and everything seemed fine. Didn't seem much faster, but whatever.
Too bad I waited until I was at work to reboot. Now it's in a bootloop, and I'm stuck at work with no phone.
Sprint sent me a new phone. Once I confirm it's got 1.5, they can have this 2.1-infected POS back.
Click to expand...
Click to collapse
Look... there's a good chance your new Hero WILL have 2.1 on it. If it does, just root it and install a custom 1.5 rom.
troublestylist said:
Tried Damagecontrol 2.09, did a clean wiped install, and everything seemed fine. Didn't seem much faster, but whatever.
Too bad I waited until I was at work to reboot. Now it's in a bootloop, and I'm stuck at work with no phone.
Click to expand...
Click to collapse
This might mean you simply didn't wipe everything before you flashed the new ROM. Always perform a full wipe before flashing new ROMs.
Take the battery out of your phone. Put it back in and reboot to Recovery (hold Home and press Power). Then select the Wipe option, and go down that list and wipe every single category (I do them each twice just to make sure).
Then go back to the main menu and flash the ROM again. That should probably solve any bootloop problems.
(I don't know if it works exactly this same way with the rooted 2.1 RUU [I'm still on rooted 1.5], so if any of the above is wrong, anybody please correct it...)
HeroMeng said:
Look... there's a good chance your new Hero WILL have 2.1 on it. If it does, just root it and install a custom 1.5 rom.
Click to expand...
Click to collapse
Yeah, I was thinking about that. If so, I might as well keep MY phone and install a 1.5 ROM on it. Less work, and they can have their "new" phone back.
chromiumleaf said:
This might mean you simply didn't wipe everything before you flashed the new ROM. Always perform a full wipe before flashing new ROMs.
Take the battery out of your phone. Put it back in and reboot to Recovery (hold Home and press Power). Then select the Wipe option, and go down that list and wipe every single category (I do them each twice just to make sure).
Then go back to the main menu and flash the ROM again. That should probably solve any bootloop problems.
(I don't know if it works exactly this same way with the rooted 2.1 RUU [I'm still on rooted 1.5], so if any of the above is wrong, anybody please correct it...)
Click to expand...
Click to collapse
Wow, so working with this ROM is like dealing with my kids. I have to tell it everything twice No thanks. Not worth the hassles.
2.1 doesn't do anything better that I can see. I'll deal with wired tethering considering how rarely I use it. The Navigation on 1.5 works better, or at least the voice recognition does.
Why exactly are you still using 1.5??? What custom 1.5 ROM would you guys recommend? Any that have ad hoc networking built in so I don't have to hack it myself?
Any that have ad hoc networking built in so I don't have to hack it myself?[/QUOTE]
Pretty sure all of them do.
Sure wish we could get WPA working for us....stupid kernel.
troublestylist said:
Wow, so working with this ROM is like dealing with my kids. I have to tell it everything twice No thanks. Not worth the hassles.
Click to expand...
Click to collapse
You don't have to do them all twice, I was just saying that I do to make sure -- personal preference. Considering how those wipe options only take like 1 second each, there is no "hassle" of which you speak. Adds maybe an extra 4 to 5 seconds to your day at most.
troublestylist said:
Why exactly are you still using 1.5??? What custom 1.5 ROM would you guys recommend? Any that have ad hoc networking built in so I don't have to hack it myself?
Click to expand...
Click to collapse
I'm not still on a 1.5 ROM, I just haven't yet updated my phone to stock 2.1 using the can't-ever-go-back-again 2.1 RUU. What I meant is that I still have the 1.5 root, but I have been using 2.1 ROMs over top of that for at least a couple months now. I think all these 2.1 ROMs are much faster than 1.5 ever was. Slow speed and lag were my biggest annoyances in stock 1.5.
We probably won't be able to answer all your questions or remove all your doubts. You won't know completely until you try some of them yourself.
If you look in the Wiki there are several 1.5 Roms out there that you can use. However, there are some apps that will only work with 2.1. Once your rooted you can flash any ROM from 1.5 or 2.1. You might also consider an AOSP rom which doesn't have Sense UI. But as I stated in another thread yesterday, most people end up adding apps to try and emulate certain characteristics of Sense UI. I don't like vanilla android, but it is supposed to be faster.
Here are all of the ROMs available. If you want a 1.5 Rom I would suggest Gumbo 1.5c, Modaco 2.2, or Fresh 1.1.
Thanks all. I honestly can't imagine how anyone could find 2.1 faster than 1.5, but I guess maybe once I'll reload 1.5, it may remind me. The "other half" of the people are (like me) saying the CPU can't handle the extra 2.1 features.
I never found 1.5 slow for anything other than phone calls. Now, those are WORSE, and the lag time to do anything else now exists, where it didn't before.
I ran DC all day, and it was just as annoying as the stock ROM. Maybe a little better in places, worse in others.
I guess I'm running "basic" stuff compared to all you guys running heavy apps or something.
Pancake 1.5 running now...refreshingly smoothly Yea, a bit of the glitz is gone, but wow, no lag.
And I have a Navigation program back that has a functional voice recognition. I hesitate to update because I'm not sure how far the revs go under 1.5. I don't want the new version back and I don't know if it's 2.1-only.
Hello all,
Been rambling around the forums in ninja mode trying to gain enough knowledge to not mess up my phone before trying to mod it but alas best laid plans....
Anyhoo I was working to put the Froyo leak on my phone and everything was good till I did a cwm wipe of the phone and wammo it had problems. I managed to use Odin to get it back to barebones stock, lost my high score in Angry Birds too dang it.
Now that I am back to this point I tried to run the Verizin updates and it downloads and goes into install mode on reboot and it dies at Updating Modem section. At that point I saw I was rooted so I removed that and tried again, no dice amigo. Did a factory wipe, nothing. Cleared the cache, fail again.
If it helps its trying to do a dh12 to di01 update. Got any ideas?
When you went to stock did you flash the stock kernel and stock recovery as well? I had to do this when I updated to dl09
Good question and yes I believe I did, I followed this: http://forum.xda-developers.com/showthread.php?t=782204&highlight=return+stock thread to get the job done. Let me try it one more time.
Also I load the PIT file with each md5 correct?
Looks like I fixed it on the second time around. Not sure what I missed but the update went through. No worries. Might pay someone to hand hold my through getting DL30 on my phone cause even as an IT guy I'm missing something every time.
Strong thing is, once the DI01 update happens it actually doesn't find any other updates...wifi is off.
VZW pulled the DL09 update due to the e911 bug until it is fixed
Makes good sense. Sooo anyone wanna tutorialize me on how to de-crappify my phone? Its worth a donation from me.
You're on di01 right?
I would odin the dl09 package, then use cwm to flash super clean 2.2. Clean, debloated froyo goodness
Sent from my SCH-I500 using XDA App
Sounds good. The problem lies in me somehow fudging up the process at some point and having to set my phone back to stock again.
Where did you see this?
"VZW pulled the DL09 update due to the e911 bug until it is fixed"
Have any sources on this one? I really would like to see them.
Not doubting you, I have just been rebooting and *228 for 3 days trying to get this update only to see this quote...
VZW sent a message to all Fascinate owners the other night acknowledging the bug and a fix being in the works. Why would they continue to push it out after that?
Sent from my SCH-I500 using XDA App
Well...
0123456789
New EA update is being pushed out.
Verizon told me to go to a store as some phones will not accept OTA updates. Seems stupid and like a lie, but whatever...
Atst44 said:
"VZW pulled the DL09 update due to the e911 bug until it is fixed"
Have any sources on this one? I really would like to see them.
Not doubting you, I have just been rebooting and *228 for 3 days trying to get this update only to see this quote...
Click to expand...
Click to collapse
He's right. Google the source if you need it. Please don't take this response as me being snarky, I don't mean it that way.
I think the biggest issue people are having is not being careful and following the directions perfectly.
I was new two days ago and did this with only one hiccup.
1. I followed the Beginner's thread in this forum to get me rooted. First pass with Odin failed as the one click code didn't recognize the phone. 2nd pas worked. Trick was to just turn on USB debugging and plug in phone, do not then click the mount notification. Leave that off as USB debugging was all that was needed.
2. I installed Mod Manager and Titanium backup right after. This was part of the main directions and Titanium (though not mentioned) allowed me to save all my specific apps that had important data, like my 100% completed Angry Birds.
3. I then followed the directions in the developer forum for the How To.. install DL30 for Froyo. This scared me at first because the CW recovery stalled when wiping data. I waited over 30 minutes before getting the courage to pull the battery and start over. Figured its only deleting user data, should be ok. It was and then it worked the 2nd time without fail. I did reboot in normal recovery, but running the update.zip put it back into CW.
4. After that, I rebooted numerous times, checked all stock apps, upgraded firmware in camera, and used Titanium to add back my apps I bought or downloaded as well as restored my bookmarks and memo notes.
In the end I've had no bugs/issues as others have reported. Only functionality not tested is bluetooth as I don't use it for anything.
I hope this helps and if you are walking through it all again, I would be glad to help specific questions based on my experience.
I was DL09 stock OTA at first. I'd recommend getting rooted and using Odin to get the stock DL09 from these forums flashed before you try to put DL30 on. As a developer myself, it just makes sense to always put on builds that are in order of each other. So DI01, then DL09, then DL30.
0123456789
superchunkwii, thanks for the feedback. When I booted into cwm recovery mode it hung too. I think my fatal mistake was I booted in regular recovery mode and did my wipe....sad. I should have just rebooted and went back in cwm like you did.
As far as freezing apps I did not know freezing angry birds would save its data. Boy was my wife is mad (she plays it the most).
I did everything else on cue so I will try again and see how she goes. IT CAN BE TAUGHT! As the genie says.
On another note I did download the EA28 update today, can I install the DL30 Rom or do I need to "downgrade" to DL09 to get this done? Anyone try?
dlmcclou said:
superchunkwii, thanks for the feedback. When I booted into cwm recovery mode it hung too. I think my fatal mistake was I booted in regular recovery mode and did my wipe....sad. I should have just rebooted and went back in cwm like you did.
As far as freezing apps I did not know freezing angry birds would save its data. Boy was my wife is mad (she plays it the most).
I did everything else on cue so I will try again and see how she goes. IT CAN BE TAUGHT! As the genie says.
On another note I did download the EA28 update today, can I install the DL30 Rom or do I need to "downgrade" to DL09 to get this done? Anyone try?
Click to expand...
Click to collapse
1. Not freeze.. that makes it so app won't run. Backup with Titanium Backup is what you need I think.
2. What is EA28? I don't think the fascinate has had that build.
Just got an update EA28 any ideas what it does
Sent from my SCH-I500 using XDA App
EA28 build is the update to fix the emrgency dialing bug in DL09. As I understand, it is otherwise the same as DL09. I am by no means an expert though.
EA28 build is the update to fix the emrgency dialing bug in DL09. As I understand, it is otherwise the same as DL09. I am by no means an expert though.
Click to expand...
Click to collapse
Cool. Can anyone confirm this?
Alright, this issue has seriously driven me insane over the last few days, and today it's gotten to the point where I'm going to do something I'll regret if somebody can't help me out. As you can tell, I'm pretty desperate.
Using Fresh 3.5.0.1, I've encountered more reboots than I can count. Whether it's checking an email or playing Asphalt, the phone frequently decides it doesn't want to cooperate and restarts itself. I decided to try to get rid of the reboots for good today with a complete wipe and new rom.
First, I made a nandroid backup, followed by a data/system wipe and cache/dalvik cache wipe. Afterward, I flashed the ZenDroid 1.1.0 kernel in case that was the issue. I then proceeded to flash CyanogenMod 7 RC1 with gapps.
That worked for all of three minutes, and then it got even worse. The phone started restarted itself when I wasn't even doing anything, up to the point where it would restart on the CM7 boot animation. I took my rage out on a nearby pillow and decided to try something else.
I downloaded the final release MIUI rom and used Calkulin's format all to wipe my phone as instructed. This time around I flashed Savage-Kernel 1.6 along with MIUI. Lo and behold, after rebooting I was finally able to swipe through the home screens again.
And then I wasn't. It started rebooting on the boot animation again. At the moment it's even worse, rebooting three seconds into the damned splash screen. I've tried keeping the battery pulled for half an hour with the HTC battery and two after market batteries. I wiped the ext partition on the micro sd card. I even physically removed the card itself. This effing phone is still rebooting on the splash screen.
I'm at the end of my wits. All I want is for my Evo to WORK, without any constant reboots or force closes that make it utterly unusable outside. If anyone could help me out with this issue, I'd be extraordinarily grateful.
Mecha2142 said:
Alright, this issue has seriously driven me insane over the last few days, and today it's gotten to the point where I'm going to do something I'll regret if somebody can't help me out. As you can tell, I'm pretty desperate.
Using Fresh 3.5.0.1, I've encountered more reboots than I can count. Whether it's checking an email or playing Asphalt, the phone frequently decides it doesn't want to cooperate and restarts itself. I decided to try to get rid of the reboots for good today with a complete wipe and new rom.
First, I made a nandroid backup, followed by a data/system wipe and cache/dalvik cache wipe. Afterward, I flashed the ZenDroid 1.1.0 kernel in case that was the issue. I then proceeded to flash CyanogenMod 7 RC1 with gapps.
That worked for all of three minutes, and then it got even worse. The phone started restarted itself when I wasn't even doing anything, up to the point where it would restart on the CM7 boot animation. I took my rage out on a nearby pillow and decided to try something else.
I downloaded the final release MIUI rom and used Calkulin's format all to wipe my phone as instructed. This time around I flashed Savage-Kernel 1.6 along with MIUI. Lo and behold, after rebooting I was finally able to swipe through the home screens again.
And then I wasn't. It started rebooting on the boot animation again. At the moment it's even worse, rebooting three seconds into the damned splash screen. I've tried keeping the battery pulled for half an hour with the HTC battery and two after market batteries. I wiped the ext partition on the micro sd card. I even physically removed the card itself. This effing phone is still rebooting on the splash screen.
I'm at the end of my wits. All I want is for my Evo to WORK, without any constant reboots or force closes that make it utterly unusable outside. If anyone could help me out with this issue, I'd be extraordinarily grateful.
Click to expand...
Click to collapse
hmm...
i don't know what kernel fresh comes with, but both of the other kernels are more aggressive ones, and i would guess your phone doesn't like them. i would try this:
Wipe twice using calk, wipe again using recovery, flash mikfroyo or stock rooted (stock kernel). If you still get reboots... unroot and take your phone back in because its a hardware problem.
I had this problem. Drove me insane. Ultimately just unrooted and got a new one from sprint. Not one reboot since I got the new one.
Sent from my PC36100 using XDA App
Well I'm still super new to the whole flashing of the ROM's. But from what you have explained the only thing I can think of is that you missed a step when you rooted your phone. Because of this that is why your phone keeps brick. You should go and check out HTC EVO Hacks (go Google it) and the guy who runs the site made a sweet video & write-up on how to root your phone. Just re-do everything and follow directions, then when your done just flash Kings Unleashed. And when you check out the HTC EVO hacks root page look for the link to the XDA root forum which has more info on how to root your HTC the proper way.
Sent from my PC36100 using XDA App
aimbdd said:
hmm...
Wipe twice using calk, wipe again using recovery, flash mikfroyo or stock rooted (stock kernel). If you still get reboots... unroot and take your phone back in because its a hardware problem.
Click to expand...
Click to collapse
Yeah, I guess I should try the stock rooted rom. If I'm only able to use that instead of any other custom rom, though, I'm going to lose it. There's something inherently frustrating about a device refusing to work for no apparent reason.
chickut123 said:
I had this problem. Drove me insane. Ultimately just unrooted and got a new one from sprint. Not one reboot since I got the new one.
Click to expand...
Click to collapse
I'm sort of hoping I won't have to do that, considering I'll likely get a refurbished unit.
Fredrow425 said:
But from what you have explained the only thing I can think of is that you missed a step when you rooted your phone. Because of this that is why your phone keeps brick. You should go and check out HTC EVO Hacks (go Google it) and the guy who runs the site made a sweet video & write-up on how to root your phone. Just re-do everything and follow directions, then when your done just flash Kings Unleashed. And when you check out the HTC EVO hacks root page look for the link to the XDA root forum which has more info on how to root your HTC the proper way.
Click to expand...
Click to collapse
I'm pretty sure that isn't the case at all. If there was an issue with the way I rooted my phone, it would have been present eight months ago when I bought it. This rebooting issue is relatively new, and it isn't bricked. I appreciate the advice, though.
It could be just a defective phone - memory isn't immortal or impervious to defects.
I'd downgrade to a Sprint ROM, and keep it stock and see how that works. You have to rule out bad hardware first, and that's the only way to do it.
I agree on all of your guys suggestions but one thing i noticed was that he said he wiped data then dalvic cache then he said he flashed the kernel then the rom. Maybe he should try and rewipe everything with calk format all then flash the rom and reboot. Then go back into recovery and flash your new kernel then reboot again and see whats up from there.
Have you tried repartitioning your SD card and formatting? I was getting random reboots on every single rom I tried, and every single kernel. Turns out my partitions somehow got messed up on my SD card and that was causing it randomly. Now I have no reboots.
akrod2as said:
Have you tried repartitioning your SD card and formatting? I was getting random reboots on every single rom I tried, and every single kernel. Turns out my partitions somehow got messed up on my SD card and that was causing it randomly. Now I have no reboots.
Click to expand...
Click to collapse
Yes, I first formatted the sd card in Windows and then partitioning it on the phone's recovery. Still no luck.
Yeah... Sprint rom or if you go through with the unrooting process (I forgot how...) then you can figure out if it is hardware.
But yeah, endless reboots are frustrating.
If Sprint rom is giving you troubles, then just return it and get a new one. It's gotta be hardware then.
Also you could try running stock rooted without any downloaded market apps. Just run what came with the phone.
You can also try stock rooted eclair 2.1
Mine started the reboot bs after the december update. Mine seems to reboot when I use it heavily even though I'm not overclocked (heats up). Before the 2.2 update, it was very fussy being outside during the summer. I would like to exchange mine for another, even though I don't use it anymore. It would be nice to have a fully functioning backup. My gf's daughter wants the evo very much. Even if I would do that, which I wouldn't, I wouldn't let someone use a possibly unstable phone. If an emergency happened, and the phone started it's rebooting bs, it would be very bad to not be able to use the phone when you need it the most.
I am guessing I would have to reactivate the evo, run it for a month or so, unroot and lock it, then take it to a service center and see if I can make it start rebooting like crazy. Maybe I will get lucky and they would give me another one. I don't care too much if it is a refurb as long as it is in good shape and works good.
Try removing the SD card and booting.
Sent from my PC36100 using XDA App
rebooting
I had this same problem with my evo. Sometimes it would be ok, but then others it wouldnt stop doing it, didnt matter what I did. It could be sitting by itself and I would hear it rebooting. Drove me mad!!!
My first evo was awesome, it was a hardware ver 3. My camera lens cracked and the gave me a refurb, hardware version 2. This is when my reboots started happening.
After 3 batteries from Sprint and two more refurbs I finally blew in front of a store full of customers telling them that either give me a NEW evo, hardware version 3 like I originally had with no problems or it was going against their wall.
I havent had one problem since.
I wasnt rooted yet so cant comment along those lines but if you take it back to stock and it still does it I recommend throwing it at one of Sprints walls. No need to do any drywall patching at your place LOL.
I hope you get it resolved as I can feel your pain!
It may not be hardware. Did you restore any apps using any back up app (Titanium Backup) after flashing the AOSP roms? If so, make sure you did NOT restore any system apps or data. This is especially important when you go from Sense to AOSP.
The test is what everyone is suggesting. Flash back to Sprint rom and see what happens.
Also, you need to flash the kernel after flashing the rom, otherwise you'll just get the kernel packaged with the rom. I usually reboot and art least try the default kernel unless I know that my phone hates it.
bigmoogle said:
It may not be hardware. Did you restore any apps using any back up app (Titanium Backup) after flashing the AOSP roms? If so, make sure you did NOT restore any system apps or data. This is especially important when you go from Sense to AOSP.
The test is what everyone is suggesting. Flash back to Sprint rom and see what happens.
Also, you need to flash the kernel after flashing the rom, otherwise you'll just get the kernel packaged with the rom. I usually reboot and art least try the default kernel unless I know that my phone hates it.
Click to expand...
Click to collapse
No, I haven't even been able to get to the stage of installing any apps before the rebooting cycle starts again. I tried installing the stock Sprint rom this morning with the stock radios and kernel and it was stable for about five minutes. It's back to rebooting again, though.
Do you guys think it's time to unroot and go to the Sprint store for an exchange?
Mecha2142 said:
No, I haven't even been able to get to the stage of installing any apps before the rebooting cycle starts again. I tried installing the stock Sprint rom this morning with the stock radios and kernel and it was stable for about five minutes. It's back to rebooting again, though.
Do you guys think it's time to unroot and go to the Sprint store for an exchange?
Click to expand...
Click to collapse
If it was me, I would take it back. I just downloaded the newest ruu and will flash it later tonight. The only thing I'm worrying about is they won't be able to reproduce the problem. I really have to be multitasking a lot and pushing the phone hard. Actually the last time it had rebooting fits was with wireless tether running. The back of the phone was warm. I put it in front of the ac vent in the car for a minute or two and that seemed to help it stop rebooting.
herbthehammer said:
If it was me, I would take it back. I just downloaded the newest ruu and will flash it later tonight. The only thing I'm worrying about is they won't be able to reproduce the problem. I really have to be multitasking a lot and pushing the phone hard. Actually the last time it had rebooting fits was with wireless tether running. The back of the phone was warm. I put it in front of the ac vent in the car for a minute or two and that seemed to help it stop rebooting.
Click to expand...
Click to collapse
Well, it looks like I'll be taking it to the store after all. I just finished unrooting my phone with the RUU, so it's as if I had never touched the software. Lo and behold, the damned thing still rebooted a minute into using the phone.
I guess that in some sick way, I can consider myself more 'fortunate' than you, seeing as how my phone doesn't even need to be used in order to begin rebooting. It's ridiculous that I have to part with my Evo because of this bs.
Mecha2142 said:
Well, it looks like I'll be taking it to the store after all. I just finished unrooting my phone with the RUU, so it's as if I had never touched the software. Lo and behold, the damned thing still rebooted a minute into using the phone.
I guess that in some sick way, I can consider myself more 'fortunate' than you, seeing as how my phone doesn't even need to be used in order to begin rebooting. It's ridiculous that I have to part with my Evo because of this bs.
Click to expand...
Click to collapse
Did you even try removing the sd card and booting the phone?
Same thing happend with my old evo it started after i install one of the first cm safe roms not nightlies not saying tyat was the cause, i tried evverything wiping unrooting botting without sd, ive been on android sice g1 and i tried everything nothing worked, ended up going to sprint and getting another refurnished it was prolly hardware issue maybe cpu overheating or something, anyways not sure why ppl are so scared of refurnished phones i believe they do a lot more tests on those phone than retail ones lol
akrod2as said:
Did you even try removing the sd card and booting the phone?
Click to expand...
Click to collapse
Yes. I've already said I tried booting the phone without the sd card several times now without success.
Hey I would have posted this on a different thread but i cant because i just made this account they want atleast 10 posts...
heres the deal... i have a rooted evo and running cm7 which i like, but i was dropping calls and where i live i should have good service. so i got the updated radio/wifi/ ect package and flashed it... it installed but did not help with the call issue... i heard many other having the same problem.
so i flashed the ota root update... which seemed like it did it really fast (wasnt watching the whole time) and the phone rebooted but gets stuck at the white htc evo screen, i let it sit there for 20 mins nothing, so right now i am recovering my old cm7... just wondering if anyone has that same problem or can help with getting better voice reception on cm7.. like i said i have tried the package for radio ect... and my prl was updated before i flashed to stable of cm7 so that should be in good standing i would imagine... thanks..
The obvious first question is, did you do a full and complete wipe of everything before you flashed the ROM?
As far as your signal, it may have been just in my area, but I know a few people that had problems texting and making calls, getting a "Network Is busy" error.
yea i did the wipe data/cache i wasnt dropping calls before the cm7 so im not sure right now im shootin to myns seeing how that is... cm7 was first flash i did
well as im trying to flash to the myns its looking like the samething... ill go through the steps...
have zip file in root of sd card
open up rom manager, have the newest clockwork thing installed
i goto flash from sd wipe data and cache are checked... i already have a backup so i skip that part
it installs.... says install is done and reboots itself... but seems to stay on that white bootscreen
if i take the battery out then i can reboot with recovery from the save file i have
blah i dont know... i got the ota installed... looked like it got a bit better reception.. i updated prl and came back to cm7 same probs... i dunno maybe ill just have to let go of cm7... really dont want to though its so sexy lol
I had the same weak signal issue with cm7 and had dropped calls and data dropping to 1x. I am on stock rooted 2.3.3 and reception is good again. Liked cm7 but need a phone I can use in the boonies.
Sent from my PC36100 using XDA Premium App
Dude, please, don't use ROM Manger.
Just boot to recovery, hopefully, you have Amon Ra, if not, search how to get it on your phone, it's not hard, do a FULL WIPE, full, wipe everything in recovery, then flash the ROM in recovery.
No offense to the Dev, I know he's a great guy, a smart guy, hard worker that makes a contribution, but Rom Manager is not the best way to do this.
Yea had to do it manually but nymph works now liking it so far
ok now i have different problem.... got the myn working liking it, but my market is completely different, not just the theme, but the apps i usually download... so tried to flash new market but it just open/closes quickly... any ideas for that?
Not sure by what you mean by the apps you usually d/l.
One thing about the Market in these newer ROMS is that sometimes, you just need to give it some time to fully sync before all your apps so up...
You should pull the market out of the zip file for the ROM and re-install that one, but you'll have to delete the one you have installed now, first.
umm usually download ninjump cant find that just some games that are usually on my phone the market on cm7 had them... ill give it a try though
look on the android market website
I posted this elsewhere with no replies yet
Im trying to install the newest CM7 on my NC and have spent the last 7 hours trying to diagnose how to get rid of the (android.process.media) unexpectedly stopped working, please try again error message. Nothing works. I've gone through the last few versions of CM7 and the gapps, I followed the instructions to the letter, it installs fine, wireless works,
When it loaded up, there was no google sign in screen, the process android.process.media error appears every few seconds or when i click on certain tabs, there is no backwards button enabled so i have to press the N to start over completely no matter where I go, the droid market works but again that error pops up and doesnt actually download anything, it just hangs on "downloading"
what the hell am i doing wrong and how can it mess up the same way on each version I have tried ? I went back a few versions and tried each one and each had their own crazy problems. What the hell, someone please help me so i dont have to return it
I don't know exactly what you are doing wrong, but I've found that following eyeballers tutorial of flashing cm7 to be pretty much foolproof
http://forum.xda-developers.com/showthread.php?t=1030227
At any rate, make sure that you use a md5sum checker on the downloaded file. Maybe it got corrupted somehow. You never know.
Anyways, don't give up. The nook is awesome.
ive followed that guide, i dont know what else to do
how do i get flash video running?
Are you installing CM7 to a microSD card? I kept having this problem running CM7 from some a-data card, after putting a bunch of images on the nook. Eventually I installed CM7 to emmc and it's been perfect since.
sleepygypsy said:
how do i get flash video running?
Click to expand...
Click to collapse
Install Adobe Flash....
patruns said:
Install Adobe Flash....
Click to expand...
Click to collapse
Did the market fix and it still says its not compatible
sleepygypsy said:
Did the market fix and it still says its not compatible
Click to expand...
Click to collapse
Try again. Follow directions. If it still fails, try a different method. iirc there are a couple of ways to fix this issue.
btw: you might find more success if you approach this with a clear head; judging from your initial post, it might be a good time to take a break, have a snack, etc. good luck.