Database Develop

I Hard-Bricked my SGS 3 Mini

Hello, my name is TNSM and i'm new here. I signed up because i can't find anything on the internet that can help me, so i thought maybe someone here may be able to help me.
I have a Samsung Galaxy S3 Mini GT-I8190 and i'm experienced with rooting and flashing custom roms stuff. So, i was looking everywhere for a rom that included the HALO feature and after days of failed research, i found a link on Youtube to download a rom with Halo for my smartphone. I went into the recovery, backed up my current rom, wiped data and performed a factory reset, installed the rom and rebooted the phone... but after i chose the "Reboot" option, the phone never again gave a sign of life. It doesn't turn on, it doesn't show any lights whatsoever, i've tried to charge it overnight, but still nothing, considered buying a USB JIG but didn't work, my cousin says the phone seems like it doesn't even have the bootloader anymore... is my phone more than hard-bricked? Is there a way to wake my phone up again? Just for the record, it has no physical damage, it just seems like it has no software inside, that it's just hardware. By the way, when i connect it to the pc using the usb cable, the pc keeps playing the sound that something was plugged in and that something was plugged out right after, and it loops forever.
I'll give more information about the phone if needed. And i hope someone's able to help me.
- TNSM

TNSM said:
Hello, my name is TNSM and i'm new here. I signed up because i can't find anything on the internet that can help me, so i thought maybe someone here may be able to help me.
I have a Samsung Galaxy S3 Mini GT-I8190 and i'm experienced with rooting and flashing custom roms stuff. So, i was looking everywhere for a rom that included the HALO feature and after days of failed research, i found a link on Youtube to download a rom with Halo for my smartphone. I went into the recovery, backed up my current rom, wiped data and performed a factory reset, installed the rom and rebooted the phone... but after i chose the "Reboot" option, the phone never again gave a sign of life. It doesn't turn on, it doesn't show any lights whatsoever, i've tried to charge it overnight, but still nothing, considered buying a USB JIG but didn't work, my cousin says the phone seems like it doesn't even have the bootloader anymore... is my phone more than hard-bricked? Is there a way to wake my phone up again? Just for the record, it has no physical damage, it just seems like it has no software inside, that it's just hardware. By the way, when i connect it to the pc using the usb cable, the pc keeps playing the sound that something was plugged in and that something was plugged out right after, and it loops forever.
I'll give more information about the phone if needed. And i hope someone's able to help me.
- TNSM
Click to expand...
Click to collapse
You may try to pull off the battery for few mins, then with someone's help hold the 3 buttons for download mode and then plug in the battery...
If you can't turn it in download mode there's no way to fix it, except jtag maybe.

[Q] Bootloop, software or hardware caused?

Hello, Its been a long time since I don't ask anything on the forum, but in this occasion I haven't found any solution to what's happening to my Xperia Z, I'm gonna do my best to present the issue.
A couple of days ago I updated my Xperia (unlocked bootloader) from Existenz 1.5.5 to the latest 3.0 and the phone was completely fine for 2 days until it started shutting down by itself constantly and with no apparent reason, so I started to get worried, the first thing I did was try and reinstall the ROM thinking that I had some something incorrectly, I has no luck with that, on the contrary the phone died on the middle of the installation and it got bricked. My next step was to try do do everything from scratch, flashing the stock rom 10.5.1.A.0.283 to root it, install recovery and try flashing the Existenz after. I managed to do everything with lots of unwanted shuts downs in the middle but I managed. Unfortunately the phone kept on having the same problem so my last option was to try and use the Sony bridge on my mac to try and make a factory reset but it didn't let me because it detected the unlocked bootloader so I relocked it with flashtool, after that I tried again and it worked, it installed the official stock rom .101 and guess what..... same issue again, when I try to turn the phone on it shows the sony logo and turns off, if I try to turn it on connected to the AC it turns on but if I start playing with the menus and options it disconnects again, ofcourse if I turn it on connected and once it's on I disconnect it it shuts down almost instantly, At first I though the problem could be software, then hardware so I tried to check the battery status in the service app and it said good battery health so now I'm completely lost.., I've found this: http://forum.xda-developers.com/xperia-z/help/hardware-fix-xperia-z-charging-booting-t2760911 but I don't know if thats my case. I was gonna go to a sony store and ask them what could be the problem, but now I'm living in Brazil and it'd take lots of time and money to get ir fixed here.
I really need help here, sorry if I posted on an incorrect place.

I just found a video of someone with the exact same problem, in case in helps: https://www.youtube.com/watch?v=zkvLchJ_0oU
UPDATE: I rooted it, install recovery and once im in recovery it doesn't turn off by itself what tells me that may not be a hardware problem, at least not battery related, all this just makes me feel more confused!!
UPDATE 2: I rebooted the phone to load the recovery again and the battery indication went from 89% 2 minutes ago to 11% this second time, maybe it's hardware after all..

Battery.....
TapaTalked from my Xperia™ Z (C660²) running Ultimate PureXZ Ultra!

I seriously don't think is the battery, I think it's something related to the energy but I'm not sure what. As I said before the battery went from 89% to 11% quite fast but when it was at 1% it stayed there for hours, if it was the battery wouldn't it had turned off? after it finally turned off I left it charging for about 12 hr and today morning I try to turn it on without it being connected and no luck, it kept shutting down after the Sony logo. Sometimes when I turn it on with the cable connected it loads the OS and I unlock the lockscreen, diconnect the cable and extraneously it stays on just with the battery power, I manage to put the ScreenOff timeout to 30 mins and it stays on all the time, as long as I don't do certain things like opening the camera, phone or sometimes it just randomly turns off from anywhere. I know it's not the rom because I've tried 4 different ones including the official installed by Sony Bridge....
If the issue is software related what could it be?? the bootloader? the bios power management? battery stats? maybe restoring TA backup(because I just relocked the bootloader using the option o flashtool, not flashing the TA backup)?
I'm concerned about buying a battery, installing it and seeing no change as I've read happened to some guys with the same problem.
I really like my phone but after this I'm not so sure i'll buy another Xperia because this has happened to so many people and apparently there's no solution, my phone is out of warranty and I life in a foreign country (Brazil) so you guys are all I have...

Same Problem Here ... Impossible to flash either from fastboot or from CWM or TWRP
Hi, I am having exactly the same problem. I was trying to revert to stock kernel from CM10.2 and was following one of the many guides here on XDA. The phone was not passing the «SONY» Logo, and immediately after such logo it simply went completely black and the phone is off. After two days of trying several things, including Fastboot of Stock ROM, fastboot of different boot.img files including Doomlord, using Sony Bridge for Mac, all of which did not solve the issue, the problem now is that when I try to flash any ROM, the flashing operation begins and then after approx 15 seconds the phone goes black and switches off. The battery is at 82%, so I am quite sure it is not a battery problem.
I am more and more convinced that the internal filesystem (or simply RAM) needs to be formatted at low level from scratch.
The only problem is that I do not know how to do it: how to do LOW LEVEL Formatting of RAM? Any instructions out there?
Any other suggestion?
Thanks

gcecchini said:
Hi, I am having exactly the same problem. I was trying to revert to stock kernel from CM10.2 and was following one of the many guides here on XDA. The phone was not passing the «SONY» Logo, and immediately after such logo it simply went completely black and the phone is off. After two days of trying several things, including Fastboot of Stock ROM, fastboot of different boot.img files including Doomlord, using Sony Bridge for Mac, all of which did not solve the issue, the problem now is that when I try to flash any ROM, the flashing operation begins and then after approx 15 seconds the phone goes black and switches off. The battery is at 82%, so I am quite sure it is not a battery problem.
I am more and more convinced that the internal filesystem (or simply RAM) needs to be formatted at low level from scratch.
The only problem is that I do not know how to do it: how to do LOW LEVEL Formatting of RAM? Any instructions out there?
Any other suggestion?
Thanks
Click to expand...
Click to collapse
It seems like there's no solution and I don't think my battery is broken so I won't try the Hardware Fix since I don't wanna break my phone more than it already is, tomorrow I'll try to go the a Sony service store and see what they think the problem is, since I unlocked my bootloader and relocked after I think they will be able to see this, I think it ain't gonna be a problem because my warranty was void long time ago, and it's 1 year anyhow.... I hope they recognize it's a sony's fault issue and they decide to fix it with no cost, very unlikely but hoping is free gcecchini, i'll keep you updated, also if you find a solution let me know.

Hi Ringox!!! I'm having exact problem as your's.. This all started when I upgraded to 4.4.4 . First it was giving some weird problem like when opening camera , the phone shuts down. Then a time came the device was not charging.. The device boots up when connected to wall charger. But as soon as charger is removed the phone shut's down. Without connecting the charger when I tried to power on, it shows sony logo for 1 second the shut's down. I tried installing every stock rom , custom rom, kernel etc and it didn't solve the problem. I also bought new battery but same problem. I don't think it's software or hardware or battery problem but may be bootloader is corrupted. May be when we flash bootloader ( as in samsung) we may solve this problem. But I cannot find any tutorial an instruction to flash bootloader.
Also from quickstyler thread I can confirm that I have same problem as him, the sony mobile battey test app shows same error battery temperature -30 C . But his hardware fix didn't work either.
By searching for the problem on youtube, xda, google and other sources I can confirm 1000s of people is getting this problem ..
Please developer and member , help us provide solutions and tips what we can do next...

I have news, after one month waiting for Sony to repair my phone they've finally said it can't be fixed and they said the problem is the motherboard which is approximately 130 dollars plus installation, so I decided to park my Xperia and buy a SGS4. Something interesting that happened is that now the phone starts and sounds, just with a black screen all the time with the backlight ON, maybe they fixed something and broke something else, I don't know. If anyone knows a solution to this rather than changing the motherboard I'd appreciate the answer. I wanna fix it to give it to my mother, but I won't be buying any other Sony smartphone ever again, their service is a disgrace and I couldn't be more unsatisfied with them.

Lumia 710 bricked. Any help?

Ok guys,
as the title says Lumia 710 is bricked.
It had last factory update and everything was working fine. Then i had to mess with it and to try to install Rataplan V9.1.
The process was working ok. By default, bootloader was in DLOAD mode, so in order to install custom ROM i needed to upgrade to Qualcomm. I have upgraded it and installed Rataplan .nb rom to the phone with NSSPro V0.54.
This is when my problems start.
The phone starts with one long vibration followed after few seconds with one short virbtation and thats it. No screen, no system, zip!
When i try to connect it again by usb to check it with NSSPro, it always starts in NAND disk mode. It does not matter do i start it normally on power button or with volume up. Its always in NAND. And it is always stuck. While the phone is connected to USB i can see Qualcomm CDMA Technologies MSM device in device manager but it has yellow mark like the driver is not installed.
I have tried several other roms, and NSS always shows that the rom is successfully installed, but the phone (other than vibration and NAND mode) is dead.
I have also tried all the solutions i could find on the net but no help. Tried, nokia recovery tool, WP recovery tool, Chimera e.t.c. Nothing works. Now i have a problem with NSS. It keeps stucking and beeing unresponsive for every option except Custom OS flash. Whatever else i click it either says tha phone is not detected or the app stucks and shuts itself down.
Is there other tool i can try?
Can i do anything to recover this phone or did i kill it?
PLEASE HELP!!!

Well that sucks and it sucks no one has tried to help here. I'm fair with Android but too new to WP's to probably be much help. Can you pull the battery out of the phone? Might pull it and leave it out a couple minutes then retry. You also might try from a different computer in case something has gone wrong on your computer in terms of port communication or maybe even a virus of some sort. Good luck.

droidzer1 said:
Well that sucks and it sucks no one has tried to help here. I'm fair with Android but too new to WP's to probably be much help. Can you pull the battery out of the phone? Might pull it and leave it out a couple minutes then retry. You also might try from a different computer in case something has gone wrong on your computer in terms of port communication or maybe even a virus of some sort. Good luck.
Click to expand...
Click to collapse
Tried allready every solution that i could find or think of, including things You described. Nothing. I was left with no other option but to send phone to service. They have a box unit with which they should be able to recover phone.
That was 2 days ago. today is third day so i am thinking that my phone has gone beyond repair. Only thing i can do is to wait and see...

Why not...?
Why not send it in real life to a windows phone expert. There should be a place to get phones repaired But, if they say that it isn't possible for them you may have rendered your phone useless. Google should be your mighty friend in this case :crying: I wish you very good luck.

SOS Xperia SP

Hello,
I am looping for assistance and advices.
I wanted to upgrade the phone of my son, for a game, Xperia sp was in 4.3 official Sony, I read several tutorial and I had the idea to pass it into 6.01. So firstly, I did a safeguard with PC software companion but impossible to install it without error (failure configuration) I triée to use titanium as sight in several tutorial, but impossible to use it because it needs that the phone is rooted. I search for a rooter and I find the towelroot application which I install on the phone, and which I launch. I again launch titanium to control that the phone is rooted and it is the case. I start the safeguard of the applications and it is there that begins my problems, the screen remains blocked and the progression of the safeguard remains to zero % and the tactile does not answer any more. I wait a little but nothing changes. I rebooted on the first time with the button power but nothing happens, then with power + volume+ always nothing and finally with the button off in the back of the phone. It shut down, I turn it on it thinking that it was ok but after a few seconds it is blocked again. I tested several times and I always have the same problem.
I dont know what to do anymore.
is the phone recoverable, so yes how?
can I still recover the data of the phone?
I think of a solution, it is to try to install twrp with Fastboot to carry out wipes but if I could have advices before making other mistakes.
I will add that I am beginner on Android (I think that you understood it), I have iPhones of my job.
thank you in advance for your Advices.
Sorry for my bad english.
problem solved.
It is the card SD which blocked the phone

So i suppose you wanted to do a backup of data right? And what do you mean "Blocked"? Phone cannot be turned on?

The phone starts correctly with access to the applications and after a few seconds the screen jams. Solved problem it was the card SD which did not appreciate the use of titanium.

Weird request - Sony Xperia Z3 Compact and Android 4.2.2

I've tried Googling for this and everything keeps coming back to this site, so I figured I'd sign up and see if the good people here can help.
I've got an old Xperia Z3 Compact that I want to downgrade to Android 4.2.2 (I've got a really old app that doesn't work properly on newer versions). I have an even older HTC Desire with CyanogenMod's version of 4.2.2 on it but can't find anything specific for the Sony. I would continue to use the Desire but it destroys batteries (literally, in the time it takes me to go to the bathroom the battery drops from 100% to 92%) and new batteries refuse to charge properly - they seem to charge for a minute or so and then stop charging and the phone trashes them - they'll drop from 50% to 35% in 5 minutes when the phone is in standby mode.
I'm totally new to the concept of changing the ROM in a phone (the Desire, with Cyanogen on it, was given to me by a friend who got bored of it). If there is a single page of instructions to do this I'd really appreciate it - I've tried searching Google and found so many different sites saying different things I'm more confused than I was before.

The oldest firmware version available on the Z3 compact is 4.4 Kitkat so I'm affraid what you're asking for is impossible

hf4al7 said:
The oldest firmware version available on the Z3 compact is 4.4 Kitkat so I'm affraid what you're asking for is impossible
Click to expand...
Click to collapse
That's frustrating. I don't think it will work on 4.4 but maybe it's worth a try. It doesn't work on Android 5 and does on 4.2.2
Is there an idiot's guide to flashing a phone around somewhere? I've never done this before and everywhere I look it seems there's a different way of doing things.

https://forum.xda-developers.com/xperia-z/general/tutorial-how-to-flash-stock-roms-t2240614
https://forum.xda-developers.com/z3-compact/general/list-stock-firmwares-d5803-d5833-t2906706
You should be good with these two links

When you get to the "installing drivers" part of the instructions, during the installation process, it will show a long list. Choose/check:
- Flashmode Drivers
(it's at the top, and then scroll down, down, down ...)
- Xperia Z3 Compact Device Driver
If you get some certificate warning, just click "Okay, install anyway."
One thing about some of the old versions of apps is that they may not write to the external SD Card.

Thanks for the pointers. I'm finally getting to try this out and only getting as far as the bit where it gives me the flash window. It tells me to press the volume down button and then connect the cable. I'm pressing the volume down button, keeping it pressed as I connect the cable, but it's not going any further. I kept it that way for long enough that my thumb got tired pressing the volume button.
Am I doing something silly? I'm using Windows 10, I think it's the 64-bit version.

I worked it out.
The instructions weren't clear (at least not to me) that the phone needs to be connected to the computer during the startup phase of Flashtool, then when it finally gives the indication to disconnect and power off, that's when you disconnect and power off. I had been trying to connect for the first time at that point, and having no end of trouble.

The phone just needs to be off before holding volume down + connecting cable.
I agree that instructions aren't always clear, but understandable. It's hard to think of every scenario .
I hope 4.4 works out for you.