Related
Hi,
My wife just got a new phone and gave up her old XT925 so I thought I would try to put CM or SlimKat on it and let my daughter play around with it. But I'm having trouble putting a custom recovery on it. I've unlocked the bootloader. I've used fastboot to write the recovery image...but when I try to reboot directly into recovery so the binary update can complete, it pauses for a couple of minutes and then reboots the OS normally. If I try entering reovery after that, I end up with the dead android with a red exclamation point in him and "no command" written below.
The phone currently has 4.4.2 and System 181.46.3.XT925.RCI.en.CA. Am I out of luck with this device and stuck on 4.4.2?
Thanks!
What recovery did you try to flash ?
Use this one, it worked for me :
http://forum.xda-developers.com/showthread.php?t=2747535
Thanks. That one worked. I wonder why I had trouble with twrp.
Orionbell37 said:
What recovery did you try to flash ?
Use this one, it worked for me :
http://forum.xda-developers.com/showthread.php?t=2747535
Click to expand...
Click to collapse
pls update the link pls
Pausky said:
pls update the link pls
Click to expand...
Click to collapse
Its because you need to rename the stock recovery to .bak at the end of the file name. The stock recovery is getting in the way of you rebooting to TWRP or what ever custom recovery you are trying to use.
If you cant figure out how to do that or don't know where in system the stock recovery is just hit me up and ill give you the path to the file. After you rename the file just go back into fastboot and reflash the custom recovery and you should be able to reboot into TWRP or what ever custom recovery you want.
Today I accidently wiped my internal and external sd card from twrp recovery mode. I was on Lolipop 5.1.
As I wanted to install Cyanogenmod Rom I tried to reflash CWM recovery. Ater doing that I was not able to enter the twrp recovery anymore. I had accecs to the unlocked bootloader and tried to reinstall the boot, recovery and system via fastboot but without any success. The phone did not boot and I couldnt enter recovery mode anymrore.
Now I accidently flashed via fastboot a wrong boot and recovery firmware (4.1) and since that I can not even enter fastboot. The pictre shows where I am stuck. On the bootloader page it says:
Error
Func NO: 10 (FUNC_BOOT_RECOVERY)
Error NO: 2
Can somebody help me to repair my device? Its brandnew.
What can I do without a recovery, without a system and without fastboot.
Here is the picture:
hxxp://s21.postimg.org/tqzu1wlhj/IMG_0191.jpg
balpem said:
Today I accidently wiped my internal and external sd card from twrp recovery mode. I was on Lolipop 5.1.
As I wanted to install Cyanogenmod Rom I tried to reflash CWM recovery. Ater doing that I was not able to enter the twrp recovery anymore. I had accecs to the unlocked bootloader and tried to reinstall the boot, recovery and system via fastboot but without any success. The phone did not boot and I couldnt enter recovery mode anymrore.
Now I accidently flashed via fastboot a wrong boot and recovery firmware (4.1) and since that I can not even enter fastboot. The pictre shows where I am stuck. On the bootloader page it says:
Error
Func NO: 10 (FUNC_BOOT_RECOVERY)
Error NO: 2
Can somebody help me to repair my device? Its brandnew.
What can I do without a recovery, without a system and without fastboot.
Here is the picture:
hxxp://s21.postimg.org/tqzu1wlhj/IMG_0191.jpg
Click to expand...
Click to collapse
So (Vol-) + (Power) w/ usb plugged in doesn't bring it to recovery mode? Have you tried with HiSuite?
jfer671 said:
So (Vol-) + (Power) w/ usb plugged in doesn't bring it to recovery mode? Have you tried with HiSuite?
Click to expand...
Click to collapse
No because I had twrp recovery installed and tried to flash cwm over it. After that I had no recovery at all. But I made some progress now... I am able to flash the same newest twrp 2.8.7.0 recovery to the phone and I managed also to flash the 5.1 stock recovery. I flashed BOOT.img from 5.1 and SYSTEM.img from 5.1 and I got rid of the error in fastboot menu.
Stock recovery I can flash via installer_r24.4.1-windows from acbka.
http://forum.xda-developers.com/mate-7/orig-development/tool-android-4-4-5-1-pc-t3186984
And these two recoveries seems to be the only one that work on my phone....? Currently I have stock recovery installed and i put MT7-L09C900B324 on my sd card (dload/UPDATE.app) and did the three buttons rescue. It seemed to work but It stoped at 90% and still no luck. What am I doing wrong this time?
Hi Suite does not recognitze the phone. When I abort the istallation and reboot the phone starts with the Huawei Logo and goes black and starts to the Huawei logo and goes black and so on...
Here is a picture of where i am stuck at 90% right now, so close...:
hxxp://s13.postimg.org/p093toz5z/IMG_0192.jpg
SOLVED
After a 36 hour marathon my mate 7 is back and working. the trick was to flash the stock recovery for all Lollipop versions wich can be foudn here: http://forum.xda-developers.com/mat...8-7-0-mate7-android-5-1-t3156779/post61958212 via linux. I somehow seem to have had trouble over wndows.
And after that do the three button rescue with the newest B 324 firmware which I have had installed before I destroyed my OS..
and my camera is now running normaly which was the initial reason i tried to install a other firmare.
:laugh:
balpem said:
...the trick was to flash the stock recovery for all Lollipop versions
Click to expand...
Click to collapse
When you say flash stock recovery for all LP versions, did you flash and then reboot each time? or flash over and when complete, flash over again still on fastboot?
Can you briefly describe in steps? Tnx! and Glad you were able to recover
jfer671 said:
When you say flash stock recovery for all LP versions, did you flash and then reboot each time? or flash over and when complete, flash over again still on fastboot?
Can you briefly describe in steps? Tnx! and Glad you were able to recover
Click to expand...
Click to collapse
I flashed via fastboot the stock recovery which you can download via the link above. the provider (user rowihel2012) claims, that this recovery works for all lolipop stock roms.
After that I made a reboot and pressed (power button and volume+) to check if its installed.
Than I downloaded the lollipop version I have had previously installed. In my case this was the B324 European version.
I put it on my sd card (dload/UPDATE.app) and launched the phone with the three button rescue method. The recovery recognized the rom on the sdcard and started to flash the OS.
After less than 5 min, my phone was restored.
I have made the experience, when using certain roms (B324, B308 etc..) with certain stock recoveries, I was not able to flash the OS and the recovery stoped always at 90%.
The recovery linked above seems to work great for the B324 version, I haven't tried any other stock roms with it.
I wonder if this will work for B327? Seems the actual last update for LP was B324, now I can't seem to get out of this firmware to go back to KK. When I flash transition B300, it's successful...but for some odd reason, when I flash 137, 143, 145 or 148...I auto go back to B327. This, after the fact I'm flashing those firmware's recoveries. Any ideas what I might do to get out of 327?
---------- Post added at 01:42 PM ---------- Previous post was at 01:38 PM ----------
Also, what's this Vol+ and Power technique?, all I get is the three menu screen (reboot, factory reset and format cache).
jfer671 said:
I wonder if this will work for B327? Seems the actual last update for LP was B324, now I can't seem to get out of this firmware to go back to KK. When I flash transition B300, it's successful...but for some odd reason, when I flash 137, 143, 145 or 148...I auto go back to B327. This, after the fact I'm flashing those firmware's recoveries. Any ideas what I might do to get out of 327?
---------- Post added at 01:42 PM ---------- Previous post was at 01:38 PM ----------
Also, what's this Vol+ and Power technique?, all I get is the three menu screen (reboot, factory reset and format cache).
Click to expand...
Click to collapse
You can try this recovery above which should work for all lollipop roms but I have no better idea as I have had basicly the same problem and could only flash the former rom i had installed whch was B324.
The Vol+ and Power i do to get into the recovery menu (the three menu screen) to check if the recovery was flashed successfully. I have had often the problem after flashing a recovery that it did not work. this is to check if the recovery works.
When i tried to flash a cwm recovery, i couldnt enter any recovery mode after that anymore. I panicked at this point but than i realised that not all recoveries did work for me. For example I could never flash a CWM recovery, not sure why. Maybe because I tried to flash a 4.4 recovery and I had a 5.1 BOOT.img installed?
balpem said:
After a 36 hour marathon my mate 7 is back and working. the trick was to flash the stock recovery for all Lollipop versions wich can be foudn here: http://forum.xda-developers.com/mat...8-7-0-mate7-android-5-1-t3156779/post61958212 via linux. I somehow seem to have had trouble over wndows.
And after that do the three button rescue with the newest B 324 firmware which I have had installed before I destroyed my OS..
and my camera is now running normaly which was the initial reason i tried to install a other firmare.
:laugh:
Click to expand...
Click to collapse
balpem said:
You can try this recovery above which should work for all lollipop roms but I have no better idea as I have had basicly the same problem and could only flash the former rom i had installed whch was B324.
The Vol+ and Power i do to get into the recovery menu (the three menu screen) to check if the recovery was flashed successfully. I have had often the problem after flashing a recovery that it did not work. this is to check if the recovery works.
When i tried to flash a cwm recovery, i couldnt enter any recovery mode after that anymore. I panicked at this point but than i realised that not all recoveries did work for me. For example I could never flash a CWM recovery, not sure why. Maybe because I tried to flash a 4.4 recovery and I had a 5.1 BOOT.img installed?
Click to expand...
Click to collapse
I see, so then it seems like some recoveries did in fact work with fastboot on me, because the Vol+ and Power worked, but it either only put me in V100R001C900B300 OR MT7-L09C900B300. I've read that I can't just flash KK over LP, that I needed to flash the B300 which is why I flashed transition package first. Should I not have done this?
Once in transition mode though (I booted up and checked, then went back into recovery), if I flashed 4.4 (recovery), it oddly put me back to B327...strange even though the recovery flashed was B137 or B145.
Let me see this link above. I'm back again at 5.1.1 LP B327. I'll do instead fastboot and flash above the recovery and so on, and I'll post the results, if any. Oddly enough, if I flashed boot, recovery and system images of 4.4, I get an "Android" boot screen that hangs, no Huawei.
I really like LP because of some of the features not found in KK like the dual windows, camera tweaks, etc. But no root yet available. TWRP doesn't seem to work as well, fails in fastboot.
balpem said:
After a 36 hour marathon my mate 7 is back and working. the trick was to flash the stock recovery for all Lollipop versions wich can be foudn here: http://forum.xda-developers.com/mat...8-7-0-mate7-android-5-1-t3156779/post61958212 via linux. I somehow seem to have had trouble over wndows.
And after that do the three button rescue with the newest B 324 firmware which I have had installed before I destroyed my OS..
and my camera is now running normaly which was the initial reason i tried to install a other firmare.
:laugh:
Click to expand...
Click to collapse
Okay...so I was able to flash down to B324, but not via the link provided. What I did was, flash B300 cust.img on (fastboot) then flash boot/recovery/cust/system.img (fastboot). Rebooted with VolumeUp + Power to check for recovery (success), performed a wipe and done! Back to B324.
Now I gotta figure how to go back down to B145, which is where I was at with Root and with no problems at all. If I flash B300 again and then B145...I get the "Android" logo (instead of Huawei) and then the HAM7 reboots and recovers itself back to B324.
I am having some issues trying to flash Recovery (TWRP). When ever I try to boot to Recovery after flashing it, it says "No command." even after I did everything correctly.
My Nexus 5s bootloader is unlocked and I am currently running Marshmallow 6.0.1 if that matters.
CableStone said:
I am having some issues trying to flash Recovery (TWRP). When ever I try to boot to Recovery after flashing it, it says "No command." even after I did everything correctly.
My Nexus 5s bootloader is unlocked and I am currently running Marshmallow 6.0.1 if that matters.
Click to expand...
Click to collapse
What do u mean it says no command, do u mean u still end up in stock recovery, the one with the android and triangle? If that's what's happening then u aren't flashing twrp correctly, or ur not booting strait to recovery after flashing it, how are u flashing it, via command line? If so do this:
fastboot flash recovery "recovery name here".zip
fastboot reboot recovery
That should fix your issue, if u don't boot straight to recovery after u flash it, or if u use something like flashify, when the device reboots it overwrites recovery with the stock recovery, which is what ur seeing
Sent from my XT1526 using Tapatalk
CableStone said:
I am having some issues trying to flash Recovery (TWRP). When ever I try to boot to Recovery after flashing it, it says "No command." even after I did everything correctly.
My Nexus 5s bootloader is unlocked and I am currently running Marshmallow 6.0.1 if that matters.
Click to expand...
Click to collapse
And after flashing the custom recovery again, do not unplug the USB cable or let the device boot. After flashing the recovery, the display should go back to the bootloader, use the volume rocker to highlight recovery, press the power to get into recovery. This will make sure that you flashed right this time. The TWRP logo should be display if everything goes right.
Recovery is flashed with the fastboot command "fastboot flash recovery name-of-file.img".
soupysoup said:
What do u mean it says no command, do u mean u still end up in stock recovery, the one with the android and triangle? If that's what's happening then u aren't flashing twrp correctly, or ur not booting strait to recovery after flashing it, how are u flashing it, via command line? If so do this:
fastboot flash recovery "recovery name here".zip
fastboot reboot recovery
That should fix your issue, if u don't boot straight to recovery after u flash it, or if u use something like flashify, when the device reboots it overwrites recovery with the stock recovery, which is what ur seeing
Sent from my XT1526 using Tapatalk
Click to expand...
Click to collapse
Yeah, sorry for missing that.. And do you need a rooted device in order to flash a TWRP?
Root is not required to flash a custom recovery or a custom rom.
soupysoup said:
fastboot flash recovery "recovery name here".zip
fastboot reboot recovery
That should fix your issue, if u don't boot straight to recovery after u flash it, or if u use something like flashify, when the device reboots it overwrites recovery with the stock recovery, which is what ur seeing
Click to expand...
Click to collapse
It seems to me that this is only required with TWRP 3.0.0 while 2.8.7.1 will happily survive a normal system boot. I've tried right now, just one phone, back to back tests, no other changes.
How come the phone overwrites 3.0.0 with stock but leaves 2.8.7.1 untouched? This is weird.
Am I missing something, perhaps?
I had this droid razr maxx hd a long time ago. I used to be pretty savvy with rooting and whatnot. At one point i rooted the phone enabled native tether and even unlocked the bootloader. however I never flashed a custom recovery. suddenly one day the phone started boot looping. I simply switched phones. now my new phone is broken and i need to get this boot loop fixed. trying to do a recovery simply ends up with it trying to boot again and loop. sometimes it shows the robot with "no command" under it. so thats not possible.
when i select ap fastboot i get device is unlocked status code 3.
So i should be able to flash something to it and get out of this bootloop right? can someone point me to a noob friendly tutorial to try and fix this?
if any more info is needed let me know
Thanks!
KiraTheSavior said:
I had this droid razr maxx hd a long time ago. I used to be pretty savvy with rooting and whatnot. At one point i rooted the phone enabled native tether and even unlocked the bootloader. however I never flashed a custom recovery. suddenly one day the phone started boot looping. I simply switched phones. now my new phone is broken and i need to get this boot loop fixed. trying to do a recovery simply ends up with it trying to boot again and loop. sometimes it shows the robot with "no command" under it. so thats not possible.
when i select ap fastboot i get device is unlocked status code 3.
So i should be able to flash something to it and get out of this bootloop right? can someone point me to a noob friendly tutorial to try and fix this?
if any more info is needed let me know
Thanks!
Click to expand...
Click to collapse
Did You have TWRP flashed as recovery or you running stock and were you running custom or stock rom.
OGdroidster said:
Did You have TWRP flashed as recovery or you running stock and were you running custom or stock rom.
Click to expand...
Click to collapse
I would say stock because i never flashed a custom recovery or anything. just root and unlock bootloader. and enable native wifi teather. but the restore doesnt work it just gives me the robot with "no command"
KiraTheSavior said:
I would say stock because i never flashed a custom recovery or anything. just root and unlock bootloader. and enable native wifi teather. but the restore doesnt work it just gives me the robot with "no command"
Click to expand...
Click to collapse
Just download the drivers for this device and install them. Then download and install rsd lite and install that. Then download the the stock firmware make sure it is the right one and flash it with rsd lite after that you will have to reroot the device. If you don't know what version of firmware you had just post a pic of your device while in ap fastboot bootloader and I can let you know.
OGdroidster said:
Just download the drivers for this device and install them. Then download and install rsd lite and install that. Then download the the stock firmware make sure it is the right one and flash it with rsd lite after that you will have to reroot the device. If you don't know what version of firmware you had just post a pic of your device while in ap fastboot bootloader and I can let you know.
Click to expand...
Click to collapse
Random question. is there any way to retrieve photos from the internal storage of this device with it stuck in a boot loop?
KiraTheSavior said:
Random question. is there any way to retrieve photos from the internal storage of this device with it stuck in a boot loop?
Click to expand...
Click to collapse
If you had a custom recovery that you could mount while in recovery. Have you tried adb.
Hi, need some urgent help here.
I was trying to install a custom rom, so I unlocked first the bootloader, then flashed twrp 3.0.2 for Android 5.1 and with it I flashed KangVip rom (porto from honor 6).
Problem was it didn't boot, just black screen.
So I supposed the problem was with the rom so I flashed via fastboot the aosp 6, obviously with same results.
I tried lot of stuff (twrp 2.8.x.x, reinstall stock firmware, restore twrp backup of stock full firmware and so on - I did almost everything I could do) and now I'm with a Huge problem: no huawei logo at start, just a white screen and nothing happen. I have twrp 3.0.2 for 5.1 installed right now but I can't install stock recovery.
Please help me, what do I gotta do?
[emoji30]
the ported rom is based on Android 6.0 you have Android 5.1 youk should flash 5.1 based rom..
it's good to flash stock and update official to b560 or b571 depending on which region to have then flash twrp recovery and then flash desire rom..
fazi2015 said:
the ported rom is based on Android 6.0 you have Android 5.1 youk should flash 5.1 based rom..
it's good to flash stock and update official to b560 or b571 depending on which region to have then flash twrp recovery and then flash desire rom..
Click to expand...
Click to collapse
Thx for this.
But I have a problem, I can't install stock recovery and if I try to flash the .img files extracted from update.app nothing happens.
Also, I still have that problem with huawei logo disappeared and a blank white screen instead.
Sent from my HUAWEI GRA-L09 using Tapatalk
boot into bootloader and flash stock recovery but if you know what exactly firmware was you have(bxxx) then no need to flash recovery just put update.app to your sd card and then force update three buttons combination (volume both and power) turn off it remove data cable then press these three buttons it'll go in recovery sometime but try two or three times(in recovery turn off device) and try again if that method not work you should flash stock recovery to do so and if it didn't go to bootloader(fastboot) then connect data cable and then press vol- and power it'll go to bootloader in bootloader flash stock recovery then force update your device....
fazi2015 said:
boot into bootloader and flash stock recovery but if you know what exactly firmware was you have(bxxx) then no need to flash recovery just put update.app to your sd card and then force update three buttons combination (volume both and power) turn off it remove data cable then press these three buttons it'll go in recovery sometime but try two or three times(in recovery turn off device) and try again if that method not work you should flash stock recovery to do so and if it didn't go to bootloader(fastboot) then connect data cable and then press vol- and power it'll go to bootloader in bootloader flash stock recovery then force update your device....
Click to expand...
Click to collapse
Solved, thanks!
Sent from my HUAWEI GRA-L09 using Tapatalk
fazi2015 said:
boot into bootloader and flash stock recovery but if you know what exactly firmware was you have(bxxx) then no need to flash recovery just put update.app to your sd card and then force update three buttons combination (volume both and power) turn off it remove data cable then press these three buttons it'll go in recovery sometime but try two or three times(in recovery turn off device) and try again if that method not work you should flash stock recovery to do so and if it didn't go to bootloader(fastboot) then connect data cable and then press vol- and power it'll go to bootloader in bootloader flash stock recovery then force update your device....
Click to expand...
Click to collapse
Hope you can help me out here...I had just gotten my HAM7 for a couple of days. Was on 4.4.2 B120, was able to get it up to B326. Just yesterday I attempted to flash up to B331 and it succeeded according to the "local update" option. Then it went on boot loop. I tried doing the force 3-button option and that worked to the point of saying it succeeded and will reboot. Now I'm stuck on Ascend Mate logo. I can no longer get into factory option mode (V+Power), only fastboot mode. Also, I can't do force update no more so I can't try any other "update.app" unless I'm missing something here.
Any help in getting this unit at least back to working condition will be a BIG help. I just received this two days ago.
Thx!!!!
jfer671 said:
Hope you can help me out here...I had just gotten my HAM7 for a couple of days. Was on 4.4.2 B120, was able to get it up to B326. Just yesterday I attempted to flash up to B331 and it succeeded according to the "local update" option. Then it went on boot loop. I tried doing the force 3-button option and that worked to the point of saying it succeeded and will reboot. Now I'm stuck on Ascend Mate logo. I can no longer get into factory option mode (V+Power), only fastboot mode. Also, I can't do force update no more so I can't try any other "update.app" unless I'm missing something here.
Any help in getting this unit at least back to working condition will be a BIG help. I just received this two days ago.
Thx!!!!
Click to expand...
Click to collapse
are you have unlock bootloader or not..
fazi2015 said:
are you have unlock bootloader or not..
Click to expand...
Click to collapse
Yes, bootloader is unlocked. FYI, I can't do Vol+ Power or 3-button force. I have no idea what went wrong after the B331 update.app flash. It said successful then boot loop after. I have looked all over the forums and tried everything from flashing C900B300 rollback to try and get 4.4.2 that I started out with, but I really don't know which firmware to start with. The last update.app files I was using was the European variants. Phone was originally locked to Ecuador MoviStar network at B120SP04, then I flashed up to B324 5.1.1. Rooted and then wanted to upgrade to B331 so I unrooted and flashed. Now I'm stuck.
jfer671 said:
Yes, bootloader is unlocked. FYI, I can't do Vol+ Power or 3-button force. I have no idea what went wrong after the B331 update.app flash. It said successful then boot loop after. I have looked all over the forums and tried everything from flashing C900B300 rollback to try and get 4.4.2 that I started out with, but I really don't know which firmware to start with. The last update.app files I was using was the European variants. Phone was originally locked to Ecuador MoviStar network at B120SP04, then I flashed up to B324 5.1.1. Rooted and then wanted to upgrade to B331 so I unrooted and flashed. Now I'm stuck.
Click to expand...
Click to collapse
now you should flash twrp recovery in fastboot mode and then flash a custom rom like kangvip I'll send you link soon...
fazi2015 said:
now you should flash twrp recovery in fastboot mode and then flash a custom rom like kangvip I'll send you link soon...
Click to expand...
Click to collapse
Thank you very much....hope that will solve the boot issue and bring this unit back to life
Alright, so I've given up complete hope that I can get my unit back up and running again. I've tried so many ways already with no success (fastboot/adb, force upgrade, etc.,), and even tried to copy my second HAM7 images (via sdk tools) and to no avail.
The thing I'm trying to understand is where exactly do I start with trying to revive? When I first got this device from eBay, it was apparently still on "MoviStar" Telefonica-Spain network so my network bars showed "R" for roaming. Somehow, I was able to flash it from being on V100R001C00B120SP04a and upgrade to B127>B145>B324 which made me able to use my own service normally. It worked fine and I was even able to root it. Decided to do a last upgrade to B331 and while the local update option showed it as successfully installed, it went into boot loop ever since. Hence, I used European firmwares for most of the flashing. My second mate was on B145 and I was able to get that to B331, which is running fine right now.
ATM, I am ONLY able to do Volume-/Power to get into fastboot.
Doesn't work:
- V+/Power (stock recovery)
- V-+/Power (3-button force)
What works:
- V-/Power with USB for fastboot
*Bootloader is unlocked, but I do believe that after flashing the last firmware of B331, I may have done a factory wipe, which probably reset the USB debugging option as well. So, I'm sure I'm stuck with a device that just might be flashed on the wrong firmware and is factory reset which prevents me from flashing a custom rom or even the stock rom???
Any last advice I would be so thankful for...still waiting on the link for KangVip rom from (fazi2015)
All the best...
jfer671 said:
Alright, so I've given up complete hope that I can get my unit back up and running again. I've tried so many ways already with no success (fastboot/adb, force upgrade, etc.,), and even tried to copy my second HAM7 images (via sdk tools) and to no avail.
The thing I'm trying to understand is where exactly do I start with trying to revive? When I first got this device from eBay, it was apparently still on "MoviStar" Telefonica-Spain network so my network bars showed "R" for roaming. Somehow, I was able to flash it from being on V100R001C00B120SP04a and upgrade to B127>B145>B324 which made me able to use my own service normally. It worked fine and I was even able to root it. Decided to do a last upgrade to B331 and while the local update option showed it as successfully installed, it went into boot loop ever since. Hence, I used European firmwares for most of the flashing. My second mate was on B145 and I was able to get that to B331, which is running fine right now.
ATM, I am ONLY able to do Volume-/Power to get into fastboot.
Doesn't work:
- V+/Power (stock recovery)
- V-+/Power (3-button force)
What works:
- V-/Power with USB for fastboot
*Bootloader is unlocked, but I do believe that after flashing the last firmware of B331, I may have done a factory wipe, which probably reset the USB debugging option as well. So, I'm sure I'm stuck with a device that just might be flashed on the wrong firmware and is factory reset which prevents me from flashing a custom rom or even the stock rom???
Any last advice I would be so thankful for...still waiting on the link for KangVip rom from (fazi2015)
All the best...
Click to expand...
Click to collapse
https://mega.co.nz/#!3N4RzbJY!saB4NY...Ao5goVNiSXAjEc
I am not 100% sure about this rom but you can try it in fastboot you should flash twrp recovery first..
fazi2015 said:
https://mega.co.nz/#!3N4RzbJY!saB4NY...Ao5goVNiSXAjEc
I am not 100% sure about this rom but you can try it in fastboot you should flash twrp recovery first..
Click to expand...
Click to collapse
Unfortunately, it says the file is no longer available
jfer671 said:
Unfortunately, it says the file is no longer available
Click to expand...
Click to collapse
try this all information is here
https://forum.xda-developers.com/mate-7/orig-development/rom-kangvip-rom-mate7-emui3-1-b351-t3228597
fazi2015 said:
try this all information is here
https://forum.xda-developers.com/mate-7/orig-development/rom-kangvip-rom-mate7-emui3-1-b351-t3228597
Click to expand...
Click to collapse
Okay, so final result is I'm stuck on a frozen logo now. The twrp bat file again showed success in flashing and rebooted the device, but I'm hung on the "Huawei Ascend" logo. I have to pull the battery to shut it off, otherwise it stays on. So I'm now sure that it's a hard bricked device since I did the stupid thing of factory resetting which probably reset the usb debug...making it almost impossible to flash any firmware now.
Thanks for the help anyways...I really appreciate it. Gonna throw this up on eBay and see if anyone wants it for parts
jfer671 said:
Okay, so final result is I'm stuck on a frozen logo now. The twrp bat file again showed success in flashing and rebooted the device, but I'm hung on the "Huawei Ascend" logo. I have to pull the battery to shut it off, otherwise it stays on. So I'm now sure that it's a hard bricked device since I did the stupid thing of factory resetting which probably reset the usb debug...making it almost impossible to flash any firmware now.
Thanks for the help anyways...I really appreciate it. Gonna throw this up on eBay and see if anyone wants it for parts
Click to expand...
Click to collapse
I know it's annoying but last time I research more and guide you I was have same problem don't give up....
I send you recovery flash in fastboot no need of usb debugging usb debugging need for adb not for fastboot in fastboot flash recovery by your self download it
https://mega.co.nz/#!GRw0CZjQ!iZllDkA6yJeWk7iEA4vEVA94r2nM_YjAuiS8B9IZdm0
then extract the zip go to resource and hold shift and left click then select open command port here then power off device completely boot into fastboot (bootloader) connect the device to pc and in command port type
fastboot flash recovery twrp_2_7.img
after that type
fastboot reboot and hold the volume- button of device it'll boot into recovery if you success then reply..
I've noticed two things when flashing KK or LP. On KK, the phone does a constant boot loop with Huawei logo (on off on off), but on LP the Huawei logo hangs...it doesn't boot loop. Is this an indication or just a fault with both OS?