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...
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?
So now that we have found the leaking crack in the bootloader and proved it's usefulness fat-tire and others are going to start work on a couple of key projects that I could use a little help on.
This will also keep conspiracy theorists at bay who call me "extremely low IQ male rooster with social development issues" (Also I have no pies)
Here is how i see the next steps:
Strip down uboot (or other bootloader) and teach it boot from it's own partition.
For example install 2nduboot in /boot, hijacking the signature check and then setting a 1MB offset to look for the real, unsigned boot.img. Repeat for recovery.
This is the real hold up and why there is nothing to "flash" as of yet. (still no pies)
Finish CWM. 100% done.
Completed. See recovery.img here: http://forum.xda-developers.com/showthread.php?t=1440645
Work on CM9 for both SDcard and internal booting
See Below
So instead of insulting me. I am looking for some people to help work on these things. We are going to be doing this is private respostories and a private irc channel due to the stupid reward that is out there.
If you are wanting to work with me. The reward (if we get done by the 22nd) goes to Doctors Without Borders. This is where we should all be donating. No negotiating.
So PM me or come to #nook-tablet @ freenode
Reserved
Bootstrap-loader (Goal #1)
Here is some more details on my thoughts on bootstrapping /boot and /recovery to boot unsigned images.
Today we are only bootstrapping with a 2nduboot on the sdcard. This would allow custom kernels and ramdisks on emmc for things like easier root, overclocking, CM9, CWM, etc
So my thoughts were to bundle together a bootstrap bootloader (uboot obviously will work, but another project that was used for CM on the touchpad called, moboot, may be a nice option to get menus and such) and the unsigned kernel+ramdisk into one binary blob. The unsigned boot.img will be at a well known offset. This will allow us to act as "stock" as possible and do things like. Replace just the kernel with an OC one. Replace just the ramdisk with ro.secure=0, etc.
{
"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 would also allow us to completely replace recovery with CWM.
Current Status: Fattire working on a meny for SD booting. Still discussing best way to do internal booting although using bauwks bootstrap uboots will work for now for emmc but incorporating a possible menu is being looked into. Low Priority
CM9 (Goal #2) Inprogress
There is a lot here and I am going to go at it pretty methodically adding one feature at a time. So graphics first, then key/touchscreen, usb gadget, etc.
There is a number of kernel changes that need to be done:
Find the closest git repo/branch/revision from omap zoom to apply B&N changes as a patch.
This will allow us to a) have revision history b) allow merging up to 3.0 easier
This is pretty important and if anyone is handy with git and knows of an easy way. Let me know
Backport key changes (fattire probably has this already done)
Backport usb gadget
Backport a hwrenderer compatable sgx drives (maybe move to a 3.x kernel at this point instead)
Backport
Current Status:
Teasers:
Wow. Thanks nemith for all the info. I will work with you and 100% will give the donation to them (verbal and writen agreement). From when I was building CWM on the GNex I remeber having to change one of the values in the .mk file to allow for adb.
Hi nemith,
That is a nice plan which aligned with my plan for modding u-boot to boot off the internal partitions .
I pushed some changes into my git repository on github which looks like #1 on your list. git://github.com/bauwks/Nook-Tablet.git
So for example, to build a 2nd u-boot that will install to the internal flash partition "recovery" and try to load the next stage at offset 256K of the internal "recovery" partition one would do:
(cd to u-boot directory and switch to second-uboot branch first, then)
PATH=/usr/local/arm-2010q1/bin:$PATH
make nt2ndboot_irecovery
make
./tools/build_nt_2ndboot_img.py -f -o irecovery.img u-boot.bin
dd if=/dev/zero of=irecovery.img bs=1 seek=262143 count=1 # pads to 256K size
Then, you can cat your irecovery.img and your real recovery.img together and blast them onto the recovery partition.
There is also a nt2ndboot_iboot config that will do the same, but is used on the "boot" partition.
I have only done minimal testing with the recovery partition 2nd uboot. I'm about to write a full image onto my recovery partition and see what happens
Update:
I flashed my recovery partition with irecovery.img + a random twrp2 image I had and it boots solely from internal flash! No more SD card needed, no more USB connection needed, just holding down power+N
nemith said:
So now that we have found the leaking crack in the bootloader and proved it's usefulness fat-tire and others are going to start work on a couple of key projects that I could use a little help on.
This will also keep conspiracy theorists at bay who call me "extremely low IQ male rooster with social development issues" (Also I have no pies)
Here is how i see the next steps:
Strip down uboot (or other bootloader) and teach it boot from it's own partition.
For example install 2nduboot in /boot, hijacking the signature check and then setting a 1MB offset to look for the real, unsigned boot.img. Repeat for recovery.
This is the real hold up and why there is nothing to "flash" as of yet. (still no pies)
Finish CWM. 100% done.
Completed. See recovery.img here: http://forum.xda-developers.com/showthread.php?t=1440645
Work on CM9 for both SDcard and internal booting
Started on this one as well. I can boot but haven't got adb working and no graphics (expected at this point)
So instead of insulting me. I am looking for some people to help work on these things. We are going to be doing this is private respostories and a private irc channel due to the stupid reward that is out there.
If you are wanting to work with me. The reward (if we get done by the 22nd) goes to Doctors Without Borders. This is where we should all be donating. No negotiating.
So PM me or come to #nook-tablet @ freenode
Click to expand...
Click to collapse
A bit on UI, cleanup, and various boot scenarios
Bauwks.. cool, glad emmc is is a go.
Current Status: Fattire working on a menu for SD booting. Still discussing best way to do internal booting although using bauwks bootstrap uboots will work for now for emmc but incorporating a possible menu is being looked into
Click to expand...
Click to collapse
UB2 update from me: A fruitful night with lots of fun enhancements, some modest UI feedback, and a sprinkling of safety/sanity fixes and other tweaks. SD and emmc options should be more convenient/consistent now, with recovery selection effectively handled by UB2 not UB1 (though power+n will remain an option obviously). I'll let nemith elucidate.
Also, bauwks, nemith suggested, and I thought it wasn't a bad idea, to expand to 512K instead of 256K as a partition buffer just to be on the safe side. I think he said the partitions are 16MB in all, so a little extra padding for possible future bloat is probably not a bad thing to have-- especially if there's gonna be a 2nd-bootloader "standard" (ie, so that any UB2 or menu will work in the future...) now's the time to decide- what do you think? Is 512 reasonable? Adding a single new .rle pushes you over. (We actually can eliminate two .rles right now, as the "charging" and "plugin" ones are effectively useless. I got rid of them, then added two more for feedback so I'm back to even, though eventually I'll probably get rid of them too.) What are your thoughts?
Considering I don't have an NT and I'm working blind here with nemith testing... I think this could wind up pretty nifty.
bauwks said:
Update:
I flashed my recovery partition with irecovery.img + a random twrp2 image I had and it boots solely from internal flash! No more SD card needed, no more USB connection needed, just holding down power+N
Click to expand...
Click to collapse
Nice!!!!
I was loathing the idea of having to keep a bootable sdcard in the thing forever. From my understanding of this, this hardware is now "cured", and just needs a special blob appended to the front of the boot and recovery partitions, eh?
dhkr234 said:
Nice!!!!
I was loathing the idea of having to keep a bootable sdcard in the thing forever. From my understanding of this, this hardware is now "cured", and just needs a special blob appended to the front of the boot and recovery partitions, eh?
Click to expand...
Click to collapse
Yeah. Or more specifically, everything in those partitions will need to be shoved over by a set amount to make room for UB2.
fattire said:
Also, bauwks, nemith suggested, and I thought it wasn't a bad idea, to expand to 512K instead of 256K as a partition buffer just to be on the safe side. I think he said the partitions are 16MB in all, so a little extra padding for possible future bloat is probably not a bad thing to have-- especially if there's gonna be a 2nd-bootloader "standard" (ie, so that any UB2 or menu will work in the future...) now's the time to decide- what do you think? Is 512 reasonable? Adding a single new .rle pushes you over. (We actually can eliminate two .rles right now, as the "charging" and "plugin" ones are effectively useless. I got rid of them, then added two more for feedback so I'm back to even, though eventually I'll probably get rid of them too.) What are your thoughts?
Click to expand...
Click to collapse
Hi fattire,
I guess it depends on how you look at it. I was looking at it like: an "image" is a concatenation of a 2nduboot and an Android kernel/ramdisk. To install, one would just dd the "image" to a partition. Then the 2nduboot wouldn't have to have a fixed max size that is predefined, if it needs to be increased you would just modify the partition offset in the bootcmd to load the stuff after the new size. It would also make updating the 2nduboot easier because it's part of the "image".
But, I have not worked with Android before so I do not have expertise in how images are typically deployed. If you always want the real image to be at a fixed offset then increasing to 512K makes a lot of sense. You are free to use the solution that best fits your problem.
By the way, the offset of the real image doesn't have to be a power of 2, it only has to be a multiple of the MMC sector size (512 bytes).
I can't really offer much as I am no android developer. I can modify basics and work thinsg out through educated trial and error but most of what you guys have been on about has been way out of my league. If it makes any difference I have 2 NTs one of which is brand new in a sealed box just sat waiting for the correct time to bother getting it out to play.
I'm quite happy to do testing, tweak things and do what I can where required.
Not sure what happened about the reward thing but as has been said before I think giving it to a good cause is a very decent and honest thing to do.
Doing it and donating the 'winnings' to a good cause is a far better idea and I commend you for following that route. Those that do it solely for the money aren't doing it for the reasons that I think XDA exists and from what I've seen before often get their money out of blatantly using other members hard work to make themselves look good, there always seems to be a lot of sitting on the fence then diving in at the last second and releasing something as their own when most of it isn't.
Anyway, enough babbling from me! Keep up the good work and when you think I can be of any help I will be more than happy to chip in where required.
bauwks said:
Hi fattire,
I guess it depends on how you look at it. I was looking at it like: an "image" is a concatenation of a 2nduboot and an Android kernel/ramdisk. To install, one would just dd the "image" to a partition. Then the 2nduboot wouldn't have to have a fixed max size that is predefined, if it needs to be increased you would just modify the partition offset in the bootcmd to load the stuff after the new size. It would also make updating the 2nduboot easier because it's part of the "image".
But, I have not worked with Android before so I do not have expertise in how images are typically deployed. If you always want the real image to be at a fixed offset then increasing to 512K makes a lot of sense. You are free to use the solution that best fits your problem.
By the way, the offset of the real image doesn't have to be a power of 2, it only has to be a multiple of the MMC sector size (512 bytes).
Click to expand...
Click to collapse
Presumably, the partition table is write protected along with the xloader and bootloader partitions, right? Now I guess that would be by power-on-write-protect rather than permanent write protect (which would obviously lock even THEM out of it...). Stupid question, but has anyone checked if the eMMC reset pin is connected to a test point on the board or on some gpio we can manipulate? I'm just wondering if we can pull something like a gfree on this sucker, especially since the eMMC is practically identical to the one on VISION/GLACIER/ACE, just larger. Bounce that reset pin and reinitialize the eMMC with write protect disabled, replace xloader and uboot with proper uncrippled ones, and BE GOD.
Progress on CM9 from @AndroidNemith http://twitpic.com/86hx6m - Twitter
dhkr234 said:
Presumably, the partition table is write protected along with the xloader and bootloader partitions, right?
Click to expand...
Click to collapse
Nope.
dhkr234 said:
Now I guess that would be by power-on-write-protect rather than permanent write protect (which would obviously lock even THEM out of it...)
Click to expand...
Click to collapse
Nope.
dhkr234 said:
Stupid question, but has anyone checked if the eMMC reset pin is connected to a test point on the board or on some gpio we can manipulate? I'm just wondering if we can pull something like a gfree on this sucker, especially since the eMMC is practically identical to the one on VISION/GLACIER/ACE, just larger. Bounce that reset pin and reinitialize the eMMC with write protect disabled, replace xloader and uboot with proper uncrippled ones, and BE GOD.
Click to expand...
Click to collapse
This is not the g2. It's not a write-protected emmc and a power cycle of the emmc will do nothing. I appreciate the enthusiasm, but you're coming to this very late.
More rambling...
If I'm not mistaken, the way you're suggesting is UB2 would be a prepended portion of the boot and recovery images as part of a "package", and this is how we were already discussing doing it in the cm9 build system-- this also matches in effect how Nook Color CM7 distros work-- the bootloader is actually re-installed with every update.zip (to enforce compatibility as newer versions of Android require newer u-boot).
However, I was considering that some people want to swap various u-boots in and out of existing boot or recovery partitions without necessarily having to push aside the rest of the image to make room. So if they're thought of as a unit, it makes total sense to do it as you suggest- but if UB2 is something that can be replaced (or updated) independently, then maybe a standard "buffer" size would be more appropriate.
We've talked about a few ideas- if a simpler boot menu is used to replace UB2, or a redirection to "see other partition for bootloader"... then it could be 512K (or whatever) mostly wasted... which may not be a big deal either.
Anyway, just typin' out loud. Lots of options, and no "right" way to do it.
bauwks said:
Hi fattire,
I guess it depends on how you look at it. I was looking at it like: an "image" is a concatenation of a 2nduboot and an Android kernel/ramdisk. To install, one would just dd the "image" to a partition. Then the 2nduboot wouldn't have to have a fixed max size that is predefined, if it needs to be increased you would just modify the partition offset in the bootcmd to load the stuff after the new size. It would also make updating the 2nduboot easier because it's part of the "image".
But, I have not worked with Android before so I do not have expertise in how images are typically deployed. If you always want the real image to be at a fixed offset then increasing to 512K makes a lot of sense. You are free to use the solution that best fits your problem.
By the way, the offset of the real image doesn't have to be a power of 2, it only has to be a multiple of the MMC sector size (512 bytes).
Click to expand...
Click to collapse
aversion of single-point-of-failure
I'd like to recommend, to avert the Single Point of Failure, a manditory and automatic backup of the /ROM/ partition. Since you're developing the first custom kernel, there will be a lot of work based upon yours for this device.
This can be handled in the init scripts. after /ROM/, /system/ and /sdcard/ mount. If the /ROM/ folder is available and there is no backup, make one. This simple step can save alot of grief in the future in case of damage.
Untested code:
Code:
#! /bin/sh
ROMBACKUPDIR="/sdcard/backup/ROM/";
BACKUPFILE=$ROMBACKUPDIR"ROMPARTITION.img";
TESTFILE="/ROM/NAMEOFANYFILE";
ROMPARTITION="/dev/block/***";
busybox test ! -e $ROMBACKUPDIR && mkdir --parents $ROMBACKUPDIR;
#no backup detected, so make one.
busybox test -f /ROM/$TESTFILE && busybox test ! -f $BACKUPFILE && busybox dd if=$ROMPARTITION of=$BACKUPFILE;
where ***=the ROM partition on your kernel and NAMEOFANYFILE=the name of any file on the /ROM/ folder
Whomever is building the AOSP!!!
Be careful with the ICS 4.0.3. There are alot of issues with the way the AOSP market place is working with it. The 4.4.3 Market has a tendancy to crash continually. Might be worth building ICS 4.0.2, and using that to elimitate all the problems whe can.
I have a mac g5 on public ip space and a NT that I can plug in if any dev's want to use that.
other than that, I'm another tester for y'all.
Loglud said:
Adam,
I own the nooktabletdev.org wiki, I will add all of those into it, or allow you an admin account. Then we can just point to there.
Click to expand...
Click to collapse
I've begun said post here: http://forum.xda-developers.com/showthread.php?p=21371828
Congrats to everyone who cracked it finally
I can say with 90% surity that You can recover a junked ROM partition or for that matter a fully junked eMMC, for the simple fact that it gives other pheriperals a chance before booting into eMMC (cannt say 100 % by myself immidiately now, because have been busy with other stuff at work over the last week, so my memory FIFO wrt my experiments on NookTab is bit blurry now).
AdamOutler said:
I've begun said post here: http://forum.xda-developers.com/showthread.php?p=21371828
Click to expand...
Click to collapse
Ahhhh, documentation!!!!
But seriously, thanks very much for that.
And FYI: Probably the best place to keep documentation is right here: http://forum.xda-developers.com/wiki/BN_Nook_Tablet -- in the xda device wiki.
Hey guys this just made you famous on the interwebz...
http://www.engadget.com/2012/01/14/nook-tablet-bootloader-bypassed-android-4-0-takes-its-first-ste
Good jorb!
Proudly presenting:
4EXT Recovery Touch
{
"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"
}
brand new user interface: "4EXT UI"
touchscreen only
extremely fast
much more useful features than the already feature-packed 4EXT Recovery Classic v2.2.7 RC5 (see 2nd post)
4EXT SmartFlash for s-on devices
optionally save space by configuring recovery to exclude /cache from backups
you can configure recovery to save even more space by excluding dalvik-cache from backups
calculates real space needed to complete a backup to save you from troubles
detects your local time zone
-> correct time is used for backups you start from within recovery
allows you to change md5sum check behaviour
displays and updates your current battery level in real time
scrollable texthistory (drag down the statusbar)
built-in interactivity (yes/no questions) for updater-scripts
built-in screenshot functionality
extensive theming capabilities!
nearly ALL YOU SEE is changeable.
"worker bar": create your own custom animations, there are (nearly) no limits! Use any shapes/sizes/animations et.c.
extra low cpu needed for that: absolutely no negative impact on backup/restore speed.
async UI rendering for optimal performance for the "heavy tasks" like backup/restore
backups even faster than with usual recoveries.
.. explore the new interface to see more
includes all features of 4EXT Recovery Classic
About 4EXT SmartFlash
This is a new feature that allows recovery to flash your boot partition just like as if you were s-off.
Credits and thanks to Team Win and Dees_Troy for their commitment to the community, for their amazing idea with the Dumlock and for extra contacting me only to offer that I may use it.
You guys really rock!
SmartFlash is a different approach to Team Win's HTC Dumlock
Just use your recovery like you would if your device were s-off
No preparations needed, other than telling the recovery that your device is actually s-on
This is done when you install recovery and answer the question that you are s-on with "yes"
You can also change that setting later on via RecoveryControl -> Recovery settings, or by editing 4ext.prop manually
Recovery will autodetect any changes done to "boot" and only attempt to flash your boot partition if it was really changed
This even reduces unnecessary writes to "boot" when for example a new rom uses the same kernel as your previous one
Before updating your boot partition, recovery will always backup your boot partition to your sdcard just for the case something goes wrong
Only the 4 latest boot images are stored, older ones will be removed automatically to prevent taking up too much space.
In case you want to enable or disable that feature temporarily, you can use a switch inside the tools menu in recovery
How it works:
Recovery will detect any requested changes for your boot partition
When you reboot out of recovery, it will prepare updating your boot partition on next rom start
This means that your boot partition will be updated when you see the HTC Splash screen, followed by 1 reboot
So basically the only visible difference to when you are s-off is one additional reboot, which takes only a few seconds.
Recovery is NOT flashed to boot and boot is also only flashed once/update
Recovery will only attempt to flash your boot partition if it was really changed
Limitations:
Radio and firmware:
Usually those are flashed via bootloader flashable zips or fastboot even on devices that are s-off.
But in case you wondered: this does not enable you to flash new firmwares or radio images via recovery.
SmartFlash needs a working kernel to be able to upgrade your boot partition.
It cannot work in case your current kernel is incompatible with your device/hboot or has been wiped outside of recovery.
For example you cannot erase boot via fastboot and then start up recovery to update your kernel.
However you don't need a working rom to use it.
The only requirement is that your current kernel is able to start (this happens before you see the boot animation) and that your system partition is mountable.
INFO:
For App and Rom devs:
Make use of the Recovery Interface Api provided by the (free and paid) 4EXT Recovery Apps to push updates/mods/addons for auto installation.
Very easy to use and to integrate into Apps or even shell scripts.
Please check 3rd post.
Info regarding 4EXT Recovery Touch and its yesno feature, or any interactive installer scripts you might already use, please see 3rd post.
Themes for 4EXT Recovery Touch:
Official 4EXT Recovery Themes Index & Discussion Thread
Download
All downloads are available through 4EXT Recovery Updater.
It's free, no ads, no tracking, no nothing, don't worry
..and of course via 4EXT Recovery Control
This ensures that your downloads are ok by automatically verifying md5sums and that known issues and changelogs are easily accessible
When you install or download a recovery via the app it makes sure that your recovery config is correctly set up.
It allows to automatically setup your time zone for recovery.
You can use it to get notified about updates regarding your recovery version
You can configure it to get notified in case any critical bugs have been discovered of the recovery version you currently have installed.
It allows me to update known issues/changelogs immediately and to quickly pull a newly released version if there were reports about critical bugs
You can also use it to just download a recovery.zip containing the image. The download will be automatically verified for correct md5sums!
By default the app also saves the recovery.img you flash on your sdcard,
so you can use it to flash the recovery via fastboot in case you need to do that one day.
4EXT Recovery Control
Free version: Recovery Updater
Fully featured: Recovery Control
For a list of its many features, visit www.4ext.net
Some examples :
Very easy to use, but also includes an extensive set of features available via "advanced mode"
Comfortable configure all settings of recovery
Calculate the space needed to create a new full or advanced backup
So you can make sure the backup will succeed before even rebooting into recovery.
Advanced Backups: While you are selecting / deselecting partitions, it will display and update the currently needed space to complete that custom backup set.
Identifies and adds your romname so you don't need to type so much when chosing a meaningful name for your backup
When you restore a backup, the app does the md5sum check instead of the recovery
This ensures that you know whether the restore process will succeed before even rebooting into recovery
Flash as many zip files you want in one go
Automatically calculate and display the md5sums of all zip files you are going to flash
Check your backups' health to ensure they will restore later when you need them, by verifying their md5sums!
Optionally, but highly not recommended:
If md5sums don't match but you really need that backup badly, you might want to restore it anyway.
You can you this app to fix the md5sums of a given backup
As an example, the following is possible to do in just one session:
Restore a backup, set to create a backup / advanced backup before the restore,
format all partitions with a file system of your choice before the restore process starts,
flash additional zip files afterwards, fix permissions and select to stay inside recovery or to reboot automatically once all actions are complete.
Much, much more! See www.4ext.net
Big thanks to craacK for a lot of great icons!
Thanks:
Big thanks to DolphiCom for all the graphics, the worker bar and a whole lot of great ideas and to the many great testers who spent all day/night testing, reporting bugs, making suggestions, helping with decisions:
Jotha, craacK, Patrics83, Euphorie, Mike1986, Whiskey103, ptr_hamilton, Lizard, TheUntouchable
Big thanks to Jotha and Whiskey103 for testing the themes features creating and their first themes for 4EXT Recovery Touch.
Special thanks to Dees_Troy who joined #4ext several times, just to tell me about important things he assumed I didn't know (and he was right! )
Also Big thanks to all the donators to 4EXT Recovery and everyone who has bought 4EXT Recovery Control! Without you I wouldn't be able to spend as much time with the project:
SO A HUGE THANK YOU!
FRANKIE-BOY, BENJAMINNZIS, DESPERANTO86, SYRAKUS, VRC8883, FISHA21, ZJXPOT, ZEEKIZ, A USER, PHILOS64, STEVEATHOME, PREACHER65, BEN_PYETT, HAWST, ANIT77, ULTRA DROID, PTR_HAMILTON, BEANBEAN50, SEBASTIAAN15 and LOVEBOATCAPTAIN
Of course BIG THANKS to KOUSH for ClockworkModRecovery!
Without him, 4EXT Recovery wouldn't exist!
Thanks a lot to the following users for initial testing for specific devices :
SPEEDYCARV, PTR_HAMILTON, JAMESCLINTON, SNOWBOARDKID503, MJESSE81, SEBASTIAAN15, THEUNTOUCHABLE, BMONSTER, ANDREIGHERGHE, PRESTON74, MADKAI, YASIR, PLAYPETEPP
IPERZAMPEM0, THESHAWTY, JBBANDOS, TAZMAN1963, GREGFERNS and INCREDULOUS
Special thanks to Invasion2 and Stlouie65 for spending at least 10 hours of their time helping me debug a really nasty issue on the myTouch 4G!
Also thanks for obtaining calibration values for the touchscreen:
Mjesse81,
Speedycarv,
Wolfepakt
Jaibar
Jayallen1980
Stlouie65
Invasion2
PacerguyDon
Ben_Pyett
Dargocitfer
Darknessrise1234
Lizard
Azazel71
Features of 4EXT Recovery Classic:
(Use 4EXT Recovery Control or Recovery Updater for complete Changelogs and Known issues!)
not all features may be relevant for all devices
Displays additional information:
Identifies your current rom and displays its name
Current filesystems on your partitions
Free space remaining of all of your volumes
Current battery charge level
Backup | Restore:
Correctly calculates free space needed to complete a backup ( version > 2.2.6 RC4 )
Tar backups (can be switched on or off)
Complete CWMR5 compatibility
All Backups you create will be named after your currently installed Rom for easier identification.
Never unwillingly get "downgraded" to EXT3 again
Always restores backups using the file systems you HAD on your partitions at the time of creation!
-> all partitions formatted with ext4 at that time, will be restored to ext4. The same is true for ext3.
You can manually change any existing Backup to ext4 or ext3
-> so that after a restore, all partitions and up with the file system you wanted!
Advanced Backup: backup only a single partition
Convert any of your partitions to EXT4 or EXT3 without data loss.
Formatting:
When you wipe or format it will always use the same file system you currently have.
-> but you can change that
When you format ext4 it will always create an aligned file system
Correctly identifies unformatted sd-ext partitions
-> if it finds one it displays a warning and suggests you may format them by visiting the 4EXT menu
Filesystem check and repair option in advanced menu
Partitioning:
Alignment check of your partitions
Full support for up to 2 sd-ext partitions + swap (Backup/restore/format/convert, fsck, et.c.)
(RE-) Partition your sdcard for sd-ext without removing your fat32 partition.
All partitions created with 4EXTRecovery will be perfectly aligned to 4k
Installing:
Integrated md5sum checking option
Menus:
Most popular menu items rearranged
Format menu
Power Menu + option to reboot into bootloader
Changed Advanced Restore: first select what you want to restore, then select the backup
-> Useful for restoring from "Advanced Backups"
4ext.prop:
Configuration file on your sdcard where you can set options to be used by 4EXTRecovery
Change all settings conveniently with 4EXT Recovery Control
Many more options to come
Share your settings / themes by packing your config into a flashable theme
Other stuff:
USB Storage Autostart (must be switched on)
Mount usb storage exposes all partitions on your sdcard to the os (not just fat32)
-> you could even partition your sdcard from your PC while connected via USB
Switch haptic feedback on/off
Button backlights
Recovery Interface Api for Apps and Scripts
Both: free and paid 4EXT apps now provide a very easy to use interface you can use to access 4EXT Recovery from within your shell scripts or apps.
Features:
wipe cache
wipe dalvik
wipe data / factory reset
install multiple zips at once
backup
If you are interested, please download this zip file with examples
How to make use of 4EXT Recovery Touch from within updater-scripts:
Since Beta 1.0.0.3 Beta 4 you can do the following:
identify whether the user is running 4EXT Recovery Touch or not (to use or not to use the following commands)
make use of the native yes/no dialogue (confirm / cancel buttons)
prevent recovery from redrawing the screen ( in case you need to use your own 3rd party interactive binary )
To identify 4EXT Recovery Touch:
Code:
if getprop("ext.edition") == "ng" then
<your code>
endif;
To use the native confirm dialogues:
Code:
ui_print("4ext: show_yesno"); # <-- recovery will pause your script and display "yes / no" buttons.
run_program("/sbin/sleep", "2"); # <-- for safety since the above is executed asynchronous
#check the return value by calling:
if getprop("ext.confirm") == "yes" then
<yourcode>
endif;
To prevent recovery from redrawing the screen ( if you want to use an external binary that needs to occupy the screen and get the focus )
Code:
ui_print("4ext: disable_scrn_update");
# don't forget to enable it again after your yesno binary or graphical installer is finished, by calling:
ui_print("4ext: enable_scrn_update"); #otherwise the recovery will appear to be frozen as it won't update the screen anymore.
Oh yeah I have been waiting for this!!
Thanks alot!!
1st post ;D
best app
Yeah after a long time
Hi,
Any links to the themes?
thanks
4D3 said:
Hi,
Any links to the themes?
thanks
Click to expand...
Click to collapse
In my signature and inside the app in the themes menu
And also somewhere inside the post
it looks very nice, good job
Does the new touch 4ext recovery have the phone-off charging bug?
rahditzz said:
Does the new touch 4ext recovery have the phone-off charging bug?
Click to expand...
Click to collapse
it will charge your device to death
jk, no, charging works inside and outside recovery.
GREAT! I honestly wasn't expecting this!
I just flashed it (latest beta, RC4). It boots, the battery level and time is right, the display works fine... I'll test the backup/restore/flash functions later this week.
--
It appears that the phone DOES charge while it's turned off! Same behavior as when using the Revolutionary 4.0.1.4 recovery (LED goes red for a few seconds, then turns off, then goes back on (red) and stays that way, == charging ).
GREAT WORK !
Awsome.. Loving it already.. hehe..
madmaxx82 said:
In my signature and inside the app in the themes menu
And also somewhere inside the post
Click to expand...
Click to collapse
I guess i can use any for the sensation?
thanks
Formhault said:
GREAT! I honestly wasn't expecting this!
I just flashed it (latest beta, RC4). It boots, the battery level and time is right, the display works fine... I'll test the backup/restore/flash functions later this week.
--
It appears that the phone DOES charge while it's turned off! Same behavior as when using the Revolutionary 4.0.1.4 recovery (LED goes red for a few seconds, then turns off, then goes back on (red) and stays that way, == charging ).
GREAT WORK !
Click to expand...
Click to collapse
Thanks!
Why weren't you expecting this ?
It's very unlikely that there are any real bugs, because it's just an improvement over RC2.
But with any new build, even if there weren't alot of changes, there is still a certain "risk".
That's why any new release gets flagged as "testing".
1.0.0.4 RC2 is the fastest 4EXT Recovery yet and as stable as the most stable version released since June last year.
Let's see how Build Nr. 2 of RC3 will behave.
madmaxx82 said:
Thanks!
Why weren't you expecting this ?
It's very unlikely that there are any real bugs, because it's just an improvement over RC2.
But with any new build, even if there weren't alot of changes, there is still a certain "risk".
That's why any new release gets flagged as "testing".
1.0.0.4 RC2 is the fastest 4EXT Recovery yet and as stable as the most stable version released since June last year.
Click to expand...
Click to collapse
I had the Desire HD and I was using this recovery! RC2, I believe, 3 months ago. I still use it on my girlfriend's Desire S !
I wasn't expecting it to be 1.0.0.4, the same as for the other phones, and in perfect condition! I thought this would be the first build...
Formhault said:
I had the Desire HD and I was using this recovery! RC2, I believe, 3 months ago. I still use it on my girlfriend's Desire S !
I wasn't expecting it to be 1.0.0.4, the same as for the other phones, and in perfect condition! I thought this would be the first build...
Click to expand...
Click to collapse
The code for all devices is the same.
Only some adjustments regarding the Touchscreen were needed for the Evo GSM
Edit: ohh and the charging problems
BTW: Please upgrade the rc2 you mention is too old so it can't be 1.0.0.4
Formhault said:
I just flashed it (latest beta, RC4).
Click to expand...
Click to collapse
Where did u get RC4? I can only get RC3..:S
rahditzz said:
Where did u get RC4? I can only get RC3..:S
Click to expand...
Click to collapse
4EXT Recovery app... That's how I got it. There's no other way you can possibly get it, anyway .
Hmm.. RC4 isnt showing up for me..:S
madmaxx82 said:
The code for all devices is the same.
Only some adjustments regarding the Touchscreen were needed for the Evo GSM
Edit: ohh and the charging problems
BTW: Please upgrade the rc2 you mention is too old so it can't be 1.0.0.4
Click to expand...
Click to collapse
Then perhaps my memory was failing on me . I'll see tomorrow what version it is on my gf's DS and update it (I only use it once every few months, anyway). I no longer own the DHD, btw.
Thanks again for bringing the 3VO into your supported-phones line
@those not being able to see RC4... Perhaps you should update the 4EXT Recovery Control app... Latest is v2.3.1
Sent from my LeeDrOiD-loaded 3VO
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.
LuneOS for the HP Touchpad
Edited: January 30 of 2022 ( Update links for the LuneOS builds )
For information about LuneOS:
https://pivotce.com/2019/10/24/luneos-october-stable-release-eggnog-latte/
For the WebOS Nation Forum:
https://forums.webosnation.com/luneos/
How to flash:
LuneOS is flash onto it's own 2GB partition /luneos.
It shares the same swap partition from Android, same as WebOS does.
The Tablet can be setup to a triple /boot : WebOS : Android (any version) and LuneOS.
This guide and files will make it a dual boot of Android and LuneOS.
The only thing to do is download and flash as always.
All process will WIPE ALL the data from the Tablet.
Back up all data to PC, before doing any of the following.
To set up Tablet:
WebOS only: novacom driver must be on PC or use the following:
Click HERE for Linux OS with Novacom driver
If the Tablet only has WebOS or Android
One a PC with the novacom driver, place the Tablet in WebOS Recovery mode.
Download: uImage.wipe_all_create_Android_Luneos
Click HERE to Download uImage.wipe_all_create_Android_Luneos
open a command prompt where the file was saved and enter:
novacom boot mem:// < uImage.wipe_all_create_Android_Luneos
( All data will be wipe, erase and formatted. Android volumes and LuneOS partition with a 1GB swap will be created.)
TWRP Recovery 3.2.1 modified to mount the LuneOS partition is flash in /boot
To flash any new test-build or stable version, only download, rename and flash.
There is no need to flash any WIPE_ALL
Main project Page:
https://github.com/webOS-ports
Testing releases to download
https://github.com/webOS-ports/luneos-testing/releases
20220125 LuneOS Testing BuildsExpand Assets: The following files are listed.
1. Download luneos-dev-image-tenderloin-20220125.rootfs.tar.gz file , renamed it to luneos.tar.gz and copy it to the Micro SD card of the Tablet.
Flash the following files in TWRP Recovery:
2. Download: The uImage-tenderloin-20220125 file , renamed it to luneos and copy it to the Micro SD card of the Tablet.
https://www.mediafire.com/folder/7hi6v6t8j092h/LuneOS
3. Download: Flash_boot_uImage_LuneOS.zip
4. Download: Flash_LuneOS.zip
If the Tablet has any version of Android or recovery:
Flash the following file with any recovery:
Download: Automatic_Wipe_All_Android_and_LuneOS_1GB_Swap_Partition.zip
Click HERE to Download Automatic_Wipe_All_Create_Android_and_LuneOS_1GB_Swap_Partition.zip
Follow steps 1,2 and 4 from above.
The file: FLINTMAN-TWRP-3.2.1-0-03-15-2018_LuneOS.zip
Is the modified Recovery to flash LuneOS and is already flash onto /boot by the previous process.
Only flash this file, if is changed or damage in any way.
Click HERE to Download all the listed Files
LuneOS is constantly changing, the following link provide the luneos-testing files.
https://github.com/webOS-ports
LuneOS Eggnog Latte
After finish flashing there will be no animation or image while booting, only shows a dark active screen.
It will take a while and then the LuneOS logo will show to set up the Tablet.
Not working:
Camera
Home Button
Issues:
The screen will dim even is been use and will turn off.
Go to settings and change it to 3 minutes, but still will turn off.
There are more, but will be fix with the next release.
how to use novacom on windows? I have installed novacom drivers but I can't seem to find novacom.exe or any novacom executable anywhere
---------- Post added at 08:57 PM ---------- Previous post was at 08:29 PM ----------
I already have android and TWRP, do I need the step:
novacom boot mem:// < uImage.wipe_all_create_Android_Luneos
?
what are the steps?
1/ Boot to TWRP
2/ Flash Automatic_Wipe_All_Android_and_LuneOS_1GB_Swap_Partition.zip
3/ Flash Flash_boot_uImage_LuneOS_Eggnog_Latte.zip
4/ Copy luneos.tar.gz to touchpad
5/ Flash Flash_LuneOS.zip
?
yeahman45 said:
how to use novacom on windows? I have installed novacom drivers but I can't seem to find novacom.exe or any novacom executable anywhere
The novacom is a driver that allows the PC to communicate with the Tablet when is place in the WebOS Recovery mode (Big USB Symbol)
There is no *.exe that can be executed to provide a graphical interface and interact with the Tablet.
All is done in a command prompt or terminal window.
The main use is to load any uImage into the Tablet's memory to boot with the following command:
novacom boot mem:// <
---------- Post added at 08:57 PM ---------- Previous post was at 08:29 PM ----------
I already have android and TWRP, do I need the step:
novacom boot mem:// < uImage.wipe_all_create_Android_Luneos
?
No, is not need it.
If the Tablet already has Android and any Recovery, then just flash:
Automatic_Wipe_All_Android_and_LuneOS_1GB_Swap_Par tition.zip
what are the steps?
Correct.
1/ Boot to TWRP
2/ Flash Automatic_Wipe_All_Android_and_LuneOS_1GB_Swap_Par tition.zip
3/ Copy luneos.tar.gz to touchpad ( download from the link and rename it )
4/ Flash Flash_LuneOS.zip
5. Flash_boot_uImage_LuneOS_Eggnog_Latte.zip
?
Click to expand...
Click to collapse
The Automatic_Wipe ( creates the LuneOS partition of 2GB plus all the standard Android volumes )
It also flash a modified version of TWRP that allows to mount the LuneOS partition.
Flash_LuneOS.zip is a script that will decompress luneos.tar.gz into the /luneos partition.
Flash_boot_uImage_LuneOS_Eggnog_Latte.zip is the uImage, to boot into LuneOS.
LuneOS is a work in progress, but once the Tablet is set up then future releases can be flash in the same way as Android ROMs, download and flash in TWRP Recovery.
ok thx. I managed to flash it luneos seems a bit sluggish but I haven't tested it in detail yet
yeahman45 said:
ok thx. I managed to flash it luneos seems a bit sluggish but I haven't tested it in detail yet
Click to expand...
Click to collapse
Thanks for the feedback, great to know the instructions can be replicated.
I am trying to apply the same optimizations that I did to all the Android ROMs and then it should work just as fast. Is using the Android Lollipop Kernel. The Web browser experience is different, allows for playback in the background and with the screen off, all native with no changes or modifications.
HP_TOUCHPAD said:
The Tablet can be setup to a triple /boot : WebOS : Android (any version) and LuneOS.
Click to expand...
Click to collapse
How would I go about doing such a triple-boot? Would I need to set up the partitions manually? If so, in what way?
Eearslya said:
How would I go about doing such a triple-boot? Would I need to set up the partitions manually? If so, in what way?
Click to expand...
Click to collapse
I did not provided the link to the file that will create the partitions for LuneOS, I will update the guide now.
Here is the file to download and flash. It will erase everything, format the storage and create the partitions:
For Android and LuneOS, it will be a Dual boot.
Click HERE to download the zip file to create Android and LuneOS partition
This is the link from the guide that allows to download all the files:
Click HERE to Download all the LuneOS and Android files
Select the best depending on your current set up.
That will do a Dual boot
For a Triple Boot to keep WebOS, Taylor a webOS APP must be use inside WebOS to create the LuneOS partitions.
Thanks for the thread, but for whatever reason I keep getting the dreaded "Access Denied" error when getting to:
novacom boot mem:// < uImage.wipe_all_create_Android_Luneos
Surely I am doing something wrong, but not sure what. I am following the directions as close as I can.
I just have plain old factory webOS 3.0.5 installed, no tweaks or anything applied.
I am on Windows 10 and do have admin access. A triple boot option would be nice.
0423TP said:
Thanks for the thread, but for whatever reason I keep getting the dreaded "Access Denied" error when getting to:
novacom boot mem:// < uImage.wipe_all_create_Android_Luneos
Surely I am doing something wrong, but not sure what. I am following the directions as close as I can.
I just have plain old factory webOS 3.0.5 installed, no tweaks or anything applied.
I am on Windows 10 and do have admin access. A triple boot option would be nice.
Click to expand...
Click to collapse
This guide is for a DUAL boot of LuneOS and Android.
WebOS will be wipe, completely remove.
If the Tablet has TWRP Recovery install then the full automatic flash zip file can be use.
The Tablet can do a Triple boot, WebOS, Android and LuneOS.
For that to be done:
Stock WebOS
Then use the ToolBox to create Android partitions.
Flash Android
Now is dual boot with WebOS and Android.
Inside WebOS using Taylor a new LuneOS partition must be created, then flash LuneOS inside WebOS.
The uImage of either Android or LuneOS must be move to the USB storage as there is not enough space in boot.
If you want to keep WebOS do not use any of the posted files, it will completely remove it.
Hello again HP_TOUCHPAD : ) thank you for your help in my thread by the way! Still keeping at it with the heat and charging.
Anyways, I ended up with another Touchpad for $20! Novacom says the battery health is impeccable, so I saw this and wanted to give it a go.
-installed novacom driver for windows 10 x64 (note, this installs to C:\Program Files\Palm, Inc. I noticed quite a lot of people struggling with this)
-downloaded uImage.wipe_all_create_Android_Luneos
-put touchpad into usb recovery mode (power off, hold vol up and power until usb icon appears)
-ran command "novacom boot mem:// < uImage.wipe_all_create_Android_Luneos"
-tablet rebooted to custom screen noting it's doing stuff and nothing on the screen will update until finished
-tablet finished, rebooted into moboot, and automatically booted into TWRP
-downloaded latest luneos and renamed to luneos.tar.gz
-copied luneos.tar.gz, Flash_boot_uImage_LuneOS_Eggnog_Latte.zip, and Flash_LuneOS.zip to touchpad
-flashed Flash_LuneOS.zip via twrp
-flashed Flash_boot_uImage_LuneOS_Eggnog_Latte.zip
-copied and flashed EverVolv 9.0 and gApps
-wiped dalvik cache
-rebooted
Moboot appeared with LuneOS and Android options. First I picked LuneOS. As noted, it sat on a BLACK screen for a while (screen was ON, just black) and after a few minutes I got the setup page!
Went through setup, then rebooted to check android, setup, and working!
All of this without a single hitch.
This rocks! Thank you for all the work on this to you and the LuneOS team
Thank you! I was considering this but have not made the time to research...
Sent from my PH-1 using Tapatalk
Nillanic said:
Hello again HP_TOUCHPAD : ) thank you for your help in my thread by the way! Still keeping at it with the heat and charging.
You are very welcome, give it some time and it will come back!
Anyways, I ended up with another Touchpad for $20! Novacom says the battery health is impeccable, so I saw this and wanted to give it a go.
The Tablet can be found anywhere, some users have found some in brand new un-open boxes in the trash bin.
Many can also be found on ebay, so there is no shortage.
-installed novacom driver for windows 10 x64 (note, this installs to C:\Program Files\Palm, Inc. I noticed quite a lot of people struggling with this)
That is the reason that I created the Live Linux OS, to provide the novacom driver built in. It will assure access to it forever.
Click Here for hp-touchpad-novacom-repair-android
-downloaded uImage.wipe_all_create_Android_Luneos
This is how is created, partitioning the internal storage with LVM:
Click HERE for the most powerful-feature-hp-touchpad-lvm
-put touchpad into usb recovery mode (power off, hold vol up and power until usb icon appears)
That is the best way to do it !
-ran command "novacom boot mem:// < uImage.wipe_all_create_Android_Luneos"
That command loads any uImage onto the Tablet's memory to boot. Is the same method to load the ToolBox, it can be use to load any Recovery with no need to have it on /boot.
-tablet rebooted to custom screen noting it's doing stuff and nothing on the screen will update until finished
The internal storage gets wipe out and repartitions.
-tablet finished, rebooted into moboot, and automatically booted into TWRP
-downloaded latest luneos and renamed to luneos.tar.gz
That is the ROM, same as Android zip files.
-copied luneos.tar.gz, Flash_boot_uImage_LuneOS_Eggnog_Latte.zip, and Flash_LuneOS.zip to touchpad
-flashed Flash_LuneOS.zip via twrp
LuneOS gets unzip and copy to the Tablet.
-flashed Flash_boot_uImage_LuneOS_Eggnog_Latte.zip
This is the uImage, it can also be loaded to memory from PC if boot is full.
-copied and flashed EverVolv 9.0 and gApps
-wiped dalvik cache
-rebooted
Moboot appeared with LuneOS and Android options. First I picked LuneOS. As noted, it sat on a BLACK screen for a while (screen was ON, just black) and after a few minutes I got the setup page!
The black screen looks like is dead, but is actually installing the OS.
Went through setup, then rebooted to check android, setup, and working!
All of this without a single hitch.
You did a great job following the guide !
This rocks! Thank you for all the work on this to you and the LuneOS team
Click to expand...
Click to collapse
Thanks for verifying that all the steps are correct to get it working.
The WebOS HP Touchpad was way ahead of it's time when introduced in 2011. The flexibility of using LVM makes it possible for endless configurations.
It can be set up:
WebOS, LuneOS and any version of Android.
Or
Android, LuneOS, Sailfish and different versions of Linux as chroot.
Click Here for setting up Linux as chroot
Click HERE for the youtube channel
Work in progress by the LuneOS team on the possible next release:
https://forums.webosnation.com/webos-events/331758-webos-user-s-online-meet-up-12.html#post3456921
There is also work on porting Android 10, if it happens we will know some time next year or sooner!
Does anyone have the latest LuneOS uImage? It seems that the download page is down.
I would also like the "image" that is referenced in this step of installing LuneOS on their website:
{
"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"
}
M.A. HP Touchpad said:
I would also like the "image" that is referenced in this step of installing LuneOS on their website:View attachment 5476941
Click to expand...
Click to collapse
It looks like everything is getting an update and the new version will be available soon, read this post:
https://forums.webosnation.com/luneos/332696-new-release-coming.html#post3457875
The new LuneOS test-builds are available.
At setup, it will show that WiFi is not available, finish the settings and then to enable it enter the following code:
Go to Apps then open QML TERM and enter this code
Code:
rmmod ath6kl ; modprobe ath6kl
systemctl mask systemd-udev-settle.service
Go to Prefs --> Wi-Fi turn ON and connect to your network.
Solution provided by:
https://forums.webosnation.com/luneos/332829-building-luneos.html#post3457972
Follow the guide and download the current files to get it working.
Any Android version can be use with LuneOS as dual boot.
LuneOS is also sharing the same swap partition with Android ( same as with WebOS )
Attached are (low quality pictures taken as there is no way to do screenshots at the moment.
Boot menu With Android (9) and LuneOS
After selecting LuneOS a blue screen will be display for about 3 minutes and 40 seconds.
After 3 minutes and 40 seconds the screen will turn black for a moment, then the LuneOS Logo will show.
There will be a setup and then the home screen will show.
Hi everyone.
First and foremost, many thanks for your fantastic work. I have been using Android on my Touchpad for a while thanks to your great efforts!
Second, this is my first time here, and I am calling in because I am a bit lost.
I have been trying to install the latest testing builds of the Eggnot Latte, and it seems that my last step is failing, and I need your kind advice.
So what have I done:
Initial situation: TP with TWIRP 3.2.1 and Android. Main computer on Windows 10 but using Ubuntu Live in case of problems...
Step 1: Downloaded and adb-sideloaded the "Automatic_Wipe_All_Android_and_LuneOS_1GB_Swap_Partition.zip" file
Step 2: Downloaded the next 3 files and copied them to the TP using Ubuntu (TWIRP MTP/USB mount and my Windows 10 don't like each other by some weird reason)
a. "luneos-dev-emulator-qemux86-64-20220207-v2.tar.gz" (and renamed it luneos.tar.gz)
b. "Flash_LuneOS.zip"
c. "Flash_boot_uImage_LuneOS.zip"
Step 3: Flashed LuneOS. While flashing I was expecting that I would get a black screen or something like that, because it says so during the flashing, but that never happened. What flashing actually does is un-tar the file into the /luneos folder i.e., copies 2 extracted files into the LuneOS folder that was originally created with the "Automatic Wipe" flashing.
Step 4: Flashed the "Boot_uImage" file. This file actually has a moboot.default file that I suppose that replaces the original one on the /boot folder.
Problem: after all these steps, the Moboot shows no LuneOS at the start.
Analysis and test: after looking at the /boot directory, I understood that we would need a uImage.LuneOS kernel file on that directory to make this work.
Site https://webos-ports.org/wiki/Install_LuneOS_for_Tenderloin has one, and I downloaded it, added the LuneOS extension and copied it into the /boot directory.
Result: after boot, the LuneOS option appears, but after choosing it, it stays as a blank screen.
Following these time-consuming efforts notwithstanding, I need to address this forum for further help i.e., does anybody have an uImage kernel file that would work with this release?
Many thanks
Touchpad_DMR said:
Hi everyone.
First and foremost, many thanks for your fantastic work. I have been using Android on my Touchpad for a while thanks to your great efforts!
Second, this is my first time here, and I am calling in because I am a bit lost.
I have been trying to install the latest testing builds of the Eggnot Latte, and it seems that my last step is failing, and I need your kind advice.
So what have I done:
Initial situation: TP with TWIRP 3.2.1 and Android. Main computer on Windows 10 but using Ubuntu Live in case of problems...
Step 1: Downloaded and adb-sideloaded the "Automatic_Wipe_All_Android_and_LuneOS_1GB_Swap_Partition.zip" file ( This file must be flash first )
After the Tablet reboot, copy the files to be flash.
Step 2: Downloaded the next 3 files and copied them to the TP using Ubuntu (TWIRP MTP/USB mount and my Windows 10 don't like each other by some weird reason)
a. "luneos-dev-emulator-qemux86-64-20220207-v2.tar.gz" (and renamed it luneos.tar.gz) (WRONG FILE, read the file name, is for an emulator to be run on a PC)
Click to expand...
Click to collapse
The correct file name is : luneos-dev-image-tenderloin-20220125.rootfs.tar.gz
The kernel file is : uImage-tenderloin-20220125
The files are located at:
20220125 LuneOS Testing BuildsThen Expand Assets:
Touchpad_DMR said:
b. "Flash_LuneOS.zip"
c. "Flash_boot_uImage_LuneOS.zip"
Step 3: Flashed LuneOS. While flashing I was expecting that I would get a black screen or something like that, because it says so during the flashing, but that never happened. What flashing actually does is un-tar the file into the /luneos folder i.e., copies 2 extracted files into the LuneOS folder that was originally created with the "Automatic Wipe" flashing.
Step 4: Flashed the "Boot_uImage" file. This file actually has a moboot.default file that I suppose that replaces the original one on the /boot folder.
Problem: after all these steps, the Moboot shows no LuneOS at the start.
Analysis and test: after looking at the /boot directory, I understood that we would need a uImage.LuneOS kernel file on that directory to make this work.
Site https://webos-ports.org/wiki/Install_LuneOS_for_Tenderloin has one, and I downloaded it, added the LuneOS extension and copied it into the /boot directory.
Result: after boot, the LuneOS option appears, but after choosing it, it stays as a blank screen.
Following these time-consuming efforts notwithstanding, I need to address this forum for further help i.e., does anybody have an uImage kernel file that would work with this release?
Many thanks
Click to expand...
Click to collapse
Try with the correct file names, there is no need to do the Automatic_Wipe_All.
Made correction to the guide to properly find the files.
Many thanks for your help!
It works like a charm!
Please keep up with the good work.
It is deeply appreciated.
In the meantime, I'll play with my Touchpad and see what it does now!