[Solved] Bricked? What can I do? - Honor 7 Q&A, Help & Troubleshooting

Hi everyone,
I am having a strange issue here. I updated to MM Beta using the Local Update Method. Update went fine, told me everything was ok.
Well, as soon as the screen turned on, I noticed that nothing was ok. The Honor logo appears, then it goes to System boot and stays there.
I didn't unlock the bootloader neither did I root it, which means everything is still original.
My problem now is, I can't do anything in the sense of:
Not possible to do a rollback, Install Fails
Not possible to install a Full Official Firmware UPDATE.APP, Install Fails
Not possible to use fastboot to flash images of course since I did not unlock it
Not possible to use the USB HiSuite Recovery method (Connect to USB and power on while pressing volume+) because it reboots instantly after showing me the "Download Update" button
I tried with several different Versions of the Firmware for PLK-L01, but nothing seems to work.
I already wrote an email to the Honor Support, but of course it will take time to answer and I don't have any other phone right now.
Should I unlock the bootloader by using the Code generated by the Huawei Website? If yes, how can I retrieve the information if the phone is not booting?
Or should I do something else?
It looks like nobody was or is in the situation I am, because everyone was able to resolve. I tried already everything that I could search and think of.
I appreciate if someone takes the time to help me since I ran out of Ideas.
And of course
Merry Christmas to everyone

Well I called support, and of course they want me to send them the phone.
Does anyone have experience in flashing the extracted firmware directly to the phone?
If I am able to unlock the bootloader, is it worth it trying? Or am I going to screw up stuff even more?

unlocking the bootloader may not help you* - and if you're sending it back, it will help you even less!
you can only flash boot, system and user from Huawei bootloader, it's a sh!t bootloader to be honest, you'll have modem and other bits from the MM flash.
did you place the rollback onto an sdcard in a directory called "dload", insert the card then do the "three button combo"?
turn it on holding vol + / vol - and power, keeping them held until the firmware updater is displayed - it should then force the downgrade.
this leaves you with an unusable phone so you then need to place the UPDATE.APP from B121** in this same sdcard directory and do the same again
You can then do B121-B140 via local update on the working phone..
* - actually unlocked bootloader saved me, flashed B121 system and user and rollback package worked
** - possibly B100 and work your way up

sminki said:
unlocking the bootloader may not help you* - and if you're sending it back, it will help you even less!
you can only flash boot, system and user from Huawei bootloader, it's a sh!t bootloader to be honest, you'll have modem and other bits from the MM flash.
did you place the rollback onto an sdcard in a directory called "dload", insert the card then do the "three button combo"?
turn it on holding vol + / vol - and power, keeping them held until the firmware updater is displayed - it should then force the downgrade.
this leaves you with an unusable phone so you then need to place the UPDATE.APP from B121** in this same sdcard directory and do the same again
You can then do B121-B140 via local update on the working phone..
* - actually unlocked bootloader saved me, flashed B121 system and user and rollback package worked
** - possibly B100 and work your way up
Click to expand...
Click to collapse
Yes, did it. It always says Failed to Update.
Neither the rollback, nor a complete Firmware works. I really don't know what to do.
On the phone they told me that it is normal that this happens, so I am quite questioning the quality of the Update service of Huawei Honor.
Still they want to cover it over the Warranty, but it will take a lot of time. And I seriously need a phone ASAP.
Any other advices maybe?
Thanks for the support anyway :good:

So, I was able to get my phone to boot back by unlocking the bootloader and flashing the B100 Firmware (Like described here)
The phone booted finally, the only problem is the Sim card not being recognized, probably because of the MM MODEM.
Now I will try to flash another full Firmware to see if I am able to get the modem back.
Otherwise I was thinking of flashing the TWRP recovery and creating myself a flashable MODEM from the UPDATE.APP of the B100. Will that work or is it influenced from the bootloader too?

the bootloader has limited end-user commands i don't think you will be able to flash "modem"

sminki said:
the bootloader has limited end-user commands i don't think you will be able to flash "modem"
Click to expand...
Click to collapse
Thank you, I was able to recover my phone completely in the end with a different approach.
I just used and flashed the B130 Full Firmware through the Vol+ Vol- Power combination. Even though it said it failed, it actually works flawlessly. The phone works even better than before.
I was scared I would not be able to recover it, but with an unlocked bootloader and the right tools, everything is possible.
So thank you again @sminki, and thanks to all of the XDA Forum members who published tools like Huawei Update Extractor and the single firmware files.
:good::good::good::highfive:

that's great news, welcome back!

Related

[Q] ill pay money for help. brick

LG C800
Device will not enter fastboot.
Can't get into recovery mode.
Each time it boots it hard resets. There is an unofficial CWM Recovery Rom on this forum from chui101 which is for this exact phone, but I have as of yet not had any luck in getting the phone to take it.
So far i've tried Flash_image recovery.img (renamed chui's CWM recovery file to recovery.img)
Doesn't seem to matter what I do the phone starts(LG on screen), resets (the LG goes away for a sec then comes back), does a hard reset (a white box with an arrow pointing out of it an to a little android), again resets the phone one last time for a "normal" boot.
I've tried a few different things to try and flash anything overtop of the stock recovery but nothing works. It seems like very early in the bootstrap is a command to do a hard reset and anything that gets put in AFTER that command is ignored. (And the phone hard resets and anything else it was supposed to do is gone.)
Device is rooted with SuperSU.
Phone is fully functional except that it hard resets every boot, and if its plugged in when off it doesn't go to a charging screen, it starts the phone 100% up.
Adb devices CAN see the phone.
I CAN get into Download (sometimes called Emergency) mode.
"reboot recovery" doesn't do anything but reboot the phone as described above.
I can't afford a new phone guys, so I'm over a barrel at this point.
i'll pay whoever provides meaningful help in getting this thing fixed.
You should start fresh. So, flash the stock rom FTF of your phone, then the phone should boot up normally. Then you could either root it and install a CUSTOM recovery, or flash a pre-rooted custom kernel that already contains a recovery. From there, just flash the custom rom you want
Just press thanks if I helped, no need for money
stock rom FTF?
From the factory?
I'd love to do that. But am bewildered as to how when every guide I've found says use fastboot -- which doesn't work on my device. And every guide without fastboot thus far has not worked. I've been reading 10 hrs a day for the last 3 days looking for a solution to this.
If there was a way to completely wipe the entire phone and then install stock rom I'd be glad to do it.... I have found no such guide... only those to replace recovery. (not a 100% clearing as if it came right off the line with no software yet installed)
Additional information:
mv /system/recovery-from-boot.p /system/recovery-from-boot.p-bak
Spits out a "No such file or directory" error
I don't know about you, but for Xperia Devices there is a PC software called Flashtool to flash stock roms and custom kernels and stuff from the PC. There should also be a software like that for your device. You just download the stock FTF for your phone (just type in google "download stock FTF for LG C800") and flash it in Flashmode that should be working
One more thing, this issue is not called bricked
press thanks if i helped
There is an LG tool but it says current software is up to date.
Other option is run recovery, which just reboots the phone as is.
No, this software I am talking about is not made by LG or Sony in my case. It should be a general tool for all LG devices. it should root, flash, install busybox, etc......
blakstar said:
No, this software I am talking about is not made by LG or Sony in my case. It should be a general tool for all LG devices. it should root, flash, install busybox, etc......
Click to expand...
Click to collapse
LG MOBILE SUPPORT TOOL ?
Thats the one that so far doesn't work.
the one named:
KDZ_FW_UPD_EN ?
He doesn't appear to support GSM phones. Plus I hit "Read info from phone" button... it gets almost everything -- correctly -- then crashes.
IT wants kdz files... looking for them now... chui has a dl link for the stock recovery but even though its a few mb it looks like only a zipped folder hierarchy with no files.
Slightly mis-read. still not finding any "generic" flashing software
trying octopus now....
crashed....
run as admin..... ah... you need their hardware which is hundreds of dollars...
Flash image gui, phone is not supported.
ok, a couple cyanogen dev's have both told me i'm screwed. Imma try for the rest of today and then just never turn it off again.
ok, paying lg to fix it... anybody guess what that will cost?
Try flashing CyanogenMod on your phone as no stock firmware is avaiable currently for your phone cyanogenmod shall fix the problem and you should boot normally (first flash CWM)
http://forum.xda-developers.com/showthread.php?t=1752704 - flashing cwm recovery (do it!)
Flashing cyanogenmod (requires usb debugging on)
First to put the cyanogenmod rom in the sdcard use adb push - http://forum.xda-developers.com/showthread.php?t=1667929
Page 1 (Pre Requisites - http://droidnoob.com/update-lg-c800-to-android-4-0-4-ics-via-cm9.html
Page 2(The actual flashing part :victory - http://droidnoob.com/update-lg-c800-to-android-4-0-4-ics-via-cm9.html/2
Probably will fix the problem....
hi techmasta,
I'd love to flash cyanogenmod, but the phone never enters fastboot to flash anything. The first link you posted says to use fastboot. I can't do that. The phone doesn't goto fastboot, it runs its recovery first.
EDIT: if there is a way to force it while the phone is in download mode that could probably work.
secondly, I've spend more than 40 hours on this issue, mostly reading forums but still a great deal on google.
I'm pretty unhappy with google as neither of those droidnoob forums ever come up. And believe me, there isn't much out there referring to the lg c800 so they should have!

I'm Not Even Sure What This Is SONY XPERIA Z2 TABLET -VERIZON- POSSIBLE BRICK?

Hey guys, please forgive me for any bad etiquette or lack of information (any information I can provide is available upon request if I leave anything out). I am new to forums in general and especially to XDA, which seems like a good place to get help.
I recently purchased a Sony Xperia Z2 Tablet from Craigslist under the assumption it was a fully unlocked tablet not associated to a carrier. Turns out it was a Verizon Z2 tablet. I dislike Verizon with a firey passion and without getting into too many details, I'm fairly certain they won't help me because a) this tablet wasn't purchased through them as a customer and b) Verizon and I have bad history (unauthorized account modification, shady charges, etc.)
So I thought I'd do my best to make the tablet mine since the asshole who sold it to me has ceased all contact and I don't know how to get a hold of him anymore. No receipt and a data-less tablet.
Anyway, I successfully rooted the tablet and began installing apps that I installed for my G4 when I rooted it (SuperSU, Adaway, Greenify, etc.)
Things were going well but I realised I wanted anything that had to do with Verizon removed from the tablet so I was going to flash Cyanogenmod onto it with a guide I found online. Now rooting and installing custom recoveries was familiar territory and I did these flawlessly. It had TWRP and I made a backup of the system -no Nandroid, sadly-and I began the flashing process. The process said it completed without issue and I went to reboot my device. Enter my current situation:
The device, when I attempted to turn it on, all it did was vibrate constantly until I let go of the power button. Attempting to enter recovery mode (green LED, power + vol down) it showed me, instead of TWRP, a very basic recovery mode with basic options. "Continue booting up", "enter safe mode", "system recovery", and "power down". I tried entering safe mode and it just shut back down, I tried doing a system recovery and it shut down. The only time I ever see the "SONY" logo is if I'm entering this mode. I can enter what I assume is "fastboot mode" (power + vol up and plugging the device into a PC). Nothing on the screen but the LED is blue. I am trying to find guides to restore it if I can and it all looks promising but the only things I know how to really do are root and install custom recovery. I know there are PC tools I can use to send commands to it while it's in fastboot, or send commands in general I just don't know where to begin.
Does anyone know how to fix this? I know it was from Verizon, which sucks, and I know the problem most likely occurred with the attempted flashing of Cyanogenmod. I think I read somewhere I might have done something regarding mismatching kernal numbers. I couldn't find a way to unlock the bootloader so I assume that had something to do with it too.
If someone could give me a guide to restore it to at least its stock ROM where I can begin rooting and installing a custom recovery again, that would be great. Even better would be just flashing a ROM on there that doesn't need Verizon or being able to take it to a stage where it's unlocked and the only evidence it was ever with a carrier is the Verizon logo on the back. I'd really hate to think I wasted money on this and now I'm at a dead end because of a mistake I made. This was supposed to be a gift for my mom on her birthday which is coming up soon. So if anyone knows anything, or has a guide where we can at least get the thing bootable again and I'll just try and deal with a rooted locked device, that would be great.
Thanks for considerations,
Marmalade_Shaws
I have spent time on that screen too.
2 things
1. .. If you installed dual recovery, there is an up, down sequence to select the recovery.
2. Find a downgrade guide, use flashtool to flash. Ft back to stock.
Also you need to know what hardware you are running..511, 561.. And use the proper version.
There are some options with the flashtool and prf maker that can remove branding and vendor stuff. I have not tried those options.
Ez-go said:
I have spent time on that screen too.
2 things
1. .. If you installed dual recovery, there is an up, down sequence to select the recovery.
2. Find a downgrade guide, use flashtool to flash. Ft back to stock.
Also you need to know what hardware you are running..511, 561.. And use the proper version.
There are some options with the flashtool and prf maker that can remove branding and vendor stuff. I have not tried those options.
Click to expand...
Click to collapse
Sorry if this is late... But where can I find the stock? I've searched everywhere and I would need to do it from a flash tool on my PC? I could use all the help I can get.
I just had a very similar experience to the OP, seemingly identical in every way, and am curious if anyone has a solution.
ADB won't function at all, and the bootloader has blocked any sort of flashing via fastboot. Can't boot into TWRP, it goes into a very minimal "recovery," which I imagine is the stock tool, and the Factory Restore option there does absolutely nothing. Flashtool would work great if ADB / Flashmode was at all functional (device blinks and vibrates in a fashion typical of something bricked, and no connection is picked up).
Verizon Z2 Tablets are 561s.
This thing dead or is there some way to push back onto it?

What worked for me to fix: The frp lock Soft-brick (using Samsung Smart Switch)

This will save you 8-12 hours of your time if you are lucky. This means that it also includes the meaningful links of 8-12 hours of searching. Sentences in italic are important. 1 link is for the Odin official website, the rest are re-links back into XDA.
The device in question is a SM-925T Tmobile S6 Edge.
The problem was this. I rooted my phone and messed around with Greenify and the Play store. To prepare for rooting, I allowed unknown downloads, unlocked the bootloader, and turned my security lock off (I had set it to a finger print lock). After I was done rooting, I immediately locked the bootloader again(<--A mistake that caused my bootloop/ soft-brick). After I was finished messing with the above apps (Greenify, etc), I wanted my phone to restart. So I held the Power button and selected restart, while I was on the lock screen (may not be important). I noticed that it took a long time to restart, and upon closer examination, I noticed another error under the "kernel is not seandroid enforcing" (which appears to be natural for rooted phones). The error was "Custom Binary blocked by FRP Lock". It was a new error. I investigated this new problem using the internet , and this dude was panicking like hell, but he didn't appear to fix his problem. He did hint that returning to the bootloader to its locked state was a mistake. Looked a bit more and this guy pointed to another thread, which introduced me to flashing and more importantly his fix, which was to flash the stock 5.1.1 image through odin. He used this link, which contains all the stock firmware for the majority of the new Samsung S6 and S6 edge versions. To make a long story short, most of these fixes involved flashing your firmware to the stock version. So I went to the Odin Website, and downloaded every version, as a couple threads have said that different versions worked for them. Here is a thread with everything you need for Odin. Now, after sorting through and finding micro USB cables that are detectable by Odin, an important step because Odin might develop a pattern of detecting then failing to detect your device through that cable, and testing all the usb 2.0 ports, I was ready, and had Odin with my stock firmware. Odin kept saying "NAND Write", then in the next line "FAIL". This was annoying as Odin wouldn't detect my device again unless I unplugged it, restarted it to download mode, then restarted Odin before plugging it back in. I got confused and found links for somehow fixing the .tar files, stock roms, .pit files (DO NOT MESS AROUND WITHOUT KNOWING WHAT THOSE THINGS DO), and other threads/websites that say to boot into recovery mode , factory reset, then wipe your cache. I could only do that once. After me messing around with all of the above file variants and supposed fixes to help with my issue, I couldn't boot into recovery mode, it got stuck on the "Samsung Galaxy S6 Edge" logo. It did not fix the NAND write failing. There however, are a lot of websites allowing you to download stock software for your phones, and I don't think I can link them as it might break a rule. Surprisingly, some have claimed that using a stock file for another device worked to fix their problem. This thread, which convinced me to use Smart Switch when it failed for everyone else, was very useful, although I recommend downloading Smart Switch from the official website of Samsung. None of the Odin flashing had worked so far, including the Roms and .pit files so I tried Smart Switch. I opened it, and upon selecting the "more" tab on the upper right corner, a bunch of tabs drop down. One should be "Emergency Software recovery and initialization". I had to find my S / N (Serial) number, and I was very confused on how to obtain that number as I was locked out. But to obtain it, do the same process to boot into download (hold volume down, home key, and power key), but stay on the prompt and don't go to the screen that has the word download in the middle. Don't do anything other then reaching the prompt confirming if you want to install a custom ROM. Then, press the home key and it should show your S / N number along with your IMEI number. Once I imputed the code I saw on my phone into Smart Switch, it told me to connect the device. Now, by this time, I realized that Odin only detects my device if it is actually in the download screen. Why shouldn't my computer? I booted into Download on my phone and followed the steps on my computer, making sure that the computer can recognize my phone while it is using a valid USB port and Cable. And after some waiting, for me, my problem was fixed and I could use my phone again, it reverted to it's out-of-box state. I hope this drawn out but very specific explanation helps you guys. It's my first post And also, this thread confirms that you can use a USB hub for flashing(at least for ROMS), Smart Switch, and for rooting.​
Thank you for this detailed account, however nothing of the above has worked for me. Odin won't flash the firmware of 5.0.2 (and I tried 5.1.1) and Smart switch does not recognize the device to do anything. BTW phone has been rooted for months and last night decided to turn on its FRP lock randomly and now I'm stuck. Any help would be greatly appreciated.
Explain throughly what you have tried. Especially different ports, cables, and computers. Did you have the right device drivers? Did you do anything else?
I followed your footsteps and and the step where it has to show me the S/No and IMEI, it only shows IMEI number. I am unable to find the S/NO any suggestions?
Xalmey said:
I followed your footsteps and and the step where it has to show me the S/No and IMEI, it only shows IMEI number. I am unable to find the S/NO any suggestions?
Click to expand...
Click to collapse
press vol down home keys and power key once you get to the first blue screen release vol and power keep holdind home but I already tried smart swich didn't help
5.1.1 has FRP lock auto turned on whenever you have a google account on the device... This is probably going to cause a lot of problems with all newer devices that get rooted. I even tried removing all google accounts, flashed recovery and flashed boot img back to stock after rooting and still FRP was bricking the device. I got supersu onto the device, all working fine for a 3rd time, as soon as I added a google account onto my device and restarted, it was FRP lock blocked and soft bricked again.... I used kies to restore to factory again, re-rooted it for the 4th time when I finally discovered an option in developer options called OEM unlock, Turning OEM unlock on turns off the FRP lock security feature.
My conclusion, If your going to root 5.1.1 make sure you remove all accounts from the device first, do not change google passwords for 72 hours prior to rooting, once rooted, YOU MUST TURN OEM Unlock ON in settings>developer options before adding any google accounts to the device.
Hi everyone!
I also got a Samsung S6 Edge + from a friend with custom binary blocked by FRP. I don't know what he was planning to do but I guess it was rooting.
He said he want me to backup any files before I try anything. Don't know how to proceed. But as suggestion, I want to ask if using "fastboot oem unlock" command would fix that.
EsperaKing said:
Hi everyone!
I also got a Samsung S6 Edge + from a friend with custom binary blocked by FRP. I don't know what he was planning to do but I guess it was rooting.
He said he want me to backup any files before I try anything. Don't know how to proceed. But as suggestion, I want to ask if using "fastboot oem unlock" command would fix that.
Click to expand...
Click to collapse
I'm pretty sure fastboot isn't for Samsung devices. Hard to back up any files u less you can get into TWRP or the phone. If you flash stock firmware is highly likely the files will be wiped
callumbr1 said:
I'm pretty sure fastboot isn't for Samsung devices. Hard to back up any files u less you can get into TWRP or the phone. If you flash stock firmware is highly likely the files will be wiped
Click to expand...
Click to collapse
There is no TWRP recovery on the phone. Yeah you're right about backing up files. I don't even know how to proceed and I can tell you I have huge experience on that stuff, rooting flashing custom recoveries and roms, etc... but in this case, I can't say if files can be backed up.
EsperaKing said:
There is no TWRP recovery on the phone. Yeah you're right about backing up files. I don't even know how to proceed and I can tell you I have huge experience on that stuff, rooting flashing custom recoveries and roms, etc... but in this case, I can't say if files can be backed up.
Click to expand...
Click to collapse
The only way is to 're flash the exact same firmware he is currently using now using the 5 files firmware package. But yo ensure csc_home is used so the data will not be wiped.
callumbr1 said:
The only way is to 're flash the exact same firmware he is currently using now using the 5 files firmware package. But yo ensure csc_home is used so the data will not be wiped.
Click to expand...
Click to collapse
Thank you for you reply.
Please can you tell me where I can find such software or how to do it clearly! I know how to use Odin but I don't know how to exclude user_data to be wiped. Thank you
Bonafid3 said:
5.1.1 has FRP lock auto turned on whenever you have a google account on the device... This is probably going to cause a lot of problems with all newer devices that get rooted. I even tried removing all google accounts, flashed recovery and flashed boot img back to stock after rooting and still FRP was bricking the device. I got supersu onto the device, all working fine for a 3rd time, as soon as I added a google account onto my device and restarted, it was FRP lock blocked and soft bricked again.... I used kies to restore to factory again, re-rooted it for the 4th time when I finally discovered an option in developer options called OEM unlock, Turning OEM unlock on turns off the FRP lock security feature.
My conclusion, If your going to root 5.1.1 make sure you remove all accounts from the device first, do not change google passwords for 72 hours prior to rooting, once rooted, YOU MUST TURN OEM Unlock ON in settings>developer options before adding any google accounts to the device.
Click to expand...
Click to collapse
Thank you thank you thank you!!! This is exactly what I was looking for I had just rooted my note 4 running 6.0.1 and had no idea what the oem option was as no rooting method talked about it at all so naturally as soon as i added my Google account phone restarted and locked up.
Kies was the answer I needed as frp lock was active in download mode and my factory reset in recovery failed everytime but running Kies firmware upgrade and entering my model and serial number it installed perfectly in download mode with frp lock still active saved me alot of hassle ?

Can't update the phone, can't do phone calls, nor texting, and several other issues

I'm pretty much ****ed with my phone.
First thing is, i can't update my phone, within the option menu, automatic update or manual one with dload folder doesnt work, The software upgrade mode never shows up, i have instead a very nice bootloop, i have to play with the VOL+ VOL- and POWER button untill i can finnaly boot.
Because of that, i'm stuck with Emui B130.
Wouldnt be that bad, if only my phone worked. But i can't take phone calls, nor send texts (or rarely can, almost only at my home, and if i'm lucky) When i travel i instantly doesnt have network anymore at all.
The phone detects my Sim Card, and i have some network, but i almost can't use it at all.
I tried to patch via fastboot the B100, B121 and B130 versions. All 3 have the update issue (S/W never shows up) and the network one PLUS the B121 version doesnt even allow me to insert my pin code.
So at this point i have a phone stucked in B130, which cant be updated, and i can't use it.
I tried to patch stock recovery, remove root, reinstall root, change the versions, i still can't access the S/W mode meaning i can't update the phone at all.
I just don't know what to do anymore, i've tried everything. I'm stucked.
Thanks in advance for eventual help.
Are you trying to update with root? You need to unroot first before you update. I haven't experimented with my phone yet but on my previous Huawei I always had to unroot before updating via dload/OTA
I tried both root and unroot, this doesn't change anything. :/
What happens when you press VOL+ VOL- and POWER on an honor 7?
Culdnt this be an Imei issue ?
Gosh This is so stupid, nothing works fine.
Now my phone just bootloops. I tried to flash with fastboot system.img and boot.img from B130, B100 and B121, and i can't make my phone to work, it just bootloops.
I thought i found the issue, i tried to flash the modem.img from my firmware, but couldnt manage to do it, and now i can't even make my phone to work. I'm so tired already of this phone. Everything was so simple with the Note 3.
Edit: And now i can't even try to flash some stock roms as i have a " Cannot load 'System.img' message.
I've done this more than 20 times and now for absolutely no reason, i have this.
I'm about to give up this phone. This is just madness. I just don't know what to do anymore.
I'd realy appreciate help of any kind.

[HELP] Error Mode Boot loop -No Access to fastboot/adb/recovery

Hi hello
So here’s a head scratcher I hope someone can help me with that won’t involve replacing my main board.
Got myself the p20 lite (ANE-LX1 C432) - Single Sim.
I unlocked the bootloader with Huawei just before they stopped handing out the codes. All was good and happy with the world.
Rooted with Magisk and Was busy messing around With Termux, Linux deploy, Mobile Terminal and some pretty basic stuff. I’ve been out of the android scene for a while so was getting reacquainted with the scene.
Anyway. I was messing around in the terminal in a root shell just fixing basic permissions after messing up my termux environment as root. Phone randomly rebooted (I must’ve messed with the wrong folder -no idea which) came back on and my IMEI and baseband were gone.
No worries, I thought. Happened tonnes of times with my previous Devices (looking at you Samsung) just a quick restore or flash and all will be happy again.
Yeah, not quite.
Note that up until this point I hadn’t touched the system partition (probably besides the mobile terminal mishap -no idea)
So over the last week or so I have tried everything. Restore from Twrp backup. Flashed stock through fastboot, through erecovery. Those flashed ok but didn’t fix it.
Putting numerous different update.app FULL & OTA updates in dload folder on SD and internal all failed. Only used my builds version of course and only ones firmware finder deemed compatible/available
Then I got desperate (read: stupid) Decided to take the unpacked firmware files and flash whichever ones twrp would let me. First tried just the modem files. Didn’t help. Then just went through the list and flashed all I could.
I think the kicker came in when I installed the Trustfirmware.img because once I did that I rebooted and now I was stuck in an endless boot loop. No way to get into recovery. Not with their ton combo nor adb/fastboot.
I still had access to fastboot at this point at least and started doing every single thing suggested all over the net just trying to get back to stock.
Tried the unbrick option on The Huawei Multi-Tool. Flashed ok. Phone still wouldn’t boot. Did it a few times with 3 approved versions. Nothing. Only access to fastboot otherwise I was in a boot loop with error mode error no 15 and the verification failure (Attached below)
Last thing I tried after reading online was to relock my boot loader and flash stock. So I locked it with Huawei Multi-Tool. Reboot......
Now I don’t even have access to fastboot. My PC’s (windows and Linux) don’t even acknowledge it and holding volume down in all the weird and wonderful ways and times does nothing. All I get is startup Huawei Logo, Error Mode as per pic Below and then reboot. That’s it.
I’m assuming it’s trying to do a factory reset after relocking the bootloader (if it even locked properly, can’t check) but it can’t get into recovery/erecovery. I dunno ?
That’s my essay of where I’m at. Warranty is already void so not an option and I don’t want to buy a new mainboard (may as well buy a new phone).
So here I am. Is this my life now or does anyone have any magic tricks to possibly suggest?
Pyrolectic13 said:
Hi hello
So here’s a head scratcher I hope someone can help me with that won’t involve replacing my main board.
Got myself the p20 lite (ANE-LX1 C432) - Single Sim.
I unlocked the bootloader with Huawei just before they stopped handing out the codes. All was good and happy with the world.
Rooted with Magisk and Was busy messing around With Termux, Linux deploy, Mobile Terminal and some pretty basic stuff. I’ve been out of the android scene for a while so was getting reacquainted with the scene.
Anyway. I was messing around in the terminal in a root shell just fixing basic permissions after messing up my termux environment as root. Phone randomly rebooted (I must’ve messed with the wrong folder -no idea which) came back on and my IMEI and baseband were gone.
No worries, I thought. Happened tonnes of times with my previous Devices (looking at you Samsung) just a quick restore or flash and all will be happy again.
Yeah, not quite.
Note that up until this point I hadn’t touched the system partition (probably besides the mobile terminal mishap -no idea)
So over the last week or so I have tried everything. Restore from Twrp backup. Flashed stock through fastboot, through erecovery. Those flashed ok but didn’t fix it.
Putting numerous different update.app FULL & OTA updates in dload folder on SD and internal all failed. Only used my builds version of course and only ones firmware finder deemed compatible/available
Then I got desperate (read: stupid) Decided to take the unpacked firmware files and flash whichever ones twrp would let me. First tried just the modem files. Didn’t help. Then just went through the list and flashed all I could.
I think the kicker came in when I installed the Trustfirmware.img because once I did that I rebooted and now I was stuck in an endless boot loop. No way to get into recovery. Not with their ton combo nor adb/fastboot.
I still had access to fastboot at this point at least and started doing every single thing suggested all over the net just trying to get back to stock.
Tried the unbrick option on The Huawei Multi-Tool. Flashed ok. Phone still wouldn’t boot. Did it a few times with 3 approved versions. Nothing. Only access to fastboot otherwise I was in a boot loop with error mode error no 15 and the verification failure (Attached below)
Last thing I tried after reading online was to relock my boot loader and flash stock. So I locked it with Huawei Multi-Tool. Reboot......
Now I don’t even have access to fastboot. My PC’s (windows and Linux) don’t even acknowledge it and holding volume down in all the weird and wonderful ways and times does nothing. All I get is startup Huawei Logo, Error Mode as per pic Below and then reboot. That’s it.
I’m assuming it’s trying to do a factory reset after relocking the bootloader (if it even locked properly, can’t check) but it can’t get into recovery/erecovery. I dunno ?
That’s my essay of where I’m at. Warranty is already void so not an option and I don’t want to buy a new mainboard (may as well buy a new phone).
So here I am. Is this my life now or does anyone have any magic tricks to possibly suggest?
Click to expand...
Click to collapse
Check the second post in this thread:
https://forum.xda-developers.com/honor-7x/help/help-stuck-error-mode-screen-t3735067
kilroystyx said:
Check the second post in this thread:
https://forum.xda-developers.com/honor-7x/help/help-stuck-error-mode-screen-t3735067
Click to expand...
Click to collapse
Thanks for this.
The battery discharged fully about two days ago.
I haven’t tried plugging it in and out as/if it turns on immediately (though even though it shows dead without charger it still comes on immediately).
I’m gonna get a weaker lower amp charger and see if that maybe helps. Fml ?
***UPDATE***
Been at it for hours. Battery is completely flat. But h second I plug it in the the Black Huawei logo comes up ten a few seconds later it’s on the same error screen for a little longer then boot loops like that constantly.
The error isn’t the same as the post in that link though. And I am FRP unlocked.
Eh.
Pyrolectic13 said:
Thanks for this.
The battery discharged fully about two days ago.
I haven’t tried plugging it in and out as/if it turns on immediately (though even though it shows dead without charger it still comes on immediately).
I’m gonna get a weaker lower amp charger and see if that maybe helps. Fml ?
***UPDATE***
Been at it for hours. Battery is completely flat. But h second I plug it in the the Black Huawei logo comes up ten a few seconds later it’s on the same error screen for a little longer then boot loops like that constantly.
The error isn’t the same as the post in that link though. And I am FRP unlocked.
Eh.
Click to expand...
Click to collapse
I guess your previous error was related to ramdisk...
Now what is your current situation?
-What error is showed in the Error mode?
-Can you reach FASTBOOT&RESCUE MODE menu?
-What is your current recovery?
kilroystyx said:
I guess your previous error was related to ramdisk...
Now what is your current situation?
-What error is showed in the Error mode?
-Can you reach FASTBOOT&RESCUE MODE menu?
-What is your current recovery?
Click to expand...
Click to collapse
As it stands I cannot enter fastboot or recovery mode. Update from SD also doesn’t do anything. Battery is completely discharged. And if I leave it on the charger it doesn’t charge, only boot loops.
So with all that the ONLY thing this phone does now is:
- Starts up Showing Huawei logo
- Error Mode Screen with Func No: 15 (bl31 image) & Error No: 1 (security verify failed)
- Reboots
Ths happens whether it’s plugged into the pc’s usb or the charger. Tried all combinations of buttons too.
It has stock recovery as I flashed that back when trying to revert back to stock.
I lost access to fastboot after I locked the bootlaoder again using the Huawei Multi Tool. It’s like it trying to do the factory wipe that it usually would after locking/unlocking the bootloader but is unable to due to the error mode screen.
Sent from my iPhone using Tapatalk
Pyrolectic13 said:
As it stands I cannot enter fastboot or recovery mode. Update from SD also doesn’t do anything. Battery is completely discharged. And if I leave it on the charger it doesn’t charge, only boot loops.
So with all that the ONLY thing this phone does now is:
- Starts up Showing Huawei logo
- Error Mode Screen with Func No: 15 (bl31 image) & Error No: 1 (security verify failed)
- Reboots
Ths happens whether it’s plugged into the pc’s usb or the charger. Tried all combinations of buttons too.
It has stock recovery as I flashed that back when trying to revert back to stock.
I lost access to fastboot after I locked the bootlaoder again using the Huawei Multi Tool. It’s like it trying to do the factory wipe that it usually would after locking/unlocking the bootloader but is unable to due to the error mode screen.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
I see, it is really bad
My last hope is to be able to do a forced Firmware upgrade. Press power button and VOL + and VOL- simultaneously. Do you see the same as the attached image?
kilroystyx said:
I see, it is really bad
My last hope is to be able to do a forced Firmware upgrade. Press power button and VOL + and VOL- simultaneously. Do you see the same as the attached image?
Click to expand...
Click to collapse
Ah man, I wish it would even do that. It makes no attempt to even pretend to see the sd card update. If I hold all the buttons in it still only comes up with the error mode and reboots.
I popped it open and connected a charger up battery to see if that would help but it doesn’t.
Do you maybe know the pin layout on the inside or know where I could get schematics? Been looking everywhere.
I’m almost done building my own Jtag box and am hoping to bring it back to life by writing straight to the damn thing.
Sent from my iPhone using Tapatalk
Pyrolectic13 said:
Ah man, I wish it would even do that. It makes no attempt to even pretend to see the sd card update. If I hold all the buttons in it still only comes up with the error mode and reboots.
I popped it open and connected a charger up battery to see if that would help but it doesn’t.
Do you maybe know the pin layout on the inside or know where I could get schematics? Been looking everywhere.
I’m almost done building my own Jtag box and am hoping to bring it back to life by writing straight to the damn thing.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
That is sad!!!
With JTAG and schematics stuff I cannot help you.
What I found recently and it was new for me (I didn't tested yet) is a possibility to install firmware via "dload" folder, but to start installation the stock recovery have to be full functional.
If I found something interesting for you I'll post here.
kilroystyx said:
That is sad!!!
With JTAG and schematics stuff I cannot help you.
What I found recently and it was new for me (I didn't tested yet) is a possibility to install firmware via "dload" folder, but to start installation the stock recovery have to be full functional.
If I found something interesting for you I'll post here.
Click to expand...
Click to collapse
To my knowledge the recovery is installed. Well erecovery. It was working up until I locked the bootloader again and it went into a boot loop instead of doing the factory reset.
Is there any other way to force sd update other than with the dload folder?
Thanks for tying to help, I appreciate it.
Pyrolectic13 said:
To my knowledge the recovery is installed. Well erecovery. It was working up until I locked the bootloader again and it went into a boot loop instead of doing the factory reset.
Is there any other way to force sd update other than with the dload folder?
Thanks for tying to help, I appreciate it.
Click to expand...
Click to collapse
You can check the official documentation about that.
Please let us know how you solved this problem.
kumarsid7 said:
Please let us know how you solved this problem.
Click to expand...
Click to collapse
Still unsolved as of yet.
I’ve finished building my own version of the Riff/Octoplus box as well as a makeshift Jtag. I’m still trying to find and piece together some firmware files and other board software I think I need.
Also, if anyone has any idea where the test point is on this board I’d really appreciate you pointing it out. I cannot find the schematics or any solid documentation anywhere.
I will attach the pics I have of both sides of the board as soon as I get home.
Sent from my iPhone using Tapatalk
in first picture youle see many circles golden 2 smallest is testpoint good luck
Pyrolectic13 said:
Still unsolved as of yet.
I’ve finished building my own version of the Riff/Octoplus box as well as a makeshift Jtag. I’m still trying to find and piece together some firmware files and other board software I think I need.
Also, if anyone has any idea where the test point is on this board I’d really appreciate you pointing it out. I cannot find the schematics or any solid documentation anywhere.
I will attach the pics I have of both sides of the board as soon as I get home.
View attachment 4579956
View attachment 4579957
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
in first picture youle see many circles golden 2 smallest is testpoint good luck
well, try to restore your device using dload method. It needs you to copy the UPDATE.APP in dload folder of an external sd card(formated in NTFS format) and then just press both vol up+down along with power button for a few seconds. It will auto launch huawei e-recovery and will try to flash the UPDATE.APP you stored in ext sd card. This should definitely work.
Dload method doesn't need you to unlock your device or bootloader.
Maybe?
I know it’s a long shot but I still have this phone. If anyone maybe knows if there’s been a way to fix this as of yet please let me know. ?
Lol. Still got this damn thing. Been searching around and seen a few people reporting similar errors. Never find out if they ever solve it though.
So. Anyone maybe have any knowledge to share? Anything at all.
I don't know if you still have your device, but I had the exact same issue with a P10 (VTR-L09)
I was able to fix fastboot using https://github.com/mashed-potatoes/PotatoNV
That tool was designed to unlock the bootloader, but I noticed that It actually flashes a slightly modified version of fastboot.
PotatoNV can also unlock P20 lite bootloader, so you should give it a shot.
Good luck!
If it works, you should be able to flash stock recovery image and then restore the system using the dload folder.
you can Repair it with Software Testpoint and Full Bootloader Unlock ,and then flash a Board Software via Software Testpoint, that helps 100%!!!
use this Firmware Download ANE-LX1
use the Software with logins and you have all what you need.
you must start the Software Testpoint so!!
VIDEO : how to start Software Testpoint P20 Lite
than in Software Testpoint you flash the included Board Software with DC-Phoenix and after that use the included dload update via sdcard and eRecovery mode and your Phone is running!!!
I would unlock the bootloader via Software Testpoint with DC-Phoenix, then the FBLock is unlocked and you can flash as you wish!!!! And the great thing about it is that you don't need an UnlockKey either, you can then read this with HCU client software, the only thing that's stupid is that you need a time-based license for the two programs, which you have to buy.
HCU client download
https://hcu-client.com
DC Phoenix download
https://forum.dc-unlocker.com/forum/modems-and-phones/huawei/155916-dc-phoenix
Since I accidentally bought a 3-day license twice and my P20 Lite is now completely rooted on Lineage 19.1, I can give away 2 access data, which are still valid for 2 days.
you can edit your smartphone with it.
username : bl26457
password : kKncnkMj
username : bl26390
password : JDAZqnkN
Then I wish you a lot of fun with it, hope it helps you if someone else is active in this thread.

Categories

Resources