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.
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.
Click to expand...
Click to collapse
There is no RUU for you, check my guide: http://forum.xda-developers.com/showthread.php?t=2541082
(read it a couple of times, and then let me know if something is not clear)
nkk71 said:
There is no RUU for you, check my guide: http://forum.xda-developers.com/showthread.php?t=2541082
(read it a couple of times, and then let me know if something is not clear)
Click to expand...
Click to collapse
So is your route not possible with Windows 8, then?
mrgreeny said:
So is your route not possible with Windows 8, then?
Click to expand...
Click to collapse
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.
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.
Click to expand...
Click to collapse
Ok, thank you!
nkk71 said:
There is no RUU for you, check my guide: http://forum.xda-developers.com/showthread.php?t=2541082
(read it a couple of times, and then let me know if something is not clear)
Click to expand...
Click to collapse
(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?
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?
Click to expand...
Click to collapse
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
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
Click to expand...
Click to collapse
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?
mrgreeny said:
Is there any risk of bricking the device?
Click to expand...
Click to collapse
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?
Click to expand...
Click to collapse
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 )
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.
Click to expand...
Click to collapse
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 )
Click to expand...
Click to collapse
Thank you very much. I shall do it later today or on Monday. Hopefully it will all go to plan!
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!
Click to expand...
Click to collapse
sure no problem,
remember: if something doesn't make sense to you, go ahead and ask.... no harm in asking
nkk71 said:
sure no problem,
remember: if something doesn't make sense to you, go ahead and ask.... no harm in asking
Click to expand...
Click to collapse
Can't get S-Off to work. Just posted in http://forum.xda-developers.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
[email protected]/# su
su
[email protected]/# chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]/# /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>
Click to expand...
Click to collapse
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.
mrgreeny said:
Can't get S-Off to work. Just posted in http://forum.xda-developers.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.
Click to expand...
Click to collapse
Not really, but can you post output of fastboot getvar all and which version of viperone you're using?
nkk71 said:
Not really, but can you post output of fastboot getvar all and which version of viperone you're using?
Click to expand...
Click to collapse
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
Click to expand...
Click to collapse
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!!!
Click to expand...
Click to collapse
(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
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
Click to expand...
Click to collapse
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?
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?
Click to expand...
Click to collapse
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.
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.
Click to expand...
Click to collapse
I will keep you up to date.. Thank you very much
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.
Click to expand...
Click to collapse
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?
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.
Click to expand...
Click to collapse
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
Click to expand...
Click to collapse
Related
I followed all the directions on relocking and unrooting my One back to factory settings and when I made it to the last step it keeps failing on me.
sending 'zip' (243622 KB)...
OKAY [ 9.533s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 33.051s
That's what it keeps saying to me. What should I do???
Kenmaster828 said:
I followed all the directions on relocking and unrooting my One back to factory settings and when I made it to the last step it keeps failing on me.
sending 'zip' (243622 KB)...
OKAY [ 9.533s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 33.051s
That's what it keeps saying to me. What should I do???
Click to expand...
Click to collapse
Why are you using a zip? Can't you use the exe RUU? Obviously has to be for your CID and MID. Check on androidruu.com if you can find one.
nkk71 said:
Why are you using a zip? Can't you use the exe RUU? Obviously has to be for your CID and MID. Check on androidruu.com if you can find one.
Click to expand...
Click to collapse
There was no .exe for my version.
I'm on the Sprint 1.31.651.2 version
Kenmaster828 said:
There was no .exe for my version.
I'm on the Sprint 1.31.651.2 version
Click to expand...
Click to collapse
to flash a RUU.zip you need to be in RUUmode (command: fastboot oem rebootRUU) and you'll need S-OFF.
herwegan said:
to flash a RUU.zip you need to be in RUUmode (command: fastboot oem rebootRUU) and you'll need S-OFF.
Click to expand...
Click to collapse
So I basically screwed myself when I reverted back to S-ON.
Kenmaster828 said:
So I basically screwed myself when I reverted back to S-ON.
Click to expand...
Click to collapse
Are you still on hboot 1.44? Then get S-Off again.
nkk71 said:
Are you still on hboot 1.44? Then get S-Off again.
Click to expand...
Click to collapse
I just got back on S-OFF. I am a happy camper
Kenmaster828 said:
I just got back on S-OFF. I am a happy camper
Click to expand...
Click to collapse
:laugh::good:
IMHO, keep S-Off no matter what, even if you have to return it for warranty (hopefully not) or even sell it. some phones are actually shipped with S-Off and (from what I've read) it's very difficult to say that you "tampered" with your phone because you have s-off. several people (on the posts) have returned their phones to service center for repair, and got them back s-off again. no complaints, unless it said RELOCKED, UNLOCKED, or TAMPERED in the bootloader. S-Off is OK.
now you can go ahead and get it back to stock.
nkk71 said:
:laugh::good:
IMHO, keep S-Off no matter what, even if you have to return it for warranty (hopefully not) or even sell it. some phones are actually shipped with S-Off and (from what I've read) it's very difficult to say that you "tampered" with your phone because you have s-off. several people (on the posts) have returned their phones to service center for repair, and got them back s-off again. no complaints, unless it said RELOCKED, UNLOCKED, or TAMPERED in the bootloader. S-Off is OK.
now you can go ahead and get it back to stock.
Click to expand...
Click to collapse
Last time I tried using Sprint 1.31.651.2, now that I am on S-OFF, can I use 1.29.651 version since that is a .exe version instead of a .zip version? I'm also asking this so I can strictly follow QBKING77's tutorial on going back to stock.
Kenmaster828 said:
Last time I tried using Sprint 1.31.651.2, now that I am on S-OFF, can I use 1.29.651 version since that is a .exe version instead of a .zip version? I'm also asking this so I can strictly follow QBKING77's tutorial on going back to stock.
Click to expand...
Click to collapse
Don't know "QBKING77's tutorial", but you can use pretty much any RUU now that you're S-Off. Downgrading is possible thanks to S-Off. Just stick to SPRINT RUUs, ROMs etc, as I understand they (and possibly Verizon) are different from other carriers.
And remember to keep S-Off, that will always allow you to downgrade if needed or flash firmware, etc.
How do you get S-Off after custom ROM
So I'm also getting the "12 signature verify fail" the OP was getting... I don't have (never have had) S-Off. I htcdev unlocked and rooted by AT&T HTC One and put the GPe ROM on it... now I'm trying to go back to stock. Can't run the RUU w/o S-Off apparently, but also apparently can't get S-Off with this ROM? Halp! How do I get out of this situation?
---------- Post added at 09:51 PM ---------- Previous post was at 09:10 PM ----------
I figured it'd be good to provide more info..
C:\and\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.15
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT34NW******
(bootloader) imei: *********************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4279mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status malformed (0 bytes))
finished. total time: 5.554s
I have tried the 502.12 and 502.15 "cingular" RUU (ZiIPs and EXEs), to no avail.
Can't revone (get "error code = 1" [not -1]), so I can't seem to get S-Off. Moonshine fails in test 2.1 (between reboots basically).
Any ideas?
Have you tried to install viper or ARHD and get S-off again?
michaeljthom said:
So I'm also getting the "12 signature verify fail" the OP was getting... I don't have (never have had) S-Off. I htcdev unlocked and rooted by AT&T HTC One and put the GPe ROM on it... now I'm trying to go back to stock. Can't run the RUU w/o S-Off apparently, but also apparently can't get S-Off with this ROM? Halp! How do I get out of this situation?
---------- Post added at 09:51 PM ---------- Previous post was at 09:10 PM ----------
I figured it'd be good to provide more info..
C:\and\platform-tools>fastboot getvar all
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-main: 1.26.502.15
(bootloader) version-misc: PVT SHIP S-ON
Any ideas?
Click to expand...
Click to collapse
Check the date in bootloader; if it's before June 2013, then revone should work. If the date is June or after then it's a patched hboot 1.44, and you need to downgrade before running revone, check this thread it has the downgrade instruction (T-Mob and ATT only): http://forum.xda-developers.com/showthread.php?t=2431515
and remember you need to be on a Sense 5, 4.1.2 based ROM.
nkk71 said:
and remember you need to be on a Sense 5, 4.1.2 based ROM.
Click to expand...
Click to collapse
So this is part of what I'm struggling with... It seems I can't get S-Off without being on a Sense 5/4.1.2 ROM, but how can I get that ROM loaded without S-Off? All the "stock" images I've found seem to all be RUUs or otherwise not work with S-On. What am I missing here?
michaeljthom said:
So this is part of what I'm struggling with... It seems I can't get S-Off without being on a Sense 5/4.1.2 ROM, but how can I get that ROM loaded without S-Off? All the "stock" images I've found seem to all be RUUs or otherwise not work with S-On. What am I missing here?
Click to expand...
Click to collapse
1- first thing, did you check the bootloader date? if it's the patched 1.44 (ie June 2013 or after) then if you do the downgrade (only for ATT and T-Mobile), I think that also includes the ROM.
2- and just to get a Sense 5/4.1.2 based ROM on your phone, you just flash it through custom recovery (any custom or stock ROM will do), if you can't find one I'll PM you a link to one that worked for me, but first check point 1
Thanks nkk71... So yeah, hboot, while v. 1.44, is dated Jul 5, 2013. So it looks like I need to downgrade that. But as you note, that link says I have to be on a stock Sense 5 ROM. I have found a TMO Germany rom, but I haven't yet found an AT&T one.
michaeljthom said:
Thanks nkk71... So yeah, hboot, while v. 1.44, is dated Jul 5, 2013. So it looks like I need to downgrade that. But as you note, that link says I have to be on a stock Sense 5 ROM. I have found a TMO Germany rom, but I haven't yet found an AT&T one.
Click to expand...
Click to collapse
I just took a quick look at the ATT downgrade guide and the first thing it asks (actually point 3) is to install a nandroid backup, that will put the correct Sense 5 ROM on your phone, no need to go look for one.
Hit the thanks button if I've helped
Score. Thanks so much. I think finding a nandroid backup (and then switching to cwm from twrp) was really the key here. But I'm now all fully restored to stock. Thanks again!!
Can someone link me to a thread or video on how to go to S-off, I don't have any rom installed and I can't go back in to recovery.
Hope I'm not screwed
LMH1998 said:
Can someone link me to a thread or video on how to go to S-off, I don't have any rom installed and I can't go back in to recovery.
Hope I'm not screwed
Click to expand...
Click to collapse
same problem . Please help!
I'm trying to get s-off but revone is keep failing with error code 1.
My One is a developer edition and hboot 1.44
Any idea? Thanks!
pirateye said:
I'm trying to get s-off but revone is keep failing with error code 1.
My One is a developer edition and hboot 1.44
Any idea? Thanks!
Click to expand...
Click to collapse
Had the same problem. You are probably on Android 4.3. and revone works on 4.2.2.
Here's what I did:
-Download any 4.2.2 rom (doesn't matter which one, just needs to be 4.2.2) You can download this: http://llabtoofer.com/2013/08/20/486/
-Make a nanadroid backup.(IMPORTANT if you don't want to lose anything)
-Wipe everything/ factory reset and flash the 4.2.2 rom
-Follow the steps for s-off with revone
-After you get s-off, go to recovery and restore from the nandroid backup
Now you will have s-off and all your data.
Ktan188 said:
Had the same problem. You are probably on Android 4.3. and revone works on 4.2.2.
Here's what I did:
-Download any 4.2.2 rom (doesn't matter which one, just needs to be 4.2.2) You can download this: http://llabtoofer.com/2013/08/20/486/
-Make a nanadroid backup.(IMPORTANT if you don't want to lose anything)
-Wipe everything/ factory reset and flash the 4.2.2 rom
-Follow the steps for s-off with revone
-After you get s-off, go to recovery and restore from the nandroid backup
Now you will have s-off and all your data.
Click to expand...
Click to collapse
It worked! Thanks a lot! :highfive:
Thanks for this I was having the same problem I'm downloading the 4.2.2 rom and doing the backup. I hope this works for me too
Ktan188 said:
Had the same problem. You are probably on Android 4.3. and revone works on 4.2.2.
Here's what I did:
-Download any 4.2.2 rom (doesn't matter which one, just needs to be 4.2.2) You can download this: http://llabtoofer.com/2013/08/20/486/
-Make a nanadroid backup.(IMPORTANT if you don't want to lose anything)
-Wipe everything/ factory reset and flash the 4.2.2 rom
-Follow the steps for s-off with revone
-After you get s-off, go to recovery and restore from the nandroid backup
Now you will have s-off and all your data.
Click to expand...
Click to collapse
Finally.. after hours of Googling an answer! Thanks so much.
Thanks a LOT!!!! I was really hating my device, didn't know what the problem is.
I will try it, finally found an answer...
Thanks...will try your method now.
Thanks!
Thank you very much for the help in this thread
i tried this one via a recovery.
but failed.. Even the Phone didn't boot and also cannot go back in recovery.
the phone is Bricked again flashed the ROM Sprint.
hBoot : 1.55.0000
OS: 3.05.651.5
[email protected] said:
i tried this one via a recovery.
but failed.. Even the Phone didn't boot and also cannot go back in recovery.
the phone is Bricked again flashed the ROM Sprint.
hBoot : 1.55.0000
OS: 3.05.651.5
Click to expand...
Click to collapse
1- be careful about the advice you get here, most of us are on M7_U / UL models not Sprint
2- revone only works on hboot 1.44
3- all s-off methods need a booted up rom!! not recovery!!!
4- use http://rumrunner.us/ or http://firewater-soff.com/ to get s-off on hboot 1.54+
5- if you're not sure what you're doing, do a little bit of research first (reading is preferred IMHO, over videos) until you are comfy with what you're doing.
the firewater also didnt work..
and nor Rumrunner
[email protected] said:
the firewater also didnt work..
and nor Rumrunner
Click to expand...
Click to collapse
Thanks for sharing as little information as possible.
1- do you know what s-on / s-off is? and what you can and cannot do with it? and whether you actually need it??
2- are you locked/unlocked (I'm talking about bootloader)
3- how about you start by posting a "fastboot getvar all" (excluding IMEI, MEID, and s/n)
4- what ROM you're running
5- a copy/paste of rumrunner and/or firewater output
nkk71 said:
Thanks for sharing as little information as possible.
1- do you know what s-on / s-off is? and what you can and cannot do with it? and whether you actually need it??
2- are you locked/unlocked (I'm talking about bootloader)
3- how about you start by posting a "fastboot getvar all" (excluding IMEI, MEID, and s/n)
4- what ROM you're running
5- a copy/paste of rumrunner and/or firewater output
Click to expand...
Click to collapse
-> yeah i know what the S-ON and S-OFF stands for.
-> yeah i need to flash a Raido.img so as to make Phone to work for SIM based for CDMA.
-> i tried flashing the radio, after rooting and unlocking, but Mr. Kapil Sir said that you have to first s-off, then u can flash radio.img
-> i am using 4.3.android. sw version : 3.05.651.5
-> firewater does nothing, where as rumrunner Pouring.... got for 8 times and asked to run after 30 seconds again for a luck to s-off.
==================== rumrunner S-OFF 0.5.0 ==============================
rumrunner 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 rumrunner 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.
Do you understand the implications of this warning?
(Yes/No)
Yes
Dear User: We will expect that YOU:
(1) Know how to use ADB and FASTBOOT binaries
---- [Yes, use these tools to test USB connection BEFORE running rumrunner] ----
(2) Realize that rumrunner S-OFF cannot support every CUSTOM rom in this world
(3) Understand that irc support IS NOT A GENERAL HELPDESK
(4) Are able to identify and download the CORRECT package for YOUR device
(5) Know how to enable USB-debugging on YOUR device (Yes, do that now)
(6) Understand that you may NOT repack or redistribute rumrunner S-OFF
Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
it's a little stinky here, hmm....
bottles are packed, here we go, shhhhhh....
hmm, cap is on tighter than I expected........
hell, that damn cap is on REALLY tight.......
pouring (1)..........................
pouring (2)...........................
pouring (3)..........................
pouring (4)...........................
pouring (5)..........................
pouring (6)...........................
pouring (7)..........................
pouring (8)...........................
Wait 30 seconds, power on device, pray, run rumrunner again.
Press ENTER to exit
executed the above exe for 3 times but same ans...
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 1.00.20.1108
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.05.651.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA35XXXXxxX164
(bootloader) imei: 9XXXXXXXXXXX499
(bootloader) meid: 99XXXXXXXXXX49
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4314mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-35824024
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.133s
[email protected] said:
-> yeah i know what the S-ON and S-OFF stands for. okay, fair enough
-> yeah i need to flash a Raido.img so as to make Phone to work for SIM based for CDMA. interesting
-> i tried flashing the radio, after rooting and unlocking, but Mr. Kapil Sir said that you have to first s-off, then u can flash radio.img I'm not familiar with Mr. Kapil Sir, or his radio flashing techniques... then again on the M7_U/UL you can flash radios without the need to be s-off, and I would assume the same for all M7 models
-> i am using 4.3.android. sw version : 3.05.651.5 not what i asked
-> firewater does nothing, where as rumrunner Pouring.... got for 8 times and asked to run after 30 seconds again for a luck to s-off. also not what i asked
Click to expand...
Click to collapse
okay, point taken Sir.
Sorry for not getting what u asked but tried my best to answer the Q's asked.
anyways Sorry again.
so what next..?
---------- Post added at 02:56 AM ---------- Previous post was at 02:50 AM ----------
Was trying to Flash a radio...
Please Check,
hope u might get the way out...
WHile S-ON
F:\Mobiles\Android\fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.039s]
finished. total time: 0.040s
F:\Mobiles\Android\fastboot>fastboot flash radio CT3G_radio.zip
target reported max download size of 1526722560 bytes
sending 'radio' (18824 KB)...
OKAY [ 2.381s]
writing 'radio'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 5.342s
while S-OFF got with firewater worked and helped to S-OFF
F:\Mobiles\Android\fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.055s]
finished. total time: 0.056s
F:\Mobiles\Android\fastboot>fastboot flash radio CT3G_radio.zip
target reported max download size of 1526722560 bytes
sending 'radio' (18824 KB)...
OKAY [ 2.381s]
writing 'radio'...
FAILED (remote: not allowed)
finished. total time: 2.427s
for sure it works after S-OFF .
but the minor mistake can led for failure and did a big mistake - a dump i m...
ok will correct.... hope u too have missed the correction..
but the think was
fastboot flash zip CT3G_radio.zip
where as i was writing
fastboot flash radio CT3G_radio.zip
so please dont sleep like me and do thinks..
sorry for diverting... but a good lesson for silly mistakes...
nkk71 said:
1- be careful about the advice you get here, most of us are on M7_U / UL models not Sprint
2- revone only works on hboot 1.44
3- all s-off methods need a booted up rom!! not recovery!!!
4- use http://rumrunner.us/ or http://firewater-soff.com/ to get s-off on hboot 1.54+
5- if you're not sure what you're doing, do a little bit of research first (reading is preferred IMHO, over videos) until you are comfy with what you're doing.
Click to expand...
Click to collapse
Hi
I am wondering if you can help me.
I am getting this error..revone failed (error code = -1) after runing ./revone -s 0 -u
(No 6 on http://forum.xda-developers.com/showthread.php?t=2314582)
***TAMPERED***
UNLOCKED
H-Boot 1.44
ROM 4.1.2
S-On
I am trying to get S-OFF so that I can remove the TAMPERED line.
I had success with ./revone -P and rebooted as per instructions.
However after reboot and running ./revone -s 0 -u
I get this
-------------------------------------
[email protected]:/data/local/tmp $ ./revone -s 0 -u
./revone -s 0 -u
revone v0.2.1
Gaining root access (thanks to Dan's motochopper)...Success.
revone failed (error code = -1)
255|[email protected]:/data/local/tmp $
______________________________________________
Any suggestions. Been trying to get to stock so I can return my device for the last 10 hours....so frustrating..
Thank you.
globalgpj said:
Hi
I am wondering if you can help me.
I am getting this error..revone failed (error code = -1) after runing ./revone -s 0 -u
(No 6 on http://forum.xda-developers.com/showthread.php?t=2314582)
***TAMPERED***
UNLOCKED
H-Boot 1.44
ROM 4.1.2
S-On
I am trying to get S-OFF so that I can remove the TAMPERED line.
I had success with ./revone -P and rebooted as per instructions.
However after reboot and running ./revone -s 0 -u
I get this
-------------------------------------
[email protected]:/data/local/tmp $ ./revone -s 0 -u
./revone -s 0 -u
revone v0.2.1
Gaining root access (thanks to Dan's motochopper)...Success.
revone failed (error code = -1)
255|[email protected]:/data/local/tmp $
______________________________________________
Any suggestions. Been trying to get to stock so I can return my device for the last 10 hours....so frustrating..
Thank you.
Click to expand...
Click to collapse
can you post a fastboot getvar all (excluding IMEI and s/n)
edit: and what ROM are you running
nkk71 said:
can you post a fastboot getvar all (excluding IMEI and s/n)
edit: and what ROM are you running
Click to expand...
Click to collapse
Hi Nkk71,
I got an even bigger problem now.
I was planning on returning my M7 to get the dreaded purple haze camera fixed. Got the GRA from the company already.
I tried to get the device to S-OFF after I got it S-On as the TAMPERED writing appeared again.
I tried revone and it always failed on line 6 ./revone -s 0 -u.
I went to try firewater and it said it couldn't do it and said to reboot.
As i rebooted into a stock rom, I went to Settings, got and error message and it asked if I wanted to send the error to HTC, I clicked no, then it went into a reboot and has been stuck on a WHITE boot screen (HTC One) and won't do anything.
I can't shut it down (tried holding down the power button 2 min+), I can boot into bootloader, I can't do anything either if I put my usb cable in either adb or fastboot, it is really FROZEN !!!!
Have I bricked my phone
I even tried to install the RUU but it failed as it needs to have a working USB connection.
It seems that all I can do is wait til the battery dies naturally.
Any advice ?
After 20 minutes still frozen boot screen. I can see the amber light on behind the speaker screen.
-------------------------------------------------------------------------
***TAMPERED***
UNLOCKED
S-ON
CID - HTC__001
H-Boot 1.44
ROM 4.1.2 (stock)
I'm running this stock ROM, RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed
and have TWRP installed.
globalgpj said:
Hi Nkk71,
I got an even bigger problem now.
Any advice ?
Click to expand...
Click to collapse
Firstly and most importantly: calm down, take it easy, chill out, and relax.... you are now panicking and starting to rush things!!
Once you've relaxed a bit:
Force reboot: press and hold POWER + VOLDOWN (under a bright light, not kidding!!), after about 5 seconds or so buttons should start blinking, and after 30 seconds or so, the phone will reboot, let go of POWER, but keep holding VOLDOWN to get back to bootloader.
(you may need to try 2 or 3 times to get it right)
and then let's see that "fastboot getvar all" (excluding IMEI and s/n)
nkk71 said:
Firstly and most importantly: calm down, take it easy, chill out, and relax.... you are now panicking and starting to rush things!!
Once you've relaxed a bit:
Force reboot: press and hold POWER + VOLDOWN (under a bright light, not kidding!!), after about 5 seconds or so buttons should start blinking, and after 30 seconds or so, the phone will reboot, let go of POWER, but keep holding VOLDOWN to get back to bootloader.
(you may need to try 2 or 3 times to get it right)
and then let's see that "fastboot getvar all" (excluding IMEI and s/n)
Click to expand...
Click to collapse
Thanks a million !!! It worked.. I heard that before, but forgot all about it. You don't hear much about that trick these days.
Yeah , no brick
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.13.3231.27
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.28.401.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4060mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.049s
-------------------
Should I try the Moonshine S-Off software to try and S-Off the device ?
http://forum.xda-developers.com/showthread.php?t=2291087
Hello. My firmware is 3.62.401.1, my hboot is 1.55 and im S-ON.
I wanna go to completely stock, but don't care about warranty. Since i have to go S-OFF with rumrunner to use RUU, and im afraid i might brick my device i flashed GURU'S REST ROM matching my firmware. Is this the same as using the RUU, or the RUU so to say, flashes it cleaner ?
Bocko92 said:
Hello. My firmware is 3.62.401.1, my hboot is 1.55 and im S-ON.
I wanna go to completely stock, but don't care about warranty. Since i have to go S-OFF with rumrunner to use RUU, and im afraid i might brick my device i flashed GURU'S REST ROM matching my firmware. Is this the same as using the RUU, or the RUU so to say, flashes it cleaner ?
Click to expand...
Click to collapse
can you post a "fastboot getvar all" (excluding IMEI and s/n)
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.21.3263.04
version-cpld: None
version-microp: None
version-main: 3.62.401.1
version-misc: PVT SHIP S-ON
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__102
battery-status: good
battery-voltage: 4001mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-bb768ae1
hbootpreupdate: 11
gencheckpt: 0
Bocko92 said:
Hello. My firmware is 3.62.401.1, my hboot is 1.55 and im S-ON.
I wanna go to completely stock, but don't care about warranty. Since i have to go S-OFF with rumrunner to use RUU, and im afraid i might brick my device i flashed GURU'S REST ROM matching my firmware. Is this the same as using the RUU, or the RUU so to say, flashes it cleaner ?
Click to expand...
Click to collapse
The Guru reset is not as complete as a true RUU but it is very close, close enough in fact you can take OTA after using it. and after the OTA your are indeed completely stock. The guru reset doesn't update your firmware so yeah it's important that you get the correct Reset to match your current firmware.
if this is the one you used you should be good to go
http://www.htc1guru.com/dld/guru_reset_m7_3-62-401-1-zip/
Bocko92 said:
version: 0.5
version-bootloader: 1.55.0000
version-main: 3.62.401.1
version-misc: PVT SHIP S-ON
product: m7_ul
modelid: PN0710000
cidnum: HTC__102
gencheckpt: 0
Click to expand...
Click to collapse
since you dont care about warranty, just go ahead and install http://www.htc1guru.com/dld/guru_reset_m7_3-62-401-1-zip/ using CWM or TWRP
if you want to receive & install OTA updates (when they become available), select "stock recovery" in installer.
nkk71 said:
since you dont care about warranty, just go ahead and install http://www.htc1guru.com/dld/guru_reset_m7_3-62-401-1-zip/ using CWM or TWRP
if you want to receive & install OTA updates (when they become available), select "stock recovery" in installer.
Click to expand...
Click to collapse
Thanks, i did install it, but i notice some lag when switching between normal notifications and toggles in the notification shade - is it normal ?
P.S I'm a new One user.
Wiped everything when installed the zip. Was just wondering if it cleans everything properly so the normal perfromance of the phone is achieved or i must play with the RUU.exe .. and S-OFF. I'd like to be completely stock since im sick of modding my phone .. and once i S-OFF i dont know how to S-ON.
Bocko92 said:
Thanks, i did install it, but i notice some lag when switching between normal notifications and toggles in the notification shade - is it normal ?
P.S I'm a new One user.
Wiped everything when installed the zip. Was just wondering if it cleans everything properly so the normal perfromance of the phone is achieved or i must play with the RUU.exe .. and S-OFF. I'd like to be completely stock since im sick of modding my phone .. and once i S-OFF i dont know how to S-ON.
Click to expand...
Click to collapse
1- if you ever decide to go S-Off then DO NOT GO BACK S-ON
2- you are now completely stock (your firmware is 3.62.401.1, and since you dont have s-off it's the official one), and the Guru Reset has put your ROM back to 100% stock -> so performance, etc. is 100% stock
3- you won't get it any different with an RUU (performance and experience)
4- you could try a factory reset, to clean everything and set up your phone from the beginning
Do you think it's worth it to go through the trouble of S-OFF-ing just to use the RUU, or the phone's just fine with the .zip. I'm kinda of perfectionist - i want to do it right and never bother again with flashing and modding?
Thanks again!
Bocko92 said:
Do you think it's worth it to go through the trouble of S-OFF-ing just to use the RUU, or the phone's just fine with the .zip. I'm kinda of perfectionist - i want to do it right and never bother again with flashing and modding?
Thanks again!
Click to expand...
Click to collapse
you're phone is 100% stock right now; the only advantages of going to S-Off and (eventually) run an RUU is if you need your bootloader to say "LOCKED" as opposed to UNLOCKED/RELOCKED.
It still says that my device's been tempered with, is that normal?
Bocko92 said:
It still says that my device's been tempered with, is that normal?
Click to expand...
Click to collapse
That's a so-so question, in theory it should go away once stock recovery has been installed, but in practice i've seen it sometimes go away and sometimes not, even when 100% stock.
Bocko92 said:
It still says that my device's been tempered with, is that normal?
Click to expand...
Click to collapse
nkk71 said:
That's a so-so question, in theory it should go away once stock recovery has been installed, but in practice i've seen it sometimes go away and sometimes not, even when 100% stock.
Click to expand...
Click to collapse
The Tampered and unlock/relock can be removed it you use nkk71 full Superguide for returning to stock >> http://forum.xda-developers.com/showthread.php?t=2541082
but it's a lot of work just to remove some red text on a screen you rarely ever see
If i want to use RUU do i have to first flash hboot 1.44 ? wont it break something with my firmware version?
Bocko92 said:
If i want to use RUU do i have to first flash hboot 1.44 ? wont it break something with my firmware version?
Click to expand...
Click to collapse
no it won't break anything in firmware, it will just downgrade hboot to allow RUU to work and "fastboot boot <name of recovery>.img" to work.
but if you're on Win8 / 8.1 that's gonna be an issue cause it will likely break fastboot & adb. better to use Win7 WinXP or even Ubuntu Live USB if you can't get your hands on Win7 or XP
EDIT: remember you have to be S-OFF !!!
I just s-offed ! Thanks again mate, i cant really thank you enough for your help!
Atm i just have windows 8.1, can i use it or i must install 7 somehwhere?
btw im on 8.1 atm and fastboot and adb works fine? or it's a issue with the 1.44 hboot?
Bocko92 said:
I just s-offed ! Thanks again mate, i cant really thank you enough for your help!
Atm i just have windows 8.1, can i use it or i must install 7 somehwhere?
btw im on 8.1 atm and fastboot and adb works fine? or it's a issue with the 1.44 hboot?
Click to expand...
Click to collapse
yeah, you're (very likely) going to have issues with win 8.1, better to get Win7 or an Ubuntu Live USB
do you have a win7 pc around somewhere handy? (cause it's not worth installing, better to "Try Ubuntu" Live USB)
Bocko92 said:
I just s-offed ! Thanks again mate, i cant really thank you enough for your help!
Atm i just have windows 8.1, can i use it or i must install 7 somehwhere?
btw im on 8.1 atm and fastboot and adb works fine? or it's a issue with the 1.44 hboot?
Click to expand...
Click to collapse
yes it the combination of win 8.1 and hboot 1.44.000 that will give you the problem
nkk71 said:
yeah, you're (very likely) going to have issues with win 8.1, better to get Win7 or an Ubuntu Live USB
do you have a win7 pc around somewhere handy? (cause it's not worth installing, better to "Try Ubuntu" Live USB)
Click to expand...
Click to collapse
Okay, im on windows 7, im S-OFF and my bootloader is unlocked but when i try to flash it it fails -
target reported max download size of 1526722560 bytes
sending 'zip' (501 KB)...
OKAY [ 0.250s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 0.733s
Bocko92 said:
Okay, im on windows 7, im S-OFF and my bootloader is unlocked but when i try to flash it it fails -
target reported max download size of 1526722560 bytes
sending 'zip' (501 KB)...
OKAY [ 0.250s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 0.733s
Click to expand...
Click to collapse
looks like android-info.txt is actually a little messed up in there
Code:
cidnum: HTC__E11cidnum: HTC__102
^^ line break missing.
, so just temporarily change CID to 11111111
fastboot oem writecid 11111111 <- 8 ones
then do the downgrade hboot, then restore cid
fastboot oem writecid HTC__102
and continue.
CANNOT THANK YOU ENOUGH KIND SIR ! I'm finally back to stock and locked. Really dude, you saved me there .. much love.
P.S No homo
After the struggle of finding a way to revert my Vodafone Australia branded HTC One back to it's former, virgin glory..
I have finally locked the bootloader, set my CID back and got a stock ROM and recovery - thanks to Guru Stock Reset ROMs, which is the closest thing I could get to being stock as there are no available RUU's.
But the last and final hurdle is S-ON. My Googling tells me all it takes is this fastboot command: "fastboot oem writesecureflag 3"
But when I throw that in a command prompt, all I get is an error:
(bootloader) partition hboot signature error
(bootloader) writesecureflag: partitions siganture failed
OKAY [ 1.624s]
finished. total time: 1.625s
Could anyone please help? I have to return my diseased pink/purple-tinted, crappy camera issue!
Jikstah said:
After the struggle of finding a way to revert my Vodafone Australia branded HTC One back to it's former, virgin glory..
I have finally locked the bootloader, set my CID back and got a stock ROM and recovery - thanks to Guru Stock Reset ROMs, which is the closest thing I could get to being stock as there are no available RUU's.
But the last and final hurdle is S-ON. My Googling tells me all it takes is this fastboot command: "fastboot oem writesecureflag 3"
But when I throw that in a command prompt, all I get is an error:
(bootloader) partition hboot signature error
(bootloader) writesecureflag: partitions siganture failed
OKAY [ 1.624s]
finished. total time: 1.625s
Could anyone please help? I have to return my diseased pink/purple-tinted, crappy camera issue!
Click to expand...
Click to collapse
wow, brick alert!
you have a modded hboot in there, so you're obviously not as stock as you'd like to think. better you rethink your strategy, and/or check my guide http://forum.xda-developers.com/showthread.php?t=2541082
nkk71 said:
wow, brick alert!
you have a modded hboot in there, so you're obviously not as stock as you'd like to think. better you rethink your strategy, and/or check my guide http://forum.xda-developers.com/showthread.php?t=2541082
Click to expand...
Click to collapse
Damn dude, how far am I from a brick? :S
and you are absolutely correct, I completely forgot about my hboot being modified at 1.55.
It's been awhile since I tampered around with my phone.
Is it then possible to downgrade my hboot to 1.44, with my current set-up? and continue to s-on?
I thank you immensely.
Jikstah said:
Damn dude, how far am I from a brick? :S
and you are absolutely correct, I completely forgot about my hboot being modified at 1.55.
It's been awhile since I tampered around with my phone.
Click to expand...
Click to collapse
Luckily the signature check kept you away from a brick, had you been able to S-On with a modded hboot, then you would have had a brick.
Jikstah said:
Is it then possible to downgrade my hboot to 1.44, with my current set-up? and continue to s-on?
Click to expand...
Click to collapse
I'm not sure what method you used to return to stock, but obviously hboot is not stock, and so could other things as well; I would recommend following my guide, especially if you intend on going S-On.
If you do want to follow my guide, post a "fastboot getvar all" (excluding IMEI and s/n), and I'll let you know which files you need.
nkk71 said:
I'm not sure what method you used to return to stock, but obviously hboot is not stock, and so could other things as well; I would recommend following my guide, especially if you intend on going S-On.
If you do want to follow my guide, post a "fastboot getvar all" (excluding IMEI and s/n), and I'll let you know which files you need.
Click to expand...
Click to collapse
I mean no offence in not wanting to follow your guide, it's great - especially for those less knowledgeable, and in need.
So here's my getvar:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: VODAP021
(bootloader) battery-status: good
(bootloader) battery-voltage: 3782mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.067s
Surely I'm close?! Thanks again.
Jikstah said:
I mean no offence in not wanting to follow your guide, it's great - especially for those less knowledgeable, and in need.
So here's my getvar:
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) modelid: PN0714000
(bootloader) cidnum: VODAP021
Surely I'm close?! Thanks again.
Click to expand...
Click to collapse
no offense taken
but you have PN0714000 + VODAP021 and firmware 3.62.401.1 (.401. = WWE unbranded), so you need to get your firmware correct too; inline with the ROM you are now on.
and personally, I don't recommend going S-Off to S-On on hboot 1.55, sometimes it works fine, but sometimes it triggers "tamper detected" and the tampered is back (can't say when/if it will happen to you)
nkk71 said:
no offense taken
but you have PN0714000 + VODAP021 and firmware 3.62.401.1 (.401. = WWE unbranded), so you need to get your firmware correct too; inline with the ROM you are now on.
and personally, I don't recommend going S-Off to S-On on hboot 1.55, sometimes it works fine, but sometimes it triggers "tamper detected" and the tampered is back (can't say when/if it will happen to you)
Click to expand...
Click to collapse
Ugh, more complications.. back to the drawing board it is!
So looks like all I need is firmware and hboot?
But do you reckon, the repair center will pay any attention to these attributes? I've heard all they check is S-ON, tamper flags and unlocked bootloaders?
Jikstah said:
Ugh, more complications.. back to the drawing board it is!
So looks like all I need is firmware and hboot?
But do you reckon, the repair center will pay any attention to these attributes? I've heard all they check is S-ON, tamper flags and unlocked bootloaders?
Click to expand...
Click to collapse
hboot will be part of the firmware.zip,
and I don't know what they will check, but you may have a problem when it comes back -> if you're S-On, LOCKED bootloader with firmware not matching your MID and CID, then chances are high that HTCDev won't unlock your phone.
nkk71 said:
hboot will be part of the firmware.zip,
and I don't know what they will check, but you may have a problem when it comes back -> if you're S-On, LOCKED bootloader with firmware not matching your MID and CID, then chances are high that HTCDev won't unlock your phone.
Click to expand...
Click to collapse
Okay, well that simplifies things..
Now I just have to find a firmware.zip
You're pretty well-versed, I must thank you again for your foresight.
Jikstah said:
Okay, well that simplifies things..
Now I just have to find a firmware.zip
You're pretty well-versed, I must thank you again for your foresight.
Click to expand...
Click to collapse
I'm assuming you used Guru ROM 2.24.980.2 ? i made a quick search but came up empty on the firmware for that. you could pull it from the OTA file if you find it; within the OTA.ZIP is another firmware.zip <- that's signed original firmware
nkk71 said:
I'm assuming you used Guru ROM 2.24.980.2 ? i made a quick search but came up empty on the firmware for that. you could pull it from the OTA file if you find it; within the OTA.ZIP is another firmware.zip <- that's signed original firmware
Click to expand...
Click to collapse
Rejoice! For I have found the exact firmware for the ROM - http://forum.xda-developers.com/showpost.php?p=44452049&postcount=438
Google is truly a wonderful thing, and you Mr. nkk71.
Jikstah said:
Rejoice! For I have found the exact firmware for the ROM - http://forum.xda-developers.com/showpost.php?p=44452049&postcount=438
Google is truly a wonderful thing, and you Mr. nkk71.
Click to expand...
Click to collapse
Nice find :good: :good:
don't forget to flash it twice:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
and since firmware & ROM are 2.xx (hboot 1.54), going from S-Off to S-On should be safe
nkk71 said:
Nice find :good: :good:
don't forget to flash it twice:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
and since firmware & ROM are 2.xx (hboot 1.54), going from S-Off to S-On should be safe
Click to expand...
Click to collapse
Oh jeez, here we go. I put the firmware.zip into my sd card, pulled up a cmd, entered rebootRUU mode, and tried to flash firmware zip.
And...
C:\adb>fastboot flash zip firmware.zip
target reported max download size of 1526722560 bytes
sending 'zip' (28294 KB)...
OKAY [ 2.210s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 2.701s
What's wrong with my CID? I even changed it from VODAP021 to HTC__039 to see if it would run, still the same error.. :|
EDIT: Okay so I SuperCID'ed, it worked however my bootloader is still 1.55? wut.
Don't tell me I need an unlocked bootloader, I need an unlocked bootloader right? -_-
I believe you said HTCdev won't unlock it if I had a non-matching firmware to my CID/MID? ugh.
EDIT: NOPE, no luck either with an unlocked bootloader - same result.
Jikstah said:
Oh jeez, here we go. I put the firmware.zip into my sd card, pulled up a cmd, entered rebootRUU mode, and tried to flash firmware zip.
And...
C:\adb>fastboot flash zip firmware.zip
target reported max download size of 1526722560 bytes
sending 'zip' (28294 KB)...
OKAY [ 2.210s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 2.701s
What's wrong with my CID? I even changed it from VODAP021 to HTC__039 to see if it would run, still the same error.. :|
EDIT: Okay so I SuperCID'ed, it worked however my bootloader is still 1.55? wut.
Don't tell me I need an unlocked bootloader, I need an unlocked bootloader right? -_-
I believe you said HTCdev won't unlock it if I had a non-matching firmware to my CID/MID? ugh.
EDIT: NOPE, no luck either with an unlocked bootloader - same result.
Click to expand...
Click to collapse
You do realize those errors/safe-guards are actually saving you!!
There's nothing wrong with your CID, so set it back to what it's supposed to be.
And the reason it's not working (actually it is), you are flashing the wrong firmware.zip, the one you are flashing is 28294 KB (probably a modded one), whereas the one you should be flashing (from the link you posted earlier) is 41197KB.
now put the correct firmware.zip in your adb/fastboot folder and flash it, fastboot doesn't use anything from your sdcard, it uses the files on your PC.
nkk71 said:
You do realize those errors/safe-guards are actually saving you!!
There's nothing wrong with your CID, so set it back to what it's supposed to be.
And the reason it's not working (actually it is), you are flashing the wrong firmware.zip, the one you are flashing is 28294 KB (probably a modded one), whereas the one you should be flashing (from the link you posted earlier) is 41197KB.
now put the correct firmware.zip in your adb/fastboot folder and flash it, fastboot doesn't use anything from your sdcard, it uses the files on your PC.
Click to expand...
Click to collapse
Gosh, you are too good. This is definitely the big break.
But nope, freakin' adb decides to bail on me and my device can no longer be detected. WTF?! What have I done to deserve such trouble.. -_-
Hello all.
The name is Daecca and first off, this was not my first phone to Costumize with Rom. or just ROOT for that matter.
But, it was the first HTC to root.
Now after doing everything by the proverbial book (Or sites) HTCdev and such.
And rooting with SuperSU (2. something as that was the newest version. I have a softbrick.
Meaning, the root removed my OS. I have tried all kinds of things found on this forum. posts from 2012 to 2015 I found here., But to no avail.
Here's the specs I can read in my Hboot.
***Tampered ***
*** Relocked ***
M7_UL PVT SHIP s-on RH
HBOOT-1.61.000
RADIO-4T.35.3218.16
OpenDSP-v35.120.274.0718
os-
eMMC-boot 2048MB
Nov 16 2015 20:23:35.129
below that are the usual options.
I have gotten multiple errors while trying to flash through the bootloaderRUU option.
C:\Android\fastboot>fastboot flash exe RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe
< waiting for device >
sending 'exe' (1014749 KB)...
OKAY [ 52.421s]
writing 'exe'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 135.899s
and
C:\Android\fastboot>fastboot flash exe RUU_M7_UL_L50_SENSE60_MR_BrightstarUS_WWE_7.17.1540.7_Radio_4T.35.3218.16_10.33Q.1718.01L_release_420191_signed_2.exe
sending 'exe' (1494393 KB)...
FAILED (remote: 02 data length is too large)
finished. total time: 0.268s
the later one was I'm guessing a wrong firmware as that was not Europe.
I am in the netherlands. So guessing europe should be it.
I have tried the Erase Cache thing aswell as the Restore thread (WHich is currently open on my computer as a separate tab)
Could anyone help me in the right Direction? I'm off to sports now and will check in a couple hours.
This is about my main phone so I am hoping for a swift solution. But I know I need patience for this.
Thanks in advance.
Daecca
PS: I know I could have responded in a different thread, But my loading time on PC is crazy atm due to all the stuff I have been looking for and downloading.
DaeccaD said:
Hello all.
The name is Daecca and first off, this was not my first phone to Costumize with Rom. or just ROOT for that matter.
But, it was the first HTC to root.
Now after doing everything by the proverbial book (Or sites) HTCdev and such.
And rooting with SuperSU (2. something as that was the newest version. I have a softbrick.
Meaning, the root removed my OS. I have tried all kinds of things found on this forum. posts from 2012 to 2015 I found here., But to no avail.
Here's the specs I can read in my Hboot.
***Tampered ***
*** Relocked ***
M7_UL PVT SHIP s-on RH
HBOOT-1.61.000
RADIO-4T.35.3218.16
OpenDSP-v35.120.274.0718
os-
eMMC-boot 2048MB
Nov 16 2015 20:23:35.129
below that are the usual options.
I have gotten multiple errors while trying to flash through the bootloaderRUU option.
C:\Android\fastboot>fastboot flash exe RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe
< waiting for device >
sending 'exe' (1014749 KB)...
OKAY [ 52.421s]
writing 'exe'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 135.899s
and
C:\Android\fastboot>fastboot flash exe RUU_M7_UL_L50_SENSE60_MR_BrightstarUS_WWE_7.17.1540.7_Radio_4T.35.3218.16_10.33Q.1718.01L_release_420191_signed_2.exe
sending 'exe' (1494393 KB)...
FAILED (remote: 02 data length is too large)
finished. total time: 0.268s
the later one was I'm guessing a wrong firmware as that was not Europe.
I am in the netherlands. So guessing europe should be it.
I have tried the Erase Cache thing aswell as the Restore thread (WHich is currently open on my computer as a separate tab)
Could anyone help me in the right Direction? I'm off to sports now and will check in a couple hours.
This is about my main phone so I am hoping for a swift solution. But I know I need patience for this.
Thanks in advance.
Daecca
PS: I know I could have responded in a different thread, But my loading time on PC is crazy atm due to all the stuff I have been looking for and downloading.
Click to expand...
Click to collapse
Are you using htc_fastboot?? Doesn't look like it!
DaeccaD said:
Hello all.
The name is Daecca and first off, this was not my first phone to Costumize with Rom. or just ROOT for that matter.
But, it was the first HTC to root.
Now after doing everything by the proverbial book (Or sites) HTCdev and such.
And rooting with SuperSU (2. something as that was the newest version. I have a softbrick.
Meaning, the root removed my OS. I have tried all kinds of things found on this forum. posts from 2012 to 2015 I found here., But to no avail.
Here's the specs I can read in my Hboot.
***Tampered ***
*** Relocked ***
M7_UL PVT SHIP s-on RH
HBOOT-1.61.000
RADIO-4T.35.3218.16
OpenDSP-v35.120.274.0718
os-
eMMC-boot 2048MB
Nov 16 2015 20:23:35.129
below that are the usual options.
I have gotten multiple errors while trying to flash through the bootloaderRUU option.
C:\Android\fastboot>fastboot flash exe RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe
< waiting for device >
sending 'exe' (1014749 KB)...
OKAY [ 52.421s]
writing 'exe'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 135.899s
and
C:\Android\fastboot>fastboot flash exe RUU_M7_UL_L50_SENSE60_MR_BrightstarUS_WWE_7.17.1540.7_Radio_4T.35.3218.16_10.33Q.1718.01L_release_420191_signed_2.exe
sending 'exe' (1494393 KB)...
FAILED (remote: 02 data length is too large)
finished. total time: 0.268s
the later one was I'm guessing a wrong firmware as that was not Europe.
I am in the netherlands. So guessing europe should be it.
I have tried the Erase Cache thing aswell as the Restore thread (WHich is currently open on my computer as a separate tab)
Could anyone help me in the right Direction? I'm off to sports now and will check in a couple hours.
This is about my main phone so I am hoping for a swift solution. But I know I need patience for this.
Thanks in advance.
Daecca
PS: I know I could have responded in a different thread, But my loading time on PC is crazy atm due to all the stuff I have been looking for and downloading.
Click to expand...
Click to collapse
First thing you should do is post your fastboot getvar all, but erase your IMEI and serial no from it. That way we will be able to determine the exact RUU for you. Second - and this is confusing, you flashed SU, and that erased your ROM? Impossible, you did something wrong, or you just ended up in a bootloop
Third - you don't flash a .exe file via fastboot. Exe is executable file which you execute via wizzard it comes with.
mb_guy said:
Are you using htc_fastboot?? Doesn't look like it!
Click to expand...
Click to collapse
Was not sure about that since I got two. one was htc and one was not, one didn't work.
donkeykong1 said:
First thing you should do is post your fastboot getvar all, but erase your IMEI and serial no from it. That way we will be able to determine the exact RUU for you. Second - and this is confusing, you flashed SU, and that erased your ROM? Impossible, you did something wrong, or you just ended up in a bootloop
Third - you don't flash a .exe file via fastboot. Exe is executable file which you execute via wizzard it comes with.
Click to expand...
Click to collapse
C:\Android\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 4292mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.647s
PS: I flashed superSU using CWM now, it could be the SU I used was not superSU and something that deleted my OS. as shown in the first post. there is no OS. (Atleast, it doesnt show in HBOOT)
and there was before I put up SU
PPS: I also tried several ZIP files. similar filenames. all with the same happening.
C:\Android\fastboot-htc\fastboot>fastboot flash zip OTA_M7_UL_JB_50_S_HTC_Europe_2.24.401.1-1.29.401.12_P2_release_324936_signedma8j1sa3e2o09s35.zip
sending 'zip' (426741 KB)...
OKAY [ 17.450s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 59.543s
Next try this time with the fastboot that was saved as HTC fastboot. still this. probably the wrong ROM?
PS: Also, thinking it indeed wasn't the superSU, I might have wiped the wrong thing (wanting to wipe cache and accidentally wiped the os.)
DaeccaD said:
C:\Android\fastboot-htc\fastboot>fastboot flash zip OTA_M7_UL_JB_50_S_HTC_Europe_2.24.401.1-1.29.401.12_P2_release_324936_signedma8j1sa3e2o09s35.zip
sending 'zip' (426741 KB)...
OKAY [ 17.450s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 59.543s
Next try this time with the fastboot that was saved as HTC fastboot. still this. probably the wrong ROM?
PS: Also, thinking it indeed wasn't the superSU, I might have wiped the wrong thing (wanting to wipe cache and accidentally wiped the os.)
Click to expand...
Click to collapse
Find 7.19.401.51 signed http://forum.xda-developers.com/showthread.php?t=3053944, and try to flash that, but be sure to use htc fastboot
donkeykong1 said:
Find 7.19.401.51 signed http://forum.xda-developers.com/showthread.php?t=3053944, and try to flash that, but be sure to use htc fastboot
Click to expand...
Click to collapse
Thank you DonkeyKong will try this as soon as possible. My computer just froze while trying the first time. now it won't see the usb in fastboot on phone. Gonna check out what happened with my drivers. Soon as I know more on it working or not I will let you know!
DaeccaD said:
Thank you DonkeyKong will try this as soon as possible. My computer just froze while trying the first time. now it won't see the usb in fastboot on phone. Gonna check out what happened with my drivers. Soon as I know more on it working or not I will let you know!
Click to expand...
Click to collapse
Good luck mate [emoji106] [emoji4]
donkeykong1 said:
Find 7.19.401.51 signed http://forum.xda-developers.com/showthread.php?t=3053944, and try to flash that, but be sure to use htc fastboot
Click to expand...
Click to collapse
Hey, am I doing something wrong here or?
C:\Android\fastboot-htc\fastboot>fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.zip
load_file: could not allocate 1688539299 bytes
error: cannot load 'PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.zip'
Thats what I got
And then I read instead of jumping in. It's doing what it needs to do now. (Just got the growing list)
DaeccaD said:
Hey, am I doing something wrong here or?
C:\Android\fastboot-htc\fastboot>fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.zip
load_file: could not allocate 1688539299 bytes
error: cannot load 'PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed.zip'
Thats what I got
And then I read instead of jumping in. It's doing what it needs to do now. (Just got the growing list)
Click to expand...
Click to collapse
Did you flash it in RUU mode?
fastboot oem rebootRUU
donkeykong1 said:
Did you flash it in RUU mode?
fastboot oem rebootRUU
Click to expand...
Click to collapse
Yes, doing it in that way. it worked out in the end. now the cmd prompt is ready. giving me the ability to type again, the phone shows the RUU HTC logo with a green bar which is now at about 90% filled up. Has been like that for about 15 minutes now. maybe 10.
Can I proceed with rebooting it into bootloader or should I wait? (Waiting could just get me an alnighter and not sure if the bar should fill up even if the CMD is done)
DaeccaD said:
Yes, doing it in that way. it worked out in the end. now the cmd prompt is ready. giving me the ability to type again, the phone shows the RUU HTC logo with a green bar which is now at about 90% filled up. Has been like that for about 15 minutes now. maybe 10.
Can I proceed with rebooting it into bootloader or should I wait? (Waiting could just get me an alnighter and not sure if the bar should fill up even if the CMD is done)
Click to expand...
Click to collapse
What exactly does cmd say at the bottom? If it' something alongst "finished..." you're good to go. Just type fastboot reboot, and enjoy
donkeykong1 said:
What exactly does cmd say at the bottom? If it' something alongst "finished..." you're good to go. Just type fastboot reboot, and enjoy
Click to expand...
Click to collapse
(bootloader) ...... Successful
OKAY
Flash Zip Complete
Execution time is 536(s)
And indeed, looked at that link of yours and gathered from that that indeed I should reboot it into bootloader.
Right now, my phone is working on upgrading 252 android apps.
Thank you very much!
Tomorrow I am going to try again with the superSU and CWMtouch. (Unless you think I should use another recovery which would be better) I want it rooted because the HTC thing comes with facebook installed. and some other things I don't want on my phone. Which is why I started this whole ordeal in the first place.
After that perhaps a good ROM for a newer android. But We'll see.
Again, thank you very much. I shall keep this forum under close watch and perhaps become a contrib myself eventually. Always wanted to deepen my knowledge on ROMs and such. perhaps this is the forum to guide me there. (After reading around a bit. I am guessing yes haha)
Cheers and thank you again, (Can't say that enough.)
DaeccaD said:
(bootloader) ...... Successful
OKAY
Flash Zip Complete
Execution time is 536(s)
And indeed, looked at that link of yours and gathered from that that indeed I should reboot it into bootloader.
Right now, my phone is working on upgrading 252 android apps.
Thank you very much!
Tomorrow I am going to try again with the superSU and CWMtouch. (Unless you think I should use another recovery which would be better) I want it rooted because the HTC thing comes with facebook installed. and some other things I don't want on my phone. Which is why I started this whole ordeal in the first place.
After that perhaps a good ROM for a newer android. But We'll see.
Again, thank you very much. I shall keep this forum under close watch and perhaps become a contrib myself eventually. Always wanted to deepen my knowledge on ROMs and such. perhaps this is the forum to guide me there. (After reading around a bit. I am guessing yes haha)
Cheers and thank you again, (Can't say that enough.)
Click to expand...
Click to collapse
TWRP recovery is the best for M7. CM stopped development a long time ago. Also, be sure to flash superSU 2.65, not lower. And when you flash recovery, make a backup of your current OS to be on the safe side
donkeykong1 said:
TWRP recovery is the best for M7. CM stopped development a long time ago. Also, be sure to flash superSU 2.65, not lower. And when you flash recovery, make a backup of your current OS to be on the safe side
Click to expand...
Click to collapse
All righty, will check that out tomorrow, thank you very much (again haha)
Cheers and good night
Daecca *Flails off, phone in hand shouting "It's alive, Ali i i ive":victory:
:victory: Problem Solved :victory:
DaeccaD said:
All righty, will check that out tomorrow, thank you very much (again haha)
Cheers and good night
Daecca *Flails off, phone in hand shouting "It's alive, Ali i i ive":victory:
:victory: Problem Solved :victory:
Click to expand...
Click to collapse
Great! Glad I could help! Enjoy your phone, and if you have any questions feel free to ask. You can shoot me a PM if you don't want to make a new thread [emoji6]
donkeykong1 said:
Great! Glad I could help! Enjoy your phone, and if you have any questions feel free to ask. You can shoot me a PM if you don't want to make a new thread [emoji6]
Click to expand...
Click to collapse
Will do, thank you very much, added you to contacts (And I think a friendrequest aswell. Ticked a box so guess so)
I am better with Samsung devices (Ace, S, S2, Note2 and Note 4), but getting to know HTC this intimately is amazing haha.
DaeccaD said:
Will do, thank you very much, added you to contacts (And I think a friendrequest aswell. Ticked a box so guess so)
I am better with Samsung devices (Ace, S, S2, Note2 and Note 4), but getting to know HTC this intimately is amazing haha.
Click to expand...
Click to collapse
You did send me a friendship request. I'll sort that out when I come home and get my hands on my laptop. I'm out now (having a beer) and I don't know how to accept things on tapatalk ?
EDIT: Sorted, request accepted [emoji4]