yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Q&A, Help & Troubleshooting] Samga:
Having read How to reconstruct a binary identical I9000XWJP6 kernel image, and more it seems to me (but I'm not an android developer) that with the available Samsung source code there are some strange issues, and as probably being a debug version, using it results in a different kernel from the one of the official firmware.

How do custom kernel developers handle this?

Is it possible and common to first create a binary identical kernel as a basis for a custom kernel?

Or is the kernel e.g. of project Voodoo worse than the original stock firmware kernel because of poor Samsung sources?

(I've already posted this question in the linked thread and in the Voodoo thread without any response. By creating a dedicated thread the topic can hopefully be handled better. Sorry for posting again ;))
[Galaxy S I9000 Q&A, Help & Troubleshooting] DamianGto:
Samsung do give out a a base for the kernel. That what we use.

Samsung then make different firmware on that base for different region. So the name is different. Like jpy. Js3 ... ...

It can be minor change in them, but it not much.

We often do alot of things that is better then stock. We also look on Linux and se if there is any new things we can use.

So dont worry. We are on top on most things...

**DamianGTO Steam kernel. 350MB Ram. 500HZ. Ext2 on all partitions. js3 base**
[XPERIA X10 Themes and Apps] thatsupnow:
Hey guys i was wondering if any of you tech savvy bros could do up a sweet james bond theme that will work with the freex10 beta 4. Might as well the guy uses a sony ericsson in the movie and his setup looked pretty sweet!!!
[Desire Q&A, Help & Troubleshooting] barryfell:
When trying to create an ext4 partition on the stock 8Gb SD card that I got with my Desire, I ended up 'bricking' it so now it's damaged and is no use any more.

I had a spare 4Gb one lying about (same make) and tried again, but suffered the same problem. Now that card is read only and I can't format it any more. Android just won't let me, and of course my PC doesn't see it as it's read only so again, 'bricked'. :(

Suffice to say now i'm furious as i've wasted 2 cards. I wasn't aware of different classes of SD cards before today but i'm guessing my problem stems from the fact that I was trying to add an ext4 partitions to class 2 cards? I wish the guides re partitioning would say that you need a better class of card to create ext3/ext4. (I was in the past able to make an ext2 ok on the first one)

Do I need to get a class 6 card to be able to use ext4?
[Desire Q&A, Help & Troubleshooting] TheGhost1233:
I don't think class and partition compatibility have anything to do with each other, the class is just a indication of the minimum write speed. Also i had no problem getting a ext3 partition on a class 2 sd card.

What program are you using to partition the cards?
[Desire Q&A, Help & Troubleshooting] barryfell:
Yeah? I had read that somewhere. I'm using Gparted Live CD.

I can't think why both cards failed the same way then.
[Desire Q&A, Help & Troubleshooting] madffrogs:
have a look at this link

http://download.cnet.com/VaioSoft-Recovery-Manager/3000-2094_4-10286449.html

manage to recover a bricked sd card with this. It might work for yours.
[Desire Q&A, Help & Troubleshooting] Meaple:
I used Gparted for my SD the other day and mysteriously, 4GB went missing. Luckily, Android reformatted it for me and I got my 4GB back :D
[Desire Q&A, Help & Troubleshooting] barryfell:
I'll try that. Thanks.
[Desire Q&A, Help & Troubleshooting] barryfell:
This is an old program. It doesn't appear to work under W7.

Not sure it would be any help anyway as Android doesn't even give me the choice to make the damaged cards visible to a PC.
[Desire Q&A, Help & Troubleshooting] TheGhost1233:
Did you try to mount them in recovery or just under android?

If only in android while booted, go in to recovery and mount it that way.
[Desire Q&A, Help & Troubleshooting] barryfell:
I don't seem to have an option to mount an SD card in recovery mode.

The only options I have are:

Reboot system now

Apply sdcard:update.zip (which doesn't work as the SD card is damaged so there is no update.zip accessible)

Wipe data/factory reset

Wipe cache partition

I think I did when I could use the update.zip but as I say, that's now not an option.

Any ideas?
[Desire Q&A, Help & Troubleshooting] buckshotjr:
Always be careful with ext4, it's known to kill the sd card's lifespan (so I've read from others, I've never tried it myself). I always use ext3 and it works fine.

P.S. Formatted with Rom Manager :/
[Desire Q&A, Help & Troubleshooting] crapula512:
ext4 will kill your card in 10 years maybe, so get that out of the equation.

boot a linux live cd if you dont have it installed (i.e. ubuntu)

open a terminal and then:

$sudo su (it will ask for your user password if you have one)

#dd if=/dev/zero of=/dev/sdX

but you have to replace that X by your phone's sd device it will probably be something like sdb or sdc, dont indicate the partition which would look like sdb1 or sdc1

once done, you hace to partition it again:

#cfdisk /dev/sdX

and then format those partition, like:

#mkfs -t ext4 /dev/sdX2 (now you have to indicate the partition)

good luck, and dont **** up your system.
[Desire Q&A, Help & Troubleshooting] barryfell:
Both my cards are already dead, so Ubuntu and Windows can't see them.
[Desire Q&A, Help & Troubleshooting] jiehao85:
What about your card reader? Maybe it is not the cards? I did my partitions using Ubuntu Live CD. My MicroSD card is a Sandisk 2GB card without any class specified.
[Desire Q&A, Help & Troubleshooting] th3:
Keep your cards and keep trying to format them after 2-3 days. Formatting in FAT32+BTRFS bricked two of mine a few weeks back but they were fine after a week and started getting recognized by then - not before though.

And yep, not to do with Class rating; I run Ext4 with a Class 2 and 4.

------------------------------

- Sent via HTC Desire -
[Desire Q&A, Help & Troubleshooting] gutsbn:
The card will be visible to Windows in computer management. Just delete the partition.

Bricked my arse
[Desire Q&A, Help & Troubleshooting] th3:
A corrupted filesystem or partition is very different to a corrupted card. You most likely have the former, not the latter.

Which Recovery and version are you using?

All Recoveries for a while allow you to mount the card via USB. The option is under "mounts and storage" in CWM Recovery, like: http://www.brutzelstube.de/wp-content/uploads/2010/09/ClockworkModRecovery.jpg

Format when it is mounted through this option via your PC.

------------------------------

- Sent via HTC Desire -
[Desire Q&A, Help & Troubleshooting] barryfell:
I don't have a card reader and it's cheaper to buy a new card than buy a card reader to maybe fix them.

I previously had an ext2 partition which I done via Clockwork recovery. However, when I tried to format the card and repartition it with an ext4 partition using Gparted Live CD I broke both the cards. At first they were just being reported as read only by Android but as I tried to fix them they became damaged so now I can't mount them.

I think the problem stems from me formatting while the cards were mounted, as mentioned earlier. My mistake there. I should have formatted them under Gparted.

Now they are damaged Gparted no longer sees them and while Windows disk management did see them for a while (when Android was reporting them as read only) now I can't see them I can't do anything to them.
[Desire Q&A, Help & Troubleshooting] barryfell:
Before I damaged it it was visible in Windows disk management, but there were no partition(s) and no ability to format. The disk was just grey, like the DVD drive..
[Desire Q&A, Help & Troubleshooting] barryfell:
I had the former at first, but further attempts to fix it ended with the latter.

I was using Clockwork, but I can no longer get in to it. As I say, all I can access are:

Reboot system now

Apply sdcard:update.zip

Wipe data/factory reset

Wipe cache partition

I used to go to 'Apply sdcard:update.zip' to get into Clockwork Recovery but as I say, this is no longer an option, as the SD card has been formatted and now damaged.

I would if I could get into Clockwork Recovery. I just don't see a way of mounting the card to do anything with it now it's damaged. (Unless I maybe bought a card reader)
[Desire Q&A, Help & Troubleshooting] barryfell:
Interesting. I'll maybe try that at some point but I have a new card on the way so i'll be making sure I format and partition it in Gparted and not make the mistake of formatting while mounted in Android.
[Desire Q&A, Help & Troubleshooting] th3:
That doesn't look damaged, just a corrupted filesystem. That's how Windows and the phone usually react to it. Damaging a card through simple formatting is really not possible. The NAND cells have to physically become corrupt to damage the card, and even then, a few cells will go bad at once, maximum. Not all of them.

------------------------------

- Sent via HTC Desire -
[Desire Q&A, Help & Troubleshooting] barryfell:
Indeed, which was why I could see it earlier, as at that point it was just corrupted.

However now I can't see it via any means on anything, apart from when inserted in my Desire and it tells me the cards is damaged.
[Desire Q&A, Help & Troubleshooting] th3:
As I've already mentioned, same happened with 2 of mine weeks back and yet there was no card damage. Search my posts and you'll see me mention it about a month back. If you understand NAND, you'll understand why formatting leading to damage is as likely as me flying around the globe every night before I go to bed :p

Yet again, if the card isn't picked up it still doesn't mean it's physically damaged/faulty. And 2 in a row physically damaged from just formatting -> not possible. Unless you used a very faulty card reader.

------------------------------

- Sent via HTC Desire -
[Desire Q&A, Help & Troubleshooting] barryfell:
I don't have a card reader.
[Desire Q&A, Help & Troubleshooting] th3:
And your CWM version is?

Even the CWM options you report seeing are borked i.e. a corrupt install, at best. I wouldn't waste another card until you get the CWM working as it should.

------------------------------

- Sent via HTC Desire -
[Desire Q&A, Help & Troubleshooting] barryfell:
OK I now have a new 8Gb class 6 card.

Before I mess this one up can I just confirm the following point, as i've just watched a 'how to' video that contradicts what some people are saying here:

What state should my phone be in before I partition with Gparted Live CD?

Should Android be booted, and in disk drive mode? (As per the video I just watched), or should I be in recovery mode?

Now I have a working SD card I can install Clockwork Recovery and reboot into that but is there a mode in that I should be in before proceeding to partition in Gparted? (Clockworks partition function only goes up to 512mb, in need at least 1024, in case you are wondering why I don't just partition with Clockwork)
[Desire Q&A, Help & Troubleshooting] barryfell:
I didn't have CWM installed, my phone was factory reset, and I couldn't re-install it until I had a working SD card. A catch22 situation.

I've installed it now though. v2.5.0.7
[Desire Q&A, Help & Troubleshooting] gosa:
First of all - please understand that I do not - in anyway say that what I'm about to suggest really applies to this problem. I can only say that my suggestion is valid, even though it might not apply here.

With that out of the way I have to ask the original poster:

Where did you get the memory cards that failed on you? Can you be 100% sure they're "original"?

The reason I'm asking is that it has been known to happen that some manufacturers of generic "no-name" memory cards make cheap and crappy low-sized cards, "fake" the size of them, brand them as Kingston, Sandisk or whatever other "real" brand and sell them for very good prices.

These memory cards look perfectly ok on the outside and also when you plug them in and "take info" on them, but after your first format - or when you try to put stuff on them that they should have the capacity for - you're f*cked.

Then again - I'm not saying this is the case here... but it is a valid point...

And by the way - I have to say I agree with what the people here (no matter if my theory above is valid in your case or not) are saying about wheter or not it's possible to bork a memory card physically by doing a bad format... I don't think that is possible
[Desire Q&A, Help & Troubleshooting] barryfell:
Both cards came with my last 2 phones. Both worked for years until last weekend when I tried to re-partition them.

I've given up on them now anyway as I have a new card.
[Desire Q&A, Help & Troubleshooting] th3:
Be in Recovery. Then partition the SD card via your PC (attach it via USB).

------------------------------

- Sent via HTC Desire -
[Desire Q&A, Help & Troubleshooting] barryfell:
OK thanks.

Damn that guide I watched that made me try and partition while the card was mounted in Android in disk drive mode! It's what has caused all my problems it seems.
[Desire Q&A, Help & Troubleshooting] crapula512:
im always partitioning my cards using fdisk(linux) or gparted while in android and have had no problems.
[Desire Q&A, Help & Troubleshooting] barryfell:
While in disk drive mode in Android?
[Upgrading, Modifying and Unlocking] ottorecker:
I just purchased a Motorola Defy in Thailand (there are not many of these here…Moto’s seem to be very rare here) and I have not been able to root this thing no matter what I have tried. None of the one-click solutions seem to work. I have been able to push the required files via adb to the phone, get into the shell and run the exploit.bin. I get back to the original directory but I the phone disconnects and when I run the adb devices command I get no devices attached. If I reboot the phone I can get it to show up on the adb devices list, but when I run the adb shell I only get a $ and not #. I have tried this many, many times with the same result. I have also re-installed the Moto usb drivers many times and does not seem to make a difference. I must be doing something wrong. This is a brand new phone in Thailand, and probably has only been available here very recently.

I really do not have any experience at any of this but I am trying to learn. I also really need this phone rooted because I cannot access any paid apps in the marketplace In Thailand, and getting some of these apps would make my life easier. I am confident I can get them if I could get root access (using MarketAccess). The reason I bought the Defy in Thailand and not another phone is it is compatible with my home country. Maybe I blew it…..

Any help or advice would be very much appreciated.
[Upgrading, Modifying and Unlocking] SmithEC:
I am brand new to all of this, and have no idea what I'm talking about.

A search turns up two guides on how to do this. One at a site called dkszone and one here. Simply by searching "root motorola defy". Dkszone credits xda with the guide. Their guide is a little different, though, in that they reference an ADB gui for Windows, which is what I would have to use. Both guides are worth reading. I can't link to them because I have not posted here enough.

One thing that does strike me is that you make a reference to getting back to the original directory and your phone disconnects. Both guides make a reference to having to reconnect. XDA in step 5 and dkszone in step 7.

Someone here knows the answer.

Haven't been to Thailand in a while. Lived on Soi Lang Suan in Bangkok for two years. '95 and '96 maybe. Is Shinawatra still in exile? I'm sure you must know that he essentially brought cellphone service to Thailand. In a big way, that's for sure. This long before he became the PM, or whatever they call it now.

.
[Upgrading, Modifying and Unlocking] ottorecker:
more specific info

I will try to get a little more specific…

I’ve used the guide posted on xda forums and I can push via adb the following files like this:

adb push Superuser.apk /sdcard/Superuser.apk

abd push su /sdcard/su

adb push busybox /sdcard/busybox

adb push exploit.bin /data/local/tmp/exploit.bin

Seems to work no problem…..

I then type the following commands

adb shell

cd data/local.tmp

chmod 0755 exploit.bin

./exploit.bin

The system chews on it a bit, shows a bunch of remarks, then $, then forked a bunch of childs (scary) and then displays the starting directory (C:\documents and settings\userblahblah).

At this point things go nowhere. There is a remark about restarting the adb server on the desktop and re-login. I guess I am not exactly sure what that means or how to do it. If it means unplugging the phone and plugging it back in I have done that. If it means rebooting the phone and/or rebooting my pc I have done that as well. If I type adb devices at the command prompt after running the exploit.bin) I get “list of devices attached” with nothing listed below. I can use kill-server and then again enter the adb devices command (adb starts) but the phone is still not recognized. I can check for hardware devices attached through device manager and the ADB interface does not show up (although it was there when I started this procedure) If I type adb shell at this point I get a device not found error. The only way I can get the phone to be recognized again is if I reboot the phone. When I do this the adb interface is listed in system hardware, I can run the adb devices command and the device shows up. When I run the adb shell command now I get a $....so no permissions, right? This has been a long, frustrating experience.

Does anyone have any idea that I am doing wrong or know of any way to fix this?

Any help or other ideas would be very much appreciated…..

BTW,

I’m pretty sure Shinawatra is still in exile…I think he has like 20 passports or something. Who knows where he is...
[Upgrading, Modifying and Unlocking] SmithEC:
I really don't know what to tell you. I really don't.

I would not be able to use that program you are talking about. I would have to use a one-click method. I know you said you have tried the one-click methods before.

I don't need this for my phone and it wouldn't work anyway, I suppose, but I put the one-click .apk on mine just for illustration purposes.

This on a phone with ASTRO file manager pro.

Downloaded one-click .apk from here onto my hard drive. That first post reads that the app is available on the Market. I couldn't find it.

Pic 1 - moved file onto my phone then removed phone from laptop

Hit the ASTRO icon on my phone and I get what you see in pic 2.

Hit sdcard and got pic 3.

Scrolled to bottom and hit the .apk and got pic 4.

Hit Open App Manager and got pic 5.

I can't continue from there because it's not made for my phone.

My intent is not to insult you. If you have done this and it doesn't work, then I am just at a loss. If the info is of no use to you, maybe someone will find it useful in the future. I suppose it's possible that this is all in the thread that I linked to. I can't take the time to read it.
[Upgrading, Modifying and Unlocking] ottorecker:
Thanks for the input and the concise instructions. I have actually tried running the z4root.apk file from the phone. It installs just fine. When I run the program (for those familiar with it) I choose permanent root (or temporary root, I have done both). There is a notification at the bottom of the program that is telling you what the program is doing at the time. It displays ‘Running exploit in order to gain root access’ (or something similar) and then ‘acquiring root shell’. The z4root program stays on the ‘acquiring root shell’ screen for about 10 seconds or so then the screen reverts back to the all applications screen. No confirmations or error messages…nothing. And the phone is definitely not rooted.

Going to Hong Kong for a day…wish I could use the app store for my wanted apps there….I think I'm going to have the same issue as Thailand (no paid app appstore access).

Still hoping for an answer….and I'm not talking about throwing my phone out the window….yet…
[Upgrading, Modifying and Unlocking] fromusofa:
Rooting Motorola Defy

Z4Root does the same thing on my Defy. I also can’t pass through ./exploit.bin either. After executing exploit.bin I get dropped to c:\...\... as expected but then I can’t even go back in adb shell as it gives the error: device offline…I can only get to adb shell after rebooting the phone, however it takes me back $ prompt instead of # prompt. So it seems like this exploit.bin is not capable of giving me # (Root) prompt and so I am unable to mount system partition with read and write access and so unable to execute the rest of the commands on the phone as well. Am I doing it wrong or missing something here? Thanks for the help.
[Upgrading, Modifying and Unlocking] Mcdomms:
The z4root worked fine till version 2.34.1. From 2.51 version on there is another utility superoneclick. You can find it in the defy section of the forum. Worked for me and a lot of others.
[Upgrading, Modifying and Unlocking] ottorecker:
Success!

I do not know why I did not find this tread before but I did get my Thailand Defy rooted using the info and file on this tread:

http://xdaforums.com/showthread.php?t=913709

I need to improve my thread searching skills....

The superonclick version that I had tried previously was different than the one posted on that thread and I did not need to use 'turn on turn off stuff' noted there........one click...done......as advertised.

Thanks for everyone's help.....you have saved a Thailand Defy from a 30 story dive out of the window:eek:..... (and saved my sanity).
[Upgrading, Modifying and Unlocking] fromusofa:
Success!

Ditto from an apartment on the 13th floor in Ottawa, Canada. :D
[Upgrading, Modifying and Unlocking] amadensor:
Rooting a Defy

I have one too. While I was on 2.1, I had to use an old version of Super One Click. The update finally came out for my phone, and moved it up to 2.2.2. The update killed my rooting, but the current Super One Click worked like a charm after the update. Mine was from the UAE, and I live in the USA, so some of the pre-installed apps did not apply to me, and were really annoying, trying to localize applications into languages I can't read or speak. Rooting let me kill off some pre-installs. The new version also seems to be a lot more battery gentle, although it really hit the battery hard the first day (I think it was just getting all of the cache and settings caught up using a lot of data connection.)
[Galaxy Tab Themes and Apps] Melmoth76:
I picked up the Tab yesterday after selling my Archos 70. To be honest the video processing onthe tab is poor. Speed wise iits great but the hardware decoder seems to not process the video correctly. This is apparent on 720p content, the image seems to be pixelated or downscaled very poorly, resulting in jagged image quality. It seems that lower resolution files such as 480p does not suffer from this problem. I have tried mp4 and mkv 720p files and the problem is still very noticable. After trying rockplayer xyplayer and a host of others i noticed that the image is far sharper under software decoding ( but too slow to be usable) , one hardware decoding is enabled the image becomes blocky.

To be honest the main reason for buying the tab was for the playback of 720p content on a good quality screen. ( archos 70 screen has poor contrast and viewing angles) , has anyone else noticed this poor hardware decoder issue? and is there any way around it? , I am running the latest firmware and feeling a bit dissapointed, my galaxy S has no such decoding issues.
[Galaxy Tab Themes and Apps] AlexTheStampede:
Poor? It plays perfectly my test file, a 1080p trailer for the last Indiana Jones... And that beast reaches a bitrate of even 50mbps!