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.
Hi, my problem is with the L31,
I've trying to downgrade from Nougat to MM. I saw on the thread this steps and i followed:
"Fastboot flash boot boot.img
Fastboot flash system system.img
Fastboot flash cust cust.img (This one is in the second zip from badwolf nougat download)
Then I flashed badwolfs recovery b2 as that one lets me transfer files from pc to phone and followed instructions from htcmania from here".
The problem is that i didn't reach to downgrade and when i try to reinstall Nougat by TWRP i get this error messages:
" E: Unknow comand (errno) update_huawei-pkg_from_ota_zip: update package from zip failed"
"Updater process ended with error: 7
Error installing zip file '/external_sd/DLoad/Update.zip'
Updating partition details...
...done"
Now my phone stays freeze on the huawei logo and the flashtool doesn't even recognize my device.
Can someone help me with this matter, please?
try to flash stock recovery and do a factory reset
simo255 said:
try to flash stock recovery and do a factory reset
Click to expand...
Click to collapse
Problem solved.:good:
aalmeida1972 said:
Problem solved.:good:
Click to expand...
Click to collapse
how did you flash a stock recovery please ???
darth_us37 said:
how did you flash a stock recovery please ???
Click to expand...
Click to collapse
I followed the steps that someone advice me. Like above.
"I had to first extract the nougat firmware with huawei firmare extractor and flash everything by fastboot
Fastboot flash boot boot.img
Fastboot flash system system.img
Fastboot flash cust cust.img (This one is in the second zip from badwolf nougat download)
Booth files you can find it in this page.
http://forum.xda-developers.com/huawei-p9lite/development/android-nougat-dev-build-huawei-t3488360/page33"
To flash img. i used the file that i attached.
Good luck
so now i restored twrp , i put the update app in sd card and it doesn't want to flash , i'm still trapped in bootloop but i have access to twrp now what to do now ?
I found the old twrp is okey for downgrade,
Just put b161 update.app into sdcard/dload and press volume down + power key.
but flash badwolf's twrp will get stuck in fastboot, though It's not really bricked.
hi, maybe you also have a solution for my problem.
i installed a wrong update via sd card (dload etc.), now my phone is just black no signal nothing. and it seems like a fastboot loop always when i plug into the pc im in fastboot without doing anything
when i try to unlock the bootloader i get "failed command not allowed")
and also when i try to flash the extracted files from update.zip i get the same error ("failed command not allowed")
by the way i didnt active usb debuggin or oem unlocking
please help thank you
how can i back from LineagueOS by Mericulus to stock android 6.0?
i install C432OemInfo-DUALSIM-P9LITE from TWRP and next upload to sd/dload/ update.app VNS-L21C432B170 and i get:
Software install failed
Incompatibilty with current version. Please download the correct update package.
What i must do? :/
When i try unlock bootloader i get error: FAILED (remote: already fastboot unlocked)
Try to use B150 or B160
It ok if you get that error. Install B160 and you will be fine. Because that s the latest official firmware. Go ahead and try :d
Just putting the firmware in dload and using 3 buttons method worked for me
i unpack update.app using HuaweiUpdateExtractor_0.9.9.3 and next flash boot.img, recovery.img, cust.img, cache.img, userdata.img and system.img. Now i have emui etc. but in settings show mi:
Code:
Model: hi6250
Compilation number: VNS-C432B160
When i try flesh update.app using 3 buttons all freeze me at 5%.
Hello Guys,
I have a U Ultra with a boot problem.
Failure: It starts, show up the logo for a short time, than it shut down.
In fastboot mode the lock status is relocked. Flashing in fastboot there is no chance. Because the OEM Unlock flag in the rom is off. The recovery does nothing, same behavior as on startup...
The only way to get the phone back to life is the sideload via OTA flash zip file on a sdcard.
Problem: I don't have such a file with os 2.21.410.1, I have only a 1.64.401.10 file.
If I try this file it shows me a Version Androis-Info Error.
Where can I get such a flash file with the version 2.21.401.1 with oreo (european version)?
On the other side I try to patch the info.bin file but , the version is easy to patch but it seems so that this file has a byte in front, that changed in a unknown way and 8 bytes in the middle of the file with the same problem, this could be a file size or checksum I don't know what it is and how it will be generated. The rest of the file is filled with zeroes.
Does somebody have information about the file structure of the info.bin in the flash file?
I heared about LeeDrOiD, that he worked a long time for HTC, maybe he could help to get this phone back to life????
Phone Info:
C:\ADB>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_oceuhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1578400000
(bootloader) serialno: ************
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: ***************
(bootloader) version-main: 2.21.401.1
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PZF10000
(bootloader) cid: HTC__034
Hope someone can help me...
davii
good/bad news
hi guys,
I run thru the infos from an other post here in the forum and that I have done successfully.
https://forum.xda-developers.com/u-ultra/help/howto-unbrick-ultra-t3891033
The behaviour is now a bit different, it runs now in a boot loop, the logo has change to the normal htc logo without red text. The recovery shows a red exclamation mark, and run in the bootloop...
The main problem remains, I need a 2.21.401.1 firmware file to flash on the phone... what a m....
I can't find such a file in the internet, the exe firmaware files end up on version 1.64... and I think, this are only us version files. I need HTC__034.
Any ideas?
Is it possible to patch a lower version of a firmware rom just to get the phone running, to open the OEM unlock, and than to flash whatever? I have an twrp backup of my mobile.
The firmware.zip file from @minhnewpro in OTA, where does it come from? The OTA looks like a twrp or titanium backup file. But I can't get it in my mobile without twrp...
Were it possible to integrate the twrp.img in the firmware.zip file as recovery partion? Would it help at all without the open bootloader, can twrp write things with a locked bootloader? I'm not so firm in that matter... In my understanding of this matter it can???
davii
davi133 said:
hi guys,
I run thru the infos from an other post here in the forum and that I have done successfully.
https://forum.xda-developers.com/u-ultra/help/howto-unbrick-ultra-t3891033
The behaviour is now a bit different, it runs now in a boot loop, the logo has change to the normal htc logo without red text. The recovery shows a red exclamation mark, and run in the bootloop...
The main problem remains, I need a 2.21.401.1 firmware file to flash on the phone... what a m....
I can't find such a file in the internet, the exe firmaware files end up on version 1.64... and I think, this are only us version files. I need HTC__034.
Any ideas?
Is it possible to patch a lower version of a firmware rom just to get the phone running, to open the OEM unlock, and than to flash whatever? I have an twrp backup of my mobile.
The firmware.zip file from @minhnewpro in OTA, where does it come from? The OTA looks like a twrp or titanium backup file. But I can't get it in my mobile without twrp...
Were it possible to integrate the twrp.img in the firmware.zip file as recovery partion? Would it help at all without the open bootloader, can twrp write things with a locked bootloader? I'm not so firm in that matter... In my understanding of this matter it can???
davii
Click to expand...
Click to collapse
Well, i used to have U Ultra and now it is dead =] and i can not do anything (Hardware problem), even i tried flash RUU by CMD or SD Card.
Back to your question. Maybe you only can try to boot into DOWNLOAD MODE => Bootloader => recovery => apply ota update.zip
minhnewpro said:
Well, i used to have U Ultra and now it is dead =] and i can not do anything (Hardware problem), even i tried flash RUU by CMD or SD Card.
Back to your question. Maybe you only can try to boot into DOWNLOAD MODE => Bootloader => recovery => apply ota update.zip
Click to expand...
Click to collapse
Thx dude,
I'm already on 2.21.401.1, there is no update for 2.21.401.1 in the net, no chance to flash a stock rom... :crying:
davi133 said:
Thx dude,
I'm already on 2.21.401.1, there is no update for 2.21.401.1 in the net, no chance to flash a stock rom... :crying:
Click to expand...
Click to collapse
hey guys, I have another idea...
my wifes mobile is the same..., and that mobile is on 1.64...,
were it possible to initiate the update on 2.21..., and then it downloads the update file. Where resides this update file? Can I get this file from my wifes mobile, to flash it on my mobile?
Does anybodey know this?
In my opinion this process is the same as the RUU flash, the file must be on a special partition, I think, then the mobile goes into RUU flash mode, and the command are fired to flash this rom, thats what I think...
davii
davi133 said:
Thx dude,
I'm already on 2.21.401.1, there is no update for 2.21.401.1 in the net, no chance to flash a stock rom... :crying:
Click to expand...
Click to collapse
Try to reflash OTA.zip by using stock recovery, maybe it will works.
minhnewpro said:
Try to reflash OTA.zip by using stock recovery, maybe it will works.
Click to expand...
Click to collapse
the recovery don't comes up, it also hangs in a bootloop. Or do you mean something different?
I can go to the fastboot mode, or in the bootmode for recovery, that dosen't help, I have no OTA with 2.21.401.1, that I could flash, just a lower version (1.64.401.10), that will be rejected by the RUU flash in because of the wrong version. To change the version in the bootloader I need a open bootload and a running os with adb, all that isn't the case.
I need OTA flashable rom with the 2.21.401.1 version to run it with RUU flash, and if this works is will work, that is the next question..., I think and hope it will work...
Why does the recovery didn't comes up, maybe that is the same problem as in the boot situation, the dead boot.img or a corrupted os, I don't know the reason, my last flash was a LeDrOiD, the boot.img maybe does no fit the original boot process. On the other hand, LeDrOiD was also an Oreo rom, as I had a problem with my magisk update I put back my original boot.img from my mobile backup, and my mobile boots up normaly, then I flashed back the LeDrOiD system things and it boots up normaly and magisk was fine.
I don't know whats wrong, why the recovery was gone, why the boot.img dosen't work and so on...
where resides the recovery.img? In the same partition as the boot partition or on its own partition?
Any other ideas?
davi133 said:
the recovery don't comes up, it also hangs in a bootloop. Or do you mean something different?
I can go to the fastboot mode, or in the bootmode for recovery, that dosen't help, I have no OTA with 2.21.401.1, that I could flash, just a lower version (1.64.401.10), that will be rejected by the RUU flash in because of the wrong version. To change the version in the bootloader I need a open bootload and a running os with adb, all that isn't the case.
I need OTA flashable rom with the 2.21.401.1 version to run it with RUU flash, and if this works is will work, that is the next question..., I think and hope it will work...
Why does the recovery didn't comes up, maybe that is the same problem as in the boot situation, the dead boot.img or a corrupted os, I don't know the reason, my last flash was a LeDrOiD, the boot.img maybe does no fit the original boot process. On the other hand, LeDrOiD was also an Oreo rom, as I had a problem with my magisk update I put back my original boot.img from my mobile backup, and my mobile boots up normaly, then I flashed back the LeDrOiD system things and it boots up normaly and magisk was fine.
I don't know whats wrong, why the recovery was gone, why the boot.img dosen't work and so on...
where resides the recovery.img? In the same partition as the boot partition or on its own partition?
Any other ideas?
Click to expand...
Click to collapse
Try extract recovery from ota.zip file and flash in download mode.
minhnewpro said:
Try to reflash OTA.zip by using stock recovery, maybe it will works.
Click to expand...
Click to collapse
hey dude,
please don't be serious but have you read my starting thread?
The bootloader is locked, you can't flash anything with fastboot! The only way to flash something is over RUU flash, so I'm a bit confused about your proposals :angel:
I hope I don't missunderstand things, because you are a senior member, and I do not want to upset anyone.
There is no OTA on the mobile so that the recovery can do it's job.
Wich OTA you mean? The real OTA from HTC look like:
OZA.zip
info.bin
zip_0.zip
zip_1.zip
etc...
Your and the other OTA's look like this:
OTA.zip
[dir] META-INF
[dir] preload
contexts.bin
etc....
Your OTA's are flashable from twrp, made with (I don't know, titanium backup)
A RUU flash want me to pass a real HTC OTA with a version higher or equal to that version that is installed before...
I know, there is a possibility to extract your OTA's but what is it good for? fastboot can't flash the recovery.img because the bootloader is locked.
That's my actual understanding of this matter and that's the behavior of the mobile.
If I'm wrong with something, please let me know.
davi133
new information on my side
The recovery comes up with these special key's (wait for the red exclamation, press power + VolUp).
Ok, but the information from htc support "WIPE DATA/FACTORY RESET" leads also to no success. Everything was made fine but after reboot is the bootloop.
The new menu in the recovery offers me to flash a real OTA from a ADB process or a SDcard, hmm, ok there is controled way now for doing this but I tryed all may real OTA's without success, because of the lower version or false cid's.
I asked the support for an actual OTA update file, but I dont think that they will give me that file.
The ADB process is a very restricted version of ADB, that mean's you can't get a shell or something like that, just the sideload and print some variables...
Is it possible to extract the real OTA, change something, and repack it?
davi133
davi133 said:
The recovery comes up with these special key's (wait for the red exclamation, press power + VolUp).
Ok, but the information from htc support "WIPE DATA/FACTORY RESET" leads also to no success. Everything was made fine but after reboot is the bootloop.
The new menu in the recovery offers me to flash a real OTA from a ADB process or a SDcard, hmm, ok there is controled way now for doing this but I tryed all may real OTA's without success, because of the lower version or false cid's.
I asked the support for an actual OTA update file, but I dont think that they will give me that file.
The ADB process is a very restricted version of ADB, that mean's you can't get a shell or something like that, just the sideload and print some variables...
Is it possible to extract the real OTA, change something, and repack it?
davi133
Click to expand...
Click to collapse
Hi Davi,
check this out (don't ask me what i had to do to get it... ):
2PZFIMG_OCEAN_NOT[email protected]80307_63.34_release_522808_signed_2_4
Rename the file to "2PZFIMG.zip" and place it in root of sdcard. Boot into download mode and confirm flash with volume+ button
thank you
Siluxsept said:
Hi Davi,
check this out (don't ask me what i had to do to get it... ):
2PZFIMG_OCEAN_NOT[email protected]80307_63.34_release_522808_signed_2_4
Rename the file to "2PZFIMG.zip" and place it in root of sdcard. Boot into download mode and confirm flash with volume+ button
Click to expand...
Click to collapse
been waiting for this firmware also..i will try this hope everything works
update
the flashing was succesfull on my htc ultra and its works..hope this can help also the op..
Siluxsept said:
Hi Davi,
check this out (don't ask me what i had to do to get it... ):
2PZFIMG_OCEAN_NOT[email protected]80307_63.34_release_522808_signed_2_4
Rename the file to "2PZFIMG.zip" and place it in root of sdcard. Boot into download mode and confirm flash with volume+ button
Click to expand...
Click to collapse
Thanks for this