Flash ICS rom via adb

[AndroidTrainee]

I just noticed that there is a problem on the push the final command line says no space left on the device

Sent from my MB860

[Ads]

[BHuber09]

That means you have >7gb on the internal storage.. seems a little ridiculous after a sbf

Sent from my Galaxy Nexus using Tapatalk 2

[AndroidTrainee]

Ikr, any ideas?

Sent from my MB860

[BHuber09]

Factory reset is the only one I can think of

Sent from my Galaxy Nexus using Tapatalk 2

[AndroidTrainee]

I'll try after sbf and root

Sent from my MB860

[BHuber09]

For future reference next time you could just
Adb shell rm /data/
Adb shell rm /cache/

That removes all those files in there, which is what a reset does

Sent from my Galaxy Nexus using Tapatalk 2

[AndroidTrainee]

Kk, i will continue tomorrow , of course thanks for every second you expend here, good night.

Sent from my MB860

[Wizard0f0s]

For future reference next time you could just
Adb shell rm /data/
Adb shell rm /cache/

That removes all those files in there, which is what a reset does

Sent from my Galaxy Nexus using Tapatalk 2

You may have to use the recursive and force flags too. I do just out of habit, so I don't know if it works without them. That would be:

Adb shell rm - rf /data/*
Adb shell rm - rf /cache/*

Doing it as /data/, etc, without the * may remove the data and cache directories as well. It "should" rebuild them on the next boot, but that's another thing I've never tried before. Worst case you would manually recreate the directories and reboot again.

The main potential issue I see with doing this is the "rm /system". You'll delete the ADB binary in the process and that will kill your session (leaving you to sbf again). I've never tried to flash like this before, but there are a couple ways I can see to do it (potentially).

1) Setup adb and busybox in a partition you won't wipe until after the install (like tmp). Without rebooting, restart adb using the one in tmp (essentially kill adb and then run the ADB binary in tmp, but you'll need to do it in one shot). You may be able to run something like (adb shell "killall adb;/tmp/adb &"). I may have the syntax wrong for the killall command. The reason for busybox is that you will remove your ability to copy and link files when you remove it (when you delete /system). You'll have to manually go through the updater-script (in the zipped META-INF folder) after you get system copied in and create all the symlinks. You'll need busybox to do that.

2) Copy things over individually. Much slower and will take a lot more time. Possibly easier to not create an sbf situation though.

I'm quite entrigued by this. I've never tried this before. :beer:

Sent from my DROIDX using Tapatalk 2

[BHuber09]

You may have to use the recursive and force flags too. I do just out of habit, so I don't know if it works without them. That would be:

Adb shell rm - rf /data/*
Adb shell rm - rf /cache/*

Doing it as /data/, etc, without the * may remove the data and cache directories as well. It "should" rebuild them on the next boot, but that's another thing I've never tried before. Worst case you would manually recreate the directories and reboot again.

The main potential issue I see with doing this is the "rm /system". You'll delete the ADB binary in the process and that will kill your session (leaving you to sbf again). I've never tried to flash like this before, but there are a couple ways I can see to do it (potentially).

1) Setup adb and busybox in a partition you won't wipe until after the install (like tmp). Without rebooting, restart adb using the one in tmp (essentially kill adb and then run the ADB binary in tmp, but you'll need to do it in one shot). You may be able to run something like (adb shell "killall adb;/tmp/adb &"). I may have the syntax wrong for the killall command. The reason for busybox is that you will remove your ability to copy and link files when you remove it (when you delete /system). You'll have to manually go through the updater-script (in the zipped META-INF folder) after you get system copied in and create all the symlinks. You'll need busybox to do that.

2) Copy things over individually. Much slower and will take a lot more time. Possibly easier to not create an sbf situation though.

I'm quite entrigued by this. I've never tried this before. :beer:

Sent from my DROIDX using Tapatalk 2

Haha I knew you'd drop in. But you know more about android and the file systems than I do so I was also hoping you'd jump in.
But for real I didn't expect it to work, but its worth a shot if it does haha

Sent from my Galaxy Nexus using Tapatalk 2

[Wizard0f0s]

Haha I knew you'd drop in. But you know more about android and the file systems than I do so I was also hoping you'd jump in.
But for real I didn't expect it to work, but its worth a shot if it does haha

Sent from my Galaxy Nexus using Tapatalk 2

Yep. I'd never thought about doing this w/o a card available.

You were doing fine w/o me too. All I do is tweak til I break it more or fix it. The trick sometimes is figuring out what I did

Sent from my DROIDX using Tapatalk 2