Database Info

[Q][ !! SOS !! ] Cannot boot in to system/recovery, and cannot flash anything

Yesterday, I was going to flash CM11.
After I flash boot.img of cm11 with fastboot, it can't return to recovery again!!:crying:
It only can boot into fastboot, cannot boot in to system or recovery, also cannot charging!!:crying:
When I want to flash back to stock boot.img, it said:
C:\adt-bundle-windows-x86_64-20131030\sdk\tools>fastboot flash boot boot.img
sending 'boot' (10240 KB)... OKAY [ 1.189s]
writing 'boot'... INFOBattery Low!!
FAILED (remote failure)
finished. total time: 1.430s
C:\adt-bundle-windows-x86_64-20131030\sdk\tools>fastboot flash boot boot.img
sending 'boot' (10240 KB)... OKAY [ 1.187s]
writing 'boot'... INFOBattery Low!!
FAILED (remote failure)
finished. total time: 1.435s
C:\adt-bundle-windows-x86_64-20131030\sdk\tools>
Click to expand...
Click to collapse
When I flash RSD, it said:
Faild flashing process. 1/23 flash partition "gpt_main0.bin" -> USB error occurred while reading/writing.
Click to expand...
Click to collapse
What can I do?:crying: Sorry for my bad English.

[email protected] said:
Yesterday, I was going to flash CM11.
After I flash boot.img of cm11 with fastboot, it can't return to recovery again!!:crying:
It only can boot into fastboot, cannot boot in to system or recovery, also cannot charging!!:crying:
When I want to flash back to stock boot.img, it said:
When I flash RSD, it said:
What can I do?:crying: Sorry for my bad English.
Click to expand...
Click to collapse
Can you try RSD using a different cable/port/computer entirely?
That's an odd and unfortunate error to receive. You put the device in fastboot mode before running RSD?

arrrghhh said:
Can you try RSD using a different cable/port/computer entirely?
That's an odd and unfortunate error to receive. You put the device in fastboot mode before running RSD?
Click to expand...
Click to collapse
Not Yet
Yes
At first, I put my PQ in fastboot mode and running RSD 6.1.5...
(asanti_c_sprint-user-4.1.2-9.8.2Q-122_XT897_FFW-5-6-release-keys-cid9.xml)
(without <step operation="getvar" var="max-download-size" />s)
...than flash recovery-clockwork-6.0.1.3-asanti.img with fastboot,
after that, Flash cm-11-20131209-NIGHTLY-xt897.zip and failed (2-3 times)
Than I take the boot.img from it and flash it with fastboot, at last: #1

[email protected] said:
Not Yet
Yes
At first, I put my PQ in fastboot mode and running RSD 6.1.5...
(asanti_c_sprint-user-4.1.2-9.8.2Q-122_XT897_FFW-5-6-release-keys-cid9.xml)
(without <step operation="getvar" var="max-download-size" />s)
...than flash recovery-clockwork-6.0.1.3-asanti.img with fastboot,
after that, Flash cm-11-20131209-NIGHTLY-xt897.zip and failed (2-3 times)
Than I take the boot.img from it and flash it with fastboot, at last: #1
Click to expand...
Click to collapse
Ok, you should not have done the boot.img flash.. not sure why you did that.
Now, you should restore with RSD. It sounds like RSD has worked in the past, but is no longer? Have you tried multiple FXZ files? If you are downgrading, there are additional lines to remove from the .xml file.

arrrghhh said:
Ok, you should not have done the boot.img flash.. not sure why you did that.
Now, you should restore with RSD. It sounds like RSD has worked in the past, but is no longer? Have you tried multiple FXZ files? If you are downgrading, there are additional lines to remove from the .xml file.
Click to expand...
Click to collapse
I restore my phone like this and it said:
Failed flashing process. 1/23 flash partition "gpt_main0.bin" -> Phone returned FAIL.
Click to expand...
Click to collapse
PS: Not「Faild flashing process. 1/23 flash partition "gpt_main0.bin" -> USB error occurred while reading/writing.」like #1

[email protected] said:
I restore my phone like this and it said:
PS: Not「Faild flashing process. 1/23 flash partition "gpt_main0.bin" -> USB error occurred while reading/writing.」like #1
Click to expand...
Click to collapse
Could be even an error on your HDD.
Try to do a deep chkdsk of your hard drive
chkdsk /f /r c: (assuming your main partition is called C: )
and / or try a different FXZ (say the ICS one)

[Q] bricked? not sure

Got a phone from a friend. Said it was bricked.
In bootloader:
*** unlocked ***
doubleshot pvt ship s-on rl
hboot-1.45.0013
microp-0353
emmc-boot
When click recovery, get 3 skateboarders and back to menu.
Tried to load a recovery:
C:\Android>fastboot flash recovery recovery-clockwork-5.0.2.7-doubleshot.img
sending 'recovery' (4754 KB)...
OKAY [ 0.888s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 2.348s
Received above error, should I perform another step first?

Somehow finally got cwm 5.0.2.7 into recovery.
Found this thread and did basically the same thing.
http://forum.xda-developers.com/showthread.php?t=2665472
Downloaded cm-9-1-(3-0-97)-r13.zip
Checked md5sum
Extract contents of ROM to PC(boot.img)
Put the full zip and gapps on SD card
Boot to recovery
Wipe data/factory reset, wipe cache partition
Flash ROM cm-9-1-(3-0-97)-r13.zip. Install successful.
Pulled battery, boot direct to bootloader
Flash kernel with fastboot <<<<< here I get the below error
fastboot flash boot boot.img
sending 'boot' (16384 KB)...
OKAY [ 2.624s]
writing 'boot'...
FAILED (remote: image update error)
finished. total time: 4.085s
Any suggestions?

Try miktouch or another stock based ROM so you don't need to flash kernel
Sent from my Nexus 4 using XDA Premium 4 mobile app

Is there a particular miktouch I should try? Would the below link be good to try?(for some reason having hard time finding)
"cx.com/mycx/share/jzvMU-erEeGfjBICOBql1A/MikTouch-0.7-signed.zip"
And just follow the steps and flash it vs cm9, correct?

Any stock based ROM is easier to flash as you don't need to flash the kernel afterwards through fastboot. Also cm9 is one of the few Roms I have seen issues for people when trying to flash, granted it is one of the better Roms out there, but right now you are just trying to get this working again, so stick with easy.
And I would think that's a good link, but didn't check
Sent from my Nexus 7 using XDA Premium 4 mobile app

installed miktouch 07...i installed the zip from sdcard and it installed and then it rebooted the phone. Stuck at mytouch4g logo screen, left it on this screen 20+ minutes. I took battery out and turned on with the same result.

any suggestions on trying something else?

waynebattle said:
installed miktouch 07...i installed the zip from sdcard and it installed and then it rebooted the phone. Stuck at mytouch4g logo screen, left it on this screen 20+ minutes. I took battery out and turned on with the same result.
Click to expand...
Click to collapse
What ROM were you on before? If its non stock, I would try to fastboot flash the boot.img
Sent from my Nexus 4 using Tapatalk

unfortunately got it from a friend like this, not sure what he had on it.
I flashed boot.img and this is what I received:
C:\Android>fastboot flash boot boot.img
sending 'boot' (3438 KB)...
OKAY [ 0.770s]
writing 'boot'...
FAILED (remote: image update error)
finished. total time: 2.229s
Any ideas?

waynebattle said:
unfortunately got it from a friend like this, not sure what he had on it.
I flashed boot.img and this is what I received:
C:\Android>fastboot flash boot boot.img
sending 'boot' (3438 KB)...
OKAY [ 0.770s]
writing 'boot'...
FAILED (remote: image update error)
finished. total time: 2.229s
Any ideas?
Click to expand...
Click to collapse
On some of my Linux distros I would have to use fastboot flash with a ./ before it would work.
./fasboot flash boot boot.Img
I have no idea why it was like this but it helped me a fee times on the DS. If its anything else I'd have no idea, I haven't messed with this since I sent mine off to a XDA user here.
Sent from my Nexus 4 using Tapatalk

Thanks. Not using linux, but tried .\fastboot with no difference in results. Thanks for trying. Anyone else have any other ideas?

waynebattle said:
Thanks. Not using linux, but tried .\fastboot with no difference in results. Thanks for trying. Anyone else have any other ideas?
Click to expand...
Click to collapse
You said you are able to get into recovery? Try factory resetting there

Download this 1.44.1107 S-Off PG59IMG Hboot. Rename it to PG59IMG.zip. Send it to the sdcard, and reboot into the bootloader. It will then be installed automatically. This may or may not solve the problem. Try flashing a ROM now.

abe5 said:
Download this 1.44.1107 S-Off PG59IMG Hboot. Rename it to PG59IMG.zip. Send it to the sdcard, and reboot into the bootloader. It will then be installed automatically. This may or may not solve the problem. Try flashing a ROM now.
Click to expand...
Click to collapse
dont you need to be locked to do this? i've tried "fastboot oem lock" but it has an error about too many links and the phone shuts off and it shows that it is still unlocked. I tried the PG59IMG.zip anyway and it said parsing and went right back to hboot within a second.. Flashed miktouch rom. Restarted phone, still just stuck on logo screen.

What do you see in the bootloader? Has something changed? Try flashing a recovery this time. The latest Clockworkmod should be fine. Then see what happens.

abe5 said:
What do you see in the bootloader? Has something changed? Try flashing a recovery this time. The latest Clockworkmod should be fine. Then see what happens.
Click to expand...
Click to collapse
I don't see any differences in the bootloader. Is there something specific you think may have changed.
Do you want me to try to reflash the cwm 5.0.2.7 version(currently loaded) or a different version(I didn't see a newer version for 4g slide)?

waynebattle said:
I don't see any differences in the bootloader. Is there something specific you think may have changed.
Do you want me to try to reflash the cwm 5.0.2.7 version(currently loaded) or a different version(I didn't see a newer version for 4g slide)?
Click to expand...
Click to collapse
Alright. This version: http://forum.xda-developers.com/showthread.php?t=2085842
Clockworkmod 6.0.4.6

abe5 said:
Alright. This version: http://forum.xda-developers.com/showthread.php?t=2085842
Clockworkmod 6.0.4.6
Click to expand...
Click to collapse
No luck, (md5 check sum verified) get error when try to flash it:
C:\Android>fastboot flash recovery cwm.img
sending 'recovery' (6338 KB)...
OKAY [ 1.285s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 2.745s

Unfortunately my friend, I believe your emmc is severally corrupt. If you are able to get adb working from within recovery you may be able to try a few more things to bring this back to life but as it stands, with s-on, you may be sol
Sent from my Nexus 7 using XDA Premium 4 mobile app

demkantor said:
Unfortunately my friend, I believe your emmc is severally corrupt. If you are able to get adb working from within recovery you may be able to try a few more things to bring this back to life but as it stands, with s-on, you may be sol
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
When you say adb working from within recovery, I am able to mount usb storage within recovery and then on pc I can do 'adb devices' and I see the device, is that what you are referring to? Thanks.

[Q] XT925 partition error?

My Xt925 has "Encrytion Unsuccessful" when I boot up. I have tried to flash a recovery img but all I get is this message.
C:\Documents and Settings\Admin\Desktop\Fastbootxt925\Fastboot>fastboot flash re covery twrp-hdrecovery.img
sending 'recovery' (6678 KB)... OKAY [ 0.844s]
writing 'recovery'...
INFOFailed to erase partition INFOFailed to flash partition recovery
FAILED (remote failure) finished. total time: 1.000s
Click to expand...
Click to collapse
Motorola XT925
Android 4.2
AF Fastboot flasmode (s)
10.9B (Sha-5b608bc, 2012-12-20 16:55:20)
eMMC info: size 16gb
Device is unlocked, status code: 3
Its Bricked isn't it?
I have tried getting some help so I hope someone reads this..

"Partition signed?"
is0lde said:
My Xt925 has "Encrytion Unsuccessful" when I boot up. I have tried to flash a recovery img but all I get is this message.
Motorola XT925
Android 4.2
AF Fastboot flasmode (s)
10.9B (Sha-5b608bc, 2012-12-20 16:55:20)
eMMC info: size 16gb
Device is unlocked, status code: 3
Its Bricked isn't it?
I have tried getting some help so I hope someone reads this..
Click to expand...
Click to collapse
I have also tried reflashing rom using RSD Lite, and get a the Following error
Failed flashing process. 2/22 Flash parition "partition signed" -> Phone returned FAIL.
Click to expand...
Click to collapse

is0lde said:
I have also tried reflashing rom using RSD Lite, and get a the Following error
Click to expand...
Click to collapse
Delete the partition signed line from the Xml and try flashing again!!!!
Al the best!!!!
Sent from my C6802 using Tapatalk

Same problem
Hey man, having the same problem, excluded the line (actually many), and it installed 14. Now the reboot is in process and nothing happens.
kumeipark said:
Delete the partition signed line from the Xml and try flashing again!!!!
Al the best!!!!
Sent from my C6802 using Tapatalk
Click to expand...
Click to collapse

mari18cf said:
Hey man, having the same problem, excluded the line (actually many), and it installed 14. Now the reboot is in process and nothing happens.
Click to expand...
Click to collapse
flash the partition file with "Mfastboot", then re-flash the stock file with only the partition, tz, and getvar(you may not have this) removed.

Stucked at "Rom Logo"

Hey guys..
I made a search on google for the best rom for a Moto G, and found a website with links for Paranoid, CNM, and Slim.. and i picked SLIMKAT
But after dong the process of installing twrp or CWM Recovery.. ended up sticking with CWM recovery cause of the buggy touch on the TWRP
so i was able to flash the rom and did it in this order
Flash Rom
Flash Gapps
Flash SU
reboot.. and got stucked at "slimkat logo"
then i decided maybe there was something wrong with the rom so i tried flashing Paranoid.. same deal.. stucked at logo.
Would anyoen please point me in the right direction fo what i need to do to fix this?
Thank you

SD card
Xcarab said:
Hey guys..
I made a search on google for the best rom for a Moto G, and found a website with links for Paranoid, CNM, and Slim.. and i picked SLIMKAT
But after dong the process of installing twrp or CWM Recovery.. ended up sticking with CWM recovery cause of the buggy touch on the TWRP
so i was able to flash the rom and did it in this order
Flash Rom
Flash Gapps
Flash SU
reboot.. and got stucked at "slimkat logo"
then i decided maybe there was something wrong with the rom so i tried flashing Paranoid.. same deal.. stucked at logo.
Would anyoen please point me in the right direction fo what i need to do to fix this?
Thank you
Click to expand...
Click to collapse
Genius me, seems at some point i deleted or formatted the sdcard now when i go to install zip on cwm recovery i get "Can't mount sd card

Xcarab said:
Genius me, seems at some point i deleted or formatted the sdcard now when i go to install zip on cwm recovery i get "Can't mount sd card
Click to expand...
Click to collapse
I'd restore stock firmware (that should get rid of those "sd card" errors) and then flash the custom recovery again.
I'd try the philZ recovery instead of CMW. And finally flash the Rom you want to.

Thank you
Landrea said:
I'd restore stock firmware (that should get rid of those "sd card" errors) and then flash the custom recovery again.
I'd try the philZ recovery instead of CMW. And finally flash the Rom you want to.
Click to expand...
Click to collapse
Ty Landrea.. in the process of doing exactly that now.. struggling on the "bootloader permission denied"
going trought the steps of unlocking bootloader again... will post how it goes

But are you sure that bootloader is unlocked?

Well i guess
denzel09 said:
But are you sure that bootloader is unlocked?
Click to expand...
Click to collapse
This is prove enough that it was
E:\Kindle Fire Utility\tools\Firmware restore lock and more 4.4.2>fastboot oem u
nlock UNIQUE_KEY
...
(bootloader) Device already unlocked!
FAILED (remote failure)
finished. total time: 0.013s
E:\Kindle Fire Utility\tools\Firmware restore lock and more 4.4.2>

Xcarab said:
Ty Landrea.. in the process of doing exactly that now.. struggling on the "bootloader permission denied"
going trought the steps of unlocking bootloader again... will post how it goes
Click to expand...
Click to collapse
Omg that's strange. Unlocked bootloader once = unlocked bootloader forever, it's impossible you somehow re-lock it.
Did you follow the instructions on Motorola webiste to unlock?

Returning to stock process
Landrea said:
Omg that's strange. Unlocked bootloader once = unlocked bootloader forever, it's impossible you somehow re-lock it.
Did you follow the instructions on Motorola webiste to unlock?
Click to expand...
Click to collapse
Yes i think the problem is in the way i am returning to stock.
I found a thread with here in XDA last night were called "Firmware restock and more 4.4.2
but instead of using the batch file i oped them up in a text editor and run every line manually to see what the console answers after each command.
i downloaded the stock rom according to my country and carrie and simply rpelaced the files but i think the checksum did not match and thats why i was getting the denied message when doing this
%fastboot% flash system system.img_sparsechunk1
%fastboot% flash system system.img_sparsechunk2
%fastboot% flash system system.img_sparsechunk3
I'm going to rename my country stock rom xml file to match the original xml file and see

Xcarab said:
Yes i think the problem is in the way i am returning to stock.
I found a thread with here in XDA last night were called "Firmware restock and more 4.4.2
but instead of using the batch file i oped them up in a text editor and run every line manually to see what the console answers after each command.
i downloaded the stock rom according to my country and carrie and simply rpelaced the files but i think the checksum did not match and thats why i was getting the denied message when doing this
%fastboot% flash system system.img_sparsechunk1
%fastboot% flash system system.img_sparsechunk2
%fastboot% flash system system.img_sparsechunk3
I'm going to rename my country stock rom xml file to match the original xml file and see
Click to expand...
Click to collapse
Buddy be careful when you go to do all this "stuff" :good:
Try to help you with Moto Tool by Alonosoch in Android Original Development section

Thank you Denzel
denzel09 said:
Buddy be careful when you go to do all this "stuff" :good:
Try to help you with Moto Tool by Alonosoch in Android Original Development section
Click to expand...
Click to collapse
"Man on Fire"
I called in sick for work already.. have to be at this all day.. so i will try everything and wont stop untill it is fixed.
Following the step by step instructions at: http://forum.xda-developers.com/showthread.php?t=2542219&highlight=sparsechunk

Xcarab said:
"Man on Fire"
I called in sick for work already.. have to be at this all day.. so i will try everything and wont stop untill it is fixed.
Following the step by step instructions at: http://forum.xda-developers.com/showthread.php?p=51155548
Click to expand...
Click to collapse
When I restored Stock, in the zip file I downloaded (en version) instead of:
system.img_sparsechunk1
system.img_sparsechunk2
system.img_sparsechunk3
there were
system.img_sparsechunk0
system.img_sparsechunk1
system.img_sparsechunk2
so I had to edit the prompt commands to match the file names.
May you're facing the same issue?
Try to auto-complete commands witht the tab key, it helps you not to give the wrong imputs

Ok, do you tried the Alonsoch tool? Read carefully the op, there is your "sparsechunk" problem and how fix it.
http://forum.xda-developers.com/showthread.php?t=2635706

Thank you Landrea and Denzel
Yes Landrea, you were absolutely right the file names did not match.. i typed in the propper names and i was able to finish the whole process
Now i'm waiting for it to boot...
Finger crossed.
Thanks a lot to both of you.. You Rock!

:victory: :victory: :victory: :victory: :victory: :victory: :victory:

Xcarab said:
Yes Landrea, you were absolutely right the file names did not match.. i typed in the propper names and i was able to finish the whole process
Now i'm waiting for it to boot...
Finger crossed.
Thanks a lot to both of you.. You Rock!
Click to expand...
Click to collapse
You're very welcome
Keep us updated!
P.S. you could hit the thanks button sometimes <3

Original Post
The original Post was about being stucked at CUSTOM ROM LOGO... since this happened with different roms i decided to go back to stock rom and then the post went in this direction.. will try again tonigh to install a custom rom.. SLIM kat looks just like my style so will go for that again
Thanlk you everyone for the quick responses and this will continue...

Xcarab said:
The original Post was about being stucked at CUSTOM ROM LOGO... since this happened with different roms i decided to go back to stock rom and then the post went in this direction.. will try again tonigh to install a custom rom.. SLIM kat looks just like my style so will go for that again
Thanlk you everyone for the quick responses and this will continue...
Click to expand...
Click to collapse
I think the reason you were being stuck at the ROM logo is because you didn't unlock your phone before you tried all this..
So.. hopefully you can restore your phone back to stock rom and start over..
good luck

neozen21 said:
I think the reason you were being stuck at the ROM logo is because you didn't unlock your phone before you tried all this..
So.. hopefully you can restore your phone back to stock rom and start over..
good luck
Click to expand...
Click to collapse
My boost mobile phone is unlock but I still can't pass the cm logo or PAC man logo or the slimkat logo ... I done try 3 recoveries but I still get the same problem. I'm currently using philz recovery BC its the only one it would let me make a complete back up without any issues.. I try twrp and cwm but I get back up failed when it gets to the "backing up data section". Anyone else get the same issue? And about the ROM getting stuck at the logo any one have any idea what could it be????? I hate stock Roms even though its not that bad since its rooted lol...
Sent from my XT1031 using XDA Premium 4 mobile app

jglm4u said:
My boost mobile phone is unlock but I still can't pass the cm logo or PAC man logo or the slimkat logo ... I done try 3 recoveries but I still get the same problem. I'm currently using philz recovery BC its the only one it would let me make a complete back up without any issues.. I try twrp and cwm but I get back up failed when it gets to the "backing up data section". Anyone else get the same issue? And about the ROM getting stuck at the logo any one have any idea what could it be????? I hate stock Roms even though its not that bad since its rooted lol...
Sent from my XT1031 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Going to post all the commands i used to get it to work
E:\Moto G\Minimal ADB and Fastboot>mfastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
E:\Moto G\Minimal ADB and Fastboot>fastboot boot TWRP-2.6.3.3-falcon.img
downloading 'boot.img'...
OKAY [ 0.296s]
booting...
OKAY [ 0.508s]
finished. total time: 0.807s
E:\Moto G\Minimal ADB and Fastboot>mfastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
E:\Moto G\Minimal ADB and Fastboot>fastboot flash recovery TWRP-2.6.3.3-falcon.i
mg
target reported max download size of 536870912 bytes
sending 'recovery' (8678 KB)...
OKAY [ 0.306s]
writing 'recovery'...
OKAY [ 0.522s]
This i used to send the rom, gapps and superuser to the media card so it was available to choose on twrp
E:\Moto G\Minimal ADB and Fastboot>adb push slim_unofficial_falcon_02-02-2014.zi
p /data/media/0
3769 KB/s (193672391 bytes in 50.180s)
E:\Moto G\Minimal ADB and Fastboot>adb push Slim_minimal_gapps.4.4.2.build.3.x.z
ip /data/media/0
3576 KB/s (62215309 bytes in 16.986s)
After that.. did
.- Do the wipes (cache/data/dalvik cache).
4.- Format system.
5.- Install the rom.
6.- Enjoy!
now on step 4, you will have to
Touch Wipe
Advanced Wipe
Check System
Then Swipe

Xcarab said:
Going to post all the commands i used to get it to work
E:\Moto G\Minimal ADB and Fastboot>mfastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
E:\Moto G\Minimal ADB and Fastboot>fastboot boot TWRP-2.6.3.3-falcon.img
downloading 'boot.img'...
OKAY [ 0.296s]
booting...
OKAY [ 0.508s]
finished. total time: 0.807s
E:\Moto G\Minimal ADB and Fastboot>mfastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
E:\Moto G\Minimal ADB and Fastboot>fastboot flash recovery TWRP-2.6.3.3-falcon.i
mg
target reported max download size of 536870912 bytes
sending 'recovery' (8678 KB)...
OKAY [ 0.306s]
writing 'recovery'...
OKAY [ 0.522s]
This i used to send the rom, gapps and superuser to the media card so it was available to choose on twrp
E:\Moto G\Minimal ADB and Fastboot>adb push slim_unofficial_falcon_02-02-2014.zi
p /data/media/0
3769 KB/s (193672391 bytes in 50.180s)
E:\Moto G\Minimal ADB and Fastboot>adb push Slim_minimal_gapps.4.4.2.build.3.x.z
ip /data/media/0
3576 KB/s (62215309 bytes in 16.986s)
After that.. did
.- Do the wipes (cache/data/dalvik cache).
4.- Format system.
5.- Install the rom.
6.- Enjoy!
now on step 4, you will have to
Touch Wipe
Advanced Wipe
Check System
Then Swipe
Click to expand...
Click to collapse
I will try this after work man thanks tho..hopefully it works for me 2
Sent from my XT1031 using XDA Premium 4 mobile app

Bricked my Honor 6 H60-L04 Indian variant while trying to install .zip files.

I recently upgraded my phone to EMUI 2.3 to EMUI 3.1 (Android lollipop 5.1), and installed CWM and rooted it. Two days ago I have downloaded cerebus app from Rom manager app and it installed by rebooting into recovery. Then a couple of minutes after rebooting the phone keep on crashing and shutting down randomly and when I tried to reboot it won't reboot but stuck for sometime at the Honor logo and since then I've tried every possible flashing and resetting I found here on XDA.
I still have access to fastboot and that is how I am able to flash ROM s and when I am trying to use the three button method it is stopping at 90 %. I couldn't even access it if my phone is not connected to my PC.
Now I've exhausted all the procedures in here and some other sites.
Somebody please suggest me something, help me.
Thank you.

Follow these steps to get it back to stock:
Download your phone's latest firmware and extract system.img, boot.img, recovery.img, cust.img from UPDATE.APP using Huawei Update Extractor tool.
Boot into bootloader mode by switching off the phone then pressing only the Vol DOWN button, and connecting it to PC simultaneously.
Flash recovery first, using this command.
Code:
fastboot flash recovery recovery.img
Flash all other extracted files similarly firing these commands.
Code:
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash system system.img
After doing this put that very UPDATE.APP from which you extracted the files in dload folder of your external SDCARD.
Switch off your phone, and press Vol UP + Vol DOWN + Power button simultaneously.
Your device will now get to the full stock firmware.
NOTE: If the manual flashing doesn't works or you get any errors, then first try only the force update method, i.e Putting the UPDATE.APP from which you extracted the files in dload folder of your external SDCARD and pressing Vol UP + Vol DOWN + Power button simultaneously after switching off your phone.

Thanks Brother.
I have tried to flash Recovery through fastboot and the following error is occurring
F:\Android\Honor root\H60-L04>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (13780 KB)...
OKAY [ 1.451s]
writing 'recovery'...
FAILED (status read failed (Too many links))
finished. total time: 1.482s
Thanks again for helping me out,.

yessasikiran said:
I have tried to flash Recovery through fastboot and the following error is occurring
F:\Android\Honor root\H60-L04>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (13780 KB)...
OKAY [ 1.451s]
writing 'recovery'...
FAILED (status read failed (Too many links))
finished. total time: 1.482s
Thanks again for helping me out,.
Click to expand...
Click to collapse
I have the same problem with a H60-L12.
I noticed, that I get that error when I try to flash a boot.img from a different EMUI version pack.
In my case, the phone had EMUI3.0 and I can write any of the EMUI3.0 boot.img's, but cannot write a boot.img from an EMUI 3.1 or EMUI4.0 update.app

yessasikiran said:
I have tried to flash Recovery through fastboot and the following error is occurring
F:\Android\Honor root\H60-L04>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (13780 KB)...
OKAY [ 1.451s]
writing 'recovery'...
FAILED (status read failed (Too many links))
finished. total time: 1.482s
Thanks again for helping me out,.
Click to expand...
Click to collapse
Which recovery image are you using?
Sent from my PLK-L01 using Tapatalk

yessasikiran said:
I have tried to flash Recovery through fastboot and the following error is occurring
F:\Android\Honor root\H60-L04>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (13780 KB)...
OKAY [ 1.451s]
writing 'recovery'...
FAILED (status read failed (Too many links))
finished. total time: 1.482s
Thanks again for helping me out,.
Click to expand...
Click to collapse
Try
download adb.zip
http://www.mediafire.com/download/o5ruw752ked884u/adb+H60.zip
extract adb.zip
download
TWRP_2.8.7.0_EN_EMUI_4.0_v4.img
https://drive.google.com/drive/folders/0By4NGNfKPDLBMW9jTy1fOHBGTm8?tid=0By4NGNfKPDLBQTZ2S0licGhjNmc
copy TWRP in adb folder
put the devices in fastboot mode
run cmd.exe as administrator and type this command
fastboot devices
fastboot flash recovery TWRP_2.8.7.0_EN_EMUI_4.0_v4.img
fastboot reboot
If does not work, try to reinstall HiSuite or install the lastet version
http://consumer.huawei.com/minisite/HiSuite_en/index.html
Nexus H791 using Tapatalk

Thnks you for replying so quickly.
I'm using "Honor 6_Firmware_H60-L04_Android 6.0_EMUI 4.0_C675B822_India_Flipkart India"
which is the latest stock firmware for Honor 6 H60-L04.
I have tried to force update with the thee button method and it worked (completed 100%)but unfortunately the phone is now in bootloop. This definitely made the phone a little better but once it got to the EMUI update screen its restarting again.
Thanks again man I though nobody would reply for this. its been so long since ive posted this.

Thank you for replying so quickly.
I'm using "Honor 6_Firmware_H60-L04_Android 6.0_EMUI 4.0_C675B822_India_Flipkart India"
which is the latest stock firmware for Honor 6 H60-L04.
I have tried to force update with the thee button method and it worked (completed 100%)but unfortunately the phone is now in bootloop. This definitely made the phone a little better but once it got to the EMUI update screen its restarting again.
Thanks again man I though nobody would reply for this. its been so long since ive posted this.

Thanks man, I'll get back to you once ive done this.
Nah man, Same thing again.
F:\Android\Honor root\TWRP>fastboot flash recovery TWRP_2.8.7.0_EN_EMUI_4.0_v4.i
mg
target reported max download size of 471859200 bytes
sending 'recovery' (14468 KB)...
OKAY [ 1.507s]
writing 'recovery'...
FAILED (status read failed (Too many links))
finished. total time: 1.535s
Thank you for guiding me through.

yessasikiran said:
Thank you for replying so quickly.
I'm using "Honor 6_Firmware_H60-L04_Android 6.0_EMUI 4.0_C675B822_India_Flipkart India"
which is the latest stock firmware for Honor 6 H60-L04.
I have tried to force update with the thee button method and it worked (completed 100%)but unfortunately the phone is now in bootloop. This definitely made the phone a little better but once it got to the EMUI update screen its restarting again.
Thanks again man I though nobody would reply for this. its been so long since ive posted this.
Click to expand...
Click to collapse
You have to use that last Lollipop package which you were on before, try the three button method with that and report.

DigiGoon said:
You have to use that last Lollipop package which you were on before, try the three button method with that and report.
Click to expand...
Click to collapse
Hey,
Yeah man I'll do that now and will get bact to you.
Thanks man

DigiGoon said:
You have to use that last Lollipop package which you were on before, try the three button method with that and report.
Click to expand...
Click to collapse
Yeah man, I've tried to flash recovery of the last Lollipop Rom and still the same message FAILED (status read failed (Too many links)).
Is there any other way that we can try to unbrick the device?
Thank you man.

yessasikiran said:
Yeah man, I've tried to flash recovery of the last Lollipop Rom and still the same message FAILED (status read failed (Too many links)).
Is there any other way that we can try to unbrick the device?
Thank you man.
Click to expand...
Click to collapse
Have you used Honor Multitool? http://forum.xda-developers.com/honor-7/general/honor-7-multi-tool-t3281176

zinko_pt said:
Have you used Honor Multitool? http://forum.xda-developers.com/honor-7/general/honor-7-multi-tool-t3281176
Click to expand...
Click to collapse
Yes sir,
Same output and stopping after trying to flash recovery while using the in brick option.
Thank you.

yessasikiran said:
Yes sir,
Same output and stopping after trying to flash recovery while using the in brick option.
Thank you.
Click to expand...
Click to collapse
When you flashed manually, did you used the same IMG files from the last installed ROM?
You can´t extract and flash IMG files of a LP ROM in a last installed MM ROM and vice versa.

yessasikiran said:
I have tried to flash Recovery through fastboot and the following error is occurring
F:\Android\Honor root\H60-L04>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (13780 KB)...
OKAY [ 1.451s]
writing 'recovery'...
FAILED (status read failed (Too many links))
finished. total time: 1.482s
Thanks again for helping me out,.
Click to expand...
Click to collapse
bro type fastboot devices and check how many available devices it shows...if it shows more than 1 device then stop the other device...if thr is only device then try stopping adb.exe and fastboot.exe(if thr)....then again type command "fastboot devices"

yessasikiran said:
Yes sir,
Same output and stopping after trying to flash recovery while using the in brick option.
Thank you.
Click to expand...
Click to collapse
Try using the latest version of the developer ROM
chetan_dua said:
bro type fastboot devices and check how many available devices it shows...if it shows more than 1 device then stop the other device...if thr is only device then try stopping adb.exe and fastboot.exe(if thr)....then again type command "fastboot devices"
Click to expand...
Click to collapse
Check in task manager to see if you have adb.exe running. Stop all and try again.

Still bricked or have u fixed it yet?

goldfinv said:
Try using the latest version of the developer ROM
Check in task manager to see if you have adb.exe running. Stop all and try again.
Click to expand...
Click to collapse
bro i was trying to help another person that was solution according to me for him
Sry if it looks like question...