TWRP recovery for the Nabi JR 16GB. (NABIJR-NV5B)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
.
This is for Nabi JR 16GB
Nabi2 is HERE
NabiXD is HERE
Nabi JR 4GB is HERE
To install this you must unlock bootloader which will ERASE THE DATA on your device, I will repeat it once more below but you have been warned
Auto Installer via NabiLabGUI http://forum.xda-developers.com/showthread.php?p=44258583#post44258583
If you wish to use TWRP for Nabi Jr 16GB this would be the instructions. USE AT OWN RISK!
1) Enter fastboot mode
With the Nabi powered off press and hold power and volume down.
2) Unlock the bootloader. This will erase everything on the device.
Code:
fastboot -i 0x0489 oem unlock
after issuing the above look at the Nabi screen and use volume keys to OK the unlock.
3) Enter fastboot mode (as described above)
4) Test and/or flash TWRP to your device.
Extract the TWRP download and place recovery.img in the same folder as your fastboot.exe
Run the command to test out TWRP
Code:
fastboot -i 0x0489 boot recovery.img
or this command to make it permanent
Code:
fastboot -i 0x0489 flash recovery recovery.img
5) To boot TWRP from power off. Press and hold power and vol up(different then fastboot and vol down)
6) MAKE A BACKUP! If it's like mine the swiping will be hard to start the backup, but just do it. The Nabijr should be in an unmolested(unrooted) condition with your personal info erased if you followed this. I can guarantee one of your fellow Nabi JR owners will at some point needs this so help them and help yourself. Now put a copy of that backup on your computer.
TWRP 2.6 for Nabi JR 16GB
TWRP 2.6 for Nabi JR 16GB(mirror)
To get your recovery back to stock if you flash TWRP:
Stock Recovery for Nabi JR 16GB(broken link)
device tree source: https://github.com/aicjofs/android_device_fuhu_juniorb
TWRP source: https://github.com/TeamWin/Team-Win-Recovery-Project/
Special thanks to Dees_Troy who helped me work out a touchscreen issue.
What's new in 2.6.1.0:
Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
Initial support for f2fs file system formatting (Moto X)
Update SuperSU install for 4.3 ROMs
Fixed a permissions bug on files created during backup
Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
Ignore lost+found folder during backup and size calculations
Various other minor bug fixes and tweaks
TWRP 2.6.1.0 for Nabi JR 16GB
Okay, two issues are making me feel dumb.
I'm not new to rooting, recoveries, ADB or Android (this is my 4th Android device), though I definitely don't consider myself an expert either.
16GB Nabi Jr, Nick Jr. Edition, rooted.
1. For whatever reason, the touchscreen does not seem to work on my rooted Nabi Jr 16GB (Nick Jr Edition, if that matters).
Tried TWRP 2.6.0.0 and 2.6.1.0
TWRP launches fine, but does not respond to the touchscreen at all. Power button will lock it, but of course then I can't slide to unlock.
All I can do is hold down Power button for 10 seconds to power it off.
TWRP does seem to be functioning, as I got root installed via Nabi Tools GUI with TWRP running.
2. I tried to restore to stock recovery with the NabiLab GUI, and via ADB Fastboot. Both report successfully loading the stock recovery, but when I boot to recovery it shows the "spinning hairball" for a second or two, then gives me a screen with the android with red caution triangle over his open chest (see image).
Any ideas where I screwed up?
bhiga said:
Okay, two issues are making me feel dumb.
I'm not new to rooting, recoveries, ADB or Android (this is my 4th Android device), though I definitely don't consider myself an expert either.
16GB Nabi Jr, Nick Jr. Edition, rooted.
1. For whatever reason, the touchscreen does not seem to work on my rooted Nabi Jr 16GB (Nick Jr Edition, if that matters).
Tried TWRP 2.6.0.0 and 2.6.1.0
TWRP launches fine, but does not respond to the touchscreen at all. Power button will lock it, but of course then I can't slide to unlock.
All I can do is hold down Power button for 10 seconds to power it off.
TWRP does seem to be functioning, as I got root installed via Nabi Tools GUI with TWRP running.
2. I tried to restore to stock recovery with the NabiLab GUI, and via ADB Fastboot. Both report successfully loading the stock recovery, but when I boot to recovery it shows the "spinning hairball" for a second or two, then gives me a screen with the android with red caution triangle over his open chest (see image).
Any ideas where I screwed up?
Click to expand...
Click to collapse
The First Q I think aicjofs would be better at answering
the 2nd looks like the Default boot loader(in the picture) .
(not TWRP)
can you preee vol + and vol - together on the dead Andoid screen and get a menu ?
also IS it USA version of the Nabi 16 Nick JR?
Thanks for the reply Eric!
Yes this is the USA version, and Yes! Pressing both Vol+ and Vol- together brought up the menu. I guess I just got used to it just appearing with Clockworkmod on my other devices.
Thanks very much! Feeling a little less dumb...
bhiga said:
Thanks for the reply Eric!
Yes this is the USA version, and Yes! Pressing both Vol+ and Vol- together brought up the menu. I guess I just got used to it just appearing with Clockworkmod on my other devices.
Thanks very much! Feeling a little less dumb...
Click to expand...
Click to collapse
One of 2 things. The kernel is different(seems unlikely since there hasn't been an update to this tablet has there?), or what has been the biggest issue is Nabi/Fuhu is using more then one manufacture and they have different accelerometers that get detected as input devices and mess with the touch interface. I would have to build a TWRP with logging enabled to check for that.
For the 2nd question, hey at least Nabi Lab GUI returned it to the stock recovery so it works! Haha.
Thanks aicjofs.
This is the version with the preloaded Nick Jr content so while I don't think there was a kernel update, I suppose anything is possible.
Here's the info from About tablet:
Model number:
NABIJR-NV5B
Edition:
NABIJR-NV5B-US-N
Android version:
4.1.2
Kernel version:
3.1.10
[email protected] #1
Fri Aug 2 09:07:50 CST 2013
Hardware Info.:
2KS16.SKU1
Product version:
1.0
Happy to dump a log if you want.
Glad that stock recovery is restored and working.
Try this one:
TWRP 2.6.1.0 with logging
Nothing has changed except more verbose logging with respect to touch.
fastboot boot recovery.img
After it boots try tapping the screen a couple times, and then do an
adb pull /cache/recovery/log twrplog.txt
In the adb directory upload the twrplog.txt somewhere for us to see.
Thanks again. PM-ed you link to twrplog.txt
I took a peek at it and it looked like nothing registered, even though I tapped each of the 4 top buttons, then the hardware back (house) button.
Weird.
bhiga said:
Thanks again. PM-ed you link to twrplog.txt
I took a peek at it and it looked like nothing registered, even though I tapped each of the 4 top buttons, then the hardware back (house) button.
Weird.
Click to expand...
Click to collapse
So your log says:
Code:
Event object: gpio-keys
EV: ST minX: 0 maxX: 0 minY: 0 maxY: 0
EV: MT minX: 0 maxX: 0 minY: 0 maxY: 0
Event object: tegra-aic325x Headphone Jack
EV: ST minX: 0 maxX: 0 minY: 0 maxY: 0
EV: MT minX: 0 maxX: 0 minY: 0 maxY: 0
Event object: lis3de_acc
EV: ST minX: -16000 maxX: 16000 minY: -16000 maxY: 16000
EV: MT minX: 0 maxX: 0 minY: 0 maxY: 0
Event object: ms-msg21xx
EV: ST minX: 0 maxX: 0 minY: 0 maxY: 0
EV: MT minX: 0 maxX: 800 minY: 0 maxY: 480
gpio-keys, tegra-aic325x have been fine on previous devices
lis3de_acc is the accelerometer that has been the issue with other Nabi's. I rechecked the TWRP source I use to disable specific Nabi things, and lis3de_acc and lis3dh_acc(some other Nabi's) are there. So that's not the issue.
ms-msg21xx is the touchscreen. On other Nabi's I'm pretty sure I have seen that one, and the Nabi2 original uses nt1103-ts.
I'm not exactly sure where to go since it sounds like you have a 1.0 kernel.
Can you pull the boot.img and recovery.img so I can compare kernels to what I have(remember I no longer have this device myself)
With TWRP booted and connected and use adb commands:
adb shell
dd if=/dev/block/mmcblk0p1 of=/data/media/recovery.img
dd if=/dev/block/mmcblk0p2 of=/data/media/boot.img
exit
adb pull /data/media/recovery.img
adb pull /data/media/boot.img
Sent, after I got my head out of la-la land.
After some testing via PM this was the version with fixed touchscreen.
TWRP 2.6.1.0 rev2
Thank you very much! Now I have a full backup.
What's new in 2.6.3.0:
Proper backup and restore of SELinux contexts (thanks to Tassadar)
Pull in some ROM information for backup name generation
Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
Add 1200x1920 theme (thanks to Tassadar)
A few other fixes and tweaks
Nabi Specific:
Changed external storage name to MicroSD card.
Added ability to backup /addon partition
Added ability to adjust screen brightness
TWRP 2.6.3.0
aicjofs said:
After some testing via PM this was the version with fixed touchscreen.
TWRP 2.6.1.0 rev2
Click to expand...
Click to collapse
So, if I have a NABIJR-NV5B-US-N this is the recovery I need to use?
n3wt said:
So, if I have a NABIJR-NV5B-US-N this is the recovery I need to use?
Click to expand...
Click to collapse
That's the one that works for me.
Sent from a device with no keyboard. Please forgive typos, they may not be my own.
bhiga said:
That's the one that works for me.
Sent from a device with no keyboard. Please forgive typos, they may not be my own.
Click to expand...
Click to collapse
Thanks for the reply! I'm working on this device for someone else so I'm trying to cover all the bases and ensure that I don't mess anything up.
n3wt said:
Thanks for the reply! I'm working on this device for someone else so I'm trying to cover all the bases and ensure that I don't mess anything up.
Click to expand...
Click to collapse
The 2.6.3.0 should have the changes from 2.6.1.0 rev 2 included so either should work. (I hate not having the device myself to check)
aicjofs said:
The 2.6.3.0 should have the changes from 2.6.1.0 rev 2 included so either should work. (I hate not having the device myself to check)
Click to expand...
Click to collapse
I'm glad you chimed in on this...I'll try the 2.6.3.0 and let you know. Do we still need a stock backup of the Nick Jr?
n3wt said:
I'm glad you chimed in on this...I'll try the 2.6.3.0 and let you know. Do we still need a stock backup of the Nick Jr?
Click to expand...
Click to collapse
Yes we do. No one has posted or at least have said they have a stock backup. If someone messes up its nice to at least have one out there somewhere even if by PM.
Related
This is a modified CWM-based recovery for the Motorola Photon 4G. It is based on my own custom code forked from the CyanogenMod team's recovery. The major changes I have made include full support for dual SD cards, support for webtop partitions (SD card and internal) and changes to Nandroid backup/restore for this phone's additional partitions.
Some highlights include:
Dual SD card support
ADB support
USB Mass Storage support
Nandroid additions/changes
ext3 formatting
Probably others
This recovery is only for UNLOCKED devices. It is intended to be flashed directly to the recovery partition.
UNLOCKED users can flash this recovery using:
Code:
moto-fastboot devices
moto-fastboot erase recovery
moto-fastboot flash recovery recovery-photon3.img
Example:
Code:
$ moto-fastboot devices
TA20700KXH fastboot
$ moto-fastboot erase recovery
erasing 'recovery'... OKAY [ 0.741s]
$ moto-fastboot flash recovery recovery.img
sending 'recovery' (4780 KB)... OKAY [ 0.490s]
writing 'recovery'... OKAY [ 0.544s]
This is posted in a DEVELOPER forum and is being released to help further the development of Android for the Motorola Photon 4G. I have NOT personally tested this on my phone and YOU assume full responsibility for any damage incurred to YOUR phone!
Click to expand...
Click to collapse
I do NOT have a Motorola Photon 4G. I have based this recovery off the Photon kernel and Atrix resources as suggested by Calkulin. I do not SUSPECT there will be problems but again, I have NOT personally tested this on my phone and YOU assume full responsibility for any damage incurred to YOUR phone!
Click to expand...
Click to collapse
SPRINT USERS
Orange 5.0.2.7-photon3 / ZIP version.
MD5 0dc70209659fecbf7a2a01fe64b431af / a7fa2daf946557006931d33f3954e350
Cyan 5.0.2.7-photon3 / ZIP version.
MD5 440baa230638bd12dfd38b67977d3ac3 / 4da9f845f5d8ae0c37d0e1deaecd931c
Light green 5.0.2.7-photon3 / ZIP version.
MD5 b0791b6a4e0ea1a593d450518f309315 / f4afa4ca6f9616713ba436149df48c46
Dark green 5.0.2.7-photon3 / ZIP version.
MD5 5ef4862918169c1b4f9b0cbd60c70267 / 12acbe4adac62dc79e9a2b9ed1d0ea3b
Blue 5.0.2.7-photon3 / ZIP version.
MD5 cb1a4b2b48d18f535f5a3ce312e3ee81 / 53eee173392a8a821e45e8ddb1bbefd6
Red 5.0.2.7-photon3 / ZIP version.
MD5 f95a0adfb47ae2b995412b89d95f40fe / ca222e4891f756b5b4ad59fe06b6f0bf
Original ROM Manager/CWM installable zip thanks to SolidHelix. You must still be UNLOCKED and have already applied at least one version of this recovery via fastboot to use them.
Source is here.
A few notes:
The "osh" partition is webtop. It is the largest by far and will take some time to backup. Nandroid is not frozen!
The "sd-ext" partition is an ext2/3 partition on your external SD card. Veterans will know this as apps2sd and data2sd from other phones. I am not aware of any use of this partition on this phone yet.
Thanks to:
Koush and the CM team for CWM
Calkulin for pointing out the kernel
Everyone who has made unlocking the Photon possible
** Changelog **
2011-11-14 (5.0.2.7-photon3):
Minor bugfix update mostly
ext4 experimental support
Added the ability to convert an ext3 partition to ext4 under advanced. Shouldn't break anything, but it is experimental
2011-09-23 (5.0.2.3-photon2):
Updated to CWR5 base source.
The blue version is now the new CWR5 color. Old blue is gone. New photos welcome!
2011-09-17 (4.0.1.5-photon1.3):
Added a verify option to the backup and restore menu.
Renamed internal SD card mount point to /emmc and external is now /sdcard (this is largely cosmetic).
Merged in miscellaneous fixes from the official CWM. Version 5 will be merged in once its ready.
2011-08-17 (4.0.1.5-photon1.2):
Changed fstab to ext3 since no kernel support yet
2011-08-17 (4.0.1.4-photon1.1):
Added 0MB option to ext3 partition size under External SD card partitioning which removes any ext3 partitions from the card (choose 0MB ext3/0MB swap to have only a FAT32 partition).
Added a red build to the mix.
Updated the update-binary in the CWM zips to be tailored for this phone.
Minor fixes to sdparted (log file related mostly).
2011-08-14 (4.0.1.4-photon1):
Initial release
Screenshots
Thanks to DarkSim2o9 for the following screenshots (these show an Atrix, but the color is identical):
Orange
Cyan
Blue
Light green
Dark green
Red
Known Issues
I doubt ext4 support works due to no kernel support. Disabled currently. Added in -photon3.
Soft keys to use as navigation may not work due to the kernel.
Miscellaneous
If you'd like ROM Manager to see this recovery as "official" you can try XCellPhoneSalesRep's suggestion posted here.
Alternately, you can try dcarpenter85's suggestion here.
For issues with recovery not sticking, see here:
Thanks to mrinehart93 for pointing this out.
The system runs /system/etc/install-recovery.sh on boot with the stock rom. On boot it checks the recovery partition for some update and with CWM installed decides to reflash the stock recovery over it. Rename or delete the file and the CWM should stick.
Click to expand...
Click to collapse
Old versions
You can browse and download old versions here.
Awsome!!!
Sent from my MB855 using XDA App
Sounds good. Will try.
Sent from my unlocked rooted Moho!
This is what Calk posted earlier......right? I know it's yours, but not to be confused......just different colors...correct?
I like that there is a choice of colors. Well done!
Awesome job. One question, how might one boot direct into the recovery from a full Power Off?
the3rd said:
Awesome job. One question, how might one boot direct into the recovery from a full Power Off?
Click to expand...
Click to collapse
Hold down volume down and power till boot. Volume down till you see android recovery, then volume up.
Also, as aaron130 said you can use quick reboot from the market.
Sent from my unlocked rooted Mopho!
Fricken Awesomeness
Sent from my Photon Blaster.
ahhh this is what im getting..it seems fastboot isnt working for some reason even tho i just rooted..some help please
C:\AndroidSDK\tools\moto-fastboot>moto-fastboot devices
C:\AndroidSDK\tools\moto-fastboot>moto-fastboot erase recovery
< waiting for device >"
edit: nevermind got it working ..thanks!
Two questions:
1. Has anybody verified the "ROM Manager support" method on the Photon yet?
2. Other than color choice, what is the difference between this recovery and the one Calkulin posted earlier?
i think theres an issue with the recovery.
it installed perfectly and booted properly.
i chose to format the internal sd partition and it didnt remove any of the data.
i havent tried to flash anything yet or make a nandroid but ill keep you posted and i do have it loaded.
thanks for all of your hard work. greatly appreciated
the3rd said:
Awesome job. One question, how might one boot direct into the recovery from a full Power Off?
Click to expand...
Click to collapse
the same way you boot into fastboot
when phone is off.......
1. press and hold power and volume down
2. when the phone displays fastboot release the buttons
3. use volume down to switch to android recovery
4. press volume up and boot into cwm
Im creating a backup as I type (speak)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
jglee311 said:
This is what Calk posted earlier......right? I know it's yours, but not to be confused......just different colors...correct?
Click to expand...
Click to collapse
Lokifish Marz said:
Two questions:
1. Has anybody verified the "ROM Manager support" method on the Photon yet?
2. Other than color choice, what is the difference between this recovery and the one Calkulin posted earlier?
Click to expand...
Click to collapse
Calkulin's is based off my -atrix3 revision. This is slightly newer code (-atrix3.1 bug fixes mostly). It uses the same kernel as his. He PM'ed me to let me know how he got it to work on this phone and I simply used his advice to create the thread.
I haven't verified ROM Manager on this phone. It may need until Koush updates ROM Manager to say it supports this phone. I thought several times about editing that out of the second post but chose to leave it for now..
tim-tim said:
i think theres an issue with the recovery.
it installed perfectly and booted properly.
i chose to format the internal sd partition and it didnt remove any of the data.
i havent tried to flash anything yet or make a nandroid but ill keep you posted and i do have it loaded.
thanks for all of your hard work. greatly appreciated
Click to expand...
Click to collapse
Under Mounts and Storage menu? If someone can provide me with /proc/mounts while booted into regular Android, I can check it out.
romracer said:
Under Mounts and Storage menu? If someone can provide me with /proc/mounts while booted into regular Android, I can check it out.
Click to expand...
Click to collapse
http://pastebin.com/uGakTEYu
Yay 4 Juggs said:
http://pastebin.com/uGakTEYu
Click to expand...
Click to collapse
Thanks, the table looks exactly like the Atrix (not surprising). If choosing "Format /sdcard" from the mounts and storage menu didn't work, I'll probably need /tmp/recovery.log after trying (but before exiting recovery - the file is lost then).
Minor update released. Biggest changes include 0MB ext partition option under external SD card partitioning which combined with 0MB swap gives you just a FAT32 partition without having to use Windows, etc. There's also a red version now.
The code is technically based on 4.0.1.5 but Koush pushed his commit late and so the build still says 4.0.1.4. I didn't see the need to recompile just for that
romracer said:
Minor update released. Biggest changes include 0MB ext partition option under external SD card partitioning which combined with 0MB swap gives you just a FAT32 partition without having to use Windows, etc. There's also a red version now.
The code is technically based on 4.0.1.5 but Koush pushed his commit late and so the build still says 4.0.1.4. I didn't see the need to recompile just for that
Click to expand...
Click to collapse
are the tools fixed such as being able to clear cache...nandroid...etc?
Say hi to "CyanoBoot" -- a 2nd bootloader/w menu aka "ub2" - (WIP)
“CyanoBoot”
(aka a "second bootloader")
Quick Guide
by fattire
(@fat__tire on Twitter)
Alpha 0: "I don't have a NT" Edition
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(Thanks to indirect for the image.)
What is CyanoBoot?
CyanoBoot (working title) is a “second bootloader” in early development, which is based on the open-source “u-boot” project, as further customized by BN & Bauwks. It is similar to the bootloader provided by Bauwks but has additional enhancements to make booting unsigned partitions easier and to generally enhance the booting experience on the Nook Tablet (aka “acclaim”) device.
CyanoBoot is intended for use with the forthcoming CyanogenMod 9, but it can also be used to boot CM7 or Ubuntu Linux or even the stock firmware (provided of course you are not legally or contractually bound from doing so. I haven’t read or agreed to any BN user agreements, so can’t speak to this.)
CyanoBoot includes an on-screen menu system, the ability to boot into three basic modes (normal, recovery, and “altboot”), configuration options, fastboot, and more.
The same version of CyanoBoot should start from both SD card and emmc (although it must be packaged and installed differently for each.) It should work on both the 1gb and 512mb RAM models. NOTE: It has been reported that some devices may require a USB cable to be plugged in to boot from SD Card. If true, this issue is not understood and is not addressed, nor is it likely to be.
NOTICE: CYANOBOOT (WORKING TITLE) IS HIGHLY EXPERIMENTAL AND IS NOT INTENDED TO BE USED BY NON-DEVELOPERS AND/OR THOSE UNWILLING TO ACCEPT FULL RESPONSIBILITY FOR ANY UNTOWARD CONSEQUENCES OF USING (OR ATTEMPTING TO USE) THE SOFTWARE. ALL SUCH ACTIVITY MUST OCCUR *ENTIRELY AT YOUR OWN RISK* AND YOU ACCEPT ALL CONSEQUENCES FOR DOING SO. THE USE OR ATTEMPTED USE MAY HAVE UNINTENDED RESULTS, INCLUDING BUT NOT LIMITED TO LOSS OF DATA, DAMAGE TO HARDWARE, AND/OR EXPLOSIVE DIARRHEA. CYANOBOOT IS NOT ENDORSED, AFFILIATED, SPONSORED, NOR ASSOCIATED WITH THE "DAS U-BOOT" PROJECT, GOOGLE, BARNES AND NOBLE LLC, TEXAS INSTRUMENTS, DENX., NOR ANY OF THEIR PARTNERS, OWNERS, EMPLOYERS, AFFILIATES, CLIENTS, SUBCONTRACTORS, OFFICERS, DIRECTORS, ADMINSTRATORS, INFORMATION PROVIDERS, ETC. EXCEPT INSOFAR AS THEY HAVE PROVIDED AND LICENSED SOURCE CODE TO BE FURTHER MODIFIED AND DISTRIBUTED. SEE THE RELEVANT GNU PUBLIC LICENSE FOR LICENSING DETAILS AND OTHER DISCLAIMERS. THIS SOFTWARE IS OBVIOUSLY INTENDED FOR USE ONLY BY THOSE WHO ARE AUTHORIZED TO DO SO.
Whew!
LIST OF THINGS
Started with “UB1” (aka u-boot, “first boot”) source code
Includes changes to support new 512MB model
Includes Bauwks’ repairs to fix “locked bootloader” malware
Many duplicate UB1 functions removed
One-build-boots-all (emmc or SD card, custom OS or stock)
Boot device indicator (top-left corner)
Bootcount indicator (top-left corner)
On-screen feedback to let you know what it’s loading.
Console-based boot menu
Support for key-combo shortcuts for menu/recovery
Alternate “Altboot” multiboot support allows 2nd OS.
Emmc setting for default boot profile (normal/altboot)
Emmc setting for default boot device (emmc or sd)
Emmc setting for automatic bootcount clearing
Boot fallback for stock firmware (0 bytes + sec. header)
Boot fallback for bauwks’ uboot (256 bytes)
Numerous visual enhancements
Unused bulky images removed (smaller file)
FASTBOOT support (w/menu selection)
On-screen build timestamp so you know version
Perhaps much more, or maybe not
There are likely bugs all over the place, but this is how it's supposed to work:
Key Shortcuts
Hold down home (“n”) key for the menu.
Hold down home (“n”) + “power” to have UB1 start recovery. If UB2 is also installed, it should respect this key combo and continue to load recovery.
The default behavior if no keys are pressed is to boot “normally”-- if booting from emmc, the boot partition (p4) from emmc will be booted. If booting from SD the boot.img on SD file will be booted.
The Boot Menu
Use the Home (“n”) key to navigate through the menu options. You can select an option with the power key.
The option you choose will override any other configuration you have made.
NOTE: Just so you don’t ask-- the reason the home and power keys are used to navigate through the menu rather than the volume up and down keys is due to a required driver not being included with u-boot 1. While the home and power keys use a very simple “gpio” method to detect if they are pressed, the volume keys are more like keyboard keys and thus are more difficult to detect. (The Nook Color bootloader, in contrast, did have the appropriate driver, so volume key detection was possible.)
Boot Indicators
Since you can boot from either SD or EMMC, it may be difficult to ascertain which version you are starting from.
Never again. You can now see whether you have loaded CyanoBoot from EMMC or SD by lookin at the top left corner:
“E” -> CyanoBoot is starting from emmc
“S” -> CyanoBoot is starting from SDCard
The # that follows this indicator is the current “bootcount”. After 8 unsuccessful boots or so, stock behavior is to run recovery with a reflash instruction. See below for instructions on clearing the bootcount at every boot automatically.
Fastboot (used for development)
For those familiar with “fastboot”, you can select the fastboot option from the CyanoBoot menu to go into fastboot mode. You can then (hopefully) flash to the boot or recovery partitions via USB cable using a command such as:
$ fastboot flash boot boot.img
Installation (SD Card boot)
(If you are preparing your own SD card for booting, you should be aware that for OMAP devices such as the acclaim, the SDcard must be formatted using a very specific configuration, which is detailed elsewhere.)
For SD Card, CyanoBoot is packaged inside a “flashing_boot.img” file to be placed in the first vfat partition of the SD-card along with the signed “mlo” and “u-boot.bin” files from the 1.4.2 update.zip.
(I'm told the mlo file may be called called MLO_es2.3_BN in the BN update.zip and should be renamed to “mlo”.)
Next, the boot (“boot.img”), recovery (“recovery.img”) and/or alternate boot (“altboot.img”) image files may optionally be placed in this partition.
Installation (EMMC boot)
To boot from emmc, the “flashing_boot_emmc.img” file, which contains a packaged version of CyanoBoot, should be put at byte 0 of the third partition (recovery) and ALSO at byte 0 of the fourth partition (boot). Then, the boot/recovery partitions must be shifted “to the right” (to make room for Cyanoboot) so that it starts 512Kb in from the start of the file. Use a padding of zeros so that the boot image contents begin exactly at 512Kb.
The boot and recovery partitions are expected to use this offset. For the alternate boot from emmc, the “altboot.img” may be the identical file used in an SD-boot, placed into the /bootdata vfat partition without any offset.
NOTE: Again, use the flashing_boot_emmc.img file for emmc boot partitions, *not* flashing_boot.img, which is for SD card boot.
Offset Info
Again, when used on the emmc, CyanoBoot must be placed at byte 0, at both the boot and recovery partitions. The “actual” boot.img and recovery.img that would normally be at byte 0 of those partitions should be moved so that it starts 512Kb in.
Always use this offset in recovery (p3) and boot (p4) partitions. In other words, put CyanoBoot at offset 0 and then pad with zeros, then put the normal boot.img or recovery.img at offset 512.)
On SD Card, the “boot.img” and “recovery.img” files should have no padding or offset or anything. Use as normal. This is similar to how “uImage” and “uRamdisk” files are used on the NookColor, only use a single file for both with a header in front.
Installation Summary
One more time. Here are the locations for the boot images:
SDCARD
(p1-vfat)/boot.img file (no offset/padding)
(p1-vfat)/recovery.img file (no offset/padding)
(p1-vfat)/altboot.img file (no offset/padding)
EMMC
(p4-/boot partition)<- CyanoBoot at byte 0, boot.img contents at 512.
(p3-/recovery partition)<- CyanoBoot at byte 0, recovery.img contents at 512.
(p6-vfat)/bootdata/altboot.img (no offset/padding, same as SDCard)
Configuration
You can control the "default boot" behavior (ie, what happens when you don’t hold down any keys). If you are a developer that does not want to constantly clear the bootcnt, you can also cause CyanoBoot to clear the bootcount automatically at every boot. To do this, three configuration files may be added to /bootdata (partition 6) on the emmc.
CONFIG #1: BOOT DEVICE
This will cause CyanoBoot to always boot from the emmc boot partition rather than SD. In this way, you can boot “through” a bootable SD card to whatever is on the emmc.
To Make Default Always Boot To EMMC
$ echo -n “1” > /bootdata/u-boot.device
CONFIG #2: ALTBOOT
Aside from the normal boot and recovery boot, a third boot option is available, called “altboot” (alternate boot). This is a kernel/ramdisk pair that can be used for a third firmware, an overclocked kernel, or whatever you like. If you choose the “altboot” as a default and it does not exist, your boot will fail.
As discussed above, the altboot.img file goes in the following location:
SDCard: file on p1 called “altboot.img” (no special padding or offset)
EMMC: file at /bootdata/altboot.img (no special padding or offset)
To Make Default Always Boot to “altboot”
echo -n “1” > /bootdata/u-boot.altboot
CONFIG #3: CLEAR BOOTCOUNT -- You can automatically zero out the bootcount with every boot. To set this:
To Make Default Automatically Clear BootCount
echo -n “1” > /bootdata/u-boot.clearbc
NOTE: A version of “Nook Tablet Tweaks” is planned to automate the above options much as Nook Color Tweaks does for the encore device in CM7.
Thanks/Credits
Thanks to chrmhoffman, nemith, xindirect, Celtic, and loglud for testing, as I don’t have a device and have never actually run this. Thanks to j4mm3r for the first encore menu code. It was pretty much rewritten for acclaim, but the first menu was invaluable in showing me how to add the code for the console. Thx to pokey9000 for stuff that helped get fastboot working.
Also thanks to BN as well as all the talented u-boot developers at Denx and elsewhere for the GPL’d code upon which this was based.
http://www.denx.de/wiki/U-Boot is where you can find the main u-boot project.
Also, a huge thanks to Bauwks for his code contribution as well as for making this possible in the first place!
Remember, this is all experimental. I'll try to update this post if there's something that needs to be updated.
(source)
If you have an issue, be sure to mention the timestamp at the bottom so everyone knows which version you're using. There will be bugs.
reserved for future expansion
Awesome
Hi,
Congratulations fattire. This is amazing work.
It boots the CM9 nicely.
Rgds,
Chris
I just gotta say, I laughed pretty hard when I read: Alpha 0: "I don't have a NT" Edition
Thanks
Wow
wow wow and we can use fastboot on the nook Tablet too? awesome
~ Veronica
Yep.
Works fine. Sometimes I have to re plug device though. But it speeds up things incredibly.
Chris
lavero.burgos said:
wow wow and we can use fastboot on the nook Tablet too? awesome
~ Veronica
Click to expand...
Click to collapse
Sent from my GT-I9000 using XDA App
Great work! Especially thanks for mentioning GPL software and folks behind it - that's thanks to them Android, Nook, Kindle, and even this bootloader were at all possible. So, where's source for the changes you made to this GPL software? Thanks again.
It's in the same directory. I'm going to make it a little clearer in the OP and I think maybe better organize the link to be in a subdirectory. So heads up that the links will change... ...changed.
fattire,
This looks great! Is it extensible to other devices like CWM recovery? I'd love to see this on the Transformer/Prime. Ubuntu on those devices replaces recovery, so it would be great to have a 2nd bootloader to get past these limitations. Also, it would be cool to see CyanoBoot on other devices like the NC and Touchpad. The TP has moboot but I think there's something to be said for consistency in this area.
Awesome work!
-mm
Yes, it'll work with CWM, TWRP2, or any other recovery. That's the point
Looks like the prime is a tegra3-based system. I don't know much about the bootloaders for Nvidia machines-- the nice thing about OMAP3/4 from Texas Instruments is that the u-boot bootloader works great, and is open source so you can extend it and stuff. While the bootloader for transformer is now unlockable I don't know that they give you the source, do they?
That said, from CM on the Qualcomm-based touchpad I know that a similar 2nd-level boot menu can be added AFTER the bootloader. Take a look at
the excellent moboot (lead developer is jcsullins) for an idea of how to add a very flexible menu that slips between the bootloader and the kernel. You can see it in action on youtube-- just look for any TouchPad cm7 or cm9 video where it boots up and you can select between CyanogenMod, WebOS, or one of the recovery images.
Hope that helps!
Mistar Muffin said:
fattire,
This looks great! Is it extensible to other devices like CWM recovery? I'd love to see this on the Transformer/Prime. Ubuntu on those devices replaces recovery, so it would be great to have a 2nd bootloader to get past these limitations. Also, it would be cool to see CyanoBoot on other devices like the NC and Touchpad. The TP has moboot but I think there's something to be said for consistency in this area.
Awesome work!
-mm
Click to expand...
Click to collapse
fattire said:
Yes, it'll work with CWM, TWRP2, or any other recovery. That's the point
Click to expand...
Click to collapse
Sorry, I was trying to ask if CyanoBoot would be available on multiple devices the same way CWM is. I understand it allows the booting of recovery images. What I did not realize was that uboot was tied to the TI OMAP platform, so you're answer was very helpful. Thank you!
Gonna be honest, I'm pretty sure this is for flashing roms such as how cwm allowed me to install cm7-teamb but I'm not sure. Also I saw someone say it flashes cm9? Sorry I'm just trying to get a feel at what this would really be used for, no offense intended.
fattire said:
It's in the same directory. I'm going to make it a little clearer in the OP and I think maybe better organize the link to be in a subdirectory. So heads up that the links will change... ...changed.
Click to expand...
Click to collapse
Thanks! Why not push it to github? (At least I had a look thru your repos on github yesterday and didn't see anything related, sorry if I missed something.)
Thanks for the awesome work fattire.
Here are the problems I found:
I manage to include cynoboot in recovery & boot but then there's device no found error using adb. Am I missing some drivers? (I am using WinXP)
because of that fastboot is not working too.
and then once enter fastboot mode. I can't get out unless I power off (n button can't navigate)
Hi,
you can use "fastboot reboot" to reboot the device. I didn't have an adb problem. Are you saying you try to adb into the device when in the menu? This doesn't work as there is no android running. I guess on windows you have to install android SDK first to get the drivers.
Rgds,
Chris
chrmhoffmann said:
Hi,
you can use "fastboot reboot" to reboot the device. I didn't have an adb problem. Are you saying you try to adb into the device when in the menu? This doesn't work as there is no android running. I guess on windows you have to install android SDK first to get the drivers.
Rgds,
Chris
Click to expand...
Click to collapse
I mean if I boot up the rom (I'm running MIUI) with the boot.img that includes cynoboot, then adb does not work (device not found). If I boot with the original boot.img, then no problem with adb
And fastboot command does not work for me either (I have android sdk installed)
I'll try the sdcard version later.
sungod88 said:
Gonna be honest, I'm pretty sure this is for flashing roms such as how cwm allowed me to install cm7-teamb but I'm not sure. Also I saw someone say it flashes cm9? Sorry I'm just trying to get a feel at what this would really be used for, no offense intended.
Click to expand...
Click to collapse
It's a bootloader
cobrato said:
I mean if I boot up the rom (I'm running MIUI) with the boot.img that includes cynoboot, then adb does not work (device not found). If I boot with the original boot.img, then no problem with adb
And fastboot command does not work for me either (I have android sdk installed)
I'll try the sdcard version later.
Click to expand...
Click to collapse
Are you using the 1.4.2 mlo and a 1.4.2 kernel?
fattire said:
Are you using the 1.4.2 mlo and a 1.4.2 kernel?
Click to expand...
Click to collapse
I'm using 1.40
Sent from my LT18i using Tapatalk
cobrato said:
I'm using 1.40
Sent from my LT18i using Tapatalk
Click to expand...
Click to collapse
cyanoboot is effectively a 1.4.2 u-boot.bin as far as handling the 512 model and all that goes. I don't konw that there were significant changes that would affect usb/adb, but jic you might want everything to match up...
Oh also, as far as fastboot goes... the device vendor_id was changed from 0x0451 to the google usb vendor id that most fastboots use which is 0x18d1. The device product_id is 0x0100.
Worked for chrmhoffman and others...
Disclaimer: You are responsible for insuring you keep a backup of your stock recovery!
See Post 7 for the Stock Recovery if you failed to keep a copy for yourself: Click here
Steps for Backing up Stock Recovery:
Code:
fastboot boot /path/to/TWRP.img
The above command will only boot the recovery and will not overwrite your stock recovery making it possible to backup your stock from within TWRP. Now backup your recovery partition from within TWRP. It will be saved on your device and named, recovery.emmc.win. You can rename it to recovery.img to flash it back via usage of fastboot or apply restore within TWRP given the original filename, recovery.emmc.win.
Or within a terminal using dd (aka Data Destroyer);
Code:
dd if=/dev/block/mmcblk0p19 of=/sdcard/stockrecovery.img
TWRP for MT2-L03
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CHANGELOG for 2.8.0.0:
-Add MTP support to recovery thanks mostly to bigbiff with a little help from Dees_Troy
-Add command line capabilities - you can now execute various TWRP features via adb instead of the touchscreen
-Add support for color in the console and give error, warning, and highlight lines different colors
-Track backup and restore progress based on file sizes to provide a much more accurate indication of progress
-Improve handling of /misc thanks to mdmower
-Improve setting of time on Qualcomm devices thanks to [NUT]
-Allow using images on slidervalue GUI objects thanks to Tassadar
-Allow using variables and addition and subtraction in variables for easier theming
-Add support for 1440x2560, 280x280, and 320x320 resolutions and update 240x240
-Allow ui.xml file to include additional xml files to help break up the theme and make TWRP easier to maintain
-Other minor fixes and improvements
Over the course of the last year or so, bigbiff has worked to migrate various Java functions from Android's MTP implementation to bring you a fully C++ based MTP implementation that allows you to transfer files to both emulated storage and Micro SD cards. It's confirmed to work on various Nexus devices but we may have to make some changes on other devices to keep Windows happy. Windows is very picky about USB IDs and its drivers. We have tested it on Windows 7 and 8 as well as Ubuntu 14.04 Trusty. MTP is enabled by default, but we do toggle it off and on automatically during certain operations such as if you choose to wipe a storage partition. You can enable or disable MTP under the mount menu in TWRP. For more about what MTP is here.
Note: Due to a weird bug with our MTP setup, you cannot copy a zip file to the root of storage with Windows. You can change the .zip to something else like .txt and then copy it to the root and rename the file back to .zip once it's copied to the device. You can also copy the zip into any subfolder.
Command line support is also now available. You can perform various OpenRecoveryScript commands via the adb shell. Depending on what you are doing you may wish to do a "twrp set tw_mtp_enabled 0" and then reboot to prevent the MTP auto toggle from killing your adb interface. You can use this option to create and restore backups, wipe, install zips, and more. Via adb shell, type twrp followed by a space then enter the OpenRecoveryScript command and hit enter. Find more OpenRecoveryScript commands here.
Installation (PC):
- You MUST have an unlocked Bootloader! /* See Post 2 */
- Download TWRP Recovery
- Boot to your Bootloader
- Plug your device to your PC
- Open Command Window
- Type, then Enter:
Code:
fastboot flash recovery /path/to/TWRP.img
- Also, a video to demonstrate the process of installing TWRP - Credit goes out to @superbass311:
Installation (Device)(More Experienced Users Only!):
- You MUST have an unlocked Bootloader! /* See Post 2 */
- You MUST be rooted!
- Must have Busybox installed or a properly compiled DD binary
- Download TWRP Recovery
- Install a Terminal Emulator from the Play Store
- Type, then Enter:
Code:
su
Followed By:
Code:
dd if=/path/to/TWRP.img of=/dev/block/mmcblk0p19
Download:
- TWRP 2.8.0.0
CONTRIBUTORS
@Modding.MyMind
@xordos
@Shaky156
SOURCES
- Recovery built in a OmniRom 4.4.4 environment using device trees/kernel/dtb
- Stock Kernel
- Stock DTB
- TWRP source from Omnirom
- MT2-L03 Device Configuration Folder - My Github
VERSION INFORMATION
- Status: Stable
- Created 2014-09-22
- Last Updated 2014-09-22
Unlock Your Bootloader:
As we all know, you are not required to be rooted to install TWRP, however, you must unlock the bootloader on your device.
You must email [email protected] asking:
Hello I purchased the Ascend Mate 2 and I would like my bootloader unlock code.
SN: xxxxxxxxxxxxxxxxxxx
IMEI: xxxxxxxxxxxxxxxxxx
Thank you
Click to expand...
Click to collapse
You should get a response within 24 hours. In a situation where 24 hours has passed by than simply be patient or send another email. This is the 1st step to being able to unlock your bootloader (as of now)!
Here is a video to demonstrate to you viewers how you can go about unlocking your bootloader.
- Video credit goes out to @superbass311
*Reserved Again*
I will flash tomorrow. You just made the HAM2 the hottest phone out.
Sent from my MT2L03 using XDA Free mobile app
Thanks to all involved. Re-installed root using TWRP. Now Titanium Backup is working properly.
Flashed just now!
Backing up at the moment.
THANK YOU ALL!!!
How I did it:
Win 8 pc.
Phone booted and usb debugging allowed.
typed "adb.exe reboot bootloader" in cmd terminal
typed "fastboot flash recovery c:\adb\TWRP.img" in cmd terminal
I downloaded zip to my adb directory, also had to rename it too "TRWP.img" as download was "TWRP_MT2-L03_RECOVERY.img"
back up completed in 480 seconds!
Did have to play with TWRP settings as I hadn't used it in a while .
DID I SAY THANK YOU!!!
For anyone who is lazy to backup your stock recovery, I have uploaded my stock recovery image backup here, it should be same for all our MT2-L03 phone
This is backup of stock recovery, only use this image if you want to revert back from TWRP to Huawei stock crappy recovery.
http://tinyurl.com/qzxkm4x
FileName: recovery_MT2L03_mmcblk0p19.img
md5sum: 35703a1fe81917cb7930ab1e9e93e499
Edit: 2nd thought, they should be same, but let's make sure. Can anyone did (or going to) backup your phone stock recovery post the md5sum of yours? The ES file explorer can calc md5sum for a file.
Thanks iammudd, I think it is confirmed the recovery image is same for all MT2L03 phone.
Absolutely freakin' FANTASTIC!!!
Flashed it via fastboot with no problems.
I couldn't get MTP to work, but that's not a huge surprise to me as I've NEVER seen MTP work properly in TWRP on any device I've had sofar. I'd be interested to see if it works for anyone else.
So awesome that a root method is built right in too!
I think this is the verge of some huge things happening for our MT2-L03s!!!
Thanks for the great work!
TheGeekRedneck said:
Absolutely freakin' FANTASTIC!!!
Flashed it via fastboot with no problems.
I couldn't get MTP to work, but that's not a huge surprise to me as I've NEVER seen MTP work properly in TWRP on any device I've had sofar. I'd be interested to see if it works for anyone else.
So awesome that a root method is built right in too!
I think this is the verge of some huge things happening for our MT2-L03s!!!
Click to expand...
Click to collapse
Thanks for the info, right, mtp not work during my init testing as well. So other device are running twrp 2.8.0 or later?
PS, there are another 2 known issus,
* date is ~1970
* off mode charging
xordos said:
Thanks for the info, right, mtp not work during my init testing as well. So other device are running twrp 2.8.0 or later?
PS, there are another 2 known issus,
* date is ~1970
* off mode charging
Click to expand...
Click to collapse
Check your hangouts
Well done everyone ! Excellent stuff.
I suppose you know what my question will be,lol, but is it feasible to be able to port this to the MT2-L05 or other Chinese models?
If it's likely to be feasible, would it be possible to have your permission to attempt a port, or do you think as the underlying processors are different
it would probably wiser to start from scratch?
Either way, good work again !
xordos said:
* date is ~1970
* off mode charging
Click to expand...
Click to collapse
Interesting that backup filename is 1970-03-23 but the timestamp is 1979-12-31 23:00 on the phone.
After FTP'ing them onto Win7, their last modified times are 2013-12-31 22:00.
The device configuration folder used to build TWRP is available on my github which you can find the link in the OP under "SOURCES". If you have any knowledge on this stuff then feel free to look it over and throw some patches my way. As it stands, mtp isn't working properly however, mtp has only been known to work for a very small select list of devices. A very small list. As for the time stamp, this isn't much of a concern on my part as it is merely cosmetic. However, the problem with it would most definitely be the result of the actual TWRP source and not the configuration folder (device tree). Feel free to look further in to it if it is bothersome.
Right now, my goal is to see if I can resolve the mtp issue if it happens to be at all plausible since the mtp featured in TWRP is still fairly new and has much more work to be done with it over at TeamWin.
Currently looking in to offmode charging as well. This is merely cosmetic. But would be nice to have.
xordos said:
For anyone who is lazy to backup your stock recovery, I have uploaded my stock recovery image backup here, it should be same for all our MT2-L03 phone
This is stock, only use this image if you want to revert back from TWRP to Huawei stock crappy recovery.
http://tinyurl.com/qzxkm4x
FileName: recovery_MT2L03_mmcblk0p19.img
md5sum: 35703a1fe81917cb7930ab1e9e93e499
Edit: 2nd thought, they should be same, but let's make sure. Can anyone did (or going to) backup your phone stock recovery post the md5sum of yours? The ES file explorer can calc md5sum for a file.
Click to expand...
Click to collapse
Yes, md5 are the same and fc on Win7 of your/my versions are the same.
4L0M said:
Well done everyone ! Excellent stuff.
I suppose you know what my question will be,lol, but is it feasible to be able to port this to the MT2-L05 or other Chinese models?
If it's likely to be feasible, would it be possible to have your permission to attempt a port, or do you think as the underlying processors are different
it would probably wiser to start from scratch?
Either way, good work again !
Click to expand...
Click to collapse
Hi, just saw your another post about MT2-L05 RESOURCES. I am not sure if Modding.MyMind have time or not to do this. Maybe we can do some quick test, if worked, then his build (after small update) can support L05 phone as well.
Sending you a PM.
Just flashed TWRP recovery, and it's working great!
Now we just need a CyanogenMod ROM. While I'm thinking about it, when does Android "L" officially get released? It would be nice to just jump from Jelly Bean to L.
xordos said:
Hi, just saw your another post about MT2-L05 RESOURCES. I am not sure if Modding.MyMind have time or not to do this. Maybe we can do some quick test, if worked, then his build (after small update) can support L05 phone as well.
Sending you a PM.
Click to expand...
Click to collapse
I'd be willing to be a guinea pig for the Mt2-l05 if you need more people.
I second that
Sent from my MT2L03 using XDA Free mobile app
Gir357 said:
Just flashed TWRP recovery, and it's working great!
Now we just need a CyanogenMod ROM. While I'm thinking about it, when does Android "L" officially get released? It would be nice to just jump from Jelly Bean to L.
Click to expand...
Click to collapse
L should be released sometime in October I believe, alongside the new Nexus phone and tablet.
Supposedly the HAM2 is getting an EMUI 3.0 update (KK) in November. I don't know if the US version is included though.
It's finally here! Recovery for the Fire TV 2. This is based off of TWRP and the way versions will work is I will increment the last digit in the version as I make updates. So 3.0.0-1 is my first release based off of 3.0.0. The downloads will be numbered starting at v1, and at the bottom of the post it will explain what is contained within each version.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As usual, this WILL void your warranty and I am NOT responsible for anything you do with this. Installing it properly won't brick your Fire TV, but doing stupid things with it might.
Installing this requires root. If you are not rooted, please see my FireTV 2 Recovery Installer page.
Installation
You can copy the files to /sdcard, a USB storage device, or an sdcard. I will be using /sdcard in the instructions, but you can replace it with /storage/usbotg for USB or /storage/sdcard1 for an sdcard.
Copy the zip file to your destination.
Connect adb
Code:
adb connect IPADDRESS
Open an adb shell
Code:
adb shell
Run the zip file (replace vX with the actual version you downloaded). This will automatically run su, so make sure to accept the prompt if necessary.
Code:
sh /sdcard/firetv2_recovery_vX.zip
Reboot
Upgrade
You may repeat this to upgrade to a newer version, or you can install an updated pre-rooted rom, as I will be uploading new versions of those with every version of recovery.
Notes
This includes bootmenu. For everyone that loved the old FireTV 1 bootmenu with Comic Sans, I'm sorry to disappoint you, but the Comic Sans is gone. When the FireTV boots, it will present you with the bootmenu where you can leave it alone and it will boot normally or you can select recovery and it will boot in to recovery. You do need a USB keyboard to interact with the bootmenu. To force it to boot in to Recovery, you can create a file /cache/bootmenu_recovery.
DHCP for Ethernet is enabled, and if there is enough demand I may add in wifi at some point. The IP address should show up in the top left corner.
USB storage, USB keyboard/mice, and sdcards should all work. Hotplugging works, so you should be able to plug and unplug devices as needed.
You can use a USB keyboard, mouse, or the mouse emulator to interact with it. To use a keyboard, you can use the arrow keys to move the cursor and the enter key to select buttons. Sliders don't require sliding, so you can just hit enter/click on them. To use the mouse emulator, use adb shell and then run the program mouse and follow the instructions.
ROMs
Recovery must be included in all ROMs. If you want to develop a ROM, please contact me about including recovery in it.
Kernels
The bootloader is locked and you cannot flash kernels. If you do attempt to flash a kernel, you will brick it.
Installing zips
You can push zips to /sdcard, put it on a USB storage, put it on an sdcard, or use adb sideload. Do note you need adb version 1.0.32 to use adb sideload.
Stuck in a loop?
If you cannot boot normally and keep going back to the bootmenu, wipe Cache from Wipe -> Advanced Wipe.
If that doesn't work, ensure Cache is not mounted from in the 'Mount' menu and run this from an adb shell:
Code:
mke2fs /dev/block/platform/mtk-msdc.0/by-name/cache
Source Code
You can find the source code here:
https://github.com/androidrbox/sloane-2ndinit
https://github.com/androidrbox/android_bootable_recovery
WARNINGS
It is extremely important you never reboot after a failure. This will most likely lead to a brick. If recovery is hung, you can use adb shell to run
Code:
killall recovery
to restart it
It is also extremely important to never reboot after wiping /system.
If you wind up bricking, you must use the Unbrick Image to unbrick.
Finally, thanks to everyone who has donated to me and those that helped to get me my FireTV 2.
Changelog and Downloads:
April 8, 2016 - v6 (md5sum: 79c1a3efbac86618fa2cdbb4901fbd77)
This should prevent auto flashing amazon updates.
This includes 2ndinit version dee776 and TWRP version 3.0.0-5.
February 14, 2016 - v5 (md5sum: 16c957c86f1f61160e14a55819610707)
This should fix the problems certain keyboard were having in recovery.
This includes 2ndinit version dee776 and TWRP version 3.0.0-4.
February 12, 2016 - v4 (md5sum: 15c6d375607839cac4b186a2b68b8b0d)
This includes 2ndinit version 743aa4 and TWRP version 3.0.0-3.
These are just changes related to the unbricking image. No other functional changes.
February 8, 2016 - v3 (md5sum: b39a4dbe0c19080a97f602f37fda63ec)
This includes an updated script. You can now just run the zip instead of needing the zip and the script.
This includes TWRP 3.0.0-2.
Added a reboot recovery option in addition to reboot system. Now reboot system will reboot straight in to Android. Reboot recovery will reboot to the bootmenu.
Fixed restoring backups.
This includes the same version of 2ndinit.
February 7, 2016 - v2 (md5sum: 762621104d158d7ce4010bea725f7181)
This includes an automated script.
This has the same versions of 2ndinit and recovery as v1.
February 6, 2016 - v1 (md5sum: 7be673dd24489080eacdd0ad00feda51)
This comes with 2ndinit version fe3362 and recovery version 3.0.0-1
Awesome work!
Will try immediately! Thanks for posting this on weekend
Thankyou Rbox, i just saw this & its put a smile on my face. Just one question do you need to reblock the updates after recovery & root have been installed? Thanks
deanr1977 said:
Thankyou Rbox, i just saw this & its put a smile on my face. Just one question do you need to reblock the updates after recovery & root have been installed? Thanks
Click to expand...
Click to collapse
As long as you don't wipe data, updates remain blocked.
rbox said:
As long as you don't wipe data, updates remain blocked.
Click to expand...
Click to collapse
I downloaded both the zips from the Github, im already rooted on the previously rooted software & updates are blocked, im not sure if to wait for AFTV News to do a guide or not, im clued up but not to ADB or Terminal savey so i gonna look at the readme & see if i should try it tonight? I rooted with the video guide before & it was a breeze, i know it sounds easy but want to do it right. Can you give me a little more info on connecting the ADB or Terminal please if you arnt busy?
deanr1977 said:
I downloaded both the zips from the Github, im already rooted on the previously rooted software & updates are blocked, im not sure if to wait for AFTV News to do a guide or not, im clued up but not to ADB or Terminal savey so i gonna look at the readme & see if i should try it tonight? I rooted with the video guide before & it was a breeze, i know it sounds easy but want to do it right. Can you give me a little more info on connecting the ADB or Terminal please if you arnt busy?
Click to expand...
Click to collapse
If you don't want to deal with adb, use the installer.
rbox said:
If you don't want to deal with adb, use the installer.
Click to expand...
Click to collapse
Thanks mate, looking at this now. Will it delete any data on the system? Kodi, Amazon apps or External Sd card? Thanks in advance
deanr1977 said:
Thanks mate, looking at this now. Will it delete any data on the system? Kodi, Amazon apps or External Sd card? Thanks in advance
Click to expand...
Click to collapse
Installing recovery and roms does nothing to data.
rbox said:
It's finally here! Recovery for the Fire TV 2. This is based off of TWRP and the way versions will work is I will increment the last digit in the version as I make updates. So 3.0.0-1 is my first release based off of 3.0.0. The downloads will be numbered starting at v1, and at the bottom of the post it will explain what is contained within each version.
As usual, this WILL void your warranty and I am NOT responsible for anything you do with this. Installing it properly won't brick your Fire TV, but doing stupid things with it might.
Installing this requires root. If you are not rooted, please see my FireTV 2 Recovery Installer page.
Installation
Copy the contents of the zip to /sdcard on your FireTV.
Remount /system as read-write
Code:
mount -o remount,rw /system
Make the /system/recovery directory
Code:
mkdir /system/recovery
Copy 2ndinitstub
Code:
cp /sdcard/2ndinitstub /system/bin/ext4_resize
Copy 2ndinit
Code:
cp /sdcard/2ndinit /system/recovery/
Copy the recovery ramdisk
Code:
cp /sdcard/ramdisk-recovery.cpio /system/recovery/
Remount /system as read-only
Code:
mount -o remount,ro /system
Upgrade
You may repeat this to upgrade, but it is easier to just install a new pre-rooted rom. Every update for recovery I will make a new rom.
Notes
This includes bootmenu. For everyone that loved the old FireTV 1 bootmenu with Comic Sans, I'm sorry to disappoint you, but the Comic Sans is gone. When the FireTV boots, it will present you with the bootmenu where you can leave it alone and it will boot normally or you can select recovery and it will boot in to recovery. You do need a USB keyboard to interact with the bootmenu. To force it to boot in to Recovery, you can create a file /cache/bootmenu_recovery.
DHCP for Ethernet is enabled, and if there is enough demand I may add in wifi at some point. The IP address should show up in the top left corner.
USB storage, USB keyboard/mice, and sdcards should all work. Hotplugging works, so you should be able to plug and unplug devices as needed.
You can use a USB keyboard, mouse, or the mouse emulator to interact with it. To use a keyboard, you can use the arrow keys to move the cursor and the enter key to select buttons. Sliders don't require sliding, so you can just hit enter/click on them. To use the mouse emulator, use adb shell and then run the program mouse and follow the instructions.
ROMs
Recovery must be included in all ROMs. If you want to develop a ROM, please contact me about including recovery in it.
Kernels
The bootloader is locked and you cannot flash kernels. If you do attempt to flash a kernel, you will brick it.
Installing zips
You can push zips to /sdcard, put it on a USB storage, put it on an sdcard, or use adb sideload. Do note you need adb version 1.0.32 to use adb sideload.
Source Code
You can find the source code here:
https://github.com/androidrbox/sloane-2ndinit
https://github.com/androidrbox/android_bootable_recovery
Finally, thanks to everyone who has donated to me and those that helped to get me my FireTV 2.
Changelog and Downloads:
Februrary 6, 2016 - v1 (md5sum: 7be673dd24489080eacdd0ad00feda51)
This comes with 2ndinit version fe3362 and recovery version 3.0.0-1
Click to expand...
Click to collapse
the commands are entered through adb correct......Also, once recovery is installed can I flash either of your pre-rooted roms or do I have to flash the version I'm currently on....i.e. if I'm on 5.0.4 I can only flash 5.0.4
thanks again for your great work!
dk1keith said:
the commands are entered through adb correct......Also, once recovery is installed can I flash either of your pre-rooted roms or do I have to flash the version I'm currently on....i.e. if I'm on 5.0.4 I can only flash 5.0.4
thanks again for your great work!
Click to expand...
Click to collapse
Yes adb shell. You can flash either version.
rbox said:
Yes adb shell. You can flash either version.
Click to expand...
Click to collapse
Awesome thanks rbox
Not working for me. everything is copied over and after reboot there is no menu. Amazon white logo for 5 seconds, than the colored logo and system is booted in less than 15 seconds.
aboshi said:
Not working for me. everything is copied over and after reboot there is no menu. Amazon white logo for 5 seconds, than the colored logo and system is booted in less than 15 seconds.
Click to expand...
Click to collapse
Same here. No boot menu. Reboot to recovery brings up the stock recovery as well.
dk1keith said:
Awesome thanks rbox
Click to expand...
Click to collapse
first command: mount -o remount,rw /system
in adb shell returns a mountermission denied
aboshi said:
Not working for me. everything is copied over and after reboot there is no menu. Amazon white logo for 5 seconds, than the colored logo and system is booted in less than 15 seconds.
Click to expand...
Click to collapse
retyre said:
Same here. No boot menu. Reboot to recovery brings up the stock recovery as well.
Click to expand...
Click to collapse
Both of you please run:
Code:
ls -lZ /system/bin/ext4_resize /system/recovery
dk1keith said:
first command: mount -o remount,rw /system
in adb shell returns a mountermission denied
Click to expand...
Click to collapse
You need to be root...
rbox said:
Both of you please run:
Code:
ls -lZ /system/bin/ext4_resize /system/recovery
You need to be root...
Click to expand...
Click to collapse
you mean by typing su?
dk1keith said:
you mean by typing su?
Click to expand...
Click to collapse
Yes, by typing su.
Code:
-rwxr-xr-x root shell u:object_r:system_file:s0 ext4_resize
-rw------- root root u:object_r:system_file:s0 2ndinit
-rw------- root root u:object_r:system_file:s0 ramdisk-recovery.cpio
aboshi said:
Code:
-rwxr-xr-x root shell u:object_r:system_file:s0 ext4_resize
-rw------- root root u:object_r:system_file:s0 2ndinit
-rw------- root root u:object_r:system_file:s0 ramdisk-recovery.cpio
Click to expand...
Click to collapse
Hrm... can you run
Code:
ls -l /system/bin/ext4_resize /system/recovery
also?
I just received my Ulefone Armor 3 and started customization. (http://ulefone.com/products/armor3/features.html)
So far I have came upon several issues, some of which you'll find below:
1) I have searched everywhere for a TWRP port and root method. Here's the ported TWRP 3.2.1 Recovery from Ulefone Power 5 which works for Ulefone Armor 3/3T. Here's the original recovery (haven't tested it).
2) Disable Ulefone Armor 3 encryption: Here's the link.
3) Google Play keeps crashing. Follow the steps here.
4) Booting now shows with small letters the following message:"Orange State, the device is unlocked and cannot be trusted. Booting will continue in 5 seconds". I don't want my device to show this message and wait 5 seconds, is there a way to do this? The message is shown because I have unlocked the bootloader.
5) TWRP backup (the one I am using, ported from Ulefone Power 3 or Armor 5) breaks when backing up modem partition and stops the backup with error. The only way so far is to take the backup deselecting the modem folder.
6) FolderMount needs a specific SU binary, which I cannot flash at all (SU by chainfire). Tried an old binary in order to update it later, but still no success. Is there any alternatives that work with Magisk?
7) Xposed installer (Gravitybox module). Many options don't work, but some of them do work. The same with Magisk Modules. I guess I have to experiment some more to see what works and what not.
8) Nova Launcher: Is it my idea or this really lags the device at start? Any good similar alternatives (mostly interested in widget resizing)?
Thank you all
A. How to install adb and Fastboot Driver
B. How to install VCom Drivers and the Vcom installer
C. How to unlock the bootloader, Install TWRP, Root, Disable Encryption
I have tested all the above myself and I have confirmed that the procedures work.
Photo Samples
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
hi , sorry i cant help much , but i also got that phone , pretty locked down on anything you try to touch , some devlopper option just not accecible , some basic option not avaiable and hidden behind encryption to the os/rom?
mine doesnt even have a recovery menu , i get a no command logo or error of acces , cant seem to be able to root it by myself ,
the most information i got was from a russian forum were every links are down and i only speak google translate russian so im hitting some heavy wall here and there too , cant even register .
im waiting for some random site i didnt know about provide a mirror link for the twrp , if i can even install it .
iv got the rom at least here
but iv got a lot of reading to do before im able to do anything productive here . im usualy a user not a devloper . its the first time i have a phone i really wanted but didnt have a huge fanbase to help me be lazy .
edit: also the phone is really nice , been able to go for 3 days before getting to 15 % , 2 hours of walking playing a 2d online game on lte with bluetooth was from 100% to 89 . speaker are incredible , nice screen , hard as reinforced metal bar , almost a pound in weight , good wifi , lots of give and take on whats avaiable as options , lots of locked stuff. i feel lots of processing is done by various encryption and the cpu is not at is full potential . gpu is basic . a good custom rom and kernel from someone who know what he or she is doing would be the most welcome , as lots of stuff seem to be behind wall also security patch from july .
I got it to work! I will soon post everything as I gather it from various sources.
There should be a link for dm verity opt for disabling encryption and google play issue that OP is having.
I did full backup of my ROM to retain my IMEI only to find that the Russian forum pulled the link for TWRP.
Im anxiously waiting for the last poster to provide new links or wait for a mirror download on Rom Provider website. Cheers:fingers-crossed:
Heres address //romprovider.com/2018/12/ulefone-armor-3-armor-3t-root-twrp/#Root_twrp_Ulefone_Armor_3_Armor_3T
NMaverick said:
I just received my Ulefone Armor 3 and started customization. (http://ulefone.com/products/armor3/features.html)
So far I have came upon several issues, some of which you'll find below:
1) I have searched everywhere for a TWRP port and root method. So far there's only an old TWRP port that has limited functionality.
The problem is mainly because Armor 3 has Oreo 8.1 and it has forcefully encrypted the data partition. When I start TWRP a password prompt request is shown that cannot be bypassed. I am using the password I had set for my device, but even if I don't set a password or fingerprint the data partition is shown encrypted (size 0). Can anyone port the latest TWRP recovery?
2) (Related to 1) Was anyone successful in disabling Ulefone Armor 3 encryption? The only way to flash Magisk v18 is to factory reset, reboot to TWRP and flash it, but this does not disable encryption.
3) Google Play keeps crashing, impossible to search and install any app. I have tried uninstalling, erasing data and cache, disabling, re-enabling (original app starts) and everything works fine, but as soon as it updates itself the app crashes again.
4) Booting now shows with small letters the following message:"Orange State, the device is unlocked and cannot be trusted. Booting will continue in 5 seconds". I don't want my device to show this message and wait 5 seconds, is there a way to do this? The message is shown because I have unlocked the bootloader.
5) TWRP backup (the one I am using, ported from Ulefone Power 3 or Armor 5) breaks when backing up modem partition and stops the backup with error (cannot find file). I hope this will get fixed when the latest TWRP is successfully ported. (I found some instructions here https://forum.xda-developers.com/android/general/guide-porting-twrp-source-t3843473 but I cannot follow them correctly).
6) FolderMount needs a specific SU binary, which I cannot flash at all (SU by chainfire). Tried an old binary in order to update it later, but still no success. Is there any alternatives that work with Magisk?
7) Xposed installer (Gravitybox module). Many options don't work, but some of them do work. The same with Magisk Modules. I guess I have to experiment some more to see what works and what not.
8) Nova Launcher: Is it my idea or this really lags the device at start? Any good similar alternatives (mostly interested in widget resizing)?
Thank you all
I will update with any new problems and solutions here.
P.S. I am using the smartphone for over 24 hours straight the last two days with a lot of rebooting, screen and wifi always on and it is only at 50% battery from a fully charged battery after a 45 day journey to me. Amazing!
Click to expand...
Click to collapse
Can you give me link for twrp?
As for decrypting, check the latest post and link from ROM Provider. I gave an address not allowed to post links yet.?
no twrp yet . files and tools to reflash in case of problems ;
https://yadi.sk/d/T6G5DkTZFKCgcQ mirrors ; https://drive.google.com/open?id=1-4rLuvTaxHY7aMAhOPrjs-xtThyDwPu6
LINK IS UP : http://www.mediafire.com/file/gd4ixxzo5jl9a8a/armor+3_3T.rar TWRP FROM ROMPROVIDER didnt test yet .
I have updated the description with the solutions. I have also checked the procedure myself and it works fine.
NMaverick said:
I have updated the description with the solutions. I have also checked the procedure myself and it works fine.
Click to expand...
Click to collapse
thank you very much , will try in the next few days .
edit ; scatter file not loading keep getting an error , gotta have to try the other method
Tasker: Notification Leds for Tasks (Update since "tasker, Notification, Set Light" stopped working)
There seem to be 4 Notification Leds in this device, the first of which is "dummy". Here are the color combinations for turning them on and off in Tasker (Code>Run Shell, with Use-Root to "on". I have used them to see when "Car Mode" is enabled when I am in my car (I use an NFC tag to turn it on).
- Task-Type "Code>Run Shell", set Use-Root to "on",
command: echo 64>/sys/class/leds/mt6370_pemu_led2/brightness/brightness (to turn on led 2 as Green)
command: echo 64>/sys/class/leds/mt6370_pemu_led3/brightness/brightness (to turn on led 3 as Blue)
The result is Light Blue.
To turn off lights you need to enter both commands:
command: echo 00>/sys/class/leds/mt6370_pemu_led2/brightness/brightness (to turn off led 2)
command: echo 00>/sys/class/leds/mt6370_pemu_led3/brightness/brightness (to turn off led 3)
Led names (under /sys/class/leds/) are the following:
lcd-backlight, mt6370_pmu_bled, mt6370_pmu_led1, mt6370_pmu_led2, mt6370_pmu_led3, mt6370_pmu_led4
Color combinations are these (1 means 64 in the commands and 0 means 00. I am not sure if putting 01 works):
Led 1 Led 2 Led 3 Led 4 Color
0 0 0 0 Off
0 0 0 1 Red
0 0 1 0 Blue
0 0 1 1 Blue-Red
0 1 0 0 Green
0 1 0 1 Light Green
0 1 1 0 Light Blue
0 1 1 1 Light Blue
1 0 0 0 Off
1 0 0 1 Red
1 0 1 0 Blue
1 0 1 1 Blue-Red
1 1 0 0 Green
1 1 0 1 Light Green
1 1 1 0 Light Blue
1 1 1 1 Light Blue
Thank this post
jordanvachon said:
thank you very much , will try in the next few days .
edit ; scatter file not loading keep getting an error , gotta have to try the other method
Click to expand...
Click to collapse
Try generating your own firmware so you retain your own imei. There is a great tutorial on "Hovatech Forum". Follow instructions for your chipset. It will need to be put in manually with drop down menu. Super easy and Im a noob. Ive already reflashed stock several times due to encryption errors and nvram issues.
Cant figure out why modem cant be backed up with twrp. Otherwise fine. Cheers
How to remove the annoying Video Recording sound
-----------------------------------------------------------------
With root access and e.g. ES Explorer just rename /system/media/audio/ui/VideoRecord.ogg to e.g. VVideoRecord.ogg
Immediate effect, no restart needed.
Does any of you have the 3T version? If so, can you make an .apk of the Intercom software and upload it? From what i understand, all the hardware for walkie-talkie is included in the 3 version, they just left out the software, which you can't download anywhere. I'd like to test installing it on my 3 version
i just got my ulefone armor 3t in yesterday and have been reading up on it. so far i have install twrp and magisk but when i boot into recovery it asks me for a password to decrypt. i cant get my pin or password to work.
i made a copy of the intercom apk but cant post a link right now
Badtoyz said:
i just got my ulefone armor 3t in yesterday and have been reading up on it. so far i have install twrp and magisk but when i boot into recovery it asks me for a password to decrypt. i cant get my pin or password to work.
i made a copy of the intercom apk but cant post a link right now
Click to expand...
Click to collapse
I'd be pretty interested in trying the intercom APK on my Armor 3 as well.
So far I have got it rooted with magisk and have exposed framework installed. All seems to e going well
That TWRP doesn't work with encrypted userdata partition - known issue. All we can do is to trade "security?" for functionality and decrypt userdata partition - all data will be lost - make Titanium and int.sd backup
Format (not wipe !) userdata partition under twrp or use adb/fastboot and w/o booting into system flash modified /vendor/etc/fstab_mt6763 with disabled force_encryption flag (disable_encryption.zip)
Operations involve stock recovery (i.e. factory reset, ota update) end up with "recovery loop" if twrp installed. if that happened - restore "para" partition or flash "para" from rom image via spflashtool.
("para" partition contains last issued reboot flag)
Links on russian 4pda forum are not dead - you have to be registered and logged in to be able to download.
A'm pretty sure that armor 3 has no intercom module (hardware) but intercom software is in intercom.zip (twrp flashable /system/app/intercom folder)
Almost nothing about UI customization in 8.1
I've found only one app that really works (very limited - see pics)
it is "Pluvius" ($2)
Updated ROMs
Armor 3
Give me one reason to mess with it.
"If it ain't broke, don't fix it."
I always forget - it's 8.1 and chances to install something pushing it into /system are low. I tried "miravision" from new ROM and that folder just disappeared after reboot if installed in /app and sfter pushing it into priv-app I had to restore /system
zelipukin said:
That TWRP doesn't work with encrypted userdata partition - known issue. All we can do is to trade "security?" for functionality and decrypt userdata partition - all data will be lost - make Titanium and int.sd backup
Format (not wipe !) userdata partition under twrp or use adb/fastboot and w/o booting into system flash modified /vendor/etc/fstab_mt6763 with disabled force_encryption flag (disable_encryption.zip)
Operations involve stock recovery (i.e. factory reset, ota update) end up with "recovery loop" if twrp installed. if that happened - restore "para" partition or flash "para" from rom image via spflashtool.
("para" partition contains last issued reboot flag)
Links on russian 4pda forum are not dead - you have to be registered and logged in to be able to download.
A'm pretty sure that armor 3 has no intercom module (hardware) but intercom software is in intercom.zip (twrp flashable /system/app/intercom folder)
Almost nothing about UI customization in 8.1
I've found only one app that really works (very limited - see pics)
it is "Pluvius" ($2)
Click to expand...
Click to collapse
Thnx for files.
Any way to ADB install Intercom? Don't really want to hack with TWRP quite yet.
yes, I think, unzip intercom folder and push it to /system/app
permissions:
folders - 0755
.apk & .*dex - 0644
And I just noticed libs (.so) in /lib/arm64 are not actual files but links (see pics)
so if you don't have these libs in /system/lib64 I attached them.
You can create links or just put lib files in /system/app/lib/arm64
is there antenna socket in Armor 3 ? It's kinda not safe (for radio chip) to turn radio on w/o antenna connected. though, I did it several times accidently (have that ptt button remapped now)
I always forgot - it's android 8.1 and chances to install something in /system are low I tried to push "miravision" from new ROM, but that folder just disappeared after reboot if installed in /app and after I pushed it to /priv-app I had to restore /system
zelipukin said:
yes, I think, unzip intercom folder and push it to /system/app
permissions:
folders - 0755
.apk & .*dex - 0644
And I just noticed libs (.so) in /lib/arm64 are not actual files but links (see pics)
so if you don't have these libs in /system/lib64 I attached them.
You can create links or just put lib files in /system/app/lib/arm64
is there antenna socket in Armor 3 ? It's kinda not safe (for radio chip) to turn radio on w/o antenna connected. though, I did it several times accidently (have that ptt button remapped now)
I always forgot - it's android 8.1 and chances to install something in /system are low I tried to push "miravision" from new ROM, but that folder just disappeared after reboot if installed in /app and after I pushed it to /priv-app I had to restore /system
Click to expand...
Click to collapse
I'll have a go at installing intercom tomorrow. Pretty sure I should have an antenna around that'll fit!