Develop Bugs

[Q] im stuck and dont know what to do...

ok i got a brand new epic and with my old epic i was on midnight rom v3.0. I put the same sd card into the new epic and i odined to dk28 and ran the 1click root with cwm3. i turned the phone off and rebooted into cwm3 and it turned it over to ext4. after that i went to restore the midnight rom 3.0 that i had saved and now i get stuck at the sammy screen... What did i do wrong? PLEASE HELP ME!

Odin back to stock and do a clean install i believe there is problems when restoring in midnight 3

ok so how do i go about doing a totally fresh install? will you give me steps PLEEEEAAASSSSSEEEE? Cause i tried doing that. this is what i tried first. I odined into dk28 and then i did one click root with cwm3 and the phone booted up. Then i 3 fingure salute into cwm3 and it automaticaly tried to convert it to ext4. everything went fine but the sd-ext that failed. then when i tried to reboot from there it got stuck.

should i partition the sd card? and its been a while since i first went to ext4 from stock dk28 and i cant exactly remember the whole process. LOL, if you could give me step by step from stock dk28 to midnight rom v3.0 i would be so releived cause right now the stock is crap...

Batt pull
download mode (Power on +1)
odin dk28
setting make sure usb debugging is checked
Root with cw3
boot into cw3 power off then (vol down+power+camera)
factory reset x3
wipe cache x3
wipe dalvik x3
flash no journalizing mod
flash midnight 3.0

I cosign on iSaint's comment. Pull the battery, go into download mode, odin to dk28, flash cwm3, no journal zip (if you want), flash the rom (do not restore. do a fresh flash). Once it's up and running, go back to cwm3, do an advanced restore and restore data only. Nothing else.

ill try again and i will let you know what happens, but im pretty sure i tried that and i get stuck at sammy. I dont know if its the new phone and the previous sd card with all my info thats effing it up or what. i think its the cwm3 converting everything to ext4 and it fails. ill let you know in a min. thanx

ok this is what happens everytime. after i root with cwm3 i turn the phone off and 3 fingure into cwm3 and b4 i can choose the zip or anything it starts trying to convert rfs to ext4 and it makes a restore point and says "no sd-ext found. skipping backup of sd ext.
generating md5 sum
backup complete
checking md5 sums...
restoring system...
restoring data...
restoring.android_secure...
restoring cache...
sd-ext.img not found. skipping restore of /sd-ext.
restore complete!
so should i still do the 9xwipe?
cause i did that b4 and it gets stuck at sammy...

i followed those exact steps and on startup it does the regular dk28 startup with a ANDROID word flashing sidways over the startup animation and then my phone starts up but i cant push anything. it keeps vibrating and shuts off and then comes back on and shuts off again and again. something is very wrong and the only thing i can do is odin back to dk28. what should i do? i am very dissapointed...

You could try the other method of converting. Install cwm 2.5.1.0 instead of cwm3 on top of dk28. Get "prepare.zip" from the original ext4 conversion thread, which will set you up with 2.5.1.2. Run the formatter from your computer. Advanced->reboot recovery from 2.5.1.0 to get to 2.5.1.2. Then flash your ext4 rom from 2.5.1.2.
Oh, and sd-ext *should* fail if you haven't formatted your sdcard for apps2sd. It won't cause any problems for you, though.

flash midnight 2.9
then flash midnight 3.0

Ok so while it was acting all bugged out I pulled battery and then 3 fingured into cwm3 and I took a chance and restored on 2.9 and everything is perfect. I think something is seriously wrong with v3.0. What do y'all think?
Sent from my SPH-D700 using XDA App

yea 3.0 doesn't work well with restoring data but glad everything worked out for you

thank all of you soooooo much for all of your help and ideas. dont know what i would do without all of you. thanx

it seems like a lot of the vibrations and boot failures comes from the wiping thing. do oneclick cwm3 and ext4 conversion then factory reset at least 3 times then do cache and dalvik at least once. after that you can install your favorite rom for the most part

[Q] RandomRom Hawk 2.3.4 flashing questions

I have been trying for the past 3 hours to flash this ROM correctly. I've tried odining the eg22 deodexed modem, converting to ext4, enabling journaling, flashing the eg22plus kernal, odining the eg22 modem, wiping 3x data,cache, and dalvik cache in all sorts of combinations. I just get the Samsung logo with vibrations after flashing the rom. Does any one have any ideas of what's causing this? Also, after restoring a backup of RandomRom Osprey, I'm receiving Google Framework errors nonstop. I am not new to flashing, but stumped on this one. I'd be grateful for any ideas. Thank you.

When you say "I've tried odining the eg22 deodexed modem, converting to ext4..." did you mean to say modem or rom?
If you're starting off by odining stock eg22 rom then everything sounds right. If not, that should be your first step.
Maybe skip journaling and do it later? Or do the modem before anything else.

xhitman88x said:
I have been trying for the past 3 hours to flash this ROM correctly. I've tried odining the eg22 deodexed modem, converting to ext4, enabling journaling, flashing the eg22plus kernal, odining the eg22 modem, wiping 3x data,cache, and dalvik cache in all sorts of combinations. I just get the Samsung logo with vibrations after flashing the rom. Does any one have any ideas of what's causing this? Also, after restoring a backup of RandomRom Osprey, I'm receiving Google Framework errors nonstop. I am not new to flashing, but stumped on this one. I'd be grateful for any ideas. Thank you.
Click to expand...
Click to collapse
Have you partitioned your sd card yet? When I flashed this rom on my phone, I already have a partitioned sd card and everything went great. When I flashed it on my wifes phone, she did not have a partitioned sd card, and I had the same problem you described above. You have to partition the sd card because you need a separate partition for rfs and for ext4. All I did was partition the sd card and everything worked great. Let me know if that works for you.

update
Thanks for replies. Yes, I meant to say I flashed the eg22 rom, but it was the deodexed version. Should I have done stock? Also, my sd card is partitioned already. I appreciate the responses again.

xhitman88x said:
Thanks for replies. Yes, I meant to say I flashed the eg22 rom, but it was the deodexed version. Should I have done stock? Also, my sd card is partitioned already. I appreciate the responses again.
Click to expand...
Click to collapse
I've modified/updated the install instructions. Try this with Option A:
How Do I Use This ROM?​
How To Install RandomROM:
Pre-Steps:
Option A: Odin the .tar for EC05 deodexed EXT4.
Option B: Use one-click to root nearly any current setup with EXT4.
Option C: Already on an EXT4 setup? You're good to go, proceed.
Steps:
A clean install is recommended (Wipe 3X).
Ensure that your phone is on CWM 3.1.0.1 (Purple).
Odin a Gingerbread modem such as EE03, EF02, or EG22.
Flash RandomROM Alpha "Hawk".
Enjoy

resolved
wow i got a response from the king himself haha..will test it after work today and post a reply..thanks for taking your time out to help me with this..i like this rom and it's worth the trouble
i put the title as resolved because i have a feeling this will work lol

no-go
still a no-go =(
i followed the instructions to the t ..not sure why hawk won't flash
well, im on osprey at the moment and i'm happy with it..

xhitman88x said:
still a no-go =(
i followed the instructions to the t ..not sure why hawk won't flash
well, im on osprey at the moment and i'm happy with it..
Click to expand...
Click to collapse
I flashed Hawk directly over Osprey, just wiped partition cache and dalvik then flashed the rom zip.
Been running awesome.

Failed to move application. Not enough memory
I'm currently running the RandomRom Hawk 2.3.4 but four of my apps won't move to the sd card. It keeps saying failed to move application, not enough memory and it clearly shows that I have enough memory. Have anybody ran into this problem?

Backups corrupted on MTD?

I converted my Legendary 2.2 backup to MTD, and it's been running pretty smoothely. But today... I tried to backup my ROM from rom manager and I got an error, when it was backing up the boot img. It backs up just fine if I back it up directly from recovery, but I noticed that inside the backup folder, all the files I had to rename from ext4 extensions to yaffs2 are just image files now. Sooo, I'm a bit unsure the backup will work if I try to restore them and I'm a bit sketched to try it out.
Can anyone help me out with what's going on here?

xLoveHateLegend said:
I converted my Legendary 2.2 backup to MTD, and it's been running pretty smoothely. But today... I tried to backup my ROM from rom manager and I got an error, when it was backing up the boot img. It backs up just fine if I back it up directly from recovery, but I noticed that inside the backup folder, all the files I had to rename from ext4 extensions to yaffs2 are just image files now. Sooo, I'm a bit unsure the backup will work if I try to restore them and I'm a bit sketched to try it out.
Can anyone help me out with what's going on here?
Click to expand...
Click to collapse
Did you change ROM Manager for MTD use? There was lots of posts about this. You need to hit menu in ROM Manager, pick Manual Flash Overide, Epic-MTD and clockwork 3.x.x.x. The CWM installed when you converted to MTD is special and needs to be the only one used. Do not flash another recovery while on MTD. If you do you will have to convert again to get it.

I have not changed ROM Manager for MTD use. Someone told me to convert it, but when I click Manual Flash Override, it asks me if I'm having trouble flashing the recovery with rom manager, but whether I click ok or cancel, it doesn't really do anything. I don't see anything about MTD in rom manager.

xLoveHateLegend said:
I have not changed ROM Manager for MTD use. Someone told me to convert it, but when I click Manual Flash Override, it asks me if I'm having trouble flashing the recovery with rom manager, but whether I click ok or cancel, it doesn't really do anything. I don't see anything about MTD in rom manager.
Click to expand...
Click to collapse
You are supposed to click OK and a screen will pop right up with 3 Epic choices. Pick Epic-MTD and the clockwork 3.x.x.x then it will use the correct MTD clockwork installed. If this don't work your ROM Manager is bad. Uninstall and reinstall. If you still can't get it working you will have to not use it and 3 finger to CWM.
Sent from my SPH-D700 using XDA App

You Save my Rom Manager =)
kennyglass123 said:
You are supposed to click OK and a screen will pop right up with 3 Epic choices. Pick Epic-MTD and the clockwork 3.x.x.x then it will use the correct MTD clockwork installed. If this don't work your ROM Manager is bad. Uninstall and reinstall. If you still can't get it working you will have to not use it and 3 finger to CWM.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Thank You very much Sir KennyGlass123.
I had this same dreaded error backing up the boot img when I upgrade to CM9 Beta 3 and used Rom Mananger 5.0.0.7 BackUp Rom option in app then it would reboot to CMW 5.0.2.7 and fail to do a backup.
The only way I was avoiding this error was to do a reboot to recovery in power options or do the 3 finger CMW then back Up would work ok. But I was annoyed about this error and how before in early FC09 & EL30 roms I had not experienced this.
I recently was with CleanGB 1.1.2 BML Rom but decided to go for MTD format. I flashed the CleanGB 1.1.2 MTD rom then tried out a bunch of other great epic 4g MTD roms while backing each before installing another and finally landed to CM9. After updating kernel and updating to CM9 pre4 I started to backup my CM9 b3 and found out I was herbed.
Not until I read your posts and followed your recommendations that it totally fixed this error in Rom Mananger. Now I have both ways to back up my current rom either using Rom Manager Back Up Rom option that kicks me to CMW or 3 finger salute, lol...
XDA is the gift that keeps on giving...
Thank You for xmas everyday with new roms and themes and great info.
Lanboy =)

[Q] Cache Issue When Wiping Using CWM & SuperWipe

I was running CM9 and then went to MIUI and then back to CM9. Ever since I have not been able to do a proper update to the CM9. Got fed up with it and tried to roll it back to one of the Nandroid backups. It got stuck for hours. Pulled the battery. Tried to go through the process of installing CM9 again fresh. Used Darkside SuperWipe and it kept freezing on "Wiping Cache" and the same thing when I use CWM (v6.0.1.4)! I have attached two screen shots. It reads:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
Then when I ask it to format the cache it get frozen.
How can I fix the cache? I cannot boot into CM9 or anything for that matter. I just get the awesome little Cyan Dude and the warp background flying at me continually until I pull the battery. Can anyone help? Is there any way to get ADB to work with out turning on USB Debugging on the phone?

Same issue with Clockworkmod Recovery
Sorry to say I can't answer your question, but actually just downloaded cm9 and was trying to factory reset in order to prepare to flash it and ran into the same cache issue. I tried everything and still couldn't get around it, almost bricked my phone, got stuck in a loop. Hadn't even done anything yet, except download the cm9 Rom. Also freezes when trying to wipe cache and when trying to restore a backup when it gets to the cache. I'll be keeping an eye on your post, and Ill let you know if I figure anything out as well.

I hate to say it but... use TWRP. It looks and works better. Trust me.
Sent from my SGH-T989 using xda app-developers app

whatiznt said:
I hate to say it but... use TWRP. It looks and works better. Trust me.
Click to expand...
Click to collapse
I trust you but on the Team Win Recovery Project's changelog you can see that it has not been updated in almost a year! CWM is updated much more frequently and also I enjoy having the touch version! Very convenient.

I've been reading that CWM v6.0.1.4 is causing problems with our phone. Would advise downgrading back to 5.0.2.7 and use the darkside scripts to wipe. I haven't had an issue with this version since it was released (other than needing to use darkside scripts lol).

jalight27 said:
Just downloaded cm9 and was trying to factory reset in order to prepare to flash it and ran into the same cache issue. I tried everything and still couldn't get around it, almost bricked my phone, got stuck in a loop. Hadn't even done anything yet, except download the cm9 Rom. Also freezes when trying to wipe cache and when trying to restore a backup when it gets to the cache. I'll be keeping an eye on your post, and Ill let you know if I figure anything out as well.
Click to expand...
Click to collapse
Thank you my friend. What you describe is exactly what happened to me. Tell me, what version of CWM Recovery do you have? Were you coming from stock? Which CM9 was it? Nightly, stable?

mintharis said:
I've been reading that CWM v6.0.1.4 is causing problems with our phone. Would advise downgrading back to 5.0.2.7 and use the darkside scripts to wipe. I haven't had an issue with this version since it was released (other than needing to use darkside scripts lol).
Click to expand...
Click to collapse
Please pardon my ignorance as I am relatively new at all this. How do you downgrade CWM? I am unable to boot the phone into the ROM. Can it be done through Recovery? ODIN?

I've looked around but I can't find a download for 5.0.2.7-- at least not one that's labeled specifically for our phone. It can be done in many different ways, flashing via recovery or Odin would definitely work, just need to find the right file.

Same version as you've got. Was actually coming from Jedi Mind Trick v8 and was going with the nighty. I loaded a backup of my stock ICS, which of course froze during the restore once it got to the cache, but I let it sit for like 15 min or so and then reset it and surprisingly it loaded up fine despite the fact that I had to reset it during the restore. I'm trying to follow up with the advice these two guys gave me on my post (really the same thing they've told you). With my extremely limited knowledge in this field I'm still working it all out and trying to make sure I ask the stupid questions so as not to mess anything up, well at least not too bad, lol.

mintharis said:
I've looked around but I can't find a download for 5.0.2.7-- at least not one that's labeled specifically for our phone. It can be done in many different ways, flashing via recovery or Odin would definitely work, just need to find the right file.
Click to expand...
Click to collapse
Go into rom manager and scroll down to previous versions

VoiD_Dweller said:
Go into rom manager and scroll down to previous versions
Click to expand...
Click to collapse
I don't have ROM manager installed. Does it provide a tar that can be flashed via Odin?

Newer Recovery
Clockworkmod 6 doesn't need the Darkside tools anymore. I had a similar problem but it was causing my phone to lock up. Just try using the regular cache wipe and dalvik cache wipe and see if that works for you.

mintharis said:
I've been reading that CWM v6.0.1.4 is causing problems with our phone. Would advise downgrading back to 5.0.2.7 and use the darkside scripts to wipe. I haven't had an issue with this version since it was released (other than needing to use darkside scripts lol).
Click to expand...
Click to collapse
I can confirm this, I have a samsung galaxy S II and I was having HUGE problems with the newer version of CWM. Cache would not clear at all even with darksides super wipe. My CM9 was stuck in a boot loop because I had forgotten to clear my cache and factory reset, and I was not able to do this at all, so i thought i was screwed.
However what i did was flash an older version of CWM (5.0.2.7) through odin, and BAM I was able to clear all my data with no problem and reflash CM9. Works perfectly now.

Pugnap00 said:
I can confirm this, I have a samsung galaxy S II and I was having HUGE problems with the newer version of CWM. Cache would not clear at all even with darksides super wipe. My CM9 was stuck in a boot loop because I had forgotten to clear my cache and factory reset, and I was not able to do this at all, so i thought i was screwed.
However what i did was flash an older version of CWM (5.0.2.7) through odin, and BAM I was able to clear all my data with no problem and reflash CM9. Works perfectly now.
Click to expand...
Click to collapse
Can you please provide a link for the 5.0.2.7 tar you flashed?

mintharis said:
I've been reading that CWM v6.0.1.4 is causing problems with our phone. Would advise downgrading back to 5.0.2.7 and use the darkside scripts to wipe. I haven't had an issue with this version since it was released (other than needing to use darkside scripts lol).
Click to expand...
Click to collapse
CWM v6.0.1.4 has pretty much made my phone useless. When in Recovery I can't even scroll down or up. I even tried restarting my phone to downgrade but I have no response from my MENU, HOME, BACK or SEARCH button.
WORD OF ADVICE. PLEASE STAY AWAY FROM CWM v6.0.1.4.

EdwardLThompson said:
I was running CM9 and then went to MIUI and then back to CM9. Ever since I have not been able to do a proper update to the CM9. Got fed up with it and tried to roll it back to one of the Nandroid backups. It got stuck for hours. Pulled the battery. Tried to go through the process of installing CM9 again fresh. Used Darkside SuperWipe and it kept freezing on "Wiping Cache" and the same thing when I use CWM (v6.0.1.4)! I have attached two screen shots. It reads:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
Then when I ask it to format the cache it get frozen.
How can I fix the cache? I cannot boot into CM9 or anything for that matter. I just get the awesome little Cyan Dude and the warp background flying at me continually until I pull the battery. Can anyone help? Is there any way to get ADB to work with out turning on USB Debugging on the phone?
Click to expand...
Click to collapse
Simple Solution is that the Cache in your device is large, it has to be cleaned, For this use Darkside cache wipe. It Solves the problem.

suffuciently hungeom
mintharis said:
Can you please provide a link for the 5.0.2.7 tar you flashed?
Click to expand...
Click to collapse
Here you go,
Look at step 6, it will have links to the tar based on your carrier. Its actually 5.0.2.6, works just the same though.
http://theunlockr.com/2011/12/01/how-to-root-the-samsung-galaxy-s-ii-all-versions/
I hope this helps you!

That happened to me as well when I was going to update to CM10. The faq for CM10 says you need to update to a Touch version of CWM which ROM Manager really wanted to install the Touch version. CWM shows it's version 6 and the menus were different but when I was finally able to get a ROM to boot in Safe Mode it reported CWM as being version 5.x. I could not mount or dismount the Cache in CWM. ODIN brought it back to stock but I messed around with the partition checkbox and hard bricked it. Otherwise it looked as tho things would have been ok after using ODIN to start over.
Darkside's wipe wouldn't work (either version) in this case.

screw cwm im going to twrp
ok same thing happened to me..but there are files i need in the phone and i dont think i want to use cwm after this...so can i use odin to flash it to twrp and recover my files through the twrp usb mount?
(lol nvm, i flashed a older version of cwm through odin and then recovered my files then got twrp)

mintharis said:
I've been reading that CWM v6.0.1.4 is causing problems with our phone. Would advise downgrading back to 5.0.2.7 and use the darkside scripts to wipe. I haven't had an issue with this version since it was released (other than needing to use darkside scripts lol).
Click to expand...
Click to collapse
Like I said in my earlier post had your exact problem and did exactly what was recommend here, and it worked beautifully. Solved all my problems, no residual effects to speak of. Now I can flash my roms in peace.

recovery help please

hi i have a major issue this morning i flashed the dark one viper theme on my m8 i am rooted soff after it installed i hit the reboot button but when it rebooted it hung at boot screen so i hard rebooted and went to recovery which is philz recovery i then wiped cache and dalvic and rebooted but it still got stuck at the boot screen so i reentered recovery it took longer to load than usual and i was greeted with this message at the bottom of the screen
E: could not mount /data to setup /data/media path i tried to restore my nandroid backup but it failed at the data partion i also restored recover settings to default just incase id accidently pressed something i shouldnt have as the touchscreen is quite sensitive but nothing has worked does anybody know how i can fix this issue please i really need my phone any advise on this would be most appreciated thank you

Try to reflash recovery and see if it fixes the mounting problem. If it does restore your nandroid
Edit: or first try to wipe /data, /system, /cache and dalvik and then restore nandroid

thanks
thank you ill give it a try is this a common issue then its had me worried

You're telling that you are rootet. But are you also running the Viper ROM.? Guess you do as you flashed a corresponding theme.
If not the problem could be cause by flashing a Viper theme on a ROM not intended to work with it .
Sent from my HTC One_M8 using XDA Free mobile app

HTCNerdYoda said:
You're telling that you are rootet. But are you also running the Viper ROM.? Guess you do as you flashed a corresponding theme.
If not the problem could be cause by flashing a Viper theme on a ROM not intended to work with it .
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
yes sorry i am running viper rom it was updated yesterday but the theme wasnt so i asked in the theme thread and he said it was fixed to work with viper 2.1.0 so i downloaded and flashed it it flashed fine but after rebooting this happened thanks for the reply any advise is apreciated

Yeah, sounds like the theme is not compatible. Reflash the ROM.

BenPope said:
Yeah, sounds like the theme is not compatible. Reflash the ROM.
Click to expand...
Click to collapse
i tried doing a restore but it failed at the data partition ill try a reflash too thank you

stathis95194 said:
Try to reflash recovery and see if it fixes the mounting problem. If it does restore your nandroid
Edit: or first try to wipe /data, /system, /cache and dalvik and then restore nandroid
Click to expand...
Click to collapse
tried wiping data system ect. but its says error mounting data formatting system worked i also tried installing the rom but its says cant mount sd card format cache didnt work either

now when i power down from recovery it says apply root this is getting worse

Are you using twrp? Try to fix permissions. If it doesn't work maybe for some reason you lost root? Try to reflash supersu maybe?

atm im using philz but i was advised to wipe system ,data , and caches and now i have no sofware on the phone and i cant install anything as it cant mount data partion or internal sd card im not sure what to do someone has said to do a full wipe flash via sneakyghosts thread but im kind of lost and i have no idea what i need to do

Philz has fix permissions as well I think. Try it first...or as I suggested try to reflash supersu maybe you lost root

i cant find fix perms anywhere i flashed supersu but im still getting the error thanks but still nothing working

i started to flash viper rom again it failed but it seems to have fixed the su problem but i still cant acess internal sd card or data partition any ides please would be apreciated thanks

Can you try to reflash Philz?
If you have no success can you try and flash TWRP and see if it makes any difference? I'm just trying to eliminate all variables.

stathis95194 said:
Can you try to reflash Philz?
If you have no success can you try and flash TWRP and see if it makes any difference? I'm just trying to eliminate all variables.
Click to expand...
Click to collapse
thank you im going to have to find them as i sent my phone to a shop to rooted but im sure that wont be too hard
ok got philz from its op as i already made a post in there i will trh that and get back to you thanks

Flash all the things!

i have reflashed philz and it still isnt reading internal sd or my data partition
edit same problem with twrp i tried fixing perms but it failed at data partion

I have your solution ?
Why?
Because I had exact same problem as you have now.
I'm on venom rom. Flashed 2.0.0 rom had not updated firmware however.
After flashing theme Viper dark I got very, very, very long boot time.
After 15 mins or so I hard "button rebooted" device. Resulting in data block being totally corrupted.
As your virtual SD card is a partition on /Data, and data is totally corrupted you won't see or be able to mount your SD card too.
Reflashing recovery, rom or whatever won't help /data stays corrupt.
Now the best part....
I got the tools for you to make your data block fine again, so it again can be mounted and you can see and use the internal sdcard.
You will of course loose anything on the data and virtual sdcard so you must flash a rom after fixing data.
Tools are on my pc, and I'm on my phone right now so I will upload it later and give you link and instructions.
That is if you still have this problem.

Vi553r said:
I have your solution ?
Why?
Because I had exact same problem as you have now.
I'm on venom rom. Flashed 2.0.0 rom had not updated firmware however.
After flashing theme Viper dark I got very, very, very long boot time.
After 15 mins or so I hard "button rebooted" device. Resulting in data block being totally corrupted.
As your virtual SD card is a partition on /Data, and data is totally corrupted you won't see or be able to mount your SD card too.
Reflashing recovery, rom or whatever won't help /data stays corrupt.
Now the best part....
I got the tools for you to make your data block fine again, so it again can be mounted and you can see and use the internal sdcard.
You will of course loose anything on the data and virtual sdcard so you must flash a rom after fixing data.
Tools are on my pc, and I'm on my phone right now so I will upload it later and give you link and instructions.
That is if you still have this problem.
Click to expand...
Click to collapse
exellent thank you so much i appreciate it very much yes i do still have the problem ive been researching all day and asking in various threads i have something on standby but ill wait to see what you did as you have alraedy encountered this problem thank you again