Related
Background: Very familiar with the Eris, rooted it, flash ROMs frequently, never had an issue.
So I bought the phone on eBay, only issue was the phone was a bit beat up and the screen had been replaced. No big deal. Turned it on everything was fine, worked for about a day, then I decided to flash another ROM. Flashed the ROM and the phone would reboot every time I got to the lock screen UNLESS I had signal, then it would work. This issue happens to EVERY ROM I flash. I wiped cache,dvlik-orwhatever, full wipe, everything each time I would flash a ROM, and none of them have been stable. After flashing the first ROM I also ran into the turn off and vibrate 5 times with a flashing green light problem. I have gotten out of this twice with the USB pull method. I have researched these issues, I have tried flashing quite a few ROMs, and nothing seems to work flawlessly. Is the DI just a terrible phone or do I just have a bad unit? The main issue seems to be with signal, such as if I go from airplane mode on to off it will reboot and then get stuck in a boot cycle and the issue with flashing the phone and having to have signal before I can unlock the phone.
I am currently about to flash the PB31IMG to see if it will resolve the issues and then attempt to re-root. Any advice would be greatly appreciated as nothing has seemed to work so far. I would key you into what I have tried but I don't remember. Basically all the things to fix the 5 vibrate issue and general flashing woes.
Update:
Still no good. Flashed the PB31IMG via vol. down and power and it still did a reboot. Unlocked, got to the white HTC screen, and restarted. Booted the second time, got to the lockscreen, and rebooted before I could even slide down the unlock. Third reboot, got to activation this time, then it rebooted. Fourth reboot, go to activation, then rebooted. Fifth reboot, got to lockscreen, then rebooted before I could slide down.
So yeah. basically you can see what I am dealing with. And it is not fun. I have tried SD card in, SD card out. Just did its 6th reboot, didnt even get to the unlock screen before rebooting.
UPDATE 5/3:
Link to the video of whats happening. Nothing special and I recorded it with my Eris, but you'll at least see the timing of the reboots and what not. And ignore the breathing. lol. Just turn off the sound. Right after the video ended it did a 5 vibe. Pulled the battery and now it's just doing bootloops.
I have never had the random reboots before, at least not at the rate and consistency you have been. To me it sounds like something went wrong in the rooting process and I would recommend unrooting and rerooting.
As for the flashing green light and 5 vibrates, I have so insight on this. It can happen if you press power and Vol+. I think it puts it in a safety mode and the only way to get out of it is a battery pull. So if you ever get stuck in a situation like this wait 10 minutes and try to turn it back on normally. If this doesn't work try booting into hboot (power + vol down) if this doesn't work power + vol up has worked for some people too.
There are cases however, where battery pulls don't help either. And no matter what the person tries the phone won't turn back on. This is a hardware problem and the only way to fix this is getting a new phone.
Dhessler5 said:
I have never had the random reboots before, at least not at the rate and consistency you have been. To me it sounds like something went wrong in the rooting process and I would recommend unrooting and rerooting.
snipped.
Click to expand...
Click to collapse
Would flashing the PB13IMG in Hboot unroot it or would I need to follow the guide? Just curious as I have never unrooted before, but I do know there is a guide for it.
The 5 vibrate thing is under control, it just has happened so I wanted to make it known.
And thanks for the info.
I would follow the guide for it, it would be the easiest and safest way and if you run into any problems they would be able to help you out and know exactly what to tell you. I have yet to unroot too so I don't want to tell you something without being 100% sure so I recommend the guide.
Alright, so it turns out flashing the image I flashed via Hboot is a way to unroot. :/ And that is when I got all the reboots in the beginning (the ones specifically posted, its not the first time). I am going to flash again once more to see if I can get a flawless start.
Still no good, flashed it again via Hboot and it restarted again. This timeat the white HTC screen after unlocking but before activation. :? Hm. Better than nothing, after the first reboot it fully loaded and everything is fine so far. Lets just home it doesn't slowly begin to degrade like last time.
A while ago while running the peanut stock ROM, every time my phone would reboot some apps would loose information (such as log in) and I was eventually unable to access the EPST settings.
If you rerooted your phone you could try to go into hboot and then recovery and "fix permissions." I am not sure if this will do any good but it couldn't hurt.
Also if it is unrooted you could try to bring it in to Verizon and see if they will give you a new phone or a restored one.
Make sure you have the stock Rom if you bring it back to Verizon also
sent from my dinc
sorry to hear this happened on an ebay phone... I've had it happen to 3 of mine... warranty took care of it since I'm still within my date. but after one year what do I do? luckily I bought my bros early upgrade meaning the Inc2 will suffice until april 2012
ohh yea my point sorry: I had an Eris before the Inc. //////had many problems after 5 they gave me the Inc if I agreed to drop my current one year contract and get a new two year paying the two year price PLUS got credited $199 for the Eris, and got to keep it, so I thought I made out until I realized this phone isn't gunna last two years. ANYWAY. I bought the Eris off Ebay, they gave me warranty after warranty no problem, best of luck
I have had my Inc for a year and have not had any issues. I would say you bought a bad model from someone on eBay. The 5vibration green light is indicative of a hardware failure and I have not seen anyone have a fix for it.
Sorry to say but I have seen no one, NO ONE recovery from the 5 vibs of death. From what I have gathered it is some sort of qualcomm download mode and I know of no way out. I have a feeling it is caused by pressing the vol + and vol - and power while trying to get into hboot.
This is just an uneducated guess. If your willing to part with the device I would love to get my hands on a 5 vibs phone.
Since it happens when the phone loses the signal, I'm wondering if it might be a radio issue. Which radio version is installed? It could be incompatible for your area/ROM/whatever.
Another thought: you said the screen was changed out. It is very possible that the kernal installed won't work for an lcd screen.
Anyway, more things to check and to test. Good luck!
mine always happened when i accidently pushed the vol + instead of vol -
twice it happened
ACD168 said:
mine always happened when i accidently pushed the vol + instead of vol -
twice it happened
Click to expand...
Click to collapse
That should be 3 vibs, not the 5.
they both won't work after wards thought as far as my testing.. had to get warranty replacements
I remember reading Chingy fixed 5 vib. It's not the end. I've seen other people fix it with ruu.
I couldnt fix mine when I got the 5 vibrations and I tried everything. My theory is that it has something to do with a messed up kernel flash since the baseband and kernel are apparently linked and I saw somewhere that flashing the same baseband 2x will cause this. It happened to me when I tried to flash a kernel twice (the first time it failed), some people could be getting this when flashing roms since they install new kernels also.
You can flash radios and kernals twice. There was one leaked radio in the past that caused problems from being flashed twice, but it isn't typical
Edit: I think chingy said something about trying a hundred different things, but eventually he got it to work by connecting to PC with battery removed. I could be wrong though because I read that post months ago. I know he got it working again by wiping system and starting fresh
I had the 5 vibs on mine a few weeks ago. It was an unfortunate event. I had the phone for almost a year, bought it new too. I had probably flashed at least a hundred times (thank you nighties for feeding my ROM flashing addiction) but I digress.
I was at work when it happened. If I remember right I believe I was re-installing a pandora apk when my phone did the vibs and led. As an fyi it is the same apk I am using now and it works fine. I initially thought oh well I'll fix it when I get home, surely someone has the answer...sadly not. I spent quite a while searching threads and google to no avail.
I was able to get it unrooted through hboot tho. I was also able to get it to boot when usb was connected to my PC, but as soon as I unplugged it would do the vibs again.
I don't like to admit defeat, but I had clearly lost. I called and got a replacement device sent (and an extended battery because the guy thought it could have been a battery issue, lucky me)
All I can do now is hope it doesn't happen again, but if it does hello warranty man. If someone does find a fix I would love to know about it for future reference.
Sent from my ADR6300 using XDA Premium App
Trifurcated said:
I had the 5 vibs on mine a few weeks ago. It was an unfortunate event. I had the phone for almost a year, bought it new too. I had probably flashed at least a hundred times (thank you nighties for feeding my ROM flashing addiction) but I digress.
I was at work when it happened. If I remember right I believe I was re-installing a pandora apk when my phone did the vibs and led. As an fyi it is the same apk I am using now and it works fine. I initially thought oh well I'll fix it when I get home, surely someone has the answer...sadly not. I spent quite a while searching threads and google to no avail.
I was able to get it unrooted through hboot tho. I was also able to get it to boot when usb was connected to my PC, but as soon as I unplugged it would do the vibs again.
I don't like to admit defeat, but I had clearly lost. I called and got a replacement device sent (and an extended battery because the guy thought it could have been a battery issue, lucky me)
All I can do now is hope it doesn't happen again, but if it does hello warranty man. If someone does find a fix I would love to know about it for future reference.
Sent from my ADR6300 using XDA Premium App
Click to expand...
Click to collapse
I think the 3, vibrate and 5 vibrate are connected because both times I had the 3 vib I had the same problems, would turn on when connected to usb then 3 vib and green flashing light... weird.
I have read a few threads on this subject, none could give me any solid answers. I have seen countless people have this issue, If I can get this solved than I would be extremely grateful.
After restoring a nandroid backup all was well and when I went to reboot I got the splash screen then the screen went black. This is where the bootanimation should kick in, but it didn't. I get a black screen and then 5 vibrates and the LED flashes green. I did end up geting into hboot and where I used to be s-off it now say s-on. I don't know how that is possible.
Has anyone been successful with fixing this? If not who is willing to help me? I am not convinced my phone is done and I am not giving up, I'm just asking the community for help.
I tried the RUU method but that didn't work either.
trock79 said:
I have read a few threads on this subject, none could give me any solid answers. I have seen countless people have this issue, If I can get this solved than I would be extremely grateful.
After restoring a nandroid backup all was well and when I went to reboot I got the splash screen then the screen went black. This is where the bootanimation should kick in, but it didn't. I get a black screen and then 5 vibrates and the LED flashes green. I did end up geting into hboot and where I used to be s-off it now say s-on. I don't know how that is possible.
Has anyone been successful with fixing this? If not who is willing to help me? I am not convinced my phone is done and I am not giving up, I'm just asking the community for help.
I tried the RUU method but that didn't work either.
Click to expand...
Click to collapse
I've gotten 5 vibrates and green led but i just battery pull and it goes away that seems its not the case for everyone and everyone this has happened to has gone for a refurb i think you can still turn on the phone when its plugged its usb connected and i think this is caused by a corruption of emmc
JoelZ9614 said:
I've gotten 5 vibrates and green led but i just battery pull and it goes away that seems its not the case for everyone and everyone this has happened to has gone for a refurb i think you can still turn on the phone when its plugged its usb connected and i think this is caused by a corruption of emmc
Click to expand...
Click to collapse
Battery pull did not work, and usb doesn't work either, but I think you are on to something about the emmc.
With USB connected I was able to get into recovery for a few seconds before it bombed out again. I think I am getting somewhere.
If you go to threads I started, I had this problem, and someone posted saying they knew how to fix it. I ended up getting a refurb though as I didn't see his post in time. Can't remember his name, I'll get back on that.
EDIT: Heres his page. http://forum.xda-developers.com/member.php?u=534126
Hello all.
I am an HTC guy through and through and have never owned a Samsung device. I'm familiar with HTC's S-OFF/HBOOT/bootloader stuff, but I'm not really all that clear on how it works for Samsung devices. I promise I've tried to do some reading before hand before coming to you, including looking at other threads, but they don't seem to be the issue I'm having.
I'm trying to help a friend out who has an AT&T GS3 that I unlocked for him and put an AOSP ROM on it a few months ago (don't worry, I made damn sure it was the AT&T version and no other carrier/international ROM).
He came to me today telling me that his phone suddenly turned off, and was not turning on again. I figure it's probably just a corrupted partition, something that I could fix with a reflash or something like that.
However, when I look at it, it seems to be something potentially worse. The phone did nothing with the battery in, so I took it out and put it back in. The phone very briefly vibrates, the Samsung logo shows for about 1.5 - 2 seconds at most, and then the screen goes dark.
When I try to enter Download Mode, I'm able to get to the custom software "warning" page, where I press Volume Up, and it shows me Download Mode and "Waiting" (as I expect it to) but then the screen just goes black again after about a second or two.
It's roughly the same with Recovery Mode, I can catch a glimpse of what looks like CWM (but I'm not entirely sure) and then the screen goes black.
If I choose to forgo the battery altogether, and I plug it in straight to the wall, the red LED on the top right lights up for again maybe 3 - 4 seconds at most, the light goes away, and the phone briefly vibrates, shows me the Samsung logo, and then goes dark.
I'm confused. I don't know if it's a brick, but then again, to me as an HTC user, "brick" means Qualcomm USB Download mode. I've also read about this infamous Samsung Sudden Death Syndrome that struck some of the 16 GB models that Samsung sold (and yes, you guessed it, this is the white 16GB model).
I don't really know what other troubleshooting options there are (but as I said before, I'm an HTC guy). If any of you have any sort of advice I would love to hear it.
Thank you for your time.
I've seen several users on here in the last few months with this issue. I worked with one of them for awhile trying to get it straightened out but couldn't resolve the problem. Some of that was due to the nature of the problem and some was probably due to the fact I didn't have the phone in my hands to help the new user better. I believe the user was able to get an exchange at an at&t service center. Sorry I can't offer more assistance. Keep us posted if you get a fix.
xBeerdroiDx said:
I've seen several users on here in the last few months with this issue. I worked with one of them for awhile trying to get it straightened out but couldn't resolve the problem. Some of that was due to the nature of the problem and some was probably due to the fact I didn't have the phone in my hands to help the new user better. I believe the user was able to get an exchange at an at&t service center. Sorry I can't offer more assistance. Keep us posted if you get a fix.
Click to expand...
Click to collapse
I appreciate you trying. I know it's such an odd issue that it's really hard to diagnose. I thought perhaps it might have to do with the battery somehow being "bad", but then the problem would be gone when I go AC only.
He's not against the idea of going to AT&T, but I feel bad; I convinced him to unlock and let me flash a new ROM so I feel that I should at least put in a good effort to make sure there's nothing more I can do.
Yeah, the biggest problem is that once you get into recovery or download mode, the device reboots/loops. This eliminates the possibility of any kind of flashing or wiping.
You might have a bad motherboard. If I was you I'd take it to att for a replacement. BTW if he doesn't have insurance for the phone they do have open enrollment , I'd wait a day or two after enrolling to submit a claim.
Wish you the best.
Sent from my SGH-I747 using xda app-developers app
LiquidSolstice said:
I appreciate you trying. I know it's such an odd issue that it's really hard to diagnose. I thought perhaps it might have to do with the battery somehow being "bad", but then the problem would be gone when I go AC only.
He's not against the idea of going to AT&T, but I feel bad; I convinced him to unlock and let me flash a new ROM so I feel that I should at least put in a good effort to make sure there's nothing more I can do.
Click to expand...
Click to collapse
It's a realllly long shot but he could contact mobile tech videos and tell them his issue and see if a jtag repair would help. If it's hardware of course he is out of luck but it's worth a shot and a lot cheaper.
Hello everyone,
I'm trying to fix a Galaxy Tab 3 (p5220) for someone. The problem is that the tablet, when turned on, goes into a bootloop.
First of all I see the "Samsung Galaxy Tab" screen, then it jumps to the android robot standing (I believe this is the screen you see when you boot into recovery mode). The problem is that I can't do anything when I see this screen, it immediately jumps to the android robot laying on its back with a big red exclamation mark above him. Within one second this screen also goes away and the tablet reboots and starts doing the same thing.
I have already tried using the button combination to boot into recovery mode, when I do that the tablet reboots directly after the Samsung screen. So then I don't even see the android robot at all.
Then I tried booting into download mode, and this does work. I tried putting the stock firmware on it using Odin (not 100% sure if I used the right firmware though.). Anyways, this seemed to go as its supposed to go, but after Odin gave the "Pass" notification it rebooted, and started doing the exact same thing.
Does anyone have any idea if this is a hardware problem or can I still fix this?
ps. The person that I'm trying to fix this tablet for borrowed it to someone, and when it returned it did this. The person doesn't have any idea what has been done with the device. But we can be pretty sure that the person who borrowed the device tried to do something with it, but failed hard.
Thanks in advance for any kind of help!
I have the same scenario here as well. I have a friends Galaxy Tab 3 (SM-T310) and it seems to sit at the splash screen and never goes anywhere. I am unable to boot into recovery. I've tried Power+Vol Up, and Power+Vol Up+Home and nothing seems to be working. I am able to get into Download Mode. I have tried flashing TWRP 2.8.3.0 and TWRP 3.1.0 via ODIN, but I am still unable to get it to boot into Recovery.
I have also downloaded the Stock ROM from SAMMobile (I didn't see a US version, so I went with Canada? I figured, why not?) Flashed that via ODIN and I am still stuck at the splash screen.
I even took the back off and unplugged the battery and left it off for a few hours, since that is what the internet told me to do, and it still does the same thing.
I did just stumble across this thread: https://forum.xda-developers.com/showthread.php?t=2618798 so I am going to try CMW and see if anything changes. I figure once I can get into the recovery I'll be golden, but I haven't gotten that far yet. Any assistance would be greatly appreciated as well.
Mantics said:
I have the same scenario here as well. I have a friends Galaxy Tab 3 (SM-T310) and it seems to sit at the splash screen and never goes anywhere. I am unable to boot into recovery. I've tried Power+Vol Up, and Power+Vol Up+Home and nothing seems to be working. I am able to get into Download Mode. I have tried flashing TWRP 2.8.3.0 and TWRP 3.1.0 via ODIN, but I am still unable to get it to boot into Recovery.
I have also downloaded the Stock ROM from SAMMobile (I didn't see a US version, so I went with Canada? I figured, why not?) Flashed that via ODIN and I am still stuck at the splash screen.
I even took the back off and unplugged the battery and left it off for a few hours, since that is what the internet told me to do, and it still does the same thing.
I did just stumble across this thread: https://forum.xda-developers.com/showthread.php?t=2618798 so I am going to try CMW and see if anything changes. I figure once I can get into the recovery I'll be golden, but I haven't gotten that far yet. Any assistance would be greatly appreciated as well.
Click to expand...
Click to collapse
Someone with the exact same problem as me, with the exact same tablet, told that he fixed it by replacing the battery. To me it makes absolutely no sense that the battery would cause this, but I've literally tried everything software related to get this fixed. So I figured, why not give it a try! I'll post here as soon as I get the battery here.
Thanks for your reply, and let me know if you get it fixed!
musknl said:
Someone with the exact same problem as me, with the exact same tablet, told that he fixed it by replacing the battery. To me it makes absolutely no sense that the battery would cause this, but I've literally tried everything software related to get this fixed. So I figured, why not give it a try! I'll post here as soon as I get the battery here.
Thanks for your reply, and let me know if you get it fixed!
Click to expand...
Click to collapse
I have seen people pull the battery connector out, and leave it be for a few hours, and I tried that first, but that didn't appear to work for me. Maybe you can try that first before ordering the battery, but if you do get a new battery and that resolves the issue, let me know! You rock!
Mantics said:
I have seen people pull the battery connector out, and leave it be for a few hours, and I tried that first, but that didn't appear to work for me. Maybe you can try that first before ordering the battery, but if you do get a new battery and that resolves the issue, let me know! You rock!
Click to expand...
Click to collapse
I had the battery out for multiple days already, so I tried what you said just now. Still did the same thing.. I'm hoping to get the battery today or tomorrow! I'll let you know.
musknl said:
I had the battery out for multiple days already, so I tried what you said just now. Still did the same thing.. I'm hoping to get the battery today or tomorrow! I'll let you know.
Click to expand...
Click to collapse
You Sir (or Ma'am, I don't want to assume gender) are amazing! I hope that works, and if so, I'll have the guy order a battery and then I'll throw it in for him as well. Hopefully we can figure this thing out!
Mantics said:
You Sir (or Ma'am, I don't want to assume gender) are amazing! I hope that works, and if so, I'll have the guy order a battery and then I'll throw it in for him as well. Hopefully we can figure this thing out!
Click to expand...
Click to collapse
I identify as an attack helicopter
Anyways, got the battery and unfortunately it didn't solve the problem
I'm going to see if I can fix it any other way, but I wouldnt know where to start...
You got any luck yet?
musknl said:
I identify as an attack helicopter
Anyways, got the battery and unfortunately it didn't solve the problem
I'm going to see if I can fix it any other way, but I wouldnt know where to start...
You got any luck yet?
Click to expand...
Click to collapse
Thanks for your reply!
I haven't really tried anything else yet, I was waiting to hear back from the battery. I had high hopes for that. Does your battery ever look like it is charging? The one I have here just kind of sits there and doesn't appear to display the "Charging Screen" it just has a battery symbol with a circle on it, but nothing moves. It isn't mine so I don't know if that is "normal" behavior. The stock battery doesn't look swollen or anything, and even though it doesn't appear to charge, it still holds a charge. I will start posting links to things I try. Maybe we can figure this thing out?
Mantics said:
Thanks for your reply!
I haven't really tried anything else yet, I was waiting to hear back from the battery. I had high hopes for that. Does your battery ever look like it is charging? The one I have here just kind of sits there and doesn't appear to display the "Charging Screen" it just has a battery symbol with a circle on it, but nothing moves. It isn't mine so I don't know if that is "normal" behavior. The stock battery doesn't look swollen or anything, and even though it doesn't appear to charge, it still holds a charge. I will start posting links to things I try. Maybe we can figure this thing out?
Click to expand...
Click to collapse
My tablet doesn't even show a battery icon.. I think yours has more chance of getting repaired than mine hehe.
Yours sounds very likely to be the battery btw. You flashed a custom recovery right? How did you do that?
musknl said:
My tablet doesn't even show a battery icon.. I think yours has more chance of getting repaired than mine hehe.
Yours sounds very likely to be the battery btw. You flashed a custom recovery right? How did you do that?
Click to expand...
Click to collapse
I can get into Download Mode, and Odin will tell me it is flashing things, I even get the little progress bar along the bottom and it will reboot the device once finished...it just never boots into the OS, and I can't get it to boot into the recovery once flashed...so I have no idea what is going on. It makes me angry, like a clown! (Also, clowns are angry.)
I haven't played around with anything today since I'm a little bummed out since they shorted me about 96 hours from my last 3 paychecks at work, so I'm kind of on strike. Anyway, I will play around with it on Monday and post everything I try, and get back to you. Maybe I'll even pull the battery out again and let it sit all weekend before I duck out 2 hours early.
---------- Post added at 02:24 PM ---------- Previous post was at 02:16 PM ----------
So, I just pulled off the back, undid the battery, and plugged a USB cable into the device for power. Do you happen to know if these will boot without a battery? I ask because it appears to be doing the same thing, so it may well be the battery, but the battery doesn't look swollen or anything, so idk? Thought?
I'm sure you've probably tried this but just wanna be sure... I've been watching this thread to see what things were tried.
When you boot to recovery it is by holding power, vol+, and home...but once the splash screen shows up let off of power but keep vol+ and home pressed...if not it will just reboot. Hope this helps, though I know it is unlikely.
Sent from my XT1609 using Tapatalk
Okay, well, hi y'all!
I have been around here, been fixing phones from your tutorials here since around 2012, so I am experienced with flashing etc.
This time though, it has got me on the point of just throwing the device away.
So, its about my mothers OnePlus 5T. It doesnt respond to anything I do to it. It won't turn on, it won't boot in to Qualcomm download mode nor in to recovery or fastboot. The device has not been tempered with before, I dont think my mother knows how to flash it
So, this is what exactly happened, according to my mother.
She woke up, got on to facebook and has been browsing a little, untill suddenly the phone turned black, gave her a warning in the left upper corner of the screen, which said something like; warning, do not share personal info. Or something like that, after that, it gave the logo of OP, and then never got a response from it ever since.
It does not react to pressing buttons, nothing, no led nothing. Charger doesnt give any response, neither did my pc with the qualcomm drivers installed.
So currently it is literally a brick, and I hope somebody can help me. I have a lot of background with flashing etc, so if the answer is really complex, no problem!
Thanks in advance,
Dane
Oneplus 5t issue
contact Oneplus.com and get a RMA to return the unit for repair or replacement. they are very friendly but not much help with trouble shooting.
daneburnes said:
Okay, well, hi y'all!
I have been around here, been fixing phones from your tutorials here since around 2012, so I am experienced with flashing etc.
This time though, it has got me on the point of just throwing the device away.
So, its about my mothers OnePlus 5T. It doesnt respond to anything I do to it. It won't turn on, it won't boot in to Qualcomm download mode nor in to recovery or fastboot. The device has not been tempered with before, I dont think my mother knows how to flash it
So, this is what exactly happened, according to my mother.
She woke up, got on to facebook and has been browsing a little, untill suddenly the phone turned black, gave her a warning in the left upper corner of the screen, which said something like; warning, do not share personal info. Or something like that, after that, it gave the logo of OP, and then never got a response from it ever since.
It does not react to pressing buttons, nothing, no led nothing. Charger doesnt give any response, neither did my pc with the qualcomm drivers installed.
So currently it is literally a brick, and I hope somebody can help me. I have a lot of background with flashing etc, so if the answer is really complex, no problem!
Thanks in advance,
Dane
Click to expand...
Click to collapse