Related
Hello All,
Here's my dilemma. I successfully rooted my HTC One (AT&T), and was recently attempting to unroot it. I followed this one here http://forum.xda-developers.com/showthread.php?t=2182823. Since I have the AT&T version, I downloaded the first one the list found there, however it wouldn't verify. Next I downloaded the AT&T AIO here http://forum.xda-developers.com/showthread.php?t=2242635. I was able to use that to figure out according to the info it displayed that I actually needed the Google Edition one from the previous link. I thought that was weird since I dont have the google edition one. But when I fast booted that one, everything appeared to go through with a hitch.....Until it restarted.
After it restarted, I only have a black screen. No start up. I restarted the phone and went into the bootloader and to my surprise, the bootloader was black instead of the normal white.
I've tried several RUUs found here http://www.androidruu.com/index.php?developer=M7
I've tried both the exe and flashing the zip.
I have no clue what to try next. Please XDA, your my only hope.
Are you s-off? I would assume so if you've been able to run multiple RUUs and are getting weird signature results. What mods/roms did you do to your phone before you started all this?
If you can get to bootloader, you're not bricked. You're on the 3.06 GE hboot, but it's not clear why you can't boot up.
iElvis said:
Are you s-off? I would assume so if you've been able to run multiple RUUs and are getting weird signature results. What mods/roms did you do to your phone before you started all this?
If you can get to bootloader, you're not bricked. You're on the 3.06 GE hboot, but it's not clear why you can't boot up.
Click to expand...
Click to collapse
----From the top of bootloader down----
***Tampered***
***Relocked***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.18.3263.15
OpenDSO-V31.120.274.0617
(in red) OS-3.03.1700.10 (3.06.1700.10)
eMMC-boot 2048MB
Aug 1 2013, 18:48:40.0
Does that help at all?
Tylegn said:
----From the top of bootloader down----
***Tampered***
***Relocked***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.18.3263.15
OpenDSO-V31.120.274.0617
(in red) OS-3.03.1700.10 (3.06.1700.10)
eMMC-boot 2048MB
Aug 1 2013, 18:48:40.0
Does that help at all?
Click to expand...
Click to collapse
Were you ever s-off? You should not have been able to run that GE RUU on an s-on AT&T phone.
iElvis said:
Were you ever s-off? You should not have been able to run that GE RUU on an s-on AT&T phone.
Click to expand...
Click to collapse
I hate to say.... I have no clue if I was before or not. I just relocked it like the directions told me. Is there any saving me? Also, thank you for your quick responses.
Tylegn said:
I hate to say.... I have no clue if I was before or not. I just relocked it like the directions told me. Is there any saving me? Also, thank you for your quick responses.
Click to expand...
Click to collapse
You bought it new? Not used from someone else? If so, it was always s-on.
You're on GE firmware somehow. It's possible you have a conflict with your model or carrier ID. Can you run through the exact steps you took when you started trying to unroot? Exactly which files you used and how you ran them?
iElvis said:
You bought it new? Not used from someone else? If so, it was always s-on.
You're on GE firmware somehow. It's possible you have a conflict with your model or carrier ID. Can you run through the exact steps you took when you started trying to unroot? Exactly which files you used and how you ran them?
Click to expand...
Click to collapse
I received the phone directly from HTC through a sell to earn contest.
Not sure if it matters much but I unlocked the bootloader through HTC Dev.
To unroot,
1) Put phone in bootloader with fastboot
2) Relocked bootloader
3) fastboot oem rebootRUU
4) fastboot flash zip 2.24.401.1.zip (failed)
Used one of the AIOs that stated I had modelid: PN0712000 and cidnum: CWS__001. That when I grabbed the GE version.
5) fastboot flash zip 3.06.1700.10.zip
6) Phone finished, rebooted to a black screen
7) Rebooted into bootloader (Which is now black instead of white)
8) Sad ever since....
Where did you get that GE zip? I'm not sure why the AIO toolkit told you that you were GE but I'd like to check the file.
I suspect the problem is that you have 4.3 GE firmware but a 4.1 OS. Flashing a 4.2 or 4.3 rom might fix.
ageldea consider
iElvis said:
Where did you get that GE zip? I'm not sure why the AIO toolkit told you that you were GE but I'd like to check the file.
I suspect the problem is that you have 4.3 GE firmware but a 4.1 OS. Flashing a 4.2 or 4.3 rom might fix.
Click to expand...
Click to collapse
This is where I got:
http://forum.xda-developers.com/showthread.php?t=2182823
I'll need a step by step from you if you can because, I'm having a h3ll of a time trying to get anything to flash.
Tylegn said:
This is where I got:
http://forum.xda-developers.com/showthread.php?t=2182823
I'll need a step by step from you if you can because, I'm having a h3ll of a time trying to get anything to flash.
Click to expand...
Click to collapse
:facepalm: Just realized the issue.
Your bootloader is locked and you still have custom recovery installed, I'm guessing. Can you select Recovery in bootloader and see what happens? If you're still with TWRP or CWM, that's the issue; you can't boot locked on custom recovery.
You have to unlock again or flash the stock recovery in fastboot. Unlocking will wipe your phone, unfortunately.
Flashing recovery in fastboot is easy if you have the stock recovery file.
fastboot flash recovery [filename].img
iElvis said:
:facepalm: Just realized the issue.
Your bootloader is locked and you still have custom recovery installed, I'm guessing. Can you select Recovery in bootloader and see what happens? If you're still with TWRP or CWM, that's the issue; you can't boot locked on custom recovery.
You have to unlock again or flash the stock recovery in fastboot. Unlocking will wipe your phone, unfortunately.
Flashing recovery in fastboot is easy if you have the stock recovery file.
fastboot flash recovery [filename].img
Click to expand...
Click to collapse
You are right about having the recovery option in the bootloader but when I try to select that option, Android shows up with the spinning blue thing in it's stomach, then it dies with a red triangle.
I'll try flashing the recovery again. After I find a stock recovery img. LOL
Thanks again!!!
I'll post what's going on as I do it.
iElvis said:
:facepalm: Just realized the issue.
Your bootloader is locked and you still have custom recovery installed, I'm guessing. Can you select Recovery in bootloader and see what happens? If you're still with TWRP or CWM, that's the issue; you can't boot locked on custom recovery.
You have to unlock again or flash the stock recovery in fastboot. Unlocking will wipe your phone, unfortunately.
Flashing recovery in fastboot is easy if you have the stock recovery file.
fastboot flash recovery [filename].img
Click to expand...
Click to collapse
Found the stock recovery. Attempted to flash it and got this:
sending 'recovery' <16303 KB>...
OKAY [ 1.786s]
writing 'recovery'...
<bootloader> signature checking...
FAILED <remote: 12 signature verify fail>
finished. total time: 3.178s
Is there a different way I should be doing it.
HTC One has the Gray HTC logo chilling on the screen...
Also tried in normal fastboot mode...
Tylegn said:
You are right about having the recovery option in the bootloader but when I try to select that option, Android shows up with the spinning blue thing in it's stomach, then it dies with a red triangle.
I'll try flashing the recovery again. After I find a stock recovery img. LOL
Thanks again!!!
I'll post what's going on as I do it.
Click to expand...
Click to collapse
Actually, I think that red triangle is stock recovery. I think to get to the recovery options you press power+vol up on that screen. But it doesn't matter because clearly you're not on custom recovery.
I don't see that 3.06 firmware package in the OP of that thread. Can you find the post you found it attached to?
iElvis said:
Actually, I think that red triangle is stock recovery. I think to get to the recovery options you press power+vol up on that screen. But it doesn't matter because clearly you're not on custom recovery.
I don't see that 3.06 firmware package in the OP of that thread. Can you find the post you found it attached to?
Click to expand...
Click to collapse
If you click on the download link in that post for the GE it downloads as that 3.06 firmware..
Also, not sure if it was smart or not but I unlocked the bootloader again to see if it would fix the conflicts you mentioned before. Haven't tried flashing anything yet...
ADD: I just successfully flashed the stock recovery.... Too scared to muck something up so I'll waif for your superior guidance!
Thanks again
Tylegn said:
If you click on the download link in that post for the GE it downloads as that 3.06 firmware..
Also, not sure if it was smart or not but I unlocked the bootloader again to see if it would fix the conflicts you mentioned before. Haven't tried flashing anything yet...
Click to expand...
Click to collapse
I forgot Mike updated that link.
Okay, I see what you did now. You've essentially upgraded your phone to a GE because the android-info.txt in this official firmware matched your MID and CID; that allowed it to run. The problem is that you can't go back now because you're s-on. Your phone won't boot because you have the GE kernel installed but I assume a Sense rom.
This should be easy to fix. You can flash custom recovery now that you've unlocked, then flash a custom rom. This will get your kernel and rom consistent again and you should be able to boot.
Unrooting is a different story. You can't go back to the stock configuration you had when you got the phone without s-off, which you can't get on 1.54 hboot. I'm afraid you're stuck until AT&T releases 4.3 and you can run a RUU.
iElvis said:
I forgot Mike updated that link.
Okay, I see what you did now. You've essentially upgraded your phone to a GE because the android-info.txt in this official firmware matched your MID and CID; that allowed it to run. The problem is that you can't go back now because you're s-on. Your phone won't boot because you have the GE kernel installed but I assume a Sense rom.
This should be easy to fix. You can flash custom recovery now that you've unlocked, then flash a custom rom. This will get your kernel and rom consistent again and you should be able to boot.
Unrooting is a different story. You can't go back to the stock configuration you had when you got the phone without s-off, which you can't get on 1.54 hboot. I'm afraid you're stuck until AT&T releases 4.3 and you can run a RUU.
Click to expand...
Click to collapse
So no getting my white bootloader back till next release? That's ok.
However, how do I flash the custom ROM. I got the customer recovery going but I don't know how to get the ROM on there.... Flashing isn't working, still getting signature failures.
Sorry
Tylegn said:
So no getting my white bootloader back till next release? That's ok.
However, how do I flash the custom ROM. I got the customer recovery going but I don't know how to get the ROM on there.... Flashing isn't working, still getting signature failures.
Sorry
Click to expand...
Click to collapse
You can only run a later firmware. When the signed 4.3 Sense firmware is released (it may be there now), you should be able to run that and get back the stock HTC bootloader.
You need to adb push the rom file onto your phone. There is a tutorial for doing it here: http://forum.xda-developers.com/showthread.php?t=2317986
iElvis said:
You can only run a later firmware. When the signed 4.3 Sense firmware is released (it may be there now), you should be able to run that and get back the stock HTC bootloader.
You need to adb push the rom file onto your phone. There is a tutorial for doing it here: http://forum.xda-developers.com/showthread.php?t=2317986
Click to expand...
Click to collapse
Thank you so much! I believe I can take it from here.....Until I brick my phone when the signed 4.3 comes out. LOL
Until next time. Thanks iElivis you are a BADA$$!:good::good::good:
Hello everyone,
This is my fisrt time writing in this forum, hope you guys can share some knowledge with me. Here is my issue:
I bought a HTC One to a guy a few weeks ago with barely no use. The thing is that I didn´t know at that time that the device was rooted with the MaximusHD. When I realized about it I reset my phone to factory settings and the new 4.3 3.22.1540.1 got installed. Thought it was ok but it is still doing some weird things so I decided to unroot the device to stock, also for warranty porpuses.
The problem comes when I try to download the RUU for my device due to I cannot find it. Should I do it through other method? Do I have to S-off to downgrade and install the RUU 1.29?
My phone is the following:
M7_UL PVT Ship S-On RH
Baseband 4A.17.3250.14
Hboot 1.54.0000
OpenDSP v31.120.274.0617
It is the european unlocked/international version bought in Spain.
I would really appreciate if someone could give a hand on this and guide me in through this process. I was an iPhone guy and now I'm freaking lost.
Thanks so much!
kikinhorap said:
Hello everyone,
This is my fisrt time writing in this forum, hope you guys can share some knowledge with me. Here is my issue:
I bought a HTC One to a guy a few weeks ago with barely no use. The thing is that I didn´t know at that time that the device was rooted with the MaximusHD. When I realized about it I reset my phone to factory settings and the new 4.3 3.22.1540.1 got installed. Thought it was ok but it is still doing some weird things so I decided to unroot the device to stock, also for warranty porpuses.
The problem comes when I try to download the RUU for my device due to I cannot find it. Should I do it through other method? Do I have to S-off to downgrade and install the RUU 1.29?
My phone is the following:
M7_UL PVT Ship S-On RH
Baseband 4A.17.3250.14
Hboot 1.54.0000
OpenDSP v31.120.274.0617
It is the european unlocked/international version bought in Spain.
I would really appreciate if someone could give a hand on this and guide me in through this process. I was an iPhone guy and now I'm freaking lost.
Thanks so much!
Click to expand...
Click to collapse
Your bootloader should already be unlocked, so simply get S-OFF using Rumrunner, then follow this guide.
Answer
attanasi0 said:
Your bootloader should already be unlocked, so simply get S-OFF using Rumrunner, then follow this guide.
Click to expand...
Click to collapse
Thanks for the reply. I've tried to s-off my htc but it hasnt worked. So I downloaded the recovery stock version and after installing it, the device told me that my phone doesnt appear to be rooted and if i wanted to install supersu, i declined and then made a recovery. Phone looks like unrooted, although within the bootloader it still shows "tampered" and "Unlocked". The recovery mode that the phone had installed has disappeared so I dont know what to do now, should I continue to s-off the device and then put it down to hboot 1.44 and follow the unroot guide???
I would like to make sure my device is unrooted in order to gain warranty privilages just in case i need to send out my phone to htc...
Thanks!
kikinhorap said:
Thanks for the reply. I've tried to s-off my htc but it hasnt worked. So I downloaded the recovery stock version and after installing it, the device told me that my phone doesnt appear to be rooted and if i wanted to install supersu, i declined and then made a recovery. Phone looks like unrooted, although within the bootloader it still shows "tampered" and "Unlocked". The recovery mode that the phone had installed has disappeared so I dont know what to do now, should I continue to s-off the device and then put it down to hboot 1.44 and follow the unroot guide???
I would like to make sure my device is unrooted in order to gain warranty privilages just in case i need to send out my phone to htc...
Thanks!
Click to expand...
Click to collapse
You don't really have a choice, unless you have the RUU for your phone. Can you post the results of "fastboot getvar all" so we can try to figure out what to do.
A
attanasi0 said:
You don't really have a choice, unless you have the RUU for your phone. Can you post the results of "fastboot getvar all" so we can try to figure out what to do.
Click to expand...
Click to collapse
I've attached the results in a jpg file. The only thing that has changed is the baseband...it went up to 4A.20.3263.16
kikinhorap said:
I've attached the results in a jpg file. The only thing that has changed is the baseband...it went up to 4A.20.3263.16
Click to expand...
Click to collapse
Just a quick note here, "version-main: <blank>" I never like that.
BTW, when posting "fastboot getvar all" it's preferably to remove IMEI and s/n; we don't need to see that.
You should probably get s-off as @attanasi0 suggested and then run a "HTC__304" downgrade RUU. (You can only downgrade if you're S-Off)
Just my two cents
nkk71 said:
Just a quick note here, "version-main: <blank>" I never like that.
BTW, when posting "fastboot getvar all" it's preferably to remove IMEI and s/n; we don't need to see that.
You should probably get s-off as @attanasi0 suggested and then run a "HTC__304" downgrade RUU. (You can only downgrade if you're S-Off)
Just my two cents
Click to expand...
Click to collapse
Im sorry about the pic, I'll edit my msg later. Im trying to s-off but it fails everytime. Dunno what to try now...
In regards to the "version main", I tried lots of times but it was blank all of them, dunno why. Some of you guys know what the reason could be?
kikinhorap said:
Im sorry about the pic, I'll edit my msg later. Im trying to s-off but it fails everytime. Dunno what to try now...
In regards to the "version main", I tried lots of times but it was blank all of them, dunno why. Some of you guys know what the reason could be?
Click to expand...
Click to collapse
When you boot to bootloader does it also show nothing in OS (7th line down or so)? Can you remember the last OTA you took?
nkk71 said:
When you boot to bootloader does it also show nothing in OS (7th line down or so)? Can you remember the last OTA you took?
Click to expand...
Click to collapse
Right, it shows just OS- but nothing else...when i bought it the guy had installed the MaximusHD 13 and I updated through OTA to the MaximusHD 20 but wasnt going smooth so I reset it to factory settings and It installed the JB 4.3 (3.22.1540.1).
Today after trying to s-off without success, I downloaded the recovery stock version for the rom I had and flashed it and the recovery mode that I had before disappeared and the baseband upgraded to 4A.20...instead of the 4A.17 that I had before that. Did the guy who sold me the htc messed it up? is there anything I can do to set my device to factory settings?
Thanks for the help guys! I appreciate it!
kikinhorap said:
Right, it shows just OS- but nothing else...when i bought it the guy had installed the MaximusHD 13 and I updated through OTA to the MaximusHD 20 but wasnt going smooth so I reset it to factory settings and It installed the JB 4.3 (3.22.1540.1).
Today after trying to s-off without success, I downloaded the recovery stock version for the rom I had and flashed it and the recovery mode that I had before disappeared and the baseband upgraded to 4A.20...instead of the 4A.17 that I had before that. Did the guy who sold me the htc messed it up? is there anything I can do to set my device to factory settings?
Thanks for the help guys! I appreciate it!
Click to expand...
Click to collapse
Well from the information available, you have
- hboot 1.54
- m7_ul
- PN0710000
- CID HTC__304
this would lead me to assume you have a 2.24.401.x based phone.
I would try to get one of the following Guru Reset ROM:
2.24.401.8 : http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-8-zip/
2.24.401.1 : http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-1-zip/
flash one of them in recovery, then follow the rumrunner steps to try to achieve S-Off.
If that is successful, then you can downgrade back to stock, using this RUU (exe): http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
check your "fastboot getvar all" after that.
Once you've done all that you can use revone (or http://forum.xda-developers.com/showthread.php?t=2477792) to remove "TAMPERED"
and also revone (or http://forum.xda-developers.com/showthread.php?t=2475914) to get you're phone "LOCKED" if you so wish
Keep S-Off !!
PS: hit the thanks button if someone has helped you
Awaiting your feedback
nkk71 said:
Well from the information available, you have
- hboot 1.54
- m7_ul
- PN0710000
- CID HTC__304
this would lead me to assume you have a 2.24.401.x based phone.
I would try to get one of the following Guru Reset ROM:
2.24.401.8 : http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-8-zip/
2.24.401.1 : http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-1-zip/
flash one of them in recovery, then follow the rumrunner steps to try to achieve S-Off.
If that is successful, then you can downgrade back to stock, using this RUU (exe): http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
check your "fastboot getvar all" after that.
Once you've done all that you can use revone (or http://forum.xda-developers.com/showthread.php?t=2477792) to remove "TAMPERED"
and also revone (or http://forum.xda-developers.com/showthread.php?t=2475914) to get you're phone "LOCKED" if you so wish
Keep S-Off !!
PS: hit the thanks button if someone has helped you
Awaiting your feedback
Click to expand...
Click to collapse
Thanks for the help. I have downloaded the Rom you gave me the link for but I dunno how to flash it due to I lost access to the teamwin recovery mode and when I click recovery onto the bootloader it goes to a black screen with a caution simbol in red and I have to reboot it.
I have tried with the goomanager to flash that rom but it doesnt let me. Any advice in this regard? I can tell goomanager to find an open recovery script (openrecovery-twrp-2.6.1.0-m7.img), should i do this? Or Im gonna end up with a bricked phone?
Thanks!
kikinhorap said:
Thanks for the help. I have downloaded the Rom you gave me the link for but I dunno how to flash it due to I lost access to the teamwin recovery mode and when I click recovery onto the bootloader it goes to a black screen with a caution simbol in red and I have to reboot it.
I have tried with the goomanager to flash that rom but it doesnt let me. Any advice in this regard? I can tell goomanager to find an open recovery script (openrecovery-twrp-2.6.1.0-m7.img), should i do this? Or Im gonna end up with a bricked phone?
Thanks!
Click to expand...
Click to collapse
"black screen with a caution simbol in red" that's stock recovery, you need to flash back a custom recovery. download (if you dont have one) from the xda threads, then enter bootloader (shut off phone, hold POWER + VOLDOWN) enter FASTBOOT, connect to PC and it should change to FASTBOOT USB
then
fastboot erase cache
fastboot flash recovery <name of recovery>.img
fastboot erase cache
fastboot reboot-bootloader
-> enter RECOVERY
then "install ZIP" in Aroma, deselect "stock recovery" so you don't need to flash it again.
nkk71 said:
"black screen with a caution simbol in red" that's stock recovery, you need to flash back a custom recovery. download (if you dont have one) from the xda threads, then enter bootloader (shut off phone, hold POWER + VOLDOWN) enter FASTBOOT, connect to PC and it should change to FASTBOOT USB
then
fastboot erase cache
fastboot flash recovery <name of recovery>.img
fastboot erase cache
fastboot reboot-bootloader
-> enter RECOVERY
then "install ZIP" in Aroma, deselect "stock recovery" so you don't need to flash it again.
Click to expand...
Click to collapse
Is the one I posted it before (openrecovery-twpr-2.6....img) ok? or should I install a different one?
Thanks for the help man, I would be even more lost than Im now without your help!
kikinhorap said:
Is the one I posted it before (openrecovery-twpr-2.6....img) ok? or should I install a different one?
Thanks for the help man, I would be even more lost than Im now without your help!
Click to expand...
Click to collapse
No problem, TWRP you mentioned should work just fine. It's the same as installing a custom ROM. I havent used TWRP but it should say something like "install zip", then find the zip and flash away.
Hopefully, that will give you a chance to successfully run rumrunner; remember to read and follow the instructions to the letter!
Good luck and keep us posted (fingers crossed)
nkk71 said:
No problem, TWRP you mentioned should work just fine. It's the same as installing a custom ROM. I havent used TWRP but it should say something like "install zip", then find the zip and flash away.
Hopefully, that will give you a chance to successfully run rumrunner; remember to read and follow the instructions to the letter!
Good luck and keep us posted (fingers crossed)
Click to expand...
Click to collapse
Well I installed the custom recovery, then flashed the stock rom 2.24.401.8 as you told me. Once I did that I ran rumrunner successfully gainning S-off.
Now I have to run the RUU but the one you suggested me is the "RUU M7 UL JB 50 HTC Europe 1.28.401.7 Radio 4A.13.3231.27 10.31.1131.05 Release 310878" but my radio is 4A.17.3250.14_10.39.1150.04L. Should I try to install it anyways? I've taken a look at the rest of RUUs and none fits my features...
btw every time I flash the stock version at the end it tells me that my phone doesnt appear to be rooted and if i want to install supersu, i always say no and after that my recovery always goes to stock, i guess it is normal, isnt it?
kikinhorap said:
Well I installed the custom recovery, then flashed the stock rom 2.24.401.8 as you told me. Once I did that I ran rumrunner successfully gainning S-off.
Click to expand...
Click to collapse
Excellent :good:
kikinhorap said:
btw every time I flash the stock version at the end it tells me that my phone doesnt appear to be rooted and if i want to install supersu, i always say no and after that my recovery always goes to stock, i guess it is normal, isnt it?
Click to expand...
Click to collapse
That's normal, dont worry about it.
kikinhorap said:
Now I have to run the RUU but the one you suggested me is the "RUU M7 UL JB 50 HTC Europe 1.28.401.7 Radio 4A.13.3231.27 10.31.1131.05 Release 310878" but my radio is 4A.17.3250.14_10.39.1150.04L. Should I try to install it anyways? I've taken a look at the rest of RUUs and none fits my features...
Click to expand...
Click to collapse
Go ahead and flash it, it will downgrade everything (now possible thanks to S-Off), and you will then receive the latest OTA package(s) to get to the most current version including radio.
nkk71 said:
Excellent :good:
That's normal, dont worry about it.
Go ahead and flash it, it will downgrade everything (now possible thanks to S-Off), and you will then receive the latest OTA package(s) to get to the most current version including radio.
Click to expand...
Click to collapse
Done!!!!! Sweet!! it worked just fine! Tampered disappeared and bootloader only shows unlocked. I have to relock it, havent I? That wouldnt mess up with my carrier right? It is just for locking the bootloader, isnt it?
Well many many thanks for your help, I couldnt have done it without it and I have learnt so much through the process Soon I'll be ready to re-root the phone again and try some custom roms hehe
Peace and greetings from Spain!
kikinhorap said:
Done!!!!! Sweet!! it worked just fine! Tampered disappeared and bootloader only shows unlocked. I have to relock it, havent I? That wouldnt mess up with my carrier right? It is just for locking the bootloader, isnt it?
Well many many thanks for your help, I couldnt have done it without it and I have learnt so much through the process Soon I'll be ready to re-root the phone again and try some custom roms hehe
Peace and greetings from Spain!
Click to expand...
Click to collapse
you should set it to LOCKED not RELOCKED using revone or http://forum.xda-developers.com/showthread.php?t=2475914
keep S-Off !!
anyway, don't why anybody would want to be on stock ROM
nkk71 said:
you should set it to LOCKED not RELOCKED using revone or http://forum.xda-developers.com/showthread.php?t=2475914
keep S-Off !!
anyway, don't why anybody would want to be on stock ROM
Click to expand...
Click to collapse
Hey! I have tried to lock it but after typing adb shell I get this "[email protected]:\ $" instead of the # that you are getting. I've tried to type "su" after that but it says that the command cannot be found. Also, when I type the code "echo -ne..." it says that I have permission denied so dunno what to do now...
Im asking in the lock/unlock threat but they just told me that its because im not rooted and that i have to install a recovery and install superuser in order to be able to introduce the code, dont really understand why I have to root it afer unrooted it :S
kikinhorap said:
Hey! I have tried to lock it but after typing adb shell I get this "[email protected]:\ $" instead of the # that you are getting. I've tried to type "su" after that but it says that the command cannot be found. Also, when I type the code "echo -ne..." it says that I have permission denied so dunno what to do now...
Im asking in the lock/unlock threat but they just told me that its because im not rooted and that i have to install a recovery and install superuser in order to be able to introduce the code, dont really understand why I have to root it afer unrooted it :S
Click to expand...
Click to collapse
You should have LOCKED it before running the RUU, because that's what made you loose root.
So before proceeding, can you give me an update of your status:
bootloader: locked/relocked/unlocked?
tampered?
ROM?
"fastboot getvar all" (remove IMEI and s/n)
Hello, I apologize in advance if I'm wrong section or anything like that ..
my htc is not 'a google edition factory but a few months ago I changed the cid and flashed
a ruu google edition and until a few days ago all good ..
unfortunately I had to format everything from cwm recovery and re install a ruu not successful, I found myself without os after several attempts I managed to put it back
now I'll post some specific
tempered
relocked (I can unlock it)
m7_ul pvt ship S-ON rh
hboot-1.54.0000
os-3.58.1700.5
now .... how can I do to install a rom and at the very least be able to turn it on?
thank you very much in advance I hope someone will be able to help me <3
edit: I forgot ... the cid is 'GOOGL001, I can not turn it on so I can not do s off to ... I flashed the boot and recovery and then the firmware but still not turn onD:
trying to flash a ruu from rebootRUU --> error signature verify fail --- 12 ---
Is your recovery working?
If so, maybe try flashing a stock GPE ROM.
Sounds like you used a custom "RUU" (maybe the one by graffixnyc) to install GPE the first time.
The same ROM is available as a standalone download (look for a thread by bigxie).
If recovery is not working you may have challenges. Me personally, I would want S-OFF before doing anything else.
Sent from my HTC One using xda app-developers app
My HTC One has all the necessary prerequisites for flashing Roms. I'm not sure how to check s-off though, but I think that's the case. I can flash Roms that do not use Aroma, but if the ROM contains Aroma there is no use. They all freeze at a certain point, I believe around some part that has to do with the System. For example, Maximus HD freezes at 1% when formatting something. Any help would be appreciated. I have looked a lot for the last few days, and can't seem to find an answer.
ronii1123 said:
My HTC One has all the necessary prerequisites for flashing Roms. I'm not sure how to check s-off though, but I think that's the case. I can flash Roms that do not use Aroma, but if the ROM contains Aroma there is no use. They all freeze at a certain point, I believe around some part that has to do with the System. For example, Maximus HD freezes at 1% when formatting something. Any help would be appreciated. I have looked a lot for the last few days, and can't seem to find an answer.
Click to expand...
Click to collapse
Okay so I'm assuming that you're flashing a kk rom here. Are you on the latest recovery and also on a kk base with the latest radios and hboot already on the device? Also make sure you're flashing the right rom for you're device. What device do you have? And also send the link to the rom you're trying to flash just so I can double check that it's correct as if it's freezing at 1% then all I can think that is the problem is you're either trying to flash a kk custom rom on a jb rom without updated firmware and radios or your recovery is out of date or the 3rd reason could simply be you're trying to flash the wrong rom for your phone.
dc959 said:
Okay so I'm assuming that you're flashing a kk rom here. Are you on the latest recovery and also on a kk base with the latest radios and hboot already on the device? Also make sure you're flashing the right rom for you're device. What device do you have? And also send the link to the rom you're trying to flash just so I can double check that it's correct as if it's freezing at 1% then all I can think that is the problem is you're either trying to flash a kk custom rom on a jb rom without updated firmware and radios or your recovery is out of date or the 3rd reason could simply be you're trying to flash the wrong rom for your phone.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2189373
That is the rom, It's Maximus HD. My hboot is 1.54, I'm not sure if my phone has the latest radios, but I have the latest TWRP recovery. 2.8.0.2 I think? I have the HTC One M7 for AT&T., but it says HTC One UL in the same screen I found the hboot. I believe the phone was converted to the GPE edition since it says GOOGL1 on the hboot screen. (I bought this second hand)
EDIT: I just want to add that Android Revolution HD yields the same results, but at 10%. And my phone is currently on a stock build of Sens 6 4.4.3, but the rom before it was GPE.
ronii1123 said:
http://forum.xda-developers.com/showthread.php?t=2189373
That is the rom, It's Maximus HD. My hboot is 1.54, I'm not sure if my phone has the latest radios, but I have the latest TWRP recovery. 2.8.0.2 I think? I have the HTC One M7 for AT&T., but it says HTC One UL in the same screen I found the hboot. I believe the phone was converted to the GPE edition since it says GOOGL1 on the hboot screen. (I bought this second hand)
EDIT: I just want to add that Android Revolution HD yields the same results, but at 10%. And my phone is currently on a stock build of Sens 6 4.4.3, but the rom before it was GPE.
Click to expand...
Click to collapse
If you go into your bootloader you'll see under the **unlocked** message you'll see something that has the phone model and then ship and after ship it will say either s-on or s-off and for the ROM you're trying to flash you have to be s-off thankfully you're on hboot 1.54 so you can use rumrunner to gain s-off if you're not so check that
dc959 said:
If you go into your bootloader you'll see under the **unlocked** message you'll see something that has the phone model and then ship and after ship it will say either s-on or s-off and for the ROM you're trying to flash you have to be s-off thankfully you're on hboot 1.54 so you can use rumrunner to gain s-off if you're not so check that
Click to expand...
Click to collapse
Looks like I am S-Off already. This is strange. It's the only device that has reacted this way to Aroma. I will say that I decide to flash Elemental X today, and that uses Aroma. That worked no problem.
ronii1123 said:
Looks like I am S-Off already. This is strange. It's the only device that has reacted this way to Aroma. I will say that I decide to flash Elemental X today, and that uses Aroma. That worked no problem.
Click to expand...
Click to collapse
Have you checked the md5 of the ROM to make sure that it isn't just a bad download or something which you would just need to re download it again?
dc959 said:
Have you checked the md5 of the ROM to make sure that it isn't just a bad download or something which you would just need to re download it again?
Click to expand...
Click to collapse
Redownloaded, same issue. My CID says CID-GOOGL1, could that be the issue? I heard that the CID is supposed to be something like 1111111 or something like that.
After every attempt, when I restore a backup, I see the text "E: Unable to mount ' /cache' " in red
ronii1123 said:
Redownloaded, same issue. My CID says CID-GOOGL1, could that be the issue? I heard that the CID is supposed to be something like 1111111 or something like that.
Click to expand...
Click to collapse
Yea that's actually what I was just about to say haha I just had to grab the links to the CID's so you can find the one for your phone as it's a converted gpe phone not a factory one which means you simply just need to go to the link I'll post here and find the RUU that is for at&t and the CID will be listed under the download link then you just need to change it.
Link for CID: http://www.htc1guru.com/downloads/ruu-file-downloads/
Once you've found your CID listed in the link which I'll have a look myself to see if I can find it for you but you need to then go into terminal or cmd and type in:
adb reboot bootloader
adb oem writecid CWS__001
fastboot erase cache
fastboot reboot
I changed the code so that it has the correct CID for you so just type in what I've typed there and you'll be back to normal and it should all flash fine
---------- Post added at 05:00 PM ---------- Previous post was at 04:39 PM ----------
ronii1123 said:
Redownloaded, same issue. My CID says CID-GOOGL1, could that be the issue? I heard that the CID is supposed to be something like 1111111 or something like that.
After every attempt, when I restore a backup, I see the text "E: Unable to mount ' /cache' " in red
Click to expand...
Click to collapse
I always receive the red text saying it can't mount cache so don't worry it's not going to stop you from flashing that's just an issue that I have no idea what's causing it but cache is a temporary file anyway so it isn't going to affect installing a ROM well at least it hasn't for me
dc959 said:
Yea that's actually what I was just about to say haha I just had to grab the links to the CID's so you can find the one for your phone as it's a converted gpe phone not a factory one which means you simply just need to go to the link I'll post here and find the RUU that is for at&t and the CID will be listed under the download link then you just need to change it.
Link for CID: http://www.htc1guru.com/downloads/ruu-file-downloads/
Once you've found your CID listed in the link which I'll have a look myself to see if I can find it for you but you need to then go into terminal or cmd and type in:
adb reboot bootloader
adb oem writecid CWS__001
fastboot erase cache
fastboot reboot
I changed the code so that it has the correct CID for you so just type in what I've typed there and you'll be back to normal and it should all flash fine
---------- Post added at 05:00 PM ---------- Previous post was at 04:39 PM ----------
I always receive the red text saying it can't mount cache so don't worry it's not going to stop you from flashing that's just an issue that I have no idea what's causing it but cache is a temporary file anyway so it isn't going to affect installing a ROM well at least it hasn't for me
Click to expand...
Click to collapse
Alright I'll give that a shot, thanks! I'll let you know of my results.
[Q&A] [RUU] Google Edition Conversion. 4.4.2 RUU Zip pre-rooted/non-rooted + Firmwar
Q&A for [RUU] Google Edition Conversion. 4.4.2 RUU Zip pre-rooted/non-rooted + Firmware
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RUU] Google Edition Conversion. 4.4.2 RUU Zip pre-rooted/non-rooted + Firmware. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
s_off question
liam_davenport said:
I had no problem with receiving update with the stock recovery installed
---------- Post added at 10:49 AM ---------- Previous post was at 10:47 AM ----------
Don't go from 4.x.xxx.xx to 5.xx.xxx.xx I've had the firmware bug that bricks you're device, it's a pain have to set up linux and run some commands
Click to expand...
Click to collapse
will the process retain s off? Thanks in advance
crazyandroid said:
will the process retain s off? Thanks in advance
Click to expand...
Click to collapse
the only way your phone can turn back to s-on is if you enter the right command manually "fastboot writesecureflag 3"
S-OFF will never turn back to S-ON by itself
alray said:
the only way your phone can turn back to s-on is if you enter the right command manually "fastboot writesecureflag 3"
S-OFF will never turn back to S-ON by itself
Click to expand...
Click to collapse
Thank you for the quick reply.
running into a problem
First time back with an HTC since the nexus one. so bear with my on the of the HTC exclusive setting, options and what not.
I keep getting an error code "FAILED (remote: 99 unknown fail)" when i try and flash the ROM, I get the error code in the same spot i would get an error the first time I ran the code. this is a different code than what he said I would get. any direction on what i need to change is greatly appreciated!
Here is the code i get --------------------------------
Tanners-MacBook-Pro:Mac Tanner$ ./fastboot flash zip RUU-HTC_One_GE-4.4.2-3.62.1700.1_Rooted.zip
sending 'zip' (514596 KB)...
OKAY [ 20.864s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 21.109s
Tanners-MacBook-Pro:Mac Tanner$
--------------------------------------------------------------
sOther Information:
Build Number 4.18.502.7 CL302626
Baseband Version "Unknown"
HBOOT 1.44
Radio 4A.17.3250.20
That might be a corrupted download. Did you try redownloading it?
I may have actually found the problem. This phone is all sorts of messed up, when i got it, it had a custom ROM, (Which was stuck on the HTC Logo), a CWM recovery, but still S-ON.
I have ran firewater and Revone methods to turn S-Off. The first time i ran it is said successful, but I never bothered to confirm.
I got it working and i was able to grant root access to applications but their were reboots ever 1-2 minutes. so i flashed a new ROM.
now, i have a working ROM (still have the random reboots), SuperSU tells me i need to update my binaries, and i still have S-ON.
I am sure they are all related, and my main goal is to get S-OFF, but i don't know how. i should quit messing around with HTC and just stick with what i know, the Nexus phones.
teport said:
I may have actually found the problem. This phone is all sorts of messed up, when i got it, it had a custom ROM, (Which was stuck on the HTC Logo), a CWM recovery, but still S-ON.
I have ran firewater and Revone methods to turn S-Off. The first time i ran it is said successful, but I never bothered to confirm.
I got it working and i was able to grant root access to applications but their were reboots ever 1-2 minutes. so i flashed a new ROM.
now, i have a working ROM (still have the random reboots), SuperSU tells me i need to update my binaries, and i still have S-ON.
I am sure they are all related, and my main goal is to get S-OFF, but i don't know how. i should quit messing around with HTC and just stick with what i know, the Nexus phones.
Click to expand...
Click to collapse
you indeed need s-off to flash this ruu and you'll (maybe) have to change your cid/mid to match the android-info.txt file packed in that ruu.
Achieving s-off on hboot 1.44 is simple:
flash ARHD 31.6 (this rom is pre-rooted and have the correct unsecured kernel for the s-off exploit to work)
Then follow instructions from Revone thread.
when s-off is acheived, confirm that your cid and mid match the android-info.txt file of the ruu (or change CID/MID so they match)
Flash the ruu in RUU mode:
Code:
fastboot oem rebootRUU
fastboot flash zip name_of_file.zip
fastboot flash zip name_of_file.zip
fastboot reboot
Never s-on and relock bootloader when using GPE
Can I just flash the newest firmware? Or there is a different firmware for gpe?
htc one m7 convert GPE questions.
htc one m7
model pn07100
android 4.3
htc sense 5.0
hboot 1.55
unlocked
I want to convert my m7 to a GPE. before i do anything to my phone ,I have a few questions to ask...
i want to install the RUU-HTC_One_GE-4.4-3.62.1700.1.zip rom (non rooted) http://forum.xda-developers.com/showthread.php?t=2358781
- does that mean i dont need to root my phone if im flashing the non rooted rom?
- my device is unlocked but in the bootloader is says that its locked in the menu. does that mean i still have to unlock the bootloader? is there a difference between having an unlocked phone and having an unlocked bootloader?
- do i need to install sync manager and install drivers for my phone?
- will i be able to receive updates from google OTA? do i need to flash stock recovery in order to receive OTA updates from google?
- how would i back up my stock rom (android 4.1.2 w/ htc sense 5.0) if i decide to go back.
- after the flash will i have to re-install all my apps?
thanks.
S-off mandatory
Hello, is absolutely essential s-off? If the device is only unlocked bootloader via HTCdev? The procedure will fail completely?
duzera said:
Hello, is absolutely essential s-off? If the device is only unlocked bootloader via HTCdev? The procedure will fail completely?
Click to expand...
Click to collapse
are you asking seriously or....?
Prerequisites
S-Off, <--------
ADB knowledge
Fastboot knowledge
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=43459658&postcount=1
i installed the google play edition for htc one m7 4.4.2 rom. how do i add/remove panels? i dont see any personalize settings in the menu? i've tried a search and no results.
graphic glitches
I have successfully converted my phone to GPE4.4.2 using the exact methods. There is no problem with that. Problem started once I did an OTA to update it with 4.4.3 where there are graphic glitches on the status bar and the bottom part of the screen. Also the power off panel won't appear after pressing (holding) the power button. Anyone suffered this? any solutions?
Edited : Problem solved by changing phone's CID. I can't change the RUU android-info's CID because the glitch would be there as the OTA's CID is GOOGL001.
Sprint?
Hey guys, does this RUU work with Sprint yet?
when upgrade to lollipop
have this problem: mount failed to mount /dev/block/mmcblk0p037 at /data device or resource busy
how to solve it ?
in 4.4.4, stuck recovery, unrooted
It doesn't affect anything. Just let it keep going. The update takes a while because it is using the older patch method.
recovery
where can I find stock recovery for gpe rom 4.4.4/4.9.1700.1 thanks in advance
I get this too but I get FAILED (remote: 42 custom id check fail) when I reboot it just reboots back into cyanogenmod11
Cillian.K said:
I get this too but I get FAILED (remote: 42 custom id check fail) when I reboot it just reboots back into cyanogenmod11
Click to expand...
Click to collapse
wrong cid make sure your cid is compatible with the ruu