Database Info

I need an easier guide...

To outline my situation, I have installed CWM to my phone, and flashed version 2.5.1.2 of Galaxy S i9000 (but the recovery boot doesn't show as CWM) on a Samsung InFuse 4G (this part I managed to find by scouring the forums) with Firmware version 2.2.1, Kernel 2.6.32.9, with Build FROYO.UCKH1. This is as far as I have gotten because I cannot seem to get a backup of my phone's ROM made. So, my question is can someone explain (without jargon, I haven't quite learned it yet) in simple steps how to resolve this issue and help me continue my way to flashing a custom ROM? I've checked and read so many other guides, but they are confusing because the steps aren't (sad to say) dumbed down for me. Here's an example of what I read:
1: dl CWM (actually had to go look this up and figure out what it was)
2: flash CWM (my phone model wasn't on the list, but after an extensive search found out that I could use the Galaxy S i9000 [supposedly])
3: boot into CWM Recovery (can't do it, for some reason it won't load on my phone.)
4: perform backup with CWM (as before, can't do it, read I could use Titanium backup but no depth was given)
5: dl a rom and place it on your sd card (this one is understood, short and to the point)
6: boot into CWM and flash rom
Unfortunately, when I start out on a new OS (already owning Windows and getting good at Linux) I tend to not even understand these so-called "Dummies Guides." I need something filled with minimal jargon that is short and sweet. Any information would be helpful
Also, I would like to know the likelihood of bricking my phone (based off of its specs) if it is possible to find out...

I'm a little bit confused here. How come you've flashed an i9000 (Galaxy S) firmware onto an Infuse? I think we can work out your backup problems though

I mean that I flashed the Galaxy S i9000 version of CWM Recovery to my phone because there wasn't an InFuse option. (according to one thread, it said that the i9000 version was compatible with the InFuse)
However, I flashed the Recovery, but when I booted into recovery mode, I was still in the stock recovery. Any explanation for this and everything else?
I don't really know anything about the Android system yet, but I hope to be good enough to become a developer one day.

DeltaOps said:
I mean that I flashed the Galaxy S i9000 version of CWM Recovery to my phone because there wasn't an InFuse option. (according to one thread, it said that the i9000 version was compatible with the InFuse)
However, I flashed the Recovery, but when I booted into recovery mode, I was still in the stock recovery. Any explanation for this and everything else?
I don't really know anything about the Android system yet, but I hope to be good enough to become a developer one day.
Click to expand...
Click to collapse
Gotcha. Sounds like the recovery hasn't flashed properly. Did you have the phone rooted before flashing the recovery?
Here is an awesome thread with video guides on just about everything you could need. Here is another. I take it you've already followed at least one of these to get the recovery flashed, so it might pay to try the 3E recovery instead and see if that works.
You may need to go right back to stock and start over. If you do, AdamOutler has got you covered right here.
I'll stay subscribed in case you need anything else, best of luck mate

My phone was rooted with SuperOneClick. Superuser was still intact. I read on a thread that the CWM Recovery could "fake flash" and that it would still be accessible by selecting "boot into recovery" but it doesn't show.
It says 3E in my recovery mode, is that the modified or is it actually stock?
I downloaded CWM from the market (method 2) but for some reason have update.zip on my phone (method 1). Any explanation? I don't exactly remember downloading a .zip file...

DeltaOps said:
My phone was rooted with SuperOneClick. Superuser was still intact. I read on a thread that the CWM Recovery could "fake flash" and that it would still be accessible by selecting "boot into recovery" but it doesn't show.
It says 3E in my recovery mode, is that the modified or is it actually stock?
I downloaded CWM from the market (method 2) but for some reason have update.zip on my phone (method 1). Any explanation? I don't exactly remember downloading a .zip file...
Click to expand...
Click to collapse
It may have 'fake flashed' and not worked at all. Both stock and modified recovery will say 3E, the difference is in the version numbers although I can't picture them off the top of my head. If CWM had worked, you would not be seeing 3E, you would see the typical array of CWM options. The modified 3E does not give you the same options CWM does, it just gives you the option to flash an 'unsigned' image from Recovery.
I have never had any luck with ROM Manager personally, although a lot of people swear by it. I found it especially flaky flashing recoveries to any device, very hit-and-miss. I personally prefer, and recommend, flashing recoveries manually via ADB. A little trickier, but a lot more trustworthy.
That said, try flashing recovery through RM again before taking any further steps. Flashing a recovery over a recovery won't hurt

I've tried three separate times to install the CWM recovery, but all were unsuccessful. What's this about ADB? I remember seeing the ADB Daemon in the SuperOneClick rooting process. And how tricky is it exactly, does it require code?
I have the Titanium Backup app on my phone, and I have backed up all the system and app data, but they are all separate files instead of a single (what, .md5?) file. I remember reading another thread that said you could back up a ROM via TB but I can't find a back up ROM option. Is there a particular way to do this or do I have to have the Premium/Pro version of TB? Or have I pretty much done all I can do with TB?

DeltaOps said:
I've tried three separate times to install the CWM recovery, but all were unsuccessful. What's this about ADB? I remember seeing the ADB Daemon in the SuperOneClick rooting process. And how tricky is it exactly, does it require code?
I have the Titanium Backup app on my phone, and I have backed up all the system and app data, but they are all separate files instead of a single (what, .md5?) file. I remember reading another thread that said you could back up a ROM via TB but I can't find a back up ROM option. Is there a particular way to do this or do I have to have the Premium/Pro version of TB? Or have I pretty much done all I can do with TB?
Click to expand...
Click to collapse
ADB is a command-line interface between your PC and your phone. You enable USB debugging and connect the phone via USB to the computer. Once you have the correct drivers installed, you can then use ADB (part of the Android SDK available for download) to send commands to your phone, as well as push and pull files. This requires full root, which you already have.
For example you can grab the recovery.img for CWN on the Infuse and tell ADB to 'flash recovery recovery.img' and actually ensure it flashes.
There are some excellent ADB tutorials floating around, this one in particular got me started. Make sure you do a bit of reading first though: the wrong command can royally screw you.
After you're familiar, you should be able to use ADB to push a recovery to your phone, whether it be unsecured 3E, or CWM.
I'll stay subscribed for any queries you may have

How close is the ADB interface to other command-line interfaces like Linux or Windows? I use both operating systems on my laptop and I have familiarized myself with both of them (mostly). What am I supposed to be expecting when I use it? Also, I can't seem to find the recovery.img file, what folder would that be under?

DeltaOps said:
How close is the ADB interface to other command-line interfaces like Linux or Windows? I use both operating systems on my laptop and I have familiarized myself with both of them (mostly). What am I supposed to be expecting when I use it? Also, I can't seem to find the recovery.img file, what folder would that be under?
Click to expand...
Click to collapse
Don't know about Linux, but ADB works through a Windows command prompt so its pretty much the same. You will need to have ADB, Fastboot plus whatever you wish to flash (recovery.img) in a 'working' directory, then run a command prompt from that directory.
You will probably need to download the recovery.img file.from XDA. It may be zipped up (they usually are).
Sent from my Galaxy Note using XDA Premium

I've successfully got ADB started in the command prompt (not that bad :]) but when I try to pull the directory map from my phone, it says: remote object "xxxxxxxxx" does not exist. And what's this about Fastboot? Edit: Did a bootloader command test, worked just fine. No success on pulling directory
Command I used: "adb pull -s xxxxxxxxxxx C:\"

DeltaOps said:
I've successfully got ADB started in the command prompt (not that bad :]) but when I try to pull the directory map from my phone, it says: remote object "xxxxxxxxx" does not exist. And what's this about Fastboot? Edit: Did a bootloader command test, worked just fine. No success on pulling directory
Command I used: "adb pull -s xxxxxxxxxxx C:\"
Click to expand...
Click to collapse
I don't think that's the correct format to pull directory structure. I'll have to read up on that one
Fastboot is another tool you can use to flash bootloaders, radios, recoveries etc through the command prompt.
Sent from my Galaxy Note using XDA Premium

You're right, tried using the <remote> variable as a file instead of the device serial. Typed:
adb pull .. files
prompt skitzed out after that. I know it won't damage anything since it's a copy procedure but I'm looking for the file and it's not there. it said it's pulling everything after skipping "special files"
Edit: It just finished, said it couldn't create the file because for some reason it was trying to copy the files from the phone to the phone

DeltaOps said:
You're right, tried using the <remote> variable as a file instead of the device serial. Typed:
adb pull .. files
prompt skitzed out after that. I know it won't damage anything since it's a copy procedure but I'm looking for the file and it's not there. it said it's pulling everything after skipping "special files"
Edit: It just finished, said it couldn't create the file because for some reason it was trying to copy the files from the phone to the phone
Click to expand...
Click to collapse
Yeah, you'll have to give it a target directory, I think it's like this '.\sdcard' to write them to the SD card?
Sent from my Galaxy Note using XDA Premium

If that's the case, then how do I make the file copy to my HDD? The drive doesn't show up on my computer (does it)?

DeltaOps said:
If that's the case, then how do I make the file copy to my HDD? The drive doesn't show up on my computer (does it)?
Click to expand...
Click to collapse
I'm sure that with the correct command, you will be able to pull the structure to your hard drive. I'm not sure if it's .\C:/ or not, I'll have a look when I'm on a proper rig and can do a proper search
Sent from my Galaxy Note using XDA Premium

Thanks! You've been great so far
That noob video was right, XDA is full of awesome people!
Edit: Got it Thanks for the pointers. Now I need to find out how to back up the entire ROM... :/

DeltaOps said:
Thanks! You've been great so far
That noob video was right, XDA is full of awesome people!
Edit: Got it Thanks for the pointers. Now I need to find out how to back up the entire ROM... :/
Click to expand...
Click to collapse
Glad you got it and glad to help. There are a hell of a lot of good people here If there's anything else you need, feel free to PM me.
Good luck buddy!
Sent from my Galaxy Note using XDA Premium

Is there perhaps any way to perform a ROM backup with ADB?

DeltaOps said:
Is there perhaps any way to perform a ROM backup with ADB?
Click to expand...
Click to collapse
Ooh good question. I don't think so, but I'm not sure. I know you can pull directories like /system/ and whatnot, but as for repackaging them into a working backup, that may be a bit more involved. I would use ADB to.push a working CWM and do it that way, but it sounds.like you're a bit better at the command-line stuff than I so you may be able to work it!
Sent from my Galaxy Note using XDA Premium

How to replace one file when failing to boot

Hey guys
I screwed up my vold.fstab trying to get "_ExternalSD" back.
Unfortunately! I did not run a nandroid before I made the change.
Now, I can dirty flash my rom on top, or go back to a nandroid from a few days ago, but I'd really just like to recover and go on my merry way. And maybe learn something in the process.
Only thing is, I can't figure out how to access the phone other than the External SD card through CWM.
Can I mount the internal /system and access through USB? Is there some facility to copy a file from one point to another? Any other methods? I guess the phone has to be up to run ADB, right?
I don't know how to generate a flashable zip but I could extract the original version of the file from the original rom. I assume that its non trivial to create a flashable zip, but maybe someone can comment? It looks like there is signing and certificates involved..
thanks for any ideas

bluenote73 said:
Hey guys
I screwed up my vold.fstab trying to get "_ExternalSD" back.
Unfortunately! I did not run a nandroid before I made the change.
Now, I can dirty flash my rom on top, or go back to a nandroid from a few days ago, but I'd really just like to recover and go on my merry way. And maybe learn something in the process.
Only thing is, I can't figure out how to access the phone other than the External SD card through CWM.
Can I mount the internal /system and access through USB? Is there some facility to copy a file from one point to another? Any other methods? I guess the phone has to be up to run ADB, right?
I don't know how to generate a flashable zip but I could extract the original version of the file from the original rom. I assume that its non trivial to create a flashable zip, but maybe someone can comment? It looks like there is signing and certificates involved..
thanks for any ideas
Click to expand...
Click to collapse
this is why i hate it when people make those guides.
messing with the vold.fstab is dangerous (even though its only a few lines) if your trying to recover your data, give up. its not going to happen. (sorry)
when you edit the vold.fstab it messed up the partitions on your internal SD card and most likely did the equivalent of wiped your /system partition. (or another important one.) your actually lucky it did not completely brick your phone.
your post was a little vague, but if you can, just restore an older nandroid, or wipe everything and install another ROM. (you can try dirty flashing but i dont think itll work)
if you cannot access CWM, then follow the steps in This guide. it should get you back up on your feet. after you follow that guide flash a gingerbread ROM (any gingerbread rom will do fine) then you can reboot and flash any ROM you want. (it needs this to fix a quirk in that script)
Hope you get it fixed
EDIT: re read your post, if your feeling adventurous and want to give it a shot, boot into CWM and connect it via usb. you can now get into an ADB shell on your phone by typing 'adb shell' if you have adb all setup and working. (im working from memory here so dont quote me on any of this)
now, you should be able to access your /system folder from that shell. be very careful though, i dont have much experience right here, and if i remember correctly you might not be in the full root directory yet)
if you can get into it try replacing your vold.fstab with a stock one,
if you dont have a stock one lying around, make a nandroid of the current state of the rom, then flash another rom, pull the vold.fstab, then re-restore back to the broken one and restore it (id upload mine but my phone is OOC right now )
after that just reboot and hope it resolves itself, if not then just follow my advice above
and keep that guide i linked to handy, messing around in CWM has the ability to brick your phone, if it does, then just follow that guide.

Klathmon said:
this is why i hate it when people make those guides.
messing with the vold.fstab is dangerous (even though its only a few lines) if your trying to recover your data, give up. its not going to happen. (sorry)
when you edit the vold.fstab it messed up the partitions on your internal SD card and most likely did the equivalent of wiped your /system partition. (or another important one.) your actually lucky it did not completely brick your phone.
your post was a little vague, but if you can, just restore an older nandroid, or wipe everything and install another ROM.
if you cannot access CWM, then follow the steps in This guide. it should get you back up on your feet. after you follow that guide flash a gingerbread ROM (any gingerbread rom will do fine) then you can reboot and flash any ROM you want. (it needs this to fix a quirk in that script)
Hope you get it fixed
Click to expand...
Click to collapse
How bout adb and pushing the file back in? Or cant you access the phone via adb?
Sent from my LG-P970 using XDA

N00BY0815 said:
How bout adb and pushing the file back in? Or cant you access the phone via adb?
Sent from my LG-P970 using XDA
Click to expand...
Click to collapse
re read your post and updated my last post right after you posted
after dealing with noobies all day, i forget sometimes people want to try big things

Thanks guys. The info I was missing was there's no special trick to attaching adb while in CWM! Just plug in!
My phone is back up and running and partitions are fine as far as I can see after just booting up.

Hi there! I messed up with the vold.fstab filfe on my tablet – I replaced it with a downloaded file with the intention to transfer apps to my external SD card.
Now my tablet is only showing the startup logo and won’t continue loading. I can access recovery mode. Now I want to restore the original vold.fstab file.
My questions:
1. Using the Android SDK, the file explorer does not show any files, though my tablet is recognized.
2. Using adb push, it yields an error: permission denied, how to successfully push the original vold.fstab and replace the existing vold.fstab?
3. If I dump an image of my tablet and edit the dumped image, would this be easier compared to the steps above?
Thanks!

http://forum.xda-developers.com/showthread.php?t=1646108
Try this.
If this doesn't help you should ask in the section for your tablet to get more specific advice.

TwitchyEye said:
http://forum.xda-developers.com/showthread.php?t=1646108
Try this.
If this doesn't help you should ask in the section for your tablet to get more specific advice.
Click to expand...
Click to collapse
Thanks, I will try it later when I got home. My tablet is not found here. I have a Skyworth S71(3G) with RK3066 chipset.

BryanF said:
Thanks, I will try it later when I got home. My tablet is not found here. I have a Skyworth S71(3G) with RK3066 chipset.
Click to expand...
Click to collapse
You need to do an adb remount before you can push. Was it rooted before?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!

Mansa_noob, yes, my tablet is rooted. I followed some instructions about adb but had an error saying access denied, and also no files are displayed at file explorer. See my posts above. I also mounted it successfully. I will post some sreenshots later.
Please if you have some instructions, I am willing to try.
---------- Post added at 07:06 AM ---------- Previous post was at 07:02 AM ----------
TwitchyEye said:
http://forum.xda-developers.com/showthread.php?t=1646108
Try this.
If this doesn't help you should ask in the section for your tablet to get more specific advice.
Click to expand...
Click to collapse
Hi twitchyEye, it did not work. It attemps to install (using the install update from ext sd card) but then says installation aborted.
Any more suggestions? Thanks

What recovery are you using? I suck with adb so I got nothing on that front.

It was the stock recovery from my Tablet. I don't have it on hand right now, I will post later. The chipset is RK3066. My problem is my tablet has no official support on the internet (maybe becaue it's still new). Model is Skyworth S71(3G).

I see. Yeah this is over my head man. I thought for sure you were running a custom recovery and it was an easy answer. I'm actually struggling right now with adb myself with a similar issue something about permissions whenever I try to do anything to my phone. So I guess right now would be a perfect time for somebody to chime in with a smarter answer!

TwitchyEye said:
I see. Yeah this is over my head man. I thought for sure you were running a custom recovery and it was an easy answer. I'm actually struggling right now with adb myself with a similar issue something about permissions whenever I try to do anything to my phone. So I guess right now would be a perfect time for somebody to chime in with a smarter answer!
Click to expand...
Click to collapse
Are you doing adb remount and still getting permission denied?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!

mansa_noob said:
Are you doing adb remount and still getting permission denied?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
Click to expand...
Click to collapse
Yes, I did adb remount and still access denied

BryanF said:
Yes, I did adb remount and still access denied
Click to expand...
Click to collapse
This is strange. A properly rooted phone would adb remount to r/w system. Something is fishy. Is it rooted+
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!

mansa_noob said:
This is strange. A properly rooted phone would adb remount to r/w system. Something is fishy. Is it rooted+
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
Click to expand...
Click to collapse
I am sure it is rooted, because I downloaded an application from Google play to check it it is rooted or not. It is really rooted. I alvo confirmed this as I can now fully backup and restore my apps using Titanium backup before the tablet is messed up.

BryanF said:
I am sure it is rooted, because I downloaded an application from Google play to check it it is rooted or not. It is really rooted. I alvo confirmed this as I can now fully backup and restore my apps using Titanium backup before the tablet is messed up.
Click to expand...
Click to collapse
OK. Odd or not, it is what it is. Is it possible for you to load a custom recovery?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!

mansa_noob said:
OK. Odd or not, it is what it is. Is it possible for you to load a custom recovery?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
Click to expand...
Click to collapse
I want to try, but the stock recovery is my last hold as I have no stock ROM. If I overwrite the stock ROM, I cannot reinstall it as I don't have a copy of it.

So why not flash cwm with nvflash and then make a backup of your current stock rom? I did exactly that.
Sent from my LG-P999 using xda premium

[Q] Questions on Bryan's CM7 build

I didn't want to clutter up the dev thread with these questions, but I've never used any CM build on any phone.
I unzipped Bryan's CM7 build to see what was inside and noticed it didn't seem to have a launcher and didn't seem to have any market app. Ok so does that mean you have to pre install Google apps from the SDcard to be able to access the market?
In reading the instructions, it seems like Bryan's CM7 build uses the same kernel as his regular beta kernel thread but that can't be right, can it, with the discussion on the thread....
I noticed that the Google apps were all modified for CM7, so does that mean that ordinary apps won't work unless they're modified?
Can I still use the TW4 launcher on CM7? Used to it.
The business about USB storage not working in Android. I assume that means you can't put anything on the SDcard using the USB cable after Android has booted up so that you have to push everything on there with ADB, is that it, in recovery mode?

1. It does contain a launcher; Its called ADW Launcher.
2. Yes, you would need to flash the google apps. I use this one
http://goo.im/gapps/gapps-gb-20110828-signed.zip
and this one http://goo.im/gapps/gapps-gb-20110828-newtalk-signed.zip​
3. You flash the gapps-gb-20110828-signed.zip file then the gapps-gb-20110828-newtalk-signed.zip google talk with video chat support.
4. Its a different kernel. CM7 is using the MTD version. While regular stock roms use BML.
5. I believe you can use the google apps on those files on any rom. But most roms already bring them integrated.
6. Apps developed for use on the Galaxy S phones like TWLauncher et al will not work as they hook onto some samsung specific programming.
7. As mentioned in 6, you cannot use TWLauncher on cm7.
8. Yes you would have to push everything through ADB in the meantime. Pushing/puling through adb does not require rebooting to recovery though.

Can someone make a video on how to install the rom?

Just follow the written instructions on the thread and you'll be fine
Sent from my SGH-T959V using xda premium

Honestly they confuse the crap outta me. A video would dumb it down for me and im sure a few others.

IDK how the heck I made my efs backup.
But if anyhow, you manage to make some sort of a tar file with your efs files, you should be fine.
After that,
do the erase_image
and mount /efs
and cd /efs
and tar xf anybackupname.tar
you will install. That is if you get your.

Donte21 said:
Honestly they confuse the crap outta me. A video would dumb it down for me and im sure a few others.
Click to expand...
Click to collapse
My suggestion is to wait until the install procedure is easier.
In the CM7 OP, Bryan said (twice) to re-read OP after updates.
Making a video will give you proper instructions for this build, but if Bryan updates the install procedure users following the video are going to have a mixed bag of results, and possible bricks.
Sent from my SGH-T959V using Tapatalk

when I try to Heimdall the boot.img I get a warning that says Tar header contained an invalid file size.

cybok0 said:
when I try to Heimdall the boot.img I get a warning that says Tar header contained an invalid file size.
Click to expand...
Click to collapse
Are you using the heimdall command prompt? Or the heimdall program?
Sent from my SGH-T959V using xda premium

Juls317 said:
Are you using the heimdall command prompt? Or the heimdall program?
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
Program, I just started reading the one click guide, I think I should of tried that first right?
---------- Post added at 09:58 AM ---------- Previous post was at 09:48 AM ----------
I will have to try this on my day off, a lot of reading and understanding to do.

cybok0 said:
Program, I just started reading the one click guide, I think I should of tried that first right?
---------- Post added at 09:58 AM ---------- Previous post was at 09:48 AM ----------
I will have to try this on my day off, a lot of reading and understanding to do.
Click to expand...
Click to collapse
You need to follow Bryan's instructions EXACTLY, a in use the heimdall command prompts
Sent from my SGH-T959V using xda premium

OK, I think I'll stick with VB, I'm not this tech savvy.

I'm going to make a video guide tonight hopefully, but of course I'm going to leave the explicit direction that noobs should not flash it
Sent from my SGH-T959V using xda premium

I have a question as well. Yes, I know that this isnt exactly high priority, but I'm wondering if later there will be a build with Wifi calling. I was trying to install it myself, but it kept force closing, and I don't wanna try anything that'll mess up my phone any worse than I have before.
Wifi calling is basically a must for me since I basically live in Smallville, KS. I get little to no service here, and without it, it usually takes forever to get anything. And yes, I've tried every modem I could, KG4 works best, since I can sometimes get one bar.
I'm trying to complain or anything, and I thank Team Acid for bringing us CM7.

Neo I'm sure at one point bryan will get that working.
Sent from my SGH-T959V using Tapatalk 2

elmejor183 said:
6. Apps developed for use on the Galaxy S phones like TWLauncher et al will not work as they hook onto some samsung specific programming.
Click to expand...
Click to collapse
So does that mean that NONE of the apps will work unless modified to run on CM7? Or are you just talking about certain Samsung issued apps? I'm in the middle of an old Tarzan novel on my e-reader program on the phone...

I have a question with the process flash boot.img with heimdall...when i open heimdall front end and put boot.img into the flash local package..i get a error the tar header contained an invalid file size..on the flash tab, it only takes pit files..also when i just use the heimdall ..a black screen happens similar like a command prompt and just exits..
how do i flash the boot.img with heimdall?
This is using fbs instructions that I am using and i am stuck on step 7. flash the latest boot.img from bryans op..
http://forum.xda-developers.com/showpost.php?p=25197350&postcount=279

Are you on windows? If so open command promt. Cd into the heimdall suite directory. Put your phone in DL mode and connect to usb. From command type "heimdall detect". Should say device detected. Then just put the boot.img in the same directory and follow the OP.

nazcalito said:
So does that mean that NONE of the apps will work unless modified to run on CM7? Or are you just talking about certain Samsung issued apps? I'm in the middle of an old Tarzan novel on my e-reader program on the phone...
Click to expand...
Click to collapse
That's just Samsung-specific stuff like TouchWiz that require Samsung's modified frameworks and extra libraries.

Just use FB's install guide instead. I was going to wait until it was installable through CWM, but this is essentially the same thing with a few extra steps.

[HOW-TO] Fix soft brick & error mounting sdcard

EDIT: I solved my own problem. Scroll down to post #8 for the solution.
My problem was that my phone (T-Mobile USA HTC One S) would not boot into ICS anymore, but I was still able to get into recovery (CWM), yet I had no access to the sdcard ("unable to mount /sdcard").
Post #8 below tells you how you can restore access to the sdcard in CWM so that you can push a ROM zip file to the sdcard via adb.
-J

Have you made any nandroids? If you have maybe you can restore. Also check in the download file in cwm that is possible place where that file may be.
Sent from my myTouch 4G Slide using xda premium

archie53 said:
Have you made any nandroids? If you have maybe you can restore. Also check in the download file in cwm that is possible place where that file may be.
Sent from my myTouch 4G Slide using xda premium
Click to expand...
Click to collapse
Unfortunately I didn't have the foresight to make a nandroid backup. My previous phone was a Samsung Galaxy S 4G, which, like most Android phones, has a removable SD-Card that stuff can be copied onto (and then flashed). Not so here obviously.
Is it even possible to push files to the sdcard using the method I tried when in CWM?

When you push the file via ADB, have you tried placing it into a folder that you know is on the /sdcard?

joshnichols189 said:
When you push the file via ADB, have you tried placing it into a folder that you know is on the /sdcard?
Click to expand...
Click to collapse
It just got worse. I got the idea to format all partitions (data, system, cache, sdcard) through CWM, and now CWM can't even mount /sdcard/ anymore...

I had to do the same thing:
adb push "NameOfFile.zip /sdcard
then go to install from zip.
Look on sd card and it will be there.
I always rename the zip files to there can be less errors.
you can also do
adb shell pull "nameOfFile.zip /sdcard
make sure the zip file is where your adb and fastboot is

My problem is CWM can't mount the /sdcard directory, so I can't flash the new OS. Is there anybody that knows how to recover from that problem?

LuckyMethod said:
My problem is CWM can't mount the /sdcard directory, so I can't flash the new OS. Is there anybody that knows how to recover from that problem?
Click to expand...
Click to collapse
Yes, I just fixed my problem yesterday after some serious trial-and-error.
1) Use the All-in-One-Kit and flash your recovery back to stock
2) Boot into the bootloader and choose to "clear storage" and afterwards to reset to factory defaults.
3) Go back to the all-in-one-kit and flash a CWM recovery version again.
4) Reboot into recovery (CWM). Your /sdcard should now be mounted and visible.
5) Now, try the UTB rom (it worked for me), rename the zip file to something short (i.e. utb.zip), and push it to the sdcard using adb as follows:
Code:
adb push utb.zip /sdcard
6) While still in CWM, flash the zip.
The trick here is that only the stock recovery is capable of restoring access to the sdcard by it's proprietary "clear storage" option.
Good luck!
-J

If that doesn't work an easy fix is boot into bootloader, goto fastboot and use "fastboot flash boot boot.img" and so fouth. In the dev section I seen a stock tmobile naindroid. Download it and you'll have your data.img and boot.img. You should be able to flash them without needing to push to /sdcard. letme know how it works
I know you fixed this already just thought this still might help

cannondale0815 said:
Yes, I just fixed my problem yesterday after some serious trial-and-error.
1) Use the All-in-One-Kit and flash your recovery back to stock
...cut...
-J
Click to expand...
Click to collapse
It worked like a charm, thank you very much. You saved my life, I was in a time crunch.

LuckyMethod said:
It worked like a charm, thank you very much. You saved my life, I was in a time crunch.
Click to expand...
Click to collapse
Happy it worked for you. Took me several days to figure this out
Sent from my HTC One S using xda premium

I too formatted my sd card but a little trial and error and using your direction, I am back in business ! Thank you , this should really be a sticky
Sent from my HTC VLE_U using xda premium

j3.cole said:
I too formatted my sd card but a little trial and error and using your direction, I am back in business ! Thank you , this should really be a sticky
Sent from my HTC VLE_U using xda premium
Click to expand...
Click to collapse
Thank you. I changed the title and original post to make it easier for people to find this thread.

I am going to try this trick tomorrow after having spent endless hours trying to fdisk/parted via adb, and flashing endless roms and updates to no avail. I will post the outcome here. I really hope this works for me like it has for you guys...

mrmoretti said:
I am going to try this trick tomorrow after having spent endless hours trying to fdisk/parted via adb, and flashing endless roms and updates to no avail. I will post the outcome here. I really hope this works for me like it has for you guys...
Click to expand...
Click to collapse
IT WORKED! This thread should be made sticky! I'm sure a lot of users who have HTC One S with built-in SD will have the same issue when mucking about with their phone. Thank you!

Bump, as too many people are having this problem.
Sent from my HTC One S using Tapatalk 2

cannondale0815 said:
Yes, I just fixed my problem yesterday after some serious trial-and-error.
1) Use the All-in-One-Kit and flash your recovery back to stock
2) Boot into the bootloader and choose to "clear storage" and afterwards to reset to factory defaults.
3) Go back to the all-in-one-kit and flash a CWM recovery version again.
4) Reboot into recovery (CWM). Your /sdcard should now be mounted and visible.
5) Now, try the UTB rom (it worked for me), rename the zip file to something short (i.e. utb.zip), and push it to the sdcard using adb as follows:
Code:
adb push utb.zip /sdcard
6) While still in CWM, flash the zip.
The trick here is that only the stock recovery is capable of restoring access to the sdcard by it's proprietary "clear storage" option.
Good luck!
-J
Click to expand...
Click to collapse
THANK YOU SO MUCH! THIS WORKED PERFECTLY!
This should definitely be included in a stickied guide for people like me who have managed to corrupt their recoveries.

Got it after several tries

hey guys i have the same problem, the solution sort of work, but when i try to do a adb push its show it was sucessful but when i do to flash it i cant see it.

yasir_jan87 said:
hey guys i have the same problem, the solution sort of work, but when i try to do a adb push its show it was sucessful but when i do to flash it i cant see it.
Click to expand...
Click to collapse
Try to shorten the filename, i.e. "rom.zip".
And try this slightly modified command instead:
adb push rom.zip /sdcard/rom.zip
Sent from my aokp_tenderloin using Tapatalk 2

[SOLVED] Please Help - Corrupted Data on Internal SD, Can't Delete

This has driven me insane. I am close to throwing this tablet out the window. So far I have had nothing but horrible experiences with it. I have a gt3113 and I can't delete several directories on the sdcard. I've tried through file managers, through my pc and through terminal emulator, nothing removes the files.
WTF do I do? I'm rooted, running stock 4.04. Trying to keep it together here.

1-May be through root browser lite and try to long press the files and fix permissions as read and write before delete??
2-or format data in cwm ( be so cautious when doing this)?
3- or as last resort flash a firmware with pit file and repartition ticked in odin? (also be very cautious when doing this)
Sent from my GT-P5100 using xda app-developers app

Mohamedselim said:
1-May be through root browser lite and try to long press the files and fix permissions as read and write before delete??
2-or format data in cwm ( be so cautious when doing this)?
3- or as last resort flash a firmware with pit file and repartition ticked in odin? (also be very cautious when doing this)
Sent from my GT-P5100 using xda app-developers app
Click to expand...
Click to collapse
I tried options 1 and 2, neither worked. 3 may have worked but I found an easier and safer solution.
Not sure if this part helped or not but in terminal I ran:
Code:
su
/system/bin/fsck_msdos -y /dev/block/vold/179:25
reboot
then I was able to delete the files from /mnt/sdcard/ instead of where I was trying to delete them from, which was /sdcard/
and it worked! Thanks a lot for your suggestions! Not sure what caused this in the first place, but if anyone else runs into this problem maybe they'll find this thread.

Bentenrai said:
This has driven me insane. I am close to throwing this tablet out the window. So far I have had nothing but horrible experiences with it. I have a gt3113 and I can't delete several directories on the sdcard. I've tried through file managers, through my pc and through terminal emulator, nothing removes the files.
WTF do I do? I'm rooted, running stock 4.04. Trying to keep it together here.
Click to expand...
Click to collapse
Bentenrai said:
I've had this thing for about a week and haven't even been able to use it yet. It's been in a bootloop or fc loop for the entire time. I finally got it running but the internal SD filled up completely with junk files and directories that couldn't be deleted. I couldn't install any apps since the stock firmware doesn't allow installing to an external card... CM9/10 force close looped because of lack of space I assume. I had narrowed down the problem but couldn't fix it, and of course as soon as you ask for help you figure it out anyway I'll give it a chance now.
Click to expand...
Click to collapse