Develop Bugs

[10 JAN][SCRIPT]IMG2CWM Converter 1.2.2

birkoffsjunk's HD2 IMG2CWM Converter​
A simple windows batch script to convert DAF builds to Clockwork Recovery ZIPs.
Originally designed for MDJ's Gingerbread NAND and posted here. Results may vary!
Instructions​
Download DAF based NAND ROM
Download & Extract this script
Place Boot.img & System.img into the 'in' folder
Double click 'RunMe.cmd' (not as admin)
Manually make any changes you wish (when prompted)
Once done, update.zip will be in the same location as 'RunMe.cmd'
META-INF Info​How to: Create Clockwork Recovery flash files
How to Create Android Update Zip Package
An updated updater-script (META-INF\com\google\android\updater-script) is required for various other Builds.
Downloads​v1 >>> here <<<
v1.1 attached (7z changed to 9.20 (ghostkid2010) & renamed out folder to temp)
v1.2 attached (Added error checking & support for system.img only)
v1.2.1 attached (Specified xcopy path & removed old 7z.exe)
v1.2.2 >>> here <<< (arif-ali's linux bash script)
Addons​arif-ali's NexusHD2-Gingerbread_V2.0 updater-script
TODO​
Add error checking
Add support for system.img only
META-INF Information
Most importantly keep it simple
License​BSD License for the script not the tools
7zip is GNU LGPL
unyaffs is GNU GPL v2

same post from MDJ
Your script works great extracting the .img file. But it's not able to create zip file. Let me edit your script with the missing file/info.
Download this file and put in folder tools;
http://downloads.sourceforge.net/sevenzip/7za920.zip
change this line;
"%LOC%\tools\7z.exe" a "%LOC%\update.zip" "%LOC%\out\*"
to;
"%LOC%\tools\7za.exe" a "%LOC%\update.zip" "%LOC%\out\*"
and it should work. it will create a zip file.
Enjoy

how it works?

How does it use? What things do I have to put in the folder "IN"?

sathara said:
how it works?
Click to expand...
Click to collapse
let you extract system.img and boot.img from android build, once you extracted all the fill, it will put all the file into a zip file so you can load via CWM

VuNhatVan said:
How does it use? What things do I have to put in the folder "IN"?
Click to expand...
Click to collapse
boot.img & system.img

It has a function to edit apk. But how do you use that function and where do you add your own apk?

10507 said:
It has a function to edit apk. But how do you use that function and where do you add your own apk?
Click to expand...
Click to collapse
it does not have a function to edit apk (correct me if i'm wrong). once you extracted all the files, go into app and add your apk there.

ghostkid2010 said:
let you extract system.img and boot.img from android build, once you extracted all the fill, it will put all the file into a zip file so you can load via CWM
Click to expand...
Click to collapse
In the Build MDJ_FroYo_Revolution_v._2.2_NAND, there is only system.img, no boot.img. How could I have boot.img?

what a usefull tool, thank you!!

VuNhatVan said:
In the Build MDJ_FroYo_Revolution_v._2.2_NAND, there is only system.img, no boot.img. How could I have boot.img?
Click to expand...
Click to collapse
If there's no boot.img, it should still work. all the boot file is already in the system.img
Let me download that build and I can tell you for sure on how to do it.. I smell that a new version of this script will be out..

Yeah it's very much a work in progress, please feel free to attach updated versions... I'll add them to the first post with accreditation

ghostkid2010 said:
If there's no boot.img, it should still work. all the boot file is already in the system.img
Let me download that build and I can tell you for sure on how to do it.. I smell that a new version of this script will be out..
Click to expand...
Click to collapse
Is it work if there is only system.img?

drizztzou said:
Is it work if there is only system.img?
Click to expand...
Click to collapse
with a little bit of editing yes

ghostkid2010 said:
same post from MDJ
Your script works great extracting the .img file. But it's not able to create zip file. Let me edit your script with the missing file/info.
Download this file and put in folder tools;
http://downloads.sourceforge.net/sevenzip/7za920.zip
change this line;
"%LOC%\tools\7z.exe" a "%LOC%\update.zip" "%LOC%\out\*"
to;
"%LOC%\tools\7za.exe" a "%LOC%\update.zip" "%LOC%\out\*"
and it should work. it will create a zip file.
Enjoy
Click to expand...
Click to collapse
can u more detail about "change this line" location ? u mean u have done it already or i have to do it myself ? which file should i edit ?

ikkon said:
what a usefull tool, thank you!!
Click to expand...
Click to collapse
YEAH! Your not kidding man...i was stoked while playing with it...Id also like to know from here...Is there a similar script for SD->NAND bc my favbe ROM has always been CORECells builds of EVO/HD based...Gave me the best batttery of all SD except for the now current NAND builds. So i figure maybe itll be even better on NAND! TAHNKS again so much for your pos t BIRKOFF! ANYone know of the SD->NAND question?

psuser said:
can u more detail about "change this line" location ? u mean u have done it already or i have to do it myself ? which file should i edit ?
Click to expand...
Click to collapse
YOU have to add an "a" after the z in 7z WITHIN the RUNME script...you have to right click it and open with NOTEPAD on PC and add the "a"

psuser said:
can u more detail about "change this line" location ? u mean u have done it already or i have to do it myself ? which file should i edit ?
Click to expand...
Click to collapse
download the new version on page 1, its fixed

Really cool idea!! I gave it a shot, it just reboots after the MAGLDR screen showing the HTC logo over and over until you boot back into recovery. It flashed fine but just wouldn't boot.

VuNhatVan said:
In the Build MDJ_FroYo_Revolution_v._2.2_NAND, there is only system.img, no boot.img. How could I have boot.img?
Click to expand...
Click to collapse
Use the following "RunMetest.bat"
http://hotfile.com/dl/95408413/0c085bd/RunMetest.rar.html
I tested with different build, system.img only, both boot.img and system.img, it was able to create a zip with all the file.
I'm not uploading the whole folder since this was started by birkoffsjunk, I'm just helping
Test it out

[TOOL] [WIN/LINUX/MAC/ANDROID] [4.2-4.4] Galaxy Nexus EXT4 to F2FS ROM Converter

This is a simple script that will convert almost any Galaxy Nexus EXT4 ROM to F2FS. The script will simply swap out the kernel (unless you plan to use an AnyKernel kernel) and edit the updater-script to replace EXT4-specific lines with F2FS-specific lines (unless you have /system formatted as EXT4, in which case the line that formats /system will be left as is). The included boot.img may be replaced with any gnex F2FS boot.img.
Also, for Windows only, @sergialess created a GUI conversion tool. It allows you to choose the ROM zip from any location, choose an alternate boot.img from any location, or even choose a flashable kernel zip from any location in order to extract the boot.img. It's pretty slick, so if you like it, show him some love! As of 7/7/14, the GUI has an option for APK deletion like the three script-based tools, but it's the only one that goes one step further and allow you to select which APKs to delete.
NOTE: If you have not reformatted your device for F2FS, you're not ready to use this tool yet. This tool will make a ROM F2FS-compatible, it will not convert your device to F2FS. To reformat your device to F2FS, start with posts #1 and #2 here: http://forum.xda-developers.com/galaxy-nexus/development/kernel-dirtyv-6-9-14-t2613655
ROMs that have successfully converted and booted:
AOKP
AOSB
Carbon
C-ROM
Cyanogenmod
LiquidSmooth
Omni FML
Paranoid Android
Shiny (make sure to use EXT_to_F2FS_2014-07-07 or later and purge APKs)
SlimKat (make sure to use EXT_to_F2FS_2014-07-07 or later)
TREX
Vanir (make sure to use EXT_to_F2FS_2014-07-07 or later)
Click to expand...
Click to collapse
ROMs that have caused problems:
You tell me!
Click to expand...
Click to collapse
Alternative F2FS kernels:
cwm-DirtyV-SR-6.15.14-2-Unified.zip - modified by @osm0sis
fancy_kernel-tuna-4.4-r53.zip
SmittyV-UR-6.15.14_F2FS_discard.zip - modified by @ilgimmy
SmittyV-UR-6.28.14.zip - may conflict with some ROMs
Click to expand...
Click to collapse
Windows instructions:
1) Ensure you have .NET installed (required for GUI and find-and-replace tool).
2) Unzip the windows zip to any empty folder.
3) Place your EXT4 gnex ROM zip in the same folder, make sure there are no other zips in this folder. (Requirement only for batch file, not GUI).
4) Run EXT4_to_F2FS_gnex.bat or EXT4_to_F2FS_gnex_GUI.exe.
Click to expand...
Click to collapse
Linux / Mac instructions:
1) Ensure you have sed, zip, and unzip installed. And note that this is a bash script.
2) Unzip the linux_mac zip to any empty folder.
3) Place your EXT4 gnex ROM zip in the same folder, make sure there are no other zips in this folder.
4) cd into your converter folder
5) Run "chmod +x EXT4_to_F2FS_gnex.sh". This only needs to be done once.
6) Run "./EXT4_to_F2FS_gnex.sh"
Click to expand...
Click to collapse
Android instructions:
1) Ensure you have a zip binary, likely located at /system/xbin. If not, flash zip_binary_flashable.zip from recovery.
2) Ensure you have busybox. Stericson's 1.22.1 definitely works: https://play.google.com/store/apps/details?id=stericson.busybox. Others may not, try Stericson's before reporting problems.
3) Unzip the android zip to any empty folder on the SD card.
4) Place your EXT4 gnex ROM zip in the same folder, make sure there are no other zips in this folder.
5) Open an Android terminal
6) Run "su" (there's problems with unzipping when not root for some reason)
7) cd into your converter folder
8) Delete boot.img if you're going to install an AnyKernel kernel after installing the converted ROM
9a) Run "sh f2fs.sh" if your /system partition is formatted F2FS
9b) Run "sh ext4.sh" if your /system partition is formatted EXT4
Click to expand...
Click to collapse
Mediafire downloads: http://www.mediafire.com/?m501v8um8nd1y
Google Drive mirror: https://drive.google.com/folderview?id=0B_Yk7pLJ4-VhVUt0QmFwUVFwYk0&usp=sharing
Changelog:
9/18/14: Windows GUI updated - Velvet is no longer purged, AnyKernel support, and EXT4 /system partition support.
9/15/14: Android version supports AnyKernel kernels and EXT4 /system partitions. Be sure to read steps 8 and 9 in the instructions.
9/14/14: Windows & Linux/Mac versions support AnyKernel kernels and EXT4 /system partitions. Window GUI has NOT been updated yet.
8/18/14: Velvet is no longer purged. All versions now include Fancy r54. Window GUI has NOT been updated yet.
7/15/14: Changed method of reading ROM ZIP name in Linux/Mac version. All versions now include Fancy r51.
7/11/14: Very minor change to Linux tool to make it compatible with the Mac terminal.
7/7/14: Windows (including GUI), Linux, & Android tools handle /data mounting (for SlimKat) and have option to purge unneeded APKs (for Shiny).
7/2/14: Added Windows GUI tool.
7/1/14: Spaces in the path are no longer a problem in the Windows version, added Linux and Android versions, included boot.img is SmittyV 6/28/14
6/25/14: Initial release, included boot.img is DirtyV 6/9/14.
Credits:
@bsmitty83, @osm0sis, @metalspring, and everyone else in the DirtyV thread who made F2FS possible: http://forum.xda-developers.com/galaxy-nexus/development/kernel-dirtyv-6-9-14-t2613655
@NABENDU1 for the grouper F2FS ROM conversion tool that inspired this: http://forum.xda-developers.com/show....php?t=2731666
@sergialess for the Windows GUI tool.
@boype for his Fancy kernel: http://forum.xda-developers.com/galaxy-nexus/development/kernel-fancy-kernel-r50-t2115590
@latenightchameleon for the idea to purge unneeded APKs from large ROM zips like Shiny.
@johansenmo for the assistance in making the Linux tool Mac compatible.
My other projects:
LiquidSmooth-OFFICIAL for maguro: http://forum.xda-developers.com/gal...m-official-liquidsmooth-kitkat-4-4-3-t2667078
LiquidSmooth-OFFICIAL for toro: http://forum.xda-developers.com/gal...m-liquidsmooth-v3-1-kitkat4-4-3-toro-t2575560
LiquidSmooth-OFFICIAL for toroplus: http://forum.xda-developers.com/gal...m-official-liquidsmooth-kitkat-4-4-3-t2672510
LiquidSmooth-UNOFFICIAL for maguro: http://forum.xda-developers.com/gal...aguro-toro-t2793275/post53641446#post53641446
LiquidSmooth-UNOFFICIAL for toro: http://forum.xda-developers.com/galaxy-nexus/verizon-develop/rom-liquidsmooth-v3-1-toro-t2793284
LiquidSmooth-UNOFFICIAL for toroplus: http://forum.xda-developers.com/galaxy-nexus/sprint-develop/rom-liquidsmooth-v3-1-toroplus-t2793281
LiquidSmooth-UNOFFICIAL for grouper: http://forum.xda-developers.com/showthread.php?t=2709385
F2FS Converter tools for grouper ROMs: http://forum.xda-developers.com/nexus-7/development/tool-grouper-ext4-to-f2fs-rom-converter-t2801653
Ting APNs to fix LTE: http://forum.xda-developers.com/galaxy-nexus/general/ting-flashable-zip-fixed-lte-android-4-t2428999
Verizon APNs to fix MMS: http://forum.xda-developers.com/android/software/tool-verizon-mms-apn-patch-t2833914
Click to expand...
Click to collapse
[poo]

~~

poo706 said:
This is a simple Windows batch script that will convert any Galaxy Nexus EXT4 ROM to F2FS. Thanks to NABENDU1 for the grouper script that inspired my gnex script: http://forum.xda-developers.com/showthread.php?t=2731666 . The script will simply swap out boot.img (i.e. the kernel) and edit the updater-script to replace EXT4-specific lines with F2FS-specific lines. The included boot.img is DirtyV 06-09-2014, but it may be replaced with any gnex F2FS boot.img.
Instructions:
1) Unzip EXT4_to_F2FS_gnex.zip to any empty folder, make sure there are no spaces anywhere in the path.
2) Place your EXT4 gnex ROM zip in the same folder, make sure there are no other zips in this folder.
3) Run EXT4_to_F2FS_gnex.bat.
Download: https://drive.google.com/folderview?id=0B_Yk7pLJ4-VhVUt0QmFwUVFwYk0&usp=sharing
[poo]
Click to expand...
Click to collapse
Magic
Works amazing, thanks!

T0RU said:
it works, hell yeah you deserve a big ass thanks from me
---------- Post added at 09:10 PM ---------- Previous post was at 09:09 PM ----------
Flashing now
Click to expand...
Click to collapse
pianistaPL said:
Magic
Works amazing, thanks!
Click to expand...
Click to collapse
Glad it worked out for you guys. I'd just throw a couple of thanks your way, but I used up my 8 first thing this morning.
[poo]

~~

T0RU said:
Odd I tried to make a f2fs for paranoid android but I keep getting this error PS it worked on shiny perfectly
HTML:
symlink: some symlinks failed
E: Error executing updater binary in zip '/sdcard/f2fsaospa.4.4.4.zip'
Error flashing zip '/sdcard/f2fsaospa.4.4.4.zip'
Click to expand...
Click to collapse
That is odd. A couple of people on this page http://forum.xda-developers.com/galaxy-nexus/help/f2fs-thread-questions-t2770735/page14 used my converter on PA without issue. Are you all using the same PA?
[poo]

~~

T0RU said:
RC2 and I do think it's because of the recovery (twrp2.7.1.0)
Click to expand...
Click to collapse
So the issue's not on my end then?
[poo]

Tried it with latest PA and Vanir and it worked just like a charm!
Then you for sharing Sir!

poo706 said:
So the issue's not on my end then?
[poo]
Click to expand...
Click to collapse
nope

ehh I still keep getting these errors
I moved back to 2.7.0.0

I tried to do this again on shiny, somehow it gives me the same error that I had with PA
any help?

T0RU said:
I tried to do this again on shiny, somehow it gives me the same error that I had with PA
any help?
Click to expand...
Click to collapse
Can you list what you do exactly? Must be something minor that you're missing out on.

it works very good thx

Just converted and flashed todays Vanir build and again without any issue!
:good::good::good::good::good:

T0RU said:
I tried to do this again on shiny, somehow it gives me the same error that I had with PA
any help?
Click to expand...
Click to collapse
I'm with Hetalk. I think something silly is going on, but I don't think it has to do with the conversion tool. (I keep wanting to refer to it as "my tool", but that somehow doesn't feel right.)
[poo]

Well well,
I flashed with fastboot this recovery --> http://www.trysoftcore.com/Recovery/TWRP-f2fs.zip
went to Advance->f2fs/ext4 switch->formatted all to f2fs (system ,cache and data)
adb sideloaded the rom (Just downloaded your tool and shiny rom again and did exactly what you said and then sideloaded it)
and after that I get this annoying message:
Code:
symlink: some symlinks failed
E: Error executing updater binary in zip '/sdcard/shiny.zip'
Error flashing zip '/sdcard/shiny.zip'
I named the zip file "Shiny.zip"
and that's all I did to get this error

T0RU said:
Well well,
I flashed with fastboot this recovery --> http://www.trysoftcore.com/Recovery/TWRP-f2fs.zip
went to Advance->f2fs/ext4 switch->formatted all to f2fs (system ,cache and data)
adb sideloaded the rom (Just downloaded your tool and shiny rom again and did exactly what you said and then sideloaded it)
and after that I get this annoying message:
Code:
symlink: some symlinks failed
E: Error executing updater binary in zip '/sdcard/shiny.zip'
Error flashing zip '/sdcard/shiny.zip'
I named the zip file "Shiny.zip"
and that's all I did to get this error
Click to expand...
Click to collapse
I think you need to change recoveries. I saw others in the dirtyv thread who ran in to problems with that recovery that supposedly is universal to all 3 gnex variants. Try the appropriate device-specific recovery under the all-in-one recovery.
[poo]

the 2.7.1.1 does not have a f2fs swice tap oddly enough
it only says EXT4 next to the twrp name

T0RU said:
the 2.7.1.1 does not have a f2fs swice tap oddly enough
it only says EXT4 next to the twrp name
Click to expand...
Click to collapse
Swice tap? What device do you have? Are you looking here for the recoveries? http://forum.xda-developers.com/showpost.php?p=49501604&postcount=1
[poo]

Unable to sideload community build

I am trying to install the latest community build , I download a latest version of 3.5.3 from OnePlus's download section.
Currently I am on 3.2.7 , not rooted and boot loader is locked. All factory setting
these are the steps
check and make sure USB debugging is on
connect the device to PC
adb reboot recovery
device goes to recovery , select language and select install from adb on my phone
checking to make sure device is recognized and authorized
adb devices
50f4f77f sideload
************************************
adb sideload Update.zip
loading: 'Update.zip'
* cannot read 'Update.zip' *
I know I am in a correct folder as I already a did a <dir> and verified update.zip is in the current folder but lets try this
adb sideload C:\adb\Update.zip
loading: 'Update.zip'
* cannot read 'Update.zip' *
:crying:
at this point I am sure there is something wrong with the zip file. so I delete it and download the 3.2.6 just to test it out and I was able to downgrade to 3.2.6 with adb sildeload. once installation was complete I tried again to download 3.5.3 and sideload it but still getting a cannot read <filename> error.
any idea what I am missing here ?
By the way , I have tried several options such as :
1- changing the location of the file from adb folder to other location
2- renaming the file
3- launching cmd prompt as an administrator and navigating to the file location

Hello,
I have a strong feeling that you are trying to flash a wrong zip file. Can you mention the size of file that you mentioned as "update.zip"?

catrawalkar said:
Hello,
I have a strong feeling that you are trying to flash a wrong zip file. Can you mention the size of file that you mentioned as "update.zip"?
Click to expand...
Click to collapse
"OnePlus3Oxygen_16_OTA_003_all_1609142002_2a17363c90cd462e.zip" is the name of the file

nima352000 said:
"OnePlus3Oxygen_16_OTA_003_all_1609142002_2a17363c90cd462e.zip" is the name of the file
Click to expand...
Click to collapse
Then why are you giving command of update.zip? You should write the name of file in the command.
Replace "update.zip" in your command to the name of file as it is.

catrawalkar said:
Then why are you giving command of update.zip? You should write the name of file in the command.
Replace "update.zip" in your command to the name of file as it is.
Click to expand...
Click to collapse
As I mentioned in my post I have already tried that this was my last attempt as many folks out here saying that "renaming" the file helped them

nima352000 said:
As I mentioned in my post I have already tried that this was my last attempt as many folks out here saying that "renaming" the file helped them
Click to expand...
Click to collapse
Can you post a screenshot of your command prompt and folder that contains zip file?

catrawalkar said:
Can you post a screenshot of your command prompt and folder that contains zip file?
Click to expand...
Click to collapse
sure , here it is

I had this issue when I tried to download the first time. The zip is corrupted. I downloaded the file again and update your adb and fastboot version. I am sure it should work fine.
---------- Post added at 08:35 AM ---------- Previous post was at 08:29 AM ----------
I also suspect the issue could be due to renaming the filename manually into update.zip and when the extension is hidden, it becomes update.zip.zip. please crosscheck to be double sure.

Reboot your computer after you download the file.
I know it sounds weird but I have to do it every time I download the community builds and I've no idea why...otherwise they give the same error. Don't rename the file either there's no need.

nima352000 said:
sure , here it is
Click to expand...
Click to collapse
There could be renaming issue. Try re-downloading file and let me know if you have resolved the issue..

Renaming the file is only for the sake of convenience. Or else you may end up giving a wrong file name by typing error when giving the sideload command as the file names are usually too long.
In this case the file should have been corrupt (not fully downloaded).

Try opening the .zip file.
If it is corrupted, the CRC will fail and it won't open.
In which case you know you have a bad download.

debasish.patra said:
I had this issue when I tried to download the first time. The zip is corrupted. I downloaded the file again and update your adb and fastboot version. I am sure it should work fine.
---------- Post added at 08:35 AM ---------- Previous post was at 08:29 AM ----------
I also suspect the issue could be due to renaming the filename manually into update.zip and when the extension is hidden, it becomes update.zip.zip. please crosscheck to be double sure.
Click to expand...
Click to collapse
Hi , I did try to reinstall the adb drivers , but I will give it a shot again. Also as far as renaming the file the file in the above screen shot is originally downloaded from OnePlus's website without renaming. >dir command shows the file extension to be correct ending with .zip not zip.zip ..
anyways I will reinstall the adb drivers again today

Roxas598 said:
Reboot your computer after you download the file.
I know it sounds weird but I have to do it every time I download the community builds and I've no idea why...otherwise they give the same error. Don't rename the file either there's no need.
Click to expand...
Click to collapse
will give this a try . download a fresh copy with original name , reboot the PC and retry ? is that the sequence you are suggesting ?

kgs1992 said:
Try opening the .zip file.
If it is corrupted, the CRC will fail and it won't open.
In which case you know you have a bad download.
Click to expand...
Click to collapse
doesn't look like that was the case . was able to open the .zip file just fine

nima352000 said:
will give this a try . download a fresh copy with original name , reboot the PC and retry ? is that the sequence you are suggesting ?
Click to expand...
Click to collapse
Yep that's it mate

debasish.patra said:
I had this issue when I tried to download the first time. The zip is corrupted. I downloaded the file again and update your adb and fastboot version. I am sure it should work fine.
---------- Post added at 08:35 AM ---------- Previous post was at 08:29 AM ----------
I also suspect the issue could be due to renaming the filename manually into update.zip and when the extension is hidden, it becomes update.zip.zip. please crosscheck to be double sure.
Click to expand...
Click to collapse
by the way may I get the link to "adb and fastboot version" which you are referring to ? just wanted to make sure I am on the right track

What version of adb are you using?
Your screen print shows 944,128 bytes whereas mine shows 1,479,680 bytes for adb.exe
eg output from the command "adb version"
Android Debug Bridge version 1.0.36
Revision 8f855a3d9b35-android
Looks like you are on:
>adb version
Android Debug Bridge version 1.0.32
Revision eac51f2bb6a8-android

Roxas598 said:
Yep that's it mate
Click to expand...
Click to collapse
it actually worked ! thanks a bunch mate !

for anybody who is having the same issue and interested what was the solution , I download a new copy of .zip file from OnePlus websire . restarted my PC and tried again and it worked . Can't make any sense of it but that was the solution

[SAMSUNG][GALAXY TAB E][SM-T560] Kernel Kitchen

Kernel Kitchen for Samsung Galaxy Tab E (SM-T560).
Based on T560XXU0AOK1 from http://opensource.samsung.com
https://github.com/codeworkx/gtelwifi_kernel_kitchen
./boot.sh - creates boot.img for use with stock samsung rom
./twrp.sh - creates twrp.img

Will there be one for SM-T560NU?

How do you install it, creating a tar, twrp or cmd?

JanValentine said:
How do you install it, creating a tar, twrp or cmd?
Click to expand...
Click to collapse
a) create a tar
b) use heimdall
heimdall flash --KERNEL boot.img
heimdall flash --RECOVERY twrp.img

codeworkx said:
a) create a tar
b) use heimdall
heimdall flash --KERNEL boot.img
heimdall flash --RECOVERY twrp.img
Click to expand...
Click to collapse
At boot.img I do not take it, so I installed it from the recovery and it worked.
THX

mkbootimg problem and ... what can I do with these files?
Again, first of all, thanks for providing this.
I've basically managed to build the artifacts (boot.img, twrp.img).
I have used
Code:
git clone https://android.googlesource.com/platform/system/core.git
to get mkbootimg, yet then both scripts fail, because that mkbootimg does not know the --dt parameter.
Without that parameter the artifacts are created.
Where can I find a suitable mkbootimg?
And then: What can I do with these files?
a) create a tar
b) use heimdall
heimdall flash --KERNEL boot.img
heimdall flash --RECOVERY twrp.img
Click to expand...
Click to collapse
I am confused - create a tar (containing which files?), and then flash the .img files?
Thanks
Ciao
V.

vaihaito said:
Again, first of all, thanks for providing this.
I've basically managed to build the artifacts (boot.img, twrp.img).
I have used
to get mkbootimg, yet then both scripts fail, because that mkbootimg does not know the --dt parameter.
Without that parameter the artifacts are created.
Where can I find a suitable mkbootimg?
And then: What can I do with these files?
I am confused - create a tar (containing which files?), and then flash the .img files?
Thanks
Ciao
V.
Click to expand...
Click to collapse
mkbootimg can be built from aosp sources. Every recent version supports dt.
Just tar the image. Tgen it can be used with odin. There are tutorials on xda.
Sent from my OnePlus 5T using XDA Labs

codeworkx said:
mkbootimg can be built from aosp sources. Every recent version supports dt.
Click to expand...
Click to collapse
It seems to be the other way round ... in 2015 they have replaced the C-based mkbootimg with the Python-based mkbootimg. The latter does not have that option.
Details and mkbootimg build instructions: Search for "gist.github.com jberkel 1087757". Cannot post real links.
Anyway, it succeeded to build.
And I managed to install twrp.img using heimdall. Works as well
Thanks again.
Ciao
V.

What changes does the kernel and the twrp make?

It would be nice If you give me a hind about how you solve this! Thanks

downgrade from 10 to 9

Hey everyone, is it possible to downgrade to Android pie ?
Does simply flashing the build will do the trick ? Or it's impossible to go back to 9 ?
Thanks

youssefkr said:
Hey everyone, is it possible to downgrade to Android pie ?
Does simply flashing the build will do the trick ? Or it's impossible to go back to 9 ?
Thanks
Click to expand...
Click to collapse
I've read about several users going back to 9. However, it will take a full wipe and a clean flash of the factory image to do so :good:

I did downgrade to 9, full wipe, flashed twrp, in my case i needed root and magisk safetynet.

1902 said:
I did downgrade to 9, full wipe, flashed twrp, in my case i needed root and magisk safetynet.
Click to expand...
Click to collapse
Im debating rolling back, what rom did you settle on?

SageWilliams said:
Im debating rolling back, what rom did you settle on?
Click to expand...
Click to collapse
Latest original pie, rooted with latest magisk, if TWRP and safetynet were 100% working i would have stayed on A10, but till then i'm gonna stay on pie :angel:

I'm on 10 rooted, and can't unroot. Magisk won't uninstall from it's app. Tried to go back to 9, but it won't flash cleanly. I can sell the phone, but only if it's stock. 9 or 10, the buyer doesn't care. I can use a little help, please.
---------- Post added at 21:52 ---------- Previous post was at 21:33 ----------
How about, if I delete the sbin file in system/root, and then do a factory reset from the phone's settings?

1902 said:
I did downgrade to 9, full wipe, flashed twrp, in my case i needed root and magisk safetynet.
Click to expand...
Click to collapse
I don't need root, but please tell me how you downgraded from 10 back to 9. I really need to do this. Thanks

grunt0300 said:
I don't need root, but please tell me how you downgraded from 10 back to 9. I really need to do this. Thanks
Click to expand...
Click to collapse
Just Grab the pie factory image from https://developers.google.com/android/images
and follow the instruction on the developers' page, note that flashing this will wipe your device.
better to watch a tutorial online on how to flash a factory image :good:

1902 said:
Just Grab the pie factory image from https://developers.google.com/android/images
and follow the instruction on the developers' page, note that flashing this will wipe your device.
better to watch a tutorial online on how to flash a factory image :good:
Click to expand...
Click to collapse
Tried it, but no go. I get the command prompt box ok, but can't put anything into it.

grunt0300 said:
Tried it, but no go. I get the command prompt box ok, but can't put anything into it.[/QUOTE
I've done it by formatting data in twrp then flash pie ota, or flash the partitions (bootloader,radio,vendor) on both slots in fastboot then fastboot update (image-taimen-pq3a.190801.002.zip)
Click to expand...
Click to collapse

grunt0300 said:
Tried it, but no go. I get the command prompt box ok, but can't put anything into it.
Click to expand...
Click to collapse
Got it done. I had the files in the wrong place. It's all good now. Android 9, stock.

Im doing something wrong.
grunt0300 said:
Got it done. I had the files in the wrong place. It's all good now. Android 9, stock.
Click to expand...
Click to collapse
Hey I'm trying to downgrade myself and running into errors when trying to execute the flash-all command. Android 9 files are in the platform tools folder just like you would flash TWRP. First time downgrading. Is there a good tutorial...cause I followed the google tutorial and "flash-all" just sint working.

Driacas said:
Hey I'm trying to downgrade myself and running into errors when trying to execute the flash-all command. Android 9 files are in the platform tools folder just like you would flash TWRP. First time downgrading. Is there a good tutorial...cause I followed the google tutorial and "flash-all" just sint working.
Click to expand...
Click to collapse
Are you doing a clean install (leaving the -w intact)?
Do you have the latest SDK toolkit?
What errors are you running into?

Az Biker said:
Are you doing a clean install (leaving the -w intact)?
Do you have the latest SDK toolkit?
What errors are you running into?
Click to expand...
Click to collapse
Yes I'm using the latest SDK tools.
This is the error I recieved.
" flash-all : The term 'flash-all' is not recognized as the name of a cmdlet, function, script file, or operable
program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ flash-all
+ ~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (flash-all:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException"
Well the android updated to 10 on its own. I attempted to flash the newest version of Magisk onto it using TWRP. Now the phone just stays put at the google logo and wont boot further. It does boot into fastboot, So I figured I should just flash the older version back on. Also im on sailfish
---------- Post added at 11:06 PM ---------- Previous post was at 10:28 PM ----------
Also there is no "Flash-all" files that downloaded with the images. I have these files: Payload (Bin File), zipped combatability file, Meta file, care map and payload properties....

Driacas said:
Yes I'm using the latest SDK tools.
This is the error I recieved.
" flash-all : The term 'flash-all' is not recognized as the name of a cmdlet, function, script file, or operable
program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ flash-all
+ ~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (flash-all:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException"
Well the android updated to 10 on its own. I attempted to flash the newest version of Magisk onto it using TWRP. Now the phone just stays put at the google logo and wont boot further. It does boot into fastboot, So I figured I should just flash the older version back on. Also im on sailfish
---------- Post added at 11:06 PM ---------- Previous post was at 10:28 PM ----------
Also there is no "Flash-all" files that downloaded with the images. I have these files: Payload (Bin File), zipped combatability file, Meta file, care map and payload properties....
Click to expand...
Click to collapse
Did you unzip the factory image TWICE? Sounds like CMD isn't finding the flash-all file, which is in the folder after the second unzip.
As far as sailfish OS, I've never dealt with it so couldn't tell you one way of the other anything about it.

Driacas said:
Also there is no "Flash-all" files that downloaded with the images. I have these files: Payload (Bin File), zipped combatability file, Meta file, care map and payload properties....
Click to expand...
Click to collapse
Sounds like you downloaded the OTA file rather than the factory image file.