yashsingh1/xdaforums huggingface dataset:
[Kyocera Zio M6000] wwwilly1986:
The home button unfortunately is not a physical button but a software-dependent touch button. It is useless unless the OS is loaded. I don't know why ADB won't see my phone when FastBoot will. Is there any command for FastBoot that will reboot it into recovery mode? I got your .img flashed just trying to get this thing into recovery mode to test it.
[Kyocera Zio M6000] hotaru:
i don't think there's a command to do it from fastboot... but on a lot of phones there's a way to get from bootloader mode to recovery using the phone's hardware buttons... if you can't find a way to do that, try booting while holding one of the other physical buttons.
[Kyocera Zio M6000] jcaf77:
i dont know if this will help you but just in case... hold volume up and down and then power... this will take to to usb download mode.... (obviously the phone has to be off before you do that key sequence)
[Kyocera Zio M6000] wwwilly1986:
Yes this will bring the phone into "Modem Download Mode"
[Kyocera Zio M6000] gregnotcraig:
hold down power for a count of 3 then hold the green power button. or is that fastboot? not near my phone at the moment...
[Kyocera Zio M6000] wwwilly1986:
That is Fastboot
[Kyocera Zio M6000] wwwilly1986:
Would anyone here be able to get me a full ROM dump of the stock 1.6 Cricket ROM please?!? I desperately need my phone back :-)
[Kyocera Zio M6000] phazei:
Try searching the forums, I posted this:

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

About a week ago. Everything you need.
[Kyocera Zio M6000] phazei:
I talked about that on page 29 of this thread.

It can't be done because the Android 1.6 - Donut was removed from the GIT repository. So it can't be compiled for the Cricket Zio. But one from the Sprint Zio should be no problem.

I'd also posted this:

http://androidforums.com/kyocera-zio/172688-just-picked-up.html#post1780268

BTW, does the Sprint boot.img have a 4K header? And what's it's base address?
[Kyocera Zio M6000] hotaru:
building clockwork recovery only uses the boot image, so it should work fine with donut.

i don't know, i haven't looked at it much, but the tools for unpacking and repacking boot images didn't say anything about anything being unusual about it... the boot.img is in the dump i posted earlier in this thread (http://ig.gl/zio.zip).

i tried installing the recovery on my brother's zio, but it apparently replaces the recovery on reboot, even tho there is no /system/recovery.img or /system/recovery-from-boot.b.
[Kyocera Zio M6000] wwwilly1986:
All of my partitions are blank, so it will not boot up from just the boot.img will it? All of these partitions are blank:

'fota_amss'

'boot'

'system'

'flex'

'recovery'

'userdata'

'fota_boot"

'cache'

'misc'
[Kyocera Zio M6000] wwwilly1986:
Never mind guys, got it back up and running. Now to get this 2.1 ported over...
[Kyocera Zio M6000] hotaru:
no that you're back up and running, i'd recommend trying to get a recovery working that will let you do nandroid backups before trying to port 2.1... it makes recovering if you screw up the system or boot partition a lot easier.

putting http://ig.gl/zio/clockwork-recovery-20101031.img on your sd card and then doing this might get you a working recovery:

# mount -o remount,rw /dev/mtdblock2 /system
# rm -r /system/*recovery*
# rm -r /cache/recovery/*
# flash_image recovery /sdcard/clockwork-recovery-20101031.img
# reboot recovery

i'm pretty sure the sprint zio doesn't replace the recovery on reboot, and it just has some files in /cache/recovery/ that tell the recovery do a data wipe instead of running normally. i could check this if i had a sprint zio here, but my brother has gone back to his place so i won't be able to test on it for a while. i'm guessing the cricket zio probably does the same thing, and if it does, there won't be anything for that first "rm -r" line to do... i just included it in case the cricket zio actually does replace the recovery image on reboot.

there shouldn't be any danger in doing this as long as your normal boot and system are working.
[Kyocera Zio M6000] Flare106:
Im not sure if im posting in the right area, i appologize beforehand if so. I have a question and was hoping someone could help me figure this out! When ever i go to select a ringtone im getting a force close message for process com.android.settings im guessing a file may be corrupted?? Any help is much appreciated!
[Kyocera Zio M6000] zyrtek69:
Good to hear.. you and hotaru are our best hope right now good work guys! Godspeed
[Kyocera Zio M6000] phazei:
No, this isn't the right place, start your own thread. That is way off topic from this thread.
[Kyocera Zio M6000] aj203355:
About 2 weeks ago my phone went to an updating to 2.1 screen. It never went through completely but it looked like an OTA update. Never saw it again. Still waiting on this update. I have zio on cricket BTW.
[Kyocera Zio M6000] rudebeats:
what!? huh??
[Kyocera Zio M6000] phazei:
Well, I just attempted to use fastboot to boot of the sprint kernel. I extracted it and checked the pieces, all good.

Attempted to fastboot with default page size, said invalid image. Seems the Zio has a 4K page rather than the standard 2K. Booted with these options:

fastboot -b 400000 -n 4096 boot sprintboot.img-zImage sprintboot.img-ramdisk.gz

And it said "booting... OKAY", but on the phone it just said "booting linux..." and didn't change from that at all...

I also tried it without the ram disk, same thing. Perhaps I'll try it with the recovery ram disk next, after backing up.
[Kyocera Zio M6000] phazei:
The Cricket Zio doesn't actually have any recovery image file that I could find. I searched the whole thing and found nothing.
[Kyocera Zio M6000] phazei:
I just flashed the stock boot.img the I pulled from the phone, back on to the phone, to test it.

Well, "fastboot -b 400000 -n 4096 flash boot boot.img" didn't work, but

"fastboot -b 400000 -n 4096 flash:raw boot boot.img-zImage boot.img-ramdisk" did work.

The phone works fine, but there's a tiny problem, for some reason the "Kyocera" boot image and "Cricket" loading screen are both gone. Screen is just dark until the OS loads.

I thought it just wasn't taking the ramdisk file, so I tried flashing it without the ram disk, then it didn't boot. Screen backlight turned on dimly and then turned off. Did that a few times. Went back into fastboot and flashed again with the ramdisk. It boots again, and now I have the Cricket logo, but still no Kyocera logo.
[Kyocera Zio M6000] killa619:
So how does the 2.1 run??
[Kyocera Zio M6000] hotaru:
i wasn't able to find any recovery image on my brother's sprint zio either, but after he left i was digging through the system image (for some reason neither unyaffs nor unyaffs2 will extract it for me), so i was using less and searching for "recovery" in system.img, and found the string "/cache/recovery/command", so there's probably either a file there or something somewhere that puts that file there before rebooting on the sprint zio. i'd think the cricket zio probably does the same thing.
[Kyocera Zio M6000] topherdownfrown:
So you successfully got2.1?
[Kyocera Zio M6000] killa619:
No he did not. I misunderstood the post.he just put the sprint 2.1 kernel on his zio.
[Kyocera Zio M6000] phazei:
Apparently CyanogenMod Donut does exist.

http://xdaforums.com/showpost.php?p=8979713&postcount=14467

So I'll be taking a shot at that soon.
[Kyocera Zio M6000] killa619:
Is this a rom that can be used with the zio?....Sorry im a newbie :-)
[Kyocera Zio M6000] phazei:
It is a ROM, it can't be used with the Zio without a lot of work.
[Kyocera Zio M6000] killa619:
You ment to say can right?
[Kyocera Zio M6000] killa619:
So if you can...what exactly has to be done in order for it to work?
[Kyocera Zio M6000] phazei:
No, I meant to say exactly what I said. It can't be used without a lot of work. I don't know what work that is. I'm attempting to figure it out. But there are issues with the CyanogenMOD Android 1.6 Donut source files, the repo is ****ed. Tried some new stuff today, still nogo. I can't even get the Sprint to boot, so currently we're all SOL unless someone who's more knowledgeable than me gives us a hand. And believe me, it doesn't take much to be more knowledgeable that me at the moment.
[Kyocera Zio M6000] s23bog:
Leak?

Maybe we can get a Cricket employee to leak a beta or alpha of the new rom. We could probably help them, and for sure it would help us.
[Kyocera Zio M6000] Spz0:
From my limited knowledge of cross-compiling for other devices and other distros of nix [and this may be way off, Im use to compiling with openembedded], it needs to be compiled from source. All files and dependencies need to be from the 1.6 repo, and for ARMv6 architecture.

If the official repo is messed up, then an alt. repository is needed to have a successful compile for our device. Then it needs to be tested, and necessary modifications/patches made to the build for optimal compatibility.
[Kyocera Zio M6000] hotaru:
why do you want 1.6? clockwork recovery doesn't depend on any particular android version, and once that's working, it'd be a lot easier to port the sprint 2.1. if you're wanting to build a full cyanogenmod rom, it'd be just as easy to do 2.2 as it would be to do 1.6.

i haven't gotten any reports from anyone on whether they've tried to get the build of clockwork recovery i posted to work...
[Kyocera Zio M6000] Spz0:
I've tried in adb (running a shell on the phone) and get a "Mount: Operation not permitted" return.

If I run su prefix, I get a permission denied return on the mount command.
[Kyocera Zio M6000] hotaru:
your phone needs to be roooted. if it is and you have a "$" prompt instead of a "#" one when you use adb shell, then you should type "su" and approve the request for root permission that pops up on your phone. once you have a "#" prompt, the mount command should work.
[Kyocera Zio M6000] Spz0:
K I'll try that and report back
[Kyocera Zio M6000] Spz0:
This is my result

# mount -o remount,rw /dev/mtdblock2 /system
mount -o remount,rw /dev/mtdblock2 /system
# rm -r /system/*recovery*
rm -r /system/*recovery*
rm failed for /system/*recovery*, No such file or directory
# rm -r /cache/recovery/*
rm -r /cache/recovery/*
rm failed for /cache/recovery/*, No such file or directory
# flash_image recovery /sdcard/clockwork-recovery-20101031.img
flash_image recovery /sdcard/clockwork-recovery-20101031.img
flash_image: not found
#

flash_image: not found.
[Kyocera Zio M6000] hotaru:
ok.the sprint zio has flash_image, but apparently the cricket zio doesn't.

get it from http://koush.tandtgaming.com/test/, put it in /system/bin and do

chmod +x /system/bin/flash_image

there's still a pretty good chance it could just do a data wipe instead of booting into recovery. if it does, it'd be helpful if you can do tar -czf /sdcard/system.tgz /system and send the system.tgz file it creates to me (hotaru@thinkindifferent.net). or if you want to play it safe, do that first and let me see if i can track down which file tells the recovery to do a data wipe.
[Kyocera Zio M6000] phazei:
Well, my phone is hosed at the moment.

I tried to flash the system.img that I pulled from it. Didn't take, but did break what was there.

I compiled unyaffs but that gave a segmentation fault on extracting. I downloaded that dump that someone uploaded around page 7. It was just the system files extracted. Used mkyaffs2image to convert it to a system file. It took, but wouldn't boot, just kept booting with a blank screen, vibrating, then rebooting into recovery where it formated data and cache, then rebooted and started over.

I think it's an issue with the permissions. If someone can actually run mkyaffs2image from their phone and create the system.img it would probably work.

http://jiggawatt.org/badc0de/android/mkfs.yaffs2.arm.tar.gz

Kind of shows how to use it in the middle of this section:

http://jiggawatt.org/badc0de/android/index.html#dynamic

I could really use this for the Cricket 1.6 Zio. Of course if someone can also provide it for the Sprint one, that'd be cool to.

Currently I can't get to adb shell on my phone at all. It says "sh" is missing. Fastboot works fine, so I've been trying things with that too. Since I was having issues with the yaffs2 images, I decided to try making an update.zip. I got the whole thing setup, modified AnyKernel as a start, but then I tried to use it with fast boot and it gave errors about missing android-info.txt and android-product.txt. Apparently the update.zip only works with the recovery menu which our phone seems to be missing, or lacking a way to enter. Sigh.
[Kyocera Zio M6000] Spz0:
Alright, I can certainly make a tarball and send ur way.

Why don't u hop onto #openzio on freenode. A little easier to chat.
[Kyocera Zio M6000] Spz0:
Oh, theres no tar program on the phone, so no tarballs as of yet.

*edit: Also no cp command. I tried adb pull with some success, although it skipped a bunch of special files on pull.
[Kyocera Zio M6000] hotaru:
ok, after some trial and error with Spz0 and phazei overy irc, we managed to get this clockwork recovery to boot on phazei's cricket zio!
[Kyocera Zio M6000] killa619:
Sweet! You guys rock!so now all you have to do is run this on a rooted zio?
[Kyocera Zio M6000] zyrtek69:
Awesome you guys are the shizniz!! So I'm guessing there's still a ways to go before 2.1? What does it mean that a clockwork recovery works now? Is this the first working complete back up?
[Kyocera Zio M6000] hotaru:
this one isn't completely working... i've fixed a few things and a new one is building now... also, we haven't figured out a way to boot into it without it doing a factory reset yet... still a long way to go before 2.1, but it's definitely progress.
[Kyocera Zio M6000] Spz0:
More like Work In Progress. :) But progress none-the-less. Since the cricket zio doesn't have any recovery to speak of, yes, this would be the first working backup. we're no where near releasing it yet.

Anyone else with relevant skills are more than welcome to join in the development fun @ #openzio
[Kyocera Zio M6000] phazei:
I was thinking about it reformating on recovery mode. When it builds the recovery image, it uses the old recovery image. We know it uses the kernel, but it probably also uses the ramdisk too. Extracts it, adds the Clockwork scripts to it, and repacks it. If that's the case, whatever was already on there, still is. So there's probably just some script that does the formating that needs to be removed. So just need to extract the recovery image, fix it, rebuild it, and it should work then.

Edit:

Looked at stock and clock, don't think that's the case. How does the sprint zio to a reset? Does it have a recovery mode?
[Kyocera Zio M6000] gregnotcraig:
"adb reboot recovery" doesn't do it? (was this mentioned earlier in the thread, but I missed it?) [edit: oops. it does. D'oh! ..and from terminal emulator ON the phone, too. thank dog for Ti Backup!]

the only modes i've seen are usb fastboot (power and then green button) and the "FOTA update modem" mode (power and volume up)

Trying various key combinations, i did find a new one (to me, anyway) -- volume down, power and camera key kick it in to a some kind of "read test pattern mode" that goes through all the memory/hardware registers .

Unfortunately, I didn't have time to sit and see just how far or long it took to go through all (and how many) registers it read and what happens after it's done.

If anyone has the time to see just what does happen before I do later this weekend...i'm curious

All other key combos that i could think of all sent it to fastboot.
[Kyocera Zio M6000] zyrtek69:
umm it looks like we may have been bamboozeled by cricket.. thats from the zio wiki
[Kyocera Zio M6000] Spz0:
Did you bother to read the source for that? Oh, there was no source reference material to confirm that statement... o.0

Bunch of heresay unless accompanied by reference material..

*edit: by the look of the sources other revisions of the wiki page, and the lack of references, there's no credibility.

http://en.wikipedia.org/w/index.php?title=Kyocera_Zio&action=history
[Kyocera Zio M6000] gregnotcraig:
But if it's on Wikipedia, it must be true [/sarcasm]
[Kyocera Zio M6000] zyrtek69:
That's a plus.. I just read it and hadn't seen that anywhere before.. was a little worried. But with you hodaku and phazei I think it'll happen sooner than later
[Kyocera Zio M6000] LordAnarchy:
I <3 mods:)

I am checking atleast two to three times a day for an "update" using Settings>About Phone>System Updates. Its just sad to see "No firmware update available". Has anyone heard of any new... news... about eclair or will Jesse Ventura be at Cricket HQ talking about conspiracies?

I am genuinely bummed at how that Huawei phone gets 2.1 yet the more expensive Zio is stuck with 1.6. The true update is 2.2 with SD support. I am enjoying the Universal Androot rooting with the Barnacle Wifi Tether app. Its pretty nice to have instant net access:)

Keep up the work guys, the thread rocks. I have the XDA app and this is my only fav thread to follow;) LOL.
[Kyocera Zio M6000] Flare106:
Agreed! Been following since this thread started, I would like to give thanks to all those trying to get us cricket guys an update! Sometimes I wonder why I even stick with the damn company, but in terms of saving money each month on a phone bill is nice!
[Kyocera Zio M6000] javajoe96:
I was thinking to myself I am going to goto Cricket's Facebook page and ***** on the wall about the update but someone already *****ed today and Cricket responded with this familiar message, "Cricket Wireless Update coming late 2010/early2011. We'll be sure to announce more details and steps when available." So then we are still in the holding pattern but I guess it is good to know they are indeed still working on it.
[Kyocera Zio M6000] alusher:
sanyo zio

i will agree you guys make my day about working on 2.1 for the zio. i too check this site three times a day. i sent a friend to buy the zio and told him they might upgrade it and if not we had some good people working hard at it. Well he went to cricket and the manager told him no upgrade and that the zio was a big mistake and sold him the other android cause it had more wieght to it. cricket as customer service goes sucks and i do wish you guys all the best on a upgrade thank you
[Kyocera Zio M6000] dreamstryder:
Hey lookit this way... maybe... JUST maybe if they wait till begining of the year... instead of a 2.1 it will be a froyo 2.2 update or maybe even gingerbread :) never know..........
[Kyocera Zio M6000] Fate43:
The update will be out either late 2010 or early 2011, Info via Cricket Wireless Facebook page and Via Both Cricket Wireless Regional managers I have talked to. There will be an update to 2.1 / not sure if it will be OTA or what but we will be receiving an update.
[Kyocera Zio M6000] Spz0:
We're working on 2.1 now. Let's see who releases it first. Heh

Got a working clockwork recovery now -still wipes data on recovery reboot - but fully functional otherwise.

Offer still stands -- anyone with android skills is welcome to join the think tank @ #openzio. :-)
[Kyocera Zio M6000] gregnotcraig:
Great news!

No link? Is it (clockwork) ready for the masses? You figured out how to get in to recovery then? Sorry, some blanks need filling in for me here.
[Kyocera Zio M6000] Spz0:
Not ready for the masses yet. Since it data/cache wipes on reboot-to-recovery (attempts at nixing that resulted in the verizon network flip), its only good for making stock nandroid backups. you'll have to use tibackup or something else to backup userdata.

Its main purpose for now, is to make it easier to test the 2.1 rom thats being worked on. Im sure it'll get worked on some more once we get 2.1 working.

I mean, I can send you a copy if you like, but its kind of pointless atm from a logic standpoint. it'd be easier still for the masses to use dump_image / flash_image / mkfs.yaffs2 if they wanted a complete backup of their current system/boot/userdata. :)
[Kyocera Zio M6000] gregnotcraig:
I do use Ti Backup (and was glad I did, when I entered 'reboot recovery' from Android Terminal Emulator. "ooh, looky there. a fresh, clean phone!").

Before I consider having you send it to me (I AM that kind of masochistic geek)...curiosity...flash the recovery image, reboot recovery and it starts clockwork? or whats the flow?
[Kyocera Zio M6000] Spz0:
flash_image recovery /<loc. to clockwork image> through adb

reboot recovery

system reboots, then you see the android appbox with a progress bar.

you need to hit the red key within a few seconds of that or it will bork out and you'll have to pull the battery.

once redkey is pressed, data/cache is wiped, then clockwork is loaded.
[Kyocera Zio M6000] gregnotcraig:
nice!

Kudos to your and everyone involved hard work on this.

I assume that the 2.1 your working on porting is either Cyanogen or AOSP?

Send me the clockwork d/l link, please? I may or may not load it...depends on how sadistic I feel today :)

Wish I could code more than "hello world", I'd love to be able to contribute to the effort...I do offer up my phone as a guinea pig, though!:)
[Kyocera Zio M6000] Spz0:
join #openzio and I'll hook you up.

We're working on the sprint 2.1 rom from the sprint sanyo zio, all the same specs, so its the most logical/fastest rom to work on
[Kyocera Zio M6000] wwwilly1986:
How do we join? My computer will not pull up the irc.freenode.net webpage
[Kyocera Zio M6000] gregnotcraig:
Oh, gotcha. That was mentioned earlier in the thread. Forgot, plus a previous reference to cyanogens github for the Donut source... brain mixed things up. I'll drop by freenode at some point!
[Kyocera Zio M6000] Spz0:
here:
[Kyocera Zio M6000] Spz0:
Sounds good m8. 8-)
[Kyocera Zio M6000] partytrikk:
any news on this? and just to be clear, is this the same as the Sanyo zio?
[Kyocera Zio M6000] wwwilly1986:
Yes, Kyocera owns Sanyo or vice versa, can't remember but it is the exact same phone.
[Kyocera Zio M6000] gregnotcraig:
IIRC, Kyocera bought Sanyo and brands their phones w/ the name.
[Kyocera Zio M6000] hotaru:
they have slightly different MTD partition layouts, but they're the same hardware.

still working on trying to figure out why the sprint rom won't boot on a cricket zio... i'm thinking maybe something in the system dump i have is corrupted somehow... next time my brother is here i'll try to get another dump from his sprint zio and see if that works. if it doesn't, then getting it to work may require disassembling things and figuring exactly what is happening.. which is a very slow and tedious process.
[Kyocera Zio M6000] partytrikk:
well just keep up the good work :) we all appreciate it!
[Kyocera Zio M6000] beatadalhagen:
Sprint's phone does appear to have a different style of speaker grille; noticed this when shopping accessories.
[Kyocera Zio M6000] jrbloodmist:
So do we know if the sprint zio has a community built up yet that can maybe give us some insight? Dumps ect?
[Kyocera Zio M6000] gregnotcraig:
We have dumps of both the Cricket Zio and the Sprint Zio.

Clockwork has been ported (I have it running on mine) and there is a small dedicated bunch doing what they can, when they can.

Check out #openzio on freenode.
[Kyocera Zio M6000] whitey10tc:
Here is an APN now if some can dump the ROM. Since it can be rooted, a recovery.img can be done, it's 1/3 to having custom 2.1 ROMs built for it.
[Kyocera Zio M6000] hpservertech:
Anyone need anything else off these devices? Have mine rooted so just let me know.
[Kyocera Zio M6000] phazei:
Are we stuck on getting a rom dump until Clockwork Recovery is updated to support the phone?

Is there another way?
[Kyocera Zio M6000] t12icky0:
yes could you do a complete rom backup? i would like to start trying to work on something. it would be very appreciated.
[Kyocera Zio M6000] hpservertech:
PM sent for the rom backup.
[Kyocera Zio M6000] chrisfic:
Could you post a link for this backup? I would like to check it out as well...
[Kyocera Zio M6000] hpservertech:
Nothing to post yet, still dont know how to do a rom backup on this device.
[Kyocera Zio M6000] xTONEx:
delete this post
[Kyocera Zio M6000] hpservertech:
why would we want to delete this post?