Database Info

[ROM]Liberated Aria 2.2.2

Liberated Aria 2.2.2 final
This is a moderately modified version of the stock HTC Aria AT&T Android 2.2.2 ROM. It has root, busybox, ro.secure=0 and some nice root utils (Superuser, etc.) and the stupid AT&T bloat has been removed. It also features a kernel that supports overclocking and has a few other tweaks to make it more efficient. This is a great rooted replacement for the stock ROM if you like HTC Sense, otherwise, Cyanogen has a very good CM7 version for the aria. You might like that better.
At this point in time, it is unlikely that HTC will offer any official updates for Aria. I consider Aria orphaned by HTC and this is probably going to be my last "Liberated" update for the Aria unless some bugs are found in this release.
[update] 11-Jan-2012: No CIQ in this ROM.
http://hoxnet.com/droid/hoxnet_aria_liberated_final.zip
MD5: 9f94eabd90d08563397bb26d95a859d0
Copy this to your SDCard and install via recovery. All caveats apply: backup with nandroid and titanium first. Delete cache and dalvik. Should install fine over existing data partitions, but it never hurts to have a titanium backup of your market apps to be sure.
Some users are having issues with installing this over an existing FR008 or R012. I have tried it several ways and it has worked for me, but if you get a boot loop, then you will probably have to do a data wipe to get this to work. If you must wipe data, you can use Market apps like MyBackup, Titanium Backup or Astro to backup all your apps to minimize the fallout from a data wipe.

Gene Poole said:
I don't know if ATTN1 is going to get us a decent liberated 2.2 based ROM anytime soon, but I've managed to get together a basically stock ROM based on the newest HTC release today. It's been properly rooted with Superuser.apk and /system/bin/su as well as busybox. It's just the system partition and seems to work out fine with my existing FR008 data partition so you should be able to keep all your apps as is, but do a nandroid and a Titanium backup to be sure.
I've also used the hoxnet OC kernel with this ROM and it works out OK as-is.
I threw this together pretty quick just to get it out there in the wild so feel free to critique it for improvements.
I'm uploading it to my hosting service and as soon as it's uploaded, I'll post a link.
Click to expand...
Click to collapse
Thanks Gene, you are the man! I'm in the process of downloading all the HTC Kitchen bits to start trying to play with it myself.

can anyone confirm if they configured adobe to work with Aria Froyo? I know it doesn't work for the new HTC Gratia so I was just wondering. Thanks

bigwavesurfer4 said:
can anyone confirm if they configured adobe to work with Aria Froyo? I know it doesn't work for the new HTC Gratia so I was just wondering. Thanks
Click to expand...
Click to collapse
Adobe what?
Sent from my HTC Liberty using XDA App

bigwavesurfer4 said:
can anyone confirm if they configured adobe to work with Aria Froyo? I know it doesn't work for the new HTC Gratia so I was just wondering. Thanks
Click to expand...
Click to collapse
If your referring to adobe flash then no. Our arias hardware can only run flash light.. sometimes not even that
Sent from my Liberty using Tapatalk

bigwavesurfer4 said:
can anyone confirm if they configured adobe to work with Aria Froyo? I know it doesn't work for the new HTC Gratia so I was just wondering. Thanks
Click to expand...
Click to collapse
But if you're talking about acrobat, then according to htc then yes, they replaced pdf reader with adobe's version.
Sent from my HTC Liberty using XDA App

Gene Poole said:
I don't know if ATTN1 is going to get us a decent liberated 2.2 based ROM anytime soon, but I've managed to get together a basically stock ROM based on the newest HTC release today. It's been properly rooted with Superuser.apk and /system/bin/su as well as busybox. It's just the system partition and seems to work out fine with my existing FR008 data partition so you should be able to keep all your apps as is, but do a nandroid and a Titanium backup to be sure.
I've also used the hoxnet OC kernel with this ROM and it works out OK as-is.
I threw this together pretty quick just to get it out there in the wild so feel free to critique it for improvements.
http://hoxnet.com/droid/hoxnet_liberated_hfr001b.zip
Click to expand...
Click to collapse
I'm sure that technically attn1 is still the lead aria dev but I really think that the inspire is his main focus now. Just keep on with what you're doing. And if you ever need a really brave but maybe a little bit green tester... I'm your man

Running your ROM, and all seems well so far! I upgraded from 2.1, didn't wipe data (just dalvik) and everything was there just like it was.
I see that there is now an option for installing non market apps in the app settings area.
Also ended up with more free space :-D
Looking forward to playing with everything!
Thanks for getting this out!
Edit: only problem so far is the darn market-google-not trusting-htc/att-fingerprint that was seen in the previous update. so I can't see the protected apps. not the rom's fault though.
Any trusted fingerprints out there for this version? does the version matter? should I just put the original 2.1 pre-all updates fingerprint back?
Sent from my HTC Aria using XDA App

So I installed this with a full wipe on my wife's phone and I'm surprised that all the neat features that the Gratia had seem to be available in this version stock. Sideloading, wired Tether, hotspot. I thought I'd be working hard to port over the stuff we want from the Gratia/FRxxx. Am I missing something here, or is AT&T finally being a decent carrier? Does anyone know anyone who did the full RUU update?

Gene Poole said:
So I installed this with a full wipe on my wife's phone and I'm surprised that all the neat features that the Gratia had seem to be available in this version stock. Sideloading, wired Tether, hotspot. I thought I'd be working hard to port over the stuff we want from the Gratia/FRxxx. Am I missing something here, or is AT&T finally being a decent carrier? Does anyone know anyone who did the full RUU update?
Click to expand...
Click to collapse
You still have all that because you didn't wipe data/factory reset. In stock trim, a clean install with this rom will result in disabled sideloading, and it will set up a proxy in the APN that with require a tethering plan to use tethering features.
AT&T is still up to it's tricks.

attn1 said:
You still have all that because you didn't wipe data/factory reset. In stock trim, a clean install with this rom will result in disabled sideloading, and it will set up a proxy in the APN that with require a tethering plan to use tethering features.
AT&T is still up to it's tricks.
Click to expand...
Click to collapse
But I did do a data wipe/factory reset on my wife's phone--at least I think I did. It came up with the HTC setup wizard just like a full wipe.

Gene Poole said:
But I did do a data wipe/factory reset on my wife's phone--at least I think I did. It came up with the HTC setup wizard just like a full wipe.
Click to expand...
Click to collapse
Well, when I installed a stock version of the release, the sideloading checkbox was disabled. So we have some oddness here.
I think you can get around the tethering plan issue by setting up a new custom APN without the new "proxy" settings pointing to AT&T's proxy. You can't just delete the setting in the provided default APN because it's locked.
We'll see how long that little hack lasts - they could require that proxy setting for data to work at all in the future, and that would kill free tethering on even unbranded firmware.
So far, I am not impressed with this official 2.2.2 AT&T ROM release at all. It gets us nothing and the branding tricks run even deeper.
I've been following your kernel work. Nice work there.

Thanks. I'm with you on this. It doesn't give us anything that wasn't already in FR008. I haven't tried the radio image yet. Anything to be gained (or lost) there? Also, I'm thinking of doing the full RUU for testing. If I do, can I still run the older RUU exe to put it back to a version that I can root with unrevoked, or will a RUU exe run over a newer version (or does it even check)?

attn1 said:
I've been following your kernel work. Nice work there.
Click to expand...
Click to collapse
Nothing but patches from your work on cyanagen.

Gene Poole said:
Thanks. I'm with you on this. It doesn't give us anything that wasn't already in FR008. I haven't tried the radio image yet. Anything to be gained (or lost) there? Also, I'm thinking of doing the full RUU for testing. If I do, can I still run the older RUU exe to put it back to a version that I can root with unrevoked, or will a RUU exe run over a newer version (or does it even check)?
Click to expand...
Click to collapse
No, please don't do that (install the new update unmodified). You will end up with a device you can't put custom recovery on. The newer hboots closes the old nand exploit, and you can't downgrade it. You won't be able to get to custom recovery again, in which case, you'd better really be liking the new stock ROM.
on the radio; I don't know, I flashed it because I can. I really didn't see anything earth-quaking yet. We should probably bundle it up so people can flash that without going to the updated and losing custom ROM capability.

What do you think the chances are that they'll crack the new hboot? I will be very dissapointed if new HTC devices become un-rootable/extremely hard to root.
Sent from my Liberty using XDA App

terwine said:
What do you think the chances are that they'll crack the new hboot? I will be very dissapointed if new HTC devices become un-rootable/extremely hard to root.
Sent from my Liberty using XDA App
Click to expand...
Click to collapse
50/50? Newer, hotter devices will always get more attention and maybe this hboot will get a trickle down benefit from that - but then again, maybe not.

Gene,
thank you for such a great contribution; just a quick question: how did you manage to extract the contents out of the .exe file ?

loursonbrun said:
Gene,
thank you for such a great contribution; just a quick question: how did you manage to extract the contents out of the .exe file ?
Click to expand...
Click to collapse
When you run the exe they extract to a folder in your temp folder. clear out your temp folder then run the exe and you will see the extracted contents (like the rom.zip) in the folder.
At least this is what I did for my Incredible, I doubt they changed it up any.

That's essentially what I did.

NS4G Clockwork recovery not backing up 4G keys

I don't normally like to post in development but I thought this needs some attention. I thought that I read that clockwork recovery was not backing up the 4G keys when doing a nand. If this is true flashing custom roms can be a bit risky because if you have a problem and loosed your keys you are screwed = no more 4g.
This was a problem for a long time on the evo with clockwork recovery many people flashed roms, would have some issue and would loose their 4g keys. Than they would flash back to a nand backup only to find out that clockwork had not backed up the keys in the nandroid. I also check my nand backup I was not able to find my wimax keys and this can be a big problem if you like using 4G.
This is what I have seen I could be incorrect but I don't think I am. Is there a way to have clockwork create a recovery specifically for the NS4G that would address this?

First of all, you are probably not running the right recovery. Secondly, the right recovery does not work at this time lol (broken keymaps). I spoke to Koush tonight and he is fixing the Nexus S 4G recovery, it should be done by tomorrow. If you are running the crespo recovery that is for the regular Nexus S, he will release one that has crespo4g in the filename, that is the one you need. After he releases that it may backup what you speak of. As of now there is no official Nexus S 4G recovery.

well actually there is. just the keymaps are broken

shabbypenguin said:
well actually there is. just the keymaps are broken
Click to expand...
Click to collapse
Exactly. Check here for the latest one: http://mirror.sea.tdrevolution.net/cm/recoveries/
* The one dated May 12th is the broken one.

yea i made the mistake of flashing it and quickly found out that it wasnt a good idea

shabbypenguin said:
yea i made the mistake of flashing it and quickly found out that it wasnt a good idea
Click to expand...
Click to collapse
Did the same lol. He doesnt have one to test it on so we were the guinea pigs.

[Q] Can anyone answer this?

I am coming from Evo 4G & early on there was a problem with clockwork recovery & wimax & a lot of people lost their RSA keys because of clockwork. I am just wondering if I risk losing my RSA keys if I restore to my nandroid of my rooted stock Rom. Is 4G different on the NS4G then on Evo? I am scared to restore, but I really want to until CM7 is more polished for the NS4G.
If you don't know the answer please tell me if you have restored a nandroid using Clockwork recovery on the NS4G and then connected to 4G afterward. This would ease my mind before restoring. I guess I could just flash a stock rooted Rom and wait for the AmonRA port to be finished.
Sent from my Nexus S 4G using XDA Premium App

Please answer if you know or if you have restored without losing 4G. Thanks in advance.

housry23 said:
Please answer if you know or if you have restored without losing 4G. Thanks in advance.
Click to expand...
Click to collapse
i have done many cwm restores and my 4g still works. i dont know anything about rsa keys, but mine is still working.

I do not know the answer to your question because I have the T-Mobile version but I used to have an Evo on Sprint so I am familiar with backing up WiMax being necessary due to RSA Keys stored in the WiMax image.
This thread should let you make a standalone WiMax img backup:
http://forum.xda-developers.com/showthread.php?t=1074584&highlight=wimax
The resulting image you can keep and can be flashed to your WiMax partition in case anything ever goes wrong in that regard.

Thanks matt2053. Went to thread and made a backup. This is exactly what I was looking for. Much appreciated. I am sure Clockwork has fixed this issue, but I always like to be on the safe side.

The truth about version of CWM and your ROM

There have been many people wondering whether or not the version of clockworkmod recovery will be compatible with certain roms. Clockworkmod has no affect on the ROM whatsoever so you can be on 5.0.2.7, touch recovery 5.5.0.4, touch recovery 5.8.1.3, etc. and you can install any rom from within those recoveries. It makes absolutely no difference what recovery you are on. Every recovery above CWM 3.0 uses edify scripting (which is what is needed for all roms above android 2.0). So if anyone tells you that you need a certain recovery to flash ICS or GB they are wrong. All Clockworkmods are compatible with ALL ROMS.

I concur. Ive tried all 3 and ive had no issues. I think some folks state to use certain ones because thats what they used and they didnt have any problems, so they keep telling everyone to do what they did.
As with any Rom load, all issues arise or dont arise based on how well you cleaned the slate before applying the ROM.
Dixit

Good to hear this re-affirmed. I am having problems flashing .zip's in CWM and know for sure it's not the version!

randomtask16 said:
Good to hear this re-affirmed. I am having problems flashing .zip's in CWM and know for sure it's not the version!
Click to expand...
Click to collapse
what issues are you having? right away the first thing i would try is downloading the rom again as you may have had a corrupted download.

From personal experience I have had a ton of issues before I ODINd the 5.5.0.4 recovery. Prior to that I was running the 5.8.1.3 and I was having a ton of issues flashing some of the roms. I don't have any proof of errors or anything but I'm certain that Appdroid will be willing to vouch for me right now.
~PsyCl0ne

I've tried them all without any major issues except for one. Flashing ROMS is one thing but the overall functioning of all the tools within seem to differ. Permissions for example work on some and not on others. They do differ overall but I agree flashing a ROM isn't an issue. Everyone has their preference and if a developer says to use a particular version, there is a reason. I'll ask you since your the expert, do the wipes and cache clears work the same way?
Sent from my SAMSUNG-SGH-I727 using xda premium

Maybe someone can tell me what's wrong with my setup, I'm on Superlite 5.0 with ROM Mgr v5.0.0.6. I can only boot into CWM (Touch 5.8.1.3) from ROM mgr and nothing else. It's not a major deal but I can't go directly to backup, restore e.g. like I used to with a GB rom.

bdbx18 said:
Maybe someone can tell me what's wrong with my setup, I'm on Superlite 5.0 with ROM Mgr v5.0.0.6. I can only boot into CWM (Touch 5.8.1.3) from ROM mgr and nothing else. It's not a major deal but I can't go directly to backup, restore e.g. like I used to with a GB rom.
Click to expand...
Click to collapse
I dont use Rom Manager, you wont find alot that use it for those functions either as its essentially passes that request off to CWM when its rebooted. So Id suggest just rebooting to recovery using the toggle panel in Superlite, then in the CWM touch, just backup, restore, do anything.
Dixit

bdbx18 said:
Maybe someone can tell me what's wrong with my setup, I'm on Superlite 5.0 with ROM Mgr v5.0.0.6. I can only boot into CWM (Touch 5.8.1.3) from ROM mgr and nothing else. It's not a major deal but I can't go directly to backup, restore e.g. like I used to with a GB rom.
Click to expand...
Click to collapse
Are you saying that if you power down and use the three-button combo it doesn't work? (ie volume up+volume down+power)
If this is the case you may want to try using Odin to flash recovery again (found in the Fix Soft Brick or in the rooting thread...)

skrambled said:
Are you saying that if you power down and use the three-button combo it doesn't work? (ie volume up+volume down+power)
If this is the case you may want to try using Odin to flash recovery again (found in the Fix Soft Brick or in the rooting thread...)
Click to expand...
Click to collapse
For my phone I don't have to hold power when booting up. I just hold both volume buttons till I see the recovery menu.
~PsyCl0ne
Sent from my SAMSUNG-SGH-I727 using XDA

PsyCl0ne said:
For my phone I don't have to hold power when booting up. I just hold both volume buttons till I see the recovery menu.
~PsyCl0ne
Sent from my SAMSUNG-SGH-I727 using XDA
Click to expand...
Click to collapse
This is exactly how I get into recovery on my AT&T phone. Holding three buttons just causes it to reboot over and over again

skrambled said:
Are you saying that if you power down and use the three-button combo it doesn't work? (ie volume up+volume down+power)
If this is the case you may want to try using Odin to flash recovery again (found in the Fix Soft Brick or in the rooting thread...)
Click to expand...
Click to collapse
What I meant is that I used to do for e.g. 'Backup current rom' from ROM mgr, name it accordingly, and it will reboot into CWM and backup with that name. Now it just reboots to CWM main panel and sits there. Even the timestamp on the backup file is off.

PsyCl0ne said:
For my phone I don't have to hold power when booting up. I just hold both volume buttons till I see the recovery menu.
~PsyCl0ne
Sent from my SAMSUNG-SGH-I727 using XDA
Click to expand...
Click to collapse
Oh yes, you're on rogers. I thought rogers users had to hold volume down only+power button to get into recovery (ie no volume up key involved). I've seen many rogers users say that...
---------- Post added at 10:20 PM ---------- Previous post was at 10:15 PM ----------
bdbx18 said:
What I meant is that I used to do for e.g. 'Backup current rom' from ROM mgr, name it accordingly, and it will reboot into CWM and backup with that name. Now it just reboots to CWM main panel and sits there. Even the timestamp on the backup file is off.
Click to expand...
Click to collapse
Oh! Now I get it. I have had weird issues with ROM Manager ever since I had this phone. Backup via ROM Manager worked a couple times on gb roms but then it started doing what you described. Ever since it started doing that I just backup from cwm, and then go back in with Root Explorer to re-name the files so I know what's what...

Can't you just boot straight to recovery from most roms as well as from rom manager if you were on a rom that didn't have that ability? I can't remember the last time I had to press buttons to get into recovery, I'm not saying it's not useful to know, but merely stating that it's highly unnecessary in most cases to ever have to touch the buttons for recovery.

sk8erwitskil said:
There have been many people wondering whether or not the version of clockworkmod recovery will be compatible with certain roms. Clockworkmod has no affect on the ROM whatsoever so you can be on 5.0.2.7, touch recovery 5.5.0.4, touch recovery 5.8.1.3, etc. and you can install any rom from within those recoveries. It makes absolutely no difference what recovery you are on. Every recovery above CWM 3.0 uses edify scripting (which is what is needed for all roms above android 2.0). So if anyone tells you that you need a certain recovery to flash ICS or GB they are wrong. All Clockworkmods are compatible with ALL ROMS.
Click to expand...
Click to collapse
You are absolutely correct. That is why I have not required any specific recovery, but told people what I use. yours . But, there is a caveat, since flashing a full rom requires reliable wipe operations from the recovery, it appears to be a hit or miss. That is why, I have specified the requirement that whatever recovery you use, use the recoveries built-in Format /system, /cache and /data, I am not going to do it within my update script.
BTW, thanks for the recovery, it cuts down a bunch of time trying to test, build..

Funny you say CWR makes no difference. I disagree. The kernel works different in different versions of cwr
With
Clockwork Touch aka recovery-clockwork-touch-5.8.1.3-hercules
I cant adb remount it gets stuck in Read only.
With
v 5.0.2.6 I have no issues
Flashing files in one ver the other may cause issues for some phones.. As we have seen every phone is handling the ICS flash different.
I have had better luck with the older CWR

mhx said:
Funny you say CWR makes no difference. I disagree. The kernel works different in different versions of cwr
With
Clockwork Touch aka recovery-clockwork-touch-5.8.1.3-hercules
I cant adb remount it gets stuck in Read only.
With
v 5.0.2.6 I have no issues
Flashing files in one ver the other may cause issues for some phones.. As we have seen every phone is handling the ICS flash different.
I have had better luck with the older CWR
Click to expand...
Click to collapse
Nope..read the OP again...he is talking about the linkage of ROM and recovery. They are unrelated...

mohan_kr said:
Nope..read the OP again...he is talking about the linkage of ROM and recovery. They are unrelated...
Click to expand...
Click to collapse
i beg to differ, mhx makes a valid point. The op may be true for gb, but for ics i too have noticed better flashes, and things "stuck better" with 5.0.2.6. I can't even get fix permissions to work on anything past 5.0.2.7

icenight89 said:
i beg to differ, mhx makes a valid point. The op may be true for gb, but for ics i too have noticed better flashes, and things "stuck better" with 5.0.2.6. I can't even get fix permissions to work on anything past 5.0.2.7
Click to expand...
Click to collapse
I've flashed multiple ICS roms multiple times on multiple CWM (touch and non) recoveries, and I've never had a single issue.

icenight89 said:
i beg to differ, mhx makes a valid point. The op may be true for gb, but for ics i too have noticed better flashes, and things "stuck better" with 5.0.2.6. I can't even get fix permissions to work on anything past 5.0.2.7
Click to expand...
Click to collapse
If the OP was talking about different features of a particular recovery, then yes there is point to it. He is talking about flashing a ROM with edifying scripting support for the skyrocket, which should work regardless of the version of the base android platform for our device, if of course the ROM creator has put the rights bits in the script for that particular ROM.

[Q] stuck on htc desire screen after flashing new rom :[

hi every time i start my HTC desire s after flashing a new rom it gets stuck on the white htc screen. i follow this guide to root and flash and for months its been going well, ive changed my roms many times, but now after trying to install a new jelly bean rom. evreytime i boot up the phone it gets stuck on the htc boot screen.
here is what i do when i flash a new ROM
extract the boot.img from rom i want to android tools folder (adb,fastboot folder)
wipe data/factory reset
wipe cache
wipe dalvik cache
install the rom i want
reboot into bootloader and enter the code: fastboot flash boot boot.img
it tells me its finished in cmd and then i reboot to get the same stuck white htc screen.
i can still access 4EXT Recovery
please help :[

smiah789 said:
hi every time i start my HTC desire s after flashing a new rom it gets stuck on the white htc screen. i follow this guide to root and flash and for months its been going well, ive changed my roms many times, but now after trying to install a new jelly bean rom. evreytime i boot up the phone it gets stuck on the htc boot screen.
here is what i do when i flash a new ROM
extract the boot.img from rom i want to android tools folder (adb,fastboot folder)
wipe data/factory reset
wipe cache
wipe dalvik cache
install the rom i want
reboot into bootloader and enter the code: fastboot flash boot boot.img
it tells me its finished in cmd and then i reboot to get the same stuck white htc screen.
i can still access 4EXT Recovery
please help :[
Click to expand...
Click to collapse
Your problem is that you're on the wrong hBoot - now go and do some searching and reading before coming back with any more questions that have been asked and answered 10 times in the last week alone :banghead:

SimonTS said:
Your problem is that you're on the wrong hBoot - now go and do some searching and reading before coming back with any more questions that have been asked and answered 10 times in the last week alone :banghead:
Click to expand...
Click to collapse
im on the wrong hboot? ive been on hboot 2.00.002 for 4-5 months why would it give me problems now ?

smiah789 said:
im on the wrong hboot? ive been on hboot 2.00.002 for 4-5 months why would it give me problems now ?
Click to expand...
Click to collapse
In that case, still searching would have revealed the likely cause;-
[OFF-TOPIC] Non-Sony screen panel DS users lounge

SimonTS said:
In that case, still searching would have revealed the likely cause;-
[OFF-TOPIC] Non-Sony screen panel DS users lounge
Click to expand...
Click to collapse
I still cant find the solution as installing any rom such as ice cream sandwich doesn't work, i still get the frozen htc screen. I tried searching for other methods but cant find the solution

smiah789 said:
I still cant find the solution as installing any rom such as ice cream sandwich doesn't work, i still get the frozen htc screen. I tried searching for other methods but cant find the solution
Click to expand...
Click to collapse
There are only three causes I can think of for the problem you have described;-
1) You aren't flashing the kernel
2) You have the wrong hBoot and it doesn't include the partition required for the new ROMs
3) You have the 'other' type of panel and need to use the specialist kernel

SimonTS said:
There are only three causes I can think of for the problem you have described;-
1) You aren't flashing the kernel
2) You have the wrong hBoot and it doesn't include the partition required for the new ROMs
3) You have the 'other' type of panel and need to use the specialist kernel
Click to expand...
Click to collapse
Actually, none of those seem to be the case here:
1. If the op is following the procedure he outlined in the first post, he is flashing the kernel
2. The op has already specified, that he is on hboot 2.00.002, any rom will work with that
3. If the op can't install ics roms either (as specified in his last post), then it can't be (only) the panel issue.
Please read before responding, SimonTS
That all being said, I can't think what the problem might be.

teadrinker said:
Actually, none of those seem to be the case here:
1. If the op is following the procedure he outlined in the first post, he is flashing the kernel
2. The op has already specified, that he is on hboot 2.00.002, any rom will work with that
3. If the op can't install ics roms either (as specified in his last post), then it can't be (only) the panel issue.
Please read before responding, SimonTS
That all being said, I can't think what the problem might be.
Click to expand...
Click to collapse
Excuse me for upsetting you in such a monumental way oh great one. I originally suggested (maybe a little abruptly, but given the majority of the posts on here and the total lack of information provided by the OP it was fair) that it was the hBoot as this is by far the most likely cause - he said he was running v2.00.002. I then suggested he look at the panel issue - he then decided to say that it wasn't just JB ROMs, but also ICS ones which had a problem. I then said I could only think of three possible causes - the same three that you can think of.
What, EXACTLY, did I say in there that caused you such upset?
The fact is that the OP STILL hasn't provided any useful information about his phone to help us help him - and he should still check his panel as a possible issue; maybe by trying to flash JB ROMs on the wrong type of panel he has caused further problems? I don't know and am just stood there with my manhood flapping in the wind to try and suggest anything else without further information from the OP.

SimonTS said:
Excuse me for upsetting you in such a monumental way oh great one. I originally suggested (maybe a little abruptly, but given the majority of the posts on here and the total lack of information provided by the OP it was fair) that it was the hBoot as this is by far the most likely cause - he said he was running v2.00.002. I then suggested he look at the panel issue - he then decided to say that it wasn't just JB ROMs, but also ICS ones which had a problem. I then said I could only think of three possible causes - the same three that you can think of.
What, EXACTLY, did I say in there that caused you such upset?
The fact is that the OP STILL hasn't provided any useful information about his phone to help us help him - and he should still check his panel as a possible issue; maybe by trying to flash JB ROMs on the wrong type of panel he has caused further problems? I don't know and am just stood there with my manhood flapping in the wind to try and suggest anything else without further information from the OP.
Click to expand...
Click to collapse
Sorry!! Didn't mean it to come across like that. I have as little idea as you what's causing this problem.

Come on you two we actually have a good question here, please let's not argue.
Can the op please post the contents of his bootloader screen.
Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.
Albert Einstein

jugg1es said:
Come on you two we actually have a good question here, please let's not argue.
Can the op please post the contents of his bootloader screen.
Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.
Albert Einstein
Click to expand...
Click to collapse
yeah, sure! no problem
SAGA PVT SHIP S-ON RL
HBOOT - 2.00.0002
Radio - 3822.10.08.04_M
eMMC-boot
Aug 22 2011, 15:22:13
ive also taken a picture of the bootloader
http://imgur.com/00TAn

This is going to sound a stupid question, are you turning off fastboot first and then pushing the img.
“Any fool can use a computer.* Many do.”
(Ted Nelson)

jugg1es said:
This is going to sound a stupid question, are you turning off fastboot first and then pushing the img.
“Any fool can use a computer.* Many do.”
(Ted Nelson)
Click to expand...
Click to collapse
After i install a rom i power it down and boot into the bootloader, connect the usb, click fast boot then push the roms img file

Ok, I'm at a loss. Anyone else?
“Any fool can use a computer.* Many do.”
(Ted Nelson)

anyone have any other ideas? :[

smiah789 said:
anyone have any other ideas? :[
Click to expand...
Click to collapse
Can you still flash GB roms?
“Any fool can use a computer.* Many do.”
(Ted Nelson)

smiah789 said:
anyone have any other ideas? :[
Click to expand...
Click to collapse
If I was in your situation then I would be starting from basics;-
Full wipe - EVERYTHING
Re-install 4EXT Touch Recovery (latest version) - Check MD5 after downloading
Re-flash hBoot - Check MD5 after downloading
Full wipe - EVERYTHING
Format all partitions to EXT4 (not EXT3)
Full wipe - EVERYTHING
Install an ICS or JB ROM - Check MD5 after downloading
If this fails then do all the above but with a known solid GB ROM - Reaper or Endymion to make sure there's not something worse going on.
Also, regardless of your previous answer, do the test to ensure which panel your DS has - better to waste 2 minutes and be proved right than waste 2 days if you are wrong.

SimonTS said:
If I was in your situation then I would be starting from basics;-
Full wipe - EVERYTHING
Re-install 4EXT Touch Recovery (latest version) - Check MD5 after downloading
Re-flash hBoot - Check MD5 after downloading
Full wipe - EVERYTHING
Format all partitions to EXT4 (not EXT3)
Full wipe - EVERYTHING
Install an ICS or JB ROM - Check MD5 after downloading
If this fails then do all the above but with a known solid GB ROM - Reaper or Endymion to make sure there's not something worse going on.
Also, regardless of your previous answer, do the test to ensure which panel your DS has - better to waste 2 minutes and be proved right than waste 2 days if you are wrong.
Click to expand...
Click to collapse
THANK YOU EVREYBODY SOO MUCH , IT WORKS!!
after seeing his suggestion to reflash the recovery, i flashed clockwork recovery via fastboot,picked a ics rom, did the usual steps and it worked!!

smiah789 said:
THANK YOU EVREYBODY SOO MUCH , IT WORKS!!
after seeing his suggestion to reflash the recovery, i flashed clockwork recovery via fastboot,picked a ics rom, did the usual steps and it worked!!
Click to expand...
Click to collapse
Glad to see that the old engineering principle I learnt years ago still works - KISS (Keep It Simple Stupid)

smiah789 said:
THANK YOU EVREYBODY SOO MUCH , IT WORKS!!
after seeing his suggestion to reflash the recovery, i flashed clockwork recovery via fastboot,picked a ics rom, did the usual steps and it worked!!
Click to expand...
Click to collapse
Could you mark the op as solved, glad your back up and running.:thumbup:
“Any fool can use a computer.* Many do.”
(Ted Nelson)