Database Info

[Q] Cannot restore backup, need stock ROM or help [RESOLVED]

I was trying to restore a backup made yesterday and had an md5 mismatch. I removed the md5 keys from the file, which allowed CWM to restore /data but once it got to /system it failed,
Restoring system...
Error while restoring /system!
I've found this...
http://forum.xda-developers.com/showpost.php?p=34555560&postcount=11​but it doesn't help.
The OP says to restore via TWRP, but my system/windows is not recognizing the phone via ADB so I cannot flash TWRP using fastboot.
Are these files available for CWM at all?

Are you able to boot into fastboot by holding power+volume down at boot? If so you can flash twrp and then flash the stock backups through twrp. I have never had issues with my pc recognizing my phone in adb mode with the phone in fastboot as far as flashing recovery, boot logo, etc. I am not able to get adb to push/pull files while in fastboot. Whether or not this works may depend on if you had usb debugging enabled in developer options prior to soft-bricking your phone.
Sent from my XT897 using xda app-developers app

UnicronAlpha99 said:
Are you able to boot into fastboot by holding power+volume down at boot? If so you can flash twrp and then flash the stock backups through twrp. I have never had issues with my pc recognizing my phone in adb mode with the phone in fastboot as far as flashing recovery, boot logo, etc. I am not able to get adb to push/pull files while in fastboot. Whether or not this works may depend on if you had usb debugging enabled in developer options prior to soft-bricking your phone.
Sent from my XT897 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the reply. I can get to fastboot, I tried just kind of blindly flashing the twrp recovery image, and you're right, it worked even though 'adb devices' still didn't show it.
So I'm back on TWRP but now, after following the instructions to create the TWRP backup folder on the SD card and restoring the files provided by drakeheart77, TWRP tells me there's no OS installed when I try to reboot to the system. All the posts I read suggest flashing a new ROM but... there aren't any ROMs from what I can tell.
As I said in the OP, I tried to restore a backup and ran into the md5 mismatch error, but I didn't say that in my noob-ness, formated everything I could and lost my OS because of that (at least from what I'm deducing... still noob-ness).
Any suggestions? Thanks again!

I'm guessing the "no os" error is due to not having anything in the /data folder. Try flashing this through twrp: http://forum.xda-developers.com/showthread.php?p=32514141
It is a backup of the stock odexed rom. Put the files in the twrp/backups/serial#here/ folder and try flashing it. Assuming that gets you up and running all you have to do to is flash the stock recovery.img through fastboot to download the ota update, if you want to.
For future backups try having twrp save them to your external sd card by selecting it in the backup menu. That way if you need to wipe internal storage for any reason you will have the external backups safe and ready for use.
Sent from my XT897 using xda app-developers app

UnicronAlpha99 said:
I'm guessing the "no os" error is due to not having anything in the /data folder. Try flashing this through twrp: http://forum.xda-developers.com/showthread.php?p=32514141
It is a backup of the stock odexed rom. Put the files in the twrp/backups/serial#here/ folder and try flashing it. Assuming that gets you up and running all you have to do to is flash the stock recovery.img through fastboot to download the ota update, if you want to.
For future backups try having twrp save them to your external sd card by selecting it in the backup menu. That way if you need to wipe internal storage for any reason you will have the external backups safe and ready for use.
Sent from my XT897 using xda app-developers app
Click to expand...
Click to collapse
Wow, that worked. So relieved I don't have a large black paperweight now... lol Thank you!

No problem man, glad you got it working. That backup Rangerbry posted unbricked my phone at one point and saved me a paperweight. This really is a great phone once you accept the little quirks.
Sent from my XT897 using xda app-developers app

Phone Won't Turn On; Soft Keys Flashing When Buttons Are Pressed

Hi all,
So, last night I successfully rooted and unlocked my One X on AT&T. Today, I tried putting a ROM on it. I flashed the boot.img first, then tried to install the ROM (Jelly Bean Sense). It failed for some reason, so I wiped and rebooted my phone.
Instead of going back to the stock ROM, the phone now will not turn on, is not recognized on both laptops I tried, and does not recognize even being charged. The only thing that happens is when I press down the power button, all of the soft keys illuminate and flash until I stop holding it. I've managed to get into the bootloader screen once, but the phone reset itself before I could do anything.
The only screen I can get to with the Vol Down+Power combo is the HTC Screen, but it's the one that shows before my custom recovery, with some warning from HTC in red letters at the bottom.
At this point, I just want a phone that works. This is a lot more complex [for me] than rooting and flashing a ROM to the Inspire I had for some reason. I fly out for vacation in two days for a few weeks, so I'd like to be able to avoid having to send this thing back to HTC or AT&T if possible.
ANY help is greatly appreciated.
If it's easier, feel free to Skype chat me.
Thanks!

Im confused.. it won't come on, but you can get to recovery? If you can manually boot into twrp you'll be fine.. may I ask which Rom you flashed? Did you flash the boot.img first? Or after you flashed Rom? Alot of guys will say flash boot.img first.. I don't have that funky hboot but I have to do my cousins alot and his will only boot correctly if I flash Rom first, then boot into bootloader and fastboot the boot.img.
Try that and let me know how it goes
Also... Let go of all the buttons when you see the white screen lol. That means you found bootloader
Sent from my HTC One XL using Tapatalk 2

InflatedTitan said:
Im confused.. it won't come on, but you can get to recovery? If you can manually boot into twrp you'll be fine.. may I ask which Rom you flashed? Did you flash the boot.img first? Or after you flashed Rom? Alot of guys will say flash boot.img first.. I don't have that funky hboot but I have to do my cousins alot and his will only boot correctly if I flash Rom first, then boot into bootloader and fastboot the boot.img.
Try that and let me know how it goes
Also... Let go of all the buttons when you see the white screen lol. That means you found bootloader
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
I can get it to boot into the Bootloader screen and the TWRP now just fine, but that's as far as it will go. The internal SD will not mount with TWRP either now.
Here's the ROM I tried to flash: http://forum.xda-developers.com/showthread.php?t=2055490
I put it on my SD card, then extracted the boot.img to the folder I have my dab/fastboot files in, then flashed the boot.img, then tried to flash the ROM.
If I can get it working again, I'll try to do it in reverse order next time and see if that works. Still trying to find a way to get a ROM on here with my Mac, and to make my SD card work again. Everything on it is backed up so it's ok if I need to wipe it.

If you can get to bootloader, you're not bricked. It's just a matter of flashing the right stuff in the right order.
It could be that your sdcard is corrupted. Factory reset from bootloader will do it, but fixing it just a matter of formatting it again. Can you mount it on your computer? What happens when you plug into your PC?

Your sdcard is corrupt. No big deal but you'll lose everything. Plug it in into computer and locate the storage and try to find a way to format it. Sorry, I have no clue with a mac I swore off apple products :thumbup:
Anyway, you seem to know the ropes for the most part. If you can format, drag Rom onto SD. Wipe everything in twrp. Cache, dalvick, factory reset, system. Flash Rom.. immediately boot into bootloader and fastboot the boot.img. choose reboot from bootloader. Good luck!
Sent from my HTC One XL using Tapatalk 2

Yep, I also suggest doing a factory reset from the bootloader ( which will erase your internal storage) but at least you'll be able to mount your SD card, put a ROM on it and flash it. I would highly recommended you to flash viper 3.0.0, you don't need to flash the boot.img and its pretty much stock JB with some tweaks.
Sent from my HTC One XL using Tapatalk 2

I am having this same problem (minus the custom screen).
My phone will boot into TWRP and all, but it won't mount (PC says the disk needs to be formatted before it can be used). When I go to reboot or anything from TWRP, it tells me there is no OS installed and am I sure.
Can anyone help?

That's good news!
I tried doing a factory reset from bootloader, but nothing happened. Maybe because the SD card won't mount?
I only have a Mac, with no PC in sight. It doesn't show up at all on here. Fastboot USB, or when I mount it as USB in TWRP. It does however show up as a device in recovery in terminal. But nothing on the desktop. Apple+Android do not mix well!
I'm ok with losing my data, what I'm not OK with is having to use this pink Razr while my nice phone is broken :'(
Thanks for all the help so far!

I do a factory reset from bootloader, it takes me into TWRP. Now is the only time it will even remotely show up on my laptop, and even then it's only via terminal when I do adb devices. Since it can't mount for some reason, is there a way to reformat via Terminal, and maybe even push the ROM to my phone from there? That's something I'm not familiar with.

elijahpr said:
I do a factory reset from bootloader, it takes me into TWRP. Now is the only time it will even remotely show up on my laptop, and even then it's only via terminal when I do adb devices. Since it can't mount for some reason, is there a way to reformat via Terminal, and maybe even push the ROM to my phone from there? That's something I'm not familiar with.
Click to expand...
Click to collapse
Format your sd..drag Rom..wipe..flash..enjoy

omario8484 said:
Format your sd..drag Rom..wipe..flash..enjoy
Click to expand...
Click to collapse
I can't format because it doesn't show up on my computer, and doing so in bootloader takes me to TWRP.

emylibef said:
I am having this same problem (minus the custom screen).
My phone will boot into TWRP and all, but it won't mount (PC says the disk needs to be formatted before it can be used). When I go to reboot or anything from TWRP, it tells me there is no OS installed and am I sure.
Can anyone help?
Click to expand...
Click to collapse
Hey dude, I followed their advice (dug out my XP machine) and now my SD card is re-formatted.
Get into the bootloader screen, hit factory reset. (When I did this on mine, it took me right to TWRP)
From there, I mounted as USB and it showed up as needing to be reformatted on my XP machine. Took a few minutes to do on this dinosaur, but it worked, cause everything is gone!
Right now I'm in the process of zipping up the Viper XL ROM (thanks for the recommendation barondebxl, it looks awesome!), which I'll put onto my SD card and wipe/flash from there. (on my Mac now).
Hopefully it works!

I'm unable to flash ROMs for some reason. It doesn't give an error, just says that it failed. Any ideas?

elijahpr said:
Get into the bootloader screen, hit factory reset.
Click to expand...
Click to collapse
No no no. This is what is corrupting your sdcard. Only do a factory reset in TWRP or once booted up. Start over and format again. Then copy over your rom.

When you and a few others mentioned doing it, what were you referring to?
I've tried three different ROMs now, and each fails without saying why in TWRP.

Problem solved! Got the stock RUU back on there and it works perfectly. Just re-rooted and unlocked again. Round two..

[Q] AT&T HTC One X Softbricked-CMmod

I believe I have bricked my phone. I was running a rooted HTC One X AT&T with an odex Jellybean/HTC Sense 4+ ROM. I wanted to test out a Cyanogenmod. Big mistake. I tried to flash it from TWRP recovery, after backing up my previous ROM, however, it was stuck in an endless boot loop. I took advice from some people online and reflashed it/ wiped caches/dalvik cache etc... When I realized it would not work unless I fastbooted it myself using USB debugging I tried to reinstall the old ROM, of course, after wiping the Cyanogenmod. Long story short there was no backup even though I backed up the phone! I now have no ROM and everything on my system is gone! My SD card folder only has a TWRP recovery and I can't install any .zip files. TWRP isn't even allowing me to mount my SD card so putting any files are out of the question. I believe, however, that usb debugging was on the whole time (is it on if on the boot loader it says fastboot usb when I plug in a USB?). Is there anyway to fix this?? I'm really screwed if I can't and please don't direct me to another thread because I need personalized help. I'm doing this on a mac by the way so anyone who knows how to use the terminal would help a lot. I can get access to windows though if needed. Just please help.

Have you tried to flash the boot.img from the zip file in fastboot?

Do you know what a brick is? When your phone does NOTHING... Similar to a brick.
What happened to you is you didn't flash the boot.img through fastboot, which caused your first problem, the bootloop..
Second thing you did incorrect was perform a factory reset in boot loader... Which completely wipes your SD card and corrupts it, and which just so happened to contain your backup no worries, easily fixable...
Download a rom on your computer. While its downloading, enter recovery and choose mount. Navigate to my computer and right click the removable storage option. Choose format. Once its done, drag rom onto phone.. Flash rom in twrp.
Extract rom on your computer, grab the boot.img and flash with fastboot.
Fastboot flash boot boot.img
Reboot phone and profit
EDIT: sorry but I hastily skimmed through your post... Those are half-assed instructions for windows, I have no clue what to do on a mac
Sent from my One X using Tapatalk 2

What he said. Toolkits are easily found too

I don't know what my buddy did...

Wow this thing sucks! I'm really appreciating my Samsung with Odin right now! So, I have years of experience rooting and flashing Samsung phones with minimal adb experience. My buddy from work asks me if I can try to fix his shield tab that he F'd up trying to flash a rom on. Come to find out he never unlocked the bootloader or flashed a recovery or rooted the dang thing, just tried to flash the rom over stock like a numbskull. We thought it was dead forever because the only thing that would mount or connect in adb was the side load through the stock recovery. So, I finally got it to connect to fastboot (don't ask me how, I don't know), unlocked the bootloader, and flashed twrp. Now it won't flash supersu in adb sideload, so I put it on an SD card (which now magically mounts and works now) and flashed the zip in recovery but it says at the very end of the process while trying to update the partitions that it can't mount the data and system partitions so I'm not sure if I'm actually getting root or not and if so if it's permanent even though it says "success" at the top after flashing. I have no way to tell. I think this is because they have been accidentally wiped. Do you think it is safe to try to flash a rom in recovery from external sd card? And if so, which one? I have no idea which version bootloader, kernel, or os is, or was, on this device, I'm not familiar with any of the roms for it, and I'm not sure what prerequisites there may be for some of them....
Thanks for the help!

rom fiend said:
it can't mount the data and system partitions so I'm not sure if I'm actually getting root or not and if so if it's permanent even though it says "success" at the top after flashing. I have no way to tell. I think this is because they have been accidentally wiped. Do you think it is safe to try to flash a rom in recovery from external sd card? And if so, which one?
Click to expand...
Click to collapse
I had the same Problem with the partitions you discribed, have tried wipe them, change the file format and change it back?
I flashed a lot of Roms from the external SD Card and it worked every time.
I think you should go with Bliss Rom. ( Just try Lollipop and Marshmallow)

OverBit said:
I had the same Problem with the partitions you discribed, have tried wipe them, change the file format and change it back?
I flashed a lot of Roms from the external SD Card and it worked every time.
I think you should go with Bliss Rom. ( Just try Lollipop and Marshmallow)
Click to expand...
Click to collapse
I can't wipe them because they won't mount. It's as if the partitions were erased completely. Not like the partitions were wiped, but like they don't exist at all anymore...
What do you mean by changing the file format? Format of what?

rom fiend said:
What do you mean by changing the file format? Format of what?
Click to expand...
Click to collapse
TWRP, wipe ,Advanced wipe
If that doesn't work just try installing a rom, boot it
If that doesn't work try this

Tried all recovery options and tried flashing bliss 6.2 with no luck. It says that it flashes successfully but also shows some errors about not being able to mount the system and data partitions. Then when I try to reboot it gets stuck at the nvidia logo (this is the closest that I've gotten to booting a rom). I can provide pictures if you want. I'm going to try the steps that you linked to as soon as the files download.

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!