Related
So I tried to flash android on to the phone using the tegra 250 images when I realized I need the apx series images for android. The thing about that is I can't find them anywhere. Anyone have any idea where a development site for the tegra apx series is? It seems Nvidia has no support for the old series anymore.
how do you upload android to the phone? what program or steps do you do? is there a debug mode or recovery mode? I believe we have to make are own images.
I was using a program provided by nvidia for programming a tegra based development kit. It is capable of flashing android and windows ce 6. If anybody with more experience would like to take a look at the drivers images and program here are the files.
http://tegradeveloper.nvidia.com/tegra/downloads
Don't the images you are looking for have to have drivers for the hardware interfaces specific to this phone?
stetkas said:
Don't the images you are looking for have to have drivers for the hardware interfaces specific to this phone?
Click to expand...
Click to collapse
I wasn't exactly worried about the hardware working as much as getting android onto the tegra and viewing the os. Creating drivers is the easy part.
dezgrz said:
I wasn't exactly worried about the hardware working as much as getting android onto the tegra and viewing the os. Creating drivers is the easy part.
Click to expand...
Click to collapse
Do you think you could write a driver for this.
APX
USB\VID_0955&PID_7416&REV_0103
USB\VID_0955&PID_7416
This VID supposedly belongs to Nvidia. This is the device that is found by Windows if you plug your phone into the usb when it is turned off and then press the u+s+b+power buttons.
I tried the Recovery Mode, like the person described above me, and it came up with the APX device.. So, if someone makes a driver for that, then we might be able to jailbreak it? (iPod Touches and iPhones jailbreak though Recovery Mode). This doesn't seem much diffirent from an iPhone or an iPod Touch.
I found out a driver that we might be able to modify to give us access. I downloaded both the froyo and c36 downloads available from the tegra site that was mentioned earlier. http://tegradeveloper.nvidia.com/tegra/downloads
These file paths could be different if your hard drive has a different drive letter and perhaps also if you have a 64-bit processer, but I found the drivers in the following directories.
C:\Program Files\NVIDIA Corporation\tegra_froyo_20101105\usbpcdriver\NvidiaUsb.inf
C:\Program Files\NVIDIA Corporation\ce6_tegra_250_5265393\os\usbpcdriver\NvidiaUsb.inf
These drivers have the hardware ID in the inf file and so Windows recognizes it and starts to install the driver and finishes, but says there is an error. I'll keep working on it though.
So, the drivers do actually work; it was my computer that was causing the problems, not the drivers. Now that the drivers are installed I think we can use the SDKs provided by Nvidia on the Tegra download page.
If this works, we now have a serious decision to make. Do we try to get android on the phone or do we stick with the Windows CE based os?
mcdietz said:
So, the drivers do actually work; it was my computer that was causing the problems, not the drivers. Now that the drivers are installed I think we can use the SDKs provided by Nvidia on the Tegra download page.
If this works, we now have a serious decision to make. Do we try to get android on the phone or do we stick with the Windows CE based os?
Click to expand...
Click to collapse
Personally, I would rather stick with current OS. Just because I don't want to brick my phone. Maybe have some additions to the current OS? Enable hidden features or something? Customizations? etc?
First off, I wanted to thank everyone who is working on trying to develop an update to improve on the Kin Two. I currently am interested in getting the TWOm when my contract expires but there is a dealbreaker for me, which is that the phone does not alert you when you have a missed call. I know there are other annoying flaws (pointed out in details at the verizon forums by fisharefriends), but this is the only flaw I cannot deal with.
I do not know what is possible of being changed/edited, but I think mcdietz should focus on implementing basic functions that are currently not on the Kin Two phone, but are on other simple lower spec feature phones.
zero2duo said:
First off, I wanted to thank everyone who is working on trying to develop an update to improve on the Kin Two. I currently am interested in getting the TWOm when my contract expires but there is a dealbreaker for me, which is that the phone does not alert you when you have a missed call. I know there are other annoying flaws (pointed out in details at the verizon forums by fisharefriends), but this is the only flaw I cannot deal with.
I do not know what is possible of being changed/edited, but I think mcdietz should focus on implementing basic functions that are currently not on the Kin Two phone, but are on other simple lower spec feature phones.
Click to expand...
Click to collapse
Implementing missing features.. That's a good start. Also, would It be possible to make it be USB device (so you can go into the phone and let's say.. change the default themes).
@mcdietz
Humm, i installed all those downloads long time ago (i guess when posted or before), but didnt tested the drivers with the APX connection.
It worked with errors in linux connection to the usb (got device errors while reading from the USB device) and didnt worked with virtual machine (though vmware detected it).
On the other hand, it worked ok in a win7 real machine and got the driver installed.
I tried to flash android on the device, using the provided images (heh, tests...) and nvflash. But you always get an error on the first try and then, in further attempts you get a "Starting flash" message loop which does nothing.
Same results if you try to do "nvflash --get-partitions" (stuck at 2nd attempt).
You may thing that it's a non working thing, but if you dont connect the device, nvflash.exe it outputs that there is no USB device connected.
A little weird...
I would want to have android at the kin (as i think that has more future than our wince version, looking @ tegra forums) and anyway, if we can somehow read/write the phone roms, we can made a backup from the current OS.
Installed the same tools on linux (native, no emulation) and the flash option didnt worked here either (normal / root user).
Code:
./nvflash --getpartitiontable test.log
outputs (if no phone connected)
Nvflash started
no usb phone found
Click to expand...
Click to collapse
outputs (if Kin on APX connected)
Nvflash started
rcm version 0X4
Command send failed (usb write failed)
Click to expand...
Click to collapse
in the first attempt. Then if called again, seems to get frozen on "Nvflash started" message.
Maybe the recovery has no way to get that data....
Windows Phone Connector?
has anyone tried using the program WP7 connector for the KIN? it works with the zune hd so why not the KIN?
Mmm just to inform....
This is what (physically) happens when the Kin is on the nvflash attempts. Phone must be just booted (not previous nvflash attempt in this boot).
Code:
PC <- Kin: 80 30 18 16 B9 E8 00 00
PC -> Kin: [1028 bytes of data]
Pc <- Kin: 04 00 00 00
PC -> Kin: [39252 bytes of data]
Seems like the response we get (rcm 0x04000000), and the next writing is done with the device autolocked, so last PC -> Kin fails.
Further attempts do not try the same procedure but directly send the last 39252 packet again, failing and getting stuck.
Using some selfmade software (cause no other works so far), i repeated the same procedure, changing the first "byte pack" to send a lame pack, and this is the output:
Code:
# ./kingateway
Opening the controller
Checking for kernel attaching
Claiming the interface
Reading from the Kin.
Received data. 8 bytes. Content:
80 30 18 16 B9 E8 00 00
Writing [02 01 00 00] to the Kin.
Reading Kin response.
Received data. 4 bytes. Content:
08 00 00 00
Writing again to the Kin
KinGATEWAY:: Error while writing to the KIN. Error Code is -9 EXITING.
So in short, fails again (haha, expected...really), but the second response from the kin is not "0400...00" but "08 00 ... 00" meaning a rcm 0x0800..000 or whatever that means.
The above error ("autolock"), tagged as Error code "9" on the program, is a integrity-defense method from the kin, not for the flashing issue but from the "command sent" over usb, which is wrong or unknown on how to operate, and is called "Endpoint Stall". Is a way to express "You'r doing it wrong and i wont hear you again".
One of my ideas is that this version of nvflash is not what was used to operate with the kin and all we get are not errors or devil's corporation actions but uncompatibility protections.
What we need, from my point of view is the Tegra SDK and/or a document where the responses from an APX device are listed (like 0x04000 is "wrong certificate" and 0x08000 is "certificate too short", etc), so we know what it's telling to us. Maybe it's easier to contact nVidia for "old" SDKs than roms...
i hate to be a party crasher but i think this thread needs to be a bumped? why did this thread randomly die? maybe i'm missing something.
I believe it died because johnkussack doesn't have a working kin right now and I don't believe anyone else here wants to try things that may "brick" their phone (I'm one of them). I'm currently trying to buy another kin two (or, uh two), then I'll definitely be digging deeper into those. I may try a hardware route on one and a software route on the other.
This is definitely the most exciting thread the kin two section of xda!
It's been a while but I now have a working KIN device and can continue my efforts. Using the resume mode command to try and force nvflash to write to the kin it displayed a message that said "writing" and then displayed "Failed to perform the following commands: create". It's been a PITA but I feel I will get something written to the device soon.
dezgrz said:
It's been a while but I now have a working KIN device and can continue my efforts. Using the resume mode command to try and force nvflash to write to the kin it displayed a message that said "writing" and then displayed "Failed to perform the following commands: create". It's been a PITA but I feel I will get something written to the device soon.
Click to expand...
Click to collapse
before doing what i lastly underlined, considering what i underlined first... i suggest that you do the reading part, relating to the partition listing.
Just a safe way to find out if the experiments work. Then you can write... with a bit of safety on your side. I mean... you know that testing things writing could not be the best idea on the brikings
Ok guys, I'm trying to look for the product code registry to change it because every time I restore the system it goes back to the original one which from an operator and I'd like to have country variant one. Anyone knows where this registry is?
And the other thing is, how could we add our operator so the roaming triangle is removed?
Thank you guys!
Hello @skyleth,
The product code is never mentioned in the registry.
If the Windows Device Recovery Tool detects normally a Lumia device connected in universal serial bus (USB) on the computer where it is installed, it will then ask you, since its user interface (UI), to select it.
Thus, are retrieved and exploited, by the software, some informations from the Lumia device. Among these, note the presence of a string value representing the product code, written in a file named product.dat, stored in a path of the device provisioning partition (DPP).
Then, the Windows Device Recovery Tool software compares this string value with those on the Microsoft Azure repository servers, to determine which package should it download. After finding this answer, it downloads, itself, a file with the extension *.vpl (variant packing list), which will be stored in a path, intended for this, of the %ProgramData% environment variable of the computer.
In the same time, the Windows Device Recovery Tool software displays, among other things, an Install software button. Once passed the three boring steps directly following the pressing this button, the package download starts. This involves several files of a few kilobytes (KB) and a *.ffu file (full flash update) of more or less than 3 gigabytes (GB), that will be stored from the same path where the *.vpl file is already previously downloaded.
Then, the Windows Device Recovery Tool software checks that the charge level of the battery of Lumia device is of 25% minimum, then sends a command to it to rebooting it immediately in the flash mode. The software checks the status of the anti-theft protection and, that it is enabled or disabled, starts the package installation.
This involves several steps, such as for example the cyclic redundancy check (CRC) of the downloaded files, the root key hash (RKH) control of Lumia device and of *.ffu file, or Platform ID control. However, list all the steps would be much too long.
The installation process completed correctly, the Windows Device Recovery Tool software sends a command to the Lumia device to rebooting it normally, thus initiating, a few seconds later, the out-of-box experience (OOBE).
If you want to change the product code writed in the device provisioning partition, you can do this easily by using the thor2 program (provided with Windows Device Recovery Tool software), by executing the thor2 -mode uefiflash -ffufile "Path\Of\FFU\File.ffu" -productcodeupdate 059x -skip_flash -reboot command.
Best regards,
Thank you, it worked! I'm going to try and see if and update pops up and fix the roaming triangle
WARNING: Trying this may brick your phone! DO IT AT YOUR OWN RISK!
I'll attach the package that you need to debrand your Lumia 1520 AT&T here.
The procedure is the same as Lumia 640 RM-1073, but use files for Lumia 1520 instead.
GUIDE: https://forum.xda-developers.com/windows-phone-8/general/brand-att-lumia-640-lte-t3294971
You must downgrade your phone to WP8.1 Stock. After you debrand your phone, you can flash your phone to RM-937/938/939.
Unfortunately, only RM-938 firmware tested and worked on Lumia 1520 RM-940, flashing RM-937 will get stuck in Flight Mode. I haven't tested the RM-939 firmware. Since I don't have a Lumia 1520 RM-940, I couldn't grab files that modify the PLAT ID back for RM-940.
As for Lumia 830 RM-983 and Lumia 640 XL RM-1062, I have no idea.
hikari_calyx said:
WARNING: Trying this may brick your phone! DO IT AT YOUR OWN RISK!
I'll attach the package that you need to debrand your Lumia 1520 AT&T here.
The procedure is the same as Lumia 640 RM-1073, but use files for Lumia 1520 instead.
GUIDE: https://forum.xda-developers.com/windows-phone-8/general/brand-att-lumia-640-lte-t3294971
You must downgrade your phone to WP8.1 Stock. After you debrand your phone, you can flash your phone to RM-937/938/939.
Unfortunately, only RM-938 firmware tested and worked on Lumia 1520 RM-940, flashing RM-937 will get stuck in Flight Mode. I haven't tested the RM-939 firmware. Since I don't have a Lumia 1520 RM-940, I couldn't grab files that modify the PLAT ID back for RM-940.
As for Lumia 830 RM-983 and Lumia 640 XL RM-1062, I have no idea.
Click to expand...
Click to collapse
I think I have been looking for this. Is this the plat/smbios files? I have branded a 32GB RM-937 to a RM-940 for testing LTE connectivity but could not locate the plat ID file to Unbrand it back...fyi I have the RM-940 Plat ID files.
Edit: Also you can take it out of flight mode (RM-940 unbranded) by loading back and updating its NVI settings via the modem configuration NVI files of the RM-940 FFU.
Attached are all the ATT platform cabs I had if anyone needs.
roll back to factory firmware with wdrt,
make a firmware dump using the desired platform id RM-XXX.FFU introduction of the following commands:
Code:
thor2 -mode ffureader -ffufile "RM-XXX.ffu" -dump_partitions -filedir c:\
to unlock the bootloader using wpinternals
switch the device to mass storage mode
using the EMMC raw tool (make a backup of all the mass storage partitions), write the plat.bin (if you do not know how to do it, it is better not to do it, if you want to ask me in a personal message)
restart your device and flash it using wpinternals: efiesp.bin, mainos.bin, data.bin.
Blue screen is not scary!(BSOD) flash with wpinternals RM-XXX.ffu!
EMMC raw tool can be used to format and unbrick EMMC ?
augustinionut said:
EMMC raw tool can be used to format and unbrick EMMC ?
Click to expand...
Click to collapse
Format using EMMCrawtool no, I described a method of substitution of partition of memory.
The program detects only Qualcomm MMC Storage devices in 9006 mode
A small instruction and the program itself on the Russian forum
Goodbye ATT
nate0 said:
I think I have been looking for this. Is this the plat/smbios files? I have branded a 32GB RM-937 to a RM-940 for testing LTE connectivity but could not locate the plat ID file to Unbrand it back...fyi I have the RM-940 Plat ID files.
Edit: Also you can take it out of flight mode (RM-940 unbranded) by loading back and updating its NVI settings via the modem configuration NVI files of the RM-940 FFU.
Attached are all the ATT platform cabs I had if anyone needs.
Click to expand...
Click to collapse
thankyou so much, I had given up hope of removing the rm-940 firmware until I saw these files. An hour later my beloved 1520 is a normal phone ...yipppeee thanks HEAPS!
Regards
Elmarko
hikari_calyx said:
WARNING: Trying this may brick your phone! DO IT AT YOUR OWN RISK!
I'll attach the package that you need to debrand your Lumia 1520 AT&T here.
The procedure is the same as Lumia 640 RM-1073, but use files for Lumia 1520 instead.
GUIDE: https://forum.xda-developers.com/windows-phone-8/general/brand-att-lumia-640-lte-t3294971
You must downgrade your phone to WP8.1 Stock. After you debrand your phone, you can flash your phone to RM-937/938/939.
Unfortunately, only RM-938 firmware tested and worked on Lumia 1520 RM-940, flashing RM-937 will get stuck in Flight Mode. I haven't tested the RM-939 firmware. Since I don't have a Lumia 1520 RM-940, I couldn't grab files that modify the PLAT ID back for RM-940.
As for Lumia 830 RM-983 and Lumia 640 XL RM-1062, I have no idea.
Click to expand...
Click to collapse
Hi hikari-calyx, I just recently picked up a Lumia 1520 for free. I followed the steps to debrand but then wanted to upgrade to WIN10 (well attemping to). Phone boots but is on Win8. Prior to this I unlocked bootloader and gained root access. However now when I use Windows Phone Internals, it tells me my phone is: RM-938_nam_canada_104, product code 059T5X8, firmware version 1028.3534.1343.0000. I apparently somehow relocked my bootloader during this process of de-branding. I get an error code in WPI stating error 0x1304:invalid platform. I am fine with staying on this Canadian/America's firmware but want to update to WIN10, if it is at all possible, and would love to have bootloader unlocked and root. I am very very new to WIN phone but have been rooting flashing custom roms on android for 10+ years. I am stumped as to what to do, if it possible to upgrade to WIN10 mobile as well as unlock bootloader. I realize I am asking a slew of questions, but I am stumped with this one. I have spent the last 8 hours reading up on getting the bootloader unlocked and root access and then hit this snag. Any help is greatly appreciated. Thank you
PS: I tried to push the original AT&T cab files from post 2 (thank you for providing those) in hopes I could then get my product ID and phone to match at RM-940 (currently it shows (RM-938 on Canada/Americas firmware) but it was a no go. In phone update (settings on phone) it shows updating but then gets an error code of ERROR: 0x80188306. I have tried several different attempts to reprogram the ATT cab files for RM-940 to no avail. Still stumped. Any suggestions or assistance is appreciated, thank you.
PS2: I have also tried to manually push the RM-940/1520 ffu file to the device under iutool -v -p 1520 (my folder with the firmware) and all a no go.
nate0 said:
I think I have been looking for this. Is this the plat/smbios files? I have branded a 32GB RM-937 to a RM-940 for testing LTE connectivity but could not locate the plat ID file to Unbrand it back...fyi I have the RM-940 Plat ID files.
Edit: Also you can take it out of flight mode (RM-940 unbranded) by loading back and updating its NVI settings via the modem configuration NVI files of the RM-940 FFU.
Attached are all the ATT platform cabs I had if anyone needs.
Click to expand...
Click to collapse
Hi Nate0, how do I go about loading back and updating its NVI settings via the modem configuration NVI files? Thank you
ozzmanj1 said:
Hi Nate0, how do I go about loading back and updating its NVI settings via the modem configuration NVI files? Thank you
Click to expand...
Click to collapse
There are a few ways. One is to use thor2 and send the json files manually. I have had mixed luck/reactions with devices by doing that. The Second way is to put the nvi files manually on the phone, but make the parent/master nvi file a version higher than stock firmware. Then simply use thor2 and the variant ffu you have to do an nviupdate skip flash. The other way only works in mass storage mode, but with Nokia/Microsoft/Lumia phones they went hardcore locking down the QC partitions so that only certain values can be touched by the nvupdater package at the OS level. So in order to update the nv settings using QPST or other modem modifying software you have to authenticate with the nvupdate api. This means someone would need to create a third party api to interface and bypass of trick the qpst software into authenticating or trick the phone into thinking it is being updated by the nvupdater package.
nate0 said:
There are a few ways. One is to use thor2 and send the json files manually. I have had mixed luck/reactions with devices by doing that. The Second way is to put the nvi files manually on the phone, but make the parent/master nvi file a version higher than stock firmware. Then simply use thor2 and the variant ffu you have to do an nviupdate skip flash. The other way only works in mass storage mode, but with Nokia/Microsoft/Lumia phones they went hardcore locking down the QC partitions so that only certain values can be touched by the nvupdater package at the OS level. So in order to update the nv settings using QPST or other modem modifying software you have to authenticate with the nvupdate api. This means someone would need to create a third party api to interface and bypass of trick the qpst software into authenticating or trick the phone into thinking it is being updated by the nvupdater package.
Click to expand...
Click to collapse
Gotcha. I am very new to Windows Phone. I was given a Lumia 1520 that is apparently got an issue. Its an AT&T RM-940, when I run WPI, it reads:
Lumia RM-938 - NAM CANADA 1040
Product Code: 059T5X8
I have tried several times to repair it but a lot of times get a Product ID mismatch. Phone is on W8, not 8.1. Version 8.0.10517.150. I am totally stumped with what I need to do to fix this. I was told that it was on US AT&T firmware 02540.00019.14484.37028, but was flashed with modded cabs for USA Tmobile. I did find the AT&T cabs and have attempted to push them but it fails every time. Is this phone toast, or is there any solution? I appreciate your help and time. Thank you
Edit, how difficult would it be to push the nvi file with a parent/master nvi file higher then the above firmware version? I have no clue on how to do that or what the commands would be. I am willing to totally give it a shot with the commands and how I would do that. Appreciate any insight, thank you in advance.
Edit : I am not sure if this is what I need to do, but this did not work for me:
thor2 -mode uefiflash -ffufile "C:\the place of the ffu\file name.ffu" -do_full_nvi_update -do_factory_reset
Edited to match what my file directory was, but got this error:
Debugging enabled for uefiflash
Initiating FFU flash operation
WinUSB in use.
isDeviceInNcsdMode
Resp from device
Json message GetVersion send/receive failed
isDeviceInNcsdMode is false
Device mode 1 Normal mode
[THOR2_flash_state] Pre-programming operations
Disable timeouts
Detecting UEFI responder
Device is not in Lumia UEFI mode
Device mode get failed, mode is 1
Connection lost, trying to re-connect
Rebooting to the normal mode...
Rebooting from the WP/MMOS failed.
Operation took about 5.00 seconds.
THOR2_ERROR_TO_COMMUNICATE_WITH_DEVICE
THOR2 1.8.2.18 exited with error code 84102 (0x14886)
Again, not sure what I am missing.
ozzmanj1 said:
Gotcha. I am very new to Windows Phone. I was given a Lumia 1520 that is apparently got an issue. Its an AT&T RM-940, when I run WPI, it reads:
Lumia RM-938 - NAM CANADA 1040
Product Code: 059T5X8
I have tried several times to repair it but a lot of times get a Product ID mismatch. Phone is on W8, not 8.1. Version 8.0.10517.150. I am totally stumped with what I need to do to fix this. I was told that it was on US AT&T firmware 02540.00019.14484.37028, but was flashed with modded cabs for USA Tmobile. I did find the AT&T cabs and have attempted to push them but it fails every time. Is this phone toast, or is there any solution? I appreciate your help and time. Thank you
Edit, how difficult would it be to push the nvi file with a parent/master nvi file higher then the above firmware version? I have no clue on how to do that or what the commands would be. I am willing to totally give it a shot with the commands and how I would do that. Appreciate any insight, thank you in advance.
Edit : I am not sure if this is what I need to do, but this did not work for me:
thor2 -mode uefiflash -ffufile "C:\the place of the ffu\file name.ffu" -do_full_nvi_update -do_factory_reset
Edited to match what my file directory was, but got this error:
Debugging enabled for uefiflash
Initiating FFU flash operation
WinUSB in use.
isDeviceInNcsdMode
Resp from device
Json message GetVersion send/receive failed
isDeviceInNcsdMode is false
Device mode 1 Normal mode
[THOR2_flash_state] Pre-programming operations
Disable timeouts
Detecting UEFI responder
Device is not in Lumia UEFI mode
Device mode get failed, mode is 1
Connection lost, trying to re-connect
Rebooting to the normal mode...
Rebooting from the WP/MMOS failed.
Operation took about 5.00 seconds.
THOR2_ERROR_TO_COMMUNICATE_WITH_DEVICE
THOR2 1.8.2.18 exited with error code 84102 (0x14886)
Again, not sure what I am missing.
Click to expand...
Click to collapse
Without knowing a whole lot about your situation and phone I would say yes It can be fixed. You can even get access to the PLAT partition mount it and edit the platform file that houses the identity so that it matches the correct model... However there is no real way to tell which model it is if it has both AT&T FW but identifies as the RM-038. What you should ask yourself is what do you want to do with the phone. If you want to use it on a carrier then decide which fw to go with after that. Pushing the cabs for the PLAT partition that have the AT&T product ID will work, but only if the firmware version you send is newer. You cannot roll back to earlier version. So it gets tricky with variant firmwares because their fw version numbers may vary slightly and if the vary a lot you are stuck doing things manually. To put the nvi files on the phone manually and update the NVI settings with thor2 is not completely simple. What I would do is flash it with WPInternals to whatever variant the PLAT ID identifies with (in the case RM-938) Let it boot up and use it that way, if you have issues you alter the PLAT ID again back to an AT&T model and flash that firmware back.
I had to dig up old info I had....
To flash a nvi json file would be like this below:
The nvi file is in json format and the version number is partial way down in the file something like line 80 or something, I cannot entirely remember but not all NVI files are the same.... You would need to find a copy of whatever variant you trying to send to to know what version number to start with so that you can alter the version number to be higher. So you are sending a local file from PC to the phone. The phone has to be booted in flash mode and this only works on Lumia phones.
Sends NVIs messages from nvi file to MMOS / label app:
thor2 -mode retail -nvifile "CustomerNvi.nvi"
Sends NVIs messages from nvi file to normal mode / NCSd:
thor2 -mode retail -nvifile "CustomerNvi.nvi -normalmode"
EDIT:
Sorry I pasted the above but there is also here the json file command to. Also I think one command tries to send the messages while the phone is booted and the other while in flash mode. I cannot entirely remember...
Sends JSON messages from JSON file to MMOS / label app:
thor2 -mode rnd -jsonfile "json_messages_file.json"
Sends JSON messages from JSON file to normal mode / NCSd:
thor2 -mode rnd -jsonfile "json_messages_file.json -normalmode"
ozzmanj1 said:
Gotcha. I am very new to Windows Phone. I was given a Lumia 1520 that is apparently got an issue. Its an AT&T RM-940, when I run WPI, it reads:
Lumia RM-938 - NAM CANADA 1040
Product Code: 059T5X8
I have tried several times to repair it but a lot of times get a Product ID mismatch. Phone is on W8, not 8.1. Version 8.0.10517.150. I am totally stumped with what I need to do to fix this. I was told that it was on US AT&T firmware 02540.00019.14484.37028, but was flashed with modded cabs for USA Tmobile. I did find the AT&T cabs and have attempted to push them but it fails every time. Is this phone toast, or is there any solution? I appreciate your help and time. Thank you
Click to expand...
Click to collapse
nate0 said:
I had to dig up old info I had....
To flash a nvi json file would be like this below:
The nvi file is in json format and the version number is partial way down in the file something like line 80 or something, I cannot entirely remember but not all NVI files are the same.... You would need to find a copy of whatever variant you trying to send to to know what version number to start with so that you can alter the version number to be higher. So you are sending a local file from PC to the phone. The phone has to be booted in flash mode and this only works on Lumia phones.
Sends NVIs messages from nvi file to MMOS / label app:
thor2 -mode retail -nvifile "CustomerNvi.nvi"
Sends NVIs messages from nvi file to normal mode / NCSd:
thor2 -mode retail -nvifile "CustomerNvi.nvi -normalmode"
EDIT:
Sorry I pasted the above but there is also here the json file command to. Also I think one command tries to send the messages while the phone is booted and the other while in flash mode. I cannot entirely remember...
Sends JSON messages from JSON file to MMOS / label app:
thor2 -mode rnd -jsonfile "json_messages_file.json"
Sends JSON messages from JSON file to normal mode / NCSd:
thor2 -mode rnd -jsonfile "json_messages_file.json -normalmode"
Click to expand...
Click to collapse
Thank you very much for all your time, I do appreciate it. The phone is on WP8.0. What I would like to ultimately do is have it back on AT&T stock firmware and then upgrade it to WP10. While I am on Tmo, that is fine, I do know the phone is sim unlocked as I put in my sim, and I get HSP+ (3.5G). But that is not a huge deal for me as I would not be using it as a daily phone. BUt yeah, I would like to simply be able to flash it back to full AT&T stock and then update to the latest WP10
I took some screenshots. When the phone is powered up and connected to WPI, it shows one model, but another when rebooted to "unlock bootloader". Please see attached to screenshots
ozzmanj1 said:
Thank you very much for all your time, I do appreciate it. The phone is on WP8.0. What I would like to ultimately do is have it back on AT&T stock firmware and then upgrade it to WP10. While I am on Tmo, that is fine, I do know the phone is sim unlocked as I put in my sim, and I get HSP+ (3.5G). But that is not a huge deal for me as I would not be using it as a daily phone. BUt yeah, I would like to simply be able to flash it back to full AT&T stock and then update to the latest WP10
I took some screenshots. When the phone is powered up and connected to WPI, it shows one model, but another when rebooted to "unlock bootloader". Please see attached to screenshots
Click to expand...
Click to collapse
Ah ok. I too use TMO. What I did with the 1520 while on TMO was I used the RM-938 Firmware. But the only RM-938 models I used were the 32GB models. With the RM-938 the Modem partitions are different and the firmware for that model of phone allowed me to configure NVI settings to that I at least got HD voice while on TMO. Wifi calling and VoLTE never seemed to actually work on W10M but HD voice did. I am not certain if I did or not but I thought I posted some place explaining how I used custom NVI settings in an attempt to get quality cellular usage out of the 1520...
nate0 said:
Ah ok. I too use TMO. What I did with the 1520 while on TMO was I used the RM-938 Firmware. But the only RM-938 models I used were the 32GB models. With the RM-938 the Modem partitions are different and the firmware for that model of phone allowed me to configure NVI settings to that I at least got HD voice while on TMO. Wifi calling and VoLTE never seemed to actually work on W10M but HD voice did. I am not certain if I did or not but I thought I posted some place explaining how I used custom NVI settings in an attempt to get quality cellular usage out of the 1520...
Click to expand...
Click to collapse
Also to note, that if this 1520 you own is indeed a RM-940 from birth even flashing the RM-938 fw won't allow any cool changes to the NV settings like I mentioned. There is a distinct difference in models at that SOC level where one has NVI settings that the other does not and even if you make them identical there are other Firmware level differences I think on the DPP partition or some other place that allowed the RM-938 only to get HD Voice.
nate0 said:
Also to note, that if this 1520 you own is indeed a RM-940 from birth even flashing the RM-938 fw won't allow any cool changes to the NV settings like I mentioned. There is a distinct difference in models at that SOC level where one has NVI settings that the other does not and even if you make them identical there are other Firmware level differences I think on the DPP partition or some other place that allowed the RM-938 only to get HD Voice.
nate0 said:
Also to note, that if this 1520 you own is indeed a RM-940 from birth even flashing the RM-938 fw won't allow any cool changes to the NV settings like I mentioned. There is a distinct difference in models at that SOC level where one has NVI settings that the other does not and even if you make them identical there are other Firmware level differences I think on the DPP partition or some other place that allowed the RM-938 only to get HD Voice.
Click to expand...
Click to collapse
I see. I went back and looked and the device was RM-940 "fro mbirth" and was flashed to RM-938. I am almost positive someone previously attempted to do what you did and it wonked it. Is it difficult to re-apply the AT&T stock firmware? At the moment I get the following errors when attempting to flash the ffu for AT&T RM940 with the emergency files and a "donor" ffu for RM-1085" The errors are, Product ID mismatch or Profile FFU has wrong platform id for connected phone.
Click to expand...
Click to collapse
@ozzmanj1 with regards to the WPI showing two different models, one shows the FW revision/OS level connected. The other shows the device configuration pulled from the Plat and DPP partitions.
I understand. I might have the cab files for the PLAT ID RM-938 that you can push to the phone to match the FW so you can at least upgrade it to WP10M, but I am unsure if that will work while on WP8. Have you tried that yet?
nate0 said:
I understand. I might have the cab files for the PLAT ID RM-938 that you can push to the phone to match the FW so you can at least upgrade it to WP10M, but I am unsure if that will work while on WP8. Have you tried that yet?
Click to expand...
Click to collapse
I have tried to push the plat files for the ATT plat RM940 files but it fails. I am very unfamiliar with thor2 and simply copying and pasting commands I am finding. Never knew about thor2 until the other day. Thank you very much for your help.
EDIT: I did find your post, guessing this is what you did.
**testing** Lumia 1520.3 ROM
I've been working on a custom ROM for the Lumia 1520.3 RM-938 32gb. The variant info for the model I'm working with is below. I wanted to know if there were any users out there US or non-US that would be wanting or willing to test a 1520.3 ROM...
forum.xda-developers.com
I did find the files for your model 32gb from the LumiaFirmware. Do I need to download the nvi files for this?
LumiaFirmware | Download all Lumia firmware And Emergency Files
Download all Lumia firmware!
www.lumiafirmware.com
Download - CustomerNvi_02540.00019.15236.45004_905_4718e5dc65cbeb980b32e2af22af2e1d.nvi
Download - RetailModeNvi_02540.00019.15236.45004_905_10b151222cbcc1dcefc95c481b4e6244.nvi
By the way, I never had a Windows Phone device before this phone. And man, this Lumia 1520 is awesome looking. I would have loved this phone I think back in 2013/2014. I always thought my Nexus 6 was the largest phone (outside the Sony Xperia Z Ultra), but nope, the 1520 is taller and ever so slightly wider.
ozzmanj1 said:
I have tried to push the plat files for the ATT plat RM940 files but it fails. I am very unfamiliar with thor2 and simply copying and pasting commands I am finding. Never knew about thor2 until the other day. Thank you very much for your help.
EDIT: I did find your post, guessing this is what you did.
**testing** Lumia 1520.3 ROM
I've been working on a custom ROM for the Lumia 1520.3 RM-938 32gb. The variant info for the model I'm working with is below. I wanted to know if there were any users out there US or non-US that would be wanting or willing to test a 1520.3 ROM...
forum.xda-developers.com
I did find the files for your model 32gb from the LumiaFirmware. Do I need to download the nvi files for this?
LumiaFirmware | Download all Lumia firmware And Emergency Files
Download all Lumia firmware!
www.lumiafirmware.com
Download - CustomerNvi_02540.00019.15236.45004_905_4718e5dc65cbeb980b32e2af22af2e1d.nvi
Download - RetailModeNvi_02540.00019.15236.45004_905_10b151222cbcc1dcefc95c481b4e6244.nvi
By the way, I never had a Windows Phone device before this phone. And man, this Lumia 1520 is awesome looking. I would have loved this phone I think back in 2013/2014. I always thought my Nexus 6 was the largest phone (outside the Sony Xperia Z Ultra), but nope, the 1520 is taller and ever so slightly wider.
Click to expand...
Click to collapse
By far the 1520 was light years beyond all smartphones back then in every way. Like up to 700nits almost in direct sunlight on the LCD. Color profile for complete LCD color control. Big 6in screen. Solid camera of course. One of THE most popular Lumias ever. One of my favorites too.
That post is me sharing Full OS ffu for the 1520.3 (RM-938). It won't work for your device. But nvi files can be pulled from any FFU. We can mount partitions from the FFU and pull whatever files we want from them. You need to get the PLAT ID to match the FW/OS version of your phone in order to move forward. I have had your scenario happen to me before, but it has been a while and I cannot remember exactly the best route to go so you can upgrade back to W10M...
What was the error you got when sending the cab file to the phone and can you list the exact cab files you sent? For Plat ID changes there is always 2 cab files that need to be sent....
Hi All !
Given a TOT file, can we edit it (lets say with any hex editor) to change its Anti Roll-Back i.e. ARB value from, say, 00 to 02 or 03?
rizkhan999 said:
Hi All !
Given a TOT file, can we edit it (lets say with any hex editor) to change its Anti Roll-Back i.e. ARB value from, say, 00 to 02 or 03?
Click to expand...
Click to collapse
100% no this is not possible. Change a single bit the signatures get invalid which will brick your device.
Sent from my LG-H815 using XDA Labs
What about hex-editing .IMG files?
steadfasterX said:
100% no this is not possible. Change a single bit the signatures get invalid which will brick your device.
Click to expand...
Click to collapse
Thanks sir. And what about editing ARB version or anything else in the rooted system image .IMG file? Will the signature hurdle be encountered here as well, or not?
rizkhan999 said:
Thanks sir. And what about editing ARB version or anything else in the rooted system image .IMG file? Will the signature hurdle be encountered here as well, or not?
Click to expand...
Click to collapse
Check my post here: http://tinyurl.com/antirollg4
If you go through the details at the beginning and follow the links you may understand better.
In short: the ARB is implemented in the bootloader and to be more clear in the certificates within. There is 100% no chance to change this other then when you break the signature algo or find a bug in the implementation.
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Check my post here: http://tinyurl.com/antirollg4
If you go through the details at the beginning and follow the links you may understand better.
In short: the ARB is implemented in the bootloader and to be more clear in the certificates within. There is 100% no chance to change this other then when you break the signature algo or find a bug in the implementation.
Click to expand...
Click to collapse
Okay sir. But really sorry to take from your precious time, actually what I am trying to do is to change (via hex editor) the echo value of 1 to 0 wherever the following instances occur in the rooted system image .IMG files:
/sys/devices/system/cpu/cpu5/online
/sys/devices/system/cpu/cpu6/online
/sys/devices/system/cpu/cpu7/online
This is in the spirit to disable two big cores.
But I have the following questions regarding this:
1. Would the IMG file still be valid and correctly flashable after changing the above mentioned values from 1 to 0?
2. Would the changes be effective only after the phone has booted into the OS or... from the powering-on of the phone and onwards?
3. What is "cpu7" in IMG files, while G4 is only hex-core (i.e. cpu1 to cpu6)?
rizkhan999 said:
Okay sir. But really sorry to take from your precious time, actually what I am trying to do is to change (via hex editor) the echo value of 1 to 0 wherever the following instances occur in the rooted system image .IMG files:
/sys/devices/system/cpu/cpu5/online
/sys/devices/system/cpu/cpu6/online
/sys/devices/system/cpu/cpu7/online
This is in the spirit to disable two big cores.
But I have the following questions regarding this:
1. Would the IMG file still be valid and correctly flashable after changing the above mentioned values from 1 to 0?
2. Would the changes be effective only after the phone has booted into the OS or... from the powering-on of the phone and onwards?
3. What is "cpu7" in IMG files, while G4 is only hex-core (i.e. cpu1 to cpu6)?
Click to expand...
Click to collapse
sys files are created and changed on boot you can't change them in the system image even if they would be there. Those are created and changed in the ram disk which is part of the boot image.
You can't change the boot image as this makes the signature invalid .
You can change the system image especially on LL when rooted. Here you can implement the disabling of the cores e.g. implemented as an init script.. but it will have an effect after booted only.
The boot process will still use all cpu cores.
You have no cpu7 on a g4. The reason is that it starts from 0 to count. Cpu0 to cpu3 are the first 4 cpus.
there is success reported with many devices to install the unofficial official v29 beta for nougat. This beta contains at least for the boot the disabling of the big cores but I don't know if your device model is supported by it or not but check this maybe.
Sent from my LG-H815 using XDA Labs
steadfasterX said:
sys files are created and changed on boot you can't change them in the system image even if they would be there. Those are created and changed in the ram disk which is part of the boot image.
You can't change the boot image as this makes the signature invalid .
You can change the system image especially on LL when rooted. Here you can implement the disabling of the cores e.g. implemented as an init script.. but it will have an effect after booted only.
The boot process will still use all cpu cores.
You have no cpu7 on a g4. The reason is that it starts from 0 to count. Cpu0 to cpu3 are the first 4 cpus.
there is success reported with many devices to install the unofficial official v29 beta for nougat. This beta contains at least for the boot the disabling of the big cores but I don't know if your device model is supported by it or not but check this maybe.
Click to expand...
Click to collapse
By LL i guess you mean LP (lollipop).
In rooted system image IMG files as well as in the TOT files, there is a mention of seven cpu's from cpu1 through cpu7. And this cpu7 is always mentioned along with cpu5 and cpu6 under the comment of A57 cores. While the rest four are A53 cores. So i wonder what this cpu7 really denotes on a hexcore processor!
I also have h815 (international variant) and using Nougat A29a rom from here. And i have flashed titan kernel with no big cores over it, from the same developer. I recovered this phone from bootloop by initially flashing the 4mb ILAPO FIX TOT file with LGUP. But the traditional TWRP from twrp official website is working fine for me. I didnt have to use custom TWRP that doesnt use two big cores.
Anyways. Thanks alot for all your time and support.
rizkhan999 said:
By LL i guess you mean LP (lollipop).
In rooted system image IMG files as well as in the TOT files, there is a mention of seven cpu's from cpu1 through cpu7. And this cpu7 is always mentioned along with cpu5 and cpu6 under the comment of A57 cores. While the rest four are A53 cores. So i wonder what this cpu7 really denotes on a hexcore processor!
I also have h815 (international variant) and using Nougat A29a rom from here. And i have flashed titan kernel with no big cores over it, from the same developer. I recovered this phone from bootloop by initially flashing the 4mb ILAPO FIX TOT file with LGUP. But the traditional TWRP from twrp official website is working fine for me. I didnt have to use custom TWRP that doesnt use two big cores.
Anyways. Thanks alot for all your time and support.
Click to expand...
Click to collapse
There is no cpu7.. Even no cpu6. The thing is you have to differ between what happens on os site and what on app site.
Some apps like kernel Adiutor starts to count from 1 instead but in the background it's still from 0..5
SoC: Qualcomm Snapdragon 808 MSM8992
CPU: 2x 1.8 GHz ARM Cortex-A57, 4x 1.44 GHz ARM Cortex-A53, Cores: 6
0-3 are a53
4-5 are a57
Sent from my LG-H815 using XDA Labs
steadfasterX said:
There is no cpu7.. Even no cpu6. The thing is you have to differ between what happens on os site and what on app site.
Some apps like kernel Adiutor starts to count from 1 instead but in the background it's still from 0..5
SoC: Qualcomm Snapdragon 808 MSM8992
CPU: 2x 1.8 GHz ARM Cortex-A57, 4x 1.44 GHz ARM Cortex-A53, Cores: 6
0-3 are a53
4-5 are a57
Click to expand...
Click to collapse
Actually the file /etc/dir/init.qcom.post_boot.sh does contain mentions of only six cores from cpu0 through cpu5. However all the IMG and TOT files contain mentions of seven cores from cpu1 through cpu7.
The first screenshot shows one of such mention of all seven cores, as highlighted in it. The second screenshot shows the mention of cpu5, cpu6 and cpu7 under A57 cores which shows that cpu7 is also treated as a big core. That's why I was asking what this seventh core mean in a hex-core device?
rizkhan999 said:
Actually the file /etc/dir/init.qcom.post_boot.sh does contain mentions of only six cores from cpu0 through cpu5. However all the IMG and TOT files contain mentions of seven cores from cpu1 through cpu7.
The first screenshot shows one of such mention of all seven cores, as highlighted in it. The second screenshot shows the mention of cpu5, cpu6 and cpu7 under A57 cores which shows that cpu7 is also treated as a big core. That's why I was asking what this seventh core mean in a hex-core device?
Click to expand...
Click to collapse
Its there but it's useless.
Mount the system image instead of using a hexeditor then grep on the files like this
grep -r cpu7 /path/
I can't verify this atm as I'm on vacation but I strongly believe this is just a leftover from another device made by LG. Keep in mind that developers are lazy and so they copy things which is ok but this also means they may copy too much without verifying . Actually this doesn't harm anything in this case (if cpu6 or 7 are not there an error is thrown and maybe shown in dmesg but that's all) so they may just don't care.
.
steadfasterX said:
100% no this is not possible. Change a single bit the signatures get invalid which will brick your device.
Click to expand...
Click to collapse
I tried flashing my H815 with H810 10o TOT file using LGUP. It gave out the invalid file error as expected. Then I modified the mentioned H810 10o TOT file by replacing all occurances of H810 with H815 and flashed it on H815 using LGUP. The phone got bricked, as also expected and became dead. No display, no download mode.
Then when I long pressed the power and vol down buttons together the phone got detected as QFUSE in Device Manager but it happened only once.
Now when I long press power and vol down buttons, the phone always vibrates but remains undetected.
I have tried this memory card unbrick method as well as tried installing qualcomm drivers after uninstalling all phones drivers using this guide but same status.
Any other unbrick guide that may work?
rizkhan999 said:
I tried flashing my H815 with H810 10o TOT file using LGUP. It gave out the invalid file error as expected. Then I modified the mentioned H810 10o TOT file by replacing all occurances of H810 with H815 and flashed it on H815 using LGUP. The phone got bricked, as also expected and became dead. No display, no download mode.
Then when I long pressed the power and vol down buttons together the phone got detected as QFUSE in Device Manager but it happened only once.
Now when I long press power and vol down buttons, the phone always vibrates but remains undetected.
I have tried this memory card unbrick method as well as tried installing qualcomm drivers after uninstalling all phones drivers using this guide but same status.
Any other unbrick guide that may work?
Click to expand...
Click to collapse
ok you hard bricked (hard not hard-hard which means you can recover).
you can recover from that hard brick by using QFIL and the RIGHT files (beware of the dragons!)
download & install QPST: https://www.androidfilehost.com/?fid=673368273298970431
download & install QPST drivers: https://www.androidfilehost.com/?fid=673368273298970430
download & extract H815 QFIL recover files: https://www.androidfilehost.com/?fid=745425885120762427
Start QFIL.exe within the Qualcomm QPST installation folder
Select Build Type: > Flat <
Browse to > prog_emmc_firehose_8992_lite.mbn <
Click Load XML button and select: > rawprogram0.xml <
then: > patch0.xml <
Take a deep breath......
Click > Download <
Wait until it finishes. Unplug USB, remove battery, put battery back and go into download mode for a full recovery by flashing a h815 KDZ
sfX
steadfasterX said:
ok you hard bricked (hard not hard-hard which means you can recover).
you can recover from that hard brick by using QFIL and the RIGHT files (beware of the dragons!)
download & install QPST: https://www.androidfilehost.com/?fid=673368273298970431
download & install QPST drivers: https://www.androidfilehost.com/?fid=673368273298970430
download & extract H815 QFIL recover files: https://www.androidfilehost.com/?fid=745425885120762427
Start QFIL.exe within the Qualcomm QPST installation folder
Select Build Type: > Flat <
Browse to > prog_emmc_firehose_8992_lite.mbn <
Click Load XML button and select: > rawprogram0.xml <
then: > patch0.xml <
Take a deep breath......
Click > Download <
Wait until it finishes. Unplug USB, remove battery, put battery back and go into download mode for a full recovery by flashing a h815 KDZ
sfX
Click to expand...
Click to collapse
Awesome. There is some progress. The screenshot shows that my phone is properly connected in QDloader 9008 mode but the QFIL during the flash process gives the error that the phone is not in the FireHose mode. Any ideas?
rizkhan999 said:
Awesome. There is some progress. The screenshot shows that my phone is properly connected in QDloader 9008 mode but the QFIL during the flash process gives the error that the phone is not in the FireHose mode. Any ideas?
Click to expand...
Click to collapse
well.. yea the 9008 mode is a PITA. The thing is 9008 is not 9008.. plus that mode is very sensitive: means u need to know some things:
timing: when you wait too long (lets say.. 5 min or longer) the 9008 mode will stop working. The device gets still detected but QFIL will not work.
so best is: prepare QFIL so you just need to click the Download button and before actually doing so pull out battery , unplug USB and plugin again. once detected in QFIL press download.
Usually u have at least 1 min or even more after the device brings up the 9008 mode so no need to hurry that much but if you wait too long it will fail.
second: when you used QFIL once you HAVE to reboot bc otherwise the firehose programmer will not fit into memory anymore and so it will fail as well.
always start the 9008 mode fresh for every try.
third: best is to pull out the battery and just plugin the USB cable. If you device is detected this way in QFIL: perfect! do it like this as this can be different from the result when the battery is in and its recommended to have not the battery in for the 9008 mode actions
fourth: last but not least: the only 100% way to bring up a 100% valid 9008 mode is by either erasing a partition (u cant do that atm) or by shorten 2 PINs on the mainboard.
this will be the last option when all the above wont help you out.
(All the above is the result of a looooong try & error process I've done during my unlocking attempts)
sfX
steadfasterX said:
well.. yea the 9008 mode is a PITA. The thing is 9008 is not 9008.. plus that mode is very sensitive: means u need to know some things: sfX
Click to expand...
Click to collapse
Thanks alot for your detailed reply. My phone has stopped getting detected by computer, as it happened a few days ago as well. And no vibrations either. So I have left it with battery removed. Will try it again after a few days. May be it starts getting detected again.
steadfasterX said:
download & extract H815 QFIL recover files: https://www.androidfilehost.com/?fid=745425885120762427
Click to expand...
Click to collapse
Btw do you also have qfil recover files of h810 and h811 variants? Can u plz upload them too? Thanx in advance.
No success still...
steadfasterX said:
well.. yea the 9008 mode is a PITA. The thing is 9008 is not 9008.. plus that mode is very sensitive: means u need to know some things:
Click to expand...
Click to collapse
Sine the phone was undetected for days, I kept it in the freezer for the night. And it has started getting detected in 9008 mode again . But I have tried it flashing while keeping the mind all the instructions, like connecting it without the battery and with battery as well, and keeping the QFIL ready and pressing the Download button as soon as the device gets detected, but I have received the same error that the phone is not in the firehose mode.
The QFIL version you shared was 2.7 with build 425. I have also tried build 437 as well and got the following error (log attached herewith):
ERROR: OpenPort:4197 It took 160.07800000 seconds to open port. Which is longer than 3.000. This indicates your target is not stable
I also tried the build 422 which gave out the same error of phone not being in the firehose mode eventhough I disconnected and connected it afresh. I think the phone is either not in the pure 9008 mode (as you also said) or that it enters the mode for a very short period of time so that the QFIL flashing fails.
Any solutions now?
rizkhan999 said:
Sine the phone was undetected for days, I kept it in the freezer for the night. And it has started getting detected in 9008 mode again . But I have tried it flashing while keeping the mind all the instructions, like connecting it without the battery and with battery as well, and keeping the QFIL ready and pressing the Download button as soon as the device gets detected, but I have received the same error that the phone is not in the firehose mode.
The QFIL version you shared was 2.7 with build 425. I have also tried build 437 as well and got the following error (log attached herewith):
ERROR: OpenPort:4197 It took 160.07800000 seconds to open port. Which is longer than 3.000. This indicates your target is not stable
I also tried the build 422 which gave out the same error of phone not being in the firehose mode eventhough I disconnected and connected it afresh. I think the phone is either not in the pure 9008 mode (as you also said) or that it enters the mode for a very short period of time so that the QFIL flashing fails.
Any solutions now?
Click to expand...
Click to collapse
Then your device may is in the R.I.P. 9008 mode. Devices who have the mainboard issue goes through several steps. The last one is being detected as 9008 only without any chance to use qfil anymore.
Only fix known is written in my bootloop fix it list (see signature) and means replacing the mainboard or for the advanced ones doing some soldering.
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Then your device may is in the R.I.P. 9008 mode. Devices who have the mainboard issue goes through several steps. The last one is being detected as 9008 only without any chance to use qfil anymore.
Click to expand...
Click to collapse
Yeah thats possible. Because the phone is getting detected in 9008 only with the battery now. While without the battery it either gives the blank battery with ? indication, while sometimes the blue screen as well (similar to G3's Blue Screen of Death).
Only fix known is written in my bootloop fix it list (see signature) and means replacing the mainboard or for the advanced ones doing some soldering.
Click to expand...
Click to collapse
Do you have any link to any of such kind of soldering tutorial? I can have it done from any hardware guy in the market.
rizkhan999 said:
Yeah thats possible. Because the phone is getting detected in 9008 only with the battery now. While without the battery it either gives the blank battery with ? indication, while sometimes the blue screen as well (similar to G3's Blue Screen of Death).
Do you have any link to any of such kind of soldering tutorial? I can have it done from any hardware guy in the market.
Click to expand...
Click to collapse
I have updated my bootloop fix it list. Scroll down to the Advanced disassemble method(s)
Sent from my LG-H815 using XDA Labs
I recently bought Asus Zenfone, because here in Ukraine is war, so I want small device with Windows (electricity often is off here because rockets fall on our electrric infrastructure etc).
So I've bought Asus Zenfone 2 used (it costed 16,25$). It came without accumulator, and 1/3 screen working. So I went to radio-market to buy new battery, it costed + ~10.25$ + 2,5$ to install battery. Then I've bought new touchscreen for it for ~22,5$, plus payed ~6,25$ to install it. Then around 7,5$ to restore battery connectors (on device and accumulator). So finally it worked, and wanted to see how to install Windows on Zenfone. Sure, if I had possibility to buy anywhere Zenfone better, new, not used, - I'ld do it, but it is not that easily available, just like any other Intel smartphone.
So, I started reading - how to make my device rooted. I don't understand how to get root. I found on wikipedia, that rooting is different from unlocking bootloader, and realized - yes. I need to unlock bootloader, and to boot from external flash-disk and install windows, or at least - new kernel with KVM support. I used pn my Android (non intel) Limbo x86 emulator, it can run some old windows 98 etc, maybe even xp, never win 2000, and if it runs win-7 or win-8 - it is so terribly slow. So I decided to buy Asus Zenfone. As in KVM mode I can send commands to CPU directly, and hope this Windows works much faster than in emulator. I hope just at least to run Windows XP on it, I need to code some C# code, so that Andorid phone is not only for mp3-playing, internet on the go and make calls, but to learn, study and to work. I don't know why Microsot, Intel and other companies don't like Intel CPUs in mobiles. They could do it if they wanted. I like WIndows because most programs are for Windows. And I want desktop x86 windows also on every mobile, intead of all Androids.
Anyway, What I tried to with my Zenfone. I found one amazing experience - that our hero and inspirer (ley God blesses him, maybe he will work in Intel/AMD/Asus/Microsoft etc to make more newer KVM kernels for future x86 phones with windows) - so Ycavan made KVM for Asus Zenfone 2. Great, I've read his thread - https://forum.xda-developers.com/t/...0-with-kvm-bridge-compiled-need-help.3145055/ - completely, with pen and paper writing down important information, downloaded all the files, and decided to start flashing.
I copied them to root of my Zenfone, unpacked tars and converted them into ZIPs. I also unpacked .img files to root of phone (I mean its folder which is visible if I connect it thorught USB, I know it is not "/" root of file system of Andoird, but anyway it is visible even inside CWM... sorry, was visible)...
So, I made some mistakes. I downloaded the kernel, tried to flash it using commands like :
fastboot flash boot boot_fhd_2.19_kvm_bridge_20150710.img
fastboot flash boot boot_fhd_2.19_kvm_bridge_20150714.img
fastboot flash boot boot_fhd_2.19_kvm_bridge_20150717.img
fastboot flash boot boot_fhd_2.20_kvm_bridge_20150820.img
fastboot flash boot boot_2.19_kvm_bridge.img
fastboot flash boot boot_fhd_2.20_kvm_bridge_20150820.img
but non of them produced bootable Zenfone. So I had to revert to previous bootloader using the CWM tool.
In fact I liked this CWM most. I found this thread - https://forum.xda-developers.com/t/...root-ze500-ze550-ze551-temporary-cwm.3114063/
or similar here on forum, and it worked amazingly. I attached Zen-phone to USB, turned it off, then on while pressing, keeping pressed volume-up key, and after Asus logo appeared and some "zzz" vibration, again it blinked and I saw bootloader with Android robot, and possibility to scroll through menu using volume up-down, to choose normal boot, or reboot/power off, or to run restore etc.
For some reason, Restore there not worked. So anyway, I understood that I can use tool like ADB (Android debug bridge) and fastboot to copy new firmwares/kernels/bootloaders etc to it, so I guessed I can do it myself, and was ready for risks... And this what bad can happen - it happened.
So, I runned in CWM - file cai_dat_CWM.bat - which asked to type ACCEPT and then T4, and phone started to go into amazing mode, some "clouds" started appearing on phone, and it loaded into special secret menu, from which I could select what to do next. To me it looked like default boot manager which I wanted to see like in Dos/Windows machines - so I can choose to run into safe mode windows, or set some settings before booting, or even use "reanimator dvd" etc to load Windows and other tools to do partitioning, passwrods recovery etc. So it looked like on desktops, and very nice. I went inside the menu, and found good option to make backup. I did it all. Then in same CWM tool (I think it is called SuperSU for Android), I finally choose to restore bootloader/kernel/boot (custom recovery), and this saved my from bricking the first time after I followed the manual from Ycavan. Well, I know I can read a lot more threads how to do this and that, but there is always risk that something wrong can happen. So I tried to read as much as I could, and follow manuals as precisely as I could understand. But my phone is kind of "bricked".
Now it shows some scfreen like TV which can't catch any tv program. So it is some random colors - see attached picture. It is good that it shows at least this. But in worse situation - it doesn't show anything. So let me tell how I achieved this, and if you can tell me how to avoid this mistake and to recover it. I hope to get help from anyone here who installed KVM kernel(s) and acheieved running Windows on their zenfone 2 (or maybe anyone who has XPerience with other x86 phones may help, or if it is general issue how to unbrick - then also non x86 users please help).
So, CWM made backup, I became more non-scared to make more experiments with firmware. But main problem is that I don't know which firmware to use. I ideally suggested that when I change kernel to KVM-supported from Ycavan - that it will work with my Andorid 5.0 (it was installed when I bought it). So, but unfortunately, after installing any of KVM kernels of Ycavan - I was unable to understand which OS to install, which version. So even I tried to try to flash whole 1GB+ image (I have downloaded UL-Z00A-WW-2.20.40.59-user.zip from official asus.com - https://www.asus.com/ua-ua/supportonly/asus zenfone 2 (ze551ml)/helpdesk_bios/ - but. I was unable to upload it to zenfone (flash it), as it said it is older than installed version.
Anyway, now it doesn't matter as I cannot run into ANdroid at all. Worse - I cannot even get Bootloader working in Android, as I see after turning phone on - only "white screen" with non-working TV-like image (see attached picture of my Zenfone 2).
So, to make this happen, I did this: I found some information about TWRP. I tried to install as recovery tool. Even though it was flashed into mobile, and I installed it from apk from Google-Play, still, I was unable to run it... So then I found even cooler tool - which was too risky to install. I was good, but Andorid stopped running at all.
This tool is called - preroot601. I runned in it preroot.bat, and then it did something similar to CWM, but several times it restartd the phone _ i have added screenshots of how it looked like on PC / Windows. So after several restarts, it did a lot of changes - Android didn't start after it. Phone always was able to start into recovery mode - into TWRP (I downloaded its .img and flased it as recovery for phone). But in TWRP I think I did something wrong. I made backup of all files (syste,, bootloader, everything). I saw it is cool - to see there terminal, ability so set attributes for files, mount partitions ... even USB -hey, can I run from flash-disk? or from external DVD/Bluray which I have in this mode? I have USB-hub, and can connect to it keyboard, mouse, flash-usb, ssd/hdd - all through Microusb-usb adapter and to usb-hub. So what I wanted to do is to try to see flash-disk, mount it on my android zenfone. And then after restart - I had black screen or this 'non-working analog-TV screen when no program/channel/wave is caught for signal"...
So, I don't even understand what I did, and why this all happened, and why I have to do to restore bootloader at least.
My aim is to have KVM enabled in the kernel. I don't mind if it is old Windows like XP working on this Zenfone, but I like windows to be my main OS on every phone which I may use in future (and hope they all be x86-64 and not ARM). So as I don't have Steamdect now (it has also AMD x86 CPU, like Zenfone), I want to do this, achieve it - having Windows on mobile - Zenfone.
I can carry it in pocket everywhere, so why not people like having desktop Windows x86-64 in each and every mobile? Even Lenovo are collaborating with IBM - then why not make also IBM-Mobile / IBM-smartphone, which will also be as good as PC - to unassemble it, change any part like on desktop, why not do it? I think everyone will enjoy it, and it will boost everything to better hights, levels.
So, please. If anyone here has similar experience of going to same screen like I have (see screenshot), or like that - black screen - indeed my device also may not even show any thing - even no ASUS logo, no bootloader (even if I press Volume-UP after powering and after flash it usually showed bootloader with robot - no... not now)...
So I don't see anything on screen of Android Zenfone now. no text, no bootloader, no recovery even - no TWRP menu. I think I am ready to format whole zenfone, and install there maybe some partition manager (like you know there is Partition magic on PCs, when I can split HDD/SSD nto two parts, one for Windows, and say other for Unix - Ubuntu or Android x 86 - all on same physical drive)... So I want some re-partitioning for intern SD memory, and be able to install there some ISOs, say with DOS, Win3.11, win 95, 98, 2000, xp, 7, 8,1 and maybe even 10. But guess last will be slow. I think Windows XP would be ideal OS for my Zenfone, if it can run fast. Win 7/8 maybe will be slow. But for some sceintific aims - like I just write some algorythm in Visual studio, and can do it even in WinXP, so why don't do it on my Zenfone? I don't like many Andorids, as they are not for work much - they are used by many people to play games, watch videos on phones, surf social networks, but not for real work. Real work is usually on WIndows, and no laptop can replace "Windows x86 in pocket" (on mobile). And I wonder why Microsoft develops "Windows for ARM" instead of investing millions into efforts like which Ycavan did - to make Windows run in KVM mode fast on x86 smartphones.
Ok, So, any ideas? What should I do now? I need some special tool to fix my phone first. Fix its loader. I think I need to bypass fastboot.exe restriction, which shows "waiting for device". Command in cmd like this: ADB.exe devices -L --- shows device from time to time - it shows:
c:\adb>adb devices -l
List of devices attached
0123456789ABCDEF device
c:\adb>fastboot flash boot boot_2.19_kvm_bridge.img
< waiting for device >
So, I cannot even flash some recovery device in this way. In devices manager I see "ADB interface" in "USB devices" category in devices treeview. And sometimes Moorefield appears, but with exclaimation mark - I have no idea how to make it disappear. I found here some info that I can install tool - xFSTK_Downloader_v1.7.0.zip - I downloaded it, installe,d but it doesn't run (I have win10 x64bit). hm... And driver required - iSOC_USB_Driver_Setup_v1.2.0.zip - I installed - but nothing.
So, what to do? How to make bootloader appear again? And how to write there prob=per bootloader with KVM kernel, and which firmware to flash so I can use KVM fast there with fast Windows...? Is it possible at all to make it run WIndows natively on Zenfone? or it will always be only in virtual machine inside some ArchLinux or in Limbo x86 on Android?
I read that Ycavan used this ArchLinux, but I don't understand why. Is he installing it over Android? Then also which version he uses? I need to know each and every version whcih he uses to make everything works. I 'ld require all the firmwares which he uses to make it work also - to make some Windows iso run on my Zenfone 2.
Did anyone achieved this successfully, except for Ycavan - to run Windows on Zenfone? Or except for him noone was able to install KVM kernel, and it was similar to mine situation? And maybe this is the reason why manufacturers of phons don't like x86 phones? I don't know. Any ideas?
See screenshots. What to do in this state?
IF anyone can please upload to somewhere whole pack of files ("WIndows on Zenfone starter kit") to make anyone able to just follow instaructions which will work in all cases to install WIndows there like Ycavan has - it would be great. There is lack of more detailed information - which .img files, .zips, firmwares etc, which OSes are supported by Ycavan's KVM kernels?
I have no idea. if anyone passed this path, and achieved Windows on Zenfone, please share your experiences, Ireally need it. Here in Ukraine when electricity disappears almost daily, we need devices like x86 phones almost for everyone. And mo matter if Windows is a bit old. KVM mode I guess must be much faster, almost native speed, so (like on tablet PCs), so please help...
Thank you all in advance, whoever will answer me.
indubhushan said:
c:\adb>adb devices -l
List of devices attached
0123456789ABCDEF device
c:\adb>fastboot flash boot boot_2.19_kvm_bridge.img
< waiting for device >
Click to expand...
Click to collapse
wrong mode. adb is only working in
- normal/boot mode
- recovery mode
fastboot is only working in
- bootloader mode
- fastboot mode
You can see 0123456789ABCDEF device in adb devices, therefore you are either in TWRP or in Android (Win?)
type adb shell and check the prompt is either $ (shell) or # (root shell)
in root shell you can flash partitions from cmd line. you can also reboot into bootloader/fastboot mode from cmd line.
Code:
adb reboot bootloader
I had success in restoring my bootloader (logo with android robot) - I intalled xFSTK, so somehow I had success to make it run, and I added threee files (1, 2, and 4th) and tried to flash it. Phone was visible as Moorefield. Then I tried to use Asus flash tool to flash big RAW image, but for some reason I don't know why - I had even whole day left it to flash, it didn't do the task - Android stopped booting - no logo showing at all - have to use xFSTK to recover. Maybe I use wrong RAW image (from official site it is .zip, so have no idea where to get those raw files).
When try to flash using flashboot - I get error: - flash cmd error.
As for devices list. My device rarely appear there. It may appear for some seconds, and then xfstk can have success to flash it, and maybe even make it runnable into Android robot scren (bootloader).
I am thinking that I need to install maybe ArchLinux, which Ycavan is using, but have no idea where to get RAW file for it, and how to flash it. Maybe some problem with my USB port on old laptop, or maybe even with USB cable (though have few good almost new cables, even new 4Amperes one). So maybe even problem in port of Zenfone itself (to change it). No idea. Because even when I tried to flash it (that huge 1GB file), phone disconnected, or showed "ready for commands", instead of showing process of ownloading RAW image/Android into phone's memory.
Flashboot/adb almost unusable. Well, I'll try, maybe it'll work.
My hope is try to go into CWM, run from it into "secret menu" on phone, and from it - to access internal memory of phone, and restore phone from backup. But when I tried to load into it once - it hanged on "clouds". I don't know...
And I don't think I'm ready now to format internal memory of phone or to repartition. At least I don't have backup on some external card (sd-card) etc.
as for adb. maybe it can't see my device, even if it is "recovery mode" (when see in devices manager in Windows - Moorefield). Now I'm stuck on xFSTK and can't go anywhere further like adding TWRP into phone, or foing into backup/restore menu on phone, and of course there is no Android. Even when I see Android robot (boot menu) - I feel happy, that at least phone shows anything, so at least bootloader workds. Maybe difference is in drivers - when I have Moorefield driver, then maybe it contradicts with Zenfone driver, and I have to reinstall them? Or use other OS? I have dual-boot (two Windowses on my laptop), so maybe I need to use one Windows - to work with Moorefield (xfstk) - when phone is in "worst" situation when no logo shows / no bootloader. And the other Windows I have to run on laptop - with Zenfone driver installed (I think it shows something like Asus device in device manager). But they seem to use contradicting drivers, I am not sure. And maybe it's some problem with my usb ports, but hope no. They seem to be ok... Maybe I'll have to go some day to give phone for diagnostics to repairing center again ;-(