Develop Bugs

Help required, possibly bricked?

Hi all,
Hopefully you can help me, i have just installed the latest radio and Modaco ROM (this isn't the first time i've did this).
After installation i got what looked like an image of a drive and an arrow, i assume this meant it couldnt find the boot image. I then tried a couple of times to reboot holding the home key but now i cant even switch it back on... even on charge the light isn't coming on
Any help would be gratefully appreciated
Thanks
GF

When the arrow and drive comes up, you're meant to leave your phone well alone, it means it's flashing something (usually something important!)
If your phone doesn't turn on, sounds like you've made a full hard brick, nothing you can do but see if you can get it repaired.

Gutted, cheers

Can you pull the battery and get into fastboot?

Breakthecycle2 said:
Can you pull the battery and get into fastboot?
Click to expand...
Click to collapse
Not sure what that is? I've tried the various power+key sequences
Thanks

GaelForce said:
Not sure what that is? I've tried the various power+key sequences
Thanks
Click to expand...
Click to collapse
Sometimes, if the Hero does not switch on, taking the battery out and reinserting it might reboot it. But if the charge light is not coming on, then it might not work. Worth a try though.
Did you get the phone through a network? If it is under warranty, you can just play dumb and return the phone. They probably won't even know that you have modded the phone. My battery stopped holding charge and would not switch on unless it was plugged in to the mains. When I returned it, they changed my battery and the main board!?! When I called them up, the service centre told me "there was some dust on the main board, so we changed it".
Not smart enough to figure out that I had rooted the phone and was running Modaco at the time.
Samsom
PS I am with T-mo BTW.

docsamsom said:
Sometimes, if the Hero does not switch on, taking the battery out and reinserting it might reboot it. But if the charge light is not coming on, then it might not work. Worth a try though.
Did you get the phone through a network? If it is under warranty, you can just play dumb and return the phone. They probably won't even know that you have modded the phone. My battery stopped holding charge and would not switch on unless it was plugged in to the mains. When I returned it, they changed my battery and the main board!?! When I called them up, the service centre told me "there was some dust on the main board, so we changed it".
Not smart enough to figure out that I had rooted the phone and was running Modaco at the time.
Samsom
PS I am with T-mo BTW.
Click to expand...
Click to collapse
Worked a treat, got a doorstep exchange today
Thanks

[Q] Reboots, not able to boot, 5 vibrates.

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.

Quick Q: Jedi Mind Trick Brick? Phone unresponsive;Veteran User

phone wont boot at all after install. wont even go into download mode.
phone worked perfectly when i was running beastmod 3.0 i believe. i stayed inactive ever since.. i made sure i could get into download right before i went ahead to the jedi mind trick update. like i said, everything worked perfectly. tested out all button combos for recovery and download mode (even did the pulling the battery and plugging the usb method) with success before i updated. yes phone was on 100% battery . it was on the charger the whole night.
i logged back on because i felt like updating and read about Jedi Mind Trick. installed TWRP recovery as well a few days ago. i wiped everything of course, flashed, repaired , reboot. I got a black screen for awhile and let it sit for 30min. no response, so i pulled the battery and tried to turn on. phone wouldnt turn on so i tried to get into download mode and failed. phone is completely unresponsive.
what to do? i'm just stumped now. i was inactive, but by no means am i new to this.

Are you sure your battery has a good charge?

brian_v3ntura said:
phone wont boot at all after install. wont even go into download mode.
phone worked perfectly when i was running beastmod 3.0 i believe. i stayed inactive ever since.. i made sure i could get into download right before i went ahead to the jedi mind trick update. like i said, everything worked perfectly. tested out all button combos for recovery and download mode (even did the pulling the battery and plugging the usb method) with success before i updated. yes phone was on 100% battery . it was on the charger the whole night.
i logged back on because i felt like updating and read about Jedi Mind Trick. installed TWRP recovery as well a few days ago. i wiped everything of course, flashed, repaired , reboot. I got a black screen for awhile and let it sit for 30min. no response, so i pulled the battery and tried to turn on. phone wouldnt turn on so i tried to get into download mode and failed. phone is completely unresponsive.
what to do? i'm just stumped now. i was inactive, but by no means am i new to this.
Click to expand...
Click to collapse
I see by no means are you a rookie but I will ask have you tried to plug your phone in to your pc and see if it makes a noise and recognizes it. Honestly I would assume prior to posting you probably tried everything so it may be unfortunate but you may have to send to JTAG or go through insurance.
Cant see a rom doing that to your phone? Unless you had some hardware failure

Have you tried using a usb jig to force it into download mode?

davwman said:
Are you sure your battery has a good charge?
Click to expand...
Click to collapse
yep. battery was just fine. never had had a problem. even popped in my spare and dad's battery to make sure it wasnt a battery related issue.
CMDann said:
Have you tried using a usb jig to force it into download mode?
Click to expand...
Click to collapse
yes. i made my own actually. it was the first thing i used to make sure i could get into download mode,with success, before the flashing process.
playya said:
I see by no means are you a rookie but I will ask have you tried to plug your phone in to your pc and see if it makes a noise and recognizes it. Honestly I would assume prior to posting you probably tried everything so it may be unfortunate but you may have to send to JTAG or go through insurance.
Cant see a rom doing that to your phone? Unless you had some hardware failure
Click to expand...
Click to collapse
after flashing:
1) i did plug into 2 laptops(windows 7) and a 2 desktop(vista and xp). "tries" to install the drivers and then makes the fail noise.
2) tried to use the SGS2 toolkit as well.
prior to flashing:
1) phone mounted successfully to 1 laptop and 1 desktop. thats all i tried it on. i used my laptop to transfer the flash zips and my desktop to back up my internal memory since i havent done it in awhile.
2) everything just worked. my only gripe was that my phone was still on gingerbread and decided to update to to ICS
i'm just puzzled myself. i did try everything that i could think of to at least get the phone to turn on somehow. i even went back to sleep and put the phone on the charger hoping the phone would just magically turn on itself >_<
i know i've been super inactive for awhile, but it only took me a few of days to get myself back up to speed and catch up on the new information.

Also would like to add that i used 3 samsung micro usb cords(2x sgs2 and vibrant),jig,2htc cords(hd3 and mytouch 4g) and even my old nokia micro usb. No success but at last the laptop is detecting the phone when trying to install drivers and then fail.
I know i did not download thw wrong rom either its not like i go off to other phone sub-forums to look for stuff.

Chalk this up to bad luck and move on. Its not the ROM. Period. Like pmtr3 said, 20,000 downloads plus, and your the first one to say this happened. Sorry to hear about your phone.
Sent from JMT Goodness

Have you tried pulling the phones battery out sim and micro sdcard... then hold the two volume buttons then olug in the usb and then place the battery while still holding the volume buttons? (Open up odin before trying)
Sent from my SGH-T989 using xda app-developers app

LoopDoGG79 said:
Chalk this up to bad luck and move on. Its not the ROM. Period. Like pmtr3 said, 20,000 downloads plus, and your the first one to say this happened. Sorry to hear about your phone.
Sent from JMT Goodness
Click to expand...
Click to collapse
i have no clue what happened. maybe some kind of freak hardware failure. i used to be so into flashing,but decided to use my phone as a phone instead of always flashing.
i did call TMo for a warranty replacement, but the SGS2 is supposedly on back order -____- they recommended an alternative device,but not details yet until they get back to me.
this isnt my first SGS2. i got mine during TMo's firesale on Nov. 19th. 3 days later, i exchanged under the 14day grace period it due to horrible data drops and robotic voice. The phone was stock at the time. Data drops made it impossible to download-on-the-go for whatever the professors assigned . 2nd one worked like a charm.
phreshjoker said:
Have you tried pulling the phones battery out sim and micro sdcard... then hold the two volume buttons then olug in the usb and then place the battery while still holding the volume buttons? (Open up odin before trying)
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
yes....i'm cutting my loses and doing a warranty exchange. Hopefully an SGS3 due to having 2 SGS2's. Usually,they will upgrade to the next device if your current device is not available and you had 2 replacements.
i'm trying to find my Good ol' G1 that never really failed me. i used to like using it from time to time whenever i had my vibrant just for nostalgia purposes.

[Q] Samsung Galaxy S3 Completely Dead

Forum Noob here, I was using my Galaxy S3 (Wind) and all of a sudden the screen went black and it turned off. Something similar had happened a couple hours before and the phone wouldn't turn on through the power button so I simply took out the battery and put it back in and it worked. Then when it happened for a second time I tried the same thing but to no avail the phone stayed dead.
So far I've tried:
Using another GS3 Stock Battery
Tried getting into download and recovery mode
Tried charging it (I do know that the battery is charging since I checked it on another phone. The red light is not on but it turns on when I take out the battery and then plug it in. After 20-30 seconds of battery insertion the red light goes away and is completely unresponsive all that time)
Tried Keeping the battery out of the phone for a couple of hours (Suggested by a friend)
Also Tried connecting it to a pc, and it only connects when I keep the battery out. When it finally connects it tries to install drivers for "QHSUSB_DLOAD" but fails.
I have no idea what's happening to my phone and I would like to get it fixed as soon as possible. After some searches I've narrowed down to either a Hard Brick or a Sudden Death Syndrome but it doesn't completely match with all the characteristics of either problem. I greatly appreciate any help and I would like to know what exactly the problem is and what my best viable option.
Thank you.

Don't know why, but it's bricked. But you mentioned it started working at one point when you put the battery in. So if you take it out, then put it back, does the phone automatically try to turn on by itself?
Qhsusb is a definite indicator of a brick, but if your power button is faulty it may have caused the brick by rebooting over and over without ever fully booting up. Basically causing corruption somewhere.
There's a debrick thread stickied in development, but if the button is also faulty it may not help for long.
Sudden death is only describing a problem the international models had after release. Doesn't apply to ours in that way.
Sent from my SGH-T999 using Tapatalk

DocHoliday77 said:
Don't know why, but it's bricked. But you mentioned it started working at one point when you put the battery in. So if you take it out, then put it back, does the phone automatically try to turn on by itself?
Qhsusb is a definite indicator of a brick, but if your power button is faulty it may have caused the brick by rebooting over and over without ever fully booting up. Basically causing corruption somewhere.
There's a debrick thread stickied in development, but if the button is also faulty it may not help for long.
Sudden death is only describing a problem the international models had after release. Doesn't apply to ours in that way.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Yeah, when you put the battery back in it doesn't do anything. Also I don't think the power button is faulty I mean it's been working fine for the last year didn't really give me any problems.

TheSoldierDude said:
Yeah, when you put the battery back in it doesn't do anything. Also I don't think the power button is faulty I mean it's been working fine for the last year didn't really give me any problems.
Click to expand...
Click to collapse
Only reason I suspect the power button is you mentioned you couldn't get it to turn on using the button, but removing/replacing the battery worked. And it can work perfectly and then fail out of nowhere. So goes when you have plastic parts! But lots of people have had issues with this button recently.
Wasn't trying to convince you that was the problem, just letting you know it's a potential culprit.
But if you think it's ok, then try to use KAsp3rd's debrick thread and see if that gets you going again.
Sent from my SGH-T999 using Tapatalk

If it's completely dead then it's most likely hard bricked. My phone just got hard bricked so you will need to buy a JIG of Ebay. If it's not that then try reflashing your ROM or re rooting it. If none of that works then just take your phone in too wherever you bought it from and have them fix it. Oh a JIG is a small USB that will re write it and force it into download mode.

Your phone in stock rom ? If stock rom that is suddenly dead mean bad emmc on the logic board with my experience.

ssingh0247 said:
If it's completely dead then it's most likely hard bricked. My phone just got hard bricked so you will need to buy a JIG of Ebay. If it's not that then try reflashing your ROM or re rooting it. If none of that works then just take your phone in too wherever you bought it from and have them fix it. Oh a JIG is a small USB that will re write it and force it into download mode.
Click to expand...
Click to collapse
Since they are seeing the QHUSB_DLOAD (which is technically a hard brick) a simple USB jig wouldn't work, however they can attempt to use my recovery method. It's at no cost and just takes some time and reading.

When you attempt to restart your phone, does anything come up at all? I've been having issues over the past week, culminating in a device that won't charge, and won't complete a boot sequence. I get as far as the Samsung splash screen (and occasionally the first snippet of the ROM's splash screen) and then....a black screen and a quick buzz. Then the whole process repeats. In my case, I believe it's the power button.

P06o said:
When you attempt to restart your phone, does anything come up at all? I've been having issues over the past week, culminating in a device that won't charge, and won't complete a boot sequence. I get as far as the Samsung splash screen (and occasionally the first snippet of the ROM's splash screen) and then....a black screen and a quick buzz. Then the whole process repeats. In my case, I believe it's the power button.
Click to expand...
Click to collapse
Remove and reinsert battery. If it turns on by itself, you are probably right about the button.
Sent from my SGH-T999N using Tapatalk

You're Right I believe
tomy1986.nt said:
Your phone in stock rom ? If stock rom that is suddenly dead mean bad emmc on the logic board with my experience.
Click to expand...
Click to collapse
I went to a Samsung service center and they told me the motherboard had to be replaced.. I did some searching and found this http://forum.xda-developers.com/showthread.php?t=2178484
I've come to the conclusion that it was indeed a bad emmc (Yes, I was using stock ROM).. Any thoughts?

Nope
P06o said:
When you attempt to restart your phone, does anything come up at all? I've been having issues over the past week, culminating in a device that won't charge, and won't complete a boot sequence. I get as far as the Samsung splash screen (and occasionally the first snippet of the ROM's splash screen) and then....a black screen and a quick buzz. Then the whole process repeats. In my case, I believe it's the power button.
Click to expand...
Click to collapse
Nothing happens at all.. its completely dead, simply a paper weight.. a very bad one of sorts

TheSoldierDude said:
I went to a Samsung service center and they told me the motherboard had to be replaced.. I did some searching and found this http://forum.xda-developers.com/showthread.php?t=2178484
I've come to the conclusion that it was indeed a bad emmc (Yes, I was using stock ROM).. Any thoughts?
Click to expand...
Click to collapse
If it indeed is a Bad EMC then it should be In Warranty Repair as Samsung does offer that. If you didn't have Insurance that is.

Thank you
Perseus71 said:
If it indeed is a Bad EMC then it should be In Warranty Repair as Samsung does offer that. If you didn't have Insurance that is.
Click to expand...
Click to collapse
Nope.. xD 3 months off warranty, and yes I got it repaired from Samsung.. Motherboard was replaced, $300.. :|
Thanks to everyone helping out though
I can't believe I didn't know about these forums before :good:

Samsung Galaxy S3 died-black screen
my s3 gone black,its not getting turned on.there was red light(indicator) for some time before i tried to restart but when i tried to switch on. it's completly died,i am not getting any display.i have purchased in UK, unlocked using it now in India.some guys told me it would because of motherboard issue (if i replace motherboard it in India will it work normal,is there any possibility?)how to fix it?please give me some solutions.

screen not working
Hi all. In my s3 the red light is flashing fast. Also the screen is black but it works. Also the phone works and I can receive phone calls. Every few minutes the screen turns on for a sec and goes off again. I can feel the vibration when I touch the screen. Pkease help me.
Thanks

hard bricked
same issue, totally dead, short red light when connecting usb be, tried this http://forum.xda-developers.com/showthread.php?t=2439367 but nothing happens when holding power button, any possible help?

syben7 said:
same issue, totally dead, short red light when connecting usb be, tried this http://forum.xda-developers.com/showthread.php?t=2439367 but nothing happens when holding power button, any possible help?
Click to expand...
Click to collapse
Answered in the other thread. Just fyi, its best to only ask your question once, in one thread. It gets messy and confusing when different things are mentioned/attempted in different threads for the same issue.
Sent from my SGH-T999 using Tapatalk

DocHoliday77 said:
Answered in the other thread. Just fyi, its best to only ask your question once, in one thread. It gets messy and confusing when different things are mentioned/attempted in different threads for the same issue.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
yea, sry about that, was actually trying to get 10 posts in so that i could go post in the dev thread concerning this, gonna check out the method you sent, thanks a ton man!

STUCK
Well my s3 (us cellular r530u), has no boot but has a red led without the battery. Is there a debricking procedure? And if so..where can i find a debrick file.

There is for us. But you need to be in Sprints forums. Theres nothing for your device here, and I dont know what they have over there. Good luck though!
Sent from my SGH-T999 using Tapatalk

Pixel 3 XL shutdown suddenly won't restart

So just now my Pixel 3 XL just suddenly shutdown and won't restart
No matter what button combo I push -- nothing !
No matter how long I push the buttons -- nothing !!
Any suggestions??
I'm assuming hardware but I wasn't doing anything -- just walking through the grocery store -- came out -- dead !

jcrompton said:
So just now my Pixel 3 XL just suddenly shutdown and won't restart
No matter what button combo I push -- nothing !
No matter how long I push the buttons -- nothing !!
Any suggestions??
I'm assuming hardware but I wasn't doing anything -- just walking through the grocery store -- came out -- dead !
Click to expand...
Click to collapse
I am having the same issue with my XL as well. Will only reboot if you boot into recovery ( vol down and power ) then reboot and continue where you left off. No fix yet.

xmattisi said:
I am having the same issue with my XL as well. Will only reboot if you boot into recovery ( vol down and power ) then reboot and continue where you left off. No fix yet.
Click to expand...
Click to collapse
Unfortunately mine won't even boot into recovery

jcrompton said:
Unfortunately mine won't even boot into recovery
Click to expand...
Click to collapse
I am sorry to hear that.

jcrompton said:
Unfortunately mine won't even boot into recovery
Click to expand...
Click to collapse
That definitely sucks! RMA...RMA...RMA! :good:

Badger50 said:
That definitely sucks! RMA...RMA...RMA! :good:
Click to expand...
Click to collapse
I went through the RMA process. Due to the fact I did not buy my phone from the Google Store they will only have me send in my phone for the process which can take 10-12 business days. Unacceptable. They did say if I bought it from them they would mail me a replacement and I could mail the bad one in but since I bought it from BestBuy I am not allowed.. GGnoRE google. To be honest, after that I am done. I am probably going to replace this phone and not buy another Google phone again.
Thank you for your support and help.

xmattisi said:
I went through the RMA process. Due to the fact I did not buy my phone from the Google Store they will only have me send in my phone for the process which can take 10-12 business days. Unacceptable. They did say if I bought it from them they would mail me a replacement and I could mail the bad one in but since I bought it from BestBuy I am not allowed.. GGnoRE google. To be honest, after that I am done. I am probably going to replace this phone and not buy another Google phone again.
Thank you for your support and help.
Click to expand...
Click to collapse
Don't blame you a bit my friend. Problem is, what to buy that doesn't have it's problems as well? I wish you well in your search :good:

xmattisi said:
I went through the RMA process. Due to the fact I did not buy my phone from the Google Store they will only have me send in my phone for the process which can take 10-12 business days. Unacceptable. They did say if I bought it from them they would mail me a replacement and I could mail the bad one in but since I bought it from BestBuy I am not allowed.. GGnoRE google. To be honest, after that I am done. I am probably going to replace this phone and not buy another Google phone again.
Thank you for your support and help.
Click to expand...
Click to collapse
Why don't you take it back to bestbuy?

jd1639 said:
Why don't you take it back to bestbuy?
Click to expand...
Click to collapse
BestBuy only has a 14 day return policy. Even when they do run the return if its not covered under a protection plan which is for physical damages ( $200 deducible to get the replacement ). On top of that they also have a restocking fee lol. When you try the return under the manufacturer warranty it tells me to Call Google.

I haven't even fully remembered what I lost but this has confirmed one of my concerns about a device that doesn't have an SD card .... Basically either Pixel I've lost everything that doesn't get backed up to the cloud
So I gotta get better at backup routine or get a device with an SD card

I believe titanium might be the way to go. https://www.titaniumtrack.com/titanium-backup.html

Well for sure TiBu would be helpful for your apps and some of the app says if you were doing backups online
I'm mainly taking about the scores of files that were accumulated in out device that may not get backed up ..... Where on a device with an SD card, I use the card mainly to store things.

Dont know if this is related, but i did a restore of a nandroid and when it finished the phone turned off all on its own. When i went to power it back on nothing would happen. Even trying to boot to recovery or fastboot did nothing. When i plugged it in no charging indicator, and it wasnt recognized by a pc. I thought it was bricked for sure. So sure i did a warranty claim. Well while boxing it up to send in i hit the power button and noticed a little white battery icon flash for a second then disapear. This was the most i got it to do since it shut it self off. So i went through the whole process again of trying to power it on again with no luck. Then i got an idea from back in the day i think it was with the droid incredible maby, to hold vol down and power while plugging it in. When i did this i again saw the little white battery icon flash on the screen. So i kept holding vol down and power while plugging and unplugging the power cord over and over again. About the sixth time plugging it in, it booted to fastboot. I screamed and jumped around like a little school girl i was so happy lol. Anyways i flashed the feb ota and it booted right up like it was brand new. Hopefully this may help someone else who thinks their phone is bricked.
Sent from my [device_name] using XDA-Developers Legacy app

cmlusco said:
Dont know if this is related, but i did a restore of a nandroid and when it finished the phone turned off all on its own. When i went to power it back on nothing would happen. Even trying to boot to recovery or fastboot did nothing. When i plugged it in no charging indicator, and it wasnt recognized by a pc. I thought it was bricked for sure. So sure i did a warranty claim. Well while boxing it up to send in i hit the power button and noticed a little white battery icon flash for a second then disapear. This was the most i got it to do since it shut it self off. So i went through the whole process again of trying to power it on again with no luck. Then i got an idea from back in the day i think it was with the droid incredible maby, to hold vol down and power while plugging it in. When i did this i again saw the little white battery icon flash on the screen. So i kept holding vol down and power while plugging and unplugging the power cord over and over again. About the sixth time plugging it in, it booted to fastboot. I screamed and jumped around like a little school girl i was so happy lol. Anyways i flashed the feb ota and it booted right up like it was brand new. Hopefully this may help someone else who thinks their phone is bricked.
Click to expand...
Click to collapse
Absolute unbelievable!!!
Now I'm thankful but maybe even more frustrated
This worked!!!!!
After an hour on the phone with Google support (I obviously knew more than they did) ..... Worse yet with an RMA device in hand ...... My phone is back up and running!!
Now... Should I send the reburbed RMA back or the original phone back? Lol

Awesome glad it worked. Im not sure if this is some sort of issue with the hardware that will eventually happen again, or just a weird software fluke thats over with for good. Its been about a week so far and all is well. I cancled the return and kept it.
Sent from my [device_name] using XDA-Developers Legacy app

cmlusco said:
Awesome glad it worked. Im not sure if this is some sort of issue with the hardware that will eventually happen again, or just a weird software fluke thats over with for good. Its been about a week so far and all is well. I cancled the return and kept it.
Click to expand...
Click to collapse
The DINC! What a great device and learning tool that was! :good::good:

Thread cleaned. Keep it civil.
The lack of respect needs to stop. All users know there will be risks when doing anything to a phone post bootloader unlock.