Database Info

IT WAS THE FINAL STEP... and it did not work. (Stuck on boot loader warning screen)

FINAL EDIT: FIXED!!! Sparsechunk files 1,2and 3 have to match the exact name with the firmware folder sparsechunk files.
I did not notice that my firmware sparsechunk files ended in .0 .1 .2 and not 1 2 3 like the tutorial had listed, so I was fastbooting the wrong sparsechunk command. That was the final fix that finally worked for me.
Original post:
SHORT VERSION:
My god this has been one crazy root journey.
I have done absolutely EVERYTHING I could pull up on google to fix my phone, and what seemed to be the final piece to the puzzle, still has not fixed anything.
My phone is bricked, and i would really appreciate help at this point.
The current problem:
When I turn on my phone, it vibrates, and displays the WARNING BOOT LOADER UNLOCKED screen, and stays there forever.
I can access my boot loader, and recovery, but I dont know what to do at this point.
I tried a quick flash stock recovery kit kat with moto tool AIO, and it didnt help.
Any ideas?
LONG VERSION (backround info may help to understand the current issue)
Now, if you want to know what began all of this, continue reading, otherwise the above is my current issue.
After successfully unlocking and rooting my phone
I downloaded SWITCHME, an app that lets you create multible users on the phone. the instructions say that you can use a sub account to test and mess around with anything because you can simply go back to the admin account that has everything untouched.
That was a lie.
1.I deleted .setup, along with a few other things THAT WHERE NOT FLAGGED AS IMPORTANT, assuming the phone would still work. and my phone went bonkers, displaying this infinite message: UNFORTUNATELY, SETUP HAS STOPPED. It was impossible to use the phone, and I could only access bootloader.
2.After endless googling, driver downloading, xda mod installing, I managed to set up my boot loader to do the guide restore stock firmware:http://forum.xda-developers.com/showthread.php?t=2542219
Sadly, I flashed the wrong model number package, I was flashing x35, when I later discovered that my phone is x45.
Flashing the x35 firmware bricked my phone further, to where it would "fail to boot up" and would only display bootloader over and over after attempting to turn the phone on.
3. Simple, I realized I flashed the wrong thing, so I downloaded the x45 firmware from the firmware teem on this website, flashed all of the commands, and bam, the phone starts up with the boot loader warning, and DOES NOT get stuck in the previous boot loader issue I had.
But now the phone wont get past that warning screen so... now im pissed.
Please, if anyone can help me I would greatly appreciate it, Im so close to getting my phone back...
EDIT 2: Looks like the phone wont stay shut down, I realized that if I dont open up boot loader, it will turn itself on and display the warning message.
EDIT:
The stuffs I have, ready to try anything:
CWM touch mod
Moto Tool AIO
Minimal ADB and Fast boot
RETUS x1045 factory firmware
All directories, folders, cmd commands are set up and working properly between all of the programs.
The phone appears to be responding to all cmd commands properly.
I also have the windows one touch super boot root method. (he superboot-windows.bat )
Im afraid to try anything major after freshly flashing the x45 firmware that seemed to bring me one step closer without the help of someone else.

I restored stock to my phone using this link yesturday http://www.ibtimes.co.uk/how-restore-motorola-moto-g-stock-firmware-1447290
it may work for you

I have almost the same problem as if the fastboot not install anything despite not display errors

great that you got it done.
maybe my few cents about my "bricking" story. (xt1032 moto g)
yesterday i wanted to change the rom from cm11 nightly to another custom rom like ehndroix/carbonrom...
first i thought that will be done in a few mins, after having already flashed a custom rom.
then the story began, getting adb work, but, 2weeks ago everything was setup and went fine. dunno why my laptop lost the "drivers".
thats the link which solved that problem: tinyurl . com / kgffjh4 [sorry cant post links outside of xda yet, spam protection]
so after a few hours of getting that fixed i, i began flashing.
suddently i got stuck in bootscreen (ehndroix logo for example)...
then i wanted to go back with my previous backup made internaly of clockworkmod. though i couldnt restore my backup because there was an error message while restoring /data of my backup
also when restoring to factory/wipe in cwm there was that error message about clouldnt "touch" /data, i dont remember the message exactly.
after thinking i bricked everything, i though lets wipe my internal sdcard, maybe that causes the /data error.
then i restarted the device and went for a shower... after 15min i came back and my device was "started".
now i dont know that exactly helped, maybe wiping all data on my phone, or just letting my device boot for a "long" time...
so, thats my yesterdays brick story.

do a factory reset if the bootloader has that option.. otherwise install or run/boot a custom revovery, then either
try the factory reset option there and reboot or..
wipe everything and install a rom

Ok try this, I'm was a victim too:
Relock and unlock bootloader
Download and flash latest Philz
From there format everything...EVERY PARTITION...switch F2FS
After switching wipe every partition again
Select and execute the other 3 wiping option ie., Clean to install new ROM and the other 2 (I can't remember now)
Do this all over again via TWRP too
Now, this is important, don't use the mfastboot for restoring stock...use the one provided by Google for its Android SDK
Flash the stock images
Flash the Moto Razr boot animation and not the one for Moto G to remove the warning sign
I'm 99.99% sure your phone will boot properly
After the phone boots, reflash the Moto G bootanimation
Good Luck!

ngr.hd said:
Ok try this, I'm was a victim too:
Relock and unlock bootloader
Download and flash latest Philz
From there format everything...EVERY PARTITION...switch F2FS
After switching wipe every partition again
Select and execute the other 3 wiping option ie., Clean to install new ROM and the other 2 (I can't remember now)
Do this all over again via TWRP too
Now, this is important, don't use the mfastboot for restoring stock...use the one provided by Google for its Android SDK
Flash the stock images
Flash the Moto Razr boot animation and not the one for Moto G to remove the warning sign
I'm 99.99% sure your phone will boot properly
After the phone boots, reflash the Moto G bootanimation
Good Luck!
Click to expand...
Click to collapse
I try to flash any recovery but after entering I get an android and says no commands, and installation does not throw errors

angelgzg said:
I try to flash any recovery but after entering I get an android and says no commands, and installation does not throw errors
Click to expand...
Click to collapse
You're still in stock recovery.
Use fastboot flash recovery xyz.zip to flash philz recovery
Use this when you're in bootloader mode.

ngr.hd said:
You're still in stock recovery.
Use fastboot flash recovery xyz.zip to flash philz recovery
Use this when you're in bootloader mode.
Click to expand...
Click to collapse
I flash the recovery but rebooted into recovery, the android keeps popping up (no commands)

FINAL EDIT: FIXED!!! Sparsechunk files 1,2and 3 have to match the exact name with the firmware folder sparsechunk files.
I did not notice that my firmware sparsechunk files ended in .0 .1 .2 and not 1 2 3 like the tutorial had listed, so I was fastbooting the wrong sparsechunk command. That was the final fix that finally worked for me.
Sorry I'm traveling a d couldnt update thread fast enough.

PROBLEMS in installing TWRP and root (20a)

spent the last 3 weeks ( NO LIE ) trying every method under the sun to get my device rooted
easy recowvery
Hard Recowvery
manual ADB and flashing img
tot updates
kdz downgrades
basically everything
im not sure what else to do if its even possible at this point
Device details
tmobile locked LG G5 (h830)
OEM unlocked
its on 20a firmware ( coming from 20i )
ive rooted and installed twrp on may phones so i have a vast knowledge of these things
a few observations are
phone seems like its rewriting stock recovery on each reboot
fastboot won't accept any commands, i get "writing 'recovery'...FAILED (remote: unknown command)"
both hard recowvery and easy recowvery work up to the part of twrp install then it reboots to nothing
FINAL NOTE
im wondering if t-mobile is blocking the fastboot commands since im on temp unlock via device unlock app
if thats not a thing idk whats wrong im hoping one of you great minds can help this poor soul

Anyone?

Did you check oem unlock in developer options

rflores said:
Did you check oem unlock in developer options
Click to expand...
Click to collapse
thanks for replying ,
yes i did
its greyed out now but its been off
the fastboot commands says its unlocked as well

Did you make sure to download the recovery image and put in the root directory of the device storage and rename it recovery? If not then non of the recowvery methods will work. Also twrp needs to be the newest image. When using easy recowvery you should hit option 5 and enter then option 7 and enter and then option 0 and enter then option 2 and enter. Select y for yes when prompted and let the program do its thing. You should be prompted to boot into recovery at the end and it will go into tarp recovery. Hit cancel when it asks for password. Then go to wipe and format. After formatted, you need to install no-opt enc or root and then you're done. If you want to update all you have to do is get latest firmware from this forum. Also' if you update you need to also re flash no opt enc or root again and I also delete recovery from boot.p file in recovery. Should be good to go!

speters04 said:
Did you make sure to download the recovery image and put in the root directory of the device storage and rename it recovery? If not then non of the recowvery methods will work. Also twrp needs to be the newest image. When using easy recowvery you should hit option 5 and enter then option 7 and enter and then option 0 and enter then option 2 and enter. Select y for yes when prompted and let the program do its thing. You should be prompted to boot into recovery at the end and it will go into tarp recovery. Hit cancel when it asks for password. Then go to wipe and format. After formatted, you need to install no-opt enc or root and then you're done. If you want to update all you have to do is get latest firmware from this forum. Also' if you update you need to also re flash no opt enc or root again and I also delete recovery from boot.p file in recovery. Should be good to go!
Click to expand...
Click to collapse
thanks for this reply
i will try this as soon as i get home
thanks in advance

speters04 said:
Did you make sure to download the recovery image and put in the root directory of the device storage and rename it recovery? If not then non of the recowvery methods will work. Also twrp needs to be the newest image. When using easy recowvery you should hit option 5 and enter then option 7 and enter and then option 0 and enter then option 2 and enter. Select y for yes when prompted and let the program do its thing. You should be prompted to boot into recovery at the end and it will go into tarp recovery. Hit cancel when it asks for password. Then go to wipe and format. After formatted, you need to install no-opt enc or root and then you're done. If you want to update all you have to do is get latest firmware from this forum. Also' if you update you need to also re flash no opt enc or root again and I also delete recovery from boot.p file in recovery. Should be good to go!
Click to expand...
Click to collapse
providing an update
Ive just tried everything listed in you post specifically and failed , so i tried like 2 more time ,
it reboots into stock recovery so still no TWRP ,
boot loader is unlocked , cause i just checked again , and its still not accepting any commands

Adb flash commands do not work for the lg g5... You have to root with either easy recowvery or hard recowvery. You have to be on 20a firmware.

speters04 said:
Adb flash commands do not work for the lg g5... You have to root with either easy recowvery or hard recowvery. You have to be on 20a firmware.
Click to expand...
Click to collapse
thanks for reply;
none of those work for me either, I've been trying all this time
it says its successful in deploying commands, but when it restarts I see the LG logo two times, then it boots back up
( i assume its rewriting recovery there )

Can you explain the exact process you are trying? It is kinda hard to diagnose the issue without knowing the full process you are trying. I have rooted several lg g5 phones with the autorecowvery tool.

I had the same issue after returning from 20k to 20a. I didn't have this problem doing the same from 20f. T-Mobile might've introduced some security kink at 20i that sticks across updates. I was only able to flash twrp after flashing 20a with UPPERCUT to enter LGUP, booting into 20a, allowing debug in developer options, then running easyrecowvery with verification disabled (press 5 for advanced options, then 7 I think, then 0 to return to main menu, then 1 or 2). With verification enabled, easyrecowvery will just take you to the non-existent Android recovery screen and leave you there. I think that's where you're stuck??

speters04 said:
Can you explain the exact process you are trying? It is kinda hard to diagnose the issue without knowing the full process you are trying. I have rooted several lg g5 phones with the autorecowvery tool.
Click to expand...
Click to collapse
well lets use Autorecowvery for example
ive exhausted all options there and Ive gotten the success messages , does its fancy restarts and success messages all around , but when it restarts to install the "no-verity-opt-encrypt" it reboots and comes right back to android . ( note it reboots 2 times at this point , so i know its rewriting stock recovery )
see below
https://ibb.co/eq5ctR

It seems like you have a recovery flash. Have you tried adv reboot recovery? If not then you need to try that. You can also use hardware combination to get into recovery. You have to select yes both times and it will reboot to recovery. If it doesn't then start over with the auto recowvery. Also, it is very important that you download twrp and copy it to your internal storage on the root. Also, once it is there you have to name it to recovery. Don't use the .img when renaming it because you end up with recovery.img.img... Sometimes it takes a few tries on the recowvery method... Hope this helps!

speters04 said:
It seems like you have a recovery flash. Have you tried adv reboot recovery? If not then you need to try that. You can also use hardware combination to get into recovery. You have to select yes both times and it will reboot to recovery. If it doesn't then start over with the auto recowvery. Also, it is very important that you download twrp and copy it to your internal storage on the root. Also, once it is there you have to name it to recovery. Don't use the .img when renaming it because you end up with recovery.img.img... Sometimes it takes a few tries on the recowvery method... Hope this helps!
Click to expand...
Click to collapse
well ive used
- "adb reboot recovery"
- hardware keys ( whenever i do this it wipes the phone ) , so i wont be trying that much cause i have stuff on it now , phones not encrypted tho
ive tried all 4 versions of twrp and renamed them all , countless times ive tried everything ive searched and read

When you first get into TWRP for the very first time, I believe it is a must to "FORMAT DATA" before you flash supersu and 'no-verify' zips

dtgo said:
well ive used
- "adb reboot recovery"
- hardware keys ( whenever i do this it wipes the phone ) , so i wont be trying that much cause i have stuff on it now , phones not encrypted tho
ive tried all 4 versions of twrp and renamed them all , countless times ive tried everything ive searched and read
Click to expand...
Click to collapse
I know this might sound silly, but have you extracted the twrp file and then renamed it to recovery? Have you tried downloading on your phone and then extracting it on your phone and then renaming it? After I looked at the image you shared it seems like the flash seems to have an error and the only thing that makes any sense to me is a bad download of twrp or an unextracted version. I've ran into that error before and it drove me nuts until I figured it out...

poog said:
When you first get into TWRP for the very first time, I believe it is a must to "FORMAT DATA" before you flash supersu and 'no-verify' zips
Click to expand...
Click to collapse
well ive been working to get to this screen it NEVER happens , i already know im set when im there
the phone isnt encrypted so i know i wont have to format data , since , format data removes encryption

speters04 said:
I know this might sound silly, but have you extracted the twrp file and then renamed it to recovery? Have you tried downloading on your phone and then extracting it on your phone and then renaming it? After I looked at the image you shared it seems like the flash seems to have an error and the only thing that makes any sense to me is a bad download of twrp or an unextracted version. I've ran into that error before and it drove me nuts until I figured it out...
Click to expand...
Click to collapse
ive tried both your suggestions plus more
copied to the phone and renamed
downloaded on the phone then renamed
dowloaded on pc and renamed then copied to phone
used adb to push and rename to phone

still having challenges with this
do you think its a dead case guys

OP isn't the only one with this hair-pulling problem...I too downgraded a new H830 from 20M (? I can't remember which one exactly since I've LG-Uppercutted 20A and troubleshooted this constant problem so many times now)---I get the exact same error as OP, also with the highly suspicious 'greyed-out OEM Unlock' (in the Developer Options of the Settings).

Hanging during Boot animation

Hello, I would like some help since I got this device just yesterday.
I got it with the EMUI 4 Android 6.0 stock installed on it. Since there was no update for it I unlocked the bootloader installed twrp rooted and manually flashed EMUI 5 7.0. Everything worked fine.
I created a backup through TWRP and restored it succefully multiple times.
Then I installed the Meticulus TWRP (since I was told it is a prerequisite for the AOSP). I Flashed the AOSP but it stuck during the boot animation (30 minutes afterwards I powered it off).
I reflashed my old TWRP and tried restoring my backup. IT fails with the explanation "Cannot wipe /vendor" while at the top it says "Cannot mount /vendor (invalid argument)" "Cannot mount /product (invalud argument)".
Anyone has a clue how to fix this? Fastboot adb all works so there should be a way to boot into an OS properly?

Since AOSP was not booting i guess you forgot formatting /data partition to ext4... And did u Used Stock vendor and not openkirin ones ?
Gesendet von meinem Honor 6X mit Tapatalk

As said I have replaced the custom TWRP with the default one so I think this should not apply anymore?
The "cannot mount vendor/product" messages came from the default TWRP after I reflashed it again.
At the top it says "cannot mount /vendor" either so I guess that is the actual problem?
It would be nice to get teh AOSP up but I really want to be able to boot into something first honestly.
And did u Used Stock vendor and not openkirin ones
Click to expand...
Click to collapse
Can you please explain? When I flashed your ROM i was on your TWRP. Does this even matter anymore?
At best I would be able to restore my backup.

To me it appears to be caused by the vendor partition.
Is there any way I can manually create that through TWRP?

algg said:
To me it appears to be caused by the vendor partition.
Is there any way I can manually create that through TWRP?
Click to expand...
Click to collapse
Yes you can but not creating it through twrp, but flashing it by fastboot mode: this is because
image (.img) files needs to be flashed by fastboot mode to avoid any kind of problem.
So, you should look for the last version of stock firmware on which you was before going custom, like BLN-L21CXXXB368 for example; tell me your build number and I'll find the package for you. Then, extract from the UPDATE.APP (a very big file that contains every partition in your phone like recovery, vendor, data, ecc. - you'll find this file inside the zip archive that contains the downloaded update) the vendor.img using Huawei Update Extractor, and then flash it through fastboot mode using the command "fastboot flash vendor vendor.img".
Otherwise, you could rely on dload method to reflash a full update package, and this should really fix everything since that it'll be like a new and clean installation of the OS. Then, unlocking the bootloader again and reflash TWRP to finally restore your previous backup made when it was working would be the final step.
Feel free to ask for further help

Thanks for the reply first really appreciate it.
I got the device on EMUI 4 Marshmallow rooted it and unlocked the bootloader then installed the BLN-L21C185B140 which worked smoothly.
I used that update.zip and extracted into dload root folder and started the huawei recovery installer but it said "package not found".
I tried flashing something to vendor before with fastboot but it said command not allowed.
Maybe I am doing something wrong?

algg said:
Thanks for the reply first really appreciate it.
I got the device on EMUI 4 Marshmallow rooted it and unlocked the bootloader then installed the BLN-L21C185B140 which worked smoothly.
I used that update.zip and extracted into dload root folder and started the huawei recovery installer but it said "package not found".
I tried flashing something to vendor before with fastboot but it said command not allowed.
Maybe I am doing something wrong?
Click to expand...
Click to collapse
Latest build on Nougat after the update was BLN-L22C185B140 so? If yes, the package that you need to download is that one. Unluckily i can't help about dload method, i never had fortune using dload because package verification always failed at 5%, i tried every combination but without success.
Command not allowed while flashing vendor image... but flashing others, like recovery or boot.img is allowed? If yes, i don't know what's causing this sorry... I'm sure that my friend @shashank1320 could surely help more than me about how using dload method correctly. Check his signature, it should contain a guide on how to use it

RedSkull23 said:
Latest build on Nougat after the update was BLN-L22C185B140 so? If yes, the package that you need to download is that one. Unluckily i can't help about dload method, i never had fortune using dload, i never be able to using it successfully because package verification always failed at 5%.
Command not allowed while flashing vendor image... but flashing others, like recovery or boot.img is allowed? If yes, i don't know what's causing this sorry... I'm sure that my friend @shashank1320 could surely help more than me about how using dload method correctly. Check his signature, it should contain a guide on how to use it
Click to expand...
Click to collapse
For fastboot yes flashing recovery or boot do work but vendor does not. Maybe the ISO is corrupted somehow I will try it again on a different machine now with the tool.
The link you posted the dload method from is the one where I initially found it as well so yea.
Also it shouldn't matter what I install since the only thing I need is the actual vendor (and product?) partition to work. I have a functional backup just TWRP cannot create/mount the partitions. So even a way to just create them without any data would actually fix my problem (at least I hope so?)

When trying to use Fastboot to flash the vendor/product img I get remote: Command not allowed (yes my bootloader is unlocked) although I can flash the recovery without any problem.
The dload method does not work as said. I placed the extracted content of the update.zip into the dload folder but the software "cannot find" the package.

algg said:
When trying to use Fastboot to flash the vendor/product img I get remote: Command not allowed (yes my bootloader is unlocked) although I can flash the recovery without any problem.
The dload method does not work as said. I placed the extracted content of the update.zip into the dload folder but the software "cannot find" the package.
Click to expand...
Click to collapse
@RedSkull23, thanks for the tag mate.
 @algg, No need to flash the vendor image as you already had the stock vendor img.
Now what else you can try is to flash the stock recovery, boot to stock recovery, select factory reset and reboot. It should most probably fix the issue.
If not, reflash the TWRP, a regular TWRO available and not specific to elite or meticulous, but generic one given by OldDroid.
I hope you have downloaded the content for dload, if not, download these for B140.
Flash this via TWRP- http://update.hicloud.com:8180/TDS/...afnaf/update_data_full_BLN-L21_hw_meafnaf.zip
no further changes and Then use dload method for this file- http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1756/g1755/v105054/f1/full/update.zip
Try above and provide feedback. This is what I could think of best possible way to have everything with all system app working.
If not, let me know and I will try to help further.

Hi, I thought I need the vendor image since TWRP (all versions) tell me "Could not mount/wipe vendor" and "Could not mount/wipe product" "invalid argument" for both.
I tried the factory reset before but it does not work. It stops at 23% then shows a red exclamation mark and just goes to the original screen with the 3 buttons (restart, shutdown and wipe).
I am currently trying to get it to recognize my sd card. But somehow it does not work through TWRP it just does not recognize the 8GB SD Card. Also I am currently on the TWRP I was before all of this happened (3.1 openkirin). Without the SD Card recognized I can't put the dload files for it on it and in turn I can't use the dload.
I mean technically it should very well be possible to fix the device since it isn't a real brick and even TWRP and Fastboot load. It's just that all those little things are somehow ruining it.

Edit: I will get a new micro sd for some reason this one does nt work. I'll say then whether the flash then dload worked.
@shashank1320
Mind explaining why I should first use TWRP to flash something and then on top of it use dload?
And why those specific files?

algg said:
Edit: I will get a new micro sd for some reason this one does nt work. I'll say then whether the flash then dload worked.
@shashank1320
Mind explaining why I should first use TWRP to flash something and then on top of it use dload?
And why those specific files?
Click to expand...
Click to collapse
Sure, let me explain.
The first file is the data file which will install few systems apps like file manager, updater, themes, clock, fm radio etc. This will work via dload as well but the installation time is around 3-7 seconds so, over the course of time and flashing few times, i realised that these PV files cannbe flashed via TWRP and it works perfectly fine specific to PV files( twrp won't supoort other stock zips). We foash this first so that it updates your buld number and also does not replace the recovery with stock (as if you flash the main update zip first, it will replace with stock recovery so flashing the 2nd file will be quick but with unstable system apps, sometime).
Now we flash the main zip file with update.app via dload and it Install the main firmware for boot, vendor, recovery, system, usrdata etc.
Hope this explanation helps, if not let me know and I will rephrase myself.

It does help. I did all of this and now in the dload app I get "Software install failed Incompatibilty with current version please download the correct update package".
When I flashed the zip you linked me with TWRP it said "cannot mount /data /vendor /product". Appearently data cannot be mounted since it is encrypted.
Any clue as to what I am doing wrong? Or is this device now a real brick with functioning recovery but without OS?

Is there any way I can "debug" what is going on while the boot animation is playing?
What is confusing me is that the boot animation plays just normal but it simply does not continue to the actual OS.

algg said:
It does help. I did all of this and now in the dload app I get "Software install failed Incompatibilty with current version please download the correct update package".
When I flashed the zip you linked me with TWRP it said "cannot mount /data /vendor /product". Appearently data cannot be mounted since it is encrypted.
Any clue as to what I am doing wrong? Or is this device now a real brick with functioning recovery but without OS?
Click to expand...
Click to collapse
Not bricked..its just Data is not mounted or encryption. Should never encrypted it. NVM.
Do one thing, boot to twrp recovery. Try flashing and get error, then go to main TWRP page and click on reboot, select recovery out of 4 options( power off, system, bootloader and recovery). It will boot to recovery, now try flashing it again and see. Most if the time it helps.
Else, go to main page, select wipe, click on format rather than wipe here, it will prompt for typing Yes to confirm. Biit to recovery from main twrp page ( as mentioned above). And try this same thing of formatting data couple of times and then flash the zip and then dload.
I know these are tedious steps but inhave revived my device many a times with all these tricks after some efforts.
Good luck

YAY it works.
Just to recap what I did:
I flashed your thing first through TWRP tried to flash your other link with dload (which did NOT work)
Then I flashed the thing (emui5 Android 7 for Europe) through TWRP played in my old backup of exactly this through TWRP cleared dalvik & cache.
Then I waited 20 minutse and now it started.
Really thanks to all of you very nice people here. I would be very baffled if it wasnt able to repair the device since Fastboot and Recovery still work.
But Huaweis recovery is beyond terrible.

algg said:
YAY it works.
Just to recap what I did:
I flashed your thing first through TWRP tried to flash your other link with dload (which did NOT work)
Then I flashed the thing (emui5 Android 7 for Europe) through TWRP played in my old backup of exactly this through TWRP cleared dalvik & cache.
Then I waited 20 minutse and now it started.
Really thanks to all of you very nice people here. I would be very baffled if it wasnt able to repair the device since Fastboot and Recovery still work.
But Huaweis recovery is beyond terrible.
Click to expand...
Click to collapse
It is terrible indeed. Glad your phone working.
Thanks to @RedSkull23 for tagging, else I may have not responded as he was already involved and was helping as usual.:good:

algg said:
Really thanks to all of you very nice people here. I would be very baffled if it wasnt able to repair the device since Fastboot and Recovery still work.
But Huaweis recovery is beyond terrible.
Click to expand...
Click to collapse
I'm happy for you man, indeed it would be so bad, especially because you got this device 3 or 4 days ago if i didn't read bad, anyway what matters is that now it works. Are you able to restore the previous backup through TWRP now? (But before trying... Make a backup of your actual OS )
shashank1320 said:
It is terrible indeed. Glad your phone working.
Thanks to @RedSkull23 for tagging, else I may have not responded as he was already involved and was helping as usual.:good:
Click to expand...
Click to collapse
Are you joking man? I just tagged you for more help, but practically you helped him in everything, not me; I'm sure that you would noticed the thread and helped as always even without my tag, i just speeded up things for being helpful to algg.
algg, I'd like to apologize myself; i didn't vanished after tagging shashank, today i just was at work and obviously i was busy for help, but as i saw with pleasure he already helped you to restore your OS and that was the objective. Nice one, guys!

Phone won't boot and can't do much from TWRP

Hi !
I installed TWRP to root my honor view 10 3/4 weeks ago.
Today I installed an update. And since then, the phone won't boot past TWRP (which I can access) or Huawei eRecovery mode.
When I land in the eRecovery mode it offers me to shutdown, reboot, or connect to wifi and do a factory reset. When I attempt the factory reset it tells me that downloading package info failed.
I tried to do a reset from TWRP without success gives me ERROR 9. I also tired to install the stock rom (update.zip) from TWRP and I also get ERROR 9.
I'm a complete noob when it comes to phones. Anyone have an idea of a solution ?
Thank you for reading !

Get a microsd card flash Dload file

aditya desai said:
Get a microsd card flash Dload file
Click to expand...
Click to collapse
Tried and it tells me system installation failed, maybe I have the wrong file ?
Thanks for your help!

ouamakavoula said:
Tried and it tells me system installation failed, maybe I have the wrong file ?
Thanks for your help!
Click to expand...
Click to collapse
Whats your model, if it is L09 then get the stock ramdisk image from magisk thread in development section and also search for recovery image. Flash it via fastboot and boot normally.
Never ever try ota on rooted phone.

shashank1320 said:
Whats your model, if it is L09 then get the stock ramdisk image from magisk thread in development section and also search for recovery image. Flash it via fastboot and boot normally.
Never ever try ota on rooted phone.
Click to expand...
Click to collapse
My model is L09, I flashed the stock ramdisk image and now I can no longer get into TWRP but I am unsure of what to do now ?
Thanks

ouamakavoula said:
My model is L09, I flashed the stock ramdisk image and now I can no longer get into TWRP but I am unsure of what to do now ?
Thanks
Click to expand...
Click to collapse
Able to boot to system now? You cam always flash twrp from fastboot. Avoid as of now and boot to stock rom first

shashank1320 said:
Able to boot to system now? You cam always flash twrp from fastboot. Avoid as of now and boot to stock rom first
Click to expand...
Click to collapse
When I try to boot the phone it displays the message that the phone in unlocked and should no be trusted, it shows the honor booting screen and after a few seconds shuts down and the process is repeating.
If i try to press the volume up key when booting it takes me to huawei eRecovery where I can either shutdown the phone or download recovery but it fails everytime.
Thanks

Try flash the No check recovery, boot into and wipe cache. Then reboot
Powered by View 10

Try this
1. Flash stock ramdisk img
2. Flash stock recovery img
3. Reboot to recovery with button combination ie; power and vol down together
4. Wipe data and cache
5. Reboot.
Hopefully it'll work if it doesn't flash system.img after 1 & 2 steps and follow the next steps

Hi please specify model
And what update you installed...
If the update was genuinely meant for phone I believe a data and cache partation format should fix this..
I hope you are atleast seeing the honor bootscreen...
Specify model so that we could point you to correct system.img
Also did twrp gave any errors formatting cache memory?

same here
BKL-L09

Tried it all with bricked Honor 6x. Any help is appreciated

I already posted here, but i was with no pc for some weeks so couldnt answer to the thread and now its old, Im back.
Situation is like this, huawei gr5 2017 (bll l22) bricked after bad flashing and software manipulation.
Vol down + power gets me to fastboot, it says phone unlocked and FRP unlock.
Download method with vol down + vol up + power doesnt work, always stuck at 5% saying "software install failed, incompatibility with current version" or doesnt say anything at all, just stuck at 5%.
Also, when i try to wipe data/factory reset from stock revoery it says "reset failed"
So dload method doesnt work, i also tried using DCPHOENIX software which saved one of my older huawei phones but it didnt work at all this time. When i flash a twrp recovery through fastboot, it flashes succesfully but when i boot into it it just boots into the stock one, and there the restore to stock option always fails after i connect to wifi saying that "failed to reach the server" or "failed to download the firmware", something like that.
I had twrp some days ago, out of the blue it booted into it. I had stock firmware on my sd card fortunately so i tried to flash the zip and itfailed with error 6 or 7, cant remember which. Anyways that twrp instance dissapeared after a reboot and now its always stock recovery, cant install twrp (described that above already).
So, do i have any options? nothing seems to work. no recovery, no dload, no dc phoenix, no fastboot (i tried flashing boot, system images through fastboot but it denied access to those partitions) flashing, i tried sp flash tool but the honor 6x roms have no scatter file and the flash tool requires one
Help, please. Ill appreciate it

What was your EMUI version before brick? Have you tried manually booting into TWRP? After you finish flashing don't reboot. Just hold power & volume down. If not then try to load TWRP recovery. It won't install but sort of load it. I don't know the exact command. If your phone is bootloader unlocked and frp unlocked try fastboot erase. System and then user data. I had a hard brick and it was even worse. No recovery, no fastboot and no dload. Just stuck. Managed to fix it myself without DC or Phoenix. So don't lose hope.

Mannan Qamar said:
What was your EMUI version before brick? Have you tried manually booting into TWRP? After you finish flashing don't reboot. Just hold power & volume down. If not then try to load TWRP recovery. It won't install but sort of load it. I don't know the exact command. If your phone is bootloader unlocked and frp unlocked try fastboot erase. System and then user data. I had a hard brick and it was even worse. No recovery, no fastboot and no dload. Just stuck. Managed to fix it myself without DC or Phoenix. So don't lose hope.
Click to expand...
Click to collapse
I cant remember if it was marshmallow or nougat so it was either emui 4 or 5. Im trying it all again and it doesnt work but ill keep doing it i guess

Try flashing recovery of nougat and then manually try to boot. Or maybe try to load the recovery without installation. It has a different command but I dunno.

hi, I have pretty much the same problem, somehow wiped the 'system' through TWRP. And since then I am trying to flash TWRP to boot, but I am getting nothing. I had EMUI 8
Tried flashing stock nougat through Multi Tool but no use, it succeeds but does not boot into anything, just the stock recovery whenever I turn it on.
Whenever I flash TWRP and try to boot into recovery (Vol-up+power), it would always boot into stock recovery.
Tried booting into eRecovery, but same thing.
Tried command fastboot boot RECOVERY-V2.img, but got the problem saying 'command not allowed'
what to do.