Asus Zenfone 2 ADB FAIL(flash_cmds error! ) - ZenFone 2 Q&A, Help & Troubleshooting

Hi everyone, i hardbricked my Zenfone 2 yesterday. But i opened it with xFSTK. It flashed a few files or something. I reached bootloader.
After that i tried to use Asus Flash Tool but while i'm flashing a raw file it stopped and didin't work for 30 min..
Then i decided to do it by myself. I downloaded the necessary files. I opened ADB in platform-tools.
But When i tried to flash boot.img i saw an error like this:
Code:
FAILED (remote: flash_cmds error! )
I do not know what to do. I have never seen an error something like that while i'm using ADB.
Also there is one more problem. The phone can reach drodiboot screen, because of this i can't send it to service i think. It means i have to solve this problem by myself. Please help me..
If there is a problem with my English, sorry about that.

Related

[Q] Error When booting up phone

Hey,
Ill explain where i was when this happened, to give everyone a better overview of the problem so someone may be able to help me more efficiently.
Been using phone for a while since it had some out, without rooting and messing around with anything and using pc companion to update firmware and bits,
2 Days ago i saw a nice theme on the arc forums so i thought, i like that and im going to install it, so i downgraded to 2.3.2 using x10 flasher then rooted with gingerbreak, updated to 2.3.3 using ota to keep root.
I started to install bits a pieces of the theme, using a root explorer, changing permissions to rw--r--r on all of the files to make them work.
It was going swimmingly, status bar changed, applications changed (Sms, Settings, Clock) those sorts of things, and then when it came to putting
SemcGenericUxpRes.apk
&
framework-res.apk
into the correct place on the phone,
/system/framework
i did the first one and it worked perfectly, rebooted itself without me pressing anything but i thought that may be normal for sony erricsson androids as i know their systems are different to the basics you get with a htc android phone.
then i put framework-res.apk into the same folder and again it started to reboot itself and i thought, great its all done and will look amazing.
The Sony Erricsson writing appeared, and then starts to bootloop, so now im thinking oh, s##t.
So i pulled the battery and left if for 10 miniutes and put it back in, no joy.
I now go back to using the x10 flasher to reinstall 2.3.2 but i get an error saying that ive not enabled usb debugging, and i probably hadnt as i had only just reinstalled 2.3.3. so i disconnect my phone and try to turn it on. no joy again
Plugged it back in on the off chance it may just have been an slight bug and tried to flash again, this time it started flashing all the bits as it does and then half way through the process it says, Error! Usb debugging not activated, disconnect phone and turn it on.
So this time when i try to turn my phone on, all i get is a Picture of a phone with an Exclamation mark above it, im assuming because the software has corrupted on the install as its only done half of it.
So here is my problem, i cant turn my phone on to get usb debugging on.
I can get into fastboot mode, blue light, holding search and plugging usb in, but dont know where to go from there.
Any Help will be much appreciated.
Many Thanks.
Shotgunfool
The message in flashtool is generic, it just tells you to enable those things when flashtool is done. It will state this wether you encounter an error or not . It shouldn't matter wether they're enabled or not for flashtool to work and flash your phone.
You might try to use SEUS to restore your phone, if i remember correctly a few others has had this problem and resolved it that way.
You might also try to flash the rooted system.img through fastboot.
Next time you mod your phone with rootexplorer just move all apk's/jar files to /system first and then set the permissions and then move them to /system/framework and /system/app this will prevent a bootloop. I learned the hard way aswell, but then again i learned to use flashtool.
Regards Dousan...
Dousan said:
The message in flashtool is generic, it just tells you to enable those things when flashtool is done. It will state this wether you encounter an error or not . It shouldn't matter wether they're enabled or not for flashtool to work and flash your phone.
You might try to use SEUS to restore your phone, if i remember correctly a few others has had this problem and resolved it that way.
You might also try to flash the rooted system.img through fastboot.
Next time you mod your phone with rootexplorer just move all apk's/jar files to /system first and then set the permissions and then move them to /system/framework and /system/app this will prevent a bootloop. I learned the hard way aswell, but then again i learned to use flashtool.
Regards Dousan...
Click to expand...
Click to collapse
When you say flash the rooted system image through fastboot, how do i go about using fastboot to flash an image?
Cheers
Shotgunfool
shotgunfool said:
When you say flash the rooted system image through fastboot, how do i go about using fastboot to flash an image?
Cheers
Shotgunfool
Click to expand...
Click to collapse
Check this link out (i'm asuming you've unlocked your bootloader. If not you might read up on pros and cons before doing so, if doing so at all):
http://forum.xda-developers.com/showthread.php?t=1043630
Regards Dousan...
If you haven't got an unlocked BL i would first try out SEUS or flashtool again
Dousan said:
Check this link out (i'm asuming you've unlocked your bootloader. If not you might read up on pros and cons before doing so, if doing so at all):
http://forum.xda-developers.com/showthread.php?t=1043630
Regards Dousan...
If you haven't got an unlocked BL i would first try out SEUS or flashtool again
Click to expand...
Click to collapse
I dont have an unlocked bootloader, as i didnt think i needed one to change themes,
when you say SEUS, do you mean Pc Companion?
and just tried flashtool again, same error
shotgunfool said:
I dont have an unlocked bootloader, as i didnt think i needed one to change themes,
when you say SEUS, do you mean Pc Companion?
and just tried flashtool again, same error
Click to expand...
Click to collapse
Nah SEUS is another tool like Pc Companion . Check out this link, the only one i could find:
e: seems that SE has taken it of their own site as the link, linked to SE's homepage and can not be found. Must be another link somewhere floating around?
You're right you don't need an unlocked BL for theming and it's weird you get that error while flashing.
Regards Dousan...
Dousan said:
Nah SEUS is another tool like Pc Companion . Check out this link, the only one i could find:
e: seems that SE has taken it of their own site as the link, linked to SE's homepage and can not be found. Must be another link somewhere floating around?
You're right you don't need an unlocked BL for theming and it's weird you get that error while flashing.
Regards Dousan...
Click to expand...
Click to collapse
Ive followed the previous link that describes unlocking the bl and flashing a rooted image, ive unlocked the bootloader, just got 2 miniutes left of the download of the custom image, so ill let you know if that works.
Thanks for your help Dousan
No Luck, im getting this error when trying to flash the modded image
Code:
C:\Users\Oscar\Desktop\BL\fastboot>fastboot flash system play_modded.img
sending 'system' (236189 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 667.320s
Any idea?
shotgunfool said:
No Luck, im getting this error when trying to flash the modded image
Code:
C:\Users\Oscar\Desktop\BL\fastboot>fastboot flash system play_modded.img
sending 'system' (236189 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 667.320s
Any idea?
Click to expand...
Click to collapse
Did you put the play_modded,img in fastboot folder?
Regards Dousan...
Dousan said:
Did you put the play_modded,img in fastboot folder?
Regards Dousan...
Click to expand...
Click to collapse
Yes,
and just got a copy of seus, and it says cannot update phone contains modified software.
This is because i removed aload of the bloat when i was rooted.
shotgunfool said:
Yes,
and just got a copy of seus, and it says cannot update phone contains modified software.
This is because i removed aload of the bloat when i was rooted.
Click to expand...
Click to collapse
Hhhmm there should be a choise to repair only in SEUS?
Regards Dousan...
Dousan said:
Hhhmm there should be a choise to repair only in SEUS?
Regards Dousan...
Click to expand...
Click to collapse
It doesnt get that far does it, it checks the current firmware before allowing you to choose whether or not you want to update/repair
shotgunfool said:
It doesnt get that far does it, it checks the current firmware before allowing you to choose whether or not you want to update/repair
Click to expand...
Click to collapse
I've google the error and a few people seems to have had it to. There's no rel fix to it as far as i can read, more like suggestions.
Try another usb cable. Try another usb port on the pc. Try it on another pc.
Ohh didn't know about SEUS haven't used it my self.
Regards Dousan.
Dousan said:
I've google the error and a few people seems to have had it to. There's no rel fix to it as far as i can read, more like suggestions.
Try another usb cable. Try another usb port on the pc. Try it on another pc.
Ohh didn't know about SEUS haven't used it my self.
Regards Dousan.
Click to expand...
Click to collapse
Thanks for the help but nothing has worked,
if anyone has any other suggestions i would greatly appreciate the help.
Many Thanks
Shotgunfool
shotgunfool said:
Thanks for the help but nothing has worked,
if anyone has any other suggestions i would greatly appreciate the help.
Many Thanks
Shotgunfool
Click to expand...
Click to collapse
You could try this:
fastboot erase cache
Regards Dousan...
e: I've googled some more and it seems that it's kind of random and most people get it resolved some how. Trying flashing over and over, waiting till the next day, using a usb cable with ferrit (absolutely no idea what that is), changing usb port, changing cable, changing machine, changing OS etc.
It might be that the file it's sending is to big to handle somehow.
Maybe try to find bin4ry's trhead in the dev section on how to boot CWM (ClockWorkMod) and from there restore your phone with zerojay's rom. It's a flashable .zip to flash from CWM. That might work if it's about the size being send when flashig/sending/booting from fastboot.
Dousan said:
You could try this:
fastboot erase cache
Regards Dousan...
e: I've googled some more and it seems that it's kind of random and most people get it resolved some how. Trying flashing over and over, waiting till the next day, using a usb cable with ferrit (absolutely no idea what that is), changing usb port, changing cable, changing machine, changing OS etc.
It might be that the file it's sending is to big to handle somehow.
Maybe try to find bin4ry's trhead in the dev section on how to boot CWM (ClockWorkMod) and from there restore your phone with zerojay's rom. It's a flashable .zip to flash from CWM. That might work if it's about the size being send when flashig/sending/booting from fastboot.
Click to expand...
Click to collapse
I get this when trying to erase cache
Code:
C:\Users\Oscar\Desktop\BL\fastboot>fastboot erase cache
erasing 'cache'...
(bootloader) Erase of partition 'cache' requested
FAILED (remote: Partition not found, or permission denied)
finished. total time: -0.000s
when trying to boot CWM it just hangs on
Code:
C:\Users\Oscar\Desktop\BL\fastboot>fastboot boot recoveryPLAY.img
downloading 'boot.img'...
and then when i disconnect the usb i get
Code:
FAILED (data transfer failure (Too many links))
finished. total time: 78.086s
Any other ideas?
Thanks, Shotgunfool
I'm out of ideas, but i see that you disconnected the phone after 78 secs when booting the CWM image. I've heard it could take a few min. to boot into. So I would try agian and let it 'hang' for atleast 2-3 min.
If nothing comes out of it i would pm Bin4ry or Alejandrissimo or Blagus for help as i think they would know alot more and they've might encountered this error before. and know how to solvd it?
Regards Dousan...
e: the last code snip you stated seems to point at the fact it's not sending or able to send anything through your usb to your phone for som reason. That error comes up while it's plugged in and while it's unplugged. It might be a drivers problem. Try to reinstall the drivers that came with the fastboot package again. I could be something in your windows settings that's preventing it from working correctly?
Dousan said:
I'm out of ideas, but i see that you disconnected the phone after 78 secs when booting the CWM image. I've heard it could take a few min. to boot into. So I would try agian and let it 'hang' for atleast 2-3 min.
If nothing comes out of it i would pm Bin4ry or Alejandrissimo or Blagus for help as i think they would know alot more and they've might encountered this error before. and know how to solvd it?
Regards Dousan...
e: the last code snip you stated seems to point at the fact it's not sending or able to send anything through your usb to your phone for som reason. That error comes up while it's plugged in and while it's unplugged. It might be a drivers problem. Try to reinstall the drivers that came with the fastboot package again. I could be something in your windows settings that's preventing it from working correctly?
Click to expand...
Click to collapse
Im getting closer, just got CWM Up and running, and i knew it shouldnt have taken long to put the image on my phone, i have a fast pc
Code:
C:\Users\Oscar\Desktop\BL\fastboot>fastboot boot recoveryPLAY.img
downloading 'boot.img'...
(bootloader) USB download speed was 129134kB/s
OKAY [ 0.530s]
booting...
(bootloader) Download buffer format: boot IMG
OKAY [ -0.000s]
finished. total time: 0.530s
lol
im pretty sure thats an error on fastboots part thats a lot of kbs
Although, ive found the weirdest fix to it hanging on sending 'boot'
and you probably wont believe me, but i was just about to go and try another pc so i plugged in my memory stick and as soon as i did, it sent it immediatly, so i have no idea, why, how, but that works
just downloading a rom to flash and fingers crossed it'll work
That's really good to hear, hope it works out this way
About the the fastboot error you refer to, it's all abaout Bits and Bytes - kB and kb and there's a huge difference between them and it's something like 8 times the difference as in 8kB is 1kb. I saw someone explain it somewhere on xda (might've been here in the play forum), that providers use it for misleading costumors to believe they get a much faster internet connection and such
Regards Dousan...
Hey, ive sent you a pm

Zenfone 2 bricked,no recovery mode,no adb, flash via fastboot premission denied

I tried to install CM13 .zip install finished ok, but after that the phone didnt boot no more.
result Zenfone 2 bricked, no recovery mode
I only have CWM temporary access, no adb.
So i tried to install stock firm from ext memory card the lastest from asus support , and the message was " can t install this package over newer version build.
I tried to flash recovery.img via fastboot and i got remote : permission denied.
Tried asus Flash tool and got permission denied , too.
Some places saids that its because its has lock pin or patern, but i cant remove it without adb access.
So i dont know what to do.
Now i read something about xFSTK, but i dont know what's the use of it.
Sorry for my poor Languaje.
Of course i prefer to have my cm13 working.
If anyone cant help me i ´ll be very greatfull
TKS
Did you unlock your phone?
Try flashing stock zip on ASUS site with temporary TWRP
Yes
HungNgocPhat said:
Did you unlock your phone?
Try flashing stock zip on ASUS site with temporary TWRP
Click to expand...
Click to collapse
It was not easy, lot of things falied.
But finally i could, Tks.

[HELP] Unbrick Huawei GR3 (TANGO) - TAG-L23

Guys: I need your understanding, experience, patience and HEEELP!!!
The history:
2 months ago, I bought a new HUAWEI GR3 (TANGO) TAG-L23. Processor = MT6753T
I tried to root it using KingoRoot. I Messed it up... Got a soft-brick: splash screen boot loop. At that moment, I still had access to Fastboot and Recovery mode (stock recovery).
After tons of days googling, found a TWRP recovery that someone claimed that worked in GR3.
I decided to flash it using fastboot commands from my PC. Result = OK. Flashed and worked like a charm.
Tired of searching a stock/custom firmware for GR3 TAG-L23, I decided to download and flash a GR3 TAG-L22 rom using TWRP.
Result = Messed it up again... this time worst... Hard-bricked I think: the phone didn't show any light, couldn't boot it again in any mode... Dead...
The only hope I had is that it is detected by Windows for about 10 seconds as MEDIATEK USB PORT (COMxx) where xx changes when I connect it from one USB port to another.
Since then, I tried almost every tutorial/video/solution/forum/website over the internet, tried almost every SP Flash tool version from v3.1224 to v5.1628, downloaded every scatter.txt for MT6753 processor, tried changing with/without battery option in SPFT, pressing every phone buttons combos, with no luck...
I always get the same error: S_FT_ENABLE_DRAM_FAIL (0xFC0)
Downloaded and installed almost every driver I found on internet: not overwritting them... I created a Virtual Machine, and test them separately using snapshots. Result = Same DRAM_FAIL error.
last week, got another HUAWEI GR3 TAG-L23, untouched, brand new...
I did the following with the new one:
Flashed TWRP recovery using fastboot commands = OK
Rooted it using SuperSU = OK
executed tons of ADB commands that found over the internet, to dump the partition table and stock rom using dd command = OK (I think... what I got is a bunch of files - system, lk, boot, logo, cache, frp, userdata, secro, recovery, nvdata, protect1 and 2, tee1 and 2, and so on).
Using the partition table information, edited one scatter.txt file for MT6753 and, one by one, adjusted the partition info (start and lenght). I did it because when using any downloaded scatter file, and selecting the files that I got from dd commands, SPFT showed error messages saying them were wrong. After editing it and loading the files that I got from the second phone, SPFT recognized them as good ones.
But.... I'm still getting the d...mn S_FT_ENABLE_DRAM_FAIL (0xFC0) error
Also tried to get a rom backup and scatter file from the second phone using MTK DROID ROOT & TOOLS v2.5.3 with no luck: it shows all phone information (except IMEIs), a green rectangle shows up, but... a weird message appears at right: "ERROR: TotalBytesPerChunk Not Found. Set Default Page/Spare=2048/64 !!!". Then I click on "BLOCKS MAP" button, a new window appears showing the partition info (that already got using adb command prompt) and "create scatter file" button is grayed out... And if I try to perform the backup, it starts fine, but ends with error, and no file is backed up...
Let me mention that I already read and googled the totalbytesperchunk error and the grayed out button stuff and tried all alternatives too, and nothing worked.
My work environment:
PC = Laptop With 8 GB RAM / Windows 10 pro x64
Virtual Machines: Windows 7 pro 32 bits, Windows XP 32 bits, Ubuntu 32 and 64 bits...
What else can I do?
How can I use the second, rooted and working phone to get a rom/firmware working dump? it is possible?
If someone decides to help me, let me know what do you need (dumped files, downloaded scatter.txt files, screenshots, whatever you need...)
COM## is a COM port. You can use a terminal program to directly interact with the device.
You are not completely bricked yet.
I do not have any further details to help you, but I can tell you there is still hope.
Connect the dead device to PC, load up a terminal app (if on windows, just load up the app named Terminal)
See where you can get with that.
good luck
Please Help cesarr4: my TAG-L23 bricked - Need your TWRP
I have a bricked GR3 after using Kingo Root. You mention in the post:
"After tons of days googling, found a TWRP recovery that someone claimed that worked in GR3. I decided to flash it using fastboot commands from my PC. Result = OK. Flashed and worked like a charm."
Please share this TWRP recovery, please.
antonioroa said:
I have a bricked GR3 after using Kingo Root. You mention in the post:
"After tons of days googling, found a TWRP recovery that someone claimed that worked in GR3. I decided to flash it using fastboot commands from my PC. Result = OK. Flashed and worked like a charm."
Please share this TWRP recovery, please.
Click to expand...
Click to collapse
I attached the recovery I'm currently using in the second GR3. I'm still looking forward the stock rom and a way to recover the first one... have u found a way to unbrick it?
Here you can find the recovery too: http://forum.xda-developers.com/android/development/recovery-twrp-3-0-2-0-huawei-tag-l01-p8-t3433520
I have the same problem with kingroot, and cannot find TAG-L23 rom.
I sent my phone to huawei support and they said it's a board problem and need to replace, the cost is near to the phone's original price.... No way!
In clangsm web page there's a stock rom but you need to pay for vip membership.
Please help with this issue.
I'm still trying to get a working rom image from the 2nd GR3 that I bought... No luck yet... I'm plenty sure that there is no need to do hardware replacement... can anyone point me to a tool/step-by-step guide to readback and save a flashable rom image from GR3 phone, and a SP tools that works with GR3 chipset/PCB?
Hi, i have a TAG-L01 and i got the same problem, i've tried a lot with no lucky, it seems sp flash tool don't support our device(or is huawei that don't want).
If you have some ideas please tell me, i will help(our devices are exactly the same, all TAG-Lxx are the same)
Hello
I have a TAG-L23. I was able to install the TRWP recovery mentioned in previous posts. But I do need the Stock ROM, since I am not able to start the phone. It is allways rebooting. any idea where to find the ROM? maybe cesarr4 can do a backup on TWRP from his second phone and we can load it. just make a backup in the recovery and Zip it, then you may share it.
srgg01 said:
Hello
I have a TAG-L23. I was able to install the TRWP recovery mentioned in previous posts. But I do need the Stock ROM, since I am not able to start the phone. It is allways rebooting. any idea where to find the ROM? maybe cesarr4 can do a backup on TWRP from his second phone and we can load it. just make a backup in the recovery and Zip it, then you may share it.
Click to expand...
Click to collapse
Done. Where can I share it for you?
cesarr4 said:
Done. Where can I share it for you?
Click to expand...
Click to collapse
please share your ROM in google drive. i've got same problem here.
Any link to the TAG-L23 ROM? please share as I believe mine is corrupted.

Cannot find the file flash.xml

Guys
I am trying to flash my zenfone 2 with
"Intel platform flash tool"
And it is the only software that recognizes and shows that my device is connected.
But it required a "flash.xml"file for the process and I cannot find such file in my downloaded stock ROM.(after unzipping)
Please any guide
How can I flash my zenfone which has a damaged Bootloader? (So no boot options are available)
And where can I find that "flash.xml" file?
Thanks.
Istiraven said:
Guys
I am trying to flash my zenfone 2 with
"Intel platform flash tool"
And it is the only software that recognizes and shows that my device is connected.
But it required a "flash.xml"file for the process and I cannot find such file in my downloaded stock ROM.(after unzipping)
Please any guide
How can I flash my zenfone which has a damaged Bootloader? (So no boot options are available)
And where can I find that "flash.xml" file?
Thanks.
Click to expand...
Click to collapse
you need to use xFSTK to flash the bootloader. even if you use intel flash tool that also you have to use xFSTK as external tool to recover your device. unfortunately you will not get that xml file you have to write it yourself. i could write it if it was necessary. but i don't think that will have any beneficial comparing the time spent on it. go to the following guide as do step by step as recommended. keep in mind if xFSTK in unable to recover you BL. intel flash tool can not help even you write or get that flash.xml. one more tip regarding recovering device. if you r able to get the temp bootloader. do not use asus flash tool. use commands method. AFT may push you to unrecoverable state.
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Thanks but something went wrong.
Hi.
Thanks for the reply
I have performed the process in exact same way it was described.
But something went wrong,
I don't know what exactly happened.
Now my phone isn't even turning on
Or vibrating or no USB sign.
But isoc driver and xfstk is still detecting my phone as moorefield device.
I really don't know what happened.
I have tried the process at least 20-30 times
But every time its saying
"Errors encounter during FW download : Aborting"
And fail.
Please help me get rid of this

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 !

Categories

Resources