Replicant

Hello Emmett,

Can you confirm that you did a full data wipe when installing 6.0004 rc1?

Cordially,
Kurtis

hello !

Yes, I did a full data wipe.

Thanks

Emmett

Do you have a full backup of your ROM / Stock ROM? I think your EFS partition is broken (I have that once, but not in Replicant)

Hi !

Thanks for your answer.
I can take a look around this.

But I supposed the EFS partition is not broken because everything worked well until now.

As I said, my phone worked well for 2 years with replicant 6.0003.
Everything worked fine. I let my phone on my desk. Two hours later, I just wanted to see if I had notification, and I discovered that my phone didn't had no signal.

The problem didn't appeared after flashing rom.
It appears because of ... forgiven it on my desk during two hours ?

It's very strange !

Hi Emmett,
could you write us the content of files /efs/FactoryApp/serial_contains and /efs/FactoryApp/hw_ver?

The folder /efs/FactoryApp/ doesn't have the file "serial_contains"
The files are :
baro_delta
batt_cable_count
earjack_count
epen_count
factorymode
fdata
hist_nv
hw_ver
keydtr
prepay
serial_no
test_nv

The content of "hw_ver" is "MP 1.300"

Hi everybody

I just flash the stock rom and I proud to say "I've got signal!!"
But I'm also sad to say "I don't know why my phone loose the signal with replicant"

Now, I have to flash a replicant rom.

So, one more question : what is the best choice between 0003 and 0004 RC1 for a daily use ?
With 0004 RC1, I understood that F-droid wasn't included. How can we install app without f-droid ?

I red this " [[https://redmine.replicant.us/projects/replicant/wiki/F-DroidAndApplications]] "
Do I have to understand that it's better to download myself apk and to take time to see if it's compliant with FSDG instead of using F-Droid ?

Thanks in advance

Emmett

Glad to hear ;)

I use Replicant 0004 RC1. Works ;)
You can install F-Droid from f-droid website.

In Replicant 0004 RC1 you have optimized LLVMPipe renderer, so you can run more applications (but still slow ... because software rendering). For example - Firefox.
But most cases are the same.

Thank you very much

I just installed 6.0004RC1

The only thing I had to do was to do a "adb kill-server && sudo adb start-server" because I hadn't root permissions to save /EFS partition

Everything seems to be fine now :-D

Hi Emmett,
I seem to have had the same pb you recently had. If I understand correctly, the solution you found is the following: you removed replicant by installing the stock rom; then you installed replicant again; and you finally got signal. Is that correct?
Can you please tell me where you got the stock rom of your device and how you flashed it (I mean which software you used)? Because I am not sure what I should do exactly with my samsung i9300.
Hope you can help,
Thx,
Louis

Hi Louis,

This is precisly what I did : Flash the stock rom.
I can't remember where I was able to find a website to download it.
I'm sure you can find something on the web
for example : https://www.phonandroid.com/forum/threads/firmware-officiel-stock-i9300xxugng3-android-4-3-samsung-galaxy-s3-i9300.99084/

To flash the stock rom, I use this command :

heimdall flash --BOOT boot.img --RECOVERY recovery.img --SYSTEM system.img --CACHE cache.img --HIDDEN hidden.img --RADIO modem.bin --BOOTLOADER sboot.bin --TZSW tz.img

I hope it gona help you !

Emmett

Thx Emmett,
I'm not sure I understand heimdall correctly though... I tried first to install the stock recovery and then to install the stock rom from the stock recovery. But I get a verification error.
Do you think I can try to install the stock rom from the replicant recovery? Or is it a bad idea?
Alternatively, is there a way to flash the stock rom without first flashing the recovery?
Maybe you can explain this to me?
Thx
Louis

Hi Emmett and all,
I did the same thing as you did, and it now works :)
Thx for the tip: it helped.
Best,
Louis

Louis R wrote:

Hi Emmett and all,
I did the same thing as you did, and it now works :)
Thx for the tip: it helped.
Best,
Louis

I've looked rapidely at the log from your bug report, and after having booted the modem, we have:

01-04 19:30:03.035  1965  2301 D use-Rlog/RLOG-RIL-IPC:
01-04 19:30:03.035  1965  2301 D use-Rlog/RLOG-RIL-IPC: xmm626_sec_modem_fmt_recv: Received FMT message
01-04 19:30:03.035  1965  2301 D use-Rlog/RLOG-RIL-IPC: xmm626_sec_modem_fmt_recv: Message: aseq=0xff, command=IPC_PWR_PHONE_PWR_UP, type=IPC_TYPE_NOTI, size=0
01-04 19:30:03.035  1965  2301 D use-Rlog/RLOG-RIL: Updating RIL radio state to 0
01-04 19:30:03.035  1965  2301 D use-Rlog/RLOG-RIL-IPC:
01-04 19:30:03.035  1965  2301 D use-Rlog/RLOG-RIL-IPC: xmm626_sec_modem_fmt_recv: Received FMT message
01-04 19:30:03.035  1965  2301 D use-Rlog/RLOG-RIL-IPC: xmm626_sec_modem_fmt_recv: Message: aseq=0x00, command=IPC_MISC_ME_IMSI, type=IPC_TYPE_NOTI, size=16
01-04 19:30:03.035  1965  2301 D use-Rlog/RLOG-RIL-IPC: ================================= IPC FMT data =================================
01-04 19:30:03.035  1965  2301 D use-Rlog/RLOG-RIL-IPC: [0000]   0F 30 30 30 30 30 30 30  30 30 30 30 30 30 30 30   .0000000 00000000
01-04 19:30:03.035  1965  2301 D use-Rlog/RLOG-RIL-IPC: ================================================================================
01-04 19:30:03.110  1965  2303 D use-Rlog/RLOG-RIL-IPC: Reading RFS data failed
01-04 19:30:03.110  1965  2303 E use-Rlog/RLOG-RIL-IPC: Receiving from IPC RFS client failed
01-04 19:30:03.110  1965  2303 E use-Rlog/RLOG-RIL: IPC RFS client loop failed
01-04 19:30:03.170  1965  2303 D use-Rlog/RLOG-RIL: Closed IPC RFS client
01-04 19:30:03.170  1965  2303 D use-Rlog/RLOG-RIL: Opened IPC RFS client

That looks like a corrupted modem data partition (EFS).

Running the stock OS or specific versions of LineageOS is capable of reparing some issues.

However we don't know yet which issues exactly.

Though we do know that it's not able to reconstruct the content of the modem data partition (EFS) from 100% from scratch.

Denis.