Related
Hello. New here. Moderate tech.
I have had success in modding phones in the past and first and finally was successful in Hard bricking my SCH-I535 (S3) roughly 6 months ago or so. I don't really recall what mod I had on it before I hard bricked it or what directions I followed but I think the mod may have been a liquidmod or something. Anyways, I gave up after a month or so of troubleshooting off and on after the brick. Until today, I came across a useful new (2014) updated youtube video that debricked my hard-bricked S3.!
However, I think it's still soft-bricked and won't load past the, "System software not authorized by Verizon Wireless...." message.
Happened to try the 'ol Vol down + Home button combo and took me into the "downloading..." - Odin Mode, I believe.
Nothing more and nothing after that.
Unsure as to what steps I should take. I would just like to get stock back on it ....Or maybe it's closer to a rom (ROM ideas).
Perhaps, I can switch my number back on the this S3 from the MyVerizon site, walk it in Verizon and tell them, No I don't know what happened..it said it was updating - - And then have it replaced under warranty instead?. Lol
Thanks!
Please review [GUIDE] Debrick your bricked SCH-I535! [BOOTLOADER/HARDBRICK]
If you still have questions, please post on that thread.
Very very helpful thank you so much!
I recently tried to root my D850 with 5.0.1 Of course, I botched it and it got stuck at the boot screen. I figured a factory reset (hard reset) might save the day, but it didn't. The device was not recognized by the PC and the MTP driver would not work no matter what I did. In desperation, I chatted with an LG USA rep. He said to submit a repair request, which I did. There was no mention of cost but at this point, I don't care if it does cost to fix it. They emailed me a FedEx label and I sent it off yesterday. There was another thread in which the OP sent his in to LG with pretty much the same thing happened and his device was repaired free, so I'm hoping for a free fix. Point is: I got this device from a seller on eBay and I was upfront with LG about that. Warranty or not, they seem willing to fix it for me. So, instead of beating your head against the wall trying to fix it, you might want to consider sending it to LG if you get it fixed yourself.
gjtoth said:
I recently tried to root my D850 with 5.0.1 Of course, I botched it and it got stuck at the boot screen. I figured a factory reset (hard reset) might save the day, but it didn't. The device was not recognized by the PC and the MTP driver would not work no matter what I did. In desperation, I chatted with an LG USA rep. He said to submit a repair request, which I did. There was no mention of cost but at this point, I don't care if it does cost to fix it. They emailed me a FedEx label and I sent it off yesterday. There was another thread in which the OP sent his in to LG with pretty much the same thing happened and his device was repaired free, so I'm hoping for a free fix. Point is: I got this device from a seller on eBay and I was upfront with LG about that. Warranty or not, they seem willing to fix it for me. So, instead of beating your head against the wall trying to fix it, you might want to consider sending it to LG if you get it fixed yourself.
Click to expand...
Click to collapse
Or you can just follow my guide which 1,000s have used to fix there phone It takes under 10min after you download everything.
http://forum.xda-developers.com/showthread.php?t=2785089
If its stuck at LG boot screen just put it into download mode and follow the guide... They will most likely charge you as they will see ROOTED in red when they go into download mode.
hyelton said:
Or you can just follow my guide which 1,000s have used to fix there phone It takes under 10min after you download everything.
http://forum.xda-developers.com/showthread.php?t=2785089
If its stuck at LG boot screen just put it into download mode and follow the guide... They will most likely charge you as they will see ROOTED in red when they go into download mode.
Click to expand...
Click to collapse
Which would PROBABLY work. But as I stated in another thread (to which I got no response), the PC is not recognizing it. And, as I stated, I don't care if they charge me or not. I just want it FIXED.
gjtoth said:
Which would PROBABLY work. But as I stated in another thread (to which I got no response), the PC is not recognizing it. And, as I stated, I don't care if they charge me or not. I just want it FIXED.
Click to expand...
Click to collapse
Then try another PC.
Sending to the company is a last resort type thing. Some cases people have been charged more than you can get a used one for at times.
The method in that thread is the exact way LG will be fixing your phone. (Unless they just replace your motherboard)
hyelton said:
Then try another PC.
Sending to the company is a last resort type thing. Some cases people have been charged more than you can get a used one for at times.
The method in that thread is the exact way LG will be fixing your phone. (Unless they just replace your motherboard)
Click to expand...
Click to collapse
If that's the exact way and it works for them, GOOD! Because I tried it and several other methods and it DID NOT WORK. As the person the said in another thread, they fixed it FREE. And, if they charge me, so what? I'll have my device working properly. I don't know where you'd get one of these for under $100, but if they fail to restore it, please DO tell me as I'd sure like to know. In fact, tell me now so I can grab one for my wife.
gjtoth said:
If that's the exact way and it works for them, GOOD! Because I tried it and several other methods and it DID NOT WORK. As the person the said in another thread, they fixed it FREE. And, if they charge me, so what? I'll have my device working properly. I don't know where you'd get one of these for under $100, but if they fail to restore it, please DO tell me as I'd sure like to know. In fact, tell me now so I can grab one for my wife.
Click to expand...
Click to collapse
They normally at least charge $200 + for a phone repair. . I've dealt with LG and LG phones for a good while now.
And not sure if you have ever posted in my guide asking for help.
Different methods? There's ONLY ONE method that works for the D850 which is the TOT method.
After downloading and installing the drivers , software and zipped tot, did you make sure phone was IN download mode? Did you make sure you changed your COM port to COM41?
You have to be sure your following everything step by step.
The guide is very simple. I can pretty much gurentee that if you lived nearby I'd have that phone fixed in under 20min.
I'm just stating myself and my guide has fixed 1,000s of LG phones.
hyelton said:
They normally at least charge $200 + for a phone repair. . I've dealt with LG and LG phones for a good while now.
And not sure if you have ever posted in my guide asking for help.
Different methods? There's ONLY ONE method that works for the D850 which is the TOT method.
After downloading and installing the drivers , software and zipped tot, did you make sure phone was IN download mode? Did you make sure you changed your COM port to COM41?
You have to be sure your following everything step by step.
The guide is very simple. I can pretty much gurentee that if you lived nearby I'd have that phone fixed in under 20min.
I'm just stating myself and my guide has fixed 1,000s of LG phones.
Click to expand...
Click to collapse
Maybe so, but it didn't fix mine. See, when the PC does not see it, nothing is going to download, upload, flash. It's a moot point anyways, as it's on it's way to LG, Ft. Worth.
gjtoth said:
Maybe so, but it didn't fix mine. See, when the PC does not see it, nothing is going to download, upload, flash. It's a moot point anyways, as it's on it's way to LG, Ft. Worth.
Click to expand...
Click to collapse
Wishing you the best of luck, Provide and update as to what happens.
SO the phone was in download mode when you tried? You`d look for LGEmodem under ports in device manager.
UPDATE
So, I sent my G3 into LG_Ft. Worth approximately a week-and-a-half ago for the symptoms sited at the beginning of the thread. Bear in mind, I got this phone from eBay and I told them that. I also told them that after I tried to do a Factory Reset, it locked at the LG boot screen. That's ALL I told them. No questions asked: They sent me a replacement unit. F R E E!
The invoice stated "Bad ROM flash. Replacement sent." I'm restoring from back-up now.
Same issue as OP
I have one G3 soft bricked. At first, i was be able to connect to dl mode. I tried LG Mobile Support tool to flash the phone back to stock , at the end, it failed. Now the phone not let me enter dl or recovery mode. PC not detect the phone at all. I'm using original Nokia USB cable. Tried with 3 computers, none of them detect when plugin and hold Vol up or down etc...
I want to follow TOT method but what can i do if computer not detect the phone?
abcchoier said:
I have one G3 soft bricked. At first, i was be able to connect to dl mode. I tried LG Mobile Support tool to flash the phone back to stock , at the end, it failed. Now the phone not let me enter dl or recovery mode. PC not detect the phone at all. I'm using original Nokia USB cable. Tried with 3 computers, none of them detect when plugin and hold Vol up or down etc...
I want to follow TOT method but what can i do if computer not detect the phone?
Click to expand...
Click to collapse
I'm sure there will be others that will have you try different things, but FOR ME, I went to the LG website and chatted with a tech. He told me to send it in. Even provided a shipping label. See the original post for what took place. They shipped me a replacement phone... F R E E. Took about two weeks.
gjtoth said:
I'm sure there will be others that will have you try different things, but FOR ME, I went to the LG website and chatted with a tech. He told me to send it in. Even provided a shipping label. See the original post for what took place. They shipped me a replacement phone... F R E E. Took about two weeks.
Click to expand...
Click to collapse
Yeah but using my back to stock guide can take about an hour depending on your connection. If connection is good then maybe 20 min.
And not all cases will be the same. There's some cases of people getting charged even just to get there phone back.
Sent from my iPhone using Tapatalk
hyelton said:
Or you can just follow my guide which 1,000s have used to fix there phone It takes under 10min after you download everything.
http://forum.xda-developers.com/showthread.php?t=2785089
If its stuck at LG boot screen just put it into download mode and follow the guide... They will most likely charge you as they will see ROOTED in red when they go into download mode.
Click to expand...
Click to collapse
Sorry to bust in on this thread. You seem like a very knowledgeable person, so i would like to know if you have a guide for rooting the AT&T varient, with a Mac? Thanks for any help.
grunt0300 said:
Sorry to bust in on this thread. You seem like a very knowledgeable person, so i would like to know if you have a guide for rooting the AT&T varient, with a Mac? Thanks for any help.
Click to expand...
Click to collapse
Sorry for the delay in case you didn't find out no, the method uses official lg firmwares. Which requires windows. So no way to do it on a Mac unless you use a virtual machine which is very buggy to do this with.
Sent from my iPhone using Tapatalk
On the topic of bricking (and unbricking !!) the D850, I just received a D850 from ebay today. I tried hyelton's procedure
to restore a stock ROM (LGD850AT-01-V10d-310-410-JUN-19-2014+0.tot) and it failed during the download.
My D850 entered a horrible bricked state, booting with a "secure booting error" message, and then alternating with red and blue LEDs. It was impossible to enter download mode. Trying to use the default recovery to do a factory reset failed. Basically it seemed like the device was bricked.
I was a little panicky because I just received the phone earlier in the day.
I then found this amazing thread on the Sprint LG G3 forum, which describes a sort of hard reset you can do inside the phone. (kind of like an alternative download mode to transfer files to the device). This requires you to short two connections in the phone with a ~2cm piece of copper wire, so you obviously need to be comfortable disassembling your phone.
http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
I am happy to report that this procedure worked perfectly to return my ATT D850 back to life, notably giving me download mode back, which I used following Hyelton's procedure to download a stock ROM back into the phone, which now worked fine.
I hope others can benefit from this.
=mxasf
So, my wife decided to buy this phone, and I am to stay away from her phones. She smashed the screen one day, and that was a door open for me. I hastily get some version of TWRP to boot on it and grab a backup, and also do an adb backup (which was crap). Then, I did a full wipe before taking it in to get repaired.
SO, what I want to walk through here boys and girls, is never, never, never, never, put Smartisan OS 2.5.3 on this phone. When my wife got her phone back I harmlessly believed that updating would not disallow me from TWRP again to recover. What this version does to the device is completely disable recovery altogether. You are always pushed to fastboot, and fastboot cannot flash anything After this realization, I borked the phone, I dd'ed out the aboot and the sbl. She had insurance, we live in China it is cheap, and after the difficulties I realized this was happening to lots of people. I figured the local service center could re-write the partitions I had pooped on and they would re-write it with an earlier firmware. My gamble paid off.
Got the phone back with 2.5.0. I immediately followed the guide here http://tinyurl.com/z7ekyxp , Russian site, to revert back. I then, deviating from the guide to be careful, fastboot boot "twrp.img". I used commands the whole way, no flashify or anything (I love flashify on my nexus 5 but I had already borked this phone once. It booted TWRP, I copied all the old SD files over to the phone. Then, the moment of truth, would a restore from my previous backup work. Yes, it did. I even followed the guide through and flashed the 2.3.5 modified update. It worked, the SuperSU and open gapps flashed without issue also.
Not a horrible phone for being extremely cheap, but they messed up an update. For those fooling around with the device, remember the partition table has a bak for all boot related things. I also see on Chinese forums that they use the headphone jack for diagnostics (My Chinese isn't great, but I looked around when I bricked my wife's phone).
One thing of note with this device is there are three versions that appear in build.prop 32, 32_younger, 306_younger, I think, but Smartisan has confirmed they are all the same, just different production batches. If you get errors in the update process, modify this to match.
Don't drink and post children, I was editing to say I ran with what smartlinux on that site said, nothing here is my idea except for running the commands yourself.
Another good dev on the device but Chinese http://blog.cofface.com/archives/1139.html. He has an app that will boot into either (stock or custom) recovery, but like I said, do not take that 2.3.5 thing. I see they have 2.5, so let's see what happens.
wangdaning said:
Another good dev on the device but Chinese http://blog.cofface.com/archives/1139.html. He has an app that will boot into either (stock or custom) recovery, but like I said, do not take that 2.3.5 thing. I see they have 2.5, so let's see what happens.
Click to expand...
Click to collapse
Hey bro, you're a native American working in Chengdu?
xcjchandler said:
Hey bro, you're a native American working in Chengdu?
Click to expand...
Click to collapse
Yep.
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!
I flashed the Google assistant some time ago and everything was fine but yesterday I decided to do some minor build prop edits and accidentally bricked my phone. Now that's fine because they have multiple ways of unbricking the T-Mobile LG v20. But when I tried to unbricking it using LGup nothing works because it registers my phone as a pixel and now my phone can't be restored. So take it from me..Don't do it!!! It isn't worth the loss. I have a brick now. An official lg v20 brick. Sigh
EDIT:
IM EDITING THIS TO ADD WHAT I DID.
Here's the story
I was trying to revert to stock with the build prop so I could upgrade my phone. so I edited the prob and removed the lines I added to get Google assistant in the first place but it crashed and when I entered TWRP to push the build prop. When that didn't work I flashed the stock tot file which got my phone working but I wanted to upgrade so I found the page in XDA to flash the kdz with LGup which I was doing but half way through it failed and Twrp was gone which started this snow ball effect.
Do you not have TWRP you can reboot into, and re-flash a backup or new ROM?
CharlzO_2000 said:
Do you not have TWRP you can reboot into, and re-flash a backup or new ROM?
Click to expand...
Click to collapse
Nope, the only thing my phone does it boot into the mode where it says "Firmware update" mode. I really think I destroyed my phone.
remix435 said:
Nope, the only thing my phone does it boot into the mode where it says "Firmware update" mode. I really think I destroyed my phone.
Click to expand...
Click to collapse
Take it to the store and tell them it happend when the phone was updating.
slayerh4x said:
Take it to the store and tell them it happend when the phone was updating.
Click to expand...
Click to collapse
That's actually a pretty good idea. I'm going as soon as TMobile opens.
I had the same problem. ADB didn't recognize my device to run command to reboot recovery. I found that ADB did pick it up while doing a factory reset. Even tho it was the original LG factory reset screen it would use TWRP to perform the reset but would automatically reboot after. So I had a command window opened with adb reboot-recovery typed then I rebooted into the original factory reset and selected yes twice. As soon as TWRP screen came up and I heard the windows chime recognizing the device I hit enter in command window to reboot recovery and it rebooted into TWRP normally where I was able to restore from backup. If you time it right you can get back to TWRP. Hope this helps
Leonarddale said:
I had the same problem. ADB didn't recognize my device to run command to reboot recovery. I found that ADB did pick it up while doing a factory reset. Even tho it was the original LG factory reset screen it would use TWRP to perform the reset but would automatically reboot after. So I had a command window opened with adb reboot-recovery typed then I rebooted into the original factory reset and selected yes twice. As soon as TWRP screen came up and I heard the windows chime recognizing the device I hit enter in command window to reboot recovery and it rebooted into TWRP normally where I was able to restore from backup. If you time it right you can get back to TWRP. Hope this helps
Click to expand...
Click to collapse
This.
remix435 said:
I flashed the Google assistant some time ago and everything was fine but yesterday I decided to do some minor build prop edits and accidentally bricked my phone. Now that's fine because they have multiple ways of unbricking the T-Mobile LG v20. But when I tried to unbricking it using LGup nothing works because it registers my phone as a pixel and now my phone can't be restored. So take it from me..Don't do it!!! It isn't worth the loss. I have a brick now. An official lg v20 brick. Sigh*
Click to expand...
Click to collapse
That is very strange, I recently bricked my phone to the point where I didn't have a system at all on it. When you boot to firmware update mode (power + volume up) and pluged it in LGUp recognized it instantly. You have the correct DLL for your device right?
shadowxaero said:
That is very strange, I recently bricked my phone to the point where I didn't have a system at all on it. When you boot to firmware update mode (power + volume up) and pluged it in LGUp recognized it instantly. You have the correct DLL for your device right?
Click to expand...
Click to collapse
My issue was that when I flashed the assistant mod it turned my device name into " google pixel" so when I hooked it up to lgup it read it as a pixel and failed the restore every time. That was the issue I couldnt change the name of my devixe back to the v20.
Leonarddale said:
I had the same problem. ADB didn't recognize my device to run command to reboot recovery. I found that ADB did pick it up while doing a factory reset. Even tho it was the original LG factory reset screen it would use TWRP to perform the reset but would automatically reboot after. So I had a command window opened with adb reboot-recovery typed then I rebooted into the original factory reset and selected yes twice. As soon as TWRP screen came up and I heard the windows chime recognizing the device I hit enter in command window to reboot recovery and it rebooted into TWRP normally where I was able to restore from backup. If you time it right you can get back to TWRP. Hope this helps
Click to expand...
Click to collapse
I disnt have anything on my phone. No twrp and I couldnt install it. The assistant mod changed my device name to PIXEL and when id connect it to the pc it read as a pixel and failed every update I LG V20 I pushed to it..that was a new type of brick lol. But I told t mobile that if I what happened and I got another one.
These old assistant mods would be taken down. The only thing needed to enable it without spoofing a phone as a Pixel is adding "ro.opa.eligible_device=true" to build.prop, and the Google app updated via Play Store.
remix435 said:
My issue was that when I flashed the assistant mod it turned my device name into " google pixel" so when I hooked it up to lgup it read it as a pixel and failed the restore every time. That was the issue I couldnt change the name of my devixe back to the v20.
Click to expand...
Click to collapse
That's the thing my phone didn't have a system on it at all and LGUp read it as what it was. When you on the firmware screen it should read based on hardware ID right? Have you tried using LG bridge? Are you on the T-Mobile variant?
This is a contributing factor in why these companies lock bootloaders. People do stupid things because they don't know what they're doing and then others encourage them to just return it and get a new one and lie. Not cool at all. How about don't root your phone if you don't know what you're doing.
markbencze said:
This is a contributing factor in why these companies lock bootloaders. People do stupid things because they don't know what they're doing and then others encourage them to just return it and get a new one and lie. Not cool at all. How about don't root your phone if you don't know what you're doing.
Click to expand...
Click to collapse
WTF! With your logic no one would learn anything.
My phone was rooted just fine. How was I suppose to know that after I flashed the stock build prop my phone was going to stay as a pixel device?? That wasn't stupid of me that was trial and error. Something stupid is if I did it again. No one specified that my phone would stay as a pixel device, go read the instructions and tell me where it says that. Also, I have "Jump on demand" so I used one of my jumps to get a brand new phone..So I paid a price for it. It wasn't just "me lying and getting a free phone" I still paid for it I paid for my mistake and Yes initially I lied but still paid and am still paying for this phone. Plus I have an s7 edge and a Huawei honor note 8 all rooted and have never ran into any issues. Why?? Because I never did what people instructions told me not to do. I always follow instructions. I've been rooting phones since I was a milk drinker all the way back to the G1 days. I'm very careful but if instructions don't cover all the basis then what?? PEOPLE, including me should continue to root and try new things. But you can't blame them if YOU(not you in particular but in general) as a developer make something and can't catch all the bugs(it isn't The developers/modders fault either)..Modding is a giant community of trial and error. The only people at fault are idiots who don't read and do some ****. Other than that we are all out here finding our way with these new devices. So yes, I have a new v20 that I paid for with MY "Jump on demand" plan that is now rooted and unlocked. Now am I going to use the Google assistant mod again?? No, because that would be stupid of me. Now get off my post.
I was just warning people so they wouldn't make the same mistake as me.
Whats the stupid part is how you managed to erase TWRP and lose access to fastboot on your device. Not that your changed something in build.prop. His logic is not flawed, whatever you did to lose access to the two essential parts of having a rooted phone is the flaw here.
Also simply doing build.prop edits should not make you lose access to TWRP nor being able to access fastboot - or did you relock your bootloader?
twistedvip said:
Whats the stupid part is how you managed to erase TWRP and lose access to fastboot on your device. Not that your changed something in build.prop. His logic is not flawed, whatever you did to lose access to the two essential parts of having a rooted phone is the flaw here.
Also simply doing build.prop edits should not make you lose access to TWRP nor being able to access fastboot - or did you relock your bootloader?
Click to expand...
Click to collapse
In stead of assuming what happened with my device how about y'all ask me the details first. But coming off the bat assuming that I just did foolishness is asinine.
I was trying to revert to stock with the build prop so I could upgrade my phone. so I edited the prob and removed the lines I added to get Google assistant in the first place but it crashed and when I entered TWRP to push the build prop. When that didn't work I flashed the stock tot file which got my phone working but I wanted to upgrade so I found the page in XDA to flash the kdz with LGup which I was doing but half way through it failed and Twrp was gone which started this snow ball effect.
So once again where's the stupidity on my part when I didn't know that my phone was still going to be labeled a a pixel after a factory reset? Please, both of you have several seats in the back.
All I'm doing is warning people about what could possibly happen. Y'all can miss me with your unnecessary opinions and comments.
No I appreciate you wanting to warn the community, but you most certainly did not post that story. You posted saying you got bricked from doing edits to your build.prop and then because of using a Google assitant mod you are hard bricked. Post that entire story as a warning because even having your phone appear as a Pixel won't do any harm - but flashing a .kdz and having it fail midway may indeed cause harm. Lack of details causes much misinformation to spread around quickly
twistedvip said:
No I appreciate you wanting to warn the community, but you most certainly did not post that story. You posted saying you got bricked from doing edits to your build.prop and then because of using a Google assitant mod you are hard bricked. Post that entire story as a warning because even having your phone appear as a Pixel won't do any harm - but flashing a .kdz and having it fail midway may indeed cause harm. Lack of details causes much misinformation to spread around quickly
Click to expand...
Click to collapse
My bad I'll edit it. And apologies for the response tone.
It's called taking responsibility. You had a phone with root and did something stupid. Instead of taking responsibility you lie and tell them the phone is defective. That is 100% your fault. I bet it worked fine before you started messing with it. Whatever man I'm gonna let this be but you can bet that when these companies look at the supposed drfrctive returned phones and see they have been tamperred with and that people are being dishonest to get a new phone when they're the sole reason the phone stopped working, eventually they will all say screw it and just lock everything down.
Hopefully you learned from this.
markbencze said:
It's called taking responsibility. You had a phone with root and did something stupid. Instead of taking responsibility you lie and tell them the phone is defective. That is 100% your fault. I bet it worked fine before you started messing with it. Whatever man I'm gonna let this be but you can bet that when these companies look at the supposed drfrctive returned phones and see they have been tamperred with and that people are being dishonest to get a new phone when they're the sole reason the phone stopped working, eventually they will all say screw it and just lock everything down.
Hopefully you learned from this.
Click to expand...
Click to collapse
Actually the phone had a few random rebootsa and use to freeze on stock. I decided to keep it because of the note 7 fiasco and I was too frustrated and pissed to return it and then they ran out. So this was well over due. But once again you know nothing Jon snow. And yes I did lie but this device already had issues. Soooo???