Database Info

[Q] Tipo Dual Questions (relock, copy fw from another phone)

Hello everyone,
I have learned a lot from these forums and am thankful for everyone's hard work here. I have a Tipo Dual that was originally with firmware 11.0.A.6.5 (ST21a2, not i2). I installed GIMLO, which is generally good, but I have some issues with it (LED doesn't light for E-mail or charge, play store and games crashing, little things like that). The phone is rooted and boot loader is unlocked (all with tools from here!). I did not make a backup of my original system before I flashed (I thought I had, but it is not there, not sure how I failed at that).
I have two questions: I have tried a lot of times to relock my boot loader so I could use SUS or PC Companion to reload the firmware. It won't relock with any of the methods I have found here. Is there a reason for that? I have reloaded a stock firmware, and even then I could not relock boot loader. Anything I should look for to allow this?
I would like to put the a2 firmware back on but the firmware I find here is always the i2 version; I understand the difference is little tweaks in how the phone deals with the GSM network, and as phone connectivity is important to me, I'd like the original a2 version again. My wife has the identical phone (with ST21a2 & 11.0.A.6.5 -- or maybe 11.0.A.8), and she has not done anything to hers. Can I root, make a nandroid backup of her phone, and somehow import/flash that to my phone? I have my contacts backed up, so I'm not worried about that, and I have all my apps, so a clean install would be fine with me. If I can do this, how do I get the backup off of her phone and onto mine? Am I right in assuming that if I manage to do this, it will replace the kernel, too (I currently have the gimlo kernel)?
Do the experts here have any advice for a noob on these two questions?
Thanks, and thanks again for all your hard work here!
Fred

RealFred2 said:
Hello everyone,
I have learned a lot from these forums and am thankful for everyone's hard work here. I have a Tipo Dual that was originally with firmware 11.0.A.6.5 (ST21a2, not i2). I installed GIMLO, which is generally good, but I have some issues with it (LED doesn't light for E-mail or charge, play store and games crashing, little things like that). The phone is rooted and boot loader is unlocked (all with tools from here!). I did not make a backup of my original system before I flashed (I thought I had, but it is not there, not sure how I failed at that).
I have two questions: I have tried a lot of times to relock my boot loader so I could use SUS or PC Companion to reload the firmware. It won't relock with any of the methods I have found here. Is there a reason for that? I have reloaded a stock firmware, and even then I could not relock boot loader. Anything I should look for to allow this?
I would like to put the a2 firmware back on but the firmware I find here is always the i2 version; I understand the difference is little tweaks in how the phone deals with the GSM network, and as phone connectivity is important to me, I'd like the original a2 version again. My wife has the identical phone (with ST21a2 & 11.0.A.6.5 -- or maybe 11.0.A.8), and she has not done anything to hers. Can I root, make a nandroid backup of her phone, and somehow import/flash that to my phone? I have my contacts backed up, so I'm not worried about that, and I have all my apps, so a clean install would be fine with me. If I can do this, how do I get the backup off of her phone and onto mine? Am I right in assuming that if I manage to do this, it will replace the kernel, too (I currently have the gimlo kernel)?
Do the experts here have any advice for a noob on these two questions?
Thanks, and thanks again for all your hard work here!
Fred
Click to expand...
Click to collapse
Yes the nandroid backup would be fine but you will need to reflash the stock kernel with flashtool i don't no if theres any difference between the kernels of i/a. plus even if you relock your bootloader you still might brick your device flashing with Seus & pcc.

gavster26 said:
Yes the nandroid backup would be fine but you will need to reflash the stock kernel with flashtool i don't no if theres any difference between the kernels of i/a. plus even if you relock your bootloader you still might brick your device flashing with Seus & pcc.
Click to expand...
Click to collapse
Thanks for responding to my question, I appreciate your help.
Do you think it's better then to just do something like flash this if I want to go back to stock:
http://forum.xda-developers.com/showthread.php?t=2270976&highlight=+tipo+dual+
and just forget trying to make it retail again? As long as Sony doesn't change and bring out an OTA/PCC update to JB, I guess there's no reason to worry about anything else in being bootloader locked, right? Especially if I can brick the thing by trying.
This is all very new to me (if I'd realized the limitations of the Tipo Dual and cm10, I would have bought the Tipo single!), but I hope to be able to play more with Android and with roms because of this excellent forum.
Thanks again,
Fred (no, not really)

RealFred2 said:
Thanks for responding to my question, I appreciate your help.
Do you think it's better then to just do something like flash this if I want to go back to stock:
http://forum.xda-developers.com/showthread.php?t=2270976&highlight=+tipo+dual+
and just forget trying to make it retail again? As long as Sony doesn't change and bring out an OTA/PCC update to JB, I guess there's no reason to worry about anything else in being bootloader locked, right? Especially if I can brick the thing by trying.
This is all very new to me (if I'd realized the limitations of the Tipo Dual and cm10, I would have bought the Tipo single!), but I hope to be able to play more with Android and with roms because of this excellent forum.
Thanks again,
Fred (no, not really)
Click to expand...
Click to collapse
If thats the firmware you want then by all means flash that bro. The nandroid backup from your wifes phone will be just the same. the backup will be on her sdcard in the file /clockworkmod/backups/ just copy it and paste it to your sdcard. restore it then flash the kernel.

There's an ftf file available im the forum to relock the bootloader.
Flash it in fastboot mode.
I myself have flashed it to relock the bootloader on my st21i2.
After that use pc companion to get your firmware.
I have relocked and then used pc companion without any problems using this method.
Should work for you too.
All the best.
Sent from my ST23i

c4cyro said:
There's an ftf file available im the forum to relock the bootloader.
Flash it in fastboot mode.
I myself have flashed it to relock the bootloader on my st21i2.
After that use pc companion to get your firmware.
I have relocked and then used pc companion without any problems using this method.
Should work for you too.
All the best.
Sent from my ST23i
Click to expand...
Click to collapse
Thanks, c4cyro; I managed to relock with flashtool (it had not worked when I had tried before, but suddenly it did); even so, I can't load from pc companion. Did you also unroot your phone? I've seen elsewhere that that can have something to do with it. I'd like to do this just because so far I haven't been able to (and I hate not being able to do stuff, even when I'm a noob).
Thanks again,
Fred

no i did not unroot. if sony pcc does not recognise your phone, you should try doing that on another system maybe.
to unroot you can use "unlockroot" program.
also, did you check this? http://forum.xda-developers.com/showthread.php?t=2001567

c4cyro said:
no i did not unroot. if sony pcc does not recognise your phone, you should try doing that on another system maybe.
to unroot you can use "unlockroot" program.
also, did you check this? http://forum.xda-developers.com/showthread.php?t=2001567
Click to expand...
Click to collapse
I wonder if it's because it's a Tipo Dual, and the firmware that Gimlo is based on for the Dual is the latest (11.0.A.6.8); even when it's locked and unrooted, pc companion just says it doesn't have any software for my phone. Really strange (and annoying). I might try loading an older firmware, locking everything up, and trying again. Or maybe I'll just reinstall Gimlo and see if I can get it to work the way I want it to!
Thanks again for your help, c4cyro,
Fred

RealFred2 said:
I wonder if it's because it's a Tipo Dual, and the firmware that Gimlo is based on for the Dual is the latest (11.0.A.6.8); even when it's locked and unrooted, pc companion just says it doesn't have any software for my phone. Really strange (and annoying). I might try loading an older firmware, locking everything up, and trying again. Or maybe I'll just reinstall Gimlo and see if I can get it to work the way I want it to!
Thanks again for your help, c4cyro,
Fred
Click to expand...
Click to collapse
maybe. does it recognise that it's a tipo or it just says that there's no software available?

c4cyro said:
maybe. does it recognise that it's a tipo or it just says that there's no software available?
Click to expand...
Click to collapse
It picks it up as Tipo Dual (listed as St21i2 instead of St21a2 bc the Gimlo .3 firmware -- which is the right one for the dual -- is the "i" version).
I've just found this firmware, which seems to be stock, so I'm going to try this:
1) try out this firmware (http://forum.xda-developers.com/showthread.php?t=2044944; 11.0.A.6.5 stock) and see what it is and how it works;
2) then install the base stock for the Tipo Dual for Gimlo (which for the dual is );
3) then install the Gimlo firmware and ROM, and see if I can get it to work the way I want (going mostly stock except for the loader, which I really like the one I'm using on Gimlo);
Will report back on how things turn out and what I end up sticking with!
Thanks again for your help, it's good to feel like I'm not hopping about on one foot on my own.
Fred

All the best!!

Bootloop on all custom ROMs (D2303)

Hey guys,
So I ve tried flashing CM 12.1 as well as 5.X AOSP mainly but also some 4.X versions and so far all of them gave me bootloops.
The steps that are necessary seem to vary depending on who you ask so i was a little confused with that, too.(BL is unlocked)
So what I did was :
1. Flash 18.0.C.1.13 FTF or 18.3.1.C.1.15 via EMMA or FTF as well
2. Update Bootloader via EMMA (tried not to do it for some version, too)
(Also rooted the stock rom after that couple times)
For CM 12.1
3. Flash CM recovery through fastboot with CMD
4.Install CM 12.1 and gapps through recovery. ( Did full wipes before and after and only after and before)
For AOSP
3. Flash boot (for one version also recovery), system and userdata (in this order) through fastboot with CMD.
(No wipes here.)
Always got bootloops after that (let them run for about 10 min)
I may have tried other variations too but those are the ones i can think of. Im not exactly sure how new the device is (used phone) since I ve read that there seems to be an issue with some newer models with the GPIO keys ( no clue what that is ).
I would be happy if anyone could actually confirm that the steps i took were right or wrong and if there are any solutions to it.
I m pretty much a noob and dont have any logs or anything but I can read through Tutorials and provide them if it helps (just link me to it)
Ps.: I have looked through the different topics on here but there is lot of varying information plus a lot of stuff that I simply do not understand so I d be glad if anyone could clarify this for me.:fingers-crossed:

SharxX8 said:
Hey guys,
So I ve tried flashing CM 12.1 as well as 5.X AOSP mainly but also some 4.X versions and so far all of them gave me bootloops.
The steps that are necessary seem to vary depending on who you ask so i was a little confused with that, too.(BL is unlocked)
So what I did was :
1. Flash 18.0.C.1.13 FTF or 18.3.1.C.1.15 via EMMA or FTF as well
2. Update Bootloader via EMMA (tried not to do it for some version, too)
(Also rooted the stock rom after that couple times)
For CM 12.1
3. Flash CM recovery through fastboot with CMD
4.Install CM 12.1 and gapps through recovery. ( Did full wipes before and after and only after and before)
For AOSP
3. Flash boot (for one version also recovery), system and userdata (in this order) through fastboot with CMD.
(No wipes here.)
Always got bootloops after that (let them run for about 10 min)
I may have tried other variations too but those are the ones i can think of. Im not exactly sure how new the device is (used phone) since I ve read that there seems to be an issue with some newer models with the GPIO keys ( no clue what that is ).
I would be happy if anyone could actually confirm that the steps i took were right or wrong and if there are any solutions to it.
I m pretty much a noob and dont have any logs or anything but I can read through Tutorials and provide them if it helps (just link me to it)
Ps.: I have looked through the different topics on here but there is lot of varying information plus a lot of stuff that I simply do not understand so I d be glad if anyone could clarify this for me.:fingers-crossed:
Click to expand...
Click to collapse
Looks all good to me, so it is strange you have bootloops.
I'm very curious on how this topic will end: https://talk.sonymobile.com/t5/Gene...lashing-FXP-AOSP-5-1-D2303/m-p/995182#U995182
Also: can somebody explain on how to get a log when the device is in bootloop? At present my phone works (because of other D2303 model?) but when I had bootloops "adb logcat" was constantly waiting for device...
I'm aware the adb process on the phone gets started early and should connect with the PC, but that didn't work with me at the time.
regards

TrickiePad said:
Looks all good to me, so it is strange you have bootloops.
I'm very curious on how this topic will end:
regards
Click to expand...
Click to collapse
galaxyfreak was kind enough to help me a littlle while trying to flash AOSP and even tho it did work eventually it was very unstable, laggy, and the sensors didnt work since apparently that was the file that caused the bootloop in the first place.
So in short it didnt work and as he said
galaxyfreak said:
I recommend sticking to stock till fix is found
Click to expand...
Click to collapse
Pretty sad but I guess thats the best for now.

TrickiePad said:
but when I had bootloops "adb logcat" was constantly waiting for device...
I'm aware the adb process on the phone gets started early and should connect with the PC, but that didn't work with me at the time.
Click to expand...
Click to collapse
For me it just took a while, so i guess at some time during the bootloop it wont be recognized. However this was for AOSP which i flashed through fastboot.
I tried to do the same for CM which was flashed thorugh recovery and it wasnt recognized by adb either.

Solution is coming soon.

galaxyfreak said:
Solution is coming soon.
Click to expand...
Click to collapse
Is this solution work also on aqua with old period ?

[Solved] (E6653) Can't update to marshmallow at all. Any hints?

Alright everyone, I'll just say I don't ever create a Q&A thread unless I've run out of options and unfortunately I have...
So my device never got an OTA and its the 22nd now so I've basically given up on that. As a result, I took matters into my own hands and unlocked the bootloader (which went fine).
FlashTool
Now the hard part is trying to use FlashTool to push an ftf file onto the device but unfortunately every time I try to use it every ftf file simply stalls after setting the max buffer size. Once it does this I have a look at the .flashtool\firmwares\prepared folder only to find a single .sin file there.
I have tried a number of things to try and get FlashTool to work including:
Using different USB Ports/Cables (I thought it might help lol.)
Using different ftf files
E6653_32.1.A.1.163_R4C_Australia_Generic
E6653_32.1.A.1.163_TH
E6653_Customized AU_1298-7277_32.1.A.1.163_R4C
Updating FlashTool to the latest (including patch)
Just pushing a single SIN item by excluding everything else
Fastboot AOSP
After FlashTool, I considered just using fastboot to push AOSP marshmallow to my phone using the following:
Code:
[FONT=Arial]fastboot flash boot boot.img[/FONT]
[FONT=Arial]fastboot flash system system.img[/FONT]
However, when I tried to push system.img it just stalled out on 'sending system.img' and never got beyond that.
Fastboot FTF
I have also tried extracting the core parts of the ftf file and using fastboot to push the .sin files onto the phone.. Didn't work =(
Sony Companion
I really should have started here but I didn't realise it was a thing until after unlocking my bootloader. But I have now tried the the Sony Companion method of updating the device but it won't work because 'contains modified sofwtare that cannot be updated'
Other stuff you need to know
More stuff you need to know:
FlashTool version: 0.9.19.10
Sony Z5 model: E6653
Bootloader status: ROOTED
Flashmode Driver: installed from FlashTool
Solved.
Installed flashtools and z5 driver on another pc and used flashtool to push firstly a Lollipop build onto the device. After confirmation of it working I put on the Marshmallow build and it booted up.
No Problems to report so far and working 100%. Only had to add another APN to get mobile data working.

Try reinstall Flashtools. Worked for me.

Haha yeah, I've tried that too but I'll give it another shot tonight just in case.

You can manually Flash the Marshmallow OTA Update file.Check out the guide here > http://rootmygalaxy.net/download-sony-xperia-z5-marshmallow-ftf-32-1-1-163-model-no-e6653/
Btw i haven't tried this method.

How can I root my flashed Sony Xperia XZ Premium ?

Hello everybody,
As you can see in the title I am searching to know how i can root my Sony Xperia XZ Premium G8141 47.1.A.12.34, that I have flashed thanks to this thread : https://forum.xda-developers.com/xz...shtool-0-9-t3736217/post75276892#post75276892
After Flashing the photo camera doesn't take pictures anymore (take green photos but video works) but I know that this is a DRM problem. I find a tutorial on XDAdevelopers that tell you how to root and fix the DRM on a Sony Xperia XZ Premium : https://forum.xda-developers.com/xz...hack-mod-sony-xperia-xz-premium-twrp-t3695171
I Checked first if my Sony was compatible with this tutorial, read everything before doing stupid things and all seams to be ok. I downloaded the XperiFix, installed it and put my device on fast boot mode before I launched the program. But after the rooting process, when my device was rebooted, the camera problem was still present and my device wasn't rooted too.
So I want to know if anyone have the same problem or know how to fix that or have an alternative solution. Is it the flash tool that I used that isn't compatible with the Xperifix software or something else ?

MashNuke said:
Hello everybody,
As you can see in the title I am searching to know how i can root my Sony Xperia XZ Premium G8141 47.1.A.12.34, that I have flashed thanks to this thread : https://forum.xda-developers.com/xz...shtool-0-9-t3736217/post75276892#post75276892
After Flashing the photo camera doesn't take pictures anymore (take green photos but video works) but I know that this is a DRM problem. I find a tutorial on XDAdevelopers that tell you how to root and fix the DRM on a Sony Xperia XZ Premium : https://forum.xda-developers.com/xz...hack-mod-sony-xperia-xz-premium-twrp-t3695171
I Checked first if my Sony was compatible with this tutorial, read everything before doing stupid things and all seams to be ok. I downloaded the XperiFix, installed it and put my device on fast boot mode before I launched the program. But after the rooting process, when my device was rebooted, the camera problem was still present and my device wasn't rooted too.
So I want to know if anyone have the same problem or know how to fix that or have an alternative solution. Is it the flash tool that I used that isn't compatible with the Xperifix software or something else ?
Click to expand...
Click to collapse
Well you unlocked your bootloader.
unlocking the bootloader will erase the TA partition which includes camera features (DRM), and now they are deleted along with whats left in TA partition.
now you can not go back to a natural device.
good news is if you follow the procedure properly on this link:
https://forum.xda-developers.com/xz...hack-mod-sony-xperia-xz-premium-twrp-t3695171
(2. Use XperiFIX to get what you want)
then you should get your DRM fix patch, read the thread carefully, youre gonna have to do it all over again as you lost TA partition which you can never get back now.
So go do procedure 1 + 2 carefully, you will get it fixed and you will also have a rooted phone
if its not working try to flash a previous version FW that supports xperifix im not sure the one you have is supported but most likely it is, then redo the process in the thread and see if it works out.
hit the thanks if I was a help

madshark2009 said:
Well you unlocked your bootloader.
unlocking the bootloader will erase the TA partition which includes camera features (DRM), and now they are deleted along with whats left in TA partition.
now you can not go back to a natural device.
good news is if you follow the procedure properly on this link:
https://forum.xda-developers.com/xz...hack-mod-sony-xperia-xz-premium-twrp-t3695171
(2. Use XperiFIX to get what you want)
then you should get your DRM fix patch, read the thread carefully, youre gonna have to do it all over again as you lost TA partition which you can never get back now.
So go do procedure 1 + 2 carefully, you will get it fixed and you will also have a rooted phone
if its not working try to flash a previous version FW that supports xperifix im not sure the one you have is supported but most likely it is, then redo the process in the thread and see if it works out.
hit the thanks if I was a help
Click to expand...
Click to collapse
Thanks for the help and for the very quick reply !
I'll try too flash a older version firmware for my device, but I didn't find links to download the right version for my actual firmware (G8141 47.1.A.12.34), so I want to no if it's a problem to take an other version (as exemple G8141 47.1.A.12.34 from XperiFirm) and flash it to my device ?

MashNuke said:
Thanks for the help and for the very quick reply !
I'll try too flash a older version firmware for my device, but I didn't find links to download the right version for my actual firmware (G8141 47.1.A.12.34), so I want to no if it's a problem to take an other version (as exemple G8141 47.1.A.12.34 from XperiFirm) and flash it to my device ?
Click to expand...
Click to collapse
i rechecked and i think the xperifix should work on any firmware so try it out
if you are unlocked just download the xperifix on that link and just run it as instructed and it should work
also check if you followed correctly:
https://www.youtube.com/watch?time_continue=8&v=XeYlIHnSuOM
also check if you installed the firmware that suits your device G1841/G1842 they are 2 different things
flash whats suited.
if that didnt work, you can download the firmware in the video using xperifirm and do the procedure again.
and to answer your question, i dont really understand you already have 47.1.A.12.34 why would you want to install it again? im not getting the question...

Issues getting Stock Android 10 installed (problems with Newflasher)

EDIT (2/5/2021):
Hmm, Newflasher just worked for me now and I'm not sure what could have changed between when I was having issues and when it worked. Other people have reported similar, transient issues with Newflasher where it works and then suddenly doesn't, and vice-versa.
I'll update this post if I'm able to isolate the issue from before.
ORIGNIAL POST:
Hello all,
I have a Xperia 5 ii ( XQ-AS62 ).
I've successfully unlocked the bootloader.
I have TWRP 3.4.0 installed, I followed this guide https://forum.xda-developers.com/t/guide-how-to-flash-twrp-on-the-xperia-5-ii.4188419/
I have no important data that needs to backed up. I'm free to wipe it (the data in system partition is corrupted anyway).
I would like to install stock Android 10 (or anything else, at this point).
I have downloaded the stock Android 10 firmware via XperiFirm 5.5.0.
The next step SHOULD be to download Newflasher, move 'newflasher.exe' into the folder containing the firmware (the folder containing the *.sin files), put my Xperia 5 ii into flash mode (hold volume down while plugging in USB-C cable), and run newflasher, at which point newflasher would flash any present *.sin files into the appropriate partitions.
I've attempted the above.
However, what I'm experiencing is that, when using Newflasher, I'm met with the error message:
No usb device with vid:0x0fce pid:0xb00b !
At which point the program exits.
This is not a unique problem, but I've not seen any actual solutions that I can use.
Threads on the topic (for other Xperia devices):
[Solved] - Full Wipe - Newsflasher -> no usb device vid:0x0fce pid:0xb00b
Hello, Device is rooted and BL is unlocked and on FW v47.2.A.10.45 Performed a wipe incl system and internal storage. (Dalvik/ART is included) Wanted to start over, and perform a full backup after this... I shouldn't have checked ''internal...
forum.xda-developers.com
No usb device with vid:0x0fce pid:0xb00b · Issue #5 · munjeni/newflasher
Hi there, I succsessfully downgraded using newflasher couple of days ago, then I accedentaly updated firmware (big fingers), so I tried downgrading again, but now I get ... Determining available fr...
github.com
https://www.reddit.com/r/SonyXperia/comments/i32207
https://www.reddit.com/r/SonyXperia/comments/887sk3
One of those threads mentions using Sony Emma. It looks like you need to be a Sony Partner to register to use that (is that true? Any of you used it before?)
My current system is borked (won't boot) so I don't think I can install/use Magisk.
Again, my goal is to get Android 10 (or anything else) installed.
I still am able to see the device when in fastboot, and TWRP seems fine, so there should be hope right?
I can confirm that my bootloader has remained unlocked.
Any suggestions?
Thanks much!

xperia companion should do the trick

flyl0 said:
xperia companion should do the trick
Click to expand...
Click to collapse
I managed to get Newflasher working but never found out why.
Would Xperia Companion still work even if there was no ROM on the device (such as if it were fully wiped)? When I tried to use Xperia Companion (before Newflasher ended up working for me) it didn't seem to recognize my device. I had no ROM loaded at the time (it was fully wiped).

could you upload the firmware please? Xperifirm doesn't have the old firmwares now
EDIT: NVM, i'm looking for the old firmware for the As52
EDIT: I found one.
I followed all instructions from the newflasher thread but my device keeps rebooting and now it says it cannot be trusted (corrupt). any advice?

barret95 said:
could you upload the firmware please? Xperifirm doesn't have the old firmwares now
EDIT: NVM, i'm looking for the old firmware for the As52
EDIT: I found one.
I followed all instructions from the newflasher thread but my device keeps rebooting and now it says it cannot be trusted (corrupt). any advice?
Click to expand...
Click to collapse
Are you still having issues? At one point, I got my own device into the state you described. I believe that when I got newflasher working (and again, I don't know why newflasher suddenly decided to work) I was able to flash the firmware and the phone booted with no issue. Is the newflasher tool telling you that it's flashing the images successfully?

barret95 said:
could you upload the firmware please? Xperifirm doesn't have the old firmwares now
EDIT: NVM, i'm looking for the old firmware for the As52
EDIT: I found one.
I followed all instructions from the newflasher thread but my device keeps rebooting and now it says it cannot be trusted (corrupt). any advice?
Click to expand...
Click to collapse
I want to downgrade to A10 since A11 is still too buggy. I have also AS52. Can you tell me where you find the firmware?

T3chDelicious said:
I want to downgrade to A10 since A11 is still too buggy. I have also AS52. Can you tell me where you find the firmware?
Click to expand...
Click to collapse
File on MEGA
mega.nz