Hi I've been doin a lot of reading of this forum. My main question is can I install a no sense hc Rom from just performing an HTC unlock or do I need to downgrade to gb anyway in which case I may aswel go s off while I'm at it.
I'm running hc official ota
There is no true no sense rom available as of yet
ok but if i just used the htc unlock could i then easily flash the new virtuous rom which has just started been developed?
Problem is i cant find the correct ruu to downgrade my device, its a uk 16gb wifi . I thought id found it but the site wont let me download.
You should be able to flash clockwork, then a custom ROM through fastboot without downgrade and root.
Haven't done it myself, but that is my understanding of how the unlocked bootloader works versus real S-Off.
I managed to do this hardware unlock and now have an unlocked bootloader. Tried. To flash cwm and corrupted the recovery. How do you install CWM through fastboot?
aranzou said:
I managed to do this hardware unlock and now have an unlocked bootloader. Tried. To flash cwm and corrupted the recovery. How do you install CWM through fastboot?
Click to expand...
Click to collapse
You have get CWM recovery, go into fastboot, connect USB, and then install via command prompt.
If you are unaware of how to do this try installing recovery via Rom Manager. Might be your easier solution.
Thanks for the reply, I actually downloaded cwm from a post in the dev section. Flashed it through command line with fastboot and now when I boot from recovery the device is stuck on a white HTC screen.
Also tried to use Rom manager but the device has to be rooted first. Can you root it through fastboot without cwm? Can I get a download link for a working cwm?
aranzou said:
Thanks for the reply, I actually downloaded cwm from a post in the dev section. Flashed it through command line with fastboot and now when I boot from recovery the device is stuck on a white HTC screen.
Also tried to use Rom manager but the device has to be rooted first. Can you root it through fastboot without cwm? Can I get a download link for a working cwm?
Click to expand...
Click to collapse
Maybe the downloaded file corrupted?
Maybe you can use this link as reference:
http://forum.xda-developers.com/showthread.php?t=1194709
Related
my HH has an unique issue when i flashing another custom rom....
before i flashed i already done this :
wipe data/cache/dalvik 3x each of them.....
and after it finished to flash and reboot its stuck on HTC logo.
this issue encountered when i flash another custom rom except the synergy 3dvo from nightly....
please help me solve this problem....
thx b4
didit.here said:
my HH has an unique issue when i flashing another custom rom....
before i flashed i already done this :
wipe data/cache/dalvik 3x each of them.....
and after it finished to flash and reboot its stuck on HTC logo.
this issue encountered when i flash another custom rom except the synergy 3dvo from nightly....
please help me solve this problem....
thx b4
Click to expand...
Click to collapse
Sounds like your kernel is not getting flashed. If you used HTC's method to unlock you'll need to use fastboot to flash the boot.img
xHausx said:
Sounds like your kernel is not getting flashed. If you used HTC's method to unlock you'll need to use fastboot to flash the boot.img
Click to expand...
Click to collapse
yeah, im using unlock method... does it mean i have to run it in fastboot usb mode if i wanna flash??
my htc is in newest OTA and in hboot 1.500
didit.here said:
yeah, im using unlock method... does it mean i have to run it in fastboot usb mode if i wanna flash??
my htc is in newest OTA and in hboot 1.500
Click to expand...
Click to collapse
I've answered this type of question a few times in other posts. I've edited my answer from a few minutes ago to help answer your question. Feel free to post back if anything isn't clear!
http://forum.xda-developers.com/showpost.php?p=18807723&postcount=3
When booted into the custom recovery through the traditional methods, reboot recovery, bootloader -> recovery, etc., HTC unlock method does not unlock *kernel* write access but does unlock *system* write access.
The main issue around kernel write access is due to the HTC unlock method only allowing kernel write access in two modes:
1) Booted in normal Android mode. My application, Flash Image GUI, will flash any kernel .zip file with the HTC unlock method because it runs in normal android mode. HTC unlocks write access to the boot partition, where the kernel is stored, in normal Android mode. Flash Image GUI also properly loads the respective WiFi modules essentially eliminating this WiFi mismatch error.
2) Fastboot booted into the custom recovery using the following command: fastboot boot c:\android\cwm-recovery.img. HTC unlock method allows kernel write access while using fastboot boot of a custom recovery.
Hope that helps!
Click to expand...
Click to collapse
joeykrim said:
I've answered this type of question a few times in other posts. I've edited my answer from a few minutes ago to help answer your question. Feel free to post back if anything isn't clear!
http://forum.xda-developers.com/showpost.php?p=18807723&postcount=3
Click to expand...
Click to collapse
whoaa it was really helping me, thx man for the suggestion.....
i think i have to try it
sorry, im to noob in flashing method
First of all i've been searching for a way to fix this for hours now without a solution.
My problem is as follows:
i installed official miui beta and got stuck with a boot loop, i was running 4text recovery but i wanted to try something different so i flashed twrp recovery in fastboot. however whenever i try to go into recovery now it just reboots and goes into boot loop again, so i cannot access recovery or boot into my rom.
I have tried flashing several recoverys via fastboot but each time it just reboots and does not enter recovery.
i have also tried rebooting into recovery using fastboot reboot recovery and adb reboot recovery but still it didn't work.
i have flashed another boot.img but now it just gets stuck on miui screen instead of boot loop
is there any way i can get any recoverys to work? i have tried looking for a 4text recovery.img as 4text was the last recovery to work but i can only seem to find the app that flashes it.
i have also tried flashing a rom through fastboot by typing fasboot flash zip rom.zip but it just says failure.
i am now downloading RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_radio_11.77.3504.00U_11.25.3504. and am going to try rename it to PG86IMG and update through bootloader after relocking it and then unlocking it again but i am not sure that will work.
in short i flashed a new recovery but it just reboots device when i try and enter it and the rom i am on happens to be stuck on boot loop so i cannot get in rom or recovery and flashing a new recovery does not work.
BTW i am S-ON HBOOT-1.49.0018
sorry for the lengthy post and also any grammatical errors as i am tired
Comments withdrawn
zcink said:
The whole problem, which is always the problem is you are S-ON. The MIUI rom will NOT run unless you install the newest firmware. You cannot install the newest firmware with S-ON because it is locked up in a partition that you cannot access unless you go s-off.
Has nothing to do with the recovery. I've been using 4ext recovery pretty much the whole time I've owned my EVO 3d and never had one single problem with it.
There are roms you can run with s-on but not the MIUI one.
Click to expand...
Click to collapse
cool, didn't know that, my problem now then is how can i reflash a different rom, bearing in mind that i cannot access recovery? do you think putting the pg86img stock ruu thingy on my sd and letting bootloader install that will work?
powellyable said:
cool, didn't know that, my problem now then is how can i reflash a different rom, bearing in mind that i cannot access recovery? do you think putting the pg86img stock ruu thingy on my sd and letting bootloader install that will work?
Click to expand...
Click to collapse
I do believe that if you are s-on, you should be able to relock the phone and then run the rru from your computer.
sonza said:
I do believe that if you are s-on, you should be able to relock the phone and then run the rru from your computer.
Click to expand...
Click to collapse
My next step was to relock it and run the ruu through bootloader, can you do it through computer/fastboot?
Sorry, I haven't been on the forum for a while.
Read the following link,
http://forum.xda-developers.com/showthread.php?t=1194053&highlight=relock
It should help you with the process.
The rru file you have should be an executable file that the name ends with "signed.exe" if memory serves. I do believe you can run this from your windows desktop if you are using windows. The link above has the adb command to use to relock the phone.
Once you are up and running again, you can install an ics rom even if you have s-on. I am running one but there are a few steps you need to do in the correct order so you don't end up where you are.
Good luck and have a great weekend!
Here is another good link to do what you are wanting to do.
http://forum.xda-developers.com/showthread.php?t=1578977
This might be even easier for you.
Comments withdrawn
So I decided to use htcdev to unlock my bootloader last night for the first time. I am on OTA 1.22.651.3. I know I am not "rooted" and am confused as to if I can actually try any custom ROMs. I read REGAWMOD's post regarding his rooter not working right now...is there another option? Sorry if I missed a post that explains this situation, but I just want to try a custom rom without screwing up my phone.
bman3333 said:
So I decided to use htcdev to unlock my bootloader last night for the first time. I am on OTA 1.22.651.3. I know I am not "rooted" and am confused as to if I can actually try any custom ROMs. I read REGAWMOD's post regarding his rooter not working right now...is there another option? Sorry if I missed a post that explains this situation, but I just want to try a custom rom without screwing up my phone.
Click to expand...
Click to collapse
There's really no reason to manually root if you've already unlocked the bootloader. All you need to do is flash a recovery and then you can flash any ROM, which will already have root access. Here's a good instructional on flashing a recovery:
http://forum.xda-developers.com/showthread.php?t=1830098
Sent from my EVO LTE
Thanks premo15 for the info and link.
The funny thing about htcdev was the stuff they make you download and the steps they make you go through to unlock the bootloader. I was thinking they were going to make me hop on one foot while patting my head and belly simultaneously. :laugh:
I read over and over, did some research, tried running cmd and so on.
having no luck
I went through the HTCDev, s-on but bootloader unlocked
I'm running stock 2.13
After unlock you need to flash twrp, you can use fastboot to do so, just download twrp from the teamwin website and put the image file in adb tools or android sdk folder and in the bootloader type fastboot flash recovery openrecovery-twrp-2.2.2.0-jewel.img
om4 said:
After unlock you need to flash twrp, you can use fastboot to do so, just download twrp from the teamwin website and put the image file in adb tools or android sdk folder and in the bootloader type fastboot flash recovery openrecovery-twrp-2.2.2.0-jewel.img
Click to expand...
Click to collapse
i tried doing that and i couldn't get it to. is there another way to do it?
Can you be more specific on how it isn't working?
om4 said:
Can you be more specific on how it isn't working?
Click to expand...
Click to collapse
yeah, sorry.
the steps i've taken were similar to the htcdev steps,
finish steps 1-7
after I typed "fastboot flash recovery recovery.img" into command prompt and gives me
"error: cannot load 'recovery.img'"
The name has to match, when you download twrp 2.2 the full name is openrecovery-twrp-2.2.2.0-jewel.img so it would be fastboot flash recovery openrecovery-twrp-2.2.2.0-jewel.img or you can rename to recovery.img
om4 said:
The name has to match, when you download twrp 2.2 the full name is openrecovery-twrp-2.2.2.0-jewel.img so it would be fastboot flash recovery openrecovery-twrp-2.2.2.0-jewel.img or you can rename to recovery.img
Click to expand...
Click to collapse
i re- downloaded and used command prompt again without changing name, worked fine this time. thanks for the help om4
flash some roms!!!!!!!!!! :victory::highfive::laugh::good::silly:
Why dont you just get goomanager from the market and flash it from there. Goomanager/flash rom/install open recovery,,,that easy bro
Sent from my EVO using xda premium
Thanks
premo15 said:
There's really no reason to manually root if you've already unlocked the bootloader. All you need to do is flash a recovery and then you can flash any ROM, which will already have root access. Here's a good instructional on flashing a recovery:
http://forum.xda-developers.com/showthread.php?t=1830098
Sent from my EVO LTE
Click to expand...
Click to collapse
Thanks Premo! I was also confused what to do at this point, might this be worth adding to the FAQ thread?
Hi Everybody,
I unlock the bootloader of my HTC view, I also did install the recovery as
http://forum.xda-developers.com/showthread.php?t=1414137
Then I jumped to install the custom rom (forgot to the S-off first), and I could not! and the existing rom is gone as well.
Now I am restarting into a black screen. I do not have a nandroid backup!
I saw a thread:
http://forum.xda-developers.com/showthread.php?t=1038638
that means I need to install a ruu! but the links are not working, if that is the case, can anybody please provide me with a working link?
Thanks,
I believe you can download a ROM, has to be same android version as the one you were on last, so GB or honeycomb. Copy the boot.IMG from the ROM into the same directory as your fast boot commands
Get into recovery flash ROM
Get into fast boot and
Open cmd on PC
Get to your adb directory
Enter
Fastboot flash boot boot.IMG
Or
Find a ROM that does not have a custom kernel
Or hope someone will upload your ruu
Flyer
If you unlocked your bootloader at htcdev.com you don't need to s-off your device! Just download any custom ROM that meet the requirements of your Flyer, enter into recovery by pressing power and volume down button, wipe everything, copy custom ROM you downloaded into the flashcard and flash it. That's it. Smooth flashing!!!
mcord11758 said:
I believe you can download a ROM, has to be same android version as the one you were on last, so GB or honeycomb. Copy the boot.IMG from the ROM into the same directory as your fast boot commands
Get into recovery flash ROM
Get into fast boot and
Open cmd on PC
Get to your adb directory
Enter
Fastboot flash boot boot.IMG
Or
Find a ROM that does not have a custom kernel
Or hope someone will upload your ruu
Flyer
Click to expand...
Click to collapse
Thanks, it was difficult to find a HC rom! apparently everybody is moving to other devices... I am downloading DesensedView
-2.1.zip hope that works. Thanks for the suggestion. I have been busy with this from yesterday and tried almost everything come into my mind. will let you know if that worked.
Keioboy said:
If you unlocked your bootloader at htcdev.com you don't need to s-off your device! Just download any custom ROM that meet the requirements of your Flyer, enter into recovery by pressing power and volume down button, wipe everything, copy custom ROM you downloaded into the flashcard and flash it. That's it. Smooth flashing!!!
Click to expand...
Click to collapse
Yes, I unlocked it on htcdev.com, and I have two roms (ICS and GC) but none works, after flashing those in recovery, a black screen comes up right after htc logo and nothing happens! I deleted everything, all the cashes and data and flashed these roms, no good, stuck on the black screen. any suggestions? I am even looking for a way to at least go back to my HC!
Thanks
OK. In this case let's try to revert everything back. Make shure what ROM was installed in your device (GB or HC) 1. go to http://htcruu.com/?dir=Flyer_View. 2. Download proper RUU installer. 3. Make Gold Card (just in case if downloaded wrong region RUU). 4. Boot into bootloader and start flashing downloaded RUU.
I am telling you that you can not flash an ICS or CG's JB rom because the boot.img will not flash through recovery with HTC dev unlock. were you on HC or GB prior
I'm not new to flashing custom roms and rooting Android devices, so I don't think I'm a noob at this. I decided to help my friend unleash the power in his HTC One S by rooting it and giving it a custom recovery, I went through the right processes, Unlocked the phone's bootloader, and flashed the superuser zip and the twrp image, as it didn't seem like a clockworkmod image was compatible with the phone.
I then booted into recovery, wiped/factory reset and then flashed the latest CM11 nightly and got an error in TWRP recovery about the bootloader not been interoperable something like "
Code:
2.15==2.13"
in the error message , fine, I rebooted back into fastboot and checked the HBOOT Version and found out the phone was on HBOOT 1.13 and I think CM11 requires the most recent HBOOT version to work on HTC devices. The phone has got S-Off though.
Now I'm stuck in a bootloop cause I already wiped the OS in TWRP, I have everything in place, the right drivers and all that, I also tried re-installing the stock rom by downloading an HTC One S's RUU file but the device wasn't recognized at all by the RUU installer, I also tried to flash a stock 4.0.x rom as a zip file, no Joy. Now the phone is stuck at the point where it doesn't have an OS to boot into at all.
I'll really appreciate the community's support helping me fix this issue.
geek-x said:
I'm not new to flashing custom roms and rooting Android devices, so I don't think I'm a noob at this. I decided to help my friend unleash the power in his HTC One S by rooting it and giving it a custom recovery, I went through the right processes, Unlocked the phone's bootloader, and flashed the superuser zip and the twrp image, as it didn't seem like a clockworkmod image was compatible with the phone.
I then booted into recovery, wiped/factory reset and then flashed the latest CM11 nightly and got an error in TWRP recovery about the bootloader not been interoperable something like "
Code:
2.15==2.13"
in the error message , fine, I rebooted back into fastboot and checked the HBOOT Version and found out the phone was on HBOOT 1.13 and I think CM11 requires the most recent HBOOT version to work on HTC devices. The phone has got S-Off though.
Now I'm stuck in a bootloop cause I already wiped the OS in TWRP, I have everything in place, the right drivers and all that, I also tried re-installing the stock rom by downloading an HTC One S's RUU file but the device wasn't recognized at all by the RUU installer, I also tried to flash a stock 4.0.x rom as a zip file, no Joy. Now the phone is stuck at the point where it doesn't have an OS to boot into at all.
I'll really appreciate the community's support helping me fix this issue.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2322755
You need that. Luckily you're already S-Off, so shouldn't be terrible to get going again. Just update the firmware, reinstall TWRP and re-flash CM11. Should be good to go afterwards.
es0tericcha0s said:
http://forum.xda-developers.com/showthread.php?t=2322755
You need that. Luckily you're already S-Off, so shouldn't be terrible to get going again. Just update the firmware, reinstall TWRP and re-flash CM11. Should be good to go afterwards.
Click to expand...
Click to collapse
Thank you so much for the reply, does it matter that I don't have an OS to boot into as I already wiped and factory reset the phone for installation of a new rom.?
geek-x said:
Thank you so much for the reply, does it matter that I don't have an OS to boot into as I already wiped and factory reset the phone for installation of a new rom.?
Click to expand...
Click to collapse
Nah, shouldn't. The firmware we're referring to here is independent of the OS.
es0tericcha0s said:
Nah, shouldn't. The firmware we're referring to here is independent of the OS.
Click to expand...
Click to collapse
At the end of the guide, should help fix the issue, there's a part where I'm supposed to install the new CM kernel from the CM .zip package, how do I flash a kernel from Fastboot?
geek-x said:
At the end of the guide, should help fix the issue, there's a part where I'm supposed to install the new CM kernel from the CM .zip package, how do I flash a kernel from Fastboot?
Click to expand...
Click to collapse
Since you are S-Off, needing fastboot to install the boot.img is not necessary. It will install through recovery.
But, for future reference, you would boot to the bootloader screen, select fastboot, then assuming you have fastboot set up on the PC and the boot.img in the directory of said fastboot, you would use this command:
fastboot flash boot boot.img
then
fastboot reboot
es0tericcha0s said:
Since you are S-Off, needing fastboot to install the boot.img is not necessary. It will install through recovery.
But, for future reference, you would boot to the bootloader screen, select fastboot, then assuming you have fastboot set up on the PC and the boot.img in the directory of said fastboot, you would use this command:
fastboot flash boot boot.img
then
fastboot reboot
Click to expand...
Click to collapse
I tried flashing the firmware.zip file from the thread but I got a FAILED: (remote: not allowed) error in command prompt at the end of the process, what did I do wrong?
UPDATE: I was able to update the bootloader version successfully, as I forgot the part where I was to boot into RUU mode with fastboot oem rebootRUU and worked perfectly the second time.
I rebooted and found out the boot loader was updated to HBoot 2.15, and I also updated twrp to the latest S4 version but now in recovery I get errors about twrp been unable to mount the /data partition. Do I flash another recovery image?
UPDATE:
Thank you so much es0tericcha0s, I really appreciate the support, I got the /data mount issue fixed finally. I just had to flash an older twrp recovery image and then reflashed the new one in fastboot and I could then flash CM successfully.
I can't believe I finally unbricked this phone, its been bricked since Sunday. Once again, es0tericcha0s, Thank you!
geek-x said:
UPDATE: I was able to update the bootloader version successfully, as I forgot the part where I was to boot into RUU mode with fastboot oem rebootRUU and worked perfectly the second time.
I rebooted and found out the boot loader was updated to HBoot 2.15, and I also updated twrp to the latest S4 version but now in recovery I get errors about twrp been unable to mount the /data partition. Do I flash another recovery image?
Click to expand...
Click to collapse
You might need to RUU back then. If you have issues with the RUU exe, then you can extract the rom.zip and install it like you did the firmware. There are quite a few tutorials on how to extract it, or there might already be a version floating around for your phone.