Related
Coming soon: Full access to the 2.x market.
Progress is being made to bring the new market to the NC (less the FC permissions or APK signature issues.) Check posts towards the end of this thread for more info.
UPDATE - Version 1.1a - 4/27 - NOW WITH MORE ROOT!
I'm happy to announce that I now have a much improved version of apk-enabler all packaged up and ready to install. This version will work much better than the last one, and should provide much better application compatibility.
Version 1.1a:
Major update...
* Added Edify code to clean up old versions before installing or re-installing (either version)
* Updated su (version 2.3.6.1 - thanks dascud)
* Updated and relocated Superuser.apk (now lives in /data/app so updates will not complian about it being a "system application" anymore.)
* Added Zeam 2.9.2 to /data/app
* Added NookColorTools to /data/app
* Added SoftKeys 3.06 to /data/app (in case anyone needs this - some apps don't display the nook status bar properly.)
* Added latest busybox binary to /system/bin
* Added a crapload of symlinks to busybox functions in /system/xbin. Almost everything works now (grep, mount, etc) without having to run through busybox or toolbox. (thanks RileyGrant)
* I have attempted to perma-enable adb by setting the adb_enabled value in /data/data/com.android.providers.settings/databases/settings.db. Unfortunately it appears that this setting is ignored - at least when auto mounting is enabled. See notes below.
Notes:
Now that we have busybox and a current version of su, we now have what resembles a "normal" android shell environment. More apps should work with the updates, and we can now get a shell (then su) via adb. You can also run the Android Termainl app and su from there.
Also, since Zeam and SoftKeys now baked in, the first boot will now ask for your preference of default launchers (Home, SoftKeys, or Zeam.)
To get ADB working, you need to update your drivers, and play with settings in NookColorTools (development section) to enable USB debugging.
I have validated this install via a fresh install and over-top of existing installs. The only requirement is that the Nook has been turned on and registered. You can flash this over older versions, the script cleans up cruft from prior runs before installation.
Original Post:
So I went about fooling around with the stock 1.2 ROM, and like many I was frustrated by the lack of certain apps in the Nook app store. So here's a little work-around until we get a properly rooted solution in place:
What this hack does:
* Updates the SQLite Settings Database (data/data/com.android.providers.settings/databases/settings.db) with a hacked version, enabling the install_non_market_apps and adb_enabled settings.
* Installs a version of "su" in /bin and /xbin.
* Installs busybox to /system/bin and sets symlinks for most shell commands in /system/xbin
* Installs SuperUser.apk, SoftKeys_3.06.apk, NookColorTools_0.2.apk, and zeam-2.9.2.apk to /data/app (you may uninstall any of these if you wish.)
* With these in place, the stock browser (and other Market apps) are fully capable of downloading, launching, and installing .apk files of your choosing.
Is this safe? What if I brick my Nook?
The Nook Color bootloader will boot anything you throw at it. There are no signature checks anywhere, and even their own code is signed using test keys. If you get a bad flash or whatever, you can always boot your Clockwork SD card and restore from there. Remember - this is not a phone - there is no subsidy or baseband to protect. So, no there's no S-ON, locked boot loader, or any of that other silly crap the carriers do to screw their customers. You can flash forwards, backwards, sideways, whatever you want, as long as you can put it on an SD card.
Overall, this is no more dangerous than running a stock android device with the "Unknown Sources" setting enabled. Nothing is happening yet that is uncharacteristic of a "standard", vanilla android device.
That said, you should probably make a backup while you are running Clockwork, just to be on the extra-safe-side.
So, is this a full ROM that I can use to flash the 1.2 update?
No. This is a stand-alone update to 1.2 that overwrites one file and adds two others. You need to have 1.2 up and running in order to use this.
How to install...
First, you must have a microSD card already flashed with ClockworkMod. I'm not getting into that, you can find a good guide in this post:
http://forum.xda-developers.com/showthread.php?t=987735
(thanks fpga_guy)
NOTE - THIS WILL ERASE YOUR SD CARD - SO YOU MIGHT WANT TO PICK UP A CHEAP 2GB CARD FOR THIS.
* Once you have Clockwork set up, drop the attached zip in the root directory, and reboot your Nook Color. Once Clockwork is booted:
* Select "install zip from sdcard", then "choose zip from sdcard"
* Select "Yes - Install apk-enabler-1-1a-signed.zip". The install process will begin promptly.
* Once flashed, you will be prompted to Reboot,
* The Nook OS will almost certainly crash on the first reboot - I'm not sure why as of yet... If it does, hold the power button until the Nook powers off completely, then turn it back on. It should continue to boot normally after this point.
* Once you are back up, you can use the browser to download and run .APK files from anywhere. Some apps do not work, others do. Fortunately for us, Superuser.apk is one that does
As for launchers, you will not see your installed apps in the Extras area of the stock launcher - B&N is doing something shady here... Instead, you will need to install another Launcher. Zeam seems to work well, while ADW doesn't.
Once Zeam is installed, you can hit the "Home" button and select it as your Launcher (permanantly, if you like...) This is where you'll see all of your downloaded apps.
I have attached the flashable zip file, plus links to SuperUser.apk and Zeam. Use the built-in Nook browser to install both of these to your device. Once you download an APK file, tap the notificaiton in the lower left corner and select "Package Installer." The usual Android install screen will appear, and you know what to do from there...
What's not working?
Probably lots of things. I know ADW doesn't work, and the open source Terminal emulator doesn't either... Superuser.apk detects SU, which is a good thing. It isn't "full root access" until I hack /etc/fstab to mount /system r/w (probably tomorrow.) B&N hacked up the frameworks pretty bad for this, so there are probably lots of issues with non-market apps. However, this should open the door to someone willing to port Nookie Froyo (or something similar) over to the stock 1.2 ROM.
Credit where credit is due:
First, thanks to everyone on XDA, the official Nook forum, CyanogenMod, NookDevs, some kind folks on IRC who helped me sort out the partition layout, some helpful folks in this thread, and probably 20 others that I'm forgetting. This would not have been possible without your help.
Where do we go from here?
I suspect we will have something more like Autonooter in a day or so... However, this is a fully usable solution for the time being. You have su, busybox, Superuser, SoftKeys, and a Launcher.
Also, someone needs to look into getting side-loaded apps onto the home-screen and/or into the Extras screen. My fear is that B&N is checking signatures there - but hopefully I'm wrong on that one....
Version 1.1a: apk-enabler-1-1a-signed.zip (1.28mb)
md5sum: 65267cf3314d7fae829881970d70b444
http://www.mediafire.com/?bb7o66282bqfp6q
Apps known to work:
Superuser
Zeam
SoftKeys
Amazon App Store for Android (works beautifully)
Amazon Mobile
Collapse (today's free game on Amazon)
Kindle Reader
File Manager
ES file explorer
Pulse (with widgets)
Facebook
Evernote
Remember The Milk
Subsonic
WP Clock - Live Wallpapers are enabled by default - the Google Maps and WP Clock live wallpapers appear in the stock Nook Home settings
Free Dictionary
TV.com
TuneIn Radio
Winamp
LastPass
Xmarks
Dolphin
DocumentsToGo
cVolume
FancyWidget
Google Voice
ReadItLater
Button Savior
Dropbox
Adobe Reader
TerminalEmulator
Apps known not to work:
Any version of GApps. Especially those packaged for Gingerbread. This is a B&N issue.
ADWLauncher
aldiko (via kingsjack)
other Input Method (via kingsjack)
appmonster (via kingsjack)
gscript lite (via kingsjack)
GApps don't work because framework.jar needs to be ported from another release. B&N broke it.
Alternative keyboards and things like that will probably break (again, due to dependancies that have been broken by B&N.)
Fortunately, B&N left enough of the package installer intact to allow us to get this far.
(feel free to add to this list, I'll only test what I personally plan to use.)
Thanks for getting off market working
Sent from my SPH-M910 using XDA App
Zero to sixty in no time flat. Gracias Senor, now I can dual boot this and the incredibly speedy cm7 builds and have the best eReader on the market and a super great 7 inch tablet to boot.
can i use cm gapps-gb-20110307-signed in stock 1.2 after root?
kingsjack said:
can i use cm gapps-gb-20110307-signed in stock 1.2 after root?
Click to expand...
Click to collapse
No, that's the Gingerbread version. If you can find one for Froyo - who knows, it might just work
HamNCheese said:
No, that's the Gingerbread version. If you can find one for Froyo - who knows, it might just work
Click to expand...
Click to collapse
thank! now i cna install most apk in my nc.
but ... when i use root.explorer, i find superuser isn't work.. didn't root in my nc.
1. install apk.enabler.zip by ClockworkMod, is work. i can install apk by brower
2. install Superuser and zeam & rootexplorer, is work, and i can use rootexplorer to install other apk, but haven't root.
kingsjack said:
thank! now i cna install most apk in my nc.
but ... when i use root.explorer, i find superuser isn't work.. didn't root in my nc.
1. install apk.enabler.zip by ClockworkMod, is work. i can install apk by brower
2. install Superuser and zeam & rootexplorer, is work, and i can use rootexplorer to install other apk, but haven't root.
Click to expand...
Click to collapse
You're welcome. I'll look into Root Explorer - I'm not sure if it's a root issue or an issue with that software. Superuser thinks it has root, so I would think other apps would as well.
FYI /system is not mounted as read/write yet - perhaps that is what Root Explorer is complaining about?
HamNCheese said:
You're welcome. I'll look into Root Explorer - I'm not sure if it's a root issue or an issue with that software. Superuser thinks it has root, so I would think other apps would as well.
FYI /system is not mounted as read/write yet - perhaps that is what Root Explorer is complaining about?
Click to expand...
Click to collapse
without this Options
kingsjack said:
without this Options
Click to expand...
Click to collapse
Right. As I mentioned, I need to fix fstab to mount everything with read/write permissions (which I plan to do tomorrow.) This is really more of a work-around to get apps on the device. We will gain better control of it over time.
HamNCheese said:
Right. As I mentioned, I need to fix fstab to mount everything with read/write permissions (which I plan to do tomorrow.) This is really more of a work-around to get apps on the device. We will gain better control of it over time.
Click to expand...
Click to collapse
thank u work
I'm guessing, very much likely, that you didn't include a Superuser.apk into /system/app which allows Root Explorer to request use of su in xbin. I'm going to try and get an AN version going for 1.2 in a day or two.
GabrialDestruir said:
I'm guessing, very much likely, that you didn't include a Superuser.apk into /system/app which allows Root Explorer to request use of su in xbin. I'm going to try and get an AN version going for 1.2 in a day or two.
Click to expand...
Click to collapse
I didn't include it because it wasn't necessary. su is present, Superuser in apk form works. The only thing missing is to re-mount everything as rwxrwx---. That would satisfy the root explorer requirement without having to go the full autonooter route. For now, anwyay....
What you describe is simply a tweak to /etc/fsatb and possibly some changes here and there in some init scripts. It shouldn't be a difficult update, re-mounting file-systems isn't exactly the hardest thing to do in Linux.
The big headline here is "load apps from untrusted sources" - something that the Nook Color is physically incapable of doing out-of-the-box. In fact, their plan is exactly the opposite. Entangle the user with app purchases that they can't get anywhere else, and cannot transfer in or out of the Nook ecosystem. That problem is solved for now, and it should do what 90% of users want right out of the box.
We can discuss the next phase after evaluating the changes to frameworks and whatnot that will get Gapps and other crucial stuff up and running - that will prove to be a more difficult task than simply breaking in to the stock system. Judging by work that was done for previous iterations of Autonooter, there are enough framework changes that it's going to take some time to work out the details.
BTW, if anyone on that team would like to share information, please contact me and I'll see what I can do to help.
If there's no R/w toggle it means somethings wrong with Root Explorer, you should look into that problem as opposed to just fixing it by remounting system in init.rc this is not a good fix for something like this and shouldn't be acceptable. There's a reason the toggles built in and that's to help protect the /system folder.
GabrialDestruir said:
If there's no R/w toggle it means somethings wrong with Root Explorer, you should look into that problem as opposed to just fixing it by remounting system in init.rc this is not a good fix for something like this and shouldn't be acceptable. There's a reason the toggles built in and that's to help protect the /system folder.
Click to expand...
Click to collapse
Hmmmmm.....guess I'll have to spring for root explorer and dig through logcat to see what's going on. It could totally be some goofy B&N thing that's screwey on this one device. More after the break....
HamNCheese said:
Apps known to work:
Superuser
Zeam
Amazon App Store for Android (works beautifully)
Amazon Mobile
Collapse (today's free game on Amazon)
Kindle Reader
File Manager
Apps known not to work:
ADWLauncher
TerminalEmulator
(feel free to add to this list, I'll only test what I personally plan to use.)
Click to expand...
Click to collapse
Please explain how you got amazon appstore on there. I signed in on mazon had it send me the link on the nook to download it which i did. When i clicked on it brought up chice to run with app installer or package installer of which one gave me a parse error and the other did nothing.
Any ideas?
So, is this a full rom that I can flash my 1.1 nook into 1.2?
HamNCheese said:
BTW, if anyone on that team would like to share information, please contact me and I'll see what I can do to help.
Click to expand...
Click to collapse
Hint.. They already have in this thread.
HamNCheese said:
I didn't include it because it wasn't necessary. su is present, Superuser in apk form works. The only thing missing is to re-mount everything as rwxrwx---. That would satisfy the root explorer requirement without having to go the full autonooter route. For now, anwyay....[/B][/B][/I]
Click to expand...
Click to collapse
installing rom manager and running fix permissions should set all the right files to rwxrwx--- shouldnt it? i havent installed the update cuz im happy with cm7 so i cant test it..
Sent from my NookColor using Tapatalk
Good work Ham. The apps used to show after rebooting under the Extras section(Now called Apps), they are not now after the framework butchering they did. However, I installed Applanet and all I had to do was a search on the device and there it was. It launched fine and downloaded apps no issue.
FIRMWARE MEDIAPAD ICS 4.0.3 HWMOD C232B005
Kernel: 3.0.8 ([email protected]_server) Thu Jun 7 17:50:45 CST 2012
Compiler: (gcc version 4.4.3 (GCC)) #1 SMP PREEMPT
Baseband: 314007 - Android: 4.0.3 - GAPPS: 4.0.4
Incremental Build: V100R002C002B010SP030
This is a modified copy of the official firmware released by Huawei C232B005 General Version (June 2012). It doesn't require running "sanix" patches nor modifications to the system partitions "boot.img"/"system.img".
As in the original, the zip file contains instructions on how to upgrade from a MicroSD memory card. The firmware contains updated GAPPS ICS 4.0.4 (gapps-ics-20120429-signed.zip).
It has been said several time however you know you will void your warranty by modifying your device.
I have tried these modified firmware several times on my MediaPad before rendering them available.
On "Androidiani.com", in the MediaPad forum, I have been releasing these same kind of modifications for the following firmwares:
C232B002, C167B003, C170B008, C170B009 and currently C232B005
I have to say thanks to many users on that forum for their contributions and suggestions.
Before you start the upgrade
Download the firmware ZIP file, unpack the file on your PC and copy the "dload" folder found in the archive on the external MicroSD card. In the same archive you will also find Huawei original PDF document in English explaining how to upgrade the device and a "readme.txt" file that lists version numbers of the various components of the firmware (kernel, baseband, build etc.).
Remember to use Huawei's "All Backup" (suggested) or similar tools to backup all the applications and data on the external MicroSD card before proceeding with the update. In this firmware it is possible to activate a remote Google backup of the applications installed from the Market using a personal Google account ("Setting -> Backup and reset -> Backup account").
Standard update method
Only copy the "dload" folder in your MicroSD card, reset the device by switching the device off (press "power" button for 10 sec). If the device doesn't start automatically again press the power button. If the update does not start repeat the operation and additionally keep pressing the Volume+ button (on the right).
Alternate update method
Use the phone application to dial the following number * # * # 2 8 4 6 5 7 9 # * # * then, from the menu that appears, select:
"Project Menu Act -> Upgrade -> SD Card Upgrade -> SD Card Upgrade External Storage".
For both methods
Follow the instructions on the device screen (in green), the complete update process will be about 10 minutes, then the device will reboot a couple of times, be patient and let the device be quiet a couple of minutes more before touching it (while updating the sim, sn, touch & coulometer firmware).
I always suggest executing a "Factory reset" after a firmware upgrade. You can do that from "Setting -> Backup & reset -> Factory data reset" and if possible also check the box related with the formatting of the device internal memory (after ensuring you have made a backup of all you may need).
IMPORTANT !!!
To avoid touching key partitions of the Android OS and the original firmware I decided to leave the duplicated "Gallery2" application (found in the "system" partition). For this reason, after the upgrade you will end up with two "Gallery" applications. Deactivate or remove the first one of the two, the one which is smaller in size. The second one has more options (Google+/PicasaWeb sync) than the one pre-installed by Huawei. Since the device is "rooted" any file manager capable of browsing folders with "root" privileges will be enough to perform the removal.
Informations
This firmware uses an alternate method to obtain "root" permissions on the MediaPad avoiding modifications to important parts of the original firmware ("boot" and "system"), at the same time it adds missing Huawei/Google applications and enable some of the functionalities that were not enabled in the original firmware.
Modifications have been applied exclusively to the device "cust" partition ("cust.img.ext4") all the remaining partitions and files have been left untouched compared to the originals Huawei ICS 4.0.3 firmware released 21 June (C232B005).
Updated:
all ICS Google Apps (gapps-ics-20120429-signed.zip)
modified permissions for "busybox" executable (755)
International language selected as "default" (English)
International wifi settings for channels (13)
Added:
Huawei applications missing in the official version
GenieWidget application included in newer gapps-ics
Removed:
"Huawei Input Method" add-on keyboard and all related Language Packs (42)
Gmail, Maps, Music2, PlusOne, Street, TagGoogle, Talkback, Youtube
Aldiko, Facebook, FoxitReader, Twitter, YozoOffice and related libraries
two space hungry games, Asphalt6, LGolf and related libraries
images and demo animations (media)
List of added/updated applications and their versions:
AccountAgent-1.1.17.apk
AllBackup-4.1.33.apk
HiDisk-3.0.21.apk
HwOUC-2.3.8.apk
PhoneFinder-2.2.0.apk
PushAgent-2.2.1.apk
Superuser-3.0.7.apk
List of functionalities added to this firmware:
"root" permissions, Superuser.apk, busybox v1.20.1, su v3.0.3.2
firmware updates from "Settings" (Huawei/Google components)
Google GenieWidget & Google Backup Transport functional
Huawei applications: All Backup, HiDisk, PhoneFinder
* FIRMWARE DOWNLOAD *
ZIP containing firmware and software (essential: huawei_apps + google_apps):
Download size: 258.649.399 bytes (247Mb) - md5: 8c8bac1094d7dcb87d959a3be1482f6f
MIRROR 1 (GameFront)
* HUAWEI KEYBOARD DOWNLOAD *
ZIP containing the new keyboard and 42 additional language packs (Huawei Input Method):
Download size: 16.266.684 bytes (15Mb) - md5: 22b4aeddd6c214ffc7e5ef753216d68b
MIRROR 1 (GameFront)
Have fun,
.:HWMOD:.
HWMOD Linux kernel 3.0.42 Overclocked + customizations update
This update replaces (overwrite) the "boot" and "cust" partitions of the device.
The update process should retain all installed applications and data.
To achieve "non destructive" update I used the same method used in OTA updates.
At the end of the update process the tablet will reboot once more after restoring the
serial number, sim/imei, firmwares for touch-screen and coulometer etc.
The update methods remain unchanged (no need to use "fastboot/adb"):
1) download the compressed ZIP archive and unpack it on your PC
2) copy the "dload" folder contained in the archive on the external SD card
3) restart the device and follow exactly the on-screen instructions (in yellow)
The "boot" contains the new kernel 3.0.42 Overclocked and the initialization "ramdisk".
The "cust" partition has been updated with the new "Superuser.apk", "su" and "busybox".
Inside the ZIP compressed archive you will find a "readme.txt" with expanded informations and instructions.
Credits to "arkusuma" for the modifications related to the touch screen driver and to "contributors/modders" on XDA.
* FIRMWARE DOWNLOAD (updated 2012/09/10) *
ZIP contains kernel (boot.img) and customization software (cust.img)
Size: 82.463.617 (∼80Mb) - md5: 05dc4f0a5aa564dc8f628659540bbb8d
MIRROR 1 (GameFront)
* HUAWEI KEYBOARD DOWNLOAD *
ZIP containing the new keyboard and 42 additional language packs (Huawei Input Method):
Download size: 16.266.684 bytes (15Mb) - md5: 22b4aeddd6c214ffc7e5ef753216d68b
MIRROR 1 (GameFront)
Have fun,
.:HWMOD:.
what modifications did you made?
441Excelsior said:
what modifications did you made?
Click to expand...
Click to collapse
Sorry for the short description, really, many more info are missing. I will do my best to update and translate asap the rest of what I have published on "Androidiani" forum.
Basically I have added "root" permissions, removed all the extra applications and updated the Google Apps to a newer version (gapps-20120429-signed.zip).
I also added a few missing Huawei utilities like AllBackup, HiDisk and PhoneFinder that were found on previous Huawei releases.
The method I used to add "root" permissions is a bit different than on other modified firmwares. I only changed "cust" partition to achieve that, all the other partitions have been left untouched as the originals from Huawei.
I probably trust Huawei developers a bit more than others
441Excelsior said:
what modifications did you made?
Click to expand...
Click to collapse
OK, I added the expected informations in the op.
I will add more info and corrections.
How bout the edge to.H/3G? In 002 when there's still stuck problem..
Sent from my SPH-D710 using Tapatalk 2
It should work in this firmware (also I haven't tried yet).
The problem you mentioned was already fixed in both Russian releases.
There are no known problems for the phone to switch between 3G <-> HDSPA.
no gmail in this release? Noticed it when i was to replace gmail apk with a modified one.
mangoman said:
no gmail in this release? Noticed it when i was to replace gmail apk with a modified one.
Click to expand...
Click to collapse
Right ... not there. Why include Gmail if you wanted to replace it anyway ?
It would have happened anyway at first update (if you decided to install it).
I have tried to remove everything that can be installed later through the Market or by placing the file in the SD card. That gives end users more freedom and let them sort out OS/firmware related problems vs. applications bugs/problems.
This also avoid keeping duplicates in your device.
Since this firmware have "root" privileges, I suggest users to install their "preferred" applications in "/cust/channel/normal/delapp/" folder so if they later want to do software reset (Factory data reset) they will not loose their "preferred" applications.
Copying the ".apk" in that folder has to be done using a file manager that works and let you browse folder with "root" privileges (read/write).
Hope I answered the question and left additional informations.
There's a bug on HWMOD b005.
Double Galery icon.
I've big mistake to disable it, and my device freeze.
fortunately i can recover it with hard reset.
I think it'll better if you add V6Supercharger too.
Thank you very much
arekwaru said:
There's a bug on HWMOD b005.
Double Galery icon.
I've big mistake to disable it, and my device freeze.
fortunately i can recover it with hard reset.
I think it'll better if you add V6Supercharger too.
Thank you very much
Click to expand...
Click to collapse
This has both galery applications, one from the ICS and another from Gapps pack. You can safely uninstall anyone using Titanium Backup. I uninstalled the default ICS one. No problems so far...
Sent from my HUAWEI MediaPad using XDA Premium HD app
arekwaru said:
There's a bug on HWMOD b005.
Double Galery icon.
I've big mistake to disable it, and my device freeze.
fortunately i can recover it with hard reset.
I think it'll better if you add V6Supercharger too.
Thank you very much
Click to expand...
Click to collapse
you right agan gigiku.com
shiranmotha said:
This has both galery applications, one from the ICS and another from Gapps pack. You can safely uninstall anyone using Titanium Backup. I uninstalled the default ICS one. No problems so far...
Sent from my HUAWEI MediaPad using XDA Premium HD app
Click to expand...
Click to collapse
Exactly, you are correct, this is not a bug, it was on purpose.
No freezing and no crashes that we know about in C232B005.
I wanted to leave the choice to the users installing this firmware.
Users can remove the one they want/prefer, one is part of the manufacturer ICS release the other is in Google Apps, they have similar options but different functionalities. The one from Google can sync your picture with those uploaded in G+/PicasaWeb. I personally prefer to keep the second one, the bigger in size.
Since this firmware has "root" privileges it will be easy to remove the duplicate Gallery2 application by using a file manager or Titanium Backup as suggested.
I have not included V6 Supercharger and other stuff because it is not sure everybody wants it on their devices. It can be installed though, for those that want it, however I doubt it's needed on the MediaPad.
Updated the OP with needed informations for applying the upgrade process.
Added an additional mirror for the download of the firmware.
Please tell if you find mistakes or have suggestions.
.:HWMOD:.
hwmod said:
Exactly, you are correct, this is not a bug, it was on purpose.
No freezing and no crashes that we know about in C232B005.
I wanted to leave the choice to the users installing this firmware.
Click to expand...
Click to collapse
Thank you for your respond. I don't know exactly how my mediapad freeze. Now I reinstall your ROM again, and no problem so far.
If you don't mind, I have request. How about change boot animation? may be like OsiMood.
actualy, I love OsiMood User Interface, but cause They stop updating, I'm not using it anymore.
But, If you don't want to add it on HWMOD, could you tell me how to change it, please. I've try many application to change it, and change from /system/media/bootanimation.zip . But, it still not change.
Thank you very much.
arekwaru said:
Thank you for your respond. I don't know exactly how my mediapad freeze. Now I reinstall your ROM again, and no problem so far.
If you don't mind, I have request. How about change boot animation? may be like OsiMood.
actualy, I love OsiMood User Interface, but cause They stop updating, I'm not using it anymore.
But, If you don't want to add it on HWMOD, could you tell me how to change it, please. I've try many application to change it, and change from /system/media/bootanimation.zip . But, it still not change.
Thank you very much.
Click to expand...
Click to collapse
I never did it myself and it depends on what are your objectives.
If you want to just change the boot animation in your device doing what you did should be enough (make sure you use a correctly formatted/packed "bootanimation.zip") and give the right attributes to the files you modify.
If you need to modify an existing firmware and add a different boot animation then you have to handle "ext4" partitions images files under Linux ("system.img.ext4" in the update archive) and substitute that file in the "ext4" image.
If you just want to modify the boot logo, not the animation, you have to rewrite the "splash" partition using "fastboot" (called "logo" in MediaPad mmcblk0p10).
I need to do a test on a brand new Mediapad (not "rooted") but I don't have access to one.
Could someone execute the following "fastboot" command on a new device:
Code:
fastboot oem device-info
and report their results here ?
I have used 2-3 roms in my mp, is it ok?
dark_fighter said:
I have used 2-3 roms in my mp, is it ok?
Click to expand...
Click to collapse
Post them anyway, also they shouldn't be different from mine (more or less):
Code:
[email protected]:~# fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
OKAY [ 0.294s]
finished. total time: 0.294s
[email protected]:~#
I am not sure the internal "fuse" is set up to allow people some chance
I believe it is a one shot only sw "fuse", that's why I asked for a brand new device, one with the original manufacturer firmware and never rooted/unlocked.
Thank you.
Hotmail over active sync as a cooparate account not works for me. Any other faced the same issue? It says couldn't connect to server.
Sent from my HUAWEI MediaPad using XDA Premium HD app
I'm using Lenovo Ideatab A3000-h,
I want to make it to be set to run only one app after booting, not even the home page could run then, it will open at the app and still at it forever, I know it's a common need and this has been asked a lot of times before, So, after searching I discovered that there is three options :
1- Creating my own Custom ROM.
2- Making my application a launcher application using android manifest.
3- run a kiosk mode like surlock.
4- Modifying AOSP source code.
So, after a lot of search, I found that the third option can be easily broken be entering the tablet in safe mode and try to remove app then, or by removing it from accessing the tab by PC, and the second option can be broken by the same way.
So, all I got now is to use either the first option or the forth option, and when taking about the first option, thanks to NeroYoung I already know how to:
setting up android kitchen.
modifying ROM img files and jar files.
modifying build.prop.
generating the resulted Custom ROM.
but I don't know the way to reach my needs by customizing a ROM, so, all I want to know is how to modify the custom/stock ROM to achieve my requirement of booting to only a specific app. also if there is another way by making (System Backup ----> Modify ----> Restore Modified System) it will be great.
and when taking about the forth option, I already downloaded the source code and did know how to access it's resources, but don't know where is the source code that controls the start-up process and how to modify it. thanks in advance for all future contributors.
Hello -
I hope someone can help with making my app persistent in my custom ROM.
In the Android manifest, I have flagged my application as "persistent", so that it automatically restarts if it crashes, is less likely to be killed by the system, etc. I know that normal applications cannot use this setting, but I am working on a custom ROM, and I load my application into the priv-app folder, and so I am able to use it.
This works perfectly well on pre-Lollipop phones. However, when I build my APK into an Android 5 ROM, the "persistent" setting is no longer honoured. I can use 'dumpsys activity' to verify that my app is persistent on Android 4.4.4, but not on Android 5.0.
Is there some additional requirement for persistence in Android 5? I see that some system-supplied apps are still persistent, so it's not as if it's completely impossible. Thanks.
Figured it out myself eventually - turns out it was to do with selinux file permissions. I had to use chcon to copy the selinux file context from another file in the priv-app folder to sort it out.
You should put [SOLVED] in your thread title
Just found a beautiful ROM on 4pda forum. The ROM is developed by user booroondook. A few specifications, thanks to Google translate:
- DIY kit for all resolutions/platforms (well, all means RK3066 or RK3188 and the two main resolutions our units support). Just download the archive and run the setup script. Warning! Lollipop ROM only for RK3188!
-FUSE support - File system in User space. internal_sd is part of /data
-OTA system updates
-mostly untouched UI
-support for SD-card located startup script
For my GA2114 this is the most stable ROM to date.
The install procedure a little bit long-enter recovery, install, reset, enter recovery, install again, wait a long time for the intialization scripts to end. When done, enter settings and change the language to English as default is Russian - by far the most complicated part of the setup
You can take a look at it here.
A more detailed install procedure in this post
Latest KitKat build from March 2016 HERE
NEW Lollipop build - March 9, 2017 :Details and download link
Personally I need more info before installing this one. Perhaps Malaysk can comment on this rom
That ROM is significant step forward with FUSE. Installation is not problematic - it justbit strange. You have to install TWICE! First time, after initial boot, the new system partitions and links and file-system permissions are setup (this step cannot be done in recovery during initial firmware update). Then, for redefined OS and file sys mapping, SECOND firmware update (without wipping!) sets up everything in adequate locations (with FUSEd linkage among storage volumes). As you may figure out, you should let device to reboot after first install, but you dont have to let it go into full loading as it will usualy stuck (because needed foles are messesd up as the SECOND install is needed to put them in FUSEd locations).
So if you have problem with Russian and Google Translated very strange output, just do as above. Two times install ROM image. And its all fine.
Now, on the poibt:
I hope Malaysk will pay attention on this. The FUSEd ROM is much advanced option to better utilize our ibternal storage than 2GB or even 4GB data partitions fixed resizing (which is huge improvement itself from idiotic 1GB OEM Chinese 'design' I'm pritty sure is just blind copy-paste from some seed OS image they took from somewhere and they even after several years dont understand at ALL).
So I would kindly ask Malaysk to consider joining efirt with his Russian coleague who did FUSE but is not updating nor customizing his ROM as much and as dynamicaly (and passionately) as Malaysk.
So if Malaysk can adopt, merge, FUSE in his ROM it will be great leap forward for everyone. Original FUSE contribution would continu to live and power up the great Malaysk ROM branch. A I hope other devs them may find interest to join efforts, to contribute to that UNIFIED branch ratger than we have nu.ber of branches, at different stages, with different strengths and weaknesses....
Learning from mature dev teams working for years on phone ROMs, it is important to join, coordinate, split in modular but UNIFIED and at the end combined ROM released. It provided much better results. And it pays off for both us, users, and devs (if we pay respect they deserve for their noble effort).
I will always stress that I personally feel interest to stimulate this community to develop and matture. I'm very disapointed by Chinese very poor SW support, but I have beleive that HW is much more capable. So if we can get advanced SW for these units, it may well pay off for ALL of us who bouth them for fraction of price of OEM ones. An even we can have much better SW and overal functionalities than OEM. So the price difference allows us to dinate deacent sums to devs here if they provided us with good ROMs.
manicuspanicus said:
Personally I need more info before installing this one. Perhaps Malaysk can comment on this rom
Click to expand...
Click to collapse
Well, it was Malaysk who actually gave me the idea to look for these ROMS, in this post he mentions the other cooks.
Yes he did in a post where people want different colour on his rom . What I'm saying is I would like to know more like the description Malaysk has in his roms. Is it a big deal to ask you to give us a review of the rom and a step by step guide on installing it if there are some different steps from all the other roms?
Στάλθηκε από το ONE A2003 μου χρησιμοποιώντας Tapatalk
As I wrote, ROM us stock modded to have FUSEd partitions for data. Stabile as stock, looks like stock, perfirms as stock...
I explained install procedure as it is but strange and someone NOT knowing Russian may be buzzed with Google Translation (thinking it is transkation mistake to have double install needed).
But the real problem here us that devs are not joining and coordinating efforts. So we have Malaysk point insatisfied users to other ROMs... When dev starts to divert users to other ROMs, it looks something is wrong here, isnt it?
manicuspanicus said:
Yes he did in a post where people want different colour on his rom . What I'm saying is I would like to know more like the description Malaysk has in his roms. Is it a big deal to ask you to give us a review of the rom and a step by step guide on installing it if there are some different steps from all the other roms?
Στάλθηκε από το ONE A2003 μου χρησιμοποιώντας Tapatalk
Click to expand...
Click to collapse
I can do that, no issue. Just give me a couple of days. It's the least I can do for fellow xda members
FUSE seems to be the right way to go, i hate the fact that as standard i can only use 1gig for user data, and i also don't want to decompile and replace the file for partition and recompile every time i want to update/change rom etc etc.
So i hope Malaysk will pick it up and some proper documentation written by someone
m00n61 said:
I can do that, no issue. Just give me a couple of days. It's the least I can do for fellow xda members
Click to expand...
Click to collapse
:good:
Booroondook DIY ROM details
WARNING! Make sure you can boot into recovery even with the screen off. This will allow you to install a factory ROM if anything goes wrong.
Back up your user data. This ROM has to format the internal Flash so all user data will be deleted.
DISCLAIMER. I am not affiliated in any way with the developer of this ROM. All credits should go to 4pda user Booroondook. I only wanted to share this ROM that works perfectly for my unit, keeping the OEM flavor and vastly improving on functionality - yet is pretty much unknown due to language barriers.
Preparing for installation
1. Download the DIY kit to your computer. Unpack into any empty folder on your computer (the full path to the folder should not contain spaces, non-Latin characters, punctuation marks and special characters, so it is not recommended unpacking on the desktop, in the "My Documents"folder, etc.
2. Switch to the folder where you unpacked the archive.
2. Run start_eng.bat. Since you are reading this HOWTO I assume you are not familiar with Russian.
3. You will be prompted to select a processor. Only two options - RK3066 and RK3188. The selection is made by entering the numbers in front of said processor type, followed by pressing the Enter key
4. Next - the choice of screen resolution. There are also two variants - 800x480 and 1024x600. Selection is carried out in the same manner as in the preceding paragraph
5. After that begins the process of assembling the firmware, which takes less than 10 seconds.
4. Wait for the ROM to be prepared and, when done, exit the batch file.You will have a new file, called update_yourprocessor_yourresolution.img
5.Rename the generated file to update.img
6. Copy the file to an SD-card
Installation
1. Insert the Sdcard containing update.img in your HU.
2. Boot into recovery. On my unit I can do that in two ways:
a. Press the reset button. Keep ot pressed while also pressing the Power button. Release the reset button and keep the power pressed a few more seconds
b. Press the reset button. Press both Home and Power buttons for about 10 seconds (the button light will flash shortly) and release the Home button followed by releasing the Power button then pressing Power again .
2. Do a factory reset - the last option in the list - to clear data and cache
3. Update the firmware. Wait for the unit to reboot.
4. Whe you see the animated logo, reset the HU and re-enter recovery mode
5. Update the firmware again. Wait for reboot
6. The first start will take longer than usual due to the need to re-create the primary filesystem and running of initialization scripts.
Release notes:
Base firmware: HA-20151010
Initial DPI is set to 160 for 800*480 screens and 240 for 1024*600. You can change this in Settings
Initial language is set to Russian. Just go to Settings (you should recognize the icon) and look for язык - this means language in Russian. Click on that and change to your preferred language.
In the release notes, Booroondook says the ROM has USB debugging enabled which will prevent using a USB stick. I don't have that issue so maybe the article is outdated. Anyway, if you have this issue, either type ADBOFF in factory settings password field or delete the file /system/etc/init.d/01adbon
Custscript
If the root GPS-card contains a file with the name custscript, it will be executed when you start the HU.The requirements for the file are the same as in conventional Linux executable scripts. That is, an indication of the shell in the first line and the line breaks Unix-style.
The first line can be: #! / System / bin / sh
For example, if you are experiencing problems with the rebooting in recoveryi (no suitable hardware buttons, or other reasons), then you could put on the card a file with the following content:
PHP:
#! / system / bin / sh
reboot recovery
And your HU will reboot in recovery mode. However, don't forget to delete it when done.
This script can also be used for "early loading" applications and services.
The advantage of the script placed on the SDcard is that unlike install-recovery.sh, if something went wrong, you can simply pull out the card to fix the script. In addition, in some cases, through a script, you can "revive" the HU.
Other features - in no particular order
1. FUSE - no need for App2SD since all space is available for apps or data;
2. OTA system updates;
3. Both OEM launchers available - not in the initial kit, appeared after a second OTA;
Screenshots
Excellent job !
Booroondook is on XDA also, hes posted a good few times in the "original thread" (RIP - the thread, not Booroondook !).
I was aware he used to make ROMs for these units, but this past year its all been about Malaysk's, not heard anything about @booroondooks's.
bootloop after instalation
Great rom in the first half hour
same here
zorantoma said:
Great rom in the first half hour
Click to expand...
Click to collapse
Mine won't even fully boot after the 2nd update from recovery..Good to see that its not just me..
Edit
Tried with a newly created image from the Bat file.
Still looped but I was able to get it to work from the recovery screen by using the "reset to factory/clear data option"
After that the setup script worked.
New version is out
New version is out, based on HA-20151204. Get it here.
The following is taken from the author's post on 4pda:
Since the original is only for RK3188 / 1024x600, the kernel versions for other combinations of CPU and resolutions are from earlier firmware:
RK3188 / 800x480 - from JY-20150824
RK3066 / 1024x600 - from HA-20151010
RK3066 / 800x480 - from KLD-20151127
New features :
1. Two factory launcher - "HA / JY" and "KLD" - you can change the settings (Display -> Desktop). Both are fully functional (weather, radio, music, Bluetooth)
2. Support for trip computer "Multitronics MPC-800" - no need for Xposed module
3. Changes to preinstalled applications in the "OEM" section:
3.1 preinstalled applications (can be completely or selectively removed (Settings - Applications)):
- Chrome
- Root Explorer
- Terminal
- Titanium Backup
- True Contacts
- DPI Changer
3.2 Preloaded set of Xposed modules
3.3 APKs for manual installation ( OEM ):
- AirPin PRO
- CarService 2.1.3
- DAB
- EasyConnected.HT01.4.0.4-151012
- GScript_v.1.1.2_Rus
- Headunit 2.15
- IOnRoad.apk
- Multitronics_2015-12-24_beta
- RemoteADB
- Torque
- TPMS
4. Removed DPI change from the "Settings". Added app "DPI Changer" (pre-installed)
Hi @m00n61,
Is the version you just posted the one for 1024x600 rk3188?
If I understood well, have to install that twice?
Thanks!
magnificus said:
Hi @m00n61,
Is the version you just posted the one for 1024x600 rk3188?
If I understood well, have to install that twice?
Thanks!
Click to expand...
Click to collapse
The link is for the so-called "constructor" that can generate the Rom for your CPU/resolution combination. Just follow the steps in the first post to generate the one you need.
If you come from stock or another ROM, yes, you have to install twice and clear data/cache before and between installations.
If you already have the previous version installed then you only need to install once and it will be upgraded, keeping all your apps.
Im still new to MTCB, will this rom work on my Eonon GA5151F? http://www.eonon.com/Car-GPS/Specific-Car-GPS/Mazda/GA5151F.html
Thanks in advance
SkiRac3rDud3 said:
Im still new to MTCB, will this rom work on my Eonon GA5151F? http://www.eonon.com/Car-GPS/Specific-Car-GPS/Mazda/GA5151F.html
Thanks in advance
Click to expand...
Click to collapse
It should work. looks like you have a RK3188/800*480 unit. To be sure, go to Settings ->About tablet and check the 3rd line. If it starts with MTCB, this ROM will work for you.
What about RK3188 with 1024*600? I only see 1024*600 for RK3066, not for RK3188...
m4f1050 said:
What about RK3188 with 1024*600? I only see 1024*600 for RK3066, not for RK3188...
Click to expand...
Click to collapse
Well, post #14 says:
"Since the original is only for RK3188 / 1024x600, the kernel versions for other combinations of CPU and resolutions are from earlier firmware."
So yes, it's there.