Hey guys i am trying to help a friend with his htc one sv. He recently updated the phone and now when it boots he gets to the lockscreen he can not do anything from here it shows the background, but no lock ring. His power buttons and volume keys do not work at this screen. We have factory reset the phone and it boots up the same. I am proficient with adb and am okay using this to restore his phone. He just wants a working phone so i am going to keep it stock so adb or if another method is available since i can access fastboot. He also was stock before this so no custom recovery. Thanks.
Edit: Its a boost mobile htc one sv
Is he still on ics? There is a jb nandroid backup around from boost, but as i think you know he has to unlock his bootloader for that.
Pull the battery then re install it hold the volume down button and then the pwr button and this will boot you into bootloader. Use the volume rocker to navigate down to factory reset and press the pwr button to select it. Let me know if this works. If not we will go in another direction
he is still on ics. i'll unlock the bootloader if i can do that but if their is anyway to boot the stock rom of ics i would be happy.
russellvone said:
Pull the battery then re install it hold the volume down button and then the pwr button and this will boot you into bootloader. Use the volume rocker to navigate down to factory reset and press the pwr button to select it. Let me know if this works. If not we will go in another direction
Click to expand...
Click to collapse
have done that already sadly no change.
Alright, has the bootloader been unlocked yet? What version was running before the update ICS or JB ?
BlackHoleSlam said:
he is still on ics. i'll unlock the bootloader if i can do that but if their is anyway to boot the stock rom of ics i would be happy.
Click to expand...
Click to collapse
You can ask for ICS rom here. I don't know, if somebody still have it. But anyway, jb or ics, you need to unlock bootloader. But try what russellvone told you first.
i am not sure which version of ics he was running previously he just came to me today showing me his phone. the bootloader is locked. He is not familar with rooting or unlocking.
I have a perfectly stock ICS backup to use, but if he hasn't even unlocked the bootloader yet really makes me wonder what's going on
Well sir tell me the info that is printed on your friend's bootloader screen
i don't have the phone on me at the moment he took it back he should bring it to me within a half hour.
Send me a personal message PM when you can get your hands on it.
Or better yet just quote this post. It alerts my phone faster when I'm quoted.
russellvone said:
Send me a personal message PM when you can get your hands on it.
Or better yet just quote this post. It alerts my phone faster when I'm quoted.
Click to expand...
Click to collapse
Sent from my HTC One using Tapatalk 4
Alright.... Looks like it took the update because it is on the JB hboot. It's gonna suck because of warranty 'void' but I'm gonna need you to unlock the bootloader via HTCdev.com.
Or since its still under warranty because the bootloader hasn't been unlocked yet he can send it back or call. Your/his choice. Just let me know what way you would like to do this
i'm unlocking his bootloader now just transfering adb.
Tell me if just unlocking the bootloader 'magically' allowed the phone boot fully into OS
well i will unlock and then can you provide your jb backup.
Alright. I'll do that.
thank you.
https://db.tt/WTTiZUT9twrp.img
https://db.tt/G0aUr1g3boot.img
Give me about 40 minutes to upload the JB system.img
Related
So from T-Mobile today, they announced that testing has been completed and everything should be all set and the update is coming out very soon.
So what I want to do is make sure everything on my phone checks out OK for the OTA update. Meaning, I want to make sure I have S-ON and stock recovery.
***I did not root my phone or install a custom ROM on it***
I unlocked the bootloader using the tool from htcdev.com. I don't know if I have the stock recovery still on my phone, I am assuming that I still do, but just for precaution I would like to make sure that I do.
What should I do to my phone to ensure that I get the OTA update? How would I go about doing that? Thanks a lot!
You'll be fine as long as you have stock recovery, you don't need to be s on or anything else. I updated to ota on my unbranded sensation and I was rooted and s off. I just flashed stock recovery in hboot before and it updated fine.
Sent from my Sensation using xda premium
OK how would I know if I have stock recovery and only stock recovery on my phone? I'm a complete noob when it comes to this.
Turn the phone off, press and hold power and volume down til hboot screen appears, once in hboot use volume keys to navigate to 'recovery' then press power to select it and if you get a screen with a phone icon and no menu appears at the top of the screen then you have stock recovery installed. And you can only have 1 recovery installed at a time.
Sent from my Sensation using xda premium
Ok now how would I be able to get out of the recovery page? Will I have to remove the battery? I don't recall there being a return or back button in HBOOT.
Also, how could I go about relocking my sensation?
Yeah remove battery or just press volume and up and hold and a menu should appear, reboot should be on there. Locking your bootloader is unnecessary, as long as you have stock recovery it will update and the update will relock the bootloader when it installs the updated one.
Sent from my Sensation using xda premium
Ok thanks!
No problem
Sent from my Sensation using xda premium
Ok it appears that I have stock recovery! And I won't be relocking the bootloader. Now here's to hoping that T-Mobile's very soon means the same thing to our very soon. Thanks for all the help!
sparx180 said:
Turn the phone off, press and hold power and volume down til hboot screen appears, once in hboot use volume keys to navigate to 'recovery' then press power to select it and if you get a screen with a phone icon and no menu appears at the top of the screen then you have stock recovery installed. And you can only have 1 recovery installed at a time.
Sent from my Sensation using xda premium
Click to expand...
Click to collapse
Just to confirm, its supposed to show a phone with a red exclamation point on it correct?
lol why update at all
Sent from my HTC Sensation Z710e using xda premium
cashman0712 said:
Just to confirm, its supposed to show a phone with a red exclamation point on it correct?
Click to expand...
Click to collapse
Yeah you're good.
For what its worth someone will have a rooted version of the stock update available for download within a few days of the update coming out. So of something doesnt work you will atill be able to get it.
Sent from a rebel ship by storing the message in an R2 unit. (Help me, XDA. You're my only hope)
Skipjacks said:
Yeah you're good.
For what its worth someone will have a rooted version of the stock update available for download within a few days of the update coming out. So of something doesnt work you will atill be able to get it.
Sent from a rebel ship by storing the message in an R2 unit. (Help me, XDA. You're my only hope)
Click to expand...
Click to collapse
Thanks, and the problem is I don't have S-OFF since I didn't use Revolutionary. I used the HTC unlocker tool. I am waiting for the ICS update before I start messing around, though I probably won't because the only thing I would want to do is disable bloatware which I can do anyways.
I relocked my bootloader and flashed an ruu hoping to fix some problems I was having and so far have been unable to unlock the bootloader again. It continues to show relocked on the screen after numerous attempts to unlock it. Every time I get the screen on the phone asking if I want to unlock and I choose yes and hit power. Once the phone reboots I go through the setup process and then go into the bootloader to check if it has unlocked. I dont really know where to go from here.
Guess I posted too soon. . . after the 15th try it took!
Mine did the same thing! Not sure why but persistence solved the issue.
Sent from my HTC One X using xda premium
If you use adb to reboot the phone in to the bootloader to enter token then it normally doesnt work. if you power the device off, then reboot to bootloader holding the vol- then enter token it works practically every time.
Move your unlock code to a different folder and try it. It worked for me on an HTC One which unlocks the same way.
galaxyjeff said:
Move your unlock code to a different folder and try it. It worked for me on an HTC One which unlocks the same way.
Click to expand...
Click to collapse
Dude, look at the date on the last post before you dug this up.
Sent from my Evita
timmaaa said:
Dude, look at the date on the last post before you dug this up.
Click to expand...
Click to collapse
And the OP had already resolved the issue, anyway (in the 2nd post).
I went to make a backup and ROM Manager said there was a new version of Recovery (ended in .8). I accepted and selected the Touch version. When I then tried to make a backup, the phone rebooted and I got this massage:
System software not authorized by Verizon Wireless has been found on your phone.
Please turn off your phone and go to the nearest Verizon Wireless store for help
Volume up/home/power just boots to this message every time. So does Volume down/home/power. There is no way to restore a backup or use the phone in any way. I have been doing this since the days of the OG Droid, but I am lost now. Please help.
sounds like you didnt unlock your booloader
Yes it does, but it has been unlocked for a long time, and I don't think I lost the unlock with tthe 4.1.2 update. How can I unlock the bootloader without being able to start the phone?
melucci said:
Yes it does, but it has been unlocked for a long time, and I don't think I lost the unlock with tthe 4.1.2 update. How can I unlock the bootloader without being able to start the phone?
Click to expand...
Click to collapse
Prostrate yourself to Odin.
Sent from my SCH-I535 using Tapatalk 2
melucci said:
Yes it does, but it has been unlocked for a long time, and I don't think I lost the unlock with tthe 4.1.2 update.
Click to expand...
Click to collapse
OTA's ALWAYS re-lock the bootloader and remove root.
Sent from my SCH-I535 using xda app-developers app
melucci said:
Yes it does, but it has been unlocked for a long time, and I don't think I lost the unlock with tthe 4.1.2 update. How can I unlock the bootloader without being able to start the phone?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1974114
See download #4 and step 1 on how to use odin.
melucci said:
Volume up/home/power just boots to this message every time. So does Volume down/home/power. There is no way to restore a backup or use the phone in any way. I have been doing this since the days of the OG Droid, but I am lost now. Please help.
Click to expand...
Click to collapse
Are you sure? Make sure you hold down Volume Down + Home for a few seconds before also hitting the Power button. I saw that same message yesterday when going back to stock and I was still able to boot into recovery/download mode. Also make sure your device is completely powered down (and not plugged in/charging)
deleted
THAT DID IT! I held volume down/home for a few seconds and then held power. The phone booted to a mode I had not seen before (recovery/download as you said?) and I said cancel and the phone booted!
I ran EZ-Unlock to unlock the boot loader. I tried several apps that require superuser permissions and they were granted it and run fine. So I assume I am still rooted, right?
Thanks so much for your help.
sounds like you should be good to go. one thing you should should consider doing is backing your IMEI if you havent already.
http://forum.xda-developers.com/showthread.php?t=1852255
bricked
melucci said:
THAT DID IT! I held volume down/home for a few seconds and then held power. The phone booted to a mode I had not seen before (recovery/download as you said?) and I said cancel and the phone booted!
I ran EZ-Unlock to unlock the boot loader. I tried several apps that require superuser permissions and they were granted it and run fine. So I assume I am still rooted, right?
Thanks so much for your help.
Click to expand...
Click to collapse
I done the same thing and it continues to go back to that same screen and will not restart.
PLEASE HELP!
kustom1955 said:
I done the same thing and it continues to go back to that same screen and will not restart.
PLEASE HELP!
Click to expand...
Click to collapse
Odin flash a stock image then re-root and unlock your bootloader if you so desire.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
Odin flash a stock image then re-root and unlock your bootloader if you so desire.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
My computer will not recognize my phone has been plugged in. I have deleted all the drivers and then reinstalled them anf can get my phone in odin mode but the computer still will not recognize my device.
Thanks for your help
kustom1955 said:
My computer will not recognize my phone has been plugged in. I have deleted all the drivers and then reinstalled them anf can get my phone in odin mode but the computer still will not recognize my device.
Thanks for your help
Click to expand...
Click to collapse
First, some background info is needed.
1) What did you do to your phone?
2) You have no success booting into Download mode?
3) Did you flash something in recovery? If so, what is the file name of the file you flashed?
Edit: Disregard #2, apparently I can't read. Are you using the Samsung OEM cable? Have you tried using a different USB port? Different computer?
SlimSnoopOS said:
First, some background info is needed.
1) What did you do to your phone?
2) You have no success booting into Download mode?
3) Did you flash something in recovery? If so, what is the file name of the file you flashed?
Edit: Disregard #2, apparently I can't read. Are you using the Samsung OEM cable? Have you tried using a different USB port? Different computer?
Click to expand...
Click to collapse
I just noticed the person you helped before me had a galaxy s3 and mine is a note 2 I605.
I opened the ROM manager app and it said something about allowing other devices to text from your same #.
I really hope this helps to figure this out. I'm going to try a different computer now.
kustom1955 said:
I just noticed the person you helped before me had a galaxy s3 and mine is a note 2 I605.
I opened the ROM manager app and it said something about allowing other devices to text from your same #.
I really hope this helps to figure this out. I'm going to try a different computer now.
Click to expand...
Click to collapse
You...have a Note 2? Why are you commenting in the Verizon GSIII forum bud? You have to try either your respective Note 2 carrier forum (i605 = Verizon Note 2 right?) or the international Note 2 forums. No one here can help you. Create a new thread in the Q/A section of the proper phone forum you need and you will receive relevant help.
SlimSnoopOS said:
You...have a Note 2? Why are you commenting in the Verizon GSIII forum bud? You have to try either your respective Note 2 carrier forum (i605 = Verizon Note 2 right?) or the international Note 2 forums. No one here can help you. Create a new thread in the Q/A section of the proper phone forum you need and you will receive relevant help.
Click to expand...
Click to collapse
Sorry, I didn't realize I was in the wrong area.
Thanks for your help
Verizon Warning NO MATTER WHAT
SlimSnoopOS said:
Odin flash a stock image then re-root and unlock your bootloader if you so desire.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
So far flashed HyperDrive, now AOKP, no matter what I do I get a yellow triangle and a warning.
I reflash stock
relfash VARLEC bootchain
reflash CWM
and try again.
No matter what options, settings, or ROM, I keep getting softbricked! ANY IDEAS?!>!
garvus said:
So far flashed HyperDrive, now AOKP, no matter what I do I get a yellow triangle and a warning.
I reflash stock
relfash VARLEC bootchain
reflash CWM
and try again.
No matter what options, settings, or ROM, I keep getting softbricked! ANY IDEAS?!>!
Click to expand...
Click to collapse
After flashing CWM, you need to unlock the bootloader. You should be flashing a vrale6 bootloader zip OR using EZ Unlock v1.2 to unlock.
Sent from my SCH-I535 using Tapatalk 4 Beta
boot loader
if during start up and i see the word SAMSUNG WITH A LOCK THAT APPEARS UNLOCKED does that mean i have an unlocked bootloader?
puchodog1977 said:
if during start up and i see the word SAMSUNG WITH A LOCK THAT APPEARS UNLOCKED does that mean i have an unlocked bootloader?
Click to expand...
Click to collapse
That means your Bootloader is not Unlocked. Make sure you use ez unlock 1.2 when unlocking. You can verify it's unlocked when you turn on the phone, and you see the word Samsung flash for a split second.
Sent from my SCH-I535 using Tapatalk 2
Hi Guys,
I have a Verizon SGS3 with stock JB 4.1.1 and I was following the steps posted here ([GUIDE] Root for Jelly Bean 4.1.1 or 4.1.2 OTA ***UPDATED 3/5***).
I got a little distracted and flashed both TWRP(1st) and Clockwork(2nd) but I still managed to successfully get to step 5 and root my phone and unlock boot loader.
Then I used clockwork and tried to install the liquid smooth 4.2 ( wiped cache and memeory etc) and after the rom installed and I selected reboot, and my phone was hard bricked. ie not response to any key and black screen, so no way to reload or restore anything. of course it was at the point I realized my mistake of flashing both.
I am going to JTAG the phone today, but I have a few questions,
My questions -
-was it because I had both TWRP and clockwork that caused this?
-if yes, how do I get rid of TWRP?
-I only want touchwiz and non of the other Verizon bloat, can you recommend a good stable rom.
thanks
What you have failed to realize that you don't have both recoveries you overwritten one when you flash the other. Believe it or not most if not all of Touchwiz ROMs are stable. The mistake came from the flashing of a custom ROMs as you failed to mention whether or not you have flashed the right Gapps for the ROM.
jmxc23 said:
What you have failed to realize that you don't have both recoveries you overwritten one when you flash the other. Believe it or not most if not all of Touchwiz ROMs are stable. The mistake came from the flashing of a custom ROMs as you failed to mention whether or not you have flashed the right Gapps for the ROM.
Click to expand...
Click to collapse
Thanks for the quick reply.
I did not flash gaaps. I thought I could do it after I got the liquid smooth 4.2 on it. Are you saying that I needed to flash the gaaps first before the liquid smooth?
Not flashing the gapps wouldn't "hard brick" your phone. You just wouldn't have the Play Store, Google Music, etc. OP, are you sure you're hard bricked? Because it's really difficult to hard brick this phone. The only way I've currently seen people HB their phone is by flashing something for the international S3. You can't get into recovery or download mode? Buy either holding Volume Up, Power or Volume Down, Power?
RCOVA said:
Not flashing the gapps wouldn't "hard brick" your phone. You just wouldn't have the Play Store, Google Music, etc. OP, are you sure you're hard bricked? Because it's really difficult to hard brick this phone. The only way I've currently seen people HB their phone is by flashing something for the international S3. You can't get into recovery or download mode? Buy either holding Volume Up, Power or Volume Down, Power?
Click to expand...
Click to collapse
none of the button combination have any response. I tried removing battery and waiting 5 mins and reinserting but nothing. My battery was at 80% when I flashed the liquid smooth and bricked it. When I plug in to the PC, the USB drivers no longer load so I cannot use ODIN.
I am out of ideas. Anything anyone can help would be appreciated. thanks
What is the name of the file you flashed?
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
What is the name of the file you flashed?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Liquid-JB-v2.2-OFFICIAL-t0lte
lloydteo said:
Liquid-JB-v2.2-OFFICIAL-t0lte
Click to expand...
Click to collapse
Well, that makes sense. You flashed the Galaxy Note 2 version. You need to flash d2vzw roms for our GSIII. Everything you did beforehand was presumably fine.
Sent from my SCH-I535 using xda app-developers app
lloydteo said:
Liquid-JB-v2.2-OFFICIAL-t0lte
Click to expand...
Click to collapse
And boom goes the dynamite.
RCOVA said:
And boom goes the dynamite.
Click to expand...
Click to collapse
Alright alright this is what you do. If the phone isn't hard bricked (which it may be since you flashed a GNII rom) you need to either try to boot into recovery (hold volume down and home at the same time, then hold power. When it vibrates, release the power and hold the other two until you get recovery) or ODIN (odin is the same, just hold volume up instead of down). Report back if you can boot into these and I will assist from there.
nrock2256 said:
Alright alright this is what you do. If the phone isn't hard bricked (which it may be since you flashed a GNII rom) you need to either try to boot into recovery (hold volume down and home at the same time, then hold power. When it vibrates, release the power and hold the other two until you get recovery) or ODIN (odin is the same, just hold volume up instead of down). Report back if you can boot into these and I will assist from there.
Click to expand...
Click to collapse
You have the button combinations reversed. Volume up puts your phone in recovery mode, volume down puts it in download (Odin) mode.
And he is hard bricked. He stated no response from any button combinations.
RCOVA said:
And he is hard bricked. He stated no response from any button combinations.
Click to expand...
Click to collapse
That is correct, there is not response from ANY buttons and my battery is confirmed charged. USB drivers unable to load when plug int o PC also.
Do you guys know of any good sites that lists the latest custom roms for verizon SGS3? I mean the correct and latest file names for the roms.
thanks
lloydteo said:
That is correct, there is not response from ANY buttons and my battery is confirmed charged. USB drivers unable to load when plug int o PC also.
Do you guys know of any good sites that lists the latest custom roms for verizon SGS3? I mean the correct and latest file names for the roms.
thanks
Click to expand...
Click to collapse
You can find them all here on xda. Just browse the Android Development and Original Android Development forums for the Verizon Galaxy s3 only. You'll find AOSP ROMs and all kernels in Original Android Development and Touchwiz ROMs and mods and other stuff in Android Development. Don't flash anything that isn't made for the Verizon Galaxy S3
Sent from my Verizon Samsung Galaxy SIII
lloydteo said:
That is correct, there is not response from ANY buttons and my battery is confirmed charged. USB drivers unable to load when plug int o PC also.
Do you guys know of any good sites that lists the latest custom roms for verizon SGS3? I mean the correct and latest file names for the roms.
thanks
Click to expand...
Click to collapse
Not that I know of besides xda and rootzwiki, just be more careful. When you download roms always look for the download links for "d2vzw" roms or that specifically state "Verizon GSIII" when the link isn't immediately on xda. Typically AOSP roms are the ones with multiple multi-carrier, multi-device download links so always check and re-check after downloading zips.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
Not that I know of besides xda and rootzwiki, just be more careful. When you download roms always look for the download links for "d2vzw" roms or that specifically state "Verizon GSIII" when the link isn't immediately on xda. Typically AOSP roms are the ones with multiple multi-carrier, multi-device download links so always check and re-check after downloading zips.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Thanks again for the pointers.
When I get my phone back today, I have decided to flash the Bean ROM. I read the instructions and have one question. What does STEP 1 mean when it says "pick the locked version?" Does he mean pick the locked ROM version? If someone can explain briefly it would be appreciated. thanks
Install Instructions:
Step 1-
Make sure u are unlocked or pick the locked version during flash
Step 2-
Wipe all(factory reset and davlick wipe) if coming from an old build
Step 3-
Install the Rom
Step 4-
Reboot and Enjoy! after first boot reboot if youre using a custom ui and not the stock one(fixed soon)
lloydteo said:
Thanks again for the pointers.
When I get my phone back today, I have decided to flash the Bean ROM. I read the instructions and have one question. What does STEP 1 mean when it says "pick the locked version?" Does he mean pick the locked ROM version? If someone can explain briefly it would be appreciated. thanks
Install Instructions:
Step 1-
Make sure u are unlocked or pick the locked version during flash
Step 2-
Wipe all(factory reset and davlick wipe) if coming from an old build
Step 3-
Install the Rom
Step 4-
Reboot and Enjoy! after first boot reboot if youre using a custom ui and not the stock one(fixed soon)
Click to expand...
Click to collapse
He's taking about your bootloader. If you chose to root and unlock your bootloader when you rooted your phone, you get the regular rom. If you chose to only root and not unlock then your bootloader is locked and you must flash the locked version.
Sent from my Verizon Samsung Galaxy SIII
lloydteo said:
Thanks again for the pointers.
When I get my phone back today, I have decided to flash the Bean ROM. I read the instructions and have one question. What does STEP 1 mean when it says "pick the locked version?" Does he mean pick the locked ROM version? If someone can explain briefly it would be appreciated. thanks
Install Instructions:
Step 1-
Make sure u are unlocked or pick the locked version during flash
Step 2-
Wipe all(factory reset and davlick wipe) if coming from an old build
Step 3-
Install the Rom
Step 4-
Reboot and Enjoy! after first boot reboot if youre using a custom ui and not the stock one(fixed soon)
Click to expand...
Click to collapse
Oh, long story short that's the ICS rom that he created in July. From July-August, we had a locked bootloader, which is what he's referring. Thi meant flashing roms required something with a Kexec boot sequence, but once the GSIII was unlocked in August his rom and every rom presently available requires you to have an unlocked bootloader.
That said, when you get your phone you will need to:
1) root
2) unlock the bootloader
3) then proceed from there, whether that's backing up your IMEI or flashing a rom, etc.
I thoroughly suggest his JB rom since there's active development on it. Beans JB rom was updated last week and has "Build 15 [04/21/13]" in the title.
joshua5683 said:
He's taking about your bootloader. If you chose to root and unlock your bootloader when you rooted your phone, you get the regular rom. If you chose to only root and not unlock then your bootloader is locked and you must flash the locked version.
Sent from my Verizon Samsung Galaxy SIII
Click to expand...
Click to collapse
Just got some bad news from the repair shop, they said that they cannot recover the phone. Any suggestions of a good shop that can recover the phone from a hard brick?
Also is this d2vzw_JellyBeans_B15 the locked or unlocked version? thans
lloydteo said:
Just got some bad news from the repair shop, they said that they cannot recover the phone. Any suggestions of a good shop that can recover the phone from a hard brick?
Also is this d2vzw_JellyBeans_B15 the locked or unlocked version? thans
Click to expand...
Click to collapse
Not sure about the shop thing but in the instructions for flashing that rom it says you must be unlocked. Which means you must have an unlocked bootloader. You do this by flashing SuperSU_Bootloader_FIXED.zip in recovery. That zip file is recommended for flashing when you're following the root guide and they have a download link for it.
Sent from my Verizon Samsung Galaxy SIII
Sorry for flooding this Forum with something basic as this but as a mere mortal I don't possess the mental capacity nor stamina to crash course my way in to this whole developers battleground.
I got a HTC ONE S that had been unlocked( I think) and when stupid me tried to do a system update (uncustomed to the way of the android as a convert apple-noob:silly I updated the phone with some kind of CID package which immediately sent the HTC in to the dreadded:
"This build is for development purposes only 20second loop of doom"
so after hours of studying this ancient language of boots, CID, builds, and alien laungage mumbo I havn't even been able to get the USB fastboot to work.
thusly I admit defeat and beg and plead to ye ascent beings only know as developers to make a complete noob-proof course of action how to tackle this peculiar problem.
so can anyone please make a step by step guid of what to download, how to install, where to get it and what to do That'd beeee swell.:highfive:
also I'll be going away so may not answer until sunday
any takers on helping me solve this riddle?
Welcome to the world of bricking and screwing up. This is not like Apple jailbreaking where you press one button on a website and it works.
This is pain and suffering. I would try and run an RUU to get the phone to stock. There are tons of threads on how to run an RUU. If the phone is not S-OFF, you will have to relock boot loader to run the RUU.
808phone said:
Welcome to the world of bricking and screwing up. This is not like Apple jailbreaking where you press one button on a website and it works.
This is pain and suffering. I would try and run an RUU to get the phone to stock. There are tons of threads on how to run an RUU. If the phone is not S-OFF, you will have to relock boot loader to run the RUU.
Click to expand...
Click to collapse
alright cheers, pretty sure it's S-ON and despite not knowing anything you just said at least it's something.
I also assume I'll need USB fastboot for this so I guess I'll start by trying to get that working
Anyone else care to explain the steps to take in greater detail? This was not a failed attempt at jailbreaking it was purely accidental so I have no experience doing this
Edit: I might add I suck at searching through forums aswell (especially when I don't know what I'm looking for) so maybe just a link to the proper threads would help me loads
LuckyXII said:
Anyone else care to explain the steps to take in greater detail? This was not a failed attempt at jailbreaking it was purely accidental so I have no experience doing this
Edit: I might add I suck at searching through forums aswell (especially when I don't know what I'm looking for) so maybe just a link to the proper threads would help me loads
Click to expand...
Click to collapse
To get back to stock, you run an RUU (ROM update utility). Here is a thread:
http://forum.xda-developers.com/showthread.php?t=2678700
I guess it's similar to running iTunes and pressing the restore button - but more involved.
not sure if I have a custom recovery but either way I couldn't flash the recovery.img and the RUU I ran didn't work (it was the same RUU that was installed on the phone)
Phone is S-ON
hboot 2.15.0000
open dps v31.1.0.45.0815
eMMc-boot
RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4
LuckyXII said:
not sure if I have a custom recovery but either way I couldn't flash the recovery.img and the RUU I ran didn't work (it was the same RUU that was installed on the phone)
Phone is S-ON
hboot 2.15.0000
open dps v31.1.0.45.0815
eMMc-boot
RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4
Click to expand...
Click to collapse
Did you relock the boot loader before running RUU?
808phone said:
Did you relock the boot loader before running RUU?
Click to expand...
Click to collapse
I followed the steps but can't say I remember seeing "relocking boot loader" I will have to check this out further in the morning
LuckyXII said:
I followed the steps but can't say I remember seeing "relocking boot loader" I will have to check this out further in the morning
Click to expand...
Click to collapse
OK, then check this link out:
http://androidforums.com/one-s-all-things-root/691874-guide-how-run-ruu-your-htc-one-s.html
808phone said:
OK, then check this link out:
http://androidforums.com/one-s-all-things-root/691874-guide-how-run-ruu-your-htc-one-s.html
Click to expand...
Click to collapse
cannot open "Unlock_code.bin" :/
tried everything... changing the directive in cmd to match the location of the bin file but nothing works
adb can't find my device but fastboot can which could be why the RUU nor unlocking bootloader won't work and to get adb to work I need to enable USB debugging which can't be done while the phone is looping (unless some1 knows the right command line)
I am retarded
since I got this phone second hand I didn't know what had been done with it other than what I installed to cause my problems...
one of the things that had been done previously was unlocking bootloader.. hence the very obvious "Unlocked" in the boot menu.... sooo unlocking an unlocked bootloader was kinda redundant
tried oem locking the boot b4 but missed to specify where the files where (C:adb), lock worked and RUU installed without a hing!
thanks for your help if I knew what I was doing your instructions would have worked perfectly!
Alright!!!!!! Well, you are set!
So..... now that's it's back to stock. Are you going to use it as-is? Or are you planning to try a custom ROM again?
Try booting into the boot loader by shutting off the phone, then pressing volume down while pressing power. If it doesn't go to boot loader, then press and hold power for something like 10 seconds until the phone shuts off, then press volume down, and power again. Keep holding volume down until you get the boot loader menu.
Write down what it says about your HBOOT and whether you are S-OFF or S-ON.
DO NOT CHOOSE ANY COMMANDS FOR NOW
Press and hold power until the phone turns off again when you are done. Then press power again to turn the phone on again after a few seconds to use your phone regularly.
808phone said:
Alright!!!!!! Well, you are set!
So..... now that's it's back to stock. Are you going to use it as-is? Or are you planning to try a custom ROM again?
Try booting into the boot loader by shutting off the phone, then pressing volume down while pressing power. If it doesn't go to boot loader, then press and hold power for something like 10 seconds until the phone shuts off, then press volume down, and power again. Keep holding volume down until you get the boot loader menu.
Write down what it says about your HBOOT and whether you are S-OFF or S-ON.
DO NOT CHOOSE ANY COMMANDS FOR NOW
Press and hold power until the phone turns off again when you are done. Then press power again to turn the phone on again after a few seconds to use your phone regularly.
Click to expand...
Click to collapse
well if I were to try something now that I've already started walking down the path it'd probably be kitkat...
http://forum.xda-developers.com/showthread.php?t=2183023
note sure if I'm ready though
LuckyXII said:
well if I were to try something now that I've already started walking down the path it'd probably be kitkat...
http://forum.xda-developers.com/showthread.php?t=2183023
note sure if I'm ready though
Click to expand...
Click to collapse
OK take your time and when you are ready, PM me. I really do suggest CandyKat if you go for a custom ROM. It is the best ROM I have used on the ONE S. CM11 was ok for me, but for some reason CandyKat is just running so much better.
808phone said:
OK take your time and when you are ready, PM me. I really do suggest CandyKat if you go for a custom ROM. It is the best ROM I have used on the ONE S. CM11 was ok for me, but for some reason CandyKat is just running so much better.
Click to expand...
Click to collapse
Alright I will look in to it! Thank you for all the help wouldn't have done it without you