Hello all ...
i've had my XZU for approximately 2 months, left the phone on the table picked it to check it, and then the phone blacked out, i've reset it using power button/volume up, that didnt work out then i did the reset using the red button right next to the sim card that made it work but am receiving a black screen with the following massage "InitialBootSetup" isnt responding do you want to close it? "wait" and "ok" no matter which one i choose ... nothing happens still black screen, everything is still running in the background as i can still recieve whatsapp massages but i cant view them since the swipe top to bottom doesnt work, went to the sony world in my country (i bought my unit from another country) they told me its a defected unit
if its a defected unit, i dont mind sending it back to the original country to replace it, but i cant back it up! all of my data are on it and i cant access my device using the PC Companion nor the service update center,
PLEASE HELP!
Could you hot boot the v4 recovery boot image, using flash tool, to do a nandroid backup then pull the backup off using adt commands? or would that require a root and an UL bootloader?
English please?
AustenlorD said:
English please?
Click to expand...
Click to collapse
LOL.... you are officially a geek Blue!
hamdogg said:
LOL.... you are officially a geek Blue!
Click to expand...
Click to collapse
haha - I cant even get an android build environment up and compiling without errors...
I was hoping that someone with more experience and knew the commands would enlighten me and the OP, and say if it was even possible to do it without an unlocked bootloader
Still Suffering ...
my phone is still dead can anyone help please!
blueether said:
Could you hot boot the v4 recovery boot image, using flash tool, to do a nandroid backup then pull the backup off using adt commands? or would that require a root and an UL bootloader?
Click to expand...
Click to collapse
Will the phone go into either flash mode or fastboot mode?
you will need to install flashtool and read this post: http://forum.xda-developers.com/showthread.php?t=2428319
1/ Try fastboot mode and use flashtool to hot boot a recovery kernel https://mega.co.nz/#!chQG0YTa!MR8D3A2FLM4KvOtXzqxHTHZrmUwSHBULDrJux8TpGEw)
- I don't know if this image will work... @hamdogg ?
- I don't know if this will work with a locked bootloader or not... Is your bootloader unlocked? Once in the recovery do a nandroid backup, possibly to an external sd card.
If that has worked I would then try the next step:
2/ If you can get into flash mode I would flash .532 ftf from this thread and start over: http://forum.xda-developers.com/showthread.php?t=2453921 - THIS WILL WIPE DATA
3/ If you got a nandroid backup from the first step and got a ftf flashed then use one of the nandroid tools to pull your user data out of the backup
I hope that some one with more experience will come along and tell you if any of that will work. #1 shouldn't wipe any data I don't think, but use at your own risk etc...
blueether said:
Will the phone go into either flash mode or fastboot mode?
you will need to install flashtool and read this post: http://forum.xda-developers.com/showthread.php?t=2428319
1/ Try fastboot mode and use flashtool to hot boot a recovery kernel https://mega.co.nz/#!chQG0YTa!MR8D3A2FLM4KvOtXzqxHTHZrmUwSHBULDrJux8TpGEw)
- I don't know if this image will work... @hamdogg ?
- I don't know if this will work with a locked bootloader or not... Is your bootloader unlocked? Once in the recovery do a nandroid backup, possibly to an external sd card.
If that has worked I would then try the next step:
2/ If you can get into flash mode I would flash .532 ftf from this thread and start over: http://forum.xda-developers.com/showthread.php?t=2453921 - THIS WILL WIPE DATA
3/ If you got a nandroid backup from the first step and got a ftf flashed then use one of the nandroid tools to pull your user data out of the backup
I hope that some one with more experience will come along and tell you if any of that will work. #1 shouldn't wipe any data I don't think, but use at your own risk etc...
Click to expand...
Click to collapse
probably won't automatically boot using Fastboot, but yes that kernel would work. For a recovery boot.
I think keep it simple is the best option.
Power off your device off. Hold volume up and then Plug you're phone into you're pc.
Go to the Sony website, download the device drivers. (Google)
Download and open ' flashtool ' on your pc. Wait while more drivers are automatically downloaded via windows update.
Did that detect you're device? If not then you may need to return it.
Then also download flashtool divers. (google)
Then flash an FTF.
Done...
Read the threads on here so you become aware on how to work the software. Remember we can't do it for you, you have to research it yourself, and read yourself.
alrighty,
i've downloaded the files from the link, used the flashtool and got the following log:
28/030/2013 12:30:00 - INFO - Device connected in fastboot mode
28/030/2013 12:30:21 - INFO - Device Status: FASTBOOT mode
28/031/2013 12:31:04 - INFO - Please wait device is rebooting into fastboot mode (via Fastboot)
28/031/2013 12:31:04 - INFO - Device will soon reboot back into fastboot mode
28/031/2013 12:31:04 - INFO - Device disconnected
28/031/2013 12:31:06 - INFO - Device connected in fastboot mode
28/031/2013 12:31:11 - INFO - Fetching connected device info
28/031/2013 12:31:11 - INFO - Connected device info: [ EP7327JBLT ]
another thing that worked is that i did "Trim Area" S1 Backup and it worked as per following:
28/028/2013 12:28:48 - INFO - Please connect your device into flashmode.
28/028/2013 12:28:49 - INFO - Opening device for R/W
28/028/2013 12:28:49 - INFO - Reading device information
28/028/2013 12:28:49 - INFO - Phone ready for flashmode operations.
28/028/2013 12:28:49 - INFO - Current device : C6802 - EP7327JBLT - 1276-4950_R3B - 1271-5715_14.2.A.0.290 - GLOBAL-HSPA_14.2.A.0.290
28/028/2013 12:28:49 - INFO - Processing loader.sin
28/028/2013 12:28:49 - INFO - Checking header
28/028/2013 12:28:49 - INFO - Flashing data
28/028/2013 12:28:50 - INFO - Loader : S1_Root_6732 - Version : MSM8974_23 / Boot version : S1_Boot_MSM8974_LA1.04_15 / Bootloader status : ROOTABLE
28/028/2013 12:28:50 - INFO - Start Reading unit 000008B2
28/028/2013 12:28:50 - INFO - Reading TA finished.
28/028/2013 12:28:50 - INFO - Ending flash session
i tried the steps that were mentioned but i dont think that they have worked,
i've been going thru the forum for the past 2 weeks to find someone with a similar problem to mine but with no luck
btw flashtool did discover my device!
28/040/2013 12:40:00 - INFO - Fetching fastboot version info from connected device
28/040/2013 12:40:00 - INFO - FASTBOOT version info: [ version: 0.5 ]
28/040/2013 12:40:05 - INFO - Device Status: FASTBOOT mode
28/040/2013 12:40:11 - INFO - Please connect your device into flashmode.
28/040/2013 12:40:13 - INFO - Bootloader unlock canceled
28/040/2013 12:40:21 - INFO - Fetching connected device info
28/040/2013 12:40:21 - INFO - Connected device info: [ EP7327JBLT ]
28/040/2013 12:40:56 - INFO - Device will now exit fastboot mode and start booting into system
28/040/2013 12:40:57 - INFO - Device disconnected
28/041/2013 12:41:09 - INFO - Device connected with USB debugging off
28/041/2013 12:41:09 - INFO - For 2011 devices line, be sure you are not in MTP mode
28/043/2013 12:43:53 - INFO - List of connected devices (Device Id) :
28/043/2013 12:43:53 - INFO - - USB\VID_0FCE&PID_019C\EP7327JBLT Driver installed : true
28/043/2013 12:43:53 - INFO - List of ADB devices :
28/043/2013 12:43:53 - INFO - - none
28/043/2013 12:43:53 - INFO - List of fastboot devices :
28/043/2013 12:43:53 - INFO - - none
28/044/2013 12:44:04 - INFO - Beginning import of Sony Xperia Z Ultra
28/044/2013 12:44:06 - INFO - Import canceled
Okay!
did the hotboot but i got the following msg:
28/047/2013 12:47:21 - INFO - Device connected in fastboot mode
28/052/2013 12:52:38 - INFO - Selected kernel (boot.img or kernel.sin): C:\Users\Ali\Downloads\stock_02.img
28/052/2013 12:52:38 - INFO - HotBooting selected kernel
28/052/2013 12:52:39 - INFO - FASTBOOT Output:
downloading 'boot.img'...
OKAY [ 0.534s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 0.598s
what does the highlighted means?
well not hard bricked then
I didn't know if the hotboot would work or not, but was worth a try, another option is to do a backup of your data via ADB. Have a read of this thread http://forum.xda-developers.com/showthread.php?t=1420351. I don't know enough about ADB to say what commands to use, but you could do a full backup and a backup of just the user data (make sure to give them different names).
Once you have a backup of your data I would flash an FTF and start from fresh and restore one of the backups
Related
So you did the inevitable... you got a phone that's bricked.. fear not.. this happens to all of us.. consider it a "right of passage" when it comes to dealing with custom ROM's
Here at xda, help is never too far away (I was there once too)
I've tried to get you back to functioning latest Local 2.1 with recovery (xrecovery)
0) You'll lose all data with this method....
come to terms with that... not stuff on the sd card but data of your phone, sms'es, contacts, applications etc
1) Turn off your phone
Pull the battery and reinsert it if you have to...
2) Install Flashtool
go here and downlad flashtool
Install on your windows pc
Thank Androxyde and Bin4ry for this kickass tool
3) Download and flash stock 2.1
Go to this thread and download a 2.1 rom in your language of choice (Dont worry that it's not your local ROM)
4) Flash this rom using Flashtool
In the first link there is a how-to. follow it and flash the downloaded ROM from step 3
Once you have 2.1 on your phone,
5) Enable USB Debugging and Root
Use flashtool and root your phone using the simple button "Root" (I know!! what an awesome tool right!!?? )
Once rooted, disconnect the phone.
6) Get yourself a root file manager
Download a file manager capable of root access such as root explorer or solid explorer.
7) Access and edit the build.prop file
Open the file manager. U should get a superuser prompt to allow root access. Touch "Allow". Go to /system and mount the system as RW. there's a file there called build.prop. open it in a text editor. Find all instances of a number that looks like this 1238-9045 (this is my build number, yours will not be the same). Edit this number(all 3 instances) to look like your build number (Found on original box or behind the battery). Save the file and exit
8) Update via SEUS OR PC companion
Now connect your phone back. PC companion or SEUS will tell you there is a new update available. follow the instructions and you'll be running the latest 2.1 for your region and variant of the mini pro
9) [optional] Root and recovery
The new firmware installed by SEUS/PC companion is not rooted. If you need it, root again (same way as in step 5). once rooted, click "Ask root perms" on flashtool. Once root access is confirmed, install xrecovery from the menu.
Hope that helped!
Enjoy
Edit: if you get an error while opening flashtool saying "JVM could not be started because heap size bla bla bla..." Please try on another pc and maybe reinstall windows on urs
Bricked u20i
My phone keeps disconnecting nce the green light goes on. Please help
I have bricked xperia mini x10, and it's failing to boot. Debugging is turned off, so flashboot can't recognize it.
16/010/2012 19:10:31 - INFO - Device connected with USB debugging off
16/010/2012 19:10:31 - INFO - For 2011 devices line, be sure you are not in MTP mode
Click to expand...
Click to collapse
Can someone help?
Immortalis said:
I have bricked xperia mini x10, and it's failing to boot. Debugging is turned off, so flashboot can't recognize it.
Can someone help?
Click to expand...
Click to collapse
Repair it with SEUS or PC Companion.
Step A: leave your phone disconnected from your PC
Step B: Run SEUS/PC Companion, and select update
Step C: It doesn't recognise your phone because it's disconnected and give you a repair option
Step D: Select it, choose your model, it will download the firmware
Step Ea: You get a popup, Press the back-button on your phone while it's off and plug in the USB-Cable
Step Eb: If you can't turn off your phone, plug in the USB-cable and press home- and power-buttons at the same time, it will do a hard reboot and enter flashmode.
Step F: Wait till it's done...
everything past item 3 is pretty hard since we can't acces anything on phone(that's bricking a phone right) to enable usb debugging.
Good tutorial though for those who installed a custom rom and they want to revert to original plus root acces.
Any ideea how to force seus or flash to force flash?
slvjpn said:
everything past item 3 is pretty hard since we can't acces anything on phone(that's bricking a phone right) to enable usb debugging.
Good tutorial though for those who installed a custom rom and they want to revert to original plus root acces.
Any ideea how to force seus or flash to force flash?
Click to expand...
Click to collapse
You don't need usb-debugging in order to flash your phone.
SmG67 said:
You don't need usb-debugging in order to flash your phone.
Click to expand...
Click to collapse
tell this to my sister's x10 pro mini ). I know your right but the phone is @&&&@%))+6)-)-))-=+( up so it doesn't know human comands
Help needed !!
Hi to all,i`m new on this forum and new to Sony Ericsson!
Few days ago i did a repair option with the PcCompanion,becouse i removed to much apk`s.
After about 2 minutes,PcCompanion displayed error (code 100) and stopped flashing!
Searched the internet and found solution!
Flashtool!
But no way it keeps telleing me an error!
17/028/2012 17:28:11 - INFO - <- This level is successfully initialized
17/028/2012 17:28:11 - INFO - Flashtool Version 0.7.0.0 built on 2012-04-14 11:34:01
17/028/2012 17:28:11 - INFO - You can drag and drop ftf files here to start flashing them
17/028/2012 17:28:20 - INFO - Device disconnected
17/028/2012 17:28:38 - INFO - Selected Xperia X10 Mini Pro (U20)_2.1 (2.1.1.A.0.6) Reloaded_Greek (by Leajian).ftf
17/028/2012 17:28:38 - INFO - Preparing files for flashing
17/028/2012 17:28:53 - INFO - Please connect your device into flashmode.
17/029/2012 17:29:01 - INFO - Device connected in flash mode
17/029/2012 17:29:02 - INFO - Opening device for R/W
17/029/2012 17:29:03 - INFO - Reading device information
17/029/2012 17:29:03 - INFO - Phone ready for flashmode operations.
17/029/2012 17:29:03 - INFO - Start Flashing
17/029/2012 17:29:03 - INFO - Flashing loader
17/029/2012 17:29:04 - INFO - Loader : S1_Loader_Root_8e35 - Version : R4A045 / Bootloader status : UNROOTABLE
17/029/2012 17:29:04 - INFO - Flashing fota1.sin
17/029/2012 17:29:04 - INFO - Ending flash session
17/029/2012 17:29:04 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="MEMORY_CLASS";ERR_STATIC="HASH_VER";ERR_DYNAMIC="Block verification failed";
17/029/2012 17:29:04 - ERROR - Error flashing. Aborted
17/029/2012 17:29:05 - INFO - Device connected in flash mode
17/029/2012 17:29:07 - INFO - Device disconnected
17/029/2012 17:29:09 - INFO - Device connected in flash mode
please any help will be usefull!
How to bring back alive my X10 Mini Pro?
Now the only thing happends,green blink for 1 second and a bit vibration!
Also tryed with SEUS,no suc6!
(Damn I've been gone a while)
Not too sure of the greek firmware file bro.. can you put the link of the forum where you got it from? are you sure it is a stock firmware?
gixxerfan said:
Hi to all,i`m new on this forum and new to Sony Ericsson!
Few days ago i did a repair option with the PcCompanion,becouse i removed to much apk`s.
After about 2 minutes,PcCompanion displayed error (code 100) and stopped flashing!
Searched the internet and found solution!
Flashtool!
But no way it keeps telleing me an error!
17/028/2012 17:28:11 - INFO - <- This level is successfully initialized
17/028/2012 17:28:11 - INFO - Flashtool Version 0.7.0.0 built on 2012-04-14 11:34:01
17/028/2012 17:28:11 - INFO - You can drag and drop ftf files here to start flashing them
17/028/2012 17:28:20 - INFO - Device disconnected
17/028/2012 17:28:38 - INFO - Selected Xperia X10 Mini Pro (U20)_2.1 (2.1.1.A.0.6) Reloaded_Greek (by Leajian).ftf
17/028/2012 17:28:38 - INFO - Preparing files for flashing
17/028/2012 17:28:53 - INFO - Please connect your device into flashmode.
17/029/2012 17:29:01 - INFO - Device connected in flash mode
17/029/2012 17:29:02 - INFO - Opening device for R/W
17/029/2012 17:29:03 - INFO - Reading device information
17/029/2012 17:29:03 - INFO - Phone ready for flashmode operations.
17/029/2012 17:29:03 - INFO - Start Flashing
17/029/2012 17:29:03 - INFO - Flashing loader
17/029/2012 17:29:04 - INFO - Loader : S1_Loader_Root_8e35 - Version : R4A045 / Bootloader status : UNROOTABLE
17/029/2012 17:29:04 - INFO - Flashing fota1.sin
17/029/2012 17:29:04 - INFO - Ending flash session
17/029/2012 17:29:04 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="MEMORY_CLASS";ERR_STATIC="HASH_VER";ERR_DYNAMIC="Block verification failed";
17/029/2012 17:29:04 - ERROR - Error flashing. Aborted
17/029/2012 17:29:05 - INFO - Device connected in flash mode
17/029/2012 17:29:07 - INFO - Device disconnected
17/029/2012 17:29:09 - INFO - Device connected in flash mode
please any help will be usefull!
How to bring back alive my X10 Mini Pro?
Now the only thing happends,green blink for 1 second and a bit vibration!
Also tryed with SEUS,no suc6!
Click to expand...
Click to collapse
cant flash using SEUS...its saying i have latest version but in reality the phone is already bricked by me and not having the original stock firmware... now it just keeps restart with sony erricson logo and turns off again and bootloop...cant root, cant flash... heard that there is some special modified usb that will make the bootloader enter download mode so that we can flash fresh firmware inside it?
jasonmiracle said:
cant flash using SEUS...its saying i have latest version but in reality the phone is already bricked by me and not having the original stock firmware... now it just keeps restart with sony erricson logo and turns off again and bootloop...cant root, cant flash... heard that there is some special modified usb that will make the bootloader enter download mode so that we can flash fresh firmware inside it?
Click to expand...
Click to collapse
You can always flash... post your model and if your bootloader is locked or unlocked ( since you're on SE kernel logo, i assume it's locked), and i can provide you with stock firmware (E10i or U20i) to flash with flashtool.
SmG67 said:
You can always flash... post your model and if your bootloader is locked or unlocked ( since you're on SE kernel logo, i assume it's locked), and i can provide you with stock firmware (E10i or U20i) to flash with flashtool.
Click to expand...
Click to collapse
hi, i am u20i model...i accidentally locked the bootloader while having nna kernel i think, because flashing customised rom and kernel, my phone will enter bootloop, thats why i pressed Restore inside s1tool.exe, which got my bootloader locked....
and now that my bootloader is locked, and i cant root my phone without turning it on( the phone bricked cant turn on anymore) i cant unlock my bootloader to flash new kernels into it... please do provide stock firmware and rom for me... i can only flash stock kernel, but not the rom... after i flashed the stock u20i kernel, i dont know how to flash the original rom into my phone, since now my phone, didnt have the CWM or XRecover anymore, which can browse my SD card, and install the rom from .zip files....
flashing stock kernel no problem but did not know how to flash the stock rom
01/041/2012 15:41:58 - INFO - Device connected in flash mode
01/041/2012 15:41:59 - INFO - Opening device for R/W
01/041/2012 15:41:59 - INFO - Reading device information
01/042/2012 15:42:00 - INFO - Phone ready for flashmode operations.
01/042/2012 15:42:00 - INFO - Start Flashing
01/042/2012 15:42:00 - INFO - Processing loader
01/042/2012 15:42:00 - INFO - Checking header
01/042/2012 15:42:00 - INFO - Flashing data
01/042/2012 15:42:02 - INFO - Loader : S1_Loader_Root_8e35 - Version : R4A045 / Bootloader status : UNROOTABLE
01/042/2012 15:42:02 - INFO - Processing kernel.sin
01/042/2012 15:42:02 - INFO - Checking header
01/042/2012 15:42:02 - INFO - Flashing data
01/042/2012 15:42:05 - INFO - Ending flash session
01/042/2012 15:42:05 - INFO - Flashing finished.
01/042/2012 15:42:05 - INFO - Please unplug and start your phone
01/042/2012 15:42:05 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
01/042/2012 15:42:06 - INFO - Device connected in flash mode
Click to expand...
Click to collapse
unable to flash customised kernel probably because of the locked bootloader
01/052/2012 15:52:27 - INFO - Device connected in flash mode
01/052/2012 15:52:27 - INFO - Opening device for R/W
01/052/2012 15:52:28 - INFO - Reading device information
01/052/2012 15:52:28 - INFO - Phone ready for flashmode operations.
01/052/2012 15:52:28 - INFO - Start Flashing
01/052/2012 15:52:28 - INFO - Processing loader
01/052/2012 15:52:28 - INFO - Checking header
01/052/2012 15:52:28 - INFO - Ending flash session
01/052/2012 15:52:28 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_DYNAMIC="SIN header verification failed"
Click to expand...
Click to collapse
s1tool shows locked bootloader
i1109.photobucket.com/albums/h426/jasonforeverlove/11-2.jpg
problem- cant turn on the phone in order to choose usb debugging mode to root the phone
problem- SEUS cant detect update to my phone...
spent 3 weeks in vail...wish i can get it working ...reli hope to succeed in using customised ROM
jasonmiracle said:
hi, i am u20i model...i accidentally locked the bootloader while having nna kernel i think, because flashing customised rom and kernel, my phone will enter bootloop, thats why i pressed Restore inside s1tool.exe, which got my bootloader locked....
...
spent 3 weeks in vail...wish i can get it working ...reli hope to succeed in using customised ROM
Click to expand...
Click to collapse
Download this, It's the complete SE 2.1 Firmware (Kernel and ROM), flashable with flashtool.
(It's about 213.5MB, although the site may display it's less in your download dialog, but it will keep downloading till it's all there)
SmG67 said:
ubuntuone.com/515oWr7b8j4PeeZfm8xZ1pIt's the complete SE 2.1 Firmware (Kernel and ROM), flashable with flashtool.
(It's about 213.5MB, although the site may display it's less in your download dialog, but it will keep downloading till it's all there)
Click to expand...
Click to collapse
im trying this out... :victory:
tks for the thread, dude
My X10 mini pro won't turn on.
I've try the methods that mentioned in this thread but it all failed.
my phone still won't turn on. if i charged it, it's just boot for 2 seconds and then dead. repeatedly.
any suggestion?
*sorry for bad english
itwasgood said:
My X10 mini pro won't turn on.
I've try the methods that mentioned in this thread but it all failed.
my phone still won't turn on. if i charged it, it's just boot for 2 seconds and then dead. repeatedly.
any suggestion?
*sorry for bad english
Click to expand...
Click to collapse
Repair with Sony Update Service or PC Companion?
SmG67 said:
Repair with Sony Update Service or PC Companion?
Click to expand...
Click to collapse
already tried it. but still it won't turned on.
flashtool does not recognize my phone
flashtool does not recognize my x10 mini pro, screen still remains black, seus and pc companion does not recognize it either. what do i do?:crying:
itwasgood said:
already tried it. but still it won't turned on.
Click to expand...
Click to collapse
Your tried to unlock your booloader and now dont turn on?
If your phones was manufacturated after 11w29, you got a hard brick.
[Q] Help with "ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";E RR_DYNAMIC="SIN head"
Can you guys please help me with this error that happens when i try to flash:
02/025/2012 11:25:35 - INFO - <- This level is successfully initialized
02/025/2012 11:25:35 - INFO - Flashtool Version 0.6.9.1 built on 2012-04-09 19:22:19
02/025/2012 11:25:35 - INFO - You can drag and drop ftf files here to start flashing them
02/025/2012 11:25:41 - INFO - Device disconnected
02/026/2012 11:26:02 - INFO - Selected X10_SE_2.6.29_DualRecovery.ftf
02/026/2012 11:26:02 - INFO - Preparing files for flashing
02/026/2012 11:26:02 - INFO - Please connect your device into flashmode.
02/026/2012 11:26:06 - INFO - Device connected in flash mode
02/026/2012 11:26:06 - INFO - Opening device for R/W
02/026/2012 11:26:07 - INFO - Reading device information
02/026/2012 11:26:07 - INFO - Phone ready for flashmode operations.
02/026/2012 11:26:07 - INFO - Start Flashing
02/026/2012 11:26:07 - INFO - Flashing loader
02/026/2012 11:26:07 - INFO - Ending flash session
02/026/2012 11:26:07 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_DYNAMIC="SIN header verification failed"
02/026/2012 11:26:07 - ERROR - Error flashing. Aborted
02/026/2012 11:26:07 - INFO - Device connected in flash mode
02/026/2012 11:26:09 - INFO - Device disconnected
02/026/2012 11:26:09 - INFO - Device connected in flash mode
Repair your X10 via SEUS PC Companion if you tried to / or have unlock(ed) your Bootloader.
If you haven't, unlock your Bootloader using one of the tutorials.
But i'd recommend checking if you can unlock with s1tool first.
Tekkpriest said:
Repair your X10 via SEUS PC Companion if you tried to / or have unlock(ed) your Bootloader.
If you haven't, unlock your Bootloader using one of the tutorials.
But i'd recommend checking if you can unlock with s1tool first.
Click to expand...
Click to collapse
I can't, after a few seconds on flash mode, the phone restarts... =/
dont worry
dude just open your seus....
there click support...->update phone->repair(written in red color) do as directed ....
then remove ur phone battery for 5 secs.... put it in... while pressing the back button and keeping it pressed... connect the usb cable to the phone.... voila it recognizes the phone and flashes it with default rom....
i semi bricked my phone a million times.... this always saved my ASS......
nt a complete NOOB now though:angel:
rohit25 said:
dude just open your seus....
there click support...->update phone->repair(written in red color) do as directed ....
then remove ur phone battery for 5 secs.... put it in... while pressing the back button and keeping it pressed... connect the usb cable to the phone.... voila it recognizes the phone and flashes it with default rom....
i semi bricked my phone a million times.... this always saved my ASS......
nt a complete NOOB now though:angel:
Click to expand...
Click to collapse
I've tried... didn't work... the green light on flash mode goes of after a few seconds and it reistarts... on both SEUS and flashtool....
when I google it it seems to always point me in the direction of bootloader problems .
ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ER R_DYNAMIC="SIN header verification failed"
'''''I tried to figure out what's causing this and I end up with the "locked bootloader solution". I tried the instructions read here: http://unlockbootloader.sonymobile.com/instructions but when I typed ##7378423## no service menu was available...
'''''
answers that helped solve related!
If you didn't already have your bootloader unlocked and tools in place to reload the Android operating system (ie, ROMs or disk images), I strongly suspected you are completely screwed.
You can install an OS from scratch on your phone, but you need a specialized environment and tools to do so and those are often proprietary and/or secret. It is far easier to load a disk image (ROM) than do a base install. Either way, part of the process is an unlocked bootloader so that you can boot into an environment/tool instead of the existing OS. If you don't have a way to boot into something besides the installed system and have pooched that system - generally the only way you as a consumer have available to hack the bootloader - then you're up the creek. – Logos Apr 6 at 12:34
so basicly there saying if you did not unlock bootloader and a way of booting OTHER then the system itself ... you bricked it ..
if you cant flash
cant use recovery
whats left ?
If this hasnt bin solved another person had the exact same problem and got it fixed it seemed to be driver related (pc wise)
Only other info i can share is he used wotan to repair wich requires a fee ...
Sent from my x10 using xda premium
This is what i could find
www.wotanserver.com/en/sony-ericsson/se/xperia-x10/unlock-tool/debranding-flash
Seus coukd not help him aswell phone would not stay in flash mode
Or look up his post an ask him personnaly
In Q&A aswell
Sent from my x10 using xda premium
Hi!
I have a Xperia X10 Mini Pro (U20) with Stock Firmware (after recovery with "UpdateService" from SE).
I have installed CWM successfully with "CWMInstaller - Windows - v5".
When I try to install "MiniCM7-2.2.1-mimmi" (or 2.2.2) it says that I need a nAA-Kernel but successfully installs CM7.
When I do a reboot CWM says that "recovery is bad and has to be renewed". After that all I get is the white "Sony Ericsson" lettering (again with the option to start CWM when pressing the back button several times).
So I tried to follow this "Bootloader and kernel guide" and unlock my bootloader first using Flashtool. But when the phone restarts it "hangs" on the white "Sony Ericsson" lettering. When I try again, Flashtool tells me that it is not possible to unlock this bootloader.
My phone is produced 10W42 - could it really be that the ancient stock firmware is the only one which works?
All I want is a more modern and fast (lightweight) android version to use my old phone furthermore.
Thanks in advance for your advice and help!
greetz
davie
davie2000 said:
Hi!
I have a Xperia X10 Mini Pro (U20) with Stock Firmware (after recovery with "UpdateService" from SE).
I have installed CWM successfully with "CWMInstaller - Windows - v5".
When I try to install "MiniCM7-2.2.1-mimmi" (or 2.2.2) it says that I need a nAA-Kernel but successfully installs CM7.
When I do a reboot CWM says that "recovery is bad and has to be renewed". After that all I get is the white "Sony Ericsson" lettering (again with the option to start CWM when pressing the back button several times).
So I tried to follow this "Bootloader and kernel guide" and unlock my bootloader first using Flashtool. But when the phone restarts it "hangs" on the white "Sony Ericsson" lettering. When I try again, Flashtool tells me that it is not possible to unlock this bootloader.
My phone is produced 10W42 - could it really be that the ancient stock firmware is the only one which works?
All I want is a more modern and fast (lightweight) android version to use my old phone furthermore.
Thanks in advance for your advice and help!
greetz
davie
Click to expand...
Click to collapse
When you install CWM it is installed in the system part of the ROM. When you installed MiniCM7 it got wiped out, because MiniCM7 is for the nAa-kernel, and in that kernel CWM is built in. Which means it doesn't need to be in the MiniCM7 ROM. That's why you lost it.
And ofcourse it 'hangs' on the white SE lettering, because the ROM you installed does not work with the Sony Ericsson kernel.
You say you unlocked the bootloader, so why don't you flash the nAa-kernel?
Prepare flashtool to flash it, then attach the usb-cable and press home- and back-buttons together to force a restart. If the bootloader unlock was successful the flash will get through and after that, you'll have CWM back and you will continue to boot into the ROM too.
And be very careful not to flash the x10blrelock.ftf by accident, it will definitely break your phone. Best is to remove that from the flashtool/firmwares folder before you proceed.
SmG67 said:
...
You say you unlocked the bootloader, so why don't you flash the nAa-kernel?
Prepare flashtool to flash it, then attach the usb-cable and press home- and back-buttons together to force a restart. If the bootloader unlock was successful the flash will get through and after that, you'll have CWM back and you will continue to boot into the ROM too.
And be very careful not to flash the x10blrelock.ftf by accident, it will definitely break your phone. Best is to remove that from the flashtool/firmwares folder before you proceed.
Click to expand...
Click to collapse
Thanks for your answer, SmG67.
The problem is, that I have _tried_ to unlock the bootloader, but it did not finish. The "s1tool" still shows a capital R in the version ("RUNNING S1_EROM VER 'R8A029'") which means "not unlocked".
I also tried to install the kernel "U20_2.6.32.61-nAa-06.ftf" but this does not work as the bootloader is locked.
So can you give me a tip, how I could move on?
davie2000 said:
Thanks for your answer, SmG67.
The problem is, that I have _tried_ to unlock the bootloader, but it did not finish. The "s1tool" still shows a capital R in the version ("RUNNING S1_EROM VER 'R8A029'") which means "not unlocked".
I also tried to install the kernel "U20_2.6.32.61-nAa-06.ftf" but this does not work as the bootloader is locked.
So can you give me a tip, how I could move on?
Click to expand...
Click to collapse
You should not have proceeded to install the ROM in the first place if you didnt unlock it. Open SONY Update Service in PC, click repair and follow what they say. When you connect your phone to PC for repair, follow what SmG67 told you
Sent from my E10i using xda premium
pongnamu said:
You should not have proceeded to install the ROM in the first place if you didnt unlock it. Open SONY Update Service in PC, click repair and follow what they say. When you connect your phone to PC for repair, follow what SmG67 told you
Click to expand...
Click to collapse
Thanks for your reply, pongnamu!
I am unsettled now, so I want to make sure to do the right things:
I have "repaired" the phone using UpdateService and made the first setup - phone is now running and USB debugging is switched on.
Then I started flashtool and clicked on the flash-button (U20_2.6.32.61-nAa-06.ftf); followed the instructions but it quits working after phone restart with the following output:
Code:
13/006/2013 12:06:28 - INFO - <- This level is successfully initialized
13/006/2013 12:06:28 - INFO - Flashtool Version 0.9.12.1 built on 2013-06-04 22:50:00
13/006/2013 12:06:32 - INFO - Device disconnected
13/007/2013 12:07:27 - INFO - Selected U20 / nAa-06 / 2.6.32.61-nAa-06
13/007/2013 12:07:27 - INFO - Preparing files for flashing
13/007/2013 12:07:27 - INFO - Please connect your device into flashmode.
13/008/2013 12:08:09 - INFO - Device connected in flash mode
13/008/2013 12:08:09 - INFO - Opening device for R/W
13/008/2013 12:08:09 - INFO - Reading device information
13/008/2013 12:08:09 - INFO - Phone ready for flashmode operations.
13/008/2013 12:08:09 - INFO - Current device : U20i - CB511P8HKN - 1238-7168_R5B - 1235-3411_2.1.1.C.0.0 - WORLD-1-8_2.1.1.C.0.0
13/008/2013 12:08:09 - INFO - Start Flashing
13/008/2013 12:08:09 - INFO - Processing loader.sin
13/008/2013 12:08:09 - INFO - Checking header
13/008/2013 12:08:09 - INFO - Ending flash session
[COLOR="Red"]13/008/2013 12:08:09 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_DYNAMIC="SIN header verification failed"[/COLOR]
13/008/2013 12:08:09 - INFO - Device connected in flash mode
[COLOR="Red"]13/008/2013 12:08:10 - ERROR - Error flashing. Aborted[/COLOR]
13/008/2013 12:08:11 - INFO - Device disconnected
13/008/2013 12:08:12 - INFO - Device connected in flash mode
13/008/2013 12:08:27 - INFO - Device disconnected
13/008/2013 12:08:35 - INFO - Device connected with USB debugging off
13/008/2013 12:08:35 - INFO - For 2011 devices line, be sure you are not in MTP mode
The phone is connected and shows an orange LED and the loading screen; nothing else happens.
Regarding to S1info the bootloader is still locked:
Code:
RUNNING S1_EROM VER "[COLOR="Red"]R[/COLOR]8A029"
SOFTWARE AID: 0001
LOADER AID: 0001
FLASH ID: "0020/00BC"
LOADER VERSION: "R4A045"
MODEL (from GDFS): U20i
SOFTWARE VERSION: 1235-3411_2.1.1.C.0.0
CUSTOM VERSION: 1238-7168_R5B
FILESYSTEM VERSION: WORLD-1-8_2.1.1.C.0.0
SERIAL NO: xxxxxxxxxx
[COLOR="YellowGreen"]SEMC SIMLOCK CERTIFICATE[/COLOR]
Elapsed:12 secs.
Can you help me out again?
davie2000 said:
...
Can you help me out again?
Click to expand...
Click to collapse
Root the phone again with flashtool and then unlock the bootloader using flashtool. After that, you should be able to flash the kernel.
SmG67 said:
Root the phone again with flashtool and then unlock the bootloader using flashtool. After that, you should be able to flash the kernel.
Click to expand...
Click to collapse
Thanks to your reply, I was able to root the device with flashtool. Afterwards I successfully started Superuser and switched off the phone again.
While unlocking the bootloader (button BLU) with flashtool afterwards it gave me the following output:
Code:
13/037/2013 16:37:33 - INFO - <- This level is successfully initialized
13/037/2013 16:37:33 - INFO - Flashtool Version 0.9.12.1 built on 2013-06-04 22:50:00
13/037/2013 16:37:38 - INFO - Device disconnected
13/038/2013 16:38:54 - INFO - Device connected with USB debugging off
13/038/2013 16:38:54 - INFO - For 2011 devices line, be sure you are not in MTP mode
13/038/2013 16:38:54 - INFO - Device connected with USB debugging on
13/038/2013 16:38:55 - INFO - Connected device : SonyEricson X10 Mini Pro
13/038/2013 16:38:55 - INFO - Installed version of busybox : N/A
13/038/2013 16:38:55 - INFO - Android version : 2.1-update1 / kernel version : 2.6.29 / Build number : 2.1.1.C.0.0
13/039/2013 16:39:02 - INFO - Decrypting E:\Program Files (x86)\[HARDWARE]\[HANDY]\Flashtool\custom\root\PsNeuter\psneuter.tar.uue.enc to E:\Program Files (x86)\[HARDWARE]\[HANDY]\Flashtool\custom\root\PsNeuter\psneuter.tar.uue
13/039/2013 16:39:10 - INFO - Pushing E:\Program Files (x86)\[HARDWARE]\[HANDY]\Flashtool\custom\root\PsNeuter\psneuter.tar.uue to /data/local/tmp
13/039/2013 16:39:10 - INFO - Pushing E:\Program Files (x86)\[HARDWARE]\[HANDY]\Flashtool\.\devices\busybox\1.20.2\busybox to /data/local/tmp/busybox
13/039/2013 16:39:10 - INFO - Pushing E:\Program Files (x86)\[HARDWARE]\[HANDY]\Flashtool\custom\root\subin\Superuser\su to /data/local/tmp/su
13/039/2013 16:39:11 - INFO - Pushing E:\Program Files (x86)\[HARDWARE]\[HANDY]\Flashtool\custom\root\subin\Superuser\Superuser.apk to /data/local/tmp/Superuser.apk
13/039/2013 16:39:11 - INFO - Running part1 of Root Exploit, please wait
13/039/2013 16:39:12 - INFO - Running rootit
13/039/2013 16:39:13 - INFO - Waiting for device. After 60secs, stop waiting will be forced
13/039/2013 16:39:13 - INFO - Device disconnected
13/039/2013 16:39:14 - INFO - Device connected with USB debugging on
13/039/2013 16:39:15 - INFO - Running part2 of Root Exploit
13/039/2013 16:39:15 - INFO - Running rootit2
13/039/2013 16:39:17 - INFO - Finished!.
13/039/2013 16:39:17 - INFO - Root should be available after reboot!
13/039/2013 16:39:17 - INFO - Device disconnected
13/040/2013 16:40:53 - INFO - Please connect your device into flashmode.
13/041/2013 16:41:58 - INFO - Device connected in flash mode
13/041/2013 16:41:58 - INFO - Opening device for R/W
13/041/2013 16:41:58 - INFO - Reading device information
13/041/2013 16:41:58 - INFO - Phone ready for flashmode operations.
13/041/2013 16:41:58 - INFO - Current device : U20i - CB511P8HKN - 1238-7168_R5B - 1235-3411_2.1.1.C.0.0 - WORLD-1-8_2.1.1.C.0.0
13/041/2013 16:41:58 - INFO - Processing loader.sin
13/041/2013 16:41:58 - INFO - Checking header
13/041/2013 16:41:58 - INFO - Flashing data
13/042/2013 16:42:00 - INFO - Loader : S1_Loader_Root_8e35 - Version : R4A045 / Boot version : R8A029 / Bootloader status : UNROOTABLE
13/042/2013 16:42:00 - INFO - Start Reading unit 00000851
13/042/2013 16:42:00 - INFO - Reading TA finished.
13/042/2013 16:42:00 - INFO - Ending flash session
13/042/2013 16:42:00 - INFO - Waiting for device to reboot
13/042/2013 16:42:00 - INFO - Waiting for device
13/042/2013 16:42:00 - INFO - Device connected in flash mode
13/042/2013 16:42:01 - INFO - Device disconnected
13/042/2013 16:42:03 - INFO - Device connected in flash mode
13/042/2013 16:42:22 - INFO - Device disconnected
13/042/2013 16:42:31 - INFO - Device connected with USB debugging off
13/042/2013 16:42:31 - INFO - For 2011 devices line, be sure you are not in MTP mode
There are no errors this time, but again nothing more happens: phone is loading and showing orange LED.
I am surprised of the log line saying that "Bootloader status is UNROOTABLE"?
btw: S1info still gives me a uppercase "R" for "not unlocked".
Can I proceed flashing the U20_2.6.32.61-nAa-06.ftf?
davie2000 said:
There are no errors this time, but again nothing more happens: phone is loading and showing orange LED.
I am surprised of the log line saying that "Bootloader status is UNROOTABLE"?
btw: S1info still gives me a uppercase "R" for "not unlocked".
Can I proceed flashing the U20_2.6.32.61-nAa-06.ftf?
Click to expand...
Click to collapse
That will fail since your bootloader is still locked. Not sure why flashtool failed to unlock it, but maybe you can try the manual method, as linked to in the opening post of the kernel.
SmG67 said:
That will fail since your bootloader is still locked. Not sure why flashtool failed to unlock it, but maybe you can try the manual method, as linked to in the opening post of the kernel.
Click to expand...
Click to collapse
You mean to unlock bootloader with "msm7227_semc.cmd" as stated in the "Bootloader and kernel guide" (from above)?
Because this always leads to:
Code:
process requires standard 2.x android firmware.
Drücken Sie eine beliebige Taste . . .
Getting ROOT rights.
* daemon not running. starting it now *
* daemon started successfully *
and the phones LED flashing red sometimes
Thats not the first device I am using custom firmware with, but this phone resists all my attempts.
Finally I managed to run CM7 on my phone following this german instruction.
My mistake was that during the flash process the phone has to be switched on normally and not to be connected in flashmode (pressing back button while plugging USB in).
Thanks for your suggestions and hints!
Hey.
I unlocked my bootloader,installed fastboot drivers etc. and when i'm trying to get to fastboot mode, the PC recognises the device in ADB mode.
What shall i do to get to fastboot mode?
TheProdigee said:
Hey.
I unlocked my bootloader,installed fastboot drivers etc. and when i'm trying to get to fastboot mode, the PC recognises the device in ADB mode.
What shall i do to get to fastboot mode?
Click to expand...
Click to collapse
-power off device
-connect cable to pc (only, not phone yet)
-HOLD volume up key WHILE connecting cable to phone now
-blue led lit's --> connected in fastboot mode successfully
asd
I'm doin this,but still adb mode.
TheProdigee said:
I'm doin this,but still adb mode.
Click to expand...
Click to collapse
so you got the blue led lit
i think you worry to much. if the led is BLUE, YOU are in fastboot mode. all okay then. just do your task now (like flash kernel)
The led isn't blue,the sony logo appears. It's in ADB mode. I have no idea I'm trying to downgrade the phone from 4.1.B.0.587 to 4.1.A.0.562,and everytime I flash the 0.562 kernel the phone stays at 0.587. Flashtool doesn't show any errors. I don't know what's goin on with this phone :laugh: Strange
07/055/2014 23:55:36 - INFO - Selected Bundle for SonyEricson Xperia Ray (ST18). FW release : 4.1.A.0.562. Customization : Kernel
07/055/2014 23:55:36 - INFO - Preparing files for flashing
07/055/2014 23:55:36 - INFO - Please connect your device into flashmode.
07/055/2014 23:55:50 - INFO - Device connected in flash mode
07/055/2014 23:55:51 - INFO - Opening device for R/W
07/055/2014 23:55:51 - INFO - Reading device information
07/055/2014 23:55:51 - INFO - Phone ready for flashmode operations.
07/055/2014 23:55:51 - INFO - Current device : ST18i - CB511VNQ2J - 1252-5860_R1I - 1248-9545_4.1.A.0.562 - WORLD-i_4.1.B.0.587
07/055/2014 23:55:51 - INFO - Start Flashing
07/055/2014 23:55:51 - INFO - Using an unofficial loader
07/055/2014 23:55:51 - INFO - Device loader has not been identified. Using the one from the bundle
07/055/2014 23:55:51 - INFO - Processing loader.sin
07/055/2014 23:55:51 - INFO - Checking header
07/055/2014 23:55:51 - INFO - Flashing data
07/055/2014 23:55:51 - INFO - Processing of loader.sin finished.
07/055/2014 23:55:53 - INFO - Loader : S1_Loader_Root_773f - Version : R4A066 / Boot version : r9A021 / Bootloader status : ROOTED
07/055/2014 23:55:53 - INFO - No bootdelivery to send
07/055/2014 23:55:53 - INFO - Processing kernel.sin
07/055/2014 23:55:53 - INFO - Checking header
07/055/2014 23:55:53 - INFO - Flashing data
07/055/2014 23:55:55 - INFO - Processing of kernel.sin finished.
07/055/2014 23:55:55 - INFO - Ending flash session
07/055/2014 23:55:55 - INFO - Flashing finished.
TheProdigee said:
The led isn't blue,the sony logo appears. It's in ADB mode. I have no idea I'm trying to downgrade the phone from 4.1.B.0.587 to 4.1.A.0.562,and everytime I flash the 0.562 kernel the phone stays at 0.587. Flashtool doesn't show any errors. I don't know what's goin on with this phone :laugh: Strange
Click to expand...
Click to collapse
ah ok i know wheres the problem 1st of all there is NO ''adb mode'' adb is a programm that interacts with your android. its no mode.
there 2 modes:
a) fastboot(mode) --> blue led --> need for flashing a kernel via fastboot [adb does this] /connect phone while hold volume UP
b) flashmode --> green led --> need for flashing ftf (firmware files) via flashtool like you want. /connect phone while hold volume DOWN
so from now, why you want to downgrade?? whats your goal??
--> if you want just run stock (latest 587 ICS) with root forget about all just get on 587 firmware & use the ''e-root'' app --> done.
--> if you want to run a custom rom (with custom kernel), just do this: put rom.zip & other files like gapps on sd. put phone into fastboot mode --> flash kernel --> boot into cwm (by pressing continesly volume down on kernel bootscreen) --> install the rom like the instructins say. most (if not all) custom ROM & kernel are prerooted, no need to do it manually
anyway if you still just want to switch to any stock rom build, HERES a good tutorial & you can download desired fw there too.
HINT: dont connect phone until flashtoll gives you that popup to do it! now connect (powered off) phone via FLASHMODE (green led) for this you need to hold volume DOWN button while connecting.
im sure you missing sth
good luck
I didn't know about this E-root app, thanks! My goal was rooting the phone!
But I'm still unable to get in fastboot mode. I'm holding volume up,connect the USB and sony logo appears.
TheProdigee said:
I didn't know about this E-root app, thanks! My goal was rooting the phone!
But I'm still unable to get in fastboot mode. I'm holding volume up,connect the USB and sony logo appears.
Click to expand...
Click to collapse
so how did you connected the phone for ulocking bootloader?? (it needs fastboot mode)
if you want to switch the firmware use flashtool!! (it flashes the whole ROM, INCLUDING kernel, no need to do this twice)--> & flashtool needs flashmode (hold volume down while connect)
fastboot is only need if you only want to switch te kernel.
if still no sucess make sure: dont do if allready...
-install android SDK (just press install packages, leave all like it is, google usb drivers are most important)
-install drivers for your phone from drivers folder in flashtool install location on your pc
also try:
-Go to settings > Security > Mark "Unknown sources"
Settings > Developer options > Mark USB debugging
Settings > Xperia > connectivity > USB connection mode > select MSC mode
Connect your phone to PC ( IMPORTANT > Skip PC Companion installation pop up on your phone.) and wait for the adb drivers to be installed.
good luck!
e root app link: http://forum.xda-developers.com/showthread.php?t=2219781
I unlocked it with testpoint method. This could be the problem?
TheProdigee said:
I unlocked it with testpoint method. This could be the problem?
Click to expand...
Click to collapse
maybe. i dont have xperience with testpoint method. but even on the testpoint thread he shows to flash kernel via fastboot (im confused) so i dont know whats wrong....
did you installed the android sdk & flashtool drivers?? (important)
& why not unlocked by official method??
That's the point,I think i'm unlocked the BL,the flashtool log says that (Bootloader status : ROOTED), and I still can't get to fastboot mode. Should I reinstall the drivers or something?
I did the testpoint method because i get Bootloader unlock allowed: No message, but the unlock was succsessful according to the flashtool log,wasn't it?
what happens when you enter
Code:
adb reboot bootloader
?
Nothing,phone reboots normally.
This may related to kernel problem. I think I used the wrong one.(Fast boot is accessible)
today i tried to install lollipop on my D6503 Z2 device running 17.xxxxxx (I cant remember and i cant turn my phone on now)
i downloaded the file from this thread http://forum.xda-developers.com/xperia-z2/development/stock-d6503-23-1-0-690-bal-rooted-t3057150
however, i cant flash the zip file since i cannot get in to recovery mode. (when ever i try to reboot into recovery mode it just boot into normal stock rom) So i tried installing TWRP from the play store app "TWRP Manager" https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager&hl=en but it failed. I remember it said something like "the installation has failed. Either you have already install custom recovery or there might be some other problems. Do you want to reboot in recovery mode?" I clicked "yes" then it booted into stock rom again. After failing I went into TWRP website and manually download the latest version of TWRO 2.8.6.0 on this website http://dl.twrp.me/sirius/ and proceed to download flashtool form www.flashtool.net/ .
I conected my device and install dual boot recovery "Z2-lockeddualrecovery2.8.3-RELEASE.installer". I choose no. 3 first (which nothing happened) and then i choose no. 1. Its said successful. I tried to reboot again which didn't change anything.
Then I opened the flashtool i downloaded and get into fastboot mode( since flash mode cant flash the img file for me. or I just don't know how to do it). In fast boot option I clicked "reboot into fastboot mode via ADB" every went fine I got the blue light with black screen. Then I clicked "select Kernel to Flash" which is my TWRP recovery. After it is done, I tried to reboot back to stock however after the sony logo is shown the screen went dark and I couldn't do anything beside pressing volume up and power to force shut down. I rebooted and nothing changes.
In short
-I tried to install lollipop pre rooted on my Z2
-Couldn't instal. I can't reboot into recovery mode
-try to manually install TWRP by downloading from its website and flash in fastboot mode (i choose "select Kernel to Flash")
-Now I cannot boot my device back to stock. After the sony is shown, the screen went black. I need to forced shutdown.
-Just realized that my kernel version changed to 3.4.0cyanogenmod
-I probably flashed the wrong kernel
-I cannot get into recovery mode
-i did do a TWRP back up
Btw here is my log when trying to flash the TWRP
28/052/2015 00:52:45 - INFO - For 2011 devices line, be sure you are not in MTP mode
28/052/2015 00:52:46 - INFO - Device connected with USB debugging on
28/052/2015 00:52:46 - INFO - Connected device : Sony Xperia Z2
28/052/2015 00:52:46 - INFO - Installed version of busybox : BusyBox v1.22.1-Stericson (2014-01-25 17:27:18 CET) multi-call binary.
28/052/2015 00:52:46 - INFO - Android version : 4.4.2 / kernel version : 3.4.0-perf-g35f9635 / Build number : 17.1.2.A.0.314
28/052/2015 00:52:46 - INFO - Checking root access
28/052/2015 00:52:47 - INFO - Root Access Allowed
28/052/2015 00:52:47 - INFO - Installing toolbox to device...
28/052/2015 00:52:47 - INFO - Pushing C:\Flashtool\custom\root\ftkit.tar to /data/local/tmp
28/052/2015 00:52:48 - INFO - Running installftkit as root thru sysrun
28/054/2015 00:54:31 - INFO - Selected null
28/054/2015 00:54:31 - INFO - Flash canceled
28/054/2015 00:54:38 - INFO - Launching Service Menu. Plese check on your phone.
28/055/2015 00:55:53 - INFO - Device Status: ADB mode
28/056/2015 00:56:19 - ERROR - This action can only be done in fastboot mode
28/056/2015 00:56:32 - INFO - Please wait device is rebooting into fastboot mode (via ADB)
28/056/2015 00:56:32 - INFO - Device will soon enter fastboot mode
28/056/2015 00:56:33 - INFO - Device disconnected
28/056/2015 00:56:35 - INFO - Device connected in fastboot mode
28/057/2015 00:57:00 - INFO - Selected kernel (boot.img or kernel.sin): D:\Downloads\twrp-2.8.6.0-sirius.img
28/057/2015 00:57:00 - INFO - Flashing selected kernel
28/057/2015 00:57:02 - INFO - sending 'boot' (11928 KB)...
28/057/2015 00:57:02 - INFO - OKAY [ 0.397s]
28/057/2015 00:57:02 - INFO - writing 'boot'...
28/057/2015 00:57:02 - INFO - OKAY [ 0.864s]
28/057/2015 00:57:02 - INFO - finished. total time: 1.261s
28/057/2015 00:57:02 - INFO - FASTBOOT Output:
sending 'boot' (11928 KB)...
OKAY [ 0.397s]
writing 'boot'...
OKAY [ 0.864s]
finished. total time: 1.261s
28/057/2015 00:57:02 - INFO - Please check the log before rebooting into system
28/057/2015 00:57:18 - INFO - Device Status: FASTBOOT mode
28/058/2015 00:58:13 - INFO - Device will now exit fastboot mode and start booting into system
28/058/2015 00:58:13 - INFO - Device disconnected
28/059/2015 00:59:11 - ERROR - This action can only be done in fastboot mode
28/059/2015 00:59:17 - INFO - Device Status: NOT FOUND
28/003/2015 01:03:27 - INFO - Device connected with USB debugging on
28/003/2015 01:03:27 - ERROR - Cannot identify your device.
28/003/2015 01:03:27 - INFO - Selecting from user input
28/004/2015 01:04:01 - INFO - Connected device : D65XX
28/004/2015 01:04:02 - INFO - Installed version of busybox : BusyBox v1.22.1 bionic (2015-03-25 05:26 +0000) multi-call binary.
28/004/2015 01:04:02 - INFO - Android version : / kernel version : 3.4.0cyanogenmod-g449fd42 / Build number :
28/004/2015 01:04:02 - INFO - Phone in recovery mode
28/004/2015 01:04:02 - INFO - Root Access Allowed
I'm going to go sleep now. Will try to wake up early as possible to reply.
Did you search? And try this? http://forum.xda-developers.com/showthread.php?p=53220435
o0 Matt 0o said:
Did you search? And try this? http://forum.xda-developers.com/showthread.php?p=53220435
Click to expand...
Click to collapse
That surely will do the trick. I personally had the same problem years back, and having had my first Sony Xperia phone, I did manage to get over it. What I did practically is detailed in that link posted by @o0Matt0o , today I see someone with same problem and I can imagine the frustration, because I did too.
Good luck friend.
sublinker said:
That surely will do the trick. I personally had the same problem years back, and having had my first Sony Xperia phone, I did manage to get over it. What I did practically is detailed in that link posted by @o0Matt0o , today I see someone with same problem and I can imagine the frustration, because I did too.
Good luck friend.
Click to expand...
Click to collapse
I've 'bricked' my phones many times. I know it frustrating. But Xperias are so easy to fix.
The best thing about a brick is you learn how to fix it.
o0 Matt 0o said:
I've 'bricked' my phones many times. I know it frustrating. But Xperias are so easy to fix.
The best thing about a brick is you learn how to fix it.
Click to expand...
Click to collapse
Sure friend, just talking about first time experience and that's what he's going through right now. You and I are now conversant with fixing these easily because it's not our first time.
o0 Matt 0o said:
Did you search? And try this? http://forum.xda-developers.com/showthread.php?p=53220435
Click to expand...
Click to collapse
Thank you I know it may seem simple but I just have no idea what to do. Its is fixed now.
sublinker said:
That surely will do the trick. I personally had the same problem years back, and having had my first Sony Xperia phone, I did manage to get over it. What I did practically is detailed in that link posted by @o0Matt0o , today I see someone with same problem and I can imagine the frustration, because I did too.
Good luck friend.
Click to expand...
Click to collapse
Thank you Im going to try flash lollipop again