So, rather than just being a "HOW I ROOT?" thread, I'm going to use this to post everything I manage to glean whilst attempting to get a custom kernel to boot. So, here goes:
Fastboot mode
Used to flash images and hot boot. Accessed by holding the volume-up rocker and plugging in the USB cable. The device must be fully powered off before entering this mode.
Flash mode
Used to flash official updates and use by Flashtool to flash "ftf" files. Accessed by holding the volume-down rocker and plugging in the USB cable. The device must be fully powered off before entering this mode.
Hard shutdown
Used when you just need to get the device turned off quickly or if you flash a bad image that causes the device to hang. Activated by holding the volume-up rocker and power switch for three seconds.
Kernel cmdline
The cmdline for the stock kernel appears to be "androidboot.hardware=qcom user_debug=31 maxcpus=2 msm_rtb.filter=0x3F ehci-hcd.park=3 lpj=192598 dwc3.maximum_speed=high dwc3_msm.prop_chg_detect=Y". I extracted this from the stock kernel.sin found in the HK 471 ROM via the use of a hex editor.
Kernel.sin
1) The kernel zImage.
2) The initrd (ram disk), which is a standard gzipped cpio.
3) A mysterious third file, which simply extracts with a ".3" extension, presumably because the unpacker doesn't know what to make of it. Perhaps this is the DTB (see below in the "Hot booting" section).
Hot booting
Attempting to hot boot a kernel results in the following:
Code:
downloading 'boot.img'...
OKAY [ 0.284s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.332s
A little investigation shows that a "dtb" probably refers to a "device tree blob," which is used to tell the kernel about the hardware within the device (since every ARM device has different addresses for the various hardware components). Perhaps the use of a dtb is new for the Xperia Z Ultra?
Making boot images
Making boot.img files and flashing them has so far yielded nothing more than a black screen when trying to boot; the device outwardly appears to be bricked, however, it is not. The only way out of this state is to hold the power button and volume-up rocker for about 3 seconds. After this, the vibration motor pulses three times and you're free to enter fastboot or flash modes again.
This failure isn't too surprising given that the hot boot attempt indicates that a dtb was not found. It is my assumption that we somehow need to put the dtb in the boot image.
Root exploits
The device seems to be patched for all known root exploits as of the time of writing this post. I've adapted DooMLoRD's root kit to attempt the relevant exploits to no avail. I've also checked the kernel source and found that at least the perf_event exploit has been patched.
Building a kernel.sin file and then making it into an "ftf" results in the loader.sin flashing fine, but the "Check header" stage of the kernel.sin fails. I'm not sure if this is because the loader.sin is making sure the kernel.sin is correctly signed or if it's because the header is actually incorrect.
There's not much information for me to go on at the moment.
So, it looks like the SIN may not work because the only "bin2sin" files I can find create SINv1 files, but the stock files are SINv3. The header appears to be different.
I stumbled upon some PDFs (http://forum.xda-developers.com/showthread.php?p=30243940) that explains the SIN file format, but it's very brief. Even this appeared only to be for SINv2.
Does anyone know if SINv3 is new for the Xperia Z Ultra? Does anyone have a tool to create these, or at least the file format specs?
All over my head im afraid mate, but good luck with your endeavors
Related
Words of wisdom ... or warning!
By following this guide, you are agreeing that neither I nor anyone else apart from yourself is responsible for any damage, loss of earnings, fire, theft, the milk not being delivered or bricking your device - you are doing the modding so you are to blame if anything goes wrong!
I will credit the original authors of all the files I have included in my guide as best as I can, if I have missed you out then I do apologise.
With thanks to: kennethpenn, SamCripp, Stevendeb25, eval-, Edgan, Mossys, papy-polo, the2dcour, plus anyone that I have missed.
Note: I have linked file downloads from the guides I used when I rooted, unlocked and flashed my device. I will included a link to the thread so if the links are broken then you should look in the threads for updated links - also just let me know and I'll try to fix them.
Right on with the guide...
Rooting:
Downloads:
- Atrix drivers - Download: 32-bit | 64-bit
- Gingerbreak - Download
Instructions:
1. Install drivers
2. Run gingerbreak.exe
3. Give the phone a minute or two and then open the app drawer to find "Gingerbreak"
4. Run gingerbreak from your phone
5. Click 'root now'
6. Wait for your phone to reboot
Whayy! Your now rooted - If all went well.
Tegrapart?.. You need this to flash the correct boot.img later on.
Downloads:
Terminal emulator - Download from market
Instructions:
1. Download and run 'Terminal emulator'
2. Enter:
Code:
su
- you may be prompted to by SuperUser, press remember and then press 'Allow'
3. Now enter:
Code:
cat /proc/cmdline
4.a. That command will return quite a large string of text, scan through it untill you find something that starts something like this: 'tegrapart=mbr:'
4.b. If you see tegrapart=mbr:d00:100:800,kpanic:2100:400:800: then just remember that your device is d00
4.c. If you see tegrapart=mbr:1100:100:800,kpanic:2500:400:800: then you need to remember that your device is 1100
Unlocking the bootloader:
Downloads:
- RSD Lite 5.3.1 - Download - Thread
- Drivers - Download - Thread
- Fastboot - Download - Thread
- IHOP_Bell pudding - Download - Thread
Instructions:
a. Extract the file from IHOP_Bell into a location your will remember
b. Extract the files from Fastboot package to a location you will remember - I will use C:\fastboot\ in my example
1. Turn off you phone
2. For safety measures, take out your SIM card and microSD card
3. Boot into RSD Mode by holding volume up and the power button at the same time until "Starting RSD protocol support" is displayed on the screen
4. Run RSD Lite on your pc
5. Press the [...] box next to the box named 'Filename'
6. Locate the file from IHOP_Bell that you extracted earlier
7. Load the file
8. Plug your phone into your pc
9. RSD Lite should recognise your device and should say something like "Model: NS Flash Olympus" mine said "SE Flash Olympus" and it should also say "Connected..."
10. Press the 'Start' Button
11. Be paitient while the phone reboots as it may take a loooong time
12. Once the phone has rebooted, open a command prompt window
13. Type in CD followed by a space and then the directory where you extracted the fastboot package - I will use C:\Fastboot\ in my example so I would type
Code:
CD C:\Fastboot\
14. Turn off your phone
15. Unplug your phone from the usb port
16. Hold the volume down button and the power button until you see 'Fastboot' on the screen
17. Press volume up to select fastboot, you will see "Starting Fastboot protocol support" on screen
18. Plug your phone into the usb port
19. Then in the command prompt window, type in the following command:
Code:
fastboot oem unlock
20. You will see a warning along with a unique device ID
21. Type in the following commands but use your unique device ID in place of the '#####'
Code:
fastboot oem unlock #####
fastboot -w
fastboot reboot
22. Now wait for your device to boot, whilst booting you should see 'Unlocked' on the boot screenFlashing 2.3.4 (Orange FR):
Downloads:
Moto-fastboot - Download - Thread
OrangeFR system - Download - Thread
OrangeFR webtop - Download - Thread
(Remember your Tegrapart you found out earlier.. download the right one for your device)
d00 - Download - Thread
1100 - Download - Thread
Instructions:
a. Unzip the moto-fastboot package into a directory you will remember, again I will place mine in a directory named motofastboot in my C: drive.
b. Extract the system, webtop and the correct tegrapart boot.img and place them inside your motofastboot directory
1. Turn off your phone and unplug it from the usb port if it is connected
2. Boot into fastboot mode by holding volume down and the power button untill you see 'Fastboot' on screen.
3. When you see fastboot, press volume up.
4. Open a command prompt and CD to the directory you placed your moto-fastboot package, I would enter:
Code:
CD C:\motofastboot
5. Now enter:
Code:
moto-fastboot flash system ORFR234-system.img
6. Once complete, enter:
Code:
moto-fastboot flash webtop webtop.img
7. And finally enter either:
Code:
moto-fastboot flash boot ORFR234-tegrapart-d00100.boot.img
OR
Code:
moto-fastboot flash boot ORFR234-tegrapart-1100100.boot.img
Depending on your Tegrapart number.
8. Turn off your phone, boot it back up and you should now be rocking Orange 2.3.4 GingerBread.
briliant guide mate! could you add some kernels and roms thats working with UK's atrix
Cheers
Thanks, this is exactly what I needed in terms of clear, complete information all in one thread.
Sorry if this is a stupid question but I'm new to the Atrix and there's so much info all over the place my head is already spinning! I'm on UK T-mobile, I assume the unlocking and rooting part is still the same, but should I still flash the Orange file or would this mess up my phone? All I really want to do is root/unlock so I can flash a custom rom.
Many thanks.
eggshaped said:
Thanks, this is exactly what I needed in terms of clear, complete information all in one thread.
Sorry if this is a stupid question but I'm new to the Atrix and there's so much info all over the place my head is already spinning! I'm on UK T-mobile, I assume the unlocking and rooting part is still the same, but should I still flash the Orange file or would this mess up my phone? All I really want to do is root/unlock so I can flash a custom rom.
Many thanks.
Click to expand...
Click to collapse
No, it won't. In fact, even Orange FR and Orange UK are as different as AT&T and T-Mobile UK. Also, ALL AT&T ROMS WORK! All you need to do is to flash faux123's kernel over the top of the ROM, just to get back your RAM. Even if you don't flash the kernel, you will not brick, just have the limited RAM issue.
Finally, most of us should be on the N_01.95.00R radio. What speeds and battery life do you get out of this on Orange UK?
It seems I have been capped to 1.9mbps
kartik50 said:
No, it won't. In fact, even Orange FR and Orange UK are as different as AT&T and T-Mobile UK. Also, ALL AT&T ROMS WORK! All you need to do is to flash faux123's kernel over the top of the ROM, just to get back your RAM. Even if you don't flash the kernel, you will not brick, just have the limited RAM issue.
Finally, most of us should be on the N_01.95.00R radio. What speeds and battery life do you get out of this on Orange UK?
It seems I have been capped to 1.9mbps
Click to expand...
Click to collapse
Thanks for replying...I think I understand what you're saying.
However, I'm on T-mobile UK not Orange. I only ever use wifi for data so not sure about speed, but battery life seems to be just over a day although I've only had the phone a few days so far. Just trying to make sense of it all .
I wish there was one definitive thread on what you need to do to get the phone to a point where you can flash a custom rom. Don't get me wrong, I'm not lazy and don't mind reading up and researching, I'm just really confused at the moment about whether I need to follow the pudding thread and flash sbf files (it says to put Pudding on the phone, whatever that is) or use Gingerbreak or SuperOneClick, and how to get cwm recovery on the phone.
....more reading up is in order I guess, until it all sinks in
Anyone know why it's stuck on the boot screen with this? I even SBF'd back to stock Orange 2.2.2 before hand. I also fastboot -w it. Is there nothing you can just flash for this?
this is what i get when trying to flash???
C:\Users\kris\Desktop\motorola>fastboot flash system ORFR234-system.img
sending 'system' (327680 KB)...
(bootloader) Image is too big, use 0x10000000 bytes chunks
FAILED (remote: (00000006))
finished. total time: 0.003s
C:\Users\kris\Desktop\motorola>moto-fastboot flash system ORFR234-system.img
'moto-fastboot' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\kris\Desktop\motorola>moto -fastboot flash system ORFR234-system.img
'moto' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\kris\Desktop\motorola>fastboot flash system ORFR234-system.img
sending 'system' (327680 KB)...
(bootloader) Image is too big, use 0x10000000 bytes chunks
FAILED (remote: (00000006))
finished. total time: 0.002s
C:\Users\kris\Desktop\motorola>moto-fastboot
'moto-fastboot' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\kris\Desktop\motorola>fastboot flash system ORFR234-system.img
sending 'system' (327680 KB)...
(bootloader) Image is too big, use 0x10000000 bytes chunks
FAILED (remote: (00000006))
finished. total time: 0.002s
C:\Users\kris\Desktop\motorola>moto-fastboot
'moto-fastboot' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\kris\Desktop\motorola>fastboot flash system ORFR234-system.img
sending 'system' (327680 KB)...
(bootloader) Image is too big, use 0x10000000 bytes chunks
FAILED (remote: (00000006))
finished. total time: 0.002s
C:\Users\kris\Desktop\motorola>
cheers
ok then, the link supplied for moto-fastboot is incorrect - found in the instruction link http://forum.xda-developers.com/showthread.php?t=1138092 - the guide also needs to add to press the up arrow to transfer the images. moto-fastboot.exe is not included in the original link.
I assume the initial link is for linux.
Nope that's what I used on windows 7 x64 mate, and I didnt have to press up to transfer the images either :S
I had no problem with the moto-fastboot, but it does just get stuck on the loading screen with unlocked.
When I run Gingerbreak, nothing happens?
EDIT: Fixed.
usb debugging on and usb storage
I heard that people are reporting bluetooth problems after rooting their atrix. Can anyone confirm that their bluetooth are working after rooting here??
airheli1201 said:
I heard that people are reporting bluetooth problems after rooting their atrix. Can anyone confirm that their bluetooth are working after rooting here??
Click to expand...
Click to collapse
I didn't have any issues
another quick question. Will the data on my internal storage be somewhat erased by following these steps???
edit: found out... yes it does, yes it does. haha. lost all my application data! oh well.
Hi,
followed all the steps on unlocking the bootloader and all went well, expect now it appears stuck on rsd saying executed 100%, but 'please manually reboot power up this phone'. Oddly though the phone is already on, what should I do?
Hi ive rooted and unlocked the bootloader and was following the guide to a T...
on the part of flashing 2.3.4 ORANGE i downloaded all the relevant files and placed them the motofastboot folder. it says to then turn the phone off and boot into fast mode which i have done. and then pressed volume up and now states tarting Fastboot protocol support
I then connect the phone to the computer and started step 5. and it says its not recognised as an internal or external command....etc etc! what am i doing wrong? i tried to put cd before the command prompt and it just says system can not find the path??? but i have everything in the correct place? help plssss
Have you put renamed the motofastbootx86 or x64 to just motobootfastboot and then your commands will work. Hope that helps
Am desperate to get Gingerbread installed on my Atrix I have followed all the above steps carefully (atleast I think I have) but when I get to the stage of flashing at the cmd prompt I get:
The program can't start because adbWinApi.dll is missing from your computer. Try reinstalling the program to fix this problem.
What am I doing wrong ??? Thanks in advance
---------- Post added at 10:18 PM ---------- Previous post was at 09:53 PM ----------
Roberts56 I had that problem at 1st and founf that the motofastboot file is corrupt, I did a search and downloaded it from elsewhere and it all worked fine.
Well it did untill I got my error message above ;-(
Here is the working version with the dll files that I was missing, hope this helps.
Sorted me out in the end and I have to say it has given my Atrix a new lease of life.
Am well impressed
Hello. I'm kinda new to all this android scene sooo have few questions. Updated mine XS via Flashtool, but stuck on rooting it .
When i access fastboot toolbox, and under "Select kernel to flash" select "recovery-nozomi.img" i get an error. Here's the log..
Code:
22/023/2012 03:23:44 - INFO - <- This level is successfully initialized
22/023/2012 03:23:44 - INFO - Flashtool Version 0.8.6.0 built on 2012-06-13 08:08:54
22/023/2012 03:23:44 - INFO - You can drag and drop ftf files here to start flashing them
22/023/2012 03:23:49 - INFO - Device disconnected
22/024/2012 03:24:10 - INFO - Device connected in fastboot mode
22/024/2012 03:24:17 - INFO - Launching Fastboot Toolbox 1.0 by DooMLoRD
22/024/2012 03:24:17 - INFO - Device Status: FASTBOOT mode
22/024/2012 03:24:19 - INFO - Device Status: FASTBOOT mode
22/024/2012 03:24:24 - INFO - Device Status: FASTBOOT mode
22/024/2012 03:24:25 - INFO - Fetching connected device info
22/024/2012 03:24:25 - INFO - Connected device info: [ PSDN:CB511WRU0U&ZLP ]
22/024/2012 03:24:28 - INFO - Fetching fastboot version info from connected device
22/024/2012 03:24:28 - INFO - FASTBOOT version info: [ version: 0.5 ]
22/024/2012 03:24:35 - INFO - Selected kernel (boot.img or kernel.sin): C:\Flashtool\recovery-nozomi.img
22/024/2012 03:24:35 - INFO - Flashing selected kernel
22/024/2012 03:24:35 - INFO - sending 'boot' (5414 KB)...
22/024/2012 03:24:35 - INFO - FAILED (remote: The Device must be rooted first)
22/024/2012 03:24:35 - INFO - finished. total time: 0.009s
22/024/2012 03:24:35 - INFO - FASTBOOT Output:
sending 'boot' (5414 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.009s
22/024/2012 03:24:35 - INFO - Please check the log before rebooting into system
What i'm doing wrong?
Also i found prerooted ICS for my XS, but it's .img format. When i was updating i updated with ".ftf" file . How do i install that ".img" ? (via fastboot toolbox by selecting "select system to Flash" ??)
Thank you
Follow the instructions in this thread:-
http://forum.xda-developers.com/showthread.php?t=1723610
I did the ftf route then manually rooted.
Good Luck.
@op, Is your bootloader unlocked?
Sent from my LT26i using XDA
I think I'll try and help some more here, as sometimes the devs assume everyone is as sharp as they are!
This is the idiots guide, forgive me if I'm stating the obvious!
Ok, make sure you have the latest version of Flashtool installed, 0.8.6.0 is the latest I believe.
Download and copy the 6.1.a.0.452 ftf file to the firmwares folder of wherever you installed flashtool, mine is c:/Flashtool/firmwares.
Now, switch off the phone... Wait 20 seconds or so.
Whilst pressing the volume down button, connect the usb.
You should, if your drivers are installed correctly see device connected in flash mode appear in the window. The phones LED will be green.
Click the lightining flash button.
Select Flash Mode.
You will see the file listed in the 'select a firmware' window; select it.
If you do not wish to wipe data, then unselect the wipe data checkbox, I suggest you do wipe, click OK.
Flashtool now preps itself and some seconds later flashing should commence.
I've been re-faslhing mine as I write this, so I know it works.
Now, rooting... You will need an unlocked bootloader, assuming you have, if you have not, then check out the link:
http://forum.xda-developers.com/showthread.php?t=1527159
You may or may not be able to unlock the bootloader, depends who the provider/supplier was. Mine was from phones4u and was a generic unbranded unit.
Once, you have unlocked the bootloader then you can procede to rooting the phone.
I am assuming here that you have downloaded the following files:
CWM-SuperSU-v0.92.zip
kernel.rar
recovery-nozomi.img
You will also have installed Fastboot, and added it to your windows paths.
First things first, browse your Xperia from Filebrowser, and copy the file "CWM-SuperSU-v0.92.zip" to the root folder.
In Windows, browse to the folder containing the .img file and the extracted kernel.sin file. Launch a command prompt from that folder, do this by holding the shft key down when you right mouse and select 'open command window here'.
Now, if you have done your paths correctly etc, type fastboot, and you will get a list of the command options, this is just to prove your paths!
Type 'fastboot flash boot recovery-nozami.img'
You will get waiting for device...
Phone off, wait 20 seconds or so...
holding volume UP key, connect usb, device will flash.
Now, unplug the usb and power up the phone, you will see a menu, using the vol keys, up and down, 'select install zip from sdcard' using the camera button to select.
then select 'choose zip file from SD card'
You should see the 'CWM-SuperSU-v0.92.zip' we copied earlier at the bottom of the list, select it.
It should now have a little list with no's and a yes, so up/dpwn to the yes with the option to install and select.
That should install correctly, mine just has, and we are almost there.
In little menu at the top, select 'go back' and you will see an option to 'reboot system', do not select it yet!
Go back to your windows prompt, and type
Type 'fastboot flash boot kernel.sin'
Now back to the phone, and insert the usb cable... press the camera button and immediately press volume up, LED will turn blue. Now, this is where it may just be my PC, but what I need to do now, is hit return on the pc and it says Waiting for device, I quickly unplug the usb, and plug it back in, and it flashes the kernel.sin file.
The trick is in the 'reboot system' and getting the vol up timing right to enter the fastboot mode.
That's the way I've done it, and it all works perfectly. Hope it helps you.
first you need to unlock bootloader which MAY void your warranty, than you have to instal custom KERNEL, doomlord have wonderful kernel.
Than over kernel recovery flash pre rooted image.
I was not aware that the ICS ftf was not an official sony release; if it is signed by Sony, you do not need an unlocked bootloader.
Custom Kernel for ICS??? Since last night?
marjohn56 said:
I was not aware that the ICS ftf was not an official sony release; if it is signed by Sony, you do not need an unlocked bootloader.
Custom Kernel for ICS??? Since last night?
Click to expand...
Click to collapse
What you are doing above is trying to root, which for now needs a unlocked bootloader to do. The official firmware itself is signed so it's not an issue, but flashing recovery and switching out kernels is, and won't be allowed on a locked bootloader.
@electrash:
Doom hasn't built a kernel for ICS yet, right? It's not a good idea to flash a GB kernel over ICS, its a good way to break things :/.
Sent from my LT26i using XDA
Which his exactly what I wrote in my instructions; as I said, he can blow ICS, he may or may not be able to root.
I'm not trying to do anything... I've already done it.
Sent from my LT26i using Tapatalk 2
marjohn56 said:
Which his exactly what I wrote in my instructions; as I said, he can blow ICS, he may or may not be able to root.
I'm not trying to do anything... I've already done it.
Sent from my LT26i using Tapatalk 2
Click to expand...
Click to collapse
Haha, thought you were the op asking that, sorry
*shuffles out of thread*
Sent from my LT26i using XDA
marjohn56, excellent instructions, thank you! As far as I saw this one is the only one that describes the process of flashing SU inside recovery. Thanks a lot!
The only thing I can add is that you may turn off your phone once SuperSU was installed. The phone will just not power on the actual system until kernel.sin will be flashed, it will be just booted to recovery every time. So once phone was turned off, just hold the volume up button and plug in the USB cable, then flash kernel.sin as described. The process of flashing kernel.sin is the same as flashing nozomi-recovery, from fastboot point of view. What we're doing is just putting recovery image to root the device and then putting kernel image back to work normally with the system.
Correct me if I'm wrong...
Hi,
I've been using CM7.2 with fxp 119 for some time and today tried an upgrade to fxp125.
Used flashtool to create a bundle with the kernel.sin that came in the zip file.
Flashed to x10.
Booted into cwm and selected install cm7.2 zip from sd card. All ok so far.
But when it rebooted it got stuck at the fxp boot screen, left it for about 30 mins and still nothing. So I pulled the battery and tried to boot it again, still nothing (stuck at fxp boot screen).
I tried wiping everything and re-installing cm7.2 but then it came up with an error (script aborted: assert failed: getprop) which I think means I deleted too much.
My next thought was to re-flash the kernel but now the phone won't boot into flash mode, holding the back button does nothing and it carries on into full phone mode then gets stuck at boot screen.
I tried varying combinations of buttons and try to do it quickly in flash mode before it jumps back to normal mode (which has worked long enough to flash a new kernel via flashtool) but it won't stay in flash mode long enough to get PC companion to repair it.
Any ideas on how to get it back up and running again on any rom?
from what i can understand is you CAN flash but its failing on pccompanion ?
so do you think you'll be able to flash a full rom trough flashtool ?
like this one for example
http://forum.xda-developers.com/showthread.php?t=1698204
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!FT 0.8 is mandatory to flash this bundle!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Yeah for some reason after a lot of attempts it did a couple of times. I had to preload Flashtool then held the back button whilst putting in the battery and plugging the USB at the same time. However it doesn't seem to do even do that any more.
If I plug it into a mains charger it tries to boot but stops at the bootscreen. If I try to plug it into the laptop on normal mode it tries does the same, if I plug it in whilst holding the back button it just tries to boot as normal then freezes at the bootscreen.
It just won't boot into flash mode at all any more.
ive helped someone before with about the same problem .
and at the end it turned out to be something silly .
so to make sure could you do the following steps.
1-Flashtool (select what to flash) then it will ask you to unplug, turn off phone etc.
2-unplug
3-take out battery
4-Replug
5-Hold back button and keep holding it
6-insert battery as your holding back button.
try flashing something you know that works / worked before . or the full rom linked i gave you.
the reason i ask you to do this is, if you cant flash or enter recovery what left right ?
Yep, am doing as you describe with a rom I know has worked before, but no matter how long I hold the back button it still starts to try to fully boot.
I've got the newest Flashtool but can't get that full ftf you linked, that file site doesn't seem to work for me, hasn't for months, just says it start downloading but never does.
The message from Flashtool (sounds serious):-
01/049/2012 19:49:34 - INFO - Selected X10_X10_X10.ftf
01/049/2012 19:49:34 - INFO - Preparing files for flashing
01/049/2012 19:49:34 - INFO - Please connect your device into flashmode.
01/049/2012 19:49:46 - INFO - Device connected in flash mode
01/049/2012 19:49:47 - INFO - Opening device for R/W
01/049/2012 19:49:47 - INFO - Reading device information
01/049/2012 19:49:47 - INFO - Phone ready for flashmode operations.
01/049/2012 19:49:47 - INFO - Start Flashing
01/049/2012 19:49:47 - INFO - Flashing loader
01/049/2012 19:49:47 - INFO - Ending flash session
01/049/2012 19:49:47 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_DYNAMIC="SIN header verification failed"
01/049/2012 19:49:47 - ERROR - Error flashing. Aborted
01/049/2012 19:49:47 - INFO - Device connected in flash mode
01/049/2012 19:49:48 - INFO - Device disconnected
01/049/2012 19:49:50 - INFO - Device connected in flash mode
ok next step is to try SEUS
instead of pc companinon.
http://sony-ericsson-update-service.en.uptodown.com/
get back to stock if possible and try again.
easy pesy
just revert back to stock 2.3.3 rom
open seus->support->update phone->in red color repair phone would be written in the window PRESS IT->wait then select your phone from the list....->it says take battery out for 5 secs->press back button and keep pressing it then connect the usb cable.....->voila it starts downloading stock rom from internet and then would update....
took 25mins with me
p.s till the process of selecting your phone you dont need to connectit just swtich off your phone.....
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 ?
Cheers for the comments about SEUS. However, before I had a chance to read them I had already read on another forum about someone using Wotan to repair a different model of Xperia that was in a similar state to mine. So I paid the fee and the thing worked.
It makes think it was something more to do with my laptop environment than the phone. Because the Wotan client came with it's own driver, which my device loaded and used when I connected it holding the back button, this seemed to make the phone stay in flash mode when connected.
From this experience I don't think holding the back button puts an X10 into flash mode, it merely asks the host 'can I be in flash mode?' and either the host says yes or no.
Awsome to hear you getting it up and running
Mind me asking if you installed flashtool drivers?
Sent from my x10 using xda premium
Hi there (and my excuses upfront if posting in the wrong section, I checked twice but you never know),
having a Archos 40 Titanium, I wanted to root my device through this (whiteboard.ping.se/Android/Rooting) tutorial on Linux. Nevertheless, nothing is perfect, and my first problem was unpacking the root file system. Some research led to a (android.stackexchange.com/questions/58825/unpack-initramfs-cpio-gz-boot-img-from-mtk6589-phone) StackExchange question and the mtk-tools, with which un- and repacking the kernel + ramdisk was pretty easy.
The next problem was on a lower level; with the resulting boot.img file, I went into fastboot mode and entered
fastboot boot boot.img
into my terminal, which gave the following output:
downloading 'boot.img'...
OKAY [ 0.191s]
booting...
while my phone showed
USB Transferring...
USB Transmission OK Time: <some number in ms> Vel: <some number in bk/s>
then, both the terminal and my phone stayed stuck for an indefinite amount of time. Thinking that this process shouldn't be stuck at this point, I tried
fastboot continue
which results in a < waiting for device > message. The only option left is dis- and reconnecting the usb cable and then running "fastboot continue", after which my phone seems to boot using the image from flash memory.
Googling only led me to (android.stackexchange.com/questions/98678/fastboot-kernel-command-line-parameters), a similar problem with no answers.
So, the question is: what causes the phone not to immediately boot, and how could I continue to eventually root my phone? Preferably with this or a similar method. Thanks in advance.
ROOT here easy : https://forum.xda-developers.com/showthread.php?t=2590225
After flashing TWRP version 3.7.0_9.0-poplar, and waiting for "Your device has been unlocked and can't be trusted." message to disappear it displays "Your device has been unlocked and the boot image is not working".
How have I flashed TWRP:
Code:
# NOTE: I am using Arch Linux as the host, not windows adb installed from official repositories.
adb reboot bootloader
fastboot oem unlock 0x################ (I have blackout unlock code)
# Restarted and seted up device again, OEM unlocked is enabled in settings + USB debugging
adb reboot bootloader
fastboot flash boot twrp-3.7.0_9-0-poplar.img
After flashing finished and phone being restarted I encountered the message above.
So far I have tried to:
Boot into recovery mode. Power button + Volume Down, the same result except now I have SONY logo for around 5 seconds.
Using ADB to boot into recovery. "adb wait-for-device" doesn't work and never sees the device.
Also when plugged into a computer green light appears in left top corner of phone and also it won't react to any buttons like Power and Volume Up/Down. But Power + Volume Up (completely turn off device) is an exception and it still works.
I think TWRP was corrupted when transferring probably because I have two cables and probably grabbed the one which likes to on random stop transferring data
Is there a way to flash original boot or repair this phone?
EDIT: Okay so I managed to enable fastboot mode. But I can't find stock Boot/ROM.
EDIT 2: Finally created ftf image using Flashtool using files downloaded using XperiFirm. Now the issue is when entering flashmode (Volume Down + Power [NOT fastboot]), green light indicator lights up for ~4.5 seconds then for 2 seconds it turns off and cycle repeats for ever until I unplug the cable. Also when just plugging cable without pressing Vol- the result is the same. If flashmode doesn't work is there a workaround to use fastboot to flash ftf file? Also when I enter fastboot mode and try to get unlock ability I get an error:
Code:
$ fastboot flashing get_unlock_ability
FAILED (remote: 'unknown command')
fastboot: error: Command failed
(Seems like Experia XZ is refusing to execute the command, but I can still flash anything I want onto it using "fastboot flash name file")
EDIT 3: Okay so using Sin extractor in flash tool I have extracted contents form kernel_S1-SW-LIVE-DE8D-PID1-0007-MMC.sin and flashed it as boot and... it works!, but also no. Because when I was messing with this phone I also have flashed something to recovery and oem partitions and I don't know what .sin files correspond to those partitions, below I provide list of files download by ExpriFirm for Experia XZ (F8331)
F8331_Orange MCV FR-ES-PL-SK-RO_41.3.A.2.192-R9E:
Code:
Folders:
boot
Sin Files:
adspso_S1-SW-LIVE-DE8D-PID1-0007-MMC.sin
amss_fs_1_S1-MODEMSW-LIVE-DE8D-PID1-0007-MMC.sin
amss_fs_2_S1-MODEMSW-LIVE-DE8D-PID1-0007-MMC.sin
amss_fsg_S1-MODEMSW-LIVE-DE8D-PID1-0007-MMC.sin
apps_log_S1-SW-LIVE-DE8D-PID1-0007-MMC.sin
cache_S1-SW-LIVE-DE8D-PID1-0007-MMC.sin
diag_S1-SW-LIVE-DE8D-PID1-0007-MMC.sin
elabel-F8331-row-row_201804120243693.1_41.3.A.2.149_S1-ELABEL-LIVE-DE8D-PID1-0004-MMC.sin
fotakernel_S1-SW-LIVE-DE8D-PID1-0007-MMC.sin
kernel_S1-SW-LIVE-DE8D-PID1-0007-MMC.sin
modem_S1-MODEMSW-LIVE-DE8D-PID1-0007-MMC.sin
oem_S1-CUST-LIVE-DE8D-PID1-0004-MMC.sin
partition-image_S1-SW-LIVE-DE8D-PID1-0007-MBR.sin
persist_S1-SW-LIVE-DE8D-PID1-0007-MMC.sin
Qnovo_S1-SW-LIVE-DE8D-PID1-0007-MMC.sin
ramdump_S1-SW-LIVE-DE8D-PID1-0007-MMC.sin
ssd_S1-SW-LIVE-DE8D-PID1-0007-MMC.sin
system_S1-SW-LIVE-DE8D-PID1-0007-MMC.sin
userdata_S1-CUST-LIVE-DE8D-PID1-0004-MMC.sin
XML Files:
fwinfo.xml
update.xml
TA Files:
auto-boot.ta
cust-reset.ta
fota-reset.ta
master-reset.ta
osv-restriction.ta
reset-kernel-cmd-debug.ta
reset-non-secure-adb.ta
reset-wipe-reason.ta
simlock.ta
F8331_Orange MCV FR-ES-PL-SK-RO_41.3.A.2.192-R9E/boot
Code:
SIN Files:
cmnlib_S1_Boot_MSM8996_LA2_0_O_204_AID_1_TONE-TEST-HWID009470E1-SWID0C-APPID01-OEM0-AID1-DEBUG00_S1-BOOT-TEST-B316-0001-MMC.sin
cmnlib_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-COM-LIVE-HWID009470E1-SWID0C-APPID01-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
cmnlib_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-LIVE-HWID009470E1-SWID0C-APPID01-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
devcfg_S1_Boot_MSM8996_LA2_0_O_204_AID_1_TONE-TEST-HWID009470E1-SWID05-OEM0-AID1-DEBUG00_S1-BOOT-TEST-B316-0001-MMC.sin
devcfg_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-COM-LIVE-HWID009470E1-SWID05-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
devcfg_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-LIVE-HWID009470E1-SWID05-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
emmc_appsboot_S1_Boot_MSM8996_LA2_0_O_204_AID_1_TONE-TEST-HWID009470E1-SWID09-OEM0-AID1-DEBUG00_S1-BOOT-TEST-B316-0001-MMC.sin
emmc_appsboot_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-COM-LIVE-HWID009470E1-SWID09-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
emmc_appsboot_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-LIVE-HWID009470E1-SWID09-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
hyp_S1_Boot_MSM8996_LA2_0_O_204_AID_1_TONE-TEST-HWID009470E1-SWID15-OEM0-AID1-DEBUG00_S1-BOOT-TEST-B316-0001-MMC.sin
hyp_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-COM-LIVE-HWID009470E1-SWID15-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
hyp_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-LIVE-HWID009470E1-SWID15-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
keymaster_S1_Boot_MSM8996_LA2_0_O_204_AID_1_TONE-TEST-HWID009470E1-SWID0C-APPID01-OEM0-AID1-DEBUG00_S1-BOOT-TEST-B316-0001-MMC.sin
keymaster_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-COM-LIVE-HWID009470E1-SWID0C-APPID01-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
keymaster_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-LIVE-HWID009470E1-SWID0C-APPID01-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
pmic_S1_Boot_MSM8996_LA2_0_O_204_AID_1_TONE-TEST-HWID009470E1-SWID16-OEM0-AID1-DEBUG00_S1-BOOT-TEST-B316-0001-MMC.sin
pmic_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-COM-LIVE-HWID009470E1-SWID16-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
pmic_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-LIVE-HWID009470E1-SWID16-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
rpm_S1_Boot_MSM8996_LA2_0_O_204_AID_1_TONE-TEST-HWID009470E1-SWID0A-OEM0-AID1-DEBUG00_S1-BOOT-TEST-B316-0001-MMC.sin
rpm_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-COM-LIVE-HWID009470E1-SWID0A-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
rpm_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-LIVE-HWID009470E1-SWID0A-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
s1sbl_S1_Boot_MSM8996_LA2_0_O_204_AID_1_TONE-S1-BOOT-TEST-B316-0001-MMC.sin
s1sbl_S1_Boot_MSM8996_LA2_0_O_204_AID_4_S1-BOOT-LIVE-DE8D-0004-ELF_S1-BOOT-LIVE-DE8D-0004-MMC.sin
tzs1attest_S1_Boot_MSM8996_LA2_0_O_204_AID_1_TONE-TEST-HWID009470E1-SWID0C-APPID01-OEM0-AID1-DEBUG00_S1-BOOT-TEST-B316-0001-MMC.sin
tzs1attest_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-COM-LIVE-HWID009470E1-SWID0C-APPID01-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
tzs1attest_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-LIVE-HWID009470E1-SWID0C-APPID01-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
tz_S1_Boot_MSM8996_LA2_0_O_204_AID_1_TONE-TEST-HWID009470E1-SWID07-OEM0-AID1-DEBUG00_S1-BOOT-TEST-B316-0001-MMC.sin
tz_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-COM-LIVE-HWID009470E1-SWID07-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
tz_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-LIVE-HWID009470E1-SWID07-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
tzs1sbl_S1_Boot_MSM8996_LA2_0_O_204_AID_1_TONE-TEST-HWID009470E1-SWID0C-APPID01-OEM0-AID1-DEBUG00_S1-BOOT-TEST-B316-0001-MMC.sin
tzs1sbl_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-COM-LIVE-HWID009470E1-SWID0C-APPID01-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
tzs1sbl_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-LIVE-HWID009470E1-SWID0C-APPID01-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
xbl_S1_Boot_MSM8996_LA2_0_O_204_AID_1_TONE-TEST-HWID009470E1-SWID00-OEM0-AID1-DEBUG00_S1-BOOT-TEST-B316-0001-MMC.sin
xbl_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-COM-LIVE-HWID009470E1-SWID00-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
xbl_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-LIVE-HWID009470E1-SWID00-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
TA Files:
Kagura_S1BootConfig_MiscTA.ta
XML Files:
boot_delivery.xml
EDIT 4: Also I have egzamined the green light further and it looks like it reboots phone, because when I hold Vol- after green light turn off it will enter fastboot mode. I now know that ROM is located in system.sin, but when I extract the data from it I get ext4 partition which I can mount but I have absolutly no idea how to flash it as Experia XZ complains that file is too big (~5.3GB). Oh and I would almost forgot, I still don't know which .sin file is the recovery one.
EDIT 5: BIG NEWS!!! After unbricking boot partition I was able to install TWRP on recovery. I will get microSD ASAP and I will see what if I can flash stock ROM at least for now.
Thanks in advice for any kind of help!