I've recently repaired my Huawei P8 Lite after it's screen was mutilated and such and I decided to try flash a different ROM onto the device, I wiped my entire device and restarted it instead of flashing the ROM I needed to and I got led into a bootloop which presented me with the Huawei logo until the device just died from battery loss.
I was able to get myself into TWRP before the bootloop occured everytime the phone auto-restarted and I tried flashing the ROM which was Resurrection Remix V.6 and in the end near its installation I did notice it printed out two lines saying "Unknown command" and then continued to say it finished the installation succesfully but when I restarted my phone, there was nothing but the bootloop.
I ended up getting frustrated at left my phone on my desk untouched and now I'm presented with a Rescue Mode panel when I try to boot into TWRP to try and flash a stock ROM. The panel presents me with a message asking me to
Please update system again
Func NO : 11 (recovery image)
ERROR NO : 2 (load failed!)
I'm able to hold my power button and volume button up to boot into Huawei eRecovery but it's as useless as this phone currently. Please note I've tried methods involving connecting my phone to my PC and troubleshooting it from here but my PC does not recognize my phone at all, it never did whilst it was running the stock firmware either. Any help is gladly appreciated.
My phone model for anyone wondering : Huawei P8 Lite ALE-L02
Update :
I've managed to flash TWRP onto my device again after enough times battling the rescue mode, I no longer get the function errors however I have discovered a problem that runs deeper than just a few missing .img's. I've re-flashed Resurrection Remix again with gapps and no errors were presented within the installation processes, I rebooted my system and got put straight back into a boot loop. I decided to go back into recovery and to my surprise there's nothing inside my internal directory besides an empty TWRP folder.
I'm assuming that my device is not properly installing/saving the files where they need to be.
Related
Edit: All happy now, a change of pc solved the problem of not detecting the device!
Hi all! I have another challenge for you!
Right, I've got myself in a tizz with my Defy +. While updating between CM10.1 versions I found myself in a situation where I couldn't get past the boot animation. So I loaded the TWRP restore I had made prior to updating...
Except it wouldn't, instead it came up with 'Failed' each time I tried any of the TWRP backups I had created. So the next step was to wipe partitions and start flashing various ROMs until I found one what worked. Except they didn't work either. Eventually I thought the best idea would be to just turn the phone off and see where I was with booting.
So power on, boot logo, blue light, red light then... nothing. Just the boot logo static. Went into the custom bootloader to go into recovery again, nothing. Pressing Custom recovery simply loops back to the top bootloader screen.
Ok next step, flash .sbf and start from scratch. So into the Moto bootloader it is to plug in and flash except... it's no longer detected by my computer.
"Ok" I think, "We'll just flash files from the SD card after I use an external SD card reader.
Except now when I enter Moto recovery to flash the TWRP recovery I get:
-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verifiaion failed
Installation aborted
So to recap:
1) Tried to flash and update, failed
2) Tried to recover, recoveries wouldn't write (I think this is becaue I'd changed to EXT4 on /data and /cache and had forgotten to go back to EXT3 before trying to recover)
3) Tried to boot, epicly failed
4) Tried to flash .sbf, Defy+ won't appear in RSDLite 5.7 with latest driver
5) Tried to flash from SD card, sig verification failed
6) Googletastic for the last four days
Notes:
a) I CAN charge the Defy+ using the wall charger but I get '?' for the battery level indicator but...
b) In Cmod bootloader 2.1 (Which I can use a little) it shows the correct battery level
c) I /was/ getting some errors with not being able to mount /cache from the moto recovery but I've since used the cmod bootmenu 2.1 to set it back to ext3 and it's all happy now, those errors aren't appearing
d) Plugging in my Defy red lens I get W8 x64 detecting the correct portal drivers and such but when I go to moto bootloader this device also doesn't appear in RSDLite
e) Both devices prompt windows to install a Motorola Flash Interface driver in Device Manager when plugged in in moto bootloader mode and neither device appears in RSDLite despite the fact the program is running in Admin mode
f) Looking at the logs in bootloader, it appears that I might not have formatted anything from ext4 to 3, everything I select in the cmod bootmenu returns .E:Error in /system/... , (Result: Invalid arguement) , Done..
So at the moment I think I need to acheive one of the following:
1) Find a file that allows me to write any useful data to /system like a recovery or some of those bootmenu files that passes the signature verification
2) Find a way to troubleshoot RSDLite so I can actually flash .sbf and get out of this hellhole
Many regards!
Alexis
If your custom recovery is not working, then you cannot do anything other than flash an sbf(nothing except data and cache wipe can be done via stock recovery): this is due to the locked boot loader(recoveries cannot be simply flashed from the stock recovery as you're trying to do)
Sent from my MB526 using Tapatalk 2
Success (ish)!
Yes I swapped to a different machine and then upgraded the version of RSD Lite installed on it from 4.7 to 6.1.5
[URL="http://forum.gsmhosting.com/vbb/f166/rsdlite-6-0-mtk-patch20-rsd-lite-6-0-a-1545012/index2.html#post8988239"]http://forum.gsmhosting.com/vbb/f166/rsdlite-6-0-mtk-patch20-rsd-lite-6-0-a-1545012/index2.html#post8988239
And flashed the 'lower' of the two .sbf's from the links on this forum for the British variant. After a DEA1 error (Phone is dead, code corrupt and all the bad things) I managed to flash the file.
As of yet I've not managed to get out of the bootloop but I've not carried out the requisite steps as mentioned in the "So you think you've bricked your Defy/Defy+" thread.
Lessons learned:
1) Motorola drivers and RSD Lite are pennickety, you will probably need to mix them up in order to get them to behave properly
2) If all else fails, use a different computer
3) You will probably need to flash over and over, while making every effort to not muck them up. Be aware the efuse system only has limited uses before it's useless though...
My saga continues, from no USB support hopefully to a fully working device again
In the end switching PC then doing the factory reset from moto recovery let the phone boot, all standard but the dodgy USB stuff at the first post is what sent me away from the right track.
Hi,
I recently acquired a Huawei Ascend G7...smashed screen and what not, replaced the screen on the phone and it starts bootlooping.
Booted into recovery, (already had TWRP), Tried flashing a zip file and i consistently get "Error executing updater binary". I have tried a few things that I have found on here but nothing seems to be working and its just stuck in boot loop. HiSuite doesn't recognize the device in fastboot mode. Before I go any further I was wondering any advice anyone could offer me on how to resolve this issue. Thanks
tdstt said:
Hi,
I recently acquired a Huawei Ascend G7...smashed screen and what not, replaced the screen on the phone and it starts bootlooping.
Booted into recovery, (already had TWRP), Tried flashing a zip file and i consistently get "Error executing updater binary". I have tried a few things that I have found on here but nothing seems to be working and its just stuck in boot loop. HiSuite doesn't recognize the device in fastboot mode. Before I go any further I was wondering any advice anyone could offer me on how to resolve this issue. Thanks
Click to expand...
Click to collapse
The "Error executing updater binary" may be due to your device name not listed in the zip file. In the updater-script file the first line is usually an assert, you can try to remove that line, re-zip the whole thing and try to flash again.
I've been trying to update my phone to emui 5.0, every time it just says update failed. I also tried to flash custom roms through twrp, which always make my build number to something about test-keys. Maybe I'm just to dum. I wiped the system and tried again, but when booted to fastboot it says locked bootloader(it isn't what I want) so I unlocked the bootloader. Now it somehow only boots into the error mode: NO11(recovery image) and NO2(load failed).
I tried button combinations, it just keeps booting to error mode(I also read through other threads, but the solutions like waiting till the phone dies, than press volume - and connect to pc didn't work).
PLEAEAEAS Help!!!
Frist off, I have a Huawei P9 Lite, Model: VNS-L31C432B394 I tried to flash SuperSU through twrp and after rebooting it was stuck in the Huawei loading screen, so I factory reset my phone and it still wouldn't start after 20 minutes of being stuck in the Huawei loading screen. I then accidently went to the advanced tab in TWRP and checked everything then wiped it instead of Formating Data and it then said that there's no OS installed and now it won't even get out of the "Your phone is not trusted..." screen. I tried to flash the update.zip from the site getdroidtips (Size: 1.26gb) for my Model but it just says "Software install failed the update package does not exist". I don't know what to do anymore, I really need help.
I also tried different flash stock roms from different sites including VNS-L31C432B411, how I did it was flash the update.zip, then update_full_VNS... and then update_data_full_public... and restarting it and then going into the eRecovery, it just said "Software Installa Failed!" once again, I also tried putting the update.app in the dload folder and restarting, going into eRecovery but it kept saying "Software install failed!"
cxybah said:
Frist off, I have a Huawei P9 Lite, Model: VNS-L31C432B394 I tried to flash SuperSU through twrp and after rebooting it was stuck in the Huawei loading screen, so I factory reset my phone and it still wouldn't start after 20 minutes of being stuck in the Huawei loading screen. I then accidently went to the advanced tab in TWRP and checked everything then wiped it instead of Formating Data and it then said that there's no OS installed and now it won't even get out of the "Your phone is not trusted..." screen. I tried to flash the update.zip from the site getdroidtips (Size: 1.26gb) for my Model but it just says "Software install failed the update package does not exist". I don't know what to do anymore, I really need help.
I also tried different flash stock roms from different sites including VNS-L31C432B411, how I did it was flash the update.zip, then update_full_VNS... and then update_data_full_public... and restarting it and then going into the eRecovery, it just said "Software Installa Failed!" once again, I also tried putting the update.app in the dload folder and restarting, going into eRecovery but it kept saying "Software install failed!"
Click to expand...
Click to collapse
Hey,
I see you f**ked up after the other....
Maybe flashing unSU with TWRP and wiping cache+dalvick cache would have solve the problem.
First wiped everything, then tried to flash a non "FULL OTA" firmware ( 1,26gb instead of +/- 1,9gb normally )
and finally tried to flash a wrong firmware ( B411 )...
Now if i'm not wrong you have a dual sim device ( correct me if needed ), so try to reflash the firmware
you got before.
Dowload VNS-L31C432B394 - FULL OTA MF - with Firmware Finder or other sources and use HWOTA like explained
in this thread.
Another method could be doing a rollback trying to revert to your marshmallow initial firmware.
Hope you will get rid of this..
All the best
Hi! I used this phone back in 2014-2015 and then in 2016 I bought an iPhone 7, so I left the phone in his box. 2 years ago I needed to use that phone because I left some important photos that I didn't backup and a red exclamation mark appeared on the up-left part of the screen when I booted it. Couldn't access recovery but only download mode, the phone is a SM-G350 (I live in Italy and it isn't an ITV but a TIM region), I didn't root it or something it was stock firmware. Last year I decided to flash the TIM firmware but a KIES Update failed appeared (ODIN said OK and it went all good), I could access recovery and an EFS error appeared. This year I tried flashing TWRP 3 to install LineageOS 13 (maybe something could change) and transferring the file and flashing worked but the phone won't boot (stuck on LineageOS boot animation). I tried formatting Data etc but the EFS error was still there. I tried flashing ITV and TIM roms from Odin with no success, only an infinite boot. Yesterday I tried flashing another recovery but even with the Odin "OK" text TWRP was still there, so I started to doubt if the internal memory went corrupted when I left it another 2 months. I found a make2fs and mount method for the EFS, it mounts, I can install the LineageOS 13 zip but the progress bar stays at about 70%. When I delete files or transfer new things into memory or trying formatting from TWRP the internal memory clears temporarily and when I reboot into recovery the files go back like I didn't delete them. I had another SM-G350 but it died totally (it booted with the same exclamation mark thing) and back in 2015 I was using it in my hand and rebooted itself in recovery mode showing a file system unknown error.