Develop Bugs

Actual (2010-06-27) hosts file

Because AdFree is not working on Desire:
I've made hosts file which is compilation of two lists and some manual additions (for correct blocking of admob). So I decided to share with my list. Use it if You want to. Please tell me if this forum is wrong for that list.

Sorry for the n00b question but how do you install this?

Nice one mate. You've just reminded me I needed to redo my hosts file after installing Modaco Froyo, and I might as well use yours as it'll be more up to date than mine.

Ghisy said:
Sorry for the n00b question but how do you install this?
Click to expand...
Click to collapse
ditto this, instructions for us noobies?

unzip the host file
than enter recovery
adb-windows shell mount /system
adb-windows shell mv /system/etc/hosts /sdcard/backuphost
adb push c:\hosts /system/etc
that should wrok if you unziped hosts.zip to c:\ and if something goes wrong you have your original hosts file backed up in /sdcard/backuphost
hope this helps
p.s. i didn't try this

did everything, and adfree is still not working in froyo...
Thanks anyway!
Edit: Now, Adfree FCs!
Edit 2: I did it again and it worked!

Could someone please create a zip file, that can be falshed through clockworkmod recovery? This would be fantastic.

Try this, mate. [Click!]

dnlgee said:
Try this, mate. [Click!]
Click to expand...
Click to collapse
Thanks dnlgee I put it in my repo on ROM Manager

This is great, thanks for sharing - it seems to work great. I might go back to a stock hosts though - I like to block ads when browsing, but I feel bad about doing it for ad-supported applications. That's just me though

shawe_ewahs said:
Thanks dnlgee I put it in my repo on ROM Manager
Click to expand...
Click to collapse
No worries, just checked your repo, there's a lot of stuff there haha.

dnlgee said:
No worries, just checked your repo, there's a lot of stuff there haha.
Click to expand...
Click to collapse
Yes, trying to do thinks more easy for all people

Thank you. I have been looking for this for a long time

Great work, it worked a charm until I changed to a new rom, went to use it again and it was gone from the downloads in Rom Manager.
Big thanks.
Panic over, It was saved as a download on my SD card, Rom Manager flashed it again from the saved location no problem.
Love it.

danbst said:
Your stuff is gone from Rom Manager it seems mate.
Would I be right in assuming I can put this on my card renamed as update.zip (if I need to?)
Use rom manager to boot into recovery and flash it manually?
Great work BTW, it worked a charm until I changed to a new rom, went to use it again and as I say it was gone.
Big thanks.
Click to expand...
Click to collapse
You don't need to rename the zip file if you're using ROM Manager, but yes you should be able to install this through the manager.
If you can't download it through the ROM Manager report, my link is always online and will be updated when possible.
Sent from my HTC Desire using Tapatalk

Just a confused question;
If we have a rooted device, what's the reason for having to use the recovery menu? Can you not simply overwrite the file?
Thanks

Yea you can, provided you reboot into recovery and mount the system, then pull or push the device back into the system.
Either way you need to boot into recovery as there's no root method that fully allows read/write access for the Desire at the moment.

Psy-Blade said:
Just a confused question;
If we have a rooted device, what's the reason for having to use the recovery menu? Can you not simply overwrite the file?
Thanks
Click to expand...
Click to collapse
It should work like this. Unfortunatelly you can't mount system partition as read/write. That is because system is blocking this in some way.
Sent from my HTC Desire using XDA App

Another quick one:
I used the zip file which people are using in the rom manager. I rebooted into clockwork and selected apply update from zip and selected the file. Appears I broke the system though lol .
Is this not the right way of doing it?
Also how do you type commands in the recovery? :S

dnlgee said:
Try this, mate. [Click!]
Click to expand...
Click to collapse
Link dead ??!! "File does not exist. Make sure you specified correct file name."

Revolutionary Rooted but Not???

First I wanted to say hi to all of you. Evo 4G is my second Android phone. I'm still a noob in training but I'm getting by.
I'm having a bit of a issue with trying to use some apps for root only and keep getting that I need to be rooted. Yes S-Off is displayed but I'm still running into this issue no matter what. Did I miss something? I'm still searching the forum to find a answer but I haven't found anything as of yet.
Let me know what you guys think.
Thanks
Z3r0
Edit: I figured out what the problem was. Me being stupid and not reading enough. Mods go ahead and lock/delete this thread.

to double check, there is an app in the market called "root check" by joeykrim.
and for apps to gain access to the phone you should have the app "superuser" it gives other apps permission to access root.

As someone previously stated, you'll need an app called "superuser" to allow apps to use root permissions.

Greenfieldan said:
As someone previously stated, you'll need an app called "superuser" to allow apps to use root permissions.
Click to expand...
Click to collapse
This.
Running Revolutionary Roots your phone, but you need superuser to give programs root access. To give programs root access, you will need a rooted ROM with the superuser application or just download the superuser app.

oldwesterncowboy said:
to double check, there is an app in the market called "root check" by joeykrim.
and for apps to gain access to the phone you should have the app "superuser" it gives other apps permission to access root.
Click to expand...
Click to collapse
Yeah I figured that out after reading the sticky at the beginning. My fault for not paying attention. I'm now rooted and loving it.
Thanks for the reply's guys.

I really did it now!!!
Ok so I'm back to ask some questions due to a noob mistake. Now I have been reading many of the threads that are available to fix my actual issues that I'm dealing with. I'm going to be very detailed so I apologize in advance.
So like a dumb dumb I decided to unroot my Evo as I was sure/ uncomfortable using the rooted OTA update to up date. So now I did some more reading and I did not need to unroot. Sorry I dont' know what I was thinking.
I've tried to run Revolutionary but all it does is aborts the operation everytime. I tried to change the recovery from Clockwork to Amon RA as I read that it is better so I tried to do that too. Nope that doesn't work either.
I was able to update the root OTA update but that was all that was done. So now I'm here asking for more help as I did more reading how to fix the current issue I'm having and its not working.
PLEASE Help me or guide me in the right direction to fix this.
This is all I am trying to accomplish:
1. Figure out why and what happend and get my Evo rooted
2. Apply the Amon RA recovery
Now if I need to completely wipe my phone I will do it if that is what you think is needed to be done. I know how to back up my app/ contacts etc. So just assist this dumb dumb please!

Anyone have any ideas?
Sent from my PC36100 using xda premium

So are you s on or s off when you go into hboot?
Sent from my PC36100 using Tapatalk

revolutionary s-off
Another noob here.... Ok I used revolutionary.io to root my 2.3.3
Hboot says s-off, downloaded superuser app, and astro file
Why does it say can't delete file when I try to delete pre installed files like Amazon mp3, ect
Ran root checker app from market said
Root Access is not properly configured or was not granted.
Superuser.apk - com.noshufou.android.su - version 3.0.5 is installed!
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
The adb binary is set to default shell user access as a standard non-root user
Standard su binary location: ls -l /system/bin/su:
/system/bin/su: No such file or directory
Standard su binary location: ls -l /system/xbin/su:
/system/xbin/su: No such file or directory
Alternate su binary location:
/sbin/su: Permission denied
Alternate su type binary location:
/system/xbin/sudo: No such file or directory
SU binary not found or not operating properly

tommytomatoe said:
So are you s on or s off when you go into hboot?
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
s on which I know is not rooted. No matter what I try it refuses to accept the revolutionary root program. Should I try a different root method or is Revolutionary for 2.3.3 the only method? I've looked and can't find any other way.

z3r0t0l0rEnCe said:
s on which I know is not rooted. No matter what I try it refuses to accept the revolutionary root program. Should I try a different root method or is Revolutionary for 2.3.3 the only method? I've looked and can't find any other way.
Click to expand...
Click to collapse
What is your HBOOT version, when you go into Bootloader?

Last I checked revolutionary won't s-off anything besides hboot 2.15 & 2.16. Not even the revolutionary hboot 6.xx
tapatalk signature here. lovely.

2.16
Sent from my PC36100 using xda premium

z3r0t0l0rEnCe said:
2.16
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
First, I would flash an unrooted stock ROM - the latest, if possible (see this post).
Then, try rooting via Revolutionary again (revolutionary.io). Sometimes during the unrooting process, everything isn't completely restored to stock, so you might just need to flash a completely stock ROM to get back to the point where Revolutionary will work again.

Captain_Throwback said:
First, I would flash an unrooted stock ROM - the latest, if possible (see this post).
Then, try rooting via Revolutionary again (revolutionary.io). Sometimes during the unrooting process, everything isn't completely restored to stock, so you might just need to flash a completely stock ROM to get back to the point where Revolutionary will work again.
Click to expand...
Click to collapse
Thanks for the heads up on this info. Now with the Stock RUU being RUU_SuperSonic_GB_Sprint_WWE_4.53.651.1_Radio_2.15 .00.0808_NV_2.15_release, does the 2.15 represent the HBOOT? As mine is the 2.16 or does that not matter?

z3r0t0l0rEnCe said:
Thanks for the heads up on this info. Now with the Stock RUU being RUU_SuperSonic_GB_Sprint_WWE_4.53.651.1_Radio_2.15 .00.0808_NV_2.15_release, does the 2.15 represent the HBOOT? As mine is the 2.16 or does that not matter?
Click to expand...
Click to collapse
The file name has nothing to do with the HBOOT version. It doesn't matter. If the HBOOT version you currently have is newer than the version in the RUU, it will simply skip updating it.

Ok ill test it when I get home from work tonight.
Sent from my PC36100 using xda premium

z3r0t0l0rEnCe said:
I've tried to run Revolutionary but all it does is aborts the operation everytime. I tried to change the recovery from Clockwork to Amon RA as I read that it is better so I tried to do that too. Nope that doesn't work either.
Now if I need to completely wipe my phone I will do it if that is what you think is needed to be done. I know how to back up my app/ contacts etc. So just assist this dumb dumb please!
Click to expand...
Click to collapse
All you need to is flash another hboot for the evo. (Any of them will work. Doesn't really matter. Look around for the files and a guide is out there I'm sure. If not, PM me. Anyway, flash it. And then run revolutionary. It should work then.
I did not know that, tommytomatoe. But regardless, what I suggested would work if my thinking is correct.

IamNotSureX said:
All you need to is flash another hboot for the evo. (Any of them will work. Doesn't really matter. Look around for the files and a guide is out there I'm sure. If not, PM me. Anyway, flash it. And then run revolutionary. It should work then.
I did not know that, tommytomatoe. But regardless, what I suggested would work if my thinking is correct.
Click to expand...
Click to collapse
He said he has Hboot 2.16. If I'm not mistaken you cannot downgrade your Hboot version from something like 2.16 to 2.15 or 2.10. Either way, Revolutionary will be able to root 2.16 just fine. Seems like all he needs to do is follow Captain Throwbacks advice to get his phone out of "What the hell are you doing to me" mode.

I have yet to perform the flash. I got caught up at work late last night. I'll do it tonight for sure when I get off work.
Thank you all for the input and I'll let you all know if my Evo will let me get it out of ""What the hell are you doing to me" mode.

[Q] Rooted Question / App Confusion

Please know in advance I've read top to bottom and through page after page of post and guide here and on other site before rooting, and I searched before posting this question...
-I rooted my Dinc using Unrevoked3, just this past Saturday.
-I successfully installed Titanium Backup and successfully have used it for back-up.
-I UNsuccessfully did an install of Root Explorer. They told me it sounds like I'm likely not rooted.
-I downloaded ConnectBot, typed Su in the cmd line and received a "Permission denied".
Unrevoked3 and the use of Titanium Backup tell me I am rooted. Root Explorer not getting permission and cmd command tell me I'm not.
Should I simply run the Unrevoked3 process again?
My end goal is to flash a custom rom ideally with better battery life, a better bluetooth (my stock set-up stinks on bt devices) and a different look like CM7.
Here is my software info it if matters:
Android Version 2.2
Baseband 2.15.00.07.28
Kernal Version 2.6.32.17-g9a2fc16
Software 3.26.605.1
I thought I read and re-read and search extensively, much appreciate any help!!

MeatplowMike said:
Please know in advance I've read top to bottom and through page after page of post and guide here and on other site before rooting, and I searched before posting this question...
-I rooted my Dinc using Unrevoked3, just this past Saturday.
-I successfully installed Titanium Backup and successfully have used it for back-up.
-I UNsuccessfully did an install of Root Explorer. They told me it sounds like I'm likely not rooted.
-I downloaded ConnectBot, typed Su in the cmd line and received a "Permission denied".
Unrevoked3 and the use of Titanium Backup tell me I am rooted. Root Explorer not getting permission and cmd command tell me I'm not.
Should I simply run the Unrevoked3 process again?
My end goal is to flash a custom rom ideally with better battery life, a better bluetooth (my stock set-up stinks on bt devices) and a different look like CM7.
Here is my software info it if matters:
Android Version 2.2
Baseband 2.15.00.07.28
Kernal Version 2.6.32.17-g9a2fc16
Software 3.26.605.1
I thought I read and re-read and search extensively, much appreciate any help!!
Click to expand...
Click to collapse
Sounds like you don't have superuser installed. If you do try uninstalling it and download it off the market.

jackbtha1 said:
Sounds like you don't have superuser installed. If you do try uninstalling it and download it off the market.
Click to expand...
Click to collapse
Even if you have it installed, search Superuser in the Market, download/install. Then open the Superuser app itself, hit Menu - Preferences, then scroll down to Su binary vX.Y.Z (X Y Z will be numbers). Touch it and update the su binary, hopefully that'll let you as it'll ask you to "Allow" root access.

I did the update and it failed, twice I'll try the remove and reinstall method next. Thx for the advice.
Sent from my ADR6300 using XDA App

So Superuser won't even allow for a removal. It was "remove updates", "clear data" or "force stop" only.
Sent from my ADR6300 using XDA App

MeatplowMike said:
So Superuser won't even allow for a removal. It was "remove updates", "clear data" or "force stop" only.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I actually remember running into this on my brothers phone a while back. I think I installed busy box off the market and it solved that problem. Not sure if that would work but worth a shot.

jackbtha1 said:
I actually remember running into this on my brothers phone a while back. I think I installed busy box off the market and it solved that problem. Not sure if that would work but worth a shot.
Click to expand...
Click to collapse
Very true, I had a similar issue once trying to uninstall apps, they'd always reappear after reboot. Needed busybox installed which fixed it.
EDIT: Instead of trying to unistall it, go to the Superuser site here, and there's a 3.0.6 flashable zip file that you can flash in ClockworkMod Recovery, maybe give that a try...? But install busybox too as mentioned above by jackbtha1.

Huge thanks for the advice. I installed Busybox and it fixed the problem immediately after I rebooted. I didn't know it was needed because Superuser, in the binary update logged that it had success with busybox, yet I'd never installed it. Alls well, thanks! Odd that Titanium was working on it's own without permissions.
NOW... if anyone wants to hold my hand through flashing a ROM on this thing. It seems many of the walk-thru guides are a year old or the updated process is scattered.

Before you install any roms make a stock backup so you have something to fall back on.
https://market.android.com/details?id=com.koushikdutta.rommanager
Sent from my Incredible using XDA Premium App

MeatplowMike said:
Huge thanks for the advice. I installed Busybox and it fixed the problem immediately after I rebooted. I didn't know it was needed because Superuser, in the binary update logged that it had success with busybox, yet I'd never installed it. Alls well, thanks! Odd that Titanium was working on it's own without permissions.
NOW... if anyone wants to hold my hand through flashing a ROM on this thing. It seems many of the walk-thru guides are a year old or the updated process is scattered.
Click to expand...
Click to collapse
The reason TiB worked was it uses a modified busybox within the app itself, so that's why it worked okay.
Sent from my ADR6300 using xda premium

Glad to hear everything worked out for you. Now as far as flashing a custom Rom do some research first and make sure you make a back up before flashing anything.

[Q] Improperly rooted

I'm kind of new to Android, but I have decent computing experience. My problem is that I recently rooted my SPH-L710 (stock rom) and when I ran Busybox I received the error message "There was a problem opening a shell with root access. This is either being caused by superuser/supersu or by a device that is improperly rooted. Try removing the superuser/supersu permissions, uninstalling this app," etc etc.
I have attempted various methods using things like root explorer and terminal emulator to remove/ change the permissions so I might delete the su file, to no avail as the phone isn't properly rooted. One thread on here mentioned that formatting the sd card - I assume it meant the phone itself - would do the trick. After that, I would of course have to flash a rom, correct? Thanks for your time.

I would do the rooting process over again, with a new download of all files.
Do you have cwm or another custom recovery working?
sent from a secret underground bunker

winstonmarrs74 said:
I'm kind of new to Android, but I have decent computing experience. My problem is that I recently rooted my SPH-L710 (stock rom) and when I ran Busybox I received the error message "There was a problem opening a shell with root access. This is either being caused by superuser/supersu or by a device that is improperly rooted. Try removing the superuser/supersu permissions, uninstalling this app," etc etc.
I have attempted various methods using things like root explorer and terminal emulator to remove/ change the permissions so I might delete the su file, to no avail as the phone isn't properly rooted. One thread on here mentioned that formatting the sd card - I assume it meant the phone itself - would do the trick. After that, I would of course have to flash a rom, correct? Thanks for your time.
Click to expand...
Click to collapse
try flashing this in recovery http://downloads.androidsu.com/superuser/su-bin-3.1.1-arm-signed.zip its the binary files required for SuperUser if your having trouble with gaining root access

Annnnd try opening super user or super such right after booting
Sent from my SPH-L710 using xda app-developers app

mjben said:
I would do the rooting process over again, with a new download of all files.
Do you have cwm or another custom recovery working?
sent from a secret underground bunker
Click to expand...
Click to collapse
I'm running CWM. I've successfully rooted a few times before, but this last time it didn't work. I unrooted and then rooted again three times and even re-downloaded all the files (cwm, odin, rom) but I can't seem to fix this. I'll attempt it again and hopefully it'll take this time.

Fantastic! I flashed the su binary zip, rebooted and superuser was already to go and phone is now properly rooted. Thanks very much! :good:

Thank you!
evo4gnoob said:
try flashing this in recovery (SU url I can't post...) its the binary files required for SuperUser if your having trouble with gaining root access
Click to expand...
Click to collapse
I would like to take this opportunity to thank you. I had been having issues trying to get root on my Sprint GS3, and nothing worked until I used that SU.
:laugh:

Paleogryph said:
I would like to take this opportunity to thank you. I had been having issues trying to get root on my Sprint GS3, and nothing worked until I used that SU.
:laugh:
Click to expand...
Click to collapse
No problem m8 glad I could help
Sent from my SPH-L710 using xda app-developers app

Need Stock Rom

I had a backup of stock before root but when i tried to back up to it today it gave me a md5 mismatch so i couldnt back up to it. From what I seen in beaups thread that I need to be on a stock rom and stock kernal for his s-off method to work. Is there a stock rom that I could flash to use the s-off method?

I'd like this answered as well. I think andy's stock rom near the bottom of the page works, but I haven't had a confirmation yet. Also wondering if odex versus deodexed versions matter.

Same boat im in just waiting for somebody to say which one we can use when we are already rooted and unlocked. I dont know how my md5's mismatched on my stock before root backup but I can't go back to it so Im kinda stuck here until we get a answer.

Aggies1288 said:
Same boat im in just waiting for somebody to say which one we can use when we are already rooted and unlocked. I dont know how my md5's mismatched on my stock before root backup but I can't go back to it so Im kinda stuck here until we get a answer.
Click to expand...
Click to collapse
Just heard andy's bonestock works trying it myself to confirm.
EDIT: Downloading the 1.1 download not the newest. Under old downloads. I would think the more stock the better.

cstrife999 said:
Just heard andy's bonestock works trying it myself to confirm.
EDIT: Downloading the 1.1 download not the newest. Under old downloads. I would think the more stock the better.
Click to expand...
Click to collapse
Just tried v1.0a..... No dice.

I'd test 1.1 but for some reason it won't let me copy the zip over to my phone... Keeps saying the device has stopped working or has been disconnected. Tried many different USB ports.... Going to have to bluetooth it which is going to take even more time...

cstrife999 said:
I'd test 1.1 but for some reason it won't let me copy the zip over to my phone... Keeps saying the device has stopped working or has been disconnected. Tried many different USB ports.... Going to have to bluetooth it which is going to take even more time...
Click to expand...
Click to collapse
Im downloading 1.1 now. Ill get back with y'all on how it went.

Aggies1288 said:
Im downloading 1.1 now. Ill get back with y'all on how it went.
Click to expand...
Click to collapse
I found VZW_Stock_Rooted_deodex from Andy
Trying that now..

mcampos7 said:
I found VZW_Stock_Rooted_deodex from Andy
Trying that now..
Click to expand...
Click to collapse
This is what I've been on since launch day. Curious if this will work.

m4rk0358 said:
This is what I've been on since launch day. Curious if this will work.
Click to expand...
Click to collapse
Actually I'm having more problems with this than I did trying it on 1.0a and NOS...
I'm trying to find my nandroid of stock rooted but I think it was on a drive that failed.
Linux boot, next???

mcampos7 said:
Actually I'm having more problems with this than I did trying it on 1.0a and NOS...
I'm trying to find my nandroid of stock rooted but I think it was on a drive that failed.
Linux boot, next???
Click to expand...
Click to collapse
Yea i got made fun of when using that lol...

SUPER MEGA ULTIMATE DISCLAIMER: IIRC = IF I REMEMBER CORRECTLY. I AM NOT RESPONSIBLE IF THIS DOESN'T WORK/SCREWS UP YOUR DEVICE/BRICKS/ETC. YOU ARE WARNED. THIS WORKED FOR ME IN THE PAST WITH MY GALAXY NEXUS BACKUPS USING CWMTOUCH 6.0.3.6 AND 6.0.4.3.
YOU ARE WARNED.
I HAVE NEVER USED TWRP FOR BACKUPS. IT IS A MERE SUGGESTION THAT THIS METHOD WILL WORK WITH SIMILAR RESULTS. I HAVE NEVER BROWSED A BACKUP FOR TWRP. ANY ATTEMPT YOU MAKE USING A TWRP BACKUP IS OF YOUR OWN COGNIZANCE. YOU HAVE BEEN WARNED.
YOU ARE WARNED.
YOU ARE WARNED.
IIRC: If you have an md5 mismatch while trying to restore in a recovery, try this process:
IF YOU HAVE A BACKUP I HIGHLY SUGGEST STORING THE BACKUP FILE ON YOUR DESKTOP JUST IN CASE!!!!
Boot into whatever ROM you're on ATM.
Browse to your ClockworkMod (or TWRP backup must have an accessible folder for it's backups) using a Root file explorer, which I happen to use "Root Explorer" and open the backup file you just made.
Inside of that will be a nandroid.md5.
Delete that file and reboot into recovery, and try restoring again.
SUPER MEGA ULTIMATE DISCLAIMER: IIRC = IF I REMEMBER CORRECTLY. I AM NOT RESPONSIBLE IF THIS DOESN'T WORK/SCREWS UP YOUR DEVICE/BRICKS/ETC. YOU ARE WARNED. THIS WORKED FOR ME IN THE PAST WITH MY GALAXY NEXUS BACKUPS USING CWMTOUCH 6.0.3.6 AND 6.0.4.3.
YOU ARE WARNED.
YOU ARE WARNED.
YOU ARE WARNED.
This method did work for me several times on several backups, but root and S-Off being so new, I cannot attest that it works for the One. YOU ARE WARNED**!!

cstrife999 said:
Yea i got made fun of when using that lol...
Click to expand...
Click to collapse
For using what? Linux? NOS?

mcampos7 said:
For using what? Linux? NOS?
Click to expand...
Click to collapse
The sojo app called my issues dumb lol. It's hard to get frustrated when humor is involved with the errors.

cstrife999 said:
The sojo app called my issues dumb lol. It's hard to get frustrated when humor is involved with the errors.
Click to expand...
Click to collapse
Looks like we may have to flash the boot.img that they are talking about in the s-off thread anybody have a guide for doing that?

I take it nobody tried deleting the nandroid.md5?

rmaccamr said:
I take it nobody tried deleting the nandroid.md5?
Click to expand...
Click to collapse
I just tried looking for where the nandroid file was. I went to my sdcard on root explorer then to clockworkmod and didn't find any of my backups there. Is there another spot that i need to look in to do that?

Aggies1288 said:
I just tried looking for where the nandroid file was. I went to my sdcard on root explorer then to clockworkmod and didn't find any of my backups there. Is there another spot that i need to look in to do that?
Click to expand...
Click to collapse
If using CWM, they will be under the /data/clockworkmod/backup directory, not /sdcard/clockworkmod/backup.

I tried the odex stock rom, but it won't flash... Anybody have this issue?

santod040 said:
If using CWM, they will be under the /data/clockworkmod/backup directory, not /sdcard/clockworkmod/backup.
Click to expand...
Click to collapse
Ok i found it it was under /data/media/clockworkmod/backup but i dont see any files inside of that that are a md5 file im going to look in the data.ext4.tar file and the system.ext4.tar.a. Does any of those ring a bell? i see the boot.img, data.ext4.tar.a, recovery.img, system.ext4.tar.a, and system.ext4.tar.b. Thats all the files inside the backup i made before i rooted.