Database Info

FC on any rom i use!

i been switching roms like CRAZY to find a stable one. i like the CM6 vanilla, Fresh 2.4.0, and NFX-Hero 2.2.1. those are my fav ive tested so far, ive tested several others as well.
I'm using RA-Heroc-v.1.5.2 Recovery mode. i have tried the clockwork recovery(that CM6 gives me) but its too buggy for me and annoying to use with so many unorganized things.
no matter what rom i use or either of those 2 recovery modes I've used. everything always force closes on the 2nd day of use. if anyone can give me tips of what i should do or what im doing wrong.

try this
http://forum.xda-developers.com/forumdisplay.php?f=650

lol....That was kinda messed up

do you wipe data, cache and ext?
you can try reformatting your sdcard and flashing fresh

ive deleleted all. there was like 5 things i can wipe i wiped em all. data, cache, ext, battery, rotate. still have issues.
edit: ive tried 3 diffrent SD cards. formatted em like 5 times each to see if i had any issues.

Wipe your davlik cache. You may have to ruu...
Sent from my HERO200 using XDA App

done that a few times as well. gone back too 2.31.651.5 and re rooted about 10 times. cause i didn't know how to get back to RA-heroc-v1.5.2 any other way.

kyhassen said:
done that a few times as well. gone back too 2.31.651.5 and re rooted about 10 times. cause i didn't know how to get back to RA-heroc-v1.5.2 any other way.
Click to expand...
Click to collapse
Hmm. Sorry I can't help. I've had similar problems but starting fresh usually fixes them.
Sent from my HERO200 using XDA App

billodell said:
Hmm. Sorry I can't help. I've had similar problems but starting fresh usually fixes them.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
k well ty for trying

Your welcome:0)
Sent from my HERO200 using XDA App

i noticed a few diffrent ways to root the phone. would this one be why im having so many issues.
http://www.machackpc.com/featured/how-to-root-your-cdma-htc-hero-running-android-2-1-windows/

you might ruu your phone back to .5 and then from your phone go to unrevoked.com or do a search in market for 1-click root. Read HERE about it. IDK if thats why, but have you tried fix apk UID mismatches. I think its found under Other in amonRA recovery.

i will try those ideas tomorrow. thank you. i heard of the 1-click root. but i heard its a virus and could possible ruin your phone, i could be wrong but its just a something i saw.

kyhassen said:
i will try those ideas tomorrow. thank you. i heard of the 1-click root. but i heard its a virus and could possible ruin your phone, i could be wrong but its just a something i saw.
Click to expand...
Click to collapse
I think that the exploit it uses can also be used by malicious apps ice it is used to root. Don't think its a virus though
Sent from my HERO200 using XDA App

[Q] Wifi Error

Sorry if this has already been posted.
My phone is rooted on stock rom.
It started freezing up and wouldnt send text messages. GO sms locked me out. I had to take the battery out and restart several times. Now i cant connect to any wifi. In wifi settings it just says error. Any ideas what could be wrong?

your best bet is probably to flash back to stock OS...i dunno if there is a one click for inspire
or you could flash a rom :]...this was probably a weird glitch that would go away with a simple full flash

Why not start with doing a factory reset?
Sent from my Desire HD using XDA Premium App

I think he already did that, but if that doesn't work, try restoring your entire phone to stock...idk if there is a one click Odin for inspire like there is for Galaxy S models

Thats what I was thinking about doing. Will try that this weekend when I have time. Thanks!

henry.menzies said:
Thats what I was thinking about doing. Will try that this weekend when I have time. Thanks!
Click to expand...
Click to collapse
There's a guide stickied to this section that believe has the link to the RUU, which is what you might try, though I think going the RUU route will unroot you.
Inspired Ace 1.0.1¦ XDA Premium

Full wipe reflash should do it.
Sent from my HTC Desire HD using XDA App

yep I would try wipe data/factory reset, wipe cache, wipe delvik cache and a clean install of the rom

Flashed CoreDroid didnt fix the problem

would flashing a new radio fix the problem?

Did you have any luck with this? Im having the same issue and debating whether or not I should flash back to stock to see if this resolves the issue. I have flashed countless ROMs since root with no luck.

My phone is doing the same thing. Not sure when it started doing it since I don't use wifi often. I wanted to check for updates and the HTC one requires WIFI be on, thats how I found out.
My phone is completely stock, with only Apps installed. Factory reset made it say something about connecting for 10 seconds or so before saying error, and now once again it just says error every time i try to enable it.

Synergy rom

What would happen if I didn't wipe before flashing? And do I need to flash the 12.2 kernel
Sent from my SCH-I535 using xda app-developers app

I'm not sure what would happen. It would probably be less stable or not work... You could always try it though.
You do not need to flash any kernel. Only flash LeanKernel if you want to. If you don't want to mess with BusyBox, I'd wait on the kernel.
Sent from my SCH-I535 using Tapatalk 2

From my experience on other devices when flashing ROMs and not wiping I would almost always bootloop. Again that is my general experience. I would assume there would be similar results.
Sent from my SCH-I535 using xda premium

I usually backup the current ROM first, then factory reset before wiping cache. I end up with good results that way. The only time I installed a ROM without wiping, it was unstable.

Well, I tried flashing it, and it seemed to work. This is without the wipe.. But the only thing I found incorrect was that the wifi notification didn't go away. That was an easy fix though.
Should the battery life be noticeably better?
Sent from my SCH-I535 using xda app-developers app

Yeah I was kind of retarded the other day and forgot to wipe.:laugh: I was greeted with a nice bootloop until I pulled the battery and tried again (this time the correct way) then everything worked great..

I haven't wiped for any of the Synergy builds and my phone is running great Running Imos kernel too. Awesome battery life from this thing

So.. Even though I didn't get a boot loop after flashing without the wipe... Do you guys think I should just wipe and flash again?
Sent from my SCH-I535 using xda app-developers app

I'm by no means an expert on the subject, but I'd say if it's working then leave it be..

ahlexkim said:
So.. Even though I didn't get a boot loop after flashing without the wipe... Do you guys think I should just wipe and flash again?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
A wipe may not be completely necessary but if you do run into problems (FCs, etc.) and post a problem the devs or users are going to ask if you did a full wipe or not - and then recommend that you do one. In the end it wouldn't hurt to wipe even if you are fully functional.
I used to hate wiping all the time but with the proper backup applications it doesn't take long at all. I use Titanium Backup to backup apps and then also do in app backups for specific things like nova launcher, minimalistic text, and gosms,

Google now issues

Okay, my issues started when I switched to the baked rom. I had gotten google now working fairly well on ICS. After I switched the voice recognition just hears me as background noise. It will listen then just go back to the tap the mic to speak screen. No searching. No crashing. Nothing. I even tried switching to cyanogenmod 10. Exact same issue. I think the offline voice files might be corrupted. Does anyone know if I might be right and if so how I can delete them?
P.S.- I always do a clean install. Factory reset, clear data in CWM, clear cache (for redundancy), clear dalvik cache.
Thank you in advance.
sincerely
- Someone clearly missing something obvious.

I know that in CM10 they say the issue is because its using the mic on the top of the device instead of the one on the bottom, and the top one is normally for noise cancelling. Try speaking into the mic at the top and see if it helps. Beyond that I can't give you any help.

I tried your idea. Nothing. Did ANOTHER clean install. Nothing. Did your idea with the clean install. Worked like a charm. Thanks!
Sent from my SCH-I535 using xda app-developers app

jlm123hi said:
I tried your idea. Nothing. Did ANOTHER clean install. Nothing. Did your idea with the clean install. Worked like a charm. Thanks!
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
You are still dirty flashing. A clean flash involves formatting system. That is where old rom is located and why phone will reboot after factory reset, dalvic and cache wipe. A clean wipe will not boot since there is no longer an OS/ROM on device.

I know what a clean install is. I have been doing it. I tried his idea AFTER I did another clean install and it worked fine.
Sent from my SCH-I535 using xda app-developers app

What prdog1 is telling you is that you are actually not doing a clean install. Factory reset/data does not remove the original rom partioned on your sd. In order to have a true clean install you need to go into mounts+storage and format the system. That removes the old rom so flashing the new one is truly a clean install. Your technically doing a dirty flash still, which is generally fine when loading the same rom base.
Sent from my YP-G70 using xda premium

Oh. That helps to explain him better. Wow I've been doing it wrong for years. Lucky for me this is the first time I've had problems. Thanks for the info!
Sent from my SCH-I535 using xda app-developers app

jlm123hi said:
Oh. That helps to explain him better. Wow I've been doing it wrong for years. Lucky for me this is the first time I've had problems. Thanks for the info!
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
This is the reason many people have problems that the majority don't have. Flashing different rom bases on top of each other can corrupt the rom and no one can troubleshoot the answer unless it is a rom bug that the majority has. Factory reset, cache and dalvic wipes help eliminate apps and data problems.

[Q] Any way to recover lost EFS?

Ok, so I probably know the answer to this already :crying:
Brief story - stock rooted ROM with custom kernel. Made backup with TWRP. Flashed stock boot,img and system.img in fastboot, flashed downloaded update from 4.4 -> 4.4.2 in recovery. Wiped cache and dalvik - started but recovery locked up. Had to hold power to reboot phone. Booted fine but no network, no IMEI, no baseband.
And no I don't have and EFS backup
I take it the phone is now buggered.
Is there anything I can do to fix this??
Appreciate anything that might help this.

Cheesy Wotsit said:
Ok, so I probably know the answer to this already :crying:
Brief story - stock rooted ROM with custom kernel. Made backup with TWRP. Flashed stock boot,img and system.img in fastboot, flashed downloaded update from 4.4 -> 4.4.2 in recovery. Wiped cache and dalvik - started but recovery locked up. Had to hold power to reboot phone. Booted fine but no network, no IMEI, no baseband.
And no I don't have and EFS backup
I take it the phone is now buggered.
Is there anything I can do to fix this??
Appreciate anything that might help this.
Click to expand...
Click to collapse
The same thing happened to me. Flash the latest version of TWRP, wipe your cache again, and your phone will be back to normal.

not true for all you may end up having to RMA I had my efs backup it still didn't fix it sorry to be the bearer of bad news but they make it sound like bringing it back is 100% but in some cases that's not true
Sent from my Nexus 4 using xda app-developers app

ddloco said:
not true for all you may end up having to RMA I had my efs backup it still didn't fix it sorry to be the bearer of bad news but they make it sound like bringing it back is 100% but in some cases that's not true
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
In his case, if he just does what I said to do he'll be fine. He didn't lose his EFS, he rebooted in the middle of a cache wipe and his partitions got messed up. Updating TWRP and wiping the cache again will set everything straight. This is a fairly common issue with older versions of TWRP.

_MetalHead_ said:
In his case, if he just does what I said to do he'll be fine. He didn't lose his EFS, he rebooted in the middle of a cache wipe and his partitions got messed up. Updating TWRP and wiping the cache again will set everything straight. This is a fairly common issue with older versions of TWRP.
Click to expand...
Click to collapse
I'm just saying the same thing happens to me and nothing that's suggested fixed it that's why I say its not 100% me and another guy both had the same problem and the only way was to RMA I also had my efs but even after doing everything from going back to stock updateubg twrp and reflashing my esf backup my phone would not correct its self so I'm not saying that this method doesn't work for some people but for me and another used it was a no go

So why are you guys still using twrp if it is causing issues?
Just use cwm instead!
Sent from my Nexus 5 using Tapatalk

Elisha said:
So why are you guys still using twrp if it is causing issues?
Just use cwm instead!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
because the majority dont have any problems.
and people, take precautionary measures and back up your efs partition, its the first thing i did as soon as i had a custom recovery. it takes 2 seconds. and store it somewhere OTHER then your phones internal storage, like on a comp or dropbox

TheAtheistOtaku said:
because the majority dont have any problems.
and people, take precautionary measures and back up your efs partition, its the first thing i did as soon as i had a custom recovery. it takes 2 seconds. and store it somewhere OTHER then your phones internal storage, like on a comp or dropbox
Click to expand...
Click to collapse
This is not an EFS issues. Simple matter of twrp messing up partitions.
Sent from my Nexus 5 using Tapatalk

Elisha said:
This is not an EFS issues. Simple matter of twrp messing up partitions.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
i know, still doesnt hurt to be caution though

ddloco said:
I'm just saying the same thing happens to me and nothing that's suggested fixed it that's why I say its not 100% me and another guy both had the same problem and the only way was to RMA I also had my efs but even after doing everything from going back to stock updateubg twrp and reflashing my esf backup my phone would not correct its self so I'm not saying that this method doesn't work for some people but for me and another used it was a no go
Click to expand...
Click to collapse
Yeah but did it happen to you the way it happened to OP? So far every single person that I have come across who was in this boat due to a bad cache wipe in TWRP was able to fix it by updating TWRP and re-wiping the cache. It's a well known issue.

_MetalHead_ said:
Yeah but did it happen to you the way it happened to OP? So far every single person that I have come across who was in this boat due to a bad cache wipe in TWRP was able to fix it by updating TWRP and re-wiping the cache. It's a well known issue.
Click to expand...
Click to collapse
Thanks for the help guys. Got it up and running again more by accident than anything. Seems like MetalHead was correct, the partition was fine but just not readable. Unfortunately in order to get up and running again I flashed all the stock images in flasboot and did a full factory reset in the stock recovery which fixed the problem. Sounds like I could have done without the full wipe after all but at least it's all fixed now.
As for backing up the EFS, lesson learned. I had the 1st official TWRP on the phone which had no option for EFS backup like the current one. Guess what I'll be doing right now??
Anyway, happy man again and thanks to all that replied :good:

I must apologize for saying its not 100% but the truth is I had the exact same thing happen and no stock or fast boot cache fixed it I'm living proof that it works for the masses but under rare circumstances this just doesn't solve it oh man how I wish this would've fixed mine I been using a inspire 4g its killing me I feel like I jumped out of a beemer and landed in a pinto lol
Sent from my Nexus 4 using xda app-developers app

Glad that the OP got the issue resolved !
on a side note , can anyone tell me what is the safest version of TWRP there ? i.e without this cache wipse issue ( taking too long to wipe ? )

ddloco said:
I must apologize for saying its not 100% but the truth is I had the exact same thing happen and no stock or fast boot cache fixed it I'm living proof that it works for the masses but under rare circumstances this just doesn't solve it oh man how I wish this would've fixed mine I been using a inspire 4g its killing me I feel like I jumped out of a beemer and landed in a pinto lol
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Thats a bummer man. What kind of phone are you using now?
Lowresolution said:
Glad that the OP got the issue resolved !
on a side note , can anyone tell me what is the safest version of TWRP there ? i.e without this cache wipse issue ( taking too long to wipe ? )
Click to expand...
Click to collapse
I believe 2.6.3.4 is the latest version. That's the one I'm on, works just fine.
Sent from my Nexus 5 using XDA Premium 4 mobile app

_MetalHead_ said:
Thats a bummer man. What kind of phone are you using now?
I believe 2.6.3.4 is the latest version. That's the one I'm on, works just fine.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Got it , thanks mate Just upgraded my version of TWRP .

the nexus 4 is my phone I gave to my wife now that its hers I'm lucky to pick it up just to hop on xda but when its her Facebook time she hurrie up and kick me off lol the phone I'm using is an HTC inspire 4g it sucks
Sent from my Nexus 4 using xda app-developers app