Hi everybody.
I had some custom roms installed but now I returned back to stock with the ruu.exe but I wanted to get root so I put twrp on my phone and flashed superuser but now there was an update for system optimizing but I cannot install it because it want to go into recovery but it open twrp because I don't have stock recovery so how will I get the stock recovery to my phone ?
Thanks in advence.
Sent from my HTC One S using xda app-developers app
Which one do you have?
The T-Mobile one is posted in a few places but not sure about others.
I have the EU one I have jelly bean since December.
Sent from my HTC One S using xda app-developers app
Simply download ville_recovery_signed.img from here and flash in fastboot mode
'fastboot flash recovery ville_recovery_signed.img'.
--- edit
little but important change...
rootrider said:
Simply download ville_recovery_signed.img from here and flash in fastboot mode
'fastboot flash boot ville_recovery_signed.img'.
Click to expand...
Click to collapse
Don't you mean
fastboot flash recovery ville_recovery_signed.img
Sent from my HTC One S using Tapatalk 2
Yep - absolutely!
Thanks a lot - was in a hurry!
Flash error...
I'm having the same problem. But when I flash the recovery (from link above) I get the error message
<remote: signature verify failed>
Is this the wrong recovery for my phone (4.1, C1, rooted, stock ROM)?
I also just realized, that I'm getting this error with ANY recovery (TWRP etc.) I'm trying to flash...
Please help! Thanks!
Schnorgl said:
I'm having the same problem. But when I flash the recovery (from link above) I get the error message
<remote: signature verify failed>
Is this the wrong recovery for my phone (4.1, C1, rooted, stock ROM)?
I also just realized, that I'm getting this error with ANY recovery (TWRP etc.) I'm trying to flash...
Please help! Thanks!
Click to expand...
Click to collapse
Are you using the all in one toolkit ?
sGollSv said:
Are you using the all in one toolkit ?
Click to expand...
Click to collapse
No, I'm not.
But I figured out what might have caused the problem: an outdated stock recovery file (they all have the same file name...
Installed RUU, TWRP and root and now everything works smoothly. What a hassle for such a minor update!
Related
I've got a Sensation (I think its a Phillipenes issue) which was upgraded to ICS 4.0.3.
Basically I've managed to complete HTC Dev Unlock, then a few days later I lost Wi-Fi connection, so have been trying to continue with installing a Custom (or even the original) ROM in an attempt to fix it.
I've now done Junoptobear to get true S-OFF
Got root access
But cant get Clockwork Mod to install in Recovery...
I've installed ROMmanager Premium and used it to install the latest Clockwork Mod - it states its downloaded and completed but when I go to the bootloader and select Recovery it flashes the white HTC screen for a brief second then back to the bootloader.
I've tried to manually download the Clockwork Mod file and install to Recovery but I get the same issue.
Does anyone have any ideas?? Many thanks!
Hi there you can install 4ext recovery you can get the file here in xda or even from the play store. Many of us use 4ext because it has many options and is very easy to use.personally I prefer 4ext. All I did was download from the play store and opened the app follow directions choose version of recovery and it will flash from the application. I was already rooted and soff when I did it but it's very easy to do. I really think you will like 4 ext recovery. You already have s OFF and root so it should not be a problem. Best of luck to you. I hope this helps! As I mentioned most of us use 4 ext recovery and I doubt you will be disappointed. Good luck.
Sent from my HTC Sensation 4G using xda premium
mattpone said:
I've got a Sensation (I think its a Phillipenes issue) which was upgraded to ICS 4.0.3.
Basically I've managed to complete HTC Dev Unlock, then a few days later I lost Wi-Fi connection, so have been trying to continue with installing a Custom (or even the original) ROM in an attempt to fix it.
I've now done Junoptobear to get true S-OFF
Got root access
But cant get Clockwork Mod to install in Recovery...
I've installed ROMmanager Premium and used it to install the latest Clockwork Mod - it states its downloaded and completed but when I go to the bootloader and select Recovery it flashes the white HTC screen for a brief second then back to the bootloader.
I've tried to manually download the Clockwork Mod file and install to Recovery but I get the same issue.
Does anyone have any ideas?? Many thanks!
Click to expand...
Click to collapse
Get the recovery from Cwm PG58IMG.zip and copy the img file to adb/fastboot folder and try these commands
fastboot erase recovery
fastboot flash recovery recovery.img
Sent from my HTC Sensation 4G using xda premium
ganeshp said:
Get the recovery from Cwm PG58IMG.zip and copy the img file to adb/fastboot folder and try these commands
fastboot erase recovery
fastboot flash recovery recovery.img
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
I may be wrong but this sorta sonuds like a problem abother member was having the other day. I think they may not have a eng Hboot installed. Question why not just let them flash the recovery using the PG58IMG.zip via bootloader?
T-Macgnolia said:
I may be wrong but this sorta sonuds like a problem abother member was having the other day. I think they may not have a eng Hboot installed. Question why not just let them flash the recovery using the PG58IMG.zip via bootloader?
Click to expand...
Click to collapse
Yeah.. I want to see the output of the command.. Also he can do it via PG58IMG.zip way which I think he already did it (he said he did it manually too... . So)
Sent from my HTC Sensation 4G using xda premium
ganeshp said:
Get the recovery from Cwm PG58IMG.zip and copy the img file to adb/fastboot folder and try these commands
fastboot erase recovery
fastboot flash recovery recovery.img
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
Awesome! That fixed it!
Looks so simple now I see it - but many thanks, that's the final step complete now!
ClockWork Mod now installed in Recovery!
Trying to install software update, every time i attempt, goes into clockwork recovery and gives an error. can anyone give me instructions on what to do?
U on venom Rom I'm guessing ?
Sent from my HTC One S using xda premium
k1llacanon said:
U on venom Rom I'm guessing ?
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
I don't think so, sounds like he's on stock Rom just rooted
CrayzyBoy said:
I don't think so, sounds like he's on stock Rom just rooted
Click to expand...
Click to collapse
Could be.. dude if your on stock you have to lock your bootloader again to do the official HTC updates ... U do this by connecting your phone to the pc in fastboot and in cmd type
Fastboot OEM lock
Sent from my HTC One S using xda premium
sayhuha said:
Trying to install software update, every time i attempt, goes into clockwork recovery and gives an error. can anyone give me instructions on what to do?
Click to expand...
Click to collapse
You should be using stock recovery and not clockworkmod. So flash stock recovery and you need to lock your bootloader.
This tool has the option to flash recovery, at least that is what I used.
http://forum.xda-developers.com/showthread.php?t=1604677
Try to go through this...
Charkatak said:
You should be using stock recovery and not clockworkmod. So flash stock recovery and you need to lock your bootloader.
This tool has the option to flash recovery, at least that is what I used.
http://forum.xda-developers.com/showthread.php?t=1604677
Try to go through this...
Click to expand...
Click to collapse
I am having the same issue, but this link to that tool does not have an option for stock recovery, so where did you get it from?
cbeezy34 said:
I am having the same issue, but this link to that tool does not have an option for stock recovery, so where did you get it from?
Click to expand...
Click to collapse
My Hasoon's All in one tool, has that option. Also you can search the web for that tool app. I tried to upload stock recovery, but looks like it exeeds the limit of 8 MB. Give me your email, I will send it to you.
Charkatak said:
My Hasoon's All in one tool, has that option. Also you can search the web for that tool app. I tried to upload stock recovery, but looks like it exeeds the limit of 8 MB. Give me your email, I will send it to you.
Click to expand...
Click to collapse
Please consider putting this up on fileshare site ..
I also have the Hasoon tool and in newest version you can only flash stock recovery if you have it yourself, it is not included.
Have been looking for the stock recovery myself but failed to find it.
xsatquest said:
Please consider putting this up on fileshare site ..
I also have the Hasoon tool and in newest version you can only flash stock recovery if you have it yourself, it is not included.
Have been looking for the stock recovery myself but failed to find it.
Click to expand...
Click to collapse
This is the thread where you can download stock recovery: http://www.modaco.com/topic/353006-...ch-recovery-for-the-htc-one-s-stock-download/
Second download link(file is calle "ville recovery") is the file for stock recovery!
Charkatak said:
This is the thread where you can download stock recovery: http://www.modaco.com/topic/353006-...ch-recovery-for-the-htc-one-s-stock-download/
Second download link(file is calle "ville recovery") is the file for stock recovery!
Click to expand...
Click to collapse
Fantastic.
I flashed this recovery using the tool and rebooted the phone.
Then i installed the OTA update (No need to relock bootloader)
Then i reinstalled CWM and SuperSU .
Now my phone is at 2.31 and rooted.
Sweet that i dont have to listen to the SMS tone over and over again just informing me that there is a firmware update available.
Thanks for the help, much appreciated.
xsatquest said:
Fantastic.
I flashed this recovery using the tool and rebooted the phone.
Then i installed the OTA update (No need to relock bootloader)
Then i reinstalled CWM and SuperSU .
Now my phone is at 2.31 and rooted.
Sweet that i dont have to listen to the SMS tone over and over again just informing me that there is a firmware update available.
Thanks for the help, much appreciated.
Click to expand...
Click to collapse
I have the same issue right now. My only concern is when you locked the bootloader did you lose your data? It's my gf phone and when I unlocked the bootloader it wiped data from the phone and she got really mad
Especially for people who rooted their phones recently using X-Factor root exploit
"If you have the newer HBOOT 1.14 (you probably do if coming from stock 2.20), boot.img's will have to be flashed separately via fastboot. Extract the boot.img from you ROM zip of choice and put it in the same directory as fastboot. Reboot your device into boot loader and run "'fastboot flash boot boot.img' (no quotes)
You can then flash the ROM" - thanks to
Guylncognito721
How to flash Custom Recovery and ROM after 2.20 root - http://forum.xda-developers.com/showthread.php?p=33179690
More information
"if you are flashing similar ROMs ( having same kernel ).. there is no need to flash boot.img separately. But say if you wanna switch from sense to aosp you must do that as they have different kernels.
Again if you are just upgrading from older version to newer version of same ROM and if there are no kernel changes no need to flash it" (thanks kancherlapraneeth)
I have seen so many topics in Q&A thread regarding this issue, thought this would help ppl
Butchered my name...
Sent from my One X using xda app-developers app
GuyIncognito721 said:
Butchered my name...
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Sorry bro.. Corrected it
If you have flashed viperROM from stock 2.20 do you still have 1.14 boot? Do I still have to flash boot separate?
And would it be worth it to just ruu to 1.85
Sent from my HTC One XL using xda app-developers app
Kole_Ackerson said:
If you have flashed viperROM from stock 2.20 do you still have 1.14 boot? Do I still have to flash boot separate?
And would it be worth it to just ruu to 1.85
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Yes.
Yes.
You can't ruu to 1.85 as downgrading hboot is not possible.
Sent from my One X using xda app-developers app
GuyIncognito721 said:
Yes.
Yes.
You can't ruu to 1.85 as downgrading hboot is not possible.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Oh wait, s-off is needed to downgrade isn't it.. haha blonde moment
Sent from my HTC One XL using xda app-developers app
Bumping this.
WR
Sent from my HTC One X
So what happens if you don't? I did the exploit and then installed Calkulin's ROM and it seems to be going fine without flashing the boot.img. Maybe this is why another ROM I tried didn't work (got stuck on the Paranoid Android screen).
ChummyDays said:
Because it stays on the stock kernel. Paranoidandroid got stuck because it probably can't run on the stock kernel... calkulin's ROM is somewhat close to the stock ROM (4.0.4 and sense)
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Aha, good to know. Thanks!
Ok I am getting "sending 'boot' (6156 KB)... FAILED (status read failed (Too many links)) any help?
The_new_user said:
Ok I am getting "sending 'boot' (6156 KB)... FAILED (status read failed (Too many links)) any help?
Click to expand...
Click to collapse
did you type
fastboot flash boot boot.img
absolutelygrim said:
did you type
fastboot flash boot boot.img
Click to expand...
Click to collapse
Yes I am in the correct directory and have my boot.img there I am typing fastboot flash boot boot.img I even tried fastboot erase cache but I am still getting the too many links error.
Going to try rebooting the computer and phone to see what happens I will report back if it fixes it.
Ok a reboot of the phone and comp was no help.
" OK I fixed it. All I did was change usb ports on my computer and it went straight through. " Hope this helps someone else later on.
need help
Can i please get some need some help
I'm currently on paranoid android 2.51 jb ROM. I did the root exploit since I was stuck on 2.20
And before I flashed paranoid android I made a twrp backup of stock sense.
Ok this is what I need help on because I was on 2.20 I had to flash the boot.img along with the custom ROM to get it working, now what I need to know is if I restore my twrp backup do I need to flash the boot.img so I can go back to stock? If so how can I get the boot.img from my backup that I made? I copied backup to my computer to look for the boot.img but there's nothing there
I wanted to post here before I make a new thread
TWRP restore does not boot
I used TWRP 2.3.1 to back up the rooted stock rom on my AT&T One X firmware 2.20. I then proceeded to flash Viper X 2.6.0 but the phone was stuck in boot loop even after I flashed the boot.img in the Viper zip file. I was able to get back into TWRP and run the restore. However, the phone continues to be in a boot loop even after the restore.
Did I miss any steps in the restore process for TWRP?
ViperX isn't for you phone. Your lucky you can get back into twrp. You need to flash your boot.img backup in fastboot.
For people trying to flash the style backup and can't find the boot.img you should be able to fastboot boot.emmc.win just as a normal boot.img.
http://forum.xda-developers.com/showthread.php?p=33743517
Sent from my One X using xda premium
Boot.img and now no image display
hello friends, was trying to root the One X att and for several times but reading the roms were not entered into the system, just by downloading the boot.img boot.img_1.88.707.2 and sent only the boot.img via fastboot, now put the original system goes, but not no picture on display, I can hear the sound of the system by opening and receiving emails but no picture. please help me because I do not know what else to do.
irosemberg said:
hello friends, was trying to root the One X att and for several times but reading the roms were not entered into the system, just by downloading the boot.img boot.img_1.88.707.2 and sent only the boot.img via fastboot, now put the original system goes, but not no picture on display, I can hear the sound of the system by opening and receiving emails but no picture. please help me because I do not know what else to do.
Click to expand...
Click to collapse
Can you give more details on what version are you on (2.20?)and are you able to boot??
Create a separate post in Q&A and many people will respond ,this not appropriate place to ask
Sent from my Nexus 4 using xda premium
I think I know what my problem was. I flashed the rom first THEN the boot.img. Which caused it to get stuck at the boot animation and I would have to go to the boot loader and flash the boo.img.
---------- Post added 12th February 2013 at 12:16 AM ---------- Previous post was 11th February 2013 at 11:40 PM ----------
sschrupp said:
So what happens if you don't? I did the exploit and then installed Calkulin's ROM and it seems to be going fine without flashing the boot.img. Maybe this is why another ROM I tried didn't work (got stuck on the Paranoid Android screen).
Click to expand...
Click to collapse
Ya same issue here too. My mistake was i flashed the boot.img after I flashed the rom. So now I'm rooting and flashing again and see if flashing boot.img the first time works.
I feel so stupid now. I kept doing fastboot boot boot.img. Not fastboot flash boot boot.img. No wonder it always stuck in the boot animation screen all the time. So I flash the boot img then i flash the rom from recovery? What do I wipe in TWRP?
Anybody knows how to fix the FAILED message I get anytime to try to wipe or flash in TWRP?
Sent from my Nexus 4 using xda premium
persheshhater said:
Anybody knows how to fix the FAILED message I get anytime to try to wipe or flash in TWRP?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Uncheck md5 checking in Twrp.
Sent from my HTC One XL
That didnt help. It always fails when it is about to update partition details...
Sent from my Nexus 4 using xda premium
ECEXCURSION said:
Uncheck md5 checking in Twrp.
Sent from my HTC One XL
Click to expand...
Click to collapse
That doesn't work I tried that before.
Idk, that was my idea.
So it fails even when you try to wipe, that's interesting (also means my assumption was wrong).
Sent from my HTC One XL
persheshhater said:
Anybody knows how to fix the FAILED message I get anytime to try to wipe or flash in TWRP?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
If u gave more info like twrp version hboot version stuff like that people could probly help u out better mabie u flashed a bad recovery?
Mabie u could try using a toolkit to reflash twrp from your pc? Or ruu to stock and star over?
Work for this guy.
http://forum.xda-developers.com/showthread.php?t=2089438&page=2
I am having the same issue
hboot1.14.0002
radio 0.19as.32.09.11_2
I am unlocked/tampered but S-on.
I thought I made a back up of CleanRom5 when I first put it on the phone, but alas I find that I didnt.
So I am between roms with s-on. Is there a way to achieve S-off with. I can still get into bootloader, and recovery.
hiperglyde said:
I am having the same issue
hboot1.14.0002
radio 0.19as.32.09.11_2
I am unlocked/tampered but S-on.
I thought I made a back up of CleanRom5 when I first put it on the phone, but alas I find that I didnt.
So I am between roms with s-on. Is there a way to achieve S-off with. I can still get into bootloader, and recovery.
Click to expand...
Click to collapse
boot to bootloader fastboot flash a 2.3 version of twrp i use 2.3.3.0 boot to recovery mount usb transfer rom to phone flash rom be sure to fastboot flash boot.img reboot
This seems to be a bug with 2.4.x.x versions of TWRP. If you downgrade to an old version, it should be OK, from what I've read.
jerrycoffman45 said:
boot to bootloader fastboot flash a 2.3 version of twrp i use 2.3.3.0 boot to recovery mount usb transfer rom to phone flash rom be sure to fastboot flash boot.img reboot
Click to expand...
Click to collapse
edit .. found it
for others that might need it
http://techerrata.com/browse/twrp2/evita
http://techerrata.com/browse/twrp2/evita
I installed 2.3.3.0 and the factory reset still failed..?
errors given were E:unable to mount '/sdcard'
did you factory reset from bootloader if so you have corrupted your sd card there is a fix let me find it
I did this and this is what Xsmagical and I did to fix it.
Take the stock android recovery from a ruu or stock Rom. (I used the one from 1.85 ruu but it doesn't matter.)
Fastboot flash the stock recovery to your phone and then reboot into bootloader where you originally wiped.
Factory reset from hboot and then Fastboot flash twrp again, mount sd should be available now. Mount sd, copy whatever Rom onto sd card and flash from there.
Freaked me out too man
this is not my post copy and paste
Thanks brother anyone else this may help
http://www.youtube.com/watch?v=H-vf5eHV3_s
I just about crapped a brick literally
Edit: For the solution, go to post #7
Looking for help here. I have a butterfly X920d.
I received an update for 1.19.707.1 yesterday and I updated it. The problem is I have TWRP installed.
So now when the main update package (1.19.707.2) is downloaded and reboots to continue installation, it always reboots into TWRP instead of installing it.
I have tried to flash 1.12.707.1 RUU but it always end up in error 43 (FAILED (remote: 43 main version check fail), upon research tells me that it is incompatible with the 1.19.707.1 I have recently updated.
To perform the above action, I locked the bootloader, which introduce a new problem. When the 1.19.707.2 reboots to install, it is stuck at the HBoot/Fastboot screen. It remain there until I manually reboot it.
In a summary;
In 1.12.707.1, installed TWRP and rooted
Got an OTA update for 1.19.707.1, download and run it, while rooted
1.19.707.1 installed properly
Phone begins to download and install 1.19.707.2
Upon restart to complete, installation stuck in TWRP screen
Relocked phone and tries to flash 1.12.707.1 RUU to return to stock
Error 43 (FAILED (remote: 43 main version check fail) in fastboot RUU flash
Restarted process 4, but now instead of booting to TWRP, it is stuck in Fastboot
I'm thinking, as the update process does not support TWRP recovery, it is stuck in 1.19.707.1
As I have locked the bootloader, TWRP is unable to start. Would unlocking it again via unlock.bin softbrick my phone?
Is there any help or guide to help me get out of this spiral of misery?
Thank you in advance.
Edit: is there anyway to flash just the stock recovery to replace twrp instead of the whole RUU?
Stock ota update uses stock recovery twrp doesn't work try to pull from stock ruu.zip unzip and locate recovery.img and flash like you did twrp
Sent from my HTC Butterfly using xda app-developers app
Bassie39 said:
Stock ota update uses stock recovery twrp doesn't work try to pull from stock ruu.zip unzip and locate recovery.img and flash like you did twrp
Sent from my HTC Butterfly using xda app-developers app
Click to expand...
Click to collapse
@Bassie39, should I use recovery from 1.12 or 1.19?
Thanks
Depends on which version your are running now
Sent from my HTC Butterfly using xda app-developers app
It is strange that 1.19.707.1 did not overwrite my TWRP recovery during the initial upgrade.
It is strange but you can try to flash recovery yourself
Sent from my HTC Butterfly using xda app-developers app
Woah, took the dive, went in and emerged successfully.
Thanks to the advice from @Bassie39, I reflash my recovery from 1.19.707.1 (link) [Please read the instructions to get the correct files.]
I had to unlock my device before flashing the recovery due to relocking it earlier. Same old story, all of the data was wiped.
Summary of my steps.
Flash stock recovery.img, extracted from 1.19.707.1 RUU
Reboot phone
1.19.707.2 installed succesfully from OTA
2.33.707.3 updated as well upon reboot
Reflash TWRP 2.6
Root using busybox
SuperSU not working in 4.2.2 (probably leftovers from the previous root)
Downloaded SuperSU and flashed in recovery
Root and Titanium backup working finally
Those who are having the same issue, you need not relock your device. Just flash stock recovery, and the OTA is good to go.
After that, flash TWRP and root if you like.
Relock is indeed not necessarily only stock boot.img and recovery.img
Sent from my HTC Butterfly using xda app-developers app
Got the impression that lock was required for flashing stock recovery from other forums.
With my dlxu it works fine stock ota runs oke and bootloader still open
Sent from my HTC Butterfly using xda app-developers app
kemikelx said:
Woah, took the dive, went in and emerged successfully.
Thanks to the advice from @Bassie39, I reflash my recovery from 1.19.707.1 (link) [Please read the instructions to get the correct files.]
I had to unlock my device before flashing the recovery due to relocking it earlier. Same old story, all of the data was wiped.
Summary of my steps.
Flash stock recovery.img, extracted from 1.19.707.1 RUU
Reboot phone
1.19.707.2 installed succesfully from OTA
2.33.707.3 updated as well upon reboot
Reflash TWRP 2.6
Root using busybox
SuperSU not working in 4.2.2 (probably leftovers from the previous root)
Downloaded SuperSU and flashed in recovery
Root and Titanium backup working finally
Those who are having the same issue, you need not relock your device. Just flash stock recovery, and the OTA is good to go.
After that, flash TWRP and root if you like.
Click to expand...
Click to collapse
I have updated to 2.33.707.3 too. But I didn't save the Update file into my computer. I want to root my phone, so I need to flash TWRP first and then flash the root file, but after that I want to change my recovery to stock one. Do you have any backup of 2.33.707.3 stock recovery.img?
can you pls help me with the stock recovery.img of 2.33.707.3. i want to upgrade to 4.3 ota and it keeps rebooting to twrp recovery. looked all around but no solutions for 707 region. would be grateful for any help.
vsinha71 said:
can you pls help me with the stock recovery.img of 2.33.707.3. i want to upgrade to 4.3 ota and it keeps rebooting to twrp recovery. looked all around but no solutions for 707 region. would be grateful for any help.
Click to expand...
Click to collapse
I'm presently having issues to update to 3.15.707.4 as well. I'm trying recovery-1.12.707.1
Edit: Recovery failed.