Hey
[edit]
don't know if i did good or bad, but i installed hboot 2.16 since i want kitkat,
but when i select recovery in the bootloader i still get the constant reboot.
[/edit]
my phone is s-off and super-cid, hboot 1.09, but when i try to install a new version of either CWM or TWRP through their apps, it says installed successfully, but after a reboot i can;t get into recovery - the phone just keeps rebooting.
also - rom manager says i have both installed.
also i can't reset the phone, when i click reset phone in the settings menu, it says it does, but after it reboots - everything is still as it was.
I guess i should not do a factory reset (in hboot menu) unless i have some sort of recovery working?
thanks
OK, all fixed now.
what i did is this:
downgraded to HBoot 2.15
relocked bootloader
installed the 3.16 RUU (only able to do it after the downgrade to 2.15 hboot, and only on one computer - otherwise got error 158)
unlocked the bootloader through HTCDev
installed latest TWRP
tried to load CM without success (didn't read all the instructions)
read all the instructions
flashed the CM boot.img
install CM11 without a problem
hoe this will help someone
how did you go from 2.16 to 2.15?
i'm having a similar issue. http://forum.xda-developers.com/htc-one-s/help/help-load-recovery-boot-rom-hboot-2-16-t2827392
thanks!
Related
Hi all,
I installed MaximusHD ROM and messed up my partitions so now I have only 2 GB available. I want to fix it by going back to stock ROM.
Currently my phone is superCID, s-off, hboot 2.16, radio 1.20.
From what I've read I should be able to install any RUU but I have not been able to. I tried to do it in fastboot mode and in normal mode when Android is on but without success. Setup starts but some unknown error appears, I think it is error 105... or 150.
I've followed some guides here but the setup won't work because of the unknown error Do I have to look for a specific RUU ?
The only thing that I have not done is to lock my bootloader prior to installing the RUU. However the guides state that I do not have to lock it if my phone is S-OFF.
If I do fastboot getvar all next to "version main" I see nothing, it is empty.
Please help!
I changed my CID to HTC__001 but this did not help Please help me to get back to stock !
mkoev said:
I changed my CID to HTC__001 but this did not help Please help me to get back to stock !
Click to expand...
Click to collapse
I had similar issue what I ended up doing was pulling the recovery image out of the install package and flashing it via fastboot and it restored my sd storage I had to use the modified recovery supplied I would try that- I believe you could change your cid to whatever RUU your trying to flash and it should work also,its seems some have downgraded to hboot 2.1.5 to flash RUU (read,read,read)best of luck
Somehow I fixed my problem yesterday. I was not able to install RUU however I was able to change my hboot back to 1.04 ... afterwards I installed the latest version of TWRP and suddenly I was able to see stuff on my internal memory. Prior to that TWRP 2.3.x.x was not able to detect my whole internal memory. Anyway... my advice to people is not to install MaximusHD via CWM although it says that it works. It does work, but it is easier with TWRP
I updated hboot to 2.16, and now i regret that. So i wanted to get back to 2.15.
This is what i've done so far.
Following all the guides and whatever i could find on the forums.
1. downgrade hboot to 2.15
2. oem relock
3. installed org RUU, downloaded on of the exe's (RUU_Ville_U_HTC_Europe_1.78.401.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258480_signed.exe) and let it do it's thing.
4. Here i wanted to get root back and all that so i could start over with flashing. So i unlocked the phone again.
5. installed twrp and rooted after this the org RUU still boots and everything works.
6. This is where things go wrong, when i flash CM11 and gapps i get installations fails, don't know why. (error executing updater binary in zip)
I don't know why it's not working, but in the bootloader it says unlocked, but "tampered" is gone, and that might be the problem, but i cannot remember what that is. s-off and cid is still there.
Any help would be welcome.
Need some help here please. My phone was running CM11, hboot 2.14 but I had to unlock the phone (locked to Rogers). So I s-off, and RUU the only version there is available. Now the unit is unlocked but running hboot 1.09. I tried flashing twrp so I can install CM back but fastboot say flash successful but won't boot to it in recovery, it boots straight to OS. Something I'm doing wrong? And should I upgrade hboot to 2.14 again? If so, how? Btw, the OS works fine but it'll ask if I want to install OTA but once it reboots, it just goes back to the OS without upgrading.
Thanks
You can find the most recent hboot & how to flash it here - http://forum.xda-developers.com/showthread.php?t=2659091
I found the easiest way was to flash the zip rather than use the FUU but use what works for you
Ahh, found the problem. Didn't know I have to manually reboot it after flashing. Thank you
Hi everyone, first of all thanks for any support you may give, I was really hoping to figure this out on my own but I've ended up with 20+ tabs open on the subject and don't seem to be getting anywhere.
So on to issue: Recently fished out my old HTC One S as a friend wants to buy it, however the custom ROM I had installed crashed when using the camera so thought I'd get this all updated for him before he takes it off me, but things have moved on a lot since I was last here, and I'm now stuck getting everything updated.
I currently have hboot 1.13, s-on and root, and my CID is HTC__001
It appears most ROMS now require either hboot 2.15 or 2.16. I incorrectly thought hboot was related to recovery, so I tried to flash latest twrp, but now phone reboots everytime it gets to lock screen, I can still get into fastboot using adb, but I can't access recovery, and I'm now stuck. So any thoughts or input on how to proceed from here would be amazing!
TL:DR:
Currently on Hboot 1.13 with s-on, need to update to 2.15. Phone keeps rebooting, can access fastboot but not recovery. help.
Thanks again, Andrew.
Update: Solved
I resolved my issue by re-locking the bootloader, and installing one of the latest RUUs with hboot 2.15. I could then unlock the bootloader again, flash the latest twrp recovery and get back to installing custom ROMs.
You'll need to flash a recovery with adb. I can't remember if you can do that with S-On, but I don't see why not.
The command is something like: adb flash recovery name-of-recovery.IMG but I don't have my notes with me.
FYI, I always had to run the command twice for it to "stick".
You'll also have to find an older recovery.
Sorry I don't have the actual commands handy, but it shouldn't be too hard to find.
Edit:
Or, you can run the RUU.
Awesome thanks, I just need to find the right recovery and RUU now. I've had a look on Teamwins website and oldest version I can find is 2.1.6, but there is no documentation to say which hboot this supports, however I have a funny feeling I'll need an older version than even that, any ideas where I could find the correct recovery to flash? Thanks again.
I have not been able to update to TWRP 2.8.5.0 from 2.8.0.3, every time I end up hanging in entering recovering in the white boot screen. I have tried fastboot and the RUU method, I always end up reinstalling the 2.8.0.3 TWRP to get recovery back. I checked the firmware everything is up to date but hboot currently on 16 latest is 19. Question could my hboot being out of date cause the update problem and can I just flash the hboot alone?
johnc0865 said:
I have not been able to update to TWRP 2.8.5.0 from 2.8.0.3, every time I end up hanging in entering recovering in the white boot screen. I have tried fastboot and the RUU method, I always end up reinstalling the 2.8.0.3 TWRP to get recovery back. I checked the firmware everything is up to date but hboot currently on 16 latest is 19. Question could my hboot being out of date cause the update problem and can I just flash the hboot alone?
Click to expand...
Click to collapse
Yes it likely is. I noticed this on the att variant as well.
johnc0865 said:
I have not been able to update to TWRP 2.8.5.0 from 2.8.0.3, every time I end up hanging in entering recovering in the white boot screen. I have tried fastboot and the RUU method, I always end up reinstalling the 2.8.0.3 TWRP to get recovery back. I checked the firmware everything is up to date but hboot currently on 16 latest is 19. Question could my hboot being out of date cause the update problem and can I just flash the hboot alone?
Click to expand...
Click to collapse
You could flash hboot alone or you can flash the firmware.zip an update everything.
Thanks for the help, I used dottat's FUU method. HBOOT and recovery updated. John