[Q]Can this Tipo be fixed? Bricked for good? - Sony Xperia Miro, Tipo (Dual), J, E

Hi
I have an old Tipo that had Gimlo running it in for a year or two with no problems (as in, I installed it in 2012 or 2013, can't remember). Anyway, I was going to give the phone to my girlfriend as I got a new one, and it seems I accidentally deleted EVERYTHING. I really don't know how I managed to botch up that bad, but I did.
When I boot, I get a vibration, the Sony logo and that's it. If I press volume up or down when pressing the power on, white/green led flashes depending on which I pushed. But basically I cannot access anything on the phone through a PC or any software that I've tried (emma, flashtool, pc companion)...
Flashtool complained something about the phone and MTP (?) and USB debugging mode. Can't post exactly what it says as I don't have access to a PC that has Flashtool. Basically the touch buttons do not react at all.

ruhowned said:
Hi
I have an old Tipo that had Gimlo running it in for a year or two with no problems (as in, I installed it in 2012 or 2013, can't remember). Anyway, I was going to give the phone to my girlfriend as I got a new one, and it seems I accidentally deleted EVERYTHING. I really don't know how I managed to botch up that bad, but I did.
When I boot, I get a vibration, the Sony logo and that's it. If I press volume up or down when pressing the power on, white/green led flashes depending on which I pushed. But basically I cannot access anything on the phone through a PC or any software that I've tried (emma, flashtool, pc companion)...
Flashtool complained something about the phone and MTP (?) and USB debugging mode. Can't post exactly what it says as I don't have access to a PC that has Flashtool. Basically the touch buttons do not react at all.
Click to expand...
Click to collapse
Try this way:
Get the stock ROM ftf and open flash tool :fingers-crossed:
Then, connect your phone and press the power up at the same time.
Then flash the stock rom and follow the step from the flash tool. :fingers-crossed:
Hope it helped.
Good Luck!

Vroyaloko said:
Try this way:
Get the stock ROM ftf and open flash tool :fingers-crossed:
Then, connect your phone and press the power up at the same time.
Then flash the stock rom and follow the step from the flash tool. :fingers-crossed:
Hope it helped.
Good Luck!
Click to expand...
Click to collapse
Still didn't have access to flashtool (I am not on my own PC and I don't have permissions to run things), but I tried sony's own tool with your inspiration and it worked! Thank you thank you thank you! I don't know where tangerang is but if I ever visit the place, I owe you a cup of coffee, a soda or whatever beverage you prefer!

Related

A whole lot of problems with Xperia J - please read

Yesterday, I started unlocking my bootloader on Xperia J ST26i in order to eventually finish with installing ParanoidAndroid 3. It all went successful until I got to the last step of rooting the device. This - http://forum.xda-developers.com/showthread.php?t=2183737 - is the method I used. I was confused when I got to step 16, because the kernel I copied for flash didn't show up. So, I'd finish with two choices after shutting the phone down, having exited CWM Recovery. I would either open CWM again, after seeing LEDs glowing purple/blue in order to press Volume down key to enter CWM - or to ignore and finish seeing grayscreen. Luckily, I was able to find a JB 4.1.2 kernel for my rooted Xperia J, so I put it and flashed it instead of the ICS kernel provided on the thread I referred to. That solved the problem. I had JB 4.1.2 installed and rooted with ROM Manager installed along with SuperSU app. The next step I was going to do was to install a ClockWork Recovery, I hesitated installing PA3 directly without a recovery image. Ironically, CW Recovery is what really made all the problems now. Searching on Google I found a way to boot directly to ClockWork Recovery, I pressed and held the buttons for initiating it but I ended up with literally no way to normally boot the phone. So, I couldn't turn on the phone except in fastboot mode. In fastboot, I whiped all the data, reset to defaults, reinstalled the boot.img and JB kernel, however after all the resets and whipping anything that, according to many sites and devs, should make the phone function again...it failed. After a dozen times of taking out the battery, button combos I ended up not being able to access neither fastboot mode with CWM showing all those options for whipping, installing etc. Only phone's upper LED was working and it blinked red so I recharged the phone, then it was all the same but it'd blink green. After another hour of trying to turn on the phone in any mode, nothing good happened. When I held the power button, it vibrated but after a minute or so only green LED activated. Then I downloaded recovery exit zips that I'd install if ever got to CWM again. I tried once again to directly boot into CWM recovering by holding the power button down and both sides of volume rocker. It blinked light blue, then green and later blue. Device flasher couldn't read the phone, so I opened flash mode. It read it, but any installation of boots or kernels failed because of the phone that either disconnected or simply failed. There was no way for me to put more files on Internal Storage or SD Card, only those LEDs started behaving the way I described. After another twenty times of battery removing, 10 second and 30 s waiting, button combos, anything I could find on Google, nothing changed. Except, suddenly, the computer is able to link with the phone after holding power button for boot that only activated the green/blue/violet LED. Still, no response from flashing program, still failed to enter fastboot, CWM, direct CWM Recovery etc. But, now when my phone is, let's say, turned on with green or blue light, I can access SD Card and Internal Storage via Windows Explorer. Just below the hard drives, I can see my phone. Great? No, it's not Xperia J as it should be, PC detects Xperia Tipo. I also noted that it's mistaken SD Card for Internal Storage... Let's see what happens when I remove SD card from the device. Please help...
Bricked
And yes, this means it's bricked. Can't boot into CWM or anything. It's only good as a storage unit, energy consuming or as a brick. I got this phone in January so please don't tell me it's irreversibly hard bricked.
dave96m said:
And yes, this means it's bricked. Can't boot into CWM or anything. It's only good as a storage unit, energy consuming or as a brick. I got this phone in January so please don't tell me it's irreversibly hard bricked.
Click to expand...
Click to collapse
Okay, so first calm down. Any sign of life means it's not hard bricked but just soft bricked.
1st download flashtool: link
2. download ur stock ftf link
3. flash it with flashtool
and u should be fine again, back to stock with a fresh phone.
Can't fastboot device - remember: button combos don't work
I've also found some solutions for more severe soft-bricking, by the way. Anyway, how to make phone open fastboot? I've said it's unresponsive to all of the button combo commands. Though, I tried one more time.
Opened the flashtool... Held volume up and plugged in the USB cable...
17/009/2013 22:09:51 - INFO - <- This level is successfully initialized
17/009/2013 22:09:51 - INFO - Flashtool Version 0.9.10.1 built on 2013-01-09 19:49:47
17/009/2013 22:09:51 - INFO - You can drag and drop ftf files here to start flashing them
17/009/2013 22:09:57 - INFO - Device disconnected
17/010/2013 22:10:12 - INFO - Device connected with USB debugging off
17/010/2013 22:10:12 - INFO - For 2011 devices line, be sure you are not in MTP mode
Immediately, upper LED started glowing green, then it turned itself off after a minute. The phone is still connected.
Remember to pull up battery (and pull in of course ) than go to flashtool, fastboot PWR + Vol Up.
Solved
http://forum.xda-developers.com/showthread.php?p=41506173#post41506174 See my last post, scroll down. Thanks for help, guys
sony xperia j - alarm problem
Hi guys,
I bought Sony Xperia J and 2 months ago I upgraded the Android to the latest version 4.1.2 (Jelly Bean).
After the upgrade the Alarm on the phone does not go off, it starts to ring (the alarm) only when I press the button to unlock the phone, I've read somewhere that when the screen is off the clock is not refreshes properly or something like that.
Can you please, help me?
Regards
Lol I know that feel bro.... It happened to me few days ago but no worries i just flashed the firmware using flashtool whenever i failed. Now i'm happy with my CM10 with vengeance kernel... its not the phone that's causing the problem its up to us how we handle it and i didnt find PA3 that interesting it was too laggy for me...
I didn't experience any of such problems that you have, but still listen to the man's advice. Install CM10. It speeds up your device, gives you options, frees your Android. My friend knows the feeling of switching from iPhone to Nexus 4 and he's like he's enlightened or something, well once again, the feeling is the same if you switch from stock Android to CM or Paranoid. I suggest you install CM because Paranoid made me a lot of problems when installing even though I did everything right, and people claim that CM is more stable...
http://forum.xda-developers.com/showthread.php?t=1997251

Bootloop Z3 CM12.1 nightly/M5 9.0 - halp?

Hm. Not good.
My Z3 has an unlocked bootloader and is rooted. It runs the latest CM 12.1 nightly and today I had the brilliant idea of flashing the M5 V9.0 kernel.
After flashing the kernel, my phone got into the much feared bootloop. Shows Sony on the screen, screen goes black, shows Sony on the screen, screen goes black, rinse/repeat. No flashing LED, no way (that I know of) to get into CM recovery.
Any thoughts on how to revive my Z3?
Or will this turn out to be one of those expensive mistakes?
Errrwin said:
Hm. Not good.
My Z3 has an unlocked bootloader and is rooted. It runs the latest CM 12.1 nightly and today I had the brilliant idea of flashing the M5 V9.0 kernel.
After flashing the kernel, my phone got into the much feared bootloop. Shows Sony on the screen, screen goes black, shows Sony on the screen, screen goes black, rinse/repeat. No flashing LED, no way (that I know of) to get into CM recovery.
Any thoughts on how to revive my Z3?
Or will this turn out to be one of those expensive mistakes?
Click to expand...
Click to collapse
Oh mate, just keep it easy. You will fix your phone in ten minutes. I have done that so many times that I hardly remember.
If you can boot into recovery, you will need to flash CM12 or any custom rom again. Make sure you wipe your data beforehand from recovery.
If you can not boot into recovery,You will need to flash FTF file using FLASHTOOL .
This is one thing you MUST not forget . ALWAYS make sure you flash the right FTF for your device. DO not flash it for another device or you might end up making an expensive mistake.
Flashtool
http://forum.xda-developers.com/showthread.php?t=920746
Download it from here
http://www.flashtool.net/index.php
How to use flashtool
http://forum.xda-developers.com/showthread.php?t=2658952
http://forum.xda-developers.com/xperia-l/general/xperia-l-how-to-flash-tool-unlocking-t2337955
REMEMBER TO DOWNLOAD AN FTF FROM YOUR DEVICE GENERAL SECTION as the guides are for different devices and the process is same expect FTF file.
Now flashtool even allows you to download FTF from the app itself.
Quote me back in case you still need help!
Good Luck
Hnk1 said:
Oh mate, just keep it easy. You will fix your phone in ten minutes. I have done that so many times that I hardly remember.
Click to expand...
Click to collapse
I suppose the hardest part is getting hold of a Windows computer.
Thanks a lot, I'll report back when I get the chance to do this. :good:
make sure you have the fastboot drivers installed for your device on the computer, turn the phone off, plug it into the computer, hold down the volume up key and turn it on, it should then go into fastboot mode wher eyou can flash the cm12 kernel to the device
if that fails then you might need a full install from scratch which is what the above suggested
Errrwin said:
I suppose the hardest part is getting hold of a Windows computer.
Thanks a lot, I'll report back when I get the chance to do this. :good:
Click to expand...
Click to collapse
Sure, feel free to quote me any time. I'd be glad to help.
Richy99 said:
make sure you have the fastboot drivers installed for your device on the computer, turn the phone off, plug it into the computer, hold down the volume up key and turn it on, it should then go into fastboot mode wher eyou can flash the cm12 kernel to the device
if that fails then you might need a full install from scratch which is what the above suggested
Click to expand...
Click to collapse
Cheers mate for your suggestion. I didn't go in details as I felt it might be a bit confusing for him to follow so many instructions.

[HELP] Bricked Z3 [D6603]

Hi all,
Thanks for your help in advance.
I think I've bricked my phone, however I'm not sure whether it's recoverable or not.
What I did, was flash my phone back to it's original ROM and rooted using the guide in a sticky on this board 'D66XX 5.0.2/5.1.1 Flashable stock Lollipop pre-rooted collection & XZ dualrecovery'
This was fine, and it booted fine, I installed root checker and confirmed that it was rooted.
I then downloaded the Official Cyanogen 12.1 Nightly build from their website, cleared cache/dalvik etc.. and attempted to flash that using TWRP. I had an error, which was something along the lines of "E:Error executing" and this was followed by "This device is leo".
I googled a little bit and found that I had to modify the 'updater-script' file in the nightly .zip in order to flash, so I did this and it seemed to install fine with no errors..
I then rebooted, and since then I've had no response from my phone. No LEDs on charging (after an hour or so). No response from holding any combination of Power/Volume buttons, and even the hard reset button located inside the SDCard cover doesn't cause any vibrations from the handset.
I'm not sure where else to go.. After a lot of searching a lot of people are suggesting to leave it charging and then try again after a long charge. I'm wondering what other people would suggest in my situation, is my handset recoverable?
Any help is greatly appreciated! Cheers
Sam
Hi, if your phone's bootloader isn't unlocked this is most likely why it's not booting up. I once installed a ROM on my phone and skipped the line where it said the bootloader needed to be unlocked(I realised this after reading through the install instructions again), I then used the flash tool to install a stock ROM and the phone was fine again, after that I unlocked the bootloader reinstalled that custom ROM that needed an unlocked bootloader and it worked. If you don't know how to do any of this an are just too lazy to find the links that guide you through this I'll find it for you and post it here(you will wait a while though). Hope this helps
GenericBridge said:
Hi, if your phone's bootloader isn't unlocked this is most likely why it's not booting up. I once installed a ROM on my phone and skipped the line where it said the bootloader needed to be unlocked(I realised this after reading through the install instructions again), I then used the flash tool to install a stock ROM and the phone was fine again, after that I unlocked the bootloader reinstalled that custom ROM that needed an unlocked bootloader and it worked. If you don't know how to do any of this an are just too lazy to find the links that guide you through this I'll find it for you and post it here(you will wait a while though). Hope this helps
Click to expand...
Click to collapse
Right.. so first of all, you're correct.. my bootloader is still Locked, as I did not unlock it.
The rest you are totally wrong about, I am unable to get any response from the phone whatsoever.. There's no bootloop, there's no response from screen, no LEDs, no vibrations, nothing. The PC (including Flashtool) doesn't recognize the phone. So flashing is kind of impossible in it's current state.
I've left it overnight (since my post) connected to a wall charger and still nothing so far. Going to leave it charging just in case it wants to resurrect itself at some point (fingers crossed).
Strickened said:
Right.. so first of all, you're correct.. my bootloader is still Locked, as I did not unlock it.
The rest you are totally wrong about, I am unable to get any response from the phone whatsoever.. There's no bootloop, there's no response from screen, no LEDs, no vibrations, nothing. The PC (including Flashtool) doesn't recognize the phone. So flashing is kind of impossible in it's current state.
I've left it overnight (since my post) connected to a wall charger and still nothing so far. Going to leave it charging just in case it wants to resurrect itself at some point (fingers crossed).
Click to expand...
Click to collapse
Does your phone get warm at all while it's in this state? Also does it not get picked up at all by your computer or does it just come up as an unrecognized device? I'm going to assume your phone might be on, in which case I'd recommend holding in the Vol+ button and then the off button, this will force the phone to shutdown if it's on, if your phone vibrates three times then it's definitely off now and you should try seeing if you can go into fastboot or flashmode mode using a computer if that doesn't work then I'm sorry but I think your phone might just be too far gone.
GenericBridge said:
Does your phone get warm at all while it's in this state? Also does it not get picked up at all by your computer or does it just come up as an unrecognized device? I'm going to assume your phone might be on, in which case I'd recommend holding in the Vol+ button and then the off button, this will force the phone to shutdown if it's on, if your phone vibrates three times then it's definitely off now and you should try seeing if you can go into fastboot or flashmode mode using a computer if that doesn't work then I'm sorry but I think your phone might just be too far gone.
Click to expand...
Click to collapse
It did come up as "Unknown Device (Device Descriptor Request Failed)", but no longer does, I'm assuming that it WAS on, but now the battery has run out and it's not charging.
I did try an "adb devices" command when it was plugged in previously but it did not list my device, and as far as I know I have all the correct drivers installed, as I used flashtool to flash CM 12.1.
I can no response from volume/power buttons with any combination as per OP.
*EDIT* The device does not raise in temperature either was connected to USB/Wall Charger
OK So I have an update..
I've removed the back of my phone, removed battery connector and replaced, and now when I connect to my Laptop using USB, The device is recognised as "SEMC Flash Device", however when holding the Volume Down button when connecting I do not have a Green LED, it shows a Red LED for roughly 2-3 seconds and then that dissappears.
Flashtool kind of "half recognises" my phone as per the following:
31/050/2015 14:50:55 - INFO - Device connected with USB debugging off
31/050/2015 14:50:55 - INFO - For 2011 devices line, be sure you are not in MTP mode
and it also shows:
31/052/2015 14:52:19 - INFO - List of connected devices (Device Id) :
31/052/2015 14:52:19 - INFO - - HID\VID_0FCE&PID_D1AC\6&8FB5D7D&0&0000 Driver installed : true
31/052/2015 14:52:19 - INFO - - USB\VID_0FCE&PID_D1AC\5&88A806&0&1 Driver installed : true
31/052/2015 14:52:19 - INFO - List of ADB devices :
31/052/2015 14:52:19 - INFO - - none
31/052/2015 14:52:19 - INFO - List of fastboot devices :
31/052/2015 14:52:19 - INFO - - none
ADB doesn't recognise and neither does Sony PC Companion, but surely this is progress in the right way? If it's now being recognised as an SEMC Device
Strickened said:
OK So I have an update..
I've removed the back of my phone, removed battery connector and replaced, and now when I connect to my Laptop using USB, The device is recognised as "SEMC Flash Device", however when holding the Volume Down button when connecting I do not have a Green LED, it shows a Red LED for roughly 2-3 seconds and then that dissappears.
Flashtool kind of "half recognises" my phone as per the following:
31/050/2015 14:50:55 - INFO - Device connected with USB debugging off
31/050/2015 14:50:55 - INFO - For 2011 devices line, be sure you are not in MTP mode
and it also shows:
31/052/2015 14:52:19 - INFO - List of connected devices (Device Id) :
31/052/2015 14:52:19 - INFO - - HID\VID_0FCE&PID_D1AC\6&8FB5D7D&0&0000 Driver installed : true
31/052/2015 14:52:19 - INFO - - USB\VID_0FCE&PID_D1AC\5&88A806&0&1 Driver installed : true
31/052/2015 14:52:19 - INFO - List of ADB devices :
31/052/2015 14:52:19 - INFO - - none
31/052/2015 14:52:19 - INFO - List of fastboot devices :
31/052/2015 14:52:19 - INFO - - none
ADB doesn't recognise and neither does Sony PC Companion, but surely this is progress in the right way? If it's now being recognised as an SEMC Device
Click to expand...
Click to collapse
Do as follows:
1. make sure your phone is off ( hold down volume+ and than press the power button, hold them down like that until the phone vibrates 3 times)
2. run flashtool as an administrator (right mouse click on the flashtool icon > Run as an administrator) ,once flashtool opens click on the lightning icon, select "OK" to chose the flashmode, and than select your stock z3 ftf file at the top ( if you have one, if not then download xperi firm and use it to download stock z3 rom )
3. after selecting the stock rom make sure APPS_LOG and USERDATA (on the upper right side) are ticked. Than go ahead and select flash (bottom right corner)
4. wait for flashtool to do its thing, eventually it will prompt you to plug in your phone
5. once that happens go ahead and hold down the volume down button, and while still holding it plug your phone to an usb cable, ( which is already connected to your pc )
6. after that flashtool will start flashing the rom
7. dont touch anything until the phone boots itself up
Brontok said:
Do as follows:
1. make sure your phone is off ( hold down volume+ and than press the power button, hold them down like that until the phone vibrates 3 times)
2. run flashtool as an administrator (right mouse click on the flashtool icon > Run as an administrator) ,once flashtool opens click on the lightning icon, select "OK" to chose the flashmode, and than select your stock z3 ftf file at the top ( if you have one, if not then download xperi firm and use it to download stock z3 rom )
3. after selecting the stock rom make sure APPS_LOG and USERDATA (on the upper right side) are ticked. Than go ahead and select flash (bottom right corner)
4. wait for flashtool to do its thing, eventually it will prompt you to plug in your phone
5. once that happens go ahead and hold down the volume down button, and while still holding it plug your phone to an usb cable, ( which is already connected to your pc )
6. after that flashtool will start flashing the rom
7. dont touch anything until the phone boots itself up
Click to expand...
Click to collapse
The phone won't boot into Flashmode, or fastboot mode, or recovery mode.. Nothing, no Sony logos, no response, no vibrations.
Strickened said:
The phone won't boot into Flashmode, or fastboot mode, or recovery mode.. Nothing, no Sony logos, no response, no vibrations.
Click to expand...
Click to collapse
Make sure the phones is turned off, then open flash tool, connect the cable to your phone while holding the volume down button, see if flashtool will say "device connected in flashmode".. if it does than you can proceed with the previous instructions, from top to down.
The problem you now have I think is you have a custom kernel installed on a locked bootloader device, with a now completely dead battery.
I don't know if it will charge in this state as I think the kernel controls charging, and as your kernel won't function with a locked bootloader, it's not going to charge either. If it's not going to charge at all, it's not going to have enough power to get into flash mode to flash a stock ftf.
The red led means there's not enough power . . . I'm wondering if you could get hold of another battery with some charge in it, if it would then allow flash mode?
I think your phone was frozen when you were trying initially, and it just stayed that way until it went dead.
I'm no expert, but I'd be willing to try if it was me, seeing as you've already dismantled it anyway.
Somebody correct me if I'm wrong, I hope there's an easier way than this.
MickieH said:
The problem you now have I think is you have a custom kernel installed on a locked bootloader device, with a now completely dead battery.
I don't know if it will charge in this state as I think the kernel controls charging, and as your kernel won't function with a locked bootloader, it's not going to charge either. If it's not going to charge at all, it's not going to have enough power to get into flash mode to flash a stock ftf.
The red led means there's not enough power . . . I'm wondering if you could get hold of another battery with some charge in it, if it would then allow flash mode?
I think your phone was frozen when you were trying initially, and it just stayed that way until it went dead.
I'm no expert, but I'd be willing to try if it was me, seeing as you've already dismantled it anyway.
Somebody correct me if I'm wrong, I hope there's an easier way than this.
Click to expand...
Click to collapse
Thank you for your suggestions, unfortunately I'm unable to get a battery with charge, and have therefore give up.. I will accept that I have bricked my phone beyond recovery, and will learn from my mistakes.
Strickened said:
Thank you for your suggestions, unfortunately I'm unable to get a battery with charge, and have therefore give up.. I will accept that I have bricked my phone beyond recovery, and will learn from my mistakes.
Click to expand...
Click to collapse
Seems a shame to give up. There's nothing wrong with the hardware by all accounts.
You can get a new battery off ebay for £10 to £15 and they're factory charged to at least 50%.
http://pages.ebay.com/link/?nav=item.view&id=291420999095&alt=web
It may or may not work, but I'd rather try than bin a couple of hundred pounds worth of phone.
Whatever you decide, I'll help if I can. I love my Z3, even more so than my Z5 right now.
Good luck either way,
Mick
Edit:
I'd even go so far as to say, if you still have the complete phone, post it to me and I'll see what I can do with it. I'll post it you back when I'm done, and if I can fix it, it's only gonna be a new battery at the most. You can't really lose, it's not working as it is.
I'd cry if I bricked my Z3, honestly. I'd like to help.
this happen to me before, same like your phone and i think it brick cos system partition already mess up...
lucky me i still have warranty on that time so i sent to SC and change new motherboard....
whatever i do, still no succeed, just blink red led
i think u need to sent it to SC, don worry they cannot detect ur phone rooted or UB cos motherboard already fried up....
hahahaha
MickieH said:
Seems a shame to give up. There's nothing wrong with the hardware by all accounts.
You can get a new battery off ebay for £10 to £15 and they're factory charged to at least 50%.
http://pages.ebay.com/link/?nav=item.view&id=291420999095&alt=web
It may or may not work, but I'd rather try than bin a couple of hundred pounds worth of phone.
Whatever you decide, I'll help if I can. I love my Z3, even more so than my Z5 right now.
Good luck either way,
Mick
Edit:
I'd even go so far as to say, if you still have the complete phone, post it to me and I'll see what I can do with it. I'll post it you back when I'm done, and if I can fix it, it's only gonna be a new battery at the most. You can't really lose, it's not working as it is.
I'd cry if I bricked my Z3, honestly. I'd like to help.
Click to expand...
Click to collapse
As much as I'd love to trust you, and I'm sure you're a man of your word, I wouldn't risk sending it out to someone I don't know.. Who's to say I'd get it back? Bricked or not it's money. I don't mean to offend you.
Buying parts that only possibly fix the issue is currently out of the question to due finances, but is a possibility further down the line.
Thank you for all your help, and if I ever do manage to fix it, or require more help I'll be sure to come back again, you've been a great help.
Cheers
Strickened said:
As much as I'd love to trust you, and I'm sure you're a man of your word, I wouldn't risk sending it out to someone I don't know.. Who's to say I'd get it back? Bricked or not it's money. I don't mean to offend you.
Buying parts that only possibly fix the issue is currently out of the question to due finances, but is a possibility further down the line.
Thank you for all your help, and if I ever do manage to fix it, or require more help I'll be sure to come back again, you've been a great help.
Cheers
Click to expand...
Click to collapse
Lol, it's ok. I don't offend that easily, but I did laugh, so thanks for that. Was probably a stupid offer anyway, thinking about it. Perhaps it's me who's too trusting lol. Funny thing is, I would have sent it back, fixed or no, but that's just me. I'm sure there's plenty of people out there who would like to rinse you of a Z3, but me, I've already got one. And a Z5. And a Z4 Tablet, oh and my old Z1 which I gave to my daughter. I've even still got my old Arc S. Either way, good luck. I hope you do get it sorted. Just don't bin it.
As for the battery. I bet any money you'd be able to flash it IF you can get a battery in it with some charge.
Here's a counter offer: I fixed a Z3 for a friend of mine a few months ago. I'll ask him if I can have his spare battery. I made one good Z3 out of two broken ones you see, for him. If he let's me have it, I'll post it to you free of charge. Even if it doesn't work, at least we tried.
MickieH said:
Lol, it's ok. I don't offend that easily, but I did laugh, so thanks for that. Was probably a stupid offer anyway, thinking about it. Perhaps it's me who's too trusting lol. Funny thing is, I would have sent it back, fixed or no, but that's just me. I'm sure there's plenty of people out there who would like to rinse you of a Z3, but me, I've already got one. And a Z5. And a Z4 Tablet, oh and my old Z1 which I gave to my daughter. I've even still got my old Arc S. Either way, good luck. I hope you do get it sorted. Just don't bin it.
As for the battery. I bet any money you'd be able to flash it IF you can get a battery in it with some charge.
Here's a counter offer: I fixed a Z3 for a friend of mine a few months ago. I'll ask him if I can have his spare battery. I made one good Z3 out of two broken ones you see, for him. If he let's me have it, I'll post it to you free of charge. Even if it doesn't work, at least we tried.
Click to expand...
Click to collapse
I might be able to get a battery today actually, a friend of mine has a z3 and he's looking to sell it, but before he does he's going to borrow it to me in order to use his battery! I may just be in luck.
If I do manage to get the battery, I'll be sure to update this post with the verdict. The only worry is that if there's any cracks in the glass at the back, I won't be able to get the battery without completely ruining his phone, so don't want to do that.
I know that my back piece is completely shattered, so if I do manage to get the phone working after all, I'll have to source a new back lol.
Also, back to the topic of trust.. It's not that I don't trust you personally, I just don't trust the internet! I greatly appreciate the offer, and if this battery doesn't working out for me I'd gladly appreciate any help from you in the future.
Thanks again!

Bricked Xperia Z3v with locked bootloader, can't enter recovery or flash mode

Hi guys. So I have been going through xda and Google for hours and hours trying solutions, to no avail. I almost never post on forums for help because I can usually find the solution. Not this time. This is my last resort next to throwing my phone out a window or praying for death's sweet release.
The facts: I have a rooted Xperia Z3v. I tried to upgrade TWRP in order to follow some directions on upgrading to Nougat. I flashed TWRP from 2.8.X.X to 3.X.X.X. I rebooted and it never made it to the Sony logo. Now, if I plug the phone in to either a wall socket or PC it vibrates, endlessly at three second intervals, each time with red LED. If I try to enter flash mode, then its the same but with a brief green led after the red. I can enter fastboot (the only way to stop it vibrating while plugged in) and my PC sees it, including Flashtool, but since my bootloader is locked permanently, I can't really do much with it.
When plugged into the wall-charger, I noticed that the charger's LED changes from "Active" to "Inactive" with every vibration. I'm pretty sure I'm in a reboot loop. The screen is totally dead and there's no logo, but every three seconds it kills it self and comes back.
I have tried everything I could think of.
What I have:
I have the stock firmware ready to go
I have TWRP backups on SD card and PC
I have Flashtool
I think my drivers are good, but not 100% sure
I can fastboot
I'm at my wit's end and losing hope.
Please, I'm open to any suggestions at all.
There is a chance to save your phone 50% this trick might work for your phone sort of .
First i need some answers
1.If you go to flash mode the phone vibrates right is it detectable by your pc at that time.
2.did you Try hard reset not by the vol button press but the very sophisticated button under the sim tray.
3.https://forum.xda-developers.com/z3/development/nougat-7-1-1-android-source-project-t3532346
try this I know this is not for your phone but you will be able to actually boot your phone or atleast take a rest for what the heck is going on with your phone
4.If none of the solutions work disscuss with me i am happy to help
Same thing here. Flashed wrong ROM via TWRP.
As a result, immediate loop (repetitive vibration, led blinking red) when connected via USB. No recovery access. Only fastboot access (blue led).
Locked bootloader.
Flashtool:
- tried flashing kernel.sin extracted from a stock ftf - no good (locked bootloader, unlocking requires flashboot which is not accessible).
- tried flashing system.sin extracted from a stock ftf - no good, flashtool says
INFO - Flashing selected system
and immediately after that
INFO - Please check the log before rebooting into system
So it clearly doesn't do anything. Any other approaches to try?
Tech core said:
First i need some answers
1.If you go to flash mode the phone vibrates right is it detectable by your pc at that time.
Click to expand...
Click to collapse
Flashmode does not work, it starts cycling immediately.
Tech core said:
2.did you Try hard reset not by the vol button press but the very sophisticated button under the sim tray.
Click to expand...
Click to collapse
Yes, certainly.
Tech core said:
3.https://forum.xda-developers.com/z3/development/nougat-7-1-1-android-source-project-t3532346
try this I know this is not for your phone but you will be able to actually boot your phone or at least take a rest for what the heck is going on with your phone
Click to expand...
Click to collapse
Can't flash anything, so can't try it.
Tech core said:
There is a chance to save your phone 50% this trick might work for your phone sort of .
First i need some answers
1.If you go to flash mode the phone vibrates right is it detectable by your pc at that time.
2.did you Try hard reset not by the vol button press but the very sophisticated button under the sim tray.
3.https://forum.xda-developers.com/z3/development/nougat-7-1-1-android-source-project-t3532346
try this I know this is not for your phone but you will be able to actually boot your phone or atleast take a rest for what the heck is going on with your phone
4.If none of the solutions work disscuss with me i am happy to help
Click to expand...
Click to collapse
I bought an M4 Aqua to keep me going for now as they're cheap. The E2306 is unrootable with 6.0.1 and I don't want to downgrade to Loli so no possibility to butt**** this one. If s300pmu1 and you figure it out, I'll do the same to mine.
TheControlled said:
I bought an M4 Aqua to keep me going for now as they're cheap. The E2306 is unrootable with 6.0.1 and I don't want to downgrade to Loli so no possibility to butt**** this one. If s300pmu1 and you figure it out, I'll do the same to mine.
Click to expand...
Click to collapse
I didnt get your comment brief it to me

XZP G8142 Bootloop

Hi, so yesterday my phone went into bootloop. I believe it happened while the phone was on low battery and I put it in stamina mode (which I never do otherwise) and maybe there was an update waiting, not sure.
Regardless, it was in bootloop, I did some digging and got flashtools, an older firmware, the usb drivers and after many hours I was able to flash it, not selecting any of the options under wipe. It didn't fix it, then I selected all options in wipe except userdata and ssd, didn't work. Then I gave up and tried the xperia companion's software repair, it didn't work, then I let the battery drain overnight and charged it a bit this morning, turned it on, still in bootloop.
Can anyone help me out here? I really did not want to upgrade in this round (xperia 1 is great but I'd rather wait for a premium or 2 version; plus release date isnt even known), and I really did not want to lose the data I had, but too late for that now.
I'm not super familiar with flashing and all that, but I believe it is bootlocked as Sony's emma tool says it is. I don't know what bootlocked is, I thought it meant locked to a carrier (which mine is not) but I guess it does not mean that.
Anyways, please help! I'm using my busted up z5 premium for now
fissure said:
Then I gave up and tried the xperia companion's software repair, it didn't work,
Click to expand...
Click to collapse
If your phone hasn't been bootloader unlocked then Xperia Companion will be your best route forward. When you say it doesn't work, what happens?
There are some instructions here
The phone needs to be turned off completely. Hold the power and volume up untill the phone vibrates three times.
Start Xpreia companion and follow the repair instructions. When it asks for you to connect the phone, plug the USB in whilst holding the volume up(+). Once the software has started you can let go.
If you are using Windows10 it might be a driver issue, as 10 fails to install drivers, but doesn't tell you. So start it in safe mode and look for 'driver signing disabled'
Thanks for replying!
When I say Xperia Companion doesn't work, I mean that I was able to successfully go through the repair option and am still in bootloop afterwards; it didn't resolve the problem.
fissure said:
Thanks for replying!
When I say Xperia Companion doesn't work, I mean that I was able to successfully go through the repair option and am still in bootloop afterwards; it didn't resolve the problem.
Click to expand...
Click to collapse
You're not describing what doesn't work. The phone doesn't boot at any point before you connect it to Xperia Companion, you put the phone into flash mode.
It doens't need to boot to get into flash mode. You just need to connect it to the PC with volume up pressed. If you can't get the phone to be recognised by Companion, you may be missing the drivers.
Try installing it with 'driver signing disabled'
Didgesteve said:
You're not describing what doesn't work. The phone doesn't boot at any point before you connect it to Xperia Companion, you put the phone into flash mode.
It doens't need to boot to get into flash mode. You just need to connect it to the PC with volume up pressed. If you can't get the phone to be recognised my Companion, you may be missing the drivers.
Try installing it with 'driver signing disabled'
Click to expand...
Click to collapse
Ok let me try to be more clear:
The phone is currently in a state that when it is turned on it boots to the Sony logo screen, stays there for about 25seconds, then restarts, repeat ad infinitum.
I am able to proceed with a software repair in Xperia Companion by selecting the device cannot connect then choosing the device type as a phone. I have connected the phone, while it is off, while pressing the volume key at the same time. Companion proceeds to repair the phone, took 10-25min. That process completes successfully within Companion. After which I disconnect my phone, turn it on, and I am still in a bootloop.
The point is, I have flashed through flashtool without problem resolution, I have repaired via Companion without resolution. Those steps were done correctly, but the bootloop persists. I'm looking for new suggestions to resolve the bootloop.
fissure said:
Ok let me try to be more clear:
The phone is currently in a state that when it is turned on it boots to the Sony logo screen, stays there for about 25seconds, then restarts, repeat ad infinitum.
I am able to proceed with a software repair in Xperia Companion by selecting the device cannot connect then choosing the device type as a phone. I have connected the phone, while it is off, while pressing the volume key at the same time. Companion proceeds to repair the phone, took 10-25min. That process completes successfully within Companion. After which I disconnect my phone, turn it on, and I am still in a bootloop.
The point is, I have flashed through flashtool without problem resolution, I have repaired via Companion without resolution. Those steps were done correctly, but the bootloop persists. I'm looking for new suggestions to resolve the bootloop.
Click to expand...
Click to collapse
Sorry, I didn't read your first post completely, my bad.
It sounds like a problem with the boot partition, but I don't understand how the Companion fails to spot it's broken as it usually wipes and re-wrties everything.
Try lettig the battery run out, so it's completely flat, won't start or power up, then charge it to 100% while turned off. Then try again.
I've never heard of Companion failing a repair on a bootlocked device before, so there'a chance it's a hardware issue.
I've tried charging it to full and using xperia companion, it still does not work.
One thing I don't think I mentioned is that when connecting the phone to the computer, xperia companion says the device is locked and it won't proceed with the repair. So I have to start Companion and choose the my device cannot be detected option and repair that way, which as I mentioned earlier does not resolve the bootloop issue.
Didgesteve said:
Sorry, I didn't read your first post completely, my bad.
It sounds like a problem with the boot partition, but I don't understand how the Companion fails to spot it's broken as it usually wipes and re-wrties everything.
Try lettig the battery run out, so it's completely flat, won't start or power up, then charge it to 100% while turned off. Then try again.
I've never heard of Companion failing a repair on a bootlocked device before, so there'a chance it's a hardware issue.
Click to expand...
Click to collapse
From what I know flashtool doesn't work and u need to use newflasher in order to flash properly. I tried flashtool one time for the xz premium and ended up not working till I used new flasher
Same problem after upgrade on low power and now bootlop. any variants?
I concur. Flash tool does not work for xz premium. You need to use new flasher. Do that and then see what happens and then we can go from there

Categories

Resources