Related
TL;DR: I need update logs or an idea what path might be missing that breaks the 8.1 update!
Hi all, strange for me to be asking for help here but it happens...
I've finally gotten my ATIV S (SGH-T899M) into a state where I'm willing to upgrade it to WP8.1. However, I am unable to do so. I've been able to install a few updates, but the actual 8.1 update won't install. The error I get (under the "Update status" line in Settings -> Phone Update: "The update was downloaded, but couldn't be opened. (80070003)"
The error code is an HRESULT or NTSTATUS wrapper around Win32 error code 3, which is ERROR_PATH_NOT_FOUND. Note that this is distinct from FILE_NOT_FOUND (2); you only get error 3 when a part of the path to a given file (or directory) is missing. I've searched online for any information about this error with regards to updates, to no avail. It does sometimes happen with Windows Updates on PC, but the instructions for resolving that aren't easily mappable to the phone.
Phone's current status:
OS version: 8.0.10532.166 (this is the pre-8.1 version; as I said, I did get some updates)
Firmware revision: 2212.13.11.2 (this is the Samsung GDR 3 version, except modified to not overwrite WP8Diag.xap or FCRouter, etc.; see http://forum.xda-developers.com/showthread.php?t=2537241)
Hardware revision: 15.3.1.0
Radio software: 2212.13.11.2
Radio hardware: 0.0.0.0
Bootloader version: 13.08.14.16
Chip SOC version: 1.5.32
Phone was originally branded for Telus Mobility in Canada, and still has signs of that in DeviceTargetingInfo (language is 0809 instead of 0409, for example, and MobileOperatorName is LUS-CA). It was factory SIM-unlocked and brand new when I got it. It is developer-unlocked, interop-unlocked, capability-unlocked, and has been subjected to numerous additional hacks; I've reversed a few that I can think of which could possibly impact the update (like messing with files in the System32 directory) but I probably missed a few of those.
Here's what happens when I try to update:
If Preview For Developers is not enabled, it does "Checking for updates" then says I'm up to date.
If PFD is enabled, it checks for updates and then, if I'm on WiFi, downloads the update CABs.
It then enters the "Preparing to install" step. This is very slow in some places, stalling for minutes at a time at some percentages, but eventually reaches 97%.
It then stops the update process with the error message in bold above.
It does NOT ever tell me what the update is.
It does NOT reboot, or even offer to reboot, at any point.
The "Check for updates" button re-appears and can be used to start the process over again.
So... any ideas or suggestions? I'd prefer to avoid a hard-reset if possible, simply because of the amount of time it would take to restore the phone to the condition I state I want it in, but I'll do one if nothing else works. Things I'm particularly looking for, in descending order:
1) Anybody else who has experienced this problem and found a solution (and what that solution is).
2) Any log files I could check to see what it was trying to do when the error occurred (ideally with the path that caused the error).
3) Anybody else who has encountered this problem but not gotten past it; we can compare what changes we made to our phones.
4) Anybody else who has a reasonably similarly-modified phone but has not experienced this error and was able to install 8.1 (so we can compare what we did to our phones, and I can possibly crib files off you).
Hope somebody can help! Thanks.
GoodDayToDie said:
TL;DR: I need update logs or an idea what path might be missing that breaks the 8.1 update!
Hi all, strange for me to be asking for help here but it happens...
I've finally gotten my ATIV S (SGH-T899M) into a state where I'm willing to upgrade it to WP8.1. However, I am unable to do so. I've been able to install a few updates, but the actual 8.1 update won't install. The error I get (under the "Update status" line in Settings -> Phone Update: "The update was downloaded, but couldn't be opened. (80070003)"
The error code is an HRESULT or NTSTATUS wrapper around Win32 error code 3, which is ERROR_PATH_NOT_FOUND. Note that this is distinct from FILE_NOT_FOUND (2); you only get error 3 when a part of the path to a given file (or directory) is missing. I've searched online for any information about this error with regards to updates, to no avail. It does sometimes happen with Windows Updates on PC, but the instructions for resolving that aren't easily mappable to the phone.
Phone's current status:
OS version: 8.0.10532.166 (this is the pre-8.1 version; as I said, I did get some updates)
Firmware revision: 2212.13.11.2 (this is the Samsung GDR 3 version, except modified to not overwrite WP8Diag.xap or FCRouter, etc.; see http://forum.xda-developers.com/showthread.php?t=2537241)
Hardware revision: 15.3.1.0
Radio software: 2212.13.11.2
Radio hardware: 0.0.0.0
Bootloader version: 13.08.14.16
Chip SOC version: 1.5.32
Phone was originally branded for Telus Mobility in Canada, and still has signs of that in DeviceTargetingInfo (language is 0809 instead of 0409, for example, and MobileOperatorName is LUS-CA). It was factory SIM-unlocked and brand new when I got it. It is developer-unlocked, interop-unlocked, capability-unlocked, and has been subjected to numerous additional hacks; I've reversed a few that I can think of which could possibly impact the update (like messing with files in the System32 directory) but I probably missed a few of those.
Here's what happens when I try to update:
If Preview For Developers is not enabled, it does "Checking for updates" then says I'm up to date.
If PFD is enabled, it checks for updates and then, if I'm on WiFi, downloads the update CABs.
It then enters the "Preparing to install" step. This is very slow in some places, stalling for minutes at a time at some percentages, but eventually reaches 97%.
It then stops the update process with the error message in bold above.
It does NOT ever tell me what the update is.
It does NOT reboot, or even offer to reboot, at any point.
The "Check for updates" button re-appears and can be used to start the process over again.
So... any ideas or suggestions? I'd prefer to avoid a hard-reset if possible, simply because of the amount of time it would take to restore the phone to the condition I state I want it in, but I'll do one if nothing else works. Things I'm particularly looking for, in descending order:
1) Anybody else who has experienced this problem and found a solution (and what that solution is).
2) Any log files I could check to see what it was trying to do when the error occurred (ideally with the path that caused the error).
3) Anybody else who has encountered this problem but not gotten past it; we can compare what changes we made to our phones.
4) Anybody else who has a reasonably similarly-modified phone but has not experienced this error and was able to install 8.1 (so we can compare what we did to our phones, and I can possibly crib files off you).
Hope somebody can help! Thanks.
Click to expand...
Click to collapse
I've seen this happening with many people. The only way is reset.
Huh. I didn't see any news about it, at all, when I searched. Lots of stories about *other* update errors for WP8.1. Lots of stories about this particular error when installing Windows updates on normal Windows (none of which, sadly, had helpful suggestions for the phone). When you say "many people" do you mean in general, or just lots of people with interop-unlocked ATIVs?
I would really like it if the source of the problem could be identified and fixed, but Microsoft seems unlikely to be helpful here. It's probably a really simple problem - a config file that needs to be edited, a folder created (we can do that), a registry value changed, something like that - but oh well. I can back up my app data, and my SMS are backed up automatically, so I suppose in the big scheme of things there's no reason *not* to do this... I just don't like it, and consider it a waste of time.
On the other hand, if I have to hard reset anyhow, I might take the opportunity to install a custom CSC. I normally try to stick as close to stock ROM as possible - making only runtime changes, basically - but it's quite possible that some of the changes I've made will *already* persist after reboot (part of why I'm hesitant to blindly hard-reset; what if it doesn't fix anything and is just a waste of time?). It would be nice to get some of the feature perks of the custom CSC though.
I had almost the same problem getting the error 80070003.
view those two posts if you are interested
post 217
post 218
Thanks, but that's.. mot actually very encouraging. I have the SGH-T899M, and as far as I know we still don't have a leaked ROM from one of those.
I also got the "Your phone couldn't be updated" message. But the code was: 80188308.
Any takers?
Phone's current status:
OS version: 8.0.10532.166 (with the three xml files....)
Firmware revision: 2216.14.01.2
Hardware revision: 3.19.1.0
Radio software: 1621.14.11.2
Radio hardware: 0.0.0.7
Bootloader version: 13.07.12.14
Chip SOC version: 2.0.15
-tdecision10
GoodDayToDie said:
Thanks, but that's.. mot actually very encouraging. I have the SGH-T899M, and as far as I know we still don't have a leaked ROM from one of those.
Click to expand...
Click to collapse
I've been trying to look into what's going on with the error message.
I found the particular error string within DuErrorsUIRes.dll. IDS_DU_ERROR_PREINSTALL_FAILED.
With that said, the only files that use the DuErrorsUIRes.dll are \PROGRAMS\DUACLIENT\DuaClientSettings.dll and \PROGRAMS\DUACLIENT\DuaNotification.exe.
I'm not good AT ALL with ASM, but you can either grab those files from your phone or grab them from the emu and load them into IDA and track it down.
I know that the code is the 6th code in the list that corresponds with the update error text.
Sorry I'm not able to help much, but hopefully this is of SOME value to you.
Thanks, Snickler. That's an approach I hadn't considered. Since the error code just means "Path not found" I was trying to think of paths it might attempt to access which could, for some reason, be missing from my phone... but working from the other end might work better.
Hi there,
I have a nearly three year old Lumia 1320 that I have as my daily driver, and have been using the Windows 10 DP since early days. Recently, the W10 release it had was the one that stuffed up SD card storage (and was getting random reboots) so I decided to go back to 8.1 and updated it to the Update 2 release.
So far so good. However, the newest W10 release came out so I decided to give it another go (especially as SD card issue resolved) so ran the appropriate software, it downloaded, and applied the image, then it failed. It said to try again, so I did and then started saying things like I didn't have enough storage. The Storage app wouldn't load, nor would Store, Phone, Messages etc. so tried the recovery tool to reflash it back to stock 8.1
This tool failed during the process and said it couldn't flash the device.
Tried various reset techniques and they all failed to get a good result. The symptom was to get the red NOKIA screen for a split second then it loaded the OS.
Now I'm getting concerned and bring out the big guns! Read the XDA tutorial on Windows Phone flashing, downloaded the tools, installed the unsigned driver, downloaded the appropriate image for my phone and went to flash.
Got to 2% and failed:
Sorry! Your device could not be flashed with the image you selected.
Please correct the following error and try again:
Failed to flash with device error { 0xd, 0x0, 0x0, 0x2, 0x0, 0x0 } : Status: 0x80000008
I looked up this 0xd code on the MS site and the error is this:
0xD While applying the image to disk, a block write operation failed.
So now to the ultimate question - does this mean my phone has a hardware error that prevents flashing, or can anyone suggest a workaround to get past this?
The model is RM-994 - the image is 059V5K2 (Australia/NZ Vodafone)
PC I am flashing with is a Core i7 2600, 8GB, Windows 10 Pro x64 with latest November update.
Any advice much appreciated.
Darren
No one?
Really no replies? Anyone on here know more low-level details or tests I can perform?
Even if someone confirms my suspicions that there is a hardware fault that simply can't be overcome, I can move on.
The phone is still running, alarms work, lock screen works (even updates Bing photo), but no Store, Storage Sense, Messages, plus many others and if I delete apps listed as unavailable, or even current apps, such as Tweetium, they disappear and return after a reboot of the device.
I have even tried remote wipe from the web and the device reboots and goes straight back to where it was.
Regards
Darren
Hi!
Yesterday I rooted (interop tools) my Lumia 640 with WM10 onboard, get full FS access and delete folder DPP (and some others) from my Phone.
After restart phone won't booted:crying:
After that I flash my phone with stock WP8.1 (lumiafirmware.com) using WPID (WDRT is not recognized my phone).
WM8.1 started successfully but 1) my SIM card is not working (present but unavailable), 2) I cant login in Microsoft account - phone want to be activated (see screenshots).
As I can guess in deleted DPP folder there were some original keys and model values. Without them my phone is not activated and I have two problems 1) and 2).
I have files from DPP folder stored on my laptop.
Please help me to restore my phone!!!
I thought to do another root and copy DPP folder back but I can't do root in WM8.1 because I have no one application that need for CustomWPSystem to make root (MixRadio is absent in stock my rom, WPD and others I can't install from Store because of problem entering in Microsoft account - see 2) ).
So I'm completely disappointed :crying::crying::crying:
Can't attach screenshot don't understand how to. May be it's limited because I'm new here.
I took another ffu with MixRadio in it and successfully rooted WM8.1.
Thank copy back DPP folder. Than reflash my phone with stock image.
But all this didn't help(((
The problem of activation and not working SIM still present.
I call to service center and thay told me to completely reflash bootloader with special equipment.
Now my question is will it solve my problems? And can I reflash bootloader myself with simple USB cable and a laptop?
Dpp contain unique key for windows activation, ssd key hash and some another's. Sometimes device flash with specific device certs.
If you have backup dpp.bin its good but may be you have to write it correctly as gpt partition.
I think this step would be good. First flash dpp or restor its stuff.
Then put phone on emergency download mode. Then flash all bootloaders then flash ffu.
I don't think it will be get re-provision or what.
ogrishko said:
Hi!
Yesterday I rooted (interop tools) my Lumia 640 with WM10 onboard, get full FS access and delete folder DPP (and some others) from my Phone.
After restart phone won't booted:crying:
After that I flash my phone with stock WP8.1 (lumiafirmware.com) using WPID (WDRT is not recognized my phone).
WM8.1 started successfully but 1) my SIM card is not working (present but unavailable), 2) I cant login in Microsoft account - phone want to be activated (see screenshots).
As I can guess in deleted DPP folder there were some original keys and model values. Without them my phone is not activated and I have two problems 1) and 2).
I have files from DPP folder stored on my laptop.
Please help me to restore my phone!!!
I thought to do another root and copy DPP folder back but I can't do root in WM8.1 because I have no one application that need for CustomWPSystem to make root (MixRadio is absent in stock my rom, WPD and others I can't install from Store because of problem entering in Microsoft account - see 2) ).
So I'm completely disappointed :crying::crying::crying:
Click to expand...
Click to collapse
Yeah..i got your point....
You have to do this.
Anyhow you need to install wm10 ...and interope it interop tool ..and apply full fs access...
Now, you need to create a simple folder with "DPP" Name and put content onside it ..reboot....gotcha you have done.
Problem
As per my knowledge...you deleted the DPP .so your phone doesn't have any connectivity...
No wifi
No cellular
No activation
So, need to install wm10 anyhow..is the only one solution
DPP partition files?
ogrishko said:
Hi!
Yesterday I rooted (interop tools) my Lumia 640 with WM10 onboard, get full FS access and delete folder DPP (and some others) from my Phone.
After restart phone won't booted:crying:
After that I flash my phone with stock WP8.1 (lumiafirmware.com) using WPID (WDRT is not recognized my phone).
WM8.1 started successfully but 1) my SIM card is not working (present but unavailable), 2) I cant login in Microsoft account - phone want to be activated (see screenshots).
As I can guess in deleted DPP folder there were some original keys and model values. Without them my phone is not activated and I have two problems 1) and 2).
I have files from DPP folder stored on my laptop.
Please help me to restore my phone!!!
I thought to do another root and copy DPP folder back but I can't do root in WM8.1 because I have no one application that need for CustomWPSystem to make root (MixRadio is absent in stock my rom, WPD and others I can't install from Store because of problem entering in Microsoft account - see 2) ).
So I'm completely disappointed :crying::crying::crying:
Click to expand...
Click to collapse
Was this an ATT locked phone in the US?
No, it's in Russian. No lock.
I bring my phone to official service center. They test my phone and said can nothing to do and they replaced my phone.
ogrishko said:
I bring my phone to official service center. They test my phone and said can nothing to do and they replaced my phone.
Click to expand...
Click to collapse
Dang. I'll tell you what happened to my phone:
I think I also deleted the DPP too. But somehow, I accidentally put T-Mobile ffu instead of att. Now, whenever I try to put att ffu it says thor2 invalid platform ID. I also tried booting to emergency download mode. Windows device recovery tool detects it as a 635, and downloads the wrong ede's and edp's. So I had to go to lumiafirmware.com and download them myself. However, when I try to use it in thor2, I get an error when it sends the ed signature. As a last resort, I used the current T-Mobile software and then used vcREG on the phone to get full fs access via MTP. But also that doesn't work the DPP folder has the exact same contents as the EFIESP folder.... I tired to also do FS access over SFTP - I can't even connect to the phone... so I'm kind of screwed...
[UPDATE]
After practically trying every single thing ever possible, and nothing working, phone seems to be bricked in QHUSUB_BULK.
So it happened day before yesterday, 8-22-17 @ ~5:50 PM, my Verizon S6 Edge (G925VZKE [64GB]) bricked out. No LED Light, nothing on Screen, nothing as if actually Hard Bricked. No booting, No download Mode, nothing. But it's not fully hard bricked actually. When I plug the device into my PC, Windows will either pop and say the device malfunctioned or it will read as "Exynos7420". I'm not quite sure what to do about it at the moment, I've read [a little] about what to do with phones in this mode using a "USB_Down_Load_32bit"/Multidownloader. I believe it to be stuck in a Diagnostic Mode I'm not versed in. This all happened while I was in the ADB Root Shell (su:s0) while the device was powered off and charging.
I am making this thread here for any devs you would want to use the knowledge and files here, to take the project further. As I cannot currently use my device at all. And I won't be getting a replacement S6 Edge for at least a month, maybe two. I love the S6, and will still choose it over most devices. I've been dedicated to researching and posting about the Samsung Exynos7420 Hardware since September 2016. That was when I came up with the plan for The Greyhat Root Project. You may recall my other thread once in the Original Development Forum & now in General. If you search "Greyhat Root" in google. My thread will be the first result. It gained a lot of traction, very very quickly. But is now dead, and the mods probably hate me for making a new thread. But I'm not trying to put new news out there this time.
It focused on how to use Kali Linux and Metasploit. It also focused on the articles at the time that was new exploit & malware research, that boasted of the possibilities we've now come to know as the Vault7 leaks. There's probably a reason I was a victim of the malware myself and I took down most of the posts. Most of the good file and resources I posted to that thread were either flagged by end users or removed by google. The real treasure of that thread is lost to the internet now, as that was the only backup I had of some of the critical files needed for the process. If you actually look through my individual posts all over, you will find some juicy tidbits of knowledge spread around this site that I've not compiled into one. A lot of it is still over my head as it was then, and partly why I took it down then. But I've been chipping away at that knowledge base everday for 10 months going on a year now. It's possible to root this device if One can take the knowledge of how to leverage the news worthy exploits from the past 2 years into a single repo/application. "Android-InsecureBankv2" is one example of such a platform. But as a teaching platform, it is not configured to provide a SuperSu Root Solution out of the box. It would still require modification of someone else's codebase w/Learning Curve.
No I have not managed to find a way to unlock the bootloader because I do not have a copy of IDA Pro or the Hex Rays Decompiler, and if I did, I still wouldn't know to use them fully. But I have managed to find quite a number of very possible attack vectors, if I can get some serious developers to take my sentiments seriously. I proved that when the posts about dirtycow were largely ignored due to device interest, and then @droidvoider helped make some of my ideas possible with the "Greyhat Root Console" he made. Realistically at this point I only wish I were an Assembler. I'm only one guy trying to poke at a Hardware/Software Package created by multiple departments of people in a conglomerate corporation. I only bring people together. I do know that in order to disassemble the Exynos7420 sboot, you're going to need to understand U-Boot on Arm64. A Uboot version dating back to either January 2016 or August 2015. I say those two dates because, The 4BOG7 files on my device date to August 2015, the 4AOJ1 files, to January 2016. Project Zero (who does a lot of tests on the G925v btw), posted in February 2017 about they found a way to bypass the KASLR feature of the stock kernel. A Kernel I do believe we can still flash to the device. It didn't gain much attention I don't think at the time because it was only one piece to the puzzle. That exploit wasn't patched until January. I know it sounds bad when I say it like this but, what this device truly needs is a friendly Botnet-C&C-Style rootkit that has it's client and server controlled by a User-Controlled, SuperSu-Style management application. Yes, it would be a rootkit you would never want to have someone else in control of. But if SuperSu were controlled by someone else other than the end user at the time, it would be just as bad. It's just a different approach to a yet unpublished methodology.
*
** The Device I refer to is currently flashed with:
******
** Full 4 File Firmware: COMBINATION_VZW_FA50_G925VVRU4AOJ1_VZW4AOJ1_CL5133452_QB6486176_REV02_user_mid_noship.tar
** BL: G925VVRU4AOJ1 ENG sboot.bin
** AP Kernel: G925VVRU4BOG7 ENG Kernel
** TrustZone Type: t-base-tui (Filenames suggesting Mobicore present as well)
******
Trying to enter Recovery Mode with the Combo firmware, in my experience, typically sends the device into a Panic and boots into "Upload Mode" if it does not simply reboot. The combination firmware does not supply a recovery.img that I've found. And inorder to recover the ENG Combination Recovery, you would have to disassemble the OJ1 ENG sboot.bin in IDA Pro and pull it out.
During the initial boot the device will enter its own recovery mode for a moment while it does its erasing stage. I used "nand erase all, re-partition, F.Reset Time, Phone Bootloader Update options in ODIN. During this breif moment with the "Erasing..." text on-screen, the phone is available in ADB Devices and shows up in recovery mode. Meaning ADB Shell should be accesible in recovery. If that's possible that means the device keystore should be accessible as well. The Recovery images tend to be bigger because the signatures are stored in the recovery from what I've read. Can't dirtycow patch anything it can see if your shell can't change it?
Using those files, I have full su authority anytime I am in ADB Shell, the shell runs within the "su:s0" context, and not the "shell:s0" context. Any and All changes are possible through the shell. Writing a new partition Table to '/dev/block/platform/15570000.ufs/sdb' using the "partx" tool, is probably what broke my phone. So in theory installing SuperSu in System Mode should work much the same as it did on G95x S8/Plus I'm gathering. @dragoodwael was correct in supposing "sdb" to be the bootloader overall, as I do now too. Once the reboot command was issued, I lost the ability to do anything at all. All thats possible now, is to find a tool that will communicate with the driver my PC's Device Manager loaded for my phone.
Every boot.img I've unpacked using Android Image Kitchen specified that a signature of "SEAndroid Type was found". BUT, the only boot.img/Kernel that did not specify that it was an "SEAndroid Type" while being unpacked, is the Stock boot.img from the 4AOJ1 Combination Firmware. Out of the 7 boot images I've unpacked, AIK determined the OJ1 Combination boot.img did NOT have an SEAndroid Signature on it.
boot.imgs I've unpacked:
1. N920A - PB2 Eng boot.img
2. N920A - FA51 Combi - PH1 boot.img
3. N920A - FA51 Combi - PL1 boot.img
4. G925V - FA50 Combi - OG2 boot.img
5. G925V - FA50 Combi - OJ1 boot.img
6. G925V - OG7 Stock boot.img
7. G925V - OG7 ENG boot.img
I'm not quite sure what that means yet, but I do know that the zip file I have that contains the 4AOJ1 factory Binary is not a tar.md5 like usual, it is just a normal .tar. What I'd LOVE to know is, can the 4AOJ1 stock boot.img be unpacked, then repacked, and retain its flashable characteristic. Because AIK does not register a standard signature. Does that mean the Oj1 boot.img uses a different mechanism for signature verification than a standard user binary, or is it simply signed with publicly available signing keys? It's a good question, what is different about its signature compared to other stock signatures. Even if we don't understand the signatures fully.
I'm also aware of the fact, that the Combination firmware doesn't actually contain a recovery.img to flash. Probably why the Device goes into Upload Mode and Panics when trying to boot recovery after using "nand flash all" and/or "re-partition" in ODIN. But if there were a Recovery Image for the OJ1 firmware, I imagine it would not have an SEAndroid signature on it as well. So there must be something to that.
I wonder what would happen if you tried to flash the OJ1 boot.img to the recovery partition as recovery.img like in the "EasyRecowvery" project, while using the full factory binary.
Is it possible that the newer "ustar" tar format used by Samsung in ODIN packages, could be using the custom fields available in a ustar header block to hold at least part of the signing mechanism? I believe so. And I say it because on my Device, it runs the Odin3 Engine (v1.1203), which looks an aweful lot like ODIN v1.12.3. Besides the naming conventions used there, ODIN expects to send/receive images within tar archives. Specifically USTAR format tar archives. So if the ODIN Engine on the phone is anything like the PC Client application, it expects USTAR format Tar archives as well. If it expects to read in a USTAR Header block, there are custom fields possible in known locations of the official tar files. Which when parsed correctly, should lead to finding the extra data after the payload 7-Zip refers to when the tar.md5 files are extracted. I'm of the mind the "Star" utility and not the the "Tar" utility is what we should be using to create and modify ODIN firmware the way our OEM's do. That is hypothesis on my part yes, but I don't think I'm very far off base.
Here is a man page on the "ustar" utility I found interesting and extremely in-depth: ustar(1) - unique standard tape archiver - Linux man page
If you want to see a list of files involved in all of this research, please refer to this folder here: https://drive.google.com/open?id=0B_EcHdXbjhT_dDRneE56WUg3Mlk
It contains all the files I've mentioned except for the OJ1 Firmware itself. This is all I'm posting for today, it's a sad day indeed. But I have to gather the bookmarks again to post the links to articles.
Hi everyone.
I have bricked my phone and I don't know how to fix it. When I turn it on, it shows a green screen with two rectangles (one blue, one red).
Sometimes, after that screen with the rectangles, there is a menu to configure my device, ant it says "welcome to device D188" , and when I choose the language, setting as new phone, it tries to connect to network but it never does. So I'm stuck there.
Before this mess, I made a backup of the oem info with twrp, but I think something went wrong because it seems that this oem info has a one ".bin" archive (that i what I've seen looking in the internet), and my twrp backup is a folder with a lot of files(with .win, .sha2, .in extensions). I have two called oeminfo.emmc (one is .win, one is .sha2).
I've tried creating a dload folder with the update.app file in my micro sdcard, and then try to update but it shows "failed".
I was going to try and flash my phone via ADB but then I realised that I have to extract this update.app and I cannot do it because appears the error: RECOVERY_RAMDIS.img: Invlid header crc - Expected: 36587 Got: 6910.
PD: all this comes because I have the Huawei P10 chinese version, and Android Pay wasn't working in Europe (I had some problems adding my card). I thought that was a problem of the chinese ROM in Europe (because when I was in China, I dind't have that problem). So, what I did is rebrand my phone, but Android was still not working (this time because android pay detected a custom rom), and anyway, I didn't like it because the update system option disappeared, in system was a lot of information that wasn't about my phone, that it was wrong (things as processor, ram, etc.). And here is the crazy thing, I went to TWRP, and I restored, when I only had a backup of OEM, system and something else...
I think my phone is now usless and canoot be fixed, but I had to try posting this, just in case someone can help me.
Thanks.