work in progress! (not working yet)
Current status: does not work (but should!), exact reason unknown (to me).
If you managed to "brick" your MOTO Z Play it enters a fail-safe mode as a last resort provided by the chipset manufacturer (Qualcomm). There are packages out there called "blank-flash" that use this mode to restore a proper bootloader that in turn re-enables the use of the fastboot method to write the other flash files and restore full operation - provided the personalized partitions are still present and in good health (or you have a backup of them at hand).
Look at this thread and download the Nougat file. It contains "blank-flash" files. These "should work" but they don't (any more). As I don't have a Z Play, I cannot research the matter myself and instructing helpful others via email exchange is ... complicated.
The thing with failing updates/flash packages is that they usually fail because they do not allow downgrading - even if they allow downgrading of some sort (e.g. OS), they may limit downgrading the second stage bootloader, the signed GPT (partitioning table) etc. As I don't know if and what's the case with the Z Play, I just assumed that *if* it works, it may require the most recent files.
If you run the blank-flash files (qboot) with --debug=2 option you see that after the programmer code is sent to the phone it doesn't send a valid / expected response and ultimately causes the process to fail.
There are many programmer files out there. Most do not work, because they need to be digitally signed with the proper keys. Some are signed with Quallcomm-keys, some with Lenovo-, Motorola- and other with test-keys. And then again, they have to fit with the qboot program that's sending the data to be flashed.
A blankflash archive consists of the following files:
qboot, blank-flash.sh ; Linux
qboot.exe, qboot.dll, blank-flash.bat ; Windows
singleimage.bin ; Both
There are different versions of the qboot program. I've found the versions 2.4, 3.37 and 3.40.
The file "singleimage.bin" contains the flash files and directions crammed into a single file, thus the name:
cmnlib.mbn
cmnlib64.mbn
devcfg.mbn
emmc_appsboot.mbn
gpt_main0.bin
index.xml
keymaster.mbn
programmer.mbn
prov.mbn
rpm.mbn
sbl1.mbn
singleimage.default.xml
singleimage.pkg.xml
tz.mbn
The XML files contain the instructions (the 'recipe'):
index.xml:
Code:
<?xml version="1.0"?>
<index>
<board id="70" name="MSM8953" storage.type="eMMC"/>
<package compatible="cpu.name:MSM8953 protocol:qboot" filename="singleimage.pkg.xml"/>
</index>
singleimage.pkg.xml:
Code:
<?xml version="1.0"?>
<package>
<programmer filename="programmer.mbn"/>
<recipe filename="singleimage.default.xml"/>
</package>
singleimage.default.xml:
Code:
<?xml version="1.0" ?>
<recipe>
<configure MemoryName="eMMC"/>
<!-- Flash GPT -->
<print what="Flashing GPT..."/>
<flash partition="partition:0" filename="gpt_main0.bin" verbose="true"/>
<print what="Re-initializing storage..."/>
<storage operation="reinit"/>
<!-- Flash bootloader -->
<print what="Flashing bootloader..."/>
<flash partition="aboot" verbose="true" filename="emmc_appsboot.mbn"/>
<flash partition="rpm" verbose="true" filename="rpm.mbn"/>
<flash partition="tz" verbose="true" filename="tz.mbn"/>
<flash partition="devcfg" verbose="true" filename="devcfg.mbn"/>
<flash partition="cmnlib" verbose="true" filename="cmnlib.mbn"/>
<flash partition="cmnlib64" verbose="true" filename="cmnlib64.mbn"/>
<flash partition="keymaster" verbose="true" filename="keymaster.mbn"/>
<flash partition="prov" verbose="true" filename="prov.mbn"/>
<flash partition="sbl1" verbose="true" filename="sbl1.mbn"/>
</recipe>
These files usually do not need to be modified.
programmer.mbn is the flash application that is sent to the phone.
I've compiled the following package, including all the qboot executables:
http://frickelbude.net/moto/blankflash[addison][D61DC5C7][25.211.10][1.07][2017-04-13].zip
D61DC5C7: crc32-checksum of programmer.mbn file (original, motorola signed) (find others here)
25.211.10: firmare package origin of the bootloader files
1.07: bootloader version
2017-04-13: time stamp of bootloader file
This didn't work with recently bricked Z Play phones as some testers confirmed. We also tried all the different programmer executables linked above just to be sure but no luck.
Outlook: you may want to try out Qualcomms QFIL (part of QPST package) (look e.g. at the download section of androidbrick).
However, that requires some handywork - you need to build some XML files, provide the proper programmer file etc. Maybe grab a firmware package e.g. for a Xiaomi phone that has all these files and try and deduce a proper layout for your Z play... and hope, any of the programmer files will actually run and communicate with the pc end.
(Usually the blank-flash files operate in 'sahara' mode/protocol and send the programmer.mbn to the phone. Then it waits for a positive response from the phone to enter 'firehose' mode in order to send all the flash data...)
/update 2017-06-10 a
I've created a blank-flash package based on the files @lozada81 linked below:
bootloader files extracted from: OTA tester Android 7.1.1 BRASIL patch june - Blur_Version.26.1.22.addison.retail.en.US.zip
blank-flash package: http://frickelbude.net/moto/blankflash[addison][D61DC5C7][26.1.22][C1.12][2017-05-22].zip
(Bootloader version: C1.12, GPT layout version: 0x000A)
/update 2017-06-10 b
Same package as above, but with a different programmer.mbn, taken from an older blank-flash package that came with an Android 6.0.1 package @lozada81 linked below.
http://frickelbude.net/moto/blankflash[addison][C0A0D740][26.1.22][C1.12][2017-05-22].zip
Well, it either fails with the infamous io-error or it finally works.. please test & report back!
Thanks OP for putting this together. I hope someone can help get what we need (someone smarter than me ). I've had to go back to my Nexus 6P, but the battery life is just horrid. I ended up ordering another Moto Z Play online. This time I'm going to keep the bootloader locked, keep the stock software, etc. I might be done with the rooting/flashing part of my life.
Moto Z Play Brick
Good afternoon.
I am from Brazil and I have a Moto Z Play XT1635-02 and downgraded from Android 7 to 6 and until then, I did the bootloader, root and installed TWRP and followed dowgrade procedures.
The problem happened after the downgrade removed the root I reinstalled the original recovery and downloaded through the mobile the update of the android January 7 via ota and after downloading began the installation and when restarting the cell phone he died and did not call any more and when connecting On the computer only the message in the device manager "Qualcomm HS-USB QDLoader 9008" no solution for now to resuscitate the device?
If someone has the solution and can help, thank you.
giba_11 said:
Good afternoon.
I am from Brazil and I have a Moto Z Play XT1635-02 and downgraded from Android 7 to 6 and until then, I did the bootloader, root and installed TWRP and followed dowgrade procedures.
The problem happened after the downgrade removed the root I reinstalled the original recovery and downloaded through the mobile the update of the android January 7 via ota and after downloading began the installation and when restarting the cell phone he died and did not call any more and when connecting On the computer only the message in the device manager "Qualcomm HS-USB QDLoader 9008" no solution for now to resuscitate the device?
If someone has the solution and can help, thank you.
Click to expand...
Click to collapse
Same with my case
Definitely going to be watching this thread. Thank you.
Sent from my SM-G955U using Tapatalk
AC
I also have my Z play stopped = (
Thanks for putting those info together, keep fingers crossed
Sent from my XT1650 using Tapatalk
Fingers crossed! Same thing with me!
I have this problem too, I'm refreshing that lenovo russian forum every 5 minutes, I'm desperate!
firmware android 7.0 update abril - compilation version NPNS25.137-24-1-9
https://www.androidfilehost.com/?fid=961840155545567726
OTA Blur_Version.25.231.4.addison.retail.en.US brasil patch may
http://motorola.erfanabdi.ir/index.....25.211.10.addison.retail.en.US&carrier=retbr
OTA tester Android 7.1.1 BRASIL patch june - Blur_Version.26.1.22.addison.retail.en.US.zip
https://drive.google.com/file/d/0B-9vIY9eZnVqY3BGM0NUdTdsclE/view
I hope util
lozada81 said:
OTA tester Android 7.1.1 BRASIL patch june - Blur_Version.26.1.22.addison.retail.en.US.zip
https://drive.google.com/file/d/0B-9vIY9eZnVqY3BGM0NUdTdsclE/view
Click to expand...
Click to collapse
I've compiled a new blank-flash package in case anyone would like to try it out (see update in 1st post).
However, I doubt it will work better than the other files. If it keeps on failing with:
Code:
FAILED: qb_flash_singleimage()->sahara_download()->IO error
then there's still something wrong with the communication between qboot and the programmer file. I.e. we would need a programmer file that works with more recent bootloader revisions.
(I assume that the blank-flash packages out there did actually work at some time in the past).
benzinerwin said:
I've compiled a new blank-flash package in case anyone would like to try it out (see update in 1st post).
However, I doubt it will work better than the other files. If it keeps on failing with:
then there's still something wrong with the communication between qboot and the programmer file. I.e. we would need a programmer file that works with more recent bootloader revisions.
(I assume that the blank-flash packages out there did actually work at some time in the past).
Click to expand...
Click to collapse
Where is the Download link ??
giri.shiva said:
Where is the Download link ??
Click to expand...
Click to collapse
People who can't read aren't supposed to download, sorry. It's too dangerous, they could flash something without knowing what it does.
Ok, I'll give you a hint: search for update and 1st post
Edit: no, not in the thread. Only in your quote.
giri.shiva said:
Where is the Download link ??
Click to expand...
Click to collapse
Ok, I'll give you a hint: search for update and 1st post
tag68 said:
People who can't read aren't supposed to download, sorry. It's too dangerous, they could flash something without knowing what it does.
Ok, I'll give you a hint: search for update and 1st post
Edit: no, not in the thread. Only in your quote.
Click to expand...
Click to collapse
I tried those already
I thought you had updated another blankflash file
No offense
benzinerwin said:
I've compiled a new blank-flash package in case anyone would like to try it out (see update in 1st post).
However, I doubt it will work better than the other files. If it keeps on failing with:
Code:
FAILED: qb_flash_singleimage()->sahara_download()->IO error
then there's still something wrong with the communication between qboot and the programmer file. I.e. we would need a programmer file that works with more recent bootloader revisions.
(I assume that the blank-flash packages out there did actually work at some time in the past).
Click to expand...
Click to collapse
in this pic, we see error do package, do recipe, do configure, buffer read , this with two firmware of lenovo.ru
https://www.mediafire.com/?eichzw02lsc9kyd
Master, firmware contain blankflash in mbm folder and work programmer until package error or work more that Previous
firmware Oficial XT1635-02_7.0_NPN25.137-24-1 - i n mbm folder blankflash file
https://cloud.mail.ru/public/HoLU/D1tHfMFQY
this two firmware contain blankflash in mbm folder and work programmer until package
firmware Oficial XT1635-02_7.0_NPN25.137-24-1
firmware XT1635-02_6.0.1_MPN24.104-44_47
http://lenovo-forums.ru/files/category/140-moto-z-play/
Thanks for the links. Actually, the older package...
lozada81 said:
firmware XT1635-02_6.0.1_MPN24.104-44_47
Click to expand...
Click to collapse
...did contain an old (duh..!) blank-flash package but also wrapped up with a different programmer.mbn, that I didn't know of before. Maybe you give this a try. I've repacked a blank-flash with this programmer.mbn and the most recent bootloader files (see update in 1st post)...
benzinerwin said:
Thanks for the links. Actually, the older package...
...did contain an old (duh..!) blank-flash package but also wrapped up with a different programmer.mbn, that I didn't know of before. Maybe you give this a try. I've repacked a blank-flash with this programmer.mbn and the most recent bootloader files (see update in 1st post)...
Click to expand...
Click to collapse
Very much to the cortrario, you are using your valuable time, your great knowledge and your ability to help us out of this huge bache called blankflash since update android 7.0 April update, unfortunately I leave my device at home and until late hours can test.
* But the other partners help them by testing and reporting their results to make it easier and faster the info required @benzinerwin
benzinerwin said:
Thanks for the links. Actually, the older package...
...did contain an old (duh..!) blank-flash package but also wrapped up with a different programmer.mbn, that I didn't know of before. Maybe you give this a try. I've repacked a blank-flash with this programmer.mbn and the most recent bootloader files (see update in 1st post)...
Click to expand...
Click to collapse
Thanks for your amazing work, Unfortunately, this package doens't work either. I get ERROR: do_package()->do_recipe()->do_configure()->buffer_read()->device_read()->IO error
hanks for your support
benzinerwin said:
Thanks for the links. Actually, the older package...
...did contain an old (duh..!) blank-flash package but also wrapped up with a different programmer.mbn, that I didn't know of before. Maybe you give this a try. I've repacked a blank-flash with this programmer.mbn and the most recent bootloader files (see update in 1st post)...
Click to expand...
Click to collapse
First of all I thank you for the help provided as well as your time, I commented that I have the 2 files that I uploaded today and in both I get the following
FAILED: qb_flash_singleimage()->do_package()->do_recipe()->do_configure()->buffer_read()->device_read()->IO error
Related
Sup everyone,
I finally got around to updating my TMO DVP. It's been stuck on 7720 this whole time and want to bring it up to Tango.
My question is: what exactly are the steps to upgrading???
Here are the threads I'm trying to follow in order:
http://forum.xda-developers.com/showthread.php?t=1103011
http://forum.xda-developers.com/showthread.php?t=1497142&nocache=1
http://forum.xda-developers.com/showthread.php?t=1736993
From what I understand it:
Install Windows Phone Support Tool
Install WP7 Backup 1.6
Install WP7 Update Cab Sender
Then???
I don't get it. I've installed WP Support tools which doesn't make sense. I have Win7-64bit. The downloads available are x86 or amd64. My computer is intel based, so which do I use? x86 doesn't install, makes sense. I installed amd64.
My next problem is, are there different versions of WP Support Tools? My Zune is up-to-date 4.8.2345.
After installing WP Support Tools:
WPSupportTools.exe is version 0.0.0.0, date modified 4/1/11
UpdateWP.exe is version 6.1.7600.16385 date modified 4/1/11
Microsoft.WindowsMobile.DeviceUpdate.dll is version 4.7.1404.3 date modified 4/1/11
When I run WP Support Tool, I get:
UpdateWP version 4.7.1404
Error: The installed version of the tool (4.7.1404) needs to be updated to match the Zune version (4.8.2345). Please install the tool version 4.8.2345.
Click to expand...
Click to collapse
What do I do?
UpdateWP.exe Information: 0 : 12/25/2012 12:48:25 AM: Device Manager Initializing
UpdateWP.exe Information: 0 : 12/25/2012 12:48:26 AM: Device Manager Initialized
UpdateWP.exe Information: 0 : zune-tuner://windowsphone/5e7a3cc3%20-%20ebd23705%20-%202fd2d1be%20-%20b9b323c8
UpdateWP.exe Error: 0 : 12/25/2012 12:48:26 AM: Update Exception: System.Runtime.InteropServices.COMException (0x801812C0): Exception from HRESULT: 0x801812C0
at Interop.ZuneWmduLib.WmduFirmwareUpdaterClass.StartFirmwareUpdate(IFirmwareUpdateCollection pUpdates, IFirmwareUpdateCallback pCallback)
at Microsoft.WindowsMobile.DeviceUpdate.Device.Microsoft.WindowsMobile.DeviceUpdate.IDevice.Update(String[] URIs, UpdateType UpdateType, Action`1 progressMadeCallback, Object context)
Click to expand...
Click to collapse
Log from when I got somewhere and nothing happened.
I've uninstalled and deleted everything. If anyone can help me out from square one it'd be much appreciated.
KnightmareCS said:
Log from when I got somewhere and nothing happened.
I've uninstalled and deleted everything. If anyone can help me out from square one it'd be much appreciated.
Click to expand...
Click to collapse
It's been a while since I did this. But you did right, AMD64 is correct. And try the file I attached as that's the newest version to match your Zune software. Let us know if you run into anything :good:
(and no, I didn't create the file. I just have it archived from a working cab sender upgrade so credits go to the original poster)
Ok,.
So I installed WP Support Tools.
Copied the files you gave into the Zune directory.
Copied WP7 Backup 1.6 into the Zune directory.
Tried running a backup.
Attached is the error message I got.
I tried the cmd method and that gave the same error.
GoodDayToDie said:
I ran into this issue too.
First question: Is your Zune install in the default location? The support tool installer seems kind of... stupid. It always installs in \Program Files\Zune even if Zune isn't actually installed there. You can copy the files from that location to wherever Zune is installed, if not. Be careful of overwrites.
Next question (really the important one, but the question above can be the reason for the problem): Is there a file called wm7updatelib.dll, or similar, in the folder with your UpdateWP.exe? If so, is it the same version (exactly, down to the build number)? If not, you may need to re-install the support tool (I suggest uninstalling it first, using appwiz.cpl).
Click to expand...
Click to collapse
Looking at this post.
I have wm7update.dll (not wm7updatelib.dll). It is file version 1.0.0.1 /product version 7.0.0.0.
Can you post the right library file?
Thanks
-
Attached are a list of my files and versions in Zune folder. (Ignore the dual Microsoft and UpdateWP, I just added garbage text to the originals)
Backing up now.
Copied the files attached.
wm7update.dll
Interop.wm7updatelib.dll
Interop.ZuneWmdulib.dll
BEASSSSSSSSST running 8773!
KnightmareCS said:
BEASSSSSSSSST running 8773!
Click to expand...
Click to collapse
Good work Glad to see you figured it out. Might want to share your experience if you ran into specific problems in case others have it?
Thanks.
All it was, was making sure I had the right file versions for the right files. Those of which I posted above.
aleunge said:
Good work Glad to see you figured it out. Might want to share your experience if you ran into specific problems in case others have it?
Click to expand...
Click to collapse
I've just update to 8773 myself as well. However, I want to ask you a question: whether we could re-write the firmware version also? My OS version is 7.10.8773.98, but firmware is 2250.1800.7720.219.
No idea. I noticed that too, but haven't seen anything about it just yet.
KnightmareCS said:
No idea. I noticed that too, but haven't seen anything about it just yet.
Click to expand...
Click to collapse
Yeah, maybe it's not necessary enough for us to consider that. However, I just noticed that while updating via Zune, this firmware version string is changed, but not with CAB sender. So, I just guess there might be a way to do it by ourselves too!
please note that the firmware package contains the bootloader drivers etc.etc.
Dell will probably not update those any more. The latest o.s. updates are provided by microsoft and they don't include any drivers whatsoever.
As long as the OS version is the most recent, you're good.
I'm not sure if anyone will find this of use, but I did so I figured I'd post it for everyone to use:
I recently ran into issues running a few binaries on my V10. After doing a bit of research I found that non-PIE (position independent executables) will not run on newer devices (5.0+). Given I needed to run non-PIE binary, I looked further into a fix. This lead me to a thread posted here on XDA about bypassing the PIE check on Android L for the Nexus 5. Unfortunately the linker included in this fix is not usable by our device. Thankfully the linked thread goes into some detail about how to patch /system/bin/linker to allow non-PIE binaries. After reading into the provided information, I was able to patch our own linker and get my non-PIE binary to run just fine.
I've thrown together a flashable ZIP that simply replaces /system/bin/linker with a patched version that will allow non-PIE binaries. :good:
As a note:
Code:
[I]
[B][COLOR="Red"]
I HAVE ONLY TESTED THIS ON MY OWN LG V10 H901 ON MARSHMALLOW (6.0).
I CANNOT VOUCH FOR ANY OTHER MODEL, VERISION, OR DEVICE. AS ALWAYS
BE SURE TO PERFORM A BACKUP BEFORE FLASHING![/COLOR][/B]
I am, by no means, a developer. I simply dabble in Android for fun. I am not
responsible for any issue(s) caused by using this patch and you are doing
so at your own risk.
[/I]
So what this does is allow older non 6.0+ compatible apps to work?
Swizzle82 said:
So what this does is allow older non 6.0+ compatible apps to work?
Click to expand...
Click to collapse
It's helpful for any app with binaries that don't support position independent execution. In my case it allowed me to use my debugging server (which wouldn't run otherwise).
this works on the latest cm build for the htc one m8
but im a little confused as to which byte was modified can you please explain how you found which byte to replace i am using hex editor on my phone and cannot find the hex allocation mentioned in the forum
well i thought it worked until i went to restart my phone and it woudnt boot... thankfully tho i didnt delete the old linker file i just renamed it to linker.old so i was able to boot into my recovery and use its file manager to fix the issue
for now i guess i will create a script to automatically switch the file when i shutdown my phone and switch it back when it starts
Hi Guys!
I would be happy if someone could post a tutorial on how to Bypass PIE on Android 6.0.1
I have some experience in disassembling ELF files, but do not know where to look for disabling PIE in linker file. I would like to learn how to do it on my own, so i am not asking someone to patch my linker file.
Using G928F with Android 6.0.1
Thank you in advance!
Please help me to patch my linker
Works on Samsung J710MM (Marshmallow 6.0.1) perfectly. Thanx a lot!!!
Could anyone help me bypass PIE On marshmallow Touchwiz 6.0.1 would greatly appreciate your help?
Deleted
As many of you probably know, the traditional way to flash firmware in a Huawei phone is to obtain the UPDATE.APP file, and place it in the /dload/ folder of the SD card.
With the Mate 9, this no longer works. The update fails, even if the update package is correct.
I'd like to bring everyone's brains together to figure out the new, correct way to flash an update. My guess is that it should be on the internal storage somewhere, since the Mate 9 Porsche will not have SD card slot. However, I've tried both the update.zip files and the update.app files in / and /dload/ and nothing seems to work.
If anyone can try and make a successful install, it will be a big breakthrough, so please, everyone, try!
Here are some firmware download links to try:
Chinese version
MHA-AL00C00B125 Full
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1356/g77/v66549/f2/full/update.zip
MHA-AL00C00B115 Full
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G990/g77/v65571/f3/full/update.zip
European Version
MHA-L29C900B115
MHA-L29C432B115
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1356/g77/v66711/f2/full/update.zip
The error I get when flashing makes me think it's down to the file version being used?
I can copy an update.app to the dload folder and using *#*#2846579#*#* and Software update it appears to validate the file, at least that an update.app file exists and then boots into the updater, where it fails at 5%. From memory, my Mate 8 would act the same if I tried to flash an older update.app file?
UPDATE: I can confirm that even with the same firmware version as the phone is on you cannot flash it by putting the update.app in the /dload folder, even though it does look like it finds the file. I'm wondering if we will see the same symptoms if we had a newer than B125 firmware to try.
duraaraa said:
As many of you probably know, the traditional way to flash firmware in a Huawei phone is to obtain the UPDATE.APP file, and place it in the /dload/ folder of the SD card.
With the Mate 9, this no longer works. The update fails, even if the update package is correct.
I'd like to bring everyone's brains together to figure out the new, correct way to flash an update. My guess is that it should be on the internal storage somewhere, since the Mate 9 Porsche will not have SD card slot. However, I've tried both the update.zip files and the update.app files in / and /dload/ and nothing seems to work.
If anyone can try and make a successful install, it will be a big breakthrough, so please, everyone, try!
Here are some firmware download links to try:
Chinese version
MHA-AL00C00B125 Full
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1356/g77/v66549/f2/full/update.zip
MHA-AL00C00B115 Full
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G990/g77/v65571/f3/full/update.zip
European Version
MHA-L29C900B115
MHA-L29C432B115
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1356/g77/v66711/f2/full/update.zip
Click to expand...
Click to collapse
I have found a way to load firmware. It's very tricky, but it works You need to spoof huawei's servers, so it's not something someone with low technical skills can do, unfortunately. Also, so far, loading older firmwares causes a forced reboot once the system boots up. I think it's to do with Huawei Account or Fingerprint, so hopefully I will resolve this within a few hours and report more.
duraaraa said:
I have found a way to load firmware. It's very tricky, but it works You need to spoof huawei's servers, so it's not something someone with low technical skills can do, unfortunately. Also, so far, loading older firmwares causes a forced reboot once the system boots up. I think it's to do with Huawei Account or Fingerprint, so hopefully I will resolve this within a few hours and report more.
Click to expand...
Click to collapse
I think its best to wait for the Euro C432B122 rom, it should come very soon.
I don't have a Mate 9 (yet), but looking through the code it looks as if it should be able to load the UPDATE.APP from a usb device (via an OTG cable) - /usb/dload/UPDATE.APP. Did anyone try that?
Found something here
http://www.carbontesla.com/2016/11/download-huawei-mate-9-b122-firmware-update-mha-l29-europe/
Maybe it helps.
dancrow said:
Found something here
http://www.carbontesla.com/2016/11/download-huawei-mate-9-b122-firmware-update-mha-l29-europe/
Maybe it helps.
Click to expand...
Click to collapse
Seems like a scam site as many others
-Edit- It seems Huawei pulled this build as i read on another forum.
gee2012 said:
Seems like a scam site as many others
-Edit- It seems Huawei pulled this build as i read on another forum.
Click to expand...
Click to collapse
Huawei pulls every build that is not linked to hisuite site. Most be legit links but Huawei is on top of it.
intruda119 said:
Huawei pulls every build that is not linked to hisuite site. Most be legit links but Huawei is on top of it.
Click to expand...
Click to collapse
Here is a working L29 B122 downloadlink i found on the android-hilfe forum https://www.hidrive.strato.com/lnk/0KFjlD4J but the update failed installation
Aah well, we`ll get he update soon i guess.
Would be awesome to be able to get the european rom to work without any limitations on the chinese phone. I would love to help you guys, but my skills are very limited and hope you guys find a way that's doable for most of us
Huawei didn't pull the build. It's a DNS problem. It's only on their server in China, and isn't on their amazon co-located servers.
Set in your hosts file:
Code:
14.215.9.39 update.hicloud.com
And magically, the link works!
Can't be installed, though. With the Mate 9, I've tried HiSuite USB flashing (fails), flashing from dload folder (fails) and flashing from eRecovery (only thing that's worked.)
I've even unpacked a full rom image to try and reverse engineer how the dload folder works, but all I get is:
Code:
/sdcard/dload/au_temp.cfg
/sdcard/dload/UPDATE.APP
/sdcard/dload/update_cust.app
/sdcard/dload/update_vendor.app
/data/media/0/dload/update_cust.app
/data/media/0/dload/update_vendor.app
/data/update/dload/UPDATE.APP
/data/update/dload/update_cust.app
/data/update/dload/update_vendor.app
/usb/dload/UPDATE.APP
/usb/dload/update_cust.app
/usb/dload/update_vendor.app
And I've tried most of those locations, and while the update.app is found, it doesn't want to flash. Even though it's willing to flash the exact same stuff in update.zip format via eRecovery.
The only other way is overriding the OTAs, but it actually has a pretty strict security check at the end for approval with some nifty encrypted text, so we're screwed there too.
i would like to know the dload method still work with SD card OR not? anyone with mate 9 got SD card in slot already try this?
New Firmware EU version
MHA-L29C432B126
changelog ::
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1366/g104/v68165/f1/full/changelog.xml
download link ::
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1366/g104/v68165/f1/full/update.zip
OnimushaPooh said:
i would like to know the dload method still work with SD card OR not? anyone with mate 9 got SD card in slot already try this?
Click to expand...
Click to collapse
The dload method no longer works. The update.app file is recognized but install always fails. HiSuite USB flash also doesn't work. Only confirmed way in is hijacking erecovery.
duraaraa said:
Only confirmed way in is hijacking erecovery.
Click to expand...
Click to collapse
I have just dicovered that dload indeed fails. Could you be elaborate / give some clue on how this "hijacking erecovery" is working?
Thanks a lot for your support.
dehnhaide said:
I have just dicovered that dload indeed fails. Could you be elaborate / give some clue on how this "hijacking erecovery" is working?
Thanks a lot for your support.
Click to expand...
Click to collapse
I wrote about it in this thread. You trick the phone into connecting to a fake query.hicloud.com and direct it to the firmware you want to download.
duraaraa said:
I wrote about it in this thread. You trick the phone into connecting to a fake query.hicloud.com and direct it to the firmware you want to download.
Click to expand...
Click to collapse
OK. I got that. But I have the whole update.zip package already downloaded. Is there any way I can flash it?! Sorry if I sound noob but this is my first Huawei Mate and am new to their firmware flashing approach.
Thanks.
Sent from my MHA-L29 using Tapatalk
Pleeez!
duraaraa said:
Huawei didn't pull the build. It's a DNS problem. It's only on their server in China, and isn't on their amazon co-located servers.
Set in your hosts file:
Code:
14.215.9.39 update.hicloud.com
And magically, the link works!
Can't be installed, though. With the Mate 9, I've tried HiSuite USB flashing (fails), flashing from dload folder (fails) and flashing from eRecovery (only thing that's worked.)
I've even unpacked a full rom image to try and reverse engineer how the dload folder works, but all I get is:
Code:
/sdcard/dload/au_temp.cfg
/sdcard/dload/UPDATE.APP
/sdcard/dload/update_cust.app
/sdcard/dload/update_vendor.app
/data/media/0/dload/update_cust.app
/data/media/0/dload/update_vendor.app
/data/update/dload/UPDATE.APP
/data/update/dload/update_cust.app
/data/update/dload/update_vendor.app
/usb/dload/UPDATE.APP
/usb/dload/update_cust.app
/usb/dload/update_vendor.app
And I've tried most of those locations, and while the update.app is found, it doesn't want to flash. Even though it's willing to flash the exact same stuff in update.zip format via eRecovery.
The only other way is overriding the OTAs, but it actually has a pretty strict security check at the end for approval with some nifty encrypted text, so we're screwed there too.
Click to expand...
Click to collapse
C'mon @duraaraa, please elaborate how the update.zip or its contents can be flashed from erecovery!!! Please... you've got me all tangled with this "Only confirmed way in is hijacking erecovery.".
Thanks for your help.
dehnhaide said:
C'mon @duraaraa, please elaborate how the update.zip or its contents can be flashed from erecovery!!! Please... you've got me all tangled with this "Only confirmed way in is hijacking erecovery.".
Thanks for your help.
Click to expand...
Click to collapse
If you want a simple explanation, here is how eRecovery works.
1. The phone sends a request to query.hicloud.com on port 80, asking for what firmware it should download.
2. query.hicloud.com sends it information about what firmware it should download, including a URL
3. The phone sends a permission request to download the files to huawei's servers. Then, the phone downloads and parses the URL plus /full/filelist.xml and gets a list of files. If it sees files which match the region of the phone, it recognizes it as a valid update, and begins downloads the files.
4. Before the install starts, the phone contacts query.hisuite.com again to confirm that it's allowed to install. If it receives permission, the phone checks the MD5 of the files it downloaded, then unzips the three files (an update, a public, and a regional file. Three zip files) The phone then tries to install them. If there is an issue (mismatch, not signed, etc.) it spits out an error and fails. If everything passes the test, it installs.
So my method of entry is emulating query.hicloud.com and update.hicloud.com to provide the phone with whatever zip files I want.
duraaraa said:
If you want a simple explanation, here is how eRecovery works.
1. The phone sends a request to query.hicloud.com on port 80, asking for what firmware it should download.
2. query.hicloud.com sends it information about what firmware it should download, including a URL
3. The phone sends a permission request to download the files to huawei's servers. Then, the phone downloads and parses the URL plus /full/filelist.xml and gets a list of files. If it sees files which match the region of the phone, it recognizes it as a valid update, and begins downloads the files.
4. Before the install starts, the phone contacts query.hisuite.com again to confirm that it's allowed to install. If it receives permission, the phone checks the MD5 of the files it downloaded, then unzips the three files (an update, a public, and a regional file. Three zip files) The phone then tries to install them. If there is an issue (mismatch, not signed, etc.) it spits out an error and fails. If everything passes the test, it installs.
So my method of entry is emulating query.hicloud.com and update.hicloud.com to provide the phone with whatever zip files I want.
Click to expand...
Click to collapse
Thanks for the explanation @duraaraa! Shall I understand that both query.hisuite.com and update.hicloud.com share the same 14.215.9.39 IP?
I have only seen the IP (14.215.9.39) for update.hicloud.com? Is there a different one for query.hicloud.com? I need to know to be able to correctly modify the /etc/hosts on my router.
Thanks for your support.
Hey,
I have mentioned it in a couple of threads already, now I feel it's time to release it:
REDLOTUSimportant, may 6th: apparently I was the only person so far who was successful with this, do not rely on it yet please!
REDLOTUS is an update tool which helps you to convince certain HUAWEI-Phones there is a new update available.
I started developing it because I felt that funkyhuawei is a bit overpriced for some more trivial use cases, but mostly I do not feel comfortable opening up my network for potential man-in-the-middle attacks by routing all DNS requests to some unknown person. On the other hand, funkyhuawei is to be acknowledged for their remarkable chat support, and their broad resources and knowledge - all of which I can not offer personally.
REDLOTUS is free and open source and self-hosted, while still simple enough to use.
Simply speaking, REDLOTUS pretends to be a Huawei update server to HiSuite (and later, to eRecovery).
It was successfully tested with my Huawei P10 VTR-L09, where I used it to re-flash the VTR-L09C432B123-Firmware after I had lost some functionality while flashing
Roadmap: Right now, this tool works only against HiSuite, but I am actively working on letting it work with eRecovery.
The source code, roadmap, and precise instructions live on Github:
Important, may 6th: apparently I was the only person so far who was successful with this, do not rely on it yet please!
https://github.com/lukx/redlotus
I wish you good luck with the tool.
Special Thanks you's go to
* @Jannomag, who was a helpful source of knowledge about the huawei update process
* @duraaraa, who had carefully described some parts of the process in earlier posts of his
Probably just id10t error since I have zero knowledge about node.js.
http://prntscr.com/f46wdh
@frgo nope, actual bug. sorry, I am fixing it right away
Edit: I had forgotten to create the firmware directory before using it, if you run "git pull" in the folder, it should start to work.
This is great news. I have a bit of a learning curve before I'll feel comfortable doing this but I applaud your efforts in bringing a solution to the P10/P10+ upgrade "problem"!
---------- Post added at 09:49 ---------- Previous post was at 08:51 ----------
I think I have made some progress with my learning curve and I know you warned about slow downloads from from Huawei, but I have no indication that anything is happening. I'd have expected to see the creation of a folder for the download at least, but after 30 minutes from running the command all I see is this below. Have I missed something?
Code:
C:\RED\redlotus-master>npm run download http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1475/g104/v84010/f1/full/filelist.xml
> [email protected] download C:\RED\redlotus-master
> node download.js -- "http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1475/g104/v84010/f1/full/filelist.xml"
So finally gave up and hit CTRL-C and got this....
scook94 said:
So finally gave up and hit CTRL-C and got this....
Click to expand...
Click to collapse
I've the exact same problem. I tried to re-install node 7.3 insted of 7.10 but didn't help...
error Windows_NT 6.1.7601
error argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "download" "http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1475/g104/v82108/f1/full/filelist.xml"
error node v7.3.0
error npm v3.10.10
error code ELIFECYCLE
error [email protected] download: `node download.js -- "http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1475/g104/v82108/f1/full/filelist.xml"`
error Exit status 3221225786
error Failed at the [email protected] download script 'node download.js -- "http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1475/g104/v82108/f1/full/filelist.xml"'.
error Make sure you have the latest version of node.js and npm installed.
error If you do, this is most likely a problem with the redlotus package,
error not with npm itself.
error Tell the author that this fails on your system:
error node download.js -- "http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1475/g104/v82108/f1/full/filelist.xml"
error You can get information on how to open an issue for this project with:
error npm bugs redlotus
error Or if that isn't available, you can get their info via:
error npm owner ls redlotus
error There is likely additional logging output above.
Hey @liomajor and @scook94, thank you for your extensive reports. It looks like I had messed with the download process yesterday when I should have gone to sleep already... Could one of you please run "git pull" and run the download again? It should give you a progress indicator, so when you see nothing within a minute or two, you can cancel right away.
Thanks for your collaboration
Lukx said:
Hey @liomajor and @scook94, thank you for your extensive reports. It looks like I had messed with the download process yesterday when I should have gone to sleep already... Could one of you please run "git pull" and run the download again? It should give you a progress indicator, so when you see nothing within a minute or two, you can cancel right away.
Thanks for your collaboration
Click to expand...
Click to collapse
Haven't quite figured out to get a "git pull" to work without it complaining about overwritten files with the merge, so I've downloaded the .zip and unpacked that. Happy to report that everything is now working, downloads currently in progress. :good:
scook94 said:
Happy to report that everything is now working, downloads currently in progress. :good:
Click to expand...
Click to collapse
Thanks a lot for the quick feedback! Awesome
Lukx said:
Hey @liomajor and @scook94Could one of you please run "git pull" and run the download again?
Click to expand...
Click to collapse
Download is running, thx
Lukx said:
Thanks a lot for the quick feedback! Awesome
Click to expand...
Click to collapse
My pleasure. I'm a little wary about proceeding with the upgrade as I see that both the FunkyHuawei method and the "Mate 9" HWOTA method have resulted in a few instances with SIM not being detected after upgrades to C432 devices. Would be nice to see a few success stories before I give it a try.
Just need the nerve to hit the button!
scook94 said:
My pleasure. I'm a little wary about proceeding with the upgrade as I see that both the FunkyHuawei method and the "Mate 9" HWOTA method have resulted in a few instances with SIM not being detected after upgrades to C432 devices. Would be nice to see a few success stories before I give it a try.
Click to expand...
Click to collapse
I had this issue, also posted on reddit (funkyhuawei sub).
After investigation it seems like an issue with the firmware itself not detecting the SIM (as Huawei probably made some small differences in the hardware other than the NAND scandal).
For me there were two options - either revert back to C109 (Orange) or use the C636 (Asia generic). I went with the latter and have no issues as of now (after a week). Plus I converted my single SIM VTR-L09 into a dual SIM VTR-L29.
davebugyi said:
I had this issue, also posted on reddit (funkyhuawei sub).
After investigation it seems like an issue with the firmware itself not detecting the SIM (as Huawei probably made some small differences in the hardware other than the NAND scandal).
For me there were two options - either revert back to C109 (Orange) or use the C636 (Asia generic). I went with the latter and have no issues as of now (after a week). Plus I converted my single SIM VTR-L09 into a dual SIM VTR-L29.
Click to expand...
Click to collapse
That's interesting. I believe this has occurred since C432B123 and is still there with B125 and B130. If it is indeed an issue with the firmware itself I find it quite alarming that Huawei haven't been on the case to fix it ASAP. I have no need of dual SIM and would prefer to keep the C432 region firmware, so I may be forced to wait...
EDIT: Although I guess if a revert to C432B120 will rectify the fault then nothing ventured, nothing gained? Especially now we have the RedLotus method to flash firmware!
scook94 said:
That's interesting. I believe this has occurred since C432B123 and is still there with B125 and B130. If it is indeed an issue with the firmware itself I find it quite alarming that Huawei haven't been on the case to fix it ASAP. I have no need of dual SIM and would prefer to keep the C432 region firmware, so I may be forced to wait...
EDIT: Although I guess if a revert to C432B120 will rectify the fault then nothing ventured, nothing gained? Especially now we have the RedLotus method to flash firmware!
Click to expand...
Click to collapse
On a side note, I installed first L09C432B130, then L09C432B126.
They both had Dual Sim menu in the settings, except the SIM was NOT recognized. Yes, I double checked if they are L09 or L29.
Did not try B120 tough.
Again, not all L09s have this issue, so it is kind of odd.
On the other hand in C636 the difference I noticed are 3 apps (which can be uninstalled) for asian language input.
Error
Hi guys, congratulations for this wonderful guide. I've run all the steps described correctly, downloaded the firmware for my P10Plus correctly, set up the hosts (I have 3, 127.0.0.1 localhost, .. 1 localhost, 127.0.0.1 query.hicloud.com), but when executing the "npm run listen-huawei" command I get the error
- (node:5744) UnhandledpromiseRejectionHarningwarning: Unhandled promise rejection (rejection id:1): error: query.hicloud.com does not resolve to localhost. Please make sure your hosts file is correct.
- (node:5744) UnhandledpromiseRejectionHarningwarning: Unhandled promise rejection (rejection id:2): error: query.hicloud.com does not resolve to localhost. Please make sure your hosts file is correct.
What's the problem? Thank you all
DonDinero said:
Hi guys, congratulations for this wonderful guide. I've run all the steps described correctly, downloaded the firmware for my P10Plus correctly, set up the hosts (I have 3, 127.0.0.1 localhost, .. 1 localhost, 127.0.0.1 query.hicloud.com), but when executing the "npm run listen-huawei" command I get the error
- (node:5744) UnhandledpromiseRejectionHarningwarning: Unhandled promise rejection (rejection id:1): error: query.hicloud.com does not resolve to localhost. Please make sure your hosts file is correct.
- (node:5744) UnhandledpromiseRejectionHarningwarning: Unhandled promise rejection (rejection id:2): error: query.hicloud.com does not resolve to localhost. Please make sure your hosts file is correct.
What's the problem? Thank you all
Click to expand...
Click to collapse
Try either with only " 127.0.0.1 query.hicloud.com" or put that one first in the HOSTS file?
Unfortunately the update failed. Downloaded and installed okay but when the device rebooted it failed, I think, at the verification stage.
Sent from my VKY-L09 using XDA-Developers Legacy app
scook94 said:
Try either with only " 127.0.0.1 query.hicloud.com" or put that one first in the HOSTS file?
Click to expand...
Click to collapse
I added line 127.0.0.1 below those already in the Hosts file ... in the original hosts file there were 2 localhost:
:: 1 localhost
127.0.0.1 localhost
Now instead:
:: 1 localhost
127.0.0.1 localhost
127.0.0.1 query.hicloud.com
DonDinero said:
Hi guys, congratulations for this wonderful guide. I've run all the steps described correctly, downloaded the firmware for my P10Plus correctly, set up the hosts (I have 3, 127.0.0.1 localhost, .. 1 localhost, 127.0.0.1 query.hicloud.com), but when executing the "npm run listen-huawei" command I get the error
- (node:5744) UnhandledpromiseRejectionHarningwarning: Unhandled promise rejection (rejection id:1): error: query.hicloud.com does not resolve to localhost. Please make sure your hosts file is correct.
- (node:5744) UnhandledpromiseRejectionHarningwarning: Unhandled promise rejection (rejection id:2): error: query.hicloud.com does not resolve to localhost. Please make sure your hosts file is correct.
What's the problem? Thank you all
Click to expand...
Click to collapse
DonDinero said:
I added line 127.0.0.1 below those already in the Hosts file ... in the original hosts file there were 2 localhost:
:: 1 localhost
127.0.0.1 localhost
Now instead:
:: 1 localhost
127.0.0.1 localhost
127.0.0.1 query.hicloud.com
Click to expand...
Click to collapse
I don't think you can have 127.0.0.1 pointing to both your own PC (localhost) as well as a web URL. Remove ":: 1 localhost" and "127.0.0.1 localhost" and it should work. You can always change it back later.
Bought an LG v20 H910.
One of the methods to change from standard ROM involved altering the phone to an H91510e.
Although the expected results from those instructions did not happen on this phone, afterward the phone WAS working as an H915.
Tried again with a different method to add TWRP to the (now) H915 but I fear it bricked.
1) I can get [fastboot mode] (vol-, then plug USB in) to come up but I have no idea from here how to get to install TWRP (or even it it did get installed).
2) Trying to enter [download mode] just gives me a colorful garbled screen.
3) Just trying now to turn on the phone says OS corrupted.
In [download mode] LGUP does run but it cannot determine the phone's model, so it won't do anything.
In [fastboot mode] the screen just has tiny writing that says "1140 fastboot mode" started, and above that it that has some data about the phone:
product_name - msm8886 64GB
variant - msm8886 64GB
bootloaded version -
baseband version -
carrier_info - N/A
serial_number - [serial number here]
signing - production
secure_boot - disabled
lock_state - locked
PS - The msm# above (8886) *could be* 9996 or 8996, etc. The print is way tiny and characters too close together. Can't really tell
Can anyone help?
ElMudshark said:
Bought an LG v20 H910.
One of the methods to change from standard ROM involved altering the phone to an H91510e.
Although the expected results from those instructions did not happen on this phone, afterward the phone WAS working as an H915.
Tried again with a different method to add TWRP to the (now) H915 but I fear it bricked.
1) I can get [fastboot mode] (vol-, then plug USB in) to come up but I have no idea from here how to get to install TWRP (or even it it did get installed).
2) Trying to enter [download mode] just gives me a colorful garbled screen.
3) Just trying now to turn on the phone says OS corrupted.
In [download mode] LGUP does run but it cannot determine the phone's model, so it won't do anything.
In [fastboot mode] the screen just has tiny writing that says "1140 fastboot mode" started, and above that it that has some data about the phone:
product_name - msm8886 64GB
variant - msm8886 64GB
bootloaded version -
baseband version -
carrier_info - N/A
serial_number - [serial number here]
signing - production
secure_boot - disabled
lock_state - locked
PS - The msm# above (8886) *could be* 9996 or 8996, etc. The print is way tiny and characters too close together. Can't really tell
Can anyone help?
Click to expand...
Click to collapse
Finish the H910 root guide and you'll be fine
Sent from my ONEPLUS A6010 using Tapatalk
clsA said:
Finish the H910 root guide and you'll be fine
Click to expand...
Click to collapse
Following the instructions at:
https://forum.xda-developers.com/v20/how-to/root-h910-v10m-t3664500
Do I have the wrong instructions? At one point the instructions say :
"Download this modified ... DirtySanta root package: [link] - Extract this somewhere that you can run adb and fastboot from."
But that [link] is dead so I found what I assumed to be the right "LG V20 Root Package.zip" and ran that, but later problems (where the instruction on what to manually type in and run) are obviously for different files than what came in my ZIP download. The instructions call for .BAT files, but I have .CMD files, and they're in a sub-folder.
Also, even though the next link also seems dead I managed to find and D/L h910-10r.zip.
Anyway, running "adb logcat -s dirtysanta" does open a CMD window that freezes after "beginning of system & beginning of main, then nothing.
In the other CMD window I'm supposed to run the .BAT files I do not have and the .CMD files will not run.
So, going back now to the instructions If I want to pick up where it failed, where do I go?
I suppose I must start the phone in fastboot mode but even so STEP1.CMD will not run.
I can run "JustRunMe.cmd" which opens a couple of DOS windows but in there steps 1 & 2 both fail.
Step 3 does /something/ on the phone (files transfers?) then the phone reboots to that LG logo screen and stays there forever.
Thanks. (Hoping that helps you to help me!)
ElMudshark said:
Following the instructions at:
https://forum.xda-developers.com/v20/how-to/root-h910-v10m-t3664500
Do I have the wrong instructions? At one point the instructions say :
"Download this modified ... DirtySanta root package: [link] - Extract this somewhere that you can run adb and fastboot from."
But that [link] is dead so I found what I assumed to be the right "LG V20 Root Package.zip" and ran that, but later problems (where the instruction on what to manually type in and run) are obviously for different files than what came in my ZIP download. The instructions call for .BAT files, but I have .CMD files, and they're in a sub-folder.
Also, even though the next link also seems dead I managed to find and D/L h910-10r.zip.
Anyway, running "adb logcat -s dirtysanta" does open a CMD window that freezes after "beginning of system & beginning of main, then nothing.
In the other CMD window I'm supposed to run the .BAT files I do not have and the .CMD files will not run.
So, going back now to the instructions If I want to pick up where it failed, where do I go?
I suppose I must start the phone in fastboot mode but even so STEP1.CMD will not run.
I can run "JustRunMe.cmd" which opens a couple of DOS windows but in there steps 1 & 2 both fail.
Step 3 does /something/ on the phone (files transfers?) then the phone reboots to that LG logo screen and stays there forever.
Thanks. (Hoping that helps you to help me!)
Click to expand...
Click to collapse
all the correct files to do the root guide are in my AFH here > https://www.androidfilehost.com/?w=files&flid=281250
theirs a Noob version of this guide here also > https://forum.xda-developers.com/showthread.php?t=3932999
clsA said:
all the correct files to do the root guide are in my AFH here > https://www.androidfilehost.com/?w=files&flid=281250 theirs a Noob version of this guide here also > https://forum.xda-developers.com/showthread.php?t=3932999
Click to expand...
Click to collapse
Trying to download the (15) files at that drop but (so far) one of the 1st several I've clicked on fails to d/l every time.
h910_root_pkg.zip seems to complete then I get a network error and the ZIP is corrupted. I tried mirrors, same result and I still have 13 files to go! The "full stock" d/l is another hour it says... Do you have another file drop or maybe all files in one ZIP?
Thanks. You're doing (as they say) the lord's work
PS 2 questions after looking over the instructions:
1) Nougat vs Oreo?
2) Once I have all the files can you tell me at what step in the instructions I should pick up at? The phone seems to be completely wiped out and I can only boot to "fastboot". Also, LGUP (that I have) will not recognize the model. The SDK says at the top left corner H910 and in the top right corner H915.
ElMudshark said:
Trying to download the (15) files at that drop but (so far) one of the 1st several I've clicked on fails to d/l every time.
h910_root_pkg.zip seems to complete then I get a network error and the ZIP is corrupted. I tried mirrors, same result and I still have 13 files to go! The "full stock" d/l is another hour it says... Do you have another file drop or maybe all files in one ZIP?
Thanks. You're doing (as they say) the lord's work
PS 2 questions after looking over the instructions:
1) Nougat vs Oreo?
2) Once I have all the files can you tell me at what step in the instructions I should pick up at? The phone seems to be completely wiped out and I can only boot to "fastboot". Also, LGUP (that I have) will not recognize the model. The SDK says at the top left corner H910 and in the top right corner H915.
Click to expand...
Click to collapse
Yes AFH is having issue today
The root package is all you need their
All the other links in the guide work fine
Sent from my ONEPLUS A6010 using Tapatalk
Have u been able to fix your phone???? This is me kn telegram @princedede . U can hala me
I have not. The one package I need AFH fails on me ("network error") every time I try to download it.
ElMudshark said:
I have not. The one package I need AFH fails on me ("network error") every time I try to download it.
Click to expand...
Click to collapse
why didn't you ask ?
here's your file > https://drive.google.com/open?id=1Vn6HUGMwCX8vZ48M6AZloikCMD82De7j
I just downloaded it again from AFH no problems
So, I have moved to a new v20. I was never able to get that file from AFH.
Anyone want to buy a (maybe not) bricked v20?
There's an insignificant crack in the lower right corner.
I *would* like to root the phone, primary reason being to get a real backup saved but once bitten...
clsA said:
why didn't you ask ?
here's your file > https://drive.google.com/open?id=1Vn6HUGMwCX8vZ48M6AZloikCMD82De7j
I just downloaded it again from AFH no problems
Click to expand...
Click to collapse
I just tried that link, maybe I waited too long but it fails me too.
ElMudshark said:
I just tried that link, maybe I waited too long but it fails me too.
Click to expand...
Click to collapse
Try now
https://www.androidfilehost.com/?fid=1395089523397955603
https://drive.google.com/file/d/1D79WTkqifCXciSWHTFNJJXpw99lzLWWO/view?usp=sharing
Sent from my ONEPLUS A6010 using Tapatalk
Still no good.
Chrome:
Google Drive
We're sorry. You can't access this item because it is in violation of our Terms of Service.
FireFox:
Google Drive
Sorry, the file you have requested does not exist.
ElMudshark said:
Still no good.
Chrome:
Google Drive
We're sorry. You can't access this item because it is in violation of our Terms of Service.
FireFox:
Google Drive
Sorry, the file you have requested does not exist.
Click to expand...
Click to collapse
I reuploaded it try now
AFH and Google Drive both each still fail me in the same way they have. No difference