Related
Hi there,
I have unlocked my Nexus One but I noticed that the bootloader says S-ON. Is there anyway to switch it to S-OFF? I searched the forums but it looks like I cannot switch it. Is this true?
What is the difference between S-OFF/S-ON...as in does it limit me from doing anything?
I tried to flash a recovery image onto my phone and it seems to work but once I reboot, the options in my recovery image dissappear and I have to reflash again. IS this due to S-ON?
Thanks,
Croyd
Not do-able.
All you gain from it is the ability to lock the bootloader up again, the recovery going missing is because the stock one is reloaded on reboot. You can rename/remove 2 files and it'll stop happening.
Thanks for the info.
What are the 2 files that need to be renamed.
I see a file called /system/etc/install-recovery.sh. Is this one of them?
Thanks,
-Croyd
Yes that is one, the other is /system/recovery-from-boot.p
Read the Recovery section from Wiki.
I figured it out the 2nd file. Thanks anyways!
Croyd
I've have recently unlocked and flashed cm10.1 ROM and I'm on s-on. Is there now a way to change it to s-off?? I want to update the radio.
Thanks in advance.
You don't need to be S-OFF to flash the radio.
So far I've had no luck using custom ROMs as it just stays on the htc boot screen and does not work. I can confirm that 'MiUi' does work on my phone - however it is buggy and I don't like it.
I want cyanogenod or either android revolution HD but none of these work.
I thinkit has something to do with the HBOOT being 1.16.000, and the ROM version i'm after is 2.34.981.1 (virgin or optus branded) - am with virgin though in Australia.
I have a custom bootloader/recovery whatever you call it, I wipe the cache, dalvik cache and factory wipe, before installing all ROM's. I can't update to stock ROM either because there is none for hboot 1.16.000
So right now my phone is pretty much a paper weight until I can get it working again.
I prefer custom ROM's if there is any that work, if not I atleast want the stock ROM to work for now so I can use my phone. If someone can help me through the process to get it working it would be greatly appreciated. Thanks.
jakeyo said:
So far I've had no luck using custom ROMs as it just stays on the htc boot screen and does not work. I can confirm that 'MiUi' does work on my phone - however it is buggy and I don't like it.
I want cyanogenod or either android revolution HD but none of these work.
I thinkit has something to do with the HBOOT being 1.16.000, and the ROM version i'm after is 2.34.981.1 (virgin or optus branded) - am with virgin though in Australia.
I have a custom bootloader/recovery whatever you call it, I wipe the cache, dalvik cache and factory wipe, before installing all ROM's. I can't update to stock ROM either because there is none for hboot 1.16.000
So right now my phone is pretty much a paper weight until I can get it working again.
I prefer custom ROM's if there is any that work, if not I atleast want the stock ROM to work for now so I can use my phone. If someone can help me through the process to get it working it would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
Hyun is looking for you at revolutionary irc channel.
Sent from my HTC Incredible S using Tapatalk
I know.. I have spoken to him.
jakeyo said:
I know.. I have spoken to him.
Click to expand...
Click to collapse
Any luck? still unable to flash anything?
jakeyo said:
So far I've had no luck using custom ROMs as it just stays on the htc boot screen and does not work. I can confirm that 'MiUi' does work on my phone - however it is buggy and I don't like it.
I want cyanogenod or either android revolution HD but none of these work.
I thinkit has something to do with the HBOOT being 1.16.000, and the ROM version i'm after is 2.34.981.1 (virgin or optus branded) - am with virgin though in Australia.
I have a custom bootloader/recovery whatever you call it, I wipe the cache, dalvik cache and factory wipe, before installing all ROM's. I can't update to stock ROM either because there is none for hboot 1.16.000
So right now my phone is pretty much a paper weight until I can get it working again.
I prefer custom ROM's if there is any that work, if not I atleast want the stock ROM to work for now so I can use my phone. If someone can help me through the process to get it working it would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
If you go to the development section of the HTC Incredible 2 forum, attn1 has a script tool that uses the latest Revolutionary/Unreovked exploit to downgrade the ROMand HBOOT to a version that is supported by Revolutionary.
If you look at the script, it is pretty simple. You would just need to use an older Virgin Mobile RUU.zip instead of the Inc2 version. It looks like the 2.12.981.2 would be the one to try.
Hang on a second, how did you S-off the Hboot 1.16?
I thought you need S-off to be able to flash a custom Rom...
How did you install Miui?
Am I missing something here?
Doesnt matter if you need S-ON or S-OFF, as long as you get permissions to access root files.
Someone installed a custom bootloader so I can install custom ROM's, and it just works.... apparently the radios are locked though.
So, another day gone by and my phone is still not working. I can use MiUi, but I ran out of data on my 3g sim and wifi doesnt work, so now I have no internet on it.
katu2006 said:
Hang on a second, how did you S-off the Hboot 1.16?
I thought you need S-off to be able to flash a custom Rom...
How did you install Miui?
Am I missing something here?
Click to expand...
Click to collapse
I'm pretty sure no soff will cause the issues he is experiencing, though he doesn't seem to be listening
no, you're all just noobs.
It was the boot.img, we swapped it with the MiUi then put back the original one, now it boots up on cyanogenmod7.1 and works completely fine.
Can access root files, can take screenshots, everything is normal.
and I have s-on.
jakeyo said:
no, you're all just noobs.
It was the boot.img, we swapped it with the MiUi then put back the original one, now it boots up on cyanogenmod7.1 and works completely fine.
Can access root files, can take screenshots, everything is normal.
and I have s-on.
Click to expand...
Click to collapse
Yes im a noob that has been using android since 2009..
You seem like a supreme douche.
Weren't you the one who was crying about wanting to go back to his iphone lol
jakeyo said:
no, you're all just noobs.
It was the boot.img, we swapped it with the MiUi then put back the original one, now it boots up on cyanogenmod7.1 and works completely fine.
Can access root files, can take screenshots, everything is normal.
and I have s-on.
Click to expand...
Click to collapse
You're calling us noobs, but you don't even know what was done on your phone...
What's the following sentence supposed to say?
"It was the boot.img, we swapped it with the MiUi then put back the original one"
To get a custom Rom, you actually have to INSTALL it...To get the custom Rom installed, you need CWM recovery. But if you have HBoot 1.16.000, you can't have a custom recovery yet.
In less your "friend" did a downgrade of the HBoot to 1.13.000, it's unlikely that you have CWM recovery on your phone. Even so, to my knowledge HBoot 1.16.000 does a version check and won't let you downgrade it.
So, the question remains, how did you get CWM recovery on your phone?
katu2006 said:
You're calling us noobs, but you don't even know what was done on your phone...
What's the following sentence supposed to say?
"It was the boot.img, we swapped it with the MiUi then put back the original one"
To get a custom Rom, you actually have to INSTALL it...To get the custom Rom installed, you need CWM recovery. But if you have HBoot 1.16.000, you can't have a custom recovery yet.
In less your "friend" did a downgrade of the HBoot to 1.13.000, it's unlikely that you have CWM recovery on your phone. Even so, to my knowledge HBoot 1.16.000 does a version check and won't let you downgrade it.
So, the question remains, how did you get CWM recovery on your phone?
Click to expand...
Click to collapse
This thread is awesome
no, if I hold down power down and power button I see S-ON and HBOOT 1.16.0000
He typed in commands to give it root permissions, not sure exactly as he remote controlled my computer and typed it in. Then yes, he flashes CWM onto the phone then I installed revolutionary.
Firstly, I went onto the HTC dev site (created an account) and followed the steps to unlock the bootloader. In the end, it was successful, and once it's finished it will wipe the phone (AND WILL STILL SAY s-on)
So then the bootloader is now unlocked, and he did various commands in fastboot. My guess is that he installed CWM from there and it just worked.
at first, cyanogenmod would not boot, so he copied the (boot.img that is working) from MiUi and repled it with cyanogenmod's. The phone booted up and worked. Then he put it back how it was and it now works. Strange, but something must've given it a kick.
I'll repeat myself.
HBOOT 1.16.0000
S-ON
Cyanogenmod &.1 (stable)
Full root access
Need I say more to prove it?
As far as I know, I just cannot flash radios, which actually require the S-OFF....
sorry if I come across as rude, just a long day..
Talk to aftab565 he has the same hboot as you and has arhd running. Sounds like your phone was temp rooted and flashed and I would advise against letting people you don't know take remote access of your pc.
Hopefully it works for him I couldn't help.
Just replied to his thread.
And I know I was aware. I had full control though (could press a certain key to disconnect the connection - and only gave a temporary password) He was only typing in CMD things to do with the phone that I've heard of before
(ADB shell, fastboot recovery etc) and in the end worked well. He said my job is done and disconnect himself, so good guy
Didn't take my eyes off the screen either.
jakeyo said:
Just replied to his thread.
And I know I was aware. I had full control though (could press a certain key to disconnect the connection - and only gave a temporary password) He was only typing in CMD things to do with the phone that I've heard of before
(ADB shell, fastboot recovery etc) and in the end worked well. He said my job is done and disconnect himself, so good guy
Click to expand...
Click to collapse
You gotta give props to these guys for donating their time. Every day there's more talk about h-boot 1.16.0000 so I figure if devs want to keep devin there'll be a rev released eventually.
I really appreciate the amount of work hes done, in total I recon he's spent about 6 hours trying to help me getting it to work.
Never left me by myself, he always helped me through every step and was always there if I needed help. I've now got CM7 thanks to him. If he didn't fix it, I would have a useless phone because I couldn't even put on the stock ROM because of my HBOOT im guessing (I did an OTA update to get 1.16.0000 therefore too new to download)
I think SOME of the custom roms do have support for 1.16.0000 and what you only need is the boot file from them to boot up your non-booting ROM then you're all good.
ok, just to put some closure and sanity on this thread.
Firstly I'm probably bettery know as hyuh on #revolutionary, and it was me who was connected to his PC.
I use teamviewer to connect to people remotely, this allows anyone who doesn't like the look of *anything* I do to diconnect me...The user in front of the PC has full control of my session and I remind them to close teamviewer after we're done.
Secondly to those who think you need to be S-OFF to install a custom ROM or custom recovery, this is simply not true in the case of the 1.16 hboot. If you follow the HTC unlock procedure then you will have sufficient access to the phone to do this, it is not S-OFF just an unlock. Your phone will be in state "S-ON unlocked" This allows certain partitions on the emmc to be written to, and this sufficient for custom ROMs.
Really all that is requird is:
Code:
fastboot flash recovery <recovery.img>
then follow the normal flashing procedures.
In jakeyo's case CM7 would not boot, but MIUI would. When I say it would not boot I do not mean a boot loop here, I mean no boot period. At this point I had expected to need to rebuild a boot image for CM7 for him suspecting that HTC had done something different in the new hboot with paritions or the boot image offset.
The reason for flashing the MIUI boot image on top of CM7 was simple, to get to adb in the boot image. However seeing nothing particularly strange in the boot sequence ( other than the mismatch and resulting bootloop) I decided to reflash the CM7 boot image through fastboot.
The phone booted fully this time without issues.
It appears that the boot image simply did not flash properly from recovery the first time but I don't have a vivo to troubleshoot further.
A couple of things:
1. Don't take the OTA for 1.16 hboot if you haven't already done so.
There is currently no unofficial unlock/S-OFF
There is no RUU to fix the phone if you screw up.
There is nothing in the OTA you can't get in other ways.
2. If you're on 1.16 and want custom ROMs and aren't worried about warranty, go ahead and do unlock from HTC, but bear in mind:
There is no RUU, so you can't go back to stock
You can't flash radios
You can't superCID or similar ( but not needed since there is no RUU )
2a. You don't need any existing root method to exist, there is no exploit involved in any of this, this will work irrespective of the current status of a root expoit existing or not.
2b. The phone does not have to be listed by HTC as being supproted. Any phone with a suitable hboot can be unlocked.
if this:
Code:
fastboot oem get_identifier_token
returns an identifier code then the phone can be ulocked.
globatron said:
ok, just to put some closure and sanity on this thread.
Firstly I'm probably bettery know as hyuh on #revolutionary, and it was me who was connected to his PC.
I use teamviewer to connect to people remotely, this allows anyone who doesn't like the look of *anything* I do to diconnect me...The user in front of the PC has full control of my session and I remind them to close teamviewer after we're done.
Secondly to those who think you need to be S-OFF to install a custom ROM or custom recovery, this is simply not true in the case of the 1.16 hboot. If you follow the HTC unlock procedure then you will have sufficient access to the phone to do this, it is not S-OFF just an unlock. Your phone will be in state "S-ON unlocked" This allows certain partitions on the emmc to be written to, and this sufficient for custom ROMs.
Really all that is requird is:
Code:
fastboot flash recovery <recovery.img>
then follow the normal flashing procedures.
In jakeyo's case CM7 would not boot, but MIUI would. When I say it would not boot I do not mean a boot loop here, I mean no boot period. At this point I had expected to need to rebuild a boot image for CM7 for him suspecting that HTC had done something different in the new hboot with paritions or the boot image offset.
The reason for flashing the MIUI boot image on top of CM7 was simple, to get to adb in the boot image. However seeing nothing particularly strange in the boot sequence ( other than the mismatch and resulting bootloop) I decided to reflash the CM7 boot image through fastboot.
The phone booted fully this time without issues.
It appears that the boot image simply did not flash properly from recovery the first time but I don't have a vivo to troubleshoot further.
A couple of things:
1. Don't take the OTA for 1.16 hboot if you haven't already done so.
There is currently no unofficial unlock/S-OFF
There is no RUU to fix the phone if you screw up.
There is nothing in the OTA you can't get in other ways.
2. If you're on 1.16 and want custom ROMs and aren't worried about warranty, go ahead and do unlock from HTC, but bear in mind:
There is no RUU, so you can't go back to stock
You can't flash radios
You can't superCID or similar ( but not needed since there is no RUU )
Click to expand...
Click to collapse
Get a mod to make a hboot sticky there will be floods of this crap further down the road.
I cannot find an answer to my problem as hard as i look. today, i decided to root my phone (HTC vivid). I rooted it successfully, i went to the Superuser and it said it needed to be updated and to flash a kernel or something like that. (i was using this program http://forum.xda-developers.com/showthread.php?t=1498003) I went to the program that i meantioned above and i clicked flash stock vivid kernel, thinking that this was the kernel i had to update or flash or whatever then my phone reboots and its all like Hurr duur im stuck on the HTC screen watcha gonna do about it. I tried many things:
One thing i tried was to do the .zip thingy, with the boot loader relocked, and it wont boot to anything else but the boot loader
i tried also to do the ruu thing, but it kept giving me errors about my phone model or something like that
Can someone please tell me what i did wrong and how to fix it?
i would really appreciate it big time!
Edit: i have an micro sd, if that info helps
I would try to restore it back to stock.
Relock to bootloader if it isn't still locked.
Then run the stock ruu for your phone from http://forum.xda-developers.com/showthread.php?t=1338919
I had my vivid stuck on the HTC screen and this worked for mine.
Also, If you rooted to ICS you are most likely stuck until the official RUU from HTC is out...
FernandoR211 said:
I would try to restore it back to stock.
Relock to bootloader if it isn't still locked.
Then run the stock ruu for your phone from http://forum.xda-developers.com/showthread.php?t=1338919
I had my vivid stuck on the HTC screen and this worked for mine.
Also, If you rooted to ICS you are most likely stuck until the official RUU from HTC is out...
Click to expand...
Click to collapse
You need to install HTC sync or the htcdrivers before running the ruu otherwise it won't see your phone and will just error out.
Sent from my HTC PH39100 using xda premium
pichi123 said:
I cannot find an answer to my problem as hard as i look. today, i decided to root my phone (HTC vivid). I rooted it successfully, i went to the Superuser and it said it needed to be updated and to flash a kernel or something like that. (i was using this program http://forum.xda-developers.com/showthread.php?t=1498003) I went to the program that i meantioned above and i clicked flash stock vivid kernel, thinking that this was the kernel i had to update or flash or whatever then my phone reboots and its all like Hurr duur im stuck on the HTC screen watcha gonna do about it. I tried many things:
One thing i tried was to do the .zip thingy, with the boot loader relocked, and it wont boot to anything else but the boot loader
i tried also to do the ruu thing, but it kept giving me errors about my phone model or something like that
Can someone please tell me what i did wrong and how to fix it?
i would really appreciate it big time!
Edit: i have an micro sd, if that info helps
Click to expand...
Click to collapse
1. You obviously didn't know what you were doing. Lessons for next time.
2. If the .zip thingy made the bootloader update and it seems like it managed to flash everything alright, then you need to make sure the zip isn't on any storage connected to the phone, then go from bootloader to fastboot, unlock the bootloader using the HTCDev bootloader unlock procedure (I hope you kept your unlock_code.bin!), then fastboot flash a recovery.img, then boot to recovery from the bootloader, and flash an ICS ROM, then go back to fastboot and flash the boot.img to get the kernel flashed.
I'm guessing that you may have flashed the ICS bootloaders, but you aren't specific enough. What ruu did you try to run, exactly what zip did you try to install?
You didn't do anything wrong, you just didn't complete the procedure.
kozmikkick said:
You need to install HTC sync or the htcdrivers before running the ruu otherwise it won't see your phone and will just error out.
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
Well I hope that was a given. BUt I guess I should have listed it. Good point!
If you have an AT&T Vivid, then you should be okay, run the latest ICS RUU and hope for the best. If not, you'll have to do it the old fashioned way through lots of fastboot commands.
thank you everyone!
/thread
My week old HTC One got messed up because i tried to root it and now theres no recovery and i cant reset it. also the wifi doesnt work. cant find stock rogers ruu.
I downloaded the OTA update for my Rogers HTC One version 1.29.631.4. The cid from my phone and the one in the ota update match I just don't know how to install it. Also atm I have no recovery installed because i deleted twrp recovery and i dont know how to get my normal one back.
EDIT: I fixed this. I have stock rogers rom and recovery back on my relocked bootloader htc one i can get ota updates normally. If anyone needs this for their rogers htc one pm me
How did you delete twrp?
fastboot flash recovery recoveryname
You probably have enough information to search now.
BenPope said:
How did you delete twrp?
fastboot flash recovery recoveryname
You probably have enough information to search now.
Click to expand...
Click to collapse
I flashed the recovery but now my wifi is stuck on turning on and then it says error.
Rogers htc one stock recovery
zelliott7234 said:
My week old HTC One got messed up because i tried to root it and now theres no recovery and i cant reset it. also the wifi doesnt work. cant find stock rogers ruu.
I downloaded the OTA update for my Rogers HTC One version 1.29.631.4. The cid from my phone and the one in the ota update match I just don't know how to install it. Also atm I have no recovery installed because i deleted twrp recovery and i dont know how to get my normal one back.
EDIT: I fixed this. I have stock rogers rom and recovery back on my relocked bootloader htc one i can get ota updates normally. If anyone needs this for their rogers htc one pm me
Click to expand...
Click to collapse
Hey I'm new to this. Please help me to restore stock rom on my Rogers Htc One.
It all started when I rebooted my phone one day. My phone loaded up the lock screen with google voice. I could say the pin but could never get my phone unlocked. The keyboard button didn't work. So rather than just bootloader/factory resetting my phone, i decided i might as well unlock it and give myself root and flash a rom and try it out. I am an experienced EVO 4G user and have flashed many a rom. I did not have any problems unlocking the phone, flashing the TWRP recovery, applying su, or flashing the rom. I flashed the rootbox rom. It worked just fine. I then decided I was going to try a different rom out. I was not aware that there were roms that would cause problems... the non-sprint roms. I then tried to flash several non-sprint roms. None of the worked and eventually my phone would only boot up into the bootloader. I was able to successfully fastboot flash the TWRP recovery back onto my phone. I tried then to load in a sprint rom. Apparently I had messed up my radios, file structure and possibly other stuff, as no rom would work at that point. After much research, I found I needed to apply the RUU to get my phone back into "sprint" mode with the correct radios and file structure. I have been trying for hours now to do just that. I have tried all the methods listed on xda. The current condition of my phone: Will boot only into bootloader, will not boot into recovery although i think the TWRP recovery is still on my phone. I have the tampered, relocked, and security warning messages at the top of my phone. I am still s-on. I cannot get s-off as I have no accessible os on the phone to use the adb commands. I do have fastboot access. I have tried to fastboot flash the ruu and I get failed messages either <remote: 12 signature verify fail> or <remote: 43 main version check fail>
Any/All advice recommendations are welcome. If there is a thread about fixing bricked phones or tools to load RUU, I have tried them to no avail.
Thanks
Have you tried running the RUU from your PC? It would also help to know if you are on 1.29 or 1.31.
MrFixit007 said:
It all started when I rebooted my phone one day. My phone loaded up the lock screen with google voice. I could say the pin but could never get my phone unlocked. The keyboard button didn't work. So rather than just bootloader/factory resetting my phone, i decided i might as well unlock it and give myself root and flash a rom and try it out. I am an experienced EVO 4G user and have flashed many a rom. I did not have any problems unlocking the phone, flashing the TWRP recovery, applying su, or flashing the rom. I flashed the rootbox rom. It worked just fine. I then decided I was going to try a different rom out. I was not aware that there were roms that would cause problems... the non-sprint roms. I then tried to flash several non-sprint roms. None of the worked and eventually my phone would only boot up into the bootloader. I was able to successfully fastboot flash the TWRP recovery back onto my phone. I tried then to load in a sprint rom. Apparently I had messed up my radios, file structure and possibly other stuff, as no rom would work at that point. After much research, I found I needed to apply the RUU to get my phone back into "sprint" mode with the correct radios and file structure. I have been trying for hours now to do just that. I have tried all the methods listed on xda. The current condition of my phone: Will boot only into bootloader, will not boot into recovery although i think the TWRP recovery is still on my phone. I have the tampered, relocked, and security warning messages at the top of my phone. I am still s-on. I cannot get s-off as I have no accessible os on the phone to use the adb commands. I do have fastboot access. I have tried to fastboot flash the ruu and I get failed messages either <remote: 12 signature verify fail> or <remote: 43 main version check fail>
Any/All advice recommendations are welcome. If there is a thread about fixing bricked phones or tools to load RUU, I have tried them to no avail.
Thanks
Click to expand...
Click to collapse
Pm me your teamviewer information and I'll help you out.
bigdaddy619 said:
Have you tried running the RUU from your PC? It would also help to know if you are on 1.29 or 1.31.
Click to expand...
Click to collapse
I am on 1.31. I have tried running the RUU from my PC and I got error 140. I tried looking that up and could not find any solutions to that. I figured it was because I am on 1.31 and not 1.29 and I still had s-on. That is when I tried to get s-off so that I could apply the 1.29. Is it possible to open a fastboot shell? I was going to try to push the revone files to the phone via fastboot and then run the commands via fastboot, but didn't get around to trying that out last night.
Indirect said:
Pm me your teamviewer information and I'll help you out.
Click to expand...
Click to collapse
Thanks a bunch! I have sent you a PM. I'll send you another one when I get home from work.
MrFixit007 said:
Thanks a bunch! I have sent you a PM. I'll send you another one when I get home from work.
Click to expand...
Click to collapse
OK!! Awesome! Indirect showed me the error of my ways!! So now I have TWRP recovery back on my phone and I was able to get RUU to be successful.
What are the recommended next steps?
MrFixit007 said:
OK!! Awesome! Indirect showed me the error of my ways!! So now I have TWRP recovery back on my phone and I was able to get RUU to be successful.
What are the recommended next steps?
Click to expand...
Click to collapse
What do you want to know?
Sent from?
MrFixit007 said:
OK!! Awesome! Indirect showed me the error of my ways!! So now I have TWRP recovery back on my phone and I was able to get RUU to be successful.
What are the recommended next steps?
Click to expand...
Click to collapse
Congrats on getting phone back up. I recommend you stay away from flashing Roms that are not for Sprint but I think you learned that part first hand already.
im0rtalz said:
Congrats on getting phone back up. I recommend you stay away from flashing Roms that are not for Sprint but I think you learned that part first hand already.
Click to expand...
Click to collapse
bigdaddy619 said:
What do you want to know?
Sent from?
Click to expand...
Click to collapse
Yeah, I sure did. Coming from an OG EVO 4G that was a little bit of a nasty surprise. Wel my phone is sitting on the fastboot screen after the successful ruu. The only message at the top is **relocked***
Can i boot like normal now? Should i flash a rom at this point? i'm kinda still wearing the kid gloves...
MrFixit007 said:
Yeah, I sure did. Coming from an OG EVO 4G that was a little bit of a nasty surprise. Wel my phone is sitting on the fastboot screen after the successful ruu. The only message at the top is **relocked***
Can i boot like normal now? Should i flash a rom at this point? i'm kinda still wearing the kid gloves...
Click to expand...
Click to collapse
Did Indirect get you S-OFF? If not you need to unlock your bootloader again then re-flash TWRP or CWM then you can flash a rom. Any questions shoot me a PM
bigdaddy619 said:
Did Indirect get you S-OFF? If not you need to unlock your bootloader again then re-flash TWRP or CWM then you can flash a rom. Any questions shoot me a PM
Click to expand...
Click to collapse
We did not get to s-off. I am still s-on. the way I understand it is that basically I am back at square one... only I can use the fastboot command to unlock the bootloader, I don't need to go to the HTC website. and once i put a recovery on i can load any SPRINT ROM i want.
i'll do my best to be good this time
MrFixit007 said:
We did not get to s-off. I am still s-on. the way I understand it is that basically I am back at square one... only I can use the fastboot command to unlock the bootloader, I don't need to go to the HTC website. and once i put a recovery on i can load any SPRINT ROM i want.
i'll do my best to be good this time
Click to expand...
Click to collapse
Check PM
MrFixit007 said:
OK!! Awesome! Indirect showed me the error of my ways!! So now I have TWRP recovery back on my phone and I was able to get RUU to be successful.
What are the recommended next steps?
Click to expand...
Click to collapse
Indirect helps so many people on herr. We are lucky to have the folks in this forum.
Sent from my (M7WLS) HTC ONE.
theotrman said:
Indirect helps so many people on herr. We are lucky to have the folks in this forum.
Sent from my (M7WLS) HTC ONE.
Click to expand...
Click to collapse
Indirect is a beast
bigdaddy619 said:
Indirect is a beast
Click to expand...
Click to collapse
yep! Indirect and bigdaddy are both beasts!
theotrman said:
Indirect helps so many people on herr. We are lucky to have the folks in this forum.
Sent from my (M7WLS) HTC ONE.
Click to expand...
Click to collapse
Indirect and bigdaddy have both helped me out bunches tonight!!! I am completely back in action!!
What in the world did Indirect do that worked to well?
I'm in a similar situation right now and I'm still stuck.
NotSneakyNinja said:
What in the world did Indirect do that worked to well?
I'm in a similar situation right now and I'm still stuck.
Click to expand...
Click to collapse
Probably downgraded him from 1.31 to 1.29 so he could RUU
Sent from?
NotSneakyNinja said:
What in the world did Indirect do that worked to well?
I'm in a similar situation right now and I'm still stuck.
Click to expand...
Click to collapse
The key is knowing what fastboot commands to use and in which order. I had gotten stuck and gotten some of them out of order. I'd be willing to help you out like indirect did for me. If you PM me your teamviewer information i can help you out.
MrFixit007 said:
The key is knowing what fastboot commands to use and in which order. I had gotten stuck and gotten some of them out of order. I'd be willing to help you out like indirect did for me. If you PM me your teamviewer information i can help you out.
Click to expand...
Click to collapse
I got him fixed up