I've got a Mate7 (MT7-L09) that I bought used, from the look of it, it's been previously unlocked (which is good, since I've been unable to get an unlock code from Huawei for it), and is running the latest L09 factory rom (See attached screen shot, yep, says unlocked.)
Unfortunately, when I try to flash CWM, I get the following:
[email protected]:~/android-sdk-linux/platform-tools$ sudo ./fastboot flash recovery recovery_h60.img
target reported max download size of 471859200 bytes
sending 'recovery' (9386 KB)...
OKAY [ 1.790s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 1.795s
Attempting to flash the stock recovery works just fine. I've downloaded a couple of different copies of CWM and they all fail with the same error. I've also tried under Windows with the same error.
I've also tried flashing the factory image from the SD card to return the phone to 'stock' before again trying to flash CWM, this also did not fix the problem.
Any ideas?
Thanks!
Justin
Turbo4V said:
I've got a Mate7 (MT7-L09) that I bought used, from the look of it, it's been previously unlocked (which is good, since I've been unable to get an unlock code from Huawei for it), and is running the latest L09 factory rom (See attached screen shot, yep, says unlocked.)
Unfortunately, when I try to flash CWM, I get the following:
[email protected]:~/android-sdk-linux/platform-tools$ sudo ./fastboot flash recovery recovery_h60.img
target reported max download size of 471859200 bytes
sending 'recovery' (9386 KB)...
OKAY [ 1.790s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 1.795s
Attempting to flash the stock recovery works just fine. I've downloaded a couple of different copies of CWM and they all fail with the same error. I've also tried under Windows with the same error.
I've also tried flashing the factory image from the SD card to return the phone to 'stock' before again trying to flash CWM, this also did not fix the problem.
Any ideas?
Thanks!
Justin
Click to expand...
Click to collapse
man who told u flash that crap cwm which is not even for mate 7 ???
where did u get that crap.. thats for honor 6 or p7..
check mate 7 forum (general) and ull find PROPER recovery cwm for mate 7 !
i think i gave u lots of clues..
And if u tried to flash other CWMs ten u have old flash adb fastboot files..
u need latest ones supports higher sizes
Simona Simmy said:
man who told u flash that crap cwm which is not even for mate 7 ???
where did u get that crap.. thats for honor 6 or p7..
check mate 7 forum (general) and ull find PROPER recovery cwm for recovery_h60.imgmate 7 !
i think i gave u lots of clues..
And if u tried to flash other CWMs ten u have old flash adb fastboot files..
u need latest ones supports higher sizes
Click to expand...
Click to collapse
This is actually a recovery for the HAM7, not the Honor6/P7. Recovery_h60.img is just what the recovery was initially called (check the thread http://forum.xda-developers.com/mat...custom-recovery-tool-mt7-l10-l10-mt7-t3022424). I got the CWM file from that thread.
I've also tried the updated version posted in the same thread (MT7_CWM_CN_EN.img) with the same results.
sudo ./fastboot flash recovery MT7_CWM_CN_EN.img
target reported max download size of 471859200 bytes
sending 'recovery' (9390 KB)...
OKAY [ 1.800s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 1.805s
Finally, I have the latest adb/fastboot from the latest android SDK (for linux). As I mentioned, I also tried it under Windows with the included adb/fastboot with no differences.
Thanks for you help!
Turbo4V said:
This is actually a recovery for the HAM7, not the Honor6/P7. Recovery_h60.img is just what the recovery was initially called (check the thread http://forum.xda-developers.com/mat...custom-recovery-tool-mt7-l10-l10-mt7-t3022424). I got the CWM file from that thread.
I've also tried the updated version posted in the same thread (MT7_CWM_CN_EN.img) with the same results.
sudo ./fastboot flash recovery MT7_CWM_CN_EN.img
target reported max download size of 471859200 bytes
sending 'recovery' (9390 KB)...
OKAY [ 1.800s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 1.805s
Finally, I have the latest adb/fastboot from the latest android SDK (for linux). As I mentioned, I also tried it under Windows with the included adb/fastboot with no differences.
Thanks for you help!
Click to expand...
Click to collapse
jeezz
download thiiis alright ? and REPORT success ! To ME
https://www.sendspace.com/file/u5jkys
Simona Simmy said:
jeezz
download thiiis alright ? and REPORT success ! To ME
https://www.sendspace.com/file/u5jkys
Click to expand...
Click to collapse
I just tried flashing your file, and get the same result:
sudo ./fastboot flash recovery MATE7_CWM.img
target reported max download size of 471859200 bytes
sending 'recovery' (9390 KB)...
OKAY [ 1.790s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 1.795s
Just for grins, I compared your file to the one that I was flashing before, and they are identical.
diff -s MATE7_CWM.img MT7_CWM_CN_EN.img
Files MATE7_CWM.img and MT7_CWM_CN_EN.img are identical
Any more ideas?
Thanks!
Jsutin
Turbo4V said:
I just tried flashing your file, and get the same result:
sudo ./fastboot flash recovery MATE7_CWM.img
target reported max download size of 471859200 bytes
sending 'recovery' (9390 KB)...
OKAY [ 1.790s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 1.795s
Just for grins, I compared your file to the one that I was flashing before, and they are identical.
diff -s MATE7_CWM.img MT7_CWM_CN_EN.img
Files MATE7_CWM.img and MT7_CWM_CN_EN.img are identical
Any more ideas?
Thanks!
Jsutin
Click to expand...
Click to collapse
U still want idea ?? u have NOT get it already?? where did u purchased it from ?? and u already thinking WHY someone got rid of it ??
Does the phone normally working ???
Did u install huawei latest drivers?
Simona Simmy said:
U still want idea ?? u have NOT get it already?? where did u purchased it from ?? and u already thinking WHY someone got rid of it ??
Does the phone normally working ???
Did u install huawei latest drivers?
Click to expand...
Click to collapse
Purchased from Swappa, device works perfectly besides not being able to flash recovery.
I've been able to put the stock Huawei firmware on an SD card and flash that. (127)
I suppose you could be correct, maybe there's something wrong with the device, but that seems unlikely given that everything else works. One thing I'm thinking is that the phone is not actually unlocked (even though it says it is on the recovery screen). Wish I could get an unlock code for this thing to try re-locking and unlocking it.
Thanks for your help.
Turbo4V said:
Purchased from Swappa, device works perfectly besides not being able to flash recovery.
I've been able to put the stock Huawei firmware on an SD card and flash that. (127)
I suppose you could be correct, maybe there's something wrong with the device, but that seems unlikely given that everything else works. One thing I'm thinking is that the phone is not actually unlocked (even though it says it is on the recovery screen). Wish I could get an unlock code for this thing to try re-locking and unlocking it.
Thanks for your help.
Click to expand...
Click to collapse
I posted already procedure how to unlock phone..
U need tools for it ..
But now am going to bed.. so check out mine threads or posts .. it is here..
Simona Simmy said:
I posted already procedure how to unlock phone..
U need tools for it ..
But now am going to bed.. so check out mine threads or posts .. it is here..
Click to expand...
Click to collapse
Thanks, I've tried using the tools, and the code generated ends up not working on the Huawei web site. (See attached). Additionally, I've tried requesting the code from Huawei, and they say that unlocking is not available for the L09
From Huawei:
Huawei Dear user:
Hello, Thank you for using Huawei's products. MT7-L09 is currently not supported by the application unlock code if you want to brush Root or third-party systems, you can go online to search to see if there is a corresponding method. After the phone Root, though not affect the warranty, but if it is due to appear Root performance was a result of failure or system problems may affect your warranty love machine, specifically whether the warranty is to be detected by the service network, then you careful consideration! THX!
Huawei Customer Service Center
Thanks again for your help, just wanted others to see the process incase they were encountering similar problems.
Justin
Turbo4V said:
Thanks, I've tried using the tools, and the code generated ends up not working on the Huawei web site. (See attached). Additionally, I've tried requesting the code from Huawei, and they say that unlocking is not available for
Click to expand...
Click to collapse
You can try Y300-100 or something like or try to relock
Simona Simmy said:
You can try Y300-100 or something like or try to relock
Click to expand...
Click to collapse
Tried that one too (and a few other models), same message.
Thanks,
Justin
Turbo4V said:
Tried that one too (and a few other models), same message.
Thanks,
Justin
Click to expand...
Click to collapse
only one thing ..
get vroot : http://forum.xda-developers.com/showthread.php?t=2434453
root it ...
download flashy : https://play.google.com/store/apps/details?id=com.cgollner.flashify
flash super su (first copy it into your sc card)
delete vroot ..
download install su :https://play.google.com/store/apps/details?id=eu.chainfire.supersu
Simona Simmy said:
You can try Y300-100 or something like or try to relock
Click to expand...
Click to collapse
Thanks again for the ideas, but that root method looks a bit sketchy (malware etc). I guess I'll just leave things 'as-is' for now, hopefully I'll be able to figure out the whole lock/relock thing one day!
Justin
Turbo4V said:
Thanks again for the ideas, but that root method looks a bit sketchy (malware etc). I guess I'll just leave things 'as-is' for now, hopefully I'll be able to figure out the whole lock/relock thing one day!
Justin
Click to expand...
Click to collapse
doont worry .. just root it .. i had it and all was ok . .u will have it just for 5-10 mins.. by that time nothing will happen.
forgot to mention.. after installing flashy flash recovery (CWM) that flashy provides download and flash..
then after installing CWM go there and flash super su
Have the same problem and my Mate7 TL7-09 also has unlocked bootloader (verified with fastboot oem getinfo-bootloader) just cannot get CWM to flash.
djpharoah said:
Have the same problem and my Mate7 TL7-09 also has unlocked bootloader (verified with fastboot oem getinfo-bootloader) just cannot get CWM to flash.
Click to expand...
Click to collapse
Here.... the same problem
Use FLASHIFY that's how I bounce back and forth with recoveries.
Turbo4V said:
I just tried flashing your file, and get the same result:
sudo ./fastboot flash recovery MATE7_CWM.img
target reported max download size of 471859200 bytes
sending 'recovery' (9390 KB)...
OKAY [ 1.790s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 1.795s
Just for grins, I compared your file to the one that I was flashing before, and they are identical.
diff -s MATE7_CWM.img MT7_CWM_CN_EN.img
Files MATE7_CWM.img and MT7_CWM_CN_EN.img are identical
Any more ideas?
Thanks!
Jsutin
Click to expand...
Click to collapse
Sounds like your boot loader is still locked or has be relocked again. That's the error you get when boot loader is locked and fast boot can't flash to the partition. Hence the "remote failure" error you're getting.
---------- Post added at 01:38 PM ---------- Previous post was at 01:34 PM ----------
Simona Simmy said:
doont worry .. just root it .. i had it and all was ok . .u will have it just for 5-10 mins.. by that time nothing will happen.
forgot to mention.. after installing flashy flash recovery (CWM) that flashy provides download and flash..
then after installing CWM go there and flash super su
Click to expand...
Click to collapse
Regardless how long you think you may have "vroot" on tour device , there's no telling what type of malware will remain hidden on it. Or what its communicating back to where ever
Related
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
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...
I executed fastboot -i 0x2A96 oem unlock before flashing. I also checked fastboot getvar unlocked so result is following.
>fastboot getvar unlocked
unlocked:
finished. total time: 0.002s*
And one more thing when I flashed cache , userdata , recovery , boot. It is all fine, there is no error. But this error occurs only when i tried to flash system. My Phone was stopped working due some decryption error and internal memory is showing as 0Mb in TWRP. I had followed my threads but no luck.
>fastboot -i 0x2A96 flash system system.img
target reported max download size of 268435456 bytes
erasing 'system'...
OKAY [ 0.018s]
sending sparse 'system' 1/4 (261218 KB)...
OKAY [ 8.737s]
writing 'system' 1/4...
**FAILED (remote: flash write failure)**
finished. total time: 9.167s
Might be Because Of Corrupted Data Partion.
atulsam said:
I executed fastboot -i 0x2A96 oem unlock before flashing. I also checked fastboot getvar unlocked so result is following.
>fastboot getvar unlocked
unlocked:
finished. total time: 0.002s*
And one more thing when I flashed cache , userdata , recovery , boot. It is all fine, there is no error. But this error occurs only when i tried to flash system. My Phone was stopped working due some decryption error and internal memory is showing as 0Mb in TWRP. I had followed my threads but no luck.
>fastboot -i 0x2A96 flash system system.img
target reported max download size of 268435456 bytes
erasing 'system'...
OKAY [ 0.018s]
sending sparse 'system' 1/4 (261218 KB)...
OKAY [ 8.737s]
writing 'system' 1/4...
**FAILED (remote: flash write failure)**
finished. total time: 9.167s
Click to expand...
Click to collapse
It Might Possible That Your Data Partition Has Been Corrupted. Download The Official Cynogen OS Zip. Extract it. In That Look For Data. And In same Folder, Press Shift&Right Click in empty Sapce And Open Command window Here. Connect Your Device In Fasboot Mode. Flash That Data Using command. And then Flash System.img by Normal Method. Hope It will Worked For Yu.
Please see the image attached.
Animdk said:
It Might Possible That Your Data Partition Has Been Corrupted. Download The Official Cynogen OS Zip. Extract it. In That Look For Data. And In same Folder, Press Shift&Right Click in empty Sapce And Open Command window Here. Connect Your Device In Fasboot Mode. Flash That Data Using command. And then Flash System.img by Normal Method. Hope It will Worked For Yu.
Click to expand...
Click to collapse
Please see the following image attached which is shared on drive.
Code:
https://drive.google.com/file/d/0B8Dudx72Yu9iamFLUzZOY1Y1TjQ/view?usp=sharing
atulsam said:
Please see the following image attached which is shared on drive.
Code:
https://drive.google.com/file/d/0B8Dudx72Yu9iamFLUzZOY1Y1TjQ/view?usp=sharing
Click to expand...
Click to collapse
Try Out My Method It Should Be Work.
And rather than Using Original USB Cabel, Use Good Original cabel. Sometimes Original USB Become Loose.
It may not be USB problem.
Animdk said:
Try Out My Method It Should Be Work.
And rather than Using Original USB Cabel, Use Good Original cabel. Sometimes Original USB Become Loose.
Click to expand...
Click to collapse
I am using amazon basics cable , this is not usb problem because data is flashing properly but system is not. And Internal memory showing as 0 Mb in TWRP, but SdCard is showing as it is.
I downloaded official tool kit and OS . I tried with two different img but result is same for both.
atulsam said:
I am using amazon basics cable , this is not usb problem because data is flashing properly but system is not. And Internal memory showing as 0 Mb in TWRP, but SdCard is showing as it is.
I downloaded official tool kit and OS . I tried with two different img but result is same for both.
Click to expand...
Click to collapse
Do Yu Tried For The Flasing Of Only Data Partition, It Might Fix Your Problem.....Otherwise, Sorry Bro....I don't Have Any Further Knowledge About This....
Animdk said:
Do Yu Tried For The Flasing Of Only Data Partition, It Might Fix Your Problem.....Otherwise, Sorry Bro....I don't Have Any Further Knowledge About This....
Click to expand...
Click to collapse
Yes I have tried that , data is flashing successfully. Since there is no system flashing so cant start my phone.
I am having the exact same problem
how did you resolve the issue
BOTDeveloper said:
I am having the exact same problem
how did you resolve the issue
Click to expand...
Click to collapse
Sorry, I did not solve yet.
How did it happened?? I'm scared if i overcome this. Cuz recently i unbricked my device from dead hardbrick
exact same issue
atulsam said:
Sorry, I did not solve yet.
Click to expand...
Click to collapse
exact same problem here please update here if you abe to fix it.
Same problem.............. Is there no one from this group to help us........... :'(
Same Probelm
Please someone help , if you have resolved the same . TIA
Guys ..ur problem solved ? Post reply
@ Heartstoler1991 - Not yet .. Please help someone ..
Same problem. Please share the solution if anyone solved it.
I found a pretty easy method but it doesn't let me post the link so send a mail to [email protected] and I give you the link!
Edit: it finally let me post it: https://forum.xda-developers.com/yu-yuphoria/help/bricked-t3174710
Good luck mates
Razor10707 said:
I found a pretty easy method but it doesn't let me post the link so send a mail to [email protected] and I give you the link!
Edit: it finally let me post it: https://forum.xda-developers.com/yu-yuphoria/help/bricked-t3174710
Good luck mates
Click to expand...
Click to collapse
Tried this method already.
Doesn't work, it gives the same exact error.
I have same problem
help me any body any solution
EDIT: Guys it worked. Some weird **** happened first, keyboard wasn't working on stock rom and everything was buggy but after an update with HiSuite and a factory reset everything works fine. Thank you for all your support.
I bricked my Honor 8 (FRD-L09) while trying to go back to stock rom. I can only acces eRecovery and Fastboot, when I try to access normal recovery, the screen just freezes at "Your device is booting now". After reading multiple guides, I tried unbricking with the Huawei Multitool but I always get these errors:
sending 'boot' (15464 KB)...
OKAY [ 0.334s]
writing 'boot'...
OKAY [ 0.371s]
finished. total time: 0.710s
target reported max download size of 471859200 bytes
sending 'cust' (433554 KB)...
OKAY [ 9.343s]
writing 'cust'...
FAILED (remote: partition error)
finished. total time: 9.358s
target reported max download size of 471859200 bytes
sending 'recovery' (36996 KB)...
OKAY [ 0.794s]
writing 'recovery'...
OKAY [ 0.883s]
finished. total time: 1.682s
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (435393 KB)...
OKAY [ 10.280s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 10.327s
I'm desperate and I don't know what to do.
EDIT: I HAVE MANAGED TO INSTALL RR BUT STILL CAN'T GO BACK TO STOCK.
Rommco05 said:
Hi, what about twrp u loos access?
Click to expand...
Click to collapse
I have regained access to twrp. I have installed a custom rom, but still can't install stock rom.
Rommco05 said:
Your hole model number is? U try yo flash stock rom via twrp?
Click to expand...
Click to collapse
FRD-L09. I haven't flashed stock rom via TWRP. I tried the huawei extractor method right now, I'm probably doing something wrong, I'll look more into it . I'm calm now that I managed to install a custom rom.
Rommco05 said:
Ok, so if still without luck try to download full stock fw B360 or B381 (2 zips)
Click to expand...
Click to collapse
Ok.. I will try that. My phone is stuck at "your device is booting up" screen after flashing stock recovery.
Note that there is also recovery2 in first update.zip when you extract it via Huawei Multitool. Thats probably why recovery never boots up, it's not all. Try to send the first basic ones - boot, recovery, recovery2, erecovery, and so on (don't exactly remember which). Then you should be fine to dload or flash the rest through fastboot (if possible). And remember to always use full-ota-mf-pv version of software (like FRD-L09C432B381) with about 2.37 GB total (2 zip files).
Rommco05 said:
You can flash back twrp?
Click to expand...
Click to collapse
Yes, I can.
So, did it work?!
PalakMi said:
So, did it work?!
Click to expand...
Click to collapse
I'm at work now. I'll try after a few hours.
Radu Florin said:
I'm at work now. I'll try after a few hours.
Click to expand...
Click to collapse
Good luck, I hope it works after all
Guys it worked. Some weird **** happened first, keyboard wasn't working on stock rom and everything was buggy but after an update with HiSuite and a factory reset everything works fine. Thank you for all your support.
Radu Florin said:
Guys it worked. Some weird **** happened first, keyboard wasn't working on stock rom and everything was buggy but after an update with HiSuite and a factory reset everything works fine. Thank you for all your support.
Click to expand...
Click to collapse
Great , your device is back :highfive:
Hi All,
I need some help please with (soft?) bricked Note 7 pro. I have the global version and installed e. foundation ROM which is a fork of LineageOS. This was working well until I loaded the latest version last week. Now the phone seems to be softbricked.
I can get into fastboot. I have downloaded TWRP violet and when I run "fastboot flash recovery twrp-3.3.0-0-violet.img" I get:
target reported max download size of 536870912 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.723s]
writing 'recovery'...
OKAY [ 0.370s]
finished. total time: 2.093s
However when I try to boot into that recovery it wont work. (I just see the "Redmi by Xiaomi" screen with the "unlocked" detail at the bottom.
I also tried to run "fastboot boot twrp-3.3.0-0-violet.img" but that leads to a "system has been destroyed" message.
I downloaded the Mi unlock tool and tried to unlock again, just in case, but that tool reported that the phone is unlocked already.
I should point out that I get the same result with twrp-3.3.1-0-violet.img
Does anyone have any suggestions as to what I can try next? I am reluctant to remove the back from the phone.
Thanks
jimmy987654321 said:
Hi All,
I need some help please with (soft?) bricked Note 7 pro. I have the global version and installed e. foundation ROM which is a fork of LineageOS. This was working well until I loaded the latest version last week. Now the phone seems to be softbricked.
I can get into fastboot. I have downloaded TWRP violet and when I run "fastboot flash recovery twrp-3.3.0-0-violet.img" I get:
target reported max download size of 536870912 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.723s]
writing 'recovery'...
OKAY [ 0.370s]
finished. total time: 2.093s
However when I try to boot into that recovery it wont work. (I just see the "Redmi by Xiaomi" screen with the "unlocked" detail at the bottom.
I also tried to run "fastboot boot twrp-3.3.0-0-violet.img" but that leads to a "system has been destroyed" message.
I downloaded the Mi unlock tool and tried to unlock again, just in case, but that tool reported that the phone is unlocked already.
I should point out that I get the same result with twrp-3.3.1-0-violet.img
Does anyone have any suggestions as to what I can try next? I am reluctant to remove the back from the phone.
Thanks
Click to expand...
Click to collapse
Use Peter's twrp or flash fastboot rom with miflash
urstrulynaveen said:
Use Peter's twrp or flash fastboot rom with miflash
Click to expand...
Click to collapse
Thanks. Ive never heard of Peters TWRP so I'll try that next. Cheers.
jimmy987654321 said:
Thanks. Ive never heard of Peters TWRP so I'll try that next. Cheers.
Click to expand...
Click to collapse
Thanks urstrulynaveen, that worked a treat. I'm very grateful. All back up and running now.
jimmy987654321 said:
Thanks urstrulynaveen, that worked a treat. I'm very grateful. All back up and running now.
Click to expand...
Click to collapse
Were you able to lock your bootloader