So I've run into a problem with my new Htc First phone, the wifi doesnt locate any access points.
Its unlocked,rooted and S-off-ed.
I can unroot and lock the bootloader but does anyone know how to S-on it?
Yea, you just have to ruu first and then follow this guide.
http://androidforums.com/internatio...-return-100-stock-revone-moonshine-s-off.html
Kendosis said:
Yea, you just have to ruu first and then follow this guide.
http://androidforums.com/internatio...-return-100-stock-revone-moonshine-s-off.html
Click to expand...
Click to collapse
Thanks!
Btw is there any known wifi problem with the First? Mine just came from america yesterday and the phone wasn't locating any access points. I thought rooting it and flashing another ROM might work for it but unfortunately it didnt
Actually I'm also having trouble flashing stock unrooted rom , could you point me in the right direction?
http://www.androidruu.com/index.php?developer=Myst
Which one should I flash?
dramon said:
Thanks!
Btw is there any known wifi problem with the First? Mine just came from america yesterday and the phone wasn't locating any access points. I thought rooting it and flashing another ROM might work for it but unfortunately it didnt
Actually I'm also having trouble flashing stock unrooted rom , could you point me in the right direction?
http://www.androidruu.com/index.php?developer=Myst
Which one should I flash?
Click to expand...
Click to collapse
You usually have to run a factory reset, cache/dalvik cache wipe before you flash roms. I get that wifi problem sometimes when trying to flash a rom before wiping.
dramon said:
Thanks!
Btw is there any known wifi problem with the First? Mine just came from america yesterday and the phone wasn't locating any access points. I thought rooting it and flashing another ROM might work for it but unfortunately it didnt
Actually I'm also having trouble flashing stock unrooted rom , could you point me in the right direction?
http://www.androidruu.com/index.php?developer=Myst
Which one should I flash?
Click to expand...
Click to collapse
DUDE QUICK THING ! you can't flash any roms in till you RELOCK THE BOOTLOADER ! I know it sounds weird but trust me you will keep the S-off status (assuming you have s-off) and everything works fine, I couldn't flash any roms in till I relocked and I heard others have this problem too.
Now the WiFi problem, if factory resetting doesn't work, try flashing the stock rooted ROM around these threads, if that doesn't work try JMZ's kernel, and if that doesn't work then you have a hardware problem, good luck.
Sent from my HTC first
If he just RUU's it he won't have to worry about relocking his boot loader, he should just use titainium backup and ruu to save time.
Kendosis said:
If he just RUU's it he won't have to worry about relocking his boot loader, he should just use titainium backup and ruu to save time.
Click to expand...
Click to collapse
Trust me I've tried RUU and even that didn't work for me, in till I relocked , it was weird but its worth a shot since relocking keeps the s-off anyways
Sent from my HTC first
SneakyGuyDavid said:
Trust me I've tried RUU and even that didn't work for me, in till I relocked , it was weird but its worth a shot since relocking keeps the s-off anyways
Sent from my HTC first
Click to expand...
Click to collapse
I've tried it many times already it works, after you ruu it you just have to turn s-on before you try to unlock the boot loader again otherwise you'll get bootloop.
Kendosis said:
I've tried it many times already it works, after you ruu it you just have to turn s-on before you try to unlock the boot loader again otherwise you'll get bootloop.
Click to expand...
Click to collapse
guys guys, you've lost me.
All I need to do is wipe away all traces of my rooting and bootloader unlocking etc as I'm returning it for warranty.
Now my First is rooted, custom recovery and s-off and unlocked .
I want it unrooted, s-on and boot loader locked.
Someone please guide me through the steps :/
btw im not a n00b, but this is my first HTC phone so I'm not too familiar with these ruu's and s-offs
dramon said:
guys guys, you've lost me.
All I need to do is wipe away all traces of my rooting and bootloader unlocking etc as I'm returning it for warranty.
Now my First is rooted, custom recovery and s-off and unlocked .
I want it unrooted, s-on and boot loader locked.
Someone please guide me through the steps :/
btw im not a n00b, but this is my first HTC phone so I'm not too familiar with these ruu's and s-offs
Click to expand...
Click to collapse
Step 1. RUU your device
Step 2. After it reboots when it's done ruu'ing just start it and go through the set up.
Step 3. Turn on USB debugging mode.
Step 4. Turn on CMD on your PC then just follow the commands below
adb devices
adb reboot bootloader
fastboot devices
fastboot oem writecid xxxxxxxx (where xxxxxxxx is your stock CID.) Mines is CWS__001 on the HTC first I'm not sure if it's the same on all devices just check to see if yours it the same, if it is just use fastboot oem writecid CWS__001
fastboot reboot-bootloader
fastboot getvar cid (It should say CWS__001 if that is your cid.)
fastboot oem writesecureflag 3
fastboot reboot-bootloader
*verify you are locked s-on
fastboot reboot
And that's it, it is a extremely simple process lol, I've done it at least 20 times since I tend to ruu my device a lot off of S-OFF, when messing around with different roms.
http://forum.xda-developers.com/showthread.php?t=841890
So its okay if I flash the ruu by the second method as in this thread?
And will custom recovery be overwritten with stock recovery?
OK Update!
I was well on my way to relock,s-on my phone etc and here's what happened
@Kendosis
@SneakyGuyDavid
1) Sucessfully RUU'd
As it happened I didnt have my sim inserted and when I rebooted, the wifi was working! When I inserted the sim the wifi stopped working. I did some bit of research and it turns out it has something to do with wifi country codes. Apparently it can be fixed by this app
https://play.google.com/store/apps/details?id=com.fardjad.android.wifixmanager
2) Since the app required root, I was going to get root again.
(Flashing RUU gave me bootloader locked)
I unlocked and then flashed CWM
3) Since I had no roms on my phone storage and the CWM doesnt mount storage, I had to sideload the ROMS.
4) No matter which roms I flashed, I was stuck in a bootloop. I relocked and tried flashing again but I was again stuck in a bootloop. CWM works fine though.
Current status: Bootloader Locked, S-off.
What do I do to fix this bootloop :/
@dramon
I told you to s-on after you ruu first otherwise you get boot loop lol.
Now RUU again and right after don't install nothing just start up the phone and turn usb debugging on and follow the steps to S-ON.
Kendosis said:
@dramon
I told you to s-on after you ruu first otherwise you get boot loop lol.
Now RUU again and right after don't install nothing just start up the phone and turn usb debugging on and follow the steps to S-ON.
Click to expand...
Click to collapse
also sideload sucks ass, if you flash TWRP then you can run adb from it and use adb push, so in cmd you would run " adb push
ROMZIPNAME.ZIP /sdcard "
Thanks guys, I now have an idea of how the rooting and unlocking works for HTC (Y)
Related
I was trying to obtain S-off through Juopunut Bear, but after it finds my device and tries to reboot it into its program, it simply doesn't reboot. The phone then will not start at all unless I pull the battery and boot into Hboot. From there I flashed my backup img through fastboot and I was good. I found this thread that said I need to ICS 3.32 firmware. On my phone I noticed I am on Software number 3.26.502.56, so I tried to flash the provided download of 3.32 using fastboot. And it did the same exact thing! Would not reboot, and had to battery-pull and re-flash my backup to get it to work.
What is my problem here?
I am on a unlocked and rooted HTC Vivid running stock ICS and stock Kernel.
I really hope I am not committing a stupid error and wasting everyone's time, but it is possible. Thanks in advance for any help!
lonehunter65 said:
I was trying to obtain S-off through Juopunut Bear, but after it finds my device and tries to reboot it into its program, it simply doesn't reboot. The phone then will not start at all unless I pull the battery and boot into Hboot. From there I flashed my backup img through fastboot and I was good. I found this thread that said I need to ICS 3.32 firmware. On my phone I noticed I am on Software number 3.26.502.56, so I tried to flash the provided download of 3.32 using fastboot. And it did the same exact thing! Would not reboot, and had to battery-pull and re-flash my backup to get it to work.
What is my problem here?
I am on a unlocked and rooted HTC Vivid running stock ICS and stock Kernel.
I really hope I am not committing a stupid error and wasting everyone's time, but it is possible. Thanks in advance for any help!
Click to expand...
Click to collapse
If you can get hboot relock the bootloader and run the stock ruu file seems to work for ant errors I've ever gotten , then just go back and redo every thing but s off it should stay off .
Bigtjmc said:
If you can get hboot relock the bootloader and run the stock ruu file seems to work for ant errors I've ever gotten , then just go back and redo every thing but s off it should stay off .
Click to expand...
Click to collapse
Not sure I'm completely understanding you. I need to relock and run stock ruu, then redo everything except s-off? That kind of defeats the purpose, I am trying to s-off
lonehunter65 said:
Not sure I'm completely understanding you. I need to relock and run stock ruu, then redo everything except s-off? That kind of defeats the purpose, I am trying to s-off
Click to expand...
Click to collapse
Yes if you are having problems after any mod to the os just relock the bootloader and run the stock ruu file and it will fix the issue , then go back after you got the phone working right and then unlock the bootloader , flash recovery , root , ect .
But the s-off should stay off and you won't have to redo that step .
So basically you will be on a stock ics with s-off
Then just redo the process to get it where you want it .
Bigtjmc said:
Yes if you are having problems after any mod to the os just relock the bootloader and run the stock ruu file and it will fix the issue , then go back after you got the phone working right and then unlock the bootloader , flash recovery , root , ect .
But the s-off should stay off and you won't have to redo that step .
So basically you will be on a stock ics with s-off
Then just redo the process to get it where you want it .
Click to expand...
Click to collapse
I'm sorry but this just doesn't make sense, the phone is automatically S-On not S-Off, so it won't 'stay s-off'. You understand what I mean?
lonehunter65 said:
I'm sorry but this just doesn't make sense, the phone is automatically S-On not S-Off, so it won't 'stay s-off'. You understand what I mean?
Click to expand...
Click to collapse
did you succeed s-off ?
if you did the s-off procedure via " wire trick " was successful the relocking the boot loader will not change the s-off it will stay off ,
Then relock. Run ruu now you are stock ics with the s-off still , and all the errors should be fixed .
Then just re unlock bl , flash recovery , root , flash New custom Rom / kernel, ect.
All I'm saying is if you have s-off then your good ,
To fix all the errors run the ruu , only reason you need to relock bl is the ruu will reject the install if you are unlocked .
Bigtjmc said:
did you succeed s-off ?
if you did the s-off procedure via " wire trick " was successful the relocking the boot loader will not change the s-off it will stay off ,
Then relock. Run ruu now you are stock ics with the s-off still , and all the errors should be fixed .
Then just re unlock bl , flash recovery , root , flash New custom Rom / kernel, ect.
All I'm saying is if you have s-off then your good ,
To fix all the errors run the ruu , only reason you need to relock bl is the ruu will reject the install if you are unlocked .
Click to expand...
Click to collapse
Oh, we are talking past each other. I did not succeed s-off, when it reboots my phone via Control Bear it does not boot into the Juopunut program, and I have never had a chance to do the wire trick! Thanks for the help though.
lonehunter65 said:
Oh, we are talking past each other. I did not succeed s-off, when it reboots my phone via Control Bear it does not boot into the Juopunut program, and I have never had a chance to do the wire trick! Thanks for the help though.
Click to expand...
Click to collapse
I had trouble on my first S-OFF attempt. I had made a mistake (I missed one of the S-OFF prep steps in section 2 of the SuperGuide, which is at http://forum.xda-developers.com/showthread.php?t=1416836 ).
If you want to try again?
-If you have relocked your bootloader, flash your phone stock using your appropriate RUU while phone is in Fastboot mode.
*** If you haven't relocked bootloader yet, you can do it first via fastboot ("fastboot oem lock")
-Start at section 1 of the superguide (unlocking the bootloader, yeah it sucks to do the process again but thankfully htc makes it easy!)
-And then you can try S-OFF process again (section 2 in superguide)
I know this is for the Vivid but I have the same problem with my EVO 3D. And Can get any help from anyone over there. I just relocked the evo but dont know the next step. Can anybody help me here?
gaarak54 said:
I know this is for the Vivid but I have the same problem with my EVO 3D. And Can get any help from anyone over there. I just relocked the evo but dont know the next step. Can anybody help me here?
Click to expand...
Click to collapse
Download the ruu from HTC or you should be able to download it from the EVO 3d forum while in fastboot mode hook you phone up to your computer fastboot should change to fastbootusb then double click on the ruu and let it do its thing do not unplug till it is finished then you will be out of box stock
Sent from my HTC PH39100 using Tapatalk 2
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)
So my problem is the further, I had a fully working HTC first with the latest Hboot update previously moonshined with the old one. So I had S-off, root, JMZ's custom kernel and an unlocked bootloader but then after a while I've done alot of flashes, zip installs tweaks and modifications that created pesky problems that wouldn't go away with a simple wipe in CWM. That's okay though I could just do a complete restore with the RUU. And i did, no I didn't re-lock the bootloader because I had S-off anyways. Everything came out great. But then I went ahead and the problems started to happen.. After unlocking the bootloader I had an eternal bootloop that wouldn't go away, but did a simple re-lock and booted up just fine.
My question is what the hell am I doing wrong? does it have to do with the version of RUU im using?
abrahammmmmmm_ said:
So my problem is the further, I had a fully working HTC first with the latest Hboot update previously moonshined with the old one. So I had S-off, root, JMZ's custom kernel and an unlocked bootloader but then after a while I've done alot of flashes, zip installs tweaks and modifications that created pesky problems that wouldn't go away with a simple wipe in CWM. That's okay though I could just do a complete restore with the RUU. And i did, no I didn't re-lock the bootloader because I had S-off anyways. Everything came out great. But then I went ahead and the problems started to happen.. After unlocking the bootloader I had an eternal bootloop that wouldn't go away, but did a simple re-lock and booted up just fine.
My question is what the hell am I doing wrong? does it have to do with the version of RUU im using?
Click to expand...
Click to collapse
You got to turn S-ON after you RUU a previously S-OFF'd device.
Kendosis said:
You got to turn S-ON after you RUU a previously S-OFF'd device.
Click to expand...
Click to collapse
Wow, well I was completely unaware of that. Sorry for the noob question but how would i go about in doing that?
abrahammmmmmm_ said:
Wow, well I was completely unaware of that. Sorry for the noob question but how would i go about in doing that?
Click to expand...
Click to collapse
http://androidforums.com/internatio...-return-100-stock-revone-moonshine-s-off.html
Kendosis said:
http://androidforums.com/internatio...-return-100-stock-revone-moonshine-s-off.html
Click to expand...
Click to collapse
Thanks! One question: what's the stock cid number for the RUU the first has? I now have S-on but when I tried to run the RUU again to see if everything was working I got error 131 which shows when there's a CID mismatch. The CID I used was cws__001. I have the first with a t-mobile simcard by the way if that changes anything
abrahammmmmmm_ said:
Thanks! One question: what's the stock cid number for the RUU the first has? I now have S-on but when I tried to run the RUU again to see if everything was working I got error 131 which shows when there's a CID mismatch. The CID I used was cws__001. I have the first with a t-mobile simcard by the way if that changes anything
Click to expand...
Click to collapse
Try a different version of the ruu, there's two iirc. Try version 1.08.502.1 if that doesn't work try the next version.
Kendosis said:
Try a different version of the ruu, there's two iirc. Try version 1.08.502.1 if that doesn't work try the next version.
Click to expand...
Click to collapse
I tried both and it's a no go. Pretty sure it has to do with me changing the cid number on without knowing to the one I said earlier. But I guess if I would ever want to run the ruu I'd have to s-off it first and do it the long way then but at least I can successfully unlock the boot loader now with no problems, or at least I think. (Haven't tried it yet)
Edit:
Problem solved I unlocked the bootloader once more moonshined and set a supercid on the phone
my htc one is stuck in the bootloader with the tampered banner on it, RELOCKED bootloader and also s-on. I have a viper one ROM on it an a twrp custom recovery.. now funny story I guarantee you will laugh. I knew the htc oem update was coming soon so I could get lollipop but I was rooted and couldn't do it. So I was trying to get s-off on my device but I missed a step on some gadget hacks tutorial and locked the bootloader (thats the funny part) then I tried unlocking it again but it didn't work. I tried going into recovery but it just rebooted back to the bootloader. I tried everything in the bootloader options and nothing worked.
my Hboot is version 1.57 and my OS is 6. 10.531.9
I tried flashing a recovery again and I cant do it it says "error cannot load--" and the same with the Unlock_code.bin it just wasn't working? what am I doing wrong and how can i fix it. please its urgent
if you have any answers you can comment here and also e-mail me at [email protected] (I would usually say text me :crying: ) once again please help I don't know what to do next.
kage_outram said:
my htc one is stuck in the bootloader with the tampered banner on it, RELOCKED bootloader and also s-on. I have a viper one ROM on it an a twrp custom recovery.. now funny story I guarantee you will laugh.
I knew the htc oem update was coming soon so I could get lollipop but I was rooted and couldn't do it. So I was trying to get s-off on my device but I missed a step on some gadget hacks tutorial and locked the bootloader (thats the funny part) then I tried unlocking it again but it didn't work. I tried going into recovery but it just rebooted back to the bootloader. I tried everything in the bootloader options and nothing worked.
my Hboot is version 1.57 and my OS is 6. 10.531.9
I tried flashing a recovery again and I cant do it it says "error cannot load--" and the same with the Unlock_code.bin it just wasn't working? what am I doing wrong and how can i fix it. please its urgent
if you have any answers you can comment here and also e-mail me at [email protected] (I would usually say text me :crying: ) once again please help I don't know what to do next.
Click to expand...
Click to collapse
Since, you are S-ON with a locked bootloader run this RUU 6.10.531.10. It will put you back at stock, then you can try to unlock you bootloader. To get S-OFF you will need to use Sunshine with your hboot 1.57.
majmoz said:
Since, you are S-ON with a locked bootloader run this RUU 6.10.531.10. It will put you back at stock, then you can try to unlock you bootloader. To get S-OFF you will need to use Sunshine with your hboot 1.57.
Click to expand...
Click to collapse
What commands do I put in to add the RUU
kage_outram said:
What commands do I put in to add the RUU
Click to expand...
Click to collapse
Download the RUU to your Windows computer
Connect the phone to the computer via USB
Boot into Bootloader/FASTBOOT USB on your phone
Double-click the RUU on your computer
majmoz said:
Download the RUU to your Windows computer
Connect the phone to the computer via USB
Boot into Bootloader/FASTBOOT USB on your phone
Double-click the RUU on your computer
Click to expand...
Click to collapse
what should happen next