Related
Is there a way to root my officialy updated to ICS, Xperia Mini(ST15i) without unlocking bootloader?(in order to downgrade etc...) I just want to root my xperia mini without messing up with the warranty....Any way to root it with locked bootloader? (4.1.B.0.431)
Thanks in advance
You have to downgrade to Gingerbread, root it and then upgrade to ICS using THIS tutorial.
There could be a different way: you should flash the 4.0.3 kernel (for example the Arc one), but I can't find the tutorial. Use the search button and see if you can find it
Feanor88 said:
You have to downgrade to Gingerbread, root it and then upgrade to ICS using THIS tutorial.
There could be a different way: you should flash the 4.0.3 kernel (for example the Arc one), but I can't find the tutorial. Use the search button and see if you can find it
Click to expand...
Click to collapse
downgrading needs unlocked bootloader... :/ i had bricked my mini some time ago because i tried to downgrade with locked... (( any other way?
Thanks
EDIT: flashing xperia arc's or Neo V's for example would brick my phone....wouldn't it? (and it also needs bootloader unlock...so i don't think i would do that... BUT thanks for your help mate
No, flashing a .ftf does NOT need an unlocked bootloader. You need to unlock it only if you want to flash a custom kernel, but for custom ROMs you can use flashtool.
Same for the 4.0.3 kernel. It's a stock kernel, so you can flash it via flashtool
It WILL end in bootloop, though. The tutorial says you can use DoomLord's root kit anyway, root the phone and then flash again the 4.0.4 kernel. But find it and read it carefully, cause I didn't try it and I can't assure you it will work.
I tried the first one I suggested, though, and my bootloader is locked!
Feanor88 said:
No, flashing a .ftf does NOT need an unlocked bootloader. You need to unlock it only if you want to flash a custom kernel, but for custom ROMs you can use flashtool.
Same for the 4.0.3 kernel. It's a stock kernel, so you can flash it via flashtool
It WILL end in bootloop, though. The tutorial says you can use DoomLord's root kit anyway, root the phone and then flash again the 4.0.4 kernel. But find it and read it carefully, cause I didn't try it and I can't assure you it will work.
I tried the first one I suggested, though, and my bootloader is locked!
Click to expand...
Click to collapse
man i have a problem...when i place my phone into flashmode (down key) it disconnects on its own...and that's why i bricked my phone long time ago....now i am afraid to do that i have installed the flashtool drivers from Flashtool/drivers.... but they mustn't work for my mini....any solution please give me the drivers you use for your Mini and work with it if you can i would really appreciate that!
What do you mean, it disconnects? How much time does it take for it to disconnect? Mine does the same. If I plug it and wait for a minute or so doing nothing, it disconnects. But if I start flashing a ROM it doesn't.
The drivers I installed are in \Flashtool\drivers.
Feanor88 said:
What do you mean, it disconnects? How much time does it take for it to disconnect? Mine does the same. If I plug it and wait for a minute or so doing nothing, it disconnects. But if I start flashing a ROM it doesn't.
The drivers I installed are in \Flashtool\drivers.
Click to expand...
Click to collapse
it takes about 1-2 minutes to disconnect.But, what if it disconnects while on downgrading?
It doesn't. At least, mine doesn't! And I flashed firmware twice a day in the last week
Anyway, both ways need the use of flashtool... so if you don't want to try it, you can't root ICS
Feanor88 said:
It doesn't. At least, mine doesn't! And I flashed firmware twice a day in the last week
Anyway, both ways need the use of flashtool... so if you don't want to try it, you can't root ICS
Click to expand...
Click to collapse
Pfff i'm a bit scared.....there is no hope that there will be somewhen another way to root...?
No, I'm sorry. Anyway, just follow this steps:
1) DON'T plug your phone.
2) Open flashtool
3) Click the lightning icon and select flashmode
4) Select the .ftf you want to flash: if you want to downgrade, select wipe data. If you want to flash the 4.0.3 kernel, unckeck wipe data and check "exclude" for everything apart from kernel. Which means you'll only flash the kernel
5) Start: you'll be asked to plug your phone. Plug it now in flashmode. This way you'll avoid it being unplugged.
Flashing will start, and your phone won't be unplugged. I suppose it's unplugged automatically when you're not doing anything, it's the same for me, but I repeat, whenever I flash something (kernel, whole ROM, whatever) everything just goes fine
Feanor88 said:
No, I'm sorry. Anyway, just follow this steps:
1) DON'T plug your phone.
2) Open flashtool
3) Click the lightning icon and select flashmode
4) Select the .ftf you want to flash: if you want to downgrade, select wipe data. If you want to flash the 4.0.3 kernel, unckeck wipe data and check "exclude" for everything apart from kernel. Which means you'll only flash the kernel
5) Start: you'll be asked to plug your phone. Plug it now in flashmode. This way you'll avoid it being unplugged.
Flashing will start, and your phone won't be unplugged. I suppose it's unplugged automatically when you're not doing anything, it's the same for me, but I repeat, whenever I flash something (kernel, whole ROM, whatever) everything just goes fine
Click to expand...
Click to collapse
i maybe try it later... thanks for your replies man DD i appreciate that
kwstas 13 said:
i maybe try it later... thanks for your replies man DD i appreciate that
Click to expand...
Click to collapse
Let me know if you need more help!
Feanor88 said:
Let me know if you need more help!
Click to expand...
Click to collapse
A friend of mine told me that if i try with locked bootloader is a simple suicide!!! :/ Now i am confused again :S
kwstas 13 said:
A friend of mine told me that if i try with locked bootloader is a simple suicide!!! :/ Now i am confused again :S
Click to expand...
Click to collapse
Who is that friend of you? He is trolling. Stay away from him. And learn this. Feanor here is a better friend for you than him, when it comes to rooting your phone.
Just do as in the tutorial Fenor had shared in his first post. Everything will be fine.
And you say you bricked your phone. May we know how your repaired it?
Thanks,
Rick
Sent from my SK17i using XDA
DragonClawsAreSharp said:
Feanor here is a better friend for you than him, when it comes to rooting your phone.
Click to expand...
Click to collapse
Blushing
But don't forget I'm a noob after all... I'll just keep pointing other people's tutorials, like for example yours, Rick
DragonClawsAreSharp said:
Who is that friend of you? He is trolling. Stay away from him. And learn this. Feanor here is a better friend for you than him, when it comes to rooting your phone.
Just do as in the tutorial Fenor had shared in his first post. Everything will be fine.
And you say you bricked your phone. May we know how your repaired it?
Thanks,
Rick
Sent from my SK17i using XDA
Click to expand...
Click to collapse
while i was downgrading with locked bootloader the procces stopped on its own at 43%....and my phone wouldn't turn on and didn't even worked with flashtool....i sent it to a service centre and they fixed it ( i think i hadn't installed the proper drivers....am i right?)
kwstas 13 said:
while i was downgrading with locked bootloader the procces stopped on its own at 43%....and my phone wouldn't turn on and didn't even worked with flashtool....i sent it to a service centre and they fixed it ( i think i hadn't installed the proper drivers....am i right?)
Click to expand...
Click to collapse
That's strange. Anyway, if you installed PC Companion you have adb drivers. Install flashmode drivers from Flashtool installazion folder, you find the executable in \Flashtool\drivers. If Windows prompts you that the drivers are dangerous, just install them anyway.
What I can say is that you DON'T need to unlock your bootloader to use flashmode in Flashtool. Otherwise, my phone would have exploded long ago
Now let me tell you this: if you are SURE you did everything the right way, and still your phone got bricked, then maybe you shouldn't try. you never know.
If you tried to to something you didn't know how to do, you probably made a mistake, and that's why the phone got bricked.In this case, I'd give it a try.
But we're not able to see your phone and test it, so whatever you do, unfortunately, you always do it on your own risk.
I couldn't be more sincere.
kwstas 13 said:
while i was downgrading with locked bootloader the procces stopped on its own at 43%....and my phone wouldn't turn on and didn't even worked with flashtool....i sent it to a service centre and they fixed it ( i think i hadn't installed the proper drivers....am i right?)
Click to expand...
Click to collapse
On all probability you are correct.
They (The service centre people) flashed a firmware using Flashtool. That's what they must have did. See. I will explain things a bit.
Your phone has some memory in it (this corresponds to what was known as phone memory in older phones). This memory is of Read Only type. That is ROM. Now, of all the types of ROMs, androids have EEPROM. That stands for Electronically Erasable Programmable ROM. So you can electronically erase the data stored in the ROM and write new data on it (even though it is called Read Only). This process of writing new data on the ROM is called flashing.
For flashing, the tool that is available to us as an open source, is Flashtool. Using it we can flash ROMs into our phones, erasing the earlier ones.
Now, Sony will not want us to flash Cyanogen Mod to our phones. So they have made up the concept of locking the bootloaders. With locked bootloaders custom ROMs can not be flashed to your phone. This is because most custom ROMs are designed for a specific Kernel (the intermediate between the OS and the hardware), and flashing a custom kernel requires unlocked bootloaders.
If you want, you can flash firmwares (ROMs + Kernels released by Sony) even if you are on locked bootloader, as long as the firmware files are signed by Sony.
This restriction however is against the OpenSource spirit of Android, and thus Sony gives us the scope to unlock bootloader at the cost of loosing the warranty, and the DRM keys (search google for that).
Now coming to your problem of unability to flash properly, make sure that you have installed all the drivers. For that open up /drivers folder in /flashtool and install the .exe there. Also install the adb drivers of your device. For that have PC Companion installed on your PC. Flashing will happen properly then.
Thanks,
Rick
Sent from my SK17i using XDA
DragonClawsAreSharp said:
On all probability you are correct.
They (The service centre people) flashed a firmware using Flashtool. That's what they must have did. See. I will explain things a bit.
Your phone has some memory in it (this corresponds to what was known as phone memory in older phones). This memory is of Read Only type. That is ROM. Now, of all the types of ROMs, androids have EEPROM. That stands for Electronically Erasable Programmable ROM. So you can electronically erase the data stored in the ROM and write new data on it (even though it is called Read Only). This process of writing new data on the ROM is called flashing.
For flashing, the tool that is available to us as an open source, is Flashtool. Using it we can flash ROMs into our phones, erasing the earlier ones.
Now, Sony will not want us to flash Cyanogen Mod to our phones. So they have made up the concept of locking the bootloaders. With locked bootloaders custom ROMs can not be flashed to your phone. This is because most custom ROMs are designed for a specific Kernel (the intermediate between the OS and the hardware), and flashing a custom kernel requires unlocked bootloaders.
If you want, you can flash firmwares (ROMs + Kernels released by Sony) even if you are on locked bootloader, as long as the firmware files are signed by Sony.
This restriction however is against the OpenSource spirit of Android, and thus Sony gives us the scope to unlock bootloader at the cost of loosing the warranty, and the DRM keys (search google for that).
Now coming to your problem of unability to flash properly, make sure that you have installed all the drivers. For that open up /drivers folder in /flashtool and install the .exe there. Also install the adb drivers of your device. For that have PC Companion installed on your PC. Flashing will happen properly then.
Thanks,
Rick
Sent from my SK17i using XDA
Click to expand...
Click to collapse
You, and all developers/people here, are simply awesome!.... But this sh*t with unlocking bootloader and loosing warranty is so....stupid....I think i will give it a try and i am gonna sure thank you.... Somethink else....my phone has also a problem on the screen while scrolling....do you know if that is a hardware or a firmware problem?
What do i mean when i say scroll problem:
1st example: While browsing the Internet and scroll with fast moves, links are pressed on its own and new tabs are opened,as links are pressed.
2nd example: While i scroll the app drawer,fast s make apps open without my will....
3nd exapmle and the most representative: While playing fruit ninja and do fast moves to cut the fruits, the touchscreen doesn't even fell that i touch the screen!!! I do fast moves to cut the fruits and nothing happens!! As a result i always lose! (just joking....)
My phone is fast and really smooth only when my moves are slow....any thoughts about that? :/
Thanks once again for your BRAVE help!
You have a Mini, right? That's a hardware problem. Very common, even if not everyone realizes it. Check THIS thread for a (possible?) solution.
Am not such a noob, I've been unlocking, flashing, rooting and messing with xdas since my first oldschool qtek ... but am going to ask totally noobish question, which has probably been answered many times and you'll probably hate me for doing so.
anyways...
after my xperia mini pro got smashed accidentaly, I've bought xperia sola today, I couldn't resisted and am just playin' with now...
am probably all about to unlock, flash, overclock and reinstall it, but I'm not going to trust sony completely, so I'm worried about things that got me in past like broken buttons, failing audio jacks etc etc. and for problems like those you're glad for your warranty, long story short, the noobish question is:
please, give me hint, link, short tutorial - which is best way to backup stock rom and state of the phone before unlocking and flashing another bootloader and roms?
for example, am I able to extract some .ftf image of rom or something like that? to be able completely revert all my activity on that phone in case I would have to let it repaired because of some hw issues? simply, which is the safest and best way to revert and fool the service guys if I would have to?
thanx a lot for any link, suggestion or kickstart...
4n60 said:
Am not such a noob, I've been unlocking, flashing, rooting and messing with xdas since my first oldschool qtek ... but am going to ask totally noobish question, which has probably been answered many times and you'll probably hate me for doing so.
anyways...
after my xperia mini pro got smashed accidentaly, I've bought xperia sola today, I couldn't resisted and am just playin' with now...
am probably all about to unlock, flash, overclock and reinstall it, but I'm not going to trust sony completely, so I'm worried about things that got me in past like broken buttons, failing audio jacks etc etc. and for problems like those you're glad for your warranty, long story short, the noobish question is:
please, give me hint, link, short tutorial - which is best way to backup stock rom and state of the phone before unlocking and flashing another bootloader and roms?
for example, am I able to extract some .ftf image of rom or something like that? to be able completely revert all my activity on that phone in case I would have to let it repaired because of some hw issues? simply, which is the safest and best way to revert and fool the service guys if I would have to?
thanx a lot for any link, suggestion or kickstart...
Click to expand...
Click to collapse
you will need... download these things
1) flashtool
2) stock ftf ICS (from dev section)
3) stock ftf GB (may be needed)
just keep these things handy whenever doing anything.....
for everything else read the stickies in this section itself........
@[email protected] said:
you will need... download these things
1) flashtool
2) stock ftf ICS (from dev section)
3) stock ftf GB (may be needed)
just keep these things handy whenever doing anything.....
for everything else read the stickies in this section itself........
Click to expand...
Click to collapse
so, flashing some stock ftf roms and then maybe update via companion or something like that must be sastifying and enough.
anything I might mess up and change via flashtool etc might be reflashed back to locked and stock via ftf...
so, its safe then, if I can revert. thanx...
and any way how to get ftf from stock rom I bought it with? or its too difficult and flashing stock roms from dev section and updating after is enough?
Hi, noobs are welcome! Or half-noobs or whatever...
OK so the official story from Sony is that if you root or unlock the bootloader, they will know and they are not obliged to accept your warranty. However, I've good news, if you return your phone to stock, for example using PC Companion or Update Service (with locked bootloader, or it will brick) then they are unlikely to refuse warranty - in fact, I've never heard of Sony refusing becuase of root.
Even better, many users here who unlocked their bootloaders have sent away for repair and their phone was repaired under warranty, with no cost! That's really good news! :victory:
4n60 said:
so, flashing some stock ftf roms and then maybe update via companion or something like that must be sastifying and enough.
anything I might mess up and change via flashtool etc might be reflashed back to locked and stock via ftf...
so, its safe then, if I can revert. thanx...
and any way how to get ftf from stock rom I bought it with? or its too difficult and flashing stock roms from dev section and updating after is enough?
Click to expand...
Click to collapse
to backup the rom u got with ur fone perform these steps:
1. You need to reinstall the firmware using SUS (Sony Update Service )
2. After completing go to C:\Program Files\Sony Mobile\Update Service\db\13740270\blob_fs\
3. Copy 2 files One of 15 mb and other around +- 200/300 MB into a New folder
4. Run FlashTool > Tools > Decrypt Files
5. Source folder : New folder that you created
6. From Files, Select both of the files and select OK
7. Wait till the decrypting finishes , after it does, a list will appear on the left
8. From Folder list, select all and move everything to the right
9. Fill all the details in the box
10. If the firmware that you are backing up is ICS then mark Disable Final Verification Check and select OK
11. Select your device > Ok
12. You will see the backed up firmware in > C: > flashtool > firmwares
[update 2] I just summarized a way to backup and restore (all based on other great DEV's work, just put in one place) your TS before your play with your TS here: http://forum.xda-developers.com/showthread.php?p=52820278#post52820278
Go check it if you plan to root your TS!
[update] With the help of cheahcl, I got the latest F/W for 4th List 1/8/2100. With the MTK SP_Flash_Tool, I was able to upload a corrected F/W for my TS and everything goes back to normal!
Thanks for cheahcl for his dump and Lokifish Marz for his All in one tools! You guys really saved my day! (and my TS).
A Quick summary: Do NOT use any method on XDA yet to root or change TWRP recovery! It seems the TS of 4th list is different in some way than the ones before which render most of stuffs here invalid. However, fear not to play around since now we have a way to go back to stock!
In my experience, I found that it's really difficult to truly brick a MTK based system. The system will just reject flashing at slightest sign that a F/W is not compatible. The only cache is you need to have the "correct" F/W specifically for your TS!
In my observation, OMate made changes between each delivery. For Example, the 4th list of 1/8/2100 is different in (At least F/W configuration) of the 3rd or earlier 1/8/2100.
------------------------below is my original story of what I tried and failed--------------------------
Just got mine (1/8/2100) 5 hrs ago! I am on the 4th list. The delivery in FAST!
The watch starts normally. I played with it for a while, than decided to root it, install TWRP and apply the security hack made by +Lokifish Marz
Now I have a brick! Just after 30 min I receive the watch!
<<Can anyone help me here?>>
First of all, in respecting to all great DEVs, I have NO intention to blame anyone else but myself. (I did this to my own watch!)
Second, I have been rooting Android since Cupcake day, so I am not a Noob... (or so I think...) I am very familiar with ADB/fastboot... and use almost daily.
So here is the guide to brick. If Anyone have any idea please help me out!
--------------------------------------------------------------------------------------------------
1st, I tried to use this tool to root+TWRP+scurity patch http://forum.xda-developers.com/showthread.php?t=2713183&page=2 knowing it's NOT tested against 1/8/2100. I just tried anyway... The script went with a lot of errors, it seems the script cannot locate correct files but still push the security patched files into the /system/app (and other places).
I turn on the watch, but it just stuck at boot logo (the orange "Truesmart" logo without animation)
Also, the Recovery is still stock, TWRP is no where to be seen.
Since ADB still works, I adb reboot couple times, pull the battery, let the watch run for 2hrs, etc... Nothing works. The watch just stuck at the boot logo.
Than I follow this thread http://forum.xda-developers.com/showthread.php?t=2641261 and http://forum.xda-developers.com/showthread.php?t=2641261 with Stock firmware downloaded from http://d-h.st/users/Lokifish Marz/?fld_id=30814#files (Omate_1-8_2100_TrueSmart_20140328.zip)
I installed all drivers, restarts my Win 7 (x86) pc (several times), and after several attempts the Flashtool just flash in the Firmware.
The Tools flash with a green Check mark, indicating everything is ok!
However the watch just become a brick after this....
Than this completed the brick process! Now the watch won't even turn on, when I try to use Flash tool again, it always say S_FT_ENABLE_DRAM_FAIL. Google this and you find it's due to flashing wrong F/W, but I don't know where went wrong!
Anyone else have same problem or it's just me? Anyone have solution?
You said everything...
You made mistake but that shouldn't be problem.
You soft brick it using wrong recovery image and root tool but as you said, you had adb and fastboot on - so if you know what are you doing and I see you know (except of that pary of flashing something that's not for your device .) you should be able to flash stock firmware back.
If you can flash another firmware, try with other firmware...
Don't know what else to say....
Omate build piece of sh*t and we'll all have problems with it...
It's very hard to differentiate devices.
All of them has same nr on mother boards and, as I said, we will all have problems with Omate and their TrueSh*t...
Sent from my C6903 using Tapatalk
funky0308 said:
You said everything...
You made mistake but that shouldn't be problem.
You soft brick it using wrong recovery image and root tool but as you said, you had adb and fastboot on - so if you know what are you doing and I see you know (except of that pary of flashing something that's not for your device .) you should be able to flash stock firmware back.
If you can flash another firmware, try with other firmware...
Don't know what else to say....
Omate build piece of sh*t and we'll all have problems with it...
It's very hard to differentiate devices.
All of them has same nr on mother boards and, as I said, we will all have problems with Omate and their TrueSh*t...
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
Ha! Very true! I think you are right! I believe Omate have many segmentation on their HW/SW, even with same model number.... A lot of things changes between versions which makes the "factory image" not compatible....
Anyone has the latest (4th list) 1/8/2100 TS who could dump their whole image for me would be helpful...
I would like to help you but mine is 2nd list and it's still on customs office...
Omate shipment experts, you just gotta love them....
Sent from my C6903 using Tapatalk
Not sure what to tell you on this. A board revision change is possible as the Omate_1-8_2100_TrueSmart_20140328.zip was from a 1/8 2100. I can't even test stuff anymore as I gave one to a tech student that's studying network and system security and the other four were stripped down, reworked into data gathering modules and then donated to near space projects.
Lokifish Marz said:
Not sure what to tell you on this. A board revision change is possible as the Omate_1-8_2100_TrueSmart_20140328.zip was from a 1/8 2100. I can't even test stuff anymore as I gave one to a tech student that's studying network and system security and the other four were stripped down, reworked into data gathering modules and then donated to near space projects.
Click to expand...
Click to collapse
Thanks Lokifish for your comment... Is there anyway to get a latest F/W? If you know anyone I could contact, please PM me... Thanks!
Anyone have yet received a 1/8/2100 on 4th list could PM me a Factory F/W dump?
I tried another XP PC with all steps checked and rechecked but still... No luck...
Teach me how to do a dump and I'll dump it for you. I was also looking how to backup my stock firmware before playing around, seeing as no one has our version of firmware uploaded for restore yet.
Also received mine yesterday and firmware version is 20140513, pretty damn recent.
You guys are going to have to help each other out on this one. I've already deleted 90% of any and all Android dev stuff from my personal file server and computer. This includes tools, guides and work going as far back as the original HTC Evo.
cheahcl said:
Teach me how to do a dump and I'll dump it for you. I was also looking how to backup my stock firmware before playing around, seeing as no one has our version of firmware uploaded for restore yet.
Also received mine yesterday and firmware version is 20140513, pretty damn recent.
Click to expand...
Click to collapse
Thanks a lot! First of all, Currently don't do anything posted on XDA yet since most of them will not work with this version of TS... (This is where I am now...)
First of all, please get all necessary tools directly from this post "All Tools" http://forum.xda-developers.com/showthread.php?t=2734687 (Do NOT download or install any other things there!)
Follow those steps: (modified from link above)
1. Download "All Tools"
2. Install Universal ADB Drivers (included in All Tools) <--If you already have ADB up and running, it's not necessarily, then.
3. Enable USB Debugging on watch
4. Launch MTKDroid Tools
5. Connect watch to PC
6. Please follow the instruction from here: http://www.chinaphonearena.com/foru...up-MTK6592-MTK6589-MTK6577-and-all-MTK-Phones
a. Skip everything above and just starts from "B) Open ADB prompt to begin communication with the phone" .
b. Don't worry about the recovery thing... TS comes with a recovery which is not locked and you can do everything this article said with only stock recovery. (also no busy box is needed, nor su since TS run everything in root!)
c. You could also refer to the video guide below for details
7. it's okay to just provide the file you got after finishing the step "C) Read back the ROM with MTK Droid Tools" I should be able to do the Step D) and after myself.
Thanks a lot for your help!
Lokifish Marz said:
You guys are going to have to help each other out on this one. I've already deleted 90% of any and all Android dev stuff from my personal file server and computer. This includes tools, guides and work going as far back as the original HTC Evo.
Click to expand...
Click to collapse
Dear Lokifish,
Could you please still keep those tools on the host servers so people can still access them? (Like "All tools", etc.) Please...... (I need a emoticon of a small kitten with big eyes here...)
Thanks!
ok will get it to tonight. about 6 hours time. cheers
lssong99 said:
Dear Lokifish,
Could you please still keep those tools on the host servers so people can still access them? (Like "All tools", etc.) Please...... (I need a emoticon of a small kitten with big eyes here...)
Thanks!
Click to expand...
Click to collapse
The space was given to me for free as a recognized developer and contributor. Seeing that I have left development completely, it is not right that I continue to use the services. So at the end of the week the files will be purged and I will ask the xda remove my developer and contributor status.
Lokifish Marz said:
The space was given to me for free as a recognized developer and contributor. Seeing that I have left development completely, it is not right that I continue to use the services. So at the end of the week the files will be purged and I will ask the xda remove my developer and contributor status.
Click to expand...
Click to collapse
Oh! I see the situation... In this case, may I have your permission to host those files somewhere (maybe by XDA moderator, or ...me?) so they could still be accessible?
I could feel your feeling on this fiasco. Must be quite frustrate experiences for you...
lssong99 said:
Oh! I see the situation... In this case, may I have your permission to host those files somewhere (maybe by XDA moderator, or ...me?) so they could still be accessible?
I could feel your feeling on this fiasco. Must be quite frustrate experiences for you...
Click to expand...
Click to collapse
https://dl.dropboxusercontent.com/u/25414599/!Files_to_FlashTool.rar
I've done step D as well, good to just flash it I guess.
Let me know if it worked, before I start messing about. I'm not good in all these stuff. Been flashing since HD2 days but still, just a tutorial follower, can probably count Linux commands I know with 1 hand.
cheahcl said:
https://dl.dropboxusercontent.com/u/25414599/!Files_to_FlashTool.rar
I've done step D as well, good to just flash it I guess.
Let me know if it worked, before I start messing about. I'm not good in all these stuff. Been flashing since HD2 days but still, just a tutorial follower, can probably count Linux commands I know with 1 hand.
Click to expand...
Click to collapse
Dear cheahcl,
Thank you soooo much for the image! I successfully restored my TS and now EVERYTHING GOES BACK TO NORMAL!
If you want to play around, please don't forge to back up your IMEI! since the MTK SP_Flash_Tool will wipe your IMEI!
Please follow this guide here: http://forum.xda-developers.com/showthread.php?t=2631953 under "IMEI Backup Procedure" before proceed anything dangerous!
After this, you are good to go! MTK is non-brickable (from what I learned for the past day... All you need is a corrected factory F/W!)
Thank you! Thank you! Thank you! Thank you! Thank you! Thank you!!
lssong99 said:
Dear cheahcl,
Thank you soooo much for the image! I successfully restored my TS and now EVERYTHING GOES BACK TO NORMAL!
If you want to play around, please don't forge to back up your IMEI! since the MTK SP_Flash_Tool will wipe your IMEI!
Please follow this guide here: http://forum.xda-developers.com/showthread.php?t=2631953 under "IMEI Backup Procedure" before proceed anything dangerous!
After this, you are good to go! MTK is non-brickable (from what I learned for the past day... All you need is a corrected factory F/W!)
Thank you! Thank you! Thank you! Thank you! Thank you! Thank you!!
Click to expand...
Click to collapse
don't sweat it, haha i needed to backup my original firmware as well anyways, seeing how scarce it is around here and all the weird discrepancies in HW/SW versions. good to know i can always fall back on this file. haha yeah i've also backed up my imei. time to play around and see.
cheers
Ive managed to get my brand new watch stuck in a bootloop after using framaRoot to root it. (I know, I know)
Now, I am able to boot into recovery mode or factory, and tried a factory reset. No luck, so i'm pretty sure the issue is in the /system partition.
Does anyone know if there are zip files somewhere that i can flash from recovery, to restore the system partition?
Device:
- 1GB / 8GB / 2100MHz Version
- Originally unrooted
- OUI 2.1
- Modem Ver: MOLY.WR8.W1315.MD.WG.MP.V4, 2013/08/14 18:16
- No other modifications besides the rooting (which did work already before I rebooted)
Spoetnicus said:
Ive managed to get my brand new watch stuck in a bootloop after using framaRoot to root it. (I know, I know)
Now, I am able to boot into recovery mode or factory, and tried a factory reset. No luck, so i'm pretty sure the issue is in the /system partition.
Does anyone know if there are zip files somewhere that i can flash from recovery, to restore the system partition?
Device:
- 1GB / 8GB / 2100MHz Version
- Originally unrooted
- OUI 2.1
- Modem Ver: MOLY.WR8.W1315.MD.WG.MP.V4, 2013/08/14 18:16
- No other modifications besides the rooting (which did work already before I rebooted)
Click to expand...
Click to collapse
The TS (or any MTK based system) does not use the usually "recovery backup/restore" way we familiar of, instead it goes the "special tool on PC backup/restore" method. You need ask people who receive their watch in around the same time as yours with same configuration to backup their watch FW with MTK tools than restore with said FW.
Basically what I had done in this thread!
Please follow my another guild to see how to do this...
http://forum.xda-developers.com/showthread.php?t=2758733
Sent from my HTC_One_max using XDA Premium HD app
lssong99 said:
The TS (or any MTK based system) does not use the usually "recovery backup/restore" way we familiar of, instead it goes the "special tool on PC backup/restore" method. You need ask people who receive their watch in around the same time as yours with same configuration to backup their watch FW with MTK tools than restore with said FW.
Basically what I had done in this thread!
Please follow my another guild to see how to do this...
http://forum.xda-developers.com/showthread.php?t=2758733
Sent from my HTC_One_max using XDA Premium HD app
Click to expand...
Click to collapse
Thanks!
Im pretty sure that I was on 'Omate_TrueSmart_20140513.103530_V2.0' before I bricked it, so that gives hope
I dont have it with me right now, but Ill try it as soon as I get back home on monday
Thanks again for the tutorials and reply
lssong99 said:
Please follow my another guild to see how to do this...
http://forum.xda-developers.com/showthread.php?t=2758733
Click to expand...
Click to collapse
HEY! It worked
I'm back at a functional Truesmart
Thank you soo much
And in case three smiley's aren't enough:
Also, quick note for other people bricking their phone, my issue (after I bricked it again), was that I used an app to change the density property, which broke the boot of the watch.
The app that broke my watch was: https://play.google.com/store/apps/details?id=com.birdapi.android.dpi
First off, hello everyone!
I've been reading the Forums for the past couple 3 days amounting to something around 9 hours total and finally signed up to ask some stuff!
I am, not a big surprise, completely new to everything related flashing, rooting and so on but thanks to this place I learned in 3 hours probably more than in a whole week back then in comp-sci classes at my university, thanks for that!
I have an old Xperia Z2 (D6503) to play with which, if bricked, wouldn't be a huge loss so I used it as my play and test ground... well what do you know, after about 3 hours of playing around I finally managed to (at least I think) kill the bootloader...
After another couple hours I fixed various problems (like actually fixing the bootloader and other errors like "failed do mount /system" ) on my own (thanks to guides), however I am now kinda "stuck".
The thing is, at current state, after a full wipe, my phone has, obviously, no OS, so I am trying to flash an original Firmware on it.
At first I googled a couple different .ftf's and tried them, only to be greeted with the "could not find META-INF/com/google/android/update-binary", a quick search told me that those are "update" .ftf which don't contain a complete ROM.
Alright, I keep searching for more .ftf files but no matter what, not a single one of them has said folder inside the META-INF when I check the contents of the zip, so I decide to use the Flashtool to download the newest available Firmware for my device, surely that will net me a fully working ROM.
For that I am using Flashtool 0.9.23.1, I successfully downloaded the newest official Firmware through XperiFirm but as soon as I select all files (except the handfull .ta files) and hit "create", the entire thing just freezes on me, leaving me without a .ftf file to flash on my phone so it has a proper OS again.
While the reason for the freeze might as well go as deep as a ****ty AMD VGA driver, is there a different way to create/obtain a FULL ROM? While it is fun and all experimenting, I am kind of losing hope and motivation after 3 days of no success...
Hope someone can help me out and thanks in advance!
EDIT: WELL, what do you know, I finally found an actual ROM (albeit a prerooted one) and was able to flash it properly, problem solved! I will maybe enhance this post as a kind of "guide" for future idiots like me who need a special case of handholding to not destroy their own device... but as always, learning by doing
Gibgub said:
First off, hello everyone!
I've been reading the Forums for the past couple 3 days amounting to something around 9 hours total and finally signed up to ask some stuff!
I am, not a big surprise, completely new to everything related flashing, rooting and so on but thanks to this place I learned in 3 hours probably more than in a whole week back then in comp-sci classes at my university, thanks for that!
I have an old Xperia Z2 (D6503) to play with which, if bricked, wouldn't be a huge loss so I used it as my play and test ground... well what do you know, after about 3 hours of playing around I finally managed to (at least I think) kill the bootloader...
After another couple hours I fixed various problems (like actually fixing the bootloader and other errors like "failed do mount /system" ) on my own (thanks to guides), however I am now kinda "stuck".
The thing is, at current state, after a full wipe, my phone has, obviously, no OS, so I am trying to flash an original Firmware on it.
At first I googled a couple different .ftf's and tried them, only to be greeted with the "could not find META-INF/com/google/android/update-binary", a quick search told me that those are "update" .ftf which don't contain a complete ROM.
Alright, I keep searching for more .ftf files but no matter what, not a single one of them has said folder inside the META-INF when I check the contents of the zip, so I decide to use the Flashtool to download the newest available Firmware for my device, surely that will net me a fully working ROM.
For that I am using Flashtool 0.9.23.1, I successfully downloaded the newest official Firmware through XperiFirm but as soon as I select all files (except the handfull .ta files) and hit "create", the entire thing just freezes on me, leaving me without a .ftf file to flash on my phone so it has a proper OS again.
While the reason for the freeze might as well go as deep as a ****ty AMD VGA driver, is there a different way to create/obtain a FULL ROM? While it is fun and all experimenting, I am kind of losing hope and motivation after 3 days of no success...
Hope someone can help me out and thanks in advance!
Click to expand...
Click to collapse
There is no need to create an ftf file your self just download an ftf file and flash it using flashtools
Thats it now you have working phone again
And another thing is that you cannot flash ftf files using recovery
raminta said:
There is no need to create an ftf file your self just download an ftf file and flash it using flashtools
Thats it now you have working phone again
Click to expand...
Click to collapse
I know, the thing is, that I couldn't find a simple ftf file that was a COMPLETE ROM and not just an update but as I wrote in my first post after editing it, I finally found one (after about 2 hours of spamming google)
raminta said:
And another thing is that you cannot flash ftf files using recovery
Click to expand...
Click to collapse
Obviously, I was trying with zips the entire time, which didn't contain the needed META-INF stuff
Hello everyone.
This is my first post here - in hope to get help with my Sony Z5 Compact.
So a week ago I have updated to Nougat,by mistake tbh.
Unfortunately Im really not happy with the device. The volume is OK unless youd like to watch some videos on a website - you won't hear much.
Then, playing a matroska file is impossible - stutters, pauses, gives you 5 fps ( I'm not joking) - it was flawless on MM (305).
So my plan is to go back to MM and I believe I've read every step by step tutorial existing on the Internet but I still have some questions.
1. How do I backup firmware? Every tutorial says about a folder with firmware files that you can import to flashtool to make an ftf backup of your stock firmware. The folder does not exist on my PC.
I've tried "repairing" etc, still, it does not exist.
2. Why do I need a backup firmware ftf for warranty?
3. Where can I find an ftf file?
Xperifirm doesn't give me anything, there are lots of fake websites, xperiablog doesn't send me an approval email for my account.
4. Is there anyone in Lodz, Poland that could help me?
I'd love to downgrade.. The phone is unusable for my work and I can't afford a new one.
Thanks in advance.
Kindest regards.
Michelangelo
Suggest you download Customized SG firmware, the lastest marshmellow is still available for download. Grab it now.
Hello, welcome to xda.
First, please do not open 2 different threads for the same problem - it's against forum rules.
About your problem: which fw you are on? you could try newest nougat firmware .33 first because the problems you described should've been fixed in this. Also you could dirty flash it and won't lose anything.
However if you want to go back to MM anyway, i would recommend 5.11 fw because it's .305 with newer security patch.
Be aware, that if you go back to MM, you will have to make a clean flash.
You can find all 3 firmwares on xperifirm from different regions(also .305). For most regions there are two different available, so click through all firmwares and look on the right side which you can choose.
What do you mean xperifirm gave you nothing?
How to download via xperifirm, create a ftf and flash viaflashtool: https://forum.xda-developers.com/z5...-33-pushed-t3581352/post71662820#post71662820
yup every update sony become worse
the best one was the last 5.1.1 i think (or one b4)
the last 6MM was meh
the last nougat (.33) is far worse from all of them
probably i won't buy sony's anymore
( i was happy with my WT19 sony ericsson arc like(Legacy Xperia) the one of the reasons i bought this sony(also easy roms flash,you just need use flash tool for stock roms you dont even need root or BTunlocked)
anyway i'm usually replace my phone every 5 years in average (when the phone stop run smooth mid-low range .like waze, temple run 2,subway surfer. apps (z5 still mid-high)
so the phones got about 4 more years, at least how i see it.
As Gewiz suggested, if you're on .376 or .378 version of the Nougat firmware, then updating to 2.33 might just fix the problems you're describing.
This is the highly recommended solution, since you won't lose any of your data or settings, and you don't really have to do anything, just wait for the update to become available for your region via OTA or Xperia Companion.
If you insist on downgrading back to MM, then you must perform a clean flash using unofficial (non-Sony) tools, which means you will lose all of your data and settings. Therefore you should backup all your data before doing so.
Being on anything but the latest version means you will forever have a non-dismissible notification nagging you about upgrading to the newest version.
If you're fine with that, then download a MM ROM from XperiFirm, create a FTF from the bundle, then flash it to your phone using Flashtool.
I think you're confused by the numerous tutorials you've read about "backups" and "warranty". You've likely read guides teaching you how to root your phone, which involves making a backup of the TA partition of your phone to preserve the DRM keys that resides within. Rooting the Z5C requires unlocking the bootloader, a process that wipes the DRM keys and voids your warranty. So, guides are there to help people make a backup of the DRM keys, so that they will have the ability to restore the keys to the phone and return the phone to warranty-eligible state when they need warranty service or resell their phone.
Since you have made no mention of rooting your phone, I assume none of this matters to you, don't worry about it.
Thank you all for the replies.
I updated from 376 to 2.33 and the phone is even more pathetic. It's slow and sluggish even with stamina mode off and data transfer/WiFi off. The battery drain is even bigger, now the alarm volume is terrible ( although video volume in chrome browser is now better). Mind you, I always do a reset after updating the phone, so everything that could be done was done.
I'm after 305 since the 5.11 introduced heating an worse performance ( I don't believe it was just a security patch).
I've managed to download 305 firmware with Xperifirm but I've hit one obstacle - I cannot create an FTF file with flashtool as the Xperifirm download unpacks the " FILE" files to many separate files and folders after download.
Could anyone please tell me how should I go about it? I'm really desperate to downgrade this phone as it was perfect until the cursed update and I can afford a new one.
Thanks in advance, and again thanks for all the replies.
MichelangeloJan said:
Thank you all for the replies.
I cannot create an FTF file with flashtool as the Xperifirm download unpacks the " FILE" files to many separate files and folders after download.
Click to expand...
Click to collapse
First: for nougat (7.0) you need flashtool in version v0.9.23.2
version 0.9.23.1 _cannot_ create ftfs out of what you downloaded with xperifirm
Second: here's a tutorial for FTFs:
http://www.xperiablog.net/2014/08/1...re-files-using-xperifirm-and-flashtool-guide/
Please note: in flashtool, you just have to click "Bundles\Create" (you don't need to decrypt, as this is done by xperifirm already)
Ok, guys I have one last question regarding this topic. Im sorry this took me so long but I don't have the Internet connection at home.
The "how to create an FTF file" tutorial says " exclude . Ta files" although the screen from it show only 2 files being excluded.
Some other tutorials either say the same or don't mention the .ta files.
So should I exclude all of them? Or should I leave "simlock. Ta" and "booter" in there?
Thanks again.
Michelangelo
Reflash firmware or make a factory reset. I am on .33 Nougat and rooted. Don't have any issues. Only have Greenify and battery life is good, performance is very good.
I also have flashed Zach's kernel, it makes a difference. However, these issues you have are not from this. Some people have reported such issues when upgrading from MM. If you don't want to unlock bootloader and root, make a factory reset or flash a whole .33 FTF in Flashtool. Also no, I haven't had these issues on .376 either.
I hope one of my tips helps you
---------- Post added at 01:15 AM ---------- Previous post was at 01:12 AM ----------
MichelangeloJan said:
Ok, guys I have one last question regarding this topic. Im sorry this took me so long but I don't have the Internet connection at home.
The "how to create an FTF file" tutorial says " exclude . Ta files" although the screen from it show only 2 files being excluded.
Some other tutorials either say the same or don't mention the .ta files.
So should I exclude all of them? Or should I leave "simlock. Ta" and "booter" in there?
Thanks again.
Michelangelo
Click to expand...
Click to collapse
Don't exclude anything, leave it as is
If you ask me, make a backup of all the stuff of your Internal Storage and wipe Userdata as well (unlocking the bootloader also does this, if you decide to do so).