Hi
Really need some advice here. After (successfully) flashing ROMs on my HTC Desire and a couple of LG / Samsung units, I decided I was fed up with the stock ICS ROM on my Arc S so found one I liked called Jelly Sandwich v6.2.
So, I rooted, no probs, unlocked the bootloader, no probs. Installed CWM and did a nandroid backup to my SD card. So far, so good.
I then used CWM to install the JS ROM and the phone is now stuck on the SONY screen, presumably the boot is looping and I have to pull the battery to shut it back down.
I can't get it into recovery, tried every combination of buttons I can think of. I can get it into fastboot by holding the menu button and inserting the USB cable and if I do a CMD line fastboot.exe -i 0x0fce getvar version I get the expected response, but if I try adb shell I get 'device not found'.
I am rubbish at best with command line stuff but I think this is my only way forward.
Have tried flashtool and I get the phone into Flashmode but it finishes with an error.... 04/048/2012 00:48:51 - INFO - Ending flash session
04/048/2012 00:48:51 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_DYNAMIC="SIN header verification failed".
Have also tried SuS and that fails with an error along the lines of "The phone has got modified software that cannot be upgraded" or similar.
Anyone tell me specifically what to try? and exactly what I need to be doing with commands etc.
Would appreciate any help no matter how small
Use the Flashtool instead of SEUS.
XperienceD said:
Use the Flashtool instead of SEUS.
Click to expand...
Click to collapse
he's saying he used flashtool but nothings working..
Sent from my AT100 using xda app-developers app
SORTED!!!
ok I sorted this eventually.
Tried everything I could think of and more besides (went through 100s of threads on here and elsewhere).
Eventually I went to wontanserver.com after seeing it recommended on a thread but it didn't work (forget the error but basically it wouldn't flash).
Then the battery died, left it on charge overnight but it was still dead so really thought that it was a hard brick.
Anyway, this morning, still very blearey eyed, I booted it into fastboot with usb connected and then the wotan tool didn't even recognise the phone, so used Flashtool to connect and the only command that would work was "Rebbot into fastboot mode (via Fastboot)"
Did that and the wotan flash tool started working, unpacking and flashing merrily along and a few minutes later the phone is back from the brink of almost certain death.
Don't know if my blurb will help anyone else, but it at least shows you should never give up :victory:
yorkiepudd said:
ok I sorted this eventually.
Tried everything I could think of and more besides (went through 100s of threads on here and elsewhere).
Eventually I went to wontanserver.com after seeing it recommended on a thread but it didn't work (forget the error but basically it wouldn't flash).
Then the battery died, left it on charge overnight but it was still dead so really thought that it was a hard brick.
Anyway, this morning, still very blearey eyed, I booted it into fastboot with usb connected and then the wotan tool didn't even recognise the phone, so used Flashtool to connect and the only command that would work was "Rebbot into fastboot mode (via Fastboot)"
Did that and the wotan flash tool started working, unpacking and flashing merrily along and a few minutes later the phone is back from the brink of almost certain death.
Don't know if my blurb will help anyone else, but it at least shows you should never give up :victory:
Click to expand...
Click to collapse
I have the exact same problem but I don't know how to solve this. Please help me.
lance26 said:
I have the exact same problem but I don't know how to solve this. Please help me.
Click to expand...
Click to collapse
Try reading the post you've quoted.
Sent from myushi
have you tried to flash a specif kernel for this rom or just redownloaded the rom? maybe there was a problem with the download
Since these problems I have installed both CynogenMod 10 and UltimateHD without any problems what so ever.
Related
So I flashed a JB backup and then the kernel with fastboot, and the screen would shake from side to side nonstop whenever I wasn't touching it. So I pick up my laptop to flash a new kernel (old one must of been corrupted, I assumed) and I drop the damn thing when it's turned on. I'm pretty sure that it messed up the HD files to where fastboot was messed up (it would force close when I tried a command) So I found another application to flash a kernel, but it said I wasn't rooted. So I, desperate, hit the delete kernel button. When I tried booting, sometimes the red light would flash three times,other times nothing.
I have since gotten a new phone (was already due for an upgrade) but as a hobbyist, I'd like to try to fix my old phone to maybe give it to someone else.
EDIT: Whoops, wrong thread. I'll keep it in here just in case I get a reply here and not in the Q/A
Mjtmaster said:
So I flashed a JB backup and then the kernel with fastboot, and the screen would shake from side to side nonstop whenever I wasn't touching it. So I pick up my laptop to flash a new kernel (old one must of been corrupted, I assumed) and I drop the damn thing when it's turned on. I'm pretty sure that it messed up the HD files to where fastboot was messed up (it would force close when I tried a command) So I found another application to flash a kernel, but it said I wasn't rooted. So I, desperate, hit the delete kernel button. When I tried booting, sometimes the red light would flash three times,other times nothing.
I have since gotten a new phone (was already due for an upgrade) but as a hobbyist, I'd like to try to fix my old phone to maybe give it to someone else.
EDIT: Whoops, wrong thread. I'll keep it in here just in case I get a reply here and not in the Q/A
Click to expand...
Click to collapse
Flashtool can usually fix something like this.
Get yourself a stock FTF and flash it to your device using flashtool. It should bring it back to life again.
Spizzy01 said:
Flashtool can usually fix something like this.
Get yourself a stock FTF and flash it to your device using flashtool. It should bring it back to life again.
Click to expand...
Click to collapse
Fastboot nor flash mode are working, but I'll try it. Upon digging my play out, Whenever I plug it in to my computer, it says USB device not recognized, and it continously flashed red on the power indicator. Just thought that was worth noting.
Mjtmaster said:
Fastboot nor flash mode are working, but I'll try it. Upon digging my play out, Whenever I plug it in to my computer, it says USB device not recognized, and it continously flashed red on the power indicator. Just thought that was worth noting.
Click to expand...
Click to collapse
So I downloaded flashtool, and I saw that it came with fastboot. I don't know how, but I managed to get it into fastoot mode and it recognized it. But now I figured out how to fix it, I can't get it into fastboot mode. Whenever I connect it it flashes red and it doesn't go to fastboot mode. Do you have any idea how to get it into fastboot mode so I can flash a kernel?
Hi, I've just registered in this forum, though I've been reading you guys for almost a year. I just want to say that you guys are awesome, i've learned too much about android because of you.
Introduction
Said that, I recently had a problem with my P350g, I'll try to be as clear as possible hoping you can help me out.
The problem came after i installed CM 9 [stable 8] on it, at first it worked perfectly (a very few panics or reboots but i'm used to it :laugh. The next day after taking a photograph the cellphone got stuck, it had done that several times before with some other ROMs so i didn't pay much attention to it, so i took the battery off and put it again, and when I tried to turn it on, there it was, the lg logo with the 4 softkeys blinking.
-- It doesn't enter to recovery (i had recovery installed at that time) pressing [- power send] at the same time, it just stays there with the lg logo blinking.
-- It does enter to the emergency mode (yellow background with "emergency mode" in black letters) pressing [+ - power] at the same time.
-- It does enter to the fastboot mode pressing [+ power send] at the same time.
what i've already tryed:
--- i've read the wiki about this phone and try everything there (and everything found on google which is pretty much the same)
http://forum.xda-developers.com/wiki/LG_Optimus_Me
--- i've tryed using the KDZ updater as somebody on this forum recommended:
http://multidroid2.feed.nu/2012/03/27/how-to-unbrickflash-your-optimus-melg-p350-2/
using firmware from here:
http://lg-phone-firmware.com/index.php?id_mod=5
and from somewhere else on the internet, the problem here is, that when it comes to "restart the phone", it doesn't start, it just keeps getting stuck on the lg logo with the 4 softkeys blinking, after some time the KDZ updater shows an error: Upgrade Error WParam: 100 LParam: 6
--- i've tryed flashing the recovery from fastboot mode as shown on this thread:
http://forum.xda-developers.com/showthread.php?t=2131247
it flashes well, everything "succeeded" but whe it comes to reboot (flashboot reboot) the cellphone says on the screen rebooting cellphone (or something like that) but it never reboots. if I take the battery off and put it on again, and then try to turn it on, the cellphone shows at the same problem, the lg logo with 4 softkeys blinking.
--- I've also tryed this tool:
http://forum.xda-developers.com/showthread.php?t=1948326
it hasn't solved my problem either.
Computers' info
I've tried this on 2 computers:
windows 7 x86
windows 8 x64
both of them have the drivers installed, I've disabled the modem on both of them, both of them have the latest android SDK tools
both computers give me the same problems, please i need your help, i'm desperate, I've been with this problem for several days and I can't solve it. I hope you can help me out
bump!
Anybody? please, i'm desperate
Hi,
Let's hope for the good
Try to flash the rom with fastboot.
and did you overclocked it too high? maybe your nand is burned?
kD said:
Hi,
Let's hope for the good
Try to flash the rom with fastboot.
and did you overclocked it too high? maybe your nand is burned?
Click to expand...
Click to collapse
thanks for answering, yes i did overclock it really high ~804MHz can't remember the exact number, but with other roms it had been working at that level of overclock without any problems (besides the casual panics and reboots) for more than half a year.
i'm going to try flashing the rom from flashboot and see what happens
I couldn't fash a rom via fastboot
IsraelMP said:
thanks for answering, yes i did overclock it really high ~804MHz can't remember the exact number, but with other roms it had been working at that level of overclock without any problems (besides the casual panics and reboots) for more than half a year.
i'm going to try flashing the rom from flashboot and see what happens
Click to expand...
Click to collapse
Hi everybody, i tried to flash a zip containing the rom on my p350, though i could not flash it. i used the command:
fastboot flash system rom.zip
but it says the file/rom size was smaller than expected. (honestly i can't remember the actual sentence) and then it says (x < y) where x is the suposed size of the rom and y is the expected size.
i tried with several roms, and a backup a user uploaded somewhere which was suposedly legitimate.
Is there something i can do?
download lg mobile support tool (lg mobile updater)
make sure that the driver is installed on the computer
open it
let it reconize the phone then
click recover phone from CS
the phone will be returned to latest stock rom for your country
then intsall recvoery again and root again
My Method
Well you need usb debugging enabled.Remove phone's batytery and connect it to pc via usb.It will boot up (horribly of course ignore it).Then fire up the kdz updater and start the flashing process.Once the phocess starts midway anywhere in the process insert the battery.The process will complete then KDZ will sat update complete...REBOOTING....and as battery is inserted it will reboot.Voila.Hope it works for you.This is my routine method.(Bricked more than 7 times lol).
Thanks for replying
MeeDa said:
download lg mobile support tool (lg mobile updater)
make sure that the driver is installed on the computer
open it
let it reconize the phone then
click recover phone from CS
the phone will be returned to latest stock rom for your country
then intsall recvoery again and root again
Click to expand...
Click to collapse
thanks for replying, i did that, when i just plug it without pressing any button the cellphone does not get recognized by the software, when i plug it in emergency mode it does get recognized but the software gives me an error.
blazecodester said:
Well you need usb debugging enabled.Remove phone's batytery and connect it to pc via usb.It will boot up (horribly of course ignore it).Then fire up the kdz updater and start the flashing process.Once the phocess starts midway anywhere in the process insert the battery.The process will complete then KDZ will sat update complete...REBOOTING....and as battery is inserted it will reboot.Voila.Hope it works for you.This is my routine method.(Bricked more than 7 times lol).
Click to expand...
Click to collapse
thanks for the answer, I tried that way, though it keeps getting stuck in the LG logo with the 4 blinking softkeys when it comes to reboot the cellphone.
Last night I installed geefree on my phone from the app store and used it to install TWRP. I downloaded a nightly CM11 and an appropriate gapps. Using geefree I rebooted to recovery (never figured out the button combination to boot to recovery "naturally") and installed both of the zips. This could be where I made my mistake, I installed both at the same time.
Now my phone loops, displaying the LG logo for a few seconds, then shutting off and rebooting before repeating the process. I can't seem to get it to go into download mode or the recovery menu. I've tried power+up, power+down, down+up and each of those while plugging the device in, etc. I can get the device to a hardware key control mode, though it doesn't seem too useful.
How can I save my phone? This forum has been a great resource in the past and I'm very grateful for the many tutorials I've followed rooting other devices. Hopefully you guys can save the day once again!
Volume up plus power is how to access recovery on sprint.
What stock sw version were you on before you flashed cm?
Did you wipe data before flashing?
Sent from my LG-LS970 using xda app-developers app
I was using stock 4.2.2, I believe. I didn't wipe the data (shame on me), a bad habit that I picked up from my first rooted device, the Samsung Moment. It didn't ever matter on that one, afaik. Thanks for the reply!
Edit: Volume up and power whether plugged in or not takes me to the hardware key control mode screen.
Second Edit: http://forum.xda-developers.com/showthread.php?t=2432476&page=35 I also found this thread where someone seems to be experiencing similar issues and they fix it with "LG Utility." Is that a PC application? It's a little vague to google, but I've been trying!
I have a bootloop issue every time i flash a rom i have to wipe all but sd flash roms and gapps the i do a restore from twrp and oly restore my boot image only and they boot no prob
I'm kind of starting to suspect my power button doesn't work at all for whatever reason. I have a lot of difficulty getting the phone to shut down, then it doesn't seem to easily power up. It's a strange collection of problems. Would a Sprint repair place be able to fix this?
If they have parts on hand if not either a swap out or a sendoff
Same problem here - bootloop and no download mode - CWM works! - urgently need help
I guess I have the same problem as InlineFourPower (apart from that my power-button has no problem).
I am stuck in bootloop since I tried to upgrade to Kitkat a few days ago. Now I can´t get into download mode any more, nor into fastboot or anything else. Only CWM works.
From within CWM I can successfully flash ROMs but that doesn´t help, since afterwards I am still stuck in bootloop. It is possible, however, to push files via adb-commands while I am in CWM.
Does anybody have an idea how to go from here or how to get download-mode back?
Device is recognized but can´t be mounted - bricked forever?
Parinibbana said:
I guess I have the same problem as InlineFourPower (apart from that my power-button has no problem).
I am stuck in bootloop since I tried to upgrade to Kitkat a few days ago. Now I can´t get into download mode any more, nor into fastboot or anything else. Only CWM works.
From within CWM I can successfully flash ROMs but that doesn´t help, since afterwards I am still stuck in bootloop. It is possible, however, to push files via adb-commands while I am in CWM.
Does anybody have an idea how to go from here or how to get download-mode back?
Click to expand...
Click to collapse
I tried a few things on Linux.
After terminal-command "ls /dev/sd*" when the device is unplugged from the computer I get "/dev/sda".
When the device is connected via USB, I get: "/dev/sda /dev/sdb"
So sdb is my LG G2.
So I went on to the next command: "gdisk -l /dev/sdb"
As a result I get: "Problem opening /dev/sdb for reading! Error is 123."
Does it mean that the phone isn´t mounted or what? Now I´ve connected my phone to another Linux machine with the same result. It is recognised (p.e. as sdd), but there is no sdd1. Seems as if it is recognized, but can´t be mounted. Does that mean my device is bricked for good? That´s it?
to get the phone into download mode you have to plug the usb cord in and hold VOL+, so to get this right as I have a case on mine, plug the usb into the phone first then hold VOL+ and plug into usb port on the computer.
it does take a loooong time to power down the phone with the button when stuck in a boot loop, just keep holding it until it shuts off, it will shut off eventually!!
plug the phone in while in download mode to install drivers and set com ports, then unplug before you begin your flash with LGFlashTool, hope this helps you out.
Cronic2009 said:
to get the phone into download mode you have to plug the usb cord in and hold VOL+, so to get this right as I have a case on mine, plug the usb in first then hold VOL+ and plug into usb port.
it does take a loooong time to power down the phone with the button when stuck in a boot loop, just keep holding it until it shuts off, hope this helps
Click to expand...
Click to collapse
Thanks Cronic2009 for your advice.
There are, however, szenarios where download-mode is not accessible any more. Neither by using the hardware-keys, nor by using the adb-command.
After four days of resarch and a lot of trial and error, I finally unbricked my F320L using the two adb-commands outlined at the beginning of that thread: http://forum.xda-developers.com/showthread.php?t=2451696
Worked like a charm.
Thanks everyone for your advice.
no problem buddy, glad you got it figured out, good luck to you from here on out!
FYI, that link doesn't work
I just wanted to ask anyone who might know, since the bootloader of the LS980 is locked, we cannot "break" this correct, so no matter what commands we decide to run through root, we cant touch the true bootloader there for LS980 fail safe? (Besides Acts of God, EMP, ect)
Cronic2009 said:
no problem buddy, glad you got it figured out, good luck to you from here on out!
Click to expand...
Click to collapse
Thanks for letting me know. I corrected the link in my previous post.
Be sure if you use a aosp based rom to flash the ZV8 modem. Your can use dr87 or furnance kernals after you flash the zva modem althought i have encountered soft brick due to this.
so i'm having this exact issue and i don't know how to get out of it. i just need to transfer the radio to my phone somehow but nothing shows up under adb devices. i'm trying to the lg mobile support tool now. its downloading the software. but if it doesn't work does any one have any fixes?
edit: i fixed it by following this http://forum.xda-developers.com/showthread.php?p=51637410&highlight=download+fail#post51637410
pitbullmommy45245 said:
so i'm having this exact issue and i don't know how to get out of it. i just need to transfer the radio to my phone somehow but nothing shows up under adb devices. i'm trying to the lg mobile support tool now. its downloading the software. but if it doesn't work does any one have any fixes?
edit: i fixed it by following this http://forum.xda-developers.com/showthread.php?p=51637410&highlight=download+fail#post51637410
Click to expand...
Click to collapse
Thank You for sharing you fixed your issue pittbullmommy but the link you posted points back to a post about a failed run on LGFlashTool, will you please fix the link and point it to the post/guide you used to fix your phone, it may help others stuck in a similar situation, glad to hear you got it fixed and working, best of luck with it from here on out!
Hi all
was just about to start a new thread but didn't want to get into trouble..anyway I am in need of some assistance please.my ls980 has been bricked for some time now been searching all over the internet for a solution to be stuck back at square one.found this video on youtube which is pretty much exactly what my phone is doing.I have used lg flash tool to revert to stock and still nothing I lost root doing that but last night,I managed to regain root access I have no idea how but it happened when i clicked ioroot batch file i went into download mode and it stated bottom left ROOTED in red so i managed that but that is it still doing what is being shown in the video its on youtube
watch?v=PjLF-pBhZSY
please if anyone has the know how I would like to fix this phone rather then bin it thank you all happy 4th everyone
After using tot and flash tool to get back to stock, did you try going into stock recovery and do a factory data reset? I know it sounds stupid especially after a tot but try it. Couldn't hurt
Sent from my LG-LS980 using Tapatalk
Borderline noob here, so please bear with me...
I have been using TWRP 2.7.0.0 to do all my work, and I was able to get the Lego ROM installed with ZVA. I got into too big of a hurry and forgot to make a backup of stock. I've also been unsuccessful in trying to install ZVC modem and firmware. Thankfully ZVA works as does the LEGO ROM, but I'd like to have stock there to access as well. The stockZVC that's on the Android Development page has been getting stuck (bootloop?) on the Sprint Spark logo. I've done TWRP's factory reset with no success. Any help would be great.
Thanks in advance!
Yes sir I've tried that and more to no avail is there anything I can do through adb I'm on stock recovery phone doesn't stay on long enough to install anything
sarfdawg said:
Borderline noob here, so please bear with me...
I have been using TWRP 2.7.0.0 to do all my work, and I was able to get the Lego ROM installed with ZVA. I got into too big of a hurry and forgot to make a backup of stock. I've also been unsuccessful in trying to install ZVC modem and firmware. Thankfully ZVA works as does the LEGO ROM, but I'd like to have stock there to access as well. The stockZVC that's on the Android Development page has been getting stuck (bootloop?) on the Sprint Spark logo. I've done TWRP's factory reset with no success. Any help would be great.
Thanks in advance!
Click to expand...
Click to collapse
You ever get her fixed?
Hey guys,
I've had my Z1C for quite some time now and have messed around with various ROMs and such and if I ever came across a problem, I would always find a solution for it online, but this time it's different. I've done a lot of searching already, and found some similar problems on the internet, but none of them were quite like the one I've got right now.
Okay, first of all, for quite some time now I've been successfully using SlimKat and only updating every couple of months or so (and yes, since SlimKat officially came out on Z1C, I've been using the official version). It all began when I decided to update to a new version today. I went to the SlimRoms website, found my device on supported devices list, downloaded the zip file, downloaded gapps, and flashed them following the instructions. I've done this many times before already and it always worked without problems, but this time after the flashing finished (which was successful), my phone wouldn't turn on. After trying one thing after another, I realized that at first this was a driver problem, then I found out that my Z1C is now recognized as a Z1. Then I went back to SlimRoms website, and check it out- after clicking on Z1C (amami) on the supported devices list, it directs you (at least it directs me) to Z1 (honami) download page. I didn't even notice the different name, because every time I did this I didn't have any problems. So that's my current story. I will now list all the major symptoms.
- After holding volume up + power button until it shuts off I plug it into a wall charger or a pc through usb cable, first I get a red LED for like a second, then a pink/purple one for a two or three seconds, then it turns yellow and stays that way (charging?). After a few seconds I get the ability to browse the phone's files, but the device is named 'Z1'. If I plug it in without force shutting it off, it goes straight into yellow LED.
- If I try to repair it with Sony PC Companion, it gives me an error that the device is running modified software. Obvious.
- If I plug it in with flashtool on, at first it gives me an error that it cannot be identified and gives me a list of devices to choose from and then asks if I want my device to be permanently recognized as the one I chose. But this doesn't seem to work, because it gives me the same error every time I try to do it again. And if I try to flash a stock firmware, I get an error ERROR - Cannot delete C:\Flashtool\.\firmwares\prepared\boot. Previously it gave me errors regarding drivers, but no matter how many times I tried to install them with the driver installer from flashtool, uninstalling the device through device manager and so on, it didn't help. But after something I did that I'm not very sure about, I don't seem to get this error anymore.
- If I try to turn it on, it vibrates once as usual, gives me the pink/purple led for a couple seconds and then nothing.
There might be something I haven't mentioned, so feel free to ask. Not sure if that matters, but I'm on unlocked bootloader.
I seriously hope there's a fix for that, not sure if my unlocked bootloader would help with a warranty repair.
I guess that's all. Thanks in advance everyone.
VidmuxD said:
There might be something I haven't mentioned, so feel free to ask. Not sure if that matters, but I'm on unlocked bootloader.
Click to expand...
Click to collapse
Flash a Z1C kernel with fastboot and try the flashtool again.
XperienceD said:
Flash a Z1C kernel with fastboot and try the flashtool again.
Click to expand...
Click to collapse
Man, thanks a lot! Worked like a charm. I was thinking about flashing something via fastboot because it seemed to be working, but I didn't want to mess up anything else before making sure it was safe. Apparently the solution was simple. You've got my gratitude!
Hey people, got this cute little phone from my wife, was delighted initially because it seemed like custom rom haven and it really is cute little piece of functional white plastic (I meant, it was), but didn't last a day in my "new to Xperia" overconfident hands.
Anyway, I couldn't find any page that was foolproof and really explaining all the details step by step, so it kindaaa seeeems that I forgot the "unlock bootloader" part. I did several unsuccessful attempts at flashing official last version TWRP via terminal emulator and recommended app (can't remember name) - both seemed to do the work but couldn't boot into recovery, just regular reset. Then I tried Rushr app and flashed that TWRP image I had on SD card. I ran Reboot to recovery option - the thing just turned off. Now, what happens is that it vibrates for a second if I hold power button, but no go from there. If I connect it to PC blue light is on and PC says something like SP1FastBoot device connected or something like that.
So the big question is, is this soft or hard brick? What should poor bastard do in any case?
EDIT: Now I realized I get blue indicator light ONLY if I hold volume up before connecting to pc. If not, nothing lights. If I hold volume DOWN, I initially got "SEMC flash device connected", something like that.
your phone is completely alright, just install flashtool,its drives unlock the bootloader(there will be an option) and install recovery, after that flash a rom or stock backup
Thanks a lot, that's great news So in order to minimize risk of such noob mistakes I made (although still not sure what went wrong), I can use Flashtool for all my custom rom needs? Also, where can I download it, the links I found on XDA are dead, and googling brings out Sony's flashtool Emma. I really have no idea if it's the same thing or not, but from description it sounds like a tool for flashing stock roms, not customs. I need to be sure this time
EDIT: On XDA page dealing with TWRP installation: http://forum.xda-developers.com/xperia-m/orig-development/recovery-twrp-xpe it is specifically mentioned NOT to use Flashtool for flashing TWRP. Now it all gets confusing What does it mean, better chose CWM recovery or what?
ojas12345 said:
your phone is completely alright, just install flashtool,its drives unlock the bootloader(there will be an option) and install recovery, after that flash a rom or stock backup
Click to expand...
Click to collapse
Would you by any chance have some specific recommendations regarding recovery and rom combination? I prefer CM, but for instance, they say new CM 13 is for specific version of firmware (4.x, not sure which), and since my device is bricked, I have no way of checking what I have. Is there some combination of recovery/rom that's basically fool/brick proof? I found Flashtool, but I have to put roms in its folder, it doesn't come with or doesn't download firmwares from server or anything right?
I'm running in circles here, I'm stuck with Flashtool, and flashing Fota TWRP via Flashtool isn't recommended so... you see my problem
EDIT: I tried to unlock bootloader via Flashtool, I got middle finger: 08/042/2016 21:42:25 - INFO - Your phone bootloader cannot be officially unlocked
What does it mean? Am I doomed with stock firmware (even if I knew how to recover it) with "no custom roms" diet forever, or is there some "unofficial" solution?
C64Ever said:
EDIT: I tried to unlock bootloader via Flashtool, I got middle finger: 08/042/2016 21:42:25 - INFO - Your phone bootloader cannot be officially unlocked
What does it mean? Am I doomed with stock firmware (even if I knew how to recover it) with "no custom roms" diet forever, or is there some "unofficial" solution?
Click to expand...
Click to collapse
I have tried it with my device and i unlocked my bootloader successfully , just bootloop once , donno why is this happening with you maybe flashtool cannot recognise properly so try reinstalling the drivers from the flashtool folder!
ojas12345 said:
I have tried it with my device and i unlocked my bootloader successfully , just bootloop once , donno why is this happening with you maybe flashtool cannot recognise properly so try reinstalling the drivers from the flashtool folder!
Click to expand...
Click to collapse
There's nothing in .flashtool folder or subfolders, just a basic empty tree Seems Flashtool is a no go in my case, I think I'll try Sony's PC Companion, I think it's intended to recover stuck rom. And it requires 5 gigs of space on hard disk, so I guess it comes with everything already in the package
Fixed! Sony's Xperia tool is nothing short of miracle. Did the whole job, completely recovered device. Good job, Sony!