Database Info

How To UN ROOT. TUTORIAL. Your Problems are solved!

UPDATE: With all of the newer rooting and S-Off methods, and new hardware and firmware revisions, this thread may or may not help with your specific case if trying to unroot and go back to unrooted stock. I originally wrote this based of of the very first root methods known for the Launch EVO. There is a good chance that this method will still work, but there could definitely be something unaccounted for in your own specific case, so tread with caution. It is very doubtful that anything in this tutorial will result in your EVO becoming a fancy-schmancy paperweight, but if something goes afoul, you could have a nice headache to deal with...
Ok guys. There is a lot of partial and mis-information floating around out there about how to UN ROOT if you have to send your phone back for replacement, or you want the official unrooted OTA 2.2.
OLD NEWS!!!---> NEWER METHODS AVAILABLE TO ACTUALLY FIX PRI DOWNGRADE> SEARCH!!!! EDIT your PRI to show 1.40, thanks to sturmen for the pointer, and Calkulin for the method: http://forum.xda-developers.com/showpost.php?p=7267559&postcount=66
This assumes you are full root, S-Off. Note, this is not tested with simple root but should work (EDIT, Simple Root is basically Toastcfh's method, so you simple root users should be set), only with Toastchf's root method and nand unlock.
After reading every thread on the forum here, I think I finally found a fool proof way to do it. All the info was out there, but in several places and each one was missing something.
1) Before you start clicking and flashing and running RUUs, Check your HBoot build. You need to have the 0.76.2000 from Toastcfh's method #2. If you have 0.79.0000 (whatever) go to step 2 below. If you're getting Bootloader errors when running an RUU, I can almost guarantee that you don't have the correct HBOOT. If you somehow still have 0.76.2000 from previous modding, proceed to step 3.
2) Toast's Nand Unlock method. Found here: http://forum.xda-developers.com/showthread.php?t=701835
EDIT: The more I think about it, I think you can just run Simple Root to re-attain the .76 HBOOT and engineering build. It would eliminate the need for any adb, and SHOULD produce the same results. Just run the RUU after you run and complete simple root. See notes in BLUE below too!
THIS STEP IS 100% NECESSARY IF YOU HAVE THE .79 HBOOT version!!!...Do step #2 in Toast's thread, just like you did when you originally unlocked NAND (OR YOU SHOULD BE ABLE TO JUST RUN SIMPLE ROOT AGAIN...UNconfirmed, but should work methinks...). Not 100% sure which steps are necessary, but I do know you need to do steps #1 (Well, #1 is Nandroid Backup, so proceed at own risk if you skip) and #2 again. Make sure after you flash the Flash_Image, and the mtd-eng through adb, that you then load the PC36IMG.zip (Engineering Build), onto the root of your SD card, and boot into HBOOT, and let it install (just like you did when rooting). I didn't bother to flash the Recovery image at the end of step 3, but I don't think it would hurt if you're nervous about losing a custom recovery image in case this method for some reason does not work. It has come to my attention that flashing the engineering build (the PC36IMG from Toast's thread)through fastboot, might be as crucial as simply having the .76 HBOOT version. It at least is a surefire way to make sure you can run an RUU on top of it. There are probably other builds/roms that will work and allow you to run the RUU, but this one is confirmed, so don't skip that step!
3) If you have the 0.76.2000 HBOOT (can be checked by powering down, and booting by holding VOL down and Power), then you can go ahead and boot into the rom, and proceed with downloading the RUUs found here: http://shipped-roms.com/shipped/Supersonic/
Go ahead and download the first one (at least). I think the others are optional to "upgrade" but why should we care. We just want to go back to unrooted stock.
4) Make sure you have the latest version of HTC Sync installed, found here: http://www.htc.com/uk/SupportViewNews.aspx?dl_id=933&news_id=627
Install, and let it do it's thing. Will probably have to restart your PC when complete. Not even 100% sure this is necessary, but it won't hurt. It's basically for the HTC drivers from what I understand.
5) Run the RUU from your pc while your evo is in the phone loaded state of the Rom, (not the bootloader) with the phone connected through USB and have HTC sync selected. Even if it doesn't connect to HTC sync on your PC, you should be ok.
If you get a USB error after the screen goes black with the HTC LOGO, don't touch the phone. Exit the RUU via the EXIT button when given the option.
6) Run the RUU again and see what happens. The Error could happen 1 more time, but just exit again, and run RUU one last time.
7) Thank everyone here at XDA that our EVOs are so badass...I'm certinly not a dev, but these devs work hard for us to have the baddest ass phone there is right now.
Any problems, let me know. I assume your errors are the same ones I was getting, and it's all because of the wrong HBOOT.
I really take no credit for this, as I'm just compiling information in a tut....

Thanks op.

Or you can flash the new FroYo update release. =D
But thanks OP. Your hard work is much appreciated.

arozer said:
Or you can flash the new FroYo update release. =D
But thanks OP. Your hard work is much appreciated.
Click to expand...
Click to collapse
You might be correct, but I couldn't get the FROYO OTA to show up in any of the roms I was using.

Question: what's the deal with the PRI? Has anyone been able to properly fix that yet?

sturmen said:
Question: what's the deal with the PRI? Has anyone been able to properly fix that yet?
Click to expand...
Click to collapse
From my research, NO...Unfortunately, but this should get you as good as possible with what's out there now..
EDIT: Yess! See below and in OP!

Bang3r said:
From my research, NO...Unfortunately, but this should get you as good as possible with what's out there now..
Click to expand...
Click to collapse
Hm. I think I remember someone made a hex-edited PRI that people can flash in case they have to return it. I'll find it...

sturmen said:
Hm. I think I remember someone made a hex-edited PRI that people can flash in case they have to return it. I'll find it...
Click to expand...
Click to collapse
That would be cool, but I'm not too worried about that part. Phone is going back tomorrow!

Well, worry even less! Special thanks to Calkulin!

thankssssss

Thanks a lot for this. I have searched for a un root that worked and you were right the bootloader was the problem. Followed directions here and I am back to stock Froyo un rooted.
Thanks
topcop

I followed your guide and ran into a few issues. From my experiences, you can only run the RUU from your software version or higher (Can't use a 1.32 RUU on a Evo with software version 1.47). Therefore, I think everyone should always flash the engineering build so they can use the earliest RUU. Just my 2 cents though...

I'm getting error 155 running Ava Froyo and trying to go back.

blix1337 said:
I followed your guide and ran into a few issues. From my experiences, you can only run the RUU from your software version or higher (Can't use a 1.32 RUU on a Evo with software version 1.47). Therefore, I think everyone should always flash the engineering build so they can use the earliest RUU. Just my 2 cents though...
Click to expand...
Click to collapse
Yes, you are correct, but so am I. This is exactly what step 2 in the OP does (which is a link to Toastcfh's thread about the engineering build).

tonyk__78 said:
I'm getting error 155 running Ava Froyo and trying to go back.
Click to expand...
Click to collapse
Ok. RE-read the OP. Everything is there. Check your HBOOT version by booting to the bootloader. If you have .79, you need to re-flash the engineering build before the RUU will work (Step 2 in the OP to get HBOOT to .76). You cannot run the RUU on top of AVA froyo or any froyo, or any rooted custom 2.1 for that matter if you don't have the proper HBOOT (Which I believe you cannot have if you are running any custom rom). Flash to the engineering build, then the RUU.

How far "unrooted" does this get you? Can you still re-root using toast's method or SimpleRoot?

joypunk said:
How far "unrooted" does this get you? Can you still re-root using toast's method or SimpleRoot?
Click to expand...
Click to collapse
Yes you can still REroot VIA those methods. As long as you don't do a FROYO OTA or manually flash the UNROOTED Froyo...there is no ROOT method for FROYO yet.
It returns completely to UNROOTED stock, except for the PRI, which there is a fix for on the 1st page.
And incidentally (and I just figured this out last night) Simple Root is Toast's method, just automated...
EDIT: I think that you could even UNROOT and RUU to 1.3x (whatever it is), then use the ROOTING methods that were in place before the official 1.47 OTA rooting methods. But, I just did simpleroot last night on top of 1.47, and it is freaking SIMPLE....1 click for root...1 click to flash recovery.

tpdtopcop said:
Thanks a lot for this. I have searched for a un root that worked and you were right the bootloader was the problem. Followed directions here and I am back to stock Froyo un rooted.
Thanks
topcop
Click to expand...
Click to collapse
This is what were trying to show you on Androidcentral as well. Glad you are set!

tonyk__78 said:
I'm getting error 155 running Ava Froyo and trying to go back.
Click to expand...
Click to collapse
As long as you have .76 HBOOT flash back to an earlier rom...one that has a 1.32 base. Then use the 1.32 RUU or 1.47 RUU. You should be set. Make sure you have completed step 2 in OP.

Yes. I have .79, thanks!
Sent from my PC36100 using XDA App

Noob Question About S-On, S-Off, and HTC's unlock

I used HTC's official unlock and my phone is unlocked, but has S-On. Is there a benefit to S-Off now that mine is unlocked? What is the difference between how the unlocks are? Sorry if i'm not making much sense, I'm new to this place and Android in general... I just got my sensation last week.

Welcome to Sensation
Don't worry, everyone's a noob at some point, I'm pretty much still a noob myself but as far as I understand it:
To this point you have unlocked your bootloader which simply allows the phone to boot with third-party software installed. In your phone there is a form of security check and the level of security is determined by whether you are S-ON or S-OFF. It's a flag at the radio level of your phone that checks images before they are allowed to be written to the system memory. So when you gain S-OFF, you gain unrestricted access to the NAND flash memory on your device, also known as root. With S-ON you can get temporary root but it's not guaranteed, with S-OFF you can get permanent root no matter what you flash.
Essentially gaining S-OFF permits superuser access to the phone, giving you control over all aspects of software and hardware.
If you like your phone the way it comes to you, all filled up with bloatware and stuck using only the latest version of Android that your carrier releases OTA, with a boring/crappy splash screen and boot animation (and so on and so forth ) then you have no real reason to get S-OFF.
If however you have seen some of the shiny ROMs put together by the devs here at XDA, or have a sweet custom splash screen you'd love to see every time you boot up the phone, or just like the idea of having complete control over YOUR phone and flashing what-the-hell-ever ROM/firmware/radio/other stuff you damn well please, then you should definitely consider rooting.
The disclaimer to all this is that if you aren't careful and don't thoroughly research what you're doing BEFORE you do it, you could brick your phone and give yourself some serious grief. The fact you're even asking this now is a point in your favour, there are far too many 'help me' posts on here from people who did something without bothering to try and understand it first. Knowledge is power and there's buckets of knowledge on this forum and others.
I'd suggest reading here and here at the very least.
Hope that helps

s-off means you may do anything with your phone,
you will lose warrenty at s-off gain it at s-on
as the other guy said if u want a nice toutch to your rom s-off it and install, if u want it still legal dont

Thanks for the info. I've been considering using an ICS OTA file on my HTC Sensation 4G, but the guides i've seen only mention S-OFF and nothing about the unlocked S-ON. I just can't wait for the official release!
On the other hand though, I also want to remove bloatware from this phone and found a script for such... but i can't seem to get any temp root method working. I'm not ready to jump off the deep end yet, but i'm tired of the unnecessary stuff.

I also couldn't wait for the official ICS release so I s-off, rooted, super CID, and flashed an ICS firmware and went to android revolution. Honestly, it's one of the best decisions Ive ever made. If you think your stock phone is running good right now, you'll be amazed when you flash it, it will run absolutely faster I tell you.
Though there are alot of risks doing all of that, it might brick your phone completely. So be very careful, read and understand everything if you're going to do all of those stuff.
Sent from revolutionized HTC Sensation ICS

HTC sensation stuck at boot
Hey Guys Noob here,
I need help big time. I gone and mess with something I shouldn't have. I'm a first time android/touch screen user so bear with me.
I was trying to S-off my phone (alrady rooted- after several tries) but I downloaded the juopunutbear zip file on my phone. I mistakenly loaded it via the CWM recovery and now the screen is stuck on that juopunutbear image.
I have tried to flash my rom because I thought it was just a boot loop, but nothing happened. I NEED some advice please don't tell me I bricked it. :crying:

man+droid said:
Hey Guys Noob here,
I need help big time. I gone and mess with something I shouldn't have. I'm a first time android/touch screen user so bear with me.
I was trying to S-off my phone (alrady rooted- after several tries) but I downloaded the juopunutbear zip file on my phone. I mistakenly loaded it via the CWM recovery and now the screen is stuck on that juopunutbear image.
I have tried to flash my rom because I thought it was just a boot loop, but nothing happened. I NEED some advice please don't tell me I bricked it. :crying:
Click to expand...
Click to collapse
if you can boot into bootloader then you are not bricked
secondly what do you mean by juopunutbear.zip and from where?
edit:you said that you are already rooted
which means that you have unlocked bootloader from htcdev site am i right?

Yes it was already unlock from HTC dev, but I was trying to get S- off using the wire trick method. In reading the Jounutbear guide thread it directed u to a link which has the zip file which I should have run on my pc but I had mistakenly installed it from my sd card and now it isn't going furthuer than that screen. I now can't using the Jbear exe bcuz it not recogining it.
I don't really want to keep adding my nonsense to the thread how can I PM someone for help.

man+droid said:
Yes it was already unlock from HTC dev, but I was trying to get S- off using the wire trick method. In reading the Jounutbear guide thread it directed u to a link which has the zip file which I should have run on my pc but I had mistakenly installed it from my sd card and now it isn't going furthuer than that screen. I now can't using the Jbear exe bcuz it not recogining it.
I don't really want to keep adding my nonsense to the thread how can I PM someone for help.
Click to expand...
Click to collapse
do this
install 4ext recovery
enable smartflash from it
flash the rom
http://forum.xda-developers.com/showthread.php?t=1631861

I did all that but the phone keeps booting up with the Juoputnutbear image that point to the phone. It looks similar to when I was just rooting the phone but it just no picking up nothing but that.

man+droid said:
I did all that but the phone keeps booting up with the Juoputnutbear image that point to the phone. It looks similar to when I was just rooting the phone but it just no picking up nothing but that.
Click to expand...
Click to collapse
that's weird
did you perform a full wipe(from recovery) before flashing the rom?
also as long as you are on S-ON use 4ext recovery to flash the rom
and before flashing the rom enable smartflash from 4ext
if you have done all the above then use a ruu.exe to return to stock condition
http://forum.xda-developers.com/showthread.php?t=1672425

Well that thread seems to be a mouth full remember I'm a noob. But I will try and read that again to get what it really says. It seems though that it was a complex instruction how to get back to the stock rom? Isn't there a file for that I can download. I get to doing that RUU thing to see if it works tho

man+droid said:
Well that thread seems to be a mouth full remember I'm a noob. But I will try and read that again to get what it really says. It seems though that it was a complex instruction how to get back to the stock rom? Isn't there a file for that I can download. I get to doing that RUU thing to see if it works tho
Click to expand...
Click to collapse
i saw your post in the other thread
you managed to install 4ext
now try to flash a custom rom
before flashing the rom enable smartflash from 4ext

Hey guys good news
I finally got the phone to power on. I saw this thread that highlead my pro http://forum.xda-developers.com/showthread.php?t=2284273 but I was really got the details from another forum. I don't know if I'm allowed to post it so I won't, but I'll sum it up.
All I need to do was flash the boot image on my current rom (get this from the zip file) and also flash the recovery image from a backup I had and presto.
But I'll go and follow you guys instruction about enabling the 4ext smart flash from now on. What I want to know though is for some custom roms (eg cyanogenmod 10.1) do I needs to be S-off to install it?
If so I'm still gonna try and S-off this here thingy. Givethanks y'all

man+droid said:
Hey guys good news
I finally got the phone to power on. I saw this thread that highlead my pro http://forum.xda-developers.com/showthread.php?t=2284273 but I was really got the details from another forum. I don't know if I'm allowed to post it so I won't, but I'll sum it up.
All I need to do was flash the boot image on my current rom (get this from the zip file) and also flash the recovery image from a backup I had and presto.
But I'll go and follow you guys instruction about enabling the 4ext smart flash from now on. What I want to know though is for some custom roms (eg cyanogenmod 10.1) do I needs to be S-off to install it?
If so I'm still gonna try and S-off this here thingy. Givethanks y'all
Click to expand...
Click to collapse
any ICS/JB rom you can install via enabling smartflash in 4EXT before flashing the ROM

ganeshp said:
any ICS/JB rom you can install via enabling smartflash in 4EXT before flashing the ROM
Click to expand...
Click to collapse
Hey thanx for the heads up. So I'm finally s-off using the J-bear method but where unlocked use to be I'm now seeing the juopunutbear there so I got back into android but it was the old CWM that was on it how do I get back the 4ext and would that be a prob if that J name remains there tho?

man+droid said:
Hey thanx for the heads up. So I'm finally s-off using the J-bear method but where unlocked use to be I'm now seeing the juopunutbear there so I got back into android but it was the old CWM that was on it how do I get back the 4ext and would that be a prob if that J name remains there tho?
Click to expand...
Click to collapse
no you are fine now
there is no problem with juopunutbear because now you have patched hboot which is unlocked
you are fine also with cwm recovery
but if you still want 4ext do only step 2 from here
http://forum.xda-developers.com/showthread.php?t=1631861

man+droid said:
I did all that but the phone keeps booting up with the Juoputnutbear image that point to the phone. It looks similar to when I was just rooting the phone but it just no picking up nothing but that.
Click to expand...
Click to collapse
might be a bad dl. Download it again and reflash or try a different rom.

[Q] HELP sensation flashed ROM wont start

Hello, first I would like to apologize as I am clearly a noob and have very little idea of what I am talking about.
I'm sure my problem has been asked before and that if I had any idea what the problem was, I could find the exact solution I need here on the forums. Unfortunately I don't even know what to search for. If any one would like to complain go ahead but please..just help me.
So I decided to root my HTC Sensation, which I believe I did without any problem, I followed the guide on this site. Nothing went wrong and as far as I was aware everything was working fine.
I then decided to flash a new ROM onto the phone. I chose the Android Revolution HD as this looked to be the popular choice. I got it from here and I believed I had followed the instructions on how to install it properly.
However, after installing the ROM I came upon a problem, the phone would not start, it would just go to the HTC boot screen and stay there forever. At first I couldn't even get back to the hboot screen, but after inserting a new and better charged battery I was able to get there, but every time I do it attempts to update and says " CID incorrect! Update Fail! Press <POWER> to reboot." and I cant do anything but get stuck in this continuous loop.
If I take the SD card out I can access the HBOOT properly, however trying to do a recovery at this point doesn't seem to work.
I have no idea what to do and would appreciate any help anyone can give me. I would be happy to just have my phone back to the way it was originally.
Thanks

Might wanna try a RUU? not sure but hopefully it should do..
Sent from my HTC-Z710a using xda premium

First off your MAJOR issue is that you flashed a rom for the Desire HD section(As soon as I clicked on your link, it said Android Revolution 7.0.2... I was like wtf? There is no 7.0.2 on the sensation forum) ... I think that's the prob... for now! Flash the correct rom and stay in the right section!
Second, I don't see why you can't get into recovery. Remove your sd card, power on the phone by holding vol-down +power to get to bootloader, select recovery and flash the right rom. I would also recommend that you delete the P58IMG.zip off your sd card as well. I'm assuming you have it on there for the ICS firmware but flashed the incorrect rom. You are far from bricking it, but keep this up and it might turn into one!

Thanks, your post is certainly reasuring though I am still not sure how to continue. Also it is possible I gave the wrong link to the rom I used, though it definitely was the same name.
Anyway what Im thinking I have to do now is 1st delete p58img.zip file from my SDcard and put the right rom on there, could you link to one?
So by removing that file I should be able to access the SDcard again and flash the new rom?

Dashdor said:
Thanks, your post is certainly reasuring though I am still not sure how to continue. Also it is possible I gave the wrong link to the rom I used, though it definitely was the same name.
Anyway what Im thinking I have to do now is 1st delete p58img.zip file from my SDcard and put the right rom on there, could you link to one?
So by removing that file I should be able to access the SDcard again and flash the new rom?
Click to expand...
Click to collapse
Here's the right link
http://forum.xda-developers.com/showthread.php?t=1098849
This is an ICS (Ice Cream Sandwich) Rom
So you need:
1) SuperCID (so that you can flash any firmware)
Instructions
2) Flash the ICS firmware (otherwise you can't use the ICS roms)
http://goo.gl/RcbMy (and make SURE that there aren't any errors - errors such as not doing the SuperCID process correctly, therefore it can't flash - I say this because it seems like many users think the firmware is flashed and then find out their rom won't start, so don't be stupid and check whether or not an error has occurred just incase!)
3) Pick a rom
Revolution
Elegancia
Insert Coin
4) Flash the 4EXT recovery, I'm sure you already have clockwork mod on there but I think that's a bit buggier... so if I were you, I'd go for the 4EXT touch recovery
http://forum.xda-developers.com/showthread.php?t=1377759
5) If you wish, you can also flash for example: tweaks and addons by awsm devs which make our phone much better if you wish!
6) you're good to go! It's that easy.
Yeah, all you have to do is remove that P58IMG.zip from your sd card and your bootloader won't force you to update or w/e. You'll be fine.

And don't forget to md5 check for roms you download !
Sent from my HTC-Z710a using xda premium

Thank you very much. It seems I hadn't performed the SuperCID part. Once I had done that I installed Elegancia and it is working perfectly.
Thanks again for your help, I really appreciate you taking the time to explain that to me.

[Q] Flash Back to HTC Stock

So I just spent ages installing Pacman Rom onto my phone, only to realise I've come to the end of my contract and will get an upgrade instead!
I'd like to take it back to a decent HTC stock rom, with an updated Sense and so on, and give that handset to my Mum.
My phone is currently rooted and s-off. As I understand it, I need to:
Create a backup using CWM or similar
Follow this video and use Android Flasher to remove Revolutionary while in Bootloader
Copy an appropriate RUU file to the SD card and install from wthin the Bootloader
Does this sound legit? I've ran into Errors 131 and 140 before while trying to run an RUU off my desktop. Also is it possible just to get an HTC RUU with Android 2.3.5 on it rather than factory 2.3.3?

xTheLostProphetx said:
So I just spent ages installing Pacman Rom onto my phone, only to realise I've come to the end of my contract and will get an upgrade instead!
I'd like to take it back to a decent HTC stock rom, with an updated Sense and so on, and give that handset to my Mum.
My phone is currently rooted and s-off. As I understand it, I need to:
Create a backup using CWM or similar
Follow this video and use Android Flasher to remove Revolutionary while in Bootloader
Copy an appropriate RUU file to the SD card and install from wthin the Bootloader
Does this sound legit? I've ran into Errors 131 and 140 before while trying to run an RUU off my desktop. Also is it possible just to get an HTC RUU with Android 2.3.5 on it rather than factory 2.3.3?
Click to expand...
Click to collapse
Yes, look at the Index, search and read - all the answers are there already.

SimonTS said:
Yes, look at the Index, search and read - all the answers are there already.
Click to expand...
Click to collapse
Hey, I've spent the past few hours searching the forum and googling. Not been able to find the answers so far... Can I just place an RUU.exe and run it off my SD card? It seems removing root using Android Flasher will leave me with Pacman rom... Surely having s-on and a custom rom will mess up my phone?

get PG88IMG.zip and flash it through bootloader

441Excelsior said:
get PG88IMG.zip and flash it through bootloader
Click to expand...
Click to collapse
Thanks a lot, this worked great!

its the easiest method

HTC One SV (Swisscom) Update 3.11.166.7 fails

Starting the proposed SW Update 3.11.166.7 on a HTC One sv (Swisscom) generates the message "E: Error installing zipfile INTERNALSDCARD: Download OTA_K2_ul_JB422_Sense50_MR_Vodafone_CH_DE 3.11.166.7...zip http://forum.xda-developers.com/images/smilies/confused.gif
[Rooted/S-Off (Moonshine)/unlocked bootloader and SID 111111]
Who knows the probably reason/solution ???
Thanks a lot for any help!
JAS

Seems that something stock is missing,then the update fails.

Seems that something stock is missing,then the update fails.
old.splatterhand said:
Seems that something stock is missing,then the update fails.
Click to expand...
Click to collapse
Thank you, but I don't understand what you mean with "Seems that something stock is missing,then the update fails."
I can imagine, that it has probably something to do with my changment of the CID from VODAP110 (Swisscom) to SID 111111.
In the Bootloader I get CID 111111, the System still says VODAP110.
Greetings
JAS

If your bootloader says 11111111, you should have SuperCid.
Would be new to me, that you can see the CID in the OS, i think what you see is something else.
The OTA update checks your system partition and your recovery, if all files the OTA wants to update are available. If one file is missing, the update stops.
Usually the system has write protection, but with S-off this is gone.
So you maybe deleted files or something else like this (also when you are not aware that you did).

SW Update 3.11.166.7 fails
old.splatterhand said:
If your bootloader says 11111111, you should have SuperCid.
Would be new to me, that you can see the CID in the OS, i think what you see is something else.
The OTA update checks your system partition and your recovery, if all files the OTA wants to update are available. If one file is missing, the update stops.
Usually the system has write protection, but with S-off this is gone.
So you maybe deleted files or something else like this (also when you are not aware that you did).
Click to expand...
Click to collapse
OK. I use a Root Explorer and it says/sees under CID still: VODAP110, the original CID of Swisscom, which I changed to SID 111111.
At the start of the update installation it mentions something like " Kernel does not have Support to reading SELinux contexts"!
Thats the only sign, that something goes wrong, then the update is soon interupted with the message I Wort in my first thread.
It is quite possible, that I deleted files, but how can I find out, which file(s) are missing?
I read in the Google in some Forum that the Update doesn't work on rooted devices, could this this be a possible reason in my case?
Thank a lot
JAS

Root itself is not a problem, only what you do with it (deleting something).
To make the story short, if you don't have a stock backup, i don't see any chance to restore a swisscom rom.
There is nothing available for swisscom.
You have three ways to go:
- remember what you deleted or restore a stock backup if you have (or maybe you know somebody who can provide you a stock backup)
- stay at the software you have
- unbrand your device and flash the free, european software

old.splatterhand said:
Root itself is not a problem, only what you do with it (deleting something).
To make the story short, if you don't have a stock backup, i don't see any chance to restore a swisscom rom.
There is nothing available for swisscom.
You have three ways to go:
- remember what you deleted or restore a stock backup if you have (or maybe you know somebody who can provide you a stock backup)
- stay at the software you have
- unbrand your device and flash the free, european software
Thanks for the very fast answer!
I prefer your third proposition and ask you, how to unbrand the device (is it necessary to do so) and where to get this free, european Software (Link to) which works on a HTC One sv?
PS: Sorry for the silly Question, but what means
Greetings
JAS
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Johann A. Sutter said:
PS: Sorry for the silly Question, but what means [ QUOTE]
Click to expand...
Click to collapse
Thats part of t forum BB Code.
The most important part for you is already done, because you are S-off and you have Supercid.
Now follow this guide (use files for k2ul):
http://forum.xda-developers.com/showthread.php?t=2386426
- backup everything what is important for you
- Downgrade hboot
- run the RUU
- run all updates
- profit
Skip the steps to get S-on, thats not needed in your case.

old.splatterhand said:
Thats part of t forum BB Code.
The most important part for you is already done, because you are S-off and you have Supercid.
Now follow this guide (use files for k2ul):
http://forum.xda-developers.com/showthread.php?t=2386426
- backup everything what is important for you
- Downgrade hboot
- run the RUU
- run all updates
- profit
Skip the steps to get S-on, thats not needed in your case.
Click to expand...
Click to collapse
Hi old.splatterhand
Thank you, everything worked well, exept that my hboot is now 1.01.0000 and with this, I'm no more able to unlock the bootloader, respectively to root the device. Trying to start with the wellknown act to come in the bootloader mode gives me always only the possibility to choose either to accept or to denie an update by using the volume up or down button and then the power button.
Because i'm working often with a root Explorer, it's important to be able to Change in the root mode.
I googled and realized, that a lot of People has the same Problem and no solution!
Thank you again, probably you can help in this case too!!!???
JAS

What is the actually state of your device? Did you runn the RUU and updated to the latest Android 4.2.2?
To stop the flashing process, remove the PL80IMG.zip from your sdcard. Delete it in Android OS or put your sdcard into a pc and delete it there.

old.splatterhand said:
What is the actually state of your device? Did you runn the RUU and updated to the latest Android 4.2.2?
To stop the flashing process, remove the PL80IMG.zip from your sdcard. Delete it in Android OS or put your sdcard into a pc and delete it there.
Click to expand...
Click to collapse
Hi
Indeed, it was the PL80IMG.zip which turned me nearly crasy!
Removing the SD Card brought already the solution of this (hopefully) last Problem.
I have to install the TMRP recovery still, but I think, i'll work this for my own!
A big thank you for all your admirable knowledge and the Patience ...!!!
JAS

Johann A. Sutter said:
Hi
Indeed, it was the PL80IMG.zip which turned me nearly crasy!
Removing the SD Card brought already the solution of this (hopefully) last Problem.
I have to install the TMRP recovery still, but I think, i'll work this for my own!
A big thank you for all your admirable knowledge and the Patience ...!!!
JAS
Click to expand...
Click to collapse
You are welcome