Hello everyone, I write through the translator, maybe someone will not understand, but I'll try to explain! I would like to know how to change the identifier to MX4 since changed it to MX4 PRO, MX5, PRO 5, to install the international firmware, thanks in advance! Acquired Chinese model M461.
Hello! Tormented with this mx4 constant Russification, considered mmcblk0boot0 in hex and noticed a curious code, and it is in the same shift in the European and Chinese vehicles and coincides with their sw_version (46151004 and 46111004) are themselves divided mmcblk0boot0 are almost identical, except for the last blocks. It crept into the idea of ??the possibility of change id. Id are placed in reverse order (as I understand machine code) version A 04 10 11 46 version of G 04 10 15 46. Checked on multiple devices with 3 different id. Offset 0000db5a. This is a sporting interest, ask for help.
google translation, sorry!
Related
Hi guys,
I'm trying to figure out how to unlock the bootloader of the ZE500KL, I have a full dump and I think that we can unlock it by modifying the aboot.bin file.
Tryied to decompile it, but not understand the output code at all because it is with addresses. Can someone help me?
Here the zip with decompiled files.
c file contains functions, svg are graphs of the functions that can be opened and viewed with google chrome, and dsm file is low level code I think, there are some interesting strings in it.
96DANGER96 said:
Hi guys,
I'm trying to figure out how to unlock the bootloader of the ZE500KL, I have a full dump and I think that we can unlock it by modifying the aboot.bin file.
Tryied to decompile it, but not understand the output code at all because it is with addresses. Can someone help me?
Here the zip with decompiled files.
c file contains functions, svg are graphs of the functions that can be opened and viewed with google chrome, and dsm file is low level code I think, there are some interesting strings in it.
Click to expand...
Click to collapse
Have you tried what the zenfone 2 does? seeing as they are fairly similar phones http://forum.xda-developers.com/zenfone2/general/congrats-to-bootlocker-unlocked-t3138547
also here is a way to root it if you have not done that already http://forum.xda-developers.com/showpost.php?p=63444749&postcount=108
deadman96385 said:
Have you tried what the zenfone 2 does? seeing as they are fairly similar phones http://forum.xda-developers.com/zenfone2/general/congrats-to-bootlocker-unlocked-t3138547
also here is a way to root it if you have not done that already http://forum.xda-developers.com/showpost.php?p=63444749&postcount=108
Click to expand...
Click to collapse
Yeah, but I don't think it's the same
Rooted and flashed twrp, thank you.
deadman96385 said:
Have you tried what the zenfone 2 does? seeing as they are fairly similar phones http://forum.xda-developers.com/zenfone2/general/congrats-to-bootlocker-unlocked-t3138547
also here is a way to root it if you have not done that already http://forum.xda-developers.com/showpost.php?p=63444749&postcount=108
Click to expand...
Click to collapse
UPDATE:
Tried shakalaka method and doesn't work, copied the key in asuskey file in /factory but at reboot in bootloader nothing happens!
These phones share naming, but under the hood they are completely different. The ZF2 is using an Intel processor and the Laser is using a SnapDragon 615 ARM processor. It would be better to look at common unlocking methods for similarly spec'd devices. Asus tends to not alter to much from standard design specs released by the SoC manufacturer. This phone is also just now getting released in the U.S so support may take a while to get development picked up. Keep an eye on 23 pin's blog because he does a lot of work with varying models of Asus devices.
earlier in my Oneplus one,....it used to be in /sys/devices/fb0000.wcnss,wlan/....mac_addr some file ending with mac_address
and edit in any text file editor and done... but in my oneplus two... no such directory is there....
can somevody help...
from my point of view..
android version is irrespective of this thing...but 32,64 bit architecture matters... in many 32 bit architeture phones like oneplus one and same problem in 64bit architecure based phone like redmi note 3 pro,lg g4,etc
can somebody please help???
I've been lurking around this forum section for a while but couldn't find a clear answer to my question :
what are the hardware differences between A2017 model ( chinese ) and A2017G model ( european )?
is it doable to get a full software replica (including OTAs ) of the european model by flashing a chinese bought model?
the only difference i could detect so far is the zte logo on the chinese version
Software, I assume, it is not a problem. The main differences are in radio modules. Each model supports different LTE Bands., e.g. A2017G supports LTE B28 but model U and Chinese doesn't.
I'm planning to buy this device as well, but I don't really like the capacitive buttons of the EU version.
I'm reading throught various thread but I cannot find an answer for the following question : if I buy the chinese A2017 model with on screen navbar (softkeys) will I be able to install LineageOS ? For example the Unjustified Dev's builds ?
As much as I've understood CM13 works ok, but Lineage 14.1 does not because of older bootloader
Alastor89 said:
I'm planning to buy this device as well, but I don't really like the capacitive buttons of the EU version.
I'm reading throught various thread but I cannot find an answer for the following question : if I buy the chinese A2017 model with on screen navbar (softkeys) will I be able to install LineageOS ? For example the Unjustified Dev's builds ?
As much as I've understood CM13 works ok, but Lineage 14.1 does not because of older bootloader
Click to expand...
Click to collapse
I think Lineage has an option to enable soft keys built into the settings
calddon said:
I think Lineage has an option to enable soft keys built into the settings
Click to expand...
Click to collapse
That was a 10 month bump. I'm pretty sure he already figured out by himself...
Choose an username... said:
That was a 10 month bump. I'm pretty sure he already figured out by himself...
Click to expand...
Click to collapse
ok, am new here. sorry about that.
Looks like we're finaly getting Nougat.
As you may all know, Nougat doesn''t support Xposed yet. So we cant use any of the amazing plugins/modules.
Would you rather have Nougat now or wait till Xposed is fully compatible?
My answer: At this point, the features and benefits of having Xposed outweigh the incremental features offered by Nougat. So, if Xiaomi continues supporting the Marshmallow build until we have xposed for Nougat, I'll stay with Android 6.0.
In most cases, they may upgrade the base to Nougat when they release stable Nougat. In this case, I'll stay on the last known stable MM ROM until we have Xposed on Nougat.
http://www.gsmarena.com/nougatpowered_xiaomi_mi_mix_spotted_on_geekbench-news-23291.php
this phone, to me is unusable to me without xposed with MIUI. there is very little nougat offers to even think about upgrading.
I choose nougat. As long as there is root I can mod the look and feel without exposed.
xposed is a must.
The article had screenshotted this https://browser.primatelabs.com/v4/cpu/1801163 result, but I found this newer entry
https://browser.primatelabs.com/v4/cpu/1816850
Pay attention to the difference in writing the device name: Mix vs. MIX. Our device's official name when apps read it out through the API is MIX and not Mix. The Android variant is also different: 7.0 is unlikely to be used as a base by MIUI, I guess they will use 7.1.1 as a base. So where do these strange 7.0 Mix entries come from?
underlines said:
The article had screenshotted this https://browser.primatelabs.com/v4/cpu/1801163 result, but I found this newer entry
https://browser.primatelabs.com/v4/cpu/1816850
Pay attention to the difference in writing the device name: Mix vs. MIX. Our device's official name when apps read it out through the API is MIX and not Mix. The Android variant is also different: 7.0 is unlikely to be used as a base by MIUI, I guess they will use 7.1.1 as a base. So where do these strange 7.0 Mix entries come from?
Click to expand...
Click to collapse
Maybe the the device reports to Benchmark apps as "Mix" on the nougat build instead of "MIX". They may have updated/modified the build.prop on the test ROM.
What I'm actually curious about is the "3GB" memory reported on the newer post. Does this mean they may release a "lite" variant with slightly lower specs?
satishp said:
Maybe the the device reports to Benchmark apps as "Mix" on the nougat build instead of "MIX". They may have updated/modified the build.prop on the test ROM.
What I'm actually curious about is the "3GB" memory reported on the newer post. Does this mean they may release a "lite" variant with slightly lower specs?
Click to expand...
Click to collapse
tl:dr
For me both screenies are fake :-/
Detailed conclusion:
This one - https://browser.primatelabs.com/v4/cpu/1801163
- has wrong board ID (should be "msm8996")
- wrong phone name (an mentioned earlier)
This one - https://browser.primatelabs.com/v4/cpu/1816850
- has wrong number of CPU cores (should be 4 core "ARM implementer 81 architecture 8 variant 2 part 517 revision 1")
- has wrong board ID (its from the Huawei manufactured Nexus 6P - codename "Angler" - should be "msm8996")
- wrong memory size
If exposed is not ready for nougat then I'm stuck on marshmallow till then.
raupe said:
tl:dr
For me both screenies are fake :-/
Detailed conclusion:
This one - https://browser.primatelabs.com/v4/cpu/1801163
- has wrong board ID (should be "msm8996")
- wrong phone name (an mentioned earlier)
This one - https://browser.primatelabs.com/v4/cpu/1816850
- has wrong number of CPU cores (should be 4 core "ARM implementer 81 architecture 8 variant 2 part 517 revision 1")
- has wrong board ID (its from the Huawei manufactured Nexus 6P - codename "Angler" - should be "msm8996")
- wrong memory size
Click to expand...
Click to collapse
Well done!
raupe said:
tl:dr
For me both screenies are fake :-/
Detailed conclusion:
This one - https://browser.primatelabs.com/v4/cpu/1801163
- has wrong board ID (should be "msm8996")
- wrong phone name (an mentioned earlier)
This one - https://browser.primatelabs.com/v4/cpu/1816850
- has wrong number of CPU cores (should be 4 core "ARM implementer 81 architecture 8 variant 2 part 517 revision 1")
- has wrong board ID (its from the Huawei manufactured Nexus 6P - codename "Angler" - should be "msm8996")
- wrong memory size
Click to expand...
Click to collapse
I've noticed that after posting my doubts, but didn't update my post. Thanks for pointing out in detail.
Hi everybody,
I just received my Zuk Edge and want to dual boot Zui 3.0 beside Mokee installed on it, to have access to U-health and stuff.
So, does anybody here know whether the DualBootPatcher works for Zuk Edge or not? It is not listed among the supported devices on this list, but somebody described in this post on Chinese Lenovo Club forum (had to Google Translate it, so I may have misunderstood some bits) how to make it work. Seems that all you have to do is edit build.prop and change product name and device to "benefit3" (ro.product.name = benefit3 ro.product.device = benefit3).
Any experience here with dual booting?