Develop Bugs

runnymede 2.4 aio force close problem, possibly XD2SDX related

Hi all,
Having some problems with running runnymede 2.4 on my desire. I have been out of the game for a while, the last time I played with custom roms was about 1.5 years ago when I first got the phone, and all I did was root it and install a stockish 2.2 rom.
I figured out how to s-off the phone and update the hboot, and have installed the fantastic looking runnymede 2.4 rom, but am getting heaps of force close errors. ive reflashed the rom a few times, and it runs fine for a few minutes, but after installing a few apps and whatnot then the errors begin. I have a feeling its related to XD2SDX not being set up correctly. I have a 16gb class 4 card in my phone atm, formatted with 1gb ext4 and the rest fat32 (with the fat32 partition being first). what makes me think this is initially the web browser works fine, but then once the errors start the browser wont even open, saying that i dont have enough free space remaining. If i go settings --> storage under internal available space it says 346mb used 666mb remaining. the only apps i have installed other than the included ones are handcent and mybackup (and let flash, youtube and tracks update).
I am about to try using a different 8gb sd card i have here out and see if that helps, as its a new trancend 16gb card, so may be dodgey. partitioned the card using gparted. first time i just used clockworkmods recovery sd card partition option, but noticed that it made an ext2 partition instead of ext4, was hoping that might be the problem but it seems it was not.
if i have missed any details please ask away, and thanks in advance for any help!

extra info:
$ su
# ls -l /data
drwxr-xr-x 2 0 0 4096 Nov 25 22:03 ad2sdx
drwxrwxr-x 2 1000 1000 4096 Nov 25 22:49 anr
drwxrwx--x 2 1000 1000 4096 Nov 26 02:01 app
lrwxrwxrwx 1 0 0 19 Nov 25 21:58 app-private -> /sd-ext/app-private
drwxr-xr-x 2 0 0 12288 Nov 25 21:55 app_s
drwx------ 5 1000 1000 4096 Nov 25 23:09 backup
drwxrwxrwx 2 0 0 20480 Nov 26 02:01 dalvik-cache
drwxrwx--x 5 0 0 12288 Nov 26 02:01 data
lrwxrwxrwx 1 0 0 14 Nov 25 21:58 data_s -> /sd-ext/data_s
lrwxrwxrwx 1 0 0 17 Nov 25 21:58 dontpanic -> /sd-ext/dontpanic
lrwxrwxrwx 1 0 0 11 Nov 25 21:58 etc -> /sd-ext/etc
lrwxrwxrwx 1 0 0 13 Nov 25 21:58 htcfs -> /sd-ext/htcfs
drwxr-xr-x 2 0 0 4096 Nov 25 21:56 lib_s
lrwxrwxrwx 1 0 0 13 Nov 25 21:58 local -> /sd-ext/local
lrwxrwxrwx 1 0 0 18 Nov 25 21:58 lost+found -> /sd-ext/lost+found
lrwxrwxrwx 1 0 0 12 Nov 25 21:58 misc -> /sd-ext/misc
lrwxrwxrwx 1 0 0 16 Nov 25 21:58 property -> /sd-ext/property
drwx------ 3 1000 1000 4096 Nov 25 21:59 secure
drwxrwxr-x 9 1000 1000 4096 Nov 26 02:01 system
drwxr-xr-x 2 1000 1000 4096 Nov 25 21:58 tombstones
lrwxrwxrwx 1 0 0 13 Nov 25 21:58 wimax -> /sd-ext/wimax
#

0M39A said:
Hi all,
Having some problems with running runnymede 2.4 on my desire. I have been out of the game for a while, the last time I played with custom roms was about 1.5 years ago when I first got the phone, and all I did was root it and install a stockish 2.2 rom.
I figured out how to s-off the phone and update the hboot, and have installed the fantastic looking runnymede 2.4 rom, but am getting heaps of force close errors. ive reflashed the rom a few times, and it runs fine for a few minutes, but after installing a few apps and whatnot then the errors begin. I have a feeling its related to XD2SDX not being set up correctly. I have a 16gb class 4 card in my phone atm, formatted with 1gb ext4 and the rest fat32 (with the fat32 partition being first). what makes me think this is initially the web browser works fine, but then once the errors start the browser wont even open, saying that i dont have enough free space remaining. If i go settings --> storage under internal available space it says 346mb used 666mb remaining. the only apps i have installed other than the included ones are handcent and mybackup (and let flash, youtube and tracks update).
I am about to try using a different 8gb sd card i have here out and see if that helps, as its a new trancend 16gb card, so may be dodgey. partitioned the card using gparted. first time i just used clockworkmods recovery sd card partition option, but noticed that it made an ext2 partition instead of ext4, was hoping that might be the problem but it seems it was not.
if i have missed any details please ask away, and thanks in advance for any help!
Click to expand...
Click to collapse
Exact same thing has happened to me. I am re-flashing the rom but this time I will let the system calm down after first boot and then reboot and then sign into google, facebook etc.
I remember this happened to me when i used supernova 2.4 with data2sd script. i did what i mentioned above and it sorted it self right out.
I will post later if this works with runnymede

same problem
i also have the same problem
amazing number of FCs
even after fresh flashing of rom i cant use browser - it says not enough free memory
FCs i get are - superuser, gmail, facebook, market etc.
i am only talking about a fresh install without adding any market apps or titanium backup (i cant install Ti Backup coz market FCs)
I am on stock hboot
i think maybe its beacuse of stock hboot
but i think seb will take care of it soon

0M39A said:
Hi all,
Having some problems with running runnymede 2.4 on my desire. I have been out of the game for a while, the last time I played with custom roms was about 1.5 years ago when I first got the phone, and all I did was root it and install a stockish 2.2 rom.
I figured out how to s-off the phone and update the hboot, and have installed the fantastic looking runnymede 2.4 rom, but am getting heaps of force close errors. ive reflashed the rom a few times, and it runs fine for a few minutes, but after installing a few apps and whatnot then the errors begin. I have a feeling its related to XD2SDX not being set up correctly. I have a 16gb class 4 card in my phone atm, formatted with 1gb ext4 and the rest fat32 (with the fat32 partition being first). what makes me think this is initially the web browser works fine, but then once the errors start the browser wont even open, saying that i dont have enough free space remaining. If i go settings --> storage under internal available space it says 346mb used 666mb remaining. the only apps i have installed other than the included ones are handcent and mybackup (and let flash, youtube and tracks update).
I am about to try using a different 8gb sd card i have here out and see if that helps, as its a new trancend 16gb card, so may be dodgey. partitioned the card using gparted. first time i just used clockworkmods recovery sd card partition option, but noticed that it made an ext2 partition instead of ext4, was hoping that might be the problem but it seems it was not.
if i have missed any details please ask away, and thanks in advance for any help!
Click to expand...
Click to collapse
I do encountered the same probs and re-flashed it for about 3-4 times. Your advice is greatly appreciated.

Wipe cache + dalvik cache. Solves most FC problems.
Sent from dGB with Transparent XDA App

Ive done some more reading, and I think the problem lies with using XD2SDX and stock hboot. Apparently it works fine with cm7r2 hboot as it has more room for dalvik cache. that is why I am seeing plenty of room on the phone yet still getting out of space errors. To test this I reinstalled using app2sd+, and so far it seems to be working great.
if i get the motivation i might try flashing cm7r2 hboot and see if the errors remain.

hi , i can confirm that it works fine with cm7r2 hboot, it has problem with stock hboot, i was meaning to post this but i was abroad for the past 4 weeks, anyways i have been using runnymede 3.0.5 with cm7r2 hboot and it was flawless except one small bug i noticed was that when you are downloading something and the screen goes of(locks) you cant unlock it till the download is finished, anyone else had this problem or just me?

[Q] Ext4 problems!!! - GParted - please help

Hello everyone,
I have been trying to create an ext4 partition using GParted. I did all necessary steps - will quickly run thru, just so you know:
1. Burnt ISO and accessed thru boot menu (running XP/SP3, btw)
2. Deleted existing allocation.
3. Created new primary partition as FAT32
4. Allocated "free space following" as 1024
5. Specified the unallocated memory (1024) as ext4.
There was no error in the operation.
However... When I tried to load stuff to the SD card, Windows prompted me to format the card before using. It made no sense but I couldn't do anything. And by formatting it, I lost everything that GPL had done in the first place.
I went over the process again, to no avail.
Does anyone know where I've possibly gone wrong? Please help.
Thanks..!

Not really but I use a program called VM (virtual machine) instead of burning a CD as I had problems using CD. then when it finishes Windows refreshes & remounts SD generally without issue, but G-parted should still read it & ext4 should be ok as windows doesn't recognise it. Even so G-parted will still reformat it even if Windows done It's thing!
Sent from my HTC Desire using XDA App

I don't understand why this happens.
G-Parted doesn't report any error. In fact, just went through the process again.
I re-started GParted to ensure that the partition was successful.
Then, I booted back to windows and tried to load the backup to the SDcard and then, bang! "You need to format your SD card before proceeding".
Right click, properties shows RAW, 0 bytes, etc. It says I have to format again... Grrr....
WTH?

Triple checked - this time, before trying to format as Windows would suggest, I rebooted back to Gparted.
As one would expect - it did show FAT32 and ext4 partitions in the card (via card reader)...
But when I try to load stuff thru Windows, it doesn't allow!!!!!
Either I am doing something wrong without realising it. Or... This really is crazy.
My SD card is class 4, by the way. Dunno if tht helps!

It sounds like gparted only creates your partition table, not your file systems.
With gparted you create 2 partitions. One FAT and one EXT. Both are uninitialized. When you connect it to Windows, and it prompts you to format the DC card, it really want to just format the FAT partition. Check the size.
Hope this helps.
-Jobo

Check the size? As in?
My SD card is a class 4, 4GB.
G-Parted shows it perfectly. 2.69 (FAT32) plus 1.0 (940-ish MB, as ext-4)
But while running from my computer, I don't see any size description. I am forced to format it and voila, back to 3.69 (FAT32).
When I run G-Parted again, it prompts me to create the partition table (without which, it cannot proceed). So... It creates partition table (msdos, default) and I go through the process again, only for it end up as a vicious cycle! :/

Make sure that both partitions are made as primary

kartnite said:
Check the size? As in?
[...]
I am forced to format it and voila, back to 3.69 (FAT32).
Click to expand...
Click to collapse
That size.
This indicates that my first thought was wrong, and it does not prompt you to just format the FAT partition, but the entire device.
In gParted, try not only creating your partitions but also formatting them. Make sure you 'apply changes' before you quit.

daym0ss said:
Make sure that both partitions are made as primary
Click to expand...
Click to collapse
Yep. Did. No use. x(
touch of jobo said:
That size.
This indicates that my first thought was wrong, and it does not prompt you to just format the FAT partition, but the entire device.
In gParted, try not only creating your partitions but also formatting them. Make sure you 'apply changes' before you quit.
Click to expand...
Click to collapse
Yep... I did just that.
In fact, I even tried doing things one at a time (instead of queuing them up and executing them at one go).
Tried it on another memory card, too.
No avail. Am i hexed or what!?!?!?!

Problem solved, guys. Got so frustrated... I just did a system wipe. Wiped the card again. Started from scratch. Voila...
Thanks for the prompt responses!
Flashed the Runnymede ROM, too. Now my question is - how o I know if A2SD+ is actually functioning?
The storage settings say that 130-ish MB free. I downloaded Quick System Info Pro which says 547MB (out of 900-ish, as shown in G-Parted when I made the ext4 partition) A2SD storage free.
Am I missing something here?

It makes no sense (to me) that wiping your phone would make a difference.
Glad you got it worked out anyway, of course!
Just for my (and maybe others') understanding:
How did you have your sd card connected to your computer, when it didn't work?
In a card reader / in your phone via recovery / in your phone while booted / ...?
-Jobo

touch of jobo said:
It makes no sense (to me) that wiping your phone would make a difference.
Glad you got it worked out anyway, of course!
Just for my (and maybe others') understanding:
How did you have your sd card connected to your computer, when it didn't work?
In a card reader / in your phone via recovery / in your phone while booted / ...?
-Jobo
Click to expand...
Click to collapse
Sorry for the delayed reply, @Jobo.
At first, I was trying via the card reader. Didn't work. Tried it thru phone (in recovery mode). Faced the same problem. Never tried it with the phone booted.
Wiped everything and tried again with the phone in recovery. Worked.
But now... Although it shows up fine when inserted in to the PC (shows 2.69 instead of 3.69 and doesn't ask to be formatted), I get the odd prompt from my phone tht memory is reducing? So... Don't really understand if the A2SD+ is 'actually' operating. :/

Open terminal emulator on your phone, enter
Code:
su
ls -l /data
and post the output here.
Sent from dGB with Transparent XDA App

touch of jobo said:
It makes no sense (to me) that wiping your phone would make a difference.
Glad you got it worked out anyway, of course!
Click to expand...
Click to collapse
Agree +1
If you ever use the 4ext recovery to check, you will see the result after you wipe all, it's doesn't matter.
Anyway, congradulation for it worked~

MatDrOiD said:
Open terminal emulator on your phone, enter
Code:
su
ls -l /data
and post the output here.
Sent from dGB with Transparent XDA App
Click to expand...
Click to collapse
Ok... Downloaded the app. This is the output, @MatDroid
Code:
$ su
# ls -l /data
drwxrwxr-x 1 1000 1000 2048 Dec 1 12:05 anr
lrwxrwxrwx 1 0 0 11 Nov 28 22:38 app -> /sd-ext/app
lrwxrwxrwx 1 0 0 19 Nov 28 22:38 app-private -> /sd-ext/app-private
drwx------ 1 1000 1000 2048 Dec 1 17:59 backup
lrwxrwxrwx 1 0 0 20 Nov 29 03:11 dalvik-cache -> /sd-ext/dalvik-cache
drwxrwx--x 1 1000 1000 2048 Dec 2 17:00 data
drwxr-x--- 1 0 1007 2048 Nov 28 22:38 dontpanic
lrwxrwxrwx 1 0 0 11 Nov 28 22:38 drm -> /data/local
drwxrwx--x 1 1000 1000 2048 Nov 28 22:33 etc
drwxr-xr-x 15 0 0 0 Dec 1 17:59 htcfs
srwxrwxrwx 1 0 1002 2048 Dec 1 13:24 inc_data_path
drwxrwx--x 1 2000 2000 2048 Nov 28 22:38 local
drwxrwx--- 1 0 0 2048 Nov 28 22:38 lost+found
drwxrwx--t 1 1000 9998 2048 Dec 2 16:45 misc
drwx------ 1 0 0 2048 Dec 2 13:40 property
drwx------ 1 1000 1000 2048 Nov 28 22:39 secure
drwxrwxr-x 1 1000 1000 2048 Dec 2 17:01 system
drwxr-xr-x 1 1000 1000 2048 Nov 28 22:38 tombstones
drwxrwx--- 1 1000 1000 2048 Nov 28 22:38 wimax
#

A2SD+ is fully working. This is the important output:
lrwxrwxrwx 1 0 0 11 Nov 28 22:38 app -> /sd-ext/app
lrwxrwxrwx 1 0 0 19 Nov 28 22:38 app-private -> /sd-ext/app-private
drwx------ 1 1000 1000 2048 Dec 1 17:59 backup
lrwxrwxrwx 1 0 0 20 Nov 29 03:11 dalvik-cache -> /sd-ext/dalvik-cache​It means, app, app-private and dalvik-cache are symlinked/moved ("->") to sd-ext of partition of SD card. That's what the A2SD+ script should do, so it works.

xesor said:
Agree +1
If you ever use the 4ext recovery to check, you will see the result after you wipe all, it's doesn't matter.
Anyway, congradulation for it worked~
Click to expand...
Click to collapse
Thanks.
MatDrOiD said:
A2SD+ is fully working. This is the important output:
lrwxrwxrwx 1 0 0 11 Nov 28 22:38 app -> /sd-ext/app
lrwxrwxrwx 1 0 0 19 Nov 28 22:38 app-private -> /sd-ext/app-private
drwx------ 1 1000 1000 2048 Dec 1 17:59 backup
lrwxrwxrwx 1 0 0 20 Nov 29 03:11 dalvik-cache -> /sd-ext/dalvik-cache​
Click to expand...
Click to collapse
Hmmm, thanks for the reassurance, mate. Just read your explanation, too.
I don't think I need to click on "move to external storage" for apps any longer, yeah?

kartnite said:
Thanks.
Hmmm, doesn't make sense to me. But thanks for the reassurance, mate.
I don't think I need to click on "move to external storage" for apps any longer, yeah?
Click to expand...
Click to collapse
Added explanation to post.
No, you MUST NOT use "move to external storage" for apps. The reason for this is simple: Android can only differentiate between apps on FAT32 partition of SD card or internal memory (/data partition). A2SD+ moves the apps you install automatically to EXT partition SD card. But android "thinks" the app is still on internal /data partition (and some app-data is still there), so there is still the option to move to external storage, but this is the FAT32 partition.

MatDrOiD said:
Added explanation to post.
No, you MUST NOT use "move to external storage" for apps. The reason for this is simple: Android can only differentiate between apps on FAT32 partition of SD card or internal memory (/data partition). A2SD+ moves the apps you install automatically to EXT partition SD card. But android "thinks" the app is still on internal /data partition (and some app-data is still there), so there is still the option to move to external storage, but this is the FAT32 partition.
Click to expand...
Click to collapse
Ha ha! I edited my last post just before you mentioned it!
Great... Understood. Will move back all apps - even those which were, by default, installed to the SD.
But can you tell me what exactly happens if, despite the A2SD+, I choose the "move to SD" option? It is moved from ext to SD, then? Tht part is slightly confusing...

As I wrote, they were moved to FAT32 partition of SD card.
Sent from dGB with Transparent XDA App

[Q] What are the dkernel and dfs partitions?

Using the linux parted command that is available when one boots into TWRP recovery, one sees the list of partitions starting with:
Code:
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 11.0MB 10.5MB dkernel
4 11.0MB 212MB 201MB ext4 dfs
What are the functions of the dkernel and dfs partitions? Are their contents installed by Amazon and left unmodified by custom ROMs? Do they serve any useful function? Do they serve to give Amazon information that the user doesn't control, or allow Amazon to do anything to the device even after it has been modified by the user?

aarons510 said:
What are the functions of the dkernel and dfs partitions? Are their contents installed by Amazon and left unmodified by custom ROMs? Do they serve any useful function?
Click to expand...
Click to collapse
Diagnostics. It's pretty much a full stand-alone ROM. It's left unmodified by custom ROMs.
aarons510 said:
Do they serve to give Amazon information that the user doesn't control, or allow Amazon to do anything to the device even after it has been modified by the user?
Click to expand...
Click to collapse
No. It's probably best if you just leave them alone, unless you plan to get into editing, compiling and installing your own ROMs and -really- want the extra storage space.

Even though the space they occupy is not great (about 3% of the total on the device), what useful function do they serve? Is it possible for a user to, well, use them for anything? Are they used by other parts of the overall system?
The space could be used by just mounting it (probably just the larger one, partition 4) on a directory on the sdcard or userdata. Or one could perhaps move the cache (now on partition 11) to partition 4 (or 3 and 4 combined) and use the space freed to expand partition 10 or 12?
I realize that it's probably more work than it's worth to figure it out just for one's own KF, but if one could write simple instructions, or even a script, to do it for the masses, it might be worthwhile.

dkernel and dfs are debugging kernel and system filesystem, some how Amazon can boot that to do debug work on the kindle... No clue how to get the stock bootloader to start it, it's not useful to us anyway.
Unless it's used by the stock recovery to restore to the stock kernel and stock system, I saved a copy of mine, but I doubt it'll ever do back on.
I have my kindle partitioned like this right now:
Model: MMC MMC08G (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Code:
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 525kB 512B
4 525kB 525kB 512B
5 525kB 16.9MB 16.4MB recovery
6 16.9MB 16.9MB 512B
7 16.9MB 25.1MB 8191kB boot
8 25.1MB 25.1MB 512B
9 25.1MB 537MB 512MB ext4 system
10 537MB 1561MB 1024MB ext4 userdata
11 1561MB 1817MB 256MB ext4 cache
12 1817MB 2841MB 1024MB fat32 media msftres
13 2841MB 7818MB 4977MB ext4 linux
I have the unused partitions set to the smallest amount to maintain the original layout (so I can still use CM9 flashes with out having to mess around), I also changed the others a little (system went from 530 or something to 512MB, etc)...
Made media 1GB, the rest is my linux system, but rest of you could just put it on media or make userdata bigger.

seishuku said:
dkernel and dfs are debugging kernel and system filesystem, some how Amazon can boot that to do debug work on the kindle... No clue how to get the stock bootloader to start it, it's not useful to us anyway.
Click to expand...
Click to collapse
I did a bit of playing around with it myself before I saw your post. I mounted partition 4 (readonly, for safety) on /sdcard/dfs and got a good look at its contents.* It does look like a fairly complete UNIX/linux system. I can't imagine why Amazon would put it on Kindles that are sold to the public, rather on just the ones they use for development. Unless, as you speculate, it's used by the stock recovery to restore to the stock kernel and stock system. Otherwise, it seems like a big waste, considering the large number of these Kindles sold.
As for your re-partitioning of your Kindle, did you install anything other than linux after you re-partitioned, like a ROM, recovery, or bootloader? Or did you just move things around and resize them after they were installed?
BTW, what's the trick for being able to choose between booting into android and booting into (regular) linux? Could the same trick be used to allow choosing between two android ROMs at boot time? (I'm presuming you didn't write your own bootloader.)
* Added in edit: I posted a listing of the contents at
http://forum.xda-developers.com/showthread.php?t=1688601.

seishuku said:
dkernel and dfs are debugging kernel and system filesystem, some how Amazon can boot that to do debug work on the kindle... No clue how to get the stock bootloader to start it, it's not useful to us anyway.
Unless it's used by the stock recovery to restore to the stock kernel and stock system, I saved a copy of mine, but I doubt it'll ever do back on.
I have the unused partitions set to the smallest amount to maintain the original layout (so I can still use CM9 flashes with out having to mess around), I also changed the others a little (system went from 530 or something to 512MB, etc)...
Made media 1GB, the rest is my linux system, but rest of you could just put it on media or make userdata bigger.
Click to expand...
Click to collapse
Thanks for sharing your partition set up. It's very clever.

seishuku said:
dkernel and dfs are debugging kernel and system filesystem, some how Amazon can boot that to do debug work on the kindle... No clue how to get the stock bootloader to start it, it's not useful to us anyway.
Unless it's used by the stock recovery to restore to the stock kernel and stock system, I saved a copy of mine, but I doubt it'll ever do back on.
I have my kindle partitioned like this right now:
Model: MMC MMC08G (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Code:
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 525kB 512B
4 525kB 525kB 512B
5 525kB 16.9MB 16.4MB recovery
6 16.9MB 16.9MB 512B
7 16.9MB 25.1MB 8191kB boot
8 25.1MB 25.1MB 512B
9 25.1MB 537MB 512MB ext4 system
10 537MB 1561MB 1024MB ext4 userdata
11 1561MB 1817MB 256MB ext4 cache
12 1817MB 2841MB 1024MB fat32 media msftres
13 2841MB 7818MB 4977MB ext4 linux
I have the unused partitions set to the smallest amount to maintain the original layout (so I can still use CM9 flashes with out having to mess around), I also changed the others a little (system went from 530 or something to 512MB, etc)...
Made media 1GB, the rest is my linux system, but rest of you could just put it on media or make userdata bigger.
Click to expand...
Click to collapse
Seishuku: could you share the trick how you move the recovery partition to the new location please? As I understand parted run under adb shell while KF is in recovery mode. Therefore, if we remove recovery partition does it allow parted to do so (since TWRP is running from recovery partition)?
Thanks.

Once recovery is booted, it's in RAM, so nothing on the MMC is being actually used... Now, if you removed/moved it and rebooted, then yeah, it wouldn't work.
So no real "trick" is needed, just make the changes, reboot and reflash recovery via fastboot.
Also, until recently I was just booting the linux kernel by fastboot, but now I've made changes to FFF 1.4 to give an added boot option to load linux... Which also needs an added partition (I just resized cache to make the space).
Edit:
Oh, after working with the boot loader for a little bit, I see how dkernel is booted... It would seem that if the normal booting means fail (both boot and recovery) a number of times, it will automatically boot the alternative system (dkernel/dfs).
To what end? No clue, I didn't save my dkernel (probably no different than stock kindle 2.6.xx kernel), I have no interest in it. lol

Thanks! very helpful information.

seishuku said:
Edit:
Oh, after working with the boot loader for a little bit, I see how dkernel is booted... It would seem that if the normal booting means fail (both boot and recovery) a number of times, it will automatically boot the alternative system (dkernel/dfs).
To what end? No clue, I didn't save my dkernel (probably no different than stock kindle 2.6.xx kernel), I have no interest in it. lol
Click to expand...
Click to collapse
It would be interesting, to me, anyway, to be able to boot into it directly. It contains adbd, presumably an adb server daemon, and bash, so one could, presumably, run a shell, at least, using adb.

[Q] Total Space 10.36GB

While listening to Spotify on my stock N71000 phone (not rooted etc) it locked up. Now it locks up 2 to 5 times a day. I have also noticed My Total Storage Card Space is now 10.36GB. Have restored the phone and still only has the Total 10.36GB with 9.61 Available. My external 64GB card is fine. I have looked at the card on my windows machine with same results.
Any ides?

It is 10.36 from the start.
Try a factory reset.
Sent from my GT-N7100 using xda premium

You won't get full 16 gb from the internal storage..
Everyone has it between 11-10 gb..
Those 5-6 gb as far as I know, they are for system partitions..
Sent from my GT-N7100

yenkoeric said:
While listening to Spotify on my stock N71000 phone (not rooted etc) it locked up. Now it locks up 2 to 5 times a day. I have also noticed My Total Storage Card Space is now 10.36GB. Have restored the phone and still only has the Total 10.36GB with 9.61 Available. My external 64GB card is fine. I have looked at the card on my windows machine with same results.
Any ides?
Click to expand...
Click to collapse
The exact size for user accessible is 11.4GB
Disk /dev/block/mmcblk0: 15.8GB (total storage)
4194kB BOTA0
4194kB BOTA1
21.0MB ext4 EFS
4194kB m9kefs1
4194kB m9kefs2
4194kB m9kefs3
8389kB PARAM
8389kB BOOT
8389kB RECOVERY
92.3MB RADIO
4194kB TOMBSTONES
1434MB ext4 CACHE
2147MB ext4 SYSTEM
587MB ext4 HIDDEN
8389kB OTA
11.4GB ext4 USERDATA (storage left for user)

Unbrick our T989! (need Help with getting a DeBrick.img)

EDIT: we need a T989D user to help us! please if you stumble upon this please read and help us out!
it seems like samsung devices have a new method to unbrick when we get QHSUSB_DLOAD when we plug it into the computer.
http://forum.xda-developers.com/showthread.php?t=2439367 : T999 Galaxy s3 T-mobile
http://forum.xda-developers.com/showthread.php?t=2600869 : I9205 Galaxy mega 6.3
http://forum.xda-developers.com/show....php?t=2624203 : N9005 Galaxy note 3
and it seems like they use the same method but someone has made a debrick.img for their devices specifically, i would love to put up a thread for people for this so we can unbrick our s2's but i dont know how they get their .imgs, i heard that we need someone on a stock rooted rom to be able to make the .img so would anyone be able to show me how to make one of these because i own 3 t989s which i will put one of them to stock if someone can show me how to make the .img.

Trozzul said:
it seems like samsung devices have a new method to unbrick when we get QHSUSB_DLOAD when we plug it into the computer.
http://forum.xda-developers.com/showthread.php?t=2439367 : T999 Galaxy s3 T-mobile
http://forum.xda-developers.com/showthread.php?t=2600869 : I9205 Galaxy mega 6.3
http://forum.xda-developers.com/show....php?t=2624203 : N9005 Galaxy note 3
and it seems like they use the same method but someone has made a debrick.img for their devices specifically, i would love to put up a thread for people for this so we can unbrick our s2's but i dont know how they get their .imgs, i heard that we need someone on a stock rooted rom to be able to make the .img so would anyone be able to show me how to make one of these because i own 3 t989s which i will put one of them to stock if someone can show me how to make the .img.
Click to expand...
Click to collapse
You use clockwork mod recovery on your phone and go to "Install .zip from SD card" then you run the "T999_Partial_Sys_Dump_for_debrick.zip" and that gives you the debrick.img to put to your SD card. Get it from http://forum.xda-developers.com/showpost.php?p=45725480&postcount=45 and if you do, please post it! I need a t989 image.. And don't worry about it saying T999, you can rename it to anything. This is just the script that makes the image, its not hardware dependent.. Only the debrick image is that you make.

Lord Zog said:
You use clockwork mod recovery on your phone and "Install .zip from SD card" then you run the "T999_Partial_Sys_Dump_for_debrick.zip" and that gives you the debrick.img to put to your SD card. Get it from http://forum.xda-developers.com/showpost.php?p=45725480&postcount=45 and if you do, please post it! I need a t989 image.. And don't worry about it saying T999, you can rename it to anything. This is just the script that makes the image, its not hardware dependent.. Only the debrick image is that you make.
Click to expand...
Click to collapse
alright cool dude i have been told that this file makes the debrick.img i just didnt know if it would work with the s2 but it looks like other people clarified that i should be able to do that when i get home. i might run into a problem though, my S2 has a stuck power button and when i go into cwm it taps on random things and im afraid it will screw me and somehow brick it (i might just factory reset so there's nothing but it could still hit one of the wrong options) , i need to find a way to get CWM touch on it but i have made a thread and nobody has helped me D: do you think From rom manager i can hit the "Install rom from SD card" option and use it on the Debrick file?

alright made a debrick.img and tried the method for the s3 and it didnt work maybe i did it wrong, heres there .img (im not on a rooted stock, is that the reason why?) mediafires being dumb and couldnt upload there: http://d-h.st/KUD sorry about Anonymous uploader i couldn't find the registration page.

Trozzul said:
alright cool dude i have been told that this file makes the debrick.img i just didnt know if it would work with the s2 but it looks like other people clarified that i should be able to do that when i get home. i might run into a problem though, my S2 has a stuck power button and when i go into cwm it taps on random things and im afraid it will screw me and somehow brick it (i might just factory reset so there's nothing but it could still hit one of the wrong options) , i need to find a way to get CWM touch on it but i have made a thread and nobody has helped me D: do you think From rom manager i can hit the "Install rom from SD card" option and use it on the Debrick file?
Click to expand...
Click to collapse
I think in ROM manager it won't mount the partitions correctly, but I'll try it on this end with the file you posted.
Nope. Doesn't work. I'll look at the image in Linux and see whats in the partitions.
OK. So, it should look like this...
# parted /dev/sdb print
Model: Generic Ultra HS-SD/MMC (scsi)
Disk /dev/sdb: 16.0GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 4194kB 67.1MB 62.9MB modem
2 67.1MB 67.2MB 131kB sbl1
3 67.2MB 67.5MB 262kB sbl2
4 67.5MB 68.0MB 524kB sbl3
5 68.0MB 70.1MB 2097kB aboot
6 70.1MB 70.6MB 524kB rpm
7 70.6MB 81.1MB 10.5MB boot
8 81.1MB 81.7MB 524kB tz
9 81.7MB 82.2MB 524kB pad
10 82.2MB 92.7MB 10.5MB param
11 92.7MB 107MB 14.3MB ext4 efs
12 107MB 110MB 3146kB modemst1
13 110MB 113MB 3146kB modemst2
14 113MB 1686MB 1573MB ext4 system
15 1686MB 14.8GB 13.1GB userdata
16 14.8GB 14.8GB 8389kB persist
17 14.8GB 15.7GB 881MB cache
18 15.7GB 15.7GB 10.5MB recovery
19 15.7GB 15.7GB 10.5MB fota
20 15.7GB 15.7GB 6291kB backup
21 15.7GB 15.7GB 3146kB fsg
22 15.7GB 15.7GB 8192B ssd
23 15.7GB 15.8GB 5243kB grow
OUR's looks like this..
#parted /dev/sdd print
Model: Generic USB SD Reader (scsi)
Disk /dev/sdd: 32.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 512B 105MB 105MB primary
2 105MB 105MB 512kB primary boot
3 105MB 107MB 1536kB primary
4 107MB 15.8GB 15.7GB extended
5 109MB 110MB 512kB logical
6 113MB 115MB 2097kB logical
7 117MB 120MB 2560kB logical
8 122MB 132MB 10.5MB logical
9 134MB 135MB 512kB logical
10 138MB 139MB 512kB logical
11 143MB 143MB 512kB logical
12 147MB 157MB 10.5MB logical
13 159MB 262MB 103MB logical lba
14 264MB 267MB 3146kB logical
15 268MB 272MB 3146kB logical
16 273MB 276MB 3146kB logical
17 277MB 380MB 103MB logical
18 382MB 385MB 3146kB logical
19 386MB 389MB 3146kB logical
20 390MB 393MB 3146kB logical
21 394MB 405MB 10.5MB logical
22 407MB 417MB 10.5MB logical
23 419MB 430MB 10.5MB logical
24 432MB 1059MB 627MB logical
25 1061MB 3211MB 2150MB logical
26 3213MB 3530MB 317MB logical
27 3532MB 3667MB 135MB logical
28 3670MB 15.8GB 12.1GB logical
This looks more MS-DOS that Linux file system.. I made it in Windows using the app everyone refers to. I'll do it now in Linux.
update: Still shows what we got. Try to do it again but in CWM.

Lord Zog said:
I think in ROM manager it won't mount the partitions correctly, but I'll try it on this end with the file you posted.
Nope. Doesn't work. I'll look at the image in Linux and see whats in the partitions.
OK. So, it should look like this...
# parted /dev/sdb print
Model: Generic Ultra HS-SD/MMC (scsi)
Disk /dev/sdb: 16.0GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 4194kB 67.1MB 62.9MB modem
2 67.1MB 67.2MB 131kB sbl1
3 67.2MB 67.5MB 262kB sbl2
4 67.5MB 68.0MB 524kB sbl3
5 68.0MB 70.1MB 2097kB aboot
6 70.1MB 70.6MB 524kB rpm
7 70.6MB 81.1MB 10.5MB boot
8 81.1MB 81.7MB 524kB tz
9 81.7MB 82.2MB 524kB pad
10 82.2MB 92.7MB 10.5MB param
11 92.7MB 107MB 14.3MB ext4 efs
12 107MB 110MB 3146kB modemst1
13 110MB 113MB 3146kB modemst2
14 113MB 1686MB 1573MB ext4 system
15 1686MB 14.8GB 13.1GB userdata
16 14.8GB 14.8GB 8389kB persist
17 14.8GB 15.7GB 881MB cache
18 15.7GB 15.7GB 10.5MB recovery
19 15.7GB 15.7GB 10.5MB fota
20 15.7GB 15.7GB 6291kB backup
21 15.7GB 15.7GB 3146kB fsg
22 15.7GB 15.7GB 8192B ssd
23 15.7GB 15.8GB 5243kB grow
OUR's looks like this..
#parted /dev/sdd print
Model: Generic USB SD Reader (scsi)
Disk /dev/sdd: 32.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 512B 105MB 105MB primary
2 105MB 105MB 512kB primary boot
3 105MB 107MB 1536kB primary
4 107MB 15.8GB 15.7GB extended
5 109MB 110MB 512kB logical
6 113MB 115MB 2097kB logical
7 117MB 120MB 2560kB logical
8 122MB 132MB 10.5MB logical
9 134MB 135MB 512kB logical
10 138MB 139MB 512kB logical
11 143MB 143MB 512kB logical
12 147MB 157MB 10.5MB logical
13 159MB 262MB 103MB logical lba
14 264MB 267MB 3146kB logical
15 268MB 272MB 3146kB logical
16 273MB 276MB 3146kB logical
17 277MB 380MB 103MB logical
18 382MB 385MB 3146kB logical
19 386MB 389MB 3146kB logical
20 390MB 393MB 3146kB logical
21 394MB 405MB 10.5MB logical
22 407MB 417MB 10.5MB logical
23 419MB 430MB 10.5MB logical
24 432MB 1059MB 627MB logical
25 1061MB 3211MB 2150MB logical
26 3213MB 3530MB 317MB logical
27 3532MB 3667MB 135MB logical
28 3670MB 15.8GB 12.1GB logical
This looks more MS-DOS that Linux file system.. I made it in Windows using the app everyone refers to. I'll do it now in Linux.
update: Still shows what we got. Try to do it again but in CWM.
Click to expand...
Click to collapse
sooo what should i do then? should i go back to stock reroot it and redo the flashing?

Trozzul said:
sooo what should i do then? should i go back to stock reroot it and redo the flashing?
Click to expand...
Click to collapse
Yeah, but from clockwork mod recovery, and rooted stock, like UVLE1.

Lord Zog said:
Yeah, but from clockwork mod recovery, and rooted stock, like UVLE1.
Click to expand...
Click to collapse
Would this be what you want me to be on? http://forum.xda-developers.com/showthread.php?t=1668502 and that .img was from CWM

Trozzul said:
Would this be what you want me to be on? http://forum.xda-developers.com/showthread.php?t=1668502 and that .img was from CWM
Click to expand...
Click to collapse
No, use uvle1 ICS
http://stockroms.net/file/GalaxyS2/SGH-T989/ICS/SGH-T989_UVLE1_ICS.zip
scroll to the bottom and hit play and use the captcha and get stock ICS.
And that was from CWM? Were you rooted? The file structure looks a lot different.. Maybe the script is extracting from the wrong partition, but I thought the T989 and T989D used /dev/block/mmcblk0 also. Sadly, I don't have another T989(D) to check

Lord Zog said:
No, use uvle1 ICS
http://stockroms.net/file/GalaxyS2/SGH-T989/ICS/SGH-T989_UVLE1_ICS.zip
scroll to the bottom and hit play and use the captcha and get stock ICS.
And that was from CWM? Were you rooted? The file structure looks a lot different.. Maybe the script is extracting from the wrong partition, but I thought the T989 and T989D used /dev/block/mmcblk0 also. Sadly, I don't have another T989(D) to check
Click to expand...
Click to collapse
yeah CWM and rooted. and i heard that we shouldnt flash the stock UVLE1 ics stock because it was bricking other peoples phones?

Trozzul said:
yeah CWM and rooted. and i heard that we shouldnt flash the stock UVLE1 ics stock because it was bricking other peoples phones?
Click to expand...
Click to collapse
From what I understand, that's if you are using 4.3 or higher, but, we're not affected as we didn't get an official 4.3 for this device

Lord Zog said:
From what I understand, that's if you are using 4.3 or higher, but, we're not affected as we didn't get an official 4.3 for this device
Click to expand...
Click to collapse
yeah im on CM 10.2 still, i forgot i still needed to get back to stock, also so when i bricked my other T989 does it matter what rom it was on before? or if it was on stock? so i came from Aokp before, for us to unbrick it does the bricked phone needed to be on stock before? what do you think exactly this .img file does? im thinking it runs the drivers from the SD card?

Lord Zog said:
From what I understand, that's if you are using 4.3 or higher, but, we're not affected as we didn't get an official 4.3 for this device
Click to expand...
Click to collapse
alright flashed that file in odin, heres the Debrick.img From rooted stock also on CWM like last time

Trozzul said:
alright flashed that file in odin, heres the Debrick.img From rooted stock also on CWM like last time
Click to expand...
Click to collapse
hmm. Still doesn't work.. Without having a physical phone to play with, its hard to do it this way.
[email protected]:/home/zog/Downloads# dd if=debrick.img of=/dev/sdg
262144+0 records in
262144+0 records out
134217728 bytes (134 MB) copied, 35.458 s, 3.8 MB/s
[email protected]:/home/zog/Downloads# parted /dev/sdg print
Model: Generic USB SD Reader (scsi)
Disk /dev/sdg: 32.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 512B 105MB 105MB primary
2 105MB 105MB 512kB primary boot
3 105MB 107MB 1536kB primary
4 107MB 15.8GB 15.7GB extended
5 109MB 110MB 512kB logical
6 113MB 115MB 2097kB logical
7 117MB 120MB 2560kB logical
8 122MB 132MB 10.5MB logical
9 134MB 135MB 512kB logical
10 138MB 139MB 512kB logical
11 143MB 143MB 512kB logical
12 147MB 157MB 10.5MB logical
13 159MB 262MB 103MB logical lba
14 264MB 267MB 3146kB logical
15 268MB 272MB 3146kB logical
16 273MB 276MB 3146kB logical
17 277MB 380MB 103MB logical
18 382MB 385MB 3146kB logical
19 386MB 389MB 3146kB logical
20 390MB 393MB 3146kB logical
21 394MB 405MB 10.5MB logical
22 407MB 417MB 10.5MB logical
23 419MB 430MB 10.5MB logical
24 432MB 1059MB 627MB logical
25 1061MB 3211MB 2150MB logical
26 3213MB 3530MB 317MB logical
27 3532MB 3667MB 135MB logical
28 3670MB 15.8GB 12.1GB logical

Lord Zog said:
hmm. Still doesn't work.. Without having a physical phone to play with, its hard to do it this way.
[email protected]:/home/zog/Downloads# dd if=debrick.img of=/dev/sdg
262144+0 records in
262144+0 records out
134217728 bytes (134 MB) copied, 35.458 s, 3.8 MB/s
[email protected]:/home/zog/Downloads# parted /dev/sdg print
Model: Generic USB SD Reader (scsi)
Disk /dev/sdg: 32.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 512B 105MB 105MB primary
2 105MB 105MB 512kB primary boot
3 105MB 107MB 1536kB primary
4 107MB 15.8GB 15.7GB extended
5 109MB 110MB 512kB logical
6 113MB 115MB 2097kB logical
7 117MB 120MB 2560kB logical
8 122MB 132MB 10.5MB logical
9 134MB 135MB 512kB logical
10 138MB 139MB 512kB logical
11 143MB 143MB 512kB logical
12 147MB 157MB 10.5MB logical
13 159MB 262MB 103MB logical lba
14 264MB 267MB 3146kB logical
15 268MB 272MB 3146kB logical
16 273MB 276MB 3146kB logical
17 277MB 380MB 103MB logical
18 382MB 385MB 3146kB logical
19 386MB 389MB 3146kB logical
20 390MB 393MB 3146kB logical
21 394MB 405MB 10.5MB logical
22 407MB 417MB 10.5MB logical
23 419MB 430MB 10.5MB logical
24 432MB 1059MB 627MB logical
25 1061MB 3211MB 2150MB logical
26 3213MB 3530MB 317MB logical
27 3532MB 3667MB 135MB logical
28 3670MB 15.8GB 12.1GB logical
Click to expand...
Click to collapse
Well what else can I do?

Trozzul said:
Well what else can I do?
Click to expand...
Click to collapse
We need to figure out the partition structure and find the right one with the .PIT file, and try to create a proper 8660_msimage.mbn or debrick.img creation.

Oh yeah, try to install BusyBox while rooted, and then try it again. I'm still trying to find partition info. So far I have found aboot, amss, boot, cache, mdm, recovery, rpm, sbl2, sbl3, system, tomb, and tz. I'm missing a few and proper flags and such
Also, in play store, when you get BusyBox, also get Android terminal emulator. Then once those 2 things are installed, run BusyBox and use smart install. Once that's done, you can try to do into Android Terminal Emulator and type
su <enter> It'll ask for SuperUser access, allow it. then
busybox dd if=/dev/block/mmcblk0 of=/sdcard/debrick.img bs=1M count=128 <enter>
When I say <enter>, I mean press enter. Try that.

Okay. We're going a different route. Get this https://mega.co.nz/#!TEthlJYY!cq8cwm3c_ilvZVrGEa9TezmOpIkHbaTgYdctr3bxAl8 Its' from http://forum.xda-developers.com/showthread.php?t=2136738
Unzip it all to its own folder, say, Backup989
Run python-2.7.3, let it install to default folder
attach the phone
then run backup.bat
It will make another folder in this folder we're in called "Backup" Once this is done, you should have 8 or so files, compress them in WinZip or WinRAR and upload that.
Files in folder should be
aboot.mbn
pitfile.pit
partition0.bin
rpm.mbn
smd_hdr.mbn
sbl1.mbn
sbl2.mbn
sbl3.mbn
and maybe 1 more, compress them all into one file and upload to me.
DO NOT run the debrick file in that archive, that IS NOT for our phones and the sectors for writing are probably NOT the same as ours and will overwrite something else that could be important. (EFS/IMEI/ANYTHING!) Only run BACKUP.BAT

Got it. Made a debrick.img manually. Its not perfect and consists of a few messy hacks. I'll fix this up and send you one to try once I look at it and the partitioning in HS-USB 9008 and HS-USB-9006 state. This was a 9008 state, then it was switched to a 9006 state and had 7 partitions. I'll post more in a bit once I get this thing fully running.

Ok, I still need partition info. After flashing in Odin, it seems to not want to boot. I can get in and out of ODIN, but the partition info is bad. I can't enter recovery, nor boot past the boot logo, not the animation, just logo. SAMSUNG, and the one that says TMOBILE S2.. I still need you to do the backup to get proper .PIT file and partition0.bin to fix MBR and the PIT partition at b0p11. But send all the backup files it makes just incase one of mine is bad. Had to use another source for SBL1.MBN...
UPDATE: Ok. After messing more things and tinkering, I can boot. I can't go to recovery tho, but ODIN works and I want to make sure my partition isn't screwed up and that why I can't get recovery. But we got boot! I'm excited. This things been dead for 3 months, and never bothered to try till now.
We need a user with a T989D to do the same as the partition table IS different. Using a PIT from a 989 and ODIN Fail's on the modem/baseband MBN file from a T989D ROM, but using a T989 ROM flashes fine, but then doesn't boot. So, we need partition info from BOTH devices, PIT File, and partition0.mbn/.bin from a T989 and a T989D MBR, as well as the other files (sbl1-3, etc) Then we can properly make 2 debrick.img files, one for T989 and one for T989D as I am using a T989D but using modified SBL1-3 files and ABOOT to get this going.
As you can see from the screenshot, my build is T998DTLUMC4, but my baseband is T989UVMC6. One is telus, one is T-Mobile.