Database Info

Accidentally wiped everything

So in the process of updating my rom, I managed to damage my /data/ partition, meaning I now have no ROM on my phone. I've updated TWRP to the newest version, I've got a stock firmware on file and a custom firmware if needed, both CWM and TWP on file, I've tried flashing or running all of the above but I can't get anything to actually load to the phone. I've also tried loading a rom via USB-OTG but I can't get it to mount. Normally in this situation I'd run an odin update for the stock firmware but I can't find anything about that, and all the brick threads in XDA don't seem to be helping. Does anyone have some suggestions?
Edit: I do have fastboot access but no ADB. Sideload isn't working through TWRP and I don't know why.

You have to return to stock using flash boot... It happened to me as well...

Well, I tried http://forum.xda-developers.com/showthread.php?t=2542219 and now I'm looking at the "warning: unlocked bootloader" screen...

Accidentally wiped system partition of huawei mate 9 dualsim

Hi im new here and i need help :^;
Have a huawei mate 9 (dual sim, unlocked bootloader) and accidentally wiped the system partition through twrp (custom for huawei mate 9 through xda so not all functions work)
tried:
- fastboot flashing system.img, boot.img and revovery.img from update.zip (MHA-L29C432B176) from "techora"
--- this ended up as a boot loop
- flashing the update.zip through twrp but i got an error message for unknown command (probably because update.zip is not made for twrp)
- using dload/UPDATE.APP using ext sd card after flashing recovery.img but nothing happened, cant access internal storage so cant move the dload folder there
- hisuite system recovery but rejected my phone because it is unlocked ... tried to relock phone but still got rejected
please help ;^;
Thanks

Got it working but not optimal
how i got it working with fastboot and twrp:
flashed romaur1.5 along with system.img from a MHA-L29C636XXX full update zip
the boot img from that was a bit messed so flashed KangVIP custom rom boot.img (dont flash the whole rom there tons of chinese bloat) ---- i probably didnt need to flash the romaur, just system.img and boot.img
that fixed everthing kinda. the os booted fine but there was a messed keyboard (google voice keyboard that didnt work) so i skipped everthing and installed a google keyboard apk, then went into Settings to redo the startup things i didnt do. The other problem is that my phone is permenantly rooted with SuperSU, cant uninstall or update through the app :/ factory resetting didnt remove the root (after flashing the stock recovery.img from update.app)
Thats all..

henry931 said:
how i got it working with fastboot and twrp:
flashed romaur1.5 along with system.img from a MHA-L29C636XXX full update zip
the boot img from that was a bit messed so flashed KangVIP custom rom boot.img (dont flash the whole rom there tons of chinese bloat) ---- i probably didnt need to flash the romaur, just system.img and boot.img
that fixed everthing kinda. the os booted fine but there was a messed keyboard (google voice keyboard that didnt work) so i skipped everthing and installed a google keyboard apk, then went into Settings to redo the startup things i didnt do. The other problem is that my phone is permenantly rooted with SuperSU, cant uninstall or update through the app :/ factory resetting didnt remove the root (after flashing the stock recovery.img from update.app)
Thats all..
Click to expand...
Click to collapse
SuperSU is in boot.img so you'd have to restore that to get rid of root.
You could use this: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
To get back to your old version or get to B190. Backing up /data is recommended if you're decrypted, or backup using titanium or similar. (that's if you want to unlock bootloader again after it's done, since it does a factory reset.)
Or you could try flashing system.img directly in twrp, to the /system partition. Youd have to flash your boot.img for B176 for this though.

ante0 said:
SuperSU is in boot.img so you'd have to restore that to get rid of root.
You could use this: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
To get back to your old version or get to B190. Backing up /data is recommended if you're decrypted, or backup using titanium or similar. (that's if you want to unlock bootloader again after it's done, since it does a factory reset.)
Or you could try flashing system.img directly in twrp, to the /system partition. Youd have to flash your boot.img for B176 for this though.
Click to expand...
Click to collapse
I've tried that, and it doesnt work for me, going to try different boot.img from another post on xda

lol that didnt work because my system image was too old, i flashed a newer version of supersu and it installed systemless and uninstalled my old one

You could have just downloaded your update.zip, taken out update.app, extracted system.img and made a flashable zip.

Powerlated said:
You could have just downloaded your update.zip, taken out update.app, extracted system.img and made a flashable zip.
Click to expand...
Click to collapse
cant be bothered, id rather just flash through fastboot

Can't get into system nor recovery

I was trying to root my zenfone 4 max (ZC554KL), and I found out that apparently I had to downgrade to another firmware, since I wasn't able to use the flash-all script that came with it, I tried to do it by imitating the script manually, by trying to do that, I screwed things up and soft bricked my phone. I also cannot get into recovery. I have flashed both TWRP and stock recovery img, but I am unable to get into recovery, it just goes back to the unlocked bootloader menu. I have tried flashing the firmware again by converting the system dat files to img, but I still cannot boot into system. I have zero idea on what do now. Please help me.

Bootloop after Magisk, even after reflashing original boot.img

I let the phone do the upgrade by itself. It booted into Android 10, I downloaded walleye-qq1a.200105.002-factory-877e8ab1.zip extracted the big zip, extracted boot.img, let Magisk patchit, flashed it with fastboot.exe flash boot went okay, rebooted, bootloop. Flashed back the unpatched boot.img, still bootloop. Downloaded walleye-ota-qq1a.200105.002-cfc5642b.zip used the payload_dumper Python script to get boot.img, verified with md5sum this is the same boot.img I am using. Downloaded one older, walleye-qq1a.191205.008-factory-fcc4bb81.zip tried to flash boot.img from that, we are still bootlooping. What now?

Hello mate, might be quicker to post your issue in this thread as it's very active. List your steps clearly re updating/flashing/patching magisk and I'm sure someone while chime in with a way forwards to resolve your bootloop issues.
https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/page3788

How to unbrick my OP7?

Hello I really need help!
Not quite sure I got myself into this mess but I can't boot into the system as there is no OS and there also isn't any recovery. Whenever I turn my phone on it goes into the bootloader (fastboot). I have tried to flash TWRP.img with flashboot but I am getting that the partition cannot be found (recovery_b).
What can I do? I have tried using the MSM tool but I also can't get the driver to install.
I believe I got here by wiping all of the data on TWRP (system ect... and also the factory reset)
Any suggestions/help would be appreciated!
Thank you.

So, there's no twrp, neither an OS. that's why it's stuck in bootloop.
You need to flash a custom rom(Lineage OS, I would suggest), but first you need to install twrp using PC.
Here's this post you can go through or you can also check this tutorial.