Database Info

[Q] CWM and .android_secure problem

Did anyone find a fix for it yet? Anything that winds up restoring .android_secure causes the phone to hang. It's getting really annoying, not sure if I read about a fix anywhere though.
EDIT
Just saw that this is a dupe thread, check here instead:
http://forum.xda-developers.com/showthread.php?p=14728596

FBis251 said:
Did anyone find a fix for it yet? Anything that winds up restoring .android_secure causes the phone to hang. It's getting really annoying, not sure if I read about a fix anywhere though.
Click to expand...
Click to collapse
You need to have made a clean backup with Krylon360's FINAL CWM, not ROM Manager.
CWM Final is v3.0.2.8
I backed up and restored .android_secure via that version without issue. It's related to the Rom Manager version that causes issues.

Iv been looking into it with dsexton and its a file on your sd card. Also you should only use krylons cwm
Sent from my SGH-T959V using XDA Premium App

I had that problem with the rom manager version of CMW too but if you let it sit on the hangup for a few minutes then just hold the power button until your phone restarts let it boot and your phone will be restored
Sent from my SGH-T959V using XDA Premium App

So I flashed CWM v.3.2.0.0 from ROM manager v.4.3.1.5 but have not yet backed up the phone's original stock ROM. Is there a workaround so I can use krylon360's CWM FINAL instead?

(smint) said:
So I flashed CWM v.3.2.0.0 from ROM manager v.4.3.1.5 but have not yet backed up the phone's original stock ROM. Is there a workaround so I can use krylon360's CWM FINAL instead?
Click to expand...
Click to collapse
Just dont use that..only use kyrlons

no CWM love
Looking for some help here. I am unable to get into recovery and therefore cannot do a nandroid backup and get to ROM-ing / hacking on my phone. Here's what I've done.
In linux I used the following commands to write krylon360's files to my phone:
adb shell
$ su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
#exit
$exit
adb push update.zip /mnt/sdcard
adb push recovery /mnt/sdcard
adb push recovery /system/bin
Next I've tried the following to get into recovery and make a nandroid backup.
1.) simultaneously hold down volume up, volume down and power button.
result: phone stops at Tmobile/GalaxyS splash screen.
if I hold down the power button and reboot, I get a frozen progress star and large battery icon displayed in the middle of the screen. This is the same result for every variation.
repair- pull battery out of phone, put back, power on and execute:
adb reboot
2.) execute: adb reboot recovery
result: phone stops at Tmobile/GalaxyS splash screen.
repair, execute:
adb reboot
3.) selected recovery from ROM Manager
result: phone stops at Tmobile/GalaxyS splash screen.
repair- pull battery out of phone, put back, power on and execute:
adb reboot
Any ideas?

Bricked?? what can I do

Hi all,
I got my replacement phone today. The first thing I wanted to do was to take the phone I am sending back and "unroot" it....Stupid me...I forgot to take the lagfix off....so now after I installed the EE2 rom to go back to stock.....I am in a DROID BOOTLOOP.....does anyone have any suggestions that I may be able to try to get it out of the bootloop? or else I have to take my chances and send it back anyway.....

Use p3droids method on mydroidworld
Sent from my SCH-I510 using XDA Premium App

Or put sd card into new phone. Make a file called disable-lagfix in the voodoo file. Flash voodoo onto bootlooped droid charge that is bootlooped and put sd card into broken charge after you flash it
Sent from my SCH-I510 using XDA Premium App

You should be able to flash a package w/ voodoo kernel like Altered Beast and get out of your boot loop. Then disable lagfix and flash the stock EE4 pkg.

hoppermi said:
You should be able to flash a package w/ voodoo kernel like Altered Beast and get out of your boot loop. Then disable lagfix and flash the stock EE4 pkg.
Click to expand...
Click to collapse
thats what I just did......I installed Gummy Package.....with kernel...voodoo...CWM.....I will report back in a few
EDIT::: yep it worked.....I asked the question before I thought about it....I got it to go...thanks to all that answered my stupid question....I answered it myself LOL

hogowner said:
thats what I just did......I installed Gummy Package.....with kernel...voodoo...CWM.....I will report back in a few
EDIT::: yep it worked.....I asked the question before I thought about it....I got it to go...thanks to all that answered my stupid question....I answered it myself LOL
Click to expand...
Click to collapse
Thanks for answering your own question. Now I don't have to ask the same question.

Couldn't you also have just flashed the stock ED1 Odin package?
http://forum.xda-developers.com/showthread.php?t=1137369
imnuts:
"Flash the ED1 or ED2 full odin package. It will take you back to stock, and you don't need to worry about voodoo being enabled/disabled if you flash one of them as it will also wipe that out."

el_brio said:
Couldn't you also have just flashed the stock ED1 Odin package?
http://forum.xda-developers.com/showthread.php?t=1137369
imnuts:
"Flash the ED1 or ED2 full odin package. It will take you back to stock, and you don't need to worry about voodoo being enabled/disabled if you flash one of them as it will also wipe that out."
Click to expand...
Click to collapse
Yes....I tired both files and it didn't let me load them in ODIN....it keep failing.....
I know it could have been a bad download...but I downloaded them each 3 times and got the same results with EE1 and EE2....
I am going to try over the weekend...don't want to send back the phone to VZ with a custom rom, voodoo and CWR installed LOL
if anyone has a good copy of either file that works with odin, please pm me your e mail address....I will e mail you back...and you can send it to me...this way I KNOW it is a good file...
thanks!

papi92 said:
Use p3droids method on mydroidworld
Sent from my SCH-I510 using XDA Premium App
Click to expand...
Click to collapse
This is for sure the best option seeing as the file is the Full blown flash file. IE like an SBF file for Moto devices.
Here is a link to the info http://www.mydroidworld.com/forums/...harge-full-factory-tar-flashing-software.html

I saw that file..not sure about loading it..it says u need 7z to unzip it and put to install it...not sure how to use. .and put is a few files when unzipped that i am not sure how to go about using it
Sent from my 4g Verizon Charge!

I'm in a worse boat than the OP. Long story short, I started getting all kinds of weird FCs the other day, well after I had flashed my last ROM, which was Gummy 1.7.5, I think -- maybe even 1.5.
Anyway, I figured no biggie, I'll just wipe and flash the 1.7.5 ODIN and then put 1.8 on top of that. About 10 hours later, I'm still not there, and I'm pretty sure I'm screwed. Would like any suggestions.
So far I've tried ODINing back to stock ED1 and ED2, and SamsungPSTing to stock ED1, all of which flash fine, but DROID boot loop. I've tried disabling lagfix, I've tried just leaving it alone, I've wiped and wiped and wiped, all to no avail. Ultimately when flashing to these stock packages the stock recovery gives me the following text when recovery starts, and I can never boot to the OS:
Before "Movie_check Start..!!"
E:Can't mount /dev/block/mmcblk0p1
After "Movi_check done!..."
E:Can't mount /dev/block/mmcblk0p3
(Invalid argument)
E:Can't mount CACHE:recovery/command
# MANUAL MODE #
E:Can't mount dev/block/mmcblk0p3
(Invalid argument)
E:Can't mount CACHE:log/recovery.log
E:Can't open CACHE:log/recovery.log
E:Can't mount dev/block/mmcblk0p3
(Invalid Argument)
Flashing rooted stock ED1 also boot loops. I can get to recovery and wipe a bunch, but to no avail.
The only thing that will kind of work is ODINing Gummy 1.7.5 This will at least boot. Problem is -- and I think this is the "root" of my problem, that programs that I had installed that I've uninstalled (and wiped a million times) keep coming up and causing FCs. It doesn't matter if I uninstall them from Manage Applications, or anything. They're always still there, still somehow on the internal memory. I also get FCs from the Gallery, the Browser, and who knows what else. At least I can make a phone call and send an email tho.
I'm thinking a trip to the Verizon store is in order, but am hoping that someone out there has a magic bullet for me.
Thanks in advance for any assistance, and let me know if I've left out any pertinent info. I really don't know much about this stuff, I've just been doing the script kiddie thing on this stuff, which has worked until yesterday...

I doubt if this fixes anything, but it will give you something to do while someone who knows way more than me can chime in. I read on the GummyCharged thread about people having the Let's Golf app constantly reappear on reboot after uninstalling it. The app ended up being in the /preinstall folder. You can look there and see if all your apps that keep FCing ended up there by some magical chance.

hogowner said:
I saw that file..not sure about loading it..it says u need 7z to unzip it and put to install it...not sure how to use. .and put is a few files when unzipped that i am not sure how to go about using it
Sent from my 4g Verizon Charge!
Click to expand...
Click to collapse
7z is just another program like WinZip or WinRar and it works the exact same way.

rheno said:
I doubt if this fixes anything, but it will give you something to do while someone who knows way more than me can chime in. I read on the GummyCharged thread about people having the Let's Golf app constantly reappear on reboot after uninstalling it. The app ended up being in the /preinstall folder. You can look there and see if all your apps that keep FCing ended up there by some magical chance.
Click to expand...
Click to collapse
Thanks rheno, I'll give that a shot.
I do have that 11MB golf game in there too.

cshorter said:
I'm in a worse boat than the OP. Long story short, I started getting all kinds of weird FCs the other day, well after I had flashed my last ROM, which was Gummy 1.7.5, I think -- maybe even 1.5.
Anyway, I figured no biggie, I'll just wipe and flash the 1.7.5 ODIN and then put 1.8 on top of that. About 10 hours later, I'm still not there, and I'm pretty sure I'm screwed. Would like any suggestions.
So far I've tried ODINing back to stock ED1 and ED2, and SamsungPSTing to stock ED1, all of which flash fine, but DROID boot loop. I've tried disabling lagfix, I've tried just leaving it alone, I've wiped and wiped and wiped, all to no avail. Ultimately when flashing to these stock packages the stock recovery gives me the following text when recovery starts, and I can never boot to the OS:
Before "Movie_check Start..!!"
E:Can't mount /dev/block/mmcblk0p1
After "Movi_check done!..."
E:Can't mount /dev/block/mmcblk0p3
(Invalid argument)
E:Can't mount CACHE:recovery/command
# MANUAL MODE #
E:Can't mount dev/block/mmcblk0p3
(Invalid argument)
E:Can't mount CACHE:log/recovery.log
E:Can't open CACHE:log/recovery.log
E:Can't mount dev/block/mmcblk0p3
(Invalid Argument)
Flashing rooted stock ED1 also boot loops. I can get to recovery and wipe a bunch, but to no avail.
The only thing that will kind of work is ODINing Gummy 1.7.5 This will at least boot. Problem is -- and I think this is the "root" of my problem, that programs that I had installed that I've uninstalled (and wiped a million times) keep coming up and causing FCs. It doesn't matter if I uninstall them from Manage Applications, or anything. They're always still there, still somehow on the internal memory. I also get FCs from the Gallery, the Browser, and who knows what else. At least I can make a phone call and send an email tho.
I'm thinking a trip to the Verizon store is in order, but am hoping that someone out there has a magic bullet for me.
Thanks in advance for any assistance, and let me know if I've left out any pertinent info. I really don't know much about this stuff, I've just been doing the script kiddie thing on this stuff, which has worked until yesterday...
Click to expand...
Click to collapse
Seeing as yours boots somewhat here is what I would do. Flash the stock ED1 file which ever one you prefer or you know that works. Then before even trying to fully boot the first time flash Imnut's CWM to the device using ODIN. If that passes boot into CWM and wipe data/cache and also dalvik. however before booting flash/install Imnut's kernel from in CWM then let it boot and see what you get.

will2live said:
Seeing as yours boots somewhat here is what I would do. Flash the stock ED1 file which ever one you prefer or you know that works. Then before even trying to fully boot the first time flash Imnut's CWM to the device using ODIN. If that passes boot into CWM and wipe data/cache and also dalvik. however before booting flash/install Imnut's kernel from in CWM then let it boot and see what you get.
Click to expand...
Click to collapse
I gave this a shot, but no dice. I could get the ED1 OS to boot, but I'd get stuck in an endless loop of FCs -- every process would FC while on the 1st setup screen. It was worth a shot.
While I was on this non-voodoo, stock except for CWM and imnuts' kernel, I ran a mount command from a shell. This is what I got:
~ # mount
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
nodev on /tmp type tmpfs (rw,relatime)
/dev/block/stl7 on /mnt/.lfs type j4fs (rw,relatime)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/stl10 on /system type rfs (rw,relatime,vfat,llw,check=no,gid/uid/rwx,
iocharset=utf8)
/dev/block/mmcblk1p1 on /sdcard type vfat (rw,nosuid,nodev,noexec,relatime,uid=1
000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso
8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/mmcblk0p3 on /cache type ext4 (rw,noatime,barrier=0,data=ordered)
~ #
I'm way over my head, but after digging around on the web, I'm pretty sure that what's happened is that the mmcblk0p3 (whatever that is -- a chip or memory?) is borked. It's showing as ext4 even though everything else is rfs.
After this last round of messing around, one thing has changed, I've now gotten Root Explorer to install. I'm back on Gummy 1.7.5, and I'm limping along, all the core stuff works, it's just most apps that are broken.
Can any devs out there give me a hand here, or am I toast?
Thanks
PS, now that I have Root Explorer, I looked in preinstall, and the golf game was in there, but that's it.

Instructions to UN-brick
Ok.... I have bricked my phone several times and became an expert at fixing it. This fix wipes everything from your phone and puts you back into a stock EE1 ROM but it makes your phone work again. I am posting the instructions here and am currently uploading the needed files. Will update this post with the links once they are up.
I HAVE PROVIDED PICTURE ATTACHMENTS SO YOU CAN REFER TO WHAT IM TALKING ABOUT
YOU WILL HAVE TO UNZIP TWO OF THESE FILES IF YOU DONT HAVE AN UNZIP UTILITY YOU MAY DOWNLOAD WINRAR FROM HERE.......
http://www.win-rar.com/download.html
1. First download all the attached files and place them somewhere you can find them or just make note of where you downloaded them.
2. Install Samsung USB driver for mobile phone.exe if you had not already done so. If you have used ODIN in the past with your Droid Charge, then you may skip this step for you already have the drivers.
3. Unzip the folder named SAMSUNGPSTlite...zip. Then open the folder and install the setup.exe file
4. When installation is done, install the Samsung SCH-150.msi file
5. Make sure your phone is off, with the battery OUT and connect it to your computer.
6. Hold volume down until your phone responds, i think with a yellow triangle. Once the triangle appears REMOVE THE BATTERY!
7. Open the Samsung Application we just installed. It will probably be under a folder named Phone flashing application. You will probably have to grant it user permission to run when asked.
8. Double click on your phone where the error points in picture 1.
9.Make sure your phone is connected on the lower right hand corner (check picture 2)
10. On the left hand side click on SW Download.
11. Make sure the drop down window says PDA + PHOne update
11. Now check the box that says Boot update.
12. CLick the button that says open AP and search for the file you downloaded AND UNZIPED named something like.... CI50_VZW_ED1 and ends with a .tar extension
13. Now click on Start Download.
14. Your phone will begin loading the information and when the operation is done you are good to go!!!
15. Turn on your phone
16. It will take a while for your phone to completely turn on so just be patient.
SamsungPST SCH-I510 For Verizon.msi
SAMSUNG_USB_Driver_for_Mobile_Phones_v1.3.1900.0.exe
SamsungPSTLite FW Setup1.0.004_MSI1ndEdition.zip
CI510_VZW_ED1_ALL_ONE-LTE-CP_REV03_user_CL986330.tar.zip - 398.55MB

The process will2live mentioned from the myandroidworld website works flawlessly sending you back to stock.
I would try that process and then as the phone reboots at the very end make sure you go into recovery mode prior to it booting up and do a FACTORY RESET but remember you will lose all your data which i assume you shouldn't have any anyhow since you're returning the phone.
This worked for me and hopefully will work for you.
cshorter said:
I gave this a shot, but no dice. I could get the ED1 OS to boot, but I'd get stuck in an endless loop of FCs -- every process would FC while on the 1st setup screen. It was worth a shot.
While I was on this non-voodoo, stock except for CWM and imnuts' kernel, I ran a mount command from a shell. This is what I got:
~ # mount
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
nodev on /tmp type tmpfs (rw,relatime)
/dev/block/stl7 on /mnt/.lfs type j4fs (rw,relatime)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/stl10 on /system type rfs (rw,relatime,vfat,llw,check=no,gid/uid/rwx,
iocharset=utf8)
/dev/block/mmcblk1p1 on /sdcard type vfat (rw,nosuid,nodev,noexec,relatime,uid=1
000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso
8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/mmcblk0p3 on /cache type ext4 (rw,noatime,barrier=0,data=ordered)
~ #
I'm way over my head, but after digging around on the web, I'm pretty sure that what's happened is that the mmcblk0p3 (whatever that is -- a chip or memory?) is borked. It's showing as ext4 even though everything else is rfs.
After this last round of messing around, one thing has changed, I've now gotten Root Explorer to install. I'm back on Gummy 1.7.5, and I'm limping along, all the core stuff works, it's just most apps that are broken.
Can any devs out there give me a hand here, or am I toast?
Thanks
PS, now that I have Root Explorer, I looked in preinstall, and the golf game was in there, but that's it.
Click to expand...
Click to collapse

thareefer said:
Ok.... I have bricked my phone several times and became an expert at fixing it. This fix wipes everything from your phone and puts you back into a stock EE1 ROM but it makes your phone work again. I am posting the instructions here and am currently uploading the needed files. Will update this post with the links once they are up.
I HAVE PROVIDED PICTURE ATTACHMENTS SO YOU CAN REFER TO WHAT IM TALKING ABOUT
YOU WILL HAVE TO UNZIP TWO OF THESE FILES IF YOU DONT HAVE AN UNZIP UTILITY YOU MAY DOWNLOAD WINRAR FROM HERE.......
http://www.win-rar.com/download.html
1. First download all the attached files and place them somewhere you can find them or just make note of where you downloaded them.
2. Install Samsung USB driver for mobile phone.exe if you had not already done so. If you have used ODIN in the past with your Droid Charge, then you may skip this step for you already have the drivers.
3. Unzip the folder named SAMSUNGPSTlite...zip. Then open the folder and install the setup.exe file
4. When installation is done, install the Samsung SCH-150.msi file
5. Make sure your phone is off, with the battery still IN and connect it to your computer.
6. Hold volume down until your phone responds, i think with a yellow triangle.
7. Open the Samsung Application we just installed. It will probably be under a folder named Phone flashing application. You will probably have to grant it user permission to run when asked.
8. Double click on your phone where the error points in picture 1.
9.Make sure your phone is connected on the lower right hand corner (check picture 2)
10. On the left hand side click on SW Download.
11. Make sure the drop down window says PDA + PHOne update
11. Now check the box that says Boot update.
12. CLick the button that says open AP and search for the file you downloaded AND UNZIPED named something like.... CI50_VZW_ED1 and ends with a .tar extension
13. Now click on Start Download.
14. Your phone will begin loading the information and when the operation is done you are good to go!!!
15. Turn on your phone
16. It will take a while for your phone to completely turn on so just be patient.
SamsungPST SCH-I510 For Verizon.msi
SAMSUNG_USB_Driver_for_Mobile_Phones_v1.3.1900.0.exe
SamsungPSTLite FW Setup1.0.004_MSI1ndEdition.zip
CI510_VZW_ED1_ALL_ONE-LTE-CP_REV03_user_CL986330.tar.zip - 398.55MB
Click to expand...
Click to collapse
This worked GREAT!!! the only thing is, I left the battery out not in......if the battery is in and you hold the volume button...nothings happens.....so just take the battery out....hold the volume button...and you are in the download menu screen..yellow triangle...then I put the battery in......then I followed your steps and it worked like a CHARM!!!
now I can return the phone completely STOCK!!!!

Thanks hogowner for pointing that out i fixed it in the original guide.

[EP4D/FP1H/FP5E][MOD][ODIN] Change Boot Splash Image

This is from a whole lot of brainstorming, reading, headaches & lack of sleep. I now understand Odin & Heimdall a whole lot better; & my skills with Samsung Android phones have increased a bit more. I hope that at least one person can benefit from having a modified param.lfs for a custom boot splash.
Let me know if there are any ways that I can improve this post.
Before you begin, this is for the fearless types that know what they're doing or go all out even if they're jumping into a tornado. Your phone may soft-brick if something goes wrong.
Modified Instructions (from kmalinich's thread):
Needed:
Rooted Samsung Droid Charge
Working ADB
Latest Odin3
Hacked param.lfs (attached & mirrored)
New jpeg boot logo size 480x800 (less than 64KB - test to see if larger works)
Steps:
Copy your new splash image (logo.jpg) to your sd card however you'd like.
Remove your SIM card for safe keeping until this process is finished
Start Odin
Enter download mode (reboot to it or disconnect the phone, take out the battery, press the volume down button, plugin the USB cable, wait for the download screen to appear & place the battery back in)
Extract param_mod.tar.md5 from droid_charge_param_mod.zip
Flash hacked param_mod.tar.md5 via Odin3 in the PDA area _*ONLY*_
Reboot into CWM recovery
Mount the system partition from within CWM
Open ADB shell
Enter these commands:
Code:
mount -o remount,rw /dev/block/stl7 /mnt/.lfs
cp /sdcard/logo.jpg /mnt/.lfs/logo.jpg
Reboot and enjoy!
Notes:
I've tested multiple versions of Heimdall with just the modified param.lfs & it fails to upload 99 times out of 100. I recommend Odin3, SamsungPST Lite, or redbend_ua.
The boot splash image only appears for a short while since the Droid Charge kernels have splash images, too. If you'd like the same image for the duration of boot, utilize an app or a guide to change your favorite kernel's splash image.
Mirror:
modded param.lfs - http://db.tt/fjyx4uEf
sample boot splash - http://db.tt/Nj26hmb6
original param.lfs - http://db.tt/HcCZ6O0H
Sources:
Free Your Android - Modifying Samsung Splash Screens (Galaxy S Series + SGS2) <- how I learned to do it
[Mod][ec09] samsung boot splash/image change 7.7.11 - xda-developers <- how I learned about it with the Fascinate
Fixes & verification of FP5E by Tanno of DroidForums

Attempted and soft-bricked phone, I am sure it was my fault, but if you are not comfortable fixing your phone then do not try this mod. That being said it looks sweet and thanks for your effort!

Endless2232 said:
Attempted and soft-bricked phone, I am sure it was my fault, but if you are not comfortable fixing your phone then do not try this mod. That being said it looks sweet and thanks for your effort!
Click to expand...
Click to collapse
Did you happen to select "Re-partition"? That will soft-brick your phone if you're only flashing the param.lfs.

CrimsonKnight13 said:
Did you happen to select "Re-partition"? That will soft-brick your phone if you're only flashing the param.lfs.
Click to expand...
Click to collapse
Nope, not a complete idiot. =) haha. I will try again later and report back.

Endless2232 said:
Nope, not a complete idiot. =) haha. I will try again later and report back.
Click to expand...
Click to collapse
I was hoping for the best. I'll do what I can to help & correct any errors that jack phones up. :fingers-crossed:

This looks great; thanks for doing this! I'll give this a try in a few days once I'm reunited with my laptop (and hence have access to Odin).
Some suggestions:
It would be good to provide the stock param.lfs for people who want to return to the original boot logo. Alternatively, you could provide a CWM zip for people who have the mod installed to revert to the original logo.
It's possible to mount filesystems and perform file operations using the Android recovery, so you could create a CWM zip and just instruct people to drop in their logo image of choice and flash it after applying the base modification through Odin. This would reduce the steps required to just flashing the Odin package and then flashing a CWM zip.
Would it be possible to flash the param.lfs file through CWM? This would simplify things even further.
Anyway, thanks again and I look forward to trying this out!

substanceD said:
This looks great; thanks for doing this! I'll give this a try in a few days once I'm reunited with my laptop (and hence have access to Odin).
Some suggestions:
It would be good to provide the stock param.lfs for people who want to return to the original boot logo. Alternatively, you could provide a CWM zip for people who have the mod installed to revert to the original logo.
It's possible to mount filesystems and perform file operations using the Android recovery, so you could create a CWM zip and just instruct people to drop in their logo image of choice and flash it after applying the base modification through Odin. This would reduce the steps required to just flashing the Odin package and then flashing a CWM zip.
Would it be possible to flash the param.lfs file through CWM? This would simplify things even further.
Anyway, thanks again and I look forward to trying this out!
Click to expand...
Click to collapse
Original param.lfs in tar.md5 format will be posted tonight.
I'm reading mixed news regarding /mnt/.lfs/ file flashing through CWM. Most people are saying its unflashable from CWM but I need to confirm that it can be done.
As far as I know, param.lfs can't be flashed through CWM.
Edit: It appears I can create a CWM zip but I'll need to dig into what others have made to verify that its doing what I need it to do.
http://forum.xda-developers.com/showthread.php?t=1474753

CrimsonKnight13 said:
Original param.lfs in tar.md5 format will be posted tonight.
I'm reading mixed news regarding /mnt/.lfs/ file flashing through CWM. Most people are saying its unflashable from CWM but I need to confirm that it can be done.
As far as I know, param.lfs can't be flashed through CWM.
Edit: It appears I can create a CWM zip but I'll need to dig into what others have made to verify that its doing what I need it to do.
http://forum.xda-developers.com/showthread.php?t=1474753
Click to expand...
Click to collapse
I'm sure others will get to this before I do, but I'll tinker a bit with this as well - at least in reference to exploring what cwm recovery can do.

Works.
Sent from my SCH-I510 using xda premium

dwitherell said:
I'm sure others will get to this before I do, but I'll tinker a bit with this as well - at least in reference to exploring what cwm recovery can do.
Click to expand...
Click to collapse
Any community effort to make this into a smooth working mod is fine with me. I'll do more research myself tonight.
kvswim said:
Works.
Click to expand...
Click to collapse
Great to know.

I attempted to make a usable CWM zip but it fails with a line in the updater-script.
assert(package_extract_file("param.lfs", "/tmp/param.lfs"),write_raw_image("/tmp/param.lfs", "/dev/block/stl7"),delete("/tmp/param.lfs"));
Click to expand...
Click to collapse
It gives the error:
assert failed: write_raw_image("/tmp/param.lfs", "/dev/block/stl7")
<snip> (Status 7)
Click to expand...
Click to collapse
I'm wondering if /dev/block/stl7 is even writable from CWM.
I have attached both zips for anyone's perusal.

CrimsonKnight13 said:
I attempted to make a usable CWM zip but it fails with a line in the updater-script.
It gives the error:
I'm wondering if /dev/block/stl7 is even writable from CWM.
I have attached both zips for anyone's perusal.
Click to expand...
Click to collapse
I've been playing around with things on my end - but it seems you are right. I've had no luck w/ this as well. Tried a few changes but to no avail. Ah well - other than that your original method worked for me

dwitherell said:
I've been playing around with things on my end - but it seems you are right. I've had no luck w/ this as well. Tried a few changes but to no avail. Ah well - other than that your original method worked for me
Click to expand...
Click to collapse
I'm glad that the original method does work & that we both came to the same conclusion. Thanks for looking into it.
Is there a method to split the zImage, change the RLE, & rejoin it into a workable kernel? Making this thread into a boot & kernel splash image mod combo would be nice. I'm coming up empty handed with my searches through Google & XDA. Most modifications are for Sony phones.

Is step #7 something that can be done within the stock recovery or is that a separate ADB command?

nismology said:
Is step #7 something that can be done within the stock recovery or is that a separate ADB command?
Click to expand...
Click to collapse
I don't recommend EVER using stock recovery due to the possibility of complications with custom-built zips.
/system can be mounted via adb shell as well. The step assumes that you know how to do it via cwm or adb. If I need to clarify, I can.

CrimsonKnight13 said:
I don't recommend EVER using stock recovery due to the possibility of complications with custom-built zips.
/system can be mounted via adb shell as well. The step assumes that you know how to do it via cwm or adb. If I need to clarify, I can.
Click to expand...
Click to collapse
I was in the process of attempting the ADB method of this mod and had CWM installed which was overwritten by the modded param file and step 6 says allow it to boot into recovery which turned out to be the stock one. I guess that is what threw me off.
I guess I didn't know I had to re-Odin CWM to remount the system partition. Just for posterity though, what is the command for mounting it via ADB? I have it all setup already. Thanks for your patience!
Edit: I got it to work. I had to let it boot up, enter shell, get superuser permission, then execute the mount command. This was great ADB practice for a newb like myself. Excellent work and it looks great! Thanks for the how-to!
:good:

nismology said:
I was in the process of attempting the ADB method of this mod and had CWM installed which was overwritten by the modded param file and step 6 says allow it to boot into recovery which turned out to be the stock one. I guess that is what threw me off.
I guess I didn't know I had to re-Odin CWM to remount the system partition. Just for posterity though, what is the command for mounting it via ADB? I have it all setup already. Thanks for your patience!
Click to expand...
Click to collapse
It doesn't & won't overwrite CWM. It is merely overwriting the /dev/block/stl7 partition of your phone.
The mount for system varies if you have rfs or ext4.
rfs
mount once: mount -t rfs -o rw /dev/block/stl10 /system
remount: mount -t rfs -o remount,rw /dev/block/stl10 /system
ext4
mount once: mount -t ext4 -o rw /dev/block/stl10 /system
remount: mount -t ext4 -o remount,rw /dev/block/stl10 /system
nismology said:
Edit: I got it to work. I had to let it boot up, enter shell, get superuser permission, then execute the mount command. This was great ADB practice for a newb like myself. Excellent work and it looks great! Thanks for the how-to!
:good:
Click to expand...
Click to collapse
Good to know. I'm glad it worked out for you.
Just doing mount is another good way since it calls up fstab or whatever equivalent it might be on the system.

CrimsonKnight13 said:
It doesn't & won't overwrite CWM. It is merely overwriting the /dev/block/stl7 partition of your phone.
The mount for system varies if you have rfs or ext4.
rfs
mount once: mount -t rfs -o rw /dev/block/stl10 /system
remount: mount -t rfs -o remount,rw /dev/block/stl10 /system
ext4
mount once: mount -t ext4 -o rw /dev/block/stl10 /system
remount: mount -t ext4 -o remount,rw /dev/block/stl10 /system
Good to know. I'm glad it worked out for you.
Just doing mount is another good way since it calls up fstab or whatever equivalent it might be on the system.
Click to expand...
Click to collapse
Thanks for that. I used a slightly different syntax for mounting /system but it seemed to work out anyway.
And by "just doing mount" are you referring to doing it through CWM? That might be a more straight-forward method indeed. I could use the ADB practice though.

And the original source of my confusion was that step #6 says "allow the phone to reboot into recovery". When you flash the modded param and power on the phone, it automatically boots into stock recovery. It might help other people if the step mentions the fact that you must enter into CWM to mount the system partition instead of "allowing" it to boot up normally, which will result in stock recovery after initial boot-up.

nismology said:
And the original source of my confusion was that step #6 says "allow the phone to reboot into recovery". When you flash the modded param and power on the phone, it automatically boots into stock recovery. It might help other people if the step mentions the fact that you must enter into CWM to mount the system partition instead of "allowing" it to boot up normally, which will result in stock recovery after initial boot-up.
Click to expand...
Click to collapse
As I said, it shouldn't be booting into stock recovery when the modded param.lfs is pushed. If you have already flashed a custom kernel, CWM recovery will stay. If you still have a stock kernel, stock recovery will constantly take over.
Additionally, whenever I did it, due to lack of logo.jpg, it would kick me straight into CWM. I'm unsure what your setup on your phone looks like though.
nismology said:
Thanks for that. I used a slightly different syntax for mounting /system but it seemed to work out anyway.
And by "just doing mount" are you referring to doing it through CWM? That might be a more straight-forward method indeed. I could use the ADB practice though.
Click to expand...
Click to collapse
Yes, mounting through CWM is the easiest way.

[HOW-TO] Unbrick your soft bricked Galaxy S III (+ bootloader brick)

STOP
Follow this guide to the letter. If you don't know what something in ODIN is used for...DON'T CLICK IT.​
Now that that's out of the way, I'd like to apologize to psycopanther for three days worth of trial and error (mostly error), but now I've got a surefire fix for softbricked devices. Kinda ironic how I discovered it though lol.
The Problem: Sometimes when you flash a ROM (TouchWiz or AOSP), there is a risk of the /system and /data partitions not wiping correctly thus leading them to be formatted with R/O permissions rather than R/W. This makes it impossible for the phone to boot up because no data can be written. Not even a typical ODIN flash back to stock or rooted stock will fix this. Using CWM to flash another ROM will yield the same no boot results. Furthermore, the stock recovery will not work and it becomes impossible to perform a factory reset. Sound frustrating? It is.
The Fix: You know how people all over the android forums are told never to tick any of the boxes in ODIN except for Auto Reboot and F. Reset Time? Well this time you will be ticking another box. If you ever run into the problem where your partitions are read-only, but the phone will still boot into Download Mode and recovery, you need to do the following steps:
BUT FIRSTPrerequisites:
ODIN: http://samsung-updates.com/Odin307.zip
Root66.tar: http://www.megashare.com/4384479 -------OR------- (Torrent)
VRALEC bootchain: http://www.androidfilehost.com/?fid=9390034591667978517
VRALF bootchain: http://www.androidfilehost.com/?fid=9390034591667978518
Using both bootchains is probably not necessary, but it's what I did and will do in the future if I ever get another soft brick.
ANDNumber of devices tested on and confirmed working: 40​
Open up ODIN
Select only the following box: F. Reset Time
Flash the VRALEC bootchain in the PDA section and wait for a PASS message
Reset ODIN
Flash the VRALF bootchain in the PDA section and wait for a PASS message
Reset ODINIf you have trouble flashing the bootchains with the method above, try this instead:
1: Flash the first bootchain.
2: Unplug the device while leaving it in "Download Mode".
3: Exit ODIN and then restart it.
4: Plug the device back in while still in "Download Mode".
5: Flash the second bootchain.
6: Repeat steps 2, 3, and 4.
Put the stock.vzw_root66.tar in the PDA section
Select the following boxes: Auto Reboot, F. Reset Time, Nand Erase All
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Start the flash process
Your phone will reboot, but it WILL NOT boot to the homescreen. After you receive a PASS message in ODIN, pull the battery and do the following:​
Reboot into Stock Recovery (hold volume-up, home button, power button simultaneously)
NOTE: You WILL see the following error in recovery so don't freak out:
Code:
E:failed to mount /data (Invalid argument)
E:Can't mount /data/fota/ipth-muc.prop
E:failed to mount /data (Invalid argument)
E:Can't mount /data/fota/ipth-muc.prop
E:failed to mount /data (Invalid argument)
E:Can't mount /data/fota/ipth-muc.prop
Wipe data/factory reset
Wipe cache partition
Reboot
Now your phone will boot up completely with no problems! Congratulations, you just saved yourself $600 and a call to Verizon.
The Question: Will this work on other carriers/devices? Possibly. To those of you on other carriers (AT&T, T-Mobile, Sprint), I am 99.99% positive this will work for you. Just be sure to download a rooted stock ROM in addition to your boot chains that can be flashed in ODIN.
DO NOT USE ROOT66 OR THE LINKED BOOT CHAINS IF YOU ARE ON ANOTHER CARRIER! YOU MUST USE YOUR OWN DEVICE-SPECIFIC FILES!
Thanks
psycopanther - for putting up with me and for figuring out the R/O issue
Invisiblek - for the bootchain files
open1your1eyes0 - for root66
h3llsdr0id - for his method of flashing the bootchains
Donations
Thank you all! - If I forgot you send me a PM
mark-in-dallas
madunix
soopervoo
tserrano35
Ryan Sherman
Kenneth Holt
mike216
kp_martin
If this worked for you please consider a donation. After all, you did just save $600 Donations keep me motivated to putting out new goodies and fixes for the community.​

Bootloader(?) brick
I recently discovered another type of brick by accident and it appeared to be associated with the bootloader. To retrace my steps, I updated to the VRALHD baseband using CWM and immediately after that I restored a backup which caused me to lose the ability to flash ROMs. When loading up another ROM, I always got to the bootanimation, but the bootsound would cut off almost immediately and I would be stuck at a black screen. I was not able to flash ROMs and even unlocking the bootloader again after Odin-ing back to stock didn't work. I was stuck with the stock ROM. The method in the OP doesn't work for this, but the following steps do:
Prerequisites
Root66
PIT file (depending on your model (16gb/32gb)) - (PIT)
Odin
The steps are simple:
Flash Root66 in the PDA slot and the PIT file in the PIT slot
Only tick Auto-reboot, Re-Partition, F. Reset Time
Boot into recovery
Factory reset + wipe dalvik
Reboot
Number of devices tested on and confirmed working: 2​
Your device should boot up normally and you should be able to flash custom ROMs now. If you are still encountering issues, try the method in the OP then re-unlock your bootloader using either AdamOutler's CASUAL or EZ Unlock. Note, if you use EZ Unlock you may continue to get a message saying that the bootloader status is UNKNOWN even after unlocking the bootloader. This was the case for me, but I then did the PIT method as described in this post, factory reset the device, and used TWRP to flash my ROM.
Just an FYI, I now use TWRP so I'm not entirely sure whether there was something specifically wrong with CWM. The partition sizes just got severely messed up.

So what's the ironic story on how you found the fix? Great write up BTW. Hope I never have to use it but keeping this in a safe place.
Sent from my SCH-I535 using xda premium

chefdave12118 said:
So what's the ironic story on how you found the fix? Great write up BTW. Hope I never have to use it but keeping this in a safe place.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Had two S3s, tried to hard brick one to use as a brick test device (it was soft bricked with the error in the OP), but ended up fixing it instead

This should be sticky'd imo

Josolanes said:
This should be sticky'd imo
Click to expand...
Click to collapse
+1
Sent from my SCH-I535 using xda premium

Excellent write up. For some soft-bricks, this might be overkill, but it will alteast get everyone back up and running no matter how severe their issue is. Thank you for the post! I am downloading the files now incase we have some hosting issues in the future. After Goo.im wiped everything a couple times I think it is important to be careful and prepared.

con247 said:
Excellent write up. For some soft-bricks, this might be overkill, but it will alteast get everyone back up and running no matter how severe their issue is. Thank you for the post! I am downloading the files now incase we have some hosting issues in the future. After Goo.im wiped everything a couple times I think it is important to be careful and prepared.
Click to expand...
Click to collapse
Added mirrors for the bootchains just in case.

lol. PROFIT!
---------- Post added at 06:39 PM ---------- Previous post was at 06:31 PM ----------
also, if you have CWM or twrp recovery, and you boot into recovery (before trying any steps above), you can connect your phone with adb and while in recovery (cwm, or twrp) and go into adb shell, and type "mount" .this should show something like this :
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/block/mmcblk0p15 on /data type ext4 (ro,nodev,noatime,nodiratime,user_xattr,barrier=1, data=ordered)
/dev/block/mmcblk0p17 on /cache type ext4 (rw,nodev,noatime,nodiratime,user_xattr,barrier=1, data=ordered)
/dev/block/mmcblk0p14 on /system type ext4 (rw,relatime,user_xattr,barrier=1,data=ordered)
the /dev/block/mmcblk0p15 is set to RO if you notice. and this will cause constant boot hanging as the /system will try to constantly write to /data in which it will fail. These were our symptoms before trying steps in OP.
MAD PROPS to PureMotive for helping solve this issue. pure genius!

psycopanther said:
lol. PROFIT!
---------- Post added at 06:39 PM ---------- Previous post was at 06:31 PM ----------
also, if you have CWM or twrp recovery, and you boot into recovery (before trying any steps above), you can connect your phone with adb and while in recovery (cwm, or twrp) and go into adb shell, and type "mount" .this should show something like this :
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/block/mmcblk0p15 on /data type ext4 (ro,nodev,noatime,nodiratime,user_xattr,barrier=1, data=ordered)
/dev/block/mmcblk0p17 on /cache type ext4 (rw,nodev,noatime,nodiratime,user_xattr,barrier=1, data=ordered)
/dev/block/mmcblk0p14 on /system type ext4 (rw,relatime,user_xattr,barrier=1,data=ordered)
the /dev/block/mmcblk0p15 is set to RO if you notice. and this will cause constant boot hanging as the /system will try to constantly write to /data in which it will fail. These were our symptoms before trying steps in OP.
MAD PROPS to PureMotive for helping solve this issue. pure genius!
Click to expand...
Click to collapse
Sorry that I didn't think of this before. The logcat you sent me did show the symptoms of a ro filesystem but it didn't click with me!

not a problem. if it were not for realizing this RO thing, i do not think we would have gotten it all figured out. thank google for allowing adb access so early in the booting process of the phone lol.
however, the next step would be WHY the system is changed to a read only. I did try to just change the RO of /data back to RW in adb unsuccessfully. If a way was figured out to do it through adb with a simple command, then it would be quicker to fix the partition ( possibly just making a recovery flashable script to do it automatically to fix softbricks, but the methods in the OP is the best route for right now. definitely a step in the right direction in making the whole custom flashing alot safer.

Still the man pure, I liked your work on the incredible forums as well. Good stuff man
Sent from my SCH-I535

What section of odin are u flashing the bootchain?

droidstyle said:
What section of odin are u flashing the bootchain?
Click to expand...
Click to collapse
PDA

Going to link this in my guide! Could you add PDA next to flashing bootchains? reason being I believe that folks might try to flash this in bootloader section unless you spell it out for them. Thx

droidstyle said:
Going to link this in my guide! Could you add PDA next to flashing bootchains? reason being I believe that folks might try to flash this in bootloader section unless you spell it out for them. Thx
Click to expand...
Click to collapse
Done and done man

complete (write) operation failed
i was on the second step and i got the fail msg ...what did i do wrong.... i just wanna get my phone back to stock.. i have downloaded the strock firmware rom but everytime i hit the start button nothing happens... please help

bakerboy81 said:
i was on the second step and i got the fail msg ...what did i do wrong.... i just wanna get my phone back to stock.. i have downloaded the strock firmware rom but everytime i hit the start button nothing happens... please help
Click to expand...
Click to collapse
Where you unable to boot? This thread is for fixing write permissions.
Sent from my SCH-I535 using Tapatalk 2

bakerboy81 said:
i was on the second step and i got the fail msg ...what did i do wrong.... i just wanna get my phone back to stock.. i have downloaded the strock firmware rom but everytime i hit the start button nothing happens... please help
Click to expand...
Click to collapse
By second step I'm assuming you are trying to flash the bootchain? Make sure you are flashing the files within the PDA secion of ODIN. If the ODIN still doesn't flash the files, try rebooting Download Mode and/or ODIN and then retry.

psycopanther said:
however, the next step would be WHY the system is changed to a read only. I did try to just change the RO of /data back to RW in adb unsuccessfully. If a way was figured out to do it through adb with a simple command, then it would be quicker to fix the partition ( possibly just making a recovery flashable script to do it automatically to fix softbricks, but the methods in the OP is the best route for right now. definitely a step in the right direction in making the whole custom flashing alot safer.
Click to expand...
Click to collapse
Agree, would be good to know the root cause -- eg. is it a bug having to do with some edge case in CWM recovery or a particular ROM that could fixed?

[SOLVED] Possibly Bricked my Phone: Can't unmount/format/wipe the /cache partition

Hi All,
I have been flashing back and forth a bit from CM9 to CM10 to try things out. Today, I attempted to restore back to CM9 and it hung for over an hour, so I hard restarted it. Now, I can't restore anything, because it hangs on the /cache partition. I also receive the message while in recovery mode
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Click to expand...
Click to collapse
I am able to get adb shell in recovery mode and I have gone through the steps to check for a bad emmc, which did not indicate badness. I have attempted to use umount from the shell on /cache, which just hangs. In recovery mode, over adb shell, I can ls and cat any of the files in /cache without apparent issue.
I have attempted Super Wipe, factory reset, manual formatting, and wipe cache, all to no avail (they all just hang).
I am running CWM 6.0.1.1.
dmesg has a message about an ext4 error, that makes me suspicious, but I don't know what to do about it.
<4>[ 8.431030] EXT4-fs warning (device mmcblk0p26): ext4_clear_journal_err:4154: Filesystem error recorded from previous mount: IO failure
<4>[ 8.442413] EXT4-fs warning (device mmcblk0p26): ext4_clear_journal_err:4155: Marking fs in need of filesystem check.
<4>[ 8.462036] EXT4-fs (mmcblk0p26): warning: mounting fs with errors, running e2fsck is recommended
<6>[ 8.475463] EXT4-fs (mmcblk0p26): recovery complete
<6>[ 8.489562] EXT4-fs (mmcblk0p26): mounted filesystem with ordered data mode. Opts:
<6>[ 9.242095] key released
<6>[ 9.243774] key released
<6>[ 9.442749] msmsdcc_runtime_suspend: Enter WIFI suspend
<6>[ 9.542755] fsa9480 5-0025: fsa9480_init_detect
<6>[ 9.547424] fsa9480 5-0025: dev1: 0x0, dev2: 0x0
<2>[ 13.382751] EXT4-fs error (device mmcblk0p26): ext4_init_inode_table:1293: comm ext4lazyinit: Something is wrong with group 0
<2>[ 13.382751] Used itable blocks: 403itable unused count: 0
<2>[ 13.382781]
<3>[ 13.411773] Aborting journal on device mmcblk0p26-8.
<2>[ 13.429321] EXT4-fs (mmcblk0p26): Remounting filesystem read-only
Click to expand...
Click to collapse
Apparently my full dmesg output was too long, so if you need anything else please ask.
Thanks in advance for any help!

I am experiencing the same thing (I think) as the OP.
I had been running alpha2 of TeamChopsticks CM10. I installed the new recovery for the skyrocket (downloaded from teamchopsticks.org). Then rebooted into recovery. formatted /system -> installed alpha3 -> installed gapps -> installed darkside-wipe-cache-only -> rebooted. Then my phone just hung on the boot animation for 10+ minutes.
After rebooting I thought I would try to install alpha2 again. I tried to format /system, and it hung.
So I rebooted again, and tried to restore a backup. That hung on "Restoring .android_secure..."
So, I rebooted again. This time I tried a factory reset. It hung on "Wiping cache..."
After rebooting this time, I selected "show log" in CWM, which shows this (I don't know if this is helpful/related):
Code:
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
I:Can't partition unsafe device: /dev/block/mmcblk1p1
I:Can't format unknown volume: /external_sd
I have also tried Fixing Permissions in CWM, with no apparent change.
Also, any time I perform an action in CWM (show logs, fix permissions, etc.) and select "go back" in the menu, the menu disappears. I am still in recovery (still see the CWM logo in the background, and see the text from my previous action), but buttons do nothing and there is no menu.
Any help would be appreciated.
Josh
---------- Post added at 10:58 AM ---------- Previous post was at 10:20 AM ----------
Another follow up to my previous post:
I have tried to reinstall cm9 and cm10 alpha2.
With each I format /system, then when I select "Go Back" in the CWM menu the menu disappears (as I mentioned before). So, I reboot, then install zip from SD -> select the cm zip and get this:
Code:
CWM-based Recovery v6.0.1.1
-- Installing: /sdcard/cm-9-20120715-EXPERIMENTAL-skyrocket-beta1.zip
And nothing after that. It will just sit there.

Don't use darkside wipe, reflash sk8ers recovery From his thread
Posted w/xda app w/ i727R
MY STICKIES
| ROMS | KERNELS | FIRMWARE | RADIOS | HOWTO'S | GUIDES | INFo |
NEWB GUIDES TO: RESTORE TO STOCK | USE ODIN | INSTALL CWM | ROOT |

vincom said:
Don't use darkside wipe, reflash sk8ers recovery From his thread
Click to expand...
Click to collapse
Interestingly (and perhaps ironically), looks like sk8er may be adding the Darkside Tools option in a forthcoming Recovery....
http://forum.xda-developers.com/showpost.php?p=30639023&postcount=267

That's pretty hilarious, so Darkside Wipe is apparently the way to go, except it doesn't work in my case.

So, I tried installing that recovery but it won't install (just like everything else).
I get this:
Code:
CWM-based Recovery v6.0.1.1
-- Installing: /sdcard/cwm6012touch_v11.zip
Is there a way to install his recovery that I am not aware of?
Thanks,
Josh

Fantastic! With some help from the TeamChopsticks IRC channel, particularly sk8erwitskil, I installed CWM Touch 6.0.1.2 and was able to restore a backup of CM9 without an issue. Now that I can do that, I'm going to give CM10 alpha 3 another go.
Please see http://forum.xda-developers.com/showthread.php?t=1777970 for any further help with the recovery.
Cheers!

cthrax said:
Fantastic! With some help from the TeamChopsticks IRC channel, particularly sk8erwitskil, I installed CWM Touch 6.0.1.2 and was able to restore a backup of CM9 without an issue. Now that I can do that, I'm going to give CM10 alpha 3 another go.
Please see http://forum.xda-developers.com/showthread.php?t=1777970 for any further help with the recovery.
Cheers!
Click to expand...
Click to collapse
Why could u install the recovery and what was the solution
Posted w/xda app w/ i727R
MY STICKIES
| ROMS | KERNELS | FIRMWARE | RADIOS | HOWTO'S | GUIDES | INFo |
NEWB GUIDES TO: RESTORE TO STOCK | USE ODIN | INSTALL CWM | ROOT |

I didn't do anything special to install recovery. I pushed the zip to my external card and installed it via the recovery. I assume the cache was not needed to be overwritten for the recovery install.

cthrax said:
I didn't do anything special to install recovery. I pushed the zip to my external card and installed it via the recovery. I assume the cache was not needed to be overwritten for the recovery install.
Click to expand...
Click to collapse
thats the way its done, i just dont understand why you couldnt do it the first place, and the cache has nothing todo with recovery just the rom

Ah, that's a confusion of terms. The original issue was that I could not restore from a backup. Or install a new rom. Apparently installing a new recovery was not an issue, I just didn't know that installing that would help at the time.

I just wanted to follow up that I was able to get my phone back thanks to help from Meanstreak242 in the IRC channel.
I ended up using an adb shell to dd the recovery image to the recovery partition (I *think* it was partition 22).

joshjryan said:
I just wanted to follow up that I was able to get my phone back thanks to help from Meanstreak242 in the IRC channel.
I ended up using an adb shell to dd the recovery image to the recovery partition (I *think* it was partition 22).
Click to expand...
Click to collapse
I'm gonna give this a go as well. Vin, seems you were onto something regarding usage in adb. I've been getting really familiar with it since. And now check out his results. Hopefully this'll work out for me too!!

KillaT21 said:
I'm gonna give this a go as well. Vin, seems you were onto something regarding usage in adb. I've been getting really familiar with it since. And now check out his results. Hopefully this'll work out for me too!!
Click to expand...
Click to collapse
Another no go. Cthrax, can you post or pm me exactly what you did?

KillaT21 said:
Another no go. Cthrax, can you post or pm me exactly what you did?
Click to expand...
Click to collapse
1. Mount phone as USB device
2. Copy newer version of ClockWorkMod Touch
3. Go back into recovery and "install zip from flash"
4. Reboot and restore backup.
5. Profit!

cthrax said:
1. Mount phone as USB device
2. Copy newer version of ClockWorkMod Touch
3. Go back into recovery and "install zip from flash"
4. Reboot and restore backup.
5. Profit!
Click to expand...
Click to collapse
well I didnt have the exact circumstance of doing a restore. I just need to format my partitions so that would hopefully allow me to flash something else. My system basically tries its hardest to stay as Read Only. Even when I mount the system, nothing. I was hoping that with a new recovery I could. It "flashes", but once i reboot, its the same o Clockworkmod Recovery v5.8.1.3

KillaT21 said:
well I didnt have the exact circumstance of doing a restore. I just need to format my partitions so that would hopefully allow me to flash something else. My system basically tries its hardest to stay as Read Only. Even when I mount the system, nothing. I was hoping that with a new recovery I could. It "flashes", but once i reboot, its the same o Clockworkmod Recovery v5.8.1.3
Click to expand...
Click to collapse
Maybe your variant of the problem is closer to what joshjryan did then. He had to use adb shell to manually use dd to copy the bits over. Hopefully he's watching and can chime in with some more comments.

Well, joshjryan, I hope youre reading this too.
This caught my attention after a dmesg:
<6>[ 1478.616302] EXT4-fs (mmcblk0p24): mounted filesystem with ordered data mod
e. Opts:
So then I
~ # parted /dev/block/mmcblk0p24
parted /dev/block/mmcblk0p24
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0p24
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: Generic SD/MMC Storage Card (sd/mmc)
Disk /dev/block/mmcblk0p24: 627MB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Could this be the cause??
Number Start End Size File system Flags
1 0.00B 627MB 627MB ext4
(parted)

cthrax said:
Maybe your variant of the problem is closer to what joshjryan did then. He had to use adb shell to manually use dd to copy the bits over. Hopefully he's watching and can chime in with some more comments.
Click to expand...
Click to collapse
This does sound similar to what I was seeing.
I also was not able to actually install the new recovery. So I did this:
I extracted cwm0612touch to get recovery.img
Then I mounted my phones SB by USB and copied recovery.img to my sd card
Then in the adb shell to my phone I used dd to copy the image to the appropriate partition
Code:
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22
Hopefully that does the trick for you!

joshjryan said:
This does sound similar to what I was seeing.
I also was not able to actually install the new recovery. So I did this:
I extracted cwm0612touch to get recovery.img
Then I mounted my phones SB by USB and copied recovery.img to my sd card
Then in the adb shell to my phone I used dd to copy the image to the appropriate partition
Code:
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22
Hopefully that does the trick for you!
Click to expand...
Click to collapse
It didnt. It installed to the right partition, but after reboot, cwmtouch5.8.1.3 is there again
Is it something in my reboot/boot that causes that?