Database Develop

[Q] HBOOT 1.16.0000, known ROMs to work?

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.

Need help here urgently

I've helped my friend to flash his Incredible S and i've experienced problems in the process. He Has a HBOOT version of 1.16.0000 and has a radio version of 3805.09.03.27_M. I've attempted to unlock the bootloader using the htcdev website's method. All the steps went well but after all the procedures, the phone still appears as S-ON. I've managed to flash the recovery into the phone and used it to flash a custom rom (Android Revolution) and rebooted the phone after the flashing is complete. The phone just gets stuck at the HTC logo with white background. I've then decided to revert everything back to normal by flashing back to stock with the official RUU but i had error 150 while flashing. I've also tried renaming the rom.zip into PG32IMG.zip to flash it through HBOOT but nothing happens. I'm really lost now, can someone give me a solution to it?

verx123 said:
I've helped my friend to flash his Incredible S and i've experienced problems in the process. He Has a HBOOT version of 1.16.0000 and has a radio version of 3805.09.03.27_M. I've attempted to unlock the bootloader using the htcdev website's method. All the steps went well but after all the procedures, the phone still appears as S-ON. I've managed to flash the recovery into the phone and used it to flash a custom rom (Android Revolution) and rebooted the phone after the flashing is complete. The phone just gets stuck at the HTC logo with white background. I've then decided to revert everything back to normal by flashing back to stock with the official RUU but i had error 150 while flashing. I've also tried renaming the rom.zip into PG32IMG.zip to flash it through HBOOT but nothing happens. I'm really lost now, can someone give me a solution to it?
Click to expand...
Click to collapse
s-on will be there...u will just be able to use custom recovery. try flashing a custom rom different from Android Revolution . by the way ..in android revolution you can also try to flash the "revert to stock 1.0 Ghz" patch because sometimes it causes that problem due to OC settings not suiting a phone.
want s-off too? See this

ajeya said:
s-on will be there...u will just be able to use custom recovery. try flashing a custom rom different from Android Revolution . by the way ..in android revolution you can also try to flash the "revert to stock 1.0 Ghz" patch because sometimes it causes that problem due to OC settings not suiting a phone.
want s-off too? See this
Click to expand...
Click to collapse
just wanna ask! how to revert to stock 1.0ghz!

I thank you for your reply.another question, can I still flash to
a sense based ROM?
Sent from my GT-N7000 using XDA App

verx123 said:
I thank you for your reply.another question, can I still flash to
a sense based ROM?
Sent from my GT-N7000 using XDA App
Click to expand...
Click to collapse
One other tip since you are dealing with an unlocked HBOOT version. When you flash a custom ROM in recovery mode you must then manually flash the boot.img file from the zip file in Fastboot mode using the command:
Fastboot flash boot [path to boot.img]

tpbklake said:
One other tip since you are dealing with an unlocked HBOOT version. When you flash a custom ROM in recovery mode you must then manually flash the boot.img file from the zip file in Fastboot mode using the command:
Fastboot flash boot [path to boot.img]
Click to expand...
Click to collapse
Umm, the path to boot.img is the root of the sdcard am i right?

Thanks guys i managed to get it S-offed and flashed to a sense 3.5 rom. But i have another problem now, my signals are super low, most of the time it write limited services. I've flashed to another radio version but the signal's still the same weak.

santhoshpirate said:
just wanna ask! how to revert to stock 1.0ghz!
Click to expand...
Click to collapse
by flashing this patch in ARHD rom !
---------- Post added at 09:52 PM ---------- Previous post was at 09:50 PM ----------
verx123 said:
Thanks guys i managed to get it S-offed and flashed to a sense 3.5 rom. But i have another problem now, my signals are super low, most of the time it write limited services. I've flashed to another radio version but the signal's still the same weak.
Click to expand...
Click to collapse
what radios have u tried? were the signals good enough before ?

It was normal until I flashed to the sense 3.5 ROM, but I've found a solution to it by flashing to an older radio version.thanks for helping me out
Sent from my GT-N7000 using XDA App

[Q] S-Off but kernel still locked?

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.

Sprint HTC One keeps rebooting after ROM install

I've unlocked bootloader, flashed recovery, and have tried installing several different roms, wiping the cache each time. Each one has heralded the same result though, after boot up after about 10 seconds of being able to use the phone, it will just restart. This has gotten me very frustrated. Any ideas?

Dysnomia said:
I've unlocked bootloader, flashed recovery, and have tried installing several different roms, wiping the cache each time. Each one has heralded the same result though, after boot up after about 10 seconds of being able to use the phone, it will just restart. This has gotten me very frustrated. Any ideas?
Click to expand...
Click to collapse
if you're using twrp, select wipe from main menu>advanced wipe>select dalviccache, cache, data, and system, then flash rom.

Which roms have you installed?
Sent from my HTCONE using Tapatalk 4 Beta

Dysnomia said:
I've unlocked bootloader, flashed recovery, and have tried installing several different roms, wiping the cache each time. Each one has heralded the same result though, after boot up after about 10 seconds of being able to use the phone, it will just restart. This has gotten me very frustrated. Any ideas?
Click to expand...
Click to collapse
krazyflipj said:
Which roms have you installed?
Sent from my HTCONE using Tapatalk 4 Beta
Click to expand...
Click to collapse
This. In particular, the first one you installed, because this sounds suspiciously like what happens when someone flashes a GSM ROM.

Rirere said:
This. In particular, the first one you installed, because this sounds suspiciously like what happens when someone flashes a GSM ROM.
Click to expand...
Click to collapse
I'm having the same problem except I think it's because I flashed the wrong kernel. It was an m7 instead of m7spr kernel. IDK how it even happened but my phone boots up with no signal. I can get to the settings quick enough and noticed baseband says unknown. Tried restoring a sense backup and installing different kernels.
Edit: Actually I flashed a kernel here in the Sprint HTC One forum. It was an aosp rom and an aosp kernel. But still no matter what I do I can't get it to stay booted.

Rirere said:
This. In particular, the first one you installed, because this sounds suspiciously like what happens when someone flashes a GSM ROM.
Click to expand...
Click to collapse
Yes, actually I accidentally downloaded the 4.3 google edition leak rom without realizing it wasnt for the sprint version

insuusvenerati said:
I'm having the same problem except I think it's because I flashed the wrong kernel. It was an m7 instead of m7spr kernel. IDK how it even happened but my phone boots up with no signal. I can get to the settings quick enough and noticed baseband says unknown. Tried restoring a sense backup and installing different kernels.
Edit: Actually I flashed a kernel here in the Sprint HTC One forum. It was an aosp rom and an aosp kernel. But still no matter what I do I can't get it to stay booted.
Click to expand...
Click to collapse
This is exactly the problem I'm having now if I install any other rom

So I relocked the bootloader and tried installing a stock ruu, but I just get an error message, no idea what to do. -_-

Ok, so apparently I need to get S-Off to use the older RUU, but can't seem to get revone working because I cant boot up for more than 15 seconds, can someone help here?

Dysnomia said:
Ok, so apparently I need to get S-Off to use the older RUU, but can't seem to get revone working because I cant boot up for more than 15 seconds, can someone help here?
Click to expand...
Click to collapse
Try this [http://forum.xda-developers.com/showthread.php?t=2251800] It helped my problem. Erased everything from the device but I had it backed up anyway. You do not need s-off but you need to relock your bootloader. It's really easy tho. Google message me or PM me here if you need help.

insuusvenerati said:
Try this [http://forum.xda-developers.com/showthread.php?t=2251800] It helped my problem. Erased everything from the device but I had it backed up anyway. You do not need s-off but you need to relock your bootloader. It's really easy tho. Google message me or PM me here if you need help.
Click to expand...
Click to collapse
already said I can't use that one because I already updated my phone to 1.31.651.2

Dysnomia said:
already said I can't use that one because I already updated my phone to 1.31.651.2
Click to expand...
Click to collapse
im on the same version have you found a solution yet???

Tlalok08 said:
im on the same version have you found a solution yet???
Click to expand...
Click to collapse
if you s-off you can use the .10 ruu (revone s-off method still works moonshine does not)

Aldo101t said:
if you s-off you can use the .10 ruu (revone s-off method still works moonshine does not)
Click to expand...
Click to collapse
i will give that a shot

Tlalok08 said:
im on the same version have you found a solution yet???
Click to expand...
Click to collapse
Ok, I tried flashing another rom, still same results. But, this one revone actually worked with, achieved S-Off and flashed the RUU.

where can i get the revone ??? sorry it this is a dumb question...

Tlalok08 said:
where can i get the revone ??? sorry it this is a dumb question...
Click to expand...
Click to collapse
There is a sticky in this forum that has the info for s off. Also in one of the dev forums there is an all in one tool that makes using revone easy.

Tlalok08 said:
where can i get the revone ??? sorry it this is a dumb question...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2319412
Or you can use this tool
http://forum.xda-developers.com/showthread.php?t=2236814

Dysnomia said:
Ok, I tried flashing another rom, still same results. But, this one revone actually worked with, achieved S-Off and flashed the RUU.
Click to expand...
Click to collapse
hi,
which rom did you install which allowed you to get revone onto the device?

ya im in the same boat. loaded a rim labeled as a sprint rom, when in aroma, i asked att tmobi or international, i selected international. had this problem ever since. just got my phone maybe 2 days ago. familiar withh rooting and android, fastboot and what not, this is my 4th htc. hero, evo , evo3d and now this please tell me it's not dead. i'm not used to all this no sd card stuff. =[

[Q] HTC Vivid Bootloop, Unlocked bootloader, S-On, TWRP installed.

Hi,
I got this phone today, and unlocked the bootloader using the htcdev website. I then flashed a rom, and wiped, and then flashed the boot.img using fastboot. It worked fine, but the cyanogenmod nightly wasn't very stable. I decided to flash a different rom, but I couldn't get anything else to work. The roms, now including the previous rom, don't boot past their boot animations and shut down and boot again. Any help would be much appreciated!
Also, when I power down from the bootloader it tries to start up again. I have to pull the battery.
Also, it's an AT&T version. ROM recommendations are needed, because I can't get anything to work. :'( Preferably de-sensitized. I've check the dev thread with all the ROMS and links.

Make sure you are doing full wipes for each rom and also flashing the boot image.
Sent from my HTC One

I do that
WildfireDEV said:
Make sure you are doing full wipes for each rom and also flashing the boot image.
Click to expand...
Click to collapse
Yeah, I do that, using the factory reset in twrp and then install the rom, and then I flash the boot image using
fastboot flash boot boot.img
which flashes it no problem. I did actually get the cyanogenmod to work, which is interesting.

Update
I've gotten a ROM to work. It's http://forum.xda-developers.com/showthread.php?t=1428726 A sensed ROM. Hmm...

Geckodudes said:
I've gotten a ROM to work. It's http://forum.xda-developers.com/showthread.php?t=1428726 A sensed ROM. Hmm...
Click to expand...
Click to collapse
You need to update to ICS first, otherwise it won't boot any JB or KitKat ROM.
Then S-off your device, it's really easy

Viajanteluz said:
You need to update to ICS first, otherwise it won't boot any JB or KitKat ROM.
Then S-off your device, it's really easy
Click to expand...
Click to collapse
Thanks! I'm running the "leaked" RUU which is supposed to update the firmware to ICS, right? Can you provide a link to S-off? I can't find anything. Well actually I can, but I can't understand it. :/

There you go: http://forum.xda-developers.com/showthread.php?t=2521157
I've changed CiD? because of Vodafone not updating to ICS.
Then upgraded with an AT&T ICS RUU - http://forum.xda-developers.com/showthread.php?t=2013122

Solved.
Viajanteluz said:
There you go: http://forum.xda-developers.com/showthread.php?t=2521157
I've changed CiD? because of Vodafone not updating to ICS.
Then upgraded with an AT&T ICS RUU - http://forum.xda-developers.com/showthread.php?t=2013122
Click to expand...
Click to collapse
Thanks. I updated to ICS and all the roms I've tried work great. Thanks a lot!

Geckodudes said:
Thanks. I updated to ICS and all the roms I've tried work great. Thanks a lot!
Click to expand...
Click to collapse
You're Welcome! :good: