NEED HELP - Bricked phone?

shady9090

Member
Mar 14, 2016
12
1
0
Hi!
Some days ago my phone is suddenly died. :(

Now it is in bootloop, I cannot enter in recovery mode but I can enter in Odin mode.
I tried to flash from odin different recovery (CWP, TWRP). The installation was successful, but after reboot I still cannot enter in recovery mode.

Can anybody help me?

Phone never rooted or flashed.
GT-I9195 LTE - European (Italy)
Original firmware, original rom, always updated.

Code:
CURRENT BINARY: Samsung Official
SYSTEM STATYS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
BOOTLOADER AP SWREV: 2
WRITE PROTECTION: Enable
Thank you,
Daniele
 
  • Like
Reactions: hearkenoath

Canercan

Member
Nov 4, 2016
7
1
0
recovery problem

As you are still on stock and the custom recovery has not flashed your best bet is probably to use Kies (not that I've ever done this, but that is my understanding for your situation)



I have a similar problem.
I have a bricked and then debricked GT 9190.
I have download mode but no recovery menu coming up when I booted to recovery. I tried flashing several custom recoveries without luck. Odin completes custom recovery flash and then reboots into recovery, where I see the same stock recovery screen without a menu (so there are no wipe cache, system etc.) but only the error codes below and the dead android.
I tried flashing an unroot image, which succeeded. I tried flashing through Heimdall and succeded. I tried adb and cmd but it does not detect device.
I also tried flashing 4 different stock roms for my country (TUR). 2 of them had 4 files and the other two one single file. I tried flashing a Russian version too. It flashed without problem but the recovery error persists. I have been looking for a solution for days now and I am stuck, without any light.

The error code in stock recovery:

manuel mode

appling multi csc
applying the cscs code tur

failed to compare 'system/csc/common/system/lib/libom.so' 'system/lib/libom.so'
(no data available)

E: failed to mount /cache
(invalid argument)

can't mount 'cache/' invalid argument

E: failed to mount /cache
(invalid argument)

E: can't mount cache/recovery/last_recovery


Any help will be appreciated.
 

IronRoo

Senior Member
Aug 4, 2014
1,342
434
0
Odin completes custom recovery flash and then reboots into recovery, where I see the same stock recovery screen without a menu (so there are no wipe cache, system etc.) but only the error codes below and the dead android.
I think it means recovery started but without a command. When you are In recovery screen press vol up (or maybe hold power button in then press vol up, not sure of exact combo)

edit: google recovery "no command"
 
Last edited:

Canercan

Member
Nov 4, 2016
7
1
0
I think it means recovery started but without a command. When you are In recovery screen press vol up (or maybe hold power button in then press vol up, not sure of exact combo)

edit: google recovery "no command"
Hi,

Thanks for your reply.

I tried all combinations with the buttons in the recovery menu. No luck.

It is also hard to try because it reboots after a few seconds of going to recovery screen. (with the error codes above.)

Also when I get into download mode it says Current Binary: Samsung Official and System Status: Official.
Even if I flash root file through ODIN.

I am also checking your advise no command on google. But did not come up with anything working yet.

Any other ideas?
 

IronRoo

Senior Member
Aug 4, 2014
1,342
434
0
Hi,

Thanks for your reply.

I tried all combinations with the buttons in the recovery menu. No luck.

It is also hard to try because it reboots after a few seconds of going to recovery screen. (with the error codes above.)

Also when I get into download mode it says Current Binary: Samsung Official and System Status: Official.
Even if I flash root file through ODIN.

I am also checking your advise no command on google. But did not come up with anything working yet.

Any other ideas?
Oh, it's rebooting. An unusual error but I think it is either corrupted memory or memory hardware issue.

If it was my phone I'd try flashing a pit file for your phone/country csc followed by a full stock rom (NOT the single file).

Else send for jtag if you think it's not hardware issue
 

Canercan

Member
Nov 4, 2016
7
1
0
Oh, it's rebooting. An unusual error but I think it is either corrupted memory or memory hardware issue.

If it was my phone I'd try flashing a pit file for your phone/country csc followed by a full stock rom (NOT the single file).

Else send for jtag if you think it's not hardware issue
Hi,

I contacted Samsung today and learnt that I have a month of warranty for it!
They said it was a mainboard issue, so they took it within warranty.

I hope they can do it in a couple of weeks,before I visit another country..

Thanks for your support.
 
  • Like
Reactions: IronRoo

DeadShadow80

New member
Aug 3, 2017
3
0
0
Same thing happened to me today randomly... Black screen on anything, boots only into download mode with no problem, 4 years out of warranty I guess XD...