Hello I have recently gotten a new HTC Vivid and discovered the world of rooting.
Here is what I have done - Reset phone - Unlocked Bootloader - PermRooted
It is successfully rooted, I am following a tutorial on flashing a custom rom but I am unable to boot into recovery mode. It gets stuck on the HTC Logo screen. The way I fix this is unplugging the battery and putting it back in.
So my questions are, what steps should I go about installing this ROM?
(I have HBOOT 1.85 and I am on S-On) (Also using CloclwordMod 5.0.2.7)
Mr Pikachuu said:
Hello I have recently gotten a new HTC Vivid and discovered the world of rooting.
Here is what I have done - Reset phone - Unlocked Bootloader - PermRooted
It is successfully rooted, I am following a tutorial on flashing a custom rom but I am unable to boot into recovery mode. It gets stuck on the HTC Logo screen. The way I fix this is unplugging the battery and putting it back in.
So my questions are, what steps should I go about installing this ROM?
(I have HBOOT 1.85 and I am on S-On) (Also using CloclwordMod 5.0.2.7)
Click to expand...
Click to collapse
I had this problem for a while also. Did you happen to download CWM through ROM Manager? That is why you are on CWM 5.0.2.7. Just flash v5.5.0.4 through fastboot and the problem should be fixed!
Here is the link to the zip file I used: http://www.4shared.com/zip/tAZgjz25/CWM-beta2.html
Hopefully this helps!
lonehunter65 said:
I had this problem for a while also. Did you happen to download CWM through ROM Manager? That is why you are on CWM 5.0.2.7. Just flash v5.5.0.4 through fastboot and the problem should be fixed!
Here is the link to the zip file I used:
Hopefully this helps!
Click to expand...
Click to collapse
Ahh, I remember seeing a post similar to what you posted but never seen a reply to weather or not it worked.
This has worked and I am now installing a custom rom Thank you very much. And out of curiosity why would the "more updated" version not work as well as the 0.4 version?
Mr Pikachuu said:
Ahh, I remember seeing a post similar to what you posted but never seen a reply to weather or not it worked.
This has worked and I am now installing a custom rom Thank you very much. And out of curiosity why would the "more updated" version not work as well as the 0.4 version?
Click to expand...
Click to collapse
No clue....
Related
Grab it here:
General: http://koush.tandtgaming.com/recoveries/
Direct Link: http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.0.4-inc.img
Use unrEVOked v3.1 to flash custom recoveries (at your own risk, of course)
1) Download
http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.0.4-inc.img
2) DO NOT PLUG IN YOUR PHONE
3) Run unrEVOked v3.1
4) Under FILE choose CUSTOM RECOVERY
5) Point to the img file
6) Plug in your phone
Updated, no issues. Thanks!
Thanks. I updated without issue.
is it better than the old?
Sent from my Incredible using XDA App
jdkoreclipse said:
is it better than the old?
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
Yes.. it's 0.0.0.3 times better than the old!
If you rooted with unrevoked 3.0 can you just use that with this image?
Sent from my Droid Incredible using the XDA App
Flashed to 2.5.0.4 no problem. But ROM Manager still indicates 2.5.0.1 is installed.
So how do I get ROM Manager to indicate the right recovery version?
UPDATE: Just after I posted this...I booted into recovery and found that I had been flashed back to the older version 2.5.0.1. What the ...! I did not do this. Did ROM Manager flash me back? How do I get 2.5.0.4 to stay flashed? I know it flashed correctly at first because it showed the new version right after I used Unrevoked 3.1. Anyone know why this is happening?
i don't really see a point in updating since it already works for me now...
rom manager reports the older version for me, but booting into recovery it is reporting the newest .4 version
Lexus One said:
Flashed to 2.5.0.4 no problem. But ROM Manager still indicates 2.5.0.1 is installed.
So how do I get ROM Manager to indicate the right recovery version?
UPDATE: Just after I posted this...I booted into recovery and found that I had been flashed back to the older version 2.5.0.1. What the ...! I did not do this. Did ROM Manager flash me back? How do I get 2.5.0.4 to stay flashed? I know it flashed correctly at first because it showed the new version right after I used Unrevoked 3.1. Anyone know why this is happening?
Click to expand...
Click to collapse
ROM Manager cannot flash recovery because NAND is still locked. Only through the unrevoked tool does NAND temporarily unlock in order to flash clockwork. So if you followed the steps correctly using the unrevoked tool then you have the correct version. Booting into recovery (I think you can't boot through ROM Manager, boot manually or via boot loader) should show the updated version.
Lexus One said:
I booted into recovery and found that I had been flashed back to the older version 2.5.0.1. What the ...! I did not do this. Did ROM Manager flash me back? How do I get 2.5.0.4 to stay flashed? I know it flashed correctly at first because it showed the new version right after I used Unrevoked 3.1. Anyone know why this is happening?
Click to expand...
Click to collapse
Boot into recovery via ROM Manager. Note the version. Then boot into recovery "manually" (hold volume down while powering on). Note the version again. Notice anything different?
elborak said:
Boot into recovery via ROM Manager. Note the version. Then boot into recovery "manually" (hold volume down while powering on). Note the version again. Notice anything different?
Click to expand...
Click to collapse
recovery by ROM Manager I get 2.5.0.1
recovery by vdown & Pon I get 2.5.0.4
Thanks, now I'm confused even more. Why are they different? And when I go back into ROM Manager it still reports 2.5.0.1. So my original question still stands: How do I get ROM Manager to display the correct version of recovery which is really 2.5.0.4? Even more...why does the recovery manager report 2.5.0.1 when booting into recovery via ROM Manager? This is reallyyyy strange!
I answered your question two posts back...
s197 said:
I answered your question two posts back...
Click to expand...
Click to collapse
Thanks for responding. I understand. But that doesn't answer my question about how to get ROM Manager to report the correct version. Do you know the answer to this?
What is even more confusing is when I boot into ClockworkMod recovery from the ROM Manager and the version of ClockworkMod Recovery is reported on screen as 2.5.0.1 when it is really 2.5.0.4....this just blows me away! It is like ROM Manager is substituting its own version number into the newer version of recovery.
Lexus One said:
Thanks for responding. I understand. But that doesn't answer my question about how to get ROM Manager to report the correct version. Do you know the answer to this?
What is even more confusing is when I boot into ClockworkMod recovery from the ROM Manager and the version of ClockworkMod Recovery is reported on screen as 2.5.0.1 when it is really 2.5.0.4....this just blows me away! It is like ROM Manager is substituting its own version number into the newer version of recovery.
Click to expand...
Click to collapse
If i understand this correctly: The version that ROM Manager reports and boots into is actually a virtual version. This is because, due to the fact that NAND isn't unlocked yet ROM manager can't actually write to it, So when it is "flashing the recovery" it really is only flashing a "virtual recovery". This is why you could on some phones have an older version of recovery flashed and ROM manager would report a newer version that is available.
In short to answer your question, you can't get ROM manager to report the newer version until rom manager has that newer version in it's list, which it currently does not. And even when it is in the list it makes no difference anyway, because unless you boot into recovery using the power button and volume button, the recovery that you boot into will be a virtual one anyway.... so it really makes no difference what ROM Manager is reporting.
And if i am incorrect in my understanding then, disregard all of this but i remember another post with all this in it.
obsidianblackhawk said:
<snip> And if i am incorrect in my understanding then, disregard all of this but i remember another post with all this in it.
Click to expand...
Click to collapse
Thanks. I appreciate your feedback on this. It would explain why I am seeing a different version for the ROM Manager. What I still don't understand is why ROM Manager misleads you into thinking you are booting to the recovery partition. I mean, why even have an option in the program to "Reboot into Recovery" if you are really NOT booting into the recovery partition, but rather a virtual recovery. So, what would happen if you tried to use the virtual recovery as opposed to the real recovery (which in this case is a different version)? Anyone know, or have tried it?
Lexus One said:
Thanks. I appreciate your feedback on this. It would explain why I am seeing a different version for the ROM Manager. What I still don't understand is why ROM Manager misleads you into thinking you are booting to the recovery partition. I mean, why even have an option in the program to "Reboot into Recovery" if you are really NOT booting into the recovery partition, but rather a virtual recovery. So, what would happen if you tried to use the virtual recovery as opposed to the real recovery (which in this case is a different version)? Anyone know, or have tried it?
Click to expand...
Click to collapse
other than flashing a new recovery, the recovery that rom manager boots into works exactly the same as the "real one" in fact i don;t do it the "hard way" any more.
This is probably a dumb question but do I open the img file after I plug in the phone?
Lexus One said:
how to get ROM Manager to report the correct version.
Click to expand...
Click to collapse
Easiest way is this:
1) Uninstall ROM Manager.
2) Reinstall ROM Manager.
ROM Manager will now display no version, as opposed to the wrong version.
And then...
Never again use the "Flash ClockworkMod Recovery" command in ROM Manager. If you want to update recovery, use the unrevoked flasher with the custom recovery option.
Changes?...
So I just rooted and flashed cm7 using this post:
http://forum.xda-developers.com/showthread.php?t=1337105
Now, it installed rom manager on my phone and also, this method flashed Revolutionary clockwork mod on my phone. the version is: 4.0.1.4
Now in rom manager, I want to use the back up option etc and for that it says I need to flash clockwork mod.
My question is, would it do any damage if I were to flash clockwork mod from rom manager although I have it installed already?
Thanks in advance
jhon101 said:
So I just rooted and flashed cm7 using this post:
http://forum.xda-developers.com/showthread.php?t=1337105
Now, it installed rom manager on my phone and also, this method flashed Revolutionary clockwork mod on my phone. the version is: 4.0.1.4
Now in rom manager, I want to use the back up option etc and for that it says I need to flash clockwork mod.
My question is, would it do any damage if I were to flash clockwork mod from rom manager although I have it installed already?
Thanks in advance
Click to expand...
Click to collapse
If you update CWM using ROM Manager, it should overwrite the Revolutionary CWM version with the latest version.
Are you sure? I tried it, takes a really long while
Sent from my Incredible S using XDA App
jhon101 said:
Are you sure? I tried it, takes a really long while
Sent from my Incredible S using XDA App
Click to expand...
Click to collapse
He's got 485 thanks, I think he knows what he's talking about.
tpbklake said:
If you update CWM using ROM Manager, it should overwrite the Revolutionary CWM version with the latest version.
Click to expand...
Click to collapse
I tried doing it. It just hangs. I mean the display doesn't turn on and that's it. I waited for about 5 minutes. Nothing happened. Although when I popped out the battery and put it back in, it worked okay but the version of CWM is the same. The one from Revolutionary as I mentioned above!
jhon101 said:
I tried doing it. It just hangs. I mean the display doesn't turn on and that's it. I waited for about 5 minutes. Nothing happened. Although when I popped out the battery and put it back in, it worked okay but the version of CWM is the same. The one from Revolutionary as I mentioned above!
Click to expand...
Click to collapse
Ok then just flash the latest CWM recovery from FASTBOOT USB mode using the command:
fastboot flash recovery recovery.img
Also you can just boot into recovery and perform a backup without using ROM Manager.
Thanks a lot man! Really! Couldn't thank you enough. Got it done!
I am sorry if there has already been a question posted on this, if so please direct me in the right way.
I have the HTC Developer Edition and am currently on Software 1.29.1540.3 and my phone has issued me the update (hurray! I need to fix the dam home and back buttons! so annoying...anyway) When I try to do the update (1.29.1540.16), my phone loads me into my custom recovery (ClockworkMod Recovery v6.0.3.1) which then issues begin! Forever is stuck in Run Bug_fix tool. WHY?! WHY?!?!?!?!
I have provided pictures of the steps that my phone goes through so if you can tell me anything about it, please do so thank you!
mikeg818 said:
I am sorry if there has already been a question posted on this, if so please direct me in the right way.
I have the HTC Developer Edition and am currently on Software 1.29.1540.3 and my phone has issued me the update (hurray! I need to fix the dam home and back buttons! so annoying...anyway) When I try to do the update (1.29.1540.16), my phone loads me into my custom recovery (ClockworkMod Recovery v6.0.3.1) which then issues begin! Forever is stuck in Run Bug_fix tool. WHY?! WHY?!?!?!?!
I have provided pictures of the steps that my phone goes through so if you can tell me anything about it, please do so thank you!
Click to expand...
Click to collapse
looks like you are with custome recovery, you need to flash STOCK Recovery for Dev edition and after that you will be able to install OTA.
Here is the link for stock recovery :
http://forum.xda-developers.com/showthread.php?t=2158763
Regards,
mahesh_9j said:
looks like you are with custome recovery, you need to flash STOCK Recovery for Dev edition and after that you will be able to install OTA.
Here is the link for stock recovery :
http://forum.xda-developers.com/showthread.php?t=2158763
Regards,
Click to expand...
Click to collapse
unfortunately the file has been deleted -__-
mikeg818 said:
unfortunately the file has been deleted -__-
Click to expand...
Click to collapse
try this : http://forum.xda-developers.com/showpost.php?p=41684414&postcount=19
mahesh_9j said:
try this : http://forum.xda-developers.com/showpost.php?p=41684414&postcount=19
Click to expand...
Click to collapse
sorry for the dumb question but can i put this on my memory and flash it through my clockworkmod recovery? or is there anoither way to do it?
and also do you know why when i delete all the ringtones, and when i delete all the apps i dont want (google magazines, books, those things) when i restart my phone they all come back?! WHY?! why are you making my life so hard HTC ONE! WHY!
mikeg818 said:
sorry for the dumb question but can i put this on my memory and flash it through my clockworkmod recovery? or is there anoither way to do it?
and also do you know why when i delete all the ringtones, and when i delete all the apps i dont want (google magazines, books, those things) when i restart my phone they all come back?! WHY?! why are you making my life so hard HTC ONE! WHY!
Click to expand...
Click to collapse
Mate,
this contains the guide to flashing/rooting etc. Please follow the steps and you'll be ok.
http://forum.xda-developers.com/showthread.php?t=2158151
Thanks,
Update issue-unable to mount internal sdcard
Hi,
I tried to perform the software update using CWM V6.0.3.0 sadly what I got is "invalid command argument" and "can't mount internal sd card" !!! Please help!
@mikeg818 : you need to flash recovery in Fastboot Mode
@sampagna : you cannot update if you have custom recovery. So first flash stock recovery in fastboot and then do the update ( provided you are on stock ROM)
x017in said:
@mikeg818 : you need to flash recovery in Fastboot Mode
@sampagna : you cannot update if you have custom recovery. So first flash stock recovery in fastboot and then do the update ( provided you are on stock ROM)
Click to expand...
Click to collapse
@x017in: Sorry for the naive question. I still have a lot to learn about android. I have rooted my phone to put down CWM. Now I know that I am having custom recovery, but I am not sure if I am having custom ROM or stock ROM. Custom ROM refers to s.th like Cyanogenmod, right?
Yep. That's what custom Rom means.. so now you need to put back the recovery that came stock with the phone. Only then will the OTA update work
Sent from my HTC One using Tapatalk 4 Beta
How to flash stcok recovery?
Hey guys, I'm new to android so I was wondering how to flash stock recovery (steps, guide)? and what does it do? Those pictures show exactly what's happening to me.
By the way I bought the htc one developer edition, it was supposed to be new but it came with CWM. So It wont let me install software OTA.
Hey guys so I was changing my roms the same way Ive been doing it since forever but this time for some reason no matter what rom I flash the phone wont boot into the rom. It wont even reach the bootanimation. It will reach the splash screen and stay there or reboot back into recovery. Is my phone bricked? All help is welcome.
Details:
Blackrose hboot
4Ext Recovery
HTC Incredible S
stinghardj said:
Hey guys so I was changing my roms the same way Ive been doing it since forever but this time for some reason no matter what rom I flash the phone wont boot into the rom. It wont even reach the bootanimation. It will reach the splash screen and stay there or reboot back into recovery. Is my phone bricked? All help is welcome.
Details:
Blackrose hboot
4Ext Recovery
HTC Incredible S
Click to expand...
Click to collapse
What ROM did you attempt to flash?
Did the ROM's author have ay specific instructions about flashing and did you follow them?
Did you attempt to flash a stock RUU/ROM?
tpbklake said:
What ROM did you attempt to flash?
Did the ROM's author have ay specific instructions about flashing and did you follow them?
Did you attempt to flash a stock RUU/ROM?
Click to expand...
Click to collapse
I tried to flash the new SVHD 2.0 rom then Nik's Project X Rebirth Rom
Looks like there's a Problem with the kernel, die you try to flash it manually, too?
Sent from my Incredible S S710e using XDA Premium 4 mobile app
stinghardj said:
I tried to flash the new SVHD 2.0 rom then Nik's Project X Rebirth Rom
Click to expand...
Click to collapse
for me, both ROMs took more than usual time to boot, like 5 minute. make sure you wait for that
stinghardj said:
I tried to flash the new SVHD 2.0 rom then Nik's Project X Rebirth Rom
Click to expand...
Click to collapse
pinkyponku said:
for me, both ROMs took more than usual time to boot, like 5 minute. make sure you wait for that
Click to expand...
Click to collapse
I installed SVHD 2.0 this afternoon and it took about 5 minutes to boot up. I am also running BlackRose and 4Ext Touch recovery.
tpbklake said:
I installed SVHD 2.0 this afternoon and it took about 5 minutes to boot up. I am also running BlackRose and 4Ext Touch recovery.
Click to expand...
Click to collapse
When I flash a ROM I don't get to the boot animation I'm stuck on the HTC splash screen. Also when I flash the ROM and do a backup with 4ext usually the backup file name is date.ROM name but 4ext can't recognize the ROM name it says unknown. Is it not flashing properly?
stinghardj said:
When I flash a ROM I don't get to the boot animation I'm stuck on the HTC splash screen. Also when I flash the ROM and do a backup with 4ext usually the backup file name is date.ROM name but 4ext can't recognize the ROM name it says unknown. Is it not flashing properly?
Click to expand...
Click to collapse
Do you have the latest version of 4Ext recovery? Have you tried flashing the boot.img manually in FASTBOOT USB mode?
tpbklake said:
Do you have the latest version of 4Ext recovery? Have you tried flashing the boot.img manually in FASTBOOT USB mode?
Click to expand...
Click to collapse
Dno't know what I did but the phone fixed itself!! Guess that's why its called the Incredible lol. Thanks for helping guys
stinghardj said:
When I flash a ROM I don't get to the boot animation I'm stuck on the HTC splash screen. Also when I flash the ROM and do a backup with 4ext usually the backup file name is date.ROM name but 4ext can't recognize the ROM name it says unknown. Is it not flashing properly?
Click to expand...
Click to collapse
stinghardj said:
Dno't know what I did but the phone fixed itself!! Guess that's why its called the Incredible lol. Thanks for helping guys
Click to expand...
Click to collapse
I dont think SVHD2 has any boot animation, it just shows HTC boot like screen (with beats audio). glad it fixed itself
Hi Guys,
I have s3 GT-I9305, android version 4.1.2, baseband version I9305XXBLL5. Australian model for Optus.
I successfully rooted and installed Philz_Touch_6.19.3 _ After that I could do Nandroid online backup and confirm it is rooted.
When I tried to flash custom ROM today - I found I can't boot in CWM/Philz recovery mode. Then I tried to different version of Philz/CWM and TWRP but none worked. It keeps booting in stock recovery mode- I get message as shown in attached image.
PS: I have USB diagnosis checked but haven't unlocked boot loader?
to be specific: my phone works fine - boots fine - It is just I want to load custom rom and it won't go to custom recovery and I can't load custom ROM.
Thanks.
HELP!
can anyone please help me out here!
I kept searching and found some solution but none worked.
I used triangle away. - didn't work
Installed custom recovery without checking auto reset and started after pulling battery out. - didn't work
It still boot in odin mode and I can't go to custom recovery
i have the same problem too when i got my phone flashed 3rd recovery last year,
the stock recovery can automaticly restore itself after reboot~
but i found the solution here in xda,just flash a zip to unlock the self-protection of the stock recovery~
i will tell you the link and the attachment several hours later after my work,if you cannt wait, you can search it here,maybe you can find it yourself.
Sent from my GT-I9305
Aphirodite said:
i have the same problem too when i got my phone flashed 3rd recovery last year,
the stock recovery can automaticly restore itself after reboot~
but i found the solution here in xda,just flash a zip to unlock the self-protection of the stock recovery~
i will tell you the link and the attachment several hours later after my work,if you cannt wait, you can search it here,maybe you can find it yourself.
Sent from my GT-I9305
Click to expand...
Click to collapse
I had a quick search but couldn't find it. Will greatly appreciate if you can post link.
Thanks
even after you flash a custom recovery...your phone will automatically flash stock recovery every time it reboots...so that's why you will get into stock even if you flash CWM/TWRP or what you like.....
here is the solution: http://forum.xda-developers.com/gal...-cf-root-cwm-recovery-ported-supersu-t1914394
read at the end of the first post....WORKAROUND......
i used myself and worked....
ggmm2013123 said:
I had a quick search but couldn't find it. Will greatly appreciate if you can post link.
Thanks
Click to expand...
Click to collapse
the guy offered the post which included the solution.
try to flash the "Remove-boot-recovery.p.zip",it will work..
good luck
:fingers-crossed:
Done
Thanks guys.
Above solution didn't work for me but I got it working through rom manager App. I reboot to recovery through ROM Manager and it worked.
How ever After I installed Pacman rom, I couldn't use App as there were no Gapps and wouldn't boot to recovery. The workaround here was to press home, volume up and lock button simultaneously and release it after few second and it will go to custom recovery.
In the end, I am on Pacman Nightly 06/04/2014 with Philz touch recovery.