Made an stupid error when flashing my phone - help needed eventually - One (M9) Q&A, Help & Troubleshooting

Hi,
have to say it was my first try ever to flash a phone.
I've followed the ReadMe-Thread to the letter and with a little bit of try&error I got it done smoothely until I came to flashing the CustomRom "lineage-18.1-20210311-UNOFFICIAL-hima".
The instruction is " Choose "Wipe" and wipe everything except for "Micro SDcard", "USB-OTG" and "SD-Ext" via the advanced wipe. ".
What I did was exactly the opposite. I did mark "Micro SDcard", "USB-OTG" and "SD-Ext" and wiped it. There was an error message but as I was shocked about my mistake I can not remember any detail.
I've done it the right way after this error without booting the device and as far as I see it the flash was successful. The phone now starts Lineage and seems to work. Not sure yet as I have not got a new prepaid SIM but it's underway already. But the "rest" of it works. Have installed some apps with adb already.
BUT: It seems as I have destroyed the recovery mode at least. When I try to boot into recovery I only get a normal boot into LineageOS. Means that I start to bootloader mode and then select "Boot to recovery" the screen becomes black and then after some time the LineageOS starts. I can also switch between download ans bootloader mode but can not reach recovery.
AND the htc_fastboot command does not have any effect, will say NO devices are visible.
May someone in the know please enlighten me what I've done and how I may eventually recover the recovery mode?
Thank you very much for reading this and if I've written absolute nonsense here please bear with me, I'm German.

I guess you can flash custom recovery again using fastboot and reinstall Lineage!

Thanks.
When I try to use htc_fastboot there is no reaction and "htc_fastboot devices" shows nothing.

Same problem with me. to negligence, i didn't do this " "Wipe" and wipe everything except for "Micro SDcard", "USB-OTG" and "SD-Ext" via the advanced wipe" and installed the lineage 18.1. and now I don't have Recovery and the phone boot to lineage os but it will not boot totally. it will shut down and then boot again. (loop)
please help me.
I can boot to download mode
unlocked
s-on
Os-4.28.401.3
any help is much appreciated. thank you in advance

Hello,
I have a similar problem. It is an m9 with an unblocked bootloader. I got it from a colleague.
It had a cyanogen mod and TWRP on it. I set the cyandogen mod to factory settings and then activated the developer options so that I can boot directly into the recovery from the operating system.
It also worked perfectly. Then I wanted to update TWRP with the TWRP app.
It worked until I was asked whether I wanted to flash TWRP into the recovery or into the boot.
I chose recovery and thus rendered the phone unusable. It only boots into the bootloader or into download mode.
My attempts to flash a stockrom via adb or an executable file on a windows pc failed.
With the latter, the smartphone at least responds via the usb port. But so far I have not found the right RUU file for the phone.
Unfortunately, it also does not respond to 0PJAIMG.zip files on an sdcard formatted with FAT32.
Is there a way to force-flash TWRP onto the phone?
Many greetings
Draal

Related

phone bricked? stuck at "this build is for.." screen

hi guys,
today i made a huge mistake. i was trying to deinstall the cm9 by just wiping my phone. accidentaly i made a "system wipe" with my recovery. now my phone ist stuck in the "this build is for development purposes only" screen. i tried to reboot into recovery via the aio kit - error: device not found. (led not flashing, not even when i connect it to the "normal" loading adapter). i just read another thread which ended in sending the device back to htc. i wonder if there is any possibility to safe my phone from that.
greetz bow111
Are you able to acces the Bootloader by closing the phone and restart it by keeping pressed at same time VOLUME DOWN + POWER ?
Be careful: Do NOT press volume UP!, Do not hold Volume Down for too long!
Once you are in the bootloader you should be able to:
A:Go into recovery and repair it from there in you have the ROM on your SD card.
B:If you are unable to acces recovery mode from bootloader, try to use the All In One Tool and flash the TWRP Recovery (the one in the right part of the window) also, note that there are too version, CDMA and GSM, if you have a sim card flash GSM, if you do not have a simcard use CDMA.
Let me know how it went
rzarectha said:
Are you able to acces the Bootloader by closing the phone and restart it by keeping pressed at same time VOLUME DOWN + POWER ?
Be careful: Do NOT press volume UP!, Do not hold Volume Down for too long!
Once you are in the bootloader you should be able to:
A:Go into recovery and repair it from there in you have the ROM on your SD card.
B:If you are unable to acces recovery mode from bootloader, try to use the All In One Tool and flash the TWRP Recovery (the one in the right part of the window) also, note that there are too version, CDMA and GSM, if you have a sim card flash GSM, if you do not have a simcard use CDMA.
Let me know how it went
Click to expand...
Click to collapse
ok. my phone just quick restarted. it directly went back to the "htc quietly brilliant" screen. pressing volume down + power button for a few seconds doesnt work to get into bootloader. i tried it serveral times. im not even able to turn the phone off. holding the power button only wont help at all.
thanks for ur help.
edit: i feel.. pranked now it worked and i went from bootloader to recovery (twrp already installed). can u tell me what to do now? thanks a lot already
Hm,
Well since you cant remove the battery on this phone, id suggest to just let it finish with what it has left off of the battery. once it is closed try to recharge it and then try to boot in recovery, ofc you might not be able to do this today, depends how much battery you had left when the problem started, but it's a chance, also if it's rooted you bootloader will be unlocked so i doubt HTC will grant you warranty for it (not 100% about this though). let us know if you manage to do any progress with it after you manage to make it close.
cheers
rzarectha said:
Hm,
Well since you cant remove the battery on this phone, id suggest to just let it finish with what it has left off of the battery. once it is closed try to recharge it and then try to boot in recovery, ofc you might not be able to do this today, depends how much battery you had left when the problem started, but it's a chance, also if it's rooted you bootloader will be unlocked so i doubt HTC will grant you warranty for it (not 100% about this though). let us know if you manage to do any progress with it after you manage to make it close.
cheers
Click to expand...
Click to collapse
i just edited my post. managed to get into recovery (twrp). what do i have to do now?
Download a new rom and transfer it to your sd card, then flash it from your recovery.
If u have the ROM in the SD card just flash it and reboot other wise as he mentioned above
Sent from my One V using xda premium
Ok, last night i went to sleep.
You now need to find a way to put a ROM on your SD card. whatever ROM you choose make sure you have the correct kernel for it (in every post for ROMs you will find a download link to the correct kernel aswell).
So what you do now (after you have the ROM .zip file on your SD card and your Kernel file in your PC) is:
-Put your phone into Bootloader, Select fast boot and connect the USB cable, and make sure it tells on your phone "FASTBOOT USB"
-Then in All in One select "Flash Kernel" and browse to the correct Kernel, and flash it.
-Reboot your phone in Recovery mode, you have the option in the fastboot screen.
-In the Recovery menu select Factory Reset -> Wipe System.
-While still in recovery go to "Install update from SD card" (or something similar) and choose the ROM .zip file, wait for it to be flashed
-reboot your phone (1st boot is always a bit slower, could take up to 5 minutes).
-after you get to your main screen, reboot the phone again and flash a Google Apps (gapps) .zip file. You will find the correct version from your ROM in the official thread of the ROM. You DO NOT run a factory reset, wipe system or anything like that for flashing Gapps.
Good luck.
got my phone working again. additionally i tried to "re-stock" my phone via a ruu.exe. now i have a new problem ( -.- ;D). my phone wont connect to wlan. it always hangs on "authenticating with wifi (dont know if translated it the right way)". some has an idea how to solve that problem?
p.s. sry for answering this late. had to do a lot of stuff for my finals :/
edit: was a problem with my router
flash a proper kernel
Sent from my One V

[SOLVED] Error Mounting /sdcard/.android_Secure!

People,
I got to install the Cyanogen Firmware on my Xperia ZL (6503) and i'm give a problem.
I follow the instructions on the http://wiki.cyanogenmod.org/w/Install_CM_for_odin
and download the file cm-10.1.2-odin.zip in this page:
http://download.cyanogenmod.org/?type=stable&device=odin
When I select the option Factory Default, the CWM show the message: Error Mounting /sdcard/.android_Secure! and no mount the internal sdcard. I'm install the .zip file from the external sdcard, and stuck on logo of Cyanogen.
Any fix for this error?
Do you mean you are unable to perform a factory reset? You can do this without using CWM. Inside of the phone settings, backup & restore, there is an option to reset to factory.
If you mean you are unable to install the zip, then maybe you need to install a different version of recovery.
ryude said:
Do you mean you are unable to perform a factory reset? You can do this without using CWM. Inside of the phone settings, backup & restore, there is an option to reset to factory.
If you mean you are unable to install the zip, then maybe you need to install a different version of recovery.
Click to expand...
Click to collapse
Humm, i'm not do factory reset before install the Cyanogenmod. I'm install the boot.img with CWM provided with cyanognen file. What's the difference do factory reset directly in original rom?
hudfer said:
Humm, i'm not do factory reset before install the Cyanogenmod. I'm install the boot.img with CWM provided with cyanognen file. What's the difference do factory reset directly in original rom?
Click to expand...
Click to collapse
Ah you're attempting to flash the boot.img file? You have to use fastboot I believe in order to flash it.
1. You must have unlocked bootloader of your device. You can do so from here.
2. Download Fastboot here.
3. Place Fastboot.zip and the boot.img files onto your Desktop.
2. Extract files from the Fastboot archive to your Desktop. Move the boot.img file into the Fastboot folder.
3. Turn ON the USB debugging option on your device by going to Menu>>Settings>>Developer options>>USB debugging.
4. Once enabled, connect your device to your PC via USB cable.
5. Launch a Command Prompt Window on the Desktop of your PC. To do so, press and hold the Shift button on your keyboard and right-click on any blank area on the screen, then choose Open command window here.
6. Type in following command into the Command Prompt Window:
adb reboot bootloader
7. Your device will reboot into the bootloader mode.
8. Once inside bootloader mode, enter the following command into Command Prompt.
fastboot flash boot boot.img
9. Once the file’s flashed, reboot your device.
10. And you’re all set! You now have CWM recovery!
ryude said:
Ah you're attempting to flash the boot.img file? You have to use fastboot I believe in order to flash it.
1. You must have unlocked bootloader of your device. You can do so from here.
2. Download Fastboot here.
3. Place Fastboot.zip and the boot.img files onto your Desktop.
2. Extract files from the Fastboot archive to your Desktop. Move the boot.img file into the Fastboot folder.
3. Turn ON the USB debugging option on your device by going to Menu>>Settings>>Developer options>>USB debugging.
4. Once enabled, connect your device to your PC via USB cable.
5. Launch a Command Prompt Window on the Desktop of your PC. To do so, press and hold the Shift button on your keyboard and right-click on any blank area on the screen, then choose Open command window here.
6. Type in following command into the Command Prompt Window:
adb reboot bootloader
7. Your device will reboot into the bootloader mode.
8. Once inside bootloader mode, enter the following command into Command Prompt.
fastboot flash boot boot.img
9. Once the file’s flashed, reboot your device.
10. And you’re all set! You now have CWM recovery!
Click to expand...
Click to collapse
Thank's for the explanation, but i'm have executed all the commands described by you and not work. Is the same commands on cyanogen wiki page. The CWM appears the same error and i'm install the cyanogen, but stucks in logo and the android is not start.
hudfer said:
Thank's for the explanation, but i'm have executed all the commands described by you and not work. Is the same commands on cyanogen wiki page. The CWM appears the same error and i'm install the cyanogen, but stucks in logo and the android is not start.
Click to expand...
Click to collapse
You should flash a stock FTF image using Flashtool. After you have completed this, you can try again.
ryude said:
You should flash a stock FTF image using Flashtool. After you have completed this, you can try again.
Click to expand...
Click to collapse
After hours of research, I resolved the problem. I`m followed the steps described on cyanogen wiki, adding the first step Factory Restore on original sony firmware and the problem persists. After launched the CWM, I select the option "Format /data" and after "Format /sdcard". After selected this options, the error message not appears again and the Cyanogen firmware install and launch successful! Probably with format, deleted some key or protection in internal sdcard. Thanks for the help!
hudfer said:
After hours of research, I resolved the problem. I`m followed the steps described on cyanogen wiki, adding the first step Factory Restore on original sony firmware and the problem persists. After launched the CWM, I select the option "Format /data" and after "Format /sdcard". After selected this options, the error message not appears again and the Cyanogen firmware install and launch successful! Probably with format, deleted some key or protection in internal sdcard. Thanks for the help!
Click to expand...
Click to collapse
I'm happy you were able to resolve your problem. How are you liking CyanogenMod so far?
ryude said:
I'm happy you were able to resolve your problem. How are you liking CyanogenMod so far?
Click to expand...
Click to collapse
The Cyanogen is always incredible, i'm use this custom rom since my Galaxy S2. The rom is very fast and clean. I most like in this version, the option "Expand Desktop", in particular opinion, the best configuration on the rom.
hudfer said:
The Cyanogen is always incredible, i'm use this custom rom since my Galaxy S2. The rom is very fast and clean. I most like in this version, the option "Expand Desktop", in particular opinion, the best configuration on the rom.
Click to expand...
Click to collapse
I'm have a first problem with full screen mode: the game "Kingdom Rush" not launch.
does not work for me
hudfer said:
After hours of research, I resolved the problem. I`m followed the steps described on cyanogen wiki, adding the first step Factory Restore on original sony firmware and the problem persists. After launched the CWM, I select the option "Format /data" and after "Format /sdcard". After selected this options, the error message not appears again and the Cyanogen firmware install and launch successful! Probably with format, deleted some key or protection in internal sdcard. Thanks for the help!
Click to expand...
Click to collapse
Hi,
I have the same issue, but after trying: "Format /sdcard" I get "Error formatting /sdcard!"
Please help! I'm researching 2 days in a row and can't find a solution.
flutur said:
Hi,
I have the same issue, but after trying: "Format /sdcard" I get "Error formatting /sdcard!"
Please help! I'm researching 2 days in a row and can't find a solution.
Click to expand...
Click to collapse
you just format your sdcard as FAT32, that's how i solved my problem
Same problem in Razr 925
ShanksVo said:
you just format your sdcard as FAT32, that's how i solved my problem
Click to expand...
Click to collapse
I have the same problem in my Razr 925. I installed with CWM 6.0.3.6-10.2 cm from the external SD.
1) First I tried from the inside SD, I never realized that appeared "Warning: No file_contexts", and install the zip of cm-10.2, the result was "Error mounting / data" "Error mounting / sdcard /. Android_secure".
2) From the external memory I managed to do it, but the logo remains Cyanogen cycling.
3) I tried to restore the backup, but "Can not mount / sdcard".
Now I don't know what to do, I researched and solution is always restart from the official android, in my case I can not start the official android. I need help please !:crying:
If you don't want to format your SD-card
flutur said:
Hi,
I have the same issue, but after trying: "Format /sdcard" I get "Error formatting /sdcard!"
Please help! I'm researching 2 days in a row and can't find a solution.
Click to expand...
Click to collapse
If you aren't able to (as in your case) or simply don't want to (as in mine, where I didn't have an external SD card handy); you can simply upgrade your recovery software.
In my case, Carbon ROM JB for the GT-N7000 came with CWM 6.0.3.5 which couldn't flash newer ROMs (like Carbon KitKat), and had issues with the internal SD card including the one in the topic of this post. Since I had just wiped my current ROM and didn't want to start up an ADB sideload session, I simply flashed PA (which came with CWM 6.0.3.7, a minor version bump but a huge difference here) and after rebooting to recovery again (I didn't even have to boot to PA), everything worked again.
(My first post that could be even considered remotely useful on XDA, so please tell me if it helped you!)
Thanks!
hudfer said:
After hours of research, I resolved the problem. I`m followed the steps described on cyanogen wiki, adding the first step Factory Restore on original sony firmware and the problem persists. After launched the CWM, I select the option "Format /data" and after "Format /sdcard". After selected this options, the error message not appears again and the Cyanogen firmware install and launch successful! Probably with format, deleted some key or protection in internal sdcard. Thanks for the help!
Click to expand...
Click to collapse
Finally!
PS: Do -not- try to encrypt your nexus 4 if you put 5.0 on it X(

[Q] iOS System Wipe

Hey XDA Members
I know there has already been similar posts to mine on XDA as I've worn out the search button on google trying to find a solution to my problem, with no avail. So I thought I would leave a description of my own situation and see if a more tech-savvy individual could kindly help me out...
So yesterday I decided it would be a good idea to unlock my bootloader & root my device simply because I wanted to remove all the bloatware which HTC 'generously' crammed into the One X. Unlocking the bootloader was simple enough following the instructions provided. However, rooting my handset was not so effortless. The root was ineffective & I got stuck with yet another unwanted app called SuperSU! (An error message regarding missing binary codes appeared every time I tried to open the application) I tried uninstalling via both settings & google play before finally factory resetting my phone. None of these methods worked
At this point it suddenly dawned on me someone so unenlightened in the art of software development or anything android related shouldn't being toying with stuff he can't afford to break! But I figured it was too late to turn back now and continued in my moment of intellectual darkness...
In my bewildered state I accidentally 'wiped system' using CWM and now I have no iOS. My HTC will only boot until the 'quietly brilliant' slogan appear's & no further. When I connect my phone to my computer via USB I can not access the removable storage device, a removable disk appears but when clicked I am prompted to 'insert removable disk'. I am lead to believe from reading related threads that if I had access to my phones storage then installing a new iOS would be relatively straight forward. Also trying to mount in CWM just retrieves an error message reading 'CWM unable to open ums lunfile (no such directory exists)'. Where do I go from here?
Any help would be much appreciated :fingers-crossed:
Flash a newer recovery, try the latest Philz touch recovery then you should be able to mount sdcard and flash a rom
Hope it helps
if tthe above suggestion doesnt work, try this
http://www.hackmyandroid.com/comprehensive-guide-on-unbricking-the-htc-one-x/4216
I recommend you flash the latest TWRP recovery since it gives you access to the phones sdcard, if your staying stock/near stock OS you can check http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html download the Download stock odexed 4.18.401.3, and just flash it in recovery or you can download w.e custom OS you like and flash it the same
Hope it helps
Thank you both for your replies :good:
m.jordan, I tried to flash TWRP onto my device (3 different versions in fact) but once entering recovery mode I was prompted to 'swipe screen to unlock' which wasn't possible because I can only use the volume controls and the power button. After that I downloaded the latest version of CWM which enables me to both use the control buttons & touch screen. I downloaded the 'stock odexed 4.18.401.3' although I have no way of flashing on my device...
I tried the method in the link you kindly provided and followed each instruction carefully. After re-unlocking my bootloader (does it matter whether the device is locked or unlocked when mounting USB storage in recovery mode?) & flashing CWM I downloaded the odexed 4.18.401.3 extracted boot.img & flashed that too. On the website you shared it then prompted me to 'mount usb storage' & my device should now be showing as 'clockworkmod' so I would be able to place the odexed 4.18.401.3.zip into the folder and then flash my handset. Unfortunately I still have no removable disks showing on my PC
My HTC One X does not have removable storage (I suppose you already knew that) & I havn't been able to get my PC to read a removable disk since the day I wiped the system.
If only I could get my computer to show an 'adb device' I'm sure this would be so much easier! I don't suppose you would know anything about that? when I use cmd prompt 'adb device' most of the time it just returns:
adb out of date. killing...
daemon started sucessfully
list of attached devices
Nothing ever shows under attached devices
Nogotaclue, my next step it to try Philz recovery & see where that takes me, i'll let you know how that goes (Although I fear it will just have the same outcome as the rest & not be able to read an sdcard)
Thanks again
well it seems if you could follow the steps on that link, then your pc is recognizing the device so there is hope. If TWRP isnt working then cool. On either the CWM or Philz there is an option called adb sideload rom, if you can't access your SD card you can always sideload and install the rom using either One_X_All-In-One_Kit or WinDroid Universal HTC Toolkit v1.1, made them available here https://www.dropbox.com/sh/fv9fun4x2c4dk2l/AABhNHvlpPUvDXUWYK5PJNhpa?dl=0
Once in recovery I believe its under the install option, you have the option to install rom from sdcard and sideload rom, just select sideload. once thats done, open either the all in one or windroid with your device connected to your pc (i recommend the all in one), select the option to sideload, and cross your fingers that it works
ProdiJay said:
Thank you both for your replies :good:
m.jordan, I tried to flash TWRP onto my device (3 different versions in fact) but once entering recovery mode I was prompted to 'swipe screen to unlock' which wasn't possible because I can only use the volume controls and the power button. After that I downloaded the latest version of CWM which enables me to both use the control buttons & touch screen. I downloaded the 'stock odexed 4.18.401.3' although I have no way of flashing on my device...
I tried the method in the link you kindly provided and followed each instruction carefully. After re-unlocking my bootloader (does it matter whether the device is locked or unlocked when mounting USB storage in recovery mode?) & flashing CWM I downloaded the odexed 4.18.401.3 extracted boot.img & flashed that too. On the website you shared it then prompted me to 'mount usb storage' & my device should now be showing as 'clockworkmod' so I would be able to place the odexed 4.18.401.3.zip into the folder and then flash my handset. Unfortunately I still have no removable disks showing on my PC
My HTC One X does not have removable storage (I suppose you already knew that) & I havn't been able to get my PC to read a removable disk since the day I wiped the system.
If only I could get my computer to show an 'adb device' I'm sure this would be so much easier! I don't suppose you would know anything about that? when I use cmd prompt 'adb device' most of the time it just returns:
adb out of date. killing...
daemon started sucessfully
list of attached devices
Nothing ever shows under attached devices
Nogotaclue, my next step it to try Philz recovery & see where that takes me, i'll let you know how that goes (Although I fear it will just have the same outcome as the rest & not be able to read an sdcard)
Thanks again
Click to expand...
Click to collapse
Man flash Philz 5.15.9 mount your sd card and you are ready to go only in this version sd card mount work no TWRP no CWM exactly Philz 5.15.9

My Honor 7x BND-L21 is quite broken, need help

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?

Pixel Experience boot loop + string of stupid decisions: is there any way out?

Hi there,
I think I (soft? hard?) bricked my whyred today after trying to install Pixel Experience (Android 10). At this time, I'm left with a flashed PE Plus that is stuck at the Google logo animation (e.g. unable to access USB debug settings); stock MIUI recovery; and fastboot, which is not recognized by ADB as I haven't had a successful boot since I flashed PE, so I can't turn USB debug on. I think I've exhausted my options, but maybe someone has a smart solution.
For those who think they can help, let me describe in detail what I did:
0) I became a dev, turned USB debug on, installed Minimal ADB and Fastboot, latest Xiaomi drivers, moved flashable zips into internal storage etc.
1) I unlocked my bootloader through Mi Unlock.
2) I successfully flashed TWRP-3.3.1.0-whyred via ADB/Fastboot and rebooted. After getting back into MIUI, I booted into recovery, which was back to stock (MIUI seems to have overwritten my recovery). At that point (probably a big mistake) I gave up on flashing TWRP and went ahead to boot right into it via ADB instead, without flashing.
3) After a successful boot into TWRP 3.3.1.0, it asked me for a decryption password. Nothing worked, so I kept googling and found out that my version of android needs TWRP 3.3.1.1, which was not on the official TWRP website yet, to decrypt automatically. I booted into TWRP 3.3.1.1 via ADB (but didn't flash), made a backup of my stock ROM, did a wipe (art/dalvik cache, cache, data, system, vendor), flashed Pixel Experience and rebooted.
4) Bootloop, I was stuck on the Google loading animation for over 20 minutes, nothing happened.
5) I panicked.
6) I tried to flash TWRP 3.3.1.1 via ABD but my PC didn't recognize my phone - probably because, for lack of successful boots, I have not managed to turn on USB debug.
7) I tried to connect to Mi Assistant through stock recovery. It didn't recognize my phone, probably for the above reason.
8) I did a data wipe through stock recovery and rebooted, hoping for whatever issue kept PE from booting normally to get resolved.
9) I'm stuck on the same Google loading animation for over 40 minutes now, no progress.
Does any of you guys see a way out, or is this story over? To recap, I have: 1) PE Plus in bootloop, no access to dev settings, 2) stock MIUI recovery with options to reboot, wipe data or connect to Mi Assistant, 3) stock fastboot, 4) a backup of my previous system on internal storage, 5) ADB on my computer that doesn't recognize my phone - no USB debugging. I don't know where to turn. I don't care much about data, I have everything in the cloud, but I'd like to save the phone if possible.
Thanks a lot.
Edit: Problem resolved - even though the connected device didn't show up in ADB on PC (adb devices came back empty), the phone was still responsive to fastboot reboot and fastboot flash recovery via PC, so I could flash TWRP 3.3.1.1 & clean flash PE. For anyone struggling with PE bootloops: make sure to 1) use TWRP 3.3.1.1 to flash, 2) do a dalvik/cache wipe after flashing the ROM and 3) not to install the TWRP app before the first successful boot - it was neglecting either 2) or 3) that caused my bootloop. The ROM itself is amazing!
mkohan said:
Hi there,
I think I (soft? hard?) bricked my whyred today after trying to install Pixel Experience (Android 10). At this time, I'm left with a flashed PE Plus that is stuck at the Google logo animation (e.g. unable to access USB debug settings); stock MIUI recovery; and fastboot, which is not recognized by ADB as I haven't had a successful boot since I flashed PE, so I can't turn USB debug on. I think I've exhausted my options, but maybe someone has a smart solution.
For those who think they can help, let me describe in detail what I did:
0) I became a dev, turned USB debug on, installed Minimal ADB and Fastboot, latest Xiaomi drivers, moved flashable zips into internal storage etc.
1) I unlocked my bootloader through Mi Unlock.
2) I successfully flashed TWRP-3.3.1.0-whyred via ADB/Fastboot and rebooted. After getting back into MIUI, I booted into recovery, which was back to stock (MIUI seems to have overwritten my recovery). At that point (probably a big mistake) I gave up on flashing TWRP and went ahead to boot right into it via ADB instead, without flashing.
3) After a successful boot into TWRP 3.3.1.0, it asked me for a decryption password. Nothing worked, so I kept googling and found out that my version of android needs TWRP 3.3.1.1, which was not on the official TWRP website yet, to decrypt automatically. I booted into TWRP 3.3.1.1 via ADB (but didn't flash), made a backup of my stock ROM, did a wipe (art/dalvik cache, cache, data, system, vendor), flashed Pixel Experience and rebooted.
4) Bootloop, I was stuck on the Google loading animation for over 20 minutes, nothing happened.
5) I panicked.
6) I tried to flash TWRP 3.3.1.1 via ABD but my PC didn't recognize my phone - probably because, for lack of successful boots, I have not managed to turn on USB debug.
7) I tried to connect to Mi Assistant through stock recovery. It didn't recognize my phone, probably for the above reason.
8) I did a data wipe through stock recovery and rebooted, hoping for whatever issue kept PE from booting normally to get resolved.
9) I'm stuck on the same Google loading animation for over 40 minutes now, no progress.
Does any of you guys see a way out, or is this story over? To recap, I have: 1) PE Plus in bootloop, no access to dev settings, 2) stock MIUI recovery with options to reboot, wipe data or connect to Mi Assistant, 3) stock fastboot, 4) a backup of my previous system on internal storage, 5) ADB on my computer that doesn't recognize my phone - no USB debugging. I don't know where to turn. I don't care much about data, I have everything in the cloud, but I'd like to save the phone if possible.
Thanks a lot.
Click to expand...
Click to collapse
I'm new to this phone as well (but not to Android). Try the following:
Download TWRP from here -> https://androidfilehost.com/?fid=6006931924117884758
Download Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip from here -> https://zackptg5.com/downloads/Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip
Power off phone. Hold down volume down and power button to boot into fastboot
Give the command fastboot flash recovery twrp-3.3.1-1-whyred.img to flash the recovery you downloaded earlier.
Boot into recovery
Flash Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip that you downloaded earlier
The above steps will at least ensure that you retain TWRP and it doesn't get overwritten by stock MIUI recovery
After that, check whether or not your phone/ROM has anti-rollback enabled and take appropriate steps accordingly.
Ok so i flashed PE 10 plus today and was met with the same problem.
Heres how i solved it
Goto fastboot option by pressing volume down and power button
Connect to pc (If it doesnt recognize, reinstall Adb drivers and phone drivers)
If it asks for decryption password just press cancel
Wipe data/internal/vendor (wont be able to wipe dalvik as it wont mount)
Flash PE 10 Plus and nothing else.
It should boot just fine.
However i run into bootloop if i flash latest magisk so i cant root my phone :/
Hope this helps
mkohan said:
Edit: Problem resolved - even though the connected device didn't show up in ADB on PC (adb devices came back empty), the phone was still responsive to fastboot reboot and fastboot flash recovery via PC, so I could flash TWRP 3.3.1.1 & clean flash PE. For anyone struggling with PE bootloops: make sure to 1) use TWRP 3.3.1.1 to flash, 2) do a dalvik/cache wipe after flashing the ROM and 3) not to install the TWRP app before the first successful boot - it was neglecting either 2) or 3) that caused my bootloop. The ROM itself is amazing!
Click to expand...
Click to collapse
hey read your post
actually adb and fastboot are two different things.
and recovery is flashed using fastboot commands not adb.
sometimes if a rom is not booting it may have issues with encryption.

Categories

Resources