Develop Bugs

[Q] Repair platform.xml?

Hi folks,
I tried to modify the platform.xml file to enable some write permissions. As far as I can tell, the app I used to modify the file didn't write it back correctly, and now my device is what might be called "semi-bricked."
Almost everything force closes, WiFi and write permissions seem to be broken, and I can't seem to get my Galaxy Nexus to communicate with my PC via USB.
I tried booting into CWM and mounting some /system, but I'm not sure how to access it since fastboot/adb don't seem to recognize the device.
I've also booted into some sort of recovery (fastboot?) that looks like the attached image. But I can't get it to do anything except boot up into the normal OS when I click the power button.
Any suggestions on how I can get access back to my device so I can repair/replace the platform.xml file and restore functionality to my phone?
Thank you very much!

Deozaan said:
Hi folks,
I tried to modify the platform.xml file to enable some write permissions. As far as I can tell, the app I used to modify the file didn't write it back correctly, and now my device is what might be called "semi-bricked."
Almost everything force closes, WiFi and write permissions seem to be broken, and I can't seem to get my Galaxy Nexus to communicate with my PC via USB.
I tried booting into CWM and mounting some /system, but I'm not sure how to access it since fastboot/adb don't seem to recognize the device.
I've also booted into some sort of recovery (fastboot?) that looks like the attached image. But I can't get it to do anything except boot up into the normal OS when I click the power button.
Click to expand...
Click to collapse
No it is not bootloader. to access to the bootloader turn on your device long pressing power, volume up and volume down buttons together (don't use odin).
To access to cwm recovery from bootloader just press volume down button until you see "recovery" option, then press power button and it will boot in recovery.
which rom are you using?
solution: download the zip file of your rom and extract the file you modified, make a zip (if you can't make a flashable zip i'll post an attachment for you) and flash it in recovery

enryea123 said:
No it is not bootloader. to access to the bootloader turn on your device long pressing power, volume up and volume down buttons together (don't use odin).
To access to cwm recovery from bootloader just press volume down button until you see "recovery" option, then press power button and it will boot in recovery.
which rom are you using?
solution: download the zip file of your rom and extract the file you modified, make a zip (if you can't make a flashable zip i'll post an attachment for you) and flash it in recovery
Click to expand...
Click to collapse
Thanks for the reply.
I actually did manage to get my PC to recognize the device via USB/adb and I copied the file back to the way it should have been. But that didn't fix anything, so I ended up doing a wipe/factory reset. Everything works now but things still seem a bit. . . off. For instance, it takes a while after my phone boots up before the WiFi will actually connect. It used to be connected almost immediately. And it takes a while for the alarm icon to load/show up in the notification area at the top. And I can't find the option in the settings anymore to use USB debugging. There are lots of little things like that, where it works, but it just doesn't quite work like it used to. . .
And to answer your question, I'm using the stock ROM that came with the Galaxy Nexus (from Google Play Store).

Deozaan said:
Thanks for the reply.
I actually did manage to get my PC to recognize the device via USB/adb and I copied the file back to the way it should have been. But that didn't fix anything, so I ended up doing a wipe/factory reset. Everything works now but things still seem a bit. . . off. For instance, it takes a while after my phone boots up before the WiFi will actually connect. It used to be connected almost immediately. And it takes a while for the alarm icon to load/show up in the notification area at the top. And I can't find the option in the settings anymore to use USB debugging. There are lots of little things like that, where it works, but it just doesn't quite work like it used to. . .
And to answer your question, I'm using the stock ROM that came with the Galaxy Nexus (from Google Play Store).
Click to expand...
Click to collapse
first: to make the "developer settings" appear go settings/About phone and tap on build number 7 times (google has hidden it in 4.2).
said that, you can:
1) fix permissions in cwm recovery (under advanced menu)
2) download a zip of your rom and flash it in recovery
3) if your bootloader is unlocked (you see a padlock when you boot your phone) you can flash a factory image to return completely stock.
4) if your bootloader is locked you can follow the 3) method but you will lose all your sdcard data.

enryea123 said:
first: to make the "developer settings" appear go settings/About phone and tap on build number 7 times (google has hidden it in 4.2).
said that, you can:
1) fix permissions in cwm recovery (under advanced menu)
2) download a zip of your rom and flash it in recovery
3) if your bootloader is unlocked (you see a padlock when you boot your phone) you can flash a factory image to return completely stock.
4) if your bootloader is locked you can follow the 3) method but you will lose all your sdcard data.
Click to expand...
Click to collapse
Thanks again for the response.
I got developer settings to appear. Hooray! Fix Permissions is one of the first things I did to try to repair the platform.xml file when things were broken. I ran it again (but from ROM Manager rather than from CWM Recovery) and it didn't seem to have any effect on the weird sluggishness when first booting up.
My bootloader is unlocked. Will I have to root again if I flash one of those factory images? I'm currently backing up the contents of my "SD card" in case I have to completely wipe the entire thing.

Deozaan said:
Thanks again for the response.
I got developer settings to appear. Hooray! Fix Permissions is one of the first things I did to try to repair the platform.xml file when things were broken. I ran it again (but from ROM Manager rather than from CWM Recovery) and it didn't seem to have any effect on the weird sluggishness when first booting up.
My bootloader is unlocked. Will I have to root again if I flash one of those factory images? I'm currently backing up the contents of my "SD card" in case I have to completely wipe the entire thing.
Click to expand...
Click to collapse
well, you can firstly try to flash a zip of your rom (search on xda or google), it should fix.
the fastboot flash method is the google method so you won't need root (you just have to go into fastboot and connect your phone to your computer, doesn't matter if you have root, or a different rom/kernel/recovery).
If you don't know you to flash from fastboot try first to flash the rom zip.
having a backup of the sdcard is always a good idea :good:, i have 2 backups of mysdcard on 2 different hard drives of my computer and the pictures i take with the camera are automatically uploaded on my dropbox .

enryea123 said:
well, you can firstly try to flash a zip of your rom (search on xda or google), it should fix.
the fastboot flash method is the google method so you won't need root (you just have to go into fastboot and connect your phone to your computer, doesn't matter if you have root, or a different rom/kernel/recovery).
If you don't know you to flash from fastboot try first to flash the rom zip.
Click to expand...
Click to collapse
Weird things are happening. I was making a backup of the "SD Card" and partway through, things stopped copying over. And pretty much everything got erased from it. No big deal, since I'd already copied the important stuff first.
But CWM Recovery won't flash the zip file. It keeps telling me the update failed. I verified the hash on the zip I downloaded and it is the same as what is listed on Google's site. But it just won't flash in CWM.

Deozaan said:
Weird things are happening. I was making a backup of the "SD Card" and partway through, things stopped copying over. And pretty much everything got erased from it. No big deal, since I'd already copied the important stuff first.
But CWM Recovery won't flash the zip file. It keeps telling me the update failed. I verified the hash on the zip I downloaded and it is the same as what is listed on Google's site. But it just won't flash in CWM.
Click to expand...
Click to collapse
wait, are you in cwm recovery o just in stock recovery (they are different)? have you previously installed a cwm recovery using fastboot? which zip are you trying to flash?
edit: ok you know what is rom manager so i think that you are in cwm.
edit2: try this zip http://goo.im/devs/bigxie/maguro/bigxie_maguro_OTA_JOP40D-signed.zip

enryea123 said:
wait, are you in cwm recovery o just in stock recovery (they are different)? have you previously installed a cwm recovery using fastboot? which zip are you trying to flash?
edit: ok you know what is rom manager so i think that you are in cwm.
edit2: try this zip
Click to expand...
Click to collapse
I was in CWM Recovery. I was using the zip file that I extracted from the link you gave me for Google's stock ROMs (I can't post external links yet):
(Factory Images "takju" for Galaxy Nexus "maguro" (GSM/HSPA+) (with Google Wallet) --> Android 4.2.1 (JOP40D))
Strangely enough, after "failing" to flash the zip, I had to log into my Google account again because I had selected the option to Wipe Data and Cache, and most things seem to be working very well again. One odd thing I'm still noticing, though, is that some things don't seem to be syncing properly. For example, if I archive some of my email in the Gmail app, then log into Gmail on my PC, the mail is still unread in my inbox. My phone downloads the new mail just fine. But the changes I make on my phone (reading, archiving, deleting, etc.) don't seem to be syncing to anywhere else.
I'm downloading the zip you suggested. I'll give that a try. Thanks!

enryea123 said:
edit2: try this zip http://goo.im/devs/bigxie/maguro/bigxie_maguro_OTA_JOP40D-signed.zip
Click to expand...
Click to collapse
Try this one
Deozaan said:
I was in CWM Recovery. I was using the zip file that I extracted from here the link you gave me (I can't post external links yet):
(Factory Images "takju" for Galaxy Nexus "maguro" (GSM/HSPA+) (with Google Wallet) --> Android 4.2.1 (JOP40D))
Strangely enough, after "failing" to flash the zip, I had to log into my Google account again because I had selected the option to Wipe Data and Cache, and most things seem to be working very well again. One odd thing I'm still noticing, though, is that some things don't seem to be syncing properly. For example, if I archive some of my email in the Gmail app, then log into Gmail on my PC, the mail is still unread in my inbox. My phone downloads the new mail just fine. But the changes I make on my phone (reading, archiving, deleting, etc.) don't seem to be syncing to anywhere else.
I'm downloading the zip you suggested. I'll give that a try. Thanks!
Click to expand...
Click to collapse
That is not a flashable zip! It is a factory image, it must be flashed via fastboot using a computer.

enryea123 said:
That is not a flashable zip! It is a factory image, it must be flashed via fastboot using a computer.
Click to expand...
Click to collapse
Just to be sure I explained myself clearly, I downloaded that Google provided factory image (a .tgz file) and inside it I found a zip file named "image-takju-jop40d.zip" which is what I tried to flash.
That said, I've just recently finished downloading the one you just suggested to me and I will give that one a try soon. Thank you again for your help. I really appreciate it.

I got it working again. The ROM you gave me failed signature verification in CWM Recovery, but I told it to install anyway and it worked. Thank you.
The problem I was having with Gmail not syncing was that I used Titanium Backup to restore my data, but because all the data from my "SD card" got erased, Titanium Backup itself lots its settings, so my Device ID was different. I guess Gmail relies on the device ID for syncing.
Thank you so much for your help! I learned a lot from the experience.

Glad i helped you. well this is one of the reasons why i don't restore data with titanium (especially system data).
and by the way:
Deozaan said:
Just to be sure I explained myself clearly, I downloaded that Google provided factory image (a .tgz file) and inside it I found a zip file named "image-takju-jop40d.zip" which is what I tried to flash.
That said, I've just recently finished downloading the one you just suggested to me and I will give that one a try soon. Thank you again for your help. I really appreciate it.
Click to expand...
Click to collapse
To fully reset and install a clean rom using fastboot you have to extract the bootloader-blabla.img and radio-blabla.img files from the tar.gz archive and then extract the 4 .img files inside the zip (that is inside the tar.gz) and flash this 6 .img files connetting your phone in bootloader mode to your computer and using fastboot in terminal (in fact this procedure reinstall the recovery too).

[Q] N5110 Note 8, is this "bricked"?

Hello,
I hope someone can help me. I'm not completely ignorant when it comes to rooting and flashing custom roms, but it's been a while since the last time I did (last time was my Samsung Galaxy S2). Today I decided I was going to root my N5110 Note 8 and install a 4.4.2 rom on it.
I decided I was going to install the Omni Rom linked here: http://forum.xda-developers.com/showthread.php?t=2569099
I apologize in advance for the long descriptions below.
Here are the steps and issues in the order that it happened:
1) Flashed CF-Auto-Root-konawifi-konawifixx-gtn5110 using Odin (Auto Reboot, F. Reset Time)
2) Downloaded Rom Manager App, and booted into Recovery from there.
3) Using CWM Recovery, I followed instructions as described on the Omni link and did a Wipe/Factory Reset
4) Using CWM Recovery, I selected to install zip from SDCard, and selected the omni-4.4.2-20140102-n5110-HOMEMADE.zip
5) After a few seconds, I got an error 7, and the installation aborted.
6) Tried to reboot back to the system, but of course now that everything is wiped, it just loops back to recovery.
7) I tried installing the zip again, same error. I checked the thread and someone mentioned the same error. OP mentioned using TWRP, so I went back into Download mode and flashed TWRP via Odin
8) After reboot, it went into TWRP. Tried installing zip again, same error. I decided I'll pick up another rom to try first. So, I took out my microSD card so that I can load the ROM over to it.
9) Booted back into TWRP - it no longer sees my SD card. Tried to power down from recovery menus in hopes to get it to see the sd card. No luck
10) I'm desperate now--I am trying to force it off by holding down the power button. It reboots back into recovery. I even try to get it back to download mode so I can flash CWM back on, in hopes that it will let me retry. But now it just shows the battery screen (like when you're charging it while powered off) at empty. I unplug the USB cable, the screen turns off.
11) I try to power it back on without the USB cable plugged in, nothing happens.
12) I plug the USB power back in, and it looks like it's booting up. It goes to the Samsung Note 8.0 N5110 screen and just flickers. The flickering increases in speed over time.
13) I force it back into Download mode, and try to run the CF Auto-Root again (like I said I'm desperate now).
14) After Odin reboots the device, it goes into the battery screen and is doing the weird flickering thing again.
I'm currently attempting to download XXCMH3_stock-rooted-official.zip in hopes to flash via Odin, but the d/l keeps timing out before the whole thing can be transferred.
Someone, please help! What am I doing wrong?

bbqnjl said:
Hello,
I hope someone can help me. I'm not completely ignorant when it comes to rooting and flashing custom roms, but it's been a while since the last time I did (last time was my Samsung Galaxy S2). Today I decided I was going to root my N5110 Note 8 and install a 4.4.2 rom on it.
I decided I was going to install the Omni Rom linked here: http://forum.xda-developers.com/showthread.php?t=2569099
I apologize in advance for the long descriptions below.
Here are the steps and issues in the order that it happened:
1) Flashed CF-Auto-Root-konawifi-konawifixx-gtn5110 using Odin (Auto Reboot, F. Reset Time)
2) Downloaded Rom Manager App, and booted into Recovery from there.
3) Using CWM Recovery, I followed instructions as described on the Omni link and did a Wipe/Factory Reset
4) Using CWM Recovery, I selected to install zip from SDCard, and selected the omni-4.4.2-20140102-n5110-HOMEMADE.zip
5) After a few seconds, I got an error 7, and the installation aborted.
6) Tried to reboot back to the system, but of course now that everything is wiped, it just loops back to recovery.
7) I tried installing the zip again, same error. I checked the thread and someone mentioned the same error. OP mentioned using TWRP, so I went back into Download mode and flashed TWRP via Odin
8) After reboot, it went into TWRP. Tried installing zip again, same error. I decided I'll pick up another rom to try first. So, I took out my microSD card so that I can load the ROM over to it.
9) Booted back into TWRP - it no longer sees my SD card. Tried to power down from recovery menus in hopes to get it to see the sd card. No luck
10) I'm desperate now--I am trying to force it off by holding down the power button. It reboots back into recovery. I even try to get it back to download mode so I can flash CWM back on, in hopes that it will let me retry. But now it just shows the battery screen (like when you're charging it while powered off) at empty. I unplug the USB cable, the screen turns off.
11) I try to power it back on without the USB cable plugged in, nothing happens.
12) I plug the USB power back in, and it looks like it's booting up. It goes to the Samsung Note 8.0 N5110 screen and just flickers. The flickering increases in speed over time.
13) I force it back into Download mode, and try to run the CF Auto-Root again (like I said I'm desperate now).
14) After Odin reboots the device, it goes into the battery screen and is doing the weird flickering thing again.
I'm currently attempting to download XXCMH3_stock-rooted-official.zip in hopes to flash via Odin, but the d/l keeps timing out before the whole thing can be transferred.
Someone, please help! What am I doing wrong?
Click to expand...
Click to collapse
Hi, just so you know... you do not need to root a stock ROM to flash a custom ROM... I am surprised that you think that is necessary
Did you ever set USB debugging to enabled?
Also what Odin do you have?
Turn off note, remove SD, and see if you can start in Stock download mode.
Flash with Odin 3.07... repeat flash with Odin 3.07 and use N5110UEFMI1_N5110XARFMI1_HOME.tar.md5 from http://samsungis.com/
Here is a copy of a reply on a thread it may help if you cannot perform the simple task of reflashing stock ROM from my small list of steps.
Harjan112 said:
Have you tried to flash with Re-Partition checked in Odin 3.07? It looks like your partions are messed up, if it was me I would just give it a try "flashing with re-partition checked" seeing as though its not working anyway.
If that don't work see if you can get a PIT file somewhere, I did read someone put up a link for a PIT file here http://forum.xda-developers.com/showthread.php?t=2544451 although I am NOT 100% sure if this is for the GT-N5110 but read thru it and if you feel adventurous give that PIT file a try.
And here is a link http://storagecow.eu/index.php?dir=Xda/Galaxy+Note+8/XXCMG2/ that someone put up with a leaked firmware and the PIT file and CODE file for the N5110 you can give that a try also.
- Unzip the file
- Open Odin 3.07 (already included in the firmware package)
- Restart phone in download mode
(Press and hold Home + Power + Volume down buttons)
- Connect phone and wait until you get a blue sign in Odin
- Add CODE_N5110XXCMG2_1031850_REV01_user_low_ship.tar to CODE
- Add CSC_OXA_N5110OXACMG2_1031850_REV01_user_mid_noship .tar to CSC
- Add kona_wifi.pit to PIT
- Make sure re-partition is ticked
- Start flash, sit back and wait a few minutes.
- If you encounter any issues with the firmware (Any FC, Bootloop etc)
- Boot into recovery mode (Home+ Power + Volume Up)
- Choose to wipe/factory reset.
(THIS WILL ERASE ALL OF YOUR DATA INCLUDING YOUR INTERNAL SD CARD!)
- Then choose reboot and you should be good to go!
Click to expand...
Click to collapse
GT-N5110 & GT-N5120 - 64GB 633x on board, Status Official on SafeRooted OEM ROMs with Wanam Xposed and RootCloak. The only way to fly 8+ hours!
This badboy don't play with Play & Triangle away!

In TWRP v2.6.3.0 look under mount and see if Micro Sdcard has an "x" if there is no "x" check this and go back to the screen where is says reboot ... reboot recovery from there, once rebooted in recovery go to install and in the top (if you are on v2.6.3.0) you should see storage, tap that and you should have a choice from internal storage and Micro SDcard, if you see Micro SDcard there you should select that and hit ok.
Hoping this helps.
Sent from my SPH-L900 using xda premium

My apologies. I didn't see any of the replies since my email subscription went to my spam folder.
Thank you for those of you who took the time to try and help me.
I know I didn't have to flash stock, but it was more of me being desperate and just trying to put ANY rom on to get it to turn on.
By some weird luck, I had got my tablet working the next day. Basically, in defeat, I just let it sit on the charger overnight thinking a full tank of gas would help it. The next morning, I seriously just pressed all the button combinations and managed to get it to go into recovery and see my SD. I tried yet again to install the Omni Rom again but no dice. It gave me an error again.
So I tried to install a rom again, this time the PAC-rom.
It worked!
Tablet is functional again!
So thank all of you and the electronics god for the miracle!
Have a great weekend you fine folks!

[Q] Failed to flash ROM, SGW doesn't boot

Hi everybody,
sorry for bothering you, but I think I might need some help.
I tried to flash ParanoidAndroid (first try ever to flash a smartphone) but failed 'somehow'.
Initial steps to create the problem
Initial Status: Gingerbread on a Galaxy W; Pretty old and pretty messed up
Download the update.zip to root the smartphone => Becoming root worked!
Download ParanoidAndroid
Download Clockwork Recovery
Created backups using Titanium Backup as root.
Copied ParanoidAndroid to the GalaxyWs internal sd card (yes, this was my mistake)
Wipe cach partition => It said, it worked, I don't know if it did
Rebooted phone => all fine
Rebooted into recovery mode applied update from SD-Card=> Selected ParanoidAndroid.zip => ErrorMessage (I think it was something like file corrupt, sorry I'm not sure about the specific words, but it sounded like this is no updatefile or this file is not a valid zip file.
Status of the problem
Bootup shows Samsung Logo
Bootup than shows GalaxyW-Screen Logo
Bootup than shows the android recovery symbol OR directly reboots
When trying to open the recovery menu, every second time I get the message "Updating (...) Installing MultiCSC... Can't access /system/csc/DBT/system"
If opening recovery menu works, I can only acces the internal storage of the galaxy to install an update (tried the paranoidandroid several times, it doesn't work)
When plugging in the galaxy w to my USB port, I don't get an USB storage shown on my 2 laptops (1 "Windows 7", 1 "Ubuntu 14.0?" )
neither odin (4.43) nor Heimdall are able to flash any files.
So, simple question, what can I do next?
-I cannot copy clockworkmod to my smartphone
-I don't know if I can easily overwrite the kernel or the bootloader.
I searched the forum but didn't find a clear solution, so sorry if this special configuration was already asked.
Thanks for your help and best regards
FrankyDroid

FrankyDroid said:
[*]Rebooted into recovery mode applied update from SD-Card=> Selected ParanoidAndroid.zip => ErrorMessage (I think it was something like file corrupt, sorry I'm not sure about the specific words, but it sounded like this is no updatefile or this file is not a valid zip file.
Click to expand...
Click to collapse
Your ROM's download has been cut either by a connection issue or by you, That is why I always have a backup rom in my SD Card. Also For kitkat, make sure you got CWM 6.0.4.5 or higher. Personally i use PhilZ Touch Recovery. It is simple enough for me. And odin recognizes your phone only in download mode. So make sure you go to download mode then plug the phone in. And also make sure while working with odin, unplug all USBs and other phones

Hey MayB4ck,
thank you for the tips, I finally got it running Using Philz Touch Recovery. Works like hell
Best regards
FrankyDroid

Galaxy Note 8 (GT-N5110) PC Connection Problems - Boot Loop - SOLVED by ME

NO ONE?????
ODIN --> Flash Stock Recovery (AP) with NAND Erase All Option Checked (because it seemed to make sense) + Auto Reboot + F. Time Reset --> Reboots to Stock Recovery (did not work before) --> Reboot into Recovery --> Wipe Data/Cache and Dalvik just to be safe (this crashed it before) --> Reboot. THE END
TL/DR: I am currently stuck on recovery/update mode. Any attempt to wipe data or clear dalvik crashes it. any attempt to access data through TWRP crashes it. Flashing stock rom or custom rom does not help. Somethings wrong with /data? It thinks it has root from the CF Auto Root, but does not really? Something wrong with partitions? Should I wipe the nand with ODIN 3.10? Repartition? ugh ... Please help ...
I have searched the forums and found nothing that describes this issue precisely. I have also tried to apply various suggestions to repair, which, for the most part seems to have made it worse. I am hoping that people still look at this forum.
PC - Windows 7
Initially @4.2.2 ---> Touchwiz debloated stock ROM which I rooted. It worked for a couple years, but the device crashed frequently. I do not recall much about the installation, but believe that I used CWM/TWRP at the time. After installing the ROM, I ran triangle away (out of the box, it had 4.1.2, i recall)
I decided to upgrade to the most recent stock ROM (4.4.2). In order to do so, I used an easy installer I found else where on XDA. (http://forum.xda-developers.com/showthread.php?t=2773712 ---ODIN One Click exe). The device was not initially recognized, so I reinstalled the official driver package (said that they already existed, but I installed again anyway). Ran 1-click and it appeared to work.
Initially, the device booted (long startup) and seemed to function. It also preserved all data and programs (presumably did not touch the internal memory - 16 GB) and possibly root /data.
I then tried to root through most recent ODIN with CF auto root. This appeared to work and rebooted (again, showing the updating android apps screen before fully booting).
The only thing that i could find that had changed was the wallpaper (showed on lock screen but not on home screen). I could no longer find the image, so tried to go to /data/data to find it with root explorer equivalent. This is where it started to act weird.
NOTE: I did not clear anything (system cache, etc. at any point)<--a lie (see below)
It showed the root folder fine, but when I clicked on /data it took a while and could not access it. It either rebooted itself or I rebooted, but this time it was stuck in a boot logo loop. I entered download mode and flashed TWRP through ODIN. I set it to not reboot automatically so that the bootloader was not overwritten automatically (thus losing recovery). TWRP came up. The computer recognized it as a Media Device after I mounted USB storage. Just in case, I copied all of the important files from the internal SD Card to my computer. I then tried to go to the file explorer to copy the wall paper and it forced a reboot. At this point it was stuck on a logo screen boot loop again. I was able to enter Download mode and reflash TWRP. This allowed me to enter recovery again, however, now it would only boot directly into recovery (or Download mode if I did the button combo). The interesting thing was that it would reboot two or three times before successfully entering TWRP.
I believe I tried to reflash the stock ROM at this point, which might have worked but made no difference.
I was also having a lot of problems getting Windows to properly recognize the device. I had to reinstall the drivers a couple times. I tried Kies after the problems started and it tried to connect by failed. The diagnose connection did not work either. I was not able to get Kies to connect though I tried several times throughout the attempted repair
I downloaded a stock-rooted 4.4.2 ROM from here and tried to flash it. It failed.
I also tried to flash via Heimdall, but initially could not find any stock ROMs for Heimdall for the Galaxy 8. (The driver utility that is included helped to get the phone recognized by Windows sporadically).
I decided to switch over to CWM touch recovery, which I flashed via ODIN (I was having issues with TWRP again and also could not get windows to recognize the device as a media device when I mounted USB storage). This worked after a couple tries and I was able to enter CWM. I attempted to flash the stock ROM but it failed. Either at that point or when I tried to mount data it returned an error that device did not have root. Again, it would only boot into CWM (on its own) or Download mode (with key combo). At some point around here I cleared the cache and dalvik (error) after it returned an error saying insufficient space when trying to flash ROM.
I dissected the .exe from the autoflash used in the beginning (stock unrooted 4.4.2) and used the contents (system.img, cache.img, hidden.img, tz.img, recovery.img and one other I do not remember) in Heimdall to create a Heimdall package. At this point I figured out I did not need to create the package, but just specify the individual files. I flashed. It appeared to complete System.img successfully and then failed. Tried again with the same result.
Now when I rebooted, it would enter download mode with the Key combo, but otherwise it booted instantly to an error screen to the effect that a firmware installation had failed and to use the repair function in Kies to fix. Kies still did not recognize it.
At this point, I figured I should stop. Currently I can get to the download screen or the error screen. The computer recognizes it but intermittently fails to install driver. Zadig.exe sees it as Gadget Serial. Sometimes Windows just sees it as SAMSUNG_Android, in which case drivers fail. Once or twice I got it to recognize it as Samsung USB Composite Device, but Kies would still not work.
That's all i have for now. If more information is needed, let me know and I will update the post when I get home from work tonight (this is from memory).
Thank you
UPDATE: last night I went home and was able to get it back to the point where I could flash TWRP or CWM recovery. If I try to flash Stock Recovery, it fails. A minor problem is that I cannot turn it off - it just turns it self on again, so the battery keeps running down.

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?