Hello there. I own a Z3 model D6603. It is unlocked bootloader and Before it had got the bootloop i had Lineage OS 16 custom rom installed on it (Android 9). I was watching some videos on chrome and then the phone heated a little and then restarted. I thouhgt it was maybe some sort of instability but then it started just bootlooping.
Current Status right now is :
Once connected to pc goes to flash mode.
I can get it to fastboot.
When connected to charger just goes into endless bootloop where only SONY logo appears and then quickly restarts
In attempt to fix it I flashed stock FTF using multiple versions of Flashtool which was fruitless. I also Tried with EMMA but nothing helped still. And then after looking I think it might be damaged TA and I've seen so many say that if that's the case then the phone is bricked forever unless you have had a backup from a previous working state which I actually do. The problem is that I don't know how to flash this TA back since the phone doesn't boot to restore it through ADB. I saw that S1tool works with older devices and doesn't work with Z3 models so I wonder if there is a way to fix this. Thank you for your time.
PS : My power button doesn't work I used to use fastboot to boot it when necessary
Issues of that kind may be a hint for a dead battery, this should be ruled out first. Note: In that case your phone might not boot even if connected to a charger!
After that is ruled out, one should try to install LineageOS 16 or later following the official installation routine from scratch.
Related
hi guys I want to ask something regarding my phone state
I got stuck with endless bootloop, when I turn on my z3 it shows red led and sony logo then proceed to reboot again,
charging also seems not working because when I insert the cable it always proceed to state that I mentioned earlier
(sony logo endless reboot etc) and not showing charging animation like it supposed to be
Just to let you know I got UBL and seems to have working fastboot and recovery mode,
also flashing with emma + flashtool not working it shows no error when flashing but my problem still persists ,
any idea how to fix my phone? any answers are appreciated, and thanks
I've had some previous experience with custom roms on my old Nexus 6P and thought I would try the same for my mate 9. Unfortunately I've discovered the Mate 9 is not as easy to install custom roms as I thought.
I've tried several things throughout the day and I feel I've accidently overwritten things I shouldn't have but can't remember everything I've done.
It is an Optus branded phone so I believe at the start of the day I had some version of L09C34. I currently have an unlocked boot loader and TWRP installed and would like to flash back to the stock firmware, but seem to be unable to do so. The boot loader is unlocked and when I try flashing extracted parts from fastboot, the phone will reboot, reboot again and sit at erecovery. Unfortunately while I can connect to wifi, no packages are found for recovery.
Additionally I now get this lovely colourful screen in lieu of the logo on initial boot.
Any help would be appreciated.
Okay, so I've managed to unbrick it and install a version of L09C432 and get it working again - thank you to various threads on XDA. I think what I noticed was that someone else had tried the C432 firmware on a C33 model and it worked. Without being able to get hold of the C34 firmware, I tried to flash nougat originally and it worked.
This morning, I've noticed I still have an issue where the touchscreen won't work when the phone is cold (i.e I can't click anything and can't turn alarms off). If I reboot the phone to recovery it's fine, so it leads me to believe its an OS thing. Also, if I give it a few minutes in my pocket, or holding my palm on the screen it then responds. This is the issue I tried to resolve by resetting and trying a different rom but seems I haven't been successful.
Finally, when I first turn the phone on and the screen lights up I see a green background with one blue and one red box. Any ideas what I have messed up there and how to fix it? I'm not too concerned, but it would be a nicety.
Just providing updates in case anyone comes a long with similar issues.
I have now fixed the strange coloured screen on initial power on. I've found the oeminfo for the C432 firmware on another XDA thread and took a backup of what was currently there, restored the C432 version and rebooted. I was presented with the eRecovery and no TWRP. Quick check in fastboot mode showed the phone relocked. I unlocked it again and it booted no issues, however was unsure if the custom rom was still installed as I was presented with the option of an OTA update. Initially my sim card was not recognised, so I had to remove and reinstall it but so far so good.
I've just reflashed my custom rom and will see how I go.
The only potential issue I have outstanding is my touchscreen not working either first thing in the morning, or when the phone is cold - i.e I've gone to the gym and left it sitting in the locker for 2 hours and I can't use the touchscreen when I come back. I can unlock it fine with the finger print reader and the phsyical buttons respond but touches on the screen won't. If the phone is left alone for a few minutes the screen shuts off and turns back on approx every 5 seconds until it becomes responsive. Has anyone seen anything like this before? My googling hasn't lead me to anything helpful.
Greetings everyone,
I decided to post my problem with my phone after searching the entire internet for similar problem but with no luck. Anyway I used to play around with my Samsung j7 pro for 2 years, I managed to flash twrp and thus many other custom roms, until last week when I recklessly flashed a sboot.img.tar file through Odin in order to fix cellular network in a rom I flashed earlier, this alone bricked my phone refusing to get past the Samsung logo, so like I do always, I tried to restore my phone by flashing the stock firmware (9.0) which I always keep on my PC, but surprise, the phone refuses to go through the process and gives me this error:
sw rev check fail bootloader device -1 binary 6
(same with 8.0 and 7.0 firmware)
I searched the internet for same error but with no luck, because I understand it's a mismatch between device bootloader current version and the firmware bootloader's, that they should be the same or higher, meaning you can't downgrade, I get that! but I never seen device with negative figure (-1) what that's supposed to mean? my device bootloader used to be on 6, how did it managed to jump to minus one ?
then I tried to flash TWRP to see if I could flash a rom and get around it, so I did, but when booting into recovery the screen goes black, I thought first the phone turned off, but not really, because TWRP seems to work with screen completely black, I knew that because I accidentally touch the screen and I sense vibration, I managed to reboot the phone via twrp just by guessing the buttons location (screen always black) in order to prove that TWRP is working with screen off. I tried to flash multiple TWRP versions but the same problem, no screen just touch, by the way there is nothing wrong with display hardware because it shows Samsung logo at start and also can boot into download mode just fine.
I hope someone could help me overcome this big of an issue, because I tried everything.
Hi team, how are u doing?
Happy new year for everyone, and I hope everybody gets very well in this year.
So I've came to try as last chance to recover my old Z5. This phone I gave to my mom and she uses every day and she loves
But a few weeks ago she tells me the phone start appear some glitches in camera, the battery discharge too fast...
My father goes to a phone center and change the battery and after that the phone don't turn it on anymore, just blinked 3 red lights and shut off.
I tooked the phone and trye to recover as I mentioned the phone was old version of some custom ROM from this forum and with all my old old knowledge hehe I've tryed to recover through TWRP but nothing happens.
So I came back to this forum and start read all the information again and how we can resolve this.
I already did:
1-wipe entire cellphone (wipe data, system, cache, kernel)
2-flahs old stock roms, and lastest stocked roms
3-I've BL locked again to try to use the Xperia Companion repair.
All this I've already did and nothing turn it back. The difference until now I could look is: "now the phone starts with xperia logo and after that android logo start loading and boot again blinking 3 red lights.
I can easy enter into flash mode and fastboot mode.
What I'm trying to do:
BLU unlocked again (I can't flashtool shows me an error "cant find loading.sin .. bla bla bla")
I've downloaded the EMMA Tool (it's the same of flashtool but created by SONY I guess - but I can't use because my BL it's locked and I don't know how to unlocked again.
I dont know if its the battery, because the phone appear to start turn on again, I think it's a software brick .. but I really don't know what I need to do.
Somebody can help me?
OH (unfortunally we have in this forum old tutorials and some of them are off already ... so it's being very hard to get more info to do this.)
I hope some kindless soul could help me in this revival
Wish you best!
Anyone?
Hi guys,
Hope someone can give me some light about diagnosing flash memo device hardware damage.
I have an OnePlus 6 A6003 that entered for sudden in CrashDump Mode. It stopped to run the OS, although the bootloader mode still worked.
Guided by some tutorials I tried to unlock trough fastboot and adb in CMD panel without success in unlocking the device.
After that, I started trying Msm Downloading tool to flash a Oxygen firmware and make it brand new. I couldn't.
The process stopped somehow in the middle of downloading to system_a. I lost hope big time here and went to SMT flashing. The tutorial advised that i could lose IMEI if i did not backed up my EFS. I didn't, but i figured i could use some downloaded backup and change my IMEI back to original, as I have the original box and data of the phone. I did it and the process of flashing the device stopped the same spot it did before.
From there I repeated the process in loop until finally I got it done. Once the original oxygen firmware was succefully flashed I was happy, till i discovered the phone still doesn't turn on. it always blurs the initial logo screen after some seconds and freezes.
At this point I think there is some hardware problem at the flashdrive device. Anyone have any idea if this still can be a software problem or can assure me how i could definitly diagnose it?
I 'd be thankful with any help.