Develop Bugs

[TUT] How to install CyanogenMod 11 /or any other ROM on your Xperia S 6.2.b.1.96

Okay guys,
I spent a whole day yesterday to exterminate lame SONY's firmware, and get a refreshment alternation
so I gathered all tutorials, which I had followed to give my Xperia S new soul, and made this all-in-one tutorial for anyone, who's not sure how to do it.
Big thank to DooMLoRD, who's is making all this awesome tools and stuff to make our Xperias alive again.
Before proceding, Your Xperia S should run on the latest official Sony's firmware (6.2.b.1.96). Otherwise...otherwise you probably ought to update it to the latest version.
Here are the links to the sites I used. I also recommend you to check them out, because there may be a more recent version of a file:
http://forum.xda-developers.com/showthread.php?t=2555243
http://forum.xda-developers.com/showthread.php?t=2447319
http://forum.xda-developers.com/showthread.php?t=2417672
1. Bootloader unlock
Checking (source: JuniorMember's post: http://forum.xda-developers.com/showpost.php?p=44713761&postcount=14)
1.1.1. In dial pad, type in *#*#7378423#*#*
1.1.2.Go to Service Info > Configuration
1.1.3. And check the Rooting Status
If it's Bootloader unlock allowed:Yes/No, then its not unlocked. If it says NO, you're not able to unlock it.
And if it's Bootloader unlocked:Yes, then it's (already) unlocked.
Unlocking (source: DooMLoRD's tutorial)
[ before we begin unlocking bootloader ]
1.2.1 Get the IMEI code for your device: type *#06# in phone dialer to find it out; note only the digits (no dashes)
1.2.2 Download the fastboot package with usb drivers (alternate drivers if the ones in package dont work OR this)
IMPORTANT: if you are using Windows 8 you will need to enable few things to allow driver installation
1.2.3.Make sure you have a windows PC with USB cable to connect the phone
1.2.4.Power down your phone and keeping the Volume Up button pressed connect the USB cable to PC; this will trigger FASTBOOT mode and windows will start driver installation, extract the above package and point the driver install to that location (usb_driver) folder.
If a phone enters but does not stay in a fastboot mode:I had that kind of problem, but I'm not sure how I actually fixed it; I only remember I did that:
1.2.4.1. Download and install Flashtool . After Installing, go to the folder where fastboot is installed and look for drivers folder; there you'll find Flashtool-drivers.exe. Install that: Be aware that there are Flashboot and Fastboot drivers at the bottom or at the top of the list Check also your phone's name.
1.2.4.2. If still does not work go to Device manager, trigger fastboot mode, connect to your computer, and quickly (when S1 Boot or sth like that appers in Device Manager) click with right mouse button (go to properties), then update driver and point to (usb_driver) folder in fastboot_with_Android_USB_file folder -> step 1.3.6.
1.2.5. Once drivers are installed just disconnect cable and power on device
[ how to unlock ] (official way)
1.3.1 First, you should confirm that it is possible to unlock the boot loader of your phone by checking the service menu: steps 1.1.1 - 1.1.3
1.3.2 Go to: http://unlockbootloader.sonymobile.com/ and read everything!
1.3.3 At the bottom click 'Start Unlocking the Bootloader'. Scroll to the bottom of the page and click "Continue" You will get numerous prompts, read all info and if you agree, click on "Accept"/"OK"/"Proceed"
1.3.4 Finally you will get a "Create Unlock request" page, enter your IMEI (sometimes the last digit needs to be removed for this to work), name and email address
1.3.5 You should now receive your unique unlock key via EMAIL, SAVE THIS KEY SAFELY
1.3.6 Extract fastboot_with_Android_USB_file.rar and open fastboot folder
1.3.7 Hold SHIFT and right click on the background of the folder Select 'Open command window here'
1.3.8 Connect your phone in fastboot mode (turn phone off, hold Volume UP button and plug in USB Cable) [make sure drivers are installed as explained above)
1.3.9 In the cmd windows type in fastboot.exe -i 0x0fce getvar version
1.3.10 If a value is returned (it will return 0.5), it means the phone is correctly connected
1.3.11 Type in fastboot.exe -i 0x0fce oem unlock 0xKEY and replace KEY with the key which u received earlier.
1.3.12 You're device should now be bootloader unlocked. You can check by followin steps 1.1.1 - 1.1.3.
2. Root (source: DooMLoRD's tutorial)
2.3.1 Download the three files from the download section in this post.
2.3.2 Open FlashTool and flash the XperiaS_LT26i_6.2.B.0.211_KernelOnly.ftf - 6.36 MB file, this is JUST the kernel of an older firmware which was rootable.
2.3.3 How to flash Put XperiaS_LT26i_6.2.B.0.211_KernelOnly.ftf to firware folder, which you can find in Fastboot's installation folder. Then hit the lighting strike, select Flashboot mode and select the kernel and hit flash and follow instructions how to enter flashmode.
2.3.4 Now once flashing is done reboot device and connect to PC in usb debuggin mode
2.3.5 CLOSE FLASHTOOL <<< VVVIMP STEP (Very very very important step it took me some time to figure out its meaning)
2.3.6 Extract the file DooMLoRD_Easy-Rooting-Toolkit_v18_perf-event-exploit.zip to root directory on c:\
execute runme_ file corresponding to your OS on desktop PC, this will execute a SPECIAL version of DooMLoRDs easy rooting toolkit <<< VVVIMP STEP
2.3.7 the above step is crucial! if you use any older version of the toolkit then IT WILL NOT WORK!
2.3.8 after rooting is over the device will restart
2.3.9 you can verify if device is rooted by checking for SuperSU app (it is the newest version)
2.3.10 once that's done, power down device and open FlashTool again
2.3.11 now flash XperiaS_LT26i_6.2.B.1.96_KernelOnly.ftf - 6.33 MB file to get back to the true kernel for the firmware
that's it after flashing is done just disconnect and power on device and enjoy rooted phone! Check with Root Checker app from GPlay.
3. CWM Recovery (source: hm9408's thorough version of DooMLoRD's tutorial)
3.1 Go to google play and download busybox. Once installed, open the app and tap install Also, make sure, you have SuperSU installed.
3.2. This should be relatively easy now. Your phone is now rooted, and you will now flash CWM Recovery on your phone. For this, hm9408 found a quick installer by DooMLoRD.
3.3 Just extract it anywhere, run it (cwm-install-en.bat, press Enter 3 times and it will start) while your phone is connected via USB, and you should be just fine. I had to do this step twice, because I didn't know you have to grant something with SuperSU. So during the process, watch the phone's screen.
3.4 You know CWM was flashed correctly when you shut down your phone, turn it on and your see the LED turns on BLUE when the Sony logo comes up. When it does, press the Volume Up button and the LED should turn GREEN for a couple of seconds, then boot into Recovery.
4. Installing custom ROM and gapps (google apps)
There's a link toCyanogenMod 11 beta 3 by RaymanFX which has already included kernel.
Other ROMs may not have included kernel, so you'll have to (1) flash it with Flastool, if it has kernel extension or (2) install it via recovery, it it has .zip extension.
4.1 Copy your ROM and gapps (their extensions have to be .zip.
4.2 Boot into recovery (step 3.4).
4.3 Navigate (with volume + and -, and power to select) to install zip, then select the file of you rom, install it, then install also the gapps by selecting the gapps.zip.
4.4. This is the most important step, DO NOT SKIP IT AT ALL COSTS For God's sake, in the main menu, wipe the cache and partitions and dalvik's cache. (I'm not sure if it's available to wipe dalvik's cache, but if it is, wipe it).
I forgot to wipe, and, holy cow, almost lost my pants, because phone didn't start, there was only sony's logo, slowly passing away again and again.
Well if that happens, look for an Xperia S firmware (e.g.) and appropriate kernel (e.g.), flash them via flashtool and wipe your sweat .

I think for a 2 years old phone, everybody should already know how to do this.
Or i think most of the people here on Xperia S XDA do already know how to do this.

xDroidZz said:
I think for a 2 years old phone, everybody should already know how to do this.
Or i think most of the people here on Xperia S XDA do already know how to do this.
Click to expand...
Click to collapse
Lol ya.

Sure?
xDroidZz said:
I think for a 2 years old phone, everybody should already know how to do this.
Or i think most of the people here on Xperia S XDA do already know how to do this.
Click to expand...
Click to collapse
I've had it for 2 years, but spent a whole day yesterday to install CM, because I struggled with fastboot drivers for 4hs, then 1h to root it, then another 2hs to properly install CWMrecovery, because I didn't know I have to have BusyBox installed and then I didn't wipe the cache and had to do everything again. And don't say me everybody should know that, because there are people who does not even try to do that, because then don't konw where to start and nothing.
Cheers!

Joej970 said:
I've had it for 2 years, but spent a whole day yesterday to install CM, because I struggled with fastboot drivers for 4hs, then 1h to root it, then another 2hs to properly install CWMrecovery, because I didn't know I have to have BusyBox installed and then I didn't wipe the cache and had to do everything again. And don't say me everybody should know that, because there are people who does not even try to do that, because then don't konw where to start and nothing.
Cheers!
Click to expand...
Click to collapse
are you kidding me? it takes me max 1 hour to read tutorial, unlock BL, flash custom kernel and flasch CM rom :laugh:

Joej970 said:
I've had it for 2 years, but spent a whole day yesterday to install CM, because I struggled with fastboot drivers for 4hs, then 1h to root it, then another 2hs to properly install CWMrecovery, because I didn't know I have to have BusyBox installed and then I didn't wipe the cache and had to do everything again. And don't say me everybody should know that, because there are people who does not even try to do that, because then don't konw where to start and nothing.
Cheers!
Click to expand...
Click to collapse
Nah. Max is 1H. there are alot of TUT already. but thanks anyways for this TUT helps alot of people who are actually new to this device

dobi235 said:
are you kidding me? it takes me max 1 hour to read tutorial, unlock BL, flash custom kernel and flasch CM rom :laugh:
Click to expand...
Click to collapse
It takes you one hour once you exactly know how to do it and in case you already have all files downloaded.
And about tutorials: they're often incomplete. In my case, I struggled with finding drivers for fastboot and making them work 4hs. The unlock tutorial says to install one drivers then try another, but none of them worked. So it took me time to search forums and find something out. Here, I wrote what I'd done, so anyone else would know what to do.
Edit: every tutorial about unlocking says Windows should report unsuccessful installation when you connect the device in fast boot mode. Well, my didn't report that, so I wasn't able to point to the usb_folder. And then phone booted up after 5secs in fastboot.

Joej970 said:
It takes you one hour once you exactly know how to do it and in case you already have all files downloaded.
And about tutorials: they're often incomplete. In my case, I struggled with finding drivers for fastboot and making them work 4hs. The unlock tutorial says to install one drivers then try another, but none of them worked. So it took me time to search forums and find something out. Here, I wrote what I'd done, so anyone else would know what to do.
Edit: every tutorial about unlocking says Windows should report unsuccessful installation when you connect the device in fast boot mode. Well, my didn't report that, so I wasn't able to point to the usb_folder. And then phone booted up after 5secs in fastboot.
Click to expand...
Click to collapse
no it took me hour to search for tutuorials (doom has for root and for unlocking BL too), read that, backup TA partiton, unlock, root, flash... DONE

I needed an whole afternoon, too! If you have to read everything from beginning and you are not able even to deal with the technical terms it needs long time. So, if I wouldn't have done it before, this tutorial would have been very useful to me :good:

magician
dobi235 said:
no it took me hour to search for tutuorials (doom has for root and for unlocking BL too), read that, backup TA partiton, unlock, root, flash... DONE
Click to expand...
Click to collapse
Well okay. Then write that down to a paper and stick it to a mirror, so you'll see your extraordinary achievement every time you wake up, and be proud of yourself, cause you did all that for the fisrt time in only one hour, although everyone else needed an afternoon. You're probably the smartest person I've ever seen, cause you apparently do magic :good:
Repair shops should totally hire you, since they often need an eternity to do their job.
Cheers

Joej970 said:
Well okay. Then write that down to a paper and stick it to a mirror, so you'll see your extraordinary achievement every time you wake up, and be proud of yourself, cause you did all that for the fisrt time in only one hour, although everyone else needed an afternoon. You're probably the smartest person I've ever seen, cause you apparently do magic :good:
Repair shops should totally hire you, since they often need an eternity to do their job.
Cheers
Click to expand...
Click to collapse
i only wanted to say that this thread is completely unnecessary.. this phone is more than 2 years old... last update was i think 1year ago.. so there is nothing new... tutorials for unlocking BL (2nd March 2012) and for rooting (17th June 2013) are here for more than a year...and tutorial for instaling CM you can find in almost every CM thread... thats all I wanted to say :victory:... have a nice day

It is kinda necessary..
Some people still dont know how to flash these roms...And then end up spamming other threads...:/

Joej970 said:
Okay guys,
I spent a whole day yesterday to exterminate lame SONY's firmware, and get a refreshment alternation
so I gathered all tutorials, which I had followed to give my Xperia S new soul, and made this all-in-one tutorial for anyone, who's not sure how to do it.
Big thank to DooMLoRD, who's is making all this awesome tools and stuff to make our Xperias alive again.
Click to expand...
Click to collapse
Your method is long and unnecessarily beating around the bush. Here's a much quicker way (how I did it in less than half an hour):
1) Copy the ROM zip to your internal storage
2) Unlock bootloader with Sony's info on their site.
3) Extract boot.img from the ROM zip / kernel zip.
4) In fastboot mode,
Code:
fastboot flash boot boot.img
fastboot reboot
5) Go into recovery while it's rebooting, wipe everything & flash the ROM zip.
TBH, DoomLord's stuff is not required, never really was for me..
Sure, it's good stuff, but not required in this case..

The tutorial is good, it's just unfortunate, is that after more than two years, yet no one has been able to unlock the bootloader problem that allows not be unlocked.
Sent from my LT26i using XDA Premium 4 mobile app

Great_Geek said:
Your method is long and unnecessarily beating around the bush. Here's a much quicker way (how I did it in less than half an hour):
1) Copy the ROM zip to your internal storage
2) Unlock bootloader with Sony's info on their site.
3) Extract boot.img from the ROM zip / kernel zip.
4) In fastboot mode,
Code:
fastboot flash boot boot.img
fastboot reboot
5) Go into recovery while it's rebooting, wipe everything & flash the ROM zip.
TBH, DoomLord's stuff is not required, never really was for me..
Sure, it's good stuff, but not required in this case..
Click to expand...
Click to collapse
Hey, hey, hey,
where do you type that code in? In terminal emulator on a phone or maybe cmd on a computer? I've seen a lot of tutorials ordering to type a code, but none of them actually explained how and where you have to write it.
Thankss!

Joej970 said:
Hey, hey, hey,
where do you type that code in? In terminal emulator on a phone or maybe cmd on a computer? I've seen a lot of tutorials ordering to type a code, but none of them actually explained how and where you have to write it.
Thankss!
Click to expand...
Click to collapse
You use fastboot.exe or the fastboot binary for linux, same one that you used for unlocking bootloader..
Finding something to type into terminal emulator is pretty rare, and it'll usually be specified that you need to type it there..

About using flash tool in my sony xperia m dual c2005

I have some doubts about the using of flash tool.
1. Is it necessary to unlock the boatloader before flashing my phone?
2. Is it necessary to tick the usb debugging before using flash tool?
3. When i use flash tool, after some time it shows failed in my xperia m dual c2005. I am curious to know the reason behind it..
Any body please help me to clear my doubts....

N RAM said:
I have some doubts about the using of flash tool.
1. Is it necessary to unlock the boatloader before flashing my phone?
2. Is it necessary to tick the usb debugging before using flash tool?
3. When i use flash tool, after some time it shows failed in my xperia m dual c2005. I am curious to know the reason behind it..
Any body please help me to clear my doubts....
Click to expand...
Click to collapse
Yes the bootloader obviously should be unlocked before you do the flashing stuff!Flashtool works for me and the state of usb debugging never affected its functionality ! Make sure you have all the drivers properly installed!

ojas12345 said:
Yes the bootloader obviously should be unlocked before you do the flashing stuff!Flashtool works for me and the state of usb debugging never affected its functionality ! Make sure you have all the drivers properly installed!
Click to expand...
Click to collapse
Thanks bro..:good:
Dude one more simple doubt. Is it possible for you to tell me how to install the drivers in my win 7?
Now I am facing another problem. I just tried to restore my xperia m dual c2005. But it didn't go well. I saw my xperia waves got stucked. So i just removed my battery an replaced it. When I switched on my phone it only shows SONY logo. I tried to repair my software by using PCC and Xperia Companion. It shows error messages. Then i showed it to a mobile service agent in a local mobile shop. He told me that m dual c2005 model had a sony only memory. So they cannot do it because the memory can't be re-writeted in this model. Is that true? Or is there any other better option to resolve my phone's issue?
Please help me bro....:crying:

N RAM said:
Thanks bro..:good:
Dude one more simple doubt. Is it possible for you to tell me how to install the drivers in my win 7?
Now I am facing another problem. I just tried to restore my xperia m dual c2005. But it didn't go well. I saw my xperia waves got stucked. So i just removed my battery an replaced it. When I switched on my phone it only shows SONY logo. I tried to repair my software by using PCC and Xperia Companion. It shows error messages. Then i showed it to a mobile service agent in a local mobile shop. He told me that m dual c2005 model had a sony only memory. So they cannot do it because the memory can't be re-writeted in this model. Is that true? Or is there any other better option to resolve my phone's issue?
Please help me bro....:crying:
Click to expand...
Click to collapse
To Install the drivers
I think you might be able to solve this problem! The problem is with your partitions.So follow:
first of all install fastboot and adb drivers from: http://forum.xda-developers.com/showthread.php?p=48915118
go to device manager and verify that and android device interface or something like that appears.
If it doesnt then s1 boot device will appear as unknown device , right click on that and update device driver and then select the option let me pick from drivers on my computer .
After that select android device then dont select anything , itll get autoselected and click next!
now your device should appear in device manager!
To restore the system completely
Install a recovery for the device by the following procedure :
first download twrp from https://twrp.me/devices/sonyxperiam.html, rename it to recovery.img
go to cmd with admin rights in the folder in which recovery is put
(flash the recovery in boot sector)
type :
fastboot flash boot recovery.img
now boot the phone up the recovery should automatically open up, it may get stuck for some time but only once it will so be patient,;
go to wipe, then advanced wipe! select every option and micro sd,internal storage and usb-otg are optional
then swipe to wipe , it will show that it failed but dont worry some partitions are of sort that they show error now after this the problem should be resolved , after this flash a rom of your choice or restore a dual stock firmware backup (note: you cannot restore backups which were made from cwm , for that flash philz or cwm recovery)
Please report and hit thanks if i helped you!

ojas12345 said:
To Install the drivers
I think you might be able to solve this problem! The problem is with your partitions.So follow:
first of all install fastboot and adb drivers from: http://forum.xda-developers.com/showthread.php?p=48915118
go to device manager and verify that and android device interface or something like that appears.
If it doesnt then s1 boot device will appear as unknown device , right click on that and update device driver and then select the option let me pick from drivers on my computer .
After that select android device then dont select anything , itll get autoselected and click next!
now your device should appear in device manager!
To restore the system completely
Install a recovery for the device by the following procedure :
first download twrp from https://twrp.me/devices/sonyxperiam.html, rename it to recovery.img
go to cmd with admin rights in the folder in which recovery is put
(flash the recovery in boot sector)
type :
fastboot flash boot recovery.img
now boot the phone up the recovery should automatically open up, it may get stuck for some time but only once it will so be patient,;
go to wipe, then advanced wipe! select every option and micro sd,internal storage and usb-otg are optional
then swipe to wipe , it will show that it failed but dont worry some partitions are of sort that they show error now after this the problem should be resolved , after this flash a rom of your choice or restore a dual stock firmware backup (note: you cannot restore backups which were made from cwm , for that flash philz or cwm recovery)
Please report and hit thanks if i helped you!
Click to expand...
Click to collapse
Thanks dude... Are you sure about this idea?
My phone is not an Indian phone. It is from Dubai. Will this country change damage my phone's main board when I boot it?
And some more doubts are remaining... May I please clear it with you....
Which will be the best flashtool?
Emma tool provided by Sony or flashtool-0.9.18.1 or flashtool-0.9.21.0
When do I need to connect my handset to the computer? Is it before when I go to cmd to type fastboot flash boot recovery.img ?
Whether I need to install flash tool before installing device drivers?
Please help me to clear all my doubts....

N RAM said:
Thanks bro..:good:
Dude one more simple doubt. Is it possible for you to tell me how to install the drivers in my win 7?
Now I am facing another problem. I just tried to restore my xperia m dual c2005. But it didn't go well. I saw my xperia waves got stucked. So i just removed my battery an replaced it. When I switched on my phone it only shows SONY logo. I tried to repair my software by using PCC and Xperia Companion. It shows error messages. Then i showed it to a mobile service agent in a local mobile shop. He told me that m dual c2005 model had a sony only memory. So they cannot do it because the memory can't be re-writeted in this model. Is that true? Or is there any other better option to resolve my phone's issue?
Please help me bro....:crying:
Click to expand...
Click to collapse
N RAM said:
Thanks dude... Are you sure about this idea?
My phone is not an Indian phone. It is from Dubai. Will this country change damage my phone's main board when I boot it?
And some more doubts are remaining... May I please clear it with you....
Which will be the best flashtool?
Emma tool provided by Sony or flashtool-0.9.18.1 or flashtool-0.9.21.0
When do I need to connect my handset to the computer? Is it before when I go to cmd to type fastboot flash boot recovery.img ?
Whether I need to install flash tool before installing device drivers?
Please help me to clear all my doubts....
Click to expand...
Click to collapse
The country doesnt matter you may flash any country's generic rom,mine was indian but I flashed brazillian..
And about the flashtool I dont think emma is good , i prefer flashtool any version...if you find the latest not working then you may try the second latest but 99% it does work good..
Most important : You need to connect your device in fastboot before installing drivers and flash the boot partition by those command so go here on how to boot in fastboot mode http://www.theandroidsoul.com/boot-sony-xperia-m-fastboot-mode-51835/
try and report ...
All the best:good:

ojas12345 said:
The country doesnt matter you may flash any country's generic rom,mine was indian but I flashed brazillian..
And about the flashtool I dont think emma is good , i prefer flashtool any version...if you find the latest not working then you may try the second latest but 99% it does work good..
try and report ...
All the best:good:
Click to expand...
Click to collapse
You are really awesome!!
For this do I need to unlock the bootloader?
Yeah. I will report about our experiment after trying it...:good:
Is it possible for me to relock bootloader? If yes, please explain me about that method...

N RAM said:
You are really awesome!!
For this do I need to unlock the bootloader?
Yeah. I will report about our experiment after trying it...:good:
Is it possible for me to relock bootloader? If yes, please explain me about that method...
Click to expand...
Click to collapse
yes you will have to unlock bootloader and for that too i suggest you use flashtool because it does the work in seconds,!
and for relocking i dont there's any method to relock bootloader , u dont need to do that after all!
It enables you to flash modes and other cool stuff! even if you dont wanna do that then dont touch it !flash a cyanogenmod recovery,which is quite basic and wont modify anything that may harm your phone...
All the best

What will be the difference between the firmwares C2005_15.5.A.1.5_CE.ftf and C2005_15.5.A.1.5_DE.rar?
Which will be the best for me to download?

ojas12345 said:
To Install the drivers
I think you might be able to solve this problem! The problem is with your partitions.So follow:
first of all install fastboot and adb drivers from: http://forum.xda-developers.com/showthread.php?p=48915118
go to device manager and verify that and android device interface or something like that appears.
If it doesnt then s1 boot device will appear as unknown device , right click on that and update device driver and then select the option let me pick from drivers on my computer .
After that select android device then dont select anything , itll get autoselected and click next!
now your device should appear in device manager!
To restore the system completely
Install a recovery for the device by the following procedure :
first download twrp from https://twrp.me/devices/sonyxperiam.html, rename it to recovery.img
go to cmd with admin rights in the folder in which recovery is put
(flash the recovery in boot sector)
type :
fastboot flash boot recovery.img
now boot the phone up the recovery should automatically open up, it may get stuck for some time but only once it will so be patient,;
go to wipe, then advanced wipe! select every option and micro sd,internal storage and usb-otg are optional
then swipe to wipe , it will show that it failed but dont worry some partitions are of sort that they show error now after this the problem should be resolved , after this flash a rom of your choice or restore a dual stock firmware backup (note: you cannot restore backups which were made from cwm , for that flash philz or cwm recovery)
Please report and hit thanks if i helped you!
Click to expand...
Click to collapse
Which is the best site for downloading latest firmware?

N RAM said:
Which is the best site for downloading latest firmware?
Click to expand...
Click to collapse
intead of flashing firmware ,it is better to flash a backup because , no chances of error
download the backup for your device from here and restore it via cwm based recovery like philz or cwm itselg
http://forum.xda-developers.com/showthread.php?t=2703161

ojas12345 said:
yes you will have to unlock bootloader and for that too i suggest you use flashtool because it does the work in seconds,!
and for relocking i dont there's any method to relock bootloader , u dont need to do that after all!
It enables you to flash modes and other cool stuff! even if you dont wanna do that then dont touch it !flash a cyanogenmod recovery,which is quite basic and wont modify anything that may harm your phone...
All the best
Click to expand...
Click to collapse
I tried to flash my xperia m dual c2005. Its only showing like the picture for long time.
what will be this? please reply me fast...

N RAM said:
I tried to flash my xperia m dual c2005. Its only showing like the picture for long time.
what will be this? please reply me fast...
Click to expand...
Click to collapse
wait for some time i think it'll take time to do that or else flash a backup after flashing a cwm based recovery!

ojas12345 said:
wait for some time i think it'll take time to do that or else flash a backup after flashing a cwm based recovery!
Click to expand...
Click to collapse
what is the meaning of that red writings?

N RAM said:
what is the meaning of that red writings?
Click to expand...
Click to collapse
I never faced that kind of a thing , make sure that you are flashing the right file!
You have unlocked your bootloader?
Again I say better flash a recovery then a backup ,its much easier.

ojas12345 said:
I never faced that kind of a thing , make sure that you are flashing the right file!
You have unlocked your bootloader?
Again I say better flash a recovery then a backup ,its much easier.
Click to expand...
Click to collapse
My phone is only showing SONY logo. So is it possible for this recovery? If yes, please tell me the correct tutorial for that and if possible any video tutorial so that i can understand it correctly...

not working
ojas12345 said:
To Install the drivers
I think you might be able to solve this problem! The problem is with your partitions.So follow:
first of all install fastboot and adb drivers from: http://forum.xda-developers.com/showthread.php?p=48915118
go to device manager and verify that and android device interface or something like that appears.
If it doesnt then s1 boot device will appear as unknown device , right click on that and update device driver and then select the option let me pick from drivers on my computer .
After that select android device then dont select anything , itll get autoselected and click next!
now your device should appear in device manager!
To restore the system completely
Install a recovery for the device by the following procedure :
first download twrp from https://twrp.me/devices/sonyxperiam.html, rename it to recovery.img
go to cmd with admin rights in the folder in which recovery is put
(flash the recovery in boot sector)
type :
fastboot flash boot recovery.img
now boot the phone up the recovery should automatically open up, it may get stuck for some time but only once it will so be patient,;
go to wipe, then advanced wipe! select every option and micro sd,internal storage and usb-otg are optional
then swipe to wipe , it will show that it failed but dont worry some partitions are of sort that they show error now after this the problem should be resolved , after this flash a rom of your choice or restore a dual stock firmware backup (note: you cannot restore backups which were made from cwm , for that flash philz or cwm recovery)
Please report and hit thanks if i helped you!
Click to expand...
Click to collapse
i am getting this error :
C:\Fastboot\android-sdk-windows\tools>fastboot flash boot recovery.img
sending 'boot' (11208 KB)...
FAILED (status read failed (Too many links))
finished. total time: -0.000s

Huge problem

Hey,
I am running the exodus rom on my oneplus 3 and after todays update I got a huge problem. My screen fails to wake up, the phone works normal I think but the screen is just black..
How do I solve a problem like this?
I have tried turning it on and off again, it did not work

Fast And Pro said:
Hey,
I am running the exodus rom on my oneplus 3 and after todays update I got a huge problem. My screen fails to wake up, the phone works normal I think but the screen is just black..
How do I solve a problem like this?
I have tried turning it on and off again, it did not work
Click to expand...
Click to collapse
dirty flash?
may be clean flash will help

JumboMan said:
dirty flash?
may be clean flash will help
Click to expand...
Click to collapse
Idk what happend
but the screen works again but my phone is now bricked and the usual guides to unbrick do not work.
This is the status of my 1+3
Bootloader: unlocked and I can boot in the bootloader
my device is recognized by my pc
I cannot enter TWRP and I cant flash TWRP.
When I try to flash it CMD says that its flashed but I still cant boot in twrp, I get a random screen with md5 checksum and some fails.
Can someone help me?

Fast And Pro said:
Idk what happend
but the screen works again but my phone is now bricked and the usual guides to unbrick do not work.
This is the status of my 1+3
Bootloader: unlocked and I can boot in the bootloader
my device is recognized by my pc
I cannot enter TWRP and I cant flash TWRP.
When I try to flash it CMD says that its flashed but I still cant boot in twrp, I get a random screen with md5 checksum and some fails.
Can someone help me?
Click to expand...
Click to collapse
I don't have answer for question.
it looks like you have some serious problem with your phone.
may be some experienced user will help you.
I think you should approach Naman bhalla as he made guide to unbrick so he may know in detail

JumboMan said:
I don't have answer for question.
it looks like you have some serious problem with your phone.
may be some experienced user will help you.
I think you should approach Naman bhalla as he made guide to unbrick so he may know in detail
Click to expand...
Click to collapse
I found a fix on the forum and this explained what my problem was
On the screen when the phone failed to md5 checksum, you've got several partition failed right? in red text.
- download this : https://www.androidfilehost.com/?fid=24591000424942573
and then extract.
- download platform tools attached below. extract in the same folder with first file you've downloaded.
- Boot your phone to fastboot mode, plug your usb, make sure adb and fastboot driver are installed.
- on the folder, hold shift and right click, click open command here
- type fastboot devices
- make sure your serial number appear.
- now flash the img of the missing file according to the partition in red text on your ms5 checksum failed one by one.
- e.g. "fastboot flash boot_aging boot_aging.img.
- make sure you flash all the missing partition.
- type fastboot reboot.
this will boot you to oos 3.1.2.
unfortunately I couldn't extract the newest oos dat. data. but you could always take the OTA
goodluck mate. sorry for my english

Fast And Pro said:
I found a fix on the forum and this explained what my problem was
On the screen when the phone failed to md5 checksum, you've got several partition failed right? in red text.
- download this : https://www.androidfilehost.com/?fid=24591000424942573
and then extract.
- download platform tools attached below. extract in the same folder with first file you've downloaded.
- Boot your phone to fastboot mode, plug your usb, make sure adb and fastboot driver are installed.
- on the folder, hold shift and right click, click open command here
- type fastboot devices
- make sure your serial number appear.
- now flash the img of the missing file according to the partition in red text on your ms5 checksum failed one by one.
- e.g. "fastboot flash boot_aging boot_aging.img.
- make sure you flash all the missing partition.
- type fastboot reboot.
this will boot you to oos 3.1.2.
unfortunately I couldn't extract the newest oos dat. data. but you could always take the OTA
goodluck mate. sorry for my english
Click to expand...
Click to collapse
Its good.
Self help is best help

Lenovo K8 Note Red State Bootloop After Flashing Custom Recovery

Hello Guys,
The issue is that i wanted to root my lenovo k8 note so follow this link "https://forum.xda-developers.com/android/development/tutorials-how-to-root-lenovo-k8-note-t3685502", Everything works file but in last rooting step no. 9
9. If you see internal storage 0mb Then GoTo Wipe and FORMAT DATA once & reboot to recovery
but in my device there has memory 59999mb so i ignored and reboot using twrp but it says no OS installed
and shows orange state, then i format phone using twrp but nothing happens again orange state and no os installed.
then i found another article with same issue "https://forum.xda-developers.com/android/help/lenovo-k8-note-stuck-boot-logo-flashing-t3751324/post75974342#post75974342" and found this
The bootlogo issue.
Hey! I read your post regarding your k8 note being stuck at the bootlogo.
Consider that you can still use TWRP, boot into it.
Then go ahead and download the SuperSU zip on your PC/laptop and connect your phone with a USB. You might be able to see the SD card folders on your PC, then you can just copy and paste it to the internal sd and flash it. You'll be good to go. If that doesn't work, in the TWRP Mode, go to advanced and select ADB sideload. You can now flash using ADB sideload.
Search for tutorials on ADB sideload. It's easy and that should work.
Click to expand...
Click to collapse
solution over there and flash supersu but nothing happens.
After so many try i locked oem bootloader in fastboot using command "fastboot oem lock", after this my lenovo k8 note show Red State.
Now i am not able to do anythig please help me out.
Basically my device is stuck at the bootloop with the
Red State
=> "Your Device has fail to pass verification and may not work properly
your device will boot in 10 sec trusted
Your device will boot in 5 seconds"
definitely I must have screwed up something.
Please help me to boot my Lenovo K8 note in normal mode.
Thanks

beingfhd said:
Hello Guys,
The issue is that i wanted to root my lenovo k8 note so follow this link "https://forum.xda-developers.com/android/development/tutorials-how-to-root-lenovo-k8-note-t3685502", Everything works file but in last rooting step no. 9
9. If you see internal storage 0mb Then GoTo Wipe and FORMAT DATA once & reboot to recovery
but in my device there has memory 59999mb so i ignored and reboot using twrp but it says no OS installed
and shows orange state, then i format phone using twrp but nothing happens again orange state and no os installed.
then i found another article with same issue "https://forum.xda-developers.com/an...-flashing-t3751324/post75974342#post75974342" and found this solution over there and flash supersu but nothing happens.
After so many try i locked oem bootloader in fastboot using command "fastboot oem lock", after this my lenovo k8 note show Red State.
Now i am not able to do anythig please help me out.
Basically my device is stuck at the bootloop with the
Red State
=> "Your Device has fail to pass verification and may not work properly
your device will boot in 10 sec trusted
Your device will boot in 5 seconds"
definitely I must have screwed up something.
Please help me to boot my Lenovo K8 note in normal mode.
Thanks
Click to expand...
Click to collapse
Are you okay with losing your data on your phone? If yes then go ahead and flash stock ROM with sp flash tool. And about your problem, I guess you wiped the /system partition as well that's why it was showing no os installed.
Another thing is that if you install twrp Do not boot up your phone, boot up into twrp by pressing volume up and power button at the same time you'll need to flash magisk or supersu so that twrp can modify partition correctly.

Thanks
Anas Rahman said:
Are you okay with losing your data on your phone? If yes then go ahead and flash stock ROM with sp flash tool. And about your problem, I guess you wiped the /system partition as well that's why it was showing no os installed.
Another thing is that if you install twrp Do not boot up your phone, boot up into twrp by pressing volume up and power button at the same time you'll need to flash magisk or supersu so that twrp can modify partition correctly.
Click to expand...
Click to collapse
Thanks for the reply but i recovered it using flash stock rom.
But i have another ques that can i flash twrp without oem unlock?

beingfhd said:
Thanks for the reply but i recovered it using flash stock rom.
But i have another ques that can i flash twrp without oem unlock?
Click to expand...
Click to collapse
No you can't

k8 note stuck on bootloop...??
need help.....my k8 note was running oreo....thn i downgraded to nougat...duo to bugs on oreo... thn i was facing more problems... so i decided to flash oreo again. ... i was trying to flash...but i was getting some brom error...so i thought it might be due to unlocked bootloader... so i tried to lock it.. and then try... and the system got deleted.... i cant even access fastboot... but device is detecting on sp flash tool... but getting the same error... help buddy... its urgent.. my device is not turning on... but the led is working....

DeepRBasak said:
need help.....my k8 note was running oreo....thn i downgraded to nougat...duo to bugs on oreo... thn i was facing more problems... so i decided to flash oreo again. ... i was trying to flash...but i was getting some brom error...so i thought it might be due to unlocked bootloader... so i tried to lock it.. and then try... and the system got deleted.... i cant even access fastboot... but device is detecting on sp flash tool... but getting the same error... help buddy... its urgent.. my device is not turning on... but the led is working....
Click to expand...
Click to collapse
This might be helpful https://forum.xda-developers.com/k8-note/how-to/lenovo-k8-note-xt1902-3-fix-dead-hard-t3791839

thank u somuch am also mobile sevice man it help full for me
Anas Rahman said:
Are you okay with losing your data on your phone? If yes then go ahead and flash stock ROM with sp flash tool. And about your problem, I guess you wiped the /system partition as well that's why it was showing no os installed.
Another thing is that if you install twrp Do not boot up your phone, boot up into twrp by pressing volume up and power button at the same time you'll need to flash magisk or supersu so that twrp can modify partition correctly.
Click to expand...
Click to collapse

I have the same problem. please help us!

HARDROCK2614 said:
I have the same problem. please help us!
Click to expand...
Click to collapse
What problem do you have, please describe

I have lost all my mind and need serious help.
Recently, the march update came. i forgot that rooted phone should not be updated by the OTA update. And i did. As a result i got stuck in a bootloop. Then I had to use the oreo ROM from this forum and flashed it using SP Flash tool. It was a successfull flash. Then I used Maui META to write the IMEI for both sim. That was successfull too(Wifi and bluetooth addresses were working by themselves and i didnt write the serial number of the phone).
After working nicely for three days, i was using Whatsapp and a friend of mine sent me a .pptx file (powerpoint presentation). I opened it using WPS office app. I opened it multiple times in morning with no problems. But in the afternoon at about 2.53 PM while i was in my car, i was unable to open the file. The phone hanged. It heated up. To get out of the hang, i restarted the phone using the power button. IT DID NOT START. All it showed was the lenovo logo screen. And after doing more restarts, the phone went completely blank.
Now i cannot start it, or charge it. So i thought of flashing it again. But when i connect it to my PC, it keeps CONNECTING and DISCONNECTING. what i saw in the device manager was that the driver keeps changing very fast betwee MTK USB PORT and PRELOADER.
I found the solution to be updating the drivers manually. I did. Now the driver shows only DA USB VCOM and when it changes, it goes invisible in the PC and then appears back. Now when i start flashing, the first red progress bar appears as: Download DA 100%. and the flash hangs. After some time, this error will popup: ERROR: STATUS_UNKNOWN_STORAGE_TYPE (0xC0040009)
Please someone help me.

custom619 said:
Recently, the march update came. i forgot that rooted phone should not be updated by the OTA update. And i did. As a result i got stuck in a bootloop. Then I had to use the oreo ROM from this forum and flashed it using SP Flash tool. It was a successfull flash. Then I used Maui META to write the IMEI for both sim. That was successfull too(Wifi and bluetooth addresses were working by themselves and i didnt write the serial number of the phone).
After working nicely for three days, i was using Whatsapp and a friend of mine sent me a .pptx file (powerpoint presentation). I opened it using WPS office app. I opened it multiple times in morning with no problems. But in the afternoon at about 2.53 PM while i was in my car, i was unable to open the file. The phone hanged. It heated up. To get out of the hang, i restarted the phone using the power button. IT DID NOT START. All it showed was the lenovo logo screen. And after doing more restarts, the phone went completely blank.
Now i cannot start it, or charge it. So i thought of flashing it again. But when i connect it to my PC, it keeps CONNECTING and DISCONNECTING. what i saw in the device manager was that the driver keeps changing very fast betwee MTK USB PORT and PRELOADER.
I found the solution to be updating the drivers manually. I did. Now the driver shows only DA USB VCOM and when it changes, it goes invisible in the PC and then appears back. Now when i start flashing, the first red progress bar appears as: Download DA 100%. and the flash hangs. After some time, this error will popup: ERROR: STATUS_UNKNOWN_STORAGE_TYPE (0xC0040009)
Please someone help me.
Click to expand...
Click to collapse
I couldn't find more about the problem online, can you please upload a screenshot of the error. Try using the latest version of SP Flash Tool and see if the problem persists

I have lost all my mind and need serious help.
here are the screenshots. Note that the battery is in the phone always because i am unable to open the back cover. During the flashing process, i did not press the vol - button.
https://ibb.co/sq8knnj
https://ibb.co/VjqKQm3
https://ibb.co/4VkVPjs
https://ibb.co/cw2BzLC
https://ibb.co/kcjjJ74
Now in the following screenshots, i kept the vol - button pressed down. Note that the driver is stuck at preloader and not DA. Also the first bar is yellow color in both these cases. However, in the above situation, multiple files were flashed. But in this below situation, only this so called "flash" was done; that too unsucessful in the end.
https://ibb.co/1QKtsCb
https://ibb.co/Ssj58Zd

custom619 said:
here are the screenshots. Note that the battery is in the phone always because i am unable to open the back cover. During the flashing process, i did not press the vol - button.
https://ibb.co/sq8knnj
https://ibb.co/VjqKQm3
https://ibb.co/4VkVPjs
https://ibb.co/cw2BzLC
https://ibb.co/kcjjJ74
Now in the following screenshots, i kept the vol - button pressed down. Note that the driver is stuck at preloader and not DA. Also the first bar is yellow color in both these cases. However, in the above situation, multiple files were flashed. But in this below situation, only this so called "flash" was done; that too unsucessful in the end.
https://ibb.co/1QKtsCb
https://ibb.co/Ssj58Zd
Click to expand...
Click to collapse
The problem may be with your drivers, i see you have Preloader drivers only.
Follow this guide for installing drivers - https://forum.xda-developers.com/elephone-m2/help/windows-10-mtk-vcom-usb-drivers-32-64-t3267033

Anas Rahman said:
The problem may be with your drivers, i see you have Preloader drivers only.
Follow this guide for installing drivers - https://forum.xda-developers.com/elephone-m2/help/windows-10-mtk-vcom-usb-drivers-32-64-t3267033
Click to expand...
Click to collapse
So i did as you said brother. I don' t know how but something happened. The phone, after a long time actually displayed up. It showed the LENOVO logo and down in the corner two things came in written :
>device unlocked
>Tool DL image Fail
I googled it up and found that it requires to flash the phone with the DA DL option ticked. I did that but it does not flash. The error is same as follows:
https://ibb.co/Ssj58Zd
Can you please guide me in the flashing process? I think the mistake is very small but i don't know where i am missing.

I have lost all my mind and need serious help.
custom619 said:
So i did as you said brother. I don' t know how but something happened. The phone, after a long time actually displayed up. It showed the LENOVO logo and down in the corner two things came in written :
>device unlocked
>Tool DL image Fail
I googled it up and found that it requires to flash the phone with the DA DL option ticked. I did that but it does not flash. The error is same as follows:
https://ibb.co/Ssj58Zd
Can you please guide me in the flashing process? I think the mistake is very small but i don't know where i am missing.
Click to expand...
Click to collapse
Okay so what i figured out is that in this state: (battery plugged in, no notification LED response, no response on power or volume buttons) the driver you require is MTK USB PORT.
I updated to this driver manually, and guess what? the phone actually flashed. But three files remained and the process hanged. (system, cache and userdata)
Now i get the errors:
>device unlocked
>Tool DL image Fail
and sometimes: >device otp failed
I am trying to flash the rest three files individually. Lets see what happens.

custom619 said:
Okay so what i figured out is that in this state: (battery plugged in, no notification LED response, no response on power or volume buttons) the driver you require is MTK USB PORT.
I updated to this driver manually, and guess what? the phone actually flashed. But three files remained and the process hanged. (system, cache and userdata)
Now i get the errors:
>device unlocked
>Tool DL image Fail
and sometimes: >device otp failed
I am trying to flash the rest three files individually. Lets see what happens.
Click to expand...
Click to collapse
Try flashing wihtout these three files, then boot to fastboot mode by pressing POWER+VOL UP and choose fastboot mode then flash these three files with fastboot commamds

Anas Rahman said:
Try flashing wihtout these three files, then boot to fastboot mode by pressing POWER+VOL UP and choose fastboot mode then flash these three files with fastboot commamds
Click to expand...
Click to collapse
I.AM.DUMBFOUNDED.
During flashing this error occurred:
(yellow bar in SPFlash tool)
[recovery] Download Flash 100%
ERROR: STATUS_MMC_ERR (0xC0040030)
[HINT]:

custom619 said:
I.AM.DUMBFOUNDED.
During flashing this error occurred:
(yellow bar in SPFlash tool)
[recovery] Download Flash 100%
ERROR: STATUS_MMC_ERR (0xC0040030)
[HINT]:
Click to expand...
Click to collapse
Couldn't find much about the error, give this a try
https://forum.xda-developers.com/k8-note/how-to/lenovo-k8-note-xt1902-3-fix-dead-hard-t3791839
ALSO, in the last few screenshots you're using firmware upgrade option please choose downlaod only.
Join the Telegram group more people can help there - -
Join «Lenovo XT1902-1/2/3 (K8 Series) Official Chat Group» on Telegram: https://t.me/K8Official

Anas Rahman said:
Couldn't find much about the error, give this a try
https://forum.xda-developers.com/k8-note/how-to/lenovo-k8-note-xt1902-3-fix-dead-hard-t3791839
ALSO, in the last few screenshots you're using firmware upgrade option please choose downlaod only.
Join the Telegram group more people can help there - -
Join «Lenovo XT1902-1/2/3 (K8 Series) Official Chat Group» on Telegram: https://t.me/K8Official
Click to expand...
Click to collapse
I Already tried this thread you suggested. No outcome.

Anas Rahman said:
Couldn't find much about the error, give this a try
https://forum.xda-developers.com/k8-note/how-to/lenovo-k8-note-xt1902-3-fix-dead-hard-t3791839
ALSO, in the last few screenshots you're using firmware upgrade option please choose downlaod only.
Join the Telegram group more people can help there - -
Join «Lenovo XT1902-1/2/3 (K8 Series) Official Chat Group» on Telegram: https://t.me/K8Official
Click to expand...
Click to collapse
This group is possibly dead. No one has responded till today...

Messed it up! :(

Hi folks,
I guess I did something really stupid. I flashed the Lineage OS 15.1 (unofficial) (https://bit.ly/2w1yVm4) directly on my HTC10 with Lineage OS 14.1 running via TWRP. I did this a few weeks ago already but figured out that there were too many bugs for me present.
Now I found out that my Home Button isn't working and that is obviously a known bug. I decided to go back to 14.1 but after flashing the phone doesn't recognize my SIM card.
Now I'm running through tons of threads and trying to find out what the next steps would be. A do have a full backup of the stock rom, which was created before the phone got rooted. The phone is S-on. Currently, I don't want to stay on 15.1 because of the bugs, which are still in it.
Is there an explanation what happens, if the 15.1 is being installed? Why is it different from switching between other roms?
Thank you in advance for kind help.
Cheers
Joe

chaos_since_78 said:
Hi folks,
I guess I did something really stupid. I flashed the Lineage OS 15.1 (unofficial) (https://bit.ly/2w1yVm4) directly on my HTC10 with Lineage OS 14.1 running via TWRP. I did this a few weeks ago already but figured out that there were too many bugs for me present.
Now I found out that my Home Button isn't working and that is obviously a known bug. I decided to go back to 14.1 but after flashing the phone doesn't recognize my SIM card.
Now I'm running through tons of threads and trying to find out what the next steps would be. A do have a full backup of the stock rom, which was created before the phone got rooted. The phone is S-on. Currently, I don't want to stay on 15.1 because of the bugs, which are still in it.
Is there an explanation what happens, if the 15.1 is being installed? Why is it different from switching between other roms?
Thank you in advance for kind help.
Cheers
Joe
Click to expand...
Click to collapse
Hint :
ERASE THE PERSIST PARTITION.
https://forum.xda-developers.com/ht...mei-signal-downgrade-oreo-8-0-t3748999/page21

Mr Hofs said:
Hint :
ERASE THE PERSIST PARTITION.
https://forum.xda-developers.com/ht...mei-signal-downgrade-oreo-8-0-t3748999/page21
Click to expand...
Click to collapse
Thank you for the hint. But for some reasons it worked perfectly when I did the same **** a few weeks ago when I tried 15.1 the first time. I reinstalled the 14.1 and everything was working perfectly.
What happend, when I installed the 15.1? Was the firmware somehow updated automatically? How do I find out, on which version my HTC10 is running right now?
Sorry for all this noobish questions. :angel:
Cheers

chaos_since_78 said:
Thank you for the hint. But for some reasons it worked perfectly when I did the same **** a few weeks ago when I tried 15.1 the first time. I reinstalled the 14.1 and everything was working perfectly.
What happend, when I installed the 15.1? Was the firmware somehow updated automatically? How do I find out, on which version my HTC10 is running right now?
Sorry for all this noobish questions. :angel:
Cheers
Click to expand...
Click to collapse
Boot to download mode and tell me what's written in the OS line ?

Hi Mr. Hofs,
This line says: OS-1.95.111.4
Is it possible to upgrade the firmware afterwards to an Oreo-compatible version without wiping the phone? Because the Lineage OS 15.1, which is currently running is fine so far, except these two anoying bugs Missing Loudspeaker and the Missing Homebutton (which might get solved with the correct firmware?)
One more question: The Hint above says: ERASE THE PERSIST PARTITION. The link shows on the first page of the thread a command for S-ON: "dd if=/dev/zero of=/dev/block/bootdevice/by-name/persist", which duplicates a partion but does not delete it. At least that is what it does under Linux. So how do I delete this persistent partition?

chaos_since_78 said:
Hi Mr. Hofs,
This line says: OS-1.95.111.4
Is it possible to upgrade the firmware afterwards to an Oreo-compatible version without wiping the phone? Because the Lineage OS 15.1, which is currently running is fine so far, except these two anoying bugs Missing Loudspeaker and the Missing Homebutton (which might get solved with the correct firmware?)
One more question: The Hint above says: ERASE THE PERSIST PARTITION. The link shows on the first page of the thread a command for S-ON: "dd if=/dev/zero of=/dev/block/bootdevice/by-name/persist", which duplicates a partion but does not delete it. At least that is what it does under Linux. So how do I delete this persistent partition?
Click to expand...
Click to collapse
That's a darn old firmware. My opinion :
Get the NOUGAT RUU (like 2.41.111) if you can locate it, Flash it (it will wipe the phone which is pretty much inevitable anyway) update to oreo and flash the latest Oreo based custom roms

Mr Hofs said:
That's a darn old firmware. My opinion :
Get the NOUGAT RUU (like 2.41.111) if you can locate it, Flash it (it will wipe the phone which is pretty much inevitable anyway) update to oreo and flash the latest Oreo based custom roms
Click to expand...
Click to collapse
Unfortunatelly, the phone does not find the 2PS6IMG.zip file, which is placed directly in the root of my SD-Card. It says "File /mnt/media_rw/ext_sd/2PS6IMG.zip not found". I have no idea whereelse I could store that file.

chaos_since_78 said:
Unfortunatelly, the phone does not find the 2PS6IMG.zip file, which is placed directly in the root of my SD-Card. It says "File /mnt/media_rw/ext_sd/2PS6IMG.zip not found". I have no idea whereelse I could store that file.
Click to expand...
Click to collapse
If the download mode is not detecting the zip file it's not named correctly because it should auto detect it. Make sure you didn't name it zip.zip

Mr Hofs said:
That's a darn old firmware. My opinion :
Get the NOUGAT RUU (like 2.41.111) if you can locate it, Flash it (it will wipe the phone which is pretty much inevitable anyway) update to oreo and flash the latest Oreo based custom roms
Click to expand...
Click to collapse
Mr Hofs said:
If the download mode is not detecting the zip file it's not named correctly because it should auto detect it. Make sure you didn't name it zip.zip
Click to expand...
Click to collapse
No, it's definitely named correctly.

chaos_since_78 said:
No, it's definitely named correctly.
Click to expand...
Click to collapse
Then it's the wrong RUU maybe? What file exactly do you want your download mode to flash?

The first file I tried: 2PS6IMG-RUU_PERFUME_WL_M60_SENSE80GP_NA_Gen_Unlock_1.53.617.5.zip
The second file I tried: 2PS6IMG_PERFUME_UHL_O80_SENSE90GP_MR_HTC_Europe_3.16.401.2_R4_release_519849.zip
I renamed them accordingly to 2PS6IMG.zip and placed them in the root of my sd card.
What is kind of strange is that the HTC Sync tool does not recognize my phone when it's connected to a Win 10 PC. I can access the sd card and it's listet in the device manager under "portable devices" where it is supposed to be.
When I execute the RUU as exe the installer starts but closes after filling the status bar without any message.
I also executed this command earlier:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/persist
from the thread: https://forum.xda-developers.com/htc-10/how-to/solution-imei-signal-downgrade-oreo-8-0-t3748999

chaos_since_78 said:
The first file I tried: 2PS6IMG-RUU_PERFUME_WL_M60_SENSE80GP_NA_Gen_Unlock_1.53.617.5.zip
The second file I tried: 2PS6IMG_PERFUME_UHL_O80_SENSE90GP_MR_HTC_Europe_3.16.401.2_R4_release_519849.zip
I renamed them accordingly to 2PS6IMG.zip and placed them in the root of my sd card.
What is kind of strange is that the HTC Sync tool does not recognize my phone when it's connected to a Win 10 PC. I can access the sd card and it's listet in the device manager under "portable devices" where it is supposed to be.
When I execute the RUU as exe the installer starts but closes after filling the status bar without any message.
I also executed this command earlier:
from the thread: https://forum.xda-developers.com/htc-10/how-to/solution-imei-signal-downgrade-oreo-8-0-t3748999
Click to expand...
Click to collapse
As I've said.....you need a 2.41.111 RUU or similar to that, you are ABSOLUTELY flashing the wrong files. Please don't believe you can "just" flash any file out there.....oh dear.
I already told you to look for a 2.41.111 RUU out there. I didn't tell you to flash a 3.16.401 RUU neither a 1.53.617 RUU!!! No idea why you would come up with those files.
STOP immediately what you are doing until we found the correct RUU!!!
---------- Post added at 11:19 PM ---------- Previous post was at 11:13 PM ----------
Look what i got for you
https://www.androidfilehost.com/?fid=890129502657598118
Now try again......just this one, nothing else

Sorry, to bother you. I renamed it and moved the file to the sd card. Same sh*t again. But it still complains about "Failed to mount '/persist' (invalid argument)" I don't know if this has anything to do with all these problems.

chaos_since_78 said:
Sorry, to bother you. I renamed it and moved the file to the sd card. Same sh*t again. But it still complains about "Failed to mount '/persist' (invalid argument)" I don't know if this has anything to do with all these problems.
Click to expand...
Click to collapse
Can you perform the "erase persist" command first, reboot to bootloader, reboot back to download mode and try again.

Mr Hofs said:
Can you perform the "erase persist" command first, reboot to bootloader, reboot back to download mode and try again.
Click to expand...
Click to collapse
Thats a tricky one, isn't it? I followed the instructions given in this video: https://www.youtube.com/watch?time_continue=1&v=vJrNEsWVyOc Instead of the metioned RUU I used the one you pointed me at. At least I could get the "/persist" problem solved.
Now it still does not find the 2PS6IMG.zip file. However, the error message has changed just to "SD mounted OTG NOT MOUNTED File NOT FOUND".
But I'm not sure if the flashing of the RUU has really work. There were tons of error messages:
E:\HTC\platform-tools>fastboot flash zip E:\HTC\OUT_2PS6_2.41.111.42\2PS6IMG.zip
Invalid sparse file format at header magic
error: write_sparse_skip_chunk: don't care size 979745195 is not a multiple of the block size 4096
Sending sparse 'zip' 1/2 (1048572 KB) error: write_sparse_skip_chunk: don't care size 979745195 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 979745195 is not a multiple of the block size 4096
OKAY [ 37.875s]
Writing sparse 'zip' 1/2 (bootloader) HOSD CL#857212
(bootloader) ERR lzipv2_init : Cannot open file /dev/fastboot_download_V
(bootloader) 2J4b7
(bootloader) ERR [SD_UPDATE_ERR] update_fb_ZIP_buf: can not find ZIP hea
(bootloader) der
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 22
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) ERR ZIP signature checking failed...
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 22
(bootloader) [email protected]
FAILED (remote: 22 RU_HEADER_ERROR )
Finished. Total time: 57.082s
The phone showed the status bar and I could flash Lineage OS 14.1 afterwards. However, radio and the fingerprint are still not working.
I'm close to bite into this stupid thing. :crying:

Not quite sure what to think at this point.
1: if the RUU flashed properly it would have put the firmware to 2.41.111
2: if the RUU flashed properly it would have replaced TWRP with the stock recovery
This situation is a complete firmware / software incompatibility. The 1.95 firmware is a marshmallow firmware. Try to flash a rom if you can grab one.
I know that when you flash a oreo rom over a nougat firmware you lose radio and vice versa. Not sure what happens exactly when you do this with a marshmallow firmware. I can check back in about 2 days. I'm on holiday but the subject intrigues me.
Cheers.

Is there any other way to flash this RUU?

Okay... Got some news. I used TWRP 3.2.3.0 to restore my backup, which was created when I first got the phone and rooted it. This restore ended with only one error saying "the system partition cannot be mounted" or something like that. I tried to boot the phone but it only showed the HTC logo for an hour or so. I restartet the phone into recovery and flashed just for fun the LOS 14.1 and et voila, I got radio back and the home button/fingerprint sensor are working again.
Question is now: On which firmware am I running? Should I risk to upgrade it. How do I upgrade it and to which version. Aim would be to get on LOS 15.1. Is it worth all the trouble?
Anyway, THANKS A LOT for your patience. I have some experience in computers but these phones are such crap in this manner! Why can't that be more easy? I think it's made so complicate with purpose! Damn vendors!

chaos_since_78 said:
Okay... Got some news. I used TWRP 3.2.3.0 to restore my backup, which was created when I first got the phone and rooted it. This restore ended with only one error saying "the system partition cannot be mounted" or something like that. I tried to boot the phone but it only showed the HTC logo for an hour or so. I restartet the phone into recovery and flashed just for fun the LOS 14.1 and et voila, I got radio back and the home button/fingerprint sensor are working again.
Question is now: On which firmware am I running? Should I risk to upgrade it. How do I upgrade it and to which version. Aim would be to get on LOS 15.1. Is it worth all the trouble?
Anyway, THANKS A LOT for your patience. I have some experience in computers but these phones are such crap in this manner! Why can't that be more easy? I think it's made so complicate with purpose! Damn vendors!
Click to expand...
Click to collapse
The answer you need is already in this thread. Your actual firmware is in download mode - OS line. It's (since the last time) 1.95.111 so that means it's a t mobile firmware. That's why i handed you the 2.41.111 RUU, that RUU still should flash just fine with the SD card method. It's the most used method around.
Cheers.

Ok. I guess I celebrated a bit early. My TWRP is now 3.1.1.0 which is pretty old. I tried to flash the latest one 3.2.3.0 but in download mode fastboot doesn't recognize the phone anymore. It just says "waiting for any device". Maybe I should get drunk first before I proceed.
PC reboot help! Sorry!