Related
Is there any way for me to downgrade my ISC to GB?
Flash the GB ROM and corresponding kernel of your choice. You just can't go back to the old hboot... but can still flash GB ROMS on the new hboot.
Sent from my HTC PH39100 using xda premium
Thanks for the help but I do not have my phone rooted right now. I've been trying for like the past hours with the all in one kit from hasooon, but I cannot seem to get it to work. I have unlocked my bootloader already. Would that be the reason why?
GlowingStar said:
Thanks for the help but I do not have my phone rooted right now. I've been trying for like the past hours with the all in one kit from hasooon, but I cannot seem to get it to work. I have unlocked my bootloader already. Would that be the reason why?
Click to expand...
Click to collapse
Could be. I'm pretty sure you need to relock your bootloader before running the RUU...
Is there a way to relock my bootloader? Also, I was trying from your superguide eariler but I just got super confused. If you could help me, that would be great.
I actually have ICS updated from GB today with the new AT&T. Now that I've updated my OS, I have no idea how to root my phone anymore because there are only posts for 2.3.4 GB. I've actually tried the permroot from hasoon, but I can't seem to get that to work.
Well, to relock the bootloader, you can either use hasoon2000's Vivid All-In-One Toolkit, which has pretty much everything you need to relock the bootloader.
Otherwise, you boot into the bootloader and into fastboot, and follow the steps for relocking the bootloader in part 6 of the Superguide.
altanimi said:
Well, to relock the bootloader, you can either use hasoon2000's Vivid All-In-One Toolkit, which has pretty much everything you need to relock the bootloader.
Otherwise, you boot into the bootloader and into fastboot, and follow the steps for relocking the bootloader in part 6 of the Superguide.
Click to expand...
Click to collapse
I actually have a question. I can't boot into bootloader by holding down power and down volume...
Successfully relocked my bootloader. Many thanks!
Okay now to root my phone. Could you tell me the exact steps to do it? I am having a lot of trouble. I run it with debugging USB on, it will then restart my phone, first it will appear something like a circle with a down arrow inside it. Afterwards, there will be a triangle icon that's red with another arrow. On the Command, it will say device not found for all files then press any key.
Appreciate your help!
GlowingStar said:
Successfully relocked my bootloader. Many thanks!
Okay now to root my phone. Could you tell me the exact steps to do it? I am having a lot of trouble. I run it with debugging USB on, it will then restart my phone, first it will appear something like a circle with a down arrow inside it. Afterwards, there will be a triangle icon that's red with another arrow. On the Command, it will say device not found for all files then press any key.
Appreciate your help!
Click to expand...
Click to collapse
You need to unlock your bootloader once again. Then root it. Use the All-In-One toolkit, it will be much easier.
unlock bootloader > then flash the wcx recovery and that should root it.
slapshot30 said:
You need to unlock your bootloader once again. Then root it. Use the All-In-One toolkit, it will be much easier.
unlock bootloader > then flash the wcx recovery and that should root it.
Click to expand...
Click to collapse
So all I need to do is unlock bootloader once again, flash the wcx recovery, then I'll be good to go. I think the reason is because I flashed the first CMW recovery. That may be the reason.
Thanks for your help
GlowingStar said:
So all I need to do is unlock bootloader once again, flash the wcx recovery, then I'll be good to go. I think the reason is because I flashed the first CMW recovery. That may be the reason.
Thanks for your help
Click to expand...
Click to collapse
Yea, the CWM is a bad idea on the Vivid. Wildchild did a very good job with his WCX recovery. Just unlock your phone again, then click the flash WCX recovery. Wildchild made his recovery so that when flashed, it would automatically give root.
slapshot30 said:
Yea, the CWM is a bad idea on the Vivid. Wildchild did a very good job with his WCX recovery. Just unlock your phone again, then click the flash WCX recovery. Wildchild made his recovery so that when flashed, it would automatically give root.
Click to expand...
Click to collapse
I actually downgraded my phone from ICS to GB. I rooted my phone with zergrush. With my phone unlocked, now it went from temproot, to permroot. I am actually trying to find a rom for my phone that I can play around with without getting bored. I want to just leave it as S-On instead of off. Hope you can help with a little bit with that.
I am having an issue that I have not seen before and could not find any resolve thru XDA or Google. I am attempting to restore the 64G Developer Edition with the RUU from HTC Dev and I keep getting the 155 error. I even have attempted to install thru CWM the .zip. Still no avail.
I am currently rooted, and have CWM installed. The device is obviously Bootloader unlock. What I was able to find is that it possibly could be a issue that it is bootloader unlocked as some posts suggest to have you bootloader locked to install RUU, but that is obviosely not a posibility with the dev ed.
So what am I doing wrong, or what is the issue. I have confirmed that I was using the correct RUU.
Help Appreciated
UPDATE
Ok, I figured out how to avoid the RUU 155 error. It seems that HTC for some dumb reason, although for a unlocked developer edition, we still have to lock the bootloader to utilize the RUU. Here are the steps I have done.
Although it is straight forward and easy to do, issues could always arise. I do not take any responsibility if things go wrong. Educate yourself first before attempting anything. If you do not know what you are doing, then don't do it.
Before Starting.
Make sure you have the latest HTC Drivers. You can use hasoon2000 HTC All-In-One Toolkit to complete that. That can be found at HTC One All-In-One Toolkit
Get the appropriate RUU from HTC Dev
1. Lock your bootloader through by booting into hoot and then going into fastboot and issuing the command fasboot oem lock.
2. Once locked, reboot your system.
3. Open RUU and follow onscreen instructions.
Notice, this will delete all of the files on the system so do this on your own cognition
4. Let the RUU do its thing. If you get an error during the process, such as 152, simply try again. I had it happen once. The phone was stuck on the black HTC screen with four triangles with exclamation points in each corner. If this happens you will not be able to reboot your phone. Simply relaunch RUU and it should reinstall it. If you get error 155 again, then you have not re-locked your bootloader.
3.Once you have successfully reinstalled the rom, you have to register with the HTC Dev to re-unlock your bootloader if that is what you want. The easiest to do this I found was by using the HTC One All-In-One Toolkit. It is a great tool and will help you with majority of things that I have mentioned above, including locking your bootloader. Follow the steps on the toolkit and you'll be all set. The Toolkit can be found here HTC One All-In-One Toolkit
If you found this helpful, click thanks. Also hit thanks to hasoon2000 for creating the toolkit.
Gotta re lock your bootloader
fastboot oem lock
I got relock it even though it came unlocked? How would I unlock it again since I don't have the tokens from HTC development, or is the ruu gonna do that by itself.
Sent from my HTC One using Tapatalk 2
I was having same issues as OP. After using the lock command, the update got longer. The black HTC screen even got as far as a progress bar. Well I now got ERROR 152 saying I should get the correct RUU. I am sure I have the right one, because there is only ONE developer edition RUU file from htcdev.com
Problem now is, I have the black HTC screen with warning signs on each corner.
One thing I saw on a video is you are supposed to restore to the same version? I had updated OTA Z(1.29.1540.16) to the latest which I cant get an RUU for. The RUU available is 1.29.1540.3 no other available. What do I do now? HTC One Dev Edition stuck on black screen with warning signs on all corners.
All I can see now is a scren that says:
***TAMPERED***
***RELOCKED***
bunch of numbers and letters in green and
RUU in orange
schn1tt3r said:
I was having same issues as OP. After using the lock command, the update got longer. The black HTC screen even got as far as a progress bar. Well I now got ERROR 152 saying I should get the correct RUU. I am sure I have the right one, because there is only ONE developer edition RUU file from htcdev.com
Problem now is, I have the black HTC screen with warning signs on each corner.
One thing I saw on a video is you are supposed to restore to the same version? I had updated OTA to the latest which I cant get an RUU for. What do I do now? HTC One Dev Edition stuck on black screen with warning signs on all corners.
Click to expand...
Click to collapse
When I was doing it, the first time I got the 152 error. I simply just redid it and it accepted it on the second try. Trying relaunching RUU that you have and try the install again. That's at least how it worked with me.
Bosnazmaj said:
When I was doing it, the first time I got the 152 error. I simply just redid it and it accepted it on the second try. Trying relaunching RUU that you have and try the install again. That's at least how it worked with me.
Click to expand...
Click to collapse
Did you get that black HTC screen with warning signs on each corner? I am re-running the RUU, hope it works or I just lost $650.
EDIT: You used RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.exe right? Were you already OTA updated? I wonder why htcdev web says BrightstarUS for the dev edition instead of something else...
EDIT2: Its on that black screen with loading thing again... still exclamation marks on every corner... hope this works or else it won't be a nice first experience with Android coming from iOS lol and I've jailbroken and tinkered on those devices for so long.
---------- Post added at 08:31 PM ---------- Previous post was at 08:21 PM ----------
Yeah 2nd attempt the same error 152. I just lost $650 right?
The green bar goes all the way to the end, it sends it all, but it doesnt reboot. It just gets error. What else can I try? Device isnt even 3 days old.
Did it a third time, after Updating Radio, thats where the error appears.
schn1tt3r said:
Did you get that black HTC screen with warning signs on each corner? I am re-running the RUU, hope it works or I just lost $650.
EDIT: You used RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.exe right? Were you already OTA updated? I wonder why htcdev web says BrightstarUS for the dev edition instead of something else...
EDIT2: Its on that black screen with loading thing again... still exclamation marks on every corner... hope this works or else it won't be a nice first experience with Android coming from iOS lol and I've jailbroken and tinkered on those devices for so long.
---------- Post added at 08:31 PM ---------- Previous post was at 08:21 PM ----------
Yeah 2nd attempt the same error 152. I just lost $650 right?
The green bar goes all the way to the end, it sends it all, but it doesnt reboot. It just gets error. What else can I try? Device isnt even 3 days old.
Did it a third time, after Updating Radio, thats where the error appears.
Click to expand...
Click to collapse
What was the software version that it came with. Was it with the most recent one? I think 1.29.401.16 one?
Bosnazmaj said:
What was the software version that it came with. Was it with the most recent one? I think 1.29.401.16 one?
Click to expand...
Click to collapse
It came with the .3 and I did OTA to .16
The RUU you can get online from their web is only .3
===============================
Ok so... that black HTC screen accepts "fastboot" commands.
I downloaded the .ZIP version of the Developer Edition OS.
I went in command prompt, I typed
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip PN07IMG_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.zip
****GOT AN ERROR*****
Code:
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
.... so again:
fastboot flash zip PN07IMG_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.zip
10 minutes later
fastboot reboot
Oh my was I happy to see the white HTC Startup.
I also have same phone de it shouldnt be tamperd relocked it should be only relocked
Sent from my HTC One using xda app-developers app
I find it funny now far Computer OS's have come and yet we always have to go back to good old DOS Command Prompt to fix things.
BTW, my phone now has bootloader RELOCKED due to the fastboot oem lock command, should I send the phone back just like that or unlock bootloader before sending it back?
I guess to Unlock bootloader again, I have to follow same instructions as if it were an AT&T version right? Did you UNLOCK yours again OP?
U sending it back to HTC?
Sent from my HTC One using Tapatalk 2
Bosnazmaj said:
U sending it back to HTC?
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Yes, that is the reason I was doing all this restoring. I had ROOTed it to install AdAway. Ads is the only major drawback when compared to iOS (this is my first Android). When you see a gray image on my phone, there are 3 sort of water drops. Like between the touch screen and LCD.
Well, I am exchanging it actually. I like the HTC One a lot. It has a tiny gap, but I dont care about that much, the weird discoloration on the sceen, though, I do mind.
That makes sense.
Sent from my HTC One using Tapatalk 2
Bosnazmaj said:
I am having an issue that I have not seen before and could not find any resolve thru XDA or Google. I am attempting to restore the 64G Developer Edition with the RUU from HTC Dev and I keep getting the 155 error. I even have attempted to install thru CWM the .zip. Still no avail.
I am currently rooted, and have CWM installed. The device is obviously Bootloader unlock. What I was able to find is that it possibly could be a issue that it is bootloader unlocked as some posts suggest to have you bootloader locked to install RUU, but that is obviosely not a posibility with the dev ed.
So what am I doing wrong, or what is the issue. I have confirmed that I was using the correct RUU.
Help Appreciated
UPDATE
Ok, I figured out how to avoid the RUU 155 error. It seems that HTC for some dumb reason, although for a unlocked developer edition, we still have to lock the bootloader to utilize the RUU. Here are the steps I have done.
Although it is straight forward and easy to do, issues could always arise. I do not take any responsibility if things go wrong. Educate yourself first before attempting anything. If you do not know what you are doing, then don't do it.
Before Starting.
Make sure you have the latest HTC Drivers. You can use hasoon2000 HTC All-In-One Toolkit to complete that. That can be found at HTC One All-In-One Toolkit
Get the appropriate RUU from HTC Dev
1. Lock your bootloader through by booting into hoot and then going into fastboot and issuing the command fasboot oem lock.
2. Once locked, reboot your system.
3. Open RUU and follow onscreen instructions.
Notice, this will delete all of the files on the system so do this on your own cognition
4. Let the RUU do its thing. If you get an error during the process, such as 152, simply try again. I had it happen once. The phone was stuck on the black HTC screen with four triangles with exclamation points in each corner. If this happens you will not be able to reboot your phone. Simply relaunch RUU and it should reinstall it. If you get error 155 again, then you have not re-locked your bootloader.
3.Once you have successfully reinstalled the rom, you have to register with the HTC Dev to re-unlock your bootloader if that is what you want. The easiest to do this I found was by using the HTC One All-In-One Toolkit. It is a great tool and will help you with majority of things that I have mentioned above, including locking your bootloader. Follow the steps on the toolkit and you'll be all set. The Toolkit can be found here HTC One All-In-One Toolkit
If you found this helpful, click thanks. Also hit thanks to hasoon2000 for creating the toolkit.
Click to expand...
Click to collapse
Thank you. This was very helpful.
Glad I could help
Sent from my HTC One using Tapatalk 2
schn1tt3r said:
It came with the .3 and I did OTA to .16
The RUU you can get online from their web is only .3
===============================
Ok so... that black HTC screen accepts "fastboot" commands.
I downloaded the .ZIP version of the Developer Edition OS.
I went in command prompt, I typed
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip PN07IMG_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.zip
****GOT AN ERROR*****
Code:
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
.... so again:
fastboot flash zip PN07IMG_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.zip
10 minutes later
fastboot reboot
Oh my was I happy to see the white HTC Startup.
Click to expand...
Click to collapse
THANK YOU MAN!!!!!!!! You just saved me. I had the same problem except I had OTA .17 and trying to flash .16. My device was all jacked up but it's back to original.
Bosnazmaj said:
I am having an issue that I have not seen before and could not find any resolve thru XDA or Google. I am attempting to restore the 64G Developer Edition with the RUU from HTC Dev and I keep getting the 155 error. I even have attempted to install thru CWM the .zip. Still no avail.
I am currently rooted, and have CWM installed. The device is obviously Bootloader unlock. What I was able to find is that it possibly could be a issue that it is bootloader unlocked as some posts suggest to have you bootloader locked to install RUU, but that is obviosely not a posibility with the dev ed.
So what am I doing wrong, or what is the issue. I have confirmed that I was using the correct RUU.
Help Appreciated
.........
Click to expand...
Click to collapse
Bosnazmaj - thank you for this wonderful write-up & knowledge. I have a Dev edition myself. Sometime ago, I got into charging issues. Initially, assuming it to be software issues, I thought I'd run the RUU. So, like you, I too figured out that I have to lock my bootloader. Ran the RUU....long story short, found out that I have to give my phone for repairs (turned out to be a hardware issue).
So, the point I am trying to make is that, if we unlock the bootloader, certain apps (like flashlight, sound recorder etc) seems to get deleted. While this, on it's own, might not sound too alarming....the problem is, if these apps are not present, then the OTA does not & will not get applied as the OTA says that these apps have to be present. I am not sure how to unlock the bootloader without losing any apps.
Any knowledge / information on this is MOST appreciated.
Actually I used titanium backup to back those apps that disappear during root before I unlocked anything. Then once I rooted and unlocked I just restored them back with titanium and all was fine. But in reality you don't want to so an ota when you are rooted as you might loose root.
Sent from my HTC One using Tapatalk 2
Can't you re-unlock the phone using following command without going through the HTCDev website mess?
Code:
fastboot oem unlock
Just a heads up. I was able to return to stock using the RUU without locking the bootloader. It took a while to figure it out.
I went from ARHD 31 to A stock rom (m7_stock_dev_1.29.1540.16_signed_052313.zip) found on an old thread, also had to find a stock recovery that would work (i think it was the one liked in the ARHD thread) and used the revone S-off method, then applied the latest RUU from the htc dev site .and it installed and the bootloader remained unlocked.
I had to get this thing ready for someone who bought it. They asked if i could return it to stock with S-off. It was a pain in the but, but got it working
I got my phone back from repair and I'm confused ass to what to do next. I'm set to 'relocked' bootloader, but s-off without recovery or su apparently on 4.3. Every guide I find requires me to do something that causes things to come to as halt. Unless I'm doing something wrong I can't flash a recovery due to some error, then can't flash anything through recovery obviously, and I tried rumrunner but that stalls out after some point saying 'device is not rooted AND unsecure kernel'. What do I do next? Will HTCDev work? That's how I originally unlocked at release.
Really need help here, leaving the country for 3 weeks thursday morning and want to be back in business.
included pic of bootloader
yeah unlock again at htc dev then you will be able to flash a recovery
Or look here
[how to] lock/unlock your bootloader without htcdev(s-off required)
Thanks, had a feeling I needed to HTCDev again but didn't want to risk it given my limited time. Took some tinkering but looks like I'm unlocked and rooted again. Thanks BD.
So, I bought a second hand Sprint HTC One from Craigslist about a week ago.. First think I did was followed QBKing77's guide on how to unlock bootloader and root. Did that fairly easily, then went through this thread ( http://forum.xda-developers.com/showthread.php?t=2386703 ) to unlock it, had to do the steps in this thread ( http://forum.xda-developers.com/showthread.php?t=2491840 ) to get it to work since I had Android 4.3 and was unsure on how to go backwards to Android 4.2.2. After I got my phone unlocked, I went and got a Net10 SIM card and a month card, activated it, threw it in my One, and.. Nothing. No signal what so ever on GSM. It does recognize my SIM, though. So, I flashed to the original Radio from Sprint ( 1.00.20.0315 ), but still couldn't connect to GSM networks. I called Sprint, and they said my phone was still active on a plan, so I went hunting for a way around that.. I saw some things about flashing to Cricket, but I didn't want that. After relocking my bootloader and trying to RUU a few times, and none of them working, I thought I should update the Firmware. So, I downloaded some UL update for 3.62.401.1 without thinking, flashed it onto my device, and when I booted it up, it started a boot loop. I could navigate the phone for a while, but after about 5 minutes of it being turned on, it would reboot. So, I went into TWRP>wipe>advanced wipe> selected Dalvik Cache, Cache, and System. After that, my system now hangs on the HTC boot screen. I can still get into Bootloader, Fastboot, and Recovery. I tried flashing to TWRP 2.5.0.0, but my touch screen stopped working in TWRP when I did that. I just flashed back to 2.6.3.0, and my touch works again in TWRP. I can't get ADB Sideloader to work.. Currently, my Bootloader is Unlocked, S-Off, superCID, HBoot 1.55.0000, Radio 4A.21.3262.04, OpenDSP v32.120.274.0909, OS 1.29.651.10. That's about all the info I can get from Bootloader. It still says Tampered as well.
What should I do? My first step is to hopefully get back to where I can actually see the homescreen.. After that, I'd like to be able to get my phone to work on GSM.. I don't know if that is possible, though. I haven't found anything about someone having a phone that is still on a Sprint plan and being able to use GSM in the US.
Use this guide
[Complete guide] to SIM unlock your HTC One Sprint for free
BD619 said:
Use this guide
[Complete guide] to SIM unlock your HTC One Sprint for free
Click to expand...
Click to collapse
I already have my phone unlocked. I have the same RUU downloaded from that thread as well, and tried it one more time, and I got Error 155, basically telling me I have the wrong RUU for my device..
Mondragoonest said:
I already have my phone unlocked. I have the same RUU downloaded from that thread as well, and tried it one more time, and I got Error 155, basically telling me I have the wrong RUU for my device..
Click to expand...
Click to collapse
Are you 100% sure you are s-off?
Try a different USB Port
USB 2 if possible.
BD619 said:
Are you 100% sure you are s-off?
Try a different USB Port
USB 2 if possible.
Click to expand...
Click to collapse
I only have two ports on my laptop, and I've tried both. I even tried a usb hub, but that gave me the same error. In my bootloader, it says I'm s-off, I used rumrunner to do it a couple days ago.
Hi all,
I've been attempting to and failing for the last few days to get a custom ROM installed on My HTC one from Sprint. About an hour ago, I realized what the problem was but unfortunately have found no way of fixing this.
So far, I have unlocked the phone using the instructions from the HTCDev site as well as installed CWM/ TWRP Bootloaders and rooted with SU installed. I wiped all of the information off of the phone and as far as I know, the original OS is no longer available. I am able to access recovery and bootloader mode no problem and can install ROM's but they do not work fully as prior to rooting, I did not turn S-Off. It is currently on and I am stuck on how exactly to proceed.
Ideally, I would like for some way to be able to turn S-off, however, because I cannot access the operating system, I have no way of running rumrunner to get it done. At best, I can turn the phone on for about 2.5 minutes before it reboots and repeats the process. Added to that, whenever I unlock the screen, only the HTC logo shows up, there's no way to access anything else. I am able to copy files to storage during that time though.
Alternatively, I would like to return it to it's original state, but trying that has failed on multiple occasions. All of the guides that I have seen to return to stock require that you either have access to the operating system (without the reboot) or have S-Off, none of which I have.
Also, during the time that the OS loads, adb does not recognize the device. Its recognized in bootloader mode and Hboot, just not during 'regular' operation.
I would appreciate any assistance that could be provided as I really need to get this phone working.
Thanks! :good:
Follow this guide it will get you up and running again
http://forum.xda-developers.com/showthread.php?t=2503646
BD619 said:
Follow this guide it will get you up and running again
http://forum.xda-developers.com/showthread.php?t=2503646
Click to expand...
Click to collapse
Thanks! Worked like a charm. Don't know why it never showed up in my search results though. Just gotta get this phone unlocked for GSM now.
Another problem
So I finally got my HTC one from sprint unlocked but I ran into another problem. Whenever I insert a GSM sim into the phone, I cannot get any signal. An 'x' is shown over my signal bar. Have already flashed the old version of the radio but I still get the same result. Currently running viper rom 5.7. Bootloader is unlocked, S-off and rooted.
Any idea what else I can do? Got the PN 072 version if that helps
BTW, I am using a Domestic GSM sim
delion19 said:
So I finally got my HTC one from sprint unlocked but I ran into another problem. Whenever I insert a GSM sim into the phone, I cannot get any signal. An 'x' is shown over my signal bar. Have already flashed the old version of the radio but I still get the same result. Currently running viper rom 5.7. Bootloader is unlocked, S-off and rooted.
Any idea what else I can do? Got the PN 072 version if that helps
BTW, I am using a Domestic GSM sim
Click to expand...
Click to collapse
I REALLY don't get why people buy a CDMA phone to use on GSM networks.... That said this is a known issue if you're running KitKat. No solution last I checked.
Kraizk said:
I REALLY don't get why people buy a CDMA phone to use on GSM networks.... That said this is a known issue if you're running KitKat. No solution last I checked.
Click to expand...
Click to collapse
Main reason I got it was cause it seemed like there was a GSM radio in the CDMA version and I travel quite often out of state. Being able to use it locally would simply be a huge bonus. Will try downgrading to 4.3 or 4.1 to see if there's any change.