Related
I posted this somewhere else, but I figured it was more appropriate to place it here.
After rooting and installing CWM using the method in the sticky at the top of the development section, (darkman's unnoficial CWM Recovery), My touchscreen no longer responds to finger input. The pen works fine, and is the only way I can navigate the tablet. Touch input doesn't work in CWM-touch either. I have tried: flashing a custom rom, flashing a stock rom through CWM, flashing stock firmware through Odin (both 4.0.4 and 4.1.2), resetting the triangle count, factory wipe/data reset, re-installing stock recovery, and changing various options in the settings. Nothing helped at all. I'm currently waiting for a reply on filing a warranty claim, but would really like not to have to send it in and wait for a new one. I've seen other people with similar issues, but most of them are either the s-pen doesn't work, or both s-pen and touch don't work. Does anyone have any idea of how to fix it, or is it definitely a hardware issue?
Thanks,
Reffu
Hi,
same issue here. Today the touchscreen stopped working suddenly after i flashed the Android Revolution HD 5.0 Rom yesterday. However, the S-Pen is still working fine. Installing other ROMs and the Stock ROM via Odin did not help. Issue allso appears in Touch-enabled-Recovery.
I see no reason, why this should be a hardware issue, although my N8000 came back from service a few days ago, where they also replaced the screen and digitizer.
Had anyone this issue before and was abled to resolve it?
Greets
I have the same problem on an n8013. Installed Revolution ROM HD version 5, rebooted and lost me touchscreen completely. Nothings worked. Flashed back to stock 4.1.2 but still no go.
Sent from my SCH-I535 using Tapatalk 2
to read this as a Note 10.1 newbie is not very encouraging. are there any similar facts between all of you like
which Note model do you have
how did you jaibreak (which method)
which rom did you have before
which rom do you have now
how did you flash a new rom
...
is there a way to find out whether the touchscreen is really "dead for touch"?
This is a bit scary - my Note 10.1 is arriving today, and I plan to root it at a minimum. I actually don't mind Touchwiz all that much on my Note 2 (which is running CleanROM ACE), so I think I might just root the 10.1 for now.
So restoring completely back to stock (via Odin) doesn't fix it? That is really odd that ROM-ing this thing might cause a hardware failure...
jiggyman said:
I have the same problem on an n8013. Installed Revolution ROM HD version 5, rebooted and lost me touchscreen completely. Nothings worked. Flashed back to stock 4.1.2 but still no go.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I would be tossing my cookies at this point ........ Did you also do a factory reset after flashing back to factory ROM?
kkretch said:
I would be tossing my cookies at this point ........ Did you also do a factory reset after flashing back to factory ROM?
Click to expand...
Click to collapse
Did anyone solve this, I'm having the same problem.
I never actually ended up solving this. I sent it in for repair (I had just bought it about a week before attempting to root) after flashing back to stock, and now I have a "new" one . I really want to root it, but I'm afraid the same thing is going to happen again. I really don't want to have to check if the warranty will cover the same issue twice, even if they don't know I rooted.
reffu said:
I never actually ended up solving this. I sent it in for repair (I had just bought it about a week before attempting to root) after flashing back to stock, and now I have a "new" one . I really want to root it, but I'm afraid the same thing is going to happen again. I really don't want to have to check if the warranty will cover the same issue twice, even if they don't know I rooted.
Click to expand...
Click to collapse
Just curious - did you just root, or did you root and install a ROM?
I am only rooted so far - haven't felt the need to ROM yet - partially due to worries about this happening. I bought a refurb from Best Buy and only get 90 days of warranty.
reffu said:
I never actually ended up solving this. I sent it in for repair (I had just bought it about a week before attempting to root) after flashing back to stock, and now I have a "new" one . I really want to root it, but I'm afraid the same thing is going to happen again. I really don't want to have to check if the warranty will cover the same issue twice, even if they don't know I rooted.
Click to expand...
Click to collapse
If they say you got a new one, you got one. They'll tell you otherwise if there's an issue over the phone.
But I wouldn't be afraid of ROMs, but to be more diligent and wise when it comes to choosing them. It's like choosing a poisonous mushroom versus an edible one to make stroganoff or stir fry. If you know what to avoid for the next time and follow the correct process to doing the root and flashing, there will not be an issues.
This is from someone who has soft-bricked my first tablet and learned how to unbrick my SIM-less Captivate and Note 10.1. It's how you apply the method and how much attention you practice not getting stuck into these situations is what matters. Especially since I bricked my tablet via experimentation and un-bricked it on the same day with ease.
It's not some big complex deal of rocket science or something only the mere geniuses can do, its how you perceive yourself and how you act. If you believe that you will suck and brick it to kingdom come , it will happen intentionally or subconsciously.
In this case, it was a freak accident where the file/s accessed and deleted the wrong files which allowed for capacitive touchscreen use, and it should be reported to x developers if you have not done so already.
I have rooted and used the Revolution HD rom, the Rom where you customize the colors of the bar/other things, and on the Captivate, the AOKP Collective. I further customized the latter with the Xperia launcher as it zips.
Did anyone find a repair for this besides replacement? My Note 2 is doing the same thing now.
Has anyone found a fix for the touch screen not working yet??
Anyone have any ideas?
Technicians input for touch problem
I am a technician and been repairing electronic devices for over 30 years and I would say the majority of repairs I have done were caused by people not happy with how their standard brand new device works and feel they need to make it better by modifying it in some way or other.
Now with smartphones if you didn't want the device as a standard rom and operating system why buy it ?
If you think the phone would be so much better with a modified rom then buy one working with a modded rom to start with as most of you put as much effort into modding as you did in your school work.
Anyone with half a brain that follows the instructions on the mod sites exactly as shown step by step will never have a problem, all those that do end up with paper weights or bricks didn't follow the instructions in numerical order.
Believe it or not even if after you have modded a rom and brought it back to standard they know it has been modded as they have a list of problems associated with repairs after roms have been modded so you are only fooling yourself they don't.
Same as the smoker that tells his Dr he has given up even though all the symptoms prove he really didn't.
So in my expert opinion if you play with modding and stuff it up why should you be eligible for a warranty claim ? The manufacturer has sold you or supplied a working item that you decided to f_ck around with and because of your stupidity expect some one else to pay for it.
I am not saying don't mod your phone with all the great roms out there but please to save yourself a lot of pain and cost some poor smuck trying to run a business in these economic times a lot of out of pocket from sending items back for replacement or warranty plus the time it takes to do all the paperwork and such, please please please read the instructions 300% or triple check you are doing everything exactly as the instructions say and you will be enjoying all the new benefits of that customised rom and laughing at all the noobs stuffing up their brand new device from not doing so.
I know this won't fix your problem but reread that last bit it was your problem as you are to clever to follow some one else's instructions
anyone have solution regarding this issue, mine have issue also, can anyone spare how to fix it without changing hardware?
---------- Post added at 06:47 AM ---------- Previous post was at 06:28 AM ----------
i hope anyone can solve my issue with touch not responding
WOW.. on TOPIC Flashing .pit might help ???
Gardum said:
I am a technician and been repairing electronic devices for over 30 years and I would say the majority of repairs I have done were caused by people not happy with how their standard brand new device works and feel they need to make it better by modifying it in some way or other.
Now with smartphones if you didn't want the device as a standard rom and operating system why buy it ?
If you think the phone would be so much better with a modified rom then buy one working with a modded rom to start with as most of you put as much effort into modding as you did in your school work.
Anyone with half a brain
Click to expand...
Click to collapse
------------------------------------------------------------------
WOW.. And you come to XDA For ? Most of the time The modded roms often fix manufacture issues and add features the manufacturer decided users do NOT Need ..Being your first post on xda . I do NOT think attacking users is the way to go. Also your post adds nothing to help the users..
ON TOPIC
Have any of you who have this issue try to do a full Wipe and flash pit file for your device.. Something is being left behind and not over written is most likely the Cause.. Also post this in the Rom developers forum So maybe he can look into it more as its his Creation..
Good Luck
erica_renee said:
------------------------------------------------------------------
WOW.. And you come to XDA For ? Most of the time The modded roms often fix manufacture issues and add features the manufacturer decided users do NOT Need ..Being your first post on xda . I do NOT think attacking users is the way to go. Also your post adds nothing to help the users..
ON TOPIC
Have any of you who have this issue try to do a full Wipe and flash pit file for your device.. Something is being left behind and not over written is most likely the Cause.. Also post this in the Rom developers forum So maybe he can look into it more as its his Creation..
Good Luck
Click to expand...
Click to collapse
thanks for reply can you give us a hint how to find pit files to flash it in Odin, pit files + official firmware tar.md5 right sir? my model is n8020 i will give it a try, thanks for reply sir
popohunters said:
thanks for reply can you give us a hint how to find pit files to flash it in Odin, pit files + official firmware tar.md5 right sir? my model is n8020 i will give it a try, thanks for reply sir
Click to expand...
Click to collapse
i Have seen them floating around random threads. There is a Thread in the General section with .pit files. Buy you MUST have the one for your Device..
Sorry i cant help I have 8013 device .
erica_renee said:
i Have seen them floating around random threads. There is a Thread in the General section with .pit files. Buy you MUST have the one for your Device..
Sorry i cant help I have 8013 device .
Click to expand...
Click to collapse
thanks sir, im done the flashing with pit files+ official firmware but touch screen is still missing, is there a modem file for touch screen maybe i missed it while its in downloading process before i brick the touch screen
any hope out there?????
confused and need help
i have a n8000 , base band version N8000XXCLL1, my touch screen stoped responding while playing a game , only Spen works , tried resetting , but no help, I'm a no-voice when it comes to programing and need a step by step guide >>>> many thanks in advance for all your help
reffu said:
I posted this somewhere else, but I figured it was more appropriate to place it here.
After rooting and installing CWM using the method in the sticky at the top of the development section, (darkman's unnoficial CWM Recovery), My touchscreen no longer responds to finger input. The pen works fine, and is the only way I can navigate the tablet. Touch input doesn't work in CWM-touch either. I have tried: flashing a custom rom, flashing a stock rom through CWM, flashing stock firmware through Odin (both 4.0.4 and 4.1.2), resetting the triangle count, factory wipe/data reset, re-installing stock recovery, and changing various options in the settings. Nothing helped at all. I'm currently waiting for a reply on filing a warranty claim, but would really like not to have to send it in and wait for a new one. I've seen other people with similar issues, but most of them are either the s-pen doesn't work, or both s-pen and touch don't work. Does anyone have any idea of how to fix it, or is it definitely a hardware issue?
I got the same problem after rooting my phone.... I used the following method and got ride of that Problem. ..
type this star code in in it Phone dialler *#2663#
Now you should see "TSP"
<update>
TAP on TSP ......it will take 5 seconds only....
......
NOW ENJOY ☺☺
Click to expand...
Click to collapse
Hi Guys,
I have GT-P3100 (Samsung Galaxy Tab2), I recently flashed Mokee ROM 4.4.4 (biggest mistake). The ROM (worked for 5-6 months) keeps restarting in every 10-15 seconds. I have tried to re-flash the ROM, but nothing is happening, I have also tried to flash the other ROMs but for most of the time I am getting this error "E: Error executing updater binary in zip 'location of the ROM file'", and even any ROM successfully installs nothing happens (the old Mokee ROM starts again on reboot, I mean come on).
I have TWRP and I tried to flash a new recovery i.e. CWM through Odin, after a successful flash TWRP starts again like the Mokee ROM.
I have also tried to flash the stock ROM fro Samsung through Odin but it fails in the middle, i have tried it multiple times. I have tried to wipe my entire phone memory, but the data and the installed ROM is still there even after a successful memory wipe
My phone keeps rebooting, I can't flash the same or any other ROM. I can't wipe my data, I can't install any other custom recovery. Nothing is happening.
The installed corrupted Mokee ROM is kind of a sticky ghost i can't get rid of. I would highly appreciate if you guys can help me out here.
If have some logs, please feel free to have a look if required. Since I am a new member I am not allowed to share a link and something is stopping to paste the logs here ( detecting a web link in the logs)
Please feel free to ask me for logs, I am always reachable at [email protected]
Thanks in advance .. I love my device.
This sounds like the dreaded eMMC (internal storage) bug that can affect some Tab2 devices, the symptoms sound similar (unable to boot properly, chip contents became read-only). This bug is caused by faulty firmware in some eMMC chips that cause problems when a particular instruction is issued (won't happen on recent ROMs and recoveries, but too late in your case). I remember there being some people who got hit by it here in XDA, but the only working solutions I remember is either replacing the eMMC chip or updating its firmware. Both solutions aren't at all easy, so I think bringing the tab to a service center would be the best option.
putr4s said:
This sounds like the dreaded eMMC (internal storage) bug that can affect some Tab2 devices, the symptoms sound similar (unable to boot properly, chip contents became read-only). This bug is caused by faulty firmware in some eMMC chips that cause problems when a particular instruction is issued (won't happen on recent ROMs and recoveries, but too late in your case). I remember there being some people who got hit by it here in XDA, but the only working solutions I remember is either replacing the eMMC chip or updating its firmware. Both solutions aren't at all easy, so I think bringing the tab to a service center would be the best option.
Click to expand...
Click to collapse
Thanks for your help. I think now I am in deep trouble in terms of phone. My device is rooted so the service center will not help me out. Perhaps I should figure out a way to do this by my own or find someone who can do this for me.
If I can have some more information, I may be able to fix this. Your information is good I am following the lead. Please share any info your think I should know, I am sure with help I will be able to find a way.
Thanks, keep rocking.
You got it fixed??
i am also facing the same issue. I flash through odin but when rebooted the old rom and recovery is there.
Odin flash is successful. but no change on EMMC content.
git it fixed?? please let me know.
bindasboy said:
You got it fixed??
i am also facing the same issue. I flash through odin but when rebooted the old rom and recovery is there.
Odin flash is successful. but no change on EMMC content.
git it fixed?? please let me know.
Click to expand...
Click to collapse
Hi,
The issue is still there, as you can see people told me the this may be caused due to an error or a malware in eMMC card of the phone (memory controller). I tried to do some research and found eMMc could be the possible problem.
I believe I installed a Chinese ROM i.e. Mokee (so called open source but I can't find its code anywhere, perhaps a fake ROM) and they did something with my phone's MBR (Master Boot Record). Re-configuring the eMMC card if so, is not an easy task and require proper equipment and knowledge of using those equipment.
I bought a new phone instead and not going to use any Chinese product ever again in my life, I hope you will be able to find a better solution for the phone.
Odin is not helpful in this case as eMMC will not take command from it. Feel free to try more option though.
Stay in touch, I am a little lazy but I will be here.
[email protected] said:
Hi,
The issue is still there, as you can see people told me the this may be caused due to an error or a malware in eMMC card of the phone (memory controller). I tried to do some research and found eMMc could be the possible problem.
I believe I installed a Chinese ROM i.e. Mokee (so called open source but I can't find its code anywhere, perhaps a fake ROM) and they did something with my phone's MBR (Master Boot Record). Re-configuring the eMMC card if so, is not an easy task and require proper equipment and knowledge of using those equipment.
I bought a new phone instead and not going to use any Chinese product ever again in my life, I hope you will be able to find a better solution for the phone.
Odin is not helpful in this case as eMMC will not take command from it. Feel free to try more option though.
Stay in touch, I am a little lazy but I will be here.
Click to expand...
Click to collapse
I don't think it is the ROM's fault as it worked for 5-6 months according to you.
Sent from my espresso3g using XDA Labs
Lightracer said:
I don't think it is the ROM's fault as it worked for 5-6 months according to you.
Sent from my espresso3g using XDA Labs
Click to expand...
Click to collapse
The ROM was installed and I never tempered with it, I became aware of the tempering when I tried to remove it or wipe internal memory. It's called a Ghostware, I checked and a lot of people with this ROM has the same problem. I hope someone will come up with some solution soon without needing to solder eMMC etc.
[email protected] said:
The ROM was installed and I never tempered with it, I became aware of the tempering when I tried to remove it or wipe internal memory. It's called a Ghostware, I checked and a lot of people with this ROM has the same problem. I hope someone will come up with some solution soon without needing to solder eMMC etc.
Click to expand...
Click to collapse
Maybe you could try asking for a solution in the ROM's thread.
Sent from my espresso3g using XDA Labs
[email protected] said:
Hi,
The issue is still there, as you can see people told me the this may be caused due to an error or a malware in eMMC card of the phone (memory controller). I tried to do some research and found eMMc could be the possible problem.
I believe I installed a Chinese ROM i.e. Mokee (so called open source but I can't find its code anywhere, perhaps a fake ROM) and they did something with my phone's MBR (Master Boot Record). Re-configuring the eMMC card if so, is not an easy task and require proper equipment and knowledge of using those equipment.
I bought a new phone instead and not going to use any Chinese product ever again in my life, I hope you will be able to find a better solution for the phone.
Odin is not helpful in this case as eMMC will not take command from it. Feel free to try more option though.
Stay in touch, I am a little lazy but I will be here.
Click to expand...
Click to collapse
The problem was with the eMMC of p3100 and not the ROM.
The only fix is using jtag, replace eMMC or get new motherboard.
I agree with @bindasboy. The symptoms are exactly the same as the emmc brick bug.
Sent from my espresso3g using XDA Labs
I just hard bricked my phone, and I'm hoping I can try to get it working again.
I have made backups using flashfire in the past. (I had a few different backups I made).
Prior to getting hard bricked, I was running the PIA firmware, but I was trying to restore from a backup that I had through flash fire, and due to a total rookie move I ended up restoring (or attempting to) restore to a PG1 unintentionally, and well now I can't do anything.
I think I may have a jig at home from a previous samsung phone (I believe an S3), would that work for my S7?
I also came across this thread: http://forum.xda-developers.com/showthread.php?t=2476353
Would that work for me?
I have a macbook pro I can use terminal with, I have a microSD card and reader, and I already have the stock PIA rom on my hard drive.
Is there hope still?
Right now regardless of what key combination I hold down my phone has a black screen.
Any help would greatly be appreciated.
Thanks in advance!
If you can't get into download mode then you don't have much to lose by trying what the other thread suggested.
@sacnotsack, thanks for the response, and that is my intention, however I am missing 1 crucial part to that thread and that is the debrick.img
Can someone with the PIA (G930TUVU4APIA) rom please post a dump of a partial system img for me? If I'm not mistaken, you can dump it with these commands in ADB.
adb shell
dd if=/dev/block/sda20 of=/sdcard/debrick.img bs=4096 count=128
Just to clarify...
sda20 should be the system partition. Any way that's what it is for me.
You can check yourself by doing typing this in ADB:
ls -al /dev/block/bootdevice/by-name
You will get something like this:
lrwxrwxrwx root root 2016-01-08 10:35 system -> /dev/block/sda20
And to get the block size you would type this:
blockdev --getbsz /dev/block/sda20
So the command
"dd if=/dev/block/sda20 of=/sdcard/debrick.img bs=4096 count=128"
If I get this working, I'll compile a nice tut for S7 users and post all the results with files in case anyone else runs into this issue.
Thank you in advance
I don't mean to be an annoyance, but does anyone have any thoughts or could point me to some direction? I know there are a lot of you that are much more knowledgable in this than I am, and all I'm hoping I can get assistance for is if someone can just make a dump of the debrick.img file so I can try to load it on my SD card.
Thanks
Hi, the easiest way to restore back to stock is to download Odin. I think it's Windows exclusive so you'll need bootcamp and install windows. After that, download Odin and extract it. Download stock firmware from androidfilehost.com, then extract. Open Odin and you'll see the options BL, AP, CP, and CSC. The firmware will have 4 or 5 files and will include these labels. Put each respective files into each options in odin. (Sometimes Odin will freeze, but let it do it's thing) After that, go into download mode (hold Volume down, Power, and Home whole turning on). Wait for Odin to recognize your device, if it doesn't, then download Samsung drivers. After it recognizes, press start and wait for the process to finish. That's it! Hopefully I was able to help.
MetalPhoenix45 said:
Hi, the easiest way to restore back to stock is to download Odin. I think it's Windows exclusive so you'll need bootcamp and install windows. After that, download Odin and extract it. Download stock firmware from androidfilehost.com, then extract. Open Odin and you'll see the options BL, AP, CP, and CSC. The firmware will have 4 or 5 files and will include these labels. Put each respective files into each options in odin. (Sometimes Odin will freeze, but let it do it's thing) After that, go into download mode (hold Volume down, Power, and Home whole turning on). Wait for Odin to recognize your device, if it doesn't, then download Samsung drivers. After it recognizes, press start and wait for the process to finish. That's it! Hopefully I was able to help.
Click to expand...
Click to collapse
MetalPhoenix45, thanks for your response. I have a Windows computer as well and I am very familiar with ODIN. The issue is, that in your explanation my guess is you are thinking the phone is in a "soft bricked" mode. The difference between a hard brick phone and a soft brick phone is that in a hard brick phone nothing is recognized when plugged in, it doesn't power on and it also doesn't show any sign of charge when it's plugged into the power.
In a soft brick mode, your phone can be stuck in a boot loop, or at the very least it still shows signs of it getting power. In which case I can just force into download mode and do what you stated above. I don't think that the things you mentioned above would work for me because when I have my phone plugged in to my computer, in device manager it doesn't detect anything. It doesn't even say unknown device or unrecognized hardware. It doesn't see it at all, and I have loaded the Samsung drivers on my pc because ODIN recognized the device prior to my issue.
I do have the stock firmware and everything on my machine, but I just can't get my phone to power or on into download boot even with a JIG.
m0d hipp¥ said:
I just hard bricked my phone, and I'm hoping I can try to get it working again.
I have made backups using flashfire in the past. (I had a few different backups I made).
Prior to getting hard bricked, I was running the PIA firmware, but I was trying to restore from a backup that I had through flash fire, and due to a total rookie move I ended up restoring (or attempting to) restore to a PG1 unintentionally, and well now I can't do anything.
I think I may have a jig at home from a previous samsung phone (I believe an S3), would that work for my S7?
I also came across this thread: http://forum.xda-developers.com/showthread.php?t=2476353
Would that work for me?
I have a macbook pro I can use terminal with, I have a microSD card and reader, and I already have the stock PIA rom on my hard drive.
Is there hope still?
Right now regardless of what key combination I hold down my phone has a black screen.
Any help would greatly be appreciated.
Thanks in advance!
Click to expand...
Click to collapse
Have you had any luck on fixing s7 I've got same issue I've even got device broken down minus the charger port due to cost of screen replacement! Not sure exactly how to test battery itself but every combination of testing battery externally I've nothing any ideas? I'd rather replace the battery vs charger port or is it completely done? This is.the first root I've ever had go wrong and haven't found any solutions yet and been looking since November
Thanks in advance for any advice
On rooted 910v now have a 920t rooted but let's just say my temper got the best of me and we'll will be replacing screen? Oddly enough as many times as the note 4 has been dropped either by myself or son not even a single scratch s7 definitely a pot more brittle!!
crazynate121 said:
Have you had any luck on fixing s7 I've got same issue I've even got device broken down minus the charger port due to cost of screen replacement! Not sure exactly how to test battery itself but every combination of testing battery externally I've nothing any ideas? I'd rather replace the battery vs charger port or is it completely done? This is.the first root I've ever had go wrong and haven't found any solutions yet and been looking since November
Thanks in advance for any advice
On rooted 910v now have a 920t rooted but let's just say my temper got the best of me and we'll will be replacing screen? Oddly enough as many times as the note 4 has been dropped either by myself or son not even a single scratch s7 definitely a pot more brittle!!
Click to expand...
Click to collapse
Unfortunately, I had no luck. I ended up haing to replace the PCB to fix the issue. Basically I learned the hard way that samsung isn't very "dev friendly". I don't blame them, but for any phone enthusiasts that plan on tinkering with their phone if you get the snapdragon version of the S7 vs the exynos version, you WILL run into trouble.
This is because the bootloader can't be unlocked on the SD models. Furthermore, if you get flagged for custom roms your warranty gets void. Over the years I've noticed Samsung is getting more and more strict about this. Honestly if you want a phone that will play nice with modding it, you should look into the google variants, Nexus, or the OnePlus. I can tell you from personal experience, OnePlus plays well with dev users. In fact they don't void the warranty for using custom roms or anything like that; in fact they're very pro and open about supporting the user base and providing a phone that the user is happy with.
Any way, that was my experience. I don't want to go off topic here, so if you have any questions you can PM me if you like, but the short answer is, if you're hard bricked then you will need to replace the motherboard/pcb. I even contacted places to see if they can jtag or jig or anything and they're not able to do it with the snapdragon S7.
bah double post, sorry I can't delete this
Funny you said nexus just ordered 2 two days ago older 7 but 4g and and what not strictly for experimental and ethical purposes of course was actually shocked at the still high priced note 5 Screen tbh but we live and learn!! SOMETIMES? LOL
m0d hipp¥ said:
Unfortunately, I had no luck. I ended up haing to replace the PCB to fix the issue. Basically I learned the hard way that samsung isn't very "dev friendly". I don't blame them, but for any phone enthusiasts that plan on tinkering with their phone if you get the snapdragon version of the S7 vs the exynos version, you WILL run into trouble.
This is because the bootloader can't be unlocked on the SD models. Furthermore, if you get flagged for custom roms your warranty gets void. Over the years I've noticed Samsung is getting more and more strict about this. Honestly if you want a phone that will play nice with modding it, you should look into the google variants, Nexus, or the OnePlus. I can tell you from personal experience, OnePlus plays well with dev users. In fact they don't void the warranty for using custom roms or anything like that; in fact they're very pro and open about supporting the user base and providing a phone that the user is happy with.
Any way, that was my experience. I don't want to go off topic here, so if you have any questions you can PM me if you like, but the short answer is, if you're hard bricked then you will need to replace the motherboard/pcb. I even contacted places to see if they can jtag or jig or anything and they're not able to do it with the snapdragon S7.
Click to expand...
Click to collapse
I am in the same boat, and considering your experience after this sore event, maybe you can help a lot of us guys here in the same situation.
My case is even worst, because, here in my country, there are NO Snapdragons, just G930F Equinoxes.
You may help im providing us lames the debrick.img file, but you must be rooted to do so. This would ve much appreciated.
Another way is to insert a blank 16GB+ SD card on the phone and format it through Odin. You just insert the card on the slot, enter download mode in the phone and load all files in Odin including the .pit. In Odin options select "Re-format" and "T Flash" that will say to the phone to format the ExtSDCard and use the ExtSDCard as destination instead of the internal emmc!
Post the image of the SD, that you can extract it with the Win32DiskImage, and you and your family will be blessed for ten generations. Also save the file in case you mess things again.
There is one method using QFil,but i'm stil trying to asemble all required files and don't now if it will even work. Should work...!!!
Anyway, can you please help us?
Best regards..
PadsPCB said:
I am in the same boat, and considering your experience after this sore event, maybe you can help a lot of us guys here in the same situation.
My case is even worst, because, here in my country, there are NO Snapdragons, just G930F Equinoxes.
You may help im providing us lames the debrick.img file, but you must be rooted to do so. This would ve much appreciated.
Another way is to insert a blank 16GB+ SD card on the phone and format it through Odin. You just insert the card on the slot, enter download mode in the phone and load all files in Odin including the .pit. In Odin options select "Re-format" and "T Flash" that will say to the phone to format the ExtSDCard and use the ExtSDCard as destination instead of the internal emmc!
Post the image of the SD, that you can extract it with the Win32DiskImage, and you and your family will be blessed for ten generations. Also save the file in case you mess things again.
There is one method using QFil,but i'm stil trying to asemble all required files and don't now if it will even work. Should work...!!!
Anyway, can you please help us?
Best regards..
Click to expand...
Click to collapse
Unfortunately, I won't be of much help. If you have the exynos S7, you would need to ask someone else with the same version of your phone for the software because the SD versions would run on different software due to different hardware.
Is there a reason why you don't try sending it out to get serviced so they can replace your PCB ?
I tried to get the debrick.img file a while back as well, but had no luck in doing so and actually I don't have my S7 phone anymore. I bought the OnePlus 3T and it's been working much better for my needs. I'm sorry to say this, but If you have any intention of modding a phone you have 2 options. 1. Get a phone that supports modding and allows you to unlock the bootloader 2. Get the unlocked variant of the phone.
If I have learned anything from my experience, it's that it is incredibly important to do your research. Not only look at the specs of the phone, but look at reviews from other users with the phone. Also if you plan on modding it, go through some threads and see how easy/difficult it is to mod that version of phone you're interested in.
m0d hipp¥ said:
Unfortunately, I won't be of much help. If you have the exynos S7, you would need to ask someone else with the same version of your phone for the software because the SD versions would run on different software due to different hardware.
Is there a reason why you don't try sending it out to get serviced so they can replace your PCB ?
I tried to get the debrick.img file a while back as well, but had no luck in doing so and actually I don't have my S7 phone anymore. I bought the OnePlus 3T and it's been working much better for my needs. I'm sorry to say this, but If you have any intention of modding a phone you have 2 options. 1. Get a phone that supports modding and allows you to unlock the bootloader 2. Get the unlocked variant of the phone.
If I have learned anything from my experience, it's that it is incredibly important to do your research. Not only look at the specs of the phone, but look at reviews from other users with the phone. Also if you plan on modding it, go through some threads and see how easy/difficult it is to mod that version of phone you're interested in.
Click to expand...
Click to collapse
Then i think got stuck, beacause in these forums there is no one willing/able/interested in helping anyone.
I said i'm in the SAME boat == I got an SM-G930T (from T-Mobile) that has a SnapDragon cpu but HERE in my country THERE ARE NO Snapdragons only Equinoxes. If we had such phones here surely i would have done this already, but G930F's won't do, as i have already tried.
So, as you know how i feel about a brand new SM-G930T Bricked, you wold be my last hope. There is no way to send it back to Samsung beacause it was bought from a friend and surely no warranty.
Anyway, best regards and rest in peace
Oh sorry, I misunderstood you. I'd like to think that it's not so much people don't want to try to help out, it's just that there is nothing that can be done for users on the snapdragon device so no one bothers unfortunately. Sorry to hear about this, and it really is unfortunate that you had to go through the same thing I went through with no help. Trust me, if I was able to do anything to provide any guidance I would.
Good luck!
This is the Odin ROM of the PL1 software for the Samsung Galaxy J3 Emerge. It was pulled from Smart Switch, which is the replacement to Kies. This is specifically for the SM-J327P for Sprint. It would appear that Boost and Virgin Mobile variants can be flashed as they are used on Sprint's network, but no promises will be made.
By using these files, any user assumes the responsibility for their devices, that they understand how to use the files and software, and accept any and all risks involved with such operations.
When selecting the files in Odin, one must select the appropriate files based on the prefix of the file name. Each of the four boxes must have a file listing.
In the "CSC" box, use the file beginning with "home_CSC" to retain your user data, or use the "CSC" file to completely wipe user data. If you bricked your device, you may need to resort to using the "CSC" file. If you flash with "home" and it still fails to work, use "CSC." (that's my understanding of the two files anyways)
If you are down-grading, you may have to select the "NAND erase all" check box. This will completely wipe the device and should allow a fresh install. Be careful, if the phone dies, I would worry about a hard brick, but I'm not positive about that though.
Google Drive link:
https://drive.google.com/file/d/0B2iEgzRTFjrQWlpEbURIWUlXLWc/view?usp=drivesdk
There have been several reports that these Odin ROMs fail to flash. If that happens to you, you may be able to try an alternate procedure here. Keep in mind this procedure will trip Knox and probably void warranty if you haven't done that already:
https://forum.xda-developers.com/general/general/rom-stock-pl1-samsung-galaxy-j3-emerge-t3689346
The newer QI1 version is posted here, and has been confirmed:
https://forum.xda-developers.com/showpost.php?p=74171277&postcount=39
and if you're more enterprising with your computer and image file skills:
https://forum.xda-developers.com/showpost.php?p=74137125&postcount=29
Greaper88 said:
This is the Odin ROM of the PL1 software for the Samsung Galaxy J3 Emerge. It was pulled from Smart Switch, which is the replacement to Kies. This is specifically for the SM-J327P for Sprint.
By using these files, any user assumes the responsibility for their devices, that they understand how to use the files and software, and accept any and all risks involved with such operations.
When selecting the files in Odin, one must select the appropriate files based on the prefix of the file name. Each of the four boxes must have a file listing. I'm not sure what the difference between the "CSC" and the "HOME _CSC" files is (or that it really matters), but I'd imagine that if one is resorting to this, then someone could tell us... Based on my previous devices, I'd recommend the "CSC" file.
https://drive.google.com/file/d/0B2iEgzRTFjrQWlpEbURIWUlXLWc/view?usp=drivesdk
Click to expand...
Click to collapse
good stuff broseph,might (MIGHT) have a go ,idk re cinfiging my type of peivacy and workarounds aint time cheap so ill leave it at that, good ish tho, I wanna create a deodexed verasion myself but had a setback pc wise regarding a unbootable Hdd , I believe a deodexed rom to be a pre-requisite to having the xposed framework workout ....am i correct in believing this guys and gals? Let me know because I really love my ubuntu pc and would most likely buy a hdd just for these type of tasks since compipation would require over 100gb from what I have heard ,. 4 gb file then decompile and rexompile eaxh of the apps and framework resources.
Doctur said:
good stuff broseph,might (MIGHT) have a go ,idk re cinfiging my type of peivacy and workarounds aint time cheap so ill leave it at that, good ish tho, I wanna create a deodexed verasion myself but had a setback pc wise regarding a unbootable Hdd , I believe a deodexed rom to be a pre-requisite to having the xposed framework workout ....am i correct in believing this guys and gals? Let me know because I really love my ubuntu pc and would most likely buy a hdd just for these type of tasks since compipation would require over 100gb from what I have heard ,. 4 gb file then decompile and rexompile eaxh of the apps and framework resources.
Click to expand...
Click to collapse
The system ROM is actually about five and a half gigabytes based on the storage info in the device settings (on my device anyways). So here's what I'm thinking makes sense for space required. I'm just gonna round the decompiled ROM up to 6GB to allow room to play with. Here's the space you'll need at a minimum:
1. 6GB for the compiled ROM.
2. 6GB for the decompiled ROM.
3. 6GB minimum for working with the ROM, so that your source is unmodified.
4. 6GB for the recompiled ROM.
So you'd need a minimum of 24 GB to work with, but the more you have, the more breathing room you have. This is just my 2¢... As for the rest of it, I have no real clue.
I just bought the j327p last week and I am returning it today if I can't get the tethering to work.
I tried editing a lot of the easily searchable fixes which there aren't many.
Do you know if installing this might work?
Just obtained this phone from Boost Mobile. Am I correct in thinking that this ROM should work on a Boost Mobile phone seeing as Boost is an MVNO of Sprint?
SammaelAkuma said:
Just obtained this phone from Boost Mobile. Am I correct in thinking that this ROM should work on a Boost Mobile phone seeing as Boost is an MVNO of Sprint?
Click to expand...
Click to collapse
It works and it's been updated from APL1 to AQB6 .. at least mine has .. and I don't know what was updated or what's new but it's still on Android 6.0 .. I just used this to fix my Boost J3 Emerge after it got stuck installing an app from the Galaxy S8
Doctur said:
...I believe a deodexed rom to be a pre-requisite to having the xposed
This link will get xposed to work...
https://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
TD378
Divided we stall,
United We Install!
Click to expand...
Click to collapse
Actually Wanam got xposed working on our device. Nice tut but its really almost standard issue when dealing with samsung. Im guessing this is your first galaxy phone? Personally done myself on the galaxy s4 sch r970 (ya the one from 2013.. ), j7 j700t and this galaxy emerge 327p, there are also many tutorials on how to do so, thanks for trying to help, but you could have just linked wanams thread wich has all cautions and tuts in like 12 words a HUGE thanks to Wanam for spending countless hours making a modded version of xposed that is compatible with ours as well as many other galaxy devices!!!
Project89Odin said:
...Im guessing this is your first galaxy phone? Personally done myself on the galaxy s4 sch r970 (ya the one from 2013.. ), j7 j700t and this galaxy emerge 327p...
Click to expand...
Click to collapse
Choose to stay away from "main stream" phones for a number of reasons.
But at the request of your post, link has been updated!
TD378
DIVIDED WE STALL
UNITED WE INSTALL
Thank you, the Galaxy J3 is not a very followed device by samsung of the fact that it is not high-end
________________________________________________________________________________
http://iphon8.fr/ galaxy note 9
Greaper88 said:
This is the Odin ROM of the PL1 software for the Samsung Galaxy J3 Emerge. It was pulled from Smart Switch, which is the replacement to Kies. This is specifically for the SM-J327P for Sprint.
By using these files, any user assumes the responsibility for their devices, that they understand how to use the files and software, and accept any and all risks involved with such operations.
When selecting the files in Odin, one must select the appropriate files based on the prefix of the file name. Each of the four boxes must have a file listing. I'm not sure what the difference between the "CSC" and the "HOME _CSC" files is (or that it really matters), but I'd imagine that if one is resorting to this, then someone could tell us... Based on my previous devices, I'd recommend the "CSC" file.
Click to expand...
Click to collapse
I'm having a severe problem right now... I'm praying this works. I keep getting a "SECURE CHECK FAIL : ABOOT" error with every firmware I try. I have a bricked j3 emerge.
do you have any tips on which file I can put where in odin? I was patient to let this download... and I feel like this is the closest thing I have that will get it working.
vivianajeanty said:
I'm having a severe problem right now... I'm praying this works. I keep getting a "SECURE CHECK FAIL : ABOOT" error with every firmware I try. I have a bricked j3 emerge.
do you have any tips on which file I can put where in odin? I was patient to let this download... and I feel like this is the closest thing I have that will get it working.
Click to expand...
Click to collapse
Download the default firmware here...
http://updato.com/firmware-archive-select-model?record=F2F2C99C28B211E7963AFA163EE8F90B
In Odin, put each file in the correct section "ex. APxxx goes in AP section."
Use CSCxxx file NOT Home_CSCxxx in CSC section. All data will be lost.
Brick problem will be solved. Let me know if you need a tut created.
TD378
Divided we stall
United we install
If refering to me as this being my first Samsung that would be a negative....mainly all ive dealt with or care to deal with besides a few exceptions ( IOS Not EVER being one of those) After all thesr years of either referring quickly to this site or the last 2 1/2 pouring countless hours learning random device or specific ...usefull or not (* Few times have i bee let downyet its been an occurance.. worth noting) I belived it was time to throw my hat inthe ring.
So mainly besides wanting to recontribute the resources I have.....mostly my hours of studying and stuff i picked up retentetion being put work and the test and the Love of Working in A Linux Terminal
(*Flavor preference is not important.)
And the Fact that I have a Laptop that can process at about 3.7ghz with 8 threads if you include hyperthreading...along with my growing older and not wanting to Let small contributions like that and Development left saught after by the few.....and honestly which matters in some places I am only scraping by so Financially I have nothing to offer the community along with Tha Mad Love I have for everything XDA ....put that together and you got me doing what I can..Lately it hasnt been to much but wait around and other issues that have eaten away at time leaving me unable to do simple things such as deodex......tho I was looking to do it the hard way and by hand..
My apologizies if the post after mine answered or the second one did but I have yet to read link .....so besides me knowing Wanam got a way around it for most the Install and Stuff
My true and Last Attempt at my first Question
FINGERS CROSSED
LONG
Would there be any necessity in the terms of Modular Functionality either individual or a compilation of your choosing and or combination that would specifically require you to deodex the firmware of any 5.0 or Higher Samsung Based Firmware so that one might have a higher sucess rate or all around better experince?
SHORT
Should i spend my time deodexing this rom for the few who have it in attempts to better the end user experience , spend my time else ?
Id like a little bit of step i the right direction but might just do it and then move to more time , intelectually and pc resource consuming work....
---------- Post added at 01:14 PM ---------- Previous post was at 01:04 PM ----------
vivianajeanty said:
I'm having a severe problem right now... I'm praying this works. I keep getting a "SECURE CHECK FAIL : ABOOT" error with every firmware I try. I have a bricked j3 emerge.
do you have any tips on which file I can put where in odin? I was patient to let this download... and I feel like this is the closest thing I have that will get it working.
Click to expand...
Click to collapse
Umm I know if you downloaded off a disrepputable and FREE source that it might be the CSC partiton. I ll pm you with a copy of my firmware that was Adb Pulled by my old Firmware subcription site and did in Fact come from my device.....or the file was set to reupload for seeding purposes....idk either way we will handle this as a community united.
NOTE
I have since given device up....
Havent given up on it ...
So yeah to modding out a new more flagship type model...
Building ,Porting , Deodexing this J3 ....
And just seeing a lil development o a mid to low end device * price =low specs=mid....ish
Growing as a person in both knowledge and contributionally as well. Thanks 4 time.... **Sorry if I ramble.**
this did get my boost samsung j3 emerge working again but the problem is no matter what i do i can not get it to pass the safety net test :/ the software version is also different from the stock version
this version:j327pvpu1apl1
stock version:J327PVPU0APJ2
am i correct in assuming that this could be my safety net issue? and if so can anyone help point me in the right direction to the stock boost firmware? ill be searching for it regardless but if i can get help before i find it then that'd be super thanks for asking
tac0xenon said:
this did get my boost samsung j3 emerge working again but the problem is no matter what i do i can not get it to pass the safety net test :/ the software version is also different from the stock version
this version:j327pvpu1apl1
stock version:J327PVPU0APJ2
am i correct in assuming that this could be my safety net issue? and if so can anyone help point me in the right direction to the stock boost firmware? ill be searching for it regardless but if i can get help before i find it then that'd be super thanks for asking
Click to expand...
Click to collapse
Are you rooted? Or running a custom kernel? Both of those things and a few others will cause you to fail. Another option would be to select NAND erase in ODIN when you flash. That will completely wipe your device before flashing, but as with any flashing procedures, it could lead to an unusable device.
Greaper88 said:
Are you rooted? Or running a custom kernel? Both of those things and a few others will cause you to fail. Another option would be to select NAND erase in ODIN when you flash. That will completely wipe your device before flashing, but as with any flashing procedures, it could lead to an unusable device.
Click to expand...
Click to collapse
I was rooted with super su but after failing safety net I began searching for a a way around it and i successfully unrooted my phone then re rooted with magisk and passed the safety net test yay! And life was good for a while until I to install xposed framework. I made a super noob mistake and flashed it with a low battery percentage and of course it died in the middle of it. I turned my phone on and no OS... Crap baskets... noob mistake number 2 my nandroid backup I must not have been paying attention and tried to save it to internal storage instead of the SD card which if you own this phone you probably know that it doesn't work that way so double crap baskets.
Fast forward to finding this post I loaded it up everything works as it should but it won't pass safety net rooted or not and no custom kernel
This is not a life or death problem as everything works flawlessly except for the safety net test But my woman likes to go on walks and play Pokémon go together and now I can't and it is slightly annoying that we are no longer able to. It's a cheap way to get outside and have a little fun towards the end of the week as opposed to Netflix and other boring stuff
tac0xenon said:
I was rooted with super su but after failing safety net I began searching for a a way around it and i successfully unrooted my phone then re rooted with magisk and passed the safety net test yay! And life was good for a while until I to install xposed framework. I made a super noob mistake and flashed it with a low battery percentage and of course it died in the middle of it. I turned my phone on and no OS... Crap baskets... noob mistake number 2 my nandroid backup I must not have been paying attention and tried to save it to internal storage instead of the SD card which if you own this phone you probably know that it doesn't work that way so double crap baskets.
Fast forward to finding this post I loaded it up everything works as it should but it won't pass safety net rooted or not and no custom kernel
This is not a life or death problem as everything works flawlessly except for the safety net test But my woman likes to go on walks and play Pokémon go together and now I can't and it is slightly annoying that we are no longer able to. It's a cheap way to get outside and have a little fun towards the end of the week as opposed to Netflix and other boring stuff
Click to expand...
Click to collapse
Hmm. I do know that you need to enable "oem unlock" and power the phone COMPLETELY off. It doesn't hurt to pull the battery for a minute, but shouldn't be necessary. Then power it on into download mode, and leave the auto reset checked in ODIN. It can take a couple of flashes I've read to get everything back to where it should be.
Greaper88 said:
Hmm. I do know that you need to enable "oem unlock" and power the phone COMPLETELY off. It doesn't hurt to pull the battery for a minute, but shouldn't be necessary. Then power it on into download mode, and leave the auto reset checked in ODIN. It can take a couple of flashes I've read to get everything back to where it should be.
Click to expand...
Click to collapse
Thanks for the tips I'll try it when I get home and let you know how it goes much appreciated
Greaper88 said:
Hmm. I do know that you need to enable "oem unlock" and power the phone COMPLETELY off. It doesn't hurt to pull the battery for a minute, but shouldn't be necessary. Then power it on into download mode, and leave the auto reset checked in ODIN. It can take a couple of flashes I've read to get everything back to where it should be.
Click to expand...
Click to collapse
Had to flash three times but your advice worked thank you very much
Frp
Hello I have a question I'm a newbie and I would like to know if when I do install the stock rom does that mean I have to put in the google account information of the person providing the stock rom
Hi to all of you.I got given an old samsung galaxy s4 mini(GT-I9192)and the person who gave it said it was broken if you can fix it you can keep/sell it.I tried opening it but it didnt respond to any keys even when i tried download/recovery/power on.As i researched online it seems to me that the device has been hardbricked.The guy who gave it to me said he had sent it to a store to repair and said that his cpu was not functioning anymore for both of his s4 minis which doesnt seem to happen just for the 2 phones that 1 person buys and because i live in Albania services arents so great.When i tried to install a custom rom from odin(latest to this date)it wouldnt recognise it but when i plugged the phone in windows made tge sound that something was plugged in and then shortly after it made the disconnecting sound whoch gives me a reason to think that the device may still be alive.I came here since this is the most know site for tech stuff.I havent seen any kind of bricking before but i read tgat the soft bricked devices just need a clean install and to wipe cache and dalvik which gives it the look when it was bought.Ive seen that you can pay for jtag or try a usb jig but i dont want to spend any money since i have a better phone (galaxy j5 2017) and i just wanted to see if i could use it to experiment with roms root and stuff on there.
Any help will be appriciated and if i have any mistakes in my languagee im sorry because as i said im from Albania and not USA/UK
NotABeast said:
Hi to all of you.I got given an old samsung galaxy s4 mini(GT-I9192)and the person who gave it said it was broken if you can fix it you can keep/sell it.I tried opening it but it didnt respond to any keys even when i tried download/recovery/power on.As i researched online it seems to me that the device has been hardbricked.The guy who gave it to me said he had sent it to a store to repair and said that his cpu was not functioning anymore for both of his s4 minis which doesnt seem to happen just for the 2 phones that 1 person buys and because i live in Albania services arents so great.When i tried to install a custom rom from odin(latest to this date)it wouldnt recognise it but when i plugged the phone in windows made tge sound that something was plugged in and then shortly after it made the disconnecting sound whoch gives me a reason to think that the device may still be alive.I came here since this is the most know site for tech stuff.I havent seen any kind of bricking before but i read tgat the soft bricked devices just need a clean install and to wipe cache and dalvik which gives it the look when it was bought.Ive seen that you can pay for jtag or try a usb jig but i dont want to spend any money since i have a better phone (galaxy j5 2017) and i just wanted to see if i could use it to experiment with roms root and stuff on there.
Any help will be appriciated and if i have any mistakes in my languagee im sorry because as i said im from Albania and not USA/UK
Click to expand...
Click to collapse
Download and install the full set of USB drivers for Samsung phones. This might be part of your connection/disconnection issue.
https://developer.samsung.com/galaxy/others/android-usb-driver-for-windows
On your Windows system, go to Control Panel>Device Manager, then connect your device, when you connect it, watch the Device Manager window, if your device connects, it should have something appear on your list of devices. Try to see what the list shows when the device connects, even if it still just a momentary connection, then come back here and post what it says. This will give me a better idea of what is going on with the device.
If what your friend told you about the CPU's being bad is true, you won't be able to fix the device(s) unless you replace the motherboard(s).
Some Samsung devices with locked bootloaders also have a hardware component called a Q-fuse, if someone attempts to flash a custom recovery or anything else custom on the device, it trips Q-fuse which then "burns" the fuse, rendering the device inoperably hardbricked. This is probably what was attempted on the devices you have. If this is what happened, you won't be able to fix it, not even Samsung themselves can fix this, all they can do is salvage the device to reclaim any possible usable hardware components.
Sent from my LGL84VL using Tapatalk
Thanks for the reply.First things to start,my friend doesnt mess up with loading custom roms as he doesnt have much knowledge on technology.Next,when i connected the device the first time it showed me the name QSHUSB_DLOAD(or smth like that because i am not avaible to use the computer right now).I tried installing some drivers and i will edit the name that i got when i use the computer in a matter of a hour or two.
NotABeast said:
Thanks for the reply.First things to start,my friend doesnt mess up with loading custom roms as he doesnt have much knowledge on technology.Next,when i connected the device the first time it showed me the name QSHUSB_DLOAD(or smth like that because i am not avaible to use the computer right now).I tried installing some drivers and i will edit the name that i got when i use the computer in a matter of a hour or two.
Click to expand...
Click to collapse
Everything you're describing is exactly the results one gets when someone tries to flash something custom via Odin, or when trying to update the device via Odin but the wrong firmware is flashed.
Generally, the only to fix this is to send the device to a professional shop to have a JTAG service performed on the device(s) or replace the motherboard.
From what you describe, I believe the devices are permanently hardbricked, the only solution then is to replace the motherboard. Other than that, you're wasting your time.
Sent from my LGL84VL using Tapatalk
Well feom what i know he doesnt know anything about odin or flashing a new rom since he doesnt even know what a rom is.Then again he hasnt done a factory reset since he doesnt know how.And he has even said that hasnt done anything else than getting it out of the box putting a sim card and just using it.If there is anything we can try to bring it to life by trying to flash a new custom rom or the original rom from an sd card or a usb flash drive(since i have the converter from charging port to usb).Anyways i was just trying to see if i could bring it to life and idk maybe give it to someone else or sell it.
Thanks for your help for the tips you have given me amd for the help that you may give in advance
NotABeast said:
Well feom what i know he doesnt know anything about odin or flashing a new rom since he doesnt even know what a rom is.Then again he hasnt done a factory reset since he doesnt know how.And he has even said that hasnt done anything else than getting it out of the box putting a sim card and just using it.If there is anything we can try to bring it to life by trying to flash a new custom rom or the original rom from an sd card or a usb flash drive(since i have the converter from charging port to usb).Anyways i was just trying to see if i could bring it to life and idk maybe give it to someone else or sell it.
Thanks for your help for the tips you have given me amd for the help that you may give in advance
Click to expand...
Click to collapse
If you can find a "debrick.img" or "unbrick.img",(sometimes, these files are debrick.bin or unbrick.bin), there is a method that involves burning the .img or .bin file on an sdcard to create a type of "bootable disk" to restore the device. The only way to get a copy of this file is from a rooted device with the same model number as yours, try to find one that someone has already creates and made available or try finding someone in this forum that has a device like yours with the same model number and then have them pull a copy of debrick.img from their device and upload it for you to download and use for your device.
Here is a thread for doing this on a galaxy S3, if you can find the specific debrick file for your exact model number, you can try this method. Use the method and the tools as described in the thread, you just need to make sure that any device specific files used in the method are those files for your specific model number.
https://forum.xda-developers.com/showthread.php?t=2581166
Sent from my LGL84VL using Tapatalk
Ok so first,if i do it on a usb will it work and will it be able to be used again as normal and the same for the sd card,will it be able to be used again?
Edit:I forgot but is there a limit to the usb or sdcard size that i will use?And is it possible if i get another samsung phone os or the debrick.img?
NotABeast said:
Ok so first,if i do it on a usb will it work and will it be able to be used again as normal and the same for the sd card,will it be able to be used again?
Edit:I forgot but is there a limit to the usb or sdcard size that i will use?And is it possible if i get another samsung phone os or the debrick.img?
Click to expand...
Click to collapse
Use an sdcard, the thread that I linked has instructions for returning the sdcard to normal usage after you're done getting the device restored. No, you can not use a debrick.img or any other file from a device with a different model number, it has to be for YOUR SPECIFIC MODEL NUMBER I have told you that in every one of my replies here, that is a MUST, it is not "optional".
Stop looking for shortcuts, I know it isn't easy to find what you need but there are no substitutes, do it the right way or don't do it at all.
Sent from my LGL84VL using Tapatalk