Search results

have you selected all the wipe ticks?

Yes, i finally succeed to connect in DIAG Mod with this tuto http://rsap-xperia-sp.blog.hu/2016/04/18/udvozlunk_a_blog_hu-n_58054 unfortunately, i could'nt unblocked the SIM access for the time being. In fact, i succeed by putting the FTM to 1, but we lost the radio when the phone is not...

if fact, my main goal is to use RSAP to connect my phone to my car, and for that, i need to enter in diag mod. it seems that the only way to do that is to allow it in the kernel with the "usb qualcomn diagnostic bridge driver" option. AndroPlus, could you build a boot.img with this option ? or...

no, it's not working. it seems that the diag access is blocked at the kernel level, and the only solution is to build a kernel with this access enabled... as i hav'nt the source, i'm not able to try. i will ask if androplus can do that for us.

pb of root with .417 i use V21 on .417 and , even supersu tells all it's ok and well root, i'm not able to have a full root. /system is mount in read-only, link2sd isn't able to delete a bloat soft, ... i hadn't this kind of problem with MM and V04. is there a solution, because for the time...

the best is to tick all the wipe and no exclude.

I think it's due to the bug of 0.9.23.1. download the patch for 0.9.23.2 from flashtool.net and it will be fine. you have only to replace the x10flasher.jar and restart flashtool.

Hello, in order to connect my new XZ to my car, in RSAP mode, i'd like to enable the SIM access via QPST. the problem is i don't find the way to open the diag mod, so i can't connect with QPST... i have installed drivers, but it seems that there isn't one for a modem access (COMxx). any idea ?

there is no recovery on stock rom. you need to root your device and upgrade the TA with the Emma tool

Hello, can you tell me if you have baseband or not, because on LTE phone, we cannot build a rom with baseband nor usable EMEI

the easiest way is to use PHIL'Z kernel. it includes the recovery by pressing "Power" and just after "sound down". once you are on recovery, select "advance features", and you will found the re-root option. just press and reboot the phone. install SU an that's done.

have you data ? with LTE ?

Hopefully, i made a img file who allows to flash the new TA. use Flashtool to flash and you should be able to flash a recovery after that . http://forum.xda-developers.com/showpost.php?p=65851727&postcount=138

you need the new bootloader in order to flash the recovery. for that, use EMMA and select the new TA

for me, you have two solutions : - hold simultaneously the power button and the vol+ key. stay the two buttons pressed until the phone vibrates 3 times (it could be long : ~1 minute) if it's not ok : - open the SIM +SD card flap : on the upper side, there is a small hole : press in it with a...

for some days, there is new fxp marshmallow builds for T3. they are not on the regular host, but click on "mirror" and you will have it. unfortunately, it seems not to be fully working... allways no sdcard and no mobile data. i did'nt test the camera.

You are lucky, because i succeed today to flashed back the new bootloader. one month ago, i made a wrong flash, and i destroied the bootloader. i was allways able to flash KK, but no longer Lollipop or Mashmallow. so, if you dont' see the new TA with Emma, here is the way i did it this morning...

did you try to make a hard reset, by holding the power button and the vol+ key. you stay with the two buttons pressed and have to wait a long time before the phone vibrate a first time an after three short times. that's it, the phone is well reset and ready to enter in flash mode.

so, did you ugrade the bootloader with Emma ? if not, you can't start any custom ROM.

have you flash the new bootloader ? it's the only way to boot !

once more, i can't boot on CM based ROM... i have no SONY logo, so no boot process...

No because, the only way to download is to accept a lot of offers which cost a lot.

yes, but i can't boot !?? i havn't the sony logo at boot, so it seems there is no bootloader ?!

Do you have external smicard? because i can't Envoyé de mon D5103 en utilisant Tapatalk

ok, i think there is a missunderstanding. in order to flash the kernel, you need to be in fastboot mode (with the blue light). so, once you have installed the zip file, shut down the phone (in recovery mode, select "power options/power off" , disconnect the phone and reconnect it in fastboot...

@ jerpelea : where do you find a working recovery.mg, because, the one i cook with the actual AOSP code is not running...

Cyanogen ROM are distributed in zip format, so you have to : - push the zip file to your sdcard - you need a kernel with recovery (for the time being, the Philz one) - you enter in recovery mode - you select "install zip" and the zip file. once it's finished, install the right kernel for that...

and 4G, and sdcard1...

Non exactly, WiFi is ok, camera not What we need also is sdcard and 4g Envoyé de mon D5103 en utilisant Tapatalk

i don't really know, but perhaps Plus has no 2G ? so, as AOSP for the time being is not able to detect 3 or 4G, may be it should only detect 2G network ---------- Post added at 12:35 AM ---------- Previous post was at 12:19 AM ---------- Good news ! the build i cooked based on the today code...

Today, the git has a lot of updates. i'll try to compile a new build tonight. I tried bluetooth sound with AOSP_L_MR1_150518 and it's well working : all sounds are well playing on an a2dp connection, but it's not easy to have allways a BT speaker in order to hear something :D. the last CM...

AMIGAnTOMEK : have you update the bootloader ?

no, you can't, and you must have the new bootloader

Exact, the drivers are included in the phone, so if it couldn't be discoverd by your PC, i think the only way is to reflash the complete ROM. for that, the best is to use Emma who recognise automaticaly the right phone. ther is no need of driver because you connect in fastboot mode, and drivers...

Sorry, just replace "device" by "seagull". now, the 150510 is released, but i don't try yet.

it's easy and depend of the answer to this question : did you use EMMA http://developer.sonymobile.com/services/flash-tool/ ? it's the only tool who allows the update. if none, you can't boot 5.1. if yes, you can boot 5.1. you have also unlock the recovery access. to verify, you shut down the...

TA partition and DRM issues are only if you unlock the bootloader, not root

vmlc : 18.1.A.2.25 is for d5103 et d5106, 18.1.a.2.32 is for d5102 obnoxiouschild : you can find the last version by using flashtool or xperifirm. in flashtool, click on "devices-check updates" select your phone, select your build corresponding to your country and your operator, or the...

Why don't you exactly the tuto ? if you make the right EXPORT (search the right place of the directory "prebuilts/gcc/linux-x86/arm/arm-eabi-4.6/bin" in order to configure precisely the CROSS_COMPILE variable, and after that you only the variable name as it's writen in the tuto and not the full...

i forgot one bad : no ext sdcard

Hello, i tried the AOSP_L_MR1_150506_device.zip from FXP, and the result is amazing. of course, there is a lot of issues : - no sound - only 2G - no camera but - wifi is well working, with WPS ok - bluetooth pairing is ok with car hand free kit. unfortunatly, RSAP is nok. the new bootloader...

recovery for 5.1.1 Hello, as we are able now to boot on 5.1.1, how to have a working recovery ? is it possible to have only TRWP in a recovery.img in order to flash the d5103 ?

just follow this thread : http://forum.xda-developers.com/xperia-t3/general/bootloader-devices-real-recovery-t3096835

which version have you flashed ? with AOSP_L_MR1_150501_seagull.zip, boot is completed well. you have only to wait, because on boot, you have first the Sony logo, after a black screen the logo "android", and an other sequence of black screen and "android". at the end : Lollipop :good: wifi ...

No, if you update the bootloader, you can boot. i got it few minutes before. i have to test and to add gapps before.

I tried that, but the problem is Emma asks for registering, i filled the form twice but didn't receive the credentials.... :( it's written that i have to wait for the validation, but now, i wait for 3 days Edit : Oups! i didn't read the install guide who speaks about the customisation.ini. i...

Did you do something special, because, i flashed the same, and i got bootloop once more...

I installed Emma and registered, but i didn't received a password. is it normal to have such a delay ?

lalotche, you said that you succeed in making a running rom, but how did you do, because, i can't. all the making process run well, finaly i have well all the images (boot, system, userdata, recovery) but no one is running. i'm allways stuck on bootloop... could you explain how it's oosible to...

i'am afraid no one... :( i tried to build AOSP, and allways bootloop. there is a recovery.img, but no way to flash it, because, the partition recovery does'nt exist. i spent a lot of time to switch between bootloop with lollipop and kitkat.