Phone doesn't boot after unlocking bootloader. - Sony Ericsson Xperia Neo, Pro

Phone doesn't boot after unlocking bootloader. - Sony Ericsson Xperia Neo, Pro

Hey,
I just unlocked the bootloader of a Xperia Neo MT15 (.69 firmware) using the testpoint method. Everything worked fine, the device identified as 'r...', I can get in fastboot and execute commands. Executing 'fastboot boot recoveryNeo.img' exits normally with download ... okay, booting..., but no new devices (like adb interface) appear, I tried several times.
But, what is worse, I can't boot the phone regularly, the screen is constantly black. After 'fastboot reboot' or removing battery and plugging in USB cable, the green LED goes on and a 'SEMC Flash Device' appears after a few seconds the LED goes off and the device vanishes. Pressing the power button causes the phone to vibrate shortly but nothing else happens.
Any idea how to get the phone working again. Thanks million times in advance for any help.
Regards!
buergi

Flash GB Kernel...such as Alliance kernel,Night-elf Kernel...

megatpanji said:
Flash GB Kernel...such as Alliance kernel,Night-elf Kernel...
Click to expand...
Click to collapse
Thanks megatpanji. Do I have to use a different Kernel? Isn't it possible to use the Stock kernel?
I followed the progress as for example described here for the Xperia Arc but I found similar descriptions for the Neo.
As I understood the progress after unlocking fastboot is open and I can hot-boot a recovery image. From where, in turn, I can push su using adb or install it from zip. Isn't that right? I'd like to understand what exactly went wrong or if I just misunderstood the progress.

why messing so much. use flashtool to flash any custom kernel. then boot into recovery (CWM), place your custom rom zip on sd card, and flash via recovery.
if wanting stock rom, then use flashtool to flash stock ftf file.

rajxelton said:
why messing so much
Click to expand...
Click to collapse
actually I tried messing up as little as possible As I said, at the moment, I'd just like to root the stock rom.
As the .69 firmware is unrootable and I did not mess up anything by downgrading I decided to use the method for unlocked bootloaders, which took me only a few minutes. Everything worked perfectly except the last step. The phone does neither boot normally nor in recovery.
Guess I'll have to begin searching a new kernel.
Nevertheless I would love to understand what went wrong so that I will not make the same error again in the future. Especially why the phone appears as "SEMC Flash Device" and shuts down shortly after it again.

i think, the kernel doesnt support the rom. you were on stock rom, so you must use stock based kernel.

rajxelton said:
i think, the kernel doesnt support the rom. you were on stock rom, so you must use stock based kernel.
Click to expand...
Click to collapse
well but I didn't flash any new kernel, did I? I only executed
Code:
fastboot boot recoveryNeo.img
As I understood this does not flash anything but does only hotboot into the recovery.

recoveryNeo.img is the kernel . this code is used to flash kernels

rajxelton said:
recoveryNeo.img is the kernel . this code is used to flash kernels
Click to expand...
Click to collapse
well and what is than the following for?
Code:
fastboot flash boot boot.img
I thought flashing writes the image to NAND while hot-booting boots from the image without changing the flash memory.
Isn't this the case?

uh :\ m mad ! maybe you are righht. i never used all this. but the boot loops you are getting is related to kernel only. maybe corrupted

So after all I tried flashing the kernel from the 4.0.2.A.0.62 ftf, which did not fix the problem. Then I relocked bootloader and flashed everything (except data wipe) and just as I thought it didn't work neither the phone booted and after some further 5 long minutes of trembling (while the phone refills the wiped cache) the phone turned on as always.
One possible reason for the trouble might be that the battery was almost fully discharged although as I started hacking it was at about 70%. Seems the phone discharged heavily over night. I guess I'll charge the phone now and will try again some other day.

Related

[How-To] Boot up custom roms when the Screen stays black...

Problem: A few people wrote that they are having problems to boot up after flashing a new kernel/rom with fastboot. When the on key is pressed, the phone vibrates but the screen stays black - no boot up screen, nothing.
Solution: Instead of flashing the new kernel via fastboot (fastboot flash boot boot.img), try booting up directly via fastboot (fastboot boot boot.img), keep the phone pluged in, press the on key for 2 seconds, battery loading icon will appear, press again the on button for 2 seconds and the phone will finally boot up.
When battery power runs low making the phone switch off and you have no pc near to boot up via custom kernel, you can still boot up the original Kernel as long as you are on stock Rom (CM7 didn´t work for me, because the kernel is flashed over fastboot).
Worked for me, hope this helps you as well.

Okay that worked..buuuutt it could only be turned on with a computer =='

lofike said:
Okay that worked..buuuutt it could only be turned on with a computer =='
Click to expand...
Click to collapse
You´re right, but if on stock, you can still boot up with the original kernel, when no computer is near. So what i do is not flashing the custom kernel at all, but only booting up. So dont use the "fastboot flash boot boot.img" command, only use the "fastboot boot boot.img" command to boot um and leave the original kernel on the Phone...
1st Post was updated

arihellmichimich said:
You´re right, but if on stock, you can still boot up with the original kernel, when no computer is near. So what i do is not flashing the custom kernel at all, but only booting up. So dont use the "fastboot flash boot boot.img" command, only use the "fastboot boot boot.img" command to boot um and leave the original kernel on the Phone...
1st Post was updated
Click to expand...
Click to collapse
This thread is not a good idea. If you flash a rom and it does not boot up. Thats means something is wrong. Forcing it to boot will cause more problems down the road.

AndroHero said:
This thread is not a good idea. If you flash a rom and it does not boot up. Thats means something is wrong. Forcing it to boot will cause more problems down the road.
Click to expand...
Click to collapse
Okay you're scaring me lol...

I had the same problem as the OP, i thought it was bricked, so i got it replaced by verizon. Sadly i can't unlock my bootloader anymore, so i'm stuck on stock, but at least I'm rooted.

AndroHero said:
This thread is not a good idea. If you flash a rom and it does not boot up. Thats means something is wrong. Forcing it to boot will cause more problems down the road.
Click to expand...
Click to collapse
Its the only way i get my phone to boot a custom kernel and it runs great. No problems at all, overclocking works great, quadrant score of 2600. If battery runs off, Im still able to boot (without custom Kernel), so no need to bother.
Somehow flashing with fastboot doesnt work on my phone. So when I flash with fastboot, im not able to boot anymore until i flash a whole rom with flashtool. If someone knows how to flash only the custom kernel with flashtool id like to know...

[Q] Kernel problems

I was trying to flash a AOSP rom for my evo3D, used GUI flash app to flash the kernel and then flashed the AOSP rom. it was hanging on HTC screen. I've read somewhere if it does this the kernel does not support that ROM. so I restored my backup and when i did I had no wifi (running viperROM sense). I know that was because of the AOSP kernel I flashed, I used the same program and flashed the sprint stock kernel and restored my back up once again. it just hangs on the Htc screen now. my back-up no longer works.
1. is there anyway to flash a kernel using fastboot (I have 1.50 unlocked)?
update:
flashed a new recovery hoping it will change my kernel back (restored backup). it does not hang on the HTC screen anymore. but now its just a black screen, I am getting the received text sounds. when i press on the power button the home, menu, back, and search lights go on but not the screen.

k2buckley said:
I haven't used the flash image gui app, so I don't have experience with it to say what might have gone wrong with the flash. However, if I were you, I would try booting your phone into recovery using fastboot. It sounds like something didn't flash right, and by booting into recovery using fastboot, you'll ensure that your boot.img (the part that has the kernel) flashes properly. So have a fresh copy of the rom you want to flash. Connect your phone to computer, and adb reboot bootloader. Then you should be in fastboot, and it'll say fastboot usb on your phone. (make sure you're in the folder that has a copy of your recovery.img) and type fastboot boot recovery.img. That will boot you to recovery. From that point, just flash the rom like normal. No need to flash the kernel separately. After you flash the rom, just try booting before flashing anything else, and see if it works.
Click to expand...
Click to collapse
I will try this.
update: I did what you told me and I restored my old backup. Thank you!

TheFlatulentFox said:
I was trying to flash a AOSP rom for my evo3D, used GUI flash app to flash the kernel and then flashed the AOSP rom. it was hanging on HTC screen. I've read somewhere if it does this the kernel does not support that ROM. so I restored my backup and when i did I had no wifi (running viperROM sense). I know that was because of the AOSP kernel I flashed, I used the same program and flashed the sprint stock kernel and restored my back up once again. it just hangs on the Htc screen now. my back-up no longer works.
1. is there anyway to flash a kernel using fastboot (I have 1.50 unlocked)?
update:
flashed a new recovery hoping it will change my kernel back (restored backup). it does not hang on the HTC screen anymore. but now its just a black screen, I am getting the received text sounds. when i press on the power button the home, menu, back, and search lights go on but not the screen.
Click to expand...
Click to collapse
k2buckley said:
I haven't used the flash image gui app, so I don't have experience with it to say what might have gone wrong with the flash. However, if I were you, I would try booting your phone into recovery using fastboot. It sounds like something didn't flash right, and by booting into recovery using fastboot, you'll ensure that your boot.img (the part that has the kernel) flashes properly. So have a fresh copy of the rom you want to flash. Connect your phone to computer, and adb reboot bootloader. Then you should be in fastboot, and it'll say fastboot usb on your phone. (make sure you're in the folder that has a copy of your recovery.img) and type fastboot boot recovery.img. That will boot you to recovery. From that point, just flash the rom like normal. No need to flash the kernel separately. After you flash the rom, just try booting before flashing anything else, and see if it works.
Click to expand...
Click to collapse
I not only wrote the tool in question, Flash Image GUI, but have used it many many times on quite a few different devices and can speak to the specific process/steps followed in the OP.
I'm going to try and take a different approach to answering this post than I normally do, let me know if this makes sense.
There are essentially three sets of files which need to be loaded on the device in order for the device to boot properly and everything operate properly. By loading these three sets of files, there will be no stuck on htc boot screen and no wifi doesnt work issues.
1) The kernel
2) The kernel modules
3) The system files for the Android OS, slang term, ROM.
If any of these three sets of files have any type of conflict, there will be problems. From the standard recovery boot mode, HTC unlock only allows 2 of the above three sets of files to be flashed. By blocking one of the three sets of files from being loaded, HTC allows the system to easily get out of sync resulting in random boot issues, WiFi issues, etc.
In addition to these issues, even if all three files are properly loaded, if any of them are incompatible with any one of the other, there will be issues.
The key to avoiding issues is making sure all three of these sets of files are one, loaded properly and two compatible.
Flash Image GUI, loads the kernel and the kernel modules, but due to Linux/Android system limitations, is not able to load the system files. The recovery mode with HTC unlock loads both the kernel modules and the system files but is not able to load the kernel.
When using Flash Image GUI first, the kernel and the kernel modules both get loaded. Booting directly into the recovery will allow the system files to be loaded and the kernel modules will get reloaded.
As long as the kernel, kernel modules and system files (ROM) are all compatible, there should be no issues with this process. If somebody wants to experiment grab a kernel and match with a ROM, then we return to the two key points, make sure they are loaded properly and that they are all compatible.
Regarding how to restore a backup, if you refer back to the OP in the Flash Image GUI thread, there are steps at the bottom of the OP under the Troubleshooting section which show the proper process. I've quoted them below and bolded the needed action, for your convenience:
joeykrim said:
Troubleshooting after Rebooting:
Issue #1: If the device hangs or reboots while on the splash screen, the kernel (or packaged ramdisk in the kernel) is NOT compatible with your device!!!
Solution for #1: Have to boot into fastboot and load the custom recovery to flash a known good kernel or restore a previously known good nandroid backup. Command: fastboot boot c:\downloads\cwm-recovery.img
Issue #2: If the device hangs or reboots while on the boot animation, the ROM is likely NOT compatible with the kernel!!!
Solution for #2: Have to boot into fastboot and load the custom recovery to flash a known good ROM/kernel combination either from a zip file or restore from a nandroid backup.
Click to expand...
Click to collapse
Hopefully this makes sense. Let me know if you still have questions. I'm writing this off the top of my head but trying to think through it from a different angle so things are clear and organized.

joeykrim said:
As long as the kernel, kernel modules and system files (ROM) are all compatible, there should be no issues with this process. If somebody wants to experiment grab a kernel and match with a ROM, then we return to the two key points, make sure they are loaded properly and that they are all compatible.
Click to expand...
Click to collapse
that must have been my mistake, the kernel modules and ROM were not compatible. thanks joeykrim and k2buckley

So i rooted my POCO X2 and installed orange fox recovery, used the same rom which came pre-installed. Now a persistent notification of "SERIAL CONSOLE ENABLED, performance maybe impacted check bootloader to disable" hovers in my notifications, my device is running on ANDROID 11. Please help!

[Q] No PG86IMG

Hi all,
It seems that I have managed to brick my device. I am on 1.50 S-ON, and was trying to flash one of the ICS ROMs through the usual method (push the zip, reboot to bootloader, fastboot to the recovery.img) which I have used multiple times successfully in the past, but the phone ended up in a reboot loop. I did not apply any firmware changes (at least not voluntarily!), since the ROM (CleanROM was the first one I tried to flash) said that this was necessary. I tried flashing different ROMs (GB or ICS), and a Nandroid backup, but none seem to work. The only clue I have as to what is going on is that fastboot says that there is no image of PG86DIAG.[zip,nbh] and PG86IMG.[zip,nbh,tar,aes,enc]. This looks like a radio issue to me, but I don't want to do anything stupid (again!), so any input would be appreciated.
Thanks a lot!

I would recommend flashing this: http://dev-host.org/ru0ow8ps0i01/PG86IMG_2.17.651.5.zip
Its haus's 2.17 fw package and has everything in it. I flashed the new fw and a rom and had the same bootloop and nothing stopped it except returning to a stock system. After flashing this i flashed a new rom and everything worked as normal.
Rename the zip file PG86IMG.zip put on root of sdcard and reboot to bootloader. (Just in case anyone needs to know) This is a completely stock rom and fw so you will need to flash another rom with superuser in it for root apps.
Hope that helps...

If I'm reading it correctly you tried ics flash and it failed and now you wanna go back or flash to another working Rom right?....if so, unplug phone from comp, pull battery and reboot into bootloader (power +vol up), pick fastboot, connect to comp, use fastboot command to get into recovery and wipe and flash a working Rom....that's also assuming you already have a Rom on sdcard......if not then push a tom to card or in cwm you can mount USB storage and do drag and drop....I really hope that points you in right direction....let me know.
With hboot 1.5 s-on you have to do the fastboot command in order to get into recovery in order to do flashes...
Sent from my PG86100 using XDA

It booted!
Hey both,
I did somehow manage to flash a regular GB ROM. The weird thing is I was doing the exact same thing I was doing before (which is onefasttereopro's method), but for whatever reason it didn't work until now. The one thing that did in fact change is that I tried flashing Chad's kernel to see if any of the ICS ROMs would work, but I don't think that's it (it seems to have been overwritten, judging by /proc/version and the fact that USB works). Thank you very much both for your help, I am very glad that I have a working device again!

how to install cwm on xperia go on jelly bean?

I've tried to look around, and the only method I seem to find is to flash back to ics, root, then install it. But is there a way to install it on jelly bean without going back to ics?

I had successfully rooted my go before, but that was with bin4ry's easy root exe. I kinda regretted not installing cwm sooner when I was still rooted in ICS. I also have no idea how to fast boot on this phone, I read a guide before, but my phone goes into charging mode before I get to click anything.

arenaboy007 said:
I had successfully rooted my go before, but that was with bin4ry's easy root exe. I kinda regretted not installing cwm sooner when I was still rooted in ICS. I also have no idea how to fast boot on this phone, I read a guide before, but my phone goes into charging mode before I get to click anything.
Click to expand...
Click to collapse
try this.
http://forum.xda-developers.com/showthread.php?t=2250695

Ben Ling said:
try this.
http://forum.xda-developers.com/showthread.php?t=2250695
Click to expand...
Click to collapse
OK last night I was stuck at step 13, but just this morning for some reason, my phone went on fastboot mode, and the computer automatically installed the drivers. Now that it's on fastboot, I tried moving on to step 14-15, this is where I get stuck again... It says open a cmd within the sdk folder, and enter the command on step 15, I get the message, "fastboot.exe is not recognized as an internal or external command." I checked both tools, and platform-tools, they both have fastboot.exe. what am I missing? I extracted the adt-bundle on my desktop if that helps.

Ben Ling said:
try this.
http://forum.xda-developers.com/showthread.php?t=2250695
Click to expand...
Click to collapse
I have not tried any custom ROM yet, the only thing I tried before was rooting my official ICS .10 from bin4ry..
hmmmm..

arenaboy007 said:
OK last night I was stuck at step 13, but just this morning for some reason, my phone went on fastboot mode, and the computer automatically installed the drivers. Now that it's on fastboot, I tried moving on to step 14-15, this is where I get stuck again... It says open a cmd within the sdk folder, and enter the command on step 15, I get the message, "fastboot.exe is not recognized as an internal or external command." I checked both tools, and platform-tools, they both have fastboot.exe. what am I missing? I extracted the adt-bundle on my desktop if that helps.
Click to expand...
Click to collapse
Try just fastboot without the .exe.
fastboot flash boot.img

androidmeda said:
Try just fastboot without the .exe.
fastboot flash boot.img
Click to expand...
Click to collapse
Actually it doesn't have the ".exe", maybe I should try it with ".exe"?

arenaboy007 said:
Actually it doesn't have the ".exe", maybe I should try it with ".exe"?
Click to expand...
Click to collapse
Put the boot.img in platform-tools and open a command window from there (shift+rclick on empty spot > open command window from here)
Then try fastboot again. Should work with or without .exe
PS. How did you get this far with the steps and have fastboot not work if you went through unlocking bootloader?
Stock and locked xGO beans.

androidmeda said:
Put the boot.img in platform-tools and open a command window from there (shift+rclick on empty spot > open command window from here)
Then try fastboot again. Should work with or without .exe!
PS. How did you get this far with the steps and have fastboot not work if you went through unlocking bootloader?
Stock and locked xGO beans.
Click to expand...
Click to collapse
Fastboot was already working, I just need to unlock the bootloader. How the fastboot driver installed, I have no idea, maybe it was when I restarted my pc this morning that sorted things out. The computer found the driver by itself for some reason. Another thing that probably help was when I pressed the volume up button by itself, and not with the power button.

-delete-
I'm an idiot. Lol. How'd it go?
Stock and locked xGO beans.

androidmeda said:
-delete-
I'm an idiot. Lol. How'd it go?
Stock and locked xGO beans.
Click to expand...
Click to collapse
I get this when I put the line from step 15, I get this message...
What now?

In the beginning I used this guide to install fastboot. Maybe it will help.
http://dottech.org/21534/how-to-ins...ows-computer-for-use-with-your-android-phone/
Drivers I installed from latest flashtool.
Stock and locked xGO beans.

androidmeda said:
In the beginning I used this guide to install fastboot. Maybe it will help.
http://dottech.org/21534/how-to-ins...ows-computer-for-use-with-your-android-phone/
Drivers I installed from latest flashtool.
Stock and locked xGO beans.
Click to expand...
Click to collapse
So I tried looking around the forums for another method on unlocking the bootloader. And I tried the SE bootloader unlocker. It seemed to me it worked in unlocking the bootloader although I still don't know how to confirm, since I still get the error on my previous post. I tried moving on and flash the boot.img and I started to get the 4 flashing colors, but I'm a bit confused on step 5 and 6 in installing cwm. And I get the flashing colors everytime I restart my phone, is this normal? I'm not finish in installing cwm so that might be a reason.

arenaboy007 said:
So I tried looking around the forums for another method on unlocking the bootloader. And I tried the SE bootloader unlocker. It seemed to me it worked in unlocking the bootloader although I still don't know how to confirm, since I still get the error on my previous post. I tried moving on and flash the boot.img and I started to get the 4 flashing colors, but I'm a bit confused on step 5 and 6 in installing cwm. And I get the flashing colors everytime I restart my phone, is this normal? I'm not finish in installing cwm so that might be a reason.
Click to expand...
Click to collapse
4 flashing colors indicate boot.img was flashed successfully (because normal boot img doesn't do that). And you will be seeing that everytime while using this ROM. You should be able to boot to CWM by holding down vol- when it starts flashing and right after the vibrate. Keep it held til you see CWM. If that doesn't work, pop your question over there in that thread for OP to read.
Stock and locked xGO beans.

androidmeda said:
4 flashing colors indicate boot.img was flashed successfully (because normal boot img doesn't do that). And you will be seeing that everytime while using this ROM. You should be able to boot to CWM by holding down vol- when it starts flashing and right after the vibrate. Keep it held til you see CWM. If that doesn't work, pop your question over there in that thread for OP to read.
Stock and locked xGO beans.
Click to expand...
Click to collapse
Thanks for the advice! CWM is installed. Time to look for custom roms!

arenaboy007 said:
I've tried to look around, and the only method I seem to find is to flash back to ics, root, then install it. But is there a way to install it on jelly bean without going back to ics?
Click to expand...
Click to collapse
I have a networked locked go (ST27i) on O2 network in the UK. The boot loader cannot be unlocked. I installed the latest generic firmware 6.2.A.1.100 via flashtool (to de-brand the O2 startup/shutdown sequence which slowed the phone a little). I rooted the phone via the DoomLoRD .bat exploit.
I have tried three versions of CWM from playstore and they all say they are incompatible with my device, so I cannot install it? As my bootloader cannot be unlocked I understand I cannot flash a custom kernel or use a custom rom.
I assume as the OP says (and after many hours reading), to install CWM recovery to a ST27i on the latest JB rom, you must flash the device from JB back to ICS, then install the CWM recovery/kernel. Then to flash the JB rom you do it through CWM and not via flash tool if you want to go back to JB, is that correct? Thus keeping the CWM recovery option on startup.
thanks in advance for any help with this!
smirnofred

smirnofred said:
I have a networked locked go (ST27i) on O2 network in the UK. The boot loader cannot be unlocked. I installed the latest generic firmware 6.2.A.1.100 via flashtool (to de-brand the O2 startup/shutdown sequence which slowed the phone a little). I rooted the phone via the DoomLoRD .bat exploit.
I have tried three versions of CWM from playstore and they all say they are incompatible with my device, so I cannot install it? As my bootloader cannot be unlocked I understand I cannot flash a custom kernel or use a custom rom.
I assume as the OP says (and after many hours reading), to install CWM recovery to a ST27i on the latest JB rom, you must flash the device from JB back to ICS, then install the CWM recovery/kernel. Then to flash the JB rom you do it through CWM and not via flash tool if you want to go back to JB, is that correct? Thus keeping the CWM recovery option on startup.
thanks in advance for any help with this!
smirnofred
Click to expand...
Click to collapse
You assumed it right. Installing CWM was actually quite easy, I was just not familiar with the steps provided on sony's website. Don't use the CWM from playstore, use the ones on this forum. Make sure the necessary files are installed, like ADB, and Android SDK tools, then install CWM through your PC with your phone connected on fastboot(Press volume up as you connect your phone). Replace the boot.img from the android platform-tools, with the boot.img from the CWM file you downloaded. Open command prompt inside platform-tools folder and type "fastboot flash boot boot.img " without the quote. When you see a bunch of numbers come up that means you have just successfully installed CWM, then type "fastboot reboot". If you see flashing colors during boot then that means you were successful. To go to CWM menu, wait for the led to flash then press volume down.

[Q] Stuck On Sony Screen

I have the castor windy version 16gb SGP511. I was previously rooted but not unlocked. I unlocked the boot loader. Installed the twrp image on the pac man thread which i think was dual recovery cause Philz,Cwm came out, so I can install lollipop version of the rom. Made a backup of the stock rom. Followed this instructions - Install the Lollipop ROM + GApps+SuperSU using whatever Recovery you have.
- Turn off device completely.
- Press <Volume Up> and plug USB cable.
- LED should turn blue.
- Send command: "fastboot erase recovery"
- Send command for Castor_Windy: "fastboot flash recovery TWRP_Castor_Windy.img"
- Send command for Castor: "fastboot flash recovery TWRP_Castor.img"
- Unplug USB cable.
- Device will reboot.
- When LED turns pink press <Volume Up> and <Volume Down> several times.
- You should now see TWRP
I wasnt fast enough so stock rom booted. I used Adb reboot recovery to access recovery and did as the above mentioned. Wiped i tried to install the rom which failed. Rebooted back to system and got stuck in Sony boot up screen. I can access fastboot. Read though the forums I have to find a ftf or a system image file and use a flash tool. What ftf file or system image my I use use which will let me root my device again.
Thanks Steve

Kamaleon said:
What ftf file or system image my I use use which will let me root my device again.
Thanks Steve
Click to expand...
Click to collapse
Try this Xperia downloader tool. Should let you see which versions are which. If you want an easy root, then stay away from the KitKat builds, unless you want to unlock bootloader.
http://forum.xda-developers.com/cro...xperifirm-xperia-firmware-downloader-t2834142
Use Flashtool to flash your downloaded ftf file. Just make sure your device is charged.
http://forum.xda-developers.com/showthread.php?t=2335555
I believe flashtool will even install the drivers for your 511

Thanks for the reply. Flashed ftf file and my tablet is up an running. Do I have to unlock my bootloader again or is it unlocked already?

Kamaleon said:
Thanks for the reply. Flashed ftf file and my tablet is up an running. Do I have to unlock my bootloader again or is it unlocked already?
Click to expand...
Click to collapse
Well, now this depends.
If you previously had KK running, and flashed a original version JellyBean ROM, then it probably locked the bootloader again.
If you flashed the same version as you had previously installed, then it didn't lock it again.

Moscow Desire said:
Well, now this depends.
If you previously had KK running, and flashed a original version JellyBean ROM, then it probably locked the bootloader again.
If you flashed the same version as you had previously installed, then it didn't lock it again.
Click to expand...
Click to collapse
Thanks. Yes i was unlocked already, went through the process again to verify. Trying to upgrade my firmware which is 17...........402. to a kk build firmware. I have the old cwm recovery 6.0.4.6. being trying to upgrade or even change recovery to any recovery except dual recovery. Through fastboot which none of them stick. Fastboot erase recovery
fastboot flash recovery recovery.img all of them(CWM,TWRP,PHILZ). The process goes smoothly but when I access recovery the old recovery comes up. What seems to be problem? I cant change my recovery or even upgrade it. I never have had this problem before some insight needed before i take a wrong turn. LOL.

Kamaleon said:
Thanks. Yes i was unlocked already, went through the process again to verify. Trying to upgrade my firmware which is 17...........402. to a kk build firmware. I have the old cwm recovery 6.0.4.6. being trying to upgrade or even change recovery to any recovery except dual recovery. Through fastboot which none of them stick. Fastboot erase recovery
fastboot flash recovery recovery.img all of them(CWM,TWRP,PHILZ). The process goes smoothly but when I access recovery the old recovery comes up. What seems to be problem? I cant change my recovery or even upgrade it. I never have had this problem before some insight needed before i take a wrong turn. LOL.
Click to expand...
Click to collapse
You mean the "factory" recovery comes up.
Well, just for info, you don't need to run the fastboot "erase" command when installing a recovery. Not necessary as the new image file will overwrite the existing.
Also, you don't exactly need to flash a recovery either. You can connect via USB, boot to bootloader, and run the "fastboot boot recovery.img (or whatever you named it) as long as your custom recovery is in the same folder as the fastboot.exe. This will just the custom recovery without installing it, thus allowing you to flash stuff.
As to why your fastboot flash isn't sticking, I'm new to the Sony tab, so haven't learned all the quirks yet as compared to Acer tabs.

Moscow Desire said:
You mean the "factory" recovery comes up.
Well, just for info, you don't need to run the fastboot "erase" command when installing a recovery. Not necessary as the new image file will overwrite the existing.
Also, you don't exactly need to flash a recovery either. You can connect via USB, boot to bootloader, and run the "fastboot boot recovery.img (or whatever you named it) as long as your custom recovery is in the same folder as the fastboot.exe. This will just the custom recovery without installing it, thus allowing you to flash stuff.
As to why your fastboot flash isn't sticking, I'm new to the Sony tab, so haven't learned all the quirks yet as compared to Acer tabs.
Click to expand...
Click to collapse
I mean cwm recovery v6.0.4.6 comes up the one I installed Doomlords thread with the advanced kernel. I ran fastboot erase recovery command to see if the new recoverys would stick and replace it but it didn't. I have done your instructions before hand thats how I am accessing the bootloader. "fastboot boot recovery.img all add this command to see If the new recovery would pop up. Thanks for the reply.

Kamaleon said:
I mean cwm recovery v6.0.4.6 comes up the one I installed Doomlords thread with the advanced kernel. I ran fastboot erase recovery command to see if the new recoverys would stick and replace it but it didn't. I have done your instructions before hand thats how I am accessing the bootloader. "fastboot boot recovery.img all add this command to see If the new recovery would pop up. Thanks for the reply.
Click to expand...
Click to collapse
Well, here's what I think is going on.
1. You installed Doomlords kernel. Note that this is a foto-kernel, which means the kernel itself has a partition that contains a recovery. What this means, is that as long a the fota-kernel was not replaced, then that specific recovery will be there.
2. You flashed a normal recovery. Now, I think this is there, but because of the fota-kernel, the fota-kernel is taking precedence.
Like I said, I don't know a lot about this Sony tab and the different partitions,as they are different from other tablets I am familiar with.
What puzzles me, is that if you flash a new "ftf" without changing any options in Flashtool, it "should" rewrite "every" partition on the tab, and install Stock recovery.
Now, based on my experience with Acer A500x and A700x tablets, I can say there are times when your issue happens. Rare, but it does happen. Things say they flash ok, but the old stuff still remains. The only option at that point, was to go back to a totally original version of the firmware.
Not sure I'm helping you on this. But the good thing, is that you can Fastboot Boot Recovery.
MD

Moscow Desire said:
Well, here's what I think is going on.
1. You installed Doomlords kernel. Note that this is a foto-kernel, which means the kernel itself has a partition that contains a recovery. What this means, is that as long a the fota-kernel was not replaced, then that specific recovery will be there.
2. You flashed a normal recovery. Now, I think this is there, but because of the fota-kernel, the fota-kernel is taking precedence.
Like I said, I don't know a lot about this Sony tab and the different partitions,as they are different from other tablets I am familiar with.
What puzzles me, is that if you flash a new "ftf" without changing any options in Flashtool, it "should" rewrite "every" partition on the tab, and install Stock recovery.
Now, based on my experience with Acer A500x and A700x tablets, I can say there are times when your issue happens. Rare, but it does happen. Things say they flash ok, but the old stuff still remains. The only option at that point, was to go back to a totally original version of the firmware.
Not sure I'm helping you on this. But the good thing, is that you can Fastboot Boot Recovery.
MD
Click to expand...
Click to collapse
I started from zero again flashed ftf Firmware SGP511_17.1.1.A.0.402. Verfied that i was bootloader unlocked I still was. Used fastboot to flash Dooms Kernel, without a problem used cwm revovery to flash Supersu. Tried to upgrade my firmware with the prerooted rooms in thread flashed with out a problem but no difference was provided. Verified in settings and initial firmware stands (SGP511_17.1.1.A.0.402). Tried to flash CM12 got stuck on a bootloop. Fastboot flashed the boot img provided didn't work for me so I flahed Teslas rom Followed instructions provided
1. Make sure you have CWM installed and a working nandroid backup
2. Download the ROM.
3. Place the ROM on your SD-Card.
4.Extract boot.img included in zip and fastboot flash it via Flashtool or CMD
5. Reboot to recovery.
6. Wipe data-factory reset/cache partition/dalvik cache
7. Flash the ROM.
Flash went through but when I try to access recovery through the rom or adb recovery doesnt come up. The tablet just stays black on recovery screen and the tablets led turns yellow. I have adb access so went to access fastboot flashed different recoverys. None of them (flashed without a problem), work but if a flashed Dooms I have access to recovery again, but loose functionality of the rom it gets stuck on sony screen. I have to do the steps all over again without a working recovery. This has being a learning experience I am HTC guy so the process with sony products is new to me as well. So where do you think I should go on from here; flash a newer ftf or lock and unlock my bootloader again to see if something happens or just move on jajajajj . Anyways thanks a lot for your help.

Kamaleon said:
I started from zero again flashed ftf Firmware SGP511_17.1.1.A.0.402. Verfied that i was bootloader unlocked I still was. Used fastboot to flash Dooms Kernel, without a problem used cwm revovery to flash Supersu. Tried to upgrade my firmware with the prerooted rooms in thread flashed with out a problem but no difference was provided. Verified in settings and initial firmware stands (SGP511_17.1.1.A.0.402). Tried to flash CM12 got stuck on a bootloop. Fastboot flashed the boot img provided didn't work for me so I flahed Teslas rom Followed instructions provided
1. Make sure you have CWM installed and a working nandroid backup
2. Download the ROM.
3. Place the ROM on your SD-Card.
4.Extract boot.img included in zip and fastboot flash it via Flashtool or CMD
5. Reboot to recovery.
6. Wipe data-factory reset/cache partition/dalvik cache
7. Flash the ROM.
Flash went through but when I try to access recovery through the rom or adb recovery doesnt come up. The tablet just stays black on recovery screen and the tablets led turns yellow. I have adb access so went to access fastboot flashed different recoverys. None of them (flashed without a problem), work but if a flashed Dooms I have access to recovery again, but loose functionality of the rom it gets stuck on sony screen. I have to do the steps all over again without a working recovery. This has being a learning experience I am HTC guy so the process with sony products is new to me as well. So where do you think I should go on from here; flash a newer ftf or lock and unlock my bootloader again to see if something happens or just move on jajajajj . Anyways thanks a lot for your help.
Click to expand...
Click to collapse
Well, I'm not sure which route to take.
However, I will tell you what I have learned the other day.
I have the 521 with unlocked bootloader. Rooted with my own boot.img, flashed SuperSU using "flashboot boot recovery.img" (yeah, sometimes it doesn't show on the display, so it takes a few times).
Now, other day I was going to check out the new LyPop pre-rooted. Fastboot flash recovery recovery,img, and it won't boot it to recovery like it should. Like it's not flashed. Tried it a couple times. Now, I didn't install the dual recovery as I'm not sure how that kernel (boot.img) will interact with my current tabs OS. Not to mention I need it for my work until tomorrow. But strangely it sounds like the same issue you have.
This weekend I will investigate it. As for me, I will probably flash the Stock ftf lyPop build, and just root it using a modified boot.img.
One thing I do know, is flashing a custom recovery to the "recovery" partition, doesn't seem to work like it used to work on other devices. It seems the flashing to the "Fota kernel" partition seems to be the only method that works. This is what happens when you flash that dual recovery, or any recovery that has a boot image using "Fota". Probably explains why you can't get rid of it using "fastboot erase recovery". because it's erasing the wrong partition. Only flashing a full ftf gets rid of it, because the ftf has a new FotaKernel it flashes.
Eh, something like that. Will look at it this weekend.

Better Mobile App

welcome