Database Develop

Noobie question

so i managed to root my g1....now when i install apps how do i know that its installing in the memory card and not the phone memory
2:what are the full advantages of rooting
3:anythin i should know since i did my rootin

1. Type in terminal
Code:
busybox df -h
and look in your /system/sd, if any of it used - then you're doing it right.
2. Tethering, apps2sd, Ram swap, overclocking, different roms, etc,
3. Search before asking, google is your friend, post in the right forum (which you did). You can figure out everything else else.
Good luck.

borodin1 said:
1. Type in terminal
Code:
busybox df -h
and look in your /system/sd, if any of it used - then you're doing it right.
2. Tethering, apps2sd, Ram swap, overclocking, different roms, etc,
3. Search before asking, google is your friend, post in the right forum (which you did). You can figure out everything else else.
Good luck.
Click to expand...
Click to collapse
alrigth actually i searched but i didnt have the right question so i wasnt gettin the answer
thanx

borodin1 said:
1. Type in terminal
Code:
busybox df -h
and look in your /system/sd, if any of it used - then you're doing it right.
2. Tethering, apps2sd, Ram swap, overclocking, different roms, etc,
3. Search before asking, google is your friend, post in the right forum (which you did). You can figure out everything else else.
Good luck.
Click to expand...
Click to collapse
I get permission denied

what do you get if you type
Code:
su
and which rom are on you?

borodin1 said:
what do you get if you type
Code:
su
and which rom are on you?
Click to expand...
Click to collapse
it asks me if i want to allow or deny

Allow it (and check the mark to always to it, you'll get sick of allowing it every time).
See if works
Code:
su
busybox df-h
This is weird though....this does not modify anything else... just gives you the output of your partitions.... works for me without su prompt.

borodin1 said:
Allow it (and check the mark to always to it, you'll get sick of allowing it every time).
See if works
Code:
su
busybox df-h
This is weird though....this does not modify anything else... just gives you the output of your partitions.... works for me without su prompt.
Click to expand...
Click to collapse
now it says busybox not found...
i completed everythin from here
http://theunlockr.com/2010/04/26/how-to-root-the-htc-g1dream/

Which rom did you flash once you rooted your phone? This will determine if you have busybox utility (which is helpfull)
OK.... here's another one
Code:
ls /system/sd/app
ls /data/app
That will give you a list of apps installed in each partition (/data/app is internal, /system/sd/app is external)
Doesn't quite give you the size or free space in each but gives you at least some idea of where your apps are going.
Good luck.

borodin1 said:
Which rom did you flash once you rooted your phone? This will determine if you have busybox utility (which is helpfull)
OK.... here's another one
Code:
ls /system/sd/app
ls /data/app
That will give you a list of apps installed in each partition (/data/app is internal, /system/sd/app is external)
Doesn't quite give you the size or free space in each but gives you at least some idea of where your apps are going.
Good luck.
Click to expand...
Click to collapse
i flashed the generic rom from unlockr

So it may not have that utility... sorry I'm not about to look through that whole website just to find out. And it's not a big deal for most people anyway. I'm sure you will not be on that rom too long anyway .

borodin1 said:
So it may not have that utility... sorry I'm not about to look through that whole website just to find out. And it's not a big deal for most people anyway. I'm sure you will not be on that rom too long anyway .
Click to expand...
Click to collapse
thats ok actually i think i need to downgrade to 1.5 again cuz i'm not even able to instal other roms it just aborts

[REQUEST] Can someone post a guide to how to get Froyo on eMMC?

I don't want to dual-boot, even, just have a nice "normal" Nookie Froyo install on eMMC. I've seen several allude to the fact that it worked for them but no reviews of how they did it. I've backed up my 2.1 install with Clockwork so I'm not really worried about that.
TIA.

It's quite simple actually. All you need is basic knowledge of adb.
All disclaimers apply, I'm not responsible for any damage. Just know that mine is running on internal partitions. And the SD does mount too!
Before doing anything, I would recommend applying a dd from your partitions to your pc.
With, for example on mmcblk0p1 (boot) adb: dd if=/dev/block/mmcblk0p1 of=boot.img
You should do that for each partition to be safe (0p1 to 0p8).
All the following commands can be execute one after one, the separations are only there to makes things a bit more clear.
Then,
Boot to a working Nookie (NF) with your uSD fresh from burning, without any google apps, and without any uSD damaged errors.
Empty your internal system and copy uSD system over, by doing:
- adb shell mount -o remount,rw /dev/block/mmcblk1 / (---there is a space after the 1---)
- adb shell
- mkdir tmpfolder
- mount /dev/block/mmcblk0p5 tmpfolder
- cd tmpfolder
- rm -r * (---note that there is space after the r---)
- cd ..
- cp -r system/* tmpfolder (---this will take a few minutes---)
- umount tmpfolder
Click to expand...
Click to collapse
Then, you need to boot push the attached files (bottom of post) except for the 2 vold files to your boot partition: mmcblk0p1. Unzip, copy content, not zip.
You could very well replace uImage with the new Quickie overclocked uImage for froyo (see dev thread).
To push attached files to boot, do:
- mount /dev/block/mmcblk0p1 tmpfolder
- exit
- adb push [folder-containing-4-attached-files-except-vold.fstab] tmpfolder
- adb shell
- umount tmpfolder
Click to expand...
Click to collapse
I would also recommend erasing all your data. But that's up to you, if you want to keep your data on it. In any case, you can revert back with the data.img you created above . So next part you could skip, haven't tried skipping personally:
Non mandatory, but you could do:
- mount /dev/block/mmcblk0p6 tmpfolder
- cd tmpfolder
- rm -r *
- cd ..
- umount tmpfolder
Click to expand...
Click to collapse
Then you need to push vold.fstab and vold.conf (unzip volds, copy content) to system/etc
Copy vold's to system/etc:
- mount /dev/block/mmcblk0p5 tmpfolder
- exit
- adb push [folder-with-vold's] tmpfolder/etc/
- adb shell
- umount tmpfolder
- rm -r tmpfolder
- exit
Click to expand...
Click to collapse
Then shut down, remove uSD, and boot.
Again, you can choose to push the Quickie uImage, I you prefer, but the accelerometer doesn't work with it at the moment. The 950 kernel does sometimes crash on boot, but once booted is quite stable.
I think that's all folks. I could have been a bit vague at some times, but this should work. And if you made your imgs as recommended, you're bullet proof.
To revert back to initial state with img files, you need to copy files to sdcard and then dd:
- adb shell mount -o remount,rw /dev/block/mmcblk1p1 sdcard
- adb push XXX.img sdcard (--could take a few minutes--)
- dd if=XXXX.img of=/dev/block/mmcblk0pX
Click to expand...
Click to collapse
Do that for each partition.
For those who don't feel up to the task, I could make a CWR flashable zip file of all this. The only thing is, CWR dosen't boot on Nookie just yet. So you couldn't restore with a zip after the change.

[Before doing anything, I would recommend applying a dd from your partitions to your pc.
With, for example on mmcblk0p1 (boot) adb: dd if=/dev/block/mmcblk0p1 of=boot.img
You should do that for each partition to be safe (0p1 to 0p8).
[/QUOTE]
I am a little confused here. What are the names of the 7 other partitions? Thanks, Great guide btw!

See here.

Do you see improved speed and touch response running nookie from emmc?

im getting a "No such file or directory" error after "adb push [folder-with-vold's] tmpfolder/etc"
I created the directory but now it looks like i am stuck at the landscape android splash screen on boot...
any ideas? I am attempting to redo the whole process again just incase i missed something.

Sorry, there's a slash after etc.
Make sure you've copied the systen files, with "ls" inside tmpfolder where you copied system. Should be a etc folder there.
Sam

to the op: I'm not knocking you here, but do you have a basic idea of generic linux file hierarchy or operations in general? Getting a basic grasp on working with files in a linux terminal will make all of these operations make a lot more sense, since most "adb shell" commands are basic linux commands.

FastCR said:
to the op: I'm not knocking you here, but do you have a basic idea of generic linux file hierarchy or operations in general? Getting a basic grasp on working with files in a linux terminal will make all of these operations make a lot more sense, since most "adb shell" commands are basic linux commands.
Click to expand...
Click to collapse
Thanks but I don't see how that comment adds anything here.
Looks like the issue is above commands copy the actual system folder (not the contents of the folder) To the root of the partition. ls shows the folder "system" not the contents including etc. They are inside the folder but if the partition is mounted as system then the folder is redundant. Will check copying the contents and see if that helps.
Once I get it working in will post back to let others know
**** in the first block of code replace
Code:
- cp -r system tmpfolder (---this will take a few minutes---)
with
Code:
- cp -r system[B]/*[/B] tmpfolder (---this will take a few minutes---)
many thanks!

FastCR said:
to the op: I'm not knocking you here, but do you have a basic idea of generic linux file hierarchy or operations in general? Getting a basic grasp on working with files in a linux terminal will make all of these operations make a lot more sense, since most "adb shell" commands are basic linux commands.
Click to expand...
Click to collapse
Why would you go out of your way to say that? It's not constructive. As a junior member with three posts and 0 thanks after a year and a half, sharpen your teeth here at XDA before you act like a big shot.

Right thanks. Changed it.
Has it worked for you?
Sent from my HTC Desire using XDA App

samuelhalff said:
You could very well replace uImage with the new Quickie overclocked uImage for froyo (see dev thread).
Click to expand...
Click to collapse
Are you certain on this part? Last I read in that thread, Froyo needs a different minimum kernel.
UPDATE: Nevermind, I missed this updated effort.
Homer

Well, last time I checked, my NC was running at 950 on froyo with setcpu.
Check the forum. There's a nookie version of quickie. Except accelerometer doesn't work..

First, huge thanks to the second poster - great guide! Can we sticky this?
Second, yes I know what dd does, etc, I've been working with Linux for about ten years . I just don't know the ins and outs of embedded devices yet.

samuelhalff said:
Right thanks. Changed it.
Has it worked for you?
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
yeah i was up till 4am last night but got it working. first i tried to use my existing nf sd card... bad idea. would boot from emmc to the touch android screen to begin, but could not get past. i assume it was the issue on nookdevs because wifi was not enabled. so i removed the setupwizard.apk but somehow bricked and was unable to boot from emmc. so i took the following steps to get things working properly:
1. reimage boot and system from the stock 1.0.1 images and reset the nook to stock, didnt even touch. at the intro screen i just powered it off.
2. next i took a fresh nf sdcard and run steps from your post(with the correction to copy system contents)
3. from there i had a working nf from sdcard! i did my tweaks (google apps, market fix and button remapping from nookdevs froyo tips)
i might to put together a post with a more verbose set of instructions for a one stop froyo shop but if i do i will be sure to give you credit for your contribution.
thanks again!

Hi,
Second, yes I know what dd does, etc, I've been working with Linux for about ten years . I just don't know the ins and outs of embedded devices yet.
Click to expand...
Click to collapse
Well, that's a nice contrast. I've been working on Linux/Android for about 2 months now
I should have mentioned that the NF uSD Card must be a newly burnt image, without all the nookie tips added to it. Of course, your Google framework will crash if you port it without your data.
By the way, there's a nice trick to get past the numb android interface, simply touch every corner of the screen, starting with top left and going clockwise. You'll then be sent the your home screen, and from there you'll log on to google account again.
I think the best way of doing it would to create a flashable .zip, which I'll make tonight if I find the time and if people are really interested. But don't forget CWR dosen't work on nookie for the time being. The only way back would be through adb.
So, does anyone wish to have a flashable zip of this? Or will it be a waist of time?
Sam

samuelhalff said:
Hi,
Well, that's a nice contrast. I've been working on Linux/Android for about 2 months now
I should have mentioned that the NF uSD Card must be a newly burnt image, without all the nookie tips added to it. Of course, your Google framework will crash if you port it without your data.
By the way, there's a nice trick to get past the numb android interface, simply touch every corner of the screen, starting with top left and going clockwise. You'll then be sent the your home screen, and from there you'll log on to google account again.
I think the best way of doing it would to create a flashable .zip, which I'll make tonight if I find the time and if people are really interested. But don't forget CWR dosen't work on nookie for the time being. The only way back would be through adb.
So, does anyone wish to have a flashable zip of this? Or will it be a waist of time?
Sam
Click to expand...
Click to collapse
I would love a flashable .zip. I think many others would as well.

starkruzr said:
I would love a flashable .zip. I think many others would as well.
Click to expand...
Click to collapse
Can't wait for a flashable zip. Maybe even some cm7 release candidates would make me real happy.
Sent from Nooted NookColor using XDA App

[Q] ADB "No space left on device"

Hey guys
So I am currently running 2.3.3 on my N1. I manually flashed the update from Here. I used the "Modified GRI40".
So after update, I noticed that my adfree wasn't working. Running the app, it tells me my host file is up to date. However, no ads are being blocked. Same after uninstalling and re-installing the app. So then I decided to try to copy the host file over manually using adb.
I run adb and get root prompt. Then I mount /system as rw using
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
It appears to work. So then I try copying the host file to /system/etc using
Code:
cp hosts /system/etc
Then I get the following error.
"write error: No space left on device"
But i do, over 30mb of free space.
So I don't know what the issue is. Im thinking that maybe /system isn't being mounted as RW so it is giving the error??
Any help would be much appreciated.
Thanks!

Did you check the /system free space, or /data?

Try doing a df -h from the terminal to verify that you do, indeed, have free space on /system as well as /data, as Jack_R1 mentioned.

codesplice said:
Try doing a df -h from the terminal to verify that you do, indeed, have free space on /system as well as /data, as Jack_R1 mentioned.
Click to expand...
Click to collapse
Well looks like somehow I don't have any space left. I went to go download a terminal application from the market but it errored saying no space left.
So now I can't even install new apps.
However, under settings->storage it says I have 28MB of free space left.
Any ideas?
Sent from my Nexus One using XDA App

Reboot, wipe Dalvik cache.
Go to Manage Applications, clear browser cache.
If it restores you some space - great, proceed with what codesplice suggested above.
If it doesn't - backup, wipe and reflash.
If no backup installed - you're out of luck.

Since you seem to have adb functioning, you can run adb shell df -h to get a readout of your available space on your different file systems. This could help troubleshoot the issue.
Additionally, rather than doing a long manual "mount" command, you could simply do an adb remount to automagically remount all file systems in read/write mode.
The indication under Settings --> Storage indicates free space on /data, I believe, and gives no indication of /system (where you're trying to copy the hosts file).
Another thought (sorry this isn't really coherent at this point...): What if you were to remove your default hosts file and then push the new one?
Code:
> adb remount
Remount succeeded
> adb shell rm /system/etc/hosts
> adb push hosts /system/etc/hosts
> adb shell chmod 644 /system/etc/hosts

codesplice said:
Another thought (sorry this isn't really coherent at this point...): What if you were to remove your default hosts file and then push the new one?
Code:
> adb remount
Remount succeeded
> adb shell rm /system/etc/hosts
> adb push hosts /system/etc/hosts
> adb shell chmod 644 /system/etc/hosts
Click to expand...
Click to collapse
Well that's thing, that is why I started this thread because I was trying to use ADB to push a new hosts file but got the no space error. So I already tried that.
Sent from my Nexus One using XDA App

I was asking if you had specifically tried removing the old one and replacing it rather than just overwriting.

Oh I see what you mean. But no I have not, let me give it a shot.
**Nope didn't work. I still got the same error, no space left on device.

Have you had the opportunity to do adb shell df -h yet?

codesplice said:
Since you seem to have adb functioning, you can run adb shell df -h to get a readout of your available space on your different file systems. This could help troubleshoot the issue.
Additionally, rather than doing a long manual "mount" command, you could simply do an adb remount to automagically remount all file systems in read/write mode.
The indication under Settings --> Storage indicates free space on /data, I believe, and gives no indication of /system (where you're trying to copy the hosts file).
Another thought (sorry this isn't really coherent at this point...): What if you were to remove your default hosts file and then push the new one?
Code:
> adb remount
Remount succeeded
> adb shell rm /system/etc/hosts
> adb push hosts /system/etc/hosts
> adb shell chmod 644 /system/etc/hosts
Click to expand...
Click to collapse
No to hijack this thread, but I just wanted to ask, does "adb remount" require root?

Brownbay said:
No to hijack this thread, but I just wanted to ask, does "adb remount" require root?
Click to expand...
Click to collapse
yes, without root access to the filesystem, adb remount will fail.

So when I try adb shell df -h, I get:
"-h: No such filesystem or directory"

You don't have busybox. Try running "adb shell df", maybe it'll still give some info.

Ok when I ran adb shell df I got a listing of filesystems. /system says size 145M and used 145M. So apparently it is full.
How could that be though?

It could be that you have some bad blocks on your /system partition (you can generally only check by doing a wipe operation in recovery and then viewing the log). These bad blocks could take up space that would otherwise store your system data, and could push you over capacity.
Or you could just have some extra bloat related to that ROM. You could drive to remove some of the applications on /system that you don't have use for (the Amazon MP3 thing, for instance). I'd suggest using Titanium Backup to do this, but you can also do it by manually using the adb shell.
Alternatively, a full wipe and clean reinstall may help make sure you don't have anything left over taking up space.

I'm thinking about just flashing a new ROM altogether as I am also having issues with the battery. Under usage, Android OS now shows somewhere around 35% of the usage. This only started happening after updating to 2.3.3.
I've always ran stock ROMs, so I haven't played with any of the custom ROMs out there. Are there any ROMs you recommend for a first timer?
*Sidenote* So a nandroid backup is a complete backup of the system state correct?
So after flashing a ROM, I can just restore the nandroid backup and my phone will be exactly as it was with the old ROM and user data?

decoyjoe said:
I'm thinking about just flashing a new ROM altogether as I am also having issues with the battery. Under usage, Android OS now shows somewhere around 35% of the usage. This only started happening after updating to 2.3.3.
I've always ran stock ROMs, so I haven't played with any of the custom ROMs out there. Are there any ROMs you recommend for a first timer?
*Sidenote* So a nandroid backup is a complete backup of the system state correct?
So after flashing a ROM, I can just restore the nandroid backup and my phone will be exactly as it was with the old ROM and user data?
Click to expand...
Click to collapse
I've been really impressed with the Kang-o-rama ROMs. Basically prettied-up versions of Cyanogen. The latest release is a beta based on CM7, so still has a few issues. The prior release (KOR 1.1Final) is still quite solid.
And yes, a nandroid backup creates a copy of your current disk image, which can then be restored at any time to revert back to a previously-working configuration (great for when you break stuff!).

decoyjoe said:
I'm thinking about just flashing a new ROM altogether as I am also having issues with the battery. Under usage, Android OS now shows somewhere around 35% of the usage. This only started happening after updating to 2.3.3.
I've always ran stock ROMs, so I haven't played with any of the custom ROMs out there. Are there any ROMs you recommend for a first timer?
*Sidenote* So a nandroid backup is a complete backup of the system state correct?
So after flashing a ROM, I can just restore the nandroid backup and my phone will be exactly as it was with the old ROM and user data?
Click to expand...
Click to collapse
Exactly Remember to wipe before restoring

Oh and that brings up another thought.
So if before I flash a new ROM, I do a Titanium Backup and then flash the ROM...
Would I then be able to restore that Titanium Backup made on the previous stock ROM to restore all my apps and user data?

[Q] How to restore wiped files?

I unlocked my HTC One Bootloader, but all my files got wiped :crying:
How can i restore files? I lost all my photos and whatsapp chat history. There must be a possibility?! But how?

thekkk said:
I unlocked my HTC One Bootloader, but all my files got wiped :crying:
How can i restore files? I lost all my photos and whatsapp chat history. There must be a possibility?! But how?
Click to expand...
Click to collapse
I don't think you can recover. It told you this when unlocking.

mb_guy said:
I don't think you can recover. It told you this when unlocking.
Click to expand...
Click to collapse
It told me that personal settings will be deleted, and i thought that only would be settings, etc...
and in the tutorial i've read there was no warning for this

Yeah I don't think you'll get anything back easily at all. Keep that phone backed up in the future!
Sent from my HTC One using Tapatalk

thekkk said:
It told me that personal settings will be deleted, and i thought that only would be settings, etc...
and in the tutorial i've read there was no warning for this
Click to expand...
Click to collapse
No the bootloader unlock screen says personal data (not settings) will be wiped which include the virtual sdcard (/data/media/0)
{
"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"
}
btw this also deleted stock apps like flashlight, calculator, sound trimmer, tuneIn, SoundHound etc.... which are stored in /data/preload

bbinder said:
Yeah I don't think you'll get anything back easily at all. Keep that phone backed up in the future!
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
It doesnt matter how difficult it is, but somehow i'm sure there must be a way, the question is how. Because every recovery software cant be used because of de MTP-mode

thekkk said:
It doesnt matter how difficult it is, but somehow i'm sure there must be a way, the question is how. Because every recovery software cant be used because of de MTP-mode
Click to expand...
Click to collapse
Sure. I just personally think that you'll give up, given those circumstances Just being realistic...
Sent from my HTC One using Tapatalk

thekkk said:
the question is how. Because every recovery software cant be used because of de MTP-mode
Click to expand...
Click to collapse
The first step is to not boot the phone until you get a dump of your data partition. Booting to a custom recovery is okay--a full Android boot is not.
In recovery (using the ADB shell), umount data and get a dump of the data partition (/dev/block/mmcblk0p37) using "dd". Since you can't write to the data partition while making its dump, you'll need to write to /system. Since /system isn't very big, you'll need to do the dump in pieces of about 350 MB each (depends on how much free space you have in /system).
The "dd" parameters you'll need are "bs" to speed things up, "skip" to tell it where to start the chunk, and "count" to determine how big the chunk is. Since /data is 25.6 GB, you'll need to do this 60-70 times, and after each chunk, use "adb pull" to copy the chunk to your computer. When you have all the chucks, reassemble them and make sure it's the same size as /dev/block/mmcblk0p37. Make sure it's a valid ext4 filesystem. Then you can start using data recovery tools.
thekkk said:
It doesnt matter how difficult it is, but somehow i'm sure there must be a way,
Click to expand...
Click to collapse
So put your money where your mouth is and do it.

fenstre said:
The first step is to not boot the phone until you get a dump of your data partition. Booting to a custom recovery is okay--a full Android boot is not.
In recovery (using the ADB shell), umount data and get a dump of the data partition (/dev/block/mmcblk0p37) using "dd". Since you can't write to the data partition while making its dump, you'll need to write to /system. Since /system isn't very big, you'll need to do the dump in pieces of about 350 MB each (depends on how much free space you have in /system).
The "dd" parameters you'll need are "bs" to speed things up, "skip" to tell it where to start the chunk, and "count" to determine how big the chunk is. Since /data is 25.6 GB, you'll need to do this 60-70 times, and after each chunk, use "adb pull" to copy the chunk to your computer. When you have all the chucks, reassemble them and make sure it's the same size as /dev/block/mmcblk0p37. Make sure it's a valid ext4 filesystem. Then you can start using data recovery tools.
So put your money where your mouth is and do it.
Click to expand...
Click to collapse
That sounds like something, first of all thanks for your input!
But how should i run this command without booting into android (I'm in clockwork-touch recovery, but doesnt seem to work)? This command works (when booted into android), i've tried it with 'dd', so i guess thats the correct way!
=> If i have to boot into android anyway to do this, i would also have an OTG plus USB-Stick (32GB), then i could do it in about 2 parts to save it directly to the usb-stick. Would that be the better aproach instead of writing it to the /system? because i don't know what action writes to the /sdcard
Just to clarify, i have to execute the following command one after the other(?) :
$ dd if=/dev/block/mmcblk0p37 bs=367001600 count=1 skip=0 of=/system/chunk1.img
adb pull /system/chunk1.img .
$ dd if=/dev/block/mmcblk0p37 bs=367001600 count=1 skip=1 of=/system/chunk2.img
adb pull /system/chunk2.img .
$ dd if=/dev/block/mmcblk0p37 bs=367001600 count=1 skip=2 of=/system/chunk3.img
adb pull /system/chunk3.img .
Do i have to make something special that i can reassemble them later or are there programms out there for that problem?

Um, every time you boot to android you are rewriting the very flash memory you are trying to recover.
The ratio of the amount of work required vs the chances of success is not a favorable one. Unless you are trying to recover video of 'baby's first steps' or a bitcoin private key, I would let this go..
Sent from my HTC One using xda app-developers app

NxNW said:
Um, every time you boot to android you are rewriting the very flash memory you are trying to recover.
The ratio of the amount of work required vs the chances of success is not a favorable one. Unless you are trying to recover video of 'baby's first steps' or a bitcoin private key, I would let this go..
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
There were memories on it, and it would be a pity if they're all gone now
I'm not that type of guy to give up, I have the motivation and the time to do it. I will give it at least a try, I have nothing to loose, except time - but that doesnt matter because I wanna have these data's back
The only one problem I see now is that if I read the block step by step and save this, I don't know how I should reassemble all these files. Anyone has an idea? Reading a block and pull it out of the phone isnt the problem

thekkk said:
=> If i have to boot into android anyway to do this, i would also have an OTG plus USB-Stick (32GB), then i could do it in about 2 parts to save it directly to the usb-stick. Would that be the better aproach instead of writing it to the /system? because i don't know what action writes to the /sdcard
Just to clarify, i have to execute the following command one after the other(?) :
$ dd if=/dev/block/mmcblk0p37 bs=367001600 count=1 skip=0 of=/system/chunk1.img
adb pull /system/chunk1.img .
$ dd if=/dev/block/mmcblk0p37 bs=367001600 count=1 skip=1 of=/system/chunk2.img
adb pull /system/chunk2.img .
$ dd if=/dev/block/mmcblk0p37 bs=367001600 count=1 skip=2 of=/system/chunk3.img
adb pull /system/chunk3.img .
Click to expand...
Click to collapse
That looks exactly right, except that normally people use "bs" as a smaller value and "count" and "skip" as a multiple of that value--I'm not sure whether it makes a difference in the real world. (I.e., instead of bs=4096 count=1 skip=1, people normally write bs=1024 count=4 skip=4.)
thekkk said:
I'm not that type of guy to give up, I have the motivation and the time to do it. I will give it at least a try, I have nothing to loose, except time - but that doesnt matter because I wanna have these data's back
The only one problem I see now is that if I read the block step by step and save this, I don't know how I should reassemble all these files. Anyone has an idea? Reading a block and pull it out of the phone isnt the problem
Click to expand...
Click to collapse
You are awesome. I was sure you'd give up.
And using a USB stick is a very good idea, but since you only have one USB port you can't type the commands on your computer using ADB. And yes, ADB should work fine when you're booted into recovery. If CWM doesn't work, you could try TWRP instead. TWRP will actually let you type the commands on the phone's screen (no need for ADB), so you can attach the USB stick.
If the chunks line up exactly (they will if you use dd like you are), on OSX or Linux you can use a program called "cat" to just dump them into one file: "cat a.txt b.txt" prints both files to the screen, so "cat part1 part2 part3 > combined" will join files into a new one (the new file is overwritten, so be careful). I would have to search online for how to join files on windows. If the chunks overlap, this forum post has a short python script that will detect a matching region at the end of one file and the start of the next and join them to a new file.
Note also that this doesn't guarantee your data will be recoverable. I wish you the best of luck, but flash storage is even trickier than hard drives, because due to wear leveling, it's possible the data you want isn't even being exposed as visible to the OS, with different NAND blocks shown instead.

fenstre said:
That looks exactly right, except that normally people use "bs" as a smaller value and "count" and "skip" as a multiple of that value--I'm not sure whether it makes a difference in the real world. (I.e., instead of bs=4096 count=1 skip=1, people normally write bs=1024 count=4 skip=4.)
You are awesome. I was sure you'd give up.
And using a USB stick is a very good idea, but since you only have one USB port you can't type the commands on your computer using ADB. And yes, ADB should work fine when you're booted into recovery. If CWM doesn't work, you could try TWRP instead. TWRP will actually let you type the commands on the phone's screen (no need for ADB), so you can attach the USB stick.
If the chunks line up exactly (they will if you use dd like you are), on OSX or Linux you can use a program called "cat" to just dump them into one file: "cat a.txt b.txt" prints both files to the screen, so "cat part1 part2 part3 > combined" will join files into a new one (the new file is overwritten, so be careful). I would have to search online for how to join files on windows. If the chunks overlap, this forum post has a short python script that will detect a matching region at the end of one file and the start of the next and join them to a new file.
Note also that this doesn't guarantee your data will be recoverable. I wish you the best of luck, but flash storage is even trickier than hard drives, because due to wear leveling, it's possible the data you want isn't even being exposed as visible to the OS, with different NAND blocks shown instead.
Click to expand...
Click to collapse
If that doesnt work on windows I have no problem to get a linux machine. What really causes concern, is that i allready saved multiple chunks with 350mb and also about 4GB and opened them in DiskInternals Linux Reader, but there was ever the same content, multiple folders and 2 files, but nearly everything about on 0kb, so it was nearly empty. Is that only because the files aren't dumped in one file?
What I actually don't get is that your writing 4*1024, but that are just 4096 Bytes, but before you talked about 350MB. I found out that for this I could also use bs=350M (M for megabytes), but I dont know if that really is a problem, couldn't explain to myself why, but you never know.
When I write directly to the USB, I'm also able to scale the size up to 4GB, because of the file-system-restriction. That would go faster. But I will try to firstly create the 60-70 chunks with 350MB and try to dump them into one file. Hope this will get me where I want to go.

thekkk said:
i allready saved multiple chunks with 350mb and also about 4GB and opened them in DiskInternals Linux Reader, but there was ever the same content, multiple folders and 2 files, but nearly everything about on 0kb, so it was nearly empty. Is that only because the files aren't dumped in one file?
What I actually don't get is that your writing 4*1024, but that are just 4096 Bytes, but before you talked about 350MB. I found out that for this I could also use bs=350M (M for megabytes)...
When I write directly to the USB, I'm also able to scale the size up to 4GB, because of the file-system-restriction. That would go faster. But I will try to firstly create the 60-70 chunks with 350MB and try to dump them into one file. Hope this will get me where I want to go.
Click to expand...
Click to collapse
What I wrote was just an example--I'm not actually suggesting you get the dump in 4 KB chunks.
As far as the chunk sizes, you just need to make sure they line up. If you start with a 350 MB chunk that was made with "bs=1M count=350", you can make the second chunk (a bigger one) with "bs=1M skip=350 count=4000". The problem is that since you used exact byte numbers for BS, it's more complicated to get them to line up correctly. For example, 1M is probably 1000000 bytes in this program, but it could also be 2^20 bytes. Basically, chuck size doesn't matter as long as they're properly lined up. Also, I wouldn't worry about the recovery tool failing until you have all or most of the chunks. However, I see that DiskInternals Linux Reader is a filesystem browser, not a recovery tool. You need a recovery tool, since the files are technically deleted (actually, the filesystem is wiped). You need a tool that looks for the data (all bytes), not what the filesystem officially says is present.

fenstre said:
What I wrote was just an example--I'm not actually suggesting you get the dump in 4 KB chunks.
As far as the chunk sizes, you just need to make sure they line up. If you start with a 350 MB chunk that was made with "bs=1M count=350", you can make the second chunk (a bigger one) with "bs=1M skip=350 count=4000". The problem is that since you used exact byte numbers for BS, it's more complicated to get them to line up correctly. For example, 1M is probably 1000000 bytes in this program, but it could also be 2^20 bytes. Basically, chuck size doesn't matter as long as they're properly lined up. Also, I wouldn't worry about the recovery tool failing until you have all or most of the chunks. However, I see that DiskInternals Linux Reader is a filesystem browser, not a recovery tool. You need a recovery tool, since the files are technically deleted (actually, the filesystem is wiped). You need a tool that looks for the data (all bytes), not what the filesystem officially says is present.
Click to expand...
Click to collapse
I'm trying it now with the following:
$ dd if=/dev/block/mmcblk0p37 of=/system/chunk1.img bs=1048576 count=350 skip=350
One sentence i don't understand, what do you mean by "properly lined up"? Are they not properly lined up when i use the above 1048576 Bytes (exactly 1 MB)?
For the recovery tool i will have a look, thanks for the tipp, if i remember correct, there was stated that this also can recover

thekkk said:
I$ dd if=/dev/block/mmcblk0p37 of=/system/chunk1.img bs=1048576 count=350 skip=350
One sentence i don't understand, what do you mean by "properly lined up"? Are they not properly lined up when i use the above 1048576 Bytes (exactly 1 MB)?
Click to expand...
Click to collapse
That's fine. But you were on to something with the USB stick idea--if I were you, I'd much rather make two dump chunks than 60.
What I mean by "lining up" is that this the following two chunks will not line up--they will have a gap between with missing data:
dd if=/dev/block/mmcblk0p37 of=/system/chunk1.img bs=1M count=350 skip=0
dd if=/dev/block/mmcblk0p37 of=/system/chunk2.img bs=1048576 count=350 skip=350
These two chunks will have overlapping data:
dd if=/dev/block/mmcblk0p37 of=/system/chunk1.img bs=1048576 count=350 skip=0
dd if=/dev/block/mmcblk0p37 of=/system/chunk2.img bs=1M count=350 skip=350
It's not an issue if you're starting from chunk 0 and using the same "bs", but if you wanted to keep the chunks you already made (with a very specific size), and continue making 4GB chunks after that, it might be tricky to get bs/count/skip right so the chunks don't overlap with your data and don't skip any, either. This is "lining up" properly.

fenstre said:
That's fine. But you were on to something with the USB stick idea--if I were you, I'd much rather make two dump chunks than 60.
What I mean by "lining up" is that this the following two chunks will not line up--they will have a gap between with missing data:
dd if=/dev/block/mmcblk0p37 of=/system/chunk1.img bs=1M count=350 skip=0
dd if=/dev/block/mmcblk0p37 of=/system/chunk2.img bs=1048576 count=350 skip=350
These two chunks will have overlapping data:
dd if=/dev/block/mmcblk0p37 of=/system/chunk1.img bs=1048576 count=350 skip=0
dd if=/dev/block/mmcblk0p37 of=/system/chunk2.img bs=1M count=350 skip=350
It's not an issue if you're starting from chunk 0 and using the same "bs", but if you wanted to keep the chunks you already made (with a very specific size), and continue making 4GB chunks after that, it might be tricky to get bs/count/skip right so the chunks don't overlap with your data and don't skip any, either. This is "lining up" properly.
Click to expand...
Click to collapse
Thanks for explenation
So i have my 77 .img chunk-files all on my pc. Btw, Windows does have "cat" also, but only in Windows Powershell, and it's soooo slow... and somehow the combined files are bigger I'll use it in linux, better approach i guess
After I have my final image, I mount that into my ubuntu machine and then try to recover, right? You said something about a "valid EXT4" filesystem, what do I have to pay attention for this? Unfortunatly I'm not a linux-Guru, but should be able to handle it with some help. I think first I try the recover tool from ubuntu that is built-in, because I havn't searched for an alternative. I don't think that i need a special one explicit for Android-files?
Many thanks that you take time and try to help me :good: , I don't think I'm wide away from my goal now. I hope that I'm a lucky guy and I can restore, at least, some files.

thekkk said:
So i have my 77 .img chunk-files all on my pc. Btw, Windows does have "cat" also, but only in Windows Powershell, and it's soooo slow... and somehow the combined files are bigger I'll use it in linux, better approach i guess
Click to expand...
Click to collapse
if you want to use windows to combine multiple files, in a normal command prompt:
copy /b file1.img + file2.img + file3.img [+ etc] outputfile.img
@fenstre, couldn't he have mounted a 64GB OTG Stick and dd the entire partition there in one go?

nkk71 said:
if you want to use windows to combine multiple files, in a normal command prompt:
copy /b file1.img + file2.img + file3.img [+ etc] outputfile.img
@fenstre, couldn't he have mounted a 64GB OTG Stick and dd the entire partition there in one go?
Click to expand...
Click to collapse
Thanks that with windows-command promt worked without any problem
Because of the OTG Stick, the filesystem has a restriction of 4GB files, so I can't dd the entire partition in one go. And I also have the partition now in one .img file. But now I'm really stucked at how to recover this, with something from Windows or Linux? Tried DMDE, it showed me the partition but I couldn't really find some old files
Someone know's whats possible and which programms do you suggest? I have a EXT4 .IMG file with about 27GB and I wanna restore wiped files.

nkk71 said:
@fenstre, couldn't he have mounted a 64GB OTG Stick and dd the entire partition there in one go?
Click to expand...
Click to collapse
Yep, I'm not so smart. Even a 32 GB stick is big enough. He would still need to reformat the stick as EXT3/4 to get around the 4GB size limit, then he'd have to jump through hoops to read the data on his computer.
thekkk said:
Someone know's whats possible and which programms do you suggest? I have a EXT4 .IMG file with about 27GB and I wanna restore wiped files.
Click to expand...
Click to collapse
I've never used one--I just searched for "ext4 undelete". I suspect that Linux will have more options than Windows. This page also lists several utilities you can try:
https://wiki.archlinux.org/index.php/File_Recovery
Let us know how it goes!

[Q] [TL][H] Xperia T. Internal storage is dead.

Welcome guys, my internal storage is dead it happend after I accidentally cleaned it (wanted to format external sd card...). I can't copy anything from PC on to it. I have no access. I'm running cm-11-20140623-NIGHTLY-mint with ClockworkModRecovery 6.x
How can I fix it?
I tried so far again cleaning it from Android level and also formating partition via recovery mode.

deywid12345 said:
Welcome guys, my internal storage is dead it happend after I accidentally cleaned it (wanted to format external sd card...). I can't copy anything from PC on to it. I have no access. I'm running cm-11-20140623-NIGHTLY-mint with ClockworkModRecovery 6.x
How can I fix it?
I tried so far again cleaning it from Android level and also formating partition via recovery mode.
Click to expand...
Click to collapse
It's an old issue with formatting your internal memory with a custom ROM, and I think it's a permission issue. Can you access ADB through recovery?
http://forum.xda-developers.com/showpost.php?p=52698386&postcount=95

Antiga Prime said:
It's an old issue with formatting your internal memory with a custom ROM, and I think it's a permission issue. Can you access ADB through recovery?
Click to expand...
Click to collapse
How can I check that? (I installed CM with tutorial step-by-step). I can use recovery mode, fastboot, my phone boot up just fine. I have read this but I don't know what I have to do. Can you tell me ? I'm depressed.

deywid12345 said:
How can I check that? (I installed CM with tutorial step-by-step). I can use recovery mode, fastboot, my phone boot up just fine. I have read this but I don't know what I have to do. Can you tell me ? I'm depressed.
Click to expand...
Click to collapse
If you install a Terminal Emulator on your phone, you might be able to avoid using ADB. Ideally you should learn how to set up ADB (google it), or read this and see if it helps you.
Let me know if you install a Terminal Emulator (and are rooted).

Antiga Prime said:
If you install a Terminal Emulator on your phone, you might be able to avoid using ADB. Ideally you should learn how to set up ADB (google it), or read this and see if it helps you.
Let me know if you install a Terminal Emulator (and are rooted).
Click to expand...
Click to collapse
I have Terminal Emulator installed and rooted yet.
What's the next step. You are my only hope to fix this man.

deywid12345 said:
I have Terminal Emulator installed and rooted yet.
What's the next step. You are my only hope to fix this man.
Click to expand...
Click to collapse
Then open Terminal Emulator and run the following commands (ignore what is in parenthesis):
Code:
su (grant access)
cd /mnt/media_rw
ls -l
Let me know what that command shows you. It should show you something similar to what I have in the attached image.

Antiga Prime said:
Then open Terminal Emulator and run the following commands (ignore what is in parenthesis):
Code:
su (grant access)
cd /mnt/media_rw
ls -l
Let me know what that command shows you. It should show you something similar to what I have in the attached image.
Click to expand...
Click to collapse
yeah it do.
Code:
drwxr -xr -x root root 1971-03-04 01:26 sdcard0
drwxrwx--- media_rw media_rw 1970-01-01 01:00 sdcard1
drwx------ media_rw media_rw 1971-03-04 01:25 usbdisk
That's what i got (can't provide you any screenshot because of not working internal mem.
(it looks like i dont have write permissions, but i have completly no clue how to fix it, just wrote that)

deywid12345 said:
yeah it do.
Code:
drwxr -xr -x root root 1971-03-04 01:26 sdcard0
drwxrwx--- media_rw media_rw 1970-01-01 01:00 sdcard1
drwx------ media_rw media_rw 1971-03-04 01:25 usbdisk
That's what i got (can't provide you any screenshot because of not working internal mem.
(it looks like i dont have write permissions, but i have completly no clue how to fix it, just wrote that)
Click to expand...
Click to collapse
Well, then you should try the following. Open the terminal again, use "su" again to grant root access, and do the following:
Code:
su
cd /mnt/media_rw
busybox chown -R 2800:2800 sdcard0
chmod 0770 sdcard0
Then either try to take a photo or create a file in your internal memory, or reboot and test your internal memory.
Edit: Just to be clear, the default user/owner for Sony internal memory is 2800, mine is set to 1023 (media_rw), as most phones should have, because I have modded the ramdisk in my kernel in order to use a certain program.

Antiga Prime said:
Well, then you should try the following. Open the terminal again, use "su" again to grant root access, and do the following:
Code:
su
cd /mnt/media_rw
busybox chown -R 2800:2800 sdcard0
chmod 0770 sdcard0
Then either try to take a photo or create a file in your internal memory, or reboot and test your internal memory.
Edit: Just to be clear, the default user/owner for Sony internal memory is 2800, mine is set to 1023 (media_rw), as most phones should have, because I have modded the ramdisk in my kernel in order to use a certain program.
Click to expand...
Click to collapse
Man it works! I ****in owe you! Worked even without rebooting phone.
Love from Poland!

deywid12345 said:
Man it works! I ****in owe you! Worked even without rebooting phone.
Love from Poland!
Click to expand...
Click to collapse
No problem. In case you're interested in learning what that just did, you might want read this and this.

Antiga Prime said:
No problem. In case you're interested in learning what that just did, you might want read this and this.
Click to expand...
Click to collapse
Thanks for all your help !
Once I saw differents privilages letters i know its about it. Back in days I was working on FreeBSD (amateur) but had to deal with things like that.

Antiga Prime said:
Well, then you should try the following. Open the terminal again, use "su" again to grant root access, and do the following:
Code:
su
cd /mnt/media_rw
busybox chown -R 2800:2800 sdcard0
chmod 0770 sdcard0
Then either try to take a photo or create a file in your internal memory, or reboot and test your internal memory.
Edit: Just to be clear, the default user/owner for Sony internal memory is 2800, mine is set to 1023 (media_rw), as most phones should have, because I have modded the ramdisk in my kernel in order to use a certain program.
Click to expand...
Click to collapse
Working with Xperia V and just fixed my sd card. Thnx :good::good::good::good:

Antiga Prime said:
No problem. In case you're interested in learning what that just did, you might want read this and this.
Click to expand...
Click to collapse
And I'm here again, anew I got same situation but I can't fix it by applying these command. Can you help me? That's what I recieve.

deywid12345 said:
And I'm here again, anew I got same situation but I can't fix it by applying these command. Can you help me?
Click to expand...
Click to collapse
Are you booted up in Android? Maybe Sdcard0 needs to be unmounted first (although I've never had to unmount it). Maybe you should try running the command from recovery when the internal memory isn't mounted (and if it is, unmount it first).

Antiga Prime said:
No problem. In case you're interested in learning what that just did, you might want read this and this.
Click to expand...
Click to collapse
Antiga Prime said:
Are you booted up in Android? Maybe Sdcard0 needs to be unmounted first (although I've never had to unmount it). Maybe you should try running the command from recovery when the internal memory isn't mounted (and if it is, unmount it first).
Click to expand...
Click to collapse
I'm running TWRP 2.8.4.1 (OmniROM 4.4) when I go to mount section and uncheck "sdcard" it doesnt get saved and on reboot it again unmounted. How do I unmount it in right way?

deywid12345 said:
I'm running TWRP 2.8.4.1 (OmniROM 4.4) when I go to mount section and uncheck "sdcard" it doesnt get saved and on reboot it again unmounted. How do I unmount it in right way?
Click to expand...
Click to collapse
I don't think I understand what you're trying to say, but you don't have to reboot in order to unmount the sdcard. All you have to do is uncheck the "sdcard" in the mount section, and then run the chown command.
Then again, how did that happen again? Did you format your sdcard0 (internal memory) again?
Run the "mount" command in Android and see if your "Sdcard0" is formatted as Vfat. If it is, you won't be able to change ownership to the partition unless you format it again in TWRP so that it changes to ext4.

Antiga Prime said:
I don't think I understand what you're trying to say, but you don't have to reboot in order to unmount the sdcard. All you have to do is uncheck the "sdcard" in the mount section, and then run the chown command.
Then again, how did that happen again? Did you format your sdcard0 (internal memory) again?
Run the "mount" command in Android and see if your "Sdcard0" is formatted as Vfat. If it is, you won't be able to change ownership to the partition unless you format it again in TWRP so that it changes to ext4.
Click to expand...
Click to collapse
Yep It happend again by formatting internal storage.
But it's working back again ! Thanks mate!
I formated it via TWRP to EXT4 then adb commands and poof, it works! God bless you.

There are so many dead question threads but the helpfulness shown here just rekindled my faith in humanity

Didn't work for me, this is the output I got:
/system/bin/sh: <stdin>[2]: cd: /mnt/media_rw:
Permission denied
Sent from my Xperia T using XDA Free mobile app

thijs84 said:
Didn't work for me, this is the output I got:
/system/bin/sh: <stdin>[2]: cd: /mnt/media_rw:
Permission denied
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
If you're having trouble to even change directories to /mnt/media_rw/, how do you know that directory exists?
Are you trying that from recovery?