Flashtool - Xperia Z5 Q&A, Help & Troubleshooting

Hi,
My phone is/was rooted with an unlocked bootloader and I have attempted to flash using flashtool, something I've done loads of time beforehand without issue.
However, it crashed and my phone won't go past 'the udpate failed' black screen when turning on.
It appears to go into both flash and fastboot modes.
Have run on flashtool again, downloaded firmware etc...but when i got to flash, it doesn't recognise the firmware so cannot prepare it, or the phone model.
Why won't it load up the firmware so i can create/prepare to flash, and how do i fix this issue so I can use my phone again? Sending me mad...any help greatly appreciated!! Just cannot get rid of this update failed problem.

Related

Unroot failed, now phone is stuck in Fastboot loop

Hi Guys,
my HTC Desire GSM is stuck in Fastboot and won't boot into the ROM. The background to this issue is that I installed S-Off and then ClockworkMod and flashed Cyogenmod 7 to see if it would fix a reboot issue on the phone. The damn thing just reboots itself when the CPU is used heavily...
Anywho, after realising that Cyogen wouldn't resolve the issue I flashed the standard Virgin UK rom back over it and upgraded to 2.22.351.2 via the system update feature. The problem was that ClockwordMod was still installed and I had to get rid of it to sent the phone off for repair to Virgin!
So I did further research and found that I could flash HBoot via the AlphaRev.nl downgrader tool. I downloaded it and popped it into the root of my SD card and it flashed the bootloader back to Hboot 0.80.0000. That should have been it, but all of the sudden the phone no longer boots into the Rom. All it does is to power on and then go into Fastboot. That's it! When I try putting the standard Virgin Rom back onto the SD it tries to load it and then says "Main Version is older!" "Update Fail!".
How do I get around this now? The phone doesn't boot, so I can't re-flash S-Off and start again, not am I able to run the stock Virgin Rom within Windows because it complains about the versions.
Is there any ways around this situation? I just want to get the phone back to stock so I can send it to Virgin and get it repaired.
P.S. I *have* used the search function and spent the last 4 hours testing various things but I'm now stuck.
Cheers Guys!
Mich

[Completed] Secure Booting Unsuccessful error

Folks, I have seen some threads on here so I will understand that you will probably hate me but seriously none of those did well for me. So that's why I am creating mine. As an owner of LG G2 mini I had been closely focusing on CM12 progress re lollipop that InvaderJohn was working on. There was a camera overexposure issue so I tried to use some working lib files and vendor/lib files and created a flashable file for TWRP recovery. I screwed it up as upong the flash my phone with CM12 didn't boot up. I wasn't able to get into recover thru adb so I pressed volume down and middle button and got myself into factory mode. I did factory reset and was in TWRP recovery again. Good. Then I reflashed the phone and there was an error saying that secure booting unsuccessful. I have LG Flashtools and tot file with dll for my LG D620fr on my laptop. This method I used once when getting the phone bricked and it worked and I was able to install stock 4.4.2 ROM. But this time... not sure why but the tot flash got stuck with 94% and while the phone was supposed to get restarted it didn't and the message above of the secure etc. popped up. I am able to get into my TWRP recovery (weird) but nothing else. I suspect I got my bootloader locked. Is there any way how to figure this out, please? I was trying the fastboot method but my phone is unrecognizeable. Any help is much appreciated.
enzo_cz said:
Folks, I have seen some threads on here so I will understand that you will probably hate me but seriously none of those did well for me. So that's why I am creating mine. As an owner of LG G2 mini I had been closely focusing on CM12 progress re lollipop that InvaderJohn was working on. There was a camera overexposure issue so I tried to use some working lib files and vendor/lib files and created a flashable file for TWRP recovery. I screwed it up as upong the flash my phone with CM12 didn't boot up. I wasn't able to get into recover thru adb so I pressed volume down and middle button and got myself into factory mode. I did factory reset and was in TWRP recovery again. Good. Then I reflashed the phone and there was an error saying that secure booting unsuccessful. I have LG Flashtools and tot file with dll for my LG D620fr on my laptop. This method I used once when getting the phone bricked and it worked and I was able to install stock 4.4.2 ROM. But this time... not sure why but the tot flash got stuck with 94% and while the phone was supposed to get restarted it didn't and the message above of the secure etc. popped up. I am able to get into my TWRP recovery (weird) but nothing else. I suspect I got my bootloader locked. Is there any way how to figure this out, please? I was trying the fastboot method but my phone is unrecognizeable. Any help is much appreciated.
Click to expand...
Click to collapse
Sounds like the bootloader is locked.
Check this thread: How to check for locked bootloader? ... but it's for the LG G3.
Best place to ask is the G2 Mini Q&A, Help & Troubleshooting.
Thread closed and thank you.

I need some help with a sm-g930f that wont boot ANY stock rom. Just boot loops.

So im trying to fix a freinds phone. He said it randomly shut off and started bootlooping on the samsung screen. So I flashed the same firmware using odin. It succeded restarted and still does the same exact thing?
No matter what I do I cannot get this damn phone to boot up. After holding vol down and power to soft reset it goes to a screen with a triangle and says installing update then to no command. If i soft reset then hold vol down and home with power download mode will come up. I cant get this phone to go into recovery the combination just brings me to the triangle screen. Maintenance mode wont even come up the triangle screen shows instead. I have knowledge of odin and flashing. Ive been flashing since the motorola cliq lol But this is making me scratch my head...Any ideas?
I want to add that when it freezes at the samsung logo the logo corrupts and gets black lines through it then restarts several seconds after?
Are you flashing all 4 firmware files with Odin or just AP?
Of course I am. I even went ahead and flashed another "non carrier" firmware to see if it made a difference and no luck.
BL
AP
CP
Home_CSC, I flashed the CSC when flashing a different firmware.
By the books and nothing seems to get this phone booting.
Have you tried just normal CSC? Home_CSC keeps data, it's basically acts as an in place upgrade rather than a fresh image.
If you're having issues you'll want a full clean wipe which means using CSC.
When trying a new firmware I flashed the "CSC" because it contains the pit file. So yes I have and that didn't work either.
The phone gets to download mode which tells me its not a brick. Still says "samsung official". FRP lock is off.
And just waiting it out doesn't work? Flashing from a custom Nougat ROM to stock Oreo was like 10+ minutes on the Samsung logo for me.
No as I said in op it always freezes at the Samsung logo over and over and over again.
My best guess is the system partition is corrupt and is un-repairable or the hardware was defect from the factory...but the phone has been In use for 2 years flawlessly...besides that it still boots up Odin(download) mode....so... Does anyone have any idea wtf is going on with this phone? Because anything I do just won't boot it normally. I can't root it and try a custom rom because "OEM unlock" isn't enabled. So WTF?
Please does anyone have any idea what is going on here?
I had some luck with getting it to the bootloader by using odin to flash the corresponding BL file. Then I flashed a combination file obtained from hardreset. But I am still stuck bypassing the FRP lock myself. Either I flash stock rom or firmware with ADB. It always get an error cllose to the end. Or the flash finished and the warning message is still there and I couldn't get pass the google authorisation stage.

Bricked LG G6 H870, tried it all

Hello everyone,
I have a European H870 and unlocked the bootloader, used ADB/FASTBOOT to install TWRP but could never get to start in recovery because of a warning screen that shows up because it is unlocked.
Couldn't get into recovery from both ADB or by utilizing the keypress method. Vol-down+power --> logo --> release power for 1 sec then back on it. I even tried with other variants of that but could never get into recovery or DL mode. What's the point of unlocking the bootloader if you can't do anything afterwards because of a stoopid warning screen?
I never had that issue with my Samsung Mini S3. But with the LG's that I have, since the bootloaders were locked, the phones display this warning screen upon powering up. I can't be the only one with this issue unless I was doing it wrong. But I wasn't. So...anyway.
So with my G5 H850 I got around this problem by using FASTBOOT FLASH RECOVERY TWRP*.IMG and then FASTBOOT REBOOT before using ADB REBOOT RECOVERY during the boot process to get into recovery before the phone had fully booted.
So I tried the same with the G6 H870, of which I also cannot get into DL mode or recovery because of this screen. The only difference was that there is something different about how the H870 loads the system so that I could not run ADB commands until the phone was already 100% booted and thus rendering my recovery flash useless.
I ended up doing something that caused my phone to always boot into fastboot so I downloaded what I thought at the time was the correct boot.img and flashed it. And now I'm at the current situation where the phone boots past the warning screen and into the logo screen but then stops for a few minutes before rebooting. This process endlessly repeating. It is obvious to me that the boot.img was incorrect.
So what I have done so far is loading all Qualcomm drivers, LG drivers, QFIL and QPST (drivers being installed or uninstalled for each instance that requires them). The problem now is that the phone shows up on a COM port but is is unrecognized to all the different software and thus can I not communicate or flash anything to it.
A couple of unbricking procedures that I tried are:
https://forum.xda-developers.com/lg-g6/how-to/lg-g6-unbrick-method-t3935924
https://androidmtk.com/use-qpst-flash-tool
There were more but I cleared my browser's memory.
So, do I need to invest in an Octoplus device to get past this or is there another way?
Thank you.

Question Stuck in boot loop after firmware flashing attempt, please help

1. I forgot to do the oem unlocking for the bootloader
2.i tried to root my phone with odin3
3.my phone was softbricked with the light blue error screen that had a waring in english,koren
4.I tried to flash a stock rom potentially of the wrong kind of A32 and the wrong CSC
5. Now the phone no longer turns on unless plugged to a computer, which makes the screen turn on and off continously. The screen is completely black when on for half a second.
What are my options in fixing my phone? If the correct CSC is needed, how do I discover it with a frozen phone such as mine?
If the device does not boot, you probably flashed the wrong firmware and corrupted the bootloader. Unfortunately there is nothing you as the end user can do to recover your device. Seek professional repair.

Categories

Resources