Related
Just wanting to start a count of how many X10's die from this rooting frenzy. Mine survives so 0 so far....
Pointless post!
Would be hard to brick with this root process unless you stupidly close cmd window or pull power/usb out while its doing its thing
I accidentally pulled the usb cable during step one, it gave me that exclamation mark when I tried turning it on, so I started over, and root worked fine, so afaik, its impossible to brick lol
Sent from my X10i using Tapatalk
There's a lot of people here (myself included) who have little to no experience with Android. So this thread might be a good idea to have to serve as a caution to less experienced users on the missteps of others.
Just my two cents...
You can't brick it with this type of root
Sent from my X10i using XDA App
MarylandCookie said:
Pointless post!
Click to expand...
Click to collapse
^^^ What he said
Its almost impossible to brick x10, unless you really want it and know what you are doing
feis said:
Its almost impossible to brick x10, unless you really want it and know what you are doing
Click to expand...
Click to collapse
Now that sounds like a challenge
I've bricked mine at least 4 times doing stupid things and not following instructions. But the flash tool or PC companion fixed it.
Bottom line: FOLLOW THE INSTRUCTIONS and search for an answer if you hit a wall.
PS, I'm not a dev and this is my first android phone
Sent from my SO-01B using XDA App
great news!
se = great hardware maker but crap software dreamer...
gavriel18 said:
I've bricked mine at least 4 times doing stupid things and not following instructions. But the flash tool or PC companion fixed it.
Bottom line: FOLLOW THE INSTRUCTIONS and search for an answer if you hit a wall.
PS, I'm not a dev and this is my first android phone
Sent from my SO-01B using XDA App
Click to expand...
Click to collapse
When you brick it, it becomes a brick. It's not recoverable any more and it's a paper weight. You can't really brick it more than once unless you have 4 x10's.
You can goof it up and it's easily fixed, as you mentioned by following the directions closely
I don't think it possible to brick the X10
bootloader is still there in case something turn wrong
someone to please confirm if what I'm saying is true or false
gavriel18 said:
I've bricked mine at least 4 times doing stupid things and not following instructions. But the flash tool or PC companion fixed it.
Bottom line: FOLLOW THE INSTRUCTIONS and search for an answer if you hit a wall.
PS, I'm not a dev and this is my first android phone
Sent from my SO-01B using XDA App
Click to expand...
Click to collapse
it's not a brick if you can fix it..
I think the only way you could "brick" it is if you rip out the battery while flashing the bootloader. Then you're screwed.
is my unbrickable? wait for solution...
In my case, I couldnt manage to update my X10i to flash OS or anything.
Actually, my Phone was "Bricked" while when I was updated by SEUS, the processing was stucked at about 25%, and it prompt "...lost connection...error occur..." then, i restart phone, only red led blinks every 2-3 sec. I realize it perhaps problem with battery, then i charge the battery overnight, and it was full charged. Now, when i turn it on, it shows green blink and a little vibration... and that is it, no any sign of booting...after try tens of time repairing, reinstalling through the SEUS and PC Comp. None of them worked...
I found your tools and guide on google, then download everything that needed for flash tool, I have latest JRE, PCC, SEUS installed, some stock ROM, Custom ROM.. downloaded. Also i did try to flash ROM of Ver. 1.6, 2.1, 2.2, 2.3. None got through the whole process, it all got stucked right after FLASHING LOADER...here is my log.
14/037/2011 01:37:12 - INFO - <- This level is successfully initialized
14/037/2011 01:37:49 - INFO - Preparing files for flashing
14/038/2011 01:38:34 - INFO - Searching Xperia....
14/038/2011 01:38:34 - INFO - Found at USB\VID_0FCE&PID_ADDE\5&20A947A6&0&5
14/038/2011 01:38:34 - INFO - Start Flashing
14/038/2011 01:38:34 - INFO - VER="R8A013";DATE="20100119";TIME="17:24:00";
14/038/2011 01:38:34 - INFO - Flashing loader
14/039/2011 01:39:40 - INFO -
14/044/2011 01:44:02 - INFO - Flashing kernel.sin
14/045/2011 01:45:17 - ERROR - Error flashing. Aborted
14/045/2011 01:45:17 - INFO - Now unplug the device and power it on
14/045/2011 01:45:17 - INFO - Then go to application settings
14/045/2011 01:45:17 - INFO - turn on Unknown Sources and Debugging
I saw some video on youtube, they only use 4-5min to flash a new OS, but in my case it took my 5mins to flash a loader.sin (<10k.) it must be something wrong with my PC's config or Handset's hardware??? Could you give a hand on this, try to figure out what is causes for my X10i? I was totally pissed off these days. Using backup phone for a week, and lost all the contacts info on my phone...
IMHO, I don't think it is possible to actually brick the phone... Not yet anyways.
I have a feeling that the main boot process is governed by the bootloader itself (no bootloader - no boot) . When that gets cracked/released I think we will start to see actual brick's at that point. Until then I don't think it is possible.
kwonada said:
In my case, I couldnt manage to update my X10i to flash OS or anything.
Actually, my Phone was "Bricked" while when I was updated by SEUS, the processing was stucked at about 25%, and it prompt "...lost connection...error occur..." then, i restart phone, only red led blinks every 2-3 sec. I realize it perhaps problem with battery, then i charge the battery overnight, and it was full charged. Now, when i turn it on, it shows green blink and a little vibration... and that is it, no any sign of booting...after try tens of time repairing, reinstalling through the SEUS and PC Comp. None of them worked...
I found your tools and guide on google, then download everything that needed for flash tool, I have latest JRE, PCC, SEUS installed, some stock ROM, Custom ROM.. downloaded. Also i did try to flash ROM of Ver. 1.6, 2.1, 2.2, 2.3. None got through the whole process, it all got stucked right after FLASHING LOADER...here is my log.
14/037/2011 01:37:12 - INFO - <- This level is successfully initialized
14/037/2011 01:37:49 - INFO - Preparing files for flashing
14/038/2011 01:38:34 - INFO - Searching Xperia....
14/038/2011 01:38:34 - INFO - Found at USB\VID_0FCE&PID_ADDE\5&20A947A6&0&5
14/038/2011 01:38:34 - INFO - Start Flashing
14/038/2011 01:38:34 - INFO - VER="R8A013";DATE="20100119";TIME="17:24:00";
14/038/2011 01:38:34 - INFO - Flashing loader
14/039/2011 01:39:40 - INFO -
14/044/2011 01:44:02 - INFO - Flashing kernel.sin
14/045/2011 01:45:17 - ERROR - Error flashing. Aborted
14/045/2011 01:45:17 - INFO - Now unplug the device and power it on
14/045/2011 01:45:17 - INFO - Then go to application settings
14/045/2011 01:45:17 - INFO - turn on Unknown Sources and Debugging
I saw some video on youtube, they only use 4-5min to flash a new OS, but in my case it took my 5mins to flash a loader.sin (<10k.) it must be something wrong with my PC's config or Handset's hardware??? Could you give a hand on this, try to figure out what is causes for my X10i? I was totally pissed off these days. Using backup phone for a week, and lost all the contacts info on my phone...
Click to expand...
Click to collapse
Interesting... From what I can tell it flashed the bootloader just fine (according to the log it only took just over a minute), but the kernel is failing to upload to the phone.
I'm not sure what would cause that. bad USB cable/connection? If possible try flashing it from a different computer to see if there is a difference.
Carlo_WPG said:
Interesting... From what I can tell it flashed the bootloader just fine (according to the log it only took just over a minute), but the kernel is failing to upload to the phone.
I'm not sure what would cause that. bad USB cable/connection? If possible try flashing it from a different computer to see if there is a difference.
Click to expand...
Click to collapse
Had this issue once, I think it was a power issue, pull the battery, hold the back button with the USB cable already plugged in put the battery back in.
Think that was the only problem.
Well, after my phone has been requiring a flash of stock FW almost daily, it won't even flash from PC COmpanion or Flashtool with stock. 2.3.3, giving me this log in Flashtool v2.9.1:
17/055/2011 09:55:37 - ERROR - Please plug you device in flash mode
17/055/2011 09:55:38 - INFO - Searching Xperia....
17/055/2011 09:55:38 - INFO - Found at USB\VID_0FCE&PID_ADDE\5&E6F0943&0&4
17/055/2011 09:55:38 - INFO - Start Flashing
17/055/2011 09:55:38 - INFO - VER="R8A013";DATE="20100119";TIME="17:24:00";
What does this error usually mean?
Any help? I've been searching the Archives and continue to, but some I'm not having much luck.
background info here:
http://forum.xda-developers.com/showthread.php?t=1301822
thanks
Looks like that error is Flashtool waiting for you to plug in your X10. What happens after it starts flashing?
Edit: Also should be in Q&A section.
Thanks redshirt. I'll repost. I also missed a title. This error happens after I plug the phone in while holding the back button. please respond there.
Please close thread.
Hello,
I am so confused I changed out my xperia play motherboard out due to the lack of touch functionality on two different digitizers. The screen worked fine along with everything except usb data transfer and touch functionality. So I changed the motherboard and confirmed that all ribbons are in locked into place and now no boot logo/ android logo at boot up. The unit vibrates like normal on boot up but no picture on the lcd. The LCD ribbons are plugged in to the motherboard properly. I tired a replacement motherboard and the original with issues and the same situation on both now. Can someone please help. I know this is not a software issue since it was fine prior to switching the motherboards.
devonthedude said:
Hello,
I am so confused I changed out my xperia play motherboard out due to the lack of touch functionality on two different digitizers. The screen worked fine along with everything except usb data transfer and touch functionality. So I changed the motherboard and confirmed that all ribbons are in locked into place and now no boot logo/ android logo at boot up. The unit vibrates like normal on boot up but no picture on the lcd. The LCD ribbons are plugged in to the motherboard properly. I tired a replacement motherboard and the original with issues and the same situation on both now. Can someone please help. I know this is not a software issue since it was fine prior to switching the motherboards.
Click to expand...
Click to collapse
Well if its a new motherboard its most likely a software issue..... Where do you expect the motherboard to get the software from? try flashing a ftf file or something because it sounds like a software issue to me
How can I flash with out access to the android os?
aaron187 said:
Well if its a new motherboard its most likely a software issue..... Where do you expect the motherboard to get the software from? try flashing a ftf file or something because it sounds like a software issue to me
Click to expand...
Click to collapse
The problem is that both motherboards are now doing the same issue, how can I flash if I cant even get my computer to recognize the usb plugged in. The unit charges via usb but wont do data transfer at all. Is there something I'm missing here on the flash that you are referring to. I have flashed both a G1 and a Thunderbolt so I have familiarity doing it but not on a phone that cant access the android os. That Sony software everyone says corrects software issues wont even see my xperia play.
Go to the xplay dev section and one of the pinned threads, flash tool has fast boot and flashing drivers. Dl flash tool and upon install there'll be a drivers-install.exe in the folder you installed it and run it.
Sent from my Xperia Play
cant get into MSc mode to flash
cj360 said:
Go to the xplay dev section and one of the pinned threads, flash tool has fast boot and flashing drivers. Dl flash tool and upon install there'll be a drivers-install.exe in the folder you installed it and run it.
Sent from my Xperia Play
Click to expand...
Click to collapse
The problem is that I CAN NOT get into MSC mode since the unit will not go into the android OS. Is there something I'm missing here, the flash tool wont connect since I can not get into msc mode.
No boot logo help!
aaron187 said:
Well if its a new motherboard its most likely a software issue..... Where do you expect the motherboard to get the software from? try flashing a ftf file or something because it sounds like a software issue to me
Click to expand...
Click to collapse
It is not a new motherboard but one pulled from a working unit. Both motherboards (my original working one and the replacement) are having the same issue now, no boot logo at all just vibrate at startup. How is this a software issue when the android os has not been flashed nor deleted off my original working motherboard (the android os is not saved to sd). Is there something I'm missing, I'm so confused. I cant get into MSC mode since the andriod os does not boot, so I dont see how flashing will help.
how to enable mtp mode
cj360 said:
Go to the xplay dev section and one of the pinned threads, flash tool has fast boot and flashing drivers. Dl flash tool and upon install there'll be a drivers-install.exe in the folder you installed it and run it.
Sent from my Xperia Play
Click to expand...
Click to collapse
Ok the tool does recognize my phone but how do I switch to MTP mode from MSC mode with out going into the android operating system since it wont boot. according to the flashtool program
26/020/2012 21:20:22 - INFO - Device connected with USB debugging off
26/020/2012 21:20:22 - INFO - For 2011 devices line, be sure you are not in MTP mode
I know i sound like a noob on this but I never ran into problems like this with my G1 or thunderbolt.
Try to go into flash mode and flash ftf through Flashtool. You have guides in pinned topics. As far as I remember it was in development section.
Tapped with Xperia Play running AOKP 4.0.4 Milestone 6
flash tool only errors out on my xperia play
olokos said:
Try to go into flash mode and flash ftf through Flashtool. You have guides in pinned topics. As far as I remember it was in development section.
Tapped with Xperia Play running AOKP 4.0.4 Milestone 6
Click to expand...
Click to collapse
Ok, I got there but here is what flashtool says:
26/049/2012 21:49:36 - INFO - Selected X10_V1_BLRelock.ftf
26/049/2012 21:49:36 - INFO - Preparing files for flashing
26/049/2012 21:49:36 - INFO - Please connect your device into flashmode.
26/049/2012 21:49:37 - INFO - Opening device for R/W
26/049/2012 21:49:37 - INFO - Reading device information
26/049/2012 21:49:42 - INFO - Start Flashing
26/049/2012 21:49:42 - INFO - Flashing loader
26/049/2012 21:49:42 - INFO - Ending flash session
26/049/2012 21:49:42 - ERROR -
26/049/2012 21:49:42 - ERROR - Error flashing. Aborted
26/049/2012 21:49:42 - INFO - Device disconnected
Why wont it flash all I get is error messages? as you can see by the log.
Flashed but won't do anything from there
Ok finally l finally flashed the 2.3 rom but the unit says restarting but nothing happens. If i restart the XP still no boot logo like before even though flash tool says its rootable and it has been flashed, here is the log:
26/023/2012 22:23:44 - INFO - Device connected with USB debugging off
26/023/2012 22:23:44 - INFO - For 2011 devices line, be sure you are not in MTP mode
26/024/2012 22:24:07 - INFO - Device disconnected
26/024/2012 22:24:15 - INFO - Selected R800x_FullStocknosimlockta_Verizon.ftf
26/024/2012 22:24:15 - INFO - Preparing files for flashing
26/024/2012 22:24:16 - INFO - Please connect your device into flashmode.
26/024/2012 22:24:40 - INFO - Device connected in flash mode
26/024/2012 22:24:40 - INFO - Opening device for R/W
26/024/2012 22:24:40 - INFO - Reading device information
26/024/2012 22:24:40 - INFO - Phone ready for flashmode operations.
26/024/2012 22:24:41 - INFO - Start Flashing
26/024/2012 22:24:41 - INFO - Flashing loader
26/024/2012 22:24:43 - INFO - Loader : S1_Loader_Root_773f - Version : R4A066 / Bootloader status : ROOTABLE
26/024/2012 22:24:43 - INFO - Flashing kernel.sin
26/024/2012 22:24:46 - INFO - Flashing fota0.sin
26/024/2012 22:24:46 - INFO - Flashing fota1.sin
26/024/2012 22:24:47 - INFO - Flashing adsp.sin
26/024/2012 22:24:50 - INFO - Flashing amss_fs.sin
26/024/2012 22:24:50 - INFO - Flashing amss.sin
26/025/2012 22:25:01 - INFO - Flashing apps_log.sin
26/025/2012 22:25:01 - INFO - Flashing system.sin
26/026/2012 22:26:45 - INFO - Flashing userdata.sin
26/026/2012 22:26:47 - INFO - Flashing cache.sin
26/026/2012 22:26:48 - INFO - Ending flash session
26/026/2012 22:26:48 - INFO - Flashing finished.
26/026/2012 22:26:48 - INFO - Please wait. Phone will reboot
26/026/2012 22:26:48 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
any pointers from here is there something i'm missing from this step to get it at least running android, I cant enable 3rd party apps nor debugging since I cant get into the android os
If I'm right then your phone will work now with no issues just flash kernel for Android 2.3 from the same section using fastboot.
Look after .img file.
Tapped with Xperia Play running AOKP 4.0.4 Milestone 6
Sorry to necrobump this thread, but I am having a similar problem. I recently replaced the LCD Flex Cable, but now the screen won't display anything. It can turn on, but nothing is shown. I can't even connect the USB so I can at try to access Flashboot/Flashmode to reflash another baseband and kernel.
Can anyone please help? Anything is appreciated.
DISCLAIMER: I AM NOT RESPONSIBLE FOR BRICKING YOUR PHONE, or anything for that matter.
Tested 2x R800a. Please let me know if it doesn't work on your device!
THIS WILL WIPE YOUR DEVICE!
So you have a R800 that can't be unlocked officially i.e:
Code:
Bootloader unlock Status: [B]No[/B]
:crying:
What this means is that while we can get the device's bootloader unlocked(TP method), it will not enable fastboot access.
So we lack the ability to flash kernels, in .img formats...but why not just make a FTF packed kernel, which we can flash through flashmode?
I'm actually not sure to tell you the truth(*insert conspiracies*), but that was the solution this whole time...
Note: I have only made FTF versions of Turbo Kernel v3.1 by CosmicDan (R800x/R800a/i/at) I have vouch for the R800a to be working, others will need testing....(just have stock FTF ready to go:fingers-crossed
Requirements
Flashtool
GSM ONLY: Vendor-Unlocked Partition layout
Dev-Host link by fma965
Google Doc's link from [URL="forum.xda-developers.com/showthread.php?t=1817548"]CosmicDan Turbo Kernel [/URL]
Ability to use Flashtool... Read Flashing A FTF by fma965
Paperclip or pin + wire for Testpoint (if BL not unlocked)
S1tool for Testpoint (if BL not unlocked)
STEP 1: BL Unlock Via Test Point method (Locked BL Only)
If your bootloader is currently LOCKED:
Read TP Guide by DragonClawsAreSharp...If you don't feel comfortable doing this...stop reading.
If you are comfortable with unlocking the bootloader then go ahead and do it.
Here is R800 TP location(quick google search): Here, and with red dot...you can use a paperclip and hold it to the (-) battery terminal to achieve the same results as the TP cable the guide shows.
In Flashtool (if you ever noticed):
Code:
S1_Loader_Root_773f - Version : R4A066 / Bootloader status : NOT_ROOTABLE ([I]lies[/I])
will now become:
Code:
S1_Loader_Root_773f,S1_Loader_test_Root_xxxx - Version : r4A069 / Bootloader status : ROOTED ([I]huehue[/I])
STEP 2: Prepare for Kernel
For GSM Only: Flash R800i_4.0.2.A.0.62_phoenixvendor.ftf with Flashtool. Let device fully boot to language selection page.
Read through Turbo Kernel (or what ever kernel.ftf you plan to use)
Grab a rom, look at the compatibility section on the kernel page.
Copy rom over to root directory of phone memory card.
Prepare your body?
STEP 3: Kernel Time + Rom
R800a/at/i Turbo Kernel 3.1 Download
R800x Turbo Kernel 3.1 Download
More Kernels!! Thanks denisfgn
Flash via Flashtool in flashmode.
Unplug usb....press and hold power button until 1 vibration....wait...wait...:victory:
Wait for the blue LED + vibration?, then press Volume Up. You should enter a sexy recovery...
Select: "Slot 1" > "TWRP Recovery" > "Wipe" > Wipe Cache, Dalvik Cache, System, then Factory Reset.
Go back to main page (hit back button), then select "Install", scroll down to the Rom you copied to the device, select and install it.
If you forgot rom: plug phone into computer, then in TWRP Select "Mount"> "Mount USB Storage" copy rom over to phone then install it
Reboot. Done.
This method should work for all Xperia 2011 devices that lack fastboot, but can be/are unlock via testpoint (anyone that can test let me know). Just need kernel to be in packed as a .ftf...
HAS THIS BEEN DONE BEFORE?? Maybe I can't search properly...
References
DragonClawsAreSharp for TP Guide
CosmicDan for Kernel
fma965 for FTF Guide
Flashtool Dev's
wedgess for Kernels
DooMLoRD for Kernel
Yay!! 1st post ever on XDA...
Don't you have to pay to use testpoint?
Sent from my R800i using Tapatalk 2
CloudShepherd said:
Don't you have to pay to use testpoint?
Sent from my R800i using Tapatalk 2
Click to expand...
Click to collapse
NO! This is 100% free. BUT, it will not give you fastboot access(you must pay for that if you really want it), I am just bypassing the fastboot requirement altogether, thus kernel.img(only be flash via fastboot) --> kernel.ftf(can be flashed via flashmode) = win
So...... It works??? I don't know why, but i don't trust in that…………
romeo_charly said:
So...... It works??? I don't know why, but i don't trust in that…………
Click to expand...
Click to collapse
It sure does, at least for my 2 R800a's. I'm not sure how I can prove it to you though...hopefully another user can confirm this as working,
Does your skepticism arise from the amount of time it took to find this method? Or that I lack recognition on here?
Here is a quick snip from Flashtool:
Code:
13/040/2013 17:40:54 - INFO - Start Flashing
13/040/2013 17:40:54 - INFO - Processing loader
13/040/2013 17:40:54 - INFO - Using an unofficial loader
13/040/2013 17:40:54 - INFO - Checking header
13/040/2013 17:40:54 - INFO - Flashing data
13/040/2013 17:40:57 - INFO - Loader : S1_Loader_Root_773f,S1_Loader_test_Root_xxxx - Version : r4A069 / Bootloader status : ROOTED
13/040/2013 17:40:57 - WARN - This file is ignored : simlock.ta
13/040/2013 17:40:57 - INFO - Processing kernel.sin
13/040/2013 17:40:57 - INFO - Checking header
13/040/2013 17:40:57 - INFO - Flashing data
I believe that it checks/reports bootloader status, and will use the unofficial loader when flashing to the phone.
Generally if the bootloader is locked it will still try this method and fail with some SEC ERR when it comes to flashing the kernel since the phone checks, making sure the certificate is present and valid(signed?) within kernel.sin (Not 100% on this, I was messing with a locked LT28i and trying to get kernel.sin made with a cert...no luck obviously)
With unlocked BL this check is not done, and the kernel is accepted.
I will post some picks of the service menu if that provides additional proof.(2.3.3 has no "Rooting Status" part, gonna try flash official ICS beta)
LoOpy! said:
It sure does, at least for my 2 R800a's. I'm not sure how I can prove it to you though...hopefully another user can confirm this as working,
Does your skepticism arise from the amount of time it took to find this method? Or that I lack recognition on here?
Here is a quick snip from Flashtool:
Code:
13/040/2013 17:40:54 - INFO - Start Flashing
13/040/2013 17:40:54 - INFO - Processing loader
13/040/2013 17:40:54 - INFO - Using an unofficial loader
13/040/2013 17:40:54 - INFO - Checking header
13/040/2013 17:40:54 - INFO - Flashing data
13/040/2013 17:40:57 - INFO - Loader : S1_Loader_Root_773f,S1_Loader_test_Root_xxxx - Version : r4A069 / Bootloader status : ROOTED
13/040/2013 17:40:57 - WARN - This file is ignored : simlock.ta
13/040/2013 17:40:57 - INFO - Processing kernel.sin
13/040/2013 17:40:57 - INFO - Checking header
13/040/2013 17:40:57 - INFO - Flashing data
I believe that it checks/reports bootloader status, and will use the unofficial loader when flashing to the phone.
Generally if the bootloader is locked it will still try this method and fail with some SEC ERR when it comes to flashing the kernel since the phone checks, making sure the certificate is present and valid(signed?) within kernel.sin (Not 100% on this, I was messing with a locked LT28i and trying to get kernel.sin made with a cert...no luck obviously)
With unlocked BL this check is not done, and the kernel is accepted.
I will post some picks of the service menu if that provides additional proof.(2.3.3 has no "Rooting Status" part, gonna try flash official ICS beta)
Click to expand...
Click to collapse
Right now stop lying and take R800i out of the list.
I have a R800i and I have a unlocked bootloader.
Due to some driver problems of my pc both the flash mode and Fastboot mode are recognized as flash mode(Need Help to solve that if anyone can please help me) now back to the topic but all flash operations work properly. so I was held away from flashing Turbo Kernel for 3 Months. Once I saw this I believed the developer and flashed the phoenix vendor firmware and stuck at 2.3.3. when I flashed this (on the latest flashtool) it showed an error: invalid handle. now I have to leave to my work with a wiped phone running ancient Gingerbread on it . too bad don't post without testing.
Followed all your instructions and it worked perfectly!
Dont know if it was the Paranoid Android Rom or what, but once installed device wouldn't boot past the Paranoid Android logo. After a hard reset it booted up almost instantly. So everything turned out fine!
I used an Xperia Play R800i, unlocked to every network, but the boot loader is locked.
Superb guide, really helped out
Romaan said:
Followed all your instructions and it worked perfectly!
Dont know if it was the Paranoid Android Rom or what, but once installed device wouldn't boot past the Paranoid Android logo. After a hard reset it booted up almost instantly. So everything turned out fine!
I used an Xperia Play R800i, unlocked to every network, but the boot loader is locked.
Superb guide, really helped out
Click to expand...
Click to collapse
Did you say an xperia play R800i with a locked bootloader???
I have one with unlocked bootloader and tried around 20 times and it was continuously giving me errors. did you use the R800a/at/I rtf????or the R800x ftf
Gladwin_Prince said:
Did you say an xperia play R800i with a locked bootloader???
I have one with unlocked bootloader and tried around 20 times and it was continuously giving me errors. did you use the R800a/at/I rtf????or the R800x ftf
Click to expand...
Click to collapse
Yep locked bootloader. I used the R800/a/at/i ftf
how you did that? how you did ftf version of custom kernel? and if you can upload here to xda how to? and if you can make ftf version of lupus GB+ICS kernel?
fail at flashing. i have r800a, and i just locked the bootloader to try this
17/009/2013 15:09:01 - INFO - <- This level is successfully initialized
17/009/2013 15:09:01 - INFO - Flashtool Version 0.9.9.0 built on 2012-11-13 22:53:30
17/009/2013 15:09:01 - INFO - You can drag and drop ftf files here to start flashing them
17/009/2013 15:09:02 - INFO - Device disconnected
17/009/2013 15:09:11 - INFO - Selected R800aTURBOv3.1.ftf
17/009/2013 15:09:11 - INFO - Preparing files for flashing
17/009/2013 15:09:13 - INFO - Please connect your device into flashmode.
17/009/2013 15:09:20 - INFO - Device connected in flash mode
17/009/2013 15:09:20 - INFO - Opening device for R/W
17/009/2013 15:09:20 - INFO - Reading device information
17/009/2013 15:09:20 - INFO - Phone ready for flashmode operations.
17/009/2013 15:09:20 - INFO - Start Flashing
17/009/2013 15:09:20 - INFO - Processing loader
17/009/2013 15:09:20 - INFO - Checking header
17/009/2013 15:09:20 - INFO - Flashing data
17/009/2013 15:09:23 - INFO - Loader : S1_Loader_Root_773f - Version : R4A066 / Bootloader status : ROOTED
17/009/2013 15:09:23 - INFO - Processing kernel.sin
17/009/2013 15:09:23 - INFO - Checking header
17/009/2013 15:09:23 - INFO - Ending flash session
17/009/2013 15:09:23 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_STATIC="SIN_HEAD_VER";ERR_DYNAMIC="Failed to verify sin header";
17/009/2013 15:09:23 - ERROR - Error flashing. Aborted
17/009/2013 15:09:23 - INFO - Device connected in flash mode
17/009/2013 15:09:25 - INFO - Device disconnected
17/009/2013 15:09:26 - INFO - Device connected in flash mode
17/009/2013 15:09:26 - INFO - Device disconnected
17/009/2013 15:09:34 - INFO - Selected R800aTURBOv3.1.ftf
17/009/2013 15:09:34 - INFO - Preparing files for flashing
17/009/2013 15:09:34 - INFO - Please connect your device into flashmode.
17/009/2013 15:09:38 - INFO - Device connected in flash mode
17/009/2013 15:09:38 - INFO - Opening device for R/W
17/009/2013 15:09:38 - INFO - Reading device information
17/009/2013 15:09:38 - INFO - Phone ready for flashmode operations.
17/009/2013 15:09:38 - INFO - Start Flashing
17/009/2013 15:09:38 - INFO - Processing loader
17/009/2013 15:09:38 - INFO - Checking header
17/009/2013 15:09:38 - INFO - Flashing data
17/009/2013 15:09:41 - INFO - Loader : S1_Loader_Root_773f - Version : R4A066 / Bootloader status : ROOTED
ravid1323 said:
how you did that? how you did ftf version of custom kernel? and if you can upload here to xda how to? and if you can make ftf version of lupus GB+ICS kernel?
fail at flashing. i have r800a, and i just locked the bootloader to try this
17/009/2013 15:09:01 - INFO - <- This level is successfully initialized
17/009/2013 15:09:01 - INFO - Flashtool Version 0.9.9.0 built on 2012-11-13 22:53:30
...
17/009/2013 15:09:20 - INFO - Processing loader
17/009/2013 15:09:20 - INFO - Checking header
17/009/2013 15:09:20 - INFO - Flashing data
17/009/2013 15:09:23 - INFO - Loader : S1_Loader_Root_773f - Version : R4A066 / Bootloader status : ROOTED
17/009/2013 15:09:23 - INFO - Processing kernel.sin
17/009/2013 15:09:23 - INFO - Checking header
17/009/2013 15:09:23 - INFO - Ending flash session
17/009/2013 15:09:23 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_STATIC="SIN_HEAD_VER";ERR_DYNAMIC="Failed to verify sin header";
17/009/2013 15:09:23 - ERROR - Error flashing. Aborted
17/009/2013 15:09:23 - INFO - Device connected in flash mode
....
Click to expand...
Click to collapse
Relocking the bootloader. Thats what is likely causing your issue...(thanks for providing the log, it kinda reinforces my original thinking regarding the bootloader, although it looks like I was slightly mistaken in stating that;"Generally if the bootloader is locked it will still try this method and fail with some SEC ERR...". (Looks like the official loader is used upon locked BL detection.)
I will look at converting more kernels over to FTF if this method works out for the majority of the people, and throwing together a guide for those that want to know how to do it themselves.
Romaan said:
Yep locked bootloader. I used the R800/a/at/i ftf
Click to expand...
Click to collapse
Ehh...I don't believe you...but glad it worked for you. I'm curious to see your Flashtool log when you flashed the kernel. Would you kindly reflash and share/post it?
Gladwin_Prince said:
Right now stop lying and take R800i out of the list.
I have a R800i and I have a unlocked bootloader.
Due to some driver problems of my pc both the flash mode and Fastboot mode are recognized as flash mode(Need Help to solve that if anyone can please help me) now back to the topic but all flash operations work properly.
...
Click to expand...
Click to collapse
I'm sure you also read the following:
LoOpy! said:
DISCLAIMER: I AM NOT RESPONSIBLE FOR BRICKING YOUR PHONE, or anything for that matter.
Tested 2x R800a. Please let me know if it doesn't work on your device!
THIS WILL WIPE YOUR DEVICE!
....
(R800x/R800a/i/at) I have vouch for the R800a to be working, others will need testing....(just have stock FTF ready to go:fingers-crossed
...
Click to expand...
Click to collapse
Your messed up drivers disconcerting. Try reinstalling the driver package in the Flashtool folder, then reboot and see if fastboot is detected.
The fact that you claim "all flash operations work properly." means? All kernels flashed while in fastboot work? Even though fastboot is detected as flashmode(by Flashtool?)? Do all flashes in flashmode work?
Can you provide more details, logs/screenshots/info regarding this 'invalid handle' error?
Did you flash the FTF while in fastboot mode?
I do apologize for your lack of ability to read the RED text on the 1st post and the rest of it as well.
"Right now stop lying and take R800i out of the list."
Nah.
LoOpy! said:
Relocking the bootloader. Thats what is likely causing your issue...(thanks for providing the log, it kinda reinforces my original thinking regarding the bootloader, although it looks like I was slightly mistaken in stating that;"Generally if the bootloader is locked it will still try this method and fail with some SEC ERR...". (Looks like the official loader is used upon locked BL detection.)
I will look at converting more kernels over to FTF if this method works out for the majority of the people, and throwing together a guide for those that want to know how to do it themselves.
Ehh...I don't believe you...but glad it worked for you. I'm curious to see your Flashtool log when you flashed the kernel. Would you kindly reflash and share/post it?
I'm sure you also read the following:
Your messed up drivers disconcerting. Try reinstalling the driver package in the Flashtool folder, then reboot and see if fastboot is detected.
The fact that you claim "all flash operations work properly." means? All kernels flashed while in fastboot work? Even though fastboot is detected as flashmode(by Flashtool?)? Do all flashes in flashmode work?
Can you provide more details, logs/screenshots/info regarding this 'invalid handle' error?
Did you flash the FTF while in fastboot mode?
I do apologize for your lack of ability to read the RED text on the 1st post and the rest of it as well.
"Right now stop lying and take R800i out of the list."
Nah.
Click to expand...
Click to collapse
sorry lo0py,
I just got angry and words flowed out. I know the hard work behind this. what I actually mentioned was my pc detects it as flash mode and all flash mode operations alone work. I was trying to flash it about 3-4 times then flashtool threw the "invalid handle" error. I am currently away from my Pc and once I am free I will try to repeat the error and get you the logcat. hope that would help you.
SORRY BUDDY IF I HAD HURT YOU. I AM REALLY SORRY
Sorry I meant that bootloader unlock status was 'no' then after test point changed to rooted.
18/050/2013 17:50:48 - INFO - Loader : S1_Loader_Root_773f,S1_Loader_test_Root_xxxx - Version : r4A069 / Bootloader status : ROOTED
18/050/2013 17:50:48 - INFO - Processing kernel.sin
18/050/2013 17:50:48 - INFO - Checking header
18/050/2013 17:50:48 - INFO - Flashing data
18/050/2013 17:50:52 - INFO - Ending flash session
18/050/2013 17:50:52 - INFO - Flashing finished.
18/050/2013 17:50:52 - INFO - Please unplug and start your phone
18/050/2013 17:50:52 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
18/050/2013 17:50:52 - INFO - Device connected in flash mode
18/050/2013 17:50:58 - INFO - Device disconnected
Gladwin_Prince said:
sorry lo0py,
I just got angry and words flowed out. I know the hard work behind this. what I actually mentioned was my pc detects it as flash mode and all flash mode operations alone work. I was trying to flash it about 3-4 times then flashtool threw the "invalid handle" error. I am currently away from my Pc and once I am free I will try to repeat the error and get you the logcat. hope that would help you.
SORRY BUDDY IF I HAD HURT YOU. I AM REALLY SORRY
Click to expand...
Click to collapse
It's all good, I can see where your frustration comes from, but try to refrain from the impulsive posts when it happens. You just end up making making everyone trying to help frustrated too.
Logs/Logcat would be great! Thanks bud.
Romaan said:
Sorry I meant that bootloader unlock status was 'no' then after test point changed to rooted.
18/050/2013 17:50:48 - INFO - Loader : S1_Loader_Root_773f,S1_Loader_test_Root_xxxx - Version : r4A069 / Bootloader status : ROOTED
18/050/2013 17:50:48 - INFO - Processing kernel.sin
18/050/2013 17:50:48 - INFO - Checking header
18/050/2013 17:50:48 - INFO - Flashing data
18/050/2013 17:50:52 - INFO - Ending flash session
18/050/2013 17:50:52 - INFO - Flashing finished.
18/050/2013 17:50:52 - INFO - Please unplug and start your phone
18/050/2013 17:50:52 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
18/050/2013 17:50:52 - INFO - Device connected in flash mode
18/050/2013 17:50:58 - INFO - Device disconnected
Click to expand...
Click to collapse
Ahh awsome! I was kinda confused from how you got the kernel on with a locked bootloader. Thanks for clarifying. :good:
So if bootloader unlock says no I can use this to unlock it still or does it have to say bootloader unlock allowed yes?
Sent from my LT28i using xda app-developers app
This works question is how do I ftf a kernel? Not likening multipoint slow
Sent from my LT28i using xda app-developers app
thanks
it worked for my bros phone but can you convert Lupusv6GB To FTF Or Give Instructions
Can i flash Turbo Kernel.ftf directly with flashtool or i need to follow all the steps?
I think if kernel are in .ftf then just use flashtool, unlocking the bootloader becomes useless.... Or am i in TERRIBLE mistake????
I need to flash .62 phoenixvendor, follow instructions with test points then flash kernel.FTF (no .img) or: flash .62 PV then flash kernel.FTF via flshtool...
Why? Some months ago i flashed a kernel.ftf from neo v (ICS) directly from flashtool.
Sorry, i'm a bit confused...
romeo_charly said:
Can i flash Turbo Kernel.ftf directly with flashtool or i need to follow all the steps?
I think if kernel are in .ftf then just use flashtool, unlocking the bootloader becomes useless.... Or am i in TERRIBLE mistake????
I need to flash .62 phoenixvendor, follow instructions with test points then flash kernel.FTF (no .img) or: flash .62 PV then flash kernel.FTF via flshtool...
Why? Some months ago i flashed a kernel.ftf from neo v (ICS) directly from flashtool.
Sorry, i'm a bit confused...
Click to expand...
Click to collapse
I would just follow the guide myself
Sent from my Sony Tablet S using xda app-developers app
How the hell do you make an ftf sin. From kernel
Sent from my R800i using xda app-developers app
Hey there,
after flashing a created boot.img I think my phone is bricked
Cannot start it anymore / no bootloader / no hardreset.
Evertime I connect it to my PC first the red LED flashes and get stuck at a green LED.
Flashtool shows "no Device" and no adb connection is working.
What did I wrong?
Is my phone bricked?
Kind regards,
Chris
dhchris said:
Hey there,
after flashing a created boot.img I think my phone is bricked
Cannot start it anymore / no bootloader / no hardreset.
Evertime I connect it to my PC first the red LED flashes and get stuck at a green LED.
Flashtool shows "no Device" and no adb connection is working.
What did I wrong?
Is my phone bricked?
Kind regards,
Chris
Click to expand...
Click to collapse
I don't think flashing boot img would hard brick. Have you tried connecting while pressing volume up and volume down? I have had situations with my old Xa where a bad flash zapped the battery to zero, and I wouldn't get any response plugging in the charger, etc, but I would try it with different cables and try holdings buttons while plugging, and it suddenly resurrected and started charging, (happened twice when Xposed N unofficial was first released)...
levone1 said:
I don't think flashing boot img would hard brick. Have you tried connecting while pressing volume up and volume down? I have had situations with my old Xa where a bad flash zapped the battery to zero, and I wouldn't get any response plugging in the charger, etc, but I would try it with different cables and try holdings buttons while plugging, and it suddenly resurrected and started charging, (happened twice when Xposed N unofficial was first released)...
Click to expand...
Click to collapse
hmm, I tried to connect in many ways, but nothing happens.
If I connect it to my charger, the red light flickers (red light to red dark to red light...)
or
it flickers from off to red to off to red...
Charging in this state over night takes no effect.
Under Flashtool the green light is on (device connected in falsh mode) and trying to flash a xperifirm-ftf:
28/041/2018 07:41:54 - INFO - Device connected in flash mode
28/042/2018 07:42:15 - INFO - Selected Bundle for Sony Xperia X Compact(F5321). FW release : 34.4.A.2.19. Customization : Customized DE
28/042/2018 07:42:15 - INFO - Preparing files for flashing
28/042/2018 07:42:48 - INFO - Please connect your device into flashmode.
28/042/2018 07:42:49 - INFO - Using Gordon gate drivers version 3.2.0.0
28/042/2018 07:42:49 - INFO - Opening device for R/W
28/042/2018 07:42:49 - INFO - Device ready for R/W.
28/042/2018 07:42:49 - INFO - Reading device information
28/042/2018 07:42:51 - INFO - Phone ready for flashmode operations.
28/042/2018 07:42:51 - INFO - Opening TA partition 2
28/043/2018 07:43:09 - INFO - Current device : D5803 - YT910ZASZ3 - 1289-4696_R5D - 1285-6521_23.5.A.1.291 - GLOBAL-LTE_23.5.A.1.291
28/043/2018 07:43:09 - INFO - Closing TA partition
28/043/2018 07:43:11 - ERROR - The bundle does not match the connected device
28/043/2018 07:43:11 - INFO - Ending flash session
28/043/2018 07:43:16 - INFO - Device connected in flash mode
28/043/2018 07:43:16 - INFO - Device disconnected
28/043/2018 07:43:21 - INFO - Device connected in flash mode
Click to expand...
Click to collapse
Sounds not so good :crying:
dhchris said:
hmm, I tried to connect in many ways, but nothing happens.
If I connect it to my charger, the red light flickers (red light to red dark to red light...)
or
it flickers from off to red to off to red...
Charging in this state over night takes no effect.
Under Flashtool the green light is on (device connected in falsh mode) and trying to flash a xperifirm-ftf:
Sounds not so good :crying:
Click to expand...
Click to collapse
Hey Guys,
now I found the mistake i´ve done.
I swapped the file.
Taken the wrong TA.img from my other phone.
Is there a way to get the phone back to life?
dhchris said:
Hey Guys,
now I found the mistake i´ve done.
I swapped the file.
Taken the wrong TA.img from my other phone.
Is there a way to get the phone back to life?
Click to expand...
Click to collapse
Did you try checking 'wipe' boxes in Flashtool? How did you flash the ta?
levone1 said:
Did you try checking 'wipe' boxes in Flashtool? How did you flash the ta?
Click to expand...
Click to collapse
Yes, tried this.
Flashed the TA manually by adb
dhchris said:
Yes, tried this.
Flashed the TA manually by adb
Click to expand...
Click to collapse
What, with dd command? Did you try to do it again with correct ta, or use adb to wipe?
Flashier wrong ta could be a big deal... I know with Z phones it was for sure a hard brick, but maybe there's hope.
Do you get the same error with Emma / Sony Companion?
Yes, dd-command.
I´m searching for my right Xc - TA.img file, but I cannot find it anymore.
adb-wipe didnt tried.
In worst case, I overwritten it by the old Z3 phones TA.
EMMA told me that the device could not be identified.
I think, that there´s no other way to get a new phone ;-(