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.
Related
Well I am fairly new to here so I might not be the best in asking and explaining.
I would like to install this:
http://forum.xda-developers.com/showthread.php?t=1685433
But cannot seem to find a step by step instruction how to. I am very new to installing a ROM and need a lot of help that is much appreciated. Thanks
is your bootloader unlocked and/or are you s-off? do you have already flashed a recovery?
First of all I have no idea what or how bootloader is and what s-off and what is flashing a recovery?
I understand I am a total noob haha.
Read the stickies, they will bring you a lot further
First you will need to security-off your cellphone.
Afterwards you'll have to root the phone.
And then the custom rom fun begins!
So lemme understand, first I have to do this:
http://forum.xda-developers.com/showthread.php?t=1373697
Even for the ROM I want to run?
First you will have to find out what your Hboot version is.
You can do this by first shutting down the phone, and then holding on the volume down button while pushing the power button (no need to hold the power button).
Then you will have to search for a topic that shows you an S-OFF method for your Hboot version.
I wonder if you can help me find one for my specific version:
this is what I got
*** LOCKED ***
VIV PVT SHIP S-ON RL
HBOOT-2.01.0001
RADIO-2822.01.08.14_M
eMMC-boot
not necessarily. you can unlock via htcdev.com/bootloader. this allows you to flash a recovery. it voids your varanty tho. if you want to go the "hard way" you follow the downgrade tutorial. your waranty will not void and you can unlock the full potential of your phone.
anyway: you need to perform one of those steps to flash a recovery what you need to flash a rom.
Ok so I have completed the one from htc, now how to I proceed to doing this one?
http://forum.xda-developers.com/showthread.php?t=1685433
Not to be anoyying or anything but can someone please help me out, I have a clean phone I would like to get this ASAP so I can continue using my phone.
Mattviahtc said:
Ok so I have completed the one from htc, now how to I proceed to doing this one?
http://forum.xda-developers.com/showthread.php?t=1685433
Click to expand...
Click to collapse
have you already flashed a recovery? if not, follow this steps, to step 8: http://forum.xda-developers.com/showthread.php?t=1337105
after that you are ready to flash a rom. download the rom you want to flash and follow the instruction 8 to 14. in that example the author used cyanogenmod as rom but you can flash every rom the same way.
i just dont know if lpremix is functional at the moment. yesterday it gave me a bootloop.
For that specific one I want to install I need to install blackrose first, how do I proceed to doing that?
Since you are on hboot 2.0 already I don't think you need blackrose. If you want to install blackrose you have to gain s-off via revolutionary. If I were you I would try without blackrose and if it does not work I'd try to use niks ics Rom to see if the fault is because of blackrose. If it is you have to downgrade your hboot and gain s-off. There is a tutorial in the development forum.
Sent from my HTC Incredible S using XDA
Well I have done it all and booted but now it had been around 20 mins with just the htc logo and it seems to be getting warm. Should I wait some more? It seems its a very big file so I think it should take a while to boot for the first time.
Mattviahtc said:
Well I have done it all and booted but now it had been around 20 mins with just the htc logo and it seems to be getting warm. Should I wait some more? It seems its a very big file so I think it should take a while to boot for the first time.
Click to expand...
Click to collapse
Have you fastboot flashed your boot.img? It wont boot without it.
Look up a guide in this forum because I don't know off the top of my head
20 minutes with the htc logo does not sound like booting at all
please try to flash niks we want ics rom, even if it is not sense4. it should boot after a maximum of 5 minutes. if that works you have to wait for a sense4 release that actually is confirmed to work.
edit: yeah and if you are still on your unlocked and s-on, dont forget to flash boot.img manually as markj338 stated above.
I have done that now when I boot it just starts the HTC logo and after a while it goes to Recolutionary
Now I really do need help ASAP as I cant even recieve calls and texts since im not in any ROM.
since you are bootlooping now to recovery we can clearly state that the rom you are using does not work. download a rom that is known to work 100% (android 2.3 (like ARHD or nik trinity) roms or niks android 4 rom). flash that rom.
the sense4 roms do not work 100% at this moment.
I have also tried this one now:
http://forum.xda-developers.com/showthread.php?t=1687777
Yet still the same error, can you please link me to one that you mentioned?
Edit: I have also tried restoring, still keep getting this problem :l
Edit yet again: Apparently I need Blackrose for both of them. How can I install it since its ment to be installed when your booted into a ROM?
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.
OK, so I got a HTC One yesterday. Checking the development status here I decided not to bother with stock a single day and went straight ahead to prepare it for custom ROMs. While I was at it I decided to go for S-OFF as well so i would be able to flash radios in the future.
I think something went wrong, the status is: phone boots into (stock) system allright, but it will not establish a WiFi connection at all (it worked prior to S-OFFing), when I move the slider from disable to enable it says "Turning on..." and is grayed out but it is stuck there for infinity. Switching Bluetooth on and off works, but due to this glitch I fear that somehow my radio partition got corrupted (if I recall that is usually where S-OFF flags etc are stored).
Here is exactly how I proceeded: I got the revone command line tool and moonshine tool in the newest versions.
First I used revone according to the steps outlined on XDA, which worked and displayed an S-OFF in the bootloader header. To my understanding this only gave me S-OFF, so then I proceded with moonshine to install unsecure bootloader, superuser.apk and su. This tool also ran through as described without a glitch and rebooted me into the bootloader showing the custom moonshine S-OFF header. I then used the One-in-all-tool to install a custom recovery (TWRP in this case). This also worked great.
Then I was getting ready to put on a custom ROM and tried to hook the device to my PC via USB as a mass storage to copy over the custom ROMs I downloaded. At first boot HTC Tell jumped up and claimed it "fixed something because it noticed it was not as expected". I fgured this was to be expected, with the device S-OFFed and stock ROM still on it but gave it no 2nd thought. I checked and S-OFF stuck even through this.
Copying the ROMs as planned would not work, I can browse the /mnt/sdcard contents and also read files from there, but no matter how and when I try to write anything it fails with an error (device is disconnected or not ready). I then tried to sideload a filemanager with SMB client feature so I could transfer the ROMs through my local WiFi but then I noticed the glitch with the WiFi which could not be resolved even with reboots and clearing cache/dalvik cache throuch recovery.
What is my best bet now? Try to rollback the moonshine S-OFF and reinstall the original bootloader which was backed up? Just install a custom ROMs and assume all is good and it will straighten itself out? Flash the original RUU stock ROM, therefore prolly going back to stock and re-doing the entire S-OFF process? Any ideas on how to further diagnose what (if anything) is wrong? Is it all possible to roll back to a completely stock base by flashing the RUU through TWRP?
You didn't need to use Moonshine, you could've just flashed CWM/TWRP and flashed the SuperSU package to get root access. As you're S-OFF I would flash an RUU to get back to a stock state (you'll keep S-OFF) and then try to re-root using the normal methods.
What software build are you on at the moment?
Thank you for your quick reply.
FYI, I am on PN07IMG_M7_UL_JB_50_HTC_Europe_1.29.401.13_Radio_4A.14.3250.13_10.33.1150.01_release_316789_signed. That was ther software / radio version installed when it came out of the box.
However, as per advice from the guys in moonshine IRC channel I have re-flashed the boot.backup-img moonshine created when it ran and the problem with WiFi seems to be gone. I will play around a bit more, but it could be the issue is resolved (although I fail to understand eactly why).
Sounds like the custom HBOOT could be the issue
Yes, I have just now understood how HBOOT and the bootloader / boot.img are two separate things.
I think my reasoning for using both tools was kind of: "well, instructions for moonshine say it needs a HTCDEV unlocked device to run, and then will install su / superuser.apk in one swoop, yet revone will S-OFF / unlock my phone without hopping through the HTCDEV hoops, so hell, I will just use revone to S-OFF / unlock and then moonshine to S-OFF again and get su / superuser.apk conveniently..." The facepalm in this might be obvious to the hardcore / experienced coders / developers here but it made sense for my layman brain (at least at that late time of night...).
The question at hand is resolved though, the device behaves just fine as of now.
Out of curiosity, what would happen if I went and flashed the entirety of the stock RUU (including all partitions like recovery, ramdisk, radio, hboot, etc) through TWRP? Would that work at all? And would it, as I presume, return the device to completely bone-stock-out-of-the-box or would there still be traces modifications?
Walter_White said:
Out of curiosity, what would happen if I went and flashed the entirety of the stock RUU (including all partitions like recovery, ramdisk, radio, hboot, etc) through TWRP? Would that work at all? And would it, as I presume, return the device to completely bone-stock-out-of-the-box or would there still be traces modifications?
Click to expand...
Click to collapse
Not all of that stuff can be flashed in recovery. Some partitions like hboot have to be flashed in rebootRUU mode. You can return to stock that way, but running a RUU is simpler and usually safer (provided you have the right RUU).
Hello all,
Firstly, I've got a (still unlocked) U.S. dev edition with S-On and Hboot 1.44.0000. I've been trying to install yesterday's OTA, but I can't seem to do it. The only changes I've made to my One since I got it were rooting it and installing TWRP in order to flash the MoDaCo toolkit. I understand that the stock recovery is needed to flash OTAs, and so I used fastboot to flash the stock recovery, but when I try to install the update, the progress bar in the recovery goes about 1/4 of the way and then it stops and displays the red triangle with exclamation mark. I'm not sure what I'm doing wrong, honestly.
I've seen varying advice aimed at other people also having difficulty suggesting I need to relock the bootloader (though as a dev edition, it was never locked, right?) or to get S-Off and then flash it somehow, so I'm not entirely sure what to do. I'd rather not resort to using a RUU as I will lose all of my data.
I didn't think a developer edition phone would be this difficult to deal with, as I've never had any problems flashing countless ROMs, kernels, etc with other android devices. I've never had an HTC phone though, so I've got no experience with S-On/Off, and to be honest I still don't understand what it is.
Anyway, how should I proceed? Thank you.
http://forum.xda-developers.com/showthread.php?t=2265618
Thank you for that, but I mentioned that I didn't want to use RUUs. There has to be a way to do this without losing my data.
1) Put your phone in s-off now that you have the 1.44 hboot, trust me is better for you.
2) Maybe you have a custom kernel.
For install OTA you need stock rom, stock recovery and stock kernel.
3) Maybe more info can help us
Deksloc said:
Hello all,
Firstly, I've got a (still unlocked) U.S. dev edition with S-On and Hboot 1.44.0000. I've been trying to install yesterday's OTA, but I can't seem to do it. The only changes I've made to my One since I got it were rooting it and installing TWRP in order to flash the MoDaCo toolkit. I understand that the stock recovery is needed to flash OTAs, and so I used fastboot to flash the stock recovery, but when I try to install the update, the progress bar in the recovery goes about 1/4 of the way and then it stops and displays the red triangle with exclamation mark. I'm not sure what I'm doing wrong, honestly.
I've seen varying advice aimed at other people also having difficulty suggesting I need to relock the bootloader (though as a dev edition, it was never locked, right?) or to get S-Off and then flash it somehow, so I'm not entirely sure what to do. I'd rather not resort to using a RUU as I will lose all of my data.
I didn't think a developer edition phone would be this difficult to deal with, as I've never had any problems flashing countless ROMs, kernels, etc with other android devices. I've never had an HTC phone though, so I've got no experience with S-On/Off, and to be honest I still don't understand what it is.
Anyway, how should I proceed? Thank you.
Click to expand...
Click to collapse
I'm having the exact same issues. I'm on HBOOT 1.44, S-On (I'd love to get S-Off, but revone keeps giving me error code -1...), and previously got the OTA's to work by flashing stock recovery, running the OTA, then reflashing TWRP. This one doesn't seem to work that way, though. If you figure anything out, or find the right stock recovery, please do share!
I've been struggling with this for over a day now.
I unlocked and rooted my phone just fine (HTC One on Sprint, 4.3) - but when I flashed a ROM, I flashed Maximus HD, which was apparently an International version and not a Sprint one. I think that messed some things up. After trying a few different ROMs on top of that, nothing works.
Each ROM I flash will "install" correctly, but when it boots to the lock screen, upon unlocking it gives me the HTC splash screen.
I'm convinced that my accidental upgrade to hboot 1.55 is rendering it impossible for me to flash any working ROMs - be it stock or otherwise. I can enter Recovery mode, adb sideload, and flash ROMs, but none of them work.
I've tried Superwipe and then Bad Boyz, but it's the same thing. After installation, it sticks at the HTC splash screen.
So, my options are limited. I think I need to find a way to revert my hboot to 1.44 from 1.55 - that way at least the stock RUU is compatible. However, I can't find any way to do this; since I'm S-On, and I can't access any ROM to mess with settings, I have no idea how to do this, or how to flash a workable ROM in order to switch to S-Off.
Anyone have any ideas. I'm seriously distraught. I just bought this phone, and I love it. I'm so sad that I decided to try this rooting/unlocking/ROM flashing business because it's disrupted my sanity.
Any thoughts or ideas will help immensely. I will give more information if needed. Thanks!
WayneQuasar said:
I've been struggling with this for over a day now.
I unlocked and rooted my phone just fine (HTC One on Sprint, 4.3) - but when I flashed a ROM, I flashed Maximus HD, which was apparently an International version and not a Sprint one. I think that messed some things up. After trying a few different ROMs on top of that, nothing works.
Each ROM I flash will "install" correctly, but when it boots to the lock screen, upon unlocking it gives me the HTC splash screen.
I'm convinced that my accidental upgrade to hboot 1.55 is rendering it impossible for me to flash any working ROMs - be it stock or otherwise. I can enter Recovery mode, adb sideload, and flash ROMs, but none of them work.
I've tried Superwipe and then Bad Boyz, but it's the same thing. After installation, it sticks at the HTC splash screen.
So, my options are limited. I think I need to find a way to revert my hboot to 1.44 from 1.55 - that way at least the stock RUU is compatible. However, I can't find any way to do this; since I'm S-On, and I can't access any ROM to mess with settings, I have no idea how to do this, or how to flash a workable ROM in order to switch to S-Off.
Anyone have any ideas. I'm seriously distraught. I just bought this phone, and I love it. I'm so sad that I decided to try this rooting/unlocking/ROM flashing business because it's disrupted my sanity.
Any thoughts or ideas will help immensely. I will give more information if needed. Thanks!
Click to expand...
Click to collapse
Check PM
same problem like TS have
Having the same issues like TS..
Can somebody point me where to look for the answers,the difference is that im on .44 boot
Somebody please
MeiTeS said:
Having the same issues like TS..
Can somebody point me where to look for the answers,the difference is that im on .44 boot
Somebody please
Click to expand...
Click to collapse
Look HERE