Ok firstly, I do have some novice experience with rooting and such, but this is my first HTC device and it seems a little different and I'm just trying to be really cautious as I can't afford to brick this phone. If someone could assist me, I have the ATT model running build 656287. Would really appreciate assistance in being able to throw CM on here. Thanks!
unlock your device from htcdev.com
flash twrp
backup your rom and data
flash supersu
Behzad.hotknife said:
unlock your device from htcdev.com
flash twrp
backup your rom and data
flash supersu
Click to expand...
Click to collapse
Unlocked it perfectly, but when I flashed TWRP and tried to boot into it, it went back into stock recovery. Any ideas?
How are you flashing the recovery?
What command are you using?
Behzad.hotknife said:
How are you flashing the recovery?
What command are you using?
Click to expand...
Click to collapse
Fastboot flash recovery recovery.img
Try another twrp issue for your HTC one A9. Look for latest on twrp page. Then recovery will boot into twrp
Related
hello, im trying to install a custom rom, and now im in recovery step. i installed like 3 different recoverys.
all of them stuck in the red text step(when i get in to recovery mode from bootloader), and even after 20-30 mins still in the same position.
can someone say me when i need to do? i really need to fix it.
Snow201 said:
hello, im trying to install a custom rom, and now im in recovery step. i installed like 3 different recoverys.
all of them stuck in the red text step(when i get in to recovery mode from bootloader), and even after 20-30 mins still in the same position.
can someone say me when i need to do? i really need to fix it.
Click to expand...
Click to collapse
Make sure you are not plugged into your pc when you boot to recovery! - if that doesn't solve it ..
Does the phone boot to the existing Rom, do you have Rom manager installed? - if so update the recovery from Rom Manager. I found that after rooting the One S using the toolkit I could not get in to recovery, the update from Rom Manager sorted it!
All the best :good:
FatherD said:
Make sure you are not plugged into your pc when you boot to recovery! - if that doesn't solve it ..
Does the phone boot to the existing Rom, do you have Rom manager installed? - if so update the recovery from Rom Manager. I found that after rooting the One S using the toolkit I could not get in to recovery, the update from Rom Manager sorted it!
All the best :good:
Click to expand...
Click to collapse
i tried before to get in to recovery mode without USB(plugged to my computer or to charger) and still same problem.
and i dont have any rom manager.
i got HTC one S only with Unlocked phone and recovery(that doesnt work), so i think i need root for rom manager.
got something else?
Snow201 said:
i tried before to get in to recovery mode without USB(plugged to my computer or to charger) and still same problem.
and i dont have any rom manager.
i got HTC one S only with Unlocked phone and recovery(that doesnt work), so i think i need root for rom manager.
got something else?
Click to expand...
Click to collapse
Had same issue with the tool kit, the cwm didnt stick. The Touch work one did stick and I was able to get into recovery. However I downloaded the app ROM MANAGER and flashed the recovery from there. Since then I've had no issues booting into reocvery or bootloader. Just download rom manager and go about it that way!
osugsxr said:
Had same issue with the tool kit, the cwm didnt stick. The Touch work one did stick and I was able to get into recovery. However I downloaded the app ROM MANAGER and flashed the recovery from there. Since then I've had no issues booting into reocvery or bootloader. Just download rom manager and go about it that way!
Click to expand...
Click to collapse
NVM, there is no recovery for HTC at all, only Galaxy and some more. what i need to do?
I had this problem when I first rooted its weird just download the recovery again but save straight to fastboot folder wherever u have the folder and don't rename then flash the recovery that's how mine worked
Sent from my HTC One S using xda premium
k1llacanon said:
I had this problem when I first rooted its weird just download the recovery again but save straight to fastboot folder wherever u have the folder and don't rename then flash the recovery that's how mine worked
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
but i dont have root... and for root my phone i need recovery
there is some other way to root?
because the ROM manager doesnt work well without root.(cant install new recovery)
Snow201 said:
but i dont have root... and for root my phone i need recovery
there is some other way to root?
because the ROM manager doesnt work well without root.(cant install new recovery)
Click to expand...
Click to collapse
I'm not telling you to use Rom manager =\
Sent from my HTC One S using xda premium
k1llacanon said:
I'm not telling you to use Rom manager =\
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Ohh. .. but still in tried install the recovery like 2-4 times.
There is other way?
Snow201 said:
Ohh. .. but still in tried install the recovery like 2-4 times.
There is other way?
Click to expand...
Click to collapse
Which recoveries have you tried, and what version of phone do you have (S3 or S4). These must match.
Make sure you bootloader unlocked OK, check in bootloader screen, should say Unlocked.
The problem youre describing sound like when you try to boot after successfully flashing a ROM but forgot to or the kernel failed to flash with it. Only happens when ROM and kernel are mismatched enough that it wont boot, fex flashing CM9 and still on HTC original kernel. Try flashing the kernel from the ROM zip file with
Code:
fastboot flash boot boot.img
You can also try booting a recovery without installing it,
Code:
fastboot boot nameofrecoveryfile.img
frdd said:
Which recoveries have you tried, and what version of phone do you have (S3 or S4). These must match.
Make sure you bootloader unlocked OK, check in bootloader screen, should say Unlocked.
The problem youre describing sound like when you try to boot after successfully flashing a ROM but forgot to or the kernel failed to flash with it. Only happens when ROM and kernel are mismatched enough that it wont boot, fex flashing CM9 and still on HTC original kernel. Try flashing the kernel from the ROM zip file with
Code:
fastboot flash boot boot.img
You can also try booting a recovery without installing it,
Code:
fastboot boot nameofrecoveryfile.img
Click to expand...
Click to collapse
nope, until now i did only unlock for my phone. and i have no idea with version i have, how do i check it?
Snow201 said:
nope, until now i did only unlock for my phone. and i have no idea with version i have, how do i check it?
Click to expand...
Click to collapse
If you have working ADB and fastboot working (there is a sticky by user fibsib that explains this) you can make sure your phone isnt really just trying to boot the OS and failing rather than trying to enter recovery with the command
Code:
adb reboot recovery
But anyways figure out which version you have before doing anything more, flash the wrong stuff and you could break stuff. There are good info here as to how to see if you have the Ville=Z520e=S4 processor model or the Ville C2/Z560e/S3 processor model.
Then download a recovery for your phone model and install it with this command from your computer
Code:
fastboot flash recovery nameofrecoveryyoudownloaded.img
Should work.
have you actually flashed a recovery yet?
which one and how did you do it?
Make sure you have your phone updated to the latest software version before you root. Download system update OTA and click update.
Otherwise you will have issues.
I am rooted T-Mobile phone with original software 1.54 and still can not do recovery or update, it is probably me but it is difficult.
If you are in the US, make sure you use the US version in the development section after you upgrade your phone. Update then try to root it might be easier.
My boot loader and phone is rooted.
AT&T Htc one X
I have tried to flash a couple roms + the boot.img but the device pauses at HTC splash screen (I DID clear caches)
but its constant and I have to go into Fastboot-Usb and reinstall the RUU in order to try again.
Does anyone have any ideas?
viprk24 said:
My boot loader and phone is rooted.
AT&T Htc one X
I have tried to flash a couple roms + the boot.img but the device pauses at HTC splash screen (I DID clear caches)
but its constant and I have to go into Fastboot-Usb and reinstall the RUU in order to try again.
Does anyone have any ideas?
Click to expand...
Click to collapse
why don't you start by reading this http://forum.xda-developers.com/showthread.php?t=1957193
If you have ruu'ed you have to root again and unlock your bootloader again.
What recovery did you install ?
My bootloader is unlocked and my phone is rooted*
And I used TWRP or what ever its called. I can root fine and ez from it Trying to get Viperxl
viprk24 said:
My bootloader is unlocked and my phone is rooted*
And I used TWRP or what ever its called. I can root fine and ez from it Trying to get Viperxl
Click to expand...
Click to collapse
did you flash a recovery yet and if so which one ? if you want help you need to give us some details ?
What rom did you try to flash ? How did you go about it ?
Thank the android gods it wasn't an international ROM.
Did you flash superuser or supersu. We will need a little more information in the steps you've taken. Can you make a list of the steps for us?
The link crappyvate sent is a great tool for help.
Sent from my One X using xda premium
viprk24 said:
My bootloader is unlocked and my phone is rooted*
And I used TWRP or what ever its called. I can root fine and ez from it Trying to get Viperxl
Click to expand...
Click to collapse
Crappyvate said:
did you flash a recovery yet and if so which one ? if you want help you need to give us some details ?
What rom did you try to flash ? How did you go about it ?
Click to expand...
Click to collapse
apparently he did and some did not read the information
I have flashed TWRP recovery or what ever I have installed Supersu successfuly and full root. I restarted booted into recovery now and wiped system cleared cache now I'm going to attempt to flash it one more time.
CheesyNutz said:
apparently he did and some did not read the information
Click to expand...
Click to collapse
surprise...that would be a first
---------- Post added at 11:07 PM ---------- Previous post was at 11:05 PM ----------
subarudroid said:
Thank the android gods it wasn't an international ROM.
Did you flash superuser or supersu. We will need a little more information in the steps you've taken. Can you make a list of the steps for us?
The link crappyvate sent is a great tool for help.
Sent from my One X using xda premium
Click to expand...
Click to collapse
don't think so since apparently he still gets the htc splash screen but need more info.
viprk24 said:
I have flashed TWRP recovery or what ever I have installed Supersu successfuly and full root. I restarted booted into recovery now and wiped system cleared cache now I'm going to attempt to flash it one more time.
Click to expand...
Click to collapse
what exactly is it doing im not understanding is it freezing ? just not installing what error code is it giving
Are you flashing the boot image for your ROM in adb?
Sent from my One X using xda premium
viprk24 said:
I have flashed TWRP recovery or what ever I have installed Supersu successfuly and full root. I restarted booted into recovery now and wiped system cleared cache now I'm going to attempt to flash it one more time.
Click to expand...
Click to collapse
ok. i'm not gonna beg if you want help I need DETAILS not vague s***t like "TWRP or whatever".. So evidently you can boot into recovery with no problem. What rom are you trying to flash ? You need to extract the boot.img from the rom.zip and flash that in fastboot and then flash the rom.zip in recovery.
If you're not booting it's most likely because your phone is not finding a kernel (boot.img)
So more details or more reading
Good luck to you
Crappyvate said:
ok. i'm not gonna beg if you want help I need DETAILS not vague s***t like "TWRP or whatever".. So evidently you can boot into recovery with no problem. What rom are you trying to flash ? You need to extract the boot.img from the rom.zip and flash that in fastboot and then flash the rom.zip in recovery.
If you're not booting it's most likely because your phone is not finding a kernel (boot.img)
So more details or more reading
Good luck to you
Click to expand...
Click to collapse
from what i can make out
hes flashed the boot.img
installed twrp
superSU
but with no details on what ERROR its giving we as a help teams are FUBARD
CheesyNutz said:
from what i can make out
hes flashed the boot.img
installed twrp
superSU
but with no details on what ERROR its giving we as a help teams are FUBARD
Click to expand...
Click to collapse
not sure the boot.img was flashed the right way...or in the right place
Calm down trolls I simply said
I flashed TRWP
Flashed Supersu
Flashboot oem unlock (Successful)
Relaunched back into bootloader
I fastboot boot.img
Then to Recovery where I Cleared cache and wiped System.
I then reflashed recovery because i wiped system.
I relaunched back into recovery and flashed rom
viprk24 said:
Calm down trolls I simply said
I flashed TRWP
Flashed Supersu
Flashboot oem unlock (Successful)
Relaunched back into bootloader
I fastboot boot.img
Then to Recovery where I Cleared cache and wiped System.
I then reflashed recovery because i wiped system.
I relaunched back into recovery and flashed rom
Click to expand...
Click to collapse
Its not a good idea to ask for help and then flame. Honestly what was hard about posting this the first time? I thought maybe English wasn't your language or something. How could you flash a recovery before unlocking???
If you wiped everything, you should reflash bootimage in adb. Then flash your ROM. Please be nice.
Sent from my One X using xda premium
viprk24 said:
Calm down trolls I simply said
I flashed TRWP
Flashed Supersu
Flashboot oem unlock (Successful)
Relaunched back into bootloader
I fastboot boot.img
Then to Recovery where I Cleared cache and wiped System.
I then reflashed recovery because i wiped system.
I relaunched back into recovery and flashed rom
Click to expand...
Click to collapse
yea bash the folks attempting to help you ... thats like biting the hand that feeds you .. im out have fun
CheesyNutz said:
yea bash the folks attempting to help you ... thats like biting the hand that feeds you .. im out have fun
Click to expand...
Click to collapse
likewise. Over and out.
curious if there is something i'm missing here... i've unlocked my bootloader successfully but whenever i fastboot flash a recovery or flash root files in recovery nothing seems to stick... not sure whats going on... i've heard of having to flash recovery everytime on devices with a locked bootloader but i didn't think that would apply here... any help is much appreciated... (this is also my first samsung/nexus device so i'm more familiar with methods used on the EVO line)
thispaininmyhead said:
curious if there is something i'm missing here... i've unlocked my bootloader successfully but whenever i fastboot flash a recovery or flash root files in recovery nothing seems to stick... not sure whats going on... i've heard of having to flash recovery everytime on devices with a locked bootloader but i didn't think that would apply here... any help is much appreciated... (this is also my first samsung/nexus device so i'm more familiar with methods used on the EVO line)
Click to expand...
Click to collapse
Make sure you're using a perm root method. and make sure you have the correct updated SU application. My root wouldn't come through because I didn't have the latest SU.
Hopefully I helped.
thispaininmyhead said:
curious if there is something i'm missing here... i've unlocked my bootloader successfully but whenever i fastboot flash a recovery or flash root files in recovery nothing seems to stick... not sure whats going on... i've heard of having to flash recovery everytime on devices with a locked bootloader but i didn't think that would apply here... any help is much appreciated... (this is also my first samsung/nexus device so i'm more familiar with methods used on the EVO line)
Click to expand...
Click to collapse
Hi,
What root method did u use?
What recovery are u using?
What ROM are u flashing?
The more info, the better
Vs Nexus S4G using tapatalk2
Unlocked the boot loader with fast boot commands then flashed superuser.zip with clockwork 3.x.x and twrp 2.2.0 haven't tried flashing any Roms since nothing seems to stick...
Sent from my Nexus S 4G using Tapatalk 2
And Vidal I used the toolkit you linked me to in my last q&a post...
Sent from my Nexus S 4G using Tapatalk 2
vidaljs said:
Hi,
What root method did u use?
What recovery are u using?
What ROM are u flashing?
The more info, the better
Also after looking into the scripts and files in the method with the toolkit it seems none of the files get pushed to the device to begin flashing
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
By default, any recovery you flash on the system will be gone by the next reboot. This is a security measure the android os does I think.
1. You can flash a ROM. Anyone. I prefer aokp or cna. That way the recovery sticks (the recovery sticks on all the ROMs besides stock)
OR
P.S. You will need the latest cwm recovery
2. So all you need to do is to flash the recovery of your choice. I would recommend CWM for this short guide. Then once flashed go to the recovery make a backup. Then if it reboots flash the same recovery again. Boot into it and restore that backup. When you restore it and go reboot system now it should come up with a menu saying recovery flash fix (or something around those lines). Hit/navigate to yes and you should get a sticky recovery from there. BTW I have not tried this method.
You cannot blame me for bricking, damaging or done anything to your phone
Hope this helps.
Regards,
UselessSniper001
P.S. I don't know how root isn't sticking. I mean if you have flashed the su is the recovery already well then you are all set to go. Unless you haven't actually flashed the su in the recovery. Then flash the recovery from your PC boot into the recovery and flash the su files in the recovery. Reboot and enjoy. Then follow this guide above. Or follow this link:
http://forum.xda-developers.com/showthread.php?t=875875&page=2
I finally figured out the SU and CWM I was flashing was ancient so I found the newest and they stuck with help of the fix ya mentioned inside CWM... Thanks
Sent from my Nexus S 4G using Tapatalk 2
Hey.
Need you help or advice..
I made a mistake when flashed my ATT One X with the latest firmware(
And now i can't do anything, I mean root or custom recovery.
I have S-OFF and super CID but I don't how to fix this.. to downgrade or to roll back to oldest firmware.
Even to have root will be perfect.
How can I manage this?
Thanks in advance!
vimev said:
Hey.
Need you help or advice..
I made a mistake when flashed my ATT One X with the latest firmware(
And now i can't do anything, I mean root or custom recovery.
I have S-OFF and super CID but I don't how to fix this.. to downgrade or to roll back to oldest firmware.
Even to have root will be perfect.
How can I manage this?
Thanks in advance!
Click to expand...
Click to collapse
According to your bootloader details you are at a good starting point. Here is what I recommend you do from here:
1. Download a custom recovery like TWRP:
http://forum.xda-developers.com/showthread.php?t=2558503
2. flash this in bootloader mode. If you don't know how here is the help thread you need to read through:
http://forum.xda-developers.com/showthread.php?t=2593382
3. Once you have a custom recovery installed, you can flash SuperSu or other root app (google is your friend.)
4. Stick with the rooted rom you have or flash another of your choosing.
Madcat8686 said:
According to your bootloader details you are at a good starting point. Here is what I recommend you do from here:
1. Download a custom recovery like TWRP:
http://forum.xda-developers.com/showthread.php?t=2558503
2. flash this in bootloader mode. If you don't know how here is the help thread you need to read through:
http://forum.xda-developers.com/showthread.php?t=2593382
3. Once you have a custom recovery installed, you can flash SuperSu or other root app (google is your friend.)
4. Stick with the rooted rom you have or flash another of your choosing.
Click to expand...
Click to collapse
Men.. thats great! Thanks a lot!
I was thinking its impossible to make root...
vimev said:
Men.. thats great! Thanks a lot!
I was thinking its impossible to make root...
Click to expand...
Click to collapse
Not impossible for you because your bootloader is unlocked and you are S-Off. You are always able to root and flash.
Hey, I have the same bootloader setup but i am unable to flash a recovery
Grinno said:
Hey, I have the same bootloader setup but i am unable to flash a recovery
Click to expand...
Click to collapse
What happens when you try to flash a recovery?
What recovery are you trying to flash?
Post your own bootloader (Don't show the IMEI)
Madcat8686 said:
Not impossible for you because your bootloader is unlocked and you are S-Off. You are always able to root and flash.
Click to expand...
Click to collapse
exad said:
What happens when you try to flash a recovery?
What recovery are you trying to flash?
Post your own bootloader (Don't show the IMEI)
Click to expand...
Click to collapse
I use EZT toolkit....It runs the commands then said fail (too many links
Grinno said:
I use EZT toolkit....It runs the commands then said fail (too many links
Click to expand...
Click to collapse
Why are you using a toolkit to flash recovery???
Just download from http://goo.im/devs/OpenRecovery/evita
or download the unofficial TWRP from the original android dev section if you plan on flashing an AOSP or CM based Rom and then fastboot flash recovery recovery_filename.img
Easy peasy. Too many links is an error that should have nothing to do with flashing recovery...
exad said:
Why are you using a toolkit to flash recovery???
Just download from http://goo.im/devs/OpenRecovery/evita
or download the unofficial TWRP from the original android dev section if you plan on flashing an AOSP or CM based Rom and then fastboot flash recovery recovery_filename.img
Easy peasy. Too many links is an error that should have nothing to do with flashing recovery...
Click to expand...
Click to collapse
Donno, Maybe fastboot/drivers or messed up. I keep getting cannot load 'recovery.img' unknown error
Grinno said:
Donno, Maybe fastboot/drivers or messed up. I keep getting cannot load 'recovery.img' unknown error
Click to expand...
Click to collapse
You need to type the filename of the recovery file you download. Either the recovery filename you are typing is wrong or the file is not in the folder you are trying to flash from.
exad said:
You need to type the filename of the recovery file you download. Either the recovery filename you are typing is wrong or the file is not in the folder you are trying to flash from.
Click to expand...
Click to collapse
Thanks, Got it to flash..... you were correct i was typing the filename wrong.
Guys, use this modified boot image to flash the newest Android L (5.0.0_LRX21P)
Flash in Bootloader (this is not a flashable zip)!!!!
Flash the stock root able rom, here available on xda.
Don't worry it's for our FLO device, just a name. Sorry, i was in a hurry.
Have fun
Jerome-X said:
Guys, use this modified boot image to flash the newest Android L (5.0.0_LRX21P)
Flash in Bootloader (this is not a flashable zip)!!!!
Flash the stock root able rom, here available on xda.
Don't worry it's for our FLO device, just a name. Sorry, i was in a hurry.
Have fun
Click to expand...
Click to collapse
Whats modified about it?
use this, if you want to flash the stock rooted rom via twrp etc...
if you use the stock one, your bootloader is locked after flash the stock rom
Jerome-X said:
use this, if you want to flash the stock rooted rom via twrp etc...
if you use the stock one, your bootloader is locked after flash the stock rom
Click to expand...
Click to collapse
Incorrect mate, it's still unlocked after flashing factory images. I flashed factory files yesterday and I only lost root and recovery which I expected to happen.
topgeardave said:
Incorrect mate, it's still unlocked after flashing factory images. I flashed factory files yesterday and I only lost root and recovery which I expected to happen.
Click to expand...
Click to collapse
Correct!
Op tell me exactly what you did here? Your talking about one thing but saying another. I dont get it
scrosler said:
Correct!
Op tell me exactly what you did here? Your talking about one thing but saying another. I dont get it
Click to expand...
Click to collapse
It's just the latest bootloader.img, he thinks if you flash it separately you won't lock your bootloader before flashing the stock rom via recovery.
To my knowledge, nothing locks the bootloader, except you (via fastboot or a toolkit).
So i can install the stock image i downloaded from google and still keep root? What about recovery?
Sorry for noob question, i've only used custom ROMs in the past.
If you flash the stock L image with fastboot, you lose root and recovery but your boot loader stays locked/unlocked (whatever it was before).
To get recovery back, just flash it with fastboot.
To get root back, flash the boot image from the OP or a modified kernel like ElementalX and then flash SuperSU.
Done.
Sent from my LG-D801
Thanks for the answer.