Related
so yeah i got my first replacement after the first time this happened... i tried flashing krylon360's rom with odin but got a fail at factory.rfs. keep in mind i am in no way shape or form a noob with odin, i have brought many of my buddies' devices back to life, but for some reason even though i use a USB jig ( which works in my captivate and personally tested and working on the SGS4g before the unrecoverable soft brick) any help please i dont want to have to send it back to t-mobile again... they already charge 10bucks just for shipping.
muleman said:
so yeah i got my first replacement after the first time this happened... i tried flashing krylon360's rom with odin but got a fail at factory.rfs. keep in mind i am in no way shape or form a noob with odin, i have brought many of my buddies' devices back to life, but for some reason even though i use a USB jig ( which works in my captivate and personally tested and working on the SGS4g before the unrecoverable soft brick) any help please i dont want to have to send it back to t-mobile again... they already charge 10bucks just for shipping.
Click to expand...
Click to collapse
Hmm I'd say if the USB jig didn't work, you're not soft bricked. That's a hard brick.
What kind of USB jig are you using?
Was it a ROM or a kernel you flashed? which one, version etc.?
Jig - verified WORKING before the flash attempt
tried to flash [ROM-ODIN]T959VUVKB5 Stock + Root By: krylon360
new sgs4g
new USB cable
opened Odin first, set file
plugged in phone got a good port connection
clicked "Start"
failed at factory.rfs
phone--!--comp screen
unresponsive to JIG
donation rewards for anybody that can help! lol this is depressing, my old captivate isnt this sensitive and has been through hell and back, but this SGS4g.... im dissappointed in.
Uninstall all the drivers for the phone make sure you have the right ones also, and try plugging it into a usb 2.0 slot then run it again, this seemed to work for me. I ran into the same issue I plugged in my jig but it gave me a black screen, but odin recognized it and I flashedthe kd1 update and it was fixed. Hope this helps
muleman said:
Jig - verified WORKING before the flash attempt
tried to flash [ROM-ODIN]T959VUVKB5 Stock + Root By: krylon360
new sgs4g
new USB cable
opened Odin first, set file
plugged in phone got a good port connection
clicked "Start"
failed at factory.rfs
phone--!--comp screen
unresponsive to JIG
Click to expand...
Click to collapse
hold your horses... I got some news for you.
you can flash at that screen
try flashing mine again, or try white's ODIN image.
Along with what krylon said, maybe a bad download, try download file again
Sent from my SGH-T959V using XDA Premium App
will do thanks guys, ill try it tonight and let ya know how it goes for me.
i still dont get how odin gets a connection but the phone itself cannot with the jig... not logical but hey in the process of flashing now
krylon360 said:
hold your horses... I got some news for you.
you can flash at that screen
try flashing mine again, or try white's ODIN image.
Click to expand...
Click to collapse
youre the man.... Thanks much
muleman said:
i still dont get how odin gets a connection but the phone itself cannot with the jig... not logical but hey in the process of flashing now
Click to expand...
Click to collapse
Heimdall works at that same warning screen too. I've done it on my SGS4G.
I am confused..
sgyee said:
Heimdall works at that same warning screen too. I've done it on my SGS4G.
Click to expand...
Click to collapse
If the computer is not recognizing the phone being plugged in, how is ODIN going to be able to process? I don't know if mine SGS4G is irrepairable but when I plug it in to the computer, it will not even show up on device manager. The drivers have been installed in the past and I have used ODIN before.
When I try using ODIN now it won't work since it won't recognize the phone.
I have used JIG and simply will not buzz. It's pretty much as dead as if the phone is not even on.
Any help guys??
amishraa said:
If the computer is not recognizing the phone being plugged in, how is ODIN going to be able to process? I don't know if mine SGS4G is irrepairable but when I plug it in to the computer, it will not even show up on device manager. The drivers have been installed in the past and I have used ODIN before.
When I try using ODIN now it won't work since it won't recognize the phone.
I have used JIG and simply will not buzz. It's pretty much as dead as if the phone is not even on.
Any help guys??
Click to expand...
Click to collapse
If its currently in the state which I'm assuming..
-won't turn on, no sign of life period...
-plugging it in the wall charger won't even show the green battery status...
-won't get recognized when plugged into pc (or odin)...
-all combinations of buttons and battery pulling+usb cable plugging does nothing...
Yea I think its safe to say it went to a land far far away just like my friend's phone and only Samsung can revive it now.. Because I remember reading all the stories how everyone brought theres back to life so easily with the button combos or the jig usage, but those phones all at least showed a sign of life with that cable screen. But if its pitch black like I'm assuming then...
Same here. The jig didn't seem to work - I still got the cell + comp but odin worked anyway and reflashed stock. It's probably better to run Odin off a desktop if you have one.
That screen scared the holy hell out of me a couple of days ago. I ended up having to re-install the samsung drivers for windows 7 and then odin picked the phone right up. The reason I *knew* the phone was recoverable from that screen was simple, though:
I read the screen. It wouldn't be telling you to try something in Kies if you couldn't do anything at that screen. So, I just kept ****ing around trying different things until it worked.
*I* have personally noticed that that screen tends to come up when you accidentally or inadvertently select "Re-Partition" on a rom/image that's not setup for it, or if for any reason your phone gets disconnected or powered off during the flashing process.
That screen scared the holy hell out of me a couple of days ago. I ended up having to re-install the samsung drivers for windows 7 and then odin picked the phone right up. The reason I *knew* the phone was recoverable from that screen was simple, though:
I read the screen. It wouldn't be telling you to try something in Kies if you couldn't do anything at that screen. So, I just kept ****ing around trying different things until it worked.
*I* have personally noticed that that screen tends to come up when you accidentally or inadvertently select "Re-Partition" on a rom/image that's not setup for it, or if for any reason your phone gets disconnected or powered off during the flashing process.
Click to expand...
Click to collapse
I second this. I have been running into this screen while trying to install root from the 2.3.4 leak. I have had black screen, fuzzy screen, random pixel screen. In most cases I have been able recognize the phone using odin. A few of the key steps that I have used to get the phone recognizable in odin are:
1. If the computer says "usb not recognized" when initially plugging in the phone, uplug it and plug it back in. Most of the time when I do this the phone is recognized as samsung device.
1b: If odin now recognizes the phone after running through step 1 I will try to flash the files again. it will usually fail after trying to load the flash files on the first try. I have to mess around with this process a few times and I can usually get a successful flash.
2. I had an case when having to deal with this problem yesterday. I was running through steps 1,1b and not having success. Odin was hanging, (I forget which step). I let it sit for about 10 minutes and was still hanging. I unplugged the phone with odin still hanging pulled battery, powered on, plugged back in. Odin, which was still open and still trying to connect, continued its already started process after plugging it back in!!! This was an accident to still have the odin running and trying to connect, but after reconnecting the phone it successfully flashed!
*I* have personally noticed that that screen tends to come up when you accidentally or inadvertently select "Re-Partition" on a rom/image that's not setup for it, or if for any reason your phone gets disconnected or powered off during the flashing process.
Click to expand...
Click to collapse
These kind of observations are especially helpful! I can concur that I get the same <phone..!..pc> error, when odin tries to flash and gets a write fail, however, I do not have the "re-partition" option set. I then have to run through my previously mentioned steps to try to get a successful flash.
My question is what can i do to keep odin from failing to write when flashing?? I have only been using PDA packages, with the exception of using discrete packages (pit,csc,phone,pda) when loading the 2.3.4 rom leak.
It seems like the flashing write error in odin in causing the <phone..!..pc> error quite often with different flash processes. Does anyone have a solution to what might be causing this write error and what can be done to prevent this whole cycle? If so I sticky or new thread might be useful for other users. It has caused to have to warranty my first phone, urrrg!
Scariest feeling ever........ Not seeing your phone come up on Odin.
Sent from my SGH-T959V using XDA Premium App
Woops ahahahha. Was talkin to my friend. SOrry!
fvnktion said:
I second this. I have been running into this screen while trying to install root from the 2.3.4 leak. I have had black screen, fuzzy screen, random pixel screen. ..... [cut] ......
Click to expand...
Click to collapse
I had the same issue yesterday, when I tried to flash KD1 vanilla (stock) ROM
using ODIN, it failed the first 4 seconds, it boots into fuzzy looking screen and
that's it, every time I tried to boot it the fuzzy screen fades away to pitch black.
there is 2 possibilities that messed up the whole thing for me:
1) Bad ROM.. (i.e, can't be used with ODIN) although some members said it works
but don't know if there anything special to do before hand, if I want to downgrade.
2) Samsung Kies' fault, I installed just right before I used ODIN, and told me my
device is not registered.. hmm.
It could be both cases, but I suspect Kies the culprit, I had to uninstall it, and
uninstall the drivers came with it, installed the drivers found here in these forums,
and Odin recognized a COM port, although black screen on the phone, flashed
to KH1 and I am back to business. phew..
GB is awesome, but I can't stand the weak WIFI issue even with the latest KH1
I have to stand 3 feet away from my router to get a solid signal, with froyo
vanilla rom, I was able to connect like 50 feet away. but that's another problem
not for this thread.
Heh funny thing I read today in some thread, there is a conflict between Kies and
Odin after the incident happened. my fault for not reading a lot, jumping the gun
almost cost me the phone :/
Hello all, this is my first real post here,
and I hate to say that I have a problem! First off let me say, I have trolled(and found MANY fixes here) and never had to sign up, because anything I needed was in the search menu!! which let me say is Awesome...
However i have a different problem this time, lol
I recieved my OTA of JB, I was rooted, after following a few steps, I unrooted and was able to update to JB, I rooted again, and somehow or another, I ended up back on ICS,(I found this VERY VERY weird) didn't think this was possible, but it happened after a few flashes.
Anyways today, I plug my phone into my pc,(after a few weeks of it working properly) to upload some pictures, it automatically started to flash, I unplug, reboot(which works most of the time) however NOT this time,
I have the following on my screen
AP Fastboot Flash Mode(S)
10.98(*)(sha-56608bc, 2012-11-23 and time)
eMMC Info:size 16gb
Device is LOCKED, Status Code:0
Battery Low
Transfer Mode: USB Connected
Partition(boot) Security Version Downgraded
Fastboot Reason : Boot Failure
usb connected
I have tried to load a 3rd party xml file aquired from this site, when loading I can get into the other screen which allows me to wipe data etc. but still nothing, Also tried to just let it run its course and nothing..
Officially I am a N00b and I would like some help
The third party file, gives me the error(rsd lite 6.1.4) flash fail
Now I cannot find much info on this, and am Kinda in a bind. Any help is appreciated and I will gladly take the n00b comments with it as I realize this is my own fault..lol
update: when I boot my phone OFF of usb cord, I get fastboot reason: sticky bit factory_fastboot at the bottom now, wtf is this? lol
waynold78 said:
Hello all, this is my first real post here,
and I hate to say that I have a problem! First off let me say, I have trolled(and found MANY fixes here) and never had to sign up, because anything I needed was in the search menu!! which let me say is Awesome...
However i have a different problem this time, lol
I recieved my OTA of JB, I was rooted, after following a few steps, I unrooted and was able to update to JB, I rooted again, and somehow or another, I ended up back on ICS,(I found this VERY VERY weird) didn't think this was possible, but it happened after a few flashes.
Anyways today, I plug my phone into my pc,(after a few weeks of it working properly) to upload some pictures, it automatically started to flash, I unplug, reboot(which works most of the time) however NOT this time,
I have the following on my screen
AP Fastboot Flash Mode(S)
10.98(*)(sha-56608bc, 2012-11-23 and time)
eMMC Info:size 16gb
Device is LOCKED, Status Code:0
Battery Low
Transfer Mode: USB Connected
Partition(boot) Security Version Downgraded
Fastboot Reason : Boot Failure
usb connected
I have tried to load a 3rd party xml file aquired from this site, when loading I can get into the other screen which allows me to wipe data etc. but still nothing, Also tried to just let it run its course and nothing..
Officially I am a N00b and I would like some help
The third party file, gives me the error(rsd lite 6.1.4) flash fail
Now I cannot find much info on this, and am Kinda in a bind. Any help is appreciated and I will gladly take the n00b comments with it as I realize this is my own fault..lol
update: when I boot my phone OFF of usb cord, I get fastboot reason: sticky bit factory_fastboot at the bottom now, wtf is this? lol
Click to expand...
Click to collapse
1) Don't use the fastboot files from here just yet... they are unofficial right now. I'm working on something better.
2) Your battery is low, you should get a factory cable or factory adapter. Look it up...
danifunker said:
1) Don't use the fastboot files from here just yet... they are unofficial right now. I'm working on something better.
2) Your battery is low, you should get a factory cable or factory adapter. Look it up...
Click to expand...
Click to collapse
I seen that it was low, switched back to my wall plug and I don't know if its charging or what, but now battery is OK, weird.
Ok, I will hold off, but from what you see , does this seem fixable? I love the phone, and if its a brick, then I may be a lil heart broken but lesson learned for sure. lol
Hello
I have the pleasure of trying to help a friend with her tablet, the samsung tab 2 10.1 - gt-p5100 .
The main thing working is the on button , which will boot but only to "samsung tab2 10.1" screen and then black /turn off.
Also I can get it to boot to ODIN mode by holding VOL DWN + power,
after proceeding to Continue with VOL UP , I get the "downloading "
and the screen also tells me
ODIN MODE
Product name GT-P5100
Custom binary download: none
Current binary: Samsung_official.
Odin mode can be turned off by holding the power button for a long while.
The tablet has no functions towards VOL UP + Power which should trigger factory / recovery setting. They do no exist on this device for what ever weird reason.
If plugged in with turned of screen the screen reveals a frozen (not spinning) thinking symbol like an asterix * , the one that would turn into a battery icon should this device boot correctly. But the battery icon never shows up, only the "frozen thinking icon"
Since I have a similar device, the first tab 10.1 called gt-P7500 , some of the components are the same.
So I have trouble shooted already these steps:
Opened device , unplugged battery, waited X minutes, re-plugged. Nothing, same problems.
Opened device, replaced port cord for power cable (the I/O flat cable, is the same in the 7500), Nothing, same problems.
Opened device, replaced battery (also the same from the 7500) , Nothing, same problems.
Also a combo of the both , Nothing, same problems.
Also I reverse tested the flat cord in my own tablet , my tablet boots fine, so the cord is fine.
Also with the battery in my own tablet, my tablet boots fine, the battery looks healty and was almost full, I recharged it fully to 100 % on my own tablet before putting it back into the p5100.
I have also tried various plugs, cable, wall-chargers, car-chargers - originals and copies alike., 1amps, 2amps...from other devices, nothing
I still do no think the charging is the problem nor the battery it self, all these work on my 7500 tablet, but on the p5100 : Nothing, same problems.
Also.. I think if the tablet would have battery issues it would not power on at all and never ever get into ODIN mode, this screen can be on for hours on end.
I also downloaded to see which functions the Odin programme could help me out with, the tablet can connect to the ID:COM , no problem and find any given ROM on my HD.
Of course I also tested connecting the tablet to the PC with the original USB cable WITHOUT Odinmode, but it will trigger connected/not connected sounds and my windows 10 will say : could not identify usb etc etc , and the screen on the tablet will turn on with that "frozen thinking icon"
So..what else can I do beside ask my friend to use the darn thing as a Frisbee ??
How can I get a normal boot sequence going or regain access to recovery/factory settings ??
The device was never rooted, never repaired prior to this. The device is 4 years old, so no more warranty.
check this link
you can try flashing an official firmware without pit file, flash custom recovery and last with pit file. all details should be in the link with details, it's lengthy but should help
Ok so , the occurrences do not mean that the emmc bug has struck this tablet ??? So because it can boot to "downloader" it is still salvageable ?? Please tell me someone if this is the case :crying:
wow i hope so . I have no knowledge of the various innards so to speak, in which order the various bits and bobs are executed and therefor we could know... Meaning my hope now flashing stock/custom and so on and so forth.
What would be the indicators to the emmc bug ? It seems it is a wide spread field of errors , mostly signs of hard brick.
I have just used this P5100XXDNA1_P5100NEEDNA1_P5100XXDMG1_HOME.tar.md5 with ODIN 3.12.3 and it did nothing. The programme ran fine , it worked within minutes. But still boots the same way.
So now while writing my pc is dl'ing the 4Files Firmwares from tsar3000. Sadly I have a feeling it will still boot the same way , I will update once I have tried.
billysam said:
check this link
you can try flashing an official firmware without pit file, flash custom recovery and last with pit file. all details should be in the link with details, it's lengthy but should help
Click to expand...
Click to collapse
so the 4 file with pit from tsar site did not do any difference , still same (non)booting. What's next ? Frisbee time ?
billysam said:
check this link
you can try flashing an official firmware without pit file, flash custom recovery and last with pit file. all details should be in the link with details, it's lengthy but should help
Click to expand...
Click to collapse
vanillaHTC said:
so the 4 file with pit from tsar site did not do any difference , still same (non)booting. What's next ? Frisbee time ?
Click to expand...
Click to collapse
I did mentioned in my guide that if you can enter into download or recovery you can still save the device. but in case it didn't even recovered with the 4 files and pit and considering you tried all the stuffs you could even with the batteries. chances are the case is the faulty emmc card where it's not writing on the card anymore. suspect anything else?
playing Frisbee is a bad idea, you can keep it as a spare if your older device needs some replacement or you can get it repaired.
Hmm ok that does not leave me many options. It is the tablet of my friend, so I will return it to her.
Do you happen to know any sites that deal with the specifics of the hardware?? Meaning a website forum where I can ask these questions. I need to understand which part does what here and specifically which part is failing in this case if we are to throw any more time and money away on this piece. Cheers
billysam said:
I did mentioned in my guide that if you can enter into download or recovery you can still save the device. but in case it didn't even recovered with the 4 files and pit and considering you tried all the stuffs you could even with the batteries. chances are the case is the faulty emmc card where it's not writing on the card anymore. suspect anything else?
playing Frisbee is a bad idea, you can keep it as a spare if your older device needs some replacement or you can get it repaired.
Click to expand...
Click to collapse
Help me anyone ? I have not been able to find the exact problem like mine , described like I did ... Can someone direct me to a hardware forum where someone might know this emmc trouble, can identify it 100 % and tell me which part to exchange ? I am my friend's only help since there are no funds to buy a new tablet for her & her kid. I really hope someone can help guide me furtheron
ok thread is closed, i gave up on this device since I could find no other help and could do nothing else. She kept the charger for her phone and the device was sent to recycle.
i have some probleme
hello guys pleas can you help me i have a galaxy tab 2 10.1
and i have installed cyanogenmod 13
but it wasn't working well, my app was all the time crshing and google play was crashing also so i tryed to install manually the google play app for the version of 6.0
and now it keep staying on the robot face and don't want to work anymore
i need help pleas is my tab broken i already tryed to do a factory reset and it doesn't change anythink
smartise said:
hello guys pleas can you help me i have a galaxy tab 2 10.1
and i have installed cyanogenmod 13
but it wasn't working well, my app was all the time crshing and google play was crashing also so i tryed to install manually the google play app for the version of 6.0
and now it keep staying on the robot face and don't want to work anymore
i need help pleas is my tab broken i already tryed to do a factory reset and it doesn't change anythink
Click to expand...
Click to collapse
which recovery and which version are you running??
smart-t78 said:
which recovery and which version are you running??
Click to expand...
Click to collapse
i'm running GT-p5110
and i use philz touch
smartise said:
i'm running GT-p5110
and i use philz touch
Click to expand...
Click to collapse
philz touch is outdated. use latest common twrp from android-andis github site. you find it here http://andi34.github.io/recoveries_tab2.html .download the zip and install it with philz.
My Sony Xperia Ion won't turn on any more. I am getting a blanks screen, no LED, nothing.
I wanted to change my phone's hostname. To do that I edited the "build.prop" file as mentioned in a guide and added it. After that my phone got stuck in a boot loop. It got to the Sony logo and then rebooted again and again.
I tried flashing the stock firmware with Flashtool, but it's giving me just an error, with no error messages.
I had to do the "hard reset" (holding volume up and power until it vibrated 3 times) to turn it off to get into flashmode.
Now I don't know what happened, but the phone stopped turning on at all. The screen is just blank, no LEDs, not even when I connect it to the charger.
I followed the [GUIDE] Recover 2012 and newer XPERIAs from SOFT-brick thread and now I'm at this point. I would have asked in it for help, but I can't post there yet.
So, my question is: does anyone have any suggestions? My last hope is waiting to see if the battery will drain in a couple of days and I can get the red LED again, to try and flash the stock image (or kernel if I figure out how to get just the kernel) back. But will that work, because I didn't have luck flashing the stock image even before?
EDIT: the guides mention draining my phone's battery. How can I do that if it's unresponsive? Some posts suggest leaving it connected to a charger for a few days. How can it drain the battery if it's connected to a charger? I guess I have nothing to lose, but can someone confirm that this will indeed help me drain the battery and get a LED signal back?
Thanks in advance
Basically the very thing that ****ed up my S years ago.
I still have to understand why the hate between normal notepads and build.prop.
EDIT: an idea
Anyway, the tip is: hard shutdown the phone as soon as possible (i.e. until you feel the 3 vibration)
This way you won't waste your precious battery juice needed for reparations (and require to externally recharge battery like I had to do)
Now, if you have unlocked BL.. I guess it's easier to recover and all with fastboot, but you can do it wirh flashtool too.
The problem now is just that its latest version is bugged. You'd have to use 0.9.18.6 or older.
Thanks for the suggestion.
The problem now is just that its latest version is bugged. You'd have to use 0.9.18.6 or older.
Click to expand...
Click to collapse
Totally bugged or? Because I successfully used the latest version to flash the stock firmware recently. Do you mean I won't be able to use the latest version now specifically because of this or?
I took up the advice from the other thread and put it to charge. Now I have a solid red LED again and I guess I can follow the thread. I'm only worried about screwing it up now by using the latest version of Flashtool.
I managed to get a red LED again. I also managed to get it into flashmode, but the phone runs out of battery before the whole FTF file can be flashed (always stops at same percentage). I charged the phone all night long.
Fastboot mode seems to work fine.
Is there a way for me to flash the whole stock firmware in fastboot mode? I have the FTF file, which contains a bunch of SIN files when I unpack it.
EDIT:
I fixed it. Details can be found in the general thread about recovering Sony Xperia phones.
Hello, my phone was rooted with Magisk for about a year now. Today, the battery died while I was watching a video on youtube, and the phone shut down. When I tried to charge it, the screen woke up with red text on top saying "Custom binary blocked by FRP lock" and it kept showing this in a loop. The screen wakes up with the text, and blacks out. then again wakes up.
I tried Googling, and the solution I saw everywhere was to flash the stock firmware. I had done this once before, so
I downloaded ODIN, and then firmware from here (https://updato.com/download-samsung.../sl/sm-j120g/06975F2714E911E7963AFA163EE8F90B).
It was one .md5 file, so I put it in the AP slot and started.
Halfway through, the phone's screen blacked out and quickly came back in, but Odin said the process Failed, and the phone showed the following message.
"An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software"
Click to expand...
Click to collapse
Now, it is stuck on the above message. It is not like the normal download mode, but I can still flash the firmware through Odin. But always, halfway through, it gives the same error. The screen blackens, then quickly wakes up (takes like one second). Also, the phone doesn't seem to be charging, as when I disconnect it from the PC, it turns off completely.
My guess is, as the phone doesn't charge, it is an issue with the battery being dead.
I tried the smart switch app, but it doesn't recognize the phone.
The device is Samsung Galaxy J1 (2016) SM-J120G.
It has TWRP installed, but I can't access it now.
Rooted with Magisk.
Please help, I am a complete noob on this subject.
ChathinduN said:
Spoiler: yep
Hello, my phone was rooted with Magisk for about a year now. Today, the battery died while I was watching a video on youtube, and the phone shut down. When I tried to charge it, the screen woke up with red text on top saying "Custom binary blocked by FRP lock" and it kept showing this in a loop. The screen wakes up with the text, and blacks out. then again wakes up.
I tried Googling, and the solution I saw everywhere was to flash the stock firmware. I had done this once before, so
I downloaded ODIN, and then firmware from here (https://updato.com/download-samsung.../sl/sm-j120g/06975F2714E911E7963AFA163EE8F90B).
It was one .md5 file, so I put it in the AP slot and started.
Halfway through, the phone's screen blacked out and quickly came back in, but Odin said the process Failed, and the phone showed the following message.
Now, it is stuck on the above message. It is not like the normal download mode, but I can still flash the firmware through Odin. But always, halfway through, it gives the same error. The screen blackens, then quickly wakes up (takes like one second). Also, the phone doesn't seem to be charging, as when I disconnect it from the PC, it turns off completely.
My guess is, as the phone doesn't charge, it is an issue with the battery being dead.
I tried the smart switch app, but it doesn't recognize the phone.
The device is Samsung Galaxy J1 (2016) SM-J120G.
It has TWRP installed, but I can't access it now.
Rooted with Magisk.
Please help, I am a complete noob on this subject.
Click to expand...
Click to collapse
try it with a different cable, fresh download of the firmware, different computer or just try it several times in a row. itll likely work with a combination of some of those aforementioned methods. also could be the batt is too dead
Youdoofus said:
try it with a different cable, fresh download of the firmware, different computer or just try it several times in a row. itll likely work with a combination of some of those aforementioned methods. also could be the batt is too dead
Click to expand...
Click to collapse
Hello, I tried everything except downloading the firmware again, coz my internet is too slow. Also, I think the issue is with the phone.
First I connected the phone to the charger and left it to charge for more than 4 hours, but it still turns black randomly. So, either it is not being charged, or it's not a battery issue. Also, I tried with my brother's PC, and with another cable but the same result.
I think the device automatically reboots. When the screen goes black, it disconnects from the PC which results in failure. This happens even when not connected to a PC.
So basically, I am stuck on that error message. Once in a while, the screen turns black. Because it turns black before the flashing process is finished, it always fails.
Can you guess why the screen turns black randomly?
Thanks.
@ChathinduN
You get the Android's Black Screen Of Death because Android OS couldn't get loaded properly.
My recommendation: Re-flash Stock ROM.
jwoegerbauer said:
@ChathinduN
You get the Android's Black Screen Of Death because Android OS couldn't get loaded properly.
My recommendation: Re-flash Stock ROM.
Click to expand...
Click to collapse
But.. that's what I am trying to do. Odin fails to flash the ROM because the screen turns black.
ChathinduN said:
But.. that's what I am trying to do. Odin fails to flash the ROM because the screen turns black.
Click to expand...
Click to collapse
you very well might have a corrupted DL of the FW. Get Samfirm and download the FW with that. Its literally 4 to 5x faster than directly from sammobile.com/firmwares