[Q] Q: BackTrack 5 ARM (with GUI via TightVNCServer) - Xoom Q&A, Help & Troubleshooting

EDIT: Found it - I was looking at BT 5 R1 instead of just version 5, which has a release for 'arm'. Inside, there is a magical README file... finally!
-----
I apologize in advance for the rookie question but: I'm trying to follow the simple instructions from this link: http://forum.xda-developers.com/showthread.php?t=1074723 in order to install BT5 on my rooted Xoom. However, I'm stuck at two very basic steps:
- Backtrack 5 for ARM with Gnome downloaded and setup (check the README file, and follow the instructions.)
Click to expand...
Click to collapse
From the given link (http://www.backtrack-linux.org/downloads/) you are presented with 2 versions for the GNOME flavor: ISO and VM - which one is the correct one?
Also, where exactly is this elusive README file that should tell me how to set everything up?? I don't see anything on the BT website to do specifically with the XOOM and the downloaded files (ISO or VM image) don't have any README file to go with them either...
Such simple thing... I'm sure it's just staring me in the face but it's driving me crazy! Thanks in advance...

Related

How to Port a ROM to Milestone2

As lately some people are asking me about ROM porting I decided to create this new thread where we can share knowledge about this hard task.
Please note this is a Dev talk thread, so DON'T ASK about fixing a particular ROM problem here. Also don't ask questions like "My phone is bricked! please help!". This IS NOT the appropriate place for it. There are plenty of other threads to help you out.
Also note that this is not a step by step guide (and not a guide at all), it's just a point where you can start from. Android is a very complex system and there are many things I don't know yet. So, research and hard work is what you need to learn it deeply. My first tip is Google really works. Don't be afraid to search
Ok, to the basics. Porting a ROM is no simple task. It requires advanced understanding of how android works and how it is organized. Previous Linux/Unix knowledge helps A LOT. As android is based on this O.S. there are many similarities between both. In fact many ppl consider android to be a kind of linux distro.
The very first task to port a ROM is finding a device which is compatible with your own. For example Defy/Milestone2. Then you are going to choose a ROM to port to your device.
As our devices (Milestone2) have a locked bootloader we now need to find a system image that have a compatible kernel with the ROM we are trying to port. This is mainly based on trial and test and takes a long time. You'll be ending flashing your phone several times with RSD Lite. You should learn how to use MotoAndroidDepacker and how to create a fixed SBF.
The basic procedure to try that:
1. Open original ROM update.zip and remove any files/commands that flashes boot/devtree/recovery/anything.
2. Install this new file on your phone via CW Recovery.
3. Boot into bootmenu and enable ADB so you can read logcat while phone boots.
4. Choose Boot/Normal. If your ROM uses 2nd-init you will need to place/edit/adapt bootscripts into bootmenu 2nd-init folder.
5. Check logcat for errors:
- If you're getting HAL errors you're going to need a new kernel;
- If you can start android without getting HAL errors but still getting errors and bootloop on android animation you should try to replace libs with appropriate original ones.
6. Once you are able to boot android you should test it's features to see what needs to be fixed.
This is what I have to say for now. The thread is now open for discussion.
At this week, motorola has just pushed the GB official update for Droid 2 and Droid 2 Global....
Can i try to port this new rom to milestone 2 and after a success boot, fix the radio..??
I was asking that, because some people has success on port CM7 to milestone 1, when it originally maked for droid 1...
tks a lot..!!
jorgebaruchi said:
At this week, motorola has just pushed the GB official update for Droid 2 and Droid 2 Global....
Can i try to port this new rom to milestone 2 and after a success boot, fix the radio..??
I was asking that, because some people has success on port CM7 to milestone 1, when it originally maked for droid 1...
tks a lot..!!
Click to expand...
Click to collapse
It may be possible, but you'll have a hard time fixing the baseband.
You may have to mod the init.rc scripts and find the right radio binaries (rild is one of them) and drivers.
Ask those ms1 people for help, if they are still with the same phone...
Sent from my Milestone 2 XDA App
I don't know if this will be relevant or not.
I wanted to know if to do any of this, having a Linux distro as OS a must or can I try my hands at it on a windows based machine. I mean I'm sure that a Linux distro will give certain advantages (as Android is based on UNIX/Linux) but can we get things to work a 100% on windows.
If yes, then will someone be kind enough to get give the list of all softwares etc. which will be required to do the job on Windows machine as well as a Linux machine.
I do know a few softwares but I'm not sure if I have an exhaustive list. I would like to learn and try and at least be able to modify in bits n pieces to begin with.
I apologize if this wasn't supposed to be asked in this thread.
The only thing i can get from SBF is a bunch of smg files.
But the only ones i can open are
preinstall.smg
CG39.smg
Is there a way to open/see the rest?
2)
Im trying to modify the CM7 rom, what boot does it use? 2nd-init or 2nd-boot?
i guess it is second-init. but not sure
thanks a lot for this !!!
WeeDv2 said:
The only thing i can get from SBF is a bunch of smg files.
But the only ones i can open are
preinstall.smg
CG39.smg
Is there a way to open/see the rest?
2)
Im trying to modify the CM7 rom, what boot does it use? 2nd-init or 2nd-boot?
Click to expand...
Click to collapse
SMG files are disk images of certain partitions of your flash memory.
You can only open CG39.smg and preinstall (CG66.smg) because they are the only images in ext3 format. The rest of images may be on ramdisk format or some proprietary format. For more details on partition codes take a look here:
http://and-developers.com/partitions:cdt
You may be able to open and see contents of other partitions but the only one that matters aside from system and preinstall is the boot partition (CG35.smg), which contains the init scripts we should mod in order to make they work with 2nd-init. Boot partition is in ramdrive format. More details here:
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
http://elinux.org/Android_on_OMAP
It is easier to unpack boot image using Dsixda's Kitchen here:
http://forum.xda-developers.com/showthread.php?t=633246
Edit: To see what boot your CM7 uses just go inside /system/bootmenu/config and look for a file called default_bootmode.conf. That should be the boot method used. It's normally 2nd-init.
sahilarora911 said:
I don't know if this will be relevant or not.
I wanted to know if to do any of this, having a Linux distro as OS a must or can I try my hands at it on a windows based machine. I mean I'm sure that a Linux distro will give certain advantages (as Android is based on UNIX/Linux) but can we get things to work a 100% on windows.
If yes, then will someone be kind enough to get give the list of all softwares etc. which will be required to do the job on Windows machine as well as a Linux machine.
I do know a few softwares but I'm not sure if I have an exhaustive list. I would like to learn and try and at least be able to modify in bits n pieces to begin with.
I apologize if this wasn't supposed to be asked in this thread.
Click to expand...
Click to collapse
Don't worry, this is the right place
As for your question: yes you can work in windows if you like, but using at least a Linux VM is more productive. I don't have a full list of applications to give you, as different mods may require different tools, but I advice you to have at least:
- Notepad++ (essential for editing text files and keeping linux end-line format);
- dsixda's Android Kitchen (http://forum.xda-developers.com/showthread.php?t=633246)
- 7zip (or some other compress tool you like)
- Moded putty for ADB as working with windows command prompt really suck (http://forum.xda-developers.com/showthread.php?t=803225)
- Oracle Virtual Box (if you are going to use linux VM).
r2beta0 said:
SMG files are disk images of certain partitions of your flash memory.
You can only open CG39.smg and preinstall (CG66.smg) because they are the only images in ext3 format. The rest of images may be on ramdisk format or some proprietary format. For more details on partition codes take a look here:
http://and-developers.com/partitions:cdt
You may be able to open and see contents of other partitions but the only one that matters aside from system and preinstall is the boot partition (CG35.smg), which contains the init scripts we should mod in order to make they work with 2nd-init. Boot partition is in ramdrive format. More details here:
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
http://elinux.org/Android_on_OMAP
It is easier to unpack boot image using Dsixda's Kitchen here:
http://forum.xda-developers.com/showthread.php?t=633246
Edit: To see what boot your CM7 uses just go inside /system/bootmenu/config and look for a file called default_bootmode.conf. That should be the boot method used. It's normally 2nd-init.
Click to expand...
Click to collapse
Thanks again r2beta
thanks r2beta0
- Notepad++ -- got it
- dsixda's Android Kitchen -- downloaded (need some link for a how-to on its usage)
- 7zip -- got it
- Moded putty for ADB -- got it
- Oracle Virtual Box -- can't install Linux on my system as this is a work machine
dunno if I can do without the last option.
sahilarora911 said:
thanks r2beta0
- Notepad++ -- got it
- dsixda's Android Kitchen -- downloaded (need some link for a how-to on its usage)
- 7zip -- got it
- Moded putty for ADB -- got it
- Oracle Virtual Box -- can't install Linux on my system as this is a work machine
dunno if I can do without the last option.
Click to expand...
Click to collapse
Oracle Virtual Box is an application that lets you run an operational system on a virtual machine, in other words, it doesn't install linux on your real computer. It's a very useful tool that I use everyday. Google for it and learn a bit, you won't be disappointed. About kitchen: the link I provided was download + guide. Read it again. If necessary read the full thread.
r2beta0 said:
Oracle Virtual Box is an application that lets you run an operational system on a virtual machine, in other words, it doesn't install linux on your real computer. It's a very useful tool that I use everyday. Google for it and learn a bit, you won't be disappointed. About kitchen: the link I provided was download + guide. Read it again. If necessary read the full thread.
Click to expand...
Click to collapse
I know a bit about virtual box but as I said I'm not allowed to have softwares not approved by the IT team to be present on the system. Though I can get away with small things like notepad++ and 7-zip, having virtual box on my system may raise some eye brows.
I'm trying to arrange an alternative system.
Me neither. I must do almost everything at home, and at this very moment I simply don't have any free time. I'm afraid you're not going to see me here very often anymore (maybe in a few months? a year? well, it might be a bit too late for milestone2...)
hi. Have a question, I want to remove baseband from a flashable zip (lets say, CM7 from Tezet) , is it posible? I dont know where to look for it (baseband). Thanks!!
Baseband is located in \system\etc\motorola\bp_nvm_default\
But don't remove it, just replace it with files from ROM, which have baseband you want.
---UFO--- said:
Baseband is located in \system\etc\motorola\bp_nvm_default\
But don't remove it, just replace it with files from ROM, which have baseband you want.
Click to expand...
Click to collapse
Ok thanks for the info.
Sent from my A953 using XDA
Hi All,
Just a quick question. I have ported Paranoid Android 2.10 to MS2 but the problem I am facing is that Reboot goes through Bootmenu and I have to choose reboot from Bootmenu again.
Any inputs?
Thanks in advance
Megalith27 said:
Hi All,
Just a quick question. I have ported Paranoid Android 2.10 to MS2 but the problem I am facing is that Reboot goes through Bootmenu and I have to choose reboot from Bootmenu again.
Any inputs?
Thanks in advance
Click to expand...
Click to collapse
I meant to get to it last night, but I was tired after work and fell asleep watch tv. Eventually, later tonight, I'll be uploading PA for MS2. Check my Defy PA thread in 12-14 hours cause I'm about to go to work and I'm not gonna feel like making a MS2 PA thread or updating my Bravo PA thread -- but the Defy Thread is always up to date when I put out new roms.
Also, I'm looking to get either a Defy or MS2 -- I've heard that there's 3G issues with AT&T users (which I am) with the MS2 -- Apparently the MS2 has different 3G frequencies than AT&T. Are there any AT&T MS2 users who are knowledgeable about that? While I can deal with no 3G, edge only, calls only -- I need to make sure I can at least do that before I commit to something.
I'd rather have the MS2 because I want a hw keyboard and I don't have the $300+ to try and get a Photon Q LTE from eBay (and I don't have to change up my repos if I get a MS2). If anyone here knows of a phone that's AT&T compatible, Defy code compatible, and has a keyboard, please let me know.
Thanks.
//Normally I'd post the latter half in the Q&A section, but ya'll don't have one so I'm just gonna piggyback
//My Bravo doesn't have a Q&A page either -- it needs one that's not my PM box...Don't PM me on how to root your phone and flash CM7 -- read one of the 5 guides on the first page of both General & Dev...:silly:
Ok devs need some help here.
I am trying to port a rom to our Milestone 2...but it bootloops on rom animation.
I tried to logcat it but I don't think it gets as far as adb server to detect the device.and just keeps saying "waiting for device"...so I end up with no logcat to diagnose the problem.
I can logcat my current working rom but only after the phone boots....am i missing something here? please, help
Any help is very much appretiated.
Thanks a lot in advance

[Q] Ubuntu on tf101 - wifi files location

Recently I've been attempting to install Ubuntu on my transformer, after a couple of mis-fires I've gotten to a state of having ubuntu 12 and the Jhinta kernel installed - and running the latest NVFLASHable asus stock android rom.
Unfortunately i'm having trouble setting up the wi-fi, it seemed to set itself up on the old kernel but with Jhinta I need to manually grab the files. /dev/mmc0p7/ as mentioned on the wiki doesn't exist, and doing a search on the four mounted filesystems only reveals some of the required files. Placing these in /lib/firmware isn't enough unfortunately.
Ideally I'd just like a download of the files, but if anyone can give me a few pointers or push me towards an android rom that has the wiki's layout it'd be greatly appreciated!
johnnoz said:
Recently I've been attempting to install Ubuntu on my transformer, after a couple of mis-fires I've gotten to a state of having ubuntu 12 and the Jhinta kernel installed - and running the latest NVFLASHable asus stock android rom.
Unfortunately i'm having trouble setting up the wi-fi, it seemed to set itself up on the old kernel but with Jhinta I need to manually grab the files. /dev/mmc0p7/ as mentioned on the wiki doesn't exist, and doing a search on the four mounted filesystems only reveals some of the required files. Placing these in /lib/firmware isn't enough unfortunately.
Ideally I'd just like a download of the files, but if anyone can give me a few pointers or push me towards an android rom that has the wiki's layout it'd be greatly appreciated!
Click to expand...
Click to collapse
Hey,
I had these problems to.
Uhm i some how magicly fixed it.
Lets see:
1. /data/misc/wifi/wpa_supplicant.conf -> /etc/wpa_supplicant.conf #optional
2. Download the default kernel files. Unpack 3.1 bla bla kernel in ubuntu at the location of lib/modules i think. ( Use sudo nautilus )
3. backup the kernel filesi n the modules and then remove them.
4. now search linux for tegra.
5. download the version 15 not 16. ( i took harmony because it works well..)
6. Now cd to the folder and use :sudo ./app*.sh -r /
If ./ doesnt work use bash.
7. reboot
8. go to X11 ( idk where i will post it.)
9. and enable GLX
10. Enjoy
Note: I haven't fix the trackpad yet.
So u need a mouse D:
Thanks for the reply! unfortunately I'm not really sure what you mean about unpacking the kernel files. I'd already placed the 3.1 modules in lib/modules prior to installing the kernel if that's what you were referring to.
johnnoz said:
Thanks for the reply! unfortunately I'm not really sure what you mean about unpacking the kernel files. I'd already placed the 3.1 modules in lib/modules prior to installing the kernel if that's what you were referring to.
Click to expand...
Click to collapse
3.1.10-g8c2655b-dirty.tar
Thats folder should be in lib/modules.
Delete the others. (BACKUP!!)
/data/misc/wifi/wpa_supplicant.conf form your android to : /etc/wpa_supplicant.conf and /etc/wpa_supplicant.conf/wpa_supplicant.conf
Enjoy.
Thays how i fixed mine :]
Aha, thanks for the clarification! Unfortunately doing this did nothing for my wi-fi, but it did fix needing usb devices to be plugged in on boot.
I have gotten the wifi working though! It's hard to say what steps were actuallly needed, but I searched for nvram.txt and fw_bcm4329.bin, placed them in both /lib/firmware and /lib/firmware/bcm4329, found the bcm4329.ko in /modules/2.{I forget the version number}/ and moved it to the empty 3.1.10-g8c2655b-dirty folder in modules (I strongly suspect this step was pointless). What finally got it working was running modprobe bcm4329 to load the wifi module.

[Kali] Managed to Run kali on G.Tab 10.1 p5200

Hey guys,
Ok so a few weeks ago i got a G tab 10.1(p5200) as a gift. And the next thing i wanted to do after rooting was run kali linux on it, but i was disappointed to hear that its x86 based and most of the arm-el or hf images for kali linux failed to work .
So after a little tweaking and lots of trail and error i finally got kali to run on my tablet here is the summerazied step of how i did it(if anybody is intersted i can post full step-by-step instructions)
0. installed busybox-i686 binary
1. extract and mount filesystem.squashfs from kali live 32-bit iso.
2. create list of files to be copied using find from an irm image.
3. create a ~5.5GB ext4 image.
4. copy the files on the list using "for" loop.
5. mount, chroot, use
I know the that ^^ wasn't very informing but im currently testing the system for problems, and when i get on a good connection i'll upload my images, but until then i can show you how to make your own just comment .
P.S: i didn't proof read this post and for that im sorry, if you find any error's feel free to correct them.
Epslon
I am intrested ..
Hey, I just found your post. Well, is a pain when having this device SGT3 10.1 and you have intel processor. Linux deploy or other apps is useless in this case. According to your post that it works on p5200, I would like to know what you've done and the steps you took to make it works in detail.

[MOD]SplashInjector[OP3/T]

SplashInjector​splash injector is a tool created by me based on the work done by @makers_mark . it is a basic command line interface but it gets the job done. it supports all oneplus devices so far except the oneplus x :crying: i can add support once someone gets me the logo.bin file from that device. The tool is pretty simple its based on the work here https://forum.xda-developers.com/oneplus-3/themes/mod-splash-screen-image-injector-t3441999 this is where i got this all from. i know it can be kinda hacky and only supports unix systems i think you can get it working by using git bash on windows. In its current state it can decode and encode all oneplus logo.bins (Including the OnePlus 5!) it can also pack flashable zips for you automatically. all you need to do is run the decode option edit the file you want in the output folder. Then you can run the encode command and it will pack it all back up. Then package it with the package command. Once again major credit to @makers_mark he did all the leg work. i just made it a little more friendly. lmk if there is any issues you find
Telegram: @ethanbanker if you need anything contact me here.
Now lets get to it
follow the instructions here located here
https://github.com/ethanbanker2428/SplashInjector
Updates:
1.52: Ok guys im not a windows expert...i barely use it so the tool does support windows now but it cant package files. it does give you all the tools and files you need to package one tho. you can use a tool such as this https://forum.xda-developers.com/android/software-hacking/tool-6-feb-android-flashable-zip-t3551772 this update also includes a completely revamped system. lmk about any bugs you find. for windows you need to install and use GIT bash. i also added a update function to easily update the tool. its simple but it works. heres my git again for you guys https://github.com/ethanbanker2428/SplashInjector
WARNING I AM NOT RESPONSIBLE FOR ANYTHING YOU DO. DO THIS AT YOUR OWN RISK
Works great dude thanks

Updated JOdin3 CASUAL to work with current stock ROMs

Hi all,
lately I needed to flash a stock ROM image to a bricked Samsung Note 8. I did not manage to do this on my mac due to JOdin3 not working properly and me not having enough in-depth knowledge to do it by hand. So I had to occupy my son's windows laptop which bugged me.
So I took the latest JOdin3 sources I could find from https://github.com/adamoutler/android-casual and adapted it until I could successfully re-flash the Samsung mobile.
The source can be found there: https://github.com/plaili/android-casual
I also created a binary zip for use on a mac: https://github.com/plaili/android-casual/blob/master/dist/JOdin3CASUAL-0.9.0-osx-incl-JavaFX.zip
You only need
a Java 11 JDK (x86_64 - also if you are on Apple Silicon) available in path, e.g. from https://adoptopenjdk.net/
heimdall 1.4.1, e.g. from https://bitbucket.org/benjamin_dobell/heimdall/downloads/?tab=downloads
and should be good to go.
There is also a generic JAR available: https://github.com/plaili/android-casual/blob/master/dist/JOdin3CASUAL-0.9.0.jar
best regards
Markus Plail
This could be a lifesaver. Instructions and performance of Jodin3 seems highly problematic. Example, don't know which tar file to load. Have five but instructions state one. Doesn't map. ????
Have you tested this successive times?
Frosty888 said:
This could be a lifesaver. Instructions and performance of Jodin3 seems highly problematic. Example, don't know which tar file to load. Have five but instructions state one. Doesn't map. ????
Click to expand...
Click to collapse
Basically the naming of the tar files should match the buttons in my version of JOdin. What image are you trying to flash?
Frosty888 said:
Have you tested this successive times?
Click to expand...
Click to collapse
I have used it several times to flash a Samsung Note 8 if that's what you mean.
best regards
Markus
Attached image is of my Jodin3Casual-r1017-dist.jar. Mine is same as buttons on right column "OLD". Bootloader, PDA,PHONE,CSC. Note this was the latest Jodin version from the website. Will check versions again, but yours seemed to be older with *090*.
"What image trying to flash?" This
Reading conflicting info about what firmware can be flashed on specific models. Have a SM-G950F with:
* Baseband ends ARA1
* Build ends CRD7
* Service provider VOD (Vodafone UK)
Want to flash following Samsung BTU (UK Samsung) firmware:
G950FXXSBDUA3_G950FOXMBDTJ1_BTU
From this link: https://www.sammobile.com/samsung/galaxy-s8/firmware/SM-G950F/BTU/download/G950FXXSBDUA3/1243160/
Am I good to go? Is the BTU firmware compatible with my device?
BTW Latest info (mid 2020) was mixed results before your updated version. Could you explain the version numbers though. Why 0.9.0?
[Release] JOdin3 CASUAL Cross Platform and Web-Based Flashing For Samsung Phones
JOdin3 Web Browser Based and Offline flashing tool This is the official support page for JOdin3, a CASUAL-X project. JOdin3 allows you to flash Odin files on Linux, Mac and Windows. It is powered by CASUAL and Benjamin Dobell 's Heimdall...
forum.xda-developers.com
Getting the Java jar file could not be launched. Check the console etc.
Frosty888 said:
Getting the Java jar file could not be launched. Check the console etc.
Click to expand...
Click to collapse
What platform are you on? And which Java version are you using?
best regards
Markus
Frosty888 said:
BTW Latest info (mid 2020) was mixed results before your updated version. Could you explain the version numbers though. Why 0.9.0?
[Release] JOdin3 CASUAL Cross Platform and Web-Based Flashing For Samsung Phones
JOdin3 Web Browser Based and Offline flashing tool This is the official support page for JOdin3, a CASUAL-X project. JOdin3 allows you to flash Odin files on Linux, Mac and Windows. It is powered by CASUAL and Benjamin Dobell 's Heimdall...
forum.xda-developers.com
Click to expand...
Click to collapse
I do not know the versioning schema used before, so I introduced my own. As it is basically a mature program und usable I chose 0.9.0.
best regards
Markus
plaili said:
What platform are you on? And which Java version are you using?
best regards
Markus
Click to expand...
Click to collapse
Just logged out of MacOS. Believe latest Java. Will check later. The original Jodin3 loads, yours doesn't and spits the "Could not be launched error".
To be honest, haven't fully tested the original Jodin3 as deterred by the bricking horror stories others have reported. Can't afford to brick a daily driver.
[QUOTE"plaili, post: 84540119, member: 11434729"]
What platform are you on? And which Java version are you using?
best regards
Markus
[/QUOTE]
Mac 10.13.6 High Sierra
Java 8 update 101 build 1.8.0
Frosty888 said:
plaili said:
What platform are you on? And which Java version are you using?
Click to expand...
Click to collapse
Mac 10.13.6 High Sierra
Java 8 update 101 build 1.8.0
Click to expand...
Click to collapse
At the moment you need Java 11 as mentioned in the OP. I will try to provide a Java 8 compatible version.
best regards
Markus
Apologies. Java JRE version 8. Not JDK. Downloading JDK now.
Ok installed JDK 11. Results:
- Standalone jar "could not be launched"
- jar in zip same as above
How do we configure and run the files? Also seeing startJOdin3.sh????
Frosty888 said:
Apologies. Java JRE version 8. Not JDK. Downloading JDK now.
Ok installed JDK 11. Results:
- Standalone jar "could not be launched"
- jar in zip same as above
How do we configure and run the files? Also seeing startJOdin3.sh????
Click to expand...
Click to collapse
You should run startJOdin3.sh
There are special command line params necessary to start it, which are included in the shell script.
best regards
Markus
plaili said:
Hi all,
lately I needed to flash a stock ROM image to a bricked Samsung Note 8. I did not manage to do this on my mac due to JOdin3 not working properly and me not having enough in-depth knowledge to do it by hand. So I had to occupy my son's windows laptop which bugged me.
So I took the latest JOdin3 sources I could find from https://github.com/adamoutler/android-casual and adapted it until I could successfully re-flash the Samsung mobile.
The source can be found there: https://github.com/plaili/android-casual
I also created a binary zip for use on a mac: https://github.com/plaili/android-casual/blob/master/dist/JOdin3CASUAL-0.9.0-osx-incl-JavaFX.zip
You only need
a Java 11 JDK (x86_64 - also if you are on Apple Silicon) available in path, e.g. from https://adoptopenjdk.net/
heimdall 1.4.1, e.g. from https://bitbucket.org/benjamin_dobell/heimdall/downloads/?tab=downloads
and should be good to go.
There is also a generic JAR available: https://github.com/plaili/android-casual/blob/master/dist/JOdin3CASUAL-0.9.0.jar
best regards
Markus Plail
Click to expand...
Click to collapse
I Install
plaili said:
Hi all,
lately I needed to flash a stock ROM image to a bricked Samsung Note 8. I did not manage to do this on my mac due to JOdin3 not working properly and me not having enough in-depth knowledge to do it by hand. So I had to occupy my son's windows laptop which bugged me.
So I took the latest JOdin3 sources I could find from https://github.com/adamoutler/android-casual and adapted it until I could successfully re-flash the Samsung mobile.
The source can be found there: https://github.com/plaili/android-casual
I also created a binary zip for use on a mac: https://github.com/plaili/android-casual/blob/master/dist/JOdin3CASUAL-0.9.0-osx-incl-JavaFX.zip
You only need
a Java 11 JDK (x86_64 - also if you are on Apple Silicon) available in path, e.g. from https://adoptopenjdk.net/
heimdall 1.4.1, e.g. from https://bitbucket.org/benjamin_dobell/heimdall/downloads/?tab=downloads
and should be good to go.
There is also a generic JAR available: https://github.com/plaili/android-casual/blob/master/dist/JOdin3CASUAL-0.9.0.jar
best regards
Markus Plail
Click to expand...
Click to collapse
plaili said:
Hi all,
lately I needed to flash a stock ROM image to a bricked Samsung Note 8. I did not manage to do this on my mac due to JOdin3 not working properly and me not having enough in-depth knowledge to do it by hand. So I had to occupy my son's windows laptop which bugged me.
So I took the latest JOdin3 sources I could find from https://github.com/adamoutler/android-casual and adapted it until I could successfully re-flash the Samsung mobile.
The source can be found there: https://github.com/plaili/android-casual
I also created a binary zip for use on a mac: https://github.com/plaili/android-casual/blob/master/dist/JOdin3CASUAL-0.9.0-osx-incl-JavaFX.zip
You only need
a Java 11 JDK (x86_64 - also if you are on Apple Silicon) available in path, e.g. from https://adoptopenjdk.net/
heimdall 1.4.1, e.g. from https://bitbucket.org/benjamin_dobell/heimdall/downloads/?tab=downloads
and should be good to go.
There is also a generic JAR available: https://github.com/plaili/android-casual/blob/master/dist/JOdin3CASUAL-0.9.0.jar
best regards
Markus Plail
Click to expand...
Click to collapse
I Installed Jodin3, Java 11 and Heimdall, i downloaded current stock ROM (and we know .pit is inside CSC zip), but i dont want to use original "AP....md5", because i want to use the "magisk AP file".. and the .pit will not work.... what i can do?
adonisSMS said:
I installed Jodin3, Java 11 and Heimdall, i downloaded current stock ROM (and we know .pit is inside CSC zip), but i dont want to use original "AP....md5", because i want to use the "magisk AP file".. and the .pit will not work.... what i can do?
Click to expand...
Click to collapse
Extract the *.pit file from the archive. Or, you could extract it from your device using heimdall.
Keule-Tm said:
Extract the *.pit file from the archive. Or, you could extract it from your device using heimdall.
Click to expand...
Click to collapse
i already tried that, but because i am changing original AP* file by the APMagisk file, original .pit not work, it tell pit is corrupted.
adonisSMS said:
i already tried that, but because i am changing original AP* file by the APMagisk file, original .pit not work, it tell pit is corrupted.
Click to expand...
Click to collapse
Take the *.pit from the original AP*, it is the same.
Keule-Tm said:
Take the *.pit from the original AP*, it is the same.
Click to expand...
Click to collapse
How i do it?

Categories

Resources