Database Develop

[Q] ¿How do I uninstall TWRP?

I've been trying to get the 1.29.1540.16 update in my HTC One Dev Edition. So I tried to flash the Stock RUU I downloaded from the HTC site, then download the OTA and then run it from the phone but it just takes me to the TWRP recovery (after I unlocked the bootloader, on "relocked" it just took me to the fastboot screen). What am I doing wrong?
Also when the first time I flashed the RUU (like 2 weeks before) the "Tampered" went away, this time this isn't happening.
Tried relocking/unlocking.
Don't know what to do. Help very much appreciated.

You have to flash the stock recovery first then run the RUU.

shadowboy23 said:
You have to flash the stock recovery first then run the RUU.
Click to expand...
Click to collapse
I feel really dumb asking this but how do I flash the stock recovery? I thought the stock recovery and Stock RUU were the same thing.

vicsalas said:
I feel really dumb asking this but how do I flash the stock recovery? I thought the stock recovery and Stock RUU were the same thing.
Click to expand...
Click to collapse
Recovery is different and it's not included in the RUU (I think). To flash the stock recovery you need to be in fastboot mode and flash via adb. Use this guide by mike1986. http://forum.xda-developers.com/showthread.php?t=2265618. Scroll down to the "Going back to stock" section.

shadowboy23 said:
Recovery is different and it's not included in the RUU (I think). To flash the stock recovery you need to be in fastboot mode and flash via adb. Use this guide by mike1986. http://forum.xda-developers.com/showthread.php?t=2265618. Scroll down to the "Going back to stock" section.
Click to expand...
Click to collapse
Really appreciate the replies. Method 2 of the link you gave me is what I've been doing, but I still see the tampered label and my phone keeps booting back to TWRP (shouldn't this be uninstalled?).

vicsalas said:
Really appreciate the replies. Method 2 of the link you gave me is what I've been doing, but I still see the tampered label and my phone keeps booting back to TWRP (shouldn't this be uninstalled?).
Click to expand...
Click to collapse
Download this: http://d-h.st/b5g
Put it in your adb folder
Reboot to bootloader
Code:
fastboot flash recovery recovery_signed-dev.img
Then you can use the OTA

MacHackz said:
Download this:
Put it in your adb folder
Reboot to bootloader
Code:
fastboot flash recovery recovery_signed-dev.img
Then you can use the OTA
Click to expand...
Click to collapse
Did that, came back an error :FAILED (remote: signature verify fail).

vicsalas said:
Did that, came back an error :FAILED (remote: signature verify fail).
Click to expand...
Click to collapse
Your bootloader is unlocked right?

tedtfra was
MacHackz said:
Your bootloader is unlocked right?
Click to expand...
Click to collapse
Didn't answer before cause I went out to the movies (and of course I didn't enjoy the movie thinking of this).
Right on the money Mac!. Hadn't unlocked the bootloader, did it and worked like a charm. Can't thank you enough, I could install the OTA and that fixed the issues with the capacitive buttons that were my only reason to do so (although phone's so great I think I'd have used it with the buttons issues as well), one last question though: I still have the "tampered" sticker, is that because I did it the other way around? I mean, should I have installed the img file you gave me and then flash the Stock RUU and that would have erased it?

vicsalas said:
Didn't answer before cause I went out to the movies (and of course I didn't enjoy the movie thinking of this).
Right on the money Mac!. Hadn't unlocked the bootloader, did it and worked like a charm. Can't thank you enough, I could install the OTA and that fixed the issues with the capacitive buttons that were my only reason to do so (although phone's so great I think I'd have used it with the buttons issues as well), one last question though: I still have the "tampered" sticker, is that because I did it the other way around? I mean, should I have installed the img file you gave me and then flash the Stock RUU and that would have erased it?
Click to expand...
Click to collapse
You can't remove the Tampered sign It's HTCs way of voiding your warranty

vicsalas said:
Didn't answer before cause I went out to the movies (and of course I didn't enjoy the movie thinking of this).
Right on the money Mac!. Hadn't unlocked the bootloader, did it and worked like a charm. Can't thank you enough, I could install the OTA and that fixed the issues with the capacitive buttons that were my only reason to do so (although phone's so great I think I'd have used it with the buttons issues as well), one last question though: I still have the "tampered" sticker, is that because I did it the other way around? I mean, should I have installed the img file you gave me and then flash the Stock RUU and that would have erased it?
Click to expand...
Click to collapse
Hey i have got the same problem, can you guide me?

[Q] How to update to 1.08? RUU won't work.

I already rooted my First on 1.05 and want to update to 1.08 since I want to go S-OFF and I saw in that thread it's for 1.08.
I tried the RUU dozens of times on 2 completely different Windows 7 x64 PCs. It sat at the Sending...... step for awhile with the phone on an HTC logo screen, and then ended in Error 155. I also tried booting into FASTBOOT USB and trying it. Same thing. Has anyone got the RUU to work? If so, what's your MD5 hash? Mine is 425MB and I would think it's a good copy since it was able to extract itself into Appdata\Local\Temp folder with no errors.
I saw in the RUU thread there's also just the OTA .zip. It won't install with TWRP. I'd have to flash to stock recovery to install it, but I couldn't find any place to get the stock recovery.
Any solutions?

GnatGoSplat said:
I already rooted my First on 1.05 and want to update to 1.08 since I want to go S-OFF and I saw in that thread it's for 1.08.
I tried the RUU dozens of times on 2 completely different Windows 7 x64 PCs. It sat at the Sending...... step for awhile with the phone on an HTC logo screen, and then ended in Error 155. I also tried booting into FASTBOOT USB and trying it. Same thing. Has anyone got the RUU to work? If so, what's your MD5 hash? Mine is 425MB and I would think it's a good copy since it was able to extract itself into Appdata\Local\Temp folder with no errors.
I saw in the RUU thread there's also just the OTA .zip. It won't install with TWRP. I'd have to flash to stock recovery to install it, but I couldn't find any place to get the stock recovery.
Any solutions?
Click to expand...
Click to collapse
I have a related problem, after bricking the phone I flashed the RUU and I cannot re unlock the bl again, anyway try to flash cwm instead of twrp and then retry with the Ota.zip. I don't know if this can solve your problem, but I've noticed that with twrp some roms did not work to me. I think also that the RUU does not work with unlocked bl, so you have first to relock, but if you do this you could have the same problem I have, that is you can't re unlock the bl... I am not an expert so I cannot assure you that these procedures are ok...

GnatGoSplat said:
I already rooted my First on 1.05 and want to update to 1.08 since I want to go S-OFF and I saw in that thread it's for 1.08.
I tried the RUU dozens of times on 2 completely different Windows 7 x64 PCs. It sat at the Sending...... step for awhile with the phone on an HTC logo screen, and then ended in Error 155. I also tried booting into FASTBOOT USB and trying it. Same thing. Has anyone got the RUU to work? If so, what's your MD5 hash? Mine is 425MB and I would think it's a good copy since it was able to extract itself into Appdata\Local\Temp folder with no errors.
I saw in the RUU thread there's also just the OTA .zip. It won't install with TWRP. I'd have to flash to stock recovery to install it, but I couldn't find any place to get the stock recovery.
Any solutions?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2287811
just flash 1.08 odexed or deodexed
Sent from my HTC first using xda premium

HarryCustom said:
I have a related problem, after bricking the phone I flashed the RUU and I cannot re unlock the bl again, anyway try to flash cwm instead of twrp and then retry with the Ota.zip. I don't know if this can solve your problem, but I've noticed that with twrp some roms did not work to me. I think also that the RUU does not work with unlocked bl, so you have first to relock, but if you do this you could have the same problem I have, that is you can't re unlock the bl... I am not an expert so I cannot assure you that these procedures are ok...
Click to expand...
Click to collapse
Thanks, that was the problem; I had to relock the bootloader and then the RUU worked. I was able to re-unlock the bootloader with no problems though. I used the All-In-One kit to do it and reused the Unlock_code.bin that I used on 1.05.
kornklown69 said:
http://forum.xda-developers.com/showthread.php?t=2287811
just flash 1.08 odexed or deodexed
Click to expand...
Click to collapse
I must be blind, I swear I looked for flashable zips but couldn't find them. Too late since I already flashed the RUU, but hopefully that will help someone else who runs into this issue.

GnatGoSplat said:
Thanks, that was the problem; I had to relock the bootloader and then the RUU worked. I was able to re-unlock the bootloader with no problems though. I used the All-In-One kit to do it and reused the Unlock_code.bin that I used on 1.05.
I must be blind, I swear I looked for flashable zips but couldn't find them. Too late since I already flashed the RUU, but hopefully that will help someone else who runs into this issue.
Click to expand...
Click to collapse
So the kornklown69 theory that also mine is correct, is S-OFF the problem. To re-unlock probably the phone must be S-ON.
So the procedure could be: Relock -> S-ON -> Re-unlock -> S-OFF.
But I don't understand how to obtain S-ON again.
Anyway my phone is Relocked and I can install custom roms, kernels and root it... Very strange!

That makes sense. With my original Droid Incredible, an S-OFF hack came out before HTC official BL unlocking and there was never any reason to unlock it since S-OFF was all you needed to install custom ROMs and root. So if you're S-OFF, there's probably no need to re-unlock it.

Having the same issue. In another thread, jmz said:
In my stock Rom thread there are new files up. They are the ota roms. So if you are running stock, download the odex one ending in 1.08 and flash in recovery, no need to wipe data. Then pull boot.img and fastboot flash it. You now have the ota software. I will post instructions to upgrade the firmware that came with the ota
Click to expand...
Click to collapse
I know what the odexed rom is, but can someone explain how to get the boot.img and fastboot flash it? Or should I just relock the bootloader?

[Guide] Reset phone using RUU / htc_fastboot.exe has stopped working

Please read and understand the guide and accompanying links in their entirety before beginning.​XDA and I am not responsible for anything you do to your phone.​
This guide should work for anyone trying to RUU their phone, but let me give you my background on this first.
While trying to run an RUU to reset my phone, I kept running into an issue: "htc_fastboot.exe has stopped working". I could get my phone to restart, but the RUU would not run successfully. I searched this site and the internet for an answer, but could not find anything that worked for me. Also, a lot of people in Q&A tend to have issues getting the RUU to work. That's why I'm writing this guide. Hopefully someone who is having trouble will search and stumble across it. I tried everything I could find - Windows 7, 8.1, different RUUs, etc and this is how I finally fixed it. I am s-off by the way and did this in Windows 8.1 Update so the guide is written from that perspective.
Steps:
1. Make sure that your computer can see your phone when you boot into fastboot. It should say Fastboot in red that changes to Fastboot USB when plugged into your computer. There are guides that help with this, so I'm not going to go into much detail. Basically you install HTC Sync to your computer and then uninstall it but leave the drivers.
2. Get a copy of fastboot and ADB. The easiest way is to get the SDK from Google (tools only) as it also includes drivers, but you can get just fastboot and adb from here (I did not use this tool personally).
3. To verify that your phone and computer are talking, open a command prompt window (I always open as administrator) and go to the folder that contains fastboot. Type "fastboot devices" (no quotes) and it should list your phone. If it does not, something did not work right with steps 1 and 2.
4. If you are s-off, you do not need to lock the bootloader. If you are s-on, then you need to lock the bootloader by typing "fastboot oem lock" (again, no quotes).
5. Download the Full Firmware from RUU here. While you're there, get the RUU as well. Make sure to get the one that is not decrypted (first link). Copy both into the folder with fastboot.
6. Flash the firmware file using fastboot following the directions in the OP from where you got it. To summarize, rename the firmware zip file to firmware.zip. Then at a command prompt, type "fastboot oem rebootRUU". When the phone shows a black screen that says HTC, type "fastboot flash zip firmware.zip". The command prompt window will show a bunch of stuff as it does its thing. When you get back to the command prompt, it's finished. At this point, type "fastboot reboot-bootloader" to restart back into the (hopefully now stock) bootloader. Personally, I had to repeat the last command again because it failed the first time.
7. At this point, you should be in the stock hboot. It should say fastboot USB in red. Now time to RUU.
8. The current RUU is an exe so run the RUU you download before (if you have a zip file, unzip the RUU and run ARUWizard.exe). I personally ran it as an administrator just to make sure limited privileges didn't cause an issue. Read each screen and keep clicking next. Eventually it will do its thing. It takes about ten minutes and sometimes seems to be frozen. Have patience grasshopper.
And that's it. I'm now running pure stock (not for long I'm sure), still s-off. If you are s-on, you will have to unlock your bootloader again.
Good luck!

I'll be the first to troll post in this guide
Nice work brother.
I've noticed the newer RUU's (M7 and M8) require you to have the matching hboot to run correctly even if your device is s-off.

I didn't know what it meant in step 8 to "unzip the RUU" since my RUU was an EXE file that could not be unzipped. After step 7, I just ran the RUU executable and it ran as expected. I was able to run everything else just like the steps say, but for step 8 I just ran the RUU executable I had downloaded for my Sprint HTC One.
Thanks for the guide!

kushanson said:
I didn't know what it meant in step 8 to "unzip the RUU" since my RUU was an EXE file that could not be unzipped. After step 7, I just ran the RUU executable and it ran as expected. I was able to run everything else just like the steps say, but for step 8 I just ran the RUU executable I had downloaded for my Sprint HTC One.
Thanks for the guide!
Click to expand...
Click to collapse
You're welcome. Glad it helped. Also, thank you for the heads up about the RUU being an exe now. It was a zip file when I wrote the guide. I've fixed the guide to reflect the change.

Dude...
I was soft bricked for about an hour until I found this. It seems fairly obvious to me now, but for some reason I had thought that only flashing the full_firmware zip in fastboot would suffice. I guess the tiny file size (80MB unzipped???) should have tipped me off.
Regardless, I'm back up and running. Thanks, coal.

i am getting error bootloader signature failed how to fix please

rajnshubham said:
i am getting error bootloader signature failed how to fix please
Click to expand...
Click to collapse
I'm guessing you are s-on. If so, you cannot flash the firmware file (I'm s-off and wrote the guide from that perspective). You most likely can just skip that step and run the ruu.exe.

coal686 said:
This guide should work for anyone trying to RUU their phone, but let me give you my background on this first.
Good luck!
Click to expand...
Click to collapse
Thanks for your guided I was able to fix an old One that I had laying around, thanks again

coal686 said:
I'm guessing you are s-on. If so, you cannot flash the firmware file (I'm s-off and wrote the guide from that perspective). You most likely can just skip that step and run the ruu.exe.
Click to expand...
Click to collapse
i think the problem was due to same hboot error. i get to know this thing few days back. anyway thanks coal686. now i updated with the ruu having hboot 1.56 and now i m on kitkat 4.4.2 stock. i can update now to higher ones. thanks buddy

I want to make sure I understand something in the steps. I know the first step is to fastboot the full firmware ruu but then comes something I'm not sure about. Do I follow that up with the. exe file?
I am s-off with 1.60.
Sent from my HTCONE using XDA Free mobile app

biker57 said:
I want to make sure I understand something in the steps. I know the first step is to fastboot the full firmware ruu but then comes something I'm not sure about. Do I follow that up with the. exe file?
I am s-off with 1.60.
Sent from my HTCONE using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for using my guide!
The first step is to flash the "full firmware from RUU" (it's actually labelled that way in the OP of the linked post). It's only the firmware, not the full RUU. Then, follow that up with the .exe file which is the entire RUU. For some reason, the RUU wouldn't run for me without flashing the firmware first.
Since you are already on hboot 1.6, you probably don't have to flash the firmware first, but I'd do it just to be safe.

I normally think of a. exe file as executable. Is this something I can run or need to fastboot?
Sent from my HTCONE using XDA Free mobile app

biker57 said:
I normally think of a. exe file as executable. Is this something I can run or need to fastboot?
Sent from my HTCONE using XDA Free mobile app
Click to expand...
Click to collapse
Just run it. Fastboot flash the firmware then just run the RUU exe.

Just wanted to report that I had the same problem with htc_fastboot.exe stopped working error and I was stuck on 3.22.1540.1 JB and there was no way on upgrading my software because OTAs would download but I would get a red mark when installing. So I skkipped most of your steps because I was not rooted or unlocked, I was all stock but reflashed the same software I was on, 3.22.1540.1 zip and did it twice since first time I got FAILED message in ADB. Once my phone restarted I tried flashing a newer RUU and still got htc_fastboot.exe error on KK and LP RUUs so just for luck tried downloading OTA from the phone but this time it DID install. So I upgraded to 4.15.1540.9 and currently downloading 4.19.1540.4. Hopefully everything goes right and I can get LP running on my phone.

cowboysgz said:
Just wanted to report that I had the same problem with htc_fastboot.exe stopped working error and I was stuck on 3.22.1540.1 JB and there was no way on upgrading my software because OTAs would download but I would get a red mark when installing. So I skkipped most of your steps because I was not rooted or unlocked, I was all stock but reflashed the same software I was on, 3.22.1540.1 zip and did it twice since first time I got FAILED message in ADB. Once my phone restarted I tried flashing a newer RUU and still got htc_fastboot.exe error on KK and LP RUUs so just for luck tried downloading OTA from the phone but this time it DID install. So I upgraded to 4.15.1540.9 and currently downloading 4.19.1540.4. Hopefully everything goes right and I can get LP running on my phone.
Click to expand...
Click to collapse
.
Thanks

Device not recognized
Whenever I plug in my device and go to fastboot, my computer tells me "USB Device not recognized". I've installed the drivers from HTC, I even went to Decide manager on my PC to see if the device appears at all. It shows on the top under "Android USB Device" and it's labeled "My HTC" but it has the error symbol on it, so o deviced to unistall the driver and install it manually. It said that I already had the correct driver.
The reason I'm trying to do all this is, back in 2013 I had put Viper ROM on my device, it worked great, I also installed cyanogen mod as well and that worked great, at the time I wanted to have the double tap to wake feature, so I installed a custom Kernel to allow that. When I had booted up my phone the HTC logo didn t go away, then the lock screen showed up, I unlocked my phone, the HTC logo was still there, then my home screen finally opened and some apps wouldn't open. Then it would restart, so I rebooted it and it would do the same thing, turn on, show the HTC, start then restart. I could go into recovery fine, Install updated version of rom, and the same problem persists

Is there any reason the RUU exe file would stop working only two screens in? I basically run it, accept the terms, click next... then nothing....... what SHOULD it be doing? Best, Rich

krakora said:
Is there any reason the RUU exe file would stop working only two screens in? I basically run it, accept the terms, click next... then nothing....... what SHOULD it be doing? Best, Rich
Click to expand...
Click to collapse
I meant to add this to my guide and didn't get around to it. You're missing a Visual C++ 2008 runtime. See this thread:
https://forum.xda-developers.com/sprint-htc-one/help/solved-ruu-starts-disappears-accepting-t3224469

coal686 said:
I meant to add this to my guide and didn't get around to it. You're missing a Visual C++ 2008 runtime. See this thread:
https://forum.xda-developers.com/sprint-htc-one/help/solved-ruu-starts-disappears-accepting-t3224469
Click to expand...
Click to collapse
Thanks so much Coal, that absolutely worked. The RUU exe runs for me, but getting 155 unknown error. Evidently its not the right RUU for my device. My bootloader is "relocked" already, S-on. So confusing. When I was following the directions on the guide, when flashing the firmware, I was getting the 12 missing signatures error also, I'm assuming its not reading it as an HTC signed firmware. Any ideas on my next direction? Best, Rich

I need help upgrading firmware and radio and Rom

I have been running this rom for quite some time and I wanted to know the procedures while being s on to upgrade the entire phone. I'm also enclosing a screenshot of my current firmware and ROM. Any help would be greatly appreciated I haven't done this since I first got my m8

Download the most recent RUU from the thread linked below to your computer:
http://forum.xda-developers.com/showthread.php?t=2729173
Make sure your phone has a full charge. Reboot your device to the bootloader and connect your phone and computer via USB cable. Select the fastboot option from the menu and you should show that you're connected via fastboot USB mode. Open up a command window with ADB and type the command "fastboot oem lock". Press enter. This command will re-lock your boot loader. Now, double-click the RUU file you downloaded to start the installer. Be patient, as it may take a few minutes for the installer to start. Once it starts, follow the prompts on your computer screen. Once the RUU completes you can disconnect your phone from your computer and reboot your phone. The RUU will wipe the internal storage on your phone, so make a back-up and store it on your computer or your external SD card, if applicable.

Can i unlock the bootloader again after doing all this by typing fastboot oem unlock in adb?

I just wanna make sure I update everything correctly and get set up for a new Rom. I'm not getting all my calls or texts. So I am guessing the radio is too outdated

Is there a way to just get an image that will bring my phone back to stock so I can upgrade everything all at once

honorlost84 said:
Is there a way to just get an image that will bring my phone back to stock so I can upgrade everything all at once
Click to expand...
Click to collapse
RUU

Alright and that won't screw up the recovery I have installed correct so I can just flash a new rom even with a locked bootloader or do I have to go through all the stupid steps to unlock it again

honorlost84 said:
Alright and that won't screw up the recovery I have installed correct so I can just flash a new rom even with a locked bootloader or do I have to go through all the stupid steps to unlock it again
Click to expand...
Click to collapse
The stock recovery will be installed. Additionally, you'll need to use HTC Dev to unlock your phone again. That's the best way to update being S-on.

So there's no way to just update the firmware and radio without having to go through the rest of that?

Actually I just looked up how to get s off on my phone I'm going to use the fire water tool and then I'll use that link to get the firmware and flash that with the fuu

honorlost84 said:
So there's no way to just update the firmware and radio without having to go through the rest of that?
Click to expand...
Click to collapse
Without being S-off, no.
honorlost84 said:
Actually I just looked up how to get s off on my phone I'm going to use the fire water tool and then I'll use that link to get the firmware and flash that with the fuu
Click to expand...
Click to collapse
Firewater has been discontinued. You have to use the Sunshine exploit for S-off.

Got a link?

honorlost84 said:
Got a link?
Click to expand...
Click to collapse
Sunshine

Sloth you deserve some Rocky road buddy

And this is what I get. I suppose nothing is simple. I got no clue what is wrong.

Kernel info

Flash a stock rooted ROM from the RUU thread I mentioned previously, then try it again.

I locked boot. Ran a ruu from boot and destroyed my os and it took me all night to recover. Can you please show me how to restore to stock? I'm kinda over it

Now that you've run the RUU, go ahead and run the Sunshine exploit. Afterwards you can go about installing recovery and flashing a new ROM, if you'd like.

Not paying 25 bucks. I'm just wanting stock. My phone got too close to getting the hammer. I'm just gonna go stock. Don't know how

HTC Desire 510 64BIT - return to full stock

Hello everyone
I have some trouble with returning to full stock. Yesterday I thought that I totally bricked my phone. Today it's working on UK Version from one of thread searched in this forum. I have RUU file for my version (i think so). When I'm try to follow steps from tutorials, it ends with fail
Now I have philz recovery, and stock rom UK version.
I started RUU on XP and follow the steps, when I am chosing update it doesn't find my phone.
Maybe it's the case that I have S-ON?
I'm not expert in this area, so please be patient.
Many thanks in advance.

Barti1XL said:
Hello everyone
I have some trouble with returning to full stock. Yesterday I thought that I totally bricked my phone. Today it's working on UK Version from one of thread searched in this forum. I have RUU file for my version (i think so). When I'm try to follow steps from tutorials, it ends with fail
Now I have philz recovery, and stock rom UK version.
I started RUU on XP and follow the steps, when I am chosing update it doesn't find my phone.
Maybe it's the case that I have S-ON?
I'm not expert in this area, so please be patient.
Many thanks in advance.
Click to expand...
Click to collapse
Being s-on doesn't mean anything you can still fix and return a phone to stock and if you already have the phone up and running just find out what your carriers APN is and input that info and you'll be able to get back online and make calls, texts etc.. If you want to S-Off for more control then visit The Root Ninja Sunshine S-Off HTC Desire 510

MrMike2182 said:
Being s-on doesn't mean anything you can still fix and return a phone to stock and if you already have the phone up and running just find out what your carriers APN is and input that info and you'll be able to get back online and make calls, texts etc.. If you want to S-Off for more control then visit *** The Root Ninja Sunshine S-Off HTC Desire 510[/URL]
Click to expand...
Click to collapse
Hi there,
I'm online now, I can make calls etc. But I just want to know, it's possible to return to full stock (I mean recovery, kernel and rom).
I tried to use RUU, but i doesn't work.
When I'm in bootloader I see :
*** Software status : modified ***
*** UNLOCKED ***
*** Security warning ***
When I'm running RUU, I see only option to update software, but on my phone is UK version, and RUU which I use is EU version.
Regards

Barti1XL said:
Hi there,
I'm online now, I can make calls etc. But I just want to know, it's possible to return to full stock (I mean recovery, kernel and rom).
I tried to use RUU, but i doesn't work.
When I'm in bootloader I see :
*** Software status : modified ***
*** UNLOCKED ***
*** Security warning ***
When I'm running RUU, I see only option to update software, but on my phone is UK version, and RUU which I use is EU version.
Regards
Click to expand...
Click to collapse
The EU version I posted works for your phone however i'd keep your phone the way it is because you will have to lock the boot again and reinstall a stock recovery to run the RUU which I can't seem to find(the stock recovery) for your phone and without it you cannot run any RUU.

MrMike2182 said:
The EU version I posted works for your phone however i'd keep your phone the way it is because you will have to lock the boot again and reinstall a stock recovery to run the RUU which I can't seem to find(the stock recovery) for your phone and without it you cannot run any RUU.
Click to expand...
Click to collapse
Actually, I found stock recovery for EU version (on polish forum, btw I'm from Poland). But I don't want to put in there, before I test it. So, please verify my steps.
1. Relock the bootloader. After that I see information which I posted in my previous post.
fastboot oem lock
fastboot reboot-bootloader
2. Reboot to bootloader, flash stock recovery.
fastboot flash recovery [name of my stock recovery]
fastboot reboot bootloader
3. Reboot to bootloader, run RUU.
After that I should have stock software. If I made somewhere any mistake, please tell me. If it will be okay, I'll upload a recovery, so the others will been able to do the same thing.
Regards

Barti1XL said:
Actually, I found stock recovery for EU version (on polish forum, btw I'm from Poland). But I don't want to put in there, before I test it. So, please verify my steps.
1. Relock the bootloader. After that I see information which I posted in my previous post.
fastboot oem lock
fastboot reboot-bootloader
2. Reboot to bootloader, flash stock recovery.
fastboot flash recovery [name of my stock recovery]
fastboot reboot bootloader
3. Reboot to bootloader, run RUU.
After that I should have stock software. If I made somewhere any mistake, please tell me. If it will be okay, I'll upload a recovery, so the others will been able to do the same thing.
Regards
Click to expand...
Click to collapse
Correct.

MrMike2182 said:
Correct.
Click to expand...
Click to collapse
Hi there, it's me again.
I finally get into RUU, and start STOCKing but it stops at step 2/8 (updating software - 100%). I wait 10,20,30 minutes and nothing...
I don't have any idea what I can do. I run XP on VM Oracle, because on 8.1 I was unable to start RUU.
Could you have access to any backup for Philz recovery?
Regards

Barti1XL said:
Hi there, it's me again.
I finally get into RUU, and start STOCKing but it stops at step 2/8 (updating software - 100%). I wait 10,20,30 minutes and nothing...
I don't have any idea what I can do. I run XP on VM Oracle, because on 8.1 I was unable to start RUU.
Could you have access to any backup for Philz recovery?
Regards
Click to expand...
Click to collapse
It's most likely stuck because your stock recovery is either not the correct one, or installed incorrectly. The RUU is known to stop there when it detects that the recovery partition has been modified and doesn't have the stock one on there... I also have no idea where to get you a stock recovery.img... I'm sure there is one around the net somewhere, if you search for it.

What do you exactly mean? I try to extract recovery from rom.zip from RUU temp folder but archive is incorrect or something like that. Later I'm going to extract it using unruu on Ubuntu 15.10.
Regards