Related
im gona send my phone in as a replacement, but i want to make sure everything looks stock before it send it in, i found a couple of ways to return to stock but i keep getting signiture verified failed, and i assume its because i have an unlocked bootloader, can any 1 help?
You should be able to find the stock rom for unlocked users in the development section. Just flash that and you will be back on stock.
But you can't re-lock the bootloader. When you unlocked it you voided the warranty, and it stays that way.
If it is a physical hardware problem, you should be able to still get warranty though.
Sorry, I meant to say my bootloader is locked, I don't have a problem with the rom, but the recovery. I am on ra recovery atm and I want to go back to google's stock. Is there anyway to do that?
Im pretty sure this works for all phones but if you flash Official OTA it will put everything back to stock(except bootloader if it has been unlocked) but doing this you will also loose root as well
i would wait for some one to tell you another way to get back to stock recovery, im sure there is a way to do it in adb or something.. Flashing the official OTA should be like a last thing wanting to do
Look for the stock recovery Tom for your phone then just flash with fastboot. That's the easiest way that I. Did it.
sent from outter space
codearray said:
Look for the stock recovery Tom for your phone then just flash with fastboot. That's the easiest way that I. Did it.
sent from outter space
Click to expand...
Click to collapse
He cant do fastboot, he has locked Bootloader.
yeah, it saids verification failed and wouldnt let me flash anything onto it
oops my bad. I had an unlocked bootloader. My other phone is locked.
sent from outter space
vvaffles said:
yeah, it saids verification failed and wouldnt let me flash anything onto it
Click to expand...
Click to collapse
Yeah i had the same problem when i tried to revert mine to stock. My bootloader was lock and wouldnt let me reflash the stock rom with verification failed.
NOT SURE IF THIS IS THE CORRECT WAY, DO AT YOUR OWN RISK :
I renamed the image to PASSIMG.zip and booted into bootloader. The bootloader automatically searches for PASSIMG and when it found it went through an update/installing process which took about 5minutes. When it booted phone was unrooted again, and had the stock recovery.
Once that was done, i installed the FRF85 (i think) update.zip from bootloader recovery, then did the same with update.zip for FRF91.
Again not sure if this was the correct way as i have never seen posts directing to do it this way - have posted questions about it in the past week or two, but never got any responses...
I'm gonna bump this thread up again. I tried downloading the original PASSIMG file for the stock and when I try and flash it by putting it on the SD card I get that the main file is older and the install is aborted. I can't fastboot the files because my bootloader is not unlocked. I'm currently running a FRG83 based ROM, does this matter? I'd like to return my phone to stock recovery and stock ROM, but so far every attempt has been met in failure... I guess it's an irony of rooting a phone without unlocking a bootloader. If you have to send it in for repairs you have to unlock the bootloader to return to stock, or you can't return to stock and you're left with custom recovery and root... either way HTC knows you're rooted. I know my issue is a hardware issue, but it would be my luck they decide to void my whole warranty.
You can't just PASSIMG your way back from FRG83, if you have it - since there's no PASSIMG for FRG83 yet (at least I'm not aware of one, and looks like Google isn't either), and the system is designed not to flash older builds. Trying to use PASSIMG to return to older builds requires some heavy preparations (has to be rooted, then downgrading HBOOT and probably flashing initial system.img from an older build through adb in recovery, using flash_image). It's possible and not very hard to do, but most probably beyond "1-click-root"ers' skills. All the relevant info is in the Wiki, so if you want to attempt it - you can try.
Unrooting FRG83 (reflashing stock recovery from FRF91, removing su and Superuser.apk from root shell) might be easier.
Also, put attention that if the phone has SLCD screen - the official stock FRF91 won't work on it.
I actually was able to PASSIMG to FRG33 then OTA back to FRG83. which I thought was odd due to the fact that I was on a FRG83 based rom. Oh well, it's 100% back to stock now. So even though people say that a rooted/unlocked phone only voids your software warranty I don't have to worry about it. Yay for keeping a locked bootloader.
I've recently gotten a Unlocked Bell (but Unrooted!) IS with Froyo on it.
I check the system software update and the gingerbread update is available for download and whatnot.
I download it and click to install but it stops after a restart on the bootloader screen where I see the install package cannot open. (You know the screen with the blue android and exclamation mark)
Is it REQUIRED that I need to root the IS to update the phone to 2.3?
I'm under Telus btw.
-Canada-
Thanks
sdkim89 said:
I've recently gotten a Unlocked Bell (but Unrooted!) IS with Froyo on it.
I check the system software update and the gingerbread update is available for download and whatnot.
I download it and click to install but it stops after a restart on the bootloader screen where I see the install package cannot open. (You know the screen with the blue android and exclamation mark)
Is it REQUIRED that I need to root the IS to update the phone to 2.3?
I'm under Telus btw.
-Canada-
Thanks
Click to expand...
Click to collapse
Since your IncS is carrier unlocked, you are trying to load a Bell GB update on the phone and I bet it is checking to see if the phone has a Bell CID (which it doesn't since you have unlocked it).
You would be better off running AlphaRevX Revolutionary to S-OFF and install ClockworkMod recovery. After that process you would then be able to install a rooted version of the IncS WWE Gingerbread ROM and lose all of the Bell bloatware.
I'm just very unsure about rooting IS 'cause it says its still in the beta stages so, I'm trying to optimize my phone as much as it's able before considering rooting (which I'm sure everyone is trying to).
Also not sure if anything will go wrong and such 'cause it's in beta
Had the Desire before and everything was sure 100% hence.
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.
Yesterday I received my one from T-Mobile UK with 1.28.61.7 on board. I am not quite a noob but I have always had devices with WWE un-branded firmwares. There is no bloatware on the device but I guess that, until s-off, I am dependant on T-Mobile to provide updates.
I am not particularly bothered about custom roms and, in the past I have usually gone with stock rooted roms so that I can go add-free and remove anything that I do not require.
Last night I lied awake thinking about the implications about what I have and I really need some informed advice about it.
If I root my device, how can I return it to stock in the future so that I can receive any ota updates that T-Mobile may eventually offer without a RUU which appear to be quite scarce?
Am I able to install custom firmwares based on higher firmwares ie. 1.29.401.12 and, if yes, will I be able to return my device back to stock without an RUU as backup?
I am most confused about the scenario which I have. I love the device apart from the 3 dot menu bar which is doing my head in and am confident in my ability to remove it but am worried about my safety net if something goes wrong. Please somebody enlighten me as to what I am and are not able to do. Thanks in advance.
bobsie41 said:
Yesterday I received my one from T-Mobile UK with 1.28.61.7 on board. I am not quite a noob but I have always had devices with WWE un-branded firmwares. There is no bloatware on the device but I guess that, until s-off, I am dependant on T-Mobile to provide updates.
I am not particularly bothered about custom roms and, in the past I have usually gone with stock rooted roms so that I can go add-free and remove anything that I do not require.
Last night I lied awake thinking about the implications about what I have and I really need some informed advice about it.
If I root my device, how can I return it to stock in the future so that I can receive any ota updates that T-Mobile may eventually offer without a RUU which appear to be quite scarce?
Am I able to install custom firmwares based on higher firmwares ie. 1.29.401.12 and, if yes, will I be able to return my device back to stock without an RUU as backup?
I am most confused about the scenario which I have. I love the device apart from the 3 dot menu bar which is doing my head in and am confident in my ability to remove it but am worried about my safety net if something goes wrong. Please somebody enlighten me as to what I am and are not able to do. Thanks in advance.
Click to expand...
Click to collapse
You have options. Firstly S-Off is not likely to come soon if at all. HTC made it such a pig to crack, the entire year I had my One X it was never (to my knowledge) posted here how to do it. But it's not really that necessary. S-Off just adds convenience for flashing kernels in recovery at the same time as a ROM. With S-on you just have to accept that a bit more faff is required using fastboot to change a kernel.
(Side note: I have not had my device arrive yet so I am staying out of the development threads. I heard a rumour you can have a flashable kernel for this phone with S-On. Anyone know if this is true?)
Once a custom recovery is on, take a backup of your stock ROM. That way if you ever really wanted to go back for an official OTA update, you could restore the backup, flash back the stock recovery and relock the bootloader. Not sure why you'd want to go this route though.
Being on XDA and knowing how to do this stuff means you can get all the features an official update will bring you, usually months before any carrier will be providing it. You'll just be going through all this extra work to get an update that has been in the custom ROMs for ages.
wnp_79 said:
You have options. Firstly S-Off is not likely to come soon if at all. HTC made it such a pig to crack, the entire year I had my One X it was never (to my knowledge) posted here how to do it. But it's not really that necessary. S-Off just adds convenience for flashing kernels in recovery at the same time as a ROM. With S-on you just have to accept that a bit more faff is required using fastboot to change a kernel.
(Side note: I have not had my device arrive yet so I am staying out of the development threads. I heard a rumour you can have a flashable kernel for this phone with S-On. Anyone know if this is true?)
Once a custom recovery is on, take a backup of your stock ROM. That way if you ever really wanted to go back for an official OTA update, you could restore the backup, flash back the stock recovery and relock the bootloader. Not sure why you'd want to go this route though.
Being on XDA and knowing how to do this stuff means you can get all the features an official update will bring you, usually months before any carrier will be providing it. You'll just be going through all this extra work to get an update that has been in the custom ROMs for ages.
Click to expand...
Click to collapse
Thanks for your answer. As I said, I am not quite a noob :silly:. The reason I am looking to go back to stock at a later date is that I believe (rightly or wrongly you tell me) that to update firmware in it's entirety, it is necessary to use an official update from the provider.
If I back up my official stock rom after I root, are you absolutely sure that when restoring this backup, I will be able to receive official ota updates? It is not that I don't believe you, just want to be 100% sure.
Edit Perhaps we are more likely to get s-off now that we are on Quallcom not Tegra?
S-off together with super cid would give us the ability to use any RUU for this device which gives us an excellent safety net.
bobsie41 said:
Thanks for your answer. As I said, I am not quite a noob :silly:. The reason I am looking to go back to stock at a later date is that I believe (rightly or wrongly you tell me) that to update firmware in it's entirety, it is necessary to use an official update from the provider.
If I back up my official stock rom after I root, are you absolutely sure that when restoring this backup, I will be able to receive official ota updates? It is not that I don't believe you, just want to be 100% sure.
Edit Perhaps we are more likely to get s-off now that we are on Quallcom not Tegra?
Click to expand...
Click to collapse
It's ok. It's always best to be sure before attempting something!
You will not loose out on anything by not using an official update. All it will be is the stock firmware with T-Mobile's add touches. More often than improvements to the stock firmware, carries tend to restrict the features of a ROM and add bloatware (like game demos you can't uninstall) because they have made a deal with a game developer to make some money forcing them upon you.
Even without a nandroid backup you'll still be able to download and flash the stock firmware somewhere here. Basically anything you do to your phone you will be able to undo if you so choose. The only exception to this is that if you re-lock your bootloader, HTC will still be able to tell that it was at some point unlocked if you wanted a warranty return.
Yeah, as long as the stock bootloader is available, you just need to flash it after restoring the backup, and the updates should arrive.
The firmware might be flashable without the RUU or OTA, it was on the One X, but it was necessary to relock the bootloader.
I say go for it, mike1986 has the stock ROM in the dev section as well as his stock like improved ROM.
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!