[SOLVED] Unroot Three UK HTC One

mrgreeny · Mar 14, 2014

Hi everyone,

I'm having some issues with my HTC One and might need to send it back for Warranty repair. I can't find the RUU anywhere for Three UK.

Does anyone know a way for me to unroot my HTC One, so to speak?

I am a bit of a noob, so go easy on me!

Thanks.

nkk71 · Mar 14, 2014

mrgreeny said:
Hi everyone,

I'm having some issues with my HTC One and might need to send it back for Warranty repair. I can't find the RUU anywhere for Three UK.

Does anyone know a way for me to unroot my HTC One, so to speak?

I am a bit of a noob, so go easy on me!

Thanks.

There is no RUU for you, check my guide: http://xdaforums.com/showthread.php?t=2541082
(read it a couple of times, and then let me know if something is not clear)

mrgreeny · Mar 14, 2014

nkk71 said:
There is no RUU for you, check my guide: http://xdaforums.com/showthread.php?t=2541082
(read it a couple of times, and then let me know if something is not clear)

So is your route not possible with Windows 8, then?

nkk71 · Mar 14, 2014

mrgreeny said:
So is your route not possible with Windows 8, then?

The main problem is Win8.1, it should work with Win8 (as far as most users said)... if you do get stuck just have an Ubuntu Live USB ready (it's under the FAQs), Ubuntu won't give you a hard time with drivers etc.

mrgreeny · Mar 14, 2014

nkk71 said:
The main problem is Win8.1, it should work with Win8 (as far as most users said)... if you do get stuck just have an Ubuntu Live USB ready (it's under the FAQs), Ubuntu won't give you a hard time with drivers etc.

Ok, thank you!

mrgreeny · Mar 17, 2014

nkk71 said:
There is no RUU for you, check my guide: http://xdaforums.com/showthread.php?t=2541082
(read it a couple of times, and then let me know if something is not clear)

(Sorry for double post)

So I don't have a RUU for Three UK, so I'd go down the CWM route? I believe my thing is x.xx.771 from what I've read.

Then all I need to do is follow those steps in the fourth post for the CWM route, and then I'll be completed unrooted and hopefully back to normal for warranty repairs?

nkk71 · Mar 18, 2014

mrgreeny said:
(Sorry for double post)

So I don't have a RUU for Three UK, so I'd go down the CWM route? I believe my thing is x.xx.771 from what I've read.

Then all I need to do is follow those steps in the fourth post for the CWM route, and then I'll be completed unrooted and hopefully back to normal for warranty repairs?

Three UK is CID H3G__001 so yes, use the CWM method and you can even use the files mentioned in post #4, since the example I was using is Three UK.

About the S-On part: from what I've seen, the UK seems pretty lenient with all that, but if you do intend on going S-Off to S-On, you do so as mentioned in the guide before any OTA to 3.xx

mrgreeny · Mar 21, 2014

nkk71 said:
Three UK is CID H3G__001 so yes, use the CWM method and you can even use the files mentioned in post #4, since the example I was using is Three UK.

About the S-On part: from what I've seen, the UK seems pretty lenient with all that, but if you do intend on going S-Off to S-On, you do so as mentioned in the guide before any OTA to 3.xx

I assume to make sure it's definitely safe to return for warranty I should go back to S-On, though?

Is there any risk of bricking the device?

nkk71 · Mar 21, 2014

mrgreeny said:
Is there any risk of bricking the device?

Can I say that 100% -> no, you could have a power outage, your favourite pet, your "favourite" child

, mess with your phone / usb / pc connection at exactly the right (wrong) nanosecond when hboot is being flashed. which may or may not result in a brick.

So I scared you a little there

But in general, no, there is no bricking involved as long as you flash things made for your phone. (ie don't go flash HTC Droid stuff on the M7)

at least nobody has complained in my thread causing a brick.

mrgreeny said:
I assume to make sure it's definitely safe to return for warranty I should go back to S-On, though?

If you want your phone to look 100% out of the box, I would say yes to the s-on part, though most posts about UK repairs have shown that they don't really care. but no harm in going S-On.

BUT, please follow the guide correctly, if you have questions, feel free to ask.
the guide has worked for many people (and was actually written after having it done in various threads, so it's sort of a result of experience, not only theory),
but if something isnt clear or doesn't make sense, you should ask; I have no issues with people asking why THIS, and why THAT, and why NOW

I prefer a question before, rather than a question after .... (yeah so I skipped step x cause I thought I didn't need it... so now what

... and yeah I didnt bother with reading it once or twice including the FAQs cause

you probably wrote them for someone else

)

mrgreeny · Mar 21, 2014

nkk71 said:
Can I say that 100% -> no, you could have a power outage, your favourite pet, your "favourite" child , mess with your phone / usb / pc connection at exactly the right (wrong) nanosecond when hboot is being flashed. which may or may not result in a brick.
No silly childrena round
So I scared you a little there
But in general, no, there is no bricking involved as long as you flash things made for your phone. (ie don't go flash HTC Droid stuff on the M7)

at least nobody has complained in my thread causing a brick.

Haha besides those points obviously!

Thank you!

nkk71 said:
If you want your phone to look 100% out of the box, I would say yes to the s-on part, though most posts about UK repairs have shown that they don't really care. but no harm in going S-On.

BUT, please follow the guide correctly, if you have questions, feel free to ask.
the guide has worked for many people (and was actually written after having it done in various threads, so it's sort of a result of experience, not only theory),
but if something isnt clear or doesn't make sense, you should ask; I have no issues with people asking why THIS, and why THAT, and why NOW

I prefer a question before, rather than a question after .... (yeah so I skipped step x cause I thought I didn't need it... so now what ... and yeah I didnt bother with reading it once or twice including the FAQs cause you probably wrote them for someone else )

Thank you very much. I shall do it later today or on Monday. Hopefully it will all go to plan!

nkk71 · Mar 21, 2014

mrgreeny said:
Haha besides those points obviously! Thank you!

Thank you very much. I shall do it later today or on Monday. Hopefully it will all go to plan!

sure no problem,

remember: if something doesn't make sense to you, go ahead and ask.... no harm in asking

mrgreeny · Apr 8, 2014

nkk71 said:
sure no problem,

remember: if something doesn't make sense to you, go ahead and ask.... no harm in asking

Can't get S-Off to work. Just posted in http://xdaforums.com/showthread.php?t=2632351&page=45 still waiting on a reply.

You may have an idea?

C:\Users\Michael>adb reboot

C:\Users\Michael>adb wait-for-device push Desktop/firewater /data/local/tmp
3116 KB/s (4432776 bytes in 1.389s)

C:\Users\Michael>adb shell
ViperOne@/# su
su
ViperOne@/# chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
ViperOne@/# /data/local/tmp/firewater
/data/local/tmp/firewater
/data/local/tmp/firewater

==================== firewater S-OFF 8.0.4.6 ===========================

firewater S-OFF comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for users
however the authors disclaim any liability for damage to your phone
or other materials or devices used during this process.

The entire risk of running firewater S-OFF lies with you, the user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever caused.

firewater S-OFF may not be rehosted, repackaged, one-clicked, etc.
support is available @ #firewater on the freenode and andirc networks
support is much faster there vs. posting helpme threads on xda etc

Do not operate a motor vehicle after interacting with firewater
Do not inhale firewater or allow firewater to come in contact with eyes
firewater is best served at extremely cold temperatures
firewater has been known to cause temporary lapses in judgement
DO NOT TAUNT FIREWATER, YOU'VE BEEN WARNED

=========================================================================

Do you understand the implications of these warnings?

(Yes/No)
Yes
Yes

!!If firewater hangs for more than 2 minutes or device enters qhusb mode, ho

!!If firewater hangs for more than 2 minutes or device enters qhusb mode, ho
ld power for 60 seconds !!
C:\Users\Michael>

Any ideas what's happening here? If I leave it too long on the Yes/No it also kicks back to C:\ Have to type Yes really quickly.

nkk71 · Apr 8, 2014

mrgreeny said:
Can't get S-Off to work. Just posted in http://xdaforums.com/showthread.php?t=2632351&page=45 still waiting on a reply.

You may have an idea?

Any ideas what's happening here? If I leave it too long on the Yes/No it also kicks back to C:\ Have to type Yes really quickly.

Not really, but can you post output of fastboot getvar all and which version of viperone you're using?

mrgreeny · Apr 8, 2014

nkk71 said:
Not really, but can you post output of fastboot getvar all and which version of viperone you're using?

Just done a nandroid backup, and when rebooting it said I needed to fix root?

For firewater to work, should I change from CWM to TWRP and use ARHD do you think?

As for the fastboot getvar all, it's hanging on < waiting for device >

I'm using ViperOne 5.7.0

edit; fastboot getvar all worked earlier today just before I used firewater

edit2; DUH! Forgot to boot to Fastboot haha!!!

C:\Users\Michael>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.771.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXX
(bootloader) imei: XXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: H3G__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3873mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.048s

nkk71 · Apr 8, 2014

mrgreeny said:
Just done a nandroid backup, and when rebooting it said I needed to fix root?

For firewater to work, should I change from CWM to TWRP and use ARHD do you think?

As for the fastboot getvar all, it's hanging on < waiting for device >

I'm using ViperOne 5.7.0

edit; fastboot getvar all worked earlier today just before I used firewater

edit2; DUH! Forgot to boot to Fastboot haha!!!

(bootloader) version-main: 2.24.771.3

your best bet would be with a 2.24 ROM, try this one:
Android_Revolution_HD-One_13.4_(4.2.2).zip 1.01 GB
https://mega.co.nz/#!3VVEjKiJ!ekbbghB0fEx-aSRyppzjG3ITeuAT4xEoO9gXBo0vPpI
MD5: D8529CA3F59CDFA4947FD76333B2F5F8
credits to @mike1986.

then use rumrunner of firewater.

Good Luck

mrgreeny · Apr 8, 2014

nkk71 said:
(bootloader) version-main: 2.24.771.3

your best bet would be with a 2.24 ROM, try this one:
Android_Revolution_HD-One_13.4_(4.2.2).zip 1.01 GB
https://mega.co.nz/#!3VVEjKiJ!ekbbghB0fEx-aSRyppzjG3ITeuAT4xEoO9gXBo0vPpI
MD5: D8529CA3F59CDFA4947FD76333B2F5F8
credits to @mike1986.

then use rumrunner of firewater.

Good Luck

Can I flash this ROM with CWM?

Also, on reboot it says "Root access possibly lost. Fix? Yes - Fix Root (/system/xbin/su)

any ideas?

nkk71 · Apr 8, 2014

mrgreeny said:
Can I flash this ROM with CWM?

Also, on reboot it says "Root access possibly lost. Fix? Yes - Fix Root (/system/xbin/su)

any ideas?

yes you can flash that with CWM, and it's already rooted and has an unsecured kernel, so you should be good to go after flashing it.

mrgreeny · Apr 8, 2014

nkk71 said:
yes you can flash that with CWM, and it's already rooted and has an unsecured kernel, so you should be good to go after flashing it.

I will keep you up to date.. Thank you very much

mrgreeny · Apr 8, 2014

nkk71 said:
yes you can flash that with CWM, and it's already rooted and has an unsecured kernel, so you should be good to go after flashing it.

S-Off done - now I'm downloading all the files for when they're needed.

Which stock recovery (From http://d-h.st/users/Guich/Stock Recovery M7) should I use?

version-main in fastboot getvar all is version-main: 2.24.771.3 so should I download that from the above link?

mrgreeny · Apr 8, 2014

nkk71 said:
yes you can flash that with CWM, and it's already rooted and has an unsecured kernel, so you should be good to go after flashing it.

Okay. this is where I'm stuck at

C:\Users\Michael>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.050s]
finished. total time: 0.050s

C:\Users\Michael>fastboot flash zip ruu.zip
< waiting for device >
sending 'zip' (104391 KB)...
OKAY [ 5.840s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 6.033s

C:\Users\Michael>fastboot flash zip ruu.zip
sending 'zip' (104391 KB)...
OKAY [ 5.645s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 5.843s

C:\Users\Michael>fastboot flash zip ruu.zip
sending 'zip' (104391 KB)...
OKAY [ 5.882s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 6.077s

C:\Users\Michael>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.044s]
finished. total time: 0.044s

[SOLVED] Unroot Three UK HTC One

Senior Member

Inactive Recognized Developer / Contributor

Senior Member

Inactive Recognized Developer / Contributor

Senior Member

Senior Member

Inactive Recognized Developer / Contributor

Senior Member

Inactive Recognized Developer / Contributor

Senior Member

Inactive Recognized Developer / Contributor

Senior Member

Inactive Recognized Developer / Contributor

Senior Member

Inactive Recognized Developer / Contributor

Senior Member

Inactive Recognized Developer / Contributor

Senior Member

Senior Member

Senior Member

Similar threads

Top Liked Posts