So my M7 started heating up, chewing battery. Everything was fine with the first L update, but after the second one, something went wrong.
Now, I don't really want to do a factory reset - if I don't have to. And to be honest, it never helped with these random battery/cpu hogs in Android.
So!
- Could anyone link me the latest KitKat RUU? OR whatever I have to flash/install?
- The warranty is now gone for the phone, so I also want to root. How should I root? Via HTCDev? Sunshine?
If I can install KitKat somehow without losing files, I would just Sunshine - would save me tons of work (restore).
Thanks!
Ps.: I am not lazy, and I really tried to find the answers - but compared to how easy to flash an LG or Samsung, HTC looks like a spacecraft.
Seriously, while the two other have simple firmware files, and a simple app to flash, HTC got RUU, different unlocks, different firmwares, etc.
* I also thought about switching it to GPE, but honestly, 5.1 is not any better.
And it's the last update for the M7... it's a dead end anyhow.
KitKat will serve this phone perfectly fine for +1-2 years.
h8Aramex said:
- Could anyone link me the latest KitKat RUU? OR whatever I have to flash/install?
Click to expand...
Click to collapse
Impossible to tell without knowing your phone info. Post the output of "fastboot getvar all" remove imei and sn before posting.
- The warranty is now gone for the phone, so I also want to root. How should I root? Via HTCDev? Sunshine?
Click to expand...
Click to collapse
If your goal is to return to kitkat then
1- return to kitkat, how exactly will be determined after you have posted your "fastboot getvar all"
2- root the phone (unlock the bootloader, flash a custom recovery, flash latest supersu.zip)
---------- Post added at 12:20 PM ---------- Previous post was at 12:18 PM ----------
If I can install Kitat somehow without losing files
Click to expand...
Click to collapse
RUU will wipe everything
Flashing a rom requires an unlocked bootloader, unlocking the bootloader wipes everything.
So you will lose your files, backup first.
Sorry for the noob question, command issued while in normal mode through ADB?
Or in fastboot through ADB?
alray said:
Impossible to tell without knowing your phone info. Post the output of "fastboot getvar all" remove imei and sn before posting.
If your goal is to return to kitkat then
1- return to kitkat, how exactly will be determined after you have posted your "fastboot getvar all"
2- root the phone (unlock the bootloader, flash a custom recovery, flash latest supersu.zip)
---------- Post added at 12:20 PM ---------- Previous post was at 12:18 PM ----------
RUU will wipe everything
Flashing a rom requires an unlocked bootloader, unlocking the bootloader wipes everything.
So you will lose your files, backup first.
Click to expand...
Click to collapse
h8Aramex said:
Or in fastboot through ADB?
Click to expand...
Click to collapse
fastboot commands are always/can only be issued when the phone is booted in bootloader mode with "fastboot usb" red caption showing.
adb commands are/can only be used when booted in the OS with usb debug turned on or from a custom recovery no matter if usb debug is turned on or off.
alray said:
fastboot commands are always/can only be issued when the phone is booted in bootloader mode with "fastboot usb" red caption showing.
adb commands are/can only be used when booted in the OS with usb debug turned on or from a custom recovery no matter if usb debug is turned on or off.
Click to expand...
Click to collapse
Sorry for the delay.
(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: 7.19.401.22
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: --------------
(bootloader) imei: 1111111111111111
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4068mV
(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.073s
Click to expand...
Click to collapse
I want the latest 4.4 FW/ROM, preferably stock.
(But if that Revolution rom works fine, I am also fine with that one.)
--------------------------------
UPDATE:
Ok, so I thought I will try things by myself... it cannot be that hard.
I was wrong.
I am now more confused than ever.
h8Aramex said:
Sorry for the delay.
I want the latest 4.4 FW/ROM, preferably stock.
(But if that Revolution rom works fine, I am also fine with that one.)
--------------------------------
UPDATE:
Ok, so I thought I will try things by myself... it cannot be that hard.
I was wrong.
I am now more confused than ever.
Click to expand...
Click to collapse
Since that your phone is s-on you can not use a RUU to downgrade, you will have to unlock your bootloader, flash a custom recovery and finally flash a 4.4 rom. You'll will not be able to downgrade the firmware with S-ON, you can only change your rom.
to unlock the bootloader go at www.htcdev.com/bootloader and follow the instructions
once done flash a custom recovery, preferably TWRP 2.8.6.0:
Code:
fastboot flash recovery twrp-2.8.6.0-m7.img
fastboot erase cache
fastboot reboot-bootloader
boot in recovery and transfer the rom zip file you want to flash to your phone storage.
in twrp select "install" and flash your rom.
alray said:
////
Click to expand...
Click to collapse
Could you link me a 4.4 ROM, please?
Preferably Stock, HTC Sense one.
I checked the pinned thread, but every file is 404 (missing) by now, since it's a very old thread/post.
Thank you!
h8Aramex said:
Could you link me a 4.4 ROM, please?
Preferably Stock, HTC Sense one.
I checked the pinned thread, but every file is 404 (missing) by now, since it's a very old thread/post.
Thank you!
Click to expand...
Click to collapse
Stock 4.4.2 rom, latest version before lollipop (6.09.401.12)
https://www.androidfilehost.com/?fid=95916177934521261
Thank you!
I have managed to unlock + root (that wasn't really so hard, using Sunshine would have been harder). Will try to stay on L now, see if the reset helped with the battery drain. If not, it's time for Kitkat!
Related
Hi all,
My girlfriend has a HTC One M7, currentley Rooted with an Unlocked bootloader, Bulletproof Kernel, CWM Recovery, S-On (can't get S-OFF no matter what I try) and running the stock 4.4.2 Sense ROM that came with the phone.
She wants to install an OTA update, obviously this won't work with the phone in it's current state. I've got experience with all of this with my Note II, but the M7 is just a whole different can of worms.
What I've tried:
Getting S-OFF (no luck whatsoever with any tools)
Flashing stock recovery and kernel
Flashing stock recovery and kernel and applying the OTA manually via recovery
I've read everything on here and nothing seems to go in. She just wants to be able to install OTA updates, even if it means unrooting her phone permanently as this will happen each time there is an OTA update.
Someone, please guide me in the right direction! Step by step maybe?
Keep in mind there is no way I can't get S-OFF.
Huge thanks to anyone that can help. I'd be eternally in your debt!!
SmokinWaffle said:
My girlfriend has a HTC One M7, currentley Rooted with an Unlocked bootloader, Bulletproof Kernel, CWM Recovery, S-On (can't get S-OFF no matter what I try) and running the stock 4.4.2 Sense ROM that came with the phone.
She wants to install an OTA update, obviously this won't work with the phone in it's current state. I've got experience with all of this with my Note II, but the M7 is just a whole different can of worms.
Click to expand...
Click to collapse
I suppose the phone is trying to apply to ota update and then show a red triangle with an exclamation mark inside?
What I've tried:
Getting S-OFF (no luck whatsoever with any tools) Any error message when trying to S-OFF? You must use the correct tool for your hboot version (probably firewater) + combination of the correct rom + kernel
Flashing stock recovery and kernel --> You must have stock recovery for ota, ota will not install using a custom one.
Flashing stock recovery and kernel and applying the OTA manually via recovery --> appyling the ota manually from stock recovery require s-off
Click to expand...
Click to collapse
I've read everything on here and nothing seems to go in. She just wants to be able to install OTA updates, even if it means unrooting her phone permanently as this will happen each time there is an OTA update
Click to expand...
Click to collapse
.
http://forum.xda-developers.com/showpost.php?p=52894276&postcount=9
http://forum.xda-developers.com/showpost.php?p=53151895&postcount=23
Keep in mind there is no way I can't get S-OFF.
Click to expand...
Click to collapse
still not sure about this, unless you get the "whelp" message from firewater...
post the output of fastboot getvar all except the imei number and serialno
alray said:
I suppose the phone is trying to apply to ota update and then show a red triangle with an exclamation mark inside?
Click to expand...
Click to collapse
Yep!
alray said:
http://forum.xda-developers.com/showpost.php?p=52894276&postcount=9
http://forum.xda-developers.com/showpost.php?p=53151895&postcount=23
Click to expand...
Click to collapse
Interesting. I don't have the phone with me at the moment and it's late but I'll try to do the POWERUP + VOL tomorrow at some point, I'll get her to try stock recovery + kernel then do it and see what it's stopping at.
alray said:
still not sure about this, unless you get the "whelp" message from firewater...
Click to expand...
Click to collapse
Didn't get that message, just keeps going indefinetley or stops, and doesn't S-OFF. Tried Firewater, Revone, RumRunner, if there is another then I've almost certainly tried it, followed all the guides including the one that flashed Android Revolution...no idea..
alray said:
post the output of fastboot getvar all except the imei number and serialno
Click to expand...
Click to collapse
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.25.3263.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: [I]XXXXXXXXXXXX[/I]
(bootloader) imei: [I]XXXXXXXXXXXXXXX[/I]
(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: 3798mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
Thanks for the prompt reply, really appreciate it and any help you can give.
SmokinWaffle said:
Yep!
Interesting. I don't have the phone with me at the moment and it's late but I'll try to do the POWERUP + VOL tomorrow at some point, I'll get her to try stock recovery + kernel then do it and see what it's stopping at.
Didn't get that message, just keeps going indefinetley or stops, and doesn't S-OFF. Tried Firewater, Revone, RumRunner, if there is another then I've almost certainly tried it, followed all the guides including the one that flashed Android Revolution...no idea..
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.25.3263.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: [I]XXXXXXXXXXXX[/I]
(bootloader) imei: [I]XXXXXXXXXXXXXXX[/I]
(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: 3798mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
Thanks for the prompt reply, really appreciate it and any help you can give.
Click to expand...
Click to collapse
your version-main? (rom version) Go in settings --> About --> Software info --> Rom version
maybe there is a ruu you could use to restore the phone(4.19.401.9), if it match your version
---------- Post added at 04:40 PM ---------- Previous post was at 04:35 PM ----------
you can also flash the stock 5.11.401.10 rom, recovery and firmware available on ARHD website
http://android-revolution-hd.blogspot.ca/p/android-revolution-hd-mirror-site-var.html
http://forum.xda-developers.com/showthread.php?t=2224752
alray said:
your version-main? (rom version) Go in settings --> About --> Software info --> Rom version
maybe there is a ruu you could use to restore the phone(4.19.401.9), if it match your version
---------- Post added at 04:40 PM ---------- Previous post was at 04:35 PM ----------
you can also flash the stock 5.11.401.10 rom, recovery and firmware available on ARHD website
http://android-revolution-hd.blogspot.ca/p/android-revolution-hd-mirror-site-var.html
http://forum.xda-developers.com/showthread.php?t=2224752
Click to expand...
Click to collapse
4.19.401.11
What exactly is the function of the RUU? I can't seems to get my head around it..
I'm guessing the ARHD steps are to try to get S-OFF?
SmokinWaffle said:
4.19.401.11
What exactly is the function of the RUU? I can't seems to get my head around it..
Click to expand...
Click to collapse
forget the ruu, your phone version is higher than the ruu. flashing a ruu (4.11.401.10) with a lower version than on your phone(4.11.401.11) require s-off.
I'm guessing the ARHD steps are to try to get S-OFF?
Click to expand...
Click to collapse
No, this is the latest stock rom(5.11.401.10) for your phone model (MID: PN0710000 and CID:HTC__001) including android 4.4.2 and sense 6.0
You can flash this stock odexed rom(5.11.401.10) from custom recovery, then flash the stock recovery(5.11.401.10) over the custom one and your phone will be stock and ready to take future ota update. You may also want to update firmware to 5.11.401.10
So after flashing that rom and stock recovery, ota would be ready to roll? Would the kernel matter?
What's the purpose / Difference of firmware and how is it updated? On my note II it was just choose a rom choose a kernel and off you go. This is so much more involved
SmokinWaffle said:
So after flashing that rom and stock recovery, ota would be ready to roll? Would the kernel matter?
Click to expand...
Click to collapse
stock kernel in included in the rom (boot.img) so if you don't flash any other kernel it should be fine.
What's the purpose / Difference of firmware and how is it updated? On my note II it was just choose a rom choose a kernel and off you go. This is so much more involved
Click to expand...
Click to collapse
firmware is all the low level code required for your phone hardware to works with the software (OS)
when speaking about HTC phone, firmware.zip include HBOOT(bootloader), BOOT(kernel), Recovery, Radio and some other stuff. if you want your phone to be 100% stock you need both stock rom + stock firmware to match the same version i.e 5.11.501.10
normally, the firmware is updated at the same time the rom version is updated (from an ota update) If you flash a rom, the rom will be updated but not the firmware.
Updating the firmware manually can be dangerous is you don't know what you are doing and flashing the wrong file. You can update firmware using this command from bootloader (with the correct firmware.zip package in the same folder you have adb and fastboot):
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
also it looks like flashing a 5.x.xxx.x firmware over a 3.x.xxx.x firmware will brick your phone. from what i see, your phone should be on a 4.x.401.x version at the moment, so it theory it should be fine.
Fails on:
>>>setting permissions
set_metadata_recursive: some changes failed
E:Error in /data/media/0/one_5.11.401.10_odexed.zip
(status 7)
Tried 3 different versions of cwm. Bad rom download?
Thinking about it I just re read your above post, could it be because the firmware isn't matched? I read your 'it should be fine' as 'dont update the firmware' not 'its fine to update' which I think is what you meant...
Firmware is 4.19.401.11 however the rom is 5.11.401.10. Can't believe I overlooked this, guess firmware needs to be 5.11.401.10 for the rom to take?
SmokinWaffle said:
Tried 3 different versions of cwm. Bad rom download?
Click to expand...
Click to collapse
No you are using CWM thats the problem. always use TWRP 2.6.3.3
alray said:
No you are using CWM thats the problem. always use TWRP 2.6.3.3
Click to expand...
Click to collapse
Huh?
Is this a requirement of ARHD or....?
Just seems odd
Edit: success!! All seems to work. Thank you. She's overjoyed!!!
Hi.
I've been trying to follow instructions from several threads about restoring an M7 to un-rooted, relocked, stock O2 ROM.
Things have gone badly from the start and I've tried so many different people's posts about what I should do that I'm completely confused now and need some help getting back on track.
At the moment all I've got is a hboot screen with fastboot working (unable to boot into recovery)
The last thing I did before this all went bed was to use 'fastboot oem relock' (which worked) I've tried 'fastboot oem unlock' but that says '[ERR] Command error !!!'.
I've tried flashing a stock rom.zip extracted from an O2 RUU but it fails with the code 'FAILED (remote: 22 loading zip info fail Please check if you flash part)'.
This is the 'getvar all' result.
C:\flashing\mini-sdk>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(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: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4229mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Any help appreciated.
Thanks.
thintin said:
Hi.
I've been trying to follow instructions from several threads about restoring an M7 to un-rooted, relocked, stock O2 ROM.
Things have gone badly from the start and I've tried so many different people's posts about what I should do that I'm completely confused now and need some help getting back on track.
At the moment all I've got is a hboot screen with fastboot working (unable to boot into recovery)
The last thing I did before this all went bed was to use 'fastboot oem relock' (which worked) I've tried 'fastboot oem unlock' but that says '[ERR] Command error !!!'.
I've tried flashing a stock rom.zip extracted from an O2 RUU but it fails with the code 'FAILED (remote: 22 loading zip info fail Please check if you flash part)'.
This is the 'getvar all' result.
C:\flashing\mini-sdk>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(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: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4229mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Any help appreciated.
Thanks.
Click to expand...
Click to collapse
remove your imei and serial number from your output above, its dangerous to post them.
according to your hboot which is 1.57 you wont beable to use that ruu, you cant back flash unless you have s-off.
also, only way to unlock your bootloader is at HTC dev again, you cant use a command to do it, so start there.
Seanie280672 said:
remove your imei and serial number from your output above, its dangerous to post them.
according to your hboot which is 1.57 you wont beable to use that ruu, you cant back flash unless you have s-off.
also, only way to unlock your bootloader is at HTC dev again, you cant use a command to do it, so start there.
Click to expand...
Click to collapse
Thanks for the tip (oops) So is that the first step I need to do, unlock the bootloader again? Just checking before I go ahead. Thanks.
Update...
I went to the HTCDev site to unlock again (I know I'm impatient but I'm running out of time to get this done) but it didn't work. This is what the site reported back:-
We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.
Error Code: Invalid Bootloader Token Length.
Error Reason: The submitted Token appears to be the wrong length and won't work.
Click to expand...
Click to collapse
I tried again and made sure the entire code was included as well as the start and finish tags but still it failed.
Help .... :-l
thintin said:
Thanks for the tip (oops) So is that the first step I need to do, unlock the bootloader again? Just checking before I go ahead. Thanks.
Click to expand...
Click to collapse
yes that's the first step, then you need to decide if you want to go s-off and flash that original rom of yours, or go unbranded, or just flash a custom recovery and a custom rom.
---------- Post added at 07:15 PM ---------- Previous post was at 06:59 PM ----------
in fact, thinking about it, you will have to go with custom rom and recovery as you need a rom on your phone to go s-off.
---------- Post added at 07:17 PM ---------- Previous post was at 07:15 PM ----------
thintin said:
Thanks for the tip (oops) So is that the first step I need to do, unlock the bootloader again? Just checking before I go ahead. Thanks.
Update...
I went to the HTCDev site to unlock again (I know I'm impatient but I'm running out of time to get this done) but it didn't work. This is what the site reported back:-
I tried again and made sure the entire code was included as well as the start and finish tags but still it failed.
Help .... :-l
Click to expand...
Click to collapse
strange, that's the only way your going to be able to unlock your bootloader, and unfortunately, there's nothing you can do with a relocked bootloader, can you post your token here so I can look over it.
Seanie280672 said:
yes that's the first step, then you need to decide if you want to go s-off and flash that original rom of yours, or go unbranded, or just flash a custom recovery and a custom rom.
---------- Post added at 07:15 PM ---------- Previous post was at 06:59 PM ----------
in fact, thinking about it, you will have to go with custom rom and recovery as you need a rom on your phone to go s-off.
---------- Post added at 07:17 PM ---------- Previous post was at 07:15 PM ----------
strange, that's the only way your going to be able to unlock your bootloader, and unfortunately, there's nothing you can do with a relocked bootloader, can you post your token here so I can look over it.
Click to expand...
Click to collapse
Sure, I appreciate your help with this
<<<< Identifier Token Start >>>>
5A5F19A2F517CC2BEA0DDADB1C3924C7
FA7846F59B3E38FC5897B053899BA233
824B607DDBDD9CE31E453E48CBE4EF5C
8ECD29487C09FE311D30DA91386C56C5
FF130E636BA23977B05905925EB17FC6
3EBBCC1BFCB2383B1A7DAFDCBFBE0AA7
8DA65BF8F702E6F44F24743AFA8573EB
AE8D23E995EED6E7CBC5981CEBBAFC66
694176C863DB9858CC535ED2D3EC609C
043196ED2CDF60AC13DEBBB636AA348E
E748366B4CA16747C0593C363D6B98E2
81C2699B2D1D979E7ACAC97D4187788E
85AEA5F27B48A9F8278A0B49D0D3838B
92E2EDFE6B16EEEDE98F322D92294ED0
E43D1945184BBF8A0CB9661B92CB9E38
040AAF8857A0FC1A4C7682ACF8120340
<<<<< Identifier Token End >>>>>
Click to expand...
Click to collapse
I'm s-on BTW in case that makes a difference; never been s-off.
thintin said:
Sure, I appreciate your help with this
I'm s-on BTW in case that makes a difference; never been s-off.
Click to expand...
Click to collapse
that's very strange, just tried mine and it worked, tried yours and I got the same messages as you, but they are the same length etc.
Is this how you unlocked your bootloader before ? do you still have your original token anywhere ?
Seanie280672 said:
that's very strange, just tried mine and it worked, tried yours and I got the same messages as you, but they are the same length etc.
Is this how you unlocked your bootloader before ? do you still have your original token anywhere ?
Click to expand...
Click to collapse
This is how I unlocked it originally. I don't have the token but I do have the email they send afterwards with the bin file attached. Shall I try and use that again?
thintin said:
This is how I unlocked it originally. I don't have the token but I do have the email they send afterwards with the bin file attached. Shall I try and use that again?
Click to expand...
Click to collapse
yes defiantly, download the attachment and click the link on the email to continue the instructions.
Seanie280672 said:
yes defiantly, download the attachment and click the link on the email to continue the instructions.
Click to expand...
Click to collapse
Okay, that worked! (Phew). I now have an unlocked bootloader again.
So to get from my custom ROM, custom recovery and 'unlocked/tampered' state back to a stock rom/recovery and locked bootloader......what order do I have to do things? I know this is a big ask but I don't want to end up in a muddle again! Thanks.
thintin said:
Okay, that worked! (Phew). I now have an unlocked bootloader again.
So to get from my custom ROM, custom recovery and 'unlocked/tampered' state back to a stock rom/recovery and locked bootloader......what order do I have to do things? I know this is a big ask but I don't want to end up in a muddle again! Thanks.
Click to expand...
Click to collapse
if you have a working rom on there now then you will have to get s-off to do everything you want to do.
Try firewater first: http://firewater-soff.com/instructions/
if that fails then you will have to use sunshine, but you do have to pay for that: http://theroot.ninja/
out of interest, which rom are you running at the moment ?
Seanie280672 said:
if you have a working rom on there now then you will have to get s-off to do everything you want to do.
Try firewater first: http://firewater-soff.com/instructions/
if that fails then you will have to use sunshine, but you do have to pay for that: http://theroot.ninja/
out of interest, which rom are you running at the moment ?
Click to expand...
Click to collapse
I'm just trying the firewater method ATM. The ROM currently on the device is Revolution HD One 71.1
thintin said:
I'm just trying the firewater method ATM. The ROM currently on the device is Revolution HD One 71.1
Click to expand...
Click to collapse
ok good, also could you post a link to the O2 RUU you downloaded earlier
Seanie280672 said:
ok good, also could you post a link to the O2 RUU you downloaded earlier
Click to expand...
Click to collapse
GRRR!
Following firewater instructions...
adb reboot <–important!!!!
Click to expand...
Click to collapse
this caused loads of text to scroll down the cmd window but the device didn't reboot - not sure if it was supposed to?
adb wait-for-device push firewater /data/local/tmp
Click to expand...
Click to collapse
did this - cmd said that daemon was not running and started it but then nothing...no command prompt, phone doing nothing...eventually I closed the window. Now ADB wont recongnise the phone!
???
The stock O2 RUU was from HTC1guru.com (I think) I had to dig around quite a lot to find it. If I find the address I'll post it here.
thintin said:
GRRR!
Following firewater instructions...
this caused loads of text to scroll down the cmd window but the device didn't reboot - not sure if it was supposed to?
did this - cmd said that daemon was not running and started it but then nothing...no command prompt, phone doing nothing...eventually I closed the window. Now ADB wont recongnise the phone!
???
The stock O2 RUU was from HTC1guru.com (I think) I had to dig around quite a lot to find it. If I find the address I'll post it here.
Click to expand...
Click to collapse
try this version of adb and fastboot instead, sounds like its out of date and also check your device manager, make sure it says MyHTC when your phone is plugged in: http://forum.xda-developers.com/showthread.php?t=2588979
thintin said:
GRRR!
Following firewater instructions...
this caused loads of text to scroll down the cmd window but the device didn't reboot - not sure if it was supposed to?
Click to expand...
Click to collapse
It looks like you typed adb reboot <–important!!!! the <-important!!! should not have been typed. It is just a comment. You will notice on the firewater page it is bold where the rest of the type is not.
majmoz said:
It looks like you typed adb reboot <–important!!!! the <-important!!! should not have been typed. It is just a comment. You will notice on the firewater page it is bold where the rest of the type is not.
Click to expand...
Click to collapse
Don't worry, I didn't type the important! bit
I'm not sure how much more time I want to spend trying to reset this device, maybe I'll just return it to O2 as it is and see if they even care that it's been unlocked!
I'll try the link you suggested and report back :tired:
Hi.
I think my guardian angel must have had a hand in this because I was only trying to reset the phone to return it due to the microphone not working. After all of these failed attempts I factory reset the current rom and bingo! Microphone working again and no need to return to O2
But thanks for all of the help you offered, I would have a lot less hair and more wrinkles without you.
My htc one At&t turned Developer edition was working perfect. No root , No custom rot or whatsoever. I was running latest update 4.4 with Sense 6. It just rebooted and then it just got stuck at the HTC one logo screen. Wont just pass that.
I hard reset with power + down. It rebooted. But then again stuck at the HTC logo screen.
I went to fastboot and tried going to recovery . It just reboots and then comes with a Red Triangle exclamation mark. I was hoping to go in recover and the clean the cache might fix the stuck on boot screen issue. It seems i am not able to go in recovery also. I don't know why.
I tried selecting the factory reset , it took its time. Then it shut down. I again booted it , again stuck at HTC logo screen. It wont load the android. It takes charging fine.
Any idea why going to recovery shows the red exclamation mark ? i have not played with the recovery.. have been getting the HTC update as normal.
Also any way i can boot it now ?? its just stuck at the boot screen.
Was my primary phone.
Thanks,
anirudhgargi said:
My htc one At&t turned Developer edition was working perfect. No root , No custom rot or whatsoever. I was running latest update 4.4 with Sense 6. It just rebooted and then it just got stuck at the HTC one logo screen. Wont just pass that.
I hard reset with power + down. It rebooted. But then again stuck at the HTC logo screen.
I went to fastboot and tried going to recovery . It just reboots and then comes with a Red Triangle exclamation mark. I was hoping to go in recover and the clean the cache might fix the stuck on boot screen issue. It seems i am not able to go in recovery also. I don't know why.
I tried selecting the factory reset , it took its time. Then it shut down. I again booted it , again stuck at HTC logo screen. It wont load the android. It takes charging fine.
Any idea why going to recovery shows the red exclamation mark ? i have not played with the recovery.. have been getting the HTC update as normal.
Also any way i can boot it now ?? its just stuck at the boot screen.
Was my primary phone.
Thanks,
Click to expand...
Click to collapse
the red exclamation mark is normal, the stock recovery is working fine. When you access the recovery and get to this point, hold volume up button and press power to access recovery options. You can factory reset from here and clear cache
stovie_steve said:
the red exclamation mark is normal, the stock recovery is working fine. When you access the recovery and get to this point, hold volume up button and press power to access recovery options. You can factory reset from here and clear cache
Click to expand...
Click to collapse
Great ! Many thanks.
I got to the Recovery menu. I cleared the cache and the selected the factory/reset. And rebooted the device.
But Its till stuck at the boot screen
anirudhgargi said:
Great ! Many thanks.
I got to the Recovery menu. I cleared the cache and the selected the factory/reset. And rebooted the device.
But Its till stuck at the boot screen
Click to expand...
Click to collapse
Can you post a fastboot getvar all and post the results, removing your IMEI and Serial number please?
Are you completely stock, S-on and locked bootloader?
S-on , Bootloader locked. Complete Stock.
stovie_steve said:
Can you post a fastboot getvar all and post the results, removing your IMEI and Serial number please?
Are you completely stock, S-on and locked bootloader?
Click to expand...
Click to collapse
Yes i am Completely on stock with S-on and locked bootloader. I switched my phone from At&t to Dev edition some months back . I installed a Brightstar RUU and did a series of OTA time to time. So it was S-on , bootloader locked and no custom recovery etc All perfect with no playing around. Was my 1st device.
Thanks
anirudhgargi said:
Yes i am Completely on stock with S-on and locked bootloader. I switched my phone from At&t to Dev edition some months back . I installed a Brightstar RUU and did a series of OTA time to time. So it was S-on , bootloader locked and no custom recovery etc All perfect with no playing around. Was my 1st device.
Thanks
Click to expand...
Click to collapse
Please post a fastboot getvar all. To do this, connect your phone to the computer and make sure you have adb/fastboot files. At the bootloader screen it shoulder say FASTBOOT USB
Open a command prompt from the folder where your ADB files are and type the command fastboot getvar all. Post the results here, and remember to remove your serial no and IMEI
GetVar All Output.
stovie_steve said:
Please post a fastboot getvar all. To do this, connect your phone to the computer and make sure you have adb/fastboot files. At the bootloader screen it shoulder say FASTBOOT USB
Open a command prompt from the folder where your ADB files are and type the command fastboot getvar all. Post the results here, and remember to remove your serial no and IMEI
Click to expand...
Click to collapse
Anirudh-Gargis-MacBook:~ anirudhgargi$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.07.1540.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: -------------------
(bootloader) imei: ----------------------
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3790mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.043s
anirudhgargi said:
Anirudh-Gargis-MacBook:~ anirudhgargi$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.07.1540.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: -------------------
(bootloader) imei: ----------------------
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3790mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.043s
Click to expand...
Click to collapse
Your CID is cidnum: 11111111 which means this phone has been rooted before. Did you run any fastboot commands e.g. fastboot writesecureflag 3 and go back to S-ON? Did you install any updates recently?
Rooted when it was 4.1 on At&t. But never then.
stovie_steve said:
Your CID is cidnum: 11111111 which means this phone has been rooted before. Did you run any fastboot commands e.g. fastboot writesecureflag 3 and go back to S-ON? Did you install any updates recently?
Click to expand...
Click to collapse
Yes it was rooted when it was 4.1 and then i installed a 4.2 via RUU.exe to get to Dev Edition. I changed to SuperCid as that time the RUU was not working for some reason. I left it 1111111 as i was able to get the OTA updates normally. Since that 4.3 no rooting and no S-off. Had been like this since then.
I did not install any update recently. Last update was back in Aug for the sense 6.0. Have been using since then without any issue , except for couple of OS crashes.
What you doubt ? Has the OS partition corrupted ? Do i need to reflash ?
anirudhgargi said:
Yes it was rooted when it was 4.1 and then i installed a 4.2 via RUU.exe to get to Dev Edition. I changed to SuperCid as that time the RUU was not working for some reason. I left it 1111111 as i was able to get the OTA updates normally. Since that 4.3 no rooting and no S-off. Had been like this since then.
I did not install any update recently. Last update was back in Aug for the sense 6.0. Have been using since then without any issue , except for couple of OS crashes.
What you doubt ? Has the OS partition corrupted ? Do i need to reflash ?
Click to expand...
Click to collapse
I checked for an RUU for your current version but cannot find one. And because you are S-ON you cannot downgrade or run an earlier RUU
Your option at present may be only to unlock the bootloader via HTC.dev, install custom ROM/Recovery and then obtain S-OFF via firewater or Sunshine to remove the TAMPERED and re-lock the bootloader
Ohh ! i don't have a Window machine also handy
stovie_steve said:
I checked for an RUU for your current version but cannot find one. And because you are S-ON you cannot downgrade or run an earlier RUU
Your option at present may be only to unlock the bootloader via HTC.dev, install custom ROM/Recovery and then obtain S-OFF via firewater or Sunshine to remove the TAMPERED and re-lock the bootloader
Click to expand...
Click to collapse
I was also checking the RUU if theres is one of 4.4 wirh sense6 released by htc.
As i am S-On i cannot download a previous version of RUU and flash that ? Why is that ?
Can a OTA update ( MR ) will do ? i can try searching for the latest OTA file
i can just place the OTA of the latest Sense 6 and then place in storage and choose update via phone storage.
anirudhgargi said:
I was also checking the RUU if theres is one of 4.4 wirh sense6 released by htc.
As i am S-On i cannot download a previous version of RUU and flash that ? Why is that ?
Can a OTA update ( MR ) will do ? i can try searching for the latest OTA file
i can just place the OTA of the latest Sense 6 and then place in storage and choose update via phone storage.
Click to expand...
Click to collapse
S-ON does not permit you to downgrade to another RUU, only upgrade. If you try and flash an RUU.zip via fastboot you will have a beautiful aluminium ornament as the phone will not work.
I don't think there is an OTA either
Many thanks, i will update after doing all those steps.
stovie_steve said:
S-ON does not permit you to downgrade to another RUU, only upgrade. If you try and flash an RUU.zip via fastboot you will have a beautiful aluminium ornament as the phone will not work.
I don't think there is an OTA either
Click to expand...
Click to collapse
I was able to find the Sense 6 4.4 OTA. Just that i am scared now.
I guess i will have to get a window pc to do that what you told.
Many thanks @stovie_steve.
Regards,
ANirudh
anirudhgargi said:
I was able to find the Sense 6 4.4 OTA. Just that i am scared now.
I guess i will have to get a window pc to do that what you told.
Many thanks @stovie_steve.
Regards,
Anirudh
Click to expand...
Click to collapse
1 more question , which file can i download after unlocking the bootloader ?
I mean can i install another binary with S-On and unlocked bootloader ? Which one shall i download
To do S-off i need to have working android (adbshell).
And just to understand the process I need that to install a custom recovery so that i can do a S-off. Once S-off i can run the 4.3 RUU exe. Right ? Of course re-lock the bootloader later as i will be doing a updates from HTC (signed) only.
After that OTA can bring me to latest OS ?
Which Custom rom to flash for next step.
anirudhgargi said:
1 more question , which file can i download after unlocking the bootloader ?
I mean can i install another binary with S-On and unlocked bootloader ? Which one shall i download
To do S-off i need to have working android (adbshell).
And just to understand the process I need that to install a custom recovery so that i can do a S-off. Once S-off i can run the 4.3 RUU exe. Right ? Of course re-lock the bootloader later as i will be doing a updates from HTC (signed) only.
After that OTA can bring me to latest OS ?
Click to expand...
Click to collapse
I have unlocked the bootloader and got a custom recovery (twrp) . I am still s-on. To do S-off
i need to have a working android , for that i need a custom rom. Can anybody tell which rom can be good , i have already the latest Stock 4.4 with "S-ON" and unlocked bootloader.
I cannot flash a htc rom directly as i am S-on and have latest update. To download a version lower (RUU avail) i need to do s-off.
My final aim to get back to Stock 4.4 Sense 6 . This way i approached my HTC one hit a boot loop and not coming out after all methods.
Hello,
I've gave my phone to service, and theyve installed a branded soft of T-Mobile which made my phone a real battery drainer + some of functions stopped working.
Tried to search through forum for a stock NOT MODIFIED rom, but im new to this and i found a lot of names like RUU, RUU zip etc a lot of numbers and ive got lost. Could somebody help me to find ROM that do NOT require root and unlocking bootloader so i could flash it to my device?
Phone model id PN07100 im from Poland, i dont want any brand just clean rom from htc
I really dont know where to find this rom :c
Ultearie said:
Hello,
I've gave my phone to service, and theyve installed a branded soft of T-Mobile which made my phone a real battery drainer + some of functions stopped working.
Tried to search through forum for a stock NOT MODIFIED rom, but im new to this and i found a lot of names like RUU, RUU zip etc a lot of numbers and ive got lost. Could somebody help me to find ROM that do NOT require root and unlocking bootloader so i could flash it to my device?
Phone model id PN07100 im from Poland, i dont want any brand just clean rom from htc
I really dont know where to find this rom :c
Click to expand...
Click to collapse
If you want a rom that doesn't require unlocking the bootloader or anything else like s-off, then the only thing you can do is to flash the same RUU you already have installed on your phone (t-mobile ruu).
post the output of "fastboot getvar all". Remove imei and serialno before posting
Where should i input this? Im a mac user, but got access to windows too
Ultearie said:
Where should i input this? Im a mac user, but got access to windows too
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1917237
@alray when i do as showed in tutorial above it gets stuck on <waiting for device>
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
FA36KW903140 offline
MacBook-Air:~ Ultearie$ fastboot getvar all
< waiting for device >
Also that device is offline is weird, i've turned on usb debugging, what could go wrong?
Ultearie said:
@alray when i do as showed in tutorial above it gets stuck on <waiting for device>
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
FA36KW903140 offline
MacBook-Air:~ Ultearie$ fastboot getvar all
< waiting for device >
Also that device is offline is weird, i've turned on usb debugging, what could go wrong?
Click to expand...
Click to collapse
Probably an outdated sdk. What is the output of "adb version" ?
@alray Figured it out
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.26.3263.05
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.24.69.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:xxx
(bootloader) imei: xxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANGB10
(bootloader) battery-status: good
(bootloader) battery-voltage: 3867mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-660ef031
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Hello All
Recentely i´ve put my phone to the latest firmware/rom Lollipop 5.0.2
I try to search on how to root the phone, but cant find anything, on how to do that, or if its possible.
Does anyone have that information on how to accomplish that?
Many Thanks to you guys.
bmgrpt said:
Hello All
Recentely i´ve put my phone to the latest firmware/rom Lollipop 5.0.2
I try to search on how to root the phone, but cant find anything, on how to do that, or if its possible.
Does anyone have that information on how to accomplish that?
Many Thanks to you guys.
Click to expand...
Click to collapse
Does it have anything to do with this thread?
Ultearie said:
@alray Figured it out
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.26.3263.05
(bootloader) version-main: 4.24.69.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANGB10
Click to expand...
Click to collapse
so you have 2 options:
Achieve s-off using Sunshine
change your cid to HTC__001
flash the international RUU version of lollipop 5.0.2/Sense 6 (7.19.401.2)
or
Unlock your bootloader
flash a custom recovery
flash a "close to stock" custom rom like arhd, insertcoin, maximusHD etc etc...
Nothing can be done without unlocking or s-off.
alray said:
so you have 2 options:
Achieve s-off using Sunshine
change your cid to HTC__001
flash the international RUU version of lollipop 5.0.2/Sense 6 (7.19.401.2)
or
Unlock your bootloader
flash a custom recovery
flash a "close to stock" custom rom like arhd, insertcoin, maximusHD etc etc...
Nothing can be done without unlocking or s-off.
Click to expand...
Click to collapse
If i use s-off will i loose warrancy?
bmgrpt said:
Hello All
Recentely i´ve put my phone to the latest firmware/rom Lollipop 5.0.2
I try to search on how to root the phone, but cant find anything, on how to do that, or if its possible.
Does anyone have that information on how to accomplish that?
Many Thanks to you guys.
Click to expand...
Click to collapse
Flash twrp recovery and then flash latest supersu.zip
---------- Post added at 10:58 AM ---------- Previous post was at 10:58 AM ----------
Ultearie said:
If i use s-off will i loose warrancy?
Click to expand...
Click to collapse
yes
Ultearie said:
Does it have anything to do with this thread?
Click to expand...
Click to collapse
If you notice the title of your thread is not specific, so yes.
It´s a generic title, not a specific one, if you dont want users to ask questions in a generic thread, you must be more specific.
alray said:
Flash twrp recovery and then flash latest supersu.zip
---------- Post added at 10:58 AM ---------- Previous post was at 10:58 AM ----------
yes
Click to expand...
Click to collapse
So i cant do anything to avoid warranty void?
bmgrpt said:
If you notice the title of your thread is not specific, so yes.
It´s a generic title, not a specific one, if you dont want users to ask questions in a generic thread, you must be more specific.
Click to expand...
Click to collapse
I already answered your question even if its obvious that its not related to this thread (read the OP). No need to start a war here because the thread title is not enough specific for you.
thanks.
---------- Post added at 11:03 AM ---------- Previous post was at 11:03 AM ----------
Ultearie said:
So i cant do anything to avoid warranty void?
Click to expand...
Click to collapse
s-off itself doesn't void warranty but there is no ruu to return your phone back to stock. Any modification will void your warranty if you can't return everything back to 100% stock.
@alray is there any guide where i can do this step by step, because i dont want to mess something up
alray said:
I already answered your question even if its obvious that its not related to this thread (read the OP). No need to start a war here because the thread title is not enough specific for you.
thanks.
---------- Post added at 11:03 AM ---------- Previous post was at 11:03 AM ----------
s-off itself doesn't void warranty but there is no ruu to return your phone back to stock. Any modification will void your warranty if you can't return everything back to 100% stock.
Click to expand...
Click to collapse
Ok
Buy the way can you tell me what are the versions that i need to flash? Either the TWRP and the SuperSU?
Do i loose the capability of getting OTA updates doing that?
On early versions when i flash the boot screen there was a red message on the boot, something like "this is for development purposes......" Do you know if it will happen here.
Thanks
Ultearie said:
@alray is there any guide where i can do this step by step, because i dont want to mess something up
Click to expand...
Click to collapse
s-off using sunshine (no guide required here, the Sunshine app will do everything for you)
To change your cid to HTC__001, reboot your phone in bootloader / fastboot usb mode and enter this command:
Code:
fastboot oem writecid HTC__001
fastboot reboot-bootloader
then confirm your cid is now HTC__001 either by using:
Code:
fastbot getvar all
or
Code:
fastboot oem readcid
or
Code:
fastboot getvar cid
then you can flash the 7.19.401.2 firmware:
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot reboot-bootloader
Confirm your firmware is now 7.19.401.2:
Code:
fastboot getvar version-main
then flash the 7.19.401.2 ruu using these instructions (with htc_fastboot): http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
Edit: BTW i'm not responsible if you brick your phone, there are always some risks.
---------- Post added at 11:28 AM ---------- Previous post was at 11:17 AM ----------
bmgrpt said:
Ok
Buy the way can you tell me what are the versions that i need to flash? Either the TWRP and the SuperSU?
Click to expand...
Click to collapse
How to find twrp for the M7
How to find latest supersu.zip
Do i loose the capability of getting OTA updates doing that?
Click to expand...
Click to collapse
Maybe yes, Maybe no. already answered that same question 45 min ago here
On early versions when i flash the boot screen there was a red message on the boot, something like "this is for development purposes......" Do you know if it will happen here.
Click to expand...
Click to collapse
Yes it will.
That being said, you are still off topic here and having 2 different discussions in this thread for 2 unrelated topic might be confusing for the OP. Please post in the appropriate thread if you have any other question, I'll be happy to help you there.
alray said:
s-off using sunshine (no guide required here, the Sunshine app will do everything for you)
To change your cid to HTC__001, reboot your phone in bootloader / fastboot usb mode and enter this command:
Code:
fastboot oem writecid HTC__001
fastboot reboot-bootloader
then confirm your cid is now HTC__001 either by using:
Code:
fastbot getvar all
or
Code:
fastboot oem readcid
or
Code:
fastboot getvar cid
then you can flash the 7.19.401.2 firmware:
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot reboot-bootloader
Confirm your firmware is now 7.19.401.2:
Code:
fastboot getvar version-main
then flash the 7.19.401.2 ruu using these instructions (with htc_fastboot): http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
---------- Post added at 11:28 AM ---------- Previous post was at 11:17 AM ----------
How to find twrp for the M7
How to find latest supersu.zip
Maybe yes, Maybe no. already answered that same question 45 min ago here
Yes it will.
That being said, you are still off topic here and having 2 different discussions in this thread for 2 unrelated topic might be confusing for the OP. Please post in the appropriate thread if you have any other question, I'll be happy to help you there.
Click to expand...
Click to collapse
Well downloaded sunshine, but after it passed compatibility test it asked me to purchase or enter code of license ;s entered fastboot and received
...
(bootloader) [JAVACARD_ERR] SD/USBDISK Init error
OKAY [ 0.000s]
finished. total time: 0.000s
Ultearie said:
Well downloaded sunshine, but after it passed compatibility test it asked me to purchase or enter code of license ;s entered fastboot and received
...
(bootloader) [JAVACARD_ERR] SD/USBDISK Init error
OKAY [ 0.000s]
finished. total time: 0.000s
Click to expand...
Click to collapse
yep Sunshine cost 25$ and will only ask you to pay for the license if it have determined that it will work on your device. If you are experiencing any problem with sunshine you can contact their help team on IRC there: http://webchat.freenode.net/?channels=sunshine-support
Guys its urgent. I am using TWRP recovery and wipe the whole phone including internal memory only left system not being wiped yet. Then when i boot to the system i cannot see the status bar! and just a popup window saying that system ui stopped.. and most importantly i cannot use virtual SD card. Cuz now i wanna re-flash the ROM so that i can fix it. But now i cannot even write or read the internal memory meaning that i cannot even download the ROM again and flash it! anyone can help? TAT
Jakob Zhang said:
Guys its urgent. I am using TWRP recovery and wipe the whole phone including internal memory only left system not being wiped yet. Then when i boot to the system i cannot see the status bar! and just a popup window saying that system ui stopped.. and most importantly i cannot use virtual SD card. Cuz now i wanna re-flash the ROM so that i can fix it. But now i cannot even write or read the internal memory meaning that i cannot even download the ROM again and flash it! anyone can help? TAT
Click to expand...
Click to collapse
What is your twrp version
What is your "fastboot getvar all" (don't post imei/sn)
alray said:
What is your twrp version
What is your "fastboot getvar all" (don't post imei/sn)
Click to expand...
Click to collapse
Hi bro mine is 2.8.4.0 version TWRP.
and i dont quite undertand ur 2nd qn? How do i check that?
Jakob Zhang said:
Hi bro mine is 2.8.4.0 version TWRP.
and i dont quite undertand ur 2nd qn? How do i check that?
Click to expand...
Click to collapse
Do you have fastboot and adb installed on your computer (the android sdk) and the latest htc drivers?
alray said:
Do you have fastboot and adb installed on your computer (the android sdk) and the latest htc drivers?
Click to expand...
Click to collapse
Yes i do i got the fastboot and adb files in my laptop. For the drivers i think yes but not sure. But when i connect my phone to laptop it shows that it is able to detect the internal storage.
Jakob Zhang said:
Yes i do i got the fastboot and adb files in my laptop. For the drivers i think yes but not sure. But when i connect my phone to laptop it shows that it is able to detect the internal storage.
Click to expand...
Click to collapse
Ok so do you know how to use fastboot/adb commands? If yes then post the output of "fastboot getvar all" (except your imei and sn).
If no read post #6 of this thread: http://forum.xda-developers.com/htc-one/help/help-to-phone-t3254025
alray said:
Ok so do you know how to use fastboot/adb commands? If yes then post the output of "fastboot getvar all" (except your imei and sn).
If no read post #6 of this thread: http://forum.xda-developers.com/htc-one/help/help-to-phone-t3254025
Click to expand...
Click to collapse
hi bro i am using win10 and i install the HTC driver from your link, and when using fastboot command it still says that waiting for device
Jakob Zhang said:
hi bro i am using win10 and i install the HTC driver from your link, and when using fastboot command it still says that waiting for device
Click to expand...
Click to collapse
Either the drivers are not installed correctly or its a connectivity issue (bad USB cable, bad USB port (phone or computer).
What is your hboot version?
Try a different cable already known to work for data connection
Try another usb port (usb 2.0 only)
Try another computer
alray said:
Either the drivers are not installed correctly or its a connectivity issue (bad USB cable, bad USB port (phone or computer).
What is your hboot version?
Try a different cable already known to work for data connection
Try another usb port (usb 2.0 only)
Try another computer
Click to expand...
Click to collapse
May i just use fastboot flash XXX.zip command to flash a new ROM so that i could fix the problem? I will try ur suggestion one by one. My hboot is ver1.54
Jakob Zhang said:
May i just use fastboot flash XXX.zip command to flash a new ROM so that i could fix the problem? I will try ur suggestion one by one. My hboot is ver1.54
Click to expand...
Click to collapse
You can't flash a rom using "fastboot flash xxx.zip" The only thing you can flash using fastboot is a RUU and that will requires fastboot connectivity and the output of "fastboot getvar all" so we can know what ruu you need.
Thx bro i am coming back
alray said:
You can't flash a rom using "fastboot flash xxx.zip" The only thing you can flash using fastboot is a RUU and that will requires fastboot connectivity and the output of "fastboot getvar all" so we can know what ruu you need.
Click to expand...
Click to collapse
''"
Hi bro sry for the late reply. I am busy for my exam these days. And thx for your kind help again! I use my roommate's laptop and it works! Here is my result for "fastboot getvar all":
C:\Users\user\Desktop\SDK>fastboot getvar all
< waiting for device >
(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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 3998mV
(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!
May i know which RUU should i flash? thx bro
Jakob Zhang said:
''"
Hi bro sry for the late reply. I am busy for my exam these days. And thx for your kind help again! I use my roommate's laptop and it works! Here is my result for "fastboot getvar all":
C:\Users\user\Desktop\SDK>fastboot getvar all
< waiting for device >
(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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 3998mV
(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!
May i know which RUU should i flash? thx bro
Click to expand...
Click to collapse
Would help to have S-OFF, There are 3 RUU that can be flashed on your phone, the first one 3.63.707.4 is an unsigned RUU and requires S-OFF, the second and third ones requires your firmware to be updated before they can be flashed on your phone...
You might want to flash this rom using twrp http://www.htc1guru.com/dld/guru_reset_m7_2-24-707-1-zip/. When installing, select yes to install stock recovery and stock radio, select no when asked to root. Then boot the phone in the OS and try updating it.
Ps. Please don't send me multiple PMs requesting "urgent" help. Just post here and I (or someone else) will eventually answer you as soon as possible.
alray said:
Would help to have S-OFF, There are 3 RUU that can be flashed on your phone, the first one 3.63.707.4 is an unsigned RUU and requires S-OFF, the second and third ones requires your firmware to be updated before they can be flashed on your phone...
You might want to flash this rom using twrp http://www.htc1guru.com/dld/guru_reset_m7_2-24-707-1-zip/. When installing, select yes to install stock recovery and stock radio, select no when asked to root. Then boot the phone in the OS and try updating it.
Ps. Please don't send me multiple PMs requesting "urgent" help. Just post here and I (or someone else) will eventually answer you as soon as possible.
Click to expand...
Click to collapse
I apologize for PM u twice bro! I download the ruu and one is in exe. format, i follow the step and it said that the phone and PC is not well connected. And the second RUU is in zip form and there are a lot of files inside like boot.img somehow. I get trouble in flashing the RUU and what is the most safe way of doing S-OFF?
Jakob Zhang said:
I apologize for PM u twice bro! I download the ruu and one is in exe. format, i follow the step and it said that the phone and PC is not well connected. And the second RUU is in zip form and there are a lot of files inside like boot.img somehow. I get trouble in flashing the RUU and what is the most safe way of doing S-OFF?
Click to expand...
Click to collapse
You should be able to S-OFF using Rumrunner which is free. The easiest way to S-OFF is Sunshine which cost 25$. Did you tried the rom linked above?
alray said:
You should be able to S-OFF using Rumrunner which is free. The easiest way to S-OFF is Sunshine which cost 25$. Did you tried the rom linked above?
Click to expand...
Click to collapse
Hi should I just use fastboot flash command to flash the rom? Since I cannot read or write on virtual sd card I dunno how to flash the rom u mentioned. Thx for ur kind and great help again
Jakob Zhang said:
Hi should I just use fastboot flash command to flash the rom? Since I cannot read or write on virtual sd card I dunno how to flash the rom u mentioned. Thx for ur kind and great help again
Click to expand...
Click to collapse
Use adb push or adb sideload to transfer the rom to your phone then flash it with twrp recovery.
alray said:
Use adb push or adb sideload to transfer the rom to your phone then flash it with twrp recovery.
Click to expand...
Click to collapse
Really really to my greatest gratitude! Now my phone back to the stock rom and functions normally! OMG thx bro Thx for your patient and amazing and detailed instructions!!!!!