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
Related
Hi, i'm a xperia mini (st15i) user & trying to install smultron karnel to install miui, so i'm connecting the phone in fastboot mode. then in flashtool "select karnel to flash". after i'm locating the file flashtool showing this msg
01/045/2012 00:45:35 - INFO - Device connected with USB debugging on
01/045/2012 00:45:44 - INFO - Connected device : ST15
01/045/2012 00:45:45 - INFO - Installed version of busybox : BusyBox v1.19.0 (2011-08-14 23:46:58 CDT) multi-call binary.
01/045/2012 00:45:45 - INFO - Android version : 2.3.3 / kernel version : 2.6.32.9-perf
01/045/2012 00:45:46 - INFO - Root Access Allowed
01/048/2012 00:48:29 - INFO - Device disconnected
01/053/2012 00:53:19 - INFO - Device connected in fastboot mode
01/053/2012 00:53:59 - INFO - Launching Fastboot Toolbox 1.0 by DooMLoRD
01/054/2012 00:54:00 - INFO - Device Status: FASTBOOT mode
01/054/2012 00:54:07 - INFO - Selected kernel (boot.img or kernel.sin): C:\boot_smultron_rc3_final (2).img
01/054/2012 00:54:07 - INFO - Flashing selected kernel
01/054/2012 00:54:07 - INFO - FASTBOOT Output:
sending 'boot' (6006 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.001s
my device is already rooted. what should i do now??
please help
thanks in advance
Is your phone's bootloader unlocked?
Yes it is
2kun said:
Yes it is
Click to expand...
Click to collapse
Got proper fastboot drivers installed?
Try removing spaces from the filename, or just rename it to boot.img and then try again.
Try these, will try to think more.
how to know that proper fastboot driver is installed or not??
have tried renaming the file to "boot.img' but the same result
Someguyfromhell said:
Got proper fastboot drivers installed?
Try removing spaces from the filename, or just rename it to boot.img and then try again.
Try these, will try to think more.
Click to expand...
Click to collapse
after connecting in fastboot mode my pc is saying in the taskbar "eject s1fastboot" so i think it's installed.
don't know what is wrong. really feeling frustrated
Did some research on Google, couldn't find solution to this, neither can I think anything more.
Phone is in fastboot mode(blue LED), bootloader is unlocked...I can't see the problem.
Anyone else, that would have ideas?
Someguyfromhell said:
Did some research on Google, couldn't find solution to this, neither can I think anything more.
Phone is in fastboot mode(blue LED), bootloader is unlocked...I can't see the problem.
Anyone else, that would have ideas?
Click to expand...
Click to collapse
thanks for your try
anyone else??
looking at the log, the kernel that u try to flash had a space in its name isnt it?
Code:
boot_smultron_rc3_final (2).img
remove the space, eg just rename it as
Code:
boot.img
and try again.
fastboot and adb run in cmd. filename must not contain any space in it, mandatory.
i've tried with boot.img with flashtool. the output was same. how to install with cmd ???
ummm seems like u didnt understand what i'm trying to say :/
forget about it.
use this instead
http://forum.xda-developers.com/showthread.php?t=1560613
problem solved. rooted by the file "runme.bat" now it's working & i think my whole night project is successful
thanks a lot
u guys are simply great
I used a custom rom "Real ICS 5.1" for past two months, suddenly this evening mobile restarted, and stuck with home screen, after i remove and insert the battery, now mobile stucks after sony logo, i restarted many times, but no luck.
just panic now.
connect with flashtool and get the log below.
04/034/2012 20:34:54 - INFO - <- This level is successfully initialized
04/034/2012 20:34:55 - INFO - Flashtool Version 0.6.8.0 built on 2012-02-26 19:26:25
04/034/2012 20:34:55 - INFO - You can drag and drop ftf files here to start flashing them
04/035/2012 20:35:01 - INFO - Device disconnected
04/035/2012 20:35:54 - INFO - Device connected in flash mode
04/037/2012 20:37:27 - INFO - <- This level is successfully initialized
04/037/2012 20:37:37 - INFO - Device disconnected
04/038/2012 20:38:02 - INFO - Device connected in flash mode
04/038/2012 20:38:42 - INFO - Device disconnected
04/039/2012 20:39:19 - INFO - Device connected with USB debugging off
04/039/2012 20:39:19 - INFO - For 2011 devices line, be sure you are not in MTP mode
04/041/2012 20:41:53 - INFO - Device disconnected
04/041/2012 20:41:58 - INFO - Device connected with USB debugging off
04/041/2012 20:41:58 - INFO - For 2011 devices line, be sure you are not in MTP mode
04/041/2012 20:41:58 - INFO - Device connected with USB debugging on
04/041/2012 20:41:59 - INFO - Connected device : WT19
04/041/2012 20:41:59 - INFO - Installed version of busybox : BusyBox v1.19.4-wraithdu (2012-02-16 23:47:29 CST) multi-call binary.
04/041/2012 20:41:59 - INFO - Android version : 4.0.4 / kernel version : 2.6.32.9-perf
04/041/2012 20:41:59 - INFO - Remounting system read-write
04/042/2012 20:42:01 - INFO - Installing toolbox to device...
04/042/2012 20:42:01 - INFO - Pushing C:\Flashtool\custom\root\ftkit.tar to /data/local/tmp
04/042/2012 20:42:04 - ERROR - failed to copy 'C:\Flashtool\custom\root\ftkit.tar' to '/data/local/tmp/ftkit.tar': No space left on device
04/042/2012 20:42:04 - INFO - Root Access Allowed
04/042/2012 20:42:38 - INFO - Log written to C:\Flashtool\flashtool_2012-10-04_08-34-54.log
I didn't know what do next, any suggestions please.
Regards
Jaleel.
jaleelchennai said:
I used a custom rom "Real ICS 5.1" for past two months, suddenly this evening mobile restarted, and stuck with home screen, after i remove and insert the battery, now mobile stucks after sony logo, i restarted many times, but no luck.
just panic now.
connect with flashtool and get the log below.
04/034/2012 20:34:54 - INFO - <- This level is successfully initialized
04/034/2012 20:34:55 - INFO - Flashtool Version 0.6.8.0 built on 2012-02-26 19:26:25
04/034/2012 20:34:55 - INFO - You can drag and drop ftf files here to start flashing them
04/035/2012 20:35:01 - INFO - Device disconnected
04/035/2012 20:35:54 - INFO - Device connected in flash mode
04/037/2012 20:37:27 - INFO - <- This level is successfully initialized
04/037/2012 20:37:37 - INFO - Device disconnected
04/038/2012 20:38:02 - INFO - Device connected in flash mode
04/038/2012 20:38:42 - INFO - Device disconnected
04/039/2012 20:39:19 - INFO - Device connected with USB debugging off
04/039/2012 20:39:19 - INFO - For 2011 devices line, be sure you are not in MTP mode
04/041/2012 20:41:53 - INFO - Device disconnected
04/041/2012 20:41:58 - INFO - Device connected with USB debugging off
04/041/2012 20:41:58 - INFO - For 2011 devices line, be sure you are not in MTP mode
04/041/2012 20:41:58 - INFO - Device connected with USB debugging on
04/041/2012 20:41:59 - INFO - Connected device : WT19
04/041/2012 20:41:59 - INFO - Installed version of busybox : BusyBox v1.19.4-wraithdu (2012-02-16 23:47:29 CST) multi-call binary.
04/041/2012 20:41:59 - INFO - Android version : 4.0.4 / kernel version : 2.6.32.9-perf
04/041/2012 20:41:59 - INFO - Remounting system read-write
04/042/2012 20:42:01 - INFO - Installing toolbox to device...
04/042/2012 20:42:01 - INFO - Pushing C:\Flashtool\custom\root\ftkit.tar to /data/local/tmp
04/042/2012 20:42:04 - ERROR - failed to copy 'C:\Flashtool\custom\root\ftkit.tar' to '/data/local/tmp/ftkit.tar': No space left on device
04/042/2012 20:42:04 - INFO - Root Access Allowed
04/042/2012 20:42:38 - INFO - Log written to C:\Flashtool\flashtool_2012-10-04_08-34-54.log
I didn't know what do next, any suggestions please.
Regards
Jaleel.
Click to expand...
Click to collapse
You must reflash stock rom in flashmode. Just select the stock gingerbread 4.0.2.A.0.42 firmware and flash it. Do you know how to do that?
can i try other custom rom?
mihahn said:
You must reflash stock rom in flashmode. Just select the stock gingerbread 4.0.2.A.0.42 firmware and flash it. Do you know how to do that?
Click to expand...
Click to collapse
can i try other custom rom? like real ics 6?
jaleelchennai said:
can i try other custom rom? like real ics 6?
Click to expand...
Click to collapse
If your bootloader is unlocked, sure. Otherwise, can you enter cwm?
yes i can enter in cwm, i will try another rom, thanks..
jaleelchennai said:
yes i can enter in cwm, i will try another rom, thanks..
Click to expand...
Click to collapse
Is your bootloader locked or unlocked? Because if it's unlocked and you chose the right kernel and rom, maybe you forgot to do a factory reset or wipe cache?
it is unlocked 7 months ago, i tried some gb roms and this ics rom, but now only i had this type of problem, that why i little worried about.
May b just reflash the right kernel (kernel panic works fine with r6) then factory reset,wipe,dalvik cache and format system and flash the rom. I hope that should solve your problem. Otherwise you can always try stock kernel & rom suggested by mihahn
Try Pestanoid v3
Can you try this my ROM Pestanoid v3 ...http://forum.xda-developers.com/showthread.php?t=1905976
Just try another rom+kernel and remeber: You will have to do a factory reset and wipe cache/dalvik cache, but only format system if it's required in rom thread! Otherwise don't format it
Sent from my SK17i running Jelly Bean via CM10
Also turn usb debugging on when using flashtools!!
Thanks for all, now it is solved with another rom and Mesa kernel. But now i am think to re-flash new rom http://forum.xda-developers.com/showthread.php?t=1908269,
will download in this evening.
Stuck after SONY logo
I tried everything bt nothing is helpin me out to solve ths issue.
I flashed my cell again n again to stock ROM. bt, still my XMP is not able to boot or charge. I've repaired my cell through SUS, bt still same problem. what to do ?? I am on stock kernel n Stock ROM (ICS 4.1.B.0.587). My Bootloead is Locked.
Pls Reply ASAP.
First of all dont panic. you have NOT BRICKED ur phone.
Just flash any other kernel and any other ROM. your device should work fine...
Once I had the same problem.
The solution is flash your mobile with another kernel and wipe everything.
Use a custom rom.if nothing happen reunlock ur bootloder with testpoint method.
Sent from my WT19i using Tapatalk 2
mihahn said:
You must reflash stock rom in flashmode. Just select the stock gingerbread 4.0.2.A.0.42 firmware and flash it. Do you know how to do that?
Click to expand...
Click to collapse
hey i jst got the same problem i installed Xperia T Ics Rom 7.1.8 and then i was using it suddenly my device restarted and is stucked on sony logo:crying:
plzz help me on that!!!
CHETANN.5 said:
hey i jst got the same problem i installed Xperia T Ics Rom 7.1.8 and then i was using it suddenly my device restarted and is stucked on sony logo:crying:
plzz help me on that!!!
Click to expand...
Click to collapse
Have you tried reflashing the stock rom? If not search on xda, there should be a tutorial
Sent from my SK17i running stock ics (.587)
mihahn said:
Have you tried reflashing the stock rom? If not search on xda, there should be a tutorial
Sent from my SK17i running stock ics (.587)
Click to expand...
Click to collapse
No coz i dont know how to flash it ..n also i had a locked bootloader
CHETANN.5 said:
No coz i dont know how to flash it ..n also i had a locked bootloader
Click to expand...
Click to collapse
You can even flash on locked bootloader
So you download the stock firmware .ftf (for ics 4.1.B.0.587) for your device. (e.g. mini=st15=smultron, minipro=sk17=mango, active=st17=satsuma, livewithwalkman=wt19=coconut). Then you install flashtool and install all drivers for all devices/modes from flashtool installation folder - drivers
Now you place the downloaded .ftf in flashtool - firmwares and delete all other files in there. Afterwards you launch flashtool
Now click on the flash - flashmode - select the .ftf - click okay - now turn off phone, take out battery, wait 10 seconds, reinsert battery, hold volume down and while holding volume down simply connect phone via usb to your pc, the green led will light up and the flashing process starts. Now wait until it has finished, disconnect phone and boot it. Done :good:
Sent from my SK17i running stock ics (.587)
Thanxxxxx it worked
N also can i now install other roms on it as did before??
Hey,
so.. I want to install a custom rom on my X10 mini pro. I have experience on doing this, because I already rooted many smartphones. But this one is just trolling me.
I used this tutorial (sorry, but it's german). Everything went well till Step 4.7.
I plug in the USB cable, let the flashtool get informations about the device, go to Plugins > Bootloader Unlock and run it.
Then I unplug the cable, start the device in flashmode and theeeen flashtool wants to start unlocking, but the device just shuts down for a moment (green light goes off) and then it reboots into flashmode again.
Here is the output from flashtool
Code:
13/021/2013 17:21:01 - INFO - <- This level is successfully initialized
13/021/2013 17:21:01 - INFO - Flashtool Version 0.9.12.1 built on 2013-06-04 22:50:00
13/021/2013 17:21:06 - INFO - Device disconnected
13/021/2013 17:21:08 - INFO - Device connected with USB debugging on
13/021/2013 17:21:09 - INFO - Connected device : SonyEricson X10 Mini Pro
13/021/2013 17:21:09 - INFO - Installed version of busybox : BusyBox v1.20.2-linusyang (2012-10-15 16:24:24 CST) multi-call binary.
13/021/2013 17:21:09 - INFO - Android version : 2.1-update1 / kernel version : 2.6.29 / Build number : 2.1.1.A.0.6
13/021/2013 17:21:10 - INFO - Checking root access
13/021/2013 17:21:14 - INFO - Root Access Allowed
13/021/2013 17:21:58 - INFO - Device connected in flash mode
13/021/2013 17:21:59 - INFO - Opening device for R/W
13/021/2013 17:21:59 - INFO - Reading device information
13/021/2013 17:21:59 - INFO - Phone ready for flashmode operations.
13/021/2013 17:21:59 - INFO - Current device : U20i - CB511NMQAZ - 1237-8223_R13B - 1235-3411_2.1.1.A.0.6 - WORLD-1-8_2.1.1.A.0.6
13/021/2013 17:21:59 - INFO - Processing loader.sin
13/021/2013 17:21:59 - INFO - Checking header
13/021/2013 17:21:59 - INFO - Flashing data
13/022/2013 17:22:01 - INFO - Loader : S1_Loader_Root_8e35 - Version : R4A045 / Boot version : R8A029 / Bootloader status : UNROOTABLE
13/022/2013 17:22:01 - INFO - Start Reading unit 00000851
13/022/2013 17:22:01 - INFO - Reading TA finished.
13/022/2013 17:22:01 - INFO - Ending flash session
13/022/2013 17:22:01 - INFO - Waiting for device to reboot
13/022/2013 17:22:01 - INFO - Waiting for device
13/022/2013 17:22:02 - INFO - Device connected in flash mode
13/022/2013 17:22:03 - INFO - Device disconnected
Code:
13/022/2013 17:22:01 - INFO - Loader : S1_Loader_Root_8e35 - Version : R4A045 / Boot version : R8A029 / [COLOR="Red"]Bootloader status : UNROOTABLE[/COLOR]
Status : unrootable? So does that mean I don't have any chance to root my device? Is there a way to bypass this?
I'd appreciate every kind of help!
regards,
furi
Well, seems like I got it. I've installed a custom kernel (nAa 2.6) but now the device won't boot anymore
It stucks at the nAa-Bootscreen. What can I do now?
furiify said:
Well, seems like I got it. I've installed a custom kernel (nAa 2.6) but now the device won't boot anymore
It stucks at the nAa-Bootscreen. What can I do now?
Click to expand...
Click to collapse
Install a ROM.
SmG67 said:
Install a ROM.
Click to expand...
Click to collapse
Can you tell me how? My pc doesn't detect the device if it's in the bootscreen. Do I have to go into the flashmode?
If yes, there's one little problem. I can't turn it off And if I pull out the battery and put it back in, then the device automatically starts into that bootscreen. ._______.
aaaaand.. I dont have any recovery installed O__o
furiify said:
Can you tell me how? My pc doesn't detect the device if it's in the bootscreen. Do I have to go into the flashmode?
If yes, there's one little problem. I can't turn it off And if I pull out the battery and put it back in, then the device automatically starts into that bootscreen. ._______.
aaaaand.. I dont have any recovery installed O__o
Click to expand...
Click to collapse
Recovery is in the kernel, use that
Reboot is Home- and Powerbuttons together
If you use the JB-kernel It should boot into Recovery, if that doesn't happen flash the kernel again, that might do the trick. Otherwise you have to press the back-button repeatedly when the phone starts up.
SmG67 said:
Recovery is in the kernel, use that
Reboot is Home- and Powerbuttons together
If you use the JB-kernel It should boot into Recovery, if that doesn't happen flash the kernel again, that might do the trick. Otherwise you have to press the back-button repeatedly when the phone starts up.
Click to expand...
Click to collapse
Thanks alot. It helped. Now I am able to boot into recovery.
BUT! I can't install any rom!? I've tried LiteCM and PureSlim.
All I get is this message :
By the way - I installed this kernel now (U20_nAa-jb-03_2.6.29.6-nAa-jb-03)
I also tried to use the newest kernel (U20_2.6.32.61-nAa-06), but I get the same result
And yes, I did a full wipe and formatted /system /cache and /data.
Now I am a bit helpless It's a JB Kernel and also JB Roms, so why won't they install? :'(
Edit : After trying and trying and trying I got the xperiabean installed.. Thanks again SmG <3
furiify said:
Thanks alot. It helped. Now I am able to boot into recovery.
BUT! I can't install any rom!? I've tried LiteCM and PureSlim.
All I get is this message :
By the way - I installed this kernel now (U20_nAa-jb-03_2.6.29.6-nAa-jb-03)
I also tried to use the newest kernel (U20_2.6.32.61-nAa-06), but I get the same result
And yes, I did a full wipe and formatted /system /cache and /data.
Now I am a bit helpless It's a JB Kernel and also JB Roms, so why won't they install? :'(
Edit : After trying and trying and trying I got the xperiabean installed.. Thanks again SmG <3
Click to expand...
Click to collapse
I think lightCM and PureSlim both look for kernel version 2.6.32.60. The Old JB kernel is 2.6.29.6 and the latest one (the 06) is 2.6.32.61. So you could edit the updater-script to reflect the correct version.
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
Hi. My D6503 device shuted down suddenly and try to open you see writing up SONY down XPERIA on screen and does not go forward. i did this things:
1) i did hard reset. (volume down+power and volume up+power and push the red button until 3 times vibration)
2)i installed pc companion and used.
3) i used flashtool to flash orginal firmware to device but when it is flushing there is writing "reading device information" and does not go forward.
i think that every thing, every details is right that i did about this 3 solution. but it is not fixed.
i am not sure my device usb debuggin is enabled and is unlocked bootloader. i could not learn that because device does not open.
i have no idea how can fix that. i read a lot of things about that but i could not find. can you help me please? thanks
Please post log in flashtool when your plug in your device to pc
Sent from my D2105 using Tapatalk
14/006/2016 16:06:39 - INFO - Flashtool Version 0.9.19.8 built on 24-09-2015 22:00:00
14/006/2016 16:06:39 - INFO - Executing search strategies to find proxy selector
14/006/2016 16:06:40 - INFO - No proxy found for IE. Trying next one
14/006/2016 16:06:40 - INFO - Strategy firefox failed trying next one : No Firefox installation found
14/006/2016 16:06:40 - INFO - No proxy found for java. Trying next one
14/006/2016 16:06:40 - INFO - Syncing devices from github
14/006/2016 16:06:40 - INFO - Scanning devices folder for changes.
14/006/2016 16:06:49 - INFO - Pulling changes from github.
14/006/2016 16:06:49 - INFO - Devices sync finished.
14/006/2016 16:06:54 - INFO - Device disconnected
14/007/2016 16:07:10 - INFO - Selected Bundle for Sony Xperia Z2 (D6503). FW release : 23.4.A.1.232_R5C. Customization : Central Europe 3 Generic_1281-8385
14/007/2016 16:07:10 - INFO - Preparing files for flashing
14/010/2016 16:10:27 - INFO - Please connect your device into flashmode.
14/011/2016 16:11:01 - INFO - Device connected in flash mode
14/011/2016 16:11:02 - INFO - Device connected in flash mode
14/011/2016 16:11:02 - INFO - Opening device for R/W
14/011/2016 16:11:02 - INFO - Reading device information
Did you use original cable from sony ?
Or maybe you have a bad cable ..
Or try to flash preroot frimware via twrp recovery then do factory reset
Sent from my D2105 using Tapatalk
i waited for 1-2 hours after the writing "reading device information" but nothings happen.
i also installed the Emma but when i try to connect Emma (turned of +volume down+usb plug in) i can not connect, nothings happen.
i installed drivers into drivers folder after flashtool was installed and when i attach the device (turn off, volume down) with usb to computer it was defined "SOMC Flash Device" below the device manager.
i used original cable but after your post i tried another cable unfortunately does not work. i searched how can i flash pre rooted firmware , i realized that you have to install twrp. but i can not find how is it install with flashtool. could you help me how can i install twrp with flashtool?
mgurer said:
i used original cable but after your post i tried another cable unfortunately does not work. i searched how can i flash pre rooted firmware , i realized that you have to install twrp. but i can not find how is it install with flashtool. could you help me how can i install twrp with flashtool?
Click to expand...
Click to collapse
Download latest androplus kernel, unpack the boot.img, then just flash the boot.img though flashtool via fastboot mode, to boot to recovery, turn on your device and when the led turn on, pres volume down and that's your twrp ..
Sent from my D2105 using Tapatalk
i downloaded last version Z2_AndroPlusKernel_v57a and flashed but it is failed. (remote: command not allowed) you can see log.
14/038/2016 20:38:14 - INFO - Device disconnected
14/038/2016 20:38:28 - INFO - Device connected in fastboot mode
14/038/2016 20:38:47 - INFO - Now plug your device in Fastboot Mode
14/039/2016 20:39:04 - INFO - Selected kernel (boot.img or kernel.sin): C:\Users\muratgurer\Desktop\boot.img
14/039/2016 20:39:04 - INFO - Flashing selected kernel
14/039/2016 20:39:05 - INFO - sending 'boot' (16342 KB)...
14/039/2016 20:39:05 - INFO - OKAY [ 0.636s]
14/039/2016 20:39:05 - INFO - writing 'boot'...
14/039/2016 20:39:05 - INFO - FAILED (remote: Command not allowed)
14/039/2016 20:39:05 - INFO - finished. total time: 0.638s
14/039/2016 20:39:05 - INFO - FASTBOOT Output:
sending 'boot' (16342 KB)...
OKAY [ 0.636s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.638s
14/039/2016 20:39:05 - INFO - Please check the log before rebooting into system
The lastest androplus kernel is v71, but that's okay .. Maybe that's error caused by your computer have two fastboot binary, one in flashtool, and one in other tool (example in minimal adb fastboot tool), if your machine have more than one fastboot, you can't use the fastboot to flash anything
Sent from my D2105 using Tapatalk
i used another pc today and i just installed only flashtool not another program and i installed drivers into flashtool. i did eveything from the beginning and the same result i have. also flushing kernel. i guess usb debugging is disable so i can not do anything.
i can not lock bootloader because of usb debugging is disable. i can not flash the kernel because of bootloader locked.
if usb debugging is disable how can i recover?