yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S22 Ultra] arjunmurali3:
Hi bro, which was your previous csc and to which did you change
[Samsung Galaxy S22 Ultra] AlyS79:
Hi

I didn't try the tool yet as I have the concers that I posted above.

What do you mean by the question? Will the tool behave differently depending on the origin and target CSC code?
[Samsung Galaxy S22 Ultra] AlyS79:
Hi All

I have looking for a long time for the way SamFW change the CSC code. I want to run the ADB command myslef from adb terminal. I know that SamFW exploits the test mode (*#0*#) to get to send some ADB (or may be AT commands),. I want to know these and run it manually in my personal phone, not because I want to hack the tool but simply because I don't trust what SamFW tool do in my phone (which worth a lot of money and have my personal data). I read in a forum (link below) that some security guys do reverse engineering for SamFW to know how it unlock the FRP and they found that the tool pushes file to the phone for that ( WoW! .. Imagine this ) , what if it pushes also a file while changing the CSC code ( I will never accept this)

https://blog-cyber.riskeco.com/en/analysis-of-samsung-frp-bypass/

Can you please help me in this challenge ? I want to run manually the ABD or AT commands (While in test mode of course *#0*#) to change the CSC code.

Looking forward for your help.
[Samsung Galaxy S22 Ultra] rodken:
Have you attempted to use the following ADB command to identify your current CSC code:

adb shell getprop ril.sales_code

Utilize the following command to change your CSC code to the desired one. Replace "desired_csc_code" with the actual CSC code you want to set:

adb shell setprop ril.sales_code desired_csc_code

You might want to dial #0# or *#0*# on your phone's dialer to enter Test Mode
[Samsung Galaxy S22 Ultra] AlyS79:
This property doesn't exist

The command below returns nothing

adb shell getprop ril.sales_code
[Samsung Galaxy S22 Ultra] AlyS79:
Hi Experts,

Can anyone help me please ?
[Samsung Galaxy S22 Ultra] nguyenlucky:
I used the dnSpy decompiler like the above article and found the piece of code that does the CSC change:

C#:

this.eval_a.eval_a(this.eval_c, null, a_, "Running exploit... ");

text3 = "FAIL";

this.eval_c = this.eval_a.eval_ae();

Thread.Sleep(300);

this.eval_a.SendLog("Changing CSC to ", null, true, false);

this.eval_a.SendLog(Form1.FormCSC_SelectedCsc, new Color?(Color.Blue), false, false);

this.eval_a.SendLog(" ... ", null, false, false);

string text5 = this.eval_a.eval_a(this.eval_c, "AT+PRECONFG=2," + Form1.FormCSC_SelectedCsc + "\r\n", null, 3000);

flag4 = text5.Contains("OK");

Look at this line

C#:

string text5 = this.eval_a.eval_a(this.eval_c, "AT+PRECONFG=2," + Form1.FormCSC_SelectedCsc + "\r\n", null, 3000);

It calls the eval_a() method with the an AT command and selected CSC. Going into that method:

C#:

private string eval_a(Form1.comInfo A_0, string A_1, CancellationTokenSource A_2 = null, int A_3 = 3000)

AT command + CSC is represented as variable A_1. Looking for A_1 in the method:

C#:

case 5:

{

if (flag2)

{

num = (short)1901658122;

num3 = (int)((IntPtr)num);

continue;

}

serialPort.WriteLine(A_1);

text = "";

Stopwatch stopwatch = new Stopwatch();

stopwatch.Start();

num = (short)1634336771;

num3 = (int)((IntPtr)num);

continue;

}

with serialPort defined as

C#:

SerialPort serialPort = new SerialPort("COM" + A_0.comport);

So I think what the application does is opening a COM port and writing the CSC directly with an AT command. So it doesn't seem to contain any files like the FRP method.

I cannot code in C#, just leveraging some coding knowledge and tracing the code in the decompiler. I am welcome to be corrected.
[Samsung Galaxy S22 Ultra] nguyenlucky:
I used the dnSpy decompiler and found the piece of code that does the CSC change:

this.eval_a.eval_a(this.eval_c, null, a_, "Running exploit... ");
text3 = "FAIL";
this.eval_c = this.eval_a.eval_ae();
Thread.Sleep(300);
this.eval_a.SendLog("Changing CSC to ", null, true, false);
this.eval_a.SendLog(Form1.FormCSC_SelectedCsc, new Color?(Color.Blue), false, false);
this.eval_a.SendLog(" ... ", null, false, false);
string text5 = this.eval_a.eval_a(this.eval_c, "AT+PRECONFG=2," + Form1.FormCSC_SelectedCsc + "\r\n", null, 3000);
flag4 = text5.Contains("OK");

Look at this line

string text5 = this.eval_a.eval_a(this.eval_c, "AT+PRECONFG=2," + Form1.FormCSC_SelectedCsc + "\r\n", null, 3000);

It calls the eval_a() method with the an AT command and selected CSC. Going into that method:

private string eval_a(Form1.comInfo A_0, string A_1, CancellationTokenSource A_2 = null, int A_3 = 3000)

AT command + CSC is represented as variable A_1. Looking for A_1 in the method:

case 5:
{
if (flag2)
{
num = (short)1901658122;
num3 = (int)((IntPtr)num);
continue;
}
serialPort.WriteLine(A_1);
text = "";
Stopwatch stopwatch = new Stopwatch();
stopwatch.Start();
num = (short)1634336771;
num3 = (int)((IntPtr)num);
continue;
}

with serialPort defined as

SerialPort serialPort = new SerialPort("COM" + A_0.comport);

So I think what the application does is opening a COM port and writing the CSC directly with an AT command. So it doesn't seem to contain any files like the FRP method.

I cannot code in C#, just leveraging some coding knowledge and tracing the code in the decompiler. I am welcome to be corrected.
[Samsung Galaxy S22 Ultra] loveuhp:
Can i change XAA to INDIA or Thailand. Im using S908U1
[Samsung Galaxy S22 Ultra] JeffATL:
One thing I noticed is that *#0*# is unnecessary. It works without enabling it
[Samsung Galaxy S22 Ultra] JeffATL:
No, you can't change North American CSC to international CSC
[Samsung Galaxy S22 Ultra] JeffATL:
did you ever get any further with this?
[XPERIA X1 Q&A, Help & Troubleshooting] thengwee:
Hi all,

I would like to know if there has been any ultralight ROMs produced for the X1.

I do not know why there are X1 ROMs that model the touch interface but I dun need all that silliyness as well.

Just a plain ROM will do.
[XPERIA X1 Q&A, Help & Troubleshooting] guru_fordy:
Look at Kack's ROM version 1.04. This is a lite ROM that I use :)
[XPERIA X1 Q&A, Help & Troubleshooting] rosebud:
Flash Rom / Hard reset,

go through setup, at the point the phone says customising rom in 3 seconds, soft reset the phone, none of the operator or sony stuff installed, sorted ;)

Cheers

Steve
[XPERIA X1 Q&A, Help & Troubleshooting] Angelusz:
You'll still get a lot of unneccesary winmo crap, no?
[XPERIA X1 Q&A, Help & Troubleshooting] jackleung:
Yeap, none of those being "installed". But the cabs and all those stupid media files still inside yr rom and you can see those w/ Resco explorer.
[XPERIA X1 Q&A, Help & Troubleshooting] ninja.rogue:
In case any of you is interested in new Xperia Dutty's Roms:

http://xdaforums.com/showthread.php?t=463136
[MTCD  Android Head Units Q&A] gaiex:
Hello,

I'm having problems with BT calls, I need to wait to the radio completly boots before using BT call

If I enter the car allready in a call and I start the car the BT on the unit will crash and not work any more, only after OFF/ON again.

Is there a way without opening the unit to see wich BT module/chip we have ?

or what could have been causing the problem ?

MCU version: MTCE_HLA_V.280b

Firmware: Hal9k_Mod_2.5_MTCD_MTCE_PX3_RK3188_1024x600_800х480_eng
[Touch Viva, MDA Basic ROM Development] cijoml:
Hi there,

I got Linux to boot at OPAL via linwizard project. Here are steps needed to get it work.

1) download image from:

http://tinderbox.x86.dev.gentoo.org/embedded/linwizard/gizard-20080602.tar.bz2

2) copy content of file to the microSD card

3) edit default txt and replace init=/linuxrc with init=/bin/sh

4) run haret and let it boot.

After a while you'll get to shell. No graphics.

Now you can attach microusb cable and connect it with your linux laptop (I recommend ubuntu)

and you will get usb0 interfece to start up.

Which IP to use to connect with OPAL I still must investigate.
[Touch Viva, MDA Basic ROM Development] cijoml:
Well ip connectivity now works:

ip=<client-ip>:<server-ip>:<gw-ip>:<netmask>:<hostname>:<device>:<autoconf>

Notas:/# ifconfig usb0 up 192.168.2.200 netmask 255.255.255.0

Listik:/usr/src/linux-2.6.27/Documentation# ping 192.168.2.202

PING 192.168.2.202 (192.168.2.202) 56(84) bytes of data.

64 bytes from 192.168.2.202: icmp_seq=1 ttl=64 time=2.95 ms

64 bytes from 192.168.2.202: icmp_seq=2 ttl=64 time=1.72 ms

And how to do it:

prolong "set CMDLINE" line with

ip=192.168.2.202:192.168.2.200:192.168.2.200:opal:usb0

But in this image there doesn't seem to be any telnet/ssh server running. I will try cook image with ssh server support later
[Touch Viva, MDA Basic ROM Development] zqyhqw:
Download error

Were not able to re-upload
[Touch Viva, MDA Basic ROM Development] donsalari:
404 file not found error!! :(
[Touch Viva, MDA Basic ROM Development] OndraSter:
http://tinderbox.x86.dev.gentoo.org/embedded/linwizard/

and open latest gizard-<date>.tar.bz2

or that I suppose.

The latest link should be http://tinderbox.x86.dev.gentoo.org/embedded/linwizard/gizard-20090703.tar.bz2
[Touch Viva, MDA Basic ROM Development] jonrulezz:
does this mean any chance of android working? anyone tried?
[Touch Viva, MDA Basic ROM Development] MusikMonk:
Hey,

I'm a new Opal user and I'm interested in getting *nix running on my device. I still haven't had the chance to mess around with this stuff but I'm excited to see this thread.

I was looking into the possibility of running Android on the Opal and it seems the closest thing is this thread bout running it on the Herald (it uses the same processor as the Opal).

I don't any experience in Linux porting so I thought I'd share this, in case anyone else is interested. And at the same time, I'll try to see if I can get something working based on what has been/is being done for other devices.

Sorry for the long post.
[Touch Viva, MDA Basic ROM Development] msigeek:
Hey Folks,

Any progress on getting Android on Opal? I am eagerly waiting to load one.

Kindly let me know, if this version of Linux when loaded, gives the UI.

Cheers'

Vijay
[Touch Viva, MDA Basic ROM Development] MusikMonk:
Android can boot on Opal

I have some good news, Android can boot on the Opal. This is just a proof of concept as it's missing tons of drivers and is completely useless.

Touchscreen and all keys except for the volume control (and obviously the reset button) are not working. So you basically can't do anything when you run it.

What I tried is the same as what's written in this thread about running Android on Gene. They're using the build made for the Herald/Wing (just as I was proposing in my last post) with customized initramfs and kernel.

You'll find all the necessary details in that thread. However, there's a newer build than the one mentioned there it's wing-linux-0.4pre2.cab. And the suitable kernel for that build is supposed to be the pre2 posted in this post but it didn't work on my Opal so I tried the older Gene kernel and it worked. The main difference between the two is bluetooth support, and that's obviously is of no use for us.

This doesn't effect the Windows rom, nor does it requires any special partitioning. Still it's best to have everything backed up before launching it, just in case.

This is the official site for the wing/herald build:

http://wing-linux.sf.net/

This thread on their forums about the Gene port will probably be of use to us:

http://sourceforge.net/apps/phpbb/wing-linux/viewtopic.php?f=4&t=4

I'm reading about the next steps but as I said before, I don't have any previous experience or knowledge about this type of things. If someone can give me hand, I would be more than grateful. At any rate, once I have better understanding of the concept I'll contact the people behind the Wing and the Gene ports.

P.S: If you do try to run this, keep in mind that this will take lots of time, specially for the first launch. And when you get an error saying something like "android sh: can't access tty" just ignore it and keep waiting. After a while you'll have a flashing "android" on the screen, and after some more waiting you'll reach the main screen.
[Touch Viva, MDA Basic ROM Development] msigeek:
Is this just THE BEGINNING

Sooper Stuff..!! So is this just THE BEGINNING??

How do we port the drivers and other required information in the build?

Cheers'

Vijay

www.msigeek.com
[Touch Viva, MDA Basic ROM Development] kshaurya:
A Lil' help :)

So am I.

Hmmm...

Right. Lets do it the way I did it.

1. Get the touchscreen working. Through HaRET, you must have got the GPIO interrupt whenever you pressed the touchscreen. You must have got two numbers corresponding to each press - a smaller number and a bigger number. The smaller number is the GPIO, and the larger number is, well, lets say a special GPIO value for the same pin.

Now checkout the Gene branch through git.

Goto /wing-linux/kernel/arch/arm/mach-omap1/board-htcherald.c

Scroll down to a block of code where you'll see the touchscreen code. Enter the smaller number in the .dav_gpio statement, and the IRQ number in the OMAP_GPIO_IRQ() statement below.

2. Follow the Kernel build instructions on the development section of the wing-linux wiki (the two make commands)

Copy the zImage into the linux folder on your SD card

Boot into wing-linux. The touchscreen should start working.

3. Now, hopefully, after the touchscreen's working, You would essentially just require two more buttons - the home button and the back button for minimum functionality. Everything else can be worked on by the touchscreen.

Then follow the instructions on the wing-linux forum (Page 2) to get the KEY(row,col) values of the keys on your handset. Hopefully you should get atleast a couple. Note down the corresponding keys and their KEY(r,c) values output.

4. Fire up board-htcherald.c again and goto the place where you have the KEY(r,c,KEY_blah) thing and replace the codes as per your obtained KEY(r,c,KEY_blah) values (The Home button is the one commented as Left Button)

5. That's all I can help you with as of now. I'm also figuring out a stable way of getting the DPad and the center select key to work, but It'll take some time.
[Touch Viva, MDA Basic ROM Development] MusikMonk:
Thanks kshaurya!

(This guy right here is the one who fixed the kernel for Gene, I asked him for some pointers).

I don't want to take my device apart just yet (I usually do my best not take to dismantle anything that I haven't owned for at least 3 months unless absolutely necessary) and I couldn't find a place that states what touchscreen it uses. I'm just hoping that it's the same a tsc2046 as well. [Is there anyone without a warranty and/or willing to check for us?]

I'm gonna double check the values I got from the touchscreen as for some reason I seem to have to IRQ values, probably forgot to get rid of some spamming irq. And, at the same time, I'm currently setting up a VM as a building environment, my main boot is Intrepid 64 and there's no 'psyco' package for 64 machines.

If anyone else have some experience and wants to try this, refer to: http://www.handhelds.org/moin/moin.cgi/HaRET_20Documentation (using haret to get the GPIO and IRQ values needed).

And to:

http://sourceforge.net/apps/trac/wing-linux/wiki/Development (acquiring the source code from Wing Linux and how to build it).

And a quick question for anyone that tried booting Android on the Opal, what screen did you get when Android finally finished booting?
[Touch Viva, MDA Basic ROM Development] kshaurya:
Huh? where did that come from? Wing Linux will not touch your WM.

Do you mean two? Well, that's exactly what you should get. Even if it's just one, enter that value in the code.

Oh no. dont tell me that you are building the entire thing. all you need to do is build the KERNEL! Please! Don't go into building the whole thing from scratch. Use the make ARCH ARM commands given on that page.
[Touch Viva, MDA Basic ROM Development] MusikMonk:
I mean to check the screen, in case it turned out to be different that what you have.

Yeah, stupid typo. :o

I noticed now that one of them appears when I keep the screen 'touched' for a bit longer.

I'm not gonna build the complete thing. Seems like I got too exited and failed to notice that building the kernel only requires a cross-compile toolchain, te rest is for compiling the whole thing.

I'm not THIS stupid usually . Honestly! :p

Thanks again!
[Touch Viva, MDA Basic ROM Development] kshaurya:
Its pretty normal :P
[Touch Viva, MDA Basic ROM Development] MusikMonk:
Weird.

I've only changed the two touchscreen values and built the kenrel. It finished without any error but now it won't boot.

It gets stuck, even before the space allocation part, with this error: "sh: can't access tty; job control turned off". And then it displays a prompt.

I'll try modifying an older build, I'm pulling them from the repos at the moment.

After all, the pre2 kernel from Gene didn't boot on my device (although it got stuck later on).
[Touch Viva, MDA Basic ROM Development] kshaurya:
Try doing a clean install - Remove the linux folder and try again.

Also, make sure that you're not forgetting to checkout the Gene branch.

git checkout Gene

Is your default.txt modified? And have you downloaded the modified initramfs.cpio?

check in the Gene forums for that.
[Touch Viva, MDA Basic ROM Development] MusikMonk:
Already tried the clean install, no dice. The default.txt is untouched and I'm using the modified intramfs. What happened this time is different from what happens using the original one, it's not asking me to specify the partition size but instead it's waiting for a command. I could probably ssh via usb but I have no clue how that might help.

And I've already checked out the Gene branch from the beginning.

I've tried compiling the kernel for pre1 (after changing the screen values) from SVN and it did boot (both using the cabs for pre1 and pre2) but no touch screen yet. All in all, I'm guessing that there's too much hardware difference here.

And the button for lowering volumes didn't work either, it seems like whatever you changed for getting it to work on Gene is the same as what we need here, but I'll think about that later.

I only have two ideas left:

- Trying to go back to a more stable build (with lesser features and lesser possibilities for errors). Maybe 0.3.

- Trying to create some kind of hybrid kernel using this alongside the HTC Vogue build as it probably has closer hardware to the Opal (obviously, I'm talking about everything beside the MSM7500 400MHz processor that it has). I'm hoping it won't get to this cause I'm definitely under qualified for that at the time being.
[Touch Viva, MDA Basic ROM Development] kshaurya:
Could you post a screenshot?

I'm assuming you mean the touchscreen values? Try interchanging and see.

I wouldn't recommend that. Defeats the whole purpose.

Why don't you try getting in touch with darkstar?
[Touch Viva, MDA Basic ROM Development] MusikMonk:
A friend borrowed my digital camera, I tried my laptop's webcam but the text it too blurry. Couldn't fix it using gimp either. So here's exactly what's showing on the screen:

mdir: Cannot creat directory `/mnt' : File exists
modprbe: could not parse modules.dep
initramfs: Creating device nodes:
initramfs: Loading /initrd.d/10-initfs.sh module
initramfs: Loading /initrd.d/30-wingboot.sh module

Selected:
ROOT_DEVICE=/dev/
CMDLINE=debug quiet psplash=false loglevel=7 init=/sbin/init console=tty0 video=omapfb:accel fbcon=rotate:3 4 root=/dev/
initramfs: Loading /initrd.d/80-loopboot.sh module
initramfs: Loading /initrd.d/85-blockboot.sh module
booting from: /dev/
mount: Mounting /dev/ on /mnt failed: Invalid argument
Unable to mount rootfs device

sh: can't access tty; job control turned off
/ $

And after the prompt, on the same line, there's a flashing '_' waiting for input.

Using the original zImage (from the pre2 cab) it's right around here that the screen clears and the Wing Linux installation script kicks in.

Will try that next.

I meant it as just a temporary test to till the cause of the incompatibility is figured out. With less things that could go wrong, it'll be easier to locate the ones that are going wrong.

You're right. I should post a thread on the project's forums asking for his help.
[Touch Viva, MDA Basic ROM Development] jonrulezz:
some guys have managed to port the htc hero build to the vogue, wondering if its the same of you will have to wait till it gets ported to the gene and then modify it?
[Touch Viva, MDA Basic ROM Development] MusikMonk:
I've posted a thread on the forums for the Wing-Linux project, maybe the developers there can give us some pointers (https://sourceforge.net/apps/phpbb/wing-linux/viewtopic.php?f=4&t=6).

This sums up where we stand right now:

Installing the cab and running it as is will get the installation stuck at space allocation as the Opal doesn't have a keyboard. The solution was to modify that particular script int the initramfs. When I found that the people working on the Gene port already made that modification I just used theirs.

With the initramfs replaced, the installation runs smoothly and Android boots. However, there's no touchscreen and none of the keys (beside 'volume up') works. Using the zImage from the Gene port, the 'volume down' button worked.

I've tried pulling the Gene branch from git and modifying the gpio and irq values for the touchscreen, the way kshaurya told me (here) that he did for the Gene zImage. But I'm either doing something wrong when checking out the branch or the branch itself has something wrong, cause the zImage I'm getting after building doesn't work (even without any modification from my side). It just gets stuck (before space allocation).

I tried pulling the master branch without checking out any branch and building that, and it did boot. But I still didn't have a working touchscreen after modifying the required values with the ones I got from haretconsole. I also tried the 0.3 and 0.4pre1 builds from the SVN to no avail (I did that before trying the master branch from git, somehow that didn't occur to me at that time).

There's no need to wait for a full port. If we manage to catch up to them, we should be able to progress in parallel.
[Touch Viva, MDA Basic ROM Development] bolillo:
Ok i have one little problem right after i se the big android icon it show the home screen then it says powering off.

Im using build 0.4pre1 ill try other two versions and see if thats the problem.
[Touch Viva, MDA Basic ROM Development] darkstar62:
Using 0.4pre1 or pre2, can you log in via SSH over USB to your phone during this and provide the output of the following commands:

ls -l /android/sys
ls -l /android/sys/class/power_supply
ls -l /android/sys/class/power_supply/*
cat /android/sys/class/power_supply/*/*
ls -l /sys
ls -l /sys/class/power_supply
ls -l /sys/class/power_supply/*
cat /sys/class/power_supply/*/*
ls -l /android/sys_dev

That'll give me a good indication of what Android is seeing. Also, if you can supply the output of:

chroot /android /system/bin/logcat

that would be excellent. On most every other device, this isn't an issue -- not sure why you're having this problem, but let's see if we can get to the bottom of it. :)

- d