Database Info

[Q] [E C1505] [SOLVED] A bunch of Questions

Hi guys,
i'm somewhat of a noob when it comes to Android devices, so please excuse my stupid questions.
First some facts about my device:
ROOT: Enabled
BOOTLOADER: Locked and not changeable
ROM: Latest available official release
(hope that helps at least a bit)
#1: Is it possible to bypass the bootloader lock via root? If so, how?
#2: If there is no way to bypass the lock, is it possible to modify the rom anyway? Because i want to add the swapon/swapoff functionality to expand the available ram via a swap partition on my external SD card. (already checked via terminal if swapon/swapoff is available)
Thank you in advance for your help. I hope there's a solution to my problem.

BrainInBlack said:
Hi guys,
i'm somewhat of a noob when it comes to Android devices, so please excuse my stupid questions.
First some facts about my device:
ROOT: Enabled
BOOTLOADER: Locked and not changeable
ROM: Latest available official release
(hope that helps at least a bit)
#1: Is it possible to bypass the bootloader lock via root? If so, how?
#2: If there is no way to bypass the lock, is it possible to modify the rom anyway? Because i want to add the swapon/swapoff functionality to expand the available ram via a swap partition on my external SD card. (already checked via terminal if swapon/swapoff is available)
Thank you in advance for your help. I hope there's a solution to my problem.
Click to expand...
Click to collapse
Can u plzz upload a screenshot of the page of ur device's bootloader status. Because as far as i know xperia e's bootloader isn't harlocked and can be unlocked easily.

Well, i don't known how to take a screenshot, at least on an android device.
Gesendet von meinem C1505 mit Tapatalk

BrainInBlack said:
Well, i don't known how to take a screenshot, at least on an android device.
Gesendet von meinem C1505 mit Tapatalk
Click to expand...
Click to collapse
Hold the volume down button + power button simultaneously .
Have a nice day
Sent from my C1505 using XDA Premium 4 mobile app

Img .tapatalk. com/d/14/01/24/uqe6y4ez.jpg
(had to bypass the 10 post linking thing)
Thanks again

BrainInBlack said:
Img .tapatalk. com/d/14/01/24/uqe6y4ez.jpg
(had to bypass the 10 post linking thing)
Thanks again
Click to expand...
Click to collapse
You're right - your phone isn't allowed a bootloader unlock.
Without bootloader unlock, you can't change ROMs, but you can install ICS, which is a bit faster than Jelly Bean, even slightly more than CyanogenMod. In fact, even with an unlocked bootloader, I'm using ICS. Here's how: http://forum.xda-developers.com/showthread.php?t=2579233
Now, you said you're a noob when it comes to Android, so here's how to flash an FTF:
This process will remove all installed apps, contacts and settings. Any music, stuff on the internal storage (the one for music etc.) or the microSD will be preserved.
0. Make sure you're on Windows 7 or below. For some reason, this doesn't work with Windows 8 or 8.1, so you'll have to get a 7 PC somehow.
1. Download Androxyde's Flashtool here: http://forum.xda-developers.com/showthread.php?t=920746 (use the unrestrict.li link, it's better)
2. Install it. By default, it is installed to C:\Flashtool. Open this folder, and then the "drivers" one. You'll see a driver setup file. Install the Flashtool and Fastboot drivers (in the list, they're on the bottom).
3. Now go back to the Flashtool folder, and open "firmwares". Put your FTF file here.
4. Open Flashtool. Click the lightning icon. Ensure that Flashmode is selected, and press OK. Choose the C1605 11.1.A.0.68 file, and press Flash.
5. When it tells you to, turn off your phone. Plug in the USB cable into your computer. Hold volume down (do not hold the power button), and (point of no return now) plug the phone into the USB cable connected to your phone. The notification light will glow green, and hopefully everything will start flashing. When the Flashtool window tells you to disconnect your phone and turn it on, do so. Set it up, and you're on ICS!
If you want to go back to Jelly Bean, download this FTF: https://www.mediafire.com/?3fmmkbmlqtjd6cy and put it into the "firmwares" folder. Now follow the guide step 4 onward, but select "11.3.A.2.23" for Jelly Bean.
Whew, long post.

So, in principle i downgrade the device to ics with an unlocked bootloader and then can flash a custom rom that is jb based, with all features i need to expand the ram?
BrainInBlack from a C1505

BrainInBlack said:
So, in principle i downgrade the device to ics with an unlocked bootloader and then can flash a custom rom that is jb based, with all features i need to expand the ram?
BrainInBlack from a C1505
Click to expand...
Click to collapse
No, ICS won't enable you to unlock your bootloader OR install CWM OR install a custom ROM. ICS is faster than any other custom ROM (other than XboosT, which is basically ICS on steroids), so if you can't have custom ROMs, the next best thing is ICS.

Another noob's question:
I installed Xposed a few days ago on my c1505 (stock firmware, locked bl). It worked perfectly. But i've read from another post that if i remove it my phone won't boot. So is there any way to remove it without breaking my device?? Waiting for answers.

buinghia98 said:
Another noob's question:
I installed Xposed a few days ago on my c1505 (stock firmware, locked bl). It worked perfectly. But i've read from another post that if i remove it my phone won't boot. So is there any way to remove it without breaking my device?? Waiting for answers.
Click to expand...
Click to collapse
It never bricked my device!!!
Sent from my C1604 using xda app-developers app

Xmoose said:
It never bricked my device!!!
Sent from my C1604 using xda app-developers app
Click to expand...
Click to collapse
B-b-but...
http://forum.xda-developers.com/showthread.php?t=2498202
I'm using XE single... i think that makes the difference. Even tipos got bricked...

buinghia98 said:
B-b-but...
http://forum.xda-developers.com/showthread.php?t=2498202
I'm using XE single... i think that makes the difference. Even tipos got bricked...
Click to expand...
Click to collapse
But UltraGamerHD is still using his phone (in fact, he's making CM11...), right?
Right now, I uninstalled Xposed, rebooted, installed Xposed, rebooted. Nothing called a brick (although I did lose a cool Xposed mod for a reboot). Well, whatever. Uninstalling doesn't brick.
In fact, the problem in the topic is either:
1. The phone hard-bricking, which is not related to Xposed at all.
OR
2. The phone's battery being discharged to 0%, to the point where the phone cannot turn itself on and start charging.

NSDCars5 said:
But UltraGamerHD is still using his phone (in fact, he's making CM11...), right?
Right now, I uninstalled Xposed, rebooted, installed Xposed, rebooted. Nothing called a brick (although I did lose a cool Xposed mod for a reboot). Well, whatever. Uninstalling doesn't brick.
In fact, the problem in the topic is either:
1. The phone hard-bricking, which is not related to Xposed at all.
OR
2. The phone's battery being discharged to 0%, to the point where the phone cannot turn itself on and start charging.
Click to expand...
Click to collapse
Are you single or married?
Just kidding. Are you using XE single or dual sim. And do you know how did UltraGamerHD repaired his phone?

buinghia98 said:
Are you single or married?
Just kidding. Are you using XE single or dual sim. And do you know how did UltraGamerHD repaired his phone?
Click to expand...
Click to collapse
1. I'm a teen. So, yeah, single.
2. My phone's single too, but it's not a teen.
3. UltraGamerHD has been making CM11 (KitKat) for our phones, he's even shown an image - too bad it's been deleted now - but I think he's still (a bit) active here, so...
4. @UltraGamerHD? Your phone's working?

NSDCars5 said:
1. I'm a teen. So, yeah, single.
2. My phone's single too, but it's not a teen.
3. UltraGamerHD has been making CM11 (KitKat) for our phones, he's even shown an image - too bad it's been deleted now - but I think he's still (a bit) active here, so...
4. @UltraGamerHD? Your phone's working?
Click to expand...
Click to collapse
1. I dont think so... there are about 4 to 5 people are experiencing this, including you (if not, why did u take it to sony?)
2. What are u developing? And do you have a Facebook account?
3. Another question... how to install PurePerformance on locked bl? Flash gordon doesn't work.

NSDCars5 said:
1. I'm a teen. So, yeah, single.
2. My phone's single too, but it's not a teen.
3. UltraGamerHD has been making CM11 (KitKat) for our phones, he's even shown an image - too bad it's been deleted now - but I think he's still (a bit) active here, so...
4. @UltraGamerHD? Your phone's working?
Click to expand...
Click to collapse
My Xperia E is Working Fine, it was just me bieng stupid.

Okay, last questions:
1 @UltraGamerHD? How did you bricked it? And How did you repair it?
2.How to install PurePerformance on locked bootloader? My XE says "bootloader unlock allowed: no" so i cant use cwm or twrp. Flash gordon doesn't work.

buinghia98 said:
1. I dont think so... there are about 4 to 5 people are experiencing this, including you (if not, why did u take it to sony?)
2. What are u developing? And do you have a Facebook account?
3. Another question... how to install PurePerformance on locked bl? Flash gordon doesn't work.
Click to expand...
Click to collapse
1. I went to Sony cause I didn't know what the issue was - they fixed it by using a Z1 or Z Ultra charger to charge it to 9%, powered it off, and let me charge the rest at home.
2. I can't say what I'm making... it's a closely guarded secret. Nope, no Facebook. I had it, but I deleted it.
3. No idea, sorry.

buinghia98 said:
Okay, last questions:
1 @UltraGamerHD? How did you bricked it? And How did you repair it?
2.How to install PurePerformance on locked bootloader? My XE says "bootloader unlock allowed: no" so i cant use cwm or twrp. Flash gordon doesn't work.
Click to expand...
Click to collapse
I did brick it once, I went to the Orange UK store in my local town and he said he used software similar to PC Companion.
Go to phoneunlockserver.com and unlock your bootloader even if it says no for £10 GBP --> Use Google Currency to Convert Price.

Since it is kind of on topic.
 @UltraGamerHD: Any status of CM11 for Xperia E?
Bug list please? and why did the thread get deleted? :/ :|

[Q&A]Android L [AOSP] [ALPHA]

This thread in here to stop spamming in original thread by unrelated questions other than developmental discussion.
So, please free to discuss unrelated developmental questions and ask your queries here!
ORIGINAL DEVELOPMENT CAN BE FOUND HERE :
http://forum.xda-developers.com/showthread.php?p=56612845

can someone post camera samples?

fancccc said:
can someone post camera samples?
Click to expand...
Click to collapse
I flashed android L and used camera,I think it is better and better than kitkat camera more sharpen, more colours
edit: sorry bro I forgot to take screenshot and revert stock rom

It installs from cm11 or from stock
Enviado desde mi C2104 usando Tapatalk 2

help
ok...out of excitment i flashed this rom using fastboot.....but now i need to go back to my other rom (liquid smooth).......how do i do this....as there is no recovery in this rom? pls help
thanks

vimanyu devgan said:
ok...out of excitment i flashed this rom using fastboot.....but now i need to go back to my other rom (liquid smooth).......how do i do this....as there is no recovery in this rom? pls help
thanks
Click to expand...
Click to collapse
Flash the boot.img from the flashable zip the same way you flashed the boot.img from Lollipop.

Update to BETA
Will it get OTA updates? or I should download new version and reflesh?
R.I.P. My english

vimanyu devgan said:
ok...out of excitment i flashed this rom using fastboot.....but now i need to go back to my other rom (liquid smooth).......how do i do this....as there is no recovery in this rom? pls help
thanks
Click to expand...
Click to collapse
never mind i figured it out....i first flashed the rom zip through fastboot....i didnt work,the phone got stuck at the sony logo, so i then flashed the boot.img from thunderzap kernel...and now i can acces cwm and flash from there.....:laugh:

Steve Mc. Gregory said:
Will it get OTA updates? or I should download new version and reflesh?
R.I.P. My english
Click to expand...
Click to collapse
No I don't think so, maybe once we get it merged with CM12 and other custom ROMs.
Sent from my Xperia L using XDA Free mobile app

Joel16 said:
No I don't think so, maybe once we get it merged with CM12 and other custom ROMs.
Click to expand...
Click to collapse
what about CyanogenMod 12? release date, or when it will be avaliable on our devices .. etc.

Steve Mc. Gregory said:
what about CyanogenMod 12? release date, or when it will be avaliable on our devices .. etc.
Click to expand...
Click to collapse
Theres no information on a new version of CM, except that Cyanogen team has started working on Xperia Z's and Nexus 5.

Steve Mc. Gregory said:
what about CyanogenMod 12? release date, or when it will be avaliable on our devices .. etc.
Click to expand...
Click to collapse
CM12 will eventually get released, either late this year or early next year. However that doesn't mean we'll be getting it as well. We probably will, once we get more bugs fixed with L but yeah, no information about that as of now.

No network right? it's so bad, if will network coverage I will use this till full release will come :crying:

Me Unlucky or whatever
I guess I am unlucky to have the .zip but not yet tasted 'L on L' . I can't get fastboot to flash those img's.
If someone can help me out, it will be really appreciated. Here's how I tried to put the ROM on my phone (failures of course)
-I started adb, ran 'adb devices', won't show up anything, re-connected again, this time adb would recognize, but state it offline. I upgraded adb from 1.0.29 to v1.0.31, it would then work properly.
-But fastboot does'nt work at all. It won't show any device when I run 'fastboot devices'.
-I tried installing drivers again (disabling signature verification and all), it would not work.
-Although flashtool does say 'device connected in fastboot mode', but when I check drivers from Devices option, it won't list any drivers, both under adb and fastboot.
I have lost hopes of flashing by that process, I might have to wait untill a flashable zip is available. But any help for now will surely be appreciated, and since WiFi and BT has been fixed, ROM is quite usable (atleast Internet can be done).
Thank You

AvinabaDalal said:
I guess I am unlucky to have the .zip but not yet tasted L on L . I cant get fastboot to flash those imgs.
If someone can help me out, it will be really appreciated. Heres how I tried to put the ROM on my phone (failures of course)
-I started adb, ran adb devices, wont show up anything, re-connected again, this time adb would recognize, but state it offline. I upgraded adb from 1.0.29 to v1.0.31, it would then work properly.
-But fastboot doesnt work at all. It wont show any device when I run fastboot devices.
-I tried installing drivers again (disabling signature verification and all), it would not work.
-Although flashtool does say device connected in fastboot mode, but when I check drivers from Devices option, it wont list any drivers, both under adb and fastboot.
I have lost hopes of flashing by that process, I might have to wait untill a flashable zip is available. But any help for now will surely be appreciated, and since WiFi and BT has been fixed, ROM is quite usable (atleast Internet can be done).
Thank You
Click to expand...
Click to collapse
unlike cm, paranoid etc come in .zips, AOSP comes in .img . Try another pc!

Is there "Scanning Effect" due broken hwComposer ?
When it gets RIL fix ? Anu hope to make it as flashable zip ?

If I installed Android L, would there be any way currently to add PIE controls? Or would I have to wait for a 5.0 ROM like PA to be able to do that?

jay_em said:
If I installed Android L, would there be any way currently to add PIE controls? Or would I have to wait for a 5.0 ROM like PA to be able to do that?
Click to expand...
Click to collapse
Pure Vanilla Android that means ,no PIE you have to wait for PA/CM12

Link For the latest build with wife and bluetooth FIXED?

oh my F.god!! people are so annoying in the other thread! first with their many of 'Thanks' posts, then telling stories about wifi issue, and it's getting even worse! now they're looking for download link to the wifi-working rom and telling varun 'how' and 'when' update the OP.. ! to the guy who 'creates' "ROMs" !!
all this stupidity on "XDA" is mind blowing for me. I hope that admins do some serious job about it. sry for the En and other things.
Sent from my C2105 using Tapatalk

[Q&A][Root]Rooting with Locked Bootloader - NO OTA Method

After much tampering I managed to identify a procedure to root our phone(s) leaving the Stock ROM intact (addition of rooting apart, sure). This will remove the requirement to do an OTA update, which in the future could remove the rooting if any update will be available (Lollipop maybe?).
The process is very straightforward and has been tested in both OS X and Windows. Here it follows:
THIS SHOULD WORK FOR ALL XPERIA PHONES WITH KITKAT INSTALLED WHICH HAD A PREVIOUS ROM VULNERABLE TO TOWELROOT.
If your phone started with KitKat 4.4.4 or later and you want to keep the locked bootloader you may be doomed.​
GENERAL GUIDELINES:
Be sure to have the full FTF for the stock ROM you are currently running
Flash only the kernel of a ROM for your phone vulnerable to the Towelroot exploit unchecking the wipe checkboxes
Reboot the phone:
The phone will bootloop, but it doesn't matter. The Linux kernel and adb are alive and thus the "Towelroot" vulnerability is exploitable by rootkitXperia
Run rootkitXperia. After the rooting it should get stuck when trying to reboot the phone(*). Interrupt it with CTRL-C
Flash back the kernel for the ROM in your phone
Reboot the phone
Manually run the command to have the RIC permanently disabled:
Code:
adb shell "su -c /data/local/tmp/install_tool.sh"
(*) In some phones (Xperia Z?) rootkitXperia may not get stuck. If the phone reboots the rooting should be complete. Just flash back your original kernel and it should be done (untested).
The following section will explain in great detail every single step needed. It also includes all the links to the SW and procedures needed:
COMPREHENSIVE TUTORIAL:
PREPARATION:
Have your phone updated to the last ROM
Download Flashtool: link
Download rootkitXperia: link
Have adb installed: Suggested links: OSX/Linux - Windows
- Windows only: Install the phone drivers (probably using Sony PC Companion. I dunno, I don't use that Windows junk )
Enable the USB debugging: HowTo
In Settings/Security enable "Unknown sources"
Make it sure Flashtool/adb can connect to the phone: just try "adb shell" from the terminal.
Download a Jelly Bean stock ROM for YOUR phone: link for D2303
Otherwise for D2303 (but it is confirmed working with the M2 Aqua D2403 as well) you can use the attached FTF (kernel only)
From Flashtool download the FTF of your latest ROM (Menu "Devices/Check Updates" at least in OS X). Be sure to use the same ID
You may want to make a full backup using the Sony system app "Backup and restore" (or equivalent in other languages)
ROOTING:
Launch Flashtool in your Mac/PC
Power off the phone
While holding the Volume Down key connect the phone to the Mac/PC via USB
The phone top led should blink red and then green
Flashtool should report that the phone is connected in flash mode
Select the JB FTF of your choice (full RoM/kernel only).
In OSX Flashtool is glitched. You may need to select an FTF and then move upward with the arrow keys
Exclude all but the kernel. Uncheck the wipe checkboxes
Proceed with the kernel flashing . The blu icon with a thunder
After the flashing has terminated disconnect the phone from the USB
Start the phone:
This is the tricky part. Android now will bootloop. But we don't care, because the underlying Linux is well alive!! adb works and so it does the Linux kernel/OS.
And that is all we need, because rootkitXperia exploits the Towelroot vulnerability but without the need of launching the graphical interface. Just hurry a bit because it may or may not last forever.
Connect the phone via USB
From the terminal cd into the rootkitXperia directory
Launch the script: install.sh in OSX/Linux - install.bat in Windows
When the script gets stuck at the phone reboot terminate it (CTRL-C)
At this point, with the phone still in bootloop, you may check if the rooting has been successful. Just type the command:
Code:
adb shell "su -c id"
which should report
Code:
uid=0(root) gid=0(root) context=u:r:init:s0
If it doesn't something went wrong (it shouldn't).
DISABLE THE RIC (enable /system read/write):
Disconnect the phone
Power it off
Hold the Volume Down key and connect it to the computer
In Flashtool flash the kernel of your latest ROM.
Like before exclude all but the kernel, no wipe needed
Also there is an issue with 18.3.1.C.1.15 installed via PC Companion/Sony Bridge for Mac. One should flash (thus not excluding it) the "BOOTBUNDLE" as well as shown in this post
Disconnect the phone from the USB and reboot it
Connect the phone
Manually run the command:
Code:
adb shell "su -c /data/local/tmp/install_tool.sh"
Reboot and enjoy your rooted phone!
What to do next:
Press "Thanks!"
Backup your TA partition: link for OS X
Put a copy in your most favorite Cloud service (Dropbox/iCloud/Google Drive/Whatever). It's better be safe than sorry.
Update SuperSU binary and apk
Install adaway to get a rid of those annoying commercial
Anything else you rooted your phone for!
Unrooting/Recovery
You may need to use the OFF button near the SIM card slot if anything went wrong (like if you forgot to uncheck the wipe flags). That shuts down the phone. You would need a needle (or something very small) to push it. (**)
Flash with Flashtool the kernel and system from the ROM you previously downloaded to keep your data - or -
Rebuild the ROM with Sony Bridge For Mac/PC Companion
(**) Thanks to Vino Kulafu for the tip.
JB Kernel from the Xperia M2 D2303 FTF attached:
It's confirmed working with the following devices:
Xperia M2 D2303
Xperia M2 Aqua D2403

It's working
Miche1asso said:
After much tampering I managed to identify a procedure to root our phone(s) leaving the Stock ROM intact (addition of rooting apart, sure). This will remove the requirement to do an OTA update, which in the future could remove the rooting if any update will be available (Lollipop maybe?).
Click to expand...
Click to collapse
Yap, I have just test it and everthing is working fine. I was using Windows. And i could also update su binary without any problem. Thank you for sharing us this method which reduce a lot of wasted time.

Andrej732 said:
Yap, I have just test it and everthing is working fine. I was using Windows. And i could also update su binary without any problem. Thank you for sharing us this method which reduce a lot of wasted time.
Click to expand...
Click to collapse
Thanks for confirming!
BTW did you use the attached kernel?

Miche1asso said:
Thanks for confirming!
BTW did you use the attached kernel?
Click to expand...
Click to collapse
Yes, everything is fine.

Many thanks for this!
Successfully rooted Generic Philippine D2303 4.4.4 KK firmware, with full R/W access using the above instructions.
However, I suggest that the above steps be updated for clarity. Happy rooting guys; this is a much more convenient way to root, albeit complicated.
This should be moved to General section or Android Development section so people can see this thread easily.
:good:

Vino Kulafu said:
However, I suggest that the above steps be updated for clarity. Happy rooting guys; this is a much more convenient way to root, albeit complicated.
Click to expand...
Click to collapse
Do you mean to make a short version? I mean, as it is now it's a full guide, from A to Z. I was thinking about making a section with the 4-5 steps for the skilled users. Too bad I didn't think about reserving the second post. Is there any way to have it added? Otherwise I'll put it in the bottom with a reference on the top.
EDIT: Added a generic procedure on the top.
This should be moved to General section or Android Development section so people can see this thread easily.
:good:
Click to expand...
Click to collapse
yeah, I was thinking about making a thread there pointing to this one as well. The process is quite generic, although I think in the Xperia Z rootkitXperia does reboot the phone disabling the RIC.

No need to make a short version, my friend; it's good enough. Here are some suggestions though:
1. I think the portion about holding the up volume key is wrong since it boots the phone into fastboot mode while we need to go to flash mode.
2. Kindly stress the importance of unchecking the wipe checkboxes in flashmode. If not unchecked, you could end up with a bootlooping phone wherein the root kit will not function since the adb debug setting has been reset, which leads to #3.
3. Make use of the OFF button near the sim card slot when faced with the situation described in #2. Just flash back the original kernel and repeat.
My experience was this:
I didn't wait for reboot; I cancelled the procedure when it hung in the reboot part. Then I shut the phone off using the OFF button near the sim card slot, then flashed back stock KK kernel only. Afterwards, I proceeded to the disabling RIC then reboot again. Presto, all is well.
:laugh:

Vino Kulafu said:
No need to make a short version, my friend; it's good enough. Here are some suggestions though:
1. I think the portion about holding the up volume key is wrong since it boots the phone into fastboot mode while we need to go to flash mode.
2. Kindly stress the importance of unchecking the wipe checkboxes in flashmode. If not unchecked, you could end up with a bootlooping phone wherein the root kit will not function since the adb debug setting has been reset, which leads to #3.
3. Make use of the OFF button near the sim card slot when faced with the situation described in #2. Just flash back the original kernel and repeat.
My experience was this:
I didn't wait for reboot; I cancelled the procedure when it hung in the reboot part. Then I shut the phone off using the OFF button near the sim card slot, then flashed back stock KK kernel only. Afterwards, I proceeded to the disabling RIC then reboot again. Presto, all is well.
:laugh:
Click to expand...
Click to collapse
Ok, let me see:
1. Crap. I always get confused. It is Volume down, then, I just checked. I'll fix it.
2. Oh, I didn't think it could get so bad. I just unchecked the boxes to avoid to lose my data.. Well, yes, thinking about that it makes sense now.
3. I'll add it. Thanks.

As i know, with Locked bootloader even if you hold volume up (+ button) it will reject the connection with phone. Otherwise great guide and you should contact someone of moderators to move this in General section.
Thanks
Xperia M2 D2303 on K.K. 4.4.4

how the Xperia M2 Aqua (D2403) ?
Is there a solution root for D2403 with locked bootloader ?
sorry bad my language

Dzepar said:
As i know, with Locked bootloader even if you hold volume up (+ button) it will reject the connection with phone. Otherwise great guide and you should contact someone of moderators to move this in General section.
Thanks
Xperia M2 D2303 on K.K. 4.4.4
Click to expand...
Click to collapse
No, no. One just needs to hold Volume Down. WIth the locked bootloader we can flash all FTF we like as long as they are from Sony.
I also made a new thread in the general section just with the "General Guidelines" also pointing to this one. But thanks.
Actually it made the portal!
i_1 said:
Is there a solution root for D2403 with locked bootloader ?
sorry bad my language
Click to expand...
Click to collapse
If it had a Jelly Bean ROM just download the FTF (don't ask me from where) and follow this guide.

sorry .. no I do not understand
after successful with rootkitxperia , so need to flash back stock kernel before?

Yes, you need flash back stock KK kernel. After doing that, the phone should boot properly. Then you can proceed to disabling the RIC module steps.

Why is this?
anyone can help ?

sorry
i_1 said:
anyone can help ?
Click to expand...
Click to collapse
sorry I'm not as thorough with his files ...
now xperia M2 Aqua (D2403) has been rooting with locked bootloader on KitKat 4.4.4
Thank you Miche1asso with this awesome work ...:good::good::good:
Thank you also for Kulafu Vino has helped me with explanation...:good::good::good:

i_1 said:
sorry I'm not as thorough with his files ...
now xperia M2 Aqua (D2403) has been rooting with locked bootloader on KitKat 4.4.4
Thank you Miche1asso with this awesome work ...:good::good::good:
Thank you also for Kulafu Vino has helped me with explanation...:good::good::good:
Click to expand...
Click to collapse
Help me please i have same phone like you i dont have kernel but have the firmware for 2403

i_1 said:
sorry I'm not as thorough with his files ...
now xperia M2 Aqua (D2403) has been rooting with locked bootloader on KitKat 4.4.4
Thank you Miche1asso with this awesome work ...:good::good::good:
Thank you also for Kulafu Vino has helped me with explanation...:good::good::good:
Click to expand...
Click to collapse
You're welcome!
So, let me understand: did you flash my attached JB kernel for the M2 D2303 in the M2 Aqua D2403? I'd like this to be confirmed so in the case I will add it to the guide.

Miche1asso said:
You're welcome!
So, let me understand: did you flash my attached JB kernel for the M2 D2303 in the M2 Aqua D2403? I'd like this to be confirmed so in the case I will add it to the guide.
Click to expand...
Click to collapse
Yes ... I'm using your D2303 JB kernel
---------- Post added at 01:20 AM ---------- Previous post was at 01:09 AM ----------
Postiga 41 said:
Help me please i have same phone like you i dont have kernel but have the firmware for 2403
Click to expand...
Click to collapse
Just wait for the later addition of tutorials from Miche1asso

Postiga 41 said:
Help me please i have same phone like you i dont have kernel but have the firmware for 2403
Click to expand...
Click to collapse
The kernel I attached in the main post works for the D2403 as well. I updated the guide confirming it. Download it and follow the instruction step by step.

After flashing latest kernel , phone just shows sony then blank screen...but adb can detect the device...
any fix??

Xperia E3 broken

Hello. I have broken my XPERIA E3. I had cyanogenmod 12 (works in 5.0 android) there and I wanted to get stock ROM. I tried to flash 4.4.4 android, but now I can't do anything. Phone turns off, there is "SONY XPERIA", and after that it turns off. I can't stop it, but I can wait when the phone gets discharged. After that I can use ANDROXYDE FLASHTOOL FOR XPERIA, but I don't know what can I flash. Please help me .
It does not matter if you give me tutorial to get stock ROM, or stay in the cyanogenmod. I need only make the phone work. Please. When I'll fix it, I will never install alternative roms or something like that. thanks. :angel:

re
876bdf said:
Hello. I have broken my XPERIA E3. I had cyanogenmod 12 (works in 5.0 android) there and I wanted to get stock ROM. I tried to flash 4.4.4 android, but now I can't do anything. Phone turns off, there is "SONY XPERIA", and after that it turns off. I can't stop it, but I can wait when the phone gets discharged. After that I can use ANDROXYDE FLASHTOOL FOR XPERIA, but I don't know what can I flash. Please help me .
It does not matter if you give me tutorial to get stock ROM, or stay in the cyanogenmod. I need only make the phone work. Please. When I'll fix it, I will never install alternative roms or something like that. thanks. :angel:
Click to expand...
Click to collapse
It is necessary to press the off button, after the flash if the battery is discharged, you will perfectly sew together it is not

I don't understand you bro... I can use the POWER button. But I don't know what I have to flash .

I suppose that since you were using cyanogenmod, you had model number D2203.
Explain to me:
-How did you flash 4.4.4 stock?
-Did you have a backup?

george_sl said:
I suppose that since you were using cyanogenmod, you had model number D2203.
Explain to me:
-How did you flash 4.4.4 stock?
-Did you have a backup?
Click to expand...
Click to collapse
I flashed it using androxyde flashtool 0.9.20. I runned flashtool64 as administrator and it doesn't completed flash. I runned flashtool64 as normal user, all was OK and I have got stock rom and all is OK. Thanx for all.

OK, good to know that your phone is fixed

I had cyanogenmod 12 (works in 5.0 android)
Click to expand...
Click to collapse
btw, can you tell me how u installed cyanogenmod? I have absolutely no idea how to install it...

876bdf said:
I don't understand you bro... I can use the POWER button. But I don't know what I have to flash .
Click to expand...
Click to collapse
First things first charge your phone and then open ur backpanel u will c a small hole near the sim trays its a small force off button grab something and hold it for 10secs....then as usual get the stock rom and flash it using the flashtool from fastboot.....that is connecting ur ohone to pc holding volume down button....

[Recovery] TWRP 3.1.1 for Xperia X Compact

Greetings!
I'd like to present a TWRP recovery for the Xperia X Compact. This release should work on Xperia X single and dual-SIM variant of the device. I am an owner of Xperia X, but some users reported that my recovery works just fine on its smaller brother.
DISCLAIMER:
I'm not responsible for any damage done to your device. You have been warned.
REQUIREMENTS
Unlocked bootloader
Working ADB and Fastboot (You can get the latest version through Android Studio or by visiting this site)
FEATURES
MTP support
ADB Sideload
Backups and restores almost every partition
Full SELinux support
Working encryption. You can access /data within recovery
USB-OTG
DOWNLOADS
INSTALLATION
Unlock the bootloader
Download the file
Put the following code in CMD/Terminal:
Code:
fastboot flash recovery twrp-3.1.1-kugo-*.img
//Replace * with the version you want to flash
Unplug the cable
Press Volume Down + Power to activate the recovery. When installed properly, the device should vibrate funnily, purple LED should appear and after a couple of seconds, you should see the TWRP screen.
Enjoy!
BUILD
You need to sync the OmniROM and vendor blobs from DonkeyCoyote. You can find my sources on GitHub.
android_device_sony_loire_common
https://github.com/omnirom/android_bootable_recovery/commits/android-7.1
Thanks:
@grayleshy - for initial TWRP
@AndroPlus for some of his flags
OmniROM team for sources
If you find my work useful, consider buying me a cup of coffee

it works perfectly! well can't say I tried all functions yet, but it certainly seems so.
thank you so much. finally a proper lastest version of twrp for XC that supports encryption on nougat.
btw. you have to flash it over fotakernel as described in OP. (hotbooting did not work. blank screen.)
I did try other regular X twrp versions with the same result in the past in hopes of finding something better, so the issue was likely the same since I hotbooted them too for a fast test. I guess that's what you get for being lazy. doh.
thanks again for posting it here.
/tuxen

Thank you for sharing.

thanks
Thanks for sharing brother
Working ⚒ perfectly on stock 7.0
no problem

Perfect, thanks. Only annoyance is that I can only reboot the system or power off now.

XperienceD said:
Perfect, thanks. Only annoyance is that I can only reboot the system or power off now.
Click to expand...
Click to collapse
That shouldn't work anyway. I can enable these flags if you want.

eagleeyetom said:
That shouldn't work anyway. I can enable these flags if you want.
Click to expand...
Click to collapse
For all I use the other options there's no need to go out of your way, but if you do make another for whatever reason having the options would be nice.

XperienceD said:
For all I use the other options there's no need to go out of your way, but if you do make another for whatever reason having the options would be nice.
Click to expand...
Click to collapse
It didn't work for me on X. I can enable them in the next version.

realtuxen said:
it works perfectly! well can't say I tried all functions yet, but it certainly seems so.
thank you so much. finally a proper lastest version of twrp for XC that supports encryption on nougat.
btw. you have to flash it over fotakernel as described in OP. (hotbooting did not work. blank screen.)
I did try other regular X twrp versions with the same result in the past in hopes of finding something better, so the issue was likely the same since I hotbooted them too for a fast test. I guess that's what you get for being lazy. doh.
thanks again for posting it here.
/tuxen
Click to expand...
Click to collapse
What do you mean by hot booting? I did this to boot to twrp without installing and have no problem
Code:
fastboot boot twrp.img
Thanks for the twrp, with this I can make full backup before trying to update to 7.1 or 8.0 later :good:

MTP is not working in this version. Everything else is top notch, will test backup/restore a bit later and report back.

trewelu said:
What do you mean by hot booting? I did this to boot to twrp without installing and have no problem
Code:
fastboot boot twrp.img
Thanks for the twrp, with this I can make full backup before trying to update to 7.1 or 8.0 later :good:
Click to expand...
Click to collapse
Exactly. I know hotbooting is not the best description, but you understood anyway.
Strange, I am not a flashophile so I usually just booted twrp this way after a upgrade with flashtool. When the phone was connected to the pc anyway.
But it only works for me with the androplus version, oshmoun's version won't boot that way either. It's not the first time I have talked odd twrp behaviour though, as another guy could not get the androplus one to work at all. I have no reason to doubt him, as this is pretty casual stuff.
I see you are still on MM, I have been on N since it came out and if I remember correctly I backed up ta just before N came out (exploit and N came out very close to each other), took the ota, and unlocked BL. So I performed all the 'fastboots' (better word? heh) on that and 7.1.1. Perhaps the bootloader changed someway? I have no idea.
Edit: if I learned to read properly the first time, you are NOT on MM (doh) but 7.0. Sorry and even more strange. Does MTP work for you? (see below)
---------- Post added at 20:00 ---------- Previous post was at 19:58 ----------
kekistaneerefugee said:
MTP is not working in this version. Everything else is top notch, will test backup/restore a bit later and report back.
Click to expand...
Click to collapse
MTP works absolutely fine here..

This version uses Sony init, so you can see the Sony screen and led indicator while entering the recovery mode. I'm not planning to change it before creating an official TWRP.

eagleeyetom said:
This version uses Sony init, so you can see the Sony screen and led indicator while entering the recovery mode. I'm not planning to change it before creating an official TWRP.
Click to expand...
Click to collapse
Is this in response to something functional, or just general cosmetics info? Doesn't the sony screen origin from the bootloader? How should a official twrp look while booting it? I get the sony boot and led then the TWRP boot image, isn't that normal when booting fotakernel replaced by TWRP? ie. the bootloader handles it when turning the phone on while holding vol down.
An official version would sure be nice. I more than appreciate what you already done. So just take your time.

realtuxen said:
But it only works for me with the androplus version, oshmoun's version won't boot that way either. It's not the first time I have talked odd twrp behaviour though, as another guy could not get the androplus one to work at all. I have no reason to doubt him, as this is pretty casual stuff.
Edit: if I learned to read properly the first time, you are NOT on MM (doh) but 7.0. Sorry and even more strange. Does MTP work for you? (see below)
Click to expand...
Click to collapse
Strange, I don't have problem booting twrp without installing for either of twrp.
I'm on 7.0. I tried to update to 7.1, but I don't get signal if I do the ta_poc + tobias drm fix method, and the drm is still marked as broken.
I really hate mtp and avoid it. I don't think I even have mtp working properly on my pc. I can't help you test that one. Sorry.

trewelu said:
Strange, I don't have problem booting twrp without installing for either of twrp.
I'm on 7.0. I tried to update to 7.1, but I don't get signal if I do the ta_poc + tobias drm fix method, and the drm is still marked as broken.
Click to expand...
Click to collapse
Why are you running it through both ta_poc and Tobias rootkernel with drm fix?
Either you use ta_poc to mount your ta backup from before the bootloader was unlocked thereby bringing the whole trim area back including drm.
Or you use Tobias rootkernel to fix or 'emulate" drm.
Both tools can disable dm verity, sony ric, etc. there is no reason (other than likely creating trouble) to run the kernel image though both tools?!
If you for example run a boot.img with drm fix through ta_poc it will remove the drm fix first. So I imagine things could go wrong of you apply drm fix again (if that is what you're doing) after using ta_poc.
I really hate mtp and avoid it. I don't think I even have mtp working properly on my pc. I can't help you test that one. Sorry.
Click to expand...
Click to collapse
Lol I hate it general too, it can come in handy when only twrp is booted though. I am not sure I have any drivers installed either. Regardless I can access a drive resembling my phone labeled 'mtp device' in 'my computer' when I boot twrp.
Edit: sorry for sidetracking the thread a bit.

eagleeyetom said:
NEEDS TESTING
USB-OTG
Click to expand...
Click to collapse
Thanks! and i can confirm that USB OTG works well.

Working on Sony Nougat
This is the only TWRP I can decrypt my data with on Sony Nougat Stock ROM, Thanks !

realtuxen said:
Both tools can disable dm verity, sony ric, etc. there is no reason (other than likely creating trouble) to run the kernel image though both tools?!
Click to expand...
Click to collapse
Using both tools stems from users reporting they had to to get Magisk to work.

XperienceD said:
Using both tools stems from users reporting they had to to get Magisk to work.
Click to expand...
Click to collapse
There was an info in one of threads, that you should get the stock kernel first through TA_POC and then through kernel repack tool. If you did not, it would work, but occassionally reboots. I am now on 7.1.1 build 206 with Genesis Kernel 1.05 (no_DRM patch version) and it works ok.
As for TWRP, thanks for this! It works ok. Can not fastboot it, must be flashed in recovery parition, but no deal for me. Only thing that I wonder, there are options to backup system, data etc, but not Internal SD (/data/data). Why?

Hi I have a question, I have N 7.1.1, and i want to root it, so i need the twrp, if I flash this twrp, its okay? Ty!