I have a stock AT&T Nexus One updated to FRF85B. I am from the US, but the Market doesn't show the paid apps. I wanted to quickroot the phone to install Market Enabler so the paid apps are available.
1. The issue is if I use quickroot on the phone, does that mean I can never go back to a stock ROM? I am confused because the quckroot for the stock AT&T Nx1 says its not a ROM re-write, just a patch.
2. Will I no longer receive updates via OTA from Google because of this?
3. Will there be additional bugs because I flashed my ROM using the quickroot method.
4. There are 2 options for Quickroot, what is the difference what is best?
5. Has anyone tried the Market Enabler program and what are your opinions?
Thanks you,
Mark Stachowski
If I were you, I'd check why the paid apps don't show first, before considering rooting. You're doing it for the wrong reasons.
The answers to almost all of your questions are in the 2 "sticky" rooting threads in Development section. Please don't be lazy, read them. And read "android 101" thread.
3. Bugs are property of ROMs that you flash, and aren't connected to rooting in any way.
5. Market Enabler works. What opinions can one have of a program that just does what it says?
Sorry I forgot to mention I am an American guy living in Saudi Arabia, it doesn't work because of that.
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.).
Hi,
I'm new to "creating android apps" and i'm looking for the following:
I'm in the proces of making an simple app, but when there is a new version of the app i would like to notify the people who use it.
The app will not be put in the Playstore so the new version would be downloaden (by the app?) from my webserver
So:
If and how is it possible to notify users and let them download a new version off the app that is not in the Playstore but on my webserver.
Does anyone have a tutorial or something for me that i can follow? :angel:
Thanks in advance!
ericosman said:
Hi,
I'm new to "creating android apps" and i'm looking for the following:
I'm in the proces of making an simple app, but when there is a new version of the app i would like to notify the people who use it.
The app will not be put in the Playstore so the new version would be downloaden (by the app?) from my webserver
So:
If and how is it possible to notify users and let them download a new version off the app that is not in the Playstore but on my webserver.
Does anyone have a tutorial or something for me that i can follow? :angel:
Thanks in advance!
Click to expand...
Click to collapse
Hello, you can google when you dont know something.
I found your answer in 4 seconds
https://stackoverflow.com/questions/9849889/how-to-notifiy-users-about-an-android-app-update
If i helped you please press the Thanks button
ericosman said:
Hi,
I'm new to "creating android apps" and i'm looking for the following:
I'm in the proces of making an simple app, but when there is a new version of the app i would like to notify the people who use it.
The app will not be put in the Playstore so the new version would be downloaden (by the app?) from my webserver
So:
If and how is it possible to notify users and let them download a new version off the app that is not in the Playstore but on my webserver.
Does anyone have a tutorial or something for me that i can follow? :angel:
Thanks in advance!
Click to expand...
Click to collapse
Since you have a webserver, you can have a simple JSON there, with the details of the new app like the version code, name etc. Once the app opens you can query for the JSON from the web-server and can check if the version code is higher, if yes, you display the message to update the app.
Another way is to use Cloud notification system like firebase etc.