Related
Stuck at "Samsung Galaxy" boot screen, cant get into bootloader, computer wont detect
Hey everyone this has been a huge hassle for me for the last few days and was hoping someone could help me. I have had to resort to using my HTC Legend...which I love but it doesnt have what I need.
I was in recovery the other day trying to load a custom rom through the CWM and I went through and accidentally hit "format system". I couldn't cancel the process so I knew something bad was going to happen....I reboot the phone and for the last 3 days I have had it plugged into the Usb charger with no luck of booting, it has been stuck at the "Samsung Galaxy S 19000M" boot screen and no further. I took the battery out and tried rebooting it after a few minutes. No luck with this either, still stuck at the Samsung screen. I CAN get into "DOWNLOAD MODE" but I CAN NOT get into recovery/bootloader (hold volume up/home button/power button).
I have put it into download mode and and plugged it into the computer (I am running Windows 7 64-bit) and it will not detect it. I have all of the correct drivers, I know this as I have a friend who owns the exact same phone and my computer detects it just fine. Odin nor ADB will detect that there is anything AT ALL plugged into the computer. It does not even come up as, "android device", or "storage", there is nothing, nota, it is as if the phone isn't even plugged in. It will not detect in "download mode" nor while its stuck at the "Samsung Galaxy S" screen, and yes I have tried a different USB cable, and still nothing..
I am quite capable with electronics but I cannot find anything on the internet as of what to do. Is there anything that I could load on an external SD card that would force the phone to flash a ROM with new kernal and modem? I think the phone is empty that is why it is not booting, as if there is nothing to load on the phone. Is there anything at all that anyone can think of??? I am completely stuck. I wanted this phone to last until the Samsung Galaxy S 2 was released here lol.
I'm with Virgin Mobile Canada. Thanks!
Cant you get it into Recovery mode?
Have you tried heimdall?
You will have to follow the instructions coming with it to the letter (about installing some custom USB-driver).
Herman76 said:
Cant you get it into Recovery mode?
Click to expand...
Click to collapse
Hey herman, "I CAN get into "DOWNLOAD MODE" but I CAN NOT get into recovery/bootloader (hold volume up/home button/power button)."
profalbert said:
Have you tried heimdall?
You will have to follow the instructions coming with it to the letter (about installing some custom USB-driver).
Click to expand...
Click to collapse
Hey, I will search for that right away and let you know how it turns out. Thank you!!
well if you have download mode then dont panic.
just flash a 3 file firmware along with pit file and re-partition and you will be fine
azzledazzle said:
well if you have download mode then dont panic.
just flash a 3 file firmware along with pit file and re-partition and you will be fine
Click to expand...
Click to collapse
How can I flash any firmware if my PC will not detect the phone? When I plug the phone in there is nothing. Odin doesn't detect the phone, Keis doesn't detect the phone, ADB does not detect the phone, and I just tried Heindall, and it does not detect the phone..... Maybe the actual hardware for the USB plug in is faulty in its self, in which case I am screwed.
Galaxy19000M said:
How can I flash any firmware if my PC will not detect the phone? When I plug the phone in there is nothing. Odin doesn't detect the phone, Keis doesn't detect the phone, ADB does not detect the phone, and I just tried Heindall, and it does not detect the phone..... Maybe the actual hardware for the USB plug in is faulty in its self, in which case I am screwed.
Click to expand...
Click to collapse
i see..... i only read the last 2 posts and im always telling people off for not reading properly
have you tried the obvious steps such as
Un-install - Re install Kies
Run Odin as administrator
Tried Alternative USB port - direct into the PC motherboard
Finally a different PC all together
hope you can get it workin hate to see another broken SGS
azzledazzle said:
i see..... i only read the last 2 posts and im always telling people off for not reading properly
have you tried the obvious steps such as
Un-install - Re install Kies
Run Odin as administrator
Tried Alternative USB port - direct into the PC motherboard
Finally a different PC all together
hope you can get it workin hate to see another broken SGS
Click to expand...
Click to collapse
I have tried, uninstall-re install of kies, run odin as admin, alternate usb port, anddd I tried plugging it into my laptop...no luck...this absolutely driving me nuts because I know the phone cant be bricked, if I can get into download mode I SHOULD be fine but for some strange reason the phone seems to be undetectable...ahhhhhhhhhhhh if only there was just some way to access the internal storage or a program that would force a flash through an external SD....
I am going to try loading Ubuntu on my computer on one of my HDD and see if it will detect the phone. I am assuming this is my last option and I have high hopes as Ubuntu detects almost anything...I will update...if it doesnt work I might be looking into taking apart the phone its self and intalling a new USB plug in on the phone motherboard...
im not sure of any other steps
last resort.... have you tried another USB cable ? like your friends cable that he uses for his phone ?
EDIT: if i was you i WOULD NOT take the phone apart.... if you do and it does not work, your warranty will be void,
at least if you cant get it working you can send it off for repair and blame kies, you will have a good chance of getting it fixed by samsung than you would yourself
azzledazzle said:
im not sure of any other steps
last resort.... have you tried another USB cable ? like your friends cable that he uses for his phone ?
Click to expand...
Click to collapse
yeah lol like I said in the first post I tried a different USB cable all together.
I have two HTC Legends, tried both cables from them, plus the OEM cable that came with the SGS
azzledazzle said:
im not sure of any other steps
last resort.... have you tried another USB cable ? like your friends cable that he uses for his phone ?
EDIT: if i was you i WOULD NOT take the phone apart.... if you do and it does not work, your warranty will be void,
at least if you cant get it working you can send it off for repair and blame kies, you will have a good chance of getting it fixed by samsung than you would yourself
Click to expand...
Click to collapse
I dont know if it has been opened already by someone else. I bought the phone for $180 CAD from a sort of "2nd turn" site. As in it was being sold as is. The phone problem reported by them was that the USB connectivity was not working. When I originally got the phone from them everything was working correctly, except the USB connectivity like it stated. It came ROOTED and loaded with the leaked version of Froyo before it was out so I automatically assumed that was causing the USB problems. I got around to changing the ROM with a reported working USB using CWM. But, still no luck with USB connectivity. I just dealt with the problem and flashed everything through CWM. Which led me to this...ugh
Is there supposed to be a warranty seal behind the battery cover? Over the screws like there usually is? Cause I see nothing..
thats not good news.
there is no warranty sticker, but samsung could find out if the phone has been opened.
It depends on the actual repair guy, to be honest, samsung will have 100's of phones to repair daily, the majority just get passed on - flashed - wiped - boxed and sent back to the owner.
however if some (P)Rick is having a bad day and wants to find out why the phone is in for repair, and he finds out its been opened up, or its had custom firmware, then he can refuse to fix the phone or send it back to you with a bill included lol.
so you have to have a good excuse incase the worst happens.
if you dont fancy your chances and you feel capable of replacing the USB yourself then hey go for it !!
azzledazzle said:
thats not good news.
there is no warranty sticker, but samsung could find out if the phone has been opened.
It depends on the actual repair guy, to be honest, samsung will have 100's of phones to repair daily, the majority just get passed on - flashed - wiped - boxed and sent back to the owner.
however if some (P)Rick is having a bad day and wants to find out why the phone is in for repair, and he finds out its been opened up, or its had custom firmware, then he can refuse to fix the phone or send it back to you with a bill included lol.
so you have to have a good excuse incase the worst happens.
if you dont fancy your chances and you feel capable of replacing the USB yourself then hey go for it !!
Click to expand...
Click to collapse
Well thank you for all the help. I am going to try installing Ubuntu first and see what happens, I have never had any driver issues with that OS EVER so if its detectable, Ubuntu will be the one to detect it. If that doesn't work I might take my chances and send it in. And if like you said that one person decides to screw me over, they at least have to send it back to me, in which case I will just open it myself and change the USB plug in like I said. (which might not even be the problem...)
Is there anyway to tell on the out side without opening it if it has indeed been opened before???
erm..... i dont think so, but i dont know what measures samsung have took to find this out.
if it was me the obvious things i would look for is, damaged screw heads and scratches down the sides - where the casing has been prised open. other than that i would not know what to look for
either way, i hope u get it fixed
azzledazzle said:
erm..... i dont think so, but i dont know what measures samsung have took to find this out.
if it was me the obvious things i would look for is, damaged screw heads and scratches down the sides - where the casing has been prised open. other than that i would not know what to look for
either way, i hope u get it fixed
Click to expand...
Click to collapse
Well I sent my phone in to Samsung last week and I just got it back today! I opened it up and I guess the problem with the phone was pretty bad lol they just gave me a new phone, I was thinking it was refurbed but it said right on the repair receipt "condition=NEW" I am extremely happy.
That aside, do you know if you can use the SGS II if it is unlocked in Canada?
Hi everybody,
a friend of mine got his HTC One (black) yesterday and rooted it. He flashed a proper custom ROM on it which I and another one of my work buddy use as well without any issues (InsertCoin). No further flashes done, no other custom kernels, no S-Off, no SuperCID. Just unlocked Bootloader and custom ROM.
He let the device run dry yesterday evening so it shut off itself automatically. He put it on his charger, the phone turned on, he did some surfing and installing apps from the market and set up his alarm. The phone charged over night and he was also able to switch off the alarm this morning.
He got ready for work, got into his car and wanted to switch on the screen on the one for some good tunes. But the screen stayed black.
When I arrived at work, he was a little upset and panicked a little. I thought I was able to recover the device.
After plugging it in to my work computer, the device manager just shows a unknown device called "QHSUSB_DLOAD" so I went to google and looked it up..
Weird thing is: QHSUSB_DLOAD wasnt seen yet on the HTC One (M7) as far as I can see it and it was pretty bad on the HTC One S. It means "Qualcom High Speed USB Download Mode" and on the One S as well as on the Nexus 4 this devices showed up after the bootloader got damaged or the device got stuck in that mode for good.
When plugging the device in (USB / Wall charger) the charging LED doesnt turn on at all, the capacitive buttons dont start to blink while holding down the power button as well.
This thing seems to be gone for good.
But aint it the way that we dont even have any access to the bootloader if its not an official update from HTC? Signature check and stuff? Since the device was rooted, no OTA updates were able to arrive at all. He told me that he didnt try to flash anything after we flashed the custom ROM.
Any advice on that?
Did you even try booting the device first thru hboot/bootloader or holding the power button to force a restart? If you did try connecting the device while on QHSUSB_DLOAD and execute a compatible RUU on your PC. RUU uses android's download mode to flash the ROM so it should be repaired by an RUU.
Already tried, no luck. Tells me the device has not been found.
I am sorry to hear that, man, but from the looks of it your friend now has a paperweight. I'd take it to an HTC service center and hear what they have to say regarding this; of course it will no longer be covered under warranty, but maybe they can fix it for you for a price or something.
Are you sure RUU can't find the phone? If it can't then I guess only a JTAG box can fix it so either send it to HTC for repair or have someone who knows JTAG fix it.
Try4Ce said:
Already tried, no luck. Tells me the device has not been found.
Click to expand...
Click to collapse
I saw this issue on my friend's GS3 once. It was hard bricked and there was no way to recover from what I read (at least on the GS3). I know I saw a thread somewhere here in this forum about the same issue and someone linked to a Sensation thread where there was a way to fix it but I'm not sure if it would apply to the One
Same problem - but the phone magically fixed itself!
I had the exact same problem with my HTC One as described in OP...
My alarm went off in the morning and I set off for work, my battery was low but I thought that I would just charge it when I got to work. I was playing a game (Dungelot) whilst waiting for my bus and was receiving pop up messages about low battery. When it got to 4% left I decided that I would finish the level then close the game down, but as I was just about to finish, the phone went blank...I assumed that I had naturally used up all the battery life and although peeved that I had probably lost my progress in the game, wasn't too bothered.
I got to work and plugged my phone in to charge on my computer. The computer wanted to search for QHSUSB_DLOAD drivers but I thought this must be what it does when my phone isn't switched on and it finds the device. I cancelled the search prompt and tried to switch my phone on...nothing happened.
I tried for the rest of the day, trying to force shut down the bricked phone by holding power in for 30 secs, trying to power into boot mode etc...everything! But the phone would not switch on and the only response I got from it was a little orange LED every now and again and the QHSUSB_DLOAD prompt.
After googling the prompt - I found myself here and REALLY began to sh*t my pants! I've only had the phone less than a month and felt I was tech-savvy enough to flash my phone with a new ROM (Android Revolution HD) to try and get rid of some of the bloatware. I had flashed a new ROM successfully a coupld of weeks before and everything had been fine up that point.
I went home depressed but throught i'd try to plug my phone into a proper mains charger rather than my work's old USB cable (that came with my previous HTC Desire Z) I was going to try a long night of searching the net to try and find a way where I could at least recover the photo's, Zoe's and vids of my new born son but had such a headache that I gave up and went for an early night.
I was woken unexpectedly the next morning by my phone alarm going off! I stopped the alarm and the home just went to Home screen as normal! I don't know how or why these events happened...whether it was the flashed ROM, the game I was playing, the battery running out before the phone could shut down properly, the old USB cable in my work not charging but detecting the device or a combination of all of those, but so far, the phone jumped back into life with the alarm after being charged in the mains all night!
Thought i'd share as it may just help someone else out there who encounters this!
Some phones have miraculously come back from QHSUSB_DLOAD with no explanation of why. Other than that it usually means a hard brick. You can send it to HTC, they will charge you and replace the main board, from what I've heard.
Sent from my HTC One using XDA Premium 4 mobile app
---------- Post added at 08:20 PM ---------- Previous post was at 08:20 PM ----------
Also, its not unheard of. I've seen it happen a few times in these forums.
Sent from my HTC One using XDA Premium 4 mobile app
I wonder if having your alarm set saved you. This phone will actually power itself on so as not to miss an alarm.
Sent from my HTC One using xda app-developers app
lampel said:
I wonder if having your alarm set saved you. This phone will actually power itself on so as not to miss an alarm.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Hi Try4Ce,
I am facing the same issue. If your friend's phone is fixed, can you share with me how the fix happened?
Many thanks in advance.
Krishna Menon.
same here
Any idea how to fix it?
Delingerb said:
Any idea how to fix it?
Click to expand...
Click to collapse
Jtag or send it to HTC is the only way.
Sent from my HTC One using Tapatalk
My Solution
Had the same Problem.
My Solution was to Download "HTC One (M7) Toolkit" and force Fastboot.
Pushed Power and Volume Down until Screen was Flashing.
Took about 2 minutes and the Phone was rebooting.
I have no idea what was happening. I have no idea if this helps or works for others. But its worth trying.
Sorry for my bad english.
Try4Ce said:
Any advice on that?
Click to expand...
Click to collapse
CoryTallman said:
Some phones have miraculously come back from QHSUSB_DLOAD with no explanation of why. Other than that it usually means a hard brick. You can send it to HTC, they will charge you and replace the main board, from what I've heard.
Click to expand...
Click to collapse
bkmenon said:
Hi Try4Ce,
I am facing the same issue. If your friend's phone is fixed, can you share with me how the fix happened?
Many thanks in advance.
Krishna Menon.
Click to expand...
Click to collapse
Delingerb said:
Any idea how to fix it?
Click to expand...
Click to collapse
This is some kind of mode that is enabled when you hold power on button when the device battery is completely drained. i.e. when you try to turn device on it will not boot up (Special I was connected to usb cable via PC to charge my phone NEXUS 4 when I get into this mode). I saw a similar mode where nvflash commands are executed something like APX(can't recall correctly) with Tegra 4 device (that time also I was connected with a usb cable and charging the tablet when it was completely drained!). A simple solution to quit this issue is DO not Panic and let the device get a little charge. After that boot normally with the power button. In case if it didn't try other modes to enter such as recovery or fastboot reboot commands if your device is getting recognised..
QHSUSB DLOAD means its a hard bricked phone, No amount of messing about with it will fix it, Send it to a service centre, it will probable have to have the motherboard replaced..Sorry
My device entered in QHSUSB_DLOAD mode after the 4.4 ota was installed and 30 minutes later, I was able to turn up the phone. It restarted itself like 5 times and then it was normal. Miracle..
danielr18 said:
My device entered in QHSUSB_DLOAD mode after the 4.4 ota was installed and 30 minutes later, I was able to turn up the phone. It restarted itself like 5 times and then it was normal. Miracle..
Click to expand...
Click to collapse
What do you mean by "force"? What did you do exactly?
My device wouldn't do anything, and it was in QHSUSB_DLOAD . But when I later pushed the power button for a minute, it worked.
danielr18 said:
My device wouldn't do anything, and it was in QHSUSB_DLOAD . But when I later pushed the power button for a minute, it worked.
Click to expand...
Click to collapse
mine spent the night carrying on waking took the charger and the green light for continued access, tried to turn it on but could not. After reading your response, I tried to hold the power button for longer. After 15 seconds the phone rang and the light came on, everything works perfect so far
Today while I was updating firmware phone gone to QHSUSB_DLOAD mode.
I am guessing it's end of road. :crying:
The phone USB port is having problems. It will charge ok wont connect to any laptop in any mode, system, fastboot or recovery. It would be powered by it for a small fraction good enough for it to be detected and then it would stop sending signals. Anybody know any fix for the problem.
Also has anyone sent their rooted phone for repair recently n got it repaired under warranty. Its revone S=off and running trickdroid.
And the error in device manager is USB BOS descriptor failed, "waiting for device", "Device cannot start. (Code 10)"
its probably the voltages messing it up. On connecting the USB it turns on car mode. I was able to briefly get the UMS to work by draining down the battery n connecting to laptop n turning it on. It worked for 2-3 boots and thats it. Its gone again...
charnsingh_online said:
its probably the voltages messing it up. On connecting the USB it turns on car mode. I was able to briefly get the UMS to work by draining down the battery n connecting to laptop n turning it on. It worked for 2-3 boots and thats it. Its gone again...
Click to expand...
Click to collapse
i'm having almost the exact same issues you are. it won't charge unless it's turned off, and it won't connect to my computer at all. sometimes if it's plugged in it'll put itself in car mode. did you manage to get yours fixed?
geometricpiss said:
i'm having almost the exact same issues you are. it won't charge unless it's turned off, and it won't connect to my computer at all. sometimes if it's plugged in it'll put itself in car mode. did you manage to get yours fixed?
Click to expand...
Click to collapse
Same problem here! I made a thread about it but no one answered..
I'm glad it charges though, yesterday when I went to bed it wouldn't charge, but this morning it did. Goes into car mode though and it won't connect to the PC. I think I'm going to bring it back for a repair/replace under warranty.
i fixed it, tried different cables and chargers and finally the charger from my old old moto cliq fixed it, i think it was short at some point of voltage troubles. Fixed since some days now. No more trouble. Also discharge ur battery a few times ( turn of fast boot from settings) and charge all the way to 100 for like 3 days. Also try booting in fastboot mode and connecting to computer see if fastboot usb is connected. took a few days to get it work using different methods. Dont exactly know which one worked
Synestic said:
Same problem here! I made a thread about it but no one answered..
I'm glad it charges though, yesterday when I went to bed it wouldn't charge, but this morning it did. Goes into car mode though and it won't connect to the PC. I think I'm going to bring it back for a repair/replace under warranty.
Click to expand...
Click to collapse
i went in to my t-mobile store to get the warranty replacement process started this morning, but of course the rep saw that i had clockwork installed on it and said he couldn't start the exchange until i got it back to stock. problem is, since it doesn't talk to my computer i can't access adb to reset my tampered/unlock flags and flash the stock recovery. i'm probably gonna have to throw down $175 to asurion to get it replaced for "water damage" or something, unless you guys have any other suggestions i might have overlooked. when i get home i'll try a bunch of different microusb cables to see if i can get any to work, like charnsingh_online mentioned.
just wanted to toss in a quick update in case anybody else is having this problem... a few hours ago someone posted about this same issue on the HTC One subreddit, and i came across a post on the vodafone forums from today describing it as well. i'm getting a little concerned that there might be a bad batch of these phones floating around that are all beginning to fail.
Quick update from me aswell
Yesterday evening it charged like normal, I could even pull the plug out and put it back in without the phone going in car mode, it would still charge.
Now this morning I wanted to try to see if it connects to my PC but that still didn't work. I put it in the charger just to see if it still would charge as easy as the evening before but it went to car mode and I was back at the beginning. Turning the device off and back on didn't resolve it.
Now it does charge again by turning off fast boot (or however it's called, I'm translating from dutch). That made it work again (but for how long?!)
EDIT
My phone finally connected to the PC. The phone still went into car mode but it didn't disconnect after that (like it used to do). I can put my music on my phone now but the phone is alternating between car mode and normal mode.. pretty odd.
I have the same problem. when I turn on the htc one, rainbow screen appears, and does not detect when I connect to PC, I will test the battery discharge, hopefully get lucky,
I'm having the same issue as well. The phone randomly now is throwing itself into portrait mode even when I don't have it plugged in, charging is very intermittent. I'm thinking there's a short somewhere on the circut board but that's only a guess. Do we think this is a hardware issue? At least I'm still on stock if I have to get the phone replaced, but what a PITA with not having an SD card to remove. I'm liking that less and less... grr.
may be a defect, i had a few cells and never appeared a similar problem, I had a galaxy s2, s3, s4, HTC Evo .
I detected car accessory mode, and the strange thing is in Fastboot Mode I can install an official RUU from my PC .
I'm thinking of a theory, it could be that the MISC partition mmcblk0p19 apparently damaged as happened with the HTC Desire for a while now, if reflashing That possibly corrupt partition with a fresh htc ONE, I'm digging into this line of research
http://www.modaco.com/topic/309939-usb-brickrickrolledb0rked-fixed/
OTG mode?
Have had Htc one x + from ebay for a week with no sync or charging problems then yesterday tried to sync but phone crashed/rebooted and asked to send error report to htc for "abnormal restart" or somthing and my pc saw it as an "un-recognised device", since then it is not even seen by my pc and will only charge when off or after restart. The usb is putting out 5v which it should only do in OTG, using an otg cable it powers flash drives ect and see's them. If I can't fix this it will go back to HTC under warranty.
aliendan2 said:
Have had Htc one x + from ebay for a week with no sync or charging problems then yesterday tried to sync but phone crashed/rebooted and asked to send error report to htc for "abnormal restart" or somthing and my pc saw it as an "un-recognised device", since then it is not even seen by my pc and will only charge when off or after restart. The usb is putting out 5v which it should only do in OTG, using an otg cable it powers flash drives ect and see's them. If I can't fix this it will go back to HTC under warranty.
Click to expand...
Click to collapse
Run phone down to 2% battery then checked and no more 5v output from the usb port,turned phone off and still no output voltage from the usb. The phone now charges and connects to my pc as it should. If the battery was removable as it is on other phones it would have done the same as discharging the battery on the htc one x + to give it a propper reset.
geometricpiss said:
i went in to my t-mobile store to get the warranty replacement process started this morning, but of course the rep saw that i had clockwork installed on it and said he couldn't start the exchange until i got it back to stock. problem is, since it doesn't talk to my computer i can't access adb to reset my tampered/unlock flags and flash the stock recovery. i'm probably gonna have to throw down $175 to asurion to get it replaced for "water damage" or something, unless you guys have any other suggestions i might have overlooked. when i get home i'll try a bunch of different microusb cables to see if i can get any to work, like charnsingh_online mentioned.
Click to expand...
Click to collapse
im looking at the same options too man... would have to pay $150 or so to get a brand new one from rogers unless they sent my phone from repair without noticing the unlocked bootloader. from what ive seen theres no way to relock it and flash the stock recovery aaaand RUU without computer connection.
looking at my situation now, im considering never rooting again just because of how screwed you are if something happens to the hardware.
i havent really considered replacing the usb port myself but i guess if i found a store where i live that can do it for a reasonable price, imma go for that.
NIKEstickER said:
im looking at the same options too man... would have to pay $150 or so to get a brand new one from rogers unless they sent my phone from repair without noticing the unlocked bootloader. from what ive seen theres no way to relock it and flash the stock recovery aaaand RUU without computer connection.
looking at my situation now, im considering never rooting again just because of how screwed you are if something happens to the hardware.
i havent really considered replacing the usb port myself but i guess if i found a store where i live that can do it for a reasonable price, imma go for that.
Click to expand...
Click to collapse
Man, you can flash it, if you have the same issue as me, i was able to flash in FASTBOOT MODE, and relock with renove , i used ADB WIFI from MARKET , with this app you are able to send ADB commands , adb shells, etc for REVONE S-OFF, or apply a RUU original, in FASTBOOT MODE your PC should detect connections.
bovoro said:
Man, you can flash it, if you have the same issue as me, i was able to flash in FASTBOOT MODE, and relock with renove , i used ADB WIFI from MARKET , with this app you are able to send ADB commands , adb shells, etc for REVONE S-OFF, or apply a RUU original, in FASTBOOT MODE your PC should detect connections.
Click to expand...
Click to collapse
well last night my computer wasnt picking it up in fastboot mode and i have all the drivers from when i unlocked a couple weeks ago so it should be recognized. but i guess i could atleast try relocking it. and cant i just get rid of root straight from the device?
do you know what command i would have to do through adb, ike fastboot oem lock or is it different?
Amm, have you used renove for s-off?? If you use fastboot oem lock maybe you will get the relocked mark or tampered maybe with Revone you can roll backto a clean locked and s-on state
Enviado desde mi HTC One usando Tapatalk 4
my phone is unlocked but is still s-on. how would i get back to stock 4.1.2 and no root after if i can relock my boatloader using that wifi adb?
look, if you lock the bootloader again being in S-ON, you will receive the label relocked or tampered with this you might void your warranty if you send it, the option that I can think, make S-OFF with REVONE, Read a little this thread : http://forum.xda-developers.com/showthread.php?t=2314582
You can fully use ADB commands via wifi, tested by me, with REVONE you can LOCK the bootloader and back to S-ON , with no trace of having changed either BOOTLOADER or S-OFF/S-ON .
Hi guys, been a bit out of the loop (hospital) but bought an Alpha around sep last year...within 2 months i used a official Maze update (OTA) and it then no longer charges...got onto them via facebook (as there were no official threads for this phone back then) and they sent me this to reflash it...
http://www.mazemobile.com/download-center
The ROM used to be there, but they have the ****ing cheek to say "people tried to flash and blamed MAZE" now it was MAZE's update in the first place that buggered my phone.:silly:..i still have the original ROM...
https://drive.google.com/drive/folders/0B8XLZxEJR8albndMcXJhWGtlVDQ
^not sure if that works for you, but basically it was..
:A really crap tutorial
:Maze Alpha flash tool.zip
:Maze_Alpha_V05_20170816
I've followed everything by the letter to no avail???
Now MAZE are bloody useless, can i count on one of you clever chaps to help me out?
P.s it's the 4 gig model.
Many thanks lads...
Any joy?
Is there anybody on here that had the same problem? You guys are usually really helpful, as i'm getting no rsponse from MAZE i thought i'd try where the true tech heads reside (i've received help before on my Xioami phones and smartwatches before) or is it that not many people have bothered with this phone? please help a guy out...much appreciated.
seedaripper said:
Is there anybody on here that had the same problem? You guys are usually really helpful, as i'm getting no rsponse from MAZE i thought i'd try where the true tech heads reside (i've received help before on my Xioami phones and smartwatches before) or is it that not many people have bothered with this phone? please help a guy out...much appreciated.
Click to expand...
Click to collapse
Well the thing is that you need to provide a bit more info. 'I've followed everything by the letter to no avail???' But you are not telling what works or not or what step you are stuck in the manual.
A lot of things come to my mind.
- is it still booting
- did you try another cable - charger
- ...
If it still boots and works a bit can you connect it to a pc and access for example the internal memory etc?
Some more info would be of help to get response... although I find the Maze Alpha part of the forum a lot of read and very little help (a bit of ranting may wake up people)
Cheers...someone lives!
Thanks for responding lukesan (much appreciated)
I'm using the original charger, it was working fine until i got the OTA so i doubt that's the problem.
No it doesn't boot (there is just enough charge to get to recovery mode,fastboot mode,normal boot)
I followed the manual/flash/tool etc (does the google drive doc show up for you as posted above?) everything seemed to go fine...but the problem still persists, it just wont charge?
Maybe i need a new ROM (or it could be the tool MAZE sent me) they are ****ing useless and i've started a bit of a social media campaign against them
(at first they were keeping in touch, but now they just ignore me completely on facebook) it pisses me off no end:crying:
P.s it does connect to my PC (sometimes), where should i dig around?
lukesan said:
Well the thing is that you need to provide a bit more info. 'I've followed everything by the letter to no avail???' But you are not telling what works or not or what step you are stuck in the manual.
A lot of things come to my mind.
- is it still booting
- did you try another cable - charger
- ...
If it still boots and works a bit can you connect it to a pc and access for example the internal memory etc?
Some more info would be of help to get response... although I find the Maze Alpha part of the forum a lot of read and very little help (a bit of ranting may wake up people)
Click to expand...
Click to collapse
seedaripper said:
Thanks for responding lukesan (much appreciated)
I'm using the original charger, it was working fine until i got the OTA so i doubt that's the problem.
No it doesn't boot (there is just enough charge to get to recovery mode,fastboot mode,normal boot)
I followed the manual/flash/tool etc (does the google drive doc show up for you as posted above?) everything seemed to go fine...but the problem still persists, it just wont charge?
Maybe i need a new ROM (or it could be the tool MAZE sent me) they are ****ing useless and i've started a bit of a social media campaign against them
(at first they were keeping in touch, but now they just ignore me completely on facebook) it pisses me off no end:crying:
P.s it does connect to my PC (sometimes), where should i dig around?
Click to expand...
Click to collapse
Just checked, and yes it is the correct manual. But lets say that even me, a veteran (with no patience), had issues with it. It is 100% correct but ... well see later on where you get.
Ok, first couple of things come up in my mind. Could still be the cable, the charger or even the the charging port that is broken. Been in the electronics business since the late 80's and these things can go wrong or broken any minute even thinking that a firmware update caused it.
Charger you can easily check if you just connect it to another charger or a pc usb port. A PC usb port will only deliver (mostly) max 400mA to 500mA .. meaning it will charge, if it still does, extremely slow. So I would keep it connected to a pc all day long or night before trying to switch it on. Trying to switch it on during charging and batt at low level will probably not work. You could try to power on after 2 or 3 hours or so and if it powers on then I would power it off again to get at least some juice in it to play around.
Cable, I would go fetch another one, they will come in handy in the future too. If it doesn't fit properly because the port is to deep in the Alpha then just take a knife and carefully cut a very small piece of the plastic, just 1mm is enough. I've done this on the 2 extra cables I have here and it works perfectly and I don't even see it aesthetically so no harm done on mine.
Now if that still doesn't work we can try the next step. But be very careful to know that that will delete all data, pictures, etc off of the phone. Because of all my toying with this phone I stuck an sd-card in it and doing a backup before I play with it again.
The manual states that you have to press the volume up button.. Well you can already test that without hurting anything as long you don't press anything on the flashtool. So only volume up and then insert the usb cable to a pc. Now the mistake I made in the beginning was to also push the power button.
So on the pc open up your device manager. If you do volume up (not in any of the other modes like fastboot etc, so from a standpoint that the phone is completely off) hold it for 2 or 3 sec and plug it into the PC. Now you should hear the typical usb connection sound and see something happening like an extra device in the manager. Probably you do not have the correct drivers installed for starters. Look for mtk drivers for your OS. Be careful, a lot of crap and virus links out there.
Now another issue that I fell for the first time is that you have to connect it twice like that to the pc to actually flash. First time ... press the 'scan' and let it do it (think the top field will become green) and then disconnect the phone and do the same volume up and connect and then it will allow you to flash.
But first check what is happening before we have to flash it.
Btw I know about their attitude. Well, as a Chinese company they must understand that by this attitude they will not going to sell any products anymore. I only bought mine because it was a special deal and I wanted to test an MTK chipset. They never replied to me why there is no real fast charge on it etc.
I also very very highly recommend you to invest, well for the price of a sandwich, to buy a usb charging doctor which will allow you to see the voltage and current. You don't need to be a doctor to us it and at least you see something instead of having to guess. Also while you are at it buy good quality chargers and a couple of cables. They will always come in handy and take some of the guesswork away if needed.
Top lad.
Again many thanks luksan (hefty bit of typing you did there mate )
I very much doubt it's the charger (i was extremely careful everytime with insertion) or port for that matter...this is the only USB-C i have (everything else is old school micro USB) and i resent forking out more money (the original trader Cafago said to send it back tracked at my own cost...£60!!!)
i'd like to try and fix the bastard and then sell it, never to return
Again, all these probs literally appeared after i did the OTA (i doubt it was coincidence)
i do like your advice on the re-doing the flash twice, so i may give that a go...bloody nora, what a pain in the arse!
Thanks for being a voice in the void pal...
See
lukesan said:
Just checked, and yes it is the correct manual. But lets say that even me, a veteran (with no patience), had issues with it. It is 100% correct but ... well see later on where you get.
Ok, first couple of things come up in my mind. Could still be the cable, the charger or even the the charging port that is broken. Been in the electronics business since the late 80's and these things can go wrong or broken any minute even thinking that a firmware update caused it.
So on the pc open up your device manager. If you do volume up (not in any of the other modes like fastboot etc, so from a standpoint that the phone is completely off) hold it for 2 or 3 sec and plug it into the PC. Now you should hear the typical usb connection sound and see something happening like an extra device in the manager. Probably you do not have the correct drivers installed for starters. Look for mtk drivers for your OS. Be careful, a lot of crap and virus links out there.
Now another issue that I fell for the first time is that you have to connect it twice like that to the pc to actually flash. First time ... press the 'scan' and let it do it (think the top field will become green) and then disconnect the phone and do the same volume up and connect and then it will allow you to flash.
But first check what is happening before we have to flash it.
.
Click to expand...
Click to collapse
seedaripper said:
Again many thanks luksan (hefty bit of typing you did there mate )
I very much doubt it's the charger (i was extremely careful everytime with insertion) or port for that matter...this is the only USB-C i have (everything else is old school micro USB) and i resent forking out more money (the original trader Cafago said to send it back tracked at my own cost...£60!!!)
i'd like to try and fix the bastard and then sell it, never to return
Again, all these probs literally appeared after i did the OTA (i doubt it was coincidence)
i do like your advice on the re-doing the flash twice, so i may give that a go...bloody nora, what a pain in the arse!
Thanks for being a voice in the void pal...
See
Click to expand...
Click to collapse
Well don't flash it twice. You have to put it in that mode twice to start it to complete the procedure. I do not believe in the wipe it 3 times to be sure, turn around and jump to make it better or faster. Loads of voodoo that is not scientifically proven around. It's all about a 0 and a 1, there is nothing in between that.
But .£60 to send that charger, LOL.
A month ago I bought an Aukey charger that included a USB-C cable for like .£12 including shipping to Belgium. (well just followed the rain and snow and landed here)
Let us know what happens next.
Any update on what you did?
GAH!
Yes, i've just tried everything again...nothing seems to work? when i actually start the tool i get a number of errors (including scatter?) then the tool boots, i then go through the broken english bollocks of the 'guide' again, do everything and it still doesn't work?? listen man, could you do me a massive favour...just outline the steps (bullet point wise) on what to do? no chatting about the chinese or voodoo
just nice clear as day steps, because as it stands i'm going to have to pay £70 just to send this piece of **** back (and probably wont get a full refund)
If you could do that (and i mean laymans terms here) i'd be forever grateful...
Cheers bud.:good::good:
lukesan said:
Any update on what you did?
Click to expand...
Click to collapse
seedaripper said:
Yes, i've just tried everything again...nothing seems to work? when i actually start the tool i get a number of errors (including scatter?) then the tool boots, i then go through the broken english bollocks of the 'guide' again, do everything and it still doesn't work?? listen man, could you do me a massive favour...just outline the steps (bullet point wise) on what to do? no chatting about the chinese or voodoo
just nice clear as day steps, because as it stands i'm going to have to pay £70 just to send this piece of **** back (and probably wont get a full refund)
If you could do that (and i mean laymans terms here) i'd be forever grateful...
Cheers bud.:good::good:
Click to expand...
Click to collapse
But what about the drivers etc.... What shows up?
ROM?
lukesan said:
Any update on what you did?
Click to expand...
Click to collapse
Perhaps it's the ROM? any chance you could give me the latest version? (or a link) i keep getting error in the light green field (FAIL) on the Tool?
I'm not sure if it's the tool or the bloody ROM?
As usual not a sodding dicky bird from MAZE (emails,twitter facebook etc) what a sh!tty company...
Nothing shows up...i think the first time i tried to plug it into the PC it ran a scan,(i don't think it found the drivers, as it doesnt show up on my computer :running win 7) from there on in, nothing? it also makes the mandatory PC sound bleep when plugged in, then about a second later i get the discharge bleep? (not sure if this is lack of charge) if i had a frigging phone i'd post screenshots! damned if i do, damned if i don't!
lukesan said:
But what about the drivers etc.... What shows up?
Click to expand...
Click to collapse
seedaripper said:
Nothing shows up...i think the first time i tried to plug it into the PC it ran a scan,(i don't think it found the drivers, as it doesnt show up on my computer :running win 7) from there on in, nothing? it also makes the mandatory PC sound bleep when plugged in, then about a second later i get the discharge bleep? (not sure if this is lack of charge) if i had a frigging phone i'd post screenshots! damned if i do, damned if i don't!
Click to expand...
Click to collapse
Well if it hasn't gotten the correct drivers it will never ever be able to flash. It's like trying to use your house keys to start your car.
I see all kinds of stuff happening if you keep the device manager open. Open up the 'ports' (com & lpt) section. Now press the 'volume up' key for a second or 2 and then connect it to a usb port while holding the key.. release it like a second later when it is connected to the port. Now you should see some stuff happening. Just did it on my win10 machine but should be pretty similar on a win7. One of them says first 'mtk usb' and then 'preloader usb vcom' . If these don't show up then look no further for now.
seedaripper said:
Perhaps it's the ROM? any chance you could give me the latest version? (or a link) i keep getting error in the light green field (FAIL) on the Tool?
I'm not sure if it's the tool or the bloody ROM?
As usual not a sodding dicky bird from MAZE (emails,twitter facebook etc) what a sh!tty company...
Click to expand...
Click to collapse
Have you tried my backup here ?
Flash TWRP using fastboot method and then boot into TWRP and do a restore with the backup I provide for Maze Alpha 4/64
dreambo said:
Have you tried my backup here ?
Flash TWRP using fastboot method and then boot into TWRP and do a restore with the backup I provide for Maze Alpha 4/64
Click to expand...
Click to collapse
His device doesn't charge and his battery is flat so I guess his by the time he can flash the device dies anyway.
er?
lukesan said:
Well if it hasn't gotten the correct drivers it will never ever be able to flash. It's like trying to use your house keys to start your car.
I see all kinds of stuff happening if you keep the device manager open. Open up the 'ports' (com & lpt) section. Now press the 'volume up' key for a second or 2 and then connect it to a usb port while holding the key.. release it like a second later when it is connected to the port. Now you should see some stuff happening. Just did it on my win10 machine but should be pretty similar on a win7. One of them says first 'mtk usb' and then 'preloader usb vcom' . If these don't show up then look no further for now.
Click to expand...
Click to collapse
Ok, did that for a split second 'media TEK preloader USB VCOM (android) (COM4)' flashes up, i managed to click on it quickly and got to mediatek properties...then went to update driver (it searched the net and found it) all this time after the original insertion, literally a second after it just disconnects? (and it doesn't show up in my computer) i get this as device status.....
Currently, this hardware device is not connected to the computer. (Code 45)
To fix this problem, reconnect this hardware device to the computer.
I plug it back in, it says normal, then a second later the above message? any ideas?
lukesan said:
His device doesn't charge and his battery is flat so I guess his by the time he can flash the device dies anyway.
Click to expand...
Click to collapse
Yep, when i try to power on i have a split second of the MAZE logo, then back to death...i Can leave it charging and i get the wobble liquid battery graphic, but it never goes above 0%, as explained this only happened after a firmware update (#dreambo)
Can't get my head round multi quote?
dreambo said:
Have you tried my backup here ?
Flash TWRP using fastboot method and then boot into TWRP and do a restore with the backup I provide for Maze Alpha 4/64
Click to expand...
Click to collapse
Yep, when i try to power on i have a split second of the MAZE logo, then back to death...i Can leave it charging and i get the wobble liquid battery graphic, but it never goes above 0%, as explained this only happened after a firmware update (#dreambo)
seedaripper said:
Ok, did that for a split second 'media TEK preloader USB VCOM (android) (COM4)' flashes up, i managed to click on it quickly and got to mediatek properties...then went to update driver (it searched the net and found it) all this time after the original insertion, literally a second after it just disconnects? (and it doesn't show up in my computer) i get this as device status.....
Currently, this hardware device is not connected to the computer. (Code 45)
To fix this problem, reconnect this hardware device to the computer.
I plug it back in, it says normal, then a second later the above message? any ideas?
Click to expand...
Click to collapse
Mmm, if you see the preloader thing then I guess that is ok. ... it is no longer an 'unknown device' which sounds fine to me. Let me quickly test on my Maze for a sec. (will edit this post).
It is normal that it disconnects. My guess is that it tries to setup comms between device and something on the pc where it can talk to. If there is no communication then it just powers down again. The display etc will all stay off since it directly does the comms to the cpu and the ram. Sort of write only state. So it is a very low level form of programming. Can be scary for people because you see nothing happening on the phone during that process.
Ok just tested again.. Can you do step 1 to 5 in the manual without an error? (to be sure I would right-click on the exe and run it as administrator to start that program)
Till that step 5 no connection to the Alpha is needed. In step 5 if you have pressed 'scan' it should say something like resetting comm ports and only the 'stop all' should be clickable.
If we are that far then I guess we are a step further.
Give that a try and then we'll see for the next step.
lukesan said:
Mmm, if you see the preloader thing then I guess that is ok. ... it is no longer an 'unknown device' which sounds fine to me. Let me quickly test on my Maze for a sec. (will edit this post).
It is normal that it disconnects. My guess is that it tries to setup comms between device and something on the pc where it can talk to. If there is no communication then it just powers down again. The display etc will all stay off since it directly does the comms to the cpu and the ram. Sort of write only state. So it is a very low level form of programming. Can be scary for people because you see nothing happening on the phone during that process.
Ok just tested again.. Can you do step 1 to 5 in the manual without an error? (to be sure I would right-click on the exe and run it as administrator to start that program)
Till that step 5 no connection to the Alpha is needed. In step 5 if you have pressed 'scan' it should say something like resetting comm ports and only the 'stop all' should be clickable.
If we are that far then I guess we are a step further.
Give that a try and then we'll see for the next step.
Click to expand...
Click to collapse
Pics ...hopefully...
Hello XDA community yesterday I was using my pixel phone normally and it was working fine today morning I woke up to check time on my phone but my phone was dead, screen was completely pitch black, charging phone doesn't work screen stays dead, even its not going to bootloader it feels like phone is completely dead but when I connect it to pc I hear connection sound and a random pop up show that device is not detected etc. I searched on internet and it feels like when I was sleeping because my phone was on charging and WIFI was connected( normally I don't use WIFI I use mobile data) maybe a software update was installed which made phone software & drivers to get corrupted because nothing is working nor its charging, booting, vibrating its completely dead
I searched on internet and also installed QUALCOMM drivers on my pc that unknown popup while connecting while to pc shifted into
Qualcomm HS-USB QDLoader 9008
and I also get know that a firehose file can maybe fix my phone because maybe bootloader is corrupted or anything if anyone can help me in this matter I will really appreciate it. Thanks!
Noman8 said:
Hello XDA community yesterday I was using my pixel phone normally and it was working fine today morning I woke up to check time on my phone but my phone was dead, screen was completely pitch black, charging phone doesn't work screen stays dead, even its not going to bootloader it feels like phone is completely dead but when I connect it to pc I hear connection sound and a random pop up show that device is not detected etc. I searched on internet and it feels like when I was sleeping because my phone was on charging and WIFI was connected( normally I don't use WIFI I use mobile data) maybe a software update was installed which made phone software & drivers to get corrupted because nothing is working nor its charging, booting, vibrating its completely dead
I searched on internet and also installed QUALCOMM drivers on my pc that unknown popup while connecting while to pc shifted into
Qualcomm HS-USB QDLoader 9008
and I also get know that a firehose file can maybe fix my phone because maybe bootloader is corrupted or anything if anyone can help me in this matter I will really appreciate it. Thanks!
Click to expand...
Click to collapse
Did you try both
Google Pixel - Update and Software Repair
&
Android Flash Tool
flash.android.com
already?
Here is a guide on how to get ADB working:
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com
Do you have OEM Unlocking enabled? Maybe unlocked bootloader (if your bootloader is dead and you haven't unlocked it previously, there might not be much hope for you)? If you can't even get into recovery/fastboot mode, you are in deep.
Morgrain said:
Did you try both
Google Pixel - Update and Software Repair
&
Android Flash Tool
flash.android.com
already?
Here is a guide on how to get ADB working:
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com
Do you have OEM Unlocking enabled? Maybe unlocked bootloader (if your bootloader is dead and you haven't unlocked it previously, there might not be much hope for you)? If you can't even get into recovery/fastboot mode, you are in deep.
Click to expand...
Click to collapse
Yes i have tried both nothing is working my phone was fresh it wasn't rooted,its bootloader was locked it was basically working flawlessly as usual but today morning it was dead, bricked nothing is working,phone is not charging pressing power button and volume down does work when connecting to pc because i hear connection and disconnection sound but nothing shows up on the screen. Feels like phone is bricked or anything... Am not sure because i have not done any modifications to my phone i was using normally and its battery was also great idk what happened...
Noman8 said:
Yes i have tried both nothing is working my phone was fresh it wasn't rooted,its bootloader was locked it was basically working flawlessly as usual but today morning it was dead, bricked nothing is working,phone is not charging pressing power button and volume down does work when connecting to pc because i hear connection and disconnection sound but nothing shows up on the screen. Feels like phone is bricked or anything... Am not sure because i have not done any modifications to my phone i was using normally and its battery was also great idk what happened...
Click to expand...
Click to collapse
You might want to wait some time, until the battery runs out/depletes. Then try to charge it/start it. But that route will take a couple of days.
Noman8 said:
No my phone was fresh it wasn't rooted,its bootloader was locked it basically working flawlessly as usual but today morning it was dead, bricked nothing is working,phone is not charging pressing power button and volume down does work when connecting to pc because i head connection and disconnection sound but nothing shows up on the screen. Feels like phone is bricked or anything... Am not sure because i have not done any modifications to my phone i was using normally and its battery was also great idk what happened...
Click to expand...
Click to collapse
Morgrain said:
You might want to wait some time, until the battery runs out/depletes. Then try to charge it/start it. But that route will take a couple of days.
Click to expand...
Click to collapse
Ahan i see btw thanks for replying!
Noman8 said:
Qualcomm HS-USB QDLoader 9008
Click to expand...
Click to collapse
Yes, your pixel is now dead. Similar to what happened with my Pixel 2.
NinjaCoool said:
Yes, your pixel is now dead. Similar to what happened with my Pixel 2.
Click to expand...
Click to collapse
Yes
pixel4-XL_firehose - Google Drive
drive.google.com
This is the pixel 4 and 4 xl firehose
r1pp3d2 said:
pixel4-XL_firehose - Google Drive
drive.google.com
This is the pixel 4 and 4 xl firehose
Click to expand...
Click to collapse
hi brother can it be fixed with firehose? please reply
and what are exact steps to flash Firehose!
r1pp3d2 said:
pixel4-XL_firehose - Google Drive
drive.google.com
This is the pixel 4 and 4 xl firehose
Click to expand...
Click to collapse
i am trying to flash this firehose to my pixel but it is requiring 2 more files "RAW PROGRAM & PATCH" FILE if u can help me here i will appreciate that!
That would be the backup of the phone. These are not backups.
Hi, just lost my pixel 4 after an android security update .
It really looks like planned obsolescence, considering this is happening few months after warranty.
Like you i'm trying to find "raw program" and "patch file".
According this website, thoses files could be generated with a python script from a file named "GPT.bin" i'm actually looking for.
If anyone succeed to respawn, don't be shy and share please.
nicauderan said:
Hi, just lost my pixel 4 after an android security update .
It really looks like planned obsolescence, considering this is happening few months after warranty.
Like you i'm trying to find "raw program" and "patch file".
According this website, thoses files could be generated with a python script from a file named "GPT.bin" i'm actually looking for.
If anyone succeed to respawn, don't be shy and share please.
Click to expand...
Click to collapse
Google doesn't just kill phones like that. My Pixel 4XL is still find, hell my Nexus 6 still works.
nicauderan said:
Hi, just lost my pixel 4 after an android security update .
It really looks like planned obsolescence, considering this is happening few months after warranty.
Like you i'm trying to find "raw program" and "patch file".
According this website, thoses files could be generated with a python script from a file named "GPT.bin" i'm actually looking for.
If anyone succeed to respawn, don't be shy and share please.
Click to expand...
Click to collapse
You are not getting your pixel back now u can replace motherboard now like i did i ordered new motherboard from ali express and Replaced it!
Just received motherboard from Ali and the pixel respawned.
Was charging my pixel 4, it was 100% charged for a good few hours, I woke up around midnight and was playing a game on my phone when suddenly it went black. I unplugged the phone and tried a few fixes. After crying it out and leaving it uncharged I plugged it into my portable charger where the lights came on, still nothing on my phone. I also tried plugging into my computer and no sounds or any sign it had been plugged into my computer from both phone or computer. I was thinking if this is a battery issue it should at least do something on my computer right? I have tried again to plug it into my portable charger and this time no lights on the portable charger. Maybe this isn't the right thread but I figured I'd post here anyway, any suggestions, should I take it to a shop? I'm not tech savvy, could it be a display or battery issue or a motherboard issue like above?
also to note, I had both the front and back glass changed almost a year ago now, and except from one dead pixel on the screen from the original glass break its been fine.
Also to note, I recently moved from Australia to Canada and am using a plug converter that my laptop computer is also plugged into and its fine, so I'm thinking it wasn't a power surge? It has two usb ports and a Au plug on the same converter plug.
Oh, you are not alone. 3 days after Android 13 update, I woke up, my Pixel 4XL alarm went off, used Android Auto to go to work and listen to music, checked email on it at work, plugged it in to my Pixel approved charger/cable as always, picked it up hours later and .... brick. No response to charger plug/unplug even with various other plugs and cables. No response to 30 sec of pressing power or power with up/down volume combos. It was a brick, just like many other Pixel 2,3,4,5 owners reported after various updates over the years, courtesy of Qualcomm chips and Google's lack of quality checking chips. Today's lesson: Stop paying Google for trash. It happened to me 280 days after the warranty expired. Google said that if it was from the Android 13 update, I should take it to UbreakitIfixit near me and they will fix it under an extension of 1 year to the warranty. We'll see. Sadly, it will still have Google's low grade Qualcomm chip design after the repair.