{
"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"
}
Fastboot Enhance
What it can do?
- Show fastboot vars
- Switch between fastbootd & bootloader
- Switch between A & B slot
- Flash Payload.bin in fastbootd
- Flash images
- Erase partitions
- Delete logical partitions
- Create logical partitions
- Resize logical partitions
- Unpack Payload.bin
- Extract specific image from Payload.bin
- Show Payload vars
- Show dynamic partition metadata
And above all, it has friendly GUI
Download
Releases · libxzr/FastbootEnhance
A user-friendly Fastboot ToolBox & Payload Dumper for Windows - libxzr/FastbootEnhance
github.com
By using this, you can freely switch between different versions of HydrogenOS & OxygenOS & Custom ROMs.
It is mostly tested on 8T but should work fine on any device shipped with dynamic partitions.
Notes for fastboot visualization
- You need to pre-install related fastboot usb drivers to make sure the device can be recognize by the software.
- Only in fastbootd or bootloader mode can the software recognize your device.
reserved2
I wonder if this would work with kb2007 TMO to go to ColorOS? I will download a check it out, thanks for the contribution!
xzr467706992 said:
Fastboot Enhance
Click to expand...
Click to collapse
Dev
xzr467706992thanks for making this tool! I created (modified) a non-working OTA incremental update Linux program to install 11.0.9.9.KB05AA on my rooted Op8T (not available as a full update yet) and this program notified me that the -cow files, when I clicked on install from payload.bin, had to be deleted as they were temp files and taking up space in super - now I'm running an unreleased build (full update) on my Op8T!!! I have no idea where you found documentation on these temp -cow files, but it was the missing part of all my work!!! Without those logical files present, there was enough room in Super to install the fully updated Super components (odm, product, system, system_ext, and product)! And I have to say, your program is awesome!!! Intuitive interface, high functionality, and makes things just easier to see and do.
mslezak said:
Dev
xzr467706992thanks for making this tool! I created (modified) a non-working OTA incremental update Linux program to install 11.0.9.9.KB05AA on my rooted Op8T (not available as a full update yet) and this program notified me that the -cow files, when I clicked on install from payload.bin, had to be deleted as they were temp files and taking up space in super - now I'm running an unreleased build (full update) on my Op8T!!! I have no idea where you found documentation on these temp -cow files, but it was the missing part of all my work!!! Without those logical files present, there was enough room in Super to install the fully updated Super components (odm, product, system, system_ext, and product)! And I have to say, your program is awesome!!! Intuitive interface, high functionality, and makes things just easier to see and do.
Click to expand...
Click to collapse
Disregard I just found your thread
Great job
mslezak said:
Dev
xzr467706992thanks for making this tool! I created (modified) a non-working OTA incremental update Linux program to install 11.0.9.9.KB05AA on my rooted Op8T (not available as a full update yet) and this program notified me that the -cow files, when I clicked on install from payload.bin, had to be deleted as they were temp files and taking up space in super - now I'm running an unreleased build (full update) on my Op8T!!! I have no idea where you found documentation on these temp -cow files, but it was the missing part of all my work!!! Without those logical files present, there was enough room in Super to install the fully updated Super components (odm, product, system, system_ext, and product)! And I have to say, your program is awesome!!! Intuitive interface, high functionality, and makes things just easier to see and do.
Click to expand...
Click to collapse
Google has mentioned the copy-on-write(COW) device here
Virtual A/B Overview | Android Open Source Project
source.android.com
For virtual a/b, the COW devices are created during the process of update. When there's enough spaces in super, they'll be created there, otherwise they'll be created in /data/gsi/ota.
xzr467706992 said:
Google has mentioned the copy-on-write(COW) device here
Virtual A/B Overview | Android Open Source Project
source.android.com
For virtual a/b, the COW devices are created during the process of update. When there's enough spaces in super, they'll be created there, otherwise they'll be created in /data/gsi/ota.
Click to expand...
Click to collapse
Yes I found it there for "virtual A/B" just an hour or two ago actually. They don't explain it too well, however.
Please don't mind I have few doubts about how to use this.
1. Suppose I have installed a custom rom and now I want to go back to Oxygen OS, can I do it by flashing the payload.bin using this fastboot enhance tool? If yes, what exact steps I have to go through?
2. If I flash the payload bin using this tool, will my all partitions will be recreated automatically as it was in a fresh stock condition when I used this 8T for first time even if the custom rom did any mess up with size or anything else? Also will it cleanup inactive slot too?
Amsal1 said:
Please don't mind I have few doubts about how to use this.
1. Suppose I have installed a custom rom and now I want to go back to Oxygen OS, can I do it by flashing the payload.bin using this fastboot enhance tool? If yes, what exact steps I have to go through?
2. If I flash the payload bin using this tool, will my all partitions will be recreated automatically as it was in a fresh stock condition when I used this 8T for first time even if the custom rom did any mess up with size or anything else? Also will it cleanup inactive slot too?
Click to expand...
Click to collapse
Yes, you can switch between custom ROMs and OOS using this tool.
This tool will only flash partitions listed in payload.bin, that means other partitions will remain unchanged.
Logical partitions will be automatically resized during flashing.
This tool will not create snapshot & switch slot when flashing, which is different from a normal update or sideload. That means the current slot will be flashed with new images in payload.
Note that on 8T, only the current slot you are using is bootable because of virtual ab, DO NOT SWITCH SLOT.
xzr467706992 said:
Yes, you can switch between custom ROMs and OOS using this tool.
This tool will only flash partitions listed in payload.bin, that means other partitions will remain unchanged.
Logical partitions will be automatically resized during flashing.
This tool will not create snapshot & switch slot when flashing, which is different from a normal update or sideload. That means the current slot will be flashed with new images in payload.
Note that on 8T, only the current slot you are using is bootable because of virtual ab, DO NOT SWITCH SLOT.
Click to expand...
Click to collapse
Thanks for your clarification
So the exact steps to flash any rom(OOS, Custom Rom) would be:
1. Boot to fastbootd mode
2. Load the payload.bin in Fastboot enhance v1.8
3. Click the flash payload.bin
4. Reboot to recovery and wipe
5. Reboot to system
right?
Amsal1 said:
Thanks for your clarification
So the exact steps to flash any rom(OOS, Custom Rom) would be:
1. Boot to fastbootd/bootloader mode
2. Load the payload.bin in Fastboot enhance v1.8
3. Click the flash payload.bin
4. Reboot to system
right?
Click to expand...
Click to collapse
Yes but you need to reboot to fastbootd for logical partitions (also theres hint in software)
Btw remember to enter recovery and wipe data after flashing
xzr467706992 said:
Yes but you need to reboot to fastbootd for logical partitions (also theres hint in software)
Btw remember to enter recovery and wipe data after flashing
Click to expand...
Click to collapse
reboot to fastbootd for logical partitions? I didn't got this.
Sure I will wipe from recovery after flashing the rom!
Amsal1 said:
reboot to fastbootd for logical partitions? I didn't got this.
Sure I will wipe from recovery after flashing the rom!
Click to expand...
Click to collapse
That means: flash payload in fastbootd because we have logical partitions.
xzr467706992 said:
That means: flash payload in fastbootd because we have logical partitions.
Click to expand...
Click to collapse
How can I enter fastbootd mode bro ? Thank you
hieu76pro said:
How can I enter fastbootd mode bro ? Thank you
Click to expand...
Click to collapse
If you are in system
adb reboot fadtboot
If you are in bootloader
Press the "reboot to fastbootd" button in software
xzr467706992 said:
If you are in system
adb reboot fadtboot
If you are in bootloader
Press the "reboot to fastbootd" button in software
Click to expand...
Click to collapse
Thanks bro
I am getting this while trying to flash evo x rom payload.bin:
These are the two cow partitions I found:
Is it safe to delete these two partitions?
Amsal1 said:
I am getting this while trying to flash evo x rom payload.bin:
View attachment 5383121
These are the two cow partitions I found:
View attachment 5383123
Is it safe to delete these two partitions?
Click to expand...
Click to collapse
Yes if system update status is none
Related
Nandroid Restore
UPDATE: XDA member Cyanogen has put together a new recovery image that has a Nandroid restore mode built right in. This allows Nandroid to be totally selfcontained on the device. My (and Markazah) program still is good for easy restores if you keep multiple backups because Cyanogen's only restores the latest backup (within the Recovery image GUI anyway.)
Here is a link to his "Pimped out recovery image with new features"
http://forum.xda-developers.com/showthread.php?t=523558
Awsome Cyanogen!
{
"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"
}
Nandroid, created through the efforts of Infernix and Brainaid, is a great tool for backing up your phone. The NANDROID backup process itself is easy to use; however, some folks are not so sure about how to restore these backups back to their phone.
Solution: Nandroid Restore and Nandroid Restore GUI
What it does:
Automates the FASTBOOT portion of the restore.
Nandroid Restore will use FASTBOOT to wipe and then restore the boot, system, userdata and recovery partitions from your phone.
When these tasks are completed, the script then reboots your phone.
What you should expect:
You should end up with a clean restore and all of your data just as you had it when you made your NANDROID backup. EASY!
Directions:
Get your phone into the Secondary Boot Loader (SPL):
Plug your phone into your computer with the USB cable
Take your NANDROID backup off of your SD card and place it in a directory on your PC with a copy of both fastboot.exe and AdbWinApi.dll.
Enter the Secondary Boot Loader (SPL) of your phone by powering down your phone and then powering it back up while holding both the <END> button and the <CAMERA> button.
Restore using NANDrest.bat from the command line:
On your PC, drop to a command prompt and navigate to the directory that you placed your NANDROID backup and fastboot.exe files.
Execute the program "nandrest.bat".
(It is also possible to simpily run this script from the folder without using the command prompt. We all have our preferences after all.)
Restore using Nandroid Restore GUI: (GUI written courtesy of XDA user Markazeh)
Make sure that the 4 Nandroid Restore GUI files are in the same folder as your NANDROID backups.
The GUI will make sure that all required files (the *.img files and Nandrest scripts.)
(See the included pictures)
Reference knowledge:
NANDROID is included with JesusFreke's testkeys modded recovery image. If you have a JF ROM then you probably already have this recovery image and NANDROID.
You must have the Engineering SPL or HardSPL to use FASTBOOT.
Fastboot.exe and AdbWinApi.dll are found in the "tools" folder of the SDK files.
FASTBOOT requires drivers to be loaded into your Windows Operating System. These drivers are in "usb_driver" folder of the SDK files.
Conclusion:
Sure, it's pretty simple and I use it to save time and automate the repair of my latest screw-up and now you can too!
Thank you to Infernix, Brainaid, JesusFreke, Haykuro, TheDudeOfLife, Google and all others that have given their skills and time to the Android community (and subsequently introduced the necessity for NANDROID. )
And thank you to XDA member Markazeh for providing the GUI for Nandrest.bat.
NANDROID post:
http://forum.xda-developers.com/showthread.php?t=459830
Secondary Boot Loader (SPL) post:
http://forum.xda-developers.com/showthread.php?t=455860
will try this, thanks.
Thank you for this.
where is nandrest.bat?
@Sandshrimp: The nandrest.bat file is inside of the nandrest.zip file. You must first unzip nandrest.zip before you will be able to access nandrest.bat.
How is this script working for the rest of you?
Hey nicksen,
i was bored this evening, so i decided to write a little GUI for your Script...
How it works:
- First off, i deleted the ":AREYOUSURE" part in your script, cause a security check is
in the GUI.
- When you start the GUI, it checks if no file is missing and shows missing files
graphically.
- You can only press the "Flash" Button, when every file is in the folder...
I renamed the "nandrest.bat" to "nandrest", that no one can accindently flash the phone by clicking the nandrest.bat. When you click "Flash" the Programm renames the script to "nandrest.bat", that Windows can open it and after your Script has finished it renames it back to "nandrest".
Hope you like it!
Greetings
Markazeh
Markazeh said:
Hey nicksen,
i was bored this evening, so i decided to write a little GUI for your Script...
How it works:
- First off, i deleted the ":AREYOUSURE" part, cause this security check is
handled in the GUI.
- When you start the GUI, it checks if no file is missing and shows missing files
graphically.
- You can only press the "Flash" Button, when every file is in the folder...
I renamed the "nandrest.bat" to "nandrest", that no one can accindently flash the phone by clicking the nandrest.bat, cause i deleted the security check in it... When you click "Flash" the Programm rename the script to "nandrest.bat", that Windows can open it. After your Script is finished it renames it to "nandrest".
Hope you like it!
Greetings
Markazeh
Click to expand...
Click to collapse
nicksen782: Thanks a bunch for the script!
Markazeh: Thanks even more for making a user friendly GUI for it!
This is amazing work, I love this community for this sort of collaborations.
I'll send people this way for easy restore.
@Markazeh -
Thanks! I like the GUI! This is technically my first contribution so I'm pretty tickled that it has been useful so soon. May I suggest that your GUI also check for the presence of AdbWinApi.dll and Fastboot.exe? Oh, and maybe throw my name on your GUI for the script portion? I can rewrite the first post of this thread to include the new GUI.
THANKS!
Yeh, I'm gonna put your name also on the GUI.
I CAN check for the other files, but some people have these files in the win dir....
I have to think about that....
I'll upload the GUI with your name in it in a few hours
May you can give a suggestion on how to handle the problem with the files....
Greets
This works great, thanks guys! Nice job!
Wow! What a great idea. We have all been needing this, IMHO.
How difficult would it be to make it possible to restore only one or more portions of the backup? For example, I did a wipe on the last flash of 1.5, and I want to restore my /data, but not the rest. If you could add that capability, this app would be perfect.
Thanks for your work.
agreed
stellarman said:
Wow! What a great idea. We have all been needing this, IMHO.
How difficult would it be to make it possible to restore only one or more portions of the backup? For example, I did a wipe on the last flash of 1.5, and I want to restore my /data, but not the rest. If you could add that capability, this app would be perfect.
Thanks for your work.
Click to expand...
Click to collapse
I'd prefer not to restore the recovery partition every time for example (it doesn't change too much in my experience outside of flashing to an "official" build). That would be a great tweak!
Ok, ill discuss with nicksen...
Markazeh said:
Ok, ill discuss with nicksen...
Click to expand...
Click to collapse
Thanks. I will keep an eye open for your answer.
Another idea: Could this script, or one like it, possibly be added to 'recovery' so that it shows in recovery mode along with the backup command? It would be really sweet if we could do an 'alt + r' (or whatever) and restore the most recent nandroid backup. I know it is asking alot. But, "to g-e-t, you have to a-s-k." Right?
stellarman said:
Thanks. I will keep an eye open for your answer.
Another idea: Could this script, or one like it, possibly be added to 'recovery' so that it shows in recovery mode along with the backup command? It would be really sweet if we could do an 'alt + r' (or whatever) and restore the most recent nandroid backup. I know it is asking alot. But, "to g-e-t, you have to a-s-k." Right?
Click to expand...
Click to collapse
Well, it should be possible in a way, but we cant do it, cause this script is for windows and android/recovery is linux based...
GUI looks good, another suggestion would be to allow user selection of what is flashed. E.g. Data.img only or just Boot.img and System.img
@ markazeh: There have been some good suggestions. Perhaps checkboxes next to the "found/not found" labels? These checkboxes could default to all checked or all checked except recovery. You could also give the user the option of flashing or not flashing individual images via these checkboxes. Maybe 3 radio buttons at the top labeled: Restore EVERYTHING, Restore ONLY data, Restore EVERYTHING except recovery. Something to that effect. How can I help further?
I personally would really like a NANDROID restore to be available via something like alt+r in the recovery mode such as stellarman has suggested. My assumption is that the recovery mode loads in some of these partitions that we would be trying to restore and that would cause a problem. However, if it were possible to safely unmount these partitions and then restore using flash_image then it might work. The flash_image program however is on the system partition so a ramdrive or other temporary solution would need to be created first. I figure that this is why this hasn't already been done.
Can anybody confirm any of this?
Well the problem is, that i have to split your script in these parts: data flashing, recovery flashing, system flashing and boot flashing, cause i cant go to a part in the script, i can only run a bat.... So im going to split your script in these parts.
Then we have 4 small scripts....
Im going to put 4 Buttons to Flash System, Boot, Data and Recovery.
Should be done Tomorrow.
Version 1.1 here...
All you need is in first post!
Note: I give no guarantee if your phone will brick... But if you use our program properly it wont brick!
awesome
Markazeh said:
Version 1.1 here...
All you need is in first post!
Note: I give no guarantee if your phone will brick... But if you use our program properly it wont brick!
Click to expand...
Click to collapse
You guys rock, thanks!
{
"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"
}
For anyone interested, below are the steps for getting your device dual-booting with CyanogenMod 10.2.
Why?
I don't want to erase native firmware and want to give a try to CyanogenMod
I want to have both native and CM, because I like native Samsung S-Pen apps, but want to have more fresh Android too
I like experimenting - it's cool!
The Idea
Our Android device has 2 boot partitions - for normal boot, and to boot into recovery. If I want to boot CyanogenMod, I need to place its boot image instead one of those boot partitions. E.g. if I want to have both native firmware and cyanogen - then obviously I need to replace recovery partition. However I can do the backup of recovery and restore it later if needed.
But, I also need to place cyanogen system and data partitions somewhere. Putting it on the external sdcard makes CM working really slow, repartitioning internal memory might be good idea, but it is not so easy and is not necessary for experimenting. Thus I've created 2 image files and put it to native data partition (mmcblk0p12) to media folder, e.g. into internal sdcard, then changed cyanogen boot image to mount those image files on boot as system and data partitions.
Prerequisites:
Rooted Samsung Galaxy Note 10.1 2012 Edition
2GB of free disk space at internal sdcard
Recovery partition backup, because we are going to replace it with CyanogenMod boot image
Clear understanding of what you are doing, because you potentially can break your device
Downloads:
CM 10.2 boot image
CM 10.2 data partition image
CM 10.2 system partition image
Steps
This manual suggests that you are going to do the recovery backup to external sdcard and has native firmware which means that recovery partition is mmcblk0p6, data partition is mmcblk0p12 and internal sdcard is /mnt/sdcard folder (otherwise you need to change the commands appropriately and might need to fix cyanogen boot image too).
Download 3 files by the links above and upload to internal sdcard of your device. Connect to your device via ADB and run ADB shell, or type the next commands in terminal emulator:
Code:
# become root
su -
# go to external sdcard to create recovery backup
cd /mnt/extSdCard
dd if=/dev/block/mmcblk0p6 of=./recovery.img
# go to internal sdcard folder
cd /mnt/sdcard
# unpack partition images - each is 1Gb of disk space
gunzip ./system.img.gz
gunzip ./data.img.gz
# write CM boot image to recovery partition
dd if=./cyanogen.img of=/dev/block/mmcblk0p6
# finish
exit
exit
Now you can reboot your device into recovery mode and see CyanogenMod booting.
Restoring native recovery:
If you got tired from CyanogenMod and/or would like to take back your recovery, please use the backup you've done before. Lets say it is placed on your external sdcard, then connect to your device via ADB and run ADB shell, or type the next commands in terminal emulator:
Code:
# become root
su -
# go to the folder with recovery backup
cd /mnt/extSdCard
# write recovery image over recovery partition
dd if=./recovery.img of=/dev/block/mmcblk0p6
Please let me know If I missed anything in my steps.
P.S. What I've changed in Cyanogen boot.img to make it using img files instead of partitions in form of patch: View attachment cyanogen_boot_img.patch. It is also necessary to create /host folder in initrd folder tree.
wow!!
it's really hard to be done xD
i thought it will be as easy as it was on my old Galaxy S2
all what i needed to do is to restart the phone and press home to boot to second Rom
i hope it's going to be easier soon
and thank you for you efforts toward our device Development
MoNsTeRmUk said:
wow!!
it's really hard to be done xD
Click to expand...
Click to collapse
Well, it is not as hard as it probably seems Download 3 files and overwrite recovery partition.
Probably I need to compose something like zip file for CWM or TWRP when I have free time... But if would be really nice if someone get it working too following current steps
X-Stranger said:
Well, it is not as hard as it probably seems Download 3 files and overwrite recovery partition.
Probably I need to compose something like zip file for CWM or TWRP when I have free time... But if would be really nice if someone get it working too following current steps
Click to expand...
Click to collapse
I really Appreciate your work here brother And as it seems our device is not getting much of the attention unlike other devices
And what i meant by hard is it's possible to be done without any mistakes , but i take sometime to do so and you need a computer every time you want to change the Rom so it's not a solution for every time use .
I wish you good luck and Thank you for your support
MoNsTeRmUk said:
I really Appreciate your work here brother And as it seems our device is not getting much of the attention unlike other devices
And what i meant by hard is it's possible to be done without any mistakes , but i take sometime to do so and you need a computer every time you want to change the Rom so it's not a solution for every time use .
I wish you good luck and Thank you for your support
Click to expand...
Click to collapse
Thanks for kind words Actually you don't need to have the computer to change ROM, you can type commands from terminal emulator directly from Android. I'm also thinking about creating small Android app which can be installed to each ROM and will be able to switch boot partition within one click.
Thanks for this superb work. Can't download last file ?
Please if can make someone flashable zip it would be great I am a noob but I want try this thanks again
Sent from my GT-N8000 using Tapatalk HD
other roms
Can I do this this with another rom
maro_X said:
Can I do this this with another rom
Click to expand...
Click to collapse
It is possible, but your another rom must be specially modified for this.
What rom are you talking about exactly?
Multi-boot solution
I've tired of writing images to boot partition every time I want to switch between native firmware and Cyanogen, so decided to compose a little program that I was talking before. So let me introduce you N8xx Boot Manager!
The idea:
You put your boot images files to some folder on your sdcard, lets say to /mnt/extSdCard/images/boot
And recovery boot images to /mnt/extSdCard/images/recovery
Now you run Boot Manager and select what you want to boot as normal boot or as recovery
As soon as you selected it, the application asks you if you would like to write this image to the appropriate partition (boot or recovery)
After successful writing it will ask you for booting from that partition, e.g. propose to reboot into your another rom or recovery
For sure all the settings like path where to keep images and boot/recovery partition names can be fixed appropriately to your device at the Settings tab
For sure the application requires root permissions, e.g. your device must be rooted. You can also check this from Settings tab
The application file: View attachment bootmanager-1.0.apk - feel free to install it to your device and use posting me bug reports
P.S. The only thing I've forgotten - the button to create native boot image file backup You still need to do it manually, sorry Hopefully in next release, if there be people interested in N8xx Boot Manager
P.P.S. Generally this program can be used for any device - just put correct images and correct boot partition names
P.P.P.S. Why N8xx and not N8xxx or N80xx? Because I've missed one symbol when typed application name in Android Studio and was too lazy to change that later :laugh:
N80xx Boot Manager
Updated version of N80xx Boot Manager: View attachment bootmanager-1.1.apk
Changelog:
Fixed application name
Fixed images path detection when no settings were changes
Added "Backup boot partiton" and "Backup recovery partition" buttons
Thus, now to install CM 10.2 as dual boot you don't need to go to ADB or terminal - just upload 3 img files to your device proper locations, installl boot manager apk, create stock boot/recovery partitions backup, then select what you want to boot and boot to that rom!
P.S. Going to update first post of this thread with steps based on Boot Manager, just would be nice if someone confirm that it works.
swamimahesh said:
Can't download last file
Click to expand...
Click to collapse
Re-uploaded.
I love u man
Finally alittle love for our device :crying:
Do I have to reinstall apps when booting to cm?
edit: I dont really understand the first step when you extract data and system.img. Can you explain more clearly the procedure?
edit2: did anyone do this dualboot successfully?
data.img.gz
Hi,
Thanks for this post !
The unpack data.img.gz don't work for me, an error occurs (with several softwares).
The md5 is ok.
Could you repost this file ?
TY.
:angel:
I can not use the n80xx boot manager app. It was failed to back up recovery or boot img. And it can not detect backup folders also. I am using revolution hd9 on n8000
Sent from my GT-N8000 using Tapatalk
netj said:
Hi,
Thanks for this post !
The unpack data.img.gz don't work for me, an error occurs (with several softwares).
The md5 is ok.
Could you repost this file ?
TY.
:angel:
Click to expand...
Click to collapse
Looks like file hosting has disk issues thus my files become broken. System.img re-uploaded already. Now please try that View attachment data.img.gz and let me know if it works for you.
muop_92 said:
I can not use the n80xx boot manager app. It was failed to back up recovery or boot img. And it can not detect backup folders also. I am using revolution hd9 on n8000
Sent from my GT-N8000 using Tapatalk
Click to expand...
Click to collapse
I'm using the same Revolution HD 9.0 by mike1986 and it works for me. The backup might fail if backup folder is not available. By default it is trying to use external sdcard for backups, it is looking for /mnt/extSdCard/images/boot and /mnt/extSdCard/images/recovery paths for the purpose. Please create those folders if you don't have it, or change boot manager settings according to your thought where the backups should be. The boot and recovery folders should exist anyway, e.g. it is up to you to create them.
X-Stranger said:
I'm using the same Revolution HD 9.0 by mike1986 and it works for me. The backup might fail if backup folder is not available. By default it is trying to use external sdcard for backups, it is looking for /mnt/extSdCard/images/boot and /mnt/extSdCard/images/recovery paths for the purpose. Please create those folders if you don't have it, or change boot manager settings according to your thought where the backups should be. The boot and recovery folders should exist anyway, e.g. it is up to you to create them.
Click to expand...
Click to collapse
Where is /mnt ? I saw in my device only /storage/extSdCard
Sent from my GT-I8160 using Tapatalk 2
muop_92 said:
Where is /mnt ? I saw in my device only /storage/extSdCard
Click to expand...
Click to collapse
It's the same. External sdcard is available on both these paths as far as I know. You can change it otherwise in application settings tab.
Ok !
X-Stranger said:
Looks like file hosting has disk issues thus my files become broken. System.img re-uploaded already. Now please try that View attachment 2519204 and let me know if it works for you.
Click to expand...
Click to collapse
Hi,
It's Ok !
Thanks !
I have just modify the paths :
dd if=/dev/mmcblk0p6 of=./recovery.img --> dd if=/dev/block/mmcblk0p6 of=./recovery.img
dd if=./cyanogen.img of=/dev/mmcblk0p6 --> dd if=./cyanogen.img of=/dev/block/mmcblk0p6
:good:
{
"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"
}
MultiROM is one-of-a-kind multi-boot mod for Oneplus 3. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
Installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
Note 1: Your device must not be encrypted (hint: if you don't know what it is, then it is encrypted).
MultiROM has 2 parts you need to install:
Modified recovery - You cand download the unified IMG file here, or specific for OP3 from second post and use fastboot or TWRP or Flashify app to flash it.
MultiROM - download the unified ZIP file here, or specific for OP3 from second post and flash it in recovery.
Go into TWRP MultiRom settings and check "Enable No-KEXEC Workaround"
Your current rom will not be erased by the installation.
Download links for specific OP3 version are in the second post.
WORKAROUND for FCs
If you get FC's in your secondary, edit build.prop in that secondary's /system dir and set:
Code:
#ro.sys.sdcardfs=true
...to comment the line (don't delete, don't set to false).
Don't boot before editing this line (flash secondary, edit and then boot).
You can edit in your primary if you are rooted, looking into:
Code:
/sdcard/multirom/roms/<your_sec_rom>/system/build.prop
*You can also try using multiromfix.zip, available in this post, thx to @Startrek852 (to disable sdcardfs support in that secondary).
Adding ROMs
1. Android
Go to recovery, select MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 6.x after first boot takes 900+mb of space.
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Source code
MultiROM - https://github.com/MR-op3/multirom
Modified TWRP - https://github.com/MR-op3/android_bootable_recovery
MultiROM device tree - https://github.com/MR-op3/device_oneplus_oneplus3
Thanks a lot to Tasssadar for creating this awesome utility.
And to @nkk71 for the No-KEXEC workaround
MultiROM, Tool/Utility for the OnePlus 3
XDA:DevDB Information
MultiROM OP3/3T, Tool/Utility for the OnePlus 3
Contributors
martinusbe, BitOBSessiOn
Version Information
Status: Alpha
Current Beta Version: 3.0.3-2
Beta Release Date: 2017-02-12
Created 2016-07-10
Last Updated 2019-09-10
Reserved
Downloads
IT WILL NOT WORK WHEN ENCRYPTED
How-To by @bihariel
MultiRom for oneplus3
Recovery 08/03 Fixed usb-otg
multirom-20160814-v33b-UNOFFICIAL-oneplus3.zip
uninstaller
Update 11/26
Recovery 11/26
multirom-20161126-v33e-UNOFFICIAL-oneplus3.zip
Update 02/05/2017 op3
for new firmware 4.0.+, so older roms/kernels will not work on this!
AFH folder here
Update 02/20 by @BitOBSessiOn Unified
In post #1183
Update 03/10 Unified By BitOBSessiOn
recovery https://www.androidfilehost.com/?fid=745425885120713897
mr zip https://www.androidfilehost.com/?fid=817550096634752067
Update 08/07 by BitOBSessiOn
Post #1950
Flashable zip to fix your locksettings can be found here
MR Manager TBO 2016/08/17
Multirom Manager apk with oneplus support
Changelog:
- Darkened UI by @daveyannihilation #WhiteUImustDie
- Added icons for OOS, Tipsy, Tesla, Validus, Slim (needs the new zip flashed)
- Supports all Oneplus devices, Redmi2, Lux unoffically (to use the icons, the MR maintainer will need to update his MR zip)
MR Manager TBO 2017/04/21
Multirom Manager apk with added oneplus3T support
Flash recovery
Flash multirom zip
Enable kexec workaround in TWRP mr settings
Enjoy!
Reserved
Please read all about the no-kexec workaround from the author directly, (to avoid duplicity and get latest information), thanks to @nkk71
http://forum.xda-developers.com/showpost.php?p=64248526&postcount=4
*Updated MultiROM Manager APK available here.
*FCs in secondaries should have been fixed in latest TWRP-MROM versions.
Thank you,
Hope someone can add support for Oxygen OS and a kernel with kexec support.
Hello, MultiRom does not recognize the recovery amends
bihariel said:
Thank you,
Hope someone can add support for Oxygen OS and a kernel with kexec support.
Click to expand...
Click to collapse
Its a first build, give me a minute, i have a family
jejemc said:
Hello, MultiRom does not recognize the recovery amends
Click to expand...
Click to collapse
i know
Great work bro :beer: :good:
Unreal work bro much alohas
And here we are!! Thanks a lot @martinusbe, working like a charm!
Superfast! Many thx! Can´t wait to get my oneplus3
Dope. Nice way to use cm13 if I need dash boot into oxygen OS awesome!!
Hey, booted into a secondary ROM and now Oxygen is throwing an "incorrect pattern" error. I remember there were some files to delete to fix this, but I can't remember which ones. (Maybe add it to the OP to prevent confusion?) Thanks for your time!
cunc-cam said:
Hey, booted into a secondary ROM and now Oxygen is throwing an "incorrect pattern" error. I remember there were some files to delete to fix this, but I can't remember which ones. (Maybe add it to the OP to prevent confusion?) Thanks for your time!
Click to expand...
Click to collapse
I am unable to boot OxygenOs, what process did you folowed?
And for the incorrect patern just go to twrp- file manager, navigate into /data/system and delete the files:
password.key
pattern.key
locksettings.db-wal
locksettings.db-shm
locksettings.db
bihariel said:
I am unable to boot OxygenOs, what process did you folowed?
And for the incorrect patern just go to twrp- file manager, navigate into /data/system and delete the files:
password.key
pattern.key
locksettings.db-wal
locksettings.db-shm
locksettings.db
Click to expand...
Click to collapse
Thanks so much! By not being able to boot oxygen, do you mean as secondary or as primary? It must be unencrypted. Beyond that I don't know. It might be harder as secondary, I don't know if it would encrypt itself again.
I can boot into oxygen when it's the primary os through the given method, but it does take a few seconds of black before the boot animation shows.
cunc-cam said:
Thanks so much! By not being able to boot oxygen, do you mean as secondary or as primary? It must be unencrypted. Beyond that I don't know. It might be harder as secondary, I don't know if it would encrypt itself again.
I can boot into oxygen when it's the primary os through the given method, but it does take a few seconds of black before the boot animation shows.
Click to expand...
Click to collapse
My phone is decrypted and oxygen as primary. But i cant boot secondary roms, it always shows me the boot menu over and over.. when i select secondaries to boot.
I was able to boot only one time a sacondary rom. Must be there something am doing wrong.
bihariel said:
My phone is decrypted and oxygen as primary. But i cant boot secondary roms, it always shows me the boot menu over and over.. when i select secondaries to boot.
I was able to boot only one time a sacondary rom. Must be there something am doing wrong.
Click to expand...
Click to collapse
Huh. Be sure you checked the custom recovery setting related to kexec, I don't think that is supported on our device. Other than that, I'm as clueless as you
Its checked kexec warkaround. Injected sector boot. When i select secondary to boot, the phone reboots but it always goes back to boot menu... Will investigate a bit more...
touchscreen does not work on boot menu
Huge thanks for this port @martinusbe
FYI, I've tried all these roms as secondary, using the K-exec workaround. All are working very fine (device decrypted)
Beanstalk
ResurrectionRemix
Slim
Tipsy
Bliss
Thank you !
Edit : Just tried the MM apk, and it does not see the MM recovery, even tho it's already installed
Have you been in touch with Tassadar to have it official ?
bud77 said:
Huge thanks for this port @martinusbe
FYI, I've tried all these roms as secondary, using the K-exec workaround. All are working very fine (device decrypted)
Beanstalk
ResurrectionRemix
Slim
Tipsy
Bliss
Thank you !
Edit : Just tried the MM apk, and it does not see the MM recovery, even tho it's already installed
Have you been in touch with Tassadar to have it official ?
Click to expand...
Click to collapse
does touchscreen working for you?
***BOOST VARIANT ONLY*** ***BOOST VARIANT ONLY*** ***BOOST VARIANT ONLY***
CLEAR/DELETE DALVIK-CACHE FOLDER FROM "/data/dalvik-cache" IN ROOT EXPLORER OR TWRP AFTER INSTALLING BOOT IMAGE TO ALLOW SYSTEM TO ADJUST
##FLASH THE LATEST SUPERSU ZIP BELOW##
P.S. I NOTICE IT IS NO LONGER SYSTEM-LESS MODE. SO WE CAN TRIM THE SUPERSU SYSTEM-LESS CONTENT FROM THE RAMDISK.
Tweaked the contents of the boot image to allow for faster boot and better runtime performance. I use it as my daily driver. App performance is snappier. Only for the Boost Desire 626s. Unzip and flash with Flashify, TWRP, or your choice of image flasher. I also added some optimization scripts to supplement the boot image. Run them with Smanager, Root Explorer or in the terminal. Also here is a zip 601626SPIEFIX.zip that when flashed in TWRP recovery will allow the system to run non-pie executables and it works great. You'll be able to run custom binaries without any issue or error. All zips in this thread are the latest.
If you have ISSUES WITH DATA SPEEDS in certain areas, especially if you tether, GO INTO THE DIALER and DIAL *#*#4636#*#* then ACCESS PHONE INFORMATION and SELECT CDMA auto (PRL) UNDER SET PREFERRED NETWORK TYPE. LTE seems to be problematic in certain areas with speeds dropping to 150kbps and with this solution you'll be getting about 600 to 700kbps so at least it'll be a gain until you get into an area with better LTE coverage. In a good coverage area, I get download speeds of up to 5 to 7 mbps with LTE on, but in bad areas, CDMA works better. If you want to tether with a wireless third party solution make sure to run in a terminal window or adb shell as root : pm disable com.htc.tetheringguard
DOWNLOAD BOOT IMAGE: http://forum.xda-developers.com/attachment.php?attachmentid=3917986&d=1477604429
DOWNLOAD SUPERSU BETA: https://download.chainfire.eu/1009/SuperSU/SR2-SuperSU-v2.78-SR2-20161029143931.zip?retrieve_file=1
DOWNLOAD SCRIPTS: http://forum.xda-developers.com/attachment.php?attachmentid=3863279&d=1472880351
DOWNLOAD PIE FIX: http://forum.xda-developers.com/attachment.php?attachmentid=3844539&d=1471383163
DOWNLOAD BOOT IMAGE TOOL : http://forum.xda-developers.com/attachment.php?attachmentid=3917995&d=1477605263
DOWNLOAD HTC DRIVERS AND MINIMAL ADB + FASTBOOT: http://forum.xda-developers.com/attachment.php?attachmentid=3868562&d=1473328405
ANDBLOCKDEV.sh from scripts zip will speed up file input and output speeds, its contents have been incorporated into the boot image so the scripts files are for your own archival.
The zip DESIRE626SIMGTOOL.zip contains the android image kitchen and the 6.0.1 Boost Desire 626S boot image contents already extracted into two folders split_img and ramdisk with recent modifications. Enjoy!
http://www.vysor.io/ is a great tool to control your android device from a computer within chrome. You should try it out.
I provided a zip named HTCDrivers.zip containing the installation for both fastboot and adb drivers for the Boost Desire 626S, and minimal adb and fastboot. This will help you connect your device up with Vysor.
COPY the FILES; fastboot.exe, adb.exe, AdbWinUsbApi.dll and AdbWinApi.dll FROM - C:\Program Files (x86)\Minimal ADB and Fastboot - TO - C:\Windows\System32 - AND - C:\Windows\SysWOW64
Once you have installed the drivers for HTC devices,
and copied the minimal adb and fastboot files specified above to both system folders, you should be able to run adb commands without a problem by just opening a command prompt as administrator,
and RUNNING the command:
adb devices
- to start the adb server. This will allow connection with Vysor.
##########
For those who prefer nightbreed813's 6.0.1 slim rom version, I uploaded 601VPNDIALOGSFIX.zip to fix the issue with authorizing VPN clients, but first YOU HAVE TO CREATE /system/priv-app/VpnDialogs in Root Explorer or any other root filesystem browser, then reboot to TWRP recovery and flash the zip.
DOWNLOAD VPNFIX : http://forum.xda-developers.com/attachment.php?attachmentid=3860930&d=1472669879
##########
Also, you can get your MSL/SPC security code easily.........
Use the info in this thread to get your MSL/SPC security code so you can write new values to NV entries in the modem. Some values are locked but you can change the BC config for both LTE and CDMA so that would at least be helpful.
INFO HERE: http://forum.xda-developers.com/spri...k-sim-t3314755
##########
Android settings can be changed in the terminal for three namespaces; system, global and secure.
In the terminal run:
settings list system
settings list global
settings list secure
For each namespace all associated settings and their values will be listed. To change a setting type:
settings put system setting_name_here value_here
settings put global setting_name_here value_here
settings put secure setting_name_here value_here
##########
{
"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"
}
Look now has working VPN......
***BOOST VARIANT ONLY*** ***BOOST VARIANT ONLY*** ***BOOST VARIANT ONLY***
anthonykb said:
Tweaked the contents of the boot image to allow for faster boot and better runtime performance. I use it as my daily driver. App performance is snappier. Only for the Boost Desire 626s. Unzip and flash with Flashify, TWRP, or your choice of image flasher. I also added some optimization scripts to supplement the boot image. Run them with Smanager, Root Explorer or in the terminal. Also here is a zip 601626SPIEFIX.zip that when flashed in TWRP recovery will allow the system to run non-pie executables and it works great. You'll be able to run custom binaries without any issue or error. All zips in this thread are the latest.
Click to expand...
Click to collapse
Will this run on the Metro Variant?
As far as I know no but you can try in case it might.
Enter these commands in a new terminal window:
cd /dev/block/platform/soc.0/7824900.sdhci/by-name
dd if=boot of=/sdcard/backup.img
The backup boot image can be flashed from the sdcard in TWRP recovery if the device fails to boot into the system after flashing the boot image contained in the zip in the attachments.
Is there anyway you would be able to make one for the metro Variant if i upload my boot image?
MetroPCS Boot Image
GotHeart said:
Is there anyway you would be able to make one for the metro Variant if i upload my boot image?
Click to expand...
Click to collapse
Did you try unzipping the boot image and flashing it already? I don't think it could work that way. I would do it if I had the metro version myself.
anthonykb said:
Did you try unzipping the boot image and flashing it already? I don't think it could work that way. I would do it if I had the metro version myself.
Click to expand...
Click to collapse
Thats what im saying.if i upload my metro boot image would you be able to optimize it like you did before with the boost Variant?
GotHeart said:
Thats what im saying.if i upload my metro boot image would you be able to optimize it like you did before with the boost Variant?
Click to expand...
Click to collapse
I meant so you tried the boost version and it wouldn't boot?
anthonykb said:
I meant so you tried the boost version and it wouldn't boot?
Click to expand...
Click to collapse
No i havent tried it yet
GotHeart said:
No i havent tried it yet
Click to expand...
Click to collapse
Backup your kernel boot image to your sdcard and flash the boost version just to make sure.
cd /dev/block/platform/soc.0/7824900.sdhci/by-name
dd if=boot of=/sdcard/backup.img
Then unzip the 601bootimg.zip file with Zarchiver in the Play Store and flash the extracted boot image.
anthonykb said:
Backup your kernel boot image to your sdcard and flash the boost version just to make sure.
Click to expand...
Click to collapse
Okay ill do it now and let you know
The phone booted but it corrupted my sdcard,so i lost everything i had on there.
GotHeart said:
The phone booted but it corrupted my sdcard,so i lost everything i had on there.
Click to expand...
Click to collapse
Flash back the backed up boot image in TWRP and see if the sdcard mounts right. The mount point contained in the boost boot image is probably wrong for the the sdcard/emmc in the metropcs phone.
I did but my sdcard got corrupted so i was forced to format it.
GotHeart said:
I did but my sdcard got corrupted so i was forced to format it.
Click to expand...
Click to collapse
I'm so sorry the process turned out to be a dud for you I have the boost model myself. Hope you can recover your files with one of those forensic data recovery tools.
anthonykb said:
I'm so sorry the process turned out to be a dud for you I have the boost model myself. Hope you can recover your files with one of those forensic data recovery tools.
Click to expand...
Click to collapse
Its nothing important lol.any chance you can share what you did or how?
Use the Android Image Kitchen by osm0sis
GotHeart said:
Its nothing important lol.any chance you can share what you did or how?
Click to expand...
Click to collapse
Use the tool at the link below to unpack the image, make your modifications, and repack the image contents (The ramdisk and split_img folders.) It's available for Windows, Linux and Android. It's a simple process expect for knowing what you'd need to do to the image.
http://forum.xda-developers.com/showthread.php?t=2073775
anthonykb said:
Use the tool at the link below to unpack the image, make your modifications, and repack the image contents (The ramdisk and split_img folders.) It's available for Windows, Linux and Android. It's a simple process expect for knowing what you'd need to do to the image.
http://forum.xda-developers.com/showthread.php?t=2073775
Click to expand...
Click to collapse
My mistake i was in a hurry when i typed that last reply.
Im aware of how to unpack/repack boot images and i appreciate the link,but i was wondering what modifications that were made.if youd prefer not to share,i can upload my boot image if youd like to make the modifications yourself.im just trying to make this compatible with the metro version.
The same modifications done for the Boost Desire 626S might not work well for the MetroPCS version so upload the image you backed up yesterday as an attachment in a reply post and I'll work on it.
Thanks a ton!
MetroPCS Boot Image
GotHeart said:
Thanks a ton!
Click to expand...
Click to collapse
Run busybox top in the terminal on your phone and post some screenshots so I can see what might need to be done. We want to see what processes would be the culprit behind bogging down precious processor time and reducing the snappiness of the device in reacting to realtime input and handling current requests.
Instructions HERE.
TO DO:
- Other things mentioned in the wiki:
https://wiki.postmarketos.org/wiki/ASUS_Eee_Pad_Transformer_(asus-tf101)
VERSION INFORMATION (CHANGELOG)
A newer MATE image is available to download. Download it here or here.
Notes about this release:
v4.0
- Please read the updated instructions.
- Vast performance improvements overall (because it's using mainline 5.12.8 grate kernel).
- It's trickier to get it working, if you cannot follow the instructions please change to v3.0.
v3.0
- Firmware has to be renamed at first boot.
Do the following command as root or using sudo:
Code:
sudo ash rename-firmware.sh
Those who are migrating from older versions or want to know what this .sh file is:
https://wiki.postmarketos.org/wiki/ASUS_Eee_Pad_Transformer_(asus-tf101)
Follow the wiki, look into Wi-Fi section.
Reboot and done.
- Bluetooth is working, but only from terminal.
Code:
sudo hciconfig hci0 up
hcitool scan
hcitool pair, etc etc
- Buttons from trackpad are working, mousepad not yet.
- Updated kernel zip. Latest release here: https://github.com/antonialoytorren...rnel_zip/PostmarketOS-kernel-3.1.10-15-r2.zip
v2.0
- Changed icons (https://github.com/vinceliuice/vimix-icon-theme) and GTK (https://github.com/vinceliuice/vimix-gtk-themes) of XFCE. Now it is a modern XFCE.
- Removed second panel to save space.
- The XFCE Whiskermenu does not close when typing in onboard.
· Other things that will be included in the next release:
- Make a desktop shortcut opening a browser linking this XDA thread.
- Try to get trackpad working
v1.0
- Initial Release
Screenshots
MATE 4.0 (mainline PostmarketOS kernel)
See HERE.
https://imgur.com/a/Sf7BbFt
XFCE 2.0
{
"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"
}
XFCE
MATE
JWM
Dual Booting Android and PostmarketOS
You can only dual boot if you have installed postmarketOS in your microSD or SD Card. If not, you (probably) have to wipe your partition where postmarketOS is located for booting Android again.
Well, the easiest way to do dual boot is this:
In the sdcard folder or whatever folder you want, put the Android ROM zip and PostmarketOS' kernel zip.
Note: Be sure to run the TWRP version 2.8.1.1, otherwise Android won't flash.
The Android ROM (I'm using timduru's ROM: https://forum.xda-developers.com/eee-pad-transformer/development/rom-t3318496) can be downloaded here: https://downloads.timduru.org/android/tf101/K.A.T/KatKiss/6.0/dev/KatKiss-6.0_034.zip
The PostmarketOS' kernel zip can be downloaded here: https://github.com/antonialoytorrens/TF101-linux-images/raw/master/postmarketOS/kernel_zip/PostmarketOS-kernel-3.1.10-15.zip (has some issues with WiFi, flashing the blob using dd and adb is more recommended, https://wiki.postmarketos.org/wiki/ASUS_Eee_Pad_Transformer_(asus-tf101))
If you want Android, go to recovery and flash timduru's ROM.
If you want PostmarketOS, go to recovery and flash my kernel zip (please, disable signature verification when flashing)
Reserved
Reserved
aat596 said:
XFCE
MATE
Click to expand...
Click to collapse
WOW! I was in the last days researching something about it because I found this machine stopped and it has a good relative hardware to run light applications, really a waste not to have more updates.
I have a question: In this procedure, I would like to leave Linux in the internal memory, what would it be like to do this and leave it as a single system instead of Android?
And congratulations
be.sign said:
WOW! I was in the last days researching something about it because I found this machine stopped and it has a good relative hardware to run light applications, really a waste not to have more updates.
I have a question: In this procedure, I would like to leave Linux in the internal memory, what would it be like to do this and leave it as a single system instead of Android?
And congratulations
Click to expand...
Click to collapse
Having the PostmarketOS system in internal memory is harder and more difficult. You cannot install it on the bigger partition (the 30 GB one), I once tried and almost bricked my tablet because fails to boot due to media/ symlinks.
Unfortunately, you have to install it on /dev/block/mmcblk0p1 (533 MB partition).
I'm trying to make an usable small desktop image for /dev/block/mmcblk0p1 , XFCE is too big for that.
Nevertheless, you can enter recovery mode, do a Factory Reset and wipe Internal Memory to delete Android; then boot Linux from SDCard and use all available space to store your files.
If you want to make your image yourself, please look at https://wiki.postmarketos.org/wiki/Installation_guide and https://wiki.postmarketos.org/wiki/ASUS_Eee_Pad_Transformer_(asus-tf101)
be.sign said:
WOW! I was in the last days researching something about it because I found this machine stopped and it has a good relative hardware to run light applications, really a waste not to have more updates.
I have a question: In this procedure, I would like to leave Linux in the internal memory, what would it be like to do this and leave it as a single system instead of Android?
And congratulations
Click to expand...
Click to collapse
EDIT: A mini JWM image is available for download. It has the size to fit in the Asus TF101 first partition (/dev/block/mmcblk0p1). Download here: https://downloads.sourceforge.net/project/tf101-linux-images/postmarketOS/minijwm-postmarketOS-TF101.zip
Then execute exactly the following commands:
Code:
$ unzip minijwm-postmarketOS-TF101.zip
$ cd minijwm-postmarketOS-TF101
$ adb push blob-asus-tf101 /cache
$ adb push minijwm-tf101.img /sdcard
$ adb shell
# dd if=/cache/blob-asus-tf101 of=/dev/block/mmcblk0p4
# dd if=/sdcard/minijwm-tf101.img of=/dev/block/mmcblk0p1
Hello, thanks a lot for your sharing
I have an error with the XFCE image. When in try to boot from an external SDCard, following message occurs : "Initramfs-extras not found".
It work's without any problem when i boot from a custom built flashed on internal storage.
Do you have an idea from the causes ?
Raphzer said:
Hello, thanks a lot for your sharing
I have an error with the XFCE image. When in try to boot from an external SDCard, following message occurs : "Initramfs-extras not found".
It work's without any problem when i boot from a custom built flashed on internal storage.
Do you have an idea from the causes ?
Click to expand...
Click to collapse
This means that initramfs-asus-tf101-extra file is missing from pmOS_boot partition. All files located in this partition are strictly required.
EDIT: Btw, now I have download the XFCE image from sourceforge, flashed it into a new SD Card and boots fine.
aat596 said:
This means that initramfs-asus-tf101-extra file is missing from pmOS_boot partition. All files located in this partition are strictly required.
EDIT: Btw, now I have download the XFCE image from sourceforge, flashed it into a new SD Card and boots fine.
Click to expand...
Click to collapse
I don't understand why it doesn't work with sdcard. I have tried to flash my working build on the sdcard and the same error occurs
No file are missing on the sdcard, very strange.
Raphzer said:
I don't understand why it doesn't work with sdcard. I have tried to flash my working build on the sdcard and the same error occurs
No file are missing on the sdcard, very strange.
Click to expand...
Click to collapse
If it's your own working build then try these steps:
Code:
$ sudo pmbootstrap init (select asus-tf101 device, select [I]none[/I] when prompting graphical interface)
$ sudo pmbootstrap install && sudo pmbootstrap export
$ sudo dd if=/tmp/postmarketOS-export/asus-tf101.img of=/path/of/sdcard status=progress
$ adb push /tmp/postmarketOS-export/blob-asus-tf101 /cache
$ adb shell
# dd if=/cache/blob-asus-tf101 of=/dev/block/mmcblk0p4
And then insert your sdcard and reboot.
Hope this helps. I have extracted it from https://wiki.postmarketos.org/wiki/ASUS_Eee_Pad_Transformer_(asus-tf101). The only difference is flashing onto internal memory or the sd card.
EDIT: Are you using a reliable SD Card (Kingston, SanDisk, ...)? It could lead to random errors or not identify it if not.
This is what i did :/
Yep,i used this sdcard on a raspberrypi before.
I think he problem come from partition label name. As i have flash everything on internal memory and sdcard, i have 2 partition named pmos_boot. In the initramfs init script, there is multiple references to label name especially for loading initramfs-extras.
I will do some tests in that way.
Raphzer said:
This is what i did :/
Yep,i used this sdcard on a raspberrypi before.
I think he problem come from partition label name. As i have flash everything on internal memory and sdcard, i have 2 partition named pmos_boot. In the initramfs init script, there is multiple references to label name especially for loading initramfs-extras.
I will do some tests in that way.
Click to expand...
Click to collapse
Yes, it could be the reason. If you run into multiple problems, try to format /system in TWRP and then try it again with only the SD Card.
Btw, what version is your TF101? SBKv1 or SBKv2? I have SBKv1, that could be another problem (but I'm not sure, as the SD Card is partition-independent, and the kernel blob file is compatible for both versions)
Very nice image !
Just tested and looks very promising.
USB mouse and keyboard gets detected but don't work.
oink666 said:
Just tested and looks very promising.
USB mouse and keyboard gets detected but don't work.
Click to expand...
Click to collapse
Yep, that's one of the things mentioned in the TODO list in my guide (look at nearly the end)
We have to compile xf86-mtrack-driver to get it working (there's no such driver in Alpine repos)
I lack a bit of C knowledge to get it working (because it fails when compiling), so help is appreciated
Awesome work.
Any chance of dual boot?
Thank you
riptide981 said:
Awesome work.
Any chance of dual boot?
Thank you
Click to expand...
Click to collapse
You can only dual boot if you have installed postmarketOS in your microSD or SD Card. If not, you (probably) have to wipe your partition where postmarketOS is located for booting Android again.
Well, the easiest way to do dual-boot is this:
In the sdcard folder or whatever folder you want, put the Android ROM zip and PostmarketOS' kernel zip.
The Android ROM (I'm using timduru's ROM: https://forum.xda-developers.com/eee-pad-transformer/development/rom-t3318496) can be downloaded here: https://downloads.timduru.org/android/tf101/K.A.T/KatKiss/6.0/dev/KatKiss-6.0_034.zip
The PostmarketOS' kernel zip can be downloaded here: https://github.com/antonialoytorrens/TF101-linux-images/raw/master/postmarketOS/kernel_zip/PostmarketOS-kernel-3.1.10-15.zip
If you want Android, go to recovery and flash timduru's ROM.
If you want PostmarketOS, go to recovery and flash my kernel zip (please, disable signature verification when flashing)
XFCE 2.0
A newer XFCE image is available to download. Download it here: https://sourceforge.net/projects/tf101-linux-images/files/postmarketOS/xfce-postmarketOS-TF101-v2.0.zip
A little screenshot:
Notes about this release:
v2.0
- Changed icons (https://github.com/vinceliuice/vimix-icon-theme) and GTK (https://github.com/vinceliuice/vimix-gtk-themes) of XFCE. Now it is a modern XFCE.
- Removed second panel to save space.
- The XFCE Whiskermenu does not close when typing in onboard.
· Other things that will be included in the next release:
- Make a desktop shortcut opening a browser linking this XDA thread.
- Try to get trackpad working
v1.0
- Initial Release
Cool stuff - i tried the latest v2.0 image but ran into some issues:
If I have the keyboard docked it won't boot - it ends up with a blinking cursor top left of the screen and a bunch of errors are shown repeatedly during bootup.
Without the keyboard it boots correctly - keyboard wont work if attaching the keyboard after the system is up.
https://photos.google.com/share/AF1...?key=UUFNdVNfZ3N6X0ZOX054eDJLYWxWd0tPYThCV1dR
Any idea on what I could try to get this going?
gh05tface said:
Cool stuff - i tried the latest v2.0 image but ran into some issues:
If I have the keyboard docked it won't boot - it ends up with a blinking cursor top left of the screen and a bunch of errors are shown repeatedly during bootup.
Without the keyboard it boots correctly - keyboard wont work if attaching the keyboard after the system is up.
https://photos.google.com/share/AF1...?key=UUFNdVNfZ3N6X0ZOX054eDJLYWxWd0tPYThCV1dR
Any idea on what I could try to get this going?
Click to expand...
Click to collapse
I have just redownloaded zip file from sourceforge and I don't have this problem, so I don't know what it could be...
But there are some questions I would like to ask you:
- Does your keyboard work on Android? You can test it by flashing Timduru's Android image (https://downloads.timduru.org/android/tf101/K.A.T/KatKiss/6.0/dev/KatKiss-6.0_034.zip).
- Have you tried to do your own XFCE from scratch? https://github.com/antonialoytorrens/TF101-linux-images#doing-xfce-from-scratch. Hope this works, otherwise a patch for this kernel is needed.
- By the way, what version is your TF101? SBKv1 or SBKv2? I have SBKv1.