Related
This is pretty much my first time doing such things in my phone. I rooted my phone and installed ARHD 11.2 without any trouble following the instructions. When ARHD released 21.0, I tried flashing the ROM but my WiFi stopped working which I did my research and found out that it requires a firmware update (3.28.xxxx) to work. So I tried FireWater which didn't work for some reason and bought SunShine which work out as expected and my M8 is now S-OFF & set my CID to 11111111.
Now, here comes the problem. I flashed 3.2.8.401.7 firmware downloaded from ARHD blog and it returns a SUCCESSFUL but with an ERROR 90, which I also did search and said that I just have to flash the firmware again without reboot in between. Now when I boot up my phone, it's stuck on the HTC Logo with an android text below it and doesn't boot up. I went into the bootloader and tried going into recovery but it went to a black screen with and phone with a red triangle and exclamation mark in between. I erased the cache with fastboot erase cache but still didn't work. Also, I noticed that on the top of my bootloader, it says "*** Software status: Modified ***". I don't know if that is supposed to be there. I remembered TAMPERED banner was supposed to be there. My M8 is unlocked as well.
TWRP 2.8.1.0
CID-11111111
HBOOT-3.19.0.0000
RADIO-1.21.21331147A1.19_2G
I followed this guide: VomerGuides [M8]: Bootldr Unlock, S-OFF, SuperCID, Firmware Upgrade & Custom Recovery
EDIT: Solved thanks to lukes91
Solution: Flash custom recovery and then flash ROM via ext_sd and you should be good to go.
Serenity13 said:
This is pretty much my first time doing such things in my phone. I rooted my phone and installed ARHD 11.2 without any trouble following the instructions. When ARHD released 21.0, I tried flashing the ROM but my WiFi stopped working which I did my research and found out that it requires a firmware update (3.28.xxxx) to work. So I tried FireWater which didn't work for some reason and bought SunShine which work out as expected and my M8 is now S-OFF & set my CID to 11111111.
Now, here comes the problem. I flashed 3.2.8.401.7 firmware downloaded from ARHD blog and it returns a SUCCESSFUL but with an ERROR 90, which I also did search and said that I just have to flash the firmware again without reboot in between. Now when I boot up my phone, it's stuck on the HTC Logo with an android text below it and doesn't boot up. I went into the bootloader and tried going into recovery but it went to a black screen with and phone with a red triangle and exclamation mark in between. I erased the cache with fastboot erase cache but still didn't work. Also, I noticed that on the top of my bootloader, it says "*** Software status: Modified ***". I don't know if that is supposed to be there. I remembered TAMPERED banner was supposed to be there. My M8 is unlocked as well.
TWRP 2.8.1.0
CID-11111111
HBOOT-3.19.0.0000
RADIO-1.21.21331147A1.19_2G
I followed this guide: VomerGuides [M8]: Bootldr Unlock, S-OFF, SuperCID, Firmware Upgrade & Custom Recovery
Click to expand...
Click to collapse
it looks like you still have stock recovery... flash a custom one and try to boot, but you might need to reflash the rom... let me know
lukes91 said:
it looks like you still have stock recovery... flash a custom one and try to boot, but you might need to reflash the rom... let me know
Click to expand...
Click to collapse
Thanks lukes91, I noticed that some people said that the Red triangle with a ! mark on it means that it's Stock Recovery. I didn't know why my TWRP got wiped off when I flashed the firmware. I'll give it a try and update this post.
edit: I'm afraid that for some odd reason. I can't get my phone connected with ADB. It's just says device not found when bootloader says FASTBOOT USB. I reinstalled the drivers from HTC Sync and tried it with HTC Sync installed and uninstalled but I still can't get it to work. I'm plugged into USB 2.0 port.
edit2: I tried plugging in my phone while it's stucked on the HTC logo. My computer detects the Phone and opens up the Internal Storage from my Computer. I have bunch of folders inside which is empty and about 0.3GB storage are used. I'm afraid that it might have to do with the USB Debugging option is off which I do not know how to get it on in bootloader.
edit3: Okay I managed to get TWRP flashed finally. How do I get the ARHD 21.1 ZIP into the Phone? I tried ADB Sideload but it just gets stuck at "Starting ADB Sideload feature..." I tried entering the command in CMD and it said Cannot read file "rom.zip"
Serenity13 said:
Thanks lukes91, I noticed that some people said that the Red triangle with a ! mark on it means that it's Stock Recovery. I didn't know why my TWRP got wiped off when I flashed the firmware. I'll give it a try and update this post.
edit: I'm afraid that for some odd reason. I can't get my phone connected with ADB. It's just says device not found when bootloader says FASTBOOT USB. I reinstalled the drivers from HTC Sync and tried it with HTC Sync installed and uninstalled but I still can't get it to work. I'm plugged into USB 2.0 port.
edit2: I tried plugging in my phone while it's stucked on the HTC logo. My computer detects the Phone and opens up the Internal Storage from my Computer. I have bunch of folders inside which is empty and about 0.3GB storage are used. I'm afraid that it might have to do with the USB Debugging option is off which I do not know how to get it on in bootloader.
edit3: Okay I managed to get TWRP flashed finally. How do I get the ARHD 21.1 ZIP into the Phone? I tried ADB Sideload but it just gets stuck at "Starting ADB Sideload feature..." I tried entering the command in CMD and it said Cannot read file "rom.zip"
Click to expand...
Click to collapse
put the rom zip inside ext_sd and flash from there
it's the easiest way...
lukes91 said:
put the rom zip inside ext_sd and flash from there
it's the easiest way...
Click to expand...
Click to collapse
Best answer :good:
lukes91 said:
put the rom zip inside ext_sd and flash from there
it's the easiest way...
Click to expand...
Click to collapse
Alright I'll give it a try. I did try it and placed it in the internal storage but the file went missing after I rebooted into recovery. I'll try your directory instead and give a reply asap.
I actually felt embarrassed on that and my stupidity lol.
edit: Thanks very much! I flashed ARHD 21.1 and now it worked. Now I feel more embarrassed after the ext_sd incident...that actually works.
Serenity13 said:
Alright I'll give it a try. I did try it and placed it in the internal storage but the file went missing after I rebooted into recovery. I'll try your directory instead and give a reply asap.
I actually felt embarrassed on that and my stupidity lol.
edit: Thanks very much! I flashed ARHD 21.1 and now it worked. Now I feel more embarrassed after the ext_sd incident...that actually works.
Click to expand...
Click to collapse
Great! Glad i helped
Sent from here
Serenity13 said:
I noticed that some people said that the Red triangle with a ! mark on it means that it's Stock Recovery. I didn't know why my TWRP got wiped off when I flashed the firmware.
Click to expand...
Click to collapse
If the firmware zip contains stock recovery, of course its going to overwrite TWRP with stock recovery. Sometimes, folks here will intentionally remove stock recovery from the firmware zip (for the express purpose of preventing custom recovery from being wiped when flashing the firmware). But as it comes with an OTA, it will contain stock recovery.
---------- Post added at 10:12 AM ---------- Previous post was at 10:08 AM ----------
Serenity13 said:
edit3: Okay I managed to get TWRP flashed finally. How do I get the ARHD 21.1 ZIP into the Phone? I tried ADB Sideload but it just gets stuck at "Starting ADB Sideload feature..." I tried entering the command in CMD and it said Cannot read file "rom.zip"
Click to expand...
Click to collapse
I know you solved your issue another way. But the adb syntax needs to contain the actual file name, in place of "rom.zip" (with no quotes). This is assuming from the error message that you did not actually rename the file to "rom.zip"(which is another way to do it).
redpoint73 said:
If the firmware zip contains stock recovery, of course its going to overwrite TWRP with stock recovery. Sometimes, folks here will intentionally remove stock recovery from the firmware zip (for the express purpose of preventing custom recovery from being wiped when flashing the firmware). But as it comes with an OTA, it will contain stock recovery.
---------- Post added at 10:12 AM ---------- Previous post was at 10:08 AM ----------
I know you solved your issue another way. But the adb syntax needs to contain the actual file name, in place of "rom.zip" (with no quotes). This is assuming from the error message that you did not actually rename the file to "rom.zip"(which is another way to do it).
Click to expand...
Click to collapse
Well I did rename the original name(Android_Revolution_HD-One_M8_21.1.zip) to rom.zip since it's way long and it didn't work the first time I entered adb side load Android_Revolution_HD-One_M8_21.1.zip. I renamed to rom.zip just to see whether if it works but I still received the same error. It could be something wrong with the ADB Sideload. It got stuck at "Starting ADB Sideload feature..." but "adb devices" listed the device with sideload tag on it. Thanks to lukes91, the method he posted above, which was the most simplest method that I should have done at the first place works perfectly.
Serenity13 said:
It could be something wrong with the ADB Sideload.
Click to expand...
Click to collapse
Could be, I've found adb sideload to be finicky, and adb push to be more reliable. Although sideload is good to have in your bag of tricks "just in case". And of course the method you eventually used (putting it on the removable SD) works, as well.
The other common cause for the error message "cannot read file" is that the file is accidentally named rom.zip.zip due to the user not realizing they have the Windows option selected to hide file extensions (and erroneously adding ".zip" to the file name). But as you loaded and flashed the file successfully by putting it on the removable SD, this likely is not the case either.
You had the ROM zip in the same folder as your adb executable, right (when trying to sideload)? An obvious thing, probably. But just asking, since its sometimes the seemingly obvious things that trip us up.
redpoint73 said:
Could be, I've found adb sideload to be finicky, and adb push to be more reliable. Although sideload is good to have in your bag of tricks "just in case". And of course the method you eventually used (putting it on the removable SD) works, as well.
The other common cause for the error message "cannot read file" is that the file is accidentally named rom.zip.zip due to the user not realizing they have the Windows option selected to hide file extensions (and erroneously adding ".zip" to the file name). But as you loaded and flashed the file successfully by putting it on the removable SD, this likely is not the case either.
You had the ROM zip in the same folder as your adb executable, right (when trying to sideload)? An obvious thing, probably. But just asking, since its sometimes the seemingly obvious things that trip us up.
Click to expand...
Click to collapse
Yep I had the ROM zip at the same folder as the adb executable. I did tried both rom.zip and rom.zip.zip in case it was the extension setting mistake. Still it was a happy ending. I got my firmware and ARHD updated. It feels so good to be updated. :good:
Hey,
I wanted to create an nandroid backup in TWRP and got error 255 in the process.
I got the log of the failed update:
cloud.directupload.net/dfZq
So i searched for a solution, and the internet said that i should remove the file wich causes backup to fail. The logs said it was '/system/app/AndroidPay'
This is a file, not a folder.
So i removed the file, keeping an backup of it, booted into TWRP and the backup still failed.
To my surprise the boot into OxygenOS fails now. It shows the Oneplus Powerd by Android logo, turns black and reboots into twrp. Recovery and Bootloader seems to work fine.
So I connected my device with my computer and tried to get the file back to '/system/app' using adb.
I tried 'adb push AndroidPay /system/app' and it seems to be transferred succesfully, however the boot into oxygenOS is still not working.
I think it can be fixed by formatting the device and flash OxygenOS new to it, but I really don't wanna do that.
General Information:
Oneplus 3
OxygenOS 3.3.4
Rooted
Xposed Installed
No custom kernal
TWRP 3.0.2-0
File wich may be broken: cloud.directupload.net/dfZs
Is there an easyer way than resetting my whole phone to get it to work ?
I'm sorry for language mistakes or maybe leaving relevant information.
Thank you for help
I've had same problem today, my solution is restore "System" part (only system) from old backup, it saved my data and OP3 works fine after that
Wipe system, then flash OOS and it should work fine. If it doesn't Im afraid you need to do a full clean install since it isn't system related then.
Hello everyone!
My oneplus3 is actually running no OS and I'm having a boot loop.
I will try to explain what happened to me with the most details I can.
Before I ****ed everything up, I think I was running OxygenOS 3.28, not really sure about it but im 100% sure it was below 4.0, and it was rooted with TWRP 3.0.2 installed.
1) Today I had a pop up saying OxygenOS 4.0.2 was available (the official one that pops on the screen on boot) "Yay so coooool Nougat!"
1.1) I downloaded it, 1.4Go, then I pressed install
1.2) TWRP showed up, I didn't know what to do and that's where I ****ed up, I set my phone "factory new" in TWRP.
1.3) Phone restarted fresh new, I thought I had 4.0.2 but naaaaah would've been too easy so the official pop up showed again, I was still 3.28 I think.
1.4) Downloaded it once more, TWRP opened again, this time i was looking for the update i just downloaded in the "install" section. I browsed for quite a while and couldn't find it.
1.5) Master ****-up here: I tried to restore a backup. Then the bootloop happened. The black screen with "Oneplus" written in white. I was able to go back in TWRP by pressing power + volume down
1.6) Tried every kind of restore unsuccessfully, and tried ADB but it wouldn't load. Also TWRP said that I was running no OS when I wanted to turn off my phone for example.
2) I downloaded 4.0.2 from one plus website on my mac, and i flashed the official recovery instead of TWRP.
2.1) Transferred the update from my mac to my PC (seems important to me) and installed ADB & everything on both PC/O+3.
2.2) so adb worked in forceboot, i've been able to flash official recovery, tried once more to wipe & everything, but clearly I have no OS now, as TWRP said.
2.3) so i had the update in a folder (not a zip, probably due to the download being done from a mac), I made it a .ZIP with winrar, but "adb sideload update.zip" crashed at 0% everytime
2.4) looked at the archive then i noticed it was first a folder "OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883" then inside it i had the content like "boot.img" & everything. So i zipped it again but without that first folder because I thought it was the problem, but it kept on crashing 0%.
2.5) restarted my PC, looked on several forums, but i couldn't find any fix. Now adb can't even open update.zip anymore, it fails even before 0%.. I tried naming it .zip.zip, keeping the name "OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip", using a third party app to allow more RAM to the cmd app...
I've been trying hard for 4 hours but I still have a O+3 without any OS... My last idea is downloading "OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip" from my PC so it downloads it directly .zip unlike on my mac...
I hope I said everything, sorry for the long post but i'm desperate.. thanks for your attention,
Valentin
Try this guide: https://forum.xda-developers.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757
Let me know if it works.
EDIT: See FAQ #1, 2, 4, 12, 14 and 17.
dbabaev21 said:
Try this guide: https://forum.xda-developers.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757
Let me know if it works.
EDIT: See FAQ #1, 2, 4, 12, 14 and 17.
Click to expand...
Click to collapse
Thank you for answering! unfortunately i've already tried that and my problem occurs when i try to sideload the update from adb recovery... "couldn't load 'update.zip'"
I dont really know what to do now because I think my only option here is to load the OS through adb as I can't boot my phone to get the update zip inside a specified folder to load it from internal storage.
Try to install the new official TWRP version i think it is 3.0.3-0 through fastboot. Boot up TWRP, wipe every partiton and copy the update.zip onto the phone. You can copy it by connecting it normaly via USB(like you would do in OOS) and install the zip file afterwards.
Sleazy_ said:
Thank you for answering! unfortunately i've already tried that and my problem occurs when i try to sideload the update from adb recovery... "couldn't load 'update.zip'"
I dont really know what to do now because I think my only option here is to load the OS through adb as I can't boot my phone to get the update zip inside a specified folder to load it from internal storage.
Click to expand...
Click to collapse
install stock recovery and then try installing official OS. Or install modded twrp 3.0.2-1.28 and then try installing Freedom OS 2.3 via sideload or through internal storage.
Sleazy_ said:
Thank you for answering! unfortunately i've already tried that and my problem occurs when i try to sideload the update from adb recovery... "couldn't load 'update.zip'"
I dont really know what to do now because I think my only option here is to load the OS through adb as I can't boot my phone to get the update zip inside a specified folder to load it from internal storage.
Click to expand...
Click to collapse
Stop fiddling with the ROM. Download the ROM afresh directly to your Windows PC/laptop. Check the md5. Then start experimenting with the other suggestions but don't again meddle with the ROM!
Sleazy_ said:
Thank you for answering! unfortunately i've already tried that and my problem occurs when i try to sideload the update from adb recovery... "couldn't load 'update.zip'"
I dont really know what to do now because I think my only option here is to load the OS through adb as I can't boot my phone to get the update zip inside a specified folder to load it from internal storage.
Click to expand...
Click to collapse
I read your post again and here are a few things:
* Don't update Stock OOS via "System updates" in Settings if you are rooted and have TWRP
* Back up your data before updating, wiping or doing something with your phone.
* For the ADB error, see the FAQ #17 in the guide I provided.
Now, try this:
Flash TWRP via fastboot > boot to TWRP > connect your phone to your PC and copy the full Stock OOS v4.0.2 OTA to your phone > reboot to fastboot and flash Stock Recovery.
It didn't touch the internal storage. So, try to install from internal storage when you are in Stock Recovery.
Let me know if it worked.
Hi everyone, I think I bricked my ZE551ML by being very very dumb, how did I come in such troubles? Well I'll explain you the whole story.
Usually I'm quite good with IT but I'm new to Android and I wanted to install Lineageos because I don't like Asus's ROM, so I searched tutorials and I found the lineage website tutorial at first it didn't seem like a hard task for me, so I started following the tutorial and I got stopped first with trying to get twrp-3.1.1-0-Z00A on the device but didn't seem to work so I tried an older version witch didn't worked too, so I came to xda to get the twrp_z00a_v24_repack and it worked (so well that I erased the system without saving anything just in case but I saved myself by getting the Asus ROM and pushing it to /sdcard/ ) so I attempted to install Lineage (that time with a save) but it gave me the "error executing updater binary in zip" so I searched on the Internet and it seemed that I had to root the phone so I downloaded addonsu-14.1-x86-signed from the Lineageos website and ran it on twrp and it told me that it worked so I wiped the system (I still got the backup) and tried to install Lineage but the same error showed up so I was thinking "Hmm maybe due to TWRP being an old version it might not work if it's not updated" so I rebooted to fastboot and then did fastboot flash recovery twrp-3.1.1-0-Z00A and tried to go in recovery, the phone rebooted, the splashscreen showed and it got to a screen similar to the splashscreen and did nothing (just heard the plug-in device sound in Windows), when I try to shut down and push the power + "+" Button it just starts as normal and the fastboot mode doesn't show.
So that's where I am, if someone could do a dumbproof step by step tutorial on how to unbrick that thing and then install Lineageos that would be so great.
Thank so much to the person (or people) that will help me
PS: I tried to search how to get out of this mess but I didn't understood all of it so I didn't wanted to get in more troubles.
Yuno17 said:
Hi everyone, I think I bricked my ZE551ML by being very very dumb, how did I come in such troubles? Well I'll explain you the whole story.
Usually I'm quite good with IT but I'm new to Android and I wanted to install Lineageos because I don't like Asus's ROM, so I searched tutorials and I found the lineage website tutorial at first it didn't seem like a hard task for me, so I started following the tutorial and I got stopped first with trying to get twrp-3.1.1-0-Z00A on the device but didn't seem to work so I tried an older version witch didn't worked too, so I came to xda to get the twrp_z00a_v24_repack and it worked (so well that I erased the system without saving anything just in case but I saved myself by getting the Asus ROM and pushing it to /sdcard/ ) so I attempted to install Lineage (that time with a save) but it gave me the "error executing updater binary in zip" so I searched on the Internet and it seemed that I had to root the phone so I downloaded addonsu-14.1-x86-signed from the Lineageos website and ran it on twrp and it told me that it worked so I wiped the system (I still got the backup) and tried to install Lineage but the same error showed up so I was thinking "Hmm maybe due to TWRP being an old version it might not work if it's not updated" so I rebooted to fastboot and then did fastboot flash recovery twrp-3.1.1-0-Z00A and tried to go in recovery, the phone rebooted, the splashscreen showed and it got to a screen similar to the splashscreen and did nothing (just heard the plug-in device sound in Windows), when I try to shut down and push the power + "+" Button it just starts as normal and the fastboot mode doesn't show.
So that's where I am, if someone could do a dumbproof step by step tutorial on how to unbrick that thing and then install Lineageos that would be so great.
Thank so much to the person (or people) that will help me
PS: I tried to search how to get out of this mess but I didn't understood all of it so I didn't wanted to get in more troubles.
Click to expand...
Click to collapse
if you are able to access recovery then dd fastboot there. if no recovery, no fastboot, no system there isonly option left. go to below thread and do step by step as suggested.. after you get fastboot mode back, do not use asus flash tool use commands to flash raw firmware see section flash firmware without AFT
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
sukhwant717 said:
if you are able to access recovery then dd fastboot there. if no recovery, no fastboot, no system there isonly option left. go to below thread and do step by step as suggested.. after you get fastboot mode back, do not use asus flash tool use commands to flash raw firmware see section flash firmware without AFT
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Click to expand...
Click to collapse
Hi, thanks for the reply, I don't know if I have to post it here or on the guide but xFSTK-downloader just won't run (Windows 10 1151) and it doesn't show up in task manager (even when the antivirus is disabled).
Have you got an idea on why it doesn't work?
Yuno17 said:
Hi, thanks for the reply, I don't know if I have to post it here or on the guide but xFSTK-downloader just won't run (Windows 10 1151) and it doesn't show up in task manager (even when the antivirus is disabled).
Have you got an idea on why it doesn't work?
Click to expand...
Click to collapse
very first of all uninstall everything especially i soc drivers and xFSTK. then disable driver signature enforcement. and go to thread above posted and do step by step.
how to disable signature enforcement and install driver on win 10 see in thread above
Hello, sorry for the generic title, but i'm quite the noob about android modding and stuff.
Anyway I wanted to root my phone, just to stream some music to my stereo system. How naive I was...
So I unlocked the bootloader, installed twrp with adb and SuperSU with twrp. Everything was fine and phone was rooted but my past naive me thought "well let's try a custom rom, why not". So I went forth and downloaded some stuff from getdroidtips and what I understood is that all I needed to do was to do a wipe, then install the zip file via twrp. I did that and didn't work. After that I realized I made a crucial mistake: I didn't backup my phone from twrp, so I was there with no OS, quite panicked and frustrated. So I tried some other roms, finally I got one that worked, this: https://forum.xda-developers.com/honor-7x/development/openkirin-aosp-8-0-honor-7x-t3746257
It works but it's barebones and on boot it shows a message: "There's an internal problem with your device. Contact your manifacturer for details.". So, I tried recovering from HiSuite, recovery mode etc but nothing worked, I reinstalled SuperSU in the new OS via twrp to see if that would help somehow, but no. in the end I had the even more naive thought that maybe unrooting would allow me to repair via hi suite or something, so I mindlessly selected "complete unroot" on the SuperSU app, and this was the second big mistake, the process somehow ****ed up the twrp install and it no longer works. Instead, if I try to enter twrp with power button + volume up button, it shows the regular "your phone has been unlocked" screen and then comes up for a split second a black screen with, on the bottom half of the screen the "no command" logo, under it some lines of code that I can't read. It suddenly disappears and sometimes enters in a bootloop showing this screen and powering off every time.
If I keep power button pressed bootloop ends and the phone boots "regularly" in the openkirin OS.
I tried reinstalling twrp the same way I did the first time. No error on adb but same no command behaviour
So what I got now is:
kind of bootlooping no command window
openkirin OS with internal problem message
fastboot and rescue mode
it seems to work on adb (everything is fine if I type adb devices)
not working HiSuite recovery
not working Huawei eRecovery
not working download mode (I guess? the power+volume up+volume down combination)
Maybe I should mention I also did a data wipe (?? the option on the right next to "advanced wipe" in the Wipe screen, if I remember correctly) in twrp before installing openkirin, it was suggested on a yt video about how to install openkirin. And that, at a stage I tried using MultiTool but it gives me an error: "exception during a web client request. Error#9", while at the bottom left it says "downloading AdbWinUsbApi.dll..."
Sorry for the general noobishness and the bad english that might be there.
So, any tips for bringing back the phone to normal? Or at least repair twrp??
Please help, I hate needing to throw this phone away just because I wanted to stream some music and because of a couple of stupid errors
Sorry for not answering earlier. It seems, between TWRP and stock recovery, you have messed up I think. When there is no proper recovery it become difficult to bring back the phone. You should try to put it in fastboot mode first, by powering off, pressing the volume lower button and connecting it to computer. Try installing TWRP and flash a custom rom other than openkirin from there if possible. Fastboot is the choice to go if recovery is messed up.
sdivk said:
Sorry for not answering earlier. It seems, between TWRP and stock recovery, you have messed up I think. When there is no proper recovery it become difficult to bring back the phone. You should try to put it in fastboot mode first, by powering off, pressing the volume lower button and connecting it to computer. Try installing TWRP and flash a custom rom other than openkirin from there if possible. Fastboot is the choice to go if recovery is messed up.
Click to expand...
Click to collapse
No worries, I managed to fix it anyway. Some things might be obvious but I'll share what I did nevertheless, in case some other newbie finds himself in a similar situation.
So there was seemingly no way of reinstalling twrp nor the stock recovery. But luck came my way and by almost random clicking I found out that, even if multitool closed as soon as I clicked the ok button in the error message, if I simply ignored the error, the program worked just fine (as I write this I installed another version and it gave no error message). So I played with it a bit and found out that it can flash twrp and it does not need a file from you, it already has a twrp version ready to install. I did that and it worked. It looks like the first twrp file I used didn't work anymore or was someway corrupted by the countless things I tried. So, with twrp working again I was able to backup the sloppy openkiring OS and try the unbrick tool. So I browsed the internet for a guide. Guides always mention as the first step for unbricking using the VENDOR.img file located inside a full stock rom. Problem is, 99% of the times they provide a rom without the needed file. So after some tries I found a good complete stock rom with the VENDOR.img here: drive.google.com/file/d/1tjHefytEWbpuV1f4YjX8AaSMzT6jr8TQ/view but I can't remember which forum/site I found it in.
I followed the guide which involves:
-extracting the UPDATE.APP file contained in the provided zip with huawei extractor tool into an X folder on your pc
-copying the VENDOR.img file contained in the X folder, on the root folder of the sd card
-backing up OS (if there's any) via twrp (I had something like 50 partitions, I guess that was messing things up a bit, but for safety I backed them all up)
-doing an advanced wipe from twrp selecting ALL checkboxes BESIDES the SDcard of course
-flashing the vendor.img file via twrp selecting the "Vendor" partition when prompted
-downloading the update_full_[your model]_hw_[your region].zip file, in my case update_full_BND-L21C_hw_eu.zip
-extracting the UPDATE.APP file contained in update_full_BND-L21C_hw_eu.zip with Huawei extractor tool in some other folder Y
-looking for a file named cust.img/CUST.img/version.img/other_name.img (I don't know which other names it can have, I was lucky and had a VERSION.img file in it)
-rename the cust.img/CUST.img/version.img/other_name.img to CUST.img and copy it from the Y folder to the X folder
-boot your phone into fastboot mode
-connect phone to multitool via usb and select the "unbrick" tab
-there, Multitool asks for a folder, give it the X folder. There are some checkmarks on the Multitool "unbrick" page. 4/5 of them should become checked after the folder input. In my case the first 4
-then, simply press the unbrick button
-wait and pray (it can look like it freezes while it's copying the system.img file but wait, it'll be fine)
So I did that and it worked flawlessly, the phone booted slowly but surely into EMUI 5.1 with Android 7.0 I think and everything was fine.
At that point I had a working OS and a working twrp but wanted to go back to the OS I was used to, Android 8.something so, I tried connecting the thing to HiSuite and it automatically asked if I wanted to update, not to 8.something but to 9.1. I thought "SURE I DO!" and updated flawlessly (I thought 9.1 hadn't even been released here in Italy).
When it booted I found out the new OS was working like an antivirusless xp pc: it didn't recognise the SIM, it would crash every 20 seconds, app downloads got stuck at 99%, if it felt like it, it rebooted, pc connection was not stable. Besides, the update being "official" and installed from "trusted" sources (HiSuite), it completely wiped twrp.
And that was the "OH ****, here we go again" moment: no twrp and worse-than-ever-working OS.
So because of the new EMUI version, I guess, Multitool kept recognizing the phone but stopped offering its own recovery, eRecovery, twrp files available for flashing. I was completely frustrated with all of this and decided to give up, but I made the last effort: I tried the relock function in multitool. So I provided the key, pressed relock, waited, prayed, and finally cheered. It worked like a charm. Phone runs now on EMUI 9.1 with locked bootloader without problems. Finally
So I guess in the end I payed 4 euros for a nice update, a painful and frustrating trip into android modding and a lesson : never do android modding!
no, just kidding, don't do it just if you are a newbie AND you don't want to risk to throw the phone in the grabage.
In all other cases consider it carefully
Oh, and also, God bless the MT Team and Russia altogether!! thanks
Quite an experience. All the best. ?
Lol sounds fun. I've bricked my Huawei Mate SE/Honor 7x more times than I can count. I'm just awaiting my 9.1. I want my GPU Turbo! Is it as good as it's supposed to be?