Develop Bugs

Help with soft briked after Xposed

I hope I'm in the right place
I have zenfone2 with LRX21V.WW-ASUS_Z00A-2.20.40.178_20160330_890_user
I rooted the device following these instructions:
Download the 1 Click Root Tool for Zenfone 2 from
Unzip and connect your phone to PC
Run CheckBeforeAction.bat .... You will get confirmation to proceed to next step
Now run Root_zenfone.bat
Your Device will be rooted automatically
Updated Supersu binary ...
Installed Busybox
Than tried to install Xposed Framework following the instructions here:
Download Xposed Installer from https://drive.google.com/file/d/0B7u...ew?usp=sharing
Connect your zenfone 2 with USB (USB debugging enabled)
Extract the downloaded folder and launch InstallXposedFramework.bat (phone will reboot)
Now launch InstallXposedInstaller.bat to install Xposed apk on your phone. Enjoy Xposed on your zenfone 2
My device rebooted and stayed in the ASUS screen
I tried to sideload stock rom (UL-Z00A-WW-2.20.40.174-user) in recovary but it fails saying:
"Can't install this package ( 3 10 09:43:34 CST 2016) over newer build ( 3 30 14:23:11 CST 2016)
E: Error in /sideload/package.zip
(status 7)
installation aborted"
any advice how to overcome the problem?

Same problem here.

Problem with installing Lineage 14.1 made by surdu_petru

First of all thank Surdu for making both CM13 and this CM14 rom.
I'm having a bit of problem with installation.
Model number is HUAWEI RIO-TL00
I am running the CM13 made by surdu_petru, 13.0-20160502-UNOFFICIAL-rio. I was able to get that installed relatively easily and it runs just smooth and fine.
I have updated the TWRP to the version listed by Surdu in the Lineage OS thread and performed factory reset before attempting to install,
but I got an error 7
the version I'm attempting to install is "lineage-14.1-20170115-UNOFFICIAL-rio"
the error messages are
comparing TZ version TZ.BF.3.0.C3-00025 to TZ.BF.3..0.C3-00022
assert failed: rio.verify_trustzone("TZ.BF.3.0.C3-00025") = "1"
Installing zip file '/external_sd/lineage-14.1-20170115-UNOFFICIAL-rio.zip'
checking for MD5 file...
skipping MD5 check: no MD5 file found
Updater process ended with ERROR:7
Error installing zip file '/external_sd/lineage-14.1-20170115-UNOFFICIAL-rio.zip'
I noticed that something on my phone definitely doesn't match with the updater script.
Removing the assert lines in the updater script will allow TWRP to install, but I cannot get past the Cyanogenmod robot face, it keeps flickering after a second.
Any suggestion on what to do is appreciated, thanks.

1. try to flash the lastest version of TWRP. surdu_petru had mentioned that in the post.
2. I experienced the same issue of looping Cyanogenmod face flickering, after force reboot. all fixed.

Bricked .. Help me !

Hello, i have bricked my phone after an hurupdate, i dont know why but the phone have suddenly turn off during twrp hurupdater process and now i can't turn on the phone, i can plug in my pc & he recognize him as "fastboot devices" but when i try to flash something or unbrick via multi tool nothing happen (FAILED (remote: Command not allowed))
I can't do anything now.. Please help me !

Albanheraibi said:
Hello, i have bricked my phone after an hurupdate, i dont know why but the phone have suddenly turn off during twrp hurupdater process and now i can't turn on the phone, i can plug in my pc & he recognize him as "fastboot devices" but when i try to flash something or unbrick via multi tool nothing happen (FAILED (remote: Command not allowed))
I can't do anything now.. Please help me !
Click to expand...
Click to collapse
Erecovery has started working for some people. you can try that

mrmazak said:
Erecovery has started working for some people. you can try that
Click to expand...
Click to collapse
Nope .. nothing work ..
Anyone know how to unbrick ? ..

I think i have flashed the wrong update, i have bndl21 & i have flashed the bndl22 or bndal10, my phone is dead ?

Albanheraibi said:
I think i have flashed the wrong update, i have bndl21 & i have flashed the bndl22 or bndal10, my phone is dead ?
Click to expand...
Click to collapse
Shouldn't be, at least not from that, not completely.
Was this the first condition, or an added problem?
I think best thing to try is the service ROM.
This one is BND-L21C432..
Service rom BND-L21C432
https://www.androidfilehost.com/?fid=11050483647474828964
1. Unzip download
2. copy the dload folder to root of sdcard
3. power on phone holding all three buttons
4. After phone finishes and reboots, unlock frp and bootloader, if needed
5. Use Huru or HWOTA to flash correct firmware for your model/ region.. If this is not the correct version for your honor 7x

Now with dc phoenix i have restore the fastboot and the erecovery, i can flash all i want but nothing happens, just boot loop at "your phone is not trusted" screen.
I was on catuva's rom before brick and now i have the catuva splashboot screen even after full firmware retore by dc phoenix.
When i try to flash in twrp i see lot of errors related to partition table (invalid argument cust, odm, sytsem etc) it seems the partition table have a problem..
The DLOAD can restore this ?

When i try to restore via dload it stuck at 5% and it says "software install failed!" ..
Someone Help me ?..

Albanheraibi said:
When i try to restore via dload it stuck at 5% and it says "software install failed!" ..
Someone Help me ?..
Click to expand...
Click to collapse
You got failed using the "service-rom" dload?
This one is Oreo I believe. There is a nougat one also.

mrmazak said:
You got failed using the "service-rom" dload?
This one is Oreo I believe. There is a nougat one also.
Click to expand...
Click to collapse
Yes stuck at 5%..
i have try to flash the Honor 7X-Elemental V1(8.X-GPU) and i get an error at the end of process >
mount: failed to mount
/dev/block/platform/hi_mci.0/by-name/system at /system: invalid argument
What i am supposed to do with this error ?

Albanheraibi said:
Yes stuck at 5%..
i have try to flash the Honor 7X-Elemental V1(8.X-GPU) and i get an error at the end of process >
mount: failed to mount
/dev/block/platform/hi_mci.0/by-name/system at /system: invalid argument
What i am supposed to do with this error ?
Click to expand...
Click to collapse
Says in the install guide for it, you must be running at newest security patch in order to install elemental.
Please focus on one thing. Getting phone to boot full stock first before trying other rom. You are going to hard brck your phon if you keep doing flashes when the stock fails to install

mrmazak said:
Says in the install guide for it, you must be running at newest security patch in order to install elemental.
Please focus on one thing. Getting phone to boot full stock first before trying other rom. You are going to hard brck your phon if you keep doing flashes when the stock fails to install
Click to expand...
Click to collapse
When i try to rollback emui5 via twrp with your guide i have this error :
write radio image...
check_write_data_to_partition,write data error update_huawei_pkg_from_ota_zip: update pakage from zip failed
E : unknown command [errno]
Updater process ended with ERROR : 9
Error installing zip file '/external_sd/HWOTA8/update.zip'
i remember that the phone has started to bootloop just after twrp flashed the wrong radio file..
This is the end ?

Albanheraibi said:
When i try to rollback emui5 via twrp with your guide i have this error :
write radio image...
check_write_data_to_partition,write data error update_huawei_pkg_from_ota_zip: update pakage from zip failed
E : unknown command [errno]
Updater process ended with ERROR : 9
Error installing zip file '/external_sd/HWOTA8/update.zip'
i remember that the phone has started to bootloop just after twrp flashed the wrong radio file..
This is the end ?
Click to expand...
Click to collapse
I am not understanding how you say you follow my guide, then post the error.
This error shows you are trying to install ota update with TWRP.
My guide sets you to install ota update file with a modified stock recovery (no-check).
If you are having trouble because of bad translation, please do not assume what you need to do and wait for proper help and translation

mrmazak said:
I am not understanding how you say you follow my guide, then post the error.
This error shows you are trying to install ota update with TWRP.
My guide sets you to install ota update file with a modified stock recovery (no-check).
If you are having trouble because of bad translation, please do not assume what you need to do and wait for proper help and translation
Click to expand...
Click to collapse
Ok after update with hurupdater via twrp (he flashed the correct radio.img file) the phone have income from death !
Thank you for trying to help me !

Oneplus 3 bricked tried multiple methods, please help

So i've bricked my oneplus 3 (oxygen 5.0.5) rooted with magisk 13 by flashing a custom rom, it was in a bootloop after the update.
I tried factory resetting via TWRP because i had a backup ready but the reset somehow failed and my phone rebooted and showed a failed md5 check with these checks failed:
* Cache : Failed
* Boot : Failed
* System : Failed
* Recovery : Failed
* md5 checksum failed
When i try to boot into recovery mode (twrp) it gives me the same message and loops.
Since then i've tried flashing several recovery.img's with several modded and non modded twrp versions, none of them got me into twrp.
I have tried the popular mega unbrick guide from Naman Bhalla twice but didn't help either.
Any ideas ?
Thanks in advance

EpicLawR said:
So i've bricked my oneplus 3 (oxygen 5.0.5) rooted with magisk 13 by flashing a custom rom, it was in a bootloop after the update.
I tried factory resetting via TWRP because i had a backup ready but the reset somehow failed and my phone rebooted and showed a failed md5 check with these checks failed:
* Cache : Failed
* Boot : Failed
* System : Failed
* Recovery : Failed
* md5 checksum failed
When i try to boot into recovery mode (twrp) it gives me the same message and loops.
Since then i've tried flashing several recovery.img's with several modded and non modded twrp versions, none of them got me into twrp.
I have tried the popular mega unbrick guide from Naman Bhalla twice but didn't help either.
Any ideas ?
Thanks in advance
Click to expand...
Click to collapse
Your only way out seems to be the Mega Unbrick Guide. What happens when using it? Is your phone recognised properly? Which Windows version are you using?

tnsmani said:
Your only way out seems to be the Mega Unbrick Guide. What happens when using it? Is your phone recognised properly? Which Windows version are you using?
Click to expand...
Click to collapse
Thanks for the reply,
When i use the tool, it seems to be working fine until the reboot. The tool detects my device as a com device and downloads everything and completes the downloading process without errors.
When the tool is done i unplug my phone to let it reboot, the md5 checksum fails again BUT this time not with the "recovery : failed" error. At this point i can still not boot into recovery mode. The only thing i can acces is the fastboot screen.
I am using windows 10 Version 1709 on an ASUS ROG g502 laptop.

EpicLawR said:
Thanks for the reply,
When i use the tool, it seems to be working fine until the reboot. The tool detects my device as a com device and downloads everything and completes the downloading process without errors.
When the tool is done i unplug my phone to let it reboot, the md5 checksum fails again BUT this time not with the "recovery : failed" error. At this point i can still not boot into recovery mode. The only thing i can acces is the fastboot screen.
I am using windows 10 Version 1709 on an ASUS ROG g502 laptop.
Click to expand...
Click to collapse
It can't be "as a com device". It has to be detected as defined in the Guide, something like QDLoader 9008 or so. I am not sure of the exact name. Check the Guide. Unless it is detected exactly as described in the Guide, the unbricking will not be successful. Plus sometimes you have to use the tool multiple times before it succeeds.
If, as you say, there are no 'failed' messages and if you are able to boot to the bootloader, you can also try sideloading the OOS ROM.
EDIT: Must have been asleep.
EDIT: On Win 10, disabling driver signature verification is very important before you install the Qualcomm drivers.

tnsmani said:
It can't be "as a com device". It has to be detected as defined in the Guide, something like QDLoader 9008 or so. I am not sure of the exact name. Check the Guide. Unless it is detected exactly as described in the Guide, the unbricking will not be successful. Plus sometimes you have to use the tool multiple times before it succeeds.
If, as you say, there are no 'failed' messages and if you are able to boot to the bootloader, you can also try sideloading the OOS ROM.
EDIT: Must have been asleep.
EDIT: On Win 10, disabling driver signature verification is very important before you install the Qualcomm drivers.
Click to expand...
Click to collapse
My device was detected as a 9008 by my computer, but by the tool it was detected as a com device. driver signature vertification was disabled when trying the tool multiple times, but i can try to use it on another computer.
Sideloading the OOS rom didn't work the first time i tried it, but i am not very familiar with that so i can try that again aswell.
Thanks.

EpicLawR said:
So i've bricked my oneplus 3 (oxygen 5.0.5) rooted with magisk 13 by flashing a custom rom, it was in a bootloop after the update.
I tried factory resetting via TWRP because i had a backup ready but the reset somehow failed and my phone rebooted and showed a failed md5 check with these checks failed:
* Cache : Failed
* Boot : Failed
* System : Failed
* Recovery : Failed
* md5 checksum failed
When i try to boot into recovery mode (twrp) it gives me the same message and loops.
Since then i've tried flashing several recovery.img's with several modded and non modded twrp versions, none of them got me into twrp.
I have tried the popular mega unbrick guide from Naman Bhalla twice but didn't help either.
Any ideas ?
Thanks in advance
Click to expand...
Click to collapse
Try to flash stock recovery if succeeded then wipe complete, after twrp with root and then install stock oos

Msmdownload is low level format tool, another method of flashing won't work if it isn't.
Since you said that msm reported succeed but after it you still got a hash fail, it's either you flash the wrong file or a you've got a bad emmc..

You can't easily brick a Oneplus device. At worst you've screwed up your options for self-contained flashing via twrp. The two most common issues restoring to stock via sdk tools on a PC are i) wrong drivers being used, make sure you've installed the oneplus drivers on your computer and the device is recognised properly; and ii) you don't have full admin rights - make sure you've run the CMD shell as administrator before you execute any of the sdk commands.

hello
1.do u unlocked your bootloader?
2.connect your phone to PC into bootloader, if you can... try these codes with fastboot
fastboot erase cache
then
fastboot flash recovery ***.img
then
fastboot boot ***.img
then you should see you recovery....
before flashing ROM go to mount and mount system,recovery and data
then flash ROM

Updater process ended error 255 device code name is olivelite

I tried to install the evolution x rom on my Redmi 8A phone I can confirm that I downloaded the right file then proceed to flash it on orange fox recovery project (sideloaded it) then suddenly it throws back the error code
Updater process ended error : 255
Tried multiple times reflashed the recovery changing to twrp ( I used the official recovery) on my previous device I also experienced this problem and there was an unofficial twrp image that solved this they say it's because I tried to flash a 64 bit Rom on a 32 bit recovery plus I can't find any "64 bit" version for my device any help????

If you need any information comment it down I won't reply instantly but I will