Thinking about starting over - EVO 4G General

I think I might RUU back to stock tonight, re-root, reformat my SD Card and just start fresh.
I've done so much to this phone, and I'm starting to see some glitches that I think I can solve by restoring to stock and going form there.
Now, if I can just remember how to run UnrEVOked in Ubuntu....

It does fix a lotta problems
A drop of Chuck Norris's semen was placed on Android OS. We now have CyanogenMod.

Sometimes when my phone used to act a little slow, I'd just wipe cache and dalvik cache and it would go back to normal. Now that I create NAND's every few days and delete the previous one (in case I have to restore my phone, this way my NAND will be as current as possible), I just wipe both caches during the NAND process and I haven't noticed my phone slow down one bit.

dont need to un-root. Just run the format-all.zip twice, flash a rom and reload apps.

One of the glitches is that none of my Nandroids will restore, which is part of why I want to start fresh, so I can have a fresh stock/rooted nandroid, and several of my apps aren't restoring data with Titanium Backup, for some reason.
Now for some reason, and this MAY be ROM related, my Swype stops Swyping, even though I just updated it via the Swype Installer, uhh, several timeas.
One other thing, I originally rooted with the one step root method, which kept freezing up, then UnrEVOked failed in Windows, which is why I did it on my Ubuntu, so right from the start things were a little messed up.
Besides, I can't remember what stock was even like anymore... lol

HipKat said:
Besides, I can't remember what stock was even like anymore... lol
Click to expand...
Click to collapse
I predict you won't like "stock" ... and even if it's tolerable, the urge to slip into that old dark rain coat will be lurking!

lol... 5 mins after Stock, I'll be reaching for a new ROM, I can see it already....
See that's the difference. On the Moment, you almost HAD to restore to stock before flashing a new ROM.
Just seemed like a lot less problems that way.

Related

NO froyo builds are stable on my nexus one.

I'm serious. It's slow everything force closes and I figured now that cyanogen had his new build of Froyo....I could give the kang o rama a try. but everything is still force closing and I have no idea how to fix it and I'm about ready to just give up :/
What do I do?
Are you completely wiping everything before you install a rom?
Give yourself a wipe, or at least a cache partition wipe
Sent from my Nexus One using XDA App
if its slow then something is using a large amount of cpu power.
I just caught Flickie doing it (thanks to CPUStatusLED)....but it stopped before i got to uninstalling it.
Backup your apps, wipe everything data, ext, cache..then install a ROM.
My phone was freezing/rebooting 3-10 times a day before I did the above and now its quite stable.
EVERYTHING has been wiped. Dalvik, cache, Factory reset, everything I could do without doing anything to the SD card.
I'm seriously at a loss for words.
Currently on kang o rama's 2.2 cyanogen build A2 btw is what I'm trying to work with. Though it has been no different for other roms. I Mean it's so unresponsive and always force closes everything
2.1 works ok ?
2.2 doesn't you say? after all wipes and a clean install of Cyanogen and other ROMs? How about stock Froyo FRF91?
It may be a hardware error if the stock one doesn't work. So even if you got an unlocked phone, Google/HTC should replace it because it's hardware. If you're installing it wrong SOMEhow.. then that's another story.
EDIT: NVM believe I found it
I just went through this.
Just download the PASSIMG.ZIP from the latest Eclair build and put it on the root of your SD card. Go into bootloader and it will automatically pick it up.
In a minute you'll be at stock Eclair. By the time you can get into the Settings menu, you'll have the majority of FRF91 downloaded. Let it do its thing and probably within 5 minutes you'll be sitting pretty on a stock FRF91 Froyo build.
http://lmgtfy.com/?q=passimg+eclair
First link
If you've used the Froyo App2SD function, then you might need to delete your .AndroidSecure folder on your SD card after a flash.
I never touched that folder and the last few times I flashed a ROM I was getting weird problems where I couldn't install things, it would hang, I would get FCs, etc. I deleted that folder, rebooted, and everything was cleared up for me.
...Of course you'll have to install those apps again.
mudrock1000 said:
I'm serious. It's slow everything force closes and I figured now that cyanogen had his new build of Froyo....I could give the kang o rama a try. but everything is still force closing and I have no idea how to fix it and I'm about ready to just give up :/
What do I do?
Click to expand...
Click to collapse
Have you installed the latest radio image? Even if you have give it another flash. I had the same problem on my Hero
mindfrost82 said:
If you've used the Froyo App2SD function, then you might need to delete your .AndroidSecure folder on your SD card after a flash.
I never touched that folder and the last few times I flashed a ROM I was getting weird problems where I couldn't install things, it would hang, I would get FCs, etc. I deleted that folder, rebooted, and everything was cleared up for me.
...Of course you'll have to install those apps again.
Click to expand...
Click to collapse
Yea thats a good idea. The short time I've been on Android, it seems like A LOT of CRAP gets brought into new builds. Everytime I flash a new rom, the Market downloads all the crap from before. lol.
While I can see it as being a nice feature, it can get troublesome. When my replacement Nexus comes tomorrow, I'm going to backup my APK files and format my SD card. Start completely from scratch on Froyo 2.2
Usually I have NO problem hunting for things myself...but I DO NOT AT ALL...see this "Passimg" in that thread.
ANYWAYS I'm gonna try reflashing the radio to see if that helps
This is why I just use stock stuff, I want my phone to just work
khaytsus said:
This is why I just use stock stuff, I want my phone to just work
Click to expand...
Click to collapse
Foo Stock dun work .
Anyways good news...I've gone more then a few minutes without it crashing. . I think the radio think might actually have worked.
Wait market crashed. I'm hoping it's just a thing and I'm gonna reboot and try again.
Nope just more Force Closes
Tell me about this passimg.
mudrock1000 said:
Foo Stock dun work .
Anyways good news...I've gone more then a few minutes without it crashing. . I think the radio think might actually have worked.
Wait market crashed. I'm hoping it's just a thing and I'm gonna reboot and try again.
Click to expand...
Click to collapse
And you're sure your N1 isn't defective?
Other then the occasional data connection failure...yea Eclair worked perfectly.
And sriously...guys I need the effing stock rom image I wanna try something else BUT I don't have it.
Oh yea. AND NOW I'm trying to reinstall the apps but it says out of space...and I can clearly see I have 111 mbs of internal storage. I think it's installing it on the SD card. IDK HOW TO MAKE IT STOP and I'm so frustrated I'm about ready to dump my n1. I've been screwing with this forever and I was excited. The first build of Cyanogen and nothing works...
mudrock1000 said:
Other then the occasional data connection failure...yea Eclair worked perfectly.
And sriously...guys I need the effing stock rom image I wanna try something else BUT I don't have it.
Oh yea. AND NOW I'm trying to reinstall the apps but it says out of space...and I can clearly see I have 111 mbs of internal storage. I think it's installing it on the SD card. IDK HOW TO MAKE IT STOP and I'm so frustrated I'm about ready to dump my n1. I've been screwing with this forever and I was excited. The first build of Cyanogen and nothing works...
Click to expand...
Click to collapse
Wipe, install rom, reboot and hold volume down to load the bootloader, power off in bootloade, pull battery, remove microsd, replace battery, boot and set it up. See what happens.
you might just have a faulty hardware (bad ram or something)
norazi said:
you might just have a faulty hardware (bad ram or something)
Click to expand...
Click to collapse
I'm betting it has something to do with data saved on the sd. . .

Froyo runs like junk

Froyo on my wife's phone runs like crap. This is the official update from minikies and it's applied to both my phone and her phone. We did them back to back. On my phone, I did the update and tossed it on the nightstand. On her phone, we did the update and rather than wait for things to "settle out", she started surfing the web, etc, immediately.
Any thoughts?
just do a reset....
As in, what, a reboot? It's been rebooted quite a bit.
Each phone may run different as using it after an update should not affect speed at all. My phone ran butter smooth with JI6 while others reported lag. You may want to wipe all the user data and cache data through the phone's recovery. To access recovery:
Shut down phone.
Hold both volume buttons along with the power button.
When the Vibrant screen comes up release the power button but hold onto the volume buttons.
A blue menu comes up and use the volume buttons to scroll and power button to select.
Keep in mind this will erase all her data and may or may not work.
Try to erase the cache first though(also through recovery). It won't erase the user data but refreshes the phone again. Start up may take a while though.
yeah I had done the cache and the other data wipe. I was seriously hoping to avoid wiping the user data because she's purchased textbooks from third party appstores and I'm not sure if they will live.
So the next question - If we move these apps to the memory card (the textbooks) and then tell the phone to nuke the user data, they will survive the experience or does wiping it also wipe the SD?
tiber said:
yeah I had done the cache and the other data wipe. I was seriously hoping to avoid wiping the user data because she's purchased textbooks from third party appstores and I'm not sure if they will live.
So the next question - If we move these apps to the memory card (the textbooks) and then tell the phone to nuke the user data, they will survive the experience or does wiping it also wipe the SD?
Click to expand...
Click to collapse
There's never a guarantee that no data will ever be lost. To be safe and sure, backup to a computer or backup everything on your external Sdcard and remove it before doing anything.
Keep in mind that RFS(Sammy's file system) will slow down over time and is only fixed in android 2.2.1 (mostly). Your best bet would be to flash a new custom rom with ext4 or just a voodoo kernel but stay stock.
SO FUNNY YOU MENTION THAT. As of 2.2 (the official froyo flash from tmo), Clockwork doesn't install so consequently I can't make voodoo go. It's the 3E bootloader. Also I've had no luck with pushing the 3E fix whomever it was discovered. It simply doesn't take. If there's a workaround, I'm all ears. My first thought was "oh just remount it as RW" and I'm clearly missing something.
Ideas on making voodoo go? That was my low hanging fruit I was trying for initially.
tiber said:
SO FUNNY YOU MENTION THAT. As of 2.2 (the official froyo flash from tmo), Clockwork doesn't install so consequently I can't make voodoo go. It's the 3E bootloader. Also I've had no luck with pushing the 3E fix whomever it was discovered. It simply doesn't take. If there's a workaround, I'm all ears. My first thought was "oh just remount it as RW" and I'm clearly missing something.
Ideas on making voodoo go? That was my low hanging fruit I was trying for initially.
Click to expand...
Click to collapse
Want to install a custom rom. Drop back to 2.1 then flash a custom rom.
Maybe there's something I'm missing here, but if clockwork doesn't work on the phone, how shall I install a different rom - even an older one?
Moot point - I figured out how to get the recovery binary moved to /system/bin on my phone, but the goal was to fix the existing froyo rather than flash a custom rom. If there was a way to drop back to 2.1, I would drop back to 2.1 and then have the tmo official update it. So let me propose something...
Given that I now have 3e recovery doing The Right Thing, I would guess I need to install clockwork, grab the 2.2 Tmobile UKVA6 ROM, then use clockwork to flash that in place. Since I'm flashing from 2.2 to 2.2 and not changing anything, will her user data live through the experience or do these flashes reset the partition with her apps on it?

[Q] google apps failing..even after full whipe of everything.

Okay, I'm here everyday reading this stuff, Id first like to say you guys rock. Everyone here, and the makers of these awesome mods, you have made my phone and my life quit amazing, and less boring like stock!
It seems something is wrong
I sort of switch back and forth between cm and savage zen when each have an update. I love savage zen because of the higher resolution, makes my evo screen crystal clear, while cm is much more stable, and has not only the meat, but the potatoes and gravy, while savage only has the meat
But anyway, no matter what I do, gmail crashes, and media crashes, market doesn't work etc. The google apps in rom manager have worked before, when I was using 2.3.4 I was able to find that google app package somewhere online.
The google apps in rom manager that im thinking of says its compatible with 2.3.3, and well I used it for a few weeks perfectly. Silly me though I'm never satisfied...
I'm running 7.0.3.1, but it seems the google apps that comes with that package has never worked, you know when you check the box for google apps.
So instead I would do it manually, and again I mean it worked fine.
I decided to go back to savage zen, loved it (everytime deleting delvik cache and full wipe)
I think I am missing something...
The order I would do things is, wipe dalvik cache/data, install mod/google apps. I mean that has always worked before just fine. I tried a before and after also, booted it before restoring my data, nothing crashed, it all went smoothly.
In recovery, I go to restore, advanced restore, then restore data. My 2 latest backups both fail. Am I not restoring correctly, oh im sure this is all my fault.
Sorry im sure this has been answered many times over...I found a few threads but they wernt quite what I was looking for because the person I was reading about both times was using cm6, and I think I did the steps correctly..but thats what I'm here for, Please help me fix my bad *** phone.
Quick Update
Okay, so yeah I do still have more to learn. I was thinking well maybe if I just wipe the cache partition....(havnt done that before..just did full wipes)
Is this all my fault? Maybe all this going back and forth is just not good? lol
I figured this out by myself. I went into titanium backup, and wiped the cache of every program that was giving me the error. Done and done. I guess clockwork mod doesn't get rid of all cache?
Well..thanks anyway...I didn't find the fix on google, or anywhere for that matter..It just came to me..
I remember reading comments about how clockwork dosent nandroid wimax keys and does not fully wipe like it should, you should try switching to amon's RA recovery.
I switched to Amon Ra a few months ago. I agree it's way better and it's nice to be able to whipe dalvik cache without waiting a few minutes for it to even get to the right screen, but I have still had a few problems even after dalvik/cache wipe. Titanium backup is a nice way of cleaning things up also, media storage!
That's something I figured out, it was media that kept crashing and it's happened again, but I do flash like a junkie! Always making sure to wipe dalvik/cache and making a nandroid backup before flashing.
Going into settings, applications, media storage then clear data. Works like a charm.
Also once I had 2 ringtones playing when my phone rang...couldn't figure it out and did EVERYTHING. Clearing media storage saved the day.
I think I'm done flashing..may of found my perfect combo
Synergy rls1 + godmode with aggressive freedom kernal.
mmmmm delicious! RLS1 made the phone actually seem to be overclocked before overclocking it (If that makes sense LOL), it ran just as smooth as it did running cyanogen overclocked to 1190. Of course I overclocked it anyway

Newbie needs help/info

I have a T-Mo G2 and want to keep my Froyo image to reinstall later if I cannot get theGingerbread to work right. I want to make an image file that will restore the phone to exactly how it is now. I have tried all kinds of stuff, but am not able to make the "img" file so that I ca do a restore when booting...
Can someone point me to what I need to install to do this, and if possible some directions on what/how to create the "img" or restore file ?
I would be most appreciative, as I had to reverse everything from the OTA of Gingerbread, since too many apps didn't work, ESPECIALLY the GPS!
My current Froyo is a temp-root system.
Thank you all!
Aloha. .
I would do full root via the wiki, and then install 4EXT (the full one that's like $2) - it will keep your old stuff straight
Ditto on previous reply
Root your G2
Backup all your apps with using Titanium backup
Get Clockwork mod ROM manger or 4ext ( I prefer 4ext) and backup your stock rom. You can download new ROM CM7 for first ROM.
If you don't like the ROM you can restore your stock ROM with CWM or 4ext at anytime.
I have a theory that Ti Backup or any backing up of apps is a bad plan. I know you can do it no problem, and that it is a great time saver, but I have a strong feeling that this ultimately results in an unstable phone with mysterious force closes etc.
Even though it's a real pain, I think you are always better off reinstalling your apps from scratch after changing to a new ROM and wiping caches.
WTF? said:
I have a theory that Ti Backup or any backing up of apps is a bad plan. I know you can do it no problem, and that it is a great time saver, but I have a strong feeling that this ultimately results in an unstable phone with mysterious force closes etc.
Even though it's a real pain, I think you are always better off reinstalling your apps from scratch after changing to a new ROM and wiping caches.
Click to expand...
Click to collapse
1. I have had zero problems with TB personally.
2. Without it your app data is gone.
3. Triple wipe, takes a few extra minutes and makes a world of a difference.
4. Do not restore system data!
5. Check md5 sums BEFORE doing anything!!!!
6. Make sure you have a recent nandroid backup and you'll be fine either way.
7. triple wipe before flashing anything including nandroids. Preferably with different wipes aka factory reset, superwipe+ ext4, then recovery wipe!
Just my 2 cents, it's saved my a$$ more then a few times...

learning experience

I did a stupid thing. I got away with it. Pure Nexus running normally now. Questions remain that boil down to this: why wasn't this a much bigger ordeal than it turns out to have been? I'd like to at least learn something when I do a bone headed thing. Here's the sequence of events.
1) 6p, pure nexus 7.1.2, latest vendor etc with twrp 2.8, rooted and running like a champ.
2) fooling around with different apps and so forth, took a look at a couple of dialers that I didn't much like, took them back off. After one of these the stock pure nexus phone app (I think this is just google dialer) started crashing constantly. Restoring titanium backups didn't stop it. Restoring a month old nandroid backup didn't stop it.
3) getting super annoyed (a poor time to start ripping stuff out), I wiped every partition on the phone in twrp except the SD card where all my recovery images and things like SuperSU.zip and some ROMs are stored. Wiped system, data, cache, boot, & dalvik cache.
4) restored a backup image and rebooted. Twrp gave me the no OS warning but I was on automatic pilot, swiped to reboot, and then I was like "what?! No OS! Wtf?" But I had already done the deed. Nothing to do now but wait to see what would happen. I was expecting moderately bad news - like I would end up monkeying with fastboot or adb if I couldn't boot back to twrp and flash the pure nexus image I was pretty sure I still had in storage.
5) result: pretty quickly I was watching the Pure Nexus boot animation so I knew that I was booting Pure Nexus. And this was the case. It took an extra long time like it does on the first boot but then there is was. Welcome. Let's get started. I set the phone back up and replaced most apps from backups and no harm, no foul. Also, the phone app stopped crashing. Bonus.
Now, I have no idea why I got the no OS warning from twrp. I'm sure that if I'd read it before I swiped to reboot and not after, like a bonehead, I would have done something like trying to flash the backup again or even the ROM I have on the SD card. Anything but reboot with the no OS warning on the screen. But the result was the same as if I'd flashed the ROM without, as I think of it now, flashing gapps or SuperSU. I had to go back and flash SuperSU but I put the apps back with titanium backup.
If anyone would like to take a shot at telling me how I got this result I think it might light up a dark area in my just-enough-experience-to-be-dangerous brain. Thanks in advance.
Truechunks said:
I did a stupid thing. I got away with it. Pure Nexus running normally now. Questions remain that boil down to this: why wasn't this a much bigger ordeal than it turns out to have been? I'd like to at least learn something when I do a bone headed thing. Here's the sequence of events.
1) 6p, pure nexus 7.1.2, latest vendor etc with twrp 2.8, rooted and running like a champ.
2) fooling around with different apps and so forth, took a look at a couple of dialers that I didn't much like, took them back off. After one of these the stock pure nexus phone app (I think this is just google dialer) started crashing constantly. Restoring titanium backups didn't stop it. Restoring a month old nandroid backup didn't stop it.
3) getting super annoyed (a poor time to start ripping stuff out), I wiped every partition on the phone in twrp except the SD card where all my recovery images and things like SuperSU.zip and some ROMs are stored. Wiped system, data, cache, boot, & dalvik cache.
4) restored a backup image and rebooted. Twrp gave me the no OS warning but I was on automatic pilot, swiped to reboot, and then I was like "what?! No OS! Wtf?" But I had already done the deed. Nothing to do now but wait to see what would happen. I was expecting moderately bad news - like I would end up monkeying with fastboot or adb if I couldn't boot back to twrp and flash the pure nexus image I was pretty sure I still had in storage.
5) result: pretty quickly I was watching the Pure Nexus boot animation so I knew that I was booting Pure Nexus. And this was the case. It took an extra long time like it does on the first boot but then there is was. Welcome. Let's get started. I set the phone back up and replaced most apps from backups and no harm, no foul. Also, the phone app stopped crashing. Bonus.
Now, I have no idea why I got the no OS warning from twrp. I'm sure that if I'd read it before I swiped to reboot and not after, like a bonehead, I would have done something like trying to flash the backup again or even the ROM I have on the SD card. Anything but reboot with the no OS warning on the screen. But the result was the same as if I'd flashed the ROM without, as I think of it now, flashing gapps or SuperSU. I had to go back and flash SuperSU but I put the apps back with titanium backup.
If anyone would like to take a shot at telling me how I got this result I think it might light up a dark area in my just-enough-experience-to-be-dangerous brain. Thanks in advance.
Click to expand...
Click to collapse
Why are you still using TWRP 2.8? 3.11 is the latest version now. Not sure if it's related or not though.
My bad. That's the SuperSU version. TWRP is the latest. 3.1.1
Moderator Information,
Thread closed at OP's request.

Categories

Resources