Related
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.
Hi.
It took my a while and I finally got my phone S-OFF and rooted. I just got a few questions
1)I want to use ICS but I don't like the laggy Sense. There seems to be at least few bugs in every custom ROM, so I'd like to stick with stock ROMs. But is there a way to "get rid of sense" or to at least mod it to be faster? Or perhaps there is another solution?
2)I read that if I use OTA updates my recovery will revert back to stock (using CWM). Is that the same case when using official RUU's ?
tripleJohn said:
Hi.
It took my a while and I finally got my phone S-OFF and rooted. I just got a few questions
1)I want to use ICS but I don't like the laggy Sense. There seems to be at least few bugs in every custom ROM, so I'd like to stick with stock ROMs. But is there a way to "get rid of sense" or to at least mod it to be faster? Or perhaps there is another solution?
2)I read that if I use OTA updates my recovery will revert back to stock (using CWM). Is that the same case when using official RUU's ?
Click to expand...
Click to collapse
Now that you have S-OFF, stay away from any official HTC OTA or RUU because they will leave your phone in an unbootable state and will be very frustrating for a noob.
There are several ICS ROMs both with and without Sense. You just need to try them and find one you like. Just remember that once the ICS kernel source for the IncS is released by HTC, some of the custom ROM issues may be solved.
tripleJohn said:
Hi.
It took my a while and I finally got my phone S-OFF and rooted. I just got a few questions
1)I want to use ICS but I don't like the laggy Sense. There seems to be at least few bugs in every custom ROM, so I'd like to stick with stock ROMs. But is there a way to "get rid of sense" or to at least mod it to be faster? Or perhaps there is another solution?
2)I read that if I use OTA updates my recovery will revert back to stock (using CWM). Is that the same case when using official RUU's ?
Click to expand...
Click to collapse
If u want ICS without sense, one of the smoothest rom is icecoldsandwich, works really well!
agree, icecoldsandwish is the best no sense rom
for sense you can use project x or cool droid
tpbklake said:
Now that you have S-OFF, stay away from any official HTC OTA or RUU because they will leave your phone in an unbootable state and will be very frustrating for a noob.
Click to expand...
Click to collapse
Hmmm.... Why is that so? I somewhere red that S-Off has got nothing to do with OTA.
I think it has to do with the OTA overwriting the bootloader,
by the way recommend IceCold too, there's only one thing that still keeps me on CM 7, on IceCold for some reason on-screen controls of several games don't work
I'm already trying out Ice Cold Sandwich, however I'still got a few questions:
Why do official RUU's will leave my phone in unbootable state
Should I use software like Rom manager or Root explorer ? I heard they have caused problems to other users.
If I make a backup with CWM, that counts as nandroid backup and you need root permissions for it (right?) . I was able to make backup of my stock ROM without root permissions and with S-ON. Is there a difference between those two?
sirpellinor said:
I think it has to do with the OTA overwriting the bootloader,
Click to expand...
Click to collapse
But I could re-lock my bootloader before running RUU. Would that make any difference?
tripleJohn said:
I'm already trying out Ice Cold Sandwich, however I'still got a few questions:
Why do official RUU's will leave my phone in unbootable state
Should I use software like Rom manager or Root explorer ? I heard they have caused problems to other users.
If I make a backup with CWM, that counts as nandroid backup and you need root permissions for it (right?) . I was able to make backup of my stock ROM without root permissions and with S-ON. Is there a difference between those two?
Click to expand...
Click to collapse
1. Beacause it overwrites stuff in the bootloader like recovery...
2. Yeah, you really should have a file explorer with root access. I use ES File Explorer
3. If you're doing a nandroid backup in recovery you just need CMW to restore it. But for that u need root permission And since you're S-OFF now, you couldn't make a backup of your S-ON stuff It's just the ROM that stays but your phone is S-OFF now no matter if you restore your backup
tripleJohn said:
I'm already trying out Ice Cold Sandwich, however I'still got a few questions:
Why do official RUU's will leave my phone in unbootable state
Should I use software like Rom manager or Root explorer ? I heard they have caused problems to other users.
If I make a backup with CWM, that counts as nandroid backup and you need root permissions for it (right?) . I was able to make backup of my stock ROM without root permissions and with S-ON. Is there a difference between those two?
But I could re-lock my bootloader before running RUU. Would that make any difference?
Click to expand...
Click to collapse
The problem with both the GB 2.3.5/Sense 3.0 RUU and the ICS 4.0.4/Sense 3.6 is that they introduced a new /lib partition that needs the latest HTC HBOOT to execute correctly.
With the Revolutionary HBOOT in place, it is designed to not allow itself to be overwritten, thus if you attempt to install either one of these RUUs, all of the pieces will get installed correctly except for the new HTC HBOOT, thus when you attempt to boot the phone, it attempts to mount the /lib partition and the Revolutionary HBOOT has no idea what that is and the ROM freezes at the point and will not boot.
As for your last question, now that you have the Revolutionary S-OFF HBOOT in place, you are no longer running the HTC HBOOT that is lockable/unlockable, so it is not really relevant to your phone anymore.
So, my chain of events:
Unlocked
Rooted
Custom ROM (DarkRaider, stock kernel)
Used for a while
Then:
I used the technique here to try the KangBang kernel.
androidauthority.com/vivid-2-0-ghz-overclock-custom-kernel-kangbang-106636
Used same technique above to use DarkRaider install to install kozmikernel, which worked.
But I got tired of having to use USB, etc. So I:
Relocked
RUU'd
Unlocked
Rooted
S-Off (wire trick)
Custom recovery (ClockworkMod touch beta)
And now I'm having issues like I did before S-Off. Trying a custom kernel causes it to fail and have the WiFi connectivity issues everyone mentioned, and I've experienced before. So I'm wondering, did the S-Off not work? I have the custom HBOOT and it says radio S-Off. Is it the recovery I'm using? Is there a specific one that works with kernels that I missed? Or is it something with DarkRaider? I feel like I just have selected the incorrect recovery, but don't know enough to be able to determine myself.
Thanks in advance to all. If it's just the recovery, I'd love it if you could point me to the correct one. THANKS!
drummerdick said:
So, my chain of events:
Unlocked
Rooted
Custom ROM (DarkRaider, stock kernel)
Used for a while
Then:
I used the technique here to try the KangBang kernel.
androidauthority.com/vivid-2-0-ghz-overclock-custom-kernel-kangbang-106636
Used same technique above to use DarkRaider install to install kozmikernel, which worked.
But I got tired of having to use USB, etc. So I:
Relocked
RUU'd
Unlocked
Rooted
S-Off (wire trick)
Custom recovery (ClockworkMod touch beta)
And now I'm having issues like I did before S-Off. Trying a custom kernel causes it to fail and have the WiFi connectivity issues everyone mentioned, and I've experienced before. So I'm wondering, did the S-Off not work? I have the custom HBOOT and it says radio S-Off. Is it the recovery I'm using? Is there a specific one that works with kernels that I missed? Or is it something with DarkRaider? I feel like I just have selected the incorrect recovery, but don't know enough to be able to determine myself.
Thanks in advance to all. If it's just the recovery, I'd love it if you could point me to the correct one. THANKS!
Click to expand...
Click to collapse
Well, the good news is that your S-OFF worked if it says S-OFF in HBOOT!
I have heard that people have trouble with CWM. I never did, but these days I use TWRP, and it works great for me.
Trying a custom kernel causes it to fail
Click to expand...
Click to collapse
Which kernel, what method, what error?
and have the WiFi connectivity issues everyone mentioned, and I've experienced before.
Click to expand...
Click to collapse
This is usually caused by not having kernel modules installed in the correct place, or possibly having old kernel modules in the /system/lib/modules directory that don't belong there anymore.
Be a little more specific about your errors, and one of us will surely be able to help you out!
Cheers,
Sean
ess.boyer said:
Well, the good news is that your S-OFF worked if it says S-OFF in HBOOT!
I have heard that people have trouble with CWM. I never did, but these days I use TWRP, and it works great for me.
Which kernel, what method, what error?
This is usually caused by not having kernel modules installed in the correct place, or possibly having old kernel modules in the /system/lib/modules directory that don't belong there anymore.
Be a little more specific about your errors, and one of us will surely be able to help you out!
Cheers,
Sean
Click to expand...
Click to collapse
Well, glad the S-Off worked. And thanks for the suggestion, I'll give TWRP a try and see if that helps before I go to more drastic measures.
As far as the kernel, it wasn't so much failing, as not doing what it was supposed to? I was only trying to install the kozmikernalb7 packaged with DarkRaider ROM, so it was through the aroma installer. It came up with some error when it first tried to install the Sweep to Wake, but I don't remember exactly what. But, it didn't install S2W, it wasn't overclockable, and the WiFi didn't work. I didn't really look into the wifi issues, I read somewhere on here it was that the kernel was still locked and not being overwritten properly. Whether that's true or not, I dunno. But it would work when I used the method described in that link. I don't know what was up with that special recovery they had, but I tried flashing it, and that didn't help at all. I'll update you on the TWRP when I have time to try it.
Thanks again!
drummerdick said:
Well, glad the S-Off worked. And thanks for the suggestion, I'll give TWRP a try and see if that helps before I go to more drastic measures.
As far as the kernel, it wasn't so much failing, as not doing what it was supposed to? I was only trying to install the kozmikernalb7 packaged with DarkRaider ROM, so it was through the aroma installer. It came up with some error when it first tried to install the Sweep to Wake, but I don't remember exactly what. But, it didn't install S2W, it wasn't overclockable, and the WiFi didn't work. I didn't really look into the wifi issues, I read somewhere on here it was that the kernel was still locked and not being overwritten properly. Whether that's true or not, I dunno. But it would work when I used the method described in that link. I don't know what was up with that special recovery they had, but I tried flashing it, and that didn't help at all. I'll update you on the TWRP when I have time to try it.
Thanks again!
Click to expand...
Click to collapse
I don't know about the kernel being "locked" (what is locking it?) but I had something similar happen to me when I first flashed a new kernel on this phone. No matter how many times I "successfully" flashed a new kernel through recovery, with S-OFF, it wouldn't overwrite the original stock kernel. I ended up having to install the S-ON version over fastboot, and from then on I haven't had any issues. Maybe give that a try. Try flashing the Holics or Faux kernels (S-ON method first), and if you can get them to work, go back to Kozmik's, or whatever you want.
ess.boyer said:
I don't know about the kernel being "locked" (what is locking it?) but I had something similar happen to me when I first flashed a new kernel on this phone. No matter how many times I "successfully" flashed a new kernel through recovery, with S-OFF, it wouldn't overwrite the original stock kernel. I ended up having to install the S-ON version over fastboot, and from then on I haven't had any issues. Maybe give that a try. Try flashing the Holics or Faux kernels (S-ON method first), and if you can get them to work, go back to Kozmik's, or whatever you want.
Click to expand...
Click to collapse
The "locked" kernel: from what I've read (and tried to understand) the HTC bootloader unlock removes the NAND lock on everything BUT the kernel (boot partition?). I may be mistaken on that (looks like), but that was what I got from everything I've read. I remember something similar with my Aria, things I couldn't do without S-Off, but I didn't have any issues with the Aria after S-Off. So I dunno.
I'll try the S-On method first, and see how that goes. Thanks for all your help!
drummerdick said:
The "locked" kernel: from what I've read (and tried to understand) the HTC bootloader unlock removes the NAND lock on everything BUT the kernel (boot partition?). I may be mistaken on that (looks like), but that was what I got from everything I've read. I remember something similar with my Aria, things I couldn't do without S-Off, but I didn't have any issues with the Aria after S-Off. So I dunno.
I'll try the S-On method first, and see how that goes. Thanks for all your help!
Click to expand...
Click to collapse
S-OFF for the Vivid unlocks the boot partition. You can flash unsecured kernels from Recovery, no problem. That's half (or more) the reason you'd S-OFF in the first place.
I have had an issue before where for some reason my kernel got "stuck" and I couldn't flash any other kernel over stock. I had to relock, run the RUU, unlock, then flash. Ever since then (the first week I had the phone, several months ago now) I haven't had a single problem.
Well, that was my goal S-Off, and also why I'm confused I can't flash kernels from recovery.
Did you do the re-lock, RUU, unlock, all already S-Off?
Sent from my HTC PH39100 using xda app-developers app
drummerdick said:
Well, that was my goal S-Off, and also why I'm confused I can't flash kernels from recovery.
Did you do the re-lock, RUU, unlock, all already S-Off?
Sent from my HTC PH39100 using xda app-developers app
Click to expand...
Click to collapse
That's right. You won't have to S-OFF again. S-OFF will stay through the process.
You might also be able to install a different kernel via fastboot (the S-ON method) first, and then if that works, you should be able to flash from recovery. If that doesn't work, try the lock, RUU, unlock.
ess.boyer said:
That's right. You won't have to S-OFF again. S-OFF will stay through the process.
You might also be able to install a different kernel via fastboot (the S-ON method) first, and then if that works, you should be able to flash from recovery. If that doesn't work, try the lock, RUU, unlock.
Click to expand...
Click to collapse
Ok, I'll give those a try when I get a chance, thanks.
Part of what I don't understand: the recovery image that the S-On method uses, why can't that just be flashed as the recovery on my phone? It looks exactly like the clockworkmod recovery that was on my phone. I'm loving the TWRP by the way, thanks for the tip. The file browser alone saved me from that stupid AT&T software update... (long story, and not all that interesting )
drummerdick said:
Part of what I don't understand: the recovery image that the S-On method uses, why can't that just be flashed as the recovery on my phone?
Click to expand...
Click to collapse
I think that recovery image you're talking about IS CWM, in which case, you could use it, no problem. I prefer TWRP for the touch interface, and the fact that it can restore backups larger than 2GB (which that version of CWM can't).
Well, check your bootloader.
If it says Unlocked, then you will still have the problem with flashing the kernel.
Flash the Juopunutbear hboot from http://unlimited.io/jbhboots.htm
Your bootloader should say = Juopunutbear = where it says LOCKED or UNLOCKED.
You should be able to flash kernels through recovery without any problems after that.
kgs1992 said:
Well, check your bootloader.
If it says Unlocked, then you will still have the problem with flashing the kernel.
Flash the Juopunutbear hboot from http://unlimited.io/jbhboots.htm
Your bootloader should say = Juopunutbear = where it says LOCKED or UNLOCKED.
You should be able to flash kernels through recovery without any problems after that.
Click to expand...
Click to collapse
I did flash the Juopunutbear HBOOT, and it does say it on the HBOOT screen. This is also part of my confusion why I'm having trouble
I think that recovery image you're talking about IS CWM, in which case, you could use it, no problem. I prefer TWRP for the touch interface, and the fact that it can restore backups larger than 2GB (which that version of CWM can't).
Click to expand...
Click to collapse
I tried just flashing the .img file from the S-On method in fastboot, but I don't think that worked. I thought I'd try that since that was supposed to be the one that was able to flash kernels. I think I ended up with a bootloop after that, lol, so I switched it back.
drummerdick said:
I did flash the Juopunutbear HBOOT, and it does say it on the HBOOT screen. This is also part of my confusion why I'm having trouble
I tried just flashing the .img file from the S-On method in fastboot, but I don't think that worked. I thought I'd try that since that was supposed to be the one that was able to flash kernels. I think I ended up with a bootloop after that, lol, so I switched it back.
Click to expand...
Click to collapse
Verify that the MD5sums for the downloaded files matches the ones provided in the respective threads.
I honestly can't believe I am asking such a rudimentary question with how long I've been here, but it's always been "htcdev root then s-off exploit" before.
Now though, I have the option of just simply installing Weaksauce to get a temproot... then running that Firewater adb script with that temproot to get S-OFF, essentially getting S-OFF without needing a (permanent) root first.
To be honest, the only reason I even want root right now is to install that app/patcher that removes the SD card restrictions KitKat added. Again, before since I had to use htcdev first I would root, then install a rooted rom, then get S-OFF, so I already had a permrooted rom before I gained S-OFF. If I already have S-OFF(that means I have full access to the entire flashrom right?), would I still not have root access because the rom itself doesn't give me that access? And if so, can I just modify a permissions file or something similar, or would I need to flash a rooted version of the stock rom? I know those exist, but since I just got this phone I don't want to heavily modify it's software just yet. I know it will still have bloatware, and as much as I hate it, almost all of it is uninstallable on the stock Sprint M8 rom (wish I coudl get rid of Sprint Zone and Sprint ID though).
Well, that, and the other reason is because this phone basically came out less than a month ago, and already had a firmware update from Sprint, it is sure to get more updates down the road. Would rooting and getting S-OFF prevent me from installing official updates? (I don't want to have to wait for a modified version to become available, and if I was going to go down that route, I might as well just use a custom rom). Or could an official update lock me back to S-ON and require me to run the exploit again (providing they didn't also patch said exploit in the update)?
Oh, and oen final thing, because I constantly hear that changing the battery (admittedly, not an issue with the M8) or doing this or that breaks Google Wallet for security purposes, would doing any of this stop Google Wallet and it's NFC features from working?
Weaksauce doesn't work on the Sprint M8.
And of course you can still take OTA updates while S-OFF (as long as your system is completely stock and you have the stock recovery).
Captain_Throwback said:
Weaksauce doesn't work on the Sprint M8.
Click to expand...
Click to collapse
Oh, I was under the impression that it could
So then my only option is the htcdev unlock? I really want to avoid basically telling HTC "Don't let this IMEI have any warranty service" if I can. I still won't have any issues getting S-OFF if I use the htcdev method though, right?
Cyber Akuma said:
Oh, I was under the impression that it could
So then my only option is the htcdev unlock? I really want to avoid basically telling HTC "Don't let this IMEI have any warranty service" if I can. I still won't have any issues getting S-OFF if I use the htcdev method though, right?
Click to expand...
Click to collapse
No, HTC Dev won't interfere with you gaining S-off.
So, does anybody know about the Google Wallet thing?
Cyber Akuma said:
So, does anybody know about the Google Wallet thing?
Click to expand...
Click to collapse
What "thing" are you referring to?
Sent from my HTC device
FinZ28 said:
What "thing" are you referring to?
Sent from my HTC device
Click to expand...
Click to collapse
Last line in my original post:
Oh, and oen final thing, because I constantly hear that changing the battery (admittedly, not an issue with the M8) or doing this or that breaks Google Wallet for security purposes, would doing any of this stop Google Wallet and it's NFC features from working?
Click to expand...
Click to collapse
Google Wallet and all its features should work just fine.
Sent from my HTC device
FinZ28 said:
Google Wallet and all its features should work just fine.
Sent from my HTC device
Click to expand...
Click to collapse
Fin is correct, that was an issue with the EVO LTE when it first came out, people were not first disabling Wallet before they flashed, and this caused an issue with app reinstallation. I believe that was resolved many updates ago for wallet.
03orlandor6 said:
Fin is correct, that was an issue with the EVO LTE when it first came out, people were not first disabling Wallet before they flashed, and this caused an issue with app reinstallation. I believe that was resolved many updates ago for wallet.
Click to expand...
Click to collapse
Thank you for the detailed response, It's a great help when people also explain why something does or doesn't work in some way.
So basically, to summarize, for a Sprint M8 I can only use the official dev unlock, and even the temporarily root methods don't work, but after I use the dev unlock I can run firewater to get S-Off?
I am going to have to install a rom with root access after I use the dev unlock though and not be able to rely on the Stock rom through aren't I? I can still get a rom that is 100% the stock rom, just with root access though, right?
Would I have to worry about anything or an OTA resetting me to S-ON? Especially if it can fix the exploit that currently allows for S-Off?
Cyber Akuma said:
Thank you for the detailed response, It's a great help when people also explain why something does or doesn't work in some way.
So basically, to summarize, for a Sprint M8 I can only use the official dev unlock, and even the temporarily root methods don't work, but after I use the dev unlock I can run firewater to get S-Off?
I am going to have to install a rom with root access after I use the dev unlock though and not be able to rely on the Stock rom through aren't I? I can still get a rom that is 100% the stock rom, just with root access though, right?
Would I have to worry about anything or an OTA resetting me to S-ON? Especially if it can fix the exploit that currently allows for S-Off?
Click to expand...
Click to collapse
Yes, use HTC Dev to unlock, install a custom recovery, then flash SuperSU for root access. You can then use Firewater to gain S-off. You can stay on the stock ROM, just be warned that you'll get update notifications if you aren't on the latest OTA update. Having said that, you won't be able to install said update unless you reinstall the stock recovery.
Sent from my HTC device
FinZ28 said:
Having said that, you won't be able to install said update unless you reinstall the stock recovery.
Click to expand...
Click to collapse
It's only the recovery that matters? Not the S-Off or having Dev unlock or anything else? And only for installing a stock update, not running it after it's been installed?
Isn't that easy to flash and re-flash? Can't I just easily re-flash back to a stock recovery, install the OTA, then flash back?
Oh, and can I lose S-Off in a future update or something this way? Or is it permanent once applied? (Although I know you can hex-exit the bootloader to make it look like it's still S-On, not sure if I want to do that since it sounds extremely risky).
Cyber Akuma said:
It's only the recovery that matters? Not the S-Off or having Dev unlock or anything else? And only for installing a stock update, not running it after it's been installed?
Isn't that easy to flash and re-flash? Can't I just easily re-flash back to a stock recovery, install the OTA, then flash back?
Oh, and can I lose S-Off in a future update or something this way? Or is it permanent once applied? (Although I know you can hex-exit the bootloader to make it look like it's still S-On, not sure if I want to do that since it sounds extremely risky).
Click to expand...
Click to collapse
It's that easy, yes, and no, you can't lose S-off by applying an OTA update. Take a look at the thread in the link below for more info:
http://forum.xda-developers.com/showthread.php?t=2720558
Sent from my HTC device
So I just recently had to get my previous HTC one m8 replaced . I have the bootloader unlocked, twrp installed and rooted all using the windroid toolkit. I'm running into issues with s-off though. Apparently since I last did this Firewater has been discountinued and replaced with sunshine? I have sunshine installed and it fails the compatibility check. Saying that it will not work on my device and that it is a known issue. Is there anyway I can s-off? Or am I just out of luck? I have software version 3.30.651.2 and am running on android 4.4.4 on the stock Rom that I just rooted. All help is appreciated��. Thanks!
opeth115 said:
So I just recently had to get my previous HTC one m8 replaced . I have the bootloader unlocked, twrp installed and rooted all using the windroid toolkit. I'm running into issues with s-off though. Apparently since I last did this Firewater has been discountinued and replaced with sunshine? I have sunshine installed and it fails the compatibility check. Saying that it will not work on my device and that it is a known issue. Is there anyway I can s-off? Or am I just out of luck? I have software version 3.30.651.2 and am running on android 4.4.4 on the stock Rom that I just rooted. All help is appreciated��. Thanks!
Click to expand...
Click to collapse
Sounds like you need a compatible kernel
Would you have a kernel in mind I need to flash? Is it as easy as flashing through twrp or am I going to have to us adb? I have no problem with adb just not to well versed in everything relating to it.
opeth115 said:
Would you have a kernel in mind I need to flash? Is it as easy as flashing through twrp or am I going to have to us adb? I have no problem with adb just not to well versed in everything relating to it.
Click to expand...
Click to collapse
Easiest way to run SunShine is to RUU and be completely stock,locked, ect.
If it still say incompatible then you are not going to get it to work no matter what you try
BD619 said:
Easiest way to run SunShine is to RUU and be completely stock,locked, ect.
If it still say incompatible then you are not going to get it to work no matter what you try
Click to expand...
Click to collapse
Well that sucks i guess.... Just did an RUU. Was completely stock, on the most updated firmware. No root or anything. It attempted to fake a root, i guess, to check everything and it would just reboot my phone. I reunlocked, rerooted, and reinstalled twrp and still no go. Guess I'm out of luck :crying: