HI, I will get right to the point. My phone is Honor 7x (BND-AL10C675 INDIAN) I screwed it up.
Now, the fastboot or recovery or E recovery nothing works!!
There is only one screen which keeps coming in a loop rebooting with a vibration
It says " ERROR MODE"
ATTENTION!
PLEASE UPDATE SYSTEM AGAIN
ERROR! FUNC NO : 8 (HIFI IMAGE)
ERROR NO : 1 (SECURITY VERIFY FAILED)
It keeps rebooting and the phone doesn't even turn off. I tried the download mode (Volume UP & Down Power button, SAME SCREEN comes up)
Let me know if you want me to write a detailed version of how I got here or ask any specific questions.
Now, all I need is at least FASTBOOT so I can do something about it. Is there anyone who can help? I hope SOME PRO OR A GEEK is able to solve this issue magically. I just can't tell you what I'm going through.
UPDATE:
As Christo31 requested and maybe it's useful for other people to help me out. Here is what I did. It's a real long story!!
I have Honor 7x (BND-AL10C675 INDIAN) I had unlocked bootloader and twrp and I was on emui 8 beta which I flashed manually using one of the tutorials here on the forum. One day, I decided to get back to stock as I was stuck in emui 8 beta and no OTA updates so I downloaded the emui 8 stable rom from firmware finder and put it in sd card "dload" folder. Now, for this method to work, we need to relock bootloader and flash stock recovery which I did and it completely wiped everything out.
Now, the "dload" method fails at 5% every time. I tried different roms for this very model but no it doesn't work. (Also, my build no. was stuck at B141 for a long time no matter what rom I changed : Yes, this is stupid, I should have fixed it first) Maybe that's why the "dload" method doesn't work.
So, in this forum I saw some with similar issue but somewhat different " Frp locked & bootloader unlocked" and I was told that the DC phoenix software might fix this and I bought some credits and used the software. Here's what I discovered
My observations with the software:
* I put the phone in fastboot and downloaded the update.app full Ota (same one emui stable) and tried to flash. The software flash well ok as it says "the software is written" but the phone doesn't boot and goes directly into the recovery mode and again the bootloader and frp are locked.
*Here, I noticed that it shows something like "opening backdoor" and then the Bootloader status goes to red and says "UNLOCKED" it means it was definitely doing something so the next I repeated the same process but as soon as the phone was "UNLOCKED", I pulled the usb cable out and I kept my command ready and tried "fastboot flash recovery_ramdisk recovery.img" and guess what it flashed that twrp file and I could see in the command line that it went "okay" so I immediately booted to recovery but again the stock recovery comes up. Also, I tried system.img also it flashes fine but phone doesn't boot. Same recovery.
REMEMBER: THE ABOVE STEPS MAY WORK FOR PEOPLE WHO HAVE UNLOCKED BOOTLOADER BUT FRP LOCKED. IN MY CASE BOTH ARE LOCKED SO THAT'S THE DIFFERENCE.
* I tried another update.app I guess it's BNDL22.ZIP or something and this time the software was trying to flash in "upgrade mode" and somehow the recovery was broke. There was some "ERROR MODE" basically the recovery was broke. I didn't care much. Although flashing another update.app would have fixed it.
* The next step I tried after a lot of trial & error for about 1.5 days. This time I did the same when the bootloader was unlocked, I pulled the cable and tried the command "fastboot oem unlock unlock code" ( I should have got this idea before, I mean it's a mess guys, I didn't sleep for too long) and I was shocked to see that it showed the options "Unlocked bootloader yes or no" and I clicked "yes" and I jumped hoping that it's over but... I ended up with 'ERROR MODE' which I described above.
* I feel, because the recovery was broken, it ended up in error mode. Just imagine if my recovery was fine and then I tried this command then it would have erased everything and maybe I might have been presented with fastboot screen with both "frp & bootloader Unlcock" or at least 'bootloader unlock" in either way, I could have flashed a 'system.img' and get into settings and BEATH THE HELL OUT OF THAT "ENABLE OEM UNLOCK' in settings. The rest you know.
I wrote this not just because someone might help me but because a lot of posts on this forum really helped me a lot and posts like these can help a lot of people down the road.
Now, my phone is still in the same loop. Reboot, Honor logo, Error mode...REPEAT
I heard that once the phone drains down completely, we may get back fastboot. Fingers crossed. Sadly, I have Mac so I borrowed windows laptop for this purpose from a friend. This is the last day and I guess I'm going to put it on sale and sell it as a scrap or something for display and stuff.
How much does motherboard cost? anyone any ideas? if it's below 4K or about 80$ then I might go for the repair if nothing works!!
I'm going to update on this very soon. Le'ts hope for a miracle. Either way my HONOR 7X IS A LEGEND.
UPDATE :
After waiting for hours, my phone got discharged and I curiously plugged in the phone pressing "volume down" button OR power + volume and all other types of combinations but the phone just goes to the same "ERROR MODE' and keeps going in the same loop.
So, I really hate Huawei for not providing stock firmware or some type of recovery for people like me to get back to stock. For example : Xiaomi has that fastboot ROMS which you can easily flash in EDL mode no matter what happens to you and of course some other ways to recovery the bricked phones.
The Huawei E recovery?? What the **** is it? Does it ever work? It's some kind of a joke. The hisuite is again **** It says 'My model is not supported" and it only showed me two very older and ancient models that are supported for recovery.
I'm not expecting warranty but at least they should give the service for the customer. Did I tell you that this phone was in Service centre for three days when it had FASTBOOT, RECOVERY, E RECOVERY working. They could n't fix it in 3 days so I rushed them to get my phone back hoping that I would recover it with the above method.
Now, I got the Redmi Note 5 Pro and my 7X is a dead brick and I'll try selling it as scrap for display etc...
Finally, I really love the XDA forums and the friendly members who are very helping and so empathetic. Thanks guys, you are the best
I'm not leaving. I'll see you on the other side. I mean, the Redmi Note 5 pro development. Keep hustling
You need to tell us what you did exactly first for any help
Thetpcguy said:
ERROR! FUNC NO : 8 (HIFI IMAGE)
ERROR NO : 1 (SECURITY VERIFY FAILED)
Click to expand...
Click to collapse
when you are in this situation
- Keep press "volume down" + "power button" for about 10 seconds, the phone will reboot
- When the phone reboot, release the "power button" but keep "volume down" and in the same time plug the micro usb cable ( you have to be ready and quick )
the phone will boot in FASTBOOT&RESCUE MODE ( hope you have unlocked bootloader and frp unlocked )
azerty11 said:
when you are in this situation
- Keep press "volume down" + "power button" for about 10 seconds, the phone will reboot
- When the phone reboot, release the "power button" but keep "volume down" and in the same time plug the micro usb cable ( you have to be ready and quick )
the phone will boot in FASTBOOT&RESCUE MODE ( hope you have unlocked bootloader and frp unlocked )
Click to expand...
Click to collapse
Hi, thanks for your help but the phone doesn't turn off. it just keeps rebooting and there is honor logo and then error mode and then phone reboots and the same cycle. I tried what you said also with other possible things but I guess I need to let the battery drain out completely as some people said it worked for them. It's almost 9 hours and it's still not drained (it was on full charge) anyway Fingers Crossed!!
christo31 said:
You need to tell us what you did exactly first for any help
Click to expand...
Click to collapse
HI, I Updated the post in full details. I hope my phone is rescued.
Let the battery drain, and then try to get into fastboot using key combinations. Let me know if you can do this, from there on you can proceed normally.
vaasu_g_wills said:
Let the battery drain, and then try to get into fastboot using key combinations. Let me know if you can do this, from there on you can proceed normally.
Click to expand...
Click to collapse
It didn't work out. It only boots in error mode and keeps going in a loop.
Thetpcguy said:
It didn't work out. It only boots in error mode and keeps going in a loop.
Click to expand...
Click to collapse
Did you try huawie suite system recovery??
vaasu_g_wills said:
Did you try huawie suite system recovery??
Click to expand...
Click to collapse
I never heard of it I'm googling it now and please throw some light on this but strangely your message got my hopes up.
UPDATE: Oh, I guess you are talking about Huawei Hisuite. I did try that and it didn't work and I included that in my post above as well. I still have my phone with me completely discharged.
Thetpcguy said:
I never heard of it I'm googling it now and please throw some light on this but strangely your message got my hopes up.
UPDATE: Oh, I guess you are talking about Huawei Hisuite. I did try that and it didn't work and I included that in my post above as well. I still have my phone with me completely discharged.
Click to expand...
Click to collapse
and with phone , off, totaly discharged, holding volume down, and plugging in the usb cable , just gives you same error mode?
---------- Post added at 10:59 PM ---------- Previous post was at 10:27 PM ----------
[/COLOR]Follow this steps.
1. Just flash with Dc phoenix
3 extract two update. App with huwai firmware extractor.
4. Check the log of dc phoix. Check which files are not flashed. By comparing with extracted files You will observe some files are not flashed. (some files are not in log of dc phoinix) Like Vendor.img product.img cust.img etc.. Note down which imgs are not flashed..
5. Now use multitool and go to unbrick option. There will be option of flashing around 5 img. Flash the 5 imgs. You will get this 5 img from extracting Update.app
6.then your phone will be working but not perfectly. Flash TWRP with fastboot.
7. Aftee flashing TWRP flash all other imgs which were not flashed by dc phoenix.
Then boot. Your phone must be good.
And again if you want then re flash with HWOTA tool. Your phone will be running now.
mrmazak said:
and with phone , off, totaly discharged, holding volume down, and plugging in the usb cable , just gives you same error mode?
Click to expand...
Click to collapse
Yes, even after that it give the error mode and goes on the same loop. Honor log, Error Mode, Reboot...REPEATED LOOP
I Already gave up on this phone but only a miracle can save this phone now.
Thetpcguy said:
Yes, even after that it give the error mode and goes on the same loop. Honor log, Error Mode, Reboot...REPEATED LOOP
I Already gave up on this phone but only a miracle can save this phone now.
Click to expand...
Click to collapse
i more question for you. Please . Does the three button combo from power off attempt to show update screen. I know for everyone the dload method is failing at 5%, but still need to know if yours is attempting this or not even try.
There might be dload method that works, according to posts on 4pda.ru
mrmazak said:
i more question for you. Please . Does the three button combo from power off attempt to show update screen. I know for everyone the dload method is failing at 5%, but still need to know if yours is attempting this or not even try.
There might be dload method that works, according to posts on 4pda.ru
Click to expand...
Click to collapse
I tried that also. Power+Volume UP+Volume Down to get into download mode but it just goes into that "ERROR MODE'
Normally, it should but maybe because I broke my stock recovery also and then tried to unlock the bootloader when the frp was locked with the DC phoenix trick (Pulling out the plug) that it's really screwed up beyond all this. Let me know if you want me to post pics or maybe if the clips canoe uploaded here, I will make short clip with what's happening. I guess I need some factory or manufacturer level stuff or I need to replace the motherboard. BTW the local guy told me it costs 8K INR which is around 125-130 USD which I'm not willing to spend. I got Redmi Note 5 Pro and I'll probably never ever buy Huawei phones ever.
ANYONE HERE WHO CAN DONATE THE MOTHERBOARD, PLEASE PM ME:laugh:
Related
last night i got the notification to say that i was able to update to 7.0 and i was so excited that i kinda forgot about xposed and stuff and now
the phone is completely useless it wont turn on it just does nothing, when its charging the white light flashes but still nothing Please help
Can you connect your phone to a computer and see if adb/fastboot still senses your device, or whether your device still shows up (or reports as a Qualcomm HS-USB)?
echo92 said:
Can you connect your phone to a computer and see if adb/fastboot still senses your device, or whether your device still shows up (or reports as a Qualcomm HS-USB)?
Click to expand...
Click to collapse
nope not seeing it
Hmm, so you're not getting anything showing up in Device Manager (like in this thread https://forum.xda-developers.com/moto-g4-plus/help/help-xt1642-hard-bricked-help-t3498943 )?
I am not familiar with the procedure of how to unbrick a device like this, vache has uploaded a blank flash file (https://forum.xda-developers.com/showpost.php?p=70701015&postcount=1975), I hope someone else can guide you on the procedure to unbrick your phone if you need such a file.
Sounds crazy, but push the power button for 2-3 minutes.... Dont know why, but worked for me in the past.
bullfinch110 said:
Sounds crazy, but push the power button for 2-3 minutes.... Dont know why, but worked for me in the past.
Click to expand...
Click to collapse
thankyou it worked perfectly
The same here after update!
I have a Moto G4 Plus, Product: athene_16mp XT1644 64GB P2A
Since last update (Nouga) my phone doesn't pass the bootloader screen. Connected to my PC, only fastboot commands works as adb don't see it. The recovery mode is dead, every time I try to enter it says:
Failed to validate recovery image. Error: Failed to pass validation, backup to fastboot. Boot up failed.
I searched the forum to find the original rom image but as I didn't Check 'Allow OEM Unlock' in Android Settings > Developer, I can't install any image from there.
Any help?
alemangioni said:
I have a Moto G4 Plus, Product: athene_16mp XT1644 64GB P2A
Since last update (Nouga) my phone doesn't pass the bootloader screen. Connected to my PC, only fastboot commands works as adb don't see it. The recovery mode is dead, every time I try to enter it says:
Failed to validate recovery image. Error: Failed to pass validation, backup to fastboot. Boot up failed.
I searched the forum to find the original rom image but as I didn't Check 'Allow OEM Unlock' in Android Settings > Developer, I can't install any image from there.
Any help?
Click to expand...
Click to collapse
If fastboot still works, perhaps try this fastboot Nougat image, see if that'll flash? https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612
It requires you booting into bootloader (so power down your device, wait 5 seconds then hold the volume down and power button, should then boot into bootloader), so it might flash a working recovery and system onto your device.
bullfinch110 said:
Sounds crazy, but push the power button for 2-3 minutes.... Dont know why, but worked for me in the past.
Click to expand...
Click to collapse
I believe there are two possible reasons...
Either 2-3 minutes forces a fully hard reset.
Or
If you have a really really flat battery sometimes as it charges and then boots up it gets stuck in repeated reboot since effort to boot drains more than it can charge in that time, so holding power button holds boot sequence long enough for battery to gain enough charge to allow boot to work..
Both are just my opinions so might be completely wrong
I think it's Option no1, because in my case the battery was nearly full charged.
Nevertheless... One guy happy to have helped, the other guy happy to have reanimated his phone:laugh:
Hi All.
I hope someone can help me. I encountered this stupid problem:
I have a L31 device and successfully installed the Nougat (test?)update through Firmware Finder. But since this wasn't the definitive update, I decided to rollback to MM. I installed the C900B300 rollback package and then the B160 package. That went well, BUT the device now refused to activate the Google services. I couldn't enter a Google account. Not from Settings > Accounts and not from any other Google app like Chrome, Play Store, Gmail or others. The screen just kept returning to the Homescreen.
Upon checking About this device, I noticed the version now was C900B160, instead of the expected C432B160. I am very positive I used the C432B160 MM package to flash. This I did with the three button method. But then how come it still showed C900B160?
So I first tried to reflash the C432B160 with the three button method. Flashing worked well, but the problem wasn't solved. Still no Google activation and still the same C900B160 number.
So then I decided to reflash the rollback package...
That turned out to be a mistake... After flashing that (and it did show 100% successfull after flashing) the device is bricked. The Huawei logo shows and then nothing happens. The logo stays in the screen. I can't even turn the device off. Short pressing the ON-OFF button does nothing and long pressing just restarts the logo and nothing more.
I tried to reflash the MM update C432B160 with the three button technique, but that doesn't work anymore!! Entering erecovery with the volume up and ON-OFF also doesn't work anymore!! The only thing that works is Fastboot when connected to a pc. That screen shows phone (and bootloader) is locked, by the way. So I can't flash boot.img and recovery.img .
Has anybody encountered such problems and knows what to do now?? Thanks guys!
Liebaart said:
Hi All.
I hope someone can help me. I encountered this stupid problem:
I have a L31 device and successfully installed the Nougat (test?)update through Firmware Finder. But since this wasn't the definitive update, I decided to rollback to MM. I installed the C900B300 rollback package and then the B160 package. That went well, BUT the device now refused to activate the Google services. I couldn't enter a Google account. Not from Settings > Accounts and not from any other Google app like Chrome, Play Store, Gmail or others. The screen just kept returning to the Homescreen.
Upon checking About this device, I noticed the version now was C900B160, instead of the expected C432B160. I am very positive I used the C432B160 MM package to flash. This I did with the three button method. But then how come it still showed C900B160?
So I first tried to reflash the C432B160 with the three button method. Flashing worked well, but the problem wasn't solved. Still no Google activation and still the same C900B160 number.
So then I decided to reflash the rollback package...
That turned out to be a mistake... After flashing that (and it did show 100% successfull after flashing) the device is bricked. The Huawei logo shows and then nothing happens. The logo stays in the screen. I can't even turn the device off. Short pressing the ON-OFF button does nothing and long pressing just restarts the logo and nothing more.
I tried to reflash the MM update C432B160 with the three button technique, but that doesn't work anymore!! Entering erecovery with the volume up and ON-OFF also doesn't work anymore!! The only thing that works is Fastboot when connected to a pc. That screen shows phone (and bootloader) is locked, by the way. So I can't flash boot.img and recovery.img .
Has anybody encountered such problems and knows what to do now?? Thanks guys!
Click to expand...
Click to collapse
With fastboot method, unlock bootloader again. Flash recovery. Boot into recovery. Wipe system and boot. Flash stock boot IMG and recovery IMG. Power off. Use dload. Now you are in bootloop. When booting press vol up 3 seconds, on e-recovery press shutdown. Press and hold power and vol up. Go to stock recovery, do factory reset.
Sent from my NEM-L21 using Tapatalk
Thanks for your help.
Trouble is that I can't unlock te bootloader, because I do not know my Product ID and I can't look it up, since I don't have a dialer... The HuaweiProductIDGenerator doesn't help. I tried several codes with it, but none worked.
Liebaart said:
Thanks for your help.
Trouble is that I can't unlock te bootloader, because I do not know my Product ID and I can't look it up, since I don't have a dialer... The HuaweiProductIDGenerator doesn't help. I tried several codes with it, but none worked.
Click to expand...
Click to collapse
Power off, vol up+ power can you go to recovery?
Sent from my NEM-L21 using Tapatalk
Liebaart said:
Thanks for your help.
Trouble is that I can't unlock te bootloader, because I do not know my Product ID and I can't look it up, since I don't have a dialer... The HuaweiProductIDGenerator doesn't help. I tried several codes with it, but none worked.
Click to expand...
Click to collapse
Post here IMEI+SN and i try to get you bootloader unlock code.
Thanks! I sent you a PM.
Anonda said:
Power off, vol up+ power can you go to recovery?
Click to expand...
Click to collapse
No, I can only get into fastboot when connected to a pc.
OK. gtdaniel was so kind to provide me with an unlock code. THANKS!
But, I don't seem te be able to use it...
I can put the phone in bootloader when connected to a pc. When I type "fastboot devices" I do get the correct serial number. But when I type "fastboot oem unlock 343...338" I get a FAILED (remote: command not allowed).
It seems this is because I never could allow OEM unlocking from the Android settings menu. But since my phone is bricked, I can not enter into that menu!
Does anybody know how to solve this??
Liebaart said:
OK. gtdaniel was so kind to provide me with an unlock code. THANKS!
But, I don't seem te be able to use it...
I can put the phone in bootloader when connected to a pc. When I type "fastboot devices" I do get the correct serial number. But when I type "fastboot oem unlock 343...338" I get a FAILED (remote: command not allowed).
It seems this is because I never could allow OEM unlocking from the Android settings menu. But since my phone is bricked, I can not enter into that menu!
Does anybody know how to solve this??
Click to expand...
Click to collapse
u can try with
VNS-L21-L22-L31 Toolkit or
SRKToolHuawei-Lod-Chong-V2.0-20161002
But i dont know is that good idea to listen to me anymore
Thanks, but the Toolkit says it can't find the device.
Liebaart said:
Thanks, but the Toolkit says it can't find the device.
Click to expand...
Click to collapse
at command line when u write adb devices u got your phone ?
Maybe is dump question but did you install adb android driver ?
I'm pretty sure that someone wrote in thread that you don't need to have this oem permission in android if you are in fastboot
dragon218 said:
at command line when u write adb devices u got your phone ?
Maybe is dump question but did you install adb android driver ?
I'm pretty sure that someone wrote in thread that you don't need to have this oem permission in android if you are in fastboot
Click to expand...
Click to collapse
OEM permission need for fastboot/unlock bootloader.
Sent from my NEM-L21 using Tapatalk
Anonda said:
OEM permission need for fastboot/unlock bootloader.
Click to expand...
Click to collapse
Yes, that's what I read too. Since I can't change that permission anymore while I can't start Android, I can't unlock. Dammit.
Is DC Unlocker my only option then? It seems their software can do it.
I'm afraid I've got some pretty bad news. Last week the same thing happened to me after I was THAT stupid to actually try and flash the rollback package for the second time. My phone got bricked just like yours, and NOTHING worked to fix it. I tried completely everything I could find on the net and XDA, and in the very end I was forced to bring it in for warranty repairs. Even they COULD NOT fix it and the phone ended up with the entire logicboard changed with a completely new one. I was lucky that it all was done under warranty. Will never do anything as stupid as that!
Really hope you find a fix somehow, but if not, the repair service is your only solution, because otherwise the phone is as good as dead.
markositoo said:
I'm afraid I've got some pretty bad news. Last week the same thing happened to me after I was THAT stupid to actually try and flash the rollback package for the second time. My phone got bricked just like yours, and NOTHING worked to fix it. I tried completely everything I could find on the net and XDA, and in the very end I was forced to bring it in for warranty repairs. Even they COULD NOT fix it and the phone ended up with the entire logicboard changed with a completely new one. I was lucky that it all was done under warranty. Will never do anything as stupid as that!
Really hope you find a fix somehow, but if not, the repair service is your only solution, because otherwise the phone is as good as dead.
Click to expand...
Click to collapse
my phone is also reedy to send to service. I have a lot of phone with android but no rom make so many damage to my phone, like this fc** rollback. finger cross, because huawei service in my country without warranty,takes for new motherboard 175 $ . I bought phone for 233 $ with 3 gb ram..... This will be harsh and pay(in)ful lesson for me.
dragon218 said:
my phone is also reedy to send to service. I have a lot of phone with android but no rom make so many damage to my phone, like this fc** rollback. finger cross, because huawei service in my country without warranty,takes for new motherboard 175 $ . I bought phone for 233 $ with 3 gb ram..... This will be harsh and pay(in)ful lesson for me.
Click to expand...
Click to collapse
Uhh, I am sorry to hear that. But yes, I had the same harsh lesson. They will be forced to changed the motherboard too, cause even they won't be able to re-flash the whole system. Though, what I did to have the warranty not declined, is I brought the phone to the service and said that - "The phone received and OTA update through the updater, I didn't look much into it and just went with it, pressed on update and everything seemed well. It worked until the moment where it installed and restarted, and now the phone is stuck on Huawei logo and you can't possibly do anything with it, not even turn it off." - and that's it. They will have to repair it under warranty because there is no proof left that you had rooted it or done any other installations not authorized by Huawei.
Best of luck!
Liebaart said:
Yes, that's what I read too. Since I can't change that permission anymore while I can't start Android, I can't unlock. Dammit.
Is DC Unlocker my only option then? It seems their software can do it.
Click to expand...
Click to collapse
I know that i read somewhere how to manage to this oem lock. I was 50 % right.
https://forum.dc-unlocker.com/forum...61751-huawei-mate-9-mha-l29-erase-frp-problem
Some user got the same problem that you have and flash boot.
But truly if u don't have "your device has been unlock" only bootloop on huawei logo, is more simple to send it back to warranty and play dump.
I have now "your device is unlock" and i pray for miracle.
Liebaart said:
Hi All.
I hope someone can help me. I encountered this stupid problem:
I have a L31 device and successfully installed the Nougat (test?)update through Firmware Finder. But since this wasn't the definitive update, I decided to rollback to MM. I installed the C900B300 rollback package and then the B160 package. That went well, BUT the device now refused to activate the Google services. I couldn't enter a Google account. Not from Settings > Accounts and not from any other Google app like Chrome, Play Store, Gmail or others. The screen just kept returning to the Homescreen.
Upon checking About this device, I noticed the version now was C900B160, instead of the expected C432B160. I am very positive I used the C432B160 MM package to flash. This I did with the three button method. But then how come it still showed C900B160?
So I first tried to reflash the C432B160 with the three button method. Flashing worked well, but the problem wasn't solved. Still no Google activation and still the same C900B160 number.
So then I decided to reflash the rollback package...
That turned out to be a mistake... After flashing that (and it did show 100% successfull after flashing) the device is bricked. The Huawei logo shows and then nothing happens. The logo stays in the screen. I can't even turn the device off. Short pressing the ON-OFF button does nothing and long pressing just restarts the logo and nothing more.
I tried to reflash the MM update C432B160 with the three button technique, but that doesn't work anymore!! Entering erecovery with the volume up and ON-OFF also doesn't work anymore!! The only thing that works is Fastboot when connected to a pc. That screen shows phone (and bootloader) is locked, by the way. So I can't flash boot.img and recovery.img .
Has anybody encountered such problems and knows what to do now?? Thanks guys!
Click to expand...
Click to collapse
I am exactly in the same situation with the difference that I don't have Fasboot! How do you get to Fastboot? Mine hangs on the screen that says the phone is unlocked and the device is booting... Vol+/Vol- and Power doesn't boot into Fastboot and my minimal ADB doesn't recognize the phone in the stages that it hangs...
---------- Post added 16th April 2017 at 12:04 AM ---------- Previous post was 15th April 2017 at 11:52 PM ----------
I have the same situation. I tried everything, Three button method, letting the battery run out completely, Vol+ and Power, Vol- and Power, connected to PC, not connected to PC. Every time I disconnect the charger, and reconnect it starts from 0. I read some other people here have the same problem. Send it to warranty and explain your rollback process unlocked the bootloader somehow (I mean the phone does do a lot of sh*ty sh*t, so this shouldn't seem very odd as well!!!) and hope that you get a repair/replacement and after that sell it on ebay hoping some stupid people like us in the first place will buy it and spend your money on a phone more reliable!
I managed to access the fastboot using the 3 button method in cold boot. Hold the Power key until the screen goes off and then release and hold down the Vol- key and immideately connect the usb cable to PC right before it vibrates or exactly when it vibrates (it's a matter of timing), and bingo you are in fastboot and you can flash system.img, recovery.img, cust.img, cache.img and boot.img from there, but this is not how I revived my phone. I used the 3 button method again when the phone was charged for like half an hour or so and the did the same cold boot trick and I could boot into the force upgrade environment (strangely this still didn't work whitout connecting the usb cable to PC), but it somehow didn't want to read the UPDATE.APP that I had in dload folder on my SD card and wanted to have it from my PC (I just felt it nad there was no indication of it ) so then I installed the DC Phoenix tool and payed 15 euros to be able to inject the complete UPDATE.APP to my bricked phone and the installation went well to 99% and failed, but I rebooted the phone and I could boot normally. Just to make sure I did a factory reset afterwards. Hope this helps.
Cannot get into Bootloader
Hey there!
Essentially as stupid as I am i flashed the Rollback Image at Android 6.0 too, because i wanted to get rid of C900. So now my phone is stuck in the Startup screen too. As mentioned here, I wanted to unlock bootloader again; The Button combination does not work, and if I want to start in bootloader via ADB, it just says "waiting for device"
i am really desperate and i don't know what i should do now
Thanks for the help
EDIT: Somehow managed to got it into Bootloader. At the moment i am unlocking it. Where do i get TWRP and the needed things? Please help, i'm just some noob who doesn't know how it's done
EDIT2: Solved, got Stock Recovery Re-installed, Flashed with the Force Update Method the Main Package of the Rollback (so not the temp rollback data), and worked. But Still C900 and no Google sign-in possible. Someone know how to solve?
Hi!
So i treid to install the twpr recovery via srk tool huawei
after i unlocked the bootloader and reboot the phone i got the ÿour device is booting now screen and i cant do anything
i tried to restart the phone then press the vol down + the usb cable and doesnt work i still get the same screen
can't acces erecovery, can't enter fastboot, i can't do anything
what do i do now?
Nickoll_no1 said:
Hi!
So i treid to install the twpr recovery via srk tool huawei
after i unlocked the bootloader and reboot the phone i got the ÿour device is booting now screen and i cant do anything
i tried to restart the phone then press the vol down + the usb cable and doesnt work i still get the same screen
can't acces erecovery, can't enter fastboot, i can't do anything
what do i do now?
Click to expand...
Click to collapse
Device stuck in device is booting now ? or the 3 option screen ?
Kcetin20 said:
Device stuck in device is booting now ? or the 3 option screen ?
Click to expand...
Click to collapse
The device is stuck in the "device is booting now':crying:
Same Problem...
Nickoll_no1 said:
The device is stuck in the "device is booting now':crying:
Click to expand...
Click to collapse
BLN-L24N - Honor 6x
Sooo, I have the same problem , here's my story. Please help I've resorted to using a SGH-T599N... Its embarrassing... I'd almost rather have an iPhone...
So Little ol' me was messing around/ deleted google play services/ reboot to twrp to recover but device ended up bricked. At the time, still able to access fastboot. I flashed recovery and firmware. I then tried dload roll back method and when it cleared the phone bootloader locked. So I unlocked bootloader again but when device re-booted the following screen came up and still remains:
" ' Your device has been unlocked and cant be trusted. ' -- ' Your device is booting now... ' " (No options are available.)
I eventually tried to restart to fastboot or erecovery BUT Everytime I try to power down the device, it tries to power up again but needs to charge for a minute before trying to boot itself back up. .(even after being on the charger for hours this happens). The problem with that is I can't get into fastboot or force dload because it automatically starts itself/ has to be plugged in until it turns back on. (Yes i've tried button mashing/ button holding/ etc. did not help)
How do I get the phone to charge, without it booting up? I have a feeling that if I can get it to start (without it first having to charge) I can get it to fastboot/ or erecovery. I have already tried to let the battery COMPLETELY drain.
Outside of that, I know the whole roll back and dload stuff. Currently it flashes the honor logo screen and then sits at "Your device is booting now..."
Bootloader is unlocked
OH! I should clarify, it boots on its own. I've tried disconnecting the battery, having it on the charger without the
battery. With the battery, Starting phone up by re-connecting the battery. No positive results
I'm about to start messing around with firmware flashing utilities, I just don't know of any. I wish there was a way to flash without being in fastboot mode. (I know very little of perl/python/linux, but I am a quick learner if you point me in the right direction.
Thank you in advance
MSDB714 said:
BLN-L24N - Honor 6x
Sooo, I have the same problem , here's my story. Please help I've resorted to using a SGH-T599N... Its embarrassing... I'd almost rather have an iPhone...
So Little ol' me was messing around/ deleted google play services/ reboot to twrp to recover but device ended up bricked. At the time, still able to access fastboot. I flashed recovery and firmware. I then tried dload roll back method and when it cleared the phone bootloader locked. So I unlocked bootloader again but when device re-booted the following screen came up and still remains:
" ' Your device has been unlocked and cant be trusted. ' -- ' Your device is booting now... ' " (No options are available.)
I eventually tried to restart to fastboot or erecovery BUT Everytime I try to power down the device, it tries to power up again but needs to charge for a minute before trying to boot itself back up. .(even after being on the charger for hours this happens). The problem with that is I can't get into fastboot or force dload because it automatically starts itself/ has to be plugged in until it turns back on. (Yes i've tried button mashing/ button holding/ etc. did not help)
How do I get the phone to charge, without it booting up? I have a feeling that if I can get it to start (without it first having to charge) I can get it to fastboot/ or erecovery. I have already tried to let the battery COMPLETELY drain.
Outside of that, I know the whole roll back and dload stuff. Currently it flashes the honor logo screen and then sits at "Your device is booting now..."
Bootloader is unlocked
OH! I should clarify, it boots on its own. I've tried disconnecting the battery, having it on the charger without the
battery. With the battery, Starting phone up by re-connecting the battery. No positive results
I'm about to start messing around with firmware flashing utilities, I just don't know of any. I wish there was a way to flash without being in fastboot mode. (I know very little of perl/python/linux, but I am a quick learner if you point me in the right direction.
Thank you in advance
Click to expand...
Click to collapse
So on ny phobe the mainboard is dead so i guess the internal storage is corrupted
I need to change that and i guess you need too...
It's not so expensive(like 40$ for my phone)
Nickoll_no1 said:
So on ny phobe the mainboard is dead so i guess the internal storage is corrupted
I need to change that and i guess you need too...
It's not so expensive(like 40$ for my phone)
Click to expand...
Click to collapse
do you have a part number?
MSDB714 said:
do you have a part number?
Click to expand...
Click to collapse
I dont think i was to a local service...it' s not so expensive but it's not cheap either
Mi A1 bricked, hard resetted it by opening the back cover and shorting two points.
It gets detected by mi flash tool but I cannot flash the stock room. It is giving me "cannot receive hello packet" and then it times out.
Any help will be appreciated.
Thank you.
I'm in the same boat, it's showing up in device manager under ports (COMS & LPT) and in flash tool, yet i cant flash anything
Any help for us?
foggs said:
I'm in the same boat, it's showing up in device manager under ports (COMS & LPT) and in flash tool, yet i cant flash anything
Any help for us?
Click to expand...
Click to collapse
It was solved after I changed the USB port on laptop. I got far as installing tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794 image and booting to fastboot and then TWRP. But after flashing AOSP extended rom it gave me "The system has been destroyed" screen. And somehow recovery is not staying. It apparently gets wiped after reboot.
udaan said:
It was solved after I changed the USB port on laptop. I got far as installing tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794 image and booting to fastboot and then TWRP. But after flashing AOSP extended rom it gave me "The system has been destroyed" screen. And somehow recovery is not staying. It apparently gets wiped after reboot.
Click to expand...
Click to collapse
I've also tried different ports, still the same message of the hello packet thing. Also when I have the phone connected to the computer I've a white led light blinking.
From reading other threads here and Xiaomi site the deep flash cable opens the com port, I already have this but won't work. There was something about a loader.img, flashing this to an sdcard and holding power and vol down button it then should boot the loader IMG and rescue the phone, this also fails for me.
foggs said:
I've also tried different ports, still the same message of the hello packet thing. Also when I have the phone connected to the computer I've a white led light blinking.
From reading other threads here and Xiaomi site the deep flash cable opens the com port, I already have this but won't work. There was something about a loader.img, flashing this to an sdcard and holding power and vol down button it then should boot the loader IMG and rescue the phone, this also fails for me.
Click to expand...
Click to collapse
Yup, I ruined one of my usb-C cable trying do do deep flash that way. I failed, so I went to one repair shop and open up the device and did the "two point short thing", which helped to be recognized by the flash tool. Then it showed me that "hello packet" thing.
Then I dug around the Internet for couple of hours and changed the USB port on laptop. I also restarted the laptop after I reinstalled the drivers. Then it actually flashed that ROM I mentioned above. But just that ROM. I tried the latest to oldest versions and all of those ROM would flash but then they will brick the phone again. Only that one worked, i.e. helped me to get to bootloader. But alas it is stuck there, no matter how many times I clean flashed it, it is refusing to boot to system. It gives me "Your SYSTEM HAS BEEN DESTROYED" message on every boot. It only goes to bootloader if I press Volume Up + Power button while booting. And it's a dead end for now. I don't know what else to do.
Also this phone was bought in Hong Kong and its warranty won't work where I am right now. I already took it to the authorized service center and those lazy people told me to change the motherboard and it will cost around $180. So I took it back. lol
Disable driver enforcment to get the hello packet.
TrueMS said:
Disable driver enforcment to get the hello packet.
Click to expand...
Click to collapse
still no hello packet
Your timeout for edl mode has passed
You must press power button for 10-15 sec to power cycle the phone
Or open it up and remove battery socket
Or wait for battery drained out
And after that edl will accept hello package
emprazol said:
Your timeout for edl mode has passed
You must press power button for 10-15 sec to power cycle the phone
Or open it up and remove battery socket
Or wait for battery drained out
And after that edl will accept hello package
Click to expand...
Click to collapse
:victory: Held the power button, clicked flash.. Success :good: it's in the process of flashing now. Thank you
Edit: successful flash now to just let it charge up. Thanks again guys for the help/suggestions ?
Update, i flashed the Oreo stock it gave my a successful flash, let the phone charge to near full. Booted the phone up, got as far as sending information to Google option and the screen became non responsive and the phone rebooted, it did this a few times and I gave up and put it in fastboot mode.
I did another flash using a different option clean flash still with Oreo ROM, I think first time I did it with keeping data not 100% though.. but ended up with the same result of it going into random reboots at different points in the setting the phone up stage.
I've now tried two 7.1.2 stock ROMs with the same results ???
I'll try a custom ROM tomorrow see if that sorts it, if not I'm out of ideas. So freaking close ?
foggs said:
Update, i flashed the Oreo stock it gave my a successful flash, let the phone charge to near full. Booted the phone up, got as far as sending information to Google option and the screen became non responsive and the phone rebooted, it did this a few times and I gave up and put it in fastboot mode.
I did another flash using a different option clean flash still with Oreo ROM, I think first time I did it with keeping data not 100% though.. but ended up with the same result of it going into random reboots at different points in the setting the phone up stage.
I've now tried two 7.1.2 stock ROMs with the same results ???
I'll try a custom ROM tomorrow see if that sorts it, if not I'm out of ideas. So freaking close ?
Click to expand...
Click to collapse
Ur presist partition is damaged..thr are many guides here about recovering it
Do the "factory flash" mode in MiFlash under EDL mode as a last resort. May wipe your IMEI and MAC's, not sure.
Could not receive magic packet is solved by using USB2 port, Windows 7 x86 (32-bit) in a VM, or power-cycling the device and starting over, any or all of the above.
Deep flash cable is only for kicking the phone out of diagnostic mode and into QDFlash mode. Not necessary if using test point. I had to use testpoint method myself, couldn't get deepflash cable to work for getting out of diagnostic mode. I hope I can get it working next time though when I inevitably brick it from repartitioning; as I broke my screen when disassembling
apexashwin said:
Ur presist partition is damaged..thr are many guides here about recovering it
Click to expand...
Click to collapse
No luck with flashing the persist.img either from 7.1.2 or 8.0 stock ROMs. I used the fastboot method and twrp with both ROMs.
I've tried the factory flash with 8.0 ROM in miflash tool this to hasn't solved the problem. It reboots on the set up I unlocked the bootloader to boot twrp flashed persist it reboots as far as bootloader unlocked screen and it stays there. ?
I'm guessing even flashing a custom ROM will do nothing either?
foggs said:
No luck with flashing the persist.img either from 7.1.2 or 8.0 stock ROMs. I used the fastboot method and twrp with both ROMs.
I've tried the factory flash with 8.0 ROM in miflash tool this to hasn't solved the problem. It reboots on the set up I unlocked the bootloader to boot twrp flashed persist it reboots as far as bootloader unlocked screen and it stays there. ?
I'm guessing even flashing a custom ROM will do nothing either?
Click to expand...
Click to collapse
Did you find the guide about fixing constant reboot? It's around somewhere, might be on MIUI forum.
foggs said:
No luck with flashing the persist.img either from 7.1.2 or 8.0 stock ROMs. I used the fastboot method and twrp with both ROMs.
I've tried the factory flash with 8.0 ROM in miflash tool this to hasn't solved the problem. It reboots on the set up I unlocked the bootloader to boot twrp flashed persist it reboots as far as bootloader unlocked screen and it stays there. ?
I'm guessing even flashing a custom ROM will do nothing either?
Click to expand...
Click to collapse
Please try presist resurrector from guides section
I think i've got it back to life.
first tried to flash 7.1.2 stock the earliest one (tissot_images_7.8.23_7.1), it hung on flashing it for nearly an hour with no success, closed the miflash application then tried another 7.1.2 (tissot_images_7.10.30_7.1)flash successful, then in stalled twrp did the persist command and reboot nearly got to the home screen just never getting over the line. then i flashed January 8.0 oreo (tissot_images_8.1.10_8.0) and was able to get on to the home screen/go into settings/enable developer options but it would eventually reboot itself, went back into twrp and did the persist command again and reboot.. success (fingers crossed) now downloading/applying April security update as i type this.
Boo installation problem with the update
looks like i lost my imei, https://forum.xda-developers.com/mi-a1/how-to/guide-how-to-restore-imei-permanently-t3759190 this is going to be a pain.. i'll post back when i try this. need a break from this mess ive made lol
thanks for the help/suggestions appreciated big time.
edit: up to the latest update April 1 security patch.
all done, down to 7.8.23 rom, did the stuff to get the imei back then flashed latest oreo rom
emprazol said:
Your timeout for edl mode has passed
You must press power button for 10-15 sec to power cycle the phone
Or open it up and remove battery socket
Or wait for battery drained out
And after that edl will accept hello package
Click to expand...
Click to collapse
Man, I was trying to fix my Redmi Note 4X for the past 6 hours and you were the ONLY guy to talk about this. Thank you so much. :victory:
THANK YOU
udaan said:
it was solved after i changed the usb port on laptop. I got far as installing tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794 image and booting to fastboot and then twrp. But after flashing aosp extended rom it gave me "the system has been destroyed" screen. And somehow recovery is not staying. It apparently gets wiped after reboot.
Click to expand...
Click to collapse
man you just solved my problem and saved for me like 180 eur thank you you are a god !!!! Thanks for using this site !!!!!!!!!! <3 <3 <3
udaan said:
It was solved after I changed the USB port on laptop. I got far as installing tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794 image and booting to fastboot and then TWRP. But after flashing AOSP extended rom it gave me "The system has been destroyed" screen. And somehow recovery is not staying. It apparently gets wiped after reboot.
Click to expand...
Click to collapse
I was unable to flash on MiFlash and after changing USB port I managed to do it!.
Many thanks!
emprazol said:
Your timeout for edl mode has passed
You must press power button for 10-15 sec to power cycle the phone
Or open it up and remove battery socket
Or wait for battery drained out
And after that edl will accept hello package
Click to expand...
Click to collapse
I love you!
I chose wrong option installing magisk and i got bricked phone. I know i am dumb. When I turn phone logo nothing appears and small information press any key to shutdown. I've tried enter by key combination, but as it says it shutdowns. Cmd/Terminal my phone is not being recognized. Is there any option to restore phone?
I'm on same boat after try installing custom rom this happened is well don't know how to fix this without fastboot mode .
Maybe keep phone like this turned on until its die I don't know man would be nice if anyone able to fix that.
When the phone is off, keep pressing volume down and the power button till you are in the bootloader. With installing magisk you wont brick your bootloader normally.
Had the same issue
nickholtus said:
When the phone is off, keep pressing volume down and the power button till you are in the bootloader. With installing magisk you wont brick your bootloader normally.
Had the same issue
Click to expand...
Click to collapse
It's not a solution, keys are binded to turn off
So when the phone is completely off, you press the power and volume down. What happens then?
Please post a picture of the message your phone gives
nickholtus said:
So when the phone is completely off, you press the power and volume down. What happens then?
Please post a picture of the message your phone give
Click to expand...
Click to collapse
Pressing power will display "Nothing logo" and the phone will turn off at that moment (due to volume - being pressed)
icetea250 said:
Pressing power will display "Nothing logo" and the phone will turn off at that moment (due to volume - being pressed)
Click to expand...
Click to collapse
DId you try to hold the keys for a long time? This is what did the trick for me on my last phone (Oneplus 8 Pro)
If you holding any buttom when it's boots up it's just turns off any combination don't work. Pc don't see phone.
I'm in the same situation. Bootloader ( with flashing critical ) unlocked, rooted with magisk on EEA 1.1.4. I'm tried to upgrade to 1.1.6 ota. I'm on slot A Turned off magisk modules and fllashed back to stock 1.1.4 bootloader. ( still on slot A ) Rebooted but can't update ota from phone. Then tried manualy it gave error 20 message, tried with sideload it gave me unexcepted update file size message, nothing worked. Then, I'm switched slot from A to B. But after that powering up the phone, just nothing logo showed and the top left corner text say: key to shutdown.... Can't enter fastboot or recovery, pc dont see anything, wall charger doesnt work to...
lba810701 said:
I'm in the same situation. Bootloader ( with flashing critical ) unlocked, rooted with magisk on EEA 1.1.4. I'm tried to upgrade to 1.1.6 ota. I'm on slot A Turned off magisk modules and fllashed back to stock 1.1.4 bootloader. ( still on slot A ) Rebooted but can't update ota from phone. Then tried manualy it gave error 20 message, tried with sideload it gave me unexcepted update file size message, nothing worked. Then, I'm switched slot from A to B. But after that powering up the phone, just nothing logo showed and the top left corner text say: key to shutdown.... Can't enter fastboot or recovery, pc dont see anything, wall charger doesnt work to...
Click to expand...
Click to collapse
Same situation but i unlocked without flashing critical and i tried changing magisk method.
Any solution? happend
lba810701 said:
I'm in the same situation. Bootloader ( with flashing critical ) unlocked, rooted with magisk on EEA 1.1.4. I'm tried to upgrade to 1.1.6 ota. I'm on slot A Turned off magisk modules and fllashed back to stock 1.1.4 bootloader. ( still on slot A ) Rebooted but can't update ota from phone. Then tried manualy it gave error 20 message, tried with sideload it gave me unexcepted update file size message, nothing worked. Then, I'm switched slot from A to B. But after that powering up the phone, just nothing logo showed and the top left corner text say: key to shutdown.... Can't enter fastboot or recovery, pc dont see anything, wall charger doesnt work to...
Click to expand...
Click to collapse
Same happend to me, except i was on 1.1.5.. any solutions yet?
Sadly no... I'm wrote to custom service, and after some letters and pictures they sad, send them the phone to repair. Tomorrow i will send it. I hope they could make it back to life again
Did you tell them that you have root and unlocked it? Or what had happened? I think mine has to be turned in too
lba810701 said:
Sadly no... I'm wrote to custom service, and after some letters and pictures they sad, send them the phone to repair. Tomorrow i will send it. I hope they could make it back to life again
Click to expand...
Click to collapse
Could you please tell me what message you received and the cost of the repair? I am thinking of sending mine in for repair and would like the information.
I'm wrote to them, my phone can't boot, can't connect to the pc because doesn't recognize it and wall charger doesn't works to. Boot stops at nothing logo and there's a text at top left cormer " key to shutdown ". I'm don't wrote anything about root. First letter they said make a factory reset, then I'm wrote back I can't do that and then I'm sent a picture about the problem. After it next letter, who saw the picture thinks it's maybe a technical error and if I'm accept it, send the phone to service center and they check it out. I hope they could repair it and not change it, because I haven't got any green tint issue, or any dust under back of the phone's glass... About the repair cost, if the problem can't resolve they send me a new phone. If I made a problem, then I must pay the phone shippings cost to them and back to me and the service center call or write me about the repair costs i want it or not.
Hope someone will find soliution for this or it's hardware problem.
Same issue!
tegazinho said:
Same issue!
Click to expand...
Click to collapse
Looks like a lot of people getting this problem on this phone.
Any news on this problem?