Database Develop

an odd problem

Howdy friends. I recently rooted and installed cyan 4.0.1/teds hero. Everything was going smooth until about 20 min ago. The messaging app kept force closing everytime I would open a thread, so I rebooted. Upon startup, it said my sd card is now damaged. I clicked format, and nothing happened at all. what's the solution? Any help would be appreciated.

i assume your doing auto apps 2 sd with an ext2/3/4 partition? go to recovery and repair ext filesystems. that should fix you up.

I did nothing beyond rooting / cyan / teds hero.

christpuncher said:
I did nothing beyond rooting / cyan / teds hero.
Click to expand...
Click to collapse
k. if you did not partition the sdcard, then take the sdcard out of the g1 (unmount it first in settings), and put it in your pc. try to get the data off of it as best that you can. repartition and format as fat/fat32. put the data back on it, then stick it back in your g1 and see if you can access it, etc.
good luck.

your sd card corrupted, gonna have to reform it, if you install the recovery image from the mytouch that is floating around in the android devolpment forum under new recovery that has an option of reformating your sd card.into 3 partions that would work for you than reflash your rom and theme

here is the link to it. just use in terminal (after putting on root of sdcard also make sure that cyanogen's 1.4 is on the root of your sdcard as well, also for safe keeping have your cm 4.0.x rom on sdcard too)
Code:
su
flash_image recovery /sdcard/recovery-RAv1.2.1G.img
reboot recovery
then once it boots into recovery use the option to format your sdcard into 3 partitions then once it is finished reflash your rom to activate apps2sd, then once it boots up go to the terminal and type
Code:
su
flash_image recovery /sdcard/cm-recovery-1.4.img
that way you will have easily partitioned your sdcard, got apps2sd workning, then return to a recovery image with a recovery console!

I agree with you on having a recovery console but that mytouch recovery is a great way to point noobs since it will easily partion the card for them

gridlock32404 said:
I agree with you on having a recovery console but that mytouch recovery is a great way to point noobs since it will easily partion the card for them
Click to expand...
Click to collapse
thats why i included the steps to going back to the 1.4 recovery after using maybe cyanogen will look into this for his next recovery image. i also sent nephron a pm to see if he would like to include it into his partitioning guides

I hope he does make it into 1.5 for us because it just his 1.4 with some great additions and just missing the console

Huge Problem With Cyanogen Auto Apps2sd

So I partitioned my sd card so i would be able to automatically have apps to sd like the faqs of the cyanogen mods said, but now that i have done the process and partition my sd card 500mb ext, 34mb linux swap, not only has it not worked and the apps are still taking up memory on my phone, it is not noticing the secondary partition in the settings and when i reboot my phone, after the g1 screen and android screen, my phone just goes blank. does anyone have any input? ive wiped and reflashed the rom, now im just clueless. and if it matters, i used Paragon Partition Manager to partition my sd card.

You could re-partition it by using the console in recovery mode.
http://forum.xda-developers.com/showthread.php?t=533731
Look at the 2nd code box and follow it. This is how I did it my first time.
It is really easy.

yea the only thing is it is either saying not found, or error could not stat device dev/block/mmcblk0 no such file or directory. so im stuck i cant even format my card and get back to 8 gigs its sayin 6.06 gigs. ionno im stuck.

Can't you use your partition manager to delete the partitions you made? Then just make 1 partition: fat32, then use the code on the link.
I use paragon Partition mgr. and that is an option to use.

If you partion your card after flashing your rom, then you must reflash your rom for changes to take effect. You have to do that so the system can change the way it runs

Oops sorry, I just reread your first post and saw that I missed that you did reflash. Try going into your recovery console and type ums_enable to mount your card and than try downloading gparted and try to reformat that way, when you are done type ums_disable to unmount. Have you tried taking your sd out when you try to boot up just to see if you can get past, it is possible that your sd corrupted

its ok thank you both, i used the recovery erase all partitions and im gonna read the second box and partition threw the console instead of on the manager.

I just had the same thing happen to me earlier today. I have the 404 Cyanogen MOD and now my SD card is stuck. I can't figure out how to get rid of that partition. All of the directions are not step by step. And this rookie is stressed out. Please let me know where or which directions you used to format your SD.

surfereddie said:
I just had the same thing happen to me earlier today. I have the 404 Cyanogen MOD and now my SD card is stuck. I can't figure out how to get rid of that partition. All of the directions are not step by step. And this rookie is stressed out. Please let me know where or which directions you used to format your SD.
Click to expand...
Click to collapse
To get it back to just a fat32 partition.... THIS WILL WIPE ALL DATA ON YOUR SDCARD!!!! MAKE A BACKUP OF FAT32 also this will only work with 1.3.1 and up cyanogen recovery image
boot into recovery and go to the recovery console and type
parted /dev/block/mmcblk0
rm 1
rm 2
rm 3 (if you have a linux-swap partition)
print (after the 4th or 5th line there is a number after a line that reads disk size or something and that will be the end value for the next command. Sorry on my g1 now)
mkpartfs primary fat32 0 xxxx(substitue with number above)
quit
reboot recovery
Then reflash your rom. That will clear all partitions of your sdcard and leave you with one whole partition that is fat32.

G1 fails at flashing and reboots

hey, I had Mighty Max's Hero rom installed onto my phone running perfect and I was happy, until today. My phone is randomly rebooting for no reason what so ever. Started yesterday morning with just one reboot and didn't think much of it then when I woke up today it was going crazy and now its just frustrating. So in my frustration I backed up my phone and put a new rom
http://forum.xda-developers.com/showthread.php?t=579674
Now when I flash it goes through everything and then says
Code:
E:Can't chown/mod /system/ (Too many open files)
E:Failure at line 22: set_perm_recursive 0 0 0755 0644
SYSTEM:
Can anyone help me out on this
Specs are in sig.

ok here is what you do, you gotta reformat and repartition your sd card, load a new NON HERO ROM on your sd card, and flash it. that SHOULD do the trick.
i know its a pain in the ass but i have had to do it a couple of times. may i suggest cyanogens rom? its really easy to flash, you just have to flash a .zip before you flash his rom. he has a WIKI. its super easy and pretty stable.

haha oh geeze I did that just before I installed Mighty Max >.<
well, i'll give it a whirl haha.
Thanks for the reply
Edit: It didn't work, I still get errors =/

Did you wipe? Wipe ext?
fix_permissions?

fenixnr said:
Did you wipe? Wipe ext?
fix_permissions?
Click to expand...
Click to collapse
Yes sir, I always do
Wipe Data/Factory
Wipe Ext
Repair Ext
Wipe Data/Factory
install rom
I don't understand why its doing this.

I noticed your using Amon Ra 1.2.3. I was having a problem with the ROM not staying on my phone until I went back to Cyanogen 1.4. Weird any time the phone was plugged in and I rebooted the ROM was gone. Try flashing and after flash unplugging, reboot and get Cyanogen back on there. Just a thought.

Chadzworld said:
I noticed your using Amon Ra 1.2.3. I was having a problem with the ROM not staying on my phone until I went back to Cyanogen 1.4. Weird any time the phone was plugged in and I rebooted the ROM was gone. Try flashing and after flash unplugging, reboot and get Cyanogen back on there. Just a thought.
Click to expand...
Click to collapse
I wasn't able to flash any roms besides a few selected, i wasn't even able to flash Cyanogen's, that even shocked me. It always flashed no matter what.
I reflashed the Mighty Max after thinking that maybe me deleting everything would fix the rom, turns out it doesn't.
When my phone goes idle, it freezes up and restarts from a crash.
I guess its when I get a text, but not all the time though.

CrazyEye said:
I wasn't able to flash any roms besides a few selected, i wasn't even able to flash Cyanogen's, that even shocked me. It always flashed no matter what.
I reflashed the Mighty Max after thinking that maybe me deleting everything would fix the rom, turns out it doesn't.
When my phone goes idle, it freezes up and restarts from a crash.
I guess its when I get a text, but not all the time though.
Click to expand...
Click to collapse
Are you wiping your Ext3 with Amon Ra Recovery 1.2.3? If so, go to recovery drop to console and hit enter, then mkefs2 -j /dev/block/mmcblk0p2 enter. Wait, let it do its thing. Then,
reboot recovery enter. Now flash and proceed to reflash your recovery back to Cyanogen 1.4. If this fails, you may want to go back to RC29. Sounds like alot of work but at least you'll have a functioning phone.

Chadzworld said:
Are you wiping your Ext3 with Amon Ra Recovery 1.2.3? If so, go to recovery drop to console and hit enter, then mkefs2 /dev/block/mmcblk0p2 enter. Wait, let it do its thing. Then,
reboot recovery enter. Now flash and proceed to reflash your recovery back to Cyanogen 1.4. If this fails, you may want to go back to RC29. Sounds like alot of work but at least you'll have a functioning phone.
Click to expand...
Click to collapse
I tried typing the first command and it wouldn't work. Maybe you typo-ed it?
mkefs2?
Can I use this code to do the same?
# mount -o rw /dev/block/mmcblk0p2 /system/sd
# rm -rf /system/sd/*
# reboot recovery

./fastboot erase recovery
./fastboot flash recovery *name of whatever you named the Cyanogen recovery image*
./fastboot reboot
Click to expand...
Click to collapse
The reason I added "*name of whatever you named the Cyanogen recovery image*" is because I tried flashing Amon Ra's 1.2.3 the same way using the default name but Terminal said I couldn't flash, so I just named it "recoveryimage.img."

blackknightavalon said:
The reason I added "*name of whatever you named the Cyanogen recovery image*" is because I tried flashing Amon Ra's 1.2.3 the same way using the default name but Terminal said I couldn't flash, so I just named it "recoveryimage.img."
Click to expand...
Click to collapse
Hmm I did that as well
in console I put
Code:
cd C:\
fastboot flash recovery cm.img (cm.img is what i named the Cyanogen recovery)
fastboot reboot
It still gives me the same error when trying to install most roms, even in the CM rom.

REFLASH THE HAYKURO "DEATH/DANGER" spl!
it'll repartition (also wipe) your phone's internal phone memory if you haven't already done so,
it's usually the cause since some roms are too big and leave residual files
next stop to ensure a clean install is to just do a data/cache wipe from the recovery menu
now you wanna either wipe/format your ext partition or just repartition your entire sd card for the heck of it
then repair ext partition,
then wipe again
then flash flash flash

phamous said:
REFLASH THE HAYKURO "DEATH/DANGER" spl!
it'll repartition (also wipe) your phone's internal phone memory if you haven't already done so,
it's usually the cause since some roms are too big and leave residual files
next stop to ensure a clean install is to just do a data/cache wipe from the recovery menu
now you wanna either wipe/format your ext partition or just repartition your entire sd card for the heck of it
then repair ext partition,
then wipe again
then flash flash flash
Click to expand...
Click to collapse
Is this the death / danger spl?
http://code.google.com/p/sapphire-port-dream/
if it is, I already have it =/

yeah that's the one, but DO IT AGAIN anyways
because it also cleans out the system.

Do I need to flash the radio again as well or just the SPL?

most times when trouble shooting these things, you'd want to repeat steps to ensure that what you're doing and what you have done at the moment aren't causing your problems, only by redo-ing these steps can you validate what's a problem and what's not, and in the process you'll most likely find a solution!
so try repartitioning, wiping, and reflashing the radio and spl, and finally reflashing your rom

just reflash both
radio, then spl
you wanna make sure everything's in good order.
sometimes if all these things don't work, it might just be your sd card has crapped out on you
and its time to get a new one, sd cards and the flash memory on them are limited to however many read and write cycles and if you've been using linux swap on them, then you're using your sd card as RAM pretty much.

phamous said:
just reflash both
radio, then spl
you wanna make sure everything's in good order.
sometimes if all these things don't work, it might just be your sd card has crapped out on you
and its time to get a new one, sd cards and the flash memory on them are limited to however many read and write cycles and if you've been using linux swap on them, then you're using your sd card as RAM pretty much.
Click to expand...
Click to collapse
I haven't been using my SD card as ext for long though.
I did what you said and it still says the same error.
I even went ahead and installed a new recovery through fastboot to Cyanogen.
EDIT:
I brought the phone back to RC33 and rerooted then upgraded recovery CM 1.3 and Haykuro Death SPL and Latest Radio and I still get the error code.....
I'm going to break this phone >:-(
SenseHero writes but doesn't boot, any reason why?

Sorry about that, check my OP post forgot the -j.

Chadzworld said:
Sorry about that, check my OP post forgot the -j.
Click to expand...
Click to collapse
it says
Code:
mkefs2 : not found

Can't apply ZIP updates. HELP! Wave invites for help.

OK.
So for the last week or two I've been trying to get myself fixed in this thread:
629469
You can read that for some background info. Seeing as this a new problem, I've posted a new thread.
I've pushed SuperD, signed-spl (danger) and ota-radio 2_22_19_26i to the phone.
But now I cant apply these updates. I choose "apply sdcard:choose zip"
and it says:
e:can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(Invalid Argument)
E:Can't mount SDCARD:
HELP.
Wave invites for help (I'll try that one again)

I've run into the same problem but I got there a slightly different way.
I recently switched ROMs from kingklick's aosp 2.1 v1.5 to openeclair 1.5, and I wanted to switch back. I went to do the usual partition, wipe everything, apply update.zip and I got almost exactly the same error message that you got:
E: can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(File not found)
E: can't mount SDCARD:
With my limited knowledge of Unix, I decided to jump into the console and dig around in the dev folder, I didn't see anything in /dev/block that was called mmcblk0, there were several files called "loopX", and also "mtdblkX".
It seems like my phone is acting as though I do not have an SD card at all. I've been testing out different things, I started the process over again by trying to partition the SD card and noticed it finished almost instantly. And now when I connect it to the computer and turn on the USB connection, my computer does not recognize it as a storage device. I then popped out the SD card and put it into the computer itself, it seems fine but there were some extra dm files that I did not expect to see. Not sure what those files are or how they got there.
I have the Death SPL, and the last ROM I used was KingKlick's AOSP 2.1 v1.5
Does anyone out there have any idea why this happened or how I can fix it?

Both of you, it sounds like your sd card is formatted wrong or corrupt. From amon-ra recovery you should try to wipe again, including the SD, and repair SD EXT. If that doen't work go back and use the "format SD" option.
One more thing, please take a few minutes and put together a signature on the forum with all your info, phone, spl, rom, sd setup, what you like for breakfast, all that stuff. Much easier to tell where to start.
Edit...if this should happen to accidentally work, please don't send any wave invites. I will probably never get rid of my 25.

Wipe data - worked (supposedly)
Wipe dalvik - Error : Run 'wipe dalvik' via console!
Wipe SD:ext partition - Error : Run 'wipe ext' via console!
Repair SD:ext - Error : Run 'fs repair' via console!
I don't see an option for "Format SD" in Amon Ra's recovery v1.5.2, so I attempted to Partition SD and give 0 space to swap and ext2. That SAID it completed successfully, but it finished suspiciously fast, and upon inserting the SD into my computer, I can see that it was not re-partitioned nor wiped.
I went into the console and tried the commands mentioned in the error messages and got "No ext partition found!" from each command. I then went back to recovery to "partition" the SD with Swap - 192MB, Ext2 - 1024MB, Fat32 - remainder (approx 2.75GB). I then tried wiping and repairing again, and got the same error messages, then went back to console to try wiping from there, and again was told "No ext partition found!"
I noticed that my SD is class 4, but class 6 is recommended, I'm considering going to buy a new class 6 SD, do you think that will help?
Filled in my sig, did I miss any info?

dracoaffectus said:
Wipe data - worked (supposedly)
Wipe dalvik - Error : Run 'wipe dalvik' via console!
Wipe SD:ext partition - Error : Run 'wipe ext' via console!
Repair SD:ext - Error : Run 'fs repair' via console!
I don't see an option for "Format SD" in Amon Ra's recovery v1.5.2, so I attempted to Partition SD and give 0 space to swap and ext2. That SAID it completed successfully, but it finished suspiciously fast, and upon inserting the SD into my computer, I can see that it was not re-partitioned nor wiped.
I went into the console and tried the commands mentioned in the error messages and got "No ext partition found!" from each command. I then went back to recovery to "partition" the SD with Swap - 192MB, Ext2 - 1024MB, Fat32 - remainder (approx 2.75GB). I then tried wiping and repairing again, and got the same error messages, then went back to console to try wiping from there, and again was told "No ext partition found!"
I noticed that my SD is class 4, but class 6 is recommended, I'm considering going to buy a new class 6 SD, do you think that will help?
Filled in my sig, did I miss any info?
Click to expand...
Click to collapse
to format it, just go to partition, then select 0 for the first two and rest for fat 32. You don't need a new card unless you're running a hero rom, and a class 4 is actually pretty fast. If formatting it doesn't work its done. This happened to me on a brand new class 6 transcend. Sent it back and got a sandisk. Good luck

I have the same problem wiht my G1 and am sending back my phone to HTC for this.
I have made a post here:
http://forum.xda-developers.com/showthread.php?p=5594269
All our phones have activated a memory debugging mode from from hboot. Modifying anything while booted to recovery or system doesn't affect anything because the trigger is happening from hboot.
You can still use fastboot while stuck in this mode. But your phone has no sd card access at the moment because it is locked by the hboot for writing debug logs.
I found that I was not able to flash in fastboot, as my hboot showed S-ON. However it was still possible to use fastboot boot.
Run cat /proc/cmdline
You will see that it says something like the following:
board_trout.disable_uart3=1 board_trout.usb_h2w_sw=1 board_trout.disable_sdcard=1 smisize=64 androidboot.baseband=3.22.26.17 androidboot.cid=ROGER001 androidboot.carrier=Rogers androidboot.keycaps=qwerty androidboot.mode=normal androidboot.serialno=HT********** androidboot.bootloader=1.33.2005 no_console_suspend=1 con
sole=null
You could mount the cache partition to your sdcard directory for flashing files:
adb shell mount -t yaffs2 /dev/block/mtdblock4 /sdcard
I've had this problem for more than a week. I have tried changing SPL, unrooting, recompiling my boot.img, and appending kernel commands.
You can also force your recovery/system to mount the sdcard, but your phone will error out because both the hboot and system will try to write to the sdcard. There is a high chance of corrupting the sd card (correctable by reformatting) this way, but you can generate a gold card:
fastboot -c "board_trout.disable_uart3=0 board_trout.usb_h2w_sw=0 board_trout.disable_sdcard=0" boot recovery.img
The -c switch appends to the kernel cmdline at the end.
There is a working solution if you have SPL 1.76.x in your HBOOT. The command to disable memory debug logs is simply
fastboot oem enableqxdm 0
However I have never seen this SPL for the dream. 32B magic users who flashed this SPL with the accompanying radio ended with semi-bricks, with their SPLs showing 32A board. Attempts to downgrade back to 1.33.x have not worked. Here's the thread:
http://forum.xda-developers.com/showthread.php?t=625604
I did theorize that we might have been able to upgrade our spl and radio to 1.76.x, run the enableqxdm command, and then downgrade back to 1.33.2010 using the test ruu. The 1.33.2010 works for the 32A magic, the 32B magic and the dream. This is one of the variants of the so called danger spl. If you have 1.33.2005 you already have a spl from the magic.

hiddengopher said:
to format it, just go to partition, then select 0 for the first two and rest for fat 32. You don't need a new card unless you're running a hero rom, and a class 4 is actually pretty fast. If formatting it doesn't work its done. This happened to me on a brand new class 6 transcend. Sent it back and got a sandisk. Good luck
Click to expand...
Click to collapse
Ok, I tried that already and it didn't work. So you're saying the SD card is useless now and I just need to get a new one?
and Xaueious, I read your post and I have one question. What do you recommend I do?

dracoaffectus said:
Ok, I tried that already and it didn't work. So you're saying the SD card is useless now and I just need to get a new one?
and Xaueious, I read your post and I have one question. What do you recommend I do?
Click to expand...
Click to collapse
Try this first.
Enter recovery then console
1. type parted /dev/block/mmcblk0
2. type rm 2 to remove ext
3. type rm 3 to remove swap
to resize fat32:
4. type print to get start value and sdcard size
5. type resize 1 <start> <sdcard size> (if i were doing this for my card it would be resize 1 512B 8169M)
Then put the card in computer and format fat32. (just to be sure)
Put it back in the phone and recovery and partition.
If no other way works, the card may be corrupt.
You could use GPARTED in linux for this. Even a GPARTED live cd would be good. In fact that may be your best option.

billquinn1 said:
Try this first.
Enter recovery then console
1. type parted /dev/block/mmcblk0
2. type rm 2 to remove ext
3. type rm 3 to remove swap
to resize fat32:
4. type print to get start value and sdcard size
5. type resize 1 <start> <sdcard size> (if i were doing this for my card it would be resize 1 512B 8169M)
Then put the card in computer and format fat32. (just to be sure)
Put it back in the phone and recovery and partition.
If no other way works, the card may be corrupt.
You could use GPARTED in linux for this. Even a GPARTED live cd would be good. In fact that may be your best option.
Click to expand...
Click to collapse
also, you're going to want to go to "go to console" in recovery to do this

billquinn1 said:
Try this first.
Enter recovery then console
1. type parted /dev/block/mmcblk0
2. type rm 2 to remove ext
3. type rm 3 to remove swap
to resize fat32:
4. type print to get start value and sdcard size
5. type resize 1 <start> <sdcard size> (if i were doing this for my card it would be resize 1 512B 8169M)
Then put the card in computer and format fat32. (just to be sure)
Put it back in the phone and recovery and partition.
If no other way works, the card may be corrupt.
You could use GPARTED in linux for this. Even a GPARTED live cd would be good. In fact that may be your best option.
Click to expand...
Click to collapse
I went to console and typed "parted /dev/block/mmcblk0" and it said "Error: Could not stat device /dev/block/mmcblk0 - No such file or directory"
I tried "parted /dev/block/mtdblock0" instead and got into parted, but when I tried any command such as "print", I got "Error: /dev/block/mtdblock0: unrecognised disk label"

dracoaffectus said:
I went to console and typed "parted /dev/block/mmcblk0" and it said "Error: Could not stat device /dev/block/mmcblk0 - No such file or directory"
I tried "parted /dev/block/mtdblock0" instead and got into parted, but when I tried any command such as "print", I got "Error: /dev/block/mtdblock0: unrecognised disk label"
Click to expand...
Click to collapse
I would say the sd card is dead. Try someone else's or a spare.

Picked up a 2GB microSD at the store for like $10 and got the same results right from the beginning.
So this means it's something wrong with my phone, and not the SD card.
Any suggestions?
....can I unroot?
I don't know if this matters, but I noticed some dm files on my sdcards after trying to startup my phone.
EDIT: I managed to UNroot my phone back to RC29 following the instructions on theunlockr.com. Now I have to contemplate if I'm ready to jump straight back into hacking again.
EDIT2: Ok, so now I'm back on the latest OpenEclair. The key to "fixing" it was to get a totally clean start by UNrooting my phone (http://bit.ly/5qbzIU thanks Unlockr.com). I wasn't able to do step 1 cause I was getting the same errors as before, so I skipped straight to loading the DreaIMG.nbh file, then continued to update to cupcake, load the latest radio, danger SPL, and openEclair, now my phone is working again. (p.s. already on Wave, so no need to send that invite Lachy95 )

Thanks
Its all fixed.
Used a different sd card, im stupid.
Thanks you thank you thank you
ill always remember

Can't find a partition option

I've been crawling forums looking for several ways to partition my SD, but to no avail.
Recently upgraded from damagecontrol 2.08 to 2.09. Bought a new 8gb micro SD.
I'd like to partition the SD card so that Apps2SD runs, and I remember the first time I rooted my phone and loaded a rom, there was an option in recovery to partition the SD card. Now, my phone boots into clockworkmod recovery v1.8.1.4, and the list of commands doesn't include a card partition option.
How can I get this option back?
I resorted to using adb and trying to work around this problem through the command line, but all of those attempts failed. "parted not found" etc.
I'm at my wit's end and my school work is suffering! (I'm crazy if my phone is not working perfectly) PLZ help this girl stay in med school!

you could flash back to godspeed or darch's unofficial 1.7 recovery found here both these recovery images have the option. clockwork must not support partitioning.
or, you could take your card out and put it in your pc and use a gparted livecd (or linux) to partition the card.
remember to backup your data first as re-partitioning will erase all data on the card.

I'd love to flash a new image, but my phone doesn't seem to allow me to. I use flashrec and it won't flash a new image.
Here's the chronology of my troubles
What I did with my rooted and fully functioning hero was...
back up apps
changed SD cards
set to factory settings via an option of the clockwork recovery
updated my rom to damagecontrol 2.09
found that apps2sd wouldn't work
tried to partition- clockwork recovery doesn't support it
tried to get back SU capabilities unsuccessfully
tried to mimic my first flash attempt unsuccessfully with flashrec
Now I'm stuck with a slowed down hero which can't allow Su and won't do apps2SD
I'm at the point of insanity with this thing
any suggestions?