Database Users

zergRush can root xperia Arc .42 fw

I followed this guide and it worked perfectly first time on my xperia Arc.

Should make life a lot simpler for those with a locked BL.

Great news! Thanks for testing Takyon!

@XperienceD, saved my hair lol. No matter what I tried, ota would not install 2.3.4.
Sent via subspace beacon from my Arc.

ingro said:
Great news! Thanks for testing Takyon!
Click to expand...
Click to collapse
It was more out of desperation lol. The pdf guide is simple to follow too.
Sent via subspace beacon from my Arc.

Lord Takyon said:
It was more out of desperation lol. The pdf guide is simple to follow too.
Sent via subspace beacon from my Arc.
Click to expand...
Click to collapse
Yes this tool can root all of version firmware now

Lord Takyon said:
I followed this guide and it worked perfectly first time.
Click to expand...
Click to collapse
Wow, that's a great news, but it's little late as I unlocked my BL a while ago, but nevertheless, it will make the life lot better for those who can't unlock the BL.

can this method work on Xperia Arc ??? cause i only see that it works on Xperia Play..

mr.alawi said:
can this method work on Xperia Arc ??? cause i only see that it works on Xperia Play..
Click to expand...
Click to collapse
Sorry, missed that info, yes it works fine on Arc, that is the phone I have.
I will edit my post.

Yep, works fine on my Arc running 4.0.2.A.0.42, bootloader locked. Can access root using Root Explorer, so everything seems to be fine for now. Finally, no need to risk having the 0% battery problem anymore

Thank you very much! But before i´ll root my arc i´ve to ask if it is possible to reroot the phone without flashing firmware over seus?

Thanks, mate . I've been a bit apprehensive of rooting by unlocking the bootloader or downgrading by flashing.
This method ought to settle those qualms I've had about the above.
Cheers!

Wow, Flawless rooting and no more downgrading bs needed .
Awesome Find.

didnt work for me gave error after step 11 in guide was couldnt find mkdir /data/local/tmp" or something similar tried the step after that one same again tried repeating guide three times so just gave up.Is there not a one click one for arc tried one i think for samsung other day but to my suprise it didnt work. help please!

Works perfectly on 4.0.1.A.0.266 Generic UK Arc S\LT18i - thanks!

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanx Man!
No more downgrade bulls**t, but we need one-click solution for the people not used to adb_shell....

cokey77 said:
didnt work for me gave error after step 11 in guide was couldnt find mkdir /data/local/tmp" or something similar tried the step after that one same again tried repeating guide three times so just gave up.Is there not a one click one for arc tried one i think for samsung other day but to my suprise it didnt work. help please!
Click to expand...
Click to collapse
You forgot to type in exit you were still in the adb shell made the same error, afterwards it worked.
Downloading the SDK took longer than the rooting process. Worked great and easy using the noob guide, thx

Works perfectly on my LT15a running 2.3.4!

works perfectly on my Xperia Arc S (LT18i)

I got the following message :
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
error: device not found
What should I do?
please note that the device is connected to the PC and it recognize it!
Thanks a lot in advance

Z2 Root Exploit

Hey guys, this is a cross-post of sorts. I just got root execution on my stock Z2 Tablet and it appears that the same method should work for Z2 phone. I have a Z2 phone but just haven't tested it on that one yet.
Here is my Windows, Linux and Mac OSX script to grab the TA partition from Sony devices and deploy full root (superuser + reboot script):
https://mega.co.nz/#!jRB1FBJT!RKIi13TRj__mi7pKIGXP654CBJHi2gc0bIlYONcSfZQ [Update, v11]
Requirements:
1. Be on a firmware earlier than .402
Instructions:
1. Extract exploit.tar.gz and run ./root.sh (Linux) or root.bat (Windows)
2. Follow the instructions and your TA.img will be given and su will be deployed.
Features:
This disables SELinux, takes out sony_ric and then deploys su to /system/xbin/su
This works on ALL Sony Android mobile phones.
This can be run on any operating system.
Survives reboots [thanks to chargemon by DooMLoRD]

can't download the file. MEGA asking me about a decryption key.

Might be onto something here. This is for those that only want root and not an unlocked BL right?

Awesome work if it is working. Unfortunately I'm on .402
Sent from my D6503 using Tapatalk

Really? how about on .55? If it'll work on that I'm rolling back the update. *gets .55 ftf*

Awesome if this in fact works on the Z2!
And who cares if it requires .69 and doesn't run under .402? The only reason I currently don't want to unlock my BL is the loss of my TA partition. So one could simply downgrade to .69, backup TA, upgrade to .402 again and unlock BL (and insert DRM keys again), right?

in_finity said:
Awesome if this in fact works on the Z2!
And who cares if it requires .69 and doesn't run under .402? The only reason I currently don't want to unlock my BL is the loss of my TA partition. So one could simply downgrade to .69, backup TA, upgrade to .402 again and unlock BL (and insert DRM keys again), right?
Click to expand...
Click to collapse
That's exactly what I did.
Technically it should work on 55 too but just not sure because I copy all the vendor libs from 69 tablet.
Someone could easily make a generic firmware that works on all phones with all firmwares but that's not my focus. I just wanted to get this out here and working for Sony because I'm surprised it isn't out already.

xsacha said:
That's exactly what I did.
Technically it should work on 55 too but just not sure because I copy all the vendor libs from 69 tablet.
Someone could easily make a generic firmware that works on all phones with all firmwares but that's not my focus. I just wanted to get this out here and working for Sony because I'm surprised it isn't out already.
Click to expand...
Click to collapse
I'll have a go with it on .55, I've been having some problems with .402 anyway so it gives me an excuse to roll back the update, now I just need to get my hands on a linux live disc. (should have one knocking about).

Awesome I hope this works. I'll have a try tomorrow
Sent from my D6503 using XDA Free mobile app

Can anyone confirm if this works? It would be great!
Sent from my D6503 using Tapatalk

This is great, can someone translate this into a more user friendly method.:good:

Wow none have tried it yet??
Sent from my Xperia Z1 Compact

I tested with D6503 17.1.A.2.69 Orange FR, and successfully crashed service menu,
but TA.img was not backuped.
My bootloader is already unlocked, but it should not affect backing up TA.

Which error did you get? Can you check output in logcat?

xsacha said:
Which error did you get? Can you check output in logcat?
Click to expand...
Click to collapse
Here is the log:
View attachment log.zip
files are in /data/local/tmp but not executed.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(don't mind su)

RyokoN said:
I tested with D6503 17.1.A.2.69 Orange FR, and successfully crashed service menu,
but TA.img was not backuped.
My bootloader is already unlocked, but it should not affect backing up TA.
Click to expand...
Click to collapse
RyokoN said:
Here is the log:
View attachment 2795383
files are in /data/local/tmp but not executed.
View attachment 2795394
(don't mind su)
Click to expand...
Click to collapse
Awesome. Looks like everything worked right up to the last vdc which was run by the wrong user. Easy fix. Looks like this definitely works on z2 phone then.
Funnily enough I actually had it right in the first version I made and quickly changed it to run as system a few minutes later.
Try my original script instead: https://mega.co.nz/#!PFoGEBAR!ulKWKy407aYE1vi0F9eZtNVROdG7DbJfFkKLcuIjDko

xsacha said:
Awesome. Looks like everything worked right up to the last vdc which was run by the wrong user. Easy fix. Looks like this definitely works on z2 phone then.
Click to expand...
Click to collapse
Bro, Who are you? You just made my day. I was about to unlock my phone since there's no exploit.
Today is the best day of my life.
Finished the graduation Exam. Received Z2 Tab, Saw that this awesome being found an exploit. I am literally happy right now. :highfive:

chesterr said:
Bro, Who are you? You just made my day. I was about to unlock my phone since there's no exploit.
Today is the best day of my life.
Finished the graduation Exam. Received Z2 Tab, Saw that this awesome being found an exploit. I am literally happy right now. :highfive:
Click to expand...
Click to collapse
Great news. I'm just a happy z2 user that can't live without root. Made a root utility for my last tablet (Blackberry Playbook) too.
I might improve this script to have more checks in it. More logging.

Awesome work xsacha and thanks!
Has anyone tried this on .55 yet??
Sent from my D6503 using Tapatalk

xsacha said:
Awesome. Looks like everything worked right up to the last vdc which was run by the wrong user. Easy fix. Looks like this definitely works on z2 phone then.
Funnily enough I actually had it right in the first version I made and quickly changed it to run as system a few minutes later.
Try my original script instead: https://mega.co.nz/#!PFoGEBAR!ulKWKy407aYE1vi0F9eZtNVROdG7DbJfFkKLcuIjDko
Click to expand...
Click to collapse
I haven't had success yet (running exploit scripts under MacOSX 10.9).
First attempt (from exploit in first post): http://pastebin.com/jwTKWwPu
Second attempt (from exploit "original script"): http://pastebin.com/N7FXRAAw
I'm on a stock standard Telstra Z2 phone (17.1.A.2.55).

[MoFo] XT1096 and AT&T XT1097 - Do NOT take the 5.1 OTA if you want to keep root

We can stay on the 5.0/5.0.2 bootloader (motoboot.img) and partition table (gpt.bin) and flash rooted 5.1 images using MoFo as well as the 5.1 kernel and radios using fastboot. Details for the XT1096 are here:
http://forum.xda-developers.com/showpost.php?p=61685122&postcount=46
Do not take the 5.1 OTA - flash manually!!!
If you upgrade to the 5.1 bootloader and partition table - YOUR COPY OF MOFO.EXE WILL NO LONGER WORK FOR YOUR DEVICE!!!!

There was a little bit of weirdness when I flashed the rooted image and tried to go into recovery to wipe cache - the dead android kept flashing at me and I couldn't get into the recovery menu. So then I flashed the 5.1 recovery. It is working fine now. I think I will flash back to 5.0 and then reflash it to see if that happens again.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Excellent news! Thanks @JulesJam!
We all learned a lot with our prior MoFo experience, so here's hoping the features are added to the 5.1 ROM with less troubleshooting this time.

Where is the rooted copy you used?

Can the mofo crew just update the binary to read the new gpt?

d33dvb said:
Can the mofo crew just update the binary to read the new gpt?
Click to expand...
Click to collapse
I am not sure what you are talking about.
MoFo.exe relies on an exploit to trick the bootloader to allow you to flash an unsigned system image. According to maiko1, the exploit was patched in the 5.1 bootloader. Supposedly he is working on trying to find an exploit in the 5.1 bootloader that he can use to do the same thing but only time will tell if he can find one.

Legacystar said:
Where is the rooted copy you used?
Click to expand...
Click to collapse
I didn't post it anywhere yet b/c of the issues I was having. @mikeoswego has a rooted image that he baked useful features into. When he posts his, I will just flash that and see how it works. He has a thread in the Android Development section of this forum where he posts his images.
http://forum.xda-developers.com/showpost.php?p=61702833&postcount=215

JulesJam said:
I am not sure what you are talking about.
MoFo.exe relies on an exploit to trick the bootloader to allow you to flash an unsigned system image. According to maiko1, the exploit was patched in the 5.1 bootloader. Supposedly he is working on trying to find an exploit in the 5.1 bootloader that he can use to do the same thing but only time will tell if he can find one.
Click to expand...
Click to collapse
I thought it was that it could not verify your device because of the way it read your info on the device. I assumed he used a zero day he had to attack the verification step of fastboot. I had thought about attacking in this manner. I mean, without busybox, can we try normal Linux shell privilege escalation attacks for this kernel version just like a desktop Linux machine? Are there any previous root methods and how they were obtained? I still say at this point, it would be great to be told what the exploit was, even without code.
---------- Post added at 05:01 AM ---------- Previous post was at 05:00 AM ----------
So it was specific to the bootloader, do we know at which version it became patched?

d33dvb said:
So it was specific to the bootloader, do we know at which version it became patched?
Click to expand...
Click to collapse
Its worked on all versions from 4.4.4 on up but according to maiko1, not on 5.1.

double post.

d33dvb said:
I still say at this point, it would be great to be told what the exploit was, even without code.
Click to expand...
Click to collapse
I think if the exploit has been patched, he should release what the exploit was as there is no harm at this point in releasing that information. Someone should ask him to do that.

The exploit was posted awhile ago according to jcase. What maiko didn't do was post his code for mofo because he owns that. If you want more info pm or tweet jcase.

[Request] Sony's Android Concept Marshmallow Build 2085

Hello everyone,
As you know Sony give us a Concept Rom based on Android Marshmallow. It should have been only accessible to 10 000 people, but, Thanks to @Jozinek, @jenkins-84, and @russel5 every possessor of an Xperia Z3 Compact can flash this rom, using Flashtools or using custom recovery.
Among the tons of great things that this rom contains, Sony gives us OTA update. Initially the rom started on version 2058 and everyone could update to 2085 BUT Sony cut, for an unknown reason, the OTA update.
Some people have been able to update their rom BEFORE Sony's update cuting, and this is my request :
Someone having a Sony Xperia Z3 Compact using Sony's Android Concept Marshmallow updated to MRA58K.Z1.2085-somc, rooted or not, with custom kernel or not, please contact me, via this thread, or via PM, so I could try to make an flashable update for everyone stuck to 2053

[NEWS]
Hi there, some people send me, or are uploading their 2085 files. Thanks to them for responding me !
In the next hour I'll be working for the 2085 flashable zip, if all goes well, between today and tomorow, it will be available !
[NEWS 2]
Not enought quick, someone made it before me, so, sorry for those who wanted to help me but jenkins-84 made it ! Will give the link here when he finish his upload ^^

it is online on his thread working fine except a few small things

moly82 said:
it is online on his thread working fine except a few small things
Click to expand...
Click to collapse
what thread ?

http://forum.xda-developers.com/showthread.php?t=3232674

I think I may have fix the Force close if you want to try mine tell it ^^

yes please!

Useless, jenkins is to quick for me x)

Moiremoi said:
I think I may have fix the Force close if you want to try mine tell it ^^
Click to expand...
Click to collapse
Can you share your link, I think there some difference between OTA vs update.zip. Home launcher is example, I have a friend who have ota and he show me that we can cho a style like iPhone or original style

lamducthien said:
Can you share your link, I think there some difference between OTA vs update.zip. Home launcher is example, I have a friend who have ota and he show me that we can cho a style like iPhone or original style
Click to expand...
Click to collapse
Sorry but in my update, there isn't the second mode of the home apps But I have the home apk and odex which have this option
Badly, it force close when I use it :/

Do you still have an untouched ota file that we with locked bootloader could sideload via adb recovery? I tried it with Jenkins version, but got bad software version error..
Sent from my D5803 using Tapatalk

StefanGA said:
Do you still have an untouched ota file that we with locked bootloader could sideload via adb recovery? I tried it with Jenkins version, but got bad software version error..
Sent from my D5803 using Tapatalk
Click to expand...
Click to collapse
Yep, I have one, @p11tiwari give me his system dump and I send it to jenkins, He's in talk with @p11tiwari to know if he can have the new update

New update released, build 2099
Sent from my D6603 using XDA Free mobile app

spityu85hun said:
New update released, build 2099
Sent from my D6603 using XDA Free mobile app
Click to expand...
Click to collapse
I know it, but I don't know if someone with a Z3 Compact have it

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Edit: It seems one boolean flag in preventing us from getting ota update, I'm gonna apply for concept. Let's see what happens next

LegendM said:
Edit: It seems one boolean flag in preventing us from getting ota update, I'm gonna apply for concept. Let's see what happens next
Click to expand...
Click to collapse
I hope you can do it !

[GUIDE] Flashing XA Ultra with Latest Flashtool (Where FSC is need)

The Lateste flashtool requires the right fsc script in order to flash something. This script is not available by default in Flashtool and let us use the 0.9.18.6 version buggy as f**k. I was getting "Error while processing whatever.sin" over and over.
Flashing with the 0.23 results in "FSC script is mandatory, Aborting flash". I don't know if this works with every firmware and every model of XA Ultra and I'm not responsive if something bad happens to your device. I'm just saying that I wanted to downgrade my .109 to .111 (service unit bla bla bla in XperiFirm) and what was getting tons of errors.
This is what I did in order to simulate a FSC script:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- Copy F32XX to .flashtool/mydevices/
- Return to devices and go to F31XX
- Copy the "default.fsc" to the F32XX directory in "mydevices"
Now rename this FSC script following your model and your firmware you want to flash.
Now open the latest flashtool and try to flash normally the firmware you want, when it asks if you want to use the FSC script, choose yes then wait for it to finish.
I do not guarantee it'll work or whatever, I'm just saying it worked to recover a Soft Bricked F3212 to .111 and got it rooted with xposed, with fully working front camera !
Edit : I don't know why the pictures are missing, please see the album here : https://imgur.com/a/bHrmT

I try tomorrow...thanx post! F3216

Thanks a lot. I've been stuck for weeks due to FSC script error. I've tried your method on F3212 and confirm that it works

Thank you @Yooooomi for your guide and I hope it will avoid bricked Ultra after flashing firmware :good:

Thanks for posting this guide

Working on F3216! Install fw after rooting and back and front cam working

Successd with my soft Bricked F3212 SA Brand, thanks a lot.

Help Downgrading to .111
So I've download the .111 service exchange unit firmware from Xpefirm, and created a bundle to flash it through flash tool, this is what I get in the attachment. What wrong am I doing here ? This is my first time dealing with Xpefirm so please guide me on what do from here

Can you tell me if it works correctly? Could you make a video? I tried to change the firmware of my XAU and brinked my device, and I'm afraid to do it again and it will happen the same. Thanks

taitakacha said:
Can you tell me if it works correctly?
Click to expand...
Click to collapse
As you see may people did it and it worked for them, on a bricked device you should try... It seems to work on every xa ultra model

Could you please rescan the images?

Can you upload images again? Thanks!

taitakacha said:
Could you please rescan the images?
Click to expand...
Click to collapse
merolrockstar said:
Can you upload images again? Thanks!
Click to expand...
Click to collapse
The images are still up. Check Link.
Only not showing correctly. idk why.
http://i.imgur.com/tfnhlxA.png
Click to expand...
Click to collapse
Btw. This worked for me. I was able to flash even with locked bootloader.
Cheers to TS.

So with this your device will no te hardbrick?

Yooooomi said:
As you see may people did it and it worked for them, on a bricked device you should try... It seems to work on every xa ultra model
Click to expand...
Click to collapse
XA Ultra dual (F3216) Flashing with flash tool.Please
post Video lesson.
Thank

I know what rooting is. Do you have to flash to root!

Am receiving the same error
Talal Tango said:
So I've download the .111 service exchange unit firmware from Xpefirm, and created a bundle to flash it through flash tool, this is what I get in the attachment. What wrong am I doing here ? This is my first time dealing with Xpefirm so please guide me on what do from here
Click to expand...
Click to collapse
Hi am on F3211 xperia ultra and after flashing recoveery and pssible a wrong bootloader I found myself wana restore to stock firmware. am currently the same error you got. please sharre with me if u find a pplace around it.
thank you.

Affable Nuru said:
Hi am on F3211 xperia ultra and after flashing recoveery and pssible a wrong bootloader I found myself wana restore to stock firmware. am currently the same error you got. please sharre with me if u find a pplace around it.
thank you.
Click to expand...
Click to collapse
Searched for a solution but didn't find anything on it, so I simply gave up. But I'll sure get back to you if I find anything.

Found that my F31XX Folder did´t have a Default FSC, instead have a "33.2.fsc".
Thinks this will work?

merolrockstar said:
Found that my F31XX Folder did´t have a Default FSC, instead have a "33.2.fsc".
Thinks this will work?
Click to expand...
Click to collapse
I used the 33.2 I think, I just replaced the version in the name by mine this evening I could attach the fsc file to the thread