yashsingh1/xdaforums huggingface dataset:
[Sony Xperia S, Acro S, Ion] hitman-xda:
Recently, Xperia Acro S was been removed from the Unlocking Bootloader list on the Official Sony site.

As maintaining a thread on Acro S section, some of my friends were unable to unlock their bootloader due to missing device in the list.

So, I Emailed Sony few weeks ago requesting them to re-list Acro S, and they said, they'll look at this. Now its been Re-listed.

I have even attached three screenshots for your conformation. So see it, Just check out below three links,

SS-01 || SS-02 || SS-03

For those who were waiting to unlock their phone, here's a good news for you all. Go ahead and get the unlock code from official Sony site providing them your IMEI.

1. To Get Unlock Code just click HERE!

2. Unlocking Bootloader step-by-step Guide, just click HERE!

Regards,

hitman-xda
[Sony Xperia S, Acro S, Ion] hitman-xda:
As I said, I'll notify you after Acro S is re-listed, I'll mention you here; [MENTION=6887296]bluvn[/MENTION] || [MENTION=5016765]sky202_how89[/MENTION] || [MENTION=6925005]els_sand[/MENTION]
[Sony Xperia S, Acro S, Ion] sky202_how89:
Wow, Thanks for the surprise! U make my days!
[Sony Xperia S, Acro S, Ion] hitman-xda:
That sounds good :)
[Sony Xperia S, Acro S, Ion] sky202_how89:
Hey but too bad is I totally brick my phone. Almost all of the solution found by google seems no used.

Out of surprise, it happened for most of the Xperia Phones who are heavy flashing with custom ROM.

Check out the thread here: http://xdaforums.com/xperia-s/help/xperia-acro-s-sim-card-service-detect-t3200650

Now my XAS is becoming a powerful MP4 Player. What a desperate. ;( ;(
[Sony Xperia S, Acro S, Ion] hitman-xda:
Did you checked weather your Bootloader is unlocked? If not then check it.

Also try to repair your phone through PC companion.

Its a strange problem. Hearing it first time.

Did you followed exact procedure of the Guide that I linked?

I don't think it occurs due to heavy flashing of ROMs, because I have used every ROM available for the phone for almost 100 times. I usually change my ROM after a month.
[Sony Xperia S, Acro S, Ion] sky202_how89:
The problem occurred when the user try to flash back to stock ROM from Custom ROM.

The Bootloader is unlocked.

Now the BL appear to be like this: Bootloader Unlock Allowed = No (*#*#7378423#*#*)

Enter fastboot fail (No fastboot detected), Only Flash is allowed.

To install CWM or TWRP required fastboot, so I can't do anything besides keep trying to flash wiith different version of stock FTF.

Solution I tried but failed:

- Fix using Sony PC Companion (PCC)

- Flash any version of stock ROM, inclusive of just flashed the "Baseband" only.

- Flash Acro-HD S0-03D ROM then flash back to stock ROM.

- *#*#4636#*#* -> Phone information -> Set preferred network type (any of the option & reboot)

- Settings -> More -> Mobile Networks -> Network Mode(any option & reboot)

- Settings -> More -> Mobile Networks -> Select providers (automatic or manual), it manage to detects the service providers but registered on the network failed.

- Insert other active SIM Card

I try to locate the Antenna Board but it seems like it was attached with the mainboard. Unlike Xperia Z, the Antenna Board is seperated.

I assume this problem occurred when the partition accidentally bricked by Flashtool? I did try to flash different version of Baseband, nothing seems work.

I need someone favors. Create a Pre-rooted Stock ROM(.ftf) with Recovery Accessed (CWM or TWRP).

I found somewhere from this forum stated that tried to install back any of the Custom ROM to fix the No Signal Issue which it appeared to be my last hope. Without Recovery(Required Fastboot to install), I couldn't install any custom ROM.
[Sony Xperia S, Acro S, Ion] hitman-xda:
First of all let me clear that 'Unlocking Bootloader Allowed = No'

That means you cannot unlock it unless your coming to stock from other ROM.

Also Bootloader can be unlocked only once. So if your coming back to stock from custom, why did you tried to unlock your BL again?

Even if you flash stock ftf, you no need to unlock your BL again.

Secondly, don't try to flash other ROMs into your phone, you could mess up everything, even hard brick.

Your Fastboot mode isn't working, right? If so, then try to install fastboot drivers from flashtool driver pack. Maybe it could work.
[Sony Xperia S, Acro S, Ion] sky202_how89:
I did not lock my BL, it just lock back by themselves. I still remember I unlock my BL with Sony Official way in 2013. After that, I did not touch that BL again. It's just after the recent flash which I did the same way like before(Custom to stock ROM), everything mess up.

I even format my pc which I thought it was my pc issue earlier. But ends up I realize it was something regarding to my BL. With BL Unlock Allowed: No, you cannot enter to your bootloader or fastboot.

This video is showing exactly my problem now:

[YOUTUBE]WdJ0DREwdEM[/YOUTUBE]

Other thread that I discovered with same issue as I am:

http://xdaforums.com/showthread.php?t=2432566

http://xdaforums.com/xperia-z/help/xperia-z-signal-drops-unable-to-connect-t2183045

My very last but not recommended solution is to change the motherboard. However, looking at the posting not only me having the issue and it mostly happened when users are flashing back from Custom ROMS to Stock ROMS.

Changing motherboard is like changing another phone, your feeling towards the phone changed. :(
[Sony Xperia S, Acro S, Ion] hitman-xda:
After flashing stock ftf, the BL status always shows 'Bootloader Unlock Allowed = No' but it is actually unlocked. So it does not get relock after flashing stock ftf.

It seems like a serious problem.

Maybe, flashing other ROM will help you a bit. For that Obviously your phone must enter into fastboot mode (which is not happening). In this case did you use 'dd' command for installing recovery? If not then you could try it. And I think you'll be succeeded to install recovery and further you can flash ROM.zip through recovery.

You just need to copy recovery.img into your internal memory and enter some command's using adb shell.
[Sony Xperia S, Acro S, Ion] Mirhawk:
You must have used a newer version of flashtool. This is causing similar issues for many people. The only solution for now seems going to Sony service center. There is another method too, flashing the TA backup, but I don''t know if it works or not.
[Sony Xperia S, Acro S, Ion] sky202_how89:
I will try & let you know soonest. Kinda busy this few days. :p

---------- Post added at 05:35 PM ---------- Previous post was at 05:32 PM ----------

YES, I am flashing with NEWEST VERSION of Flashtool. After that, the result turned nagative.

Do you mean TA Partition? Do you have a backup copy of it?

---------- Post added at 05:41 PM ---------- Previous post was at 05:35 PM ----------

Latest UPDATE about the issue, PLEASE TAKE NOTE BECAUSE YOU'RE ABOUT TO BRICK YOUR PHONE JUST LIKE ME. THIS IS IMPORTANT!

@hitman-xda , Please pass this message around. Btw, How to quote the name?

http://xdaforums.com/xperia-s/help/...ice-detect-t3200650/post62904161#post62904161
[Sony Xperia S, Acro S, Ion] Mirhawk:
Flashing with latest flashtool flashes a partition which renders modem of the phone useless. Yes, I mean the TA partition. Each phone's TA partition is unique, so if You flash mine or other person's TA partition, Your phone would not even boot.
[Sony Xperia S, Acro S, Ion] sky202_how89:
This is toooooooooooooooooooooooooooo OVER! It means my phone is bricked forever.

It's their mistake but we have to bear it on our owns.
[Sony Xperia S, Acro S, Ion] hitman-xda:
Did nothing worked?
[Sony Xperia S, Acro S, Ion] sky202_how89:
Yes, nothing worked because Flashtool just accidentally bricked our Sony in the whole world. A careless mistake destroy the phone.

In 0.9.18.X, simlock.ta is always excluded by default but a careless mistake on the version 0.9.19.(1234) (at that time), The Simlock.ta is included while flashing. Each phone TA has their own unique number. Besides changing the mianboard (the only solution right now), no ones manage to solve this issue.

I wonder how many Sony phone in the world has already been bricked by this Flashtool update.
[Sony Xperia S, Acro S, Ion] hitman-xda:
Well, that is disappointing :(

Hard to believe, that Sony really did that serious change in its software.
[Sony Xperia S, Acro S, Ion] sky202_how89:
At least you're out of trouble. I suggest you need to backup your TA Partition just in case.

Each TA is unique and cannot be transferred.

If your TA is used by 3rd party, they may face a Hard Brick & cannot be recovered anymore.

Well, this is an added Security by Sony. They are not stupid to "share" openly for free.

Now I'm realize.
[Sony Xperia S, Acro S, Ion] hitman-xda:
I can't do that. Coz I have already unlocked my bootloader months ago :(
[Sony Xperia S, Acro S, Ion] sky202_how89:
That's bad but still not too late. Your next Sony in future will be secured :D

I'm already ordered the replacement mainboard.

What kind of mainboard-Lock BL or Unlock BL, I do not know because it's not a new one.

Waiting for shipment.
[Sony Xperia S, Acro S, Ion] hitman-xda:
Yup gonna do that in my next xperia. Even I have edited my guide and added to backup TA.
[Sony Xperia S, Acro S, Ion] sky202_how89:
My XAS Revived!!!!!!!!!!!

I got my motherboard even though it's a 2nd hand motherboard but great news about this 2nd hand motherboard,

It's a LOCKED BL and.....

The version which last updated which is 6.2.B.0.200, I guess the first hand owner sold his XAS at pretty earlier time. (Est. one year + usage)

So, this mainboard can be considered as very new. It's a HK Edition Mainboard.

Well, I want to say..... XAS, I am back!!!
[Sony Xperia S, Acro S, Ion] damaru:
How can I check if there is something messed up with my bootloader? I got the phone second hand from someone who tried to unlock 'it' and he doesn't know if he messed around with the bootloader or not.

The wifi works great - and gps too. I've rooted the phone too. But the bootloader says no to unlocking. I've flashed aosp-hikari for locked bootloader at this point.

Should I flash back to stock to see if the bootloader is ok?
[Sony Xperia S, Acro S, Ion] hitman-xda:
Most of the time when bootloader is unlocked + stock original ROM, it says Bootloader unlocked = Yes.

When bootloader is unlocked + stock ROM (ftf) if shows Bootloader is unlocked = no

First of all try to repair your phone with PC companion. It'll flash original Sony ROM. Then check with the code whether it shows yes or no.

I think this is the only way to check whether your Bootloader is unlocked or not.

Regards,

hitman-xda
[Sony Xperia S, Acro S, Ion] damaru:
Thanks - I'll try that. I guess after that I'll have to re-root if I want to. And there wouldn't be any way to install android 5 with a locked bootloader right?
[Sony Xperia S, Acro S, Ion] hitman-xda:
Yeah! You'll have to re-root again.

There may be some ROMs available for locked Bootloader you could only flash those. Not sure if there is LP.

Regards,

hitman-xda
[Nexus 6 Q&A, Help & Troubleshooting] ProRules:
Hello guys im wondering if its safe to add a bit headphone gain using kernel adiutor?
[Nexus 6 Q&A, Help & Troubleshooting] basicreece:
Im on Chroma using built in kernel, ive added a small boost and its perfect.
[Verizon LG G2] darkharbinger81:
1st the phone is a Verizon lg g2

Android 5.0.2

software version vs98039A

2nd the phone used to be my primary, but I've been using an s3 that was given to me for free.

3rd, I finally decided to root and flash recovery (worked exceptionally well and quick too)

I don't think there's a way to unlock boot loader,but I miss having the ability to have better on it for speed stability and battery life which I've always gotten from aokp rooms, but since my s3 has a locked boot loaded and the g2 does too is it still possible to flash either pacman, paranoid android or an aokp from since I'm on stock lollipop?
[Verizon LG G3] vv1914:
I am eligible for an upgrade. I love my G3 but I'm really debating if i should move on or not. What do you guys think?
[ZenFone 2 Q&A, Help & Troubleshooting] Sudresta:
Hey Folks,

Ran a bit of trouble with my new Zenfone 2 , got it just a couple of days ago and a system update seems to have messed up. The phone froze half way through the update process and I had to turn it off (ran out of patience) and when I booted it up it just loads up to the ASUS logo and stays there for eternity.

I was not able to get to the Recovery mode, had a war with the dead android guy with the red triangle, ( holding power and volume up didn't help). I did however manage to get the device recognized on the Platform tools command like when I connected to my PC. I tried the ADB reboot command, ADB reboot recovery, and they didnt help. I did manage to work a couple of fastboot commands, fastboot erase data and fastboot erase cache BUT, looks like that's got me into deeper trouble.

Ever since I did that, I cannot manually go into the recovery mode anymore using the power and volume keys. I get a white USB logo and something that looks like a battery status bar below it. No combination of keys seem to help.

To make it worse, my device is not recognized on my PC anymore, ADB devices command doesn't list it, and neither does fastboot devices. I did however notice that now on my device manager, the phone shows up as a 'ortable Device - MTP USB Device'. No ammount of uninstalling and re-installing various kinds of ADB and USB drivers seem to help.

I did see a few blogs that give a fix for the same issue on a zenfone 5, but being a noob (hate to admit it) at this, I dont wanna risk it unless I'm sure it will help.

Can anyone help me out on this please? Any kind of help would be much appreciated
[ZenFone 2 Q&A, Help & Troubleshooting] Sagarvaghela:
Download the Lastest firmware from here

https://www.asus.com/support/Download/39/1/0/13/Lk0Sg1Ulh0Ph49Hl/32/

If you WW then download.

keep the zip file in SD card and rename it as MOFD_SDUPDATE.zip

Now go to bootloader and then recovery mode. it will automatically apply update. update may take time 10~20 mins
[ZenFone 2 Q&A, Help & Troubleshooting] corrsea:
From your description you probably need to read this thread

http://xdaforums.com/showthread.php?t=3162848

Sorry it's not good news
[ZenFone 2 Q&A, Help & Troubleshooting] Kartik007:
It's showing error (status 7) . Help Me !!
[ZenFone 2 Q&A, Help & Troubleshooting] faiyaz_m2003:
stuck on usb logo

please help me my asus zenfone 2 z008d got the same problem from yesterday . its stuck on usb logo
[ZenFone 2 Q&A, Help & Troubleshooting] metallicumahua:
Search xFSTK for repair/temporary fastboot, do the tutorial. Then goto recovery if still can. If recovery missing try to fastboot recovery. If failed then u must use Asus Flashtool to flash raw image. After that retry to flash droidboot, recovery, boot. Reboot to fastbootand go to recovery, then choose adb. Run adb sideload to flash full firmware.zip
[ZenFone 2 Q&A, Help & Troubleshooting] timbernot:
I become an expert at unbricking hehe ￼;)

Stuck on USB logo...

Turn your phone off...

Start downloader ..flashing ifwi and fwr dnx and os image..connect phone.

Try flash os image on its own repeatedly ...ignore errors just keep doing it .

Then after 10 goes at it ..flash ifwi and dnx with it repeatedly till success.

Note that when it succeeds ..

Stop! and pause, keep an eye on your screen of phone..you see it flash , might take 5 mins before you see this start ..but when its finished ..you flash raw in flash tool after and it will reboot straight into system all by itself ￼

Me have been guilty of flashing raw before the flash of downloader...and a bet many others have too.

Ps select, wipe data in flash tool too.
[ZenFone 2 Q&A, Help & Troubleshooting] ritupaul91:
i did update using the new firmware as u told by renaming the file to MOFD_SDUPDATE.zip

but after that my imei changed to 0049100491.....

then i formated whole using miracle box

now its stuck on asus logo and can't update now

hang on logo

please help
[ZenFone 2 Q&A, Help & Troubleshooting] krasCGQ:
You may want to reflash your phone using RAW firmware.
[One (M9) Q&A, Help & Troubleshooting] guyverzero:
So let me explain the scenario; I have a T-Mobile M9 that's S-Off, running Venom, and wanted to update the firmware from 1.32 to 2.7. I had done this in late July and got the success, and the firmware was running fine, but eventually the phone decided to just shut off on me, and the only way to turn it back on was via forced reboot. For the two weeks after that I had tried just about every method I read on Sneakyghost's post on the subject (I did an RUU, changed to superCID and flashed 2.10, did the full wipe and no wipe firmware) and every single time if I updated to anything newer than what was on my M9 originally it would, inevitably, do that thing where it became unresponsive after a while.

Since this seems to be a problem that only I'm having, I assume it's something I have to be doing wrong. With that in mind, is there any sort of video that has been made or really, really simple and thorough step by step instructions that could guide me through the process in a detailed way? I hate that I have to ask this, but I feel like I've done my homework and tried several different methods, and all of them have failed. I have HTC sync installed, I've tried on two different computers, I've done everything. I even flashed back 1.32 in the exact same way that I flashed 2.7, and as soon as I put it back to the old one it immediately solves the problem. Without fail putting the new firmware on has made my phone do this at least once within two days of installing, and then multiple times after that (I must've tried this about four or five separate times over three weeks). The obvious problem here is that the phone is completely unresponsive, which means that if it does this overnight my alarm doesn't work. Not to mention the missed calls and annoyances that occur when it happens throughout the day.

I just want to be able to experience the new firmware. Because right now I still have to deal with a (relatively) crappy camera experience and a phone that overheats constantly. I'm also really worried that when the M update comes out it may force me to have a newer firmware, and if I can't do it correctly I'll be out of luck.

So if anyone could help it'd be so very appreciated, either by telling me something I could have done wrong (I flashed the firmware via fastboot method both over viper and later over a stock Sense build). I also have the newest radio, so I literally have no idea what I could be doing wrong at this point, but I hope someone does. Again, thanks in advance.
[One (M9) Q&A, Help & Troubleshooting] clsA:
instructions are here >> http://xdaforums.com/att-one-m9/general/att-developer-edition-ruu-how-to-t3086948

use the sdcard method and the DE RUU or the T-mobile RUU and your phone should work fine
[One (M9) Q&A, Help & Troubleshooting] guyverzero:
Would restoring my nandroid after flashing that RUU cause anything to go wrong?
[One (M9) Q&A, Help & Troubleshooting] clsA:
it's always better to start fresh after the RUU
[One (M9) Q&A, Help & Troubleshooting] guyverzero:
Nope, it's doing the same thing again. This is my GSam from last night.

Now, let me stress that I did everything clean. RUU, did a clean setup, clean venom flash, etc. I didn't restore any settings. I don't know what to do, as the phone is completely normal under 1.32. Oh and I flash 1.32 in the same exact way I do 2.7 as well, there's no difference

View attachment 3478032
[Android Q&A, Help & Troubleshooting] Feveth:
And I am looking for a method to dump the mmcblk through ADB but without shell access. Can I force ADB to pull special files?

This device is an United TAB1023. This same device also secures /system by the kernel, and only loads signed kernels and recoveries, so I will need an unlock as well, but that's another problem.
[Sony Xperia E3] lexiyuri:
Hi Guys, this week Xperia M2 received the usual PTCRB certificate that leads M2 to lollipop. Thinking on that basis i´ve analyzed the hardware of Xperia E3 and Xperia M2 and interestingly the difference is only 4 Gb of internal storage and some minor differences in camera, screen resolution and little not so important things.

2014 Xperia models with Yukon core:

Xperia T2 Ultra

Xperia T3

Xperia M2 / M2 Aqua

Xperia E3

All they share in common one thing: yukon architecture and bird names too ;) So, lets make a filter, thinking in techical specs comparing E3 and M2 only (specs related barely to raw hardware)

Xperia M2: February 2014

CPU: Qualcomm MSM8926 Snapdragon 400 with Quad-core 1.2 GHz Cortex-A7 and GPU Adreno 305. 1 Gb RAM, Internal Storage 8 Gb.

Lollipop certified today by PTCRB

----------------------------------------------------------------------------------

Xperia E3: September 2014

CPU: Qualcomm MSM8926 Snapdragon 400 with Quad-core 1.2 GHz Cortex-A7 and GPU Adreno 305. 1 Gb RAM, Internal Storage 4 Gb.

Theres not certainity about lollipop or marshmallow

So i have realized the conclusion that due to technical problems, especially derived of the replacement of Dalvik for ART in Lollipop, we cant have lollipop in our little E3 due to associated hardware issues.

A Xperia Blog guy named sergio, told me this:

I don't say our phones so different, in fact you know M2 is D2303 and E3 is D2203. E3 is like a cheap M2. Poor camera, less screen, less internal storage, etc.

The problem is that, without swapping the internal memory by the external SD card, it's almost impossible to install a SINGLE APP. Apps, due to Android RunTime, increased the size (Dalvik+ART compatibility), that's why having lollipop inside a 4GB phone is just a crazy idea.

Can you compile it?: Yes!

Is it a good rom for an average user?: No.

Imagine you work at Sony. Think about Lollipop as an end-user rom... Wouldn't they prefer being hold back in 4.4 but at least have some more space to install apps, or, would you roll out an ota that only let's you install 1 single app in your phone?

But, now the key. Marshmallow let's you use your SD as an ampliation of your internal memory. That's why there's still a possibility that Sony updates it. The only one.

If I were you I'd wait until Sony decides what devices to update. And please, don't believe in rumors or filtrations, that only creates false hopes.

While sony doesnt clarify this, i´m almost sure we are not going to get lollipop but maybe M
[Sony Xperia E3] vanugenth:
Thank you for sharing this. I sure hope we get M on the E3.
[Sony Xperia E3] aidy.lucas:
E3 won't skip lollipop then get marshmallow it doesn't work like that. Kk is the end of the line.

D2303,18.3.1.C.1.15 kk, deodexed, debloated, rooted, philz touch recovery, bravia engine 2+x-reality+z3 super vivid, viper audio, xposed mods.
[Sony Xperia E3] Nicklas Van Dam:
are you sure? where do you know that?
[Sony Xperia E3] edi194:
Yes, IMO support for e3 ends with KK.

But, if M2 is similiar and it gets probably LP, then sources will be available for lp for it. So, probably after m2 update some devs probably can build fully working lp rom for e3 bcoz hardware similarity.
[Sony Xperia E3] Nicklas Van Dam:
Hmmm that's great, but is that release only for D2203, D2206 and D2243 only or can be for another type? Like D2202 and D2212 may be?
[Sony Xperia E3] AlexVat:
Sorry to give you the bad news guys, but here it goes: http://blogs.sonymobile.com/2015/10/06/sony-xperia-and-android-6-0-marshmallow/

I'm really sorry and upset because apart the 4GB nand the E3 had decent specs for getting at least 5.1 :(
[Sony Xperia E3] LotR656:
And thats it..... disappointed. They could publish at least working camera and everything will be nice.
[Sony Xperia E3] Tommil:
I can understand, that its not beneficial to keep developers working on upgrades for older (and cheaper) phones. But its not beneficial either to have courting because of providing vulneable phones to customers. I bought my E3 (D2203) less than month ago and there are no paches against Stagefright exploit. I have read Marshmallow compatibility document (static.googleusercontent.com/media/source.android.com/et//compatibility/android-cdd.pdf) and I do not see any reasons, why E3 must stay on KitKat.