Hi all,
This is the consolidated thread for all Marshmallow ROMs for the Mediapad M2 8.0 8" devices, as downloads available from the Huawei hicloud.com servers (see below for whois info on this domain, to verify that the domain owner is Huawei). If anyone is running a ROM more recent than those mentioned here, please reply in this thread. Also, if you can mention the source from where you downloaded it, please also add that source in your reply, and I will update this post accordingly and give you credit for finding it
This post will be updated as and when new info becomes available. In this post you will find:
ROM downloads for the Mediapad M2 8.0 Marshmallow ROMs.
Installation instructions for the ROMs
Rooting/Unrooting instructions
DPI/LCD Density change instructions
How to perform Local Updates on Marshmallow ROMs
Issues/Problems Noticed
Instructions to recover from a bad ROM install/softbrick/bootloop
Obligatory Disclaimer: I have not tested any of the ROMs mentioned below (apart from B203 and B207 on the M2-802L) because I do not have the proper device models. Also note that even though they are available for download from the Huawei hicloud site, these ROMs have not (as far as I know) been actually formally released by Huawei.
M2-801L
Note: user @omaga reports that B202 seems to contain a newer kernel and security patch than B205.
B205: http://update.hicloud.com:8180/TDS/data/files/p4/s10/G506/g0/v57899/f2/full/M2-801LC100B205.zip
Thanks to user [MENTION]Caelestiel[/MENTION] for mentioning that B205 existed for M2-801L so that I could search for it - a valid download link for it was not present in my previous search.
B205 Text Link:
Code:
http://update.hicloud.com:8180/TDS/data/files/p4/s10/G506/g0/v57899/f2/full/M2-801LC100B205.zip
B202: http://update.hicloud.com:8180/TDS/data/files/p4/s10/G506/g0/v70346/f1/full/update.zip
B202 Text link:
Code:
http://update.hicloud.com:8180/TDS/data/files/p4/s10/G506/g0/v70346/f1/full/update.zip
@omaga has found B206 for the 801L (thanks, omaga!); however the ROM download is NOT from an official Huawei server.
user @pajosekX has found B206 for the 801L on an official Huawei server! Thanks, pajosekX! User @allrightlite has verified upgrading from B008 to this B206 ROM. Thanks, allrightlite!
B206: http://update.hicloud.com:8180/TDS/data/files/p4/s10/G506/g0/v74068/f1/full/M2-801LC100B206.zip
B206 Text link:
Code:
http://update.hicloud.com:8180/TDS/data/files/p4/s10/G506/g0/v74068/f1/full/M2-801LC100B206.zip[CODE]
[SIZE="4"][B]M2-801W[/B][/SIZE]
[B]Note: user [user=691574]@elendiir[/user] reported that[COLOR="Red"] you should skip the installation step where you unzip the downloaded ROM[/COLOR]. See [URL="https://forum.xda-developers.com/showpost.php?p=70623587&postcount=63"]post #63 [/URL]in this thread. Thanks, Elendiir! [/B]
[B]B202 European cust channel M2-801WC232B202[/B] found by XDA user [user=427926]@lonwas[/user] (see [URL="https://forum.xda-developers.com/showpost.php?p=70691260&postcount=77"]post #77[/URL] in this thread):
[url]http://update.hicloud.com:8180/TDS/data/files/p4/s10/G506/g0/v74308/f1/full/update.zip[/url]
Text link: [CODE]http://update.hicloud.com:8180/TDS/data/files/p4/s10/G506/g0/v74308/f1/full/update.zip
B213: XDA user @ruggles says in a thread replythat the B213 zip posted here worked for him. But please note that this B213 download is NOT from an official Huawei server.
M2-802L
Note: My M2-802L just got an official OTA update from Huawei to B203 (I had restored my old B005 ROM from TWRP). This OTA update does have the Huawei Swype IME keyboard, though (I had lost Swype when I flashed B207 over B005). However, the kernel and security patch version in this B203 OTA update are older than the one on B207. Also, both B203 as well as B207 ( after following the update path B005 -> B203 OTA -> B207) seem to have the "3G/4G icon is always on" problem. See below.
B203: http://update.hicloud.com:8180/TDS/data/files/p4/s10/G506/g0/v65143/f1/full/M2-802LC209B203.zip
B203 Text Link:
Code:
http://update.hicloud.com:8180/TDS/data/files/p4/s10/G506/g0/v65143/f1/full/M2-802LC209B203.zip
B207: http://update.hicloud.com:8180/TDS/data/files/p4/s10/G506/g0/v67917/f1/full/update.zip
B207 Text link:
Code:
http://update.hicloud.com:8180/TDS/data/files/p4/s10/G506/g0/v67917/f1/full/update.zip
3G/4G icon always on: I've confirmed that this is due to B203; the upgrade path B005->B207 does not have this issue. B005->B203, B005->B203->B207 and B005->B207->B203 all have the issue. While it appears to be alarming, no data seems to actually be going through the mobile data if Wifi is on ("Settings"->"About Tablet"->"Status" shows mobile data as disconnected); so it seems to be just be an indicator the current mobile data speeds.
Also note that flashing B207 over B203 will remove the Swype IME.
M2-803L
B215: http://update.hicloud.com:8180/TDS/data/files/p4/s10/G506/g0/v60481/f3/full/update.zip
B215 Text link:
Code:
http://update.hicloud.com:8180/TDS/data/files/p4/s10/G506/g0/v60481/f3/full/update.zip
Sorry, M2 10.0 owners, I do not know what is the proper ROM numbering for the M2 10.0 Android 6.0 Marshmallow ROMs - I have found ROM B030 for the M2-A01L and ROM B020 for the M2-A01W, maybe some M2 10.0 owners can tell me if these are Marshmallow ROMs...? If anyone can confirm that the above-linked B0XX ROMs for the A01L and A01W are Marshmallow, I will update the thread accordingly.
Installation Instructions:
If you are currently rooted and/or have a custom recovery installed, you will need to go back to the Huawei official recovery to install this update. You can do this by following the instructions in my previous post here.
Download the appropriate ROM update zip from one of the above links.
Note: If you are using one of the wifi-only models - specifically the M2-801W, user @elendiir reported that you should skip this step. See post #63 in this thread. Thanks, Elendiir! Extract the contents of the zip file in the link after it has finished downloading. The contents should be something like this:
Code:
[update.zip contains]
├── META-INF
│** ├── blacklist.conf
│** ├── CERT.RSA
│** ├── CERT.SF
│** ├── com
│** │** ├── android
│** │** │** └── otacert
│** │** └── google
│** │** └── android
│** │** ├── update-binary
│** │** └── updater-script
│** └── MANIFEST.MF
└── UPDATE.APP
5 directories, 8 files
Create a folder called dload on your SD Card. You can create it on either the internal or the external SD, it doesn't matter.
Copy the entire contents of the unzipped download package into the dload folder on your SD Card, which you created above. Alternatively, you could just unzip the contents directly into the dload directory on your external/internal SD card.
Go to your phone's "Settings". There, navigate to "Updater"->"Menu"->"Local Update", select the displayed option, and allow it to install. Your phone will boot into the original OEM recovery and install the ROM, after which it should (hopefully) boot into the new ROM.
It should then connect to the Google Play Store and update the Google framework. All your settings, apps etc should still be preserved - mine were.
Local updates on Marshmallow ROMs
In the Huawei Marshmallow (Mm) ROMs, the updater app does not have the "Local Update" option anymore. So how do you do an update from the SD Card (say you want to install a different Mm ROM)?
Here's how to do local updates on Huawei Mm ROMs. I used the dialer method. If you are on one of the Wifi-only models, XDA user @elendiir has this method for performing a Local Update on Marshmallow (where the updater app does not have the "Local Update" option), especially on the Wifi-only models which don't come with a dialler app. Thanks, Elendiir!
elendiir said:
Maybe you should extent the description how to flash roms via the local update in Marshmallow for the Wifi-only models:
Tested on my M2-801-W:
Start the included calculator app
switch to landscape mode in order to enable the more advanced input mode (you will need this in order to enter the "()" as described in the next step)
enter the follwoing string: ()()2846579()() and press the = sign
you should now have entered the project menu
select number 4 for software upgrade and then sdcard upgrade
If you're on a Wifi-only model and the instructions above don't work for you, then you may need to use the HwOUC app method detailed in the link above.
Not sure if this also works on the models with SIM card - but there you can enter mostly the same sting via the dialer app: *#*#2846579#*#* as you have already described.
Cheers
Elendiir
Click to expand...
Click to collapse
Rooting/Unrooting instructions using phhusson's Superuser:
Rooting:
First install TWRP as your recovery. If in doubt, use the excellent Huawei Mediapad M2 rooting guide found on these forums.
Then grab the latest superuser.zip (from phhusson's Superuser project which is an actively-maintained fork of Koush's open-source Superuser project), and install it via the TWRP recovery.
Finally, get the "phh superuser" app from the Google Play store.
At this point, you should be successfully rooted. To check, you can install an app which requests root permissions (maybe a terminal app like Termux, firewall app like AFWall+, or file manager like MiXplorer), run it, and see if the root permission app dialog comes up and if the app successfully gets root after you give it the permission in the dialog.
Unrooting:
For this, you need to fastboot flash the BOOT.img from your ROM. This will involve you extracting the BOOT.img from the UPDATE.app of the ROM you flashed.
Make sure that you have ADB and FASTBOOT installed on your computer. You can use the 15-second ADB installer available here on XDA.
Uninstall the "PHH Superuser" app on your device using the app manager or the Google Play Store.
Unzip the ROM's zip file. If you're on Windows, you can use the excellent 7-zip tool for this. On Linux, you can just use the unzip command. After unzipping, you should have an UPDATE.APP file. This is the full ROM update image which we will use.
Extract BOOT.img from your ROM's UPDATE.APP using the Huawei Update Extractor tool (make sure to use the "Huawei Mediapad M2 (M2-802L)" profile in the Huawei Update Extractor tool) and save it somewhere on your computer's hard disk.
Boot your phone into the bootloader - this is called "fastboot mode".
If you have ADB enabled, you can use the following command
Code:
adb reboot bootloader
If you don't have ADB set up, you can use the hardware keys method to enter the bootloader - first shut down the phone, and then press POWER+VOLDN simultaneously.
Of the two methods, I'd recommend the ADB method because it works every time (using the hardware keys method I had mixed success; sometimes it would boot into the bootloader and sometimes it would boot into the normal ROM.
With the USB cable connected to your phone, open up a command prompt in the directory where you extracted BOOT.img, and run the following fastboot command:
Code:
fastboot flash boot BOOT.img
Reboot your computer:
Code:
fastboot reboot
And that's it, you should now be unrooted.
DPI/LCD Density Change:
If you're rooted, you can change the DPI/LCD density. If you're going to attempt this, I'd suggest making a TWRP backup first just in case your phone does not boot after changing the DPI/LCD density.
A big Thanks to [MENTION]Eagle-no1[/MENTION] for testing that a DPI/LCD Density Change to 380 and also 360 works without issues for him. The full thread is here.
To do this manually, you will find the DPI settings in /system/build.prop with these original values:
Code:
ro.sf.lcd_density=480
hw.lcd_density=480
Simply change the above so that it looks like this:
Code:
ro.sf.lcd_density=360
hw.lcd_density=360
and then reboot your device, and you should be good to go.
Have fun!
Issues/Problems Noticed
XDA user @guille3073 has noticed a problem with the M2-802L and 5GHz WiFi Networks set to "AC-Only" mode, and I have verified the issue. Please see this post and the one before it. The solution is to change your 5GHz WiFi band to be in "Mixed" mode or "N-Only" mode. Thanks, guille3073! If anyone else notices this issue on a different device model than the 802L, please mention it in the comments to it can be added here. Update: User @lepidas reports the same issue on the 801L as well.
Instructions to recover from a bad ROM install/softbrick/bootloop:
First, make sure that you have known good official Huawei ROM for your particular device model. Then, follow the instructions (replace all references to the ROM version with the correct ROM for your device) in this post. Note: The detailed guide for extracting and flashing specific partitions from Huawei ROMs is here. Wish you good luck in your unbricking efforts.
WHOIS INFO:
Code:
Queried whois.markmonitor.com with "hicloud.com"...
Domain Name: hicloud.com
Registry Domain ID: 1429950708_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.markmonitor.com
Registrar URL: http://www.markmonitor.com
Updated Date: 2016-05-03T10:37:45-0700
Creation Date: 2008-03-22T06:56:43-0700
Registrar Registration Expiration Date: 2023-03-22T06:56:43-0700
Registrar: MarkMonitor, Inc.
Registrar IANA ID: 292
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: +1.2083895740
Domain Status: clientUpdateProhibited (https://www.icann.org/epp#clientUpdateProhibited)
Domain Status: clientTransferProhibited (https://www.icann.org/epp#clientTransferProhibited)
Domain Status: clientDeleteProhibited (https://www.icann.org/epp#clientDeleteProhibited)
Domain Status: serverUpdateProhibited (https://www.icann.org/epp#serverUpdateProhibited)
Domain Status: serverTransferProhibited (https://www.icann.org/epp#serverTransferProhibited)
Domain Status: serverDeleteProhibited (https://www.icann.org/epp#serverDeleteProhibited)
Registry Registrant ID:
Registrant Name: Domain Administrator
Registrant Organization: Huawei Technologies Co., Ltd.
Registrant Street: Huawei Base, Bantian, Longgang District
Registrant City: Shenzhen
Registrant State/Province: Guangdong
Registrant Postal Code: 518129
Registrant Country: CN
Registrant Phone: +86.75528560097
Registrant Phone Ext:
Registrant Fax: +86.75528560390
Registrant Fax Ext:
Registrant Email: [email protected]
Registry Admin ID:
Admin Name: Domain Administrator
Admin Organization: Huawei Technologies Co., Ltd.
Admin Street: Huawei Base, Bantian, Longgang District
Admin City: Shenzhen
Admin State/Province: Guangdong
Admin Postal Code: 518129
Admin Country: CN
Admin Phone: +86.75528560097
Admin Phone Ext:
Admin Fax: +86.75528560390
Admin Fax Ext:
Admin Email: [email protected]
Registry Tech ID:
Tech Name: Domain Administrator
Tech Organization: Huawei Technologies Co., Ltd.
Tech Street: Huawei Base, Bantian, Longgang District
Tech City: Shenzhen
Tech State/Province: Guangdong
Tech Postal Code: 518129
Tech Country: CN
Tech Phone: +86.75528560097
Tech Phone Ext:
Tech Fax: +86.75528560390
Tech Fax Ext:
Tech Email: [email protected]
Name Server: ns4.dnsv5.com
Name Server: ns3.dnsv5.com
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2017-01-10T01:10:48-0800 <<<
A big big shoutout to Team MT and XDA user [MENTION]gmanrainy[/MENTION] for the Huawei Firmware Finder tool available here on XDA - I wish I had known about this earlier when I was manually searching the Huawei servers for ROMs :silly:
Excellent thread, great work beast.in.black! that firmware tool is a great find
In my 10" current (latest) version is M2-A01WV100R001C100B007 Android 5.1.1, but update zip seems to be only 56Mb?
mele80 said:
In my 10" current (latest) version is M2-A01WV100R001C100B007 Android 5.1.1, but update zip seems to be only 56Mb?
Click to expand...
Click to collapse
It might not be a full update - for example, on my 802L, B003 was a full update, but B005 was an OTA partial update and not a full system image update.
omaga said:
Excellent thread, great work beast.in.black! that firmware tool is a great find
Click to expand...
Click to collapse
Isn't it just! I found it by accident on Google when I was trying to search for Marshmallow ROMs for our devices. I was like"Oh yeah, these guys are awesome!"
Big thumbs :good: up to Team MT for the work on the Firmware Finder tool!
How i root my M2-801L there no OEM lock open possibility of the developer's settings.
Eagle-no1 said:
How i root my M2-801L there no OEM lock open possibility of the developer's settings.
Click to expand...
Click to collapse
Did you try pressing the build number about 8 times in quick succession? Which ROM version are you using?
You will find the build number in "settings" -> "About tablet". Just press on the actual build number (the stuff that says "M2-801Lblabla") about 7 or 8 times quickly, and it should show a message saying that you are a developer.
I had the B205 firmware in my M2-801L, now i downloaded/and installed the B202 version and its seems to be a newer firmware version. B205 kernel is dated Jul 28 2016 and the android security patch is dated 1 july 2016, baseband is 21.600.23.00.010.
Now with the B202 firmware the kernel is dated Mon 7 Nov 2016 and the android security patch is dated 1 oct 2016, baseband 21.600.27.00.010
beast.in.black said:
Did you try pressing the build number about 8 times in quick succession? Which ROM version are you using?
You will find the build number in "settings" -> "About tablet". Just press on the actual build number (the stuff that says "M2-801Lblabla") about 7 or 8 times quickly, and it should show a message saying that you are a developer.
Click to expand...
Click to collapse
Build number M2-801LC100B205 and tapped eight times.
No OEM Unlock selection choice developer options.
omaga said:
I had the B205 firmware in my M2-801L, now i downloaded/and installed the B202 version and its seems to be a newer firmware version. B205 kernel is dated Jul 28 2016 and the android security patch is dated 1 july 2016, baseband is 21.600.23.00.010.
Now with the B202 firmware the kernel is dated Mon 7 Nov 2016 and the android security patch is dated 1 oct 2016, baseband 21.600.27.00.010
Click to expand...
Click to collapse
Good to know, thank you! I will update the original post accordingly.
Eagle-no1 said:
Build number M2-801LC100B205 and tapped eight times.
No OEM Unlock selection choice developer options.
Click to expand...
Click to collapse
omaga reports that B202 seems to have newer content than B205. Can you try B202 and see?
beast.in.black said:
omaga reports that B202 seems to have newer content than B205. Can you try B202 and see?
Click to expand...
Click to collapse
I have this Huawei_MediaPad M2 8.0_Firmware_M2-801L_Android 5.1.1_EMUI 3.1_V100R001C209B008CUSTC209D001 earlier.
I have just got Huawei unlock password.
Edit:
I download B202 and test and report soon.
Eagle-no1 said:
I have this Huawei_MediaPad M2 8.0_Firmware_M2-801L_Android 5.1.1_EMUI 3.1_V100R001C209B008CUSTC209D001 earlier.
I have just got Huawei unlock password.
Edit:
I download B202 and test and report soon.
Click to expand...
Click to collapse
Oh I see! OK. It's very peculiar that you haven't got the developer access on the stock B008 ROM. Could you please post a pic of your phone's "Settings" main menu screen, the bottom section whereyou see the "About Tablet" and "Updater" settings menu items?
No OEM locking choice in B202 version, now i downgrade back B008 version and look there.
-------------------------
Edit:
B008 version included OEM lock open option. Android is 5.1.1
Eagle-no1 said:
B008 version included OEM lock open option. Android is 5.1.1
Click to expand...
Click to collapse
Awesome! Now you can unlock the bootloader and phone! Good luck in your rooting efforts
beast.in.black said:
Awesome! Now you can unlock the bootloader and phone! Good luck in your rooting efforts
Click to expand...
Click to collapse
Yes but how do I install android 6.0
Eagle-no1 said:
Yes but how do I install android 6.0
Click to expand...
Click to collapse
The ROMs in my original post are Android 6.0, and the installation instructions should be common across phones.
Also, if you successfully installed B202, you already had Android 6.0 on your phone
You need the developer options so that you can unlock your bootloader and phone so that you can root the phone. Rooting the phone is separate from installing Android 6.0 on it - they are two separate things :cyclops:
EDIT: BTW, I apologize if the above sounds patronizing - it wasn't meant to be. I see that you have 400+ posts so you are experienced here. Maybe I didn't understand your question...?
beast.in.black said:
The ROMs in my original post are Android 6.0, and the installation instructions should be common across phones.
Also, if you successfully installed B202, you already had Android 6.0 on your phone
You need the developer options so that you can unlock your bootloader and phone so that you can root the phone. Rooting the phone is separate from installing Android 6.0 on it - they are two separate things :cyclops:
EDIT: BTW, I apologize if the above sounds patronizing - it wasn't meant to be. I see that you have 400+ posts so you are experienced here. Maybe I didn't understand your question...?
Click to expand...
Click to collapse
I can install android 6, version B202 or B205, but there are no OEM Unclock options and I do not get done as rooting.
Only B008 is OEM Unlock choice.
Yes I am already a very old man (64Years) and I do not understand everything because I am Finnish and I use the Google translator.
---------- Post added at 16:37 ---------- Previous post was at 16:19 ----------
Now is rooted version b008 Thank you your help.
Eagle-no1 said:
I can install android 6, version B202 or B205, but there are no OEM Unclock options and I do not get done as rooting.
Only B008 is OEM Unlock choice.
Yes I am already a very old man (64Years) and I do not understand everything because I am Finnish and I use the Google translator..
Click to expand...
Click to collapse
No problem, thank you so much for your patience, I really appreciate it.
Eagle-no1 said:
---------- Post added at 16:37 ---------- Previous post was at 16:19 ----------
Now is rooted version b008 Thank you your help.
Click to expand...
Click to collapse
Awesome! Now your bootloader and phone must be unlocked. This is good, because now we can root your Android 6.0 ROM too
So next steps for you:
Now you have to replace TWRP with stock recovery (need to put back the stock recovery otherwise you cannot install the Android 6 update). For this, you can flash the original RECOVERY.img from your B008 ROM. The recovery.img needs to be flashed using fastboot mode. You can extract the RECOVERY.img from B008 using the Huawei update extractor (use the "Huawei Mediapad M2 (M2-802L)" profile in the Update Extractor tool). If you have problems, let me know and I can help you with this.
Then install the Android 6 ROM
Then reinstall TWRP, and re-root the Android 6 ROM
Unfortunately all the above steps are necessary because once you flash the new Android 6 ROM, you lose root (you need to unroot the previous ROM, and also restore recovery back to original Huawei recovery).
beast.in.black said:
No problem, thank you so much for your patience, I really appreciate it.
Awesome! Now your bootloader and phone must be unlocked. This is good, because now we can root your Android 6.0 ROM too
So next steps for you:
Now you have to replace TWRP with stock recovery (need to put back the stock recovery otherwise you cannot install the Android 6 update). For this, you can flash the original RECOVERY.img from your B008 ROM. The recovery.img needs to be flashed using fastboot mode. You can extract the RECOVERY.img from B008 using the Huawei update extractor (use the "Huawei Mediapad M2 (M2-802L)" profile in the Update Extractor tool). If you have problems, let me know and I can help you with this.
Then install the Android 6 ROM
Then reinstall TWRP, and re-root the Android 6 ROM
Unfortunately all the above steps are necessary because once you flash the new Android 6 ROM, you lose root (you need to unroot the previous ROM, and also restore recovery back to original Huawei recovery).
Click to expand...
Click to collapse
Ok, i try and report later today in finnish time
Edit:
Everything else manages just fine, version B205, but when I install SuperSU the pad stops Huawei logo, I am now waiting for a long time and does not start.
I go test now version B202
Edit:2
after B202 install i install TWRP boot normal, install SuperSU and no boot, must go B008 version
Related
To delete
To delete
Thanks for files ... we would be surely making a Custom rom for Nokia X soon ...
To delete
New software update for Nokia X: v. 11.1.1
Hey,
we have started rolling out a new update for Nokia X (RM-980): v. 11.1.1 This is a minor release and available via OTA (Over-The-Air). Find the update instructions from here: http://www.nokia.com/global/support/software-update/nokia-x-software-update/
Key changes compared to previous 10.0.3 SW version include:
Colors of 3rd party app tiles can be changed.
Phone software performance improvements.
please share this patch....
anaheiim said:
HOW TO
DOWNLOAD AND FLASH ALL ANDROID NOKIA STOCK ROM
Click to expand...
Click to collapse
Great job. Many thanks
Data Package Manager 4.2 (2013.7.5).
Not Found
The requested URL /download/hBk0dY/ was not found on this server.
Apache/2.4.6 (Ubuntu) Server at htcfanboys.tweakparadise.com Port 80
pls could you paste another link? i will really appreciate it, thanx
I can't find stock rom
After i download the rom RM-980 from NaviFirm+ and take the flash steps,
And copy the file in \ProgramData\Nokia\Packages\rm-980
when i open product support tool for store 5.0
I can't find the rom
jkenic said:
Not Found
The requested URL /download/hBk0dY/ was not found on this server.
Apache/2.4.6 (Ubuntu) Server at htcfanboys.tweakparadise.com Port 80
pls could you paste another link? i will really appreciate it, thanx
Click to expand...
Click to collapse
Corrected
setrweda said:
After i download the rom RM-980 from NaviFirm+ and take the flash steps,
And copy the file in \ProgramData\Nokia\Packages\rm-980
when i open product support tool for store 5.0
I can't find the rom
Click to expand...
Click to collapse
You use NaviFirm + to download a downgrade rom?
If this is not your goal, use rather Data Package Manager.
If you use NaviFirm+ you must rename the files correctly.
And not bother to write wholesale.
Link of post #1 rectified.
I tried NaviFirm+ cuz' Data Package Manager ROM download not available any more
- I want flash Nokia x RM-980 - give me Nokia start up logo and stop booting
- The reason: i make wrong file system permissions while root
setrweda said:
I tried NaviFirm+ cuz' Data Package Manager ROM download not available any more
- I want flash Nokia x RM-980 - give me Nokia start up logo and stop booting
- The reason: i make wrong file system permissions while root
Click to expand...
Click to collapse
The post #1 are updated for DPM, so you can use DPM.
Everything just worked fine and perfect, really superb,
Thanks for all who help and assist in this post
Thanks ( Anaheiim )
By the way my real name is: Faisal i'm from Egypt
And i'm a big fan of Bayern Munich i watch all they matches
And i play with my friends FIFA or PES and beat them with Bayern Munich LOL
Thanks again
Preparing to flash
Hello guys,
I've attached some printscreens during my preparations for a 11.1.1 update ROM version (unfortunately, OTA update is unavailable in my Region - Romania). The printscreens are in chronological order, as instructed in the first post from this thread:
1. When the download reaches 99%, it enters in a "Verification" status, but it never reaches 100%, instead it reverts to "Not downloaded". Is this normal?
2. If I try a second download, the progress bar shows "?%" for a few seconds, then resets to "0%".
3. Am I missing any files needed for flashing?
4. What's the advantage in changing the Product Code for your phone? What's the main difference between 059T9D8 RM-980 NDT EURO PL (Poland) and 059V301 RM-980 GLOBAL SWAP?
So, long story short:
I'm worried that maybe some of the files are downloaded incompletely (since the download progress never makes it to 100%), could you prove me wrong? I really want to flash my Nokia X with the latest update, but I want to make everything right in the first time.
Thanks and keep up the good work!
Bust3r.
How do i download firmware 11.1.1 for nokia x
I'm using the Data package manager tool to search with my product code but the result only have 1.1.2.2. So can you give me the link of firmware 11.1.1 or 10.1.1. Thanks!
error while doing flashing
while doing flashing it is showing error
'Dcp was referenced from the Vpl but the file was not found: 'C:\ProgramData\Nokia\Packages\Products\RM-980\RM980_059V301_10.0.3_061.dcp'
Exception:
System.IO.FileNotFoundException: Dcp was referenced from the Vpl but the file was not found: 'C:\ProgramData\Nokia\Packages\Products\RM-980\RM980_059V301_10.0.3_061.dcp'
at Nokia.Gamma.VariantPackage.VplParser.FlashFiles(St ring useCase)
at Nokia.CareSuite.PlugIns.GammaRecovery.RecoveryDial og.RecoveryDialogModel.CheckDataPackage()
at Nokia.CareSuite.PlugIns.GammaRecovery.RecoveryDial og.RecoveryDialogModel.Flash()
at Nokia.CareSuite.PlugIns.GammaRecovery.RecoveryDial og.RecoveryDialogModel.<HandleDownloadVariantPacka geCompleted>b__10(Object state)
Please someone help me with this
Im using the Vanilla AOSP rom
And when i try to flash back to the stock rom, it's stuck on this step then show the error window,
Product type
rm-980
product code
059T986
will give u the latest firmwiire... TRY THAT ONE @maxricardo ... ALSO OPEN UR BACK COVER.. THERE IS A PRODUCT CODE... USE THAT CODE IF STILL ERROR...
thanks for the help mate.. everything went so smooth on RM-980..
i've got this message when try to download a firmware
RM-914 059S3Q0
Download variant package failure details
Issue category : RemoteServerException
Wrong file size or checksum: nds2.fds-fire.nokia.com/fds_fire/1401/2414/7334088385/7A3F18F9_RM914_3056.40000.1349.2003_RETAIL_apac_indonesia_205_03_367275_prd_signed.ffu
Update: The instructions below are for the AGM X1 eu version, for the AGM X1 International version follow this thread, it's a work in progress and not available yet.
As you might be aware the AGM X1 is a fantastic rugged android, aside from the great hardware, the source code of the phone is available to devs. The combination of excellent ruggedness, hardware and open source makes the AGM X1 "the best choice in phones" at the moment for me period.
Unfortunately the information on how to root and install the available Lineage OS port is not very clear
I spent a few hours trying to find the best place to start and it's quite difficult to find
https://w3bsit3-dns.com/forum/index.php?showtopic=814951
This page contains a post below the main top section of the page.
https://w3bsit3-dns.com/forum/index.php?showtopic=814951
Here's the start of the important stuff with some additional information that I added
"The jist of the thread
TWRP 3.1.0 for AGM X1
---------------------
AGM-X1-flash-TWRP-root.zip ( 21,66 ?? )
https://w3bsit3-dns.com/forum/dl/post/10034644/AGM-X1-flash-TWRP-root.zip
OR
Download TWRP + ROOT from Google
https://drive.google.com/open?id=0B871Z4mt2B7Qb0RLMVlSemR4Szg
sha256sum
AGM-X1-flash-TWRP-root.zip b34b19f6666f0456f68e3a452c97aacf2fd3f1b06819ef7a633d95259d22a25f
SR3-SuperSU-v2.79-SR3-20170114223742.zip e147970ca377a184a177092f4c4a8022420cc30785fdaf95e16703da8312426d
Now here comes the difficult part, trying to decipher the following text
Text from thread (bad english)
Installation takes place in a similar way as inthis post, Except that you need to choose the same name! The fifth! The item and the installation of the root rights occurs automatically when you exit TWRP.
Can anyone help me with this, I cannot decipher the above paragraph. Also note that this forum is broken and not working correctly as a site (many issues including: no registration available and also the important link in the paragraph above does not work)https://forum-lw-1.xda-cdn.com/images/smilies/rolleyes.gif
P.s not interested in king root method (too many mentions of malware), will use twrp.
Update: (thanks to Skill3r)
clearer guide - also note that this zip contains twrp 3.0 instead of 3.1 due to backups not working with 3.1 (important)
https://forum.xda-developers.com/an...m-snapdragon-617-4gb-64-t3533020/post71877054
The steps :
First You need to download this package and extract it : http://www53.zippyshare.com/v/3sgYq5cu/file.html
sha256sum
AGM-X1-flash-TWRP - Skill3r MOD.rar a0e755dc513b716e5a5369481f0761a4c6a9ec60401bd9c0c060579da87f3668
Contents with sha256 hash
adb.exe f05ff055b2ce9213d0b349da7ef713664d66a13134be76820cd072cd1e44211a same as twrp 3.1 version
AdbWinApi.dll 14a51482aa003db79a400f4b15c158397fe6d57ee6606b3d633fa431a7bfdf4b same as twrp 3.1 version
AdbWinUsbApi.dll 041c6859bb4fc78d3a903dd901298cd1ecfb75b6be0646b74954cd722280a407 same as twrp 3.1 version
fastboot.exe 632f4f2039b76082f2c090f6aec43893e93e8b32d0aae6b7cfa03f9b71d5d897 same as twrp 3.1 version
One-key-flash-twrp.bat f3e5a611166e970cb41a0040979da305b9d91abc44537cab9af94110381fbf54 different from 3.1 version
recovery_AMG-X1_es_by_MDSdev.img 3eb8df185afaacaae4a754ba3c18e5e86ea140f0b115ab73d28fe2ba64088fae different from 3.1 version
SR3-SuperSU-v2.79-SR3-20170114223742.zip e147970ca377a184a177092f4c4a8022420cc30785fdaf95e16703da8312426d same as twrp 3.1 version
1) Enable the developper settings
Go to Settings>About phone and hit "kernel version" 7 times to unlock
2) Enable the OEM bootloader unlock
Find in settings>dev options
3) Enable the USB debugging
Also in settings>dev options
4) Plug an usb cable and when the windows ask for the RSA identity of the computer, allow it and check to always allow the computer.
5) Shutdown your phone
6) Press VOL down + power and after long press the power button
7) Now in recovery mode, go to reboot to bootloader, a green message is shown with fastboot.
8) Now launch the One-key-flash-twrp.bat in package and plug your phone
9) Press any key and follow the instructions in the script.
10) TWRP should launch, you need to swipe to allow modifications in system
11) Press a key in the script, TWRP should reload, TWRP is now installed in the phone, you need to allow modifications in system again.
12) To root the phone, you just need to exit TWRP, he gonna ask to root the phone, you just need to swipe to root the phone.
Now you have TWRP installed and the phone is rooted.
If something goes wrong and bootloop the phone, please just follow the AGM instructions with the original package and the procedure to reflash the rom (on the external SD card and with VOL UP + VOL Down + Power)
I've made progress, but I'm stuck on finding a suitable driver for the adb interface on windows XP for the AGM X1.
For drivers I've tried
NOT WORKING! Google USB drivers
https://developer.android.com/studio/run/win-usb.html
sha256sum
latest_usb_driver_windows.zip 1ee1d023a99ffac962af4454eb9b9900f6858c687b4d5311e8fb361548d6c078
NOT WORKING!
https://forum.hovatek.com/thread-16965.html
which should bring you here
https://drive.google.com/file/d/0B4S-Z726VJ2SLW9zNXdqWDBQQkE/view
sha256sum
a3312727a77c3ab89e0d7463cd252cffec554a182f78195f6908f62132c5c174
The important file in the zip archive is
SHA-256 08e5e7e5f30801b363f08a6106425faa1c505bd048a18c846a5b3e5959a4998e
Called
Setup.exe
Qualcomm_USB_Driver_V1.0.exe
among others.......
MD5
906c4effd6a20be22ea026a43a3cb7b3
SHA-1
89df6ca0d893d9355741d8ca11cdebea1fbbb095
NOT WORKING!
Univeral drivers
https://github.com/koush/UniversalAdbDriver
https://adb.clockworkmod.com/
sha256sum
UniversalAdbDriverSetup.msi 4e77e303bba6cf84588bdb6da91f7a875d406f7930cbe9f4d2aae0b643c0c928
NOTE: Problem installing: universal adb driver, there was a problem with this windows installer
Does any one have any advise please. Obviously I've checked the Manufacturers site they have not provided a driver. The chipset is Qualcomm MSM8952.
Thanks in advance.
Hello, for the drivers, simply plug the phone on USB and select CD in options (where you can check 'simply reload' mtp etc ...)
On the computer you can install the drivers now
Hi Skill3r,
Recommended (MAYBE THE DRIVERS WORK ON OTHER VERSIONS OF WINDOWS, BUT LINUX IS SO MUCH EASIER/BETTER)
I gave up on Windows XP. Now I'm using Xubuntu 16.04 LTS and EVERYTHING IS CONNECTING TO THE COMPUTER with this guide (without going to qtadb installation)
http://bernaerts.dyndns.org/linux/74-ubuntu/354-ubuntu-xenial-android-adb-fastboot-qtadb
p.s the vendor ID is "Qualcomm, Inc": with the code: 05c6 (it's in that github download in the link above, no need to add it specially just follow the guide)
The phone is recognized no special drivers required IT ALL THERE ALREADY! I took the commands from the bat file, changed (take away .exe e.g fastboot.exe to fastboot)
So the problem I'm getting now just after loading twrp with this command
fastboot boot recovery_AGM-X1_es_by_MD5dev.img
And this problem is............
That the touchscreen is unresponsive and I'm unable to check the box and swipe to allow TWRP to modify the system.
I have the AGM X1 International edition.
For me also:
Wenn I´m in the TWRP menu, i´m nt able to click on a button or swipe the last button, because the Touchscreen doesn´t work.
How can I solve this problem, install twrp and root the phone? because i would install LINAGEOS...or what is the best Rom/Custom Rom for the agm x1?
Please help me.
thanks
Both twrp image files below (twrp 3 and 3.1) have the touchscreen problem
sha256
AGM-X1-TWRP-3.1.0.img 22b7d529511b0b191c09e850c14b0d4ed6e32cdddc6defd688bcd78d40be2528
recovery_AMG-X1_es_by_MDSdev.img 3eb8df185afaacaae4a754ba3c18e5e86ea140f0b115ab73d28fe2ba64088fae
motsch_, what version of AGM X1 do you have, international?
Have you found any references to this problem in the main discussion pages.
We need to look for any references to this problem, or special img's for this version of phone.
Here's the older xda thread on the agm x1
https://forum.xda-developers.com/ge...ualcomm-snapdragon-617-4gb-64-t3533005/page12
Hi,
how can I see which version does i have?
For the moment i havent found any solution for installing twrp.
I have rooted the phone with Kingroot.
Doesnt exist a solution for us?
We can go to "settings" > "about phone" > scroll to bottom and let me know the
hardware version
software version
kernel version
I know mine is X1 international not EU as I just bought it and the EU version is discontinued, it has the following
hardware version: V1.00
software version: L1253.6.03.01.BYD
kernel version: 3.10.73
Also is there any awesome developers out there that would be interested in making a TWRP version - forked from the original TWRP and put on github.
And maybe then make your own port of Lineage, again with all changes to original Lineage forked on github.
Open Source and transparency of course is the reason for this.
Any one else with a AGM X1, please chime in because if we can get just a few dollars together we can get this done very quickly.
I pledge $25 for round one
Here's a reference to the touchscreen issue
https://translate.google.com/transl.../index.php?showtopic=814951&st=460&edit-text=
08/01/17, 18:45
"Am11go,
I downloaded AGM X1 TWRP Supersu from the caps, it helped, booted TWRP, but the screen did not react at all, like all buttons except on / off, it extinguishes the screen and does not include anymore ... Apparently the hands are crooked, although with bv5000 It was. How to determine which TWRP, under which version?"
if you can find a solution, can you let me please know that?
Found on 4PDA :
Demanda Sam, dit - il. TWRP assemblé avec le noyau et DTB de L1253.6.02.01.BYD. Maintenant , l'écran tactile fonctionne très bien.
hxxps://4pda.ru/forum/dl/post/10490628/twrp_3.0_L1253.6.02.01.BYD.zip
hxxps://4pda.ru/forum/dl/post/10490629/twrp_3.1_L1253.6.02.01.BYD.zip
AGM X1
HARDWARE & VERSIONS
International version
screen: Edo rm67191 fhd Amoled non-oleofobic non-sunlight readable
HW: Qualcomm MSM8952 hs8952qc
Hw other: RAM 4 Gb LPDDR3 933 mhz
fingerprint reader – FPC1020
notification led – aw2013
camera – Omnivision OV13850 13MP ??
SW: Android 5.1.1 LMY47V
L1253.6.02.01.BYD
EU version
screen: Samsung s6e3fa3 fhd super amoled oleofobic?? non-sunlight readable??
HW: Qualcomm MSM8952 hs8952qc
SW: Android 5.1.1 LMY47V
L1253.6.02.01.EU
Gold version
screen: like international?
HW: same?
SW: like international?
reference discussions: https://4pda.ru/forum/index.php?showtopic=793964
https://forum.xda-developers.com/ge...gm-x1-qualcomm-snapdragon-617-4gb-64-t3533005
https://www.movilesdualsim.com/foros/agm-x1-sd617.1152/
about screen: https://www.devicespecifications.com/en/editor-review/993738/3
http://gearopen.com/phones/agm-x1-review-rugged-smartphone-not-drown-but-froze-53924/
KERNEL SOURCE
https://github.com/zhaochengw/android_kernel_agm_agma3eu
KERNEL CONFIGS EU vs INTERNATIONAL MAIN DIFFERENCE
EU
CONFIG_TOUCHSCREEN_GT1XX=y
CONFIG_TOUCHSCREEN_GT1X_GESTURE=y
CONFIG_TOUCHSCREEN_GT1X_FH=y
# CONFIG_TOUCHSCREEN_SYNAPTICS_DSX_V20 is not set
INTERNATIONAL
# CONFIG_TOUCHSCREEN_GT1XX is not set
CONFIG_TOUCHSCREEN_SYNAPTICS_DSX_V20=y
CONFIG_TOUCHSCREEN_SYNAPTICS_DSX_I2C_V20=y
CONFIG_TOUCHSCREEN_SYNAPTICS_DSX_RMI_DEV_V20=y
CONFIG_TOUCHSCREEN_SYNAPTICS_DSX_TEST_REPORTING_V20=y
CONFIG_TOUCHSCREEN_SYNAPTICS_DSX_FW_UPDATE_V20=y
# CONFIG_TOUCHSCREEN_SYNAPTICS_GLOVE is not set
I compared the kernel configs from latest international lollipop rom with the one from Flyme OS 5 (compatible with x1 EU). I have not a boot.img from latest EU firmware, but should not matter.
This should explain the black screen when trying to install EU rom on International X1.
I found these options are not enabled in standard kernels, they may be of interest:
CONFIG_MSM_VPU CONFIG_POWER_AVS_MSM CONFIG_USB_MSM_ACA
reference: how extract kernel configs with extract-ikconfig (from kernel_dir/scripts)
https://github.com/MotorolaMobilityLLC/kernel-msm/issues/73
ROMS
EU: stock,lineage 13, flymeOs 5-6 https://4pda.ru/forum/index.php?showtopic=814951
INTERNATIONAL: only stock (latest is L1253.6.03.02.BYD)
lineage 13 (removed) https://4pda.ru/forum/index.php?showtopic=814951&st=300#entry62399105
PORTING ROMS AND KERNELS
From EU to International:
take EU roms and replace boot.img with one from International roms? (kernel and dtb table??)
From other Phones:
- Similar MSM8952 Phones: https://www.gizmotimes.com/lists/phones-qualcomm-snapdragon-617-processor/19660
- Guides: https://forum.xda-developers.com/android/general/how-to-port-roms-easy-100-t2804390
https://forum.xda-developers.com/showthread.php?t=2707438
http://ohheyitslou.blogspot.it/2011/09/ohheyitslou-custom-android-kernel-guide.html
- Interesting Kernels: https://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836
On Snapdragon 617 at the moment should be possible Overclock, but I have found no Voltage control patches from other phones kernels.
TWRP
EU: https://4pda.ru/forum/index.php?showtopic=814951
INTERNATIONAL: https://4pda.ru/forum/index.php?showtopic=814951&st=300#entry62309514
TWRP 3.0 for android 5, TWRP 3.1.0 should be for android 6 and it may have problems with restoring
TWRP reference info https://www.movilesdualsim.com/tema/twrp-by-mdsdev-para-el-x1.168070/
Hi liamotoub,
Thanks for the information. So Lineage OS is not available on the international version of the AGM X1 yet. I see.
Also Thank you skill3r for the links, I see they are 404 now unfortunately.
liamotoub, you seem to know what you're doing? would you consider taking on this as a project.
It's certainly worth keeping an eye on 4PDA, pitty I cannot read russian. If any members of 4PDA in the loop regarding the AGM X1 international are reading this please chime in. Thank you all
Hello, unfortunately I'm not a programmer, I just do "trial and error".
404 is a 4pda.ru error for not registered users, follow this guide to register
hxxps://doorsgeek.blogspot.it/2015/08/4pdaru-loginregister-captcha-tutorial.html
To read just use google translate
hxxps://translate.google.com/translate?hl=it&sl=ru&tl=en&u=https%3A%2F%2F4pda.ru%2Fforum%2Findex.php%3Fshowtopic%3D793964%26st%3D1300&sandbox=1
PS. another phone with a lot of ROMs (android 5 6 7) and similar hardware of X1 (msm8952) is ZTE Nubia Z11 mini
hxxps://translate.google.com/translate?hl=it&sl=ru&tl=en&u=https%3A%2F%2F4pda.ru%2Fforum%2Findex.php%3Fshowtopic%3D803370&sandbox=1
and what can i do with the "twrp_3.0_L1253.6.02.01.BYD.img" from the download from 4pda?
I would install twrp on my x1
motsch_ said:
and what can i do with the "twrp_3.0_L1253.6.02.01.BYD.img" from the download from 4pda?
I would install twrp on my x1
Click to expand...
Click to collapse
With TWRP you can flash another image (lineage OS for example, when we find or make a suitable version for the international version AGM X1)
TWRP will also give you the option to get root permissions, so you can use certain apps that require it. It's like the difference between user and administrator account in windows. It's called rooting because Android is based on Linux, the root account is the account with "super user" privileges, your phone will be open to allow more areas of the system to be used/wrote to/read. It allows your phone it's full potential.
With TWRP we can also do backups and restores of the entire existing ROM and phone contents
So TWRP is the first step before we get the ROM (lineage OS) on the phone https://forum-lw-1.xda-cdn.com/images/smilies/cowboy.gif
Another option for rooting is available called King Root however this comes with a lot of MALWARE AND ADWARE and it is advised not to use it. Besides it doesn't have all the flashing, backup and restore tools anyway. It just gets you root.
That is why we really need to find a working copy of TWRP for the AGM X1
INSTRUCTION TO COMPILE KERNEL (with android ndk on linux 64bit)
git clone hxxps://github.com/zhaochengw/android_kernel_agm_agma3eu
cd android_kernel_agm_agma3eu
export ARCH=arm64
export SUBARCH=arm64
export CROSS_COMPILE=/opt/android-ndk/toolchains/arm-linux-androideabi-4.9/prebuilt/linux-x86_64/bin/aarch64-linux-android-
[adapt commandline to your installation or use the one in the kernel sources (toolchains/aarch64-linux-android-4.9/bin)]
make xconfig
[load your agm X1 config file, EU version is in arch/arm64/configs/agma3eu_defconfig,and make your changes]
make -jX
[where X is number of your cpu cores]
bootimg/dtbTool -o dt.img -s 2048 -p ./scripts/dtc/ ./arch/arm/boot/dts
bootimg/mkbootimg --ramdisk bootimg/ramdisk_agma3eu.img --ramdisk_offset 0x01000000 --base 0x80000000 --tags_offset 0x00000100 --pagesize 2048 --kernel arch/arm64/boot/Image.gz --cmdline "console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom msm_rtb.filter=0x237 ehci-hcd.park=3 androidboot.bootdevice=7824900.sdhci lpm_levels.sleep_disabled=1 earlyprintk" --dt dt.img --output boot.img
Image.gz ramdisk_agma3eu.img dt.img will be incapsulated in boot.img.
Test if kernel works:
#adb push boot.img boot
If not boot restore previous boot image.
notes:
1.if you load the international kernel config, and you got some errors related to VENDOR, enable
CONFIG_MACH_HIS_SMARTPHONE CONFIG_HIS_BOOT_INFO
and fill CONFIG_HIS_VENDOR_NAME: Android CONFIG_HIS_PRODUCT_NAME:agma3eu
2.if you got an error related to msm_dba_internal.h not found, edit
drivers/video/msm/msm_dba/msm_dba.c and replace #include <msm_dba_internal.h> with #include "msm_dba_internal.h"
PS. replacing my boot.img is not sufficient to make Lineage 13 and FlymeOS5 work, they go in bootloop.
I've uploaded the TWRP versions for the AGM X1 "International version" from the 4PDA links above, to save somebody the trouble of signing up. Version 3.1 is what you want I think (but maybe the backups/restores don't work on v3.1 as skill3r has pointed out or maybe the international version is different?)
SHA-256
72422060a34a995a6f29da1c0a6d5737f7df3ad426d0a7105267730f22e74b9c
File name twrp_3.0_L1253.6.02.01.BYD.zip
Download: https://mega.nz/#!0yZCyIaA!lUnmyeQNinQlzIcwfWZ8F5l6Pz2jlumxzhVx57U6G-M
SHA-256
96c92a52805c0db4fc84c652199887e93a30dae3fe3ead36e14715f7fc736d22
File name twrp_3.1_L1253.6.02.01.BYD.zip
Download: https://mega.nz/#!FmxmFKgK!cCfNsGj3gRMVkl_EI6ROI2-5RbFQsuyElFxRIvN76ug
Also, liamotoub, send me your PayPal address and I'll send a few dollars your way, that information is great thus far
These 2 files should be TWRP 3.0.3 and 3.1.0 right?
I want to point out that also the latest 3.1.1 ( relased for the gold X1 by a Spanish forum, movilesdualsim) works on international X1 mega:#!vB9g3Aab!_gyrr6rP_rJDheGgIseI2u2TglNw1vmv7dDjUnDYJb4 with not encrypted phone.
To try it without touching the recovery partition use:
#adb reboot bootloader
#fastboot boot recovery_name.img
EDIT: it give some problems when flashing new INTernational ROMs, because they think the phone is GOLD and refuse to install due to their updater-script; should be sufficient to modify the build.prop of this recovery or a similar file, with international version "signature".
TWRP 3.0.3 3.1.1, those that I tried, fail to recognize encrypted fylesistems, so backups of this kind will not work.
Another minor bug is the wrong date (1970) in automatic naming of backups folder, but that's common on most phones.
I managed to make FlymeOs 5.1 boot on international X1, but I don't recomend it, it's full of bloatwares and wifi and other things looks to be not working
https://mega.nz/#!djJ3jbbT!Kr6qMyTcggsrYyPeDnySHpp7EOgUZnG-tvTqewdqkmk
Make full working nandroid backup before trying it.
To port lineage 13 I think marshmallow kernel sources are needed, with present sources only lollipop roms could be ported AFAIK, like CM 12.1.
Question to X1 users: on stock rooted rom, do root requesting apps (afwall, kernel audiutor etc) start at boot time? On mine no, I have to start them manually.
On stock rom beware of these preinstalled apps, may be adware:
com.gangyun.beautysnap
com.oupeng.max.hisense
Is there any specific advantage using the TWRP movilesdualsim 3.1.1 version rather than the 4PDA versions other than a slightly higher version.
If I encrypt my phone would there be any other issues other than not being able to do twrp backups and restores? It would still work?
In fact, I've released Win10 Mobile Offline Update Package V5 in China, but I've never released it in xda before.
Well... I tested OTC Updater provided by Microsoft, it will get a secret update to Windows 10 Mobile 10586.107 which is already used for my Offline Update Packages.
To download OTC Updater:
http://www.microsoft.com/en-us/download/details.aspx?id=56120
Click to expand...
Click to collapse
Here's the partial output log:
Code:
...
(ID): Found update: Windows Phone 8.1 Production Bundle - OS 10.0.13080.107 update for Nokia RM-1010_1003 CMC-CN based devices
(ID): 196 installable packages found
(ID): 1/196: Downloading Microsoft.MainOS.Production_Lang_sk-SK.spkg.20093217.cab
(ID): 2/196: Downloading Microsoft.MainOS.Production_Lang_ru-RU.spkg.20093216.cab
...
I was using Nokia Lumia 638 when testing.
I presume it will get a hidden update called "Windows Phone 8.1 Production Bundle - OS 10.0.13080.107 update for (PhoneManufacturer) (PhoneManufacturerModelName) (PhoneMobileOperatorName) based devices" to identify if the device is eligable to W10M, and the update itself provided all of the packages with extension name spkg/spku/spkr instead of cbs/cbsu/cbsr.
Right now, I collected 361 spkg/spkr/spku for the project, but far from perfect. List of packages is attached below.
What I'm going to request is:
Try to get all of the packages links of "Windows Phone 8.1 Production Bundle - OS 10.0.13080.107 update for (PhoneManufacturer) (PhoneManufacturerModelName) (PhoneMobileOperatorName) based devices".
And here's how I'm going to use a new tool with these packages as my new offline update package V6:
1. Use getdulogs command to get the device info, including it's model, codename (For example, the codename of Lumia 830 is Tesla) and packages structure.
2. Check if the phone is a cancelled prototype device, or the current OS version is supported.
3. Check if the phone is confirmed unsupported like HTC 8X, and Win 10 Mobile preinstalled device like Lumia 950.
4. Prepare required update packages according to packages structure included in the phone by copying them to a temporary directory. Remove PIN lock will no longer required, but recommended.
5. If the phone doesn't have the language you're using on PC (For example, HTC One M8 for Windows AT&T and T-Mobile don't have Chinese included), it will ask you if you want to add extra languages.
6. Push the packages in the temporary directory to your phone to execute the update procedure. Since it analyzed your phone, you needn't to worry about your default keyboard and speech if you're not using English (United States).
7. After the update procedure finished, the tool will ask you if you want to use OTC Updater to get further updates if the phone is eligable to later OS.
After V6 release, only confirmed unsupported models will get listed, which will heavily reduce the length of guide.
Custom 21.329.01.00.00 firmware and 17.100.19.01.00 web interface for E5770
The firmware is based on the original global firmware version 21.329.01.00.00. It can be installed on any technological firmware, or updated from a modified firmware.
Flash using balongflash (Windows, Linux).
Attention!
This firmware can render your device unbootable! Use it only if you are aware of all the risks and consequences. In case of any problems, do not wait for help, you're on your own. Do not install firmware by non-tech-savvy people request, and do not sell routers with this firmware preinstalled.
Changes:
Firmware digital signature verification in the firmware server is disabled
Added support for IPv6 on mobile networks (disabled by default, could be activated "ipv6" script)
ADB installed and Telnet activated (disabled by default, controlled from the OLED menu)
The stock versions of busybox, iptables and ip6tables programs are replaced with full-fledged ones
The "atc" utility is installed to send AT commands from the console
Installed "ttl" script for modifying (fixing) TTL (for IPv4) and HL (for IPv6)
Installed "imei" script to change IMEI
A local transparent proxy server "tpws" and a script "anticensorship" are installed to circumvent censorship to sites from the registry of prohibited sites in Russian Federation (IPv4 only)
Added DNS over TLS resolver stubby (version 1.5.1, compiled with OpenSSL 1.0.2p) and DNS-level adblock (IPv4 only)
Added extended menu on OLED screen
Added RNDIS and ECM Ethernet switching functionality without a switch program on a computer
All NVRAM items are unlocked
AT^DATALOCK code is disabled
Added kernel module TUN/TAP (for OpenVPN and other programs)
Added OpenVPN (version 2.4.6, compiled with OpenSSL 1.0.2p) and scripts for DNS redirection
Added curl (version 7.63.0, compiled with OpenSSL 1.0.2p)
Added EXT4 kernel module and swap support
Added script for installing Entware application repository
Added script "adblock_update", for updating the list of advertising domains
Added script to change MAC address of Wi-Fi in Extender mode (script "wifiext_mac") and USB MAC addresses (script "usb_mac")
Removed mobile connection logging (mobile logger) to extend flash memory lifetime
Multilingual web interface with GSM/UMTS/LTE band selection menu
The extended menu on the OLED screen allows you to manage network mode (LTE/3G/GSM), TTL modification, circumvent censorship, ad blocking, IMEI change, USB composition, control access to the web interface, Telnet and ADB.
TTL modification and IMEI change require a reboot. The remaining menu items are applied instantly.
To activate extended menu, press left (WPS) button 7 times on Wi-Fi information screen.
The "anticensorship" script helps to bypass Deep Packet Inspection (DPI) systems on some operators in order to bypass web site blocking. It starts the local proxy server from zapret complex https://github.com/bol-van/zapret, modifying the packets in such a way as to complicate their analysis, and redirects all traffic to ports 80 (for HTTP) and 443 (for HTTPS) to local proxy. The proxy server works autonomously, without any third-party server on the Internet. It is recommended to use it in conjunction with DNS over TLS, in order to prevent possible DNS hijacking by the operator.
Advertisement blocking is performed on DNS level with dnsmasq DNS server. It works with DNS over TLS as upstream, requests for which are redirected if the corresponding menu item is activated from the OLED screen. EasyList and RuAdList https://forums.lanik.us/viewtopic.php?f=102&t=32524 from raletag and AdAway https://adaway.org/hosts.txt are used as an ad lists.
Ad-blocking at the DNS level works worse than full-fledged content blockers in browsers (AdBlock, µBlock), but it works on any device and in any program without additional settings.
You can also control ad blocking with the "dns_over_tls" script.
Domain lists could be updated using "adblock_update" command.
Entware application repository allows you to install additional Linux software from the armv7sf-k3.2 entware repository http://bin.entware.net/armv7sf-k3.2/Packages.html, using "opkg" package manager used in open source firmware for OpenWRT routers. Entware is installed using the "entware install" command. Entware files are installed in /opt, which is mounted in /online/opt. You can install many programs on 30 MB free space after installation on /online partition.
The router and Entware environments are independent of each other, the installed Entware software cannot be called from the router's environment, and the firmware programs and scripts cannot be called from the Entware. This was done to ensure that the installed packages would not conflict with files in the firmware.
To gain access to the Entware environment, use the "entware shell" command, to exit, type exit (or press CTRL+D).
Entware is designed for advanced users who understand how to customize and use installable programs. About 15 MB of free RAM is available in the router, the launch of heavy programs can lead to the crash of important services for the router (especially when DNS over TLS is enabled), remember that.
Download link
https://github.com/Huawei-LTE-routers-mods/Huawei_E5770_mod_fw_webui
More information about Huawei LTE routers (zeronet network): https://zn.amorgan.xyz/1HegcCNqxTuhPaHmjZwPGZ9LY34vXD6H1V/
E5770 O2 FW version 21.200.19.01.405 SIM unlock
Huawei E5770 from British O2 network with firmware version 21.200.19.01.405 could be unlocked for free with a special firmware, without disassembling the device.
This firmware is based on 21.200.19.01.405 version and could be installed without flash code.
E5770s_Update_21.200.19.01.405_o2_simunlock_signed.7z
If you want to install another official firmware or a custom firmware, you need to downgrade 21.200.19.01.405 to a special technological firmware version 21.180.99.10.00, which does not check firmware digital signatures.
E5770s_DOWNGRADE_o2_21.200.19.01.405_to_21.180.99.10.00_signed.7z
To install the firmware, press both RESET button (on the back of the device) and POWER button, connect it to the PC and use balongflash software (Windows, Linux)
More information about Huawei LTE routers (zeronet network): https://zn.amorgan.xyz/1HegcCNqxTuhPaHmjZwPGZ9LY34vXD6H1V/
Thabks for the share. Is it possible to unlock all bands to use it anywhere in the globe?
link not working
Hi I tried downloading the modded firmware but it only goes to 20% every time then hangs. can you fix please or host somewhere else.
many thanks
abiliotiago said:
Thabks for the share. Is it possible to unlock all bands to use it anywhere in the globe?
Click to expand...
Click to collapse
No, that's a hardware limitation. Different hardware modifications have different radio hardware. They could be converted by soldering some components though.
paybelb said:
Hi I tried downloading the modded firmware but it only goes to 20% every time then hangs. can you fix please or host somewhere else.
many thanks
Click to expand...
Click to collapse
You can download ZeroNet and download it from there, because ZeroNet to Internet gateways are unreliable.
E5770 FW version 21.327.01.00.1133, 21.200.19.01.405, 21.318.01.02.07 downgrade to technological 21.180.99.10.00
This special firmware allows installing technological firmware on firmware versions mentioned in the title, without entering OEM code (AT^DATALOCK), and without using test-point (needle method).
Technological firmware allows installing any other firmware (even with incorrect or corrupted signature), without any restrictions.
WARNING: If you flash this firmware, you won't be able to revert your old firmware version because there's no official firmware files of these version available in public access. You can install any other firmware though.
→ E5770s_DOWNGRADE_21.318.01.02.07_to_21.180.99.10.00 ←
→ E5770s_DOWNGRADE_21.327.01.00.1133_to_21.180.99.10.00 ←
→ E5770s_DOWNGRADE_21.200.19.01.405_to_21.180.99.10.00 ←
More information about Huawei LTE routers (zeronet network): https://zn.amorgan.xyz/1HegcCNqxTuhPaHmjZwPGZ9LY34vXD6H1V/
ValdikSS said:
No, that's a hardware limitation. Different hardware modifications have different radio hardware. They could be converted by soldering some components though.
Click to expand...
Click to collapse
Thanks for the explanation.
Which router do you recommend for the most compatibility LTE worldwide?
abiliotiago said:
Thanks for the explanation.
Which router do you recommend for the most compatibility LTE worldwide?
Click to expand...
Click to collapse
Probably something with Qualcomm chipset, which I'm not savvy in.
It depends on LTE bands or countries you're planning to use the device.
ValdikSS said:
Probably something with Qualcomm chipset, which I'm not savvy in.
It depends on LTE bands or countries you're planning to use the device.
Click to expand...
Click to collapse
Not sure right now
I just wanted something that could work for holidays wherever I decided to go
Thanks
unfortunatly balong_flash doesn't seem to work on windows 10
zebignasty said:
unfortunatly balong_flash doesn't seem to work on windows 10
Click to expand...
Click to collapse
worked fine for me on Windows 10 Pro
Version 2.3.1. Based on firmware 21.329.01.00.00 and webui 17.100.19.01.00
Changes since v2.3:
Firmware:
* Fix passwd_def telnet default password file
* Fix OpenVPN NAT scripts: properly remove added FORWARDING and INPUT DROP rules, clarify README
* Clarify net.{down,up} scripts
There are more than one variant of E5770.
Will this firmware work on E5770S-923 model?
BarakOsama said:
There are more than one variant of E5770.
Will this firmware work on E5770S-923 model?
Click to expand...
Click to collapse
Yes it will.
Hi OP,
my device is stuck on download mode.
can you please explain the flashing steps for the custom firmware.
As per your Read-Me the firmware should be flashed by balong_flash FLASH_FILE.BIN command.
Whats unclear to me is which file is to be flashed first. There are 2 .bin files in the custom firmware archive.
It will be a great help if you can give a step-by-step guide.
BarakOsama said:
Hi OP,
my device is stuck on download mode.
Click to expand...
Click to collapse
First of all, to install custom firmware you need to install technological firmware somehow. You can't install it just by flashing, it will require flash code which cannot be obtained easily. To bypass flash code check, I made downgrading firmwares for several firmware versions. You need to install downgrading firmware for your current firmware version, which will downgrade to technological firmware, and from technological firmware you can install any firmware, including custom one.
What exact steps did you perform, what exact result did you get?
ValdikSS said:
First of all, to install custom firmware you need to install technological firmware somehow. You can't install it just by flashing, it will require flash code which cannot be obtained easily. To bypass flash code check, I made downgrading firmwares for several firmware versions. You need to install downgrading firmware for your current firmware version, which will downgrade to technological firmware, and from technological firmware you can install any firmware, including custom one.
What exact steps did you perform, what exact result did you get?
Click to expand...
Click to collapse
After two days of googling I found the original firmware I had on the device and now the device is working again :victory:
Can you provide me a downgrading firmware to E5770s-923 21.316.03.00.1133 firmware version?.
E5770s_UPDATE_21.316.03.00.1133_WEBUI_17.100.13.02.1133_MRE5.zip
I flashed the custom firmware.
But somehow I cannot access the extended menu.
Software version: 21.329.01.00.00
Web UI version: 17.100.19.01.00
BarakOsama said:
I flashed the custom firmware.
But somehow I cannot access the extended menu.
Software version: 21.329.01.00.00
Web UI version: 17.100.19.01.00
Click to expand...
Click to collapse
You need to press left button 7 times on the wi-fi information screen.
After a bit of experimenting (and a lot of fights with the bootloader since it always decided to relock itself preventing me from simply using fastboot) I managed to get the global fw to run on an AT&T device.
TLDR: You can just dd the global partitions while rooted and then restore through adb sideload.
Guide: https://github.com/filiphsandstrom/surface-duo
quick question.
for step number 2 "Use payload_dumper from the rooting guide to extract the partition images", am i extracting the partition images from the Global version or the AT&T version?
So does this mean anyone using this firmware has sim unlock? I saw on the GitHub you mentioned it works on another network outside of AT&T
edchuxda said:
quick question.
for step number 2 "Use payload_dumper from the rooting guide to extract the partition images", am i extracting the partition images from the Global version or the AT&T version?
Click to expand...
Click to collapse
The global version. The script will then dd those to the correct place
I had great success with this and have relocked the bootloader as a normal duo device thanks, if anyone has any questions about how i managed it let me know. Thanks so much @filfat
I just wanted to thank the OP for making this process easy with the instructions and for the new life given to this phone. Now that the phone has been converted to the global version what happens if another update comes down the pipe? Do we flash the global version, at&t version or sit tight and await further instructions ?
@Draco32 or @filfat
First:
1|duo:/data/local/tmp # chmod +x globalify.sh && ./globalify.sh;
./globalify.sh[7]: syntax error: unexpected 'newline'
1|duo:/data/local/tmp #
Why error?
Next:
I am assisted by the guide on this page:
GitHub - filiphsandstrom/surface-duo: Convert a Surface Duo AT&T to the global variant.
Convert a Surface Duo AT&T to the global variant. Contribute to filiphsandstrom/surface-duo development by creating an account on GitHub.
github.com
I'm on step 8. At 47%, it shows me an aborted installation message. Reason: incompatibility.
How to solve it?
I took the system from:
https://android.googleapis.com/packages/ota-api/package/a9bfdee15f2137f020fffded98b4bdee5d8bec8e.zip
Hoffman404 said:
@Draco32 or @filfat
First:
1|duo:/data/local/tmp # chmod +x globalify.sh && ./globalify.sh;
./globalify.sh[7]: syntax error: unexpected 'newline'
1|duo:/data/local/tmp #
Why error?
Next:
I am assisted by the guide on this page:
GitHub - filiphsandstrom/surface-duo: Convert a Surface Duo AT&T to the global variant.
Convert a Surface Duo AT&T to the global variant. Contribute to filiphsandstrom/surface-duo development by creating an account on GitHub.
github.com
I'm on step 8. At 47%, it shows me an aborted installation message. Reason: incompatibility.
How to solve it?
I took the system from:
https://android.googleapis.com/packages/ota-api/package/a9bfdee15f2137f020fffded98b4bdee5d8bec8e.zip
Click to expand...
Click to collapse
The way i did it to simplify was to just copy and paste the commands unfortunately my shell wasn't executing the script correctly I had some errors
Eazii said:
I just wanted to thank the OP for making this process easy with the instructions and for the new life given to this phone. Now that the phone has been converted to the global version what happens if another update comes down the pipe? Do we flash the global version, at&t version, or sit tight and await further instructions ?
Click to expand...
Click to collapse
I have the same question when the duo announcing the newest OTA. The at&t Duo which turned to a global variant can update by OTA or must flash the new images by this method.
Draco32 said:
The way i did it to simplify was to just copy and paste the commands unfortunately my shell wasn't executing the script correctly I had some errors
Click to expand...
Click to collapse
copy and paste what commands exactly? are you saying do each .img 1 by 1? or something else? i copy/paste the commands from the github but i got stuck at 47% same as the other guy.
I just received a OTA update and it failed. I followed this method to unlock my At&t version.
How do I go about updating, but more importantly which OTA should I be looking to flash, At&t or Global?
run sideload to 94% already but still locked sim. how to know if esim is working?
Eazii said:
I just received a OTA update and it failed. I followed this method to unlock my At&t version.
How do I go about updating, but more importantly which OTA should I be looking to flash, At&t or Global?
Click to expand...
Click to collapse
Can you please confirm if esim capability was available or not after installing global variant image?
thanks!
Hi everybody,
I noticed this repository wasn't up anymore which I thought was a crying shame so I managed to track down the source code and re-uploaded it here:
GitHub - EyeCantCU/surface-duo-globalify: Converts AT&T Surface Duo to global firmware
Converts AT&T Surface Duo to global firmware. Contribute to EyeCantCU/surface-duo-globalify development by creating an account on GitHub.
github.com
I make no promises this will work successfully on your device and take no responsibility for whatever may happen. My Duo (I want in on that 3/ds and Windows 11 action) is in the mail and I'm going to be trying this myself.
CertifiedBlyndGuy said:
Hi everybody,
I noticed this repository wasn't up anymore which I thought was a crying shame so I managed to track down the source code and re-uploaded it here:
GitHub - EyeCantCU/surface-duo-globalify: Converts AT&T Surface Duo to global firmware
Converts AT&T Surface Duo to global firmware. Contribute to EyeCantCU/surface-duo-globalify development by creating an account on GitHub.
github.com
I make no promises this will work successfully on your device and take no responsibility for whatever may happen. My Duo (I want in on that 3/ds and Windows 11 action) is in the mail and I'm going to be trying this myself.
Click to expand...
Click to collapse
the link was unable now. Cloud u share it again?
cyhd said:
the link was unable now. Cloud u share it again?
Click to expand...
Click to collapse
A bit of googling found the repo https://github.com/kenpc-git/surface-duo
I wonder if updates worked after this? would this be a way for AT&T users to get the latest 12L update?
Anyone who used this and is running it still? Any issues?
Worked for me, flashed it to global and it automatically upgraded to 12L
When I try the adb sideload I have the following message:
------------------
E:
(adbd status 5)
Install from ADB completed with status 1.
Installation aborted.
-------------------
Can someone help on this ? Thank you.
Hoffman404 said:
@Draco32 or @filfat
First:
1|duo:/data/local/tmp # chmod +x globalify.sh && ./globalify.sh;
./globalify.sh[7]: syntax error: unexpected 'newline'
1|duo:/data/local/tmp #
Why error?
Next:
I am assisted by the guide on this page:
GitHub - filiphsandstrom/surface-duo: Convert a Surface Duo AT&T to the global variant.
Convert a Surface Duo AT&T to the global variant. Contribute to filiphsandstrom/surface-duo development by creating an account on GitHub.
github.com
I'm on step 8. At 47%, it shows me an aborted installation message. Reason: incompatibility.
How to solve it?
I took the system from:
https://android.googleapis.com/packages/ota-api/package/a9bfdee15f2137f020fffded98b4bdee5d8bec8e.zip
Click to expand...
Click to collapse
I had the same issue regarding "syntax error: unexpected 'newline' "
Any clue or update to it?
Draco32 said:
I had great success with this and have relocked the bootloader as a normal duo device thanks, if anyone has any questions about how i managed it let me know. Thanks so much @filfat
Click to expand...
Click to collapse
Could you tell the process of relocking bootloader?