(Solved)*Help* Clockwork Recovery bricked my phone!!! - Kyocera Zio M6000

I just bought the premium version of Clockwork Recovery. Just before that I ran the "fix permissions" as it was my understanding its supposed to help fix apps from "force close". It instructed me to reboot and now its stuck at the Kyocera boot logo with...
CANNOT READ BOOT IMAGE HEADER
USB Fastboot: V0.5
Machine ID: 1007074 v0
Build Date: Oct 26, 2010, 23:13:15
MSM Id: 44
MSM Version: 1.2
Modem Build Id: 76XXT-4715-TSNCJPLYM
Serial Number: UNKNOWN
ptn 0 name='fota_amss' start=538 len=132
This ptn goes all the way to 8 then after that flash_detect_size 4G!
I take it my phone is totally bricked? Now what?

Not totally bricked, just need the update package
Sent from my Zio using XDA Premium App

Yeah I was able to get it back. But now I have a triangle in the status bar and don't know what that is. I thought it was that I needed to *228 my phone but it won't do it.

I accidentally did the same thing today and have no idea to fix it. could you please help me out, im new to all of this.
Nevermind i figured out how to fix it

You all didnt read my clockwork recovery thread posted further up on this sub forum.....
Please read it.
That recovery image doesnt work. Flat out. Im trying to get a hold of Koush to remove it from the rom manager list, but hes hard to get a hold of on the weekdays.
You need to flash your original recovery back to the recovery partition through fastboot in order to "unbrick" your phone.

Well I got my phone back working again. The MIN, SID and one other part of the phone was reset! How this happened don't know. Its all fixed now but my signal strengh sucks now.

It happened because the image doesn't work - and if you would have read my thread on clockworkmod recovery, you would have known that and not borked ur recovery.
You guys need to read threads before going all cowboy n ****.
If you have a copy of your stock recovery image (which you should have all your images backed up if you're flashing different images to your phones), you need to flash that to your recovery partition in order to fix your issue.
Sent from my Zio using XDA App

Spz0 said:
You guys need to read threads before going all cowboy n ****.
Click to expand...
Click to collapse
This literally made me LOL.
Sent from my Zio using XDA App

I'm sorry but rofl, I'm being safe since Rom Manager bricked my phone last October.
Sent from my Zio using XDA Premium App

/agree
Spz0 said:
You all didnt read my clockwork recovery thread posted further up on this sub forum.....
Please read it.
That recovery image doesnt work. Flat out. Im trying to get a hold of Koush to remove it from the rom manager list, but hes hard to get a hold of on the weekdays.
You need to flash your original recovery back to the recovery partition through fastboot in order to "unbrick" your phone.
Click to expand...
Click to collapse
I think he needs to change the thread title to something more appropriate like " Help, I did something wrong while using Clockwork Recovery and now I Bricked my phone! "

Or "Help, I didn't bother to research and bricked my phone"
Sent from my Zio using XDA Premium App

I was able to fix it. All is working as it should.
ZIO 2.2 ROOTED
ADW Launcher EX
Gingerbread Theme

please tell me...i did the same thing. I d apprecate it muchly. [email protected]

z3r0t0l0rEnCe said:
I just bought the premium version of Clockwork Recovery. Just before that I ran the "fix permissions" as it was my understanding its supposed to help fix apps from "force close". It instructed me to reboot and now its stuck at the Kyocera boot logo with...
CANNOT READ BOOT IMAGE HEADER
USB Fastboot: V0.5
Machine ID: 1007074 v0
Build Date: Oct 26, 2010, 23:13:15
MSM Id: 44
MSM Version: 1.2
Modem Build Id: 76XXT-4715-TSNCJPLYM
Serial Number: UNKNOWN
ptn 0 name='fota_amss' start=538 len=132
This ptn goes all the way to 8 then after that flash_detect_size 4G!
I take it my phone is totally bricked? Now what?
Click to expand...
Click to collapse
what are the button combination 2 boot in recovery, my Sanyo/Kyocera M6000 Zio was bricked same way, I downloaded stock rom, nandroid backup. But dont know how 2 boot in reovery to attempt 2 fix it.... sorry 4 noob question

Power (red) + Send (green) from powered off state. You should boot up to USB Fastboot. From there you will need to connect to your computer and from AndroidSDK in command prompt type "fastboot boot openzio-recovery"
Sent from my Zio using XDA Premium App

like a dumb ass I did the same thing to my phone about half an hour ago and still trying to restore it back to fix it.

Related

N1 won't accept any ROM imgs

So a buddy sent me his N1 that had been stuck in a boot loop. I asked him to give me the details of what the phone had been through. Of course he didn't know squat! I assume it's a European version (he's in the Philippines).
When I got the N1 it didn't boot to recovery but it did boot to bootloader. I was finally able to flash Aman_RA recovery thru adb. Now I can boot into recovery. I've tried flashing 3 different roms (all MD5 checks pass) but the N1 one shoots out different errors for each ROM. For ex. Missing wallpaper/desire.jpg or some other weird error.
I've been searching for 2 weeks. When I enter bootloader mode and hboot, the device looks for a PASSDIAG.zip. I dl a stock image from the developer.htc site and renamed it to PASSDIAG.zip. If finds it but then gives error about missing PASSDIAG.nbh or image not being the right one.
If I use adb to wipe the cache (in bootloader mode) it works fine, but when I try to wipe userdata I get the "FAILED" to wipe error. Fastboot windows-devices gives me HTCxxxxxxxx so i know it communicates. And i was able to flash recovery twice. No problems .
EDIT: IF YOU NOTICE IN THE SECOND IMAGE THE BLUE STATUS BAR SHOWS UP AND GOES TO THE TOP AS IF IT ACTUALLY WAS DOING SOMETHING
I tried to flash an image using fastboot and adb (flash userdata userdata.img ) but it just hangs for ever.
I just can't flash an Os on this thing. Trully, bricked me thinks?
How do I know what original build should be on it? As I read to flash an original recovery. I can only get the Aman_RA to flash.
Someone mentioned to get ahold of the stock build for EPF30. How in the world do they know that. I sure as hell can't find it...lol. Everything in google search points me to everything but that build.
Thanks in advanced.
Go to Wiki, link in my signature.
Install Amon_Ra's latest recovery.
Go to Stock ROM section and download the only Eclair ROM it has there, the first one.
Go to Guides, look at "unroot/restore", PASSIMG.ZIP method. Execute.
If it doesn't flash the PASSIMG - post the error it gives.
If it does and you're on Eclair - congratulations, work your way from there.
I see 26 images. I assume this one is it "Passion-EPE54B.zip"? Seeing as the first one is ATT. Thank you for pointing me to this wiki. Can't wait to try it.
Did you try selecting clear storage?
@ SiN Well, it's weird. In recovery I can wipe storage, cache and dalvic cache. I wiped everything that could be wiped. And still got errors on any rom I tried.
So in fastboot adb I tried
Code:
fastboot erase userdata
and I get an error FAILED. But when I do
Code:
fastboot erase cache
it says OK!
I'm gonna try what Jack suggest right now....I will post update in a few hours? LOL, I'm @ work and will try to get this to work from these PCs
The passimg you used, it wasn't a zip within a zip was it? That can cause the blue bar thing.
So the .zip I used was the second from the top in the stock rom wiki. I think EPF45, and I get an error. I renamed it to PASSIMG.zip (made sure its not a zip of a zip) and got the red status bar. One error...."cannot unzzip .zip" see picture. Now I get static x screen that turns to pixelated dust. LOL...almost there. I guess its a rom region thing?
Sent from my HTC HD2 using XDA App(CM6)
Try:
fastboot erase system
Click to expand...
Click to collapse
Repeat several times.
Looks like your system partition fails when attempting write. Might be a failed partition, might be something recoverable.
Then try to apply PASSIMG again.
fastboot erase system
erasing 'system'.... FAILED <remote: not allowed>
Click to expand...
Click to collapse
Sent from my HTC HD2 using XDA App
EDIT: I tired
fastboot oem unlock
Click to expand...
Click to collapse
and it says
device already UNLOCKED!
Click to expand...
Click to collapse
Haha, man this fool really did a number on it. He said he installed pinochle from the market and then it stopped booting. IDK
Hello ,
i cannot start my phone (nexus one) .
i search more time on the forum but i dont understand perfectly.
in recovery mode appear "tricolore" screen ... is wrong ? if i put phone in usb computer nothing happened. (no usb device found)
where is my solution for can use my nexus one ?
system is android 2....
thanks in advance and sorry for my bad english /
if someone can explain me step by step i will appreciated.
Can you explain tricolor screen?
Sent from my Nexus One using XDA App
some like that: first image ... with three little androids on the skateboards botton without any words
give me your email or send to me a "hello" from my email : [email protected] because im a new member and i cant post linked to image here (privilege)
You mean like this?
Sent from my Nexus One using XDA App
yes ... is this that ,.,.,\when i press down volume + power
and four colour screen when phone started normally (power) and phone is freeze
What were you doing before the problem started?
Sent from my Nexus One using XDA App
give me your email for send to you image / here i cant post
Don't think I need an image...
The pic I posted is the bootloader (not recovery). Recovery looks black...
Tell me what you were doing, and we'll take it from there...
Sent from my Nexus One using XDA App
i attach images
I can go in boot mode too ...
I have this:
-Fast boot
-Recovery
-Clear Storage
-Sim Lock
when i press fast boot i have another screen with : bootloader,reboot,reboot bootloader,power down
i press boot loader screen is freeze .
where i get wrong ?
SD checking......
Loading [Passdiag.zip]
error image
and its freeze again

[Q]Accessing Recovery With Broken Power Button

So I have a bit of an issue. Over the weekend my power button stopped working like it has for many people.
I finally got to a computer last night and was able to turn it on using a method I had read about.
I was using madaco's desire port but I didn't have the option for wake with trackball baked into it. Which I need to have my phone usable. So I had another ROM baked on his site with that option in it but I forgot to tick the option to have the .zip signed. (I'm using an older recovery, had been to lazy to update)
I didn't realized it wasn't signed until I had go into recovery, wiped everything and then attempted to flash at which time it said no because it wasn't signed. So I said F it I'll do it in the morning.
So today I realized I can't boot the phone up because I had wiped everything, including the ext partition. It just sits at the X screen with the unlocked paddle lock on it. Due to this I can't access it with ADB to get to recovery.
If I restart the phone and put it into HBOOT I can't select recovery because you have to press the power button to select the option.
I also tried finding a fastboot command to boot into recovery but didn't locate one.
SOO
Does anyone have a clue how I can get this damn thing into recovery? I'm normally really good with this stuff but I am stumped at this point.
And before anyone says it I can't exchange it because my screen is cracked.
If you can grab a kernel and and recovery image on your PC you can boot them using
fastboot boot <kernel image> <recovery image>
Is that going to get me to a point where I can flash a new rom on it? I was running all of my cache on SD so when I wiped it is messed the rom up.
It already has Amon_RA recovery on it, the release prior to the newest one. So do I really need to flash another one to it?
All I can think of is possibly reverting to stock via the passimg method, but I can't remember if you need to use the power button to confirm during the process?
Once you have a working ROM, you can root via superoneclick, and install superboot to boot into recovery.
Problem is, you'll then have a stock recovery...
Once you're booted and rooted though, you can always use adb, or ROM Manager right?
Sent from my Nexus One using XDA App
danger-rat said:
All I can think of is possibly reverting to stock via the passimg method, but I can't remember if you need to use the power button to confirm during the process?
Once you have a working ROM, you can root via superoneclick, and install superboot to boot into recovery.
Problem is, you'll then have a stock recovery...
Once you're booted and rooted though, you can always use adb, or ROM Manager right?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Yeah that's the route I'm thinking about taking. But I think there are option you have to use the power button to confirm.
I'm messing around with different boot.img right now to try and get it to boot. If I could just get the damn thing to boot I'd be all set cause I can use adb from that point. But right now when it stops at the X screen ADB can detected the phone but if you try to access the shell you get "failed to link /system/bin/sh
Thanks for the input man
If your bootloader is unlocked, you can re-image with fastboot.
Also, if you're not unlocked, I'm pretty sure the passimg only selects options with the volume keys...
Sent from my Nexus One using XDA App
I went with the superboot method. When I ran the .bat files it restarted the device and put it into recovery. I flashed a fresh ROM from there.
It's made it to the boot animation so I'll see if it fully boots up in a minute .
Okay, I'm back in action. Thanks for the in put guys.
Great!
D'ya need an unlocked bootloader to use superboot (I've never used it)?
Sent from my Nexus One using XDA App
Just discovered this gem:
http://forum.xda-developers.com/showthread.php?t=825909
Sent from my Nexus One using XDA App
danger-rat said:
Great!
D'ya need an unlocked bootloader to use superboot (I've never used it)?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I'm pretty sure you do. It says you'll probably need to as a foot note in the directions for superboot.
I may be wrong, I haven't kept up on much relating to rooting the Nexus since it first came out.
I think you're probably right... Thanks!
Sent from my Nexus One using XDA App

Emergency need help ASAP

Okay so I was helping a guy root his Droid 1 and I got him successfully rooted however I turned it over to another guy I know who has a Droid who knows avout the roms he tried to get him to install ultimate Droid 2.2 but he forgot to wipe so it wouldn't boot I told him to go back into recovery and do a reset and it finally worked however that's when left then I left the chat and the other guy that was helping was getting him to install a kernel for ovcing and that's when it whent bad the phone wouldn't reboot he's tried everything reinstalling the rom and doing resets but his phone won't boot he can access recovery clockworkmod* but that's it and he didn't back up his stock Rom he does have access to a computer with internet can someone pleases reach me through gtalk were Im talking to him my contact is [email protected] he needs his phone going buy Monday for work please help
Sent from my HERO200 using XDA App
My suggestion is download the latest sholes cyanogen mod 6.1 RC4, boot into clockwork mod recovery and mount the SDcard (using clockwork) with the USB cable attached to the PC holding the cyanogenmod zip, copy zip to phone and flash with clockwork.
Sent from my Droid
Oh yea I forgot that
Sent from my HERO200 using XDA App

[Q] BRICK?!?! Please Help

Sorry if this is the wrong place to post this, but I need help recovering from what I think is a brick.
I recently did a factory restore, because my streak 7 was acting strange, fc, and such. When I rebooted, nothing.... no fastboot, no recovery of any kind, only usb connection is apx, which I did install the drivers for, and it does connect to my pc as apx.
I have got what info I got from a thread about a bricked streak, which got me through installing the apx drivers, but the rest is more device specific..... i think?
Now I need help flashing a recovery... I think?? any suggestions?
look up in the fastboot thread... i posted on how to flash using fastboot. get the original shipping roms from the performance thread and flash those.
fastboot is lower into the hardware level than recovery....
bogdi1988 said:
look up in the fastboot thread... i posted on how to flash using fastboot. get the original shipping roms from the performance thread and flash those.
fastboot is lower into the hardware level than recovery....
Click to expand...
Click to collapse
]
It wont boot into fastboot either?? tried every thing all I can get is apx connection through usb
im having the same issue
If you guys would read the dev thread you would know I am almost done with a CWM recovery. Follow my thread and hit the thanks button and I will let you know on the thread when it is done.
Sent from my SGH-T959 using XDA Premium App
binarybishop said:
If you guys would read the dev thread you would know I am almost done with a CWM recovery. Follow my thread and hit the thanks button and I will let you know on the thread when it is done.
Sent from my SGH-T959 using XDA Premium App
Click to expand...
Click to collapse
how would we flash your recovery and we cant get passed our first issue...and you shouldnt ask for someone to press thanks .....let them do it when they feel needed
I always have to flash the recovery twice. I think the app should do that for me.
Giving thanks and clicking ad banner supports development! Time is money. Software development and support takes lots of time. Click 10 ads if you like the software! click 10 ads if you need support! Watch the updates roll out!
- Posted via mobile

[Q] Help! Phone won't boot up or recovery menu!

I have a samsung captivate and i have been using the ROM fasty 2.5 for the past few months and i noticed there was a fasty III 1.3, So i went into my clockwork recovery and back up'd my system and data and whiped it all and proceeded to install the ZIP to my phone. When it all had finished i tried to reboot my phone and i got this staticy screen and then it would repeatedly restart over and over back to the static. So i then forced it to stay off and tried to boot it up to the recovery menu by holding the volume buttons and the power button and it can't boot to the recovery menu. Instead it just stays at the I896 screen. Is there anything i can do to fix this problem? i need my phone working as soon as possible so any help would be very much appreciated!
Sounds to me like you didn't flash the GB bootloaders. Might need to get yourself a jig and then flash the right bootloaders
Sent from my SAMSUNG-SGH-I897 using xda premium
Sorry for being a huge noob, but i'm still pretty new to this whole thing. What a jig?
Phizzard said:
Sorry for being a huge noob, but i'm still pretty new to this whole thing. What a jig?
Click to expand...
Click to collapse
Take a look at the sticky threads and search for a download mode jig
Sent from my SAMSUNG-SGH-I897 using xda premium
I checked all the sticky notes and the web and it looks like these all include me messing around with the insides of my phone and tinkering with the hardware. I am not very comfortable doing that or do i have the understanding or tools to mess with that. Is there anything i can do software related to unbrick this. Or is my phone truly F'd?
No worries! I ended up using odin3 to restore it. Thank you very much for your help anyways! i will be sure to grab those GB loaders this time.

Categories

Resources