Related
So I was on atomic fusion and tried to flash another gb rom. Somewhere during the odin process it seemed to be stuck and I stopped it and tried again to get a red screen of death. I tried everything to get to d/l mode but nothing. So I called att and I have about a week left in my warranty so I went that route. Am I gonna be charged 400 dollars when they find out I was rooted with roms not theirs? I'm really nervous, I should have never flashed to gb, its to freeking complicated for me to understand all the bootloading and kernal stuff. Any thoughts or experiences to help ease the pain? Thanks
Prolly shouldn't have flashed if you weren't confident. In yourself.
Sent from my SGH-I897 using XDA Premium App
If your phone shows any signs of life they will most likely be able to tell that you are not stock.
Your fine, I did the same thing as you are doing. I just acted like a clueless idiot and they never suspected a thing, but it was with Rogers not AT&T.
Sent from my Galaxy S Firefly 3.0
For all the topics asking this question I'm yet to see anyone come back saying that they have been refused, or charged extra after a new one is already sent out. In all likely hood they don't even check because they don't really care. If it is a hardware issues they are gonna have to swap pieces or even the main/motherboard which will come with stock pre-loaded at factory. If it is software they will just use what ever method they designed into the phone to force rewrite over what was in there before.
Now if you were taking it to a service center, where they are going to take a look in hopes of getting that very phone back into a working condition then maybe... just maybe. But if the phone does not boot then they are just gonna add it to the rewrite pile and give you a referb (or new if you ask nicely enough). This is why they always say "you might lose all your data so make a backup before hand."
Thanks, that makes me feel better, now all I have to do is survive a couple days without it. I won't be making that mistake again. What did I do wrong? I had no problem going from phoenix ultimate to atomic fusion. I was gonna try to go to cog5, I thought I was doing it right. All I did was use the odin that it said to use and it seemed to be stuck. What do you do when it freezes up during the odin process? Are you screwed no matter what you do? Should I have used the odin that takes you to stock 2.1 first? I'm really trying to understand all this but there's just so many ways about everything.
My samsung captivate had never given me any problems(in the very short but good few months I've had it) until I tried to downgrade from Gingerbread(2.3.5) to Froyo about 4 days back.
While using Odin 1 click (and the phone was rooted) to accomplish what I just said, the process seemingly carried out perfectly, the "passed" message appeared in Odin and it looked like it was a success, but instead of rebooting as usual after flashing, my Cappy just went completely blank, and has stayed like that ever since. :crying:
I have tried every button combo there is, and since Jigs are for soft bricks, I guess there's no use.
The only remedy that I haven't gone for yet, is Jtag.
Can someone, anyone, PLEASE help me here!?
Hoping someone gets it working here..
Yep. If zero signs of life...even when wall charging, then sounds like hard brick.
Which Odin did u use to downgrade ??
Just curious...
Sent from my SAMSUNG-SGH-I777 using xda premium
4-2ndtwin said:
Yep. If zero signs of life...even when wall charging, then sounds like hard brick.
Which Odin did u use to downgrade ??
Just curious...
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
Well I've used Odin 3 v 1.8.5 and even Odin3 v1.7 many, many times and it's all run perfectly, but this one was Odin 3 One Click v 1.00
I've never bricked a phone ever, and yeah this one's a badass hard brick for sure.
ANY help would be really appreciated, all!
Can you provide a link to the thread you dl'd from?
mrhaley30705 said:
Can you provide a link to the thread you dl'd from?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=731989
As you can see, it's from here. That's the Odin I used, but I don't think there was anything wrong with the file(at least I hope not)
It completed the process, gave the "passed" message, and then the phone went blank, like immediately.
Any thoughts on how that may have happened? 'Cause I thought it may have been bricked due to Odin crashing, but it did go through till the end, seemingly successful.
Anup7 said:
http://forum.xda-developers.com/showthread.php?t=731989
As you can see, it's from here. That's the Odin I used, but I don't think there was anything wrong with the file(at least I hope not)
It completed the process, gave the "passed" message, and then the phone went blank, like immediately.
Any thoughts on how that may have happened? 'Cause I thought it may have been bricked due to Odin crashing, but it did go through till the end, seemingly successful.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=841512
^ ^ This jig, is it for a hard bricked captivate or a soft bricked one? 'Coz although I'm definitely not confident with tearing up a micro USB cable, I'm going to give it a shot tomorrow. Heading to Radioshack first thing in the morning. Last shot God dammit :/
^
Jig won't do anything for a "Hard" Brick...only J-tag and/or Unbrickable Mod.
Sent from my SAMSUNG-SGH-I777 using xda premium
Anup7 said:
http://forum.xda-developers.com/showthread.php?t=731989
As you can see, it's from here. That's the Odin I used, but I don't think there was anything wrong with the file(at least I hope not)
It completed the process, gave the "passed" message, and then the phone went blank, like immediately.
Any thoughts on how that may have happened? 'Cause I thought it may have been bricked due to Odin crashing, but it did go through till the end, seemingly successful.
Click to expand...
Click to collapse
Something had to go wrong when the jf6 bootloaders were flashed, obviously. If u did not close that Odin yet (unlikely, i know) u could scroll through the log and see what it says about the boot.bin and sbl.bin.
Sent from my SAMSUNG-SGH-I777 using xda premium
Well Odin was closed, as expected. So that's not an option obviously.
Is Jtag doable by users, like could I get instructions on how to go about it? Or would I have to send it in?
And any other ideas?
Regardless, i recommend mobiletechvideos.com for the fix.
Respected and reliable !!
Sent from my SAMSUNG-SGH-I777 using xda premium
How long have you had the phone?? Only three months?
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Anup7 said:
Well Odin was closed, as expected. So that's not an option obviously.
Is Jtag doable by users, like could I get instructions on how to go about it? Or would I have to send it in?
And any other ideas?
Click to expand...
Click to collapse
Here are some threads from the dev forum...
Developing methods to recover bricks without JTAG
The Captivate Development Platform mod AKA UnBrickable Mod
[HOW-TO]UnBrick the UnBrickable Captivate
....or like I said before, check out mobiletechvideos.com
Anup7 said:
Well Odin was closed, as expected. So that's not an option obviously.
Is Jtag doable by users, like could I get instructions on how to go about it? Or would I have to send it in?
And any other ideas?
Click to expand...
Click to collapse
Dude if nothing works and you have had the phone for less than 1 year call at&t tell him you had your phone plugged into your computer over night charging, you woke up and the phone won't turn on now. And yiur house lost power and regained and there must have been a power surge around your area. You don't know what happened but it won't respond to anything....also do you know if your tripped the flash counter at all? Or did you reset it? P.m. me if any help needed I just went through this with my note....if all else fails p.m. me I have another fix but it isn't free but its cheaper than buying a new phone outright...
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
No flash counter with the Captivate.
4-2ndtwin said:
No flash counter with the Captivate.
Click to expand...
Click to collapse
Well I thought of that too, but then there's a problem. I actually bought this phone from a friend, a couple months ago, since I wasn't sure how good of a model this was and I didn't want to go get myself a new Cappy just to be let down and want another one, you know?
Still, spent 160$ on it.
Anyway, he doesn't have the receipt, there's no way I can get att to replace it like you suggested.
And just a side note, the phone was in mint condition, never even been rooted before it got to me, lol!
Btw nope, no flash counter.
Huh? Att will not ask for a receipt when doing a warranty exchange...I've never had an issue with people not having receipts for a manufacturer defect....you will be fine as long as the phone was purchase less than a year ago
This Public Service Announcement brought to you by a pimped out At&t gNote rocking *The Collectives* AOCP CP1...
Kflan22 said:
Huh? Att will not ask for a receipt when doing a warranty exchange...I've never had an issue with people not having receipts for a manufacturer defect....you will be fine as long as the phone was purchase less than a year ago
This Public Service Announcement brought to you by a pimped out At&t gNote rocking *The Collectives* AOCP CP1...
Click to expand...
Click to collapse
I thought they'd need it as proof, but thanks!
I'll head over to ATT in a couple hours and see what they say.
I'll let you know.
FYI - the return may have a hiccup in it. Since you bought it from a friend and not from AT&T (or an authorized reseller), they don't have any proof of how long you've had it. There's no way for them to know whether you got it yesterday or 2 years ago, so they may put up a fight about honoring the warranty.
This is just speculation, but I just wanted to throw it out there that it may not go as smoothly as we would all like it to go for you.
jmtheiss said:
FYI - the return may have a hiccup in it. Since you bought it from a friend and not from AT&T (or an authorized reseller), they don't have any proof of how long you've had it. There's no way for them to know whether you got it yesterday or 2 years ago, so they may put up a fight about honoring the warranty.
This is just speculation, but I just wanted to throw it out there that it may not go as smoothly as we would all like it to go for you.
Click to expand...
Click to collapse
Thanks for the heads up though!
Any suggestions on how I should go about it then? Should I even tell ATT that I got it from a friend? Instead I could say I got it from ATT but lost the receipt...maybe a loophole somewhere.
If the phone had been activated for less than a year and its not a refurbished unit, they should replace it.
I don't know if this will catch on or not, but I'd like to hear people's stories on how they screwed up or thought they screwed up their phone and fixed it? I think this could be an interesting thread with plenty of good stories and such
absoluterebirth said:
I don't know if this will catch on or not, but I'd like to hear people's stories on how they screwed up or thought they screwed up their phone and fixed it? I think this could be an interesting thread with plenty of good stories and such
Click to expand...
Click to collapse
I haven't screwed this phone up but I remember when I first started rooting phones I bricked my Vibrant (Galaxy S). I think I bricked it because I flashed the wrong radio or something. After that I have never bricked another phone. **Knock on wood**
Now I take extra caution and read extensively before rooting, flashing Roms, kernels etc.
sent from my neXus 5
Heres how i screwed my Nexus 5 on stock, I forgot to charge it and its now dead..
How i fixed it? I charged it :good:
I didn't because I actually read the stickies on the top of the general forum.
/Thread
Sent from my Nexus 5 using Tapatalk
Just took apart my Nexus 5 after it was unresponsive after a week of putting into rice/silica gels. No idea of what I am doing. I have never opened anything up in my life. Soaked motherboard into isopropyl and cleaned it with toothbrush, dropped it like 10 times, ripped a couple of cables. Should be all good though. Will post if it worked.
eastpac said:
Just took apart my Nexus 5 after it was unresponsive after a week of putting into rice/silica gels. No idea of what I am doing. I have never opened anything up in my life. Soaked motherboard into isopropyl and cleaned it with toothbrush, dropped it like 10 times, ripped a couple of cables. Should be all good though. Will post if it worked.
Click to expand...
Click to collapse
Yeah, ripping cables is probably not going to turn out "all good". Just my opinion
markdapimp said:
Heres how i screwed my Nexus 5 on stock, I forgot to charge it and its now dead..
How i fixed it? I charged it :good:
Click to expand...
Click to collapse
Please accept this Thanks as your post is very accurate and straight to the point.:good: Many of us have had that experience before whether it's forgetting to charge it over night by not plugging it into a charging source or it running out of battery power from heavy/extented usuage and not being able to charge it immediately after.:highfive:
DON`T USE TOOLKITS, these are related to most screwups Oh and get your rooting/flashing/adb skills up to par
FuMMoD said:
I didn't because I actually read the stickies on the top of the general forum.
/Thread
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Same!
Sent from my Nexus 5 using Tapatalk
I've only totally bricked one device, that was a sprint HTC evo (og evo). I got a replacement device via insurance and due to new firmware, I bricked it trying to root it/set s-off. No fix possible, only a new phone.
As far as nexi, nexus 5 specifically, I've soft bricked it a ton of times. But, one of the reasons I love the nexus brand, its never taken any more than a nandroid restore or only once a revert to stock. Unless you Dev test (and knowingly flash untested fw) or just start randomly picking zips and flash a modem or boot loader from a different device I've found it damn near impossible to make a nexus device unrecoverable.
I did initially flash the multi-boot mod w an incompatible ROM (beanstalk) and a kernel that really didn't like the multi-boot idea either (don't remember which ver of which kernel ATM). I was stuck on the "Google" boot loader screen for hours til I tried flashing a different ROM (which also changed the kernel) and trying again. Frustrated the hell out of me, kept phone unusable for almost a whole day, and wasted a ton of my time due to my laziness to read the whole thread.
Best advice ever given on XDA, whether you are a novice/learning/a noob or a android pro many years of experience or even a skilled developer.....
ALWAYS, ALWAYS, ALWAYS... did I say ALWAYS read the whole op or even better whole op and hopefully 90%+ of the thread before you try something you are unsure of.
Sent from my Nexus 5 using Xparent Skyblue Tapatalk 2
helioXverse said:
As far as nexi
Click to expand...
Click to collapse
Nexuses
Had the device perfectly set-up, with a few twrp backups as well and then for no reason...moved those backups from the device to the pc (probably in order to free some space). Then in a sequence of screw-ups, downloaded Flashify and wiped the cache and and dalvik cache from within the app (thinking it would be cool)...AND...bootloop! No backups...nothing! Booted to recovery...wiped cache/Dalvik the usual way, still nothing! Wiped data...nothing! Couldn't get ADB to work in the recovery. Finally -> Bootloader -> Fastboot Flash Stock ROM!
Did not stop though. in the next 5 minutes I was back with custom recovery, root and Titanium backup...ready to get back the device in shape (done and dusted as I type )
Reading the undervolting thread I decided to go -75 across the board. I succeeded but then tried to push it lower. Bootloops occurred. Backup copied back to SD card from PC failed to restore (said data failed. This was my first time restoring a ROM on the Nexus 5. If someone has insight as to why this happened it would be appreciated). Decided to go aosp and flash Rasta + trinity kernel but for some reason my mobile data wouldn't activate nor could I update PRL or profile by clicking on the usual option even after reboot and continuously clicking. Now I'm just getting my phone back to the original state it was in before I screwed up my UV values. Cataclysm + ElementalX #Life of a Phone Nerd
Sent from my Nexus 5 using XDA Premium 4 mobile app
gee2012 said:
DON`T USE TOOLKITS, these are related to most screwups Oh and get your rooting/flashing/adb skills up to par
Click to expand...
Click to collapse
I actually used a toolkit to return mine back to stock after i shipped it out to LG for repair after my son dropped. It was much easier for me than to write out the commands. took me about 10 minutes and that was because I locked the bootloader before flashing a zip. and i had to go back yada yada but worked out fine.
Screwed up 2 Galaxy S2's, first one because I didn't pay close enough attention to the brickbug, second one because it just died... Due to the brickbug. Other than those I've never killed a phone. I thought I had broken my friends Nexus 5 though, I unlocked it and went to root it for him but TWRP/CWM couldn't mount any partitions because it's "encrypted". Got it fixed though.
I've killed xbox's, PSP's, everything. It's all part of the learning process.
...When I first got my Nexus 5 in MTP on my Windows PC I had my phone hooked up to, on Internal Memory I saw a folder called sdcard that was not there before that was supposedly empty according to MTP. Deleted it. Turns out it was a symlink screwup in MTP, and it deleted my entire SD card including photos, luckily the important ones were already uploaded to Facebook and such. Now I backup my phone almost daily just in case.
I bricked my Archos Home Connect 35 once. Kinda my fault. I had set the bootloader to boot SDE firmware for it defaultly on boot. (Dev edition firmware from Google that was rootable). I updated from .82 firmware to .83 firmware, forgot to change that. It took the SDE firmware out, normally youd have to reinstall it, and since it was set to boot from that in Archos. mess of a firmware and bootloader, it would just bootloop because the SDE firmware wasnt there. No way to get out of it. RMA'd it and got a new one from Archos though. Never again, will always just manually select the SDE Dev Edition firmware when/if i ever reboot it. (Its just a Alarm clock mostly that plays Pandora occasionally. it last went 300 days without a reboot until it hard locked and I had to reboot. )
Never had a unrecoverable problem with my Galaxy S4, or my Nexus 5.Worst case with the S4 I Odin'd back to stock firmware. Nexus 5 got a corrupt data or cache partition once, i could have ran fsck but I flashed stock images instead.
I was having an issue having my phone seen on my PC. This is after I've rooted... Transferred music and pics from PC to phone, so I knew my drivers were installed. So I tried going back to stock. I downloaded the stock image and tried fastboot flashing. My download was corrupted. It got froze sending the radio. Froze for 30 min... Just kept saying sending. So I finally unplugged and rebooted to bootloader as everything else has been wiped. Tried again and it froze again at sending the boot loader. Froze for 30 min. I unplugged and tried rebooting. It never turned back on. No charging indication or anything. Officially bricked. I had tmo send me a new one and I'm returning the old one today. Wish me luck
First brick of my life and I've been rooting and modding since the OG Nex1
Sent from my Nexus 5 using Tapatalk
My GPS was working intermittently so I applied the cardboard fix and now its great. But in the process I damaged my back cover and now NFC and wireless charging don't work.
Really wishing I just RMA'd it.
Sent from my Nexus 5 using XDA Premium 4 mobile app
I never noticed this but couple days ago, my wife's note 3 started to lock up constantly throughout the day. I told her these things happen sometimes and to just take the battery out, and put it back in and let it restart. When she did this, I realized under the SAMSUNG on bootup, there was an unlocked padlock with the wording CUSTOM under it. I was shocked and confused how this can be...
I asked her about it, and she said it's been like that since we got the phones. She remembers at the AT&T store that the seal was broken off by the salesman, so there is no way it was a returned phone.
What gives? ATT is going to give her a refurb phone, but she's very mad because we've had the phone for 2 months and had no idea she had an unlocked phone, and she shouldn't be penalized for getting a 'used' phone.
They told her that it was the nova launcher that is causing the issues, becuase it's an unofficial app. these people....
I told her maybe she got lucky and got a dev phone (too bad dev phone keeps locking up lol)
any ideas on this?
try running the "root checker" app on it. Mine showed it after I first flashed it.
Sent from my SM-N900T using Tapatalk
They are stupid. It's not Nova.
I highly doubt it is a dev phone... But if it is, I would love to see the model number of the device and system info. Would you be willing to post that info?
Sent from my SAMSUNG-SM-N9005A using XDA Premium 4 mobile app
graydiggy said:
They are stupid. It's not Nova.
I highly doubt it is a dev phone... But if it is, I would love to see the model number of the device and system info. Would you be willing to post that info?
Sent from my SAMSUNG-SM-N9005A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
sure, i will try to get it to you guys.
This is hilarious, I installed nova before I root my phone, and there was no custom and pad lock when reboot, the custom and pad lock only showed up after I rooted my phone, the custom and pad lock had remained on the screen even I unroot the phone. I think your wife got a returned phone.
It still had all the seals on it!!!
here are the pictures. she got a replacement phone, and that is messed up too. the screen fails to turn on. everytime you press ON, the phone vibrates, but nothing from screen. She said after she took battery out etc, THAT phone ended up with the custom logo at bottom too. I have no idea what she's doing to these phones!!!!
I thought the custom only happened when you rooted it and placed safestrap or a recovery on them.
Looks normal to me.its not a developer edition.
I am curious as to why it is throwing this Custom status when it isn't.
I assume both are complete stock. no root, etc.
Sent from my SM-N9005 using XDA Premium 4 mobile app
razorseal said:
here are the pictures. she got a replacement phone, and that is messed up too. the screen fails to turn on. everytime you press ON, the phone vibrates, but nothing from screen. She said after she took battery out etc, THAT phone ended up with the custom logo at bottom too. I have no idea what she's doing to these phones!!!!
Click to expand...
Click to collapse
i would use the return to MJ5 stock thread and flash the odin MJ5, then the MI9 fix and then the proper Mj5 files again and see if that clears up the issue. something seems to be lingering in the system that gives it the "custom" status.
coolmingli said:
This is hilarious, I installed nova before I root my phone, and there was no custom and pad lock when reboot, the custom and pad lock only showed up after I rooted my phone, the custom and pad lock had remained on the screen even I unroot the phone. I think your wife got a returned phone.
Click to expand...
Click to collapse
graydiggy said:
Looks normal to me.its not a developer edition.
I am curious as to why it is throwing this Custom status when it isn't.
I assume both are complete stock. no root, etc.
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
the2rrell said:
i would use the return to MJ5 stock thread and flash the odin MJ5, then the MI9 fix and then the proper Mj5 files again and see if that clears up the issue. something seems to be lingering in the system that gives it the "custom" status.
Click to expand...
Click to collapse
I might have to do that, but what a hassle. this woman just wants to use her phone! Might do a factory reset for her, see how that works out..
coolmingli said:
This is hilarious, I installed nova before I root my phone, and there was no custom and pad lock when reboot, the custom and pad lock only showed up after I rooted my phone, the custom and pad lock had remained on the screen even I unroot the phone. I think your wife got a returned phone.
Click to expand...
Click to collapse
graydiggy said:
Looks normal to me.its not a developer edition.
I am curious as to why it is throwing this Custom status when it isn't.
I assume both are complete stock. no root, etc.
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
100% stock. she wouldn't know a thing about root.
razorseal said:
I might have to do that, but what a hassle. this woman just wants to use her phone! Might do a factory reset for her, see how that works out..
100% stock. she wouldn't know a thing about root.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2559715
here is the link to the Back to MJ5 stock thread, in all honesty once you get the files downloaded it only takes about 20 min to have the phone booting back up to stock MJ5 "WithOut ROOT" i just did this about 2 weeks ago. it DID get rid of the "custom" status and recovered my brick at the same time.
def worth trying!!!
You can root with kingo and use triangle away to remove the custom status.
As far as the other issues, a factory reset might help but a restore will be more likely to get rid of everything causing problems
Sent from my SM-N9005 using XDA Premium 4 mobile app
My first note 3 did that too, a few days before it went into bootloops. Something was wrong with it. Att swapped it as it was within the first 2 weeks.
Swap it out is my suggestion, If you still can. It may start going wrong one day.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
WHat I might do is, go to the ATT store with BOTH phones, and show them how this one keeps locking up (well I can't show that probably as it's random) but I can show the custom thing.
then I can show the refurbished phone that I just received and how the screen fails to turn on.
hopefully the corp store can get the idea, and give me a new phone or something
razorseal said:
WHat I might do is, go to the ATT store with BOTH phones, and show them how this one keeps locking up (well I can't show that probably as it's random) but I can show the custom thing.
then I can show the refurbished phone that I just received and how the screen fails to turn on.
hopefully the corp store can get the idea, and give me a new phone or something
Click to expand...
Click to collapse
OH CRAP NO!!!!
if they SEE the custom status, they will not even deal with you unless you get a really cool rep. They instantly think that you tried to ROOT the phone and that is why you have ANY ISSUE you are talking about. i would not bring that phone into the store looking like that bruh.
the custom status is a symbol for root/modded phones. just do the stock restore, and IF at that point you want to take it back go for it. at least you will not have the custom lock screen going against you.
the2rrell said:
OH CRAP NO!!!!
if they SEE the custom status, they will not even deal with you unless you get a really cool rep. They instantly think that you tried to ROOT the phone and that is why you have ANY ISSUE you are talking about. i would not bring that phone into the store looking like that bruh.
the custom status is a symbol for root/modded phones. just do the stock restore, and IF at that point you want to take it back go for it. at least you will not have the custom lock screen going against you.
Click to expand...
Click to collapse
The point is not how to get rid of the custom logo, the point is why OP's wife brand new Note 3 sealed in the box has the logo, ATT should exchange it with a new phone not an refurbished.
coolmingli said:
The point is not how to get rid of the custom logo, the point is why OP's wife brand new Note 3 sealed in the box has the logo, ATT should exchange it with a new phone not an refurbished.
Click to expand...
Click to collapse
i feel that, but what you are saying is that you want ATT ( big brother so to speak ) to admit that sent him a modded phone? WONT HAPPEN!!!
they will accuse her/him of tinkering and that is what caused the custom logo. even IF it came that way. i dont see them eating that blame as im sure they have quality control and procedures in place that should catch that kind of slip. and if it did slip through....you expect them to say yep your right we screwed up.
things happen, but i dont see them being ok with that....lol
I did be real mad if I bought the phone contract or not only found out it's been tempered.
coolmingli said:
I did be real mad if I bought the phone contract or not only found out it's been tempered.
Click to expand...
Click to collapse
i would too, but being mad will not change there view of a custom phone. best you can do is either fix it yourself ( stock odin packages ).
Orrr go into the store and HOPE you get a rep that doesnt know what the CUSTOM logo means.
My Verizon LG G2 was rooted and was trying to install CWM. Was booting into recovery through CWM App and now phone will not turn on at all. Just vibrates when I hit the power button. Any help please?
The Loki patch is not a bootloader unlock you cannot install cwm through ROM manager you have to use an app called freegee once the screen is not turning on I don't think its fixable I may be wrong but it sounds like its really bricked
Sent from my LG-VS980 using Tapatalk
---------- Post added at 02:29 PM ---------- Previous post was at 02:28 PM ----------
Crap spell checker added once
Sent from my LG-VS980 using Tapatalk
I used Freegee to install. Was trying to boot into recovery using CWM.
Same problem
there has to be some sort of a fix... I downloaded freegee, then installed TWRP, rebooted it, and now it wont turn on, is NOT recognized by my computer, and wont even load the logo after i hold the power + Vol. Down. if I hold them for a while, red LED will show until I let go of them.
Same thing happened to me today. Cant get it to come on at all.
hopk1719 said:
My Verizon LG G2 was rooted and was trying to install CWM. Was booting into recovery through CWM App and now phone will not turn on at all. Just vibrates when I hit the power button. Any help please?
Click to expand...
Click to collapse
Has happened to a few of us. I wish I would have seen this post before I tried to flash recovery
The dev of freegee has removed twrp from the app until he finds out what happened plug your phone in maybe 30 minutes and try to turn it on the dev of freegee says your g2s should be fixable don't know how but he knows this phone a lot better than me if it still won't turn on wait a few days and hopefully someone will come up with a fix I feel bad for you guys hope you can get your g2s fixed
Sent from my LG-VS980 using Tapatalk
---------- Post added at 12:34 AM ---------- Previous post was at 12:18 AM ----------
Correction he has removed 12b support entirely
Sent from my LG-VS980 using Tapatalk
spinninbsod said:
The dev of freegee has removed twrp from the app until he finds out what happened plug your phone in maybe 30 minutes and try to turn it on the dev of freegee says your g2s should be fixable don't know how but he knows this phone a lot better than me if it still won't turn on wait a few days and hopefully someone will come up with a fix I feel bad for you guys hope you can get your g2s fixed
Sent from my LG-VS980 using Tapatalk
---------- Post added at 12:34 AM ---------- Previous post was at 12:18 AM ----------
Correction he has removed 12b support entirely
Sent from my LG-VS980 using Tapatalk
Click to expand...
Click to collapse
Yah, this sucks. Just curious if the manual way is working fine with the ota 12b?
I wouldn't try it its not freegee the app I wonder if Verizon/lg patched the bootloader to deny our current Recovery's this seems to be happening to people who just bought there g2s they must have just patched the bootloader but no ota update this has Verizon's name written all over it
Sent from my LG-VS980 using Tapatalk
spinninbsod said:
I wouldn't try it its not freegee the app I wonder if Verizon/lg patched the bootloader to deny our current Recovery's this seems to be happening to people who just bought there g2s they must have just patched the bootloader but no ota update this has Verizon's name written all over it
Sent from my LG-VS980 using Tapatalk
Click to expand...
Click to collapse
I bought a used one and used the app and my phone is bricked. I'm talking about manually using adb. That method works still?
It is not the app it is the recovery shellnut thinks verizin /lg did something we are all very confused if I were you just to be safe I wouldn't try it
Sent from my LG-VS980 using Tapatalk
Is there any news on this? I have tried everything to get the g2 to fire back up but no luck. When charging the led blinks red. When attempting to turn it on the phone vibrates every 2 seconds. I think I am just going to get a replacement. Anyone have any advice?
On a separate note, I have no idea why this happened. I clean wiped, installed a rom, rebooted all from recovery and the phone never booted into anything. I wasn't even a slight bit worried because I know I did this correctly.
I appreciate it, thanks.
mattandroidmatt said:
Is there any news on this? I have tried everything to get the g2 to fire back up but no luck. When charging the led blinks red. When attempting to turn it on the phone vibrates every 2 seconds. I think I am just going to get a replacement. Anyone have any advice?
On a separate note, I have no idea why this happened. I clean wiped, installed a rom, rebooted all from recovery and the phone never booted into anything. I wasn't even a slight bit worried because I know I did this correctly.
I appreciate it, thanks.
Click to expand...
Click to collapse
Just get a replacement. tell them that it wont turn on. DO NOT tell them that you rooted it. hahaha
Just had this happen to me.
It's probably dead.
Plug it in and give it some time to charge.
I finally got into recovery mode and was able to restore a ROM (bad flash and was stuck at the LG logo)
Freegee has been bricking devices since its conception. I'm surprised people are still trying to use it.
If anyone reads this before trying to use it, I would suggest not to.
I've used flashify once and it worked fine, but it's really best to push it via adb. Don't know how? Google is your friend. Or the search function on these forums. There's full guides on how to push a recovery on the g2.
Taking the easy way is normally never the best way.
Sent from my VS980 4G
So does this mean the phone is fried? I received mine like this and have no idea what to do. I am not a Verizon customer so I have no way to return the phone. I took it in a trade for my phone thinking it must be fixable and now I am without a device. I know it is my own fault for not doing my research first but this really just sucks :/
nickkeslar said:
So does this mean the phone is fried? I received mine like this and have no idea what to do. I am not a Verizon customer so I have no way to return the phone. I took it in a trade for my phone thinking it must be fixable and now I am without a device. I know it is my own fault for not doing my research first but this really just sucks :/
Click to expand...
Click to collapse
Can you plug the phone into the computer and enter download mode? If not and you can't get get into recovery, then it is bricked.
You could always try to use lg's one year warrenty. It will cost you thought.
Sent from my Vs980 running CloudyFlex 2.0
Lawlrus said:
Can you plug the phone into the computer and enter download mode? If not and you can't get get into recovery, then it is bricked.
You could always try to use lg's one year warrenty. It will cost you thought.
Sent from my Vs980 running CloudyFlex 2.0
Click to expand...
Click to collapse
No download mode, no recovery. The stupid LED wouldn't even light up. Luckily, I was fortunate enough to get my old phone back. A guy found me on craigslist and texted me asking me to unlock his model LS980 for T-Mobile, and in turn he would trade me the VS980 for a Droid Ultra. And like I said, I obliged and thought I could fix it, without doing my research first. Well like I said, I was fortunate enough that he traded me back today. Now I have another swap set up with a guy tomorrow, to trade my Ultra for his LS980. But this one has issues too. For some reason it has no sound at all, unless you use a Bluetooth. I'm sure that will be annoying really really fast, so anyone have any ideas where I can find the info to fix this? Lol
nickkeslar said:
No download mode, no recovery. The stupid LED wouldn't even light up. Luckily, I was fortunate enough to get my old phone back. A guy found me on craigslist and texted me asking me to unlock his model LS980 for T-Mobile, and in turn he would trade me the VS980 for a Droid Ultra. And like I said, I obliged and thought I could fix it, without doing my research first. Well like I said, I was fortunate enough that he traded me back today. Now I have another swap set up with a guy tomorrow, to trade my Ultra for his LS980. But this one has issues too. For some reason it has no sound at all, unless you use a Bluetooth. I'm sure that will be annoying really really fast, so anyone have any ideas where I can find the info to fix this? Lol
Click to expand...
Click to collapse
I am pretty sure that LG has a 1 year warranty and they would've replaced it for you for free. I went to Verizon and they sent me a new one right away but a while back I had upgraded my old droid 1 before the 1 year period ended and I bricked it just messing around. Motorola replaced it with a refurb and I never even went to Verizon. I just had to pay shipping. Maybe you should try the same thing. Just send a couple emails back and forth with LG customer support and see what happens. Good luck.
Add me to the brick list
Lawlrus said:
Can you plug the phone into the computer and enter download mode? If not and you can't get get into recovery, then it is bricked.
You could always try to use lg's one year warrenty. It will cost you thought.
Sent from my Vs980 running CloudyFlex 2.0
Click to expand...
Click to collapse
Mine did the same thing this morning, although it has been fine for 2 months since root+xposed+freegee (for TWRP).
But if I send it back for warranty replacement, will they be able to see it has been rooted if it won't turn on? I love the phone, but really don't want to be billed full price for a new one.