Database Info

Mate 7 brick ?

Hi everyone being under marshmallow 6.0 B560 with my MATE 7 TL10 I decided to Xposed installed. I read some walkthroughs on the net and at one time by restarting the laptop I saw that the system had planted (message: the system application do not answer something like that). So I did a reset wip / data / etc .. starting in TWRP manual (Version 3.0.2 UNOFFICIAL) but unfortunately I know not what means my phone is bricked? (Completely blocks the Huawei logo. So I tried to reinstall my backup I made with TWRP just before installing Xposed but I error = 255. So I tried to install a new rom it is a 5.1.1 or 6.0 or even KangVIP I have the error file is corrupted So I passed on stock recovery mode to try to re-install the official ROM, but without success.:
When I put the update.zip file or folder dload (with the file update.app) on the SD card, the system remains blocked 5%. I even tried to inject a Rom in fastboot mode with the PC but without success (blocks on the logo).
info: I can access without problems in fastboot mode and the bootloader is unlocked.
One idea to solve the problem please

Honor 6X infinite boot

Hi everybody,
I'm here to ask for help cause i have a problem with my honor 6X.
I was looking to implement carstream on it in order to have access to my youtube playlists. So i did the following :
- Find the Bootloader code for unlocking
- I unlocked the bootloader with the appropriate commands. After that i got the message that the phone was unlocked on boot
- After that i flashed TWRP in order to have a recovery custom. It worked well and i was having the TWRP menu when booting the phone with the volume up and power button
- Next, i tried to root the phone by adding magisk. Flash on TWRP did well but after the first boot i was asked by a message to insert the password to unlock phone crypting. I wasn't having this password so i tried to flash magisk again. After two flash the phone was booting correctly and i set it up. I installed Root checker and the phone was correctly rooted. The only problem was that i couldn't access to some parameters options like developer mode or unknown sources. The parameter app was closing when trying to access this options.
- As the problem looked to be from the OS i tried to implement a custom one (Pixel Experience) using the TWRP recovery i added before. After that everything started to go wrong. When i was in flash menu of TWRP i didn't know which partition to use in order to flash the system.img file. I choose the system partition to do it and operation was done. I boot the phone and after that but it stayed frozen on the boot image (honor on blue background).
- After a whole night waiting for the phone to boot i tried to boot on the TWRP recovery in order to add a new custom rom but i couldn't do it. Th e only recovery i have access is EMUI recovery. I tried to do a backup on the EMUI recovery but the phone still don't want to boot.
As th e situation looks critical i ask you for some help in order to avoid to make it worst. I currently have access to the recovery EMUI and i'm pretty sure to fastboot too even if i didn't try. First step know is to try to make the phone working again and maybe with some help try to implement carstream again.
Thank you for your help

[HELP] Bricked device ? need help

my device is BL-L21 version (EU variant)
I saw this thread : https://forum.xda-developers.com/honor-6x/development/rom-aospextended-6-4-honor-6x-t3935711
So rebranded my phone to indian model to get emui 8 according to this video : https://www.youtube.com/watch?v=onj2Z5eh7Mo
Then flashed this custom askuccio recovery : https://drive.google.com/file/d/1qvIgmlPPJ0amS8-aNEIG3xDKc9tHxrW7/view
Now in custom recovery followed the instructions (wipe system cache dalvik data) but could got errors like "could not mount this" "unable to unmount that"
At the time I didn't know all I had to do was to change filesystem then get back to previous one.
So I went into fastboot erase system, data ,cache.
I also wiped internal storage, which I think was the big mistake I've done.
Then back into recovery flash asop6.4 and let it do it's thing, it got stuck on boot screen for quite some time.
When I got back to it, EMUI eRecovery stated something went wrong and proposed to factory reset device. Which I did but gave an error.
Now I tried
* dload method https://forum.xda-developers.com/showpost.php?p=73954487&postcount=240, download link is dead btw.
after copying dload to /sdcard/ and rebooting with vol+/vol-/pwr down, gives : "software install failed"
* HurUpdater, I have trouble finding the correct update.zip/update_all_hw.zip/update_data_public.zip files. Since I can't boot any rom right now I can't use Firmware Finder app.
I also tried to look into /tmp/recovery.log. deleted it because too big, just wanted the result of HurUpdater but I guess permissions have changed and now nothing gets written to it.
* eRecovery to try to get back to stock and do it all over but it didn't work, which is normal since everything is unlocked in the phone.
device then reboots and goes to eRecovery.
I just want to get AOSPExtended running, what should I do ?
Oh yeah also, beginner mistake : I don't have any backup.

Did I do something wrong to get no answers?

Google Pixel - No apply update from ADB in recovery and other strange things

Hello everyone,
The starting situation is the Google Pixel of my mother was stuck on android 8.0. While showing there was an update available, the update would always fail to install after the reboot in the process. I found advice to factory reset the phone and then update, but this didn't help.
So my first thought was, if the update won't install the normal way I will do it manually. Google OTA installation guide says, get file (latest), reboot to recovery, plug in to USB, choose apply update by adb.
At this point the guide loses me, because the recovery screen I get to only lists reboot, reboot bootloader, simlock tool and device info tool (see picture). The device info will only tell "failed to update device info". The simlock tool just says "failed to enable simlock". Further while on this screen the phone isn't visible as an ADB device any more.
Next thing to try cause this didn't work was getting the image file (latest) from Google and flashing it through fastboot flash all, which led to a boot loop and the phone not starting at all. So I went and flashed back to the android 8 that was on it before and the phone booted again, but I'm still not any step further.
Next idea was maybe the recovery is broken somehow, so I went to install TWRP. Following the instructions I copied the latest version zip onto the phone and booted the img through fastboot. So far everything is fine, but when I install the zip I will get several errors about "can't mount /persist". And the installation won't work.
At this point I am out of ideas, so maybe someone here can tell me if and how this can be fixed? I wasn't able to find any information on this issue, aside from some xiaomi phones can show similar errors with the /persist partition and TWRP.
Any help would be welcome.

Android Recovery: Issues flashing via ADB or external SD card

Hey,
following happend: I dirty flashed LOS 17.1 february update over december version following the instructions ivan gave. After flashing gapps and magisk I flashed the newest TWRP image.
Everything went well (at least it seamt so) I booted to LOS and set up new fingerprints (had to deleate them before flashing), started first app (spotify) and screen went black and phone restarted. Than I got the the FRP Lock message and wasn't able to boot agian neither to LOS nor to TWRP.
Everything followed is here. Tldr: I wasn't able to reflash Stock Rom with Odin no matter what I tried and got lost bettween download mode and nothing.
However I somehow got Android Recovery working!! This is what I can and cannot do:
chrisrevoltes said:
Now I'm able to boot to download mode and original recovery but not to system.
This is what Recovery shows:
View attachment 5218201
I can wipe data and cache partition, but not system partition.
I can view the logs, but I'm not sure what they are telling me....
I can view my external SD card, but trying to install ether TWRP, LOS or the stock image aborted with an error Update from external storage is disabled following a reboot to recovery. Any idea how to enable that?
ADB seams to be working. It can find the phone, although there is an message Stopping adbd... on the phone.
View attachment 5218209
adb devices -l shows:
XXXXXXXcf0cd263704 sideload product:heroltexx model:SM_G930F device:herolte transport_id:8
Sideloading the stock image or TWRP results in: Total xfer: 0.00x in console and adb status 1 on phonescreen with phone reboot to recovery.
Any other adb command (except those three getter) has ether no effect or results in an error.
Any further attempt to flash again with Odin results in the same errors like described in my last post.
Any ideas? ADB or external storage seams like a good way. But system partition worries me.
Click to expand...
Click to collapse
Can anyone help me?

Some time ago I had a Samsung S6 Edge G925I with which I had the same problems and errors as you. After an intense week flashing systems and without getting it to work, I took it to a colleague who has box and other tools to unbrick, unfortunately he discovered that the problem was hardware, more specifically emmc memory problem, I had to resort to changing the plate and problem solved. I would advise you to try all the firmwares that you can from your binary and with old versions of Odin, without opening as administrator, I hope you are lucky; I'll keep thinking if I can think of another solution, regards.

Thanks! I have finally made it. It took my the third day (thanks to covid home office) but I'm now up again with new LOS (but old TWRP).
For the record: My last try was using an older and modified version of Odin (3.13 here) and flashing the newest stock image with extracted PIT file. After 3 minutest it finally booted.
Im not sure if it was the older Odin version (some recommending using v3.14 for devices newer 2018) or the modified Odin version.