Related
Hi there,
I fear I hard bricked my G1 (after long years of good service as gps device thanks to a 2600mAh battery).
Since it was quite slow on CM7, I downgraded it to CM6.1. But this would'nt boot. (boot loop)
So I did a bit of reading and decided to downgrade the radio too. I downloaded a flashable zip and flashed it the usual way in the CWM recovery - which didn't finish (after a few minutes), so I removed the battery.
Since then my G1 wont start any more. On top of that, it want event charge. If I try to charge it the status led wont event light up. (I already tried it with two different batteries, both yield the same results.)
Funny thing though: If I don't charge it and let it sit for a few hours, the status LED very shortly lights up when pressing the power button. (But other than this nothing happens and if I press the power button again shortly after the LED stays dead.)
So ... I fear the problem is hardware and not software related.
Does anybody have an idea what could be broken (software or hardware) and if it's software based if there's a way to revive my phone?
(Before anybody asks ... yes, I have newer android phones, but I really live my G1 for nostalgic value so if there a way to get it running again I definitely would try.)
thx a lot,
Bapf
Sounds like you need JTAG, and don't take this the wrong way, but flashing firmware isn't the usual way, its the way you brick your phone. If possible always use fast boot to flash firmware or you are asking for a brick.
You can buy the JTAG equipment yourself and the software is free. Or you can see if you can find someone locally to do it. Unless you have a particular sentimental value to this phone it maybe cheaper to buy a new one.... Sorry for bad news
Sent from my Nexus 7 using xda premium
Bricked G1 - Try Again w/ SIM Card IN!
I had the exact symptoms mentioned in this post - tried nearly everything until I finally put back in the SIM card (even through I don't have T-Mobile anymore) - it booted again and registers the AC adapter and/or USB cable. Hope this helps some who are struggling at this level as I did!!
Bapf said:
Hi there,
I fear I hard bricked my G1 (after long years of good service as gps device thanks to a 2600mAh battery).
Since it was quite slow on CM7, I downgraded it to CM6.1. But this would'nt boot. (boot loop)
So I did a bit of reading and decided to downgrade the radio too. I downloaded a flashable zip and flashed it the usual way in the CWM recovery - which didn't finish (after a few minutes), so I removed the battery.
Since then my G1 wont start any more. On top of that, it want event charge. If I try to charge it the status led wont event light up. (I already tried it with two different batteries, both yield the same results.)
Funny thing though: If I don't charge it and let it sit for a few hours, the status LED very shortly lights up when pressing the power button. (But other than this nothing happens and if I press the power button again shortly after the LED stays dead.)
So ... I fear the problem is hardware and not software related.
Does anybody have an idea what could be broken (software or hardware) and if it's software based if there's a way to revive my phone?
(Before anybody asks ... yes, I have newer android phones, but I really live my G1 for nostalgic value so if there a way to get it running again I definitely would try.)
thx a lot,
Bapf
Click to expand...
Click to collapse
I don't know if this will work,as I've never encountered a situation such as this, but have you tried bootloader(power button+camera button)?
If you can get it into bootloader, then I have the original rc29 DREAIMG.NBH file(plus, rc29 is the best place to start if you want to root it or install a custom rom).If you get it working and just want stock 1.6, i have those updates as well.
(all said out of hope, I have a g1 and I love it,I'm really glad that someone else shares my enthusiasm!!)
If bootloader works, give me your email and i'll send you the files, good luck!:fingers-crossed:
Nope. It won't even start the bootloader.
Sent from my Nexus 4 using xda app-developers app
Well thats unfortunite, I guess it's just for a soft brick.
I updated my phone just recently and came across this major issue.
I used Sony's own tools for updating that leaves two options "Sony Companion" and "Sony Update Service".
Both giving the same results for my phone, even a full reinstall doesn't work.
When done updating you set your Xperia ZR back on as the software says.
It starts normally showing the Sony logo, Xperia logo and some Xperia animations.
When it gets to the lock screen and asks for your pin code to unlock your sim-card everything is fine.
Here it comes.
When setting your screen in standby and back on the touchscreen function is not working anymore.
Other buttons are working fine (power, volume, photo)
I talked to a Sony employee and he came to the conclusion that it's a Hardware defect, that sounds to me like a bad excuse.
The screen works the first time but not the second time it's turned on.
Looks to me like a software problem.
Are any others of you experiencing this problem with the Xperia ZR? Please, let me know below!
I don't have a solution yet or if you have a solution, let us/me know down here.
Thanks in advance!
It sounds like the firmwarepart with drivers four the touchscreen didn't bite. If it's anything like the 4.2.1-4.2.2 in HTC that part needs to get through.
Is there any way of restarting the process through companion?
Skickat från min HTC One via Tapatalk 2
A temporarily solution is to touch the screen when pressing the power button to turn on the screen.
Example: Touch with your left index finger on the screen and press power shortly as you normally do, then move your index finger over the screen.
But you have to do this every time you turn on the screen!
Ceremco said:
A temporarily solution is to touch the screen when pressing the power button to turn on the screen.
Example: Touch with your left index finger on the screen and press power shortly as you normally do, then move your index finger over the screen.
But you have to do this every time you turn on the screen!
Click to expand...
Click to collapse
Have you tried flashing the ftf file through flashtool?
djpeesh said:
Have you tried flashing the ftf file through flashtool?
Click to expand...
Click to collapse
No, I haven't tried that yet, because I'm not familiar with flashtool.
It's easy.
1. Do a search for flashtool and download the exe file.
2. Install it. Install the latest drivers by going to the install drivers menu in the program.
3. Download the ftf file on the android development section.
4. Save it in the c drive folder for flashtool-->>firmware
5. Press the big flash (lightning symbol)
6. Chose flash mode
7. Your firmware should show up. Choose the C5503 firmware.
8. It will tell you to turn off your phone and while plugging in, keep the back button pressed. Since the zr doesn't have a back button, hold the volume down button.
9. It should do everything automatically. You'll be on a new os. Reboot and you're done.
Sent from my C5503 using Tapatalk 2
djpeesh said:
It's easy.
1. Do a search for flashtool and download the exe file.
2. Install it. Install the latest drivers by going to the install drivers menu in the program.
3. Download the ftf file on the android development section.
4. Save it in the c drive folder for flashtool-->>firmware
5. Press the big flash (lightning symbol)
6. Chose flash mode
7. Your firmware should show up. Choose the C5503 firmware.
8. It will tell you to turn off your phone and while plugging in, keep the back button pressed. Since the zr doesn't have a back button, hold the volume down button.
9. It should do everything automatically. You'll be on a new os. Reboot and you're done.
Sent from my C5503 using Tapatalk 2
Click to expand...
Click to collapse
I'll try that :fingers-crossed:
Did you also try the update to 4.2.2?
It's still bugging me that they released it and it didn't work. (for my Sony Xperia ZR at least)
Great it worked!
I took flashtool from androxyde.github.io and I also took the firmware from there.
For me the first 3 times flashing went wrong, but it's nothing to worry about just reconnect the USB while pressing volume-down button and retry.
So I am now back to android 4.1.2 and the screen is working fine without any problems.
Thanks djpeesh!
I have the same problem but I don't want to revert to 4.1.2 is there another workaround? This is really stupid SONY says that an app can cause this but there is pretty much nothing on my device. I did a hard reset and it didn't help. I'll try something else to see if I can avoid the downgrade. I think everything started when I activated debugging mode.
Same happens with mine.At times I am not able to accept phones calls by sliding. i have to press the power button several times to switch off and on the screen and then it functions again
motodude said:
Same happens with mine.At times I am not able to accept phones calls by sliding. i have to press the power button several times to switch off and on the screen and then it functions again
Click to expand...
Click to collapse
I tried flashing 4.2.2 russian rom and it didn't work, tried 4.1.2 russian version, also didn't work. I'll try another ROM now and if it still doesn't work I'll go to where I bought it and I'm going to smash it in the sellers head (angry). I'm so disappointed in SONY.
andes83 said:
I tried flashing 4.2.2 russian rom and it didn't work, tried 4.1.2 russian version, also didn't work. I'll try another ROM now and if it still doesn't work I'll go to where I bought it and I'm going to smash it in the sellers head (angry). I'm so disappointed in SONY.
Click to expand...
Click to collapse
Please dont try this method, as this might brick your phone permanently and you might end up in jail.
motodude said:
Please dont try this method, as this might brick your phone permanently and you might end up in jail.
Click to expand...
Click to collapse
I managed to make the screen work again but then it stopped like before. I suspect that there might be a SIM card problem is your sim a genuine micro SIM or is it like mine a chopped mini one?
I sended my Xperia ZR back to sony, because I talked to a SONY employee about this and his answer was to send it back for repairs. After all **** installations that didn't work. At the look of it the frimware for the screen is not inplemented in the new 4.2.2 update. If you could rip the 4.1.2 screen frimware off and migrate it with the 4.2.2 update that could work, but that is a bit to advanced for me.
Ceremco said:
I sended my Xperia ZR back to sony, because I talked to a SONY employee about this and his answer was to send it back for repairs. After all **** installations that didn't work. At the look of it the frimware for the screen is not inplemented in the new 4.2.2 update. If you could rip the 4.1.2 screen frimware off and migrate it with the 4.2.2 update that could work, but that is a bit to advanced for me.
Click to expand...
Click to collapse
My screen didn't work even with a 4.1.2 official roms tomorrow I'm going to send it for repairs. It's really annoying to spend 500 dollars and have these stupid problems my HTC TOUCH HD is 5 years old and has never been repaired, still works the old beast, and this device is 10 days old and already is getting on my nerves.
andes83 said:
I managed to make the screen work again but then it stopped like before. I suspect that there might be a SIM card problem is your sim a genuine micro SIM or is it like mine a chopped mini one?
Click to expand...
Click to collapse
Yus, chopped one
motodude said:
Yus, chopped one
Click to expand...
Click to collapse
Well, that wasn't the problem anyway I just left mine in the repair shop, they tried to blame for messing up the software of the phone but I used only SONY official firmware, so let's see what they'll come up with next I hope they won't make me pay for repairs because this will be a very sad story.
andes83 said:
Well, that wasn't the problem anyway I just left mine in the repair shop, they tried to blame for messing up the software of the phone but I used only SONY official firmware, so let's see what they'll come up with next I hope they won't make me pay for repairs because this will be a very sad story.
Click to expand...
Click to collapse
Why are they saying that you have messed up with the software,in which firmware are you in.
motodude said:
Why are they saying that you have messed up with the software,in which firmware are you in.
Click to expand...
Click to collapse
I used only software from this page http://forum.xda-developers.com/showthread.php?t=2384512 and Sony Companion repair tool. I don't know what their problem was, probably just want to score some money or something.
I know this topic become legacy already, but how do u guys solve it? My xperia zr screen becomes crazy if overheat a bit. No matter what firmware used. Have to off screen and then on back. Very annoying.
Okay, how about this one?
My phone WAS stuck in one of these infamous boot loop/battery thingys, but I just removed the battery and charged it with an external RC Battery charger ($60, charges EVERY type of battery, everyone should have one). When I put it back in, everything was great. I then used Flashtool to unlock the bootloader without problem. Then I went to flash a stock ROM to the thing via flashtool and left it go. When I came back, flashtool had completed the operation without errors, and had last told me to reset the phone. The phone, however, wouldn't turn on or respond AT ALL to anything I did. So I took the battery out and charged it, thinking it must just have run out of power but upon putting the battery back in, the phone remained unresponsive.
No modes, no lights, nothing. The ONLY thing that happens is if I have the thing plugged into the PC and I hold the UP (maybe the DOWN, i don't remember) button, the PC detects and tries to find drivers for something called QHSUSB_DLOAD... qualcomm High Speed USB download drivers, maybe? I've looked around and somewhere someone said that for another Xperia (don't remember which one) THEY had read that you could get the phone into flashboot mode somehow once installing the drivers. They supposedly come with the "gordon's" USB tools or whatever the heck it's called, but I couldn't get xp to accept anything included with gordon's as a proper driver. Yes, I know I had to INSTALL gordons, since an exe sure isn't a driver.
I've also found that, at least for the Galaxy 2, once you're at a point where it's asking for QHSUSB_DLOAD drivers, there's nothing you can do short of JTAG repair. However, as my friend so succinctly put it, "That's not a galaxy, it's an xperia" so I'm still holding onto hope. Anybody have any ideas? Or where I could find a QHSUSB_DLOAD driver and what to do with it then? I AM planning on getting a jtagger soon, so maybe this'll be the reason I finally do.
1) you did not unlock your boot loader successfully using flash tool, that's impossible.
2) uninstall all Sony and any phone software/drivers from your PC
3) charge your phone for at least 24 hours without touching it.
4) install pccompanion to your PC
5) with the phone still turned off, press and hold the volume down button and attach usb cable, then whilst still holding the volume button press the power button until the phone vibrates.
6) the phone should go in to flash mode and you should be able to repair using flash tool, if it doesn't try the next steps.
7) install flash tool and run drivers.exe, choose flash mode, fastboot and tx drivers.
8) press and hold volume. Up and power button until phone vibrates and go back to step 5
9) after you have tried all this please let me know what happens
Sent from my LT30p using xda premium
xperia
gregbradley said:
1) you did not unlock your boot loader successfully using flash tool, that's impossible.
2) uninstall all Sony and any phone software/drivers from your PC
3) charge your phone for at least 24 hours without touching it.
4) install pccompanion to your PC
5) with the phone still turned off, press and hold the volume down button and attach usb cable, then whilst still holding the volume button press the power button until the phone vibrates.
6) the phone should go in to flash mode and you should be able to repair using flash tool, if it doesn't try the next steps.
7) install flash tool and run drivers.exe, choose flash mode, fastboot and tx drivers.
8) press and hold volume. Up and power button until phone vibrates and go back to step 5
9) after you have tried all this please let me know what happens
Sent from my LT30p using xda premium
Click to expand...
Click to collapse
1) Are you sure of that? I mean, it even has a BUTTON for it... it just automates the flashboot thingy if I remember correctly... the thing is, when I was writing my post, I wasn't sure if I was confusing this phone with another I was working on right then... but, no I'm pretty certain I did it through flashboot. Maybe not. Anyway, it wouldn't have even let me flash if my bootloader was locked still, right?
2) Haha- I'm afraid that's not really possible, BUT I already have PC companion installed and it was working fine. (Can you unlock your bootloader through PC companion? Maybe THAT's what I did- I KNOW I didn't do it through the command prompt, though...)
3) Okay, I am actually trying this as we speak, though I did take the battery out and charged it fully already
4) PC Companion installed
5) asks for QHSUSB_DLOAD driver, never vibrates
6) I wish
7)done
8) does nothing
9) Okay, so I will allow that perhaps there are things going on that all the uninstalling and reinstalling would fix and so I will try it out on a clean computer here in a little bit, but I don't think I'm gonna have any luck. I'll let you know what happens...
1) I am certain you have not unlocked your bootloader via flash tool or by pccompanion.
2) step 3 said charge battery for 24 hours, so you have not done that yet.
3) the remaining steps need to be done after the charging, so please follow the instructions as I have said them
4) the way you keep confusing terms and mixing up words makes me think you have not really done your research before trying to flash your phone. Reading is a great thing, try post 2 of the all in one thread. (there is no such thing as flashboot, that's a weird mixture of two different things, flash mode and fast boot, you need to know the difference between them. Also you can flash roms with a locked bootloader, you need to understand the difference between rooting and unlocking)
Sent from my LT30p using xda premium
greg,since 23rd February 2013 you can unlock BL via flashtool.You should know that...
Unified Bootloader unlock feature with the new BLU icon. No more unlock plugin.
Click to expand...
Click to collapse
http://www.flashtool.net/changelog.html
AFAIK that is just for the devices it could unlock before (2012 and before), not the newer devices that it could never unlock such as ours.
Sent from my LT30p using xda premium
gregbradley said:
1) I am certain you have not unlocked your bootloader via flash tool or by pccompanion.
2) step 3 said charge battery for 24 hours, so you have not done that yet.
3) the remaining steps need to be done after the charging, so please follow the instructions as I have said them
4) the way you keep confusing terms and mixing up words makes me think you have not really done your research before trying to flash your phone. Reading is a great thing, try post 2 of the all in one thread. (there is no such thing as flashboot, that's a weird mixture of two different things, flash mode and fast boot, you need to know the difference between them. Also you can flash roms with a locked bootloader, you need to understand the difference between rooting and unlocking)
Sent from my LT30p using xda premium
Click to expand...
Click to collapse
1) http://news.softpedia.com/news/Sony...ts-Flash-Tool-for-Xperia-Devices-315706.shtml - no wait, that just says it's supported by flashtool. I'll keep looking. I could tell you real easy if my bootloader was unlocked or not, but the thing wont turn on Would flashtool have offered me the bootloader unlock button if it didn't support it for my device? It tells me how to get to flashmode erroneously (for MY model, not most) but I figured it just wanted me in flashmode so I put the phone in flashmode. Hell, maybe I never unlocked the bootloader and just tried flashing a stock rom... would flashtool have allowed me to try and flash a non-stock rom with an unlocked bootloader? Would THAT have bricked the phone? I'm gonna go see what the rom I flashed was called now....
2) yeah, as I said, I'm doing that right now. though I took the battery out and charged it, so I thought it might work... even still, it's not been on for 24 hours yet as I writing this, so waiting... is there something that being on the charger for 24hours does besides ensure the battery is charged? Calibration or something? I can assure you the battery is fully charged to peak capacity.
3) will do, though when it doesn't work, do you promise that we can try to talk about QHSUSB_DLOAD? I promise that when it DOES work, I'll happily thank you and admit that even though you haven't quite given me a reason WHY, leaving it plugged in for 24 hours did something more than charge the battery. I know that sounds sarcastic, but I really think there's a chance it could but as I said, I can assure you the battery is charged to peak capacity
4) so I call "flashmode" "flash boot" mode- I am quite well aware of the differences between flashmode and fastboot mode. Figured since the one said flash and the one said fast it was obvious. Man, I did my "research", I read the all-in-one thread, as well as others... I've done this to dozens of phones over the last 3 years and just recently an Xperia Play which acquainted me with many of the idiosyncrasies of the Xperia line, flashboot, pc companion, etc... so when, after 3 years I finally actually ASK a question, I start to get this particular brand of close- mindedness... the way you keep not even trying to actually answer my question makes me think you didn't necessarily read my post before offering up a standard "cookie cutter" recipe which you don't necessarily understand enough to see how it might not necessarily apply. My REAL question was about QHSUSB_DLOAD device requiring a driver since that's the ONLY RESPONSE I CAN GET AT ALL from a phone WITH A FULLY CHARGED BATTERY. (you see, there I wanted to say QHSUSB_DLOAD driver, but that's not quite correct- QHSUSB_DLOAD.dll would be a possible name for the driver, but it's really a device called QHSUSB_DLOAD which does not have a driver. See how I'm taking pains to watch my words so as to not promote confusion.)
Cause you're RIGHT, really; using the proper terms IS important, but can you tell me that you SERIOUSLY didn't know what I meant when I said flashboot mode instead of flashmode? Or that you knew what I meant, but you thought that I didn't ? Did I ever confuse the two terms flashboot and fastboot? "there's no such thing as a flashboot"... what a silly-sounding thing to say... anyway, I never said there was- just that there was a flashboot mode. )Anyway, I do appreciate the help, just not the attitude, y'know?
The attitude was not meant (Nor I hope delivered, maybe its just a style of writing and trying to get to the point quick)
What charging for 24 hours does is to make sure there is some charge in the phone. I am no technical expert here, I am just very good at fault finding and knowing a trick or two that helps. The majority of people on here do not do their own fault finding before asking for help so before I dive in and help people I want to know that something simple has not been overlooked.
Charging for 24 hours has helped about 80% of the people on here who claim a hard/soft brick and they have tried ABSOLUTELY EVERYTHING to fix it.
Anyway, as for the QHSUSB download, I have had that before and just a perseverance of starting again from scratch and charging worked. (That's why I asked you to wipe all sony/phone/adb etc software from your pc) However, I am sure you are aware that the majority of times this happens you are left with a hard brick. Google gives a lot of results on this about Samsung and HTC phones (All of which offer no solutions) but very little for xperia phones.
All I am trying to do is guide you through some fault finding techniques and then give you some advice on things that have worked for people in the past.
NB
It is sometimes hard for me to hold the hand of all the users I help. I get between 20-30 PM's a day (Some of which are quite bad mannered because I have not replied within a few hours with a message on how to help them, that does not put me in a good mood) and check the Q&A thread (And general thread for those that cannot post in the correct forum) on a very regular basis in order to help people, but the increase in people not reading and just flashing means I cannot dedicate the time to being a personal assistant to all, you may have see 4 new threads in the Q&A section in the last 24 hours, all made by different users with the same problem, all of which occurred because they were flash happy and tried CM roms without unlocking the bootloader....
EDIT
There is still no such thing as flashboot....its called flashmode
In the past some users have called these two modes different things, got them mixed up or even thought they were the same thing, that's why I wanted to know which one you meant.
Also, the flashtool you linked to in point 1 is the official flashtool for Sony that only works on unlocked bootloaders. The flashtool from the first post in the dev section is the original flashtool by Androxyde and Bin4ry (First developed for the x10) and is the one to use for flashing FTF's and the one you used from your original post.
i also have this problem.
my xperia TL won't response anything. Plug in to PC it searching for QHUSB_DLOAD driver.
now, phone still in my drawer for 4 month
gregbradley;45518226]The attitude was not meant (Nor I hope delivered, maybe its just a style of writing and trying to get to the point quick)
Click to expand...
Click to collapse
S'okay. Attitude was a big strong for what I meant, but I couldn't think of the right word at the time...
What charging for 24 hours does is to make sure there is some charge in the phone.
Click to expand...
Click to collapse
Yeah, that's what I had gathered... I just got out of a bootloop by charging the battery with a programmable peak charger, so I KNOW its got a full charge.
The majority of people on here do not do their own fault finding before asking for help so before I dive in and help people I want to know that something simple has not been overlooked.
Charging for 24 hours has helped about 80% of the people on here who claim a hard/soft brick and they have tried ABSOLUTELY EVERYTHING to fix it.
Click to expand...
Click to collapse
See, right- that's what I always hear everybody say on forurms like this... cause it's TRUE. Most people asking a question generally barely know the proper question to ask and when the DO, they don't think to SEARCH for it. (Although I've always found the Xda forum search EXTREMELY lacking; I'd do a search for a term in the xda search and get nothing so I had to go to google and find the proper xda page through IT. It's much better of late, though)
However, it has been my experience that everything everybody always complains about; people asking before even searching themselves, people asking questions but not providing enough relevant information for the questions to be answered, etc... all these "rules of conduct" are based around the avoidance of WASTED TIME/EFFORT. Which I whole-heartedly agree with. I almost never ask about anything on the forums because it's almost ALWAYS faster to find the answer myself. It's usually out there.. so when I DO post a question, I will give a detailed account of my situation, how I got there and where I'm at... so, with all that everybody says about reading BEFORE you post questions why does it always seem like NO ONE EVER READS MY QUESTIONS before answering? For example, this time I was just like- "wow, dude didn't even read the background, gave me a cookie-cutter set of instructions and didn't even TRY to answer my actual question!"
Anyway, as for the QHSUSB download, I have had that before and just a perseverance of starting again from scratch and charging worked. (That's why I asked you to wipe all sony/phone/adb etc software from your pc)
Click to expand...
Click to collapse
For real? You've actually had that before and come out of it? Was it on an xperia device? That means there IS hope beyond JTAG service... galaxys don't have flashmode, know what I'm sayin? I'm thinking maybe if I get the QHSUSB_DLOAD driver qpst or (more likely) qxdm will communicate with the port and I can do something like getting it into flashmode or rebuilding it or just figuring out what happened.
Haven't had much luck finding the drivers, but I haven't really looked that hard yet...
However, I am sure you are aware that the majority of times this happens you are left with a hard brick. Google gives a lot of results on this about Samsung and HTC phones (All of which offer no solutions) but very little for xperia phones.
Click to expand...
Click to collapse
Sure am. Yeah, what led me to post was when every time QHSUSB_DLOAD was even mentioned by galaxy owners, the immediate consensus was that this always means you're bricked and require JTAG repair service. As you say, not much regarding xperia, although the ONE thing I saw was someone who said that THEY heard something about getting the driver and being able to parlay that up into getting it back into flashmode or fastboot mode but that's about it. I'm gonna keep on it...
NB
It is sometimes hard for me to hold the hand of all the users I help. I get between 20-30 PM's a day (Some of which are quite bad mannered because I have not replied within a few hours with a message on how to help them, that does not put me in a good mood) and check the Q&A thread (And general thread for those that cannot post in the correct forum) on a very regular basis in order to help people, but the increase in people not reading and just flashing means I cannot dedicate the time to being a personal assistant to all, you may have see 4 new threads in the Q&A section in the last 24 hours, all made by different users with the same problem, all of which occurred because they were flash happy and tried CM roms without unlocking the bootloader....
Click to expand...
Click to collapse
No doubt... it is sometimes hard for me to ask questions because most times I only end up having to bring the person supposed to be helping me up to speed simply to be able to ask the question and have the answer be (usually, but not ALWAYS) "you're guess is as good as mine". I don't mean you, just so you know; I'm speaking of "how it usually goes".
EDIT
There is still no such thing as flashboot....its called flashmode
Click to expand...
Click to collapse
oh, for sure. flashboot MODE, however- well, there's still no such thing, but at least it's not as blatantly misleading
In the past some users have called these two modes different things, got them mixed up or even thought they were the same thing, that's why I wanted to know which one you meant.
Click to expand...
Click to collapse
I was actually talking about fastmode and fastflash mode, but I would expect you'd never heard of THEM before, either?
Also, the flashtool you linked to in point 1 is the official flashtool for Sony that only works on unlocked bootloaders. The flashtool from the first post in the dev section is the original flashtool by Androxyde and Bin4ry (First developed for the x10) and is the one to use for flashing FTF's and the one you used from your original post.
Click to expand...
Click to collapse
[/QUOTE]
Yeah, I know; I posted that link thinking it said something other than what it did- like there's gonna be a news article about Sony adding support I edited the post and mentioned that and left the link instead of just deleting it. Dunno why.
All that the Sony flashtool can really do is return you back to stock, right? I think I read something like that...
So anyways, I tried it after charging 24hrs but there was no difference. Gonna look into this Qualcomm HSUSB Download driver- ANYONE know ANYTHING about it?
adol.ivxx said:
For real? You've actually had that before and come out of it? Was it on an xperia device? That means there IS hope beyond JTAG service...
Click to expand...
Click to collapse
Yes, but it only happened the once, a fair few years ago before I really had heard of the problem. That's why I can not be quite sure how I fixed it, but it certainly was nothing more than perseverance of trying different things.
I was actually talking about fastmode and fastflash mode, but I would expect you'd never heard of THEM before, either?
Click to expand...
Click to collapse
Not for Sony Xperia devices.
So anyways, I tried it after charging 24hrs but there was no difference. Gonna look into this Qualcomm HSUSB Download driver- ANYONE know ANYTHING about it?
Click to expand...
Click to collapse
Sorry I could not have been more help. I will continue to dig around and ask others I know that might shed more light on this. I will post here again as when I have something you might appreciate. Good luck.
Ur phone is hardbricked
Hi, it's my first post, and I need your help.
I have a Sony Xperia SP C5302, untouched Android 4.1.2 (12.0.A.2.254)
Last day I rebooted the device and it didn't turn on, and I haven't installed anything, just normal use. I tried several things and I could turn it on first with the reset hole on the back (10 seconds), then pressing volume down + power, and the device turned on ok. Later I realize the pc (with PC Companion) doesn't recognize the phone. It's the same pc I always use without issues, and with the original cable. Tried on a different pc, but it's the same, luckily I can charge the phone without problem.
Today I made the factory reset, and the only good thing I got is that now I don't need to do the 10 seconds on the back hole, but I must press volume down + power to turn it on, in fact if I just press power (and not volume down), it vibrates but it doesn't turn on, and it won't turn on again unless I do the 10 seconds on the back. The PC still doesn't recognize the phone.
If it helps, phone was rooted and I was using GravityBox for some tweaks, but it was like that for quite a long time, without any issue.
I'd really appreciate your help!
In your position, I would consider this: (back up important data)
Flash full 254 afresh without rooting or recovery.
Test it. If it works, re-root and install whatever you had previously, and enjoy.
If not - send it to sony centre - probably hardware issues...
Thank you for your help!
I thought the same, but then I realized there's no USB connection, so I can't flash the phone. Even worst, I have the 266 update pending, so I tried that over wifi, but i don't know with it says there was an error, the update never installs, I tried twice.
It's incredible, I had the phone for 4 months, and just like that, it's broken.
Again, thank you for your time, and if there is anything you think I can try, your welcome!
I had a similar problem my solution was to factory reset restore all the system apps I had removed basicly make it look like it had never been rooted then use the unroot and cleanup option in superSU and sent it to Sony who replaced it
Programming is a race between engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
Remove all drivers that you have installed related to android on your computer.
Reinstall all of them.
Try to change from MTP to MSC in USB settings to see if your USB port is still working.
Guys, thank you all for your help, I guess I'll have to live without usb, and forget about flashing. I really liked sony phones
Tl;Dr - my pixel 5a5g got the black screen of death a few months ago. Last night, I tried using the flash tool to try to flash it back to Android from GrapheneOS - so that Google would be willing to fix it maybe. Flashing seemed to fail. Unsure what to try or do next.
---------------
My Pixel has had the black screen of death for a few months now. I'm assuming it is from falling a few feet to the ground. It had a custom ROM - GrapheneOS - on it. Unless I can reflash to stock Android, it sounds like Google/ubreakifix won't look at it, and thus - no chance of repairing it for free or a smaller charge.
The other night, I tried attaching an OTG keyboard to the phone to log in to it. Since the display is black, I'm not sure it worked. I also tried several times to press where I thought the numbers for logging in would be - on my completely black screen. Somehow, I was eventually able to get my PC and Google's flash tool to recognize the phone. However, I might have messed up on some steps - because I think it might be bricked now.
I think I forgot to remove the grapheneOS key via their Web installer before trying to flash android. I used minimal abd tools to unlock the bootloader (and it still says it is unlocked)... When I tried flashing back to stock android using the android web tool, it went through the motions, but then said something like it needs to detect the phone again after flashing. And it wouldn't detect the phone again. Even if I unplugged then replugged the phone. The directions said I shouldn't/wouldn't need to press any keys on the phone for this step, but it just wasn't progressing further... So, I ended up holding the power button and volume down button - and it went into fastboot(?) again - or whatever that does.
I can repeat the steps of going thru the motions of flashing the device now, but now it gives an error saying something like it can't lock the device.
Being that the 5a screen is completely black, I have no idea what is going on - or what to do from here. I've reached out to some local repair places, but honestly, if I can't flash it myself to stock so that Google/ubreakifix would look at it, then it probably isn't worth sinking money into.... There's decent condition used ones around $120 or something out there... And ubreakifix would probably charge between $160 and $200 for screen replacement + labor - and I'm assuming that's not including a motherboard replacement - if necessary.
Ubreakifix said that they would be willing to look at it, but they can't actually do any repairs to it if it isn't running stock Android. They'd charge for the labor, and they'd temporarily use a screen to look at what it is doing/not doing... But wouldn't actually do the screen repair. I'm assuming the phone never flashed completely, but I'm hoping they can tell me if their diagnostic tools work on it - since I imagine it should work -- IF stock Android is actually installed again on it.
I've also looked into doing something like getting a displaylink adapter + display link app so that I can see the screen on the computer... But even after my multiple attempts of logging in to the phone, I can't send app downloads to the phone. Google Play store shows that the phone was "last seen" months ago... And even if I could push the app download, GrapheneOS still requires manual approval from the user to accept/finalize install of the app... Which would be pretty hard to do without seeing the screen. And obviously since I've tried flashing the phone several times last night, i have no idea what the phone is looking like. Probably app downloads are out of the question now.
Apparently you can't normally do display out of any sort with Pixel phones. The rumor I've seen on here and/or reddit is that Google got rid of it years ago, maybe so that they can sell more Chromecasts...
Does anyone have any further suggestions? I could try using scrcpy or whatever it's called, but I probably should have tried to use that before attempting to flash the phone... It's sure hard to give up on something that I spent good money on. I'd like to think there's something I haven't tried yet that I can do to save it...
You could probably try these steps:
1. Open up Device Manager on PC
2. Connect your phone
3. Hold Power + Volume Down
If you have new device in Device Manager, you can do everything with your device like flashing or try "to remove the grapheneOS key".
Edit: I'm dumb and didn't notice that part where you tried this. You should just boot into fastboot and remove that custom AVB key with fastboot erase avb_custom_key, and then reflash the phone on flash.android.com. Hope that helps!