Database Info

[LINUX] FastBoot Protical On Your Vega (DEV)

Hi iv been testing this for a while and iv gotta say ..... its amazing the vega can do something the xoom cannot .... fastboot boot. Witch for a rom dev saves a lot of time
Ok this is relatively safe but is dev only thing so use with a little cation :-D as always dont blame me for a brick
[Video]
Watch it here
http://www.youtube.com/watch?v=llZ3qYSlLUE
[GUIDE]
From recovery
1) extract the .zip from below and allow the fastboot binary to be executes
2) reboot to recovery
3) format boot partition in recovery
4) reboot (now your device will drop to fastboot)
5) it will do this every boot until l boot.img is restored
From NVflash
1) extract the .zip from below and allow the fastboot binary to be executes
2) boot into APX mode
2) format boot partition with nvflash ( ./nvflash --bl bootloader.bin --format_partition 7 -go )
3) (now your device will drop to fastboot)
4) it will do this every boot until l boot.img is restored
[OTHER INFO]
Seeing as the vega reports as a different vendor we have to specify this in the fastboot command some examples can be found below
./fastboot -i 0x955 -b 0x10000000 boot zImage ramdisk
Click to expand...
Click to collapse
./fastboot -i 0x955 -b 0x10000000 boot boot.img
Click to expand...
Click to collapse
./fastboot -i 0x955 -b 0x10000000 flash boot.img
Click to expand...
Click to collapse
./fastboot -i 0x955 -b 0x10000000 flash:raw zImage ramdisk
Click to expand...
Click to collapse
(This one is useful as u dont have to worry about a command line in normal cases)
[DOWNLOAD]
HERE !!!

Like to see a video of this is use...
Sent from my Vega using Tapatalk

Would love to give this a try but clearly I'm not a dev since I have no clue what to do

dagrim1 said:
Would love to give this a try but clearly I'm not a dev since I have no clue what to do
Click to expand...
Click to collapse
Ha ha, me to. I keep starting to think I am getting a handle on the scene and then something like this shows me how much I dont have a bloody clue!
Sent from my HTC Desire using XDA Premium App

gadgetuk99 said:
Like to see a video of this is use...
Sent from my Vega using Tapatalk
Click to expand...
Click to collapse
There is a video of this now in the main post

What is the advantage of this fastboot for a developer?
I remember getting that prompt when I switched from USB Slave to USB Host on Paul's Modaco ROM. I was quite clueless (I opened a help thread both here and in Modaco) and only re-flashing the stock ROM helped me any.

Nice work!
Does this allow you to push e.g. kernel images from my pc to boot on-the-fly or does the images need to be on the device already?
Sorry if that seems like a dumb question

FastBoot means that the device boots off a ROM image on your PC, instead of a burnt ROM. This has no advantage to non-devs (other then possibly brick protection, but they are pretty unbrickable as is).
To be clear: This does not make it boot "faster" and it probably has no use for you. Move along

Just checking. This'll be really useful in testing all of my broken kernel builds

how exacly does this work. Ive tried building roms in the past for my defy but got fed up with bricking it trying to bring the defy back to life was a real pain in the ass.
I would like to have a go with the vega if this makes it simpler.
Does it mean i can boot an image that is on my pc whilst leaving the internal image the same?
and can i simply re boot and have every thing as it was befor?
thanks in advange for any help!

I've extracted the advent .exe file to see if it'd be possible to re-flash the full stock ROM without having to use Windows. I got successful in reaching Fastboot mode, and when I execute ./fastboot I see a command which says "flashall", which would flash "boot.img", recovery and system.img. Would that be enough to boot safely? I see as well the possibility to execute an "update" command. If I converted the adventupdate.exe to adventupdate.zip, would said command flash the contents (aka the ROM?).
I may be saying foolish things, but I am curious about this.

edit boot.img-ramdisk

heres where im at now. im trying to edit the init.rc
i have extracted the boot.img using unpack-bootimg.pl and have got the follwing
empty folder called ramdisk
boot.img-ramdisk.cpio.gz
boot.img-ramdisk.gz
boot.img-kernell.gz
i am now stuck extracting the ramdisk to edit init.rc
i also get error gunzip is not a recognied command
any help??

add.thebad said:
i am trying to edit the init.rc but have problems extracting boot.img-ramdisk.gz
i have made a rom dump
then extracted boot.img
got boot.img-ramdisk.gz so extracted that
and now i have a file called boot.img-ramdisk nothing else
so how can i edit ramdisk?
thanks in advance. any help welcome
Click to expand...
Click to collapse
add.thebad,
Been a while since I've done this, lol, but these are the instructions I followed:
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images
There's links to the Perl scripts in that page too.
Hope this helps.
Cheers!

thanks but the link to the scripts is broke. dont suppose you know where to get another

add.thebad said:
thanks but the link to the scripts is broke. dont suppose you know where to get another
Click to expand...
Click to collapse
Adam (that's right, right? ),
I found an XDA version of the "How To" link I posted above: http://forum.xda-developers.com/showthread.php?t=443994 and the files are at the bottom of the first post and they are still available.
By the way, I used these instructions (along with lots of help from Amon_RA himself) for unpacking and repacking Amon_RA's custom recovery .img file (I built a version that doesn't require the use of a trackball for the Eris).
I think after you unpack the ramdisk, you'll just replace / update your init.rc file and then repack everything before doing the mkbootfs on your ramdisk directory (followed by your particular mkbootimg command).
Good luck!
Cheers!

thanks for you help i have the scripts now and i can get it to extract however i get the error "gunzip is not recognised" and the files it does extract are emply

add.thebad said:
thanks for you help i have the scripts now and i can get it to extract however i get the error "gunzip is not recognised" and the files it does extract are emply
Click to expand...
Click to collapse
Are you on a Linux system?
The gzip / gunzip utilities should be on your system and/or referenced in you PATH environment variable.
Do a find / -name 'gzip' 2> /dev/null or find / -name gunzip 2> /dev/null or whereis gunzip or which gunzip (one of these should reveal the utility's location).
The unpack-bootimg.pl does use the gunzip command to extract the files, so you will need this utility.
Cheers!

after a bit of reading i think the way i have got my boot.img is wrong could this be why the folder is empty?

add.thebad said:
after a bit of reading i think the way i have got my boot.img is wrong could this be why the folder is empty?
Click to expand...
Click to collapse
Not sure... Like I said, I started with a known, good recovery.img file... I never have (yet) played with a boot.img file...

scary alien said:
Not sure... Like I said, I started with a known, good recovery.img file... I never have (yet) played with a boot.img file...
Click to expand...
Click to collapse
i managed to extract a boot.img from an official system image and tried that and got the same result. could i have anything to do with gunzip not being recognised

add.thebad said:
i managed to extract a boot.img from an official system image and tried that and got the same result. could i have anything to do with gunzip not being recognised
Click to expand...
Click to collapse
lol...I think we cross-posted a little bit ago...see above ^^^ for my post about your gunzip utility.

scary alien said:
lol...I think we cross-posted a little bit ago...see above ^^^ for my post about your gunzip utility.
Click to expand...
Click to collapse
haha so we did.
no im on windows and cant get gunzip to work. think i have gzip working tho
any ideas?

add.thebad said:
haha so we did.
no im on windows and cant get gunzip to work. think i have gzip working tho
any ideas?
Click to expand...
Click to collapse
Yeah, you'll have to grab some Windows versions of the Unix commands.
I can't remember where I got mine, but a quick search yielded this as a possible starting place:
http://www.cyberciti.biz/faq/unix-command-line-utilities-for-windows/
There's a couple of links to sets of tools. After you download and install these, make sure you point / change your Windows PATH to point to the utilities or just do all of your work in the same directory.
You really just need the utilities that are referenced in the Perl script... Not sure I'd bother with the whole Cygwin thing (your call, of course).
Cheers!

scary alien said:
Yeah, you'll have to grab some Windows versions of the Unix commands.
I can't remember where I got mine, but a quick search yielded this as a possible starting place:
http://www.cyberciti.biz/faq/unix-command-line-utilities-for-windows/
There's a couple of links to sets of tools. After you download and install these, make sure you point / change your Windows PATH to point to the utilities or just do all of your work in the same directory.
You really just need the utilities that are referenced in the Perl script... Not sure I'd bother with the whole Cygwin thing (your call, of course).
Cheers!
Click to expand...
Click to collapse
Ok will try that. I allready have cygwin to try get the commands i will try ur link tho. Think im getting a bit outa my depth but ive learnt so much so far i dont want to give up so thanks for your help

heres where im at now. im trying to edit the init.rc
i have extracted the boot.img using unpack-bootimg.pl and have got the follwing
empty folder called ramdisk
boot.img-ramdisk.cpio.gz
boot.img-ramdisk.gz
boot.img-kernell.gz
i am now stuck extracting the ramdisk to edit init.rc
i also get error gunzip is not a recognied command
any help??

add.thebad said:
heres where im at now. im trying to edit the init.rc
i have extracted the boot.img using unpack-bootimg.pl and have got the follwing
empty folder called ramdisk
boot.img-ramdisk.cpio.gz
boot.img-ramdisk.gz
boot.img-kernell.gz
i am now stuck extracting the ramdisk to edit init.rc
i also get error gunzip is not a recognied command
any help??
Click to expand...
Click to collapse
Well, I spent some time tonight trying to do this under Windows myself, but I used the split_bootimg.pl Perl script instead to create the *.img-kernel and *.img-ramdisk.gz files (with mixed success). lol, I had a hard time re-finding some good Unix commands that would run under Windows (I've got some good ones on my work PC, but that doesn't help me now).
Here's the relevant section in the original HOWTO link I sent you:
% ./split_bootimg.pl boot.img
Page size: 2048 (0x00000800)
Kernel size: 1388548 (0x00153004)
Ramdisk size: 141518 (0x000228ce)
Second size: 0 (0x00000000)
Board name:
Command line: no_console_suspend=1
Writing boot.img-kernel ... complete.
Writing boot.img-ramdisk.gz ... complete.
Now, extracting the ramdisk under Windows is a little trickier and I couldn't get the whole way there because I couldn't find the cpio command for Windows (you might have it already if you are using Cygwin). Anyway, the documentation explains that you would create a temporary "ramdisk" directory, change to it, use the gzip utility to uncompress and feed the output to the cpio command to actually extract the files and directories:
Extract the ramdisk.
% mkdir ramdisk
% cd ramdisk
% gzip -dc ../boot.img-ramdisk.gz | cpio -i
% cd ..
That should work for you (if you have appropriate utilities) and should give you the various files that comprise the ramdisk for you to modify (i.e., the init.rc).
After modifying them, you would use the mkbootfs utility (not sure if this is actually available in Windows) to re-pack the ramdisk and then use the mkbootimg command to re-pack your boot image.
It might be easier to get a Linux distro installed that you can launch from Windows just to do this.
Good luck!

scary alien said:
It might be easier to get a Linux distro installed that you can launch from Windows just to do this.
Good luck!
Click to expand...
Click to collapse
ahaa managed to get everything extracted and edit the init.rc so thank you for all your help
one the linux side of things i have ubuntu dual boot and use it from time to time im just not familiar with the commands on it so prefer windows. might try it more oftern since it can be a pain finding all the tools for windows
ne way all i need to do now is repackage it which is proving to be a bit of a problem atm.
a sleep less night and ill c how i get on lol
cheers for the help

add.thebad said:
ahaa managed to get everything extracted and edit the init.rc so thank you for all your help
one the linux side of things i have ubuntu dual boot and use it from time to time im just not familiar with the commands on it so prefer windows. might try it more oftern since it can be a pain finding all the tools for windows
ne way all i need to do now is repackage it which is proving to be a bit of a problem atm.
a sleep less night and ill c how i get on lol
cheers for the help
Click to expand...
Click to collapse
Adam,
Glad you are making progress .
Here's the last few bits that I used to re-pack my ramdisk and to rebuild the bootable recovery .img file (i.e., ramdisk + kernel):
# pack-up the ramdisk directory's files to build the new ramdisk .zip
#
mkbootfs ./ramdisk | gzip > ramdisk-new.gz
# now, repack the kernel and ramdisk to make the new recovery image
#
mkbootimg --cmdline 'no_console_suspend=1 console=null' --kernel recovery-RA-eris-v1.6.2.img-kernel --ramdisk ramdisk-new.gz --base 0x11200000 -o new-recovery.img
This is very similar to the instructions in the HOWTO thread.
Also, note the --base parameter in the mkbootimg line, this is unique/specific to each phone/bootable image since it appears to be the boot/load address, so you'll have to know or find-out what this particular value is for your situation.
Good luck and let me know how it goes.
Cheers to you, too!

scary alien said:
Adam,
Glad you are making progress .
Here's the last few bits that I used to re-pack my ramdisk and to rebuild the bootable recovery .img file (i.e., ramdisk + kernel):
# pack-up the ramdisk directory's files to build the new ramdisk .zip
#
mkbootfs ./ramdisk | gzip > ramdisk-new.gz
# now, repack the kernel and ramdisk to make the new recovery image
#
mkbootimg --cmdline 'no_console_suspend=1 console=null' --kernel recovery-RA-eris-v1.6.2.img-kernel --ramdisk ramdisk-new.gz --base 0x11200000 -o new-recovery.img
This is very similar to the instructions in the HOWTO thread.
Also, note the --base parameter in the mkbootimg line, this is unique/specific to each phone/bootable image since it appears to be the boot/load address, so you'll have to know or find-out what this particular value is for your situation.
Good luck and let me know how it goes.
Cheers to you, too!
Click to expand...
Click to collapse
ok gave up in windows cannot find a command or perl script for mkbootfs so now in ubuntu giving it a try

i can do that first bit fine. does it need to be re cpio?
on the next commannd i type
Code:
mkbootimg --cmdline 'no_console_suspend=1 console=null' --boot.img-kernel.gz --boot.img-ramdisk.gz ----base 0x10000000 -o new-boot.img
and get this
Code:
[email protected]:~/Desktop$ mkbootimg --cmdline 'no_console_suspend=1 console=null' --boot.img-kernel.gz --boot.img-ramdisk.gz ----base 0x10000000 -o new-boot.img
usage: mkbootimg
--kernel <filename>
--ramdisk <filename>
[ --second <2ndbootloader-filename> ]
[ --cmdline <kernel-commandline> ]
[ --board <boardname> ]
[ --base <address> ]
-o|--output <filename>
but nothing is outputted on my desktop

add.thebad said:
ok gave up in windows cannot find a command or perl script for mkbootfs so now in ubuntu giving it a try
Click to expand...
Click to collapse
I believe that the mkbootfs utility is available / created as a result of building / compiling the Android open source.
Like I mentioned before, its been a while since I did all this myself, but I had to download and do the base "make" for the Android open source since I was actually changing and recompiling the custom recovery.
So, you'll need to check-out / download the desired AOSP branch / version from the proper location (which eludes me at the moment). Then, I believe doing the base / generic "make" for the AOSP will create or reveal the mkbootfs utility.
One of the threads in the following forum should have a better, starter explanation for doing the above that I could post here:
http://forum.xda-developers.com/forumdisplay.php?f=613
I'd dig into this more with you tonight, but I gotta do my taxes and then go into work for a few hours tonight (ugh on both counts, lol!).
Good luck!

[q] loop devices

how i am know if my tablet "loop devices" support
or how i am kae him to suport loop devices

Code:
cd /sdcard/wherever/
cp /proc/config.gz ./
gunzip ./config.gz
cat ./config | grep LOOP
"LOOP" must be in all caps, or it won't work.

thanks
EndlessDissent said:
Code:
cd /sdcard/wherever/
cp /proc/config.gz ./
gunzip ./config.gz
cat ./config | grep LOOP
"LOOP" must be in all caps, or it won't work.
Click to expand...
Click to collapse
thanks bat you say
Code:
cd /sdcard/wherever/
bat what it is
Code:
wherever
what i am need put there
or how i am loop my device

mihael1996 said:
thanks bat you say
Code:
cd /sdcard/wherever/
bat what it is
Code:
wherever
what i am need put there
or how i am loop my device
Click to expand...
Click to collapse
It means to just cd wherever you like. It doesn't matter where you unzip the file. Just do it in whatever folder you want. All those commands do is copy the kernel configuration to whichever folder you're in, unzip it, search for the loop device configuration options, and print it to the screen.

EndlessDissent said:
It means to just cd wherever you like. It doesn't matter where you unzip the file. Just do it in whatever folder you want. All those commands do is copy the kernel configuration to whichever folder you're in, unzip it, search for the loop device configuration options, and print it to the screen.
Click to expand...
Click to collapse
realy thank you
can you say to me from where downlode this zip file ?
from here it ok ? http://forum.xda-developers.com/showthread.php?t=2246062
and do you have a skype ?

mihael1996 said:
realy thank you
can you say to me from where downlode this zip file ?
from here it ok ? http://forum.xda-developers.com/showthread.php?t=2246062
and do you have a skype ?
Click to expand...
Click to collapse
You're not supposed to download anything. You just use the commands I posted to copy and read your current kernel config. It's all on the tablet already. You just need to type the commands.
If you want to know if that kernel supports loop devices, you could flash it before running the commands I posted. Or, just ask in the thread.
No, I don't have Skype. I hate Microsoft and everything they touch.

where i am put this commands ?

Terminal Emulator

Odin4 v1.0 for Linux

Hi Folks - The Info below is "obsolete" as @TheAirBlow found a New Version in the LAP$US Samsung leak ( something I didn't know was a thing ... show's how much attention I've been paying lately lol )
The newer version appears to support newer samsung firmwares which using lz4 files inside the tar's ( according to the license at least )
OFFICIAL Samsung Odin v4 1.2.1-dc05e3ea - For Linux
Try out my new Linux flash tool called Thor - https://forum.xda-developers.com/t/dev-thor-flash-utility-the-new-samsung-flash-tool.4597355, which has all the features of this tool + extras, like the usual Windows Odin ones which are missing in...
forum.xda-developers.com
[OLD POST BELOW]
Hi Folks
It's been a while since I posted here but I think it might be time for me to get involved again
Anyway I was reading the "Odin Downloader Release Notes.xls" and decided to translate the Korean to English. I was quite surprised to see that there was an Entry noting the release of "Odin V1.0 for Linux" ... WTF a Linux version of Odin. I figured I'd try to track this B**tard down and I've finally found one.
In some random Odin3 v3.12.7 Download I've discovered a binary called odin4 which looks legit. It's a command line tool.
The help looks like this
Code:
Usage : odin4 [args...]
Odin4 downloader. odin4 version 1.0.
-v SHOW VERSION
-w Show License
-b Add Bootloader file
-a Add AP image file
-c Add CP image file
-s Add CSC file
-u Add UMS file
-V Home binary validation check with pit file
-d Set a device path (detect automatically without this option)
-l Show downloadable devices path
IMPORTANT : You must set up your system to detect your device.
create this file: /etc/udev/rules.d/51-android.rules
to add a line to the file:
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666", GROUP="plugdev"
(http://developer.android.com/tools/device.html)
And you maybe need to unload a module cdc_acm before downloading.
$sudo rmmod cdc_acm
OR
echo "blacklist cdc_acm" > /etc/modprobe.d/cdc_acm-blacklist.conf
Example :
$sudo rmmod cdc_acm
$odin4 -b BL_XXXX.tar.md5 -a AP_XXXX.tar.md5 -c CP_XXXX.tar.md5 -s CSC_XXXX.tar.md5
Example (Select One Device):
$odin4 -l
PATH_OF_DEVICE_A
PATH_OF_DEVICE_B
$odin4 -b BL_XXXX.tar.md5 -a AP_XXXX.tar.md5 -c CP_XXXX.tar.md5 -s CSC_XXXX.tar.md5 -d PATH_OF_DEVICE_A
and the beginning of the show license has
Code:
odin4 -w
Copyright(C) 2016 Samsung Electronics.Co, Ltd. All rights reserved.
the file output is as follows
Code:
odin4: ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.24, BuildID[sha1]=bdec684a47ab0b2109cb60b1bea18e3878750f30, with debug_info, not stripped
Not stripped with debug info.. sounds interesting!
I've attached the Odin rar file I found it in if anyone is interesting in playing with it. I haven't managed to flash anything with it. although I was only attempting to flash a J320FN combination firmware.
Obviously use at your own risk etc etc.. and have fun!
trevd

Additional: I can confirm this works a treat on the Galaxy S6 at least ( SM-G920P ) :good:

[/QUOTE] I was only attempting to flash a J320FN [/QUOTE]
Well isn't that interesting. Is that the J3 series Samsung, that I have the J320, the J327 and the J337-V?

I decided to make an unexpected change to linux, currently on Ubuntu 14. So I have had to find new tools to work with. I'm not even sure this was really ever intended to work, but it does. Perfectly. restored a Galaxy S4 SM-S975L to stock using your linux based binary. Truly impressive.
---------- Post added at 05:09 PM ---------- Previous post was at 04:56 PM ----------
P.S. So far this has done everything the Windows based ODIN does. Just re-rooted with it too

It also works with newest of Samsung phones, flashed Galaxy G975U earlier, must decompress lz4 files and repack tar

kalexander7 said:
It also works with newest of Samsung phones, flashed Galaxy G975U earlier, must decompress lz4 files and repack tar
Click to expand...
Click to collapse
Yeah that's what I was doing with those newer firmwares. I did contemplate writing a bash wrapper to handle the lz4b stuff but never got round to it lol. I'm always hunting for a newer version which might slip out of Samsung by accident at some point.

Hi
Sorry for joining to this thread a few years later. I cannot find the odin4 .rar file that trevd is supposed to have uploaded. Could you pleae help?
Thanks

Would be nice if somebody has a download link for this, thanks.

feddozz said:
Hi
Sorry for joining to this thread a few years later. I cannot find the odin4 .rar file that trevd is supposed to have uploaded. Could you pleae help?
Thanks
Click to expand...
Click to collapse
Synt4x.93 said:
Would be nice if somebody has a download link for this, thanks.
Click to expand...
Click to collapse
Found one! There you go...
https://androidfilehost.com/?fid=674106145207484582
Another: https://androidfilehost.com/?fid=6006931924117939794

trevd said:
Hi Folks
It's been a while since I posted here but I think it might be time for me to get involved again
Anyway I was reading the "Odin Downloader Release Notes.xls" and decided to translate the Korean to English. I was quite surprised to see that there was an Entry noting the release of "Odin V1.0 for Linux" ... WTF a Linux version of Odin. I figured I'd try to track this B**tard down and I've finally found one.
In some random Odin3 v3.12.7 Download I've discovered a binary called odin4 which looks legit. It's a command line tool.
The help looks like this
Code:
Usage : odin4 [args...]
Odin4 downloader. odin4 version 1.0.
-v SHOW VERSION
-w Show License
-b Add Bootloader file
-a Add AP image file
-c Add CP image file
-s Add CSC file
-u Add UMS file
-V Home binary validation check with pit file
-d Set a device path (detect automatically without this option)
-l Show downloadable devices path
IMPORTANT : You must set up your system to detect your device.
create this file: /etc/udev/rules.d/51-android.rules
to add a line to the file:
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666", GROUP="plugdev"
(http://developer.android.com/tools/device.html)
And you maybe need to unload a module cdc_acm before downloading.
$sudo rmmod cdc_acm
OR
echo "blacklist cdc_acm" > /etc/modprobe.d/cdc_acm-blacklist.conf
Example :
$sudo rmmod cdc_acm
$odin4 -b BL_XXXX.tar.md5 -a AP_XXXX.tar.md5 -c CP_XXXX.tar.md5 -s CSC_XXXX.tar.md5
Example (Select One Device):
$odin4 -l
PATH_OF_DEVICE_A
PATH_OF_DEVICE_B
$odin4 -b BL_XXXX.tar.md5 -a AP_XXXX.tar.md5 -c CP_XXXX.tar.md5 -s CSC_XXXX.tar.md5 -d PATH_OF_DEVICE_A
and the beginning of the show license has
Code:
odin4 -w
Copyright(C) 2016 Samsung Electronics.Co, Ltd. All rights reserved.
the file output is as follows
Code:
odin4: ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.24, BuildID[sha1]=bdec684a47ab0b2109cb60b1bea18e3878750f30, with debug_info, not stripped
Not stripped with debug info.. sounds interesting!
I've attached the Odin rar file I found it in if anyone is interesting in playing with it. I haven't managed to flash anything with it. although I was only attempting to flash a J320FN combination firmware.
Obviously use at your own risk etc etc.. and have fun!
trevd
Click to expand...
Click to collapse
Hi, I realize that the binary you found is non exist in any other Odin download, even from it's official Odin Forum. I've been using Odin version that you've uploaded several times with big success. However, in my phone I can only flash Android 7.0 with this Odin version.
Now that I have a stock ROM for 9.0, this Odin version doesn't work. Even after I decompress lz4 and re-tar it again. After long digging on the internet, many told me that it was because I was using older version of Odin. Yours is 3.12, the latest now is 3.14. They suggested me to use newer version, little did they know I don't have Windows machine. Heimdall is a mess and never work on my Samsung, Jodin doesn't work as well.
I was wondering if you have newer version of Odin ? With binary as well ?
-------------------------------------------------------------------------------------------------------------------------
UPDATE
--------------------------------------------------------------------------------------------------------------------------
After changing ports and cable around 126722 times, I can confirm this Odin STILL WORKS !
I was able to flash a fresh ROM of Android 9 on my Samsung Galaxy S8.
TIPS : Use USB 3.0 cable, but not a fast charging cable. Fast charging cable didn't work on me at all. As for ports, port 3.0 works just fine
Only for flashing a fresh ROM. Rooting doesn't seem to work at all.

sheinbo said:
After changing ports and cables around 126721 times, I failed completely to get JODIN working - now I discover this thread- but I have to admit: I have not idea what exactly to do with odin4 (blame on me). So 2 questions: could anybody tell step by step what do do with that ODIN4 - and: did anybody flash A10 or A11?
Click to expand...
Click to collapse
1. I'm assuming you have a Linux machine ? This will run only in Linux terminal environment (or Mac -- perhaps). You can read the first post from the OP, he explains in detailed of how to use this tool (in example section), I don't think I could explain any better than the OP.
Download Odin4 from this thread, then extract it in a folder along with your extracted ROM. Inside your folder, right click and choose "Open in Terminal". Put your phone in Download mode, try to connect it 126721 times with a cable to your machine and start flashing from terminal with this code :
sudo chmod a+x odin4
./odin4 -b [your BL file] -a [your AP file] -c [your CP file] -s [your CSC file]
Click to expand...
Click to collapse
For better example, take a look at OP's original post. If flashing is succeed, your phone will restart automatically. If not, change the cable 126721 more times.
2. No. Haven't tried with A10 or A11

Question Bootloader Unlocked Warning

Has anybody figured out how to get rid of the Bootloader Unlocked warning when booting this phone? It certainly slows down the booting process.

I haven't figured it out yet. To be honest I've been trying to figure out what apps are safe to uninstall and a custom ROM or how to update to Android 12. But I'll definitely let you know if I figure a way out.

dfreedom834 said:
I haven't figured it out yet. To be honest I've been trying to figure out what apps are safe to uninstall and a custom ROM or how to update to Android 12. But I'll definitely let you know if I figure a way out.
Click to expand...
Click to collapse
I have been trying to build TWRP for this device. I am very close, but the mkbootimg command script is issuing a bad argument and I have been unable to trace it down so far.
Code:
[100% 4/4] Target boot image: /mnt/audio/android/twrp/out/target/product/minsk/boot.img
FAILED: /android/twrp/out/target/product/minsk/boot.img
/bin/bash -c "(/android/twrp/out/host/linux-x86/bin/mkbootimg --kernel /mnt/audio/android/twrp/out/target/product/minsk/kernel --ramdisk /android/twrp/out/target/product/minsk/ramdisk.img --base 0x00000000 --pagesize 4096 --cmdline \"console=ttyMSM0,115200n8 androidboot.hardware
=qcom androidboot.console=ttyMSM0 androidboot.memcg=1 lpm_levels.sleep_disabled=1 video=vfb:640x400,bpp=32,memsize=3072000 msm_rtb.filter=0x237 servic
e_locator.enable=1 swiotlb=1 androidboot.usbcontroller=a600000.dwc3 earlycon=msm_geni_serial,0x880000 loop.max_part=7 printk.devkmsg=on androidboot.ha
b.csv=10 androidboot.hab.product=minsk androidboot.hab.cid=50 firmware_class.path=/vendor/firmware_mnt/image buildvariant=user buildvariant=eng\" --os
_version 16.1.0 --os_patch_level 2099-12-31 --ramdisk_offset 0x01000000 --tags_offset 0x00000100 --dtb device/motorola/minsk/prebuilt/dtb.img --header
_version 2 --output /mnt/audio/android/twrp/out/target/product/minsk/boot.img ) && (true )"
mkbootimg: error: unrecognized arguments: --dtb device/motorola/minsk/prebuilt/dtb.img
ninja: build stopped: subcommand failed.
15:01:24 ninja failed with: exit status 1
So the --dtb should be --recovery_dtbo I believe. Not sure where this command is being generated in order to fix it.

I was running into problems like that I factor rest it and turned it off. Where did you compile the boot.img from? And ya it would work better if it was trying to go to the right path. I had to find a boot.img from one of the over seas ones I kept getting it were it would root but the screen did respond.

lexridge said:
So the --dtb should be --recovery_dtbo I believe. Not sure where this command is being generated in order to fix it.
Click to expand...
Click to collapse
I could be wrong but the recovery I'm using (orange fox) does use a kernel_dtb. So it seems your recovery image kernel doesn't have the right path to the dtb binary it needs. Try searching the build directory for any _dtb/.dtb and rename accordingly. I'd you need to alter the dtb from a related SoC there are tools for unpacking and modifying those.
The recovery and boot ones would be similar I imagine since those files are a map of the device's hardware.

dfreedom834 said:
I was running into problems like that I factor rest it and turned it off. Where did you compile the boot.img from? And ya it would work better if it was trying to go to the right path. I had to find a boot.img from one of the over seas ones I kept getting it were it would root but the screen did respond.
Click to expand...
Click to collapse
I took the boot.img from the full device A11 factory image.
MINSK_RETUS_11_RPCS31.Q2-109-16-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
I used the same one to create my magisk boot.img as well. I used dumpyara to build the device tree using the above file for my source which seemed to work properly. No errors in other words.

elrod16 said:
I could be wrong but the recovery I'm using (orange fox) does use a kernel_dtb. So it seems your recovery image kernel doesn't have the right path to the dtb binary it needs. Try searching the build directory for any _dtb/.dtb and rename accordingly. I'd you need to alter the dtb from a related SoC there are tools for unpacking and modifying those.
The recovery and boot ones would be similar I imagine since those files are a map of the device's hardware.
Click to expand...
Click to collapse
I have a dtbo directory containing these files:
Code:
00_kernel
01_dtbdump_amxbr.dtb
02_dtbdump_amxbr.dtb
03_dtbdump_amxbr.dtb
04_dtbdump_amxbr.dtb
05_dtbdump_amxbr.dtb
I also have a dtb.img in the root of the device tree. I will copy it to dtbo.img and see what happens. Thanks for the hint.

lexridge said:
I have a dtbo directory containing these files:
Code:
00_kernel
01_dtbdump_amxbr.dtb
02_dtbdump_amxbr.dtb
03_dtbdump_amxbr.dtb
04_dtbdump_amxbr.dtb
05_dtbdump_amxbr.dtb
I also have a dtb.img in the root of the device tree. I will copy it to dtbo.img and see what happens. Thanks for the hint.
Click to expand...
Click to collapse
I think dtb.img probably has all of the dtb files compiled together

elrod16 said:
I think dtb.img probably has all of the dtb files compiled together
Click to expand...
Click to collapse
That is my thought as well.

lexridge said:
That is my thought as well.
Click to expand...
Click to collapse
I just recently had to deal with all this crap because I didn't know GPD changed which revision of the mediatek SoC they used in the GPD XD while keeping the serial numbers the same. Flashed my old one's backup on it and half the cores were stuck offlined when it booted up. Ended up having to get ahold of the stock kernel for that board revision and patch in the correct dtb for that SoC.
I don't have links but some of the sites that delve into generic Linux kernel porting have tools for decompiling kernel_dtb files to an editable form that you can then recompile if you do have device/driver issues. Also the magisk module for enabling TWRP sdcard storage backups has some Android arm64 native binaries in it that can help with tearing apart kernel/recovery images. (They both are technically kernel images, just one boots a minimal OS).
Edit: I think any dtbo files would be individual compiled object files that get linked into the final dtb image.
Edit 2: I just saw your other comment above. Congrats, that sounds like a viable (and probably long term stable) way you found.

On another topic, I have been trying to mount /system as r/w (thru adb). It appears /system is not actually a mount point but under a different mount point. Any idea what that might be? Doing a cat on /proc/mounts yeilds a crapload of mounts, with many belonging to magisk, but no /system.

I know its been 4 month since last activity, but has there been any progress on this?

There does not seem to have been much progress on this, but I read somewhere recently that the G Stylus (2021) was either the most popular or best-selling Moto phone in 2021. Who knows if that is exactly true, but if it is indeed so popular, here's to hoping that some capable developers will take an interest in it eventually!

Several folks have mentioned that loading a GSI (Generic System Image) should be possible, but I have not had any extended downtime myself to be able to try this. But if you do, you can find some guidance for the 2020 version of the G Stylus at:
https://forum.xda-developers.com/t/...ic-system-image-on-the-moto-g-stylus.4131199/