Database Info

[Q] RX_TIMEOUT + Trouble with ODIN Flash

Okay so yesterday I decided that I wanted to restore the factory EP4 ODIN package from imnuts' website so that I can factory upgrade to FP1 and re-root.
So I downloaded the factory image and the PIT file and started the flash process with ODIN - yes, all checkboxes were selected appropriately. Well about 10 seconds into the flash, a little red message popped up on the top left corner of my phone while in DL mode that says "RX_TIMEOUT". However, the flash continued on to eventually (after about an hour) succeed.
When I went to boot up my phone, I got a Samsung logo for about an hour. Pulled the battery, tried again, same thing. Tried the flash again, same thing. Tried a few more times (each time taking 30-50 minutes, sometimes an hour) and same thing. Downloaded EE4 and tried that - same thing.
Here are the things I've tried:
- flash with battery in AND out
- flash with PIT file and without
- downloaded the EP4 image again, in case of bad download
- downloaded EE4 and tried to flash it (same result)
- let the phone charge for a bit
- tried ALL USB ports
A few flashes ago, I ended up in factory recovery (thought that was a good sign) but when I clicked reboot, I got the Sammy logo again.
EDIT: Well, after the last failed flash, I lost download mode it's toast. Any advice?

What version of Odin are you using?
Does the charging icon come up if you plug it into the wall? Maybe the cable is bad.
I've noticed that either my cable, or the mini usb port on the phone are going bad. If I move the cable/phone even slightly, it loses USB connection with the comp. Now I make sure there is a good connection, and I don't move the phone/cable AT ALL when I am flashing via ODIN.
edit: this is actually being discussed in another thread RIGHT NOW: http://forum.xda-developers.com/showpost.php?p=24412728&postcount=290

I would guess cable, though I would have tried a new cable before going through so many bad flashes.

Thanks for the replies - yes, I know it's being discussed in that thread, I started the discussion. I just figured it would be easier to post a new thread than to extend that one.
Anyway, Imnuts, I actually did try a different USB cable and the funny thing is that the ODIN flash was WAY faster, but failed (actually reported as failed). With the first cable, it was taking a really long time but it the flash passed.
But it doesn't matter anyway because I figured since I managed to (somehow) get into the stock recovery (even though I was unable to do anything), the phone must have been wiped and restored to factory, although bricked. So, I called up Big Red and they sent me a new one under factory warranty

New phone, new results - trying to flash the recovery image.
0302_charge_recovery.tar.md5
I have 1 usb port on my laptop - never had an issue with ODIN before this. I have always used a USB hub on my laptop to remedy the other broken port.
There are 4 ports on the hub and I get different ODIN results with each one:
USB1) PASS - but still no recovery on my phone (Samsung logo forever if I try to get into recovery, but phone will boot up fine)
USB2) DOES NOT FINISH - I get a RQT_CLOSE !! error in ODIN and nothing happens after that. The result of this flash is a soft-brick with the little PHONE -> PC icon.
USB3) FAIL
USB4) Hangs at "SetupConnection.." forever
LAPTOP PORT) Random result from the list above
Each one of these also yields the RX_TIMEOUT stamp on the phone screen.
I'm at a loss for how to get the damn recovery on my phone. I have tried 3 different cables. My only other option left is to try to use someone else's computer.

n1ghtwish said:
New phone, new results - trying to flash the recovery image.
0302_charge_recovery.tar.md5
I have 1 usb port on my laptop - never had an issue with ODIN before this. I have always used a USB hub on my laptop to remedy the other broken port.
There are 4 ports on the hub and I get different ODIN results with each one:
USB1) PASS - but still no recovery on my phone (Samsung logo forever if I try to get into recovery, but phone will boot up fine)
USB2) DOES NOT FINISH - I get a RQT_CLOSE !! error in ODIN and nothing happens after that. The result of this flash is a soft-brick with the little PHONE -> PC icon.
USB3) FAIL
USB4) Hangs at "SetupConnection.." forever
LAPTOP PORT) Random result from the list above
Each one of these also yields the RX_TIMEOUT stamp on the phone screen.
I'm at a loss for how to get the damn recovery on my phone. I have tried 3 different cables. My only other option left is to try to use someone else's computer.
Click to expand...
Click to collapse
After USB1 pass, phone off, three button press didn't work? (Vol. up, home, power) try quick boot app from market see if that'll get you in recovery.
Sent from my SCH-I510 using xda premium

n1ghtwish said:
New phone, new results - trying to flash the recovery image.
0302_charge_recovery.tar.md5
I have 1 usb port on my laptop - never had an issue with ODIN before this. I have always used a USB hub on my laptop to remedy the other broken port.
There are 4 ports on the hub and I get different ODIN results with each one:
USB1) PASS - but still no recovery on my phone (Samsung logo forever if I try to get into recovery, but phone will boot up fine)
USB2) DOES NOT FINISH - I get a RQT_CLOSE !! error in ODIN and nothing happens after that. The result of this flash is a soft-brick with the little PHONE -> PC icon.
USB3) FAIL
USB4) Hangs at "SetupConnection.." forever
LAPTOP PORT) Random result from the list above
Each one of these also yields the RX_TIMEOUT stamp on the phone screen.
I'm at a loss for how to get the damn recovery on my phone. I have tried 3 different cables. My only other option left is to try to use someone else's computer.
Click to expand...
Click to collapse
I suggest try someone else computer. Obviously, there is data drops and caused between the driver and your O/S or hardware.

After a few more tries and almost throwing the laptop and the phone out the window, it passed and I now have recovery and stock rooted FP1.
Good lord.

For future reference, I would avoid using Odin with the phone connected to a USB hub. It only adds a failure point in the connection. Given that you already have one bad USB port the way it sounds, odds are the other one is partially bad as well, given your issues with Odin.

imnuts said:
For future reference, I would avoid using Odin with the phone connected to a USB hub. It only adds a failure point in the connection. Given that you already have one bad USB port the way it sounds, odds are the other one is partially bad as well, given your issues with Odin.
Click to expand...
Click to collapse
Well, that's why I tried without the hub. Oh well, it's done.
I'm not much of a computer person really, I only use this thing for breaking my phone

n1ghtwish said:
Well, that's why I tried without the hub. Oh well, it's done.
Click to expand...
Click to collapse
That's what imnuts was saying, though. Using a hub adds a failure point, which is a bad thing, but you also said one of the USB ports on the laptop had already gone bad. Two side-by-side ports are typically linked, whether out at the ports or back at the controller. If one went bad, the other is also likely to not function properly. The main point is that in the future I would avoid flashing using that laptop all together.

[Q] Stuck in a soft boot (2nd time) trying Adb to get past the recovery file issue

I've spent weeks surfing the forums trying to get past the common recovery file rename and replacement with a system manager that is in super user mode etc. I don't know if it's the particular version of the recovery file that I've replaced being bad, but the first time I was soft bricked I was able to physically reset with a guitar wire in that whole ( was weird cuz it seemed like the button wasn't going to work cuz after minutes of turning the phone on and off it just randomly worked) Let me explain better because after chosing a different recovery file it soft bricked again however the reset isnt working. Ok so if I have USB cable in it brings up charging battery logo (showing the battery as dead which isnt true because the time it did reset... when it worked, the icon illuminated green suddenly. If the USB isnt connected upon turn on the samsung comes on indefinitely (forever)... tried with sim in & out etc. If I reset into download mode it just says downloading (let it go for three hours before stopping it once). Ive installed odin and tried to fix it that way... I made a Jig with 3X100k resistors and 1 1ohm 1watt ..( attempting to get the 301k resistance between the 4th and 5th pin in the micro usb connection... Didn't work ( used a voltmeter to test the jig but I didn't know what the reading should be but I saw a difference ( thougt the 1 watt addition was messing it up so I omitted that resistor. Still didnt work.... guess I could splurge and buy a jig online as a back up if I cant beat it differently. Lastly and more promising was downloading ADB and getting it running correctly... at first because of the inability to adjust bugging or not the device wasnt recognized... miraculously I left it alone andcame back and tried it... device is recognized... tried to adb pull recovery.orig file to C: to rename and push back but I didn't see it on the PC to rename after Adb says the pull file command was done. Thanks for your patience with all this info on first message. Im new to this. Im sad that I have to get into this just to take control bake but there is a user and or group that is runing in my background and changing my permissions and running so many processes its like slow motion. doing this so I can run the roms to control my traffic and get some Ram back... I wish I could just ask him to please stop. Thank you for any help.

If I reset into download mode it just says downloading (let it go for three hours before stopping it once)
Click to expand...
Click to collapse
What exactly are you doing with it when you have it in download mode? If you can get into DL mode already, what's the point of the jig?
What was the exact procedure you used with Odin, and at what point did the flash fail? Maybe I'm missing something in that wall of text, but it seems like, if Odin isn't working for you, you could always try to Heimdall back to stock and then flash a kernel & CWM one-click installer.
http://forum.xda-developers.com/showthread.php?t=1629079&highlight=uclb3
BTW, please separate your paragraphs. One big block of text is kind of a pain in the ass to read through.

Odin
ApexPredatorBoids said:
What exactly are you doing with it when you have it in download mode? If you can get into DL mode already, what's the point of the jig?
What was the exact procedure you used with Odin, and at what point did the flash fail? Maybe I'm missing something in that wall of text, but it seems like, if Odin isn't working for you, you could always try to Heimdall back to stock and then flash a kernel & CWM one-click installer.
http://forum.xda-developers.com/showthread.php?t=1629079&highlight=uclb3
BTW, please separate your paragraphs. One big block of text is kind of a pain in the ass to read through.
Click to expand...
Click to collapse
Odin wasn't recognizing the device before at all, but since I set up ADB and ran the adb sync comand, now when I run Odin it recognizes the device as com5 not com++ (not sure if that matters). I'll try and start a pit and see what happens.
If I went back to stock what kernel do you recomend I flash and do you know a good recovery file to replace the original one to get past the signature verification when reinstalling packets.

Flash entropy's dd kernel. There is no need to replace any recovery file in GB (that's only on froyo).
Sent from my sweet & buttery Infuse

[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!

Xperia Z5 stuck in bootloop and flashtool cannot recognize it.

Hello guys,
It is my first time yesterday to flash and root my Xperia Z5 since the camera app always says that it is currently in use.
I used this guide by sceryavuz . And it turned out great, I have used my phone for a day without any errors or problems encountered. But the thing is, I still cannot use the camera app and it has the same currently used by other application message so I decided to downgrade it to Marshmallow this morning. So I went to the same routine, downloaded an FTF file and loaded it into the flashtool.
After clicking Flash device in the flashtool and waited for the flashmode, I connected and pressed the volume down button of my phone but the flashtool is not reading and recognizing my phone. So I decided to open the TWRP and assumed that factory resetting my phone will do the work and it turns out that it just removed the /system folder and now I have a bigger problem with my phone.
When I'm connecting in flashmode the LED is turning to red, green, then will turn off, and then will do the same cycle if left unattended.
Could you guys please help me out with this. You'll be greatly appreciated guys. Thanks!
My phone is E6653 Xperia Z5

Well, you should reflash the system, by a custom rom of your choice or even the stock rom if you want to.
I'm using a custom rom and I highly recommend you to do so if you already lost your data, give it a try.
You don't need to downgrade to MM, it not an android version issue, I would recommend you carbon rom. Go to it's thread and figure out how to flash it, if you need help ask over there or quote me back in this thread.
Another option could be restoring your phone with xperia companion but you will need to relock the bootloader and get flashmode to work again. You can also try flashtool from your computer. Anyway I recommend you to do so ONLY and ONLY if you want your phone to run stock again as it was when you bought it.
Otherwise yep, figure out what's a customrom and how to flash it, you find tons of custom roms in xda threads. having already TWRP is an advantage, less sketchy stuff to do.
Hope it helped, as I said, quote me back if you need help
Edit: if you need the files we're running the exact same device, if you don't find em (and only if you can't find em) i could send them to you.

ofmoll said:
Well, you should reflash the system, by a custom rom of your choice or even the stock rom if you want to.
I'm using a custom rom and I highly recommend you to do so if you already lost your data, give it a try.
You don't need to downgrade to MM, it not an android version issue, I would recommend you carbon rom. Go to it's thread and figure out how to flash it, if you need help ask over there or quote me back in this thread.
Another option could be restoring your phone with xperia companion but you will need to relock the bootloader and get flashmode to work again. You can also try flashtool from your computer. Anyway I recommend you to do so ONLY and ONLY if you want your phone to run stock again as it was when you bought it.
Otherwise yep, figure out what's a customrom and how to flash it, you find tons of custom roms in xda threads. having already TWRP is an advantage, less sketchy stuff to do.
Hope it helped, as I said, quote me back if you need help
Edit: if you need the files we're running the exact same device, if you don't find em (and only if you can't find em) i could send them to you.
Click to expand...
Click to collapse
Hi ofmoll,
I'm sorry for the very late response, I had an internet connection issue this past week. I have tried your suggestion by using Carbon Rom, it works perfectly fine but I have one problem. It is not charging and the battery keeps saying that it is on 100% even if it is not. I'm trying to reflash other ROMs and I'll get back to you as soon as I finish flashing. Happy new year! Thanks!

Hi,
I tried to flash my phone a carbon rom and a crdroid rom and it was successful, my problem was it wasn't charging, and whenever I try to use flashtool, and I am entering flashmode, the phone turns red then green then after a minute it turns red again and then green after I press volume down and connect the phone to my PC. And the PC seems cannot recognize my device since no sounds are going off my computer when I connect it. I hope you can share your expertise regarding this.

Toshiiiiiiii said:
Hi,
I tried to flash my phone a carbon rom and a crdroid rom and it was successful, my problem was it wasn't charging, and whenever I try to use flashtool, and I am entering flashmode, the phone turns red then green then after a minute it turns red again and then green after I press volume down and connect the phone to my PC. And the PC seems cannot recognize my device since no sounds are going off my computer when I connect it. I hope you can share your expertise regarding this.
Click to expand...
Click to collapse
So you say it's not charging? Or did you manage to solve that? You don't really need flashtool at this point (unless you want to relock the bootloader, but I guess there are backdoors for that as well)
If it's not charging, well, the options are this: either it's a hardware problem, for example charger or charge port, or a software problem, because some files are needed for the phone to detect a charger source plugged in.
1. If the software is crashing you can try going into TWRP and wipe cache and dalvik cache, may help may not, try. If you get it yo work remember to calibrate the battery after it, it might be important because after flahsing roms and having this kind of issues the battery could not be showing the actual percentage of battery. So just calibrate, it's easy, Google it.
2. It could happen that the phone is charging but the battery status icon won't show it, I'm not too sure about this but I heard that could happen, might not be the case.
3. In none of that works, search, make a lot of research of people with your same problem and try amd try and try, If nothing works a clean reflash should solve it, usually does, if not try another rom, another kernel or go back to stock. It's your choice, but anyway I guess a clean reflash should get it working. I had the same issue with LineageOS and wiping Dalvik Cache solved it.
If you wipe dalvik expect a long reboot time, I don't suggest you to turn the phone off while it boots up. Wiping Dalvik means all cache files have to be built again the next time you reboot your phone, so yeah, expect some battery drain and a hot device while it boots up, but don't panic, it's totally normal.
Happy new year, hope you get it working again
Remember to hit thanks, cheers!

ofmoll said:
So you say it's not charging? Or did you manage to solve that? You don't really need flashtool at this point (unless you want to relock the bootloader, but I guess there are backdoors for that as well)
If it's not charging, well, the options are this: either it's a hardware problem, for example charger or charge port, or a software problem, because some files are needed for the phone to detect a charger source plugged in.
1. If the software is crashing you can try going into TWRP and wipe cache and dalvik cache, may help may not, try. If you get it yo work remember to calibrate the battery after it, it might be important because after flahsing roms and having this kind of issues the battery could not be showing the actual percentage of battery. So just calibrate, it's easy, Google it.
2. It could happen that the phone is charging but the battery status icon won't show it, I'm not too sure about this but I heard that could happen, might not be the case.
3. In none of that works, search, make a lot of research of people with your same problem and try amd try and try, If nothing works a clean reflash should solve it, usually does, if not try another rom, another kernel or go back to stock. It's your choice, but anyway I guess a clean reflash should get it working. I had the same issue with LineageOS and wiping Dalvik Cache solved it.
If you wipe dalvik expect a long reboot time, I don't suggest you to turn the phone off while it boots up. Wiping Dalvik means all cache files have to be built again the next time you reboot your phone, so yeah, expect some battery drain and a hot device while it boots up, but don't panic, it's totally normal.
Happy new year, hope you get it working again
Remember to hit thanks, cheers!
Click to expand...
Click to collapse
Hi Sir,
Happy new year! Thanks for your reply and I really appreciated it. When I connect the phone to my charger when it's off, it turns on then shows the screen of charging 0% by carbon rom then immediately dies after 2 bars being filled. I hope that it is not a hardware problem since when I connect my phone to my computer via the usb, it lights on but the computer can't recognize it. I am suspecting that this is a rom problem with my phone since the phone shows that it's charging connected to AC and 100% even if it is not connected to a charger. I am trying to get the flashmode to work again so I can flash a stock rom to it because the stock rom works perfectly fine but the camera. I will try all your suggestions tomorrow and I'll research harder to solve this. Will post an update once done. Cheers!

Toshiiiiiiii said:
Hi Sir,
Happy new year! Thanks for your reply and I really appreciated it. When I connect the phone to my charger when it's off, it turns on then shows the screen of charging 0% by carbon rom then immediately dies after 2 bars being filled. I hope that it is not a hardware problem since when I connect my phone to my computer via the usb, it lights on but the computer can't recognize it. I am suspecting that this is a rom problem with my phone since the phone shows that it's charging connected to AC and 100% even if it is not connected to a charger. I am trying to get the flashmode to work again so I can flash a stock rom to it because the stock rom works perfectly fine but the camera. I will try all your suggestions tomorrow and I'll research harder to solve this. Will post an update once done. Cheers!
Click to expand...
Click to collapse
As said, first of all try what I said. It nothing of that solves it, I suggest you 3 options
1. Either go stock, try using XPeria Companion, but I think since you flashed custom it doesn't work, at least for me. For Companion you'll need to relock bootloader. Or go stock by flashing a stock rom via TWRP. Note that after flashing a custom rom you'll never go back to the "real" stock if you don't have a backup, but you can always flash a stock rom.
2. You can also try to reflash the rom and see if that works.
3. Download a Custom kernel, then go to TWRP, wipe everything, then first of all flash the Kernel (remember to ensure that's a kernel for your device). Then reflash the ROM. This could look stupid because the ROM comes with a built-in kernel itself, but it solved an issue I had with random reboots. I didn't read this anywhere, I tried and for me it solved a problem I had which everybody was telling me that was caused by hardware, then it came out to be a Kernel issue. Try to if you want.
Try what I said before as well. This is all I know
Cheers
Edit: I forgot to tell you that PC Companion won't recognize your phone if it's running a customROM. Use Android File Transfer instead. You also need to check "use usb to transfer files" on the notifications pannel. Enable USB debugging as well, I guess you know how to do it, in case: you need to go to "about phone" in settings, hit 8 times Build Number, then the developer options should appear and check Android Debugging. That's it.

TWRP seems have bricked my galaxy S7.

Hello community,
I regulary use some custom or stock firmware for my Samasung phones for several years (since My first Galaxy S1 !)
I love refurbirsh old phones withh new relases of android when operators and Samsung stop maintenance. I Limit my experimentation to last stock roms from Sammobile or CyanogeneMod/LineageOS wihth open Gapps.
Last days it was my galaxy S7's turn, to give it to my daughter : New battery,new back cover and new ROM.
My goal was to install Android 9/lineageOS 16 herolte version from operator stock rom.
First try : install TWRP with adb and linux heimdall. Tricky part was to reboot in recovery mode before it is overwritten by stock rom.
Not so easy without battery removal. Result, I ended in boot loop because of crypted data partition. First mistake.
2nd try : Format system and data via TWRP install lieageos zip and nano Gapps. Worked OK.
BUT, impossible to power off the phone. Only reboot was possible even power off with TWRP.
Not happy with this.
3rd try : reinstall last stock Firmware from sammobile via Odin. Process successfull reboot OK. Minimal configuration to check all is working as expected.
4th try : Install TWRP via Odin. Process Successfull but haven't succeed to get Recovery mode befor normal boot.
Then things became bad : After boot to welcome screen (with the hour and notifications), phone became completly stuck. No touchscreen or button responsive.
I forced reboot with volume down + power.
And I fell into the green screen of death with the error message "emergency recover".
Since then I can still boot in download mode and Odin detect the phone correctly, but impossible to write anything back in the phone.
after clicking start button, Odin failed with timeout either at the begining, or at system.img from stock rom.
I have tried others USB cables, Other releases of Odin, others stock roms.
I although tried repart with PIT file, even "erase all" option. But Nothing else than timeouts, and reboots in green screen of death.
I'm afraid internal memory has been definitiveley corrupted.
I ended up with reopen the phone and remove battery to keep it safe.
Before I seek for another motherboard, I ask here if there is something else to try.
Thanks for your help.

Yes
1. Reinstall drivers
2. Try new Odin version
3. flash latest available stock firmware for your region.
4. Try to Run Odin with Administrator rights
5. Flash 4 file firmware
6. Flash one by one file firmware
7. Extract boot, kernel and recovery files from stock firmware and flash one by one, then do full firmware flash...

If can go to download mode can reflash stock firmware with odin.

Teddy Lo said:
Yes
1. Reinstall drivers
2. Try new Odin version
3. flash latest available stock firmware for your region.
4. Try to Run Odin with Administrator rights
5. Flash 4 file firmware
6. Flash one by one file firmware
7. Extract boot, kernel and recovery files from stock firmware and flash one by one, then do full firmware flash...
Click to expand...
Click to collapse
Which version of MS Windos? I have tried windows 7, and 10 neither worked!
What drivers?
I have tried 3.14.1, 3.14.4 - neither worked!

1. Samsung drivers :
Samsung_USB_Driver_v1.7.48.0.zip
drive.google.com
2. Latest stock firmware by using your full model name, and region for your device otherwhise it will fail all the time...
Latest stock firmware by using your full model name, and region for your device otherwhise it will fail all the time...

Hi thank you for suggestions. I have prepared flash with heimdall by untar unlzm4 the imgs. But something went wrong maybe by unplug the battery. The phone never woke up.

Use multimater and check battery voltage it must be minimum 3.8v to boot up.... Since you messed up your bootloader you wont be able to charge your phone most likely. So you need then or buy new battery or charge manually direct...
Here is example:
Red wire is +
Black Wire is -
on your battery
See picture where is + and where -
Once you are Successfully charge your battery, put your phone into the Download mode Vol+ / Home /Power button, etc...
Good luck

Hi, I'm back with some more news. I've tried th above solution, Test battery with multimeter showed me 1V. I then tried to charge the battery. Tricky part was to stick the wire on such small pins. Anyway It sort of worked as I could measure 3.8V after charging
But bad luck, the phone still doesn't want to power up.

didou691 said:
Hi, I'm back with some more news. I've tried th above solution, Test battery with multimeter showed me 1V. I then tried to charge the battery. Tricky part was to stick the wire on such small pins. Anyway It sort of worked as I could measure 3.8V after charging
But bad luck, the phone still doesn't want to power up.
Click to expand...
Click to collapse
Make sure that the power button, and volume buttons has good connection, also check charging port if it is good connected and clean all dirt inside usb port.

My take on the battery would be buy a "new" one.
didou691 said:
Hi, I'm back with some more news. I've tried th above solution, Test battery with multimeter showed me 1V. I then tried to charge the battery. Tricky part was to stick the wire on such small pins. Anyway It sort of worked as I could measure 3.8V after charging
But bad luck, the phone still doesn't want to power up.
Click to expand...
Click to collapse
From past experience any fiddling with the contacts and "plugs" on the battery or else where is a very dodgy proposition. My suggestion is (as above) buy a new battery, the very low voltage (1V) makes me think that the battery is shot.
Good luck