Hi everybody welcome to my tutorial about Flashing with Flashtool. This thread is for those who want to reflash their device back to Sony Stock. See below for last details about this thread and the last build by Sony.
Note: I DO NOT OWN THIS DEVICE ANYMORE. PICTURES ARE REMOVED FROM MY DROPBOX AND THUS NOT VISEBLE. FOR NOW JUST RELY ON THE EXPLANATION PLEASE. ANY QUESTION CAN BE ASKED HERE. I DO NOT RESPOND TO TECHMAIL!
Created: 23-02-2014
Updated: 05-07-2014
Latest Android build released by Sony: 12.1.A.1.205
Let's begin shall we.. We shall!
First you need to download the correct ftf file for your device/operator or needs. This can be done here: http://forum.xda-developers.com/showthread.php?t=2311964 In there you can share and download firmware files in .ftf format..
You alsol need a program called Flashtool. You can download this here: http://forum.xda-developers.com/showthread.php?t=920746
For Windows 8 and 8.1 users I also recommend you to read this thread: http://forum.xda-developers.com/showthread.php?t=2095087 Microsoft has enhanced the security in Windows 8/8.1 and Windows won't install proper signed drivers.
When you are done with that you need to move your downloaded firmware file to the proper location for flashtool to be found:
C:\Flashtool\Firmwares
After that you are good to go, just remember the following:
Bootloader locked? If not you wont have BE2/OTA/PCC etc (for unlocking and relocking: http://forum.xda-developers.com/showthread.php?t=2354721 )
I've made backups of my important files that are stored on my phone?
Battery at atleast 50%?
I have patience?
I got something to do meanwhile?
The last two things are very important
Let's get started:
1: Open Flashtool:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Flashtool(.exe) for 32Bits systems and Flashtool64(.exe) for 64Bits systems
2: Press the Lightningbolt picture and select Flashmode
This will give another screen.
3: Select the downloaded ftf. (In this case 2.254)
Make sure that all the wipes are checked and the others are unchecked. This is to prevent any bootloops or other problems after downgrading.
4: Press Flash and the next two lines will be added to the flashtool log
The files are being prepared and checked. Have a bit of patience please.
5: Turn off your phone and turn it back on into Flashmode
After this the process will start.
After flashing you can disconnect your phone and boot it up.
Via Flashtool you can also reset your system after. For example:
You are running the latest ExistenZe ROM from our beloved Niaboc79 and you want to go back to stock for a reason WITHOUT losing data! Just flash the last Stock ROM and untick the following boxes:
Untick DATA and APPSLOG!! But keep CACHE to wipe the /cache (is the same as a wipe cache via CWM).
FAQ
- My Phone wont stay into flashmode
> Turn it off, wait a few minutes and turn it back into flashmode
- Flashtool wont recognise my phone
> Make sure you have the proper drivers installed. See C://Flashtool/Drivers
- Flashing failed
> Problem depends on the error code given by Flashtool. Post the problem here and perhaps we can help
- Got a bootloop
> Reflash again
- Even after reflash I got into a bootloop
> Turn off your phone via the small button behind the batterycover and wait a few minutes. Then try again. If that doesnt work you need to flash again.
- Booting takes ages
> This is normal. The entire cache needs to be rebuild. Patience my dear..
- After flashing and booting my phone is laggy.
> Reboot device and wait a bit. The phone needs to fully reset and boot itself. Have some patience dear.
- Do I need to unlock my bootloader to use flashtool
> NO!
- Can I unlock my bootloader with flashtool?
> NO!
- Can I relock my bootloader with flashtool?
> Yes
> Reserved by me
downgrade to root?
first, thanks! Very nice guide. I'm new to the experia world, my previous phone was a Desire S.
I have a question:
I have a problem with all stock roms with the mediaserver process. It is always running while I listen to music (which is a lot of time) and drains a lot of battery (up to 65%). Though I use poweramp player which is totally independent of the process (own library and decoder). On my Desire S on CM11 I don't have the issue this is why I want to move to a custom rom. I'm on 4.3 now (was hoping this would fix the issue) and want to root and full backup with keys for warranty purposes and then move to a custom rom.
Is it right that I have to downgrade first, since there is no root for 4.3 yet? If yes, what ROM? I have a C5303 and don't know what version I had previously. I bought it in Switzerland without SIMlock or any branding. Is there a way I can find out what my previous version was or can I basically just use any generic C5303 version?
Would you recommend 12.0.A.1.284 in order to be able to use DoomLords rootkit: http://forum.xda-developers.com/showthread.php?p=42701183#post42701183 ?
It's just that I don't know if I ever was on this version, also regarding warranty...
I know, many questions, but I just reached a point where I don't seem to get further without asking. Hope someone can clarify some of them.
Thanks in advance!
EDIT: And also I was wondering: In the picture says flashmode is reached by pressing the back button while connection, but there are softkeys. Is it not done with volume down?
mrjraider said:
Small changes.. @ moderators Is it possible this can become a sticky?
Click to expand...
Click to collapse
+1 for a sticky!
Nice done!
TheMorpheus said:
+1 for a sticky!
Nice done!
Click to expand...
Click to collapse
after flashing done
i have to turn on phone & make usb debugging & unknown source option check
but whenever i am going to boot it again reboot after colour bootscreen
i had tried number of times flashing again & again
i am attaching my flashtool log file also
Azhar
According to the log you attached everything went fine. So I dont understand the problem.
Perhaps an idea to redownload it? Sometimes it wont work properly because the ftf file is somewhat damaged..
I have to relock the bootloader before restore?
Edit
No, it's not needed!
reflashig stock rom
Thanks for this nice guide. Im having a lot of issues with the 4.3 rom.
I flashed via SUS, editing build.prop to let the phone detect the new version, because my phone is carrier locked, and they didnt released the update yet.
I have a lot of lag, and I must force reset lots of times, so I want to make a clean install, because last time I only updated.
So my question is, if I do a factory reset, my build.prop is going to change to the original file (Orange's rom) or ill keep with my modified file? (Stock center Europe)
What do you recommend to me? If I reflash a stock European ftf via flashtool, I'll have the stock's build.prop, and I'll receive those Ota updates without problem?
Thanks for your work!
No if you have a TA backup you need to reflash your ROM and Restore TA partition
mrjraider said:
No if you have a TA backup you need to reflash your ROM and Restore TA partition
Click to expand...
Click to collapse
I don't have the backup, because my phone has the bootloader locked, and the only thing I have done is root and editing build.prop to be able to upgrade to European 4.3. Everything is working for me, track id and BE. (btw I have a backup of my build.prop in the computer)
I only want to do a fresh install of 4.3, not my carriers rom, because is on 4.1.2
So can I reflash any Stock 4.3 rom? The rom has it's own build.prop?
Thanks for your help Mrjraider
diolo said:
I don't have the backup, because my phone has the bootloader locked, and the only thing I have done is root and editing build.prop to be able to upgrade to European 4.3. Everything is working for me, track id and BE. (btw I have a backup of my build.prop in the computer)
I only want to do a fresh install of 4.3, not my carriers rom, because is on 4.1.2
So can I reflash any Stock 4.3 rom? The rom has it's own build.prop?
Thanks for your help Mrjraider
Click to expand...
Click to collapse
Yes you can. Simply download the ftf file and follow the steps in the OP
Hi mrjraider,
Many thanks for the guide!
A quick question. I am now in 4.3, bootloader locked. If I downgrade to 4.1.2 (.254 for example) my bootloader is still locked, correct?
Thanks!
Yes
I want to go back to stock from AOSP ROM and I don't know what's the right .ftf file for 12.1.A.0.266 but I think I know the right file for 12.0.A.2.254 (German branded C5303) (I'm from Germany ). If I would flash the 12.0.A.2.254 .ftf file would the Update Center show me the 4.3 OTA update and everything would work like on stock before? And would I lose root even with Voodoo OTA RootKeeper and the option enabled to try keeping Superuser access in SuperSU?
You need to look in the thread I linked to. There you can find many FTF files.
mrjraider said:
You need to look in the thread I linked to. There you can find many FTF files.
Click to expand...
Click to collapse
I know I already looked there but I'm not sure which one is right, because I didn't see a generic one for all C5303 and I don't want do have a foreign branding
Edit: found it, sorry
Gesendet von meinem Sony Xperia SP C5303
hey bro, am looking for Sony C5303_12.0.A.2.254 tft generic global or CE version also UK version ,am unable to find them . I have being searching xda and a found a link that is broken,so please if any one can help.Thanks in advance.:fingers-crossed:
desmond462 said:
hey bro, am looking for Sony C5303_12.0.A.2.254 tft generic global or CE version also UK version ,am unable to find them . I have being searching xda and a found a link that is broken,so please if any one can help.Thanks in advance.:fingers-crossed:
Click to expand...
Click to collapse
Do not ask for ftf files in here. There is a proper thread for this
Normaly I would help but the chances of getting an older update is decreasing every day since the update of Sony has rolled out a few weeks ago
Well done ! Rollback firmware 4.3 to 4.1
Hi guys ! thanks for guide. I got successfull revert my phone from update 266 to 254.
hi sir, i'm on .254 rooted and just want to go back to stock because i want to update it to 4.3, is it the safest way? if so, what will happen to my apps like greenify, Titanium backup, and those apps that was already transferred to sd card? should i have to uninstall these aps? does it have remaining unwiped data to be cleaned if flashing the stock rom?
thank you..
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
New method of rooting your Arc (zergRush method) press this link.
http://forum.xda-developers.com/showthread.php?t=1312859
Warning: use .184 first or you will brick your device.
There are so many threads calling for 2.3.4 and Root and the information is spread all around the forum. I will therefore give a straight answer here: 2.3.4 can be rooted now.
Flash UK.184-> Generic_World(Nordic).181 ->Root + OTA = Rooted 2.3.4
Here is the link for the .181 firmware: http://www.mediafire.com/?y9s73andrl4bllc
This method with .184 first, always works for me.
I made it safe with the LED/battery problem, so I flashed the UK.184 first before I flashed the one above (.181) and I had no problem with LED/battery!
-Turn off your phone and flash to UK.184 firmware (wipe data).
-Start your phone and agree to the normal stuff (note: no battery problem now).
-Turn off your phone once more.
-Flash Generic_World(Nordic).181 and start your phone again (wipe data).
-Plug in your USB-cable to the computer and phone again (ignore PCC companion set-up).
-Make sure USB-debugging is activated in the settings menu.
-Install Gingerbreak 1.2 and press "Root the phone".
-The phone reboots by itself in about 30 seconds after pressing Root (if not, pull down notification bar and press on mass storage and push mount SD-card - it works everytime)!
-After reboot and a long wait, go to settings and install OTA.
-Phone collects firmware OTA and reboots many times.
-Now Its working and you have rooted 2.3.4
Don't touch anything else during this procedure.
UK.184 firmware is here: http://www.multiupload.com/LEA95XC5J0
--------------------------------------------------------
Read also this:
Edit 26/9: this is my findings after reading all posts:
After reading all posts I am getting an idea of the problem (but no solution if you already have problem).
(a) Some people had .368/.145 and flashed to .181 with Root and then OTA to 2.3.4 and it worked fine, (but they will probably get LED-problem next time they need to flash down because they obmitted the .184 step).
(b) Some people already had 2.3.4 and flashed to .181 and got LED-problem right away.
(c) Some people had .368/.145 and flashed first to .184 and then .181 with root before OTA to 2.3.4 and they seems to be fine.
(d) Some people (including me), already had 2.3.4 and flashed to .184 before flashing again to .181 with root and OTA to 2.3.4 and there was No LED-problem. (I also tried several times to flash down again without trouble, but always with .184 first).
Edit 3/10
(e) Some people coming from 2.3.2 can flash .2.3.2 again and root + update OTA to 2.3.4 (But ofcourse, when you want to go down again, be careful).
-So it seems that .181 alone makes the LED-trouble if you want to upgrade your firmware with root to 2.3.4.
-But a combination of .184 and .181 seems to work, when done the first time only!!! It is too late if you did any other way in the beginning.
I therefore don't think it is by chance or random to get LED-trouble, it depends on what you did in the first instance?
There's no other way to do it without flashing? I ain't got the knowledge to flash, plus I don't really trust this method cuz if I make something wrong, the only way to fix it is seus
Sent from my LT15i using XDA Premium App
flashed back to 2.3.2 without any problems
If something goes wrong you can flash it with FlashTool, too and uncheck "wipe data" if you don't want to reflash with SEUS because of losing data.
Sent from my LT15i using XDA Premium App
Retrosid said:
I ain't got the knowledge to flash
Click to expand...
Click to collapse
Well you're in the best place to learn.
nvm guys, dont try this, i ran into the 0% battery, but the first time i flashed it, it was fine, but the second time this happened, and now im getting an replacement device from rogers
jatt101 said:
nvm guys, dont try this, i ran into the 0% battery, but the first time i flashed it, it was fine, but the second time this happened, and now im getting an replacement device from rogers
Click to expand...
Click to collapse
I am not sure you understand or if you read everything posted here on xda-forum?
Read my post sciptum in the post, It says: "better to flash down to UK.184 first so you don't get battery problem"!!
ahahahahaha man i totally didnt see that, i guess i was to excited , bro can you post the uk firmware as well though?, but the funny thing is i flashed the .181 firmware the first time without any problems, and i kinda messed up so i had to flash it again and thats when i ran into the problem, i suggest you post a proper procedure people like me might be to excited and might not read what you wrote LOL
jatt101 said:
ahahahahaha man i totally didnt see that, i guess i was to excited , bro can you post the uk firmware as well though?, but the funny thing is i flashed the .181 firmware the first time without any problems, and i kinda messed up so i had to flash it again and thats when i ran into the problem, i suggest you post a proper procedure people like me might be to excited and might not read what you wrote LOL
Click to expand...
Click to collapse
UK.184 is on the sticky thread on top of the Arc forum called "firmware index", but I will provide it here for you, lazy bugger!
http://www.multiupload.com/LEA95XC5J0
datagubben said:
UK.184 is on the sticky thread on top of the Arc forum called "firmware index", but I will provide it here for you, lazy bugger!
http://www.multiupload.com/LEA95XC5J0
Click to expand...
Click to collapse
ahahha thanks man, so basically what you want us to do is flash the generic uk .184, and then flash the world generic .181, and then use gingerbreak to root it, and you have a rooted 2.3.4, but one thing that i dont understand is how does flashing the uk firmware prevent the battery problem, and why does it even occur?
jatt101 said:
ahahha thanks man, so basically what you want us to do is flash the generic uk .184, and then flash the world generic .181, and then use gingerbreak to root it, and you have a rooted 2.3.4, but one thing that i dont understand is how does flashing the uk firmware prevent the battery problem, and why does it even occur?
Click to expand...
Click to collapse
Yes, do that! And the the UK.184 stops the battery problem. Why? I don't know. It just works. You need people who tries different combinations and this time my combination worked.
jatt101 said:
ahahha thanks man, so basically what you want us to do is flash the generic uk .184, and then flash the world generic .181, and then use gingerbreak to root it, and you have a rooted 2.3.4, but one thing that i dont understand is how does flashing the uk firmware prevent the battery problem, and why does it even occur?
Click to expand...
Click to collapse
nvm !
so flashing uk .184 first, then global generic .181, root, then ota to 2.3.4 !
thx for that solution ! you are THE man ! (or woman ?)
okay datagubben i am suffering from the battery problem and if i flash to .184 then .181 and then to 2.34 does the battery problem go away?
Coming from 2.3.4 already:
Yes, flash UK.184 first then Generic_World(Nordic).181 + make Root and then OTA. You will then have rooted 2.3.4 and being a happy man/woman without battery problem.
Did you not read the first post?
I only have one "thanks" for this discovery
datagubben said:
Coming from 2.3.4 already:
Yes, flash UK.184 first then Generic_World(Nordic).181 + make Root and then OTA. You will then have rooted 2.3.4 and being a happy man/woman without battery problem.
Did you not read the first post?
Click to expand...
Click to collapse
First of all thank u for telling us all the proper way to do it, secondly yes i read your first post but i guess u skipped where i said that i am suffering from the battery problem and if i did ur method of flashing would my existing problem go away, well i tried it nevertheless and it still remains ..... but thank u once again for pointing out the correct way of doing it.
thanks bro now i have root in 2.3.4.
rubenswing said:
First of all thank u for telling us all the proper way to do it, secondly yes i read your first post but i guess u skipped where i said that i am suffering from the battery problem and if i did ur method of flashing would my existing problem go away, well i tried it nevertheless and it still remains ..... but thank u once again for pointing out the correct way of doing it.
Click to expand...
Click to collapse
Ok, here we go:
-Turn off your phone and flash to UK.184 firmware.
-Start your phone and agree to the normal stuff (note: no battery problem).
-Turn off your phone once more.
-Flash Generic_World(Nordic).181 and start your phone again.
-Plug in your USB-cable to the computer and phone again.
-Make sure USB-debugging is activated in the settings menu.
-Install Gingerbreak 1.2 and press "Root the phone".
-The phone reboots by itself in about 20 seconds after pressing Root.
-After reboot and a long wait, go to settings and install OTA.
-Phone collects firmware OTA and reboots many times.
-Now Its working and you have rooted 2.3.4?
Don't touch anything else during this procedure.
My arc keeps telling me "could not update" at the ota part of the procedure. Any suggestions?
Can anyone confirm whether this method will work or not?
I have unlocked rogers arc.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Since we got update threads scattered everywhere, I figured I'd organized things into one thread, as well as give away some new updates.
Retail EU:
81.5.31006-81.5.40002.Retail.en.EU 4.0.4-4.0.4
81.5.32002-81.5.40002.Retail.en.EU 4.0.4-4.0.4
81.5.4002-91.2.26001.Retail.en.EU 4.0.4-4.1.2
Retail GB:
81.5.31002-81.5.39001.Retail.en.GB 4.0.4-4.0.4
81.5.39001-91.2.29001.Retail.en.GB 4.0.4-4.1.2
Orange GB:
81.5.31002-91.2.26001.Orange.en.GB 4.0.4-4.1.2
O2 DE:
81.5.32002-81.5.39002.O2.en.DE 4.0.4-4.0.4
81.5.39002-91.2.26001.O2.en.DE 4.0.4-4.1.2
Vodafone FR:
81.5.31002-81.5.39001.Vodafone.en.FR 4.0.4-4.0.4
81.5.39001-91.2.26001.Vodafone.en.FR 4.0.4-4.1.2
Brasil BR:
871.110.12008-871.110.12012.Brasil.en.BR 4.0.4-4.0.4
871.110.12012-871.111.20003.Brasil.en.BR 4.0.4-4.0.4
871.111.20003-982.50.20.Brasil.en.BR 4.0.4-4.1.2
AmericaMovil MX:
871.110.13009-982.50.25004.AmericaMovil.en.MX 4.0.4-4.1.2
If you have an OTA update.zip please PM it to me or contact me on google talk ([email protected]) and I will quick add it to this thread, with safe hosting, credits to The Firmware Team's Pzyduck for providing safe-haven for these types of files.
Instructions for pulling an OTA update.zip:
Do NOT install the update! Do these first!
Be rooted. We got plenty of methods. Motofail2go for ICS, and my RAZRiRoot.zip for turl1's Clockworkmod.
Download the Root Explorer app, or the ES File Manager app. (Instructions are for Root Explorer.)
Open Root Explorer and go to the ~/cache/ directory, which resides on the root directory of the phone '~/'
Hit the 'Mount R/W' in the corner, if successful will then say 'Mount R/O'
Copy the update file .zip from the ~/cache/ to your sdcard, external to be safe. External is in ~/mnt/external1/ and Internal is ~/sdcard/.
Copy over the update file .zip from the sdcard(s) you chose to your computer and upload it.
You will want to use Voodoo's OTA Rootkeeper before updating if you have a locked bootloader, you can find my thread on a RAZR i compatible version here.
Send me or post a link here to the update and exactly what System Version you were on, and where the update takes you to.
The community will thank you for your help!
Enjoy. Remember to do your part to the community and contribute all updates!
Hmm, but I can't put the EU update.zip on it when I'm on GB without losing data, right?
Vistaus said:
Hmm, but I can't put the EU update.zip on it when I'm on GB without losing data, right?
Click to expand...
Click to collapse
You cannot install any of these on different carriers without use of fastboots and unlocked bootloader.
These updates will ONLY work from PointA-PointB.
Here's another Update Zip for 40002EU. For this one you have to come from 32002 EU. The one in the OP is from 31006.
http://forum.xda-developers.com/showthread.php?p=34886686
Sent from my XT890
HSD-Pilot said:
Here's another Update Zip for 40002EU. For this one you have to come from 32002 EU. The one in the OP is from 31006.
http://forum.xda-developers.com/showthread.php?p=34886686
Sent from my XT890
Click to expand...
Click to collapse
Thanks! Uploaded to server, renamed, and added to the OP.
mattlgroff said:
You cannot install any of these on different carriers without use of fastboots and unlocked bootloader.
These updates will ONLY work from PointA-PointB.
Click to expand...
Click to collapse
mattlgroff, im in 81.5.31006.Retail.en.EU - 4.0.4. and in software update i get notification of an ota. i down loaded that file when ask if i want to install it i select yes. but when in recovery it always fails. why, isnt that the official? because after that i tried flashing it in recovery but it fails too.
before alll this i was already on 81.5.40002.Retail.en.EU - 4.0.4. coming from 81.5.31006.Retail.en.EU. but i wanted to downgrade back to 81.5.31006.Retail.en.EU. and my phone died. thanks to hsd pilot my phone came back to life he sended me a file http://forum.xda-developers.com/attachment.php?attachmentid=1528201&d=1354399653. but now im stuck in what i told you at the begining. why?? what can i do to go back to 81.5.40002.Retail.en.EU. i know this is not the thread sorry but i was watching your new otas. and i cant install the one for my version.
Are you rooted? If yes and you used the Root with insecured Kernel, then you probably have the wrong Boot.img on your Phone. Grap the Boot_signed out of the 31006 Fastboot File and flash it through fastboot
fastboot flash boot boot_signed
Sent from my XT890
HSD-Pilot said:
Are you rooted? If yes and you used the Root with insecured Kernel, then you probably have the wrong Boot.img on your Phone. Grap the Boot_signed out of the 31006 Fastboot File and flash it through fastboot
fastboot flash boot boot_signed
Sent from my XT890
Click to expand...
Click to collapse
As HDS-Pilot says.
The error message from side-loading will tell us exactly the problem.
mattlgroff said:
As HDS-Pilot says.
The error message from side-loading will tell us exactly the problem.[/QUOTE
thank you guys!!! that was the problem and another one was that i erase alot of apk.s that i dont use so at time of flashing i saw it said something about an apk. missing so i fastbooted again and flash boot.img and here i am with the 40002.rt.eu. and now waiting for jellybean
Click to expand...
Click to collapse
If I want to update, it can be done on a homemade fastboot or I need to use a stock firmware, my bootloader is unlocked, can I flash a totally stock firmware without problem and then use the OTA update? Thanks.
joel_sinbad said:
If I want to update, it can be done on a homemade fastboot or I need to use a stock firmware, my bootloader is unlocked, can I flash a totally stock firmware without problem and then use the OTA update? Thanks.
Click to expand...
Click to collapse
Yes you can.
I have version 871.110.12008.XT890.Brasil.en.BR installed from sbf.droid-developers
My Razr i bootloader is unlooked and rooted. When i try to install the update with the android button (in about system) i recive error message after reboot. How can i install this update manually with fastboot console?
Thanks!
First, use an Root Explorer and copy your downloaded Update Zip out of the Cache Folder and leak it
Edit : Ok, it's in the OP already. Sorry, it's 1am in Germany :sly:
Your RazR i is rooted, how did you root it? If you used the Unlocked Root (insecure Kernel), than grap the boot signed out of the sbf you flashed and use fastboot to install it
fastboot flash boot boot_signed.
After that it should work. If not, you maybe deleted some System Apps. If that's the case, flash the system_signed.
Sent from my XT890
Hi all, if I have link2sd linked applications. if I do what he says here respectively, applications may be lost or will stay intact?
I have this doubt, I would not lose my apps linked by link2sd when updating
josmel91 said:
Hi all, if I have link2sd linked applications. if I do what he says here respectively, applications may be lost or will stay intact?
I have this doubt, I would not lose my apps linked by link2sd when updating
Click to expand...
Click to collapse
I have no clue. I'd ask in the Q&A section if you want an answer quickly
Hello matt,
Could you pull the latest homescreen & circle widget combo from the latest ota of XT890. I noticed that the occasional lag on on the launcher has been fixed with new version. I want to install it on my droid razr to get a fresh taste.
Semseddin said:
Hello matt,
Could you pull the latest homescreen & circle widget combo from the latest ota of XT890. I noticed that the occasional lag on on the launcher has been fixed with new version. I want to install it on my droid razr to get a fresh taste.
Click to expand...
Click to collapse
After getting a DMCA Takedown Request from posting those before from the MB886 I'm afraid I can't help you there.
The 81.5.31002-81.5.39001.Retail.en.GB OTA update did something to my RAZR i's GSM radio, and now it can't recognize any SIM that I put in it ('No service'). :\ It used to work perfectly on 81.5.31002 prior to the update. Can anyone help me out?
I have tried reflashing the original 81.5.31002 stock firmware, the 81.5.39001 firmware as well as the latest EU firmwares using RSD Lite, didn't help at all. The GSM radio still seems to be out. I have also tried setting the network type to GSM in the *#*#4636#*#*-triggered menu and rebooting the phone, but even that doesn't help.
jenova941 said:
The 81.5.31002-81.5.39001.Retail.en.GB OTA update did something to my RAZR i's GSM radio, and now it can't recognize any SIM that I put in it ('No service'). :\ It used to work perfectly on 81.5.31002 prior to the update. Can anyone help me out?
I have tried reflashing the original 81.5.31002 stock firmware, the 81.5.39001 firmware as well as the latest EU firmwares using RSD Lite, didn't help at all. The GSM radio still seems to be out. I have also tried setting the network type to GSM in the *#*#4636#*#*-triggered menu and rebooting the phone, but even that doesn't help.
Click to expand...
Click to collapse
Use my home-made fastboot to go back to 81.5.31002.
Install the OTA again up to 81.5.39001.
See if that works
mattlgroff said:
Use my home-made fastboot to go back to 81.5.31002.
Install the OTA again up to 81.5.39001.
See if that works
Click to expand...
Click to collapse
Thanks, downloading. Do I just flash it using CWM, RSD Lite or something else?
Hi
As I struggled a bit, here's how to root the HTC One M8 Dual SIM.
Disclaimer
As always, if you **** your phone up, it's not my fault. Don't blame me. Further, I will not answer any questions about this. Please help yourself.
Please use the "Thanks" ( :good: ) button if you just want to say "Thank you" or "Great" or "I wanna marry you".
Prerequisites
HTC One M8 Dual SIM (m8_dugl)
A complete backup of your phone! (e.g. with titanium backup)
fastboot installed
USB Cable
Some time (do not hurry!)
htc DEV UNLOCK (http://www.htcdev.com/bootloader/unlock-instructions)
Warning
Make sure you have a "m8_dugl" device:
Reboot your device to the bootloader (POWER+VOLUME_UP until the screen blacks out, then POWER+VOLUME_DOWN). If it reads there something different than "m8_dugl", then this guide is not for you!
Steps
Download the custom recovery "TWRP" from here: https://s.basketbuild.com/devs/Captain_Throwback/One (M8)/ALL/Recovery (See hint below)
Download "UPDATE-SuperSU-vX.XX.zip" from here: http://download.chainfire.eu/supersu
Copy "UPDATE-SuperSU-vX.XX.zip" to you phone's internal SD
--> Until now no harm has been done to you device but DEV UNLOCK. So this would also be a good time to do a BACKUP! #JustSaying
Open a command prompt and navigate to your fastboot executable.
Put your phone into fastboot mode: POWER+VOLUME_UP until the screen blacks out, then press POWER+VOLUME_DOWN. You see some options soon. Use the volume buttons to navigate, the power button to perform the selected action. Select FASTBOOT and press the POWER button.
Connect you phone to the PC
Type "./fastboot boot path/to/where/you/saved/TWRP_Recovery_x.x.x.x_M8_CPTB.img"
If boot does not work, you can flash the recovery to your phone. But remember: When you do a stock update, you must revert back to a stock recovery!
Do flash the custom recovert, type "./fastboot flash recovery path/to/where/you/saved/TWRP_Recovery_x.x.x.x_M8_CPTB.img"
Touch "Install"
Select the "UPDATE-SuperSU-vX.XX.zip" file
Swipe to start
Touch Reboot System.
You're phone should be rooted.
** Hint **
If the newest TWRP does not work, try a different one.
If none of them work, try the official one: http://teamw.in/project/twrp2/225
If the official TWRP does not work for you, you can try the following one, but it's rather old: http://forum.xda-developers.com/htc...al-sim-european-version-t2816991/post54258731
****
Cheers,
Chris
PS: @donmarkoni provided some resources that might be useful to you. See his post: http://forum.xda-developers.com/showpost.php?p=56134225&postcount=12
Changelog:
[2015-01-18] Updated parts that do not work anymore. Made version numbers generic.
[2014-10-20] a) I have been hinted that the official TWRP should work for the m8_dugl as well. b) The current version of SuperSU is v2.14 and works well. c) @donmarkoni provided some more resources worth mentioning.
cimnine said:
Hi
As I struggled a bit, here's how to root the HTC One M8 Dual SIM.
Disclaimer
As always, if you **** your phone up, it's not my fault. Don't blame me. Further, I will not answer any questions about this. Please help yourself.
Prerequisites
HTC One M8 Dual SIM (m8_dugl)
fastboot installed
USB Cable
Some time (do not hurry!)
htc DEV UNLOCK (http://www.htcdev.com/bootloader/unlock-instructions)
Note: Reboot your device to the bootloader (POWER+VOLUME_UP until the screen blacks out, then POWER+VOLUME_DOWN). If it reads there something different than "m8_dugl", then this guide is not for you!
Steps
Download the custom recovery from here: http://forum.xda-developers.com/htc...al-sim-european-version-t2816991/post54258731 (It must be made for the m8_dugl, the 'normal' m8 recoveries from TWRP/CWM do not work (yet)!)
Download "UPDATE-SuperSU-v2.02.zip" from here: http://download.chainfire.eu/supersu
Copy "UPDATE-SuperSU-v2.02.zip" to you phone's internal SD
Open a command prompt and navigate to your fastboot executable.
Put your phone into fastboot mode: POWER+VOLUME_UP until the screen blacks out, then POWER+VOLUME_DOWN. Now you see some options. Use the volume buttons to navigate, the power button to perform the selected action. (Just select FASTBOOT and press the POWER button.)
Connect you phone to the PC
Type "./fastboot boot path/to/where/you/saved/m8-dual-twrp.img"
--> Until now no harm has been done to you device but DEV UNLOCK. So this would also be a good time to do a BACKUP! #JustSaying
Touch "Install"
Select the "UPDATE-SuperSU-v2.02.zip" file
Swipe to start
Touch Reboot System.
You should be rooted.
I did not test that yet, but this method should not prevent you from receiving OTAs. But I won't vouch for that.
Cheers,
Chris
Click to expand...
Click to collapse
Thank you Chris,
step by step guides are always helpful, as the answer a lot of questions about the whole procedure. So I´m at least rooted now. Let´s see if OTA´s will work, but they can also be installed via adb. I prefer having a custom recovery for installs and making backups from data, so this solution is the one I need (and always used before btw).
Thank you !
Guido
thanks alot i hope xda opening section for us HTC-M8 Dual Sim Owners
[deleted]
guidogsbn said:
Thank you Chris,
step by step guides are always helpful, as the answer a lot of questions about the whole procedure. So I´m at least rooted now. Let´s see if OTA´s will work, but they can also be installed via adb. I prefer having a custom recovery for installs and making backups from data, so this solution is the one I need (and always used before btw).
Thank you !
Guido
Click to expand...
Click to collapse
Hi
I hope you will tell us if the OTA will work.
By the way, do you know of unlocking the bootloader with HTC Dev create any issue for the future OTA?
Cheers
TBH
Sent from my HTC One_M8 dual sim using Tapatalk
thebighunt said:
Hi
I hope you will tell us if the OTA will work.
By the way, do you know of unlocking the bootloader with HTC Dev create any issue for the future OTA?
Cheers
TBH
Sent from my HTC One_M8 dual sim using Tapatalk
Click to expand...
Click to collapse
With re-locked bootloader and stock recovery OTA will work:good:
guidogsbn said:
With re-locked bootloader and stock recovery OTA will work:good:
Click to expand...
Click to collapse
Thanks
I'm still with the stock recovery
TBH
Sent from my HTC One_M8 dual sim using Tapatalk
Stuck in a boot loop
Hi,
thanks for the guide and it worked perectly. No problems all day long after rooting the phone.
But since this morning I am stuck in a boot loop! Already tried factory reset, that works at first, after the phone is loading some updates, it is running into a boot loop
Is there anything I can do?
Rgds
Volker
Edit: Updated SuperSu, Works again...
m8 update ?
any1 knows if we are ever gonna get updates like regular m8 ? , i am still waiting on the root thing hoping they will update ,
any1 have any information or should i go ahead and root ? , is the performance better after rooting and removing all that bloatware or no significant difference ?
last question plz , does xposed module work with this phone and sense 6 toolbox use in android revolution hd rom ?
i tried asking million times here and and htc and called them and chatted online with them and all says they have no information and only 1 source ( august-sept ) under testing ,, so thats why i am asking plz if any1 knows anything , or can u advice me what to do ?!! cuz my phone sucks compared to my friends regular updated stock m8 in every aspect , sound , performance , battery , benchmarks , ......etc
aymanzz said:
any1 knows if we are ever gonna get updates like regular m8 ? , i am still waiting on the root thing hoping they will update ,
any1 have any information or should i go ahead and root ? , is the performance better after rooting and removing all that bloatware or no significant difference ?
last question plz , does xposed module work with this phone and sense 6 toolbox use in android revolution hd rom ?
i tried asking million times here and and htc and called them and chatted online with them and all says they have no information and only 1 source ( august-sept ) under testing ,, so thats why i am asking plz if any1 knows anything , or can u advice me what to do ?!! cuz my phone sucks compared to my friends regular updated stock m8 in every aspect , sound , performance , battery , benchmarks , ......etc
Click to expand...
Click to collapse
I read somewhere that our dual sim should get directly Android L and until then no update. Xposed module, sense 6 and Wanam Xsense are working good, of course u need to be rooted
FYI - You might want to update this guide to point to the official TWRP for M8 now that it supports Dual SIM.
cimnine said:
Hi
As I struggled a bit, here's how to root the HTC One M8 Dual SIM.
...
Cheers,
Chris
Click to expand...
Click to collapse
@cimnine, I'll leave these links here for you to put in the OP and for the other guys to have at hand:
0P6BIMG_M8_DUGL_K44_SENSE60_HTC_Europe_1.45.401.12_R_Radio_1.18.30306251.05G_30.57.306251.00L_release_381655_combined_signed.zip 1.40 GB
2014-07-26--03-35-20 KOT49H release-keys.zip 1.45 GB
M8_dugl_preload.zip 89.5 MB
m8_dugl_stock_recovery_1.45.401.12.img 13.6 MB
0P6BIMG_M8_TWRP_Recovery_2.8.0.5_CPTB 12.50 MB Thanks to @Captain_Throwback
OTA_M8_DUGL_K444_SENSE60_MR_HTC_Europe_3.33.401.6-1.45.401.12_R_release_3986927s90q9xyzwqo8q8g.zip
Cheers!
donmarkoni said:
@cimnine, I'll leave these links here for you to put in the OP and for the other guys to have at hand:
0P6BIMG_M8_DUGL_K44_SENSE60_HTC_Europe_1.45.401.12_R_Radio_1.18.30306251.05G_30.57.306251.00L_release_381655_combined_signed.zip 1.40 GB
2014-07-26--03-35-20 KOT49H release-keys.zip 1.45 GB
M8_dugl_preload.zip 89.5 MB
m8_dugl_stock_recovery_1.45.401.12.img 13.6 MB
0P6BIMG_M8_TWRP_Recovery_2.8.0.5_CPTB 12.50 MB Thanks to @Captain_Throwback
Cheers!
Click to expand...
Click to collapse
No need to post my TWRP here - the official one works fine.
Captain_Throwback said:
No need to post my TWRP here - the official one works fine.
Click to expand...
Click to collapse
OK, I will remove if you want me to, but most of the credit goes to you for unified TWRP, working MTP and UMS.
donmarkoni said:
@cimnine, I'll leave these links here for you to put in the OP and for the other guys to have at hand:
0P6BIMG_M8_DUGL_K44_SENSE60_HTC_Europe_1.45.401.12_R_Radio_1.18.30306251.05G_30.57.306251.00L_release_381655_combined_signed.zip 1.40 GB
2014-07-26--03-35-20 KOT49H release-keys.zip 1.45 GB
M8_dugl_preload.zip 89.5 MB
m8_dugl_stock_recovery_1.45.401.12.img 13.6 MB
0P6BIMG_M8_TWRP_Recovery_2.8.0.5_CPTB 12.50 MB Thanks to @Captain_Throwback
Cheers!
Click to expand...
Click to collapse
@donmarkoni: i posted this question in the stock recovery thread but got no reply...
i have downloaded the mega file 0P6BIMG_M8_DUGL_K44_SENSE60_HTC_Europe_1.45.401.12_R_Ra.... 2 times before and tried winzip, 7-zip and winrar but zip file is corrupt. is this a new file? i cant see an md5 or sha. size of my download from windows properties is 1,506,353,851 bytes.
have you checked the file?
the '2014-07-26--03-35-20 KOT49H release-keys.zip' is a clean TWRP backup?
i have made my own backup by temp installing TWRP 2.8 so can also confirm that works (thanks again Captain_Throwback)
any sign of an original RUU yet?
Stepp said:
I read somewhere that our dual sim should get directly Android L and until then no update. Xposed module, sense 6 and Wanam Xsense are working good, of course u need to be rooted
Click to expand...
Click to collapse
See that table from http://android-revolution-hd.blogspot.ch/2014/10/htc-devices-to-receive-android-50.html
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
guidogsbn said:
With re-locked bootloader and stock recovery OTA will work:good:
Click to expand...
Click to collapse
That's why I usually don't install the recovery but only boot it. We'll see in Spring 2015 if it works, it seems that we won't get an update any sooner.
PS: Can some moderator remove the 5 Minutes Wait restriction from my account? I'm not exactly new to XDA, am I?
gazzacbr said:
@donmarkoni: i posted this question in the stock recovery thread but got no reply...
i have downloaded the mega file 0P6BIMG_M8_DUGL_K44_SENSE60_HTC_Europe_1.45.401.12_R_Ra.... 2 times before and tried winzip, 7-zip and winrar but zip file is corrupt. is this a new file? i cant see an md5 or sha. size of my download from windows properties is 1,506,353,851 bytes.
have you checked the file?
the '2014-07-26--03-35-20 KOT49H release-keys.zip' is a clean TWRP backup?
i have made my own backup by temp installing TWRP 2.8 so can also confirm that works (thanks again Captain_Throwback)
any sign of an original RUU yet?
Click to expand...
Click to collapse
0P6BIMG_M8_DUGL_K44_SENSE60_HTC_Europe_1.45.401.12.....signed.zip is a encrypted signed zip, as the file name suggests. It does work, as you can see here. All other files are good too. That's all I can say about it, as I don't have that phone, I was just helping.
cimnine said:
That's why I usually don't install the recovery but only boot it. We'll see in Spring 2015 if it works, it seems that we won't get an update any sooner.
PS: Can some moderator remove the 5 Minutes Wait restriction from my account? I'm not exactly new to XDA, am I?
Click to expand...
Click to collapse
Maybe earlier with 4.4.4 as LLabTooFer4 posted on twitter :
LlabTooFeR @LlabTooFeR 30. Sep.
M8 Dual SIM users don't be disappointed not getting 4.4.3, you will get 4.4.4 before the end of October
:good:
donmarkoni;...encrypted signed zip...That's all I can say about it said:
Ok, thanks for info. Looks like at least one user had success with it so i will keep it in a safe place
Click to expand...
Click to collapse
Hi,
trying to root a phone of a friend, z1 compact.
He has 5.1.1 installed.
Should i wait or root now, because i heard there is a new update for z1compact? Do i need to unlock the bootloader to root it? New version is not stable yet i read and causes bootloops.
What is the easiest way i should root it, step by step?
I am not that experienced with android myself, so any tips are welcome. He just wants his phone rooted to control internet/data access for some apps, and have more control over the apps installed....
Thanks in advance!
m123456789 said:
Hi,
trying to root a phone of a friend, z1 compact.
He has 5.1.1 installed.
Should i wait or root now, because i heard there is a new update for z1compact? Do i need to unlock the bootloader to root it? New version is not stable yet i read and causes bootloops.
What is the easiest way i should root it, step by step?
I am not that experienced with android myself, so any tips are welcome. He just wants his phone rooted to control internet/data access for some apps, and have more control over the apps installed....
Thanks in advance!
Click to expand...
Click to collapse
Someone here - http://forum.xda-developers.com/sony-xperia-z1-compact/general/root-14-6-0-368-via-kingroot-t3242735 - says they got kingroot method working on 5.1, but not yet able to switch to SuperSU, (https://www.google.com/url?q=http:/...bskDFQ&usg=AFQjCNEbOT7fDsBIA-flXO3m6zakipqSLw). I haven't heard of that working on 5.1 up till now. Besides that with locked bl, only root is this - http://forum.xda-developers.com/son...ck-step-step-to-rooted-lollipop-14-6-t3213465.
Doesn't seem to be any reason to wait. The last update is still 5.1, and the last news is that there will be no M for Z1c, - (http://forum.xda-developers.com/son...al/marshmallow-upgrade-z1-z1-compact-t3218903).
levone1 said:
Someone here - http://forum.xda-developers.com/sony-xperia-z1-compact/general/root-14-6-0-368-via-kingroot-t3242735 - says they got kingroot method working on 5.1, but not yet able to switch to SuperSU, (https://www.google.com/url?q=http:/...bskDFQ&usg=AFQjCNEbOT7fDsBIA-flXO3m6zakipqSLw). I haven't heard of that working on 5.1 up till now. Besides that with locked bl, only root is this - http://forum.xda-developers.com/son...ck-step-step-to-rooted-lollipop-14-6-t3213465.
Doesn't seem to be any reason to wait. The last update is still 5.1, and the last news is that there will be no M for Z1c, - (http://forum.xda-developers.com/son...al/marshmallow-upgrade-z1-z1-compact-t3218903).
Click to expand...
Click to collapse
(So i use this tutorial: http://forum.xda-developers.com/showpost.php?p=62222794&postcount=37)
So i need to:
1. Somehow downgrade device to stock kitkat (that is 4.4 right?), then root it
2. and then update to 5.1.1 again?
In step 2, would you recommend update to a prerooted version like this one? 14.6.A.1.216 http://forum.xda-developers.com/son...03-14-6-1-216-customized-ce5-central-t3243035
m123456789 said:
(So i use this tutorial: http://forum.xda-developers.com/showpost.php?p=62222794&postcount=37)
So i need to:
1. Somehow downgrade device to stock kitkat (that is 4.4 right?), then root it
2. and then update to 5.1.1 again?
In step 2, would you recommend update to a prerooted version like this one? 14.6.A.1.216 http://forum.xda-developers.com/son...03-14-6-1-216-customized-ce5-central-t3243035
Click to expand...
Click to collapse
I haven't yet tried .216. Its new as of a couple of days ago. I also haven't yet tried PRFs. I've read a few threads that seem to indicate occasional problems with them. Since I have unlocked bl, I've been able to root the easy way, so I'm not sure what options or limitations there are with that rooting method. From my experience, I would recommend RockZ1 ROM, (.368). It has anything you would want included, and may well update to the new fw anytime soon...
Don't unlock the bootloader many functions will be lost if you are trying to keep the stock rom.
Sent from my C6902 using XDA Premium 4 mobile app
The device is now in Boot Loop after trying to go from the 5.1.1 to 4.4.4 using Sony Mobily Flasher and then trying to install 14.4.A.0.157 ...
What did I do wrong, what can i do now?
Thanks for any help
I just turned phone off, loaded 14.4.A.0.157 with Sony Mobile Flasher, plugged in with volume down key. Then it was flashing and finished. Then unplugged and started.
And now it keeps restarting at startup (when the "waves" appear). That's a bootloop right? I turned it off with the small red button now.
I tried flashing again with same method. And it is still bootlooping after it......
Any expert could help? Or is the phone broken forever now
Did you wipe data / cache?
Steffe89 said:
Did you wipe data / cache?
Click to expand...
Click to collapse
No, where or how should i do that?
Edit: did some research. Should i have selected something in SonyMobileFlasher?
Because I don't find cache i only have these 2 options:
APPS_LOG
USERDATA
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://i.imgur.com/RCJNhRO.jpg
Repair the phone via PC Companion.
Sent from my C6902 using XDA Premium 4 mobile app
DetmL said:
Repair the phone via PC Companion.
Sent from my C6902 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
PC Companion does not recognize the phone. When i plug it in, it says searching, but then... "no phone connected"
But in windows i see it connected as a drive which i can not use
m123456789 said:
No, where or how should i do that?
Edit: did some research. Should i have selected something in SonyMobileFlasher?
Because I don't find cache i only have these 2 options:
APPS_LOG
USERDATA
http://i.imgur.com/RCJNhRO.jpg
Click to expand...
Click to collapse
Yes, check the 2 'wipe' boxes, and flash again. I bet that will do it. The same thing happened to me with . 216
levone1 said:
Yes, check the 2 'wipe' boxes, and flash again. I bet that will do it. The same thing happened to me with . 216
Click to expand...
Click to collapse
Just tried with another version. Bootloop aswell. Now i noticed in log, that i should have enabled unknown sources and debugging? But i can't enable it now, because it does not boot.
09/000/2015 02:00:46 - INFO - Flashing finished.
09/000/2015 02:00:46 - INFO - Please unplug and start your phone
09/000/2015 02:00:46 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
Trying your method now, with the 2 wipes selected
Edit: with wipe it now boots. thanks! trying to install .108 now, because other is not rootable.
and after rooting kitkat4.4.4 .108, i try to update to a prerooted 5.1.1
I am on a rooted 4.4.4 .108 now.
How do i proceed?
For example, how can i load this prerooted 5.1.1 http://forum.xda-developers.com/son...03-14-6-1-216-customized-ce5-central-t3243035 ?
m123456789 said:
Just tried with another version. Bootloop aswell. Now i noticed in log, that i should have enabled unknown sources and debugging? But i can't enable it now, because it does not boot.
09/000/2015 02:00:46 - INFO - Flashing finished.
09/000/2015 02:00:46 - INFO - Please unplug and start your phone
09/000/2015 02:00:46 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
Trying your method now, with the 2 wipes selected
Edit: with wipe it now boots. thanks! trying to install .108 now, because other is not rootable.
and after rooting kitkat4.4.4 .108, i try to update to a prerooted 5.1.1
Click to expand...
Click to collapse
The msg about unknown sources, etc. comes after the flash bc now your phone is stock, so by default they're not checked. It wouldn't have flashed if they weren't checked in the first place. You'll probably hit some bumps, but don't give up. There's almost always a fix...
On rooted 4.4.4 with Superuser installed. Then trying to load the prerooted 5.1.1 zip.
So rebooted with volume down and installed the prerooted zip file from SD. With CWRM
Everything seems to work, but at the end of flashing i saw some message like:
"set_perm some changes failed"
Then after restart all apps get optimized and i am on 5.1.1.
However, i think i lost root, also no SuperUser installed? And the Superuser was included in the zip prerooted file.
Don't worry, seems to work fine after installing lockeddualrecovery.
How exactly do i install the
xposed-v75-sdk22-arm.zip ?
thanks in advance
m123456789 said:
I am on a rooted 4.4.4 .108 now.
How do i proceed?
For example, how can i load this prerooted 5.1.1 http://forum.xda-developers.com/son...03-14-6-1-216-customized-ce5-central-t3243035 ?
Click to expand...
Click to collapse
It's not worth it to update, believe me
m123456789 said:
Don't worry, seems to work fine after installing lockeddualrecovery.
How exactly do i install the
xposed-v75-sdk22-arm.zip ?
thanks in advance
Click to expand...
Click to collapse
Open recovery > select 'install' > choose file. You'll get a long reboot and the whole 'optimizing' thing again.
Yes, after installing xposedv75, it rebooted and loaded addiotional ~+100 apps But it seems to work.
What program would you guys recommend in terms of saving data, restricting internet access of apps (and maybe even ads). And some other for spoofing/restricting requested usage access of certain apps?
(I tried Xprivacy, but it is pretty advanced. It did not seem to block inapp ads or internet access, even when you denied it. Also it only lists apps which are newly installed, not preinstalled ones.
Maybe it is easy but I just didn't understand it yet )
Over the past couple of days, I have been experiencing various issues with flashtool. Using the internets help and many hours of my time I managed to fix most of these problems that occurred for me. Although there are hundreds of Flashtool step by step instructions, I thought it would be best for an updated and more in depth on what you should be aware of first before clicking "Flash".
Firstly, I do not take responsibility for any device broken or damaged since there is ALWAYS a minute chance of your device bricking.
Lets start, shall we?
Things Needed
Z5 Compact
Original Cable (or any cable actually that is working and can transfer files)
Flashtool 0.9.22.3
Sony Xperia Z5 Compact Stock Rom
Okay to start off.. Yes, this should work with other phones however I am not providing the stock roms for those, it takes a simple google search to find them ie. "Sony Xperia Z5 Stock Rom ftf"
You don't need the latest stock rom either since you can update once the phone is setup depending on if you have access to OTA updates (Over the Air).
Step 1.
Download flashtool if you haven't already. If you have an older version of flashtool, uninstall it and make sure all old files are gone for good and also be sure the new one is fully installed. I prefer to use the magnet link on the website (for torrents) since using uploaded.net takes forever.
Step 2a.
If you're on Windows 8/8.1/10 then please take note to this specific paragraph, any other OS skip to 2b Windows 8/8.1 like to have its security tight, so they block you from installing drivers with unsigned certificates to "keep your computer from harm" but just go ahead and follow the instructions to allow your computer install these drivers. If the drivers aren't installed correctly, then you won't be flashing anything today Okay, go to Settings>General and then click on 'Restart Now' under 'Advanced Startup'.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This will restart your PC. It will then take you to a screen that gives you various options. On Windows 8 you will see 'Troubleshoot' and on Windows 8.1 you will see 'Start-up Settings'. Select either that appears. This will take you to another page that will ask to restart windows in order to use some advanced startup features, just click 'Restart'. If it already takes you to the page without restart, or if your computer just restarted and you're getting the options of what to select, make sure you select 'Disable driver signature enforcement'.
Your computer should now restart with driver signature enforcement disabled. Now, go ahead and carry on with the instructions in 2b!
Step 2b.
Navigate to the 'drivers' folder where you installed Flashtool. If you cant remember where you installed it, the default directory should be in "C:\Flashtool". Open 'Flashtool-drivers.exe' and install:
Flashmode Drivers
Fastboot Drivers
Z5 Compact Device Driver (Or whatever your device is)
Now we have successfully installed the drivers for flashtool and our device!
Step 3.
Find the stock rom you downloaded, copy and paste it into your firmwares folder in flashtool. For me, this is in "C:\Users\Matty\.flashTool\firmwares". People have been saying to delete the folders inside the firmwares folder, do not do this as the flash might not work.
Step 4.
Note
If you're running 64bit, I recommend you to not use Flashtool64.exe at first, just use the standard 'Flashtool.exe'. If you dont get an icon on your desktop from the setup, just navigate to the folder in the directory you installed it in, then right click and click send to desktop so you can access it easy
Step 5.
Open Flashtool from your newly created shortcut on your desktop. Click the Flash icon, then click Flashmode, then hit Ok. Click your Firmware on the left to start off with. You might have to hit the firmware dropdown until it gets to the actual firmware like so:
If you want to remove all your data, where it says Wipe, hit all the boxes. (APPS_LOG, DIAG, SSD, USERDATA). Then click Flash. You will now see "Preparing files for flashing" on your screen. Be very patient, and in the meantime, turn your phone off ready to enter Flashmode. Make sure your phone is switched off and NOT plugged.
When you see this box come up on your computer, It's probably time to connect the USB to your computer, and enter flashmode on your phone.
Plug the USB into your computer
(TRY USB 2.0 FIRST, SOME REASON NO USB 3.0 PORT WORKED FOR ME+MANY OTHER PEOPLE HAD PROBLEMS WITH USB 3.0 I.E loader.sin errors)
Entering Flash Mode
Hold the Volume Down button and plug the USB cable from your computer into your phone. You should hear the Windows noise it makes to say the device is connected to the PC. If any extra drivers are needed to complete the flash it could take longer for the flash to start. You should then see a constant green light in the top right of your device, gently put it somewhere without unplugging the charger and let Flashtool do the hard work
Step 6.
Leave the device for no longer than 30 minutes. However, if you're unsure be safe and leave it for a full hour, go out have a nice brew, do a tap and dance and come back and it should be done. The only reason it would get stuck is because you unplugged the phone during the Flash, or if the cable somewhat died throughout the operation. If so, repeat the instructions in hope your device will be as good as new
Flashtool will now let you know when it is done. It will say "Flashing finished, please uplug and start your phone."
If it says that, hooray! You have successfully flashed your phone with stock rom!
If not and you get an error before it even wants to flash, or throughout the process you get an error, post it below and I'll take a look. I'm not very good but I know quite a few errors.
END OF TUTORIAL
I just thought I'd help the community out in a way that I can, since I'm bad at like everything else lol.
Peace folks :highfive: :cyclops:
Great write-up! I know it probably would have helped me months ago for something like this to exist. For anyone coming here for info, it also took me three PC's before I found one that played well with flash tool. Also if you ever get a failure, reboot PC, phone, and try again. Persistence pays off.
civicsr2cool said:
Great write-up! I know it probably would have helped me months ago for something like this to exist. For anyone coming here for info, it also took me three PC's before I found one that played well with flash tool. Also if you ever get a failure, reboot PC, phone, and try again. Persistence pays off.
Click to expand...
Click to collapse
Thanks buddy! I suppose the old saying does work.
"Have you tried turning it off and on again?" Works mostly for me lol
If you're on Windows 8/8.1
Click to expand...
Click to collapse
on Windows 10 to
Good work
ciopik said:
on Windows 10 to
Good work
Click to expand...
Click to collapse
I'll add that now, thanks man
The firmware folder is not detected by Flashtool although I have put it in the correct folder...
I have tried hundred of times, i just dont understand
you dont need unlock bootloader for stock kernel\rom right?
If you want to upgrade you better use Xperia companion.
If you want to downgrade and use FlashTool and if you have a problem you better have unlocked bootloader.
Guys,
This is a good tutorial. but I met a dead end, i got " processing partition.sin finished with errors" message, any suggestion?
Thanks for the help, this is my first time flashing
Regards
I am facing same issue i have xperia z5 dual unlocked bootloader i have installed flashtool and drivers correctly and i have placed the ftf firmware in given directory also but flashtool not showing any thing but for m4 aqua i am able to see the ftf firmware please help me
---------- Post added at 09:36 AM ---------- Previous post was at 09:32 AM ----------
EMJI79 said:
The firmware folder is not detected by Flashtool although I have put it in the correct folder...
I have tried hundred of times, i just dont understand
Click to expand...
Click to collapse
Same problem here:crying:
when i get to step 6 it starts flashing but then my phone just switch on on itself and the process stop
my IMEI become unknown,
please help
hi, can i do this on Z5C Docomo (SO-02H)?
also can i flash global rom on that...?
Hey guys.
I have a Z5 Compact (E5823) that's stuck on android version 5.1.1. It never shows any available updates in the Software Update screen. I'd like to get it on 6.0 in the least just for the better permissions system it contains.
In searching for a way to update it, naturally I found this page and all the helpful info it contains. I've never been steered wrong by XDA in the past. I've always found information on this site helpful, and it works.
I've downloaded Flashtool.
I've followed all of the instruction for installation, including the annoying driver installation process for Windows 8.1.
I've downloaded multiple firmwares from Xperifirm.
I can get everything happening, and it looks to work when looking at the Flashtool screen. It says it's complete (just like the little image at the bottom of the initial post).
Nothing seems to have happened to the phone. I boot it back up and it's still running the same old 5.1.1. Flashtool runs through it's process very fast, as in a few seconds, not the half an hour suggested.
The phone came from Hong Kong as far as I can tell. It may have been a refubished phone, I can't be sure. I'm trying to get the Customised AU version 6.0 software on it.
What am I doing wrong? I don't know what else to try, and it's annoying me. PLEASE HELP.
Thanks. Paul.
plazmafire said:
Hey guys.
I have a Z5 Compact (E5823) that's stuck on android version 5.1.1. It never shows any available updates in the Software Update screen. I'd like to get it on 6.0 in the least just for the better permissions system it contains.
In searching for a way to update it, naturally I found this page and all the helpful info it contains. I've never been steered wrong by XDA in the past. I've always found information on this site helpful, and it works.
I've downloaded Flashtool.
I've followed all of the instruction for installation, including the annoying driver installation process for Windows 8.1.
I've downloaded multiple firmwares from Xperifirm.
I can get everything happening, and it looks to work when looking at the Flashtool screen. It says it's complete (just like the little image at the bottom of the initial post).
Nothing seems to have happened to the phone. I boot it back up and it's still running the same old 5.1.1. Flashtool runs through it's process very fast, as in a few seconds, not the half an hour suggested.
The phone came from Hong Kong as far as I can tell. It may have been a refubished phone, I can't be sure. I'm trying to get the Customised AU version 6.0 software on it.
What am I doing wrong? I don't know what else to try, and it's annoying me. PLEASE HELP.
Thanks. Paul.
Click to expand...
Click to collapse
You better ask your question in the Z5 section, you're more likely to have answers and it's the same process (sorry I don't remember guq I did at the time I had the phone).
Sent from my HTC U12+ using XDA Labs
EMJI79 said:
You better ask your question in the Z5 section, you're more likely to have answers and it's the same process (sorry I don't remember guq I did at the time I had the phone).
Sent from my HTC U12+ using XDA Labs
Click to expand...
Click to collapse
Will do.
Thanks.
Hey, man, I used 9.18.5 and it worked
Mamada. said:
Hey, man, I used 9.18.5 and it worked
Click to expand...
Click to collapse
Any idea where I can find a good copy of version 9.18.5?
Hey,
I'm experiencing an issue with Flashtool.
Last weekend I successfully rooted my Z5C with the "How to root Z5C - the new, less painful way"-guide.
Finally the Z5C was flashed with Nougat (Customized DE) and rooted with Magisk (rooted with SuperSU first, but then switched to Magisk), even with working TA partition.
After reading that the Australian Stock ROM doesn't have battery drain issues, I tried flashing that one. Unluckily I'm always getting the following error:
17/059/2019 18:59:25 - ERROR - Processing of system.sin finished with errors.
17/059/2019 18:59:25 - INFO - Ending flash session
17/059/2019 18:59:25 - ERROR - ERR_SEVERITY="MINOR";ERR_CODE="0017";ERR_DYNAMIC="80090012";
Now I can't boot my phone and TWRP seems to be gone too, so I can't restore the backup I did beforehand.
Any idea how to fix this error?
EDIT:
If anyone wonders: I managed to make it work by downloading the firmware again and using a different USB-cable on a different USB-port. Can't say which of those things exactly helped.