OG Evo vs. Evo 3d - HTC EVO 3D

OG Evo vs. Evo 3d - HTC EVO 3D

Finally getting my flash fix. Withdrawals from flashing was bad..dreams of recovery..hand automatically pressing volume down..wondering if wiping dalvic would improve my gas mileage. Well I notice some differences from the OG evo.
1. Roms much bigger. At least twice the size. This means I need a bigger sd card for backups and the roms themselves.
2. Backups and restores are faster.
3. Initial bootup is much quicker..!!!!
4. Make backups of WatchIt..and restore with titanium else it will say update needed and when trying to update it says up to date.
5. Sprint hotspot fixed.
6. Wifi tether is still finicky.
These are the initial ones I found so far. We have reached what we all waited for. Now, to sit back and see these roms improve. Who said the developers left? They are like us, waited and when we got the green light....full bore ahead.

Spyderekz said:
screw this thread
Click to expand...
Click to collapse
10 characters

Related

Saying Hi, ROM Recommendations & Other Noob Questions

Kind of long, but genuine, trying not to get too much bashed here...
Preface/Experience: A year ago or so I experimented with the Samsung Nexus S line of phones from all the major carriers, rooted them, flashed some ROMs, etc, and all my knowledge was learned from here (thanks!), but that was a while ago. I ended up not keeping any of them due to issues at the time with them (GPS locking, single core, 3G, etc) and decided to wait for some newer technology. I recently picked up an HTC Sensation to finally replace my old Blackberry after I had some issues with it the other day. As soon as I took it out of the box, my girlfriend was all mad because the entire time she has had her Thunderbolt she has complained about the SMS application not having separate "bubbles" for the chat windows, and of course Sense 3.0 does this (yes, she has tried handcent and such but doesnt like it). She also fell in love with the Sense 3.0 lock screens I have, home screen scroll, etc. I decided this would be a good first task for me to get back into the Android game...
I spent the first day or so searching about what the hell S-On/S-Off were, how to root these, etc. I successfully have S-Off, root, etc on both our phones via the revolutionary application, clockwork recovery is installed, as well as titanium backup. I have also successfully flashed a synergyROM onto her phone with Sense 3.0 and she has been enjoying it for the most part.
Now, onto the questions...
First, as nice as this ROM is, its a little too modified for her liking. Is there a ROM that would suit her desires better? She is looking for basically stock looking, bloatware removed if possible, with Sense 3.0 messaging and lock screens at a minimum. Nothing too major really, just UI tweaks.
Second, am I correct that after flashing a ROM you need to reinstall titanium backup each time so you can restore your apps and data? Is there a Zip file I can store on the SD card to install TiBu so I dont have to sign in and get it from the market each time?
Third, am I also correct that the main purpose of clockwork recovery is to backup the ROM, and the main purpose of TiBu is for the apps and their data? Meaning, to get the stock ROM back on this phone, I use clockwork to flash the backup I made, then use TiBu to flash the backup I made with that? I know this seems simple, but I just want to be clear Im thinking about this correctly.
Fourth, does it make a difference if I boot into clockwork recovery to flash a ROM versus doing it through ROM manager?
Oh, and fifth. WTH is a radio file/ROM/whatever you want to call it and how do you know which one you have? We are having an issue with her 4G not working on this new ROM I flashed, I assume its an error on my behalf, possibly the radio file? I'm not too clear on what those are just yet (I know, I should know before I started, but oh well)... I will be searching again through the 5 mile long thread over at the site where I found the ROM about 4G connectivity, but so far I haven't seen any issues posted by other people which is why I think I might have missed a step or something.
Any insight to any of these questions is appreciated, and I thank you all in advance!

02CWRX said:
Kind of long, but genuine, trying not to get too much bashed here...
Preface/Experience: A year ago or so I experimented with the Samsung Nexus S line of phones from all the major carriers, rooted them, flashed some ROMs, etc, and all my knowledge was learned from here (thanks!), but that was a while ago. I ended up not keeping any of them due to issues at the time with them (GPS locking, single core, 3G, etc) and decided to wait for some newer technology. I recently picked up an HTC Sensation to finally replace my old Blackberry after I had some issues with it the other day. As soon as I took it out of the box, my girlfriend was all mad because the entire time she has had her Thunderbolt she has complained about the SMS application not having separate "bubbles" for the chat windows, and of course Sense 3.0 does this (yes, she has tried handcent and such but doesnt like it). She also fell in love with the Sense 3.0 lock screens I have, home screen scroll, etc. I decided this would be a good first task for me to get back into the Android game...
I spent the first day or so searching about what the hell S-On/S-Off were, how to root these, etc. I successfully have S-Off, root, etc on both our phones via the revolutionary application, clockwork recovery is installed, as well as titanium backup. I have also successfully flashed a synergyROM onto her phone with Sense 3.0 and she has been enjoying it for the most part.
Now, onto the questions...
First, as nice as this ROM is, its a little too modified for her liking. Is there a ROM that would suit her desires better? She is looking for basically stock looking, bloatware removed if possible, with Sense 3.0 messaging and lock screens at a minimum. Nothing too major really, just UI tweaks.
Second, am I correct that after flashing a ROM you need to reinstall titanium backup each time so you can restore your apps and data? Is there a Zip file I can store on the SD card to install TiBu so I dont have to sign in and get it from the market each time?
Third, am I also correct that the main purpose of clockwork recovery is to backup the ROM, and the main purpose of TiBu is for the apps and their data? Meaning, to get the stock ROM back on this phone, I use clockwork to flash the backup I made, then use TiBu to flash the backup I made with that? I know this seems simple, but I just want to be clear Im thinking about this correctly.
Fourth, does it make a difference if I boot into clockwork recovery to flash a ROM versus doing it through ROM manager?
Oh, and fifth. WTH is a radio file/ROM/whatever you want to call it and how do you know which one you have? We are having an issue with her 4G not working on this new ROM I flashed, I assume its an error on my behalf, possibly the radio file? I'm not too clear on what those are just yet (I know, I should know before I started, but oh well)... I will be searching again through the 5 mile long thread over at the site where I found the ROM about 4G connectivity, but so far I haven't seen any issues posted by other people which is why I think I might have missed a step or something.
Any insight to any of these questions is appreciated, and I thank you all in advance!
Click to expand...
Click to collapse
Ok... Got to a real keyboard so I'll toss some answered out there and try to put some structure to the not so structured wealth of information...
One: Synergy is probably the most tweaked up ROM out there. If you're looking for something that's simply bullet-proof reliable, I highly recommend BAMF Forever. Chingy also has some good ROMs in the Gingeritis line. BAMF can be found at teambamf.com and Chingy's ROMs are at themilkmik.com.
If those prove too modified, there's a few debloated ROMs based off the latest OTA patched up to fix the problems with the OTA version.
Two: You wouldn't be looking for a .zip for Titanium Backup. You'd be looking for an .apk file. Not sure where to find that though. Not may devs pack a backup app with their ROM because tastes vary and TiBu isn't the only app that does what it does.
Three: You pretty much have the idea regarding Clockwork backups (a.k.a., nandroid backups). I will direct you to my Q&A thread linked in my sig regarding TiBu. Basically, doing a batch backup is all good, but doing a batch restore is an excellent way to render your ROM useless. Devs use different apps and versions and frameworks and the system data often doesn't work well one ROM to another.
Four: Regarding CWR and Rom Manager, pretty much every dev recommends against using Rom Manager for flashing their ROM. There seems to be issues for whatever reason and it's just proven unreliable over time. A custom recovery is the only good way to flash a ROM and perform the various utility functions a custom recovery affords. You have your choice between CWR, Amon Ra, and TeamWin.
Five: Let me break this down into the 6 basic kinds of flashable files. First, and most common is a ROM. This is the OS, kernel, and UI along with whatever apps the dev has added They are usually 250MB to 310MB .zip files.
Second would be a kernel. ROMs are packed with kernel, but custom kernels exist that may be better for your purposes.
Third, would be radios. Radios can be individual radio firmwares, or a pair of them for CDMA and LTE all in one .zip file. A pair will be roughly 24-25MB, a single radio roughly half that. I explain more about radios in my thread.
Forth would be custom recoveries. These you rarely need to flash, perhaps never, so long as the version you're using supports the ROM's that are out there, and just about every version out there for the Tbolt does.
Fifth would be bootloaders. This is something you pretty much NEVER need to flash unless you've got a pretty good reason to mess with it. Bad radio and bootloader flashes will brick your device.
Sixth would be an RUU. An RUU is a full firmware package for your device. New bootloader, stock recovery, stock kernel, stock ROM, and radios.
There are also mods and patches that you can flash as well. Those are done in the same way as ROMs and kernels. The firmware hierarchy would look something like [bootloader>radio>recovery>ROM] with the bootloader being about as basic as it gets. Once you get used to how all this fits together it will make a lot of sense.
Hope this helps. If you have further questions feel free to hit me up on gtalk, pm me here, or post in this thread or my Q&A thread. I'll get back with you ASAP.

Thanks for the reply, I added you to gtalk also. I kind of feel like a horses ass because Im not sure how I missed that Q&A link; I presume its because I was doing nothing but searching the forums and didn't see the stickies somehow - d'oh. Kind of embarrassing to read that right after doing exactly what it says not to do (ask for ROM suggestions, ask a question about the radios which is laid out as well).
I was looking at the BAMF ROMs just last night actually, looks like I will check those out. I chose the Synergy simply based off the 3 screen shots I saw with the Sense 3.0 (which was my goal). That ROM is pretty cool, but as I said, its a bit much for my (her) needs at this point. Since I got it swapped around and such, it seems Im on the right track none the less.
Ahh, apk, duh. Also the logic as to why its not included makes perfect sense, I hadnt thought of it like that since I just saw those two (clockwork and TiBu) as the "common standard" and went with them even though Im sure plenty of people use others. I just thought I read in one of the how-tos that "setting up accounts" could be skipped simply by loading a TiBu, but since you cant do that without having it and you have to setup the market account to get it, it seemed bassackwards to me I suppose. Oh well. I've made do just fine so far by loading it through the market both times I've needed to.
I assume by "custom recovery" you mean the recovery console using custom software such as CWR which has replaced the factory console. I used CWR to flash it the first time and then when I messed it up with the TiBu restore (which you also covered in your Q&A I read last night after I figured it out and fixed it), I re-flashed it via ROM manager and had no issues that way either - hence the question originally. I will stick to doing it through CWR.
The order of things makes some sense to me now and the light is starting to shine through. I still didn't see much about the radio in the ROM thread, so I'm still curious why we are only looking at 3G. I also (oddly?) didnt see a recommended radio to go with the ROM, but it was late and I was tired. I will look into this again.
Is there a good source for a nice clean stock RUU for her phone just in case we need to go back to stock to warranty it? It has a loose charging plug currently that we may want to have addressed. Alternatively, is there a better way to get it back to "out of the box stock" than flashing an RUU?
Thanks again!

02CWRX said:
Thanks for the reply, I added you to gtalk also. I kind of feel like a horses ass because Im not sure how I missed that Q&A link; I presume its because I was doing nothing but searching the forums and didn't see the stickies somehow - d'oh. Kind of embarrassing to read that right after doing exactly what it says not to do (ask for ROM suggestions, ask a question about the radios which is laid out as well).
I was looking at the BAMF ROMs just last night actually, looks like I will check those out. I chose the Synergy simply based off the 3 screen shots I saw with the Sense 3.0 (which was my goal). That ROM is pretty cool, but as I said, its a bit much for my (her) needs at this point. Since I got it swapped around and such, it seems Im on the right track none the less.
Ahh, apk, duh. Also the logic as to why its not included makes perfect sense, I hadnt thought of it like that since I just saw those two (clockwork and TiBu) as the "common standard" and went with them even though Im sure plenty of people use others. I just thought I read in one of the how-tos that "setting up accounts" could be skipped simply by loading a TiBu, but since you cant do that without having it and you have to setup the market account to get it, it seemed bassackwards to me I suppose. Oh well. I've made do just fine so far by loading it through the market both times I've needed to.
I assume by "custom recovery" you mean the recovery console using custom software such as CWR which has replaced the factory console. I used CWR to flash it the first time and then when I messed it up with the TiBu restore (which you also covered in your Q&A I read last night after I figured it out and fixed it), I re-flashed it via ROM manager and had no issues that way either - hence the question originally. I will stick to doing it through CWR.
The order of things makes some sense to me now and the light is starting to shine through. I still didn't see much about the radio in the ROM thread, so I'm still curious why we are only looking at 3G. I also (oddly?) didnt see a recommended radio to go with the ROM, but it was late and I was tired. I will look into this again.
Is there a good source for a nice clean stock RUU for her phone just in case we need to go back to stock to warranty it? It has a loose charging plug currently that we may want to have addressed. Alternatively, is there a better way to get it back to "out of the box stock" than flashing an RUU?
Thanks again!
Click to expand...
Click to collapse
I think the RUU for 2.11.605.3 is floating around here somewhere. If it's not here, it's on Rootzwiki. The problem with flashing an RUU to return to stock is that if you rooted via Revolutionary it's not going to work. The bootloader Revolutionary is patched to prevent overwriting. You'll need to find a guide for unrooting after a Revolutionary root, but I think I have one in my thread. If you rooted via ADB, then flashing an RUU should do the trick.
Not really sure why LTE isn't working. LTE and CDMA data are handled on the same chip with the same radio so if one doesn't work, the other shouldn't work either. My best suggestion is try a different radio. I'd suggest the 2.10 radio or one of the 2.11 radios. People have generally been having pretty good luck with those. You might try going into the radio settings and forcing it to use LTE Only. If it can't find an LTE signal it'll revert back to 1x. For reference, any radio from an RUU 1.70 or later will work just fine with all the Gingerbread ROMs currently out there.
Hit me up if you've got any more questions.

Turns out it was in fact user error. There is a toggle built into the ROM to exclude LTE service if you wish *facepalm*
I had looked in a radio menu before after the first flash knowing of such toggles, but it was already selected correctly. It got reflashed after the TiBu mishap, still no 4G, and we called it a night. Today I found where someone mentioned a toggle and where it was, so I texted her to look following those directions. Sure enough she found it and she was able to change it to have 4G. I'm curious which menu I looked in initially and which menu she found the toggle in now. In any case, it seems its all working and that's what matters.

02CWRX said:
Turns out it was in fact user error. There is a toggle built into the ROM to exclude LTE service if you wish *facepalm*
I had looked in a radio menu before after the first flash knowing of such toggles, but it was already selected correctly. It got reflashed after the TiBu mishap, still no 4G, and we called it a night. Today I found where someone mentioned a toggle and where it was, so I texted her to look following those directions. Sure enough she found it and she was able to change it to have 4G. I'm curious which menu I looked in initially and which menu she found the toggle in now. In any case, it seems its all working and that's what matters.
Click to expand...
Click to collapse
There's two of them, I know. Don't know why we need two that basically do the same thing, but we do! Glad you got it working. I use an app called LTE On/Off for flipping back and forth. Sometimes you need that because it'll stick on 3G when you know you're in an LTE area and it helps to kinda force it.

[How To] Stop Bootloop for Sense 3.5

Just to preface a couple of things:
I am not a developer.
I have never written code, a ROM, a Kernel, Theme, etc
I am just a regular Flashaholic that has been tinkering with Android since the OG EVO
I have about 300+ apps and games that I always restore to every ROM I run (What can I say, I am a Amazon Free App Whore and like to play games)
I have a Class 4 SanDisk 32 GB Micro SD card installed
If you are like me, you like to have the latest and the greatest on your phone and have been trying to find a good, stable build of Sense 3.5 for the EVO 3D. I have had issues with almost every Sense 3.5 ROM out there for the EVO 3D. Once I get everything flashed and restored, I get the dreaded bootloops every minute or so.
I tried most of the latest versions of 3.5 ROM's out there: Eternity, Hydro, Prime XL, AndroTech, etc. Every single one of them had issues with bootlooping (even though most people were saying it was a stable build) and I tried everything, fixing permissions, flashing a new kernel, wiping everything and starting fresh, etc. Nothing seemed to fix the issue. I got a few different suggestions to fix the issue. "It must be an incompatible app", "Try a different kernal", "Do a fresh flash and restore", "Don't restore data from the apps on Titanium Backup", etc. Nothing seemed to work. So, for the last week or two I have been playing around with different options trying to narrow down the issue.
The normal steps I would go through to get a new ROM setup (THIS CAUSED BOOTLOOPS):
Wipe Data, Cache and Dalvik 3 to 4 Times Each
Run Chad's Modified SuperWipe 2-3 times
Flash Sense 3.5 ROM
Reboot
Let it settle without logging into any accounts or restoring anything
Reboot to Recovery
Flash New Kernel (If desired)
Reboot and let settle
Reboot to Recovery
Flash Amaze Camera (If desired)
Reboot and let settle
Log Into Google (let sync), Log Into FB (let sync), log into all accounts (let sync)
Restore apps only (no data) through Titanium Backup
Let settle
Move all apps (that can be moved) to the SD card with App2SD Pro Application
The ROM might run fine for a little while, then BOOTLOOP
The last time I did this was 2 days ago on Prime XL Sense 3.5 and the same thing happened. I noticed that the phone would only bootloop when the application icons on the SD card started populating into the application drawer (meaning that the system was gathering them off of the SD card for use). Instead of wiping everything and starting over, I simply Uninstalled all applications with Titanium Backup and the bootloops stopped.
The steps I have taken since that have not caused a bootloop and have allowed me to reboot without issues:
Restored about 30 apps at a time all less than 30 Mb each
Moved only games under 30 Mb each to the SD Card through the HTC Low Storage Wizard
Installed a couple of 40+ Mb games like Blood & Glory and Bejeweled and did not move them to the SD card
With this process, I have been running Prime XL for more than 12 hours with only one random reboot and no bootloops. I can restart my phone with no issues.
I then moved a 40+ Mb game to my SD card and tried to reboot. Guess what, I got bootloops. I had to uninstall all the applications off of my SD card in between the 1 minute bootloops (took a few boots to get them all uninstalled since you have to do it through the Settings-->Applications-->SD Card menu). Once I got all of them off of my SD card, the bootloops stopped and I restored those applications again without the large game on my SD card and rebooted just fine. I repeated this again with a different app that was 40+ Mb and the same thing happened.
Like I said in the preface, I am no developer, coder, themer, etc. (Just a guy trying to figure out a problem), but it seems that the issue with these bootloops lies in reading large applications or games off of the SD card. It might also be the combination of having a lot of apps on the SD card and the larger app/game as well. It has nothing to do with anything else in the ROM as far as I can tell.
Hopefully a good dev can read this and find a way to fix the issue with whatever script is causing the problem. I think I have isolated the issue since the only thing that changed causing the bootloops was the larger app/game that I moved to the SD card.
It might help the devs if some other people can reproduce this issue and confirm what I am saying is correct for more than just me.

I have also tried this on Virus' Eternity 3.5 and Hydro 3.5 with similar results.

well let me ask you this...
are you the only one getting bootloops? seems if you are getting the same problem with every build, the issue is something you are doing. you should try getting a class 10 sd card or something with a much higher read capability and see if the issue goes away.
also...
cool story bro. and should i flash this from recovery? is a full format required before i flash???? oh wait.. wait..
also also...
it must take you years to flash a new rom... i dont understand the whole "let the phone settle" theory. as soon as i boot up i start logging into my accounts and sending text messages, browsing the web, using the phone. never had an issue that was traced back to "didnt let the phone settle" lol
in any case, i think you may be on to something here with this, but like i said the issue is isolated to your unique usage. flash a 3.0 rom like clean rom, go through that whole dragged out install process again, same scenario, set up, everything, and see if you get bootloops.

cobraboy85 said:
well let me ask you this...
are you the only one getting bootloops? seems if you are getting the same problem with every build, the issue is something you are doing. you should try getting a class 10 sd card or something with a much higher read capability and see if the issue goes away.
also...
cool story bro. and should i flash this from recovery? is a full format required before i flash???? oh wait.. wait..
also also...
it must take you years to flash a new rom... i dont understand the whole "let the phone settle" theory. as soon as i boot up i start logging into my accounts and sending text messages, browsing the web, using the phone. never had an issue that was traced back to "didnt let the phone settle" lol
in any case, i think you may be on to something here with this, but like i said the issue is isolated to your unique usage. flash a 3.0 rom like clean rom, go through that whole dragged out install process again, same scenario, set up, everything, and see if you get bootloops.
Click to expand...
Click to collapse
I'm not the only one getting bootloops. I have read the same issue with people getting bootloops in every Sense 3.5 ROM all over this forum. I have been flashing for about a year now and usually flash a new ROM every week or two. I used to not go through that extended process, but I have been trying different things to get 3.5 stable. I was more trying things that I have heard. (like letting it settle) I don't think it really does anything, but it can't hurt.
I don't have this issue with Sense 3.0 buddy. I usually just wipe everything once, Superwipe once and then flash and restore and with Sense 3.0 it works fine. I tried that with Sense 3.5 and got bootloops. So like I said in the OP I started trying different things. The list of what I did just shows that I was being extremely careful.
Trust me, it is not the process or the SD card, because I have never had this issue with any other type of ROM besides Sense 3.5 and I am not the only one experiencing the bootloops.
Also, Class on an SD card is not an exact measurement. A Class 4 can be better than a Class 10 because the manufacture measures the speed differently or as a best case scenario instead of consistent performance. See Wikipedia info below:
"The Speed Class Rating is the official unit of speed measurement for SD cards. The class number guarantees a minimum write speed as a multiple of 8 Mbit/s (1 MB/s). The SD Association defines several speed class ratings, but manufacturers may claim conformance to those ratings without independent verification."
"is not as specific as Speed Classes are on how to measure speed. Manufacturers may report best-case speeds and may report the card's fastest read speed, which is typically faster than the write speed."

I would say it has to be an issue with you restoring from titanium backup. If you are doing it In a batch and your like me there are some sense 3.0 apks in my backups. If you batch restore anything that doesn't play nice with sense 3.5 it doesn't matter.if you are restoring data or not.at that point
Sent from my PG86100 using xda premium

cobraboy85 said:
well let me ask you this...
are you the only one getting bootloops? seems if you are getting the same problem with every build, the issue is something you are doing. you should try getting a class 10 sd card or something with a much higher read capability and see if the issue goes away.
also...
cool story bro. and should i flash this from recovery? is a full format required before i flash???? oh wait.. wait..
also also...
it must take you years to flash a new rom... i dont understand the whole "let the phone settle" theory. as soon as i boot up i start logging into my accounts and sending text messages, browsing the web, using the phone. never had an issue that was traced back to "didnt let the phone settle" lol
in any case, i think you may be on to something here with this, but like i said the issue is isolated to your unique usage. flash a 3.0 rom like clean rom, go through that whole dragged out install process again, same scenario, set up, everything, and see if you get bootloops.
Click to expand...
Click to collapse
Ok, your first point was helpful, but the rest was necessarily douchey. You should have just said your first point and then told him wrong section instead of making yourself look like a child. Way to go dude.

drgonzo712 said:
I'm not the only one getting bootloops. I have read the same issue with people getting bootloops in every Sense 3.5 ROM all over this forum. I have been flashing for about a year now and usually flash a new ROM every week or two. I used to not go through that extended process, but I have been trying different things to get 3.5 stable. I was more trying things that I have heard. (like letting it settle) I don't think it really does anything, but it can't hurt.
I don't have this issue with Sense 3.0 buddy. I usually just wipe everything once, Superwipe once and then flash and restore and with Sense 3.0 it works fine. I tried that with Sense 3.5 and got bootloops. So like I said in the OP I started trying different things. The list of what I did just shows that I was being extremely careful.
Trust me, it is not the process or the SD card, because I have never had this issue with any other type of ROM besides Sense 3.5 and I am not the only one experiencing the bootloops.
Also, Class on an SD card is not an exact measurement. A Class 4 can be better than a Class 10 because the manufacture measures the speed differently or as a best case scenario instead of consistent performance. See Wikipedia info below:
"The Speed Class Rating is the official unit of speed measurement for SD cards. The class number guarantees a minimum write speed as a multiple of 8 Mbit/s (1 MB/s). The SD Association defines several speed class ratings, but manufacturers may claim conformance to those ratings without independent verification."
"is not as specific as Speed Classes are on how to measure speed. Manufacturers may report best-case speeds and may report the card's fastest read speed, which is typically faster than the write speed."
Click to expand...
Click to collapse
Word. That makes a little more sense then… and yes I am familiar with the difference between class rating and read speeds. In my personal experience, sandisk and PNY are the two that consistently rate their cards accurately. I only use PNY myself… anyways, back on topic…
Like somebody else suggested before this, you should try not using titanium back. Try these two things…
1 ) uninstall ALL data/app/ files (basically all of your apps you add with TB)… run the ROM for a few days, see if you get reboots. Run processor at stock frequencies, etc etc… as STOCK as possible for a few days (other than you having a custom ROM obviously.)
2 ) re-install apps, and do it manually, 1 by 1, with root explorer (reason is because root explorer is faster when doing it manually) and do not backup, restore, any kind of data whatsoever. You just want .apks. do not install any of them to the SD card.
3 ) move larger apps to the SD card
4) move all apps possible to the sd card
The point here is to change one dimension of your functioning ROM one phase at a time so you can easily pinpoint what is causing your issues. Very detailed process of elimination is key when trouble-shooting anything. For each one of these steps, wait a couple days to move to the next one. The longer you go without having a problem, the more likely it is that a problem showing itself after the next phase was indeed caused by that phase.
I am suspicious of TB, to be honest… I would start by removing that app out of your daily routine. I have used my backup root since it was released and still never had an issue… the one time I used TB, had force closes, odd little un-explained issues… it just isn’t as simple as my backup root, and simplicity is what you want when using apps that backup all your ****. The more cut and dry, the better.
Good luck
---------- Post added at 03:44 PM ---------- Previous post was at 03:32 PM ----------
Wasn’t trying to be a douche about it.. but I guess it did kind of come off that way, haha. Sorry if I was a little bit critical in my comments… not intended, just how I communicate sometimes – forward and in black and white.
Anyways, to the OP, hopefully you are able to get somewhere with the input of my post… trouble-shooting can be annoying but the key is to be patient and do things in increments.
and i didnt come here spouting "oooo wrong section wrong section..." because thats not my job and i didnt want to come off like a douche... i try to contribute and not be so critical, but sometimes i just am.

I got a quick question why move apps to the SD card to begin with? The phone has massive amounts of internal storage.(why app2sd is left out of many ROMs for the 3vo)
I would rather have the SD space for roms, tweaks, music etc. I'm with you with the games and etc. I use a ton of different apps, I also store any apps I think I might use later on my SD card in uninstalled apk form...
An example is a Craigslist app I use, I rarely use it, so I install and uninstall as needed. And I've read that titanium backup doesn't play nice with batch operations.. just my 2 cents, and thanks for your post, I was gonna flash a sense 3.5 ROM tonight, not even gonna bother with it now.
Shot from my sharp shooter in 3d
cleanrom2.9.5

bmtdan said:
I would say it has to be an issue with you restoring from titanium backup. If you are doing it In a batch and your like me there are some sense 3.0 apks in my backups. If you batch restore anything that doesn't play nice with sense 3.5 it doesn't matter.if you are restoring data or not.at that point
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Can't be that, when I restore whatever apps from TB and don't move them to the SD card they are fine and the phone does great. It only happens when I move apps to the SD card. Shows that it doesn't have anything to do with the apps themselves, but something with Sense 3.5 reading them from my SD card.

hitman4274 said:
I got a quick question why move apps to the SD card to begin with? The phone has massive amounts of internal storage.(why app2sd is left out of many ROMs for the 3vo)
I would rather have the SD space for roms, tweaks, music etc. I'm with you with the games and etc. I use a ton of different apps, I also store any apps I think I might use later on my SD card in uninstalled apk form...
An example is a Craigslist app I use, I rarely use it, so I install and uninstall as needed. And I've read that titanium backup doesn't play nice with batch operations.. just my 2 cents, and thanks for your post, I was gonna flash a sense 3.5 ROM tonight, not even gonna bother with it now.
Shot from my sharp shooter in 3d
cleanrom2.9.5
Click to expand...
Click to collapse
Yes, it has 1GB of internal storage, but it is not enough when you have around 300 apps and games (Plants vs Zombies, Blood & Glory, Peggle, All the Angry Birds, etc) they go well above the 1 GB internal. I have to move to SD to get them all on there. I don't us A2SD, I just move them to the SD card through the standard process.

Update:
I hit a random reboot and then when it rebooted I started getting bootloops again even without moving the large apps/games to the SD card. So the process in the OP is not a fix, it just worked for a while.
However, when it was in between bootloops, I unmounted the SD card and they stopped.
The issue has to be something with the SD card being read by Sense 3.5 because I have never had this issue with Sense 3.0. What I am trying now is Formatting the SD card and the Partition on the SD card and starting fresh. Only going to move my pics and Nandroids back to the SD card. Hopefully a fresh SD card will allow me to move the apps over there and make things all good. Not to optimistic, but keeping my fingers crossed.

Found the solution!!
Ok, so after playing around with all this stuff for a long time and trying different things, I found out that if you move more than 59 apps (so 60 or more) to the SD card, you will get boot loops on Sense 3.5 if you move 59 or less everything works fine.

drgonzo712 said:
Ok, so after playing around with all this stuff for a long time and trying different things, I found out that if you move more than 59 apps (so 60 or more) to the SD card, you will get boot loops on Sense 3.5 if you move 59 or less everything works fine.
Click to expand...
Click to collapse
So does the <59 rule still hold truth?
Im facing the same headache on cyanogen so it's definitely not just HTC with this problem.

drgonzo712 said:
Yes, it has 1GB of internal storage, but it is not enough when you have around 300 apps and games (Plants vs Zombies, Blood & Glory, Peggle, All the Angry Birds, etc) they go well above the 1 GB internal. I have to move to SD to get them all on there. I don't us A2SD, I just move them to the SD card through the standard process.
Click to expand...
Click to collapse
that would give any phone the bootloops

[Q] OG to 3D Help

So I ran over my OG Evo this morning after it fell out of my jacket pocket while I was getting into my car.
Asurion is sending me a 3D as a replacement and while I'm jazzed about the better performance potential, I'm seeing all kinds of horror about rooting it with the 1.5 hboot.
I'm running Mik 2.61 and was heading to Mik 3 this weekend. So i'm hoping to find a ROM that's got similar performance and battery life. I'm also wondering the best way to not lose all my data (gaming, mms/sms, etc) since I've never had to swap phones like this. My last full backup with TBPro was yesterday afteroon so I'm guessing I'll lose anything after that.
So any help with the swap of data and recommendations on a killer ROM would be welcomed!

P_M_G said:
So I ran over my OG Evo this morning after it fell out of my jacket pocket while I was getting into my car.
Asurion is sending me a 3D as a replacement and while I'm jazzed about the better performance potential, I'm seeing all kinds of horror about rooting it with the 1.5 hboot.
I'm running Mik 2.61 and was heading to Mik 3 this weekend. So i'm hoping to find a ROM that's got similar performance and battery life. I'm also wondering the best way to not lose all my data (gaming, mms/sms, etc) since I've never had to swap phones like this. My last full backup with TBPro was yesterday afteroon so I'm guessing I'll lose anything after that.
So any help with the swap of data and recommendations on a killer ROM would be welcomed!
Click to expand...
Click to collapse
Hboot 1.5 isn't all that bad, you just have to read a little to get everything working. There are plenty of tutorials an recommendations that will help you be a flashaholic on 1.5.
In my personal opinion (which means absolutely nothing in the real world), stock on the 3D destroys MikG. In no way am I saying that Mik is bad. In fact, if Mik had a ROM for the 3D, I'd most likely be on it. It's what I was running on the OG as well.
With that said, there are a ton of wonderful ROMs here. Olympus is getting great reviews and it's fairly user friendly. I'm personally running a Nocturnal ROM (that gets no love cause it's basically stock with Zeus mod) that I think its amazing.
Your gonna love the 3D, just root that bad boy and do some testing, your bound to find something you like.
And yes, in terms of the data for your apps, the last backup will have to do. Just don't attempt to restore system backups. That might screw something up.

Thanks - so can I just copy the backup file from my old SD card to the new card, push installs of apps from web to phone including TBPro, then use TBPro to restore app data?
My whole reason for rooting my OG was to get rid of the bloat, then I n00bed and tried to download the GB OTA, bricked, lost root, waited fro Revolutionary to get root back, went from stock to CM7, to Synergy, to Mik...
I guess I'm not fully understanding the 3D still being S-ON and having root ... or am I still n00bing with that comment?? LOL.

They did the same to me mine came with hboot 1.4 and was brand new not refurb. this was about 2 weeks ago cross your fingers!

I lnow how good mik roms are I remeber when I had my incredible but for the evo 3d I would reccomend Olympos titan Hd it the vest on performance and battery life_!
Sent from my PG86100 using XDA App

Same thing happened to me man. My Evo fell out of my lap when I was getting out of my car, straight onto the driveway. I was also planning on moving from MikG 2.6 to 3.0, I had it on my sdcard lol. So I waited till Asurion said I was getting a 3D, and I finished the claim.
I was also pretty confused about the rooting with 1.5 hboot like I had but you just have to follow directions to the word.
http://forum.xda-developers.com/showthread.php?t=1239821
That is the guide I used to root mine, but I failed the first time when it came to like step 12 when your Evo will ask you if you want to unlock it. My problem was I didn't have the HTC drivers installed, so make sure you do that. The only limitation with this method is that you can't flash kernels through recovery, because the boot partition is still locked. You have to download and app called flash image GUI (available in the market for 99 cents) and use that to either search a rom zip and extract the kernel info, or just pick a kernel zip by itself. This will apply the kernel, wipe dalvik and cache, and then reboot your device. Do this before you flash the rom you want to run. And make sure you do a nandroid of your stock rom first before anything.
As far as roms go, I recommend Myn's Warm 2.3. Very snappy, looks great, and very stable unlike some other roms I've tried. I used Myn's 2.2 on the OG Evo back before MikG came out. The dev community here isn't as big as the Evo's but there are some great devs here, I'm sure you'll warm up to it quick like I did.

New LTE owner... Lagging?

Ok guys... coming over from the OG Evo 4G... I love this phone so far. I've had it for about 2 days. Everything is great, except it seems that I'm getting some serious lag when coming out of applications or interwebs using the home key. I get 2 or 3 seconds of "loading" and then it fills in. They phone is stock with very little added at this point. I did get the new OTA update right when I activated, so not sure if its an issue with that or not. Is anyone else getting this lag? With the power this phone has, I feel there should be zero lag when doing simple activities... 2 or 3 seconds isn't acceptable. Tried a factory reset... Didn't improve. Any suggestions????

You're experiencing multitasking issues with sense reloads. Rooting can really help with that sort of thing.
Its really too bad you took that OTA, You won't be able to get full S-OFF.
If you aren't the rooting type, changing launchers can help

STIDRIVER said:
Ok guys... coming over from the OG Evo 4G... I love this phone so far. I've had it for about 2 days. Everything is great, except it seems that I'm getting some serious lag when coming out of applications or interwebs using the home key. I get 2 or 3 seconds of "loading" and then it fills in. They phone is stock with very little added at this point. I did get the new OTA update right when I activated, so not sure if its an issue with that or not. Is anyone else getting this lag? With the power this phone has, I feel there should be zero lag when doing simple activities... 2 or 3 seconds isn't acceptable. Tried a factory reset... Didn't improve. Any suggestions????
Click to expand...
Click to collapse
Root it and flash rom htc totally failed with multitasking
Sent from the depths of hell

Thanks for the responses guys... I have rooted/Rom'd my last 2 phones heavily (OG Droid, OG Evo) and am fairly comfortable with it. I guess I just wanted to enjoy this one stock for a while. After running ICS and JB Roms on my old EVO for the last 6 months... It is nice to have everything working at the same time (Netflix, Camera etc...). Plus, Rom'ing seems a little iffy on this Evo so far with reports of actual bricking (yes, I know.. usually user error) and borking Google Wallet. I am decent at this stuff, but I do make my share of mistakes. And seeing as how I bought this phone off eBay (not due for an upgrade), I can't afford to break it. Do you guys think this issue is being addressed by HTC? I hope so......

Rxpert said:
You're experiencing multitasking issues with sense reloads. Rooting can really help with that sort of thing.
Its really too bad you took that OTA, You won't be able to get full S-OFF.
If you aren't the rooting type, changing launchers can help
Click to expand...
Click to collapse
Are there launchers that are more successfull than others for this phone? Apex? Nova?

STIDRIVER said:
Thanks for the responses guys... I have rooted/Rom'd my last 2 phones heavily (OG Droid, OG Evo) and am fairly comfortable with it. I guess I just wanted to enjoy this one stock for a while. After running ICS and JB Roms on my old EVO for the last 6 months... It is nice to have everything working at the same time (Netflix, Camera etc...). Plus, Rom'ing seems a little iffy on this Evo so far with reports of actual bricking (yes, I know.. usually user error) and borking Google Wallet. I am decent at this stuff, but I do make my share of mistakes. And seeing as how I bought this phone off eBay (not due for an upgrade), I can't afford to break it. Do you guys think this issue is being addressed by HTC? I hope so......
Click to expand...
Click to collapse
Supposedly it is but i dont think it has been fully addressed as devs are still making work arounds for it on thw new ota so my guess is yet another fail for htc
Sent from the depths of hell

STIDRIVER said:
Thanks for the responses guys... I have rooted/Rom'd my last 2 phones heavily (OG Droid, OG Evo) and am fairly comfortable with it. I guess I just wanted to enjoy this one stock for a while. After running ICS and JB Roms on my old EVO for the last 6 months... It is nice to have everything working at the same time (Netflix, Camera etc...). Plus, Rom'ing seems a little iffy on this Evo so far with reports of actual bricking (yes, I know.. usually user error) and borking Google Wallet. I am decent at this stuff, but I do make my share of mistakes. And seeing as how I bought this phone off eBay (not due for an upgrade), I can't afford to break it. Do you guys think this issue is being addressed by HTC? I hope so......
Click to expand...
Click to collapse
Clear wallet settings before flashing just to be sure if you're worried about that.
Unlock and root your phone, follow the 1.15 flashing instructions and get cm10, it will feel like a new phone. Well worth any risk (which IMO is low following instructions).
sent from my LTEvo

<shameless self promotion> Check out Dont Panic for clear info pertaining to HBOOT, ROOT, and RECOVERY </shameless self promotion>

I think something might be wrong with your phone. We've taken a dive into these phones the last couple of weeks. I got an EVO Lte first. It came with the newest update. So I rooted, but no s-off, of course. Running stock ROM. Runs great. No complaints, except the multi-tasking, of course. No lags, though.
MIL decided to move into a smartphone and got the same phone a few days ago, with my help. Left it completely stock and worked on it extensively loading apps, configuring it, etc. I notice zero difference between the phones. Same performance, no lag on either one, etc.
P.S. Wife picked up an S3 on Saturday. I'm in charge of setting it up, too. I expected to be realy wowwed by it. But after a couple of days of playing with it, I think I like the Evo better. I like both phones, but I think I made the right choice for me. It would be nice if HTC was as developer friendly as Samsung, though.

Update: Factory reset fixed the lag... it was acting up still right after I did it, which is when I posted the thread. But, after letting it settle for a day or so, its fine. Awesomeness restored. Thanks for the help though, and when the modding bug hits me, I know where to go.

Sometimes after just flashing a new ROM its a good idea to factory reset first, it gets tested for the device intended and released for others but an image is basically a snapshot of the ROM and everything in it, when you factory restore a new ROM, you really start fresh

STIDRIVER said:
Update: Factory reset fixed the lag... it was acting up still right after I did it, which is when I posted the thread. But, after letting it settle for a day or so, its fine. Awesomeness restored. Thanks for the help though, and when the modding bug hits me, I know where to go.
Click to expand...
Click to collapse
I hope you have better luck than I did. The lag came back. So far, minus the last few things that aren't working properly, CM10 is the way to go. It's like a whole new phone. No Lag, smooth as butter, no more waiting for Sense to load, just a much better all around experience. Thanks to Toast and Deck, incredible work!

Still running like a champ... I think the phone was just confused with activation, setup and the evil AirRave that hates all my phones... Factory reset seems to have worked. Trying to hold off on root/rom for now...

continuing on with the Rezound?...

I've had the Rezound for some time now and am actually on my 3rd replacement(issues before with overheating & signal drops). Anyway, the current Rezound I've had for awhile & never bothered unlocking/rooting thinking it'd eventually encounter problems like my previous ones. I finally decided I'd like to tinker with some ROMs but been having a hell of a time getting a recovery to stick/work properly & getting S-OFF(It updated to the most recent ICS not too long ago).
It's now almost 1AM(been at it since around 9PM)... read lot's of guides from multiple forums, tried multiple procedures, etc... & so far only got the phone unlocked and a delightful **TAMPERED*** msg in HBOOT. - although the phone still boots up & functions just fine. I've been having that urge to "throw in the towel" & even as is, someone's offered me $200 for the phone. If I sell it, I can pick up either a GS3 for an extra $100 or a RAZR MAXX HD for an extra $75. I remember the original RAZR's screen bothered my eyes and didn't like the G Nexus I had briefly.
I do have a bit of an attachment to this Rezound but this S-OFF/root bit is really pissing me off now. What would you guys do?
[EDIT] A bit of a glitch there getting Aman Ra loaded but it's done now(still displays tampered in hboot but oh well, it's working anyway...) & have NeoMAX 2.0 installed (still S-ON). Last time I tried tinkering with this phone they only had temp root available. Going to play around with it for awhile now and see how things go. ^_^

S-Off is definitely not mandatory. I have been flashing roms for over a year on my rezound and I am s-on. If you have unlocked bootloader and root your set. You just occasionally need your pc to push the boot.img.

Tampered just means you have a custom recovery installed. Like im_high_tech said, you can flash kernels when you're s-on. If you need help with that, let us know.

voxigenboy said:
I've had the Rezound for some time now and am actually on my 3rd replacement(issues before with overheating & signal drops). Anyway, the current Rezound I've had for awhile & never bothered unlocking/rooting thinking it'd eventually encounter problems like my previous ones. I finally decided I'd like to tinker with some ROMs but been having a hell of a time getting a recovery to stick/work properly & getting S-OFF(It updated to the most recent ICS not too long ago).
It's now almost 1AM(been at it since around 9PM)... read lot's of guides from multiple forums, tried multiple procedures, etc... & so far only got the phone unlocked and a delightful **TAMPERED*** msg in HBOOT. - although the phone still boots up & functions just fine. I've been having that urge to "throw in the towel" & even as is, someone's offered me $200 for the phone. If I sell it, I can pick up either a GS3 for an extra $100 or a RAZR MAXX HD for an extra $75. I remember the original RAZR's screen bothered my eyes and didn't like the G Nexus I had briefly.
I do have a bit of an attachment to this Rezound but this S-OFF/root bit is really pissing me off now. What would you guys do?
[EDIT] A bit of a glitch there getting Aman Ra loaded but it's done now(still displays tampered in hboot but oh well, it's working anyway...) & have NeoMAX 2.0 installed (still S-ON). Last time I tried tinkering with this phone they only had temp root available. Going to play around with it for awhile now and see how things go. ^_^
Click to expand...
Click to collapse
If frustration about the ***TAMPERED*** thing is what is making you think of changing phones, don't worry about that, it's supposed to say that. As shrike mentioned, that's normal. It just means you have a custom recovery on it.
I would keep the Rezzy if you don't want to spend any more money. It's a great phone imho.

feralicious said:
If frustration about the ***TAMPERED*** thing is what is making you think of changing phones, don't worry about that, it's supposed to say that. As shrike mentioned, that's normal. It just means you have a custom recovery on it.
I would keep the Rezzy if you don't want to spend any more money. It's a great phone imho.
Click to expand...
Click to collapse
I am right there with you. The Rezound is great and thanks to the devs just keeps getting better. It is hard for me to justify losing my unlimited data for new phone when this one does all I need it to....and more.

Cerealkillah said:
I am right there with you. The Rezound is great and thanks to the devs just keeps getting better. It is hard for me to justify losing my unlimited data for new phone when this one does all I need it to....and more.
Click to expand...
Click to collapse
Just so you know, you'll only lose your unlimited data if you renew/upgrade. You can buy a phone from a 3rd party and switch out whenever you want & maintain your unlimited.
I have a Galaxy S3 now that I'm using as my primary(and unlimited is still there). The Rezound I've held onto though as a backup & use it as my media player.

He speaks the truth. I had a TBolt and my wife had the Rezound. She hated the proximity issue so we switched (score for me). When I checked with Big Red, they confirmed that I would not lose my unlimited data, so I switched and haven't looked back
voxigenboy said:
Just so you know, you'll only lose your unlimited data if you renew/upgrade. You can buy a phone from a 3rd party and switch out whenever you want & maintain your unlimited.
I have a Galaxy S3 now that I'm using as my primary(and unlimited is still there). The Rezound I've held onto though as a backup & use it as my media player.
Click to expand...
Click to collapse
Sent from my ADR6425LVW using xda app-developers app

Better Mobile App

welcome