Salta al contenuto principale

Lanciato da Samsung a marzo 2016. Modello SM-G930.

425 Domande Visualizza tutte

Help diagnosing system crash after flash stock+factory reset+wipe?

Long question, sorry (...f****** long repair process)

I've been trying to fix my wife's phone for weeks now. The short version is that I can now flash a stock G930V firmware using Odin, phone boots, proceed through setup etc. but some time later (a few hours to a couple days at most) the phone will crash to a black screen, won't boot, doesn't seem to want to charge (meter currently shows it drawing 0.2A at 5.2V), and I can't get into DL mode. Sometimes after leaving it a while, I can get it to charge and/or enter DL mode after connecting to my PC. Then I'll flash a stock firmware (including the CSC not HOME_CSC file) boot into recovery, wipe data factory reset & clear cache. Phone boots, go through setup, (most recently we tried not importing apps or settings -only thing she installed was Tumblr app after ~12 hrs) it stays usable for hours to days, and then crashes again.

I'm sorta lost on how best to proceed, or what could be the root cause, so any and all advice is appreciated. I'm not sure I can even access the phone through my PC when it's crashed out, but if so are there any adb commands or debug apps that might shed some light?

How we got here:

Originally she had system crash after an OTA update (she thinks). We tried a wipe + clear cache, phone wouldn't boot, or got stuck in a boot loop. I was having trouble getting into recovery or DL mode, so I opened the phone to pull the battery (screen was cracked beforehand and died upon opening). Replaced that, meanwhile noticing the battery voltage was low (~2.4V) but it took a charge so I left it alone. Also noticed damage to power flex board side connector, but I checked for shorts and continuity and it was fine so I left it alone. New screen installed I flashed a stock firmware (latest 7.0 iirc) through Odin, phone boots but we can't get past setup wizard because of frp lock (either forgot the username/pass or too many password changes in the weeks the phone was out of use, even after verifying the credentials it was locked out from excess attempts).

So I proceeded to try every bypass trick I could find, changing bootloaders and upgrading and downgrading between 6.X and 7.0, so many times I couldn't even tell you, until eventually I was able to get in to enable USB debugging and used adb to update android account info. Get through setup, phone works a while, (maybe did an OTA update) then some time later crash..

Now Odin fails at "get PIT for mapping" so I try flashing several stock firmwares (with re-partition checked) until one works and the phone boots and so on and so on ad nauseam. A few days ago I replaced the battery (old one was DEAD dead) and that got it out of it's blackout state, and yet here it is on my bench dead and lifeless once again.

I'm gonna check the power flex connection again (it was fine but that was a few mating cycles ago), but if that doesn't do it I'm totally at a loss here. Do androids get malicious rootkits? Wife got one on her laptop around the same time this all started but I figured that for a coincidence (laptop was an imposter tech support remote desktop ransom scam).

Rispondi a questa domanda Anch'io ho questo problema

Questa è una buona domanda?

Punteggio 0
Aggiungi un commento

2 Risposte

Risposta Più Utile

1) Don't mess with the pit file!

2) you're not suppose to repartition

3) If you have a "V", flash the "U".

There is a thread on both XDA and Reddit on how to flash to 930U. This is the best stock rom.

NOTE: You likely will need to flash with a custom ODIN that is also posted in the same place as the "U" ROM.

4) flash the home CSC

Notes from experience:

• obviously flash to "U" with SIM card in

• it likely will boot successfully, but crash all over the place

• reboot into recovery mode, and do a factory reset

• let the setup wizard complete again, perform all updates from Samsung in Settings --> Software Update

• then repeat booting into recovery and perform another factory reset again

You should be at a nominally working phone.

Lastly, if you did mess with the PIT, the concern is you broke the file system.

Consider different MicroUSB cables.

Questa risposta è stata utile?

Punteggio 2

4 Commenti:

did you forget an "if" before the bit about the USB-C connector? I thought all S7's had mini-B connectors

da

My bad, removing the comment about USB-C. I was thinking S8, but everything else is the same.

da

I'll admit I lost some confidence when I read the USB-C bit, but ok, I'll give the U firmware a go. (I flashed one at one point, possibly as a step in downgrading the bootloader for a frp bypass hack.)

Also I did discover a malfunctioning USB host controller on my PC through this process. At first I thought bad cables, and maybe one was, but the intermittent chip failures definitely interrupted a firmware flash or two, and probably contributed to this mess.

da

Oh, it may not be malfunctioning. I had something like that while flashing the S8 (which is where the USB-C comment came from). I went to "Device Manager" to update drive and manually looked for the Samsung USB drivers. That should install the special download mode drivers. If that doesn't work, try deleting it then scanning for hardware changes.

da

Aggiungi un commento

try flash it with Official firmware in four files called “complete ROM“

Questa risposta è stata utile?

Punteggio 0
Aggiungi un commento

Aggiungi la tua risposta

Stephen Barnwell sarà eternamente grato.
Visualizza Statistiche:

Ultime 24 Ore: 1

Ultimi 7 Giorni: 2

Ultimi 30 Giorni: 4

Tutti i Tempi: 610