Related
Okay my freind and i tried to root this g4 and a internet user told me that this method also works for normal g4's. But now we have a brick, when we're starting the device it says:
ERROR: Failed to pass validation, backup to fastboot
Failed to vertify hab image boot
failed to validate boot image.
We're now downling a stock firmware, the name is: XT1622_ATHENE-TESCO_MPJ24.139-23.4_cid50_subsidy-TESCOEU_CFC.xml.zip
I don't know if it's the right, but bootloader says athene_13mp XT1622b and ATHENE_EMEA_DSDS_CUST
Is this the right one? How can we recover it when it's the wrong?
Can anybody help us?
Solve
Hi! I had the same problem , and recently I managed to solve it. for me I just installed a different rom stock (not official ) and the problem was solved!
Downloads: Rom for XT1640, XT1626 and XT1641 (Torrent) : https://drive.google.com/file/d/0Byb_8WkC6g1XV053N2hXNkpnOWM/view?pageId=106752732436593453453
if this rom not work, try this : http://forum.xda-developers.com/moto-g4/development/stock-moto-g4-marshmallow-6-0-1-stock-t3382999
and the commands, if you dont know: https://drive.google.com/open?id=0B_WcFxq0JJ-ESlYyMWpNTWU0WVE
Both of they worked for me (Yeah i tested the both).
Dont forget that this erases your celphone data.
einhuman197 said:
Okay my freind and i tried to root this g4 and a internet user told me that this method also works for normal g4's. But now we have a brick, when we're starting the device it says:
ERROR: Failed to pass validation, backup to fastboot
Failed to vertify hab image boot
failed to validate boot image.
We're now downling a stock firmware, the name is: XT1622_ATHENE-TESCO_MPJ24.139-23.4_cid50_subsidy-TESCOEU_CFC.xml.zip
I don't know if it's the right, but bootloader says athene_13mp XT1622b and ATHENE_EMEA_DSDS_CUST
Is this the right one? How can we recover it when it's the wrong?
Can anybody help us?
Click to expand...
Click to collapse
tell about your situation detailed. what method did you try to root the phone? did you unlock the bootloader first? which version of supersu did you flash? did you flash recovery first and is it working?..... in any case, unlocking the bootloader and flashing the twrp/cwm recovery followed by stock firmware flash should help. provide more details.
Droid Turbo XT1254 Marshmallow->Lollipop downgrade (unlocking bootloader)COMING SOON?
*this is new thread because I started last as Q&A by mistake so first 2 pages may look off with posts and answers.
DOWNGRADING EXPERIMENT TOPIC
So as you may know , after upgrading to Marshmallow OTA, on locked bootloader there won't be any option to unlock bootloader (ever as some people say) , sunshine officially doens't support Marshmallow. The only option is to downgrade which again isn't possible on locked BL..
Or is it ?
Introduction - skip to DOWNGRADE
First of all I'm not an programmer , but have some experience with locked down motorola's bl's , firmware's ,downgrades and so on..
I'm sure when somebody says impossible, it doesn't really mean impossible, but rather not worthy to some. So in my case I bought the phone few days ago, wasn't fully up to date with infos on unlocking BL so didn't check FW version when buying , just after I checked and phone was updated on MM 1-2 days before buying it. On not unlockable BL phone will become useless to me very soon, while unlocked I would plan to have it for long period of time. It goes in Verzion's favour for me to ditch the phone and buy a new one except I'm not in USA , there are no Verzion services in my country and if there were I would never ever buy (again) anything from Verzion. Well I lived in Japan , and there is network Softbank which is well.. Imagine Verizon but on steroids when it comes to tying people down, locked bootloaders and software, insane fee's and so on.. Well that Softbank bough Verizon some time ago .. I was avoiding them at all cost, but on to the topic now.
DOWNGRADE - fastboot
I would like to invite everybody who is interested in this and who can help to participate in this. Every programmer that has time and can contribute would be greatly appreciated! In return I'm willing to sacrifice my phone and my time , even paying some reasonable donations.
While experimenting in the end I was able to flash all bootloader files from various different versions including all partitions related to it which gets upgraded. Even managed to flash XT1250 MM bootloader. Bootloader version DOES change in bootloader / fastboot ,But it doesn't mean ANYTHING. While downgrading , something else, possibly other parts of bootloader obviously search for match and there is more to it than simple bootloader , more experienced , chime on in here! SElinux enforcing? Verity?
(see attachments)
SU4TL-49 bootloader.img to motoboot flash - Successfully
SU4TL-49 manually flashing 1 by 1:
tz.mbn -[/B] Successfully
SBL1.mbn (bootloader) - [/B] Successfully
sdi.mbn - [/B] Successfully
fsg.mbn to mdm1m9kefs3 - [/B] Successfully
rpm.mbn - [/B] Successfully
emmc_appsboot.mbn to aboot - [/B] Successfully
gpt.bin to "partition" , it's the partitions info partition, people say it can't be downgraded or flashed cross versions. After some experimenting mfastboot failed but fastboot succeded, on some versions mfastboot worked - [/B] Successfully
What I can't get to downgrade / cross flash no mather which bootloader and combinations of firmware im on :
boot.img
recovery.img
system,img (sparse_chunk files)
I will go deeper, but hope that new full firmware SBF will be released soon in case of brick. Verzion is slow. I'm making my own full 6.0.1 xml.zip based on full flashable zip's , repacked system.img sparsechunks, rewrited the script but can't get to flash system files due to invalid signed image. Any help with that? It would also help already bricked guys because who knows when'll Verzion release it..
Downgrade OTA way , stock Android Recovery
While stock android recovery is pretty much useless, it can do software upgrades OTA on a fully stock system , which we on locked bootloaders and MM have.
In my opinion , the way is to trick stock recovery into thinking it's flashing ota, and that whole envieroment is like recovery is expecting it while it's actually flashing downgraded version full / close to full firmware in combination with you flashing some partitions manually through fastboot. OTA's contain only "patch" and just replaces files which get changed on new SW. Or even maybe reverse OTA downgrade?
I've made my own update.zip and signed it , but so far get footer size is wrong error so can't flash it .. Need more help here too..
That looks promising!
Marshmallow feels slower than lollipop for me and I wish I could downgrade but I just can't!
I am looking forward to see what you can do about this issue
Good luck bro!
sorry for my mistake, I do not intend to comment here
@EjđiSixo
How to remove the "signed" of system image or bypass it? Fastboot or RSD are stuck at flashing system image. Does this "sign" relate to boot, recovery, partition? Or it's simply the "sign" to prevent downgrade???
I've never succeeded with partition downgrade...
---------- Post added at 10:29 PM ---------- Previous post was at 10:19 PM ----------
when I was flashing the only system.img (3GB), it said that "wrong at header magi". But after a bit time, fastboot separated the file and began to flash. But still failed because of signed image.
I've tried to remove the code from updater-script but it could not write files to system
Not out yet!
Thanks! I think if we all try , we can do it ! For now main focus is downgrading anyhow, even to half working Lollipop just in the purpose of unlocking bootloader with sunshine.
@mr_5kool
Feel free to comment and ask / suggest, thats what this topic is for!
Unforutenately thats the part I haven't yet figured out myself. It is a " permissions" to prevent the downgrade , bootloader and possibly something else checks current version / keys / properly signed image and then flashes. With other bootloader I'm still not able to flash it because it's obviously locked. Motorola probably signs their images differently.
You can't flash 3GB image because when flashing, phone recieve's partition first to ram so max download size is set to 255mb per file. You have to repack system.img to sparse chunks. But you don't have to bother with it , I already repacked system.img which I found at fully stock flashable MCG24.251-5 . It again failed due to invalid signed image . If we could figure out what is exactly signed and how , that would open a lot more possibilities. Possibly even flashing prerooted roms on locked bootloader. There are more possibilities , who knows..
Currently the only thing notices downgrade when flashing is recovery. In bootloader log says I tried to downgrade. Even with downgraded bootloader (kind of, there is sbl2 and sbl3 but they don't get upgraded )
Anyway, I tried something just for the "gags" . Flashed all partitions of XT1250 bootloader. Got to Motorola's site, posted "unlock bootloader data". It returned it's not unlockable of course.. The first sequence of numbers in data is your imei , it starts with 99 and it's verzion's specific imei.
My theory is that motorola ties unlock bootloader data to every phone and imei and stores it in database ( please confirm) . So even with moto maxx bootloader I can't unlock because :
1 it reads my verzion imei
2 it doesn't find alltogether data in the database..
I don't know what are other numbers in the data you get from fastboot, possibly some serial numbers and so on, haven't really checked it .. That's why i think this method is not possible at all for now. Manipulating that data in your phone and running it through motorola's site knowing that exact same code works for some device might be possible, but I think there is really way too much impossible messing involved. If somebody can share more about this?
lol
http://forum.xda-developers.com/dro...ficial-marshmallow-build-mcg24-t3512813/page2
I've renamed it like suggested in the post #11
Download link is at 1st page. It's just a OTA.
Yes I just renamed it.
IT DOESN'T WORK WITH ADB AND YOU CAN'T FLASH IT AGAIN THROUGH RECOVERY. ITS OTA.
EDIT: The post that I was responding to has been removed.
The method to downgrade from Lollipop to Kitkat is the same with what I've done. It may be possible. Some said that "impossible to downgrade with locked bootloader on vrz". So the system image may be signed with bootloader (or imei, serial or something else, god know).
The unlock method of Sunshine takes place in Trustzone (sbl2). They cannot get unlock code.
You succesfully downgraded LL to KK on droid? There is partition for trust zone alone "tz.mbn" , downgradable without any problem. I only see sbl1 get's upgraded on droid turbo , never saw in any firmware sbl2 or 3 yet.. So I'm little confused.. I remember I saw some PDF regarding that..
Yes, successfully downgraded 5.1 to 4.4.4 on Droid Turbo but with unlocked bootloader. I helped this guy.
http://forum.xda-developers.com/droid-turbo/help/solved-problem-downgrade-install-ota-t3497791
http://forum.xda-developers.com/droid-turbo/help/how-to-downgrade-lollipop-5-1-to-kitkat-t3494459
Finally managed to *Brick my devices while trying to make latest sbf firmware (what an irony ) because used some of files from that stupid OTA . Tried flashing all possible firmware I have but it doesn't fix it so system got corrupted probably and for now didn't succed flashing any of the available systems. Flashing MM recovery doesn't help. It's a " recovery loop".
Basically phone starts , vibrates , goes into recovery, it says "erasing" , it does the factory reset then restarts and over and over again erasing restarting loop.
I'll continue exploring downgrade options but top priority now is making working marshmallow sbf or waiting for stupid Verzion to release it already. Just checked with SUA and it still doesn't show repair so firmware isn't available still.
Biggest problem is signed system images which are probably signed by RSA and I need help with that..
I have same problem erasing
Can't flash SU4TL gpt.bin anymore , so success was definitely connected to experiment and steps I did so I'll investigate more.
@EjđiSixo
I have never tried before. My Moto X2013 failed to downgrade from LL to KK, too. So, it's the common problem of Verizon Motorola Devices.
If you have problem with "erasing", just enter recovery by "hold power button for a while then fast press volume up button". Phone will enter recovery and do the factory reset. But when rebooting the system, "erasing" appear again.
If partition is dead, flash the higher version, commonly gpt and tz.
PS: still waiting for the official xml firmware
ChazzMatt said:
Yes, successfully downgraded 5.1 to 4.4.4 on Droid Turbo but with unlocked bootloader. I helped this guy.
http://forum.xda-developers.com/droid-turbo/help/solved-problem-downgrade-install-ota-t3497791
http://forum.xda-developers.com/droid-turbo/help/how-to-downgrade-lollipop-5-1-to-kitkat-t3494459
side note, I hate this Q&A format. Not sure why XDA even has it. You can't even format URL links correctly.
Click to expand...
Click to collapse
mr_5kool said:
@EjđiSixo
I have never tried before. My Moto X2013 failed to downgrade from LL to KK, too. So, it's the common problem of Verizon Motorola Devices.
If you have problem with "erasing", just enter recovery by "hold power button for a while then fast press volume up button". Phone will enter recovery and do the factory reset. But when rebooting the system, "erasing" appear again.
If partition is dead, flash the higher version, commonly gpt and tz.
PS: still waiting for the official xml firmware
Click to expand...
Click to collapse
I wonder if there is any way to force Verizon to release firmware. This is really low of the lowest, it says 1 week after OTA , now it's almost 1 month. Until somebody forces them , it can be months as far as they are considered. No help from developers / programmers either on any of 2 subjects so don't see my method of full MM SBF working.
god know
:v
ChazzMatt said:
Yes, successfully downgraded 5.1 to 4.4.4 on Droid Turbo but with unlocked bootloader. I helped this guy.
http://forum.xda-developers.com/droid-turbo/help/solved-problem-downgrade-install-ota-t3497791
http://forum.xda-developers.com/droid-turbo/help/how-to-downgrade-lollipop-5-1-to-kitkat-t3494459
Click to expand...
Click to collapse
Exactly brother .
I solved my problem .
I can downgrade from Marshmallow to lollipop is very easy for my ..
But first step is unlocked bootloader from lollipop..
Sent from my XT1254 using XDA Free mobile app
Yeah people , we all know everything can be done with unlocked bootloader. It's a GOD mode. Nothing strange about downgrading with unlocked BL. This topic is for people stuck on locked BL like myself to try to odowngrade on lollipop only in purpose of UNLOCKING BL. So let's for now focus on locked BL's.
Hi guys
My phone has a little problem: after being failed on flashing fw, everytime I power on the phone (after completely power off), it starts at bootloader screen. I have to press power to get it on. I asked several people and they said that there was s fastboot command could fix this. Does anyone know this command please tell me. Thanks guys!!!!
You can see the reason why it's doing by parsing the output of "fastboot getvar all" and looking at the "(bootloader) reason:xxxx" entry, but we know what it is already...
fastboot oem fb_mode_clear
and you should be good to go.
Surprised this was hard to find, seems like it asked and answered several times a week in the various Moto device sections, probably about once a week here.
Thanks acejavelin
And I'm really sorry
It's a bit hard to find the keywords
And I have several more questions:
1. there 2 file xml in a fw: flashfile and serviceflash
Which file is used to fully flash system? What are the differences between them?
2. I cannot flash rom dual sim or 6.0.1 reteu to my 6.0 retasia XT1572 (via rsd). It shows "failed" at gpt, boot, recovery or system. Is this a problem of locked bootloader?
Thankssss
mr_5kool said:
Thanks acejavelin
And I'm really sorry
It's a bit hard to find the keywords
And I have several more questions:
1. there 2 file xml in a fw: flashfile and serviceflash
Which file is used to fully flash system? What are the differences between them?
2. I cannot flash rom dual sim or 6.0.1 reteu to my 6.0 retasia XT1572 (via rsd). It shows "failed" at gpt, boot, recovery or system. Is this a problem of locked bootloader?
Thankssss
Click to expand...
Click to collapse
1. You can open/view each .xml file in any text editor to compare,
/I suggest to use fastboot and cmd/
2. Dual sim RetLA hasn't all bands you need in Asia, reteu - only single sim.
2.a With locked BL you can only flash the same or upper version of system(retasia).
mr_5kool said:
Thanks acejavelin
And I'm really sorry
It's a bit hard to find the keywords
And I have several more questions:
1. there 2 file xml in a fw: flashfile and serviceflash
Which file is used to fully flash system? What are the differences between them?
2. I cannot flash rom dual sim or 6.0.1 reteu to my 6.0 retasia XT1572 (via rsd). It shows "failed" at gpt, boot, recovery or system. Is this a problem of locked bootloader?
Thankssss
Click to expand...
Click to collapse
No, you can't flash reteu factory images to retasia at all, it won't let you, at least not bootloader or gpt.bin (partition table)... Your bootloader state is not relevant, our unlocked bootloader is like HTC (some things are still checked/protected) not like Nexus.
Flashfile.xml is the one to look at, they are all fastboot commands, if you look at any Moto Style factory flashing instructions, then compare it to the contents of flashfile.xml, the process should be fairly explanatory. Look in my signature for a return to stock thread and read the first post carefully.
Guys
I successfully flashed RETEU 6.0.1 to my RETASIA 6.0 via RSD:
1. I flashed the RETASIA dual sim (6.0). It wasn't a successful flash. The modem has been failed to flash. The system failed to start. It stopped at logo.
2. Then, I flashed RETEU 6.0.1 to it, it started with RETEU 6.0.1 system
I've tried this method to another XT1572 RETASIA (and other PC too) but RSD show failed at boot, recovery, and also system.
This makes me wonder...
mr_5kool said:
Guys
I successfully flashed RETEU 6.0.1 to my RETASIA 6.0 via RSD:
1. I flashed the RETASIA dual sim (6.0). It wasn't a successful flash. The modem has been failed to flash. The system failed to start. It stopped at logo.
2. Then, I flashed RETEU 6.0.1 to it, it started with RETEU 6.0.1 system
I've tried this method to another XT1572 RETASIA (and other PC too) but RSD show failed at boot, recovery, and also system.
This makes me wonder...
Click to expand...
Click to collapse
???
Downgrade(6.0.16.0) cannot be done with locked BL.
Also cannot be done with flashing BL & GPT. So cannot be done with RSD - only with fastboot & command line.
What do you want to achieve? RetEu 6.0.1. will work good(all bands) for you. But single sim.
Maybe this one you can flash:
XT1572_CLARK_RETASIA_DS_6.0.1_MPHS24.107-58-5_cid7_subsidy-DEFAULT_CFC.xml.zip
https://firmware.center/firmware/Motorola/Moto X Style/Stock/XT1572/
dzidexx said:
???
Downgrade(6.0.16.0) cannot be done with locked BL.
Also cannot be done with flashing BL & GPT. So cannot be done with RSD - only with fastboot & command line.
What do you want to achieve? RetEu 6.0.1. will work good(all bands) for you. But single sim.
Click to expand...
Click to collapse
It's not downgrade, because RETASIA single or dual sim are 6.0
RETEU is 6.0.1
I used 2 update.zip to optain Nougat then
dzidexx said:
Maybe this one you can flash:
XT1572_CLARK_RETASIA_DS_6.0.1_MPHS24.107-58-5_cid7_subsidy-DEFAULT_CFC.xml.zip
https://firmware.center/firmware/Motorola/Moto X Style/Stock/XT1572/
Click to expand...
Click to collapse
I cannot flash this version to my friend's phone (via RSD)
I don't know why
The problem here is: another guy had flashed RETLA 6.0.1 dual sim to his RETASIA 6.0 single sim. The fw had been flashed but the phone was softbrick. He had to flash RETEU 6.0.1 then. And now, he's having Nougat. The bootloader has not been unlocked (said him) and he did flash via RSD
If you flashed reteu 6.0.1 - any 6.0 is downgrade.
Without Bootloader and gpt you can try to do it(unlocked BL of course).
With fastboot not rsd.
@mr_5kool
---------- Post added at 01:01 PM ---------- Previous post was at 12:38 PM ----------
mr_5kool said:
The problem here is: another guy had flashed RETLA 6.0.1 dual sim to his RETASIA 6.0 single sim. The fw had been flashed but the phone was softbrick. He had to flash RETEU 6.0.1 then. And now, he's having Nougat. The bootloader has not been unlocked (said him) and he did flash via RSD
Click to expand...
Click to collapse
All these succesfull steps were "upgrade".
dzidexx said:
If you flashed reteu 6.0.1 - any 6.0 is downgrade.
Without Bootloader and gpt you can try to do it(unlocked BL of course).
With fastboot not rsd.
@mr_5kool
---------- Post added at 01:01 PM ---------- Previous post was at 12:38 PM ----------
All these succesfull steps were "upgrade".
Click to expand...
Click to collapse
I see
But this failed on another phone
Maybe his phone's bootloader has not been unlocked yet
acejavelin said:
No, you can't flash reteu factory images to retasia at all, it won't let you, at least not bootloader or gpt.bin (partition table)... Your bootloader state is not relevant, our unlocked bootloader is like HTC (some things are still checked/protected) not like Nexus.
Flashfile.xml is the one to look at, they are all fastboot commands, if you look at any Moto Style factory flashing instructions, then compare it to the contents of flashfile.xml, the process should be fairly explanatory. Look in my signature for a return to stock thread and read the first post carefully.
Click to expand...
Click to collapse
I've just taken a look at ROM's XMLs. The difference between flashfile and serviceflash is subsidy: slcf_rev_d_default_v1.0.nvm
Flashfile has this line: <subsidy_lock_config MD5="d41d8cd98f00b204e9800998ecf8427e" name="slcf_rev_d_default_v1.0.nvm"/>
mr_5kool said:
I've just taken a look at ROM's XMLs. The difference between flashfile and serviceflash is subsidy: slcf_rev_d_default_v1.0.nvm
Flashfile has this line: <subsidy_lock_config MD5="d41d8cd98f00b204e9800998ecf8427e" name="slcf_rev_d_default_v1.0.nvm"/>
Click to expand...
Click to collapse
Flashfile is a complete flash... Servicefile does not erase data (an upgrade).
This is my first time posting on XDA, so sorry if the formatting is bad.
I've tried to root my P9 lite installing TWRP and Magisk, everything went fine, until the last reboot that caused a bootloop.
Trying to fix this I mistakenly wiped the System partition (instead of Data), reading online people adviced to flash the update.zip, when i tried it I had "unable to mount /vendor" and "unable to mount /product".
I tried the update.app method and the eRecovery tool, but still nothing.
I read that the problem was probably caused by en error in boot.img or recovery.img, so i extracted those files from the firmware and flashed them using TWRP. By doing so i deleted TWRP itself leaving me unable to flash system.img.
I tried to flash it using fastboot, but every time i try to write a command regarding flashing i get a FAILED (remote: command not allowed).
Now i have a bricked phone, i can access fastboot but it doesnt seem to be working. I cant access adb since i can't access the recovery (at least i dont know how to ).
Any advices?
Do you have bootloader unlock code?
Dino_S said:
Do you have bootloader unlock code?
Click to expand...
Click to collapse
Yes I do.
Unlock bootloader again and in fastboot flash system.img and boot from firmware,I used b370
---------- Post added at 12:46 AM ---------- Previous post was at 12:38 AM ----------
Extract from update.zip file update.app and use huawei update extractor and extract files from that system.img and boot.img and put in fastboot folder and flash it
Dino_S said:
Unlock bootloader again and in fastboot flash system.img and boot from firmware,I used b370
---------- Post added at 12:46 AM ---------- Previous post was at 12:38 AM ----------
Extract from update.zip file update.app and use huawei update extractor and extract files from that system.img and boot.img and put in fastboot folder and flash it
Click to expand...
Click to collapse
I can't, whenever I try using a fastboot command I get "FAILED (remote: command not allowed)
How much is internal data memory in twrp
Dino_S said:
How much is internal data memory in twrp
Click to expand...
Click to collapse
Around 10 gb, by the way I can't access twrp anymore, since I flashed recovery.img
TinkyWinkyJr said:
Around 10 gb, by the way I can't access twrp anymore, since I flashed recovery.img
Click to expand...
Click to collapse
It is showing in fastboot mode unlocked both
Dino_S said:
It is showing in fastboot mode unlocked both
Click to expand...
Click to collapse
Bootloader unlocked and FPR locked (or is it FRP?)
I have same prob yesterday,and showing me same thing,but i flashed twrp again and format data and system to ext4,and from fastboot flash system and boot img and it booted,it is confusing to undestand yours problem
---------- Post added at 01:15 AM ---------- Previous post was at 01:14 AM ----------
TinkyWinkyJr said:
Bootloader unlocked and FPR locked (or is it FRP?)
Click to expand...
Click to collapse
Mine showing FRP unlocked
hey guys
i have the same problem, had rr marshmallow on my p9 lite and tried to flash the new recovery for nougat by old droid. since then i cant enter nowhere without fastboot. phone unlocked and frp unlocked. does anybody have another idea. flashing stock recovery did not work, flashing twrp did also not work. need more ideas, erecovery and dload method do not work, i have acces to fastboot
Try to flash the correct oem.info.I've had the same problem with my P9(EVA-L09).
Post removed
If You have H870 use >>>THIS FIRMWARE<<<, and >>>THIS TUTORIAL<<< to flash phone. After that just boot Your phone to Fastboot and use command 'fastboot oem lock'. It's gonna lock your bootloader and wipe phone memory. Remember to flash phone with stock firmware from first link before relocking bootloader. Otherwise it ain't gonna work or You can even brick Your phone.
I have lock before flash.
I think i have brick the phone...
Told you... FIRST FLASH, THEN LOCK
---------- Post added at 14:15 ---------- Previous post was at 14:15 ----------
Can You boot download mode?
Yes but red message.
Please check "Enable oem unlock" un développement option.
evilpacer said:
Yes but red message.
Please check "Enable oem unlock" un développement option.
Click to expand...
Click to collapse
You still should be able to flash stock firmware with locked bootloader. What model exactly You got?
I have the h870
It's very hard to go in download mode.
10 try for 1 success.
So if You can boot into download mode, try to flash stock firmware. You can use one from the link I provided. If You wont be able to flash it, probably it's a memory hardware problem.
OK thanks i try it to night.
I am lock with this error.
I'm pretty sure that it happens because You're trying to downgrade from Pie to Oreo. Use >>>Z3x<<< to downgrade or flash V29a.
Chamelleon said:
I'm pretty sure that it happens because You're trying to downgrade from Pie to Oreo. Use >>>Z3x<<< to downgrade or flash V29a.
Click to expand...
Click to collapse
Yes i try to downgrade pie to oreo.
I try your tool i can't find the good way to flash or downgrade.
UNLOCK
Mode: Emergency
Model: H870
Elapsed: 1 secs. --> (v9.5)
Not supported in this mode!
Flash
Mode: Emergency
Model: H870
Elapsed: 1 secs. --> (v9.5)
Phone mode is DOWNLOAD
Start flashing.
LAF: 00000001
Laf cmd error: invalid LAF protocol.
Flashing error.
Elapsed: 0 secs. --> (v9.5)
Check 29a thread, someone posted something about uppercut there, but I'm not familiar with this method.
I fix It thank you for your help @Chamelleon
I use https://drive.google.com/open?id=1swf_HDSrWKDxerYNYOjWQ66ZEPTCi9hS
and https://drive.google.com/open?id=1tEgipU7D2kNBmSltb1QWfQ4E5i5qHtOQ
After that the phone boot and i downgrade it.