yashsingh1/xdaforums huggingface dataset:
[Defy Android Development] ephumuris:
Here is a test SBF version of MIUI latest (27/5/11) with English patch applied and including Swype and full battery percentage display too. Replaced data icons with sense ones as the green ruins the whole look!

Please do a nandroid first as i'm not sure if this even works on other peoples Defy. I tested and it works on mine.

To install:

You need to be on Nordic rom or be using it as a base for your current rom such as CM7 :)

Install my sbf through Moto flasher. Let boot. Report.

Note: May not be full English on first boot. Go to settings and re-set English language, reboot into recovery and clear cache and dalvik cache it seemed to do the job for me.

DOWN!Download me now!
[Defy Android Development] vazzz:
Thanks, man :)
[Defy Android Development] ephumuris:
Remember this is a test please don't blame me if your wife leaves you.

Ephumuris. Defy CM7 by Quarx.
[Defy Android Development] joker20:
sounds not good. after flashing bootloader error . restart same error after moto logo.
[Defy Android Development] fantasy8:
Good Job.

Thx
[Defy Android Development] kirpeace:
is it working?
[Defy Android Development] Antszej:
Is there only english/chinese? Any other languages like Polish?

Sent from DEFY running Quarx's CM7
[Defy Android Development] AkkiandDefy:
Same

Swyped by my Defy using CM-7 beta 6 with the XDA premium App
[Defy Android Development] ephumuris:
Hmm seems to not work for others... I wonder what would need to be done differently.

Removed download link for now.

Ephumuris. Defy CM7 by Quarx.
[Defy Android Development] bihariel:
i think the problem is when we make a data factory reset from normal recovery which makes 2-nd init unusable. i am trying this baut for build spanish miui, and i think a method that would work is first install an original froyo->boot it completely->reboot to bootloader and flash the moded sbf. i will report back if works.
[Defy Android Development] samorgs:
I tried it, flashed over CM7 without wiping and it worked. Then tried a full wipe with stock recovery and it sticks at the M logo.

I was on nordic 3.4.2.177 base before I flashed. After wiping had to reflash full nordic and tried again, still stuck on Motorola logo.
[Defy Android Development] sunoldman:
I made a Custom sbf with CM7 nightly build before,

http://xdaforums.com/showpost.php?p=14199021&postcount=14

Came across the same problem, it seems that we should modify the dumped CG39 a bit.
[Defy Android Development] m11kkaa:
I think it would be greate&enough if we would have a SBF which only contains Custom Bootmenu so it's small and flashes very fast.

After flashing that CWM can be used to flash.
[Defy Android Development] bihariel:
This is what you are looking for. http://xdaforums.com/showthread.php?p=14223629#post14223629
[Defy Android Development] m11kkaa:
That Thread was created 2 minutes before my post :)

Thank you very much
[Defy Android Development] androidtester80:
I'm sorry if it's a dumb question, I'm new to this, what's the point of a sbf? Why not just a nandroid?
[Defy Android Development] nepotu:
It's quite useful to have a SBF. If something is going wrong, let's say you'll try to put one nandroid which is not successfully applied or you by mistake wipe your phone using stock recovery you'll have to flash fist a Froyo SBF and then you can install 2nd Init and apply the nandroid, while by having the CM7/MIUI SBF you'll have only to apply it and that's it.
[Defy Android Development] androidtester80:
So, basically , it's for the lazy ones :) instead of flashing nordic, root, install 2ndInit and Miui, you just flash this sbf. 5 minutes less and a chance of bricking the phone. I'm going for the long way.

We should focus on finding and reporting bugs on the basic Miui, this would really help make a better release.
[Defy Android Development] hailmary:
wife vs modding

u got me there.my wife

is starting to bothered by my modding schemes on my defy.

she said im so poor of me,if i get my defy brick she will buy me iphone4..

but i say no,buy me more defys.she sai:(d how many defys u want-2 more defys.

thats 3 total ^^ then she raised her brow & silently smiles.

maybe she think im going nuts.:D

little offtopic fun
[HD2 Android Q&A, Help & Troubleshooting and Genera] ksubedi:
I am currently developing a tool that helps repartitioning magldr, updating recovery, and more. I just finished writing code for a newer version with more features than the older one here -> http://xdaforums.com/showthread.php?t=1090783 . I am about to release it soon, but i want some people to test out my app before releasing. so if u are interested to help me, please mail me right now at cwm [at] wireshock.com and ill send you the files. i will add your names in the credits section of the thread. I need

someone using clk who has clockworkmod 3.1.0.1 or lower

someone using magldr who has clockworkmod 3.1.0.1 or lower

someone using magldr who has clockworkmod 3.1.0.1 or lower and a nandroid backup to test partitioning.

Thanks :)
[HD2 Android Q&A, Help & Troubleshooting and Genera] azer0:
Any chance of this corrupting nand?

If not, sign me in
[Eee Pad Transformer Q&A, Help & Troubleshooting] dicko99:
Just playing with the standard software now...

One little gotcha I encountered. I was running my wifi on channel 13 to avoid clashes with the neighbours but the transformer couldn't detect it.

Channel 13 is legal and valid here in the UK and I had told the Transformer that I am in the UK.

I changed to a lower channel number and everything connected fine.

Now waiting for the battery to exceed 50% so that I can apply the latest update.

R.
[Eee Pad Transformer Q&A, Help & Troubleshooting] xufuchang:
Congrats. welcome to the club :D
[Eee Pad Transformer Q&A, Help & Troubleshooting] wilbur-force:
im sure what it actually says is 50% charge or have the unit plugged in ;) who needs to wait :) enjoy !
[Eee Pad Transformer Q&A, Help & Troubleshooting] e^n:
I also got mine this morning, and while the tablet will power on and be perfectly usable, the batteries in either unit don't seem to be charging. My battery indicator is stuck at 44% and SystemPanel says the battery voltage is 7mV

I left it charging for some 5 hours or so, but it will not power on without the cord attached with either unit.

Any suggestions?
[Eee Pad Transformer Q&A, Help & Troubleshooting] wilbur-force:
hmmm. that does sound strange - i know they recommend an 8 hour charge first but im sure mine reported 100% after just a few hours. Are you charging both together ? have you tried charging individually ? either that or id be tempted to flash the update anyway as it may just be a software glitch .... ?
[Eee Pad Transformer Q&A, Help & Troubleshooting] e^n:
I have tried both, and even when it's just the tablet plugged directly into the charger it powers on just fine and is perfectly usable, but says it is not charging and that the battery is 44%

I don't really know what to do from here, I can't update as it needs either charging or more than 50%, and i can't get it to charge properly to bring it up to that level.

Even with the microSD card it doesn't want to work, and it obviously won't work connected just to USB.
[Eee Pad Transformer Q&A, Help & Troubleshooting] wilbur-force:
depending on how much you have tinkered with it it might be worth trying a hard reset .... ?
[Eee Pad Transformer Q&A, Help & Troubleshooting] e^n:
I've managed to update it to 8.2.3.13 with the microsd update (seperate icon in notifications) but still the same values. I've done a factory reset, is there a lower level reset I can do?
[Eee Pad Transformer Q&A, Help & Troubleshooting] wilbur-force:
no. the factory reset was what i was thinking of.

which value are you looking at for the battery percentage ? if its a market widget then some of those dont work properly ... my toolbar currently says 100% but the Asus widget is telling me 60% (The Asus widget is correct).
[Eee Pad Transformer Q&A, Help & Troubleshooting] e^n:
It's the default honeycomb indicator in the bottom right, and in settings->about

I don't have an asus widget, but I haven't re-signed on to the market. I also updated the firmware of the dock now, with no obvious difference. I'm quite colour blind but the light seems to be green.

I guess I have a defective tablet with a damaged battery. Very annoying since we have a bank holiday on Monday and so I won't be able to get a replacement until mid next week. I'll leave it on charge for some time to see what happens.
[Eee Pad Transformer Q&A, Help & Troubleshooting] wilbur-force:
you might find its the charger not the battery ........

have you got any other USB socket chargers you could try ? ie plug the ASUS cable into another charger block ?

I bleieve the ASUS charger pulls more power but ive just plugged my cable into an HTC charger and the TF showed as 'charging' .....
[Eee Pad Transformer Q&A, Help & Troubleshooting] UKseagull:
Are you 100% sure that the 2 parts of the wall charger are clipped together correctly? They are a very tight fit but will snap into place with enough force.
[Eee Pad Transformer Q&A, Help & Troubleshooting] e^n:
They're definitely clipped together correctly as the device powers up and runs just fine on it, and I think it has charged the dock. I was able to pull the power out and the tablet didn't immediately power off, but i'm leaving it charging for now.

Given the lack of people with a similar issue, I'm just going to contact ebuyer on tuesday and get it returned. What a huge pain in the butt.
[Eee Pad Transformer Q&A, Help & Troubleshooting] UKseagull:
One of the power supplies has a known fault and the part number is 0B-LF, the updated PSU has this part number 0B-1LF. Take a look at the sticker on yours and check if you have the dodgy version, the print is very small!

http://xdaforums.com/showthread.php?t=1081435
[Eee Pad Transformer Q&A, Help & Troubleshooting] e^n:
Unfortunately I have the OB-1LF adaptor. I've now confirmed that charging the dock works, the tablet won't boot on the dock unless the power is in, but i can pull it [the power] out immediately and the tablet is fully functional.

The battery display is now 43% after being charged for a while, with systempanel still reporting 7mV.

There has to be something wrong with the power management chip or firmware I guess. Filling in a return form right now.
[Eee Pad Transformer Q&A, Help & Troubleshooting] kingkay:
I've had the same problem with my second unit of the Transformer, luckily the shop i purchased it off from changed my adapter. Now charging works fine.

You should definitely return it.
[Eee Pad Transformer Q&A, Help & Troubleshooting] e^n:
The thing is, even when sitting on the dock it doesn't charge, on or off. That makes me think it's a problem with the unit. Either way it's a bank holiday over here on Monday so this won't get back to the suppliers until Wed at the earliest.

I've also noticed it seems to be developing some leakage along the bottom edge, which is never welcome.

Thanks for your help.
[Eee Pad Transformer Q&A, Help & Troubleshooting] kingkay:
Hmmm the dock itself may have no charge at all and it's difficult to tell if it has because there is no battery meter for it (yet). - You could check the LED indicator when it is plugged in though.

And if it is functional, it may be because it is using the tablet's battery.

Anyway I hope everything works out. It is such a shame that we experience such a hassle for a quality product!
[Eee Pad Transformer Q&A, Help & Troubleshooting] e^n:
Well I can't say for sure, but I believe the LED was green (I am very colourblind)

I've left it switched on on the dock for well over 12 hours now, mostly with the screen off, so I'll leave it until it absolutely discharges and maybe another 12 hours too, see if that resets anything.
[Eee Pad Transformer Q&A, Help & Troubleshooting] e^n:
FWIW the tablet has these messages repeated over and over in dmesg:

<4>[ 970.948181] warnning:charging current over sepc ret=0
<4>[ 970.948202] bq20z45_get_psp val->intval =Not charging ret =48c0 charging=0
<3>[ 970.949765] power_supply dock_battery: driver failed to report `capacity' property
<3>[ 970.949857] power_supply dock_battery: driver failed to report `status' property
<4>[ 970.952609] bq20z45_get_capacity val->intval=43 ret=45
<4>[ 970.953373] bq20z45_get_psp voltage_now =7586
<4>[ 970.954475] bq20z45_get_psp temp=288
<4>[ 970.955813] warnning:charging current over sepc ret=0
<4>[ 970.955825] bq20z45_get_psp val->intval =Not charging ret =48c0 charging=0

This is with the dock unplugged, it lasted basically 24 hours with regular use plugged into the dock, so it looks like the battery is damaged or the controller is or some similar issue.
[Android Software/Hacking General [Developers Only]] Jamin13:
Not sure if I'm about to get crucified for putting this here but I'm not sure where else to put it without an official board for the Echo.

I managed to get a system dump of the Kyocera Echo. Just posting it for anyone who wants it.
[Android Software/Hacking General [Developers Only]] Jamin13:
Kyocera Echo System Dump

First system dump I did was incomplete.

I redid it and got all the files now. :D

They are in the link now

http://www.mediafire.com/?yw43fp639voglx9
[Android Software/Hacking General [Developers Only]] cloud_9:
Is this the original / stock ROM for echo, bro?

If it is, how to use it?
[Android Software/Hacking General [Developers Only]] Jamin13:
It is the original stock ROM for the Echo but since there hasn't been any development (as far as I know), there may not be a way to use it for the phone.

Sent from my Kyocera Echo.
[Android Software/Hacking General [Developers Only]] Dreddge:
Not like it matters. There isnt **** out there for this phone, no recovery, no roms, nothing.

I just got mine today, and its on ebay.
[Android Software/Hacking General [Developers Only]] Jamin13:
I'd hope that wouldn't be the only reason you bought it.

Sent from my Kyocera Echo.
[Android Software/Hacking General [Developers Only]] Dreddge:
No, but I like to customize my phone. I enjoy a good ROM.

Stock Froyo is ****.
[Android Software/Hacking General [Developers Only]] Jamin13:
I know what you mean.

I'm slightly holding out on the fact that something could be in development but even if there isn't, I like the phone. :D
[Android Software/Hacking General [Developers Only]] cloud_9:
I already downloaded bro,

how to use it? is there any download mode in Echo??
[Android Software/Hacking General [Developers Only]] Mattix724:
That's what we said about the Kyocera ZIO M6000... we may not have Rom Manager support but we do have a recovery image of CWM that works via fastboot and USB.

Don't give up just because there is nothing as far as development right now... if we gave up we would've never got OpenZio rom based on stock and definitely no OC kernel.

If you really want more from your device, read some threads here on XDA and Google how to build a custom rom.

EDIT: You'll need a recovery image, I would try to use fastboot with our recovery image, do not flash it, if it works then your one step closer to gingerbread.
[Android Software/Hacking General [Developers Only]] Jamin13:
Why use fastboot?
[Android Software/Hacking General [Developers Only]] Mattix724:
To try booting our CWM recovery image until you can get proper CWM support.

Check our section of the forums it should be stickied under Development.

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

Boot your Echo into fastboot and try this...

"fastboot boot recovery.img"

You'll probably want to change whatever our recovery is called to just recovery to make it easier to type in the command prompt. You will need to have the SDK and JDK installed along with your Echo drivers. Kyocera has released the Echo development kit which has your source code that you will need when it comes time to building a custom kernel and overclocking.
[Android Software/Hacking General [Developers Only]] Jamin13:
What could happen if that recovery doesn't work?
[Android Software/Hacking General [Developers Only]] Mattix724:
Nothing will happen if the recovery image doesn't work, just as long as you do not flash the image to your phone's stock recovery.

You can safely try to boot the image from the fastboot screen by simply typing

"fastboot boot recovery.img"

If the image works you will be able to use CWM but you would have to use fastboot every time you want to backup your current rom or flash a new rom. Obviously you always want to backup first before attempting any modifications to the rom. Once you have a backup you can attempt to build CM7 from the Echo source code.
[Android Software/Hacking General [Developers Only]] Jamin13:
Alright, thanks for the info.

I'll check it out and post back if I run into a problem or it works. :p
[Android Software/Hacking General [Developers Only]] Mattix724:
Alright, if it doesn't work you can probably decompile our recovery and a copy of your recovery and build one that will work on your device, man I'm talking some serious Linux work....

Damn... I need my computer back...
[Android Software/Hacking General [Developers Only]] Jamin13:
Ahah, I just can't seem to get my recovery from my phone. Know what commands I could run to do that?

I'm not sure there is a recovery though, it's just the Android image with no options.
[Android Software/Hacking General [Developers Only]] Mattix724:
Okay, in fastboot does it show the partitions, does it have a number before the name of the partition?

I.E:

01 boot

02 recovery

03 system

04 data

05 cache

When using adb shell with root you will want to remember which number recovery was. Then use the cat command on the mtd# of your recovery image.

I.E:

$su

#cat /dev/mtd/mtd2 > /sdcard/recovery.img

Your pulled recovery image will now be in the root of your sdcard.
[Android Software/Hacking General [Developers Only]] Jamin13:
I read those in some file in my phone. I'll check them again before I try it.
[Android Software/Hacking General [Developers Only]] Mattix724:
It should be on the fastboot screen, you can start fastboot from a powered off state with a button combination.

Our fastboot on the Zio is to hold both send and power until it turns on with fastboot.
[Android Software/Hacking General [Developers Only]] Jamin13:
Now that's where a problem may lie.

There's only three buttons: Power, Volume Up, and Volume Down.

Power + Volume Down = Recovery Mode

Power + Volume Up = Download Mode (Tried using ADB and just the phone so I know that)

Unless I'm missing a button, those are the only modes we have.
[Android Software/Hacking General [Developers Only]] Mattix724:
There is no camera button or call button? Try holding all three together.
[Android Software/Hacking General [Developers Only]] Jamin13:
That's peculiar...The screens are off but the green LED is on...
[Android Software/Hacking General [Developers Only]] Mattix724:
I can't find anything about fastboot for the Echo...

Looks like Kyocera did it again, yet another slapped together hack and smash phone. They can't do anything the easy way.

Do you know if the Echo has a locked boot loader or S-on?

You will probably have to do some digging to find out which partition is the recovery so you can copy it and try to build CWM using stock recovery as a starting point then try to flash it to the same partition you started with and pray the button combo for recovery will work with the new recovery.

We don't even have a button combo for Recovery that is easy to access. Gosh darn you Kyocera!
[Android Software/Hacking General [Developers Only]] Jamin13:
It's a nice phone, just not dev friendly. XD

Let's find that partition...
[Android Software/Hacking General [Developers Only]] Jamin13:
Took a look in the mtd file in the /proc

dev: size erasesize name mtd0:

00600000 00040000 "boot" mtd1:

0e600000 00040000 "system" mtd2:

01900000 00040000 "cache" mtd3:

02780000 00040000 "fota" mtd4:

00100000 00040000 "pltable" mtd5:

00200000 00040000 "splash" mtd6:

00500000 00040000 "recovery" mtd7:

21200000 00040000 "userdatd" mtd8:

07f80000 00040000 "delta

So it should be mtd 1 and mtd 7.
[Android Software/Hacking General [Developers Only]] Mattix724:
That's what you need. Now to compile a working CWM recovery image. Keep a copy of the stock recovery so you can flash it back if needed. Now, how can you safety test a compiled recovery image without flashing yet?
[Android Software/Hacking General [Developers Only]] Jamin13:
No clue. :/

The commands to get the recovery partition are Linux commands right?
[Android Software/Hacking General [Developers Only]] Mattix724:
You can run the cat command from terminal emulator on your phone to copy your recovery partition.

cat /dev/mtd/mtd7 > /sdcard/recovery.img
[Android Software/Hacking General [Developers Only]] Jamin13:
Alright that's what I was gonna do. I'll check the next time I boot into Ubuntu.

Any precautions or warnings?
[Android Software/Hacking General [Developers Only]] Jamin13:
I got the(those) partition(s) now.

So now I need to find a guide on porting it...
[Android Software/Hacking General [Developers Only]] Mattix724:
Now that you have your recovery.img extracted try to compile a CWM image.
[Android Software/Hacking General [Developers Only]] Mattix724:
Any luck getting a recovery working yet?
[Android Software/Hacking General [Developers Only]] Jamin13:
Not yet. I've haven't started it yet because I'm trying to find a decent guide to do it.
[Android Software/Hacking General [Developers Only]] Mattix724:
http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html

Check that out.
[Android Software/Hacking General [Developers Only]] Jamin13:
Is the recovery partition what you get through the dump_image command?
[Android Software/Hacking General [Developers Only]] Mattix724:
You've already got your recovery from using cat. This guide does use alot of fastboot for testing the image and dumping and flashing the image.

You just need to get the source for ClockworkMod Recovery and build off of your stock recovery. Although I have no clue how you can test the image without fastboot. I guess you can always adb push the image from where you extracted it, which would be time consuming.
[Android Software/Hacking General [Developers Only]] Mattix724:
Oops, double post
[Android Software/Hacking General [Developers Only]] Jamin13:
Yeah, the testing might be the hardest part besides the actual port. It could be a lot of hard work just to brick my phone. :p
[Android Software/Hacking General [Developers Only]] Mattix724:
That's what the recovery you pulled is for... just do not touch the other partitions yet!
[Android Software/Hacking General [Developers Only]] Jamin13:
Ahah, I wasn't planning on since I have no clue what they could change.
[Android Software/Hacking General [Developers Only]] :
Jamin13,

I've been watching this thread. I don't know much about ROM development, but I know how to flash ROM's and used Clockwork recovery on my old Hero. I'm will to help test things when you get to that point. Since my Echo is my primary phone I many not always be available, but I will do what I can.

J
[Android Software/Hacking General [Developers Only]] Jamin13:
Ran into a snag, when trying to unpack the recovery.img, the files are all empty files.
[Android Software/Hacking General [Developers Only]] Mattix724:
Which recovery.img? OpenZio or your stock extracted image?
[Android Software/Hacking General [Developers Only]] Jamin13:
The stock extracted image.
[Android Software/Hacking General [Developers Only]] Mattix724:
How did you unpack the image?
[Android Software/Hacking General [Developers Only]] Jamin13:
I tried to use the command in Koush's guide: build/tools/device/mkvendor.sh device_manufacturer_name device_name /your/path/to/the/boot.img
[Android Software/Hacking General [Developers Only]] Jamin13:
Also, I actually was told that there is no actual recovery on the phone so if you do have a problem, you have to go back to Sprint to get it fixed. :X
[Android Software/Hacking General [Developers Only]] Mattix724:
Sprint always does funny things
[Android Software/Hacking General [Developers Only]] Jamin13:
I still can't figure out why it won't work...