Instructions:
https://jolla.com/sailfishxinstall/
Download:
http://images.devaamo.fi/sfe/suzu/
thanks to all the guys that worked on this port.
Kernel source:
https://github.com/mer-hybris/android_kernel_sony_msm
This make_ext4fs works for flashing on macOS
For some reason with this build the system-icons vanish for me after restarting the device once :/
I had much better results using this build.
Also by default (at least with the image I linked) only two of the 6 cpu-cores are enabled. To fix that one must add this under the init-section of the /init.loire.pwr.rc file and reboot (All credit for this go to abranson from the #sailfishos-porters irc).
Thanks for this port! are you planning to continue building for Xperia X or is a test build before official release?
Enviado desde mi F5121 mediante Tapatalk
keep going till then, also ive updated the above link
how flash it?
FuLiterary said:
how flash it?
Click to expand...
Click to collapse
read the first post
FuLiterary said:
how flash it?
Click to expand...
Click to collapse
make sure when you are flashing sailfish support only F5121 and does not support sdxc
Hello, friend! I am a Chinese user, I do not understand the tutorial, there is no mor
Jozinek said:
so only Linux or MacOS too?
Click to expand...
Click to collapse
Flashing works on macOS too. You just need to use the make_ext4fs I linked instead of the one linked on top.
janeliang34 said:
Hello, friend! I am a Chinese user, I do not understand the tutorial, there is no mor
Click to expand...
Click to collapse
extract the tar, open a terminal inside the extracted folder and run ./flash.sh
One question. Zip file with AOSP should be moved intact or only vendor folder from inside it?
Seems it has to be whole .zip.
Jozinek said:
i never make something like this in MacOS (i have Macbook Air, but also with Windows), can you write step by step how to make it. This is something totally new for me (i flashed hundreds of XPERIA smartphones, i have Emma tool, but never try this...)
Click to expand...
Click to collapse
Sure thing
First of all your bootloader needs to be unlocked. I'm assuming you already did that but if not you should read about backuping your drm-keys because otherwise they can't be recovered after unlocking your bootloader unless you do that.
If you don't have fastboot installed yet follow this guide.
After that download the first file linked at the top of this thread.
Unpack the archive (if you can't open it I recommend "the unarchiver" from the app-store).
Place both this file and the zip from the third link at the top in the unpacked folder (in the path where the flash.sh is). Don't unpack the .zip file!
After that open a terminal and navigate to your unpacked folder (if you don't know how to do that google for "terminal tutorial mac").
Run
Code:
chmod +x flash.sh
chmod +x make_ext4fs
to mark the flash-script and the make_ext4fs-file as executable.
Boot your device into fastboot mode (hold volume up while it's turned off and plug in your usb-cable) and finally run
Code:
./flash.sh
to install sailfishOS on the device.
If there is a "hybris-recovery.img" file in the directory (can't quite remember if that's the case with this build) also run
Code:
fastboot flash recovery hybris-recovery.img
to install a sailfishOS specific recovery.
After that you can reboot your device and enjoy Sailfish OS
@Jozinek
You didn't unpack the .tar.bz, inside are all files needed to flash. Than You have to move make_ext4fs, AOSP.zip and flash.fs into created (by unpacking) folder and start/cd Terminal there.
Jozinek said:
Edit3 - it worked now, it was bad make_ext4fs, thanks all of you
Click to expand...
Click to collapse
So that means you are doing a review on YouTube, right?
Friend, is there a tutorial for Windows installation? To be more detailed, this is my first contact
janeliang34 said:
Friend, is there a tutorial for Windows installation? To be more detailed, this is my first contact
Click to expand...
Click to collapse
Right now there is no windows support. The final build (which will be officially sold by Jolla) will make windows-installation possible.
If you know your way around cygwin you could probably get it to flash using windows (other than the flash.sh script there's nothing *nix-exclusive).
Is the rom stable enough for daily use ? and is Alien Dalvik available in this rom to run Android apps ?
no android dalvik or any software that needs license, this version is just community version like aosp without play store.
when flashing there's error make_ext4fs: no such file or directory, when i use the second one there's error: wrong exec format
Related
Hello all you Triple-Booters out there! I would like to introduce to you:
Convert2Dualboot-SD Tool
What is this you ask?
This is a little tool that I've put together that will convert any standard flashable roms for our Nook Color to be DualbootSD compatible. No more waiting on my lazy arse to update you guys!!! I used APK manager as a base for my script. I've written 3 different versions that will run on Linux, OSX and Android. All neccesary binaries are included with each version.
Click to expand...
Click to collapse
Can I use any kind of flashable zips?
Yes and no. You could use any standard flashable "rom" or "gapps" zips only.
Click to expand...
Click to collapse
How do I use it?
You drop a standard rom .zip into a "rom-to-modify" folder. Then execute a shell script that will give you an option to convert it for flashing to Primary or Alternate boot on the DualbootSD.
Click to expand...
Click to collapse
Can I use any CWM Recovery for flashing?
Absolutely not! Only use the CWM Recovery that was included with the DualbootSD.
Click to expand...
Click to collapse
Will you be updating this to add new features and stuff?
Not sure what features I can add, but you can always check the CHANGE LOG in post 3.
Click to expand...
Click to collapse
Can you give us step by step directions on how to use this?
Of course! See second post for more details.
Click to expand...
Click to collapse
***Disclaimer: Usual disclaimer applies here as well... you use this at your own risk, I am not responsible for anything that happens to any of your devices. You assume all responsibility when using this tool.***
Credits:
Daneshm90 for the APK Manager Script I used as a base
Pinako/Inportb/Jyio/Boss! - for his Android binaries
DizzyDen - for porting this over to DOS and his many ideas to get the script to where it's at
HacDan - for some bash guidance
If I forgot someone else, please notify me.
Convert2Dualboot-SD Tool-README
Convert2Dualboot-SD-Linux v1.4
DOWNLOAD
*C2DSD=Convert2Dualboot-SD*
1-Extract the zip file you just downloaded anywhere on your system
2-In the C2DSD folder, there are 2 folders called "modify-for-pri" and "modify-for-alt". Copy your rom.zip and/or gapps.zip file into its respective folder. No need to rename the file as long as it has a .zip extension.
3-Open up terminal and cd into Convert2Dualboot-SD-Linux
4-At the termninal prompt execute the C2DSD script
Code:
$ sh convert*
5-This will give you a menu where you can choose to modify the "rom" and/or "gapps" for either Primary or Alternate boot. It will also give you an option to clear out recently modded zips. Now with option to mod both ROM & GAPPS on the fly. Just place both files inside either "modify-for-pri" or "modify-for-alt" and choose the option to modify both from the menu.
6-Choose your option and wait while it does its thing.
7-Once it's finished you can exit the program by choosing "0"
8-Now browse to the C2DSD folder and you can find your DualbootSD modded rom file either in "Primary-Mod" or "Alternate-Mod" depending on your earlier selection.
9-Copy that file to the /sdcard partition of your DualbootSD
10-Boot to CWM Recovery that is included with the DualbootSD
11-Flash and enjoy!
Click to expand...
Click to collapse
------------------------------------------------------------------------------------------
Convert2Dualboot-SD-OSX v1.4
DOWNLOAD
*C2DSD=Convert2Dualboot-SD*
1-Extract the zip file you just downloaded anywhere on your system
2-In the C2DSD folder, there are 2 folders called "modify-for-pri" and "modify-for-alt". Copy your rom.zip and/or gapps.zip file into its respective folder. No need to rename the file as long as it has a .zip extension.
3-Open up terminal and cd into Convert2Dualboot-SD-OSX
4-At the termninal prompt execute the C2DSD script
Code:
$ ./convert*
5-This will give you a menu where you can choose to modify the "rom" and/or "gapps" for either Primary or Alternate boot. It will also give you an option to clear out recently modded zips. Now with option to mod both ROM & GAPPS on the fly. Just place both files inside either "modify-for-pri" or "modify-for-alt" and choose the option to modify both from the menu.
6-Choose your option and wait while it does its thing.
7-Once it's finished you can exit the program by choosing "0"
8-Copy that file to the /sdcard partition of your DualbootSD
9-Boot to CWM Recovery that is included with the DualbootSD
10-Flash and enjoy!
Click to expand...
Click to collapse
------------------------------------------------------------------------------------------
Convert2Dualboot-SD-Android v1.4
DOWNLOAD
*C2DSD=Convert2Dualboot-SD*
1-This will allow you to modify the zip files directly on your Nook
2-Extract the zip file you just downloaded to the root of your DualbootSD /sdcard partition.
3-The folder should be named c2dsd
4-In the c2dsd folder, there are 2 folders called "modify-for-pri" and "modify-for-alt". Copy your rom.zip or gapps.zip file into its respective folder. No need to rename the file as long as it has a .zip extension.
5-Open up any Terminal Emulator and cd into the c2dsd folder which should be "/sdcard/c2dsd"
6-At the termninal prompt execute the C2DSD script
Code:
$ su
# sh convert*
7-This will give you a menu where you can choose to modify the "rom" and/or "gapps" for either Primary or Alternate boot. It will also give you an option to clear out recently modded zips. Now with option to mod both ROM & GAPPS on the fly. Just place both files inside either "modify-for-pri" or "modify-for-alt" and choose the option to modify both from the menu.
8-Choose your option and wait while it does its thing.
9-Once it's finished you can exit the program by choosing "0"
10-Now you can choose to boot to CWM Recovery that is included with the DualbootSD
11-Choose "install zip from sdcard" and browse to either "Primary-Mod" or "Alternate-Mod" depending on your earlier selection.
12-Flash and enjoy!
Click to expand...
Click to collapse
------------------------------------------------------------------------------------------
Convert2Dualboot-SD-DOS v1.3
DOWNLOAD
*C2DSD=Convert2Dualboot-SD*
1-Extract the zip file you just downloaded anywhere on your system
2-In the C2DSD folder, there are 2 folders called "modify-for-pri" and "modify-for-alt". Copy your rom.zip and/or gapps.zip file into its respective folder. No need to rename the file as long as it has a .zip extension.
3-Open up command window and cd into Convert2Dualboot-SD-DOS or create a shortcut on your desktop
4-At the command prompt execute the C2DSD script
Code:
convert2dualboot-sd-dos
5-This will give you a menu where you can choose to modify the "rom" and/or "gapps" for either Primary or Alternate boot. It will also give you an option to clear out recently modded zips. Now with option to mod both ROM & GAPPS on the fly. Just place both files inside either "modify-for-pri" or "modify-for-alt" and choose the option to modify both from the menu.
6-Choose your option and wait while it does its thing.
7-Once it's finished you can exit the program by choosing "0"
8-Copy that file to the /sdcard partition of your DualbootSD
9-Boot to CWM Recovery that is included with the DualbootSD
10-Flash and enjoy!
Click to expand...
Click to collapse
And that's all she wrote... well he, being me.
If I've helped in anyway. Don't hesitate to hit the thanks button.
Change log:
v1.4 (6/8/2012)
-Fixed gapps being zipped with rom when converting rom & gapps together
-Added SDCacheMount to converted roms (see the SDCacheMount thread for more info)
-Fixed mkimage binary executing error for Linux version
-No DOS update yet.... DizzyDen?????
-Thanks goes to xda user "shumash" for the SDCacheMount addition into the script
v1.3a
-Mkimage error on Android Script fixed.
-Mkimage is dependent on 'libmusl.so' which I did not include and linked in the tools folder. I overlooked this tidbit because I had "BOTBREW" installed on my system so it never complained about linking to it.
v1.3
-I effed up on the script!
-RASTAVIPER kept asking me about issues with his gapps. Apparently the mod for Gapps Alt Boot had the wrong mount points inserted into the updater script. NOW I SEE IT!
-Also in the DOS version. Prep of ROM Alt Boot had the wrong mount points as well. Sorry guys.
-It's been fixed and uploaded. Please don't use v1.2 anymore. Thanks.
v1.2
-Changed up UI layout of script: Please re-read README from post 2 above for edited instructions.
-Edited script to speed up mod process (Thanks DizzyDen!)
-Added option to mod both "ROM & GAPPS" on the fly
-Android version now has a tool.img file. This makes modding quicker and safer.
-Added DOS version ported by DizzyDen! (Thank you sir!)
-Modding for EMMC dualboot version in the works???? (That's if you guys want it)
v1.1
-Added gapps option
-Cleaned up some scripting behaviors
v1.0
-Initial release
Well.. after some thought, it really didn't make sense to release this without an option to mod gapps for the DualbootSD. I mean what good is a rom without gapps?!
Convert2Dualboot-SD v1.1 is up if anyone wants to try.
Check post 3 for all changlogs.
Thanks,
Racks
Taking advantage of the opportunity to try something new, I made a dual-boot card for my sister-in-law.
This is cool. I actually haven't tested the card yet as I have my device flashed to internal and have modded the recovery some. I haven't backed up any of the changes I made (I know, I know) and don't want to have to do it again.
I may try updating the card now that you've included gapps, though. I hadn't made a bootable card since I first rooted this thing, and to be honest it was by accident even that time. So I was wondering how to get gapps, was thinking about setting an alt-recovery just for that.
But anyway, I hadn't looked at how to do the gapps yet, maybe it was easier than that. But this seems even easier.
Cool, man! I bet the dual/triple booters will love being able to make their own updates. The experience I had last night couldn't have been easier. My wife got me and her sister the Nooks at the same time, I am excited for her to see what I have been talking about the last six months.
I will be sure to try this once my NC gets here. Thanks!
Racks,
Works great but there's an odd 0 byte file in the DB zip called ^[email protected] Is that an artifact and can I just delete it?
shumash said:
Racks,
Works great but there's an odd 0 byte file in the DB zip called ^[email protected] Is that an artifact and can I just delete it?
Click to expand...
Click to collapse
DB zip? Sorry, but what are you referring to with that?
And could you also let me know which one you used? OSX, Linux, Android?
Edit: That might just be the stupid __MACOSX hidden folder that osx likes to include Forgot to exclude that and the .gitignore file when zipping. Although they aren't detrimental to running the C2DSD Tool, you can choose to delete them if you wish.
Thanks,
Racks
Thanks a lot Racks... great work... we'll get together and sort out the windows based version... can include it in your work here... or as another feature of the IMEI generator.
DizzyDen said:
Thanks a lot Racks... great work... we'll get together and sort out the windows based version... can include it in your work here... or as another feature of the IMEI generator.
Click to expand...
Click to collapse
Awesome to hear! Was hoping you would jump in.
We'll hook up and get the Windows based version here as well as incorporate it into your IMEI generator.
Thanks!
Racks
racks11479 said:
Awesome to hear! Was hoping you would jump in.
We'll hook up and get the Windows based version here as well as incorporate it into your IMEI generator.
Thanks!
Racks
Click to expand...
Click to collapse
Sounds like a plan... I just got in from work... and am off tomorrow.
DizzyDen said:
Thanks a lot Racks... great work... we'll get together and sort out the windows based version... can include it in your work here... or as another feature of the IMEI generator.
Click to expand...
Click to collapse
racks11479 said:
Awesome to hear! Was hoping you would jump in.
We'll hook up and get the Windows based version here as well as incorporate it into your IMEI generator.
Thanks!
Racks
Click to expand...
Click to collapse
+1 from a meathead windows user here.
Sent from my NookColor racks tripple boot using Tapatalk 2
racks11479 said:
DB zip? Sorry, but what are you referring to with that?
And could you also let me know which one you used? OSX, Linux, Android?
--SNIP--
Thanks,
Racks
Click to expand...
Click to collapse
Sorry for being vague. I meant the modded dualboot sd zip build. But I tried it again and it was fine, so let's say no more about it, eh?
On a related note, since you're so motivated now, how about creating those separate cache1 and cache2 partitions so that we don't have to wait so long to boot between the two?
Anyone who tried the new modding option and that would like to share with us which CM9 rom (nightly) did he convert and is working fine after conversion?
spdsl said:
+1 from a meathead windows user here.
Sent from my NookColor racks tripple boot using Tapatalk 2
Click to expand...
Click to collapse
Was hoping to have something before I had to go to work this morning... didn't get it completed...
to keep as close as Racks' I will have a DOS batch file available sometime tonight...
True Windows GUI version will be available early in the week.
Keeping with Racks' desires... both will be open source and stored on his github... I use AutoIT for windows programming these things.
shumash said:
On a related note, since you're so motivated now, how about creating those separate cache1 and cache2 partitions so that we don't have to wait so long to boot between the two?
Click to expand...
Click to collapse
Racks, I just sent you a PM that might help with this issue.
shumash said:
Racks,
Works great but there's an odd 0 byte file in the DB zip called ^[email protected] Is that an artifact and can I just delete it?
Click to expand...
Click to collapse
UPDATE: I converted the latest Mirage build, and when I tried to flash it, Recovery complained that it wasn't a valid zip file. Checked it and the same weird file was in the converted flashable zip. When I ran the conversion a second time, all was good and it flashed as expected. I had deleted all the extraneous _MACOSX and .gitignore file stuff prior to running it the first time. BTW, the problem in the quoted post was when I converted an ICS build the first time, too. Racks, do you think that there is something that occurs the first time the script is run that is different on subsequent runs that might account for this?
Just installed nightly 28.4 without Opengl and then gapps which appeared in the folder Primary Mod after conversion.
After that I cant get inside shop.I click to open it and it gets me back to main menu.
Any ideas?Reflashing of gapps didnt work.
RASTAVIPER said:
Just installed nightly 28.4 without Opengl and then gapps which appeared in the folder Primary Mod after conversion.
After that I cant get inside shop.I click to open it and it gets me back to main menu.
Any ideas?Reflashing of gapps didnt work.
Click to expand...
Click to collapse
Primary mod is for Primary boot. Default primary boot was CM7, so I'm assuming you formatted /system1 & /data1 before flashing?
Could you also unzip the contents of the converted gapps zip. And check the updater script. All /system variables should be /system1.
-Racks
I didn't format anything before flashing. I thought this as an upgrade, so after conversion I just proceed to flashing.
Finally, I flashed your own gapps that you have at your dualboot topic and now everything is back to normal.
Unfortunately, even after this upgrade, I still continue to deal with FC issues of mail, Facebook and of other random apps.I think there is some problem with my card and CM9, since CM7 runs perfect from emmc or from same mem card.
Unleashed from my Revolutionized Desire HD
So there it is. It incorporates two workarounds:
gr_init() called twice to fix the black screen problem
small kernel patch to allow param.ko to update params.blk inside /mnt/.lfs before rebooting
This is very preliminary work. I can not provide any guarantee it will not brick your device or cause a rift in the space-time continuum (it hasn't bricked mine or caused a rift but that's statistically insignificant).
I recommend you flash this recovery with dd and not Odin/heimdall after rooting with the system.img method (see http://forum.xda-developers.com/showthread.php?t=2104638), but be careful with the partition number (for example if you forget the number 2 and type mmcblk0p1 you will end up rewriting your partition table, thus bricking your device).
Before flashing anything, consider making a backup of the original recovery partition (other partitions can be backed up as well: EFS, modemfs, etc. see http://forum.xda-developers.com/showthread.php?t=2032642)
Code:
dd if=/dev/block/mmcblk0p21 of=/sdcard/backup-recovery.img
Then install CWM:
Code:
dd if=/sdcard/recovery-clockwork-6.0.2.7-golden-2.img of=/dev/block/mmcblk0p21
or if you copied the file on the external sd:
Code:
dd if=/storage/extSdCard/recovery-clockwork-6.0.2.7-golden-2.img of=/dev/block/mmcblk0p21
Update: version 2 that works with both internal and external sdcard. If you want to use the external SD, it must be formated with one FAT32 partition (mmcblk1p1). Make sure to repartition/reformat your SD if this is not the case! This can be done in the systems parameters of the phone, or alternatively under Windows/Linux.
Here is an Odin flashable package made by spawk (thanks to him): http://forum.xda-developers.com/showpost.php?p=36962108&postcount=59 Contrary to the method above, flashing with Odin (or Heimdall) will increase your download count!
To reboot into recovery, you can either :
- use the vol-up + home + power combo, but it does not work on all phones (reason unknown)
- with stock, use ROM Manager to reboot into recovery
- with CM10, well simply select recovery when rebooting
- with adb enabled, run "adb reboot recovery"
If your current system fails to boot, and you need to get into recovery, and the three-button combo does not work, you can always reflash a known working system.img and use one of the methods above.
Adb sideloading does not seem to work. Need to investigate why
so just flash it? thats it? and we will have working display?
Can u provide more info? Becuase i think some users will not understand the procedure
Men can you provide the device tree and your changes on kernel so I can merge them on my repos?
Enviado desde mi GT-I8190 usando Tapatalk 2
OliverG96 said:
Men can you provide the device tree and your changes on kernel so I can merge them on my repos?
Click to expand...
Click to collapse
There are no kernel changes. I just used GT-I8190_JB_Opensource_Update1.zip with the golden_defconfig
You need to update graphics.c and android_reboot.c (attached). I will upload the device tree a bit later, need to clean it up first.
xd.bx said:
There are no kernel changes. I just used GT-I8190_JB_Opensource_Update1.zip with the golden_defconfig
You need to update graphics.c and android_reboot.c (attached). I will upload the device tree a bit later, need to clean it up first.
Click to expand...
Click to collapse
Thanks, I'll merge this on my repos, if you want we can work together on cm10
Enviado desde mi GT-I8190 usando Tapatalk 2
It gives me No such file or directory
1.)You need to make a good procedure to the first post. this is chaos.
what do u mean by updating graphics.c..... replacing by new one? and the other file location?
2.) What do u mean by : be careful with the partition number (for example if you forget the number 2 you will end up rewriting your partition table, thus bricking your device).
Shapeshift said:
You need to make a good procedure to the first post. this is chaos.
what do u mean by updating graphics.c..... replacing by new one? and the other file location?
Click to expand...
Click to collapse
There's a board define to specify a different graphics.c Just using it and copying the correct graphics.c will work...
Enviado desde mi GT-I8190 usando Tapatalk 2
and android reboot.c where do i copy both files.
Never mind I did it. However I've got an Error mounting /sdcard!
Shapeshift said:
and android reboot.c where do i copy both files.
Click to expand...
Click to collapse
I'm gonna push to cm gerrit the workaround to keeep android_reboot.c inside device tree
Enviado desde mi GT-I8190 usando Tapatalk 2
OliverG96 said:
Thanks, I'll merge this on my repos, if you want we can work together on cm10
Click to expand...
Click to collapse
I'd be glad to work with you on this, especially considering that you already are a cm developer (I'm not really used to gerrit)
Can i honestly ask you to make a procedure? like steps or something. i am not good at cwm and things
I am asking you : how to update graphics.c and android reboot.c ? plz help asap
Shapeshift said:
Can i honestly ask you to make a procedure? like steps or something. i am not good at cwm and things
Click to expand...
Click to collapse
Sure. First you need to root your phone with the system.img method you'll find in other threads.
Next, uncompress and copy the recovery.img on your SD card, which is then to be inserted in the phone.
Then you enable must adb debugging in the system preferences, and with the Android SDK installed on your PC, run "adb shell". If it says adb: command not found you'll have to find where the adb binary is, and use the full path (such as, "C:\Program Files\android-sdk\platform-tools\adb.exe" but that's an example, you must find what the proper path is).
Next after having run "adb shell" you enter "su" to obtain root privileges (you will get a warning prompt. simply answer yes). Finally, run "dd if=/sdcard/recovery-clockwork-6.0.2.7-golden.img of=/dev/block/mmcblk0p21" to install CWM, and then you can reboot into CWM after exiting the shell (use the "exit" command twice) with the command "adb reboot recovery".
Now regarding the two C files I posted, it is a matter of copying them into your CM10 tree.
graphics.c goes into bootable/recovery/minui/ (however it is better to use the BoardConfig to setup a device-specific graphics.c)
android-boot.c goes into system/core/libcutils/
This will only get you so far, you'll need for instance Oliver's device tree to compile golden.
hm. i have already adb and i have specified path in windows for it. so i can run it everywhere. my device is rooted and i have only one more question for you. Do i need external sd? cant i put it onto internal sd?
Shapeshift said:
hm. i have already adb and i have specified path in windows for it. so i can run it everywhere. my device is rooted and i have only one more question for you. Do i need external sd? cant i put it onto internal sd?
Click to expand...
Click to collapse
Yes, sure. Or use /tmp/ to store it temporarily (the file will go away after the next boot)
So I just found out something really cool, the stock (prebuilt) j4fs.ko and param.ko modules can be loaded along a 3.0.31 kernel built from source, which means it will be possible to simply use them instead of this android_boot ugly hack.
ok i have installed cwm. but it cant mount sdcard. try to fix. nothing is mountable. cant mount sdcard as well as backup folder
Just posting here to say a big thank you to all of you devs!
:good:
PS: And a small (silly) question:
as i 'm not using a pre-rooted ROM. What if I made an ODIN flashable tar.md5 of the original *.img? Wouldnt it work?
Description: Utility (hereinafter - the kitchen) to make changes to the firmware image for the Lenovo K900.
Operating System Requirements: Any Linux-like system (I recommend Ubuntu), any digit. For correct working kitchen must be installed packges: p7zip, p7zip-full, jdk, jre, python, ia32-libs.
Features: Removing the preinstalled Chinese software from the VibeROM firmwares; other firmware - manual; deodexing firmware; adding ROOT rights in firmware; editing build.prop; installing Google apps (* not verified), repacking the system.img.gz image.
Instructions for use:
- unpack the archive to any folder;
- Run the kitchen with console command ./kitchen.sh and enter the root password (required for file operations);
- Copy the file system.img or system.img.gz in a folder /in/;
- Enter 1 if throwing system.img.gz image archive folder in /in/, or go to step 2 if the folder /in/ drop files system.img;
- Type 2 to mount the image, while in the kitchen wearing the phrase "System: unmounted" will change to "System: mounted". The system is mounted in a folder /mount/;
Then simply describe the menu items:
3 - removes Chinese preinstalled software according file cn-apps in /scripts/ folder;
4 - "easier" firmware by deleting unnecessary files, animation off; applies mods - Record video to MP4, boot animation changed to "clipped " (you can change your folder /scripts/mod/);
5 - deodexing firmware (it takes quite a long time , up to 10 min);
6 - adding ROOT rights (used SuperSU 1.93). If you want to use a different version, you can replace the files in the /scripts/root/;
7 - editing build.prop file by using gedit;
8 - Set the Google apps light with a minimum set of software, you can further install more right already from Google Market (not tested);
9 - edited image packaging system system.img.gz. Ready to pick up the file from the folder /out/;
10 - unmount mounted image. Performed at the end of all operations with an editable manner;
0 - unpack inb firmware;
x - exit.
Download link:
http://forum.xda-developers.com/devdb/project/dl/?id=5359
Download mirror:
https://drive.google.com/folderview?id=0Bz3X7ZuowQimM3c0ZFV2QlZMR2c&usp=sharing
XDA:DevDB Information
Lenovo K900 kitchen, Tool/Utility for the Lenovo K900
Contributors
xxx-man-by
Version Information
Status: Testing
Stable Release Date: 2014-02-17
Created 2014-02-19
Last Updated 2014-06-07
What a great job！:good:
Amazing
Now its time to cook some ROM's
Lenovo K900 kitchen 1.21 beta
Released new version 1.21 beta
Whats new:
- Added support for firmware format INB (unpacking only);
- SuperSU binaries updated to version 1.93;
- Added support for complex tools with Android 4.3 (deodex, zipalign, optipng). Work is not very stable.
great, I hv prepared ubuntu and hv started cooking
Released new version 1.23
Whats new:
- Changed the script for implementation Root rights firmware (to fully support Android 4.3)
Just asking...
no kitchen for Windows7?
pjsplayez said:
Just asking...
no kitchen for Windows7?
Click to expand...
Click to collapse
No. Only for Linux-like OS, because Windows cannot work with images, mounting, rights etc...
Thank you i try it and install root Good Job
Just ask
xxx-man-by.. why not just "inb" file in "sdfuse" folder ?!. thanks before
Thank you, I am being to buy that device ^_^
Dual boot
Hello, anyone know how the best way to dual boot os in my laptop?
i want to boot windows 7 with ubuntu.
Hope anyone can give me guide or give me any link to make a dual boot.
help XXX-Man
i think the link is not working anymore.
REupload please
pjsplayez said:
help XXX-Man
i think the link is not working anymore.
REupload please
Click to expand...
Click to collapse
Ok. I`ll upload to the mirror. Please wait. DONE.
pjsplayez said:
Hello, anyone know how the best way to dual boot os in my laptop?
i want to boot windows 7 with ubuntu.
Hope anyone can give me guide or give me any link to make a dual boot.
Click to expand...
Click to collapse
if you need linux just for cooking, dont install it to harddrive.. just throwit on some usb drive and run it live..
use pendrivelinux or yumi to make live linux on usb.
xxx-man-by, if we have already the unpacked system folder like the VIBEROM Dev1418?
sev7en said:
xxx-man-by, if we have already the unpacked system folder like the VIBEROM Dev1418?
Click to expand...
Click to collapse
I do not understand what you mean.
xxx-man-by said:
I do not understand what you mean.
Click to expand...
Click to collapse
Good morning,
to start my kitchen, I download the original VIBEROM image file, redhookbay-ota-VIBEROM_V1.0_1418_DEV_K900.zip but if I extract it on the "IN" folder I haven't the .img packages to mount (e.g. the system folder is already unpacked):
Also, after that, I get only the system.img file but in other release I used before, e.g. the one for the VIVO, I had the way to pack directly the image to flash. Here which one is the next step?
Thank you,
sev7en said:
Good morning,
to start my kitchen, I download the original VIBEROM image file, redhookbay-ota-VIBEROM_V1.0_1418_DEV_K900.zip but if I extract it on the "IN" folder I haven't the .img packages to mount (e.g. the system folder is already unpacked):
Also, after that, I get only the system.img file but in other release I used before, e.g. the one for the VIVO, I had the way to pack directly the image to flash. Here which one is the next step?
Thank you,
Click to expand...
Click to collapse
redhookbay-ota-VIBEROM_V1.0_1418_DEV_K900.zip - this is ordinary zip file, K900 kitchen is not working with OTA zip archives. To start working with kitchen you need to put in the /in/ folder only system.img, system.img.gz, or any INB file (to unpack it). Only like this.
xxx-man-by said:
redhookbay-ota-VIBEROM_V1.0_1418_DEV_K900.zip - this is ordinary zip file, K900 kitchen is not working with OTA zip archives. To start working with kitchen you need to put in the /in/ folder only system.img, system.img.gz, or any INB file (to unpack it). Only like this.
Click to expand...
Click to collapse
thank you for getting me back sooner, with your unique Kitchen we are able to manage that files as well to repack them but when done how we get the final package to flash?
thanks once again for that
@MikeChannon, please delete this.
Deleted topic because I don't think about giving more support.
Use @SuperR. kitchen.
Reserved
ohhh thanks bro!!! great job
Enviado desde mi POCOPHONE F1 mediante Tapatalk
I want to use Linux. How to use?
Virus??!!
Why my windows 10 security center scaned the virus??!!
ClassiCTR said:
I want to use Linux. How to use?
Click to expand...
Click to collapse
Sorry, it's a Windows tool.
568060545 said:
Why my windows 10 security center scaned the virus??!!
Click to expand...
Click to collapse
Because batch file it's converted to .exe and thats why. Don't worry. It's safe.
Version updated to 1.1
Best performance
https://www.androidfilehost.com/?fid=6006931924117938149
JamFlux said:
Version updated to 1.1
Best performance
https://www.androidfilehost.com/?fid=6006931924117938149
Click to expand...
Click to collapse
hi bro, first thank you for the mighty work you do
i need to repack my rom to other format not to original format
zemzmi said:
hi bro, first thank you for the mighty work you do
i need to repack my rom to other format not to original format
Click to expand...
Click to collapse
Go to 01-Project folder, then temp folder and rename for the format you need: system.img, system.new.dat or system.new.dat.br, then restart application and recover the project.
JamFlux said:
Go to 01-Project folder, then temp folder and rename for the format you need: system.img, system.new.dat or system.new.dat.br, then restart application and recover the project.
Click to expand...
Click to collapse
thanks and good work :good:
possible virus detected
JamFlux said:
Because batch file it's converted to .exe and thats why. Don't worry. It's safe.
Click to expand...
Click to collapse
So then, Why is SUR.exe needed if Sur.bat works ok without it?
Bro, virustotal detects 8/69 threats of SUR.exe file:
https://www.virustotal.com/gui/file/68f8708f5f156caef86535cb132e82527eb08ead3facaf3f09c10ab28618670c/behavior/VirusTotal%20Jujubox
Behaviour of this file does these filesystem actions:
Code:
Processes Tree
2584 - factura.exe
148 - C:\Windows\system32\cmd /c C:\Users\<USER>\AppData\Local\Temp\D751.tmp\D752.bat C:\Users\<USER>\Downloads\factura.exe
2812 - mode con: cols=72 lines=13
WTH is factura.exe?
Similarly, SUR_v1.1u.7z is 13/51 detected by Virustotal.
najabi said:
So then, Why is SUR.exe needed if Sur.bat works ok without it?
Bro, virustotal detects 8/69 threats of SUR.exe file:
https://www.virustotal.com/gui/file/68f8708f5f156caef86535cb132e82527eb08ead3facaf3f09c10ab28618670c/behavior/VirusTotal%20Jujubox
Behaviour of this file does these filesystem actions:
Code:
Processes Tree
2584 - factura.exe
148 - C:\Windows\system32\cmd /c C:\Users\<USER>\AppData\Local\Temp\D751.tmp\D752.bat C:\Users\<USER>\Downloads\factura.exe
2812 - mode con: cols=72 lines=13
WTH is factura.exe?
Similarly, SUR_v1.1u.7z is 13/51 detected by Virustotal.
Click to expand...
Click to collapse
Hi @najabi
I used a tool to compile .bat to .exe, may be its a false positive. I use that program because it can add administrative privileges. But now I put administrative privileges to .bat inside. Just use .bat from here: https://github.com/jamflux/SUR/raw/master/SUR.bat
Can't open?
JamFlux said:
Hi @najabi
I used a tool to compile .bat to .exe, may be its a false positive. I use that program because it can add administrative privileges. But now I put administrative privileges to .bat inside. Just use .bat from here: https://github.com/jamflux/SUR/raw/master/SUR.bat
Click to expand...
Click to collapse
Hi JamFlux,
I tried to unpack a vendor .zip with the utility using the .bat but I got an error anyway.
I think it's best to use scripting commands than .exe binaries when possible, they are easier to spot and analyse. You can use administrative command promt aswell. Which tool do you use to make executables from .bat files? Is it from reputable sources?
najabi said:
Hi JamFlux,
I tried to unpack a vendor .zip with the utility using the .bat but I got an error anyway.
I think it's best to use scripting commands than .exe binaries when possible, they are easier to spot and analyse. You can use administrative command promt aswell. Which tool do you use to make executables from .bat files? Is it from reputable sources?
Click to expand...
Click to collapse
Hi
I'm using this tool:
https://bat-to-exe-converter.uptodown.com/windows
But now I'm using command promt inside .bat
Hope you can unpack vendor.img
Best regards
JamFlux said:
Hi
I'm using this tool:
https://bat-to-exe-converter.uptodown.com/windows
But now I'm using command promt inside .bat
Hope you can unpack vendor.img
Best regards
Click to expand...
Click to collapse
In my opinion, I don't think it's a reputable tool, the developer's webpage doesn't work, and uptodown is not exactly a trusted source.
We must be extra careful these days as they put virus everywhere in executables.
That SUR.exe file is detected as infected by several engines, I think you should consider removing it from the tool.
najabi said:
In my opinion, I don't think it's a reputable tool, the developer's webpage doesn't work, and uptodown is not exactly a trusted source.
We must be extra careful these days as they put virus everywhere in executables.
That SUR.exe file is detected as infected by several engines, I think you should consider removing it from the tool.
Click to expand...
Click to collapse
I remove totally the executable in new version. Thanks.
New version 1.2 supporting deodexing from android 8.0 to android Q.
Download: https://www.androidfilehost.com/?fid=6006931924117945116
@JamFlux mate i have one question. Can I also unpack, edit (removing or adding apps, e.g.) and repack MIUI ROMs? Thx!
Sent from my [device_name] using XDA-Developers Legacy app
Is there any kind of tool FOR Android that can extract a boot image from a payload.bin? Or do you basically need a PC for the task? I do it all the time from my desktop, but a tool to do it on my phone itself would be super convenient if it exists somewhere. Thanks guys!
H4X0R46 said:
Is there any kind of tool FOR Android that can extract a boot image from a payload.bin? Or do you basically need a PC for the task? I do it all the time from my desktop, but a tool to do it on my phone itself would be super convenient if it exists somewhere. Thanks guys!
Click to expand...
Click to collapse
There's a high likelihood that Termux can do it. If you have a payload.bin that you can link me I'll try it. I think it can run these python scripts assuming there's nothing wrong with them.
https://github.com/cyxx/extract_android_ota_payload
Spaceminer said:
There's a high likelihood that Termux can do it. If you have a payload.bin that you can link me I'll try it. I think it can run these python scripts assuming there's nothing wrong with them.
https://github.com/cyxx/extract_android_ota_payload
Click to expand...
Click to collapse
Here's a download link for the latest OxygenOS build for a OnePlus 7 Pro: https://www.oneplus.com/support/softwareupgrade/details?code=PM1574156267635
I tried to run the python script with Termux, it said it couldn't execute the script, permission was denied. I granted it superuser too. Try it out, I may have done it wrong. Thanks man! [emoji16]
EDIT: You'll have to extract the payload.bin, that link is to a full flashable rom zip.
H4X0R46 said:
Here's a download link for the latest OxygenOS build for a OnePlus 7 Pro: https://www.oneplus.com/support/softwareupgrade/details?code=PM1574156267635
I tried to run the python script with Termux, it said it couldn't execute the script, permission was denied. I granted it superuser too. Try it out, I may have done it wrong. Thanks man! [emoji16]
EDIT: You'll have to extract the payload.bin, that link is to a full flashable rom zip.
Click to expand...
Click to collapse
I think I know what happened. Was the file on an sdcard? Because scripts can't run there, and I totally forgot about that. You normally have to copy the file into termux's home location. /data/data/com.termux/files/home If you get permission denied there, then change the group owner, and user to what's in the screen shot and it'll work. You can avoid that situation entirely though, by downloading the file directly into Termux's home folder using wget. For those scripts to run you'll need to install python and protobuf too. From termux run, (without root), pkg install protobuf & pkg install python.
I'm going to try extracting that. Downloading it now.
Edit: I tried but I can't get it to work. The scripts error out because it's expecting some kind of info from Google. I tried adjusting the metainfo structure to match a pixel device and it got further into the process, but it still gives an error. What do you use on pc? I might be able to port it to Termux.
Spaceminer said:
I think I know what happened. Was the file on an sdcard? Because scripts can't run there, and I totally forgot about that. You normally have to copy the file into termux's home location. /data/data/com.termux/files/home If you get permission denied there, then change the group owner, and user to what's in the screen shot and it'll work. You can avoid that situation entirely though, by downloading the file directly into Termux's home folder using wget. For those scripts to run you'll need to install python and protobuf too. From termux run, (without root), pkg install protobuf & pkg install python.
I'm going to try extracting that. Downloading it now.
Edit: I tried but I can't get it to work. The scripts error out because it's expecting some kind of info from Google. I tried adjusting the metainfo structure to match a pixel device and it got further into the process, but it still gives an error. What do you use on pc? I might be able to port it to Termux.
Click to expand...
Click to collapse
Thanks for testing this out, sorry for the late reply, life's been hectic. The tool I USUALLY use for WIndows is payload dumper 64. I'll link it here.
Link: https://androidfilehost.com/?fid=818070582850510260