Hello guys,
I gave my friend my EVO 3D (CDMA, Sprint) a few months ago when I upgraded to a new phone. Ever since she called Sprint to activate the phone (at the time running SOS M 2.6 ROM) she had nothing but problems. She also didn't have the Google Services packet working for some reason (all Google Apps worked fine with me, even thought hangouts was new I didn't use it on the Evo). After a while I tried to install Cyanogen on it and it failed (it won't boot and get stuck on a loop), eventually resorting to Venom, which is what she has now.
The phone is so slow it takes the keyboard 10-15 seconds to respond between button-pressing. Swipe is obviously impossible, and the phone sometimes gets stuck on boot. The whole thing is sluggish as hell. I'm not sure what going on, the phone was perfectly fine, and now after 3 ROM it's a piece of crap.
I am going to have the phone tomorrow again and I have permission to wipe it clean and try again. What I need is a ROM that has 4.0 if possible, but what's more important for me is that the thing would work smoothly. Having the 3D camera would also be nice. What ROMs would you recommend? Something that should work for sure? Anyone else have issues with Hangouts maybe?
Thanks, all suggestions welcome.
beholder121 said:
Hello guys,
I gave my friend my EVO 3D (CDMA, Sprint) a few months ago when I upgraded to a new phone. Ever since she called Sprint to activate the phone (at the time running SOS M 2.6 ROM) she had nothing but problems. She also didn't have the Google Services packet working for some reason (all Google Apps worked fine with me, even thought hangouts was new I didn't use it on the Evo). After a while I tried to install Cyanogen on it and it failed (it won't boot and get stuck on a loop), eventually resorting to Venom, which is what she has now.
The phone is so slow it takes the keyboard 10-15 seconds to respond between button-pressing. Swipe is obviously impossible, and the phone sometimes gets stuck on boot. The whole thing is sluggish as hell. I'm not sure what going on, the phone was perfectly fine, and now after 3 ROM it's a piece of crap.
I am going to have the phone tomorrow again and I have permission to wipe it clean and try again. What I need is a ROM that has 4.0 if possible, but what's more important for me is that the thing would work smoothly. Having the 3D camera would also be nice. What ROMs would you recommend? Something that should work for sure? Anyone else have issues with Hangouts maybe?
Thanks, all suggestions welcome.
Click to expand...
Click to collapse
All right bro, so it's good that your phone isn't bricked, and it is just slow, so that's the first good part. I'll give you a couple of steps to help your EPIC (because 3D is epic) phone get into the fastest zone possible.
STEP 1) Flash a well-built, not in beta stages, stable rom like NegaLite-BluRom (/showthread.php?t=1745093)
STEP 2) Flash a stable, overclocked (for you) kernel. The best options are Mirage and ButteredToast. Those are the best and most common. DON'T FLASH THIS KERNEL WITH RECOVERY. Install Flash Image GUI apk on your rom (if you can't install it because of huge lag, try the adb method-check out a list of adb commands)
STEP 3) After flashing and rebooting, install an CPU manager of your choice (CPU Master is free)
STEP 4) Overlcock your phone to your need (this is probably your problem
STEP 5) Enjoy your lag-free phone.
*********************Additional Info:
NegaLite supports 3D (just check out its awesome 3D boot animation)
Its IceCream Sandwhich
It can be flashed with S-ON using 4EXT (install this before installing the ROM)
If possible with you lag, backup all your data and contacts using Titanium Backup (save you some time later)
Related
Well here is the issue, I bought the HTC Thunderbolt awhile ago. I then rooted my phone but left the original ROM on it since the custom roms were not stable. I noticed verizon was pushing me some update and I just ignored them. I woke up today to see my phone rebooted with the screen on an exsclamation point. And then my Thunderbolt keeps rebooting itself now. I tried going into ROM Manager to download a Custom ROM but the phone just reboots before I can do it. I just installed Liquid Gingersense v1.6 rom with the MR2 OTA Radio which said it installed just fine after installing the Liquid Gingersense rom. I went through setting up the google account fine and after it booted to the main screen now my phone boots all over again, get stuck at htc screen for a bit then loads the phone fine then boots again. I am really not sure what the heck is going on. I am new to the MR2 OTA Radio since I cam from the Droid 1. So I hope it was not the install order I did it. I Have turned off the phone booted it with still same rebooting over and over issue. If anyone has idea's please let me know. Much appreciated. Thanks
I'm in the same boat. I have wiped the SD card and done a factory reset on the phone. It is no longer rooted, as I can't install and run apps requiring root permission. The update fails every time it tries to install, I also get the exclamation point android screen when the update tries to install. I'll take the update, I don't care. I just want a reliable phone again.
I'm seeing this issue come up a lot. Some of you folks seem pretty upset by it, and reasonably so. Search through the threads and you'll find you solution.
For those who are STILL running that antique and wildly obsolete ROM that the jcase rooting process leaves you with, I'd like to set a few facts before you. First of all, that ROM wasn't provided as a long-term daily driver. It's OLD and it's not very efficient with the battery. Second, simply because it's stock doesn't mean it's inherently stable. It's probably less stable than the custom ROMs out there. Third, the only ROMs really struggling with stability were the 2.01 RUU gingerbread builds. That build is obsolete, but not nearly as obsolete as the ROM that the rooting process leaves you with. The stability issues with the second OTA had nothing to do with the ROM, but rather, the radio that came with the RUU. In short, it's foolhardy to believe that custom ROMs are somehow inherently dangerous or unstable.
I'd like to suggest to whoever might be running the rooted ancient ROM the rooting process leaves you with to abandon it at your earliest convenience. Flash an MR2 radio, and if you like stock, use the stock rooted debloated ROM based on the 1.70 RUU. If you decide not to do this, and your phone auto-accepts the update, you'll probably lose everything on the phone trying to get it working again. Save yourself that hassle. Flashing ROMs isn't hard and people do it everyday.
My issue has been plaguing me for several weeks now. I just stared developing for Android, so I'm a bit of a noob (forgive any obvious mistakes that I have made, or do make)
I have an HTC EVO 3D that I got about 8 months ago. One of the first things I did after I got it was root the puppy and flash a custom Gingerbread ROM to it. That worked great as a development tool for a while, with no issues, whatsoever.
After some time, I updated my custom Gingerbread ROM to a custom ICS ROM, which again, worked fine, minus the minor inconvenience of it occasionally rebooting when I would hit the debug icon on my IDE (Eclipse). That would only happen every once and a while. However, one day last week, all it did, when I hit debug, was reboot. I figured that the ROM was bad in some way, and flashed a custom JellyBean ROM to it. Same issue. I flashed another JB ROM(CM 10), with the same issue. After that, I've done everything that I can think of to fix this issue. I've tried flashing everything that Clockwork would let me flash (Dalvik, cache, did a factory reset, etc) I tried reformatting the SD card, and even tried 3 new ones. I tried reflashing the ROM, I tried 3 other computers, and even re installed Windows on one of them! In my experimentation, I have discovered that it also reboots when I try to record video with the native JB camera (I say that because I installed another camera app from the Play Store, and that works fine).
I'm thinking maybe a memory leak? I honestly have no idea.
HTC EVO 3D
HBOOT 1.40
S-OFF
Thanks in advance
Hi. i own an HTC EVO V 4G (Virgin Mobile). i used the Search function but sadly didnt found exactly what i needed.
a month or so after activating the phone, i decided to Root, S-off, Flash Recovery, bootloader and a custom Rom. However, its been a while now, that when i do a fresh install i get some inconsistency problems. for example, my first Rom was Harmonia, but later on i switched to MidnightRom. there the problems started to show up. the Sense version was working fine, but then i wanted to try out the Jellybean version. and when i did (after wiping everything, of course) some apps were not working. PlayStore wouldnt let me download anything, Tethering was not working, when using "reboot" the phone would get in a bootloop, which would only go away by removing the battery. and 3D games (Shadowgun, Temple Run, etc.) were graphically laggy. more like, unplayable. the image was distorted to the point it was impossible to see what was going on. messed around with fixing permissions, deleting Cache and Dalvik, re-flashing, and the problem was still there. i tried with other Jellybean Roms (both 4.1 and 4.2) and noticed that the problems were still there. anyways, after deciding to live with the problems (running Wild For the Night). months later i decide to flash MidnightRom again and i see that all the problems are magically gone. to this day ive been running only 4.1+ Roms and i dont have many issues whatsoever. BUT. i tried a Senseless Stock-based Rom the other day (started to miss 3D camera) and it ran well, but the overall behavior of the phone was laggy. it would take longer than usual to do anything. took me about 5 re-flashes to get rid of all the problems. then just yesterday i tried a few other Roms. some worked, though DU was really laggy, and the icons would switch places by themselves at times. as i saw the problem was not going away with re-flashing, fixing permissions and whatnot, i decide to restore to my most stable Flashed Rom.
just to clarify, here is what i do every time im about to flash a new ROM:
Wipe everything except SD card
Wipe Cache and Dalvik
Flash.
Reboot
after i flashed, if something went wrong, or if im flashing something ontop:
Wipe Cache and Dalvik
Fix permissions
Reboot
so question is, is this normal? does this has to do with the phone switching from ICS to JB? or am i doing something wrong?
also, just curious... is there a way one could, say, by some weird reason be "half S-off"? because although my bootloader says S-Off, and i have been able to flash many things, i remember that when doing the Wire thing i experienced many errors, and the thing said it was successful by itself a few seconds later while i wasnt doing anything.
and also, which is the best and most stable Hboot version i could use?
My HBoot version is 1.04.2000 (PG8610000)
Radio is 1.09.00.0706
My Recovery is 4EXT latest version
Thanks in advance
Hey guys; I've been using dastin1015's ROMs for almost a year now on my Sprint Evo 3D. I definitely don't know everything (probably not even close) about using custom ROMs, but I'm not a complete noob.
That said, I screwed up. I successfully replaced my 4ext touch recovery with TWRP as dastin1015 says must be done for this ROM. I then wiped everything except my SD card and 'System' and flashed the latest ROM located here (Villuminati 12/08/13), and the "full complete" GApps package located here (4.4).
I rebooted the phone, and admired the new CM splash screen. Once the ROM loaded, I immediately got a couple of stock (system) apps (com.android.phone and ThemeManager along with some others) forceclosing repeatedly, preventing the phone from fully booting and making it very difficult for me to reboot the phone into recovery-- the messages popped up over and over again on top of the menu for reboot. I eventually did manage to get back into TWRP though.
At that point, I wiped *everything* except my SD card, and flashed the ROM and GApps again. Now I'm having the same problem, but with even more system apps force-closing, and I cannot reboot the phone or do anything else with it via the phone itself.
What do I do now? Can I fix this with ADB?
I read that using this 4.4.1 GApps might solve or prevent this problem, but it's iffy. In any case, unless someone has a better solution, that's the next thing I wanna try after managing to reboot into recovery. Do any of you think that will work?
Thank you.
Yes that one worked for me and I used 4ext with no problems
Sent from my Evo 3D CDMA using XDA Premium 4 mobile app
Glad to hear it dschlemmer.
The proper answer to the first part of my question (can I fix this in adb) is "of course, you idiot, just connect the phone to your pc and type "adb reboot recovery" and then wipe and re-install your old ROM or something."
However, I can't get the PC to recognize the phone, despite it having the proper drivers and having recognized it before. I think it's stuck at a phase in its boot-up that comes before the usb debugging is activated. My PC recognizes something is plugged in, based on the ding noise it makes (it's a Win 7 Pro x64 machine, and I think most of us are familiar with that ding noise), but the normal behavior of searching for and finding the drivers and then telling me the device is ready to use never occurs. Neither is there that "safely remove hardware" button in the taskbar.
So, of course, if the computer itself doesn't recognize it, adb can't either (confirmed by typing "adb devices" and it showing nothing). Is there anything I can do, or have I actually managed to completely (irreparably) brick my phone?
EDIT: The usb port is functioning, at least, as is whatever part of the circuitry or firmware controls the LED while plugged in and/or charging, because that works just like it should. It's just that I can't do anything but repeatedly cycle through the same "Unfortunately, the process com.android.phone has stopped", "Unfortunately, Themes provider has stopped", and a couple other messages that get covered up by those two, including one I briefly saw that mentioned "Settings". Haven't been able to see any of the others for long enough to identify any part of them.
EDIT2: I forgot about using the bootloader. Completely forgot. Stupid. Successfully in recovery, about to flash the same ROM with the new GApps. If it gets screwy again, I'll just remove the battery, replace it, and get into the bootloader to get into recovery.
dschlemmer318 said:
Yes that one worked for me and I used 4ext with no problems
Sent from my Evo 3D CDMA using XDA Premium 4 mobile app
Click to expand...
Click to collapse
From that version of GApps, what all did you download and use, exactly? I grabbed Standard and almost everything that didn't come included with it and flashed it all with the same ROM and the phone went into a bootloop that consisted of repeatedly verifiying apps (67 of them), throwing an error message similar to the ones I was getting before, then rebooting to do it all again.
I got a new Galaxy S4 ($50 at Best Buy with a 2-year contract renewal, woot-- Sprint wanted to charge me $200 for the same thing through them directly), so this isn't a pressing issue anymore, but I'd like to give the Evo 3D to my sister-in-law for Christmas. I ended up putting some AOKP Jelly Bean ROM on it (the zip was labeled Unofficial AOKP JB 3.5, I believe) I had sitting in the roms folder on my sd card with its own kernel next to it, and the phone appears to be functioning fine, but I'd like to a) figure out wtf the problem was/is with this ROM or GApps or whatever (something I did wrong probably) because dastin's stuff has always worked great for me before, and b) see Kit Kat in action on the phone. Either that or put it back to stock, which was, what, ICS? Did Sprint Evo's ever get an official upgrade to Jelly Bean?
In any case, and in lieu of posting in the relevant thread in the development forum since I don't have enough posts yet, here's the information about the phone at the time of this weirdness:
S-OFF
Hboot 1.40
Radio 1.09.00.0706
TWRP v2.6.3.0 recovery
NineInchNails' kernel posted in dastin1015's CM10.1-based ROM thread (Wild for the Night)
The ROM on the phone before the attempt to upgrade was dastin's latest Hood Pope version (Oct. 21st, 2013), which had been running just fine up until...
.... about 2 weeks ago, I uninstalled this Call Recorder app because I was running out of internal storage (~40 MB left) and I thought the app was causing it. Even though all the recordings seem to have been on the sd card, uninstalling it appeared to remove about 350 MB of something from the internal storage. Shortly after that (but not immediately after), every time I would end a phone call com.android.phone would force-close. I thought it was weird, but not too troublesome since it only happened after I ended a call, so it didn't affect my actual usage of the phone beyond having to tap an extra button every time I hung up the phone.
Then the other day, I noticed Villuminati was out and it was Kit Kat, so I went to install it, which failed spectacularly (as I said above, probably due to something I did or didn't do, but I'm not positive), and I posted this thread. You pretty much know the rest if you've read to this point.
electrickoolaid said:
From that version of GApps, what all did you download and use, exactly? I grabbed Standard and almost everything that didn't come included with it and flashed it all with the same ROM and the phone went into a bootloop that consisted of repeatedly verifiying apps (67 of them), throwing an error message similar to the ones I was getting before, then rebooting to do it all again.
I got a new Galaxy S4 ($50 at Best Buy with a 2-year contract renewal, woot-- Sprint wanted to charge me $200 for the same thing through them directly), so this isn't a pressing issue anymore, but I'd like to give the Evo 3D to my sister-in-law for Christmas. I ended up putting some AOKP Jelly Bean ROM on it (the zip was labeled Unofficial AOKP JB 3.5, I believe) I had sitting in the roms folder on my sd card with its own kernel next to it, and the phone appears to be functioning fine, but I'd like to a) figure out wtf the problem was/is with this ROM or GApps or whatever (something I did wrong probably) because dastin's stuff has always worked great for me before, and b) see Kit Kat in action on the phone. Either that or put it back to stock, which was, what, ICS? Did Sprint Evo's ever get an official upgrade to Jelly Bean?
In any case, and in lieu of posting in the relevant thread in the development forum since I don't have enough posts yet, here's the information about the phone at the time of this weirdness:
S-OFF
Hboot 1.40
Radio 1.09.00.0706
TWRP v2.6.3.0 recovery
NineInchNails' kernel posted in dastin1015's CM10.1-based ROM thread (Wild for the Night)
The ROM on the phone before the attempt to upgrade was dastin's latest Hood Pope version (Oct. 21st, 2013), which had been running just fine up until...
.... about 2 weeks ago, I uninstalled this Call Recorder app because I was running out of internal storage (~40 MB left) and I thought the app was causing it. Even though all the recordings seem to have been on the sd card, uninstalling it appeared to remove about 350 MB of something from the internal storage. Shortly after that (but not immediately after), every time I would end a phone call com.android.phone would force-close. I thought it was weird, but not too troublesome since it only happened after I ended a call, so it didn't affect my actual usage of the phone beyond having to tap an extra button every time I hung up the phone.
Then the other day, I noticed Villuminati was out and it was Kit Kat, so I went to install it, which failed spectacularly (as I said above, probably due to something I did or didn't do, but I'm not positive), and I posted this thread. You pretty much know the rest if you've read to this point.
Click to expand...
Click to collapse
i flashed rom then 12-6_gapps_standard_4.4.1_signed then reboot this is the link for the gapps : http://forum.xda-developers.com/showthread.php?t=2012857
So my girlfriend's EVO 4G LTE is a bit of.. well, I'm gonna say bastard. I'm not new when it comes to rooting devices but I've never had to deal with one that fought me so much.
I've been through this adventure many times with it, and it gets more complicated each time. Here is what's happened with it so far.
It was stock, and it was terrible. It lagged so much, despite factory resets, that apps like google maps were completely unusable. It got no battery life AT ALL, and was generally freeze-happy and miserable.
So then I s-off'd it and after learning all its quirks, installed recovery and CM 11.2 (I think? It's been a year)
This worked great! For.. a few days. The phone worked, we went on vacation to a roaming area where Sprint had no coverage. We come back, and only the data works, texts and calls do not, and the phone acts like it's not activated. Yay. All attempts to get it activated are met with failure, much to the confusion of the poor sprint person on the line. The phone just will not take, at all. (damn lack of real sim cards..) We tried recovering back to a backup from twrp of the stock firmware but that won't work either? It wouldn't register with sprint even on the backed up version of stock sense. The phone seemed dead at this point. Bricked radio?
So we give up. We bring it to the sprint store, and they do some magic to it, and its back to stock, slow and terrible, but functional. We don't touch it until about three weeks ago.
But, my girlfriend is tired, again, of the terribleness, and asks me to try again. Okay, sure.
I install TWRP again, so far so good. The phone is still S-OFF from last time, which is nice. I go to install CM11.2 from the files used from last time (the MD5 does check out correct) But, the phone complains about not having a new enough bootloader. ???? (So I assume sprint downgraded the bootloader in the process of fixing it. somehow)
I forget the exact numbers, but we can't install CM11.2, only 10. or 10.whatever. the newest 10. Okay, fine. I gather a new set of cyanogen files, gapps, whatever, and flash all of that, so far so good.
This time it works, and stays working! Yay! So I thought.
As it turns out, its on a very old version of android (so old that it goes into a special usb file host mode when usb is plugged in) and more importantly, the camera is TERRIBLE. I've read that the evo 4g lte uses a special ImageSense chip to boost camera performance, and that cyanogen 10 does not support it. I can tell, because the camera is absolutely terrible. The battery life also is terrible, presumably because it lacks optimizations. It had way better battery life on CM11.2 when it worked. Other then that, its working just fine, but the camera is just unacceptable.
So, I want to know what to do from here. I see a few paths.
plan A:
update HBOOT to a newer version to allow the install of CM11.2
(how do I do that? I heard you have to use an RUU, but which RUU? I read that there is some touchscreen driver that is an issue depending on what version you run)
(Once I install the ruu is it business as usual, install twrp and then flash cyanogen like normal? Will it do the crazy not activation thing again? was that a fluke??)
plan B:
update HBOOT, but to a much newer one that allows the install of CM12 or whatever the newer ones are. Presumably updating past the touch screen driver issue and not allowing us to go back to an old version.
(once again, what do I need to do that? Is this advisable? I quite prefer the idea of running a newer version. So if this is the better idea, I will do it.)
I thank you greatly for your help. I'm not used to it being this complicated. I've read a lot of things about this phone and it seems very conflicting at times. I just want to get straightened out.
yeah, it's probably running like crap because the firmware is so out of date.
use this RUU http://forum.xda-developers.com/showthread.php?t=2653730
then re-flash twrp and another ROM if you want (i've been running cm12.1 for MONTHS) but she might be able to survive just like that. only fear would be staying vulnerable to security threats, but you've been living in that house this whole time anyway.
for a good while i was running this stock 4.3 with root and some xposed modules installed to get the cm functionality that i missed. but seriously, run the RUU, let it activate, then go under settings and update profile and PRL, fire up maps/navigation with GPS on so that it gets a good lock and its cache populated, then you should be good from there.
Thank you!
Can I use the same utility that I used to flash twrp (that one-click thing that seems to support a half million phones) or do I need something special? This sounds very easy to do. Almost too easy, given that the story of this phone's life is that the easiest thing I've ever done to it was take it completely apart to replace its battery.
never used the one-click stuff. flashing recovery via fastboot is simple enough.
get the adb tools, here's some easy instructions for that http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
get the latest twrp from here https://dl.twrp.me/jewel/
then follow these directions to flash twrp https://wiki.cyanogenmod.org/w/Install_CM_for_jewel#Installing_a_custom_recovery_using_fastboot
if not installing cm or any other rooted rom (you want to root stock) get supersu from here http://forum.xda-developers.com/showthread.php?t=1538053 and use the twrp installable zip
If you've gone through the trouble to S-Off, then fastboot flash the latest TWRP (3.0.2.0, I believe), which supports the new partition layout (extra 4gig of internal SD space).
From there, flash the official 651.4 developers version, go through the device setup which updates your PRL, then shut it down and reboot to TWRP and flash the latest CM12.1 and a proper gapps package (I use "stock", which is a bit much for some, but I like having everything available to me).
The one thing I do that most don't is to disable zRam and enable swap with my own script I wrote specifically for the external SD I formatted as vFat/ext4/swap.
After doing all this, I do not have the issues you seem to have, and the PRL seems to stay from the last install of stock Sense 5. Even with all the apps I have installed, it's still fairly snappy. Facebook/Messenger, and other memory hogging apps run smooth with no discernable lag, unless there's network issues.
YMMV, but look into using an app like "Ampre" to measure battery life and gauge if the battery is going bad or not.
Outside of that, there's not much left to do with these older devices that hasn't been done already.