[Q] Migrating from 5.1 SOAK to FINAL - Moto X Q&A

Hello friends!
Sorry if this is not the right board to ask questions, but this will be of public utility to everyone in a situation like mine!
I updated to every SOAK test since 5.0.2, aways used the ZIP OTA option, so I could retain my apps and (more important) data... With the final release, I see some people downgrading to get it, and other people using RSD as in this (portuguese) post: (motox-brasil.blogspot.com.br/2015/06/firmware-motox-firmware-retail-brasil.html). I use a bank app that allow me to use ATM services without the card, just generating a token from the app, and I use microsoft's and google's token generator to login on many sites with two steps autentications.
As you can see, I would be very happy if I could use a zip to get to final 5.1...
If it is impossible, I would be happy if provided with some way to backup this data with as little friction as possible...
Thanks for any help!
Ps.: I intend to edit this (first) post with any relevant info posted on thread, to serve as reference to people!

Your phone model, your soak version exact build name (see About phone tab)?

Related

Official 2.2 is out !

Hello all. The Android™ 2.2 (Froyo) software upgrade for Milestone is now being rolled out in selected countries, please visit http://moto.ly/milestonefroyo for instructions on how to upgrade your device.
From motorola on facebook
EDIT: some user in page 2 or 3 can download 2.2 from moto server, we're waiting for you !
EDIT 2 :
from sileshn and his friend borjich
http://www.megaupload.com/?d=ICJ105SS
from evolucja :
http://multiupload.com/RBL6Z1399E
from exboy
Kernel version
2.6.32.9-gafbfc43
[email protected]#1
razer54 said:
Hello all. The Android™ 2.2 (Froyo) software upgrade for Milestone is now being rolled out in selected countries, please visit http://moto.ly/milestonefroyo for instructions on how to upgrade your device.
From motorola on facebook
Click to expand...
Click to collapse
Does it still have the kernel errors?
As I see it's only for UK as for now.
razer54 said:
Hello all. The Android™ 2.2 (Froyo) software upgrade for Milestone is now being rolled out in selected countries, please visit http://moto.ly/milestonefroyo for instructions on how to upgrade your device.
From motorola on facebook
Click to expand...
Click to collapse
At this page , there doesnt seem to be any change mentioned
Code:
https://supportforums.motorola.com/community/manager/softwareupgrades
mystichobo said:
Does it still have the kernel errors?
Click to expand...
Click to collapse
seems that version is still the same, 05.02.26 - so there's few changes but probably kernel is the same like in previous O2 leak
motorola is releasing country by country.
from france, no 2.2 at this time ...
but it look like released in uk.
if someone can post sbf
EDIT : nothing too with a proxy from UK
Hopefully someone from uk can post sbf or nandroid backup for this 1
Sent from my Milestone using Tapatalk
SBF file is very appreciated in this topic ;p
sbf would be nice and also to know if its better than the o2 leak!
I hope for the best... but after reading this:
-----------------------------------------------------------------------------
Key Things to Consider Prior to Upgrading to Android 2.2 (Froyo)
-Motorola is committed to continually meet and exceed our consumers' expectations. Due to the extremely high number of requests for the Android 2.2. (FROYO) software upgrade, we are making the upgrade package available to consumers who wish to voluntarily upgrade their own devices via MSU.
-Exhaustive testing process has concluded that users may experience some adverse effects associated with the upgrade which could include slower operation of some phone functions and applications. Performance may be improved by limiting open applications.
-Media saved on your memory SD card will be preserved, but DRM (Digital Rights Management) protected Media stored on your phone's internal memory will not be preserved.
-Not all applications downloaded with your current software will be compatible with your upgraded software.
----------------------------------------------------------------------------
I can't help but feel the possibility of finding ourselves with another kernel full of DSI errors is still existent.
Motorola themselves "warn" their "volunteers" about possible slowdowns and also say having less apps open MIGHT (not even "will") solve the problem.
Sorry if I sound too douchy or pessimistic... maybe it's the fact I haven't slept at all. I hope I'm totally wrong about my assumptions.
That info was taken from this link: http://www.motorola.com/staticfiles/Support/GB-EN/froyo/milestonenotification.htm
4ny0n3 said:
I hope for the best... but after reading this:
-----------------------------------------------------------------------------
Key Things to Consider Prior to Upgrading to Android 2.2 (Froyo)
-Motorola is committed to continually meet and exceed our consumers' expectations. Due to the extremely high number of requests for the Android 2.2. (FROYO) software upgrade, we are making the upgrade package available to consumers who wish to voluntarily upgrade their own devices via MSU.
-Exhaustive testing process has concluded that users may experience some adverse effects associated with the upgrade which could include slower operation of some phone functions and applications. Performance may be improved by limiting open applications.
-Media saved on your memory SD card will be preserved, but DRM (Digital Rights Management) protected Media stored on your phone's internal memory will not be preserved.
-Not all applications downloaded with your current software will be compatible with your upgraded software.
----------------------------------------------------------------------------
I can't help but feel the possibility of finding ourselves with another kernel full of DSI errors is still existent.
Motorola themselves "warn" their "volunteers" about possible slowdowns and also say having less apps open MIGHT (not even "will") solve the problem.
Sorry if I sound too douchy or pessimistic... maybe it's the fact I haven't slept at all. I hope I'm totally wrong about my assumptions.
That info was taken from this link: http://www.motorola.com/staticfiles/Support/GB-EN/froyo/milestonenotification.htm
Click to expand...
Click to collapse
Youre not being pessimistic! is motorola!
"we can't solve DSI Error problem, so it's now a feature and no more a bug"
We all know that Froyo have too high system requirements too run well on Milestone (RAM), motorola cant make miracle... That was only reason for delayed froyo.
https:// + msuUser:ra1nb0w7C01orsMoto%[email protected]/download/SHOLS_U2_05.26.0_SIGNED_UCASHLSMR2EMEAB1B806F.0R_PDS003_USAMS1FRYORTGB_P009_A006_HWp2a_WIG145007_1FF.sbf.gz
you can try this for now
Chad_Petree said:
Youre not being pessimistic! is motorola!
Click to expand...
Click to collapse
Sigh... I suppose... ='(
Thanks v00d00ley, downloading!!
kidscracker said:
Thanks v00d00ley, downloading!!
Click to expand...
Click to collapse
Edit: It works now. Downloading!
I can't download, What's the username and password? I tried firefox and chrome and link doesn't work. I removed spaces as well.
lukas77 said:
Edit: It works now. Downloading!
I can't download, What's the username and password? I tried firefox and chrome and link doesn't work. I removed spaces as well.
Click to expand...
Click to collapse
EDIT: Lukas already got it working but this might answer to others having the same problem.
User: msuUser
Password: ra1nb0w7C01orsMoto
v00d00ley said:
https:// + msuUser:ra1nb0w7C01orsMoto%[email protected]/download/SHOLS_U2_05.26.0_SIGNED_UCASHLSMR2EMEAB1B806F.0R_PDS003_USAMS1FRYORTGB_P009_A006_HWp2a_WIG145007_1FF.sbf.gz
you can try this for now
Click to expand...
Click to collapse
rsd authentication required user and passwd
4ny0n3 said:
EDIT: Lukas already got it working but this might answer to others having the same problem.
User: msuUser
Password: ra1nb0w7C01orsMoto
Click to expand...
Click to collapse
Does not work. File not found.

[ROM & Kernel] CyanogenMod 7

Hi. I'd like to announce you that I'll try to port CM7 to Arc.
I need some people to test it too as I don't have Arc.
It'll be system.img flashable via fastboot. So, ANYONE?
Of course that you need unlocked bootloader because there's no other way of flashing system.img file except fastboot!
Note: be prepared to most probably lose all data to ensure that CM7 will run on clean system (to avoid any additional bugs).
Brick recovery:
If CM7 system.img ever bricks your phone, simply connect it to the fastboot and flash Bin4ry's rooted system.img (easiest way), or reflash with FlashTool.
Some kind of global EULA. Breaking these terms will reflect as stopping releasing progress to the public on some time.
*Do not remind me about posting my progress. I know that I have to post progress when there will be any, I'm not stupid.
*Do NOT ask me to switch to 2.3.4 CM7 because there are only nightly builds for a few devices.
*Do NOT mirror my files once they appear. Reasons:
1) With no mirrors I can keep track of download counter.
2) With no mirrors I ensure that all people download latest release, not some outdated file from mirror.
3) Mediafire is FREE and it has NO DOWNLOAD WAITING.
Everything I publish will be in this Mediafire folder. Again, don't mirror.
Update - 16th May: I have plans to make a custom kernel too. Wait for further info
Update - June 2011: Jerpelea has taken over CM7 development for Arc. FreeXperia project expanded to Xperia Arc and Play. Play will be maintained by me. Arc project closed - thread closed.
If you're happy to explain things in terms so simple a 5 year old can understand them, I'm happy to test for you...
Step666 said:
If you're happy to explain things in terms so simple a 5 year old can understand them, I'm happy to test for you...
Click to expand...
Click to collapse
Do you have SIM-unlocked phone, and can you unlock bootloader?
I've already unlocked the bootloader.
And rooted via Bin4ry's method.
I'm working 12.00-16.00 (BST) tomorrow, then off 'til 12.00 (BST) on Wednesday, so I should be around quite a bit over the next few days.
Step666 said:
If you're happy to explain things in terms so simple a 5 year old can understand them, I'm happy to test for you...
Click to expand...
Click to collapse
I don't mind to being a tester for you unless you mind I am doing this during asian time zone
Step666 said:
I've already unlocked the bootloader.
And rooted via Bin4ry's method.
I'm working 12.00-16.00 (BST) tomorrow, then off 'til 12.00 (BST) on Wednesday, so I should be around quite a bit over the next few days.
Click to expand...
Click to collapse
Great!!! Same way as you flashed Bin4ry's system.img, you'll flash this one too, so don't worry
blagus said:
Great!!! Same way as you flashed Bin4ry's system.img, you'll flash this one too, so don't worry
Click to expand...
Click to collapse
Sounds fine to me.
I'll spend this evening getting my Defy ready to use again, just in case...
I'll be happy to test - I can also help with debugging and possibly porting too (no actual dev experience, but do have the ability to read and understand things, and have plenty of linux experience). I'll be able to test over the next 3 weeks, but I do have university exams, and they take priority obviously. Once those 3 weeks are over I'll have lots of spare time for a couple of months, so can help properly then! My phone is sim and bootloader unlocked, but not rooted at the moment.
Obviously, this is my main phone, so just for clarity, not doing anything that ca affect the ability of the phone to go into fastboot mode, correct?
Step666 said:
Sounds fine to me.
I'll spend this evening getting my Defy ready to use again, just in case...
Click to expand...
Click to collapse
Worst thing that can happen is that you'll have to reflash rooted system.img by Bin4ry. But better safe than sorry
chriscpritchard said:
I'll be happy to test - I can also help with debugging and possibly porting too (no actual dev experience, but do have the ability to read and understand things, and have plenty of linux experience). I'll be able to test over the next 3 weeks, but I do have university exams, and they take priority obviously. Once those 3 weeks are over I'll have lots of spare time for a couple of months, so can help properly then! My phone is sim and bootloader unlocked, but not rooted at the moment.
Obviously, this is my main phone, so just for clarity, not doing anything that ca affect the ability of the phone to go into fastboot mode, correct?
Click to expand...
Click to collapse
Correct.
Well, knowing me luck...
I know there shouldn't be any risk, it'd just be simpler for me to have a fully functional phone to use while the Arc is being tinkered with.
Step666 said:
Well, knowing me luck...
I know there shouldn't be any risk, it'd just be simpler for me to have a fully functional phone to use while the Arc is being tinkered with.
Click to expand...
Click to collapse
Yes, if that's acceptable for you to have Arc for testing only, then cool!
It's always better to have backup phone so you have time to fix another one.
In that case, I think I'll buy myself a cheap £10 payg phone from the local supermarket, just in case - I can stick my current SIM in it while developing/testing.
I hope you both are ready for the data loss. It's necessary, to ensure that ROM will run on clean phone and avoid any bugs possible due to installed application and user settings.
I have Titanium Backup, I'll be fine
edit: to be honest, so long as I don't lose my text messages, which I back up regularly anyway, I don't really care about the rest.
I don't use my Arc for music, I have a proper Walkman for that. I basically haven't used the Arc's camera because it's a long time since I last had a phone with a good camera, so I'm unused to it now and I can always re-download apps...
Good luck guys nice to see a bit of community co-operation, hope all goes well
I shall follow the goings on with anticipation
Sent from my LT15i using Tapatalk
Can redownload apps - it's a new phone, so don't have any text messages and music is all on my PC contacts, emails etc are all saved on google's servers and don't have any photos!
Thanks a lot
So, I can count on rustynuts34 too?
I hope you have MSN, Yahoo!, gTalk, or meet on IRC (MSN preferably) so we can discuss faster once I start with porting (that should be in next few days)
blagus said:
Thanks a lot
So, I can count on rustynuts34 too?
Click to expand...
Click to collapse
Would love too but need my phone all day, im more of a night time Rom flasher lol I know nothing of devving or linux would not know where to start. But wish you guys all the luck in the world with it sorry I wont be able to help much :-(
Sent from my LT15i using Tapatalk
blagus said:
Thanks a lot
So, I can count on rustynuts34 too?
I hope you have MSN, Yahoo!, gTalk, or meet on IRC (MSN preferably) so we can discuss faster once I start with porting (that should be in next few days)
Click to expand...
Click to collapse
I added you on MSN.
Count me in

[Q] MB886-4.1.1中文完美ROOT底包.rar

anybody know what this is MB886-4.1.1中文完美ROOT底包.rar
A hope!
What is it? Any links?
Sent from my DROID BIONIC using Tapatalk 2
I am guessing is Chinese i used google translator and it translates to this The MB886-4.1.1 the perfect Chinese ROOT bottom package. Rar
Sent from my MB886 using xda premium
I looked around and saw that too, but because I have no idea whos who in the Chinese hacking world I have no idea how safe or good that .rar is...
Sound like a brick lol.
Sent from my MotoAHD Maxx
http://bbs.gfan.com/android-5675929-1-1.html
This is aparently a method to roll back the AHD on ATT to 4.0.4
Says something about using QPST.
I have no experience so im posting this and waiting till someone who understands it more can comment.
Well hopefully our great devs find a root for JB
Sent from my MB886 using xda premium
DON'T FLASH IT!!!
This is most likely the Asian version and WILL BRICK YOUR PHONE!!!.
In case you haven't heard of me, I've been helping a lot around the Atrix 2 community. Then when i bricked it, at&t ran out of Atrix 2s and gave me and Atrix HD instead. Since then, I've been hiding in the shadows so I won't look like a n00b.
I'll take a look at this.
until then...
DON'T FLASH IT!!!
Check out that link I posted.
That looked very helpful. We just need someone with experience to make sure it could/does work.
TTLayland said:
Check out that link I posted.
That looked very helpful. We just need someone with experience to make sure it could/does work.
Click to expand...
Click to collapse
http://pan.baidu.com/share/link?shareid=178961&uk=2030448855
There is the link just press the white button that says "下载" and download.
DEVS ONLY!!!!!
Started the download but its crawling along even on 20mbps connection.
Im no Deve though. Still the link I posted is a downgrade for US ATT phones!
IF that really works then we are saved even if JB isnt rooted ever!
So check it out as well. It uses QPST to fix bricked phones from the translated english I could make out.
i tried it
I tried no brick but it wouldnt come out of fastboot. Flashed back to 4.1.1 because it wouldn't let me flash to ICS either.
What method did you try.
The root or the rollback?
IDK anything yet,
10 minutes remaining.
I cant find download link
Sent from my MB886 using xda premium
tcf38012 said:
DON'T FLASH IT!!!
This is most likely the Asian version and WILL BRICK YOUR PHONE!!!.
In case you haven't heard of me, I've been helping a lot around the Atrix 2 community. Then when i bricked it, at&t ran out of Atrix 2s and gave me and Atrix HD instead. Since then, I've been hiding in the shadows so I won't look like a n00b.
I'll take a look at this.
until then...
DON'T FLASH IT!!!
Click to expand...
Click to collapse
Any news?
Not to sound pushy or anything but I'm really interested in this whole concept
Sent from my MB886 using xda app-developers app
don't work.
only dev edition
marshok said:
don't work.
only dev edition
Click to expand...
Click to collapse
In China they sell them with unlocked bootloaders out of the box, don't even have to unlock them lol
So what's that mean for us Matt? While you LOL we wait anxiously for any hope of root.
Kinda figures the chinese hackers would be better than us
Since no one brought this up. This is form the chinese forum specificaly for ATT phones and rolling back.
We have to be able to get something from this. Here is the translated forum post and thread link.
http://bbs.gfan.com/android-5675929-1-1.html
Thread Title Translates into "[Experience] 4.1 downgrade to 4 and then root then OTA upgrade to 4.1 and then delete the at&t official app"
From the forums found this address http://item.taobao.com/item.htm?spm=a1z09.5.0.40.sdQ42d&id=15839118382 Taobao bought mb886
Hand of machine comparison simple, no packaging box, no headset, no HDMI line (does not clearly full of should is what sample), only machine, and line and charger, Hou cover see with somewhat rough, words see does not Qing (just carefully see has see, original is has layer film, tore has lot has), however I is doesn't matter, 1500 Yuan, buy this machine of principles originally is enough on line, on figure a CrystalTalk.
Hand machine is 4.1.1 Chinese, no locked bootloader, you have root, Forum of Chinese-speaking fees, useful original and I try not to toss the habit
http://sbf.droid-developers.org/dinara/list.php
4.1.1 under firmware, installed the pre-release driver according to RSD brush machine for tutorials in the forums.
All the best, starting with a long time feels good, but too many app at&t too tired, and would also like to buy things with market unlocker (because they do the Internet for many years, never trusting any app store in the country, even before the official market is entering into the definition, 4 well after some), there is the root idea.
Forums and XDA-pass, and found that we cannot root, downgrading is dangerous, but don't see a post saying who try to downgrade the bricks.
Worked, we said that it would lose IMEI, use QPST out IMEI spare.
Then download from the above address 7.7.1Q-144_MB886_MR1-22_SIGNED_CFC.xml.zip (also need to modify the XML file, remove the GetVar two lines),
After the wipe (can be a feeling, first wipe wipe cache has been contained), RSD flush, when brush is also very worried about bricks, but smoothly brushed inside, after the restart, settings, found that IMEI in, not lose it? Also use QPST and search a bit, 550.
Opens the developer options the first use debug and unknown sources of security, from: http://Forum.xda-developers.com/showthread.php?t=1940594 motofail2go_ Windows.zip, implementation extracted run.bat, follow the prompts to root successfully, and then go to play store updated superuser, updated into superuser update Su
And then go to play Voodoo store installed OTA rootkeeper, or you can download from its official, http://DL.project-Voodoo.org/apps/, after install, backup root, and then UN-root, and then restore against each, several times, confirm no problem.
Enter the settings of the system update, start the download update package, download fast, faster than play app store synchronization, waited until all the app is installed, system update again to begin the update the update succeeds, IMEI (wrong ... ... ), But discovered that 4.0.4 with real racing2 does not know how ... ...
Deletion of official procedures,
AABSync.apk
All begin with ATT. APK
CityID.apk
CodeScanner.apk
DigitalLocker.apk
Facebook.apk (Kung Fu network can not be used)
FamilyMap.apk
Kindle.apk (K4 and KT)
myATT.apk
Navigator.apk
SmartWifi.apk
Swype.apk
UVerse.apk
YelloPage.apk
YPCom.apk
And corresponds to the odex files, some of these files in/system/app, in/system/vendor/app, by deleting out wipe the cache (note that only wipe cache)
Delete method is to use ES File Manager manually to a directory with the TF card, XDA people recommend Titanium Backup, I haven't tried, there are free versions of both of these play store.
Circles I had, the small circle to the right of the display can be a battery, did not find major problems currently in use, there is less of an issue People are following a fall in a YP, a collapse at app, XDA people to machine YP-free version, I didn't pay attention to the MB886 is there, anyway, is the ~
Final column is used to document mentioned above some of the app was downloaded directly from the play store
Firmware file:
7.7.1Q-144_MB886_MR1-22_SIGNED_CFC.xml.zip
MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip
motofail2go_windows.zip
http://vulnfactory.org/public/motofail2go_windows.zip
RSDLite6.1.4.msi
Motorola_PreRelease_Mobile_Drivers_5.9.1_32bit.msi
http://forum.xda-developers.com/showthread.php?t=1891582
QPST.2.7.378.msi
http://forum.xda-developers.com/showthread.php?t=1801997
VoodooOTARootKeeper.apk http://dl.project-voodoo.org/apps/VoodooOTARootKeeper.apk
Firmware file in addition to a package, not enough, drop in Baidu's Web site, http://pan.Baidu.com/share/link?shareid=236789&UK=889233909
Finally finally, I'm not sure whether all of the lock-free MB886 can do, even not all buy from Taobao shop can do so well.
Click to expand...
Click to collapse

First custom 5.1.1 ROM released by Booroondook!

Mod edit: link removed (4pda links not allowed)
Booroondook has first done FUSE ROM and now there is he again... Bravo! Many, many improvements and fixes. Sorry he is not paying attention to XDA (doing all really for free, not for donations here) but he deserves all credits.
Full Post translation and download link
Here is the full post with download link, please donate to the dev if you like his work.
The firmware is designed as a "designer" under both options screen resolutions (800x480 and 1024x600). Everyone can afford to assemble his own version. How to assemble the firmware is described in detail here:
The order of assembly of the firmware
The firmware is available as a set designer or "do it yourself" - as anyone this thing called - and is a set of modules for self-assembly of the finished image of the firmware. The assembly is made on a computer running Windows (versions from XP and higher).
How to assemble:
1) Download the archive unpack into any empty folder on your computer (the full path to the folder does not contain spaces, non-Latin characters, punctuation marks and special characters, so not recommended for unpacking on the desktop, in the "My Documents", etc. )
2) turn in this same folder
3) Run start_rus.bat file (or start_eng.bat, if you are dearer to the English interface)
4) you will be asked to choose a processor. Only two options - RK3066 and RK3188. The selection is made by entering the numbers specified opposite processor type, and then pressing the Enter key
5) The following sentence - to select the screen resolution. Options are also two - 800x480 and 1024x600. The selection is made in the same manner as in the previous paragraph
6) After this, the firmware build process, which takes less than 10 seconds.
7) The result of the process - file update_ <vash_protsessor> _ <vashe_razreshenie> .img, which, after renaming update.img you can sew in a familiar way radio When you first start after flashing is (as usual in my firmware) conducted preset application and then fit /system/build.prop configuration file under the processor type and resolution (800x480 for the recorder will be installed screen density of 160 to 1024x600 - 240). Then reboot, after which the tape recorder will be completely ready for operation.
Features flashing process. Due to the fact that changing breakdown flash memory sections (including as compared with previously released on FUSE-firmware Android 4.4.4), the process can be performed in two stages, both stages are the same.
That is, you normally install firmware mode rekaveri (thus necessarily choosing the option with full data cleaning). The device is rebooted and ... hang on animated screensaver. If you want to wait, wait - but the result is not guaranteed. If you do not want to wait, press the RESET, then (without releasing RESET'a) - POWER. Without releasing the POWER, release the RESET, waiting 3 seconds and release POWER. All - a few seconds later we are back in rekaveri mode where once again just repeat the flashing process - again, choose the menu item, involves the installation of firmware and data cleaning, and ... forward. After the second cassette recorder firmware to be released to the operating mode (although longer than usual, as is the formation of the primary file system).
Option: instead of the second flashing, you can try to select a lower menu item - "clean and reset to factory condition."
As you understand, all your data will be lost after flashing, so advance reservations and they do not say I did not warn.
Attention!!! Those who do not have the RESET button and mechanical buttons. Before flashing be sure to ask if you can overload the radio in rekaveri mode from the "hung" or off state. If this method is not, then you better not reflash.
OTA-upgrade
The firmware is the possibility of prompt automatic updates. OTA (Over the Air - "air") or FOTA (Firmware Over the Air) - a technology that allows to (semi-) automatically obtain and install the update packages. User Intervention here minimum - it is only necessary to press the button, confirming compliance with the installation. Well, there is still a button manually check for updates. And all the rest State makes self - sends a request to the server, downloads the update package, checks it for validity (verifies the certificate used to sign the update package with a key available in the firmware), reloads the State in rekaveri mode where automatically launches the update process, and finally PG reboots to the operating mode.
Naturally, for the possibility of State OTA-update should have a working Internet connection. Automatic prompting to check for updates are sent automatically after every download SI operating mode and communication with the Internet. If desired, you can request a renewal of the "out of order" by pressing the appropriate button in the dialog "Settings" - "About your device" - "OTA update system." Another essential requirement to enable OTA updates - is the availability of free space on the "GPS-card" (/ mnt / external_sd), and (of course) the availability and serviceability of the card itself. In case of problems with the card update can be downloaded to start, but then will be a network error. Available space on the card must be two times larger than the size of the update package. As practice shows, the usual pack "weighing" of up to 20 MB. Although there are cases of 55-MB blocks. In general, if you keep on the card 120 MB of free space, the problems you should not be.
Cancellation OTA update? Unfortunately, a simple interactive option is not provided. But you can do the following: Open the file for editing /system/build.prop. Find it (towards the end of the file) option ro.product.ota.host = www.booroondook.ru: 2300. Replace the URL-address of the update server (www.booroondook.ru:2300) to something "obscene". For example, suppose that this line will look like this: ro.product.ota.host = localhost. Save the file, restart the SU. Everything - Updates you will not torture any more.
Disclaimer: The self-fulfilling complicated technical procedure for flashing the device, you will definitely take full responsibility for possible negative consequences up to the irrevocable failure of your head unit.
Version - from 06/03/2016
Link to the firmware (made on the basis of KLD-20160511): https://mega.nz/#!XFZUQKAI!H2L7gsRIuVn1D7x7slQjE_XclmVP6RWXRp-VRmc5-uU
Innovations regarding the factory options:
- Cloning a resolution of 800x480 by kernel patch (kernel.img)
- Completely redesigned Russian translation
- Root access running SuperSU
- 5 launcher to choose from ( "Settings" - "Desktop")
- 4 options "Bluetooth" application ( "Telephone"), 5 application options, "Music" and "Radio". Alternative applications are installed through the "OEM" application, return to the original (nominal) version - after the usual removal of the application settings ( "Uninstall updates")
- In settings Added "For Developers", "Screen" - "Font size" and "Display" - "Display Density"
- In settings added to the monitoring data
- OTA-update functionality
- Added missing "OEM" applications, "Weather", "DVR" (Annex "Weather" - in the version revised respected vitarkananda)
- Added widgets "Weather", "Music", "Telephone", "Video" and "Navigation", ported from the firmware for MTCD
- Partition "OEM" is increased to 384 MB. This section can be used, for example, as a "warehouse" APK-relevant distributions
- Built-in support for working with trip computer Multitronics MPC-800 (Bluetooth-name DUAL-SPP)
Attention:
1) please do not ask questions why this firmware does not work Xposed. The answer is - it does not work and on the drive firmware, and generally have Xposed big problem with Android 5 (or higher). When someone finds a way to get to work on our Xposed firmware, in principle, I immediately implement it in its firmware.
2) Management of screensaver (MTCScreenClock.apk) is only possible through /system/build.prop File Edit (parameters ro.product.screenclock = true | false and ro.product.screentimeout = 5 | 10 | 15 | 20 | 30 | 60 ). Interactive control timeout in the factory firmware is not provided, and I realize it too failed.
Note: Because an application "Weather" uses a revised version of vitarkananda, the new version of the application (as they become available) can be installed instead of the usual simple by replacing labor-intensive system file.
For developers, the public certificate signed APK following: MTCBlueTooth.apk, MTCMusic.apk, MTCRadio.apk, MTCScreenClock.apk. This means that signing their "swing" application to the same certificate (and increasing code version), you can give users the ability to easily install your development instead of forcing them to carry out the replacement of system files with setting permissions.
https://mega.nz/#!XFZUQKAI!H2L7gsRIuVn1D7x7slQjE_XclmVP6RWXRp-VRmc5-uU
[size=+1]Thread cleaned.
Keep the drama out of the public forum. If you're not a moderator you have no place telling other members how to post, no matter which side of the argument you're on, use the report feature and let us deal with it. If you have a problem with a certain member/developer do not create drama in the public forum, again, use the report feature. If it isn't a reportable offence then just leave it alone or take it elsewhere. If you believe there is a developer that is stealing someone's work and/or not giving credit, you guessed it... use the report feature. See the theme here? XDA isn't the place for your petty squabbling, if you have a valid case to argue then take the right approach and call on the moderation team. And I'll repeat, keep this drama out of the public forum. This goes for both of you.[/size]
Heisenberg said:
[size=+1]Thread cleaned.
Keep the drama out of the public forum. If you're not a moderator you have no place telling other members how to post, no matter which side of the argument you're on, use the report feature and let us deal with it. If you have a problem with a certain member/developer do not create drama in the public forum, again, use the report feature. If it isn't a reportable offence then just leave it alone or take it elsewhere. If you believe there is a developer that is stealing someone's work and/or not giving credit, you guessed it... use the report feature. See the theme here? XDA isn't the place for your petty squabbling, if you have a valid case to argue then take the right approach and call on the moderation team. And I'll repeat, keep this drama out of the public forum. This goes for both of you.[/size]
Click to expand...
Click to collapse
Your "cleaning" means no one has a clue what on earth has gone on and what all the "drama" was, as there appears to be just 2 posts left, one a quote from booroondook on xda.
It would probably be best if you removed the text from your post, or simply put "Moderator cleaned thread" or something, - currently your post confuses everyone as youve removed text and/or posts, so no one knows what you are talking about.
Since when are 4pda.ru links not allowed ? I have used them and seen them used many times over the past 2 years, or is that just referring to their use in thread titles ?
typos1 said:
Your "cleaning" means no one has a clue what on earth has gone on and what all the "drama" was, as there appears to be just 2 posts left, one a quote from booroondook on xda. If you'd like to become a moderator please feel free to make an application but until then please leave it to us. If you'd like to become a moderator feel free to make an application but until then please leave it to us. If you'd like to become a moderator feel free to make an application but until then please leave it to us.
It would probably be best if you removed the text from your post, or simply put "Moderator cleaned thread" or something, - currently your post confuses everyone as youve removed text and/or posts, so no one knows what you are talking about.
Since when are 4pda.ru links not allowed ? I have used them and seen them used many times over the past 2 years, or is that just referring to their use in thread titles ?
Click to expand...
Click to collapse
You're not meant to have a clue what's going on, that's the entire point of cleaning a thread, to remove inappropriate posts so they cannot be seen. I'm not sure why this even matters to you, you weren't involved, it isn't your business, and this thread is now back to its original purpose. Thanks for your input, but no, I won't be editing my message, it was left for a reason.
4pda links aren't allowed on XDA and haven't been for quite some time. If you are using them I suggest you stop because it could affect you negatively. We can't get to every link on this site, we act on reports made by our members, when we receive a report about disallowed links (or stumble across them) they are removed.
If you'd like to become a moderator feel free to make an application but until then please leave it to us, thanks.
Heisenberg said:
You're not meant to have a clue what's going on, that's the entire point of cleaning a thread, to remove inappropriate posts so they cannot be seen. I'm not sure why this even matters to you, you weren't involved, it isn't your business, and this thread is now back to its original purpose. Thanks for your input, but no, I won't be editing my message, it was left for a reason.
4pda links aren't allowed on XDA and haven't been for quite some time. If you are using them I suggest you stop because it could affect you negatively. We can't get to every link on this site, we act on reports made by our members, when we receive a report about disallowed links (or stumble across them) they are removed.
If you'd like to become a moderator feel free to make an application but until then please leave it to us, thanks.
Click to expand...
Click to collapse
Why 4pda links are not allowed? Where we can find list of prohibited sites?
pa.ko said:
Why 4pda links are not allowed? Where we can find list of prohibited sites?
Click to expand...
Click to collapse
The main reason is because 4pda is rife with piracy, warez, and there are major issues with GPL compliance on that site. You're also not meant to direct members to competing forums.
Thanks for explanation. True. But they also have original work like this...
pa.ko said:
Thanks for explanation. True. But they also have original work like this...
Click to expand...
Click to collapse
There is no way for you or I to know if that work is actually original. 4pda is notorious for kanging. On the surface it looks like original work but no way to prove that. This is beside the point though; 4pda is blacklisted for all of the rotten crap that takes place there, it's that crap that pulls down any original work that might be posted.
tried...not working
went to build for rk3066 pressed 1 then enter got error message..."sorry RK3066 CPU does not support in this firmware" just thought i would let others know
WECoyote633 said:
went to build for rk3066 pressed 1 then enter got error message..."sorry RK3066 CPU does not support in this firmware" just thought i would let others know
Click to expand...
Click to collapse
Your a dev and youre trying to make a RK3066 ROM ? Or youve just tried to install it on an RK3066 unit ?
typos1 said:
Your a dev and youre trying to make a RK3066 ROM ? Or youve just tried to install it on an RK3066 unit ?
Click to expand...
Click to collapse
not a developer...followed instructions in first post got error with the first step
WECoyote633 said:
not a developer...followed instructions in first post got error with the first step
Click to expand...
Click to collapse
This ROM is not compatible with 3066.
The build.bat is from a previous version.
miffymiffy said:
This ROM is not compatible with 3066.
The build.bat is from a previous version.
Click to expand...
Click to collapse
thx for info..that being the case this info might be mentioned in the first post....and the diy package perhaps shouldn't give the option to choose between the 3066 and the 3188..will continue to wait for a possible rk3066 version of 5.1.1....thx again
WECoyote633 said:
thx for info..that being the case this info might be mentioned in the first post....and the diy package perhaps shouldn't give the option to choose between the 3066 and the 3188..will continue to wait for a possible rk3066 version of 5.1.1....thx again
Click to expand...
Click to collapse
It is mentioned in the Lollipop thread and I think the original thread for booroondook's ROM, which is still open, this thread is kinda superfluous really.
I have a screen for avelo toyota
Puild number rk3188-eng4.4.4 310 ....
Android 4.4.4
MCU version
Mtcb-ksp-v2.86
I would like to update it to 5.1
Is the a suitable version for me ? Because most of the versions i found are mtcb-kdl
Is this version ok with me.? Does it effect my screen ?
---------- Post added at 04:22 AM ---------- Previous post was at 04:21 AM ----------
My problem is my device is 4.4.4 I would like to update to 5.1.1 and my device type is mtcb ksp
I didn't find an update please tell me how to update it
mr-mo7ammad said:
I have a screen for avelo toyota
Puild number rk3188-eng4.4.4 310 ....
Android 4.4.4
MCU version
Mtcb-ksp-v2.86
I would like to update it to 5.1
Is the a suitable version for me ? Because most of the versions i found are mtcb-kdl
Is this version ok with me.? Does it effect my screen ?
---------- Post added at 04:22 AM ---------- Previous post was at 04:21 AM ----------
My problem is my device is 4.4.4 I would like to update to 5.1.1 and my device type is mtcb ksp
I didn't find an update please tell me how to update it
Click to expand...
Click to collapse
Answered 10 times already!
MCU is not important, you already have MTCB unit so you can flash MTCB roms (4.4.4. or 5.1.1.)
you are probably afraid because of ksp-v2.86, that does not matter so you can flash any MTCB based rom.
mr-mo7ammad said:
I have a screen for avelo toyota
Puild number rk3188-eng4.4.4 310 ....
Android 4.4.4
MCU version
Mtcb-ksp-v2.86
I would like to update it to 5.1
Is the a suitable version for me ? Because most of the versions i found are mtcb-kdl
Is this version ok with me.? Does it effect my screen ?
---------- Post added at 04:22 AM ---------- Previous post was at 04:21 AM ----------
My problem is my device is 4.4.4 I would like to update to 5.1.1 and my device type is mtcb ksp
I didn't find an update please tell me how to update it
Click to expand...
Click to collapse
Would probably be a good idea if you read the wiki before posting.
Does anyone know how modifing exception apks for MTCScreenClock? After I modified Build.prop to activate the Screenclock, it only works when radio apk, music apk,... are working and I'd like it works always except when I'm using GPS navigator.
By the other hand, I'd like to change transparent background for MTCScreenclock and I know that the installed MTCScreeclock.apk is not the issue because I used the same and it wasn't transparent in KitKat versions. Thank you
I have got installed in my headunit last LP version of DSA (5.1.1.).

Finding P40 Pro firmware

Been researching for ages now, made a good few mistakes, had gms services installed all smooth sailing, manually updated with hisuite and team mt to 10.0.1.175 but I've stuffed up now.
I went hunting for a firmware version to restore Ota updates and have spiraled down a deep dark rabbit hole.
Self inflicted issue I flashed Emui 10.0.1.154 from reading threads in hopes of regaining Ota updates but obviously wiped all the data (silly me made no backups) and now need to reinstall googlefier but I'm unable to with the firmware version being too high up.
Now begins the major issue I'm stuck at 10.0.154 and I can't find firmware anywhere as team mt online firmware finder is currently bringing back errors both through apk and online, I saw a thread somewhere about Huawei moving databases or something like that.
I have found some other sites like huaweidl but the firmwares hosted are incompatible
I have a Els-NX9
Build is (185E9R4P1)
Region is clearly C185
I've typically searched for ELS-LGRP4 firmwares as the results often were favorable.
Currently I can't find firmware to match closest I've gotten is (C432) firmwares which is probably why Ota updates stopped working in the first place.
At this point I don't care about emui 11 or updates anymore I just want gms and gapps back I'm losing my mind can anyone assist?
Tristen_luke said:
Been researching for ages now, made a good few mistakes, had gms services installed all smooth sailing, manually updated with hisuite and team mt to 10.0.1.175 but I've stuffed up now.
I went hunting for a firmware version to restore Ota updates and have spiraled down a deep dark rabbit hole.
Self inflicted issue I flashed Emui 10.0.1.154 from reading threads in hopes of regaining Ota updates but obviously wiped all the data (silly me made no backups) and now need to reinstall googlefier but I'm unable to with the firmware version being too high up.
Now begins the major issue I'm stuck at 10.0.154 and I can't find firmware anywhere as team mt online firmware finder is currently bringing back errors both through apk and online, I saw a thread somewhere about Huawei moving databases or something like that.
I have found some other sites like huaweidl but the firmwares hosted are incompatible
I have a Els-NX9
Build is (185E9R4P1)
Region is clearly C185
I've typically searched for ELS-LGRP4 firmwares as the results often were favorable.
Currently I can't find firmware to match closest I've gotten is (C432) firmwares which is probably why Ota updates stopped working in the first place.
At this point I don't care about emui 11 or updates anymore I just want gms and gapps back I'm losing my mind can anyone assist?
Click to expand...
Click to collapse
Welcome to XDA!
Please help us to keep our forum neat!, do not double post threads, read the rules and more importantly, enjoy!
orb3000 said:
Welcome to XDA!
Please help us to keep our forum neat!, do not double post threads, read the rules and more importantly, enjoy!
Click to expand...
Click to collapse
Thank you, double post was a mistake, my apologies. I've hunted for a delete option but could not find one, but I appreciate the welcome. I have also done my best to understand the rules and will do my best to abide by the.
Tristen_luke said:
Thank you, double post was a mistake, my apologies. I've hunted for a delete option but could not find one, but I appreciate the welcome. I have also done my best to understand the rules and will do my best to abide by the.
Click to expand...
Click to collapse
my firmware repository
HiDrive
my.hidrive.com
starbase64 said:
my firmware repository
HiDrive
my.hidrive.com
Click to expand...
Click to collapse
amazing, you're a champ, thank you! I'm going to give the file (Huawei_P40_Pro_Elsa-N29D 10.1.0.131(C185E9R4P1)_Firmware_EMUI10.1.0_05016PVQ.zip) a goI.
'm still struggling to wrap my mind around phone models. The build number matches perfectly but not the model number. phone says NX9 whereas the package says N29D, are there any threads I can read on this, would love to learn more
Tristen_luke said:
amazing, you're a champ, thank you! I'm going to give the file (Huawei_P40_Pro_Elsa-N29D 10.1.0.131(C185E9R4P1)_Firmware_EMUI10.1.0_05016PVQ.zip) a goI.
'm still struggling to wrap my mind around phone models. The build number matches perfectly but not the model number. phone says NX9 whereas the package says N29D, are there any threads I can read on this, would love to learn more
Click to expand...
Click to collapse
Just an update @starbase64 thank you for the firmware, what a treat both my issues solved tonight after many a late night of searching and reading. I have both Gms now and Emui 11 through Ota updates.
Just to provide my method to other readers,
I downloaded the aforementioned firmware version for my build. Extracted it to a USB thumbdrive making sure the dload folder was at the root of the drive. And then used the otg method to flash the firmware.
@Bender007 also want to say thanks for the amazing googlefier app, both times now it was super easy to work with.
Tristen_luke said:
Just an update @starbase64 thank you for the firmware, what a treat both my issues solved tonight after many a late night of searching and reading. I have both Gms now and Emui 11 through Ota updates.
Just to provide my method to other readers,
I downloaded the aforementioned firmware version for my build. Extracted it to a USB thumbdrive making sure the dload folder was at the root of the drive. And then used the otg method to flash the firmware.
@Bender007 also want to say thanks for the amazing googlefier app, both times now it was super easy to work with.
Click to expand...
Click to collapse
Thank you for starting this thread and thanks to @starbase64 for the repository. Appreciate it

Categories

Resources